TBOX-56: Allow remote Tamr restart

↪ Pull Request
Add functions for restarting, starting, and stopping a tamr instance. This can be run locally or on a remote system using a user provided paramiko.SSHClient()
✔ PR Todo

[x] Add documentation
[x] Add examples
[x] Ensure you are following the practices in the contributor guide and coding_standards

Use consistent and descriptive name conventions
Uses google-style docstrings
Uses versioned API/client methods only
Avoid global variables
Avoid giant try/catch
Don't use mutable default variables
Use a main() function in your scripts

[x] Added/updated testing for this change (ensure you are testing any changes/new code!)
[x] Update title to link to TBOX issue (i.e. start pull request title with TBOX-xx)
[x] Approval from first code-reviewer
[ ] Approval from second code-reviewer (only required if a second reviewer has left comments)
[x] Pass all checks

Is it possible to pipe through the intermediate printouts into logs?  I am able to use this successfully, but the only output I see is
INFO <4627340736> [2021-11-04 12:16:35,598] tamr_toolbox.sysadmin.instance <instance.py:261> Stopping Tamr software.
INFO <4627340736> [2021-11-04 12:16:43,717] tamr_toolbox.sysadmin.instance <instance.py:270> Stopping Tamr dependencies.
INFO <4627340736> [2021-11-04 12:17:31,979] tamr_toolbox.sysadmin.instance <instance.py:213> Starting Tamr dependencies.
INFO <4627340736> [2021-11-04 12:19:50,440] tamr_toolbox.sysadmin.instance <instance.py:221> Starting Tamr software.

It would be nice if there was a way to see all of the feedback that I'm used to when restarting Tamr.

@skalish Updated code to include a verbose flag that will pipe all of the output into the INFO log in real time. When verbose is false the same info is put into DEBUG. Previously this info was put into DEBUG but it wasn't written until the process was complete. Example verbose output:
INFO <140735495742336> [2022-02-23 08:48:10,841] tamr_toolbox.sysadmin.instance <instance.py:46> Running command [sudo su - ubuntu -c '/home/ubuntu//tamr/stop-unify.sh'] on remote machine (unknown) as user 'keziah.katz'.
INFO <140735495742336> [2022-02-23 08:48:11,926] tamr_toolbox.sysadmin.instance <instance.py:71> STDOUT: Working directory is /home/ubuntu
Stopping running processes with pid files in /home/ubuntu/tamr/pids
Stopping unify-all (pid 7505).
INFO <140735495742336> [2022-02-23 08:48:12,928] tamr_toolbox.sysadmin.instance <instance.py:71> STDOUT: .
INFO <140735495742336> [2022-02-23 08:48:13,933] tamr_toolbox.sysadmin.instance <instance.py:71> STDOUT: .
INFO <140735495742336> [2022-02-23 08:48:14,934] tamr_toolbox.sysadmin.instance <instance.py:71> STDOUT: .
INFO <140735495742336> [2022-02-23 08:48:15,935] tamr_toolbox.sysadmin.instance <instance.py:71> STDOUT: .
INFO <140735495742336> [2022-02-23 08:48:16,941] tamr_toolbox.sysadmin.instance <instance.py:71> STDOUT: .
INFO <140735495742336> [2022-02-23 08:48:17,942] tamr_toolbox.sysadmin.instance <instance.py:71> STDOUT: .
INFO <140735495742336> [2022-02-23 08:48:18,948] tamr_toolbox.sysadmin.instance <instance.py:71> STDOUT: .
INFO <140735495742336> [2022-02-23 08:48:19,953] tamr_toolbox.sysadmin.instance <instance.py:71> STDOUT: .
INFO <140735495742336> [2022-02-23 08:48:20,953] tamr_toolbox.sysadmin.instance <instance.py:71> STDOUT: .
INFO <140735495742336> [2022-02-23 08:48:21,956] tamr_toolbox.sysadmin.instance <instance.py:71> STDOUT:  force killed after 10 seconds.
INFO <140735495742336> [2022-02-23 08:48:22,960] tamr_toolbox.sysadmin.instance <instance.py:71> STDOUT: Stopping connect (pid 8189) done.
INFO <140735495742336> [2022-02-23 08:48:23,963] tamr_toolbox.sysadmin.instance <instance.py:71> STDOUT: Stopping validify (pid 8284)-- already not running.
INFO <140735495742336> [2022-02-23 08:48:24,968] tamr_toolbox.sysadmin.instance <instance.py:71> STDOUT: Stopping previewSpark (pid 7472) done.
INFO <140735495742336> [2022-02-23 08:48:25,971] tamr_toolbox.sysadmin.instance <instance.py:87> Command ended with exit code 0.


Configuration options not clear with font scaling

What are you trying to do?
I have my Dalamud font scaling set to 36pt font. I've noticed an issue with several other mods where the options in windows don't look correct, I believe this is what is causing the problems in RepairMe as well.
What is the expected behavior?
I expect to be able to clearly see all options and settings, with enough width to clearly see the contents of what I need to set
What actually happened?
May options are too narrow for me to even see the value of the field
Suggested solution
I've submitted a few bugs to another mod, DailyDuty, you might be able to make a similar change to this mod.
Logs
No response
FFXIV Update

[X] I have confirmed that I have the latest version of XIVLauncher and RepairMe.

this happens in the configuration window only? or in the alerts/bars as well?
can you provide a screenshot?


HTML: some part of big file is parsed wrong

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.65
OS Version: Ubuntu 20 x64

Steps to Reproduce:

open big HTML file, it is valid html page from Yahoo site. File in zip -
https www.yahoo.com.zip

go to lines 1242 ... 1244 and see RED parts - they must not be red.

I can reproduce the issue, but I was unable to extract it in a smaller, reproducible sample.
@alexdima Any idea why some parts are rendered in red although the Inspect Tokens and Scopes hover can compute a scope (although it takes a very long time to compute)

@aledima See question above...

