Naming Graphs of Custom Monitor Data

Following this link, it shows us how to make custom monitor data graphs. But when the appear, they appear as "CUSTOM MONITOR DATA 1", "CUSTOM MONITOR DATA 2" ...
Is there anyway to give custom names to these graphs?

hello inH4te.
Current custom name it is fixed. (link)
we will think of ways you can modify the name of the chart.

@junoyoon
please comment.

No. it's not possible now...  it's hard-coded in the following location.
https://github.com/naver/ngrinder/blob/develop/ngrinder-controller/src/main/webapp/WEB-INF/ftl/perftest/detail_report/monitor.ftl#L39


Temperature, Humidity, & Light Sensor

  {
    "id": "ZB:6b1301",
    "type_tag": "device_type.lm",
    "type": "LM",
    "name": "Freezer",
    "area": "1",
    "zone": "17",
    "sort_order": "",
    "is_window": "",
    "bypass": "0",
    "schar_24hr": "0",
    "sresp_24hr": "0",
    "sresp_mode_0": "0",
    "sresp_entry_0": "0",
    "sresp_exit_0": "0",
    "group_name": "Sensors",
    "group_id": "<snip>",
    "default_group_id": "1",
    "sort_id": "1",
    "sresp_mode_1": "0",
    "sresp_entry_1": "0",
    "sresp_exit_1": "0",
    "sresp_mode_2": "0",
    "sresp_entry_2": "0",
    "sresp_exit_2": "0",
    "sresp_mode_3": "0",
    "uuid": "<snip>",
    "sresp_entry_3": "0",
    "sresp_exit_3": "0",
    "sresp_mode_4": "0",
    "sresp_entry_4": "0",
    "sresp_exit_4": "0",
    "version": "LMHT_<IP_ADDRESS>TC",
    "origin": "abode",
    "has_subscription": null,
    "control_url": "",
    "deep_link": null,
    "status_color": "#5cb85c",
    "faults": {
      "low_battery": 0,
      "tempered": 0,
      "supervision": 0,
      "out_of_order": 0,
      "no_response": 0
    },
    "status": "-5 \u00b0F",
    "statuses": {
      "temperature": "-5 \u00b0F",
      "temp": "-20.65",
      "lux": "0 lx",
      "humidity": "0 %"
    },
    "status_ex": "",
    "actions": [
      { "label": "High Temperature Alarm", "value": "a=1&z=17&trigger=TSH;" },
      { "label": "Low Temperature Alarm", "value": "a=1&z=17&trigger=TSL;" },
      { "label": "High Humidity Alarm", "value": "a=1&z=17&trigger=HMH;" },
      { "label": "Low Humidity Alarm", "value": "a=1&z=17&trigger=HML;" }
    ],
    "status_icons": [],
    "statusEx": "0",
    "icon": "assets/icons/occupancy-sensor.svg"
  }

It looks like there's already code for this sensor in both Abodepy and Home Assistant. Does this device show up in HA? It looks like Abodepy might be trying to pull the temp, lux and humidity data from the wrong part of the JSON data. This is the function that is being called in abodepy/sensor.py to get the temp, lux and humidity data:
    def _get_numeric_status(self, key):
        """Extract the numeric value from the statuses object."""
        value = self._get_status(key)

        if value and any(i.isdigit() for i in value):
            return float(re.sub("[^0-9.]", "", value))
        return None

This is the _get_status function:
    def _get_status(self, key):
        return self._json_state.get(CONST.STATUSES_KEY, {}).get(key)

It looks like this needs to actually pull the temp, lux and humidity data from the dictionary in the "statuses" key. Unfortunately I don't have one of these devices to test this out...

It looks like this needs to actually pull the temp, lux and humidity data from the dictionary in the "statuses" key.
That's exactly what the _get_status function does. It pulls a key from the statuses dict, and then the _get_numeric_status removes all additional characters other than 0-9 and a decimal point and converts it to a floating point number.

For some reason my sensor does not show up in HA at all. Is there any info I can pull from HA to help diagnose the issue?

Ah, that makes sense. Not sure how I completely missed the CONST.STATUSES_KEY (even though it's in all caps, lol).
@ahutchings Does it show up in the HA logs at all as an unknown device?
I might just order one of these... been looking for a humidity sensor for my house's crawl space.

Well that's a slightly embarrassing oversight on my part. It would seem that I added all the requisite code to support sensors but never added it as something HASS could initialize. That's what happens when I write code I can't actually test. :(

No worries - thanks for getting it to the point where it was a one-liner to fix. :)
Humidity, lux, and temp are all showing up in HA 0.69.0 now, so I'm closing this out.


refactor: make pkce option a client setting

Refactor pkce to be a client setting so it doesn't have to be configured on invocation for each method.

also call exchangeSessionForCode in the background if detectSession is enabled
also remove the flowType option from signInWithOAuth

Leaving this with a refactor: prefix so semver doesn't trigger another release as I'd like to get another three PRs in

remove OAuth flowType param
add magic link binding
add recover bindings
Before making another release


rain: 1.2.0 -> 1.3.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/aws-cloudformation/rain/releases.
meta.description for rain is: A development workflow tool for working with AWS CloudFormation
meta.homepage for rain is: https://github.com/aws-cloudformation/rain
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 1.3.2 with grep in /nix/store/g4ak3yn8k51w1yxlm1zrs6579yc4qqhd-rain-1.3.2
found 1.3.2 in filename of file in /nix/store/g4ak3yn8k51w1yxlm1zrs6579yc4qqhd-rain-1.3.2

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
rain

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/g4ak3yn8k51w1yxlm1zrs6579yc4qqhd-rain-1.3.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A rain https://github.com/r-ryantm/nixpkgs/archive/848de83f8762712258ffcebee562c782f2d3f6bd.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/g4ak3yn8k51w1yxlm1zrs6579yc4qqhd-rain-1.3.2
ls -la /nix/store/g4ak3yn8k51w1yxlm1zrs6579yc4qqhd-rain-1.3.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

rain

Maintainer pings
cc @jiegec for testing.

Wait for next release until upstream fixes the version issue.


Non determinism of Walker AI controllers

Hello everyone,
Thanks for making the Traffic-Manager deterministic in CARLA 9.10.1(#3333). However, the pedestrians with walker AI controllers still seem to behave in non-deterministic ways. This would prohibit users from repeating the simulation over multiple runs.
It would be great if you can let me know if there is already a workaround for making walkers with AI controller *deterministic. Can you let me know if there is a seed within the AI controller that can help me replicate the same simulation over multiple runs?
Thanks in advance.

Has this been fixed in carla 0.9.11?

Has this been fixed in carla 0.9.11?

Hi @pavanteja295, sorry for the delay. @bernatx will come back to you with an answer soon.

Hi @bernatx, do you have any updates on this?

Hi, I will check if adding an specific seed for the Recast & Detour library is enough to get deterministic pedestrians, and I will get back to you. Regards

Hi @bernatx, I also interested in the pedestrian reproducibility. I wonder where I should add the seed for the detour and recast git repo? Do you think it is necessary to modify other walker navigation files? Thank you!

We would find this feature useful as well.  Was it added in 0.9.12?

This feature is not included in 0.9.12 version but it will be in next release in a few weeks.
You can use the dev branch version in the next days where it will be included.

@bernatx  I am still encountering this source of non-determinism in 0.9.13 Any updates on this?


add failing (!) multiple assignment with rest tests

They all fail at the moment. At least one of them may even cause a segfault.

By the way, this is the cause of some crashes posted in #2769. The backtrace is misleading as this is a codegen issue:
*a, _ = []
p a

    1 000 OP_ARRAY      R1      R3      127     ; R1:a    (OOPS!)
    1 001 OP_LOADSELF   R3
    1 002 OP_MOVE       R4      R1              ; R1:a
    1 003 OP_MOVE       R5      R2              ; R2:b
    1 004 OP_SEND       R3      :p      2
    1 005 OP_STOP


How to detect a slow consumer

Hi, according to https://github.com/nats-io/nats-site/blob/master/content/documentation/server/gnatsd-slow-consumers.md#slow-consumers-identified-in-the-client

It is better to catch a slow consumer locally in the client rather than to allow the server to detect this condition. This example demonstrates how to define and register an asynchronous error handler that will handle slow consumer errors.

How to archive this in Node.js?
When my applications run into a "slow consumer" condition no error is emitted. I only get a "REQ_TIMEOUT" on the producer side.
The next question is how can I recover from this state when I can't detect it? Thanks!
In https://github.com/nats-io/node-nats/issues/71 @derekcollison said that we can use an error callback which will let us know if the server dropped messages because the client was too slow. I couldn't find it https://github.com/nats-io/node-nats/blob/master/lib/nats.js#L132

@StarpTech The quick answer is  you cannot.  Multithreaded environments support this feature because the subscription buffers incoming messages while handlers and i/o tasks execute.
In node, user code is single threaded. When a data arrives and node sends an event dispatched to the event loop of the application. That event will trigger parsing of the data, if a message is found it is then dispatched to the subscription. The current inbound processing doesn't try to extract multiple messages as that would introduce an artificial latency. And while all that is going on, no other events can be processed.
If you are running into slow consumer problems, likely you need to scale your subscribers using queue groups so the load of the processing can be fanned out to multiple workers.

@aricart thanks for the explanation.
Theoretically: When I scale up my subscribers in combination with a queue-group it doesn't prevent me from a stale process. NATS will cut off the connection and the client will remain in a broken state without any chance to come back in a clear state.
According to nats documentation:

... When detected in the server, the server will disconnect the connection with the slow consumer to protect itself and the integrity of the messaging system.

so the best case is to restart the client in case of a socket "close" event and of course to scale up your consumers.

@StarpTech if the server disconnects you, your reconnect logic should trigger. Outbound messages in the pending queue should be published. On reconnect, the client will resubscribe. You will lose any messages that were in-flight when you were disconnected.

Yep, disconnect -> reconnecting -> reconnect event is fired, thanks!


TypeError: the JSON object must be str, bytes or bytearray, not NoneType

""" File "C:\Users\dingj\Desktop\testtt\new\main.py", line 5, in
from AppOpener import open
File "C:\Users\dingj\Desktop\testtt\new\venv\Lib\site-packages\AppOpener_init_.py", line 7, in
check.check_json()
File "C:\Users\dingj\Desktop\testtt\new\venv\Lib\site-packages\AppOpener\check.py", line 63, in check_json
create_file()
File "C:\Users\dingj\Desktop\testtt\new\venv\Lib\site-packages\AppOpener\check.py", line 53, in create_file
apps = json.loads(result.stdout)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\dingj\AppData\Local\Programs\Python\Python311\Lib\json_init_.py", line 339, in loads
raise TypeError(f'the JSON object must be str, bytes or bytearray, '
TypeError: the JSON object must be str, bytes or bytearray, not NoneType
Process finished with exit code 1
"""
Using pycharm

and also when I want to run "python setup.py sdist bdist_wheel" it shows "error: invalid command 'bdist_wheel'"..please help

Actually, I would love to solve this but my exams are going on so I'll fix it later. Promise.

@OWO99 AppOpener only works on windows

@OWO99 AppOpener only works on windows

YES I'm using windows

This will be fixed, with AppOpener v1.7 releasing on 10th Of March

@OWO99 are you using Windows XP or Windows 7 or Windows 10?
Note: AppOpener won't run on XP and 7

@athrvvvv Hi, I am facing same issue at the moment, is your fix something you already might have there or still a work in progress? Thanks.

@athrvvvv Hi, I am facing same issue at the moment, is your fix something you already might have there or still a work in progress? Thanks.

I will inform you, about this matter.

Relax guys, releasing AppOpener v1.7 this month!! which solves #15 #11 #13 🤝😊

AppOpener v1.7 just released!! ✌
Install AppOpener v1.7:
pip install AppOpener==1.7

I have added an Exception, if the File creation process failed, it will create files using the old method in AppOpener v1.3
Hope soo, this works!! Btw, thanks @codingbro163  for suggesting the solution 🤝👍
If your Issue is fixed, you may close this now 😊
Lots of love,
athrv ❤


Path to subscription DLQ incorrect

In the 'Path to the dead-letter queue' section, for topics it reads:
<topic path>/Subscription/<subscription path>/$deadletterqueue
but after a lot of struggling to get this to work, I found on other blogs that the correct path should be:
<topic path>/Subscriptions/<subscription path>/$deadletterqueue (note Subscription has become plural).
This then allowed me to access the DLQ as expected.

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

ID: a9c35042-f064-0f34-8d16-ad40e829ca39
Version Independent ID: 19d4a83e-55c8-8b9c-38a0-0e9a26ba2cdb
Content: Service Bus dead-letter queues
Content Source: articles/service-bus-messaging/service-bus-dead-letter-queues.md
Service: service-bus-messaging
GitHub Login: @axisc
Microsoft Alias: aschhab

Hi @SubjectiveKirby Thank you for your feedback! We will review and update as appropriate.

Hi @SubjectiveKirby - Thanks again for reporting this and helping us drive improvements towards MS Docs! I've created a PR that corrects the DLQ path and the change should reflect within 24hrs.
We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Merge prTesting_201904111038 branch to master branch

Docs Build status updates of commit a2fffed:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details
Dependent Files

split/updateTestRef.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


kweb issues

kweb demo has some issues with the hierarchy not showing correctly

@Jan-David-Black
@sebastian-goeldi

I guess this is now pretty obsolete ;)


