hide the "reporting diagnostics for module" messages unless --trace or --verify-module are present

/cc @Chris-Hawblitzel

It was only used to decide how to print the "reporting diagnostics" message, in that function, so it became unused after this change.


Pull maven down inside dockerfile

When I set this up, I was using a makefile to handle building ahead of time - building in the container is probably preferable. This fixes that

Ooops, already fixed it, but not commited :D thx Nathan! merging


Timeshift does not work well with zap and the --time option

Hi, this may be expected behaviour based on the documentation, but it seems like zap should be treated differently.
tsp -I dektec -P zap 0x32  -P timeshift --time 10000 -O file output.ts
If the MPTS bit rate is 10 Mbps but the SPTS bit rate is 1 Mbps, it seems like the --time option calculates the buffer size based on the initial bit rate of the MPTS and the buffer will be 10x what you expect. The documentation does indicate that this is case, but I think it would be better in the zap case to use the bitrate of the SPTS.
It is easy to workaround, but I just wanted to point it out.

RTFM is usually the right answer. From the TSDuck user's guide, reference section for tsp in chapter 3:

Bitrate propagation
At any point in the chain, all plugin have some knowledge of the transport stream bitrate, or rendering speed. Some plugins use that bitrate information, some others don’t. The plugin regulate is a typical example. It uses the rendering speed as an information to lower the transmission speed.
As a general rule, tsp collects the input bitrate, either from the input plugin itself which extracts the bitrate from a hardware input device (this is the case for ASI cards for instance) or, if the input plugin is not able to report a bitrate, tsp automatically analyzes PCR's at the output of the input plugin and computes the corresponding bitrate.
Then, the bitrate is transmitted from plugin to plugin.
Some plugins may inadvertently propagate incorrect bitrates while some plugins may force a (correct) recomputation of the bitrate. To illustrate the first case, consider “-I file ... -P zap ...” using sample bitrate values. You read a complete 36 Mb/s input and tsp evaluates this bitrate. Then, -P zap extracts a 4 Mb/s service and removes everything else. But it does not recompute the transport stream bitrate. So, the propagated bitrate information is still 36 Mb/s. If this information is not used downstream in other plugins, we don't care. But if we use the bitrate information in -P regulate -O ip, we will regulate at 36 Mb/s a stream which should be played at 4 Mb/s. This is why, in specific situations like this, we need to recompute the bitrate using -P pcrbitrate before -P regulate.

TSDuck is a toolbox for engineers. Each tool does a specific simple task. Combining them may result in incorrect setup, which can be expected when you want to simulate error conditions. With such low-level tools, the user needs to carefully combine the tools to achieve the expected result.
The plugin zap actually reduces the bitrate by removing packets but does not change the bitrate information. You should add the plugin pcrbitrate to actually recompute the bitrate information which is propagated, resulting in -P zap ... -P pcrbitrate -P timeshift .... Thus, the plugin timeshift will compute its buffer size from the actual bitrate at that point of the chain.


onPress not working while using renderLink

I started wondering, why I can't get the onPress function working. On the moment I got the renderLink function, the onPress isn't available anymore.
 <Autolink                     text="This is the string to parse for urls https://frank/4, phone numbers"                     stripPrefix={true}                     onPress={link => console.log(link)}                     phone={false}                     email={false}                     renderLink={link => {                        tempLink = link;                        tempLink = tempLink                          .substring(tempLink.indexOf("/"))                         .substring(1);                        console.log(tempLink);                        return link.substring(0, link.indexOf("/"));                      }}                     showAlert={false}                   />

Currently, renderLink assumes you're doing a completely custom link implementation, including your own onPress handlers. This provides maximum flexibility but obviously requires a bit more effort to implement.
Take a look at how the default onPress handler looks to see how your version should currently be implemented and let me know if you have suggestions on how to make it easier (while still being flexible).

Did you got any Example how it could work ?

Just as it does in the default onPress handler:
<Autolink
  renderLink={(text, match, index) => (
    <Text
      key={index}
      onPress={() => doSomething(match)}
    >
      {text}
    </Text>
  )}
/>

Ok thank you. That makes a lot of sense. I will think about a better implementation.
My Solution:
<Autolink                     text={this.props.data.text}                     stripPrefix={true}                     phone={false}                     email={false}                     style={{ fontSize: 20, color: "purple" }}                     renderLink={(text, match, index) => {                       return (                         <Text                           key={index}                           style={{ color: "blue", fontSize: 20 }}                           onPress={() => alert(text)}                         >                           {text.substring(0, text.indexOf("/"))}                         </Text>                       );                     }}                     showAlert={false}                   />


Schema version 2

Phase 2 of: #1468
Proposal: gist.github.com/delvedor/eccf0936048dda2ecf0708156a8a726c
This pr generates a new file: schema-v2.json. It has the new structure outlined in the proposal above. A new compiler step has been added to generate the schema v1 as well.

After some more thinking on the proposal, I see a potential issue by considering multiple response definitions as a flat list of equivalent definitions.
Client generators should be able to distinguish the nominal response from non-nominal error responses to represent API endpoints as function/methods that use the language's idiomatic representation of success and failure. That will be function result/exception in Java, a Result that can be either success or failure in Rust, the result, error result pair in Go, etc.
A way to address that is to add a flag on response definitions indicating if they're nominal or not, e.g. nominal: true. It doesn't have to be an enum as languages have a concept of success or failure, but nothing inbetween ("it kinda worked, but not completely").
Now there's also another issue with multiple responses in each category. For example, what should the response type look like for an endpoint that has several nominal responses? Does this introduce a union at a higher level, or should we merge all nominal property responses in a single type?
TL;DR: I'm wondering if we should limit ourselves to only one nominal response (using optional properties if needed) with multiple status codes and encode this constraint in the schema. Errors may not need that constraint as languages often have the ability to return a set of unrelated errors.

Superseded by https://github.com/elastic/elasticsearch-specification/pull/1536.


#2219

Issue #, if available: #2219
Description of changes:
Set missing fields during domain update operation
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Thank you for the changes @acharviakou
/ok-to-test

As I can see one test failed
According to job history https://prow.ack.aws.dev/job-history/s3/ack-prow-logs/pr-logs/directory/opensearchservice-verify-attribution
Previous build failed because of the same error
Job link: https://prow.ack.aws.dev/view/s3/ack-prow-logs/pr-logs/pull/aws-controllers-k8s_opensearchservice-controller/77/opensearchservice-verify-attribution/1844225177622155264
Changes: https://github.com/aws-controllers-k8s/opensearchservice-controller/pull/77
Should I change something?


docs: fix syntax for dirs with slashes

Docs for the fix discovered in https://github.com/infracost/infracost-atlantis/issues/43.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Feel free to take this one over if needed, I wasn't sure if all references need updated.

Thanks @jmreicha yeah this looks great! You're right that all references need updated - just giving it a quick test on my dev Atlantis and then will merge.

Hello Guys
I have a atlantis and infracost running on a VM instead of Docker and I am getting this error:
exit status 2: running "echo /tmp/${BASE_REPO_OWNER}-${BASE_REPO_NAME}-${PULL_NUM}-${WORKSPACE}-${REPO_REL_DIR//\//-}-infracost.json" in "/var/spool/atlantis/repos/a-b-c/base/1152/acc":
sh: 1: Bad substitution

@zohairraza Hello! Thanks for reporting! It seems like the syntax we're using is valid for /bin/bash, however your error message suggests that you run it in /bin/sh which doesn't support some bash functionality. Can you share more where you use these commands? If it's a shell script, for example, you can replace the first line with #!/bin/bash to make it work.

Thanks for responding, yes we figured that out
We have multiple workspaces and somehow atlantis was using /bin/sh
We used this approach to fix it :

also noticed later that show command was necessary in plan
- show
- env:
    name: INFRACOST_OUTPUT
    command: echo /tmp/${BASE_REPO_OWNER}-${BASE_REPO_NAME}-${PULL_NUM}-${WORKSPACE}-$(echo $REPO_REL_DIR | sed "s/\\//-/g")-infracost.json

@zohairraza Awesome! Nice solution! We may need to add a Troubleshooting section to Atlantis docs to make it more visible. Thanks for posting it! 👍
If I may ask about your impressions, did it work as you expected? And were there any other issues with our example to get it working?

Hey sorry for delayed response
Yes it works as expected and it's awesome, just found one issue that I thought could be important to look into.
In GKE, when you add a load balancer via ingress, infracost doesn't recognise the change

@zohairraza No worries! Thank you for letting us know! :) Is it possible to share an example with Terraform resources so we could reproduce the issue and then fix it?

Here is the resource, the ingress is configured via istio
resource "kubernetes_manifest" "ingress" {
manifest = {
"apiVersion" : "networking.k8s.io/v1",
"kind" : "Ingress",
"metadata" : {
"name" : "instrument-gke-ingress-${var.suffix}",
"namespace" : kubernetes_namespace.monitoring.metadata[0].name,
"annotations" : {
"kubernetes.io/ingress.allow-http" : "false",
"kubernetes.io/ingress.class" : "gce",
"kubernetes.io/ingress.global-static-ip-name" : "instrument-ingress-ip-${var.suffix}",
"networking.gke.io/managed-certificates" : "instrument-cert",
"networking.gke.io/v1beta1.FrontendConfig" : "instrument-ingress-frontendconfig-${var.suffix}"
},
},
"spec" : {
"rules" : [
{
"http" : {
"paths" : [
{
"backend" : {
"service" : {
"name" : "grafana",
"port" : {
"number" : 3000
}
}
},
"path" : "/grafana",
"pathType" : "Prefix"
}
        ]
      },
    },
  ]
},

}

@zohairraza Thank you! I'm afraid Infracost doesn't support this resource yet thus it can't show the costs for it. We list currently supported resources here: https://www.infracost.io/docs/supported_resources/google/. Feel free to create a new GH issue requesting this resource support. This way we can get community's attention to get upvotes. We prioritize adding the new resources based on that.


get contents of files opened with gulp.src(..., {read: false});

Hello,
Person new to gulp asking for help. So far I am loving it. I am currently looking to do something a little strange: I would like to open a bunch of files using gulp.src(..., {read: false}), and perform various operations on them, some of which include filtering down which files were included. After a number of operations, I would like to then be able to read the comments, as if I had use gulp.src without the read: false flag. Is there a way to do this?

Consider posting your questions at Stackoverflow, because Github Issue Tracker is not really a platform for help/learn/support questions.


Deploy single file to AppService

Can someone advise on how the best way to deploy a single file to an AppService.
Scenario is a I have two build processes one produces a webjob, the other produces an exe that's going to be invoked; the exe build process is out of my control so I can't easily change it.
So I can have a release that links the two artefacts and deploy the webjob in the normal way, but I can't work out how to get the exe into the AppService.

@phatcher , currently single file deployment (except zip & war) is not supported.
Can you try to copy the exe file to a empty directory and try deploying the same directory to Azure App Service ?

@phatcher , is the issue resolved ?

@phatcher , Closing the thread, as the workaround provided will resolve the issue.
Please feel feel to reopen the thread or create a new one, if required. :)


Where to see event_data in dashboard?

Can't figure out where to see event_data, I'm looking everywhere, also ?view=event in the pages details, I only find the event_name
I tried the following to track events
umami.trackEvent(`Button"`, { type: "signup", userId: 123 });
umami.trackEvent(`Button 2"`, "StriNg");

What am I missing?
Tried to open a Discussion instead but couldn't 🤔 the button is greyed out for me, haha 🤦🏼 just found the checkbox you need to click before you can start a discussion 😅

https://github.com/umami-software/umami/releases/tag/v1.39.0

