As a user, I can find travel information

Add content or links to content (may be on other websites such as TripAdvisor) pertaining to:

Places to stay near the conference venue, or within easy accessibility
Other interesting things to do in the area
Other interesting things to do in Thailand
How to get from the airport to the conference venue

@ditsara Good idea :-)

I can work on it. Do we have a already have a place on website for it?

Not yet. I was thinking we could maybe add a separate section, to keep it separate from the main conference infomation (@olivierobert feel free to chime in). I think just some links to info should be fine.

Places to stay (Google Maps link to hotels near Pullman King Power): https://www.google.com/maps/search/hotels+near+Victory+Monument,+Thanon+Phaya+Thai,+Ratchathewi,+Bangkok/@13.7599053,100.5342982,16z/data=!4m6!2m5!5m3!5m2!1s2019-09-06!2i2!6e3

Interesting things to do in the area / in Thailand: maybe the appropriate tripadvisor page?

How to get from the hotel: I could write something up for this -- Grab, ARL, regular taxi

Fixed in #82


Add Stunnel Images

https://github.com/jboss-container-images/jboss-amqstreams-1-openshift-image/issues/8

@kyguy I think Paolo understands this much better than me ... so it might be best if he does the reviewing. Would that be ok @ppatierno?

Switched the format of the modules to mirror upstream images. Let me know what you think

:-)


[Bug]: Site always redirects

What happened?
When I build win11React with vite and serve the build dir using a nodejs script, it always redirects to https://andrewstech.me/win11react-add-test/, and i would like to host it locally rather than having it redirect.
To reproduce the behavior?
Build and put the build dir in the same dir as this nodejs script:
`const express = require('express');
const path = require('path');
const app = express();
app.use(express.static(path.join(__dirname, 'build')));
app.get('*', (req, res) => {
res.sendFile(path.join(__dirname, 'build', 'index.html'));
});
app.listen(3000, () => {
console.log('Server is listening on port 3000');
});
`
What browser are you seeing the problem on?
Chrome

This is only a temporary thing for our main site. You can disable it by removing line 6 from this file https://github.com/blueedgetechno/win11React/blob/master/public/react-pwa.js

Thank you


Difference between packed_simd and portable-simd, and which one should I use?

Hi thanks for the Rust language and the two libraries! I wonder which one should I use now? They seems to have similar features and one even links to the other.

I had the same question, and this issue helped me understand the future of these repos.


Build wasm during regular build?

Summary
How can I build just the wasm file during a regular cargo build?
Additional Details
I am not interested in building an entire npm package or running in nodejs even, so I don't really want the full wasm-pack route. I want to use paritytech/wasmi to basically interpret wasm binaries directly. I want to have some libraries that get set as imports that can be referenced from the wasm modules I'm interpretting.
Ideally I would have a sub project which is a lib and referenced via:
[dependencies]
context = { path = "context" }

And the context is just a lib similar to the add example (sans nodejs).
I would like to do a single cargo build and have it produce a wasm file which I can load from disk at runtime.
Is this possible right now? How could I modify the add example library to produce a .wasm file during cargo build?
When I build today it appears to only generate a .so file by default.

You can just do cargo build --target wasm32-unknown-unknown to generate a .wasm file (it will be in the target/wasm32-unknown-unknown/{release/debug} folder)
Since you're using a wasm interpreter, you can't use wasm-bindgen, since wasm-bindgen is designed for JS, therefore it generates JS shims.
So you'll have to create your own bindings, like this:
#[no_mangle]
pub extern "C" fn add(a: i32, b: i32) -> i32 {
    a + b
}

Or if you want to import wasm functions from the host:
extern "C" {
    fn foo(x: i32) -> i32;
}

You'll want to read these:
https://doc.rust-lang.org/std/keyword.extern.html
https://doc.rust-lang.org/book/ch19-01-unsafe-rust.html#using-extern-functions-to-call-external-code
https://doc.rust-lang.org/reference/items/external-blocks.html
https://doc.rust-lang.org/nomicon/ffi.html
Keep in mind that the Rust FFI is generally based around C, and wasm is more restrictive than C, so not everything will work.

@Pauan has you covered for executing Cargo to produce a wasm file, and currently Cargo has no capability to produce both a native binary and a wasm binary as part of the same build, but a feature could be requested on Cargo for that!

Thanks! The --target flag was the key I was missing.


chore(ci/cd): Deploy AM EE on nightly environment

fixes gravitee-io/issues#7626

Note: If this is merged we may want to have this for RiskAssessment and include the plugin.

Indeed, we will have to update the config during the RiskAssessment integration


WIP: Addressing Windows issues with get started tutorial

What's changed

Addressing major issues with Getting Started per Windows users experience per Jim's and now my walkthrough (path of least resistance; e.g., not removing scp from the tutorial, just explaining how to get Git Bash or PowerShell/Win32-OpenSSH)
Provide info re: scp options and how to get it
Add info about needing to open a port and share a drive
Updated Docker Cloud on AWS docs (already done in PR #4647 )

Related

Fixes #3078
Fixes #3648

Reviewers
@friism
Signed-off-by: Victoria Bialas<EMAIL_ADDRESS>

@JimGalasyn thanks, I've got a lot more to do yet

@friism this is getting closer to being finished, please have a look when you get a chance. I have a little more to do on the last sections, but should be close.

lgtm!

Don't forget to change the title from WIP before you commit. 👍

@mstanleyjones thanks, I would never forget such a thing! :-)

