Mug/Integration Setup: Config flow could not be loaded: 500 Internal Server Error Server got itself in trouble

Home Assistant Version (eg. 2023.2): 2023.2.5
Ember Mug Component Version (eg. 0.5.0): 0.5.0-beta-6 and 0.5.0-beta-9; 0.5.0-beta-5 is last working version.

Description
Attempting to pair/configure mug with HA following some changes to my Bluetooth adapter that were previously causing issues (added extension cable due to concerns over USB3 interference).
What I Did
Deleted integration for previously paired mug with connection issues prior to USB/Bluetooth changes.
Attempted to re-pair and reconfigure from discovered devices, and received the Config flow could not be loaded: 500 Internal Server Error Server got itself in trouble error when configuring the discovered integration for the mug.
The error is accompanied by an error in the HA log related to helpers/data_entry_flow.py:44 including a traceback that I have included below.
Using HACS, I re-downloaded each 0.5.0 beta version 5-9 trying each and found that 0.5.0-beta-5 works as anticipated for the integration/configure screen, but I receive the error for 0.5.0-beta-6 and onward (thru the most recent 0.5.0-beta-9 release).
Logs / Errors
Logger: aiohttp.server
Source: helpers/data_entry_flow.py:44
First occurred: 3:28:42 PM (1 occurrences)
Last logged: 3:28:42 PM
Error handling request

Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_protocol.py", line 435, in _handle_request
    resp = await request_handler(request)
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_app.py", line 504, in _handle
    resp = await handler(request)
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_middlewares.py", line 117, in impl
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 60, in security_filter_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 100, in forwarded_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 28, in request_context_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 80, in ban_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 236, in auth_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 145, in handle
    result = await result
  File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 171, in get
    return await super().get(request, flow_id)
  File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 100, in get
    result = self._prepare_result_json(result)
  File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 184, in _prepare_result_json
    return _prepare_config_flow_result_json(result, super()._prepare_result_json)
  File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 121, in _prepare_config_flow_result_json
    return prepare_result_json(result)
  File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 44, in _prepare_result_json
    data["data_schema"] = voluptuous_serialize.convert(
  File "/usr/local/lib/python3.10/site-packages/voluptuous_serialize/__init__.py", line 40, in convert
    pval = convert(value, custom_serializer=custom_serializer)
  File "/usr/local/lib/python3.10/site-packages/voluptuous_serialize/__init__.py", line 113, in convert
    if issubclass(schema, Enum):
TypeError: issubclass() arg 1 must be a class

Oh, sorry about that. I added a new option and it caused an issue. It should be fixed. I created a tenth beta.
If you are removing and re-adding a mug and it is not automatically re-discovered you might need to go into bluetoothctl and remove the previous one with `remove``then it shoudl pop up.

Thanks @sopelj !
0.5.0-beta-10 resolves the error I described, but the extra option appeared as a checkbox with no label in the config flow:

I did complete a restart of HA following redownload of 0.5.0-beta-10, but not sure if I reloaded the devices page before starting the config flow (if that would make a difference).
That said, the config flow did indeed work and my mug paired!
On my end the changes I made to the adapter setup seem to have improved connectivity as well. I had bluetoothctl open in a terminal, but didn't have to remove the mug first before entering & pairing. Your new read/write functionality also worked - I was able to update the name of the mug.
Thanks again for all your work on this project! If you feel like it, you should add a 'buymeacoffee' link or similar to the project page.

Awesome! I'm glad it works now!
You don't need to manually remove the device in order to re-add it, you just need to remove it to get the notification for autodiscovery. (However, sometime you can still get it after reboot)
That's really strange that you don't have the text. I wonder if the old one is still cached or something. I have the text for the new entry on mine. What language is your Home Assistant set to? Regardless it should fall back to the default keys.

I appreciate the suggestion, I might, but I'm just glad it can be of use.
Also, unrelated, but I see you have yours set to fahrenheit, so I was wondering, are your readings correct? A few have mentionned issues with fahrenheit. It should be fixed, but I haven't heard back about it yet from them yet.

I would wager that the label for that option was my fault for not reloading the HA UI in the browser tab.
On your question about temp readings in Fahrenheit, it does look like mine are working. 72F/matching room temp when idle and 160-170F when adding hot water. Reasonably close. I'll see if it stabilizes at the 135F setpoint of my mug in the reading and then add a note to the issue you linked.
Thanks again!

Oh that could do it!
Awesome! Thank you very much!
The non beta release should be out in a couple days if no other issues crop up.
Don't hesitate if there are any other issues or suggestions.

Ok, fixed in 0.5.0. Don't hesitate if there is anything else.


Added comments to documentation regarding the control grid scaling in case of using an affine transformation as t0

Added clarifying comments regarding the scaling of the control grid in the case of providing an affine transformation as starting point to:

docstrings of transforms MultiBSplineTransformWithNormal, AdvancedBSplineTransform, BSplineStackTransform, RecursiveBSplineTransform
the manual (section 5.3.5)

See http://lists.bigr.nl/pipermail/elastix/2017-February/002501.html

Thank you @quakberto , this is fixed with commit e4c66b6dd0c81c67b94606996e5e84d03a8996a7


Linux Support

Proper Linux support for project OpenGL! This contribution is intended to be inline with Cherno's programming intent and style.
Premake creates multiple Makefiles as .make files. Each project Makefile needs to be specified for compilation. To compile OpenGL-Examples, run from the command prompt:
make -f OpenGL-Examples.make

Confirming that these changes providing linux support worked on my arch linux system.  Very helpful.

@DaveAxiom thank you for your contribution! I'll check it out and merge it in once I'm happy. What Linux distro did you use?

I use a Ubuntu variant distribution. Ubuntu is a Debian based system which many popular distributions are also based on. The directions for installing required libraries is on the Hazel Project Linux PR branch. https://github.com/LovelySanta/Hazel/tree/linux-support-v2#32-linux

Running the OpenGL-Example one failed to load returning this error
[00:09:29] GLCORE: Could not open file '../assets/shaders/test.vert.glsl'
[00:09:29] GLCORE: Could not open file '../assets/shaders/test.frag.glsl'
[00:09:29] GLCORE: [OpenGL Debug HIGH] 0:1(1): error: syntax error, unexpected $end
[00:09:29] GLCORE: Assertion Failed: GL_DEBUG_SEVERITY_HIGH

Os: Ubuntu

@AliAlboainin96 This branch is modified minimally to make it easy to merge. Change into the OpenGL-Examples directory and try running OpenGL-Examples again. The Hazel project has the same issue and it's expected that an asset manager will be written someday. Sorry about that.
cd OpenGL-Examples
../bin/Debug-linux-x86_64/OpenGL-Examples/OpenGL-Examples

@DaveAxiom For some reason deleting the repo and recloning it worked !

This seg faulted on example for me and I sort of assumed it might be a conflict with installed glfw. As a learning exercise I decided to follow the commits on this to a clean branch and make my own Linux build more to my taste. I didn't really keep easy merging in mind, renaming and moving subprojects (and updating to latest original sources) but I'm pretty happy with the result, especially as it doesn't segfault anymore.
I diverged a fair bit but it might be worth a quick look at mine for things like the system glfw support and copying of shaders. It's my first time using premake so feel free to point out if I've done anything dumb too, I can't test Windows so it's entirely possible I broke it :)
https://github.com/DominoMarama/OpenGL

u@c:/OpenGL$ bin/Debug-linux-x86_64/OpenGL-Examples/OpenGL-Examples
[18:05:00] GLCORE: OpenGL Info:
[18:05:00] GLCORE:   Vendor: NVIDIA Corporation
[18:05:00] GLCORE:   Renderer: NVS 5200M/PCIe/SSE2
[18:05:00] GLCORE:   Version: 3.3.0 NVIDIA 390.143
Segmentation fault (core dumped)
u@c:/OpenGL$

@pulsatorius
The minimum version of OpenGL needed is 3.3 which is what you have. You do have an old video card. I can give you tips on how to get this project setup in CodeBlocks for you to step through and debug. This is my output for this program:
[22:55:04] GLCORE:   Vendor: X.Org
[22:55:04] GLCORE:   Renderer: AMD Radeon (TM) RX 460 Graphics (POLARIS11, DRM 3.35.0, 5.4.0-72-generic, LLVM 11.0.0)
[22:55:04] GLCORE:   Version: 4.6 (Compatibility Profile) Mesa 20.2.6```

I use Eclipse not CodeBlocks normally. In this case I use the CLI, with make -j4 -f OpenGL-Sandbox.make.
The version is set by the program. When I run the code I have created from Cherno's OpenGL Course on YouTube, with
    glfwWindowHint(GLFW_CONTEXT_VERSION_MAJOR, 3);
    glfwWindowHint(GLFW_CONTEXT_VERSION_MINOR, 3);
    glfwWindowHint(GLFW_OPENGL_PROFILE, GLFW_OPENGL_COMPAT_PROFILE);

, note the COMPAT instead of CORE, I get
4.6.0 NVIDIA 390.143
Registering test Clear Color
Registering test 2D Texture

So the Nvidia driver can run OpenGL 4.6.0.

Shouldn't this conversation be held at https://github.com/DaveAxiom/OpenGL?
I tried to debug and got this.
Thread #1 [OpenGL-Sandbox] 152096 [core: 2] (Suspended : Signal : SIGSEGV:Segmentation fault)
	0x0
	GLCore::Utils::EnableGLDebugging() at OpenGLDebug.cpp:42 0x5555555d187e
	SandboxLayer::OnAttach() at SandboxLayer.cpp:16 0x5555555bf4b3
	GLCore::LayerStack::PushLayer() at LayerStack.cpp:20 0x5555555c43a1
	GLCore::Application::PushLayer() at Application.cpp:38 0x5555555bfa4b
	Sandbox::Sandbox() at SandboxApp.cpp:11 0x55555556d215
	std::make_unique<Sandbox>() at unique_ptr.h:857 0x555555572a99
	main() at SandboxApp.cpp:17 0x5555555673d7

It looks like the call to glDebugMessageCallback() gives the segmentation fault.
According to http://docs.gl/gl4/glDebugMessageCallback it was introduced in OpenGL 4.2.

If I change lines 49 in /OpenGL-Core/src/Platform/Windows/WindowsWindow.cpp from
49:		glfwWindowHint(GLFW_CONTEXT_VERSION_MAJOR, 3);

to
49:		glfwWindowHint(GLFW_CONTEXT_VERSION_MAJOR, 4);

I get a black window, which I think is the correct behaviour.
I think I'll be using this lines 49-51 in my code:
49:		glfwWindowHint(GLFW_CONTEXT_VERSION_MAJOR, 4);
50:		glfwWindowHint(GLFW_CONTEXT_VERSION_MINOR, 3);
51:		glfwWindowHint(GLFW_OPENGL_PROFILE, GLFW_OPENGL_COMPAT_PROFILE);

Commenting out lines 49-51 also works for me.


Handle updates to certs or CA info

If the certificates or CA info is updated (re-issued, transferred to a different CA, etc), the charm needs to handle that by updating the files on disk (already done) and restarting the services (added here).

tls_client.certs.changed is currently handled by kick_api_server. The new update_certs handler will conflict with it.
I do think that kick_api_server doesn't do enough. Presumably we'd want to restart kube-controller-manager, too, given that it takes in the CA and cert/key as options.
We probably don't need to restart kube-scheduler, but I also don't see any real harm in doing it.
All that said, I recommend removing the kick_api_server handler in favor of the new update_cert one.

Updated per review.  As per the other PRs (copying here for completeness), this was tested manually on AWS by doing the following:

Deploy CDK with the four patched charms & docker subordinate, wait to settle
Run some test pod in the cluster (I used busybox and left processes running on the pod)
Add Vault to the cluster, wait to settle
Unseal Vault, wait to settle
Remove EasyRSA, wait to settle
Update kubectl config
Confirm pod is still functioning

Unseal Vault, wait to settle

In testing, during this step, I found that there is a race that can leave kubernetes-master in a bad state where kube-apiserver is no longer able to connect to etcd.
The following sequence occurred:

certificates-relation-changed hook ran, resulting in new certs being written, and kube-apiserver being restarted as expected. However, cert information used to connect to etcd was -not- updated during this time, as those come from the etcd relation (handled in handle_etcd_relation), not the certificates relation.
etcd-relation-changed hook ran, in which the etcd relation provided new client cert and CA info. However, start_master did not run again, so handle_etcd_relation was not called again, so the new certs were never written.

In this state, all kubectl calls fail. Hooks on kubernetes-master and kubernetes-worker are affected (staying in "executing" state for a long time, as they retry kubectl commands), and the cluster has not recovered on its own. Removing easyrsa did not help.

Flannel also failed to switch to the new etcd client cert info. From journalctl -o cat -u flannel:
E0701 19:17:33.771678   29435 watch.go:171] Subnet watch failed: client: etcd cluster is unavailable or misconfigured; error #0: x509: certificate signed by unknown authority
; error #1: x509: certificate signed by unknown authority
; error #2: x509: certificate signed by unknown authority
E0701 19:17:34.511649   29435 watch.go:43] Watch subnets: client: etcd cluster is unavailable or misconfigured; error #0: x509: certificate signed by unknown authority
; error #1: x509: certificate signed by unknown authority
; error #2: x509: certificate signed by unknown authority
E0701 19:17:34.787105   29435 watch.go:171] Subnet watch failed: client: etcd cluster is unavailable or misconfigured; error #0: x509: certificate signed by unknown authority
; error #1: x509: certificate signed by unknown authority
; error #2: x509: certificate signed by unknown authority
E0701 19:17:35.527465   29435 watch.go:43] Watch subnets: client: etcd cluster is unavailable or misconfigured; error #0: x509: certificate signed by unknown authority
; error #1: x509: certificate signed by unknown authority
; error #2: x509: certificate signed by unknown authority
E0701 19:17:35.805219   29435 watch.go:171] Subnet watch failed: client: etcd cluster is unavailable or misconfigured; error #0: x509: certificate signed by unknown authority
; error #1: x509: certificate signed by unknown authority

