Use documentElement.clientWidth/Height as viewport

On Android, window.innerHeight/Width does not correspond to the
actual viewport as seen by user and WebDriver.
jQuery also uses this for detecting viewport.

@j0tunn @scf2k

:ok:


PR - Add 'hide' support and a new meta-data option to List2need directive

Added the support for "hide" option to affect the hidden status to all requirements in the list. This allows to easily create a list of requirements that could be only presented as a table in the final output.
.. list2need::
      :types: req
      :tags: A
      :hide: True
      * (NEED-A) Login user
      * (NEED-B) Provide login screen
      * (NEED-C) Create password hash
      * (NEED-D) Recalculate hash and compare

   .. needtable::
      :types: req
      :tags: A
      :style: table
      :columns: id, title, content, links

this example is added in the documentation
The PR also add a new meta-data option to give the ability to set meta-data (including extra defined custom option to all elements in the list)
.. list2need::
      :types: req
      :tags: A
      :meta-data: validation="Test, Review of Design", status="open"
      * (NEED-A) Login user
      * (NEED-B) Provide login screen
      * (NEED-C) Create password hash
      * (NEED-D) Recalculate hash and compare

The PR is also looking already quite good, just 1-2 minor comments to the code. And 1-2 test cases are missing :) Can you add them? Then I will give it a go 👍
If any help is needed, just let me know.

I would like to know if these is a way to perform the tests based on the needs.json output instead of parsing/inspecting the html output. At this level, I don't want to test if the "hidden state" or "all options" are properly rendered, but I want to focus on "if the needs in the list have these global options attached to them (and the same with the hide status)

I would like to know if these is a way to perform the tests based on the needs.json output instead of parsing/inspecting the html output. At this level, I don't want to test if the "hidden state" or "all options" are properly rendered, but I want to focus on "if the needs in the list have these global options attached to them (and the same with the hide status)

For sure you can also build the test-projects with the "needs" builder to check the needs.json output.
And we also have some test cases, where the internal data (stored in the env var) is directly checked.
So it is open to you, to choose the best data element to check.

I fixed some bugs and added tests for both features (list_global_inputs and hide)

Heya, the whole list_global_options I feel is overcomplicating things, and also negates the need for a separate hide option (or in-fact tags etc). Just do this:
.. list2need::
   :need-options:
      :hide:
      :tags: a,b,c
      :status: open
      :validation: Test, Review of Design

then there is no need for any complex regex parsing; you just basically take the whole block and insert it into the jinja (removing top/bottom blank-lines)

I though about something like that, I'm just a bit concerned about the fact I've never seen "nested" options elsewhere. So, I though that adding ":hide:", ":tags:", ... would be more the same syntax than with the ..need / ..req directive.
What do you think ?

Im just a bit concerned about the fact I've never seen "nested" options elsewhere.

list_global_inputs are nested options, just in a completely bespoke format 😅
How I said above is the way to go; it is much clearer to the user what options will be parsed through to the needs


zero 2 w compatability

I tried using a zero 2 w,  raspberry states the 2 is backwards compatible with the zero. I'm assuming that it doesn't work with the software as I cant get it to boot with the chattersync software installed, has anyone else used a zero 2 with chattersync ?

I see you closed the issue, did you find anything out? I haven't had a chance to check on this yet.
P

Hi Pete,
yes, I found that it works well with the zero 2.
I'm not familiar with git hub or how the pi worked.
I had made a mistake when loading the files.
I loaded the files in git hub and not the linked file in the image folder.
What through me a curve ball was that the image loader did not give an error so I assumed I had transferred the operating system correctly.
Once I used the correct image it went well.
Thank you for releasing this and all your efforts with this, its a great tool you've created.


Navbar link not highlighting correctly

On vercel deployement, When I click on Appearances it highlights Home in navbar It should highlight Appearances.

It is easy fix.
I want to work on it .

please assign me with this task @aslams2020


Extra Study + User Synonyms

Added a gif for user synonyms in reviews and a brief explanation.
Updated the Extra Study picture and included a description of the burned items section.

Changes proposed in this pull request:

Can you add a ? at the end of the title 'What's considered a Burned Item' to be consistent with the other headers?

I've made the change now and added the missing question mark.


big endian start bit offset is already handled outside of kcd.py

This was changed for the dbc backend in 18b4cc31efb18f5a3f313de4f061d84b911f1123 but was not changed in the kcd backend.

I'm a little bit confused because of the tests which fail.
I assume the major problem here is the offset of big endian values. The kcd spec says:

Least significant bit offset of the signal relative to the least significant bit of the messages data payload.

I'm not quite sure whats the least significant bit of the message data payload, but from my understanding the offset for big endian values is calculated using the 8 * idiv(x; 8) + 7 - mod(x; 8) formulae.
However that would mean the_homer.kcd included in this repo is wrong, as A, B and C collide. Maybe it should be this instead:
<Signal name="A" offset="7" length="17" endianess="big"/>
<Signal name="B" offset="22" length="1" endianess="big"/>
<Signal name="C" offset="21" length="5" endianess="big"/>

Which would result in 23 bits to be interpreted like this:
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
A A A A A A A A A A A  A  A  A  A  A  A  B  C  C  C  C  C

So maybe the test file is wrong?

Is there a bug in the KCD parser, or should this be closed?


[Support]: I'm very lost

Describe the problem you are having
I installed the addon and went to start it and that's when i started having issues. I noticed that it required a /config/swatch.yml file so i created one and then it wanted it to be filled in so I found code from someone because I want to make sure it works before changing all the information and putting in the work. I keep trying to start it but nothing. Please help I'm new to the config file stuff.
Version
3.1.0-2717ec6
Swatch config file
# to one camera or common between many / all cameras
objects:
  # REQUIRED: Name of the object
  trash_can:
    # REQUIRED: the list of color variants that this object can be detected as. Useful for
    # different lighting conditions
    color_variants:
      # REQUIRED: the name of the color variant
      default:
        # REQUIRED: the lower R, G, B values that are considered a potential match for the
        # color variant of the object.
        color_lower: 70, 70, 0
        # REQUIRED: the upper R, G, B values that are considered a potential match for the
        # color variant of the object.
        color_upper: 110, 100, 50
        # OPTIONAL: the time range for when this color variant is allowed
        # NOTE: make sure that /etc/localtime is passed to the container so it has valid time
        time_range:
          # OPTIONAL: Color variant is valid if current time is > this 24H time (Default: shown below).
          after: "00:00"
          # OPTIONAL: Color variant is valid if current time is < this 24H time (Default: shown below).
          before: "24:00"
    # OPTIONAL: the min area of the bounding box around groups of matching R, G, B pixels
    # considered a true positive. This is not recommended to be set as a super small amount
    # could be a false positive. (Default: shown below)
    min_area: 1000
    # OPTIONAL: the max area of the bounding box around groups of pixels with R, G, B
    # values within the bounds to be considered a true positive (Default: shown below).
    max_area: 100000
    # OPTIONAL: the min ratio of width/height of bounding box for valid object detection (default: shown below).
    min_ratio: 0
     # OPTIONAL: the max ratio of width/height of bounding box for valid object detection (default: shown below).
    max_ratio: 24000000
    # REQUIRED: Define list of cameras that will be used for color detection.
cameras:
  # REQUIRED: Name of the camera
  front_doorbell_cam:
    # OPTIONAL: Frequency in seconds to run detection on the camera.
    # a value of 0 disables auto detection (Default: shown below).
    auto_detect: 0
    # OPTIONAL: Configure the url and retention of snapshots. (Default: Shown Below)
    snapshot_config:
        # OPTIONAL: but highly recommended, setting the default url for a snapshot to be
        # processed by this camera. This is required for auto detection (Default: none).
        url: "http://ip.ad.dr.ess/jpg"
        # OPTIONAL: Whether or not to draw bounding boxes for confirmed objects in the snapshots (Default: shown below).
        bounding_box: true
        # OPTIONAL: Whether or not to save a clean png of the snapshot along with the annotated jpg (Default: shown below).
        clean_snapshot: true
        # OPTIONAL: Whether or not to save the snapshots of confirmed detections (Default: shown below).
        save_detections: true
        # OPTIONAL: Whether or not to save the snapshots of missed detections (Default: shown below).
        save_misses: false
        # OPTIONAL: Variations of snapshots to keep. Options are all, mask, crop (Default: shown below).
        mode: "all"
        # OPTIONAL: Number of days of snapshots to keep (Default: shown below).
        retain_days: 7
    # REQUIRED: Zones are cropped areas where the object can be expected to be.
    # This makes searching / matches for efficient and more predictable than searching
    # the entire image.
    zones:
      # REQUIRED: Name of the zone.
      street:
        # REQUIRED: Coordinates to crop the zone by.
        # NOTE: The order of the coordinates are: x, y, x+w, y+h starting in the top left corner as 0, 0.
        coordinates: 225, 540, 350, 620
        # REQUIRED: List of objects that may be in this zone. These correspond to
        # the objects list defined previously and are matched by name.
        objects:
          - trash_can

Relevant log output
[2023-11-07 14:26:05,534]: INFO - Importing SwatchApp Config
[2023-11-07 14:26:05,536]: INFO - Verified SwatchApp Config
Starting migrations
[2023-11-07 14:26:05,581]: INFO - Starting migrations
There is nothing to migrate
[2023-11-07 14:26:05,630]: INFO - There is nothing to migrate
[2023-11-07 14:26:05,634]: INFO - Starting snapshot cleanup
[2023-11-07 14:26:05,635]: INFO - Starting Detection Cleanup

Any other information that may be helpful
No response

I managed to find the Swatch page "http://<IP_ADDRESS>:4500/dashboard" and I changed the url: to "rtsp://<IP_ADDRESS>:554/ucast/11" but still no live feed shows? what am i doing wrong

swatch does not support live feeds, I think there may be some misunderstanding on how swatch works

Oh how does it work? I thought that I could have a camera detect a certain color in an area and use that as a sensor?

It just pulls snapshots from the camera either when a command is sent or on a regular interval (example config shows it every 5 minutes)

oh okay. I tried using the color playground and enter my image url but when i get to the submit image button and click it it does nothing. Am I doing something wrong?


removes setup_requires from setup.py

As discussed before we can remove setup_requires from setup.py and just install flake8 inside travis ci container.

I signed it !


Make apigatewayv2 resource name fields consistent with other ACK controllers

apigatewayv2 resources have fields like 'DomainName', 'APIId', which ideally should be renamed to 'Name' and 'Id'
This is the standard across other service controllers, ex: 'BucketName' is renamed to 'Name' in s3-controller