@friism @johndmulhausen @JimGalasyn  I'm merging this now w/the reviews, approvals, and several walk throughs on my own on both Mac and Linux, it goes a long way towards explaining alternatives for connecting to VMs, and fixing the x-platform/Windows stumbling blocks, and introduces docker-machine env earlier (this was originally mentioned on part 6 with regard to Docker Cloud).
What I did not do, is re-do the (asciinema)[https://asciinema.org/]. I think it's okay for now that these show docker-machine ssh and docker-machine scp as examples.  When we add in Play with Docker, we can re-do it to be more consistent with this new approach.


windows 7: resin/rpi-raspbian deprecation warning (cant build image)

Please provide us with the following information:

This issue is for a: (mark with an x)
- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Build seeed/1-temperature-sensor/modules/temperature-sensor/Dockerfile.arm32v7 (or the deps version, both reference resin/rpi-raspbian)
Build will fail due to deprecation warning from resin

Any log messages given by the failure

Sending build context to Docker daemon  14.34kB
Step 1/11 : FROM resin/rpi-raspbian:stretch
Executing 1 build trigger
---> Running in d8dbf30fcbba
standard_init_linux.go:207: exec user process caused "exec format error"
The command '/bin/sh -c cat /.resin/deprecation-warning' returned a non-zero code: 1

Expected/desired behavior

Successful build of temperature-sensor docker image

OS and Version?

Windows 7

Versions

Mention any other details that might be useful

The whole resin docker repository is deprecated: https://hub.docker.com/r/resin/rpi-raspbian/
Migrated to balenalib which also has rpi-raspbian image: https://hub.docker.com/r/balenalib/rpi-raspbian

but when running dockerfile with balenalib image as base image, the cross-build-start command fails:

Step 2/11 : RUN [ "cross-build-start" ]
---> Running in 170986dc98e2
OCI runtime create failed: container_linux.go:344: starting container process caused "exec: "cross-build-start": executable file not found in $PATH": unknown

edit: the image is successfully built (no deprecation warning stopping the build) when building on Windows 10 Pro 1809. It gets past the deprecation warning message (this stops the Docker build on Windows 7). After running the image as container on my raspberry pi, however, I run into this issue: https://github.com/Azure-Samples/azure-iot-starter-kits/issues/31

Closing this issue because it works properly on Windows 10 Pro 1809 with Docker CE.


[Issue-194][Feature] Support spark 3.2.0

What changes were proposed in this pull request?
support spark 3.2.0
Why are the changes needed?
After SPARK-36892, MapOutputTrackerWorker#getMapSizesByExecutorId has been modified to include method names and return parameter types, Java.lang.NoSuchMethodException will be thrown when the RssShuffleManager#getExpectedTasksByExecutorId method is called, The version of our production environment is 3.2.0.
Does this PR introduce any user-facing change?
No
How was this patch tested?
reused intergration-test

We need to add a "-Pspark3.2.0" pipeline.

You can add the pipeline in https://github.com/apache/incubator-uniffle/blob/master/.github/workflows/parallel.yml

Codecov Report

Merging #201 (e5ce3a3) into master (6b9f2d1) will decrease coverage by 1.37%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #201      +/-   ##
============================================
- Coverage     58.48%   57.11%   -1.38%
+ Complexity     1277     1198      -79
============================================
  Files           158      149       -9
  Lines          8463     7965     -498
  Branches        785      754      -31
============================================
- Hits           4950     4549     -401
+ Misses         3259     3173      -86
+ Partials        254      243      -11

Impacted Files
Coverage Δ

.../apache/uniffle/coordinator/CoordinatorServer.java
59.57% <0.00%> (-5.32%)
:arrow_down:

...storage/handler/impl/DataSkippableReadHandler.java
81.25% <0.00%> (-3.13%)
:arrow_down:

.../org/apache/spark/shuffle/writer/WriterBuffer.java

...k/shuffle/writer/WrappedByteArrayOutputStream.java

...pache/spark/shuffle/writer/WriteBufferManager.java

...org/apache/spark/shuffle/writer/AddBlockEvent.java

...org/apache/spark/shuffle/RssSparkShuffleUtils.java

.../java/org/apache/spark/shuffle/RssSparkConfig.java

...e/spark/shuffle/reader/RssShuffleDataIterator.java

...ava/org/apache/spark/shuffle/RssShuffleHandle.java

... and 1 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Modify the related the document at the same time.

All done, Can you help review please? @jerqi

Thank you for your patience and kindness. @jerqi


Adding Score Feature to the Snake Game #281

Fixes Issue🛠
Closes #281
Description👨💻
Score feature added to the snake game
How this has been tested✅
Tested on my local system and it works fine
Checklist✅

[] My code follows the style guidelines of this project
[] I have performed a self-review of my own code
[] I have commented my code, particularly in hard-to-understand areas
[] I have added demonstration in the form of GIF/video file
[] I am an Open Source Contributor

Screenshots/GIF📷
https://github.com/Priyanshi662/FunFusion/assets/148339919/f6fe583e-9800-4535-a87b-eb3fda262f41

@Priyanshi662 check out my PR for the issue #281

@Priyanshi662 please checkout my PR as soon as possible

@prakharsingh-74 please resolve conflicts


Issue 188/adjust styling of checkbox groups

Adjust styling of checkbox groups #188

Hang on - going to do this better

@zheileman Good to go now


.gitignore and image enhancements

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

Closes #37074

New lines at the eof

@raisedadead Committed the changes. Should I update glyphicons-halflings-regular.svg with blank-at-eof as well?


[Feature Request] CLI rewrite needs to support "pretty" log format and log level for older SDKs

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

Describe the solution you'd like
All SDKs basically expect server start-dev to be able to set --log-format to something like "pretty" and --log-level to a needed value (Go, TS, Python, .NET, Core, etc). Today we have no concept of --log-format of "pretty", just text and json, and we have no concept of --log-level for just server, we have --log-level-server which we intentionally separated because we want warn the default there.
Suggestion: Add pretty as an alias for text in --log-format, and change --log-level-server to default to --log-level if not set, and change --log-level default for just this command to warn.

Your suggestion seems fine to me. 👍

Done in #535


The request and limit parameters in Sentinel Instance cannot be modified in the configuration.

Avoid making key configurations hardcoded. Here.

The operator does not want you to create a sentinel cluster yourself, it will automatically identify the sentinel cluster you need and create it. If you need customized processing, CRD supports sentinel type CR identification

Hi, @tianshimoyi @ColinChamber
Under the condition of not wanting users to create their own sentinel clusters, do you think we need to provide a field for users to specify the replicas and resource requirements of sentinel? For instance, changing EnableSentinel to SentinelConfig.
type SentinelConfig struct{
   EnableSentinel bool
   Replicas int32
   Resources *corev1.ResourceRequirements
}

I have based the current default resource settings on the redis-operator.
https://github.com/RocksLabs/kvrocks-operator/pull/36/files#diff-a8a584490794acc39bdbcd0073aabf63d756cf54f53900751cecaf596af1a070R90
https://github.com/spotahome/redis-operator/blob/master/operator/redisfailover/service/generator.go#L505

@jiayouxujin You can create a sentinel cluster first, and specify information such as resources, so that you can customize sentinel

@tianshimoyi OK, I get it.
If there is no sentinel in the current k8s cluster and enableSentinel is true, operator will automatically create a default sentinel.


Reboot loop with reboot-before-run: True

Hi,
When I add reboot-before-run: True to my app I get stuck in a reboot loop with no console available.
Code is at https://github.com/MatthewWilkes/tildamk3-dronehunt - works fine on pyboard.py and through mpy-cross.
Matt

I have tried your code, and immediately after the code starts running the red, green and LCD backlight flash slowly in order (this is a hardfault). Is this what is happening for you? (Oddly enough though, the code runs fine on my development badge, which annoyingly is the one with the debug header soldered on)

I will check again over the weekend, but iirc, I got an alternating black and white screen. It wasn't red/green backlight flash.

I meant the red LED, green LED and backlight LED (with white screen) will flash alternately. Looks like the hardfault behaviour then.


WorkItem-Import: Revisions and attachments are created with the token owner's account

Originally posted by @omustapasa in https://github.com/solidify/jira-azuredevops-migrator/issues/443
I have recently checked-out the latest code from master.
Exporter seems to produce the correct results as per the JSON files generated.
Importer however creates all related history and attachments with the same account the application runner uses (token owner in my case)
I am not sure if this is caused by a change on ADO API or it is somewhat a side effect of having some preview features on/off and/or used access token for importer execution not having certain rights.
It would be great to have it resolved as my migration is quite dependent on this at this stage.
I would like to know if this is a limitation as per ADO API or something else.

@omustapasa, does this problem happen for comments as well? Or are comments assigned to the correct user?

Needs to be fixed ahead of the 3.0 release

@omustapasa, does this problem happen for comments as well? Or are comments assigned to the correct user?

It happens for comments as well.
Regardless where you look at the comments and other history (Details at the bottom of the page or history tab) token owner is the owner of all actions.
If this is a change in the Azure Boards API I would suggest adding the original comment owner in the comments section at least as in : " says: " format.

@omustapasa OK! noted.
It's most likely a failure in the code somewhere, as this has worked as expected before. If you're in a hurry, you can grab the latest stable release from here: https://github.com/solidify/jira-azuredevops-migrator/releases/tag/v2.3.117

@omustapasa I have been unable to reproduce the issue, when I run the a fresh build of master, everything seems fine and the history entries and comments are created by the correct author.
Have you checked the export log? Does it complain that there are missing user mappings? It might be that if it cannot resolve the author of the change/comment, it will default to the author of the issue, in this case the token owner.
Relabeling this as a support issue

Screenshot for reference. Here you can see that the original authors are added. The only mention of me is adding/deleting links and creating the issue. These operations must be made by the token owner.

Hello @Alexander-Hjelm,
I can tell you not all users from JIRA are available on ADO and user.txt as we had coworkers who left the organization.
For their accounts I used the default account option on the user.txt as in
<EMAIL_ADDRESS>However I still see my personal account as the comment and attachment owner where all the user stories, epics are have their own respective owners assigned.
P.S: Not all users are assigned to the available team for the project on ADO however since all other assignations work as expected I do not see this being a problem as per same users are the ones making the comments which is not assigned correctly.
Sadly for my case the situation is not what you are presenting. Maybe there's an issue with my user.txt and its location.
Currently my users.txt is located in the same folder as where the jira workitems are being exported and I am using the same folder for the import (I am using the same config for the importer copy/paste)

It might be that if it cannot resolve the author of the change/comment, it will default to the author of the issue, in this case the token owner

It might be the case as I have quite a lot of users removed or inactive on JIRA but I can not reason why the existing users are present as the "Assigned To'' but not in the comments section at all.

Is the users.txt file case sensitive for email accounts?
Does it have to be present somewhere else for the importer to read for comments?
Does not the default mapping in users.txt work for non existent users for comments? I could simply run the script with that robotic user anyways but it is interesting that it defaults to the token owner rather than the default which is set in the users.txt

Not sure how I can debug this and move forward, I am losing the whole meaning of my data without the comments and its not good.
For reference here is my config:
{   "source-project": "GOT",   "target-project": "TESTPROJECT",   "query": "project = 'GOT' AND Sprint='Sprint 62' ORDER BY created DESC",   "using-jira-cloud": true,   "workspace": "C:\\Temp\\JiraExport\\",   "epic-link-field": "Epic Link",   "sprint-field": "Sprint",   "download-options": 7,   "batch-size": 20,   "log-level": "Info",   "attachment-folder": "Attachments",   "user-mapping-file": "users.txt",   "base-area-path": "Gotham",   "base-iteration-path": "",   "ignore-failed-links": true,   "process-template": "Scrum",   "link-map": {     "link": [       {         "source": "Epic",         "target": "System.LinkTypes.Hierarchy-Reverse"       }     ]   },   "type-map": {     "type": [       {         "source": "Epic",         "target": "Feature"       },       {         "source": "Story - Development",         "target": "Product Backlog Item"       },       {         "source": "Bug",         "target": "Bug"       },       {         "source": "Task - Development",         "target": "Task"       },       {         "source": "Sub-task Development",         "target": "Task"       }     ]   },   "field-map": {     "field": [       {         "source": "Sprint",         "source-type": "name",         "target": "System.IterationPath",         "mapper": "MapSprint"       },       {         "source": "summary",         "target": "System.Title",         "mapper": "MapTitle"       },       {         "source": "assignee",         "target": "System.AssignedTo",         "mapper": "MapUser"       },       {         "source": "description",         "target": "System.Description",         "mapper": "MapRendered"       },       {         "source": "priority",         "target": "Microsoft.VSTS.Common.Priority",         "mapping": {           "values": [             {               "source": "1",               "target": "1"             },             {               "source": "2",               "target": "2"             },             {               "source": "3",               "target": "3"             },             {               "source": "4",               "target": "4"             },             {               "source": "5",               "target": "5"             },             {               "source" : "High",               "target": "1"             },             {               "source" : "Medium",               "target": "2"             },             {               "source" : "Low",               "target": "3"             }           ]         }       },       {         "source": "labels",         "target": "System.Tags",         "mapper": "MapTags"       },       **{         "source": "comment",         "target": "System.History",         "mapper": "MapRendered"       },**       {         "source": "status",         "target": "System.State",         "mapping": {           "values": [             {               "source": "Candidate",               "target": "Candidate"             },             {               "source": "Reopened",               "target": "Reopened"             },             {               "source": "Development",               "target": "Development"             },             {               "source": "Documentation",               "target": "Documentation"             }, 			      {               "source": "Under Investigation",               "target": "Under Investigation"             },             {               "source": "Functional specification",               "target": "Functional Specification"             },             {               "source": "Technical specification",               "target": "Technical Specification"             },             {               "source": "UI/UX design",               "target": "UI/UX Design"             },             {               "source": "Waiting for client approval",               "target": "Waiting for Client Approval"             },             {               "source": "Quality Assurance",               "target": "Quality Assurance"             },             {               "source": "Ready to Go",               "target": "Ready to Go"             },             {               "source": "Internal Review",               "target": "Internal Review"             },             {               "source": "Backlog",               "target": "Backlog"             },             {               "source": "Waiting for Internal",               "target": "Waiting for Internal"             },             {               "source": "Waiting for external",               "target": "Waiting for External"             },             {               "source": "In Progress",               "target": "In Progress"             },             {               "source": "Pending Production Release",               "target": "Pending Production Release"             },             {               "source": "Done",               "target": "Done"             },             {               "source": "Canceled",               "target": "Cancelled"             }           ]         }       },       {         "source": "Story points remaining",         "source-type": "name",         "target": "Microsoft.VSTS.Scheduling.StoryPoints"       },       {         "source": "Story point estimate",         "source-type": "name",         "target": "Microsoft.VSTS.Scheduling.Effort"       },       {         "source": "timeestimate",         "target": "Microsoft.VSTS.Scheduling.RemainingWork",         "mapper": "MapRemainingWork"       },       {         "source": "Description",         "target": "Microsoft.VSTS.TCM.ReproSteps",         "for": "Bug"       },       {         "source": "environment",         "source-type": "name",         "target": "Microsoft.VSTS.TCM.SystemInfo"       },       {         "source": "Reporter",         "target": "Custom.Reporter",         "mapper": "MapUser"       },       {         "source": "Responsible AM",         "target": "Custom.ResponsibleAM",         "mapper": "MapUser"       },       {         "source": "Account",         "target": "Custom.Account",         "mapper": "MapArray"       },       {         "source": "Product Category",         "target": "Custom.ProductCategory",         "mapper": "MapArray"       },       {         "source": "Component",         "target": "Custom.Component",         "mapper": "MapArray"       },       {         "source": "Customer(s)",         "target": "Custom.Customers",         "mapper": "MapArray"       },       {         "source": "Due Date",         "source-type": "dateTime",         "target": "Microsoft.VSTS.Scheduling.TargetDate"       }     ]   } }
and here is a look at the users.txt
<some<EMAIL_ADDRESS><EMAIL_ADDRESS>

I can tell you not all users from JIRA are available on ADO and user.txt as we had coworkers who left the organization.
For their accounts I used the default account option on the user.txt as in
<EMAIL_ADDRESS>
In this case it will not resolve the mapping properly, unless you can a user explicitly with the email<EMAIL_ADDRESS>You can try omitting the default (asterisk *) line in your user mapping. You should get the jira ids instead on the ADO side , and maybe that will help you debug.

Sadly for my case the situation is not what you are presenting. Maybe there's an issue with my user.txt and its location.
Currently my users.txt is located in the same folder as where the jira workitems are being exported and I am using the same folder for the import (I am using the same config for the importer copy/paste)

The user mapping file should be inside the migration workspace (for you: C:\Temp\JiraExport\). Alternatively you can address it globally in the config.json. Try something like C:\Temp\JiraExport\users.txt

Is the users.txt file case sensitive for email accounts?

Yes

Does it have to be present somewhere else for the importer to read for comments?

Nope, should only be in the config

Does not the default mapping in users.txt work for non existent users for comments? I could simply run the script with that robotic user anyways but it is interesting that it defaults to the token owner rather than the default which is set in the users.txt

Not sure about comments tbh, but some for operations (like creating new workitems) you cannot control who shows up in the work item history, it will be set to whoever ran the command.
Can you upload your migration logs here? You can drag-drop the txt-files into the issue to attach a file. Both the import and exports logs, preferably.

Hello again @Alexander-Hjelm,
I have anonymized the files and here they are.
Most of the errors are due to inactive user accounts and mappings not being found as a result of them not being available on ADO but a default.
wi-import-log-220927-145018.txt
jira-export-log-220927-125646.txt

I see that many of your user's have their email hidden, so the migrator will use the jira IDs instead of the emails. Try to map the user ID's instead (see the documentation on the config file or FAQ for examples), and see if that makes it better?
Also, which version of the jira migrator is this? I see a lot of this issue, but this was fixed on the master branch some time ago:
[E][14:52:55] The identity value 'Microsoft.VisualStudio.Services.WebApi.IdentityRef' for field 'Assigned To' is an unknown identity.

@Alexander-Hjelm
My users.txt file only uses JIRA user IDs and AzureDevops email accounts.
Do you mean that I should use ADO accountId instead of ADO emails?
I am using the latest from master a week or two ago I believe.
It was suggested to use the latest from master instead of the release version due to a null reference exception.
I can get the latest from master and give it another go but need to understand how to fix the issue with comment owners.
I will try see if I can write a blog post of a step by step after I finish my migration ;)

