Bump promu to v0.5.0

It also includes an update of RELEASE.md since this version simplifies a
bit the release process: promu will take care of drafting the GitHub
release.
cc @brancz as the next release shepherd.

Neat! I'm assuming we just have to be consistent, but how does matching from the changelog -> git tag -> github release title work?
Generally lgtm, feel free to merge, still interested though.

how does matching from the changelog -> git tag -> github release title work?

promu release parses the changelog and extracts the last entry from it. The title of the section makes the title of the release. The git tag is generated manually but if you blindly apply the instructions from RELEASE.md, it should just :tm: work.

@brancz promu parses the markdown in the changelog. The specifics are in the getChangelog() function.

We have a few repos where we don't use CHANGELOG.md. For example, blackbox_exporter changelogs are done manually in the github release only.


[bug] Setting default window to as invisible in the config it leads to Tauri crashing on Linux.

Describe the bug
I am trying to have the window hidden by default while I spawn a new process and then show the window but on Linux, if you set the default window to be invisible in the config it leads to Tauri crashing, works fine on Windows & macOS.
Reproduction

Set visible property in windows to false & run the app

 "windows": [
      {
        "label": "main",
        "title": "main",
        "width": 1000,
        "height": 700,
        "resizable": true,
        "fullscreen": false,
        "center": true,
        "focus": true,
       "visible": false
      }
],

Expected behavior
To have the default window stay invisible until it is set to visible without crashing.
Platform and versions
Environment
  › OS: Ubuntu 22.04 X64
  › Node.js: 14.16.0
  › npm: 8.1.2
  › pnpm: Not installed!
  › yarn: 1.22.10
  › rustup: 1.24.3
  › rustc: 1.60.0
  › cargo: 1.60.0
  › Rust toolchain: stable-x86_64-unknown-linux-gnu

Packages
  › @tauri-apps/cli [NPM]: 1.0.0-rc.10
  › @tauri-apps/api [NPM]: 1.0.0-rc.3
  › tauri [RUST]: 1.0.0-rc.10,
  › tauri-build [RUST]: 1.0.0-rc.8,
  › tao [RUST]: 0.8.4,
  › wry [RUST]: 0.16.2,

App
  › build-type: bundle
  › CSP: unset
  › distDir: ../build
  › devPath: http://localhost:3000/
  › framework: React

App directory structure
  ├─ node_modules
  ├─ src
  ├─ scripts
  ├─ .git
  ├─ .github
  ├─ src-tauri
  ├─ build
  └─ public

Stack trace
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', /home/fayeed/.cargo/registry/src/github.com-1ecc6299db9ec823/tao-0.8.4/src/platform_impl/linux/window.rs:602:39
stack backtrace:
   0: rust_begin_unwind
             at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panicking.rs:584:5
   1: core::panicking::panic_fmt
             at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/core/src/panicking.rs:143:14
   2: core::panicking::panic
             at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/core/src/panicking.rs:48:5
   3: core::option::Option<T>::unwrap
             at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/core/src/option.rs:752:21
   4: tao::platform_impl::platform::window::Window::current_monitor
             at /home/fayeed/.cargo/registry/src/github.com-1ecc6299db9ec823/tao-0.8.4/src/platform_impl/linux/window.rs:602:18
   5: tao::window::Window::current_monitor
             at /home/fayeed/.cargo/registry/src/github.com-1ecc6299db9ec823/tao-0.8.4/src/window.rs:914:5
   6: tauri_runtime_wry::center_window
             at /home/fayeed/.cargo/registry/src/github.com-1ecc6299db9ec823/tauri-runtime-wry-0.5.1/src/lib.rs:2857:26
   7: tauri_runtime_wry::create_webview
             at /home/fayeed/.cargo/registry/src/github.com-1ecc6299db9ec823/tauri-runtime-wry-0.5.1/src/lib.rs:2941:13
   8: <tauri_runtime_wry::Wry<T> as tauri_runtime::Runtime<T>>::create_window
             at /home/fayeed/.cargo/registry/src/github.com-1ecc6299db9ec823/tauri-runtime-wry-0.5.1/src/lib.rs:1936:19
   9: tauri::app::Builder<R>::build
             at /home/fayeed/.cargo/registry/src/github.com-1ecc6299db9ec823/tauri-1.0.0-rc.10/src/app.rs:1418:22
  10: ad4min::main
             at ./src/main.rs:59:26
  11: core::ops::function::FnOnce::call_once
             at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/core/src/ops/function.rs:227

Additional context
No response

Does somebody got a better idea than this?

