code whitespace not being respected

The whitespace in code blocks isn't being respected in the rendered site.
For example, https://appsody.dev/docs/stacks/create-or-modify looks like this:

The github-rendered markdown, however, looks like this:

https://github.com/appsody/docs/blob/master/docs/stacks/create-or-modify.md

Thanks for spotting this @ebullient 🙂Looks inconsistent with the rest of the documentation so will take a look at this asap


Fix detection of org-scoped packages

Alternative fix for #260, adds tests and makes a more targeted fix than #261 which appears to introduce other issues.
Do not merge, currently just for testing.

Great to have a test (thought it probably makes sense to pull it out of examples/ and into tests/ -- realize this is a work in progress).  I closed out #261.
I assume you didn't see the other issue I saw with a missing loglevel library?  (Since the tests passed, I assume not ... however, it could just be that a different set of packages lead to a different layout.)
Do you think we can land today?  I was hoping to focus on this stuff with my blog post, although worst case I can workaround the issue with some package renaming (or just not use Slack).

Do you think we can land today?

By "land", I meant commit and cut a new release of @pulumi/aws.
If not today, tomorrow is fine also.

I assume you didn't see the other issue I saw with a missing loglevel library? (Since the tests passed, I assume not ... however, it could just be that a different set of packages lead to a different layout.)

Yeah - per

Awesome 🎉


Remove extra verify-callback

Plus exercising the CI autest to figure out test failures.

[approve ci autest]

$ git grep "set_verify("
iocore/net/SSLClientUtils.cc:  SSL_CTX_set_verify(client_ctx, SSL_VERIFY_PEER, verify_callback);
iocore/net/SSLNetVConnection.cc:      SSL_set_verify(this->ssl, SSL_VERIFY_PEER, verify_callback);
iocore/net/SSLUtils.cc:  SSL_set_verify(ssl, server_verify_client, ssl_verify_client_callback);
iocore/net/SSLUtils.cc:    SSL_CTX_set_verify(ctx, server_verify_client, ssl_verify_client_callback);
tools/http_load/http_load.c:      SSL_CTX_set_verify(ssl_ctx, SSL_VERIFY_NONE, cert_verify_callback);

I assume the other is the one in SSLNetVConnection.cc. Do we want to set the callback function to SSL rather than SSL_CTX?

Good point. Should review the client side as well.  I noticed double prints from the server verify callback when looking at the debug statements from the autest failures.  I had figured that with multiple calls to SSL_*_set_verify, the last one in would be the only one called.  But for openssl at least, it appears that there is a slot for the SSL_CTX and a slot for the SSL object itself.
Originally we just had the SSL_CTX version.  I added the SSL object version to deal with dynamic updates I believe.  Need to review some git history.

Perhaps we can go ahead and land this change, and track down additional potential redundant calls later.  I tried to do a quick fix that seemed to match on the other side, but several of the tls_client_verify* autests fail.  I doubt I will have much time to get back to this for some time.

Cherry-picked to v9.1.x branch.


[JSS][Forms][React] Implement file upload to jss 13

Is your feature request related to a problem? Please describe.
Current implementation JSS doesn't support file upload and this component is implemented in Sitecore 9.3.
Describe the solution you'd like
I found that file upload component was created and merged to release/14.0.0 (PR). It would be great also to merge it to JSS 13 version.
Your Environment
Sitecore Version: 9.3
JSS Version: 13.0.5
Browser Name and version: All browsers
Operating System and version (desktop or mobile): All operating systems

@mlukasz7 Added in JSS 13.2.0, in #392


Add optional parameter to prevent negative balances with admin pay

I'm thinking something along the lines of:
/adminpay Erigitic -250 [true/false]
This will be an optional parameter that'll default to false, thus allowing balances to go negative when using admin pay. This is the current behavior. If true, balances will be prevented from going below 0.

Remember to raise a CommandException so command blocks know the payment failed


Merging Development to Main

Welcome to Codecov :tada:
Once merged to your default branch, Codecov will compare your coverage reports and display the results in this comment.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


[QUESTION] Can you use a header row with onEachRow?

Prerequisites

[x] Have read and understood: https://github.com/Maatwebsite/Laravel-Excel/blob/3.1/.github/SUPPORT.md
[x] Checked if your Laravel Excel version is still supported: https://docs.laravel-excel.com/3.1/getting-started/support.html#supported-versions
[x] Checked that your question isn't already asked before.
[x] Filled in the entire issue template

Versions

PHP version: 7.3.20
Laravel version: 7.26.1
Package version: 3.1.21

Description
Can you use a header row with onEachRow? How? Everything I try says I can't access the Row object as an array. Can't pass an array to onEachRow either.

Yes you can, you have to to $row->toArray()  to ghet the actual array. https://docs.laravel-excel.com/3.1/imports/model.html#handling-persistence-on-your-own

I'm open for a PR that adds ArrayAccess to the Row class.


Prototype for azure emitter

Prototype for azure emitter. The logic is similar to MGC azure plugin. Azure emitter provides function how to process azure data, unbranding emitter just calls this function.

API change check
APIView has identified API level changes in this PR and created following API reviews.
@typespec/http-client-csharp


Merge pull request #16 from Moebirdie/feature/add-js

Merge pull request #15 from Moebirdie/main

Should bring everything in sync


ast example fails to compile

Dear All
Most probably the issue is at my end but I wonder if you have any ideas.
cargo build works and all but one of the examples runs, but the ast example fails with 12 warnings and this error:
$ cargo run --example=ast 0
... 12 warnings
error: linking with `cc` failed: exit status: 1
  |
  = note: env ...
  = note: Undefined symbols for architecture x86_64:
      "_clingo_program_builder_init", referenced from:
          clingo::ast::ProgramBuilder::from::hf7d9290884ba38a9 in ast-77276d986174349c.9q7shmipeyu9bfa.rcgu.o
    ld: symbol(s) not found for architecture x86_64
    clang: error: linker command failed with exit code 1 (use -v to see invocation)

error: could not compile `clingo` (example "ast") due to previous error

cargo test fails with a similar error:
...
error: could not compile `clingo` (test "integration_test") due to previous error

My clingo works normally as far as I can tell.  I have CLINGO_LIBRARY_PATH set.
This is the version of clingo I have:
$ clingo -v
clingo version 5.5.0
Address model: 64-bit

libclingo version 5.5.0
Configuration: without Python, without Lua

libclasp version 3.3.6 (libpotassco version 1.1.0)
Configuration: WITH_THREADS=1
Copyright (C) Benjamin Kaufmann

License: The MIT License <https://opensource.org/licenses/MIT>

Am I missing something?
With thanks and best wishes
Ivan

If you use dynamic linking, you need to include the path to libclingo into your LD_LIBRARY_PATH
For example, in bash:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/your/custom/libclingo/path/

Also make sure to use the correct version of clingo  which for clingo-rs-0.8.0 is clingo-5.6.2.
You can get the latest clingo via conda.
Alternative, you can use the static-linking feature.

Thanks, I missed the bit about LD_LIBRARY_PATH in the README.  Now working.  So:

exports:

export CLINGO_LIBRARY_PATH=/my/custom/libclingo/path/
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$CLINGO_LIBRARY_PATH

upgrade to clingo-5.6.2 (I installed clingo with nix, so upgraded that)


Renamed "Scientific Extension" to "Scientific Citation Extension" #990

Related Issue(s): #990
Proposed Changes:

Renamed "Scientific Extension" to "Scientific Citation Extension", no breaking change (i.e. extension identifier and prefix are not changed)
Add Collection Assets to list of "useful" Collection extensions

PR Checklist:

[x] This PR is made against the dev branch (all proposed changes except releases should be against dev, not master).
[x] This PR has no breaking changes.
[x] I have added my changes to the CHANGELOG or a CHANGELOG entry is not required.
[ ] This PR affects the STAC API spec, and I have opened issue/PR #XXX to track the change.

+1 for keeping the field names the same. DOIs, publications, and citations are very much a scientific community focused thing.
If there were field changes, it's likely going to be rough going, but not impossible.
Curious if there were any thoughts on what else might go in sci:?

The initial idea was to add reproducibility-related fields, for example, but most have been added to "processing" already.

This all looks good to me. I'm approving despite the current failing test.  Not sure what'w causing it, looks like all examples have validated.

Failing due to #1000


Missing Server 2022 info

This page does not mention compatibility with Windows Server 2022. Jeff Woolsey mentioned the Storage Migration Service in the Server 2022 launch event, so I presume that it's compatible, but I hope you'll clarify.
Many thanks!

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

ID: 293dff88-4f13-d13a-bf54-4166598e0b81
Version Independent ID: 58d2fc54-4f15-a67b-94f3-197e2dac7bc7
Content: Storage Migration Service overview
Content Source: WindowsServerDocs/storage/storage-migration-service/overview.md
Product: windows-server
Technology: storage
GitHub Login: @JasonGerend
Microsoft Alias: jgerend

Compatibility with Windows Server 2022 now documented.
#please-close


Times are incorrect by 1 hour

I am on EST and have confirmed that my operating system date and time is correct and in the correct time zone (EST).  In Home Assistant configuration.yaml, I also have the correct time zone specified.
When I look at sun.sun in Developer Tools, I see:
next_dawn: 2022-01-26T11:49:05.209042+00:00
next_dusk: 2022-01-26T23:32:27.668985+00:00
next_midnight: 2022-01-26T05:40:39+00:00
next_noon: 2022-01-26T17:40:29+00:00
next_rising: 2022-01-26T12:13:44.614876+00:00
next_setting: 2022-01-26T23:07:48.178739+00:00
elevation: -26.91
azimuth: 260.96
rising: false
friendly_name: Sun
Since I am on EST, 5 hours behind UTC, I'd expect sun-card to show 7:13am and 6:07pm respectively for the next sunrise / sunset.  Instead, I see:

All the times are 6 hours behind the UTC times, as if daylight savings time is in effect.  With some other code using a value_template of {{ as_timestamp(states.sun.sun.attributes.next_rising) | timestamp_custom(' %I:%M %p') | replace(" 0", "") }}, I get the correct results:

Follow up to this.  The problem is because the card displays the times in the timezone of the user, not the timezone of the home assistant installation.  So in my case, the installation is on EST and I am viewing on a system set to CST.  Which has the consequence of displaying the incorrect times for these events.

Hi,
I'm having the same issue. Is there already a fix for this?

Hi,
I'm having the same issue. Is there already a fix for this?

See my comment above.  This is just how HA works.  There was apparently no thought that people would want to use a system in a different time zone, so instead of localizing the UI to pick up the user's current time zone, it just uses the system's time zone.  I worked around this by adding code to take care of it myself.

Thanks for the reply. I use HA now for two weeks so I’m still a noob. Used domoticz before. Where do I put the code?


brushes on disabled layers not marked as entities get merged with worldspawn when using TB groups hierarchy

when on FuncGodotMapSettings.use_trenchbroom_groups_hierarchy == true
if have a layer disabled on TB and there's geometry that is not marked as entity (ie func_whatever)
such geometry isn't discarded but merged with the worldspawn; it should be

that can be problematic because if have a layer "prefabs" with brushes, either standalone or grouped, that have no entity applied

then those will get merged on map build with worldspawn, forcing to either not have such layer on TB map, or to not use FuncGodotMapSettings.use_trenchbroom_groups_hierarchy

because once merged on the same MeshInstance node can't delete them
even deleting nodes manually after every map build is time waste.