@Alexander-Hjelm
I can confirm with the latest master of today, comments are shown as per their respective owner!
You can close this support ticket now I guess.
I am receiving exceptions regarding TF401326: Invalid field status 'ReadOnly' for field 'System.BoardColumn'.
Is it something that you have ever faced before?

OK! Happy to hear :)

I am receiving exceptions regarding TF401326: Invalid field status 'ReadOnly' for field 'System.BoardColumn'.
Is it something that you have ever faced before?

Nope, not for the jira-ado migrator specifically, but in other contexts yes. You aren't explicitly mapping System.BoardColumn though, so it shouldn't be an issue... It probably has something to do with the setup of your ADO boards.
No idea at the moment, but we'll have to keep an eye on it. If the issue causes you problems then feel free to open a new issue with a description :)


Handle invalid URL input from UI

When a UI is incorrect, it's best to display an error page to notify users about the situation.

https://github.com/ZeroX-DG/moon/pull/108


Error installing pinpoint using pip

Its seems like you have some hidden or special character formatting on some of your Icon files like "barcodes/5x5_10bit/Icon\r" which is causing problems under installation.
Console output:
C:\Users\user>pip install https://github.com/jgraving/pinpoint/archive/v0.0.1-alpha.zip
Collecting https://github.com/jgraving/pinpoint/archive/v0.0.1-alpha.zip
Downloading https://github.com/jgraving/pinpoint/archive/v0.0.1-alpha.zip \ 1.3MB 3.2MB/s
ERROR: Could not install packages due to an EnvironmentError: [Errno 22] Invalid argument: 'C:\Users\user\AppData\Local\Temp\pip-req-build-sru32ebf\barcodes/5x5_10bit/Icon\r

These files are also empty and could possibly be ignored + removed?


[Please read the message below] I have not seen an example of working with an external server

I love working with python, so I chose fastapi (backend server) as my server. Does it make sense to use solidstart then? In this case, is it better to use solid js?

It depends what your goal is by backend. If you mean you want to use Python to render web pages then I'd probably go with just SolidJS I'm not sure Start offers much here. SolidStart assumes that the backend runs a bit of javascript (or is static) for serving pages. Truthfully, you could make a site using Start with ssr: false but it will render a static index.html page and require no JS on the server.
If you mean a backend that serves data and APIs then Start could be used a separate JS web server in tandem.


Provided checkpoint incompatible with provided dataset

I have one a small problem with your provided checkpoints.
I downloaded the 3DSSG dataset from here:  https://campar.in.tum.de/public_datasets/3DSSG/3DSSG.zip including the classes.txt which has 528 classes.
I downloaded the checkpoints from here:  https://drive.google.com/drive/folders/1RbNUpHLQiY1zskd0buAgvl-yFwnD9N8M?usp=sharing
When I try to evaluate the model using:
python scripts/evaluate_vaegan.py --dataset_3RScan ../3RScan_v2/data/ --exp ./experiments/final_checkpoints/shared --with_points False --with_feats True --epoch 100 --path2atlas ./experiments/atlasnet/model_70.pth --evaluate_diversity False

I get the following error:
RuntimeError: Error(s) in loading state_dict for Sg2ScVAEModel:
        size mismatch for obj_embeddings_ec_box.weight: copying a param with shape torch.Size([162, 128]) from checkpoint, the shape in current model is torch.Size([530, 128]).
        size mismatch for obj_embeddings_ec_shape.weight: copying a param with shape torch.Size([162, 128]) from checkpoint, the shape in current model is torch.Size([530, 128]).
        size mismatch for pred_embeddings_ec_box.weight: copying a param with shape torch.Size([27, 256]) from checkpoint, the shape in current model is torch.Size([41, 256]).
        size mismatch for pred_embeddings_ec_shape.weight: copying a param with shape torch.Size([27, 256]) from checkpoint, the shape in current model is torch.Size([41, 256]).
        size mismatch for obj_embeddings_dc_box.weight: copying a param with shape torch.Size([162, 256]) from checkpoint, the shape in current model is torch.Size([530, 256]).
        size mismatch for obj_embeddings_dc_man.weight: copying a param with shape torch.Size([162, 256]) from checkpoint, the shape in current model is torch.Size([530, 256]).
        size mismatch for obj_embeddings_dc_shape.weight: copying a param with shape torch.Size([162, 256]) from checkpoint, the shape in current model is torch.Size([530, 256]).
        size mismatch for pred_embeddings_dc_box.weight: copying a param with shape torch.Size([27, 512]) from checkpoint, the shape in current model is torch.Size([41, 512]).
        size mismatch for pred_embeddings_dc_shape.weight: copying a param with shape torch.Size([27, 512]) from checkpoint, the shape in current model is torch.Size([41, 512]).
        size mismatch for pred_embeddings_dc.weight: copying a param with shape torch.Size([27, 256]) from checkpoint, the shape in current model is torch.Size([41, 256]).
        size mismatch for pred_embeddings_man_dc.weight: copying a param with shape torch.Size([27, 768]) from checkpoint, the shape in current model is torch.Size([41, 768]).

I think this error is generated because self.obj_embeddings_ec_box = nn.Embedding(num_objs + 1, obj_embedding_dim) in Sg2ScVAEModel in VAEGAN_SHARED.py takes the number of classes as the number of input features. And the number of classes is defined by the length of vocab['object_idx_to_name'] which is loaded from the classes.txt which is 528 classes + the first row scene. This similar for the relationships and self.pred_embeddings_ec_box = nn.Embedding(num_preds, 2 * embedding_dim).
Seams like you trained only with 161 classes and 27 relationships. Could you provide me with the correct classes.txt file and relationships.json to replicate your results?

Hi there, thanks for pointing this out. The classes.txt and relationships.txt files for the subset of classes that we train with, can be found here:  https://campar.in.tum.de/public_datasets/3DSSG/3DSSG_subset.zip


Fix ST2_CHANNEL description.

Fix description and clarify meaning of ST2_CHANNEL

Since ST2_CHANNEL=hubot by default, can we say that it's optional in README?
In running the bot command there is ST2_CHANNEL=mychannel
ST2_AUTH_USERNAME=testu \
ST2_AUTH_PASSWORD=testp \
HUBOT_SLACK_TOKEN=token \
# not needed to set up in most of the cases
ST2_CHANNEL=mychannel \
PORT=8181 \
bin/hubot --name "st2-bot" -a slack --alias !

Since ST2_CHANNEL=hubot by default, can we say that it's optional in README?

yes. Will add that clarification. I should really not be making any code changes this early in the morning :)


Add restart options to reload environment

After auto-reload as been removed, it is more difficult to debug when making regular changes. Start task does not recreate Odoo container, so no changes are reflected.
This ensures Odoo is recreated after every start command.
It also adds a VSCode task and button to easily restart Odoo and the proxy.
It would be nice to do it automatically when you press the "Restart" button in the VSCode debugger, but AFAICS that only restarts the "Attach" configurations, which will always find the debugger already running, leaving no option but to "Disconnect" and launch again.
If you press "Restart Odoo", the debugging session is also disconnected and needs to be lauched again.

@Yajo tests are failing due to some other problem.
Seems like the set-env option in GH Actions is not deprecated anymore, it is disabled :sweat_smile:


WebRTC in iOS 14.3 is not working

[x] I have read the README
[x] I have already searched for the same problem
[x] I have read and done the setup for Android: IMPORTANT Note for Android and iOS and IMPORTANT Note for Android
[x] I have read and done the setup for iOS: IMPORTANT Note for Android and iOS and IMPORTANT Note for iOS
[x] I have ran the sample app and it does not work there

Environment

Technology
Version

Flutter version
1.22.5 stable channel

Plugin version
4.0.0+4

Android version

iOS version
14.3

Xcode version
12.3

Device information:
Description
Expected behavior:
Create the call as it is doing in https://webrtc.github.io/test-pages/src/iframe-apprtc/ and the app is perfectly working in android as expected.
Current behavior:
But the web view is saying the unable to get access of user media and unable to create RTC peer connection.
Steps to reproduce

InAppWebView(
                initialUrl: callUrl,
                initialOptions: InAppWebViewGroupOptions(
                  crossPlatform: InAppWebViewOptions(
                      mediaPlaybackRequiresUserGesture: false,
                      debuggingEnabled: true,
                      clearCache: true,
                      javaScriptEnabled: true,
                      preferredContentMode: UserPreferredContentMode.MOBILE
                  ),
                ),
                onWebViewCreated: (InAppWebViewController controller) {
                  //web view created
                },
                androidOnPermissionRequest: (InAppWebViewController controller, String origin, List<String> resources) async {
                  print('resource list : ${resources.toString()}'); // allready allowed the camera and microphone permission
                  return PermissionRequestResponse(resources: resources, action: PermissionRequestResponseAction.GRANT);
                }
            )

Please see my comment here on how to setup WebRTC on iOS 14.3+ https://github.com/pichillilorenzo/flutter_inappwebview/issues/200#issuecomment-772393262


BUG-115518. Add revised infra, ds and edw blueprints

Shared services and attached clusters cannot be launched via the UI yet. Thought the first part of the cloud storage changes would be enough, but that wasn't the case.
Template for this: https://github.com/hortonworks/dp-demo-utils/blob/master/cumulus-poc/templates/template_infra_krb.json
@doktoric  - could you please review / merge.
These are blueprints are from the working set at:  https://github.com/hortonworks/dp-demo-utils/blob/master/cumulus-poc/blueprints
Abandoning the old PR at https://github.com/hortonworks/cloudbreak/pull/4270

@sidseth I think we should not separate attached vs standalone blueprint that properties should be part of the blueprint generation?
@akanto @keyki any thoughts?

In terms of separated 'attached' and 'standalone' blueprints - the two blueprints have different components. Standalone typically has a few additional components like YARN ATS as compared to the attached blueprint.
My understanding was that it's relatively simple to have two different blueprints, and maybe select the ones which show up based on whether they're configured to be standalone or attached or BOTH.
@doktoric - will need guidance from you on how to proceed here. It's more than config properties which change between the two blueprints.

Re-purposing this again. Have removed the standalone blueprints from the PR. Those can be added back after we figure out Richard's comment about single blueprints.
@lajosrodek  - have addressed your comments in the https://github.com/hortonworks/dp-demo-utils/tree/master/cumulus-poc repo.

Updated again, after a conversation with @doktoric . Back to the original intent of adding the infra blueprint to cloudbreak. Will work on adding the workload blueprints separately.


systemd

in system-setup file
for detect DM, dm_detect():
systemctl cat display-manager.service | awk -F'/' '/^Exec/ {print $NF}'

or use instead of status : show
systemctl show sddm | grep "State=enabled"

