Recommendation to Archive

@mfansler rgdal, rgeos, maptools and rgrass7 were archived on CRAN 16 October 2023. They should have been withdrawn by all downstream aggregators at that point for R 4.3, certainly for R 4.4. None of the retired packages are being maintained and will fail when GDAL, GEOS, or PROJ (upstream libraries) cause breakages. As maintainer of the retired packages, I cannot be expected to alert all downstream package managers/aggregators. Sufficiently noisy warnings were inserted into the retired packages and into sp, which has been moved to sf to satisfy its needs for functionality from GDAL, GEOS, or PROJ. I will not notify anybody, that is not my responsibility, I have done what could be done with obvious cases or where contacted by users experiencing problems. See https://r-spatial.github.io/evolution/, and the video of https://edzer.github.io/UseR2024 when it is posted.

Originally posted by @rsbivand in https://github.com/conda-forge/staged-recipes/issues/27072#issuecomment-2245190651

There won't be newer versions and the current on won't build in newer R, so I'm +1.


fix(curriculum): add a lesson to registration form practice project for requiring radio buttons

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #47456

User can make it mandatory to select a radio button using the required attribute.

The request was to add a checked attribute to the buttons and create a legend. However, I personally feel that a required attribute is the best and the cleanest way to address this issue. This leaves both radio buttons unchecked initially, however, does not allow any user to submit the form without choosing one. And since all radio buttons are grouped together with the name attribute, the required attribute is applied on the entire group of buttons, so adding new buttons will maintain the required attribute provided they have the same name attribute to them.

About that screenshot...
The correct test to run is
npm run test:curriculum --block='Learn HTML Forms by Building a Registration Form'
Your changes will fail. You have removed code added in some of the later stepts

I am extremely sorry for the mistakes. Thank you for being patient with me.

@NiharPhansalkar

The request was to add a checked attribute to the buttons and create a legend. However, I personally feel that a required attribute is the best and the cleanest way to address this issue.

And you have checked your implementation with a screen reader to make sure it functions appropriately? There is a reason we settled on that particular solution in the issue. If you feel that your solution is better and can justify it then please make the argument in the issue. But until the consensus on the solution has changed in the issue then I don't think you should be able to make the decision by yourself that it should be implemented differently.
I'm afraid I have to recommend that this PR not be approved because it does not follow accessibility best practices for implementing a required radio button grouping.

@bbsmooth I have made the required changes. I changed all required into checked and also added in the legend. Please re-review the PR.

@bbsmooth @ieahleen
Please review, but we will try and land this later than usual because it adds files which is a logistical problem - for deployments.
We will try and fit this into the queue next week. But that should not stop you from reviewing it.
Thanks.

Sure, I will look into it over the weekend and make the required changes. 👍

@NiharPhansalkar, how is this going so far?


Upgrade to Python 3

Hello.
It’s been roughly a year since Python 2 support has stopped, and most distribution have stopped shipping it. It would be great if this exporter could be upgraded to support Python 3.
Are there any technical limitations that would prevent this?
I can work on a PR if help is needed.

Hello, any plans to work in this issue? I can also help if needed.

Any PR on updating python would be welcome

Hi saied ,
I done this upgrade. please check my pr and merge if you approve it.
thanks


make check fails on O3D300 IFM camera

I am trying to use your libo3d3xx on github to extract the point cloud from an O3D300 IFM camera.
Following the testing process ($ make check) I am getting some errors:
I am running Ubuntu 10.04 LTS 64 bit.
toma@ubuntu:~/git/libo3d3xx/build$ ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=64 time=0.523 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=64 time=0.614 ms
toma@ubuntu:~/git/libo3d3xx/build/src/bin$ ./o3d3xx-dump
{
"o3d3xx":
{
"libo3d3xx": "111",
"Date": "Fri Dec  4 21:41:40 2015",
"HWInfo":
{
"Mainboard": "#!02_M381_002_12345678_008022169",
"Illumination": "#!02_I300_001_01867212_008001175",
"MACAddress": "00:02:01:40:1C:71",
"Frontend": "#!02_F341_002_12345678_008022593",
"Diagnose": "#!02_D312_C27_12345678_008022683",
"Connector": "#!02_A310_001_12345678_008022060"
},
"SWVersion":
{
"IFM_Software": "1.1.288",
"Linux": "Linux version 3.11.0-00001-g4e630e2 (eswadmin@dettlx79) (gcc version 4.7.2 (GCC) ) #1 SMP Mon Jun 8 10:25:20 CEST 2015",
"Diagnostic_Controller": "0.3.9",
"ELDK": "GOLDENEYE_ELDK-2015-07-01_16-26-37-cc5673110f1bff06b66149c8320f6c1823d87891",
"Calibration_Version": "0.6.4",
"Calibration_Device": "00:02:01:40:1c:71",
"Main_Application": "0.4.34",
"Algorithm_Version": "0.6.19"
},
"Device":
{
"Name": "New sensor",
"Description": "",
"ActiveApplication": "0",
"PcicEipEnabled": "false",
"PcicTcpPort": "50010",
"PcicProtocolVersion": "3",
"IOLogicType": "1",
"IODebouncing": "true",
"IOExternApplicationSwitch": "0",
"SessionTimeout": "30",
"ServiceReportPassedBuffer": "5",
"ServiceReportFailedBuffer": "5",
"ExtrinsicCalibTransX": "0",
"ExtrinsicCalibTransY": "0",
"ExtrinsicCalibTransZ": "0",
"ExtrinsicCalibRotX": "0",
"ExtrinsicCalibRotY": "0",
"ExtrinsicCalibRotZ": "0",
"IPAddressConfig": "0",
"PasswordActivated": "false",
"OperatingMode": "0",
"DeviceType": "",
"ArticleNumber": "",
"ArticleStatus": "",
"UpTime": "6.95301075392642e-310",
"ImageTimestampReference": "32232032",
"TemperatureFront1": "1.592485828261073e-316",
"TemperatureFront2": "6.952977167208689e-310",
"TemperatureIMX6": "1.592497685836573e-316",
"TemperatureIllu": "1.592509543412073e-316"
},
"Net":
{
"MACAddress": "",
"NetworkSpeed": "0",
"StaticIPv4Address": "<IP_ADDRESS>",
"StaticIPv4SubNetMask": "<IP_ADDRESS>",
"StaticIPv4Gateway": "<IP_ADDRESS>",
"UseDHCP": "false"
},
"Apps": ""
}
}
toma@ubuntu:~/git/libo3d3xx/build$ make check
[  4%] Built target gtest
[ 56%] Built target o3d3xx
[ 60%] Built target gtest_main
[100%] Built target o3d3xx-tests
[==========] Running 55 tests from 9 test cases.
[----------] Global test environment set-up.
[----------] 4 tests from TemporalFilterTest
[ RUN      ] TemporalFilterTest.TemporalFilterConfig_General
[       OK ] TemporalFilterTest.TemporalFilterConfig_General (237 ms)
[ RUN      ] TemporalFilterTest.GetTemporalFilterParameters
unknown file: Failure
C++ exception with description "XMLRPC invalid application index" thrown in the test body.
[  FAILED  ] TemporalFilterTest.GetTemporalFilterParameters (982 ms)
[ RUN      ] TemporalFilterTest.GetTemporalFilterParameterLimits
unknown file: Failure
C++ exception with description "XMLRPC invalid application index" thrown in the test body.
[  FAILED  ] TemporalFilterTest.GetTemporalFilterParameterLimits (1000 ms)
[ RUN      ] TemporalFilterTest.TemporalFilterConfig_JSON
unknown file: Failure
C++ exception with description "XMLRPC invalid application index" thrown in the test body.
[  FAILED  ] TemporalFilterTest.TemporalFilterConfig_JSON (1009 ms)
[----------] 4 tests from TemporalFilterTest (3229 ms total)
[----------] 1 test from ImportExport_Tests
[ RUN      ] ImportExport_Tests.ImportExportApp
/home/toma/git/libo3d3xx/test/o3d3xx-import-export-tests.cpp:22: Failure
Expected: bytes = cam->ExportIFMApp(active_idx) doesn't throw an exception.
Actual: it throws.
[  FAILED  ] ImportExport_Tests.ImportExportApp (508 ms)
[----------] 1 test from ImportExport_Tests (508 ms total)
[----------] 8 tests from ImageBuffers_Tests
[ RUN      ] ImageBuffers_Tests.Cloud
/home/toma/git/libo3d3xx/test/o3d3xx-image-tests.cpp:28: Failure
Value of: fg->WaitForFrame(img.get(), 1000)
Actual: false
Expected: true
/home/toma/git/libo3d3xx/test/o3d3xx-image-tests.cpp:41: Failure
Value of: fg->WaitForFrame(img2.get(), 1000)
Actual: false
Expected: true
[  FAILED  ] ImageBuffers_Tests.Cloud (2002 ms)
[ RUN      ] ImageBuffers_Tests.XYZImage
/home/toma/git/libo3d3xx/test/o3d3xx-image-tests.cpp:65: Failure
Value of: fg->WaitForFrame(buff.get(), 1000)
Actual: false
Expected: true
[  FAILED  ] ImageBuffers_Tests.XYZImage (1002 ms)
[ RUN      ] ImageBuffers_Tests.DepthImage
/home/toma/git/libo3d3xx/test/o3d3xx-image-tests.cpp:120: Failure
Value of: fg->WaitForFrame(img.get(), 1000)
Actual: false
Expected: true
Floating point exception (core dumped)
make[3]: *** [test/CMakeFiles/check] Error 136
make[2]: *** [test/CMakeFiles/check.dir/all] Error 2
make[1]: *** [test/CMakeFiles/check.dir/rule] Error 2
make: *** [check] Error 2

It appears as though there are no applications loaded on the camera. The best thing to do here would be to set it back to factory defaults and rerun the test suite. You can do this with the o3d3xx-reset command line tool.

@tomatac @tpanzarella the O3D300 is a sensor not a camera. You can easily
check this by counting the pins on the connector.
5 PIN connector -> Camera
8 PIN connector -> Sensor
The Sensor has two apps pre installed one for dimensioning and the other
one for completeness. But the sensor does not have an application pre
installed. You can try to create one with the command line tools.
Am 05.12.2015 12:38 nachm. schrieb "Tom Panzarella" <
<EMAIL_ADDRESS>
It appears as though there are no applications loaded on the camera. The
best thing to do here would be to set it back to factory defaults and rerun
the test suite. You can do this with the o3d3xx-reset command line tool.
—
Reply to this email directly or view it on GitHub
https://github.com/lovepark/libo3d3xx/issues/28#issuecomment-162174920.

I ran o3d3xx-reset and "make check" after that. "make check" reported the same errors.
I do have the sensor but IFM said that it should work.
How do I create and install an app on the sensor?
The sensor is running a version of Linux. How do I login into the sensor, SSH? What is the default password?

@tomatac I'll check this in the office on monday. At the moment I have no 03D300 available. O3D300 is compatible with O3D303. The main difference is the missing default camera application.
Sure, the device is running an embedded linux. The ssh access is only available for ifm maintenance purposes.

Attached is a JSON dump of the camera created via o3d3xx-dump. This is running IFM firmware 1.1.288 and was created with libo3d3xx version 0.2.0. You should ensure that is what your s/w stack looks like. This has one application installed. The default as shipped with the camera product and not the sensor product. I have not used the sensor at all and @graugans would be the authority on noted the differences. However, in theory, you should be able to take the attached camera.json file and load it on your camera like:
$ o3d3xx-config < camera.json