This is a tough one, because of the way brushes and entities are handled. We decided that there are too many questions associated with how to handle Worldspawn split across multiple TrenchBroom layers and so what we settled on is that, since there is only 1 Worldspawn in a map file, there would be only 1 Worldspawn in a built map, so all Worldspawn brushes, regardless of their layer, would be merged out of those layers and into the entity_0_worldspawn.
We also just generally don't recommend using Worldspawn in general to make maps for Godot, due to a number of issues with that practice. It really only exists as a quick option for people to just quickly place a few brushes and build a map, to get started right away with something simple.
I'm not opposed to the goal, but it's a complicated ask. It will likely have to start in GeoGenerator to solve for it, but that is difficult in itself due to how the map file determines layers and layer settings.

Closing issue due to inactivity and no current plans to implement.
For anyone running into this issue, I recommend either moving your prefabs to a separate map file or converting them into brush entities in order to avoid them building with the rest of the map.
Anyone who absolutely needs FuncGodot to ignore worldspawn brushes on disabled layers is still welcome to submit a PR.


SvelteKit on Cloudflare requests not flushed

Bug description
I am using SvelteKit deployed on Cloudflare Pages. I try to log server side events but get a debug message for the capture but never for the flush and shutdown

My server side posthog client is as follows
import { PUBLIC_POSTHOG_KEY, PUBLIC_URL } from '$env/static/public';
import { PostHog } from 'posthog-node';

const client = new PostHog(PUBLIC_POSTHOG_KEY, {
	flushAt: 1,
	flushInterval: 0,
	disableGeoip: false,
	fetch: fetch,
	enable: !PUBLIC_URL.includes('localhost') && !PUBLIC_URL.includes('dev')
});

client.debug(true);

export default client;

Environment
@sveltejs/kit 2.5.0
@sveltejs/adapter-cloudflare 4.1.0
posthog-node 3.6.3
Related sub-libraries

[ ] All of them
[ ] posthog-web
[X] posthog-node
[ ] posthog-react-native

Additional context
Thank you for your bug report – we love squashing them! (No problem. You guys are doing a great job)

@benjackwhite maybe https://github.com/PostHog/posthog-js-lite/pull/191 will help?
Seems like the flush was never called or the queue was still 0.

Is there a way I can check that to narrow down the scope of the problem?

Is there a way I can check that to narrow down the scope of the problem?

We're going to release the first preview of the new major version, then you can test it out again, https://github.com/PostHog/posthog-js-lite/pull/191 and some other improvements should have helped.

@Pelps12 https://www.npmjs.com/package/posthog-node/v/4.0.0-beta.1

https://www.npmjs.com/package/posthog-node/v/4.0.0-beta.2 should also help, check the changelog in case you need to do a migration from v3 to v4.
Closing this as possibly fixed, let us know if that's not the case.


Glow At Countdown Time doesn't reset

