feat: Docker container and Ext service relationship synthesis

Relevant information

Ticket: NR-270773
Relationship synthesis file added for Docker container and EXT service
Example EXT service: https://staging.onenr.io/0bRK94JLgQE
Example Infra Container: https://staging.onenr.io/0qwyDKnleQn

Checklist

[ ] I've read the guidelines and understand the acceptance criteria.
[ ] The value of the attribute marked as identifier will be unique and valid.
[ ] I've confirmed that my entity type wasn't already defined. If it is I'm providing an explanation above.

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


chore(package): update lerna-update-wizard to version 0.9.3

Closes #104

Pull Request Test Coverage Report for Build 319

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 314:
0.0%

Covered Lines:
588

Relevant Lines:
588

💛  - Coveralls


Add a property "errorStyle" for TextField

Hello,
I'm developing an App with material-ui and this App uses many TextFields for a big Form. The input is validated on the serverside and I get back a status like "Wrong value" etc.
Depending on the Error I'd like to color the input-field instead of red for example orange, green or yellow. At the moment I can't see any way to do that.
Is there a way there could be an "errorStyle" be added so the "color" css value can be changed from theme.errorColor to a custom one?

I added a pull request that allows you to pass a prop to Text Fields called "errorStyle"(object) which will overwrite the styles with the ones you pass. @WolfspiritM #1022

That's awesome. Thank you very much!

No problem :)

Fixed with #1079


Subdomain Enumertion Is not happening and some tools throws errors as Module Not Found

Describe the bug
I installed by following all the steps on installation guide and when I run the subdomain enumeration tools seperately .. they are running fine and giving output , but when I run the ./reconftw script there is only 0 or 1 only subdomains found as shown below

but after the script executes , I cannot able to run the tools individually also ... and I used ReconFTW before but and it worked fine , but after I update to the new version 2.5.2 I face these errors! . Is it due to the new version or anything wrong with mine ?
Im using kali linux 22.4 in virtual box , can somebody help me with this

Hi , Thankyou for responding!!

ReconFTW main ( I downloaded using git clone )
./ReconFTW -d REDACTED.COM -r -q 5
I Tried running the installer more that 5 times from yesterday
Yes I have Network Connectivity

Thankyou

Hi There ,
I think I have found the potential problem here . The resolvers.txt and resolvers_trusted.txt are empty even after running the ./install and ./reconftw scripts . I also tried to manually wget then from trickest but after running ./reconftw they again become empty as shown below. What can I do to resolve this issue

Hey! Thanks for the info provided, reconftw runs the following code in order to update the resolvers list:
https://github.com/six2dez/reconftw/blob/c8dfd2e7b944bb9806af76be7b5c7158d3f7292a/reconftw.sh#L2121-L2126
I recommend you to check if:

These commands run well if you run it manually (the wget commands).
Check your resolvers_url and resolvers_trusted_url in your reconftw.cfg, (lines 12 and 13).
There is also a update_resolvers flag on reconftw.cfg that you can set to false in order to skip the resolvers update within reconftw.

Check these steps and tell me the results, thanks!

Hi ,
Thankyou , I looked into it .... now it seem running perfectly (just the resolvers part) . but i also get this following error which I mentioned during my first message above.. It throws errors during "Permutations by regex analysis" part

I tried installing. It using pip, apt and also pipx .. but i cannot install it

Hi! I think the right package for editdistance via apt is python3-edlib, however I can install it via pip3 install editdistance. It should be installed via the installer :(


Changed barcode scanner git and doc link to new repo address

From the old repo:

Note: This repository is no longer maintained. The official repository is now at phonegap/phonegap-plugin-barcodescanner.

(Third try... hope this works.)

+1


Some problems with setting up TLS

Trying to set up a central LAPI so that the decisions can be shared among agents both in and outside of the Kubernetes cluster.
Should work with TLS authentication, but have a bit of a different way of doing things and the Helm Chart currently doesn't really support my usecase.
We have an existing cert-manager for one. Even with the examples in ./hack/tls, it's a bit tricky to make it work. So I'll try to list my findings here. We can separate those to different GitHub issues if need be.

LAPI sets CLIENT_ TLS variables, but probably doesn't need to
LAPI (and the agent) expect to find the ca.crt in the same Secret when tls.caBundle is true

This works when you have the same issuer for both agent and LAPI, since the at least with cert-manager the ca.crt will be in the same Secret.
We have a separate intermediate CA for the Kubernetes cluster the LAPI would be running in, and another one for the agents outside of the cluster, so there should be a way to define a separate root CA certificate to be trusted.

Enabling tls.certManager.enabled always creates an issuer, and there's no way to use an existing one.

In our case, there's an existing ClusterIssuer that I would like to use for fetching a Certificate for both LAPI and agents within the cluster.

I was unable to find a way to define the bouncers_allowed_ou and agents_allowed_ou, but perhaps I have missed something.
I'm also not sure about having both an Issuer and a ClusterIssuer, are both needed?

It's kind of convenient to be able to create a cert-manager ClusterIssuer or Issuer, but I would perhaps lean towards having that out-of-scope for this Chart and just document the fact for the user.

At the bare minimum, I'd need a way to define a separate CA certificate to be trusted. The other things I can probably work my way around by defining the Certificate resources and such separately.
Would of course be neater, if the Chart just supported some of the things we need, but I understand if you want to keep the setup more opinionated.
But, for example, It's kind of convenient to be able to create a cert-manager ClusterIssuer or Issuer, but I would perhaps lean towards having that out-of-scope for this Chart and just document the fact for the user.

Three things that come to mind

the CLIENT_ variables are used by cscli inside the lapi pod, not a requirement but really useful for debugging. It needs to connect even if the agent is not running. It would be neat to have a unix socket connection to simplify local clients.
bouncers_allowed_ou, agents_allowed_ou are not set correctly. The fix is in 1.5.0-rc5, see https://github.com/crowdsecurity/crowdsec/commit/68d4bdc1bd3dd775fa36791f2fb878b1dd26ea70
I am not sure it warrants a 1.4 release, unfortunately our release process is not yet geared towards small, hot-fixes
Adding an alternate CA for the client is a legitimate use case. We can easily support it in the container, but we'll be more careful to avoid adding unnecessary complications in the chart.

For the rest we have to think of the right approach
Thanks!


Added VisualStudio Code to .gitignore

It's ok to do this, but it could also be beneficial to keep that folder and some files in it, e.g. extensions.json can be used to give other users recommendations for extensions that might be useful. Or a tasks.json that comes with predefined common tasks like build or run a testserver.


Ensure both universe and the test repo exist before running upgrade/d…

…owngrade test
When testing in the super-job, we test the universe version, not the version in a test repo
cc @susanxhuynh

LGTM, thanks.


Fix analyzer errors in glfw_generator.dart

@jtmcdole one more please :)

Done.  Thanks again!
On Wed, Dec 13, 2017 at 5:38 AM, David Morgan<EMAIL_ADDRESS>wrote:

@jtmcdole https://github.com/jtmcdole one more please :)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/dart-glfw/pull/14#issuecomment-351393278, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA9VNjBslvlrYUlcJ9l8JYlb-1PTJQShks5s_9NAgaJpZM4RAjqd
.


Pointcut includes the new annotation

Codecov Report

Merging #172 into master will decrease coverage by 0.3%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master     #172      +/-   ##
============================================
- Coverage     83.48%   83.17%   -0.31%
- Complexity      190      210      +20
============================================
  Files            41       50       +9
  Lines           787      844      +57
  Branches         49       52       +3
============================================
+ Hits            657      702      +45
- Misses          112      123      +11
- Partials         18       19       +1

Impacted Files
Coverage Δ
Complexity Δ

...net/javacrumbs/shedlock/test/boot/Application.java
25% <ø> (ø)
1 <0> (?)

...n/net/javacrumbs/shedlock/test/boot/Application.kt
33.33% <ø> (ø)
1 <0> (?)

...et/javacrumbs/shedlock/test/boot/ScheduledTasks.kt
50% <100%> (ø)
1 <1> (?)

...ck/spring/aop/MethodProxyScheduledLockAdvisor.java
100% <100%> (ø)
3 <1> (ø)
:arrow_down:

...javacrumbs/shedlock/test/boot/HelloController.java
75% <0%> (ø)
1% <0%> (?)

...cronaut/internal/LockingNotSupportedException.java
100% <0%> (ø)
1% <0%> (?)

.../javacrumbs/shedlock/test/boot/ScheduledTasks.java
33.33% <0%> (ø)
1% <0%> (?)

.../internal/MicronautLockConfigurationExtractor.java
100% <0%> (ø)
9% <0%> (?)

... and 3 more

Continue to review full report at Codecov.

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


Tedious deprecation warning

Environment
Knex version:  0.21.1
Database + version: MSSQL
OS: Ubuntu 18.04.
@smorey2
Bug

Explain what kind of behaviour you are getting and how you think it should do

Not necessarily a bug, but there's a deprecation warning in the MSSQL driver. Since the driver for knex is a copypasta from the tedious mssql driver, I am not sure if this error actually occurs in the mssql dependency or in the knex driver code.

Error message

Mon, 22 Jun 2020 13:56:10 GMT tedious deprecated The default value for `config.options.enableArithAbort` will change from `false` to `true` in the next major version of `tedious`. Set the value to `true` or `false` explicitly to silence this message. at node_modules/mssql/lib/tedious/connection-pool.js:61:23

Reduced test code, for example in https://npm.runkit.com/knex or if it needs real
database connection to MySQL or PostgreSQL, then single file example which initializes
needed data and demonstrates the problem.

The test code can very simply be dumbed down to the following, assuming we have a database configuration for an MSSQL connection in the config object referenced, and assuming a table test existing in the target db.
async function() {
    const knex = require('knex');
    const db = knex(config);

    const rows = await db('test');

    return rows;
}

Upon the first query, the warning listed in 2 will be displayed.

Which node-mssql driver version are you using? Your error message is showing that it is indeed coming from dependency, not from knex.

Your reproduction case is not showing the used configuration. It is important in this case (and usually in other cases too)...

@elhigu sorry, the config is as simple as it can be.
{
    "database": {
        "client": "mssql",
        "connection": {
            "host": "db",
            "user": "sa",
            "password": "somepassword",
            "database": "somedatabase"
        }
    }
}