I suspect flannel, calico, canal, and tigera-secure-ee all need similar work to account for this transition.

@Cynerva Please take a look at the following PRs to address the issue in the other charms as well:

https://github.com/charmed-kubernetes/charm-flannel/pull/55
https://github.com/charmed-kubernetes/layer-calico/pull/38
https://github.com/charmed-kubernetes/layer-canal/pull/35
https://github.com/charmed-kubernetes/layer-tigera-secure-ee/pull/17

Ready for review. Tested the latest commit as follows:

Deployed charmed-kubernetes with modified charms (bundle.yaml).
Deployed vault in auto-unlock mode:

juju deploy cs:percona-cluster
juju deploy cs:~openstack-charmers-next/vault
juju config vault auto-generate-root-ca-cert=true totally-unsecure-auto-unlock=true
juju relate vault percona-cluster

Waited for cluster to settle.
Related vault to etcd:

juju relate vault:certificates etcd

Waited for cluster to settle (took ~5 minutes).
Related vault to kubeapi-load-balancer, kubernetes-master, kubernetes-worker:

juju relate vault:certificates kubeapi-load-balancer
juju relate vault:certificates kubernetes-master
juju relate vault:certificates kubernetes-worker

Waited for cluster to settle (took another ~5 minutes).
Removed easyrsa:

juju remove-application easyrsa

Some comments:

Addons that needed restarting: coredns, metrics-server, heapster, nginx-ingress-controller. I suspect others likely need it too, e.g. csi-rbdplugin. To be safe, I made the charm restart all addons that are managed by CDK. We will need to document for users that they may need to manually restart addons they have brought themselves.
DNS impact is small, as CoreDNS still responds to DNS lookups while it is unable to reach k8s. Since the restart of CoreDNS is a rolling restart, there is no downtime.
Ingress impact is moderate, as ingress is temporarily unavailable while nginx-ingress-controller is restarted (because it is a DaemonSet that binds to host ports).
Doing the migration in two steps (etcd first, then kubernetes) reduces overall downtime, and in particular, seems to cause much less downtime for ingress.

This now depends on https://github.com/charmed-kubernetes/cdk-addons/pull/133
I updated the addon restart code to select on a new cdk-restart-on-ca-change label.
Tested again as described in https://github.com/charmed-kubernetes/charm-kubernetes-master/pull/34#issuecomment-510186591, went well. Needs review.

Do not merge, needs retest.
Updated kubectl calls in this PR to use charms.layer.kubernetes_common.kubectl, and changed the new remove_state calls to clear_flag. Needs review.

Done testing, awaiting approval.


Long Term Statistics doesn't show up on HA 2012.12+

From this discussion started at community forum.
Problem:
Long term statistics appears to be broken on HA core 2022.12.
Long story short:
The probable cause, as mentioned in this developers blog post, is a change in recorders "recorder/statistics_during_period" api response. In particular "statistic_id" field is no longer being repeated for each list item in the returned map.
I spinned up a v2022.11.5 system and can confirm LTS are displaying there as expected!
Below are example PM2.5 measurements from this station, last 6 months and week period of time.
Results from newest core 2022.12.2:
pl0194a_pm25-core2022.12.2-2022-12-11_22 46 37.csv
pl0194a_pm25-core2022.12.2-2022-12-11_22 46 45.csv
pl0194a_pm25-core2022.12.2-ws.json
Compared to previous last stable version of core 2022.11.5:
pl0194a_pm25-core2022.11.5-2022-12-11_22 43 50.csv
pl0194a_pm25-core2022.11.5-2022-12-11_22 45 33.csv
pl0194a_pm25-core2022.11.5-ws.json

Ah this is good info. It does look like this malfunction is caused by this breaking change in the HA API. Here is a beta with a fix, would you mind trying it ?
https://raw.githubusercontent.com/alexarch21/history-explorer-card/main/history-explorer-card.js

Getting late but here are some quick results:
v1.0.39

vs beta

Also the previously posted view with 4 statistics now shows more data:

Also the "undefined" strings in CSV statistics export are now properly showing entity_id..

Perfect, that was it then. I will release a hotfix on HACS. Thanks for reporting this !


Fix reolving

Coverage remained the same at 98.056% when pulling 683b15102daea9ce38b25d3e589de051b6ff4f47 on fix-reolving into d7907dc12af3cc923b6dd06342ca8cfc6adafc26 on master.


Duplicated 'moment' library from bonnie into cql_qdm_patientapi

Duplicated 'moment' library from bonnie into cql_qdm_patientapi, but only when running tests

tweaked test configs to run the most simple cql-dependent test
removed placeholder example test

This is the first part of replacing https://github.com/projecttacoma/cql_qdm_patientapi/pull/67
JIRA: https://jira.mitre.org/browse/BONNIE-972
TESTS: run 'bundle exec teaspoon'
(in support of Cumulative Medication Duration)

Looks good to me. One question, when I run the test why does the output say " 1 example, 0 failures"? Why "example"?

It does that for the Bonnie teaspoon console runner, too. I poked around for actually almost an hour and never figured out why. In the teaspoon html runner it doesn’t say that. I can’t find “example” in the source code. I figure it's no big deal for now.

I didn't have instanbul installed, even. But following the 'npm install' request it worked just fine for me. Maybe you need to do a 'bundle install'?
Starting the Teaspoon server...
Teaspoon running default suite at http://<IP_ADDRESS>:57487/teaspoon/default
.

Finished in 0.01300 seconds
1 example, 0 failures

=============================== Coverage summary ===============================
Statements   : 42.93% ( 1138/2651 )
Branches     : 11.43% ( 225/1969 )
Functions    : 26.17% ( 196/749 )
Lines        : 39.69% ( 672/1693 )
================================================================================

I have pushed the config for coverage. This is much cleaner now:
=============================== Coverage summary ===============================
Statements   : 42.48% ( 746/1756 )
Branches     : 6.78% ( 53/782 )
Functions    : 30.8% ( 134/435 )
Lines        : 35.97% ( 554/1540 )
================================================================================

This doesn't include support libraries.


Application hangs when given a long expression.

Describe the bug
If I write a long expression and press equal to and return to this application after a while, it gets hanged !!!!!!
To Reproduce
Steps to reproduce the behavior:

OPEN CALCULATOR PLUS.

Write down a long expression and press equal to button.

Press the multi tasking button and then come back to the application little while later.

The application hangs

Expected behavior
The expected behaviour should have been that, it should have given me the answer instead of hanging itself 😑
Screenshots
N/A
Android (please complete the following information):

Device: Realme 6 (RMX 2001).
OS: Android 10
App Version 1.11.1

Fixed in latest beta
2.0.0


Candlestick Chart can be mixed with Line chart ?

Can I combine Candlestick Chart  with LineChart in coordinate axis ?  I don't see anything in the document.
Like this

This is not supported yet, but being considered.
Closing as duplicate of #883

The tooltip freaks out when 2+ lines are added. Is there a way to create a custom function for candlestick + line graphs for the tooltip?

Any updates on this? Would be great to have multiple lines on a candlestick graph. Is there maybe another way doing that?


Mancala Board

Description; Exactly replicate the figma design of the Manacala Game board

Use gradients to show the depth of each pot on the board.
For the main side pots (2), adjust the gradients to accurately represent their depth.
Position the "number of seeds within each pot" according to the layout shown in Figma.
The seed color should be #D9D9D9.