Thanks, not exactly sure how to use that or I mean I can't see values for example from userId: 123 right?
Maybe funnels or campaign in v2 would bring a way to see which logged-in user is doing what?


Move quadicon rendering to helpers step 3

Small step in cleaning up (and speeding up) the quadicon rendering.
In the need future we need to be able to render quadicons inside JSON-backed GTLs so we will need to be able to send quadicons either as HTML fragments or as JSON to be rendered on the client side.
Also we need to move the logic from views to some classes to better support provider plugability for quadicons.
This PR speeds up the rendering of VM quadicons by 20% measuring the total time for the server to respond for 1000 quadicons.

@mzazrivec, @h-kataria : review, please?
It's step one of refactoring, focus is on properly converting partials to Ruby.

@martinpovolny quadicons are missing on list of services screen

@martinpovolny quadicons are missing on "All Catalog Items" & "All Services" nodes in catalog explorer as well.

@h-kataria : fixed the problem and added a spec for that. Thx!

verified fix, looks good.

@himdel ready to merge, if it looks good to you.


Pull request to help reduce writing multiple @OnShowRationale methods

Added a getPermissionName() method in PermissionRequest interface. Users can now query for what permission the rationale is to be shown.
Please check and pull if good. Thanks!

Two of the tests are failing, which I'm hoping are unrelated to the changes made here.
http://pastie.org/private/4qxmzqwho7vegiso8jtpa

We won't be able to merge pull request that fail test cases. Let me find the issue.
@hotchemi I think we should have --stacktrace option for circle ci. WDYT?

@shiraji u mean travis ci? We can do that.

BTW, why the developer needs to know which permission rationale is shown? Could you give us a sample code that require to call this method? Because if the developer want to differentiate the permission like sample code
    @OnShowRationale({Manifest.permission.READ_CONTACTS, Manifest.permission.WRITE_CONTACTS})
    void showRationaleForContact(PermissionRequest request) {
        showRationaleDialog(R.string.permission_contacts_rationale, request);
    }

Then, the developer should create methods for each permission.
    @OnShowRationale(Manifest.permission.READ_CONTACTS)
    void showRationaleForContact(PermissionRequest request) {
        showRationaleDialog(R.string.permission_contacts_rationale, request);
    }

    @OnShowRationale(Manifest.permission.WRITE_CONTACTS)
    void showRationaleForContact2(PermissionRequest request) {
        showRationaleDialog(R.string.permission_contacts_rationale, request);
    }

Am I missing something?

Yea, travis ci. I was confused with other project.

Sorry, my bad. I was trying to get the tests to run and might have deleted by accident. Were those sources for the tests made by hand? Must have been tedious.
By the way, the reason for this pull request is to be able to avoid writing @OnShowRationale multiple times. The user can:
@OnShowRationale({Manifest.permission.READ_CONTACTS, Manifest.permission.WRITE_CONTACTS})     void showRationaleForContact(PermissionRequest request) {         showRationaleDialog(request.getPermissionName(), request);         //or showRationaleDialog(request); even     }
So the PR can't be merged unless the checks are made to pass?

Well, it's up to other maintainers. They think this function is useful for this project, then yes. However, I personally don't see the point to have this function in order to avoid writing @OnShouRationale, if there is other use case for this, I might agree.

So the PR can't be merged unless the checks are made to pass?

I don't think any of project want to merge pull request that fail test cases.

I guess this is preference over value type thing. I wanted to map the rationale dialog logic in one place and came up with this. PR is already in place, hopefully the maintainers can merge with little to no issue. :P

IMO, I'm not a huge fun of this idea. The reason is it constrains users to implement getPermissionName even if they don't want to do.
The solution is what @shiraji said. When you want to show rationale stuff by each permission, you should request permissions one by one.

And when it comes to test source, yes it's so massive so we're trying to separate to each java file.

The users don't even have to care about getPermissionName(), they get the option if they wish to go that route.

Sorry, but this issue is still there, it always returns only first value.
https://github.com/hotchemi/PermissionsDispatcher/pull/85#discussion_r51228668

Oops. Will get that fixed.

This fixes that. Your call guys.

Now, how the developer knows which permission is to be shown? You return all of them.

Just realized that it fails in another way. The processor seems to work with chunks of permission request rather than the individual permission. A lot more is to be done to achieve this and I underestimated the level of change needed. I'm closing this PR.
By the way, it doesn't return all of them. Just the array from @NeedsPermission.
Thanks for your time guys. Might open up another one next time.

OK, Thanks for your contribution  @aneophyte .


Failed to import -

Failing module

GitHub: https://github.com/my/repo
npm: https://npmjs.com/package/my_package

import { something } from "https://esm.sh/my_module"

Error message
After onload I got this:
/* your error log here */

Additional info

esm.sh version:
Browser version:

@Khalilheyrani6367 kindly fix the issue content and header or close it. Incase this issue isn't fixed under 24 hours, @ije can force-close it.


Maximum call stack size exceeded when webpack making a huge project bundle

Bug report
I upgrade my project from webpack 3 to 4 , this project is very huge, after run 30-40s give me this error, but in a small project it is fine.
What is the current behavior?
Unhandled rejection RangeError: Maximum call stack size exceeded
    at new Function (<anonymous>)
    at AsyncSeriesHookCodeFactory.create (/Users/mobike/Desktop/app-vue/node_modules/tapable/lib/HookCodeFactory.js:24:12)
    at AsyncSeriesHook.compile (/Users/mobike/Desktop/app-vue/node_modules/tapable/lib/AsyncSeriesHook.js:29:18)
    at AsyncSeriesHook._createCall (/Users/mobike/Desktop/app-vue/node_modules/tapable/lib/Hook.js:24:15)
    at AsyncSeriesHook.lazyCompileHook (/Users/mobike/Desktop/app-vue/node_modules/tapable/lib/Hook.js:34:22)
    at Compiler.emitAssets (/Users/mobike/Desktop/app-vue/node_modules/webpack/lib/Compiler.js:311:19)
    at onCompiled (/Users/mobike/Desktop/app-vue/node_modules/webpack/lib/Compiler.js:178:9)
    at hooks.afterCompile.callAsync.err (/Users/mobike/Desktop/app-vue/node_modules/webpack/lib/Compiler.js:500:14)
    at AsyncSeriesHook.eval [as callAsync] (eval at create (/Users/mobike/Desktop/app-vue/node_modules/tapable/lib/HookCodeFactory.js:24:12), <anonymous>:6:1)
    at AsyncSeriesHook.lazyCompileHook [as _callAsync] (/Users/mobike/Desktop/app-vue/node_modules/tapable/lib/Hook.js:35:21)
    at compilation.seal.err (/Users/mobike/Desktop/app-vue/node_modules/webpack/lib/Compiler.js:497:30)
    at AsyncSeriesHook.eval [as callAsync] (eval at create (/Users/mobike/Desktop/app-vue/node_modules/tapable/lib/HookCodeFactory.js:24:12), <anonymous>:6:1)
    at AsyncSeriesHook.lazyCompileHook [as _callAsync] (/Users/mobike/Desktop/app-vue/node_modules/tapable/lib/Hook.js:35:21)
    at hooks.optimizeAssets.callAsync.err (/Users/mobike/Desktop/app-vue/node_modules/webpack/lib/Compilation.js:995:35)
    at AsyncSeriesHook.eval [as callAsync] (eval at create (/Users/mobike/Desktop/app-vue/node_modules/tapable/lib/HookCodeFactory.js:24:12), <anonymous>:6:1)
    at AsyncSeriesHook.lazyCompileHook [as _callAsync] (/Users/mobike/Desktop/app-vue/node_modules/tapable/lib/Hook.js:35:21)

If the current behavior is a bug, please provide the steps to reproduce.
this is my package.json, This project made by vue, I tried delete 3/4 pages of this project, then webpack work well.......
"dependencies": {
"axios": "^0.16.2",
"babel-runtime": "^6.26.0",
"better-scroll": "^0.1.15",
"lodash": "^4.17.4",
"lodash.sortby": "^4.7.0",
"moment": "^2.18.1",
"node.extend": "^2.0.0",
"qs": "^6.5.0",
"request": "^2.83.0",
"throttle-debounce": "^1.0.1",
"tiny-cookie": "^2.1.1",
"vue": "^2.5.2",
"vue-i18n": "^7.3.2",
"vue-infinite-scroll": "^2.0.1",
"vue-multiselect": "^2.1.0",
"vue-router": "^2.6.0",
"vuex": "^2.5.0"
},
"devDependencies": {
"autoprefixer": "^7.1.2",
"babel-core": "^6.22.1",
"babel-eslint": "^7.1.1",
"babel-loader": "^7.1.4",
"babel-plugin-transform-runtime": "^6.22.0",
"babel-preset-env": "^1.3.2",
"babel-preset-stage-2": "^6.22.0",
"babel-register": "^6.22.0",
"chalk": "^2.0.1",
"connect-history-api-fallback": "^1.3.0",
"copy-webpack-plugin": "^4.5.2",
"cos-nodejs-sdk-v5": "1.2.5",
"css-loader": "^0.28.11",
"cssnano": "^3.10.0",
"eslint": "^3.19.0",
"eslint-config-standard": "^6.2.1",
"eslint-friendly-formatter": "^3.0.0",
"eslint-loader": "^2.0.0",
"eslint-plugin-html": "^3.0.0",
"eslint-plugin-promise": "^3.4.0",
"eslint-plugin-standard": "^2.0.1",
"eventsource-polyfill": "^0.9.6",
"exec-cmds": "^1.0.1",
"express": "^4.14.1",
"file-loader": "^1.1.11",
"fix-orientation": "0.0.2",
"friendly-errors-webpack-plugin": "^1.7.0",
"glob": "^7.1.2",
"happypack": "^5.0.0",
"html-webpack-plugin": "^3.2.0",
"http-proxy-middleware": "^0.17.3",
"inline-manifest-webpack-plugin": "^4.0.0",
"ip": "^1.1.5",
"less": "^3.0.4",
"less-loader": "^4.1.0",
"mini-css-extract-plugin": "^0.4.1",
"ndir": "^0.1.5",
"opn": "^5.1.0",
"optimize-css-assets-webpack-plugin": "^4.0.3",
"ora": "^1.2.0",
"px2rem-loader": "^0.1.9",
"rimraf": "^2.6.2",
"semver": "^5.3.0",
"shelljs": "^0.7.6",
"uglifyjs-webpack-plugin": "^1.2.5",
"url-loader": "^1.0.1",
"vue-lazyload": "^1.2.3",
"vue-loader": "^15.2.4",
"vue-multiselect": "^2.0.6",
"vue-style-loader": "^4.1.0",
"vue-template-compiler": "^2.3.3",
"vuex": "^2.5.0",
"webpack": "^4.12.2",
"webpack-cli": "^3.0.8",
"webpack-dev-middleware": "^3.1.3",
"webpack-hot-middleware": "^2.22.2",
"webpack-merge": "^4.1.0"
},
What is the expected behavior?
package everything as I expect

Other relevant information:
webpack version:  4.12.2
Node.js version: 8.11.1
Operating System: mac os
Additional tools:

Thanks for your report. It would be great if you reduce your issue to a small reproducible example. Best put this example into a github repository together with instructions how to get to the problem.

i found this is a html-webpack-html bug, when i have 300+ new HtmlWebpackPlugin() for multiple pages

I'm closing the issue since it is related to html-webpack-html.

any updates on this issue ?
waiting for response


Does all traffic have to go through livekit server?

As the question goes, I ran the test locally and found that all traffic went through the server, even though I had added stun

right, This is what SFU(Selective Forwarding Unit) does. You need client mesh without a server to handle/forward traffic.


cc-wrapper: add support for pacret hardening flag on aarch64

Description of changes
Rather than trying to shovel all these features under a single flag as in #320597, I'm now strongly leaning in the direction of exposing them separately (more on my reasoning @ https://discourse.nixos.org/t/future-design-of-hardening-flags/38826/6?u=ris)
One thing that stood out during the testing of #320597 was how few problems aarch64's pac-ret feature appeared to cause compared to x86's shadow-stacks. So this leading me to fast-tracking support for it.
The gotcha, again, is that I don't have access to one of these processors, so I'm going to need help testing this. Owners of ARM v8.3+ systems doing a bootstrap build of e.g. pkgsExtraHardening.hello on this branch would really be helping us out here. Example systems implementing ARM v8.3+ include AWS Graviton3 or Apple M1+ systems (running linux). The common Ampere Altra systems (including the Nix community builder and Hetzner) do not implement ARM v8.3.
Things done

Built on platform(s)

[ ] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

I built up to pkgsExtraHardening.ffmpeg and all the deps of pkgsExtraHardening.firefox (I'm a bit short on RAM to fully build Firefox without it being too annoying) on a NixOS M1 Pro. I have not been able to identify an issue.

@ofborg eval

Will merge after rebase.

Thanks for all your work on package hardening. Hopefully we can flip more of this stuff on by default in the future.


Recalibrate Lever servo speed

Need to redo the lever servo speed calibration now that the new servos are in place and the tensioning rubber bands help them up.
Important: Perform this test while gripping a cone!  That is the only state we actually care about the lever position.
These telemetry lines can be uncommented to provided the necessary information:
//        telemetry.addData("Lever position: ", robotCfg.scorer.hardware.lever.currentPosition)
//        telemetry.addData("Lever done: ", robotCfg.scorer.hardware.lever.isDone)

"When extending the lever, the telemetry agrees exactly with the motor.  When retracting the lever, the motion finishes about 0.5 seconds before the telemetry indicates that it is done."  This is pretty good.


Feature Request: Run without the current file being linked to a database

My SQL database is at work, but they don't allow me to connect VSCode to the database, so when I'm home I was hoping to format the SQL code using SQL Transformer, but the file is not connected to a database when I'm at home or using VS Code.
Is it possible for this to be able to format even if a SQL database is not attached to the file?
Currently, this feature doesn't work using SQL Transformer. But, 2 extensions that do work even without being attached to a database are:
SQL Beautify - https://marketplace.visualstudio.com/items?itemName=clarkyu.vscode-sql-beautify
and I have seen another but can't find it now. I think the one above uses an NPM package.

I realized that if I highlight the text then use SQL Transformer, then it will format the code, no problem.


Added Video Size on Settings

Fix #667

Thanks for the contribution! There are some changes that i want to make before merging this into the main branch. I will get this merged into main soon


ChartVIew structs not present in beta

v2 ticket
Ticket description:

please check this tutorial https://github.com/AppPear/ChartView/wiki/How-to-create-your-first-chart


Clean up the js

Dear lord... There are a ton of JS files and inline all over the place. The js situation is a mess.
Notes to self (or anyone who wants to clean this up):

All inline styles should go in their own respective files (or at the very least custom.js).
We have included require.js so we should use it.

For the learns:
Require js: http://requirejs.org/docs/start.html#add
The module pattern with JQuery: http://stackoverflow.com/questions/10371539/why-define-anonymous-function-and-pass-jquery-as-the-argument
The module pattern in general: http://addyosmani.com/resources/essentialjsdesignpatterns/book/#modulepatternjavascript

Dually noted Petepete. Imma get on it.

Oh sweet! It's going to be a bit of a chore to organize the code because of how scattered it is right now. LMK if you have questions about js file shit, I just read a lot about it.


(Team3) regex testcases internal merge

Since dataReader is already changed. team3-regex-dataReader no longer needs to exist.
Merge team3-regex-datareader into another branch: team3-regex-testcases.

@zuozhi Please make sure to modularize your PR to make the reviews easier.  Do not give me a big PR :-)

@chenlica I won't push anything to the current Regex Translator PR until we talked on Thursday. Currently I'm fixing bugs, adding more test cases, and doing performance test in team3-regex-testcases branch.

@zuozhi 👍


feat: support humaneval multi-PLE

pls add the related dataset configs here https://github.com/bytedance/SandboxFusion/blob/main/sandbox/configs/local.yaml#L28

pls add the related dataset configs here https://github.com/bytedance/SandboxFusion/blob/main/sandbox/configs/local.yaml#L28

not necessary now...


Ability to dynamically resolve Angular (+ potentially other FW) components used in rich text elements

When richTextResolver is used to generate html with components or directives and then passed to angular using e.g. innerHtml the output is rendered just as html and no components / directives are not resolved.
This behavior is correct because Angular doesn't know how it should resolve components inside html (which is just a string). In order for this to work, developers need to create components / directives dynamically using approach such as https://netbasal.com/dynamically-creating-components-with-angular-a7346f4a982d
We could provide some guidelines of how this might work or release a new Angular specific npm package which could do that automatically.

Resolving to Angular components is not something the SDK would implement directly. It might be possible to use the new https://github.com/kontent-ai/rich-text-resolver-js to resolve the rich text.


Shops not giving items

Hey, there appears to be a problem on Magic 7.9.9 where items purchased via spells inheriting buyshop don't go into your inventory - it takes the cost, but the item is never handed out.
I've been able to reproduce it with the inbuilt Ollivander spell, though I'm not sure if any more are affected.

Yikes! Thanks for pointing that out. That was an embarassingly bad refactor mistake. I just released 7.9.10 as a hotfix.

No worries haha - happens to the best of us!
Thanks once again for the speedy fix :)


