Upgrade win32metadata to 60.0.34

https://www.nuget.org/packages/Microsoft.Windows.SDK.Win32Metadata/60.0.34-preview
For me this most notably includes D3D12 Agility SDK 1.613.1 and annotations that leverage #2771.

Thanks for the reminder - I'll update the metadata shortly.

@kennykerr why insta-close this when an external contributor has already put in the work?

There are many external contributors. The top contributors are all non-Microsoft last I checked.
The metadata has blocking bugs that need to be resolved first (e.g. https://github.com/microsoft/win32metadata/issues/1908)
There isn't currently a way to validate the winmd provenance, so it has to be done in house. Once we have a yml workflow to validate provenance, external contributors can update metadata.
Your PR snuck in unrelated changes beyond simply updating metadata.

Can I submit the "unrelated changes" separately without risking them being closed, such as readability improvements to crates/libs/bindgen/default/readme.md and handling PSID?

For what it's worth, starting an insta-close with a more thorough review like the above would have been a lot more friendly.

Discrete contributions fixing very specific things are welcome. A PR to improve a readme file for example is great.
An "unrelated changes" PR that includes fixes to a variety of unrelated things will not be accepted.
If there's anything that requires discussion, please open an issue for discussion to avoid spending time on a PR unnecessarily.

An "unrelated changes" PR that includes fixes to a variety of unrelated things will not be accepted.

Yeah, that's implicit. I shouldn't have sneaked the formatting fixes in for sure.

and handling PSID?

This won't have an effect without the metadata update, and is probably not very useful to you in isolation.

@kennykerr I do have a specific question with regards to DXGI_SWAP_CHAIN_DESC(1)::Flags (and the decode desc) which is of type UINT. In https://github.com/microsoft/win32metadata/pull/1757 I associated that with DXGI_SWAP_CHAIN_FLAG, but this enum has int ABI by default (unlike the enums I added in that PR in enums.json which were all given "type": "uint", and ILSpy shows e.g. enum DXGI_PRESENT : uint).
Is there anything we can do in windows-rs to tie this back to an enum type when the ABI mismatches? Is there a tracking issue open about this?

[..] unlike the enums I added in that PR in enums.json which were all given "type": "uint", and ILSpy shows e.g. enum DXGI_PRESENT : uint).

We need to go back and fix that in metadata; looks like we missed these uint types. I probably should have been more clear in my PR comment.

We'll have to wait for this (and https://github.com/microsoft/win32metadata/issues/1908) to get fixed before updating windows-rs.

@riverar thanks, what's the right way to correct the type, list it in enums.json?

@MarijnS95 Ideally yup, with the rsp method as a fallback. We can double-check with Mike too on the other side of the fence.

[..] unlike the enums I added in that PR in enums.json which were all given "type": "uint", and ILSpy shows e.g. enum DXGI_PRESENT : uint).

We need to go back and fix that in metadata; looks like we missed these uint types. I probably should have been more clear in my PR comment.

@riverar just to double-check, what do you mean by this?

The type: uint was wrong, and should have been kept at the default int?
Forcing the untyped enums like DXGI_SWAP_CHAIN_FLAG mentioned here to uint, as that is how all current ABI is using it?

I assume the latter.


Implement Posix timer functionality

We need clock_gettime to do #161, and newlib has that, but only if _POSIX_TIMERS is defined. We might need to rebuild newlib to enable this.