After you do that, please post the output of o3d3xx-dump.
NOTE: The attached file has the .txt extension so it is compatible with github attachments.
camera.json.txt

@tomatac @tpanzarella you may have to edit the JSON and change O3D303 -> O3D300

I suppose an alternative to having to edit the JSON (not sure where it would need to be edited as this is the libo3d3xx JSON serialization which basically gets turned into a bunch of XMLRPC calls internally by the library), you could use the command line tools to simply add an application. You can do that with the following command line:
$ echo '{"o3d3xx":{"Apps":[{}]}}' | o3d3xx-config

This will create the application with all of the camera default settings applied. Most notably an imager configuration of under5m_moderate running at 5Hz.

Thank you very much for your feedback!
I think that the first step I should do is to back up the state of the camera. How do I do that?
For me it is very important to be able to use the sensor applications also.
This is my test camera and I use it to evaluate application. Some applications are simple enough and the sensor applications are good enough, other are more complex and I am looking to use OpenCV.
Is there anywhere I can find documentation about the software architecture of this smart camera?
I would like to understand better how things work. Thanks! Toma

@tomatac I think @graugans could advise you on how to offically back up the sensor product. Likely through a function available in IFM Vision Assistant (Windows GUI software). But I defer to him.
With respect to your efforts in building an OpenCV-based application utilizing libo3d3xx as the driver, I can likely answer any specific questions you may have. In short, the high-level concept of the library is to do all the configuration and manipulation utilizing the command line tools. You can pretty much do anything with them. Then once you have things set up the way you like, you then write custom code utilizing the library's frame grabbing API. A quick and dirty example of using the frame grabbing API is available here. A more thorough example can be gleaned from the camera node of the ROS bindings. Additionally, through my company we can offer you commercial support or build custom applications to your specification.

@tomatac maybe the term application is a bit misleading  those are build into the device firmware. Whenever you create or delete one this is only a JSON file which selects the particular functionality and algorithm on the camera.
You can create a full device backup of the camera with the help of the ifm Vision Assitant this will download all applications and the device configuration. You can re-apply this backup again with the help of the vision assistant.
I am part of the embedded core team for the O3D3xx. Most of the support I do here is in my spare time. If you need more application related support do not hesitate to call our application support team.
I am an expert on the camera interface not on how to solve applications.

I've tested the command line from @tpanzarella on my O3D302 (60° opening angle variant) and added activation of the first application. Otherwise the tests do fail again because the newly created application is not active
echo '{"o3d3xx":{"Apps":[{}],"Device":{"ActiveApplication":"1"}}}' | o3d3xx-config

You can check for an application with the command
o3d3xx-ls
  [1] id=829551123, name=New application, description=
* [2] id=1788193191, name=New application, description=
  [3] id=44362294, name=New application, description=

The asterisk marks the active application
If you want to delete a application you can use the commandline tool o3d3xx-rm
o3d3xx-rm -i 2

This removes the application on index 2.
When I run the make check command I still have some issues but those look like minor issues.
[ RUN      ] DenseImageTest.ActiveApplication
unknown file: Failure
C++ exception with description "XMLRPC finished but the called failed" thrown in SetUp().
unknown file: Failure
C++ exception with description "XMLRPC invalid application index" thrown in TearDown().
[  FAILED  ] DenseImageTest.ActiveApplication (2009 ms)
[ RUN      ] DenseImageTest.ImageSize
unknown file: Failure
C++ exception with description "XMLRPC finished but the called failed" thrown in SetUp().
unknown file: Failure
C++ exception with description "XMLRPC invalid application index" thrown in TearDown().
[  FAILED  ] DenseImageTest.ImageSize (2008 ms)
[----------] 2 tests from DenseImageTest (4017 ms total)
...
[----------] Global test environment tear-down
[==========] 57 tests from 9 test cases ran. (107863 ms total)
[  PASSED  ] 55 tests.
[  FAILED  ] 2 tests, listed below:
[  FAILED  ] DenseImageTest.ActiveApplication
[  FAILED  ] DenseImageTest.ImageSize

@tpanzarella am I right the DenseImageTest is from the 100K test suit? So those may fail with any device other than the O3D303 because for the activation of the 100K feature an binary application is uploaded to the device.

@graugans That is correct. Particularly for the 0.2.0 release it uploads the binary application. This has changed on the dev branch since the 100K is directly exposed via XMLRPC.

Hi. First I would like to thank you for your support. I also do this evaluation also in my spare time.
I think that this is a great technology and I hope that will pay off in the future.
I am trying to understand how does the camera works and based on your feedback I think that I am getting there.
The ifmVisionAssistant has 3 options "Export Settings", "Import Settings" and "Reset to Factory Defaults". I think that the "Export Settings" is equivalent to a backup and the "Reset to Factory Defaults" + "Import Settings" is equivalent to a restore. @graugans could you please confirm or redirect me to the right person that can confirm?
Now, for adding the application that allows me to capture the cloud point, I will summarize what I understood I should do:

Take the output of o3d3xx-dump from my camera and add in the applications section (the "sample application") from Tom's dump (that way I can retain the settings that are very specific to my camera like the MAC address)
write the new file to the camera: o3d3xx-config < camera.json
restart the camera
check if the application is registered ok: o3d3xx-ls
make it the active application: echo '{"o3d3xx":{"Apps":[{}],"Device":{"ActiveApplication":"1"}}}' | o3d3xx-config
run the "make check"
Are these the right steps?

@tomatac A few notes... You don't have to worry about things like the MAC address, etc. libo3d3xx does not try to overwrite anything in the HWInfo or SWVersion sections of the JSON. They are treated as read-only. They are reported upon by o3d3xx-dump as they contain useful information for debugging and troubleshooting.
In terms of setting an application active, you can just use this:
$ echo '{"o3d3xx":{"Device":{"ActiveApplication":"2"}}}' | o3d3xx-config

The above assumes you want to mark the application at index number 2 active. Adjust as necessary for your environment.
Basically, the o3d3xx-config application takes in a JSON file in the format output by o3d3xx-dump. However, it can also take just JSON snippets so long as they are fully qualified.

@tomatac
To create a new default application the recommended way is to use
echo '{"o3d3xx":{"Apps":[{}]}' | o3d3xx-config    # create a default camera application
echo '{"o3d3xx":{"Device":{"ActiveApplication":"1"}}}' | o3d3xx-config # activate application on index 1

Or use it in one single command:
echo '{"o3d3xx":{"Apps":[{}],"Device":{"ActiveApplication":"1"}}}' | o3d3xx-config

The reuse of the JSON dump is not needed. Because the camera uses its default settings.
The ifmVisionAssistant has 3 options "Export Settings", "Import Settings" and "Reset to Factory Defaults". I think that the "Export Settings" is equivalent to a backup and the "Reset to Factory Defaults" + "Import Settings" is equivalent to a restore. @graugans could you please confirm or redirect me to the right person that can confirm?

Yes you are right.
The MAC address of the device is burned into the CPU there is no way to change it through the camera software. So you are not able to alter it. HWInfo and SWVersion and stuff like this is as well read-only from on board camera software.

@tomatac @graugans One other thing to note... as @graugans points out above, there still may be issues with the 100K imager tests for the specific sensor that you have. As libo3d3xx utilizes gtest as its unit testing framework, you can run the unit tests but disable the 100K tests since we know they are expected to fail in your particular instance. The easiest way to do this would be to invoke the make check part of the build like:
$ GTEST_FILTER=-DenseImageTest.* make check

Creating the default application worked fine:
echo '{"o3d3xx":{"Apps":[{}]}}' | ./o3d3xx-config
Activation of the application at index 1 did not work. I got this error:
“Failed to configure camera from JSON config '-': XMLRPC value out of range”
I used a variation recommended earlier by @tpanzarella:

I used ./o3d3xx-dump to dump my camera settings into a file (default_app.json)
I edited the file and changed "ActiveApplication": "1"
Applied the settings to the camera: o3d3xx-config < default_app.json
Checked if the settings were applied successfully: ./o3d3xx-dump

“make check” passed all the tests, with the 2 exceptions mentioned above that are related to the high resolution option.
Also ./o3d3xx-viewer worked well.
Thank you for your help!


[CAM-11109] Cloud Academy: documentation review concerning CAM organization admistration

@gsanchezu @aryaroudi please review

Please @SergioQCL, review Travis build that is failing:


Update Grpc dependency

Fixes https://github.com/pulumi/pulumi-dotnet/issues/218.
MacOS runner version had to be bumped to 12 because of https://github.com/grpc/grpc/issues/32558

The upstream issue got closed as won't do:

MacOS11 is EOL and GitHub Actions will drop support, June 28. Closing this one.

It sounds like we need to proceed with this one. @Frassle I'll let you merge if you agree.

I'm going to go ahead and merge this. We're now getting errors in CI runs due to GitHub Actions imminent dropping of support for macOS 11.

This is a scheduled macOS-11 brownout. The macOS-11 environment is deprecated and will be removed on June 28th, 2024.

Doesn't this cause a regression of https://github.com/pulumi/pulumi-dotnet/issues/249?


:CoqJumpToEnd hangs neovim if Coqtail hasn't been fired yet.

Coq 8.19.2
nvim 0.9.5
Anytime if :CoqJumpToEnd runs before :CoqStart, the neovim session will hang, accepts no input and possibly damage the file contents.
It sounds silly but in fact I mapped some shortcuts for these instructions.
And sometimes I forgot to even fire up Coqtail first, so I encountered this.
Thanks a lot for this tool, it's really helpful !

This was tricky, thanks for catching it. I believe #361 fixes the problem. I've tested it some on my end, but I'd appreciate it if you could try it out a bit and make sure it seems ok.

Checked on NVIM v0.10.0 & NVIM v0.9.5 in two different systems, both work fine now.
Thank you very much for this quick fix !


Publish on Pypi

Would be nice to be able to pip install this library.

OK, I will do it a little bit later. Thank you for your patience.

Nice!


keep rekeying

[keep rekeying]
my log id: 8f40f203e4375313cc6c251c

related to #11291

@tkisme I'm looking at your logs now, and the underlying issue is very different from #11291.  Can we re-open this?

Confirmed,problem gone

Great!  And I merged a permanent fix into master in keybase/kbfs#1543.  Closing again.


Clarification: saving offset in binary

First of all, great project and implementation!
I was just wondering what is the motivation of using offset in binary for struct, string, vector etc.
As described in the specification, these types are written by using
[offset] which  points to --> [size] [data..]
What is the advantage of using the offset for these data types?
Why not just to write it directly after each other like bool or array attributes?
Thanks in advance!

Consider this example
struct
{
  bytes field1;
  string field2 = "";
  byte[] field3;
}

in the struct definition you'll have 3 offsets of unit32 pointing to the corresponding data later in buffer
[uint32(field1-offset)],[uint32(field2-offset)],[uint32(field3-offset)],[field1-size,field1-data],[field2-size,field2-data],[field3-size,field3-item1,...,field3-itemN]

Great, thanks for the fast response!
Using your example, I was wondering, why not just remove the
[uint32(field1-offset)],[uint32(field2-offset)],[uint32(field3-offset)]
and write directly
[field1-size,field1-data],[field2-size,field2-data],[field3-size,field3-item1,...,field3-itemN]
This would reduce the size and parsing complexity.
Or am I missing a use-case where the offset has an advantage?

Perfect, makes sense, thanks for the clarification!


get_intflux should return results even if there is no mask.