Accessibility - arrow key drawing

Some people have trouble drawing. If it isn't too high effort, it would be nice to add an accesibility mode that turns on arrow key cursor movement + draw button (double tap to lock). Dragging on screen would only reposition the cursor, not draw
As with all acessibility features, this mode will probably be beneficial for everyone,  making it easier to make precise changes

Hey I’d love to take a shot at this, should this affect object placement too and if so should it be the same interact key?


(FACT-1118) Add 'noatime' option to mountpoint fact

CLA signed by all contributors.

Can you add a short description of why this is needed in the commit message?

Like this? It's not strictly needed for anything, but since it's supported on the operating system level, we might as well display it to the user too, no?

@peterhuene why did we leave it off previously?

Appears to be an oversight.

:+1: for merging then.

It seems we're missing MNT_CPROTECT, MNT_QUARANTINE, MNT_IGNORE_OWNERSHIP, MNT_NOUSERXATTR, and MNT_MULTILABEL on OSX too.

@peterhuene could you please handle that? I don't have an OSX machine around to test that; though I could cook up the patch if you like.

I assume that the above are all OSX specific?

@peterhuene it certainly seems like that; at least I cannot find them on OpenBSD or FreeBSD.

I'll file a ticket for the OSX specific flags.


What is the difference between event.preventDefault() and event.stopPropagation() in JavaScript?

Understanding the Difference Between event.preventDefault() and event.stopPropagation() in JavaScript
JavaScript is used to make websites interactive, and it often has to respond to different actions a user takes, like clicking a button or filling out a form. To do this, JavaScript listens to "events" on a webpage, and sometimes developers use special commands to control these events. Two of those commands are event.preventDefault() and event.stopPropagation(). Although they sound similar, they do different things. Let's explore each one!
What Does event.preventDefault() Do?
event.preventDefault() is used when you want to stop the browser from doing something that it would normally do. For example, when you click on a link, the browser usually takes you to a new webpage. But sometimes, you might want to stop this from happening.  This is where event.preventDefault() comes in.
Here are a few examples of when you might use event.preventDefault():

Stopping a link from opening a new webpage.
Preventing a form from being submitted before all the fields are filled out.

In short, event.preventDefault() blocks the browser's default behavior for an event.
What Does event.stopPropagation() Do?
event.stopPropagation() is used when you want to stop an event from "bubbling" up to other elements. Let me explain what "bubbling" means. In HTML, elements are often nested inside each other. For instance, a button might be inside a div, and that div might be inside a larger section. When you click on the button, JavaScript sees that click event not only on the button but also on all the elements around it, like the div and the section. This process is called "event bubbling."
Sometimes, you want to stop this bubbling. For example, if you click on a button, you may want only the button to react, not the whole page. By using event.stopPropagation(), you can make sure that the event stays only with the button and doesn't affect the other elements.
Here are a few examples of when you might use event.stopPropagation():

Preventing a click on a button from also triggering a click event on its parent element.
Making sure only one specific part of the page reacts to an event without affecting other parts.

In short, event.stopPropagation() stops an event from spreading out to other elements.
Summary: The Key Difference

event.preventDefault() stops the browser’s default action for an event. It’s like telling the browser, "Don’t do what you usually do!"
event.stopPropagation() stops an event from moving up the chain of elements. It’s like telling the event, "Stay here, don’t tell anyone else!"

Knowing the difference between these two commands can help you better control how your webpage behaves, making it more interactive and user-friendly!

Thanks @travisliu! Could you open a PR for this?


[Doc ]

Feature description
Give which tech stack you use in this project for  beginner contributor
Describe the solution
Give Tech Stack you use in this
for example react .js , typescript , like this
Describe alternatives
No response
Additional context
No response
Are you working on this?
None

We use react and tailwind and that we use the TS can be seen here:

What exacty we use can be seen here: https://github.com/getAlby/lightning-browser-extension/blob/master/package.json
I assume that even a beginner contributor can know package.json, what do you think?

thankss


AuthorizationFailure for azure storage sdk

Is OAuth Client credentials supported by the sdk?
I have created service principal.To my storage account I added the role  to this principal  of Storage Account Contributor.
When I run my go app which creates a new directory in the share I get bellow error
RESPONSE 403: 403 This request is not authorized to perform this operation.
ERROR CODE: AuthorizationFailure

Can you share a snippet of code surrounding how you constructing the ManagedIdentity credential.


mass.search service crashes when mass server response contains tracks from spotify