Figma for reference; https://www.figma.com/design/6fQvKQWmxnt0XLUSjBjecj/MANCALA-Game-UI?node-id=1141-16535&m=dev
How it looks right now

How it should look as its on figma

Can I be assigned this issue? I have extensive knowledge of Figma and I’m a developer, I’ll like to be given the opportunity to apply my skills please?

@Israelrex9 can I be assigned this issue, please. I'm a product designer and can delever a clean design.

✨ When applying for a task, please include a brief description of your experience and an estimated time frame for completion.

As a UI/UX Designer, I have extensive experience in creating user-centered designs that enhance user experiences and meet business objectives. My expertise includes:
User Research, wireframing and prototyping, Visual Design, Interaction Design and collaboration.
As a Full-Stack Blockchain Developer, I possess a robust skill set in both front-end and back-end development, My experience includes html, css, react, JavaScript Cairo ,TypeScript, rust and small knowledge on GO.
I’d have my PR ready in less than 24 hours once I’m assigned.

@Israelrex9, can I be assigned this issue, please. I'm a product designer with almost 2 years of experience in this field and can deliver a clean design in 3 days.
https://www.figma.com/design/ziGnFqAHvDKbjr3JNoK7NX/Portfolio?node-id=168-345&t=C6TaonHUTQAcYtMO-0

@Israelrex9, can I be assigned this issue, please. I'm a product designer with almost 2 years of experience in this field and can deliver a clean design in 3 days.
Here are some things I've done. https://www.figma.com/design/ziGnFqAHvDKbjr3JNoK7NX/Portfolio?node-id=168-345&t=C6TaonHUTQAcYtMO-0

Hello, really nice figma, but this is a frontend development task.

Hi @Israelrex9 I'm an experienced frontend developer and I would love to contribute to this projects.  Below is my onlydust profile and also frontend contributions I've done
https://app.onlydust.com/u/kateberryd

Hello I’m Isaac, a full-stack JavaScript developer with a proven track record of contributing to starknet and od hack projects
here is my OnlyDust profile
https://app.onlydust.com/u/Dprof-in-tech
To solve this issue I would follow the due instructions using CSS elements to position and achieve the needed design look from the figma file, noting the properties of each widget so I can give a pixel-perfect job.
I would deliver this task within a timeline of 2 days given no blockers and if there are any I would make sure to provide a notice beforehand
May I be assigned to this task so I can start off with my solution?

Hi @Israelrex9 I am a frontend developer with a knack for pixel perfect implementation and I would love to work on this issue
Here is my onlydust profile: https://app.onlydust.com/u/Ayoazeez26
Here is my github profile: https://github.com/Ayoazeez26
I would take 2 working days to deliver this task unfailingly

I would love to work on this issue. i am a full stack web3 developer. I have been exploring Mancala since last day and have gone through the codebase and I reckon I can solve this issue
Here is my Profile:- https://app.onlydust.com/u/PoulavBhowmick03
Not much, since recently opened the account, but I can get this done

@kateberryd I just assigned this task to you. Let me know if you need help with anything else

@okhaimie-dev Thank you. I'll communicate on telegram


BIP32-compatible HD wallet support

What sort of derivation are we using today? Is there a reason we chose to do something non-standard here? How much work would it be to adopt BIP32 instead?

does smapp already support hierarchical deterministic wallet generation?

We have some kind of derivation, but only by index. Not by derivation path as in BIP32 standard.
So probably the answer is NO.
Originally posted by @brusherru in https://github.com/spacemeshos/smapp/issues/888#issuecomment-1176760541

Seems we're using this implementation of ed25519 under the hood: https://github.com/spacemeshos/ed25519-WASM which wraps this implementation into wasm: github.com/spacemeshos/ed25519, and finally here is an actual implementation of NewDerivedKeyFromSeed: https://github.com/spacemeshos/ed25519/blob/d72da3b5f487b39d182a66532d362f5929962470/ed25519_ext.go#L96-L109
And this is how we call in particular deriveNewKeyPair from JS: https://github.com/spacemeshos/smapp/blob/develop/desktop/cryptoService.ts#L57-L67

It seems we need to replace this WASM implementation with one that provides deriving keypair from the HD path.
Btw, do we need to support also BIP44 "Multi-Account Hierarchy for Deterministic Wallets"?

Btw, do we need to support also BIP44 "Multi-Account Hierarchy for Deterministic Wallets"?

Very likely, yes. I think this is the standard. Will ask @oriya to investigate.

This is what standard tools like mycrypto give you:

Here's a useful tool: https://iancoleman.io/bip39/

okay here is what I know so far -
Yes, it seems be the standard.
Wallets that follow the BIP44 standard can import each other’s seeds.
The BIP44 standard also allows for multiple different currencies. So there's a different branch for Bitcoin and a different branch for Ethereum, and a different branch for Litecoin. And basically any type of cryptocurrency or blockchain that can support mnemonic phrases, derived under this standard, has a branch that it uses. and makes it possible to handle all the different currencies listed here:
Registered coin types for BIP-0044
Spacemesh Coin is already registered as Coin Typeof BIP44

Also, regarding your referenced image above - I found a longer article that mentions this tool, confirming that
"Most users of Ethereum are utilizing an address with a derivation path of m/44'/60'/0'/0/0 (BIP44)”
a side-note from Aviv is that we don't need to support full arbitrary paths - just 1 level of accounts per wallet.
I am going to keep investigating ... hope this is helpful for now.

Hi @oriya, remove please label on hold when your research will be finished.

Check-list:

[x] create POC for smapp with support ed25519++ bip32/43/44 through bip39 (mnemonic)
[ ] integrate through the new interface encrypt/decrypt wallet and add bip44 index for new sub-account to the wallet
[ ] add unit tests and sync with smcli
[ ] add documentation for wallet integration in SMIPS


[CO-175] Run Sidebar callback on escape click

Allow closing the sidebar with Escape key

@khola @Horay @raczyk
I think we should rename the onClick prop to the onClose, it's more convenient since it's only fired by elements that close the sidebar.
example here https://material-ui.com/components/drawers/


the xxx.archive(req, xxx) method don't  work

version:
sails 1.2.3
sails-hook-multitenant 0.5.17
I try to do something like this ->

and got this ->

the other methods work fine!

Oh, it's great bug. I will fix and comment the resolution to this bug.
Thx for report this problem in the hook.

@acalvoa thanks for sharing this on GitHub. I'm new to Sails so I don't yet know my way around it but I was wondering about how this goes about multi tenancy, how does it separate data/access to data? By table schema, connection, row access level?

@cyupa The multitenancy database connection, use differents databases (database connections) to access data by each client in your platform, normally in the same DBMS.
The main idea, is separate the data between clients, obtaining two benefits.

The access to data is totally separate, conserving the data schema and structures avoiding merge of data across clients.
Allow query with better performance, because the clients queries only read in tables with his data, avoiding read, select and find in tables with a large volume of not relevant data.

Thanks for taking time to provide me with this answer.
Much appreciated.

Hello guys, sorry for the delay coding a solution for this issue.
The solution was published in the PR #12. with package versión 0.5.19
Any question or bug finded, please tell me for fix them in short.
Thx for your contributions.
@xhb if the solution its Ok?, can u close the issue. Thx a lot


Allow extending the load_dataset parameters in custom tasks inheriting AbsTask

Currently, it is only possible to pass in a path and revision to load_dataset. This is fairly limiting, and forces users to implement their own AbsTask.load_data` function, which relies on the internals of the library.
This PR allow to specify any parameter supported by datasets.load_dataset in custom tasks. Currently, the metadata is specified as such:
    my_task = TaskMetadata(
        name="MyTask",
        hf_hub_name="org/dataset",
        revision="1.0",
        ...
    )

This is hard to extend as we would need to add new keys to that Pydantic object for each load_dataset key we want to support.
This PR proposes to instead have the following structure:
    my_task = TaskMetadata(
        name="MyTask",
        dataset={
            "path": "org/dataset",
            "revision": "123"
        }
        ...
    )

This allows users to add any key they want (dataset config name, token, etc.). All key/values are passed in to load_dataset. ~Note that this is done in a backward compatible manner. A pydantic validator supports the old parameters and populates the dataset dictionary.~
Migration
We've included in the PR a migration of all the built-in tasks to avoid logging a deprecation warning when running them. This is what causes most of the line changes.
Refactoring
While migrating the tasks to the new metadata_dict to use dataset that a lot of time, AbsTask.load_data was overridden for the sole purpose of inserting a dataset_transform call. This was such a common pattern that this led to a lot of duplication. We propose here to call dataset_transform in AbsTask, and this default to a no-op.
Bug fixes
A few times, the revision of the dataset was not passed to load_dataset, leading to a discrepancy between the revision in the metadata and the actual loaded data. These were fixed and I indicated the location of these issues in the PR.
Testing
I see that the repo contains test suites for all abstract tasks. Please let me know if any additional testing is required from our end.
cc. @gbmarc1

This pr. might also relate to the discussion in #301 about creating two dataset sources mteb org + original dataset.

I'll address the comments some time tomorrow!

This seems like a very pragmatic change, with an extremely clean PR description. Nice job!
Moving the load_dataset logic and calling dataset_transform from the AbsTask might make some dataset instances slightly less clear for new contributors. AFAICT it's a deduplication vs. indirection/coupling trade-off, and I think it's very worth it in this instance 👍
As a side-note: I've been looking into codemodification-programming for cases like this, something like gritql. If you have any experience here, I'd love to hear about it in a discussion.

Perfect @gariepyalex I have set the tests to run assuming they pass it will be merged it - thanks again for the contribution. If you do want to participate in the MMTEB coming up, feel free to add your names and 2 points to the points sheet (if not feel free to ignore this part).

Great! I'll add our names there.


Replace mention of "azureml-dataprep"

Replace mention of "azureml-dataprep" with "azureml-dataset-runtime". We have made "azureml-dataprep" private and do not recommend users interact directly with it. Instead, "azureml-dataset-runtime" controls the version of dataprep to depend on.

@yikei : Thanks for your contribution! The author(s) have been notified to review your proposed change.


mac-9, mac-22, mac-25, mac-24 and mac-7 are dead.

Type of Request
bug
Infrastructure Environment
LUCI, Github, Cocoon scheduler, Autosubmit, etc...
What is happening?
mac-9, mac-22, mac-25, mac-24 and mac-7 are dead.

Steps to reproduce
Step 1:
Step 2:
..
Step n:
Expected results
I expect to see X when Y is finished.

All five machines above are of sync with Salt master, run command "salt-call state.apply" to re-sync with Salt master again.


Adding ec2 instances to subnets

Hello,
I've been experimenting with the vpc module to modularise my Terraform code in general. On creation of the VPC with a public and private subnets, I wish to launch instances in these subnets.
The subnets variable itself is a Terraform list and does this mean I have to actually dereference individual elements of the subnets to actually launch instances using the `aws_instance' resource?

