parametrising conversion to trecweb script to include Iain's metadata

changes

use argparse for future proof argument passing
includes metadata in trecweb form

an example doc in this format:
<DOCNO>CAR_000000afe1da525b3db17db77f350b187441a9ed</DOCNO>
<DOCHDR>

</DOCHDR>
<TITLE>
enwiki Johannisthal Air Field
</TITLE>
<TAG>
 Accidents
</TAG>
<BODY>
The 1913 Johannisthal Air Disaster happened close to the air field, killing all 28 passengers.The German astronaut Reinhard Furrer died on September 9, 1995 during historic flight show.
</BODY>
</DOC>

The enwiki prefix should be removed for CAR.
I recommend replacing  with a meaningful tag.  e.g.  or similar.

Why replace? removing makes more sense


Invalidation

Browsers generally keep track of what regions of the screen have been invalidated and re-render only those regions of the screen. This PR changes Blitz to use nodes that have been invalidated and rerender only those parts of the screen (along with any layers touching those regions)

It appears this may be blocked until Vello has a incremental scene API: https://github.com/linebender/vello/pull/243#issuecomment-1423391870


Fix display "fan_speed" if only percent(%) or RPM is available.

Tested on both 69902 and 69703 machines.

Sorry it took so long to get to this. I'm rejecting this because of the use of exceptions for flow control. I just pushed a commit that has the same effect: 24fdd7d9cd9df0e19ba4cc18ef6c5d0634e05048

Thanks for that! I'm not sure when to use exceptions and when to use flow control. Which one do you recommend in general?


🐛 Bug Report: Tech Insights plugin - Property 'getScheduledTasks' is missing

📜 Description
We added TechInsights plugin but unfortunately we get an error on yarn tsc
👍 Expected behavior
yarn tsc should pass
👎 Actual Behavior with Screenshots

👟 Reproduction steps

install TechInsights plugin
add minimal setup by following the readme
run yarn tsc

📃 Provide the context for the Bug.

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
Yes I am willing to submit a PR!

You seem to have a lot of duplicate versions of packages. Most importantly, there are two mutually incompatible @backstage/backend-tasks. You may have pulled in a version of tech-insights that was built against the very most recent Backstage, while your overall Backstage installation is at an older version. yarn why @backstage/backend-tasks can give more details on what causes the versions to get pulled in.
It might be worth considering upgrading your overall Backstage version, since you seem to be on a fairly recent one already. The alternative is to choose a slightly older tech-insights, but that is maybe less compelling.

@freben
thank you for response 🙏

You may have pulled in a version of tech-insights that was built against the very most recent Backstage, while your overall Backstage installation is at an older version.

hmm.
Let me try upgrade Backstage and see how it goes.
AFAIK, we're only one minor version down (1.11.1), which was released yesterday and we added the TI plugin apprx. 2 weeks ago. Is there a possibility that TI plugin was built against v 1.12.x at that point?
Is there a way to prevent this in the future?
thank you

You seem to have a lot of duplicate versions of packages.

I am thinking or removing them manually, but not sure if they won't 💣  up 😭

We upgraded Backstage to the latest and all the dependencies for the old version of backstage/backend-tasks
the output of yarn why backstage/backend-tasks
yarn why v1.22.19
[1/4] 🤔  Why do we have the module<EMAIL_ADDRESS>[2/4] 🚚  Initialising dependency graph...
[3/4] 🔍  Finding dependency...
[4/4] 🚡  Calculating file sizes...
=> Found "<EMAIL_ADDRESS>info Reasons this module exists
   - "_project_#backend" depends on it
   - Hoisted from "_project_#backend#@backstage#backend-tasks"
   - Hoisted from "_project_#backend#@backstage#plugin-catalog-backend-module-aws#@backstage#backend-tasks"
   - Hoisted from "_project_#backend#@backstage#plugin-catalog-backend-module-github#@backstage#backend-tasks"
   - Hoisted from "_project_#backend#@backstage#plugin-scaffolder-backend#@backstage#backend-tasks"
   - Hoisted from "_project_#backend#@backstage#plugin-search-backend-node#@backstage#backend-tasks"
   - Hoisted from "_project_#backend#@backstage#plugin-tech-insights-backend#@backstage#backend-tasks"
   - Hoisted from "_project_#backend#@backstage#plugin-tech-insights-node#@backstage#backend-tasks"
   - Hoisted from "_project_#backend#@backstage#backend-common#@backstage#backend-app-api#@backstage#backend-tasks"
   - Hoisted from "_project_#backend#@backstage#backend-common#@backstage#backend-plugin-api#@backstage#backend-tasks"
info Disk size without dependencies: "168KB"
info Disk size with unique dependencies: "13.34MB"
info Disk size with transitive dependencies: "168KB"
info Number of shared dependencies: 271
✨  Done in 1.68s.

As for duplicated packages.
I don't see a way to avoid it keeping in mind that we use backstage's plugins and there reason of duplicated packages seem to be because of the dependencies between them. 🤔


Info related to CI infrastructure setup for Flannel

We wanted some details on how the current CI infrastructure is setup for Flannel, so that we can setup CI infrastructure on z Systems (big endian)?
1.             How frequent the CI runs on average?
2.             What is the recommended H/W and configuration requirement?
3.             Special S/W requirements (if any).
Thanks,
Ryan D'Mello

It's all public. Just take a look at the .travis.yml file.

Once per commit
Whatever travis uses
Whatever travis uses


docs(typo): remove unintended semicolon

