GNOME 42 compatibility + removal of fullscreen buttons

I believe I've fixed the main (/only one I found) compatibility issue with GNOME42  (#190) : the preferences/settings menu. The call set_titlebar()  is not supported by libadwaita; this is resolved by adding the headerBar as its own object as recommended in the libadwaita documentation.
In addition, I have removed the fullscreen buttons as this has been buggy for quite some time and doesn't seem to have an easy fix (https://github.com/zagortenay333/timepp/issues/179#issuecomment-979915164).

Thank you!

Somebody, please review and merge this PR!

@zagortenay333 would you be willing to allow more people to be able to help will pull requests review like maybe @landegt, if he is willing, and myself? I don't have any experience with extension management but I have over 10 years of programming experience and would be willing to help because I've been using this extension for a long time and recently upgraded to gnome 42 and realized how much it integrated into my workflow once it was no longer available. If not that's also fine I can follow this pull request to get it working for myself but not everyone would be comfortable with doing that and this extension provided the easiest way that I could find to add that functionality. My objective is not so much to take over your extension but rather to help ease the burden on you. I feel that this extension provides very important functionality to gnome that I haven't been able to find elsewhere.

@landegt does the edit button on alarms work for you? When I mouse over the alarm it shows like in the screenshot

but when I mouse over the actual button it disappears.

Is this change compatible with gnome versions 40 and 41? If not then they must be removed from the metadata file.

There is also this other pull requests which seems to fix the close buttons. Could you please check if it works?

There is also this other pull requests which seems to fix the close buttons. Could you please check if it works?

Yeah I can test both of those things and let you know.
So I'll test

These changes on 40 and 41 (For me however the edit button is not working on 42, I'll test in a VM to see if it's something specific to my machine)
And look for the pull request that fixes the close buttons and test it as well.

There is also this other pull requests which seems to fix the close buttons. Could you please check if it works?

Yeah I can test both of those things and let you know.
So I'll test
1. These changes on 40 and 41 (For me however the edit button is not working on 42, I'll test in a VM to see if it's something specific to my machine)

2. And look for the pull request that fixes the close buttons and test it as well.

@c-git thanks for checking compatibility. On the other pull request as far as I can see only the general settings become available with the other options for timer, Stopwatch, etc being hidden. If the window close button fix works, I could definitely add that into this pull request sometime tomorrow. I will also look into the edit button disappearing for the alarms, thanks for noticing this.

I haven't had a chance to try the other versions yet but I found out more info on the edit button (I also cannot remember if this problem existed before the upgrade to gnome 42, the work around seems familiar so I'm not sure). The edit button disappears if I move the mouse over from the any direction except down however if I come up on it from the bottom it works fine and is clickable. Not a big issue for me as this work around is fine, which is probably why I didn't remember that this may have been happening in my setup even before.

I made a short clip of the problem but couldn't figure out where to upload it so you could view in your browser so uploaded to discord. Happy to upload somewhere else that is more convenient Video

I have the same issue.
The current latest version of time++ does not let me to click the edit button. it disappears when the cursor of mouse touches it.
GNOME v: 42.3.1
GTK v: 3.24.34
GDM v: 42.0


Refactoring

I apply code refactoring for the improvement of readability and maintainability.

Thanks for the PR! We're working on refactoring a lot of our C++ code right now to follow better styling. There's a few things in here inconsistent with where we are going (such as making sure it's always two spaces of indentation, no tabs), and we're trying to avoid use of the whole std namespace and such, so we won't directly merge this one. I appreciate the effort :)


New cask metasploit 4.14.6

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} reports no offenses.
[x] The commit message includes the cask’s name and version.

Additionally, if adding a new cask:

[x] Named the cask according to the [token reference].
[x] brew cask install {{cask_file}} worked successfully.
[x] brew cask uninstall {{cask_file}} worked successfully.
[ ] Checked there are no [open pull requests] for the same cask.
[x] Checked the cask was not already refused in [closed issues].
[x] Checked the cask is submitted to [the correct repo].

New version of #31182

Thank you.

Thank you for the work you put into HBC.    👍


Unsaved changes, and publish new entry fails (netlify deployment).

Describe the bug
1 - Infinite unsaved changes, but the entries appear on the workflow section, however when I try to publish it to production, deployment fails.
To Reproduce
**1 - Create a new post and filling it up.
2 - Try to save it (Unsaved changes bug, see image)
3 - Publish (Deployment starts but fails, see image)**
Expected behavior

Screenshots
I do not what is causing this problem as well.

When I try to save

After trying save the post...

When I publish a new entry and then deployment fails

Applicable Versions:

Netlify CMS version: 2.11.23
Git provider: Github
OS: Manjaro Arch Linux 64bytes
Browser version Firefox Developver - Last version

Node.JS version: 12.18.3

CMS configuration