Hi,
You need to use element() interpolation function to pick single subnet to provide to aws_instance, like this:
module "vpc" {
  # ... omitted
}

resource "aws_instance" "this" {
  subnet_id = "${element(module.vpc.public_subnets, 0)}"
  # ... omitted
}


How to use manga inpainter?

Or has it not been added to the GUI yet?

hi, you can upgrade to the latest version to use it.
pip install lama-cleaner==0.27.1

hi, you can upgrade to the latest version to use it.
pip install lama-cleaner==0.27.1

I did so. the manga button did not appear.

Okay, after a full removal and installation, it was fixed. Sorry


[do not merge] Mockup of concepts section

Considering adding a Concepts section to the Tezos docs. Not sure if it makes sense to add this kind of information here when opentezos.com is available, but people are making the case for some basic info on how blockchains work to be added here.

Stale; closing.


Update requirejs example

I found that several errors in requirejs example.

Invalid url for requirejs cdn.
Invalid baseUrl.
Load d3, not d3-selection and d3-collection.

No.3 will make no problem if my other pull request #178 is merged, but it's not yet done, and I think it would be better to follow d3's micro library philosophy.
However, d3's micro libraries just contain source files, not build files, while npm modules do. So I added notice comment in console and above graph div.

Thanks for the fix!


patches: add patch fixing CVE-2023-45288

I also would like to note we've removed the following hunk (https://github.com/golang-fips/go/pull/182/files#diff-a497aafe01591ce7d323007d9264916724d180df7df77b7beed4d00776aa6288R25) from the included patch file as it isn't necessary in these builds.


[VS Code]Connection lost then be trapped

Issue Type: Bug
When I run live share and lost connection, vscode will ask me reconnect or cancle. But both of them will try to reconnect the server. So that, if remote server stoped, it will be trapped in dead circle, then I have to use force close my vscode :(
Extension version: 1.0.905
VS Code version: Code 1.38.1 (b37e54c98e1a74ba89e03073e5a3761284e3ffb0, 2019-09-11T13:31:32.854Z)
OS version: Darwin x64 18.7.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-5350U CPU @ 1.80GHz (4 x 1800)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: enabledoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_deferred_display_list: disabled_offskia_renderer: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
6, 7, 8

Memory (System)
8.00GB (0.14GB free)

Process Argv

Screen Reader
no

VM
0%

@isKevinTrue thanks for reporting the issue. I am trying to recreate the situation that you are facing but I was not able to hit the issue where my VS Code is hung trying to connect to remote server. This is what I was trying to do:

Share a session from a machine and join the session from another machine.
Put the second machine to sleep (for a long time)
Disconnect internet from the first machine.
Wake up second machine and cancel rejoin action.

I did not reconnection once I have clicked cancel in the pop up. Is there something else that you are doing while reconnecting?

I used with 2 PC. (PC_A runs VS2019 and Windows 10, PC_B runs VSCode and macOS10.14)

Connect with live-share
Sleep PC_B
PC_A stop share
wake PC_B up.

Then my vscode will be unable to exit and do things even more. (Maybe we are under debuging? PC_A start a build process while PC_B under sleeping.)


Fixing modifications

For many of the altered protein sequence, modification data will also be incorrect.
After table updated:
https://github.com/pombase/curation/issues/3024
we need to

export table
check which sequences have affected residues
(note this is not as simple as just checking on a residue basis, will need to be done on a dataset&protein basis because many residues  will be correct by chance)
also whether something needs repairing will depend on the age of the change and the age of the publication (although I imagine most HTP data will be old versions sequence because most proteomics pipelines use protein sequence from uniprot)
Need to record somewhere the difference between the old and new (most of the recent ones are truncations, but not all)
Kim can "repair" the spreadsheet data.
we can get a separate report of which genes have modification in Canto, and the numbers to decide whether to manually or automatically fix

This is a really bad description of what needs to happen to fix the "modified residue" problems.

Kim can "repair" the spreadsheet data

Which spreadsheet?

I mean the 'phaf' files, but @manu can do this no we have no need to reduce his work load imminently ;)

@manu this ticket is probably covered by one of yours?

This is in the pipeline yes, after I discuss with Kim. The ones from the svn folder (vast majority of mistakes were there, I guess because they used Uniprot sequences for mass spec or other HT method) are fixed.

This is done


Make page for displaying a single repo

The purpose of this page is to demonstrate that we can get data about a single specific repository. This page should display the basic JSON data for the repo.

We want to display the name, description, latest version, date created, URL from the remote, base_path from the distribution.


How to have different navbar and transitions for Android and iOS?

Version

react-native-router-flux v3.35.0
react-native v0.33.

In Android the navbar should only have the title and have no transitions between pages.
How can I do this?
In the examples there's only a index.js and no difference between android and ios.
I tried to hide the navbar if Platform.OS is android but then the title also disappears.
Am I missing something?
Thanks.

<Scene duration={Utils.isIOS() ? transitonDuration(ms) : 0} />


What does the colors mean in the tool window?

I know red means missing a translation. But what does orange/yellow and white mean?

I was wondering about this as well, so I went looking through the code and found:
if(missesValues(row, table)) {
    component.setForeground(JBColor.RED);
} else if(hasDuplicates(row, table)) {
    component.setForeground(JBColor.ORANGE);
}

So, orange means that the value is duplicated and white is just the standard, no problem color.

Possibly add configuration options to adjust the colour palette

I think there are two issues here.

Yellow is not ideal if you use the Light theme. Having a way to configure the palette is one way to address this, adjusting the colors based on the theme might be easier to implement.
I believe the most important issue is discoverability, and that might be an easy fix(es)

Add a tooltip on yellow and red keys.
There is a message appended to the key but only in the Tree View. Having a message for all issues in both views would be nice.


Replicate PR1012 in OTG GRIBI compliance test

Reference: https://github.com/openconfig/featureprofiles/pull/1012

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 55.714%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1170

Relevant Lines:
2100

💛  - Coveralls


Corrected repo link address in README.md and Cargo.toml

Details
Corrected repository link address from:
substrait/substrait-rs

to
substrait-io/substrait-rs

in the following files:

README.md
Cargo.toml

Thanks @nseekhao
Closes https://github.com/substrait-io/substrait-rs/issues/3


Bug 1873030: Make a subscription without at least one candidate fail resolution.

In order to allow subscriptions to be satisfied by an
already-installed CSV, those operators that are already associated
with a subscription are now a part of the resolution constraint
system. As a result, already-installed operators can appear in
resolution output.

/bugzilla refresh

/test unit

/lgtm

/retest

/hold cancel

/lgtm


DB error

following installation instructions i get:
metlo-db-1      | 2022-10-14 11:41:09.171 UTC [1] LOG:  database system is ready to accept connections
metlo-jobs      | Migration "removeOwnerColumnFromApitrace1665697571667" failed, error: Table "api_trace" does not exist.
metlo-jobs      | /usr/src/app/backend/node_modules/typeorm/query-runner/BaseQueryRunner.js:193
metlo-jobs      |             throw new TypeORMError_1.TypeORMError(`Table "${tableName}" does not exist.`);
metlo-jobs      |                   ^
metlo-jobs      |
metlo-jobs      | TypeORMError: Table "api_trace" does not exist.
metlo-jobs      |     at PostgresQueryRunner.getCachedTable (/usr/src/app/backend/node_modules/typeorm/query-runner/BaseQueryRunner.js:193:19)
metlo-jobs      |     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
metlo-jobs      |     at async PostgresQueryRunner.dropColumn (/usr/src/app/backend/node_modules/typeorm/driver/postgres/PostgresQueryRunner.js:1098:15)
metlo-jobs      |
metlo-jobs      | Node.js v18.10.0
metlo-jobs      | error Command failed with exit code 1.
metlo-jobs      | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
metlo-jobs exited with code 1
metlo-ingestor  | Migration "removeOwnerColumnFromApitrace1665697571667" failed, error: Table "api_trace" does not exis

Hey @eikaramba , let me take a look at this and get back to you.

Hey @eikaramba , sorry for the wait. Error should be gone now with the latest docker images.


[Benchmark] Explicitly set cache sizes

Turns out sled's cache size was still set incorrectly, but it doesn't really make an impact in the results.
I also updated the results because they were very outdated, feel free to run them on your hardware.

Thanks! I merged the first commit, and will re-run them on my machine


function Base.getindex(out::FMU2EvaluationOutput, ind) is not prepared when ind is a vector of indices

Base.getindex is called when the input arguments are an FMU2EvaluationOutput (out) and anything but not a CartesianIndex{A}.
In the example below, ind is a vector of indices.
Minimal example
import FMI: Base.getindex
fmi = fmiLoad("SpringPendulumExtForce1D", "Dymola", "2022x"; type=:ME)
fmiSimulate(fmi) #<-since no FMU2Component allocated <-and I will make a ticket rightaway for that.
Base.getindex(fmu(;dx_refs=:all),[1,2])

You need this when you want to make a Flux.Chain which uses a substet of the FMU-derivatives, e.g.
inputN = [2,9,10,12,17,24,25]
net = Chain(x -> myFMU(; x=x,dx_refs=:all),
            dx -> cache(dx),
            dx -> dx[inputN],
		…)

There is a workaround (if you only have dx-Output): One can use myFMU(...).dx as output of the first layer.
Proposed solution!?
Dispatch for ind::AbstractVector{<:Integer}
If that's okay for you, I can make a draft.

Yep, you are correct. See #58


Bugfix/issue 2380 algebra solver references

Submission Checklist

[ ] Run unit tests: ./runTests.py src/test/unit (NA)
[x] Run cpplint: make cpplint (ran it, but I think it is NA)
[x] Declare copyright holder and open-source license: see below

Summary
Add references regarding the implementation of the algebraic solver. Fix some errors in the doc.
Intended Effect
Help users use the solver and more advanced users investigate the algorithmic details of the solver.
How to Verify
Proofread the Stan reference manual.
Side Effects
Documentation
Stan manual
Reviewer Suggestions
Copyright and Licensing
Please list the copyright holder for the work you are submitting (this will be you or your assignee, such as a university or company): Charles Margossian
By submitting this pull request, the copyright holder is agreeing to license the submitted work under the following licenses:

Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

I edited all.bib using bibdesk, but this may have not been the right approach, seeing all the differences this seems to have created between the original and the new file. What method do you use to edit all.bib?

