Fail to detect WeMo Switch with firmware WeMo_WW_2.00.10062.PVT-OWRT-SNS

ouimeaux works really well with the previous firmware, but it can't detect my WeMo Switch after upgrading firmware. Restoring to factory setting doesn't help.

+1

I seem to be having the same issue with WeMo_WW_2.00.10062.PVT-OWRT-InsightV2. If I run wemo -f list about a dozen times I will get a response once or twice in there. Increasing the timeout doesn't seem to help, it will either respond instantly or not at all.

Heck, ok, I'll try to look at this as soon as I can.
On Tue, Mar 15, 2016 at 10:36 AM Ethan Madden<EMAIL_ADDRESS>wrote:

I seem to be having the same issue with
WeMo_WW_2.00.10062.PVT-OWRT-InsightV2. If I run wemo -f list about a dozen
times I will get a response once or twice in there. Increasing the timeout
doesn't seem to help, it will either respond instantly or not at all.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/iancmcc/ouimeaux/issues/118#issuecomment-196882676

From the Belkin forum, may aid in fixing the issue:
"I believe the problem is related to a change in the way the latest firmware for the WeMo switches responds (or not) to the SSDP discovery packet. Unless the source port is set to 1900 as well as the destination port, the WeMo's now ignore the discovery broadcast.  Could someone please confirm this with Belkin and find out if their code will stay this way or if they will revert to their earlier implementation?"
hanging out for a fix!


Syntax improvements & snippets

Use the sublime text coldfusion tmLanguage, which is a single file rather than the multiple files used previously, and appears to be more up to date
Added snippets from the TextMate ColdFusion bundle.  NB: this does seem to have some negative performance and I recommend changing the editor.quickSuggestions setting to false, or increasing the delay time if this is problematic

I have published the extension to the Markeplace. Thank you very much for the awesome work!

Thanks!


Would you ever support redox os?

Their current window-manager is terrible, and this is written in rust.
I don't know how difficult it'd be, but they need the help.
https://www.redox-os.org/

AFAIK Redox uses its own display manager stack. At a bare minimum, redox would need to support the same DRM api that Wayland/Way Cooler uses to draw to the screen (not to mention cario and all the other dependencies).
It is unlikely that will happen. Let me know if they get Wayland support though.

