The WSL system cannot be started due to memory occupation

Windows Version
Microsoft windows[Version10.0.22621.1992]
WSL Version
<IP_ADDRESS>
Are you using WSL 1 or WSL 2?

[X] WSL 2
[ ] WSL 1

Kernel Version
No response
Distro Version
No response
Other Software
No response
Repro Steps
My WSL system reached 256G of virtual memory, and I shut it down without cleaning up.
Expected Behavior
My WSL system can start normally
Actual Behavior
My WSL system is not starting properly.
My WSL storage is full and can't, but I can't open the WSL to clean up. A deadlock has occurred.
Diagnostic Logs
No response

/dumps


Update Time Series Insights spec with GA features, including Operations.

Highlighted changes:

Add a GA spec
Fix the inheritance problems with EventSourceResource and its properties and parameters. This was based on the changes @mcardosos recently made, but in a way that kept the discriminator on the EventSourceCreateOrUpdateParameters.
Add new GA features, including operations, to both spec.

Changes have been tested by generating a CSharp client using the latest version of autorest.
There are no autorest linter errors.
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[ ] The title of the PR is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[ ] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[ ] If applicable, the PR references the bug/issue that it fixes.
[ ] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[ ] I have read the contribution guidelines.
[ ] My spec meets the review criteria:

[ ] The spec conforms to the Swagger 2.0 specification.
[ ] The spec follows the guidelines described in the Swagger checklist document.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

@olydis My build failed while installing autorest.

The command "npm install -g autorest" failed and exited with 1 during .
Your build has been stopped.

Is there a way to trigger a new build, other than pushing a new commit?
Also, the way I submitted the PR includes the old commits from when we originally added the preview spec. If you want I can try to figure out how to squash the commits and resubmit the PR. But the link in the checklist "For information on cleaning up the commits in your pull request, see this page." is broken.

@ravbhatnagar new features

@ravbhatnagar These are the same features you signed off on earlier this week, + an Operations handler.

@sandshadow indeed, the age of your first commits makes Travis use a super old configuration (that installs an old version of Node.js but then npm i -g autorest will pull in recent AutoRest which requires newer Node...)
So yes, it would be super helpful if you could squash or rebase your PR against current current 🙂

I just realize, you actually opened the PR against master, please retarget against current


Front should be formatted by eslint

As discussed in #28, the official typescript linter is eslint and should be used in place of ng lint

Could be an idea to have the linter of the front-end as a Github action like it is for the backend. It would be consistent at least

job to run the front-end linter has been moved to a github action thanks to #35

Sounds verbose for a GitHub action, isn't there an npm GitHub action that can do
Use npm
Do install, lint
Basta
I'm gonna check when integrating eslint

Yeah you can find something like that. But that's not really an official gh actions. So I prefere like that. Could be a possibility one day to create out own gh action if we think it becomes painful


How to set the bottleneck layer

Hi,
I can't find the bottleneck layer in buildmodel.py. And there is no such setting in the run.py file. How can we set the layer?
Best,
Xu

You should be able to have 'buildmodel.py' construct everything for you.  Or, even more simply, try
python run.py (do python run.py --help for instructions)
If you would like to construct things yourself, there is a bit of a tricky order to it.  I put together a minimalmodel.py to show you how to get off the ground.


When is this package going to be released?

What you are trying to do.
We have upgraded all of our current web application to vue 3 but it heavily depends on bootstrap-vue which is getting less compatible with vue 3 although @vue/compat is supposed to fix this.
Is there any estimated release date for this repository?
Cheers.

There are quite a few releases: https://www.npmjs.com/package/bootstrap-vue-next?activeTab=versions
The repo is now in a weird state, see #2 .
There people (like me) using it in production. I don't think there is a clear plan what constitutes as a stable release at the moment.

Yes we are hoping this can be solved swiftly as well. Sounds like @VividLemon has been working hard making several improvements, but a repo was deleted.


Update IfCaseLet.swift

I was browsing this file and noticed that, from the looks of it, ElseContent is never actually used in the body? 😱😅

(We're obviously working in TCA way more often 🤣)


Adding Javascript Voice generator from the text.

Develop a Javascript {Voice Generator} app.
Description 📜
This voice generator project will provide the different voices for different countries on providing the specific text.
Requirements 🛠
HTML, CSS, JS
Bonuses ✨

Add tasks that are challenging.
App can have this thing.
Developers can also add this to the app.
It will be great if App has this.

Any number of people can work on a single issue 👨💻👨💻
This issue is open to all.🌍

Project location 👉🏻 {AppName}/Username/
👨🏻💻 Happy Coding 👩🏻💻

Can i work on this project.

Sure @Sahil-K123


Fix bug where editing and original recurring event disappears whenever it clashes with pre-existing recurring events

LGTM! Bug spotted !

Great bug spotted! LGTM


[FEATURE] GitOps approach to create Grafana Datasource and Grafana Dashboards on AMG.

Is your feature request related to a problem? Please describe
We can benefit from a GitOps approach to create Grafana Datasource and Grafana Dashboards from GitOps repo on remote AMG. We can also think about deploying Grafana Operator to achieve this.
Describe the solution you'd like
A GitOps approach to create Grafana Datasource and Grafana Dashboards from GitOps repo on remote AMG.  This will help customers to manage a Single repo to create Dashboards on same kind across multiple clusters. This Decouples the Grafana Dashboard work for Ops Personas from Cloud Infra personas who creates this accelarator infrastructure. Using GitOps approach helps customers who wants to run 100s and 1000s of clusters to create Grafana Dashs.
Describe alternatives you've considered
Grafana Operator
Additional context
https://github.com/grafana-operator/grafana-operator

Commenting to keep the ticket active.

Hello. Please keep this ticket open. This is an important feature we are working on for.

Commenting to keep the ticket active.

@elamaran11 Will extend the duration of closing tickets as some items like this one are planned to be done

This is not fuly complete. We still need to complete V2 which is GitOps repo to create Grafana Dashboards

Closing as per #151


Bug Report: Vulkan Renderers don't set debug names on resources

Describe the bug
Before the vulkan frontend was rewritten months ago, it used to have very good coverage of VK_EXT_debug_utils. The new frontend does a decent job, but it does not mark resources (i.e buffers and images) with debug names, making it very difficult to track these resources in renderdoc.
Reproduction

Repros On: tz_triangle_demo
Repro Type: unexpected behaviour
Repro Rate: every time
Repro Severity (how badly does it affect your bottom line): very little
Repro Steps
Steps to reproduce the bug:

Open up RenderDoc
Build tz_triangle_demo on vulkan-debug
Run tz_triangle_demo under renderdoc.
Take a capture
View the resource inspector (Window -> Resource Inspector)
See that buffers and images that belong to renderers are poorly named (e.g Buffer 298). Run the opengl-debug version of tz_triangle_demo to see much better debug naming (e.g Dbgui Renderer:B1)

Expected behavior
DEBUG NAMES PLS
Screenshots
tz_triangle_demo-vulkan_debug

tz_triangle_demo-opengl_debug

Conditions (please complete the following information):

OS: windows
Render API: vulkan
Build Config: debug
Version: master
Compiler: clang

Fixed in cc0a779a93619e964725a808a5c35d5d9fa20782


upgrade from antlr3 to antlr4

So some files don't add licenses, please add.

change your title like '[IOTDB-xxx] upgrade from antlr3 to antlr4', which xxx is your issue id on jira so that jira can track this issue

https://github.com/apache/incubator-iotdb/pull/564


The non-standard image naming format cannot download the image, causing the rancher offline installation to fail

What kind of request is this (question/bug/enhancement/feature request):
question
Steps to reproduce (least amount of steps as possible):
Offline installation according to Air Gap Install.
Result:
Cannot download image, causing the rancher offline installation to fail
The standard image name format should be:<repository.yourdomain.com:port>/<project>/<image_name>:<tag>, some  images repository (such as: harbor) will be checked according to this standard, Images that do not match the standard cannot be uploaded or downloaded.
If an image is stored in the dockerhub library project, you can omit the repository address and project name and write only the image name, such as: busybox.
When installing the K8S cluster offline, a private images repository address is automatically added at the beginning of the image to download.
If you need to download the image for busybox, automatically add the private images repository address will be: <repository.yourdomain.com: port>/busybox. This is not a standard image naming format, so the image cannot be downloaded.
Environment information

Rancher version:
rancher/rancher:v2.1.x

Installation option :
HA

@orangedeng @superseb

To me, this impllies that our air gap installation doesnt work at all, but we've tested and verified that it does. What am I missing? What is different about the scenario being described ehre?

@cjellick It only happens when user is using Harbor as registry.
busybox will be changed to repository.yourdomain.com/busybox in the air gap setup.
But in Harbor users cannot drop the library field. Harbor users have to use repository.yourdomain.com/library/busybox.


Ability to authenticate with config profiles or custom session credentials

Correct me if i am wrong but the only way of authenticating with control tower and other services is by a role arn which then uses your configured default aws profile to assume the role. It would be great to have other methods of authenticating with these services like config profiles and even custom session credentials. ex : {"sessionId": "", "sessionKey": "", "sessionToken": ""}

Hi @Tochey , thanks for this message. Control tower does not expose an official API yet and that is the whole point of this library, to provide an api. That means that the way to authenticate with control tower is to piggyback on the web front end authentication so our only option is roles that can be assumed by the logged in user with his/hers/theirs credentials. I hope this makes sense. If I misunderstood something please let me know.

Does ControlTower have to assume a role to work with the internal API? Is there some reason it can't use the default Session()?
I log into my management account using the AWSAdministratorAccess role generated by Identity Center.
When I try to use the ARN of that role, I get an InvalidCredentials error.
tower = ControlTower("arn:aws:iam::111111111111:role/aws-reserved/sso.amazonaws.com/AWSReservedSSO_AWSAdministratorAccess_aaaaaaaaaaaaaaaa")

InvalidCredentials: An error occurred (AccessDenied) when calling the AssumeRole operation: User: arn:aws:iam::111111111111:role/aws-reserved/sso.amazonaws.com/AWSReservedSSO_AWSAdministratorAccess_aaaaaaaaaaaaaaaa/... is not authorized to perform: sts:AssumeRole on resource: arn:aws:iam::111111111111:role/aws-reserved/sso.amazonaws.com/AWSReservedSSO_AWSAdministratorAccess_aaaaaaaaaaaaaaaa

That makes sense because the role cannot assume itself. But I don't understand why a new role assumption is necessary.
The workaround for now is to create an extra stack in my management account with a role whose trust policy allows it to be assumed by the AWSAdministratorAccess role. The template may look like this:
  AwsApiLibRole:
      Type: AWS::IAM::Role
      Properties:
        RoleName: AwsApiLib
        AssumeRolePolicyDocument:
          Version: "2012-10-17"
          Statement:
            - Effect: Allow
              Principal:
                AWS: arn:aws:iam::111111111111:role/aws-reserved/sso.amazonaws.com/AWSReservedSSO_AWSAdministratorAccess_aaaaaaaaaaaaaaaa)
              Action: sts:AssumeRole
        ManagedPolicyArns:
          - "arn:aws:iam::aws:policy/AdministratorAccess"