In the event that there is no mask, get_intflux breaks (per PIPE-1890 in the pipeline version). This was fixed in my fork and on the pipeline version, but not in your main, @jjtobin. As this has become an issue for a dataset that I'm testing, I'm merging it to your main for consistency with the pipeline version.
@r-xue - just a quick note that you'll see this show up in the PR you are monitoring for changes, but it is already fixed in pipeline in PIPE-1890.

Yes. noted. thanks.


youtube error

youtube scrobble at v1.6 not running now. Maybe youtube change some codes.

Works for me. Can you link a video which doesn't scrobble?

This one doesn't work.
http://www.youtube.com/watch?v=OjJky0LzMuw&feature=channel_video_title

That is expected behavior. The scrobbler identifies tack (mostly) by its title which in your case doesn't tell anything about the author nor the track title.
Look at the right side of the omnibx (address bar) - you should see a gray icon with question mark everytime the scrobbler was unable to recognize the track. When you click it, you can input correct song info.
(I see I forgot to mention this in the help section. Noting it for the next release.)


AttributeError: module 'tensorflow.compat.v2' has no attribute 'app'

Hi,
First of all, I'm new to github and Iwasn't sure where to post this so sorry if it's in the wrong place. I'm trying to set up an object detector for my master's but I keep on running into issues.
System information

OS Platform and Distribution: Windows 10
TensorFlow version: 2.3.0
CUDA: 10.1
cuDNN:  7.6.5

I've tried many many different things but I keep on running into issues that prevent me from training a model, "AttributeError: module 'tensorflow.compat.v2' has no attribute 'app'" is the latest
I have followed the guide which can be found on this github page:
https://github.com/TannerGilbert/Tensorflow-Object-Detection-API-Train-Model
I have followed this pretty much to the letter aside from the fact that I didn't download the master branch but went with r2.3.0 instead to ensure compatibility.
I ran the following command in anaconda to try and train the model:
python model_main_tf2.py --pipeline_config_path=training/ssd_efficientdet_d0_512x512_coco17_tpu-8.config --model_dir=training --alsologtostderr
This gave me the following error:

This is the code of the model_main_tf2.py file:
from absl import flags
import tensorflow.compat.v2 as tf
from object_detection import model_hparams
from object_detection import model_lib_v2

flags.DEFINE_string('pipeline_config_path', None, 'Path to pipeline config '
                    'file.')
flags.DEFINE_integer('num_train_steps', None, 'Number of train steps.')
flags.DEFINE_bool('eval_on_train_data', False, 'Enable evaluating on train '
                  'data (only supported in distributed training).')
flags.DEFINE_integer('sample_1_of_n_eval_examples', None, 'Will sample one of '
                     'every n eval input examples, where n is provided.')
flags.DEFINE_integer('sample_1_of_n_eval_on_train_examples', 5, 'Will sample '
                     'one of every n train input examples for evaluation, '
                     'where n is provided. This is only used if '
                     '`eval_training_data` is True.')
flags.DEFINE_string(
    'hparams_overrides', None, 'Hyperparameter overrides, '
    'represented as a string containing comma-separated '
    'hparam_name=value pairs.')
flags.DEFINE_string(
    'model_dir', None, 'Path to output model directory '
                       'where event and checkpoint files will be written.')
flags.DEFINE_string(
    'checkpoint_dir', None, 'Path to directory holding a checkpoint.  If '
    '`checkpoint_dir` is provided, this binary operates in eval-only mode, '
    'writing resulting metrics to `model_dir`.')

flags.DEFINE_integer('eval_timeout', 3600, 'Number of seconds to wait for an'
                     'evaluation checkpoint before exiting.')
flags.DEFINE_integer(
    'num_workers', 1, 'When num_workers > 1, training uses '
    'MultiWorkerMirroredStrategy. When num_workers = 1 it uses '
    'MirroredStrategy.')

FLAGS = flags.FLAGS

def main(unused_argv):
  flags.mark_flag_as_required('model_dir')
  flags.mark_flag_as_required('pipeline_config_path')
  tf.config.set_soft_device_placement(True)

  if FLAGS.checkpoint_dir:
    model_lib_v2.eval_continuously(
        hparams=model_hparams.create_hparams(FLAGS.hparams_overrides),
        pipeline_config_path=FLAGS.pipeline_config_path,
        model_dir=FLAGS.model_dir,
        train_steps=FLAGS.num_train_steps,
        sample_1_of_n_eval_examples=FLAGS.sample_1_of_n_eval_examples,
        sample_1_of_n_eval_on_train_examples=(
            FLAGS.sample_1_of_n_eval_on_train_examples),
        checkpoint_dir=FLAGS.checkpoint_dir,
        wait_interval=300, timeout=FLAGS.eval_timeout)
  else:
    if tf.config.get_visible_devices('TPU'):
      resolver = tf.distribute.cluster_resolver.TPUClusterResolver()
      tf.config.experimental_connect_to_cluster(resolver)
      tf.tpu.experimental.initialize_tpu_system(resolver)
      strategy = tf.distribute.experimental.TPUStrategy(resolver)
    elif FLAGS.num_workers > 1:
      strategy = tf.distribute.experimental.MultiWorkerMirroredStrategy()
    else:
      strategy = tf.compat.v2.distribute.MirroredStrategy()

    with strategy.scope():
      model_lib_v2.train_loop(
          hparams=model_hparams.create_hparams(FLAGS.hparams_overrides),
          pipeline_config_path=FLAGS.pipeline_config_path,
          model_dir=FLAGS.model_dir,
          train_steps=FLAGS.num_train_steps,
          use_tpu=FLAGS.use_tpu)

if __name__ == '__main__':
  tf.app.run()

I did a quick search and I found that tf.app has been removed from TF2, yet it is still used in TF2 files?
Is there an easy workaround to this? I can't seem to get it to work, but that might just be because I'm not exactly a good programmer.
Thanks.

@007Nick700
Could you please refer to this comment of similar resolved issue and let us know.


BOT Keep Loading

Hello,
I have configured the app as instruction but it keeps loadin on my SharePoint sites
Here is the configuration Details
.\Configure-McsForSite.ps1 -siteUrl "https://mytenant.sharepoint.com/sites/SPODemo" -botUrl "https://copilotstudio.microsoft.com/environments/ENVID/botid" -botName "Nascar Master" -customScope "api://APPID/SW92227-Test.Read" -clientId "Client ID" -authority "https://login.microsoftonline.com/TenantID" -buttonLabel "Nascar Test"

Any Updates

Any updates


Bug: Console error parsing id token

Prerequisites

[X] I have searched the repository’s issues and Kinde community to ensure my issue isn’t a duplicate
[X] I have checked the latest version of the library to replicate my issue
[X] I have read the contributing guidelines
[X] I agree to the terms within the code of conduct

Describe the issue
Occasionally when parsing the ID token the following console error is thrown

Library URL
https://github.com/kinde-oss/kinde-auth-pkce-js
Library version
3.0.16
Operating system(s)
macOS
Operating system version(s)
Ventura
Further environment details
No response
Reproducible test case URL
No response
Additional information
No response

This seems to be resolved


Appstudio update test-component-pac-vopn

Pipelines as Code configuration proposal

Pipelines as Code CI/test-component-pac-vopn-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
7 seconds
init

✅ Succeeded
20 seconds
clone-repository

✅ Succeeded
34 seconds
build-container

✅ Succeeded
15 seconds
deprecated-base-image-check

✅ Succeeded
3 minutes
clair-scan

✅ Succeeded
14 seconds
sanity-inspect-image

✅ Succeeded
44 seconds
clamav-scan

✅ Succeeded
16 seconds
sbom-json-check

✅ Succeeded
12 seconds
sanity-optional-label-check

✅ Succeeded
12 seconds
sanity-label-check

✅ Succeeded
8 seconds
show-summary

Pipelines as Code CI/test-component-pac-vopn-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
5 seconds
init

✅ Succeeded
13 seconds
clone-repository

✅ Succeeded
36 seconds
build-container

✅ Succeeded
12 seconds
sanity-inspect-image

✅ Succeeded
11 seconds
deprecated-base-image-check

✅ Succeeded
8 seconds
clair-scan

✅ Succeeded
37 seconds
clamav-scan

✅ Succeeded
11 seconds
sbom-json-check

✅ Succeeded
16 seconds
sanity-label-check

✅ Succeeded
16 seconds
sanity-optional-label-check

✅ Succeeded
10 seconds
show-summary


tests leak fix

Fixes leaks introduced by #112

Hmm does not seem to be fixed: https://cdash.hdfgroup.org/viewDynamicAnalysis.php?buildid=20646

From https://cdash.hdfgroup.org/viewDynamicAnalysisFile.php?id=46470:
=================================================================
==7586==ERROR: LeakSanitizer: detected memory leaks

Direct leak Direct leak of 22 byte(s) in 1 object(s) allocated from:
    #0 0x7f763fdf81f8 in __interceptor_malloc ../../.././libsanitizer/asan/asan_malloc_linux.cc:38
    #1 0x7f7640f0fea8 in NA_Test_server_init /home/travis/build/mercury-hpc/mercury/Testing/na/na_test.c:442
    #2 0x7f7640f0b235 in HG_Test_server_init /home/travis/build/mercury-hpc/mercury/Testing/mercury_test.c:323
    #3 0x7f7640efe9be in main /home/travis/build/mercury-hpc/mercury/Testing/test_server.c:57
    #4 0x7f763e4547ec in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x217ec)

That doesn't seem right... It's reporting a leak for something that 8 lines later is obviously freed.
Direct leak Direct leak of 16 byte(s) in 1 object(s) allocated from:
    #0 0x7f763fdf81f8 in __interceptor_malloc ../../.././libsanitizer/asan/asan_malloc_linux.cc:38
    #1 0x7f763f4ba7fd in na_bmi_addr_self /home/travis/build/mercury-hpc/mercury/src/na/na_bmi.c:866
    #2 0x7f763f4b2d16 in NA_Addr_self /home/travis/build/mercury-hpc/mercury/src/na/na.c:629
    #3 0x7f7640f0fe76 in NA_Test_server_init /home/travis/build/mercury-hpc/mercury/Testing/na/na_test.c:436
    #4 0x7f7640f0b235 in HG_Test_server_init /home/travis/build/mercury-hpc/mercury/Testing/mercury_test.c:323
    #5 0x7f7640efe9be in main /home/travis/build/mercury-hpc/mercury/Testing/test_server.c:57
    #6 0x7f763e4547ec in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x217ec)

Same here, Addr_self and Addr_free for BMI correspond to a single malloc/free pair.
Also, does the check that github reports not correspond to all of the tests done?

Yeah the check only means that the configure/build/test were run sucessfully, you still need to look at the dashboard to check that test results are passing or not. I can probably make it more strict so that it actually fails every time a test does not pass.

Yeah that's probably a good idea. Also, how do I tell which branch the cdash website is showing? I didn't see that info anywhere.

Just check the travis build number in the build name: travis-ci-linux-x64-gcc-debug-addresssanitizer-231

My problem is that if I make it more strict, it will fail for everything, even for random failures like we currently have with the CCI tcp plugin... so I would rather keep it more permissive for now.

I just tried on my laptop and I don't see the leaks anymore with tsan, I'm not sure why it shows up with travis still...

The leaks are gone on my end, but I am getting data race output from tsan for cci+sm tests in a free call from sm_handle_connect_reply. Completely different output from the cdash stuff.

Oh, and I've been using gcc 5.1 for testing.