Changing field names will break backward compatibility. Closing.


Use dependencies.yaml to generate environment files

Updates MRC to use dependencies.yaml for the source of truth for environment files, and adds a pre-commit hook to ensure the environment files get generated before commit. Also adds the pre-commit hook as a check in CI to ensure we catch missed changes.

/merge


helm: prevent failure on 1.17 upgrade from 1.16 due to nil values in templates

Please ensure your pull request adheres to the following guidelines:

[x] For first time contributors, read Submitting a pull request
[x] All code is covered by unit and/or runtime tests where feasible.
[x] All commits contain a well written commit description including a title,
description and a Fixes: #XXX line if the commit addresses a particular
GitHub issue.
[x] If your commit description contains a Fixes: <commit-id> tag, then
please add the commit author[s] as reviewer[s] to this issue.
[x] All commits are signed off. See the section Developer’s Certificate of Origin
[x] Provide a title or release-note blurb suitable for the release notes.
[x] Are you a user of Cilium? Please add yourself to the Users doc
[x] Thanks for contributing!

Previously, upgrading from helm chart 1.16 to 1.17-dev would fail because some values would evaluate to nil due to changes in the default values, printing errors like:
Error: UPGRADE FAILED: template: cilium/templates/cilium-configmap.yaml:354:14: executing "cilium/templates/cilium-configmap.yaml" at <.Values.bpf.events.default.rateLimit>: nil pointer evaluating interface {}.rateLimit

This change adds () to such values to prevent nil pointer errors.

@kema-dev can you provide the steps you are using to perform the upgrade?

Well, was doing this

kind create cluster --config ./path/to/kind-config.yaml (basic config with 2 masters 4 workers)
helm upgrade --install --create-namespace --namespace kube-system --repo https://helm.cilium.io cilium cilium --version 1.16 --values ./path/to/cilium-values.yaml (whaterver config)
helm upgrade --install --create-namespace --namespace kube-system cilium path/to/cilium/install/kubernetes/cilium --values ./path/to/cilium-values.yaml (cilium repo cloned locally, same cilium config)

Just tried, can't reproduce, works just fine. Sorry for the inconvenience, this can be closed (letting you do it as you maybe have special procedure)
Enjoying cilium alot though !

Just a FYI in case other runs through the same issue.
I got the same message (coming from main at 5810af7e31e8561432a0794979ddcae79fe55a4c two weeks ago), the upgrade --install --reuse gave
Error: UPGRADE FAILED: template: cilium/templates/hubble/tls-provided/metrics-server-secret.yaml:1:55: executing "cilium/templates/hubble/tls-provided/metrics-server-secret.yaml" at <.Values.hubble.metrics.tls.enabled>: nil pointer evaluating interface {}.enable

and providing the hubble.metrics.tls.enabled gave
Error: UPGRADE FAILED: template: cilium/templates/cilium-agent/daemonset.yaml:54:48: executing "cilium/templates/cilium-agent/daemonset.yaml" at <include (print $.Template.BasePath "/cilium-configmap.yaml") .>: error calling include: template: cilium/templates/cilium-configmap.yaml:359:14: executing "cilium/templates/cilium-configmap.yaml" at <.Values.bpf.events.default.rateLimit>: nil pointer evaluating interface {}.rateLimit

However, doing without --reuse flag was the key for me.


Support test and set of KV via vm listener

Modified the disk_detach_int code path to include optional key, value params. The KV will be written with the given dict only if the current KV data matches the given key, value pair.
Ensuring a test-and-set of the KV in specific scenarios - right now just the VM listener.

Fixes #1621


Added Red Black Tree data structure

Added Red Black Tree data structure with its implementation and brief background of what it is and why we use it.

@kibergrad
Great work 💯
You can follow me and star this repo for further updates.
Have fun 🙌

@ShehrozIrfan thanks
Sure I am gonna follow and star this repo, this repo is going to become a good collection of programming resources for others.
Thanks :)


Pinia settings panel is not loaded immediatly when current page does not have any useStore

Reproduction step:

goto some page does not include any useStore
open devtools pinia page (settings panel does not appear)
goto some page include useStore
refresh devtools
settings panel appears

Record:
https://github.com/user-attachments/assets/ca32f8aa-fc05-4194-91c2-2020fb07e9fd

Yes, I noticed this, but I guess it has something to do with the design of the pinia devtools plugin, and maybe devtools v6 as well. But anyway, I think it makes sense to register pinia and let it come out. So if we confirm that it is the design problem of pinia devtools plugin, I think we can submit PR for it.

Yes, I noticed this, but I guess it has something to do with the design of the pinia devtools plugin, and maybe devtools v6 as well. But anyway, I think it makes sense to register pinia and let it come out. So if we confirm that it is the design problem of pinia devtools plugin, I think we can submit issue or PR to pinia repo for it.

Pinia will register devtools once they have at least one store, see
https://github.com/vuejs/pinia/blob/128f4352d2c18c0992cbab67b1a9261ff8a766ca/packages/pinia/src/store.ts#L731C8-L744
So plugin settings will update when somewhere has useStore calls.
But applet does not subscribe the plugin changes, should we support it?

Upstream issue, related https://github.com/vuejs/pinia/issues/2818


Add Spec revision-2 for server side support

I will merge after 2 more people review

(out of the people i requested review from)

$schema can be omitted right

Yes but it's there to let people know which schema to use

ok

@EmmaTheMartian @Hellscaped Can one of you review this PR?

Coolio, I see no other problems or nitpicks

( @EmmaTheMartian remember to approve the changes as just resolving the threads doesn't automatically do that)

I don't know if I can on mobile and I'm not at my PC

Turns out it was just a hidden button :P

I think I can merge the PR now


Can't disconnect a path

I have a path connected to the tram track. I wanted to disconnect it but I couldn't because
"This can't be disconnected because it connects members of a relation.".
Indeed there are many tram relations on the tram track. iD doesn't allow me to disconnect it, but I can remove that shared node without any problem.

However, it can be ommited by adding a node on a line, split it, and remove that connected line. That's the only possibility I know now, which doesn't spoil relations.
Is it a bug, feature, or is possible to disconnect it somehow? If I can delete a node, why can't I disconnect it?

I believe this is to serve iD's purpose: To not damage other users' data.

@maro-21 Can you try to select the path first and then shift right-klick on the connecting node? Are you offered the operation disconnect?

Can you try to select the path first and then shift right-klick on the connecting node? Are you offered the operation disconnect?

I tested the scenario and this should work. Disconnecting the node alone would disconnect all the ways, so iD is blocking you from disconnecting the railways (which are in the same relation). If you only want to disconnect the path, you have to select that along with the node.
Theoretically we could allow iD to disconnect the ways which aren't relation members. I'm not sure if this would be confusing.

Theoretically we could allow iD to disconnect the ways which aren't relation members. I'm not sure if this would be confusing.

I think it would. However, I think a hint towards the workaround in the error message would be in order. Along the lines of "Try to Shift+Select specific objects to disconnect" -- it's difficult to formulate a short but understandable message.

Answering my own question: I can disconnect this path by selecting the path, holding Shift, clicking the node, then clicking D. Then only the path is disconnected from the tram track, and the rails are still connected. This is not a bug, so I'm closing the issue.


Support for windows

Trying to address #14

Simply setting replica and rank to 1 which import of distributed.get_world_size failed.

@veralauee

Currently testing on windows 10. Will update results here.

Hi @DominicDataScienctist ！We are grateful for your efforts in helping improve mmfashion open-source project during your personal time.
Welcome to join OpenMMLab Special Interest Group (SIG) private channel on Discord, where you can share your experiences, ideas, and build connections with like-minded peers. To join the SIG channel, simply message moderator— OpenMMLab on Discord or briefly share your open-source contributions in the #introductions channel and we will assist you. Look forward to seeing you there! Join us ：https://discord.gg/UjgXkPWNqA
If you have a WeChat account，welcome to join our community on WeChat. You can add our assistant ：openmmlabwx. Please add "mmsig + Github ID" as a remark when adding friends：）
Thank you again for your contribution❤


[BUG] Dark theme doesn't work anymore

Right now, the dark theme doesn't work anymore.
See the print below

My SO: Ubuntu linux 20.04

okay. thanks for this report.
An update will be pushed this week to rectify this.
Thanks and warm regards.
On Mon, Jun 29, 2020 at 3:04 PM Guilherme Viana<EMAIL_ADDRESS>wrote:

My SO: Ubuntu linux 20.04
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/olubunmitosin/whatsapp/issues/3#issuecomment-651144338,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKDKYNGVGZH335JU5CXZ23LRZCNQLANCNFSM4OLH3XSA
.


declare t and Differential(t) at top-level scope

These only need to be declared once afaict.

Is there going to be a performance hit from declaring @parameters t, without specifying it as a const?


Update test case files for upcoming LISF 7.3

@jvgeiger was this issue resolved by #671 ? If not, what updates are needed?

@jvgeiger was this issue resolved by #671 ? If not, what updates are needed?

Yes.
I will close this issue.

Yes.
I will close this issue.


"The requested crate does not exist" message if a version does not exist

"The requested crate does not exist" is the message if you try to load up docs for a crate that exists, in a version that does not. Could just use a small tweak in how it reports the error.

Error messages definitely needs improvements.
docs.rs is also giving same error message when an author not exists, i.e: https://docs.rs/releases/non-existent-author

Triage: This should be an easy fix, error messages in general do need improvement still

Mentor:

The current error is Nope::CrateNotFound which is accurate but still not a good error. As of now, a better error doesn't exist, so we'll make it
Go to src/web/error.rs and find the Nope enum. Add a new variant named VersionNotFound, this will be our new error
Update the Display implementation for Nope and add the new variant with a helpful message
Docs.rs uses iron for its web framework and iron operates off of a hander system, where individual objects (structs, enums, etc.) define their behavior as the responder to a web request by implementing the Handler trait. The default page that the user sees is created by using the Page struct. Add the VersionNotFound variant to Nope's handler.
Within the VersionNotFound branch of the handler, construct a new page

Page::new("the requested crate version does not exist".to_owned()) Create a new page with the requested crate version does not exist as the content
.set_status(status::NotFound) Set the status of the response to 404
.title("The requested version does not exist") Set the title of the page
.to_resp("error") Render the page using the error template

Go to src/web/rustdoc.rs and change the error to the new Nope::VersionNotFound

I'll start working on this. Thank you @Kixiron for the detailed description of what to do :blush:

Mhh, doesn't seem to be as easy as it first looked. As a start, I'm not even able to reproduce the error.
Opening any of the following

https://docs.rs/non-existent
https://docs.rs/sqlx/42
https://docs.rs/releases/non-existent-author (example from above)
all produce a 404 page with the content

The requested resource does not exist
no such resource

which maps to to the Nope::ResourceNotFound enum variant. So I was not able to get a Crate not found message but always ended up with a no such resource. Due to this I believe the above fix will not suffice, since there seems to be another bug.
I tried tracking down if the Nope::CrateNotFound enum is even constructed (Yes!) and where it gets lost. I believe the code responsible for this is
https://github.com/rust-lang/docs.rs/blob/bfa6adaabd3081be8e5d0f93d498b93d167469b9/src/web/mod.rs#L182-L232
It seems like the error might lie in the chaining of the handlers, the branch in line 189 is not entered even if a CrateNotFound is constructed earlier.

I think that handler shouldn't be modifying the error at all, just logging it. If you remove the let err = bit, does it work?

The let err = ... bit is necessary because that error is passed to the  Self::chain call at the end. I'm not quite sure what the chain does though.
I'm fairly sure that the issue is the chaining of the handlers with or_else. Since the router_handler (and apparently the database_file_handler as well) will return a Nope::CrateNotFound, static_handler is tried, which returns an Os error wrapped in an IonError which gets converted to a nope::RessourceNotFound. So even if I were to add a different variant to Nope that would just be ignored since this method will look for a static file if the shared_resource_handler, router_handler and database_file_handler return a status: status::NotFound error. Assuming that the VersionNotFound variant would also come with a status::NotFound.

The let err = ... bit is necessary because that error is passed to the Self::chain call at the end. I'm not quite sure what the chain does though.

You can use e in the chain call instead.

even if I were to add a different variant to Nope that would just be ignored since this method will look for a static file

Hmm ... could you switch the order so that the router_handler always comes last? That way any 404 errors would come from it, not from other handlers.
There's probably a more robust way to do this but this should enough to fix the problem, if you think of a better way do let me know though.

Yes, changing the order of the handlers somewhat solves the problem for now. I guess it's okay since the router_handler returns the most specific errors at the moment and there is no harm in dropping the earlier errors. Should someone introduce more specific user facing error in the other handlers however, they will likely get swallowed by the router_handler at the end...
Not an ideal situation but at the moment I can't think of an easy more robust solution.
It should be noted that changing the order of the handlers might change the performance of the service in production.
PR #1043 contains a bug-fix for the handler order issue and introduces the VersionNotFound error.

It should be noted that changing the order of the handlers might change the performance of the service in production.

It will, but it will change it for the better ;) since it's only doing expensive database lookups after the cheap things fail. Thanks for thinking about it though!
In any case it should only be a minor difference since almost all requests are to the shared resource handler or router, I think only /favicon.ico is handled by the static_handler and the database handler is empty in prod.

