fvr

Click to expand!
Issue Type
Bug
Have you reproduced the bug with TF nightly?
Yes
Source
source
Tensorflow Version
dewxc
Custom Code
Yes
OS Platform and Distribution
sdac
Mobile device
sx
Python version
c
Bazel version
xsxd
GCC/Compiler version
scdx
CUDA/cuDNN version
dc
GPU model and memory
wsc
Current Behaviour?
A bug happened!

Standalone code to reproduce the issue
sdacv

Relevant log output
recfdssdc

https://www.reddit.com/r/AntManandtheWasp_tv/
https://www.reddit.com/r/CreedIIImobiletV/
https://www.pastery.net/usmyhs/
https://paste.vpsfree.cz/zs:AtDpl/
https://paste.artemix.org/-/87UpCw
https://paste.rs/4GZ
https://bpa.st/NAPMU
https://ideone.com/BHMKEI
https://paste.rs/4GZ
https://paste.feed-the-beast.com/view/ff17c144
https://paste2.org/2EyK1Yha
https://dotnetfiddle.net/Q4tQ48
https://rentry.co/cad9t
https://paste2.org/sUyxkWKX

https://www.reddit.com/r/AntManandtheWasp_tv/
https://www.reddit.com/r/CreedIIImobiletV/
https://www.pastery.net/usmyhs/
https://paste.vpsfree.cz/zs:AtDpl/
https://paste.artemix.org/-/87UpCw
https://paste.rs/4GZ
https://bpa.st/NAPMU
https://ideone.com/BHMKEI
https://paste.rs/4GZ
https://paste.feed-the-beast.com/view/ff17c144
https://paste2.org/2EyK1Yha
https://dotnetfiddle.net/Q4tQ48
https://rentry.co/cad9t
https://paste2.org/sUyxkWKX

Please don't spam


feat(linting): no floating promises

:tada: This PR is included in version 1.44.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


console showing error

Describe the bug
Chrome is not live updating every time code is written in vs.code. writing code on a file using ".js" is not appearing or executing whereas files using ".html" are updating only after closing and reloading
To Reproduce
Steps to reproduce the behaviour:

Go to 'Vs.code'
Create 'new file using .js'
write "console.log('hello world')"
right click and select open with live server
right click again and click on inspect
find console and error showing Live reload enabled

Expected behavior
The console should simply show "Hello world"
Desktop (please complete the following information):

OS: Mac M1 pro
Browser [chrome,]
Version 120.0.6099.199

Additional context
I have just started learning coding and have no clue what I am doing or even know how to use GitHub at all so i hope this reaches someone who can help. sorry for uploading this request somewhere wrong.

How are you linking your .js file to your html?