Well we don't test sm on travis so that's normal. Also Cdash only collects the results that the travis build submits, it's not doing any test itself.

I'm using 5.3.1 here and it's gone too for me. I suspect travis is not fetching the pull request correctly...

Can you try to push a fake commit to that pull request to trigger the build again?

Is there something about the travis env preventing running the sm tests?

Yes there were some failures, I forgot now the actual error though I would have to try again

Hmm that's really bizarre, same failures again in the dashboard after your fake commit...

This is quite confusing. Perhaps we're running into some local compiler issues (ie the asan/tsan libs used in the local gcc get pointed at the system gcc)?

If we wanted to, we could get gcc 4.8 through an ubuntu PPA - https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/test . That should have the sanitizers.

Yes I tried those already, it's buggy, and same for that https://bugs.launchpad.net/ubuntu/+source/gcc-5/+bug/1413474

I don't think it's a compiler issue... ok I have another idea :) can you try to push a commit that prints a line in the test so that we can see if we're testing the right version?

Committed - search for the string "ZZZ" in the output.
FWIW, I'm running into some strange issues in my local setup. tsan/asan cause the na_simple_cci_* test to fail. Clients run fine, but the server Finalizes and returns a non-zero exit code without any indication of error. However, when I run the test directly (na_test_server/na_test_client), the server hangs in the progress loop after the clients are finished and exit, test_done_g never having been set.
Tests are green when not using *san.

Yes there is an issue with the na_simple_cci* tests, I saw that too, I haven't figured out yet why it fails, that's the only ones that fail.

Oh, I figured out why the hang was happening - there was a hard-coded number of expected clients under those tests (and that count (2) doesn't match up with the number of clients ran in the test (4) ).

Awesome, @JohnPJenkins!

As I suspected, I don't see the string, so that means it's indeed not testing the right version... funny

Maybe they just broke something in the travis code

More specifically, na_simple_* loops over the count of expected clients doing a progress loop (with timeout NA_MAX_IDLE_TIME), which is set in NA_Test_server_init to be MPIEXEC_MAX_NUMPROCS. NUMRPOCS is 2, the -np option is given as 4.
Tests aren't green still - here's the leak report for na_test_server -c cci -p sm:
Direct leak of 32 byte(s) in 1 object(s) allocated from:
    #0 0x7f4af79f009a in __interceptor_malloc ../../.././libsanitizer/asan/asan_malloc_linux.cc:38
    #1 0x7f4af676c43a in tsearch (/lib/x86_64-linux-gnu/libc.so.6+0xf143a)

Indirect leak of 4096 byte(s) in 1 object(s) allocated from:
    #0 0x7f4af79f0201 in __interceptor_calloc ../../.././libsanitizer/asan/asan_malloc_linux.cc:54
    #1 0x7f4af22e5114 in sm_create_conn /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:1522
    #2 0x7f4af22e65b5 in sm_handle_connect /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:1935
    #3 0x7f4af22e705e in sm_progress_sock /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:2143
    #4 0x7f4af22e31b3 in sm_conn_thread /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:795
    #5 0x7f4af6465e99 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x7e99)

Indirect leak of 4096 byte(s) in 1 object(s) allocated from:
    #0 0x7f4af79f0201 in __interceptor_calloc ../../.././libsanitizer/asan/asan_malloc_linux.cc:54
    #1 0x7f4af22e51bf in sm_create_conn /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:1539
    #2 0x7f4af22e65b5 in sm_handle_connect /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:1935
    #3 0x7f4af22e705e in sm_progress_sock /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:2143
    #4 0x7f4af22e31b3 in sm_conn_thread /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:795
    #5 0x7f4af6465e99 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x7e99)

Indirect leak of 144 byte(s) in 1 object(s) allocated from:
    #0 0x7f4af79f0201 in __interceptor_calloc ../../.././libsanitizer/asan/asan_malloc_linux.cc:54
    #1 0x7f4af22e501e in sm_create_conn /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:1498
    #2 0x7f4af22e65b5 in sm_handle_connect /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:1935
    #3 0x7f4af22e705e in sm_progress_sock /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:2143
    #4 0x7f4af22e31b3 in sm_conn_thread /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:795
    #5 0x7f4af6465e99 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x7e99)

Indirect leak of 64 byte(s) in 1 object(s) allocated from:
    #0 0x7f4af79f0201 in __interceptor_calloc ../../.././libsanitizer/asan/asan_malloc_linux.cc:54
    #1 0x7f4af7744356 in handle_connect_request /nfs2/jenkins/work/sds/mercury/src/na/na_cci.c:1786
    #2 0x7f4af7745379 in na_cci_progress /nfs2/jenkins/work/sds/mercury/src/na/na_cci.c:1927
    #3 0x7f4af771cea5 in NA_Progress /nfs2/jenkins/work/sds/mercury/src/na/na.c:1482
    #4 0x403791 in main /nfs2/jenkins/work/sds/mercury/Testing/na/test_server.c:298
    #5 0x7f4af669c76c in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2176c)

Indirect leak of 64 byte(s) in 1 object(s) allocated from:
    #0 0x7f4af79f0201 in __interceptor_calloc ../../.././libsanitizer/asan/asan_malloc_linux.cc:54
    #1 0x7f4af22e500b in sm_create_conn /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:1497
    #2 0x7f4af22e65b5 in sm_handle_connect /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:1935
    #3 0x7f4af22e705e in sm_progress_sock /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:2143
    #4 0x7f4af22e31b3 in sm_conn_thread /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:795
    #5 0x7f4af6465e99 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x7e99)

Indirect leak of 31 byte(s) in 1 object(s) allocated from:
    #0 0x7f4af79bbd8f in __interceptor_strdup ../../.././libsanitizer/asan/asan_interceptors.cc:514
    #1 0x7f4af22e5090 in sm_create_conn /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:1509
    #2 0x7f4af22e65b5 in sm_handle_connect /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:1935
    #3 0x7f4af22e705e in sm_progress_sock /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:2143
    #4 0x7f4af22e31b3 in sm_conn_thread /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:795
    #5 0x7f4af6465e99 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x7e99)

Indirect leak of 31 byte(s) in 1 object(s) allocated from:
    #0 0x7f4af79bbd8f in __interceptor_strdup ../../.././libsanitizer/asan/asan_interceptors.cc:514
    #1 0x7f4af77445b3 in handle_connect_request /nfs2/jenkins/work/sds/mercury/src/na/na_cci.c:1797
    #2 0x7f4af7745379 in na_cci_progress /nfs2/jenkins/work/sds/mercury/src/na/na_cci.c:1927
    #3 0x7f4af771cea5 in NA_Progress /nfs2/jenkins/work/sds/mercury/src/na/na.c:1482
    #4 0x403791 in main /nfs2/jenkins/work/sds/mercury/Testing/na/test_server.c:298
    #5 0x7f4af669c76c in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2176c)

Indirect leak of 31 byte(s) in 1 object(s) allocated from:
    #0 0x7f4af79bbd8f in __interceptor_strdup ../../.././libsanitizer/asan/asan_interceptors.cc:514
    #1 0x7f4af22e52a9 in sm_create_conn /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:1557
    #2 0x7f4af22e65b5 in sm_handle_connect /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:1935
    #3 0x7f4af22e705e in sm_progress_sock /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:2143
    #4 0x7f4af22e31b3 in sm_conn_thread /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:795
    #5 0x7f4af6465e99 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x7e99)

SUMMARY: AddressSanitizer: 8589 byte(s) leaked in 9 allocation(s)

Could that be related to #111 ?

Hmm, can't tell. Some would seem to be legit CCI leaks (leaks caused in CCI's managed progress thread), while others are in the CCI NA. Don't know what's up with tsearch leaking :) - any code using that?

./src/plugins/ctp/sm/ctp_sm_api.c:1674:	node = tsearch(sconn, &sep->conns, sm_compare_conns);

Ah, tsearch allocates when it fails to find a node and inserts a new one.
Is there any way we can add suppressions similar to valgrind? We shouldn't fail HG builds b/c leaks in BMI/CCI. (BMI fails when it is instrumented with asan because a hash function overreads its input).

asan does allow suppressions: http://clang.llvm.org/docs/AddressSanitizer.html#issue-suppression

We can pass options to Ctest using CTEST_MEMORYCHECK_SANITIZER_OPTIONS, see for example in Testing/script/travis_script.cmake line 88, so I think we could do that

Well but that's another topic, I would like to understand first why travis is not testing the right revision in the pull requests...

I stepped through the travis log and re-ran the git commands locally with no issue. Is this another bad caching issue?

Here is what travis does:
0.60s$ git clone --depth=50 https://github.com/mercury-hpc/mercury.git mercury-hpc/mercury

Cloning into 'mercury-hpc/mercury'...

remote: Counting objects: 427, done.

remote: Compressing objects: 100% (280/280), done.

remote: Total 427 (delta 246), reused 247 (delta 144), pack-reused 0

Receiving objects: 100% (427/427), 270.00 KiB | 0 bytes/s, done.

Resolving deltas: 100% (246/246), done.

Checking connectivity... done.

$ cd mercury-hpc/mercury

0.30s$ git fetch origin +refs/pull/114/merge:

remote: Counting objects: 18, done.

remote: Compressing objects: 100% (17/17), done.

remote: Total 18 (delta 14), reused 4 (delta 1), pack-reused 0

Unpacking objects: 100% (18/18), done.

From https://github.com/mercury-hpc/mercury

 * branch            refs/pull/114/merge -> FETCH_HEAD

$ git checkout -qf FETCH_HEAD

Can you add in a search to the test shell or travis build matrix after the git operations happen? ie a find mercury-hpc/mercury -name \*.c | xargs grep ZZZ? Might need to change the path of course.

I'm heading out for the weekend, will be back on Wednesday.

OK! I'll post here if I find something. For now what I can say is that the git command is correct and gets your commit with the string but the string is not in log. You can get the log by clicking on raw log and look for the string which should appear just before the listen printf.

osx fix in c98da537119d4732190e477de7fcfdb1558d235c and pull request ctest fix in 5f9aa818bf1e75bd53937ef8d5fd585b7f6aba49

Hey, noticed this (minus the debug statements) got pulled. Were the issues we were having resolved?

Yes I fixed the issue on OS X (segfault with locator in na_info_parse) and the pull request problem where ctest was actually doing a checkout of another revision so it's not doing that anymore. I haven't fixed the na_simple_* test though but that should be a separate issue.

That's good to hear! Now back to productive work :).

Oh and before we change topic and forget, let me know when you have a look at #107

I've made a note of it, though I don't know exactly when I'll look at it. I have a fairly hectic week ahead of me...

Oh no problem, just meant when you have time, that's really minor anyway, thanks!

Hi John,
I just pushed a commit to CCI that fixes several leaks in the SM connection path. Can you recheck the below or are you filtering out CCI internal leak messages?
Scott