Add Markdown markup classifier

The name of the classifier(s) you would like to add:

Topic :: Text Processing :: Markup :: Markdown

Why do you want to add this classifier?
A package that does text processing of Markdown files can reference this classifier. I'm developing a package that needs it.

Thanks!


Priority class calico-priority isn't high enough for the calico-node daemonset

Expected Behavior
The calico-node daemonset should always be scheduled onto a node.
Current Behavior
The calico-node pods aren't always scheduled due to the calico-priority priority class not being higher than system-cluster-critical.
Possible Solution
Use system-node-critical priority class for the calico-node daemonset. Or even better allow the priority classes to be configured so we can use system-cluster-critical for the other Calico components.
Steps to Reproduce (for bugs)
Deploy resources onto the cluster with system-cluster-critical priority to saturate a node, this happens when the resources are in place before the calico-node pod but it should also work to deschedule the pod.
Context
This is currently blocking our adoption of the Tigera operator.
Your Environment
AWS EKS v1.21, v1.20, v1.19 & v1.18

FYI the comment about system-node-critical only being usable in kube-system is no longer correct as of Kubernetes v1.17.

If you are saturating a node with pods all with system-cluster-critical, then won't the system still evict pods, but since everything is system-node-critical then the pods evicted will be randomly chosen? I think the only thing replacing the calico-priority with system-cluster-critical would do is ensure that calico-node isn't the 1st pods evicted when a node is under pressure.
I'm not saying we shouldn't do this but I don't know if it is solving this expected behavior.

The calico-node daemonset should always be scheduled onto a node.

I'd be willing to review a PR with this change. I'm not sure if we can just make this switch directly or need to include checking the kubernetes version of the cluster to continue using calico-priority on K8s older than v1.17.

@tmjd I think the specifics here are that calico-node should use system-node-critical which has a higher priority than system-cluster-critical (used for deployments and stateful sets). If a daemonset can't be scheduled due to a lower priority it stays in the pending state, if it's a deployment then it will cause a node scale out event (if CA or equivalent is supported). In our case we have a set of tainted nodes for our system components which either use no priority class, system-node-critical or system-cluster-critical; if calico-node doesn't use system-node-critical it can't guarantee that it will be scheduled on these nodes.
I think the perfect solution would be to default the Calico components to system-node-critical and system-cluster-critical if the Kubernetes version is v1.17 or greater.

I'm sorry I just understood that there were 2 different system-*-critical priority classes here. Even though in my first message I mentioned them both. I see what you were saying now. I think your suggestion sounds good

I think the perfect solution would be to default the Calico components to system-node-critical and system-cluster-critical if the Kubernetes version is v1.17 or greater.

@tmjd is this something you'd need a PR for or is it something that will be actively looked into?

I would happily review a PR for this change. I added a backlog item for this but am not sure when it will get prioritized.
I did verify we do not need to maintain K8s v1.16 compatibility so it won't be necessary to maintain the previous calico priority class, we can remove that and just use the new system-*-critical classes.  I wanted to pass that information along if you were inclined to submit a PR.

Thanks @tmjd that was literally my next question. I'll create a PR for this, hopefully this week but if not it'll be the week after next due to annual leave.

@tmjd I've opened https://github.com/tigera/operator/pull/1473 to fix this.


Clustered Datastores - Modeling/Inventory Refresh

Return storage pods from the VMwareWebService gem and add to storage inventory.  Also link up hosts to clustered datastores through the datastore.parent property.
ems_folders table now contains the 'datastore' folder with a StorageCluster folder below that:

@miq-bot add-label wip, providers/vmware, enhancement

Looks great for a first pass @agrare

@miq-bot remove-label wip
cc @blomquisg @jrafanie

@agrare I looked into why the UI was displaying the datastore cluster... I believe it's because it's using this code to get the child nodes and isn't excluding them..
https://github.com/ManageIQ/manageiq/blob/e55c2adfbc15dee2b4f7e4d313e2e1b09b027f75/app/controllers/application_controller/tree_support.rb#L414-L488
Will need to do the minimum to that code to get this working but we may have to rewrite/merge that logic with existing tree building code.

@agrare Looks great!  I put a screenshot to my own memory when we come back to this.

@agrare can you fix the rubocop style issues?


feat (docs): added subdomain/region information

My only concern here is that we are removing the details where we a user needs to use <IP_ADDRESS> for Android and/or figure out their ip address to use for iOS when running on a physical device

I think that's preferable. If we need that kind of information that should be in the react native guide or similar (which maybe we need to update?) but I don't think we should have the dnsmasq page or a dedicated page for figuring it out the IP of people's devices.


[Feature] Layernorm Tag

Description
Add tag to layernorm when sequence parallelism is enabled. This will trigger additional allreduce within tensor parallel group in deepspeed.
Checklist

[x] PR's title starts with a category (e.g. [Bugfix], [Model], [Tutorial], etc)
[x] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage
[x] Code is well-documented

Thanks @szhengac


Fix TF/TFlite install order for qemu

This is a duplicate of #8312 for ci_qemu.
Thanks @manupa-arm @leandron @Lunderberg

closing in favor of #8316


Popups do not have any landmark role

Bug Report
Popups render in  without any landmark role. They need to have either region (with aria-label) or complementary role.
Steps
In doc site, open any popup example and click on a trigger to display the popup. Observe rendered DOM structure.
Expected Result
All DOM nodes need to be rendered in a landmark.
Actual Result
Popup does not have any aria role.
Version
0.21.0

this was already fixed. closing.


Mob farm does not work for slime

I tried to us the mob shard on a slime and it worked fine, but then when I put it into the farm it did not work, other entities still worked just not a slime. (I did try looking at the block data but it showed it was active.)

Hello,
I just tried with a slime in a netherite mob farm and everything seems to work. Can you give me more details (type of mob shard used, type of mob farm used) ?

So, I did some testing and it seems that it will only work if you capture the smallest slime (which may be intentional idk).


log level

Changed logging.properties levels from ALL to DEBUG to cut down on verbose catalina.out logging issues.