@charlesm93  GitHub.  Yes, please don't just change all the bib around because bibdesk has a different notion of formatting.  It'd probably be OK, but in general it's not good policy on a shared repo because of the potential for merge conflicts.

Bibdesk automatically adds a ton of metadata to the .bib, hence
all the conflicts.  It helps if you export as “Minimal BibTex” but even
then the auto formatting will cause conflicts.
What you want to do is edit the new references in Bibdesk, export
as “Minimal BibTex” and then cut and paste the exported text to
all.bib.

On Aug 14, 2017, at 12:20 PM, Bob Carpenter<EMAIL_ADDRESS>wrote:
@charlesm93 https://github.com/charlesm93 GitHub. Yes, please don't just change all the bib around because bibdesk has a different notion of formatting. It'd probably be OK, but in general it's not good policy on a shared repo because of the potential for merge conflicts.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/stan-dev/stan/pull/2382#issuecomment-322236585, or mute the thread https://github.com/notifications/unsubscribe-auth/ABdNlkpLa3kmsqn4jaQWsvRL4f_cXrVbks5sYHPFgaJpZM4O2WuS.

ok, the all.bib file should be fine now.


Define compile command in source

Someone mentioned in our open meeting last week that they would like the ability to define the compile command in the source, so when they execute the Run Action command, it will use the command defined in the active source.
ILEditor 2 had this feature kind of and it was awesome. Of course, this also has to support all the ILE languages, including RPG, COBOL, CL, DDS, SQL, etc.
Some ideas of what format we could use. Please comment with your suggestions too.
Simple comments
Simply put, you could define the command after a specific comment is found:
//compile: CRTBNDRPG PGM(&OPENLIB/&OPENMBR) ...

Scott Klement's BUILD tool
A quote from his documentation, which you can see here:

The build tool needs some way of knowing which comments in the program represent commands that should be run to build the code, and which comments are just ordinary comments. I wanted my build tool to be able to work with any programming language without having to actually understand the syntax of the language itself, and since every language has its own way of denoting a comment, I really had no way of picking out a comment from the rest of the code.
The solution I came up with was to look for the *> characters in the source code. Anywhere these two characters appear together would be assumed to be the start of a compile command.
With that in mind, I could make some minor changes to my source code to turn it into a build script. Using the same example as before, I added the *> symbols into my code as follows:
      * To compile:
      *>  OVRDBF FILE(CBOMASyy) TOFILE(CBOMAS08)
      *>  DLTPGM PYUEMPLR4
      *>  CRTBNDRPG PYUEMPLR4 SRCFILE(xxx/QRPGLESRC) DBGVIEW(*LIST)
      *>  CHGOBJOWN OBJ(PYUEMPLR4) OBJTYPE(*PGM) NEWOWN(KLOWN)
      *>  CHGPGM PGM(PYUEMPLR4) USRPRF(*OWNER)
      *>  DLTOVR *ALL

It would also use the Action variables instead of the variables in Scott's tool, since this has to work for streamfiles too.

After reading SK Build tool for the first time (!) and based on the knowledge of similar tools I have used, I would put some coins on the table:

the idea of using a separated character or characters to identify this section is great; usually, I saw this section at the very beginning of the source file, before any other lines, but in RPG ILE completely free it should follow the **free line;
also, this section usually ends with a clear final string, in order not to raise any doubt there is something more: in SK's solution there is no need for it because each subsection is a command on its own;
this solution implies each subsection >is< a command, whereas other solutions have pre-compilation commands, parameters only for the compilation command (which in turn is determined by the underlying procedure), and post-compilation commands.
I think we could try to write this parser getting the most from the various methods, like:
keeping the character(s) that identify this section,
keeping the form of self-contained subsections,
keeping the order of pre and post commands to the compilation command,
defining how to ask the underlying procedure to automatically determine the compilation command (placeholder sort of?), explicitly setting only the compilation parameters >or< write the whole compilation command.
I agree with you about the use of Action or similar to set variables which will work for stream files too.


Merge examples into a single examples folder

This seems completed with the latest updates in discussion w/ @ehennestad

Yes, thanks!


could not select device driver "nvidia" with capabilities: [[gpu]]

Apple M2 Pro, mscOS 14.2.1
run command: docker compose -f "docker-compose.yaml" up -d, got an error:
Attaching to gpt-sovits-container
Error response from daemon: could not select device driver "nvidia" with capabilities: [[gpu]]

this is docker-compose.yaml:
version: '3.8'

services:
  gpt-sovits:
    image: breakstring/gpt-sovits:latest   # please change the image name and tag base your environment. If the tag contains the word 'elite', such as "latest-elite", it indicates that the image does not include the necessary models such as GPT-SoVITS, UVR5, Damo ASR, etc. You will need to download them yourself and map them into the container.
    container_name: gpt-sovits-container
    environment:
      - is_half=False
      - is_share=False
    volumes:
      - ./output:/workspace/output
      - ./logs:/workspace/logs
      - ./SoVITS_weights:/workspace/SoVITS_weights
      - ./reference:/workspace/reference
    working_dir: /workspace
    ports:
      - "9880:9880"
      - "9871:9871"
      - "9872:9872"
      - "9873:9873"
      - "9874:9874"
    shm_size: 16G
    deploy:
      resources:
        reservations:
          devices:
          - driver: nvidia
            count: "all"
            capabilities: [gpu]
    stdin_open: true
    tty: true
    restart: unless-stopped

dose anyone know how to solve this? i have no idea how to solve this problem

@breakstring 看看？

Apple M2 Pro, mscOS 14.2.1 run command: docker compose -f "docker-compose.yaml" up -d, got an error:
Attaching to gpt-sovits-container
Error response from daemon: could not select device driver "nvidia" with capabilities: [[gpu]]

this is docker-compose.yaml:
version: '3.8'

services:
  gpt-sovits:
    image: breakstring/gpt-sovits:latest   # please change the image name and tag base your environment. If the tag contains the word 'elite', such as "latest-elite", it indicates that the image does not include the necessary models such as GPT-SoVITS, UVR5, Damo ASR, etc. You will need to download them yourself and map them into the container.
    container_name: gpt-sovits-container
    environment:
      - is_half=False
      - is_share=False
    volumes:
      - ./output:/workspace/output
      - ./logs:/workspace/logs
      - ./SoVITS_weights:/workspace/SoVITS_weights
      - ./reference:/workspace/reference
    working_dir: /workspace
    ports:
      - "9880:9880"
      - "9871:9871"
      - "9872:9872"
      - "9873:9873"
      - "9874:9874"
    shm_size: 16G
    deploy:
      resources:
        reservations:
          devices:
          - driver: nvidia
            count: "all"
            capabilities: [gpu]
    stdin_open: true
    tty: true
    restart: unless-stopped

dose anyone know how to solve this? i have no idea how to solve this problem

对不起，我没有在Mac平台上做过测试。但是按照我的理解Mac上没有Nvidia的显卡，所以可能无法安装对应的驱动以及在Docker里做基于GPU的训练和推理。因为我对目前这个项目还不是很熟悉，可能还需要些时间才能弄明白如何用纯CPU的方式来运行，然后再制作专门的CPU型的镜像。
I'm sorry, I haven't tested this on the Mac platform. However, based on my understanding, Mac doesn't have Nvidia graphics cards, so it may not be possible to install the corresponding drivers or perform GPU-based training and inference in Docker. Since I'm not very familiar with this project yet, it may take some time to figure out how to run it in a pure CPU manner, and then create a dedicated CPU-based image.

Need mps for training with GPU on M series Mac, which is only available on macOS, so it's not suggested to use this program via docker on Mac.
I'm not a docker user, so I'm not very familiar with this, hope the information may help.


update selenized light and dark to match the canonical selenized sRGB values

The original values in #257 correspond to those in the AppleRGB column in selenized the-values.md, but they should be the values from the sRGB column instead (as they are for the black/white variants).

thanks


Relax dependency constraints

@i80and Can you please take a look? We want to use this but cannot until a version is released with looser dependency constraints.

@ofek Hello! I'm happy to relax most of these constraints, but we will have to continue to pin docutils==0.16 since we interact closely with its internals.

Done!

@i80and Thanks, I'll keep a look out for the next release!


Cannot finish local build

I've been trying to build a caddy docker image with porkbun DNS using this Dockerfile:
FROM caddy:builder AS builder

RUN xcaddy build --with github.com/caddy-dns/porkbun

FROM caddy:latest

COPY --from=builder /usr/bin/caddy /usr/bin/caddy

And every single time the build freezes on the go download phase and does not advance:

What could be going on?
Thanks

Similar issue here. Building with xcaddy and the process hangs here:

You can work around this by adding --with<EMAIL_ADDRESS>to your build command... not sure why this fixes it.
This might be related to https://github.com/caddyserver/caddy/issues/5301, but in those cases the go get command was panicking, not just hanging.
Since the workaround is the same for both, I wonder if it's the same bug.
The Go team is aware of the bug and knows what the cause is. However due to low morale at Google right now, I'm told it's hard to find motivation to dig in and fix it. Understandably, we will need to wait for a proper fix.

Another solution for porkbun specifically is apparently to update its caddy/v2 dependency to v2.6.3

The dependency bump works for now at least.
Fixed in #3 with v0.1.1 published.


az container not working in 2.0.5

Why it was removed the container module in the latest version? What's the replacement now?

@mayurid can you comment on this one?

not work on 2.0.6 too

Hi Christian,
The CI/CD pipeline creation commands in the Azure CLI and ACS portal blade have been deprecated. We experimented with the ‘az container release create’ functionality, but based on user feedback and product usage, it became clear that we needed to improve container experiences directly within the VS Team Services portal and client tools like Visual Studio IDE, as well as target a broader set of deployment environments.  At //build 2017, experience improvements were made available for Visual Studio and Team Services to support container CI/CD to App Services and Service Fabric, with Kubernetes coming soon. Note that any CI/CD pipelines that were originally created with the ‘az container release create’ command will continue to function properly, because it created VSTS build/release definitions and Azure resources like Azure Container Service and Azure Container Registry that are supported products.
More information:
Continuous Delivery Tools for Visual Studio
Regards,
John

Thanks @johnsta for the feedback 👍 I was able to create the registry and the integration manually, the problem I had then was that when creating the tunnel by running this command:

az acs dcos browse -g myacs-rg -n myacs

That command was useful because I could easily access the DC/OS UI and access the containers in a private manner. Sure, I can create the tunnel using Putty but I couldn't access the containers because they're using a dynamic port. It seems that the above command is using the "az container" command too because it doesn't work in the latest version. Any other recommendation or alternative?