Should someone introduce more specific user facing error in the other handlers however, they will likely get swallowed by the router_handler at the end

This is true, but I don't foresee more specific errors: all the previous handlers are for static files.

Oops, seems like my fix to this produced some errors in prod which were not visible in testing #1051 . PR #1052 reverted the change responsible for this which again breaks the message.
One way of dealing with this problem could be to keep the order of the handlers reverted to in #1052 but propagate the errors differently, such that the user will see the one returned by the route_hanlder should every handler return a 404 instead of the error from the last handler.
If that seems like a sensible thing and no one has an idea how to solve the problem more elegantly, I'd be happy to send another PR :)

Yeah I misunderstood what was going on - database_handler is misnamed, it should say storage_handler, because it goes through S3 in prod.

propagate the errors differently, such that the user will see the one returned by the route_hanlder should every handler return a 404 instead of the error from the last handler.

That seems reasonable - I tried that and ran into some edge cases where it didn't quite work (requesting /x.js), but it seems fixable.

I don't think #1090 fixes this, it changed "the requested resource does not exist" to "the requested crate does not exist", but I don't see any "the requested version does not exist" messages.


[Rog Ally][ChimeraOS][V43.1] Buttons stop working when opening virtual keyboard

Problem:
Non-standard Xbox buttons stop working, and the issue can only be resolved by restarting a Rog Ally.
(Rog Button and guide)
How to reproduce:
Open the virtual keyboard in-game or in the configuration.
Observe that the non-standard Xbox buttons have stopped working.
Steps taken so far:
I have attempted to resolve the issue by restarting a service, which sometimes works, but not always.
I have checked the systemd service logs, but I couldn't notice any abnormalities.
Sorry if this text is confusing, English is not my first language.

Thanks for the issue, let me reproduce it on my device...

Hi. I see the same issue. The two front buttons that are mapped stop working if the virtual keyboard opens. We have to restart the service somehow to fix the issue.

Happens here too (Gentoo install on ROG Ally), using ChimeraOS gamescope and gamescope-session. Just bringing OSK up (by clicking the search button, for instance) disables the special keys. A service restart makes then work again.


chore:reword content for contributors

This PR changes the wording and the structure of the CONTRIBUTING and README. The idea is to make those already great content more friendly to our potential contributors, as well as adding new key elements for a new contribution.

:ship:


[stable/datadog] ADD UDS socket for trace agent

What this PR does / why we need it:

Add DD_AC_INCLUDE and DD_AC_EXCLUDE to all containers
Add "Unix Domain Socket" support in trace-agent
Add new parameter to specify the dogstatsd socket path on the host
Fix typos in values.yaml
Update "tags:" example in values.yaml

Which issue this PR fixes

fixes #22375, fixes #21586, fixes #22030

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[ ] DCO signed
[ ] Chart Version bumped
[ ] Variables are documented in the README.md
[ ] Title of the PR starts with chart name (e.g. [stable/mychartname])

/lgtm

/lgtm


PHP8 Support

Coverage decreased (-0.2%) to 99.835% when pulling c54c811aed48f6c554c13b27d47cdce1849fbd9c on funct:php8 into 349d9df06b0b97321240854be8640238bc8bbfad on prooph:master.

This should be ready now @codeliner @prolic


3.0 Migration: Elasticsearch Clients and Templates

What needs to be done
Provide automated migration recipe(s) for mitigations of

#688

where possible.
:warning: Please read Spring Boot 3 Upgrade Report Contribution Guideline :warning:

Hi @fabapp2
I will like to pick up this enhancement.

Hi @ravig-kant !
Could you do #688 too (first)? I didn't look into it yet so the research would be on you too :)
I am not very responsive but @sanagaraj-pivotal should be able to provide help.


removeUnknownsAndDefaults removes fill="none" from path

Describe the bug
Using the removeUnknownsAndDefaults plugin would remove instances of fill="none" from path elements
This is unexpected as it's neither a default or unknown value
To Reproduce
Have an svg like:
<svg width="24" height="24" viewBox="0 0 24 24" fill="black" xmlns="http://www.w3.org/2000/svg">
  <path fill-rule="evenodd" clip-rule="evenodd" d="M0 0h24v24H0z" fill="none"/>
  <path fill-rule="evenodd" clip-rule="evenodd" d="M3 17.25V21h3.75L17.81 9.94l-3.75-3.75L3 17.25zM20.71 7.04c.39-.39.39-1.02 0-1.41l-2.34-2.34c-.39-.39-1.02-.39-1.41 0l-1.83 1.83 3.75 3.75 1.83-1.83z" />
</svg>

process it using the removeUnknownsAndDefaults plugin
Observe fill="none" is removed from the first path element

Expected behavior
fill="none" should not be removed
Screenshots
Without fill="none"

With fill="none"

Desktop (please complete the following information):

SVGO Version: ^2.7.0 => 2.7.0
NodeJs Version: 14.18.1
OS: Windows 10 10.0.19044

Hey! I'm unable to reproduce the issue in both SVGO v2.7.0 with Node.js v14.18.1, nor with the latest version of SVGO (v3.0.5).
The [fill=none] attribute remains and the SVG renders fine in both cases.
Can you still reproduce this? If so, could you share the exact config you're using?


useGoogleLogin | no success, error or response for google child profile

working fine for normal google account.
When I am signing in to chrome with child profile and when a login() is called, there is no sign of activity from the library, i.e. as stated, the onSuccess and onError do not get called.
const GoogleLogin = () => {
  const handleSuccess = (codeResponse: any) => {
    console.log('Login Success:', codeResponse);
  }

  const handleError = (error: any) => {
    console.log('Login Failed:', error);
  }

  const login = useGoogleLogin({
    flow: 'auth-code',
    onSuccess: handleSuccess,
    onError: handleError
  })

  return (
    <>
      <div>
        <Button onClick={() => login()}>
          Sign in with Google 🚀{' '}
        </Button>
      </div>
    </>
  )
}

I am facing the same issue. It was working fine some days ago. But now google sign in dialog window disappear after clicking on google account, nothing show in console and not called the onSuccess and onError function.

Same happens to if you use ux_mode="redirect"

Yes this seems to be broken at the moment.  I'm also unable to produce this working on Google Chrome.

Try to add http://localhost/ to the authorized origins in the Google cloud console

Was facing the same problem. It does not show anything in Brave browser but I tried in Chrome and it was working fine. So, just try in different browsers.


Revert "Add dependency managment."

This reverts commit 76298083e1c2ac29f2b79938c9184a5966289e6c.
Dependencies are now being managed by the parent pom.

Integration tests: https://beta-jenkins.mcc.schubergphilis.com/job/cosmic/job/0002-tracking-repo-branch-build/159/


ImportError: No module named conv_bc01

Ubuntu 14.04 LTS. CUDA 7.5.
However, I installed cudarray without cuda support.
And after installation I got:
grinya@mypc:~/cudarray$ python
import cudarray
CUDArray: CUDA back-end not available, using NumPy.
Traceback (most recent call last):
File "", line 1, in
File "cudarray/init.py", line 40, in
from .numpy_backend import *
File "cudarray/numpy_backend/init.py", line 2, in
from .nnet import *
File "cudarray/numpy_backend/nnet/init.py", line 3, in
from .conv_bc01 import *
ImportError: No module named conv_bc01
But the file in the directory "cudarray/numpy_backend/nnet" does exist. I do not understand this error.

Could the installation have failed? I assume you have run python setup.py --without-cuda install. Make sure a recent version of Cython is installed.

I do not think so, because during installation there were no errors.
Yes, I used sudo python setup.py --without-cuda install.
I have latest Cython. Version 0.23.4

Ok, I'll try it out then! :)

Here is a log  of installation