What version of Music Assistant has the issue?
2024.1.0b2
The problem
The problem is that compact_item in services.py tries to pop keys from a list when the dict it receives from the server contains a list of lists.
How to reproduce
I don't really know, but with a spotify account setup, all searches fail when track is checked.
Relevant log output
Here is a stack trace from hass:
homeassistant  | Traceback (most recent call last):
homeassistant  |   File "/usr/src/homeassistant/homeassistant/components/websocket_api/decorators.py", line 26, in _handle_async_response
homeassistant  |     await func(hass, connection, msg)
homeassistant  |   File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 782, in handle_execute_script
homeassistant  |     script_result = await script_obj.async_run(
homeassistant  |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^
homeassistant  |   File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 1587, in async_run
homeassistant  |     return await asyncio.shield(run.async_run())
homeassistant  |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
homeassistant  |   File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 426, in async_run
homeassistant  |     await self._async_step(log_exceptions=False)
homeassistant  |   File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 479, in _async_step
homeassistant  |     self._handle_exception(
homeassistant  |   File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 502, in _handle_exception
homeassistant  |     raise exception
homeassistant  |   File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 476, in _async_step
homeassistant  |     await getattr(self, handler)()
homeassistant  |   File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 713, in _async_call_service_step
homeassistant  |     response_data = await self._async_run_long_action(
homeassistant  |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
homeassistant  |   File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 675, in _async_run_long_action
homeassistant  |     return long_task.result()
homeassistant  |            ^^^^^^^^^^^^^^^^^^
homeassistant  |   File "/usr/src/homeassistant/homeassistant/core.py", line 2149, in async_call
homeassistant  |     response_data = await coro
homeassistant  |                     ^^^^^^^^^^
homeassistant  |   File "/usr/src/homeassistant/homeassistant/core.py", line 2186, in _execute_service
homeassistant  |     return await target(service_call)
homeassistant  |            ^^^^^^^^^^^^^^^^^^^^^^^^^^
homeassistant  |   File "/config/custom_components/mass/services.py", line 69, in handle_search
homeassistant  |     compact_item(item)
homeassistant  |   File "/config/custom_components/mass/services.py", line 62, in compact_item
homeassistant  |     compact_item(subitem)
homeassistant  |   File "/config/custom_components/mass/services.py", line 56, in compact_item
homeassistant  |     item.pop(key, None)
homeassistant  | TypeError: pop expected at most 1 argument, got 2

And here is a problematic reply from the mass server, you can see that external_ids is a list of one element that itself contains a list:
{
   "media_type":"track",
   "item_id":"1lCRw5FEZ1gPDNPzy1K4zW",
   "provider":"spotify",
   "name":"We Are The Champions",
   "provider_mappings":[
      {
         "item_id":"1lCRw5FEZ1gPDNPzy1K4zW",
         "provider_domain":"spotify",
         "provider_instance":"spotify",
         "available":true,
         "audio_format":{
            "content_type":"ogg",
            "sample_rate":44100,
            "bit_depth":16,
            "channels":2,
            "output_format_str":"ogg",
            "bit_rate":320
         },
         "url":"https://open.spotify.com/track/1lCRw5FEZ1gPDNPzy1K4zW",
         "details":"None"
      }
   ],
   "external_ids":[
      [
         "isrc",
         "GBUM71029619"
      ]
   ], ...
}

Additional information
Seems like a server issue, it's strange that external_ids is a list!
What version of Home Assistant Core are your running
2024.1.2
What type of installation are you running?
Home Assistant OS
On what type of hardware are you running?
Linux

We will close this soon if we don’t receive any more info.

Here is an example of a search that fails, but they all fail really when I search for a track:
services: mass.search
data:
  limit: 5
  media_type:
    - track
  name: something

And here is the response when I patch compact_item to handle a list of lists:
artists: []
albums: []
tracks:
  - media_type: track
    item_id: 0Fk2JzsQIhZvfm5AC0FRKG
    provider: spotify
    name: Something Going On
    external_ids:
      - - isrc
        - FRX872019105
    sort_name: something going on
    uri: spotify://track/0Fk2JzsQIhZvfm5AC0FRKG
    duration: 308
    version: Kompa Gouyad Extended Mix
    artists:
      - media_type: artist
        item_id: 2DBaDAcrh5sf17yR1qbnsy
        provider: spotify
        name: Kaysha
        external_ids: []
        sort_name: kaysha
        uri: spotify://artist/2DBaDAcrh5sf17yR1qbnsy
      - media_type: artist
        item_id: 1HbVmlLVon4MWfiMZmZ9kR
        provider: spotify
        name: Dj Benjimix
        external_ids: []
        sort_name: benjimix
        uri: spotify://artist/1HbVmlLVon4MWfiMZmZ9kR
      - media_type: artist
        item_id: 18zQrhTEkqtdwBXW4HTapp
        provider: spotify
        name: Gellokeyzz
        external_ids: []
        sort_name: gellokeyzz
        uri: spotify://artist/18zQrhTEkqtdwBXW4HTapp
      - media_type: artist
        item_id: 00eXN0mxI8gYKIRlrpBD6p
        provider: spotify
        name: G-Mixx
        external_ids: []
        sort_name: g-mixx
        uri: spotify://artist/00eXN0mxI8gYKIRlrpBD6p
      - media_type: artist
        item_id: 6gJHWIsO12jAZRCofnBrEH
        provider: spotify
        name: JustGerdy
        external_ids: []
        sort_name: justgerdy
        uri: spotify://artist/6gJHWIsO12jAZRCofnBrEH
    album:
      media_type: album
      item_id: 1YhWmO4SE7x0h02vgFv5at
      provider: spotify
      name: Something Going On
      external_ids: []
      sort_name: something going on
      uri: spotify://album/1YhWmO4SE7x0h02vgFv5at
      version: Kompa Gouyad Extended Mix
      year: 2020
      artists:
        - media_type: artist
          item_id: 2DBaDAcrh5sf17yR1qbnsy
          provider: spotify
          name: Kaysha
          external_ids: []
          sort_name: kaysha
          uri: spotify://artist/2DBaDAcrh5sf17yR1qbnsy
      album_type: single
playlists: []
radio: []

As you can see, external_ids is a list of lists. Is it by design or a server issue?

Looking at the server source code, it seems expected, see: https://github.com/music-assistant/server/commit/866ad760ce7e7baf6c1fdddaab708a44951d7afc#diff-0978b2897cdb1b19ecb1b4df73d6f8fea8df0b7fc294bc62dfbaf80a7cf70b13R205

Thanks. This will get looked at in due course. If you identify a fix PRs are welcome

Please try again with beta 85 as this is working for me now.

If this is still a problem we can reopen

I am still getting this error, same recreation as above. Whenever I include 'track' as a media_type, the search fails giving the TypeError: pop expected at most 1 argument, got 2 trace. Everything on my system should be up to date though, so I'm curious if this is still broken for anyone else.

Thanks for reopening this, I just opened a PR that should fix this. It seems there may be deeper issues with the external_ids field (should be a flat list?) but it shouldn't be relevant to this PR since even if that is fixed it would still be a list and trigger this edge case.

Can this issue be reopened? After updating to the latest, I still cannot search for tracks from spotify.
fails searching for tracks

succeeds with all other media types

2024.1.0 is the latest release and the fix is not included in that. You can install the repo manually if you need this functionality now, or you can wait until the next release or RC is cut.

2024.2.0 has been released.


V10.0.7 azcopy sync takes a long time to copy last few files

Running AZCOPY V10.0.7 (possibly you have correct in 10.0.8 but here goes)
It seems the AZCOPY sync command is really quick except for the last 10-20 files. It seems to jsut freak out and only copying them very very slowly.

@Kapanther Was this an upload or a download?

Was a download.  From blob to local

Ill see if the behavious is in 10.0 8

Thanks.  In theory, the issue should be fixed, since in <IP_ADDRESS> we fixed the only known cause of that problem.  Will be interesting to hear what you observe.

@johnrusk just to confirm this issue is resolved by 10.0.8.  Thanks guys.  No delay at all now.

@JohnRusk @zezha-msft
Guys not sure what happened in 10.0.9 but this is now back again. 10.0.8 definitely had this fixed.
I have tested in both 'copy' and 'sync' and both seem to just timeout and not copy anything for last 10-200 files.
Any ideas?

Hi @Kapanther .  Sometimes behavior like that can vary from one run to the next.  But 10.0.8 and 10.0.9 are both supposed to take actions to spot the variations in behaviour and remedy them.  It looks like that didn't happen fo you.  Would you be able to send us the log file from the 10.0.9 run?  They log files can be found in the %USERPROFILE%.azcopy directory on Windows.
BTW, log files contain file names, but any SAS tokens used for authentication are redacted and so are not present in the log.

PS. You can email the (zipped) log to us if desired.  Most of us on the team have our real email addresses in our profiles.

@Kapanther Also, if sending a log is not convenient, you can extract just the performance info from the log, and that will probably give us enough to go on. To do so, use PowerShell like this (but replace the log file name with the name of your log file, in %USERPROFILE%\.AzCopy directory).
select-string .\858ebb30-4796-914f-632e-dc355cda0e1c.log -Pattern "PERF" | Out-File perfLines.txt
The above extracts all the performance info into a file named perfLines.txt.

Hi @Kapanther please give the GA version (10.1.0) a try. Thanks!

@Kapanther, I'm about to close this, since we've had no reports of this in the GA version. If you'd like to re-open it, please let us know.


UI_REACT: Enable 'Show types' in main panel display.

Currently 'Show types' appears in the options pull-down menu in the react UI:

It doesn't do anything yet.  It should display the field type as is seen with the angular UI:

Note that the pulldown has a check box (it's toggle-able) - see the 'Toggle mappings column' option for a react equivalent.
Quick build instructions:
Clone a local atlasmap as usual - work from a dev branch off of master
`
cd ./atlasmap
git remote add upstream https://github.com/atlasmap/atlasmap.git
git fetch upstream
git pull -r upstream master
git push origin master
git checkout -b i1523
./mvnw clean install -DskipTests -Pitests
cd ~/git-clone/atlasmap/standalone
../mvnw clean spring-boot:run -Pitests
I like to build the angular UI so I can compare
cd ~/git-clone/atlasmap/ui
./build.sh --skip-tests -Pitests
React
cd ~/git-clone/atlasmap/ui-react/
yarn
yarn build
cd ~/git-clone/atlasmap/ui-react/packages/atlasmap-standalone
yarn start
`
Ref: https://github.com/atlasmap/atlasmap/commit/165626ff596b4f0b421ac489352ead5342d37f6b for something similar

@jpav - Hey - just send any questions my or Riccardo's way.

Actually hold on a bit, I have next in my TODO list a refactoring to move the rendering of the element to the consumer side - so, the App - to allow for any kind of visualization (the preview thingy for example)

@riccardo-forina I guess let me know when I can pursue this.


Annoying non-existent dependency file warnings

I've got these annoying warnings on build:
CMake Warning at /usr/share/cmake-2.8/Modules/FindCUDA/make2cmake.cmake:66 (message):
   Removing non-existent dependency file: generic/THStorage.h

CMake Warning at /usr/share/cmake-2.8/Modules/FindCUDA/make2cmake.cmake:66 (message):
   Removing non-existent dependency file: generic/THStorageCopy.h

CMake Warning at /usr/share/cmake-2.8/Modules/FindCUDA/make2cmake.cmake:66 (message):
   Removing non-existent dependency file: generic/THTensor.h

CMake Warning at /usr/share/cmake-2.8/Modules/FindCUDA/make2cmake.cmake:66 (message):
   Removing non-existent dependency file: generic/THTensorCopy.h

CMake Warning at /usr/share/cmake-2.8/Modules/FindCUDA/make2cmake.cmake:66 (message):
   Removing non-existent dependency file: generic/THTensorRandom.h

CMake Warning at /usr/share/cmake-2.8/Modules/FindCUDA/make2cmake.cmake:66 (message):
   Removing non-existent dependency file: generic/THTensorMath.h

CMake Warning at /usr/share/cmake-2.8/Modules/FindCUDA/make2cmake.cmake:66 (message):
   Removing non-existent dependency file: generic/THTensorConv.h

CMake Warning at /usr/share/cmake-2.8/Modules/FindCUDA/make2cmake.cmake:66 (message):
   Removing non-existent dependency file: generic/THTensorLapack.h

I comment out the line in make2cmake file, but is it possible to do something better with it? These warnings show up whenever you build something with THC.
(Sorry accidentally posted an empty issue in the beginning)

I think the dependencies do exist, just not being located.  I tried adding the TH path to include directories, and that's not sufficient, but I reckon something along those lines might somehow fix it.
INCLUDE_DIRECTORIES("${Torch_INSTALL_INCLUDE}/TH")

Rather than commenting out in make2cmake, one can comment out the following in /usr/share/cmake-2.8/Modules/FindCUDA/run_nvcc.cmake instead.  There might be consequences to this, but doing touch on a .cu file seems to trigger rebuild, when calling via luarocks make.
# Generate the dependency file
#cuda_execute_process(
#  "Generating dependency file: ${NVCC_generated_dependency_file}"
#  COMMAND "${CUDA_NVCC_EXECUTABLE}"
#  -M
#  ${CUDACC_DEFINE}
#  "${source_file}"
#  -o "${NVCC_generated_dependency_file}"
#  ${CCBIN}
#  ${nvcc_flags}
#  ${nvcc_host_compiler_flags}
#  ${depends_CUDA_NVCC_FLAGS}
#  -DNVCC
#  ${CUDA_NVCC_INCLUDE_ARGS}
#  )

#if(CUDA_result)
#  message(FATAL_ERROR "Error generating ${generated_file}")
#endif()

# Generate the cmake readable dependency file to a temp file.  Don't put the
# quotes just around the filenames for the input_file and output_file variables.
# CMake will pass the quotes through and not be able to find the file.
#cuda_execute_process(
#  "Generating temporary cmake readable file: ${cmake_dependency_file}.tmp"
#  COMMAND "${CMAKE_COMMAND}"
#  -D "input_file:FILEPATH=${NVCC_generated_dependency_file}"
#  -D "output_file:FILEPATH=${cmake_dependency_file}.tmp"
#  -P "${CUDA_make2cmake}"
#  )

#if(CUDA_result)
#  message(FATAL_ERROR "Error generating ${generated_file}")
#endif()

# Copy the file if it is different
#cuda_execute_process(
#  "Copy if different ${cmake_dependency_file}.tmp to ${cmake_dependency_file}"
#  COMMAND "${CMAKE_COMMAND}" -E copy_if_different "${cmake_dependency_file}.tmp" "${cmake_dependency_file}"
#  )

#if(CUDA_result)
#  message(FATAL_ERROR "Error generating ${generated_file}")
#endif()

# Delete the temporary file
#cuda_execute_process(
#  "Removing ${cmake_dependency_file}.tmp and ${NVCC_generated_dependency_file}"
#  COMMAND "${CMAKE_COMMAND}" -E remove "${cmake_dependency_file}.tmp" "${NVCC_generated_dependency_file}"
#  )

#if(CUDA_result)
#  message(FATAL_ERROR "Error generating ${generated_file}")
#endif()

The advantage that I see in modifying htis file, rather than make2cmake, is that it is more cuda-specific, and we can just include all these FindCUDA files inside torch, eg inside a cmake directory.

was this ever solved? I get the same thing - install on Ubuntu on a raspberry pi.
The files are there:
$locate THTensorCopy.h

~/torch/install/include/TH/generic/THTensorCopy.h
~/torch/pkg/torch/lib/TH/generic/THTensorCopy.h

But i get that stream of files not found. I edited cmake, but with no luck

Yes, I fixed it in https://github.com/torch/cutorch/pull/256 .  Please try, and confirm works ok, or else let me know any issues.

Note: how to try?  Like this:
git clone https://github.com/torch/cutorch.git
cd cutorch
git remote add hugh https://github.com/hughperkins/cutorch.git
git fetch hugh
git merge hugh/EXPERIMENTAL-improved-dependencies -m "merge"
luarocks make rocks/cutorch-scm-1.rockspec
luajit -l cutorch -e 'cutorch.test()'

this works, thanks Hugh!

Thanks, @hughperkins .  This fixes me! :)

Cool.  @soumith what do you think are reasonable criteria to merge this?  Any particular tests you think it would be good for me to run?  Some kind of travis build perhaps?  I'm guessing for travis, the problem is not so much lack of gpu hardware, so much as, cuda toolkit installation license?

Not sure how well this will work on Mac (since I havent tested this on Mac), but you could try https://github.com/hughperkins/FindCUDA  It is based on cmake 3.5.0-rc1, ie the latest bleeding-edge version of cmake.  I've tested it using cmake 3.2.2, on ubuntu 15.10.

Update: the problem is now solvable very simply.  Simply do:
luarocks install FindCUDA

Thats it! From now on, your builds will be incremental, and will no longer produce streams of warning messages.

Thanks for your hard work !

@hughperkins what a relief, thank you so much! FindCUDA was really an important 'patch' for every cutorch/cunn developer.
General questions: What is the state of this drop-in replacement for FindCuda.cmake? Is it a temporary solution until the official FindCuda gets updated? Does it have to be installed manually after a virgin torch installation via luarocks install FindCuda?

Thanks!

Is it a temporary solution until the official FindCuda gets updated?

I'm not sure I'd label it 'temporary', since cmake wont be updated in LTS ubuntu until maybe 18.04?  It's possible it might be updated in time for 16.04, I havent really checked.  But I guess that 16.04 was taken from Debian sid (or equivalent) a few months ago, and therefore has the old version still?
So, I'd say more 'It is a solution until the official FindCuda gets updated, in ubuntu lts, which might not be until 18.04'

Does it have to be installed manually after a virgin torch installation via luarocks install FindCuda?

It does.  Boris was pushing to have it added into 'distro'.  Personally, I tend to think that the subset of people who install distro who are going to hack on cutorch is pretty small, and maybe what we really want is something like a 'cutorch maintainers  faq', which might also reference FindCUDA install in passing?  But I dont have a strong opinion on this, either way is ok for me :-)

(Note that a 'cutorch maintainers faq' would sort of tie into this https://github.com/torch/cutorch/issues/70#issuecomment-189757152 perhaps? )

(Mind you, I have to say, that the installation is a lot more beautiful after installing FindCUDA . I've added FindCUDA to my own automated installations, so I dont have to watch page after page of spam scrolling past :-D
cd ~
wget https://github.com/hughperkins/FindCUDA/archive/v3.5-1.tar.gz -q -O ~/FindCUDA-v3.5-1.tar.gz
tar -xf FindCUDA-v3.5-1.tar.gz
cd ~/FindCUDA-3.5-1
luarocks make rocks/findcuda-scm-1.rockspec
rm ~/FindCUDA-v3.5-1.tar.gz

Seems like this is a solved problem now?

I'm facing this issue, what's the solution this days? (3 years later :)


Check for error when scanning command output.

          1 Error

:no_entry_sign:
Please include a CHANGELOG entry.

  Generated by :no_entry_sign: Danger

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@aae0f11). Click here to learn what that means.
The diff coverage is 0%.

@@            Coverage Diff            @@
##             master     #430   +/-   ##
=========================================
  Coverage          ?   67.13%
=========================================
  Files             ?      152
  Lines             ?     8895
  Branches          ?        0
=========================================
  Hits              ?     5972
  Misses            ?     2451
  Partials          ?      472

Impacted Files
Coverage Δ

util/shell/command.go
68.29% <0%> (ø)

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 aae0f11...3e86222. Read the comment docs.


RSS feed icon does not open in a new tab

Is your feature request related to a problem? Please describe.
This is mainly an inconsistency that I noticed. When you click on the social icons, it opens in an external tab. However, when you click on the RSS feed icon, it opens in the same tab. This potentially affects UX because it takes the user away from the website.
Describe the solution you'd like
Add a target="_blank" for the feed.
{%- if site.rss_icon -%}                          {% endif %}
Describe alternatives you've considered
N/A
Additional context
N/A

There's no right or wrong with this, happy for people to close this based on interest.


413 Payload Too Large - Option to change body-parser limit

I am running to a 413 Payload Too Large while using graphql-yoga directly.
My request payload size is around ~130KB.
As I understand this is happening because we are using body-parser-graphql which relies on the default limit value of body-parser which is 100KB.
Possible solutions are

Pass options supported by body-parser in body-parser-graphql and pass them through.
Pass just the limit option in body-parser-graphql and pass it through to body-parser
Hardcode a higher value as limit in body-parser-graphql to mitigate this issue.

Please let me know if this can be done? I can take it up.
Thanks!

As we have to touch body-parser-graphql anyways, let's go for the clean option, which is 1)

Related PRs
https://github.com/graphql-middleware/body-parser-graphql/pull/38
https://github.com/graphcool/graphql-yoga/pull/266

This is closed now.


Add edit icon to all edit buttons

Add icons to more common buttons, such as the pen icon to the edit button. Icons make it easier to recognize the function of the button.

@sepidehshahi how about the pencil-alt icon found here? https://heroicons.com

works for me @greatislander


Update show.html.erb

Fixes #97

@audiolion Thanks for your contribution to Open Source Friday! You rock!


Add details kebab

Refactored the modals which display all tags, projects, historical data, and export. This allows the modals to be lazily launched from a kebab in addition to the expanding row area.
Note that some kebab options may be disabled. For example, "View all projects" is disabled when grouped by project and node. The "View all tags" option is enabled only when grouped by projects.
Fixes https://github.com/project-koku/koku-ui/issues/627
OCP project:

OCP cluster:

AWS:

Codecov Report

Merging #750 into master will decrease coverage by 0.01%.
The diff coverage is 60%.

@@            Coverage Diff             @@
##           master     #750      +/-   ##
==========================================
- Coverage   76.89%   76.88%   -0.02%
==========================================
  Files         229      229
  Lines        3813     3815       +2
  Branches      665      665
==========================================
+ Hits         2932     2933       +1
- Misses        792      793       +1
  Partials       89       89

Impacted Files
Coverage Δ

src/api/ocpOnAwsReports.ts
85% <ø> (ø)
:arrow_up:

src/store/ui/uiReducer.ts
100% <ø> (ø)
:arrow_up:

src/store/ui/uiActions.ts
100% <ø> (ø)
:arrow_up:

...ages/ocpOnAwsDashboard/ocpOnAwsDashboardWidget.tsx
72.22% <0%> (ø)
:arrow_up:

src/store/ocpExport/ocpExportReducer.ts
100% <100%> (ø)
:arrow_up:

src/store/ocpOnAwsExport/ocpOnAwsExportReducer.ts
100% <100%> (ø)
:arrow_up:

src/store/awsExport/awsExportReducer.ts
100% <100%> (ø)
:arrow_up:

src/store/ui/uiSelectors.ts
87.5% <0%> (-12.5%)
:arrow_down:

Continue to review full report at Codecov.

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


Fontsize in MathML

Hi!
I can't increase font size of the MathML equations (that inserted in MS Word by Python-docx).
Standart MathML attributes like mathsize or maxsize or scriptminsize don't work.
There are no any problems with the running of code but MathML equation has CambriaMath font with font size 11 (I need to make it 14).
Any others attributes for setup the math font (like fontweight or fontcolor others) don't work.
What I do wrong?
Here is an example of code that I used:
    from sympy import*
    from sympy.abc import*
    from sympy.printing.mathml import mathml
    from lxml import etree

    math_ml = '''
    <math xmlns="http://www.w3.org/1998/Math/MathML" mathsize='50pt' fontweight='bold'>
        <mstyle>
        <msub>
            <mi>t</mi>
            <mi>Н-Р</mi>
        </msub>
        <mi>=</mi>
        <mfrac>
        <msrow>
            <msub>
                <mi>t</mi>
                <mi>Н</mi>
                </msub>
                <mi>+</mi>
                <msub>
                    <mi>t</mi>
                    <mi>Р</mi>
                </msub>
                <mi>+</mi>
                <msub>
                    <mi>t</mi>
                    <mi>Д</mi>
                </msub>
            </msrow>
            <mn>60</mn>
        </mfrac>
        </mstyle>
    </math>'''

    tree = etree.fromstring(math_ml)
    mml2omml_stylesheet_path = 'MML2OMML.XSL'
    xslt = etree.parse(mml2omml_stylesheet_path)
    transform = etree.XSLT(xslt)
    new_dom = transform(tree)

    doc = docx.Document ()
    p = doc.add_paragraph()
    p._element.append(new_dom.getroot())

    report.save('Report.docx')```

Your code does not seem to involve MathJax in any way, so it is probably misplaced to report the issue here.  The problem is probably with the XSLT stylesheet that is converting the MathML, but again, that has nothing to do with MathJax.  It may be that the xsl file doesn't handle mathsize and fontweight properly, for example.  Note that fontweight, 'fontfamily,  fontsize, color, backgroundand similar attributes are deprecated in MathML3 in favor of directly settingstyleproperties, or usingmathsize, mathcolor, and mathbackground.  There never was a fontcolor` attribute.
From a Google search, the xsl stylesheet you are using appears to be a Microsoft product, so you will have to report the issue to them.
As an aside, your MathML is not correct.  The <msrow> tag should only appear within <mstack> or < mlongdiv>, so is missed here.  It should just be an <mrow>.  Also, your <mi>=</mi> and <mi>+</mi> probably should be <mo>=</mo> and <mo>+</mo> to get the semantics and the spacing correct.  Finally, your <mstyle> is unneeded, since it sets no styles.  Your indenting is also off, though that doesn't affect the output.
Finally, although you are not using MathJax, MathJax does render the MathML properly (once the <msrow> is changed to an <mrow>), in the larger font size, and with bold.


[git#1] Search & checkout remote branches

At the moment, in the Branch Select dropdown we only show the local branches, but we already have access to list the remote branches.
We should allow users to search for remote branches and checkout them locally. This should probably be in a separate dropdown or a modal which needs to be designed.

UI for this: https://www.figma.com/file/ysPkVjIsd1JA4cttEWcVJM/Git-for-Desktop?node-id=1%3A700


Expose node position in input string

I'd like to know the position in the input string each node is at. I'm working on sqlc support for inserting multiple rows and want to find the location of the VALUES clause in the input string to repeat it for each row.
(I know COPY FROM is better, faster and stronger - but it lacks ON CONFLICT)

Hi @Jille,
Generally speaking, node positions are already tracked - but unfortunately only at the level of individual A_Const nodes. Here is an example with the Ruby library (same approach applies to Go, its just easier to prototype for me):
q = "INSERT INTO x VALUES (1,2), (3, 4)"
PgQuery.parse(q).tree.stmts[0].stmt.insert_stmt.select_stmt.select_stmt.values_lists.map {|i| i.list.items.map {|j| j.a_const.location } }
=> [[22, 24], [29, 32]]

For reference the relevant portion of the parse tree (i.e. one item in the VALUES list), looks like this here:
<PgQuery::Node: list: <
  PgQuery::List: items: [
    <PgQuery::Node: a_const: <PgQuery::A_Const: val: <PgQuery::Node: integer: <PgQuery::Integer: ival: 1>>, location: 22>>,
    <PgQuery::Node: a_const: <PgQuery::A_Const: val: <PgQuery::Node: integer: <PgQuery::Integer: ival: 2>>, location: 24>>
  ]
>>

Now I assume it would be helpful in your case if the List node (i.e. above the A_Const nodes), had a location attached - since the individual constant locations will not match the exact start of each row (e.g. in this example position 22 is the first value "1", instead of the opening parenthesis "(").
However, short of a patch to the Postgres portion of the parser, this can't be easily added. What's more, unfortunately the Node element in question (List), is very commonly used - its also special in the sense that whilst its a valid parse node, the node definition is kept separate (directly in pg_list.h), and its often used in contexts outside the parse tree - so its very unlikely that an upstream patch would be accepted that adds a location field to that node.
Now we could potentially carry an additional patch to the Postgres source (we already have a small set), that adds location to the List node - my main worry there is that we're making all parser outputs a lot bigger (though we could mitigate that by gating this via an extra flag), and that we have one more patch to rebase for each new version. So this would be possible, but time intensive with a small amount of long-term maintenance overhead.
Thus, overall, I would focus on the first element on each list, and then go back one token to find the actual starting point of the row. You can use the scanner to find the token positions, here again a Ruby example for reference:
PgQuery.scan("INSERT INTO x VALUES (1,2), (3, 4)")[0].tokens
=> [<PgQuery::ScanToken: start: 0, end: 6, token: :INSERT, keyword_kind: :UNRESERVED_KEYWORD>,
 <PgQuery::ScanToken: start: 7, end: 11, token: :INTO, keyword_kind: :RESERVED_KEYWORD>,
 <PgQuery::ScanToken: start: 12, end: 13, token: :IDENT, keyword_kind: :NO_KEYWORD>,
 <PgQuery::ScanToken: start: 14, end: 20, token: :VALUES, keyword_kind: :COL_NAME_KEYWORD>,
 <PgQuery::ScanToken: start: 21, end: 22, token: :ASCII_40, keyword_kind: :NO_KEYWORD>,
 <PgQuery::ScanToken: start: 22, end: 23, token: :ICONST, keyword_kind: :NO_KEYWORD>,
 <PgQuery::ScanToken: start: 23, end: 24, token: :ASCII_44, keyword_kind: :NO_KEYWORD>,
 <PgQuery::ScanToken: start: 24, end: 25, token: :ICONST, keyword_kind: :NO_KEYWORD>,
 <PgQuery::ScanToken: start: 25, end: 26, token: :ASCII_41, keyword_kind: :NO_KEYWORD>,
 <PgQuery::ScanToken: start: 26, end: 27, token: :ASCII_44, keyword_kind: :NO_KEYWORD>,
 <PgQuery::ScanToken: start: 28, end: 29, token: :ASCII_40, keyword_kind: :NO_KEYWORD>,
 <PgQuery::ScanToken: start: 29, end: 30, token: :ICONST, keyword_kind: :NO_KEYWORD>,
 <PgQuery::ScanToken: start: 30, end: 31, token: :ASCII_44, keyword_kind: :NO_KEYWORD>,
 <PgQuery::ScanToken: start: 32, end: 33, token: :ICONST, keyword_kind: :NO_KEYWORD>,
 <PgQuery::ScanToken: start: 33, end: 34, token: :ASCII_41, keyword_kind: :NO_KEYWORD>]

start: 21, end: 22, token: :ASCII_40 is the parenthesis that starts the first row, start: 28, end: 29, token: :ASCII_40 is the parenthesis that starts the second row, etc.
In Go that data is accessible via the Scan function.
Hope that helps!

Nice, I can make that work. Thanks for the detailed reply Lukas!


Show if checkboxes (and radios?) are not found in the DOM

Show if checkboxes with multiple options use things like _field_1[B'encodedStr'] instead of their var name. That _field_n can be found in the encoded part of the input id. For example, in the id X2ZpZWxkXzM_0 the X2ZpZWxkXzM might be decoded into _field_1[B'encodedStr'] or something.
We can find which variable name corresponds to _field_n encoded in the value attribute of an input element whose name attribute is _varnames. See _varnames in #173.
We hope work on this is going to be part of the big refactor for proxy variables (like index variables), #158.

This has been fixed in one of the PRs for #158.


Parallel calling

Changes to allow WES CNV calling.

Bams & bais download in parallel. Addresses #11
New option "scatter" to run cnv calling in multiple subjobs
Bump up timeout to 4h & instance type to x16
Make run_name non-optional to fix #12
Variable references fixed in calls to parallel
Step 4 (cnv calling) now scatters intervals & runs separate jobs if requested
PostProcess step now uses batch input string to accommodate potential parallel call directories

Initial testing - https://platform.dnanexus.com/panx/projects/Gj2jj604ByG4z4z5j0VzyX8P/monitor

This change is

closing as superseded by #19


Make exclusions part of the policy interface

With this PR, the exclusions interface of Trireme changes and any excluded networks are provided
as part of the policy resolution. This both simplifies the design and allows the dynamic update of
the networks that need to be excluded.

Codecov Report

Merging #197 into master will decrease coverage by 0.02%.
The diff coverage is 56.6%.

@@            Coverage Diff             @@
##           master     #197      +/-   ##
==========================================
- Coverage   49.38%   49.35%   -0.03%
==========================================
  Files          33       33
  Lines        4360     4194     -166
==========================================
- Hits         2153     2070      -83
+ Misses       2017     1928      -89
- Partials      190      196       +6

Impacted Files
Coverage Δ

supervisor/supervisormock.go
0% <ø> (ø)
:arrow_up:

supervisor/supervisor.go
69% <ø> (+5.11%)
:arrow_up:

supervisor/iptablesctrl/iptables.go
51.53% <0%> (-2.46%)
:arrow_down:

cmd/remoteenforcer/remoteenforcer_linux.go
0% <0%> (ø)
:arrow_up:

trireme.go
49.61% <100%> (-0.39%)
:arrow_down:

supervisor/iptablesctrl/acls.go
70.68% <64.44%> (+3.73%)
:arrow_up:

monitor/linuxmonitor/linuxMonitor.go
68.62% <0%> (+6.86%)
: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 a0b2dd6...5efc489. Read the comment docs.


[topgen] Alert handler integration

Carried over from #675 and rebased onto master.
This PR is a first attempt to integrate the alert handler into the top level generator. For this purpose, the hmac has been extended with a "dummy alert" that is derived from an internal error signal.
Topgen has been extended to support alerts in the same way as interrupts - i.e., the alerts can be specified in the hjson of a module in order to have them automatically connected to the alert handler on the top-level. I the future we might extend reggen to provide alert testing registers (similar to the interrupt testing registers) as well.
The four escalation signals that are currently output by the alert handler are connected to a helper peripheral named nmi_gen which simply converts the received escalation signals to regular interrupts such that the mechanism can be tested. This is going to be changed in the future once "real" hardware countermeasures are available. The PR introducing the nmi_gen is here #894 .
Note that this PR is also gated by an interface change in the alert handler rx/tx primitives which makes top-level wiring a bit simpler #906.
Also note that by default, pings are disabled and no escalation protocol is configured. Hence the change should not affect existing dv and software infrastructure. I successfully ran the top-level sanity check in VCS, and the OpenOCD compliance tests in Verilator.
Signed-off-by: Michael Schaffner<EMAIL_ADDRESS>

Ok, I amended a few things and rebased onto the newest master. Lint is clean except for nmi gen which needs some additional waivers. Chip sanity works in VCS, and the OpenOCD testsuite passes in Verilator.
@cindychip @eunchan @tjaychen  since I am not going to be around for a while, feel free to merge this PR if there are no other issues (in order to prevent it from becoming stale again).

thanks @msfschaffner ! i'll pull this locally also to have a quick look, and hopefully afterwards will approve!
Thanks for the work!

Hi Michael, I send you a PR request on your branch: https://github.com/msfschaffner/opentitan/pull/3 for the DV change I suggested. Let me know what you think.

Thanks @msfschaffner for the PR. I have some minor comments only. Question: The NMIs are all connected to the PLIC. Shouln't one of the NMIs be connected to the NMI input of the core (irq_nm_i)? This is the only real NMI in the system. Everything else can be masked (both at the PLIC level and inside the core).

Thanks for reviewing @vogelpi!
Yes that is the plan, but we have not really discussed the actual escalation signalling strategy yet. I added a dummy peripheral called nmi_gen in order to be able to sink the four escalation signals and provide an easy way to run first tests on the top-level. Also, I did not want to break the current system by connecting the AH to a "real" NMI before we finished the block-level DV/FPV on the AH.
I suggest we do not wire up the NMI until we are sure that 1) the AH works correctly, and 2) that we have an idea of our escalation signalling strategy. The nmi_gen peripheral may change or even disappear in the future.

Hi Michael, I send you a PR request on your branch: msfschaffner#3 for the DV change I suggested. Let me know what you think.

Thanks @cindychip, I'll take a look and merge it into my PR.

I suggest we do not wire up the NMI until we are sure that 1) the AH works correctly, and 2) that we have an idea of our escalation signalling strategy. The nmi_gen peripheral may change or even disappear in the future.