The 'az acs dcos browse' command continues to be supported. Seems like there was a recent regression and how you need to also explicitly pass in the --ssh-key-file argument, which should include the full path to the SSH private key associated with your cluster.
The command used to look up your default SSH path, and that behavior now seems to have regressed. I noticed you opened up a separate issue (thank you) and we should track that there, i.e. https://github.com/Azure/azure-cli/issues/3232

Ok, got it, I thought it was related, sorry 👍
I'll continue in the other ticket then and for me that will be all for this one :)

@johnsta I see you even deleted the page I was using as reference :( https://docs.microsoft.com/en-us/azure/container-service/container-service-setup-ci-cd

the az container command is not owned by ACS, removing label.


Problem validating JSON document against schema: I[#] S[#] doesn't validate with "transaction#"   I[#/service/name] S[#/properties/service/properties/name/type] expected string, but got null

I'm trying to get started with elastic-apm[flask] (version 2.1.1, on Python 3.6.5) and apm-server (6.2.4) running in docker.
My virtualenv after running, pip install Flask elastic-apm[flask] looks like:
blinker==1.4
certifi==2018.4.16
click==6.7
elastic-apm==2.1.1
Flask==1.0.2
itsdangerous==0.24
Jinja2==2.10
MarkupSafe==1.0
pyspark==2.2.1
urllib3==1.23
Werkzeug==0.14.1

My docker-compose.yml:
version: '3.6'
services:

  elasticsearch:
    image: docker.elastic.co/elasticsearch/elasticsearch:6.2.4

  kibana:
    image: docker.elastic.co/kibana/kibana:6.2.4
    depends_on:
    - elasticsearch
    ports:
    - '5601:5601'

  apm-server:
    image: docker.elastic.co/apm/apm-server:6.2.4
    depends_on:
    - elasticsearch
    ports:
    - '8200:8200'

Kibana apm dashboard shows status of apm-server is green.
from elasticapm.contrib.flask import ElasticAPM
from flask import Flask

app = Flask(__name__)
apm = ElasticAPM(app)

@app.route("/")
def hello():
    return "Hello World!

I use the following command to start hello.py
env FLASK_APP=hello.py flask run

When accessing doing curl localhost:5000, I see "Hello, world!" printed, but the following error occurs:
<IP_ADDRESS> - - [08/Jun/2018 16:27:46] "GET / HTTP/1.1" 200 -
HTTP 400: Problem validating JSON document against schema: I[#] S[#] doesn't validate with "transaction#"
  I[#/service/name] S[#/properties/service/properties/name/type] expected string, but got null
Failed to submit message: '<no message value>'
Traceback (most recent call last):
  File "/Users/ksmets/.virtualenvs/elastic-apm-flask/lib/python3.6/site-packages/elasticapm/transport/http_base.py", line 45, in send_sync
    url = self.sync_transport.send(self, data, headers)
  File "/Users/ksmets/.virtualenvs/elastic-apm-flask/lib/python3.6/site-packages/elasticapm/transport/http.py", line 77, in send
    raise TransportException(message, data, print_trace=print_trace)
elasticapm.transport.base.TransportException: HTTP 400: Problem validating JSON document against schema: I[#] S[#] doesn't validate with "transaction#"
  I[#/service/name] S[#/properties/service/properties/name/type] expected string, but got null

apm-server_1     | 2018-06-08T14:43:46.346Z	ERROR	[request]	beater/handlers.go:384	error handling request	{"request_id": "b448367c-c79b-46cf-8e16-9a9fb08726c1", "error": "Problem validating JSON document against schema: I[#] S[#] doesn't validate with \"transaction#\"\n  I[#/service/name] S[#/properties/service/properties/name/type] expected string, but got null"}
apm-server_1     | 2018-06-08T14:43:46.346Z	INFO	[request]	beater/handlers.go:150	handled request	{"request_id": "b448367c-c79b-46cf-8e16-9a9fb08726c1", "response_code": 400, "method": "POST", "URL": "/v1/transactions", "content_length": 676, "remote_address": "<IP_ADDRESS>", "user_agent": "elasticapm-python/2.1.1"

Kibana apm dashboard shows no apm data is flowing in.
Any ideas?

@ksmets Thanks for getting in touch.  This error indicates that the service name is not set.
One way to do that with your code:
app = Flask(__name__)
app.config['ELASTIC_APM'] = {
    'SERVICE_NAME': 'my-app',
}
apm = ElasticAPM(app)

Check out our flask configuration docs
for more options.

Thx, that indeed was the missing piece of the puzzle: env FLASK_APP=hello.py ELASTIC_APM_SERVICE_NAME=hello flask run

hi all i have the same problem, but when i start the app it runs it in the loopback
env FLASK_APP=hello.py ELASTIC_APM_SERVICE_NAME=hello flask run
http://<IP_ADDRESS>:5000/
but i want to run it like this <IP_ADDRESS>
if name == "main":
app.run(host='<IP_ADDRESS>', port= 5000)
that is how i got in the hello,py file that i have
how can i run this command with the <IP_ADDRESS> instead of the <IP_ADDRESS>??
env FLASK_APP=hello.py ELASTIC_APM_SERVICE_NAME=hello flask run


joint qpos and framepos outputs are different after calling mj_step

Hi,
I'm a PhD student and I'm trying to use MuJoCo for motion planning.
I use a 'framepos' sensor to measure the current position of an object. The object is controlled by an actuator which outputs a force in x-direction of the global frame.
Here a minimal example code including a model xml string:
import mujoco

xml = """
<?xml version="1.0" encoding="utf-8"?>
<mujoco model="planar_transport_system">
    <compiler angle="radian" coordinate="local" />
    <option timestep="0.001" cone="elliptic" jacobian="auto" gravity="0 0 -9.81"/>

    <worldbody>
        <body name="body_0" pos="0 0 0" gravcomp="1">
            <joint name="joint_0" type="free" damping="0"></joint>
            <geom name="geom_0" type="box" size="0.0775 0.0775 0.006" mass="1" pos="0 0 0" rgba="0 1 0 1"/>
        </body>

        <light directional="true" ambient="0.2 0.2 0.2" diffuse="0.8 0.8 0.8" specular="0.3 0.3 0.3" castshadow="false" pos="0 0 4" dir="0 0 -1" name="light0" />
    </worldbody>

    <sensor>
        <framepos name="pos_sensor" objtype="xbody" objname="body_0"/>
    </sensor>

    <actuator>
        <general name="actuator_x" joint="joint_0" gear="1 0 0 0 0 0" dyntype="none" gaintype="fixed" gainprm="1 0 0" biastype="none"/>
    </actuator>
</mujoco>
"""

model = mujoco.MjModel.from_xml_string(xml)
data = mujoco.MjData(model)

# joint
joint_name = "joint_0"
joint_id = model.joint(joint_name).id
joint_addr = model.jnt_qposadr[joint_id]
joint_dim = 7
# actuator
actuator_name = "actuator_x"
actuator_id = model.actuator(actuator_name).id
# sensor
pos_sensor_name = "pos_sensor"
pos_sensor_view = model.sensor(pos_sensor_name)
pos_sensor_id = pos_sensor_view.id
pos_sensor_adr = pos_sensor_view.adr[0]
pos_sensor_dim = pos_sensor_view.dim[0]

for step in range(0,10):
    data.ctrl[actuator_id] = 2
    mujoco.mj_step(model, data, nstep=1)

    print(f"step {step} - sensor output: {data.sensordata[pos_sensor_adr]:.6f}, joint qpos: {data.qpos[joint_addr]:.6f}")

Here is the output of my example code (for simplicity, I only considered the x components):
step 0 - sensor output: 0.000000, joint qpos: 0.000002
step 1 - sensor output: 0.000002, joint qpos: 0.000006
step 2 - sensor output: 0.000006, joint qpos: 0.000012
step 3 - sensor output: 0.000012, joint qpos: 0.000020
step 4 - sensor output: 0.000020, joint qpos: 0.000030
step 5 - sensor output: 0.000030, joint qpos: 0.000042
step 6 - sensor output: 0.000042, joint qpos: 0.000056
step 7 - sensor output: 0.000056, joint qpos: 0.000072
step 8 - sensor output: 0.000072, joint qpos: 0.000090
step 9 - sensor output: 0.000090, joint qpos: 0.000110

I was wondering why the sensor output is 0 after calling mj_step(). So I compared the sensor values to the joint qpos. Both should output the current position of the object w.r.t. the global frame. As shown in the example output, the sensor outputs and the qpos differ by exactly one call of mj_step(). Is this the desired behavior? For this particular example, I would have expected the sensor outputs and joint qpos to be similar in each step.
System Info

OS: Linux-6.2.0-39-generic-x86_64-with-glibc2.35 # 40~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Nov 16 10:53:04 UTC 2
Python: 3.11.6
MuJoCo: 3.1.1

Many thanks in advance!

Although it's counter-intuitive, this is the expected behaviour.
Take a look at the simulation pipeline docs to see what happens when you call mj_step.
qpos is an input to forward dynamics, and based on this input, the accelerations and all the sensor values are computed. So your sensor readings will always correspond to the qpos at the start of the step.
The very last part of mj_step is integration, where the computed accelerations are used to advance qpos, so the qpos you read at the end of the step corresponds to the next step's position.
Does that make sense?

If you want to get the "latest" sensor readings, you can always call mj_step1 after each mj_step. This is expensive but will update the sensor values to the current state. Note that this cannot work for sensors that report force or acceleration, since these are also a function of the control, which is perhaps unknown (since it might be a function of the sensor values).


support expiry date for facebook api >= 2.3

I'm troubled to get the expiry datetime as i use newer version of facebook API version. Please check my commits. Thanks.

Sorry for not getting around to this one, @irkho! I left some comments.

I just encountered this issue.  I was calling get_extended_access_token without specifying any version and my just started breaking today.  I was no longer getting expiration timestamps.  This PR fixed the issue for me (and I've learned my lesson about not specifying a version ;) ).

Well, this must be the longest it's ever taken to get a pull request merged. 😅 Sorry guys, and thanks for this. :sparkles: :cake: :sparkles:

This is in v1.0.11 on PyPi now.


add more support for testing

https://github.com/alingse/asasalint/issues/17

miss flag for testing


Testing

Continue testing various scenarios and edge cases to ensure robustness.

### Test Planning
Test Coverage for UI Interactions:
Tests for key user interactions, such as:

Clicking color buttons and updating the guess.
Pressing the "Check" button to evaluate a guess.
Winning and losing the game.
Starting a new game.

Mock Firebase Interactions:

Mock Firebase functions in the tests to simulate stats fetching and game result saving. This ensures tests don't rely on real database interactions.

Edge Cases: add tests for edge cases like:

randomCode or latestGuess being empty or undefined.
Extremely high or low values for tryNumber.

Snapshot Testing:

Use snapshot testing for static components like the home page or the final win/lose screens.

Added a CheckButton integration test.


Cut v3.1.0 release

There are ~20 commits in master since v3.0.0.
From a quick scan I think we've only added new lints and fixed bugs so this could be a MINOR version bump. Whoever takes on preparing the release candidate tag + announcement should verify that there isn't anything in the diff set that would require a major version bump (ref guidelines).
This is also a good chance for folks with open PRs/issues to make the case for whether we should hold the tag for any pending work.

I'll try to get through this list today.

I'll try to get through this list today.

So far, the only one that seems like it could be problematic is https://github.com/zmap/zlint/commit/747b41fe8a541f5dd39e5a323a81729ccfe8629e.

Since downstream projects depend on lint results and names for policy decisions changes of this nature will result in MAJOR version revision.

Seeing as how we had 130 certificates in the corpus turn bad on us due to a change in this lint I wouldn't be too surprised if this made lights turn red downstream. Of course, adding a new lint that makes certificates fail is going to happen, but this will trigger a "it was okay yesterday!" moment for some projects.

So far, the only one that seems like it could be problematic is https://github.com/zmap/zlint/commit/747b41fe8a541f5dd39e5a323a81729ccfe8629e.

Since downstream projects depend on lint results and names for policy decisions changes of this nature will result in MAJOR version revision.

Seeing as how we had 130 certificates in the corpus turn bad on us due to a change in this lint I wouldn't be too surprised if this made lights turn red downstream. Of course, adding a new lint that makes certificates fail is going to happen, but this will trigger a "it was okay yesterday!" moment for some projects.

@christopher-henderson That's a good point, thanks for flagging that one.
I'm of the opinion that this case is a bug-fix and so the change in lint results shouldn't be seen as a breaking change like if a new requirement were added, or existing results reclassified. I'm very open to different interpretations if folks disagree but I feel like we could still call this a minor release.
What do others think?

@christopher-henderson That's a good point, thanks for flagging that one.
I'm of the opinion that this case is a bug-fix and so the change in lint results shouldn't be seen as a breaking change like if a new requirement were added, or existing results reclassified. I'm very open to different interpretations if folks disagree but I feel like we could still call this a minor release.
What do others think?

I think that this is a minor revision. Every bug fix in this project is going to lead to changed lint results. The API is not changing.

I think that this is a minor revision. Every bug fix in this project is going to lead to changed lint results. The API is not changing.

I agree as well. Lint results should change if bugs were introduced and that doesn't seem to justify a major revision.

I agree as well. Lint results should change if bugs were introduced and that doesn't seem to justify a major revision.

I happen to agree that it does not warrant a major revision, but better to say something when you see something.

I happen to agree that it does not warrant a major revision, but better to say something when you see something.

Absolutely! I appreciate you surfacing the question!
On Sat, Jan 23, 2021 at 2:24 PM Christopher Henderson <
<EMAIL_ADDRESS>wrote:

I happen to agree that it does not warrant a major revision, but better to
say something when you see something.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/zmap/zlint/issues/545#issuecomment-766189117, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AABREUFH4S5VNT4TTECIXWLS3NEAZANCNFSM4WHS77BQ
.

Absolutely! I appreciate you surfacing the question!
On Sat, Jan 23, 2021 at 2:24 PM Christopher Henderson <
<EMAIL_ADDRESS>wrote:

I happen to agree that it does not warrant a major revision, but better to
say something when you see something.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/zmap/zlint/issues/545#issuecomment-766189117, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AABREUFH4S5VNT4TTECIXWLS3NEAZANCNFSM4WHS77BQ
.

+1 - I think it's a sign of a healthy project to have these discussions.

+1 - I think it's a sign of a healthy project to have these discussions.

I'd like to block the RC tag on https://github.com/zmap/zlint/issues/553 being resolved.

I'd like to block the RC tag on https://github.com/zmap/zlint/issues/553 being resolved.

With https://github.com/zmap/zlint/pull/556 landed we're unblocked on this release if we want to push forward before figuring out a way to resolve #553.

With https://github.com/zmap/zlint/pull/556 landed we're unblocked on this release if we want to push forward before figuring out a way to resolve #553.

I'll put notes together this weekend and get on top of the release (have to study the release procedure real quick for it looks not especially off-kilter)

I'll put notes together this weekend and get on top of the release (have to study the release procedure real quick for it looks not especially off-kilter)

Pecked my way through the workflow for a tag and call for testing. However, I don't think I have post privileges to zlint-announcements (note that I'm not too familiar with Google Groups so I may have just missed the new post widget somewhere)

Pecked my way through the workflow for a tag and call for testing. However, I don't think I have post privileges to zlint-announcements (note that I'm not too familiar with Google Groups so I may have just missed the new post widget somewhere)

Thanks @christopher-henderson, it looks like you sorted out groups access? I see a post from you in there now.

Oh yeah, Zakir got me rolling on that.

@christopher-henderson Will you have a chance to cut the final tag shortly? Thanks!

@cpu precisely, I was going to cut the release this morning after a quick check that relative silence in response to the RC is normal (just to double check, I didn't want to cut and then panic that I was suppose to look out for testing response from ).

after a quick check that relative silence in response to the RC is normal

Very normal :-)
Thanks!

So I think I may have done something wrong. The v3.1.0 release only has two assets in it (it's missing the built binaries). I did faff around a bit and ended up making multiple drafts :slightly_frowning_face:

Would there be any issue in taking the binaries from v3.1.0-rc1 and manually dragging them into this one? There we no changes in the RC, however I don't know if there is something like version stamping into the resulting binaries that would cause there to be a difference.

Thanks @christopher-henderson

Would there be any issue in taking the binaries from v3.1.0-rc1 and manually dragging them into this one? There we no changes in the RC, however I don't know if there is something like version stamping into the resulting binaries that would cause there to be a difference.

That seems fine to me. AFAICT we don't have any fancy version embedding (but probably should).

I did faff around a bit and ended up making multiple drafts, that may have thrown off goreleaser slightly_frowning_face

Could you update the CONTRIBUTING.md docs to mention this issue about creating multiple drafts? It's definitely something we'll want to keep in mind for future releases.

There's something going on with v3.1.0 above and beyond the release artifacts. Updating ZCertificate is showing the dependency as an incompatible Go mod version:
zcertificate on  cpu-zlint-3.1.0 [$] via 🐹 v1.15.7
> go get<EMAIL_ADDRESS>go: github.com/zmap/zlint v3.1.0 => v3.1.0+incompatible

zcertificate on  cpu-zlint-3.1.0 [$!] via 🐹 v1.15.7
> git diff go.mod
diff --git a/go.mod b/go.mod
index 1093fa8..14efeb0 100644
--- a/go.mod
+++ b/go.mod
@@ -5,6 +5,7 @@ go 1.16
 require (
        github.com/sirupsen/logrus v1.7.0
        github.com/zmap/zcrypto v0.0.0-20201211161100-e54a5822fb7e
+       github.com/zmap/zlint v3.1.0+incompatible // indirect
        github.com/zmap/zlint/v3 v3.0.0
        golang.org/x/crypto v0.0.0-20201208171446-5f87f3452ae9 // indirect
        golang.org/x/net v0.0.0-20201209123823-ac852fbbde11 // indirect

@cpu it's my understanding that +incompatible means that the dependency in question is not of the module system that Go came up with a few years back. Did zceritificate update it's Go version to 1.16 as well? Maybe the whole system has been updated to want go.mod in the root of the repo (hence not picking up on ./v3/go.mod and thinking that we're not a module)?

Did zceritificate update it's Go version to 1.16 as well?

Yup, I landed PRs for this in zcrypto, zlint and zcertificate

Maybe the whole system has been updated to want go.mod in the root of the repo (hence not picking up on ./v3/go.mod and thinking that we're not a module)?

Ohhhhh! Your comment totally made me realize what I did wrong.....

go get<EMAIL_ADDRESS>
should be:

go get<EMAIL_ADDRESS>
The import is: "github.com/zmap/zlint/v3", the "v3" part is critical.
Sorry for the false alarm!!! PEBKAC error through and through.

Sorry for the false alarm!!! PEBKAC error through and through.

:facepalm: Confirmed w/ https://github.com/zmap/zcertificate/pull/26  We're all good!

:laughing:

PEBKAC

Not enough people in the world know this acronym.
As an side, I'll get on top of doing the super high tech, DevOps compliant, exercise of manually dragging and dropping a binary into GitHub.

As an side, I'll get on top of doing the super high tech, DevOps compliant, exercise of manually dragging and dropping a binary into GitHub.

:laughing: Thank you. We can close this issue afterwards I think.

Release v3.1.0


support Multi termvectors API

supports https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-multi-termvectors.html

That's looking really good, thank you for your support. :-)
Can you double check that all properties defined in the REST API spec for mtermvectors are available?
Also: Did you notice there's a generator that takes a REST API spec file as input and emits Go code for a service as output? You can see it in the generate-api branch. It makes creating missing services a bit easier than doing everything manually.

Thank you for your reply.

Can you double check that all properties defined in the REST API spec for mtermvectors are available?

Oh, OK. I'll see it.

Also: Did you notice there's a generator that takes a REST API spec file as input and emits Go code for a service as output? You can see it in the generate-api branch. It makes creating missing services a bit easier than doing everything manually.

It seems good. This PR implemented by my hands, I'll try it.

It's okay. No need to change it if all properties are there. The generator is simply for creating a skeleton for you.
I'll integrate it with the next release. Thanks for being a contributor.

Thank you for your comments. I've added some properties related elasticsearch/mtermvectors.json at 2.4 · elastic/elasticsearch .

So I've just added your PR. I've changed a few things; maybe you can double check if that makes sense.
Most changes are stylistic or fix a typo. However there's a significant change in verifying the request. In my understanding, it should be okay to call the /_mtermvectors endpoints in 3 possible ways (as described here and in the REST API spec.

Index and type: /{index}/{type}/_mtermvectors (no docs in body required)
Index but no type: /{index}/_mtermvectors (pass docs with type in the body)
No index and no type: /_mtermvectors (pass docs in the body)

What's not possible is 4. No index but a type. I've changed the Validate func accordingly and implemented a test for that behavior.
I've also changed the call in client.go to not require index and type, i.e. change
func (c *Client) MultiTermVectors(index, typ string) *MultiTermvectorService { ... }

... to ...
func (c *Client) MultiTermVectors() *MultiTermvectorService { ... }

I will release a new version of Elastic later this evening. If something's wrong, we'll fix it in the next release.

looks good to me. thanks! :)
2016/06/24 20:18 "Oliver Eilhard"<EMAIL_ADDRESS>
So I've just added your PR. I've changed a few things; maybe you can
double check if that makes sense.
Most changes are stylistic or fix a typo. However there's a significant
change in verifying the request. In my understanding, it should be okay to
call the /_mtermvectors endpoints in 3 possible ways (as described here
https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-multi-termvectors.html
and in the REST API spec
https://github.com/elastic/elasticsearch/blob/master/rest-api-spec/src/main/resources/rest-api-spec/api/mtermvectors.json
.

Index and type: /{index}/{type}/_mtermvectors (no docs in body
required)
Index but no type: /{index}/_mtermvectors (pass docs with type in
the body)
No index and no type: /_mtermvectors (pass docs in the body)

What's not possible is 4. No index but a type. I've changed the Validate
func accordingly and implemented a test for that behavior.
I've also changed the call in client.go to not require index and type,
i.e. change
func (c *Client) MultiTermVectors(index, typ string) *MultiTermvectorService { ... }
... to ...
func (c *Client) MultiTermVectors() *MultiTermvectorService { ... }
I will release a new version of Elastic later this evening. If something's
wrong, we'll fix it in the next release.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/olivere/elastic/pull/308#issuecomment-228320460, or mute
the thread
https://github.com/notifications/unsubscribe/AAd_pBZbdR_H2WK9YGY5uIJP7Am5SnyBks5qO7z2gaJpZM4I6SN0
.


docs: Add base pages for flank layers

Fixes #1509

architecture

presentation

cli

domain
data
adapter

Checklist

[ ] Update mkdocs.yml

I have to figure out how to serve markdown files for mkdocs, from outside of docs directory. I cannot find it in documentation. Seems to mkdocs forces to use only the docs directory which is a ridiculous design decision. I have to make sure.


NEC - PC Engine - TurboGrafx-16 duplicates (PC Engine Mini)

Processing NEC - PC Engine - TurboGrafx-16 (20230819-064535) in Retool 2.01.5 on default settings (and excluding everything except 'Games'), the following duplicates remain in the dat. It's probably related to some recent edits of these in no intro.
Fantasy Zone (Japan) (PC Engine Mini)
Fantasy Zone (USA)
Gradius (Japan) (PC Engine Mini)
Gradius (World) (Wii U Virtual Console)
Salamander (Japan) (PC Engine Mini)
Salamander (World) (Wii U Virtual Console)

Update: I see now, they changed capitalization from "mini" to "Mini", needs to be changed in https://github.com/unexpectedpanda/retool-clonelists-metadata/blob/7e9f945ae975ddc6778bacaf295a388362b3d750/config/internal-config.json#L253

Nice catch, thanks for the heads up :)
internal-config.json and the PCE metadata files have been updated.


Adjust existing and add additional badge types

Acceptance Criteria:

Please reference the Figma file for the specific parameters and token values.
Get the latest token JSON file from @twjeffery

All color values should have semantic token names

Ensure new properties are available to use in the Badge sandbox on the design system website.

Figma designs
Add the following "new" badge types:

Archived

Blue

Yellow

Pink

Violet

Aqua

Light green

All badges now have a border color that differs from the background color, ensure that this is implemented.

This includes adding borders to existing badges:

Dark
Light
Information
Warning
Emergency
Success

Undocument the following badge type:

"Midtone"

I believe this also includes the work detailed in #1517 , Can you check @Spark450 ?
If so, maybe copy the details from that story over here, and close that story.


Query language for filter

Fixes #1375
Implementation notes (Read this document to understand the query language syntax and API.)
TODO List

[x] Support API endpoint under workitems: /api/spaces/{spaceid}/workitems?filter[expression]={} (Pranav - redirect such API to search endpoint by adding given space_id in AND clause)
[x] Integration tests under controller (Baiju)
[x] Create a map of acceptable keys to coidesponding column/field in the database. (Pranav)
[x] Update the expression compiler to identify space_id column in work_items table (See workitem/expression_compiler.go function: isJSONField) (Konrad, fixed in 187e1c72ad6a07cada81e0f482bd908b4b705a84)

@baijum can we have a sample input to verify simplest possible query?
I know the structure(how it looks) but it will be great to mention it here too.
thanks.

@baijum snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1449-2

@baijum snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1449-3

@baijum snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1449-4

@baijum snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1449-5

@baijum snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1449-6

@baijum snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1449-9

@baijum snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1449-10

@baijum snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1449-11

@baijum snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1449-12

@baijum snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1449-13

@baijum snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1449-14

@baijum snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1449-15

@baijum snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1449-16

@baijum snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1449-17

@baijum snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1449-18

@baijum snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1449-19

From @kwk on chat on his latest changes:
I greatly simplified the Query struct by making Children a simple []Query.
Instead of manually writing the SQL Where clause and comparing against that we now construct a proper expected expression and compare against the outcome of that one.
We now use $NOT, $AND, and $OR and those are stored as constants Q_NOT, Q_AND, Q_OR.
generateExpression is now a member function of the Query struct.
Query construction is simplified by adding not specifying nil/false explicitly as these are automatically filled by Go.
The query language whitebox test is no longer a test suite but a simple set of test functions that can run in parallel and can be executed directly from within VSCode using the run test shortcut above each test. This greatly improves the development iteration speed.

I am working on  Create a map of acceptable keys to corresponding column/field in the database. part of the description.
After my change, the user will be using "area"/"iteration" keys and not "system.area", "system.iteration" keys.
API will consider query value as UUID.

@baijum snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1449-23

@baijum snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1449-24

@baijum snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1449-25

@baijum snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1449-26

yes @kwk so many nil to be passed. :disappointed:
I could think of only one way that is to club all function params in a struct and pass it but testing.* is generated by goa and not sure if we can customize/change that part!

@baijum snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1449-27

@baijum snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1449-28

@baijum snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1449-29

@baijum snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1449-30

@baijum snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1449-31

@kwk @baijum I have added few scenario-driven tests for search API here https://github.com/fabric8-services/fabric8-wit/pull/1449/commits/dc08ed9373a3346430aa60aeba6515e9c21ab8bb
I would like to know your thoughts.
Also, some white box tests were failing in Jenkins, I have fixed them here https://github.com/fabric8-services/fabric8-wit/pull/1449/commits/2ca67ca1ee78e723a2647095d2b35de51535e58e
Please review when available.
And there are some other tests failing in build
--- FAIL: TestSpacesSearchOK (0.07s)
	search_spaces_blackbox_test.go:181: with different values got equal description, wanted different description
--- FAIL: TestRunSearchSpacesREST (0.08s)

On local, when running this test individually it passes but when running make test-integration-no-covrage it fails.
Also on master branch, I was able to see that error after running make && make test-integration-no-coverage
And unit-tests are passing in all cases.

@baijum snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1449-32

thanks @aslakknutsen for https://github.com/fabric8-services/fabric8-wit/pull/1503/files
build is now passing :)

@baijum snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1449-33

Codecov Report

Merging #1449 into master will increase coverage by 0.13%.
The diff coverage is 78.24%.

@@            Coverage Diff             @@
##           master    #1449      +/-   ##
==========================================
+ Coverage   58.91%   59.04%   +0.13%
==========================================
  Files         121      121
  Lines       14282    14504     +222
==========================================
+ Hits         8414     8564     +150
- Misses       5212     5268      +56
- Partials      656      672      +16

Impacted Files
Coverage Δ

controller/workitem.go
80.88% <100%> (-0.16%)
:arrow_down:

controller/search.go
69.87% <55.17%> (-3.88%)
:arrow_down:

search/search_repository.go
80.29% <80.11%> (-0.15%)
:arrow_down:

workitem/expression_compiler.go
80.31% <83.33%> (-0.02%)
:arrow_down:

models/transaction.go
41.66% <0%> (-25%)
:arrow_down:

remoteworkitem/github.go
78.37% <0%> (-21.63%)
:arrow_down:

remoteworkitem/scheduler.go
46.93% <0%> (-16.33%)
:arrow_down:

Continue to review full report at Codecov.

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

@baijum snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1449-34

@baijum snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1449-35

@baijum snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1449-36

@baijum snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1449-37

@baijum snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1449-38

@baijum snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1449-39

@baijum snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1449-40

@baijum snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1449-41

@baijum snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1449-42

@baijum snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1449-43

@baijum snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1449-44

@baijum snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1449-45

@baijum snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1449-46


Update $nextjs-app.md

added 'use client' directive to form.tsx client component

If form.tsx is the client component, does it require the 'use client' directive at the top above the imports?

Thanks!


ENSCORESW-2744: remove dependent_xref when removing master

Requirements

Filling out the template is required. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion;
Review the contributing guidelines for this repository; remember in particular:

do not modify code without testing for regression
provide simple unit tests to test the changes
if you change the schema you must patch the test databases as well, see Updating the schema
the PR must not fail unit testing

Description
Using one or more sentences, describe in detail the proposed changes.
Remove all dependent_xref when the main xref is removed
Use case
Describe the problem. Please provide an example representing the motivation behind the need for having these changes in place.
Before loading a new set of xrefs into the core database, existing xrefs from updated sources are removed from the core database. This is done source by source, meaning that dependent sources are only deleted if there is an update to that source. As their mapping depends on the master source, they should be removed at the same time.
Benefits
If applicable, describe the advantages the changes will have.
If a dependent source is not updated but its master is, we do not end up with orphan entries. This also means we remove older mappings more regularly.
Possible Drawbacks
If applicable, describe any possible undesirable consequence of the changes.
The query is not optimised and can take a while to run on the server. It also leaves the xref entries in the xref table as they can be dependent of multiple sources.
Testing
Have you added/modified unit tests to test the changes?
This was tested on gorilla which failed last release due to a single PDB that was left as an orphan. It is left as an orphan before the code change but is cleanly removed with this update. This was also run on a hundred species to check for regression.
If so, do the tests pass/fail?
The identified edge case is fixed and no new regressions are detected.
Have you run the entire test suite and no regression was detected?
NA

It is not a bad suggestion. Currently, they are basically treated as unmapped entries, so they do not really harm anything, but it would be cleaner to get rid of them eventually.
I will put a ticket in for this but would rather avoid including it into this change as it would need to be done as a post-processing stage (or run the same query dozen of times as we got through each source)

Coverage remained the same at 82.605% when pulling 667e4c421e666d16f35f1a5c6801a3ba7c065145 on bugfix/cleanup_dependent into 962bf85971fd5ec9bf9243e1e745976a9ff68456 on master.

luckily, we got rid of dependent dependents when we removed GO from the xref pipeline. If such a scenario ever happens again, we should spot it quickly as a number of unlinked entries will appear