On Jul 1, 2016, at 6:16 PM, John Jenkins<EMAIL_ADDRESS>wrote:
More specifically, na_simple_* loops over the count of expected clients doing a progress loop (with timeout NA_MAX_IDLE_TIME), which is set in NA_Test_server_init to be MPIEXEC_MAX_NUMPROCS. NUMRPOCS is 2, the -np option is given as 4.
Tests aren't green still - here's the leak report for na_test_server -c cci -p sm:
Direct leak of 32 byte(s) in 1 object(s) allocated from:
#0 0x7f4af79f009a in __interceptor_malloc ../../.././libsanitizer/asan/asan_malloc_linux.cc:38
#1 0x7f4af676c43a in tsearch (/lib/x86_64-linux-gnu/libc.so.6+0xf143a)
Indirect leak of 4096 byte(s) in 1 object(s) allocated from:
#0 0x7f4af79f0201 in __interceptor_calloc ../../.././libsanitizer/asan/asan_malloc_linux.cc:54
#1 0x7f4af22e5114 in sm_create_conn /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:1522
#2 0x7f4af22e65b5 in sm_handle_connect /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:1935
#3 0x7f4af22e705e in sm_progress_sock /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:2143
#4 0x7f4af22e31b3 in sm_conn_thread /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:795
#5 0x7f4af6465e99 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x7e99)
Indirect leak of 4096 byte(s) in 1 object(s) allocated from:
#0 0x7f4af79f0201 in __interceptor_calloc ../../.././libsanitizer/asan/asan_malloc_linux.cc:54
#1 0x7f4af22e51bf in sm_create_conn /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:1539
#2 0x7f4af22e65b5 in sm_handle_connect /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:1935
#3 0x7f4af22e705e in sm_progress_sock /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:2143
#4 0x7f4af22e31b3 in sm_conn_thread /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:795
#5 0x7f4af6465e99 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x7e99)
Indirect leak of 144 byte(s) in 1 object(s) allocated from:
#0 0x7f4af79f0201 in __interceptor_calloc ../../.././libsanitizer/asan/asan_malloc_linux.cc:54
#1 0x7f4af22e501e in sm_create_conn /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:1498
#2 0x7f4af22e65b5 in sm_handle_connect /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:1935
#3 0x7f4af22e705e in sm_progress_sock /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:2143
#4 0x7f4af22e31b3 in sm_conn_thread /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:795
#5 0x7f4af6465e99 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x7e99)
Indirect leak of 64 byte(s) in 1 object(s) allocated from:
#0 0x7f4af79f0201 in __interceptor_calloc ../../.././libsanitizer/asan/asan_malloc_linux.cc:54
#1 0x7f4af7744356 in handle_connect_request /nfs2/jenkins/work/sds/mercury/src/na/na_cci.c:1786
#2 0x7f4af7745379 in na_cci_progress /nfs2/jenkins/work/sds/mercury/src/na/na_cci.c:1927
#3 0x7f4af771cea5 in NA_Progress /nfs2/jenkins/work/sds/mercury/src/na/na.c:1482
#4 0x403791 in main /nfs2/jenkins/work/sds/mercury/Testing/na/test_server.c:298
#5 0x7f4af669c76c in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2176c)
Indirect leak of 64 byte(s) in 1 object(s) allocated from:
#0 0x7f4af79f0201 in __interceptor_calloc ../../.././libsanitizer/asan/asan_malloc_linux.cc:54
#1 0x7f4af22e500b in sm_create_conn /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:1497
#2 0x7f4af22e65b5 in sm_handle_connect /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:1935
#3 0x7f4af22e705e in sm_progress_sock /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:2143
#4 0x7f4af22e31b3 in sm_conn_thread /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:795
#5 0x7f4af6465e99 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x7e99)
Indirect leak of 31 byte(s) in 1 object(s) allocated from:
#0 0x7f4af79bbd8f in __interceptor_strdup ../../.././libsanitizer/asan/asan_interceptors.cc:514
#1 0x7f4af22e5090 in sm_create_conn /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:1509
#2 0x7f4af22e65b5 in sm_handle_connect /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:1935
#3 0x7f4af22e705e in sm_progress_sock /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:2143
#4 0x7f4af22e31b3 in sm_conn_thread /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:795
#5 0x7f4af6465e99 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x7e99)
Indirect leak of 31 byte(s) in 1 object(s) allocated from:
#0 0x7f4af79bbd8f in __interceptor_strdup ../../.././libsanitizer/asan/asan_interceptors.cc:514
#1 0x7f4af77445b3 in handle_connect_request /nfs2/jenkins/work/sds/mercury/src/na/na_cci.c:1797
#2 0x7f4af7745379 in na_cci_progress /nfs2/jenkins/work/sds/mercury/src/na/na_cci.c:1927
#3 0x7f4af771cea5 in NA_Progress /nfs2/jenkins/work/sds/mercury/src/na/na.c:1482
#4 0x403791 in main /nfs2/jenkins/work/sds/mercury/Testing/na/test_server.c:298
#5 0x7f4af669c76c in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2176c)
Indirect leak of 31 byte(s) in 1 object(s) allocated from:
#0 0x7f4af79bbd8f in __interceptor_strdup ../../.././libsanitizer/asan/asan_interceptors.cc:514
#1 0x7f4af22e52a9 in sm_create_conn /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:1557
#2 0x7f4af22e65b5 in sm_handle_connect /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:1935
#3 0x7f4af22e705e in sm_progress_sock /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:2143
#4 0x7f4af22e31b3 in sm_conn_thread /nfs2/jenkins/work/sds/cci/src/plugins/ctp/sm/ctp_sm_api.c:795
#5 0x7f4af6465e99 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x7e99)
SUMMARY: AddressSanitizer: 8589 byte(s) leaked in 9 allocation(s)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Thanks Scott! I'll plan to look at it either today or later next week.
I believe the way it currently works is that Travis success is just based on the test suite, but it also performs and reports through HDFs CDash interface the sanitizer results. @soumagne?

Yes it reports thread sanitizer and address sanitizer results. https://cdash.hdfgroup.org/index.php?project=MERCURY The interface should be updated and cleaner when we update to the latest version of cdash but the IT person has not gotten to it yet.
We are not filtering out CCI leak messages.

Also travis does not test sm for now, I have to get back to it as they were some issues when I enabled it, I can try again though.

@scottatchley Just checked SM - connection leaks are gone. Thanks for the fix!

Thanks for the check!
Are there any outstanding issues with the sm transport? Blocking mode? Race conditions? Other?