Makes sense to me, thanks for clarifying this Michael.

@cindychip I had to update a couple of things and hence I rebased your commit into this PR (instead of using the merged PR you made). could you PTAL?

@cindychip @eunchan let me know when HMAC is ready to move this one in.

Sure, thanks for the reminder. I will wait a weekend for this PR
https://github.com/lowRISC/opentitan/pull/949, in case people have some
last min comments.
Once the sign off PR is merged, feel free to merge the alert handler.
On Fri, Nov 22, 2019 at 5:01 PM Michael Schaffner<EMAIL_ADDRESS>wrote:

@cindychip https://github.com/cindychip @eunchan
https://github.com/eunchan let me know when HMAC is ready to move this
one in.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lowRISC/opentitan/pull/918?email_source=notifications&email_token=ACXPOOLPACF436DGV6N5HU3QVB6GJA5CNFSM4JKMHDS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEE7I7FQ#issuecomment-557748118,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACXPOOPILGG6WE2SDPC74CDQVB6GJANCNFSM4JKMHDSQ
.

Thanks @cindychip. I'll rebase this one such that we can merge it.

@eunchan @sjgitty @cindychip  shall I bounce HMAC back to D2/V2 with this PR?

@eunchan @sjgitty @cindychip shall I bounce HMAC back to D2/V2 with this PR?