When that resource is created I can use the ControlTower class like this:
tower = ControlTower("arn:aws:iam::111111111111:role/AwsApiLib")

But as @Tochey says it would be more convenient to use the existing session.


Chrome Headless doesn't work with Google Maps 3D or Google Earth - "Google Earth isn't supported in your browser"

Steps to reproduce
Tell us about your environment:

Puppeteer version: 0.11.0
Platform / OS version: Ubuntu 14.04.5 LTS
URLs (if applicable):
https://www.google.co.uk/maps/@51.6506889,-0.4041839,40a,35y,113.57h,73.36t/data=!3m1!1e3
https://earth.google.com/web/@51.6499525,-0.40162489,64.98644774a,251.31324967d,35y,111.968

What steps will reproduce the problem?
const puppeteer = require('puppeteer');

async function run() {
    const browser = await puppeteer.launch();
    const page = await browser.newPage();

    await page.setViewport({width:2880, height:1800});
    await page.goto('https://www.google.co.uk/maps/@51.5516152,0.7010375,66a,35y,170.86h,79.21t/data=!3m1!1e3', {"waitUntil" : "networkidle"});
    await page.screenshot({ path: './example-2d.png' });

    browser.close();
}

run();

What is the expected result?
I expect the result to render the same way as it does in the Chrome Browser for desktop.
What happens instead?
For the google maps link it renders in 2D rather than 3D.
For google earth an error message is given:

Aw Snap! The new Google Earth isn't supported by your browser yet. Try this link in Chrome instead. If you don't have Chrome installed, download it here

I got the 3d version on Mac. Since Puppeteer uses--disable-gpu by default, I wonder if that affects the 3d webgl version of maps on Linux.

Ah that may be it, I may have been using disable-gpu from the command line out of habit as well, I'll try it again

Closing in favor of https://stackoverflow.com/questions/46343607/chrome-headless-doesnt-work-with-google-maps-3d-or-google-earth


Set ulimit to recommended values

Currently the MongoDB image doesn't change the default ulimit values, what is not ideal for production deployments.
https://docs.mongodb.com/manual/reference/ulimit/

@hhorak @praiskup @pkubatrh Does setting limits also apply to MariaDB/PostgreSQL? Is it somehow handled in RHSCL images?

Ulimits on RHEL/Fedora systems are usually generous enough by default (at least from PostgreSQL POV).