The database object of that is thje config. I am using mssql (not node-mssql, though we might mean the same thing) at 6.2.0

Right driver package name is actually just mssql. I suppose knex might set enableArithAbort implicitly to driver configuration. Looks like we might need to lock more tightly with knex which driver major versions are supported with each release to prevent need to add compatibility code for multiple differently behaving driver versions.

You can enable it like this:
connection: {
            host: < some hostname >,
            user: < some username >,
            password: < some pasword >,
            database: '< Database >',
            options: {
                enableArithAbort: true,
              }
        }

@piobrien I have tried that, that doesn't work for me. I have tried updating both mssql and knex, nad that doesn't do anything for me.

@david1602 That is odd, my snippet was from a working deployment with the latest versions of Knex and mssql.
My Knexfile has this and doesn't produce the depreciation message:
module.exports = {

development: {
        client: 'mssql',
        connection: {
            host: 'some hostname',
            user: 'service account',
            password: 'service account password',
            database: 'TestDB',
            options: {
                encrypt: true,
                enableArithAbort: true,
                port: 1433
              }
        }
    }
};

@david1602 If you are using a connection string instead of object, tedious won't parse it properly (happened to me)
https://github.com/tediousjs/node-mssql/issues/995

That appears to be the issue. Ugh. I guess I'll just live with the warning for now, since it's easier to deal with that than not being able to use a single environment variable.


Create 0000-01-02-moohendis.md.

layout: slide
title: "Welcome to our second slide!"
Your text
Use the left arrow to go back!

https://guides.github.com/features/mastering-markdown/


[FLINK-21903][docs-zh] Translate "Importing Flink into an IDE" page into Chinese

What is the purpose of the change
The page url is https://ci.apache.org/projects/flink/flink-docs-release-1.12/zh/flinkDev/ide_setup.html
The markdown file is located in 'docs/content.zh/docs/flinkDev/ide_setup.md' now.
The doc is still in English on the master branch.So translate "Importing Flink into an IDE" page into Chinese
Brief change log
translate 'docs/content.zh/docs/flinkDev/ide_setup.md' file
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? no

hi @wuchong  . I reopened a merge request to resolve this conflict. Thank you very very much for your suggestion.
I will learn git rebase next


How can I replace cluster id to speaker name

I need to add speaker name for each cluster. How can do this?

If you know that the speaker number correspond to your speaker name,you can add your speaker name here in advance.

thanks but I have more than 10 people. I need to add a name in predicted_label = uisrnnModel.predict(feats, inference_args)  this line

the model also recognize who is talking

Let me make sure I have it right.So you want to revise the predict function and  it can return your speaker name?

yes

Maybe you can add your speaker name which cluster_id correspond to in BeamState in uisrnn.py and use it when prediction function return the results.

I know that, in beamstate trace variable get cluster ids but its get multiple and differents values


bump to version 0.12.1

@MartijnKaijser who can review this?

when mirroring a repository original commits should be preserved. Are there any patches we need to add to original reops of libass or harfbuzz? If this is not the case, we should drop this mirror completely.

@FernetMenta need defined fopen_utf8 in ass_utils.c at least. which called by freetype246MT.lib.

ok but this change needs to be a separate commit not hidden in this big update to 0.12.1 . we need to know why patches have been made and their source.

@taxigps Freetype don't need fopen_utf8 anymore. This patch can be removed.

@Karlson2k I think freetype still need fopen_utf8 under windows platform. other wise kodi can't load fonts in some none english path.

@FernetMenta that patch already in commit https://github.com/xbmc/libass/commit/01f9b0d4c5a5820b2d61324e46a70412dabeecf2

yes, those 2 commits float on top of https://github.com/xbmc/libass/commits/master/libass and they should stay there after rebase of libass

@taxigps
See https://github.com/xbmc/xbmc/blob/master/xbmc/guilib/GUIFontTTF.cpp#L100

@Karlson2k why do we still use freetype 2.4.6 on Windows?

@Karlson2k windows system use unicode not utf-8. so freetype need call fopen_utf8 witch trans utf-8 filename into unicode to open. see readme.txt in freetype-2.4.6-win32-3.7z

@FernetMenta I think because it satisfy everybody since nobody asked for bump.

@taxigps, could you please check code at my link?

@Karlson2k so we load font in memory before call freetype. In this case, we should rebuild freetype-2.4.6-win32-3.7z to remove use of fopen_utf8.

@taxigps We don't care if fopen_utf8 is used or not.
It can be removed and not included for next builds.

then I ask again :) is there anything added to libass. If not, the sources should be removed from this repo. for a small change a patch should do as well.

@FernetMenta nothing added to libass now. and I want to add one in pull request #1 :)

This repo should be a build environment for libass on VS, right? I would bring libass in line with the other dependencies. Means remove it from this repo and update the readme accordingly. You could add a patch folder to this repo and place the libass patches there.

Yes, I think this repo just be a build environment for libass on VS now. And I need export function ass_set_line_position so kodi can call it to set subtitles position use setting "subtitles.align", how to do this now? and when can I add the patch in #1 ?

remove folder libass, create a folder patches and place your patches in this folder. then update readme with build instructions.

see #3


Inspector does not work in either IE11 or Edge

To reproduce the issue, open up the PG in IE11 or Edge and view the debug layer.

Ping @Temechon : Is that something you can work on ? I try to close all issues before 3.1

I'll see what I can do, but debugging IE/EDge is very difficult as the browser crash as soon as the console is opened...