Sounds like D2/V1. new feature that needs a new test.

Updated hmac.prj.hjson to bounce the module back to D2/V1 due to the added alert.


use ipv6 to connect to the server

if i try and connect to my vm via ipv6 it wont connect, please help me...
[Interface]
PrivateKey = PRIVATE_KEY
Address = <IP_ADDRESS>/24,fd42:42:42::3/64
DNS = <IP_ADDRESS>,<IP_ADDRESS>,2a00:5a60::ad1:0ff,2a00:5a60::ad2:0ff
MTU = 1420
[Peer]
PublicKey = PUBLIC_KEY
AllowedIPs = <IP_ADDRESS>/0,::/0
Endpoint = 2604:a880:400:d1::7d0:6001:51820
PersistentKeepalive = 0

it says unable to parse endpoint as error.
IPV6 > IPV6

fix:
Endpoint = [2604:a880:400:d1::7d0:6001]:51820


WFLY-10736 Workaround for JGRP-2294.

https://issues.jboss.org/browse/WFLY-10736

No longer necessary, as 4.0.15.Final was just released and contains fix.


WIP: feat(): update to capacitor3

Android

[ ] Card verification
[ ] Card tokens
[ ] Source tokens
[ ] PII tokens
[ ] Account tokens
[ ] Payment Methods
[ ] Payment Intents
[ ] Setup Intents
[ ] Google Pay
[x] Apple Pay