Hey Britt,
Upgraded to 3.0 (Was super easy to copy over my settings because I'm a brain dead Holy Paladin) and was just going through the new options. I decided to test out the glow time because with my previous frames I would have them change colors based on glimmer duration and thought this would be a good replacement. I noticed that when reapplying the HoT to the target the glow time doesn't reset. And unlike my previous ticket, I supplied pictures this time. I'll be sure to submit more tickets if anything else pops up. Thank you.

Nice catch, I'll sort it out and fix it asap. Thanks for testing and reporting!

Hrm, on a side note... There should be a profile option in the sidebar under Enhanced Raid Frames right after Icon Options... Hrm... That's concerning...


feat: add robosense support

PR Type

New Feature

Related Links

The issue: https://github.com/tier4/nebula/issues/76
Description

This change proposes Robosense Helios and Bpearl support for nebula.
Review Procedure

It is still in progress.
Remarks

Pre-Review Checklist for the PR Author
PR Author should check the checkboxes below when creating the PR.

[ ] Assign PR to reviewer

Checklist for the PR Reviewer
Reviewers should check the checkboxes below before approval.

[ ] Commits are properly organized and messages are according to the guideline
[ ] (Optional) Unit tests have been written for new behavior
[ ] PR title describes the changes

Post-Review Checklist for the PR Author
PR Author should check the checkboxes below before merging.

[ ] All open points are addressed and tracked via issues or tickets

CI Checks

Build and test for PR: Required to pass before the merge.

Codecov Report
Patch coverage has no change and project coverage change: +1.74% :tada:

Comparison is base (ea482a8) 9.93% compared to head (69eac4c) 11.67%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff            @@
##            main      #77      +/-   ##
=========================================
+ Coverage   9.93%   11.67%   +1.74%
=========================================
  Files        118       64      -54
  Lines      10147     8052    -2095
  Branches    1533     1517      -16
=========================================
- Hits        1008      940      -68
+ Misses      8034     6011    -2023
+ Partials    1105     1101       -4

Flag
Coverage Δ

differential
11.67% <0.00%> (?)

total
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed
Coverage Δ

...ula_common/include/nebula_common/nebula_common.hpp
0.00% <ø> (ø)

...src/nebula_decoders_robosense/robosense_driver.cpp
0.00% <0.00%> (ø)

...robosense_hw_interfaces/robosense_hw_interface.cpp
0.00% <0.00%> (ø)

...c/robosense/robosense_hw_interface_ros_wrapper.cpp
0.00% <0.00%> (ø)

... and 57 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Hello, I have been working on this for some time. I have managed to get a point cloud with Helios 5515. It is still work in progress and I wanted to share an update. I tried to follow Hesai part.
Robosense has a different byte order than Hesai, it is big-endian. So, direct memcpy into a struct doesn't work. I have used Boost.Endian library to cope with byte order issue.
There are some hard coded parts for timestamps and return modes for now, I am working on them.
Helios 5515 and Bpearl 3.0 support configuration only via web interface, so it seems not possible to implement setup sensor part.
Here is an image of a Helios point cloud: (I haven't applied correction values yet)

Hello @drwnz @amc-nu @mojomex , I have completed for Helios and I think it is ready for review. I will continue with Bpearl and waiting your feedbacks.
Thank you

Hello @mojomex , thank you for the feedback! I am working on them.
Here is the pcap file: https://drive.google.com/file/d/1xfm1kB3YZQ5n4Ur9A7B76Aw1jeI_r3GJ/view?usp=drive_link
For Helios:
    <arg name="sensor_ip" default="<IP_ADDRESS>" description="Lidar Sensor IP"/>
    <arg name="host_ip" default="<IP_ADDRESS>" description="Broadcast IP from Sensor"/>
    <arg name="data_port" default="2011" description="LiDAR Data Port"/>
    <arg name="gnss_port" default="3011" description="LiDAR GNSS Port"/>

For Bpearl (It hasn't been added yet.):
    <arg name="sensor_ip" default="<IP_ADDRESS>" description="Lidar Sensor IP"/>
    <arg name="host_ip" default="<IP_ADDRESS>" description="Broadcast IP from Sensor"/>
    <arg name="data_port" default="2010" description="LiDAR Data Port"/>
    <arg name="gnss_port" default="3010" description="LiDAR GNSS Port"/>

Hello @mojomex @drwnz @amc-nu , I worked on the current feedback and added Bpearl also. The provided pcap file has both Helios and Bpearl.
About the MTU_SIZE and MAX_SCAN_BUFFER_POINTS, I am not sure how to calculate them. Do you have a suggestion for that?
I am waiting your further comments.
Thank you!

Hi, I just tested the driver with the PCAP file and for Helios it works perfectly. For Bpearl, it outputs the pointclouds but logs [robosense_cloud]: Timestamp error, verify clock source. ~10 times per second, i.e. for every scan. Could you look into this @mebasoglu?
Thank you!

About the MTU_SIZE and MAX_SCAN_BUFFER_POINTS, I am not sure how to calculate them. Do you have a suggestion for that?

As for MAX_SCAN_BUFFER_POINTS, this number should correspond to the theoretical maximum number of points in one scan. This is usually given in the datasheet under 'specifications' or similar. In case of Bpearl:

Number of Output Points | 576000 pts / s (Single Return Mode), 1152000 pts / s (Dual Return Mode)

The formula would be $N = f \cdot (FoV \div r_H) \cdot n_C \cdot n_R = 10 Hz \cdot (360^{\circ} \div 0.2^{\circ}) \cdot 32 \cdot 2 = 1152000 \frac{1}{s}$
where $N$ is MAX_SCAN_BUFFER_POINTS, $f$ is the frequency the sensor is running at, $FoV$ is the field of view, $r_H$ is the horizontal angular resolution, $n_C$ is the number of channels and $n_R$ is the maximum number of returns the sensor supports.
This number remains constant even for different framerates as the horizontal resolution is inversely proportional to the framerate.
As for MTU_SIZE, all packets sent by the sensor are 1248 B as far as I can tell, so leaving MTU at the default 1500 is fine.

Hello, it seems we have two different Bpearl models, v3.0 and v4.0 at the office. While transitioning to v4.0, some packet definitions have changed such as time stamp. The warning that @mojomex got about timestamps is also because of that. I am working on these different versions of Bpearl. I will let you know when it is completed.

Hello @mojomex , thank you for the feedback.
I fixed the parts excluding timestamp issue, I am working on that currently.

Hello again @mojomex , I have found the problem. I used nanoseconds instead of microseconds while decoding timestamp, although it says microseconds on the manual. It should be fine right now.
Also, for the spellcheck test, Idat and Vdat current and voltage words are failing. Should I add them to the list also or is it okay for them to fail?

Hello @mojomex , we received a firmware update for our Bpearl v4 from Robsense, the time synchronization didn't work before.
Currently, we started using the driver one of our projects, I think it is ready for a full review.
I have recorded new pcap files here: https://drive.google.com/drive/folders/1YNdhyhujirSQaI-NSMjTSoDZi2vt9OC5
All the destination addresses were rewriten as broadcast.
Here are the configurations:

helios_rewrited.pcapng
Time sync: GPRMC+PPS

    <arg name="sensor_model" default="Helios" description="Helios|Bpearl"/>
    <arg name="sensor_ip" default="<IP_ADDRESS>" description="Lidar Sensor IP"/>
    <arg name="host_ip" default="<IP_ADDRESS>" description="Broadcast IP from Sensor"/>
    <arg name="data_port" default="2010" description="LiDAR Data Port"/>
    <arg name="gnss_port" default="3010" description="LiDAR GNSS Port"/>

bpearlv4_rewrited.pcapng
Time sync: GPRMC+PPS

    <arg name="sensor_model" default="Bpearl" description="Helios|Bpearl"/>
    <arg name="sensor_ip" default="<IP_ADDRESS>" description="Lidar Sensor IP"/>
    <arg name="host_ip" default="<IP_ADDRESS>" description="Broadcast IP from Sensor"/>
    <arg name="data_port" default="2010" description="LiDAR Data Port"/>
    <arg name="gnss_port" default="3010" description="LiDAR GNSS Port"/>

helios-gprmc-bpearl-pps_rewrited.pcapng
We have one Helios and two Bpearls in this pcap.

Helios time sync: GPRMC+PPS
    <arg name="sensor_model" default="Helios" description="Helios|Bpearl"/>
    <arg name="sensor_ip" default="<IP_ADDRESS>" description="Lidar Sensor IP"/>
    <arg name="host_ip" default="<IP_ADDRESS>" description="Broadcast IP from Sensor"/>
    <arg name="data_port" default="2011" description="LiDAR Data Port"/>
    <arg name="gnss_port" default="3011" description="LiDAR GNSS Port"/>

Bpearl v3 1 time sync: PPS only
    <arg name="sensor_model" default="Bpearl" description="Helios|Bpearl"/>
    <arg name="sensor_ip" default="<IP_ADDRESS>" description="Lidar Sensor IP"/>
    <arg name="host_ip" default="<IP_ADDRESS>" description="Broadcast IP from Sensor"/>
    <arg name="data_port" default="2010" description="LiDAR Data Port"/>
    <arg name="gnss_port" default="3010" description="LiDAR GNSS Port"/>

Bpearlv3 2 time sync: PPS only
    <arg name="sensor_model" default="Bpearl" description="Helios|Bpearl"/>
    <arg name="sensor_ip" default="<IP_ADDRESS>" description="Lidar Sensor IP"/>
    <arg name="host_ip" default="<IP_ADDRESS>" description="Broadcast IP from Sensor"/>
    <arg name="data_port" default="2012" description="LiDAR Data Port"/>
    <arg name="gnss_port" default="3012" description="LiDAR GNSS Port"/>

Hello @mojomex , thank you for the great feedback. I am working on the channel problem for Bpearl and will have a look at the other things. I will let you know when I am done. Thank you ❤

After consulting with @drwnz, we should probably introduce a static mapping from orig_ring to ring.
The datasheet's appendix E has a table of channel/elevation, so sorting that by elevation should yield this mapping!

@mebasoglu @mojomex regarding the timestamping - I checked with Robosense, and they do not currently support time-based scan phase synchronization like Hesai does. It sounds like it is possible to update though, so I will continue to follow up with them, but for now we don't have to worry about the timestamps not aligning with ToS.

Hello @mojomex @drwnz ,
Since correction angles are different for each sensor, it seems the order of the rings are also different. Sorting calibration data descending by vertical angles and creating corrected channels numbers with the new indexes solves the ring problem.

Apart from these, one thing I missed is the PTP synchronization. I only checked utc_time flag for sensor timestamp, and it only represents GPRMC synchronization. I am going to push one more commit to handle PTP sync also.

Hello @mojomex @drwnz ,
I pushed a commit to handle PTP time synchronization also.
About the version question, on the web interface of Bpearl v3, it says "Hardware version" is v3. So it is a hardware improvement also for v4.


Font family in custom themes

Hi, thanks for the fantastic library.
I feel like I am missing something obvious, I'm looking at building a custom theme and defining the font family for the theme, like some of the inbuilt themes do (wireframe for example).
I've found the definitions of the inbuilt themes and they use the "fontFamily" key, but when I add this to my custom theme, nothing happens.
Is this possible?
Thanks

Sorry for wasting your time, that works perfectly, I just wasn't passing the config in correctly.
Thanks!

@tom-acceleratecompliance Good.
Here's an example, if anyone else looking for that:
https://play.tailwindcss.com/QtVDNrydis?file=config


won't compile on debian linux

I just bought a fancy Slamtec RPLIDAR A1 - 360 Laser Range Scanner from adafruit
this led me here to clone and make this project trying to run the ultra simple demo -
in the sdk dir i run make - i have g++ installed - errors below error code was:
make: *** [/home/ben/code/rplidar_sdk/sdk/mak_common.inc:43: make_subs] Error 1
ake[1]: Entering directory '/home/ben/code/rplidar_sdk/sdk/sdk'
 CXX  src/rplidar_driver.cpp
src/rplidar_driver.cpp: In member function ‘virtual int rp::standalone::rplidar::RPlidarDriverImplCommon::_getSyncBitByAngle(int, int)’:
src/rplidar_driver.cpp:671:16: warning: variable ‘last_angleInc_q16’ set but not used [-Wunused-but-set-variable]
  671 |     static int last_angleInc_q16 = 0;
      |                ^~~~~~~~~~~~~~~~~
src/rplidar_driver.cpp:673:9: warning: unused variable ‘syncBit_check_threshold’ [-Wunused-variable]
  673 |     int syncBit_check_threshold = (int)((5 << 16) / angleInc_q16) + 1;//find syncBit in 0~3 degree
      |         ^~~~~~~~~~~~~~~~~~~~~~~
src/rplidar_driver.cpp: In member function ‘virtual u_result rp::standalone::rplidar::RPlidarDriverImplCommon::_cacheUltraCapsuledScanData()’:
src/rplidar_driver.cpp:771:46: warning: unused variable ‘last_scan_count’ [-Wunused-variable]
  771 |     size_t                                   last_scan_count = 0;
      |                                              ^~~~~~~~~~~~~~~
src/rplidar_driver.cpp: In member function ‘virtual void rp::standalone::rplidar::RPlidarDriverImplCommon::_capsuleToNormal(const rplidar_response_capsule_measurement_nodes_t&, rplidar_response_measurement_node_hq_t*, size_t&)’:
src/rplidar_driver.cpp:850:17: warning: unused variable ‘syncBit_check_threshold’ [-Wunused-variable]
  850 |             int syncBit_check_threshold = (int)((2 << 16) / angleInc_q16) + 1;//find syncBit in 0~1 degree
      |                 ^~~~~~~~~~~~~~~~~~~~~~~
src/rplidar_driver.cpp: In function ‘_u32 rp::standalone::rplidar::_crc32cal(_u32, void*, _u16)’:
src/rplidar_driver.cpp:1027:23: warning: suggest parentheses around ‘-’ in operand of ‘&’ [-Wparentheses]
 1027 |     _u8 leftBytes = 4 - len & 0x3;
      |                     ~~^~~~~
src/rplidar_driver.cpp: In member function ‘virtual void rp::standalone::rplidar::RPlidarDriverImplCommon::_ultraCapsuleToNormal(const rplidar_response_ultra_capsule_measurement_nodes_t&, rplidar_response_measurement_node_hq_t*, size_t&)’:
src/rplidar_driver.cpp:1238:32: warning: comparison of integer expressions of different signedness: ‘int’ and ‘unsigned int’ [-Wsign-compare]
 1238 |             if ((dist_predict1 == 0xFFFFFE00) || (dist_predict1 == 0x1FF)) {
      |                  ~~~~~~~~~~~~~~^~~~~~~~~~~~~
src/rplidar_driver.cpp:1246:32: warning: comparison of integer expressions of different signedness: ‘int’ and ‘unsigned int’ [-Wsign-compare]
 1246 |             if ((dist_predict2 == 0xFFFFFE00) || (dist_predict2 == 0x1FF)) {
      |                  ~~~~~~~~~~~~~~^~~~~~~~~~~~~
src/rplidar_driver.cpp:1256:21: warning: unused variable ‘syncBit_check_threshold’ [-Wunused-variable]
 1256 |                 int syncBit_check_threshold = (int)((3 << 16) / angleInc_q16)+1;//find syncBit in 0~1 degree
      |                     ^~~~~~~~~~~~~~~~~~~~~~~
src/rplidar_driver.cpp: In member function ‘virtual u_result rp::standalone::rplidar::RPlidarDriverImplCommon::grabScanData(rplidar_response_measurement_node_t*, size_t&, _u32)’:
src/rplidar_driver.cpp:1826:26: error: narrowing conversion of ‘rp::hal::Event::EVENT_TIMEOUT’ from ‘int’ to ‘long unsigned int’ [-Wnarrowing]
 1826 |     case rp::hal::Event::EVENT_TIMEOUT:
      |                          ^~~~~~~~~~~~~
src/rplidar_driver.cpp: In member function ‘virtual u_result rp::standalone::rplidar::RPlidarDriverImplCommon::grabScanDataHq(rplidar_response_measurement_node_hq_t*, size_t&, _u32)’:
src/rplidar_driver.cpp:1855:26: error: narrowing conversion of ‘rp::hal::Event::EVENT_TIMEOUT’ from ‘int’ to ‘long unsigned int’ [-Wnarrowing]
 1855 |     case rp::hal::Event::EVENT_TIMEOUT:
      |                          ^~~~~~~~~~~~~
src/rplidar_driver.cpp: In member function ‘virtual u_result rp::standalone::rplidar::RPlidarDriverImplCommon::startMotor()’:
src/rplidar_driver.cpp:2222:26: warning: control reaches end of non-void function [-Wreturn-type]
 2222 |         setLidarSpinSpeed(600);//set default rpm to tof lidar
      |         ~~~~~~~~~~~~~~~~~^~~~~
make[1]: *** [/home/ben/code/rplidar_sdk/sdk/mak_common.inc:82: /home/ben/code/rplidar_sdk/sdk/obj/Linux/Release/sdk/src/rplidar_driver.o] Error 1
make[1]: Leaving directory '/home/ben/code/rplidar_sdk/sdk/sdk'
make: *** [/home/ben/code/rplidar_sdk/sdk/mak_common.inc:43: make_subs] Error 1

I just hit the same error. Making this change to event.h got it to compile and the demos are now running properly for me:
diff --git a/sdk/sdk/src/hal/event.h b/sdk/sdk/src/hal/event.h
index 5e05234..f25d5ac 100644
--- a/sdk/sdk/src/hal/event.h
+++ b/sdk/sdk/src/hal/event.h
@@ -42,7 +42,7 @@ public:
enum
{
EVENT_OK = 1,

   EVENT_TIMEOUT = -1,

   EVENT_TIMEOUT = 2,
   EVENT_FAILED = 0,

};

Thanks - i ended up tossing out the rplidar USB adapter which also seemed defective on arrival and used an arduino to read from the RPLIDAR which worked out - there are several libraries out there and you just need a serial port

For people coming to this error now, the current code in master has 0xFFFFFFFFFFFFFFFF for the value of EVENT_TIMEOUT instead of -1. However, v1.12.0 and below still contain this error (or at least v1.11.0, the version on slamtech.com, still does).
In short, if you're compiling on a Raspberry Pi: clone master, don't use the release tags.
https://github.com/Slamtec/rplidar_sdk/blob/9d85aae434d39fc4014018dcbf8711f8918b0254/sdk/src/hal/event.h#L46

For those curious the offending line in master currently has EVENT_TIMEOUT set to 0xFFFFFFFFFFFF instead of -1 but that's still giving me problems on my RPI 3A+. No problems on Ubuntu 20.04 though... Setting the enum to 2 fixes the issue. Haven't figured out why. #54 probably fixes this issue.


How Do I run the training?

Hi, I'm still new in AI, and I want to use audiolm-pytorch to train to another language,
can you explain more after I put the dataset and download hubert checkpoint, so what should I do?
What do you mean in the README,
-- Create a directory for the sample file
mkdir many_identical_copies_of_cocochorales_single_sample_resampled_24kHz_trimmed_first_second
Do I put my samples voice 24khz in that folder, and what script should I run next to get the result?
Really appreciate for you help

I found it, using sbatch_job.sh. thanks


Get Travis working

Does the caching give us any performance advantage? When I tried it in the Slick build it didn't make a difference. There seems to be an upstream cache anyway so that resolving is fast.

The benefit is in not needing to update the cache every time for useless, noisy changes, only updating dependency versions or sbt version. I've never fully tested it to be honest, and also things change over time.

I have found enabling the caching feature to be a noticeable speed benefit in a variety of other repos.

otoh, in a small repo like this it probably doesn't matter much either way.

Well it's done, and it's a small change. Not sure if you're exactly contesting it or not, but I'm happy to drop it if preferred, no sweat.

I'd be fine merging as-is, but I'll let @szeiger make the call.

I don't have a strong opinion. I've neither seen substantial performance improvements nor problems caused by caching. Let's give it a try.

thank you Dale!

No worries. Thanks for the merge.


Do we need source-map-support when node can support this by --enable-source-maps ?

perhaps not, just following the docs https://remix.run/docs/en/main/start/v2#source-map-support


chore(package): update rollup to version 0.49.1

Closes #280

Codecov Report

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

@@           Coverage Diff           @@
##           master     #282   +/-   ##
=======================================
  Coverage   89.25%   89.25%
=======================================
  Files           1        1
  Lines         214      214
=======================================
  Hits          191      191
  Misses         23       23

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 09ab8ec...c0e1130. Read the comment docs.


user state is causing user.name memory scope null.

Github issues should be used for bugs and feature requests. Use Stack Overflow for general "how-to" questions.
Version
What package version of the SDK are you using.
Describe the bug
var test = _userState.CreateProperty("UserProfile").GetAsync(turnContext, () => new UserProfile());
after adding this line all the mapping with user scope is becoming null.
return this.dialogManager.OnTurnAsync(turnContext, cancellationToken: cancellationToken);
To Reproduce
Steps to reproduce the behavior:
added the userstate accessor in https://github.com/microsoft/botbuilder-dotnet/blob/4.Future/tests/Microsoft.Bot.Builder.TestBot.Json/TestBot.cs
run the 4 sample it will give null for user.name
Expected behavior
Give a clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
[bug]

Assigning to @stevenic as this is adaptive in 4.Future branch.

is  there any work around for this bug. what is the ETA . let me know if you need any more info regarding this bug.

This doesn't repro on current branch.

Hi @tomlm I am still able to reproduce with latest code.
in project Microsoft.Bot.Builder.TestBot.Json  in file TestBot.cs i have added only this line of code
var test = _userState.CreateProperty("UserProfile").GetAsync(turnContext, () => new UserProfile());
let me know if i am missing something.

Reopening per @som-nitjsr's comment
Closing microsoft/botbuilder-dotnet#2636 as that is a dupe.

I finally was able to reproduce this, subtle bug, thanks for the persistence @som-nitjsr !

Thanks @tomlm  fix is working.

Addressed via #2642


Bug: Ion-Textarea toggles and losses focus everytime on tap

Ionic version:  (check one with "x")
[ ] 1.x
[x ] 2.x
I'm submitting a ...  (check one with "x")
[ x] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
Clicking/tapping on textarea toggles focus and keyboard.
Expected behavior:
When tap occurs, if the focus/keyboard is not shown -> show keyboard and focus input. If the textarea has focus and keyboard is open -> tap on ion-textarea should not loose focus and close keyboard, instead should allow user to change the location of cursor and select text in textarea.
Steps to reproduce:
Just create a ion-textarea and try in android
-->
Related code:
<ion-textarea class="name-input"
                  placeholder="name"
                  [(ngModel)]="name"></ion-textarea>

EDIT: I tested by wrapping ion-textarea with ion-item and it works fine.

Thanks, we will look into this.

+1

the same problem
+1

same problem in ionic 3.19.0
+1

confirm glitch also, 3.19.1

https://github.com/ionic-team/ionic/issues/5744#issuecomment-404232682


handle another^H^H^H^H^H^H^Hmore backwards compatibility regressions

This regression was in the ability to detect whether or not backends have changed or not. There is a likely future optimization in the Backend.fetch function but outside the scope of this PR.
Also added to the diff integration test to make sure we test the NOOP case.
And I have no idea how line 25 of the Makefile ever worked before but it works now (I'm assuming something on the coverage tool changed).
cc @fortinmath

[x] confirm if this regression is in ldap/userpass
[x] better test coverage on diff

I think we now have :100: test coveage of the diff action which is kind of cool. The last pr also fixes #162 (and we've added a smoke test to capture this scenario)


[BUG] - SFU not working on local

UE Version:
UE  5.4.0-33043543+++UE5+Release-5.4
Frontend Version:
UE5.4-1.0.1
Problem component
SFU
Description
I'm running all of the components on my local machine, everything works fine except SFU. Are the TURN/STUN servers required for the SFU to work?
The problem is that when I connect the player directly to the streamer, everything works fine and I get the stream, controls etc.
But when I try to run SFU, it gets stuck. Here is the the logs that SFU server generates:
Connecting to Signalling Server at ws://localhost:8889
Connected to signalling server
Got offer from streamer
[SdpEndpoint.processOffer] mediasoup Producer created, kind: video, type: simulcast, paused: false
[SdpEndpoint.processOffer] mediasoup Producer created, kind: audio, type: simple, paused: false
[SdpEndpoint.processOffer] SCTP association received
[SdpEndpoint.createAnswer] Make 'recvonly' SDP Answer
Sending answer to streamer.

And the log on the Signalling server:
23:14:52.420 SFU (::1) connected
23:14:52.420 ::1 <- {"type":"identify"}
23:14:52.424 ::1 -> {"type":"endpointId","id":"SFU"}
23:14:52.424 5 -> {"type":"listStreamers"}
23:14:52.424 5 <- {"type":"streamerList","ids":["DefaultStreamer"]}
23:14:52.425 5 -> {"type":"subscribe","streamerId":"DefaultStreamer"}
23:14:52.425 DefaultStreamer <- {"type":"playerConnected","playerId":"5","dataChannel":true,"sfu":true,"sendOffer":true}
23:14:52.514 DefaultStreamer -> 5 {"type":"offer","sdp":"v=0\r\no=-<PHONE_NUMBER>793849380 2 IN IP4 <IP_ADDRESS>\r\ns=-\r\nt=0 0\r\na=group:BUNDLE 0 1 2\r\na=extmap-allow-mixed\r\na=msid-semantic: WMS pixelstreaming_audio_stream_id pixelstreaming_video_stream_id\r\nm=video 9 UDP/TLS/RTP/SAVPF 96 97 98 99 100 101 102 103 104 105 106\r\nc=IN IP4 <IP_ADDRESS>\r\na=rtcp:9 IN IP4 <IP_ADDRESS>\r\na=ice-ufrag:1Rnh\r\na=ice-pwd:B2ri0A5wiIVHbvs1PAkgjviX\r\na=ice-options:trickle\r\na=fingerprint:sha-256 09:79:26:28:AB:94:43:CF:EA:BC:20:11:C3:BC:C6:42:B3:15:69:D4:57:AC:DE:A1:AA:69:6E:6A:EE:29:28:9D\r\na=setup:actpass\r\na=mid:0\r\na=extmap:1 urn:ietf:params:rtp-hdrext:toffset\r\na=extmap:2 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time\r\na=extmap:3 urn:3gpp:video-orientation\r\na=extmap:4 http://www.ietf.org/id/draft-holmer-rmcat-transport-wide-cc-extensions-01\r\na=extmap:5 http://www.webrtc.org/experiments/rtp-hdrext/playout-delay\r\na=extmap:6 http://www.webrtc.org/experiments/rtp-hdrext/video-content-type\r\na=extmap:7 http://www.webrtc.org/experiments/rtp-hdrext/video-timing\r\na=extmap:8 http://www.webrtc.org/experiments/rtp-hdrext/color-space\r\na=extmap:9 urn:ietf:params:rtp-hdrext:sdes:mid\r\na=extmap:10 urn:ietf:params:rtp-hdrext:sdes:rtp-stream-id\r\na=extmap:11 urn:ietf:params:rtp-hdrext:sdes:repaired-rtp-stream-id\r\na=sendonly\r\na=msid:pixelstreaming_video_stream_id pixelstreaming_video_track_label\r\na=rtcp-mux\r\na=rtcp-rsize\r\na=rtpmap:96 H264/90000\r\na=rtcp-fb:96 goog-remb\r\na=rtcp-fb:96 transport-cc\r\na=rtcp-fb:96 ccm fir\r\na=rtcp-fb:96 nack\r\na=rtcp-fb:96 nack pli\r\na=fmtp:96 level-asymmetry-allowed=1;packetization-mode=1;profile-level-id=42e01f\r\na=rtpmap:97 rtx/90000\r\na=fmtp:97 apt=96\r\na=rtpmap:98 H264/90000\r\na=rtcp-fb:98 goog-remb\r\na=rtcp-fb:98 transport-cc\r\na=rtcp-fb:98 ccm fir\r\na=rtcp-fb:98 nack\r\na=rtcp-fb:98 nack pli\r\na=fmtp:98 level-asymmetry-allowed=1;packetization-mode=1;profile-level-id=42001f\r\na=rtpmap:99 rtx/90000\r\na=fmtp:99 apt=98\r\na=rtpmap:100 VP8/90000\r\na=rtcp-fb:100 goog-remb\r\na=rtcp-fb:100 transport-cc\r\na=rtcp-fb:100 ccm fir\r\na=rtcp-fb:100 nack\r\na=rtcp-fb:100 nack pli\r\na=rtpmap:101 rtx/90000\r\na=fmtp:101 apt=100\r\na=rtpmap:102 VP9/90000\r\na=rtcp-fb:102 goog-remb\r\na=rtcp-fb:102 transport-cc\r\na=rtcp-fb:102 ccm fir\r\na=rtcp-fb:102 nack\r\na=rtcp-fb:102 nack pli\r\na=rtpmap:103 rtx/90000\r\na=fmtp:103 apt=102\r\na=rtpmap:104 red/90000\r\na=rtpmap:105 rtx/90000\r\na=fmtp:105 apt=104\r\na=rtpmap:106 ulpfec/90000\r\na=rid:simulcast3 send\r\na=rid:simulcast2 send\r\na=rid:simulcast1 send\r\na=simulcast:send simulcast3;simulcast2;simulcast1\r\nm=audio 9 UDP/TLS/RTP/SAVPF 111 63 110\r\nc=IN IP4 <IP_ADDRESS>\r\na=rtcp:9 IN IP4 <IP_ADDRESS>\r\na=ice-ufrag:1Rnh\r\na=ice-pwd:B2ri0A5wiIVHbvs1PAkgjviX\r\na=ice-options:trickle\r\na=fingerprint:sha-256 09:79:26:28:AB:94:43:CF:EA:BC:20:11:C3:BC:C6:42:B3:15:69:D4:57:AC:DE:A1:AA:69:6E:6A:EE:29:28:9D\r\na=setup:actpass\r\na=mid:1\r\na=extmap:14 urn:ietf:params:rtp-hdrext:ssrc-audio-level\r\na=extmap:2 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time\r\na=extmap:4 http://www.ietf.org/id/draft-holmer-rmcat-transport-wide-cc-extensions-01\r\na=extmap:9 urn:ietf:params:rtp-hdrext:sdes:mid\r\na=sendonly\r\na=msid:pixelstreaming_audio_stream_id pixelstreaming_audio_track_label\r\na=rtcp-mux\r\na=rtpmap:111 opus/48000/2\r\na=rtcp-fb:111 transport-cc\r\na=fmtp:111 maxaveragebitrate=510000;maxplaybackrate=48000;minptime=3;sprop-stereo=1;stereo=1;usedtx=0;useinbandfec=1\r\na=rtpmap:63 red/48000/2\r\na=fmtp:63 111/111\r\na=rtpmap:110 telephone-event/48000\r\na=maxptime:120\r\na=ptime:20\r\na=ssrc:1436041484 cname:mJiLjwjcGea+bmk9\r\na=ssrc:1436041484 msid:pixelstreaming_audio_stream_id pixelstreaming_audio_track_label\r\nm=application 9 UDP/DTLS/SCTP webrtc-datachannel\r\nc=IN IP4 <IP_ADDRESS>\r\na=ice-ufrag:1Rnh\r\na=ice-pwd:B2ri0A5wiIVHbvs1PAkgjviX\r\na=ice-options:trickle\r\na=fingerprint:sha-256 09:79:26:28:AB:94:43:CF:EA:BC:20:11:C3:BC:C6:42:B3:15:69:D4:57:AC:DE:A1:AA:69:6E:6A:EE:29:28:9D\r\na=setup:actpass\r\na=mid:2\r\na=sctp-port:5000\r\na=max-message-size:262144\r\n"}
23:14:52.529 SFU -> DefaultStreamer {"type":"answer","sdp":"v=0\r\no=mediasoup-client 10000 1 IN IP4 <IP_ADDRESS>\r\ns=-\r\nt=0 0\r\na=ice-lite\r\na=fingerprint:sha-512 DE:6E:54:CB:85:F8:DD:17:95:24:81:B4:C7:A2:E5:2A:50:75:CD:9A:BE:44:4E:04:21:A3:23:F0:CA:98:76:7D:9C:AC:C5:A9:4A:C6:CB:66:6A:1C:41:49:46:6E:E7:32:9D:2D:39:91:CA:C8:FD:C6:5F:19:DB:05:7F:F3:20:27\r\na=msid-semantic: WMS *\r\na=group:BUNDLE 0 1 2\r\nm=video 7 UDP/TLS/RTP/SAVPF 100 101 96 97\r\nc=IN IP4 <IP_ADDRESS>\r\na=rtpmap:100 VP8/90000\r\na=rtpmap:101 rtx/90000\r\na=rtpmap:96 H264/90000\r\na=rtpmap:97 rtx/90000\r\na=fmtp:100 packetization-mode=1;profile-level-id=42e01f;level-asymmetry-allowed=1\r\na=fmtp:101 apt=100\r\na=fmtp:96 packetization-mode=1;level-asymmetry-allowed=1;profile-level-id=42e01f\r\na=fmtp:97 apt=96\r\na=rtcp-fb:100 transport-cc \r\na=rtcp-fb:100 ccm fir\r\na=rtcp-fb:100 nack \r\na=rtcp-fb:100 nack pli\r\na=rtcp-fb:96 transport-cc \r\na=rtcp-fb:96 ccm fir\r\na=rtcp-fb:96 nack \r\na=rtcp-fb:96 nack pli\r\na=extmap:9 urn:ietf:params:rtp-hdrext:sdes:mid\r\na=extmap:10 urn:ietf:params:rtp-hdrext:sdes:rtp-stream-id\r\na=extmap:11 urn:ietf:params:rtp-hdrext:sdes:repaired-rtp-stream-id\r\na=extmap:2 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time\r\na=extmap:4 http://www.ietf.org/id/draft-holmer-rmcat-transport-wide-cc-extensions-01\r\na=extmap:3 urn:3gpp:video-orientation\r\na=extmap:1 urn:ietf:params:rtp-hdrext:toffset\r\na=setup:active\r\na=mid:0\r\na=recvonly\r\na=ice-ufrag:8bpyk2cr0tqp19gi\r\na=ice-pwd:aljwmguh6bgfrr2s3yopb5z6zsxs0o3p\r\na=candidate:udpcandidate 1 udp<PHONE_NUMBER> <IP_ADDRESS> 40196 typ host\r\na=end-of-candidates\r\na=ice-options:renomination\r\na=rtcp-mux\r\na=rtcp-rsize\r\na=rid:simulcast3 recv\r\na=rid:simulcast2 recv\r\na=rid:simulcast1 recv\r\na=simulcast:recv simulcast3;simulcast2;simulcast1\r\nm=audio 7 UDP/TLS/RTP/SAVPF 111\r\nc=IN IP4 <IP_ADDRESS>\r\na=rtpmap:111 opus/48000/2\r\na=rtcp-fb:111 transport-cc \r\na=extmap:9 urn:ietf:params:rtp-hdrext:sdes:mid\r\na=extmap:2 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time\r\na=extmap:4 http://www.ietf.org/id/draft-holmer-rmcat-transport-wide-cc-extensions-01\r\na=extmap:14 urn:ietf:params:rtp-hdrext:ssrc-audio-level\r\na=setup:active\r\na=mid:1\r\na=recvonly\r\na=ice-ufrag:8bpyk2cr0tqp19gi\r\na=ice-pwd:aljwmguh6bgfrr2s3yopb5z6zsxs0o3p\r\na=candidate:udpcandidate 1 udp<PHONE_NUMBER> <IP_ADDRESS> 40196 typ host\r\na=end-of-candidates\r\na=ice-options:renomination\r\na=rtcp-mux\r\na=rtcp-rsize\r\nm=application 7 UDP/DTLS/SCTP webrtc-datachannel\r\nc=IN IP4 <IP_ADDRESS>\r\na=setup:active\r\na=mid:2\r\na=ice-ufrag:8bpyk2cr0tqp19gi\r\na=ice-pwd:aljwmguh6bgfrr2s3yopb5z6zsxs0o3p\r\na=candidate:udpcandidate 1 udp<PHONE_NUMBER> <IP_ADDRESS> 40196 typ host\r\na=end-of-candidates\r\na=ice-options:renomination\r\na=sctp-port:5000\r\na=max-message-size:262144\r\n"}
23:14:52.547 DefaultStreamer -> 5 {"type":"iceCandidate","candidate":{"sdpMid":"0","sdpMLineIndex":0,"candidate":"..."}}
23:14:52.581 DefaultStreamer -> 5 {"type":"iceCandidate","candidate":{"sdpMid":"0","sdpMLineIndex":0,"candidate":"..."}}
23:14:52.614 DefaultStreamer -> 5 {"type":"iceCandidate","candidate":{"sdpMid":"0","sdpMLineIndex":0,"candidate":"..."}}
23:14:52.648 DefaultStreamer -> 5 {"type":"iceCandidate","candidate":{"sdpMid":"0","sdpMLineIndex":0,"candidate":"..."}}
23:14:52.681 DefaultStreamer -> 5 {"type":"iceCandidate","candidate":{"sdpMid":"0","sdpMLineIndex":0,"candidate":"..."}}
23:14:52.714 DefaultStreamer -> 5 {"type":"iceCandidate","candidate":{"sdpMid":"0","sdpMLineIndex":0,"candidate":"..."}}
23:14:52.748 DefaultStreamer -> 5 {"type":"iceCandidate","candidate":{"sdpMid":"1","sdpMLineIndex":1,"candidate":"..."}}
23:14:52.782 DefaultStreamer -> 5 {"type":"iceCandidate","candidate":{"sdpMid":"1","sdpMLineIndex":1,"candidate":"..."}}
23:14:52.815 DefaultStreamer -> 5 {"type":"iceCandidate","candidate":{"sdpMid":"1","sdpMLineIndex":1,"candidate":"..."}}
23:14:52.849 DefaultStreamer -> 5 {"type":"iceCandidate","candidate":{"sdpMid":"1","sdpMLineIndex":1,"candidate":"..."}}
23:14:52.883 DefaultStreamer -> 5 {"type":"iceCandidate","candidate":{"sdpMid":"1","sdpMLineIndex":1,"candidate":"..."}}
23:14:52.917 DefaultStreamer -> 5 {"type":"iceCandidate","candidate":{"sdpMid":"1","sdpMLineIndex":1,"candidate":"..."}}
23:14:52.950 DefaultStreamer -> 5 {"type":"iceCandidate","candidate":{"sdpMid":"2","sdpMLineIndex":2,"candidate":"..."}}
23:14:52.984 DefaultStreamer -> 5 {"type":"iceCandidate","candidate":{"sdpMid":"2","sdpMLineIndex":2,"candidate":"..."}}
23:14:53.017 DefaultStreamer -> 5 {"type":"iceCandidate","candidate":{"sdpMid":"2","sdpMLineIndex":2,"candidate":"..."}}
23:14:53.052 DefaultStreamer -> 5 {"type":"iceCandidate","candidate":{"sdpMid":"2","sdpMLineIndex":2,"candidate":"..."}}
23:14:53.085 DefaultStreamer -> 5 {"type":"iceCandidate","candidate":{"sdpMid":"2","sdpMLineIndex":2,"candidate":"..."}}
23:14:53.119 DefaultStreamer -> 5 {"type":"iceCandidate","candidate":{"sdpMid":"2","sdpMLineIndex":2,"candidate":"..."}}
23:14:53.153 DefaultStreamer -> 5 {"type":"iceCandidate","candidate":{"sdpMid":"0","sdpMLineIndex":0,"candidate":"..."}}
23:14:53.187 DefaultStreamer -> 5 {"type":"iceCandidate","candidate":{"sdpMid":"0","sdpMLineIndex":0,"candidate":"..."}}
23:14:53.220 DefaultStreamer -> 5 {"type":"iceCandidate","candidate":{"sdpMid":"0","sdpMLineIndex":0,"candidate":"..."}}
23:14:53.254 DefaultStreamer -> 5 {"type":"iceCandidate","candidate":{"sdpMid":"0","sdpMLineIndex":0,"candidate":"..."}}
23:14:53.287 DefaultStreamer -> 5 {"type":"iceCandidate","candidate":{"sdpMid":"0","sdpMLineIndex":0,"candidate":"..."}}
23:14:53.321 DefaultStreamer -> 5 {"type":"iceCandidate","candidate":{"sdpMid":"0","sdpMLineIndex":0,"candidate":"..."}}

I put some code on the streamer offer process, and here is the result (It's a GIF):

Also, I changed some parts of the code to allow the player to connect to the Mediasoup producers without waiting for the streamer, and did the same thing and logged the stats, on the player side there were some packet transfers so I'm assuming that the player side is OK.
I'm a novice in the Mediasoup and WebRTC, but I searched for this issue for a while, and I was wondering, is it normal that the SFU is ignoring the ICE candidate request? I tried searching for this and found that the Mediasoup WebRTC doesn't have any way of parsing the ICE data, but why does the Plugin send the ICE data to the signaling, even though it knows that the Player that is connected is SFU?
Steps to Reproduce:

Download the release from Github
Follow the instructions on setting up the components

Install packages and build-dev on frontend/lib folder
Install packages, link the lib folder and build-dev on frontend/ui-library folder
Install packages, link the lib+ui-library folder and build-dev on frontend/implementations/typescript folder
Install set the configure the app and run using serve command on frontend/implementations/typescript folder

Install dependencies and run the signalling server
Configure and run SFU server with <IP_ADDRESS> as public IP
The SFU is stuck at a certain point!

Expected behavior

SFU connects and streams data to player without issue!

Screenshots
UE logs:

Platform (please complete the following information):

OS: Windows 11
Browser: Chrome 124

Are the TURN/STUN servers required for the SFU to work?

No.

I tried searching for this and found that the Mediasoup WebRTC doesn't have any way of parsing the ICE data, but why does the Plugin send the ICE data to the signaling, even though it knows that the Player that is connected is SFU

Largely the UE plugin will do the same set of steps for both normal browser peers and SFU. While you are correct about the ICE candidates being unused, I think it more a side effect of the same codepaths being used in the PS plugin. It shouldn't hurt anything by sending them.

Steps to Reproduce:
Download the release from Github
Follow the instructions on setting up the components
Install packages and build-dev on frontend/lib folder
Install packages, link the lib folder and build-dev on frontend/ui-library folder
Install packages, link the lib+ui-library folder and build-dev on frontend/implementations/typescript folder
Install set the configure the app and run using serve command on frontend/implementations/typescript folder
Install dependencies and run the signalling server
Configure and run SFU server with <IP_ADDRESS> as public IP
The SFU is stuck at a certain point!

From this, is it correct that you have tried running a completely unmodified PSInfra and the SFU will not stream?

Configure and run SFU server with <IP_ADDRESS> as public IP

And do you get the same result if you start the SFU with no public IP specified?

Sorry for not getting back to you sooner, I tried running SFU with no public IP specified, and it works fine. I was trying to run with listenIps: [{ ip: "<IP_ADDRESS>", announcedIp: "<IP_ADDRESS>" }], data, but this doesn't work. it seems that I forget to read the comment in the config file that says:
// here you must specify ip addresses to listen on
// some browsers have issues with connecting to ICE on
// localhost so you might have to specify a proper
// private or public ip here.

: )


Parameters

Allow commands that don't require parameters to have parameters instead of failing silently.

As recommended by some other programmers I know that work with the API. This feature will be scrapped, due to it being bad practice for users.


Docs: next steps

The documentation is currently rendered using the sphinx-immaterial theme. See #270 and #271 for details. There are still some known issues, however:

[ ] The HGS pseudocode in intro to HGS does not render correctly. I opened an issue for this: https://github.com/jbms/sphinx-immaterial/issues/272.
[ ] API type hints sometimes render as ~typing.List, rather than List.

Some additional things:

[x] As a bit of a long-term goal, I'd much rather we host our stuff using GitHub, which we already use for everything else. It's not hard to build the documentation in a separate workflow, and we can just put the rendered docs in a gh-pages branch for GitHub to pick up.
[ ] Previews for PRs is something GitHub is working on; that's tracked here. Also relevant: https://github.com/actions/deploy-pages/issues/180. We'll keep using RTD for this in the meantime.
[x] A custom domain name, like https://pyvrp.org.
[ ] Versioned documentation. We'll probably not generate docs for older versions, but should start adding pinned docs versions for releases from now on, including a latest (last released version) and develop that defaults to current main. Or something like that.

I've added a workflow that renders the documentation and deploys to GitHub Pages. Together with the domain name I bought yesterday we now deploy to https://pyvrp.org/. 🎉

HGS pseudocode has been fixed upstream in the sphinx-immaterial theme. All we have to do is wait for that to hit PyPI.

The versioning is something I'll look into sometime soon, possibly upcoming weekend.

The notes are aligned kind of ugly here:

I opened an issue about this in the theme a while ago, and that has now been fixed upstream. All we have to do is wait for that fix to hit PyPI and then upgrade the theme.

Later, at some point: check if this is fixed https://github.com/jbms/sphinx-immaterial/issues/345 and update to latest Sphinx.

I'm closing this issue since all the open points are now tracked in other places.


Fix Bugs

[ ] I eye power the page breaks. So help me check haha.
[ ] Fix some bugs. Make sure no more * for the listing.
[ ] Make sure that the tables are all okay.

Codecov Report

Merging #277 (4097f7f) into master (455a39f) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #277   +/-   ##
=========================================
  Coverage     38.50%   38.50%
  Complexity      558      558
=========================================
  Files           178      178
  Lines          3301     3301
  Branches        397      397
=========================================
  Hits           1271     1271
  Misses         1888     1888
  Partials        142      142

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 455a39f...4097f7f. Read the comment docs.


Web worker example doesn't work

Using https://github.com/Netflix/falcor/blob/master/examples/datasource/webWorkerSource.js as an example against latest master, I get the error:
ERRORS: {"message":"An exception was thrown when making a request."}
Which can be traced back to the lack of a falcor.Observable class.
Could the example be updated or some pointers on how to achieve a similar result?
/cc @michaelbpaulson

@adammw Yes, you could always replace it with an Rx.Observable (npm i rx).  This code is old.  Its where we had our own small rx library, which was a long time ago.
So replace falcor.Observable.create(...); with Rx.Observable.create(...);.  If you get the example working again, I would be greatly pleased to merge in a PR :)

Hey @michaelbpaulson, I was looking into this example and came across this and figured a good way to understand it would be to fix it! So I have opened up #733. Thanks!


Query API

Hi,
I'd like to query mailchimp for a specific email address. I'm doing this but it's not working:
          members_match = gibbon.lists(list_id).members.retrieve(params: {email_address: member[:email] })["members"]

Am I doing something wrong ?
Thanks!
Stephane

According to MailChimp's docs, that should return the first 10 members. I don't know what passing email_address to that call does (if anything).
I suggest looking at the List Members Instance doc instead. There you can see that you can see that one can fetch a specific member by email address. You need to hash the lower cased email address. With Gibbon, I think that would look like this:
email_hash = <email address lowercased, trimmed, and md5 hashed>
gibbon.lists(list_id).members(email_hash).retrieve

You should always wrap calls in a begin/rescue so you can handle errors returned by the API.


For new 3botconnect identity registrations require 2x input of 24 word seed

I have made a lot of mistakes in the first time registration of a number of  3botconnect identities.  To make sure other people to not fall in the same trap (believing that they have entered the correct 24-word sequence and blaming the software for being buggy) maybe at first input ask twice for the 24-word seed input.

I feel people will just copy paste it the 2nd time around so this would just be an annoyence instead.
@rkhamis what do you think?

I agree with @grimpy. they would just paste it, don't you think, @weynandkuijpers

hmmmmm --okay - fair point. But then what would be a good strategy to no allows people to enter a typo. Can we do a check (hash?) that is also presented in the app on the phone (x digit code) that verifies the the words were entered correctly.
PS> tlaking / thinking about this only makes sense if going forward the "manual" entry of the 24 words is mandatory. If it it temporary (local SDK install) then pet's close the issue - not worth the effort.


Don't link to Spanish Wikipedia

Because the README is in English

Not sure why it thinks I changed the last line


Error spawn EACCES with webpack dev server for vue-cli

My environment:

Centos7 via VirtualBox (installed on Windows7)
Node version: 6.10.3
Npm version : 3.10.10
I'm behind a corporate proxy

I initialized a new project "vuetest" with vue-cli, and now I want to run a webpack server. I use the following command:
npm run dev
This command is equivalent to "webpack-dev-server --open --hot", here is my "package.json" file to check:
{
  "name": "vuetest",
  "description": "A Vue.js project",
  "version": "1.0.0",
  "author": "",
  "private": true,
  "scripts": {
    "dev": "cross-env NODE_ENV=development webpack-dev-server --open --hot",
    "build": "cross-env NODE_ENV=production webpack --progress --hide-modules"
  },
  "dependencies": {
    "vue": "^2.3.3"
  },
  "devDependencies": {
    "babel-core": "^6.0.0",
    "babel-loader": "^6.0.0",
    "babel-preset-env": "^1.5.1",
    "cross-env": "^3.2.4",
    "css-loader": "^0.25.0",
    "file-loader": "^0.9.0",
    "vue-loader": "^12.1.0",
    "vue-template-compiler": "^2.3.3",
    "webpack": "^2.6.1",
    "webpack-dev-server": "^2.4.5"
  }
}

But I get the following error:
><EMAIL_ADDRESS>dev /var/www/html/vuetest
> cross-env NODE_ENV=development webpack-dev-server --open --hot

Project is running at http://localhost:8080/
webpack output is served from /dist/
404s will fallback to /index.html
internal/child_process.js:319
    throw errnoException(err, 'spawn');
    ^

Error: spawn EACCES
    at exports._errnoException (util.js:1018:11)
    at ChildProcess.spawn (internal/child_process.js:319:11)
    at Object.exports.spawn (child_process.js:378:9)
    at module.exports (/var/www/html/vuetest/node_modules/opn/index.js:75:24)
    at reportReadiness (/var/www/html/vuetest/node_modules/webpack-dev-server/bin/webpack-dev-server.js:424:3)
    at Server.<anonymous> (/var/www/html/vuetest/node_modules/webpack-dev-server/bin/webpack-dev-server.js:404:4)
    at Server.g (events.js:292:16)
    at emitNone (events.js:86:13)
    at Server.emit (events.js:185:7)
    at emitListeningNT (net.js:1284:10)

npm ERR! Linux 3.10.0-514.el7.x86_64
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "run" "dev"
npm ERR! node v6.10.3
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>dev: `cross-env NODE_ENV=development webpack-dev-server --open --hot`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>dev script 'cross-env NODE_ENV=development webpack-dev-server --open --hot'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the vuetest package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     cross-env NODE_ENV=development webpack-dev-server --open --hot
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs vuetest
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls vuetest
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /var/www/html/vuetest/npm-debug.log

Here's the contents of the "npm-debug.log" file:
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'dev' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'predev', 'dev', 'postdev' ]
5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 silly lifecycle<EMAIL_ADDRESS>no script for predev, continuing
7 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>8 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
9 verbose lifecycle<EMAIL_ADDRESS>PATH: /usr/lib/node_modules/npm/bin/node-gyp-bin:/var/www/html/vuetest/node_modules/.bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/bdupre/.local/bin:/home/bdupre/bin
10 verbose lifecycle<EMAIL_ADDRESS>CWD: /var/www/html/vuetest
11 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c',
11 silly lifecycle   'cross-env NODE_ENV=development webpack-dev-server --open --hot' ]
12 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1  signal: null
13 info lifecycle<EMAIL_ADDRESS>Failed to exec dev script
14 verbose stack Error<EMAIL_ADDRESS>dev: `cross-env NODE_ENV=development webpack-dev-server --open --hot`
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/lib/utils/lifecycle.js:255:16)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at EventEmitter.emit (events.js:191:7)
14 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at ChildProcess.emit (events.js:191:7)
14 verbose stack     at maybeClose (internal/child_process.js:886:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid<EMAIL_ADDRESS>16 verbose cwd /var/www/html/vuetest
17 error Linux 3.10.0-514.el7.x86_64
18 error argv "/usr/bin/node" "/usr/bin/npm" "run" "dev"
19 error node v6.10.3
20 error npm  v3.10.10
21 error code ELIFECYCLE
22 error<EMAIL_ADDRESS>dev: `cross-env NODE_ENV=development webpack-dev-server --open --hot`
22 error Exit status 1
23 error Failed at the<EMAIL_ADDRESS>dev script 'cross-env NODE_ENV=development webpack-dev-server --open --hot'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the vuetest package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error     cross-env NODE_ENV=development webpack-dev-server --open --hot
23 error You can get information on how to open an issue for this project with:
23 error     npm bugs vuetest
23 error Or if that isn't available, you can get their info via:
23 error     npm owner ls vuetest
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]

Does anyone know how to fix it please?

@webpack-bot move to webpack/webpack-dev-server
Problem with opn?


notebook() arguments aren't kwargs

https://github.com/mpastell/Weave.jl/blob/c9a814759dba764931582f7dc91e0d92633a7e4d/src/Weave.jl#L173-L184
For example, if you want to set a nbconvert_options string, you also need to set an out_path and a timeout, even if you don't intend to fiddle with those defaults.

Is this fixed by #196?

Sorry, you're right, I did fix it with the reorganization in the PR. Closing now.


Node animation lags behind edge animation

(Discussed on a hangout with @davkal)

Can reproduce with debug toolbar...

This happens when new edges are created that connect to nodes that are moving to a new position. Those edges currently dont animate because they have no prior state.
A possible fix would be passing the source and target nodes from a previous layout run (cant be the current state because those are the final positions) to the edge and injecting those coords as prior waypoints into the edge (via react-motion's defaultStyle).
This is not a regression, seen in 0.13, removing milestone.

I've seen this when no new edges are coming in; just by clicking the redraw button.


notebooks.ai login and sample project down

Login page doesn't load, and neither does the sample project.
If it's just me, I'm using chrome and mac

Problem seems to be resolved. Thanks for reporting.


Rephrase README

Reference: https://code.visualstudio.com/docs/languages/typescript.

:tada: This issue has been resolved in version 2.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
Visual Studio Marketplace
GitHub release

Your semantic-release bot :package::rocket:


Services mentioned 3 times in search list

There were some issues with the search index for this service #455 . I re_indexed it a lot. Now it's appearing multiple times in the search.

Issue migrated to our-city-app/mobicage-backend#75


Uncaught TypeError in descriptor.py line 553

Aider version: 0.55.0
Python version: 3.11.7
Platform: Windows-10-10.0.26120-SP0
Python implementation: CPython
Virtual environment: No
OS: Windows 10 (64bit)
Git version: git version 2.42.0.windows.2
An uncaught exception occurred:
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "__main__.py", line 7, in <module>
    sys.exit(main())
             ^^^^^^
  File "main.py", line 414, in main
    if not check_streamlit_install(io):
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "main.py", line 144, in check_streamlit_install
    return utils.check_pip_install_extra(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "utils.py", line 325, in check_pip_install_extra
    __import__(module)
  File "__init__.py", line 55, in <module>
    from streamlit.delta_generator import DeltaGenerator as _DeltaGenerator
  File "delta_generator.py", line 36, in <module>
    from streamlit import config, cursor, env_util, logger, runtime, type_util, util
  File "cursor.py", line 18, in <module>
    from streamlit.runtime.scriptrunner import get_script_run_ctx
  File "__init__.py", line 16, in <module>
    from streamlit.runtime.runtime import Runtime as Runtime
  File "runtime.py", line 29, in <module>
    from streamlit.proto.BackMsg_pb2 import BackMsg
  File "BackMsg_pb2.py", line 14, in <module>
    from streamlit.proto import ClientState_pb2 as streamlit_dot_proto_dot_ClientState__pb2
  File "ClientState_pb2.py", line 14, in <module>
    from streamlit.proto import WidgetStates_pb2 as streamlit_dot_proto_dot_WidgetStates__pb2
  File "WidgetStates_pb2.py", line 14, in <module>
    from streamlit.proto import Common_pb2 as streamlit_dot_proto_dot_Common__pb2
  File "Common_pb2.py", line 36, in <module>
    _descriptor.FieldDescriptor(
  File "descriptor.py", line 553, in __new__
    _message.Message._CheckCalledFromGeneratedFile()
TypeError: Descriptors cannot be created directly.
If this call came from a _pb2.py file, your generated code is out of date and must be regenerated with protoc >= 3.19.0.
If you cannot immediately regenerate your protos, some other possible workarounds are:
 1. Downgrade the protobuf package to 3.20.x or lower.
 2. Set PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=python (but this will use pure-Python parsing and will be much slower).

More information: https://developers.google.com/protocol-buffers/docs/news/2022-05-06#python-updates

Thanks for trying aider and filing this issue.
How did you install aider? What environment are you using? It looks like you don't have the correct set of dependencies installed. This doc may be helpful:
https://aider.chat/docs/troubleshooting/imports.html
I'm going to close this issue for now, but feel free to add a comment here and I will re-open. Or feel free to file a new issue any time.


TDVT smoke tests fail "Tableau doesn't recognize the source type..."

About You:
Name: Cassidy
Company: Blockpoint Systems
Your question:
I'm having issues getting my smoke tests to pass. I am using a custom connector built for JDBC and am using python 3.7.2, tableau 2021.3, and TDVT 2.3.1. Currently I am failing both smoke tests with a DataSourceException "Tableau doesn't recognize the source type...". Here are my current thoughts on the issue.
Could be file path related, but I have the following:

In my ini file I have specified a command line override:CommandLineOverride = -DConnectPluginsPath="C:\Users\Cassidy Mountjoy\Desktop\development\...\bsql_tableau_connector"
I can verify this filepath is correct by starting tableau using: tableau.exe -DConnectPluginsPath="C:\Users\Cassidy Mountjoy\...\bsql_tableau_connector" and connecting to my data source

Could be password related?

I have a generated password file that contains the correct password. I did it when I added the data source.
When I open the .tds file in tableau desktop and try to drag a column to view it I am prompted for a password... the tutorial said this could be a problem. Maybe this has to do with how I generate my tds files. I am using "python -m tdvt.tdvt run bsql_jdbc --generate --verify".

Internal tracking id: 1322353

Any insight into this would be greatly appreciated

The error message indicates the connector was not loaded correctly.  You can check the log file see if you can find specific reason.
The password file is only used in TDVT test.  It's not used in Tableau.

I will check the log files. The connector loads in tableau, it doesn't load when I'm running TDVT.

I can't find why my connector didn't load successfully. Just to reiterate, it loads successfully when I specify the path and start Tableau desktop. When I run TDVT it doesn't load successfully. The test_metadata.csv can't be found, but I'm not sure how if that relates.

Sadly that was not the issue. I tested this by moving my connector to a file path without spaces, updated my .ini file, and generated/reran the smoke tests. I did notice that I'm currently using python 3.9 when the requirement is 3.7, I'm not sure if this would make a difference but I'm going to try 3.7.

One more idea: try switching to forward slashes, removing the " and/or using relative paths.  Its possible one of these is not handled correctly as passed through the TDVT python code. CommandLineOverride = -DConnectPluginsPath=C:/Users/CASSI~1/Desktop/development/.../bsql_tableau_connector
The tabquey_logs.zip/<test-suite>/log.txt should contain details about why the plugin did or didn't load during TDVT usage. Look for lines containing connector-plugin, connector-plugin-warning and connector-plugin-error.
A more verbose set of logs can be generated by adding -DLogLevel=Debug to the CommandLineOverride: CommandLineOverride = -DConnectPluginsPath=folder_path -DLogLevel=Debug
To investigate further we'll likely need the details described on the bug artifacts page. For which set of logs to include, tabquery_logs.zip will be the most relevant set based on the description so far.

I ended up resolving this issue, the file path pointed to the wrong directory.


certigo: enable tests

certigo: enable tests
@nix { "action": "setPhase", "phase": "checkPhase" }
running tests
=== RUN   TestDump
--- PASS: TestDump (0.00s)
=== RUN   TestDumpMissingFile
--- PASS: TestDumpMissingFile (0.00s)
=== RUN   TestConnect
--- PASS: TestConnect (0.00s)
PASS
ok      github.com/square/certigo/cli   0.007s
=== RUN   TestPrivateKey
--- PASS: TestPrivateKey (0.00s)
=== RUN   TestTrustedCert
--- PASS: TestTrustedCert (0.00s)
PASS
ok      github.com/square/certigo/jceks 0.002s
=== RUN   TestExtract
--- PASS: TestExtract (0.00s)
PASS
ok      github.com/square/certigo/pkcs7 0.001s
=== RUN   TestNilPacket
--- PASS: TestNilPacket (0.00s)
=== RUN   TestConnReadErr
--- PASS: TestConnReadErr (0.01s)
PASS
ok      github.com/square/certigo/starttls/ldap 0.012s

Tests have been failing under Darwin since this got merged.
https://hydra.nixos.org/job/nixpkgs/trunk/certigo.x86_64-darwin


We need some null checks in Controller

I tried this:
public IActionResult TestFile => File((string)null, "text/plain"); and it failed with

Looks like this was fixed in 3a876e38 if I'm reading the bug right, @pranavkm was the branch you saw this on up to date?

Ah, interesting, so this particular exception already throws an ArgNullException?

This was beta8 code - so maybe the NotNull checks weren't in?

Yes, but oddly you filed the bug after you made the NotNull change :smile:

Sounds like we're all in agreement that this is fixed, shall I close it as norepro?

I'm ok with the current state. However we do have some inconsistencies in terms of where the ArgNull occurs. For instance:

https://github.com/aspnet/Mvc/blob/dev/src/Microsoft.AspNet.Mvc.ViewFeatures/Controller.cs#L1020-L1023
https://github.com/aspnet/Mvc/blob/dev/src/Microsoft.AspNet.Mvc.ViewFeatures/Controller.cs#L608-L611

perform null checks wen invoked versus the vast majority expect the underlying code to do it.

@Eilon I think what we're getting at here is trying to decide whether we want to make null checks at every level of functions that call each other for safety and to get a slimmer stacktrace, or if we want to only check something at it's lowest possible level so as not to have the top of a function be crowded by null checks when a callee below is going to do that work anyway. Thoughts?

Eh, I think at this point we can take it from direct customer feedback, like the ViewResult thing. So, perhaps no extra work to do here at this point.

K, closing it out then.


How is it possible to change hideExpression of input dynamically?

I'm passing config downloaded from server to formly. In my form I have a complex visibility condition, it depends of emptiness of some form fields and values that are entered outside of the form.
The config of that field is something like the following
{
  "key": "bad_input",
  "type": "input",
  "hideExpression": "!model.key1 || !model.key2 || !${externalObject.property}",
  "templateOptions": {
    "label": "Label"
  }
}

I'm handling changes of externalObject.property, put it in !model.key1 || !model.key2 || !${externalObject.property} expression, find the description of this field and change fields[index].hideExpression. After that hideExpression is either !model.key1 || !model.key2 || !true or !model.key1 || !model.key2 || !false. Still that seem to have no effect. Field is not visible on both values.
I've created simple StackBlitz with similar problem. I'm trying to change hideExpression of input -- https://stackblitz.com/edit/ngx-formly-ui-material-8bxaru?file=src%2Fapp%2Fapp.component.ts
hideExpression changes on 'toogle visibility' click, while actual visibility of input does not. Input disappears after first click and stay hidden.
Please note that I'm getting json from server, hence using function in hide expression is not an option in my case.
Formly version is 5.10.6 if that matters

try this:
"expressionProperties": {
     "hide": () => !this.model.key1 || !this.model.key2 || !this.externalObject.property
}

Thanks for your answer @10229428 ! Still using functions is not the best option here, cause I'm getting JSON from backend, there can be no functions.
I've tried to rewrite my example and change expressionProperties.hide instead of changing hideExpression. Still result merely the same - https://stackblitz.com/edit/ngx-formly-ui-material-jnqvzs?file=src%2Fapp%2Fapp.component.ts
BTW, what is the difference between using expressionProperties.hide and using hideExpression?

you need to re-assign a new value for the fields in order to detect changes:
toogle() {
  ...
  this.fields[0] = { ...this.fields[0] };
  this.fields = [...this.fields];
}

if you handle the changes only on the initialization step then just make sure to not render formly-formly until you've done with the changes (check our doc example https://formly.dev/examples/other/json-powered)

what is the difference between using expressionProperties.hide and using hideExpression?

better rely on hideExpression, expressionProperties.hide doesn't take into account the field validation.


Passing --sync to perf programs throws an exception when printing results

When running --sync tests, an exception is thrown when printing results.
For example, running:
# Not checked in currently, but probably any perf test in our repo will do:
dotnet run --no-build -c release -f netcoreapp3.1 -p sdk\keyvault\Azure.Security.KeyVault.Secrets\perf\Azure.Security.KeyVault.Secrets.Perf.csproj -- ListSecrets --rate 200 --latency --sync

Will print toward the end:
=== Results ===
Completed 72 operations in a weighted-average of 10.13s (7.11 ops/s, 0.141 s/op)

=== Latency Distribution ===
 50.000%        131.29ms
 75.000%        157.92ms
 90.000%        176.04ms
 99.000%        238.90ms
 99.900%        238.90ms
 99.990%        238.90ms
 99.999%        238.90ms
100.000%        258.08ms

=== Corrected Latency Distribution ===
Exception: System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at Azure.Test.Perf.PerfProgram.PrintLatencies(String header, List`1[] latencies) in C:\src\azure-sdk-for-net\common\Perf\Azure.Test.Perf\PerfProgram.cs:line 358
   at Azure.Test.Perf.PerfProgram.RunTestsAsync(IPerfTest[] tests, PerfOptions options, String title, Boolean warmup) in C:\src\azure-sdk-for-net\common\Perf\Azure.Test.Perf\PerfProgram.cs:line 330
   at Azure.Test.Perf.PerfProgram.Run(Type testType, PerfOptions options) in C:\src\azure-sdk-for-net\common\Perf\Azure.Test.Perf\PerfProgram.cs:line 107
=== Cleanup ===
Exception: System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at Azure.Test.Perf.PerfProgram.PrintLatencies(String header, List`1[] latencies) in C:\src\azure-sdk-for-net\common\Perf\Azure.Test.Perf\PerfProgram.cs:line 358
   at Azure.Test.Perf.PerfProgram.RunTestsAsync(IPerfTest[] tests, PerfOptions options, String title, Boolean warmup) in C:\src\azure-sdk-for-net\common\Perf\Azure.Test.Perf\PerfProgram.cs:line 330
   at Azure.Test.Perf.PerfProgram.Run(Type testType, PerfOptions options) in C:\src\azure-sdk-for-net\common\Perf\Azure.Test.Perf\PerfProgram.cs:line 107
   at Azure.Test.Perf.PerfProgram.Run(Type testType, PerfOptions options) in C:\src\azure-sdk-for-net\common\Perf\Azure.Test.Perf\PerfProgram.cs:line 139
...................Unhandled exception. System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at Azure.Test.Perf.PerfProgram.PrintLatencies(String header, List`1[] latencies) in C:\src\azure-sdk-for-net\common\Perf\Azure.Test.Perf\PerfProgram.cs:line 358
   at Azure.Test.Perf.PerfProgram.RunTestsAsync(IPerfTest[] tests, PerfOptions options, String title, Boolean warmup) in C:\src\azure-sdk-for-net\common\Perf\Azure.Test.Perf\PerfProgram.cs:line 330
   at Azure.Test.Perf.PerfProgram.Run(Type testType, PerfOptions options) in C:\src\azure-sdk-for-net\common\Perf\Azure.Test.Perf\PerfProgram.cs:line 107
   at Azure.Test.Perf.PerfProgram.Run(Type testType, PerfOptions options) in C:\src\azure-sdk-for-net\common\Perf\Azure.Test.Perf\PerfProgram.cs:line 139
   at Azure.Test.Perf.PerfProgram.Run(Type testType, PerfOptions options) in C:\src\azure-sdk-for-net\common\Perf\Azure.Test.Perf\PerfProgram.cs:line 157
   at Azure.Test.Perf.PerfProgram.Run(Type testType, PerfOptions options) in C:\src\azure-sdk-for-net\common\Perf\Azure.Test.Perf\PerfProgram.cs:line 163
   at Azure.Test.Perf.PerfProgram.<>c__DisplayClass9_0.<<Main>b__1>d.MoveNext() in C:\src\azure-sdk-for-net\common\Perf\Azure.Test.Perf\PerfProgram.cs:line 45
--- End of stack trace from previous location where exception was thrown ---
   at Azure.Test.Perf.PerfProgram.Main(Assembly assembly, String[] args) in C:\src\azure-sdk-for-net\common\Perf\Azure.Test.Perf\PerfProgram.cs:line 40
   at <Program>$.<<Main>$>d__0.MoveNext() in C:\src\azure-sdk-for-net\sdk\keyvault\Azure.Security.KeyVault.Secrets\perf\Program.cs:line 7
--- End of stack trace from previous location where exception was thrown ---
   at <Program>$.<Main>(String[] args)
.

It looks like the rate parameter is not working at all with sync.  The rate and latency parameters are both considered "experimental" in the .NET perf framework.


Scaling up VMs can cause error

I was doing this workflow quite a bit while scaling up the # of VMs on GCE. Specifically:

on GCE I had increased my pool of VMs
i was trying to delete a pipeline and getting that error message
if I did gcloud compute instances list and grep for the ip mentioned in the error message, it can’t be found
after doing clean-launch and launch i can delete just fine again

So I'm guessing GCE didn’t give me back the VMs/ips I was running pachd on?
docker-user@dev:~/gofordatascience$ make run
pachctl delete-repo compile16
pachctl delete-pipeline compile16
error from DeletePipeline: Get https://<IP_ADDRESS>:443/api/v1/namespaces/default/pods?labelSelector=app%3Dde2996c23d39f0f371994d7a73dd4b95%2Csuite%3Dpachyderm: dial tcp <IP_ADDRESS>:443: getsockopt: connection refused
Makefile:18: recipe for target 'clean-compile' failed
make: *** [clean-compile] Error 1
docker-user@dev:~/gofordatascience$ make run
pachctl delete-repo compile16
pachctl delete-pipeline compile16
pachctl delete-repo filter || true
pachctl delete-pipeline filter
pachctl delete-repo repodata
pachctl create-repo repodata
pachctl start-commit repodata > commitID
cat repodata.csv | pachctl put-file repodata `cat commitID` repodata.csv
pachctl finish-commit repodata `cat commitID`
rm commitID
cd repofilter && make
make[1]: Entering directory '/home/docker-user/gofordatascience/repofilter'
CGO_ENABLED=0 go build -o repofilter
docker build --force-rm=true -t sjezewski/repofilter .
Sending build context to Docker daemon 2.603 MB
Step 1 : FROM golang:latest
 ---> 64ce57bcc69b
Step 2 : RUN apt-get update -yq &&   apt-get install -yq --no-install-recommends     git     ca-certificates     curl     fuse &&   apt-get clean &&   rm -rf /var/lib/apt
 ---> Using cache
 ---> 649caee90c65
Step 3 : RUN go get github.com/pachyderm/pachyderm &&     go get github.com/pachyderm/pachyderm/src/server/cmd/job-shim &&     cp $GOPATH/bin/job-shim /job-shim
 ---> Using cache
 ---> 67a8b25a295c
Step 4 : ADD repofilter /repofilter
 ---> Using cache
 ---> 27b57bc99353
Successfully built 27b57bc99353
docker push sjezewski/repofilter
The push refers to a repository [docker.io/sjezewski/repofilter]
4215f6f6bfcf: Layer already exists
75053577a1f3: Layer already exists
3c5037ce03b1: Layer already exists
a25686109000: Layer already exists
5f70bf18a086: Layer already exists
8ffabf722fd1: Layer already exists
e0b458be0976: Layer already exists
64f70c418198: Layer already exists
8befcf623ce4: Layer already exists
3d5a262d6929: Layer already exists
6eb35183d3b8: Layer already exists
latest: digest: sha256:f8062841e32332cedf5d2d17ddc81e9349e0a135ee52f04d4f5885a0783ae3b3 size: 3844
make[1]: Leaving directory '/home/docker-user/gofordatascience/repofilter'
pachctl create-pipeline -f pipelines/justfilter.json
pachctl create-pipeline -f pipelines/justcompile.json
docker-user@dev:~/gofordatascience$

I think this was a sharing issue, so should be fixed by pfs refactor


trigger a new container build

Preview is available here:http://developers-pr1144.previews.kube001.services.stellar-ops.com


Issue regarding updating MS ToDo Task's status to completed.

Description
I am trying to update the Status to 'completed' of Microsoft ToDo's Task using Microsoft Graph REST API v1.0 -> Microsoft To Do API. I am using Python language. but on the status change to 'completed' the task on my MS ToDo will be deleted rather than fall into the list of completed tasks.
The same code was working perfectly 2 months ago but now it is not.
Please provide me with the right guidance.
Regards

Kaushal Dhamelia

closing as duplicate of #2747


RC.3 Circuit Construction Kit AC & AC: Virtual Lab

@KatieWoe @arouinfar @ariel-phet @kathy-phet circuit-construction-kit-ac/1.0.0-rc.3 and circuit-construction-kit-ac-virtual-lab/1.0.0-rc.3 are ready for RC testing.  This has been a high priority sim.  Document issues in https://github.com/phetsims/circuit-construction-kit-common/issues and link to this issue.
This is a minor spot check to confirm one issue discovered in rc.2.  None of the code changes seem platform specific.  So just testing on 1 browser sounds good.
Assigning to @kathy-phet and @KatieWoe for prioritization.

Focus and Special Instructions

Issues to Verify

[x] Should meter tool labels disappear when all tools are in the play area? (note this points to an issue comment)

These issues should have the "status:ready-for-qa" label. Check these issues off and close them if they are fixed.
Otherwise, post a comment in the issue saying that it wasn't fixed and link back to this issue. If the label is
"status:ready-for-review" or "status:fixed-pending-deploy" then assign back to the developer when done, even if fixed.

Link(s)
Deployed:

AC

AC Virtual Lab

[x] Tester = NS, Platform = macOS12.0.1 + chrome , Time = .5

[ ] Tester = ??, Platform = ??  , Time = ??

I do not believe the XHTML, iframe, etc. need to be double-checked in this version.  If it is procedure or policy to do so, please do so.

FAQs for QA Members

There are multiple tests in this issue... Which test should I do first?
Test in order! Test the first thing first, the second thing second, and so on.

How should I format my issue?

We typically assign the developer who opened the issue in the QA repository.

My question isn't in here... What should I do?
You should:

Consult the QA Book.
Google it.
Ask Katie.
Ask a developer.
Google it again.
Cry.

Hello! This branch was recently patched for https://github.com/phetsims/scenery/issues/1309. Before a final publication, can we please spot check one more RC to verify that that fix is working in this build? Let me know if you have any questions.

I tested https://phet-dev.colorado.edu/html/circuit-construction-kit-ac-virtual-lab/1.0.0-rc.3/phet/xhtml/circuit-construction-kit-ac-virtual-lab_all.xhtml and the sim did not crash when opening the about dialog.  Is that expected?

Yes. The sim should not crash.

From slack:
Sam Reid:house_with_garden:  13 minutes ago
I tested https://phet-dev.colorado.edu/html/circuit-construction-kit-ac-virtual-lab/1.0.0-rc.3/phet/xhtml/circuit-construction-kit-ac-virtual-lab_all.xhtml and the sim did not crash when opening the about dialog.  Is that expected?
Jesse Greenberg  6 minutes ago
OK, yes it is possible that CCK did not have this problem yet.
Sam Reid:house_with_garden:  5 minutes ago
Should we still RC the scenery change?
Jesse Greenberg  < 1 minute ago
I think so, if possible. I wanted to eagerly patch published sims with interactive description even if they didn't exhibit this bug. Without this patch, if a  is ever added through a maintenance release to AboutDialog strings (or any other strings) that are used in the PDOM it would crash in XHTML. (edited)
Sam Reid:house_with_garden:  < 1 minute ago
Sure, I have another RC due to credits changes, so I’ll include spot check for that.
Jesse Greenberg  < 1 minute ago
OK, thank you!

I'll be creating RC.4 to spot check credits and XHTML about dialog changes, so I think testing RC.3 can be stopped.


UKHPI - 1.1.1: Non-text Content

See https://docs.google.com/spreadsheets/d/1YS3N5ps9pJGFOxBDi9C2DwA37WQPIVax/edit?gid=1215429860#gid=1215429860&range=5:5

@tomguilbert Here's a screenshot of what's been done, notice the alt="UKHPI Logo" attribute:

Previously this was missing, and people using screen readers could not tell what was that image about, see https://www.w3schools.com/tags/att_img_alt.asp for more information.
There are two ways to test this, either using a screen reader or visiting https://hmlr-dev-pres.epimorphics.net/app/ukhpi/ and inspecting the logo image using dev tools (Right Click on the logo -> Inspect, make sure the <img> element is selected, rather than the link)

Thanks for the explanation Bogdan - looks good and I can see using the silktide accessibility checker that this no longer fails in dev.


I cannot init.

Hi, all.
I got latest version
$ curl -LO https://Deployer.org/Deployer.phar
$ sudo mv Deployer.phar /usr/local/bin/dep

and executed  init.
$ mkdir Deployer
$  cd Deployer
$ dep init
/usr/local/bin/dep: line 1: syntax error near unexpected token `newline'
/usr/local/bin/dep: line 1: `<!doctype html>'

Can I recover this ?
thanks.

Upvote & Fund

We're using Polar.sh so you can upvote and help fund this issue.
We receive the funding once the issue is completed & confirmed by you.
Thank you in advance for helping prioritize & fund our backlog.

Your link for phar is wrong (https://deployer.org/docs/6.x/installation#download-phar-archive).
Use this one https://deployer.org/deployer.phar
Furthermore, consider to use v7 instead of 6

Thanks.
I got from https://deployer.org/deployer.phar  and retry dep init.
I got error,  "Call to undefined function Deployer\Utility=posix_setsid()",
so I install php-process extension and retry dep init.
I got deploy.php successfully.
Thanks.
Regards.


When will the source code be released？

Thanks for the interest -- I just released the source code!