We also need clock_gettime for lest (and that's all it needs). I did a stub here

We have CMOS-time now, with a helper to compute seconds since epoch. The issue with using that directly is that it's horribly expensive, like 200k cycles (!) depending on your system (lots of vm exits). We're looking at how we can implement better time-keeping solution, without relying on regular timer interrupts (which we only have on if timers are active).

Implemented with RTC.


Support Android API levels 24 - 27

Fixes #13883.
@I3oris The ioctl definition in the REPLy shard has been modified because it is incompatible with Bionic C's definition, needed by this PR. Feel free to incorporate this into upstream.

reply is  is the upstream repo for the lib/reply subtree in this directory. Any change we do in that directory should be upstreamed to keep in sync. Or better: apply it upstream first and then downstream it by pulling the subtree.

So in case of those upstream repos ever becomes inactive (and we don't take ownership), does that permanently prevent us from applying patches like this?

Then we could fork our own upstream.
Or break the subtree connection entirely. If the upstream repo is inactive, there's no reason to stay in sync anyway.

The objective is that we should always be able to pull in the latest upstream changes with git subtree pull --prefix lib/reply https://github.com/I3oris/reply master. Without having to resolve conflicts because we added our own modifications.

I just realized that for some reason lib/reply isn't actually setup as a subtree. We'll have to fix that, but not in this PR.


feat: switch to file-based OLM catalogs

In order to switch to new file-based OLM catalogs, following changes were made

upgrade to newer version of operator-sdk tools (operator-sdk, olm)

Generate existing bundles

Add 0.0.13 bundle to the new catalog image by

creating new catalog index dockerfile
adding package definition for observability-operator *  add 0.0.13 bundle and channels

Add olm/update-channels.sh script to update olm catalog channels

Fix GitHub workflow to adapt to constraints introduced by the new file-based catalog

NOTE: This PR introduces a change to CI post-merge action - release.
Previously, when a commit is merged to main, the CI job used to publish a catalog image which did not require any change to the code. With the file-based catalog, the new bundle that is published needs to be added to the catalog index.yaml file. Hence, the CI job release that calls the olm-publish action now adds a commit on top the commit that got merged into main and pushes that commit to the repo if a catalog image could be published successfully.
JIRA: https://issues.redhat.com/browse/MON-2791
Signed-off-by: Sunil Thaha<EMAIL_ADDRESS>

I tried to release my custom catalog image and deploy it to my 4.12 cluster and it works fine.

@jan--f

I think it would be great to have more comments around the opm usage, especially the Dockerfile and opm serve. The documentation wasn't super straight forward to find and outlining what these pieces actually do might be a service to future developers.

As soon as this merges, I am happy to write a docs/ops/release.md where we can explain the release workflow.
For OLM Catalog I used the following refs

https://olm.operatorframework.io/docs/tasks/creating-a-catalog/
https://docs.okd.io/4.11/operators/admin/olm-managing-custom-catalogs.html#olm-managing-custom-catalogs-fb

Where do we want these references to be updated?

Closing this in favour of https://github.com/rhobs/observability-operator/pull/195 where the catalog index file will be maintained in the olm-catalog branch


As an addition to #334 have convenience methods for EF json(b) value conversions

We're currently using something like this in our codebase, it won't allow you to query into it but we always pull in the full entity on other criteria anyway.
    public static class NpgsqlEntitiyFrameworkConversionExtensions
    {
        private class JsonConversion<TModel> : ValueConverter<TModel, string>
        {
            public JsonConversion(Formatting formatting = Formatting.None) :
                base(
                    model => JsonConvert.SerializeObject(model, formatting),
                    str => JsonConvert.DeserializeObject<TModel>(str)
                )
            {
            }
        }

        public static PropertyBuilder<TModel> HasJsonConversion<TModel>(this PropertyBuilder<TModel> builder, Formatting formatting = Formatting.None)
            => builder.HasColumnType("json").HasConversion(new JsonConversion<TModel>(formatting));

        public static PropertyBuilder<TModel> HasJsonbConversion<TModel>(this PropertyBuilder<TModel> builder)
            => builder.HasColumnType("jsonb").HasConversion(new JsonConversion<TModel>());
    }

Related: #334
Also until 2.1.3 is out people will have issues like this https://github.com/npgsql/Npgsql.EntityFrameworkCore.PostgreSQL/issues/412 (if they map to JObject or friends)
The temporary fix (and same issue) is noted here https://github.com/aspnet/EntityFrameworkCore/issues/12203

It's a nice idea. But do you really think belongs in the Npgsql provider, as opposed to the user's codebase? Reasons not to may be:

There's very little extra value here (users can easily define this themselves)
This has nothing to do with Npgsql and can work just as well on any other provider (so you may actually consider proposing this to EF Core)

True, without being able to query on it such a thing could indeed work for other databases. I can't wait for npgsql support for Json.Net as I've copied this file into quite a few projects already ;)

Trust me, I really tried to have a proper JSON.NET plugin (#334) with querying for 2.1, but the expression translating turned out to have some serious complications (documented there). I really hope we find a good way around the issues and have a plugin ready for 2.2.
Am going to close this for now - as I wrote above I actually think it could be a nice addition to EF Core, consider sending them a PR.


Bugfix/cloning environment

About this PR
TLDR: The rolebinding named admin from the cloned source environment is lost during cloning and instead replaced by the rolebinding created from oc new-project. This results nonetheless in a usable cloned environment and fixes the issues listed by Gerard.
Proposal: Once this is merged, open an issue to handle this better in 2.0. I believe that using tailor could simplify the cloning scripts a lot.
Details:
oc new-project <project-name>  creates a role binding with name admin, for example (abbreviated):
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  name: admin
  namespace: autst-feature-16
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: admin
subjects:
  - kind: ServiceAccount
    name: jenkins
    namespace: autst-cd

When using oc apply the role binding named admin in rolebinding.yaml (exported from the cloned environment, here autst-dev) wins and replaces the role binding above.
This means jenkins itself no longer has admin provisions and fails fatally.
When using oc create however the existing rolebinding created by new-project is not overwritten. However the rolebinding named 'admin' from rolebinding.yaml gets lost.
In projects created with the provisioning app, the rolebinding called admin typically have the admin users who where listed during creation and the service account cd/cd-integration in it.
Losing these permissions in the cloned project is typically not a (bigger) problem .
We tested the changes with our production environment(s).
We aim to target fixing this more fundamentally for ODS 2.0.
Thanks to @clemensutschig for getting to these findings!


[Bug]: OpenAI Agents ValueError: Tool with name python not found

Bug Description
I have not  make any function with name of python. But still I am getting an error of tool not fond with python name.
Version
Tried with 0.7.20 to 0.8.0
Steps to Reproduce
def multiply(args: list) -> int:
    print(numpy.prod((args)))
    return numpy.prod((args))

multiply_tool = FunctionTool.from_defaults(fn=multiply)

def add(args: list) -> int:
    for num in args:
        num+=num
    return num

add_tool = FunctionTool.from_defaults(fn=add)

llm = OpenAI(temperature=0, model="gpt-3.5-turbo-0613", openai_api_key='api_key')
agent = OpenAIAgent.from_tools(
    [
        multiply_tool,
        add_tool,
    ],
    llm=llm,
    verbose=True,
    callback_manager=callback_manager
)

response = agent.chat("a ate 2 apples, b ate 9 apples and c ate 1 apples. 1 apple cost is 7.8. how much total cost will be")
print('response = ',response)

Relevant Logs/Tracbacks
ValueError                                Traceback (most recent call last)
/tmp/ipykernel_41861/1112129131.py in <module>
----> 1 response = agent.chat("a ate 2 apples, b ate 9 apples and c ate 1 apples. I apple cost is 7.8. how much total cost will be")
      2 print('response = ',response)

~/anaconda3/lib/python3.10/site-packages/llama_index/agent/openai_agent.py in chat(self, message, chat_history, function_call)
    267         function_call: Union[str, dict] = "auto",
    268     ) -> AgentChatResponse:
--> 269         chat_response = self._chat(
    270             message, chat_history, function_call, mode=ChatResponseMode.WAIT
    271         )

~/anaconda3/lib/python3.10/site-packages/llama_index/agent/openai_agent.py in _chat(self, message, chat_history, function_call, mode)
    232                 break
    233             assert isinstance(self.latest_function_call, dict)
--> 234             self._call_function(tools, self.latest_function_call)
    235             n_function_calls += 1
    236

~/anaconda3/lib/python3.10/site-packages/llama_index/agent/openai_agent.py in _call_function(self, tools, function_call)
    176
    177     def _call_function(self, tools: List[BaseTool], function_call: dict) -> None:
--> 178         function_message, tool_output = call_function(
    179             tools, function_call, verbose=self._verbose
    180         )

~/anaconda3/lib/python3.10/site-packages/llama_index/agent/openai_agent.py in call_function(tools, function_call, verbose)
     46         print("=== Calling Function ===")
     47         print(f"Calling function: {name} with args: {arguments_str}")
---> 48     tool = get_function_by_name(tools, name)
     49     argument_dict = json.loads(arguments_str)
     50     output = tool(**argument_dict)

~/anaconda3/lib/python3.10/site-packages/llama_index/agent/openai_agent.py in get_function_by_name(tools, name)
     33     name_to_tool = {tool.metadata.name: tool for tool in tools}
     34     if name not in name_to_tool:
---> 35         raise ValueError(f"Tool with name {name} not found")
     36     return name_to_tool[name]
     37

ValueError: Tool with name python not found

Hi, following up on this to say that I'm getting this error too.

Hi, I'm also getting this "python not found error" when trying to recreate this Multi-docs agent notebook:
https://docs.llamaindex.ai/en/stable/examples/agent/multi_document_agents/
The only part I changed with the code is the document names part; other than that, it's basically bone stock as the example.
This was run on llama-index v0.10.25.
Please let me know if you need more materials.  Thank you in advance.


Incorrect module structure advice

Plugin version
1.32.0
Gradle version
8.4
JDK version
17
(Optional) Kotlin and Kotlin Gradle Plugin (KGP) version
1.9.23
(Optional) Android Gradle Plugin (AGP) version
8.3.2
Describe the bug
We have module C, which depends on project android modules A and B, as well as on android compose dependencies.
The report contains advice that module C could be a JVM project.
Module structure advice
This project uses limited Android features and could be a JVM project.
* Has Android library dependencies.

We cannot remove Android dependencies from this module, which means, as far as I understand, we cannot make this module a JVM project. However, the check fails with the advice to change the module structure to the JVM project.
We have temporarily disabled module structure checks:
issues {
    all {
        onModuleStructure {
            severity("ignore")
        }
    }
}

We have other similar modules in our project, but the reports do not contain similar advice for them.
How can we suppress this particular advice?
To Reproduce
Steps to reproduce the behavior:

Create Android module A
Create Android module B
Create a dependency of module B on module A
Add multiple dependency composites to module B
Run check on module B

Expected behavior
The absence of such advice for modules that cannot get rid of Android dependencies or a clear way to suppress such advice.

Thanks for the issue.
There are two kinds of "module advice" related to this:

This project uses limited Android features and could be a JVM project.
This project uses no Android features and should be a JVM project.

What you have is could. The difference is based on a heuristic that gives various Android feature a value and, if the sum of the values reaches a certain threshhold, it trips over from could to should.
The truth is I simply haven't had enough feedback on this feature, which should be considered "incubating" to use Gradle terminology, so I don't know where that line should be. I appreciate this feedback.


All space-cli getters throws weird errors if project flag isn't provided

Running space-cli get <> without the --project flag throws unpredictable errors. We should have a function called getProjectID() which returns the projectID and a boolean (specifying if the projectID) exists are not. This function will attempt to get the projectId from viper.
All getters can call this function and check if the projectId has been provided

is there a way in viper to make the flag as required compulsory

We cannot make this flag required since its a persistent flag


Failed to activate the atom-color-highlight package

[Enter steps to reproduce below:]

...
...

Atom Version: 1.2.4
System: Mac OS X 10.11.1
Thrown From: Atom Core
Stack Trace
Failed to activate the atom-color-highlight package
At Cannot read property 'eachEditorView' of undefined

TypeError: Cannot read property 'eachEditorView' of undefined
    at AtomColorHighlight.activate (<anonymous>:34:23)
    at Package.module.exports.Package.activateNow (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:170:19)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/package.js:150:32
    at Package.module.exports.Package.measure (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:92:15)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/package.js:143:26
    at Package.module.exports.Package.activate (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:140:34)
    at PackageManager.module.exports.PackageManager.activatePackage (/Applications/Atom.app/Contents/Resources/app.asar/src/package-manager.js:512:21)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/package-manager.js:495:29
    at Config.module.exports.Config.transact (/Applications/Atom.app/Contents/Resources/app.asar/src/config.js:311:16)
    at PackageManager.module.exports.PackageManager.activatePackages (/Applications/Atom.app/Contents/Resources/app.asar/src/package-manager.js:490:19)

Commands

Config
{
  "core": {
    "disabledPackages": [
      "autoflow",
      "minimap"
    ],
    "themes": [
      "atom-dark-ui",
      "tomorrow-night-eighties"
    ]
  },
  "editor": {
    "fontSize": 14,
    "preferredLineLength": 2000
  }
}

Installed Packages
# User
atom-color-highlight, v2.0.14
autocomplete-plus, v0.22.3
merge-conflicts, v1.2.8
tomorrow-night-eighties, v0.1.0

# Dev
No dev packages

The atom-color-highlight package appears to have been unpublished.  I would suggest uninstalling it and finding an alternative.


FAILED - RETRYING: Master | wait for the apiserver to be running

I started playing around with kubernetes and kubespray and created 3 new servers for my first cluster. Unfortunately kubespray playbook dies while waiting for apiserver. Do you have any advice how to solve this issue?
Thanks!
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT
Environment:

Cloud provider or hardware configuration:
3 VMs running on ESXI 6.5
ux-messias: 2 cores / 4 GB RAM
node-one & node-two: 2 cores / 2 GB RAM

Ansible host:
Laptop i7, 12GB RAM

OS (printf "$(uname -srm)\n$(cat /etc/os-release)\n"):

Ansible host:
cwo@hermes:~/dev/kubespray$ printf "$(uname -srm)\n$(cat /etc/os-release)\n"
Linux 4.13.0-36-generic x86_64
NAME="Ubuntu"
VERSION="17.10 (Artful Aardvark)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 17.10"
VERSION_ID="17.10"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=artful
UBUNTU_CODENAME=artful
Kubernetes cluster nodes:
cwo@hermes:~/dev/kubespray$ ansible all -b -K -i inventory/esxi/hosts.ini -m raw -a 'printf "$(uname -srm)\n$(cat /etc/os-release)\n"'
SUDO password:
node-one | SUCCESS | rc=0 >>
Linux 4.4.0-116-generic x86_64
NAME="Ubuntu"
VERSION="16.04.4 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.4 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial
Shared connection to node-one closed.
ux-messias | SUCCESS | rc=0 >>
Linux 4.4.0-116-generic x86_64
NAME="Ubuntu"
VERSION="16.04.4 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.4 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial
Shared connection to ux-messias closed.
node-two | SUCCESS | rc=0 >>
Linux 4.4.0-116-generic x86_64
NAME="Ubuntu"
VERSION="16.04.4 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.4 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial
Shared connection to node-two closed.

Version of Ansible (ansible --version):
cwo@hermes:~/dev/kubespray$ ansible --version
ansible <IP_ADDRESS>
config file = /home/cwo/dev/kubespray/ansible.cfg
configured module search path = [u'/home/cwo/dev/kubespray/library']
ansible python module location = /usr/lib/python2.7/dist-packages/ansible
executable location = /usr/bin/ansible
python version = 2.7.14 (default, Sep 23 2017, 22:06:14) [GCC 7.2.0]

Kubespray version (commit) (git rev-parse --short HEAD):
cwo@hermes:~/dev/kubespray$ git rev-parse --short HEAD
a40d9f3c
Network plugin used:
DEFAULT?
Copy of your inventory file:
[kube-master]
ux-messias
[etcd]
ux-messias
node-one
node-two
[kube-node]
node-one
node-two
[k8s-cluster:children]
kube-node
kube-master
Command used to invoke ansible:
ansible-playbook -K -b -i inventory/esxi/hosts.ini cluster.yml
Output of ansible run:
https://gist.github.com/chr1stus/22317a592e9ce29492a536faf0c0c65e
Anything else do we need to know:
cwo@ux-messias:~$ sudo docker ps -a
CONTAINER ID        IMAGE                                                                                COMMAND                  CREATED             STATUS                            PORTS               NAMES
628cb192cd64        quay.io/coreos/hyperkube@sha256:7f7c0a9a488286741479b793428411003edc8f9bdab8e686554da761f76bd443   "/hyperkube apiser..."   2 minutes ago       Exited (255) About a minute ago                       k8s_kube-apiserver_kube-apiserver-ux-messias_kube-system_80452df2c3d5de416f3a5ae96654977d_1
40d0d0c90e2e        quay.io/coreos/hyperkube@sha256:7f7c0a9a488286741479b793428411003edc8f9bdab8e686554da761f76bd443   "/hyperkube proxy ..."   11 minutes ago      Up 11 minutes                                         k8s_kube-proxy_kube-proxy-ux-messias_kube-system_5367c140f9e735ce76c671a93d65491f_4
21c156962075        quay.io/coreos/etcd:v3.2.4                                                                         "/usr/local/bin/etcd"    11 minutes ago      Up 11 minutes                                         etcd1
9a48db35055b        gcr.io/google_containers/pause-amd64:3.0                                                           "/pause"                 11 minutes ago      Up 11 minutes                                         k8s_POD_kube-apiserver-ux-messias_kube-system_80452df2c3d5de416f3a5ae96654977d_8
dad78141386a        gcr.io/google_containers/pause-amd64:3.0                                                           "/pause"                 11 minutes ago      Up 11 minutes                                         k8s_POD_kube-proxy-ux-messias_kube-system_5367c140f9e735ce76c671a93d65491f_6
68886d177d6d        quay.io/coreos/hyperkube@sha256:7f7c0a9a488286741479b793428411003edc8f9bdab8e686554da761f76bd443   "/hyperkube proxy ..."   12 minutes ago      Exited (1) 12 minutes ago                             k8s_kube-proxy_kube-proxy-ux-messias_kube-system_5367c140f9e735ce76c671a93d65491f_3
809c4db66b4a        gcr.io/google_containers/pause-amd64:3.0                                                           "/pause"                 12 minutes ago      Exited (0) 12 minutes ago                             k8s_POD_kube-proxy-ux-messias_kube-system_5367c140f9e735ce76c671a93d65491f_4
2188ee0dc3b6        quay.io/coreos/hyperkube@sha256:b5eb7d69ca52899d0cbc395a68129b6ca35d1f632a189d7869b25968e2065a19   "/hyperkube proxy ..."   23 hours ago        Exited (1) 23 hours ago                               k8s_kube-proxy_kube-proxy-ux-messias_kube-system_b8b88e6f3de59c2991792a35a4da3dbe_279
208c6b276ecc        gcr.io/google_containers/pause-amd64:3.0                                                           "/pause"                 45 hours ago        Exited (0) 23 hours ago                               k8s_POD_kube-proxy-ux-messias_kube-system_b8b88e6f3de59c2991792a35a4da3dbe_1
cwo@ux-messias:~$ sudo docker logs 628cb192cd64 >& apiserver-fail.log

apiserver-fail.log

Hi!
In the meanwhile I switched from master to v2.4.0 tag - still have the same issue. I can also reproduce this with vagrant, too.
-- Christian

Ansible output not properly visible, can you fix that ?

Hi,
I fixed the output for the ansible run & attached docker logs from apiserver.
Based on how I understood the apiserver.log, I reviewed the config and changed some parameters - I guess the important thing was to change group_vars/all.yml and explicit set the cert_management parameter. I thought cert_management: script is a default parameter and had this parameter not set before.
Now my cluster is deploying!!!
Nevertheless - I would like to understand what I did wrong to let other newbies not run into the same issue!
Thanks for your help!
Regards,
Christian

by seeing this output this is not cert_management: script problem definitely, but from this output it's pretty hard to guess where is the problem, i would say that there is some wrong character somewhere and by that it was failing, but not sure. if this is fixed by you and you don't know where the issue was i will close this issue, if problem happens again feel free to reopen or join slack channel where you can talk with others (even those who don't read issues)

I can confirm that cert_management: script not not seem to be the default.  I stumbled on this error using master branch using contrib/terraform/openstack. And uncommenting cert_management: script plus re-run got me past the error.  Thanks @chr1stus!


Vercel: This Serverless Function (FUNCTION_INVOCATION_FAILED) with pocket host

I have a sveltekit project, that is perfecly rnning on my local machine. I use PocketBase as my DB, which is hosted on pockethost. The Pockethost domain is saved in a .env file locally  and I have  set the vercel env settings properly. As soon as vercel has built the project, I see the following Error: FUNCTION_INVOCATION_FAILED. The logs say, that they cannot GET /
Of course I have googled and tried to resolve the issue for example by temporary deleting the images from  the static folder. Bt that didn't help.
I have no Idea, what the Problem is. Does somebody have any ideas?

Can you paste a screenshot of the exact network log showing the error?


Issues Using CUDA with Face Recognition on Jetson Nano

System Information

face_recognition version: 1.3.0
Python version: 3.6.9 (JetPack Pre-installed Version)
Operating System: Ubuntu 18.04 (Jetpack 4.6)

Description
Hi all,
For the past week or so, I have been trying to get Face Recognition and Dlib to work with CUDA on the Jetson Nano 4GB. I have attempted multiple installation combinations of Dlib and the Face Recognition library, but none have succeeded in enabling me to use the "cnn" model with the face_locations() function (each failing with different kinds of errors).
Note: In each of the below cases, any problem was exhibited regardless of the image loaded into the face_locations() function. Where Dlib was built from source, the Dlib compilation process always reported that "DLIB WILL USE CUDA". Installations of Dlib that could be successfully imported into Python always returned True and 1 when "dlib.DLIB_USE_CUDA" and "print(dlib.cuda.get_num_devices())" were entered into Python respectively.
Installation Process
Originally, I attempted to install Dlib version 19.22.1 via "pip3 install dlib" (the latest version at the time prior to the release of Dlib version 19.23). I didn't think that I needed to implement the fix in Dlib for Jetson Nano outlined in the "Jetson Nano installation instructions" article in the README, as the problem mentioned in the article had supposedly since been fixed in a past cuDNN/JetPack SDK update. The library downloaded successfully, but attempting to import the library was met with "Segmentation fault (core dumped)". Research suggested that I try downgrading the library to version 19.21.1 and, on doing so (using pip), was able to import the library without issue and use it with face_recognition.
I then tried to use the "cnn" model with the face_locations() function in a simple program to detect the position of a face in an image. Each time I ran the program, the GPU showed 0% usage, and it would either freeze the computer before failing with "Killed" in the terminal (usually after a few minutes), or completely freeze up the entire system, forcing me to perform a hard restart of the computer. Using other face_recognition functions, such as face_encodings() and compare_faces() (for facial recognition), or face_locations() with the default HOG-based model worked without error.
With the release of Dlib 19.23, I uninstalled Dlib 19.21.1 and tried installing Dlib 19.23 using pip, but was also met with "Segmentation fault (core dumped)" on import into Python, as with Dlib 19.22.1. To rule out not building Dlib from source as being an issue, I uninstalled 19.23 and built from source the previously working Dlib 19.21 release (without applying the old cuDNN "forward_algo = forward_best_algo" fix), but the "cnn" model still failed to run.
I then attempted to build 19.23 using NumPy 1.19.4 (instead of version 1.19.5 that was previously installed on my system and used for the above few Dlib installations) and exporting the "OPENBLAS_CORETYPE=ARMV8" environmental variable into the Terminal (suggestions from the internet to fix the "Segmentation fault" on import issue), with no success.
My current installation now consists of a built from source version of Dlib 19.21 (using NumPy 1.19.4), following the instructions to comment out "forward_algo = forward_best_algo" before compiling the package. On running the "cnn" model with face_locations(), the GPU, for the first time, showed GPU usage (99%), before the program crashed 15-20 seconds later with the following error:

Click the arrow to view the full Python Terminal crash output.

Traceback (most recent call last):
  File "face-recog-test.py", line 36, in <module>
    face_locations = face_recognition.face_locations(image, number_of_times_to_upsample=0, model="cnn")
  File "/usr/local/lib/python3.6/dist-packages/face_recognition/api.py", line 119, in face_locations
    return [_trim_css_to_bounds(_rect_to_css(face.rect), img.shape) for face in _raw_face_locations(img, number_of_times_to_upsample, "cnn")]
  File "/usr/local/lib/python3.6/dist-packages/face_recognition/api.py", line 103, in _raw_face_locations
    return cnn_face_detector(img, number_of_times_to_upsample)
RuntimeError: Error while calling cudnnFindConvolutionBackwardDataAlgorithm( context(), (const cudnnFilterDescriptor_t)filter_handle, descriptor(dest_desc), (const cudnnConvolutionDescriptor_t)conv_handle, descriptor(data), num_possilbe_algorithms, &num_algorithms, perf_results.data()) in file /home/dev/dlib-19.21/dlib/cuda/cudnn_dlibapi.cpp:856. code: 4, reason: A call to cuDNN failed
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated
cudaStreamDestroy() failed. Reason: the launch timed out and was terminated
cudaFree() failed. Reason: the launch timed out and was terminated
cudaFreeHost() failed. Reason: the launch timed out and was terminated

If anyone can provide me with some advice on how to proceed, it would be greatly appreciated.
Thank you

It's little bit late but if you still have problem, try this way:
wget http://dlib.net/files/dlib-19.23.tar.bz2
tar jxvf dlib-19.23.tar.bz2
cd dlib-19.23/
mkdir build
cd build/
cmake ..
cmake --build .
cd ../
sudo python3 setup.py install
sudo pip3 install face_recognition

With jtop command you can see if GPU is in use
sudo pip3 install jetson-stats
or better:
python3
import dlib
print(dlib.DLIB_USE_CUDA)

and check if output is True
Good luck!

import dlib
Illegal instruction (core dumped)
jetson@jetson4g:~/face_recognition/dlib-19.23$

Same issue here. Have you found the fix?

It's little bit late but if you still have problem, try this way:
wget http://dlib.net/files/dlib-19.23.tar.bz2
tar jxvf dlib-19.23.tar.bz2
cd dlib-19.23/
mkdir build
cd build/
cmake ..
cmake --build .
cd ../
sudo python3 setup.py install
sudo pip3 install face_recognition

With jtop command you can see if GPU is in use sudo pip3 install jetson-stats  or better:
python3
import dlib
print(dlib.DLIB_USE_CUDA)

and check if output is True
Good luck!

I followed the compilation steps, and when I type "print(dlib.DLIB_USE_CUDA)", the response is "TRUE." However, when I attempt to run the code, I receive a "Segmentation fault (core dumped)" error.
I followed Paul's steps, and everything worked, but the frames per second (fps) were low, and it wasn't using the GPU. The version of dlib was 19.17. When I tried the more recent versions like 19.24, 19.23, 19.21, I encountered the same "Segmentation fault (core dumped)" message.
Paul:
https://www.youtube.com/watch?v=yOdVnQuhfeI&list=PLGs0VKk2DiYxP-ElZ7-QXIERFFPkOuP4_&index=38
Nvidia forum
https://forums.developer.nvidia.com/t/simple-accelerated-face-recognition/142679/19
I'm using numpy 1.19.4

I have different error when I used face_recognition
Load Error: Error while calling cudaOccupancyMaxPotentialBlockSize(&num_blocks,&num_threads,K) in file /root/pkgs/dlib/dlib/cuda/cuda_utils.h:164. code: 222, reason: the provided PTX was compiled with an unsupported toolchain

I have different error when I used face_recognition Load Error: Error while calling cudaOccupancyMaxPotentialBlockSize(&num_blocks,&num_threads,K) in file /root/pkgs/dlib/dlib/cuda/cuda_utils.h:164. code: 222, reason: the provided PTX was compiled with an unsupported toolchain

Me too. Have you solved it


Wippersnapper preprocessor script for printing the library versions to boot outtxt

@brentru this is tied in with https://github.com/adafruit/Adafruit_Wippersnapper_Arduino/pull/607
It adds a new flag to allow specifying the location of the header file to be generated/replaced --include_print_dependencies_header although now I've settled on not being able to modify the build flags I could probably pick a better name as it no longer adds an extra include to the build flags.

@brentru this is ready for re-review. Hopefully this is resolved satisfactorily, I've acted on the great suggestions and added some context for the os.system change (use "show resolved")


Rename?

Here's a list of some pg tools:

pg_dump
pg_restore
pg_stat_activity
pg_ctl
pg_amcheck
pg_basebackup
pg_verifybackup
pg_config
pg_isready

Notice how they all use "_" instead of "-" in the name. This tool should probably do the same.
I can do all the renaming and fixing links, just need a +1.

Done.


dashboard viewer react component

just like embed html, but for React
ability to add a dashboard viewer to a react app. It's possible now, but we can make it easier by preparing custom component.
sample code (just for general overview):
import DashboardViewer from 'keen-dashboard-builder/lib/viewer/component';

const App123 = props => {
  return (
    <DashboardViewer
       projectId='123'
       accessKey='000'
    />
  );
}

How is it possible to do this with the above sample code?  I'm trying to incorporate a DashboardViewer into a sample react app, but am not having any luck.  I'm also using TypeScript, so a typings file would also be most helpful.

react component hasn't been released yet but you can try with https://jsfiddle.net/s8r7mt6x/
support for typescript is in our backlog and will be added in the future

react component has been released -> https://github.com/keen/react-public-dashboard


Fix issue #17801, crash on double-tap under TalkBack on Android

The _controller field of TextField is null, if the app creates its own controller, resulting in a crash in return new Sematics() onTap() callack. It should use instead _effectiveController value. The crash prevents users under TalkBack on Android from showing soft keyboard after double-tap, as instructed by TalkBack.

I signed the Contributor License Agreement (CLA)!

Good find! Can you please add a test for this?

@goderbauer - adding test to Flutter build is beyond my skill set at this time. My total Flutter experience is about 2 weeks, I released a small app and could add tests within that app, but don't know how to build and test the entire Flutter...
The sample app that I submitted with issue #17801 could be used for such testing (crash reported when the app is run under TalkBack), but beyond that I'm completely lost, I'm sorry...
Greg

@gregko No worries. I'll add the test when I find some time.

I've taken over this PR in https://github.com/flutter/flutter/pull/17892 to add tests. Closing this one.

Thank you for taking care of it! Next time I have something to contribute, I'll take care of tests as well.


feat: add support for umami analytics

I added support for umami to my blog.
Umami is a self hosted analytics solution. I chose it because for some reason even Plausible self hosted was blocked by uBlock Origin. I figured I would offer to have the changes upstream as well.
Feel free to close this if it is not wanted.

This is great, thanks for the PR!

I added support for umami to my blog.
Umami is a self hosted analytics solution. I chose it because for some reason even Plausible self hosted was blocked by uBlock Origin. I figured I would offer to have the changes upstream as well.
Feel free to close this if it is not wanted.

Hello my umami is not working! I have replaced with us.umami.is on next.js file and added extra index.js and umami.js file on components still its not collecting any data


[Form] [labels doesn't work]

I'm using the form component for the login on my website, but sometimes the blue border of the input stops working, and the label overlaps the input and covers the content. How do I solve this issue? How can I make the label animation and the blue border when focusing on the input continue to work? Sometimes, when I reload the page, it stops working.

I finally figured out that all input forms should be initialized using initTE
Required ES init:
Input
*
* UMD autoinits are enabled by default. This means that you don't need to initialize the component manually. However if you are using Tailwind Elements ES format then you should pass the required components to the initTE method.


Custom header style interpolator

Currently we cannot configure header transition style so this PR is going to address this problem.
Developers can adding headerStyleInterpolator to StackNavigatorConfig to specify the header style interpolator

I think we should re-consider this approach. Instead of just adjusting the style/interpolators, I think it makes more sense to provide an entirely different header component. That way, people can customize the header more completely (for some header designs, it might not make sense to have a 'center' and 'right' interpolator)
Please re-open if you have a good argument for doing it this way. Otherwise, can you make a new PR for the alternate-header-component API?

I think this would be helpful to add. My particular situation has a title that is not center aligned on iOS, so being able to customize the transition to only include opacity is very helpful.
It's also unclear why #1293 was accepted, when conceptually this feels very similar.


Port-Forward shortcut dashboard

What would you like to be added:
Add a editable small dashboard on the cluster overview page were one can set favorites services for port-forwarding.

related: #2282, #2340, #2230, #542, #541

Sounds like an excellent extension idea.


[Pluging:Logging] Crash with json format

Using the logging plugin with json format results in IOError: not opened for reading while trying to serialize the Uploader object in the data hash passed to the _log_message_json function.  It looks like it also fails attempting to serialize the record object as well.  In both cases, it looks like the Uploader and record object class names (as opposed to the actual objects) are intended after comparing to the output of the :human and :heroku formats.
Thanks for an awesome gem!

@onomated Could you post here a minimal self-contained example that reproduces the crash? You can use the example in CONTRIBUTING.md for the template.

@onomated I managed to reproduce the bug, and pushed a fix. The problem was mainly in ActiveSupport overriding #to_json that the logging plugin uses, which had different behaviour than Ruby's JSON standard library.

@janko-m Awesome!  Thanks for the quick fix.  I'll do a better job of using the issue's template next time


zstd submodule updated to version 1.5.4

@foobargeez thanks for the update, but I just beat you to it with change 274acf6a767e921ba1580e01e40deae5f69f37f2.
One point for the next time -- just updating the zstd submodules isn't enough -- a couple of tests in 01_basic.t  need fixed .to update the version number test  - see my checking for the details.
#
# Compress::Stream::Zstd Version 0.204
# ZSTD_VERSION_NUMBER            [10](https://github.com/pmqs/Compress-Stream-Zstd/actions/runs/4147054955/jobs/7182645107#step:8:11)504
# ZSTD_VERSION_STRING            1.5.4
# ZSTD_MAX_CLEVEL                22
# ZSTD_MIN_CLEVEL                -[13](https://github.com/pmqs/Compress-Stream-Zstd/actions/runs/4147054955/jobs/7182645107#step:8:14)1072
#

#   Failed test at t/01_basic.t line 30.
#          got: '10504'
#     expected: '10502'

#   Failed test at t/01_basic.t line 31.
#          got: '1.5.4'
#     expected: '1.5.2'
# Looks like you failed 2 tests of [16](https://github.com/pmqs/Compress-Stream-Zstd/actions/runs/4147054955/jobs/7182645107#step:8:17).

thanks
Paul

Thanks @pmqs -- will make a note for next time.


[Finder] Name or service not known

i keep getting this error but how do i know which url causing this error ?
Scanning...
[*] Found: ***.tv
[*] Found: ***.com
[*] Found: ***.***.net
multiprocessing.pool.RemoteTraceback:
"""
Traceback (most recent call last):
  File "/usr/lib/python3.6/urllib/request.py", line 1318, in do_open
    encode_chunked=req.has_header('Transfer-encoding'))
  File "/usr/lib/python3.6/http/client.py", line 1254, in request
    self._send_request(method, url, body, headers, encode_chunked)
  File "/usr/lib/python3.6/http/client.py", line 1300, in _send_request
    self.endheaders(body, encode_chunked=encode_chunked)
  File "/usr/lib/python3.6/http/client.py", line 1249, in endheaders
    self._send_output(message_body, encode_chunked=encode_chunked)
  File "/usr/lib/python3.6/http/client.py", line 1036, in _send_output
    self.send(msg)
  File "/usr/lib/python3.6/http/client.py", line 974, in send
    self.connect()
  File "/usr/lib/python3.6/http/client.py", line 946, in connect
    (self.host,self.port), self.timeout, self.source_address)
  File "/usr/lib/python3.6/socket.py", line 704, in create_connection
    for res in getaddrinfo(host, port, 0, SOCK_STREAM):
  File "/usr/lib/python3.6/socket.py", line 745, in getaddrinfo
    for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -2] Name or service not known

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.6/multiprocessing/pool.py", line 119, in worker
    result = (True, func(*args, **kwds))
  File "/usr/lib/python3.6/multiprocessing/pool.py", line 44, in mapstar
    return list(map(*args))
  File "gitfinder.py", line 25, in findgitrepo
    with urlopen(''.join(['http://', domain, '/.git/HEAD']), timeout=5) as response:
  File "/usr/lib/python3.6/urllib/request.py", line 223, in urlopen
    return opener.open(url, data, timeout)
  File "/usr/lib/python3.6/urllib/request.py", line 526, in open
    response = self._open(req, data)
  File "/usr/lib/python3.6/urllib/request.py", line 544, in _open
    '_open', req)
  File "/usr/lib/python3.6/urllib/request.py", line 504, in _call_chain
    result = func(*args)
  File "/usr/lib/python3.6/urllib/request.py", line 1346, in http_open
    return self.do_open(http.client.HTTPConnection, req)
  File "/usr/lib/python3.6/urllib/request.py", line 1320, in do_open
    raise URLError(err)
urllib.error.URLError: <urlopen error [Errno -2] Name or service not known>
"""

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "gitfinder.py", line 84, in <module>
    main()
  File "gitfinder.py", line 80, in main
    pool.map(fun, domains)
  File "/usr/lib/python3.6/multiprocessing/pool.py", line 266, in map
    return self._map_async(func, iterable, mapstar, chunksize).get()
  File "/usr/lib/python3.6/multiprocessing/pool.py", line 644, in get
    raise self._value
urllib.error.URLError: <urlopen error [Errno -2] Name or service not known>

Did you check your list of domains? My guess would be that there are some expired, non-existent or invalid domains in the list, as the error comes from the socket.getaddrinfo function?
How many nameservers have you configured? Maybe you ran into a rate limiting issue or so?


[WIP] Make the UI responsive on all devices/resolutions

NOT MERGE THIS FOR THE MOMENT
This is the changes at the moment:

Portairt mode only is supported atm, for phones and tablet
Moved the main toolbar on top-left side of the screen
Made a little trick to make the icons added to the map responsive at 100%
Removed complety the scrollbar

Here some screens: http://imgur.com/a/KZFFi

Are you goiing to reopen it, it looked to be nice work based on the screenshots


VST3 version not recognized in Cubase or Reaper on Mac M1pro

I've tried with Cubase 12 (M1 native), Cubase 11 (Rosetta 2) and Reaper, not showing up at all. AU version works.

Hi!
Can you confirm for me where the VST3 is installed on your Mac? And that that location is being scanned for plugins by Cubase?

Hi, I have it installed in:
Library/Audio/Plug-Ins/VST3
That's where the installer put it, with the rest of my plugins. Cubase is definitely scanning there but it's not even showing up in the blocklist or anything, it's just not finding it at all.
Clearing plugin cache and re-scanning in Reaper and Kushview Element got the VST3 to show up in those, but when inserting it both apps crash.
Hope this helps, and big thanks for the awesome work on this!

It does help. What would be most helpful would be a dump from a version of them plugin with debugging symbols.
If you don't know how to do that we can try and make do in the meantime. Is this version 0.5.7 that's not working? Does 0.5.6 work?

Neither 0.5.7 or 0.5.6 work or appear in Cubase. 0.5.7 does appear in
Reaper but crashes on load, I can send the MacOS crash log if that will
help but I don't know how to get anything more than that.
On Tue, Dec 20, 2022 at 2:00 PM Steven Atkinson @.***>
wrote:

It does help. What would be most helpful would be a dump from a version of
them plugin with debugging symbols.
If you don't know how to do that we can try and make do in the meantime.
Is this version 0.5.7 that's not working? Does 0.5.6 work?
—
Reply to this email directly, view it on GitHub
https://github.com/sdatkinson/NeuralAmpModelerPlugin/issues/17#issuecomment-1360017154,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A3JC4TJT7UTGNAMFLNP5SPLWOH65RANCNFSM6AAAAAATC6GYII
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
-Andreas

I had a look and it's currently quite a mystery why the VST3 is not showing up in Steinberg hosts to me

I tried on an intel mac

I had a look and it's currently quite a mystery why the VST3 is not showing up in Steinberg hosts to me

Whew, glad to hear at least it wasn't an obvious error 😅 appreciate you checking, @olilarkin!
Is there any reason this wouldn't be consistent across all versions of Cubase? If not, I've got an old version of LE I might be able to install and use to troubleshoot.

For me, it was also not showing up in VST3 test host that comes in the Sdk
zip
On Fri, 30 Dec 2022 at 02:27, Steven Atkinson @.***>
wrote:

I had a look and it's currently quite a mystery why the VST3 is not
showing up in Steinberg hosts to me
Whew, glad to hear at least it wasn't an obvious error 😅 appreciate you
checking, @olilarkin https://github.com/olilarkin!
Is there any reason this wouldn't be consistent across all versions of
Cubase? If not, I've got an old version of LE I might be able to install
and use to troubleshoot.
—
Reply to this email directly, view it on GitHub
https://github.com/sdatkinson/NeuralAmpModelerPlugin/issues/17#issuecomment-1367675256,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFACLTMVOU6HXJT3TUHNITWPY3BVANCNFSM6AAAAAATC6GYII
.
You are receiving this because you were mentioned.Message ID:
@.***>

VST not appearing on Cubase Elements 10 on Windows 11 also.

Confirming that the vst3 does not appear on Cubase Pro 12, Windows 10 nor Windows 11

Steinberg's VST3 sdk comes with a validator cli tool and you can also run unit tests in the VST3PluginTestHost (both fail). There are some bugs in the buffer allocating code (@sdatkinson which is a bit nasty imo !) making these changes allows the plugin to pass the validation (note commenting out the meter),  there is still an error todo with tail processing from the unit tests in VST3PluginTestHost
NeuralAmpModelerPlugin-08-38-23.patch

This is really helpful. The buffer code is...not my cleanest work haha.
Yeah, that sounds like a reasonable place to dig in, and also squares with my observation that LSTM models (which don't subclass the buffer class) seem to behave better.

Well, I think I've found a possible explanation why the plugin didn't show up in the VST3PluginTestHost: The VST3_SUBCATEGORY was defined as "Effect"; switching this to "Fx" made it show up, and switching it back to "Effect" made it disappear again...so I think that's it (and possibly why the plugin doesn't show up in Cubase as well???)
Just merged in #54 with this fix among others (I discovered the missing InitBool independently thanks to the SDK unit tests--guessing @olilarkin you found it like that as well!. I didn't see the fills since _ProcessInput() is called immediately after and fills in those arrays...but I'll probably jump back and put that one in quick just to be thorough!)
At any rate, a92fe974f04ef41fffd2b322d9675f5e83373967 (current commit on main as of my writing this) may resolve this issue thanks to the "Fx" subcategory change; if someone can check and report back then that'd be swell 😄

Not sure why your latest version didn't publish release artifacts on github. I just built locally and the VST3_SUBCATEGORY change seems to have fixed the problem with steinberg hosts. (Shows up in VST3TestHost and Cubase 12) 🥳

Not sure why your latest version didn't publish release artifacts on github.

I hadn't clicked "publish" yet. I was doing some final testing before going live 🙂

I just built locally and the VST3_SUBCATEGORY change seems to have fixed the problem with steinberg hosts. (Shows up in VST3TestHost and Cubase 12) 🥳

Great! Marking this as resolved then


Need to determine the base type of a complex element

First off -- thank you, this library is awesome!
I would like to be able to figure out what the base type of a complex element is, so I came up with this hack that monkeypatches an extends_type property onto XsdComplexType.
from xmlschema.components.xsdbase import get_xsd_attribute, get_xsd_component
from xmlschema.components.elements import XsdComplexType
from xmlschema.qnames import split_reference

def _extends_type(self):
    '''Hack on an 'extends_type' property to XsdComplexType'''
    if not self.has_extension():
        return None
    content_spec = get_xsd_component(self.content_type.elem)
    content_base = get_xsd_attribute(content_spec, 'base')
    base_qname, namespace = split_reference(content_base, self.schema.namespaces)
    return self.schema.maps.lookup_type(base_qname)

XsdComplexType.extends_type = property(fget=_extends_type)

Most of this logic is taken directly from factories.py ... seems to work, but not 100% sure of the best way this could be integrated into the existing library.

After a clash with circularity issues I decided to try the merge of factories code into XsdComponent's subclasses. This can be done defining a _parse method, that is called whenever self.elem is set, each component is built once and with lesser complications. Also parsing errors can simply be collected by the component, raising at the end if the validation mode is 'strict'.
This could be the _parse() method for XsdUnion, that take the code of xsd_union_factory():
def _parse(self):
    elem = self.elem
    schema = self.schema
    options = self.options
    member_types = []

    for child in iter_xsd_declarations(elem):
        mt = xsd_simple_type_factory(child, schema, **options)
        if isinstance(mt, XMLSchemaParseError):
            self.errors.append(mt)
        else:
            member_types.append(mt)

    if 'memberTypes' in elem.attrib:
        for name in elem.attrib['memberTypes'].split():
            type_qname = split_reference(name, schema.namespaces)[0]
            mt = schema.maps.lookup_type(type_qname, **options)
            if isinstance(mt, XMLSchemaParseError):
                self.errors.append(mt)
            elif not isinstance(mt, XsdSimpleType):
                self.errors.append(XMLSchemaParseError("a simpleType required", mt))
            else:
                member_types.append(mt)

    if not member_types:
        self.errors.append(XMLSchemaParseError("missing union type declarations", self))

    self.member_types = member_types

Still some of work for this but I'm quite confident that's will be a good choice.
If you want to take a look at the development code I've pushed an 'altdev' branch into the repo.
In the development code I introduced also a XMLSchemaValidator base class (validator.py) for checking parsed components and schemas, that is based on XML Schema validation modes ('strict', 'lax', 'skip'). This ought resolve some validation options and define the library behaviour for each situation.

Factories code now is into class methods (version 0.9.10, just published). Seems to be a better choice for building and rebuilding XSD components. The components class hierarchy has been changed, in order to unify all XML Schema information items with the common base class XsdBaseComponent (module xmlschema/xsdbase).
In the same module the XMLSchemaValidator class has been replaced by a ValidatorMixin.
I wait observations about this or if you are satisfied please close the ticket.
Thanks

I'll play with it at some point in the next week and get back to you.


Capitalized scheme throws

Not sure if it's a valid issue, but
bitcoin:1BgGZ9tcN4rm9KBzDn7KprQz87SZ26SAMH?amount=20.3&label=Foobar decodes fine while BITCOIN:1BgGZ9tcN4rm9KBzDn7KprQz87SZ26SAMH?amount=20.3&label=Foobar throws Invalid BIP21 URI

The scheme component ("bitcoin:") is case-insensitive, and implementations must accept any combination of uppercase and lowercase letters. The rest of the URI is case-sensitive, including the query parameter keys.

That is a bug.

Fixed in #12 v2.0.3


The getPinName() routine is absent

According to the documentation to the 0.6.1 release (http://iotdk.intel.com/docs/master/mraa/namespacemraa.html#aa436b58bf20a87909c7344bf58d42706), but the compiler says:
"aio.c: In function ‘int main()’:
aio.c:6:38: error: ‘getPinName’ is not a member of ‘mraa’"

What version of mraa do you have installed?
opkg info libmraa0

More importantly this is not a feature of v0.6.1 but is a feature for
upcoming releases:
http://iotdk.intel.com/docs/mraa/v0.6.1/namespacemraa.html#aa436b58bf20a87909c7344bf58d42706
You need to use master from intelgalactic-dev to get that function.
On 7 April 2015 at 11:04, Tom Ingleby<EMAIL_ADDRESS>wrote:

What version of mraa do you have installed?
opkg info libmraa0
—
Reply to this email directly or view it on GitHub
https://github.com/intel-iot-devkit/mraa/issues/183#issuecomment-90494284
.

--
Brendan Le Foll
http://www.madeo.co.uk

Sorry, guys, it's my fault. I've looked into the wrong doc page. Thanks for help.


need to fix prometheus yml config

It wont work following your guide.
The poller doesnt know about the /metrics. So you need to add the metrics path into the prometheus.yml.
Like below:
- job_name: 'unifipoller'
    scrape_interval: 30s
    static_configs:
    - targets: ['localhost:9130']
    metrics_path: /metrics

What error did you get without that setting?
The docs indicate /metrics is the default path when one is not provided. It should work without that setting. Perhaps you've changed something else to make this not work with the defaults?
Docs: https://prometheus.io/docs/introduction/first_steps/#configuring-prometheus

Prometheus expects metrics to be available on targets on a path of /metrics.

The docs say /scrape in https://unifipoller.com/docs/dependencies/prometheus#prometheus-configuration-for-urls which is what might have lead to this issue. Just guessing though :)


Change Connection API to be synchronous

The execute query functions will look like this:
   /// Execute a query.
   ///
   /// - Parameter query: The query to execute.
   /// - Returns: An instance of QueryResult representing the result of the query execution.
  func execute(query: Query) -> QueryResult

Transaction related functions will be changed in the same way:
    /// Start a transaction.
    ///
    /// - Returns:  An instance of QueryResult representing the result of the execution of start transaction command.
    func startTransaction() -> QueryResult

We can also throw errors instead of returning them inside QueryResult.

ResultFetcher will be synchronous only, i.e.
    /// Fetch the next row of the query result. This function is non-blocking.
    ///
    /// - Parameter callback: A callback to call when the next row of the query result is ready.
    func fetchNext(callback: ([Any?]?) ->())

will be removed.

@shmuelk mentioned you were thinking about making Kuery functions throw instead of returning QueryResult.error(). IMO, that would be better.
Also, if we were to do that, I think it would be worth considering moving rows and titles from ResultSet into QueryResult as optionals and removing ResultSet entirely. Then QueryResult could be as simple as:
public class QueryResult {
    private let resultFetcher: ResultFetcher?

    // number of rows affected by a INSERT/UPDATE/DELETE or
    // number of rows returned by a SELECT (may be -1 if we fetch the result set iteratively)
    public let affectedRows: Int
    public let columnNames: [String]?
    public let resultSet: RowSequence?
    public lazy var rows: [[String: Any?]]? = {
        ...
    }()
}

What do you think?

OK, we can do this.
@shmuelk proposed to use numberOfAffectedRows instead of affectedRows, titles instead of columnNames (because these don't have to be table columns), and rowSequence instead of resultSet.

@irar2 Hello :),
Is it possible to know when the synchronous api will be released?

Hi @irar2,
Having the syncronous API will be great!
Thank you in advance

@irar2 I was reading at the implementation of the MySQL plugin and I didn't find asynchronous call to the database, so actually I was wondering why do you decide to use completion handler instead of simple return and catch ?

@shmuelk Would be amazing to have a synchronous API

This item will be addressed by https://github.com/IBM-Swift/Swift-Kuery/pull/152

We no longer plan on addressing this via the changes related to PR #152.
We will however look at providing a utility function to wrap the asynchronous API which will allow synchronous usage of the SwiftKuery API.


Add schema url to an id field

Right now, a schema instance has a version number, but it's not possible to retrace which schema it was generated from. One resolution is to also include the url of the schema to a top level id field.

describedBy has been added to schemas


[Enhancement] Add Skeleton Screen Effect while Loading Blog

The current effect of loading blog may let user confuse what will load, we can add the skeleton screen effect to improve the user experience
Current Screenshots

Reference

https://mui.com/material-ui/react-skeleton/
https://www.npmjs.com/package/react-loading-skeletons
https://www.smashingmagazine.com/2020/04/skeleton-screens-react/
https://blog.logrocket.com/build-skeleton-screen-css/

Follow this tutorial: https://www.youtube.com/watch?v=g74Q0wRc6BQ, Maybe we have to refactor the blog post at first.

https://nextjs.org/docs/app/building-your-application/routing/loading-ui-and-streaming

hey @1chooo
i can add skeleton loader or screen for your site, so whenever data is loading we can display the skeleton.

hey @1chooo i can add skeleton loader or screen for your site, so whenever data is loading we can display the skeleton.

@mu-irfan really appreciate!! I’ll attach the details later.


Pilot fails with {"code"=>"Enter a demo account user name, or deselect since update from 2.72.0 > 2.78.0

Issue Description
Since I updated to fastlane 2.78  I get the error above and my CI build fails. But the app is uploaded. The error is triggered during distributing the build to testers.
Complete output when running fastlane, including the stack trace and command used
[07:48:55]: Distributing new build to testers: 0.20.0 - 3600
[07:49:10]: Sending crash report...
[07:49:10]: The stack trace is sanitized so no personal information is sent.
[07:49:10]: To see what we are sending, look here: /Users/vagrant/.fastlane/latest_crash.json
[07:49:10]: Learn more at https://docs.fastlane.tools/actions/opt_out_crash_reporting/
[07:49:10]: You can disable crash reporting by adding `opt_out_crash_reporting` at the top of your Fastfile
[07:49:10]: -------------------
[07:49:10]: --- Step: slack ---
[07:49:10]: -------------------
[07:49:10]: Successfully sent Slack notification
[07:49:10]: {"code"=>"Enter a demo account user name, or deselect \"A demo account is required to use all the features of the app.\"", "description"=>"Failed to submit build for review."}
+------+----------------------------+-------------+
|                fastlane summary                 |
+------+----------------------------+-------------+
| Step | Action                     | Time (in s) |
+------+----------------------------+-------------+
| 1    | Verifying fastlane version | 0           |
| 2    | default_platform           | 0           |
| 3    | cocoapods                  | 70          |
| 4    | get_version_number         | 6           |
| 5    | Switch to ios test lane    | 0           |
| 6    | scan                       | 511         |
| 7    | danger                     | 1           |
| 8    | increment_version_number   | 1           |
| 9    | increment_build_number     | 2           |
| 10   | read_changelog             | 0           |
| 11   | gym                        | 844         |
| 12   | set_github_release         | 0           |
| 13   | crashlytics                | 54          |
| 💥   | pilot                      | 1748        |
| 15   | slack                      | 0           |
+------+----------------------------+-------------+
[07:49:10]: fastlane finished with errors
Looking for related GitHub issues on fastlane/fastlane...
Found no similar issues. To create a new issue, please visit:
https://github.com/fastlane/fastlane/issues/new
Run `fastlane env` to append the fastlane environment to your issue
bundler: failed to load command: fastlane (/usr/local/bin/fastlane)
Spaceship::UnexpectedResponse: [!] {"code"=>"Enter a demo account user name, or deselect \"A demo account is required to use all the features of the app.\"", "description"=>"Failed to submit build for review."}
  /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.78.0/spaceship/lib/spaceship/test_flight/client.rb:290:in `handle_response'
  /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.78.0/spaceship/lib/spaceship/test_flight/client.rb:72:in `post_for_testflight_review'
  /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.78.0/spaceship/lib/spaceship/test_flight/build.rb:204:in `submit_for_testflight_review!'
  /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.78.0/pilot/lib/pilot/build_manager.rb:149:in `distribute_build'
  /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.78.0/pilot/lib/pilot/build_manager.rb:88:in `distribute'
  /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.78.0/pilot/lib/pilot/build_manager.rb:52:in `upload'
  /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.78.0/fastlane/lib/fastlane/actions/upload_to_testflight.rb:16:in `run'
  /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.78.0/fastlane/lib/fastlane/runner.rb:253:in `block (2 levels) in execute_action'
  /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.78.0/fastlane/lib/fastlane/actions/actions_helper.rb:50:in `execute_action'
  /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.78.0/fastlane/lib/fastlane/runner.rb:231:in `block in execute_action'
  /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.78.0/fastlane/lib/fastlane/runner.rb:227:in `chdir'
  /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.78.0/fastlane/lib/fastlane/runner.rb:227:in `execute_action'
  /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.78.0/fastlane/lib/fastlane/runner.rb:148:in `trigger_action_by_name'
  /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.78.0/fastlane/lib/fastlane/fast_file.rb:148:in `method_missing'
  Fastfile:180:in `block (2 levels) in parsing_binding'
  /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.78.0/fastlane/lib/fastlane/lane.rb:33:in `call'
  /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.78.0/fastlane/lib/fastlane/runner.rb:49:in `block in execute'
  /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.78.0/fastlane/lib/fastlane/runner.rb:45:in `chdir'
  /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.78.0/fastlane/lib/fastlane/runner.rb:45:in `execute'
  /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.78.0/fastlane/lib/fastlane/lane_manager.rb:56:in `cruise_lane'
  /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.78.0/fastlane/lib/fastlane/command_line_handler.rb:36:in `handle'
  /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.78.0/fastlane/lib/fastlane/commands_generator.rb:108:in `block (2 levels) in run'
  /usr/local/lib/ruby/gems/2.4.0/gems/commander-fastlane-4.4.5/lib/commander/command.rb:178:in `call'
  /usr/local/lib/ruby/gems/2.4.0/gems/commander-fastlane-4.4.5/lib/commander/command.rb:153:in `run'
  /usr/local/lib/ruby/gems/2.4.0/gems/commander-fastlane-4.4.5/lib/commander/runner.rb:476:in `run_active_command'
  /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.78.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:75:in `run!'
  /usr/local/lib/ruby/gems/2.4.0/gems/commander-fastlane-4.4.5/lib/commander/delegates.rb:15:in `run!'
  /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.78.0/fastlane/lib/fastlane/commands_generator.rb:337:in `run'
  /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.78.0/fastlane/lib/fastlane/commands_generator.rb:42:in `start'
  /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.78.0/fastlane/lib/fastlane/cli_tools_distributor.rb:98:in `take_off'
  /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.78.0/bin/fastlane:20:in `<top (required)>'
  /usr/local/bin/fastlane:23:in `load'
  /usr/local/bin/fastlane:23:in `<top (required)>'

Environment

✅ fastlane environment ✅
Stack

Key
Value

OS
10.13.2

Ruby
2.4.2

Bundler?
true

Git
git version 2.15.1

Installation Source
~/.gem/bin/fastlane

Host
Mac OS X 10.13.2 (17C205)

Ruby Lib Dir
/usr/local/Cellar/ruby/2.4.2_1/lib

OpenSSL Version
OpenSSL 1.0.2l  25 May 2017

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
9.2

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
# Fastlane Documentation:
# https://github.com/fastlane/fastlane/tree/master/fastlane/docs
#
# Fastlane actions:
# https://docs.fastlane.tools/actions/
#
# Bitrise with fastlane example:
# https://github.com/bitrise-samples/fastlane/blob/master/BitriseFastlaneSample/fastlane/Fastfile
#
# AUTHENTICATION
# https://docs.fastlane.tools/best-practices/continuous-integration/
# https://github.com/fastlane/fastlane/tree/master/spaceship
#
# Change the syntax highlighting to Ruby
# All lines starting with a # are ignored when running `fastlane`
#
#
# This file was created by the help of https://gist.github.com/ulhas/e8e529d08849b8cda947
#
#
# NOTE: To use faslane first do:
#           gem install bundler && bundle install
#
#       and then run:
#           bundle exec fastlane release product_name:Gasoline version:"1.0.0" github_account:"blackjacx"
#           bundle exec fastlane test product_name:Gasoline
#
# Configure the following environment variables for your project
# on your CI and in fastlane/.env:
#
# ENV["GITHUB_TOKEN"] = "..."
# ENV["SLACK_URL"] = "..."
# ENV["BITRISE_DEPLOY_DIR"] = "..."
# ENV['CRASHLYTICS_API_TOKEN'] = "..."
# ENV['CRASHLYTICS_BUILD_SECRET'] = "..."
# ENV['FASTLANE_USER'] = "..."
# ENV['FASTLANE_PASSWORD'] = "..."
# ENV['FASTLANE_DONT_STORE_PASSWORD'] = "..."

# TODO: deploy to TestFlight, Crashlytics, Hockey, ... & move away from Bitrise

# This is the minimum version number required.
# Update this, if you use features of a newer version.
fastlane_version "2.55.0"

default_platform :ios

platform :ios do

  before_all do
    cocoapods(use_bundle_exec: true, repo_update: true)
  end

  after_all do
    # This is called, only if the executed lane was successful
    slack(success: true, message: "*Successfully Built App 🎉*")
  end

  error do |lane, exception|
    # This block is called, only if the executed lane failed
    slack(success: false, message: "*#{lane} failed with #{exception.message}*")
  end

  ##############################################################################
  # Playground Lane
  ##############################################################################

  lane :playground do |options|
    stamp_changelog(
      section_identifier: version, # Stamp Unreleased section with newly released build number
      placeholder_line: "* Your contribution here."
    )
  end

  ##############################################################################
  # Preparing Release
  ##############################################################################

  lane :prepare_release do |options|

    raise "No product_name provided!".red unless options[:product_name]
    raise "No version provided!".red unless options[:version]

    product_name = options[:product_name]
    version = options[:version]

    ensure_git_status_clean
    ensure_git_branch(branch: "develop")

    increment_version_number(
      version_number: version
    )

    stamp_changelog(
      section_identifier: version, # Stamp Unreleased section with newly released build number
      placeholder_line: "* Your contribution here."
    )
  end

  ##############################################################################
  # Release Lane
  ##############################################################################

  desc "Releases a new product version"
  lane :release do |options|

    possible_tester_groups = ["appstore", "beta", "nightly"]
    tester_groups = "#{options[:tester_groups]}"

    raise "No product_name provided!".red unless options[:product_name]
    raise "No build provided!".red unless options[:build]
    raise "No github_account provided!".red unless options[:github_account]
    raise "No tester groups provided! Provide at least one of the following as ruby array: #{possible_tester_groups}".red if options[:tester_groups].empty?

    product_name = options[:product_name]
    build = options[:build]
    github_account = options[:github_account]
    project = "#{product_name}.xcodeproj"
    workspace = "#{product_name}.xcworkspace"
    version = get_version_number(xcodeproj: "#{project}", target: "#{product_name}")
    deploy_dir = ENV["BITRISE_DEPLOY_DIR"]
    ipa_name = "#{product_name}.ipa"
    ipa_path = "#{deploy_dir}/#{product_name}.ipa"
    dsym_path = "#{deploy_dir}/#{product_name}.app.dSYM.zip"
    run_danger = options[:run_danger]
    tester_whatsnew = File.read("./metadata/whatsnew.txt")
    export_options_plist = "./fastlane/ExportOptions.plist"

    test(product_name: product_name, run_danger: run_danger)

    # Increments CFBundleVersion by one and sets CFBundleShortVersionString
    increment_version_number(version_number: version)
    increment_build_number(build_number: build)

    # read changelog
    changelog = read_changelog(
      section_identifier: "[#{version}]",
      excluded_markdown_elements: []
    )

    changelog_no_md = changelog
        .gsub(/\* \[(.+): /, '* ')
        .gsub(/ - (.+)\./, '')
        .gsub(/###/, '')
        .strip

    gym(
      workspace: workspace,
      scheme: product_name,
      buildlog_path: deploy_dir,
      output_directory: deploy_dir,
      output_name: ipa_name,
      export_options: export_options_plist,
      include_bitcode: true,
      include_symbols: true,
      clean: true
    )

    set_github_release(
      repository_name: "#{github_account}/#{product_name}",
      api_token: ENV["GITHUB_TOKEN"],
      name: version,
      tag_name: version,
      description: (changelog || "No changelog provided"),
      commitish: "master"
    )

    crashlytics(
      crashlytics_path: "./Pods/Crashlytics/iOS/Crashlytics.framework",
      groups: tester_groups,
      notes: changelog_no_md,
      notifications: false
    )

    pilot(
      changelog: changelog_no_md,
      ipa: "#{ipa_path}",
      groups: tester_groups,
      distribute_external: true
    )

    sh("ls -la #{deploy_dir}")
    puts tester_groups
  end

  ##############################################################################
  # Test Lane
  ##############################################################################

  desc "Runs tests optionally with danger"
  lane :test do |options|

    raise "No product_name provided!".red unless options[:product_name]

    product_name = options[:product_name]
    run_danger = options[:run_danger]

    # Easily run tests of your iOS app using scan
    scan(
      workspace: "#{product_name}.xcworkspace",
      scheme: product_name,
      clean: true,
      devices: ["iPhone 8"],
      skip_build: false,
      output_types: "html",
      skip_slack: true,
      output_directory: ENV["BITRISE_DEPLOY_DIR"]
    )

    # Runs danger for the project
    if run_danger
      danger(
        use_bundle_exec: true,
        github_api_token: ENV["GITHUB_TOKEN"],
        verbose: true
      )
    end
  end

  ##############################################################################
  # Manually Refreshing Crashlytics dSYM's
  ##############################################################################

  lane :refresh_dsyms do
    # This needs to be done after uploading a new app to ITC since Apple
    # recompiles the apps from bitcode hich results in new dSYM's.
    # NOTE: upload_symbols_to_crashlytics relies in the installed Fabric.app
    # https://github.com/fastlane/fastlane/issues/10255
    # https://krausefx.com/blog/download-dsym-symbolication-files-from-itunes-connect-for-bitcode-ios-apps
    # https://docs.fabric.io/apple/crashlytics/missing-dsyms.html#upload-symbols-script
    user = ENV["FASTLANE_USER"]
    app_id = CredentialsManager::AppfileConfig.try_fetch_value(:app_identifier)

    download_dsyms(username: user, app_identifier: app_id)
    upload_symbols_to_crashlytics
  end
end

`./fastlane/Appfile`
app_identifier "com.ioki.passenger" # The bundle identifier of your app

team_id "P4LECE5B35" # Developer Portal Team ID
itc_team_id "118614410" # ID identifying the team Deutsche Bahn AG

# you can even provide different app identifiers, Apple IDs and team names per lane:
# More information: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Appfile.md

fastlane gems

Gem
Version
Update-Status

fastlane
2.78.0
✅ Up-To-Date

Loaded fastlane plugins:

Plugin
Version
Update-Status

fastlane-plugin-changelog
0.9.0
✅ Up-To-Date

Loaded gems

Gem
Version

did_you_mean
1.1.0

bundler
1.16.0

io-console
0.4.6

rake
12.3.0

CFPropertyList
2.3.6

concurrent-ruby
1.0.5

i18n
0.9.3

minitest
5.11.1

thread_safe
0.3.6

tzinfo
1.2.4

activesupport
4.2.10

public_suffix
2.0.5

addressable
2.5.2

babosa
1.0.2

claide
1.0.2

colored2
3.1.2

cork
0.3.0

nap
1.1.0

open4
1.3.4

claide-plugins
0.9.2

fuzzy_match
2.0.4

cocoapods-core
1.4.0

cocoapods-deintegrate
1.0.2

cocoapods-downloader
1.1.3

cocoapods-plugins
1.0.0

cocoapods-search
1.0.0

cocoapods-stats
1.0.0

netrc
0.11.0

cocoapods-trunk
1.3.0

cocoapods-try
1.1.0

escape
0.0.4

fourflusher
2.0.1

gh_inspector
1.0.3

molinillo
0.6.4

ruby-macho
1.1.0

nanaimo
0.2.3

xcodeproj
1.5.4

cocoapods
1.4.0

colored
1.2

highline
1.7.10

commander-fastlane
4.4.5

multipart-post
2.0.0

faraday
0.14.0

faraday-http-cache
1.3.1

git
1.3.0

kramdown
1.16.2

no_proxy_fix
0.1.2

sawyer
0.8.1

octokit
4.8.0

unicode-display_width
1.3.0

terminal-table
1.8.0

danger
5.5.6

danger-plugin-api
1.0.0

danger-changelog
0.2.1

danger-commit_lint
0.0.6

thor
0.20.0

danger-swiftlint
0.12.1

declarative
0.0.10

declarative-option
0.1.0

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20170404

dotenv
2.2.1

excon
0.60.0

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

faraday_middleware
0.12.2

fastimage
2.1.1

jwt
2.1.0

little-plugger
1.1.4

multi_json
1.13.1

logging
2.2.2

memoist
0.16.0

os
0.9.6

signet
0.8.1

googleauth
0.6.2

httpclient
2.8.3

mime-types-data
3.2016.0521

mime-types
3.1

uber
0.1.0

representable
3.0.4

retriable
3.1.1

google-api-client
0.13.6

json
2.1.0

mini_magick
4.5.1

multi_xml
0.6.0

plist
3.4.0

rubyzip
1.2.1

security
0.1.3

slack-notifier
2.3.2

terminal-notifier
1.8.0

tty-screen
0.6.4

tty-cursor
0.5.0

tty-spinner
0.8.0

word_wrap
1.0.0

rouge
2.0.7

xcpretty
0.2.8

xcpretty-travis-formatter
1.0.0

fastlane-plugin-changelog
0.9.0

generated on: 2018-01-23

Should be fixed with now with #11760 😊 Happy fastlaning 🚀


Index Settings Contributor sample

This sample works on Liferay Portal 7.1.x

@luanmaoski would you be willing to send me an informative Readme for this new sample? You can find instructions on how to do this here. Thanks!

Hi @codyhoag, you can find the README here.

@luanmaoski thanks! I'll make sure this gets in as official documentation once the sample is live.