For IE This may require a win7 install:(

Up?

I'm on it but like @Temechon when I launch IE it crashes directly, I'm looking for a solution.

The only way I know of to debug IE11 issues is by using Visual Studio.

or with a win7 build

Color picker is the culprit input type="color" makes it crash please disable on IE

Didn't see your comment but came to the same conclusion! Thank you :)
It's fixed now.


Parsing Error Rendering Documentation

I am receiving the following error when attempting to render the boilerplate API Blueprint file mentioned in the docs. This file is saved as test.apib at the root of my project.
Argument 1 passed to M165437\BlueprintDocs\Elements\Api::__construct() must be an instance of Hmaus\Reynaldo\Elements\ApiDescriptionRoot, null given, called in /var/www/vendor/m165437/laravel-blueprint-docs/src/BlueprintDocs.php on line 88

My Laravel version is 5.8 and my Drafter version is v4.0.0-pre.5
Below is my configuration:
<?php

return [
    'route' => 'docs',
    'condense_navigation' => false,
    'blueprint_file' => base_path('test.apib'),
    'drafter' => base_path('vendor/bin/drafter')
];

The issue seems to be that this parseRefract method is returning null https://github.com/M165437/laravel-blueprint-docs/blob/master/src/BlueprintDocs.php#L74
because this getFirstElementByType method is returning null https://github.com/hendrikmaus/reynaldo/blob/master/src/Elements/ParseResultElement.php#L9.
Digging deeper, this seems to be caused by this conditional never being true (https://github.com/hendrikmaus/reynaldo/blob/master/src/Parser/RefractParser.php#L147) because this method call (https://github.com/hendrikmaus/reynaldo/blob/master/src/Parser/RefractParser.php#L166) is failing to detect the "Master Category" of the document.
If I add a dd($className, $element); above this line (https://github.com/hendrikmaus/reynaldo/blob/master/src/Parser/RefractParser.php#L180), the output is attached.
dd_output.txt
As you can see from the attached output and the hasClass method, the "api" class is not being found because the method expects the content of $element['meta']['classes'] to be a string, but it's actually an array.
Can someone please help me debug this?

I was using a pre-release of drafter, hence the breaking changes. I downgraded to Drafter v3.2.7 which resolved the issue 👍

see https://github.com/hendrikmaus/reynaldo/pull/4


release sync: 0.39.x

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind cleanup

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build
/area engine
/area tests

What this PR does / why we need it:
Sync for 0.39.0 release
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

NONE

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [LucaGuerra]

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

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,LucaGuerra]

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

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, FedeDP, LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,FedeDP,LucaGuerra]

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

/milestone 0.39.0


Load drains

There seems to be an issue wiht using PUC_Maximo_Asset_ID. These IDs all start with N- and I believe the schema expects a numeric type.
Three options I see here:

Remove "N-" and load the remainder, if we need to present this to a PUC user we can just add N- to the Node ID in the report/interface, not sure if that's going to be necessary yet anyway
Flip back to DPW_Node_ID, similarly, we can crosswalk this later, but probably more work to crosswalk technically than to just present the ID and prepend N-
Modify schema to accept a string

Seems simple enough. Though, relies on a known-convention.
Also simple. Not sure what the use cases and reporting needs are here.
Least feasible.  Easy to do for this instance, but creates and awkward fork and a need to PR core with a significant change.

Another options is to add an external_id -like field that is a string, and PR that upstream, which I'd guess would be more feasible. We can ask @sferik.

@afomi I probably wouldn’t merge a patch to migrate external_id to a string type upstream but obviously feel free to make this change in this fork, if that’s the path of least resistance.
Generally speaking, I only merge patches upstream that add some value to Adopt-a-Hydrant in Boston because that’s their actual codebase. It’s not clear to me that making things more generic in this way would have any tangible benefit to the City of Boston and I can think of a couple disadvantages.
It’s best to think of Adopt-a-Hydrant Boston as a reference implementation, rather than a generic template.

Thanks for the prompt feedback @sferik! We'll proceed accordingly.

Seems like modifying the schema to use a varchar for this field is the best route, what do you think @afomi ?

ya, varchar seems simple. I'll try to knock this out this weekend.

I didn't do much here except to only load drains if they are either:

Storm Water Inlet Drain
Catch Basin Drain

This is 98% of the drains, but keeps out the unadoptable ones. Also, I didn't do anything regarding the city_id.

The N- will now be removed. Will this load work, or does data need to be migrated?

21364 Drains loaded for adoptadrainsf.herokuapp.com


Why is tanh not used as activation at the last layer of generator?

The DCGAN paper mentions about the use of tanh. Is there any reason why it is not used? What is the difference in the results in both cases.
Thank you.

More specifically in the below line of code.
x = (self.dc4(h))

the last layer in the generator is tanh because it making value between -1 and 1. and make over the network is more stable in the case of color image and video.


feature request: support URL objects

Modern Node.js APIs have first support for Web Standard URL objects, so it would be useful to have this interface in this plugin as well.
import { defineConfig } from "vite";
import react from "@vitejs/plugin-react";
import { viteStaticCopy } from "vite-plugin-static-copy";

// https://vitejs.dev/config/
export default defineConfig({
  base: "/fml-web/",
  plugins: [
    viteStaticCopy({
      targets: [
        {
          src: new URL("lib/foo.wasm", import.meta.url),
          dest: new URL(".", import.meta.url),
        },
      ],
    }),
    react(),
  ],
});

While I think accepting URL objects is useful, I think there's multiple things that needs to be considered.

src receives a glob. It's not a file path.

If a URL object is passed, should it be treated as a file path? or a glob?
Should it receive URLPattern as well?

Rollup doesn't receive URL objects. Few people would recognize that src/dest can receive URL objects.


Have to request permission on each run

Whenever we are using any feature from the plugin such as showOverlayWindow, performGlobalAction, etc. we have to request permission again, on each run.
Expected Output: We should be able to request the permission once, and it should not be required for future runs, unless user manually revokes the permission, or the app gets deleted.
Also, if this gets implemented, it would be great to have revokeAccessibilityPermission as well.
By the way, huge thanks for building this, as this takes care of all the heavy lifting we'll have to do to implement Accessability service in Flutter.

hello did you try it on release mode cuz I think this related to only debugging

Yes, after some digging I found out that as well. Accessability service gets stopped when we stop debugging, as it basically force stops the debugged app.


[Suggestion] Doesn't Play Well with Mono-Repo Projects (Lerna)

Hello,
Currently our project uses lerna to manage our mono repo of several sub-packages. So we have the following project structure:
root
-- package.json
-- packages
-- -- subPackage1
-- -- -- package.json
-- -- subPackage2
-- -- -- package.json
-- -- etc.

However, we "hoist" all of our dependencies so that when we install all the dependencies, the structure looks like this:
root
-- package.json
-- node_modules <---- where all of the dependencies are installed for all sub packages
-- packages
-- -- subPackage1
-- -- -- package.json
-- -- subPackage2
-- -- -- package.json
-- -- etc.

This means that when I run electron-rebuild from the root to try to rebuild a dependency of subPackage1, electron-rebuild checks the package.json inside of /root to see if the package is a dependency, and can't find it. This is because it is actually declared as a dependency of subPackage1 inside of root/packages/subPackage1/package.json. That means that I have to add the dependency to the root package.json just so that electron-rebuild can find it and rebuild it, even though it's in the root /node_modules/ directory where it is scanning.
It would be great if I could tell electron-rebuild what package.json to check against when scanning so that I wouldn't have to declare the package as a dependency in my root directory just to satisfy electron-rebuild.
Example:
electron-rebuild --module-dir . --package-json ./packages/app/main/package.json

Nevermind, I figured out how to accomplish this.
In my case I had to run the following command from the root/packages/subPackage1/ directory:
../../node_modules/.bin/electron-rebuild -w <packageName> -m ../..
This way it checks the dependency list of root/packages/subPackage1/package.json but looks for the dependency to rebuild inside of root/node_modules/.

Yes, this is very much needed. For me, electron-rebuild runs, doesn't do anything, and exits with a green checkmark. This is really annoying.

This wasn't working for me. The install hook won't run if it's not declared in the root package.json and I run yarn install from the root (sometimes I run yarn install from my package root).
After adding the install hook to the root package.json, along with electron, electron-rebuild, and serialport, under dependencies, then it finally rebuilt correctly.

Same problem with yarn workspaces.


Tensorflow serving

/kind feature
I am currently preparing serving for a tensorflow model which is using SCANN library.
As process of model training is automated through KF pipelines, builded model is stored on minio.
In that case I want to use tensorflow kfserving to be able to load model from this storage.
However, using SCANN with TFserving requires custom docker image, prepared by Google - link.
It would be great to possibly pass custom image to TFserving.

@jw-websensa this is possible today, on tensorflow spec you can pass the image field provided the assumption that startup arguments are still the same.
apiVersion: "serving.kubeflow.org/v1beta1"
kind: "InferenceService"
metadata:
  name: "scann"
spec:
  predictor:
    tensorflow:
      image: google/tf-serving-scann:latest
      storageUri: "gs://kfserving-samples/models/tensorflow/xxx"

Thank you @yuzisun, is it also possible from v1alpha2 api?

@jw-websensa nope, only supported on v1beta1


MSRV?

What's the minimum stable Rust version supported by this library? I've dug through the docs a bit and hadn't spotted any mention of a version.

Not sure. How would one go about figuring this out? It requires std::arch::asm stabilization for x86 targets if that helps.

Uh, there's probably more sophisticated ways to do so, but for serial_test I mostly just tested with various Rust versions, and then added a CI check to make sure the declared MSRV still kept worked.
Although https://doc.rust-lang.org/stable/core/arch/macro.asm.html does say 1.59.0, so that's probably a good place to start :)

Hm, 1.59.0 builds fine. It seems to reliably cause an issue that I thought had only shown up in the test suite under sanitizers, though.

https://github.com/kprotty/usync/pull/11 adds a test/badge for 1.59.0, but I'm also seeing a test issue locally.


Test with julia v1.7

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@e5b0ccb). Click here to learn what that means.
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff            @@
##             master     #20   +/-   ##
========================================
  Coverage          ?   0.00%
========================================
  Files             ?       6
  Lines             ?     507
  Branches          ?       0
========================================
  Hits              ?       0
  Misses            ?     507
  Partials          ?       0

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.


Bug fix or and "<=>" cause coredump in query

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Unable to change Source schema

Describe the Bug with repro steps

Create a new data mapper
Add source and target schema
Once added, change the source schema from Settings->Edit Source schema
After I select new schema, I do not see it reflecting in the dialog box
Also, the new schema is not properly loaded and is not overwriting the old schema as it should

(Please find recording attached)

Screenshots or Videos
https://github.com/Azure/LogicAppsUX/assets/80121421/cf39f568-15ef-4887-aac3-cad76610b507
Version
using logic app standard extension
Additional context
Expected behavior:

Browse should reflect schema as I upload it (not when I switch options and then it shows as in the video)
Old schema should be overwritten, but it does not

Able to reproduce this one, will start looking into a fix

Hi @shahparth-lab thanks for reporting this issue! We will take a look at fixing it. As a workaround for now, you can always copy the file into your "Schemas" folder and add it with "Select existing"


Add the ability to override the server that's used by a given SyncSession

This is for internal use by ROS as part of its support for failover. If the SyncSession is active, we ask the underlying sync::Session to disconnect and reconnect to the new server. We also stash away the overridden server's details so it can be used again we later disconnect and reconnect. If the session is not yet active, we simply stash away the details to be used when establishing the connection.
Fixes #563.
Blocked on getting the necessary sync API added (https://github.com/realm/realm-sync/commit/1f08d1534cc340c3e4303b24d14b0be6c7de906e, but there's no corresponding PR at this time).
Not yet ready for review. Still needs:

[ ] Testing
[x] Documentation

Testing this is a little bit complicated as we need to fake having a second server with the same server-side state as the first server. We can likely simulate this by just listening on a second port and proxying all of the data received over to the real server. I've tested it manually by doing the proxying using nc, and have started work on adding unit tests, but they're much more involved than the code change itself was.

@bdash I am merging now, and I hope you will have time to finish the tests.


git-release-manager - version:bump to v1.29.2

Backstage release v1.29.2 has been published, this Pull Request contains the changes to upgrade git-release-manager to this new release
Please review the changelog before approving, there may be manual changes needed:

Changelog: v1.29.2
Upgrade Helper: From 1.26.0 to 1.29.2

Created by Version Bump<PHONE_NUMBER>5

Hi @erikengervall, I'm not sure why the tests are failing? Could you give me a hand, please? I'm just doing a version bump to get the plugin up to the latest Backstage version.

Hi @erikengervall, I'm not sure why the tests are failing? Could you give me a hand, please? I'm just doing a version bump to get the plugin up to the latest Backstage version.

Judging by the CI logs it seems that upstream package upgrades has updated some of the classnames of some components which I seem to have built snapshot tests for. Updating the snapshots would resolve the issue.

Thanks @erikengervall, that got me heading in the right direction 🚀


Feat: ui.time_picker component

This PR introduces a new ui.time_picker component with the following API:
export interface TimePicker {
  /** An identifying name for this component. */
  name: Id
  /** Text to be displayed alongside the component. */
  label?: S
  /** A string that provides a brief hint to the user as to what kind of information is expected in the field. */
  placeholder?: S
  /** The time value in hh:mm format. E.g. '10:30', '14:25', '23:59', '00:00' */
  value?: S
  /** True if this field is disabled. */
  disabled?: B
  /** The width of the time picker, e.g. '100px'. Defaults to '100%'. */
  width?: S
  /** True if the component should be visible. Defaults to True. */
  visible?: B
  /** True if the form should be submitted when the time is selected. */
  trigger?: B
  /** True if this is a required field. Defaults to False. */
  required?: B
  /** True if time picker should use a 12-hour time format. Defaults to True. */
  time_format_12h?: B
  /** The minimum allowed time value in hh:mm format. E.g.: '08:00', '13:30' */
  min?: S
  /** The maximum allowed time value in hh:mm format. E.g.: '15:30', '00:00' */
  max?: S
  /** Limits the available minutes to select from. One of `1`, `5`, `10`, `15`, `20`, `30` or `60`. Defaults to `1`. */
  minutes_step?: U
}

https://user-images.githubusercontent.com/23740173/189341542-910f1376-5be7-42ab-a5d9-664c0dd9df16.mov

The part I don't like is that AM/PM is part of the API, and that time_format_12h affects the return value, not just the display of hours.
I would keep it simple and restrict value, min, max and the return value consistently to 24-hr hh:mm time format, similar to how the date picker restricts it to the ISO 8601 date format. This will simplify the front-end code (no AM/PM parsing), and is also one less thing to reason about when processing the submitted date in Python.
Notice that the examples in the PR are confusing at the moment - should there be a space before AM/PM, or not? The examples / docs use both.
The time_format_12h can be renamed to hour_cycle (one of 12 default, or 24), similar to the naming used by Intl.DateTimeFormat. It should only affect the hour display, not the return value. For example, allow the user to pick 6:45 and PM, but submit 18:45.

Thanks @lo5 for making this simple and consistent! Just one note - the plan was to have hour cycle defined as you proposed but then there is an issue after generating a types.py where
class TimePickerHourCycle:
    12 = '12'
    24 = '24'

which is not a valid python code since Expression cannot be assignment target.
Is it worth handling in wavegen.ts or can we stick with an already implemented time_format_12h boolean?

Is it worth handling in wavegen.ts or can we stick with an already implemented time_format_12h boolean?

Define hour_cycle as string instead of '12' | '24'. I don't like the boolean time_format_12h because 11 and 23 are valid hour cycles (we don't have to support them today, but someone might bring this up in the future).