Roughly tried to run ulimit on my box, and it seems that from mongo perspective only the max number of opened file descriptor issue (default is 1024, so far I haven't seen different different default, while mongo suggest to have 64k, which sounds crazy TBH).

Btw., there seems to be soft limit of 4096 simultaneously opened file descriptors per process on my box.  I've seen some weird scenarios (GNU tar archives very deep directory structure) where the default 1024 limit is approached .. but I'm curious whether this is really an issue in case of mongodb and why.

Not sure if it good, but it seems that limits are not set in a image, but are related to host machine. So it may differ on every machine...
It is possible to set defaults in docker daemon by using --default-ulimit ("If these defaults are not set, ulimit settings will be inherited, if not set on docker run, from the Docker daemon." - https://docs.docker.com/engine/reference/commandline/dockerd/).
In case that other database images are not setting this, using defaults from docker daemon seems enough IMPOV.

Although the fix is relatively simple, I would let setting of limits to the user (when invoking docker run or centrally to docker daemon). So closing this issue now. It could be fixed when this decision cause any problem to someone.
Proposed fix:
diff --git a/3.2/root/usr/bin/run-mongod b/3.2/root/usr/bin/run-mongod
index 2814661..96cca13 100755
--- a/3.2/root/usr/bin/run-mongod
+++ b/3.2/root/usr/bin/run-mongod
@@ -68,4 +68,5 @@ wait_for_mongo_down

 # Make sure env variables don't propagate to mongod process.
 unset MONGODB_USER MONGODB_PASSWORD MONGODB_DATABASE MONGODB_ADMIN_PASSWORD
+setup_soft_limits
 exec mongod $mongo_common_args --auth
diff --git a/3.2/root/usr/bin/run-mongod-replication b/3.2/root/usr/bin/run-mongod-replication
index 7c86615..31e1a3c 100755
--- a/3.2/root/usr/bin/run-mongod-replication
+++ b/3.2/root/usr/bin/run-mongod-replication
@@ -69,5 +69,6 @@ ${CONTAINER_SCRIPTS_PATH}/init-replset.sh &

 # Make sure env variables don't propagate to mongod process.
 unset MONGODB_USER MONGODB_PASSWORD MONGODB_DATABASE MONGODB_ADMIN_PASSWORD
-mongod ${mongo_common_args} --replSet "${MONGODB_REPLICA_NAME}" &
+(setup_soft_limits;
+mongod ${mongo_common_args} --replSet "${MONGODB_REPLICA_NAME}") &
 wait
diff --git a/3.2/root/usr/share/container-scripts/mongodb/common.sh b/3.2/root/usr/share/container-scripts/mongodb/common.sh
index 4d35a0d..b023d9d 100644
--- a/3.2/root/usr/share/container-scripts/mongodb/common.sh
+++ b/3.2/root/usr/share/container-scripts/mongodb/common.sh
@@ -177,6 +177,14 @@ function setup_default_datadir() {
   fi
 }

+# setup_soft_limits sets soft limits to maximum (hard limit)
+function setup_soft_limits() {
+  info "Setting soft limits to maximum"
+  for x in c d e f i l m n q r s t u v x; do
+    ulimit -S${x} $(ulimit -H${x})
+  done
+}
+
 # info prints a message prefixed by date and time.
 function info() {
   printf "=> [%s] %s\n" "$(date +'%a %b %d %T')" "$*"


Tws scramble

I think I've addressed all your comments.
I'm running one sample with deletions on just to make sure that I haven't messed that up in Scramble.wdl.  If that's successful, I think we might be ready to merge pending additional comments.


Fix Ci integration tests

Fixes https://github.com/PaulRBerg/create-eth-app/issues/238

integration tests were failing because GitHub was blocking the HEAD requests with 403 error

Adding a User-Agent header unblocks it.

replace url-exist library with inbuilt nodejs https module

$ yarn test:integration
 PASS  test/integration/frameworks.test.ts (7.269 s)
 PASS  test/integration/templates.test.ts (33.703 s)

Test Suites: 2 passed, 2 total
Tests:       35 passed, 35 total
Snapshots:   0 total
Time:        33.87 s
Ran all test suites matching /test\/integration/i.

@PaulRBerg Have reverted the type change. Please review again.


refactor(android): migrate VideoDecoderPropertiesModule to Kotlin

Summary
refactor(android): migrate VideoDecoderPropertiesModule to Kotlin
Motivation
Changes
Test plan

@freeboub @KrzysztofMoch
I made a mistake with this PR
I've created correction PR #3959


feat: profile page & chore: referral code Text in form

Your checklist for this pull request
🚨Please review the guidelines for contributing to this repository.

[ ] Make sure you are requesting to pull a topic/feature/bugfix branch (right side). Don't request your default branch!
[ ] Make sure you are making a pull request against the default branch (left side). Also you should start your branch off default branch.
[ ] Check the commit's or even all commits' message styles matches our requested structure.
[ ] Check your code additions will fail neither code linting checks nor unit test.
[ ] I have added necessary documentation (if appropriate)

Description
Added Profile Page
Changed Referred by text to Referral Code
Update Guest Lecture Heading
Updated Workshop Name
❤Thank you!
Post merge checklist

[ ] Follow steps from the guidelines for contributing to this repository.
[ ] If you are a new contributor, ping in the thread and one of the maintainers will add you to all-contributors list.

@ORKO06 @riteshsp2000 is it still required?

@ORKO06 closing this due to staleness.


Failed to load SDF from URL

trying the server auto reload setup on mac os.
I just get to see the standard cube

 ./bin/sdf-viewer app url http://localhost:8080/foo.wasm
2024-11-25T21:59:06.778099Z  INFO sdf_viewer::metadata: sdf-viewer 1.5.3 (@)
2024-11-25T21:59:06.778181Z  INFO sdf_viewer::metadata: Build date: Mon, 25 Nov 2024 16:58:32 -0500 (debug)
2024-11-25T21:59:06.779499Z  INFO sdf_viewer::run: Arguments: Cli { command: App(CliApp { sdf_provider: Url(CliAppWatchUrl { url: "http://localhost:8080/foo.wasm" }) }) }
2024-11-25T21:59:06.906808Z  INFO new: sdf_viewer::app: Initialization complete! Starting main loop...
2024-11-25T21:59:06.907399Z  INFO new: sdf_viewer::app::scene::sdf: Using 64x64x64 voxels (dimensions: 2x2x2)
2024-11-25T21:59:07.100312Z  INFO sdf_viewer::app::scene: Loaded SDF chunk (167274 updates) in 30.004125ms (CPU) + 601.584µs (GPU)
2024-11-25T21:59:07.148606Z  INFO sdf_viewer::app::scene: Loaded SDF chunk (127638 updates) in 23.0035ms (CPU) + skipped (GPU)
2024-11-25 16:59:07.174 sdf-viewer[85906:21656739] +[IMKClient subclass]: chose IMKClient_Legacy
2024-11-25 16:59:07.174 sdf-viewer[85906:21656739] +[IMKInputSession subclass]: chose IMKInputSession_Legacy
2024-11-25T21:59:07.187601Z  INFO sdf_viewer::app::scene: Loaded last SDF chunk in 3.375µs (GPU)
2024-11-25T21:59:13.750538Z  INFO sdf_viewer::sdf::wasm::load: Server supports watching for file changes, enabling continuous updates.
2024-11-25T21:59:23.550146Z ERROR sdf_viewer::sdf::wasm::load: Failed to load SDF from URL (Error while importing "wasi_snapshot_preview1"."proc_exit": incompatible import type. Expected Function(FunctionType { params: [I32], results: [] }) but received Function(FunctionType { params: [I32], results: [I32] })) or file (No such file or directory (os error 2))

attached version info
buildAndRun.zip
version.zip

I think this is caused by the main method containing any code. as soon as i comment the code out it works, uncomment makes it fail again.

When there is any error loading the SDF, the default cube is shown. This is a bad fallback, but it was easier than showing an error :sweat_smile:.
The error was that my fake WASI API had a wrong function signature. This was a really hacky solution since I couldn't find a good WASI crate at the time. It should be fixed now (released in v1.2.2), but this new WASI crate will likely need some more testing.
Thanks for opening the issue!


Josh Mancuso- Sprint2: Data Wrangling

Assignment 1 looks great! Nice work with commenting your code. All the parts look like they were completed. Feel free to do stretch goals with different data if you want/need further challenge.

Outstanding work on the daily assignments this week. Your code and comments are fantastic and you completed the sprint challenges very well. I am excited to see what you do in the coming weeks. Your work is wonderful. Keep it up!

Excellent work on the Sprint Challenge. All parts were completed successfully with proper output. Your code is well written. I would suggest additional comments within your code to help others follow your process. Outstanding work this week!


Show inside a container

I would to show the toast inside a container, and not in a floating position inside the page. Is it possible?

Can you please a more concrete example of what you'd like to be able to do?

For example, I want to show the alert upon a form, so not show it in the middle/top/bottom of the page but in a specific position.

@matzrm you could in theory embed a toast container directly in your form, although you'd then need to add positioning overrides to force it into the right location.  This level of customization probably wouldn't be driven by the library itself (since it isn't a common ask and it largely depends on the needs of the consumer) but it absolutely could be done by you if you styled it as such.


🐞 entrypoint evaluated when calling with_exec

What is the issue?
Consider the following example
dag.container().from_("registry.dagger.io/engine:v0.9.6").with_exec(["apk", "add", "--no-cache", "nodejs"])

This example errors with:
218: exec dagger-entrypoint.sh apk add --no-cache nodejs npm
218: [0.06s] mkdir: can't create directory '/sys/fs/cgroup/init': Read-only file system
218: exec dagger-entrypoint.sh apk add --no-cache nodejs npm ERROR: process "dagger-entrypoint.sh apk add --no-cache nodejs npm" did not complete successfully: exit code: 1

Note the usage of the entrypoint. This is different from Docker's default behaviour of using the entrypoint only when running, but not when building containers.
Dagger version
dagger v0.9.6 (registry.dagger.io/engine) darwin/arm64
Steps to reproduce
No response
Log output
No response

Closing. Wasn't aware of skip_entrypoint parameter.


Support for change back to AU915 in Australia

This firmware does not support the rollback to AU915 in Australia which was successfully voted and implemented around 17 April 2023. My rockpi hotspot is only sending beacons which are not being witnessed and is not witnessing other beacons. When will the firmware be updated to support this change on the network?

Our hotspots have always supported this frequency plan and still do.
You may need to go into your hotspot local diagnostics and do a factory reset from the "Device Configuration" menu by clicking on "Reset to Factory Defaults"

Hi
Thanks for your email on this. I understand there was recently a vote to
revert back to AU915 following the change to the AS923_1C dual plan. Can
you confirm my hotspot and curret firmware support the change back to AU915?
My hotspot stopped receiving rewards since the change and is only sending
beacons with no witnesses (no issues previously). There are many people in
Australia having similar issues right now.
In the mean time I have done the reset to factory defaults but your advice
on the above would be appreciated.
Regards
Chris
On Thu, 4 May 2023, 9:36 am Aaron Shaw, @.***> wrote:

Our hotspots have always supported this frequency plan and still do.
You may need to go into your hotspot local diagnostics and do a factory
reset from the "Device Configuration" menu by clicking on "Reset to Factory
Defaults"
—
Reply to this email directly, view it on GitHub
https://github.com/NebraLtd/helium-nebra-indoor1/issues/1#issuecomment-1533882573,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATWAPHDJULWAQAQAA7IDYLTXELTXLANCNFSM6AAAAAAXQWVOG4
.
You are receiving this because you authored the thread.Message ID:
@.***>

Yes AU915 has always worked on our devices and still does.
You can see the relevant code here... https://github.com/NebraLtd/hm-pktfwd/blob/master/pktfwd/config/lora_templates_sx1301/global_conf.json.AU915_SB2
As long as your device is showing region AU915 on the diagnostics page then everything is working fine.
This region band is pulled automatically from helium gateway-rs software which in turn grabs this from the oracles which base it on the location assert. So it's not something we have direct control over - the region band name is just pulled down directly from there.

Thanks for confirming that. Nothing about my setup has changed. I did a
reset to factory defaults but have since sent a beacon with no witnesses.
Can you think of any reason why I am not being witnessed nor witnessing
since last week? Previously no issues with regular rewards.
Regards
Chris
On Thu, 4 May 2023, 2:29 pm Aaron Shaw, @.***> wrote:

Yes AU915 has always worked on our devices and still does.
You can see the relevant code here...
https://github.com/NebraLtd/hm-pktfwd/blob/master/pktfwd/config/lora_templates_sx1301/global_conf.json.AU915_SB2
As long as your device is showing region AU915 on the diagnostics page
then everything is working fine.
This region band is pulled automatically from helium gateway-rs software
which in turn grabs this from the oracles which base it on the location
assert. So it's not something we have direct control over - the region band
name is just pulled down directly from there.
—
Reply to this email directly, view it on GitHub
https://github.com/NebraLtd/helium-nebra-indoor1/issues/1#issuecomment-1534081517,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATWAPHDQSPWOOH3NTYFQVLLXEMWBFANCNFSM6AAAAAAXQWVOG4
.
You are receiving this because you authored the thread.Message ID:
@.***>

Yes it says region plan AU915.  All the hotspots around me are still receiving rewards so it’s a problem with my hotspot it seems.
From: Aaron Shaw @.>
Sent: Friday, May 5, 2023 1:43 AM
To: NebraLtd/helium-nebra-indoor1 @.>
Cc: Psych101 @.>; Author @.>
Subject: Re: [NebraLtd/helium-nebra-indoor1] Support for change back to AU915 in Australia (Issue #1)
Might be other hotspots being on the wrong frequency nearby.
If it says au915 on your one, then it's correct
Easiest way to test is with an au915 sensor
—
Reply to this email directly, view it on GitHub https://github.com/NebraLtd/helium-nebra-indoor1/issues/1#issuecomment-1535006391 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ATWAPHCUARBY5ZZA7UI4KELXEPFBBANCNFSM6AAAAAAXQWVOG4 .
You are receiving this because you authored the thread.  https://github.com/notifications/beacon/ATWAPHEGCCTHHDSWXZS6DUDXEPFBBA5CNFSM6AAAAAAXQWVOG6WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS3PZLLO.gif Message ID: @.*** @.***> >

Check all the antenna connections

Hi
My hotspot just started witnessing after receiving the new firmware v1.0.2-9 a couple of hours ago.  It seems it was a firmware issue after all.  What was the change in the firmware to correct the issue?
Regards
Chris
From: Aaron Shaw @.>
Sent: Friday, May 5, 2023 8:32 AM
To: NebraLtd/helium-nebra-indoor1 @.>
Cc: Psych101 @.>; Author @.>
Subject: Re: [NebraLtd/helium-nebra-indoor1] Support for change back to AU915 in Australia (Issue #1)
Check all the antenna connections
—
Reply to this email directly, view it on GitHub https://github.com/NebraLtd/helium-nebra-indoor1/issues/1#issuecomment-1535490085 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ATWAPHAM3RUTCFENUJLX273XEQU5VANCNFSM6AAAAAAXQWVOG4 .
You are receiving this because you authored the thread.  https://github.com/notifications/beacon/ATWAPHDEYXFWK6P3R2NGINDXEQU5VA5CNFSM6AAAAAAXQWVOG6WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS3QW4CK.gif Message ID: @.*** @.***> >

@Psych101 the was no change on the packet forwarder or miner

The only other change is that I rebooted but I had already tried that
several times in the past.
On Wed, 10 May 2023, 3:10 am Aaron Shaw, @.***> wrote:

@Psych101 https://github.com/Psych101 the was no change on the packet
forwarder or miner
—
Reply to this email directly, view it on GitHub
https://github.com/NebraLtd/helium-nebra-indoor1/issues/1#issuecomment-1540557025,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATWAPHAN7XLU6DRJG3ZTKGLXFJ3CBANCNFSM6AAAAAAXQWVOG4
.
You are receiving this because you were mentioned.Message ID:
@.***>


fix(agent): additional MQTT entity to allow screen locking via screensaver for different desktops

As stated in https://github.com/joshuar/go-hass-agent/issues/74#issuecomment-1918028522 I have some issues with the MQTT screen locking. Therefore I added an additional MQTT entity which allows locking using another mechanism, based on the screensaver. I build this for cinnamon, gnome and KDE but I have only tested the first one. The other ones I have implemented based on the information I found on the internet, so theoretically they should work as well.
I am aware this is mainly a workaround when screen locking with the designated session based mechanism does not work which may only be the case with my system setup. So I totally understand if you decide not to merge it due to being to specific :smiley: .

Hey @jaynis this looks good. I was hoping to avoid needing to use any kind of desktop-specific D-Bus methods for this but I think your approach is the right one for now. I've found it difficult to understand if there is a single canonical path/destination/method for screen unlocking; I was helping another user previously with getting screen locking working and we had to do a lot of digging to try to find something that worked for both of our distributions and setups.
I think we go with this approach and then, if we find a single way that works for everyone, we can always move to that.
Thanks again for your contribution! :handshake: :tada:
PS. I've changed the title to follow a conventional commit pattern which is the style I've been using for this project and will ensure this change appears in the auto-generated changelog.

Thank you for merging this!
I think distro / desktop environment peculiarities will always be a problem when implementing such kind of features as you already have described. Therefore I think what would be additionally cool to have is a MQTT topic where arbitrary messages could be dispatched to each specifying the dbus method, path and so. That would be the most generic approach and new functionalities could be easily tried out with home assistants mqtt.publish service without any code changes. Ultimately a dedicated go_hass_agent.dbus_call action could be implemented wrapping the MQTT request into something more specific. The only downside I see here is the security impact e.g. someone with access to the MQTT broker potentially gains wide privileges over the system where the hass agent runs on. Therefore it might be beneficial to make the user opt-in to such a feature on the hass agents UI.
Do you mind if I create a proposal issue for that?

Hey @jaynis that's an interesting idea. So Go Hass Agent would listen on an MQTT topic and you'd issue a MQTT publish msg from Home Assistant to the topic, that contains a D-Bus destination/path/method to action something on the device running Go Hass Agent? I think that would certainly be useful for advanced users. It could be interesting to see how much of a device could be automated this way. If you wanted to look into it, go for it! Happy for an issue to be created about this.
Agreed on the security aspect. I've written a little bit about the security implications of enabling the existing MQTT functionality here. No doubt it could be rewritten and/or expanded for any new features like this proposal.


update abstracttrees compat

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.7%) to 63.226%

Totals

Change from base Build<PHONE_NUMBER>:
-0.7%

Covered Lines:
98

Relevant Lines:
155

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 63.924%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
101

Relevant Lines:
158

💛  - Coveralls


BluetoothClient.Connect works but BluetoothClient.ConnectAsync does not

// This line runs without fail
await Task.Run(() => _client.Connect(_deviceInfo.DeviceAddress, _serviceClassId));
// When replacing above line with this, the code throws the exception: System.Net.Sockets.SocketException: 'An invalid argument was supplied.'
await _client.ConnectAsync(_deviceInfo.DeviceAddress, _serviceClassId);
Is this a bug in ConnectAsync method?

What platform is this on please?

Windows 11, x64, Version: 22H2
btw: Thank you so much for your work and open sourcing this project to the community.

I also see the same problem on my Windows 11 device, using ConnectAsync or BeginConnect/EndConnect (crashes on the EndConnect with the same error as above).  I am coding under Maui, .Net 7.0.


performance: reduce and test size of futures

Prior to this PR, each outbound connection future was 22k. This is
really big.
The reason behind this is how Rust sizes Futures; the stack size is
allocated based on the maximum required size through any branch. This
means even obscure code paths can bloat up the entire future for
everyone.
 This is done in a few ways:

Box::pin expensive futures. While we have to allocate these when we
hit them, of course, when we don't hit these codepaths they are now
"free". We have a lot of uncommon expensive code paths. Especially HBONE
vs passthrough; hbone is way more expensive. But also on demand XDS,
DNS, etc
Arc the Config which is large
A variety of other micro-optimizations

A new assertions module is added to verify we do not regress.
Spawning 10k connections before this PR used about 660Mb, now we are at 300mb

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

test_ztunnel
b66b0e8c2ee0d2dca7685b377c9d6cc8bacfa52d
link
true
/test test

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

Hyper bug is fixed, this is ready to go

In response to a cherrypick label: new pull request created: #989


Makes changes for lint msgs issue #507 - FMRS_MA_2018.js

@knod oh you're right actually, I agree.

@ethanbb  I made the change.

@ethanstrominger : btw, you can have a different commit message for subsequent commits. Something that's descriptive about that specific commit.


Image compression doc fix

Description
This PR fixes a very minor issue with the tutorial for the new image compression control sample. Due to a wrong order at the top of the file, the caption rendered wrong:

This PR fixes this by adjusting the ordering in the tutorial to be in line with the other tutorials.
Note: This is a pure documentation fix
General Checklist:
Please ensure the following points are checked:

[ ] My code follows the coding style
[ ] I have reviewed file licenses
[ ] I have commented any added functions (in line with Doxygen)
[ ] I have commented any code that could be hard to understand
[ ] My changes do not add any new compiler warnings
[ ] My changes do not add any new validation layer errors or warnings
[ ] I have used existing framework/helper functions where possible
[ ] My changes do not add any regressions
[ ] I have tested every sample to ensure everything runs correctly
[ ] This PR describes the scope and expected impact of the changes I am making

Note: The Samples CI runs a number of checks including:

[ ] I have updated the header Copyright to reflect the current year (CI build will fail if Copyright is out of date)
[ ] My changes build on Windows, Linux, macOS and Android. Otherwise I have documented any exceptions

Closing this, see Jon's PR #999


windows: fix version detection when multiple gem is installed

In the previous version, installed multiple version is not
handled correctly, so only last version is detected correctly.
Before:
If rake (13.0.3, 13.0.1) then, FindInstalledGem("rake", "13.0.3")
returns False because ["13.0.3,", "13.0.1"].Contains("13.0.3") is
checked.
After:
If rake (13.0.3, 13.0.1) then, FindInstalledGem("rake", "13.0.3")
returns True because ["13.0.3", "13.0.1"].Contains("13.0.3") is
checked.

Thanks!

Thanks!

Released as v2.82.23.

Released as v2.82.23.


cross entropy kernel: inplace modification of input

Hello,
Regarding inplace modification of PyTorch tensors, there are already multiple (#254, #262, #272) issues. I would also like to point out that according to PyTorch docs for mark_dirty():
Every tensor that’s been modified in-place in a call to forward() should be given to this function, to ensure correctness of our checks

So can you please look into it and come up with a resolution? :-)
Now I noticed another thing.
Since currently gradient is being calculated during forward pass, during backward pass, if grad of loss w.r.t. cross entropy output is 1.0, no calculation is done and only the grad calculated during the forward pass is returned. However, just doing that seems to make backward pass take almost the same time as the forward pass. I do not understand why that would be so.
I profiled both forward and backward passes using Triton's proton profiler with the following script:
import torch
# from torch.nn import CrossEntropyLoss as TorchCrossEntropyLoss

from liger_kernel.transformers.cross_entropy import LigerCrossEntropyLoss

import triton.profiler as proton

device = 'cpu'
if torch.cuda.is_available():
    device = 'cuda'
elif torch.xpu.is_available():
    device = 'xpu'
else:
    print('No accelerator available, running on CPU')

def run():
    # Create Tensors to hold input and outputs.
    with proton.scope("0-init"):
        V = 131072
        B = 8
        T = 2048

        _input = torch.randn(B * T, V, requires_grad=True, device=device)
        target = torch.randint(V, (B * T, 1), device=device).squeeze(1)

        # layer = TorchCrossEntropyLoss()
        layer = LigerCrossEntropyLoss()

    with proton.scope("1-warmup"):
        for _ in range(10):
            y = layer(_input, target)
            y.backward(retain_graph=True)

    for _ in range(100):
        # Forward pass:
        with proton.scope("2-forward"):
            y = layer(_input, target)

        # Backward pass:
        with proton.scope("3-backward"):
            y.backward(retain_graph=True)

func = proton.profile(run, name="cross_entropy", context='shadow')
func()

# Write out the profile
# Visualize using `proton-viewer -m time/ms ./cross_entropy.hatchet`
proton.finalize()

Below is the time breakdown among different kernels:
3361.863 ROOT
├─ 8.295 0-init
│  ├─ 8.292 _ZN2at6native54_GLOBAL__N__d8ceb000_21_DistributionNormal_cu_0c5b6e8543distribution_elementwise_grid_stride_kernelIfLi4EZNS0_9templates4cuda20normal_and_transformIffPNS_17CUDAGeneratorImplEZZZNS4_13normal_kernelIS7_EEvRKNS_10TensorBaseEddT_ENKUlvE_clEvENKUlvE0_clEvEUlfE_EEvRNS_18TensorIteratorBaseET1_T2_EUlP24curandStatePhilox4_32_10E0_ZNS1_27distribution_nullary_kernelIff6float4S7_SM_SF_EEvSH_SJ_RKT3_T4_EUlifE_EEviNS_15PhiloxCudaStateESI_SJ_
│  └─ 0.003 _ZN2at6native60_GLOBAL__N__2b2da9da_27_DistributionRandomKernel_cu_f88cee4443distribution_elementwise_grid_stride_kernelIjLi4EZZZNS0_9templates4cuda21random_from_to_kernelIPNS_17CUDAGeneratorImplEEEvRNS_18TensorIteratorBaseEmlT_ENKUlvE_clEvENKUlvE2_clEvEUlP24curandStatePhilox4_32_10E0_ZNS1_27distribution_nullary_kernelIlj5uint4S7_SF_ZZZS5_IS7_EvS9_mlSA_ENKSB_clEvENKSC_clEvEUljE_EEvS9_T2_RKT3_T4_EUlijE_EEviNS_15PhiloxCudaStateET1_SJ_
├─ 291.116 1-warmup
│  ├─ 0.087 _ZN2at6native13reduce_kernelILi512ELi1ENS0_8ReduceOpIfNS0_14func_wrapper_tIfZNS0_11sum_functorIfffEclERNS_14TensorIteratorEEUlffE_EEjfLi4EEEEEvT1_
│  ├─ 0.058 _ZN2at6native13reduce_kernelILi512ELi1ENS0_8ReduceOpIlNS0_14func_wrapper_tIlZNS0_11sum_functorIlllEclERNS_14TensorIteratorEEUlllE_EEjlLi4EEEEEvT1_
│  ├─ 0.041 _ZN2at6native27unrolled_elementwise_kernelIZZZNS0_23direct_copy_kernel_cudaERNS_18TensorIteratorBaseEENKUlvE1_clEvENKUlvE2_clEvEUllE_NS_6detail5ArrayIPcLi2EEE23TrivialOffsetCalculatorILi1EjESC_NS0_6memory12LoadWithCastILi1EEENSD_13StoreWithCastILi1EEEEEviT_T0_T1_T2_T3_T4_
│  ├─ 0.039 _ZN2at6native29vectorized_elementwise_kernelILi4ENS0_11FillFunctorIfEENS_6detail5ArrayIPcLi1EEEEEviT0_T1_
│  ├─ 0.027 _ZN2at6native29vectorized_elementwise_kernelILi4ENS0_13AUnaryFunctorIllbNS0_51_GLOBAL__N__28ce311f_18_CompareEQKernel_cu_d8008c9616CompareEqFunctorIlEEEENS_6detail5ArrayIPcLi2EEEEEviT0_T1_
│  ├─ 0.015 _ZN2at6native29vectorized_elementwise_kernelILi4ENS0_13BinaryFunctorIffbNS0_51_GLOBAL__N__28ce311f_18_CompareEQKernel_cu_d8008c9616CompareEqFunctorIfEEEENS_6detail5ArrayIPcLi3EEEEEviT0_T1_
│  ├─ 136.551 _ZN2at6native29vectorized_elementwise_kernelILi4ENS0_15CUDAFunctor_addIfEENS_6detail5ArrayIPcLi3EEEEEviT0_T1_
│  └─ 154.297 liger_cross_entropy_kernel
├─ 1545.133 2-forward
│  ├─ 0.878 _ZN2at6native13reduce_kernelILi512ELi1ENS0_8ReduceOpIfNS0_14func_wrapper_tIfZNS0_11sum_functorIfffEclERNS_14TensorIteratorEEUlffE_EEjfLi4EEEEEvT1_
│  ├─ 0.569 _ZN2at6native13reduce_kernelILi512ELi1ENS0_8ReduceOpIlNS0_14func_wrapper_tIlZNS0_11sum_functorIlllEclERNS_14TensorIteratorEEUlllE_EEjlLi4EEEEEvT1_
│  ├─ 0.401 _ZN2at6native27unrolled_elementwise_kernelIZZZNS0_23direct_copy_kernel_cudaERNS_18TensorIteratorBaseEENKUlvE1_clEvENKUlvE2_clEvEUllE_NS_6detail5ArrayIPcLi2EEE23TrivialOffsetCalculatorILi1EjESC_NS0_6memory12LoadWithCastILi1EEENSD_13StoreWithCastILi1EEEEEviT_T0_T1_T2_T3_T4_
│  ├─ 0.207 _ZN2at6native29vectorized_elementwise_kernelILi4ENS0_11FillFunctorIfEENS_6detail5ArrayIPcLi1EEEEEviT0_T1_
│  ├─ 0.275 _ZN2at6native29vectorized_elementwise_kernelILi4ENS0_13AUnaryFunctorIllbNS0_51_GLOBAL__N__28ce311f_18_CompareEQKernel_cu_d8008c9616CompareEqFunctorIlEEEENS_6detail5ArrayIPcLi2EEEEEviT0_T1_
│  └─ 1542.804 liger_cross_entropy_kernel
└─ 1517.319 3-backward
   ├─ 0.171 _ZN2at6native29vectorized_elementwise_kernelILi4ENS0_11FillFunctorIfEENS_6detail5ArrayIPcLi1EEEEEviT0_T1_
   ├─ 0.148 _ZN2at6native29vectorized_elementwise_kernelILi4ENS0_13BinaryFunctorIffbNS0_51_GLOBAL__N__28ce311f_18_CompareEQKernel_cu_d8008c9616CompareEqFunctorIfEEEENS_6detail5ArrayIPcLi3EEEEEviT0_T1_
   └─ 1517.000 _ZN2at6native29vectorized_elementwise_kernelILi4ENS0_15CUDAFunctor_addIfEENS_6detail5ArrayIPcLi3EEEEEviT0_T1_

Notice that during backward, almost 100% time is spent in the last kernel, namely _ZN2at6native29vectorized_elementwise_kernelILi4ENS0_15CUDAFunctor_addIfEENS_6detail5ArrayIPcLi3EEEEEviT0_T1_. I have checked this kernel takes similar amount of time in the PyTorch/huggingface version of the calculation.
So are we gaining much from the inplace calculation? It already seems illegal and there is hardly any backward pass speedup even with it

Thanks! mark_dirty() can definitely be a resolution to inplace calculation warning.

Notice that during backward, almost 100% time is spent in the last kernel, namely ZN2at6native29vectorized_elementwise_kernelILi4ENS0_15CUDAFunctor_addIfEENS_6detail5ArrayIPcLi3EEEEEviT0_T1.  I have checked this kernel takes similar amount of time in the PyTorch/huggingface version of the calculation.

I guess this kernel is gradient accumulation kernel, not gradient calculation? I suppose there is another calculation kernel called in the torch version? Below is the trace of liger ce's backward:

I think the main reason liger's ce does forward and backward in a single kernel + inplace is for fused linear ce usage, which has to acquire gradients and handles previous layer's gradients as well, so inplace calculation won't be an issue for it.

Thanks! mark_dirty() can definitely be a potential resolution to inplace calculation warning.

Notice that during backward, almost 100% time is spent in the last kernel, namely ZN2at6native29vectorized_elementwise_kernelILi4ENS0_15CUDAFunctor_addIfEENS_6detail5ArrayIPcLi3EEEEEviT0_T1.  I have checked this kernel takes similar amount of time in the PyTorch/huggingface version of the calculation.

I guess this kernel is gradient accumulation kernel, not gradient calculation? I suppose there is another calculation kernel called in the torch version? Below is the trace of liger ce's backward:

Yes. I was surprised that this accumulation kernel could take that much time. Then I was thinking maybe the grad could be saved into _input.grad directly in the forward kernel to avoid this accumulation. But I am not sure if this can be done though.

I think the main reason liger's ce does forward and backward in a single kernel + inplace is for fused linear ce usage, which has to acquire gradients and handles previous layer's gradients as well, so inplace calculation won't be an issue for it.

This makes sense.


Make name change permissions more flexible

Organizations may want to restrict which users groups are allowed to change their Zulip name, rather than allowing/disallowing name changes across the board. For example, it may be useful to prevent guest users from changing their names.
We should therefore replace the "Prevent users from changing their name" setting with a more flexible choice, in the same location in SETTINGS / ORGANIZATION PERMISSIONS:

Label: Who can change their name

Options:

Default to everyone being allowed to change their name.

For existing orgs, migrate the value of the "Prevent users from changing their name" option:

checked -> Admins
not checked -> everyone

This option should be implemented using the new groups system, like "Who can unsubscribe others from this channel?".
https://zulip.com/help/restrict-name-and-email-changes should be updated accordingly.
Related issues:

#7683
#19525 -- this should use the groups-based system, not roles, for storing the permissions.

@zulipbot claim

Hi @alya,
I have thoroughly reviewed the codebase, and based on my understanding, I can write a migration to change the 'Prevent users from changing their name' boolean field to a 'who can change' short integer. We will offer 5 choices for this field, such as admins, admins and moderators, etc., and will store the selected choice accordingly. Then, we will create a specific function to determine whether the current user can modify their name based on these choices. Finally, we will implement the necessary changes in the frontend. This is my approach to solve this issue. Can I proceed with this approach?

@Aditya8840 If you feel that you need feedback on your approach, please post a specific question in the Zulip development community. Be sure to follow https://zulip.readthedocs.io/en/latest/contributing/asking-great-questions.html. Thanks!

@zulipbot abandon

@zulipbot claim

Hi @Vector73,
I wanted to check if you’re currently working on this issue. If not, I would love to contribute and take it up.

No, I am not. Feel free to work on it.

@zulipbot claim

Unassigning myself from this issue. I’m unable to test stuff of such issue. I’ll read more about testing(and ldap) and then take it up again.
@zulipbot abandon

Hey @alya, Could you please assign this issue to me?
I also have a question: Has the API endpoint been modified to accommodate the above frontend change? Currently, it's implemented as a checkbox, but I need to transform it into a dropdown with 4-5 options. Or is there something that I am missing about this issue?
Thank you!

@shuklamaneesh23 have you reviewed the contributor guide instructions for how to claim an issue?

Has the API endpoint been modified to accommodate the above frontend change?

This is up to you to investigate.

have you reviewed the contributor guide instructions for how to claim an issue?
Apologies for pinging you, @alya, to get this issue assigned to me. Currently, I have a claimed issue, so I'm unable to claim another one using the Zulip bot.

OK, in that case you need to follow the instructions in the contributor guide for how to ask for another issue to be assigned to you.

@zulipbot claim

@zulipbot claim


Structural/non-structural labels in the dataset

Currently the code assumes all NaNs and empty cells to be structurally missing.
However, there might be actual sampling missing values.
Users could be given the option to specify the labels used for structural/sampling missing values so they can be treated differently.
To begin with, sampling missingness may be assumed to be missing at random and we can do a complete-case analysis (i.e remove the rows with sampling missing values), or we could include them within the event tree under the edge label "missing".

Missing data
There are four different ways to deal with "missing" data.

Structurally missing values: Where a variable's recording is missing because it didn't make sense to record it. E.g. patient died.
Missing values: Where there is no reason for the data to be missing other than the data was not collected.
Structural zero: Where the value of a variable is never possible given previous events.
Sampling zero: Where an event could happen but it has never actually been recorded in the dataset.

@ashenvi10 Would you say this is correct? Please modify these definitions if not.
We need to determine how the user will tell the package which is which.


add methodology #971

closes #971

Missing is still a relation between methodology and methodical focus (if there is one we want to describe...). Any suggestions?


Incease maxPayloadLength upper limit and/or allow 0 (limitless)

My uWebSockets.js app daily handles large amount of data (10-35GB per conn) with no issue.
One of my colleagues tried to increase the maxPayloadLength to 100GB for stress testing but it didn't work. Apparently, there's a 50GB upper bound limit.
 maxPayloadLength: 100 * 1024 * 1024 * 1024 // failed

Is there any reason for that?
@alexhultman two suggestions if you don't mind:

allow maxPayloadLength to take value 0 (no limit) and let the user handle the limit logic on his side
increase the default maxPayloadLength to a much larger value: for example 100TB (see websocket-frame-size-limitation)

If you want to transfer hundreds of GB you really shouldn't use one single WebSocket message. Use streaming HTTP and you can cut your memory usage in half at least?

@alexhultman what maxPayloadLength is for? Is a a limitation per message or a total limitation?

Docs for maxPayloadLength say per message

Maximum length of received message. If a client tries to send you a message larger than this, the connection is immediately closed

Thanks for the pointer @hst-m

@alexhultman our service is WebSocket based. I'm afraid the Streaming won't help.


Use Grove Ultrasonic ranger with Nodejs and Python

HI guys,
Is there any way to use the ultrasonic ranger sensor with python or node.js ?
Thanks in advance

Hi,
We have a driver for the HSCR-04, URM37 and MaxSonar that work with all the supported languages. There was also a contribution with a driver for the Grove version of the ultrasonic sensor but it hasn't been merged yet because it needs some clean-up. Which one do you have?

Thanks for your reply.
I have this one :
http://www.gotronic.fr/art-telemetre-a-ultrasons-grove-sen10737p-18976.htm
I hope that you have a solution for that one.
Thanks again.

That's the one. Here's the code: https://github.com/arcatdmz/upm/commit/0277b7fcd7806a5ff11cb9a7eb36c650f3384859 in case you want to build the sensor driver yourself until we merge it.

The ultrasonic ranger sensor was added to the main branch. I do expect it to be merged with HSCR04 at some point though since they work the same way.


powershell: fix the build

For some reason, building powershell derivation started failing with
these errors:
  liblttng-ust.so.0 -> not found!
  ...
  libpam.so.0 -> not found!

This patch adds these dependencies
Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

I think you will need to add it to the library path for this to fix your problem.

@matthewbauer I can do that, however currently .so's referring to these libraries resolve well:
~/P/n/nixpkgs (powershell-fix|…) $ ldd /nix/store/wb1nbgl7kav2wdsy6hbb20ngznwpbzma-powershell-6.0.2/share/powershell/*.so | grep lttng
	liblttng-ust.so.0 => /nix/store/08ziz6wz4gznjmn5j3n7g9jk5ydk7r3j-lttng-ust-2.10.1/lib/liblttng-ust.so.0 (0x00007fef06584000)
	liblttng-ust-tracepoint.so.0 => /nix/store/08ziz6wz4gznjmn5j3n7g9jk5ydk7r3j-lttng-ust-2.10.1/lib/liblttng-ust-tracepoint.so.0 (0x00007fef054c7000)
~/P/n/nixpkgs (powershell-fix|…) $ ldd /nix/store/wb1nbgl7kav2wdsy6hbb20ngznwpbzma-powershell-6.0.2/share/powershell/*.so | grep pam
	libpam.so.0 => /nix/store/bx17bcz9z9gh7bjh22vi3qk3s8206izw-linux-pam-1.3.0/lib/libpam.so.0 (0x00007fed8c8a6000)
	libpam.so.0 => /nix/store/bx17bcz9z9gh7bjh22vi3qk3s8206izw-linux-pam-1.3.0/lib/libpam.so.0 (0x00007f10ec332000)

Do you think I need to cover that in makeLibraryPath anyway?

Amended the patch to include all libraries in the wrapper.


XED Encoder API

We've got decent coverage of the decoder API but very little of the encoder. We need to do that. There should be decent coverage of the XED enums so this should mostly be just binding the various xed_encoder_request_set_xxx methods.
As far as I can tell the general way that encoding works in XED is as follows:

You create an empty xed_encoder_request_t (which is actually a xed_decoded_inst_t)
You set a bunch of options on it
You call xed_encode to encode the instruction

Some extra notes:

We can't use DecodedInst as-is because a bunch of the accessors panic if they get an invalid XED enum value. We either need to adjust how it works, or define a new type to use instead.
xed_operand_values_t is also a xed_decoded_inst_t. I'm not sure if a pointer gets stored in the instruction and thus there should be lifetimes involved.
There's also xed_encode_nop which doesn't quite fit in but might be ok to have as a free-floating function.

I suspect a InstructionBuilder type thing might actually be a good fit here. I haven't really spent any time thinking about what it would look like though.

@flier I'm probably not gonna touch this one for a while so if you want an issue to try out this is probably a good one :)


Mapping a futures::Future to an ES6 Promise?

(This issue is mostly opened for "discussion" purposes, trying to reach the right target audience)
A lot of people will probably have the use-case of mapping a Rust futures::Future to an ES6 Promise.  My solution right now has been to do this:
fn foo() -> impl futures::Future<Item = String, Error = String> {
    // ...
}

#[wasm_bindgen]
struct JsApi { /* ... */ }

#[wasm_bindgen]
impl JsApi {
    pub fn foo(&self, resolve: JsValue, reject: JsValue) {
        let future = foo()
            .map(move |s| resolveString(resolve, s))
            .map_err(move |e| rejectString(reject, e));
        self.executor.spawn(future);
    }
}

#[wasm_bindgen(module = "../ffi")]
extern "C" {
    #[allow(non_snake_case)]
    fn resolveString(resolve: JsValue, string: String);
    #[allow(non_snake_case)]
    fn rejectString(reject: JsValue, string: String);
}

Then, in ffi.ts:
export function resolveString(resolve: (value: string) => void, value: string) {
  console.debug("resolved:", value);
  resolve(value);
}
export function rejectString(reject: (value: string) => void, value: string) {
  console.warn("rejected:", value);
  reject(value);
}

...and finally:
export function foo() {
  return new Promise<string>((resolve, reject) => wasm.foo(resolve, reject));
}

This is quite verbose and lots of boilerplate.  Some ideas on what might help:

Being able to call JsValues from Rust.
Supporting generics + monomorphized extern JS functions
Having native support for Promise/Future in particular since it might be a common use-case.

Any other ideas on how to improve this?

I think this'd be a fantastic idea! I unfortunately haven't figure out much of a way to work with closures and wasm-bindgen today, but I'm hopeful that we can figure that out soon to start binding APIs like promises!

I have integrated ES Promises and Futures (and tokio) once before, and I wrote a bit about the gotchas that will be encountered: https://github.com/starlingjs/starling/blob/master/src/promise_future_glue.rs#L1-L67

I have added in an excellent (and very fast) Executor to stdweb.
And it's easy to convert from Future -> Promise or from Promise -> Future.
This might help out with Future / Promise support in wasm-bindgen. Feel free to ask me for advice.

Nice! I think that's some great work to start from. I think an integration crate like this would probably start out as a separate crate rather than built into wasm-bindgen itself, and I'd be totally down for reviewing PRs to do so.

Support for this is added in https://github.com/rustwasm/wasm-bindgen/pull/600

https://github.com/rustwasm/wasm-bindgen/pull/600 merged!


Disabling front view crosshair only

Hello, I'm a... hm... a longtime user of Shoulder Surfing and I'm back using it. :)
Is there a way to disable the front view crosshair without disabling the third person one? In the following 2014 video, you see the crosshair is visible on third person camera but it's hidden on front view: https://youtu.be/fEUZd3gcvew?t=61.
 The only way I've found to disable it was to set Third Person Crosshair to false, then I miss it on third person camera. Set Third Person Crosshair back to true and I have the crosshair showing on both front view and third person camera.

Regards,
(EDIT: fixed. Redone a lost edit)

You can now set the crosshair visibility for each perspective individually


Replace unnecessary identity calls in sql tests

There are many places throughout the SQL tests where we pass arguments of the form (schema, identityFn, identityFn). Most of the functions that accept these arguments have an overload that accepts just schema and assumes the identityFn. This PR prefers the latter.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

R: @apilloud

Run BeamSQL PostCommit

Run SQL PostCommit

Run Dataflow Runner Nexmark Tests


POOL-705 Add StakePrizePool

oh shoot, don't merge this yet! I forgot to mention that when you push to the master branch with this and the reference app repo it deploys to netlify/prod. Which would normally be fine but if the reference app doesn't support Stake prize pools then we don't want these changes live yet.


[Bug] Property called "Status" is transformed to "Statu"

Hi there :)
I am trying to generate some classes with the online generator and for obvious reasons my class called "Status" is transformed to "Statu" is there a workaround ?
Input:
{
  "id": "http://some.site.somewhere/entry-schema#",
  "$schema": "http://url-to-schema.com#",
  "description": "a simple schema",
  "type": "object",
  "properties": {
    "status": {
      "type": "array",
      "items": {
        "type": "string",
        "default": "EMPTY",
        "enum": [
          "FIRST_VALUE",
          "SECOND_VALUE"
        ]
      }
    }
  }
}

Output:
-----------------------------------com.example.Example.java-----------------------------------

package com.example;

import java.util.List;
import com.google.gson.annotations.Expose;
import com.google.gson.annotations.SerializedName;

/**
* a simple schema
*
*/
public class Example {

@SerializedName("status")
@Expose
private List<Statu> status = null;

public List<Statu> getStatus() {
return status;
}

public void setStatus(List<Statu> status) {
this.status = status;
}

}
-----------------------------------com.example.Statu.java-----------------------------------

package com.example;

import java.util.HashMap;
import java.util.Map;
import com.google.gson.annotations.SerializedName;

public enum Statu {

@SerializedName("FIRST_VALUE")
FIRST_VALUE("FIRST_VALUE"),
@SerializedName("SECOND_VALUE")
SECOND_VALUE("SECOND_VALUE");
private final String value;
private final static Map<String, Statu> CONSTANTS = new HashMap<String, Statu>();

static {
for (Statu c: values()) {
CONSTANTS.put(c.value, c);
}
}

private Statu(String value) {
this.value = value;
}

@Override
public String toString() {
return this.value;
}

public String value() {
return this.value;
}

public static Statu fromValue(String value) {
Statu constant = CONSTANTS.get(value);
if (constant == null) {
throw new IllegalArgumentException(value);
} else {
return constant;
}
}

}

There isn't really a workaround I'm afraid, other than renaming this field from status to statuses. Lists are expected to contain multiple items the type of a list item is named by creating a singular noun.
We'll need to add a special case to the inflector so that it does not attempt to singularize this word:
https://github.com/joelittlejohn/jsonschema2pojo/blob/master/jsonschema2pojo-core/src/main/java/org/jsonschema2pojo/util/Inflector.java

Hi @joelittlejohn thank you for the fast answer :)
Can I do a pull request for that case ? How many time will it takes till the new release ? We need it for a professional project.
BTW: Thank you for this great tool :)