Thanks for the info, I can't reproduce the error. Try uninstalling CUDArray with pip uninstall cudarray (try multiple times to make sure all installations are removed). Then clean temporary CUDArray files with python setup.py clean. Finally, try installing again. If this doesn't work, you might want to try another Python distribution. I recommend Anaconda Python.

Well, I used Anaconda Python 2.7.
pip uninstall cudarray tells that Cannot uninstall requirement cudarray, not installed
Just tried reinstalling after python setup.py clean. The same problem.

I see! Can you try installing without sudo?

Oh, smth different. At least I can see my Anaconda path in log:
grinya@grinyamipt:~/cudarray$ python setup.py --without-cuda install
/home/grinya/anaconda2/lib/python2.7/site-packages/setuptools-19.2-py2.7.egg/setuptools/dist.py:284: UserWarning: Normalizing '0.1.dev' to '0.1.dev0'
running install
running bdist_egg
running egg_info
writing requirements to cudarray.egg-info/requires.txt
error: [Errno 13] Permission denied: 'cudarray.egg-info/requires.txt'

This is probably because the previous installation was with sudo. Make sure to uninstall CUDArray first (uninstall with sudo, that is).

Oh. Tried as you said. The same problem. Here is log

I do not understand, but running python from a different directory (instead of cudarray's directory) works fine. And there is no ImportError =)

Great! The reason why it didn't work was because Python tried to import cudarray from your working directory. This failed as the cythonized files are stored in a separate build directory. Another time If you want to store cythonized files along with your python code you should install with python setup.py develop.

Thank you!


Python: Memory Store supports a hybrid search in weaviate over nearest Vector matches which the current implements

Hi folks!
I'm experimenting features of a long term memory store with weaviate. Currently, it supports the nearest vector search (See: https://github.com/microsoft/semantic-kernel/blob/main/python/semantic_kernel/memory/semantic_text_memory.py#L152) all over the storages but as far as I know, some of vector databases such as weaviate are capable of "hybrid" search. So, I would memory store to have hybrid search to extend a searching ability.
I want to hear the voice of folks.

I commented on the PR! Overall I think it's good to have and should be supported. There's the Kernel Memory project (https://github.com/microsoft/kernel-memory) that @dluc @crickman and others are building but it'll likely take some time before a Python client supporting hybrid search is available. Adding this inside the Text Memory Skill could be a good interim solution

I have been looking on the Kernel Memory and looking forward to supporting a Python client! Any chances to contribute it, I will!
In the mean while, I hope #3329 can be a short time solution as you mentioned.

This will come in with the updated memory connector abstraction soon.


Starting error

syncthing.log
SyncTrayzor.log

Upgrade to the latest version.

Upgrade to the latest version.


add parameterizable duration to retrieve data from prometheus

Note: that's the last thing missing to be able to fix back the PR on prometheus side

For the name, yeah I'm agree it's not a super good one. But so far I don't have better. If you have a better one I will replace it :).
Maybe the weekend will help to find it.
Why not to have a duration instead.

How about MetadataLookbackInterval?

Here we go, it should be a bit better now

We could also store the look back interval in the metadataService instance and change it the same way URLs are changed.
This keeps complexity out of the langserver package and prevents the race condition mentioned above.

I'm not really in favor of doing the same than the prometheus URL. It doesn't require the same completexity and I prefer that the metadataService is opened to use freely the from/start value instead of passing by an attribute.

So first I think I will forget you were implying I am lazy.

Sorry for having worded this in an offensive way.
I feel like I should clarify a few things here:

"laziness" in the sense of "avoiding effort" is often a legitimate reason to not do something, especially in the context of a voluntary activities.
The concept of "laziness" as a character flaw is quite problematic, since it's often used to blame and shame people for what might be the symptoms of mental health issues or invisible disabilities. From individuals with executive dysfunction caused by ADHD or ASD there are reports of this contributing to a negative self image and depression. So I should have known better than to imply it.
Since this doesn't really come across in PR discussions that focus on what problems are still to be addressed until something can be merged: Your contributions to this project consistently have been of high quality and are very much appreciated.

here we go, this one should be fine now.
It will remain to update the client of the langserver after that. And then it will need to be released in order to be used in Prometheus.
But otherwise normally that should be the end of the changes requested in order to integrate it into Prometheus.


Add support for Rainforest Eagle-200

Breaking Change:
None
Description:
Add integration for Rainforest Eagle-200 device
Related issue (if applicable): None
Pull request with documentation for home-assistant.io (if applicable): home-assistant/home-assistant.io#9761
Example entry for configuration.yaml (if applicable):
# Example configuration.yaml entry
sensor:
  - platform: rainforest_eagle
    ip_address: <IP Address>
    cloud_id: <Cloud ID>
    install_code: <Install Code>

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[x] I have followed the development checklist

If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[x] The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
[x] New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
[ ] Untested files have been added to .coveragerc.

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

I don't suppose anyone knows if this works for the z109 too?

I haven't tried it against an original Eagle (z109) but I dont think it would work since the Eagle and Eagle-200 API calls are different.


Implement Cancel API method

@pymonger will need to touch base with the SPS team (either @ryanhunter-jpl or @drewm-jpl ), to see if the the API method is implemented.

@LucaCinquini is there a ticket for the implementation of this on the SPS side?  I think given the time left on this, I'm going to assign this issue to 23.3.

We do have an existing ticket which I also moved to 23.1:
https://github.com/unity-sds/unity-sps-prototype/issues/158

Moving this to "Future Work" / (backlog this ticket) as this is part of the deprecated work.  We may revisit this in the future.
@pymonger @GodwinShen @mike-gangl


DATETIME fields in Recorder using MySQL database discard subsecond information.

Home Assistant release (hass --version): 0.38.3
Python release (python3 --version):  Python 3.4.2
Component/platform: Recorder
Description of problem:  Recorder creates tables using DATETIME  for date/time information.
In Sqlite, DATETIME is implemented as a character field, so fractions of a second are stored and retrieved.  In MySQL, DATETIME fields by default do not store fractional seconds.  Use DATETIME(6) in MySQL to define a field equivalent to Sqlite's DATETIME.  SQLAlchemy knows about various "dialects" for different databases.
Expected:  Microsecond time resolution when retrieving DATETIME fields from MySQL database.
Problem-relevant configuration.yaml entries and steps to reproduce:
recorder:
  db_url: mysql://[User]:[Password]@[Host]/homeassistant?charset=utf8

>mysql -u[User] -p[Password] -h[Host] homeassistant # start mysql client to query database
mysql> SELECT created FROM states ORDER BY created DESC LIMIT 10;
.  .  .  created times have no subsecond info.

Traceback (if applicable):
Additional info:
The database schema including tables can be created prior to starting homeassistant with a MySQL database using DATETIME(6) for DATETIME fields to preserve the subsecond information.  This solution breaks when the database schema is updated from homeassistant.

The lack of activity probably signifies a lack of interest.  Go ahead and close this item.  If I pursue this issue, I will do the development I think is appropriate before opening another PR.


Error: Can't subset columns that don't exist. ✖ Column y_log_ddm, doesn't exist.

was able to test it this time, worked w/ this fix! #16

Thanks!! It passed the tests anyways.
I shall run a manual test to be sure.
When are you available to talk about the new gravity version?
On Wed, Feb 17, 2021, 6:16 AM Sarah Charlotte Johnson <
<EMAIL_ADDRESS>wrote:

was able to test it this time, worked w/ this fix! #16
https://github.com/pachamaltese/gravity/pull/16
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pachamaltese/gravity/issues/17, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACM7UONNRREKDIKOPUVZFWLS7OCQPANCNFSM4XX7LSWA
.

perfect, thank you! and I'll DM you on twitter and let you know my availability

fixed in #15


Fix deprecation warning

This patch makes devnull use the events module instead of process.EventEmitter because the latter has been deprecated in node 6.
This silences an annoying warning that is logged to the console when devnull is required.

ty


fix: add description in package.json

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fix converters for driver v2 + JSON support

This fixes the converters for version 2.x of the driver - now in use on main. v2 requires strict use of types.
We also add support for complex types - Tuple, Map and Nested. These are serialized to a JSON string. This thus supports the JSON type (results for this are returned as a Tuple). This allows uses to view JSON logs in the logs panel and explore.
Finally, to test all of this i've added significant tests so we don't miss issues with driver upgrades and types in the future.
This includes some IT tests - these use a Clickhouse instance (specified via env variables CLICKHOUSE_HOST and CLICKHOUSE_PORT - currently not secure). If these aren't specified we use a docker container. The former is appropriate for CI since it uses Drone (which uses docker itself for the tests and we don't support docker in docker yet @scottlepp @bossinc).  Can add support for a secure remote clickhouse instance if needed -this would actually allow us to test secure connections which is currently skipped.

Closes https://github.com/grafana/clickhouse-datasource/issues/141

The IT tests should skip if the env variables are not set and docker isn't available @scottlepp @bossinc - i can't see the drone failures - can you please share here?

@gingerwizard
Running target: Lint
exec: golangci-lint run ./...
pkg/plugin/driver_test.go:130:11: Error return value of `conn.Exec` is not checked (errcheck)
	conn.Exec("DROP TABLE simple_table")
	         ^
pkg/converters/converters.go:232:2: `name` is unused (structcheck)
	name string
	^
pkg/converters/converters.go:233:2: `kind` is unused (structcheck)
	kind interface{}
	^
Error: running "golangci-lint run ./..." failed with exit code 1```

@bossinc we now support following env.
CLICKHOUSE_USERNAME
CLICKHOUSE_PASSWORD
CLICKHOUSE_SSL - set to true to use SSL
CLICKHOUSE_USE_DOCKER - set to false to use an external instance for IT tests


How does parameter "enhance_data" actually work?

I'm trying to improve the accuracy on my Custom Trained Models and from what I read a good technique is to augment the images: rotate, skew, flip, etc.

What does this parameter actually do?

Currently, enhance_data parameter only performs horizontal flipping. More options will be provided later.


Handling database auto re-connection

This will handling MongoDB auto re-connection automatically ( 3 retry times ), especially useful if you work with MongoDB Replica Set ( Auto re-connect if the primary node went down ).
( I have changed to use Replica Set recently. )

When exactly do you need this? When have you been facing the issue of disconnection? Somehow I've never seen an issue like that and I am wondering why this is a required workaround. Could you elaborate more on the case(s) where this is helpful?

Ah, that makes sense. Though trying three reconnections in this brief time, is that sufficient? Taking a quick glimpse at Replica Sets in Mongo it seemst that the average election for a new primary MongoDB instance being completed takes around 10 seconds?
And to be sure, this change isn't tackling an issue you're currently facing but is a safety measure for a potential hazard that could come up in production. You're not facing any random connection losses?
I don't see this influencing the default behavior much, so it looks good to me.

Though trying three reconnections in this brief time, is that sufficient?

I think the re-connection is actually happening in the next pymongo operation, not so sure about the under laying mechanic, but I did simulate the situation by manually block the connection of the primary node and the code worked. :D

is a safety measure for a potential hazard that could come up in production.  You're not facing any random connection losses?

No, no connection issue here, it's for the safety, yes :)
Thanks @BigRoy !

I think the re-connection is actually happening in the next pymongo operation, not so sure about the under laying mechanic, but I did simulate the situation by manually block the connection of the primary node and the code worked. :D

Did you try the same with a "write" operation? See: https://docs.mongodb.com/manual/replication/#automatic-failover - it states:

The replica set cannot process write operations until the election completes successfully. The replica set can continue to serve read queries if such queries are configured to run on secondaries while the primary is offline.

So it's likely that read operations are easier to pass, but the write might still fail.
A bit unrelated to the code itself though. :)

Did you try the same with a "write" operation?

Yap, I did try with insert_one ;) , and it did wait a bit longer ( must be waiting the election ! ) :P

Merging this !!


VM using 100% CPU on Linux 3+

This doesn't happen using linux.iso. Low CPU usage is very important to me, do you know why this happened? Is the kernel configuration available?

I solved this using CONFIG_NO_HZ_IDLE and HZ=100.

Yes, that's indeed a problem. Under Javascript the idle time should exceed 4ms. For jor1k I put even HZ=50 here.

I wonder how do you avoid 100% CPU (on one core) with Linux, all the Linux images (2.6.x and 3.x) on copy.sh use 100% and my self compiled kernel with CONFIG_NO_HZ_IDLE=y and HZ=50 too, on both firefox and chromium.

Well, I have everything under my control. My own distribution, my own emulator, my own compiled Linux, my own programmed Linux idle function (which wasn't implemented yet).
x86 is much more complicated. So I am not sure, what the Linux operating system expects for a system. I guess you compiled also for a single core.

This repo builds an ISO image for v86 that didn't use 100% CPU last time I tested: https://github.com/ysangkok/build-v86-9p-linux
The repo contains a Linux config that uses the settings I mentioned earlier in this thread.

I would try to debug the setTimeout function in Javascript. to see what is the average timeout in ms for the Javascript engine. Also there is the update of the screen now and then which could influence the total CPU usage.
I tried it myself and it looks like, that the IPS indeed decrease when idle but the CPU usage remains the same.

ysangkok: Do you have a binary?

@s-macke yes
Here's the ISO image: https://hushfile.it/55681e725bfa2#HGrNrA2-vQP4QW20zblBtY-AjHfqrpStbaqhurka
Here's the root filesystem: https://hushfile.it/55681fc278c8d#DgLyVmrj8E-EEes80V2duyTEPQ0Sdgkai2SDpu0C
Here's the root filesystem JSON: https://hushfile.it/55682033f0e6f#8yX12xOCqtYu_a98KyRS9r5ts15NjkqtaTv5wH8H
And here's a sample HTML file that has a 9p filesystem configured for it: https://github.com/ysangkok/browser-http-proxy/blob/master/basic.html


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/67120

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/77197

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/77211

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/77303

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/84186

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/114917

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/116229


F# cannot find Arachne.Http.State.Cookie.Parse when used in another project

See discussion at https://github.com/panesofglass/websharper.owin/pull/1

NOTE: if you open the namespace and don't use the FQN, this appears to compile and work fine in a console app, though not in WebSharper.

False alarm; WebSharper.Owin was built with F# 3.0. Bumping that to F# 3.1 solved the problem. @kolektiv should we consider bumping Arachne to F# 3.0?


Doc nit: Include instructions to "npm install shpjs" in readme

It's surprisingly hard to find this project on npm, by search on npm or elsewhere.  There are many shapefile projects, your username is different, etc.

feel free to open a pull request 😄


Allow warning with cartopy in docs plotting build

Fixes https://github.com/pydata/xarray/issues/4030
It looks like this is triggered by the new cartopy version now being installed
on RTD (version 0.17.0 -> 0.18.0).
Long term we should fix this, but for now it's better just to disable the
warning.
Here's the message from RTD:
Exception occurred:
  File "/home/docs/checkouts/readthedocs.org/user_builds/xray/conda/latest/lib/python3.8/site-packages/IPython/sphinxext/ipython_directive.py", line 586, in process_input
    raise RuntimeError('Non Expected warning in `{}` line {}'.format(filename, lineno))
RuntimeError: Non Expected warning in `/home/docs/checkouts/readthedocs.org/user_builds/xray/checkouts/latest/doc/plotting.rst` line 732
The full traceback has been saved in /tmp/sphinx-err-qav6jjmm.log, if you want to report the issue to the developers.
Please also report this if it was a user error, so that a better error message can be provided next time.
A bug report can be filed in the tracker at <https://github.com/sphinx-doc/sphinx/issues>. Thanks!

>>>-------------------------------------------------------------------------
Warning in /home/docs/checkouts/readthedocs.org/user_builds/xray/checkouts/latest/doc/plotting.rst at block ending on line 732
Specify :okwarning: as an option in the ipython:: block to suppress this message
----------------------------------------------------------------------------
/home/docs/checkouts/readthedocs.org/user_builds/xray/checkouts/latest/xarray/plot/facetgrid.py:373: UserWarning: Tight layout not applied. The left and right margins cannot be made large enough to accommodate all axes decorations.
  self.fig.tight_layout()
<<<-------------------------------------------------------------------------

https://readthedocs.org/projects/xray/builds/10969146/

I'm merging this for now to fix our CI...


feat: new error message for legacy chart

SUMMARY

This adds an error if the user selects a chart that uses the legacy api. It also goes through and deletes a former error message that was keyed off of the api endpoint.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

https://user-images.githubusercontent.com/48933336/177880384-65f31d8d-3cc1-41c0-bf3d-a06fbd99c7ae.mov

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

Thanks @AAfghahi! Can you add some screenshots too?

/testenv up

/testenv up

/testenv up


UndefVarError: m_x_t_min not defined

I ran into this error while running the 1_state_estimation_forward_only demo as a .jl script inside the Atom Juno IDE. I'm running Ubuntu 18.04.
This is expected behavior since Julia v. 1.0.0. as noted here: JuliaLang/julia#28523
In order to access global variables inside blocks, they must be specified with the global keyword inside the block.
This snippet reproduces the error:
i = 10
while i > 0
    println(i -= 1)
end

UndefVarError: i not defined

This is the fix:
i = 10
while i > 0
    global i
    println(i -= 1)
end

Note that this error does not occur with IJulia notebooks. Apparently, this behavior is defined differently for interactive evaluation contexts: JuliaLang/julia#28789.

great find @mroavi although I dont see your code snippet in 1_state_estimation_forward_only demo . Can yo specify at which line the error occurs and how to fix it (eg global t after the for t=1:n_samples ?). Feel free to fix the issue and submit as PR.

Right. The code snippet is just the simplest example that I could think of to show/reproduce the problem. I think that such issue shows up in most of the demos. I will test them and add the fix.


update url, old url was 404

Somewhat minor, but the old git.io url is a 404.

See also:

https://github.com/necolas/normalize.css/commit/0c31dada5189a577f16fc61cbd8680e7f35bcca3
https://github.com/necolas/normalize.css/issues/411

--
@dieseltravis This should come with the update, but let's change it anyway. :)


Update knowledge api minimum wage rates

These values have been updated to match the content here: https://www.gov.uk/national-minimum-wage-rates#current-rates
The knowledge_api is used to tell Alexa about important values on GOV.UK so we should keep this up to date. (Check it out at https://www.gov.uk/api/content/knowledge-alpha)
We'll need to republish the content item on 1st April by running:
  rake publishing_api:publish_knowledge

against publisher on a backend box.

Thanks! 🎉


fix spelling in OpenStack ex_files description

"on the no  de" should be "on the node".
Description
"on the no  de" should be "on the node" in the API docs
Status

done, ready for review

Checklist (tick everything that applies)

[x] Code linting (required, can be done after the PR checks)
[x] Documentation
[x] Tests
[x] ICLA (required for bigger changes)

Thanks! Merged in trunk. ✨


Create Get Support Screen

Description:

Create Get Support Screen
Implement the screen to full functionality

hey @peculiaruc can i work on this issue?

hey @peculiaruc can i work on this issue?

Sure

okay on it, please assign it to me😇


Fix skipped redis unit tests

Updating to 2.X.X of StackExchange,Redis broke the unit tests because we can't properly mock the ISubscriber class.
This is for tracking https://github.com/StackExchange/StackExchange.Redis/issues/969 and fixing our unit tests once a fix has been made.

Also re-enable RedisHubLifetimeManagerBenchmark


Add caching for cargo dependencies in Travis builds.

Assigning @hdevalence for review, if that's okay with you?


Change location API and Generalize location entities

Solve #337 #338

Thank you for taking the time to contribute! This is sincerely appreciated. 😇


Rule suggestion: Flag QueryNew() with duplicate columns.

CF11 allows
querynew('Name,Email,Email')
without any bad side-effects.  At best this is at least a code smell.
In Lucee , this causes a hard error.
What do you think of starting a rule set for items like that that are code smells that Adobe CF forgives, but other engines fail on.

added to dev
"QueryNew declares column y multiple times, this is a hard error in some CFML implementations."


No builds. Your build is being queued. If your build has not started in over a minute, click the button below.

Before opening, please confirm:
I have checked to see if my question is addressed in the FAQ.
I have searched for duplicate or closed issues.
I have read the guide for submitting bug reports.
I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
Describe the bug
After Clicking Save and Deploy. Build got stucked.
I already checked this in the issue. They are mentioned , this is because of permission issue,
But where i need to change the permission, I got stuck with this.
Let me know how to solve this.
Expected behavior
it needs to setup the four step process
provision , Build , Deploy and Verify
Reproduction steps

Host new app
2.Select Bit Bucket
3.Save and Deploy
I got the error

Build Settings
No response

Hi @Sureshkumar251997, thanks for raising.

I already checked this in the issue. They are mentioned , this is because of permission issue,
But where i need to change the permission, I got stuck with this.

Can you link the issue here that describes your issue? Also, if there are any specific log messages, please copy here (be sure to remove sensitive information).
Thanks!

Hi @Sureshkumar251997, thanks for raising.

I already checked this in the issue. They are mentioned , this is because of permission issue,
But where i need to change the permission, I got stuck with this.

Can you link the issue here that describes your issue? Also, if there are any specific log messages, please copy here (be sure to remove sensitive information).
Thanks!

Hi @Sureshkumar251997, thanks for raising.

I already checked this in the issue. They are mentioned , this is because of permission issue,
But where i need to change the permission, I got stuck with this.

Can you link the issue here that describes your issue? Also, if there are any specific log messages, please copy here (be sure to remove sensitive information).
Thanks!

This is my APP ID : dt929pepd0nfi.
I am using Bit Bucket.
Step: 1
I selected bitbucket with repo and branch
Step: 2
Confirm build settings for the front end
Step : 3
When I click save and deploy , It got stucked
No builds.
Your build is being queued. If your build has not started in over a minute, click the button below.

Expected behavior
it needs to setup the four step process
provision , Build , Deploy and Verify
It is not happening.
This issue is not solved
Thanks .


Add Codeforces Problems

I would like to add the problems listed below to codeforces solutions
900 Rating:

1543-A
1705-B
1689-B

1000 Rating:

479-A
58-A

@aaryahjolia Please assign this issue to me


SUP-6598: update-public-ephemeral-spark-example

The purpose of this PR is to update our public facing terraform example for using ephemeral spark on an AWS deployment. This uses the code that we most recently performed scale-testing on. There are a lot of changes in here that I'm not sure if they can be done / have been done correctly. Some of my concerns are:

I switched from using a local.tfvars file to using .tf files. Can this be used by customers as well?
Some of our files, like the label.tf file which provides the tag refers to a labels module that is internal only. I excluded the reference to this module when setting up the file. But I am not sure if this will work as intended if used by customers.
The provider.tf file in the example I pulled from has references to where the output should be saved (our GCP backend). How should this be referenced for customers? Or will this just not work and should I be sticking to the previous format of using local variables and outputs?

The purpose of this PR is to update our public facing terraform example for using ephemeral spark on an AWS deployment. This uses the code that we most recently performed scale-testing on. There are a lot of changes in here that I'm not sure if they can be done / have been done correctly. Some of my concerns are:

I switched from using a local.tfvars file to using .tf files. Can this be used by customers as well?
Some of our files, like the label.tf file which provides the tag refers to a labels module that is internal only. I excluded the reference to this module when setting up the file. But I am not sure if this will work as intended if used by customers.
The provider.tf file in the example I pulled from has references to where the output should be saved (our GCP backend). How should this be referenced for customers? Or will this just not work and should I be sticking to the previous format of using local variables and outputs?

Generally, variables are good for modules and examples and locals are good for concrete usage. The examples are abstracted a bit since we don't concretely know what environment they'll be used in.
Tagging is very important part of using AWS. Policies are often enforced via tags. Give that it's a freeform field, the standards will vary from user to user, but having showing off a generic way of adding tags that a user of this module could adapt sounds good to me.
These examples can't assume too much how the state should be managed. That will vary quite a bit based on the user of the module, since there are lots of ways Terraform pipelines are managed. All we can really do is define the providers that the examples require.


Possible to include pre-defined Prompts?

Thanks for your contribution to the community.
I am wondering if it is possible to include pre-defined prompts such as the ones at https://github.com/f/awesome-chatgpt-prompts ?

Can you be more specific about how this feature would be integrated with this extension?

I will consider adding this feature to the slightly later version and provide an optional toggle


Indexify-hotfix

Small PR to fix indexify for Sub/Conditional dimensions
Added two test for FD in combination with Sub/Conditional dimensions.

Codecov Report

Merging #652 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #652      +/-   ##
==========================================
+ Coverage   87.37%   87.37%   +<.01%
==========================================
  Files          93       93
  Lines        9149     9151       +2
  Branches     1831     1833       +2
==========================================
+ Hits         7994     7996       +2
  Misses        932      932
  Partials      223      223

Impacted Files
Coverage Δ

devito/types.py
91.24% <100%> (+0.04%)
:arrow_up:

Continue to review full report at Codecov.

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


post request endpoints are not correct

open the console.
most post requests from the client to the url that conatrin the monitor-server are passed with two slashes (//)
for example:
POST https://<IP_ADDRESS>/hkube/monitor-server*//*store/algorithms/apply 400
look between the monitor server and the store

Fixed some versions before (1.1.142)


Few configurations are not persistent after a server restart.

All the configurations to yang file,which i instantiated using edit-config or user-rpc command are not persistent, only a few config persists, after a server restart.
i was able to observe this in the Rpc reply,  while trying to process the  rpc.
It was actually persistent initially, but lately, i need to configure few modules, every time after a restart.
Is there any fix for this?

Only configuration in startup datastore persists, the one in running (the default datastore, generally) does not.

So is it a goof process to create configurations targeted to the startup datastore rather than candidate or running?

Naturally, if you want your configuration to persist across reboots and be the default one after system start.


#128: Implement collection overrides for external Solr:

This PR adds the ability to override the external Solr collection by specifying the alternative in the configuration file.
(The Maven archetype for the external Solr connector already had the collectionName property present in the config, but it was ignored. I'm not sure why the override wasn't implemented at the time.)
If merged, I'll modify the wiki pages as necessary.

Thanks @mattflax looks great!

Thanks @mattflax looks great!


Hope to make one for AIM

Can I entrust you to redefine the CAN BUS protocol of 20022 BRZ?
It is used on the display of AIM and pay you. This problem is bothering me

This project is for RaceChrono, not AIM.
[For my own records, we've chatted offline and I helped Kenny find the info about AIM setup for gen2]


HHH-14227 fix testing failure on Oracle

Oracle stores null value when Lob field contains empty content, which happens to be the case for the original testing case.

thanks!


Cutom headers missing when using path based routing

Hi, We are seeing an issue after upgrading from Marathon-LB 1.12.0 to 1.14.2 with path-based routing. All the custom headers are being dropped and not being sent to the backend. Is this an issue with haproxy version or marathon-lb?
Marathon-LB configuration:
  "labels": {
    "HAPROXY_GROUP": "external",
    "HAPROXY_0_BACKEND_HTTP_OPTIONS": "  option httplog\n option forwardfor\n  http-request set-header X-Forwarded-Port %[dst_port]\n  http-request add-header X-Forwarded-Proto https if { ssl_fc }\n",
    "HAPROXY_0_PATH": "-i /mobile",
    "HAPROXY_0_VHOST": "stg-chicago.example.net ,stg.example.net ",
    "HAPROXY_0_HTTPS_FRONTEND_ACL_ONLY_WITH_PATH": "  acl path_{backend} path_beg {path}\n use_backend {backend} if path_{backend}\n"
  },

HQSMLrchalla$ curl --location --request PUT 'https://stg-chicago.example.net/mobile/devices/hh::fedsdsdsdsdTLKrBA:AdfdfdfdA91bFvln4f6iVsksPpATVeLmzXHhEudWZGWrsC0ldaoSRLMCGIPH5PCPUFIFBMZFA5gzH3dTtTEeT3oP6kktVu8a0l2T4l9x4OfLzpOpYrnvc2qV3Iz' --header 'Content-Type: application/json' --header 'OAuth-Consumer-Key: scRdfsfsfsdfdsfdsfsdfdsfsdfsd0xdxEq' --data-raw '{
    "consumerName" : "hh",
    "token" : "fe3f4TLKrfadfafaffadfadfadfadfafadfadfadfdafadfdafadfafadfTEeT3oP6kktVu8a0l2T4l9x4OfLzpOpqpNTQtljJLT9c3fMBTqXbsfYrnvc2qV3Iz",
    "deviceType" : "ios",
   "subscriptions":  ["/hh/demo"]
}'

"Expected OAuth-Consumer-Key or Authorization header"

The above query/request is failing only in the latest version 1.14.2 and is still working as expected in 1.12.0 version
PS: Path-based routing, in general, is working fine it is only failing when the backend expects headers in the request

Closing this for anyone facing this issue, Not sure if it marathon-lb or haproxy 2.0 the headers are getting normalized the OAuth-Consumer-Key is now being presented to backend app as oauth-consumer-key we changed our app to accept case insensitive headers and everything is working fine now


StorageAccount custom domain indirect validation not working

When I try to create a storage account with custom domain using indirect subdomain validation the setting is ignored and the com.microsoft.azure.CloudException: The custom domain name could not be verified. is thrown and in the message you can see that no asverify domain is used

could you pls add some sample repro code?

azureManager.azure().storageAccounts()
	.define("mysa").
	.withRegion("west-europe")
	.withNewResourceGroup()
	.withCustomDomain("mysa.mydomain.com", true);

Even if I use it on update and I see the PATCH body looks like below{
{"properties":{"customDomain":{"name":"mysa.mydomain.com","useSubDomain":true}}}
it throws: com.microsoft.azure.CloudException: Status code 409, {"error":{"code":"StorageDomainNameCouldNotVerify",
storageAccount.update().withCustomDomain("mysa.mydomain.com", true).apply();

@anuchandy any ideas?

@jkubrynski did you create a CNAME record subdomain alias with subdomain asverify and map it to your storage account url? after this step storage account needs to be updated with the custom domain.

@jkubrynski Did @anuchandy 's suggested fix help you with the issue?

Adding needs-more-info and closing this issue that hasn't had a follow-up since September 2017.


Switch to java 21 in parent pom

As per title
Should help getting unit test workflow green again (see https://github.com/knative-extensions/eventing-kafka-broker/actions/runs/7140644527/job/19451034741?pr=3522)

/cc @Cali0707 @matzew


Can not connect to server

I'm not sure if my problem is related to the my simple python code:
import geoglows
river_id_list = [210004000,210006110,210006111,]
forecast_data = geoglows.data.forecast (river_id_list, date='20241215', format='df', data_source='aws')
I get the following output:
Traceback (most recent call last):
File "/usr/local/lib64/python3.9/site-packages/aiohttp/connector.py", line 980, in _wrap_create_connection
return await self._loop.create_connection(*args, **kwargs)  # type: ignore[return-value]  # noqa
File "/usr/lib64/python3.9/asyncio/base_events.py", line 1090, in create_connection
transport, protocol = await self._create_connection_transport(
File "/usr/lib64/python3.9/asyncio/base_events.py", line 1120, in _create_connection_transport
await waiter
File "/usr/lib64/python3.9/asyncio/sslproto.py", line 534, in data_received
ssldata, appdata = self._sslpipe.feed_ssldata(data)
File "/usr/lib64/python3.9/asyncio/sslproto.py", line 188, in feed_ssldata
self._sslobj.do_handshake()
File "/usr/lib64/python3.9/ssl.py", line 945, in do_handshake
self._sslobj.do_handshake()
ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1147)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/aiobotocore/httpsession.py", line 208, in send
response = await self._session.request(
File "/usr/local/lib64/python3.9/site-packages/aiohttp/client.py", line 536, in _request
conn = await self._connector.connect(
File "/usr/local/lib64/python3.9/site-packages/aiohttp/connector.py", line 540, in connect
proto = await self._create_connection(req, traces, timeout)
File "/usr/local/lib64/python3.9/site-packages/aiohttp/connector.py", line 901, in _create_connection
_, proto = await self._create_direct_connection(req, traces, timeout)
File "/usr/local/lib64/python3.9/site-packages/aiohttp/connector.py", line 1206, in _create_direct_connection
raise last_exc
File "/usr/local/lib64/python3.9/site-packages/aiohttp/connector.py", line 1175, in _create_direct_connection
transp, proto = await self._wrap_create_connection(
File "/usr/local/lib64/python3.9/site-packages/aiohttp/connector.py", line 982, in _wrap_create_connection
raise ClientConnectorCertificateError(req.connection_key, exc) from exc
aiohttp.client_exceptions.ClientConnectorCertificateError: Cannot connect to host geoglows-v2-forecasts.s3.us-west-2.amazonaws.com:443 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1147)')]
Is the problem on my side or on the AWS server side?
Thank you,
Vladimir

Hi Vladimir. It looks like your code was unable to connect to the bucket. Probably because a certificate expired or was inaccessible. The AWS buckets do occasionally have temporary outages. I'm not able to reproduce the error after trying on multiple machines. Does it work for you now? It may have been a temporary outage that is now resolved.

Hi Riley,
Thank you for the quick answer.
I found a solution here:
https://community.openai.com/t/ssl-certificate-verify-failed-certificate-verify-failed-self-signed-certificate-in-certificate-chain/705003/6
I put the following variables in my environment
export SSL_CERT_FILE=/etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem
export REQUESTS_CA_BUNDLE=/etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem
and now everything works.

@meersonv I just want to clarify that getting our data doesn't require specifying certificates. AWS uses https but my understanding is that validation happens using default settings.
My guess is that your system was missing standard certificate settings or had an issue with SSL verification. Hence you had to set those variables manually.


Fix PushNotificationIOS fetchCompletionHandler documentation link

There seems to be broken link to Apple's developers documentation in finish() function description (https://facebook.github.io/react-native/docs/pushnotificationios#finish). Current one redirects to main UIApplicationDelegate page.
This PR fixes that and points directly to application:didReceiveRemoteNotification:fetchCompletionHandler: instance method docs.

Hey there! Could you pull down master to address this language linting error? It has the fix! Thanks!

Hey, @rachelnabors 👋  I've rebased with master, it should be good now.


Added color palette feature for Wrapper

I think this feature might be useful if users want to use their own color palette.

That's a bit problematic...
So if we are going that way, both Background and Foreground colors should be editable.
Also, the length of Foreground colors and Background colors should be equal otherwise plugin has to throw an error.
Enabling this, will dramatically reduce the chance of creating unique combinations, yet people might want to edit colors to their brand colors, that's totally understandable.


implement a2dp remain todo/interfaces

Implement the remain A2DP todo/interfaces as follow:
Implement the bt_a2dp_stream_reconfig: Modify reconfig_req callback to
pass codec_cfg to application. Remove reconfig_rsp callback,
config_rsp is used. Remove reconfigured callback, configured callback is used.
Implement the bt_a2dp_stream_release: The release_req,
release_rsp and released callbacks are already defined,
implement them in this change.
Implement the bt_a2dp_stream_suspend: The suspend_req,
suspend_rsp and suspended callbacks are already defined,
implement them in this change.
Add and implement the bt_a2dp_stream_abort: Add abort_req,
abort_rsp and aborted callbacks.
Implement bt_a2dp_disconnect.
Simplify the codes: (1) use the same bt_avdtp_ctrl_params to process open,
start, suspend, close and abort operations. (2) use same a2dp_ctrl_ind to
process open, start, suspend, close and abort operations. (3) use the same
bt_a2dp_ctrl_cb to process open, start, suspend, close and abort operations.
(4) use the same bt_avdtp_ctrl to process open, start, suspend, close and
abort operations. (5) move the status to common struct bt_avdtp_req.
Add shell test.

@lylezhu2012 are you planning to review this?

@lylezhu2012 are you planning to review this?

Yes. I will make it done before this weekend.

@MarkWangChinese there still seems to be some compliance error

Github doesn't allow doing inline commenting on commit messages, so I'll do it here. Let's look at the first commit in this PR:

Implement the bt_a2dp_stream_reconfig: Modify reconfig_req callback to
pass codec_cfg to application. Remove reconfig_rsp callback,
config_rsp is used. Remove reconfigured callback,
configured callback is used.
Implement the bt_a2dp_stream_release: The release_req,
release_rsp and released callbacks are already defined,
implement them in this change.
Implement the bt_a2dp_stream_suspend: The suspend_req,
suspend_rsp and suspended callbacks are already defined,
implement them in this change.
Add and implement the bt_a2dp_stream_abort: Add abort_req,
abort_rsp and aborted callbacks.
Implement bt_a2dp_disconnect.
Simplify the codes: (1) use the same bt_avdtp_ctrl_params to process open,
start, suspend, close and abort operations. (2) use same a2dp_ctrl_ind to
process open, start, suspend, close and abort operations. (3) use the same
bt_a2dp_ctrl_cb to process open, start, suspend, close and abort
operations. (4) use the same bt_avdtp_ctrl to process open, start,
suspend, close and abort operations. (5) move the status to common struct
bt_avdtp_req.
change A2DP_MAX_IE_LENGTH as BT_A2DP_MAX_IE_LENGTH

Each of those paragraph is a single logical change in itself, i.e. these changes should all be in separate commits. Whenever you find yourself enumerating multiple changes in the commit message and those changes are not tightly coupled, it's a good indication that you need to split things up. Additionally, in this same commit you're also including coding style changes to unrelated lines of code - those should also be in a separate commit.

Github doesn't allow doing inline commenting on commit messages, so I'll do it here. Let's look at the first commit in this PR:

Implement the bt_a2dp_stream_reconfig: Modify reconfig_req callback to
pass codec_cfg to application. Remove reconfig_rsp callback,
config_rsp is used. Remove reconfigured callback,
configured callback is used.
Implement the bt_a2dp_stream_release: The release_req,
release_rsp and released callbacks are already defined,
implement them in this change.
Implement the bt_a2dp_stream_suspend: The suspend_req,
suspend_rsp and suspended callbacks are already defined,
implement them in this change.
Add and implement the bt_a2dp_stream_abort: Add abort_req,
abort_rsp and aborted callbacks.
Implement bt_a2dp_disconnect.
Simplify the codes: (1) use the same bt_avdtp_ctrl_params to process open,
start, suspend, close and abort operations. (2) use same a2dp_ctrl_ind to
process open, start, suspend, close and abort operations. (3) use the same
bt_a2dp_ctrl_cb to process open, start, suspend, close and abort
operations. (4) use the same bt_avdtp_ctrl to process open, start,
suspend, close and abort operations. (5) move the status to common struct
bt_avdtp_req.
change A2DP_MAX_IE_LENGTH as BT_A2DP_MAX_IE_LENGTH

Each of those paragraphs is a single logical change in itself, i.e. these changes should all be in separate commits. Whenever you find yourself enumerating multiple changes in the commit message and those changes are not tightly coupled, it's a good indication that you need to split things up. Additionally, in this same commit you're also including coding style changes to unrelated lines of code - those should also be in a separate commit.

Hi @jhedberg I have split the commit to three commits. I do the code format firstly with one commit. Then add one commit for the reconfig implementation and codes optimization. The last one is the new added close, suspend and abort. The second commit is still little big, but it is hard and need more effort to split because there are some common optimizations in it. Please help to review again. Thanks.

@MarkWangChinese are you still working on this? There are several failed CI checks.

@MarkWangChinese are you still working on this? There are several failed CI checks.

Hi @jhedberg Sure, I am still working on it. I will fix it recently. Thanks


Plugin hub button no longer shows up

It seems Runelite updated how the plugin hub shows up and the hijacked plugin hub no longer shows up after today's runelite update.
The hijacked plugins do seem to load however they are also not shown in the list of plugins

Still uses the old button format but it works.


Add clarity-icons/clarity-icons-api.js to build output

Select one ...  (check one with "x")
[ ] bug
[ ] feature request
[x] enhancement

Expected behavior
Include clarity-icons/clarity-icons-api.js in build output
Actual behavior
clarity-icons/clarity-icons-api.js removed from build output in 0.10.8
Reproduction of behavior
Not possible
Environment details
Node 8.5
npm 5.4.2

Hi @goodmorninggoaway
Thanks for pointing this out. We'll have someone look at this ASAP.

I'm preparing a PR

Hi @goodmorninggoaway thanks again for submitting the PR.  Closing this issue.


Announcement: Library's future

With the respect to those who use and contribute to this library I feel I need to share the future vision of react-advanced-form, and make it clear what is the development status now.
What happens now
Although there are minor issues, I treat the current state of the library (1.6.7) as stable. It's actively used in production, and it's safe to introduce it to your project.
However, I want to announce that all the current feature development is stopped. Bugfixes should be introduced occasionally, but, unfortunately, I have no time to investigate and solve each bug due to work/life schedule. If you discover and issue, please feel free to investigate and solve it, I will support you with suggestions and review your pull request.
What happens in the future?
This doesn't mean that the library is stale. On the contrary, I will try to dedicate time to introduce the next major version of the library, hopefully, somewhere this year. It will be re-written in TypeScript, and contain a lot of architectural improvements.
This project hasn't been written in the most proper way due to time constrains, and some decisions taken at the very beginning still backfire (#268, #287) after a year of its existence. I don't believe solving them is possible with the current state of the architecture, thus I'm putting my effort in re-writing this library from scratch, utilizing proper event sourcing, and making its architecture resilient toward future adjustments or features.

I plan to release the first beta of 2.0 approximately in the autumn of 2019. It will be a breaking change, it will introduce new API (#264), and it will eradicate a ton of existing issues caused by architectural problems.

What does it mean for developers?
If you are using RAF you may not get new features this year. Bugs will be solved depending on their priority, and I would be thankful for bug reporters to attempt to solve bugs as well. It's an open source project, so you are welcome to contribute and fix things. There is no pressure on you, and no pressure on the current contributors, we all do it in the free time.
What does it mean for contributors?
Please try to help others with questions or issues, if you have time. I am extremely thankful for people who support this project!
Afterword
I'm thankful for your understanding and will try to support your questions as much as I can. The project is not going anywhere, I'm just taking a step back to rethink it, and make a better version of it.

I wanted to bump this to let anybody interested know that the plans regarding improving the library has been in discussion since the last year. I don't have much time to dedicate to it at the moment, but there is a solid foundation developed that would eventually become<EMAIL_ADDRESS>I treat the absence of issues during this period as a sign that the latest release is stable and can be safely relied on.
Thank you for using this library.

Any news regarding typescript support?

Hey, @MushroomMaula. There are no plans to provide a TypeScript support to the current version. We welcome external type definitions by contributors (i.e. as a PR to DefinitelyTyped repo).
The next version of RAF is rewritten entirely in TypeScript. I don't have any dates when the next version lands, as it's not on my schedule. There may be time to work on it somewhen closer to the end of the year. I wouldn't expect that release sooner than next year due to resources limitation.


Range iterators?

Currently it is not possible to do something like
for n in u5::MIN..u5::MAX {
    //...
}

Implementing this would be possible if/when step_trait is stable.
Alternatively it is possible to create a new range-like type which implements IntoIterator, produced by something like u5::range(u5::MIN, u5::MAX). The downside of course is that this function would become unnecessary if step_trait is stabilized.

Hey, thanks for filing the feature request. I am happy to add an optional feature to support step_trait. I actually have that need from time to time as well.
I'm planning to get this in within a few days.

Hey, thanks for filing the feature request. I am happy to add an optional feature to support step_trait. I actually have that need from time to time as well.
I'm planning to get this in within a few days.

if that is okay with you - I have implemented this already, so perhaps I can open a PR and see whatever additional changes it require.

Oh awesome! Sure, please send over a PR

Merged it. Do you want this published on crates.io right away or is it enough to roll this into whatever is the next version?

thanks for merging. I don't need this right now, so feel free to push this whenever you want.

Sounds good. Thanks again for your contribution!


Request: Add support for Qwen models

Hello,
As more people jump on board with using and developing Qwen's open-source models, we've seen a bunch of variants popping up. I think it'd be really cool if this project could support them. Right now, there's a lot of buzz around a variant from a Japanese LLM developer named Rinna, specifically the Nekomata-7b/14b based on Qwen, and it would be cool if this works on mobile devices easily.
I'm not totally sure how tough it would be to add this, but Qwen's already up and running in the original llama.cpp repo here, so this might help a bit.
(Also, English isn't my first language, so sorry for any odd bits🙏)
Thank you!

Sorry please don't mind about this, I simply missed that it's already supported...


arXiv completeness check

Create a script that regularly checks missing arXiv CORE records. This script exists on legacy and we also used to have a similar one on labs a while ago - we just need to resurrect it.

TECH NOTES

Create a new repo in cerns-sis, which will used for completeness checks in our different projects.
Create a cli that will reuse this completeness check (code must be refactored).
Add a dockerfile which will run the cli command
Add the cronjob in hep application that will run everyday from Monday to Friday. Make sure to pass all the necessary secrets for Zulip.

@benjamin-bergia ☝ could you please have a look?


Error while cancelling orders

I'm getting the error 'proto:\xa0syntax error (line 1:1): unexpected token "{\\"order_ids\\": [{\\"market\\": \\"BTC-USD\\", \\"order_id\\": \\"6659a34f-8ec2-4689-8030-22f02113140d\\"}]}"' while trying to cancel orders.
This is my function:
def cancell_all_pending_orders(self):
        open_orders = coinbase_client.listOrders()
        order_ids = [{'market': order['product_id'], 'order_id': order['order_id']} for order in open_orders]
        order_cancelled = coinbase_client.cancelOrders(order_ids)
        print(f"ORDERS MANAGEMENT | {order_ids} cancelled succesfully")

Should be fixed now that we're pointing to the official SDK


Request for wiki pages

Hi, can you please migrate the documentation for the following pages?
https://github.com/microsoft/ajaxmin/wiki/Migrating-v4-to-v5
https://github.com/microsoft/ajaxmin/wiki/AjaxMinTask
Thanks!

This project is no longer being maintained.


Resize handle does not display

Hi, I'm wrapping my single file component with draggable resizable, the dragging works, yet the resize handles appear to be of 0 height and 100% container width.
I'm using the tag like this:
<vue-draggable-resizable  :x='x' :y='y' :w='width' :h='height' :parent='true' :active="true" v-if='show' @click='setToTop' :style='{"z-index": zIndex}' :class='{"isBelow": isBelow}'>
the width and height are set to be:
x: 1000,
width:396,
height: 1000
The sizing for all the handles are 396 * 0, and they don't show up even after I changed their height and z-index.

Please help, thanks.

Please provide a basic example of the issue using https://jsfiddle.net/ or https://codepen.io/


Fix conda-ci GitHub Action CI by using mambaforge directly

Currently the CI is failing on Linux and Windows with a weird conflict error. This is due to the fact that we are install mamba (from the conda-forge channel) on the top of miniconda3 (that by default install all the packages from the defaults channel). To make an analogy in apt world, this is like installing Debian, and then trying to install packages from the Ubuntu repo: something can go wrong.
To solve this problem, we install mambaforge (a installer like miniconda3 but already using conda-forge packages) directly, so we always and only use packages from the conda-forge channel.
Fix https://github.com/ami-iit/bipedal-locomotion-framework/issues/592 .
Similar to:

https://github.com/robotology/robotology-superbuild/pull/840
https://github.com/robotology/robometry/pull/141
https://github.com/robotology-playground/yarp-devices-ros2/pull/44
https://github.com/gazebosim/gazebo-classic/pull/3287

Thank you @traversaro for handling this


⚠ Bofrost.lu has degraded performance

In fbd8177, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1127 ms

Resolved: Bofrost.lu performance has improved in 1e4f43d after 18 minutes.


Missing GitHub release & tag for RC9

RC9 is missing a git tag and the GitHub release (which could link to the Changelog)

Thanks for the reminder :).


Added pygy/j2c

This is a CSS preprocessor working from JS objects. Raw source is 6KB, mingzipped down to 800 bytes.
http://j2c.py.gy https://github.com/pygy/j2c

Great, thanks :-)
How long does it take after make for the site to update?


Confusing "This state has not been shared" notification

There is a new bar that says "This state has not been shared, share and copy the JSON or RAW url to avoid losing progress." and seems to not go away unless you click the "Share" button in the notification bar. It then never returns, even as you change the state. This is confusing, inconsistent, and looks like an error, but most of the time it's entirely normal to use Neuroglancer for browsing without saving states.

Should be resolved by #429


deploy: Do not use kubelet plugins location for driver socket

/var/lib/kubelet/{plugins,plugins_registry} is the location for plugins which
are supposed to implement kubelet's plugin registration API. This is implemented
by node-driver-registrar sidecar container in case of a CSI driver.
So PMEM-CSI should not use these locations for creating its listening socket.
No we use plugin state directory(/var/lib/pmem-csi.intel.com) for this.
Fixes: #394

Can you add a comment? If the node-driver-registrar had a command line option for it, we could use that to document the usage, but /registration is hard-coded in the source (https://github.com/kubernetes-csi/node-driver-registrar/blob/6ef000ae529ad4c8e2928f0803d65ac25f3f9fcf/cmd/csi-node-driver-registrar/node_register.go#L38).

Can you add a comment to /registration? If the node-driver-registrar had a command line option for it, we could use that to document the usage, but /registration is hard-coded in the source (https://github.com/kubernetes-csi/node-driver-registrar/blob/6ef000ae529ad4c8e2928f0803d65ac25f3f9fcf/cmd/csi-node-driver-registrar/node_register.go#L38).

Done.

is this fix available in 1.16?  if yes, which 1.16.x?


Neume grouping

As suggested during the seminar on Monday, there should be a feature to detect grouping of notes <nc> within a <neume>.

I am not sure what this is. @elsinhadl, do you know about this? It seems this was a point Katarina brought up. Do you remember?

If I remember correctly, she was interested in groups of notes within a neume. For example
<syl wordpos="t" xml:id="m-a898a3d6-2fec-11ef-a1ac-3645f29ecd15">te</syl>
  <neume xml:id="m-a898a3f4-2fec-11ef-a1ac-3645f29ecd15">
    <nc xml:id="m-a898a41c-2fec-11ef-a1ac-3645f29ecd15" pname="g" oct="2"/>
    <nc xml:id="m-a898a43a-2fec-11ef-a1ac-3645f29ecd15" pname="a" oct="2"/>
    <nc xml:id="m-a898a458-2fec-11ef-a1ac-3645f29ecd15" pname="b" oct="2"/>
    <nc xml:id="m-a898a480-2fec-11ef-a1ac-3645f29ecd15" pname="c" oct="3"/>
    <nc xml:id="m-a898a49e-2fec-11ef-a1ac-3645f29ecd15" pname="b" oct="2"/>
  </neume>
  <neume xml:id="m-a898a4c6-2fec-11ef-a1ac-3645f29ecd15">
    <nc tilt="n" xml:id="m-a898a4ee-2fec-11ef-a1ac-3645f29ecd15" pname="b" oct="2"/>
    <nc xml:id="m-a898a50c-2fec-11ef-a1ac-3645f29ecd15" pname="a" oct="2"/>
  </neume>
</syl>

The first group of notes (5 notes) is within the first <neume/>, and the second group of notes (2 notes) is within the second <neume/>

To be honest, I don't recall that she was interested in group of notes within a single neume. Perhaps she wanted to search for a specific series of notes (or contour) within a single syllable?

Hmmm, maybe she refer to be able to see the individual neumes in a syllable. In other words, to be able to distinguish the boundaries between one neume and the next in a syllable. That is a Verovio issue. And, thankfully, it is solved now, so we can close this one! :)
See this from the latest main version:

Against this from the latest commit in develop:

Even the oblique ligatures are fixed in this last version (with the downward stroke placed next to the oblique ligature).

Oh that's wonderful! I hope they will update the npm package soon


bug in joint_GMM.h?

log_likelihoods(smpPtr, 1) = 0;
should it be log_likelihoods(smpPtr, 0) ?
similarly some other log_likelihoods(smpPtr, 1) statements

resolved


Add auto-correction for Style/EndBlock cop

Style/EndBlock seems like a simple cop & should support safe auto-correction.

Before submitting the PR make sure the following are checked:

[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Run bundle exec rake default. It executes all tests and RuboCop for itself, and generates the documentation.

Thanks!