iOS

[ ] Card verification
[ ] Card tokens
[ ] Source tokens
[ ] PII tokens
[ ] Account tokens
[ ] Payment Methods
[ ] Payment Intents
[ ] Setup Intents
[x] Google Pay
[ ] Apple Pay

Web

[ ] Card verification
[ ] Card tokens
[x] Source tokens
[ ] PII tokens
[ ] Account tokens
[ ] Payment Methods
[ ] Payment Intents
[ ] Setup Intents
[x] Google Pay
[x] Apple Pay

https://github.com/capacitor-community/stripe/compare/master...paystory-de:master

Amazing!

https://github.com/capacitor-community/stripe/releases/tag/v3.0.0-0

Few issues still there on iOS:
Android build is fine.
❌  /Users/vagrant/git/node_modules/@capacitor-community/stripe/ios/Plugin/PKAuthViewDelegate.swift:41:102: cannot convert value of type 'Error?' to expected argument type 'String?'
                    callback.reject("unable to create payment method: " + err!.localizedDescription, err)
❌  /Users/vagrant/git/node_modules/@capacitor-community/stripe/ios/Plugin/PKAuthViewDelegate.swift:53:93: cannot convert value of type 'NSError?' to expected argument type 'String?'
                            callback.reject("payment failed: " + err!.localizedDescription, err)
❌  /Users/vagrant/git/node_modules/@capacitor-community/stripe/ios/Plugin/PKAuthViewDelegate.swift:79:93: cannot convert value of type 'Error?' to expected argument type 'String?'
                    callback.reject("unable to create token: " + err!.localizedDescription, err)

and
        call.error("Google Pay is not available on iOS")
             ^~~~~
             reject