Yes feel free to submit a PR. I think you can simply add the word to the 'irregular' list here:
https://github.com/joelittlejohn/jsonschema2pojo/blob/master/jsonschema2pojo-core/src/main/java/org/jsonschema2pojo/util/Inflector.java#L102
We don't need to ever pluralize anything so it doesn't matter that pluralizing 'status' would no longer become 'statuses'.
I'm happy to create a release whenever you're ready. Please do install and test your other project against a local snapshot of this plugin though, we want to be sure that your PR change solves the problem.

@joelittlejohn I've right know published a PR hope I did it the right way :)

Thanks for reporting this Sebastien. I went a slightly different way with the fix in the end. There's now a specific secularization rule to fix this case, and this allows other similar cases to be unaffected.
I'll release this shortly.

Perfect ! Thank you very much Joe :)


agnos updater: faster flashing

There was a good intention here but it's much slower. The len seems too expensive, and almost doubles the flashing time.
3m20s compared to 6m not using len

* 3m26s was before this whole change

I don't see why this would? There's no way len is that expensive, and I doubt the relative difference is much.
How did you test this and confirm it's this?

I flashed the exact 10.1 image, same commit, with this change and without

I probably did the rookiest mistake:

flashed AGNOS 10.1 image in AGNOS 11 (24.04) and was slow, so I said in my head “it’s clearly not my mistake, for sure it’s adeeb’s cleanup, since the speed was good, tested 10+ times before”
removed your cleanup - len - (while being in 20.04) and flashed AGNOS 10.1 again while being in AGNOS 10.1 (20.04) and flashed fast