From: John Jenkins<EMAIL_ADDRESS>Date: July 8, 2016 at 2:09:21 PM EDT
To: mercury-hpc/mercury<EMAIL_ADDRESS>Cc: Mention<EMAIL_ADDRESS>Atchley, Scott<EMAIL_ADDRESS>Subject: Re: [mercury-hpc/mercury] tests leak fix (#114)
@scottatchleyhttps://github.com/scottatchley Just checked SM - connection leaks are gone. Thanks for the fix!

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/mercury-hpc/mercury/pull/114#issuecomment-231431677, or mute the threadhttps://github.com/notifications/unsubscribe/AAlWwOC_215V5TCmBGaknMqzAFxpFQdpks5qTpJNgaJpZM4JDWr7.

I'll defer to @carns on blocking support, haven't tried it myself. Otherwise, nothing outstanding AFAICT!

Blocking mode on the cci/sm transport works great for me!  Not even a hiccup.

Ok, thanks for the confirmation. I will continue to focus on verbs. I will probably write a CCI native test that spawns multiple threads on both a client and server and repeatedly connect, communicate, disconnect, and repeat.

@scottatchley , you might want to look at that: https://cdash.hdfgroup.org/viewDynamicAnalysisFile.php?id=46913
I enabled the sm transport in travis and am getting some errors.

FYI, the RMA options specifically will fail when using CCI/SM on some linux distros if you don't set /proc/sys/kernel/yama/ptrace_scope to 0 (as root).  This loosens permission restrictions on that system call to allow two pids owned by the same users to access each other's memory.
If CCI/SM gets a predictable errno out of the cma system calls in this case then maybe it could print a verbose error message suggesting that fix?  A few of us have bumped into it at different times.
Not sure if that's what's going on, but it might be worth checking in that docker image.

Hmm ok thanks I just checked and it's indeed set to 1 so I guess that's the problem. I can't change that value though as this image does not allow me to be root unless I use another image which requires other changes and increases the boot time.

1 - restricted ptrace: a process must have a predefined relationship
with the inferior it wants to call PTRACE_ATTACH on. By default,
this relationship is that of only its descendants when the above
classic criteria is also met. To change the relationship, an
inferior can call prctl(PR_SET_PTRACER, debugger, ...) to declare
an allowed debugger PID to call PTRACE_ATTACH on the inferior.
Using PTRACE_TRACEME is unchanged.
I guess we could also call prctl in that case...

You beat me to this.
This is only required if using CMA. If using the mmap bounce buffers, it is not needed.
Perhaps we can add the prctl() call if CMA is enabled. I am hesitant to do that in a library without warning the application user that this security feature has been disabled.
Thoughts/comments?

On Jul 11, 2016, at 6:00 PM, Jerome Soumagne<EMAIL_ADDRESS>wrote:
1 - restricted ptrace: a process must have a predefined relationship
with the inferior it wants to call PTRACE_ATTACH on. By default,
this relationship is that of only its descendants when the above
classic criteria is also met. To change the relationship, an
inferior can call prctl(PR_SET_PTRACER, debugger, ...) to declare
an allowed debugger PID to call PTRACE_ATTACH on the inferior.
Using PTRACE_TRACEME is unchanged.
I guess we could also call prctl in that case...

I just reread the process_vm_[write|read]v() manpage. If it fails with EPERM, I have added the following message:
ctp_sm_rma: process_vm_[write|read]v() failed because it cannot trace another process. See https://www.kernel.org/doc/Documentation/security/Yama.txt for more details.

Ah ok then for the time being I could just simply try to have CMA disabled on the travis images, I also understand now why only the tests that call NA_Put/NA_Get were failing.
Hmmm yes that's true, although that's probably not as worse as setting ptrace_scope to 0 as root... Just googled it to see if others had the same issue and found that discussion: https://www.open-mpi.org/community/lists/users/2015/02/26391.php ... looks like their decision was to enable CMA if no yama and no PR_SET_PTRACER.
Maybe the best solution is to keep the verbose error message or have an option force CMA I guess which would call prctl() and throw a warning...

CCI has --with-cma to enable CMA. Perhaps I should change the default to --without-cma and include a message in the configure --help output that enabling CMA will force the ability to trace? I could put more detail in the sm README.

I added prctl(PR_SET_PTRACER, PR_SET_PTRACER_ANY, 0, 0, 0) if sm is used in the mercury testing suite and everything is fine now with CMA.
Just been thinking a little more and if enabling CMA in CCI changes permissions under the hood then it may do too much in some cases if let's say somebody only wants to have CMA enabled between parent and child processes and not any process. I think the best option is to just keep the verbose error message and let the app decide :)

For my 2c, I like the idea of keeping cma on by default and just doing what we can via docs/error messages to tell people how to either turn it off or set permissions.
I'm worried about the failure mode of accidentally compiling without CMA support and then being confused by the resulting performance :)

Ok, I will leave configure alone. If it detects CMA, it will compile it in. If compiled in and it fails, it will print the warning once when the first RMA fails with EPERM.


PTX-1907  [torpedo] Torpedo failing to validate host on openshift 4.2…

modified code to use 'date'

Following torpedo job is using the code changes made in this request
https://jenkins.portworx.co/job/Torpedo/view/Torpedo 2.2/job/tp-openshift4.2-op-2.2-csi/

@nareshdesh could you please run a test on openshift 3.11 before merging, I remember it has some limited command set

@nareshdesh as thiago requested, let's run this PR on a openshift 4.2 job an merge after it passes.


pageserver: filtered WAL ingest for sharding

Problem
Currently, if one creates many shards they will all ingest all the data: not much use!  We want them to ingest a proportional share of the data each.
Closes: #6025
Summary of changes

WalIngest object gets a copy of the ShardIdentity for the Tenant it was created by.
While iterating the blocks part of a decoded record, blocks that do not match the current shard are ignored, apart from on shard zero where they are used to update relation sizes in observe_decoded_block (but not stored).
Before committing a DataDirModificiation from a WAL record, we check if it's empty, and drop the record if so.  This check is necessary (rather than just looking at the blocks part) because certain record types may modify blocks in non-obvious ways (e.g. ingest_heapam_record).
Add WAL ingest metrics to record the total received, total committed, and total filtered out
Behaviour for unsharded tenants is unchanged: they will continue to ingest all blocks, and will take the fast path through is_key_local that doesn't bother calculating any hashes.

After this change, shards store a subset of the tenant's total data, and accurate relation sizes are only maintained on shard zero.
Checklist before requesting a review

[ ] I have performed a self-review of my code.
[ ] If it is a core feature, I have added thorough tests.
[ ] Do we need to implement analytics? if so did you add the relevant metrics to the dashboard?
[ ] If this PR requires public announcement, mark it with /release-notes label and add several sentences in this section.

Checklist before merging

[ ] Do not forget to reformat commit message to not include the above checklist

If the filtering is done on the pageserver side, then we will have number of pageservers * number of shards as much internal network traffic as a factor to the WAL's traffic size. As a stopgap however this makes sense.


[18.09] openjpeg: adding patch for CVE-2018-7648

Motivation for this change
Part of #47122
Backporting #49542
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

Success on aarch64-linux (full log)
Attempted: openjpeg
Partial log (click to expand)
strip is /nix/store/y4ymnvgxygpq05h03kyzbj572zmh6zla-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/0x2s6r8m6qgdwnazg1kannbvmfafnvi1-openjpeg-2.3.0/lib  /nix/store/0x2s6r8m6qgdwnazg1kannbvmfafnvi1-openjpeg-2.3.0/bin
patching script interpreter paths in /nix/store/0x2s6r8m6qgdwnazg1kannbvmfafnvi1-openjpeg-2.3.0
checking for references to /build in /nix/store/0x2s6r8m6qgdwnazg1kannbvmfafnvi1-openjpeg-2.3.0...
shrinking RPATHs of ELF executables and libraries in /nix/store/2x4jix9131ssz1gjiyjjkiz483p74d6g-openjpeg-2.3.0-dev
strip is /nix/store/y4ymnvgxygpq05h03kyzbj572zmh6zla-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/2x4jix9131ssz1gjiyjjkiz483p74d6g-openjpeg-2.3.0-dev/lib
patching script interpreter paths in /nix/store/2x4jix9131ssz1gjiyjjkiz483p74d6g-openjpeg-2.3.0-dev
checking for references to /build in /nix/store/2x4jix9131ssz1gjiyjjkiz483p74d6g-openjpeg-2.3.0-dev...
/nix/store/0x2s6r8m6qgdwnazg1kannbvmfafnvi1-openjpeg-2.3.0

Success on x86_64-linux (full log)
Attempted: openjpeg
Partial log (click to expand)
strip is /nix/store/h0lbngpv6ln56hjj59i6l77vxq25flbz-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/jr4dsas5l12wy8qzagvcdinqihf2p6i2-openjpeg-2.3.0/lib  /nix/store/jr4dsas5l12wy8qzagvcdinqihf2p6i2-openjpeg-2.3.0/bin
patching script interpreter paths in /nix/store/jr4dsas5l12wy8qzagvcdinqihf2p6i2-openjpeg-2.3.0
checking for references to /build in /nix/store/jr4dsas5l12wy8qzagvcdinqihf2p6i2-openjpeg-2.3.0...
shrinking RPATHs of ELF executables and libraries in /nix/store/vrxn8dk591gpk88q15ig8f5m39bp43w2-openjpeg-2.3.0-dev
strip is /nix/store/h0lbngpv6ln56hjj59i6l77vxq25flbz-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/vrxn8dk591gpk88q15ig8f5m39bp43w2-openjpeg-2.3.0-dev/lib
patching script interpreter paths in /nix/store/vrxn8dk591gpk88q15ig8f5m39bp43w2-openjpeg-2.3.0-dev
checking for references to /build in /nix/store/vrxn8dk591gpk88q15ig8f5m39bp43w2-openjpeg-2.3.0-dev...
/nix/store/jr4dsas5l12wy8qzagvcdinqihf2p6i2-openjpeg-2.3.0

As we have lots of full rebuilds scheduled for 18.09 due to security issues, let's keep collecting and merge them all together at once so Hydra only has one full rebuild to handle.
Please coordinate on Freenode in #nixos-security before merging this.


Add cowplot and other requirements to shiny dockerfile

Adds the following to the docker file used to run the shiny webserver:

cowplot used in app.R
digest used in app.R
patchwork used in app.R
viridis used in methods.Rmd
pander used in report_depmap_app.R

Removes shinyWidgets and causaleffect since they don't appear to be currently used.
Additional changes to fix issues deploying:

rename markdown files to match actual case in code/app.R
increases startup timeout to 180 seconds

Fixes #13

Looks OK. Could mention that this fixes issue  #13

Looks OK. Could mention that this fixes issue #13

Done.

Can you also add the following to the docker file used to run the shiny webserver:

DT used in app.R

This would fix and close issue #26 , I think.

I added the DT library to Dockerfile.shiny.
Before #26 is completely fixed we will need a PR to merge this commit on develop into master:
https://github.com/hirscheylab/ddh/commit/2c91707903c0c33b2da0f6eb3bba6627e1ff0367

I cherry-picked 2c91707 into this branch


The "main" in package.json should reference the common js package

Not required as the "main" can point to a CJS or UMD Module


NavigationService Binding in HamburguerMenu is failing

Hi, first congrats for this awesomeeee work!
But, I work with Prism 6 and Mvvm, of course, but when I do it:
<controls:HamburgerMenu NavigationService="{Binding NavigationService}">
    <controls:HamburgerButtonInfo>
        <StackPanel Orientation="Horizontal" VerticalAlignment="Center">
            <SymbolIcon Height="48" Symbol="Home" Width="48" />
            <TextBlock Margin="12, 0, 0, 0" Text="Home" VerticalAlignment="Center" />
        </StackPanel>
    </controls:HamburgerButtonInfo>
</controls:HamburgerMenu>

This is my view model
private readonly INavigationService _navigationService;

public INavigationService NavigationService
{
    get { return _navigationService; }
}

public MainPageViewModel(IUserRepository userRepository, INavigationService navigationService)
{
    _navigationService = navigationService;
}

When the page loads I just see this behavior:

I am debugging the code to try to find the issue, but I just realize that the binding on navigation service not works, because the get accessor in NavigationService it is never called, but if I do this binding in a TextBlock for example it works, can you help me?

Blank screen shot? Haha! Thanks.

**First
Are you sure you want to put the HamburgerMenu in your MainPage? Could you please review the Minimal project and double-check you are doing this right?
**Second
Are you sure you want to NOT implement INavigable in your view-model? In Template10, this means the NavigationService is automatically injected for you. Again, see Minimal.
**Third
I have never considered this scenario, but I agree that it should work. Why it is not working is unclear to me, but I will not able to chase it for a while. If you discover the reason, I recommend you create a pull request I can handle for you. I hope you understand.

The navigation service is injected by Unity Container.

How are you ensuring that the Nav Service is the correct service for the frame?


Cant't edit any shortcut

Quicksilver 1.5.4, Sierra 10.12.5, plugins disabled
I'm unable to edit any shortcut. Not in general preferences nor in triggers menu. I want to change or disable activation shortcut, is there any config key that I can edit?

This has been fixed. The fix will appear in the next release.
See #2361


Speed up things with optimized gzip compression

Hey,
the following nginx changes let us save 50 percent of the traffic made by an default wordpress installation.
What do you think?
Have a nice day! 🙂

thueske

Hey m8,
definitely a good idea.
I didn't consider to also activate gzip in the "sub"-webserver configs since it should already be enabled be the nginx-proxy in the first place.
Nevertheless it should not hurt to implement it in the "sub"-nginx too.
Better safe than sorry. 😆
Thank you ! (:


Check for all public services

For the public command, check for everything from https://github.com/arkadiyt/aws_public_ips
The remaining services to check for are:

APIGateway
Cloudfront
Lightsail
Redshift
ElasticSearch

Redshift and ElasticSearch would each need to be added as resources to the prepare step as they have Security Groups.
Lightsail is sort of it's own beast, but would need to be added to the prepare step.
APIGateway and CloudFront can be added independently.

Mostly handled in #157 .  The public command does not handle Redshift, ElasticSearch, or Lightsail, but the audit command will give some info about these.


TS-4892: Metric wrong for http.current_active_client_connections

Moved the m_active flag to ProxyClientSession.  Added set_session_activate and clear_session_activate methods which will only increment/decrement the current_active_client_connections counter if the m_active flag changes value.
In all cases, the set_session_action is called from HttpSM when the request header is successfully parsed.
For Http1, the clear_session_active is called when the transaction is completed and when the session is closed.
For Http2, the clear_session_active is called when the number of active streams goes to zero.  The session may not necessarily be closing at this point, but it is idle until another stream comes in.
We have been running with this patch in production

FreeBSD build successful! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/870/ for details.

Linux build successful! See https://ci.trafficserver.apache.org/job/Github-Linux/766/ for details.


chore(noir): Release 0.3.0

:robot: I have created a release beep boop
0.3.0 (2023-03-10)
⚠ BREAKING CHANGES

nargo: rename contract command to codegen-verifier (#959)
replace dummy ABIs with FunctionSignature type alias (#930)
nargo: save program ABI alongside ACIR (#922)
nargo: restrict CliError visibility to crate (#911)
prevent inconsistent language usage in Driver (#881)
abi: add explicit return type field to ABI. (#865)
abi: merge both abi encoding/decoding methods (#862)
abi: add an explicit mapping from ABI params to witness indices (#851)
Allow impls on primitive types (#847)

Features

abi: add an explicit mapping from ABI params to witness indices (#851) (5bd4bd5)
abi: add explicit return type field to ABI. (#865) (8ca5676)
abi: merge both abi encoding/decoding methods (#862) (fecd32c)
add support for reading boolean arrays from toml (#900) (93d83bf)
Allow impls on primitive types (#847) (479da0e)
ci: Publish noir_wasm when we cut a release (#871) (5186ab9)
compile: compile w/dependencies and options (#965) (3f897f6)
compile: Noir std lib embedded (#973) (13b9069)
Implement basic contracts (#944) (8ba3ab2)
Implement endianness specified versions of to_bytes to_radix and to_bits (#914) (43abc6b)
nargo: save program ABI alongside ACIR (#922) (ddaf305)
separate contract/program compilation from IO (#967) (c60f545)
Silence output of prove and verify (#892) (811b346)
ssa: add location to ssa instructions (#931) (356858b)
update to ACVM 0.5.0 (#902) (9b58da4)

Bug Fixes

abi: ensure that return value is loaded from toml (#883) (adba24c)
add more readable error for missing argument in toml (#971) (e31f41f)
allow parsing strings from toml into booleans (#894) (f729a00)
check the argument count of generic types (#970) (2688dc4)
compute witness when println evaluated before input (#891) (2727b34)
correct type checking to handle false bools (#893) (6c7aa2f)
display command description in CLI for nargo prove (#949) (2829af1)
evaluate constant division (#909) (b91307b)
Fix multiple call of to_le_bytes (#941) (2ee0119)
generate valid toml when outputting nested structs  (#936) (ba947a7)
Improve member access error (#940) (9b5b5f6)
nargo: Switch order of writing acir file and acir checksum file (#895) (4fc94dc)
nargo: Use yml extension for bug report link presented upon panic (#960) (f7b3711)
nargo: Use yml extension on the bug report link presented upon panic (f7b3711)
noir_wasm: Update wasm ACIR serialization (#898) (575436f)
Optimize parser (#869) (e927a39)
prevent inconsistent language usage in Driver (48cda7a)
prevent inconsistent language usage in Driver (#881) (48cda7a)
properly initialise Evaluator in test (#863) (bbb70bd)
properly initialise Evaluator in test (bbb70bd)
Remove uses of std::process::exit (#963) (870ea46)
ssa: fix the compile-time check for equality in acir-gen (#904) (161e4fb)

Miscellaneous Chores

nargo: rename contract command to codegen-verifier (#959) (2e63492)
nargo: restrict CliError visibility to crate (#911) (ed0e1ab)
replace dummy ABIs with FunctionSignature type alias (#930) (156125b)

This PR was generated with Release Please. See documentation.

We should probably push out a new release next week as the docs have gotten ahead of the releases and the changes are starting to accumulate.

@TomAFrench can you approve this PR please

@kevaundray One thing to be aware of is that this release will break usage of noirup due to https://github.com/noir-lang/noirup/issues/14. We may want to perform a quick fix for this before releasing.

@kevaundray One thing to be aware of is that this release will break usage of noirup due to noir-lang/noirup#14. We may want to perform a quick fix for this before releasing.

Good catch -- didn't see that issue, if its a quick fix, it makes sense to wait -- note that we probably want to block all PRs that modify docs until we release this

Yep, it's a quick fix. I've made a PR to address the issue here: https://github.com/noir-lang/noirup/pull/15

@kevaundray We should be gtg once https://github.com/noir-lang/noirup/pull/15 is merged.

@TomAFrench That PR should now be merged!

:robot: Release is at https://github.com/noir-lang/noir/releases/tag/v0.3.0 :sunflower:


Documentation - Creating new OpenAI account and get an API KEY

Document creating new OpenAI account and how to get an API KEY. This can be initially free new account to show user what to expect. (OpenAI account credits do expire even if not used)

Creating a New OpenAI Account
Visit OpenAI Website:

Go to the OpenAI platform website: platform.openai.com.

Sign Up:

Click on the 'Sign Up' button.
Enter your email address and create a password, or use your Google, Microsoft, or Apple account for a quicker sign-up.

Tell Us About You:

Fill in your First Name, Last Name, and Birthday.
Click ‘Agree’ to accept terms and conditions.

Verification (If you signed up with email and password):

You will receive a verification email from OpenAI.
Open the email and click on the verification link to activate your account.

Obtaining an API Key
Access API Section:

Once your account is set up, log in and navigate to the OpenAI dashboard.
Click on 'API Keys' in the dashboard.

Phone Verification:

Enter your phone number for verification.
You will receive a verification code via text message.
Enter this code in the provided space to verify your phone number.

Create API Key:

Look for the option to create a new API key.
Name your key for easy identification (e.g., 'GranContentKit').
Click 'Create Secret Key'.

Copy API Key:

Your new API key will be displayed on the screen.
Copy this key and store it securely. It is crucial as it will not be displayed again.
Consider saving it in a secure note or password manager.

Free Account Limitations:

Start experimenting with $5 in free credit that can be used during your first 3 months. To keep things simple and flexible, pay only for the resources you use. (Pricing)
Be aware that a free account may have limitations on the number of API calls or access to certain models.
Review these limitations to understand the scope of your account.

Notes for Beginners

API Key Security: Treat your API key like a sensitive password. Keep it confidential.
Dashboard Familiarization: Explore the OpenAI dashboard to understand its features.
Assistance: If you're stuck, seek help from online forums, OpenAI support, or knowledgeable friends.
Stay Informed: Monitor OpenAI for feature updates or policy changes.

Integrating with Salesforce (GCAI Playground)

Salesforce External Credential Configuration: Use your new OpenAI API key to configure the External Credential in Salesforce. This is essential for integrating AI functionalities with Salesforce's LWC (Lightning Web Components).

Default Model Usage

Model Selection: The GCAI Playground uses the gpt-3.5-turbo-instruct model by default. Note that models like GPT-4 might require a paid account and could lead to Salesforce API callout timeouts.

Compliance and Disclaimer

Responsibility: Your integration of OpenAI with Salesforce via GCAI Playground must comply with both Salesforce and OpenAI's terms, considering security and compliance aspects.

Additional Tips

Updates and Security: Regularly check for updates in OpenAI's API and usage policies. Keep your API key secure.
Support and Documentation: For detailed information, refer to OpenAI's official documentation and seek support from community forums or OpenAI's help center.

 Remember, these instructions are designed to guide you through each step with ease and clarity.

@iandrosov I have added the documentation above. Let me know if it needs any adjustments or if I need to add it anywhere else.


Use backup path from applicationbackup to validate deletion

Instead of using "namespace+backup name" use backup.Status.BackupPath to validate if the backup
has been deleted from the cloud
Signed-off-by: Rohit-PX<EMAIL_ADDRESS>

Tested here:
    --- PASS: TestApplicationBackup (4357.35s)
    --- PASS: TestApplicationBackup/applicationBackupRestoreTest (403.68s)
    --- PASS: TestApplicationBackup/applicationBackupDelBackupLocation (152.46s)
    --- PASS: TestApplicationBackup/applicationBackupMultiple (192.54s)
    --- PASS: TestApplicationBackup/preExecRuleTest (310.81s)
    --- PASS: TestApplicationBackup/postExecRuleTest (270.84s)
    --- PASS: TestApplicationBackup/preExecMissingRuleTest (170.43s)
    --- PASS: TestApplicationBackup/postExecMissingRuleTest (170.60s)
    --- PASS: TestApplicationBackup/preExecFailingRuleTest (190.50s)
    --- PASS: TestApplicationBackup/postExecFailingRuleTest (180.45s)
    --- PASS: TestApplicationBackup/labelSelector (551.46s)
    --- PASS: TestApplicationBackup/scheduleTests (1763.39s)
        --- PASS: TestApplicationBackup/scheduleTests/intervalTest (460.69s)
        --- PASS: TestApplicationBackup/scheduleTests/dailyTest (306.41s)
        --- PASS: TestApplicationBackup/scheduleTests/weeklyTest (336.37s)
        --- PASS: TestApplicationBackup/scheduleTests/monthlyTest (376.36s)
        --- PASS: TestApplicationBackup/scheduleTests/invalidPolicyTest (280.39s)


how to merge multiple reports

HI, is it support merge multiple diff reports like jacoco merge report? Because most of my project are maven project with multiple sub_project?

The tool does not support merging reports after the fact.
I think you could produce a merged report by passing in multiple coverage reports when you run diff cover.


Long imports

Importing ParallelExperiment takes more than 5 seconds on my machine. Can we do something about it?

It is particularly perplexing considering that parallel_experiment.py is small, and the imports therein are short.

I tested and doing from qiskit_experiments.framework import ParallelExperiment is about as slow as importing the entire package, maybe slightly slower. This is expected behavior since it has to first import the entire package and then delete the rest of the namespace: https://stackoverflow.com/questions/17605659/why-does-it-take-longer-to-import-a-function-from-a-module-than-the-entire-modul/17605700
Maybe the issue should be how to improve our package import speed overall instead.

@wshanks comments:

For import qiskit_experiments, the total import time is around 1.1 seconds. The time for numpy, scipy, matplotlib, scikit-learn, cvxpy, and pandas is 0.64 seconds, and the time for qiskit not counting those is another 0.21 seconds. We probably can't run an experiment without those (except cvxpy and scikit-learn are not needed for many experiments; they're 0.14 seconds), so I don't know that we can get much faster. Maybe it's possible to go from nothing to running an experiment with just qiskit and the other dependencies could only be imported during the analysis after the job is already submitted, but I think that would require a lot of discipline with how things are imported.

Further discussion contained some suggestion for lazy imports, but they were inconvenient and had their drawbacks. Therefore I'm closing the issue.


async101 & async119 now respects transform-async-generator-decorators

fixes #315
I noticed the flag wasn't documented at all in usage.rst, so added it there.
I also think it should be enabled for ASYNC119?
The flag becomes somewhat weirdly named for ASYNC101 since it will also suppress errors in sync functions. Idk if it warrants a rename, or I should just mention it in the docs, or explicitly only make it have an effect on async funcs, or something else.

hrm, I kinda wanna make the test_changelog_and_version tests be part of pre-commit. I keep forgetting to check those before pushing

hrm, I kinda wanna make the test_changelog_and_version tests be part of pre-commit. I keep forgetting to check those before pushing

wait, I just noticed we have
def update_version() -> None:
    # If we've added a new version to the changelog, update __version__ to match
    last_version = next(iter(get_releases()))
    if last_version != VERSION:
        INIT_FILE = ROOT_PATH / "flake8_async" / "__init__.py"
        subs = (f'__version__ = "{VERSION}"', f'__version__ = "{last_version}"')
        INIT_FILE.write_text(INIT_FILE.read_text().replace(*subs))

which means the test for checking changelog matching __version__ is kinda redundant (contributor docs also say you should increment __version__). It'd perhaps be safer to do assert last_version == VERSION, and if we want the convenience of replacing __version__ that should perhaps be done in the pre-commit hook.

Oh I can't even have FUTURE stuff in the changelog because tests must pass to merge. I'll def do some retooling of this at some point


gem unable to download data from https://rubygems.org/

Hello.
I've installed Ruby Installer for Windows 1.9.3-p392 and try to install gem, then I got a following error.
$ gem install bundler
ERROR:  Could not find a valid gem 'bundler' (>= 0), here is why:
          Unable to download data from https://rubygems.org/ - SSL_connect SYSCALL returned=5 errno=0 state=SSLv3 read server session ticket A (https:
//rubygems.org/latest_specs.4.8.gz)

I don't know is this a problem of Ruby Installer or rubygems :confused:
(gem 2.0.3 has a similar issue on GItHub)
Do you have any ideas to solve this problem ?
My environments are following:

Windows 7 (x64)
Ruby Installer for Windows 1.9.3-p392
gem 2.0.3

Regards,

I have the same problem.
Here's everything I get from CMD:
[code]
F:[X] SDK>gem install shoes --pre
ERROR:  Could not find a valid gem 'shoes' (>= 0), here is why:
Unable to download data from https://rubygems.org/ - SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed (https://api.rubygems.org/specs.4.8.gz)
F:[X] SDK>
[/code]

That is actually a different issue altogether.
But rubygems.org was experiencing some problems. However, It should be fixed now.

i just update gem...
1- Download [ZIP] GEM from https://rubygems.org/pages/download#formats
2- open CMD as Administrator on folder extracted from ZIP
3- run: ruby setup.rb
4- be happy


v0.15

Added feature PREBUILD_ADDITIONAL_TASKS to allow for custom tasks to be done during prebuild
aok-versions (run on login) displays iSH AOK-FS & Alpine/Debian release
Debian uptime doesnt work on iSH - fixed by a replacement uptime that always displays 0.00, 0.00, 0.00
Setup can run on chrooted iSH
Improved propagating errors to terminate the build
moved Debian/ish_replacement_bins -> FamDeb
preventing mistaken error detection if CUSTOM_FILES_TEMPLATE is undefined
aok_launcher - added network-check
Save prebuild time & add it (if applicable) when displaying total deploy time
Corrected build time to include compress step

Awesome.  Thank you!


Nuxt UI Pro License required?

Describe the change
Is it possible to use undocs without a nuxt ui pro license? I think it would be good to add some documentation around it.
(Background: I'm considering using undocs for the documentation of a few of my projects https://github.com/apollo-server-integrations/apollo-server-integration-h3, https://github.com/tobiasdiez/nuxt-graphql-server, https://github.com/tobiasdiez/storybook-vue-addon. But if I have to pay 200 Euro for the pro version, then I'll probably go with a simpler solution for the docs.)
URLs
No response
Additional information

[ ] Would you be willing to help?

Hi. thanks for your interest ❤
Undocs is currently only meant for usage in the unjs ecosystem and got a license for it. It is too early for me to promise anything on behalf of Nuxt UI Pro but it is likely it will be open/free for all open source docs once reusable.

Make sense, thanks for the clarification!


Rewrite Bitcoin overview page

Thank you for your contribution to the IC Developer Portal.
Before submitting your Pull Request, please make sure that:

[ ] You have updated the .github/CODEOWNERS file according to your changes.
[ ] You have registered new documents to /sidebars.js if any.

@jessiemongeon1 could you please take a look? Thanks!


Bracket search key error

The bracket search implementation presume that tags dis, navName and navNameFormat exist.
It is not always the case which lead to a keyError

f755c4c083b9c66a1371edbcc23c9babcdf185c7

Solved in 0.92.1


Unsupported version of Java

Good evening. I use version 1.12.2, but the plugin requires java version 16, can I somehow run it on java 11, or what should I do in this case?

That's too bad.


[ISSUE ##724]🚀Add MessageArrivingListener

Which Issue(s) This PR Fixes(Closes)

Fixes #724
Brief Description

How Did You Test This Change?

🚀Thanks for your contribution🎉. CodeRabbit(AI) will review your code first🔥


Allow multiple indicator dependencies in Snakemake

Snakemake needs some rethinking about how indicator dependencies are handled for example in cases where we have multiple input variables into the same indicator

The secondaryVariables setup provides a good model for how to do this.


Refactor cursors to inherit from BaseCursor, scroll with a Mongoid::Scroll::Base64EncodedCursor

@FabienChaynes take a look, this lets you scroll normally.
Feed::Item.desc(:position).limit(5).scroll(Mongoid::Scroll::Base64EncodedCursor) do |record, next_cursor|
   # next_cursor is of type Mongoid::Scroll::Base64EncodedCursor
end

I removed support for Mongoid 3, 4 and moped, I think it's time.

Specs passing. There's probably a more methodical way to approach writing these tests than the lots of copy-paste.

@FabienChaynes good eyes, not sure how you saw this 😅 fixed, added specs to reuse both the cursor returned and the serialized cursor for all types

Thanks for a thorough code review!


[Attention]: No longer able to maintain this project

I'm happy people are getting use out of this component, however, I have not used it in quite a while, and have not been able to give it the support it needs!
If you are interested in collaborator access or forking, please let me know.  Thanks.

It seems that there are bugs/issues arising from latest React (v15). I investigated a bit but decided it would be easier to create a new component (since it's pretty simple) without the debt of this codebase. This ended up being a better option for our use case that this tool was solving. Dropping here in case it may be relevant to anyone's project(s). https://github.com/mmw/react-password-strength
So this is an FYI that I will not be supporting react-ux-password-field at this time.

Looks great.  Thanks for the help @mmw, and good luck with the project!


Add clarity around concurrent updates

From the f2f:
Proposal: In the “Blocking Operations” section change it to say “...that mutate the same resource…” instead of “...that act on the same set of resources...”
&& creating Binding is not necessary considered mutating an Instance, it’s a Broker’s choice
&& move “Blocking Operations” out from under Async
&& change 422 in createBinding response status code table to include this concurrency stuff
Signed-off-by: Doug Davis<EMAIL_ADDRESS>

LGTM

@duglin PR title has a TYPO: conurrent should be concurrent

@jmrodri fixed!  thanks

LGTM

LGTM

just one more review needed

Not sure I count but LGTM :)

Added text about orphan mitigation per the weekly meeting.

I changed the error code from 422 to "409 Conflict" - seemed more appropriate, but what do others think?

@duglin 409 Conflict does sound more appropriate.  👍

LGTM

reviews needed

updated and ready for reviews

LGTM

LGTM

ready for next round of reviews

LGTM

The proposal defines a fixed error body. A broker can neither change the description nor add additional data that might be useful to identify why there is a conflict. Can we make this a bit more flexible?

@fmui See:  https://github.com/duglin/servicebroker/blob/6cbba3d423f3d7e5ebadd2e650f245ce531e1e2f/spec.md#broker-errors  it says: "For error responses, the following fields are valid. Others will be ignored. ".  While it would be nice if it was a bit clearer, I view that as saying the broker may include other fields (extensions) but they might be ignored by the platform.  Does that cover it?

Not really. The proposal says:
"...then the broker MUST reject the request with an HTTP 409 Conflict and the following body: ..."
This is much more restrictive than defined in the Broker Error section. It doesn't even allow to return a different description text. I don't see a reason why this error should have stricter rules than other errors.

I don't think it was meant to be more restrictive. I think an generic "error PR" to make us more consistent would be good to answer these concerns. In particular:

which fields in the error json MUST be as exactly specified or can be tweaked (e.g description)
are additional fields (extensions) allowed and how are they added? (wrapper or top-level)

and we should touch all error text to ensure consistency.

+1 to allowing for additional fields. We have already run into some issues because brokers are built on platforms that provide some fixed fields for all error responses.

@fmui can we clarify all of this in a follow-on PR? I'd prefer to keep this one more focused on just this one usecase.

I have a few concerns here.

changing the MUST from 422 to 409 is a backwards incompatible change
similar to fmui concern, this feels like a very restrictive error message, where brokers may want to include more or different details that could be helpful in resolving the issue
I don't understand the benefits of making this change.  I can see that 409 may be somewhat more correct, but do we have platforms that will perform a different behavior based on this?  As long as we are returning an error and a useful message I don't see a reason to be more prescriptive than we already are.

I reverted back to 422 and decided to add the "extensibility" text into this PR instead of creating a new one.  See what people think.

@duglin merge conflict!

rebased

This is going to give me merge conflict fun times in the async bindings PR. But LGTM anyway!

LGTM

LGTM

lgtm


feat: [cheqd] top accounts module

Description
Closes: #XXXX

jira: https://forbole.atlassian.net/browse/BDU-707

Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...

[x] included the correct type prefix in the PR title
[ ] added ! to the type prefix if API or client breaking change
[x] targeted the correct branch
[x] provided a link to the relevant issue or specification
[x] added a changelog entry to CHANGELOG.md
[ ] included comments for documenting Go code
[ ] updated the relevant documentation or specification
[x] reviewed "Files changed" and left comments if necessary
[ ] confirmed all CI checks have passed

Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...

[ ] confirmed the correct type prefix in the PR title
[ ] confirmed ! in the type prefix if API or client breaking change
[ ] confirmed all author checklist items have been addressed
[ ] reviewed API design and naming
[ ] reviewed documentation is accurate
[ ] reviewed tests and test coverage
[ ] manually tested (if applicable)

Codecov Report

:exclamation: No coverage uploaded for pull request base (chains/cheqd/mainnet@c2728e3). Click here to learn what that means.
The diff coverage is n/a.

:exclamation: Current head a8459ee differs from pull request most recent head eb016a6. Consider uploading reports for the commit eb016a6 to get more accurate results

@@                   Coverage Diff                   @@
##             chains/cheqd/mainnet     #510   +/-   ##
=======================================================
  Coverage                        ?   58.06%
=======================================================
  Files                           ?       20
  Lines                           ?     1495
  Branches                        ?        0
=======================================================
  Hits                            ?      868
  Misses                          ?      522
  Partials                        ?      105


Fix issue with URL building in custom connector

When submitting a connector, please make sure that you follow the requirements below, otherwise your PR might be rejected. We want to make you have a well-built connector, a smooth certification experience, and your users are happy :)
If this is your first time submitting to GitHub and you need some help, please sign up for this session.

[ ] I attest that the connector doesn't exist on the Power Platform today. I've verified by checking the pull requests in GitHub and by searching for the connector on the platform or in the documentation.
[x] I attest that the connector works and I verified by deploying and testing all the operations.
[x] I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
[x] I attest that I have added response schemas to my actions, unless the response schema is dynamic.
[x] I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
[x] If this is a certified connector, I confirm that apiProperties.json has a valid brand color and doesn't use an invalid brand color, #007ee5 or #ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.

If you are an Independent Publisher, you must also attest to the following to ensure a smooth publishing process:

[ ] I have named this PR after the pattern of "Connector Name (Independent Publisher)" ex: HubSpot Marketing (Independent Publisher)
[ ] Within this PR markdown file, I have pasted screenshots that show: 3 unique operations (actions/triggers) working within a Flow. This can be in one flow or part of multiple flows. For each one of those flows, I have pasted in screenshots of the Flow succeeding.
[ ] Within this PR markdown file, I have pasted in a screenshot from the Test operations section within the Custom Connector UI.
[ ] If the connector uses OAuth, I have provided detailed steps on how to create an app in the readme.md.

Hello @dox42diegoschleis,
Apologies if I am not clear in my previous message.  I mentioned about the swagger validation is failing with below errors. Please confirm, so that I will approve it.
##[error]The path template has been changed for the operation. ValuePath: operation/Dox42Call Source: NewSwagger
##[error]The location has been changed for the parameter. Existing flows will continue to send the parameter in the old location. ValuePath: operation/Dox42Call/parameter/querystring/in Source: NewSwagger
##[error]The path template has been changed for the operation. ValuePath: operation/Dox42CallPost Source: NewSwagger
##[error]The location has been changed for the parameter. Existing flows will continue to send the parameter in the old location. ValuePath: operation/Dox42CallPost/parameter/querystring/in Source: NewSwagger

Hello @vmanoharas, I understand that the swagger validation is failing.
Before proceeding, I would like some clarification on how existing flows will be affected by this change.
From my understanding, the custom connector is copied into a Power Apps Environment and therefore not connected to this connector in the GitHub repo, correct?
Existing flows seem to work with the old implementation, however there seem to have been some changes, breaking new implementations of this custom connector.

Thank you very much for @dox42diegoschleis for confirming.  I will go ahead and approve this PR. Thank you for working with us.


add new misc. resources

Please select the type of changes this PR has and add some context.
🏆 Enhancements
Added some new resources.

Thank you for the PR, @aliraza5490! Merged into master.


Enable collection of code coverage

Updated to latest 15.x release (15.8.0+ required for collecting code coverage)

Yes, it is stored in TestResults/ . Thanks for thinking of that.


Add option - boolean: infer github links

Please review: Pass-through of boolean option github or g to documentationjs, so the output is linked to github.

:+1: thanks! I'll look into whether we can just pass all options to the method, but that'll take a little longer to spec out.

Thank you :)


exampleLoader does not work with JupyterLab 2.x and above

The current version of the JupyterLab VRE customization extension  does not work with JupyterLab 2.x and above. This limits the upgradeability of the VRE JupyterLab UI.
The customization extension needs to be migrated. See also the Extension Migration Guide.

fixed in the jsonload_jl3 branch