Thanks for a deep review @mturoci!

Note that when you create a docs page for a new component (time_picker.md), it needs to be added here.

Should it be also present in website/widgets/overview.md and py/examples/form.py?

Should it be also present in website/widgets/overview.md and py/examples/form.py?

Yes, thanks.


Update athena-workgroups.tf

Add component tag to Athena workgroups
Remove sub-folder for Athena logs

Pull Request Objective
This piece of work is being tracked in this Slack thread.
Additional tags on Athena workgroups will allow for a more granular cost analysis.

Checklist

[!NOTE]
Each items should be checked. Skipping below checks could delay your PR review!

[X] I have reviewed the style guide
and ensured that my code complies with it
[x] All checks have passed (or override label applied, if I've
used the override-static-analysis label, I've explained why)
[X] I have self-reviewed my code
[x] I have reviewed the checks and can attest they're as expected

Additional Comments

Resubmitted as https://github.com/ministryofjustice/analytical-platform/pull/5616 with fully verified code commit


Add information on the build environments and configurations

Could help with the reproducibility of the builds. Might require some rebuilding to be sure of the reported configurations.

The thrift-binary repository now builds the binaries using actions.


Order of posts displayed on homepage

Should be using time of creation instead of last modified time

Fixed in PR #31


Correctly deal with unknown blocks when initializing ledger DB in presence of EBBs

When we initialize the ledger DB, it is possible that a ledger DB on-disk snapshot refers to a block that is expected to be present in the immutable DB, but isn't. When this happens, we should discard the snapshot and try to use an older snapshot instead.
This was already implemented, but the way we checked whether the block was present was by comparing slot numbers. If the slot number of the Point required by the ledger DB was present in the immutable DB, we assumed that the block must be present. This isn't correct, however. It is possible that the immutable DB contains an EBB of that slot, by the ledger DB snapshot refers to the regular block in the same slot. In this scenario, initialization of the ledger DB failed with an internal error, and we would not attempt to try an earlier version.

Note that there are two ways for the on-disk ledger DB snapshot to refer to a block that is intended to be in the immutable DB, but isn't:

Data loss in the imm DB
We take a snapshot of the ledger DB, but haven't yet copied all now-immutable blocks from the volatile DB to the immutable DB.

Note that (2) is not actually all that unlikely now that we take a ledger DB snapshot when we shut down the node. We should think about this.

Closed in #1451.


Concepts: Declarative Multi-Stage Delivery still shows the super old shipyard format

When navigating through the docs, I found this example:
stages:
  - name: "dev"
    deployment_strategy: "direct"
    test_strategy: "functional"
  - name: "hardening"
    deployment_strategy: "blue_green_service"
    test_strategy: "performance"
  - name: "production"
    deployment_strategy: "blue_green_service"
    remediation_strategy: "automated"

at
https://keptn.sh/docs/concepts/delivery/
This example is not supported since Keptn 0.8, so a good while.
Definition of Done

[ ] Rewrite https://keptn.sh/docs/concepts/delivery/ such that it fits the current shipyard concept

stale


RuntimeError: size mismatch at /opt/conda/conda-bld/pytorch_1512386481460/work/torch/lib/THC/generic/THCTensorMathBlas.cu:243

When I ran 'Auxiliary Deep Generative Model.ipynb', I met this problem:
RuntimeError                              Traceback (most recent call last)
 in ()
13             u = u.cuda(device=0)
14
---> 15         L = -elbo(x, y)
16         U = -elbo(u)
17
~/miniconda3/envs/pytorch/lib/python3.6/site-packages/torch/nn/modules/module.py in call(self, *input, **kwargs)
323         for hook in self._forward_pre_hooks.values():
324             hook(self, input)
--> 325         result = self.forward(*input, **kwargs)
326         for hook in self._forward_hooks.values():
327             hook_result = hook(self, input, result)
~/code/baidu/semi-supervised-pytorch/semi-supervised/inference/variational.py in forward(self, x, y)
86         ys = self.sampler.resample(ys)
87
---> 88         reconstruction = self.model(xs, ys)
89
90         # p(x|y,z)
~/miniconda3/envs/pytorch/lib/python3.6/site-packages/torch/nn/modules/module.py in call(self, *input, **kwargs)
323         for hook in self._forward_pre_hooks.values():
324             hook(self, input)
--> 325         result = self.forward(*input, **kwargs)
326         for hook in self._forward_hooks.values():
327             hook_result = hook(self, input, result)
~/code/baidu/semi-supervised-pytorch/semi-supervised/models/dgm.py in forward(self, x, y)
155
156         # Latent inference q(z|a,y,x)
--> 157         z, z_mu, z_log_var = self.encoder(torch.cat([x, y, q_a], dim=1))
158
159         # Generative p(x|z,y)
~/miniconda3/envs/pytorch/lib/python3.6/site-packages/torch/nn/modules/module.py in call(self, *input, **kwargs)
323         for hook in self._forward_pre_hooks.values():
324             hook(self, input)
--> 325         result = self.forward(*input, **kwargs)
326         for hook in self._forward_hooks.values():
327             hook_result = hook(self, input, result)
~/code/baidu/semi-supervised-pytorch/semi-supervised/models/vae.py in forward(self, x)
55     def forward(self, x):
56         for layer in self.hidden:
---> 57             x = F.relu(layer(x))
58         return self.sample(x)
59
~/miniconda3/envs/pytorch/lib/python3.6/site-packages/torch/nn/modules/module.py in call(self, *input, **kwargs)
323         for hook in self._forward_pre_hooks.values():
324             hook(self, input)
--> 325         result = self.forward(*input, **kwargs)
326         for hook in self._forward_hooks.values():
327             hook_result = hook(self, input, result)
~/miniconda3/envs/pytorch/lib/python3.6/site-packages/torch/nn/modules/linear.py in forward(self, input)
53
54     def forward(self, input):
---> 55         return F.linear(input, self.weight, self.bias)
56
57     def repr(self):
~/miniconda3/envs/pytorch/lib/python3.6/site-packages/torch/nn/functional.py in linear(input, weight, bias)
833     if input.dim() == 2 and bias is not None:
834         # fused op is marginally faster
--> 835         return torch.addmm(bias, input, weight.t())
836
837     output = input.matmul(weight.t())
RuntimeError: size mismatch at /opt/conda/conda-bld/pytorch_1512386481460/work/torch/lib/THC/generic/THCTensorMathBlas.cu:243
Can you give me some suggestion? What's more, I wanna know the version of pytorch in your code and I'm using the version pytorch-0.3.0-cuda80.

If you didn't change anything in the notebook then I find this error strange. It looks like the number of neurons in the hidden layer of the encoder for the z variable does not match, in any case it needs an input of size x.size() + y.size() + a.size(). I think I used pytorch-0.3.0 back when I developed it, but I recently had students make it work with pytorch-1.0.0 (though with some warnings).


fixed API urls

@eisber : Thanks for your contribution to the Azure documentation! The author, @slivkins, has been notified to review your proposed change.

sign-off

#sign-off


api 19 & 22 thumb issue

first of all thank you for the amazing library
I am showing and hiding the thumb based on a user action, but when it appears
on android 4.4 api 19 the thumb is appearing huge, and on api 22 it is not appearing at all.
is there a fix that you would suggest?
and also, I wanted the bar to be very thin so I made the width 1. but on api 19 it appears pretty thick compared to all other android versions.
Thank you again
BTW I copied the library and changed things a little bit to fit my needs for example, my layout rotates rotates independent from the orientation so I had to change the thumb ontouch method to work with all different orientations. I hope you don't mind

removing the radius of the thumb made it normal size again, and replacing the barCardView with a linearlayout fixed the bar size problem

Hi! Can you share an example of the issue?
Thank you


consider working together on ruby-sys

Hey yinz,
Psyched to see this become an actual thing!
For another "Rust in Ruby" project, I recently extracted https://github.com/steveklabnik/ruby-sys . From looking at your vendored libmrisys, it looks like it's got almost all the same stuff. Maybe we can make the two compatible, so you don't have to worry about the bindings anymore?

There's also https://github.com/dylanmckay/mri-sys which is used by https://github.com/dylanmckay/rurust (embedding Ruby in Rust, rather than extending Ruby using Rust).
Along similar lines to rurust, there's https://github.com/anima-engine/mrusty (embedding mruby, rather than mri) - if helix ever grows support for embedding, it may be worth looking at how mrusty handles injecting things into the runtime (it injects virtual files, which can be loaded with require from the embedded Ruby interpreter).

👍 in principle
There are a few challenges. The main one is that a lot of "functions" in CRuby are actually macros. Obviously, we don't have access to those at runtime, so we need a glue layer to "re-export" them as functions/named symbols so they can be called from Rust.
How this works now is that we ship a small C-extension called helix_runtime that we build on the end-user's machine using the standard C compilation toolchain.
If we were to merge the code we also need to move that extension and keep that in-sync with the Rust binding.
Also 👍 on figuring out the grand unification between supporting both C Ruby and mruby. (@hone02 will be interested in this.)

so we need a glue layer to "re-export" them as functions/named symbols so they can be called from Rust.

Yeah, this is tough. The aproach ruru has taken is to just port them, but that can be a bit of a problem, if things diverge...

One would hope that if things diverge, it would happen in a major version bump of Ruby, but I guess that's not necessarily the case.

I'm definitely interested, but my impression is that the mruby/mri API is fairly different.

Seems like we could still use ruby-sys, if we wanted to. I'm not sure if it gains us a huge benefit right now, but any sort of standardization sounds beneficial. One thing work considering is how this would interact with our efforts for safe function calls in #64. @steveklabnik

I'm not sure if it gains us a huge benefit right now, but any sort of standardization sounds beneficial.

I feel like it benefits users more than each project, that is, it's more about the interop than anything else.
Stuff has stagnated for me a bit lately, but I'm still down. I've been wanting to look into https://github.com/steveklabnik/ruby-sys/issues/14 sometime soon, but my spare open source time has been.... small lately 😦

@steveklabnik :+1: Seems worth giving it a shot.


added test case to waypoint

Closes #4866

I love your PRs, but you need to do two things:

Have a more descriptive title that includes the waypoint name

"added test case to waypoint" could be about anything

Describe the change in your PR body, especially if you tested locally or not.

I did test this and it worked well.
However, looks like you'll need to rebase to deal with some merge conflicts.

Can I submit a new PR and delete this one? I think I messed up my local repo with rebase command.

Sure just close this one and submit the new one

Closing as per user request.


Reddit Bridge - single displaying the author of the post.

Hello!
Thank you for your work!
For some reason, the author of the post is not displayed in any of the tested RSS readers.
But the author is displayed in the RSS bridge web interface.

I realized my mistake!
Instead of Mrss, you need an Atom.


Automated cherry pick of #9435: fix(host): fix set windows password with escape charater

Cherry pick of #9435 on release/3.4.
#9435: fix(host): fix set windows password with escape charater

/lgtm
/approve


Bug on multipage export

Hi,
Please see the screenshot below where the Title and Issuer field is overlapped when exporting to multipage.

Closing this in favor of Reactive Resume v3 release.
If you continue to face this issue, please raise a new one and I'll have a look at it as soon as I can.
In the meantime, if you are able to, please consider donating to keep supporting the project: https://www.buymeacoffee.com/AmruthPillai :)
Thank you!


Can't get SOLR to work

There was an error loading a Vagrantfile. The file being loaded
and the error message are shown below. This is usually caused by
a syntax error.

Path: /Users/leequessenberry/Sites/ecbarton.test/Vagrantfile
Line number: 0
Message: Psych::SyntaxError: (/Users/leequessenberry/Sites/ecbarton.test/default.config.yml): did not find expected key while parsing a block mapping at line 10 column 1

Issue Type

Bug Report / Support Request

Your Environment

Vagrant 2.0.3
VirtualBox 5.1.10r112026
zsh: command not found: ansible

Your OS

macOS (version)

Full console output
> $ vagrant reload --provision                                                                                ⬡ 6.11.4 [±master ●]
There was an error loading a Vagrantfile. The file being loaded
and the error message are shown below. This is usually caused by
a syntax error.

Path: /Users/leequessenberry/Sites/ecbarton.test/Vagrantfile
Line number: 0
Message: Psych::SyntaxError: (/Users/leequessenberry/Sites/ecbarton.test/default.config.yml): did not find expected key while parsing a block mapping at line 10 column 1

Summary
I am just trying to get a simple search API with SOLR set up and nothing seems to work. When I uncomment the line in the config file, I get the above error. I am not sure what I am missing.

# Run specified scripts before or after VM is provisioned. Use {{ playbook_dir }}
# to reference the provisioning/ folder in Drupal VM or {{ config_dir }} to
# reference the directory where your `config.yml` is.
pre_provision_scripts: []
post_provision_scripts: []
  - "{{ playbook_dir }}/../examples/scripts/configure-solr.sh"

https://puu.sh/zKZy0/b07a3f8a20.png

@lquessenberry Remove the [] in addition to uncommenting
post_provision_scripts:
  - "{{ playbook_dir }}/../examples/scripts/configure-solr.sh"

That was the trick. I ran it into a linter to check and we're good to go. I am still relatively new to YAML.


introduce cli commands starting with "run"

currently, the couper binary is just the server. starting the binary ./couper starts the server.
in the future, we will most likely need more commands to be incorporated into the binary, e.g. couper validate.
for now, we should start the server with the sub command run:
$ couper run -f couper.hcl

see #11


SSL Support

This PR adds SSL Support, including relevant demos and tests @jkyberneees

This is awesome!


App crashes while scanning QR code from showcase

Description of problem
On Android: When scanning the QR code that issues the credential, the app crashes. The credential offer however, does appear after opening the wallet up again.
On iOS: When following the lawyer use case, getting the credentials and revoking one of them, the app crashes after scanning the proof request QR code
Expected behavior
Steps to reproduce
Android

Go through any of the showcase flows and try to scan the credential QR code
The app will crash
open it again and you'll see the credential offer

iOS

Go through the showcase flow
get the credential(s)
revoke one of them
Scan the proof request QR code
the app will crash

Screenshots and/or log output
Environment

[x] Occurs on Android
[x] Occurs on iOS

Build #: 1792
Android Device Model: pixel 8
iOS Device Model: iPhone SE
Workaround
Severity

[x] High
[ ] Medium
[ ] Low

Checked both iOS and Android. Seems to work fine now.


add check balance feature

can someone develop  vanityEth to add unlimited checking balance feature ! is that possible ?
thanks

It is almost impossible to generate wallets with an existing balance. This tool is not meant for brute forcing


Add .bumpversion.cfg to support automated bumping of the version in meta.yml

tudatpy GitHub repository will execute the below bump version command to tudatpy-feedstock nightly when there are new commits received on the develop branch in the last 24 hours.
bump2version dev --config-file .bumpversion.cfg --verbose
This command will bump the version and git_rev in recipe/meta.yml in develop branch of tudatpy-feedstock, create a tag, and push the tag to tudatpy-feedstock.

Changes in branch https://github.com/tudat-team/tudatpy-feedstock/tree/19-add-bumpversion-cfg

Closing as changes merged in pull request https://github.com/tudat-team/tudatpy-feedstock/pull/20


Update Laravel Framework to 6.0

Resolves #1301

This could use a more serious review since it's a fairly major update

Looks Gucci to me as well.


devcontainers broken with latest chromadb

Describe the bug
Running make backend in the devcontainer results in an error:
Your system has an unsupported version of sqlite3. Chroma requires sqlite3 >= 3.35.0.

The problem arises because the dev (and demo) containers are using Debian bullseye which includes sqlite3 3.34.1, whereas we'd need Debian bookworm to meet that requirement (reference https://packages.debian.org/search?keywords=sqlite3 )

Hey @mieslep !
How are you?
I've seen some reports of that in the last few days. Let me see what we can do.

This should be fixed now.

Hmm okay so https://mcr.microsoft.com/en-us/product/devcontainers/python/about 3.10 and 3.10-bookworm are equivalent then the PR I have is redundant.
I far prefer devcontainers for complex project like this and Langchain... there's a lot of complexity in setting up dev environments and this dramatically simplifies things. Plus, being on Windows, it makes things dramatically simpler in a devcontainer :)

I see!
I used to use them quite a bit when I had a Windows machine but it has been a while since I used it and only contributors currently use the Langflow devcontainers.
Happy to know it is working.
Let me know if there are any improvements we should make.
I love my tasks setup for VSCode. Maybe I'll add them to the repo too.


*: expose StreamingCallSink into documents.

Previously we can't see StreamingCallSink in document. This PR fix this.

@BusyJay , PTAL, thanks.

LGTM

LGTM

/run-all-tests


Unable to authenticate

In older versions of the game (only tested in b1.7.3 and b1.6.6), while using LaunchWrapper, the game is unable to authenticate the player on Multiplayer servers. The server does have online-mode patched and it works with the Betacraft proxy for example, but it always fails to verify the user while using LaunchWrapper, resulting in the "Failed to verify username!" screen while trying to join the server.

Please test with latest commit. Contact me on Discord @lassebq if you're looking for builds

Can confirm, authentication works now.


Detected usage of a non-sanitized input variable: when esc_url() is used

I get a "Detected usage of a non-sanitized input variable:" error on this line:
$featured_embed_url = esc_url( wp_unslash( $_POST['foo'] ) ); // input var okay

Does esc_url() count as sanitizing?

No, esc_url() is not a sanitizing function, it is an escaping function. There used to be a sanitize_url(), but it has been deprecated in favor of esc_url_raw(). I think that esc_url_raw() would be the correct function to use to sanitize a URL for the database/redirect/other use, while esc_url() would be used to escape it for display. And in fact, esc_url_raw() is already in our list of sanitizing functions, so if you change this to esc_url_raw() the error should go away. :smile:

That fixes it. Thanks!


How to set the filename using multipart form data and raw stream of buffer?

Sending form data works well when using streams created with fs but I'm actually trying to upload data from a Node buffer, and unfortunately that doesn't work well.
It seems that I'm missing the part where the filename is specified in the form data, and I found nothing in your source code to help.
When transmitting form data, it should look like this:
'Content-Disposition: form-data; name="file"; filename="myfile.ext" [...]

What I'm actually missing is how to set the filename="myfile.ext" part without using a stream from fs?

In any case someone needs it, here is the solution:
popsicle.form only support uploading files using standard file stream, to work with buffer or other stream type you need to use form-data directly:
    const form = new FormData();
    form.append('file', mystream, {
      filename: myfilename,
      knownLength: myfile.length
    });

@sinedied popsicle.form returns an instance of form-data, so it allows all the same features to work as you've just used. Just call const form = popsicle.form() and append after it.

I'd love to improve the README with this note! 😄

popsicle.form is undefined in popsicle 12.0.1

@Obapelumi You can use form-data directly nowadays. This was largely before form-data has a browser aliased version (e.g. https://github.com/form-data/form-data/blob/d7026253e728af9568503dc3dc55cd1a566605e0/package.json#L11).


Feature: Interactive Coding while in Debug

Would be really nice to have this option.  I'm working on a multi-nested loop, hit a break point, be great to try out a few options right there, get it fixed, and keep moving.

have your checked out the "Debug Interactive" feature?
https://github.com/Microsoft/PTVS/wiki/Debugging

I think this refers to "Edit and Continue" available for C#, VB.NET, and C++:
https://github.com/Microsoft/PTVS/issues/77

this question was raised about 3 years ago ,i wonder if the ENC available now?


DOC: add ACSetInterface to docs

This PR adds the ACSetInterface file to the docs markdown so that the doscstrings in ACSetInterface.jl will build in the documentation.

I've been able to successfully build this locally and it includes the appropriate doc strings

Thanks Andrew!


[docs]fix some apostrophe in typescript doc

[x] I have followed (at least) the PR section of the contributing guide.

The -es.md suffix indicates that this is used for the translated version. It's simply missing a translation. Please see https://github.com/mui-org/material-ui/pull/15754#issuecomment-493923705 and either change the original typescript.md or file an issue in crowdin.

@eps1lon Thanks. Sorry was editing the wrong file. Pushed my changes now :)

Please remove the changes to the -es.md file.

Please remove the changes to the -es.md file.

Thanks. done~


re-implement tx indexing

The tx indexing and query system was removed to attempt a more modular and minimal implementation.
The goal I have in mind is to simply log to file all EventSwitch events (serialized using amino:binary, using protobuf for speed), and then to make readers that can idempotent-ly index or filter these events for whatever purpose, including tx indexing, but also streaming of filtered events (from the RPC using websockets, say). These streaming readers would be independent processes from the full node, so there would be possibly no resource contention depending on the configuration. Since log files could be read by any process, the node wouldn't even have to know who are the listeners are.
We could possibly use an existing persistent pubsub system to implement this, but if we're going to use such an external dependency, it needs to be implemented in Go, be minimal and simple, and mature. Alternatively we should implement one from scratch if a suitable implementation cannot be found.
The log file could use pkgs/autofile, or a fork that doesn't automatically delete older chunk files, and we could leave it up to the user to run a background service that deletes older chunk files as needed.
I'm open to alternative solutions, but this seems to be the most conceptually simple solution. Compared to Tendermint1, instead of an asynchronous pubsub, Tendermint2 has the original synchronous simple event switch. Tendermint1 bakes in several pubsub listeners, but Tendermint2 would be more minimal and simply log all events to the filesystem.

Original issue: https://github.com/gnolang/gno/issues/275

@moul
Can you please explain this part more? I'm not sure why we'd need a pubsub system in the first place

We could possibly use an existing persistent pubsub system to implement this, but if we're going to use such an external dependency, it needs to be implemented in Go, be minimal and simple, and mature. Alternatively we should implement one from scratch if a suitable implementation cannot be found.

Make sure that we can have a standalone collector feeding a pubsub system. And another standalone processor that consumes the pubsub.
PubSub could be a simple file, a database, not necessarily an advanced API.


Make sure to apply pathogen filters to genome exports.

Summary:

What: Fix the data that we export for tree builds.

Notes:
When we build trees, we export all of a group's samples to a fasta file for the nexstrain pipeline to ingest. This export script was missing filters for specific pathogens, so it was writing all of a county's sequences for all pathogens to this file. These sequences were likely ignored by the SC2 pipeline, but broke the MPX pipeline which is stricter about input requirements.
I updated the tests to add sequences for multiple pathogens as part of the setup method, ensured that nearly all of the test cases failed, and then added the patch to export.py and all tests succeeded. I also manually kicked off a rebuild of a previously failed mpox tree in prod with this patch and it succeeded.
Checklist:

[x] I merged latest <base branch>
[x] I manually verified the change
[x] I added labels to my PR
[ ] I tested in multiple browsers
[x] I added relevant unit tests
[ ] I have notified others of changes they need to make locally (migrations, jobs, package updates, etc)

Thanks Jessss! How come all mpox trees diff ppl built for testing worked fine before Mikala's build? 🤔

did they have any SC2 samples in their accounts?


Add Acknowledgements to images used and change default cursor icon

LGTM, good job on polishing the outlook of the app. 👍


Customize background color of recorded files

Issue
Currently, the background of rendered Terminalizer recordings are white. This imposes design restrictions on how we can display the recordings/gifs to the end user.
Question
Is there an option to set the background color behind the rendered terminal?
Example
Demonstration of the issue achieved by setting the background color on the Terminalizer GitHub repository page to a non-#FFF color.

☝

The work-around is to specify a negative margin or use the boxShadow to set the background.  That's been sufficient for my needs.
frameBox:
  type: floating
  title: PowerShell
  style:
    border: 2px solid cornflowerblue
    boxShadow: 0px 0px 0px 20px blue
    margin: 10px

Another workaround - find terminalizer dir, open render/dist/css/app.css file and change background-color in body section.


Support LodeWallet

Already spoke to their team. When I tested using their "Nami" wallet injection, the TXes would go thru, but on our client side would say failed.
They recommended to add support for "cardano.LodeWallet"  and test again. If this does not work, I will go back to them to see what is going on.

Last time I tested, there was a white screen after TX submission, however, wallet dev mentioned the issue is on their side + the TX actually works. Closing as completed.


Speaker-blind speech recognition

Depends on #143
Adding a streaming ASR pipeline needed a big refactoring (that began with #143).
This PR continues this effort to allow a new type of pipeline that transcribes speech instead of segmenting it.
A default ASR model based on Whisper is provided, but the dependency is not mandatory.
Additional modifications were also needed to make Whisper compatible with batched inference.
Note that we do not condition Whisper on previous transcriptions here. I expected this to degrade transcription quality but I found it rather robust in my experiments with the microphone and spontaneous speech in various languages (English, Spanish and French).
The new Transcription pipeline can also use a segmentation model as a local VAD to skip non-voiced chunks. In my experiments, this worked better and faster than using Whisper's no_speech_prob.
Transcription is also compatible with diart.stream, diart.benchmark, diart.tune and diart.serve (hence diart.client too).
Still missing

README examples and possible restructuring

Changelog
TBD

Is this feature considered implemented?

@BlokusPokus it seemed to work last time I tried but I didn't merge because I wanted to include a faster implementation of Whisper and I needed to clean up the code. Feel free to try it out but it's a pretty old version of the library. I need to find some time to update this PR. If you feel like it, it would be an amazing contribution!

Yeah we definitely need a faster-whisper / WhisperLive implementation. WhisperLive also integrated VAD and I see it has some overlapping features.

Yeah we definitely need a faster-whisper / WhisperLive implementation. WhisperLive also integrated VAD and I see it has some overlapping features.

Have you started to work on the faster-whisper implementation?
Is whisperX helpful to you? It uses faster-whisper.

@GeorgeDeac @ywangwxd This feature is pretty much finished. But I think it would be nice to replace the default ASR by a faster one, like the ones you mention. Feel free to work on top of this PR, as I'm not too available to work on this as I'd like.
I'd gladly merge a PR to replace the default ASR and add a couple of examples in the README. I can take care of resolving the conflicts with the main branch after the feature is good

I'd suggest creating some basic tutorial content before merging into main - I tried this branch out and it was a struggle to integrate both Transcription and VAD into a single pipeline - something that's necessary when using Whisper in order to avoid hallucinated words in transcripts. (I get "Thank You" a lot when brief silences are transcribed by whisper)
I also ran into sampling issues when calling a transcription pipeline via diart.client. - these weren't present when doing simple diarization, and I'm not sure whether they're related to my own inexperience with this toolchain or suggestive of an issue with the code. In any case, a robust exemplar for a chained pipeline would be a good addition to the README.  I created a couple:
simple: https://gist.github.com/arbuckle/d41cb5e25ccc588f4a98b8430eca40b5
complex: https://gist.github.com/arbuckle/5163d435ba174ee3ae866e789fa03f23
The complex example works, but it feels wrong and the performance is not yet to my satisfaction. (VAD needs to be tuned)


Map content moves when zooming

My simple test-app (created with V1 beta2) has some strange zooming behaviour: when zooming out, the drawn polygon moves south-east and returns to its correct postion when the zoom operation ends. When zooming in, the drawn polygon moves north-west and returns to its correct postion when the zoom operation ends.
this is my app:
var map = L.map('map').setView([51.505, -0.09], 13);
L.tileLayer('http://{s}.tile.openstreetmap.org/{z}/{x}/{y}.png', {
  maxZoom: 18,
  attribution: "© OpenStreetMap contributors"
}).addTo(map);
var polygon = L.polygon([
  [51.509, -0.08],
  [51.503, -0.06],
  [51.51, -0.047]
]).addTo(map);

I published the app to testmapw.meteor.com, have a look...
If I replace V1.0.0 beta2 with V0.7.3 everything is ok again.

Cannot reproduce in beta2.
http://playground-leaflet.rhcloud.com/waj/edit?html,output

Did you try testmapw.meteor.com ?

Yeah, but if I cannot reproduce the bug in a controlled minimal environment, I have to assume it's not a problem in the Leaflet core.
Also, I cannot know what's going on in your webpage, as all the JS is minified and I cannot trace code execution.

Thank you for looking into this! I understand your position.
I would like to debug this myself then; I just need some advice on how/where to start.
I made a minimal Meteor app (https://www.meteor.com/) using a meteor package that wraps the leaflet V1Beta2 library: https://atmospherejs.com/bevanhunt/leaflet and deployed this to maptestw.meteor.com.
This shows the error as you have seen.
If I just replace the leaflet library package with an older version (V0.7.3) the error goes away.
I notified the package author of this problem too (https://github.com/bevanhunt/meteor-leaflet/issues/61) and he suspects it could have to do with "the tile set not having fully loaded"
Could you point me in a direction to verify this or give me some other advice to start debugging this?

Not sure if this info is of any value diagnosing the problem, but If I set { zoomAnimation: false } for the map, the erratic content movement is gone (but alas, also the animation :{ )...

Sorry, I know this is closed, but I ran into this problem as well. My problem was due to using the old css file (0.7.3) instead of the current one (1.0.3). Hope this helps someone.

You helped me @tc33133, thanks!

Dear @tc33133 , what css file did you update?

I was using the hosted version, and I didn't update the stylesheet link.
IE I was using

running version 1.0.3, so I should have been using

If you follow the directions to use the hosted version here http://leafletjs.com/download.html you should be fine.


LIST VIEW [ALL ENTITIES]: all columns must be sortable

List = all columns must be sortable, so far only first name and via dropdown also last name is sortable

For the Beta Version: the first and last name should be made sortable at least and not only via the dropdown


Firestore: using listDocuments() requires EmulatorCredentials when running with dev services

Operations like Firestore.listDocuments() require specific Admin credentials. In the production environment this is ensured by the default GCP credentials, however, when connecting to an emulator (i.e. via Dev Services) specific credentials need to be provided, for which the EmulatorCredentials class can be used.
The current integration logic does not provide this functionality, therefore these operations cannot be used in an emulator environment.

Example implementation based on the reference docs. Running this example results in an error when dev services are enabled.
`
package org.acme;
import java.util.ArrayList;
import java.util.List;
import java.util.concurrent.ExecutionException;
import java.util.stream.Collectors;
import java.util.stream.StreamSupport;
import jakarta.inject.Inject;
import jakarta.ws.rs.GET;
import jakarta.ws.rs.Path;
import jakarta.ws.rs.Produces;
import jakarta.ws.rs.core.MediaType;
import com.google.api.core.ApiFuture;
import com.google.api.core.ApiFutures;
import com.google.cloud.firestore.CollectionReference;
import com.google.cloud.firestore.Firestore;
import com.google.cloud.firestore.Query;
import com.google.cloud.firestore.QuerySnapshot;
import com.google.cloud.firestore.WriteResult;
@Path("/firestore")
public class FirestoreResource {
@Inject
Firestore firestore; // Inject Firestore
@GET
@Produces(MediaType.TEXT_PLAIN)
public String firestore() throws ExecutionException, InterruptedException {
    // Insert 3 persons
    CollectionReference persons = firestore.collection("persons");
    List<ApiFuture<WriteResult>> futures = new ArrayList<>();
    futures.add(persons.document("1").set(new Person(1L, "John", "Doe")));
    futures.add(persons.document("2").set(new Person(2L, "Jane", "Doe")));
    futures.add(persons.document("3").set(new Person(3L, "Charles", "Baudelaire")));
    ApiFutures.allAsList(futures).get();

    return StreamSupport.stream(persons.listDocuments().spliterator(), false)
            .map(r -> {
                try {
                   return  r.get().get();
                } catch (InterruptedException | ExecutionException e) {
                    throw new RuntimeException(e);
                }
            }).map(document -> document.getId() + " - " + document.getString("firstname") + " "
                    + document.getString("lastname") + "\n")
            .collect(Collectors.joining());

//
// Search for lastname=Doe
//        Query query = persons.whereEqualTo("lastname", "Doe");
//        ApiFuture querySnapshot = query.get();
//        return querySnapshot.get().getDocuments().stream()
//                .map(document -> document.getId() + " - " + document.getString("firstname") + " "
//                        + document.getString("lastname") + "\n")
//                .collect(Collectors.joining());
}
}
`

Branch with implemented testcase: https://github.com/jfbenckhuijsen/quarkus-google-cloud-services/tree/firestore-admin-queries

Anyone able to respond to this?

Hi,
I think we can switch to Credentials everywhere, this has the advantage of making it easy to mock the credentials and stick to the lower level type in the hierarchy that is used almost everywhere.
As you said, this is not the case for FirebaseAdmin, people that uses FirebaseAdmin must provide an object of type GoogleCredentials.
This PR did exactly that: https://github.com/quarkiverse/quarkus-google-cloud-services/pull/579
As you said, we should be able, when using emulator, to automatically create such overridden bean, if you're willing to do this (ideally for all supported service that provides emulator configuration) a PR would be highly welcome.

On it!

#602 created

As far as I could tell, only Firestore has specific EmulatorCredentials to use. Spanner has a setEmulatorHost, but that has already been implemented. So AFAIK this should complete this issue

@loicmathieu tested a local SNAPSHOT version of the code vs my own setup, seems to work nicely, so looks like we can close this issue?

Yes, thanks for reporting!
Fixed by #602


Display text in sans-serif font

VS Code's overlays use sans-serif fonts for regular text within overlays. It would be neat if we could do the same here.
(e.g. https://code.visualstudio.com/images/intellisense_paramater_info.png)
Given that this is potentially down to user preference, this could be a preference rather than a default.
(This is already possible through mdpopups' user CSS preference, but IMO would make a good default.)

Would be nice to see some screenshots on multiple platforms of what a "default" sans-serif font stack would look like!

On macOS:

(Don't have my Windows machine handy currently, but I can get a screenshot for that later.)
You can try this locally with the following in Packages/Users/mdpopups.css:
.mdpopups .lsp_hover {
	font-family: sans-serif;
	line-height: 1.4em;
}

.lsp_hover div.highlight,
.lsp_hover pre.highlight {
	margin-bottom: 0;
}

Nice, we don't even have to argue over which sans-serif font - the default on OS-X looks good.
If if works looks good on Windows, let's ship it!

Here is how it looks on Windows showing a hover for JSON.stringify:

There are some other bugs with the shown signature but the CSS itself looks good. Want to do a PR?

Oh, I totally neglected to take the screenshot 🤦♂
I'll PR it up 😃

mdpopups and normal popups use the font specified by the "font_face" setting in the Preferences by default. I think this is the best default behavior. Fonts, colors etc. are all of personal taste and I would only add as much CSS entries as required to arrange anything correctly - most of that is already done by mdpopups. Custom/fixed font-faces are not part of it.
mdpopups did so in the past, too, but finally removed anything with 2.0 release as you'll never satisfy the majority with that.
Imagine the situation of 100 packages providing popups, each of them with different font settings and styles. Who the f.. should customize all of them back to personal needs? It makes life of theme authors even harder. Only few already take CSS styles into account, right now.
It is the job of a theme to provide font-faces and maybe even custom colors. Anything else is users choice.
With mdpopups we have a common mdpopups.css which can be used to modify all or single package's popups settings in one place.
What LSP and all the other packages must do is to provide a documentation of all css classes being used.
Example:
GitGutter as an example uses a gitgutter_popup.css which contains all required classes and rules instead of hard-coding them into the python code. It provides the safe defaults and the documentation of each required element. What it does is adapting the colors of several elements to the selected color scheme to look well out of the box in 99%.  Try to keep it short and helpful, please.

The descriptive text isn't code and can be displayed in a more readable sans serif font just as the rest of the UI. Which sans-serif font is of course up to the theme author. I expect the sans-serif keyword to render the same font as the UI, but if that's true depends on the minihtml implementation (there is no built-in variable to lean on otherwise).
What @deathaxe is ranting about is just what you get when you let plugins create UI without a restrictive framework that decides exactly what that UI looks like. mdpopups is just a tool and not already a requirement just to keep UI variation down.
The situation has been much worse over at Atom. Having a full fledged browser to work with and a very limited style guide sparked the creation of loads of new UI by plugins. In the early days it was definitely hard to deal with as a UI theme developer. But you know what? It all shakes down in the end. Shared utilities (like mdpopups) become more mature as we better understand what UI-api's people need, and plugins migrate to these utilities because they deliver value. Let's not lock down what you can and cannot do in a plugin in this first (post-beta) iteration of the feature.
Of course plugins should create as little UI as possible, and not invent fancy new UI, so that they fit in with all possible UI themes and are easily customisable. What is and isn't reasonable is up in the air. Switching from code/monospace font to a UI/sans-serif font is in my opinion a minor and reasonable style decision.


*.: Add a way to ensure all created metrics are properly registered in Prometheus Registry.

We have lot's of issue recently when we add metric, instrument and it's not actually registered :man_facepalming:  e.g https://github.com/thanos-io/thanos/issues/2100
That's enough. I am looking on a mandatory way to test if ALL metrics are actually registered when you start Thanos binary.
Some ideas:
A) Mandatory unit test for all Metrics structs with Registerer that checks what was registered.

More automated?
B) Grep for all metrics creations and check e2e tests if /metrics shows them (kind of primitive)
C) New** methods for Prometheus client that registers metrics in custom registery
D) Wrap prometheus client library with something that allows checking if New* method that creates metrics has the corresponding metrics in Registered. (weird)

Any hints on how to do it, @brian-brazil @beorn7 @brancz ? I think C makes sense the most + add item to CONTRIBUTING.md

@beorn7 is there an idea to improve prom client for such metric constructor? Which allows passing Registerer? Why would you not register that's the question :/ I guess this is for ability to register in multiple registeres...

https://www.robustperception.io/when-should-you-unit-test-instrumentation and https://www.robustperception.io/how-to-unit-test-prometheus-instrumentation have my general thoughts.
Promauto with a global registry does have its advantages.

Yes, but we need something for the custom registry. The global registry is anti-pattern as we tried to explain during out talk with @kakkoyun  http://are-you-testing-your-observability.now.sh/

Maybe we should just expand promauto package (: That would be nice

The global registry is anti-pattern as we tried to explain during out talk

This will always be a point of contention. I wouldn't take for granted that all will share your opinion, even after watching your talk.

Maybe we should just expand promauto package

The "elegance" of the global registry is that you can just say promauto.NewCounter with the normal arguments. With a custom registry, you need to pass it in as an additional parameter. That doubles the (already high) number of constructor functions. And then you need to add another set with Must... because the auto-register functions would return an error and you probably want the panicking versions, too.
Or you go down the approach that OpenTelemetry took and add factory methods like NewCounter to the registry. Those method would return collectors already registered with the registry whose method you have called. I considered this approach multiple times but always ran into some reason not to use it. Things I remember right now:

It would be a quite large shift from the current pattern.
It would be "yet another way of doing the same thing".
Since registration can fail, the return value of those methods needed to include an error. And/or you create MustNewCounter style methods, which would panic instead.
One of the reasons why people use custom registries is that they want to register the same collector with different libraries, or they want to have the option of not registering at all or register later. (Those needs are certainly rare, but very easy and common cases can be handled with a global registry. I'm concerned if we provide three different ways (for easy cases, intermediate cases, and rare special cases) instead of just two.)
The registry would not have a simple interface with only Register and Gather as methods, but there would be a very fat interface (NewCounter, MustNewCounter, NewGauge, MustNewGauge, NewCounterVec, etc. etc.).

I'm sure there are more reasons.
Coming back to your original problem:

It's easy to write glue code on your own for the suggested factory functions that create a metric and register it immediately. If it works out well, we can consider them as additions to promauto or in a separate package.
Have you looked at https://godoc.org/github.com/prometheus/client_golang/prometheus/testutil#GatherAndCompare ?
You could write a little helper that registers all Collectors in a struct via reflection. (I have considered that quite often, and it might be a good idea as a tool in client_golang. Again, I would be interested to see it in use first.)

Awesome, thanks for this :heart:

This will always be a point of contention. I wouldn't take for granted that all will share your opinion, even after watching your talk.

Totally, but at least I can share my opinion, right? (: And I don't expect anyone to change their mind after our talk. It was touching many things (: And we need to work on persuasion skills first... (:

.With a custom registry, you need to pass it in as an additional parameter. That doubles the (already high) number of constructor functions.

Hm, I think I like it despite the arguments...
OK, so it looks we have plenty of options here:
A) Mandatory unit test for all Metrics structs with Registerer that checks what was registered.
B) our wrapper for: New** methods for Prometheus client that registers metrics in the custom registry
C) our wrapper for: register with New** methods (so your factory idea)
D)  You could write a little helper that registers all Collectors in a struct via reflection. (I have considered that quite often, and it might be a good idea as a tool in client_golang. Again, I would be interested to see it in use first.)
Hm.. could give example for D @beorn7 ?
I love the idea of us exploring one of this and propose this to https://github.com/prometheus/client_golang

Hm.. could give example for D @beorn7 ?

https://github.com/prometheus/client_golang/pull/712

:heart: Thanks! I commented, on your PR.. TL;DR I think still some promauto.NewCounter(reg, opts...) is the most tempting for me. (:

https://github.com/prometheus/client_golang/pull/713 is my idea of going down the promauto path.

I am super  happy with: https://github.com/prometheus/client_golang/pull/713
This would my choice.
Any other opinion @SuperQ @GiedriusS @kakkoyun @yeya24 ?

I also really like the factory idea in prometheus/client_golang#713.
I don't know how intensively reflection used in client_golang, but I'd love to avoid that., for this one.
So thanks @beorn7 ❤ Please feel free to reach out, if you need a hand on this.

AC:

Update prometheus client go dependency
Move all metric creation to newly created promauto.With

Done :tada:
https://github.com/thanos-io/thanos/pull/2228
Thanks @beorn7 :heart:


Add aarch64 support for Buffer Overflow module and add install instructions

Added installation and usage instructions
Added aarch64 support to buffer overflow plugin

Thanks Alot :-)


E2E test coverage for BRC feature

Context
AB#222988 AB#235845
Change proposed in this pull request
E2E tests against the d02 environment.
Guidance to review
Run the tests targeting the above environment.
Checklist (add/remove as appropriate)

[x] Work items have been linked (use AB#)
[x] Your code builds clean without any errors or warnings
[x] You have run all unit/integration tests and they pass
[x] Your branch has been rebased onto main
[x] You have tested by running locally
[ ] You have reviewed with UX/Design

@Faizan-ahmad00 would you be able to review this PR?


implement compression

Use the new DataPipe object to write data with compression. This requires you to write the data pipe without data, load the file back in, and append to it with the append method. See the test here

See this open issue for the plan for an improved workflow

https://github.com/NeurodataWithoutBorders/matnwb/issues/184.


Send some missing fields to PayPal

Hi, thanks for the contribution. Can you please confirm that this works in a production environment and then I will tag. Note that the tests were failing due to an unlrelated issue, I have fixed that in a separate PR.

Yes, we use this fix a few days in production at sliceproducts.com web-store and everything is OK

Released as v2.2.2


Loads of console.logs when using custom importers

Seems to be this line:
        console.log(data); // ugly hack

what is it a hack for?

It is to keep the libuv loop alive: https://github.com/sass/node-sass/pull/615.
Also see the discussion: https://github.com/sass/node-sass/pull/644#discussion_r23903134. This will be removed, once we have custom function implemented.


Tower of Hanoi in C++

Have you read the Contributing Guidelines on Pull Requests?
(Write your answer here.)
YES
Description
(Write your answer here.)
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
(Write your answer here.)
Tower Of Hanoi in C++

@bhav09 @HarshCasper Please review my PR and merge it


Table body classname

Actually, only 1 commit is related to this PR
https://github.com/Andreyco/fixed-data-table/commit/de7d03f247098e40fa24c4bc8095ef5f17a6565b

Thanks for your pull request. I apologize for leaving this project in limbo and not addressing your concerns. I have archived this project after doing a final release to make it compatible with React v16.


Changed alignment of options in descriptions.

Hi!
I found the alignment of option's description a bit messed up honestly.
I tried to fix that, i tested with long meta argument or with descriptions that included newlines and seems OK to me.
The only thing i can not understand is why i had to change the directive "~&" to "~%" to make things works.
I am open to critics and review for this patch (i mean, more than usual!).
Bye!
C.

Hi @cage2,
Thanks for the pull request! I'll look at it in the next few days!

On Sun, Apr 19, 2020 at 09:50:16AM -0700, Thomas Schaper wrote:

Hi @cage2,

Hi!

Thanks for the pull request! I'll look at it in the next few days!

Thank you very much for your work and your quick reply! :)
Bye!
C.

On Sat, May 23, 2020 at 03:08:29AM -0700, Thomas Schaper wrote:

@libre-man commented on this pull request.

Hi!

Thanks for the changes, I've merged  it in e14c9b5 after doing some
minor changes and adding some tests!

Thanks to you for your review  and clearing my doubts about the format
directive! :)
Bye!
C.


Fix ohai deprecation link in the release notes

The wrong link was put into the release notes

Yolo link fixing


refactor(search2): optimise number of attachment retrievals

Checklist

[x] the contributor license agreement is signed
[x] commit message follows commit guidelines
[x] tests are included
[ ] screenshots are included showing significant UI changes
[ ] documentation is changed or added

Description of change

Profiling revealed a lot of time was spent in search2 requests in ifNotBroken due to both uses calling off to retrieve the same
attachment. Significant performance (both speed and DB calls) improvements were possible if instead we re-use the attachment we retrieve when we first check for broken attachment status rather than throwing it away.
Existing tests provide coverage for this, and I also undertook manual testing.
(While doing this, I noticed that for broken attachments the New UI was showing _no_description - just the exclamation mark. This was due to the change to show the Kaltura description. As a result, I rejigged that a little too - and so now broken attachments are more likely to show a description.)

Thanks @PenghaiZhang , I'll merge on green. :wink:

Flaked on known flaky. Merging.


chore: deprecate := variants of inductive and structure

Deprecates inductive ... :=, structure ... :=, and class ... := in favor of the ... where variant. Currently this syntax produces a warning, controlled by the linter.deprecated option.
Breaking change: modifies Lean.Linter.logLintIf to use Lean.Linter.getLinterValue to determine if a linter value is set. This means that the linter.all option now is taken into account when the linter option is not set.
Part of #5236

@adomani @grunweg I noticed that logLintIf didn't take into account linter.all, and I modified the logic here. It seems to me that it was meant to respond to linter.all, but please let me know if it's not supposed to.

Kyle, thanks for the heads up!  I think that I never used logLintIf (at least not directly), but I'll keep an eye out for linters misbehaving!  :smile:


Fixed specifying private key to esp_supp_dpp_bootstrap_gen

Fixes #8478

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


./node_modules/ng4-geoautocomplete/auto-complete.service.js

Please solv this issue

I'm getting the same issue as well


Use machines.yaml to create machine crd object during cluster creation.

This doesn't create master vm as per machines.yaml. This will be fixed later.

This change is


DynamicValue.schema made public

Resolves #332

Lint is failing.

I know will finish it later (went back to the stack safety topic for now)

Please just re-open when you have a chance to get the build passing!


[Sema] Fix crash on bad inheritance clause

When checking for the superclass type, ensure we don't use a protocol composition's superclass type if it doesn't have one.
Resolves SR-8160.

@swift-ci please smoke test

Thanks!


Thread safe requests

@andypf, this is a good idea and make perfect sense.
Looks good, besides a couple of things regarding a slightly change in the http scheme and the verify_mode code and also two minor unnecessary changes (cosmetic/style?), please see inline comments.

Hello gildub,
ok, I will do the changes and update this pull request asap.
Thanks for the review!
Andreas

@andypf,
Thanks for the prompt update.
I understand the single quotes are better unless interpolation is needed. I suppose I got busted for trying to use them in another project or maybe it was a wrongly configured Rubocop. Anyway, I propose to do another patch to go across and change all unnecessary double quotes so we are consistent.


DNSPerf 2.11.1 Homebrew MacOS Ventura

dnsperf-2.11.1 on macos ventura using homebrew
doh-uri extended option not working:
dnsperf -m doh -s blahblah.com -O doh-uri=https://blahblah.com/dns-query
DNS Performance Testing Tool
Version 2.11.1
invalid long option: doh-uri=https://blahblah.com/dns-query
Cannot seem to get it to take a uri, have tried many iterations of the syntax
robertpaolucci@CNMUS0022 dnsperf-2.11.1 % dnsperf -H
DNS Performance Testing Tool
Version 2.11.1
Usage: dnsperf ... -O [=] ...
Available long options:
latency-histogram: collect and print detailed latency histograms
verbose-interval-stats: print detailed statistics for each stats_interval
num-queries-per-conn=: Number of queries to send per connection
suppress=<message[,message,...]>: suppress messages/warnings, see man-page for list of message types
doh-method=<doh_method>: the HTTP method to use for DNS-over-HTTPS: GET or POST (default: GET)
doh-uri=<doh_uri>: the URI to use for DNS-over-HTTPS (default: https://localhost/dns-query)

It's option=value
Try:
-O doh-uri=https://blahblah.com/dns-query

Sorry, didn't see the edit in my email. Thanks for the report, will fix as soon as I can.

@RobertPaolucci-CUJO can you compile develop branch and test?


feat: documentation for what is Injected in JS runtime

Maybe, i don't know where to search for it.
I found it in code base eventually, but still some explanation would be helpful :)
I'm not sure, if I should use it, if it's in legacy dir:
https://github.com/warp-contracts/warp/blob/main/src/legacy/smartweave-global.ts

it's in legacy dir as it is inherited from original SmartWeave implementation, you can read some more about it here https://github.com/ArweaveTeam/SmartWeave/blob/master/CONTRACT-GUIDE.md#smartweave-global-api
I'll try to add info about it to the SDK docs and to the Warp Academy next week.

Great! Thanks SmartWeave.block.timestamp is in seconds or milliseconds?


software bug

coodinator should not block the pod deletion
CNI spec suggest DEL command to succeed in common case

fix https://github.com/spidernet-io/spiderpool/pull/1985/files#diff-1b02d7d6507c2ac3fa4d2bd908521ce5cd0ffd610806f7826404eb88e4cd6013