Didn’t even realize that len was in noop not in unsparsify. AGNOS 10.1 is sparsified.
Leaving this open until I find the real reason.
“Give someone enough chances to make mistakes, and eventually they’ll make fewer mistakes than you do.”

After some hours spent, profiling, etc managed to get to this (in 24.04):
uv python:
$ python -V
Python 3.12.3
$ python decompress.py
0.001038 seconds

system python (from ubuntu)
$ /usr/bin/python -V
Python 3.12.3
$ /usr/bin/python decompress.py
0.000400 seconds

Although the uv python is compiled with optimizations, I also tested this and it's much faster at computations, it seems that for some reason on lzma decompress it's not. Investigating further.


Feature/myosim 2

Shoot, sorry, this was a personal pull request. I accidentally sent it to yours...


Issue when clicking on execute shell and view logs from Pods in deployment details page

On master-head - commit id: 33f755f1

Dashboard --> Deployment --> Create
Create a deployment
Go to Deployment details page by clicking on the deployment created.
Click on the ellipsis on the Pod.

Click on Execute Shell - Button clear is half seen on the Dashboard

Click on View logs - Buttons clear, download are half seen on the Dashboard

On master-head - commit id: ec04f7878cf
Original Issue  is still seen
View Logs:

Exec Shell:

On master-head - commit id: ec04f787
Exec shell: -- as expected

View logs:

There is too big space below the buttons download.
Also the dropdown for test as seen in the snapshots do not do anything.
Questions:

What is dropdown on test expected to do ?
When is Follow enabled ?

Reopening because of these issues ^^

https://github.com/rancher/dashboard/pull/1512

On master-head - commit id: d4b3bc899
These issues exist
Reopening the issue.

resolved here: https://github.com/rancher/dashboard/pull/1571/commits/015d6272a9bba883c6113825703e8223846141e3

The fix in #1512 was..not good, but I fixed it yesterday.

Verified on 2.5.0-rc7 and setting v3/settings/ui-offline-preferred  to false

View logs and Exec shells look good


Update dependencies

Updating Flask dependency. Should fix #61
Tested with raspberry pi 1 and python 3.9.2.
Tested the app locally on archlinux with python 3.10.2 (couldn't pair though, but I haven't run it with sudo on this device, only disabled the plugins)
Chores:

Changed the sigterm handler to not crash...
also check permanent bluetooth/bluez override

I tried doing just the updates (same code, just installed different reqs versions) and am getting this error now:
  File "/home/micael/.local/pipx/venvs/nxbt/lib/python3.10/site-packages/dns/namedict.py", line 35, in <module>
    class NameDict(collections.MutableMapping):