https://the-guild.dev/graphql/yoga-server/docs/integrations/integration-with-nextjs#example-1
- ;(async () => {
+ (async () => {

Hi! Thank you for taking the time to contribute here 🙂
This is not an unintended semicolon, removing it actually breaks the code. This is because of JS auto-semicolon feature. We are not manually putting semicolon at the end of our lines here, so JS adds them for us. But sometimes, it doesn't understand where the end of the statement is. It is the case here: if you remove the semicolon, the function returned by createYoga will be executed with the following anonymous function as a parameter.
But I agree this is not very readable. But I would suggest to either not have an IIF, or add all semicolons, which would resolve the ambiguity.

I see, I noticed that no semicolons are used as a convention so I thought it was unintended. But yes, you're correct, not including the semicolon may cause an error with the IIFE. I'll close this pr, thanks for your time!


extensions/media-preview — Lets add (optional) support for autoplaying video and video looping.

RFE for extensions «media-preview» — Lets add (optional) support for autoplaying video and video looping.
It really need for fast preview of lot of small files (video assets, visualizations, … for me — I need this for algorithms visuzalization, lot of small video files, constantly refreshing…)
Looks, it can be done by couple of options «loop video» and «autoplay video» and changing couple of lines in
extensions/media-preview/media/videoPreview.js like this
	video.playsInline = true;
	video.autoplay = setting.video_autoplay;
	video.loop = setting.videoloop;

These options have (unfortunately abandoned) extension «Preview MP4», but will be much better to get it out the box.

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_smiling_face: This feature request received a sufficient number of community upvotes and we moved it to our backlog. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

For verification, the relevant settings are:

mediaPreview.video.autoPlay
mediaPreview.video.loop

@mjbvz is this only for certain video types? I tried testing this with last iteration's release notes and can't see videos autoplaying or looping

This is only when you open a video file in the editor (not videos in the preview)
Try opening a video file by clicking on it in the explorer

ahh that makes sense, thanks for clarifying!


Use Translations

I'm exploring options to improve message customization and localization in our project. Currently, we're using the TextComponent translation tag to handle translations on the client side.
To provide a more flexible solution, I'm considering the following approaches:

Default Minecraft Translations: Use the default Minecraft translations for a base set of messages. This would simplify the translation process for common messages.

User-Defined Translations: Allow users to customize specific messages to fit their preferences or language requirements. This could involve providing a configuration file or in-game interface for users to modify translations.

I would like to take this issue :D

hi can you check this with Arabic and Hebrew as well? (they write the opposite direction if you don't know) thanks

This looks great, and in the future, I may be involved in the translation of Chinese Simplified

i can help for the spanish one


Create XlsxMetadata

Create a class with a method that allow to list sheets (position and label) from a XLSX file

Class created, can be found here


Update README.md

@ReneSkukies  the links currently dont end up in the toolboxes, but go to the images. Can you still fix this?

🎉


Parallelizer: Spurious loop carried depencence error in inlined tasks

Compiling this code
import "regent"

fspace MeshFields {
   x : double -- Unknowns of the implicit solver
}

__demand(__inline)
task rhs( Mesh : region(ispace(int3d), MeshFields),
          elem : int3d(MeshFields, Mesh) )
where
   reads writes (Mesh.x)
do
   var f =  (@elem).x
   return f
end

__demand (__inline)
task foo( Mesh : region(ispace(int3d), MeshFields),
           elem : int3d(MeshFields, Mesh) )
where
   reads writes(Mesh.x)
do
   (@elem).x += 1
   var dx1 = rhs(Mesh, elem)
end

__demand(__cuda, __leaf, __parallel)
task AdvanceMesh( Mesh : region(ispace(int3d), MeshFields) )
where
   reads writes(Mesh.x)
do
   __demand(__openmp)
   for c in Mesh do
      for step = 0, 1000 do
         -- This does not compile
         foo(Mesh, c)
         -- This does
         --Mesh[c].x += 1
         --var dx1 = rhs(Mesh, c)
      end
   end
end

produces the following error
Example2.rg:13: OpenMP code generation failed: found a loop-carried dependence
   var f =  (@elem).x

If the content of the task foo is copied inside the main loop, the error disappears.

Should be fixed by 147fbea7. Could you pull and try again?

Fixed. Thanks


Ubuntu bionic cleanup

I did a test build with bundle exec rake --trace stemcell:build_os_image[ubuntu,bionic,/opt/bosh/tmp/ubuntu-bionic-pr-204.tgz] and that passed.
Is there any CI involved for those kind of PRs ?

@rkoster maybe you could have a look given that you have a similar WIP branch for dropping ixgbevf custom installation?

For context:

Original story from linked branch: https://www.pivotaltracker.com/n/projects/956238/stories/174635234
Branch was never merged and instead the following commit was made against the bionic branch: https://github.com/cloudfoundry/bosh-linux-stemcell-builder/commit/fc0a38a419c3a57a664a8b6459330387bc6240c1

@toabctl https://github.com/cloudfoundry/bosh-linux-stemcell-builder/pull/207 has been merged

Thanks! @toabctl

@rkoster @ramonskie I don't want to complain, but I thought you don't want to merge this PR? Now dracut support got removed for bionic.
Don't get me wrong - I'm happy that it got removed. Just want to make sure that this is really what you wanted to do?!
p.s. https://github.com/cloudfoundry/bosh-linux-stemcell-builder/pull/208 is the dracut removal for ubuntu-jammy/master .

@toabctl yeah we talked it over a bit more and decided it's okey for bionic.


Persist X-Forwarded-Proto header from upstream

Do you want to request a feature or report a bug?
Bug

What did you do?
Spun up a service with an AWS ELB that terminates SSL in front of Traefik. In the below diagram the ELB:

Passes port 80 through so that Traefik issues a 302 redirect to port 443.
Terminates port 443 and passes it to Traefik on port 81, which is configured to pass through to the service.

What did you expect to see?
The X-Forwarded-Proto header from the AWS LB would pass through to the final service as "https", which is what the AWS LB set.
What did you see instead?
Traefik appears to be replacing this header with its own X-Forwarded-Proto header when it passes through port 81. The final service sees "http" for the value of the header and incorrectly assumes that it is being served insecurely.
Output of traefik version: (What version of Traefik are you using?)

1.3.6

Or for the exact image:
traefik:latest@sha256:83dc4274db668b6b0d0685ae53a5517eb8e2245f949e6072747cec428d3faf4a

What is your environment & configuration (arguments, toml, provider, platform, ...)?
From the Docker Swarm stack definition:
app:
    image: traefik:latest
    command: --web --docker --docker.swarmmode --docker.watch --entryPoints='Name:http Address::80 Redirect.EntryPoint:https' --entryPoints='Name:https Address::443 TLS' --entryPoints='Name:internal Address::81' --defaultEntryPoints=http,https --acme.entryPoint=https<EMAIL_ADDRESS>--acme.storage=/etc/traefik/acme/acme.json --acme.onHostRule=true
    ports:
      - 80:80
      - 81:81
      - 443:443
      - 8080:8080
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - acme:/etc/traefik/acme
    deploy:
      mode: global
      placement:
        constraints:
          - node.role == manager

User error. The AWS ELBs were set up with "SSL" => "TCP" protocol termination, which does not add the header. Switching protocols to "HTTPS" => "HTTP" add the header properly.


Deactivate invert image filter for double and float images.

Invert image filter doesn't work with double and float images

Looks fine to me - will merge if no objections at the meeting tomorrow.
@rdebroiz , one point: Could you try to avoid cosmetic changes like the whitespace? I know it shouldn't be there in the first place, and in this case it's not too big of a deal, but it clutters the diffs a bit so it is slightly harder to see where the real changes take place.


The run app pin does not work on USBizi

Pin P0.4 is Run App pin but the firmware is skip this pin and execute application no matter the pin is high or low.

This regressed such that it never runs the app now, except when soft reboot. Disabling functionality for now in 0.9.0, see #204


how  to connect  the  sui wallet  by click "connect button"?

I use
import { JsonRpcProvider, devnetConnection } from<EMAIL_ADDRESS>const provider = new JsonRpcProvider(devnetConnection);
console.log(provider);
I want to use  sui  api  to do  like  this?

what  should  I do ?

You can use a wallet adapter or a connection UI to handle this. We recommend Sui Wallet Kit, which is built for this use-case: https://sui-wallet-kit.vercel.app/


WebpackDevServer API - HMR with async chunks when doing code splitting results in inconsistent chunk names (which makes GET calls to undefined.js)

Do you want to request a feature or report a bug?
Regression bug - as described here: https://github.com/webpack/webpack/issues/433#issuecomment-286803302
What is the current behavior?
When adding HMR support to a project that has async chunks (was imported using syntax-dynamic-import) webpack does not keep the same name of the changed chunk. Therefore calls to x-undefined.js are being made.
For some reason everything seems to be working only when also adding NamedModulesPlugin which is according to the docs optional. It seems it's actually mandatory.
Important Note: I did NOT test it using the CLI option. Everything has been tested using the WebpackDevServer API.
If the current behavior is a bug, please provide the steps to reproduce.
Just add an HMR support to a project by adding:
    filename: '[name]-[chunkhash].js',
    chunkFilename: '[name]-[chunkhash].js',

config.entry.application.unshift('react-hot-loader/patch');
config.entry.application.unshift('webpack/hot/dev-server');
config.entry.application.unshift(`webpack-dev-server/client?${config.output.publicPath}`);

// HMR (Hot Module Replacement) plugins
config.plugins.push(new webpack.HotModuleReplacementPlugin());

Add hot: true to the WebpackDevServer configurations.
The above fails.
Now, try also adding:
config.plugins.push(new webpack.NamedModulesPlugin());

Now everything is working again.
What is the expected behavior?
The expected behavior would be that HMR will work without the need to add NamedModulesPlugin.
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.
Webpack version: 2.3.3
Node.js version: 6.10.1
OS: macOS

@kazazor problem still exists?

Closing due to inactivity. Please test with latest version and feel free to reopen if still regressions. Thanks!

@evenstensberg totally still happening for me
chunkFilename: '[name].[chunkhash:8].chunk.js',
const {supportsWebp} = await import(/* webpackChunkName: "chunk-bar-baz", webpackPrefetch: true */ '../shared/utils')

"webpack": "^4.29.0",

@limeandcoconut Duplicate https://github.com/webpack/webpack-dev-server/issues/1717? If not please open issue in webpack-dev-server with minimum reproducible test repo, thanks!

@evenstensberg  It does not appear to be a duplicate of that. I think it's a duplicate of #8677 (which I just now found). I agree with @maclockard that creating a minimal repo large enough to cause chunking issues using dynamic imports is non-trivial.


Minor bug fix

ibc-setup init fails due to trailing commas in yaml file which is unable to read

the CI seems to be broken here

Thanks for the commit.
For the CI, we ensure there are proper changelog entries when we cut a release, following this pattern: https://github.com/confio/ts-relayer/blob/main/DEVELOPMENT.md#maintain-a-clean-changelog
TL;DR: run yarn changeset and enter some info on this (patch level), so we can include it in the next changelog

Ahh my bad. changeset is interesting, will keep this in mind from next time onwards. Thanks


Update index.html

#16: Added the toggle
#10: Fixed the divs

#16, #10

Why put acquisition stuff on the index.html? Weren't we going to add pages for other encounters? Is this just going to be for acquisition?


SP2019 based transformation do not report as cross-farm in telemetry

Related to _vti_pvt/service.cnf sometimes returning <IP_ADDRESS>12, which flags a transformation to be SP2019 while it's actually SPO. Investigation ongoing.

This is not something to fix in the transformation code base, hence closing this issue


Build(deps-dev): Bump eslint from 8.6.0 to 8.7.0 (#2403)

Pull request opened by the merge tool on behalf of #2403

Merged in ecb9cd72e984de28edee893751a6163eb5bcf4e3


Relationships not displaying correctly in new cayley version

Cayley Forum - https://discourse.cayley.io
Slack - cayleygraph.slack.com, invites: https://cayley-slackin.herokuapp.com

Description
Unable to display relationships correctly. We have a set of entity relations.
When A -->B
and when we query the relation. It would give relation between A and B when we query for A. This is not happening in the latest version of Cayley.
When we give  B , it would give the relation. In previous version that is 7.2 we are getting the results correctly. But in 7.7 we are unable to get this and customers have raised bug
Steps to reproduce the issue:
Create relation  between A and B, A Query for A
Received results:
Getting empty results
{
"result": [
[]
]
}
Expected results:
"result": [
	[
		"test-A",
		"test-B"
	],
	{
		"relation": "DependsOn",
		"source": "test-A",
		"target": "test-B"
	},
	{

Backend database: (database and version)
7,7

Hi is there any update on this?


fix: correct nonexistent fixed-versions

These cases of fixed-version references to versions that don't exist in the APKINDEX were found by in-progress validation logic in wolfictl. In some cases, the versions found have been withdrawn. In other cases, it looks like -r0 was assumed to exist but it didn't at time of entry.
cc: @jonjohnsonjr
Note: This is expected to fail validation because it's modifying existing event data.

Note: This is expected to fail validation because it's modifying existing event data.

🤔


Define behaviour when @LRA annotated method throws an exception

The specification defines that a method annotated with @LRA finishes the LRA (either with complete or cancel). There is not defined what happens when such method is ended by a thrown exception.
It would be good to define this behaviour.
JTA java developers are used to how the JTA works in way that RuntimeException rolls-back the transaction while the checked exceptions do not. The CDI @Transactional defines what are exceptions that rolls-back the transaction then. The similar approach could be taken for @LRA as well.

on discussion on meeting 2019-02-04: any exception thrown from the @LRA annotated method cancel the LRA. The cancelOn/cancelOnFamily controls to cancel the LRA based on the error code returns from the @LRA annotated method which is the REST endpoint.

I was thinking to create a PR on this but I found one case I'm not sure how that should be handled. What if the exception is thrown from the method which does not started the LRA context.
// -> incoming LRA context with already started LRA
@LRA(Type.SUPPORTS)
public void method() {
  throw new RuntimeException();
}

Will this cancel the LRA context which came from outer space? Or throwing the exception will cause to cancel the LRA only when started at the same method?

@ochaloup I believe that depends on the value of the end attribute of the @LRA annotation

If you have non-exception case like microservice A calls a microservice B then
@LRA(Type.REQUIRES_NEW)
public void microserviceAMethod() {
   ClientBuilder.newClient().target(<<microserviceBMethod>>).post();
}

@LRA(Type.SUPPORTS, end = true)
public void microserviceBMethod() {
  // do some business logic
}

The end is by default to true, this fact is emphasized at the microserviceBMethod. When the microserviceBMethod and returns back to microservice B the LRA is not ended. The LRA will be ended at the end of the microserviceAMethod. It means the responsibility for ending the LRA is on he method that started the original context. How is it with exception that would be thrown in microserviceBMethod. Will the microservice B cancel the LRA even it only received the context and the B does not start it? Or it should be responsibility of microservice A (microserviceAMethod to handle the error codes and then decides to throw an exception (and cancel the LRA) or ignore the errors?

I'm not sure about your reasoning of the ending of the LRA. SUPPORTS has the following definition
If called inside a LRA context the managed bean method execution must then continue inside this LRA context.
Since it executes inside the LRA context started by microserviceAMethod, the end means that the microserviceBMethod closes the LRA context which was started by microserviceAMethod.
If you want that microserviceAMethod has complete control over the LRA, the SUPPORTS should be replaced with NOT_SUPPORTED. Then the microserviceAMethod can decide what to do with the LRA based on the return value (including exceptions) it receives from microserviceBMethod.

The only special case is when we throw a WebApplicationException.
In thtat case, we need to take the value of the status (getResponse().getStatus() ) and see if the value is covered by any on the cancelOn or cancelOnFamily values and decide on that if the LRA needs to be cancelled or not.

+1

The decision on the meeting was that

exceptions thrown from the method are not about to be specially handled by the LRA
the default cancelOnFamily will be defined to contain 4xx and 5xx errors
even there is no special handling to be mentioned in the spec, there should be a mentioned that:
-- is expected that by default the RuntimeException is transformed by the JAX-RS exception mapper to the 5xx error code. It's not the defined elsewhere in specification but it's usual behaviour. We expect that the implementation will transform the Exceptions to 5xx code which should cause cancelling the LRA at the end.
-- when the framework itself does not map the exceptions in this way (aka RuntimeException is not mapped to 5xx) it could be required to add separate exception mapping.
-- the user should consider this error code handling especially when he use the MP Fault Tolerance

+1 just one comment:

the default cancelOnFamily will be defined to contain 4xx and 5xx errors

I believe that decision was only 5xx - https://docs.google.com/document/d/1HBPiXpsXcQp9T8JeoT-IDs-EblZX1SxuTV5qjUPzwrM/edit#bookmark=id.bqi49xey9iw9

@xstefank I wanted to mostly clarify what is in spec already (see
https://github.com/eclipse/microprofile-lra/blob/master/api/src/main/java/org/eclipse/microprofile/lra/annotation/LRA.java#L197)
I think the 4xx and 5xx are correct to be default for cancelOnFamily.
If you get 4xx where the error code means bad request or not processable I argue it should be still canceled
https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#4xx_Client_errors
if I summarize my understanding of the cancelOn/cancelOnFamily meaning then (it would be good to be clarified in spec too): the @LRA is the JAX-RS method, if that method returns the paritcular error in the Response then the LRA is cancelled. Otherwise the LRA is finished (completed).
I'm not sure if the 4xx error code should mean completion.

@ochaloup +1

The javadoc for cancelOnFamily says:
     * The cancelOnFamily element can be set to indicate which families of
     * HTTP response codes will cause the current LRA to cancel. By default client
     * errors (4xx codes) and server errors (5xx codes) will result in
     * cancellation of the LRA.

I think the fix should ensure that default corresponds to this javadoc


how to use moveit with gazebo

Description
how to use moveit with gazebo
Your environment

ROS Distro: humble
OS Version:  Ubuntu 22.04
Binary build

Please give me some help
I only found https://github.com/lbr-stack/lbr_fri_ros2_stack

I was thinking of explaining MoveIt 2 & Gazebo (Fortress) integration as a sub-task of porting the Multiple Robot Arms Tutorial to ROS 2. This issue is related. The integration can be separated from the multiple arms tutorial to make it easier to understand. I will be able to dedicate time to this very soon.

thanks， Wish you all the best.


build: Update Vulkan-Headers to 1.3.239

Also update glslang and SPIRV-Headers for the next release.

CI Vulkan-ExtensionLayer build queued with queue ID 6340.

CI Vulkan-ExtensionLayer build # 260 passed.

CI Vulkan-ExtensionLayer build queued with queue ID 6350.

CI Vulkan-ExtensionLayer build # 261 running.

CI Vulkan-ExtensionLayer build # 261 passed.


Updated the comments around client secret.

Addresses #2449

@captainsafia can I get eyes on this because it's helping people not configure swashbuckle to expose client secrets.


Update readme to show -a headers option

Update documentation to include options added by this PR.

Thank you


fix top node output format incorrect

#1111

Hi @wujiangfa-xlauncher , can you open a pull request on the main repo?
We usually merge it to the main repo https://github.com/kubernetes/kubernetes and the mirror the code to this repo.

/check-cla

@lauchokyip Thank you for your reply.

What happened?

@lauchokyip  I see. Thank you

@lauchokyip  https://github.com/kubernetes/kubernetes/pull/105113

/close

Keeping track in this PR https://github.com/kubernetes/kubernetes/pull/105121


Convert between (Int|UInt)(16|32|64) and Data while respecting endianness

@paulrolfe I've added Int16, 32, 64 support as well

retest this please

retest this please

Looks like some tests need to be fixed.

what was the change, ps?

retest this please

retest this please


Meteor 1.3 - React is not defined when using npm React

I'm using React from npm with Meteor 1.3 and am having issues getting FlowRouter + Meteor React Layout working.
Exception from Tracker recompute function:
debug.js:41 ReferenceError: React is not defined
    at FlowRouter.route.action [as _action] (routes.jsx:4)
    at Route.callAction (route.js:51)
    at router.js:447
    at Object.Tracker.nonreactive (tracker.js:589)
    at router.js:431
    at Tracker.Computation._compute (tracker.js:323)
    at Tracker.Computation._recompute (tracker.js:342)
    at Object.Tracker._runFlush (tracker.js:481)
    at Object.Tracker.flush (tracker.js:441)
    at Router._invalidateTracker (router.js:489)

If you import React in my routes.jsx file, you get this
invariant.js:39 Uncaught Error: Invariant Violation: addComponentAsRefTo(...): Only a ReactOwner can have refs.

This is due to the reason that, we've multiple copies on React. Hope you are trying to use React as a node module. Right?
Solution is to create a version of ReactLayout directly loaded from the npm. I'll work on it.

Yep! React as a node module. I figured that was the issue. Thank you!

Should react-mounter be permanently used instead of meteor-react-layout?

Im using beta 4 of Meteor 1.3 and no issues. I doubt its an issue with react layout

Dont install meteor add react if you have done so.

@SylarRuby  I had not. This issue had already been closed. I was just wondering about the status of React Layout vs React Mounter in the future.

Okay. You should not ReactLayout after Meteor 1.3+
Just use react-mounter and get React from NPM.
See: Getting Started with Meteor 1.3 and React

Can you please explain why we shouldn't use ReactLayout with Meteor 1.3? I understand the double-React issue, however I was planning on forking ReactLayout so that it imports React from npm rather than using the meteor package. Are there any other incompatibilities that I should be aware of?
I can't use react-mounter. I've just tried it and it breaks by project since it doesn't have server-side support.
My project used to use FlowRouter SSR + ReactLayout quite happily.
Now I wish to use Meteor 1.3, nom-based React + FlowRouter SSR.
Thanks,
Tim

@timothyarmes react-mounter will be SSR ready soon. (in this week)
And SSR work in the FlowRouter is complete :)

@arunoda
I must worry ?
modules.js:22694 Warning: React attempted to reuse markup in a container but the checksum was invalid. This generally means that you are using server rendering and the markup generated on the server was not what the client was expecting. React injected new markup to compensate which works but you have lost many of the benefits of server rendering. Instead, figure out why the markup being generated is different on the client or server:


Add support for defining local contexts

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

10 of 10 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 94.068%

Totals

Change from base Build<PHONE_NUMBER>:
0.03%

Covered Lines:
616

Relevant Lines:
646

💛  - Coveralls


[Todo] Live reload

It looks like we could dynamically enable live reload using something like this LIVE_RELOAD=... yarn .... This would allows us to opt-in to use of WebSockets based on the user’s preference. Sometimes it can get annoying to use live reloading.
There is some very good documentation here for how to get started with WebSockets: https://github.com/websockets/ws#websocket-compression. What’s left is wiring this up to the emitted app file so that, as we port, we can emit and respond to socket requests to live reload the page.

Reference implementation here: https://github.com/egoist/maho/blob/12cf4eddc6d02e5e655cb22231694cc60b00b5cf/packages/maho/src/node.tsx#L270.

Reference implementation here: https://github.com/egoist/maho/blob/12cf4eddc6d02e5e655cb22231694cc60b00b5cf/packages/maho/src/node.tsx#L270.

Yay!

Yay!


(qbittorrent) Pushing v<IP_ADDRESS> failed

From https://github.com/chocolatey-community/chocolatey-coreteampackages/commit/dc506b9188c45afcf59ecc00365bbcfa42287e89 (@choco‑bot gist):

Ignored

Icon
Name
NuspecVersion
IgnoreMessage

qbittorrent
<IP_ADDRESS>
AU ignored on: System.Management.Automation.RuntimeException: Chocolatey v0.10.15 Attempting to push qbittorrent.<IP_ADDRESS>.nupkg to https://push.chocolatey.org An error has occurred. It's possible the package version already exists on the repository.

Known issue, and the issue is already being tracked in the pinned issue #1217 .
Until the chocolatey.org issue https://github.com/chocolatey/chocolatey.org/issues/613 is fixed, this will continue to happend.
Unfortunately nothing we can do about it, and since it is a duplicate I will be closing this issue.

Duplicate of #1217


Update create-fhir-data.md

Proposal to change "prefis" to "prefix"

Coverage remained the same at 94.353% when pulling e9cb66f616be642a7e54c16bee4888070fce8eae on mwieler:patch-1 into 1eade87b1d937acb760ff91777f0647f2a7d22a6 on medplum:main.


Drop steps, just show the code: Create an ASP.NET Core app with user data protected by authorization

[Enter feedback here]

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

ID: b66f8ffa-699c-8b11-0cab-805f5953805f
Version Independent ID: 7c151ed5-fd78-84fd-a08a-88912990c4ca
Content: Create an ASP.NET Core app with user data protected by authorization
Content Source: aspnetcore/security/authorization/secure-data.md
Product: aspnet-core
Technology: aspnetcore-security
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

Do this in the next upgrade.


I am new here, May I ask How can I compile tesseract 5a on cmake ,it appears ICU and SW issues

The following ICU libraries were not found:
uc (required)
i18n (required)
Failed to find all ICU components (missing: ICU_INCLUDE_DIR ICU_LIBRARY _ICU_REQUIRED_LIBS_FOUND) (Required is at least version "52.1")
Configuring incomplete, errors occurred!

I use cmake 3.16 gui

Please use the user forum for questions.


Error connecting to local node on Debian 11

Describe the bug
Retrying HTTP request for http://localhost:3030 because of error: FetchError: request to http://localhost:3030/ failed, reason: connect ECONNREFUSED ::1:3030
Debian 11
Installed near cli
Ran near-indexer-for-explorer indexer

BLOCKER

@evergreen-trading-systems was it working before with NEAR CLI for you?
@khorolets have you seen such an error?

@evergreen-trading-systems could you give us the near-cli command to run, I can't reproduce it on Mac

@volovyk-s
on Mac
$ NEAR_ENV=local near state test.near
Loaded master account test.near key from /Users/khorolets/.near/validator_key.json with public key = ed25519:C7gcTuvcRKZkucxP2ihFKzTGQ6H2C2m5v8i79Lbk96fB
Account test.near
{
  amount: '999999899999150889875000000000000',
  locked: '53503741786773065593486268425715',
  code_hash: '11111111111111111111111111111111',
  storage_usage: 182,
  storage_paid_at: 0,
  block_height: 30295,
  block_hash: 'C9HtmQh9F79WAv2XKnTCh3DzEEAvBZ1Citd2EsNw8wMp',
  formattedAmount: '999,999,899.999150889875'
}

$ near --version
2.1.1

This command does not work on Debian 11 - NEAR_ENV=local near state test.near

I have tried it on Debian 11 and Arch, works fine, probably your machine setup is the reason.
My output:
serhii@debian11-uni:~/Projects/nearcore$ NEAR_ENV=local near state test.near
Loaded master account test.near key from /home/serhii/.near/validator_key.json with public key = ed25519:3rDbqMNQoaCcPLX86nhozk1EzjKYGydGbUEsjgmji9sw
Account test.near
{
  amount: '1000000000000000000000000000000000',
  locked: '50000970335441577554223744292238',
  code_hash: '11111111111111111111111111111111',
  storage_usage: 182,
  storage_paid_at: 0,
  block_height: 582,
  block_hash: 'CpUN6QPdFkrFUbTJi53SwNyGejWSX4DaV9LcFaZL3Enk',
  formattedAmount: '1,000,000,000'
}

Feel free to reopen if if you will be able to reproduce it on other machines.

please reopen and demonstrate that it works via video

Clearly shows it not working
https://user-images.githubusercontent.com/4870868/142728043-e39f0363-234f-404a-8c09-7c2bb9a08adf.mp4


Support ESLint 8.x

ESLint has released the first beta versions of v8 🎉
https://eslint.org/blog/2021/08/eslint-v8.0.0-beta.0-released
https://eslint.org/blog/2021/08/eslint-v8.0.0-beta.1-released
It would be awesome to have official ESLint 8 support. 👊
I'm happy to help where I can of course 🙂

Hi!
I assume this is what you opened the issue about?
❯ npm i -D eslint-config-prettier
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: undefined@undefined
npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/eslint
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/eslint-config-prettier
npm ERR!   dev eslint-config-prettier@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

Adding --force it manages to install:
❯ npm i -D eslint-config-prettier --force
npm WARN using --force Recommended protections disabled.
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving<EMAIL_ADDRESS>npm WARN Found<EMAIL_ADDRESS>npm WARN node_modules/eslint
npm WARN   dev<EMAIL_ADDRESS>from the root project
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm WARN node_modules/eslint-config-prettier
npm WARN   dev eslint-config-prettier@"*" from the root project
npm WARN
npm WARN Conflicting peer dependency<EMAIL_ADDRESS>npm WARN node_modules/eslint
npm WARN   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm WARN   node_modules/eslint-config-prettier
npm WARN     dev eslint-config-prettier@"*" from the root project

added 1 package, and audited 130 packages in 544ms

17 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

And everything seems to work.
The peer dependency on ESLint is set to >=7.0.0, so it’ll Just Work when ESLint 8.0.0 is released. At some point after that I’ll go through and update this repo and only test with ESLint 8 going forward.
If you know of a peer dependency range that includes pre-releases I’m all ears!

I’m going to close this since ESLint 8.0.0 has been released and eslint-config-prettier works with ESLint 8.0.0.


refresh id_token and access_token if expired for tina cloud calls

This was pretty simple. The access_token contains the client_id and iss (the token issuer). If we have the refresh_token that's really all we need to make a call to get a refreshed access_token and id_token. Before any request is made to Tina Cloud we check if the token is expired, if it is we try to refresh it and swap the tokens.
I also implemented a super quick JWT parsing method because I didn't see a dependency that could parse jwts and I didn't want to add one.
Tested this out by giving my pool 5 minute token expiry and it works pretty well! Feedback welcome, JS is hard.

I'm not sure how to comprehend the e2e test output. But they pass locally 🤷♂

@mittonface There was an issue with running e2e testing in CI. If you merge main into this it should fix it.


Ali : Behavior, Strategy, Implementation: 3 Weeks

Learning Objectives

Priorities: 🥚, 🐣, 🐥, 🐔 (click to learn more)

There is a lot to learn in this repository. If you can't master all the material
at once, that's expected! Anything you don't master now will always be waiting
for you to review when you need it. These 4 emoji's will help you prioritize
your study time and to measure your progress:

🥚: Understanding this material is required, it covers the base skills you'll
need to move on. You do not need to finish all of them but should feel
comfortable that you could with enough time.
🐣: You have started all of these exercises and feel you could complete them
all if you just had more time. It may not be easy for you but with effort you
can make it through.
🐥: You have studied the examples and started some exercises if you had time.
You should have a big-picture understanding of these concepts/skills, but may
not be confident completing the exercises.
🐔: These concepts or skills are not necessary but are related to this module.
If you are finished with 🥚, 🐣 and 🐥 you can use the 🐔 exercises to push
yourself without getting distracted from the module's main objectives.

1. Remix
Practice studying and remixing other people's solutions to coding challenges. Create your own solutions by mixing and matching pieces from other people's code.

🐣 Reconstructing: You can reconstruct a variety of solutions to the same challenge when they are presented as parsons problems.
🐣 Analyzing: You can analyze a function written at your level. This includes:

[ ] Behavior: Write documentation, test cases and use cases to describe the function's behavior.
[ ] Strategy: Describe the function's strategy using plain english.
[ ] Implementation: List the language features in a function and explain how each one is used.
[ ] Small Changes: You can think of 2+ changes to the function's implementation that would not change it's strategy.

🐣 Remixing You can analyze several solutions to the same challenge then ...

[ ] Write: Your own solution by remixing the ones you studied.
[ ] Explain: How the other solutions inspired yours; what ideas did you take from them? what ideas did you not take?
[ ] Analyze: Complete a write-up your own solution as though someone else wrote it.

2. Write

🐣 Function Design:

[ ] Writing Tests: Given a working function, you can write passing test cases to describe it's behavior.
[ ] Writing Functions: You can design multiple solutions to the same code challenge, keeping notes about different experiments you tried along the way.

[ ] 🐣 Generating Documentation: You can write a JSDoc comment for your solutions and run a script to generate markdown documentation.
[ ] 🐣 Fuzz Testing: You write solutions that pass randomly generated test cases.
🐥 Test Driven Development: You can solve open-ended, ambiguous coding challenges at your level:

[ ] Reading Docs: You can understand what the function is supposed to do by reading it's JSDoc description.
[ ] Writing Tests: You can write test cases before there is a function to test.
[ ] Writing Functions: You can write one function that passes the test cases you have prepared (even if it's just 1 test case!).
[ ] Refactoring: You can improve your function's implementation without failing any test cases that were passing.
[ ] Iterative Development: You can repeat the TDD process until you are satisfied with your test cases and solution.

[ ] 🐔 Code Golf: Write your solutions with the fewest characters possible! This won't help you write readable code, but it will make you think deeply about JS, your strategy and implementation.

3. Review

🐣 Continuous Integration: You can check your code's quality before pushing so your CI checks all pass.

[ ] Formatting
[ ] Linting
[ ] Testing

[ ] 🐣 Code Review: You can use a checklist to give a thorough, positive and constructive review of your classmates' solutions.
[ ] 🐔 Code Coverage: You can explain what code coverage is, why it's important, and can write unit tests with 100% code coverage.

my fork of module repository

Learning Objectives

Hi @Ibrahim86Ali , what do you need more time to find what was good and less good?

Hi @Ibrahim86Ali , what do you mean need more time to find what was good and less good?

hi @samirm00  thanks for reviewing my check  what i meant am studying today .js doc ,tests (unit tests), use cases ....so i create the check in because its Thursday,
and i will fill it later with the :
Need Help With
What went well?
What went less well?
Lessons Learned
thanks for understanding

@Ibrahim86Ali  You don't have to do them now, on Thursday.

@Ibrahim86Ali You don't have to do them now, on Thursday.

@Ibrahim86Ali do you need some help?

@bermarte  hi bermarte ... for the being moment  i feel ok with the testing  and who to deep analysing of the behavior of the function and how  to do multi impantation  for the same function ...if wehave a good understanding for the language features (.js)....the only thing is to find the time to practis ....thanks a lot for following up

There's no fork.

There's no fork.
@bermarte  i add it sorry ... i forgot


update sorting filters on user profile page

Sorting filters should include:

Trip Reports written
posts in Random Tracks
Tagged In / @ mentions

Looks good now, thanks!


Error building the repository

Hello,
I am trying to follow the Gemmini ONNX tutorial.
I just run gemmini/scripts/build-onnx-inference.sh that executes the build.sh script on onnxruntime-riscv.
I modified a bit the flags and the one used are the following:
./build.sh --config=Release --cmake_extra_defines onnxruntime_USE_SYSTOLIC=ON onnxruntime_SYSTOLIC_INT8=ON onnxruntime_SYSTOLIC_FP32=OFF

That execution throw an error. The output of the build is next:
[ 34%] Linking CXX static library libonnxruntime_graph.a
[ 34%] Built target onnxruntime_graph
Scanning dependencies of target onnxruntime_providers_systolic
[ 34%] Building CXX object CMakeFiles/onnxruntime_providers_systolic.dir/home/user/Documents/chipyard/generators/gemmini/software/onnxruntime-riscv/onnxruntime/core/providers/systolic/fusion/qlinearadd_relu_fuse.cc.o
[ 34%] Building CXX object CMakeFiles/onnxruntime_providers_systolic.dir/home/user/Documents/chipyard/generators/gemmini/software/onnxruntime-riscv/onnxruntime/core/providers/systolic/fusion/qlinearconv_relu_fuse.cc.o
[ 35%] Building CXX object CMakeFiles/onnxruntime_providers_systolic.dir/home/user/Documents/chipyard/generators/gemmini/software/onnxruntime-riscv/onnxruntime/core/providers/systolic/math/gemm.cc.o
[ 35%] Building CXX object CMakeFiles/onnxruntime_providers_systolic.dir/home/user/Documents/chipyard/generators/gemmini/software/onnxruntime-riscv/onnxruntime/core/providers/systolic/math/matmul.cc.o
[ 35%] Building CXX object CMakeFiles/onnxruntime_providers_systolic.dir/home/user/Documents/chipyard/generators/gemmini/software/onnxruntime-riscv/onnxruntime/core/providers/systolic/math/quantize_linear_matmul.cc.o
[ 35%] Building CXX object CMakeFiles/onnxruntime_providers_systolic.dir/home/user/Documents/chipyard/generators/gemmini/software/onnxruntime-riscv/onnxruntime/core/providers/systolic/nn/conv.cc.o
[ 35%] Building CXX object CMakeFiles/onnxruntime_providers_systolic.dir/home/user/Documents/chipyard/generators/gemmini/software/onnxruntime-riscv/onnxruntime/core/providers/systolic/nn/maxpool.cc.o
[ 35%] Building CXX object CMakeFiles/onnxruntime_providers_systolic.dir/home/user/Documents/chipyard/generators/gemmini/software/onnxruntime-riscv/onnxruntime/core/providers/systolic/nn/qlinearconv.cc.o
/home/user/Documents/chipyard/generators/gemmini/software/onnxruntime-riscv/onnxruntime/core/providers/systolic/nn/qlinearconv.cc: In member function 'virtual onnxruntime::common::Status onnxruntime::systolic::QLinearConv_nhwc::Compute(onnxruntime::OpKernelContext*) const':
/home/user/Documents/chipyard/generators/gemmini/software/onnxruntime-riscv/onnxruntime/core/providers/systolic/nn/qlinearconv.cc:218:29: error: 'class onnxruntime::profiling::Profiler' has no member named 'StartTime'; did you mean 'GetStartTimeNs'?
  218 |       start_time = profiler.StartTime();
      |                             ^~~~~~~~~
      |                             GetStartTimeNs
/home/user/Documents/chipyard/generators/gemmini/software/onnxruntime-riscv/onnxruntime/core/providers/systolic/nn/qlinearconv.cc:252:31: error: 'class onnxruntime::profiling::Profiler' has no member named 'StartTime'; did you mean 'GetStartTimeNs'?
  252 |         start_time = profiler.StartTime();
      |                               ^~~~~~~~~
      |                               GetStartTimeNs
/home/user/Documents/chipyard/generators/gemmini/software/onnxruntime-riscv/onnxruntime/core/providers/systolic/nn/qlinearconv.cc:283:31: error: 'class onnxruntime::profiling::Profiler' has no member named 'StartTime'; did you mean 'GetStartTimeNs'?
  283 |         start_time = profiler.StartTime();
      |                               ^~~~~~~~~
      |                               GetStartTimeNs
/home/user/Documents/chipyard/generators/gemmini/software/onnxruntime-riscv/onnxruntime/core/providers/systolic/nn/qlinearconv.cc: In member function 'virtual onnxruntime::common::Status onnxruntime::systolic::QLinearConv::Compute(onnxruntime::OpKernelContext*) const':
/home/user/Documents/chipyard/generators/gemmini/software/onnxruntime-riscv/onnxruntime/core/providers/systolic/nn/qlinearconv.cc:458:31: error: 'class onnxruntime::profiling::Profiler' has no member named 'StartTime'; did you mean 'GetStartTimeNs'?
  458 |         start_time = profiler.StartTime();
      |                               ^~~~~~~~~
      |                               GetStartTimeNs
/home/user/Documents/chipyard/generators/gemmini/software/onnxruntime-riscv/onnxruntime/core/providers/systolic/nn/qlinearconv.cc:502:33: error: 'class onnxruntime::profiling::Profiler' has no member named 'StartTime'; did you mean 'GetStartTimeNs'?
  502 |           start_time = profiler.StartTime();
      |                                 ^~~~~~~~~
      |                                 GetStartTimeNs
/home/user/Documents/chipyard/generators/gemmini/software/onnxruntime-riscv/onnxruntime/core/providers/systolic/nn/qlinearconv.cc:530:31: error: 'class onnxruntime::profiling::Profiler' has no member named 'StartTime'; did you mean 'GetStartTimeNs'?
  530 |         start_time = profiler.StartTime();
      |                               ^~~~~~~~~
      |                               GetStartTimeNs
make[2]: *** [CMakeFiles/onnxruntime_providers_systolic.dir/build.make:154: CMakeFiles/onnxruntime_providers_systolic.dir/home/user/Documents/chipyard/generators/gemmini/software/onnxruntime-riscv/onnxruntime/core/providers/systolic/nn/qlinearconv.cc.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:1265: CMakeFiles/onnxruntime_providers_systolic.dir/all] Error 2
make: *** [Makefile:163: all] Error 2
Traceback (most recent call last):
  File "/home/user/Documents/chipyard/generators/gemmini/software/onnxruntime-riscv/tools/ci_build/build.py", line 2160, in <module>
    sys.exit(main())
  File "/home/user/Documents/chipyard/generators/gemmini/software/onnxruntime-riscv/tools/ci_build/build.py", line 2086, in main
    build_targets(args, cmake_path, build_dir, configs, num_parallel_jobs, args.target)
  File "/home/user/Documents/chipyard/generators/gemmini/software/onnxruntime-riscv/tools/ci_build/build.py", line 1087, in build_targets
    run_subprocess(cmd_args, env=env)
  File "/home/user/Documents/chipyard/generators/gemmini/software/onnxruntime-riscv/tools/ci_build/build.py", line 591, in run_subprocess
    return run(*args, cwd=cwd, capture_stdout=capture_stdout, shell=shell, env=my_env)
  File "/home/user/Documents/chipyard/generators/gemmini/software/onnxruntime-riscv/tools/python/util/run.py", line 41, in run
    completed_process = subprocess.run(
  File "/home/user/anaconda3/lib/python3.9/subprocess.py", line 528, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['/usr/bin/cmake', '--build', 'build/Release', '--config', 'Release']' returned non-zero exit status 2.
Building against Release
riscv64-unknown-linux-gnu-g++: error: ../..//build/Release/libonnxruntime_test_utils.a: No such file or directory
riscv64-unknown-linux-gnu-g++: error: ../..//build/Release/libonnxruntime_session.a: No such file or directory
riscv64-unknown-linux-gnu-g++: error: ../..//build/Release/libonnxruntime_providers.a: No such file or directory
riscv64-unknown-linux-gnu-g++: error: ../..//build/Release/libonnxruntime_util.a: No such file or directory
riscv64-unknown-linux-gnu-g++: error: ../..//build/Release/libonnxruntime_util.a: No such file or directory
riscv64-unknown-linux-gnu-g++: error: ../..//build/Release/libonnxruntime_providers_systolic.a: No such file or directory
riscv64-unknown-linux-gnu-g++: error: ../..//build/Release/libonnxruntime_flatbuffers.a: No such file or directory
riscv64-unknown-linux-gnu-g++: error: ../..//build/Release/external/re2/libre2.a: No such file or directory
riscv64-unknown-linux-gnu-g++: error: ../..//build/Release/external/onnx/libonnx.a: No such file or directory
riscv64-unknown-linux-gnu-g++: error: ../..//build/Release/external/re2/libre2.a: No such file or directory
make: *** [Makefile:11: ort_test] Error 1
Please ignore any dlopen warning above. Glibc hates being statically linked.

Urgency
High.
System information

Linux Ubuntu-20.04
Python version: 3.9.7
GCC/Compiler version (if compiling from source): riscv64-unknown-linux-gnu-* from the riscv-tools esp-tools branch
GPU model and memory:  Gemmini
Chipyard: 1.6.2 (commit 481398b910fa95ec88dd578c67ba358a4d83129d)
ONNX-runtime-riscv: commit 7bbd0496b579863c6906c0449932ac5ddc4c5357, origin/2021-05-12
Gemmini: commit c47cb7f3eb5c18390f176f3a53c43c8546d487d2

Expected behavior
Successful installation of the repository.

Sorry about that; it seems our subrepos had a version mismatch.
Could you try the latest version of ONNX-Runtime (on branch 2021-12-23)?

With the last version it works fine.
Thank you very much!

Thank you for exposing this issue!


Problem with AD user sign in after password change

v3.2.1 build 6002
When signed in as an AD user and using Ticket Viewer to change password, there appears to be an issue when signing out and signing in again with the new password.  When the new password is entered in the XCreds local login screen the screen goes black for several seconds and then returns without signing in.  If the old password is then entered, sign in succeeds normally.

please test in v4 and reopen if still happens

please test in v4 and reopen if still happens


Added the Mostly Adequate Guide to Functional Programming

Thanks, awesome book by the way! Could you please add it to the book file instead? It's definitely not an interactive thing.

Yeah sure I was just thinking the same thing! Sorry for the mix up!
Thanks, awesome book by the way! Could you please add it to the book file
instead? It's definitely not an interactive thing.
—
Reply to this email directly or view it on GitHub
https://github.com/vhf/free-programming-books/pull/1824#issuecomment-176955334
.


proton.json: Add Proton 6.3 (1580130)

This only adds Proton 6.3 to proton.json.
The default version is unchanged.

FYI: Proton 6.3 seems to have again some huge regressions. Mouse input lag after longer playtime and specifically for ETS2 it broke the virtual desktop for multi monitor setups are some of the newly introduced issues.


Installation error: [InvalidArgumentException] could not find a version of package rubix/ml matching your minimum stability

Last time I tried setting up RubixMl on macOS, I got this error regarding not matching my minimum-stability. I was later able to install it after setting up "minimum-stability:dev" in composer.json.

Now I'm trying to set up RubixMl on a windows machine and I get the same error again.
So far I've tried it with 'composer require rubix/ml:dev-master' and 'composer require rubix/ml:"*" and I'm still not able to successfully install.

I might be missing something or doing something wrong. Can someone help me on this?

This is the composer.json I am using atm @najiagul:
{
    "require": {
        "rubix/ml": "dev-master"
    }
}

Hi @najiagul!
This is because we haven't released a stable version number yet (soon though)
You can either require a specific version in your composer.json file such as 0.1.0-rc5 or dev-master or you could lower your projects stability requirements to dev
    "minimum-stability": "dev",

Let me know if you need any more help getting started!

This is what I modified in my composer.json

It still gave the same error
I then lowered the stability to dev in my composer.lock

This doesn't solve the issue either

Hmmmm interesting @najiagul ... are you able to create one of the example projects with composer?

@andrewdalpino  I just tried the Housing Price Predictor and it was created very smoothly.

If you were able to install the project with no issues, that signals to me that there is something in your composer configuration that is preventing you from installing the package. Since you were able to install the Housing example, could you use the composer.json file from that project as a template for your other projects?

Yes I am using that file now and it works just as fine. Thanks a lot!

@andrewdalpino Do you have any plans when to release a stable version? Currently you could require rubix/ml with a version constraint like *@dev to not having to set the minimum stability to dev for all project dependencies. But in our case we have a plugin which uses rubix/ml for some AI features. Assume this plugin is named example/plugin then you cannot require example/plugin: *@dev in a project - this will not work as long as you do not set minimum-stability to dev. Same for dev-master. See https://github.com/composer/composer/issues/1478 for more details.
So while it currently is possible to include rubix/ml as a project dependency, it is impossible for libraries / plugins which use rubix/mlas a dependency to provide stabe versions.

Hey @BlackbitNeueMedien yes we are currently in the release candidate stage and plan to release 0.1.0 either in the next release or the month after. And yes we are aware of this constraint on packages requiring Rubix ML while we stabilize our public API.
Thanks for the question! Feel free to join our channel on Telegram https://t.me/RubixML

We are now in stable mode!


fix merge bug in dataset.merge

Wrong merge happening. Should be labels not inputs.

Build triggered. sha1 is merged.

Refer to this link for build results (access rights to CI server needed):
/job/nd4j_PR/261/

Build finished. No test results found.


Repo Details screen interface

We need to implement repo's details screen interface based on the latest Figma design.

UPD. Mock design is not final ⚠ It would be modified later on but in PoC scope before the release.


Fix broken query string binding test

This test was relying on the parsing behavior of QueryString, that it
would omit the key and value when the value is empty. The expectations
weren't consistent with other tests for 'empty' values.

FYI only will merge to unblock CI

:shipit: but added suggestions for a quick-n-dirty follow-up.


Regex impaired

So I know nothing about regex, but I'd like to be able to narrow down my searches a little.
How would I go about pulling videos that must contain wordA, but must also not contain wordB?
(e.g.  I want to look for videos where the title contains "linux", but I'm not interested in "kali" linux)

Unfortunately, the YouTube API does not provide support for this.

Sorry, I was wrong. There is support for this:

Your request can also use the Boolean NOT (-) and OR (|) operators to exclude videos or to find videos that are associated with one of several search terms. For example, to search for videos matching either "boating" or "sailing", set the q parameter value to boating|sailing. Similarly, to search for videos matching either "boating" or "sailing" but not "fishing", set the q parameter value to boating|sailing -fishing. Note that the pipe character must be URL-escaped when it is sent in your API request. The URL-escaped value for the pipe character is %7C.

Therefore, if you want to search for "linux", but excluding results that contain "kali", then you can use:
youtube-viewer "linux -kali"


Camera magnifies device rotation on Android React Native webview

Description:
On Android, in React Native's WebView, the polyfill causes the camera to be extremely sensitive to device motion - a slight tilt rotates the scene many times. It otherwise is accurately mapping camera rotation to device rotation - just a multiplier issue.
Rotation works correctly in the component on iOS, and also on the Samsung system web browser.
Is there a field I can adjust to alter the rotation intensity? Or is this a known issue with the React browser on Android?

webvr-polyfill version: 0.10.6
Browser name/version/release channel: React Native (0.55.4) WebView
Operating System: Android 8.0.0

What browser engine is React Native's WebView? There were some regressions in recent Chromium versions that you may be running into: https://github.com/immersive-web/webvr-polyfill/releases/tag/v0.10.3

I re-integrated the polyfill from scratch, and now I can't reproduce the problem - it's working correctly on Android. I'll keep an eye out if it resurfaces.


How do I change the default Chromecast background?

Have you read the Tutorials?
Yes
Have you read the FAQ and checked for duplicate open issues?
Yes
What version of Shaka Player are you using?
3.1.6
Please ask your question
When using the default Cast Receiver ID, the Chromecast initially shows the default "Ready to try Shaka's Chromecast support?" Is it possible to add a custom background?

There's no built-in way to do it. The default cast receiver is meant to be a demo that shows how you can make your own receiver. It's not meant to be a production app, per-se.
I don't see why it would hurt to include an optional flag in the appData passed into the default receiver using shaka.cast.CastSender.setAppData, though. Like, an URL you can provide that will override the images provided in the CSS. The code changes would entirely be in the demo and the default cast receiver, rather than the library proper, so it'd be a fairly safe change.

@theodab I'm not sure we want to support this, since we want to do https://github.com/shaka-project/shaka-player/issues/4214 in the future

I think this team should focus on #4214 and drive users toward styled media receivers once they are more capable and better integrated with Shaka.
In the meantime, you can make whatever changes you want to our demo receiver, or build your own on top of our receiver APIs.  Either way, you'd be publishing a custom receiver.


Missed String's .ToLower(CultureInfo) and .ToUpper(CultureInfo) overloads

http://forums.bridge.net/forum/general/feature-requests/726
A related Bridge2 issue.

i am affraid that we will not implement it because at this moment there is no such possibility in javascript


Confused about prev_action_embedding in dd-ppo

❓ Questions and Help
I notice that input_dim of prev_action_embedding is 5 in dd-ppo.
https://github.com/facebookresearch/habitat-lab/blob/7c4286653211bbfaca59d0807c28bfb3a6b962bf/habitat_baselines/rl/ddppo/policy/resnet_policy.py#L204
In my view, the previous action may be a one-dimension vector or a four-dimension one-hot vector. why do you add one during forwarding ?

0 is given when there is no previous actions, i.e. at the start of the episode.

Thank you for the fast reply!
So prev_action contains "no previous action", "stop", "move_forward", "turn left" and "turn right".
But I am still confused about the code as below:
https://github.com/facebookresearch/habitat-lab/blob/7c4286653211bbfaca59d0807c28bfb3a6b962bf/habitat_baselines/rl/ddppo/policy/resnet_policy.py#L413
Why do you add "1" in this line?
Thanks

prev_actions just contains the previous action, so  "stop", "move_forward", "turn left" and "turn right", which map to [0, 1, 2, 3].  In the case of the start of the episode, the value of that is undefined however.  The +1 shifts all the defined values up 1 and then leaves zero for when it is undefined -- the * masks will make it zero when a given step is the start of an episode.

Thank you!


Gift sats > Share via link:Need a button.

Needs a button, I have shared or something.

And once that is pressed, it goes to the Gifts list

Verified this issue on staging app v2.0.5(381)


Update Fixtures

Have fixtures registered in fixture.js so the whole API can be browsed in one location and the request handling logic is separate.
e.g.
/src/models/fixtures/fixture.js
import fixture from 'can/util/fixture/';
import product from './product';    // product request handler

fixture('GET /api/products/{pc5}', product);

export default fixture;

/src/models/product
import pc18173 from './products/pc18173';

export default function(request) {
  let requestData = request.data || {};

  if(requestData.fields) {
    let pc18173_reduced = {
      pc5: '18173',
      colorid: { }
    };
    let colorid;

    for(colorid in pc18173.colorid) {
      pc18173_reduced.colorid[colorid] = {
        colorid: colorid,
        finish: pc18173.colorid[colorid].finish
      };
    }

    return pc18173_reduced;
  }
  else {
    return pc18173;
  }
}

@Alfredo-Delgado I like that the urls would all be in one place.  A few things to consider:

Often, fixtures are several functions or stores.
These modules wouldn't really be useful on their own.
You wouldn't be able to easily mix-and match fixtures.  Sometimes I might want an "error" case like:

import 'fixtures/players`'
import 'fixtures/teams_cant_update'

To set something up like this, I would have to repeat every url instead of just getting some mixed selection of working and broken fixtures.
Fixtures are a strange thing because they are mostly a side-effect.  I wonder if we should return some artifact.  This might work well with "error" fixtures.

Couldn't your tests request /api/players?teams-cant-update=1 or /api/teams?cant-update=1 and have the logic around which response would be appropriate reside in fixtures/[handler].js?

Maybe, but that's tricker w/ lists of data.  You might want {complete: true} to return data sometimes and not other times.  You wouldn't want someone to go to a special url.


Change Readme git url

Thank you for your upstream version
Fix Build from Source README.md section

Done


Requirements for admin side of application

Requirements for admin-facing functionality are undiscovered.  Are these even necessary?  Or is this application an improved interface for existing administrative functions at the City of Cleveland?

Django has built-in admin functionality so we just need to document its URL and how to get in. We can create admin users with python manage.py createsuperuser.
Ariel, do you remember what the admin URL was? I think we might be able to reach it just by adding /admin/ to the URL.

So we have the admin logins (lots-admin), but the "Download Page" functionality wasn't working, neither was the CSV dump function, which may have been because phone2 was added at some point, but not for all applications and not necessarily in the database yet?


[README][LICENSE] added Crimea to list of prohibited regions

/cc @timanglade

lgtm :+1:
(For interested parties: we’re adding this due to export restrictions around software that contains/calls encryption methods such as Realm.)


Provide direction / inverse option in Transformer.transform

From discussion with @snowman2
Currently the Transformer.transform method only provides the forward transform. But, we could also support the inverse transform.
The proj_trans functions have a direction argument (https://proj4.org/development/reference/functions.html#c.proj_trans)
So it could be an inverse=False|True to be consistent with Proj. Or a direction='forward'|'inverse' to be closer to the proj API, but I think the inverse is nicer.

Thanks!


Module 4 Unit 4

Module: 04
Unit: 4
Task: 02
Step: 03
Description of issue: Step 3 says "Deploy the following ARM templates to create the virtual network, subnets, and VMs needed for this exercise:"
Correction: Virtual networks and subnets are already created in task 1 therefore the correct statement should be "Deploy the following ARM templates to create VMs needed for this exercise:"

Thank you for the feedback. This has been updated.


⚠ Visual-Crew_Builder has degraded performance

In b170a88, Visual-Crew_Builder (https://visual-crew-builder.ai) experienced degraded performance:

HTTP code: 200
Response time: 1360 ms

Resolved: Visual-Crew_Builder performance has improved in 918a746 after 11 minutes.


error loading preference bundle on A12

on A12 iphone xr ios 12.2, preference bundle error when open Choicy in setting

jailbroken by unc0ver 3.7.0~b3


Updated with ros2-control Foxy API

Updated gazebo_ros2_control with the ros2-control Foxy API

joint_limit_interface is unavailable. See this for more details https://github.com/ros-controls/ros2_control/issues/279

NOTE:
ros-foxy-transmission-interface is still not avaiblable, you should include this dependency in your workspace
Signed-off-by: ahcorde<EMAIL_ADDRESS>

@bmagyar and @Karsten1987 do you mind to have a look ?

@bmagyar and @Karsten1987 do you mind to have a look ?

The demo for the velocity controller is not working. The position controller demo works properly.
Steps to reproduce this:

On a terminal execute: ros2 launch gazebo_ros2_control_demos cart_example_velocity.launch.py
On another terminal execute: ros2 run gazebo_ros2_control_demos example_velocity

You will see that the cart is not moving. Digging around a bit, I saw that the node velocity_test_node is publishing to the topic /commands instead of /cart_pole_controller/commands. But even after remapping the topic to the correct one and making sure that the messages are published on the correct topic (ros2 topic echo /cart_pole_controller/commands shows the expected messages), the cart still doesn't move. Am I missing something?

The demo for the velocity controller is not working. The position controller demo works properly.
Steps to reproduce this:

On a terminal execute: ros2 launch gazebo_ros2_control_demos cart_example_velocity.launch.py
On another terminal execute: ros2 run gazebo_ros2_control_demos example_velocity

You will see that the cart is not moving. Digging around a bit, I saw that the node velocity_test_node is publishing to the topic /commands instead of /cart_pole_controller/commands. But even after remapping the topic to the correct one and making sure that the messages are published on the correct topic (ros2 topic echo /cart_pole_controller/commands shows the expected messages), the cart still doesn't move. Am I missing something?

@MartinPeris thank you for testing. This commit should fix the issue https://github.com/ros-simulation/gazebo_ros2_control/pull/44/commits/a69ff7c25d4adc843fd5239c3310f181e5032ba2

@MartinPeris thank you for testing. This commit should fix the issue https://github.com/ros-simulation/gazebo_ros2_control/pull/44/commits/a69ff7c25d4adc843fd5239c3310f181e5032ba2

Thanks for the quick fix! It works :)

Thanks for the quick fix! It works :)

@ahcorde Before merging this PR to the master branch, I think those lines below should use RCLCPP_INFO rather than  RCLCPP_ERROR.
https://github.com/ros-simulation/gazebo_ros2_control/blob/ahcorde%2Fupdate%2Ffoxy/gazebo_ros2_control/src/gazebo_ros2_control_plugin.cpp#L289
https://github.com/ros-simulation/gazebo_ros2_control/blob/ahcorde%2Fupdate%2Ffoxy/gazebo_ros2_control/src/gazebo_ros2_control_plugin.cpp#L453
https://github.com/ros-simulation/gazebo_ros2_control/blob/ahcorde%2Fupdate%2Ffoxy/gazebo_ros2_control/src/gazebo_ros2_control_plugin.cpp#L499
https://github.com/ros-simulation/gazebo_ros2_control/blob/ahcorde%2Fupdate%2Ffoxy/gazebo_ros2_control/src/gazebo_ros2_control_plugin.cpp#L505
https://github.com/ros-simulation/gazebo_ros2_control/blob/ahcorde%2Fupdate%2Ffoxy/gazebo_ros2_control/src/gazebo_ros2_control_plugin.cpp#L513
https://github.com/ros-simulation/gazebo_ros2_control/blob/ahcorde%2Fupdate%2Ffoxy/gazebo_ros2_control/src/gazebo_ros2_control_plugin.cpp#L525

@ahcorde Before merging this PR to the master branch, I think those lines below should use RCLCPP_INFO rather than  RCLCPP_ERROR.
https://github.com/ros-simulation/gazebo_ros2_control/blob/ahcorde%2Fupdate%2Ffoxy/gazebo_ros2_control/src/gazebo_ros2_control_plugin.cpp#L289
https://github.com/ros-simulation/gazebo_ros2_control/blob/ahcorde%2Fupdate%2Ffoxy/gazebo_ros2_control/src/gazebo_ros2_control_plugin.cpp#L453
https://github.com/ros-simulation/gazebo_ros2_control/blob/ahcorde%2Fupdate%2Ffoxy/gazebo_ros2_control/src/gazebo_ros2_control_plugin.cpp#L499
https://github.com/ros-simulation/gazebo_ros2_control/blob/ahcorde%2Fupdate%2Ffoxy/gazebo_ros2_control/src/gazebo_ros2_control_plugin.cpp#L505
https://github.com/ros-simulation/gazebo_ros2_control/blob/ahcorde%2Fupdate%2Ffoxy/gazebo_ros2_control/src/gazebo_ros2_control_plugin.cpp#L513
https://github.com/ros-simulation/gazebo_ros2_control/blob/ahcorde%2Fupdate%2Ffoxy/gazebo_ros2_control/src/gazebo_ros2_control_plugin.cpp#L525

I've just released transmission_interface, https://github.com/ros/rosdistro/pull/28054

I've just released transmission_interface, https://github.com/ros/rosdistro/pull/28054

There are some additional strange behavior on my side, compared to master branch (with ros2_control and controllers set to respective version). The joints are not able to maintain at a certain position. I am using joint_state_controller and joint_trajectory_controller. the hardware interface is hardware_interface/PositionJointInterface.
I have attached the video here (old )(new)
I have also checked that the command that goes in SetPosition() inside write() is the correct value, however the state is not able to maintain the position. It seems to me it's how the communication between ros2_control and gazebo triggering this error.

There are some additional strange behavior on my side, compared to master branch (with ros2_control and controllers set to respective version). The joints are not able to maintain at a certain position. I am using joint_state_controller and joint_trajectory_controller. the hardware interface is hardware_interface/PositionJointInterface.
I have attached the video here (old )(new)
I have also checked that the command that goes in SetPosition() inside write() is the correct value, however the state is not able to maintain the position. It seems to me it's how the communication between ros2_control and gazebo triggering this error.

@Briancbn can you share your config files? Otherwise I can't reproduce it. Probably something wrong there because the rrbot is able to hold the joint positions.

@Briancbn can you share your config files? Otherwise I can't reproduce it. Probably something wrong there because the rrbot is able to hold the joint positions.

It's the same as the universal_robot one
controller.yaml
joint_state_controller:
  ros__parameters:
    type: joint_state_controller/JointStateController
    publish_rate: 100

ur3e_pos_joint_traj_controller:
  ros__parameters:
    type: joint_trajectory_controller/JointTrajectoryController
    joints:
      - ur3e_shoulder_pan_joint
      - ur3e_shoulder_lift_joint
      - ur3e_elbow_joint
      - ur3e_wrist_1_joint
      - ur3e_wrist_2_joint
      - ur3e_wrist_3_joint
    constraints:
      goal_time: 0.6
      stopped_velocity_tolerance: 0.05
      ur3e_shoulder_pan_joint: {trajectory: 0.1, goal: 0.1}
      ur3e_shoulder_lift_joint: {trajectory: 0.1, goal: 0.1}
      ur3e_elbow_joint: {trajectory: 0.1, goal: 0.1}
      ur3e_wrist_1_joint: {trajectory: 0.1, goal: 0.1}
      ur3e_wrist_2_joint: {trajectory: 0.1, goal: 0.1}
      ur3e_wrist_3_joint: {trajectory: 0.1, goal: 0.1}
    stop_trajectory_duration: 0.5
    state_publish_rate: 500
    action_monitor_rate: 10

ur5_pos_joint_traj_controller:
  ros__parameters:
  ...

The xacro file,
<gazebo>
    <plugin name="gazebo_ros2_control" filename="libgazebo_ros2_control.so">
        <robot_sim_type>gazebo_ros2_control/GazeboSystem</robot_sim_type>
        <parameters>$(find <package-name>)/config/controller.yaml</parameters>
    </plugin>
</gazebo>

Please do share the rrbot config with me as well just for reference. Thanks.

It's the same as the universal_robot one
controller.yaml
joint_state_controller:
  ros__parameters:
    type: joint_state_controller/JointStateController
    publish_rate: 100

ur3e_pos_joint_traj_controller:
  ros__parameters:
    type: joint_trajectory_controller/JointTrajectoryController
    joints:
      - ur3e_shoulder_pan_joint
      - ur3e_shoulder_lift_joint
      - ur3e_elbow_joint
      - ur3e_wrist_1_joint
      - ur3e_wrist_2_joint
      - ur3e_wrist_3_joint
    constraints:
      goal_time: 0.6
      stopped_velocity_tolerance: 0.05
      ur3e_shoulder_pan_joint: {trajectory: 0.1, goal: 0.1}
      ur3e_shoulder_lift_joint: {trajectory: 0.1, goal: 0.1}
      ur3e_elbow_joint: {trajectory: 0.1, goal: 0.1}
      ur3e_wrist_1_joint: {trajectory: 0.1, goal: 0.1}
      ur3e_wrist_2_joint: {trajectory: 0.1, goal: 0.1}
      ur3e_wrist_3_joint: {trajectory: 0.1, goal: 0.1}
    stop_trajectory_duration: 0.5
    state_publish_rate: 500
    action_monitor_rate: 10

ur5_pos_joint_traj_controller:
  ros__parameters:
  ...

The xacro file,
<gazebo>
    <plugin name="gazebo_ros2_control" filename="libgazebo_ros2_control.so">
        <robot_sim_type>gazebo_ros2_control/GazeboSystem</robot_sim_type>
        <parameters>$(find <package-name>)/config/controller.yaml</parameters>
    </plugin>
</gazebo>

Please do share the rrbot config with me as well just for reference. Thanks.

Could you please share the rrbot config with me as well just for reference. Thanks a lot!:)

Here it's the PR https://github.com/ros-simulation/gazebo_ros_demos/pull/41

Could you please share the rrbot config with me as well just for reference. Thanks a lot!:)

Here it's the PR https://github.com/ros-simulation/gazebo_ros_demos/pull/41

ROS can't find rrbot_moveit_demo_nodes if I run the rocker or docker commands.
rocker --x11 --nvidia --name gazebo_ros2_control_demo gazebo_ros2_control:latest
Executing command:  docker run -it   --rm    --name gazebo_ros2_control_demo   --gpus all  -e DISPLAY -e TERM   -e QT_X11_NO_MITSHM=1   -e XAUTHORITY=/tmp/.docker.xauth -v /tmp/.docker.xauth:/tmp/.docker.xauth   -v /tmp/.X11-unix:/tmp/.X11-unix   -v /etc/localtime:/etc/localtime:ro    29e3892534f3  Package 'rrbot_moveit_demo_nodes' not found: "package 'rrbot_moveit_demo_nodes' not found, searching: ['/home/ros2_ws/install', '/opt/ros/foxy']"
Does rocker check for packages outside it's container as well?

ROS can't find rrbot_moveit_demo_nodes if I run the rocker or docker commands.
rocker --x11 --nvidia --name gazebo_ros2_control_demo gazebo_ros2_control:latest
Executing command:  docker run -it   --rm    --name gazebo_ros2_control_demo   --gpus all  -e DISPLAY -e TERM   -e QT_X11_NO_MITSHM=1   -e XAUTHORITY=/tmp/.docker.xauth -v /tmp/.docker.xauth:/tmp/.docker.xauth   -v /tmp/.X11-unix:/tmp/.X11-unix   -v /etc/localtime:/etc/localtime:ro    29e3892534f3  Package 'rrbot_moveit_demo_nodes' not found: "package 'rrbot_moveit_demo_nodes' not found, searching: ['/home/ros2_ws/install', '/opt/ros/foxy']"
Does rocker check for packages outside it's container as well?

The rrbot examples are not included in the Dockerfile, You should add the moveit repos and the rrbot packages, I think this Dockerfile may be usefull for you

The rrbot examples are not included in the Dockerfile, You should add the moveit repos and the rrbot packages, I think this Dockerfile may be usefull for you

Probably something wrong there because the rrbot is able to hold the joint positions.

I can verify that it does work properly on rrbot. You can go ahead and merge this. I will need to do some more investigation and get back to you, I am still not clear on what was causing my problem.

Probably something wrong there because the rrbot is able to hold the joint positions.

I can verify that it does work properly on rrbot. You can go ahead and merge this. I will need to do some more investigation and get back to you, I am still not clear on what was causing my problem.

As discussed yesterday on the ros2_control WG, I have removed the PID controllers.
Would you mind taking another look?  @karsten @bmagyar

As discussed yesterday on the ros2_control WG, I have removed the PID controllers.
Would you mind taking another look?  @karsten @bmagyar

@Karsten1987 I got rid of the transmission_interface package.

@bmagyar removed the e-stop too

@ahcorde
line 492  RCLCPP_ERROR  -> RCLCPP_INFO

Basically all demos crash with the following output:
 ➭ ros2 run gazebo_ros2_control_demos example_velocity
[INFO] [1612206600.790995219] [velocity_test_node]: node created
libc++abi.dylib: terminating with uncaught exception of type std::__1::system_error: mutex lock failed: Invalid argument

The cartpole is moving though within Gazebo, so I don't think that's a major issue.
The position example has a weird console output and I don't really understand what the pole is doing (it's bouncing a bunch of time left and right and stops at the origin again).
feedback->desired.velocities :-1
feedback->desired.positions :0.00146672
feedback->desired.velocities :-1
feedback->desired.positions :0.00146672
feedback->desired.velocities :-1
feedback->desired.positions :0.00146672
feedback->desired.velocities :-1
feedback->desired.positions :0.00146672
feedback->desired.velocities :-1
feedback->desired.positions :0.00146672
feedback->desired.velocities :-1
feedback->desired.positions :0.00146672
feedback->desired.velocities :-1
feedback->desired.positions :0.00146672
feedback->desired.velocities :-1
feedback->desired.positions :0.00146672
feedback->desired.velocities :-1
common_result_response time:<PHONE_NUMBER>.215468
SUCCEEDED result code
async_send_goal
libc++abi.dylib: terminating with uncaught exception of type std::__1::system_error: mutex lock failed: Invalid argument

I updated the gazebo_ros_demos ros2 branch to include the ros2_control tag.

@ahcorde  it seems the current gazebo_ros2_control does not support multiple ros2_control tags. Only the joints in the first ros2_control tag are detected.

@JaehyunShim  can you try the last commit https://github.com/ros-simulation/gazebo_ros2_control/pull/44/commits/794da79c0b46a8adc4a7ff909429a69d518eea99?

I'm going to try this today, but for me https://github.com/ros-simulation/gazebo_ros2_control/pull/44#pullrequestreview-575263658 is still an issue.
Just wrapping the code that parses the yaml file with:
if (!impl_->param_file_.empty())
{
  // Code that loads params
}

is enough.
Also, last time I tried, I had error parsing complex yaml files like this one. The double arrays were loaded as string arrays.

I've tested our TIAGo mobile base with diff drive and it worked fine after some fixes to the diff drive controller.

We'll start working on a full TIAGo robot to test JTC and eventually MoveIt!. We're not full time on this, so I expect it to take a few weeks.

Is there anything that can be done for consistency in the controller.yaml file format for real physical robots and simulated robots?
Controllers are spawned in urdf files now but can you make gazebo_ros2_control an executable so you can run it in a launch file as you could in ROS1?

@JaehyunShim can you try the last commit 794da79?

It worked. Thanks!

There are some additional strange behavior on my side, compared to master branch (with ros2_control and controllers set to respective version). The joints are not able to maintain at a non-zero certain position. I am using joint_state_controller and joint_trajectory_controller. the hardware interface is hardware_interface/PositionJointInterface.
I have attached the video here (old )(new) Both models and controller parameters are exactly the same.
I have also checked that the command that goes in SetPosition() inside write() is the correct value, however the state is not able to maintain the position. It seems to me it's how the communication between ros2_control and gazebo triggering this error.
Update: links was wrong updated

I am encountering the same problem actually. How did you fix it?

I am encountering the same problem actually. How did you fix it?

@JaehyunShim Here is my comments https://github.com/ros-simulation/gazebo_ros2_control/pull/44#discussion_r565177746. There are several ways to workaround it. Currently, I created an additional gazebo plugin to help calling SetParam("fmax", 0, <joint-force-limit>) inside the Load() function.

* joint_limit_interface is unavailable. See this for more details [ros-controls/ros2_control#279](https://github.com/ros-controls/ros2_control/issues/279)

@ahcorde Should there be a notice in the doc on the problem that the missingjoint_limit_interface may cause if you would like to make use of the PositionInterface, mainly due to fmax is unset?

@JaehyunShim

1. Is there anything that can be done for consistency in the controller.yaml file format for [real physical robots](https://github.com/ros-controls/ros2_control_demos/blob/master/ros2_control_demo_robot/controllers/rrbot_forward_controller_position.yaml) and [simulated](https://github.com/ros-simulation/gazebo_ros2_control/blob/master/gazebo_ros2_control_demos/config/cartpole_controller.yaml) robots?

2. Controllers are spawned in [urdf files](https://github.com/ros-simulation/gazebo_ros2_control/blob/master/gazebo_ros2_control_demos/urdf/test_cart_position.xacro.urdf#L62) now but can you make gazebo_ros2_control an executable so you can run it in a launch file as you could in [ROS1](https://github.com/ros-industrial/universal_robot/blob/kinetic-devel/ur_gazebo/launch/ur10.launch#L26)?

Regarding this, we're not providing any ROS2 control params through the URDF, and instead use https://github.com/ros-controls/ros2_control/pull/310 to load them once gazebo and the controller manager in it are running. Here you can see the controller params yaml file
I've got a launch file ready but not pushed, hopefully I can push it tonight.

@JaehyunShim and  @v-lopez I unified the yaml file. Can you try it ?

@chapulina, I was able to reproduce the issue in the docker container. The available classes are:
[gzserver-1] [ERROR] [1612347697.537043257] [controller_manager]: available classes:
[gzserver-1] [ERROR] [1612347697.537051929] [controller_manager]: controller_manager/test_controller
[gzserver-1] [ERROR] [1612347697.537056274] [controller_manager]: forward_command_controller/ForwardCommandController
[gzserver-1] [ERROR] [1612347697.537060021] [controller_manager]: joint_state_controller/JointStateController
[gzserver-1] [ERROR] [1612347697.537063475] [controller_manager]: joint_trajectory_controller/JointTrajectoryController
[gzserver-1] [ERROR] [1612347697.537067085] [controller_manager]: velocity_controllers/JointGroupVelocityController
[gzserver-1] [ERROR] [1612347697.537071095] [controller_manager]: Loader for controller 'effort_controllers' not found

I can see that the package effort_controllers was released  but it seems that it not still synchronized.

@v-lopez I think @ahcorde made modifications on corresponding lines in the last commit for the first point.
What I mean by the following

Controllers are spawned in urdf files now but can you make gazebo_ros2_control an executable so you can run it in a launch file as you could in ROS1?

is it is not really intuitive you set which controller you are going to use for your robot in a urdf file. You will have to recompile your package every time you switch to different controllers (or you can compile with the symlink option but still does not look that intuitive). Why does gazebo_ros2_control take this method rather than link?
,.

@Briancbn I still do not understand why I need to additionally add it to my code to make it work whereas the example provided in the gazebo_ros2_control_demos (which uses the same gazebo_ros2_control::GazeboSystem) already works without it.

@JaehyunShim I only find out through experiment. I don't know what is causing this, and why the rrbot is working. Maybe @ahcorde or @chapulina could explain this?

@JaehyunShim or @Briancbn can you open an issue ?


chore: bdd-nh-1585407807 to 0.0.1

chore: Promote bdd-nh-1585407807 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


ci: Add Allure Reporting for test results

Description

Testing

Additional context

Codecov Report

Merging #84 (2a4c289) into main (60c0d8e) will decrease coverage by 2.60%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##              main      #84      +/-   ##
===========================================
- Coverage   100.00%   97.40%   -2.60%
===========================================
  Files           13       13
  Lines          462      462
  Branches        67       67
===========================================
- Hits           462      450      -12
- Misses           0       10      +10
- Partials         0        2       +2

Flag
Coverage Δ

integration
?

unittests
96.96% <ø> (ø)

unittests-3.10
92.42% <ø> (ø)

unittests-3.11
92.42% <ø> (ø)

unittests-3.8
92.42% <ø> (ø)

unittests-3.9
92.42% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 2 files with indirect coverage changes


feat(Dropdown): add upward prop

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1603   +/-   ##
=======================================
  Coverage   99.74%   99.74%
=======================================
  Files         141      141
  Lines        2398     2398
=======================================
  Hits         2392     2392
  Misses          6        6

Impacted Files
Coverage Δ

src/modules/Dropdown/Dropdown.js
100% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Released in<EMAIL_ADDRESS>


Update the label from totallyNotMaster to totallyNotMain

Updating this label to match with other updates from master to main.

Good catch! I only replaced instances that had clean word breaks so it missed spots like this 😅

Good catch! I only replaced instances that had clean word breaks so it missed spots like this 😅


Make sure KafkaSink/KafkaSource dispose properly on shutdown request

Prior to this, the KafkaSource and KafkaSink didn't properly dispose
of the KafkaClient resulting in programs using KafkaSource and
KafkaSink hanging when shutdown was requested.
Also remove temporarily added note in the python celsius-kafka readme
about having to use ctrl-c after shutdown tool.
Resolves #1442

@dipinhora  Small change, otherwise ready to merge

@jtfmumm Thanks for catching that. Fixed.

@SeanTAllen It doesn't seem like Travis ran for this PR. Is this related to the open sourcing of the repo?

Nope. I need to update the travis config to handle this pattern of branch name

@SeanTAllen Is there another branch naming scheme we're supposed to be using?

@dipinhora no. i just opened a PR to address this, you'll want to bring the change from that onto your branch as well.

Yes, I'll rebase once that is merged. Thanks.

@dipinhora can't find the review thing for some reason, works as expected


iOS & Android bug: Please fix difference in signature of onDetection method

The (detection)="OnDetection($event)" method has different signature when called on Android and on IOS.  On Android the barcode is an object which was serialized as a string, on iOS it is a javascript object, see screenshots below.
iOS:

Android:

It would be great to have the iOS variant (javascript object) consistently on both platforms. It would also be great to have typescript typings for the entire barcode object in the event. Currently, the type is simply data: { [key: string]: any };

That's a bug the return value should be any array of objects not strings

Same here, tested on android, data is type

data: { [key: string]: any };


please add "temporary-email.org", "internxt.com"

please add "temporary-email.org", "internxt.com"

Thanks! added temporary-email.org only. I dont see reason for internxt.com to be true.

Hey Also from https://internxt.com/temporary-email
add crankymonkey.info

please add 10minute-email.com

@7c internxt.com
https://internxt.com/temporary-email

added to automation


Run Build Task not running on Linux

VSCode Version: 1.1.0-alpha
OS Version: Ubuntu 16.04

Steps to Reproduce:

Run Build Task (Ctrl+Shift+B or run from F1 menu)

The tasks window opens but the errors are not showing up.

@vsccarl can you please provide the workspace showing this behavior. An easy explanation is that there might not be any problem matchers configured.

I was working with the smoke test repo but I'm not able to repro on the latest build. I'll reopen if any other builds repro.


Avoid transitioning from pinch until all fingers have been released.

This fixes issue #6478:

pinch end is triggered only when both fingers are released
down trigger only happens if we aren't pinching

@puckey, thanks for the pull request! Maintainers, we have a signed CLA from @puckey, so you can review this at any time.
:warning: I noticed that CHANGES.md has not been updated. If this change updates the public API in any way, fixes a bug, or makes any non-trivial update, please add a bullet point to CHANGES.md and comment on this pull request so we know it was updated. For more info, see the Pull Request Guidelines.

I am a bot who helps you make Cesium awesome! Contributions to my configuration are welcome.
:earth_africa: :earth_americas: :earth_asia:

Thanks @puckey!  @emackey can you review?

@puckey thanks again for the pull request!
@emackey is this something you can look at?  It is only a few lines of code.

I do, sorry for the delay.  I need to carve out a bit of time to try this on a touchscreen.

Updated CHANGES.md in a32d774bc01.


MovieCard-Componenet.html

#Successfully completed issue no #740
Please check and merged
Final output something like this.
https://play.tailwindcss.com/SqiPHDQYac

Make rounded corners. That will go better with design system I guess.

https://play.tailwindcss.com/SqiPHDQYac
Will it fine as I have given rounded large.

Make it 2xl as we are using that everywhere.  @Kumar-Ankit56

Make it 2xl as we are using that everywhere. @Kumar-Ankit56

@Rajdip019  changes done

Great work @Kumar-Ankit56

It only works if you hover on the bottom part of the image. But it should be visible while hovering on the whole card. And add some padding below the button as well. @Kumar-Ankit56


Fix TLS configuration for response hijacking.

Fixes https://github.com/docker/docker/issues/19280
Signed-off-by: David Calavera<EMAIL_ADDRESS>

the silliest :pensive:

I've also attached the changelog here to merge all together.

ping @MHBauer @dongluochen :smile:

LGTM

LGTM, testing with engine and it fixes the issue. We should not flag this as fixing it since it won't really be fixed until this is vendored in.

agreed, I've removed the label


Android Kotlin: 10.06 Create a Paint Application in Android.

Description :scroll:

Give a step-by-step tutorial of creating a Paint Application in Android.
Required Documentation or Video or Audio.

Domain of Contribution :bar_chart:

[x] Android Dev (Kotlin)

References :
https://www.geeksforgeeks.org/how-to-create-a-paint-application-in-android/

Please Read it Carefully Before Contributing

Changes should be made in Android_Development_With_Kotlin/ directory under Android_Development_With_Kotlin branch.
Inside Android_Development_With_Kotlin/ directory creates a directory and names it according to the topic ( for this issue 10. Custom Views)
Inside 10. Custom Views/ directory add your task with subtopic number and name and make changes accordingly.
You have to push your PR to the Android_Development_With_Kotlin branch only.
You can take help to the references but don't simply try to copy it. Just explain in your own word.
This issue is for GWOC'21 contributors only.
You need to push in a single commit. If there exists more than one commit then you need to squash your commits into one commit.
Will assign you on a first come first serve basis.
Please try to complete your assigned task within 7 days. If you need some more time then, please inform mentors and supervisors.
If you have two previously assigned issues on Android-Kotlin pending then please first complete them.

Supervisor @rahulsain

Happy Contributing. Best of Luck.:sparkling_heart:

/assign documentation

@sirilalithaadapa hey are you want to work on this issue?

@sirilaalithaadapa @sitamadex11 am sorry I didn't see the earlier messages if this issue is meant to be assigned to someone else , you can un-assign me

close this issue it is merged

close this issue it is merged

let it be open  for audio and video issue

close this issue it is merged

let it be open for audio and video issue

oaky