/Users/vagrant/git/node_modules/@capacitor-community/stripe/ios/Plugin/StripePlugin.swift:668:33: warning: 'getSavedCall' is deprecated: renamed to 'savedCall(withID:)'
        if let c = self.bridge?.getSavedCall(ctx.callbackId) {
                                ^
/Users/vagrant/git/node_modules/@capacitor-community/stripe/ios/Plugin/StripePlugin.swift:668:33: note: use 'savedCall(withID:)' instead
        if let c = self.bridge?.getSavedCall(ctx.callbackId) {

@patrickbussmann Thanks for check working. I fixed and pre-released 3.0.0-1. This is still working.

https://github.com/capacitor-community/stripe/releases/tag/v3.0.0-1

@rdlabo do we have documentation to follow?
ie
Vue
Angular

@donPuerto not yet. For the time being, I plan to spend my time on refactoring and feature checking.
But Capacitor 3 don't support IE, so this plugin don't support IE too. Thanks.

@rdlabo Thanks for the work mate. Yeah dump that IE :)

Secret key of Stripe is not public key. This plugin suggest input secret key to code. This is not recommended.
It seems that it will need to be remade into a completely new style in v3 support.

Secret key of Stripe is not public key. This plugin suggest input secret key to code. This is not recommended.
It seems that it will need to be remade into a completely new style in v3 support.

You mean removing the secret key?
Can we help you somehow with this new style?

@rdlabo
Hi team!
I think we should remove these classes and methods.
https://github.com/capacitor-community/stripe/blob/feat/v3/src/web.ts#L376-L430
https://github.com/capacitor-community/stripe/blob/feat/v3/src/web.ts#L319-L373
There using a Stripe secret key, but the key should not use on the frontend.
I think we should recreate it to follow the Stripe JavaScript SDK.
If you wanna try this, I can help you.

@patrickbussmann @hideokamoto YES. I will remove secret key and method of using this.
Currently this plugin can create payment alone. But will be change to have to using backend. The big role of the plugin will be to create a payment UI.
I will do the rough development, so I would appreciate it if you could help me with the tests and reviews.

I get no response from Google Pay.
 const { success, token } = (await stripePlugin.payWithGooglePay({
gets never resolved.

gets never resolved.

Because of missing upgrade: https://capacitorjs.com/docs/updating/plugins/3-0#android-request-codes
Lets give @rdlabo some time. Then we can start writing tests and then all people can start using this with Capv3.

@patrickbussmann @hideokamoto YES. I will remove secret key and method of using this.
Currently this plugin can create payment alone. But will be change to have to using backend. The big role of the plugin will be to create a payment UI.
I will do the rough development, so I would appreciate it if you could help me with the tests and reviews.

Do you have time to take a look into that issue?

@hideokamoto I created draft of web implements.
https://github.com/capacitor-community/stripe/pull/74/commits/d2b0d2199a0a88b0f988135f29248024b59fccae
Stripe's "Elements" is not useful for Plugin, so we should create Web Components like PaymentSheet in iOS & Android. Can you create with StencilJS?

YES!!!!

This is Android!!

Released: https://github.com/capacitor-community/stripe/releases/tag/v3.0.0-2
Support only these method:

initialize
createPaymentSheet
presentPaymentSheet

ApplePay and GooglePay is included at PaymentSheet. So these method is removed.

Released: https://github.com/capacitor-community/stripe/releases/tag/v3.0.0-2
Support only these method:

initialize
createPaymentSheet
presentPaymentSheet

ApplePay and GooglePay is included at PaymentSheet. So these method is removed.

README is here: https://github.com/capacitor-community/stripe/tree/feat/v3
Demo Implements is here: https://github.com/capacitor-community/stripe/tree/feat/v3/demo

 Stripe.addListener(PaymentSheetEventsEnum.Completed, (response) => {
      console.log('PaymentSheetEventsEnum.Completed', response);
    });

@danielehrhardt Thanks try and sorry missing. I fixed type and release at https://github.com/capacitor-community/stripe/releases/tag/v3.0.0-3
If it is possible, please try again. Thanks.

@danielehrhardt Thanks try, and sorry mistake. I fixed type and release at https://github.com/capacitor-community/stripe/releases/tag/v3.0.0-3
If it is possible, please try again. Thanks.

To be on the safe side I added your case to the demo app so that the build process will fail when its an issue.
https://github.com/capacitor-community/stripe/pull/78

@danielehrhardt @patrickbussmann Thanks for try🙏
I will merge to master branch. Let's discuss Individual new issues!


[🐞] Multiple rewrites paths casuing a RegExp error

Which component is affected?
Qwik City (routing)
Describe the bug
For some reason, defining the same path 3 times causes the rewrite routes function to throw
I've already added a test to the core that proves that and I'm going to fix it
Reproduction
not relevant
Steps to reproduce
for the following configuration of the qwik-city vite plugin:
rewriteRoutes: [
    {
      prefix: 'de',
      paths: {
        produkt: 'produkt',
      },
    },
    {
      prefix: 'no',
      paths: {
        produkt: 'produkt',
      },
    },
    {
      prefix: 'fi',
      paths: {
        produkt: 'tuote',
      },
    },
  ],

The rewriteRoutes function throws an error
System Info
not relevant

Additional Information
No response

fixed by #6377


fetch api protocol?

Now we are using React Native version 0.4 with Fetch API. Since we cannot capture the request from Fetch while using a third-party security tunnel, we cannot know what protocol the Fetch implements either. Is it HTTP, HTTP/2 or websocket?

We're cutting down on the number of outstanding issues, in order to allow us to focus. I'm closing this issue because it has been open for over 60 days with no activity. If you think it should still be opened let us know why. PRs are always welcome.


Fix basetoken related issues on in publish and asset detail pages

Fixes #1855 #1863 .
Changes proposed in this PR:

fix infinite price loading
test asset: https://market.oceanprotocol.com/asset/did:op:2f2cd3221dfc80540d753cfad6859fe84e62327f5d7f95387170f4f4136b7d82
fixed baseToken update in publish form when switching networks
fix footer text when there are ve Allocations but no sales or sales are not available, see issue below

So i filled the from on goerli until the last step, then i switched to mumbai and i got this error at Create token and pricing

another test, didn't get an error, just stuck in loop, switched from mumbai to goerli in last step. The basetoken address is updated .

another test, didn't get an error, just stuck in loop, switched from mumbai to goerli in last step. The basetoken address is updated .

I couldn't replicate this. I can change to any network in the last step without issues (basetoken gets updated, tx runs correctly).


Unable To Use Damaged Crafting Tools

Hey!
The Cooking Table is unable to use the Actually Additions Knife, and the Carving Knife from Animania after the first use. It still detects the AA Knife, but is unable to use it.
Forge 1.12.2-<IP_ADDRESS>73
CookingForBlockheads_1.12.2-6.3.26
ActuallyAdditions-1.12.2-r134

Thank you :)


fix(freertos): Made select function non-blocking on Linux target (IDFGH-13569)

The select function wrapper was rewritten to be non-blocking on Linux systems, as it was stealing all the CPU time from lower priority tasks when called from a higher priority task. This is because the FreeRTOS scheduler does not know that the task thread is sleeping during the system call.
This issue manifests all "slow" system calls on the Linux target, but handling the case of select fixes the problems for most ESP-IDF components.
The FreeRTOS POSIX port documentation lists this as a known issue, so user code is responsible handling this case if other system calls are used, even if unknowingly.
This closes the GH issue #14395 "select() blocks the FreeRTOS scheduler on Linux target".
Additional Notes

I'd suggest adding a note and a reference to this section of the FreeRTOS documentation to the ESP-IDF documentation.
The fix can be confirmed by running the code in my previous bug report #14395.

Hi @snake-4, this looks like a great improvement!
The only question I have here is how did you determine the number of 10 ticks for waiting? Is there a reasoning why it's exactly 10 or could it be something else, too?

There's no specific reason why it's 10 but it has to be at least 1 tick to let the FreeRTOS scheduler know that lower priority tasks may run. Although, at 1 tick delay, it would take up 50% of the simulator's CPU time (not the actual host CPU time). A delay of 10 ticks seemed like a good trade-off.
I'll refer to threads that are not scheduled by the FreeRTOS scheduler as raw threads and FreeRTOS tasks as just tasks below.
The reason why polling is used is because while it is possible to signal raw threads from tasks (using pthread), other way around is not possible as a FreeRTOS semaphore would have to be used. The simulator does not expect the FreeRTOS APIs to be called from raw threads and doing so will cause issues as mentioned here.
A method for achieving what I've said above could be done by modifying the FreeRTOS scheduler's internal state to immediately schedule the task waiting on IO upon completion, but this approach would require modifying the simulator's source code.

As per my original post, all blocking host system calls (except select) will be considered as "work" by the FreeRTOS scheduler. This includes usleep as well.


Dialogflow: Memory leak when a client is created and immediately closed

Thanks for stopping by to let us know something could be better!
PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.
Please run down the following list and make sure you've tried the usual "quick fixes":

Search the issues already opened: https://github.com/GoogleCloudPlatform/google-cloud-node/issues
Search StackOverflow: http://stackoverflow.com/questions/tagged/google-cloud-platform+node.js
Check our Troubleshooting guide: https://googlecloudplatform.github.io/google-cloud-node/#/docs/guides/troubleshooting
Check our FAQ: https://googlecloudplatform.github.io/google-cloud-node/#/docs/guides/faq

If you are still having issues, please be sure to include as much information as possible:
Environment details

which product (packages/*): @google-cloud/dialogflow
OS: All
Node.js version: 18.16.0
npm version: 9.5.0
google-cloud-node version: 5.7.1

Steps to reproduce
import Dialogflow from '@google-cloud/dialogflow';

const opts = {
  servicePath: "dialogflow.googleapis.com",
  port: 443,
  clientConfig: {
  },
  fallback: false,
  credentials: {
    private_key: "...",
    client_email: "...",
  },
  projectId: "...",
  scopes: [
    "https://www.googleapis.com/auth/cloud-platform",
    "https://www.googleapis.com/auth/dialogflow",
  ],
  apiEndpoint: undefined,
};
const conversationProfilesClient = new Dialogflow.ConversationProfilesClient(opts);
await conversationProfilesClient.close();

The constructor creates operationsClient which tries to connect and registers itself in channelz, but the ctor doesn't assign anything to conversationProfilesStub, so close is no-op. We're left with a memory leak in channelz.
Our use-case was creating this object for calling projectLocationConversationProfilePath (why are these functions not static?).

Other objects like ConversationClient and more have the same issue.


What is Entity.setExtraData(); do?

can anyone tell me?

Set the entityes NBT tag. Not sure about its syntax, but things like {CustomNameVisible:0} are possible (for making jeb sheeps or Dinnerbone/Grumm entityes that dont show the nametag).
Also I am not sure if this is an issue exactly....

thx


Changing sidebar color doesn't work at all

When I change the data-color attribute in the sidebar div (http://prntscr.com/kq9chj) it doesn't change and shows brown. (http://prntscr.com/kq9cu2)
Any ideas?

Hello @xmadscientist,
Thank you for using our products, the free version has only 2 colors for the sidebar (white and dark).
Best,
Stefan

@groovemen I paid $300 for the admin dashboard.


WRP-7678: Upgrade less-loader dependency to latest version

Checklist

[x] I have read and understand the contribution guide
[x] A CHANGELOG entry is included
[ ] At least one test case is included for this feature or bug fix
[x] Documentation was added or is not needed
[ ] This is an API breaking change

Issue Resolved / Feature Added
Less-loader needs to be in sync with the version enact cli is using.
Resolution
Updated less-loader dependency to v11.
There were no breaking changes affecting our code https://github.com/webpack-contrib/less-loader/releases.
Additional Considerations
Minimum supported Node.js version is now 14.15.0 (https://github.com/webpack-contrib/less-loader/releases/tag/v11.0.0).
Links
WRP-7678
Comments
Enact-DCO-1.0-Signed-off-by: Stanca Pop<EMAIL_ADDRESS>

In less-loader v10.0.0, there an API change exists: https://github.com/webpack-contrib/less-loader/releases/tag/v10.0.0
Is it possible to check if this API change does not affect the storybook-utils?
I'll merge it as soon as it's checked.

In less-loader v10.0.0, there an API change exists: https://github.com/webpack-contrib/less-loader/releases/tag/v10.0.0 Is it possible to check if this API change does not affect the storybook-utils? Please answer this question and describe on Additional Considerations in the PR description.
I'll merge it as soon as it's checked.

API change from release v10.0.0 does not affect the storybook-utils.


Fixed setup.py to include all the files and packages.

In setup.py, you need to provide all the packages and not just top level packages.  As a result when you install buffer-python using pip, buffpy/model and buffpy/manager  packages is not available.

Thumbs up!

Any chance of this getting fixed?


Using your code in node without ioBroker

Mathias,
Some years ago I started to use Node with the code from https://github.com/rannmann/node-husqvarna-automower but now that Husqvarna have published an official API I would like to set up something similar but using WebSocket to gather changes instead of reading the mower status every 3 minutes.  You have produced almost what I want but I don't want to install ioBroker. I just want to run a job on my Mac to gather the data and save it so it can be interpreted by a web page an example of which I attach. Do you have the code without reference to ioBroker which I may use please?
Kind regards,
Graham Lawrence
<EMAIL_ADDRESS>

Hi Graham,
Thank you for your interest in this adapter. I took the initial code directly from husqvarna. Take a look at https://developer.husqvarnagroup.cloud/apis/Automower+Connect+API#/websocket, perhaps you can take some Ideas from there.

Thank you for your help.


Experimentally querying Perm in /v2/routes/:guid/apps causes severe performance degradation (as non-admin)

Submitting this issue to cloud_controller_ng after discussing this beforehand on Slack with replies to confirm my hypothesis about what could be the performance issue/regression here with the help of @monamohebbi @tcdowney @selzoc (and @ericpromislow @Gerg CC'ed in Slack thread).
Issue
We are reporting this issue as part of an upgrade of CF v249 -> CF v5.1.0 and we're aware this is not a validated upgrade path. This concerns a rather large foundation (~85k apps, but only a few 100's running at the same time). As we wrote before, we see a severe performance degradation between the old and the new version with a 100% CPU ruby processes on the API nodes from time to time (which we inspected with rbspy as suggested earlier). However, we now managed to pinpoint the specific call (we do that call ourselves, we know where and why), and it is this call:
GET /v2/routes?inline-relations-depth=1&q=host:XXX
(Please note that we did read the historical background about inline-relations-depth and its deprecation, changing it from ird=1 to ird=0 and then query the app details we needed ourselves afterwards will still show the routes query to keep on performing poorly if the slow code-path is picked, depending on perm)
The interesting part here is that we noted the following: depending on some variable (I currently suspect user role?) this call can choose 2 completely different code-paths, the one we see most often performs perfectly fine (sub-second) but the other one (more limited user role, suspected?) performs horrible at this scale; it literally takes 10-20 seconds to return on a huge RDS instance (AWS db.m4.10xlarge I believe) and during that time, the API (cc) seems pretty much blocked/busy with this request and unable to serve others at a fast rate, basically degrading the whole cluster performance by a lot.
Context
It seems that the slow code-path is doing additional checking including, but not limited to this:
SELECT count(*) AS \"count\" FROM \"routes\" WHERE ((\"routes\".\"guid\" IN (HUGE-LIST-OF-UUIDs-HERE) [..]
SELECT * FROM \"routes\" WHERE ((\"routes\".\"guid\" IN (HUGE-LIST-OF-UUIDs-HERE) [..]

This (to me, with limited knowledge) clearly looks like an additional security check to make sure you are not able to get routes you're not supposed to see (which is why we suspect user roles play a role in this), can you confirm or deny this (the existence of two paths) and that one performs rather poorly at scale (while having ~85k apps in ~4 spaces, we know this scales badly and will fix that after this performance issue is resolved). Going through the git history for the RoutesController (/app/controllers/runtime/routes_controller.rb) seems rather interesting, mostly commit a09f3fb12ceb540b30c9216fbe964241135a463f that refers to Pivotal Tracker issue #157581579 that seems to describe this, if we understand it correctly? And later also a4d4364f09c98ab9b1a38e30ac6ffda40ba72e56 that refers to Pivotal Tracker issue #157581627 for a different endpoint (/v2/routes/:guid/route_mappings).
Rough numbers of apps: ~85k
Rough number of routes: ~85k
Rough number of orgs: ~5
Rough number of spaces: ~10 (2 per org)
Rough number of apps/routes per space: ~10-20k over ~5 spaces (poor man's sharding)
Steps to Reproduce
As non-admin user, execute request on a rather large foundation, as described:
GET /v2/routes?inline-relations-depth=1&q=host:XXX or GET /v2/routes?inline-relations-depth=0&q=host:XXX
Expected result
A sub-second response for the request sent, as admin users would get.
Current result
ruby 100% CPU with top on (one of the) API node(s). During that time, the API (cc) seems pretty much blocked/busy with this request and unable to serve others at a fast rate, basically degrading the whole cluster performance by a lot. The takes 10-20 seconds to return as a non-admin user.
Possible Fix
Revert the (dead?) perm code commits mentioned above, or make sure they perform.
As per @monamohebbi: "there's a lot of historical context related to this question, perm (ie that commit you linked to), and inline-relations-depth generally. @tcdowney might know more. what I can tell you is that your suspicion about multiple perm code paths is almost certainly correct."
As per @selzoc: "it was definitely part of a perm effort to limit access, as you figured out.  unfortunately, that effort failed, but there is some code still resident in capi that changed shape to support it. we are in the process of trying to move everything to the v3 api, which is easier for us to make performant. and there's future work to add /v3/routes"
As per @tcdowney: "Since the perm work is stalled out, this might just be a change we need to revert -- you're the first I'm aware of to report perf issues from it though so the rough numbers of apps, routes, and apps/routes per space will help us repro/confirm the root cause"
Possible Workaround
I think a user with the cloud_controller.admin or cloud_controller.admin_readonly would be able to bypass this since they can view everything, but yes definitely seems like a performance regression here. (as per @tcdowney)
Reverting back to an older capi-release (like before v1.59.0) is not a real option either for most.
/v3/routes does not exist in any version of capi-release yet, so that is no workaround. (as per @Gerg)
End note
Please let me know if there is anything else I could/should provide to help resolve this issue!

Brief update: when grepping for queryer.can_read_globally (the check that seems to determine to use the perm code path or not), it seems this is present in the following (api v2) controllers?
app/controllers/runtime/organizations_controller.rb commit 601ed012ce388d23effb68cb0701a99fec366539
app/controllers/runtime/routes_controller.rb (commits already mentioned above)
And it seems to also match for the following api v3 controllers (which we don't use atm):
app/controllers/v3/tasks_controller.rb
app/controllers/v3/droplets_controller.rb
app/controllers/v3/isolation_segments_controller.rb
app/controllers/v3/packages_controller.rb
app/controllers/v3/route_mappings_controller.rb
app/controllers/v3/organizations_controller.rb
app/controllers/v3/service_instances_controller.rb
app/controllers/v3/service_bindings_controller.rb
app/controllers/v3/processes_controller.rb
app/controllers/v3/apps_controller.rb
app/controllers/v3/spaces_controller.rb
app/controllers/v3/builds_controller.rb
app/controllers/v3/deployments_controller.rb

@djvdorp thanks for the investigation you've done so far in to this performance issue. I'm especially grateful for the detailed information regarding the size and shape of your data since that will help us reproduce the issue and validate our code changes.
For context, this code came about due to our efforts last Spring to integrate with the "perm" permissions service that would allow for user authorization via role-based access control instead of Cloud Controller's existing ideas of permissions. This service required us to send a list of resource identifiers (in this case app guids) to it so that it could make access control decisions for those resources. This work required changes to the existing Cloud Controller-based access control and, as you've discovered, these new queries are not performant for users that have access to a large number of apps.
Work on the RBAC perm service is on indefinite hiatus and will likely never be implemented in the v2 APIs since efforts are underway to reach feature parity in v3 and deprecate them (see: https://lists.cloudfoundry.org/g/cf-dev/topic/26659245#8305). Given that, I think we should remove perm integration from the v2 organizations_controller.rb and routes_controller.rb and have them revert back to using the queries that they used before.
Tagging our PMs @zrob and @ssisil so they're aware of this issue.

@djvdorp were you seeing issues with the OrganizationsController endpoints as well (/v2/organizations)?

@tcdowney no, we did not, sorry if that was unclear. Our use-case does not have a lot of orgs (and spaces) so we were not seeing issues there -- just wanted to share that similar commits are there :slightly_smiling_face:

Cool, I broke that work out in to a separate story then. Commit e676a6e60adb4831081fb8e2c04b545d56e8b6da should address this, just need to deliver it to our PMs and it will work its way in to the next capi-release.


ECONNRESET

{ error: 'read ECONNRESET' }

Hello, can you provide further information on how you are getting this error so I can reproduce it? Post the code that you are using, and check that you are also using the latest version of animu-desu.

i apologise for the disturbance i caused, its just that my retarded & oversmart govt. banned the anime sites to look cool and mature. i was able to access the contents using vpn/hosts. thank you for your dedication and hard work to make such useful things.

No problem man, if you face anything else feel free to post it :).


Issue with /docs/user-guide/persistent-volumes/walkthrough/

Issue with /docs/user-guide/persistent-volumes/walkthrough/
Hello,
The files path have moved. For example
docs/user-guide/persistent-volumes/claims/claim-01.yaml
became
test/fixtures/doc-yaml/user-guide/persistent-volumes/claims/claim-01.yaml
Regards.

Fixed


Zonal script is blocked

Zonal is blocked as a script from an unauthenticated source. This is seen in the current demo version of PRISM Cambodia:
https://prism-khm-internal-demo.surge.sh/
I'm on Chrome Version 105.0.5195.125 (Official Build) (x86_64), Mac OSX

PR is up and ready for review here: https://github.com/WFP-VAM/prism-app/pull/581


Add SailfishOS

https://github.com/sailfishos-community/awesome-sailfishos
A curated list of awesome Sailfish OS resources.
Sailfish OS is a mobile operating system based on open source and developed by the Finnish mobile company Jolla Ltd. and the Sailfish OS community.
By submitting this pull request I confirm I've read and complied with the below requirements.
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

I have read and understood the contribution guidelines and the instructions for creating a list.
This pull request has a descriptive title.For example, Add Name of List, not Update readme.md or Add awesome list.
The entry in the Awesome list should:

Include a short description about the project/theme of the list. It should not describe the list itself.Example: - [Fish](…) - User-friendly shell., not - [Fish](…) - Resources for Fish..
Be added at the bottom of the appropriate category.

The list I'm submitting complies with these requirements:

Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
It's the result of hard work and the best I could possibly produce.
Non-generated Markdown file in a GitHub repo.
Includes a succinct description of the project/theme at the top of the readme. (Example)
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Not a duplicate.
Only has awesome items. Awesome lists are curations of the best, not everything.
Includes a project logo/illustration whenever possible.

Either fullwidth or placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to maximum half the width of the original image.

Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
Includes the Awesome badge.

Should be placed on the right side of the readme heading.
Should link back to this list.

Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.
Should only have one level of sub-lists, preferably none.

Has an appropriate license.

That means something like CC0, not a code licence like MIT, BSD, Apache, etc.
WTFPL and Unlicense are not acceptable licenses.
If you use a license badge, it should be SVG, not PNG.

Has contribution guidelines.

The file should be named contributing.md. Casing is up to you.

Has consistent formatting and proper spelling/grammar.

The link and description are separated by a dash. Example: - [AVA](…) - JavaScript test runner.
The description starts with an uppercase character and ends with a period.
Drop all the A / An prefixes in the descriptions.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

Doesn't include a Travis badge.You can still use Travis for list linting, but the badge has no value in the readme.

Go to the top and read it again.

Hey, sorry for the lack of response, please see #1363.

❯ awesome-lint https://github.com/sailfishos-community/awesome-sailfishos
✖ Linting

  README.md:36:49
  ✖   19:1   ToC item "Tips and Tricks" does not match corresponding heading "Deploy"  remark-lint:awesome/toc
  ✖   36:49  List item description must end with proper punctuation                    remark-lint:awesome/list-item
  ✖   37:61  List item description must end with proper punctuation                    remark-lint:awesome/list-item
  ✖   39:62  List item description must end with proper punctuation                    remark-lint:awesome/list-item
  ✖   41:63  List item description must end with proper punctuation                    remark-lint:awesome/list-item
  ✖   43:68  List item link and description separated by invalid whitespace            remark-lint:awesome/list-item
  ✖   45:82  List item link and description separated by invalid whitespace            remark-lint:awesome/list-item
  ✖   50:60  List item description must end with proper punctuation                    remark-lint:awesome/list-item
  ✖   52:53  List item description must end with proper punctuation                    remark-lint:awesome/list-item
  ✖   54:48  List item description must end with proper punctuation                    remark-lint:awesome/list-item
  ✖   56:51  List item description must end with proper punctuation                    remark-lint:awesome/list-item
  ✖   59:50  List item description must end with proper punctuation                    remark-lint:awesome/list-item
  ✖   63:80  List item link and description separated by invalid whitespace            remark-lint:awesome/list-item
  ✖   65:77  List item description must end with proper punctuation                    remark-lint:awesome/list-item
  ✖   66:81  List item description must end with proper punctuation                    remark-lint:awesome/list-item
  ✖  114:54  List item description must end with proper punctuation                    remark-lint:awesome/list-item
  ✖  115:49  List item description must end with proper punctuation                    remark-lint:awesome/list-item
  ✖  116:58  List item description must end with proper punctuation                    remark-lint:awesome/list-item
  ✖  120:46  List item description must end with proper punctuation                    remark-lint:awesome/list-item
  ✖  121:83  List item description must end with proper punctuation                    remark-lint:awesome/list-item
  ✖  138:79  List item link and description separated by invalid whitespace            remark-lint:awesome/list-item

  21 errors

https://github.com/sindresorhus/awesome-lint

Can you fix the merge conflict?

Closing for lack of response.


WIP: Bump to Spring Boot 2.1

This tests will most likely fail for the time being because the OT dependencies have not propagated to Maven Central yet.
They will be restarted once those deps are ready


Cleanup common port forwarding code

This moves the various copies of port forwarding code in the Device subclasses into the ProtocolDiscovery class.

move port forwarding to a common location
throw exception if protocol Uri is not discovered or port forwarding fails
cancel discovery protocol subscriptions on iOS launches (wasn't happening before)
fix iOS port forwarding to match other implementations
add tests

@johnmccutchan

LGTM after fixing travis failures


2 comments on changes in jsPDF v2.0.0

I just upgraded to jsPDF 2.0.0 and noticed two things:

lineHeight can't be specified anymore in the constructor of a new document:

const doc = new jsPDF({
  orientation: 'portrait',
  unit: 'mm',
  format: 'a4',
  lineHeight: 1.5,
});

Instead, one has to define lineHeight in a separate command: doc.setLineHeightFactor(1.5);. Is this doing the same in the background?

setFontStyle is missing. Instead, the font style can be defined in setFont. However, this requires to repeat the font definition itself. To me it is unclear why the font style has to be defined together with setFont, while the size and color (setFontSize, setTextColor) are separate methods. What are the reasons here?

There should probably be an upgrade guide that reflects these (and possibly other) changes and their reasons :-)

Yes, setLineHeightFactor has the same effect as setting it in the initial constructor. The advantage is that it can be changed throughout the document.

setFontStyle was removed because of the way custom fonts are added/used. A custom font is always associated with a specific font style, so setting only the style might be an invalid operation if the current font does not support this style.

I agree. The thing is, the changes were made over the last two years and by different people. Some of them are no longer part of this project. Also, due to huge refactorings, the diff between the last two versions is huge, which is why its very hard to find out what really changed. Unfortunately, I also don't have the time for such things. But if you or anyone else wants to dig into that and create a pull request, I would happily merge it.

Thank you for the explanation. It is a lot clearer now.
Regarding point 3:
I guess that really relevant are only the methods and interfaces that are exported to the users. Intrinsics are probably not relevant. How about we diff the index.d.ts / index.js of both versions and describe the changes?

In theory, comparing the typings files would be a good idea. The thing is, I'm not sure how accurate the typings file from 1.5.3 is. But you may give it a try, of course.


CoreCLR

Can TestHelpers be moved to a vNext project targetting dnx451 and dnxcore50 as well as any existing profiles (net45/net40/etc)
See the following Compose commits for some assistance or shout me on twitter/here:
https://github.com/smudge202/compose/commit/121c9c55149b97ed341101988a1f0e468163f27b
https://github.com/smudge202/compose/commit/d231fdc704dab183409ab140f7978128be585bcf
https://github.com/smudge202/compose/commit/a09fa07805ea86e5b3ae9db17c387809aa2b65c0

You intend to mark this as back in progress? (T'is closed)

It is closed. I've removed the in progress label not added?

My bad =/


Style: add copy to clipboard #28

Hey @AbdulkarimOgaji, thank you so much for the contribution!  For this project, feature PRs are made to the test branch, so we can make sure everything is working properly before pushing to production
Please refer to this part of our Contributing guidelines for more detailed instructions on how to make a PR successfully.
We will close this PR for now, but feel free to make a new one to our test branch and ask us any questions if you have any. 😊


Langtorch

Could you add langtorch to the list? It's the java equivalent of langchain.
Building composable LLM application with Java.
https://github.com/Knowly-ai/langtorch

Thank you @li2109 for pointing LangTorch. Added to the list.


Windows Installer

Can you provide a Windows installer also.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/24484918-windows-installer?utm_campaign=plugin&utm_content=tracker%2F505659&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F505659&utm_medium=issues&utm_source=github).

hi @sirinath
there's no installer yet, but for the time being you can run Crate from the tarball which you can download here: https://crate.io/install/