AttributeError: module 'collections' has no attribute 'MutableMapping'

This version fixed the issue I had on 3.10: dnspython==2.2.1
Not sure exactly on which version this was fixed.

I tried doing just the updates (same code, just installed different reqs versions) and am getting this error now:
  File "/home/micael/.local/pipx/venvs/nxbt/lib/python3.10/site-packages/dns/namedict.py", line 35, in <module>
    class NameDict(collections.MutableMapping):
AttributeError: module 'collections' has no attribute 'MutableMapping'

can you posts steps to reproduce?

can you posts steps to reproduce?

I'm not too sure what exactly are the steps, and I fixed it already, but I'll try to say what I did:

be me
have Python 3.10.4
have pipx 1.0.0
run pipx install nxbt
run sudo nxbt webapp
get errors (the ones about Flask and such)
find this PR
read updated dependencies
run pipx inject nxbt Flask==2.0.0
run pipx inject nxbt Flask-SocketIO==5.1.0
run pipx inject nxbt eventlet==0.33.0
run sudo nbxt webapp
get error related to dnspython (the one on my comment)
run pipx inject nxbt dnspython==2.2.1
run sudo nbxt webapp
works!

Oh, okay. Mine runs on python 3.92 with dnspython 1.16.0, no issues there. Since it's not a direct dependency I'd hope it would update to the newest one available. As it comes through eventlet and eventlet requires dnspython as any >= it's weird you ran into issues with this. But if it works for you then it's fine by me...

I've just tried installing your branch on a clean 3.10 venv, and it worked straight away, picked up the updated dnspython and everything, so I guess my problem was that I was trying to manually update the requirements by myself.

When I try both merging @l4desu-mizu's PR into my local installation of NXBT, and using @MicaelJarniac's pipx method, I'm left with the same error, as follows:
https://pastebin.com/raw/5ZCgF0ye
Any idea what's going wrong here?

Looks like there was a change in the flask socketio package. There is a recenz update. I'll have a look at it and try bumping the versions again.

If my assumptions are wrong it might help to know the steps you took to get that error message.

Yes, I installed the original package through pip and then merged your pr files into the package in /usr/local/lib/python3.10/dist-packages/nxbt which I'm kind of now seeing might have been a poor idea. I also tried the other method in the thread (using pipx to install nxbt and inject dependencies). I'll try to check out the pr with git and run from source but I'm not particularly familiar doing so, so I'll play around with it a little bit and see if I can get it to work.

I checked the steps Micael posted. They worked fine for me too. So you might be able to get it running with a fresh install and pipx.
I wonder if you could also do:

create a virtualenv virtualenv .venv
activate it source .venv/bin/activate
and just install the branch there pip install git+https://github.com/l4desu-mizu/nxbt.git@update_dependencies
which would then mean that you probably could run it with (sudo) nxbt webapp
not sure though haven't really tested it, only tried starting it and it seems fine.

Had our controller working fine but today it crashed and wouldn't reload. I generated a new virtual machine and now I'm getting this again, even after updating the dependencies with this pull request
Traceback (most recent call last):   File "/usr/local/bin/nxbt", line 8, in <module>     sys.exit(main())   File "/usr/local/lib/python3.8/dist-packages/nxbt/cli.py", line 321, in main     from .web import start_web_app   File "/usr/local/lib/python3.8/dist-packages/nxbt/web/__init__.py", line 1, in <module>     from .app import start_web_app   File "/usr/local/lib/python3.8/dist-packages/nxbt/web/app.py", line 9, in <module>     from flask import Flask, render_template, request   File "/usr/local/lib/python3.8/dist-packages/flask/__init__.py", line 14, in <module>     from jinja2 import escape ImportError: cannot import name 'escape' from 'jinja2' (/usr/local/lib/python3.8/dist-packages/jinja2/__init__.py)

When I tried to run pipx install nxbt I got this error (I already have microsoft visual C++ or greater)
    C:\Users\owner\.local\pipx\logs\cmd_2022-08-27_19.59.17_pip_errors.log

pip failed to build packages:
    dbus-python
    psutil

Some possibly relevant errors from pip install:
    error: subprocess-exited-with-error
    error: [WinError 193] %1 is not a valid Win32 application
    error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
    error: legacy-install-failure```

are you running this on windows? i dont think that'll work. from what i've seen this is not written to run on windows and i'm also uncertain about dbus-python packages for windows.

When I tried to run pipx install nxbt I got this error (I already have microsoft visual C++ or greater)
    C:\Users\owner\.local\pipx\logs\cmd_2022-08-27_19.59.17_pip_errors.log

pip failed to build packages:
    dbus-python
    psutil

Some possibly relevant errors from pip install:
    error: subprocess-exited-with-error
    error: [WinError 193] %1 is not a valid Win32 application
    error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
    error: legacy-install-failure```

are you running this on windows? i dont think that'll work. from what i've seen this is not written to run on windows and i'm also uncertain about dbus-python packages for windows.

I've been running it on windows from a virtual machine as per the instructions of Brikwerk's project for the last few months + your pull request with no issues

my set up looks like this

setup(
    name="nxbt",
    include_package_data=True,
    long_description_content_type="text/markdown",
    install_requires=[
        "dbus-python==1.2.16",
        "Flask~=2.0.0",
        "Flask-SocketIO~=5.1.0",
        "eventlet~=0.33.0",
        "blessed==1.17.10",
        "pynput==1.7.1",
        "psutil==5.6.6",
        "cryptography==3.3.2",
    ],
    extra_require={
        "dev": [
            "pytest"
        ]
    }
)```

Okay I managed to fix this issue by doing the following:
changing setup.py to contain this:
"Flask~=2.1.0",
"jinja2<3.1.0",
"Flask-SocketIO~=5.1.0",
"eventlet~=0.33.0",
I also noticed it was searching in a path directory "python3.8/dist-packages" but such a directory didn't exist on my hard drive, so I made one and pasted the flask folder in there (version 2.1.0 after running pip install flask==2.1.0
Finally, I reran vagrantsetup.py, and generated a new virtual machine via vagrant up

Had our controller working fine but today it crashed and wouldn't reload. I generated a new virtual machine and now I'm getting this again, even after updating the dependencies with this pull request
Traceback (most recent call last): File "/usr/local/bin/nxbt", line 8, in <module> sys.exit(main()) File "/usr/local/lib/python3.8/dist-packages/nxbt/cli.py", line 321, in main from .web import start_web_app File "/usr/local/lib/python3.8/dist-packages/nxbt/web/__init__.py", line 1, in <module> from .app import start_web_app File "/usr/local/lib/python3.8/dist-packages/nxbt/web/app.py", line 9, in <module> from flask import Flask, render_template, request File "/usr/local/lib/python3.8/dist-packages/flask/__init__.py", line 14, in <module> from jinja2 import escape ImportError: cannot import name 'escape' from 'jinja2' (/usr/local/lib/python3.8/dist-packages/jinja2/__init__.py)
When I tried to run pipx install nxbt I got this error (I already have microsoft visual C++ or greater)
    C:\Users\owner\.local\pipx\logs\cmd_2022-08-27_19.59.17_pip_errors.log

pip failed to build packages:
    dbus-python
    psutil

Some possibly relevant errors from pip install:
    error: subprocess-exited-with-error
    error: [WinError 193] %1 is not a valid Win32 application
    error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
    error: legacy-install-failure```

@l4desu-mizu Did you notice any improvement with macros running more consistently after updating dependencies? I just got the latest official release working but have noticed that the macros are sometimes incosistent.

@l4desu-mizu Did you notice any improvement with macros running more consistently after updating dependencies? I just got the latest official release working but have noticed that the macros are sometimes incosistent.

never used the macros sorry. but i would think that these changes mainly impact the usage of the server.


adds url params and history to routes

Codecov Report

Merging #32 into master will decrease coverage by 2.67%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##           master      #32      +/-   ##
==========================================
- Coverage   61.09%   58.41%   -2.68%
==========================================
  Files          40       41       +1
  Lines         586      630      +44
  Branches       51       61      +10
==========================================
+ Hits          358      368      +10
- Misses        220      253      +33
- Partials        8        9       +1

Impacted Files
Coverage Δ

...scovery-elasticsearch-app/src/state/rootReducer.ts
88.88% <ø> (-1.59%)
:arrow_down:

...very-elasticsearch-app/src/components/Settings.tsx
21.73% <0%> (-0.49%)
:arrow_down:

...overy-elasticsearch-app/src/components/Landing.tsx
46.15% <50%> (+0.69%)
:arrow_up:

...es/react-discovery-elasticsearch-app/src/index.tsx
78.57% <50%> (-2.92%)
:arrow_down:

...asticsearch-app/src/components/DrawerListItems.tsx
92.85% <88.88%> (-2.15%)
:arrow_down:

...sticsearch-app/src/components/ViewTypeSwitcher.tsx
82.6% <0%> (ø)
:arrow_up:

...arch-app/src/components/hit-views/Kulturobjekt.tsx
24.39% <0%> (ø)

...y-elasticsearch-app/src/components/ListFilters.tsx
97.14% <0%> (+2.85%)
: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 fa85fc5...67bdcb1. Read the comment docs.


included big-cluster config

nf-core/proteomicslfq pull request
Many thanks for contributing to nf-core/proteomicslfq!
Please fill in the appropriate checklist below (delete whatever is not relevant).
These are the most common things requested on pull requests (PRs).
PR checklist

[x] This comment contains a description of changes (with reason)
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If necessary, also make a PR on the nf-core/proteomicslfq branch on the nf-core/test-datasets repo
[ ] Ensure the test suite passes (nextflow run . -profile test,docker).
[ ] Make sure your code lints (nf-core lint .).
[ ] Documentation in docs is updated
[ ] CHANGELOG.md is updated
[ ] README.md is updated

Learn more about contributing: CONTRIBUTING.md

I guess this is fine for development but in the long-term, I would like to see this in
https://github.com/nf-core/configs
Just to not have too many configs. Usually, people have to write their own config anyway.


Add implementation recommendation to crypto API reference

Added note explaining the recommendation of using the SDKs over the HTTP endpoints for production environments.
Thank you for helping make the Dapr documentation better!
Please follow this checklist before submitting:

[X] Commits are signed with Developer Certificate of Origin (DCO - learn more)
[X] Read the contribution guide
In addition, please fill out the following to help reviewers understand this pull request:

Description
#3952 already got merged, so applying the recommended changes here instead.

Thanks!


Forward RTP packets to other tools (e.g. ffmpeg)