backend: # Set up your backend
  name: github
  repo: ulises-castro/****
  preview_context: netlify/deployment

local_backend: false # Optional if you want to use the local proxy mode

publish_mode: editorial_workflow
media_folder: static/assets   # I'm not using these default  assets directories at the moment.
public_folder: /assets

display_url: https://*****.netlify.com/

collections:
  - name: "posts"
    label: "Posts"
    folder: "content/posts"
    create: true
    delete: true
    path: "{{slug}}/index"
    slug: "{{year}}-{{month}}-{{day}}-{{slug}}"
    media_folder: "images"
    public_folder: "./images"
    fields:
      - { label: "Title", name: "title", widget: "string" }
      - { label: "Author", name: "author", widget: "relation", collection: "authors", valueField: "name", searchFields: ["name"] }
      - { label: "Publish Date", name: "date", widget: "datetime", format: "YYYY-MM-DD", dateFormat: "YYYY-MM-DD", timeFormat: false }
      - { label: "Excerpt", name: "excerpt", widget: "string", required: false }
      - { label: "Hero", name: "hero", widget: "image" }
      - { label: "Body", name: "body", widget: "markdown" }
  - name: "authors"
    label: "Authors"
    folder: "content/authors/authors"
    create: true
    delete: true
    format: "yml"
    identifier_field: "name"
    media_folder: "avatars"
    public_folder: "./avatars"
    editor:
      preview: false
    fields:
      - { label: Name, name: name, widget: string }
      - { label: Bio, name: bio, widget: string }
      - { label: Featured, name: featured, widget: boolean, default: false }
      - { label: Avatar, name: avatar, widget: image }
      - { label: Social, name: social, widget: list, collapsed: false, field: { label: URL, name: url, widget: string } }

Additional context
I'm using novela theme.

Hi @ulises-castro, can you share the latest CMS versions as shown in the browser logs when you open the CMS.
Latest versions are:

<EMAIL_ADDRESS><EMAIL_ADDRESS>
I recommend updating to the latest versions.
As for the build failure, that seems like a Gatsby issue so I recommend posting on their repo.

@erezrokah , I upgraded those packages, however I receiving the message "Failed to persist entry: TypeError: r.has is not a function", when I try to save it.
And this appears on console

I desactivated the editor_workflow at Gatsby-config.js so it works now.


Add CaFile for KafkaRecorder when simpleSSL enabled

Description
Currently, there is no way to add CaFile, when SASL_SSL enabled. This pull request add CaFile for KafkaRecorder when simpleSSL enabled
Motivation and Context
How Has This Been Tested?
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[X] I have added tests to cover my changes.
[X] All new and existing tests passed.

@paragor awesome! Thanks

@zhouzhuojie interesting PR!

Codecov Report

Merging #534 (11e22d3) into main (347a36d) will not change coverage.
The diff coverage is 100.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@           Coverage Diff           @@
##             main     #534   +/-   ##
=======================================
  Coverage   80.96%   80.96%
=======================================
  Files          28       28
  Lines        2222     2222
=======================================
  Hits         1799     1799
  Misses        334      334
  Partials       89       89

Impacted Files
Coverage Δ

pkg/handler/data_recorder_kafka.go
73.87% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


I want to use custom camera

Hello ;-)
Thank you very much for your fantastic plugin.
I'm simply wondering whether I may utilize the custom camera that I made.

Take a look at the following screenshot:

Give me this screen after that:

Thanks for considering my request.

That would probably not be too difficult for Android. The problem is that iOS uses the native document scanner, so I can't customize that. It would only be possible if I use Vision instead.

I appreciate your reply. How can I include it in Android?
Or will you include that in the future?

I'll consider it if time allows. Right now you can't do this with Android.

OK, Thank You

Is the answer same for using the cropping/image editing screen for without camera usage?
e.g. using share functionality to import an image from third party apps and passing image path to the cropper.

Yeah it's basically the same. In order to make that work I would need to skip the camera capture on Android, and send the cropper an image. On iOS it's possible, but tricky because right now this plugin uses VisionKit.

Yes this will be a great addition to this lib

+1 this would be a great addition or if you can expose the cropping functionality on Adnroid would be great!

+1
Team, I'm also looking for something similar, just to show the rectangular mask on camera without any functionality.


Add support for ethabi Tuple types

Part of the Solidity structs epic: graph-node issue #766
This PR brings in the updates to ethabi, adds support for the new Token variant (ethabi::Token::Tuple), and provides conversions to and from asc types.

Let's hold off with merging this until the following PRs have been merged:

https://github.com/graphprotocol/ethabi/pull/3
https://github.com/graphprotocol/graph-cli/pull/243
https://github.com/graphprotocol/graph-ts/pull/49


Custom tags input

Implements a custom tags input and integrates it into the new tag architecture for testing purposes. Partially addresses #605

Testing:

Open a plan
Open up activity directive form
Add existing tags from the tags field by typing into the tags input and selecting existing tags using arrow keys or via click.
Add new tags by entering a tag that does not yet exist and hitting enter or clicking on "add <tag_name> (enter)"
Disassociate tags from the activity directive by deleting them from the tags input. This can be accomplished by focusing on the input and pressing backspace/delete (windows/mac) or by clicking on the tags in the input.
Click on a different activity directive and ensure that the tags you have added from the other directive are available for selection.

Questions:

Pastel colors are automatically generated for new tags. Is this behavior acceptable if we don't ship tag color editing at the same time? Alternatively we use a single color for now and/or users can edit tag colors via API.
Should the Tags component be more generic? It could potentially serve as a general autosuggest with single/multiple inputs and could be decoupled from Aerie's tag type? Will require more work and investigation if desired.

Not ready to merge, need aerie to first provide tags when getting merge activities.

Can we remove the old tags lib from package/package-lock?


Update devDependencies to not reference pre versions of internal packages

Found while going through package.json files.
Doing an empty changeset as dev dependency updates don't affect end users.

If we wanted to be very conservative we could do a small patch changeset entry. In the case that a dev dependency has some impact on the published package.


A way for schema plugins to extend Query class

The problem is that sometimes it's needed to have own methods to the conditions chain.
I.e. I have a plugin that adds access permissions to the schema (call it acl). It adds an instance method findByOwner to the schema.
Also I have a plugin that adds flags to the same schema (call it flags). It adds an instance method findByFlag to the schema.
Now I want to query documents of this schema filtered by the owner as well as by some flag. Each of these filters could be applied separately:
MyModel.findByOwner(owner, callback);

and
MyModel.findByFlag(flag, callback);

But it's impossible to chain them like:
MyModel.findByOwner(owner).findByFlag(flag).exec(callback);

Someone advised to extend mongoose.Query's prototype. But IMO it breaks the principle that plugin only affects the schema it was applied to.
Maybe it's possible to move Query class reference to the Schema and call it in the model methods like:
Model.where = function where (path, val) {
  var mq = new this.schema.Query({}, {}, this, this.collection).find({});
  return mq.where.apply(mq, arguments);
};

Plugins will be able to overwrite Query class reference with the child of mongoose.Query extended with the necessary methods.
Are there any pitfalls with this solution?

Worth investigating, but I'm not sure there isn't already a good solution though. What's wrong with extending Query? It would not necessarily affect any other schemas - just have a new MyModelQuery class whose prototype is an Object.create(Query) and then add functions to your heart's content. Query functions return this, so I can't quite think of any problems with that approach.

Nice solution, btw. Didn't think about it that way. But anyway I need to overwrite mongoose.Model's methods to return instances of my own mongoose.Query descent.
Thank you.

Yeah you're right, that's a little messy. I'll mark this ticket for a future release - not sure where on the roadmap this'll fall, but I see your point.

+1

Released in 4.5, see #3740, etc.


Fix issues to improve code quality

Summary of Changes

Fix logger.exception to directly log the exception traceback
Fix the warning as passing an exception context is not recomended
Use string formatting syntax {} while using the format method
Add DeepSource to catch these issues in future

Tests
No tests requires updation in this change-set.
Documentation
No documentation requires updation in this change-set.
CheckList
Make sure you have checked all steps below to ensure a timely review.

[x] PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"

In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

[x] PR includes a summary of changes.
[x] PR adds unit tests, updates existing unit tests, OR documents why no test additions or modifications are needed.
[x] In case of new functionality, my PR adds documentation that describes how to use it.

All the public functions and the classes in the PR contain docstrings that explain what it does

[x] PR passes make test
[x] I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message"

Notes
Hi @jinhyukchang,
I forked and ran analysis on this repository and found some interesting issues in the code. You can take a look at the results here.
To continue running analysis on every PR, just follow these simple steps:

Merge this PR. I've added a customised .deepsource.toml for this repo which you can use directly.
Sign up on DeepSource and grant access to this repository here.
Activate analysis here.

You can take a look at the Getting Started docs for the steps.

Codecov Report

Merging #54 into master will not change coverage.
The diff coverage is 0%.

@@           Coverage Diff           @@
##           master      #54   +/-   ##
=======================================
  Coverage   82.57%   82.57%
=======================================
  Files          49       49
  Lines        2209     2209
  Branches      203      203
=======================================
  Hits         1824     1824
  Misses        312      312
  Partials       73       73

Impacted Files
Coverage Δ

databuilder/models/neo4j_csv_serde.py
80.85% <ø> (ø)
:arrow_up:

databuilder/extractor/db_api_extractor.py
0% <0%> (ø)
:arrow_up:

databuilder/models/user.py
82.81% <0%> (ø)
:arrow_up:

databuilder/extractor/neo4j_extractor.py
81.13% <0%> (ø)
: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 bbefcd8...3e78a5d. Read the comment docs.

Hi @jinhyukchang, poke.


Update example config to use ENVVARS for database creds

cmdline arguments are viewable in systemwide process table.
database creds should be held in envvars and references as envvars on the commandline to avoid leaking into the process table.

Something like this should work at the linux/osX cmdline
\$ is used to prevent bash from trying to replace the variables will creating the command.
sensuctl handler create influx-db \
--type pipe \
--env-vars "INFLUX_USER='user', INFLUX_PASS='pass'"
--command "sensu-influxdb-handler \
--addr 'http://<IP_ADDRESS>:8086' \
--db-name 'myDB' \
--username \${INFLUX_USER} \
--password \${INFLUX_PASS}"

Actual no.. this is all wrong.
What we need is for influxdb handler to optionally parse ENVVARS  instead of arguments.
If it inputted as an argument on the cmdline even via envvar substitution it leaks into the process table.
I'll try to do a PR for this teaching the handler to check for special envvar values.


spotify media player

Description:
Spotify recently opened up their "Connect" playback web api: https://developer.spotify.com/web-api/web-api-connect-endpoint-reference/
Now we can have a Spotify media player with standard playback controls, track metadata, etc. Also can switch devices (implemented via source_select).
Pending https://github.com/plamere/spotipy/pull/182 on the spotipy library; temporarily depending on my fork.
Requirements:

Spotify Premium account
Spotify developer "Application" created: https://developer.spotify.com/my-applications/#!/applications
Client ID and secret from Application
Set Application redirect URI to http://<your_url>/api/spotify

I hope someone else can test this before it is merged.
Pull request in home-assistant.github.io with documentation (if applicable): https://github.com/home-assistant/home-assistant.github.io/pull/2406
Example entry for configuration.yaml (if applicable):
media_player:
  - platform: spotify
    client_id: !secret spotify_client_id
    client_secret: !secret spotify_client_secret

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

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

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

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] New dependencies have been added to the REQUIREMENTS variable ([example][ex-requir]).
[x] New dependencies are only imported inside functions that use them ([example][ex-import]).
[x] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[x] New files were added to .coveragerc.
[ex-requir]: https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/keyboard.py#L14
[ex-import]: https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/keyboard.py#L54

This is being tested by a few people. Don't merge yet, please.

A few users have tested this and confirmed it works. Ready to merge!

This worked for me, although the redirect caused a file download in my browser. I believe it's because Spotify expects to POST back to /api/spotify but you only accept GETs.
Other than that very small note, everything seems to work!

@robbiet480 POST results in 405: Method Not Allowed since oauth sends a GET, I guess. I haven't been able to find any documentation on what HTTP verb and/or headers are required to not cause a file download in this case.

Sorry for taking so long to review. I've been busy.
I removed the calls to schedule_update_ha_state, your device does not overwrite should_poll and thus the default value True is active. When a device should be polled, Home Assistant will automatically call update after it calls a service.
This looks good 🐬

Hello, I tried using this media player, but I get the following error :
File "/usr/local/lib/python3.5/dist-packages/homeassistant/components/media_player/spotify.py", line 156, in update
self.refresh_spotify_instance()
File "/usr/local/lib/python3.5/dist-packages/homeassistant/components/media_player/spotify.py", line 143, in refresh_spotify_instance
self._oauth.is_token_expired(self._token_info))
AttributeError: 'SpotifyOAuth' object has no attribute 'is_token_expired'

@pbros Make sure you've installed the correct version of spotipy. For future questions, please open an issue, post on the community forum, or visit us on gitter.


Color Loss

Noticing that many of my images are experiencing color loss, even without lowering the quality or doing any resizing.  Any idea what's causing it?  Additionally, the proxied is about 200KB larger in this first instance:
Original:

Proxied:

If you're not changing the quality or resizing, what options are you passing to the proxy?

@sosso The original image has an embedded ICC color management profile, while the proxy output image does not. This absence explains the visual difference.


CONFIG_SCHEMA is missing payload defaults in digital_outputs node

[x] I have read the README.md file and visited the Github Wiki to see if the information there helps.

Describe the bug
Runtime error occurs in logging message if payload_on and payload_off are not configured for digital outputs
Expected behavior
"ON" and "OFF" should be used as default payload for digital outputs when nothing is configured.
Error messages and traceback
(ERROR): Exception while handling received MQTT message:
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/pi_mqtt_gpio/server.py", line 528, in on_msg
    handle_set(topic_prefix, msg)
  File "/usr/local/lib/python2.7/dist-packages/pi_mqtt_gpio/server.py", line 221, in handle_set
    if payload not in (output_config["on_payload"], output_config["off_payload"]):
KeyError: 'on_payload'

Config
  host: mqtt
  port: 1883
  client_id: pi-mqttXXX
  user: ""
  password: ""
  topic_prefix: /oh3/

gpio_modules:
  - name: piface
    module: piface2

digital_inputs:
  - name: carport_contact
    module: piface
    pin: 7

digital_outputs:
  - name: carport_close_trigger
    module: piface
    pin: 7

Hardware

Platform: Raspberry Pi
Connected hardware:  piface2

System:

OS: Raspbian
Python version: Python 2.7.9
User you're running as: root
Using a virtualenv?: no

Additional context
I think there are simply two lines missing in init.py:
default "ON" between 264/265
default "OFF" between 268/269

Oh! That looks like a regression. I guess it was caused by a merge somewhere and we didn't spot it.
Thanks!

Oh! That looks like a regression. I guess it was caused by a merge somewhere and we didn't spot it.
Thanks!


Don't remove metadata when other instance of service (with same name) remains

LGTM code wise. How can we test/verify if this works/doesn't break?

@simonvanderveldt I've created a second automated build for this branch, so you can run amochtar/registrator:multi-instance and verify

Ran both the current master and this branch locally.
When killing 1 of 2 services the following happens:

master: the KV tree for the service is removed
this branch: The KV tree for the service stays

When killing both services the KV tree for this service is removed


some question about the dataset

what is the dataset of pretrained model Mobilefacenet?Hoping to  get your answers.

What are the datasets of all the pretrained models?


Missing integrated CI calls

The readme explains it covers 100% of the gitlab v3 api. However I cannot find some of the integrated CI-calls. For example get the status of a commit or posting the status of a commit. Is this by design or did it not yet get implemented after the gitlab was merged with CI?

It's not yet implemented as it is relativelly new feature in Gitlab.
I will submit PR if I have some free time. I already started working a bit on it.


Anybody tested this on Xiaomi Redmi Note 10S?

I am considering purchasing a Xiaomi phone, but I've heard they put a lot of crap in the factory OS.
I am running Linux on all of my hardware so I don't have access to Windows, that's why I was looking for something like this script.
Did anyone test it on Xiaomi Redmi Note 10S?

Well, it will work on any Android phone but the apps listed in the script predominantly found on Xiaomi phones. You can modify the script according to your need (which apps to keep/uninstall/disable).
By any means, if you ran into trouble you can factory reset your phone to undo all changes but make sure to back-up data.

Thank you. I need to look up how to backup all that so in case of a failure I can quickly get up and running again without losing everything.


dbt_utils: Could not find a satisfactory version from options: ['=0.7.0', '>=0.6.0', '<0.7.0', '>=0.6.0', '<0.7.0', '>=0.4.0', '<0.7.0']

Describe the bug
I have dbt version 0.20.0
I am trying to run 'dbt deps' in install dbt utils
I see this error message:
fishtown-analytics/dbt_utils: Could not find a satisfactory version from options: ['=0.7.0', '>=0.6.0', '<0.7.0', '>=0.6.0', '<0.7.0', '>=0.4.0', '<0.7.0']

Hi @asmurthy, could you provide the full contents of your packages.yml? It sounds like you have some dependency conflicts.
The latest version of this package (v0.4.0) is compatible with dbt v0.20 and dbt-utils v0.7.

@jtcohen6 the latest version on the hub is 0.3.0

@erika-e Ah, sorry for the confusion. Going forward, we'll be serving the latest versions of our packages in the dbt-labs namespace: https://hub.getdbt.com/dbt-labs/audit_helper/latest/. The fishtown-analytics versions are there for backwards compatibility.
More details in discourse: https://discourse.getdbt.com/t/packages-dbt-labs-in-the-dbt-hub/2711/4

🤦♀  I just popped the hub in google and didn't even think of that. Thanks for clarifying and for the speedy response!

@jtcohen6 - I think it was related to the version of dbt. It looks OK now. Thanks


ELD dataset description

Hi,
I download your pretrained model and ELD dataset to know more details of your paper.
But I failed with run test_ELD.sh
I found in the ELD dataset, every scene in a specific camera there is 16 raw data and some have 16 corresponding RGB data.
Is this should be 3 (isos) * 2(lowlight ratio) = 6 examples?
And I find  img_ids_set = [[4, 9, 14], [5, 10, 15]]   in the the_ELD.py  adn gt_ids = np.array([1, 6, 11, 16]) in sid_dataset.py.
I do not know exactly what this ids means.

Thank you for the feedback.
Did you address the problem?

Diving into your code and paper more deeply, I find the understanding about the eld dataset.
In some words, every scene has 16 raw data, and [4 9 14]-th case is the scaled 100 lowlight data. and [5, 10, 15]-th is the scaled 200 lowlight data.
the corredponding gt has 4 case, I do not exactly get the idea of the gt case process.
gt_ids = np.array([1, 6, 11, 16])
 ind = np.argmin(np.abs(self.img_ids[img_id] - gt_ids))

With the noise existance, I do not know use l1 to find gt is a proper way.

Yes, thanks for the description.
For each scene, I capture the long-exposure reference images four times to avoid accidential error (e.g. scene/camera motion)
This can be examined by calculating the PSNR using image id 1 and 16 (the resulting value should be high enough to ensure no error occurs.
For evaluation, I choose the nearest reference image id w.r.t. the input image id as ground truth, but you are free to use fixed id (e.g. image id 1) as ground truth as well

In other words, if one gt has very low psnr, this may have some motion.
By the way, I notice your description in your paper, I think you rexclude the accidential data in the ELD dataset.
I got it , thanks so much.

Another question about noisy samples generation.
I notice the function generate_noisy_obs in sid_dataset.py which is never be used.
Is this the noise model parameters?
def generate_noisy_obs(y):
    def sample_params():
        # log_a = np.random.uniform(low=np.log(1e-4), high=np.log(1.2e-3))
        log_a = np.random.uniform(low=np.log(1e-4), high=np.log(0.012))
        log_b = np.random.standard_normal() * 0.26 + 2.18 * log_a
        log_c = np.random.uniform(low=np.log(1e-9), high=np.log(1e-7))
        log_d = np.random.uniform(low=np.log(1e-8), high=np.log(1e-6))
        a = np.exp(log_a)
        b = np.exp(log_b)
        c = np.exp(log_c)
        d = np.exp(log_d)
        return a, b, c, d

    # sig_read = 10. ** np.random.uniform(low=-3., high=-1.5)
    # sig_shot = 10. ** np.random.uniform(low=-2., high=-1.)

    ratio = np.random.uniform(low=100, high=300)
    # ratio = 1

    a, b, c, d = sample_params()
    chi = 1 / a
    q = 1 / (2**14)

    y = y / ratio

    # Burst denoising
    # shot = np.random.randn(*y.shape).astype(np.float32) * np.sqrt(np.maximum(y, 1e-10)) * sig_shot
    # read = np.random.randn(*y.shape).astype(np.float32) * sig_read
    # z = y + shot + read

    if a > 1.2e-3:
        z = np.random.poisson(chi*y).astype(np.float32) / chi
    else:
        z = y + np.random.randn(*y.shape).astype(np.float32) * np.sqrt(np.maximum(y*a, 1e-10))

    z = z + np.random.randn(*y.shape).astype(np.float32) * np.sqrt(np.maximum(b, 1e-10)) # Gaussian noise
    z = z + np.random.randn(1, y.shape[1], 1).astype(np.float32) * np.sqrt(c) # banding noise
    z = z + np.random.uniform(low=-0.5*q, high=0.5*q) # quantisation error

    z = z * ratio

    return z

Ok, I just forgot to delete it (as I should have not released it)
It's a preliminary version of the noise model developed during the research stage.
It's not our final model, but may give you some hints to reproduce it.


whitelist CDN fraud prevention site *.forter.com and Zelle banking

I made a post on the pi-hole discourse,  but no-one has relied. Within a site like swimoutlet.com, they use a fraud protection service called forter.com. We also found when Google shopping a page was being blocked with the subdomain clickserve.dartsearch.net. I also posted how Zelle within Citbank.com is blocked, which I'm pretty sure is *.online-metrix.net.
On a side note I've tried to white list all of the Google Play Store. I've whitelisted all of the [1-20].client-channel.google.com subdomains and others mentioned here,  as well as ssl.google-analytics.com. Installation just hangs, tried on multiple Android phones.

@RobbieTheK forter.com and its subdomains are not blocked in default blocklists. Can you paste the output of pihole -q forter.com?

pihole -q forter.com

haps it's another domain then?
ihole -q forter.com
 Match found in Whitelist
   93e140b8b0e84b09ac891c94e68686d2-c74f8a20b3ca.cdn.forter.com
   c74f8a20b3ca.cdn4.forter.com
   cdn0.forter.com
   cdn3.forter.com
   cdn4.forter.com
   cdn9.forter.com
   cdn.forter.com

Here's another, landing pages from emails never redirect properly with this:
pihole -q trackcmp
 Match found in list.0.raw.githubusercontent.com.domains:
   trackcmp.net
 Match found in list.2.sysctl.org.domains:
   trackcmp.net

@RobbieTheK trackcmp.net seems to be a email tracker, so it will not be added

@RobbieTheK trackcmp.net seems to be a email tracker, so it will not be added

OK that I understand but what about *.forter.com?

@RobbieTheK I will look into it, even I had some of *.forter.com in my Pihole log (Vox media maybe?)


[AMBARI-24774] Wrong settings in exported blueprint

What changes were proposed in this pull request?

Fix the bug that only one component per service was included in component_settings.

Eliminate discrepancy between original cluster and the one re-created using exported blueprint by changing the blueprint export for settings:

Export recovery_setting only at the component-level.  Service- and cluster-level settings are still handled when creating cluster using blueprint.
Export setting if it does not match default value defined in stack metainfo as opposed to exporting if it's true (since stack may define it as true by default, in which case a false is significant).

https://issues.apache.org/jira/browse/AMBARI-24774
How was this patch tested?
Exported blueprints for various settings, and created clusters using exported blueprints.
Tweaked unit test.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/4304/
Test PASSed.


Media Key Not Working

Server: Windows 10, latest Barrier
Client: Arch Gnome 41, latest Waynergy
Input: raw-keymap
wl-clipboard installed
Dropping gid from 1001 to 1000
wl-clipboard 2.0.0
Copyright (C) 2019 Sergey Bugaev
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
wl-clipboard 2.0.0
Copyright (C) 2019 Sergey Bugaev
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Child died:
46276
Status:
1
0.000000110: [WARN] Could not kill lingering wlpaste instances: -1

Watch mode requires a compositor that supports wlroots data-control protocol
Watch mode requires a compositor that supports wlroots data-control protocol
Child died:
46278
Status:
1
Child died:
46277
Status:
1
0.004570085: [WARN] uinput does not support xkb keymaps -- use raw-keymap instead
0.004620686: [WARN] Idle inhibit request, but no idle manager support
1378.676578965: [ERROR] Keycode 264 is unsupported by uinput (max 256), dropping
1378.788337884: [ERROR] Keycode 264 is unsupported by uinput (max 256), dropping
1379.369884512: [ERROR] Keycode 264 is unsupported by uinput (max 256), dropping
1379.497723944: [ERROR] Keycode 264 is unsupported by uinput (max 256), dropping
1380.021551182: [ERROR] Keycode 264 is unsupported by uinput (max 256), dropping
1380.176657532: [ERROR] Keycode 264 is unsupported by uinput (max 256), dropping
1380.503267951: [ERROR] Keycode 264 is unsupported by uinput (max 256), dropping
1380.659793603: [ERROR] Keycode 264 is unsupported by uinput (max 256), dropping
1383.491429443: [ERROR] Keycode 264 is unsupported by uinput (max 256), dropping
1383.604201944: [ERROR] Keycode 264 is unsupported by uinput (max 256), dropping

From server:
[2022-03-03T09:47:10] DEBUG1: onKeyDown id=57519 mask=0x0000 button=0x0100
[2022-03-03T09:47:10] DEBUG1: hook: 0x000000af 0x81000001
[2022-03-03T09:47:10] DEBUG1: hook: 0x60af0000 0x81000001
[2022-03-03T09:47:10] DEBUG1: hook: 0x70af0000 0x81000001
[2022-03-03T09:47:10] DEBUG1: event: Key char=0, vk=0xaf, nagr=0, lParam=0x81000001
[2022-03-03T09:47:10] DEBUG1: new mask: 0x0000
[2022-03-03T09:47:10] DEBUG1: new mask: 0x0000
[2022-03-03T09:47:10] DEBUG1: onKeyUp id=57519 mask=0x0000 button=0x0100
[2022-03-03T09:47:11] DEBUG1: hook: 0x000000ae 0x01000001
[2022-03-03T09:47:11] DEBUG1: hook: 0x60ae0000 0x01000001
[2022-03-03T09:47:11] DEBUG1: hook: 0x70ae0000 0x01000001
[2022-03-03T09:47:11] DEBUG1: event: Key char=0, vk=0xae, nagr=0, lParam=0x01000001
[2022-03-03T09:47:11] DEBUG1: new mask: 0x0000
[2022-03-03T09:47:11] DEBUG1: new mask: 0x0000
[2022-03-03T09:47:11] DEBUG1: onKeyDown id=57518 mask=0x0000 button=0x0100
[2022-03-03T09:47:11] DEBUG1: hook: 0x000000ae 0x81000001
[2022-03-03T09:47:11] DEBUG1: hook: 0x60ae0000 0x81000001
[2022-03-03T09:47:11] DEBUG1: hook: 0x70ae0000 0x81000001
[2022-03-03T09:47:11] DEBUG1: event: Key char=0, vk=0xae, nagr=0, lParam=0x81000001
[2022-03-03T09:47:11] DEBUG1: new mask: 0x0000
[2022-03-03T09:47:11] DEBUG1: new mask: 0x0000
[2022-03-03T09:47:11] DEBUG1: onKeyUp id=57518 mask=0x0000 button=0x0100

As you can see from the log, server report same button ID for both VOLUP and VOLDOWN. The only difference is the id. On client side, it reports the keycodes as 264, despite the server send 255. This cause raw key mapping not possible. I'm uncertain whether this is Barrier issue or not as I can't find a similar ticket in their issue.

This is definitely a waynergy issue; the keycode is being checked before the required offset (-8 at the uinput level, because of historical weirdness) is applied. It shall be fixed shortly.

Hello, the media key still not working in latest version.
857.321167185: [DEBUG] Keycode: 264, state 1
857.321191016: [DEBUG] Modifiers: depressed: 0 latched: 0 locked: 10 group: 0
857.393269699: [DEBUG] Keycode: 264, state 0
857.393292059: [DEBUG] Modifiers: depressed: 0 latched: 0 locked: 10 group: 0
857.455371127: [DEBUG] Keycode: 264, state 1
857.455395214: [DEBUG] Modifiers: depressed: 0 latched: 0 locked: 10 group: 0
857.521351047: [DEBUG] Keycode: 264, state 0
857.521374648: [DEBUG] Modifiers: depressed: 0 latched: 0 locked: 10 group: 0
857.600860911: [DEBUG] Keycode: 264, state 1
857.600880676: [DEBUG] Modifiers: depressed: 0 latched: 0 locked: 10 group: 0
857.663553289: [DEBUG] Keycode: 264, state 0
857.663577689: [DEBUG] Modifiers: depressed: 0 latched: 0 locked: 10 group: 0
857.738065990: [DEBUG] Keycode: 264, state 1
857.738085564: [DEBUG] Modifiers: depressed: 0 latched: 0 locked: 10 group: 0
857.808641363: [DEBUG] Keycode: 264, state 0
857.808665160: [DEBUG] Modifiers: depressed: 0 latched: 0 locked: 10 group: 0

No error, but system didn't handle it. how can i map it with same keycode for every media key.
Btw, https://github.com/r-c-f/waynergy/blob/246c8632d357a2ce2e6501c81031beb754a2bb9e/src/wl_idle.c#L52.
this should not apply user custom offset, if user used offset 8, the keycode will map to KEY_PLAY, will cause the music pause and play in idle status.

I'll have to look further into the media key issue. Could you get a debug log of the barrier server when trying to use media keys?
As for the idle issue I'll probably add a setting for a specific raw keycode in perference to an xkb name, for situations where the xkb layout isn't actually being used. That should make it much easier for you to find a setting that doesn't conflict with a real keycode you care about.

Here is the log
[2022-07-06T09:41:10] DEBUG1: send key up to "chenxy-archlinux" id=57519, mask=0x2000, button=0x0100 [2022-07-06T09:41:10] DEBUG2: writef(DKUP%2i%2i%2i) [2022-07-06T09:41:10] DEBUG2: wrote 10 bytes [2022-07-06T09:41:10] DEBUG2: msg from "chenxy-archlinux": CNOP [2022-07-06T09:41:10] DEBUG2: no-op from [2022-07-06T09:41:11] DEBUG1: hook: 0x000000af 0x01000001 [2022-07-06T09:41:11] DEBUG1: hook: 0x60af0000 0x01000001 [2022-07-06T09:41:11] DEBUG1: hook: 0x70af0000 0x01000001 [2022-07-06T09:41:11] DEBUG1: event: Key char=0, vk=0xaf, nagr=0, lParam=0x01000001 [2022-07-06T09:41:11] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:11] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:11] DEBUG1: onKeyDown id=57519 mask=0x2000 button=0x0100 [2022-07-06T09:41:11] DEBUG1: send key down to "chenxy-archlinux" id=57519, mask=0x2000, button=0x0100 [2022-07-06T09:41:11] DEBUG2: writef(DKDN%2i%2i%2i) [2022-07-06T09:41:11] DEBUG2: wrote 10 bytes [2022-07-06T09:41:11] DEBUG2: msg from "chenxy-archlinux": CNOP [2022-07-06T09:41:11] DEBUG2: no-op from [2022-07-06T09:41:11] DEBUG1: hook: 0x000000af 0x81000001 [2022-07-06T09:41:11] DEBUG1: hook: 0x60af0000 0x81000001 [2022-07-06T09:41:11] DEBUG1: hook: 0x70af0000 0x81000001 [2022-07-06T09:41:11] DEBUG1: event: Key char=0, vk=0xaf, nagr=0, lParam=0x81000001 [2022-07-06T09:41:11] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:11] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:11] DEBUG1: onKeyUp id=57519 mask=0x2000 button=0x0100 [2022-07-06T09:41:11] DEBUG1: send key up to "chenxy-archlinux" id=57519, mask=0x2000, button=0x0100 [2022-07-06T09:41:11] DEBUG2: writef(DKUP%2i%2i%2i) [2022-07-06T09:41:11] DEBUG2: wrote 10 bytes [2022-07-06T09:41:11] DEBUG2: msg from "chenxy-archlinux": CNOP [2022-07-06T09:41:11] DEBUG2: no-op from [2022-07-06T09:41:11] DEBUG1: hook: 0x000000ae 0x01000001 [2022-07-06T09:41:11] DEBUG1: hook: 0x60ae0000 0x01000001 [2022-07-06T09:41:11] DEBUG1: hook: 0x70ae0000 0x01000001 [2022-07-06T09:41:11] DEBUG1: event: Key char=0, vk=0xae, nagr=0, lParam=0x01000001 [2022-07-06T09:41:11] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:11] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:11] DEBUG1: onKeyDown id=57518 mask=0x2000 button=0x0100 [2022-07-06T09:41:11] DEBUG1: send key down to "chenxy-archlinux" id=57518, mask=0x2000, button=0x0100 [2022-07-06T09:41:11] DEBUG2: writef(DKDN%2i%2i%2i) [2022-07-06T09:41:11] DEBUG2: wrote 10 bytes [2022-07-06T09:41:11] DEBUG2: msg from "chenxy-archlinux": CNOP [2022-07-06T09:41:11] DEBUG2: no-op from [2022-07-06T09:41:11] DEBUG1: hook: 0x000000ae 0x81000001 [2022-07-06T09:41:11] DEBUG1: hook: 0x60ae0000 0x81000001 [2022-07-06T09:41:11] DEBUG1: hook: 0x70ae0000 0x81000001 [2022-07-06T09:41:11] DEBUG1: event: Key char=0, vk=0xae, nagr=0, lParam=0x81000001 [2022-07-06T09:41:11] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:11] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:11] DEBUG1: onKeyUp id=57518 mask=0x2000 button=0x0100 [2022-07-06T09:41:11] DEBUG1: send key up to "chenxy-archlinux" id=57518, mask=0x2000, button=0x0100 [2022-07-06T09:41:11] DEBUG2: writef(DKUP%2i%2i%2i) [2022-07-06T09:41:11] DEBUG2: wrote 10 bytes [2022-07-06T09:41:11] DEBUG2: msg from "chenxy-archlinux": CNOP [2022-07-06T09:41:11] DEBUG2: no-op from [2022-07-06T09:41:11] DEBUG1: hook: 0x000000ae 0x01000001 [2022-07-06T09:41:11] DEBUG1: hook: 0x60ae0000 0x01000001 [2022-07-06T09:41:11] DEBUG1: hook: 0x70ae0000 0x01000001 [2022-07-06T09:41:11] DEBUG1: event: Key char=0, vk=0xae, nagr=0, lParam=0x01000001 [2022-07-06T09:41:11] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:11] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:11] DEBUG1: onKeyDown id=57518 mask=0x2000 button=0x0100 [2022-07-06T09:41:11] DEBUG1: send key down to "chenxy-archlinux" id=57518, mask=0x2000, button=0x0100 [2022-07-06T09:41:11] DEBUG2: writef(DKDN%2i%2i%2i) [2022-07-06T09:41:11] DEBUG2: wrote 10 bytes [2022-07-06T09:41:11] DEBUG2: msg from "chenxy-archlinux": CNOP [2022-07-06T09:41:11] DEBUG2: no-op from [2022-07-06T09:41:12] DEBUG1: hook: 0x000000ae 0x81000001 [2022-07-06T09:41:12] DEBUG1: hook: 0x60ae0000 0x81000001 [2022-07-06T09:41:12] DEBUG1: hook: 0x70ae0000 0x81000001 [2022-07-06T09:41:12] DEBUG1: event: Key char=0, vk=0xae, nagr=0, lParam=0x81000001 [2022-07-06T09:41:12] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:12] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:12] DEBUG1: onKeyUp id=57518 mask=0x2000 button=0x0100 [2022-07-06T09:41:12] DEBUG1: send key up to "chenxy-archlinux" id=57518, mask=0x2000, button=0x0100 [2022-07-06T09:41:12] DEBUG2: writef(DKUP%2i%2i%2i) [2022-07-06T09:41:12] DEBUG2: wrote 10 bytes [2022-07-06T09:41:12] DEBUG2: msg from "chenxy-archlinux": CNOP [2022-07-06T09:41:12] DEBUG2: no-op from [2022-07-06T09:41:12] DEBUG1: hook: 0x000000ae 0x01000001 [2022-07-06T09:41:12] DEBUG1: hook: 0x60ae0000 0x01000001 [2022-07-06T09:41:12] DEBUG1: hook: 0x70ae0000 0x01000001 [2022-07-06T09:41:12] DEBUG1: event: Key char=0, vk=0xae, nagr=0, lParam=0x01000001 [2022-07-06T09:41:12] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:12] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:12] DEBUG1: onKeyDown id=57518 mask=0x2000 button=0x0100 [2022-07-06T09:41:12] DEBUG1: send key down to "chenxy-archlinux" id=57518, mask=0x2000, button=0x0100 [2022-07-06T09:41:12] DEBUG2: writef(DKDN%2i%2i%2i) [2022-07-06T09:41:12] DEBUG2: wrote 10 bytes [2022-07-06T09:41:12] DEBUG2: msg from "chenxy-archlinux": CNOP [2022-07-06T09:41:12] DEBUG2: no-op from [2022-07-06T09:41:12] DEBUG1: hook: 0x000000ae 0x81000001 [2022-07-06T09:41:12] DEBUG1: hook: 0x60ae0000 0x81000001 [2022-07-06T09:41:12] DEBUG1: hook: 0x70ae0000 0x81000001 [2022-07-06T09:41:12] DEBUG1: event: Key char=0, vk=0xae, nagr=0, lParam=0x81000001 [2022-07-06T09:41:12] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:12] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:12] DEBUG1: onKeyUp id=57518 mask=0x2000 button=0x0100 [2022-07-06T09:41:12] DEBUG1: send key up to "chenxy-archlinux" id=57518, mask=0x2000, button=0x0100 [2022-07-06T09:41:12] DEBUG2: writef(DKUP%2i%2i%2i) [2022-07-06T09:41:12] DEBUG2: wrote 10 bytes [2022-07-06T09:41:12] DEBUG2: msg from "chenxy-archlinux": CNOP [2022-07-06T09:41:12] DEBUG2: no-op from [2022-07-06T09:41:12] DEBUG1: hook: 0x000000ae 0x01000001 [2022-07-06T09:41:12] DEBUG1: hook: 0x60ae0000 0x01000001 [2022-07-06T09:41:12] DEBUG1: hook: 0x70ae0000 0x01000001 [2022-07-06T09:41:12] DEBUG1: event: Key char=0, vk=0xae, nagr=0, lParam=0x01000001 [2022-07-06T09:41:12] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:12] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:12] DEBUG1: onKeyDown id=57518 mask=0x2000 button=0x0100 [2022-07-06T09:41:12] DEBUG1: send key down to "chenxy-archlinux" id=57518, mask=0x2000, button=0x0100 [2022-07-06T09:41:12] DEBUG2: writef(DKDN%2i%2i%2i) [2022-07-06T09:41:12] DEBUG2: wrote 10 bytes [2022-07-06T09:41:12] DEBUG2: msg from "chenxy-archlinux": CNOP [2022-07-06T09:41:12] DEBUG2: no-op from [2022-07-06T09:41:12] DEBUG1: hook: 0x000000ae 0x81000001 [2022-07-06T09:41:12] DEBUG1: hook: 0x60ae0000 0x81000001 [2022-07-06T09:41:12] DEBUG1: hook: 0x70ae0000 0x81000001 [2022-07-06T09:41:12] DEBUG1: event: Key char=0, vk=0xae, nagr=0, lParam=0x81000001 [2022-07-06T09:41:12] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:12] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:12] DEBUG1: onKeyUp id=57518 mask=0x2000 button=0x0100 [2022-07-06T09:41:12] DEBUG1: send key up to "chenxy-archlinux" id=57518, mask=0x2000, button=0x0100 [2022-07-06T09:41:12] DEBUG2: writef(DKUP%2i%2i%2i) [2022-07-06T09:41:12] DEBUG2: wrote 10 bytes [2022-07-06T09:41:12] DEBUG2: msg from "chenxy-archlinux": CNOP [2022-07-06T09:41:12] DEBUG2: no-op from [2022-07-06T09:41:12] DEBUG1: hook: 0x000000ae 0x01000001 [2022-07-06T09:41:12] DEBUG1: hook: 0x60ae0000 0x01000001 [2022-07-06T09:41:12] DEBUG1: hook: 0x70ae0000 0x01000001 [2022-07-06T09:41:12] DEBUG1: event: Key char=0, vk=0xae, nagr=0, lParam=0x01000001 [2022-07-06T09:41:12] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:12] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:12] DEBUG1: onKeyDown id=57518 mask=0x2000 button=0x0100 [2022-07-06T09:41:12] DEBUG1: send key down to "chenxy-archlinux" id=57518, mask=0x2000, button=0x0100 [2022-07-06T09:41:12] DEBUG2: writef(DKDN%2i%2i%2i) [2022-07-06T09:41:12] DEBUG2: wrote 10 bytes [2022-07-06T09:41:12] DEBUG2: msg from "chenxy-archlinux": CNOP [2022-07-06T09:41:12] DEBUG2: no-op from [2022-07-06T09:41:12] DEBUG2: writef(CALV) [2022-07-06T09:41:12] DEBUG2: wrote 4 bytes [2022-07-06T09:41:12] DEBUG2: msg from "chenxy-archlinux": CALV [2022-07-06T09:41:12] DEBUG1: hook: 0x000000ae 0x81000001 [2022-07-06T09:41:12] DEBUG1: hook: 0x60ae0000 0x81000001 [2022-07-06T09:41:12] DEBUG1: hook: 0x70ae0000 0x81000001 [2022-07-06T09:41:12] DEBUG1: event: Key char=0, vk=0xae, nagr=0, lParam=0x81000001 [2022-07-06T09:41:12] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:12] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:12] DEBUG1: onKeyUp id=57518 mask=0x2000 button=0x0100 [2022-07-06T09:41:12] DEBUG1: send key up to "chenxy-archlinux" id=57518, mask=0x2000, button=0x0100 [2022-07-06T09:41:12] DEBUG2: writef(DKUP%2i%2i%2i) [2022-07-06T09:41:12] DEBUG2: wrote 10 bytes [2022-07-06T09:41:12] DEBUG2: msg from "chenxy-archlinux": CNOP [2022-07-06T09:41:12] DEBUG2: no-op from [2022-07-06T09:41:12] DEBUG2: msg from "chenxy-archlinux": CNOP [2022-07-06T09:41:12] DEBUG2: no-op from [2022-07-06T09:41:13] DEBUG1: hook: 0x000000af 0x01000001 [2022-07-06T09:41:13] DEBUG1: hook: 0x60af0000 0x01000001 [2022-07-06T09:41:13] DEBUG1: hook: 0x70af0000 0x01000001 [2022-07-06T09:41:13] DEBUG1: event: Key char=0, vk=0xaf, nagr=0, lParam=0x01000001 [2022-07-06T09:41:13] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:13] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:13] DEBUG1: onKeyDown id=57519 mask=0x2000 button=0x0100 [2022-07-06T09:41:13] DEBUG1: send key down to "chenxy-archlinux" id=57519, mask=0x2000, button=0x0100 [2022-07-06T09:41:13] DEBUG2: writef(DKDN%2i%2i%2i) [2022-07-06T09:41:13] DEBUG2: wrote 10 bytes [2022-07-06T09:41:13] DEBUG2: msg from "chenxy-archlinux": CNOP [2022-07-06T09:41:13] DEBUG2: no-op from [2022-07-06T09:41:13] DEBUG1: hook: 0x000000af 0x81000001 [2022-07-06T09:41:13] DEBUG1: hook: 0x60af0000 0x81000001 [2022-07-06T09:41:13] DEBUG1: hook: 0x70af0000 0x81000001 [2022-07-06T09:41:13] DEBUG1: event: Key char=0, vk=0xaf, nagr=0, lParam=0x81000001 [2022-07-06T09:41:13] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:13] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:13] DEBUG1: onKeyUp id=57519 mask=0x2000 button=0x0100 [2022-07-06T09:41:13] DEBUG1: send key up to "chenxy-archlinux" id=57519, mask=0x2000, button=0x0100 [2022-07-06T09:41:13] DEBUG2: writef(DKUP%2i%2i%2i) [2022-07-06T09:41:13] DEBUG2: wrote 10 bytes [2022-07-06T09:41:13] DEBUG2: msg from "chenxy-archlinux": CNOP [2022-07-06T09:41:13] DEBUG2: no-op from [2022-07-06T09:41:13] DEBUG1: hook: 0x000000ae 0x01000001 [2022-07-06T09:41:13] DEBUG1: hook: 0x60ae0000 0x01000001 [2022-07-06T09:41:13] DEBUG1: hook: 0x70ae0000 0x01000001 [2022-07-06T09:41:13] DEBUG1: event: Key char=0, vk=0xae, nagr=0, lParam=0x01000001 [2022-07-06T09:41:13] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:13] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:13] DEBUG1: onKeyDown id=57518 mask=0x2000 button=0x0100 [2022-07-06T09:41:13] DEBUG1: send key down to "chenxy-archlinux" id=57518, mask=0x2000, button=0x0100 [2022-07-06T09:41:13] DEBUG2: writef(DKDN%2i%2i%2i) [2022-07-06T09:41:13] DEBUG2: wrote 10 bytes [2022-07-06T09:41:13] DEBUG2: msg from "chenxy-archlinux": CNOP [2022-07-06T09:41:13] DEBUG2: no-op from [2022-07-06T09:41:13] DEBUG1: hook: 0x000000ae 0x81000001 [2022-07-06T09:41:13] DEBUG1: hook: 0x60ae0000 0x81000001 [2022-07-06T09:41:13] DEBUG1: hook: 0x70ae0000 0x81000001 [2022-07-06T09:41:13] DEBUG1: event: Key char=0, vk=0xae, nagr=0, lParam=0x81000001 [2022-07-06T09:41:13] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:13] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:13] DEBUG1: onKeyUp id=57518 mask=0x2000 button=0x0100 [2022-07-06T09:41:13] DEBUG1: send key up to "chenxy-archlinux" id=57518, mask=0x2000, button=0x0100 [2022-07-06T09:41:13] DEBUG2: writef(DKUP%2i%2i%2i) [2022-07-06T09:41:13] DEBUG2: wrote 10 bytes [2022-07-06T09:41:13] DEBUG2: msg from "chenxy-archlinux": CNOP [2022-07-06T09:41:13] DEBUG2: no-op from [2022-07-06T09:41:14] DEBUG1: hook: 0x000000ad 0x01000001 [2022-07-06T09:41:14] DEBUG1: hook: 0x60ad0000 0x01000001 [2022-07-06T09:41:14] DEBUG1: hook: 0x70ad0000 0x01000001 [2022-07-06T09:41:14] DEBUG1: event: Key char=0, vk=0xad, nagr=0, lParam=0x01000001 [2022-07-06T09:41:14] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:14] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:14] DEBUG1: onKeyDown id=57517 mask=0x2000 button=0x0100 [2022-07-06T09:41:14] DEBUG1: send key down to "chenxy-archlinux" id=57517, mask=0x2000, button=0x0100 [2022-07-06T09:41:14] DEBUG2: writef(DKDN%2i%2i%2i) [2022-07-06T09:41:14] DEBUG2: wrote 10 bytes [2022-07-06T09:41:14] DEBUG2: msg from "chenxy-archlinux": CNOP [2022-07-06T09:41:14] DEBUG2: no-op from [2022-07-06T09:41:14] DEBUG1: hook: 0x000000ad 0x81000001 [2022-07-06T09:41:14] DEBUG1: hook: 0x60ad0000 0x81000001 [2022-07-06T09:41:14] DEBUG1: hook: 0x70ad0000 0x81000001 [2022-07-06T09:41:14] DEBUG1: event: Key char=0, vk=0xad, nagr=0, lParam=0x81000001 [2022-07-06T09:41:14] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:14] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:14] DEBUG1: onKeyUp id=57517 mask=0x2000 button=0x0100 [2022-07-06T09:41:14] DEBUG1: send key up to "chenxy-archlinux" id=57517, mask=0x2000, button=0x0100 [2022-07-06T09:41:14] DEBUG2: writef(DKUP%2i%2i%2i) [2022-07-06T09:41:14] DEBUG2: wrote 10 bytes [2022-07-06T09:41:14] DEBUG2: msg from "chenxy-archlinux": CNOP [2022-07-06T09:41:14] DEBUG2: no-op from [2022-07-06T09:41:14] DEBUG1: hook: 0x000000b0 0x01000001 [2022-07-06T09:41:14] DEBUG1: hook: 0x60b00000 0x01000001 [2022-07-06T09:41:14] DEBUG1: hook: 0x70b00000 0x01000001 [2022-07-06T09:41:14] DEBUG1: event: Key char=0, vk=0xb0, nagr=0, lParam=0x01000001 [2022-07-06T09:41:14] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:14] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:14] DEBUG1: onKeyDown id=57520 mask=0x2000 button=0x0100 [2022-07-06T09:41:14] DEBUG1: send key down to "chenxy-archlinux" id=57520, mask=0x2000, button=0x0100 [2022-07-06T09:41:14] DEBUG2: writef(DKDN%2i%2i%2i) [2022-07-06T09:41:14] DEBUG2: wrote 10 bytes [2022-07-06T09:41:14] DEBUG2: msg from "chenxy-archlinux": CNOP [2022-07-06T09:41:14] DEBUG2: no-op from [2022-07-06T09:41:15] DEBUG1: hook: 0x000000b0 0x81000001 [2022-07-06T09:41:15] DEBUG1: hook: 0x60b00000 0x81000001 [2022-07-06T09:41:15] DEBUG1: hook: 0x70b00000 0x81000001 [2022-07-06T09:41:15] DEBUG1: event: Key char=0, vk=0xb0, nagr=0, lParam=0x81000001 [2022-07-06T09:41:15] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:15] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:15] DEBUG1: onKeyUp id=57520 mask=0x2000 button=0x0100 [2022-07-06T09:41:15] DEBUG1: send key up to "chenxy-archlinux" id=57520, mask=0x2000, button=0x0100 [2022-07-06T09:41:15] DEBUG2: writef(DKUP%2i%2i%2i) [2022-07-06T09:41:15] DEBUG2: wrote 10 bytes [2022-07-06T09:41:15] DEBUG2: msg from "chenxy-archlinux": CNOP [2022-07-06T09:41:15] DEBUG2: no-op from [2022-07-06T09:41:15] DEBUG2: writef(CALV) [2022-07-06T09:41:15] DEBUG2: wrote 4 bytes [2022-07-06T09:41:15] DEBUG2: msg from "chenxy-archlinux": CALV [2022-07-06T09:41:15] DEBUG2: msg from "chenxy-archlinux": CNOP [2022-07-06T09:41:15] DEBUG2: no-op from [2022-07-06T09:41:16] DEBUG1: hook: 0x000000b3 0x01000001 [2022-07-06T09:41:16] DEBUG1: hook: 0x60b30000 0x01000001 [2022-07-06T09:41:16] DEBUG1: hook: 0x70b30000 0x01000001 [2022-07-06T09:41:16] DEBUG1: event: Key char=0, vk=0xb3, nagr=0, lParam=0x01000001 [2022-07-06T09:41:16] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:16] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:16] DEBUG1: onKeyDown id=57523 mask=0x2000 button=0x0100 [2022-07-06T09:41:16] DEBUG1: send key down to "chenxy-archlinux" id=57523, mask=0x2000, button=0x0100 [2022-07-06T09:41:16] DEBUG2: writef(DKDN%2i%2i%2i) [2022-07-06T09:41:16] DEBUG2: wrote 10 bytes [2022-07-06T09:41:16] DEBUG2: msg from "chenxy-archlinux": CNOP [2022-07-06T09:41:16] DEBUG2: no-op from [2022-07-06T09:41:16] DEBUG1: hook: 0x000000b3 0x81000001 [2022-07-06T09:41:16] DEBUG1: hook: 0x60b30000 0x81000001 [2022-07-06T09:41:16] DEBUG1: hook: 0x70b30000 0x81000001 [2022-07-06T09:41:16] DEBUG1: event: Key char=0, vk=0xb3, nagr=0, lParam=0x81000001 [2022-07-06T09:41:16] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:16] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:16] DEBUG1: onKeyUp id=57523 mask=0x2000 button=0x0100 [2022-07-06T09:41:16] DEBUG1: send key up to "chenxy-archlinux" id=57523, mask=0x2000, button=0x0100 [2022-07-06T09:41:16] DEBUG2: writef(DKUP%2i%2i%2i) [2022-07-06T09:41:16] DEBUG2: wrote 10 bytes [2022-07-06T09:41:16] DEBUG2: msg from "chenxy-archlinux": CNOP [2022-07-06T09:41:16] DEBUG2: no-op from [2022-07-06T09:41:17] DEBUG1: hook: 0x000000b1 0x01000001 [2022-07-06T09:41:17] DEBUG1: hook: 0x60b10000 0x01000001 [2022-07-06T09:41:17] DEBUG1: hook: 0x70b10000 0x01000001 [2022-07-06T09:41:17] DEBUG1: event: Key char=0, vk=0xb1, nagr=0, lParam=0x01000001 [2022-07-06T09:41:17] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:17] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:17] DEBUG1: onKeyDown id=57521 mask=0x2000 button=0x0100 [2022-07-06T09:41:17] DEBUG1: send key down to "chenxy-archlinux" id=57521, mask=0x2000, button=0x0100 [2022-07-06T09:41:17] DEBUG2: writef(DKDN%2i%2i%2i) [2022-07-06T09:41:17] DEBUG2: wrote 10 bytes [2022-07-06T09:41:17] DEBUG2: msg from "chenxy-archlinux": CNOP [2022-07-06T09:41:17] DEBUG2: no-op from [2022-07-06T09:41:18] DEBUG1: hook: 0x000000b1 0x81000001 [2022-07-06T09:41:18] DEBUG1: hook: 0x60b10000 0x81000001 [2022-07-06T09:41:18] DEBUG1: hook: 0x70b10000 0x81000001 [2022-07-06T09:41:18] DEBUG1: event: Key char=0, vk=0xb1, nagr=0, lParam=0x81000001 [2022-07-06T09:41:18] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:18] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:18] DEBUG1: onKeyUp id=57521 mask=0x2000 button=0x0100 [2022-07-06T09:41:18] DEBUG1: send key up to "chenxy-archlinux" id=57521, mask=0x2000, button=0x0100 [2022-07-06T09:41:18] DEBUG2: writef(DKUP%2i%2i%2i) [2022-07-06T09:41:18] DEBUG2: wrote 10 bytes [2022-07-06T09:41:18] DEBUG2: msg from "chenxy-archlinux": CNOP [2022-07-06T09:41:18] DEBUG2: no-op from [2022-07-06T09:41:18] DEBUG2: writef(CALV) [2022-07-06T09:41:18] DEBUG2: wrote 4 bytes [2022-07-06T09:41:18] DEBUG2: msg from "chenxy-archlinux": CALV [2022-07-06T09:41:18] DEBUG2: msg from "chenxy-archlinux": CNOP [2022-07-06T09:41:18] DEBUG2: no-op from [2022-07-06T09:41:20] DEBUG1: hook: 0x000000af 0x01000001 [2022-07-06T09:41:20] DEBUG1: hook: 0x60af0000 0x01000001 [2022-07-06T09:41:20] DEBUG1: hook: 0x70af0000 0x01000001 [2022-07-06T09:41:20] DEBUG1: event: Key char=0, vk=0xaf, nagr=0, lParam=0x01000001 [2022-07-06T09:41:20] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:20] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:20] DEBUG1: onKeyDown id=57519 mask=0x2000 button=0x0100 [2022-07-06T09:41:20] DEBUG1: send key down to "chenxy-archlinux" id=57519, mask=0x2000, button=0x0100 [2022-07-06T09:41:20] DEBUG2: writef(DKDN%2i%2i%2i) [2022-07-06T09:41:20] DEBUG2: wrote 10 bytes [2022-07-06T09:41:20] DEBUG2: msg from "chenxy-archlinux": CNOP [2022-07-06T09:41:20] DEBUG2: no-op from [2022-07-06T09:41:20] DEBUG1: hook: 0x000000af 0x81000001 [2022-07-06T09:41:20] DEBUG1: hook: 0x60af0000 0x81000001 [2022-07-06T09:41:20] DEBUG1: hook: 0x70af0000 0x81000001 [2022-07-06T09:41:20] DEBUG1: event: Key char=0, vk=0xaf, nagr=0, lParam=0x81000001 [2022-07-06T09:41:20] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:20] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:20] DEBUG1: onKeyUp id=57519 mask=0x2000 button=0x0100 [2022-07-06T09:41:20] DEBUG1: send key up to "chenxy-archlinux" id=57519, mask=0x2000, button=0x0100 [2022-07-06T09:41:20] DEBUG2: writef(DKUP%2i%2i%2i) [2022-07-06T09:41:20] DEBUG2: wrote 10 bytes [2022-07-06T09:41:20] DEBUG2: msg from "chenxy-archlinux": CNOP [2022-07-06T09:41:20] DEBUG2: no-op from [2022-07-06T09:41:20] DEBUG1: hook: 0x000000ae 0x01000001 [2022-07-06T09:41:20] DEBUG1: hook: 0x60ae0000 0x01000001 [2022-07-06T09:41:20] DEBUG1: hook: 0x70ae0000 0x01000001 [2022-07-06T09:41:20] DEBUG1: event: Key char=0, vk=0xae, nagr=0, lParam=0x01000001 [2022-07-06T09:41:20] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:20] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:20] DEBUG1: onKeyDown id=57518 mask=0x2000 button=0x0100 [2022-07-06T09:41:20] DEBUG1: send key down to "chenxy-archlinux" id=57518, mask=0x2000, button=0x0100 [2022-07-06T09:41:20] DEBUG2: writef(DKDN%2i%2i%2i) [2022-07-06T09:41:20] DEBUG2: wrote 10 bytes [2022-07-06T09:41:20] DEBUG2: msg from "chenxy-archlinux": CNOP [2022-07-06T09:41:20] DEBUG2: no-op from [2022-07-06T09:41:20] DEBUG1: hook: 0x000000ae 0x81000001 [2022-07-06T09:41:20] DEBUG1: hook: 0x60ae0000 0x81000001 [2022-07-06T09:41:20] DEBUG1: hook: 0x70ae0000 0x81000001 [2022-07-06T09:41:20] DEBUG1: event: Key char=0, vk=0xae, nagr=0, lParam=0x81000001 [2022-07-06T09:41:20] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:20] DEBUG1: new mask: 0x2000 [2022-07-06T09:41:20] DEBUG1: onKeyUp id=57518 mask=0x2000 button=0x0100 [2022-07-06T09:41:20] DEBUG1: send key up to "chenxy-archlinux" id=57518, mask=0x2000, button=0x0100 [2022-07-06T09:41:20] DEBUG2: writef(DKUP%2i%2i%2i)
And when long press the vol up:
[2022-07-06T09:44:32] DEBUG1: onKeyRepeat id=57519 mask=0x2000 count=1 button=0x0100 [2022-07-06T09:44:32] DEBUG1: send key repeat to "chenxy-archlinux" id=57519, mask=0x2000, count=1, button=0x0100 [2022-07-06T09:44:32] DEBUG2: writef(DKRP%2i%2i%2i%2i) [2022-07-06T09:44:32] DEBUG2: wrote 12 bytes [2022-07-06T09:44:32] DEBUG2: msg from "chenxy-archlinux": CNOP [2022-07-06T09:44:32] DEBUG2: no-op from [2022-07-06T09:44:32] DEBUG1: hook: 0x000000af 0x01000001 [2022-07-06T09:44:32] DEBUG1: hook: 0x60af0000 0x01000001 [2022-07-06T09:44:32] DEBUG1: hook: 0x70af0000 0x01000001 [2022-07-06T09:44:32] DEBUG1: event: Key char=0, vk=0xaf, nagr=0, lParam=0x01000001 [2022-07-06T09:44:32] DEBUG1: new mask: 0x2000 [2022-07-06T09:44:32] DEBUG1: new mask: 0x2000
Thank you for focus in this issue!

The nuclear option would be to set syn_raw_keycodes to false in the config, recreating the raw keymap as necessary (as barrier is sending a nonsense button ID here).

The nuclear option would be to set syn_raw_keycodes to false in the config, recreating the raw keymap as necessary (as barrier is sending a nonsense button ID here).

Look like set syn_raw_keycodes to false makes the media keys can be detected with different raw key
355.216050750: [WARN] Key 57518 outside configured keymap, dropping
355.311426692: [WARN] Key 57518 outside configured keymap, dropping
355.687007941: [WARN] Key 57518 outside configured keymap, dropping
355.792525201: [WARN] Key 57518 outside configured keymap, dropping
355.975325957: [WARN] Key 57519 outside configured keymap, dropping
356.071800216: [WARN] Key 57519 outside configured keymap, dropping
356.334669981: [WARN] Key 57518 outside configured keymap, dropping
356.455290369: [WARN] Key 57518 outside configured keymap, dropping
356.743454316: [WARN] Key 57517 outside configured keymap, dropping
356.887212997: [WARN] Key 57517 outside configured keymap, dropping
357.111416000: [WARN] Key 57520 outside configured keymap, dropping
357.294007339: [WARN] Key 57520 outside configured keymap, dropping
357.542632473: [WARN] Key 57523 outside configured keymap, dropping
357.789614250: [WARN] Key 57523 outside configured keymap, dropping

But the bad thing is the other keys were mapped to the wrongly key (even no map).
Maybe i need remap all the keys if i need fix the media keys.
Could we just send the 'Synergy mapped key codes' for media keys only? (When detected some special keyCode like 264 and make it configable)

#40 should maybe address this: keep the existing raw keymap, remove syn_raw_keycodes setting altogether, and instead add a new section:
[id-keymap]
57218 = foo
57219 = bar

with foo and bar replaced with whatever uinput code you want for the given key.
Also setting idle-inhibit/keycode will use the exact value provided, with no mapping or offsets of any kind, which should make things more straightforward if you know exactly which value you want to use.

I have tested the id-keymap and working well ! great job.
and idle-inhibit/keycode look like working too
42.837024644: [DEBUG] Got idle event, responding with keypress
42.837050436: [DEBUG] Modifiers: depressed: 0 latched: 0 locked: 0 group: 0
42.837080112: [DEBUG] Modifiers: depressed: 0 latched: 0 locked: 0 group: 0
42.837358796: [DEBUG] Got resume event

It maybe great to print something logs when trigger wlKeyRaw just like wlKey? but whatever, it works well!
https://github.com/r-c-f/waynergy/pull/40/commits/abf7a9b48a5f43903f42842e76d43c770cd7d01f#diff-6282fc15995e77918033a56e50f652d44f40e8a01ac3a1fd68ade5280de89d23L123


how to emit events to stop start webcam

Hi there (I am busy, so the PR will be delayed :/)
However I have a quick question. You are listening for these events:
        $scope.$on('START_WEBCAM', startWebcam);
        $scope.$on('STOP_WEBCAM', stopWebcam);

I was not able to trigger them when switching the view with:
	$scope.$on('$ionicView.beforeLeave', function(){
		console.log("beforeleave");
		$scope.$emit('STOP_WEBCAM');

	});

I am new to angular, so I suppose I am doing something wrong here, maybe you can help :)

got it.
$scope.$broadcast('START_WEBCAM');
However, when emiting START_WEBCAM, it is not visible although the pop-up, asking for permissions appears.

disregard that aswell. I accidentally trigger START_WEBCAM two times, thus creating two video tags, only the second tag shows the stream.
$ionicView.beforeLeave seems to get triggered twice. :/

thank you very much for this: $scope.$broadcast('STOP_WEBCAM') !

Hi @jonashartmann , how do you disable the camera? e.g when navigating to a different state?


Packages: Improve introduction text

Task Description
Page: https://github.com/solettaproject/soletta/wiki/Packages
Talk a little more about what the packages are for, what they hold and what Linux distros we currently support.
Dependencies
None

done


NameError: name 'bollinger_mavg' is not defined

My portfolio and watchlist are displayed and then I get this.
----- Scanning portfolio for stocks to sell -----
Traceback (most recent call last):
File "main.py", line 258, in
scan_stocks()
File "main.py", line 240, in scan_stocks
cross = golden_cross(symbol, n1=50, n2=200, days=30, direction="below")
File "main.py", line 170, in golden_cross
sma1 = bollinger_mavg(price, n=int(n1), fillna=False)
NameError: name 'bollinger_mavg' is not defined
jdubb@Latitude-D630:~/RobinhoodBot/robinhoodbot$
What could this be?

I am assuming the implementation of Bollinger Moving Averages are missing from the code provided. You can either write your own definition to implement it or wait for the authors to provide the code for it.
Here is a repo i found that might help you understand what Bollinger moving/rolling averages are -
[https://github.com/umeshpalai/Rolling-Mean-Bollingerbands/blob/master/Rolling Mean %26 Standard Deviation.ipynb](Umesh's repo)


Try to not indent the active debugging line

This is a screenshot of a debugging session in VS Code insiders:

It would be nice if a source code line does not move if it becomes active - this would make tracking the execution path easier.
Currently, it is indented by the yellow inline decorator.
The yellow arrow could be rendered before the line:

In the special cases where the yellow arrow is in the middle of the line, this does not work. However, this does not happen very often so it is not that annoying.
What do you think @isidorn, @connor4312, @weinand?

Yes, I agree, shifting a line in order to show the arrow is annoying.
But I don't think that there is an easy way to avoid that...
@isidorn ?

Good idea. The thing with decorations is that they always push the text and as far as I know there is no option for the decoration to not push.
So we would need to do some css tricks in order to make this working.
Maybe @alexdima has a good suggestion on a nice way to make decorations not push?

Maybe something similar to what liveshare uses to show the cursor name can be used:

💯 ^💯
I recently thought what makes me still uncomfortable using debug in VSCode and think this is it. I think devtools do this really really well, they never shift a line when debugging, rather:

when a breakpoint is added, the line shifts only (and only) if there are multiple debug breakpoints possible in the line
when you just step over code, no breakpoint is shown, rather the current stopped statement is highlighted
when a breakpoint is added and there are multiple breakpoints possible, each one appears "ghosted" to indicate you can add breakpoints and to reduce the line indentation to just one

Maybe @alexdima has a good suggestion on a nice way to make decorations not push?

I think the LiveShare cursor also uses a ::before decoration. I think there are some CSS properties that you could set on the decoration to make it not push the content. Maybe you could try to inspect element on the LiveShare cursor.

I also face difficulties to follow the execution path when the code I am looking is constantly shifting with this yellow decorator appearing in the middle of a line.
Could I suggest to make this behavior optional as "Show Inline Breakpoint Candidates"?

@alexdima thanks for the idea, I took a liveshare approach to use position: absolute and not push.
To make this nice, I am not pushing when there is space on the left for me to put my decoration. if the decoration is on the middle of the line I will push as before which I think is expected.
You can see it in this gif:

Since this came in pretty late in the endgame and since next 3 weeks I am on vacation, I would need 2 volunteers to test this out for 20-30 minutes, today (out of source) or tomorrow.
Let me know if somebody has time to try it out, would really appreciate it.

@isidorn pls count me in!

I can do tomorrow.

Sold to the two gentlemen from North Germany...

Some testing (only possible out of sources because we have no build today):
I guess here, we cannot prevent the indentation because the breakpoint is in the middle of the line. Imho the only way to make this scenario nicer is to use a different way of indicating the current statement, e.g. like Devtools does with using background color:

What I like about Devtools approach is that they clearly distinguish between a line where I added breakpoints to and a line I am just stepping through:

Here I feel the 2 indicators are not pixel perfectly aligned (I am running with zoom: 1 btw):

Even without zoom I think they are 1px off:

Not sure the padding could be every so slightly greater here in this case:

Didn't find any major issues so far!

like Devtools does with using background color

I think this also helps to see what expression is being evaluated (range vs position).

Yeah especially when you are reaching the end of a function, they do not highlight anything.

@bpasero thanks for testing this out!
Yes I agree that the background color is a better solution because it does not push. I have created this issue so we consider this in the future https://github.com/microsoft/vscode/issues/127776
And as you said they do a great job of: add a breakpoint on a line -> we show you inline breakpoint candidates on that line
I can not get the pixel perfect vertical alignment. I currenty put 2px on top, if I do 3px it looks worse on my machine. So I will stick with the current one.
As for more padding for the cursor at the start of the line I have added 1 px now so it should breathe better.

I tested this for various debuggers and did not find any other problems than this minor nit:
for small indents the arrow gets clipped

BTW, on my LG 5k retina display the vertical alignment of gutter and inline arrows is correct:

@weinand good catch for not enough leading whitespace. We could fix that, but I would not do it now.
As for smaller icon, that makes sense, however let's first try the background approach and if it does not work then we can involve Miguel for a smaller icon.
Also since Retina 5K screen says it is good then I guess it is good :)

BTW, my testing was done with Insiders, so I do not have your latest alignment changes.
And I'm using default fonts and sizes.

@rzhao271 Isi's changes addressed Ben's feedback (https://github.com/microsoft/vscode/issues/124169#issuecomment-872219638)
I've verified that alignment and space between arrow and caret are good:

The vertical alignment is still off for non-default line heights. For an exaggerated height, for instance:

I will actually move to a new issue, I think what we have is fine for release but we should fix this in July.


Need axiom delay on axiom-ls causing 429

Need axiom delay on axiom-ls
causing 429 ratel imiting on 25 droplets.

hey @gprime31 ,
how repeatable is this? Meaning after the rate limit cool down, does it happen constantly? And at what point?
Running doctl account ratelimit will show the current limit ( default is 5,000 an hour ) and how many you have left.

Ah... that cound be it, spun up 50 back-to-back-to-back and 20 small targets. Because i didn't see it at first, then it started happening. However it does not effect the run, the droplets still spin up and shut down like they should.
Thanks, i'll close.

Yep that sounds like it could do it. Glad we got it sorted. let us know if u run into any more issues. :)

Thanks for the support @0xtavian !!!


Xamarin.Auth 1.3.1-alpha-01 nuget package is not installing.

I'm getting the following error trying to install the Xamarin.Auth package in Xamarin Studio on iOS for my PCL project.
How the files look in my packages folder of my project.

The error:
Adding Xamarin.Auth...
Installing 'Xamarin.Auth 1.3.1-alpha-01'.
Added file 'lib\portable-net45+wp8+wpa81+win8+MonoAndroid10+MonoTouch10+XamarinIOS10\Xamarin.Auth.dll' to folder 'Xamarin.Auth.1.3.1-alpha-01'.
Added file 'lib\MonoAndroid10\Xamarin.Auth.dll' to folder 'Xamarin.Auth.1.3.1-alpha-01'.
Added file 'lib\Xamarin.iOS10\Xamarin.Auth.dll' to folder 'Xamarin.Auth.1.3.1-alpha-01'.
Added file 'lib\MonoTouch10\Xamarin.Auth.dll' to folder 'Xamarin.Auth.1.3.1-alpha-01'.
Added file 'lib\wp8\Xamarin.Auth.dll' to folder 'Xamarin.Auth.1.3.1-alpha-01'.
Added file 'lib\wpa81\Xamarin.Auth.dll' to folder 'Xamarin.Auth.1.3.1-alpha-01'.
Added file 'lib\win81\Xamarin.Auth.dll' to folder 'Xamarin.Auth.1.3.1-alpha-01'.
Added file 'Xamarin.Auth.1.3.1-alpha-01.nupkg' to folder 'Xamarin.Auth.1.3.1-alpha-01'.
Successfully installed 'Xamarin.Auth 1.3.1-alpha-01'.
Adding 'Xamarin.Auth 1.3.1-alpha-01' to EventingVolunteers.
Could not install package 'Xamarin.Auth 1.3.1-alpha-01'. You are trying to install this package into a project that targets 'portable-net45+win+wp80+MonoTouch10+MonoAndroid10+xamarinmac20+xamarintvos10+xamarinwatchos10+xamarinios10', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.

Investigating.
Seems that nuget packaging on CI bot which is Mac has issues with '' and '/'. Thanks for the screenshot that helped us to track the '' issue. I will change nuspec ASAP and publish 1.3.1-alpha-02 and will ask you kindly to report if that fixes the issue.

1.3.1-alpha-02 pushed/published few secs ago

Thank you. It works now.

Actually, it appears that there is still a problem with the nuget package. The portable package has the wrong slash issue still:

From previous comment I cannot deduce if the nuget is working or not? Can it be loaded?

From issue #122 seems like nuget is loaded:
https://github.com/xamarin/Xamarin.Auth/issues/122

I looked at the commit. You forgot to change one of the two slashes for the portable dll.

alpha-03 published
Please try it out and see if this version fixes the issue.

Thanks. Fixed.


Added Warning message & card instruction for testing purpose

I have added the following . Please review.

[x] included a line that says that Shop page is still in the Development process.
[x] included a warning that tells the user not to enter their Real Credit/Debit card information
[x] included instructions on what to enter in the credit card field for testing purposes

Great work @chinmaym07!
I went through the changes that you've made and they look good to me, I've gone ahead and requested @hanszhang00 to review the changes as well and then we can merge your commit!
It is a good habit to create an issue about the idea first and then linking your pull request to that issue for organizing the PRs, so try to do that in the future, nevertheless impressive ideas and good job!

Thanks a lot @neverdue and I will make sure to do that in the future ☺

@chinmaym07 good work! I will go ahead and merge the changes.
@neverdue thanks a lot for reviewing the changes! I really appreciate it man.


🔧 Update pyproject.toml

Removed empty line which caused poetry to omit import of additional modules without throwing an error.
(You can test this by keeping the empty line and changing the version of a module after the empty line - notice the module will not update in the updated docker image.)

Thanks! I just migrated the project to uv, so this is probably no longer a problem. I'm gonna close this one now. Thanks! :coffee:


Implemented first and last property for pagination

Added first and last property to the pagination class and relevant tests.
Relevant issue: #567
Travis failed because of python 2.6 no longer being supported by SQLAlchemy see #587.

This will need to get rebased on #687 once it gets merged.  Then, assuming tests still pass, I think this PR is GTG.

Unfortunately, after rebasing this PR onto the 2.x maintenance branch and running tox locally, I periodically see an exception thrown from the 2.7-lowest tox run:
Traceback (most recent call last):
  File "/home/rsyring/projects/flask-sqlalchemy/tests/test_sessions.py", line 33, in test_session_scoping_changing
    assert fb not in db.session  # because a new scope is generated on each call
AssertionError: assert <FOOBar (transient<PHONE_NUMBER>62512)> not in <sqlalchemy.orm.scoping.scoped_session object at 0x7f7cf943bd10>
 +  where <sqlalchemy.orm.scoping.scoped_session object at 0x7f7cf943bd10> = <SQLAlchemy engine=<sqlalchemy.engine.url.URL object at 0x7f7cf93c76d0>>.session

I've not had time to look into it further and don't think this should hold up the 2.4 release.  If it ends up being a quick fix, I'm happy to release it with 2.4.  But if not, I'm going to bump the milestone to 2.x.

For what it's worth I am able to locally reproduce that intermittently-failing test on latest master 42d40b3f7e11d58b05d42ee172464a782ca8ec92/(3.0.0.dev) on Python 3.7 and 2.7, so perhaps not related to the PR?
Unfortunately that's about all I bring to the table right now as I just stumbled in here from a google search and cloned/ran the tests, but hopefully a useful as a datapoint at least.
platform darwin -- Python 3.7.3, pytest-4.5.0, py-1.8.0, pluggy-0.11.0
=================================================== FAILURES ===================================================
________________________________________ test_session_scoping_changing _________________________________________
tests/test_sessions.py:33: in test_session_scoping_changing
    assert fb not in db.session  # because a new scope is generated on each call
E   assert <FOOBar (transient<PHONE_NUMBER>)> not in <sqlalchemy.orm.scoping.scoped_session object at 0x10a305860>
E    +  where <sqlalchemy.orm.scoping.scoped_session object at 0x10a305860> = <SQLAlchemy engine=sqlite:///:memory:>.session

I ended up implementing this a little differently in #1098 to account for a few other things such as the last page not having a full page of items.


Part 2 of reconstruction attack post

This is really great. I think it sends a very clear message. Thanks for writing it.
Here are some comments:

The first paragraph (starting with "This is the second of two posts") seems redundant. Maybe just add a hyperlink to "In the last post" in the second paragraph and remove the first.  In particular, on the dp.org homepage the first paragraph is all that shows.
Maybe mention that diffix, despite the name, is not differentially private.
"A query with Ω(n) conditions is answered with noise with standard deviation Ω(sqrt{n}), enough to thwart the reconstruction algorithms." Maybe say "enough to thwart the efficient reconstruction algorithms"
Link to https://arxiv.org/abs/1810.05692 ?
"restrict the query allowed by Diffix." -> "restrict the queries allowed by Diffix."
"A U.S. social security number consists of a string formatted like xxx-xx-xxxx with ten unknown digits in three blocks separated by dashes. There are potentially ten billion different strings that could appear in this column." ten should be nine and ten billion should be one billion.
In the conclusion "Systems like this fall into the trap of the classic arms race, where a designer builds a system to protect against certain attacks, then a clever and determined adversary defeats the system, and the designer is forced to make revisions." perhaps add a sentence on why this is bad, like "This cycle may never terminate and we can never be confident that it has and that the system is finally secure enough to use."
I note that the pull request is merging into the reconstruction-attacks branch instead of master. An extra merge will be needed to make it go live.

Thanks for the comments. I've incorporated the edits and updated the pull request.


[Remote Translog] Incremental download of translog

Describe the bug
During failover, we read and download the translog metadata and data twice.
To fix
Translog should be read and download only once for 1 IndexShard in its lifetime.

Covered in https://github.com/opensearch-project/OpenSearch/issues/15277 . Closing this .


Beacon chain: g-spec.k

The haskell-backend kprove hangs for g-spec.  The REPL hangs even before starting the REPL command prompt.
The thing is that the g-spec is quite similar to f2-spec in terms of the spec structure and the complexity, but f2-spec is passed.
To reproduce:
$ git clone git@github.com:runtimeverification/beacon-chain-verification.git
$ git checkout bd82ad69a2a8a414209149bb63bd70d5938bba30
$ cd dynamic
$ make deps
$ make build-static
$ kprove -d .build/defn/static -m VERIFICATION tests/symbolic/g-spec.k

It seems that this part (https://github.com/runtimeverification/beacon-chain-verification/blob/master/dynamic/tests/symbolic/g-spec.k#L77-L81) is problematic.  When they are commented out, the REPL quickly returned the command prompt. (Of course, the spec cannot be proved without them.)   Furthermore, among them, these two lines (https://github.com/runtimeverification/beacon-chain-verification/blob/master/dynamic/tests/symbolic/g-spec.k#L79-L80) seem to be most problematic --- if the two lines are commented out, the REPL returned the prompt in ~2min (with nine sub-claims split by the startup simplification).  But with the two lines, the REPL didn't return after 10min, and I killed it.
So, it seems that the startup simplification has a performance bug, when they are more than three equalities that split claims by case analysis.

The problem is an excessive number of branches created in the first step.

Sorry, my last comment was from looking at an old version of g-spec.k. I'm still not sure what the present issue is.


Propagate x-ms-client-default to properties and operation params

This change addresses issue #268 which reports that x-ms-client-default isn't being propagated to the clientDefaultValue field of model properties and operation parameters.  I've wired up clientDefaultValue handling for the following scenarios:

ObjectSchema property (It was already implemented but looking for x-ms-client-default in the wrong place)
Operation parameters (query, path, header)
Operation request bodies

I've also added a unit test that exercises these paths.  I'll run Laurent's new testserver spec with this to see whether it handles all of the cases there correctly.
/cc @lmazuel

Merging this to unblock other work.


Fix #12310

The modified line was syntactically incorrect

Fixes https://github.com/webpack/webpack/issues/12310

What kind of change does this PR introduce?

bugfix for an obvious JS syntax error
Did you add tests for your changes?

Up to you guys
Does this PR introduce a breaking change?

What needs to be documented once your changes are merged?
nothing

And please accept CLA

And please accept CLA

Can you add test?

I think the best would be to make the creator of that part of the code have a look on this. Otherways I'm fine with patch-package...

Can you add test?

I think the best would be to make the creator of that part of the code have a look on this. Otherways I'm fine with patch-package...

Looks good, please also add an test case for this. You can add a case to test/cases/parsing/local-modules.

Sorry, i don't know how to add a test for this. The files you're referring to (test/cases/parsing/local-modules/index.js), as far as I can understand, are not relevant, as they test the behavior of define calls. This is a transformation issue. There's a plain syntax error in one of the transformation templates. I suppose those templates don't have a test yet, otherwise this bug would have been uncovered earlier. But again, I might be missing something about the test suite, I've read test/README.md which didn't really help me in where to look to cover this bug.

Looks good, please also add an test case for this. You can add a case to test/cases/parsing/local-modules.

Sorry, i don't know how to add a test for this. The files you're referring to (test/cases/parsing/local-modules/index.js), as far as I can understand, are not relevant, as they test the behavior of define calls. This is a transformation issue. There's a plain syntax error in one of the transformation templates. I suppose those templates don't have a test yet, otherwise this bug would have been uncovered earlier. But again, I might be missing something about the test suite, I've read test/README.md which didn't really help me in where to look to cover this bug.

Can you add test here https://github.com/webpack/webpack/tree/master/test/configCases

Can you add test here https://github.com/webpack/webpack/tree/master/test/configCases

Thanks

Thanks


Display top 10 active users to bar chart (Dynamically)

The following logics are added:

Get the top 10 active users real-time
Display the name of the user and the number of messages sent by this user to the bar chart.

In my local side:

In the global website:

The nav bar now will change to this when it reaches certain limit.
Clicking on the burger will invoke the side bar, this feature is currently under development, the function is not being invoked somehow.

Hey in this PR, the following functions are working perfectly.

Get the geological location of where the user sends the post and display the result in the GeoChart (Real-time).
Get the top 10 active users and display the result in BarChart (Real-time).
Responsive nav-bar: change to burger sign when the window size is smaller than certain limit. (Currently, the side bar has problem popping up after clicking on the burger sign, while I intend to put this to a new PR.)

Indentation issues have been fixed also.


Knausj windows terminal and powershell integration

Part of #562 :
migrates both the power shell and the windows terminal integration to the new "architecture"

@rntz overlooked that "split right" and co was already implemented in the .talon file.
If you want, I can change "split right" (in the .py file) to do the same as "split vertically". I think my thought at that time was, that since "split left" wasn't possible, I won't do "split right" either. But I am quite open about that.

I believe these changes will solve #770 with the tag "tag(): user.generic_windows_shell" being added to powershell and windows terminal talon files.
Should we also add commands to open new tabs for a given terminal type? Probably ideally this would be a csv file config or read from the windows terminal config itself, but assuming using the default profile numbers for now...e.g.
(open|new) powershell:
    key(ctrl-shift-1)

(open|new) (command prompt|CMD):
    key(ctrl-shift-2)

(open|new) (ubuntu|linux):
    key(ctrl-shift-3)

@choskeli I think in my own fork I solved it with "profile " since I have many more profiles. But you can open a new pull request to add your solution (or ask on of the knausj collaborators how to handle that, I am not one of the maintainers).


Run SonarCloud only on pull requests to master

Run SonarCloud less often to reduce build times for normal CI builds.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: anoraznizam sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


Update api-server version to v1.2.80

Changes in this PR

Bump version to v1.2.80[1] to get the changes in [2].

[1] https://github.com/wso2/identity-api-server/tree/v1.2.80
[2] https://github.com/wso2/identity-api-server/pull/488

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/6183956978

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/6183956978
Status: success


fix: removed feature flag check for workspaces in middleware

Description
Now there is no longer a check in middleware to see if you have the workspaces feature flag enabled or not. Everyone gets access to it.
What type of PR is this? (check all applicable)

[ ] 🍕 Feature
[x] 🐛 Bug Fix
[ ] 📝 Documentation Update
[ ] 🎨 Style
[ ] 🧑💻 Code Refactor
[ ] 🔥 Performance Improvements
[ ] ✅ Test
[ ] 🤖 Build
[ ] 🔁 CI
[ ] 📦 Chore (Release)
[ ] ⏩ Revert

Related Tickets & Documents
Fixes #2711
Mobile & Desktop Screenshots/Recordings

Steps to QA

Ensure you're logged in
Navigate to /
You're redirected to the last workspace you used. Since this will be the first time on this deploy preview, it should be your personal workspace that loads.

Added to documentation?

[ ] 📜 README.md
[ ] 📓 docs.opensauced.pizza
[ ] 🍕 dev.to/opensauced
[ ] 📕 storybook
[ ] 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?
See #2704
[optional] What gif best describes this PR or how it makes you feel?

Nice! 🎏
When this lands on prod, this will essentially launch the MVP?

Yep! I'm removing it from the code and then once we're in prod we're MVP for workspaces, and the last bit will be to delete the feature flag from Posthog once in prod.


Merge in fixes from tejassharma96/pitchfork_api

Copies in the changes done in https://github.com/tejassharma96/pitchfork_api by @tejassharma96
Let me know if I missed anything!

Did the requirements change with @tejassharma96? It looks like there is an error on Travis: ImportError: cannot import name 'HTMLParseError' that might have to do with needing to update requirements.txt.

@johnwmillr I forgot to push up requirements.txt, but that's done now and Travis is happy. Merging.

FYI, this is now published on pypi: https://pypi.org/project/pitchfork/


Bug in compiler sdk 2.5.0-dev.1.0: Expected to get sdk digest at null

Works with dart-sdk 2.5.0-dev.0.0
Works in build mode:
"D:\dart-sdk\dart-sdk 2.5.0-dev.1.0\bin\pub.bat" global run webdev build --output=web:build
But webdev serve fails:
pubspec:
dependencies:
  angular: ^6.0.0-alpha
  angular_components: ^0.14.0-alpha

dev_dependencies:
  angular_test: ^2.3.1
  build_runner: ^1.6.2
  build_test: ^0.10.8
  build_web_compilers: ^2.1.4
  test: ^1.5.1
  stream_channel: ^2.0.0

"D:\dart-sdk\dart-sdk 2.5.0-dev.1.0\bin\pub.bat" global run webdev serve web:53322
[WARNING] Throwing away cached asset graph due to Dart SDK update.
[INFO] Cleaning up outputs from previous builds. completed, took 1.4s
[INFO] Building new asset graph completed, took 2.3s
[INFO] Checking for unexpected pre-existing outputs. completed, took 1ms
[INFO] Serving `web` on http://<IP_ADDRESS>:53322
[SEVERE]build_web_compilers:ddc on package:meta/dart2js.ddc.module: Error compiling dartdevc module:meta|lib/dart2js.ddc.js

We're sorry, you've found a bug in our compiler.
You can report this bug at:
    https://github.com/dart-lang/sdk/issues/labels/area-dev-compiler  <-- URL DOES NOT EXIST!
Please include the information below in your report, along with
any other information that may help us track it down. Thanks!
-------------------- %< --------------------
    dartdevc -k arguments: --dart-sdk-summary=D:\dart-sdk\dart-sdk 2.5.0-dev.1.0/lib/_internal/ddc_sdk.dill --modules=amd --no-summarize -o C:\Users\Stephan\AppData\Local\Temp\scratch_spacefff4af8f-adf2-11e9-920f-f01faf42001c\packages/meta/dart2js.ddc.js --source-map --packages=file:///C:/Users/Stephan/AppData/Local/Temp/kernel_builder_fff4afa6-adf2-11e9-920f-f01faf42001c/.packages --module-name=packages/meta/dart2js --multi-root-scheme=org-dartlang-app --multi-root=. --track-widget-creation --inline-source-map package:meta/dart2js.dart
    dart --version: 2.5.0-dev.1.0 (Tue Jul 9 15:27:01 2019 +0200) on "windows_x64"

Bad state: Expected to get sdk digest at null
#0      initializeIncrementalCompiler (package:front_end/src/api_unstable/ddc.dart:149:5)
<asynchronous suspension>
#1      _compile (package:dev_compiler/src/kernel/command.dart:252:27)
<asynchronous suspension>
#2      compile (package:dev_compiler/src/kernel/command.dart:43:18)
<asynchronous suspension>
#3      compile (package:dev_compiler/src/compiler/shared_command.dart:408:12)
#4      _CompilerWorker.performRequest.<anonymous closure> (file:///C:/b/s/w/ir/cache/builder/sdk/pkg/dev_compiler/bin/dartdevc.dart:64:13)
#5      _rootRun (dart:async/zone.dart:1124:13)
#6      _CustomZone.run (dart:async/zone.dart:1021:19)
#7      _runZoned (dart:async/zone.dart:1516:10)
#8      runZoned (dart:async/zone.dart:1463:12)
#9      _CompilerWorker.performRequest (file:///C:/b/s/w/ir/cache/builder/sdk/pkg/dev_compiler/bin/dartdevc.dart:62:24)
<asynchronous suspension>
#10     AsyncWorkerLoop.run.<anonymous closure> (package:bazel_worker/src/worker/async_worker_loop.dart:33:41)
#11     _rootRun (dart:async/zone.dart:1124:13)
#12     _CustomZone.run (dart:async/zone.dart:1021:19)
#13     _runZoned (dart:async/zone.dart:1516:10)
#14     runZoned (dart:async/zone.dart:1463:12)
#15     AsyncWorkerLoop.run (package:bazel_worker/src/worker/async_worker_loop.dart:33:26)
<asynchronous suspension>
#16     main (file:///C:/b/s/w/ir/cache/builder/sdk/pkg/dev_compiler/bin/dartdevc.dart:28:57)
<asynchronous suspension>
#17     _startIsolate.<anonymous closure> (dart:isolate-patch/isolate_patch.dart:301:32)
#18     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:172:12)

This error then repeats for:
[SEVERE]build_web_compilers:ddc on package:logging/logging.ddc.module: Error compiling dartdevc module:logging|lib/logging.ddc.js
[WARNING]build_web_compilers:entrypoint on web/main.dart: Unable to read logging|lib/logging.ddc.js, check your console or the `.dart_tool/build/generated/logging/lib/logging.ddc.js.errors` log file.
[SEVERE]build_web_compilers:ddc on package:meta/meta.ddc.module: Error compiling dartdevc module:meta|lib/meta.ddc.js
[SEVERE]build_web_compilers:ddc on package:collection/src/comparators.ddc.module: Error compiling dartdevc module:collection|lib/src/comparators.ddc.js
[WARNING]build_web_compilers:entrypoint on web/main.dart: Unable to read meta|lib/dart2js.ddc.js, check your console or the `.dart_tool/build/generated/meta/lib/dart2js.ddc.js.errors` log file.
[WARNING]build_web_compilers:entrypoint on web/main.dart: Unable to read meta|lib/meta.ddc.js, check your console or the `.dart_tool/build/generated/meta/lib/meta.ddc.js.errors` log file.
[SEVERE]build_web_compilers:ddc on package:collection/src/utils.ddc.module: Error compiling dartdevc module:collection|lib/src/utils.ddc.js

plus a few dozen more...

A change has landed that should fix and will be included in the next dev release.
Duplicate of #37490.


adds description of field format type to field compliance dialog

Coverage remained the same at 27.594% when pulling e0d7365d771008778f2fb1a54b1e0462791e4929 on theseyi:field-format-desc into a20ca2a0ddff7d341fda5d937fa4a7e7db3c2e41 on linkedin:master.

Codecov Report

Merging #1255 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #1255   +/-   ##
======================================
  Coverage    5.83%   5.83%
======================================
  Files          57      57
  Lines        2211    2211
  Branches      478     478
======================================
  Hits          129     129
  Misses       2082    2082

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 a20ca2a...e0d7365. Read the comment docs.


Steps to do after proposal accepted

in the evolution process description, adding steps to do after a proposal is accepted (create repos, announce, etc.)
If something is missing, please comment

Can we use this opportunity to also add a note about submitting an ECA and signing off on commits? e.g. https://wiki.eclipse.org/Development_Resources/Contributing_via_Git


[PE-D] Not enough examples for 'find' command

Firstly

Example on UG given was for 'For names, only full words will be matched'. Personally, as a user, I felt it would be good if there is an example that shows partial match .
Secondly

I felt like there should be a mentioning of how find command work between prefixes (and or or).

Labels: type.DocumentationBug severity.Medium
original: DALIN-Prog/ped#3

Intended functionality.