Don't panic in tao's current_monitor function, return None instead (Unless this is a bug and it's supposed to have a gtk window).
Maybe use the primary monitor as a fallback if current_monitor returns None? I don't know if that would be

And, unrelated but annoying, center() doesn't account the monitor position which leads to the window being moved to the leftmost monitor (and with different monitor sizes it ends up not being centered). I think the fix could be as easy as this?
// Inside center_window() in tauri-runtime-wry
#[cfg(target_os = "linux")]
window.set_outer_position(WryPhysicalPosition::new(
        monitor_pos.x + x,
        monitor_pos.y + y,
));

Fixed in tao 0.8.5, to use that just run cd src-tauri && cargo update -p tao (still publishing, will be ready in a few minutes). I'll fix the center API in a separate PR.


App registration need to be multi-tenant

This is not specified in the documentation. But if you want to allow users from other directories. The application will need to be set to multi-tenant. Otherwise, the consent process will fail.

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

ID: 692852cd-11a6-1d6b-9540-caec9d0f14a4
Version Independent ID: 4c376561-6015-6dab-e23e-feffe74ccc8b
Content: Authorize developer accounts by using Azure Active Directory - Azure API Management
Content Source: articles/api-management/api-management-howto-aad.md
Service: api-management
GitHub Login: @miaojiang
Microsoft Alias: apimpm

Hi @ehrnst Thanks for your feedback. We will review and update as appropriate.

@ehrnst I have assigned this to content author for further review and update as appropriate.

This issue has been resolved. Please reach out or create a new issue if you have any more questions or concerns. Thank you! #please-close


remove NO_NEG_DIV flag and hard-code it in the division operator

now that the soft-fork has activated.
This patch removes all logic around having two separate op_div functions and makes a single one with the NO_NEG_DIV behavior. The test cases for the /-operator are updated to expect the no-negative-div behavior.
Since the soft-fork to disallow division with negative numbers activated a long time ago, there is no reason to keep this flag around anymore. It only creates a risk of forgetting to pass it in.

we pin our dependencies, so the fixup has to happen when we bump the dependency. This can be done atomically in the same commit (or at least PR)


Initial Support for "Solar charger"

Summary :memo:
These changes will implement the initial support for Victron Solar Chargers. Currently tested with BlueSolar 75/15.
Details
Due to missing devices on the load connector, displaying the load could not be tested properly. All other values are in sync with the output of the Victron App.
Checks

[ ] Closed #798
[ ] Tested Changes
[ ] Stakeholder Approval

Here is a sample output:
INFO:victron_ble.scanner:Reading data for ['d7:70:ba:8e:59:a2'] {   "name": "California Solar",   "address": "D7:70:BA:8E:59:A2",   "rssi": -53,   "payload": {     "charge_state": "bulk",     "current": 0.5,     "load": 0,     "power": 7,     "voltage": 12.7,     "yield_today": 10   } }

Amazing work! Can you please add a set of new test cases as well for the new SolarCharger device class so we make sure we don't break the parsing logic in the future?

Looking good! Can you duplicate tests from https://github.com/keshavdv/victron-ble/blob/main/tests/test_dc_energy_meter.py into a new file with some of your broadcasted data to improve coverage on the new code?

Looking good! Can you duplicate tests from https://github.com/keshavdv/victron-ble/blob/main/tests/test_dc_energy_meter.py into a new file with some of your broadcasted data to improve coverage on the new code?

Tests have been added.

I had to strip off the upper bytes to get the load:            pkt.external_device_load & 0x01FFMaybe the upper bytes indicate if the load-output exists or not? Could you output the following for debug purposes:            pkt.external_device_load & 0xFE00How many values do you see in the Victron App for your Solar Charger? Any additional data?The other possibility is, that Victron has hard-coded the available values per device.Am 31.12.2022 um 00:07 schrieb Keshav Varma @.***>:
@keshavdv commented on this pull request.
In victron_ble/devices/solar_charger.py:

PACKET = Struct(

   # Charge State:   0 - Off

   #                 3 - Bulk

   #                 4 - Absorption

   #                 5 - Float

   "charge_state" / Int16sl,

   # Battery voltage reading in 0.01V increments

   "battery_voltage" / Int16ul,

   # Battery charging Current reading in 0.1A increments

   "battery_charging_current" / Int16ul,

   # Todays solar power yield in 10Wh increments

   "yield_today" / Int16ul,

   # Current power from solar in 1W increments

   "solar_power" / Int16ul,

   # External device load in 0.1A increments

   "external_device_load" / Int16ul,

@stefanor Which model are you testing with? I think only the smaller output models have dedicated load outputs so I wonder if these values are nonsense for the other models.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

I've moved the "ChargerState" into base.py


Modular User Edit Components

Summary
Because of the addition of customizable values that are added to the user class, the edit pages must be able to support the generation of new edit fields for the sake of keeping the new information up to date.
Details

The primary roster edit page must support modular components that have been added to the user class through Assignable values detailed in #301
Processes such as Promotion, Qualification submissions, etc. need to be configurable with Assignable values.

Closed in favor of #333


Question about data_util.py

I find that data_util.py ignores comma while parsing babi task. That is, if the answer of a question is s,w(denotes south and west in positional_reasoning), this parser would treat them as a unit. Furthermore, while asking what stuff someone has and the answer would be "milk,pen,hat" or something like that, the parser would treat them as a unit as well. Is that a correct way?

Hi guohanyu123,
Sorry for the late reply. Since MemN2N assumes that each answer is just one word, "s,w" and "milk,pen,hat" should be treated as units.

Thanks for your reply, vinhkhuc. So apart from MemN2N, can I say that adding an RNN decoder for seq2seq output would provide a better performance? I am just wondering.

That's an interesting question. I'm not sure if anyone has tried it before. Also, using grammar tree parser + word embedding may help.
Besides that, adding gradient noise can improve the accuracy of memory networks: http://arxiv.org/abs/1511.06807.


Return code from ble_hs_hci_cmd_tx is HEX207, while it should be a BLE_HS_E... type of error

Hi all!
Im porting the driver part of the Nimble stack to my own platform. The whole thing is work in progress and i'm trying to run the stack. The problem that I run into right now, is running the Advertisement example where
Now, in the call ble_hs_hci_cmd_tx(..) at line 338 "rc = ack.bha_status". This value is set to DEC519, which translates to 0x207. However, if I look at the definition of the ACK type, i see in the comment that I have to interpret this error as /* A BLE_HS_E<...> error; NOT a naked HCI code. */
Now, looking at https://mynewt.apache.org/latest/network/docs/ble_hs/ble_hs_return_codes.html , there is no code BLE_HS_E... with the value 0x207. For sure, a normal HCI can take that value, but it should not be interpreted that way.
Q1: How should I terpret this rc? As a HS or a HCI rc?
Q2: Why is the rc set to a value it could in theory not take? The RC is incompatible with ack.bha_status.
Cheers,
Rob

error codes with base 0x200 are HCI errors so 0x207 is a HCI error code 7 (memory capacity exceeded)

I see that my question was not completely clear;
Do I have to trust the comment behind the struct definition of the ack struct saying
bha_status /* A BLE_HS_E<...> error; NOT a naked HCI code. */
This is since there is a HCI code set to that field, although the documentation says it should not.

comment is correct - this is not a raw HCI code, but a HCI code converted to BLE_HS error so it can be returned to application and will not be confused with "standard" BLE_HS error. each raw HCI code has corresponding BLE_HS error which is basically HCI code + 0x200 and this is what is set in bha_status

Ah, I see, Missed the conversion step, sorry. Thanks for the quick reply!


Doc changes

I noticed the typo of Immutalbe in the 1.8.0 release notes. I went looking for other small typos.

Thank you @phil-davis


restic restore helper image can be configured with cli flag

This is an attempt to address #638. I also did not find it straightforward to pass the image from a velero server argument to the plugin command. So, I tried to keep changes to a minimum and to just get something working but I'm sure this could be improved. I'd be happy to continue to refine this PR but would love to get some feedback before spending too much time on it. I'd really just like to help get a fix for this so that we can use an official velero build in our on-prem, air gapped environment.

Thanks for this @ryane. We should consider the approach here as part of #584 - do we want to use ConfigMaps instead of CLI flags for configuring plugins? We shouldn't have to change code every time a new flag/config option is added. cc @carlisia

This looks good @ryane. If it could be made to use ConfigMap for this plugin config it would be better.

@ryane we decided to go with a ConfigMap-based approach since it will be more extensible for generic configuration of all plugins. See #1311 which recently merged. Appreciate the PR regardless!

excellent, thx!


Error while running the pipeline 05_03_Pipeline_mnist.ipynb

Notebook
05_03_Pipeline_mnist.ipynb
Describe the bug
in the third step of the pipeline we are getting struck
with below error
"/usr/local/lib/python3.6/dist-packages/tensorflow_estimator/python/estimator/training.py", line 246, in new
exporters = _validate_exporters(exporters)
File "/usr/local/lib/python3.6/dist-packages/tensorflow_estimator/python/estimator/training.py", line 86, in _validate_exporters
' {}'.format(full_list_of_names))
ValueError: An Exporter cannot have a name that is None or empty. All exporter names: ['']
Expected behavior
expect the sample pipeline to work without any issues
Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

EKS version: 1.17
Kubeflow version:  1.1
eks-kubeflow-workshop version: v1.0.2 release

/assign


Modified the GPU documentation structure.

Description
Previously the administrative part and usage part were intermixed.
Urgency

[ ] Blocker
[x] High
[ ] Medium

Requirements

Test all commands and procedures.
Build content locally and test for formatting/links.
Add redirects to dcos-website/redirect-files.
Change all affected versions (e.g. 1.7, 1.8, and 1.9).
See the contribution guidelines.

@joerg84 I made some changes (fixed links, text edits, moved the doc out of the "marathon" section). If you are OK with the changes, I will merge.

LGTM

@joerg84 @sascala this directory should be named /gpu/ not /gpus/

@joerg84 @sascala another problem i have had to fix is that the enterprise documentation was not updated with these changes (e.g. topic moved from administration to usage were not deleted from enterprise docs).


Split deploy into (local) install and (remote) deploy

See https://github.com/slipset/deps-deploy/discussions/44 for more background.

install should use tools.build's install task for local installation.
deploy should continue to use deps-deploy's deploy task but warn if :installer is present and not :remote.

Downstream users of build-clj need usage/documentation updates since they currently explain how to use deploy for local installs.

Docs https://clojure.github.io/tools.build/clojure.tools.build.api.html#var-install

install task added and documented; need to update downstream consumers.


Text detection

Not completed. Hasn't been tested due to the lack of a device. Need to implement responsive functionality to display text.


Ignore files in diff with .gitattributes

fixes #12653
close #16262
first step for #14786, #14528
This PR adds a .gitattributes parser to Gitea. It works like on Gitlab and "caches" the .gitattribute file from the root of the default branch in repo.git/info/attributes. The diff supports now the linguist-generated keyword and hides these file in the output.

I still need to try this out, but does it also hide the diff for linguist-generated, like in GitHub?
I think even better would be to collapse the diff (AND not run the diffing algo, but that's not required here).

nope.
This is not the way.
git check-attr is the correct tool.

I still need to try this out, but does it also hide the text diff by default for linguist-generated, like in GitHub?
I think even better would be to collapse the diff (AND not run the diffing algo until it's needed).

The diff is initially hidden like on Github. The diff is not delayed because that's how Gitea works at the moment. See https://github.blog/2016-12-06-how-we-made-diff-pages-3x-faster/ how Github may do it.

git check-attr is the correct tool.

Yes, the correct tool but it does not work with bare repos. See https://gitlab.com/gitlab-org/gitlab-foss/-/issues/2315#note_3339982 and the following posts.

git check-attr is the correct tool.

Yes, the correct tool but it does not work with bare repos. See https://gitlab.com/gitlab-org/gitlab-foss/-/issues/2315#note_3339982 and the following posts.

False. We already use git check-attr in bare repositories.
Please look at:
https://github.com/go-gitea/gitea/blob/main/modules/git/repo_attribute.go
There is already an aborted partial attempt at getting the language from the repo attributes in #14833 which is almost there.

Cool, don't know why it didn't work for me yesterday 🤷♂
I added a new version of this PR which uses check-attr. The copy of the .gitattributes skips the creation of a temporary index.

It should also check enry.IsGenerated

replaced by #16773


[Components] Create storybook components for "Internal Pages"

Context
The internal page components can be found here: https://www.figma.com/file/aoIxdVZVGltGy4lWetuWKU/Component-Library-(External)?node-id=0%3A1
Acceptance Criteria
The following components can be created from the internal reference:

[x] H1, H2, H3, H4, H5, H6
[ ] #29
[x] Attribution elements
[x] Paragraphs
[x] Sidebar menu overlay
[x] Sidebars
[x] Interior Page Layout
[x] Lists
[x] Links
[x] Quotes
[x] Images
[x] Table
[x] Callouts (skip upload callout)
[x] Lower page navigation
[ ] Footnotes (waiting for mdx rendering)
[x] Breadcrumbs
[x] Version picker

Interior Landing Page components (located in "Landing Page components in the component library):

[x] "Cadence Header"
[X] "Cadence Card"
[x] "Cadence Header Card"
[ ] "Intro section"
Note that I would change the naming of these as they will be used generically for any tool

Status update:

Created storybook components for headings, attributions, paragraphs, left sidebar, table of contents sidebar
Created the interior page layout, and connected everything except attributions and the left nav to the markdown renderer

Next steps:

Discuss codeblocks and nav switcher
Add any other components from the interior page design

@srinjoyc I added the remaining components under Additional components above, let me know if any are missing

Thanks @alse - double checked here and that looks accurate!

Status update:

Added Tables, Callouts, Lower page nav, Breadcrumbs, Internal version select, Internal sidebar menu in #40 .
Footnotes are partially finished, and waiting for mdx rendering

Next steps:

Interior Landing Page components

Status update:

Finished the cadence header & cards
@srinjoyc I added the title/cta/image section to the list as "Intro section" (From Tool landing page)

Next steps:

Intro section and codeblock

@srinjoyc I added the code block styling + modal in #75 . I'll check it off as done in this issue, and we can continue any code highlighting + mdx rendering work as part of #29


Update aws-java-sdk-core to 1.12.772

About this PR
📦 Updates com.amazonaws:aws-java-sdk-core from 1.12.459 to 1.12.772
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.amazonaws", artifactId = "aws-java-sdk-core" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.amazonaws", artifactId = "aws-java-sdk-core" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #810.


Running 2 client together from sample app. First client works fine but second client gives 400 error

Running 2 client together from sample app. First client works fine but second client gives 400 error.
Steps to reproduce
Run both app and open up login screen together try to login in both of them one by one.
First client will be logged in perfectly but second client returns 400(Screenshot attached).

Your second client is most likely miss-configured. Try adding logging to the application. Identity Server will write the error to your log file.

Thanks @bobekhj for replying.
Firstly i am using sample code of identity server and i haven't made any change in the code.
Secondly if i try to run the second client first then it works but the first client will give me error...:-(

dup of https://github.com/IdentityServer/IdentityServer4/issues/3339


Incorrect Page Title. Displaying "Frontity Site"

Site wanerd.com
conflict with site-info:
connection siteinfo

endpoint siteinfo

Fixed with a redeploy.


Deal with autoencoder training "dead neurons"

We know from Anthropic's paper that sparse autoencoders will, in practice, not utilize all the neurons made available to them. Autoencoder neurons that cannot activate are called "dead neurons." Detecting any dead neurons during autoencoder training and automatically perturbing/further training them in Anthropic's fashion should improve autoencoder expressiveness.

When I train the autoencoders on openwebtext rather than the much skimpier truthful_qa, there are then almost no unused autoencoder dimensions at an autoencoder 10 times later than the hidden dimension. This doesn't mean no dead neurons are present, but does mean that the truthful_qa autoencoder training was on quite a small dataset relative to trainable parameters.
I will still verify dead neuron count, in both cases.

At least stdout a dead neuron count from train_autoencoder.


Initial fuzzing support

Verify that the results of all implementations match using a fuzzer.
See the Rust fuzz book for details.

Hello,
Thank you @Shnatsel for submitting this PR. It was one of the items in my to do list and was happy to see it already completed.

These have found no failures after ~250 million iterations, so congrats on the great work!


Custom snippet paths should be expanded

Feature Description
I'm loving the native snippets implementation. I'm choosing to add my own custom snippet location like so:
sources = {
  default = {  "lsp", "path", "snippets", "buffer" },
  providers = {
    snippets = {
      opts = {
        search_paths = { "/Users/Oli/.config/snippets" },
      }
    },
  }
}

However, if I change the path to ~/config/snippets it doesn't work. happy to add this as a PR.

PR welcome!


fix: fix modal close contrast

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[x] My changes do not use shortened URLs or affiliate links.

Closes #37834
Closes #37378

locally built and tested


feat(apps): apps:run will now print on stderr if the command errors

deis/workflow-cli#81
Requires workflow-cli#7d1fe129bc6721c31940a5d93a5d396a4d5839df

This is failing because the CLI is being cached by docker, but I'm not sure what to do about it.

As a temporary fix I'm just changing docker to download the version of the CLI this PR requires. We'll talk more about the underlying cause in #167


Indentation-rule do code wrapping instead of just indentation

I think that is quite problematic that Indentation-rule currently does more than indentation check, it actually checks line breaking and auto-formatting wrap code.  I found that enable auto line breaking is too code-breaking for me and it is very hard to make it compatible with Android Studio, even when I apply code formatting setup by ktlint.
I generally don't like automatic line breaking and I prefer to do it manually. But I still want to check and fix the correct indentation. Would be please possible to split indentation and line-breaking to two different rules set, please?

Yes, that's what we are planning to do (see #764) and the split you suggested would make a lot of sense imo


current volunteer dashboard

As a Volunteer, I want to be able view tasks  assigned by the admin.
I need to view each task separately
So that I can choose which task that I want to complete
Acceptance Criteria
Given the volunteer is on the dashboard,
When the Volunteer selects the tasks menu ,
Then the system should show the volunteer all tasks assigned by the admin


Trying (and failing) to add Eberg Cooly C35HD support

I've decoded most needed dpcodes so far, and generated the following yaml, but the integrations crashes on config flow for me. I can't really spot where i'm making the error. Any pointers?
name: Eberg Cooly C35HD
primary_entity:
  entity: climate
  dps:
    - id: 1
      name: power
      type: boolean
      mapping:
        - dps_val: false
          value: "off"
          icon: "mdi:hvac-off"
          icon_priority: 1
      hidden: true
    - id: 4
      name: unknown_4
      type: integer
    - id: 5
      name: hvac_mode
      type: string
      mapping:
        - dps_val: 3
          icon: "mdi:snowflake"
          icon_priority: 2
          constraint: power
          conditions:
            - dps_val: false
              value_redirect: power
            - dps_val: true
              value: cool
        - dps_val: 4
          icon: "mdi:fan"
          icon_priority: 2
          constraint: power
          conditions:
            - dps_val: false
              value_redirect: power
              value: "off"
            - dps_val: true
              value: fan_only
        - dps_val: 2
          icon: "mdi:water"
          icon_priority: 2
          constraint: power
          conditions:
            - dps_val: false
              value_redirect: power
            - dps_val: true
              value: dry
        - dps_val: 1
          icon: "mdi:fire"
          icon_priority: 2
          constraint: power
          conditions:
            - dps_val: false
              value_redirect: power
            - dps_val: true
              value: heat
    - id: 6
      name: temperature
      type: integer
      mapping:
        - constraint: temperature_unit
          conditions:
            - dps_val: true
              range:
                min: 13
                max: 32
            - dps_val: false
              range:
                min: 55
                max: 90
    - id: 8
      name: fan_mode
      type: string
      mapping:
        - dps_val: 0
          value: "auto"
        - dps_val: 1
          value: "low"
        - dps_val: 2
          value: "medium"
        - dps_val: 3
          value: "high"
    - id: 10
      name: temperature_unit
      type: boolean
      mapping:
        - dps_val: true
          value: "C"
        - dps_val: false
          value: "F"
    - id: 13
      type: integer
      name: unknown_13
    - id: 14
      type: integer
      name: unknown_14
    - id: 15
      type: integer
      name: unknown_15
    - id: 16
      name: swing_mode
      type: boolean
      mapping:
        - dps_val: true
          value: "vertical"
        - dps_val: false
          value: "off"
    - id: 17
      type: boolean
      name: unknown_15
    - id: 18
      type: int
      name: unknown_18
    - id: 19
      type: boolean
      name: unknown_19

2021-12-21 23:04:25 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/aiohttp/web_protocol.py", line 435, in _handle_request
resp = await request_handler(request)
File "/usr/local/lib/python3.9/site-packages/aiohttp/web_app.py", line 504, in _handle
resp = await handler(request)
File "/usr/local/lib/python3.9/site-packages/aiohttp/web_middlewares.py", line 117, in impl
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 60, in security_filter_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 220, in forwarded_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 28, in request_context_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 78, in ban_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 181, in auth_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 137, in handle
result = await result
File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 157, in post
return await super().post(request, flow_id)
File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 62, in wrapper
result = await method(view, request, *args, **kwargs)
File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 110, in post
result = await self._flow_mgr.async_configure(flow_id, data)
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 252, in async_configure
result = await self._async_handle_step(flow, cur_step["step_id"], user_input)
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 325, in _async_handle_step
result: FlowResult = await getattr(flow, method)(user_input)
File "/config/custom_components/tuya_local/config_flow.py", line 35, in async_step_user
return await self.async_step_select_type()
File "/config/custom_components/tuya_local/config_flow.py", line 63, in async_step_select_type
async for type in self.device.async_possible_types():
File "/config/custom_components/tuya_local/device.py", line 94, in async_possible_types
for match in possible_matches(cached_state):
File "/config/custom_components/tuya_local/helpers/device_config.py", line 620, in possible_matches
if parsed.matches(dps):
File "/config/custom_components/tuya_local/helpers/device_config.py", line 89, in matches
if d.id not in dps.keys() or not _typematch(d.type, dps[d.id]):
File "/config/custom_components/tuya_local/helpers/device_config.py", line 23, in _typematch
if isinstance(value, type):
TypeError: isinstance() arg 2 must be a type or tuple of types

    - id: 18
      type: int
      name: unknown_18

The type here should be integer.
Hopefully this helps get it going so you can figure out some more of the values.

    - id: 18
      type: int
      name: unknown_18

The type here should be integer.
Hopefully this helps get it going so you can figure out some more of the values.

If you have access to the Tuya Developer portal (which you may have set up to get your local keys, or to try your device using the default tuya integration), there is an API Explorer, which you can use to get more information about your device.  The most useful is under "Smart Home Management System" / "Device Control" / "Get Device Specification Attribute", which provides a complete listing of all the attributes accessible via the cloud API, including thier local IDs.

@make-all functionality wise i've gotten everything that the tuya api offers, except for schedules. I just didn't have time to sit down and fix this, thanks for the pointer with int/integer. Once I do you can expect a PR. I didn't know you can get local IDs out of the tuya api, I'll take a look into it. I'm going local exactly because the tuya api doesn't offer some functionality on my device (the swing mode), and trips up every integration because tuya specifies c_f be 'c' or 'f' but my device returns true/false

There should be current_temperature readings as well (probably in C and F).  The app also exposes timers, but these can be replaced by automations within Home Assistant, so not really a high priority, I agree.

There should be current_temperature readings as well (probably in C and F).
There are 2, one for C the other for F

@make-all Ok, I've fixed it, this is what I'm now working with, and it almost works:
name: Eberg Cooly C35HD
primary_entity:
  entity: climate
  dps:
    - id: 1
      name: power
      type: boolean
      mapping:
        - dps_val: false
          value: "off"
          icon: "mdi:hvac-off"
          icon_priority: 1
      hidden: true
    - id: 4
      name: unknown_4
      type: integer
    - id: 5
      name: hvac_mode
      type: string
      mapping:
        - dps_val: 3
          icon: "mdi:snowflake"
          icon_priority: 2
          constraint: power
          conditions:
            - dps_val: false
              value_redirect: power
            - dps_val: true
              value: cool
        - dps_val: 4
          icon: "mdi:fan"
          icon_priority: 2
          constraint: power
          conditions:
            - dps_val: false
              value_redirect: power
              value: "off"
            - dps_val: true
              value: fan_only
        - dps_val: 2
          icon: "mdi:water"
          icon_priority: 2
          constraint: power
          conditions:
            - dps_val: false
              value_redirect: power
            - dps_val: true
              value: dry
        - dps_val: 1
          icon: "mdi:fire"
          icon_priority: 2
          constraint: power
          conditions:
            - dps_val: false
              value_redirect: power
            - dps_val: true
              value: heat
    - id: 6
      name: temperature
      type: integer
      mapping:
        - constraint: temperature_unit
          conditions:
            - dps_val: false
              range:
                min: 13
                max: 32
            - dps_val: true
              range:
                min: 55
                max: 90
    - id: 8
      name: fan_mode
      type: string
      mapping:
        - dps_val: 0
          value: "auto"
        - dps_val: 1
          value: "low"
        - dps_val: 2
          value: "medium"
        - dps_val: 3
          value: "high"
    - id: 10
      name: temperature_unit
      type: boolean
      mapping:
        - dps_val: true
          value: "C"
        - dps_val: false
          value: "F"
    - id: 13
      type: integer
      name: unknown_13
    - id: 14
      type: integer
      name: unknown_14
    - id: 15
      type: integer
      name: unknown_15
    - id: 16
      name: swing_mode
      type: boolean
      mapping:
        - dps_val: true
          value: "vertical"
        - dps_val: false
          value: "off"
    - id: 17
      type: boolean
      name: unknown_15
    - id: 18
      type: integer
      name: unknown_18
    - id: 19
      type: boolean
      name: unknown_19

Except the temperature is off. The unit is set to C, it should give me 25 as per tuya-cli. These are my notes as to dpcodes:
1: switch on/off
4: unknown int
5: mode string (1 - heat, 2 - dry, 3 - cool, 4 - fan)
6: temp_c int
8: speed string (0 - auto,1 - low, 2 - medium, 3 - high)
10: c_f boolean (true - celsius)
13: unknown int
14: unknown int
15: unknown int
16: swing (true - vertical) boolean
17: unknown bool
18: temp_f int
19: unknown bool

And this is the output of tuya-cli
{
  devId: '4875044784cca893e465',
  dps: {
    '1': true,
    '4': 0,
    '5': '4',
    '6': 25,
    '8': '1',
    '10': false,
    '13': 0,
    '14': 0,
    '15': 0,
    '16': false,
    '17': false,
    '18': 78,
    '19': false
  }
}

But home assistant gives me -3.9 C

9

PR in #113


Handle FileAlreadyExistsException in ScalaPBGenerator

workaround for https://github.com/bazelbuild/rules_scala/issues/779

@sholokhov can you comment I consent. in this PR please?

I consent.

@iirina could you help us see how to satisfy the CLA bot. @ittaiz and I no longer have that power.

@johnynek given that he already said that, can I close this PR, and open a new one with me as the only author on the code?


fix(connectors): fixes MGDCTRS-754, added query parameter reset_credentials to get addon params to reset client secret

Description
Added query parameter reset_credentials to get addon params to reset client secret
Verification Steps
Integration tests included must pass.
Checklist (Definition of Done)

[X] All acceptance criteria specified in JIRA have been completed
[X] Unit and integration tests added that prove the fix is effective or the feature works (tested against emulated and non-emulated OCM environment)
- [ ] Documentation added for the feature
[ ] CI and all relevant tests are passing
[ ] Code Review completed
- [ ] Verified independently by reviewer
- [ ] Required metrics/dashboards/alerts have been added (or PR created).
- [ ] Required Standard Operating Procedure (SOP) is added.
- [ ] JIRA has created for changes required on the client side

@akoserwal does this look like the correct way to reset client secrets?

@akoserwal does this look like the correct way to reset client secrets?

yes

@lburgazzoli @valdar please approve.


Update adaptors.sql to use tblproperties macro

resolves #
docs dbt-labs/docs.getdbt.com/#

Problem
tblproperties clause macro is not used when creating tables. Add macro to adaptor.sql
Solution
Add macro
Checklist

[ x] I have read the contributing guide and understand what's expected of me
[x ] I have run this code in development and it appears to resolve the stated issue
[ ] This PR includes tests, or tests are not required/relevant for this PR
[ ] This PR has no interface changes (e.g. macros, cli, logs, json artifacts, config files, adapter interface, etc) or this PR has already received feedback and approval from Product or DX

see discussion https://github.com/dbt-labs/dbt-spark/discussions/847

@fleid: Could you merge this PR?

@colin-rogers-dbt  can you review this? :bow:

@JCZuurmond are we doing this one?
Looks like the changelog entry is missing.

@etheleon can you add a changelog entry?

hey @colin-rogers-dbt working on it 👍


Debug Chrome Error

Error :
       ` ChromeProxyService: Failed to evaluate expression 'window': InternalError: No frame with index 36.
      `

flutter doctor -v
[✓] Flutter (Channel stable, 2.10.4, on macOS 12.3 21E230 darwin-x64, locale en-AE)
• Flutter version 2.10.4 at /Users/pselvaraj/Downloads/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision c860cba910 (11 days ago), 2022-03-25 00:23:12 -0500
• Engine revision 57d3bac3dd
• Dart version 2.16.2
• DevTools version 2.9.2
[✗] Android toolchain - develop for Android devices
✗ Unable to locate Android SDK.
Install Android Studio from: https://developer.android.com/studio/index.html
On first launch it will assist you in installing the Android SDK components.
(or visit https://flutter.dev/docs/get-started/install/macos#android-setup for detailed instructions).
If the Android SDK has been installed to a custom location, please use
flutter config --android-sdk to update to that location.
[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
• Xcode at /Applications/Xcode.app/Contents/Developer
• CocoaPods version 1.11.3
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[!] Android Studio (not installed)
• Android Studio not found; download from https://developer.android.com/studio/index.html
(or visit https://flutter.dev/docs/get-started/install/macos#android-setup for detailed instructions).
[✓] VS Code (version 1.65.2)
• VS Code at /Users/pselvaraj/Downloads/Visual Studio Code.app/Contents
• Flutter extension version 3.38.1
[✓] VS Code (version 1.66.0)
• VS Code at /Users/pselvaraj/Downloads/Visual Studio Code 3.app/Contents
• Flutter extension version 3.38.1
[✓] VS Code (version 1.66.0)
• VS Code at /Users/pselvaraj/Downloads/Visual Studio Code 4.app/Contents
• Flutter extension version 3.38.1
[✓] VS Code (version 1.62.1)
• VS Code at /Users/pselvaraj/Downloads/Visual Studio Code 2.app/Contents
• Flutter extension version 3.38.1
[✓] Connected device (1 available)
• Chrome (web) • chrome • web-javascript • Google Chrome 100.0.4896.75
[✓] HTTP Host Availability
• All required HTTP hosts are available
! Doctor found issues in 2 categories.
exit code 0
When I try debug through chrome the chrome doesn't response throws the above error, Cannot debug my app any more.

duplicate of https://github.com/flutter/flutter/issues/101224

Closing this as duplicate of linked issue. Please follow-up in it for further updates.


VS code is blurry if the right most (or second?) monitor is scaled, while the left most (or first?) is not

Does this issue occur when all extensions are disabled?: Yes/No
Yes

VS Code Version:
1.76.0-insider

OS Version:
Ubuntu 20.04 LTS:
$ uname -a Linux HOSTNAME 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Fresh install of code-insiders, running on wayland with following command line:
$ /usr/bin/code-insiders --enable-features=UseOzonePlatform --ozone-platform=wayland
Steps to Reproduce:
When opening vscode it seems that the text is blurry depending on which monitor is scaled. Here are a couple of screenshots to show what I mean, and how to reproduce it:

Left (monitor 1) 100%. Right (monitor 2) 150%:

Here the text is blurry, and it is only vscode that is, the electron wrapper scales fine

Left (monitor 2) 150%. Right (monitor 1) turned off:

Here the text is rendered fine

Left (monitor 2) 150%. Right (monitor 1) 100:

Here it is also fine

I'm getting a similar error. Fractional scaling works fine if I only use the display with fractional scaling, but when I use an additional display without scaling, it's blurry.
I'm on Fedora 37 and using 1.75.1. More specifically:
$ uname -a
Linux fedora.tail8f479.ts.net 6.1.10-200.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Mon Feb  6 23:56:48 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
$ code --version
1.75.1
441438abd1ac652551dbe4d408dfcec8a499b8bf
x64

This is how I'm trying to run code:
$ code --enable-features=UseOzonePlatform --ozone-platform=wayland
Warning: 'enable-features' is not in the list of known options, but still passed to Electron/Chromium.
Warning: 'ozone-platform' is not in the list of known options, but still passed to Electron/Chromium.

I get the same warnings in all cases, even though fractional scaling works when (and only when) I only use the one display with fractional scaling.
If I just run code without the wayland flags, then it is blurry in all cases.

I'm getting a similar error. Fractional scaling works fine if I only use the display with fractional scaling, but when I use an additional display without scaling, it's blurry. The arrangement of the displays does not appear to matter.
I'm on Fedora 37 and using code 1.75.1. More specifically:
$ code --version
1.75.1
441438abd1ac652551dbe4d408dfcec8a499b8bf
x64

This is how I'm trying to run code:
$ code --enable-features=UseOzonePlatform --ozone-platform=wayland
Warning: 'enable-features' is not in the list of known options, but still passed to Electron/Chromium.
Warning: 'ozone-platform' is not in the list of known options, but still passed to Electron/Chromium.

I get the same warnings in all cases, even though fractional scaling works when (and only when) I only use the one display with fractional scaling.
If I just run code without the wayland flags, then it is blurry in all cases.

I think this is related with https://github.com/microsoft/vscode/issues/161231. Which was linked with something unrelated and closed down.
Regardless of arrangement if not all displays are scaled vscode starts blurry and you can fix it by running "Developer: Reload window".

You're right, same issue for me. Reloading the window it fixes the blurriness. Thank you!

I have the same issue, but reloading the window does not fix it.

looks like this is back: https://github.com/microsoft/vscode/issues/174876
I can reproduce this on both current insiders and current stable:
Version: 1.83.0-insider
Commit: 5a400e53e985dc5e24f6ee574b07ab23943841c5
Date: 2023-09-07T17:35:22.926Z
Electron: 25.8.0
ElectronBuildId: 23503258
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 6.0.19-060019-generic

scaling 175%, single display:

scaling 175%, second display connected with 100%:

curiously enough, using x11 instead of wayland, the result is fuzzier in full-res, but much nicer visually on the high density display

Thanks for the update @matejcik, it seems to have regressed with Chromium 114 that enables fractional scaling experiment by default on wayland. Issue is tracked in https://github.com/microsoft/vscode/issues/192590, I will merge this to it.


osd: fix monitor_name error when scaling out OSDs (bp #5261)

This is a manual backport of pull request #5261 done by Mergify

Mergify commands and options

More conditions and actions can be found in the documentation.
You can also trigger Mergify actions by commenting on this pull request:

@Mergifyio refresh will re-evaluate the rules
@Mergifyio rebase will rebase this PR
@Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

look at your merge queues
generate the Mergify configuration with the simulator.

Finally, you can contact us on https://mergify.io/

jenkins test centos-non_container-add_osds

jenkins test centos-container-add_osds

jenkins test centos-container-all_daemons

jenkins test centos-container-purge

jenkins test centos-container-all_daemons


Update README.md

Fixes #.
Fixed the documentation README.md file with proper changes
Description of the changes:
Changed the grammatical errors.
Changed the date to data.
How changes were validated:

Specify how you tested your changes (i.e. manual/ad-hoc testing, automated testing, new automated tests added)-->

I tested my changes by using an advanced automated spell checker.

 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.You have signed the CLA already but the status is still pending? Let us recheck it.


Core: Revert changing logback scope from "compile" to "runtime"

This changed introduced in #3340 causes logback to not be shipped in the bundle.
We've wasted enough time trying to find a proper sbt configuration, let's revert.

closed by 7f4db686d0e3f37d622302861a3109cf59d4b2e3


WARN  [mavlink] ignoring CMD with same SYS/COMP (1/1) ID

PX4 v1.5 (stable) produces following messages in infinite loop:
WARN  [mavlink] ignoring CMD with same SYS/COMP (1/1) ID
WARN  [mavlink] ignoring CMD with same SYS/COMP (1/1) ID
WARN  [mavlink] ignoring CMD with same SYS/COMP (1/1) ID
WARN  [mavlink] ignoring CMD with same SYS/COMP (1/1) ID
WARN  [mavlink] ignoring CMD with same SYS/COMP (1/1) ID
WARN  [mavlink] ignoring CMD with same SYS/COMP (1/1) ID

main.conf:
[General]
TcpServerPort=0
ReportStats=false
MavlinkDialect=ardupilotmega

[UartEndpoint px4]
Device = /dev/ttyS1
Baud = 921600

[UdpEndpoint wifibroadcast]
Mode = Normal
Address = <IP_ADDRESS>
Port = 14550

[UdpEndpoint qgc]
Mode = Normal
Address = <IP_ADDRESS>
Port = 14550

What HW are you working on? Is this on mavlink-router from master branch?  My first suspect would be the logging system with wrong sysid/compid, but you don't have that enabled.... So, what do you have running on the wifibroadcast endpoint?

This is some message that PX4 send periodically with the wrong target system id.
Like this one: https://github.com/PX4/Firmware/pull/6896/commits/519ca279342d173c41b1eac6b057de06cc772476

HW is a odroid-c0, connected to pixhawk as companion at 921600 bps. mavlink-router
was built from master branch, px4 is latest stable (not master). Wifibroadcast is a unidirectional transport - it only receives mavlink packets, but never send data back (https://github.com/svpcom/wifibroadcast)

@svpcom this seems to be a problem in PX4 not mavlink-router as @zehortigoza said.  The only message we send ourselves to the flight stack is to start the log streaming (if you have that enabled on the configuration file).
Btw, nice to see wifibroadcast alive again. I hope to be able to test it later.


Update indent code style and remove unused styles

@vsn4ik Can you update the PR that you don't change the indentation? This will break every PR that is still open, but i'm planning to change the indents when moving to 2.0!
Just keep the removal of the unused styles here and generate the dist files and screenshots to verify that nothing breaks!
Thanks!

PR updated, Phantomjs font looks different on Linux.

Yeah I see that the font has changed, maybe you can just revert the changes on the screenshots and dist files. I will checkout this branch and try it locally (I guess my fotns are ok) and when this PR is merged I will generate the dist files and screenshots again (if needed)

PR updated.

Thanks @vsn4ik! I will try this branch later today. Then the PR should be good to merge!

Tested the branch, every looks good! Thanks @vsn4ik!


KDE Plasma's Create a New Activity displays a black screen

Describe the bug
In Plasma5, when you open activity settings dialog, you get a black screen.
If I hover around, I'm able to see mouse pointer changing to text cursor somewhere in there. From there, I was able to figure out the first setting -- Give it a name. No idea about the rest. This is a bug and shouldn't be happening.
Steps To Reproduce
Steps to reproduce the behavior:

Meta + Q to bring up activities.
Click Create activity...
See your activity settings dialog.

Expected behavior
This activity settings dialog should not be a black screen.
Screenshots

Additional context
Add any other context about the problem here.
Notify maintainers

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
❯ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.15.94, NixOS, 23.05 (Stoat), 23.05pre456790.988cc958c57`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.13.2`
 - channels(root): `"nixos"`
 - channels(chris): `"home-manager"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Nothing big changed. It showed okay later. Must be graphic/theme related issue.


Error with Quora plugin

Error: Elements matching selector ".MoreNavItem.SidebarNavItem.SiteHeaderNavItem.HoverMenu svg" were not loaded ater 10000 milliseconds.
at checkSelector (file:///Users/shawnmurphy/Library/Application%20Support/Google/Chrome/Default/Extensions/hlkhpekhgcaigleojiocoeockhcaglia/0.5.7_0/src/plugin.js:137:27)

(Closing in favor of #130)


occurrences highlight stuck the selection word

Type: Bug
I don’t know how to describe this problem. It seems that I pressed a certain key combination (unreasonable) that caused some problems with occurrences highlight.
It's a bit blurry, but if you look closely you'll notice that when I select an empty line, the highlight is still there:

I Split the Editor. If the editor edits the same source file at the same time, the highlight will be stuck in another editor.
But if two editors are not editing the same source file at the same time, this problem will not occur.
It seem that is vscode feature but idk.
Tried:
editor.occurrencesHighlight = false (work, but i needed it)
editor.selectionHighlight = false
Editor: Multi Document Occurrences Highlight = false and true (both have this buggly)
and i tried to restart the vscode and restart the pc, and nothing.
VS Code version: Code 1.84.2 (1a5daa3a0231a0fbba4f14db7ec463cf99d7768e, 2023-11-09T10:51:52.184Z)
OS version: Windows_NT x64 10.0.22635
Modes:

System Info

Item
Value

CPUs
AMD Ryzen 5 5600G with Radeon Graphics          (12 x 3893)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
15.29GB (7.70GB free)

Process Argv
--crash-reporter-id 95d4c8d0-afc5-4da2-960b-1cd90fa6a90f

Screen Reader
no

VM
0%

Extensions (12)

Extension
Author (truncated)
Version

doxdocgen
csc
1.4.0

vscode-eslint
dba
2.4.2

code-runner
for
0.12.1

vscode-language-pack-zh-hans
MS-
1.84.2023111509

remote-containers
ms-
0.321.0

remote-ssh
ms-
0.107.0

remote-ssh-edit
ms-
0.86.0

remote-wsl
ms-
0.81.8

cmake-tools
ms-
1.16.31

cpptools-extension-pack
ms-
1.3.0

cmake
twx
0.0.17

vscode-lldb
vad
1.10.0

(1 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30410667
py29gd2263:30880072
vscaac:30438847
vsclangdc:30486549
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30695312
azure-dev_surveyone:30548225
2e4cg342:30602488
89544117:30613380
showlangstatbar:30737416
pythonfmttext:30731395
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
pythonnosmt12:30797651
pythonidxpt:30866567
pythonnoceb:30805159
synctok:30869157
dsvsc013:30795093
dsvsc014:30804076
dsvsc015:30845448
pythontestfixtcf:30871695
pythonregdiag2:30871582
pyreplss1:30886140
pythonmypyd1:30879173
pythoncet0:30885854
pythontbext0:30879054
dsvsc016:30886110
dsvsc017cf:30886113
dsvsc018:30886114
aa_t_chat:30882232

problem still haven't fix

2 quick follow up questions, what is the value of your editor.occurrenceHighlight enum setting? And second, does this only repro when in a split view of the same file, or does this repro when split viewing different files as well?

Default. i do not touch it.

same file

Thank you for the responses! Will be looking into this.

Closing this as a dupe in favor of #198866


Setting random seed

Hi --
I'm trying to set this up so that it gets the exact same results every time (eg, for regression tests).  Even when I set the seeds, I get (slightly) different results on each run.  Any ideas what might be going on there?
Thanks

Hi!
cudnn convolutions are not deterministic. This is one of possible sources of stochasticity. Let me know if it's still non deterministic with other implementations of convolutions.

Ah good point -- let me test that and get back to you.
On Mon, Nov 13, 2017 at 6:45 PM Ilya Kostrikov<EMAIL_ADDRESS>wrote:

Hi!
cudnn convolutions are not deterministic. This is one of possible sources
of stochasticity. Let me know if it's still non deterministic with other
implementations of convolutions.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ikostrikov/pytorch-a2c-ppo-acktr/issues/22#issuecomment-344097377,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFzgfRkWRygvPx9hPGwGke44v8DYccmOks5s2NSxgaJpZM4QclnR
.

Doesn't look like that's the source of the nondeterminism.  If I build the pytorch from github and set the flag:
torch.backends.cudnn.deterministic = True

I still see the nondeterminism.  Same goes for if I set
torch.backends.cudnn.enabled = False

If I run w/ --no-cuda option, then the results appear to be deterministic.

Actually, this is interesting even without the context of RL.
Let's not close it yet, probably it makes sense to open an issue in the pytorch repo.

Yeah it's a little funny -- I don't totally believe I haven't made a mistake.  When I get a chance I'll put together something self-contained and open a pytorch issue if it persists.

@bkj Hi, is it possible that in your testing code you haven't set "deterministic=True"? (as in model.py):

def.act(self, inputs, states, masks, deterministic=False):

(For posterity -- this bug was happening before pytorch added the torch.backends.cudnn.deterministic flag -- so it should be fixed now.)

Thanks! I will add a deterministic option to the code today.


Fix cuda compiler path problem in opencv

I met similar problem with #2749 and this patch can fix the problem. Besides, another problem could happen like this issue stated. Switch to toolset v140 can prevent this. However, this is a problem related to CUDA, so it's not fixed here.

This is fixed in CMake 3.11 FYI...

That would be great.

Fixed at #2906


Lambda function is not reusable for OpenApiGatewayToLambda

when I try to reuse a lambda function in OpenApiGatewayToLambda constructor via existingLambdaObj, I get an error relating to https://github.com/awslabs/aws-solutions-constructs/blob/9315c9324cb902a50b852a4d61dbb17f8573e2a7/source/patterns/%40aws-solutions-constructs/aws-openapigateway-lambda/lib/index.ts#L215
as this permission is added for every lambda but cdk would create it over and over again with the same name and it has an expectation of it to be unique.

Just to clarify as we dive deeper - you are sharing a Lambda function between 2 openapigateway-lambda constructs?

We've  implemented the fix for this, it should be published to the various repositories this evening.

thank you.

v2.71.0 includes this fix


Download with extra sets of headers

In the buildLabel.sh script, I had to add extra download options using different sets of headers in order for the server to return the file.
Then came some “mocha”-labels, and a new set of headers had to be found for those. And to even download from the server once the URL was given, the server needed these headers. So Installomator needs to be able to try these same sets of headers for the download, so we can get it to work.
Maybe we can figure out in the fuse to somehow determine automatically which headers are needed for a certain server, but until then, my method is to download from a browser (Safari or Brave), and then inspect what headers it used for the download.
The 3 sets of headers has been added to both scripts now, in the same order, and as clear as can be done, so the differences is more obvious.

Instead of trying repeatedly with different sets of headers, I think we should define custom curl options in the label and then use those in the download:
in the label:
curlOptions="-H \"User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.1 Safari/605.1.15\" \
-H \"accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9\" \
-H \"accept-encoding: gzip, deflate, br\" \
-H \"accept-language: en-US,en;q=0.9\" \
-H \"sec-fetch-dest: document\" \
-H \"sec-fetch-mode: navigate\" \
-H \"sec-fetch-user: ?1\" \
-H \"sec-gpc: 1\" \
-H \"upgrade-insecure-requests: 1\" "

and then where the actual download happens:
curl -fsL ${=curlOptions} "$downloadURL" -o "$archiveName"

Thanks, I think this is much better approach, too.
I do however get an error when downloading, but the quoting seems a little "wild".
Suggestions to how to fix this?

took me a while to figure that out, too. Turns out, the easiest way is to define curlOptions as an array:
curlOptions=( -H "User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.1 Safari/605.1.15"
-H "accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9"
-H "accept-encoding: gzip, deflate, br"
-H "accept-language: en-US,en;q=0.9"
-H "sec-fetch-dest: document"
-H "sec-fetch-mode: navigate"
-H "sec-fetch-user: ?1"
-H "sec-gpc: 1"
-H "upgrade-insecure-requests: 1" )

curl -fsL ${curlOptions} "$downloadURL" -o "$archiveName"

sorry for the confusion

But that is even more beautiful in the label, and it works great!

checkLabels.sh should be updated as well. Hopefully done later tonight.

This was my most recent run of buildLabel.sh for mochatn3270:
./utils/buildLabel.sh https://mochasoft.dk/tn3270.dmg.zip
Changing directory to /Users/installomator/Documents/git/Installomator/2022-01-19-17-04-48
Working dir: /Users/installomator/Documents/git/Installomator/2022-01-19-17-04-48
Downloading https://mochasoft.dk/tn3270.dmg.zip
tn3270.dmg.zip
Redirecting to (maybe this can help us with version):
HTTP/2 400
content-length: 339
content-type: text/html; charset=us-ascii
server: Microsoft-HTTPAPI/2.0
date: Wed, 19 Jan 2022 22:04:49 GMT

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0  1346    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (22) The requested URL returned error: 406
error downloading https://mochasoft.dk/tn3270.dmg.zip with no headers.
result: tn3270.dmg.zip
https://mochasoft.dk/tn3270.dmg.zip
Trying 1st set of extra headers to download.
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 5934k  100 5934k    0     0  2276k      0  0:00:02  0:00:02 --:--:-- 2279k
archiveTempName: tn3270.dmg.zip
archivePath: https://mochasoft.dk/tn3270.dmg.zip
Calculated archiveName: tn3270.dmg.zip
name: tn3270.dmg
archiveExt: zip
Compressed file found
Disk image found: /Users/installomator/Documents/git/Installomator/2022-01-19-17-04-48/tn3270.dmg
archiveExt: dmgInZip
DMG investigation.
Mounting /Users/installomator/Documents/git/Installomator/2022-01-19-17-04-48/tn3270.dmg
Mounted: /Volumes/Mocha TN3270 for macOS
App found: /Volumes/Mocha TN3270 for macOS/TN3270.app
Application investigation.
Team ID found for app: RR9F5EPNVW
"disk4" ejected.
identifier: tn3270

**********

Labels should be named in small caps, numbers 0-9, “-”, and “_”. No other characters allowed.

appNewVersion is often difficult to find. Can sometimes be found in the filename, sometimes as part of the download redirects, but also on a web page. See redirect and archivePath above if link contains information about this. That is a good place to start

tn3270)
    name="TN3270"
    type="appInDmgInZip"
    downloadURL="https://mochasoft.dk/tn3270.dmg.zip"
    appNewVersion=""
    expectedTeamID="RR9F5EPNVW"
    ;;

Above should be saved in a file with exact same name as label, and given extension “.sh”.
Put this file in folder “fragments/labels”.

Output running ./assemble.sh mochatn3270 DEBUG=1:
./assemble.sh mochatn3270 DEBUG=1
2022-01-19 17:08:05 mochatn3270 setting variable from argument DEBUG=1
2022-01-19 17:08:05 mochatn3270 ################## Start Installomator v. 9.0dev
2022-01-19 17:08:05 mochatn3270 ################## mochatn3270
2022-01-19 17:08:05 mochatn3270 DEBUG mode 1 enabled.
2022-01-19 17:08:05 mochatn3270 BLOCKING_PROCESS_ACTION=tell_user
2022-01-19 17:08:05 mochatn3270 NOTIFY=success
2022-01-19 17:08:05 mochatn3270 LOGO=/System/Applications/App Store.app/Contents/Resources/AppIcon.icns
2022-01-19 17:08:05 mochatn3270 no blocking processes defined, using TN3270 as default
2022-01-19 17:08:05 mochatn3270 Changing directory to /Users/installomator/Documents/git/Installomator/build
2022-01-19 17:08:05 mochatn3270 App(s) found:
2022-01-19 17:08:05 mochatn3270 could not find TN3270.app
2022-01-19 17:08:05 mochatn3270 appversion:
2022-01-19 17:08:05 mochatn3270 Latest version not specified.
2022-01-19 17:08:05 mochatn3270 Downloading https://mochasoft.dk/tn3270.dmg.zip to TN3270.zip
2022-01-19 17:08:07 mochatn3270 DEBUG mode 1, not checking for blocking processes
2022-01-19 17:08:07 mochatn3270 Installing TN3270
2022-01-19 17:08:07 mochatn3270 Unzipping TN3270.zip
2022-01-19 17:08:07 mochatn3270 found dmg: /Users/installomator/Documents/git/Installomator/build/tn3270.dmg
2022-01-19 17:08:07 mochatn3270 Mounting /Users/installomator/Documents/git/Installomator/build/tn3270.dmg
2022-01-19 17:08:07 mochatn3270 Mounted: /Volumes/Mocha TN3270 for macOS
2022-01-19 17:08:07 mochatn3270 Verifying: /Volumes/Mocha TN3270 for macOS/TN3270.app
2022-01-19 17:08:08 mochatn3270 Team ID matching: RR9F5EPNVW (expected: RR9F5EPNVW )
2022-01-19 17:08:08 mochatn3270 Downloaded version of TN3270 is 2.6.1 (replacing version ).
2022-01-19 17:08:08 mochatn3270 App has LSMinimumSystemVersion: 10.9
2022-01-19 17:08:08 mochatn3270 DEBUG mode 1 enabled, skipping remove, copy and chown steps
2022-01-19 17:08:08 mochatn3270 Finishing...
2022-01-19 17:08:18 mochatn3270 App(s) found:
2022-01-19 17:08:18 mochatn3270 could not find TN3270.app
2022-01-19 17:08:18 mochatn3270 Installed TN3270
2022-01-19 17:08:18 mochatn3270 notifying
2022-01-19 17:08:18 mochatn3270 Unmounting /Volumes/Mocha TN3270 for macOS
"disk4" ejected.
2022-01-19 17:08:19 mochatn3270 DEBUG mode 1, not reopening anything
2022-01-19 17:08:19 mochatn3270 ################## End Installomator, exit code 0

Thanks for your work on this!


Mocha test stops without further execution of other test cases if an expect fails in a test case.

describe('API testing: meeting', function () {
it('Testing meeting update view count call without error', function (done) {
request(app).post('/meeting/updateViewCount').send({ videoId: 17 }).set('Accept', 'application/json').expect(200).end(function (err, res) {
should.not.exist(err);
should.exist(res.body);
expect(res.body.status).to.equal('Success'); // This fails
done();
});
});-- In above test case I am passing invalid videoId as 17 , no record exists with this id and it will fail and mocha throws below error and exit.
throw err;
^
AssertionError: expected 'Error' to equal 'Success'
But I want it to continue further executing below test and also many other in different files and show the result of passed and failed with proper execution.
it('Testing meeting update view count call with error', function (done) {
    request(app).post('/meeting/updateViewCount').send({ videoId: 's' }).set('Accept', 'application/json').expect(200).end(function (err, res) {
        expect(res.body.status).to.equal('Error');
        done();
    });
});

});
Is this an issue or am i missing something here, I am new to mocha tests, earlier i worked on java and grails testing frameworks where i never faced any such issues.
Thanks
Sandeep

Mocha does normally run all tests and report multiple passes and failures; if it's not doing so that's a bug of some sort. However, it's also possible that what's actually happening is some other issue... What's the full output you get if you run just that file (node_modules/.bin/mocha path/to/specific/test.js)?
P.S. You can surround your code blocks with ``` to get cleaner formatting (and optionally include a language to get syntax highlighting), e.g.:
```javascript
your(
  code()
    .here
  )
```

...becomes...
your(
  code()
    .here
  )

@ScottFreeCode , I have run the single test file with 3 testcases , but still am facing the same issue.
Below is the output of single file execution, first test case passed and second failed due to expected error and 3rd did not run at all mocha exited with exception of 2nd and without running 3rd test.
API testing: meeting synopsis
✓ Testing meeting synopsis list call (4554ms)
/Users/svedavya/Documents//package/repo/node_modules/temp-fs/index.js:32
throw err;
^
AssertionError: expected 'Error' to equal 'Success'
at Test. (/Users/svedavya/package/repo/test/api/MeetingSynopsisTests.js:53:40)
at Test.assert (/Users/svedavya/Documents/package/repo/node_modules/supertest/lib/test.js:179:6)
at Server.assert (/Users/svedavya/Documents/package/repo/node_modules/supertest/lib/test.js:131:12)
at Object.onceWrapper (events.js:293:19)
at emitNone (events.js:86:13)
at Server.emit (events.js:188:7)
at emitCloseNT (net.js:1568:8)
at /Users/svedavya/Documents/package/repo/node_modules/async-listener/glue.js:188:31
at _combinedTickCallback (internal/process/next_tick.js:77:11)
at process._tickDomainCallback (internal/process/next_tick.js:128:9)
at process.fallback (/Users/svedavya/Documents/package/repo/node_modules/async-listener/index.js:529:15)

That is definitely odd: it doesn't even look like a test failure reported by Mocha, looks more like an exception killing the Node process as a whole. But that shouldn't happen, since Mocha is supposed to (and normally does) catch any exceptions that occur during testing (and report them to the current asynchronous test if it is currently waiting for an asynchronous test to complete). (Not that that adds much over my initial thought that this is indeed a problem that shouldn't occur, but it's more specific at least...)
Hmm... three test cases in the file -- any chance I could look at the whole file, with some idea of what the dependencies are doing? Better yet (although I hope it won't be needed, it's hard to tell at this point -- nothing jumps out at me as obviously wrong with the code you've shown so far) -- if you feel like making it easier for me and getting some experience digging into the issue yourself, a complete example (but more minimal than the project as a whole, if possible) that I could copy-paste and run myself to play with and debug would be really helpful.

I have found the issue and solved it myself, it was the supertest plugin which was causing the issue when assert fails , it was not propagating the exception to next level instead it was exiting the node thread. I had used chai-http with proper exception mechanism and issue resolved.

Interesting -- I've used Supertest before and didn't run into this... Is there a link to an issue on the Supertest repo we could put here for reference?
Glad you were able to track it down in, any case!

I have this exact same issue. Is there no way to use Supertest? Using chai-http is not an easy solution, we have way too many mocha test cases to change at this point!

I have found the issue and solved it myself, it was the supertest plugin which was causing the issue when assert fails , it was not propagating the exception to next level instead it was exiting the node thread. I had used chai-http with proper exception mechanism and issue resolved.

I am using grunt + mocha and run into similar issue.
Perhaps an easier solution is to set mocha option --bail, -b
This will allow mocha to continue further tests when previous test fails.
But inside the test, it will stop after encountering the failing assertions.
describe("Title", () => {
  describe('#Tag', () => {
    it('Test1', () => {
      assert(false);
      // this line will NOT be execute
    }

    it('Test2', () => {
      // this line will be execute
      assert(true);
    }
  }
}

@sandeepvedavyas, Can you please tell us how did you solve the issue with chai-http as I'm also facing the same issue?

I also have a similar kind of situation, my tests are getting failed on the first occurrence.
Mocha: 8.1.3
Supertest: 3.3.0
chai: 3.5.0
My observation is that when I use expect in order to do the assertion if assertions get failed then only I am getting this kind of issue, in a few of the cases where we have used should for the assertions those suites are not getting interrupted.
Also, the --bail option is also not working out for me :(.
thanks


Add support for dnsmasq

What do you guys think about adding support for dnsmasq in separate recipe? I can submit a pull request.

I don't think this is an enhancement on our end. Its something you would provide in an environment or wrapper cookbook.


Doc cleanup for logentry template

Proposing changes suggested in external review.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: jkohen
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: costinm
If they are not already assigned, you can assign the PR to them by writing /assign @costinm in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Hi @jkohen. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@jkohen: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests.sh
ba213935435c5ebfb148ea5bd85b303af29b3be3
link
/test e2e-simpleTests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jkohen: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests.sh
ba213935435c5ebfb148ea5bd85b303af29b3be3
link
/test e2e-simpleTests

prow/istio-integ-k8s-tests.sh
ba213935435c5ebfb148ea5bd85b303af29b3be3
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jkohen: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
ba213935435c5ebfb148ea5bd85b303af29b3be3
link
/test istio-integ-k8s-tests

prow/e2e-simpleTests-cni.sh
ba213935435c5ebfb148ea5bd85b303af29b3be3
link
/test e2e-simpleTests-cni

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jkohen: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
ba213935435c5ebfb148ea5bd85b303af29b3be3
link
/test istio-integ-k8s-tests

prow/e2e-simpleTests-cni.sh
ba213935435c5ebfb148ea5bd85b303af29b3be3
link
/test e2e-simpleTests-cni

prow/istio-pilot-multicluster-e2e.sh
ba213935435c5ebfb148ea5bd85b303af29b3be3
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

As discussed with Doug, I'm going to drop this change in favor of a Stackdriver-specific template.


[disabled] not changed for

My html
<md-tab label="Body" [disabled]="disableBodyTab">           <textarea></textarea>  </md-tab>
ts file:
checkMethod() {
this.disableBodyTab = this.requestForm.get('method').value === 'get';
}
After checkMethod triggered, the value for disableBodyTab  changed to false, but it's still disabled.
If I change the html to:
<md-tab label="Body{{disableBodyTab}}" [disabled]="disableBodyTab">           <textarea></textarea>  </md-tab>
It works. Is it a bug?

Can you provide a reproduction in either stackblitz or plunker?
The tab should disable as you say, however we need a reproduction to investigate.


subsys: random: Fix semaphore initial count of xoroshiro128

Fix semaphore initial count of rand32_xoroshiro128
Signed-off-by: Ramakrishna Pallala<EMAIL_ADDRESS>

in this driver, originally the semaphore initial count is set to 0 but k_sem_give() is invoked first and the caller will be blocked forever.
please check sys_rand32_get() in subsys/random/rand32_xoroshiro128.c

in this driver, originally the semaphore initial count is set to 0 but k_sem_give() is invoked first and the caller will be blocked forever.
please check sys_rand32_get() in subsys/random/rand32_xoroshiro128.c

can you add this to the commit message


Issue listening for playBytes topic

I am trying to move audio playing from Rhasspy to my own intent handling app built using rhasspy-hermes-app. I figured the example here would be a great place to start.
Unfortunately, I can't even get that example app to function properly. When I run it and speak the wake word, I get the following output:
/home/pi/.local/lib/python3.7/site-packages/rhasspyhermes_app/__init__.py:259: RuntimeWarning: coroutine 'HermesApp.on_topic.<locals>.wrapper.<locals>.wrapped' was never awaited
  function_2(data, payload)
RuntimeWarning: Enable tracemalloc to get the object allocation traceback

I'm pretty new to Python so this is a bit challenging for me to debug. If someone could point me in the right direction that would be highly appreciated.

It seems you have hit this bug:
https://github.com/rhasspy/rhasspy-hermes-app/pull/89/files
It's already fixed by the above PR, but not yet released. For now you could do the one-line fix in your local copy of rhasspy-hermes-app by editing /home/pi/.local/lib/python3.7/site-packages/rhasspyhermes_app/__init__.py.

Actually I think I might have found a bug?
When I dive into HermesApp::on_raw_message (line 259) and add an await statement before the function call, the error goes away and the example works again.

Gotcha, I found the same you mentioned I think. Thanks for the info!

Release 1.1.2 with the fix has been published now: https://github.com/rhasspy/rhasspy-hermes-app/releases/tag/v1.1.2


Replace animations shown in Jupyter Notebooks by matplotlib animations

ATM we use imageio to produce videos from frames. This is causing some issues in notebooks, like poorly rendered movies...
I came across matplotlib animations, which allow a movie to be created out of a sequence of frames built with simple functions and have handy methods such as to_html5_video and to_jshtml. These seem to render nicely in Google Colab, and to_jshtml even has built-in play/pause/forward/etc buttons to control the video play.
See this example Google Colab.
WDYT?

This issue seems to be out of place with our current paradigm. Gonna close it as not planned, add it to a visualisations document and eventually we can open it up if we decide to follow on this.


Fix issues with moduleResolution NodeNext

Fixes #15

I was able to reproduce this type error, it's happened when I'm importing icons with named export.

Sorry for not fixing this myself. Completely forgot about it. 😅
Will this be included in a release soon? It's quite essential for projects where this issue occured.


Does this project support other models of whisper base tiny

I want to run whisper on my low hash rate terminal device and speed it up, but does the project only speed up for the large model

Changue this code line:
from faster_whisper import WhisperModel
model_size = "large-v2"

to
from faster_whisper import WhisperModel
model_size = "tiny"


tt_SiliconDriver support multiple cards

Related to redesign https://docs.google.com/drawings/d/1-m1azdsBqMA0A6ATYRMfkhyeuOJuGCEI62N5a96LXj0/edit
Following are the blockers to allow trivial transition in tt-metal from using several tt_SiliconDevice to using a single one to manage the whole cluster (tt_SiliconDevice will be renamed to tt::umd::Cluster). I tried doing the rewrite and have stumbled upon a couple of API issues:

wait_for_non_mmio_flush doesn't accept chip_id
assert_risc_reset -> there should be a variant accepting chip_id. Also not sure if the current variant works for more than one mmio chip.

This includes broadcast_tensix_risc_reset_to_cluster, broadcast_write_to_cluster and ethernet_broadcast_write

start_device -> check if it works for multiple mmio chips
devices_grouped_by_assoc_mmio_device_ -> add support in tt_ClusterDescriptor
nice to have: check for a chip if it is a remote chip: https://github.com/tenstorrent/tt-metal/blob/main/tt_metal/llrt/tt_cluster.cpp#L458

5 is already present with is_chip_mmio_capable

Probably related to 4, get_closest_mmio_chip seems to assume a single connected cluster of chips

Related to 4: We don't support multiple cluster of cards currently, marked explicit by #165 .
However, tt_metal still needs this map which it builds itself. I've added the support directly to tt_clusterDesc in #167
1 will be fixed by #166


[integration] Infracost

Tool / Product Name
Infracost
Goal
I want to trigger infracost to check cloud costs from a Keptn sequence

#help-integrations on Slack

[X] Yes

No Existing Integrations

[X] Yes

Assisted
No
Any other info?
https://github.com/keptn-contrib/artifacthub/pull/147

I have this working. Demo repo here: https://github.com/agardnerIT/keptninfracost2
The current version is running a custom Python container which has Python + requests module + prometheus python client installed.

Run Infracost using their API
Define the fields I care about and want to push to Prometheus (this would work with any metrics backend or observability platform)
Add labels and push metrics to Prometheus

@bradmccoydev will be demoing this on the Infracost call today. @alikajeh1 FYI

https://www.youtube.com/watch?v=L8AWjCAHv-4

This is now done, listed on Keptn.sh and have been announced to the Infracost community. closing.


Complete the undoing of PR #99

This commit brings the head of main back to the state that it was at commit 742a9d2d, which is the merge of PR#101.   It completes the undo of #99 that was only partially fixed by PR #103 .   After merging this PR, the head should diff cleanly against commit 742a9d2d .
It took 2 mistakes to get here.  PR #99 was  dummy for testing.  The first mistake was that it started from branch Mu2eII_SM21 but I asked to merge it into main.  The second mistake was to merge it, not close it.
In addition to the intended dummy change to README.md PR #99 inadvertently included changes to 3 files:
JobConfig/beam/prolog.fcl
JobConfig/cosmic/geom_cosmic.txt
JobConfig/cosmic/geom_cosmic_current.txt

:sunny: The tests passed at b754c870ac5a07b4acdf3f8a21260a63ced158f7.

Test
Result
Details

merge
:white_check_mark:
Merged b754c870ac5a07b4acdf3f8a21260a63ced158f7 at 04e3b28462400e7a088f7cf618a173c89366ba90

build (prof)
:white_check_mark:
Log file. Build time: 14 min 56 sec

ceSimReco
:white_check_mark:
Log file.

g4test_03MT
:white_check_mark:
Log file.

transportOnly
:white_check_mark:
Log file.

POT
:white_check_mark:
Log file.

g4study
:white_check_mark:
Log file.

cosmicSimReco
:white_check_mark:
Log file.

cosmicOffSpill
:white_check_mark:
Log file.

ceSteps
:white_check_mark:
Log file.

ceDigi
:white_check_mark:
Log file.

muDauSteps
:white_check_mark:
Log file.

ceMix
:white_check_mark:
Log file.

rootOverlaps
:white_check_mark:
Log file.

g4surfaceCheck
:white_check_mark:
Log file.

FIXME, TODO
:white_check_mark:
TODO (0) FIXME (0) in 0 files

clang-tidy
:white_check_mark:
0 errors 0 warnings

N.B. These results were obtained from a build of this Pull Request at b754c870ac5a07b4acdf3f8a21260a63ced158f7 after being merged into the base branch at 04e3b28462400e7a088f7cf618a173c89366ba90.
For more information, please check the job page here.
Build artifacts are deleted after 5 days. If this is not desired, select Keep this build forever on the job page.

I ran jobs 0, 1, of the nightly POT set.  I used val.fcl and valCompare to compare the output of these jobs with the output of the 3 corresponding jobs from early morning yesterday (Wed Sept 29).  All 307 histograms were an exact match.


TICKScript woes - Adding two fields

I'm not really sure where to start with this one, but I have tried on both the community site and the Gophers Slack channel.
I'm having some serious issues with a TICKScript that I'm sure worked for a period and now will not - And it's the simplest script ever.
// Measurement selection
var db = 'telegraf'

var rp = 'autogen'
var measurement = 'winperf_hypervhealth'
var groupBy = ['host']
var whereFilter = lambda: TRUE

// Get a window of data
var data = stream
    |from()
        .database(db)
        .retentionPolicy(rp)
        .measurement(measurement)
        .groupBy(groupBy)
        .where(whereFilter)
    // Keep only one field
    |eval(lambda: "Health_OK" + "Health_Critical")
        .as('Total_VMs')
        .keep()
    |influxDBOut()
        .database(db)
        .retentionPolicy(rp)
        .measurement(measurement)
        .tag('kapacitor', 'true')

I literally only need to sum two fields, but as the info says in the community forum post, I either get data from a single node, or not at all. If I change the influxDBOut() to an alert() node with .log(), I see all 3 fields have values.
Nothing in the logs that I can see, and I have other TICKScripts running and writing to InfluxDB with no issues.
Any ideas?

I believe this may be due to mismatched timestamps in the two fields. Eval expects them to have the same timestamp. Check out this guide and this guide as they solve this using a batch stream or a window() node with an .align() property.

Hi it's fixed; I have same pb.
thanks !


Disable test_shark_model_suite while it is failing.

Follow-up to https://github.com/iree-org/iree/pull/10576 (see https://github.com/nod-ai/SHARK/issues/373).
This PR should be reverted once the job succeeds again.

fyi @mariecwhite , @dan-garvey


Support multiple formats in the outbound postoffice

Is your feature request related to a problem? Please describe.

We need to be able to support multiple outbound formats. EBIX, CIM and so on.
To do that we will expand the post office with the concept of schemas.
Describe the solution you'd like.

We will extend the function that peeks with the following functionallity.

It will fetch a bundle from cosmos
Take the type and version from the document, and combine that with the query parameter format
Combine those and look in the schemas storage for any schemas following the type type/format/version
Map the contents of messages into that format, and content type the query parameter content-type
Return the message

@Renetnielsen included in PI #190


fix(linky): throw error if input is not a string

BREAKING CHANGE:
Before this change, the filter assumed that the input (if not undefined/null) was of type 'string'
and that certain methods (such as .match()) would be available on it. Passing a non-string value
would most likely result in a not-very-useful error being thrown (trying to call a method that does
not exist) or in unexpected behavior (if the input happened to have the assumed methods).
After this change, a proper (informative) error will be thrown. If you want to pass non-string
values through linky, you need to explicitly convert them to strings first.
Since input values could be initialized asynchronously, undefined or null will still be
returned unchanged (without throwing an error).
Closes #13547

TBH, I don't expect this change to actually break (m)any apps, since an error was thrown anyway (unless non-string inut had a "properly" behaving .match() method, which is unlikely).
We should, of course, keep the BC notice, but I wouldn't be too concerned about it.

just two observations:

looks inconsistent (eg not to throw on false but throw on true)
due to the BC nature and that we are in the final stages for 1.5, I would push this to 1.6

I think this is not really much of a BC. It is really just providing a better error message for an invalid input.
Regarding the fact that it does not throw on false: this is standard practice for filters, since often they receive null or undefined initially while waiting for watch values to kick in.

@petebacondarwin I am ok with doing nothing with null/undefined, but handling true and false different, sounds strange

Yes, I take it back in other filters we now test == null. E.g. https://github.com/angular/angular.js/blob/master/src/ng/filter/orderBy.js#L201
We should do this here too.

I tried to stay as close as possible to what happens now (in order to minimize the impact of the BC). Currently, falsy values are returned as is (i.e. won't throw an error).
But, I agree the current behavior is not correct. I'll make the suggested change and put this on the 1.6 milestone.

Updated, PTAL.

LGTM

One small comment that can be ignored. Otherwise, LGTM

Since it is barely a much of a breaking change I would like to get this into RC 1 - are there any strong objections to this?

If @petebacondarwin is ok with this making it into 1.5, then I am ok

Let's add the short-circuit and merge into RC 1

Smashing!

@gkalpak - you need to put the "Closes" statements before the "BREAKING CHANGES" statement, because the changelog.js generator doesn't strip them out of the BREAKING CHANGES block.

Oops, you're right ! Noted ;)


Do you test you model on IJB?

did you ever test the model on IJB? and how's the results?

No，but welcome

@TreB1eN, actually, I use your retrain model SE-IR-50 and evaluation script from insightface and loose crop data from VGG group to evaluate the performance on IJBB, the results turn to be wired---it is a little bit bad as following:
0.0001-34.37%, 0.001--59.43%, 0.01--81.77%, 0.1--93.19%. do you have any comments about this results?

@TreB1eN, actually, I used your pretrained model SE-IR-50 and evaluation script from insightface and loose crop data from VGG group to evaluate the performance on IJBB, the results turn to be wired---it is a little bit bad as following:
0.0001-34.37%, 0.001--59.43%, 0.01--81.77%, 0.1--93.19%. do you have any comments about this results?

hello, the evaluation code in insightface only supports  keras and mxnet form of pretrained weight, how did you load in pytorch model? did you modified the code yourself? Could you please share your code, thx


Trying to run multiple services at the same time causes timeout failures

Describe the bug
When running the integration tests on a GKE, EKS, or RKE cluster I get a failure: service.go:36: Failed to create service kxshh: exit status 1: time="2019-10-31T16:29:04-07:00" level=fatal msg="Timeout: request did not complete within requested timeout 30s"
To Reproduce

Clone the repo
Download the latest alpha CLI (v0.6.0-alpha.2)
Run go test -v -race ./tests/integration/... -integration-tests

Expected behavior
All tests should run and pass. There should not be timeout errors. This works on my k3s cluster.
Kubernetes version & type (GKE, on-prem): kubectl version GKE
Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.2", GitCommit:"c97fe5036ef3df2967d086711e6c0c405941e14b", GitTreeState:"clean", BuildDate:"2019-10-15T19:18:23Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"14+", GitVersion:"v1.14.7-gke.14", GitCommit:"d7951e52ecdf56a1de9e031c553569ec13849a80", GitTreeState:"clean", BuildDate:"2019-10-11T23:17:57Z", GoVersion:"go1.12.9b4", Compiler:"gc", Platform:"linux/amd64"}

Type:
Rio version: rio info
Rio Version: v0.6.0-alpha.2 (d9675e43)
Rio CLI Version: v0.6.0-alpha.2 (d9675e43)

Additional context
Nothing in rio systemlogs
go version go1.13.3 darwin/amd64

Do you get that specific error message on EKS or just GKE ? Looks like a K8's overload, we may need to turn off parallel testing in some cases. Can you try removing some of the spec.Parallel() calls, or changing to spec.Sequential().

Running them sequentially fixes the issue. It's on EKS, GKE, and RKE. Strange that it happens on all of these and not on k3s though

@rancher-max as low priority please test more; as we discussed seemed like issue may be insufficient cluster resources (vCPU, Mem, etc). Perhaps with larger clusters the issue will not happen.

It might be due to either cluster resources or configurations built with rancher. When I created an RKE cluster through Rancher, I had this issue. However when I created one manually. using the same node configurations, I did not encounter this. Also, GKE and EKS have been through rancher.
So I believe this is instead due to creating a cluster through Rancher. I don't think it's resource dependent though, because when I import these clusters that work into my Rancher configuration, they still work.


Fix travis-ci tests

It looks like the tests haven't been run for a while and are failing in #18
This is an attempt to get those working again.

Thanks guys !
I have fixed the spec tests in v2.1.2. So I'm closing this. Please re-open if still needed.


privacy added

Fixes:  #3605
Description
Updated privacy policy page to make it more genuine.

Type of PR

[x] Bug fix
[x] Feature enhancement

Screenshots

Checklist:

[x] I have made this change from my own.
[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generate no new warnings.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers and screenshots after making the changes.

@anadisharma121 please work with updated branch

@sailaja-adapa please open this issue so that I can update it in the updated branch.

i mistakenly closed this PR @anadisharma121


ERROR: Couldn't find env file , during Travis CI Build with Docker

What happened?
I am using a clean default set-up of Django Cookiecutter, didn't add or change anything. I am connecting Travis CI with it and the build fails because Travis can't find the ENV files.
The log output:
18.84s$ pip install -r requirements.txt
before_script.1
0.42s$ docker-compose -v
before_script.2
0.24s$ docker -v
Docker version 18.06.0-ce, build 0ffa825
0.40s$ docker-compose -f local.yml build
ERROR: Couldn't find env file: /home/travis/build/webconexus/myod/.envs/.local/.django
The command "docker-compose -f local.yml build" failed and exited with 1 during .
Your build has been stopped.

Which makes sense because the .env files are excluded from Github so they won't be there anymore when Travis clones the repo, but how to solve this issue then? This should work out of the box right, because the .travis.yml is included with Django Cookiecutter is supposed to work

Used Travis encrypted files to solve this, leaving the doc link here if someone else encounters this:
https://docs.travis-ci.com/user/encrypting-files/#encrypting-multiple-files


syntax highlighting looks odd for html

I might be mistaken by reporting this, but why is < template > different from

Can you confirm you're on the latest version?

i was not! I just updated and now both are red.. but oddly

Hmm, does it look like that all of the time? Try this: https://github.com/posva/vim-vue#my-syntax-highlighting-stops-working-randomly

Yes I tried that, no go. but:
it seems as if vim-stylus was out of date as well, or maybe some other plugins i had, i destroyed .vim/plugged and ran a fresh :PlugInstall
still its a bit odd that <script> is rendering that way

what's even more odd is if i
vi main.styl the syntax is proper but if i vi main.vue w/ stylus, its broken, splitting that with main.styl is broken as well.. its as if vue breaks stylus syntax..

@posva yes i agree mostly, the code in the tags work now and i'm happy. just kind of odd how stylus randomly breaks, i'll look more into vim-stylus

There's an incompatibility somewhere between NERDTree and vim-vue or one of the deps (all latest plugins and vim).
Editing a .vue directly works, but navigating to it is broken.

I had the same problem, solving it by deleting vim-polyglot

I'm not sure if this is still an issue for people but I can't reproduce it myself.
@acidjazz if you're still experiencing the stylus issue, please create a new issue for that.


Multi line env value

Describe the bug
The multi-line env value for the SSH Private Key is not supported, therefore its failing when we ssh using this.
Expected behavior
Enable multi-line env value feature

Can you not store your SSH key in a single line and then consume it? It should work, right?
Use this to convert it:
tr -d '\n' < key.txt