Hey guys,
I'm having trouble forwarding RTP packets to ffmpeg and I wonder if you could point me to the right direction.
The whole WebRTC logic works very smoothly (your golang API is really nice btw) but ffmpeg doesn't seem to be able to parse the stream I'm trying to feed it.
I wonder if pion's RTP packets are forwardable at all...
I'm using gortp to send RTP packets I'm receiving from pion.
Here's a sample code
        // Create local addr
	var laddr *net.IPAddr
	if laddr, err = net.ResolveIPAddr("ip", "<IP_ADDRESS>"); err != nil {
		err = fmt.Errorf("main: creating local addr failed: %w", err)
		return
	}

	// Create a UDP transport with "local" address and use this for a "local" RTP session
	// The RTP session uses the transport to receive and send RTP packets to the remote peer.
	var tp *rtp.TransportUDP
	if tp, err = rtp.NewTransportUDP(laddr, 5000, ""); err != nil {
		err = fmt.Errorf("main: creating udp transport failed: %w", err)
		return
	}

	// TransportUDP implements TransportWrite and TransportRecv interfaces thus
	// use it to initialize the Session for both interfaces.
	rs := rtp.NewSession(tp, tp)

	// Add address of a remote peer (participant)
	if _, err = rs.AddRemote(&rtp.Address{
		CtrlPort: 5002 + 1,
		DataPort: 5002,
		IPAddr:   laddr.IP,
		Zone:     "",
	}); err != nil {
		err = fmt.Errorf("main: adding remote failed: %w", err)
		return
	}

	// Listen on transport
	if err = rs.ListenOnTransports(); err != nil {
		err = fmt.Errorf("main: listening on transports failed: %w", err)
		return
	}

	// Handle new track
	pc.OnTrack(func(track *webrtc.Track, receiver *webrtc.RTPReceiver) {
		// Send a PLI so that the publisher is pushing a keyframe every 2 seconds
		go func() {
			t := time.NewTicker(2 * time.Second)
			for range t.C {
				// Write rtcp
				if err := pc.WriteRTCP([]rtcp.Packet{&rtcp.PictureLossIndication{MediaSSRC: track.SSRC()}}); err != nil {
					shared.Logger.ErrorC(ctx, fmt.Errorf("main: writing rtcp failed: %w", err))
				}
			}
		}()

		// Loop
		var idx uint32
		var ss *rtp.SsrcStream
		for {
			// Read
			rp, err := track.ReadRTP()
			if err != nil {
				shared.Logger.ErrorC(ctx, fmt.Errorf("main: reading rtp  %s failed: %w", track.Kind(), err))
				return
			}

			// No stream
			if ss == nil {
				// Create a media stream.
				if idx, err = rs.NewSsrcStreamOut(&rtp.Address{
					CtrlPort: 5000 + 1,
					DataPort: 5000,
					IPAddr:   laddr.IP,
					Zone:     "",
				}, rp.SSRC, rp.SequenceNumber); err.Error() != "" {
					shared.Logger.ErrorC(ctx, fmt.Errorf("main: creating ssrc stream failed: %w", err))
					return
				}
				ss = rs.SsrcStreamOutForIndex(idx)
				ss.SetPayloadType(rp.PayloadType)
			}

			// Create packet
			wp := rs.NewDataPacketForStream(idx, rp.Timestamp)
			wp.SetPayload(rp.Payload)

			// Write packet
			if _, err = rs.WriteData(wp); err != nil {
				wp.FreePacket()
				shared.Logger.ErrorC(ctx, fmt.Errorf("main: writing packet failed: %w", err))
				return
			}
			wp.FreePacket()
		}
	})

I've tried all sort of sdp with ffmpeg but no luck. Here's my latest sdp if that helps:
v=0
o=- 1 1 IN IP4 <IP_ADDRESS>
s=Test
c=IN IP4 <IP_ADDRESS>
t=0 0
a=recvonly
m=video 5002 RTP 126
a=rtpmap:126 H264/90000
a=fmtp:126 profile-level-id=42e01f;level-asymmetry-allowed=1;packetization-mode=1

ffmpeg waits forever without doing anything, as if it wasn't receiving any stream at all.
If you have any idea how I can make this work, that would be awesome. Otherwise, if you feel this is not an issue with pion, feel free to close this issue.
Thanks in advance.
Cheers

Hey @asticode, thanks for checking out Pion!

Are you sure it is H264 only. Did you create a MediaEngine that only allows H264? OnTrack is only firing once?
I would just forward the raw H264 packets. The following is pseudo code, but should work.

buf := make([]byte, 1500)
for {
    n, err := track.Read(buf)

    udpTransport.Write(buff[:n])
}

I would try GStreamer, a little easier to debug. Then come back to ffmpeg when this is working.

// Pipeline that listens on port 5000, check that are even getting data
gst-launch-1.0 udpsrc port=5000 ! fakesink dump=true

// Are you getting valid H264 packets
gst-launch-1.0 udpsrc port=5000 ! application/x-rtp ! rtph264depay ! fakesink dump=true

// Decode and play them
gst-launch-1.0 udpsrc port=5000 ! application/x-rtp ! rtph264depay ! decodebin ! autovideosink

@asticode If you are interested, it would also be SUPER helpful to have this an example application! examples/rtp-forwarder
It would forward a single H264 stream, and then we could print out the H264 ffmpeg should use. I am happy to help as well, then would love to share what you built in Slack/Twitter. I bet this is a really common thing people are trying to build :)

@Sean-Der thanks a bunch for the suggestions, I managed to make it work by simply UDP forwarding raw packets as you suggested.
However now I need to find a way to generate automatically the sdp I provide ffmpeg depending on what the user is sending. Here's how I see things:

parse the offer which is a SessionDescription => is there an exported function to parse the offer SDP and get all streams/attributes/payload types/etc. ?
add an OnTrack handler that checks the payload type of the first RTP packet and, based on the offer SDP parsed attributes, add the proper stream to the SDP I will provide ffmpeg => is there an exported function to create an SDP from scratch ?

I think that could work. Do you have other suggestions ?
I'm using the code in a private project therefore neither sharable or advertisable. However I'm using the open source golang encoder I've built on top of libav (ffmpeg libs), therefore if I strip all private stuff and create a simple example application, I would love to add a examples/rtp-forwarder 🙂 But first I need to fix the sdp generation 😄

For parsing you could use the SDP library that pion/webrtc uses! Unmarshall I think this will be more of a pain though.
I would look at the first RTP packet in OnTrack and then generate it by hand. You can use Marshal or just do a string with a bunch of format specifiers.
When you get the SDP generation done I think an example showing this off would be super powerful!
Also if you need an example on your private project I am happy to help on Slack or email sean @ pion.ly the more people that use Pion the better it gets :)


Add addresses in Durham, NC

Status:

[x] Research sources and propose best source (and it's data license)
[x] Review proposed source
[ ] Approve source based on review comments
[ ] Add to OpenAddresses

NOTE: Proposed source notes should include basic column mapping to OpenAddress data model.

wrote and requested data and permission (https://durhamnc.gov/1227/GIS-Services )09/27/2016.  I believe data can be downloaded from here: https://opendurham.nc.gov/explore/?q=address&sort=modified (**there are three different datasets (with different amounts of records)).  It appears all three have a ODBL license - not sure if we can have that for this project?  http://opendatacommons.org/licenses/odbl/

Email and data received - **No Mention of copyright - I e-mailed and asked as well as voicemail.  Will call again today.
Hi Justin,
Per your request I have placed the latest shapefile of the county-wide address points on our FTP site for you to download. Please follow the login credentials below to access this site:
Web browser entry: -
Username: -
Password: -
Please copy the contents of the folder to your hard drive or local network as soon as you can and let me know when you have successfully done so, so that I can remove the folder to free up the space in our ftp site for future customers.
If you have any problem downloading the data or using the file, please let me know.
Regards,
Jing N Huang
GIS Analyst II
Technology Solutions - GIS, City of Durham
101 City Hall Plaza, 4th Floor, Ste 4142
Durham, NC 27701-3329
P<PHONE_NUMBER>, ext 33244
F<PHONE_NUMBER>
<EMAIL_ADDRESS>http://www.durhamnc.gov/departments/gis/

uploading data to dropbox and will update link

https://www.dropbox.com/sh/4pwm2iyb25tlbk1/AABLnuePkbhdURtA-zruuzA-a?dl=0
***I need to get a copyright response before I can say use this data

Called Mr. Huang for past three days and left voicemails and e-mails.  No response.  Called the GIS Manager ( Marcus Bryant) and he was not in office either.  Left him a voice mail.  I will continue to follow-up until I understand what metadata/ terms/ copyright on shapefile is.

Marcus Bryant called me back - its open - use for whatever you want!  He told me we cannot receive in writing and told me to follow their terms here: http://opendurham.nc.gov/terms/terms-of-use/

@iandees A curious set of mixed messages in the src data license (local gov't says use it for anything, but it's technically released under an ODbL).
What's OpenAddresses approach to ODbL sources? Are there other ODbL datasets included already?

Looks like there are a handful of other ODbL datasets included:

https://github.com/openaddresses/openaddresses/search?utf8=✓&q=odbl

Yep, we have a couple ODbL sources. They should only be included in the share-alike output of OpenAddresses.
It does appear that the Durham folks are confused about what ODbL means, or maybe the dataset they gave via FTP is different than the one on the opendurham portal?

I think the open data concept is new to some people. When I spoke with Mr. Bryant - he said that this is a new concept to the people there and they put the cart before the horse; literally called the open data movement and the direction of all things tech the Wild West!  But I asked him about the terms of use and he said there were none.  I pointed out that their site has two different sets of terms and they conflict.  He said the new open data portals terms are the most current and to use those as the terms; as they have yet to update anything on their sites end.  I believe the data I received from Mr. Huang is the most current dataset - but if we want to use points from the open portal instead that is up to who does the import (*then the actual license is right there - as Nate noticed it is ODBL for all three address points datasets) http://opendurham.nc.gov/explore/?sort=modified&q=address then click information.  Sorry, its a bit long winded, but just want to make sure we know terms and source of data.

As long as we mark the right "attribution required" and "share-alike" flags in the OA source information, the data will be handled appropriately in our system.

@nvkelso can we close this issue?  Thanks!

I can still add the data here. I'll close it with the pull request in a minute.


Custom commissioning UI | Get SSID and Password

Here sample app manages the entire commissioning flow but as per our requirement we want to implement custom commissioning flows instead of using System UI is there any possibility of using Home APIs with custom UI instead of Play Services provided default UI (Scanner / Managing network credential internally) or it will commission through Google Play Services and Default UI only?
As of now, we're following CHIPTool And the user has to provide SSID and Password as input in the commissioning flow. But we want to automate that so that users don't have to enter any network credentials manually
How can I get SSID / Password automatically, Is it something possible in Android at all to get current network credentials to automate this process even in custom commissioning flows?

A key goal of the Google Home Mobile SDK is so that you don't have to deal with these issues. So, no, it's not possible to cherry-pick specific functionality from it.