To add on to this: I haven't spoken with the redox devs at all, but from what I've seen of the development as an outsider they want to build their own system not based on traditional Unix-likes (including the gui, which is why they aren't implementing Wayland). Things could have changed, or I could just be misunderstanding their goals.

https://doc.redox-os.org/book/introduction/what_is_redox.html
it says its supposed to be able to run linux applications just fine, later on, so i'd assume they'd have to support wayland/x.org to some extent, right? I don't actually know though.
I would assume that a window manager counts as an application? but i'm not actually sure, and i'm sure you know far better than I do the answer to that question.

Most of the reason I don't think it will happen is this thread.
Supporting Wayland requires significant kernel work (eg I don't know if they implement DRM, I have a feeling they don't), and if the work can't be justified for other Linux applications I did see it being a thing.
I'll wait and see what happens

And a window manager is technically an application, but an application that talks more or less directly to certain kernel interfaces. And that link you sent specifically says they are not POSIX compliant

From this thread, Is redox going to support wayland?, it looks like with a port of Mesa and a graphics driver it would be possible.


<< and >> on dashboard reports not working?

Is it a duplicate question?
Not that I can find
Describe the bug
On the dashboard, the reports list on the right. At the bottom there are different pages of reports and you can go to the pages by clicking the ">" or "<", these work fine, but the go-to-first-page and go-to-last-page buttons "<<" and ">>" don't work.
To Reproduce
Steps to reproduce the behavior:

Go to 'Dashboard'
Click on '<<' or '>>'
Nothing happens

Expected behavior
Should go to the last page or first page of the reports
Info
Uptime Kuma Version:1.80
Using Docker?: Yes
Docker Version: 20.10.7
Node.js Version (Without Docker only):
OS: Ubuntu
Browser: Firefox, Chrome, Safari

They are not first/last buttons.
https://github.com/louislam/uptime-kuma/blob/2e24312f67352d71ec30cea32ecc7ff9d14bceb2/src/pages/Details.vue#L212-L220

Oh ok! Sorry, typically thats what those symbols mean.
Thank you!


[WIP] Fix MiqWidgetSet#description validation to fix rake db:seed

It looks that it is possible to have MiqWidgetSet with same description but with different userid.
When those are present in DB and they have MiqWidgetSet#description=='Default Dashboard' then
MiqWidgetSet.seed is failing (when we do update!())

@miq-bot cross_repo_tests manageiq-ui-classic, manageiq-api

@miq-bot cross_repo_tests manageiq-ui-classic, manageiq-api

My DB has
[#<MiqWidgetSet:0x00007faf7396c100 id: nil, description: "default dashboard for user admin in group id 2", owner_id: nil, userid: "admin", group_id: 2>,
 #<MiqWidgetSet:0x00007faf73977e38 id: nil, description: "Default Dashboard for Physical Infrastructure Group", owner_id: 20, userid: nil, group_id: 20>,
 #<MiqWidgetSet:0x00007faf73977bb8 id: nil, description: "Optimization", owner_id: 5, userid: nil, group_id: 5>,
 #<MiqWidgetSet:0x00007faf73977938 id: nil, description: "Default Dashboard", owner_id: nil, userid: nil, group_id: nil>]

Notice the first one has owner_id as nil, but group_id as 2, and this is the one it fails on.  I don't understand what the difference between owner_id and group_id is.  cc @gtanzillo

My DB has
[#<MiqWidgetSet:0x00007faf7396c100 id: nil, description: "default dashboard for user admin in group id 2", owner_id: nil, userid: "admin", group_id: 2>,
 #<MiqWidgetSet:0x00007faf73977e38 id: nil, description: "Default Dashboard for Physical Infrastructure Group", owner_id: 20, userid: nil, group_id: 20>,
 #<MiqWidgetSet:0x00007faf73977bb8 id: nil, description: "Optimization", owner_id: 5, userid: nil, group_id: 5>,
 #<MiqWidgetSet:0x00007faf73977938 id: nil, description: "Default Dashboard", owner_id: nil, userid: nil, group_id: nil>]

Notice the first one has owner_id as nil, but group_id as 2, and this is the one it fails on.  I don't understand what the difference between owner_id and group_id is.  cc @gtanzillo

This PR does fix my seeding, though. :+1:
Only thing I'm not sure about is if this fix is correct.  I'm not sure why we have unique descriptions, so I don't know if scoping further (effectively allowing duplicate descriptions), is a problem or not.  Perhaps @gtanzillo knows better.

This PR does fix my seeding, though. :+1:
Only thing I'm not sure about is if this fix is correct.  I'm not sure why we have unique descriptions, so I don't know if scoping further (effectively allowing duplicate descriptions), is a problem or not.  Perhaps @gtanzillo knows better.

Only thing I'm not sure about is if this fix is correct. I'm not sure why we have unique descriptions, so I don't know if scoping further (effectively allowing duplicate descriptions), is a problem or not. Perhaps @gtanzillo knows better.

I'm not sure either, we look up widget sets by name during seeding here. It's possible we were just trying to prevent ambiguity in the UI if it lists them by description only. Perhaps we can just get rid of the uniqueness validation on description if that's not necessary.

Only thing I'm not sure about is if this fix is correct. I'm not sure why we have unique descriptions, so I don't know if scoping further (effectively allowing duplicate descriptions), is a problem or not. Perhaps @gtanzillo knows better.

I'm not sure either, we look up widget sets by name during seeding here. It's possible we were just trying to prevent ambiguity in the UI if it lists them by description only. Perhaps we can just get rid of the uniqueness validation on description if that's not necessary.

@gtanzillo @Fryguy

Yes, unique descriptions per group come from UI.
owner_id vs group_id - we treat with group_id as well as with owner_id and owner_type == 'MiqGroup' and I don't see any difference now and any other usage where owner_type == 'MiqGroup'
MiqWidgets with MiqWidget#userid comes are created when you go on Overview -> Dashboard. And it is generated for user when this dashboard does not exist yet. But it takes name of other widget but when this name is default then you have  more widget sets with same name. And issue is that seed method selects widget set according to name and it picks the wrong one and then it basically tries to update description which is already used.

Currently I am testing an alternative - to pick correct widget set in seed process.

@gtanzillo @Fryguy

Yes, unique descriptions per group come from UI.
owner_id vs group_id - we treat with group_id as well as with owner_id and owner_type == 'MiqGroup' and I don't see any difference now and any other usage where owner_type == 'MiqGroup'
MiqWidgets with MiqWidget#userid comes are created when you go on Overview -> Dashboard. And it is generated for user when this dashboard does not exist yet. But it takes name of other widget but when this name is default then you have  more widget sets with same name. And issue is that seed method selects widget set according to name and it picks the wrong one and then it basically tries to update description which is already used.

Currently I am testing an alternative - to pick correct widget set in seed process.

@miq-bot cross_repo_tests manageiq-ui-classic, manageiq-api

@miq-bot cross_repo_tests manageiq-ui-classic, manageiq-api

@miq-bot cross_repo_tests manageiq-ui-classic, manageiq-api including https://github.com/ManageIQ/manageiq-api/pull/995

@miq-bot cross_repo_tests manageiq-ui-classic, manageiq-api including https://github.com/ManageIQ/manageiq-api/pull/995


[Bug]: Default Height Prevents Scaling

Browser
No response
Package version
Current
React version
16
Description
Situation
I have a grid layout (2x2) and i would like to include <CodeEditor> in one of my grid-template-areas
Here is a very straight forward of my grid where i have set the 'Ace' Editor to take up the <main> component.
I have found that if i use <CodeEditor> it inline styles height: 480px; as seen here
<div class="awsui_resizable-box_1gl9c_1563r_455 react-resizable" style="height: 480px;">
https://github.com/cloudscape-design/components/blob/6d47c50e077d1e06d6c71d25416a920f8944adb3/src/code-editor/styles.scss#L192
Source code
https://github.com/cloudscape-design/components/blob/6d47c50e077d1e06d6c71d25416a920f8944adb3/src/code-editor/styles.scss#L192
Reproduction

CodePen

Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate problems

Hi @32teeth,
thanks for reaching out. There is editorContentHeight to customise editor height. Can you use it to set editor height to fit container?

Closing due to inactivity. Feel free to reopen if the solution above did not work for you


Fix calls to xdg-open from netrw

Apparently modern xdg-open returns before triggering its actions,
which causes the netrw invocation to fail. The simple fix is to run the
command in the background. Should be harmless for older xdg-open.

Codecov Report

Merging #5563 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #5563      +/-   ##
==========================================
+ Coverage   82.84%   82.84%   +<.01%
==========================================
  Files         137      137
  Lines      151743   151743
==========================================
+ Hits       125708   125709       +1
+ Misses      26035    26034       -1

Impacted Files
Coverage Δ

src/channel.c
84% <0%> (-0.08%)
:arrow_down:

src/terminal.c
82.24% <0%> (+0.03%)
:arrow_up:

src/drawline.c
84.8% <0%> (+0.13%)
:arrow_up:

Continue to review full report at Codecov.

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

Although @cecamp reads and comments here occasionally, it is usually easier to contact him directly. So please use the provided e-mail at the top of the file and contact him directly. Make sure to remove the uppercase letters (NOSPAM). Thanks!


fix(bug): input spacey names gets trimmed

fix #256
https://drive.google.com/file/d/1AG55tkWBylhnjsfIoBUb14XAytd8NceC/view?usp=sharing
if any changes required let me know !
Thank You :smile:

Hi @adityadeshlahre unfortunately I need to close this PR. We did a full refactoring of the UI and moved the forms and inputs to use shadcn/ui, and this was fixed as a part of this migration (#262)


line property of no-empty-source warnings are undefined

Problem
const {lint} = require('stylelint'); // v9.1.3

(async () => {
  const {results} = await lint({
    code: '',
    config: {
      rules: {'no-empty-source': true}
    }
  });

  console.log(results[0].warnings[0]);
})();

When I run the code above, it prints
{ line: 1,
  column: 1,
  rule: 'no-empty-source',
  severity: 'error',
  text: 'Unexpected empty source (no-empty-source)' }

But when I use stylelint-processor-styled-components,
const {lint} = require('stylelint'); // v9.1.3

(async () => {
  const {results} = await lint({
    code: '',
    config: {
      processors: ['stylelint-processor-styled-components'], // v1.3.1
      rules: {'no-empty-source': true}
    }
  });

  console.log(results[0].warnings[0]);
})();

it prints
{ line: undefined,
  column: 1,
  rule: 'no-empty-source',
  severity: 'error',
  text: 'Unexpected empty source (no-empty-source)' }

As you can see, this processor makes line property of the no-empty-source warning undefined.
Expected result
In this case, I expect line to be 1 even if stylelint-processor-styled-components is enabled.

Hmm, well for one we recommend using our shared config that disables warnings that don't make sense with our processor (such as that one), but it seems you have some very specific use case you want to use here. It would probably be a pretty simple fix, I guess it's because there aren't any lines so we aren't building our sourcemaps and then sourceMaps[1] = undefined. If you want to look into this and submit a PR feel free, but I don't think this is high priority for us

Oh okay, if it has further repercussions it could definitely something worth fixing, sorry, I just didn't see the usecase, we could even do something as simple as just outputting a default value of 1 as the line number


fix: GUI overwriting simulation output log

Removed debugging log messages for file saving that was overwriting the simulation output log when a simulation completed.

@dylansdaniels
Can you merge this one too?


Add 2024-10-01 stable to Microsoft.Dashboard

ARM (Control Plane) API Specification Update Pull Request

[!TIP]
Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

Purpose of this PR
What's the purpose of this PR? Check the specific option that applies. This is mandatory!

[ ] New resource provider.
[x] New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been created in adherence to OpenAPI specs PR creation guidance).
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix OpenAPI spec quality issues in S360.
[ ] Convert existing OpenAPI spec to TypeSpec spec (do not combine this with implementing changes for a new API version).
[ ] Other, please clarify:

edit this with your clarification

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[x] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[ ] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.

Additional information

 Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.

Getting help

First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
For help with ARM review (PR workflow diagram Step 2), see https://aka.ms/azsdk/pr-arm-review.
If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

Note: this is an identical version to 2023-10-01-preview. We are just releasing an identical stable version of it.
https://github.com/Azure/azure-rest-api-specs/tree/main/specification/dashboard/resource-manager/Microsoft.Dashboard/preview/2023-10-01-preview

Breaking changes previously reviewed and approved in https://github.com/Azure/azure-rest-api-specs-pr/pull/19253


Retrieve sphere ID from UserDefaults and run recovery check earlier

Previously, we were reading the known sphere identity from the SQLite database. This is suboptimal for a couple reasons:

The database is an index, not a source of truth, and can be thrown away and re-built at any time.
The source of truth for the known sphere identity is AppDefaults.standard.sphereIdentity (UserDefaults)

We store the identity here upon sphere creation
UserDefaults persist for the life of the app container

Relying on the database meant we had to wait until database migration was complete before checking for recovery state.

This PR makes the following changes:

Read known sphere identity from AppDefaults.standard.sphereIdentity
Run recovery check as early as possible (.start)

Additionally, I added some logs to NoosphereService to make it clearer when we experience a cache miss due to failure to construct sphere.

Playtested recovery on simulator successfully.
Steps:

Create sphere with app client at Noosphere v0.14.x
Redeem invite code
Make some notes
Sync
Update to this branch, with client at Noosphere v0.15.0
Recover


2 april 2021 in spain

hi,
dt.date(2021, 4, 2) in holidays.ES() don't work

This was fixed on #469 . Closing, thx!


Split IvyPublishResolvedVersionsJavaIntegTest

@bot-gradle test and merge

Pre-tested commit build failed.

@bot-gradle test and merge

OK, I've already triggered a build for you.

Thanks for taking care of this Bo!


New Features

Pulls in a couple PRs, adds formatting with Prettier.
Notable features:

Hour mode is now available
Padding is customizable (see details in #330)
Instead of duration, end_time can be specified.
Supports empty task list, displayed like this:

Also fixes bug in the display of dates.

README.md need an update :

If there is no end property but a duration property is provided, the end date is automatically calculated.
Added a new view mode: hour.
Custom padding for view mode: You can now add custom padding using VIEW_MODE_PADDING. Pass options.view_mode_padding if needed.
Start date is formatted in Gantt>setup_gantt_dates. Consider adding an option for default and custom date formats.
Minor fixes on date instances.
Commit (0b235d3397b): Verified HTML instance and added default date as a Date instance (1970).
Code formatted with Prettier.

I encountered an error while building (I'm trying to get a stable version incorporating all previous PRs since 0.6.1):


Fix localstack version + add required env var to api for tests + Add stagingWorkspaceType (PS-867)

Aah sorry, it seems I have forgotten here the PR for fixing that broken localstack. Is it ok if I keep it in one PR?


Use grapheme clusters in Text instead of char

char is not what users typically expect as a 'letter' so we should use
grapheme clusters instead. These can't always be represented as single
rust char types so the Text now stores a Vec of single grapheme Strings.
Fixes #44
While this makes sense from the rust side I'm not sure if it has an effect on the javascript implementation compatability. Also, not sure of its affect on the binary encoding from the javascript side again.

This is great stuff, I'm going to go ahead and merge. I am a little concerned about performance as the code paths relating to inserting and removing characters are some of the hottest parts of the frontend. However, it's going to change reasonably substantially when the new sequence patch format is merged (I have a branch with the implementation which I keep up to date with main, I'm just waiting for the JS branch to merge before putting in a PR). Once that's done then I think we should revisit performance and perhaps consider adding some benchmarks to CI.

Nice! I agree that text should best be segmented by grapheme cluster. I also looked into adding something like this on the JS side, but I was a bit hesitant about adding a dependency that would increase the code size. Am I right in understanding that the dependency on the unicode-segmentation crate is only in the Rust frontend, so it won't affect the size of the compiled wasm module?
In terms of compatibility between JS and Rust, I think both backends should allow each text "character" to be any sequence of unicode code points. The segmentation into grapheme clusters should happen once when the text is first inserted on the frontend, and thereafter everything else just preserves the segmentation that was initially performed. This gives us robustness in case the rules for grapheme cluster segmentation change (which I believe could happen from one version of the Unicode standard to the next).

Yeah this dependency will only be pulled in by applications using the Rust frontend, the backend is completely agnostic to the segmentations as you describe.


Github icon color on dark mode

Change the Github icon color on the home-page, when it's darkmode

I would like to work on this issue


[Marketplace] We agreed to hide counter

EPAM AI DIAL chat version
0.18.0
What happened?
Please hide the counter in all places

Confidential information

[X] I confirm that do not share any confidential information

Verified on staging env successfully


Error handling old method of image aquisition [not whitecube]

global name 'image_id' is not defined
I'm running from current source.
filenameformat = %image_id% - %artist% - %title%

Are you using whitecube ui? latest commit might have bug for whitecube.

Nope, and I'm using the same configs I have been for the past year. Haven't touched the cookie. Haven't had to.
[Network]
useproxy = False
proxyaddress =
useragent = Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/37.0.2062.124 Safari/537.36
userobots = True
timeout = 60
retry = 3
retrywait = 5

[Debug]
loglevel = DEBUG
enabledump = True
skipdumpfilter =
dumpmediumpage = False
dumptagsearchpage = False
debughttp = False

[IrfanView]
irfanviewpath = C:\Program Files\IrfanView
startirfanview = False
startirfanslide = False
createdownloadlists = False

[Settings]
filenameformat = %image_id% - %artist% - %title%
filenamemangaformat = %image_id% - %artist%/%image_id% - %artist% - %title% - %page_number%
downloadlistdirectory = C:\PixivUtil2\
uselist = True
processfromdb = True
overwrite = False
tagsseparator = ,
daylastupdated = 0
rootdirectory = .
alwayscheckfilesize = False
checkupdatedlimit = 0
downloadavatar = False
createmangadir = True
usetagsasdir = False
useblacklisttags = False
usesuppresstags = False
tagslimit = -1
writeimageinfo = False
datediff = 0
backupoldfile = False
writeugoirainfo = False
createugoira = True
deletezipfile = True
enableinfiniteloop = False
verifyimage = False
writeurlindescription = False
urlblacklistregex =
urldumpfilename = url_list_%Y%m%d
dbpath =
creategif = True
useblacklistmembers = False

[Authentication]
username = vampiricwulf
password = master
cookie = 6872988_013f0cbf1e12ae340670c9fcf845fc7d
keepsignedin = 1

[Pixiv]
numberofpage = 0
r18mode = False
dateformat = ''

Thanks for the quick edit, was just doing that.

can you give the stacktrace or log file?

http://pastebin.com/VFVgnrTA
How would I produce a stacktrace?

just run the app and copy the console output. It should show which line of code is failing.

I run from the source (python PixivUtil2.py), I'm looking at it right now, no lines of output that provide any sort of error message other than what you already see.

ok, do you have the imageid, so I can test?

There's some located in the pastebin, and it's not limited to just those, it's all images that give me that error.
One of the image_ids: 59634164

I can confirm it works on commit e6d2beeaa7b04b4c8c115a700ce9a9e2829a27e4

hmm, it is because whitecube then. I'll check it.

I'm going to assume it to be this line:
https://github.com/Nandaka/PixivUtil2/commit/9d9f232b080a9e00508c1c7bb6fe93095c951f71#diff-30eb981ce68adac654c4cdeb81b2924cR272

try the latest commit, it should be fixed for non-whitecube

Looks like it works!


Add logic to leverage additional_stores for DCD reporter files

Add logic to leverage additional_stores for DCD reporter files to write them to a data store suitable for potentially large files

This issue will be handled by https://github.com/xperrylinn/atomate2-openmm/pull/14

https://github.com/xperrylinn/atomate2-openmm/pull/14 has been merged


Experience

I used this for two weeks then someone logged into my account and changed my guns around and it kept kicking me out. Why would you guys build something with a trojan in it?

?
who knows what you have installed and from where you downloaded it.

Updated

Close the issue please, you are clogging up development


Dependency error with Python versions > 3.10

Fizzysearch currently depends on numpy 1.22.4. This version of numpy is only compatible to Python versions until 3.10. When trying to install fizzysearch with Python > 3.10, it will fail with errors during installation. The reason being that starting with Python 3.10, distutils (on which numpy 1.22.4 depends) is no longer included by default and has been integrated into setuptools. Therefore, with newer Python installations, the installation process fails with
ModuleNotFoundError: No module named 'distutils'
Solution: Use a newer version of numpy that is compatible with Python > 3.10

I had perviously pinned numpy to 1.22.4 because newer versions caused conflicts in some other libraries which didn't support the newer numpy. (I forget which)
Will give it another try, with newer numpy versions. Hopefully those other packages have since also upgraded.


viewRender is not working ui-calendar

<div ui-calendar="{{uiConfig.calendar}}" calendar="simbaCalendar" ng-model="eventSources">
</div>

I have used remote url to fetch events.
$scope.uiConfig = {
        calendar:{
            height: 450,
            editable: false,
            stick: true,
            header:{
                left: 'prev,next today',
                center: 'title',
                right: 'month,basicWeek,basicDay'
            },
            viewRender: function(view, element) {
                $log.debug("View Changed: ", view.visStart, view.visEnd, view.start, view.end);
            }
        }
    };

viewRender is not working into uiConfig object. $log.debug is not print in console.
Please help me.
Thanks.

I think should change: ui-calendar="{{uiConfig.calendar}}" to ui-calendar="uiConfig.calendar"

Working very well...Thanks


Lora Class C Example

Hello
Do you have a sample or a suggestion on how to set the device to be a Class C Device?
Thanks
Greg

If you take a look at the latest command reference http://ww1.microchip.com/downloads/en/DeviceDoc/RN2903 LoRa Technology Module Command Reference User Guide-DS40001811B.pdf
There is a command mac set class c that should do the trick, but you'll have to first upgrade to 1.0.5 firmware using the LoRa Development Suite GUI https://www.microchip.com/developmenttools/ProductDetails/dv164140-1

thank you!!

@lolsborn I cannot find the place to download firmware version 1.0.5.

Are you using the RN2903 (US) or RN2843 (EU)?
Here is the US version link:
https://www.microchip.com/wwwproducts/en/RN2903
If you go to *software *you'll want to download two things

LoRa Development Suite (You'll use this GUI to flash the device)
RN2903 Firmware v1.0.5 http://ww1.microchip.com/downloads/en/DeviceDoc/RN2903_1.0.5_Nov_06_2018_10.45.27.zip

There are two copies of the firmware one is the "unified" version which includes the bootloader which is used for flashing using a Pic programmer. You want the other one, that one doesn't contain the bootloader and is used for programming over USB.
On Sun, Jun 16, 2019, at 11:24 AM, Greg Svitak wrote:

@lolsborn https://github.com/lolsborn I cannot find the place to download firmware version 1.0.5.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/ronoth/LoStik/issues/19?email_source=notifications&email_token=AAAOZBBY6DNQBMFD6MVEU3DP22AM3A5CNFSM4HYBIGH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXZSOWA#issuecomment-502474584, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAOZBATU6SF2L7LNEOBZF3P22AM3ANCNFSM4HYBIGHQ.

Hello excuse me english I want to know if everyone knows how read the value that sends the LoRa server in the node. I configure the RN2903a to class c and it responds ok, in class a it works correctly, Thanks.


added RocketChatClient and samples

Added the RocketChatClient and a sample to it.

I updated them accordingly. For the demo scene, I created a canvas, on which people can test some methods and get used to the basics very quickly.


[ExperimentalWarning] When doing a transcript.

ExperimentalWarning: buffer.File is an experimental feature and might change at any time
Maybe replacing the used deprecate-features with other alts..
(node:12008) ExperimentalWarning: buffer.File is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
ExperimentalWarning: buffer.File is an experimental feature and might change at any time
    at emitExperimentalWarning (node:internal/util:238:11)
    at new File (node:internal/file:40:5)
    at makeEntry (node:internal/deps/undici/undici:6295:43)
    at FormData.append (node:internal/deps/undici/undici:6207:23)
    at _REST.resolveRequest (D:\MYBOT\node_modules\@discordjs\rest\dist\index.js:1314:20)
    at _REST.queueRequest (D:\MYBOT\node_modules\@discordjs\rest\dist\index.js:1252:46)
    at _REST.request (D:\MYBOT\node_modules\@discordjs\rest\dist\index.js:1218:33)
    at _REST.post (D:\MYBOT\node_modules\@discordjs\rest\dist\index.js:1192:17)
    at TextChannel.send (D:\MYBOT\node_modules\discord.js\src\structures\interfaces\TextBasedChannel.js:162:38)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

I do not think this is a discord-html-transcripts issue, looking at the stack trace, this comes from undici which is called from @discordjs/rest and from discord.js. I would recommend updating node.js if possible.


Timed out fetching a new connection from the pool

Bug description
I'm creating a multitenant system managed by this function:
import { PrismaClient as TenantPrismaClient } from "C:/Users/GianroccoNicassio/Documents/dev/atoms-api/prisma/tenant/generated/atoms_tenant/index.js";

/**
 * This class defines methods for tenant database connection creation.
 *
 * @class TenantDatabase
 */
class TenantDatabase {
  // Declaring properties.
  public prisma: TenantPrismaClient<any> | undefined;

  // Declaring methods.
  constructor(tenant: any) {
    this._setTenant(tenant);
  }

  /**
   * This method creates a new database connection on database requested.
   *
   * @method _setTenant
   * @param tenant any
   */
  private async _setTenant(tenant: any) {
    // Create a new connection and set it like connection instance.
    this._setPrismaClient(
      new TenantPrismaClient({
        datasources: {
          db: {
            url: process.env.CUSTOM_DATABASE_URL + tenant.db_name + ";",
          },
        },
      })
    );
  }

  /**
   * This method is a setter for prisma client property of the instance.
   *
   * @method _setPrismaClient
   * @param prismaClient object - TenantPrismaClient
   */
  private _setPrismaClient(prismaClient: TenantPrismaClient) {
    this.prisma = prismaClient;
  }
}

// Interface to standardize a connection.
interface PrismaConnectionDictonary {
  [key: string]: TenantDatabase;
}

/**
 * This class defines tenants' database connections gesture methods.
 * This is an artifice to define a "smart" connection pool that doesn't permit to instantiate more than one db connection for tenant.
 * @class TenantConnection
 */
class TenantConnection {
  // Declaring properties.
  private _connection_pool: PrismaConnectionDictonary;

  // Declaring constructor.
  constructor() {
    this._connection_pool = {};
  }

  /**
   * This method is used to retrieve requested tenant prisma client.
   *
   * @method getPrismaClient
   * @param tenant any
   */
  public getPrismaClient(tenant: any) {
    try {
      // Connection pool already has a connection for the tenant requested?
      if (this._connection_pool[tenant.code]) {
        // Returning the existing connection.
        return this._connection_pool[tenant.code].prisma;
      } else {
        // Creating a new connection and updates the pool.
        let connection = new TenantDatabase(tenant);

        this._updateConnectionPool({ [tenant.code]: connection });

        return connection.prisma;
      }
    } catch (error) {
      throw error;
    }
  }

  /**
   * This method updates connection pool with existing instance of connection established.
   *
   * @method _updateConnectionPool
   * @param connection object - PrismaConnection
   */
  private _updateConnectionPool(connection: { [key: string]: TenantDatabase }) {
    try {
      Object.assign(this._connection_pool, connection);
    } catch (error) {
      throw error;
    }
  }
}

// Declaring db connections gesture instance as loader.
let database = new TenantConnection();

// Exporting loader.
export default database;

I have a .prisma schema with the structure of all tenants and the url value of the datasource db has the shadow tenant database url. Every time that an HTTP request is sent to the server, it has an X-Tenant header inside the headers to search the tenant requested and use it to create a PrismaClient and insert it inside the dictionary connection_pool, or recycle it if it was already created and inserted in the dictionary.
The problem is random and 1/2 times every 3 days this error income:

Ignore connection limit: 1, the same error incomed with 5 and 100 connections.
What can I do for this?
Note:
@garrensmith https://github.com/prisma/prisma/issues/7249
I saw that you closed this issue that it's pretty similar to my issue. Did you find the solution for this?
How to reproduce
Actually there is no way to reproduce it, there is this function and 1/2 times every 3 day this bug happens.
Expected behavior
It must work as always. It must take the tenant object, extract the db_name and use it with the URL combo and connect to that. It works always, except in these cases.
Prisma information
There are no schema problems.
The bug incomes everytime in the first query done to the tenant database selected. As you can see from the image, the query is on contact.findUnique(), nothing special.
Environment & setup

OS:
Database:
Node.js version:

Prisma Version
Environment variables loaded from .env
prisma                  : 4.11.0
@prisma/client          : 4.16.1
Current platform        : windows
Query Engine (Node-API) : libquery-engine 8fde8fef4033376662cad983758335009d522acb (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli 8fde8fef4033376662cad983758335009d522acb (at<EMAIL_ADDRESS>Format Wasm             : @prisma/prisma-fmt-wasm 4.11.0-57.8fde8fef4033376662cad983758335009d522acb
Default Engines Hash    : 8fde8fef4033376662cad983758335009d522acb
Studio                  : 0.483.0

Which database are you using here?
Unrelated note: I noticed that your Prisma CLI version is not in sync (4.11.0) with the Prisma Client, we recommend keeping these in sync.

Which database are you using here?
Unrelated note: I noticed that your Prisma CLI version is not in sync (4.11.0) with the Prisma Client, we recommend keeping these in sync.

Sorry, I forgot that note block. Anyway, I updated the info.

Hello @Giarry156
we have a similar approach and use multiple prisma clients in our company in similar dictionary.
Let's think about it:

this error needs some time to happen
you are able to add tenants at runtime
you have a default connection limit if not explicitly set, which depends on your cpu cores, see: documentation
your database has a fixed size of connections it allows ( especially in cloud environments)

A connection pool timeout happens if the prisma client is not able to receive a connection from the connection pool in time (connection timeout). According to this what  are possible issues, or what would i check:

check how many tenants and prisma instances you want to create. I create them initially once on startup
the connection limit: set it manually like recomemded in the doc link. Assuming you have 4 cores, where your prisma app is running, each prisma Client will per default use connection limit of (2 threads × 4 cores +1) = 9.  Assuming you have 2 tenants, you are already requesting for each prisma Client 2×9=18 connections  in worst case if you do not set the connection limit manually. Prisma would recommend to give one tenant1 prisma dbclient a connection_limit of 5 and for tenant2  a limit of 4 if i understand it correcrly.  So that you do not exceed the 9. You share them between the clients. If you don't set it manually, maybe the other threads are already maintaing other connections in their pool. So other prisma connections pools can not be filled with enough connections to handle your queries
Your database server must be able to fit this max number of additional 9 client connections (also  user connections or other applications can access your database and needs connections - so dont forget them)
according to this knowledge i would not allow to add tenants at runtime. Or you reinstantiate prisma clients with an adjusted limit if one dbclient is added. You as the developer should be in control which tenants are created with which connection limits. Assume via frontend admin users are adding prisma clients and they create 10 tenants and you are not in control. That is why I set them up on startup (via environment variable holding a json array of several database connection urls including the connection limit) and then they are not touched again.
Verify if there are long lasting queries running in the background. Querys block the connection and let them free into the pool if they finish. If you have multiple long lasting queries running at the same time, this can cause issues, then you are forced to improve your query performance
If you are in the production environment I also recommend pgboucer for managing and removing dead connections, but don't forget the pgbouncer=true in the url

Here also some useful link related to the pool size:
https://www.prisma.io/docs/guides/performance-and-optimization/connection-management#recommended-connection-pool-size
I hope this helps to figure out the issue. If you got the issue, i would be interested in the solution :)
Best regards
Andreas

We're not using multitenancy but we're running on Google Cloud Run which can scale up. We're also using pgBouncer with pgbouncer=true option enabled in DATABASE_URL. I'm still figuring out why is this happening and we've recently set up a monitoring of prisma connection pool which proves the point that there's something rotten.
Here's our Prisma code setup:
import { Prisma as P, PrismaClient } from '@prisma/client';
import { Service } from 'typedi';

class PrismaInternal extends PrismaClient {
  constructor() {
    let config: P.PrismaClientOptions = {};

    super(config);

    this.$connect().catch(e => {
      throw e;
    });
  }

  async $connect() {
    try {
      return await super.$connect();
    } catch (error) {
      console.error(
        `Failed to establish a connection with the database at ${process.env.DATABASE_URL}. Terminating a process...`
      );
      console.error(error);
      process.exit(1);
    }
  }
}

const prismaGlobal = new PrismaInternal();

// to make double sure we only use a single instance of Prisma
// to avoid connection pool issues: https://www.prisma.io/docs/guides/performance-and-optimization/connection-management#prevent-hot-reloading-from-creating-new-instances-of-prismaclient
@Service({ global: true, factory: () => prismaGlobal })
export class Prisma extends PrismaInternal {}

And here's how we monitor the prisma every 5 minutes:
  async sendMetrics(serviceName: string) {
    const project_id = await this.getGcpProjectId();
    const metrics = await this.prisma.$metrics.json();

    const metricsToReport = METRICS_TO_REPORT.flatMap(metricName => {
      return metrics.gauges.find(({ key }) => key === metricName);
    });

    const data = metricsToReport.filter(Boolean).map(
      metric =>
        ({
          metricKind: 'GAUGE',
          unit: 'connections',
          metric: {
            type: METRIC_TYPE,
            labels: {
              metric: metric?.key,
            },
          },
          resource: {
            type: 'generic_node',
            labels: {
              project_id,
              location: 'us-central1',
              namespace: serviceName,
              node_id: `${process.env.K_REVISION || 'local'}:${
                process.env.K_INSTANCE || 'local'
              }`,
            },
          },
          valueType: 'INT64',
          points: [
            {
              interval: {
                endTime: {
                  seconds: Date.now() / 1000,
                },
              },
              value: {
                int64Value: metric?.value,
              },
            },
          ],
        } as google.monitoring.v3.ITimeSeries)
    );

And this is the graph we see of Prisma open connections over time:

We didn't set a connection limit in our DATABASE_URL and it appears from the chart that Prisma goes wild on allocating new connections.

@Durisvk Facing the same issue with metrics.

@Durisvk @imwexpex Please create new issues for your problems. Although they are also about connections, they do not seem to be caused by the same root problem as what @Giarry156 reported - and hence we can not debug them in the same issue. Make sure to fill the full issue template, so we have all the information we usually need. Thank you.

I think @andreasvh-conceto gave a great response here, that I hoped helped @Giarry156 to figure this out. Closing for now.


Check length of host group before erroring. Fix race condition

When multiple hosts run at the same time with a new host group,
a race condition occurs. All the hosts query and find that the
host group does not exist. They then all try to create the host
group. Only one will succeed, the others will get an api error.
If the group gets created/exists, the subuquent call to get the host
group will have one result.

Fixes #215


Correction at the comments

line 17: 78 and 110 in Ascii is the character 'N' and 'n'. Not 'Y' and 'y'
line 24: 89 and 121 in Ascii is the character 'Y' and 'y'. Not 'N' and 'n'

line 17: 78 and 110 in Ascii is the character 'N' and 'n'. Not 'Y' and 'y'
line 24: 89 and 121 in Ascii is the character 'Y' and 'y'. Not 'N' and 'n'


Pretty much the entire GoDoc

I think possibly this package was started before golint started chirping at people about the form their GoDoc comments too. Regardless, golint has something to say about every single comment on every single function, and besides making the package harder to use, might affect other documentation-generating tools that consume go and emit a document. I should have done it long ago.

Closing this because it's more-or-less done here and completely done in the downstream onramp which I recommend most people use anyway.


feat: Allow editing free canvas in preview mode

Closes #1739
This PR:

saves the changes made while previewing free canvas layout in different breakpoints, and keeps the layouts separate for each breakpoint (xl, lg, md, sm),
makes the preview mode size reflect the true size of the breakpoint, making the area horizontally scrollable when the screen size if lower than the breakpoint that's being previewed,
adds a new preview breakpoint (xl) and aligns all of them with free canvas layout breakpoints.

How to test

Go to this link.
Add two new charts.
Proceed to layout options.
✅ See that there are four options in the preview menu (up from three).
Switch to a dashboard / free canvas layout.
✅ Enable preview mode and see that the first one shows 4 columns, the next one 3, then 2 and 1.
✅ Edit the dashboard in different preview modes and see that the changes are persisted between switches.
Make your browser window smaller.
Enable first (xl) preview mode.
✅ See that the area still shows 4 columns and is horizontally scrollable, which allows users with smaller screens prepare their dashboards for larger ones when they're embedded.

I find the behavior of the preview buttons a bit confusing.

When I click on the left arrow when the panel is hidden, to reshow the panel, I am out of the preview mode, and I find it confusing since the UI elements are so far away from each other on the screen.
Maybe the fact that we are "in preview mode" should be more explicit.
I can open the left panel by clicking on the title, but then I cannot close it
Would it be possible to show the extent of the screen + the width in pixel ?

On the coding size, nothing stood out as blocking. I think it would be good to add tests, particularly around the "initialized" behavior, and around the changing layouts responsively and checking what happens.
I wonder as a user if we should mark layouts differently in the UI when they have been changed from the auto layout ? Will the user have to change the 4 layouts ? I think having to think about 4 different screen size is a bit difficult for the user, I wonder why decision was made to increase to 4, instead of reducing to 2 layouts ? As far as I understood, dashboards would be used mainly in articles in a CMS where the width would be not so large ?

Thanks for reviewing and feedback @ptbrowne 🙇♂

For the showing / closing of sidebar, I would ping @KerstinFaye – I think the initial idea was to give more screen estate to be able to preview the charts without distractions, as it's not intended to edit e.g. shared filters or titles while in this mode. Maybe changing the >> icon to X would already help?
Here also ping @KerstinFaye, I agree it could be a bit more explicit, maybe again with the "close preview" button, rather than "show sidebar and exit the preview by proxy",
I am not sure if I reproduce, I'm able to close the title / description annotator with "Back to main button". But it's another question if we should be able to edit the titles while in preview, I guess it should be disabled 👍
Do you mean some additional text, e.g. at the top, indicating whether the given layout "fits" on user's screen? Like Preview width: 1280px / Screen width: 1086px? I tried to make it obvious by having scrollbar on top, so you immediately see that it needs to be scrolled, but that would be another solution :)

For marking the layouts as "edited", we also discussed this briefly with @KerstinFaye yesterday; we could have e.g. a "reset" button to be able to get back to original layout, derived automatically from largest one, currently we need to switch the layout from free canvas to a different one, go back to editing mode, then to layouting and change layout to free canvas again. Here we didn't make a decision yet, but could be a nice improvement 😄
I think we had even more breakpoints at first (5?), but without an option to modify the smaller ones. I think it's good to give an option to edit each layout separately, as e.g. by default the two-column layout moves charts to the right, and not left, as I'd expect. Having a way to fix it or tailor the layout for each breakpoint would help mitigate that, but also could make it more time-consuming if you have lots of charts and really custom layout with totally different order than a default one.
Here I think also a potential solution would be something like "propagate layout down", to auto-create layouts for breakpoints smaller than the current one based on current layout 🤔

Here I think also a potential solution would be something like "propagate layout down", to auto-create layouts for breakpoints smaller than the current one based on current layout 🤔

This is the default behavior of the library if you do not specify a layout. So maybe if a responsive layout has not been changed by the user, it should not be saved ?

I am not sure if I reproduce, I'm able to close the title / description annotator with "Back to main button".

My mistake, I thought "Back to main" would go to the previous page, sorry.

But it's another question if we should be able to edit the titles while in preview, I guess it should be disabled 👍

Mmh, not sure, maybe it's interesting to be able to see that your title on mobile is very long and therefore should be changed ?

Do you mean some additional text, e.g. at the top, indicating whether the given layout "fits" on user's screen? Like Preview width: 1280px / Screen width: 1086px?

I think it could be a good information for the user to know what is the size in pixel of the layout. I imagine a chart editor wanting to make a dashboard for an article, maybe they know the size of their article layout ?

I think it's good to give an option to edit each layout separately, as e.g. by default the two-column layout moves charts to the right, and not left, as I'd expect

I wonder about the usecase here to be able to change 4 screens ? I personally would feel bad to write in a documentation: "For best results, you are required to modify the 4 responsive screens". I think people generally think in terms of "mobile", "desktop" and anything beyond that is too complicated.

This is the default behavior of the library if you do not specify a layout. So maybe if a responsive layout has not been changed by the user, it should not be saved ?

Yup, I think it's a good approach to only save the layout if it has been actually manually modified by the user 👍 Still, they could go out-of-sync if larger layout is edited afterwards, but this maybe will eliminate at least some cases of reorganizing layouts in different previews (maybe with some indication of already being edited, this would be clear).

Mmh, not sure, maybe it's interesting to be able to see that your title on mobile is very long and therefore should be changed ?

Agree :)

I think it could be a good information for the user to know what is the size in pixel of the layout. I imagine a chart editor wanting to make a dashboard for an article, maybe they know the size of their article layout ?

Right, this also makes sense 👍

I wonder about the usecase here to be able to change 4 screens ? I personally would feel bad to write in a documentation: "For best results, you are required to modify the 4 responsive screens". I think people generally think in terms of "mobile", "desktop" and anything beyond that is too complicated.

To me it's still a trade-off between an effort to create a chart, and potentially fitting better e.g. a tablet or smaller laptop screen :) Either we give an option to tailor the layouts better for more screens, resulting in better end-user experience, or we limit this to two, to make editor's life easier. I think I'd personally prioritize end-users, but there's also a point in keeping it simple.
I would like to also discuss this with Kerstin before making bigger changes, but thanks again for the comments, I think they're really valuable 💯

I would like to also discuss this with Kerstin before making bigger changes, but thanks again for the comments, I think they're really valuable 💯

For sure, as I said, nothing is blocking for me :)

Either we give an option to tailor the layouts better for more screens, resulting in better end-user experience, or we limit this to two, to make editor's life easier. I think I'd personally prioritize end-users, but there's also a point in keeping it simple.

I think the risk I see is that by making the experience of responsiveness too complicated, people do not do it, and then end users suffer ;) Also I think there is a point of facilitating chart creators life because if they spend less time on tweaking responsiveness issue, maybe they can spend more time finding a good title / description etc.. which in the end would help the end user ;)

@ptbrowne Thank you for your feedback and input.
UI text for preview button:
I appreciate your ideas. I've already done the changes in Accent.
( However, the French translations are still pending. Since I translated the German version slightly differently, I would welcome your input on the French translation.)
Scrollbar that appears when the current screen size is too small for the preview:
I discussed an improvement with @bprusinowski to place the scrollbar at the bottom of the window and create a sticky segment for the "show sidebar" and preview buttons at the top.  I think your suggestion to display pixel dimensions is interesting, but I'm not sure it's necessary given our 4 available screen preview sizes. (but I keep it in mind for the next iteration)
Making the preview mode more explicit and having the UI elements in the preview mode closer together:
The preview mode still allows users to edit. To me hiding the sidebar rather than having an "exit preview mode" option would be the correct element for this case. Users can still edit charts and titles in this mode.
4 preview sizes & and edit independently:
I find the option to edit and make changes for each size independently valuable.
And to be mentioned as well that it is not an obligation, since they can simply proceed without making any changes and leave the default version.  The default version already provides good results, which can often be published as-is. (This is different from a scenario where users would have to create everything from scratch.)
I agree with Bartosz that a reset button to revert to the default version could be useful. I'll add this to the list for the next iteration. We've also considered an option to "sync layout based on next bigger size," but this enhancement can be discussed later.
For now, I don't think it takes users much time to scan through the preview sizes and check if it looks good.
I wouldn't automatically adapt the smaller size to changes made in the bigger size, for the reason Bartosz mentioned. I believe it's easier for users to understand that each size can be edited individually.
I'd like to keep the 4 different sizes, since I realized in the usability test, that small desktop screen is often used as well.


Lack of HealthCheck ,we need it

Currently Dubbo does not have the ability of readiness check and that is somehow very helpful and needed in production env.
Does dubbo team has any plans on it ? can you show some detail design drafts ?
Our team currently is planing to add the healthcheck ability on dubbo , so we want to know dubbo team's opinion , if ok , we may give a pr on this topic.

@stoneapple
Can you describe the requirements in detail? Or is the dubbo service fully exposed to provide hooks?

@stoneapple It's a nice way to describe more details for your idea.

@stoneapple
Can you describe the requirements in detail? Or the dubbo services fully exposed to provide hooks?

we know dubbo have the delay exposed ability, sometimes delay time is not easy to figure out. Also we may want to check other resources like db,cache before we exposed our service to meet the business trade.

我这边提供一个思路看看是否可行，实现一个最低优先级的ServiceBean, 在这里拿到所有spring上下文ServiceBean的名字(BeanFactoryUtils.beansOfTypeIncludingAncestors(applicationContext, ServiceBean.class, false, false)), 每次在服务export时把成功暴露的bean从map剔除，在最后一个低优先级servicebean中检查没有正确暴露服务。

我这边提供一个思路看看是否可行，实现一个最低优先级的ServiceBean, 在这里拿到所有spring上下文ServiceBean的名字(BeanFactoryUtils.beansOfTypeIncludingAncestors(applicationContext, ServiceBean.class, false, false)), 每次在服务export时把成功暴露的bean从map剔除，在最后一个低优先级servicebean中检查没有正确暴露服务

should not rely on spring.

what I propose is to provide a builtin health service which expose metrics data to the user, from which at lease user can easily to learn whether all other services are UP or not.

In what condition would we consider a service is ready for use?
Currently, we have a serial of model[https://github.com/apache/incubator-dubbo/tree/master/dubbo-rpc/dubbo-rpc-api/src/main/java/org/apache/dubbo/rpc/model] artifacts which store all the services consumed and provided by one application. Some telnet commands, for example, ls, online and offline rely on this model to retrieve service status and update the service status if it's a write command.
But the service status in these models on reflects whether a service has been published to the registry. It cannot meet @stoneapple's requirements:

we know dubbo have the delay exposed ability, sometimes delay time is not easy to figure out. Also we may want to check other resources like db,cache before we exposed our service to meet the business trade.

To meet this customized requirement, I think we should add a hook mechainism in the export/unexport process and let the users to register callbacks, once the export/unexport process finished Dubbo will trigger all these callbacks. And still, besides callbacks, we need a place to store the status of all services, and I think model artifacts can be a good choice.
A step further, what about the abnormal scenarios, e.g., connection broken, resource exhausted, should we also update the service status, these will mostly happens at runtime, while the scenario @stoneapple cares is focused on starup phase.

How to export the health check service to end users, monitor systems or peer Dubbo Consumers? http, telnet or Dubbo?

I think http is more general and more convenience to use for end users and monitor systems, but for peer Dubbo Conumers it maybe not the the case.

In what condition would we consider a service is ready for use?
Currently, we have a serial of model artifacts which store all the services consumed and provided by one application. Some telnet commands, for example, ls, online and offline rely on this model to retrieve service status and update the service status if it's a write command.
But the service status in these models only reflects whether a service has been published to the registry. It cannot meet @stoneapple's requirements:

we know dubbo have the delay exposed ability, sometimes delay time is not easy to figure out. Also we may want to check other resources like db,cache before we exposed our service to meet the business trade.

To meet this customized requirement, I think we should add a hook mechainism in the export/unexport process and let the users to register callbacks, once the export/unexport process finished Dubbo will trigger all these callbacks. And still, besides callbacks, we need a place to store the status of all services, and I think model artifacts can be a good choice.
A step further, what about the abnormal scenarios, e.g., connection broken, resource exhausted, should we also update the service status, these will mostly happens at runtime, while the scenario @stoneapple cares is focused on starup phase.

How to export the health check service to end users, monitor systems or peer Dubbo Consumers? http, telnet or Dubbo?

I think http is more general and more convenience to use for end users and monitor systems, but for peer Dubbo Conumers it maybe not the the case.

yes,i think a hook mechanism maybe a nice solution.Simply,add all the service ready for export to a list collection , when all the ready service are all added, we check the system readiness. Let these services do export if check passes, or waiting until check passes.
       besides startup, we also need runtime checking ability

Dear all,
Adding health checking for a service is an interesting feature.
Was this feature implemented in the recent version, or do we have any plan to implement it in a near future?


Update Shapes API to return data as tuple

🧰 Task
As discussed in #2784 , it is surprising that directly editing the list returned in my_shapes_layer.data doesn't update the layer's shapes, even if the user tries a layer refresh.
We should update Shapes.data to return a Tuple instead of a list, as it is immutable, and update the API docs to mention that the data property is read-only.

I think some of the list methods are useful for the Shapes layer manipulation, such as pop and  insert.
Problems of a property being editable but not functional also apply to layer.features["key"] = value. How about just emphasize it more in docs? (My personal opinion is that this is not what tuple is supposed to be used.)


Support reading CPU arch from uname

As titled.

Closed via https://github.com/Simple-XX/SimpleKernel/issues/126


Repository maintenance: add GitHub Repo Gardening action and issue templates

Proposed changes:
The Repo Gardening action is a tool that one can use to automate some of the tasks that you can perform to monitor activity in your repository.
https://github.com/marketplace/actions/repository-gardening
It includes different tasks, that can be enabled based on your needs.
This PR gets us started with the action by enabling a few tasks.

This action relies on a few secrets that have already been added to this repo.
Of note, gatherSupportReferences and replyToCustomersReminder aren't too useful right now, but will become useful once the plugin is released on WordPress.com and once we start receiving feedback from WordPress.com site owners.
The flagOss task will point to #fediverse for now. This can be updated later on.
I've added mapping for our 2 block directories, but that mapping can be extended for more automatic labeling later on.

This PR also brings in issue templates that are commonly used across Automattic repos.
Other information:

[ ] Have you written new tests for your changes, if applicable?

Testing instructions:
This cannot really be tested befre the PR is merged, since it is only triggered on issues and PR events that happen once it has been merged.

thanks @jeherve


Test cases for numeric and temporal planning

@roeger @arbimo This PR adds the tests for the oneshot planning mode for both numerical and temporal domains. I also added new tests for the anytime mode in the numerical domain.
The conftest.py file has been modified to accept planners that support the anytime mode.

Hi @arbimo,
can you check this pull request and let us know if we can proceed with the merge?
--Ivan


Missing metrics for Buckets without any tag

It looks like the exporter is ignoring S3 Buckets, that do not have any tag. When running it only shows a few buckets, which are this that have tags and others are missing. As soon as I add a tag to a Bucket that does not have one before, it shows up in the metrics.
This is my config:
discovery:
  jobs:
    - type: s3
      addCloudwatchTimestamp: true
      length: 172800
      period: 86400
      regions:
      - eu-west-1
      - us-west-1
      - us-west-2
      - eu-central-1
      roles:
      - roleArn: "arn:aws:iam::xxxxxxxxxxxx:role/cloudwatch-exporter" # production
      - roleArn: "arn:aws:iam::yyyyyyyyyyyy:role/cloudwatch-exporter" # common
      metrics:
        - name: NumberOfObjects
          statistics:
            - Average
        - name: BucketSizeBytes
          statistics:
            - Average

The logs do not indicate any error:
{"level":"info","msg":"Parse config..","time":"2021-07-12T13:42:56Z"}
{"level":"info","msg":"Startup completed","time":"2021-07-12T13:42:56Z"}

The same issue for ElastiCache.
No metrics on cluster without any tags. After I added a tag, the metrics for this cluster was successfully grabbed by YACE.
config:
  discovery:
    jobs:
    - type: ec
      period: 300
      length: 300
      regions:
      - eu-central-1
      metrics:
      - name: NewConnections
        statistics:
        - 'Average'
      - name: CurrConnections
        statistics:
      - name: CPUUtilization
        statistics:
        - 'Average'
      - name: EngineCPUUtilization

I just noticed that it is actually mentioned in the README:

Note: Only tagged resources are discovered.

It would still be desirable from our side to have this.

Thats not intended currently. We rely on tags in the exporter.

Thats not intended currently. We rely on tags in the exporter.

Is this because of a technical limitation/hurdle or because it is just not desired for some reason?
I am asking because we have to decide how to continue with this issue. IMO not catching untagged resources will inevitably make some resources invisible, if someone forgets to add a tag and therefore make alerting more unreliable.

After some digging I learned that this is a technical limitation that stems from the AWS ResourceGroupStagingAPI's GetResources API. It is what YACE uses to find resources to pull metrics for, and it only returns resources that have been tagged at any point in history.
https://docs.aws.amazon.com/cli/latest/reference/resourcegroupstaggingapi/get-resources.html


Add scrollable div layer to Project metadata view to prevent cutoff of CLOSE button

Currently if values in the Project metadata editor are too large then the CLOSE button is not seen and clickable to users.
Current Results
If the length of values is too long in any of the keys, then sometimes the CLOSE button will be cutoff and hidden from a user preventing them from being able to close the Project metadata panel.
Expected Behavior
Provide 2 things:

a scrollable div layer that can hold and scroll through all the key:value rows.
while scrolling, keep the CLOSE button at the bottom, and the Key and Value header labeling at the top.

Screenshots

Versions

Operating System: Windows 10
Browser Version: Firefox
JRE or JDK Version: JDK15
OpenRefine: 3.5 beta1

Datasets

Additional context
Using Cypress support for Visual testing, ensure to add 1 Cypress test that can

click edit on Title row and add lots of text into value input box and click OK.
using a previously cropped baseline image of the lower left corner that includes the CLOSE button.
compare that cropped baseline image with a clip region of the screen during test, such as example (adjust numbers as necessary)

  .toMatchImageSnapshot({
    clip: { x: 125, y: 870, width: 75, height: 50 },
  });

assert that the CLOSE button is still displayed and seen

I would like to work on this issue.

Is there any cypress visual test already implemented ? . I am unable to find it .


Cluster Stuck Removing "wrangler.cattle.io/mgmt-cluster-remove"

Rancher Server Setup

Rancher version: v2.5.9
Installation option (Docker install/Helm Chart):

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): Helm Chart on RKE

Proxy/Cert Details: Certmanage but use custom officially signed certificate for the Rancher Ingress

Information about the Cluster

Kubernetes version: v1.19.15

Describe the bug
I wanted to remove a cluster from our Rancher but its been stuck for hours on "Waiting on wrangler.cattle.io/mgmt-cluster-remove".  I already tried restarted the Rancher Cluster and I already tried deleted the cluster node of the cluster I want to be removed.
Result
Cluster is stuck in removing state.
Expected Result
The cluster should be removed from Rancher.
Screenshots

Logs (Rancher Container in K8s)
2021/10/14 08:43:14 [ERROR] error syncing 'c-jf2t5/m-16c7c070bc7e': handler node-controller: ClusterUnavailable 503: ClusterUnavailable 503: cluster not found, requeuing
2021/10/14 08:43:14 [ERROR] error syncing 'c-jf2t5/m-17d543fc3464': handler node-controller: ClusterUnavailable 503: ClusterUnavailable 503: cluster not found, requeuing
2021/10/14 08:43:14 [ERROR] error syncing 'c-jf2t5/m-f9af0ee1cad8': handler node-controller: ClusterUnavailable 503: ClusterUnavailable 503: cluster not found, requeuing
2021/10/14 08:43:14 [ERROR] error syncing 'c-jf2t5/m-d426e9cca313': handler node-controller: ClusterUnavailable 503: ClusterUnavailable 503: cluster not found, requeuing
2021/10/14 08:43:14 [ERROR] error syncing 'c-jf2t5/m-0ee5ab4659cc': handler node-controller: ClusterUnavailable 503: ClusterUnavailable 503: cluster not found, requeuing
2021/10/14 08:43:14 [ERROR] error syncing 'c-jf2t5/m-9b107055cd5c': handler node-controller: ClusterUnavailable 503: ClusterUnavailable 503: cluster not found, requeuing

Same issue here. We tried deleting the cluster while rancher was under heavy load.
No it is stuck.

We've removed finalizers with

k edit clusters.management.cattle.io/c-jf2t5
and the cluster got deleted.
Nevertheless I'm not sure about the side effects.

Thanks. That worked.


Use new enabledFeature param for Analytics

Related to tracker issue:

https://github.com/flutter/flutter/issues/128251

This updates the Analytics constructor to provide it with the enabled features for the flutter-tool. This will be sent with each event for the flutter-tool.
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

LGTM ship it

🎉 , i just need to put out a CL in g3 to update the package first and then should be good to go

@eliasyishak it looks like this was pushed during b/315823847 which was an outage a few days ago. Can you try pushing a new commit to get it picked up again? Thanks!


Filter data by multiple columns values

Let's say I have a table with 2 columns: Age 1 and Age 2.

Now I need to filter rows that have some value in Age 1 or Age 2
https://codesandbox.io/s/muidatatables-custom-toolbar-9n5fq?fontsize=14&hidenavigation=1&theme=dark
I know I can use filterOptions for certain column and use logic(value, filterVal) {..} - but it contains value from current cell. How to get data from other column in my filter?

The way to do this would be to create another column with the values you want to filter on and hide it's display, and then hide the filtering for the two other columns. Example:
const columns = [{name: "Name"}, {name: "Title"}, {name: "Location"},
{
  name: "Age",
  options: {
    filter: false,
  }
}, {
  name:"Age 2",
  options: {
    filter: false,
  }
},
{
  name: "Ages",
  options: {
    display: false,
  }
}];

https://codesandbox.io/s/muidatatables-custom-toolbar-7fvfk?file=/index.js

ref : https://github.com/gregnb/mui-datatables/blob/master/examples/customize-filter/index.js

@wdh2100 i have a similar issue but i am thinking that the best way to do that is extend
column.filterOptions.filterOptions call with row and rowIndex,
i would like to push my branch with changes, how i can get access ?

@andrew-vogulkin

how i can get access ?

Is this means, You want to push your code?
Of course it's possible.
Read the reference below.
thanks,
ref :

https://opensource.com/article/19/7/create-pull-request-github
-https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request

Resolved in version 3.0.1 - a new "rows" field has been added to the logic callback which allows access to all data within the row.


CPP/Metal/CUDA: does not follow HLSL style memory packing with matrixs loaded from 'device' memory

Problem:
//TEST_INPUT:cbuffer(data=[1.0 4.0 7.0  2.0 5.0 8.0  3.0 6.0 9.0]):name colMatrixBuffer
ConstantBuffer<column_major float3x3> colMatrixBuffer;

//TEST_INPUT:cbuffer(data=[1.0 2.0 3.0  4.0 5.0 6.0  7.0 8.0 9.0]):name rowMatrixBuffer
ConstantBuffer<row_major float3x3> rowMatrixBuffer;

For GLSL/HLSL/SPIRV the non default-layout matrix will be loaded into a float3[3]. This is not tightly packed and correct behavior.
Currently CPP/CUDA/Metal load these as tightly packed (different behavior than HLSL)

Closing since this is not a Slang problem, just a test problem.

This is a Slang problem since Slang should not be converting matrix<T,3,3> (tightly packed) into float3 [0]; float3 [1]; float3 [2];  (not tightly packed)

Closed for-now unless the issue becomes a problem

No actionable item here. Closing.


Update gemspec and version number

Forked repo into Drip org
Update gemspec to allow omniauth 1 and 2 in order to update

bump

UPDATE: This PR is unnecessary, as long as bundler can resolve omniauth-oauth2 to v1.7.1


SSL certificate

I think there is a missing self signed certificate as the REST api of Magento does only work when there is a certificate available.
I've added it in the docker file and then it was working

From my experience the rest api worked just fine without ssl, you must ofcourse disable the forced ssl redirect in magento to have this work.

If you have added it, could you show it in a PR? I'm not saying it will be accepted, but it will be more clear what you have done

With the introduction of dockerwest/nginx, https support for all nginx images is now included

how to add https: see https://github.com/dockerwest/nginx/blob/master/README.md#enable-https


PerfectMazeXL

Hi, the PerfectMazeExtraLarge environment  seems to take more than 60 minutes to be evaluated on a nvidia L4 GPU, for 500 episodes.
I was wondering what was the setup used to rollout on such environment and any obstacles you've met ?

setup as in the GPU type


jax.numpy array indexing has different out-of-bounds behavior to numpy

import jax
import jax.numpy as np

x = np.arange(10)
x = jax.device_put(x)
print(x[[13]])

This prints [3], but it should actually throw an out of bounds error like the original NumPy.
P.S.: why does np.arange return a host array? Is this intended behavior or shouldn't it rather behave like np.array and return a device array?

Notably, even non-fancy indexing doesn't raise a bounds error anymore (it wraps instead). Using the example in https://github.com/google/jax/issues/278#issuecomment-457829164:
import jax
import jax.numpy as np

x = np.arange(10)
x = jax.device_put(x)
print(x[13])  # 3

For reference, TensorFlow returns 0 on out-of-bounds indexing: https://www.tensorflow.org/api_docs/python/tf/gather

This has led to a pretty nasty bug for me. This kind of silent failure seems quite dangerous.
I'm not quite sure I understand how checking would be slower since it seems to be that under-the-hood there's some returned_ix = min(ix, len(xs) - 1) calculation happening anyway. Barring that, it would be nice to have a feature analogous to JAX_DEBUG_NANS that would run with standard bounds checking enabled.

See also https://github.com/google/jax/issues/1451.

I'm not quite sure I understand how checking would be slower since it seems to be that under-the-hood there's some returned_ix = min(ix, len(xs) - 1) calculation happening anyway

The problem is that pausing execution to check for errors can be expensive, especially on accelerators, because control flow all happens on the CPU.
Even on CPUs bounds checks can slow things down, e.g., note this guidance from Cython:
https://cython.readthedocs.io/en/latest/src/userguide/numpy_tutorial.html#tuning-indexing-further
That said, I agree that we should absolutely have a debug mode here. And default behavior of returning NaNs for out of bounds indexing results would be safer than silent wrapping.

The problem is that pausing execution to check for errors can be expensive, especially on accelerators, because control flow all happens on the CPU.

This makes sense to me in principle, but I guess I'm not sure how bounds checking ends up being more expensive than returned_ix = min(ix, len(xs) - 1). Aren't they roughly isomorphic? Both end up branching on ix.

That said, I agree that we should absolutely have a debug mode here. And default behavior of returning NaNs for out of bounds indexing results would be safer than silent wrapping.

Totally agree! Hadn't considered returning NaNs.

This makes sense to me in principle, but I guess I'm not sure how bounds checking ends up being more expensive than returned_ix = min(ix, len(xs) - 1). Aren't they roughly isomorphic? Both end up branching on ix.

The most expensive part -- or maybe just a little tricky to do efficiently -- is raising an error back in Python. TensorFlow does this on the CPU but not the GPU, for example.
I  also suspect it may be more efficient for XLA to do silent wrapping since it needs to support negative indices already. Instead of using returned_ix = min(ix, len(xs) - 1) and doing a separate bounds check on returned_ix, it could just use returned_ix = ix % len(xs).

The most expensive part -- or maybe just a little tricky to do efficiently -- is raising an error back in Python. TensorFlow does this on the CPU but not the GPU, for example.

Ah ok, I see what you mean now.

I also suspect it may be more efficient for XLA to do silent wrapping since it needs to support negative indices already. Instead of using returned_ix = min(ix, len(xs) - 1) and doing a separate bounds check on returned_ix, it could just use returned_ix = ix % len(xs).

Yeah this would def make sense. The weird thing is that XLA doesn't seem to do any wrapping. It just returns the last element AFAICT.

Is there a consensus on this yet? The suggestion of a debug mode & documentation would really solve the issue of stumbling into this without realising it, which is what happened to me! Additional runtime nan seems like a good suggestion too, though I admittedly do not know whether it is feasible.

Sorry this has caused problems for you! The out-of-bounds indexing issue is discussed in the documentation here: https://jax.readthedocs.io/en/latest/notebooks/Common_Gotchas_in_JAX.html#out-of-bounds-indexing Do you have suggestions for a better place to surface the issue?
Regarding a runtime warning: that unfortunately is not possible for the same reason that a runtime error cannot be raised; see the discussion at the above link.

You might find jax.experimental.checkify useful for catching OOB checks.

Do you have suggestions for a better place to surface the issue in the docs?

I have many times read Sharp Bits page but I have never noticed OOB section. So, may be it would be better to move it closer to Random Numbers section (e.g. after the section)? It is good place to draw attention since everybody has some issues with RNGs.

You might find jax.experimental.checkify useful for catching OOB checks.

It looks usefull. I'll definitely try. Thanks!


[wayland] window decoration sometime doesn't appear in Weston 8

The window decoration sometimes doesn't appear in Weston 8 even if we use the -d option to show the decorations, but there are no problems with other Wayland compositors. I'm not sure the cause, but https://github.com/sony/flutter-embedded-linux/pull/221 change is affecting it.
Related issues

https://github.com/sony/flutter-embedded-linux/issues/6

Weird, with Weston 9 sometimes the decorations aren't displayed until it detects a mouse movement (haven't tried on touch enabled device with Weston for now).
Once the movement is detected, the decoration buttons show up.
There is slight variance between the decoration strip showing and not but in both cases they appear once there is mouse movement.
Is this the same observation?
https://user-images.githubusercontent.com/3979134/149368076-0cf6f193-0944-46ee-99e3-a8da9a17d2d8.mp4

Thank you for your comment. Yes, it is.

Closing as it seems to work fine on top of master branch.


Adding videos to Voting page

This PR renders vimeo and youtube videos.
Example:

I still recommend testing this out yourself, as a screenshot can't capture all controls.

LGTM.
If you wanted to change the outlined button, I think you'd need to conditionally set background-color: white; opacity: 1; You can also do nested selectors in styled-components – you could convert the top level div in VotePanel to a styled component and then target the outlined button class w/ those styles.


feat: Code review and suggestions

This PR resolves #6

Mailbox is does not do anything special than its uncommon name, so I'd like to suggest rename it to Channel.
Also, Mailbox.send() and Mailbox.join() seem to have different level of abstraction.

Closing stale PR


[Audio] Adds ICustomBufferAudioSource to implement custom audio sources

PR Details
Adds an entry point for custom audio sources.
Description
The basic idea is to use a similar approach as the streaming sources that read files from the disc in blocks but have an endless callback for audio blocks. For this, the user can implement the interface ICustomBufferAudioSource and pass it to the constructor of StreamedBufferSound. This StreamedBuferSound instance will then behave like any Sound instance in Stride.
Example code for playing a sine wave on mouse click:
class MyCustomAudioSource : CustomAudioSourceBase
{
    // Callback from the audio engine
    public override bool ComputeAudioData(AudioData bufferToFill, out bool endOfStream)
    {
        // Create audio data
        GenerateSineWave(bufferToFill.Data);

        bufferToFill.CountDataBytes += BlockSizeInBytes;

        endOfStream = false;
        return true; // success
    }

    public float Frequency = 440f;

    float phase = 0;
    float left, right;
    private void GenerateSineWave(WaveBuffer buffer)
    {

        var channels = Channels;
        var samples = buffer.ShortBufferCount;

        var increment = Frequency / SampleRate;
        for (int i = 0; i < samples; i += channels)
        {
            phase += increment;

            if (phase > 1.0f)
                phase -= 1.0f;

            left = right = (float)Math.Sin(phase * Math.PI * 2);

            buffer.ShortBuffer[i] = (short)(left * short.MaxValue);
            buffer.ShortBuffer[i + 1] = (short)(right * short.MaxValue);
        }
    }
}

public class AudioPlay : AsyncScript
{
    public override async Task Execute()
    {
        // Create custom audio source
        var mySource = new MyCustomAudioSource();

        // Create the sound, spacialized sounds must be mono
        var sound = new StreamedBufferSound(Audio.AudioEngine, mySource, spatialized: false);

        // Create a sound instance
        var soundInstance = sound.CreateInstance();

        // Set the volume
        soundInstance.Volume = 0.0f;

        // Play the sound
        soundInstance.Play();

        while (Game.IsRunning)
        {
            var pressed = Input.IsMouseButtonDown(MouseButton.Left);

            // Turn up volume on mouse down
            soundInstance.Volume = pressed ? 0.5f : 0;

            // Set frequency accoring to mouse y position
            mySource.Frequency = (float)Math.Pow(20000, 1 - Input.MousePosition.Y);

            // Do stuff every new frame
            await Script.NextFrame();
        }
    }
}

Motivation and Context
For a project we require to use the Rapture3D engine from Blue Ripple Sound:
https://www.blueripplesound.com/product-listings/gaming
Types of changes

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

Checklist

[ ] My change requires a change to the documentation.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

I'm also looking for this kind of functionality after struggling a fair bit with DynamicSoundSource - my use case is fairly similar, I would like an audio emitter to play sounds, and I am able to generate into a buffer on demand.
Is there anything that I can do to get this PR across the line? (assuming it works)

Hello @markdchurchill,
Thanks for jumping in and sharing your situation!
I'm pretty happy with how this approach turned out. Although the project that initially needed this ended up going in a different direction, I still think this has potential. It probably needs a bit of testing or a simple proof of concept to show it does the job.
If you're up for it, try merging this branch into your fork and give it a whirl. If it works out for you, that'd be a solid argument to get this PR over the finish line.
I would love to see this feature make it into Stride, and your use case could help push this forward. Let me know how it goes or if you need help setting things up!

Reupped as https://github.com/stride3d/stride/pull/2162

Closing as for the updated: #2162


Add QFSAE logo to the PCB template

Fixes #5

May as well add the logo to the formatting in the schematic sheet too.

Actually don't worry about it, it's a bit more of a job


fix(query): updating with setQueryData should not affect fetchStatus

queries can be fetching while we are making a manual update are still fetching, so we have to set fields that affect the fetch conditionally (fetchStatus, fetchFailureCount)
fixes #3594

@lgenzelis fyi

:tada: This PR is included in version 4.0.0-beta.11 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Question about compressor status

I was looking at the thermostat information coming back from the ISY and had a question or two about it.
First, it is pretty important to know if the compressor in a heat pump or A/C unit is running. Is there a direct way to see this, or would it require us to “learn” this from a number of sources. Is “pending cool” an indication that the unit is set to cool but the compressor is off?  Same question goes for a resistive heating element. I do see a 2nd stage heating. I guess I could assume the resistive unit is in use. Is that correct?
It may seem obvious, but I want to verify I understand your meanings. 😊
{0, "Idle"},
{1, "Heating"},
{2, "Cooling"},
{3, "Fan Only"},
{4, "Pending Heat"},
{5, "Pending Cool"},
{6, "Vent"},
{7, "Aux Heat"},
{8, "2nd Stage Heating"},
{9, "2nd Stage Cooling"},
{10, "2nd Stage Aux Heat"},
{11, "2nd Stage Aux Cooling"},
Thanks,

From: https://www.ecobee.com/home/developer/api/documentation/v1/objects/Thermostat.shtml

The status of all equipment controlled by this Thermostat. Only running equipment is listed in the CSV String.
Values: heatPump, heatPump2, heatPump3, compCool1, compCool2, auxHeat1, auxHeat2, auxHeat3, fan, humidifier, dehumidifier, ventilator, economizer, compHotWater, auxHotWater.
Note: If no equipment is currently running an empty String is returned. If Settings.hasHeatPump is true, heatPump value will be returned for heating, compCool for cooling, and auxHeat for aux heat. If Settings.hasForcedAir or Settings.hasBoiler is true, auxHeat value will be returned for heating and compCool for cooling (heatPump will not show up for heating).

The issue will be how to show this on the ISY since more than one can be running we would need a status for each one.

Currently on the ISY the CLIHCS will be set to 0-8 which correspond to those values:
0 = Idle
1 = Heat
2 = Cool
3 = Heat2
4 = Heat3
5 = Cool2
6 = AuxHeat
7 = AuxHeat2
8 = AuxHeat3
If they show up in the equipementStatus.

I'm not sure what the "Pending" states mean.  Will need to get confirmation from Ecobee.


feat(system-security-plan): initial creation of SSP Model

Description
Implements the OSCALModel interface on an SSP.

Simply the library functions for this PR, follow on addressing the cmd aspect
Additional data is going to be required to fully complete the SSP, in the meantime left "<TODO...>" remarks to try and indicate additional vetting needed on those fields

Related Issue
Fixes #797
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Other (security config, docs update, etc)

Checklist before merging

[ ] Test, docs, adr added or updated as needed
[ ] Schema Updates applied
[ ] Contributor Guide Steps followed

To discuss:
Are we merging validations (via backmatter) into the SSP? Or are we maintaining the original links to the validations and performing a relative path mapping (to get those links properly added to the ImplementedRequirements.ByComponents? IF we want to go that route, we need to re-tool part of the compose functionality to partially compose compdefs (e.g., get the imported ones, re-write the validation/ref relative paths)

To discuss: Are we merging validations (via backmatter) into the SSP? Or are we maintaining the original links to the validations and performing a relative path mapping (to get those links properly added to the ImplementedRequirements.ByComponents? IF we want to go that route, we need to re-tool part of the compose functionality to partially compose compdefs (e.g., get the imported ones, re-write the validation/ref relative paths)

I do think we should discuss this! Do you see this as a blocker for this PR or simply something we should discuss ASAP (next week)?

Do you see this as a blocker for this PR or simply something we should discuss

Yeah mostly just something to discuss - I don't think it's blocking anything here/whatever decision wouldn't invalidate anything done so far.

If possible I would like to see more guidance in PR's for how to review these changes

Agreed! I felt similarly when I was recently reviewing the profile model implementation. I can start a working doc somewhere, maybe Notion for now as we work through a process?

If possible I would like to see more guidance in PR's for how to review these changes

Agreed! I felt similarly when I was recently reviewing the profile model implementation. I can start a working doc somewhere, maybe Notion for now as we work through a process?

Open to anything that helps spread awareness. Some of this can be self-documenting but my request is simply some information in the PR that describes or establishes context for the changes.
This PR touches the SSP OSCAL model - here is associated information to review. This work follows 'x' pattern and you can see linked documentation support the logic. Lula applies opinionation to the use of 'y' field in the SSP type for 'z' reason. etc etc


Implement incomingConnectionToPortNumberFailed native event.

This change is

PR is added to the queue for testing as 2. task. (a169e88)

Hi @dersim-davaod, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

Test (Success) 93986313 build is completed (a169e88)
See https://github.com/ThaliTester/TestResults/tree/93986313a169e88_Implement_incomingConnectionToPortNumberFailed_native_event__dersim-davaod/ for the logs

Test 93986313a169e88(a169e88) has failed
See https://github.com/ThaliTester/TestResults/tree/93986313a169e88_Implement_incomingConnectionToPortNumberFailed_native_event__dersim-davaod/ for the fail logs

@dersim-davaod What do we need to have this PR merged?