You can't write js to html! JSX file `jsx
function App() {
return (
<>
</>
)
}
`


[DOC-META] Dashboard Documentation

What do you want to do?
Make a change to existing documentation
Add new documentation
Report a technical problem with the documentation
Other
Give a brief description of your request.
We need to build the documentation for OpenSearch Dashboards.
Which versions are affected?
We'll start with version 2.0. We should keep an eye on any differences between 2.0 and 1.3. If there are no differences, we can backport to 1.3.
Which pages or URLs are affected?
Here is where the dashboard content exists today:
https://opensearch.org/docs/latest/dashboards/index/
What resources are available (for example, links to a related issue, PR, design doc, or feature brief)?
The UX team should be able to provide the best insight into how dashboards are used by customers.
Andrew Hopp - PM
Other:
Here's a suggested TOC for the Dashboards section of the doc:

[x] #941
[x] #991
[x] #992
[x] #993
[x] #994
[x] #995
[x] #996
[x] #997

We don't want to go into details about each plugin here. We can refer to the plugins and give a summary of the functionality, but we want to describe specific dashboard functionality with the plugin itself.

Assign to Melissa once she gets access to Github.

Content sections being written and published in order of priority and as completed. Priority 1 content status = writing

Closing meta issue. Topic-specific issues will be opened as needed.


Use correct store when loading indexes for graft base

Previously, we were trying to load indexes from the store corresponding to the subgraph being deployed. This was the wrong shard, resulting in deployment failures when a subgraph is on a different shard from its graft based.
This updates the call to use the correct store.

Any timeline for when this will be merged and released?

@yash251

Any timeline for when this will be merged and released?

Confirming this has been released to production, and deploying grafts now works correctly.


Imported WIP into breadcrumbs

Describe your changes
Imported WIP componenet into BreadcrumbsTemplate.tsx, which resolves issue #97
Screenshots - If Any (Optional)
Issue ticket number and link - If Any
Issue #97
Checklist before requesting a review

[x] I have performed a self-review of my code.
[x] Followed the repository's Contributing Guidelines.
[x] I ran the app and tested it locally to verify that it works as expected.

Additional Information (Optional)
Any additional information that you want to give us.

Thanks so much for your contribution!


Problem with PostgreSQL when retrieving products

Issue Summary
A bug when using PostgreSQL as DB backend.
An invalid query is being used to get products in the catalogue (both in dashboard and regular).
This stems from the get_queryset method in ProductListView:
queryset = Product.browsable.base_queryset()
For now, I replaced it with Product.objects.all() to get it to work.
\lib\site-packages\oscar\templates\oscar\base.html, error at line 0

column "catalogue_product.structure" must appear in the GROUP BY clause or be used in an aggregate function LINE 1: SELECT "catalogue_product"."id", "catalogue_product"."struct... ^

Full query:
SELECT "catalogue_product"."id", "catalogue_product"."structure",   "catalogue_product"."upc", "catalogue_product"."parent_id",   "catalogue_product"."title", "catalogue_product"."slug",   "catalogue_product"."description", "catalogue_product"."product_class_id",   "catalogue_product"."rating", "catalogue_product"."date_created",   "catalogue_product"."date_updated", "catalogue_product"."is_discountable",   COUNT("catalogue_productclass_options"."option_id") AS   "num_product_class_options",   COUNT("catalogue_product_product_options"."option_id") AS   "num_product_options", "catalogue_productclass"."id",   "catalogue_productclass"."name", "catalogue_productclass"."slug",   "catalogue_productclass"."requires_shipping",   "catalogue_productclass"."track_stock" FROM "catalogue_product" LEFT OUTER   JOIN "catalogue_productclass" ON ("catalogue_product"."product_class_id" =   "catalogue_productclass"."id") LEFT OUTER JOIN   "catalogue_productclass_options" ON ("catalogue_productclass"."id" =   "catalogue_productclass_options"."productclass_id") LEFT OUTER JOIN   "catalogue_product_product_options" ON ("catalogue_product"."id" =   "catalogue_product_product_options"."product_id") WHERE   "catalogue_product"."parent_id" IS NULL GROUP BY "catalogue_product"."id",   "catalogue_productclass"."id" ORDER BY "catalogue_product"."date_updated"   DESC  LIMIT 1
Steps to Reproduce

Run the server
Add a product (after adding arbitrary category, product type and partner)
Visit the homepage and get products (Menu: Browse Store > All products) or through the dashboard (Menu: Catalogue > Products)

This bug does not occur when retrieving other information, such as the product types, categories, ranges etc.
Technical details

Python version: 3.6.4
Django version: 2.0.7
Oscar version: 1.6.4.
PostgreSQL version: 9.0.23.

I can't reproduce this on the sandbox. I think your issue is that you are using an unsupported version of PostgreSQL. Django 1.11.x requires PostgreSQL 9.3 or higher.

You're right - after upgrading to 9.6 it works.
Thanks!


GLES3 draw commands don't unbind the array buffer

Godot version:
3.2.b3
OS/device including version:
All
Issue description:
Missing unbind statements for the ARRAY_BUFFER at the end of _draw_xxx() commands in GLES3, except for _draw_gui_promitive() which has it. Nothing catastrophic since the buffer is unbound automatically on the next bind, but this could potentially slow down rendering a notch as the buffer is not given back to the GL driver on time. In GLES2 everything is good wrt unbinding.
The patch:
gles3_array_buffer_unbind.patch.txt
Steps to reproduce:
Minimal reproduction project:

I have no strong feelings on this, feel free to make a PR.


Clickable Schema (Types)

The idea is to be able to Cmd + Click on the types in a .prisma file, to go to some information of what they actually mean (e.g. postgres.schema).
We should investigate how this could work.

Okay, this does feel a bit forward-looking since what we currently have is mostly self-explanatory:
String => text
Boolean => boolean
Int => int
Float => double
DateTime => timestamp

I'll put this on my plate, but at a lower priority than website + testing.

Internal Note: Dropping because undefined where it would link to.

The target could be based on something like that: https://github.com/prisma/specs/pull/291/files#diff-d4cc93f9d37eb5db26995253d6a42c5eR1031 (Be aware that this is justa PR)

Now with native types, seems this would be the better and more appropriate solution: https://github.com/prisma/language-tools/issues/704


SyntaxError: Unexpected token '?'  if ((architecture ?? this.provider.architecture) === 'arm64') {

While using the plugin under serverless2.0 with Nodejs 12.x I'm getting the bellow error,
I think it's since "nullish coalescing operator"(??) isn't supported on lower versions of nodejs (only 14.5 and above - with ECMAScript11+)
Syntax Error -------------------------------------------
SyntaxError: Unexpected token '?'
/opt/atlassian/pipelines/agent/build/node_modules/serverless-plugin-lambda-insights/index.js:98
if ((architecture ?? this.provider.architecture) === 'arm64') {
^
SyntaxError: Unexpected token '?'

Thank you for reporting the issue, working on a fix today.


Blank float terminal in Windows

Describe the bug
:LspSaga term_toggle displays a blank float window
Blank window:

I can open terminal using :split | terminal:

Steps to reproduce
nvim --clean -u init.vim
:Lspsaga term_toggle
init.vim:
call plug#begin()
  Plug 'glepnir/lspsaga.nvim'
call plug#end()

lua <<EOF
  require('lspsaga').setup({})
EOF

Expected behavior
The float terminal should display initial text like current working directory, etc. and I should be able to type in commands.
Neovim version (nvim -v)
NVIM v0.8.1
lspsaga commit
ac134041da57f7592a46775f235ed84880bc0b27
Terminal name/version
cmd.exe 10.0.19041.746

windows shell command is what ? looks like windows does not have $SHELL

does termopen('cmd.exe') can  work ?

Yes, termopen('cmd.exe') works. You made me realize that using $SHELL envar or :Lsp term_toggle cmd.exe will work.
Thanks.


Chrome: Can't save songs to an existing playlist

Can only save a song by selecting its save icon and creating a new playlist from that menu. Can't even then save another song to that new playlist. Worked fine before v0.173.

Got it. I can reproduce over here. I'll have it fixed today, sorry.


Bad results in ArkPlanner for Global servers

Environment
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.97 Safari/537.36
URL
https://penguin-stats.io/planner
Steps to reproduce
Run ArkPlanner for anything involving higher level materials in US servers.
What is expected?
Only stages that are actually released in Global will be included in calculated results, or you will have the option to filter out stages not yet released from the Exclude Stages option.
What is actually happening?
The Exclude Stages option only displays stages released in Global, but stages from chapters 6 and 7 will still be included in the ArkPlanner results with no way to exclude them.

Just ran into this problem. Had to switch the server back to CN in order to uncheck all the chapter 6 and 7 stages, otherwise they were included in the results even though they don't show up in the excluded stages section when on US server.
Looking through the rest of the open issues though, I think that this is the same problem as #315 (using google translate)

Thanks for reporting this issue. After we've done refactoring Planner this shall be fixed ;) :heart:


Deprecation! Flutter 3.3.2 Outlined Button property

In flutter's 3.3.2 version OutlinedButton's primary color was deprecated.
What kind of property can I use instead of that?

Hi @asadbekdev
You can use the style property for this.
If you still have issues, please see https://flutter.dev/community for resources and asking questions like this,
you may also get some help if you post it on Stack Overflow and if you need help with your code, please see https://www.reddit.com/r/flutterhelp/
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you


Update documentation on dynamic_update_slice_in_dim

I was extremely surprised to find that start_indices is implicitly set to 0 for dimensions other than axis, rather than requiring that all other dimensions be equal or broadcastable to each other:
>>> z = jnp.zeros((3, 5))
>>> u = jnp.ones((2, 2))
>>> jax.lax.dynamic_update_slice_in_dim(z, u, 1, axis=0)
Array([[0., 0., 0., 0., 0.],
       [1., 1., 0., 0., 0.],
       [1., 1., 0., 0., 0.]], dtype=float32)

I think it's non-obvious that this is how the dynamic_update_*_in_dim methods would work, so noting it in the documentation would be nice.
This led to me really struggling to track down a bug yesterday, which turned out to be in the following code:
updated = jax.lax.dynamic_update_slice_in_dim(operand, update, start_index, axis=2)

Unfortunately, I called this code both with arrays of shape (batch, head, time, hidden) and (batch2, batch, head, time, hidden). When I was looking for the bug, I thought this couldn't be the problem since I was assuming it would error if it received "incompatible" shapes. Later when I did find it, I assumed it was just broadcasting since the time dimension was size 1. (Thanks for the tip on Twitter @mattjj!)
If this is an unintended use of dynamic_update_slice_in_dim, it might be nice to do a dimension check, but maybe people are relying on this behavior.

Hi - thanks for the report, and sorry for the unclear semantics here. Can you say more about what your expected result would be? Were you expecting an error because u.shape[1] != z.shape[1]?

Yeah I think I was expecting the semantics to be something like numpy slice updates, so for axis=2:
slice = slice(start_index, start_index + update.shape[2])
operand[:, :, slice] = update

I think another way this might trip someone up is if they were expecting broadcasting of size-1 dimensions, but instead got the 0-th index updated in those dimensions instead.

Makes sense, thanks. I believe this was the intended use-case for this function, I might add some shape validation and see if it breaks any code.

Re-opening and re-naming to track the possibility of adding input validation to these functions.


boolean field option is true if option is present but boolean method parameter option is false if option is present

Minimal example:
@CommandLine.Command(name = "test")
public class TestCommand implements Command {
    @Option(names = "-r")
    public boolean option1;

    @CommandLine.Command(name = "subcommand")
    void start(@Option(names = "-s") boolean option2) {
        System.out.println("-r is "+option1 +" and -s is "+option2);
    }
}

Command: test -r subcommand -s
Output: -r is true and -s is false

It seems also that no matter what value I specify for -s option (after adding arity="1"), the value is always false.
@CommandLine.Command(name = "test")
public class TestCommand implements Command {
    @Option(names = "-r")
    public boolean option1;

    @CommandLine.Command(name = "subcommand")
    void start(@Option(names = "-s", arity = "1") boolean option2) {
        System.out.println("-r is "+option1 +" and -s is "+option2);
    }
}

Command: test -r subcommand -s true
Output: -r is true and -s is false

I tested both variants you mentioned but I am unable to reproduce the issue.
Can you try with -Dpicocli.trace=DEBUG and paste the output here?

I don't have anymore the previous minimal example but I've created a minimal project where you can reproduce the issue with a test:
PicocliTest.zip
Just unzip and run with ./gradlew clean assemble :test --tests "test.MyTest" --info
And look at:
MyTest > testIssue1772() FAILED
    org.opentest4j.AssertionFailedError:
    expected: "------> -r is true and -s is true <------"
     but was: "------> -r is true and -s is false <------"

@Onedy Thank you for the test project to reproduce the issue.
I created a derived test that tests the same without using Spring:
package test;

import org.junit.jupiter.api.Test;
import picocli.CommandLine;
import picocli.CommandLine.*;

import static org.junit.jupiter.api.Assertions.*;
import static picocli.CommandLine.ScopeType.INHERIT;

/**
 * https://github.com/remkop/picocli/issues/1772
 */
public class Issue1772 {
    public CommandLine getTestCommandLine(ParentTestCommand parentCommand, TestCommand testCommand, IFactory factory) {
        CommandLine commandLine = new CommandLine(parentCommand, factory);
        commandLine.addSubcommand(testCommand);
        return commandLine;
    }
    @Command(name = "parentTestCommand", mixinStandardHelpOptions = true, scope = INHERIT)
    static class ParentTestCommand {
    }

    @Command(name = "test")
    static class TestCommand {
        @Option(names = "-r")
        public boolean option1;

        public static String testString;

        @Command(name = "subcommand")
        void start(@Option(names = "-s") boolean option2) {
            testString = "------> -r is " + option1 + " and -s is " + option2 + " <------";
        }
    }

    @Test
    public void testIssue1772() {
        CommandLine commandLine = getTestCommandLine(new ParentTestCommand(), new TestCommand(), CommandLine.defaultFactory());
        commandLine.execute("test", "-r", "subcommand", "-s");
        assertEquals("------> -r is true and -s is true <------", TestCommand.testString);
    }
}

The above test fails with picocli 4.6.3, as demonstrated when I add it to the test project you provided:
Issue1772 > testIssue1772() FAILED
    org.opentest4j.AssertionFailedError: expected: <------> -r is true and -s is true <------> but was: <------> -r is true and -s is false <------>
        at org.junit.jupiter.api.AssertionUtils.fail(AssertionUtils.java:55)
        at org.junit.jupiter.api.AssertionUtils.failNotEqual(AssertionUtils.java:62)
        at org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:182)
        at org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:177)
        at org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:1141)
        at test.Issue1772.testIssue1772(Issue1772.java:40)

But when I run the same test with the current version of picocli in the main branch (which has the fix for #1741), then the same test passes.
So, I believe this ticket can also be closed: since it won't be a problem after the fix for #1741 is released in the next version of picocli.


Add support for Irwin-Hall distribution

Go through the Gaussian distribution class, the Binomial class and the Exponential class which are subclasses of General distribution class.
I would like to expand this to include another distribution, the Irwin-Hall distribution.
This one might be slightly more challenging than the other distributions ;)

@whynesspower That sounds like a great plan! Just a headsup, I'm moving towards using seaborn instead of matplotlib(see this #63 ), I will merge it soon so the changes will reflect in the codebase as well.
Apart from that, everything sounds great. Assigning this to you :)


Return Types changed

When the clear text value is NULL, the returned type is NULL, too. Edit made in order to make the section more detailed.

@gotqn : Thanks for your contribution! The author, @edmacauley, has been notified to review your proposed change.

Thanks for that clarity edit, @gotqn #sign-off


Controller is called twice with custom url parameter type

I have such a code:
http://pastebin.com/8sC7nAEp
If im using this parameter in:
url: "/{name:spaceReplace}",

Then my controller is called twice, if i change spaceReplace for string for example then its called only one time. Whats going on?
Also its called actually only when there are spaces in parameter, if not its called only one time.
Also its called like that only if i access url by ui-sref. If i access it manually then there is no problem.

I had a similar problem with a custom type being used for prettifying dates in the URL; the route change would be called twice, and thus the controller would also be instantiated, destroyed and the instantiated again. I resolved it be providing an "equals" method for my custom type.
For example:
var spaceReplace = {
    // original "encode", "decode", "is" methods
    equals: function(a,b) { return a === b; }
};

I had a similar problem with a custom type being used for prettifying dates in the URL; the route change would be called twice, and thus the controller would also be instantiated, destroyed and the instantiated again. I resolved it be providing an "equals" method for my custom type.
For example:
var spaceReplace = {
    // original "encode", "decode", "is" methods
    equals: function(a,b) { return a === b; }
};

Well i will check it in work. I hope it works. I have one time bindings so from user side there is no diffrence, but it still had to do request for get something etc.

If you change equals to always return true, does the double loading go away (not suggesting this as a fix; just diagnostic)?

Yea it works with return true ! Also its working how it should be, whats the diffrence ?

Working how it should is a happy coincidence. :)
From the docks, the equals method:

Determines whether two decoded values are equivalent.

From your code sample, I'd suggest that your equals method returned if, when both passed through the decode method, the outputs matched.

Sounds like this was cleared up?


Changing from React-dom-factories to React-createElement

Are there transforms to change from https://www.npmjs.com/package/react-dom-factories to React CreateElement. Given that this React CodeMod already provides a handy transform for React CreateElement to JSX ?

Not that I know of, but I'm happy to entertain a PR. It's not very useful nowadays tho. CLosing this, but lemme know if you make a PR.


[RPI2B] Camera could not be opened

When I launch sudo node server.js on my Raspberry Pi 2 B, I got an error:
socket.js:14
var camera = new cv.VideoCapture(0);
             ^
Error: Camera could not be opened
    at Error (native)
    at Object.<anonymous> (/home/x/face-detection-node-opencv/server/lib/routes/socket.js:14:14)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.<anonymous> (/home/x/face-detection-node-opencv/server/server.js:26:21)
    at Module._compile (module.js:460:26)

I tried with both open-cv 2.4.1 compiled on the RPI and installed from apt-get.
Any idea?

Unfortunately, OpenCV 2.4.1 has not worked for others... see https://github.com/peterbraden/node-opencv/issues/176. Can you try installing 2.4.9 or higher (but not 3.x)?

Hey drejkim,
unfortunately I do have the same Issue with my Raspberry 3 on OpenCV 2.4.13 and Node.js 0.12.15. I compiled OpenCV on the Raspberry (no errors). Also the npm install did work out fine ..
Any Ideas?

Solved it actually. Another Process (Service) of mine was keeping the camera busy.


Update pre-commit hooks.

To get rid of the Vale error, change "Cable Modeling description" to "Cable modeling description".

To get rid of the Vale error, change "Cable Modeling description" to "Cable modeling description".
[vale] doc/source/API/CableModeling.rst#L1 [Google.Headings] 'Cable Modeling' should use sentence-style capitalization.

Agreed @PipKat . I will get rid of this warning within this PR.


Re-enable netsync on meatspike - fixes #4070

About the PR
Fixes #4070 by re-enabling netsync.
Screenshots

Changelog
:cl:

fix: Dead bodies show up on meatspikes again.

Doesn't fix it as it should be a visualizer.

nope, calling this sufficiently silly.
In regards to Visualizers
Allow me to address the anxieties underlying your concerns, rather than try to
answer every possible question you might have left unvoiced. First, let us
consider the fact that Visualizers are additional code. This simple fact has
far-reaching implications. It requires radical re-thinking of the use of
visualizers not as a definitive, but as a trade-off between maintainability and
network usage. It also requires planning and forethought as to the frequency
and cost of state changes that run in direct opposition to the 'One Way Of
Doing Everything' mindset.
I find it helpful at times like these to remind myself that our true enemy is
code. Code is what makes our programs run and generally is required for all of
these machinations to function in any way at all. But inseparable from code is
its dark twin, dependency. Code is inextricibly bound to itself, and today we
clearly see this in all of the bugs that have cropped up due to reliance on
code that has since changed in form or semantics. In adding additional code,
visualizers cause reliance on not only the visualizer framework itself, but
every single mechanism that must be added to make a visualizer function, while
netsync merely increases dependency on an existing, often-tested engine feature,
unlikely to change, rooted in RobustToolbox's own state synchronization framework.
We should thank netsync for giving us respite from this overpowering force.
It has thrown a switch and exorcised our demons in a single stroke.

From my understanding, the Visualizers are a necessary evil to get Photography in.
That said. Working on Content-level stuff, 8 out of 10 bugs have been visualizer-related. And 10 out 10, it was due to the syncing server and client state.

eh, as far as I can tell most bugs so far seem to not be visualizer-related as much as they are related in general to being based upon code which then suddenly gets refactored or changed.
For example, a server error occurs when gibbing something that you are pulling now because the pullable component gets removed before the puller actually detaches from it.
If I tried to fix it I'd probably get told to refactor the entirety of the pulling system.
Changing the semantics back would likely break other things.


Allow manual refresh/download for a specific pool's metadata

This is a feature request for the UI part of capability (against cardano-wallet here ).
It would be nice to add a refresh metadata against a pool ID to be able to fetch up-to-date information independently of SMASH server status, given that 99% of users cant be bothered with adding a custom SMASH server instance in settings, unless Daedalus team is open to add community-run SMASH instances to pre-populated list that comes as part of installation.

If you need to refresh stake pools metadata, go to the Stake pools settings in Daedalus, and select "None". Then (optionally) select "IOHK" again.

@rvl
First - this assumes the pool ID is correctly showing up in smash already, which is not always the case.
Secondly - switching to None and then back would mean end user starts rebuilding pool DB for every pool from smash (even those that were correct), resulting in wait.
Again, these are not issues that I face, but it gives a very frustrating UX , especially when user knows the pool ID, can see the valid metadata in community hosted pool explorers (and at times even SMASH instances). For such cases, it would be much easier to be able to delegate either using the ID itself or have an option to fetch the metadata given the pool ID

@rdlrt we are working on extending the list of stake pools that are shown in Daedalus so that you can view stake pools without metadata as well as the private ones (profit margin === 100). This will enable you to delegate to stake pools that do not have any metadata too. The feature you are requesting is the "next step" in case this is doable on the cardano-wallet side since we depend on it's Api.
@rvl would that be feasible?


add relation between container projects and persistent volume claims

persistent_volume_claims are under a namespace\project. This PR adds the relation.
depends on https://github.com/ManageIQ/manageiq-schema/pull/60

@zakiva Please review
cc @simon3z @moolitayer @cben
@miq-bot add_label providers/containers

Please add test for this relation in refresher_spec.
You might have to also adjust graph refresh.

Looks good. nit comment

@moolitayer Fixed

@Fryguy @blomquisg https://github.com/ManageIQ/manageiq-schema/pull/60 was merged. Can we merge this one too?


7.2 Release

Rebase into 7.x

This looks like a merge failure:
Document/Multiple/BulkAll/BulkAllObservable.cs(27,32): error CS0102: The type 'BulkAllObservable<T>' already contains a definition for '_bulkResponseCallback' [/home/vsts/work/1/s/src/Nest/Nest.csproj]

PR closed in favour of cherry-pick into 7.x


Items Counter

Project implementations: 👇🏼 closes #3

Create a counter function that shows the number of items on the home page.
The count function is covered with unit tests using Jest.

Good job Benson, The item counters works correctly. nothing more to add.


No mouse on second monitor after rescaling

Hi, thanks for making this!
I wonder if someone can offer advice about using this tool to set up multiple monitors with different scaling, and still be able to move the mouse across both screens. Currently I do the following:

Start my compositor (dwl) which is configured to use normal (x1) scaling for all monitors by default.
Use an alias that calls this script with a predefined --pos argument to position the second screen (left/right)
Call this script again with the --scale argument to scale the second screen if necessary.

I often attach different screens because this is for a NUC box which I sometimes carry around. Everything is working fine except if I rescale the second screen, and then I can't move the mouse to it anymore. Is this a known issue? Are there any workarounds? Most of my workflow is keyboard driven, but occasionally the mouse is convenient (e.g. for web browsing).
Cheers

Please report this to your compositor. This doesn't seem like a wlr-randr bug. wlr-randr doesn't have control over the mouse.
Maybe it's because there's a gap in your output layout, so the mouse gets stuck at the edge of a screen.


[BUG] VAICOMPRO window opens, but cannot be found anywhere in the screen space

Describe the bug
VAICOMPRO window opens, but cannot be found anywhere in the screen space
To Reproduce
Steps to reproduce the behavior:
Start Voice Attack, plugins enabled
press ctrl alt c to bring up VPC window
Expected behavior
A clear and concise description of what you expected to happen.
VPC window appears, interact with the window, continue playing DCS
Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.
Can't find the window...

close voice attack then delete your config file in C:\Program Files (x86)\VoiceAttack\Apps\VAICOMPRO\Config (or wherever you installed voice attack)
then re-open

Oh My Gosh, that totally worked!
Thank You Thank you Thank you!

From: Wreyth @.>
Sent: Wednesday, December 18, 2024 21:27
To: Penecruz/VAICOMPRO-Community @.>
Cc: CDRKrotchetyUSN87 @.>; Author @.>
Subject: Re: [Penecruz/VAICOMPRO-Community] [BUG] VAICOMPRO window opens, but cannot be found anywhere in the screen space (Issue #143)
close voice attack then delete your config file in C:\Program Files (x86)\VoiceAttack\Apps\VAICOMPRO\Config (or wherever you installed voice attack)
then re-open
—
Reply to this email directly, view it on GitHubhttps://github.com/Penecruz/VAICOMPRO-Community/issues/143#issuecomment-2552697654, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BNWRHWDV6KYFLU6YB2BJQ332GI4ITAVCNFSM6AAAAABTTTTCNOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJSGY4TONRVGQ.
You are receiving this because you authored the thread.Message ID: @.***>


in help, still cheatcoin reference

$ xdag
xdag client/server, version 0.2.1.
Usage: xdag flags [pool_ip:port]
If pool_ip:port argument is given, then the node operates as a miner.
Flags:
-a address     - specify your address to use in the miner
-c ip:port     - address of another cheatcoin full node to connect
-d             - run as daemon (default is interactive mode)
-h             - print this help
-i             - run as interactive terminal for daemon running in this folder
-l             - output non zero balances of all accounts
-m N           - use N CPU mining threads (default is 0)
-p ip:port     - public address of this node
-P ip:port:CFG - run the pool, bind to ip:port, CFG is miners:fee:reward:direct:maxip:fund
miners - maximum allowed number of miners,
fee - pool fee in percent,
reward - reward to miner who got a block in percent,
direct - reward to miners participated in earned block in percent,
maxip - maximum allowed number of miners connected from single ip,
fund - community fund fee in percent
-r             - load local blocks and wait for 'run' command to continue
-s ip:port     - address of this node to bind to
-t             - connect to test net (default is main net)
-v N           - set loglevel to N

easy fix


Screen not rendering on Intel graphics

Already reported ? *

[X] I have searched the existing open and closed issues.

Regression?
Yes
System Info and Version
Hyprland 0.45.0 built from branch  at commit  dirty ().
Date:
Tag: , commits:
built against aquamarine 0.5.0
flags set:
debug
System Information:
System name: Linux
Node name: FreakyArchBTW
Release: 6.11.9-arch1-1
Version: #1 SMP PREEMPT_DYNAMIC Sun, 17 Nov 2024 16:06:17 +0000
GPU information:
00:02.0 VGA compatible controller [0300]: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller])
os-release: NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rolling
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://archlinux.org/"
DOCUMENTATION_URL="https://wiki.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://gitlab.archlinux.org/groups/archlinux/-/issues"
PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/"
LOGO=archlinux-logo
plugins:
unknown: not runtime
Description
This has started happening after I updated hyprland to 0.45.1. Whenever I start hyprland (either via tty or sddm), the screen turns off and stays off. When I switch ttys and go back to the hyprland tty, it shows one frame and it freezes. I am running an Intel I5-6300u with a 520 integrated gpu.
How to reproduce
Start Hyprland (either via sddm or tty) on the cpu specified on v0.45.1 and above
Crash reports, logs, images, videos
No response

can you bisect this? https://wiki.hyprland.org/Crashes-and-Bugs/#bisecting-an-issue

ok, between 0.45.0 and 0.45.1 (where this started happening), it output:
[c4a77b8da7783d95345935cd2468d83cd54d182b] core: guard pmonitor in focuswindow

I don't think you did it correctly if that's the output. Check the git head (latest git) and if it's bad, select that as bad and put 0.45 as good

between 0.45.0 and head
[83be2480c45bdead9110fdf137a1cd2f5a203378] workspace: fix missing name via focusworkspaceoncurrentmonitor (#8484)

are you sure this couldn't be a aquamarine regression?
https://gitlab.archlinux.org/archlinux/packaging/packages/hyprland/-/commit/a6f593168059910617ec760ff3e49f9fbafdc787 was released a day before 0.45 on arch

it is aquamarine. i installed that version of hyprland and it still isn't rendering. pacman doesn't wanna downgrade aquamarine because it apparently breaks this "libaquamarine" dependency that hyprland uses.

what version of mesa are you using @themonglord? i noticed the same, also on intel, when upgrading mesa to version 24.3.0 (and reported it to upstream mesa), and the fix for me was downgrading mesa to 24.2.7 (by, in my case, disabling the arch testing repos and running pacman -Syuu)

unless mesa can point to a culprit being hyprland doing something wrong, I disagree.


WIP: Add angular-cli.json option to explicitly specify entryModule when …

…it can’t be inferred from code
In some cases @ngtools/webpack is unable to resolve the application entry module automatically.
This commit exposes entryModule option of AotPlugin in angular-cli.json so that you can specify it by hand.

Please @hansl @filipesilva can you point me in right direction with appveyor failure? can't reproduce it on my machine :(

And also please suggest a proper place and way to test this

@hansl is the appropriate person to review this PR.
Meanwhile though, can you provide a test case that would break without this enhancement?
Regarding appveyor, I think it was having some trouble a bit ago. It shouldn't be relevant to your PR atm.

@filipesilva I have the following test case, just can't figure out how and where to properly incorporate it into the test suite:
if (someCondition) {
  platformBrowserDynamic().bootstrapModule(AppModule, { providers }).catch((reason) => {
    console.error(reason);
  });
} else {
  platformBrowserDynamic().bootstrapModule(AppModule).catch((reason) => {
    console.error(reason);
  });
}

I know this is somewhat contrived example, it is just to show the static resolver is not 100% bulletproof.

https://github.com/angular/angular-cli/issues/2887#issuecomment-268699091 -- the workaround suggested in this comment also breaks resolution

This is a use case we need to fix, rather than work around. I'll take a look at it.


F#: Improved char literals

This adds the missing \xFF and \uFFFF character escapes to character literals.
I also removed the incorrect "string" from the F# example page.

Finally found a page which lists all escape sequences. I think this is ready.


Having trouble unboxing this box

When I try to unbox this I receive this error log:
1 error generated.
make: *** [Release/obj.target/sha3/src/addon.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:258:23)
gyp ERR! stack at ChildProcess.emit (events.js:182:13)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:237:12)
gyp ERR! System Darwin 16.7.0
gyp ERR! command "/usr/local/Cellar/node/10.4.1/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/BreckStodghill/workspace/truffleAngular/node_modules/sha3
gyp ERR! node -v v10.4.1
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

I see you're using node v10.4.1. Does the same issue exist for node 8.9.x?

I've tested with node 10. If this issue still persists, feel free to reopen this with some more details (preferably what's above in the stacktrace you copied).


The assembly reference 'ClaySharp' could not be loaded for module 'Orchard.DesignerTools'.

Fresh install of Orchard v.<IP_ADDRESS>.
Installed Designer Tools and activated Shape Tracing.
Error is encountered:
The assembly reference 'ClaySharp' could not be loaded for module 'Orchard.DesignerTools'.
There are generally a few ways to solve this issue:

Install any dependent module.
Remove the assembly reference from the project file if it's not needed.
Ensure the assembly reference is present in the 'bin' directory of the module.
Ensure the assembly reference is present in the 'bin' directory of the application.
Specify the strong name of the assembly (name, version, culture, publickey) if the assembly is present in the GAC.

This is a good one, we have removed this assembly and any reference to it 4 years ago. If you find any reference to it, even a string that would prove that we didn't completely get rid of it.

I did a quick search on Github and nothing appears when I search for ClaySharp. Can you check for old files on your side? Maybe you are using an old DesignerTools version. Or are you actually taking it from the gallery? (which you should not in this case)

I did a search and wasn't able to find any reference to ClaySharp


docs: add string()

Implements https://github.com/fabian-hiller/valibot/issues/209#issuecomment-1755624961

Thank you very much! I'll take a closer look at the PR in the next few days and give you feedback.

You are great! Thanks a lot. I will try to review the changes in the next few days.
One idea I had was to list the authors of the documentation at the bottom of each page, like in Qwik. What do you think about that? Here is an example: https://qwik.builder.io/docs/

@kazizi55 please pull my latest changes, start the website in your development environment and let me know what you think about them.

Thanks to all the contributors who have helped make this documentation better!

Sounds great!
This would motivate contributors to improve docs more 😄
Can I add this section in another PR?

Sounds great! This would motivate contributors to improve docs more 😄
Can I add this section in another PR?

Yes, this would be a big help. Don't focus to much on the design (unless you have experience with it and enjoy doing it). I can improve the CSS afterwards before merging the PR.

Currently, generics in types cannot be fully mapped with <Property />. I noticed this with StringSchema for example. We'll have to look at this again.
// This is how it looks
BaseSchema<string>

// And this is how it should look
BaseSchema<TOutput = string>

Yes, this would be a big help. Don't focus to much on the design (unless you have experience with it and enjoy doing it). I can improve the CSS afterwards before merging the PR.

Thank you for your kindness 😄
OK! I'm gonna work on it!

Currently, generics in types cannot be fully mapped with . I noticed this with StringSchema for example. We'll have to look at this again.

That's true.
I'm gonna fix it in the next few days 😄

@fabian-hiller

Currently, generics in types cannot be fully mapped with . I noticed this with StringSchema for example. We'll have to look at this again.

Fixed!
https://github.com/fabian-hiller/valibot/pull/220/commits/2c4c0b9b8303b5ca1b77142391e05b36ec52e353
Now, generics with default parameter can be displayed!
https://deploy-preview-220--valibot.netlify.app/api/StringSchema/

Thanks a lot. I plan to review the new changes in the next days.

@kazizi55 can you review my changes? I think that we are slowly approaching our destination. 🏁

@fabian-hiller
LGTM! Thank you for your changes 😄
What do you think about the next actions to complete the API document?
Which pages should I write next?
I think it's better to create a new issue which includes to-do list, so that we can check which document is completed or not. 😄

Are you happy with the current version? Would you change anything? I will take another look at everything in the next few days and also check how other API references present there information to give feedback. But we are on the right track and I think we will reach a final version soon.

I have further improved the string API reference and updated the references of all types. I'll take another look at it tomorrow. I think we can merge the changes shortly and then add the other API references one by one. 🚀

@kazizi55 thank you again for your contribution! I will merge this PR and post the draft on Twitter to get more feedback before we add the other references.

https://valibot.dev/api/string/

Unfortunately, no. We probably only get feedback when people use the API reference and don't understand or miss something. I will create a issue soon where we can coordinate the API reference extension. 🧩


go_fish rewrite

Moving MIOpen out of go_fish and into its own lib file.
Expected go_fish cmd behavior:

go_fish.py -h should print go_fish help (not MIOpen help)
go_fish.py miopen --> should print MIOpen help
go_fish.py miopen -h  --> should print MIOpen help
go_fish.py  miopen --update_solvers --> typical update_solvers run

Anyother MIOpen cmd ran the same as before. MIOpen lib is default, no need to specify, but if you do specify the results will be the same.
Go fish was split into:

go_fish.py (strictly start up script to launch library, get processes from lib and apply join())
miopen/miopen_lib.py (MIOpen tuning lib, all miopen code)
mituna_interface.py (Tuning lib interface - non MIOpen code)

All miopen scripts touch in this PR have been moved to miopen/ dir
Absolutely no functionality change applied, other than moving functions around.

Moving forward I would be interested in seeing if we could accomplish this module linking without altering tuna. Meaning for a new module: a developer would flush out their tables & workers, pull the Tuna framework, and then no additional changes are required to Tuna. If we were still launching from go_fish, we would need to have a mechanism for linking to input parsing and a worker factory function. I wonder how to introduce this without updating go_fish.py or libraries.py with each new addition.

Let me work on this, i have an idea


OSX Wwise won't generate soundbank because plugin does not have license.

Hello, I've just tried using a plugin from the Wwise export in OSX. It loads into the Wwise editor, and plays sounds from the plugin properly from inside the editor, but whenever I try to generate a soundbank I get an error saying "No license for 'wind' plug-in. Please contact<EMAIL_ADDRESS>to obtain a license." (the plugin is called wind). I'm on OSX 10.11.3, Wwise version 2<IP_ADDRESS>63 (although I had this issue with  2<IP_ADDRESS>23 as well).

hi @unriginal could you send me a link to your plugin and I'll take a look

Yes, the plugin link is here:
https://enzienaudio.com/h/unoriginal/wind/
I also changed the name in case wind was reserved by some other plugin, but yeah, same result.

@unriginal is it possible for you to use Wwise version 2<IP_ADDRESS>75 until we figure this out? I'm able to generate soundbanks with the plugin correctly in that version.

hi @unriginal it looks like backwards compatibility with plug-ins in the latest version of Wwise has been broken, I've been told that the next release will fix it all and to wait for that. Alternatively 2<IP_ADDRESS>75 is confirmed to be working.


There's only one GPU，How should I change it？about bash scripts/run_main_ens_fea_dist.sh

CUDA_ID="0"
batch_size=10
NPROC=1

and keep all other settings unchanged.

thank you
---Original---
From: @.>
Date: Sun, Mar 20, 2022 11:50 AM
To: @.>;
Cc<EMAIL_ADDRESS>Subject: Re: [Equationliu/GA-Attack] There's only one GPU，How should I change it？about bash scripts/run_main_ens_fea_dist.sh (Issue #1)
CUDA_ID="0" batch_size=10 NPROC=1
and keep all other settings unchanged.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.Message ID: @.***>


provider api: better errors on invalid cert

The error returned by send-manifest when the user has an invalid (revoked in this case) cert is:
Error: Put "https://provider.sjc1p0.mainnet.akashian.io:8443/deployment/477826/manifest": EOF

It should be more informative.

looks like errors returned by VerifyPeerCertificate are not returned properly during TLS handshake

We should have a RPC node for each region. It comes in pairs. @hydrogen18 hitting forboles RPC node.
@troian - Please document what you said on the sprint planning call here so we have the full context of the workflow and potential issues, and workarounds.

TLS handshake errors may come from 2 places

client: if handshake fails here that returns well formatted error with explanation of what caused to terminate
server: if VerifyPeerCertificate errors client only receives alert during TLS handshake and always returns remote error: tls: bad handshake regardless to what was actually cause of termination.

reason for recent failures was triggered during query of certificate from chain on server side during TLS handshake and as pointed in RPC node running in private mode alongside with each provider may fix they issue.
closing for now. reopen/create if solution above does not help


Game options

Some games can have various set of rules. It should be possible to choose what rules to use.

This is now available as of https://github.com/Zomis/Games/commit/5261136207bc5179f251117f00d1c0b23b81546e and have been added to and tested in Hanabi.


Document component settings

Component settings are currently not documented.
I'm assuming that they are not since they are simply properties of the class but it'd still be nice to have.

Closing this off given that 0.6 is moving to a framework-agnostic suite of API tools, and will no longer include the server. See https://discuss.apistar.org/t/api-star-as-a-framework-independant-tool/614 and #624.


Fix github actions

I think we could publish our models to Huggingface Hub instead of S3 and add them as submodules, I'll experiment with it and update this branch.


Claimed block devices become unclaimed after deleting them and the corresponding ndm pods.

Description

Block devices used for creating pool becomes claimed. These devices become unclaimed again if they are deleted and restart the respective openebs-ndm pods.

Expected Behavior

Used block device should be unclaimed only when the pool is deleted.

Current Behavior

BD became unclaimed.

Steps to Reproduce

Create CSPC pool.

NAME                   AGE
cstor-cspc-disk-pool   12m

cstor-cspc-disk-pool-gzxl   giri-node1   102K        49.7G   49.8G      ONLINE   12m
cstor-cspc-disk-pool-jkf8   giri-node3   101K        49.7G   49.8G      ONLINE   12m
cstor-cspc-disk-pool-xvc5   giri-node2   164K        49.7G   49.8G      ONLINE   12m

Check if block devices are claimed.

NAME                                           NODENAME     SIZE          CLAIMSTATE   STATUS   AGE
blockdevice-0ee17cf390682c34a3d42e8149c5c776   giri-node2<PHONE_NUMBER>0   Claimed      Active   4m58s
blockdevice-111cc41d48cd83408e1b45347a2c9d83   giri-node1<PHONE_NUMBER>0   Claimed      Active   4m56s
blockdevice-13113626d35a434a33f02ef4f943a7bd   giri-node3<PHONE_NUMBER>0   Claimed      Active   4m58s

Delete block devices and restart openebs-ndm pods.
Check if the block devices are unclaimed.

blockdevice-0ee17cf390682c34a3d42e8149c5c776   giri-node2<PHONE_NUMBER>0   Unclaimed    Active   9m56s
blockdevice-111cc41d48cd83408e1b45347a2c9d83   giri-node1<PHONE_NUMBER>0   Unclaimed    Active   9m54s
blockdevice-13113626d35a434a33f02ef4f943a7bd   giri-node3<PHONE_NUMBER>0   Unclaimed    Active   9m45s

Screenshots

Your Environment

kubectl get nodes:
kubectl get pods --all-namespaces:
kubectl get services:
kubectl get sc:
kubectl get pv:
kubectl get pvc:
OS (from /etc/os-release):
Kernel (from uname -a):
Install tools:
Others:

Fixed in #416.
A finalizer is added to the BlockDevice resource while claiming to prevent accidental deletion of the resource.


Turn mux tracing String tag into a polymorphic variable

This way we will avoid Show instances on peerid floating around.

Fixed by #1162


Add "Mark as unread" option to three-dot topic menu

At present, the three-dot topic menu includes a "Mark all messages as read" option even when the topic has no unreads, which can be confusing. Instead, we should do the following:

[ ] When the topic has at least one unread messages, show a "Mark all messages as read" option (same as now).
[ ] Otherwise, when there are no unreads, show a "Mark all messages as unread" option instead.

CZO discussion

@zulipbot claim

@zulipbot claim. Unfortunately I couldnt reproduce https://github.com/zulip/zulip/issues/25336 so I am going to start this one.

@zulipbot claim.

Hello @alya , Can I work on this issue while I wait for my PR review and possible merge?. Thank you

Please focus on getting the other PR ready for integration prior to picking up a new issue. You can ask again once it receives the "integration review" label.

Alright. Thanks

@zulipbot claim


Improved path challenge handling.

We are willing to reply to up to 5 outstanding challenges on a connection, as it is legal for a client to send more than one.  We limit to 5 to prevent excessive challenging.

We now accept path challege responses on any network path, in accordance with RFC 9000 section 8.2.3.

This patch addresses the issue raised by [#189], though with a different implementation.  It also addresses another issue, which is that we may need to reply to more than one remote challenge on the same path.  Both sides are bounded, currently to 5 items, to avoid any possible resource attack.  There are tests and coverage remains at 100%.

I will lint this one further and push an update tonight or tomorrow morning


PostgreSQL-specific ltrim and rtrim

As @marekklis pointed out in https://github.com/zio/zio-sql/pull/339,  it appears that PostgreSQL can take an additional, optional parameter in ltrim and rtrim functions.
Just adding these functions in PostgresModule might cause import clashes. We need to figure out the way to deal with such situation.

Probably we should move these function from the core module to modules specific for every database servers.

This is still an open issue. Research is needed to find out if ltrim and rtrim behave differently on different databases. If yes, then move them to specific modules and implement accordingly.

It would be best if there is a way to override in the DB-specific module the default implementation from core. That way, even if ltrim is behaving the same for MySQL, MSSQL, Oracle and Postgre, but differently for XXX - it will be easy to add XXX db support without rewriting the core. (Just stating the obvious)

Probably we should move these functions from the core module to modules specific for every database servers.

The unary variants of ltrim and rtrim behave the same for all supported DMBS. There is however a difference in the two-argument variant:

MySQL: Returns the string str with leading space characters removed. Returns NULL if str is NULL.
Oracle: LTRIM removes from the left end of char all of the characters contained in set. If you do not specify set, then it defaults to a single blank.
PostgreSQL: Removes the longest string containing only characters in characters (a space by default) from the start of string.
SQL Server: Returns a character expression with a type of string argument where the space character char(32) or other specified characters are removed from the beginning of a character_expression.

So I'd leave Ltrim and Rtrim in the core module, but add Ltrim2 and Rtrim2 in all submodules that support it.
Note that while SQL Server since 2022 (compatibility level 160) supports ltrim and rtrim with two args, the Azure SQL Edge image used in tests doesn't because it has compatibility level 150. I presume this one is used because the SQL Server image doesn't run on M1 without workarounds. Therefore I omitted it for now. If the two-arg variant is needed for SQL Server then I guess one needs to implement some tests based on the mcr.microsoft.com/mssql/server:2022-latest image and disable them on M1 machines.
Side note to the naming: There is some inconsistency in the casing of Ltrim and LPad. I personally prefer LTrim because it's written how you pronounce it ("l-trim"). But for consistency I named the new functions Ltrim2 and Rtrim2. Would it be okay if I rename it (a breaking change)? Should I add an alias and deprecate the other one? Or should we leave it as it is? WDYT?


Allow Users to Add FAQs

I'd like to propose a feature that enables users to submit their own FAQs to the application. This would enhance user engagement and allow for a more comprehensive FAQ section.
I would like to solve the issue. Please assign to me.

I have also resolved issue #428, which allows users to submit their own FAQs.

please reply me

Please reply me.


Convenience methods for modifying GoogleNoiseProperties

This PR adds GoogleNoiseProperties.override, which allows users to create a new GoogleNoiseProperties with manually-specified values. These values can be specified in three different ways:

Providing a single value for a field will set all existing keys to that value. For example, gate_times_ns=1 will overwrite all previously-specified gate durations with 1ns.
Providing an appropriately-typed dict for a field will update the existing dict with the given values. For example, t1_ns={GridQubit(0, 0): 1} will set the (0, 0) qubit's T1 time to 1ns, overwriting any existing value.
For fields with OpIdentifier keys, providing a Gate-based mapping will update all matching OpIdentifiers with the given value. For example, gate_pauli_errors={cirq.ZPowGate, 0.01} will set all mappings with a cirq.ZPowGate-based key (regardless of qubits) to 0.01.

Calls to override can be chained to simplify value assignments. For example:
new_props = noise_props.override(t1_ns=100).override(t1_ns={cirq.MeasurementGate: 25})

creates new_props based on noise_props, with measurement T1 set to 25ns and all others set to 100ns.
This is part 5 of #4666; part 4 was #5187. Remaining steps include:

Reinstatement of compare_generated_noise_to_metrics using new types

CC @vcatherine: does this fulfill the ease-of-use criteria you're looking for?

Converted to draft due to lingering type issues. Review can wait until these are resolved.

Typechecker appeased, this is once again ready for review.

User experience LGTM, thanks Orion!

Oops, applied changes to the wrong branch (3b4a instead of 3b4b). Fixing.

Changes should be here now.


Question: prevent or detect "alter session"?

My understanding is that an "alter session" command like alter session set time_zone='0:00' - when issued for a connection acquired via hikaricp - will affect all other connections as well.  Is that correct and can I somehow prevent or at least detect this?
Note: Oracle does not allow to prevent such an "alter session" because anyone who can connect can also issue (most) "alter session" commands.

We're not going to engage in SQL parsing, or even string matching, on every query just to catch this.  In short: don't do that.


Cannot Import from fastapi_users.db for Tortoise

Hi, i am a newbie trying to do learn how to use fastapi-users.
Following the example here https://frankie567.github.io/fastapi-users/configuration/full_example/, i was able to run with sqlalchemy and not tortoise orm
from fastapi_users.db import TortoiseBaseUserModel, TortoiseUserDatabase
ImportError: cannot import name 'TortoiseBaseUserModel' from 'fastapi_users.db'
I don't know if it's an issue or it is me doing something wrong. Any help would be helpful

Solved, i don't know why but making new project with new virtual environment works


CopyFile: more verbose error on failure

The real explanation of the error from cp is in the stderr output.

/ok-to-test

/retest


Make it clear that this is for Inbound traffic only and does not impact Outbound traffic from the App Service

In Christina Compy's announcement blog post on this she makes it clear that this does not affect traffic outbound from the App Service.  https://azure.github.io/AppService/2020/03/16/Public-Preview-of-Private-Link-on-App-Service.html   That is important and should be noted here as well for completeness and to avoid confusion on what Private Link provides for App Services.

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

ID: 2174e399-063b-129a-eef6-2c49a67fd4e2
Version Independent ID: 6cb95aa6-fb50-b966-4c9a-01e0718d0bcb
Content: Connect privately to a Web App using Azure Private Endpoint
Content Source: articles/app-service/networking/private-endpoint.md
Service: app-service
GitHub Login: @Ericgre
Microsoft Alias: ericg

hello, thank you for the feedback, but it's already in the doc :
Private Endpoint is only used for incoming flows to your Web App. Outgoing flows will not use this Private Endpoint, but you can inject outgoing flows to your network in a different subnet through the VNet integration feature.
Eric

Sorry about that Ericgre, my bad, I scanned the document for outbound not outgoing.   This came up in a research point for a customer.   You can close this issue.


Add unit and e2e tests

Making a good effort in paying the technical debt. Filing and fixing other issues while I find them while writing tests.
Issues fixed:
#35
#36

Because this code base is getting big and I keep making "big" changes to it, I'm going to do a best effort release of some tests to establish the testing infrastructure for v0.0.4 and can build on that later.


Revert "hugo migration"

Reverts DestinyMcQ/Destiny-s-Artistry#2

👷 Deploy Preview for destinysartistry processing.

Name
Link

🔨 Latest commit
d91fd0d19df6fef1178bcff04679537be710fb9b

🔍 Latest deploy log
https://app.netlify.com/sites/destinysartistry/deploys/633b30c10cb7e800081e61b8


Envoy x-envoy-upstream-rq-timeout-ms header on individual request being stripped out

Bug description
Making requests to a service with no VirtualService (or with a VirtualService with no timeout configured) that includes x-envoy-upstream-rq-timeout-ms does not take effect. The service responds successfully after its normal amount of time.
This should work, per https://istio.io/docs/tasks/traffic-management/request-timeouts/

One more thing to note about timeouts in Istio is that in addition to overriding them in route rules, as you did in this task, they can also be overridden on a per-request basis if the application adds an x-envoy-upstream-rq-timeout-ms header on outbound requests. In the header, the timeout is specified in milliseconds instead of seconds.

Relevant cluster dump info for the route
"route": {
  "cluster": "outbound|80||route-happy-service.default.svc.cluster.local",
  "timeout": "0s",
  "retry_policy": {
    "retry_on": "connect-failure,refused-stream,unavailable,cancelled,resource-exhausted,retriable-status-codes",
    "num_retries": 2,
    "retry_host_predicate": [
    {
      "name": "envoy.retry_host_predicates.previous_hosts"
    }
    ],
    "host_selection_retry_max_attempts": "3",
    "retriable_status_codes": [
      503
    ]
  },
  "max_grpc_timeout": "0s"
},

Relevant debug logs that show two extra headers I sent (x-my-test and x-envoy-upstream-rq-timeout-ms) were received differently:
[2019-06-17 17:10:29.394][27][debug][router] [external/envoy/source/common/router/router.cc:381] [C32248][S5641947549702591261] router decoding headers:
':authority', 'route-happy-service.default'
':path', '/uta'
':method', 'POST'
':scheme', 'https'
'user-agent', 'curl/7.52.1'
'accept', '*/*'
'content-type', 'application/json'
'x-my-test', 'true'
'content-length', '1019'
'x-forwarded-proto', 'http'
'x-request-id', 'a7a9cd5b-66e2-438a-8436-ab62ae2c1af4'
'x-envoy-decorator-operation', 'route-happy-service.default.svc.cluster.local:80/*'
'x-istio-attributes', 'CkkKF2Rlc3RpbmF0aW9uLnNlcnZpY2UudWlkEi4SLGlzdGlvOi8vZGVmYXVsdC9zZXJ2aWNlcy9yb3V0ZS1oYXBweS1zZXJ2aWNlCksKGGRlc3RpbmF0aW9uLnNlcnZpY2UuaG9zdBIvEi1yb3V0ZS1oYXBweS1zZXJ2aWNlLmRlZmF1bHQuc3ZjLmNsdXN0ZXIubG9jYWwKKgodZGVzdGluYXRpb24uc2VydmljZS5uYW1lc3BhY2USCRIHZGVmYXVsdAoxChhkZXN0aW5hdGlvbi5zZXJ2aWNlLm5hbWUSFRITcm91dGUtaGFwcHktc2VydmljZQpJCgpzb3VyY2UudWlkEjsSOWt1YmVybmV0ZXM6Ly9yb3V0ZS1oYXBweS1zZXJ2aWNlLTU3OTY5ODU1NmMtbHJoOXYuZGVmYXVsdA=='
'x-b3-traceid', '9518ddd2fc589ea0d881425e569c43e7'
'x-b3-spanid', 'd881425e569c43e7'
'x-b3-sampled', '0'

[2019-06-17 17:10:29.394][27][debug][router] [external/envoy/source/common/router/router.cc:381] [C32248][S5641947549702591261] router decoding headers:
':authority', 'route-happy-service.default'
':path', '/uta'
':method', 'POST'
':scheme', 'https'
'user-agent', 'curl/7.52.1'
'accept', '*/*'
'content-type', 'application/json'
'x-my-test', 'true'
'content-length', '1019'
'x-forwarded-proto', 'http'
'x-request-id', 'a7a9cd5b-66e2-438a-8436-ab62ae2c1af4'
'x-envoy-decorator-operation', 'route-happy-service.default.svc.cluster.local:80/*'
'x-istio-attributes', 'CkkKF2Rlc3RpbmF0aW9uLnNlcnZpY2UudWlkEi4SLGlzdGlvOi8vZGVmYXVsdC9zZXJ2aWNlcy9yb3V0ZS1oYXBweS1zZXJ2aWNlCksKGGRlc3RpbmF0aW9uLnNlcnZpY2UuaG9zdBIvEi1yb3V0ZS1oYXBweS1zZXJ2aWNlLmRlZmF1bHQuc3ZjLmNsdXN0ZXIubG9jYWwKKgodZGVzdGluYXRpb24uc2VydmljZS5uYW1lc3BhY2USCRIHZGVmYXVsdAoxChhkZXN0aW5hdGlvbi5zZXJ2aWNlLm5hbWUSFRITcm91dGUtaGFwcHktc2VydmljZQpJCgpzb3VyY2UudWlkEjsSOWt1YmVybmV0ZXM6Ly9yb3V0ZS1oYXBweS1zZXJ2aWNlLTU3OTY5ODU1NmMtbHJoOXYuZGVmYXVsdA=='
'x-b3-traceid', '9518ddd2fc589ea0d881425e569c43e7'
'x-b3-spanid', 'd881425e569c43e7'
'x-b3-sampled', '0'

Affected product area (please put an X in all that apply)
[ ] Configuration Infrastructure
[ X ] Docs
[ ] Installation
[ X ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastrcture
Expected behavior
A request to a service with x-envoy-upstream-rq-timeout-ms should timeout after the desired amount of time, especially when a VirtualService is not setting a value itself.
Steps to reproduce the bug

Deploy a service that takes at least a second to respond.
Make a request with x-envoy-upstream-rq-timeout-ms: 100.
See that the service responds normally after it's normal amount of time.

Version (include the output of istioctl version --remote and kubectl version)
istio 1.1.4 / k8s 1.11.8
How was Istio installed?
Helm w/mTLS

@jaygorrell
Could there be an application level conflict causing the issue?
Please check our updated docs on the topic: https://istio.io/docs/concepts/traffic-management/#compatibility-with-application-level-fault-handling

@rcaballeromx Wouldn't that only apply to things like retries where it compounds the value? In the case of a timeout, it doesn't matter if both are handling it since it's a short-circuit.
Either way, no application fault handling here, and having a 100ms timeout allow a 30+ second response come through is a good proof.

I have exact same problems.
If it is via istio-ilbgateway , this header will be overwritten and it will take effect.
But, It does not overwrite and take effect via mesh, and the x-envoy-upstream-rq-timeout-ms header is not output to the log.
Then it occurs not only x-envoy-upstream-rq-timeout-ms but also x-envoy-max-retries header.
Is there any update on this issue?
Version (include the output of istioctl version --remote and kubectl version)
istio 1.2.2 / k8s v1.13.6-gke.13
How was Istio installed?
Helm template w/mTLS

@istio/wg-networking-maintainers does this sound a real issue or intended behavior? Note the mentioned release is 1.1.

Re-open per https://github.com/istio/istio/issues/19111

@Dev25 @jaygorrell did you guys finally managed to solve this?
With this setup: nginx-ingress --> ingress-gateway --> VirtualService --> Pod I'm always getting an 15s timeout which I don't find a way to change.
This didn't happened without the nginx-ingress. Seems like the additional hops cause this headers to be stripped out.

The x-envoy-upstream-rq-timeout-ms header appears to work between containers if you use respect_expected_rq_timeout of envoy.
https://www.envoyproxy.io/docs/envoy/latest/api-v2/config/filter/http/router/v2/router.proto
In istio it seems to use EnvoyFilter for this setting, but I don't know how to set this up.


Kube support Apple Silicon M2

kubectl apply -f $(weaver kube deploy kube_deploy.yaml)

As Service Weaver Docs documentation deploy to local Kubernetes but got error message
$ kubectl logs weaver-main-c7d548af-4de23858-6cf988775f-clw9n
NewBabysitter: create envelope: NewEnvelope: connect to weavelet: read protobuf length: EOF
-----BEGIN STDERR-----
Cannot run macOS (Mach-O) executable in Docker: Exec format error

-----END STDERR-----
exit status 126

hey @cage1016 what are you using to run docker / k8 ?
I am also on a m2 Mac and use Orb Stack.  I used to use Docker on Mac etc, but am very happy with Orb Stack.  So it might help ...

This work has been deprioritized for now


test: 💍 Use generic handleSdkError function to handle errors

JIRA Link
DA-468
Changelog / Description
Remove the repetitive handling of errors while fetching some storage values from SDK. Use generic handleSdkError to handle conversion of SDK errors to throw corresponding exceptions
Checklist -

[ ] New Feature ?
[ ] Updated swagger annotation (if API structure is changed) ?
[x] Unit Test (if possible) ?
[ ] Updated the Readme.md (if required) ?

:tada: This PR is included in version 2.2.0-alpha.6 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.4.0-alpha.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.4.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add async filtering to portfolios

Changes

Added async filtering by name for portfolios
Portfolios component is now function using hooks
updated react-router-dom to be able to use router hooks

Fixes

fixed default count value for async pagination to 0

no longer shows 0 - 50 before the first API request is finished. Now its 0 - 0

@lgalis @gmcculloug limit should be now kept when filtering.

Codecov Report

Merging #279 into master will decrease coverage by 0.19%.
The diff coverage is 88.46%.

@@            Coverage Diff            @@
##           master     #279     +/-   ##
=========================================
- Coverage   83.67%   83.48%   -0.2%
=========================================
  Files         105      105
  Lines        1213     1223     +10
  Branches      104      106      +2
=========================================
+ Hits         1015     1021      +6
- Misses        180      184      +4
  Partials       18       18

Impacted Files
Coverage Δ

src/smart-components/common/async-pagination.js
54.54% <ø> (ø)
:arrow_up:

...ntational-components/shared/filter-toolbar-item.js
80% <ø> (ø)
:arrow_up:

src/toolbar/schemas/portfolios-toolbar.schema.js
100% <ø> (ø)
:arrow_up:

src/helpers/portfolio/portfolio-helper.js
76.92% <100%> (ø)
:arrow_up:

src/smart-components/portfolio/portfolios.js
83.87% <88%> (-11.37%)
:arrow_down:

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 290f5d4...c62cbd2. Read the comment docs.


gigablast support added issue #234

Fixes #234
Checklist

[x] I have read the Contribution & Best practices Guide and my PR follows them.
[x] My branch is up-to-date with the Upstream master branch.
[x] I have added necessary documentation (if appropriate)

Changes proposed in this pull request:

@starlord1311 this is your third PR for the same issue. I had commented on the very first issue that you're supposed to update your existing PR and not keep creating new ones for the same issue.
If face any problems while updating the PR, feel free to ask in the Gitter channels. But please don't keep making multiple PRs for the same issue

@niranjan94 sorry my laptop had crashed so had to make a new pr. wont happen next time

can someone help me with this pr?

its working totally fine when i am running it locally

There are a lot of issues with your PR. Nothing complicated but you are not following the basic guidelines because of which the build is failing.

First and foremost you need to fill out your PR description completely which is empty in many places.
Either use fix no of spaces or tabs in your code. Don't mix them.
Squash your commits into one, take help from this doc.
Take help from this latest Travis report on your PR which shows what you are doing wrong.

  when it is run locally.

 when it is run locally

Please squash your commits into one. Ignore UI bug, it'll be fixed in #372

Hi @starlord1311 do you know how to squash commits?  I learned how to squash commits a few months ago  so I could help you with that if you would be interested.  If so, please let me know, did you create this PR via git on the command line or by a gui tool that does git or by using the GitHub web pages?

@cclauss using git. can you help me with squashing the commits? because i read about it and the command is not working in the git

#309 and #360 will try to claim the letter "c".

git push --force origin gigablast_support

Please mention Gigablast in the README.md as well.

Bummer.  You are outa date...  now you gotta go thru these two step. https://docs.python.org/devguide/gitbootcamp.html#syncing-with-upstream

@cclauss did the required steps.

Double bummer...  My PR was merged at same time.  Do over;=(

@cclauss @realslimshanky can someone explain why codacy was unable to analyse. it is working perfectly fine when i run it locally. and till now codacy had approved the pr

@starlord1311 please amend your commit message and put a blank line in between.

This PR has gotten really long and also the recent master changes are not reflected.
Should we close this ?
suggestions @niranjan94
Thanks

@starlord1311, let's close this and create a fresh one :)

Agree with @AnshulMalik
No point in wandering here :sweat_smile:

We have achieved support for many search engines. We now focus on stability and performance. No more search engines are needed currently. Therefore closing this.


Put Nearform logo in bottom left

Issue:
Eyes are drawn to the NearForm logo although it is a secondary element in terms of hierarchy.
Fix:

Remove the Nearform logo from the header. https://github.com/nearform/node-clinic-common/pull/24 (Merged)
This PR will put the logo in the bottom left. Since https://github.com/nearform/node-clinic-flame/pull/115 created the space required. (Merged)

Recommended to merge https://github.com/nearform/node-clinic-flame/pull/115 before this one. (Merged)
Position of logo will be adjusted via:
https://github.com/nearform/node-clinic-common/pull/29

Looks a little offset vertically. Can it be centered vertically in the footer bar? Otherwise lgtm

@jasnell - Have a look here:

Position of logo will be adjusted via:

nearform/node-clinic-common#29


ngcc messes up ng version

🐞 Bug report
Command (mark with an x)

- [x] version

Is this a regression?
Regression caused by running ngcc
Description
When I run ngcc (via ng serve on an Ivy enabled project), ng version gives me some weird results.
🔬 Minimal Reproduction
ng new my-app --enable-ivy
cd my-app
ng serve # this runs ngcc
ng version
🔥 Exception or Error
Angular CLI: 8.0.0-beta.15
Node: 11.10.0
OS: linux x64
Angular: 8.0.0-beta.12
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.800.0-beta.15
@angular-devkit/build-angular     0.800.0-beta.15
@angular-devkit/build-optimizer   0.800.0-beta.15
@angular-devkit/build-webpack     0.800.0-beta.15
@angular-devkit/core              8.0.0-beta.15
@angular-devkit/schematics        8.0.0-beta.15
@angular/@types                   <error>
@angular/cli                      8.0.0-beta.15
@angular/events                   <error>
@angular/fire                     5.1.2
@angular/firebase                 <error>
@angular/rxjs                     <error>
@angular/source-map               <error>
@angular/tslib                    <error>
@angular/typescript               <error>
@ngtools/webpack                  8.0.0-beta.15
@schematics/angular               8.0.0-beta.15
@schematics/update                0.800.0-beta.15
rxjs                              6.4.0
typescript                        3.4.3
webpack                           4.29.6

I don't expect to see @angular/typescript or @angular/events or @angular/rxjs here.

Rob is having trouble reproducing this, but I've done it on both Linux and Mac (two machines), so it might be related to some environment condition (node 11? yarn?)

@petebacondarwin can you please take a look? This seems like a bug in the NGCC compiler.


Multiline constructor bug

The fromJson method of the multilinestring factory had a type issue. This is the fix.

resolves https://github.com/divvitco/geodart/issues/8


Rejection sink

Adds a new RejectSink which is basically just a FilterSink but it rejects with a SinkException rather than just dropping items.  Refactors how FilterSink is built to make it reusable for RejectSink.
Also cleaned up the test suite for basic sinks to split tests for each sink type out into their own test classes, plus renamed and refactored tests into Given, When, Then style.
Again this PR is consolidating pieces of work done elsewhere into a portable and reusable form for our Core Libraries.

I think we need to add the following dependencies to pom.xml in projectors-core:
<dependency>
    <groupId>org.apache.commons</groupId>
    <artifactId>commons-lang3</artifactId>
</dependency>

<dependency>
    <groupId>io.opentelemetry</groupId>
    <artifactId>opentelemetry-api</artifactId>
</dependency>

Otherwise I see a lot of red in IntelliJ in FilterSink.java

Weird those should already be there, mvn dependency:tree output with -Dincludes for the relevant libraries:

[INFO] --- dependency:3.8.1:tree (default-cli) @ projectors-core ---
[INFO] io.telicent.smart-caches:projectors-core:jar:0.25.0-SNAPSHOT
[INFO] +- io.telicent.smart-caches:observability-core:jar:0.25.0-SNAPSHOT:compile
[INFO] |  - org.apache.commons:commons-lang3:jar:3.17.0:compile
[INFO] +- org.apache.jena:jena-arq:jar:5.2.0:compile
[INFO] |  - org.apache.jena:jena-core:jar:5.2.0:compile
[INFO] |     - org.apache.jena:jena-base:jar:5.2.0:compile
[INFO] |        +- org.apache.commons:commons-csv:jar:1.12.0:compile
[INFO] |        - org.apache.commons:commons-compress:jar:1.27.1:compile
[INFO] - org.apache.commons:commons-collections4:jar:4.4:compile

[INFO] --- dependency:3.8.1:tree (default-cli) @ projectors-core ---
[INFO] io.telicent.smart-caches:projectors-core:jar:0.25.0-SNAPSHOT
[INFO] +- io.telicent.smart-caches:observability-core:jar:0.25.0-SNAPSHOT:compile
[INFO] |  - io.opentelemetry:opentelemetry-api:jar:1.44.1:compile
[INFO] |     - io.opentelemetry:opentelemetry-context:jar:1.44.1:compile
[INFO] - io.opentelemetry:opentelemetry-sdk:jar:1.44.1:test
[INFO]    +- io.opentelemetry:opentelemetry-sdk-common:jar:1.44.1:test
[INFO]    +- io.opentelemetry:opentelemetry-sdk-trace:jar:1.44.1:test
[INFO]    |  - io.opentelemetry:opentelemetry-api-incubator:jar:1.44.1-alpha:test
[INFO]    +- io.opentelemetry:opentelemetry-sdk-metrics:jar:1.44.1:test
[INFO]    - io.opentelemetry:opentelemetry-sdk-logs:jar:1.44.1:test

So guessing IntelliJ is being awkward about resolving dependencies for you?

mvn dependency:tree

I think the dependencies are being pulled in transitively, so it complies OK, but InitelliJ is probably complaining because if you run mvn dependency:analyze it shows them as being undeclared.

mvn dependency:tree

I think the dependencies are being pulled in transitively, so it complies OK, but InitelliJ is probably complaining because if you run mvn dependency:analyze it shows them as being undeclared.

Good point, generally we've somewhat relied on transitive dependencies so we don't end up redefining dependencies everywhere but may be worth reviewing that a bit to see if there's scope for minimising the dependencies in some modules e.g. I note projectors-core depends on jena-arq but never actually uses any Jena APIs


Add somthing

Reasons for making this change:
TODO
Links to documentation supporting these rule changes:
TODO
If this is a new template:

Link to application or project’s homepage: TODO

@NNickChen any links to StackOverflow discussions or other documentation about this change?

Seconding what @paulsmithkc said - this doesn't feel like an appropriate change to make, and without more context I plan to close this PR in a day or two.


[issue-4467] update linkis version to 1.4.0 for docker and snapshot

update linkis version to 1.4.0 for docker and snapshot #4467

1.3.2-SNAPSHOT
update to 1.4.0-SNAPSHOT


Increase footnote font size

Description

Increased footnote font size and spacing between footnotes.
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] Code quality improvements

How to test

Checklist

[x] I have tested this code
[ ] I have updated the documentation

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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 30.011%

Totals

Change from base Build 998516112:
0.0%

Covered Lines:
3196

Relevant Lines:
9805

💛  - Coveralls


change to use telescope export

@Conni2461
Currently we use :Telescope gh_issues for run command it is a nice command and easy to use even without mapping because it have autocomplete
if i use that export i need run :Telescope ghcli gh_issues or :Telescope ghcli issuses and the second path doesn't have autocomplete. It only complete ghcli word.

The second part will get completion with https://github.com/nvim-telescope/telescope.nvim/pull/398 not perfect but completion.
You should be able to rename your ghcli.lua to gh.lua and then users can do :Telescope gh issues
I just don't think we should promote any bad practices in an "official" telescope extension. People will come by and look at the code of other extensions to get an understanding how to write their own extension.

The second part will get completion with https://github.com/nvim-telescope/telescope.nvim/pull/398 not perfect but completion.
You should be able to rename your ghcli.lua to gh.lua and then users can do :Telescope gh issues
I just don't think we should promote any bad practices in an "official" telescope extension. People will come by and look at the code of other extensions to get an understanding how to write their own extension.

I update it and i will merge after telescope support full autocomplete on extensions

I update it and i will merge after telescope support full autocomplete on extensions

Thank you :)

Thank you :)


fix pipe.ts with - move properties to right place

related to https://github.com/KaotoIO/kaoto-next/issues/653

@tplevko I'll merge it after https://github.com/KaotoIO/kaoto-next/pull/691


Create 0000-01-02-YOUR-USERNAME

Add username's file.

created a branch, created a file and made a commit, and opened a pull request.


NETOBSERV-621 split summary metrics, limit 5 per chart

Also changed the textual stats above metrics: instead of showing in/out/both, they now show different stats: avg/total/latest
Before:

After:

@stleerh  / folks,
We discussed about this PR yesterday, I know there was some concerns for not showing the "both" view anymore (in + out traffic). I continue to think it's maybe not something needed and even desirable, because I'm not sure it really makes sense to compare volumes in and out and I fear it would just add unnecessary noise .. So as that something you raised I'm ok to create a follow-up task, I'd just ask if you could try this as it is now in day to day usage and see if really you feel this is limiting your experience or not

Just tested it and works as expected :+1:
As a user I would prefer checkboxes with indicators showing the number of metrics available on each since every situation is different.
It would avoid you to open a tab and see it's empty before moving to the other one for example:

Empty
Filled

I agree it simplify some tricky situations where it was not readable at all previously so this is an improvment, but you also loose comfort of looking all at once when you have 5 lines or less in your graphs

Previous (messy)
Previous (readable)
New In
New Out

If we really we can't do checkboxes for GA I'm fine merging this.

Ok, ok .. on popular demand, here's it back as a single metric tab - with radio button

Thanks Julien, looks good!
/approve


[Used by]  maven GAV has made a mistake

[x] I have searched the issues of this repository and believe that this is not a duplicate.
[x] I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: dubbo-2.7.1
Operating System version: win10 edge/chrome
Java version: 1.8

Steps to reproduce this issue

[Used by]  maven GAV has made a mistake

<dependency>
  <groupId>org.apache.dubbo</groupId>
  <artifactId>dubbo</artifactId>
  <version>ubbo-2.7.1</version>
</dependency>

Expected Result
<dependency>
  <groupId>org.apache.dubbo</groupId>
  <artifactId>dubbo</artifactId>
  <version>2.7.1</version>
</dependency>

ubbo-2.7.1 -> 2.7.1
Actual Result
What actually happens?
If there is an exception, please attach the exception trace:
Just put your stack trace here!

Yes, I notice that as well. But I don't know how Github is getting that.

Used by is temporarily closed.


'license' property added to the package.json

'npm' gives a warning regarding the lacking of 'license' property in the package.

This should be closed in favor of #37 as the license field should, according to npm spec, use SPDX identifiers.


Deduplicate identical multipart/form-data request payloads

Is your feature request related to a problem? Please describe.
Currently, if you start a capture and make the following two requests:
curl localhost -F foo=bar
curl localhost -F foo=bar

... Hoverfly will not recognize these as the same request, and it will record two request/response pairs in the simulation output.
This is because multipart/form-data POST request bodies separate the form fields using a user-defined delimiter (boundary), which is typically random. MDN has a nice concise description of how these requests are structured (with examples) here.
For the example above, the simulation shows the request bodies for these two requests as:
"body": [
	{
		"matcher": "exact",
		"value": "--------------------------9c2c1f1950ea2fff\r\nContent-Disposition: form-data; name=\"foo\"\r\n\r\nbar\r\n--------------------------9c2c1f1950ea2fff--\r\n"
	}
]

"body": [
	{
		"matcher": "exact",
		"value": "--------------------------400771b7006844db\r\nContent-Disposition: form-data; name=\"foo\"\r\n\r\nbar\r\n--------------------------400771b7006844db--\r\n"
	}
]

This means that if I run the same suite of requests multiple times, the simulation data set will grow in size with redundant copies instead of skipping the ones it's already seen.
Describe the solution you'd like
Ideally Hoverfly would be aware of multipart/form-data request bodies, and provide a mechanism that would allow these two requests to be considered identical (or use this behavior by default).
Describe alternatives you've considered
I suspect that these boundaries could be removed using a custom Middleware script, but I would prefer not to have to bring in a second library to parse HTTP in a spec-compliant way (or to rely on a home-grown parsing strategy).
Additional context
Brief mention of this problem on Gitter: Permalink

@tommysitu you can assign this to me. I would like to work on this issue.

@tommysitu  I looked at this issue and read about multipart/form-data. This form of encoding is basically used for sending files. We can send non-file or text fields as well. I feel we should not do a comparison of the files at the proxy layer primarily due to  2 reasons 1) security concerns (storing files on the proxy layer and then using it for comparison) 2) abuse (one can abuse the hoverfly proxy server) by sending huge files multiple times and reducing the space. I personally feel that we should limit this feature to non-file or text fields encoded with multipart/form-data. What do you suggest on the same?

@tommysitu could you please help me with the above concern? ^^

I think hoverfly should be used for matching structured data only, and multi-part form data is usually for uploading files, probably not worth supporting it.


[QUESTION]: Traffic is going to reverse proxy despite setting up authorization module sidecar

How can the Team help you today?
** We have enabled CSM authorization module and enabled the sidecar which has started successfully. The pvc requests are still going to reverse proxy and disabling the password causes failure **

Will raise as a bug


Set $LOAD_PATH instead of puppet's libdir

Commit 7f7e74f02c set puppet's libdir to include the lib directory for
each module in the modulepath. Doing so enabled puppet's autoloader to
load modules that hadn't been pluginsynced. However, this only worked for
code that the autoloader directly loaded. It didn't work when the
autoloaded type, provider, etc required helper code in the same module,
or different module, because the module's lib directory was not in ruby's
$LOAD_PATH.
The commit also relied on inconsistent behavior in puppet whereby sometimes
puppet assumed libdir was a (semi)colon separated list of directories, and
sometimes it assumed a single directory. In Puppet 4.0, puppet will
only interpret the libdir setting as a single directory[1].
As a result, this commit stops setting libdir and instead updates the
ruby $LOAD_PATH. In doing so, rspec-puppet is the "application" the uses
puppet as a "library". In that pattern, rspec-puppet is the thing that
sets the ruby $LOAD_PATH, and puppet just uses the specified $LOAD_PATH.
This is similar to how we fixed loading faces from modules[2] in commit[3].
[1] https://tickets.puppetlabs.com/browse/PUP-3336
[2] https://projects.puppetlabs.com/issues/7316
[3] https://github.com/puppetlabs/puppet/commit/4f99f25cd

@joshcooper Just came back to this one...
Any more thoughts?

@fatmcgav thanks for the ping. I think we need to figure out why RSpec::Puppet::Support#setup_puppet is never getting called. I would expect rspec-puppet to call it automatically as part of test framework setup so that modules don't need to, but I'm not sure about that.
Since setup_puppet is never called, many things are not configured correctly, e.g. vardir is set to /dev/null, in addition to the specific issue of $LOAD_PATH not being updated. Once we call setup_puppet things should just work.

Yeah, I've rebased and tested this locally and it works fine for me.

@hunner @DavidS I've updated the PR to resolve the conflict. I updated the setup_puppet method so that it allows modulepath to be specified, which is probably not the right thing for Puppet 4. Alternatively, I could something like the following, though I'm not sure what basedir should be  in rspec-puppet?
basedir = Puppet.version.to_f >= 4.0 ? Puppet[:environmentpath] : Puppet[:modulepath]
Dir["#{basedir}/*/lib"].entries.each do |lib|
  $LOAD_PATH << lib
end

Most important for rspec-puppet, as I'm currently using it, is to have the containing module's lib/ in the load path.

Changes Unknown when pulling d4278834d5236deb497b84fbd937bc33e6a717a3 on joshcooper:dont-set-libdir into ** on rodjek:master**.


Inconsistent context examples

When trying to learn contexts, I got stuck on the Docusaurus example. I had to reach for the Yew API docs (a.k.a. cargo docs for Yew Next) to get things working. That's when I noticed that the docs are inconsistent on this topic.
The first example is found in docs/concepts/contexts.mdx, which is hosted here on yew.rs.
The second example is on the use_context page in the Yew Next cargo docs.
Example 1:
#[derive(Clone, Debug, PartialEq)]
struct Theme {
    foreground: String,
    background: String,
}

#[function_component]
fn App() -> Html {
    let theme = use_memo(|_| Theme {
        foreground: "yellow".to_owned(),
        background: "pink".to_owned(),
    }, ());

    html! {
        <ContextProvider<Rc<Theme>> context={theme}>
            <NavButton />
        </ContextProvider<Rc<Theme>>>
    }
}

#[function_component]
fn NavButton() -> Html {
    let theme = use_context::<Theme>();

    html! {
        // use theme
    }
}

Example 2 (snippet):
#[derive(Clone, Debug, PartialEq)]
struct Theme {
    foreground: String,
    background: String,
}

#[function_component]
pub fn App() -> Html {
    let ctx = use_state(|| Theme {
        foreground: "#000000".to_owned(),
        background: "#eeeeee".to_owned(),
    });

    html! {
        // `ctx` is type `Rc<UseStateHandle<Theme>>` while we need `Theme`
        // so we deref it.
        // It derefs to `&Theme`, hence the clone
        <ContextProvider<Theme> context={(*ctx).clone()}>
            // Every child here and their children will have access to this context.
            <Toolbar />
        </ContextProvider<Theme>>
    }
}

/// The toolbar.
/// This component has access to the context
#[function_component]
pub fn Toolbar() -> Html {
    html! {
        <div>
            <ThemedButton />
        </div>
    }
}

/// Button placed in `Toolbar`.
/// As this component is a child of `ThemeContextProvider` in the component tree, it also has access to the context.
#[function_component]
pub fn ThemedButton() -> Html {
    let theme = use_context::<Theme>().expect("no ctx found");

    html! {
        <button style={format!("background: {}; color: {};", theme.background, theme.foreground)}>
            { "Click me!" }
        </button>
    }
}

Example 1 uses use_memo and ContextProvider<Rc<Theme>>. Example 2 uses use_state and ContextProvider<Theme>.
I suspect Example 1 is either incomplete or out-of-date because theme in NavButton has type Option<Theme>, which is not mentioned. It also has a None value if you try to unwrap, which is where I got stuck. Example 2 works fine.
It would be nice if the context docs were consistent.
I am not still not sure whether use_memo or use_state is preferred or if both can be used, but an explanation would be helpful.

Hi, I agree with you. I couldn't get the first example to work. use_context always returned None.
Also, the second example causes a performance problem as the context struct Theme will be cloned for each child using it.
I am currently implementing a translation system with a struct that I want to store on the state, and it is just not right to clone all of my Translator struct, with all of the loaded translations data, for each child.
Then I am wondering if Yew has the ability to support reference-based contexts, just like in example 1 (but it is not working), or should I use an external library?


Enable access logs per service at runtime

Describe the feature request
I'm on a mission to make istio more "debuggable".
I would like the ability to enable access logs at runtime on a per service basis.  You can do it at a mesh level here https://istio.io/latest/docs/tasks/observability/logs/access-log/#enable-envoy-s-access-logging but that is extremely overkill when you're just debugging a single service.
Describe alternatives you've considered
None (open to suggestions)
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[x] User Experience
[x] Developer Infrastructure
Additional context

We discussed in the networking wg, we expect 1.8 to have first class API to do that and till such time the recommendation is to use EnvoyFilter to enable per service. Sample filter https://github.com/nrjpoddar/cncf_webinar_istio_debugging/blob/master/access_log_envoy_filter_workload.yaml

Ahhh great stuff, thank you @ramaraochavali

@ramaraochavali @nrjpoddar I don't suppose you know if I can configure the raw envoy logging level by an EnvoyFilter?
The access logs are useful but the http logs (showing request/response headers) in envoy are super useful.

AFAIK, that is not possible via Envoy filters. Only way I know of to control the Envoy raw logging is via annotations.

@Stono can you update the issue to say first class APIs for both access and component logs? As @ramaraochavali mentioned we don't have a good mechanism for turning on "debug" Envoy logging at a service/workload level especially in a auto-scale scenario without requiring restarts.

Aye Aye captain

cc @douglas-reid @mandarjog for visbility.

@mandarjog tangentially, this is somewhat related to prior discussions around telemetry profiles and allowing a "debug this service" type of interaction (as opposed to turning on all different types of logs, traces, metrics, etc., independently).

Does envoy even support configuring log levels via XDS? perhaps with RTDS?


Add E2E test for snapshot in S3 minio

[x] Postgres. xref: https://github.com/kubedb/postgres/pull/272
[ ] Elasticsearch
[ ] MongoDB
[ ] MySQL

I think we should add those tests to Stash. Not to kubedb anymore after postgres is done.


Get save slice working in v2

Done:

dump json blob into slice.params of new slice
pass save_slice params in original format
@mistercrunch

LGTM, thanks for fixing!


Implement (mutable) memory views to avoid allocation/copies of set/get routines

Memory instance is in the interpreter in the wasmi crate


Add Release To Build And Upload Workflow

Issue #, if available:
N/A
Description of changes:
Add Release To Build And Upload Workflow. Add build and upload task with release disabled in workflow dispatch on merge to main.
https://github.com/aws/amazon-cloudwatch-agent-operator/actions/runs/8332755543/job/22804130603
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

https://github.com/aws/amazon-cloudwatch-agent-operator/actions/runs/8348547133/job/22852147688
Change after skipping full step instead of just upload to release


Update README.md

Allow the required peer dependancies and also to install, rather than run

Thank you @gbrits for your contribution. I had totally not seen this typo.

Thank you @gbrits for your contribution. I had totally not seen this typo.

Any time :)


Add more context error messages

Scope & Purpose
Add error message details for some agencycomm failure scenarios.
Only relevant for debug and trace logging.
There will be no PRs for 3.7 and devel, as all the AgencyComm was restructured in 3.7 and this code simply does not exist anymore there.

[ ] Bug-Fix for devel-branch (i.e. no need for backports?)
[x] Bug-Fix for a released version (did you remember to port this to all relevant release branches?)

Testing & Verification
This change is a trivial rework / code cleanup without any test coverage.
http://<IP_ADDRESS>:8080/view/PR/job/arangodb-matrix-pr/10861/

Tests blue