@aeschli Here is a reduced repro:
<script>window.$_mod_ybar={
</script>
<script type="text/javascript">
    console.log(`hello world`);
</script>

I believe this is caused by embedding a complex JS grammar inside HTML. The JS grammar inside HTML needs to be a grammar which at every step of the way checks if a </script> tag appears. The one we use inside HTML currently doesn't do this like in this example. There are many other JS patterns which reproduce this.

Thanks @alexdima. What your are mentioning is https://github.com/microsoft/vscode/issues/20488
Interestingly, the JavaScript in the example https www.yahoo.com.zip is not incomplete or missing any closing brackets.
But it is all JavaScript code one one line. So I guess we stop and then get stuck in a rue that does not contain </script>
Closing as dup of https://github.com/microsoft/vscode/issues/20488

:+1: The builtin bracket matcher thinks that some brackets are not closed:

It is possible that they are closed correctly on a long line which gets skipped during tokenization.


Support extended SemVer where applicable

Changes

Fixed the -d CLI argument. It wasn't working
Added -r for a dry-run. Just prints the parsed versions
Fixed the app/build.gradle replacements so that it doesn't ignore versionName any more and simply does both replacements in one go. Before, the replace-in-files was returning "not changed" for the second match.
Now allows versions like 1.0.1-beta2 or 1.03+20201002. IOS still receives the plain vanilla 1.0.1 here; so if your version scheme abides with iOS standards; there should be no breaking changes.

NOTE: package.json file needs work before you can merge this, if you want to
Background
I find my self doing a bunch of point-releases on Android these days and I was frustrated that https://github.com/tj-mc/react-native-version-setter/issues/4 was impossible, due to iOS.
I needed this for work, and if you want to use it. That is fine. But, if you feel that I'm taking the project in a wrong direction; that's fine too.

Thanks so much for the detailed PR! I appreciate the work. From a first glance I would be happy to integrate, and this seems like a perfectly find direction for the project. I will review this tonight and get back to you. Cheers.

Merged, now supporting #4 . Thanks for the PR!

Cool. Remember to change name and version back before publishing


Unable to install

HI,
I just ran across this repo and thought I would test out the functionality.    I am using stackblitz to try to test it quickly and easily but in the app.module file the import cannot find module ngx-click-to-edit/dist/ngx-click-to-edit
https://stackblitz.com/edit/angular-sdzxtk
Any assistance would be appreciated.  Thanks.

Hi,
How Can I get the Old(Original) value after submit?. If anything get failed in backend


[RESOLVED] Interface eth0(): High error rate (>2 for 5m)

Problem started at 11:54:29 on 2023.05.16
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Operational data: errors in: 1, errors out: 0
Original problem ID: 20733
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23483&eventid=20733

Problem has been resolved in 3m 0s at 11:57:29 on 2023.05.16
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Original problem ID: 20733


Helper errors should be emitted to stdout as -f json events

When running bpftrace with -f json, I think it's reasonable to expect events from the execution, like helper errors, to be emitted to stdout. Unfortunately, that output only goes to stderr as a WARNING log.
If we run with -kk, we see the error clearly but not on stdout, as JSON output:
>  sudo src/bpftrace -kk -f json -B line --btf -o foo -e 'struct foo {int a;}; tracepoint:syscalls:sys_enter_nanosleep { printf("test\n"); $tmp = ((struct foo*) 0)->a; }'
{"type": "attached_probes", "data": {"probes": 1}}
{"type": "printf", "data": "test\n"}
stdin:1:89-110: WARNING: Failed to probe_read_kernel: Numerical result out of range (-34)
struct foo {int a;}; tracepoint:syscalls:sys_enter_nanosleep { printf("test\n"); $tmp = ((struct foo*) 0)->a; }
                                                                                ~~~~~~~~~~~~~~~~~~~~~```

Describe the solution you'd like
I'm open to suggestions but I think it's not unreasonable to have -kk in conjunction with -f json generate events like
{"type": "helper_error", "helper": "bpf_probe_read_kernel", "line": 1, "col": 89}
In particular, this would help when used with -o or piped to other post-processing tools.

I put up #2326 as a first pass at this.


refactor(semantic): change the reference flag to ReferenceFlags::Type if it is used within a TSTypeQuery

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#5444  👈
#5441
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @Dunqing and the rest of your teammates on  Graphite


is there a way to set a timeout for specific controller or request endpoints?

I'm not sure how or where timeouts are handled. I only get problems with my client if a request takes longer than 11_000ms -> 408 Request Timeout.
For endpoints that perform longer data processing operations, I would like to increase this timeout. I can't find any hint in the docs, is this possible?

It seems as if I have found a way. But it feels ugly. It would be better to set a max timeout e.g. 20 seconds, and if the promise is not resolved within this period, the server should respond with 408.
Here is my workaround for now.
@ApiDocument({ name: "system" })
@Controller("/system")
export class SystemController {
  @Get("/info")
  getInfo(rev: RequestEvent) {
    const opThatLasts = (ms: number): Promise<string> =>
    new Promise((resolve) => {
      setTimeout(() => {
        resolve("ok");
      }, ms);
    });

    const resultPromise = opThatLasts(20_000);
    rev.waitUntil(resultPromise);

    return rev.respondWith(resultPromise as any);
    // return resultPromise;
  }
}

That doesn't solve the problem in the case that both timeouts are larger than the magical 11 seconds.
If I do following, all promises will resolve asynchronously, but the client that calls the endpoint still receives a timeout 408 after 11 seconds.
const withTimeout = (p: Promise<any>, ms: number) =>
  Promise.race([
    p,
    new Promise((res) => setTimeout(res, ms)).then(() => {
      console.log("log from inside first promise");
      throw new HttpError(408);
    }),
  ]);

app.get("/", async () => {
  console.log("log incoming request");
  const myProcess = () => {
    console.log("log from inside second promise");
    return new Promise((res) => setTimeout(res, 15_000));
  };
  await withTimeout(myProcess(), 20_000);
  console.log("log after await");
  return "done!";
});

I think I have to increase the internal time out somehow to solve the problem.

how about this?
// timeout 11s.
await withTimeout(myProcess(), 11000);

BTW in nodejs, set timeout server with server.setTimeout. but i don't know the config in deno.

I think you have misunderstood me. I want the response to wait longer for resolving the process promise not to reduce the default time to something less than the magic 11_000ms.
I have found out what the problem is. It is the awaiter function in nhttp_utils.ts, which works with "hardcoded" timeouts.
It checks in unequal periods if the response is still resolved:

sleep 0ms -> check response
sleep another 200ms -> check response
sleep another 400ms -> check response
sleep another 600ms -> check response
sleep another 800ms -> check response
sleep another 1000ms -> check response
sleep another 1200ms -> check response
sleep another 1400ms -> check response
sleep another 1600ms -> check response
sleep another 1800ms -> check response
sleep another 2000ms -> check response (sums up to 11_000ms) -> if still no response, return 408

https://github.com/nhttp/nhttp/blob/86f541ed3349504f2d35688f7a8b49661b484862/src/nhttp_util.ts#L5-L24
Shouldn't there be a smarter implementation? Or shouldn't there at least be a way to inject a custom timeout from outside to override the defaults?

Oh I see. The code is wait and timeout for undefined returns on a handler. if there is a response, then awaiter is not executed.
maybe I will give a timeout value option in the nhttp config to handle this. what do you think?. or have any ideas?

as I mentioned, there is no timeout feature in Deno. and if you adopt the expressjs feature, it will be more or less like this..
const wait = (ms: number) => new Promise((r) => setTimeout(r, ms));

// this is similar req.setTimeout in express but in middleware.
const timeout = (ms: number): Handler => (_, next) => {
  return Promise.race([
    next(),
    wait(ms).then(() => next(new HttpError(408))),
  ]);
};

const app = nhttp();

app.get("/", timeout(11000), async () => {
  // asume process save to db 20s and request timeout is 11s. so this routes reject to 408.
  await wait(20000);
  return "done";
});

in Expressjs
const app = express();

app.get("/", async (req, res) => {
  req.setTimeout(11000);
  await wait(20000);
  res.send("done");
});

I'm sorry, no, that doesn't solve the problem. With the timeoutHandler I can reduce the timeout but not increase it beyond above the 11 seconds, because this does not bypass the awaiter logic and with Promise.race an HttpError(408) is always returned for the shortest time period.
As long as there is no way to set a global timeout in  nhttp, I go with my first working workaround (waitUntil + respondWith).
Thx

I'm not sure. Maybe the problem is the swagger wrapper I'm using? I don't know the internals but could it be the problem, that the return value is not registered in rev[s_response] so I'm running into the 'awaiter' logic.
This is how I use it, which internally calls the 'awaiter':
@ApiDocument({ name: "system" })
@Controller("/system")
export class SystemController {
  @Get("/info")
  getInfo(rev: RequestEvent) {
    const resultPromise = anyMethodThatResolvesAfter11Seconds(20_000);
    return anyMethodThatResolvesAfter11Seconds(20_000);
  }
}

const anyMethodThatResolvesAfter11Seconds = (ms: number) => {
  return new Promise((resolve) => {
    setTimeout(() => {
      resolve("ok");
    }, ms);
  });
}

i tested in my laptop, and work fine as expected.
@ApiDocument({ name: "system" })
@Controller("/system")
export class SystemController {

  @Get("/info")
  getInfo(rev: RequestEvent) {
    return anyMethodThatResolvesAfter11Seconds(20_000);
  }
}

const anyMethodThatResolvesAfter11Seconds = (ms: number) => {
  return new Promise((resolve) => {
    const now = Date.now();
    setTimeout(() => {
      // resolve 20000ms
      resolve(`${Date.now() - now}ms`);
    }, ms);
  });
}

That's really strange. I copied your code to have it exactly the same, but I still get a timeout with that code after 11 seconds 🤔
Also upgraded from nhttp 1.3.10 -> 1.3.13 and using these imports, but had no effect:
"nhttp_controller"<EMAIL_ADDRESS>"nhttp_swagger"<EMAIL_ADDRESS>"nhttp_validator"<EMAIL_ADDRESS>

Oh dear, I was just about to set up a simple project to reproduce the error. Then I realized that everything works as it should, as you say. 🙈
I analyzed everything and found that the return before the next() is missing in one of my middlewares. 😔
Thanks for the always fast and great help and sorry that the error was mine.


Add minutesStep property to TimePicker

It would be nice to add minutesStep property to TimePicker. This property would be responsible for how many minutes should be added/subtracted when moving the clock pointer - like in Materia-UI v0.xx TimePicker component.

Nice, either i suggest adding two poperties, minTime and maxTime. These properties would be checked if are in the range (between minTime and maxTime) after filling the input; If it is not in range the  function prop onError would be trigged and the input highlighted in red. Thk you.


Compiler rrrors when building for tizen 5.5

I am trying to build nntrainer for tizen 5.5, the build process fails with some compiler errors:
 597 [   90s] [11/153] Compiling C++ object 'nntrainer/d48ed23<EMAIL_ADDRESS> 598 [   90s] FAILED: nntrainer/d48ed23<EMAIL_ADDRESS> 599 [   90s] c++ -Inntrainer/d48ed23@@nntrainer@sha -Inntrainer -I../nntrainer -Inntrainer/../api -I../nntrainer/../api -I../nntrainer/../api/ccapi/include -I/usr/include/nnstreamer -Inntra
 600 [   90s] In file included from /usr/include/nnstreamer/nnstreamer-single.h:29:0,
 601 [   90s]                  from ../nntrainer/layers/nnstreamer_layer.h:19,
 602 [   90s]                  from /home/abuild/rpmbuild/BUILD/nntrainer-0.1.1/nntrainer/layers/nnstreamer_layer.cpp:18:
 603 [   90s] /usr/include/nnstreamer/nnstreamer.h:165:35: error: redeclaration of 'tizen_error_e ML_ERROR_NONE'
 604 [   90s]    ML_ERROR_NONE                 = TIZEN_ERROR_NONE, /**< Success! */
 605 [   90s]                                    ^~~~~~~~~~~~~~~~

There are a lot more than this one, but it wouldn't fit on the page.
Any idea what could cause this failure?
I can share the full log if needed.
Thank you.

:octocat: cibot: Thank you for posting issue #855. The person in charge will reply soon.

:octocat: cibot: Thank you for posting issue #855. The person in charge will reply soon.

Could you give us more information to reproduce the issue?
IMO, the commit id of the repo, build command and gbs conf should do.

Could you give us more information to reproduce the issue?
IMO, the commit id of the repo, build command and gbs conf should do.

@zhoonit I think the issue is that with tizen 5.5, nnstreamer includes error code (as ml_error_e) with nnstreamer.h header than a separate header. (tizen_error.h with tizen 6.0). This creates the error on redeclaration. Please let me know if you can check this on your side. IMO you can either add a patch to tizen_5.5 branch of nnstreamer to update the headers (make sure not to break existing applications) or check declarations on nntrainer side depending on tizen version.
@nscotto As nntrainer is official released since tizen 6.0, we did not test with nnstreamer in earlier versions of tizen (tizen 5.5 in this case). Based on the issue https://github.com/nnstreamer/nntrainer/issues/851, can you please describe the application and the architecture/os version you want to use nntrainer for? We will able to help you better with this.

@zhoonit I think the issue is that with tizen 5.5, nnstreamer includes error code (as ml_error_e) with nnstreamer.h header than a separate header. (tizen_error.h with tizen 6.0). This creates the error on redeclaration. Please let me know if you can check this on your side. IMO you can either add a patch to tizen_5.5 branch of nnstreamer to update the headers (make sure not to break existing applications) or check declarations on nntrainer side depending on tizen version.
@nscotto As nntrainer is official released since tizen 6.0, we did not test with nnstreamer in earlier versions of tizen (tizen 5.5 in this case). Based on the issue https://github.com/nnstreamer/nntrainer/issues/851, can you please describe the application and the architecture/os version you want to use nntrainer for? We will able to help you better with this.

later should work, I'll make a patch

later should work, I'll make a patch

Added a workaround patch under tizen 6. (#866)
Please note that tizen_5.5 is not officially supported, although the patch should make it working as of now, it might not in the near future.

Added a workaround patch under tizen 6. (#866)
Please note that tizen_5.5 is not officially supported, although the patch should make it working as of now, it might not in the near future.

@nscotto Is this issue resolved?

Yes! Sorry for the late reply.

Thank you for the reply :) I'll close this issue.


MangoPay\Exception Message: Cannot create or write to file

i create the tmp folder and set permission also but still it gives the mention error while i create the new natural user : can anybody help?

Hello @rajinth!
What system (Windows/Mac/etc) are you running when you encounter this problem? Please make sure you've created a folder and have correctly specified the full path to it when configuring Mangopay (ex: $this->mangoPayApi->Config->TemporaryFolder = 'C:\\path\\to\\folder';), following the README.md documentation from https://github.com/Mangopay/mangopay2-php-sdk .
Please let us know some more details if you still have this issue.
Thank you!


Pin orjson dependency.

Remediation for: https://github.com/apache/beam/issues/28318.
If orjson doesn't come up with a fix, we can pin the last tested version.

I believe you could pin the dependency to orjson 3.9.2 - as we are currently running orjson 3.9.2 without problems and the orjson github project issue mentioned others were reverting from 3.9.4 to 3.9.2 to avoid the problem.

ok. done


Add --include-introns for cellranger workflow

Closes #72. I added a parameter to the run-cellranger.nf workflow to allow for flexibility to use cellranger with snRNA-seq samples. To use the --include-introns flag you would implement it at the time of running the workflow by executing:
nextflow run cellranger-quant/run-cellranger.nf --include_introns:"--include-introns"
I don't think this is a permanent fix for this. Before we run all of our samples I think a better solution might be to grab the seq-unit from the scpca-library-metadata.tsv file and based on if the seq-unit == nucleus, then we would use the flag for --include-introns.
However, since we are still in the benchmarking phase, I thought it might not be the best approach to give up complete control. It could be useful to compare some of the snRNA-seq runs using cellranger with and without this flag rather than include it as a default immediately.

Should we automatically switch modes based on the sample? That is, if the seq_unit is nucleus, we use --include-introns but if it is cell we do not?

I just realized that you addressed this in your PR submission, which I obviously didn't read again this morning. I blame Monday. Apologies.
I still think it makes sense to set the option up as an input to the process to facilitate later changes, but I'm really sorry for just repeating something you already addressed.

No worries at all. I do agree we will need to do a final update before we run everything to automatically use the --include-introns for snRNA-seq samples, assuming we that's what we end up deciding on. I moved it to be an input to the process to get us started.


Issues interface

We discussed a problem, that we should not run script for issues preparing and have an ability to parse, filter and dump 'raw' issue reports. So in this PR, I added the common interface for all issues. It allows unifying parsing/analysis of code quality reports from different analyzers.

We decided that @property is hard to use with dataclasses so getter is ok, if we do not want to write serialization/deserialization manually.


feat(ui-shell): Add Side Navigation component

Closes IBM/carbon-components-react#1414
Changelog
New

src/components/UIShell/SideNav*.js
src/components/UIShell/SkipToContent for usage in header

Changed

src/components/UIShell/Header now uses a custom Link component to enable consumers to specify their own link element
Header classes no longer have platform- in them

Removed

Something seems off? 🤔

@alisonjoseph should be good with the latest style fix in carbon-components!


Explore alternative table structure for packages

Right now ingesting SBOMs slow (see #165). A first investigation shows that a lot of traffic happens on the tables around packages (package versions, qualified packages, …). I think it makes sense exploring alternative ways of storing this information.
Ideas:

flat table: package url, split up, qualifiers as JSON field (?)
ltree: might not work as we don't have actual "labels"
using values as primary key (vs auto-increments), not sure this works

One aspect of this is also that question if a package "belongs" to an SBOM. Or is just referenced by an SBOM. The question is, what will happen when an SBOM gets deleted. IMHO this should remove all packages stored in the database as well.

So far I've been considering packages to not belong to an SBOM.
This allows folks to navigate from the root -> package -> what else includes/references/uses it across all of the SBOMs we have.
log4j -><EMAIL_ADDRESS>-> { quarkus-1.2, eap-9.7, ...}
The reason for the qualifiers to be outside of the base package is mostly due to not having to canonicalize or care about order of qualifiers, or to be able to do searches based on subsets of qualifiers.  Likewise, keeping versions separate allows us to know that<EMAIL_ADDRESS>and<EMAIL_ADDRESS>are both variants of the same Platonic package.
We could fully denormalize and let a qualified package version be a single row in a single DB, but then we are somewhat back to having to find a different way to group variants back together.

So far I've been considering packages to not belong to an SBOM.

That's an interesting aspect. I didn't fully check, but I noticed some "sbom_id" field, at least once. We also have the requirements of the "document describes" entrypoint, which not all SBOMs have. So maybe we do need the idea of an SBOM, and the fact that packages can be contained in one. But that's a topic for another issue/discussion.

We could fully denormalize and let a qualified package version be a single row in a single DB, but then we are somewhat back to having to find a different way to group variants back together.

Yes, that's the downside. And we would have a lot of duplicate values in the table as well (increasing storage). Maybe an index could help, maybe ltree, … I don't know. But that's the whole point: measure, don't guess!

A relationship between packages is an assertion tied to an SBOM.
Many SBOMs can make different assertions.

So in SPDX terms: we have a global pool of packages and a per-SBOM table (not DB table) of package relationships?

Yes

I think we solved this some time ago. If not, we can re-open.


feat(epub): Add EPUB support

Addresses https://github.com/microsoft/markitdown/issues/88.
Adds new converter + new test.

@0xRaduan love this PR. We already have a dependency for HTML to text (markdownify) in the HTML convertor. Can you check if that would be sufficient?


Doc Expansion in autogen

How can I default hide expansion for all tags using swagger-autogen? Like this attached image.

Hi @nil1729. You can do this passing the parameter docExpansion = 'none' in the middleware of swaggerUI, like:
const swaggerUi = require('swagger-ui-express')
const swaggerFile = require('./swagger_output.json')
const express = require('express')
const app = express()

app.use('/doc', swaggerUi.serve, swaggerUi.setup(swaggerFile, false, { docExpansion: "none" }))

if you succeed, let us know.

Hi @nil1729. You can do this passing the parameter docExpansion = 'none' in the middleware of swaggerUI, like:
const swaggerUi = require('swagger-ui-express')
const swaggerFile = require('./swagger_output.json')
const express = require('express')
const app = express()

app.use('/doc', swaggerUi.serve, swaggerUi.setup(swaggerFile, false, { docExpansion: "none" }))

if you succeed, let us know.

Thank you so much @davibaltar for your reply. It's working.

Hi, thanks for the response !
I have another question concerning the docExpansion.
If i the option argument is not false, the docExpansion is not triggered, is it normal ?
This is working
app.use('/doc', swaggerUi.serve, swaggerUi.setup(swaggerFile, false, { docExpansion: 'none' }));
In this case, the customCss is applied but the docExpansion is not.
app.use('/doc', swaggerUi.serve, swaggerUi.setup(swaggerFile, { customCss: '.swagger-ui .topbar { display: none }' }, { docExpansion: 'none' }));
Is it an issue or i miss something ?
Thanks.

Hy @sofian-sd ...
Your question has been around for a long time. I imagine I've already found the answer, but since someone else might have the same question, here's the solution:
app.use('/doc', swaggerUi.serve, swaggerUi.setup(swaggerFile, { customCss: '.swagger-ui .topbar { display: none }', swaggerOptions: { docExpansion: "none" } });


Defined X index_patterns, but still logs are not updating when selecting from Settings -> index pattern

Hi,
I have configured FileBeat -> LogStash -> Elasticsearch <- Kibana + Logtrail.
FileBeat collects logs from different projects. Logtash strucutres these logs and split them into different indexes by project & week using following output: index => "logs-%{project}-%{+YYYY}w%{+ww}"
Above is working fine and the documents are stored in the right index.
My goal then is to be able to view from Kibana logtrail the logs for a specific project. So I have configured several index_patterns in logtrail.json. For example:

"default_index": "logs-projectA-*",
"default_index": "logs-projectB-*",
etc.

In the UI of Kibana logTrail, under Settings, I can see in the drop down my different index pattern:  logs-projectA-, logs-projectB-, etc.
Problem: when selecting logs-projectB-, I am not getting the logs of my projectB. It still shows the logs of logs-projectA- that was initially selected.
Am I doing something wrong?
Note: it works fine when changing the i parameter in the URL: http://localhost:5601/app/logtrail#/?q=&h=All&t=Now&i=logs-projectB-&_g=()
Apparently, the dropdown selection is not used correctly?

Hi @remi-bast

What is the version of Kibana & Logtrail you have installed?
when you change the dropdown does the URL change?
Can you check in the browser debug console, the search query sent from logtrail?

Hi sivasamyk,
I have Kibana version 6.3.2: kibana-6.3.2-windows-x86_64
I have installed Logtrail using: ./bin/kibana-plugin install https://github.com/sivasamyk/logtrail/releases/download/v0.1.29/logtrail-6.3.2-0.1.29.zip
Inside kibana-6.3.2-windows-x86_64\plugins\logtrail\package.json, it shows below information, so version 0.1.29 isntalled:
"name": "logtrail",
"version": "0.1.29",
"description": "Plugin to view, search & tail logs in Kibana",
"main": "index.js",
"kibana": {
"version": "6.3.2"
}
When I select a new value in the dropdown, the URL does not change. The settings popup even does not close. When I click search, the popup closes, but the URL does not change.
From debug console, the search query is still using non selected index.
In below screenshot, I have selected logs-default-, but still querying log-zainirq- that was used by default.

Looks like you are using Windows OS. Which browser are you using?
On Sun, Aug 12, 2018 at 13:08 remi-bast<EMAIL_ADDRESS>wrote:

Hi sivasamyk,
I have Kibana version 6.3.2: kibana-6.3.2-windows-x86_64
I have installed Logtrail using: ./bin/kibana-plugin install
https://github.com/sivasamyk/logtrail/releases/download/v0.1.29/logtrail-6.3.2-0.1.29.zip
Inside kibana-6.3.2-windows-x86_64\plugins\logtrail\package.json, it shows
below information, so version 0.1.29 isntalled:
"name": "logtrail",
"version": "0.1.29",
"description": "Plugin to view, search & tail logs in Kibana",
"main": "index.js",
"kibana": {
"version": "6.3.2"
}
When I select a new value in the dropdown, the URL does not change. The
settings popup even does not close. When I click search, the popup closes,
but the URL does not change.
From debug console, the search query is still using non selected index.
In below screenshot, I have selected logs-default-, but still querying
log-zainirq- that was used by default.
[image: image]
https://user-images.githubusercontent.com/38810070/43999750-bc007d56-9e3c-11e8-800d-740329186e7f.png
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/sivasamyk/logtrail/issues/301#issuecomment-412324807,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABZXevRmv7TbtaIcjjNMuoUMDqdBgPmVks5uP9tYgaJpZM4V5Zc3
.

Yes, using Windows 10 Pro - 64 bits.
I tried with different browsers but same behaviour:

IE 11
Chrome Version 68.0.3440.106
Firefox Quantum 61.0.1
Opera 54

Can you share the full screenshot of the settings popup? There should be Ok button in settings popup. Clicking the OK button will change the selected index pattern.


[Connexoon RTS] BadCredentialsException, probably due to overuse of event listener

Describe the bug
I've had this start happening with my Australian Connexion unit. Occasionally it would happen once or twice a day and no issue, the integration would still work fine. However tonight, I'm not able to use it anymore, with the error '[custom_components.tahoma] invalid_auth' on HA start.
I did get a couple of the 'pyhoma.exceptions.BadCredentialsException: Bad credentials' prior to the blinds stop working.
My update interval was set at 60 seconds, even though these blinds are stateless so just show up as unknown.
Originally posted by @callifo in https://github.com/iMicknl/ha-tahoma/issues/278#issuecomment-770187935
Expected behavior
Connexoon RTS unit doesn't support any IO devices, thus there is no need for an event listener.
Environment (please complete the following information):

Hub: Somfy Connexoon RTS (Australia)
ha-tahoma version: latest
Home Assistant version: latest
Platform: n/a

Additional context
Related to https://github.com/iMicknl/ha-tahoma/issues/300

@callifo thanks for reporting. This is definitely something we need to address. For now, could you try removing the integration (and thus not calling the login endpoint for a while). After some days, you should be unblocked.
Set the event listener to a high interval, like a month. This should prevent you from being blocked.

Related to #300. Maybe as a quick fix, we can set the update interval very high if we just have RTS devices?


Stable diffusion XL or Pixart Sigma 900m please

Please make stable diffusion sdxl app or Pixart Sigma 900m please.
I can't get it to work on termux android so I hope you can make an Qualcomm app I got 888 phone btw

Hi @KintCark , apologies for the delayed response. Thank you for the feature request! We'll add this to our list of models requested.

Hi @KintCark , apologies for the delayed response. Thank you for the feature request! We'll add this to our list of models requested.

Hey I'm sorry but I lost my 888 cpu phone my current phone is not supported:(

Can this work on 865 adreno 650 phones?

We recommend using the neural processors in recent chipsets due to the huge computational demand in GenAI models. Even if it can run on older phone we don't think it'd be a good user experience at all (slow inference, battery drains etc).

We recommend using the neural processors in recent chipsets due to the huge computational demand in GenAI models. Even if it can run on older phone we don't think it'd be a good user experience at all (slow inference, battery drains etc).

My phone runs ai fine my battery doesn't drain fast at all. I just want an native stable diffusion app that I can run any model I want from sd1.4 to flux1 without having to use termux emulator also I want to be able to use loras scripts textual inversions. Running stable diffusion locally on android without emulator is way faster and less power hungry than using termux emulator. Hopefully one day we can get  a full featured app im waiting on shifthackz to update but he is adding termux so idk how it will be used but hopefully it's better than using original termux.

We recommend using the neural processors in recent chipsets due to the huge computational demand in GenAI models. Even if it can run on older phone we don't think it'd be a good user experience at all (slow inference, battery drains etc).

Omg I just read documentation my phone is supported XD if you do add pixart Sigma 900m please make is just an full feature stable diffusion app with lora. Support and sdxl make it into an app instead of just source files cause I currently don't have a pc and can't build the app.


Vampire The Masquerade: Justice - Compatibility

The following game can be added to the compatibility list:
Game: Vampire The Masquerade: Justice
Distribution: Steam
OpenXR Runtime in VD: VDXR
Runtime in overlay: VDXR

The game is using UE4 and needs the parameter "-hmd=openxr" in order to use VDXR.
Like all the other openXR games that use the parameter method, hand positioning is off.
A less common problem is that the right analogue stick won't let you turn.

Thanks, For the hand positioning, is it the pivot point (twisting wrist) about 10cm off?

Thanks, For the hand positioning, is it the pivot point (twisting wrist) about 10cm off?

yes

Can you send me the log file from VDXR so I can see the application name and add a quirk for it?


Error in accept and decline share using webUI

Describe the bug
When a pending share is tried to be accepted/declined using webUI, an error is shown. However, the share is accepted even with an error in the UI.
Steps to reproduce
Steps to reproduce the behavior:

Create user Alice and Brian
As user Alice, share a new created folder simple-folder with user Brian
As user Brian, decline the pending share using the decline action button
As user Brian, accept the pending share using the accept action button

Expected behavior
The share should be accepted/declined without any error in the webUI.
Actual behavior
With the decline action, an error is shown in the webUI. And the share is still in pending state until the page is reloaded.

With the accept action, an error is shown in the webUI. However, the share is shown as accepted only after the page reload.

Related to https://github.com/owncloud/web/issues/4946

re-tested with local server oCIS version 1.11.0 and web 4.1.0
Works correct, @jasson99 please close
Decline action:

Accept action after decline:


[Feature] can we also get file mimetype inside listContents() ?

without it, it means we have to make an extra request for each file to get its mimetype which with a big list could take forever.

it possible to be done by using the https://github.com/thephpleague/flysystem/blob/master/src/Plugin/ListWith.php
thanx so much for the awesome work.


suggestion: bed_color tag

The new beds have colors, which aren't detected by .material
They work exactly like the base colors of the Banner block, where we have the .base_color tag.
Either .base_color could be advanced by a else-if to work also for beds, or a own tag, like .bed_color.

added dmaterials for this in latest dev build (so you can do RED_BED and BLUE_BED and etc as material names)


added PathMatcher

Proposed replacement for ExludedPathMatcher.

Thanks. The build is broken due to Javadoc issues.

This is a core component, we need a test class to verify the behaviour. Also, the ExcludedPathMatcher should be marked as deprecated and certainly be nothing more than an inherited class from this one.
Finally, the documentation must be updated, in the release notes (https://github.com/pac4j/pac4j/blob/master/documentation/docs/release-notes.md) as well as in the matchers page (https://github.com/pac4j/pac4j/blob/master/documentation/docs/matchers.md).

Not included with this pull, but something to keep in mind in future as a usability improvement:
It might be useful for matchers to have a name field. So, in configuration, you could do:
Now:
PathMatcher matcher = new PathMatcher()
    .excludePath("/")
    .excludePath("/login")
    .excludePath(FORM_CLIENT_CALLBACK);
config.addMatcher("authPathMatcher", matcher);

Future:
PathMatcher matcher = new PathMatcher("authPathMatcher")
    .excludePath("/")
    .excludePath("/login")
    .excludePath(FORM_CLIENT_CALLBACK);
config.addMatcher(matcher);

@wardr I'm not sure about the fluent API style: or at least, I think it should also work in a Java Bean style, because for example if one wants to define a PathMatcher as part of his dropwizard configuration, it should work out of the box with something like this:
  matchers:
    authPathMatcher:
      class: o.p.c.m.PathMatcher
      excludePaths:
        - /
        - /login

As for the name, to me it seems cleaner to have the name as part of the Config and not as part of the Matcher object, this would prevent adding multiple matchers with the same name!
Actually, I think it should be the same with the Clients @leleuj

Good point. Would adding a method: setExcludePaths(String... paths) make it work for the Dropwizard configuration case?

Let me do some tests tomorrow morning and tell you, but if I take too long, just add it and then I will submit another PR if it's problematic :)

@wardr actually Jackson will use the getters to add elements to the Sets, so you just need to make them public (which is not a bad idea anyway).

+1
@victornoel Please merge in when it's ok for you.

@victornoel all changes incorporated, thanks.
Note, I don't recommend adding the regex's directly (e.g. pathMatcher.getExcludedPatterns().add("...")), because doing so would by-pass the warnings and validation checks in the excludeRegex method.  Not really a big deal though.

@wadr Just to be sure people don't add regexp directly, why not return an immutable set in the getter?

@leleuj the problem is that I would have liked if people could exploit the javabean nature of the matcher so that they could define them declaratively, for example via the dropwizard configuration file.
For this we need either a mutable getter of the collection or a setter for the collection.
In that case @wardr simply add a setter for the whole collections setExcludedPatterns and setExcludedRegexps and iterate over them to validate them if needed and also print the message.

Ok, should be good to go now.

Fair point; done.


just want to know how you got galaxy brain badge ?

You need to answer two discussions. Here, comment on these two disscussions, and when I set your comment as answer you'll get it: #5, #6

Closing as finished


Bump Dependencies #1550074640

Bumps dependencies for product-is. Link : https://github.com/wso2/product-is/actions/runs/1550074640

 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.jenkins-is-staging seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Crashed when used openssl which enabled "Control Flow Guard" on Windows x64

Here is the steps I build the openssl 3.1.1:

run command perl Configure VC-WIN64A-masm no-ssl3 no-autoload-config CFLAGS="/W3 /wd4090 /nologo /O2 /guard:cf" to config
run command "nmake" to build

When I used the openssl lib, I got the crash:

Can we enable the "CFG" on win x64 with the config VC-WIN64A-masm? Am I use the correct way to enable CFG? I used the same steps to build openssl 1.1.1, it works fine, no crash occurred.

BTW，when I run test, I got the below failure:
05-test_pbe.t ......................
# ERROR: (bool) 'PKCS5_PBE_keyivgen(ctx, pbe_password, strlen(pbe_password), algor->parameter, cipher, md, 1) == true' failed @ test\pbetest.c:77
# false
# 18830300:error:0308010C:digital envelope routines:inner_evp_generic_fetch:unsupported:crypto\evp\evp_fetch.c:341:Global default library context, Algorithm (PBKDF1 : 0), Properties ()
# OPENSSL_TEST_RAND_ORDER=1701652449
not ok 1 - test_pkcs5_pbe_rc4_md5
------------------------------------------------------------------------------
# ERROR: (bool) 'PKCS5_PBE_keyivgen(ctx, pbe_password, strlen(pbe_password), algor->parameter, cipher, md, 1) == true' failed @ test\pbetest.c:77
# false
# 18830300:error:0308010C:digital envelope routines:inner_evp_generic_fetch:unsupported:crypto\evp\evp_fetch.c:341:Global default library context, Algorithm (PBKDF1 : 0), Properties (<null>)
# OPENSSL_TEST_RAND_ORDER=1701652449
not ok 2 - test_pkcs5_pbe_des_sha1

What could be the cause of these errors? Is it a mistake in my build steps or an issue with my environment? Will this error result in a crash?

PBKDF1 comes from the legacy provider.. Does your pbetest.c file contain the following?
int setup_tests(void)
{
#ifdef OPENSSL_NO_AUTOLOAD_CONFIG
    /* Load required providers if not done via configuration */
    legacy = OSSL_PROVIDER_load(NULL, "legacy");
    dflt = OSSL_PROVIDER_load(NULL, "default");
    if (!TEST_ptr(legacy) || !TEST_ptr(dflt)) {
        cleanup_tests();
        return -1;
    }
#endif

i.e. It does something special when you use  no-autoload-config

@slontis No, here is my pbetest.c
int setup_tests(void)
{
#if !defined OPENSSL_NO_RC4 && !defined OPENSSL_NO_MD5
ADD_TEST(test_pkcs5_pbe_rc4_md5);
#endif
#if !defined OPENSSL_NO_DES && !defined OPENSSL_NO_SHA1
ADD_TEST(test_pkcs5_pbe_des_sha1);
#endif
return 1;

}
Is there something wrong?

Probably worth getting the latest..
either 3.1.4 or 3.2 (See www.openssl.org/source)
See  github.com/openssl/openssl/pull/21621
(This fixes your test issue, but maybe not your other issue)

@slontis  Thank you so much, So can we enable CFG on windows x64 platform, We suspect that the crash is caused by enabling Control Flow Guard (CFG), but we are currently uncertain about how to fix this issue. Can you provide any assistance or suggestions?

@slontis @nhorman , From the callstack, we know that the crash occured in function:
`int ossl_cipher_hw_generic_cbc(PROV_CIPHER_CTX *dat, unsigned char *out,
const unsigned char *in, size_t len)
{
if (dat->stream.cbc)
(*dat->stream.cbc) (in, out, len, dat->ks, dat->iv, dat->enc);
else if (dat->enc)
CRYPTO_cbc128_encrypt(in, out, len, dat->ks, dat->iv, dat->block);
else
CRYPTO_cbc128_decrypt(in, out, len, dat->ks, dat->iv, dat->block);
return 1;

}`
If this is a CFG issue, then it is probably caused by "(*dat->stream.cbc) (in, out, len, dat->ks, dat->iv, dat->enc);", and through our tests, we found that the CFG verification failed for the following three functions.

So we believe that the (*dat->stream.cbc)  should be pointed to cbc_decrypt_bulk, is that right? Can you provide us with some direction or suggestions for resolving this issue? Thanks a lot.

The issue is related to https://github.com/openssl/openssl/issues/22896.
It may be some time before this is addressed.

Hi @slontis We have some new findings regarding this issue, On the devices that has no issue, I found that after ossl_cipher_generic_block_update, it does not proceed to the ossl_cipher_hw_generic_cbc function but instead goes to cipher_hw_aesni_ecb. This indicates that on the devices without issues and those with issues, the difference lies in the assignment of ctx->hw->cipher.
So can you help to tell me how ctx->hw->cipher is specifically assigned? Why is ctx->hw->cipher assigned to ossl_cipher_hw_generic_cbc instead of cipher_hw_aesni_ecb on the machines with issues?

This seems like another undefined behavior detection.
the cbc128_f function pointer is defined as:
typedef void (*cbc128_f) (const unsigned char *in, unsigned char *out,
                          size_t len, const void *key,
                          unsigned char ivec[16], int enc);

And while I haven't looked it up yet, I imagine the function signature of the function this pointer points to doesn't match.  Its part of the class of errors tracked here:
https://github.com/openssl/openssl/issues/22896

Hi @nhorman How should we fix this issue or continue researching it? I would greatly appreciate any guidance or suggestions you could provide. Our app is unable to launch due to this issue.

The thing to do is format the callback funciton that cbc128_f points to to have the same arguments are return type as the definition above..  You can see examples of this in the LHASH code thunk routines

Hi @nhorman @asiplas Here's the information about my crashing machine:

The crash occurs at the location shown in the image:

We can see that dat->stream.cbc is set to the function AES_cbc_encrypt, and then the CFG check fails. I have tested this machine and confirmed that it does not support the AES-NI instruction set. Shouldn't this cbc be set to something other than AES_cbc_encrypt? Do you have any suggestions to fix this issue? If you could provide a patch, it would be greatly appreciated.

I made a suggestion above.  The function that stream.cbc points to needs to have the same prototype as the cbc_128f type

@nhorman I see that AES_cbc_encrypt is defined in aes_cbc.c, but it seems that during the OpenSSL build, aes_cbc.c is not compiled, and it looks like the implementation from aes-x86_64.asm is used directly. Are you suggesting that I should modify the implementation in the aes-x86_64.asm file?

The asm code isn't typed (as its asm), its the header file (and then all the corresponding implementations that need to be changed.

Hi @nhorman
Just wanted to update you that after adding the no-asm flag when building OpenSSL to disable the use of assembly code, the problem was resolved. So, it was indeed an issue with the assembly code that caused the CFG check to fail, right?

I'm honestly kind of suprised that worked for you.  The prototype for the stream.cbc function is where this is occuring (and we have lots of instances of this from the referenced issues).  building with no-asm should just switch your environment to using a non-asm code path, which should still have the prototyping errors

@nhorman However, adding no-asm does solve my problem, but we're concerned about the performance impact and hesitant to use this solution. Also, I noticed that the aes_cbc.c file was not compiled when building version 3.1.5. Is this correct?

Hi @nhorman
We now want to follow the above plan and would like your guidance on the following two questions:
How can we include aes_cbc.c when compiling OpenSSL 3.1.5?
How can we prevent the AES_cbc_encrypt function definition from being generated in the aes-x86_64.asm file? Do we need to modify the aes-x86_64.pl file?
We would greatly appreciate it if you could provide detailed instructions on how to do this.

aes_cbc is always included in openssl-builds by default
you can disable asm by configuring with no-asm, as you've done above.

Hi @nhorman
I am absolutely certain that aes_cbc.c is not compiled by default in version 3.1.5, I just want to know how to add it to the build process.
I don't want to add no-asm because I don not want to disable all assembly code.

Hi @nhorman, Is the following change acceptable? I tested it and found that it can be added to the Makefile. Making this change shouldn't cause any other issues, right?
diff --git a/crypto/aes/build.info b/crypto/aes/build.info
index aff318b3..25295bf6 100644
--- a/crypto/aes/build.info
+++ b/crypto/aes/build.info
@@ -67,7 +67,7 @@ IF[{- !$disabled{asm} -}]
ENDIF
$COMMON=aes_misc.c aes_ecb.c $AESASM
-SOURCE[../../libcrypto]=$COMMON aes_cfb.c aes_ofb.c aes_wrap.c
+SOURCE[../../libcrypto]=$COMMON aes_cbc.c aes_cfb.c aes_ofb.c aes_wrap.c
IF[{- !$disabled{'deprecated-3.0'} -}]
SOURCE[../../libcrypto]=aes_ige.c
ENDIF

IMO, no.  You will have built AES in CBC mode.  It is always built.  It's not always the aes_cbc.c file that is used when assembly implementations are available.  Try running ./util/wrap.pl apps/openssl list -cipher-algorithms in your build directory.  AES-128-CBC should be listed as are other flavours of AES in CBC mode.
If you are unwilling to turn off assembly code, you will either have to submit a pull request adding control flow guard support to the assembly code or build without control flow guard.  There simply is no other option.

Hi @paulidale , So the assembly code for AES cbc encryption in OpenSSL doesn't support CFG, right?
Additionally, the issue we're encountering occurs on AMD machines. When we enable CFG, the OpenSSL crashes, and the reason is that the AES_cbc_encrypt function causes the CFG check to fail, as I mentioned earlier. So, I don't want to use the assembly implementation of AES_cbc_encrypt and would prefer to use the one in aes_cbc.c. Besides modifying crypto/aes/build.info, I also made the following changes:
`diff --git a/crypto/aes/asm/aes-x86_64.pl b/crypto/aes/asm/aes-x86_64.pl
index 25f7ded9..b8b6beee 100644
--- a/crypto/aes/asm/aes-x86_64.pl
+++ b/crypto/aes/asm/aes-x86_64.pl
@@ -1732,14 +1732,14 @@ my $aes_key="80(%rsp)";		# copy of aes_key
my $mark="80+240(%rsp)";	# copy of aes_key->rounds
$code.=<<___;
-.globl	AES_cbc_encrypt
-.type	AES_cbc_encrypt,@function,6
+.globl	AES_cbc_encrypt1
+.type	AES_cbc_encrypt1,@function,6
.align	16
.extern	OPENSSL_ia32cap_P
.globl	asm_AES_cbc_encrypt
.hidden	asm_AES_cbc_encrypt
asm_AES_cbc_encrypt:
-AES_cbc_encrypt:
+AES_cbc_encrypt1:
.cfi_startproc
endbranch
cmp	$0,%rdx	# check length
@@ -2892,8 +2892,8 @@ cbc_se_handler:
.rva	.LSEH_end_AES_set_decrypt_key
.rva	.LSEH_info_AES_set_decrypt_key

.rva	.LSEH_begin_AES_cbc_encrypt
.rva	.LSEH_end_AES_cbc_encrypt

.rva	.LSEH_begin_AES_cbc_encrypt1
.rva	.LSEH_end_AES_cbc_encrypt1
.rva	.LSEH_info_AES_cbc_encrypt

.section	.xdata
`
These changes solve my issue where the app fails to launch on my AMD machine. Our app must have CFG enabled, and we cannot use no-asm to disable all assembly code. Therefore, I just want to know if these changes can be considered as a workaround? We genuinely don't know how to resolve the issue we're encountering while keeping CFG enabled and not disabling assembly code.

They would be a work around.  They would not be accepted into the projects code base I suspect.

Hi @paulidale Thanks, we would task it as a work around as we do not have other soultions

The proper solution is to modify the assembly functions to support CFG.  This will probably require community input I suspect.

hi @nhorman
When I renamed the AES_cbc_encrypt in aes-x86_64.pl add aes_cbc.c into build like I mentioned above, then change the code like this:

It also works


import/no-extraneous-dependencies support Unreleased npm packages

index.html
<html>
  <body>
      <script src="/fspa/externals/aorta-common.js"></script>
  </body>
</html>

webpack4 config
externals: {
   'aortaCommon': 'aorta-common',
}

usage:
import aortaCommon from 'aorta-common';

Now, this import  statement call error:
'aorta-common' should be listed in the project's dependencies.Run 'npm i -S aorta-common' to additeslint(import/no-extraneous-dependencies)
Missing file extension for "aorta-common"eslint(import/extensions)

But,  aorta-common package was not published!

Then how can webpack use it?

aorta-common compiles a library from webpack in another project, then put this library on the server.
@ljharb

.eslintrc.js
globals: {
  aortaCommon: true
}

I use the above ESLint configuration.
Then the Error disappear..

What you're describing is very rare - libraries should not be bundled, only apps should, and as such, apps shouldn't be consuming bundles, only creating them.


Dart selects: Make chaining more fluent

Currently, to form a more complicated Dart query, one would write
(select(table)
  ..orderBy([(row) => OrderingTerm.asc(row.id)])
  ..limit(10))
  .watch();

That's not good, but it quickly gets worse when using joins and mapping the result query:
return ((select(table)
          ..orderBy([(row) => OrderingTerm.asc(row.content.length)])
          ..where((row) => row.id.isBetweenValues(5, 40)))
        .join([innerJoin(another, another.foo.equalsExp(table.bar)])
          ..limit(10))
    .map((r) => r.readTable(another))
    .watchSingle();

Even though it's discouraged by "Efficient Dart",  I'd argue this query would be much easier to write when ignoring avoid_returning_this. If orderBy, where and limit just returned their instances, nesting would be removed entirely:
return select(table)
  .orderBy([(row) => OrderingTerm.asc(row.content.length)])
  .where((row) => row.id.isBetweenValues(5, 40))
  .join([innerJoin(another, another.foo.equalsExp(table.bar)])
  .limit(10)
  .map((r) => r.readTable(another))
  .watchSingle();

This would be a massively breaking change.
It would really hard to migrate without adding tons of bugs.
@simolus3 Can I close this as not planned?

Yeah and IMO this has also gotten a lot easier for common queries with the manager APIs.


Update hierarchical output: nested -> details

I'm going to claim that this fixes #52, where I got rather confused about hierarchical output support.  Not mentioned there but relevant and in need of addressing:
The "nested" key was changed to "details" with issue json-schema-org/json-schema-spec#1347 and PR json-schema-org/json-schema-spec#1351
@marksparkza should I add "hierarchical" to the list of available outputs in the docstrings or are you intentionally leaving it out because it is experimental?  Since it (and the proposed "list" format) are backwards-compatible, I'd propose documenting it.

Codecov Report
Base: 90.82% // Head: 90.82% // No change to project coverage :thumbsup:

Coverage data is based on head (d77a0f0) compared to base (806a090).
Patch coverage: 100.00% of modified lines in pull request are covered.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##             main      #57   +/-   ##
=======================================
  Coverage   90.82%   90.82%
=======================================
  Files          21       21
  Lines        1973     1973
  Branches      377      377
=======================================
  Hits         1792     1792
  Misses        119      119
  Partials       62       62

Impacted Files
Coverage Δ

jschon/output.py
96.25% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

I'll need to update this PR with the changed submodule commit once marksparkza/json-schema-spec#1 is merged.

This PR now includes the submodule update and should be good to go.

I'm happy to merge this, just noting the following:

The output schema itself has not yet been updated. However, there are additional issues with the output schema (e.g. output always passes against "flag", regardless of format). I made some improvements in a local branch a while back; I must just revisit that and then I'll submit a PR including the nested-to-details change.
I'd prefer to leave it out of the docs at this stage, because it can't be cross-referenced with any published spec/draft.

@marksparkza thanks!  Yes, that makes sense about the documentation, that's why I asked rather than including it in the PR :-)
@gregsdennis you night want to take a look at the changes Mark made in his fork to get the output spec working for his purposes.

Please be aware that the next version of output is not yet finalized.  I'd prefer people don't start taking a dependency on libraries that use it in its current state.  I've published it only as a beta in JsonSchema.Net.

I've published it only as a beta in JsonSchema.Net.

@gregsdennis that's basically what @marksparkza has done with this project, which is why the option isn't documented (this PR just updated the field name - the format was already supported).  From the CHANGELOG for the next release:
* Catalog support for the `next` JSON Schema draft
* `hierarchical` output format
* In-place JSON Patch `add`, `remove` and `replace` operations on ``JSON`` class

I don't think it makes sense to say that other implementations can't add experimental beta features.

I'm fine if it's explicitly listed as experimental.  Of course, in the end, I'm just supplying an opinion.


[image_picker] Handle iOS permission denied or restricted

Thanks for the submission, but delegating these errors to the client for handling in their preferred manner is the intended behavior.
Also, in the future please fill out the PR template instead of deleting it.


Assemble.io

I have the newer tagged on for my assemble.io but I have to go to the page handlebars to actually have the newer task to work. I can't just modify my .json file or any other file except for page template. How can I get newer to work for assemble.io for every file and generate accordingly?
Thanks

Anyone?

If your task is a 1:1 task (generating one destination file for every one source file), grunt-newer works by comparing modification times of the source file to modification times of the destination file.  If the source is newer, the task is run on that source file to generate the destination file.
I know of assemble.io, but I don't have time to put into debugging your particular issue.  So I can't say immediately if grunt-newer should be expected to work with assemble.  If someone else finds this and is interested in helping you debug, it would help them get started if you could provide an example project or config file.  It is especially time consuming to try to guess at how to reproduce an issue that someone reports.


Refactor terms of service content for use across multiple components

Add new route for undecorated (static) terms page shown in mobile apps.

Refactor terms of service content into new component.
Use the component in /terms and in new route /terms-undecorated.
/terms-undecorated will be used by mobile apps when presenting terms of service to users of the mobile app.

@hueachilles I think that we can just make it go to plain/undecorated view with a simple query parameter.
/terms?view=plain
Was there a reason you had to implement it in a separate component?

@hueachilles I think that we can just make it go to plain/undecorated view with a simple query parameter. /terms?view=plain
Was there a reason you had to implement it in a separate component?

@hueachilles I have made this simple change which doesn't require separate component. bceac4dcd53da2c3f3eadfe820d9c4ad34383389


can't view dailymotion VODs

On v1.12.2 Windows 7
C:\Users\User>livestreamer http://www.dailymotion.com/video/x3e679g
[cli][info] Found matching plugin dailymotion for URL http://www.dailymotion.com
/video/x3e679g
error: Unable to parse JSON: No JSON object could be decoded (u'#EXTM3U\n#EXT-X-
STREAM-INF:PROGRA ...)
I have tried using other Videos which reproduces the same error message

#666 ... already reported, but not yet resolved.

fix #1129


Recall values getting overriden in calc_statistics_new()

While iterating over different classes, max/mean recall values in statistics are getting overriden with new values.
https://github.com/fnozarian/OpenPCDet/blob/fe56e561e9a1fa7f558b4aceeadb37b0a11effee/pcdet/models/detectors/pv_rcnn_ssl.py#L370-L373
May be we can do something like we are doing for storing the precision i.e. adding the values for each class in class_metrics_all and storing this dictionary in statistics:
https://github.com/fnozarian/OpenPCDet/blob/fe56e561e9a1fa7f558b4aceeadb37b0a11effee/pcdet/models/detectors/pv_rcnn_ssl.py#L362-L368

Yes, I also noticed that. Fixed. Thanks


hwameistor-ui CrashLoopBackOff

/docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration
/docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/
/docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh
10-listen-on-ipv6-by-default.sh: info: Getting the checksum of /etc/nginx/conf.d/default.conf
10-listen-on-ipv6-by-default.sh: info: Enabled listen on IPv6 in /etc/nginx/conf.d/default.conf
/docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh
/docker-entrypoint.sh: Launching /docker-entrypoint.d/30-tune-worker-processes.sh
/docker-entrypoint.sh: Configuration complete; ready for start up
2023/11/21 03:02:42 [warn] 1#1: the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /etc/nginx/nginx.conf:1
nginx: [warn] the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /etc/nginx/nginx.conf:1
2023/11/21 03:02:42 [emerg] 1#1: host not found in upstream "hwameistor-apiserver" in /etc/nginx/nginx.conf:50
nginx: [emerg] host not found in upstream "hwameistor-apiserver" in /etc/nginx/nginx.conf:50

coredns CrashLoopBackOff


[CP] Handle privatecommand messages that pass no data #112590

Cherry picking #112590 in order to fix exceptions reported in issues like #113973
Creating PR on behalf of @justinmc based on the discussion in #112590
CP request https://github.com/flutter/flutter/issues/114462
Fixes #113973
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[ ] All existing and new tests are passing.

Hi @justinmc @itsjustkevin could you look into it

@justinmc this PR is already mentioned in the CP request. Ok I updated this PR's description to link CP

Ah sorry I missed that issue.  Just left a comment over there.


Expose reqwest's rustls feature

It would be interesting to have the possibility of using reqwest's rustls backend instead of nativetls so users can decide which tls back-end they will choose.
I am particularly using rustls and I would like to be able to share it with google-oauth.

ok, merged. thanks for using this library.


feat: labels on proposals

Towards https://github.com/snapshot-labs/workflow/issues/143
Summary:

Allows labels in proposals
Add tests to check if hasedTypes exist in hashedTypes.json (makes it easy to modify types in future)

How to test:

Run yarn test
Edit test/examples/proposal.json with different label values

Can we enforce a max lenght for label string? It can be 24

Using "maxLength": 8, reason:
https://github.com/snapshot-labs/sx-monorepo/pull/829#discussion_r1786105787
https://github.com/snapshot-labs/snapshot.js/blob/master/src/schemas/space.json#L407


Keycloak setup for user Registration & Authentication

[x] Extract the data of supabase in Json format.
[x] Create migration for keycloakUserId in the users table
[x] Register users to keycloak through NestJs
[x] Login users to get keycloak access token
[x] Work on the jwt-strategy to validate accessToken of keycloak.
[x] Fetch organization owner and return details for @User decorator details

User Story:
As a system administrator, I want to set up user registration and authentication in Keycloak to ensure a secure and user-friendly experience for individuals accessing our platform.
Acceptance Criteria:

User Registration:

Given that I am a system administrator, I should be able to configure Keycloak to allow users to register for an account.
Given the registration process, users should provide essential information such as username, email, and password.

Email Verification:

Given a user registers, an email verification process should be implemented, ensuring the validity of the provided email address.
Given the verification email is sent, users should receive clear instructions on how to verify their email address.

Password Policies:

Given user registration, Keycloak should enforce strong password policies, including minimum length and complexity requirements.

Authentication Methods:

Given registered users, Keycloak should support multiple authentication methods, including username/password, FIDO, and multi-factor authentication (MFA).

Forgot Password Functionality:

Given a user forgets their password, Keycloak should provide a "Forgot Password" functionality.
Given a password reset request, users should receive a secure email link allowing them to reset their password.

Terms of Service and Privacy Policy:

Given user registration, Keycloak should provide the ability to present and enforce acceptance of terms of service and privacy policy during the registration process.

Account Lockout Mechanism:

Given repeated failed login attempts, Keycloak should implement an account lockout mechanism to protect against brute-force attacks.

User Profile Management:

Given successful authentication, users should be able to manage and update their profile information within Keycloak.

Logging and Auditing:

Given user registration and authentication activities, Keycloak should log relevant information for auditing purposes, including successful and unsuccessful attempts.

Secure Connection:

Given the sensitive nature of authentication, Keycloak should enforce secure connections (HTTPS) to protect data during transmission.

Documentation:

Given the completion of the setup, comprehensive documentation should be provided for administrators and developers, covering the configuration, customization, and troubleshooting steps for user registration and authentication in Keycloak.

Tested on the QA environment and the changes look fine.


[RFC] Ability to index multiple vector points per document

With the growing interest in approximate nearest neighbor search with Vespa, there has also been increased demand for the ability to index multiple vectors per Vespa document.
Motivation:

Transformer models have length limitations, so longer text needs to be chunked into paragraphs or sentence levels. The classic approach is splitting into separate Vespa documents, which causes redundancy of other fields, like the title, price, and availability.
Documents might have multi-valued vector properties. For example, an e-commerce product might be described with multiple images. ColBERT is a model where a text is represented using multi-vector representations. One vector per text token (subword)

Schema
Representing multiple vectors is best done using a mixed tensor with one mapped dimension and a dense dimension. Using mixed mapped/dense allows for representing a variable number of vectors per document.
For example, for an e-commerce search use case, we can encode all the product images using CLIP and index them for efficient text-to-image search. Similarly, the textual product data might be longer than transformer input length limitations (typically 512 subwords), so there is a need to have a chunked representation.
schema product {
   document product {

      field title type string {..}
      field brand type string {..}
      field available type bool {..}
      field categories type array<string> {..}
      field global_ctr_popularity type float {..}
      field text_chunks type array<string> {..}

      field image_embeddings type tensor<float>(image{}, x[768]) {
           indexing: attribute | index
      }

      field text_embeddings type tensor<float>(chunk{}, x[384]) {
          indexing: attribute | index
      }
   }

   rank-profile default {
      inputs {
        query(text_embedding) tensor<float>(x[384])
        query(image_embedding) tensor<float>(x[768])
      }
  }
}

A mixed tensor example
tensor<float>(chunk{}, x[384]): {chunk1:[0.1,.....],chunk2:[0.02,...]}

Query
Given a user query white cotton t-shirt for men with vertical grey stripes, we can encode the query input using the text transformer and the text clip encoder and search in both embedding spaces using the same query request.  This example uses Vespa's ability to run inference; see embeddings made easy.
{
 "yql": "select * from product where available = true and (({targetHits:10}nearestNeighbor(text_embeddings,text_embedding)) or ({targetHits:10}nearestNeighbor(image_embeddings,image_embedding)))",
"input.query(text_embedding)=embed(transformer, \"white cotton t-shirt for men with vertical grey stripes\")",
 "input.query(image_embedding)=embed(clip, \"white cotton t-shirt for men with vertical grey stripes\")"
}

This query searches both the text and image embedding space using OR. A simple bool filter constrains both nearest neighbor search operators. This costs less resource than doing two queries, as the filter execution is shared.
The query request is expected to expose at least 20 hits to the first-phase ranking. It's up to the ranking function to score the documents, for example, using a more advanced ranking model.
Ranking
The nearestNeighbor query operator calculates a rawScore during the graph traversal, and the value depends on the distance-metric configured for the field.
This score can be accessed during ranking using the
either closeness(dimension, name) or distance(dimension, name) rank features.
Today dimension can be label or field. Where label can be used if one has multiple nearestNeighbor query items searching the same field. (Batch query support).
 rank-profile default {
      inputs {
        query(text_embedding) tensor<float>(x[384])
        query(image_embedding) tensor<float>(x[768])
      }
      first-phase {
         expression: closeness(field, text_embeddings) + closeness(field, image_embeddings)
      }
  }

A straightforward implementation would simply let closeness() return the score of the closest vector.
Since the graph traversal depends on a  properdistance-metric, we are limited to using the max score for the graph traversal/candidate retrieval.
Still, users could use more advanced tensor aggregations in the first-phase ranking expression (e.g., using sum or average over the closeness, expressed as a tensor expression). But the retrieval phase is only limited to using max closeness/min distance.
There is also a need to identify the closest vector, which vector made the document be retrieved. This could identify the "correct" image, when displaying the hit, or the "correct" text chunk. This could be done using a sub-feature, which is calculated in case the field is a mixed tensor (with multiple vectors):
closeness(field, text_embeddings).best

Which would return a tensor
{
    {chunk1:1}:1.0,
}

Indicating that the chunk with label 1 was the vector that caused the doc to be retrieved. This could then be used in either ranking or as part of match-features or summary-features to identify the best matching image/text chunk for display purposes.
It could also be helpful to have all the similarity scores for all vectors:
closeness(field, text_embeddings).scores

Which would return a tensor with all the closeness/distance scores for all vectors:
tensor<float>(chunk{}): {chunk1: 0.3, chunk2:0.1, chunk3:0.2}

In this case, users could use aggregates in the first-phase or second-phase.
In this example, using the average of each closeness score:
first-phase {
  expression: reduce(closeness(field, text_embeddings).scores , avg, chunk)
}

Using max aggregation:
first-phase {
  expression: reduce(closeness(field, text_embeddings).scores , max, chunk)
}

Which would be equivalent to using
first-phase {
  expression: closeness(field, text_embeddings)
}

Similarly, there should be distance(dimension, field).scores / distance(dimension, field).best
Feedback requested
Any feedback on this feature is highly welcome.

Another case not covered in the query example is the case where you have hybrid retrieval, combining the dense operators with sparse retrieval:
where available = true and (
  userQuery() or
  ({targetHits:10}nearestNeighbor(text_embeddings,text_embedding)) or
  ({targetHits:10}nearestNeighbor(image_embeddings,image_embedding))
)

where userQuery() is read from query and in Vespa 8 uses weakAnd. In this case, hits might be exposed to the first-phase ranking with no closeness or rawScore scores. Should we, in this case, calculate it on-demand so that the end user doesn't need to write another tensor expression to cover this case?

Alternative names

closeness(field, text_embeddings).closest versus closeness(field, text_embeddings).best

closeness(field, text_embeddings).all versus closeness(field, text_embeddings).scores

distance(field, text_embeddings).closest versus distance(field, text_embeddings).best

distance(field, text_embeddings).all versus distance(field, text_embeddings).scores

The first feature returns a single tensor with the label of the closest set to 1.0.
The second feature returns a tensor with all labels and the distances/closeness float score.

Support for multiple vectors per document is needed to avoid having to create artificially granular documents!  (E.g. Instead of BlogPostSentence, it would be easier to index BlogPost (but with a list of sentence embeddings contained inside))

Yes, although for text documents in general the best option might be to map it to N vectors representing the concepts discussed (a "vector cloud"), rather than one vector per sentence.

This sounds very much like what I need to index longer texts.  I need to rank higher texts that generally match the query, but also point out which paragraphs in particular match best.

Multi-vector indexing is available from Vespa 8.144.19.
https://blog.vespa.ai/semantic-search-with-multi-vector-indexing/


Merge forked changes back upstream

These are all of the changes we've made to our fork of next-routes, requesting a merge back upstream.
Most of these are dependency upgrades (using https://renovatebot.com/ instead of Greenkeeper), but there are also some updates to config, tests, and documentation.

Not sure what's the merge strategy by default on this project, but hopefully it won't merge all 128 commits and instead will squash and merge?

Thanks a lot @elliottsj that looks good like a great start. I'm currently working on other things and can't test it all out. We'll need some community feedback on the changes, @emileber spotted some good points. Please merge when you're ready, I'm going to add to to npm then so you can publish future updates.


add matrix gem, which is required for builds and no longer in ruby stdlib

I rule and have completed some work on Case Manager that's ready for review!
Heroku builds are failing with:
/tmp/codon/tmp/buildpacks/50d5eddf222a9b7326028041d4e6509f915ccf2c/lib/language_pack/helpers/rake_runner.rb:100:in `load_rake_tasks!': Could not detect rake tasks (LanguagePack::Helpers::RakeRunner::CannotLoadRakefileError)
ensure you can run `$ bundle exec rake -P` against your app
and using the production group of your Gemfile.
rake aborted!
LoadError: cannot load such file -- matrix

turns out matrix got separated from the ruby stdlib but our heroku builds depend on it still, so re-adding it to our gemfile explicitly.
see https://github.com/gdelugre/origami/issues/81 for example
This pull request makes the following changes:

add matrix gem to gemfile

no view changes
no issues
For reviewer:

Adjust the title to explain what it does for the notification email to the listserv.
Tag this PR:

feature if it contains a feature, fix, or similar. This is anything that contains a user-facing fix in some way, such as frontend changes, alterations to backend behavior, or bug fixes.
dependencies if it contains library upgrades or similar. This is anything that upgrades any dependency, such as a Gemfile update or npm package upgrade.

If it contains neither, no need to tag this PR.

godmode to get deployable


Unable to manipulate Json Object in HTML

I am planning to fetch single record from Fire database and show it inside the form but that is not happening.
Below is the code.
Component
product:Observable;
let id = this.route.snapshot.paramMap.get('id');
if(id)
this.product = this.productservice.get(id).snapshotChanges().map(res =>{
return res.payload.val();
})
Service:
get(productId){
return this.db.object('/products/'+productId);
}
HTML
Product Title{{product|async|json}}

<input required ngModel #title="ngModel" name="title" type="text" class="form-control" id="title" placeholder="Enter Title">

 Product title is required.

In above HTML I am getting
{ "category": "indian", "imglink": "http://onedaycart.com/odcb/wp-content/uploads/2016/04/Main_Chicken_Tikka_Kadai.jpg", "price": "10", "title": "Paneer Chop" }.
But how can access category or title or price?
Need help urgently

You could so something like this:

 title: {{productObj.title }}
 Category: {{productObj.category}}
 Price: {{productObj.price | currency:'EUR' }}


"Show if true" in embeded lists don't seem to use the field-values  of their parent/show view anymore since beta.16

Describe the bug
The show-if-true does not give an error-message but it just does not work anymore.
If I restore an old version of my app then the conditional show-if-true works fine as long as I don't open this list in the new list builder. Then it immediatly malfunctions.

I can't reproduce this. Adding a show if condition in the new list builder works fine and if I create a list in an old version and open it with a new list builder it also acts as it should.
Are you doing anything special here @HFolkertH , e.g. using joinfields or anything like this? Maybe you could paste a couple of screenshots of your list builder and your table structure

the show-view sets a relation between Order and the embeded list-view on Orderlines.  As long as the Order has the status "In bestelling" then Orderlines can be edited or deleted.

Everything seems fine. No error messages about formula syntax

But when I open the orders page the Edit icon and action are not shown for orders with status " In bestelling" .  It always worked correctly with  the old List builder. When I empty the show-if formula the edit icon and action are there.

This should be fixed in #2336 - i have deployed to saltcorn.com, would you be able to test @HFolkertH

Fixed!  Thanks


Include environment options in gym env name?

I would like to test out some of these environments in existing RL reference implementations, eg Baselines, Dopamine, RLLib, etc. But I would especially like to be able to use some of the environment options (eg distribution_mode="easy"), and it seems like this isn't super easy to do without digging deep into the source code of these reference implementations and modifying the line where they do gym.make() to add the desired flags.
I wonder if it would be possible to encode the environment options in the environment name itself. For example, instead of just allowing the env name procgen:procgen-coinrun-v0, you could allow procgen:procgen-coinrun-v0@distribution_mode=easy (or any such syntax). That way people could try out these reference implementations without modification even from the command line, but still access the cool environment options you all have enabled.

I think there's too many combinations to do that unfortunately.  However if you write some code like this: https://github.com/openai/procgen/blob/master/procgen/gym_registration.py#L24 and then register the names you want to use in your experiment it should work fine.
If you want to do that without modifying the procgen source, you can create your own package, say, procgen_experiments and do gym.make("procgen_experiments:<name>")

Gotcha, yeah it would have to be a modification in Gym itself to support flags without explicitly registering each combination.

gym does support that through the use of **kwargs to gym.make, but it sounded like you didn't want to do that

If I pass distribution_mode as an argument to gym.make, would the argument be used while creating the environment?
For ex:
env = gym.make("procgen:procgen-fruitbot-v0", distribution_mode = 'easy', num_levels=1, start_level = 0)

It's supposed to, does that not work?

It does. I thought the above comments meant that these args can't be used with gym.make.

gym does support that through the use of **kwargs to gym.make, but it sounded like you didn't want to do that

^ This was meant to indicate that it did.  The original poster may not be in a position to use that though, since they mentioned using some RL frameworks, which probably don't support gym.make with kwargs, only the string version.

I updated the docs to make this more clear.


Add a custom resource definition plugin

This adds a CRD plugin into networkservicemesh. This takes care of adding
custom resources for networkserviceendpoints, networkservicechannels, and
networkservices. This includes validators for the resources as well, and
makes use of the existing generated go code from our protobufs as the
payload.
In practice, this appears as the following:
localadmin@kmestery1604:~$ kubectl get crd
NAME                                          AGE
networkeservicendpoints.networkservice.mesh   4m
networkservicechannels.networkservice.mesh    4m
networkservices.networkservice.mesh           4m
localadmin@kmestery1604:~$ kubectl get NetworkService -o yaml
apiVersion: v1
items:
- apiVersion: networkservice.mesh/v1
  kind: NetworkService
  metadata:
    clusterName: ""
    creationTimestamp: 2018-05-21T18:16:56Z
    name: networkservice-radio
    namespace: default
    resourceVersion: "8781"
    selfLink: /apis/networkservice.mesh/v1/namespaces/default/networkservices/networkservice-radio
    uid: 25014149-5d23-11e8-a84b-0800275bf7f3
  spec:
    message: NetworkService Radio Network
    name: Hog*Invalid*Name
    selector: purple
    thisshouldfail: yes-it-should
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""
localadmin@kmestery1604:~$

Signed-off-by: Kyle Mestery<EMAIL_ADDRESS>

@fkautz @edwarnicke @jhnbrns If we all agree code generation is the way forward here, it may help if I commit the generators (the new files in cmd/*) in a separate patch. Let me know, as I know this pulled in a lot for the small amount to actual changes I had to make.

I should note this will eventually close Issue #48 as well.


Version 4.1.0 release

Changed

Added support for version v2.1-<IP_ADDRESS> of the DocuSign ESignature API.
Updated the SDK release version.

closing b/c we have new swagger


Line wrapping

Turns out this is really wrong approach. Will make another, simpler attempt.

Superseded by #15.


Lf filter not working

Hello, I tried applying the lf feature on the main graph but the other graphs do not show.
Is there something I need to turn off?
This is the code I am using:
KnackInitAsync = function ($, callback) { // Load the Knack Toolkit Library (KTL)
(window.LazyLoad = LazyLoad) && LazyLoad.js(['https://ctrnd.s3.amazonaws.com/Lib/KTL/KTL_Start.js'], () => {
loadKtl($, callback, (typeof KnackApp === 'function' ? KnackApp : null), '' /KTL version, leave blank to get latest/, 'min'/min or full/);
})
};
//This file is a template that shows how to customize the KTL for your application.
//Insert the code below in the Javascript pane of your app's Builder, just after the loader code.
//Once the KTL is done loading, it will jump in the ktlReady function and apply your desired settings.
//All code must be located inside the ktlReady section.
//See GitHub's Wiki for more details.
//Your app's version.
window.APP_VERSION = '1.0.0';
window.ktlReady = function (appInfo = {}) {
var ktl = new Ktl($, appInfo);
//KTL Setup - BEGIN
ktl.scenes.setCfg({
    //versionDisplayName: '', //Short version of your app name. Leave empty to hide it. Comment whole line for actual app name.
})

ktl.core.setCfg({
    developerNames: ['Firstname Lastname'], //Add your name here to get super powers!

    //Main KTL feature switches.  Here is where your App can override the defaults and enable/disable the features.
    enabled: {
        //"Basic" features
        //Enabled by default. To disable them, their flag must exist and be set to false.
        versionInfo: {
            viShowAppInfo: false,
            viShowKtlInfo: false,
            viShowToRoles: ['Developer'], //Array of Account Roles strings who can see the version info bar. Leave empty for all.
            viPosX: 'right', //right, center, left
            viPosY: 'top', //top, bottom
            viPosXMobile: 'center', //right, center, left
            viPosYMobile: 'bottom', //top, bottom
            viOpacity: 50, //0 to 100
            viOpacityHover: 100, //0 to 100
        },

        showMenuInTitle: false,
        selTextOnFocus: false,
        inlineEditColor: false,
        rowHoverHighlight: false,
        chznBetter: false,
        autoFocus: false,
        sortedMenus: false,
        userFilters: false,
        persistentForm: false,
        calendarGotoDate: false,
        rememberMe: false,
        formPreValidation: false,
        spinnerWatchDog: false,
        idleWatchDog: false,
        debugWnd: false,
    },
})
//KTL Setup - END

//KTL callbacks to your App - BEGIN
//KTL callbacks to your App - END

/////////////////////////////////////////////////
//Your App-specific code goes here...

}

Hi,
You need to enable User Filters for this to work in your config userFilters: true,.
Charles

Thank you for your response Charles.
I will apply that.
Best regards,
Godfred Brown
On Thu, Sep 7, 2023, 15:08 Charles Brunelle @.***>
wrote:

Hi,
You need to enable User Filters for this to work in your config userFilters:
true,.
Charles
—
Reply to this email directly, view it on GitHub
https://github.com/cortexrd/Knack-Toolkit-Library/issues/99#issuecomment-1710322955,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKFEUQNVOW6SVIXJDP473D3XZHPPTANCNFSM6AAAAAA4OZFZ2U
.
You are receiving this because you authored the thread.Message ID:
@.***>

No problem.
I will open a Pull request soon because it shouldn't depend on userFilters.  Afterward, you won't need to enable this for _lf to work.
Charles

Godfred,
Can you test the latest release v0.15.12 please?  Press Ctrl+F5 to do a full refresh.
Norm


Bump gke-operator image to 1.1.1-rc3

We still need the 2.5 version of 1.0.100 in 2.6 but can be done in separate PR

https://github.com/rancher/system-charts/pull/483


Add the plotter to measurement tool menu AND visualization tool menu

Implementing the change requested by @jo-mueller with a small one liner. Closes #137

LGTM

☝


chore: update release-plz CI to use actions-rust-lang/setup-rust-toolchain

This pull request updates the release-plz CI workflow to replace the use of dtolnay/rust-toolchain with actions-rust-lang/setup-rust-toolchain. This change provides several advantages, including:

Caching support: Speeds up CI runs by utilizing Rust cache effectively.
Support for rust-toolchain file: Automatically picks the Rust version specified in the rust-toolchain file.
Ability to pin to a specific commit: Ensures stability in CI environments.
Problem matcher integration: Improves developer experience by highlighting errors inline in GitHub.

Changes:

Updated the Install Rust toolchain step in the release-plz-release and release-plz-pr jobs to use actions-rust-lang/setup-rust-toolchain@<latest-commit-sha>.
Pinned the action to a specific commit SHA for stability.

References:

See #1832
actions-rust-lang/setup-rust-toolchain documentation.

Thanks. Can you change the action for all other workflows files as well?


How to transfer density potential from one simulation to another?

Hello,
I want to calculate density/xc potential in one DFT simulation and use it in another DFT simulation. I found that it is stored on a radial grid around each atom, so it will be not compatible. Is there a way to do that? For example through the common Cartesian grid?
Thanks

You will need to give more specifics of what you want to do -- for example, if you keep the basis functions exactly the same between calculations, you can dump out the vxc matrix from one calculation and add it to hcore in the new calculation. But also this cannot be done from the inputs, you will need to be a bit of coding.

Ideally, I want to calculate one system, store the potential on a grid, e.g. electrostatic potential. Then upload this potential in second calculation of another system, which can have different number of atoms and types of atoms.

This task can be done using the code shown in example 31-xc_value_on_grid.py and
30-ao_value_on_grid.py. You need to save the weights of each grid. Then the XC
potential matrix elements can be evaluated. You need to implemented a function
similar to nr_rks or nr_uks in pyscf.dft.numint , given the required
ao values, integration weights and XC potential.
On Fri, Aug 28, 2020 at 06:30:31AM -0700, sivkov wrote:

Ideally, I want to calculate one system, store the potential on a grid, e.g. electrostatic potential. Then upload this potential in second calculation of another system, which can have different number of atoms and types of atoms.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/pyscf/pyscf/issues/689#issuecomment-682576212

--

Thank you for the help, it helps.
Another question, how can I calculate Hartree potential on a given density? I did not find such example and some part of a code where I could recognize Hartree potential calculation.
Thanks.

There is no function to compute Hartree potential in real space. There is an
example showing how to implement a function to compute this potential
https://github.com/pyscf/pyscf/blob/master/examples/1-advanced/031-MEP.py

Trying to understand how XC is calculated here
https://github.com/pyscf/pyscf/blob/6bf1664eea6da8c40302586b622ead488941e580/pyscf/dft/numint.py#L850
The first question, why do we need atomic orbital derivative? It is needed for meta kinetic contributions but not for GGA.
Then,
I understood that there is a sum aow = wv[0]*phi_ao + sum( wv[1:4] * grad_phi_ao[1:4] )
aow.shape = [Nao, Ngrids]
then we convolve like einsum("an,bn->ab",ao,aow) getting the matrix of XC potential
If I understood correctly, we calculate integrals as <phi_a|V0|phi_b> + sum_i <phi_a|V_i|grad_phi_b_i> ; i=1..3
This is not clear for me.

Sorry, but I update it.

This is by definition of functional derivatives when evaluating <i | \delta \nabla \rho / \delta \rho | j >

@dithillobothrium , thanks for posting this issue.
@dithillobothrium , @fishjojo , @sunqm , it seems this issue can be closed?


{Lab} Fix #11445: Add possible values for disk type parameter

Fixes https://github.com/Azure/azure-cli/issues/11445
Related command

Description

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Lab


tag releases?

it is currently not possible to build documentation for this package on Swiftinit as it has no semver tags.

Out of interest how is swiftinit running the dock build at the moment. I have a custom script which drags all the hummingbird package into this one package, copy the relevant symbol graph files into a separate folder and then build the docs from that. This allows me to get links between packages.
Not sure where the docc project is when it comes to generating documentation for multiple related packages

Swiftinit doesn’t do anything special for the Hummingbird repos, it just builds docs for each package individually and links them against the other packages in the database.
Swiftinit does not compile the docs with DocC, it uses a different tool called Unidoc.

I've tagged the last 1.x release 1.12.0 and I've tagged the 2.0 beta. I've kept the tags inline with the hummingbird repo, even though documentation for all the projects is contained here.
Hopefully one day I'll be able to move the docs into their actual packages and docc will be a build me a cross package set of documentation. Haven't investigated this much further recently


V3/remove this throw call transaction h

Introducing the use of assertions to address throw; calls that lack try-catch blocks. Upon examining the caller code that utilized methods containing the questioned throw; calls, it became clear that, in the current state of development, there are no scenarios where execution could reach these throw; calls. However, we cannot guarantee this for future development. For instance, if someone attempts to use getCurrentMarker() without first verifying isInsideAMarker(), ModSecurity would encounter the throw; and terminate. The issue with the other throw; call is similar in that it is, fortunately, unreachable at the moment. However, it differs because this throw; is intended to handle a case that has not yet been developed.
Fortunately, I found an article titled "Effective Use of Assertions in C++" by Mike A. Martin in (ACM SIGPLAN Language Tips, page 3), which offers a neat way to handle such cases, specifically regarding argument validation and unreachable code. Link to the article.
Following the guidance from this article, I addressed the issues and also included modifications to enrich assert error messages. Furthermore, I updated configure.ac to maintain the usual build procedure and modified README.md to introduce the new configure flag.

Just for the record: this PR fixes two SonarCloud issues in files:

headers/modsecurity/transaction.h
src/rule_with_actions.cc

I also added these references as conversation.

Please pull the modifications from #3134, and apply this PR. Or you can resolve the conflicts here.

@gberkes
Could you please address requested change to complete this issue?