LGTM! Please consider back porting this to the 1.2.x series, specifically this is important enough to release a 1.2.5... @buggtb @RyanMcDonagh thanks!

righty-o
On Sat, 18 Aug 2018, 04:51 Chris Mattmann<EMAIL_ADDRESS>wrote:

LGTM! Please consider back porting this to the 1.2.x series, specifically
this is important enough to release a 1.2.5... @buggtb
https://github.com/buggtb @RyanMcDonagh
https://github.com/RyanMcDonagh thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/oodt/pull/68#issuecomment-414029967, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAGUeKoi2gZahTQYfsKXxC4aNMqLB37aks5uR481gaJpZM4WByOi
.

--
Spicule Limited is registered in England & Wales. Company Number:
09954122. Registered office: First Floor, Telecom House, 125-135 Preston
Road, Brighton, England, BN1 6AF. VAT No. 251478891.
All engagements
are subject to Spicule Terms and Conditions of Business. This email and its
contents are intended solely for the individual to whom it is addressed and
may contain information that is confidential, privileged or otherwise
protected from disclosure, distributing or copying. Any views or opinions
presented in this email are solely those of the author and do not
necessarily represent those of Spicule Limited. The company accepts no
liability for any damage caused by any virus transmitted by this email. If
you have received this message in error, please notify us immediately by
reply email before deleting it from your system. Service of legal notice
cannot be effected on Spicule Limited by email.

@buggtb can you roll a 1.2.5 with these updates? Then we can upgrade in DRAT...

I shall do just that!
On 31 August 2018 at 15:29:26, Chris Mattmann<EMAIL_ADDRESS>wrote:
@buggtb https://github.com/buggtb can you roll a 1.2.5 with these
updates? Then we can upgrade in DRAT...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/oodt/pull/68#issuecomment-417681817, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAGUeFBtyjt3Uovz54IGb8O3Er0hWa4mks5uWUhEgaJpZM4WByOi
.
--
Spicule Limited is registered in England & Wales. Company Number:
09954122. Registered office: First Floor, Telecom House, 125-135 Preston
Road, Brighton, England, BN1 6AF. VAT No. 251478891.
All engagements
are subject to Spicule Terms and Conditions of Business. This email and its
contents are intended solely for the individual to whom it is addressed and
may contain information that is confidential, privileged or otherwise
protected from disclosure, distributing or copying. Any views or opinions
presented in this email are solely those of the author and do not
necessarily represent those of Spicule Limited. The company accepts no
liability for any damage caused by any virus transmitted by this email. If
you have received this message in error, please notify us immediately by
reply email before deleting it from your system. Service of legal notice
cannot be effected on Spicule Limited by email.


Support Android N (Unicode 9) Emoji

I'd love to see the new Unicode 9 Emoji introduced with Android N in the repo
Hope you'll consider

They were added two days before your post.

Terribly sorry. Didn't see your commit.


docs: fix broken links

What type of PR is this?
(REQUIRED)

documentation

What this PR does / why we need it:
(REQUIRED)

This pull request fixes some broken (404) links.
Which issue(s) this PR fixes:
(REQUIRED)

This pull request is related to https://github.com/urfave/cli/issues/1939 , but this pull request doesn't resolve the issue completely.
Special notes for your reviewer:
(fill-in or delete this section)

Testing
(fill-in or delete this section)

Release Notes
(REQUIRED)

Some links are still broken, but I'm not sure how we should fix them.
$ git ls-files | grep -E "\.md$" | xargs lychee --max-concurrency 10 -a 429
  247/247 ━━━━━━━━━━━━━━━━━━━━ Finished extracting links                                                                                Issues found in 2 inputs. Find details below.

[docs/CHANGELOG.md]:
✗ [404] https://github.com/lynncyrin/ | Failed: Network error: Not Found
✗ [404] https://github.com/urfave/cli/compare/v1.22.4...v1 | Failed: Network error: Not Found
✗ [404] https://github.com/masonj188 | Failed: Network error: Not Found
✗ [404] https://github.com/urfave/891 | Failed: Network error: Not Found

[docs/CONTRIBUTING.md]:
✗ [404] https://github.com/urfave/cli/tree/v1 | Failed: Network error: Not Found

🔍 247 Total (in 12s) ✅ 237 OK 🚫 6 Errors 💤 4 Excluded
💡 There were issues with GitHub URLs. You could try setting a GitHub token and running lychee again.%


Large public data set and modeling inference ingestion

Various large public data sets exist on Kaggle, etc. which may be used with ML pipelines.

determine which data sets would produce large numbers of entries
add logging to pipelines to log the data to FeatureBase
use a visualizer example with the data and include queries that can be run to produce graphs

This is inbound in the /set directory. Insertion was tested to 24M entries.

Will be renaming "set" directories to "bigdata-set".

Replaced by #15


How to disable encryption?

I want to use plain IMAP/SMTP, without encryption. How can I enable this? I always get
Error: cannot connect to IMAP server

Caused by:
    error:1408F10B:SSL routines:ssl3_get_record:wrong version number:ssl/record/ssl3_record.c:331:

despite already having
imap-starttls = false

in my config.

imap-starttls is for using the STARTTLS protocol instead of SSL/TLS. To disable encryption you can use imap-insecure.

I do have imap-insecure = true in my config, so this does not work @soywod

Mmmh strange. Could you share your config (himalaya config, system, os etc)?

Hello,
I meet the same problem. I use MS Office at work, so I set up a davmail gateway on my machine. Everything being in local on my machine, I did not set up any certificate.
mbsync works great with this setup (with SSLType None), I tried to run some IMAP commands directly from telnet, it works well too.
However, himalaya doesn't work. I have the same error message than the first post of this issue and no other error in the debug logs:
$ RUST_LOG=debug himalaya
[2022-03-28T14:26:52Z INFO  himalaya::compl::compl_args] entering completion command matcher
[2022-03-28T14:26:52Z INFO  himalaya::config::deserialized_config] begin: try to parse config from path
[2022-03-28T14:26:52Z DEBUG himalaya::config::deserialized_config] path: None
[2022-03-28T14:26:52Z INFO  himalaya::config::deserialized_config] end: try to parse config from path
[2022-03-28T14:26:52Z INFO  himalaya::config::account_config] begin: parsing account and backend configs from config and account name
[2022-03-28T14:26:52Z DEBUG himalaya::config::account_config] account name: "default"
[2022-03-28T14:26:52Z INFO  himalaya::config::account_config] end: parsing account and backend configs from config and account name
[2022-03-28T14:26:52Z INFO  himalaya::backends::imap::imap_args] entering imap command matcher
[2022-03-28T14:26:52Z INFO  himalaya::config::account_args] >> account command matcher
[2022-03-28T14:26:52Z INFO  himalaya::config::account_args] << account command matcher
[2022-03-28T14:26:52Z INFO  himalaya::mbox::mbox_args] entering mailbox command matcher
[2022-03-28T14:26:52Z INFO  himalaya::msg::msg_args] entering message command matcher
[2022-03-28T14:26:52Z INFO  himalaya::msg::msg_args] default list command matched
[2022-03-28T14:26:52Z DEBUG himalaya::msg::msg_handlers] page size: 50
[2022-03-28T14:26:52Z DEBUG himalaya::backends::imap::imap_backend] create TLS builder
[2022-03-28T14:26:52Z DEBUG himalaya::backends::imap::imap_backend] insecure: false
[2022-03-28T14:26:52Z DEBUG himalaya::backends::imap::imap_backend] create client
[2022-03-28T14:26:52Z DEBUG himalaya::backends::imap::imap_backend] host: localhost
[2022-03-28T14:26:52Z DEBUG himalaya::backends::imap::imap_backend] port: 1143
[2022-03-28T14:26:52Z DEBUG himalaya::backends::imap::imap_backend] starttls: false
Error: cannot connect to IMAP server

Caused by:
    error:1408F10B:SSL routines:ssl3_get_record:wrong version number:ssl/record/ssl3_record.c:331:

I set up imap-insecure = true in my configuration, however, according to the wiki, imap-insecure allows invalid certificates, does it work with no certificate?
Finally, I have the same problem for sending mails:
$ himalaya write
(s)end, (e)dit, (l)ocal/(r)emote draft or (d)iscard? s
Error: Connection error: error:1408F10B:SSL routines:ssl3_get_record:wrong version number:ssl/record/ssl3_record.c:331:

Caused by:
    0: error:1408F10B:SSL routines:ssl3_get_record:wrong version number:ssl/record/ssl3_record.c:331:
    1: error:1408F10B:SSL routines:ssl3_get_record:wrong version number:ssl/record/ssl3_record.c:331:
    2: error:1408F10B:SSL routines:ssl3_get_record:wrong version number:ssl/record/ssl3_record.c:331:

(RUST_LOG=debug doesn't show anything interesting).

OS: Arch Linux (5.16.16-arch1-1)
davmail: 6.0.1
himalaya: 0.5.10 (from community/himalaya)
himalaya configuration:

name = "Pierre-Albéric TROUPLIN"
downloads-dir = "/home/pat/tmp"

[work]
default = true
email =<EMAIL_ADDRESS>
smtp-host = "localhost"
#smtp-host = "<IP_ADDRESS>"
smtp-port = 1025
smtp-login =<EMAIL_ADDRESS>smtp-passwd-cmd = "bw get password mail.work.com"
smtp-insecure = true

imap-host = "localhost"
#imap-host = "<IP_ADDRESS>"
imap-port = 1143
imap-login =<EMAIL_ADDRESS>imap-passwd-cmd = "bw get password mail.work.com"
imap-insecure = false

+1

It looks like message never arrived, sorry for the delay. Indeed we miss a config option to disable SSL. For now, even the insecure option still uses the SSL module. I will try to add it ASAP.

I think you right. Even if insecure is on, the TLS layer is still used,
which leads to openssl runtime errors. I could introduce a new option
imap-ssl at true by default, and if imap-ssl and imap-starttls
are false then encryption is disabled. What do you think?
On 28 Mar 2022, at 16:53 (+0200), soywod/himalaya wrote:

Hello,
I meet the same problem. I use MS Office at work, so I set up a davmail gateway on my machine. Everything being in local on my machine, I did not set up any certificate.
mbsync works great with this setup (with SSLType None), I tried to run some IMAP commands directly from telnet, it works well too.
However, himalaya doesn't work. I have the same error message than the first post of this issue and no other error in the debug logs:
$ RUST_LOG=debug himalaya
[2022-03-28T14:26:52Z INFO  himalaya::compl::compl_args] entering completion command matcher
[2022-03-28T14:26:52Z INFO  himalaya::config::deserialized_config] begin: try to parse config from path
[2022-03-28T14:26:52Z DEBUG himalaya::config::deserialized_config] path: None
[2022-03-28T14:26:52Z INFO  himalaya::config::deserialized_config] end: try to parse config from path
[2022-03-28T14:26:52Z INFO  himalaya::config::account_config] begin: parsing account and backend configs from config and account name
[2022-03-28T14:26:52Z DEBUG himalaya::config::account_config] account name: "default"
[2022-03-28T14:26:52Z INFO  himalaya::config::account_config] end: parsing account and backend configs from config and account name
[2022-03-28T14:26:52Z INFO  himalaya::backends::imap::imap_args] entering imap command matcher
[2022-03-28T14:26:52Z INFO  himalaya::config::account_args] >> account command matcher
[2022-03-28T14:26:52Z INFO  himalaya::config::account_args] << account command matcher
[2022-03-28T14:26:52Z INFO  himalaya::mbox::mbox_args] entering mailbox command matcher
[2022-03-28T14:26:52Z INFO  himalaya::msg::msg_args] entering message command matcher
[2022-03-28T14:26:52Z INFO  himalaya::msg::msg_args] default list command matched
[2022-03-28T14:26:52Z DEBUG himalaya::msg::msg_handlers] page size: 50
[2022-03-28T14:26:52Z DEBUG himalaya::backends::imap::imap_backend] create TLS builder
[2022-03-28T14:26:52Z DEBUG himalaya::backends::imap::imap_backend] insecure: false
[2022-03-28T14:26:52Z DEBUG himalaya::backends::imap::imap_backend] create client
[2022-03-28T14:26:52Z DEBUG himalaya::backends::imap::imap_backend] host: localhost
[2022-03-28T14:26:52Z DEBUG himalaya::backends::imap::imap_backend] port: 1143
[2022-03-28T14:26:52Z DEBUG himalaya::backends::imap::imap_backend] starttls: false
Error: cannot connect to IMAP server

Caused by:
 error:1408F10B:SSL routines:ssl3_get_record:wrong version number:ssl/record/ssl3_record.c:331:

I set up imap-insecure = true in my configuration, however, according to the wiki, imap-insecure allows invalid certificates, does it work with no certificate?
Finally, I have the same problem for sending mails:
$ himalaya write
(s)end, (e)dit, (l)ocal/(r)emote draft or (d)iscard? s
Error: Connection error: error:1408F10B:SSL routines:ssl3_get_record:wrong version number:ssl/record/ssl3_record.c:331:

Caused by:
 0: error:1408F10B:SSL routines:ssl3_get_record:wrong version number:ssl/record/ssl3_record.c:331:
 1: error:1408F10B:SSL routines:ssl3_get_record:wrong version number:ssl/record/ssl3_record.c:331:
 2: error:1408F10B:SSL routines:ssl3_get_record:wrong version number:ssl/record/ssl3_record.c:331:

(RUST_LOG=debug doesn't show anything interesting).

OS: Arch Linux (5.16.16-arch1-1)
davmail: 6.0.1
himalaya: 0.5.10 (from community/himalaya)
himalaya configuration:

name = "Pierre-Albéric TROUPLIN"
downloads-dir = "/home/pat/tmp"

[work]
default = true
email =<EMAIL_ADDRESS>
smtp-host = "localhost"
#smtp-host = "<IP_ADDRESS>"
smtp-port = 1025
smtp-login =<EMAIL_ADDRESS>smtp-passwd-cmd = "bw get password mail.work.com"
smtp-insecure = true

imap-host = "localhost"
#imap-host = "<IP_ADDRESS>"
imap-port = 1143
imap-login =<EMAIL_ADDRESS>imap-passwd-cmd = "bw get password mail.work.com"
imap-insecure = false

--
Reply to this email directly or view it on GitHub:
https://github.com/soywod/himalaya/issues/347#issuecomment-1080756012
You are receiving this because you modified the open/close state.
Message ID: @.***>

--
Cordialement
Clément DOUIN
Développeur Web Full-Stack
https://soywod.me

Added the option imap-ssl and smtp-ssl in the last release v0.6.1 :tada:


Using a default relay server is potentially dangerous or unreliable

Hey! I think as a good suggestion to solve the above, one of the two following could be done:

Remove the default relay (not as preferable, which is understandable!)
Put it behind a flag (--use-default-relay)

I brought up this exact issue with https://github.com/schollz/croc/issues/277 but as you see the author has simply deleted the issue. Huge red flag to me.
Their reply was simply:

See https://github.com/schollz/croc/blob/master/LICENSE re your questions

(GitHub is setup to send emails for any notifications for me, so I was able to save that.)
and then closed and deleted the issue.
croc says it takes inspiration from magic-wormhole, I hope this was not part of it :laughing:

Please explain how the usage of the relay server might be dangerous
How does removing the relay server mitigate this issue? Wormhole still needs one for functioning in many cases.
How can the user experience not be massively downgraded by any fixes for this issue?

You may want to look into #150 and other related issues discussing this problem.
P.S.: You'll get responses to your issues about as good and polite as the issue itself.

@lf94 thanks for the note!
There's a pretty direct usability/security tradeoff here, for sure, but I think it comes out in favor of continuing to use a baked-in default relay server.
The usability side of the tradeoff is:
The wormhole codes can be so short only because they assume both sides already have a common relay through which they can find each other. Within the context of that shared server, they only need a single number (the "4" in 4-purple-horseshoe) to talk to each other, as opposed to anyone else who is using the server at the same time. If we couldn't assume that, the code would need to include a hostname too (and a port number if it wasn't a default). I feel that would make the codes much more difficult to recite and transcribe, because hostnames are not created with phonetic distinguishability in mind.
Plus, you must actually have a relay server to use, and it must have a public IP address. So before I can send you a file, I'd have to either choose a pre-existing relay server (and include its hostname in the code I tell you), or run one myself, which means renting a VPS somewhere, and/or registering a domain name, which is far beyond what a casual user can be expected to do.
The security side of the tradeoff is:
No matter which relay server you end up using, that server will be able to see the ciphertext of the messages you exchange. They'll be able to see your IP address, and that of your recipient (unless you use --tor). They can prevent your transfer from happening, by dropping or corrupting your messages.
If your connection happens to go through the transit helper as well (e.g. if neither you or your recipient has a public IP address), the transit helper gets to learn the same things, plus they learn the number of bytes you're transferring.
However, the protocol is designed to ensure that neither one can see the plaintext of your messages, modulo the well-documented "one guess per transfer" attack against the low-entropy wormhole code. The server gets no more power than an attacker who has taken over your local network, or the coffee-shop WiFi you're using. Unless you've done something unwise (and kinda anti-social) like running wormhole send in a script that automatically retries upon failure, you and your recipient will almost certainly give up on magic-wormhole well before this attacker has a reasonable chance of success, because they have a 65535-in-65536 chance of getting it wrong, and each time they guess wrong, you have to re-start the whole process with a new wormhole code.
Using your own relay server prevents my relay server from mounting this sort of attack, but it doesn't protect you against that coffee-ship WiFi attacker, or someone who manages to compromise your relay server. It's also not what protects your friends (whom you've invited to use your relay server) against you: that protection comes from the protocol and the cryptography, and is the same thing that protects you against me (as the operator of the default relay server).
So, given that using a non-default server makes the codes much much harder to convey from the human sender to the human recipient, and (I feel) doesn't improve the security significantly, I think the best approach is the one we're using: a baked-in default, with an easy way to override it if that's your thing (wormhole --relay-url=YOURRELAY, or set the $WORMHOLE_RELAY_URL environment variable).
@lf94 does that explanation feel ok to you?

@lf94 thanks for the note!
There's a pretty direct usability/security tradeoff here, for sure, but I think it comes out in favor of continuing to use a baked-in default relay server.
The usability side of the tradeoff is:
The wormhole codes can be so short only because they assume both sides already have a common relay through which they can find each other. Within the context of that shared server, they only need a single number (the "4" in 4-purple-horseshoe) to talk to each other, as opposed to anyone else who is using the server at the same time. If we couldn't assume that, the code would need to include a hostname too (and a port number if it wasn't a default). I feel that would make the codes much more difficult to recite and transcribe, because hostnames are not created with phonetic distinguishability in mind.
Plus, you must actually have a relay server to use, and it must have a public IP address. So before I can send you a file, I'd have to either choose a pre-existing relay server (and include its hostname in the code I tell you), or run one myself, which means renting a VPS somewhere, and/or registering a domain name, which is far beyond what a casual user can be expected to do.
The security side of the tradeoff is:
No matter which relay server you end up using, that server will be able to see the ciphertext of the messages you exchange. They'll be able to see your IP address, and that of your recipient (unless you use --tor). They can prevent your transfer from happening, by dropping or corrupting your messages.
If your connection happens to go through the transit helper as well (e.g. if neither you or your recipient has a public IP address), the transit helper gets to learn the same things, plus they learn the number of bytes you're transferring.
However, the protocol is designed to ensure that neither one can see the plaintext of your messages, modulo the well-documented "one guess per transfer" attack against the low-entropy wormhole code. The server gets no more power than an attacker who has taken over your local network, or the coffee-shop WiFi you're using. Unless you've done something unwise (and kinda anti-social) like running wormhole send in a script that automatically retries upon failure, you and your recipient will almost certainly give up on magic-wormhole well before this attacker has a reasonable chance of success, because they have a 65535-in-65536 chance of getting it wrong, and each time they guess wrong, you have to re-start the whole process with a new wormhole code.
Using your own relay server prevents my relay server from mounting this sort of attack, but it doesn't protect you against that coffee-ship WiFi attacker, or someone who manages to compromise your relay server. It's also not what protects your friends (whom you've invited to use your relay server) against you: that protection comes from the protocol and the cryptography, and is the same thing that protects you against me (as the operator of the default relay server).
So, given that using a non-default server makes the codes much much harder to convey from the human sender to the human recipient, and (I feel) doesn't improve the security significantly, I think the best approach is the one we're using: a baked-in default, with an easy way to override it if that's your thing (wormhole --relay-url=YOURRELAY, or set the $WORMHOLE_RELAY_URL environment variable).
@lf94 does that explanation feel ok to you?

That explanation is excellent. Thank you for taking the time to provide such educating documentation to users. You can close this issue :slightly_smiling_face:

That explanation is excellent. Thank you for taking the time to provide such educating documentation to users. You can close this issue :slightly_smiling_face:

Awesome, thanks! Will do.

Awesome, thanks! Will do.


Module not found: Error: Can't resolve 'child_process' in 'C:\QFL-Latest\node_mo dules\clipboardy\node_modules\execa'

Module not found: Error: Can't resolve 'child_process' in 'C:\QFL-Latest\node_mo
dules\clipboardy\node_modules\execa'

How are you running this? child_process is a built in module in Node.js.

I am using angular cli project. I am giving "npm install clipboardy --save", then in my angular-cli.json inside scripts tag i am including clipboardy/index as
"scripts": [
"../node_modules/jquery/dist/jquery.min.js",
"../node_modules/tether/dist/js/tether.min.js",
"../node_modules/bootstrap/dist/js/bootstrap.min.js",
"../node_modules/lodash/lodash.js",
"../node_modules/clipboardy/index.js"
      ]

Then in my ts file i am giving, "const clipboardy = require('clipboardy');"
When i give "ng serve", the error comes

Use Stack Overflow for support questions.

Yeah, you can't use child_process in the browser.

Use this module instead:
https://github.com/sindresorhus/copy-text-to-clipboard


Moving IFS Objects

Hello,
I am unable to perform moving and copying objects from IFS Browser .
Beste regards,
Giovanni

QCCSID: 65535
Features enabled:

git: true
grep: true
tn5250: true
setccsid: true
GENCMDXML.PGM: false
QZDFMDB2.PGM: true
iconv: true
attr: true

SQL enabled: false
Source dates enabled: false

I wonder if this has something to do with QNTC.

I think so. It works fine in all other folders

@HenryMiller So I've been looking into this and I don't think it's a Code for IBM i problem. I get the same result when I do the same thing in pase.


[EASI-4238] Added latestModifiedDts field to operational need resolver

EASI-4238

Changes and Description

Added lastModifiedDts for tracking usage which maps against various tables' change

How to test this change

PR Author Review Checklist

[x] Met the ticket's acceptance criteria, or will meet them in a subsequent PR.
[x] Added or updated tests for backend resolvers or other functions as needed.
[ ] Added or updated client tests for new components, parent components, functions, or e2e tests as necessary.
[x] Updated the Postman Collection if necessary.

PR Reviewer Guidelines

It's best to pull the branch locally and test it, rather than just looking at the code online!
Check that all code is adequately covered by tests - if it isn't feel free to suggest the addition of tests.
Always make comments, even if it's minor, or if you don't understand why something was done.

Thanks @OddTomBrooks,
I haven't pulled this to test locally yet. I have concerns about the architecture. Each model plan has at least 32 operational needs. Effectively, this means anytime this is endpoint is called, it will reach out to the database at least 32 times. If it is called for multiple model plans, the number of db queries grows (n+1).
I think a dataloader is warranted for this use case to ensure their is only one query to the database.
Also, I wanted to check is there a reason this is on the operational need and not on the model plan itself? From the JIRA ticket, it looks like the ask is for the most recent date for the entire operational solution and implementation section, not an individual operational need. That could accomplished similarly with a query that takes a model plan id. A dataloader would still be warranted with this approach, but it would already cut down from >= 32 queries to 1 (for each model plan).

This was added to the operational needs resolver as from the Slack conversation this seems to be the requested structure. A significant degree of complexity can be resolved by simply omitting the lastModifiedDts field from queries except where necessary, which to my understanding of GraphQL will occlude the unnecessary field resolution.
I will investigate performance and architectural considerations.

This was added to the operational needs resolver as from the Slack conversation this seems to be the requested structure. A significant degree of complexity can be resolved by simply omitting the lastModifiedDts field from queries except where necessary, which to my understanding of GraphQL will occlude the unnecessary field resolution.
I will investigate performance and architectural considerations.

Thanks @OddTomBrooks for taking a look. My take from that slack conversation was that it could be on the model plan or the need, so I wanted to see if you considered the model_plan_id approach.
And that's definitely true that the query will only be called when the field is requested. However, we can't control when this is called. Someone could query a model plan collection, and get the needs for every model plan.

I think in any case having this property on the model plan / task list itself (rather than on each need) means the FE won't have to query many needs and find the largest, but rather have the backend make a single query across the entire model plan and return a single date. I think that makes things a bit less complex for both the backend and the frontend!


Call Stack (most recent call first):
  CMakeLists.txt:124 (gz_configure_build)

---
Finished <<< gz-math7 [10.7s]
Starting >>> gz-common5
Starting >>> gz-msgs9
Starting >>> sdformat13
--- stderr: gz-common5
CMake Warning at /ws/src/install/share/cmake/gz-cmake3/cmake3/GzConfigureBuild.cmake:69 (message):
   CONFIGURATION WARNINGS:
   -- Skipping component [geospatial]: Missing dependency [GDAL].
      ^~~~~ Set SKIP_geospatial=true in cmake to suppress this warning.

   -- Skipping component [graphics]: Missing dependency [assimp].
      ^~~~~ Set SKIP_graphics=true in cmake to suppress this warning.

Call Stack (most recent call first):
  CMakeLists.txt:139 (gz_configure_build)

---
[Processing: gz-common5, gz-msgs9, sdformat13]
Finished <<< gz-common5 [42.6s]
Starting >>> gz-plugin2
[Processing: gz-msgs9, gz-plugin2, sdformat13]
Finished <<< gz-plugin2 [40.7s]
Starting >>> gz-rendering7
--- stderr: gz-rendering7
CMake Warning at /usr/share/cmake-3.18/Modules/CMakeFindDependencyMacro.cmake:47 (find_package):
  By not providing "Findgz-common5-graphics.cmake" in CMAKE_MODULE_PATH this
  project has asked CMake to find a package configuration file provided by
  "gz-common5-graphics", but CMake did not find one.

  Could not find a package configuration file provided by
  "gz-common5-graphics" (requested version 5.3.1) with any of the following
  names:

    gz-common5-graphicsConfig.cmake
    gz-common5-graphics-config.cmake

  Add the installation prefix of "gz-common5-graphics" to CMAKE_PREFIX_PATH
  or set "gz-common5-graphics_DIR" to a directory containing one of the above
  files.  If "gz-common5-graphics" provides a separate development package or
  SDK, be sure it has been installed.
Call Stack (most recent call first):
  /ws/src/install/lib/cmake/gz-common5/gz-common5-config.cmake:188 (find_dependency)
  /ws/src/install/share/cmake/gz-cmake3/cmake3/GzUtils.cmake:231 (find_package)
  CMakeLists.txt:39 (gz_find_package)

CMake Warning at /ws/src/install/share/cmake/gz-cmake3/cmake3/GzUtils.cmake:231 (find_package):
  Found package configuration file:

    /ws/src/install/lib/cmake/gz-common5/gz-common5-config.cmake

  but it set gz-common5_FOUND to FALSE so package "gz-common5" is considered
  to be NOT FOUND.  Reason given by package:

  gz-common5 could not be found because dependency gz-common5-graphics could
  not be found.

Call Stack (most recent call first):
  CMakeLists.txt:39 (gz_find_package)

CUDA_TOOLKIT_ROOT_DIR not found or specified
CMake Warning at /ws/src/install/share/cmake/gz-cmake3/cmake3/GzConfigureBuild.cmake:69 (message):
   CONFIGURATION WARNINGS:
   -- Skipping component [ogre]: Missing dependency [OpenGL].
      ^~~~~ Set SKIP_ogre=true in cmake to suppress this warning.

   -- Skipping component [ogre2]: Missing dependency [OpenGL].
      ^~~~~ Set SKIP_ogre2=true in cmake to suppress this warning.

   -- Skipping component [ogre]: Missing dependency [GzOGRE] (Components: RTShaderSystem, Terrain, Overlay, Paging).
      ^~~~~ Set SKIP_ogre=true in cmake to suppress this warning.

   -- Skipping component [optix]: Missing dependency [OptiX].
      ^~~~~ Set SKIP_optix=true in cmake to suppress this warning.

Call Stack (most recent call first):
  CMakeLists.txt:176 (gz_configure_build)

CMake Error at /ws/src/install/share/cmake/gz-cmake3/cmake3/GzConfigureBuild.cmake:73 (message):
  -- BUILD ERRORS: These must be resolved before compiling.
Call Stack (most recent call first):
  CMakeLists.txt:176 (gz_configure_build)

CMake Error at /ws/src/install/share/cmake/gz-cmake3/cmake3/GzConfigureBuild.cmake:75 (message):
  --    Missing dependency [gz-common5] (Components: graphics, events,
  geospatial)
Call Stack (most recent call first):
  CMakeLists.txt:176 (gz_configure_build)

CMake Error at /ws/src/install/share/cmake/gz-cmake3/cmake3/GzConfigureBuild.cmake:77 (message):
  -- END BUILD ERRORS

Call Stack (most recent call first):
  CMakeLists.txt:176 (gz_configure_build)

CMake Error at /ws/src/install/share/cmake/gz-cmake3/cmake3/GzConfigureBuild.cmake:82 (message):
  Errors encountered in build.  Please see BUILD ERRORS above.
Call Stack (most recent call first):
  CMakeLists.txt:176 (gz_configure_build)

---
Failed   <<< gz-rendering7 [0.89s, exited with code 1]
Aborted  <<< sdformat13 [2min 1s]
Aborted  <<< gz-msgs9 [2min 42s]

Summary: 6 packages finished [2min 57s]
  1 package failed: gz-rendering7
  2 packages aborted: gz-msgs9 sdformat13
  4 packages had stderr output: gz-common5 gz-math7 gz-rendering7 sdformat13
  7 packages not processed
Error: building at STEP "RUN colcon build --cmake-args -DBUILD_TESTING=OFF --merge-install": while running runtime: exit status 1

Any idea how to resolve this? I really would like to include gazebo in our bullseye-based https://github.com/fsfw-dresden/usb-live-linux ..

gz-common5-graphics has a few dependencies:
libtinyxml2-dev
libfreeimage-dev
libgts-dev

make sure to install these libraries as well.
Note that there is a one-liner cmd to install all dependencies in this section on the doc page:
https://gazebosim.org/docs/garden/install_ubuntu_src#install-dependencies

Mhh it is a different error now, also the dependency libogre-next-2.3-dev listed in gz-sim/.github/ci/packages.apt is not in the debian repositories, but the error seems unrelated:
STEP 9/11: RUN vcs import < collection-garden.yaml
................
=== ./gz-cmake (git) ===
Cloning into '.'...
=== ./gz-common (git) ===
Cloning into '.'...
=== ./gz-fuel-tools (git) ===
Cloning into '.'...
=== ./gz-gui (git) ===
Cloning into '.'...
=== ./gz-launch (git) ===
Cloning into '.'...
=== ./gz-math (git) ===
Cloning into '.'...
=== ./gz-msgs (git) ===
Cloning into '.'...
=== ./gz-physics (git) ===
Cloning into '.'...
=== ./gz-plugin (git) ===
Cloning into '.'...
=== ./gz-rendering (git) ===
Cloning into '.'...
=== ./gz-sensors (git) ===
Cloning into '.'...
=== ./gz-sim (git) ===
Cloning into '.'...
=== ./gz-tools (git) ===
Cloning into '.'...
=== ./gz-transport (git) ===
Cloning into '.'...
=== ./gz-utils (git) ===
Cloning into '.'...
=== ./sdformat (git) ===
Cloning into '.'...
--> cf80f9fd69e
STEP 10/11: RUN colcon graph
gz-cmake3       +***************
gz-tools2        +
gz-utils2         +**.*******.**
gz-math7           +*****.******
gz-common5          +  ** ******
gz-msgs9             + * *  ****
sdformat13            +   *  **.
gz-fuel_tools8         +      *.
gz-plugin2              + ***.**
gz-transport12           +  ****
gz-physics6               +   *.
gz-rendering7              +***.
gz-gui7                     + **
gz-sensors7                  +*.
gz-sim7                       +*
gz-launch6                     +
--> ad2688e86ee
STEP 11/11: RUN colcon build --cmake-args -DBUILD_TESTING=OFF --merge-install
Starting >>> gz-cmake3
Finished <<< gz-cmake3 [0.85s]
Starting >>> gz-utils2
Starting >>> gz-tools2
Finished <<< gz-utils2 [2.79s]
Starting >>> gz-math7
Finished <<< gz-tools2 [4.36s]
[Processing: gz-math7]
[Processing: gz-math7]
[Processing: gz-math7]
[Processing: gz-math7]
[Processing: gz-math7]
[Processing: gz-math7]
[Processing: gz-math7]
[Processing: gz-math7]
[Processing: gz-math7]
[Processing: gz-math7]
[Processing: gz-math7]
[Processing: gz-math7]
[Processing: gz-math7]
Finished <<< gz-math7 [6min 45s]
Starting >>> gz-common5
Starting >>> gz-msgs9
Starting >>> sdformat13
--- stderr: gz-common5
Warning, assimp below 5.2.0 detected, setting compatibility mode
---[Processing: gz-common5, gz-msgs9, sdformat13]
[Processing: gz-common5, gz-msgs9, sdformat13]
[Processing: gz-common5, gz-msgs9, sdformat13]
[Processing: gz-common5, gz-msgs9, sdformat13]
Finished <<< gz-common5 [2min 3s]
Starting >>> gz-plugin2

[Processing: gz-msgs9, gz-plugin2, sdformat13]
Finished <<< gz-plugin2 [39.3s]
Starting >>> gz-rendering7
[Processing: gz-msgs9, gz-rendering7, sdformat13]
[Processing: gz-msgs9, gz-rendering7, sdformat13]
[Processing: gz-msgs9, gz-rendering7, sdformat13]
Finished <<< gz-msgs9 [4min 25s]
Starting >>> gz-transport12
Starting >>> gz-fuel_tools8
--- stderr: gz-transport12
CMake Warning at CMakeLists.txt:60 (message):
  lsb_release executable not found.  Disabling focal-specific workarounds

/ws/src/gz-transport/src/NodeShared.cc: In member function ‘void gz::transport::v12::NodeShared::OnNewConnection(const gz::transport::v12::MessagePublisher&)’:
/ws/src/gz-transport/src/NodeShared.cc:1216:32: error: ‘class zmq::socket_t’ has no member named ‘set’
 1216 |     this->dataPtr->subscriber->set(zmq::sockopt::subscribe, topic);
      |                                ^~~
/ws/src/gz-transport/src/NodeShared.cc:1216:41: error: ‘zmq::sockopt’ has not been declared
 1216 |     this->dataPtr->subscriber->set(zmq::sockopt::subscribe, topic);
      |                                         ^~~~~~~
/ws/src/gz-transport/src/NodeShared.cc: In member function ‘bool gz::transport::v12::NodeShared::InitializeSockets()’:
/ws/src/gz-transport/src/NodeShared.cc:1410:31: error: ‘class zmq::socket_t’ has no member named ‘set’
 1410 |     this->dataPtr->publisher->set(zmq::sockopt::linger, lingerVal);
      |                               ^~~
/ws/src/gz-transport/src/NodeShared.cc:1410:40: error: ‘zmq::sockopt’ has not been declared
 1410 |     this->dataPtr->publisher->set(zmq::sockopt::linger, lingerVal);
      |                                        ^~~~~~~
/ws/src/gz-transport/src/NodeShared.cc:1433:32: error: ‘class zmq::socket_t’ has no member named ‘set’
 1433 |     this->dataPtr->subscriber->set(zmq::sockopt::rcvhwm, rcvQueueVal);
      |                                ^~~
/ws/src/gz-transport/src/NodeShared.cc:1433:41: error: ‘zmq::sockopt’ has not been declared
 1433 |     this->dataPtr->subscriber->set(zmq::sockopt::rcvhwm, rcvQueueVal);
      |                                         ^~~~~~~
/ws/src/gz-transport/src/NodeShared.cc:1456:31: error: ‘class zmq::socket_t’ has no member named ‘set’
 1456 |     this->dataPtr->publisher->set(zmq::sockopt::sndhwm, sndQueueVal);
      |                               ^~~
/ws/src/gz-transport/src/NodeShared.cc:1456:40: error: ‘zmq::sockopt’ has not been declared
 1456 |     this->dataPtr->publisher->set(zmq::sockopt::sndhwm, sndQueueVal);
      |                                        ^~~~~~~
/ws/src/gz-transport/src/NodeShared.cc:1460:35: error: ‘class zmq::socket_t’ has no member named ‘get’
 1460 |         this->dataPtr->publisher->get(zmq::sockopt::last_endpoint);
      |                                   ^~~
/ws/src/gz-transport/src/NodeShared.cc:1460:44: error: ‘zmq::sockopt’ has not been declared
 1460 |         this->dataPtr->publisher->get(zmq::sockopt::last_endpoint);
      |                                            ^~~~~~~
/ws/src/gz-transport/src/NodeShared.cc:1464:38: error: ‘class zmq::socket_t’ has no member named ‘set’
 1464 |     this->dataPtr->responseReceiver->set(zmq::sockopt::routing_id, id);
      |                                      ^~~
/ws/src/gz-transport/src/NodeShared.cc:1464:47: error: ‘zmq::sockopt’ has not been declared
 1464 |     this->dataPtr->responseReceiver->set(zmq::sockopt::routing_id, id);
      |                                               ^~~~~~~
/ws/src/gz-transport/src/NodeShared.cc:1466:65: error: ‘class zmq::socket_t’ has no member named ‘get’
 1466 |     this->myRequesterAddress = this->dataPtr->responseReceiver->get(
      |                                                                 ^~~
/ws/src/gz-transport/src/NodeShared.cc:1467:14: error: ‘zmq::sockopt’ has not been declared
 1467 |         zmq::sockopt::last_endpoint);
      |              ^~~~~~~
/ws/src/gz-transport/src/NodeShared.cc:1471:29: error: ‘class zmq::socket_t’ has no member named ‘set’
 1471 |     this->dataPtr->replier->set(zmq::sockopt::routing_id, id);
      |                             ^~~
/ws/src/gz-transport/src/NodeShared.cc:1471:38: error: ‘zmq::sockopt’ has not been declared
 1471 |     this->dataPtr->replier->set(zmq::sockopt::routing_id, id);
      |                                      ^~~~~~~
/ws/src/gz-transport/src/NodeShared.cc:1473:29: error: ‘class zmq::socket_t’ has no member named ‘set’
 1473 |     this->dataPtr->replier->set(zmq::sockopt::linger, lingerVal);
      |                             ^~~
/ws/src/gz-transport/src/NodeShared.cc:1473:38: error: ‘zmq::sockopt’ has not been declared
 1473 |     this->dataPtr->replier->set(zmq::sockopt::linger, lingerVal);
      |                                      ^~~~~~~
/ws/src/gz-transport/src/NodeShared.cc:1474:29: error: ‘class zmq::socket_t’ has no member named ‘set’
 1474 |     this->dataPtr->replier->set(zmq::sockopt::router_mandatory, routeOn);
      |                             ^~~
/ws/src/gz-transport/src/NodeShared.cc:1474:38: error: ‘zmq::sockopt’ has not been declared
 1474 |     this->dataPtr->replier->set(zmq::sockopt::router_mandatory, routeOn);
      |                                      ^~~~~~~
/ws/src/gz-transport/src/NodeShared.cc:1477:33: error: ‘class zmq::socket_t’ has no member named ‘get’
 1477 |         this->dataPtr->replier->get(zmq::sockopt::last_endpoint);
      |                                 ^~~
/ws/src/gz-transport/src/NodeShared.cc:1477:42: error: ‘zmq::sockopt’ has not been declared
 1477 |         this->dataPtr->replier->get(zmq::sockopt::last_endpoint);
      |                                          ^~~~~~~
/ws/src/gz-transport/src/NodeShared.cc:1479:31: error: ‘class zmq::socket_t’ has no member named ‘set’
 1479 |     this->dataPtr->requester->set(zmq::sockopt::linger, lingerVal);
      |                               ^~~
/ws/src/gz-transport/src/NodeShared.cc:1479:40: error: ‘zmq::sockopt’ has not been declared
 1479 |     this->dataPtr->requester->set(zmq::sockopt::linger, lingerVal);
      |                                        ^~~~~~~
/ws/src/gz-transport/src/NodeShared.cc:1480:31: error: ‘class zmq::socket_t’ has no member named ‘set’
 1480 |     this->dataPtr->requester->set(zmq::sockopt::router_mandatory, routeOn);
      |                               ^~~
/ws/src/gz-transport/src/NodeShared.cc:1480:40: error: ‘zmq::sockopt’ has not been declared
 1480 |     this->dataPtr->requester->set(zmq::sockopt::router_mandatory, routeOn);
      |                                        ^~~~~~~
/ws/src/gz-transport/src/NodeShared.cc: In member function ‘int gz::transport::v12::NodeShared::RcvHwm()’:
/ws/src/gz-transport/src/NodeShared.cc:1556:41: error: ‘class zmq::socket_t’ has no member named ‘get’
 1556 |     rcvHwm = this->dataPtr->subscriber->get(zmq::sockopt::rcvhwm);
      |                                         ^~~
/ws/src/gz-transport/src/NodeShared.cc:1556:50: error: ‘zmq::sockopt’ has not been declared
 1556 |     rcvHwm = this->dataPtr->subscriber->get(zmq::sockopt::rcvhwm);
      |                                                  ^~~~~~~
/ws/src/gz-transport/src/NodeShared.cc: In member function ‘int gz::transport::v12::NodeShared::SndHwm()’:
/ws/src/gz-transport/src/NodeShared.cc:1577:40: error: ‘class zmq::socket_t’ has no member named ‘get’
 1577 |     sndHwm = this->dataPtr->publisher->get(zmq::sockopt::sndhwm);
      |                                        ^~~
/ws/src/gz-transport/src/NodeShared.cc:1577:49: error: ‘zmq::sockopt’ has not been declared
 1577 |     sndHwm = this->dataPtr->publisher->get(zmq::sockopt::sndhwm);
      |                                                 ^~~~~~~
/ws/src/gz-transport/src/NodeShared.cc: In member function ‘void gz::transport::v12::NodeSharedPrivate::SecurityOnNewConnection()’:
/ws/src/gz-transport/src/NodeShared.cc:1678:23: error: ‘class zmq::socket_t’ has no member named ‘set’
 1678 |     this->subscriber->set(zmq::sockopt::plain_username, user);
      |                       ^~~
/ws/src/gz-transport/src/NodeShared.cc:1678:32: error: ‘zmq::sockopt’ has not been declared
 1678 |     this->subscriber->set(zmq::sockopt::plain_username, user);
      |                                ^~~~~~~
/ws/src/gz-transport/src/NodeShared.cc:1679:23: error: ‘class zmq::socket_t’ has no member named ‘set’
 1679 |     this->subscriber->set(zmq::sockopt::plain_password, pass);
      |                       ^~~
/ws/src/gz-transport/src/NodeShared.cc:1679:32: error: ‘zmq::sockopt’ has not been declared
 1679 |     this->subscriber->set(zmq::sockopt::plain_password, pass);
      |                                ^~~~~~~
/ws/src/gz-transport/src/NodeShared.cc: In member function ‘void gz::transport::v12::NodeSharedPrivate::SecurityInit()’:
/ws/src/gz-transport/src/NodeShared.cc:1703:22: error: ‘class zmq::socket_t’ has no member named ‘set’
 1703 |     this->publisher->set(zmq::sockopt::plain_server, asPlainSecurityServer);
      |                      ^~~
/ws/src/gz-transport/src/NodeShared.cc:1703:31: error: ‘zmq::sockopt’ has not been declared
 1703 |     this->publisher->set(zmq::sockopt::plain_server, asPlainSecurityServer);
      |                               ^~~~~~~
/ws/src/gz-transport/src/NodeShared.cc:1704:22: error: ‘class zmq::socket_t’ has no member named ‘set’
 1704 |     this->publisher->set(zmq::sockopt::zap_domain, kGzAuthDomain);
      |                      ^~~
/ws/src/gz-transport/src/NodeShared.cc:1704:31: error: ‘zmq::sockopt’ has not been declared
 1704 |     this->publisher->set(zmq::sockopt::zap_domain, kGzAuthDomain);
      |                               ^~~~~~~
gmake[2]: *** [src/CMakeFiles/gz-transport12.dir/build.make:199: src/CMakeFiles/gz-transport12.dir/NodeShared.cc.o] Error 1
gmake[1]: *** [CMakeFiles/Makefile2:431: src/CMakeFiles/gz-transport12.dir/all] Error 2
gmake: *** [Makefile:182: all] Error 2
---
Failed   <<< gz-transport12 [1min 39s, exited with code 2]
[Processing: gz-fuel_tools8, gz-rendering7, gz-transport12, sdformat13]
[Processing: gz-fuel_tools8, gz-rendering7, gz-transport12, sdformat13]
[Processing: gz-fuel_tools8, gz-rendering7, gz-transport12, sdformat13]
Aborted  <<< gz-fuel_tools8 [2min 44s]
Aborted  <<< sdformat13 [9min 13s]
Aborted  <<< gz-rendering7 [7min 3s]

Summary: 7 packages finished [16min 35s]
  1 package failed: gz-transport12
  3 packages aborted: gz-fuel_tools8 gz-rendering7 sdformat13
  3 packages had stderr output: gz-common5 gz-rendering7 gz-transport12
  5 packages not processed
Error: building at STEP "RUN colcon build --cmake-args -DBUILD_TESTING=OFF --merge-install": while running runtime: exit status 2

lsb_release executable not found

maybe try apt-get installing lsb-release and see if that makes a difference?
missing libogre-next-2.3-dev means that you'll only have access to the ogre 1.x render engine. The libogre-next-2.3-dev  debs are probably not available in debian bullseye

Closing since this doesn't appear to be a gz-rendering issue.


Update 01-basic.rb

added the required json file.

This change is already incorporated into the repo. Thanks!
https://github.com/elastic/elasticsearch-rails/commit/e1fc0e6df0b85d2eb65df1dec1459fc1da980dc8


Updated: dependencys

Greetings.

Coverage remained the same at 52.362% when pulling fe94043f590a1a929932080d126b464503c7ecfd on frank-dspeed:master into f793de34cd78519aac3d4060d589ccb681e84456 on Olegas:master.

Coverage remained the same at 52.362% when pulling fe94043f590a1a929932080d126b464503c7ecfd on frank-dspeed:master into f793de34cd78519aac3d4060d589ccb681e84456 on Olegas:master.

@frank-dspeed Thanks!


jquery-ui.min.js made available locally

Removed link to jquery.com domain, issuing jquery-ui.min.js file as local resource.

I've merged this first commit as discussed in #18. As the other commit does not need merging I'll need to close this PR rather than merge it in its entirety. Rest assured though, the desired change is now merged.


Don't create model automatically for agent

After decoupling agent from langchain handler mindsdb langchain model is not required for agent.
In this PR automatic model creation is removed.
Agent can be used as:
agent=connection.agents.create('my_agent', skills=['my_skill'], prompt_template='Answer the user input in a helpful way')

# or with default prompt template
agent=connection.agents.create('my_agent', skills=['my_skill'])

dependent on https://github.com/mindsdb/mindsdb/pull/9525

I don't merge this PR because we can't release sdk before mindsdb part is released


Add additional classes for headings

[x] Text Shadow Class
[x] Border-Y Headings

Added as heading variants


Use never as default player collision

Use never as default player collision

Not sure about this change because anyone who isn't in a team will have collisions?

Yeah but the problem now is, 1.8 can push 1.9 users and 1.9 users can't push 1.8 users

But yeah, it's true. We probably should put everyone in a team while joining until some plugin changes it.

I think this would be up to the server owner. We could add an option to add everyone on the server into one team..

So why were this closed?

It was decided that this patch would not be beneficial I believe, it'll be redone soon no doubt.

Awesome, will donate then ;)


enable hitsumabushi.Args for Windows

Fixed by https://github.com/hajimehoshi/hitsumabushi/commit/ed7eb119837a7609ccf7bb1c5c9017cd8c23c72c


Remove unrecommended flag from output

The current output indirectly advertizes premature out-of-order migration,
which would be bad if it happened widely.
We can keep the flag, but should not advertize it.
the following two lines should be removed:
      _logger.stderr('Force migration with '
          '--${CommandLineOptions.skipPubOutdatedFlag} (not recommended)');

Michael Thomsen
Patchset 3
Jul 08
Let me explain my thinking here, and see if that resonates:
Listing a flag in output, even with a disclaimer saying "not recommended" means a bunch of people are going to just run it with the flag without understanding the consequences. There is a lot of UX research on this; if someone sees a UI string with a disclaimer and an action, some amount of users just go for the action.
During technical preview we don't want developers to generally start migrating and publishing. So having them run the tool and be told that they are not ready to migrate, and then "give up" is the desired outcome.
During technical preview, we would like a few to try migrating; preferable those that have "root packages" with no or very few unmigrated dependencies. To those we can message the existence of the flag separately.
Later during beta it's more of the same: We'd like for the root packages to migrate first, and then the next "ring". Again, we're like to take an active hand in managing this, and we can communicate the flag as needed to those we're working with.
I'm still divided on whether we disclose the flag in output when we get to stable. But it's easy to add the flag if we feel a lot of users are looking for it and don't know about.

https://github.com/dart-lang/sdk/commit/897706edbdbdd1e08601387b95dc931edde55e75


chore: extract merge from UC and simplify

Please read contributing guidelines and remove this line.

Benchmark results
No metrics with a significant change found.

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit f85a8708 and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
128 txs

l1_rollup_calldata_size_in_bytes
45,412
179,524
716,068

l1_rollup_calldata_gas
221,680
866,608
3,448,336

l1_rollup_execution_gas
314,167
984,348
3,667,993

l2_block_processing_time_in_ms
1,159
4,375
17,277 (-1%)

note_successful_decrypting_time_in_ms
335 (-2%)
1,003 (-1%)
3,693 (-2%)

note_trial_decrypting_time_in_ms
48.6 (-10%)
43.7 (-13%)
146 (-1%)

l2_block_building_time_in_ms
18,172 (-1%)
71,955
289,784

l2_block_rollup_simulation_time_in_ms
13,066
51,672
209,088

l2_block_public_tx_process_time_in_ms
5,073 (-1%)
20,136
80,441

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
13,887
26,746

note_history_successful_decrypting_time_in_ms
2,391 (-2%)
4,714 (-2%)

note_history_trial_decrypting_time_in_ms
88.5 (-1%)
191 (-10%)

node_database_size_in_bytes
17,301,584
32,989,264

pxe_database_size_in_bytes
29,923
59,478

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
315 (-1%)
44,897
26,193

private-kernel-ordering
192 (-1%)
44,513
14,929

base-rollup
1,406 (-1%)
128,970
881

root-rollup
83.1
4,088
677

private-kernel-inner
420 (-1%)
72,056
26,193

public-kernel-private-input
241 (-1%)
32,615
26,193

public-kernel-non-first-iteration
240
32,657
26,193

merge-rollup
7.65
2,608
881

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
1 leaves
2 leaves
8 leaves
16 leaves
32 leaves
128 leaves
64 leaves
512 leaves
1024 leaves
2048 leaves
8192 leaves

batch_insert_into_append_only_tree_16_depth_ms
10.3
10.6 (-7%)
12.7
17.1 (+2%)
22.9
63.6 (-1%)
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.9
17.5
23.0
31.6
47.0
143
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.597
0.590 (-7%)
0.540
0.531 (+2%)
0.480
0.440 (-1%)
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
N/A
N/A
N/A
74.9 (-1%)
47.6
238 (-1%)
462
898
3,546 (-1%)

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
N/A
N/A
N/A
159
96.0
543
1,055
2,079
8,223

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
N/A
N/A
N/A
0.460 (-2%)
0.488
0.435 (-1%)
0.432
0.428
0.427 (-1%)

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
N/A
N/A
N/A
103 (-2%)
57.0
350
691
1,371
5,402 (-1%)

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
N/A
N/A
N/A
197
104
691
1,363
2,707
10,771

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
N/A
N/A
N/A
0.491 (-1%)
0.498
0.474
0.475
0.476
0.471

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
N/A
56.7
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
N/A
94.1
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
N/A
0.579
N/A
N/A
N/A
N/A
N/A
N/A
N/A

Miscellaneous
Transaction sizes based on how many contracts are deployed in the tx.

Metric
0 deployed contracts
1 deployed contracts

tx_size_in_bytes
15,575
37,677

Transaction processing duration by data writes.

Metric
0 new commitments
1 new commitments

tx_pxe_processing_time_ms
582 (-1%)
1,360 (-1%)

Metric
1 public data writes

tx_sequencer_processing_time_ms
625 (-1%)


Compact view for history records

I don't like that at all, to be honest. This zigzag line now looks out of place, the notion of if-then is lost and the logic in which the line breaks in two when it gets too long makes absolutely no sense comparing to Rules.
I'm not even talking how I had to add a number of styles so everything else would not just fall apart.
I'm putting it here you you can judge yourself. My call, lets get to it in 2.1.

True, looks pretty strange.

enykeev: I agree with you. Let's target this for 2.1. However, for me, this is better than timestamp in new line :P.

This is unacceptable.
let's talk tonight, wire Davide if we can, brainstorm how to fix it,
and iterate till we like it.

Seems like after some discussion, we finally managed to find a compromise that would work. We're basically rolling back to the same order of columns we had before the repaint.

I've also put few more changes (based on @dzimine feedback) to that PR.

I'm gonna merge that to make sure all our packages are building and installing correctly. If you have more feedback, leave it there, and we'll get back to it as soon as we have time.

@enykeev I like the compromise. It's looking good. I definitely missed it. These changes are against st2web. Does that mean even community people get to see Brocade colors?
I didn't see these changes being picked up for bwc-ui. So I am a little confused on what the plan is.


fix: Fix for storing all objects in case of 'folder' transfer

What this PR changes/adds
Fix issue of transferring only last object in case of folder transfer
Fix issue with missing complete file per transferred object
Fix error in resolving secret for empty key
Adds integration test for multiobjects transfer
Why it does that
Currently multiple object transfer does not work as expected - it stores all objects with the same name - which means that all apart from last one gets overwritten.
Further notes
Additionally this PR adjust existing Integration test to test single object transfer as well as multi objects transfer.
Linked Issue(s)
I have noticed that similar issue was created today by @Pluci - so I did not double the issue
Closes #154

@paullatzelsperger / @ndr-brt - could you approve the awaiting workflows?
I hope it should be the last round - it is only about updating the DEPENDENCIES file.

@dorkau80 DEPENDENCIES is outdated again. It's a pain, but one we cannot avoid unfortunately.
Regarding the duplicate PR #155: on first glance it looks as though your PR is more comprehensive, but I haven't looked in detail. Seems like there is some cross-pr-communication going on anyway. Were you able to coordinate with @Pluci about possibly merging those two PRs?

@Pluci - Is it ok for you if we go with my PR? I think I have addressed all the comments from your and my code review.

@ndr-brt - conflicts solved.


Remove client pins and ensure latest pbr

This fixes client installs
cinderclient was pinned due to version discovery code being added that
broke, which has since been reverted.
Novaclient was pinned due to a volume-attach bug, but a new enough
release of novaclient is in pip that doesn't have this issue.
To ensure we get the right ones we express that we need newer/equal to
the versions that have our fixes in them.

retest

I sort of feel at this point we should think about doing the clients in venvs and running the update alternatives module to set the binaries in the right place.

That's something we could consider for 1.3, or just flat out removing the pins and taking clients as they come. I don't think our modules require the older versions of these clients any more.

retest


Dominaria code "DAR" instead of "DOM"

Just wondering if there's a reason that the code for Dominaria was changed from DOM to DAR in commit 5c2c103746b00658e483c5b281b1007d83a2a1be or if it was a mistake. Thanks!

It's intentional. It's not clear exactly why, but MTGA internally refers to the Dominaria set with the short code DAR. Maybe that was it's short code during development.


Where do we put tests that use jetty, but not jetty-runtime?

There's a few scenarios where Jetty is in use, but wouldn't use the jetty-runtime (or jetty-distribution) to execute.
A few common examples:

Solr
Spring-Boot
Dropwizard

You could add jetty booted via an OSGi container as another example

I don't think we need to test jetty per-se in these scenarios.  We just need to test the capabilities of the runtime.   So in this case such applications would likely be based on the openjdk-runtime.     We need tests at that level to check the capabilities the runtime provides: JRE, logging, cloud debugger, memcache, etc.
Having some 3rd party sample jars to test would not hurt either.

for low hanging fruit, Solr is an easy one then.
its pretty much an unpack, configure, and run setup.

I'm with @gregw that jetty-specific tests should not be in this repo. Closing.