in initmenu file, config_editor()
is very bab to edit this files ! show them yes, but do not use sudo. For change/edit systemd configurations use sub-folders for overwrite
journald.conf.d/*.conf
logind.conf.d/*.conf
coredump.conf.d/*.conf
system.conf.d/*.conf

other :
in this line https://github.com/Chrysostomus/bmenu/blob/master/bin/system-setup#L247  edit slim for config sddm ?

Thanks for the ideas!
Could you elaborate your idea about using .d subfolders?

man journald.conf.d

can install configuration snippets in  /usr/lib/systemd/*.conf.d/.

is the same as /etc/sysctl.d/

for don't have .pacnew use systemd/*.conf.d/ directory
if user change original file .conf ,  this change may not be used if it is rewritten in the subdirectory conf.d/

I do not see too how to handle this for a user edit, but it is possible to list files in /XXX.conf.d/. And display a text saying to make these edits in this directory.

Implemented suggestions.


Develop

Coverage increased (+0.02%) to 86.395% when pulling 0d0745e381487eee601833bb99b7ae83c275939c on develop into 1f128043d56123aa4741121c3ebf986b849c7143 on qa.

Coverage decreased (-0.04%) to 86.334% when pulling 7d6b1c3ba6272374800d2318ab2a08586f84410b on develop into 1f128043d56123aa4741121c3ebf986b849c7143 on qa.


Correction of a NullReferenceException when hovering a MenuButton

When a color was not implicitly specified (Colors defined by themes, so not the Custom menu shown in the example)
Fixes #5

Added animation of Chevron when expanding/collapsing menus


input type="number" is valid when a non numeric value is entered in IE 11

When entering text or a combination of text and numbers, form.number.$valid" does not always validate to false.
Examples:
"ddd" validates to true (not OK)
"ddd3" validates to true (not OK)
"3ddd" validates to false
"33" validates to true
When using the required attribute, it works as expected.
Tested OK in Chrome and Firefox 28.0
Plnkr: http://plnkr.co/edit/uqOkCPxNYQWg8xog1IKi?p=preview
Looks like it is a similar issue to #2144

Tracked in https://github.com/angular/angular.js/issues/10981 with more info


Add support for Errors FrozenInvocation

The original changes to LimitedSeverityErrorContainer did not include support for the Errors function call. This change adds support for Errors with a new FrozenInvocation.

:heavy_check_mark: No Binary Compatibility issues for Microsoft.PowerFx.Connectors.dll
:heavy_check_mark: No Binary Compatibility issues for Microsoft.PowerFx.Core.dll
:heavy_check_mark: No Binary Compatibility issues for Microsoft.PowerFx.Interpreter.dll
:heavy_check_mark: No Binary Compatibility issues for Microsoft.PowerFx.LanguageServerProtocol.dll
:heavy_check_mark: No Binary Compatibility issues for Microsoft.PowerFx.Transport.Attributes.dll

:heavy_check_mark: No Binary Compatibility issues for Microsoft.PowerFx.Connectors.dll
:heavy_check_mark: No Binary Compatibility issues for Microsoft.PowerFx.Core.dll
:heavy_check_mark: No Binary Compatibility issues for Microsoft.PowerFx.Interpreter.dll
:heavy_check_mark: No Binary Compatibility issues for Microsoft.PowerFx.LanguageServerProtocol.dll
:heavy_check_mark: No Binary Compatibility issues for Microsoft.PowerFx.Transport.Attributes.dll


Nested form fields?

type address = {
  line1: string,
  line2: option<string>,
  zip: int,
}

module FormFields = %lenses(
  type state = {
    name: string,
    email: string,
    address: address,
  }
)

Is it possible for lenses to support nested records? It doesn't seem like it's possible to make it work with reform:
<input
  className="input"
  value={form.values.address.line2->Belt_Option.getWithDefault("")}
  onChange={ReForm.Helpers.handleChange(form.handleChange(FormFields.Address))}
  type_="text"
/>

Is this even a valid way to think about the use case? Should all form fields be top-level by design? Any guidance or feedback appreciated.

unfortunately it's not possible currently and we haven't thought of a good way to make it
buuut what we've been doing for is to treat nested data as nested forms, so we create a new "ReForm instance" for every
module AddressState = %lenses(
type state = {
  line1: string,
  line2: option<string>,
  zip: int,
}
)

module FormFields = %lenses(
  type state = {
    name: string,
    email: string,
    address: AddressState.state,
  }
)

Thanks for the suggestion, makes sense.

Can we close? @fakenickels


Deploy on Node 18

:clipboard: Description
From #9292
We are currently deploying on Node 16, which will reach EOL and stop getting security patches in ~2 months on 11 Sep 2023
https://nodejs.org/en/blog/announcements/nodejs16-eol
Node 18 will get patches for another ~2 years
The current LTS release is Node 20.
I'm going to suggest we:

~Merge this, update the branch protection rules (to account for the changed workflow names) and continue to run the tests on Node 16/18~
Continue to deploy on Node 16 in the immediate term
Start running on Node 18 in local dev
Switch the docker image over to Node 18 some time in the next few weeks
Try running the tests on Node 20 once we're prod is happy on Node 18

@SnoozeThis wait until July 16 2023

(https://snoozeth.is/StSfHlZUDFI) I will wait until Sun, 16 Jul 2023 00:00:00 UTC and then add a comment.

Resolved.


IP4 Failure on BB AI After Update Per bbb.io/update (bad route)

Describe the bug
After updating /opt/scripts, any internet comms fail for ipv4 addresses when connected to home wifi. Not sure about ethernet.
This is because usb0 is set as the default gateway (per ip route), apparently it's because of stray configuration leftover in /etc/network/interfaces.
(deleting this entry in ip route causes kernel to correctly set a sensible default- in my case, wlan0)
Describe which image you are running (example: bone-debian-10.2-iot-armhf-2020-02-03-4gb.img.xz)
The one that came with the board from the supplier (digikey?). Can pull dogtag/ID later.
Describe your hardware
BB AI.
Describe any Capes Installed
Please run this built-in script
sudo /opt/scripts/tools/version.sh
I don't have access as the moment but I can update this posting later if necessary.
To Reproduce
Steps to reproduce the behavior:

Get a fresh board.
Connect it to your home wifi (or maybe it wont work on ethernet either?)
Follow the instructions on bbb.ai/update
It will fail after updating /opt/scripts and updating kernel (maybe with a restart?) and you shouldn't be able to update cloud9 scripts (assuming that github is stil ipv4 by the time you try this).

Expected behavior
Screenshots
Additional context

Here's a paste demonstrating the same problem if you are trying to use ethernet:
with usb0 stuff in /etc/network/interfaces:
default via <IP_ADDRESS> dev usb0 onlink linkdown
<IP_ADDRESS> via <IP_ADDRESS> dev eth0
<IP_ADDRESS>/24 dev usb1 proto kernel scope link src <IP_ADDRESS> linkdown
<IP_ADDRESS>/30 dev usb0 proto kernel scope link src <IP_ADDRESS> linkdown
<IP_ADDRESS>/24 dev eth0 proto kernel scope link src <IP_ADDRESS>
<IP_ADDRESS> dev eth0 scope link
<IP_ADDRESS> via <IP_ADDRESS> dev eth0

after removing usb0 stuff from /etc/network/interfaces and reboot:
default via <IP_ADDRESS> dev eth0
<IP_ADDRESS> via <IP_ADDRESS> dev eth0
<IP_ADDRESS>/24 dev usb1 proto kernel scope link src <IP_ADDRESS> linkdown
<IP_ADDRESS>/24 dev usb0 proto kernel scope link src <IP_ADDRESS> linkdown
<IP_ADDRESS>/24 dev eth0 proto kernel scope link src <IP_ADDRESS>
<IP_ADDRESS> dev eth0 scope link
<IP_ADDRESS> via <IP_ADDRESS> dev eth0


user/crgarcia12/task is omitting user settings without warning

Task name:
Description:
If the user specifies projects: to be published, but omitted to set PublishWebProjects:false. The task will silently build the first project that it finds instead of the explicitly specified projects. For example:
- task: DotNetCoreCLI@2
  inputs:
    command: publish
    projects: myProject.csproj

That task will silently omit the projects input, instead, it will search for all projects in the repo. To get only the specified project to be published, one has to write:
- task: DotNetCoreCLI@2
  inputs:
    command: publish
    projects: myProject.csproj
    publishWebProjects : false

I think the behavior should be different, and if the user specifies projects, that should have precedence over publishWebProjects, but that could have backwards compatibility issues, so instead I decided to propose a warning that alerts the user of the missing setting
Documentation changes required: (Y/N) N
Added unit tests: (Y/N) N
Attached related issue: (Y/N) https://github.com/microsoft/azure-pipelines-tasks/issues/15339
Checklist:

[ ] Task version was bumped - please check instruction how to do it
[ X ] Checked that applied changes work as expected

@anatolybolshakov

@rvairavelu @rohit-batra could you please take a look?


Fix UB/unsoundness in slice_to_long

There are two problems with the previous impl:

It assumes the layout of slices. The layout of slices is not guaranteed, and may change at any time.

It assumes that the pointer being read from is correctly aligned for reads of a u64. This is not true in general, and not true in the tests (this can be observed with cargo miri test). The usual algorithm is to do smaller reads until an alignment boundary is reached, but just calling read_unaligned is simpler and unlikely to be much slower on platforms like x86_64.

Thanks for the effort!
However I replaced that code with a safe version in https://github.com/badboy/crc64-rs/commit/56537c58e344a11a2a4dbfa344df650209fc727c


Version 0.4.x of Hodler PRO is marked as 0.2 like the last update i.e. no version change

New version of Hodler OS is marked like the old version HODLEROS 0.2
Proper name should have template: Hodler OS vx.y.z for example: Hodler OS v4.3.1

Included in the current version of the updater


Fails with FOC/Crud Plugin

I'm using the FOC/Crud plugin and would like to use this as well but it seems to conflict. Is there something I can do to make this work?
2016-01-23 05:02:46 Error: [Cake\Network\Exception\NotFoundException] Not found
Request URL: /en/users/view/1
Stack Trace:
#0 /home/vagrant/public/cakebooks/vendor/friendsofcake/crud/src/Traits/FindMethodTrait.php(50): Crud\Action\ViewAction->_notFound('1', Object(Crud\Event\Subject))
#1 /home/vagrant/public/cakebooks/vendor/friendsofcake/crud/src/Action/viewAction.php(53): Crud\Action\ViewAction->_findRecord('1', Object(Crud\Event\Subject))
#2 [internal function]: Crud\Action\ViewAction->_handle('1')
#3 /home/vagrant/public/cakebooks/vendor/friendsofcake/crud/src/Action/BaseAction.php(69): call_user_func_array(Array, Array)
#4 /home/vagrant/public/cakebooks/vendor/friendsofcake/crud/src/Controller/Component/CrudComponent.php(228): Crud\Action\BaseAction->handle(Array)
#5 /home/vagrant/public/cakebooks/src/Controller/UsersController.php(133): Crud\Controller\Component\CrudComponent->execute()
#6 [internal function]: App\Controller\UsersController->view('1')
#7 /home/vagrant/public/cakebooks/vendor/friendsofcake/crud/src/Controller/ControllerTrait.php(51): call_user_func_array(Array, Array)
#8 /home/vagrant/public/cakebooks/vendor/cakephp/cakephp/src/Routing/Dispatcher.php(114): App\Controller\AppController->invokeAction()
#9 /home/vagrant/public/cakebooks/vendor/cakephp/cakephp/src/Routing/Dispatcher.php(87): Cake\Routing\Dispatcher->_invoke(Object(App\Controller\UsersController))
#10 /home/vagrant/public/cakebooks/webroot/index.php(36): Cake\Routing\Dispatcher->dispatch(Object(Cake\Network\Request), Object(Cake\Network\Response))
#11 {main}

I guess this is more a CRUD issue but I thought you might have some ideas.

You need to set the findMethod config for view action to obfuscate.

@bravo-kernel Would be great if you could help updating the docs for using the plugin with CRUD :)

Not sure if this is what you mean? I set the findMethod in my view action to the following
$this->Crud->action()->findMethod('obfuscate');

but I get
Unknown finder method "obfuscate"

So it would seem that I have to create my own findMethod as well?

    public function index()
    {
        $this->Crud->action()->config('findMethod', 'obfuscated');
        .....
        return $this->Crud->execute();
    }

    public function view()
    {
        $this->Crud->action()->config('findMethod', 'obfuscated');
        .....
        return $this->Crud->execute();
    }

Updated and tested the code above, should work

@justinatack You need to load the Obfuscate behavior for your table.

For historic purposes... @justinatack missed the trailing d in obfuscated in his example. Should be (and will also work):
$this->Crud->action()->findMethod('obfuscated');

Ah, I mistyped the name in my initial comment.

@justinatack can this issue be closed?

Yeah you can close it. I found it did improve things a little with my view, add and edit views but I was still having issues with my index view and form submissions, I think it's related to something I have done. I have put this issue aside for now as I don't have time to address it but I'll look at it again in the near future. Thanks for all the help.


Dynamic library broken under Windows : unresolved external symbol simdjson::json_parse_ptr

Hi! I am tring to update vcpkg's simdjson to v0.2.0. And it seems that dynamic library support on Windows with MSVC is broken:
json2json.cpp.obj : error LNK2001: unresolved external symbol "int (__cdecl* simdjson::json_parse_ptr)(unsigned char const *,unsigned __int64,class simdjson::ParsedJson &,bool)" (?json_parse_ptr@simdjson@@3P6AHPEBE_KAEAVParsedJson@1@_N@ZEA)
tools\json2json.exe : fatal error LNK1120: 1 unresolved externals
...
pointercheck.cpp.obj : error LNK2001: unresolved external symbol "int (__cdecl* simdjson::json_parse_ptr)(unsigned char const *,unsigned __int64,class simdjson::ParsedJson &,bool)" (?json_parse_ptr@simdjson@@3P6AHPEBE_KAEAVParsedJson@1@_N@ZEA)
tests\pointercheck.exe : fatal error LNK1120: 1 unresolved externals
...
basictests.cpp.obj : error LNK2001: unresolved external symbol "int (__cdecl* simdjson::json_parse_ptr)(unsigned char const *,unsigned __int64,class simdjson::ParsedJson &,bool)" (?json_parse_ptr@simdjson@@3P6AHPEBE_KAEAVParsedJson@1@_N@ZEA)
tests\basictests.exe : fatal error LNK1120: 1 unresolved externals

In simdjson's CMakeLists.txt, WINDOWS_EXPORT_ALL_SYMBOLS is used to automatically export symbols found in the dll:
https://github.com/lemire/simdjson/blob/349068dcda596261dba68a4238bbbc0af4c66ef3/src/CMakeLists.txt#L66
Unfortunately, the document of WINDOWS_EXPORT_ALL_SYMBOLS also says that:

For global data symbols, __declspec(dllimport) must still be used when compiling against the code in the .dll. All other function symbols will be automatically exported and imported by callers.

json_parse_ptr is defined as a data symbol here:
https://github.com/lemire/simdjson/blob/349068dcda596261dba68a4238bbbc0af4c66ef3/include/simdjson/jsonparser.h#L30
It is a data symbol, so that is why there are so many unresolved externals errors.
CMAKE_WINDOWS_EXPORT_ALL_SYMBOLS has been discarded for some other reasons in vcpkg: https://github.com/microsoft/vcpkg/blob/master/docs/maintainers/maintainer-guide.md#do-not-add-cmake_windows_export_all_symbols
So, I suggest we may consider discarding WINDOWS_EXPORT_ALL_SYMBOLS as well.
I think we have two choices here:

Discard dynamic library support on Windows.
Use __decpspec() to decorate all the public APIs, like what I did in:

libfoo_v2
libfoo_v3

What seems immediately obvious to me is that we need to add tests for dynamic library support. We have CI tests under Windows... but not for dynamic library.
@myd7349  Would you be willing to prepare a PR or, at least, elaborate on your proposal?

The bug is verified: https://ci.appveyor.com/project/lemire/simdjson

cc @ioioioio

cc @jkeiser

I think that illustrative logic from @myd7349 's example  is found in this file...
https://github.com/myd7349/Ongoing-Study/blob/3d28ccb7e50e344dc2599269726e2ddd581880f0/cpp/CMake/libfoo_v2/include/libfoo/foo.h

@myd7349 BTW, we do want to export json_parse_ptr as a function pointer.

Or maybe not.

Ok. I have a possible fix in this PR...
https://github.com/lemire/simdjson/pull/252
It builds.
However ctest fails because the DLL is not found. It is a path issue.

Ok. Need to copy over the DLL... I think it works now.

@myd7349 We can build a DLL and link against it on Windows. This is now part of our CI. Hopefully, this will solve the issue you encountered.
Of course, it is still possible to change how we generate the DLL.
I will shortly issue a new release.


tarball job fails on master

Describe the bug
https://hydra.nixos.org/build/130890698
To Reproduce
Steps to reproduce the behavior:
Notify maintainers

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:

It builds now; latest ATM: https://hydra.nixos.org/build/131061086


markdown-ify our contact page, add GPG details

Closes #33 in tiaga

I should also mention, tested locally.

:+1: from me, just need t'otherd

Looks good.

FDI'd with extreme J


ui: add settings page with change email form

ref: cern-sis/issues-inspire#179

@karolina-siemieniuk-morawska thank you! Could we add e2e when you modify the email that the Change button is active? Also with a validation error?


Take over maintenance or replace nfproxy

Upstream project is unmaintained, we should vendor it to continue maintenance.

I think we want to yeet that one anyway. Don't know if vendoring is worth the effort since there wont be any change in upstream and we have it pinned anyway


Allow lifetime parameters in functions

#[cxx::bridge]
pub mod ffi {
    extern "C" {
        type CThing;
        type CThingChild;
        fn MakeAChildCThing<'a> (v: &'a mut CThing, key: &str) -> &'a mut CThingChild;
    }
}

reports:
error[cxxbridge]: extern function with generic parameters is not supported yet

    ┌─ ../ff.rs:19:9
    │
 19 │         fn MakeAChildCThing<'a> (v: &'a mut CThing, key: &str) -> &'a mut CThingChild;
    │         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ extern function with generic parameters is not supported yet
    │

As far as I can tell, this requires a bit more nuance in
fn parse_extern_fn(foreign_fn: &ForeignItemFn, lang: Lang) -> Result<ExternFn> {
    let generics = &foreign_fn.sig.generics;
    if !generics.params.is_empty() || generics.where_clause.is_some() {
        return Err(Error::new_spanned(
            foreign_fn,
            "extern function with generic parameters is not supported yet",
        ));
    }
   ...
}

to let lifetime generic parameters through whilst rejecting all other types of generic parameters.
Before trying to put together a PR, I wanted to ask whether you consider lifetime parameters "harmless" here and would accept a PR.
Arguments to allow such lifetime parameters:

It enables Rust code to manipulate trees/more complex data structures on the C++ side which is currently impossible.
The current restriction is arbitrary - this would work:

fn MakeAChildCThing (v: &mut CThing, pos: u16) -> &mut CThingChild;

Arguments not to allow this:

We are stating to Rust code that it's safe to manipulate CThingChild even though it's owned by CThing, and there are no guarantees that C++ will make this safe. In fact it's incredibly likely that typical C++ code will make this unsafe, unless a lot of attention has been paid to pointer stability.
There is a nasty workaround, which is instead to return UniquePtr<CThingChild> and then call into_raw. This obviously requires an unsafe keyword on the Rust side, which might be a good thing.

Sorry about the seemingly arbitrary restriction, I know those can be frustrating.
I restricted this in the MVP to preserve the property that one can examine just the C++ side, without context about the specific code on the Rust code or even Rust at all, and notice anything incorrect just based on one's usual heuristics for reviewing C++ code and seeing the red flags.
If we allow an output reference where the decision of which of two input references it's supposed to borrow from is only encoded in the Rust-side signature, then it's possible for the C++ implementation of a function to be wrong in a way that cannot be caught by reviewing only C++ code.
I am interested in solving this but we need to be careful that afterward it still remains possible to audit and find every possible soundness bug in the program by starting from some C++ code or from a Rust unsafe block.
Some ideas:

We could put in heuristics about signatures involving &str and other specific types. For example in a signature like fn(&mut CThing, &str) -> &mut CThingChild it's obvious that the output mutable reference isn't going to be borrowed from inside the contents of the const &str, and it would be a big red flag in the C++ code if it were, so this is fine to allow.

We could allow raw pointers in FFI signatures, where an extern "C" function with any raw pointer argument makes it unsafe to call. The expectation would be that the user wraps these in a safe function with the correct lifetimes in its signature. When auditing, you find the unsafe block inside that safe wrapper and confirm that its lifetime expectations match the behavior of the C++ implementation.

Thanks for the reply. Yes, I agree with your reasoning.
I prefer the latter solution (allowing raw pointers through FFI), and I was eventually going to propose that anyway as a good thing to do: it feels correct to force people to write unsafe blocks for stuff like this. That's essentially what I'm doing via the UniquePtr<...>::into_raw() workaround.
I do not feel I'm very likely to get around to doing that especially soon, mind you :) - it's probably a more substantial change than tinkering with parse_extern_fn. But it's good to know which way you're thinking about it in case I get a bit of time. Thanks again.


copy k8s.io/kubernetes/pkg/util/io to k8s.io/utils/io

This change is a precondition of moving k8s.io/kubernetes/pkg/util/mount out of the kubernetes package. The whole set of work is related to kubernetes/kubernetes#69585. Once this is merged I'll update the kubernetes code to reference it and remove the package from kubernetes/kubernetes
/kind feature
/assign @lavalamp
/cc @andrewsykim

I've definitely signed the CLA, seems to have succeed on one of 3 PRs. Guess we'll try again.
/check-cla

/test cla/linuxfoundation

Looks like the CLA check is failing on one of the merged commits. This will probably need overridden. The commits all come from kubernetes/kubernetes so they should have already been covered, right?

Any thoughts on tests for this?  It's pretty trivial, but I hate untested code.
I'll approve since it's not making life any worse.  Ping me on the followup if you need.

/lgtm
/approve

@thockin Thanks! I'll add some tests and submit a PR for them tomorrow.

@mcrute also update README here https://github.com/kubernetes/utils#libraries :)

Thanks for preserving history!


Modules from HotReplacementPlugin being injected into inline JS

When I'm using inline JS with webpack-dev-server, the inline JS code will be injected with hot replacement code from HotReplacementPlugin and webpack bootstrap code.
In my circumstance, the inline JS code throws an error claiming Automatic publicPath is not supported in this browser and stops execution.
If I run a build instead of dev server, the inline JS script works perfectly.
I have no idea how to deal with this.
I'll be waiting for your reply on this, thanks.

Hi @YUCLing,
thank you for the issue report!
I'm very sorry, but is a really big problem to fix it, hardly possible, because Webpack self generates JS code and hasn't option to disable injection of HMR code.
Only one idea comes to mind. This is a "hack", of course, but it will work.
Pass the isDev variable into Pug template and use inline JS only if isDev is false.
Pass the mode into webpack.config.js:
packages.json
{
  "scripts": {
    "start": "webpack serve --mode=development",
    "build": "webpack --mode=production --progress",
  },
}

webpack.config.js
module.exports = (env, argv) => {
  const isDev = argv.mode === 'development';

  return {
    entry: {
      index: './src/views/home/index.pug',
    },
    plugins: [
      new PugPlugin(),
    ],
    module: {
      rules: [
        {
          test: /.pug$/,
          loader: PugPlugin.loader,
          options: {
            data: {
              isDev, // pass variable in all Pug files
            }
          }
        },
      ],
    },
  };
}

Pug file
head
  if isDev
    script(src=require('./main.js') defer='defer')
  else
    script=require('./main.js?inline')
body

Sad to hear this, but still appreciate your effort.
Since I can accept using extracted JS in dev mode, so the temporary hack works for me. 😃
However, this will be helpful and can make the code simpler if there will be a solution found.

I will try to find a workaround for this problem.

@YUCLing
I found the problem, I can fix it!

@YUCLing
I have fixed the issue in v4.9.2.

Strange, I'm still getting unexpected output here...
Let me see if I can make a minimal reproduction. 😄

@YUCLing

unexpected output

In webpack serve mode or by build too?

@YUCLing

unexpected output

In webpack serve mode or by build too?

Still serve only since I only use HMR in dev mode.

@YUCLing
yes, inlined JS contains the HRM code (inc. source maps) and works in a Browser very well with reference to source file.

The same issue was described by mini-css-extract-plugin issue.
It is a limitation of Webpack.


Feature request: Include lessons on asynchronous calls and Promises prior to API challenges.

Challenge Build a Wikipedia Viewer has an issue.
User Agent is: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:53.0) Gecko/20100101 Firefox/53.0.
Please describe how to reproduce this issue, and include links to screenshots if possible.
On the Weather App Challenge and the Wikipedia Viewer challenge I had to be shown code that would make my API call work. Both challenges involved asynchronous data and "Promise" code of some sort. Honestly, I feel like I cheated on these after banging my head against the proverbial wall for a couple days, and having to ask for the answer. A little preparation prior to this would have helped. At least, I hope it would have :) I do have a thick skull.
https://codepen.io/TinCan-Assassin/pen/qmZrOQ?editors=1111
Comments starting at JS line 42 regard this issue.

This is a bug due to the lack of preparation prior to the challenge.
Sent from my Verizon, Samsung Galaxy smartphone
-------- Original message --------From: VarCI Bot<EMAIL_ADDRESS>Date: 4/25/17  8:28 PM  (GMT-05:00) To: freeCodeCamp/freeCodeCamp<EMAIL_ADDRESS>Cc: TinCan-Assassin<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [freeCodeCamp/freeCodeCamp] Feature request: Include lessons on asynchronous calls and Promises prior to API challenges. (#14593)
Hi @TinCan-Assassin
The issue tracker is for reporting bugs only. If this is a request for help with a challenge, please use the help chat room or try looking through the forum for help with a specific challenge.
If this is the case, please close this issue.
Happy Coding.
Automated response by Var.CI 🤖
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/freeCodeCamp/freeCodeCamp","title":"freeCodeCamp/freeCodeCamp","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/freeCodeCamp/freeCodeCamp"}},"updates":{"snippets":[{"icon":"PERSON","message":"@VarCI-bot in #14593: Hi @TinCan-Assassin\n\nThe issue tracker is for reporting bugs only. If this is a request for help with a challenge, please use the help chat room or try looking through the forum for help with a specific challenge.\n\nIf this is the case, please close this issue.\n\nHappy Coding.\n\n\n--\n_Automated response by Var.CI_ :robot:"}],"action":{"name":"View Issue","url":"https://github.com/freeCodeCamp/freeCodeCamp/issues/14593#issuecomment-297202969"}}}


Fixes #703 fixes trip future date issue in AddNewTripActivity.java

Description
When I selected a future date of the current month on add new trip screen it gives error snack bar. But when I selected next month date it works fine. So I have fixed that when we selected any future date of any month. It works fine.
Fixes #703
Type of change
Just put an x in the [] which are valid.

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes.

[X] ./gradlew assembleDebug assembleRelease
[X] ./gradlew checkstyle

Checklist:

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[X] My changes generate no new warnings

@AminullahTajMuhammad Travis checks are failing. Please check.

@Swati4star fixed changes


.github/workflows: split release into pre-release-ci and release (manual)

Previously, we run the release workflow automatically whenever a v* tag
gets pushed. The existing workflow does not work because the tests can be
flaky. When that happens, there's no way to release a new TF version since
goreleaser will only run once all the acceptance tests pass.
Until the flakiness goes away, we will split the release workflow into
two: pre-release-ci (that runs automatically like before), and release (which
has to be triggered manually after all the acceptance tests are triaged).
Commit checklist

[X] Changelog -- irrelevant
[X] Doc gen (make generate) -- irrelevant
[X] Integration test(s) -- irrelevant
[X] Acceptance test(s) -- irrelevant
[X] Example(s) -- irrelevant

TFTR!


ML 1.1 : Variables, Range, Population Distribution, Sample Distribution (V) #600

Description 📜
A video giving an overview of the topics Variables, Range, Population Distribution, Sample Distribution
Fixes #600

Type of change 📝

[x] Video (Animations, screen-recordings, presentations and regular explanatory films are all possibilties etc)

Domain of Contribution 📊

[x] Machine Learning

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

Welcome to the open source community @deepthi1107. Hope you make more contributions in future! PR merged.


moveit: 2.7.2-1 in 'rolling/distribution.yaml' [bloom]

Increasing version of package(s) in repository moveit to 2.7.2-1:

upstream repository: https://github.com/ros-planning/moveit2.git
release repository: https://github.com/ros2-gbp/moveit2-release.git
distro file: rolling/distribution.yaml
bloom version: 0.11.2
previous version for package: 2.7.1-1

chomp_motion_planner

No changes

moveit
* moveit_py: Python interface for MoveIt 2
* Contributors: Jens Vanhooydonck, Peter David Fagan, Robert Haschke, Sebastian Jahr

moveit_chomp_optimizer_adapter

No changes

moveit_common
* Switch from qos_event.hpp to event_handler.hpp (#2111 <https://github.com/ros-planning/moveit2/issues/2111>)
  * Switch from qos_event.hpp to event_handler.hpp
  * moveit_common: Add a cmake interface library to keep humble support on main
  * Include qos_event.hpp or event_handler.hpp depending on the ROS 2 version
  * Fix ament_lint_cmake
  * Fix clang-tidy
  * PRIVATE linking in some cases
  * Update moveit_common/cmake/moveit_package.cmake
  Co-authored-by: Chris Thrasher<EMAIL_ADDRESS>  * Fix servo and cleanup excessive CMake variable usage
  * Cleanup & make compiling
  * Small variable naming and const cleanup
  * Restore OpenCV linking
  * Public/private linking fixup
  * Revert "Restore OpenCV linking"
  This reverts commit 57a9efa806e59223e35a1f7e998d7b52f930c263.
  ---------
  Co-authored-by: JafarAbdi<EMAIL_ADDRESS>  Co-authored-by: Jafar<EMAIL_ADDRESS>  Co-authored-by: AndyZe<EMAIL_ADDRESS>  Co-authored-by: Chris Thrasher<EMAIL_ADDRESS>* enabled -wformat (#2065 <https://github.com/ros-planning/moveit2/issues/2065>)
  Co-authored-by: Sebastian Jahr<EMAIL_ADDRESS>* Contributors: Heramb Modugula, Sebastian Jahr

moveit_configs_utils
* Update pre-commit (#2094 <https://github.com/ros-planning/moveit2/issues/2094>)
* Use $DISPLAY rather than assuming :0 (#2049 <https://github.com/ros-planning/moveit2/issues/2049>)
  * Use $DISPLAY rather than assuming :
  * Double quotes
  ---------
  Co-authored-by: Sebastian Jahr<EMAIL_ADDRESS>* Contributors: Shobuj Paul, Stephanie Eng

moveit_core
* Add JointModel::satisfiesAccelerationBounds() (#2092 <https://github.com/ros-planning/moveit2/issues/2092>)
  * Add JointModel::satisfiesAccelerationBounds()
  * Check Jerk bounds too
  * Check if bounds exist
  ---------
  Co-authored-by: Sebastian Jahr<EMAIL_ADDRESS>* A ROS param for Servo filter coefficient (#2091 <https://github.com/ros-planning/moveit2/issues/2091>)
  * Add generate_parameter_library as dependency
  * Generate and export parameter target
  * Update butterworth filter to use params
  * Move param listener declaration to header
  * Formatting
  * Remove unnecessary rclcpp include
  * Fix alphabetical order
  * Make param listener local
  * Fix target exporting in cmake
  * Add moveit_ prefix to parameter library target
  * Remove obsolete comment
  * Member variable naming
  * Alphabetize
  ---------
  Co-authored-by: AndyZe<EMAIL_ADDRESS>* Merge pull request #1900 <https://github.com/ros-planning/moveit2/issues/1900> from Abishalini/pr-sync-1245f15
  Sync with MoveIt1
* Readd comment and assign error code
* Merge https://github.com/ros-planning/moveit/commit/1245f151393fe09023efec3e1faead2d26737227
* Add test and debug issue where TOTG returns accels > limit (#2084 <https://github.com/ros-planning/moveit2/issues/2084>)
* Move stateless PlanningScene helper functions out of the class (#2025 <https://github.com/ros-planning/moveit2/issues/2025>)
* Document how collision checking includes descendent links (#2058 <https://github.com/ros-planning/moveit2/issues/2058>)
* Optionally mitigate Ruckig overshoot (#2051 <https://github.com/ros-planning/moveit2/issues/2051>)
  * Optionally mitigate Ruckig overshoot
  * Cleanup
* Delete the Ruckig "batches" option, deprecated by #1990 <https://github.com/ros-planning/moveit2/issues/1990> (#2028 <https://github.com/ros-planning/moveit2/issues/2028>)
* Merge PR #3197 <https://github.com/ros-planning/moveit2/issues/3197>: Improve computeCartesianPath()
* Gracefully handle gtest 1.8 (Melodic)
  gtest 1.8 doesn't provide SetUpTestSuite().
  Thus, we cannot share the RobotModel across tests.
* Add unit tests for computeCartesianPath()
* Add utils to simplify (approximate) equality checks for Eigen entities
* robot_model_test_utils: Add loadIKPluginForGroup()
* Simplify test_cartesian_interpolator.cpp
* Generalize computeCartesianPath() to consider a link_offset
  This allows performing a circular motion about a non-link origin.
* Cleanup CartesianInterpolator
  - Fixup doc comments
  - Add API providing the translation vector = direction * distance
  - Simplify implementation
* Contributors: Abishalini, Abishalini Sivaraman, AndyZe, Robert Haschke, V Mohammed Ibrahim

moveit_hybrid_planning
* Switch from qos_event.hpp to event_handler.hpp (#2111 <https://github.com/ros-planning/moveit2/issues/2111>)
  * Switch from qos_event.hpp to event_handler.hpp
  * moveit_common: Add a cmake interface library to keep humble support on main
  * Include qos_event.hpp or event_handler.hpp depending on the ROS 2 version
  * Fix ament_lint_cmake
  * Fix clang-tidy
  * PRIVATE linking in some cases
  * Update moveit_common/cmake/moveit_package.cmake
  Co-authored-by: Chris Thrasher<EMAIL_ADDRESS>  * Fix servo and cleanup excessive CMake variable usage
  * Cleanup & make compiling
  * Small variable naming and const cleanup
  * Restore OpenCV linking
  * Public/private linking fixup
  * Revert "Restore OpenCV linking"
  This reverts commit 57a9efa806e59223e35a1f7e998d7b52f930c263.
  ---------
  Co-authored-by: JafarAbdi<EMAIL_ADDRESS>  Co-authored-by: Jafar<EMAIL_ADDRESS>  Co-authored-by: AndyZe<EMAIL_ADDRESS>  Co-authored-by: Chris Thrasher<EMAIL_ADDRESS>* Update pre-commit (#2094 <https://github.com/ros-planning/moveit2/issues/2094>)
* [hybrid planning] improve planning scene monitoring (#1090 <https://github.com/ros-planning/moveit2/issues/1090>)
  * Create new PSM in local constraint solver. Different type of collision checking.
  * Small boolean logic fixup
  * Don't configure planning scene monitor twice and pass scene as const
  * Remove not required call of updateSceneWithCurrentState()
  * Revert PlanningSceneMonitorConstPtr to PlanningSceneMonitorPtr
  * Set planning_scene_monitor update rate
  * Decrease planning scene update rate
  * Use updateSceneWithCurrentState() in psm
  * Revert the manner of collision checking
  ---------
  Co-authored-by: Sebastian Jahr<EMAIL_ADDRESS>* Contributors: AndyZe, Sebastian Jahr, Shobuj Paul

moveit_kinematics
* Fix moveit_kinematics dependency on moveit_ros_planning (#2109 <https://github.com/ros-planning/moveit2/issues/2109>)
  This dependency is unconditionally used even if tests are disabled.
* Update pre-commit (#2094 <https://github.com/ros-planning/moveit2/issues/2094>)
* Readability: kinematic_state -> robot_state (#2078 <https://github.com/ros-planning/moveit2/issues/2078>)
* Contributors: Scott K Logan, Sebastian Jahr, Shobuj Paul

moveit_planners

No changes

moveit_planners_chomp

No changes

moveit_planners_ompl
* Update pre-commit (#2094 <https://github.com/ros-planning/moveit2/issues/2094>)
* Contributors: Shobuj Paul

moveit_plugins

No changes

moveit_py
* Fix Formatting in Python Documentation (#2085 <https://github.com/ros-planning/moveit2/issues/2085>)
  * fix formatting in docs
  * Fix clang-tidy warnings
  ---------
  Co-authored-by: Tyler Weaver<EMAIL_ADDRESS>  Co-authored-by: Tyler Weaver<EMAIL_ADDRESS>  Co-authored-by: Sebastian Jahr<EMAIL_ADDRESS>* Update moveit_py 'get_planning_scene_monitor' to return NonConst (#2098 <https://github.com/ros-planning/moveit2/issues/2098>)
  Co-authored-by: Jafar<EMAIL_ADDRESS>* Fix MoveItCpp issues (port from MoveIt1) (#2001 <https://github.com/ros-planning/moveit2/issues/2001>)
  * Fix MoveitCpp's const member accessors
  They should return a ConstPtr instead of a const Ptr&!
  * Fix SEVERE ClassLoader warning when releasing MoveItCpp
  - PSM was released before copy of its RobotModel -> removed extra RobotModel copy
  - clearContents() was broken:
  - resets in wrong order: psm_ should be last
  - trajectory_execution_manager_ was missing
  I suggest to omit clearContents() and rely on the (correct) ordering of member variables.
  While this is not explicit, we ensure that we don't miss any newly added member variable.
  Fix: https://github.com/ros-planning/moveit2/issues/1597
  ---------
  Co-authored-by: Sebastian Jahr<EMAIL_ADDRESS>  Co-authored-by: Jafar<EMAIL_ADDRESS>  Co-authored-by: Sebastian Jahr<EMAIL_ADDRESS>  Co-authored-by: JafarAbdi<EMAIL_ADDRESS>* Extract parallel planning from moveit cpp (#2043 <https://github.com/ros-planning/moveit2/issues/2043>)
  * Add parallel_planning_interface
  * Add parallel planning interface
  * Rename package to pipeline_planning_interface
  * Move plan_responses_container into own header + source file
  * Add plan_responses_contrainer source file
  * Add solution selection and stopping criterion function files
  * Remove parallel planning from moveit_cpp
  * Move parallel planning into planning package
  * Update moveit_cpp
  * Drop planning_interface changes
  * Add documentation
  * Update other moveit packages
  * Remove removed header
  * Address CI complains
  * Address clang-tidy complains
  * Address clang-tidy complains 2
  * Address clang-tidy complains 3
  * Extract planning pipeline map creation function from moveit_cpp
  * Cleanup comment
  * Use const moveit::core::RobotModelConstPtr&
  * Formatting
  * Add header descriptions
  * Remove superfluous TODOs
  * Cleanup
* moveit_py citation (#2029 <https://github.com/ros-planning/moveit2/issues/2029>)
* Added set_robot_trajectory_msg to python bindings (#2050 <https://github.com/ros-planning/moveit2/issues/2050>)
* Contributors: Jens Vanhooydonck, Peter David Fagan, Robert Haschke, Sebastian Jahr

moveit_resources_prbt_ikfast_manipulator_plugin

No changes

moveit_resources_prbt_moveit_config
* Update pre-commit (#2094 <https://github.com/ros-planning/moveit2/issues/2094>)
* Contributors: Shobuj Paul

moveit_resources_prbt_pg70_support

No changes

moveit_resources_prbt_support

No changes

moveit_ros

No changes

moveit_ros_benchmarks
* Update pre-commit (#2094 <https://github.com/ros-planning/moveit2/issues/2094>)
* Extract parallel planning from moveit cpp (#2043 <https://github.com/ros-planning/moveit2/issues/2043>)
  * Add parallel_planning_interface
  * Add parallel planning interface
  * Rename package to pipeline_planning_interface
  * Move plan_responses_container into own header + source file
  * Add plan_responses_contrainer source file
  * Add solution selection and stopping criterion function files
  * Remove parallel planning from moveit_cpp
  * Move parallel planning into planning package
  * Update moveit_cpp
  * Drop planning_interface changes
  * Add documentation
  * Update other moveit packages
  * Remove removed header
  * Address CI complains
  * Address clang-tidy complains
  * Address clang-tidy complains 2
  * Address clang-tidy complains 3
  * Extract planning pipeline map creation function from moveit_cpp
  * Cleanup comment
  * Use const moveit::core::RobotModelConstPtr&
  * Formatting
  * Add header descriptions
  * Remove superfluous TODOs
  * Cleanup
* Contributors: Sebastian Jahr, Shobuj Paul

moveit_ros_control_interface

No changes

moveit_ros_move_group
* Fix MoveItCpp issues (port from MoveIt1) (#2001 <https://github.com/ros-planning/moveit2/issues/2001>)
  * Fix MoveitCpp's const member accessors
  They should return a ConstPtr instead of a const Ptr&!
  * Fix SEVERE ClassLoader warning when releasing MoveItCpp
  - PSM was released before copy of its RobotModel -> removed extra RobotModel copy
  - clearContents() was broken:
  - resets in wrong order: psm_ should be last
  - trajectory_execution_manager_ was missing
  I suggest to omit clearContents() and rely on the (correct) ordering of member variables.
  While this is not explicit, we ensure that we don't miss any newly added member variable.
  Fix: https://github.com/ros-planning/moveit2/issues/1597
  ---------
  Co-authored-by: Sebastian Jahr<EMAIL_ADDRESS>  Co-authored-by: Jafar<EMAIL_ADDRESS>  Co-authored-by: Sebastian Jahr<EMAIL_ADDRESS>  Co-authored-by: JafarAbdi<EMAIL_ADDRESS>* Contributors: Robert Haschke

moveit_ros_occupancy_map_monitor
* Switch from qos_event.hpp to event_handler.hpp (#2111 <https://github.com/ros-planning/moveit2/issues/2111>)
  * Switch from qos_event.hpp to event_handler.hpp
  * moveit_common: Add a cmake interface library to keep humble support on main
  * Include qos_event.hpp or event_handler.hpp depending on the ROS 2 version
  * Fix ament_lint_cmake
  * Fix clang-tidy
  * PRIVATE linking in some cases
  * Update moveit_common/cmake/moveit_package.cmake
  Co-authored-by: Chris Thrasher<EMAIL_ADDRESS>  * Fix servo and cleanup excessive CMake variable usage
  * Cleanup & make compiling
  * Small variable naming and const cleanup
  * Restore OpenCV linking
  * Public/private linking fixup
  * Revert "Restore OpenCV linking"
  This reverts commit 57a9efa806e59223e35a1f7e998d7b52f930c263.
  ---------
  Co-authored-by: JafarAbdi<EMAIL_ADDRESS>  Co-authored-by: Jafar<EMAIL_ADDRESS>  Co-authored-by: AndyZe<EMAIL_ADDRESS>  Co-authored-by: Chris Thrasher<EMAIL_ADDRESS>* Contributors: Sebastian Jahr

moveit_ros_perception
* Switch from qos_event.hpp to event_handler.hpp (#2111 <https://github.com/ros-planning/moveit2/issues/2111>)
  * Switch from qos_event.hpp to event_handler.hpp
  * moveit_common: Add a cmake interface library to keep humble support on main
  * Include qos_event.hpp or event_handler.hpp depending on the ROS 2 version
  * Fix ament_lint_cmake
  * Fix clang-tidy
  * PRIVATE linking in some cases
  * Update moveit_common/cmake/moveit_package.cmake
  Co-authored-by: Chris Thrasher<EMAIL_ADDRESS>  * Fix servo and cleanup excessive CMake variable usage
  * Cleanup & make compiling
  * Small variable naming and const cleanup
  * Restore OpenCV linking
  * Public/private linking fixup
  * Revert "Restore OpenCV linking"
  This reverts commit 57a9efa806e59223e35a1f7e998d7b52f930c263.
  ---------
  Co-authored-by: JafarAbdi<EMAIL_ADDRESS>  Co-authored-by: Jafar<EMAIL_ADDRESS>  Co-authored-by: AndyZe<EMAIL_ADDRESS>  Co-authored-by: Chris Thrasher<EMAIL_ADDRESS>* Update pre-commit (#2094 <https://github.com/ros-planning/moveit2/issues/2094>)
* Contributors: Sebastian Jahr, Shobuj Paul

moveit_ros_planning
* Switch from qos_event.hpp to event_handler.hpp (#2111 <https://github.com/ros-planning/moveit2/issues/2111>)
  * Switch from qos_event.hpp to event_handler.hpp
  * moveit_common: Add a cmake interface library to keep humble support on main
  * Include qos_event.hpp or event_handler.hpp depending on the ROS 2 version
  * Fix ament_lint_cmake
  * Fix clang-tidy
  * PRIVATE linking in some cases
  * Update moveit_common/cmake/moveit_package.cmake
  Co-authored-by: Chris Thrasher<EMAIL_ADDRESS>  * Fix servo and cleanup excessive CMake variable usage
  * Cleanup & make compiling
  * Small variable naming and const cleanup
  * Restore OpenCV linking
  * Public/private linking fixup
  * Revert "Restore OpenCV linking"
  This reverts commit 57a9efa806e59223e35a1f7e998d7b52f930c263.
  ---------
  Co-authored-by: JafarAbdi<EMAIL_ADDRESS>  Co-authored-by: Jafar<EMAIL_ADDRESS>  Co-authored-by: AndyZe<EMAIL_ADDRESS>  Co-authored-by: Chris Thrasher<EMAIL_ADDRESS>* Fix MoveItCpp issues (port from MoveIt1) (#2001 <https://github.com/ros-planning/moveit2/issues/2001>)
  * Fix MoveitCpp's const member accessors
  They should return a ConstPtr instead of a const Ptr&!
  * Fix SEVERE ClassLoader warning when releasing MoveItCpp
  - PSM was released before copy of its RobotModel -> removed extra RobotModel copy
  - clearContents() was broken:
  - resets in wrong order: psm_ should be last
  - trajectory_execution_manager_ was missing
  I suggest to omit clearContents() and rely on the (correct) ordering of member variables.
  While this is not explicit, we ensure that we don't miss any newly added member variable.
  Fix: https://github.com/ros-planning/moveit2/issues/1597
  ---------
  Co-authored-by: Sebastian Jahr<EMAIL_ADDRESS>  Co-authored-by: Jafar<EMAIL_ADDRESS>  Co-authored-by: Sebastian Jahr<EMAIL_ADDRESS>  Co-authored-by: JafarAbdi<EMAIL_ADDRESS>* Extract parallel planning from moveit cpp (#2043 <https://github.com/ros-planning/moveit2/issues/2043>)
  * Add parallel_planning_interface
  * Add parallel planning interface
  * Rename package to pipeline_planning_interface
  * Move plan_responses_container into own header + source file
  * Add plan_responses_contrainer source file
  * Add solution selection and stopping criterion function files
  * Remove parallel planning from moveit_cpp
  * Move parallel planning into planning package
  * Update moveit_cpp
  * Drop planning_interface changes
  * Add documentation
  * Update other moveit packages
  * Remove removed header
  * Address CI complains
  * Address clang-tidy complains
  * Address clang-tidy complains 2
  * Address clang-tidy complains 3
  * Extract planning pipeline map creation function from moveit_cpp
  * Cleanup comment
  * Use const moveit::core::RobotModelConstPtr&
  * Formatting
  * Add header descriptions
  * Remove superfluous TODOs
  * Cleanup
* Move displaced launch file into planning_component_tools (#2044 <https://github.com/ros-planning/moveit2/issues/2044>)
* Contributors: Robert Haschke, Sebastian Jahr

moveit_ros_planning_interface
* Update pre-commit (#2094 <https://github.com/ros-planning/moveit2/issues/2094>)
* Merge pull request #1900 <https://github.com/ros-planning/moveit2/issues/1900> from Abishalini/pr-sync-1245f15
  Sync with MoveIt1
* Readd comment and assign error code
* Merge https://github.com/ros-planning/moveit/commit/1245f151393fe09023efec3e1faead2d26737227
* Update description of moveit_ros_planning_interface (#2045 <https://github.com/ros-planning/moveit2/issues/2045>)
  * Update description of moveit_ros_planning_interface
  * Update moveit_ros/planning_interface/package.xml
  Co-authored-by: Henning Kayser<EMAIL_ADDRESS>  ---------
  Co-authored-by: Henning Kayser<EMAIL_ADDRESS>* Merge PR #3197 <https://github.com/ros-planning/moveit2/issues/3197>: Improve computeCartesianPath()
* Simplify MGI::computeCartesianPath()
* Contributors: Abishalini, Abishalini Sivaraman, Robert Haschke, Sebastian Jahr, Shobuj Paul

moveit_ros_robot_interaction

No changes

moveit_ros_visualization
* Readability: kinematic_state -> robot_state (#2078 <https://github.com/ros-planning/moveit2/issues/2078>)
* Contributors: Sebastian Jahr

moveit_ros_warehouse
* Switch from qos_event.hpp to event_handler.hpp (#2111 <https://github.com/ros-planning/moveit2/issues/2111>)
  * Switch from qos_event.hpp to event_handler.hpp
  * moveit_common: Add a cmake interface library to keep humble support on main
  * Include qos_event.hpp or event_handler.hpp depending on the ROS 2 version
  * Fix ament_lint_cmake
  * Fix clang-tidy
  * PRIVATE linking in some cases
  * Update moveit_common/cmake/moveit_package.cmake
  Co-authored-by: Chris Thrasher<EMAIL_ADDRESS>  * Fix servo and cleanup excessive CMake variable usage
  * Cleanup & make compiling
  * Small variable naming and const cleanup
  * Restore OpenCV linking
  * Public/private linking fixup
  * Revert "Restore OpenCV linking"
  This reverts commit 57a9efa806e59223e35a1f7e998d7b52f930c263.
  ---------
  Co-authored-by: JafarAbdi<EMAIL_ADDRESS>  Co-authored-by: Jafar<EMAIL_ADDRESS>  Co-authored-by: AndyZe<EMAIL_ADDRESS>  Co-authored-by: Chris Thrasher<EMAIL_ADDRESS>* Contributors: Sebastian Jahr

moveit_runtime

No changes

moveit_servo
* Switch from qos_event.hpp to event_handler.hpp (#2111 <https://github.com/ros-planning/moveit2/issues/2111>)
  * Switch from qos_event.hpp to event_handler.hpp
  * moveit_common: Add a cmake interface library to keep humble support on main
  * Include qos_event.hpp or event_handler.hpp depending on the ROS 2 version
  * Fix ament_lint_cmake
  * Fix clang-tidy
  * PRIVATE linking in some cases
  * Update moveit_common/cmake/moveit_package.cmake
  Co-authored-by: Chris Thrasher<EMAIL_ADDRESS>  * Fix servo and cleanup excessive CMake variable usage
  * Cleanup & make compiling
  * Small variable naming and const cleanup
  * Restore OpenCV linking
  * Public/private linking fixup
  * Revert "Restore OpenCV linking"
  This reverts commit 57a9efa806e59223e35a1f7e998d7b52f930c263.
  ---------
  Co-authored-by: JafarAbdi<EMAIL_ADDRESS>  Co-authored-by: Jafar<EMAIL_ADDRESS>  Co-authored-by: AndyZe<EMAIL_ADDRESS>  Co-authored-by: Chris Thrasher<EMAIL_ADDRESS>* [Servo] Document the new low-pass filter param (#2114 <https://github.com/ros-planning/moveit2/issues/2114>)
  * [Servo] Document the new low-pass filter param
  * More intuitive parameter ordering
* Update pre-commit (#2094 <https://github.com/ros-planning/moveit2/issues/2094>)
* Compute velocity using central difference (#2080 <https://github.com/ros-planning/moveit2/issues/2080>)
  * Compute velocity using central difference
  * Update calculation
  * Save and use x(t - dt)
  * Fix saving x(t - dt)
  * Fix confusing comment.
  * Explainer comment for last_joint_state_
  Co-authored-by: AndyZe<EMAIL_ADDRESS>  * Change x to q in comments to signify joint domain
  * Avoid pass-by-reference for basic types
  ---------
  Co-authored-by: AndyZe<EMAIL_ADDRESS>* Contributors: AndyZe, Sebastian Jahr, Shobuj Paul, V Mohammed Ibrahim

moveit_setup_app_plugins

No changes

moveit_setup_assistant
* Update pre-commit (#2094 <https://github.com/ros-planning/moveit2/issues/2094>)
* Contributors: Shobuj Paul

moveit_setup_controllers
* Update pre-commit (#2094 <https://github.com/ros-planning/moveit2/issues/2094>)
* Contributors: Shobuj Paul

moveit_setup_core_plugins
* Update pre-commit (#2094 <https://github.com/ros-planning/moveit2/issues/2094>)
* Add URDF Loader Exceptions and Fix Infinite While-Loop when URDF file isn't in a ROS Package (#2032 <https://github.com/ros-planning/moveit2/issues/2032>)
  * Fixed infinite while loop in utilities.cpp and added some exception handling to start screen widget
  * Fix trailing whitespace, fix getSharePath exception catch on empty request
  * Fix clang tidy suggestion and error message updates based on pr comments
* Contributors: Chance Cardona, Shobuj Paul

moveit_setup_framework
* Add URDF Loader Exceptions and Fix Infinite While-Loop when URDF file isn't in a ROS Package (#2032 <https://github.com/ros-planning/moveit2/issues/2032>)
  * Fixed infinite while loop in utilities.cpp and added some exception handling to start screen widget
  * Fix trailing whitespace, fix getSharePath exception catch on empty request
  * Fix clang tidy suggestion and error message updates based on pr comments
* Contributors: Chance Cardona

moveit_setup_srdf_plugins

No changes

moveit_simple_controller_manager

No changes

pilz_industrial_motion_planner
* Update pre-commit (#2094 <https://github.com/ros-planning/moveit2/issues/2094>)
* PILZ: Throw if IK solver doesn't exist (#2082 <https://github.com/ros-planning/moveit2/issues/2082>)
  * Throw if IK solver doesn't exist
  * Format
* Contributors: Sebastian Jahr, Shobuj Paul

pilz_industrial_motion_planner_testutils

No changes

@cottsay here is a new rolling release with your change. I'm sorry it took me a bit to get this out.

This pull request has been mentioned on ROS Discourse. There might be relevant details there:
https://discourse.ros.org/t/preparing-for-iron-branching-on-rolling-2023-04-18/30980/3


Not sending error to elastic

Hello,
I am trying to use the package with laravel 6 but i got this error:
`"Call to undefined method Elastic\Apm\Impl\Span::setLabel()","trace":"#0 /var/www/html/vendor/anik/elastic-apm-php/src/Agent.php(82): Anik\ElasticApm\Agent->includeSpansToTransaction(Object(Elastic\Apm\Impl\Transaction), Object(Anik\ElasticApm\Spans\QuerySpan))\n#1 /var/www/html/vendor/anik/elastic-apm-php/src/Middleware/RecordForegroundTransaction.php(95): Anik\ElasticApm\Agent->capture()\n#2 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(212): Anik\ElasticApm\Middleware\RecordForegroundTransaction->terminate(Object(Illuminate\Http\Request), Object(Illuminate\Http\Response))\n#3 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(183): Illuminate\Foundation\Http\Kernel->terminateMiddleware(Object(Illuminate\Http\Request), Object(Illuminate\Http\Response))\n#4 /var/www/html/public/index.php(62): Illuminate\Foundation\Http\Kernel->terminate(Object(Illuminate\Http\Request), Object(Illuminate\Http\Response))\n#5 {main}"
I need your help to show errors on my kibana apm dashboard`
Thanks,

I didn't use the package since release. I hopefully will try to update the package this weekend. I guess there is a breaking change in the elastic apm PHP agent. As it's not stable.

I didn't use the package since release. I hopefully will try to update the package this weekend. I guess there is a breaking change in the elastic apm PHP agent. As it's not stable.

@aladin-tsi it is an issue with the latest v1.0.0-beta1 from elastic.
PR submitted: https://github.com/ssi-anik/elastic-apm-php/pull/5

@graemlourens , @aladin-tsi , Are you both able to send the errors to Elastic APM?

@aladin-tsi yes, with my branch it was working when i was experiementing with it a while ago: https://github.com/graemlourens/elastic-apm-php havn't touched it since February, so not sure


BroadPhaseQuery/NarrowPhaseQuery

This exposes BroadPhaseQuery and more of the NarrowPhaseQuery methods.
I didn't like the existing collector objects because they required excessive heap allocation and didn't allow the application to control early exit behavior.   I converted them to C callback functions, and internally the bindings create a C++ collector class that calls the C callback for every hit.  This gives the application more control over how it handles the hits -- it could append to a list, track the closest hit, do custom filtering, immediately cancel the raycast on the first hit, etc.

Oops, the ToJolt methods for the filters are returning references to stack memory, I'll need to rethink those.

Ok this should be good to go, I'm using the new raycast/shapecast callbacks in LÖVR successfully now.  If you have a better idea for those _padding members, go for it, it was just to silence a warning about padding >_<.

Thanks!