Allow to customize persisted operations errors

Description
This PR aims to allow the customization of errors in Persisted Operations plugin.
Issue
fixes #2047
Concerns
I have implemented multiple ways to customize errors with polymorphic options. I'm not sure if this wanted, since it seems this pattern is not heavily used in the code base. But I think it can be a good DX, since the most general use-case will probably to add a static extensions such as HTTP status.
Don't hesitate If you have suggestion about option names, I'm not totally satisfied.
I also give access to the payload of the onParams function to the error factory. Perhaps I should filter to avoid passing setters and only give access to params and request ?
Usage example
import { createYoga } from 'graphql-yoga'
import { createServer } from 'node:http'
import { usePersistedOperations } from '@graphql-yoga/plugin-persisted-operations'
import { CustomErrorClass } from './custom-error-class'

const yoga = createYoga({
  plugins: [
    usePersistedOperations({
      customErrors: {
        // You can change the error message
        notFound: 'Not Found',
        // Or customize the error with a GraphqlError options object, allowing you to add extensions
        keyNotFound: {
          message: 'Key Not Found',
          extensions: {
            http: {
              status: 404
            }
          }
        },
        // Or customize with a factory function allowing you to use your own error class or format
        persistedQueryOnly: () => {
          return new CustomErrorClass('Only Persisted Operations are allowed')
        }
      }
    })
  ]
})

const server = createServer(yoga)
server.listen(4000, () => {
  console.info('Server is running on http://localhost:4000/graphql')
})

Looks good! Thanks @EmrysMyrddin !


Prevent inconsistent data in json files.

Dumping the json content directly into the final output files creates
inconsistend data temporarily, which may cause strange
effects. Writing to temporary files and atomically renaming them
should fix this.
Works only on unix-like systems where os.rename can overwrite existing
files.

@tobox it would be nice if you fix the problems which let the tests to fail.

This only fixes a small aspect of the bigger problem that also caused #44, namely that apparently in many instances, the output of this script currently is served directly by webservers. This PR may guarantee an atomic modification to the JSON files, but not to the RRDs or PNGs. So I somehow have the feeling there should be a more general approach to the bigger problem, rather than fixing several small effects it has.

If somebody was working on fixing the bigger problem, I would agree that this PR should not be merged yet. If nobody is working on it, I guess a workaround for real-world problems should be considered for merging, especially since this minor change is trivial to revert.

I have (unfortunately) seen a complete messed up nodes.json due to some hard reset of a server. I would therefore appreciate such a change. But It would be good when the buffer is actually written to disk before the file is renamed
f.flush()
os.fsync(f.fileno())


CircleAvatar jpeg图片无法显示为圆形 (CircleAvatar jpeg image cannot be displayed as a circle)

CircleAvatar(
    child: Image.asset('lib/images/none.jpeg'),
    radius: 32.0,
),

他应该是个圆形，但是却显示了方形
(google translate)
He should be a circle, but it shows a square

@lpxiana Please provide your flutter doctor -v output. does it display it in original form or doesn't display at all? Are there any errors when you run it with --verbose?

Instead of this:
CircleAvatar(
child: Image.asset('lib/images/none.jpeg'),
radius: 32.0,
),
Use this:
CircleAvatar(
backgroundImage: AssetImage('lib/images/none.jpeg'),
),

https://api.flutter.dev/flutter/material/CircleAvatar-class.html


add structure tab

fix #3

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


Vscode dev containers extension seems not to respect http.proxy setting

Hi, I am using vscode and vscode dev containers extension with a proxy. However the extension seems to not respect http.proxy and connect to microsoft server directly, whereby vscode stuck at 'Adding dev container configure file'.

VSCode Version:  1.74.0
Local OS Version: Debian Buster
Local chip architecture: arm64
Reproduces in: Remote - Containers
Name of Dev Container Definition with Issue: Debian

Steps to Reproduce:

Let the local machine access Internet only via http.proxy.
Open an empty folder in vscode
Add dev container configure file
vscode sucks

It seems that the extension tries to connect microsoft server directly.
netstat -an | grep 443
tcp        0      1 <IP_ADDRESS>:33536       <IP_ADDRESS>:443       SYN_SENT

I think this is duplicate of microsoft/vscode-remote-release#7431


Add DeploymentAware = false parameter into build

Add DeploymentAware = false parameter into build
https://docs.camunda.org/manual/7.6/user-guide/process-engine/the-job-executor/#job-execution-in-heterogeneous-clusters.
This will ensure that when server is restarted, any async jobs will still execute.

@baddlan can you look into this please


💬 RFC: Break Sliding Version Policy for the React 18 Upgrade

🔖 Need
Maintaining the sliding version policy of supporting both React 17 and 18 will cause more headaches for maintainers, consumers, and developers than it will solve. Since many libraries have broken support from 17 to 18, Backstage will have to introduce extra complexity to maintain compatibility between the two versions. This means contributors will need to write more code to work around this inflexibility, and maintainers will have to put in more effort to properly review submissions.
Additionally, plugin developers will also have to introduce similar logic to maintain compatibility between the two versions, since there may still be people relying on React 17. Besides the code complexity, we have seen contributors run into issues with Material UI typing due to having support for both React 16 and 17. Finally, developers will have to adjust their codebases to support React 18 anyway, so breaking the versioning policy in this case will make that work simpler for them.
There are going to be a few places where support for React 17 and 18 will be difficult from a library imports standpoint. To begin with, the way we render components in React 18 will look like:
/* rendering the root in React 17 */
import React from 'react';
import ReactDOM from 'react-dom';

const container = document.getElementById('root');
ReactDOM.render(<App />, container);

But in React 18, we make the following changes:
import { createRoot } from 'react-dom/client';
const container = document.getElementById('app');
const root = createRoot(container!);
root.render(<App tab="home" />);

The two versions can then be rendered by version checking and dynamically importing the relevant modules:
import '@backstage/cli/asset-types';
import React, { type ReactNode } from 'react';
import App from './App';

// render conditionally depending on the react version
const version = React.version.split('.');
const container = document.getElementById('root');
let renderMethod: (element: ReactNode) => void;

// react 18
if (version[0] === '18') {
  const { createRoot } = require('react-dom/client');
  const root = createRoot(container!);
  renderMethod = (el: ReactNode) => root.render(el);
  // react 17
} else {
  const { render } = require('react-dom');
  renderMethod = (el: ReactNode) => render(el, container);
}

renderMethod(<App />);

While this doesn’t look appealing on the eyes, it’s still not a very common method to write, since it only needs to exist in a single place realistically.
Unfortunately, the problem doesn’t just end here. @testing-library/react-hooks, an important module which Backstage relies on for many test suites, drops support for React 18 entirely. Instead, the maintainers suggest using @testing-library/react. In addition to moving libraries, their testing APIs have also changed, as well as their signatures and how they are expected to be used.
For example, the old version of renderHook from @testing-library/react-hooks would return a number of values, such as the error (if any), helper functions to wait until a specific event such as an update or value change, and a waitFor function. The new version of renderHook only returns the result of rendering the hook, and rerender and unmount functions. In order to utilize the other functions, they must be imported from the library:
- const { result, waitForValueToChange } = renderHook(() =>
+ const { result } = renderHook(() =>
   useEntityRelationNodesAndEdges({
     rootEntityRefs: ['b:d/c'],
     unidirectional: true,
     mergeRelations: true,
   }),
 );

As if this wasn’t already inconvenient, the waitForValueToChange function no longer exists in the new @testing-library/react library whatsoever. The developers now recommend you to instead use the waitFor function. Following the above test, the way it would use waitForValueToChange would then need to change from:
// old method uses this function here
await waitForValueToChange(
    () => result.current.nodes && result.current.edges,
);

// more test logic down here
const { nodes, edges, loading, error } = result.current;

expect(loading).toBe(false);
expect(error).toBeUndefined();
// more expects down here

To now instead doing:
// now we must keep re-running our expects inside of this function
// until it stops throwing an error
await waitFor(() => {
	const { nodes, edges, loading, error } = result.current;

	// these will throw
	expect(loading).toBe(false);
	expect(error).toBeUndefined();
	// more expects down here
});

Besides this, there is another problem. I mentioned earlier that renderHooks no longer returns error as a field. With the new library, you have to explicitly wrap the hook into a function which calls renderHook, and then you call it and assert that it throws an error. Here is an example of how it’s done in React 17 versus 18:
// old method:
const { result } = renderHook(
  props =>
    useElementFilter(props.tree, elements =>
      elements
        .selectByComponentData({
          key: WRAPPING_COMPONENT_KEY,
          withStrictError: 'Could not find component',
        })
        .findComponentData({ key: INNER_COMPONENT_KEY }),
    ),
  {
    initialProps: { tree },
    wrapper: Wrapper,
  },
);
expect(result.error?.message).toEqual('Could not find component');

In the new method:
const run = () =>
  renderHook(
    props =>
      useElementFilter(props.tree, elements =>
        elements
          .selectByComponentData({
            key: WRAPPING_COMPONENT_KEY,
            withStrictError: 'Could not find component',
          })
          .findComponentData({ key: INNER_COMPONENT_KEY }),
      ),
    {
      initialProps: { tree },
      wrapper: Wrapper,
    },
  );

expect(run()).toThrow(new Error('Could not find component'));

In theory, supporting all of this functionality while maintaining the version window is possible. Though you can probably sense from the above examples, it would add a lot of additional complexity. This would be a problem for both existing and new contributors alike. Especially when you consider that Backstage is meant to be used by large enterprises, many of which may be coming from non-TypeScript backgrounds such as Java and C#.
Yet another problem that we uncovered switching dependencies was that certain components would re-render twice with the newer version of React. For example, the following test verifies that components will receive APIs and does so by throwing an error via the errorApi:
  it('should provide mock API implementations', async () => {
    const A = () => {
      const errorApi = useApi(errorApiRef);
      errorApi.post(new Error('NOPE'));
      return null;
    };

    const { error } = await withLogCollector(['error'], async () => {
      await expect(renderInTestApp(A)).rejects.toThrow('NOPE');
    });

    expect(error).toEqual([
      expect.objectContaining({
        detail: new Error(
          'MockErrorApi received unexpected error, Error: NOPE',
        ),
      }),
      expect.stringMatching(/^The above error occurred in the <A> component:/),
    ]);
  });

In React 18, we encountered a problem where this component would re-render twice, so we would need to check for that error to have been thrown twice. After investigating, we found that the only way to avert this behavior without rewriting any of the code was by forcing the testing library to render with synchronous mode by passing legacyRoot: true to the render method from @testing-library/react. This causes the component to fallback to using the rendering method for React 17. Although this is a fixable problem, it illuminates another point where messy logic would have to be introduced in order to compensate for the fact that we are supporting multiple React versions. Having to fallback to legacy rendering in tests would also mean missing behavior that would exist when someone is running Backstage with React 18 – a significant portion of the user base.
Another issue you’ll encounter maintaining compatibility is that, because @testing-library/react drops support for React 17 altogether, we would need to take some extra steps in order for it to pull a React-17 compatible version. Because this is a major breaking change from their side, the APIs used from that package would change depending on the respective version of React being used. For reference, this is the number of tests affected by this change:

(yes I am using a light theme in this screenshot and proud of it)
🎉 Proposal
We propose the following:

We will break the version window policy in order to avert adding additional complexity to maintain a legacy React version. While this isn’t ideal, it will help prevent headaches for many contributors and maintainers. Since we will only be worrying about a single version of React, debugging React-specific issues will be straightforward, because we’ll be able to rule out any legacy behavior. This will ease the burden for new adopters as well, because they will not have to write their components and tests with multiple versions in mind. Maintainers will also benefit from this, since the code will be simpler to read, reviewing PRs will be much easier. Since many libraries already require React 18 anyway such as Material UI v5, much of the code will need to be migrated to use React 18 regardless. Breaking the version window will simply reduce the amount of code that will need to be written for it.
We will do our best to provide resources in order to assist anyone still on React 17 migrate their codebase and test suites to the new version. We can contribute any tooling that will be necessary here, provide documentation on what to upgrade, how to upgrade, and assist community members with the upgrade.

〽 Alternatives
We have considered maintaining compatibility with both React 17 and 18, despite the complexity and the overhead it would introduce. The alternative would involve:

Conditional Rendering: By writing conditional rendering logic, we could support both React 17 and 18. However, this could make our code harder to maintain and less readable. Moreover, the cases where the logic is required are rare, which makes the effort seem disproportionate.
Testing Libraries: We considered keeping the @testing-library/react-hooks for React 17 and using @testing-library/react for React 18. However, this alternative would force us to adapt to two different testing APIs, and it might also imply duplicate tests or conditional testing logic.
Legacy Rendering: Using legacyRoot: true in tests to fall back to React 17 rendering could avoid the double rendering issue in React 18. However, this would also mean our tests wouldn't accurately represent the behavior seen by a significant portion of our user base running Backstage with React 18.  Note: This will only help with tests, not the main app, so it’s not a complete alternative.

❌ Risks
The primary risks associated with this proposal include:

Community Acceptance: There's a risk of causing friction within the community, particularly for those who still rely on React 17. These users would be compelled to upgrade to React 18.

Testing Coverage: By moving away from legacy rendering in tests, there is a potential risk of uncovering new, unanticipated issues that could affect the stability of our codebase.

Migration Complexity: The migration process from React 17 to 18 might be challenging for some users, particularly those new to Backstage or from non-TypeScript backgrounds.

Dependency Problems: There's also a risk associated with the dependencies, especially for frontend plugins, that have broken compatibility between React 17 and 18, which might introduce unknown challenges that we have yet to anticipate.

Future Precedent: This move could set a precedent for breaking the sliding version window policy for future upgrades, which could lead to uncertainty about our versioning policy.

It feels like it’s possible to have both React 17 & 18 code in the same codebase. The problem is that I can sense it introducing lots of complexity and giving maintainers a death by a thousand cuts. I also feel like for many dependencies, this isn’t a problem, because with something like an Apollo GraphQL client, it only gets used so much. But since React is a fundamental part of the codebase, it becomes a much more intensive thing to maintain.
I’m sure that there’s a lot of stuff that can be tested to see what works / what doesn’t, but the problem is that it has to be done in the first place.
👀 Have you spent some time to check if this RFC has been raised before?

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

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

We upgraded to React 18 in late May of this year. It was a pretty smooth migration and has been smooth sailing ever since. We would consider our Backstage instance about mid-sized with little over a dozen custom frontend plugins just to give you a sense of size. Where we have a gap is our test coverage isn't as good as we would like and the most work for this migration was around fixing tests.

Summary of discussion that we had last week around this: We're still hopeful that we'll be able to ship support for v18 without breaking compatibility with v17. We would still do an immediate switch to v18 in this repo and stop testing towards v17, but that doesn't mean we need to break v17 support. In the few places where it might be required, such as test utilities, we will provide best effort multi-version support without tests. The support for v17 may slowly or immediately break over time after this initial release, but we will aim to have at least a few releases that provide a window for projects to migrate to v18 at their own pace.

Thanks, everyone for the comments! This seems to be addressed by #20598, right?
We're closing this issue, but feel free to reopen it if that's not the case 🙌🏻


Text to voice

Issue Type:

[ x] Feature Request

Describe the bug
just like voice to text app, isn't it awesome ,if we add  text to voice project
Possible solution
I want to add text to voice Project.

Add functionality in that same project

Add functionality in that same project

Ohh, maam, i saw  few moments back , it is already present in your projects.Ok, i will surely add more functionalities in the same project.

@mayank-del ?


Strings like 'l2' and 'l1' would be preferable as 'L2' and 'L1"

In skimming over the changes that black did I noticed the strings 'l1' and 'l2'. Normally for names lower case l is avoided as it can be mistaken for capital I and even for numeric 1 depending on font. I think it would be preferable to have these as uppercase L, since the docstring even talks about L2 loss where L is in capitals. This is in code like NetworkNeuralClassifier/Regressor among others. And where we test the value, if we choose to accept lower case for compatibility, then maybe do an upper() so it can be compared to 'L2' etc.

I agree in general, but we have other loss functions coded as lower case strings: cross_entropy, cross_entropy_sigmoid, so I think we need a consistent solution. I suggest replace l1 with absolute_error and l2 with squared_error.
@beichensinn what do you think?

The strings across the API are case insensitive as it does a lower() on what is passed in to compare against constants in the code in lowercase. If upper() was done instead it would just mean the constants all became upper internally and maybe we'd show them that way in the docstring too. It would not change the API in this case; but changing to different strings means deprecating the l1 and l2 so they'd have to stay in the code for a while. Of course doing this upper() instead, and having it as 'L1' internally and in the docs, the API, would not prevent users from using the 'l1' etc in lowercase in their code and thus have the potential readability problem there still, that different strings would prevent.

@woodsp-ibm @adekusar-drl I am new to qiskit contributions but I am interested in picking up this issue. Would that be ok?
I think using upper() and comparing to 'L1' internally is a good idea since it would make the code more readible and the docstrings more clear. I think it could also be beneficial to add support for 'absolute_error' and 'squared_error' in addition to 'L1' and 'L2' respectively.
I also saw a comment in #92 suggesting that we should extract the if...else block to a seperate class and I could see that being in the scope of this PR. Do you agree? If so, could you provide some more information on that (e.g. what class should I look at)?
Thanks!

@mattwright99 Surely, you can work on this issue!
I'd prefer to keep string constants in lower case just to keep them more readable in the documentation. I suggest to gracefully deprecate l1 and l2 in favor of 'absolute_error' and 'squared_error' cause this would solve the issue completely.
The if block you mentioned, is it the if block where we instantiate a loss object out of a string value? If so, then I happy to discuss your suggestion here, but please don't code it upfront.

@adekusar-drl Alright, i am excited to start contributing!
My plan at the moment is to change all the occurances of 'l1' and 'l2' to 'absolute_error' and 'squared_error' throughout the source code, the unit tests, and documentation. I will also continue to handle 'l1' and 'l2' as we do now but output a depreciation warning if they are provided. Should i use the deprecate_arguments() function? If so, could you explain how that works or point me to an example? Anything else I might be missing?

@adekusar-drl I added all the possible ways you can use deprecations in the test_deprecation.py. However All methods/decorators expect you to deprecate a class, method, argument. property or function. Nothing for default values. The message being created automatically doesn't support it. Would it be possible for you to add a warnings.warn method in your PR for that situation and I will then create some method to support it and use it in place, either in the same PR or another ?

@manoelmarques Yes, we can generate manual warnings.
@mattwright99 Please add lines like these:
warnings.warn(
    "The 'l2' value is deprecated as of 0.2.0 "
    "and will be removed no sooner than 3 months after the release. "
    "You should use the 'squared_error' value instead.",
    DeprecationWarning,
)

The version number in the text depends on the date when you'll be able to finish the PR. We can edit it later on.

@adekusar-drl sounds good, I am just about to publish a PR


Improvements

This is what I'm using. Seems that the maintainer is not committing any more changes, so I'm just putting this here in case it's useful to anyone else. It'd be cool if somebody (not me 🙃) wants to actively maintain a fork.
Incorporates https://github.com/Russell91/sshrc/pull/102 and https://github.com/Russell91/sshrc/pull/75 with fixes and tweaks. Also respects  .hushlogin on a second hop by checking for $SSHHOME/.sshrc.d/.hushlogin.

I'll be glad to review and pull then into my fork.

👍 Where is your fork?


Final presentations Wednesday, May 6th at 6:00pm at BIDS

Hey @berkeley-dsc/purchasing - this is a thread to coordinate information / images / etc for the BIDS final presentation. Here's the info:
Where - BIDS
When - May 6th, 6:00pm
What - Probably a 10-15 minute presentation with a bit more info than last time
Let me know if you guys can be there...this'll be the last official presentation for this project, so you should come and get some credit. There will also be a happy hour afterward.
I'm going to need some updated pretty pictures, and a few talking points for each project. We can discuss tomorrow.
It would be great if @agcinsf could be there as well...let me know if that's possible so I can tell Anthony etc.
Thanks for all your hard work guys, getting close to the finish line!

why so late in the day???
this makes it difficult for folks with kids
darius
On Wed, Apr 22, 2015 at 11:04 AM, Chris Holdgraf<EMAIL_ADDRESS>wrote:

Hey @berkeley-dsc/purchasing
https://github.com/orgs/berkeley-dsc/teams/purchasing - this is a
thread to coordinate information / images / etc for the BIDS final
presentation. Here's the info:
Where - BIDS
When - May 6th, 6:00pm
What - Probably a 10-15 minute presentation with a bit more info than
last time
Let me know if you guys can be there...this'll be the last official
presentation for this project, so you should come and get some credit.
There will also be a happy hour afterward.
I'm going to need some updated pretty pictures, and a few talking points
for each project. We can discuss tomorrow.
It would be great if @agcinsf https://github.com/agcinsf could be there
as well...let me know if that's possible so I can tell Anthony etc.
Thanks for all your hard work guys, getting close to the finish line!
—
Reply to this email directly or view it on GitHub
https://github.com/berkeley-dsc/purchasing/issues/18.

--
Darius Mehri
Ph.D. Candidate, Sociology
University of California, Berkeley

I think they Anthony thought that later would increase attendance...I
didn't really have a say in the matter, but I will let the organizing team
know about this issue.
On Wed, Apr 22, 2015 at 11:08 AM, dariusmehri<EMAIL_ADDRESS>wrote:

why so late in the day???
this makes it difficult for folks with kids
darius
On Wed, Apr 22, 2015 at 11:04 AM, Chris Holdgraf<EMAIL_ADDRESS>
wrote:

Hey @berkeley-dsc/purchasing
https://github.com/orgs/berkeley-dsc/teams/purchasing - this is a
thread to coordinate information / images / etc for the BIDS final
presentation. Here's the info:
Where - BIDS
When - May 6th, 6:00pm
What - Probably a 10-15 minute presentation with a bit more info than
last time
Let me know if you guys can be there...this'll be the last official
presentation for this project, so you should come and get some credit.
There will also be a happy hour afterward.
I'm going to need some updated pretty pictures, and a few talking points
for each project. We can discuss tomorrow.
It would be great if @agcinsf https://github.com/agcinsf could be
there
as well...let me know if that's possible so I can tell Anthony etc.
Thanks for all your hard work guys, getting close to the finish line!
—
Reply to this email directly or view it on GitHub
https://github.com/berkeley-dsc/purchasing/issues/18.

--
Darius Mehri
Ph.D. Candidate, Sociology
University of California, Berkeley
—
Reply to this email directly or view it on GitHub
https://github.com/berkeley-dsc/purchasing/issues/18#issuecomment-95287333
.

Apologies for the evening event.  I hope all team members are able to attend, to receive the credit you all deserve.  As Chris mentioned, the logic behind the 6pm start time was to allow industry partners with 5pm COB to attend.  Truly, there was no 100% optimal solution here.

ok, i just may not be able to attend, i have to check w/ my wife, darius
On Wed, Apr 22, 2015 at 11:12 AM, Chris Holdgraf<EMAIL_ADDRESS>wrote:

I think they Anthony thought that later would increase attendance...I
didn't really have a say in the matter, but I will let the organizing team
know about this issue.
On Wed, Apr 22, 2015 at 11:08 AM, dariusmehri<EMAIL_ADDRESS>wrote:

why so late in the day???
this makes it difficult for folks with kids
darius
On Wed, Apr 22, 2015 at 11:04 AM, Chris Holdgraf <
<EMAIL_ADDRESS>
wrote:

Hey @berkeley-dsc/purchasing
https://github.com/orgs/berkeley-dsc/teams/purchasing - this is a
thread to coordinate information / images / etc for the BIDS final
presentation. Here's the info:
Where - BIDS
When - May 6th, 6:00pm
What - Probably a 10-15 minute presentation with a bit more info than
last time
Let me know if you guys can be there...this'll be the last official
presentation for this project, so you should come and get some credit.
There will also be a happy hour afterward.
I'm going to need some updated pretty pictures, and a few talking
points
for each project. We can discuss tomorrow.
It would be great if @agcinsf https://github.com/agcinsf could be
there
as well...let me know if that's possible so I can tell Anthony etc.
Thanks for all your hard work guys, getting close to the finish line!
—
Reply to this email directly or view it on GitHub
https://github.com/berkeley-dsc/purchasing/issues/18.

--
Darius Mehri
Ph.D. Candidate, Sociology
University of California, Berkeley
—
Reply to this email directly or view it on GitHub
<
https://github.com/berkeley-dsc/purchasing/issues/18#issuecomment-95287333

.

—
Reply to this email directly or view it on GitHub
https://github.com/berkeley-dsc/purchasing/issues/18#issuecomment-95288605
.

--
Darius Mehri
Ph.D. Candidate, Sociology
University of California, Berkeley

i see, no worries, darius
On Wed, Apr 22, 2015 at 11:50 AM, Daniel Turek<EMAIL_ADDRESS>wrote:

Apologies for the evening event. I hope all team members are able to
attend, to receive the credit you all deserve. As Chris mentioned, the
logic behind the 6pm start time was to allow industry partners with 5pm COB
to attend. Truly, there was no 100% optimal solution here.
—
Reply to this email directly or view it on GitHub
https://github.com/berkeley-dsc/purchasing/issues/18#issuecomment-95299767
.

--
Darius Mehri
Ph.D. Candidate, Sociology
University of California, Berkeley

hey @agcinsf, any chance that you can make it to this? The organizers are trying to get a head count on collaborators who are going to be present.

Absolutely I will be there.
Ac

On May 2, 2015, at 11:39 AM, Chris Holdgraf<EMAIL_ADDRESS>wrote:
hey @agcinsf, any chance that you can make it to this? The organizers are trying to get a head count on collaborators who are going to be present.
—
Reply to this email directly or view it on GitHub.

@dariusmehri and @nlin3330, I really like the graphs and networks that you've put on the google drive (in the network_analysis_data folder). It sounds like there are a lot of interesting stats in there (e.g., betweenness). Can you create some quick summary plots of these (e.g., the distribution of betweenness scores for all departments for one month over 3 years).

hi chris, i am working on this, the graphs are interesting but there is not
much detail because they are not broken down according to item type, i have
item type graphs but haven't posted them yet, i will send out all plots,
graphs, story, conclusion, what to do going forward, and so on, this
evening in power point,  and will post all graphs and so on on drive, i
will be focusing on a few measures and graphs for the presentation (so not
to confuse the participants or muddle up with too much info), darius
On Mon, May 4, 2015 at 4:42 PM, Chris Holdgraf<EMAIL_ADDRESS>wrote:

@dariusmehri https://github.com/dariusmehri and @nlin3330
https://github.com/nlin3330, I really like the graphs and networks that
you've put on the google drive (in the network_analysis_data folder). It
sounds like there are a lot of interesting stats in there (e.g.,
betweenness). Can you create some quick summary plots of these (e.g., the
distribution of betweenness scores for all departments for one month over 3
years).
—
Reply to this email directly or view it on GitHub
https://github.com/berkeley-dsc/purchasing/issues/18#issuecomment-98885549
.

--
Darius Mehri
Ph.D. Candidate, Sociology
University of California, Berkeley

ok that sounds great. I'll try to incorporate some of your plots in the
poster as well. The bigger (in resolution) the images are, the better.
On Mon, May 4, 2015 at 4:53 PM, dariusmehri<EMAIL_ADDRESS>wrote:

hi chris, i am working on this, the graphs are interesting but there is not
much detail because they are not broken down according to item type, i have
item type graphs but haven't posted them yet, i will send out all plots,
graphs, story, conclusion, what to do going forward, and so on, this
evening in power point, and will post all graphs and so on on drive, i
will be focusing on a few measures and graphs for the presentation (so not
to confuse the participants or muddle up with too much info), darius
On Mon, May 4, 2015 at 4:42 PM, Chris Holdgraf<EMAIL_ADDRESS>wrote:

@dariusmehri https://github.com/dariusmehri and @nlin3330
https://github.com/nlin3330, I really like the graphs and networks
that
you've put on the google drive (in the network_analysis_data folder). It
sounds like there are a lot of interesting stats in there (e.g.,
betweenness). Can you create some quick summary plots of these (e.g., the
distribution of betweenness scores for all departments for one month
over 3
years).
—
Reply to this email directly or view it on GitHub
<
https://github.com/berkeley-dsc/purchasing/issues/18#issuecomment-98885549
.

--
Darius Mehri
Ph.D. Candidate, Sociology
University of California, Berkeley
—
Reply to this email directly or view it on GitHub
https://github.com/berkeley-dsc/purchasing/issues/18#issuecomment-98886646
.


Windows Audio Output (for discord) stops working

When i run my script everything is working fine as expected.
But i got a strange bug: the windows audio output for (eg.) discord will stop working as soon as i start the script.
I found the issue while i was showing my script to a friend with discord, suddenly i couldnt hear him anymore.
I was able to reproduce this everytime.
Closing the script does not fix the issue, i need to rejoin discord to fix it.
Looks like youtube audio is still working fine, but i read that also zoom has this issue: https://stackoverflow.com/questions/66251391/python-speech-recognition-library-causes-speaker-output-from-discord-or-zoom-t
I know from different situations, that discord is VERY sensitive to any changes on the audiodrivers, which often causes users need to do a rejoin.
Any idea on how to fix that? My script needs to run parallel to other tools so that is a big issue for my usecase.

fixed --> change windows audio setting of the output device, so that applications do not have only/full control over the device.
just documenting, in case someone has the same issue.


this is valid code but is it good?

@AvdLee  i find these more easy, and works, but is it good practice?

I would say it's less readable, but yeah, it could work! Honestly, would you mind creating an issue for these kind of questions? I'm closing this PR :)


updated opensll now i cant create new instances or start an instance

Bug Report
System Information

Ubuntu 16.04.3 LTS
AMP Release "TITAN" v<IP_ADDRESS>, built 10/06/2019 11:53
Which AMP release stream you're using (Mainline, Nightly or FastTrack)

I confirm:

[x] that I have searched for an existing bug report for this issue.
[ ] that I am using the latest available version of AMP.
[x] that my operating system is up-to-date.

I fear that attempting to update amp will cause even more problems then there already are.

Symptoms

What are you trying to do?
start or create a new instance
What are you expecting to happen?
an instance will be started or created
What is actually happening? (Nothing is not an acceptable answer!)
https://i.imgur.com/3EsIsOK.png a screencap of the log

Reproduction
i was having some openssl troubles, some of its files were missing so while amp was running i di
sudo apt-get purge --auto-remove openssl
sudo apt-get install openssl
then when i went back to amp and tried to start and create an instance it would not allow it to create or start an instance.

Closed due to inactivity.


Extension causes high cpu load

Issue Type: Performance
Extension Name: vscode-icons
Extension Version: 8.2.0
OS Version: Linux x64 4.15.0-46-generic
VSCode version: 1.31.1

:warning: Make sure to attach this file from your home-directory: /home/guillermo/robertohuertasm.vscode-icons-unresponsive.cpuprofile.txt :warning:
Find more details here: https://github.com/Microsoft/vscode/wiki/Explain:-extension-causes-high-cpu-load

Attach a link to the file or your issue is useless to us.


A more clear way to push data to client

Everytime a browser connects to that URL, the websocketd server will start a new instance of your process.

That's strange... Why not:
client A
var ws = new WebSocket('ws://localhost:8080/A');

ws.onmessage = function(event) {
  console.log('A got message: ' + event.data);
};

client B
var ws = new WebSocket('ws://localhost:8080/B');

ws.onmessage = function(event) {
  console.log('B got message: ' + event.data);
};

server
println("A\t"+"message contentA");
println("B\t"+"message contentB");

Then websocketd --port=8080 server client A will only log A got message: A    message contentA, client B will only log B got message: B    message contentB....I think this way is much clear...:)

It's a bit harder than just "println". Server has to read lines from clients and pass them to program that's running, program that's running has ability to see what client is talking to them using environment variables, lines that come from program go to clients regardless of timeouts... If client disconnects or timesout we need to kill program that was running for it. That's design of websocketd.
Making support for singleton programs was discussed (aka demultiplexing) in #50, #84, #95, #132; #135; you could comment on the opinions stated there.

I'll keep it open for a few days in case if I misunderstood you.

Well, I'm using WebSockets just for pushing data from server to clients.
For clients pulling data from server, I use ajax...
I know it's not informal, but it's easy to understand.


我可以用自己的數據集嗎

我想用這篇論文做我的數據集
但我現在只有正樣本
幾個異常照片還有ground truth
把它包成跟mvtec dataset 一樣
這樣子是可行的嗎
"C:\Users\user\OneDrive\桌面\Dynamic-noise-AD-master\MVTec\capsule\train\good"
"C:\Users\user\OneDrive\桌面\Dynamic-noise-AD-master\MVTec\capsule\test\good"
"C:\Users\user\OneDrive\桌面\Dynamic-noise-AD-master\MVTec\capsule\test\poke"
"C:\Users\user\OneDrive\桌面\Dynamic-noise-AD-master\MVTec\capsule\ground_truth"
mvtec跟capsule我是故意命名跟mvtec一樣的

Hi Henry,
if I understand correctly, then you want to use your own dataset and you structured it like the mvtec dataset? That should  absolutely be feasible and work. Just make sure that the config.yaml is also pointing to the correct data_dir and data name should be MVTec. Please also keep in mind that the ground_truth folder has subfolders for the defect categories e.g for your "poke" example:
C:\Users\user\OneDrive\桌面\Dynamic-noise-AD-master\MVTec\capsule\ground_truth**\poke**


fix #125 qrcode printing

This fixes the qr code voucher printing on my raspiblitz. It would be great to have it merged and moved the raspiblitz tag to. thx.

I dont know why mypy/check fails - its just CSS fixes.


move fileExists to jest-util

not sure why it fails the integration test...

@facebook-github-bot import

Closing for now as there are some plans to make fileExists in the resolver faster.


[bootstrapper] change newer version detected action

Summary of the Pull Request
What is this about:
When a newer version is detected, don't run the new version's MSI, instead show an error dialog and exit.

What is include in the PR:
Improve the error dialog logic. Add more logging.
How does someone test / validate:

Build the bootstrapper
Run the bootstrapper when there is no newer version installed -> the bootstrapper should proceed to install PowerToys
Run the bootstrapper when a newer version is installed -> the bootstrapper should show the error dialog and exit

Quality Checklist

[x] Linked issue: #9678
[ ] Communication: I've discussed this with core contributors in the issue.
[ ] Tests: Added/updated and all pass
[ ] Installer: Added/updated and all pass
[ ] Localization: All end user facing strings can be localized
[ ] Docs: Added/ updated
[ ] Binaries: Any new files are added to WXS / YML

[x] No new binaries
[ ] YML for signing for new binaries
[ ] WXS for installer for new binaries

Contributor License Agreement (CLA)
A CLA must be signed. If not, go over here and sign the CLA.

A better logger initialization will be done by https://github.com/microsoft/PowerToys/issues/9684


add payloads

How to add payloads? not accurate results for basic payloads cant show results.. thanks

i have a vulnerable test site and my payload is  i try to scan but no result and scan finish..

Hi @drown95 ,
First of all, using custom payloads are available with the --custom-payload option.
 --custom-payload string   Add custom payloads from file

e.g
$ dalfox url http://testphp.vulnweb.com/listproducts.php\?cat\=123\&artist\=123\&asdf\=ff --custom-payload ~/HAHWUL/tool/dalfox/samples/sample_custompayload.txt

And for second question, Do you have any examples? Whether the vulnerability operating in the actual browser does not appear in the tool, it occurs due to differences in cookie/header/HTTP settings (e.g. follow redirect). First of all, I think you need to figure out exactly what kind of problem it is.

Does it print in the log as Reflected?

e.g
[I] Reflected cat param => inHTML[1]   $
    48 line:  	Error: Unknown column '123DalFox' in 'where cl

Isn't it the same even after setting cookies/headers when triggering the browser?

  -H, --header string           Add custom headers
  -C, --cookie string           Add custom cookie
        --user-agent string       Add custom UserAgent
        --delay int               Milliseconds between send to same host (1000==1s)
        --follow-redirects        Following redirection
        --timeout int             Second of timeout (default 10)

oh thank you.. :)

@drown95
If you have any more questions, submit them as an issue. You're always welcome :D


What should the recommended block size be?

need to pick a few standard sizes for libraries to support, for 10K, 100K, 1M+ credentials. Will also affect the hardware demands for provers (smaller block sizes may be chosen to better support IoT devices)

Tradeoffs:

The more revocations in the block the slower the token generation for the prover is
larger block size (timing)

slower for the prover
no impact for the verifier
no impact for the issuer

larger block size (bandwidth)

smaller registry for the prover to download, but larger registry metadata (doesn't change)
no impact for verifier
not too big of an impact for issuer (maybe not true at large scale)

block size shouldn't have too big of an impact on privacy?


Cannot Use Pseudo Parameters In S3 Bucket for events

Issue:
I want to create a service that uses an S3 bucket as an event source, and I want the #{AWS::AccountId} to be in the bucket name to guarantee a unique bucket name.  However, this does not work as expected;  when trying to deploy the service, I receive an error message:
Bucket name should not contain uppercase characters.
Reproduce:
Environment Information:
  Your Environment Information ---------------------------
     Operating System:          darwin
     Node Version:              12.14.1
     Framework Version:         1.80.0
     Plugin Version:            3.8.1
     SDK Version:               2.3.1
     Components Version:        2.34.9

serverless-pseudo-parameters version: 2.5.0
serverless.yml
service: sample-bucket-project
provider:
  name: aws
  region: us-west-2
  runtime: nodejs12.x
plugins:
  - serverless-pseudo-parameters

functions:
  test:
    handler: index.handler
    events:
      - s3:
          bucket: my-events-bucket-#{AWS::AccountId}

Full command output:
$ serverless deploy
Serverless: Packaging service...
Serverless: Excluding development dependencies...

  Serverless Error ---------------------------------------

  my-events-bucket-#{AWS::AccountId} - Bucket name should not contain uppercase characters. Please check provider.s3.my-events-bucket-#{AWS::AccountId} and/or s3 events of function "test".

  Get Support --------------------------------------------
     Docs:          docs.serverless.com
     Bugs:          github.com/serverless/serverless/issues
     Issues:        forum.serverless.com

  Your Environment Information ---------------------------
     Operating System:          darwin
     Node Version:              12.14.1
     Framework Version:         1.80.0
     Plugin Version:            3.8.1
     SDK Version:               2.3.1
     Components Version:        2.34.9

Closing, as all functionalities as provided by this plugin are now covered by the Framework (since v2.50.0)


Add source : NAS

It's really an interesting project !
Is it planned to support network peripherals as a NAS for example ?
It is unfortunate to have to copy files (movies / series) a second time ...

That sounds interesting, but actually I don't know so much about NAS. How does the operating system see the storage? is it like a mounted drive? in that case it works great with it, because you can set the upload-location to anything you want that is recognizable by the system as a valid path. If it works differently, I guess I would have to implement some sort of API for this.
Regarding the copying of the files: A file-crawler is in the works, meaning in a future update of streama you will be able to configure a file-system location that will be crawled by the application. Files will be found and recognized through a naming-convention and they will be added as shows/episodes/movies automatically.

That's pretty much what you'd need for a NAS. It's typically a mountable network drive, so you'd just get a mounted folder locally present with content already in it.
Would be nice if you can set it to "store" files there too - so you can upload from anywhere to your NAS as backing store.

The ability to store there is already available today, you just need to change the storage path configured in the config.groovy. I will make this setting more accessible through the interface soon. But for now you could change the value there, make sure tomcat has read/write permissions to your target folder, and you should be good to go

The operating system see the storage as a mountable network drive.
It's could also be a FTP :)
Personally, I have a server (in a hoster) that can launch Streama.
But, my films and series are in my house on my NAS.
It'd be cool to use Streama with "external source", no ?

Oh you mean like that? Interesting.. I actually have no idea how to get something like that in place without first saving it on the server (requiring you to use bandwidth to transfer it there) and then from there uploading into the NAS.. and each time it plays a file also fetching from nas and routing through the server. But I know a guy who is really good with this kind of stuff. Maybe he has some ideas :)

@jcoifej
If your NAS can be seen by the network that your server is on, you can mount it as a directory in your file-system. Then you could set that location in config.groovy. NFS supports that out of the box and works quite well (if you have the required bandwith).
@dularion
I think it would make sense to leave NAS mounting to the filesystem. No need for an additional interface, as all popular interfaces (NFS, Samba, SSH) can be mounted easily in GNU/Linux.

Well in that case that functionally is already in place. Easier for me :)

The project is going to become really big and hard to maintain with all these supported storage types (AWS S3, Google Drive, etc)
It would be better if Streama only supported local file system. Consider that I need to include my Google Drive library. In that case I will write fuse module, that will mount the remote cloud storage into my local file system.
So Streama provides beautiful interface to display library and watch movies. Users wtire/reuse fuse modules to meet their needs.

Agreed! Sounds like a good plan!

I think @gkiko nailed it.  Most if not all external or remote storage devices can be mounted in some way. That shouldn't be Streama's problem.

Agreed, file-mounting is not a streama issue and is up to the user to mount the files locally for streama to access.


Add documentation around CustomRulePath in Settings file to README.md

PR Summary

Add documentation around CustomRulePath in Settings file to README.md

PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Change is not breaking
[x] Make sure all .cs, .ps1 and .psm1 files have the correct copyright header
[x] Make sure you've added a new test if existing tests do not effectively test the code changed and/or updated documentation
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.

This change is

@bergmeister as per request the updated docs.

Not sure why the build is failing. Looks like pipeline is broken?

Not sure why the build is failing. Looks like pipeline is broken?

It's a sporadic failure, for which I have PR #1632 to fix. I restarted the build, which worked this time.


RExecutorService - Some tasks won't get executed

The setup:
Service A -> Producing tasks to executor service
Service B -> Consuming tasks (RedissonNode)
ServiceA static, ServiceB is autoscaled in N replicas
Expected behaviour
All tasks put into executor service will get executed, tasks counter is reporting correct value.
Actual behaviour
Some tasks won't get executed, the task counter is reporting negative numbers.
Steps to reproduce or test case
I was trying hard to get a reproducer on this but I am unable to simulate it deterministically. But I tracked it down to shutdown of the redisson node.
The best that could be done for reproducing the issue is to run n replicas of RedissonNode(s) schedule hundreds of tasks to the executor service and then shut down and startup some of these RedissonNodes. If for example the task print some random id or stores it somewhere you will find out that some ids are missing even though the queue is empty (the tasks HASH is empty) and counter is having a negative value of exact number of missing tasks.
My hypothesis is that the issue is in org.redisson.executor.TasksRunnerService#executeCallable
if the RedissonInstance is in shutdown state the finally clause will still decrement the counter but as the exception is not thrown the task is not re-queued. But it is a wild guess.
Redis version
Single node non-clustered v5.0.7
Redisson version
3.12.3

Done


Convert javascript to typescript?

Is your feature request related to a new game or help the app to be better? Please describe the feature.
Check if it will be easy to use typescript instead of javascript

Should we use module?


feat: use correct builder return types for Model::newQuery* methods

[x] Added or updated tests
[ ] Documented user facing changes
[ ] Updated CHANGELOG.md

Changes
This PR adds new NewModelQueryDynamicMethodReturnTypeExtension that returns correct types for Model::newQuery* method family.
Breaking changes
n/a

I like the arrows!


Keepalive check results should honor token substitution

Expected Behavior
Token substitution syntax is honored in client keepalive attributes.
Current Behavior
Token substitution syntax is not honored in client keepalive attributes. For example, using token substitution to populate the contacts array does not result in desired values from custom client attributes.
Possible Solution
Apply object_substitute_tokens method to client.keepalive hash in create_keepalive_check
Steps to Reproduce (for bugs)

Configure a client with client.keepalive attributes using token substitution, e.g.:
{ "client": { "keepalive": { "contacts": [ ":::primary_contact|ops:::" ] }, "primary_contact": "dev" } }
Shut off the client and wait for keepalive check result
Observe that tokens not substituted in keepalive event

Context
In the case of keepalive check results, the client keepalive attributes, are merged into the top level of the check result, making it a reasonable place to use token substitution.
This customization works for standard client check results, so folks expect it to work for keepalives also.
Your Environment

Sensu version used: 1.2.1

Assigning to 1.4 milestone per @portertech

Closed by #1854


Fix CVE-2023-4262 (BDSA-2023-2642)  in zephyr >= v3.4

Need to fix CVE-2023-4262 (BDSA-2023-2642)  in zephyr <= v3.4
A similar issue has been registered under security advisories: https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-56p9-5p3v-hhrc.
Buffer overflow vulnerabilities are found at the following locations in the Zephyr Mgmt subsystem source code:
https://github.com/zephyrproject-rtos/zephyr/blob/main/subsys/mgmt/mcumgr/transport/src/smp.c
Severity level is measured as moderate (5.1) in security/advisories/GHSA-56p9-5p3v-hhrc. But in our Black Duck scan, it has been registered as Critical security risk:

Impact
This issue impacts the mcumgr security. If the unchecked inputs above are attacker-controlled and cross a security boundary, the impact of the buffer overflow vulnerabilities could range from denial of service to arbitrary code execution.
Environment:

OS: Windows
zephyr version: 3.2.0

Need to fix CVE-2023-4262 (BDSA-2023-2642) in zephyr <= v3.4

Nothing to fix, the claim is false, the size of use data comes from the network buffer which comes from the networking stack or bluetooth stack, it is not a user (remote) controlled variable. This was disputed previously and @0xdea was asked to provide a reproducable application showing which has never been provided.


Add a script to keep version numbers in sync

The version number appears in multiple places: in neo/version.py, setup.py, doc/conf.py and doc/install.rst
To simplify making releases, we should make it easier to update all these files at the same time, e.g. with a script.

I take it.

neo/version.py and setup.py are already sync
doc/conf.py is easy with import neo in conf.py. Is that OK ?
Is it OK to have a generic unzip neo-X-Y-Y.zip in doc/install.rst that it is always OK ?

For doc/install.rst, you can probably use the substituion |version|
see http://www.sphinx-doc.org/en/master/markup/inline.html#substitutions

Done in #479.
In code block it is no simple simple but with a bit of hacking in rst_epilog it is OK.
I hope this will build on readthedocs.

Build failed on readthedocs: https://readthedocs.org/projects/neo/builds/6832928/

Fixed in d9209fc52f27729e6550d6d4063ff33e819cb0dc


Ignoring a single resource

** Question : **
How do I, or is it possible to annotate a resource in some way such that it is skipped from the compliance scanning?

Hi Paul,
Currently there is no piece of code supporting this. IMHO, this could be a tough requirement, but will have a look.
No promises though 😄


Autogenerates all enum's String, removing the stringer dependency.

Minor API breaks due to naming conventions: ID -> Id and TimeStamp -> Timestamp. We can avoid that by changing the code generator, but it fells better to translate the snake_case directly to SnakeCase without handling special cases.

Removes the function doCreate, which was copying the results unnecessarily.

Closes #349
Related to #298

I think "ID" is idiomatic for Go (https://github.com/golang/go/wiki/CodeReviewComments#initialisms).


Change MusicNotationKit to MusicNotationCore in the project

Change all references to MusicNotationKit to MusicNotationCore. The only place left, I believe is in the header of each file. You can do a search/replace for // MusicNotationKit

Hello, I'd like to contribute to this project so I'm starting with something simple. #122

Fixed by #122


Add banner and logos

This PR adds a banner to the Readme file.
Logo usage

@snide I added the SVGs and removed the PNGs. I also created a markdown brand kit page.


Updated Jackson libraries to safe version + POM refactoring

Changes ::

Updated Jackson libraries to safe version
Moved dependency versions to property tag
Bumped up pom version

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.sedup4 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Create lib/domains/vn/edu/oanhvu/tmt.txt

@xueainrsnr The domain registrant for tmt.oanhvu.edu.vn is Trần Minh Thời (Tran Minh Thoi). This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@xueainrsnr Regrettably, this request has signs of fraud. I have to close it without merging.
It does not mean that something is wrong with the school. The issue is related to a combination of suspicious factors related to the domain itself.
Please enroll to GitHub Student Developer Program at https://education.github.com/discount_requests/application. Then apply for JetBrains educational subscription with your GitHub account (GitHub tab at https://www.jetbrains.com/shop/eform/students).
Thank you for your understanding!


Doesn't support npm

npm has support for workspaces, but it looks like this only considers yarn, lerna, and pnpm. Have you considered adding support for npm?

Hey @joeyfigaro, I had to fork this to support my scenarios.  I simplified the code, added npx capability, and added npm support.  Give it a try! https://github.com/alienfast/find-monorepo-root


[temp] governance: vote

from #975 to check rebase

pls update wasm

I've added a468be8 to fix the gov params loading from the genesis config

pushed back to #975 for merging


http log in html report not correct for dynamic scenario outline

#472 works as expected, but the log appender seems to be the same instance for all scenarios, and in the HTML report appears only in the last scenario or something like that. needs fixing and an opportunity to re-factor the execution-units  a little more

released 0.9.2


Use nonexistent

This PR fixes #

Nonexistent is the right word for this.

Since technically they are both correct, please keep non-existent as it is more readable variant (as I think at least).

The current code is non-existing not non-existent,
https://forum.thefreedictionary.com/postst60749_Non-existing-VS--Not-existing.aspx#:~:text=Non existing -- This is,Dinosaurs are presently nonexistent.
https://english.stackexchange.com/questions/444048/non-existing-or-nonexisting
https://english.stackexchange.com/questions/237113/nonexistent-non-existent-or-non-existent

did that already: https://github.com/microsoft/vscode/commit/dbeff882f511cc2a3427ed9370780687668590ce


PHP Parse error:  syntax error, unexpected ''

I was trying to learn more about this module and encountered an error hence this fix.

Can see no reason why this tiny fix wouldn't be accepted, suspect the maintainers just haven't had sight of it @sheadawson @JorisDebonnet @ajshort Could a maintainer be assigned to this?

I don't have write permissions, sorry! @mattclegg ?

Yeah sorry, this shouldn't have been committed to master. Can the Travis tests be enabled on this repo to catch errors like this?

@mattclegg The travis file, https://github.com/symbiote/silverstripe-memberprofiles/blob/master/.travis.yml, has PHP_CS setup.  That ought to have picked up the error

Yes you're right @gordonbanderson, but Travis currently isn't active for the repository; https://travis-ci.org/github/symbiote/silverstripe-memberprofiles

Appreciate all the input from everyone here, and the pull requests submitted to fix the issues. I've now merged https://github.com/symbiote/silverstripe-memberprofiles/pull/172 (big thanks @mattclegg), and I've made sure it's now enabled over on https://travis-ci.org/github/symbiote/silverstripe-memberprofiles. This specific problem has been resolved as part of those changes, as can be seen from the successful builds :smile:


Add Turkish language to the list

@mrtavor please add the language and push the PR. Thanks!

no problem @ux-git, one moment


Deployment instructions

I am getting errors on multiple steps of the deployment.
I had the previous framework fully deployed and I tried to run the update but it was not successful.
I then decided to just run the delete commands and cleanup commands and start fresh however it is not clear to me if I need to clone the repo or is it being pulled from Git.
I decided to clone the repo with the legacy script and then attempt the deployment from there and I received and error yet again.

I have attached a screen shot of the error.

I see the same error. (with a CID dashboard deployment).

Please read README, it covers compatibility and has usage instructions


Add Changelog v1.16.6 (#19339)

Frontport #19339
Co-authored-by: delvh<EMAIL_ADDRESS>Co-authored-by: techknowlogick<EMAIL_ADDRESS>Co-authored-by: Lunny Xiao<EMAIL_ADDRESS>Co-authored-by: zeripath<EMAIL_ADDRESS>

I should add some reminder - it hit me every time again!

Codecov Report

Merging #19450 (8edda23) into main (d242511) will decrease coverage by 0.10%.
The diff coverage is 42.79%.

:exclamation: Current head 8edda23 differs from pull request most recent head ddee1a5. Consider uploading reports for the commit ddee1a5 to get more accurate results

@@            Coverage Diff             @@
##             main   #19450      +/-   ##
==========================================
- Coverage   47.51%   47.40%   -0.11%
==========================================
  Files         944      951       +7
  Lines      131549   132333     +784
==========================================
+ Hits        62500    62738     +238
- Misses      61541    62044     +503
- Partials     7508     7551      +43

Impacted Files
Coverage Δ

cmd/dump.go
0.71% <0.00%> (-0.01%)
:arrow_down:

cmd/serv.go
2.33% <0.00%> (-0.06%)
:arrow_down:

models/action.go
48.61% <0.00%> (ø)

models/error.go
36.46% <ø> (-0.03%)
:arrow_down:

models/issue_label.go
68.02% <0.00%> (ø)

models/issue_lock.go
0.00% <0.00%> (ø)

models/issue_project.go
31.70% <0.00%> (ø)

models/organization/team_repo.go
76.19% <0.00%> (ø)

models/pull.go
55.81% <0.00%> (ø)

models/statistic.go
0.00% <0.00%> (ø)

... and 122 more

Continue to review full report at Codecov.

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


False "Symbol" is unknown import symbol

Environment data

Language Server version: 2022.10.30
OS and version: Ubuntu 22.04.1, Windows 11
Python version (& distribution if applicable, e.g. Anaconda): python3.10
"python.analysis.typeCheckingMode": "basic"
requirements.txt

Code Snippet

from django.forms.utils import RenderableFormMixin

# Duplicated django.forms.utils to ./django_forms_utils.py
from .django_forms_utils import RenderableFormMixin as LocalRenderableFormMixin

# No autocomplete
renderable_form = RenderableFormMixin()
renderable_form.render()

# Autocomplete and intellisense works
local_renderable_form = LocalRenderableFormMixin()
renderable_form.render()

Repro Steps

Create virtual environment with virtualenv
pip install django==4.1.2
Create a python module and try to import RenderableFormMixin from django.forms.utils

Expected behavior
Be able to recognize RenderableFormMixin as a class in django.forms.utils
as it does with other module members
Actual behavior
(import) RenderableFormMixin: Unknown
"RenderableFormMixin" is unknown import symbolPylance[reportGeneralTypeIssues]
But when you copy django/forms/utils.py to ./django_forms_utils.py and import
RenderableFormMixin as LocalRenderableFormMixin it works as expected.

Logs

[Info  - 4:24:15 PM] (7993) Pylance language server 2022.10.30 (pyright 50e12b4b) starting
[Info  - 4:24:15 PM] (7993) Server root directory: /home/ilir/.vscode/extensions/ms-python.vscode-pylance-2022.10.30/dist
[Info  - 4:24:15 PM] (7993) Starting service instance "test"
[Info  - 4:24:15 PM] (7993) Notebook support: LSP
[Info  - 4:24:15 PM] (7993) Interactive window support: LSP
[Info  - 4:24:16 PM] (7993) No configuration file found.
[Info  - 4:24:16 PM] (7993) No pyproject.toml file found.
[Info  - 4:24:16 PM] (7993) Setting pythonPath for service "test": "/home/ilir/Documents/test/venv/bin/python"
[Warn  - 4:24:16 PM] (7993) stubPath /home/ilir/Documents/test/typings is not a valid directory.
[Info  - 4:24:16 PM] (7993) Assuming Python version 3.10
[Info  - 4:24:16 PM] (7993) Assuming Python platform Linux
[Info  - 4:24:16 PM] (7993) Search paths for /home/ilir/Documents/test
[Info  - 4:24:16 PM] (7993)   /home/ilir/.vscode/extensions/ms-python.vscode-pylance-2022.10.30/dist/typeshed-fallback/stdlib
[Info  - 4:24:16 PM] (7993)   /home/ilir/Documents/test
[Info  - 4:24:16 PM] (7993)   /home/ilir/Documents/test/typings
[Info  - 4:24:16 PM] (7993)   /home/ilir/.vscode/extensions/ms-python.vscode-pylance-2022.10.30/dist/typeshed-fallback/stubs/...
 Because suddenly now most of django-related autocompletion and intellisense do not work.
Example: There are clearly arguments declared in DateField.__init__, but parameter info shows only (*args, **kwargs) -> None

I have done a clean reinstall of vscode and python extensions but no help.

Thank you, overriding shipped stubs with https://github.com/typeddjango/django-stubs at ${workspaceFolder}/typings brings back the functionality

We've been discussing ways to improve the django stubs situation in an internal issue: https://github.com/microsoft/pyrx/issues/4135.
At the moment this is unfortunately by design. If the bundled https://github.com/sbdchd/django-types are not working for you, you can try using https://github.com/typeddjango/django-stubs as @ikcom mentions above, which has its own downsides, but may work better in your scenario. You could also submit fixes to https://github.com/sbdchd/django-types and we'll pick them up automatically.


adding Spokane location

Adding Spokane May 20 event and RSVP info.

Awesome! I'm merging this in, I hope the event turns out great!


manifest for version 0.5.1 states it's version 0.4.9

manifest for version 0.5.1 states it's version 0.4.9

Fixed in 0.5.2


Can't add watch / + button grayed out

This is similar to 646: https://github.com/microsoft/vscode-python/issues/646 and also
https://github.com/microsoft/vscode/issues/42291
but those are closed as fixed so I figured I should report the problem, even without knowing how to reproduce it.
Environment data

VS Code version: 1.36.1
Extension version: 2019.6.24221
OS and version: Windows 10
Python version: 3.7.3
Type of virtual environment used: venv

Expected behaviour:
In the current venv, clicking "+" button in Watch header in Debug sidebar creates new watch with a field for the expression
Actual behaviour:
Watch button disappeared. Remained absent after multiple restarts of VSCode. in this venv, including after deactivating and reactivating the venv. Can still enter watches from context menu. Later, the + came back, while in the middle of a session (hadn't closed VSCode).
Steps to reproduce:
Don't know yet. Will update if it recurs while I'm paying attention.

Issue moved to microsoft/ptvsd #1655 via ZenHub


Linking against system-installed cuda and cudnn

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): No
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Debian sid
TensorFlow installed from (source or binary): source (trying)
TensorFlow version (use command below): git master (commit 9fb9ac66ce) or any version before.
Python version: 3.6
Bazel version (if compiling from source): 0.9.0
GCC/Compiler version (if compiling from source): 7.2.0
CUDA/cuDNN version: CUDA 9.0, cuDNN 6.0
GPU model and memory: GeForce GTX 1070
Exact command to reproduce:
bazel build --config=opt --config=mkl --config=cuda //tensorflow/tools/pip_package:build_pip_package

Describe the problem
The build system currently require that all the libraries from the CUDA toolkit are stored in a specific directory called cuda_toolkit_path, both in the bazel scripts and in the configure.py script. However, some systems (like Debian) have a packaged version of CUDA which installs the libraries in the standard path which cannot be found by configure.py.
The compiler can find those libraries just right with nothing more than -lcuda. It would be nice if the build system could rely on the compiler's ability to find its libraries instead of relying on the knowledge of their full path.
Source code / logs
As a feature-request / enhancement-request, this section seems irrelevant.

Hi @Celelibi ! In the current build from the source process , It asks locations of Cuda files while running the configure.py script for gpu support .Attached relevant thread for reference. Could we move this to closed status now. Thank you!


bin collisions in histogram_from_sketch possible

Summary
If a dataset profile has logged values in a relatively tight range but are large in absolute value, and there are enough bins, the bin edge calculations can hit collisions because of numeric precision on the float values used.
This affects the conversion of the profile to a summary.

mitigation in place to prevent errors due to bin width collisions, will follow up in next version to support calling a double version of the kll_sketch so we have closer to the expected precision coming from python floats.


Highlight OnDrag is Interrupted with A MarkSeries's onValueMouseOver event trigger

How can I make sure a onDrag for the Zoom-in component to not interrupted by an onValueMouseOver triggered function in a MarkSeries?
I tried to play around the ordering of the two, but if I place ZoomIn Component After MarkSeries, the onValueMouseOver won't trigger at all.
Any hint will be appreciated! thanks

A new version of the highlight component is in progress (see #939). Check out my bidirection drag chart in there for more details


Add ibm-blockchain-network to incubator charts

Source Repository:

https://github.com/IBM-Blockchain/ibm-container-service

Hello,
I have already signed a CLA with the Linux Foundation using the email address attached to my GitHub account (deallen@us.ibm.com).  I have also logged into the Linux Foundation website and verified this.  The group name is CNCF - IBM.
I do notice that the name shown there is deallen, and perhaps the issue is that this differs with my GitHub user name, eddie-at-ibm, despite my email matching on both sites.

The link to view our signed CLA is also available to me.

I have also sent an email to<EMAIL_ADDRESS>


plex: <IP_ADDRESS>4 -> <IP_ADDRESS>3

Motivation for this change
Update to latest non plex pass version.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @colemickens @forkk @lnl7 @pjones @thoughtpolice

r19.09 is at v1.16.5.xxx now. Previous updates have not been backported.
No idea if breakage is to be expected (service module or direct user).


fix: Add missing options to storage constructor

The README says:

The storage parameter defines how the contents of the drive will be stored....

name: the name of the file to be stored
opts

key: the feed key of the underlying Hypercore instance
discoveryKey: the discovery key of the underlying Hypercore instance

drive: the current Hyperdrive instance

It wasn't clear to me if opts still has the feed key and discovery key, but I pass them along here anyway. If the README is out of date, I can update it too in this PR.
This feature /could be/(?) useful if you are creating a storage adapter that needs the drive/hypertrie, like files-as-files, although I haven't gone too far down that rabbithole yet.

Old major, thanks tho!


The release application is slower than the debug version

I wrote a simple number sorting program that I run in the Flutter app. To my surprise, the debug version is much faster than the release version of the app. I have already tried generating apk versions with various flutter commands but to no effect. Could this be the cause? How to solve this problem?
I wanted to compare the performance of Flutter with React Native.
I will add that the flutter app in the release version is slower than the app in the release version in React Native which seems strange due to the fact that Flutter is compiled almost to a native language and React Native has to be interpreted. The debug version of Flutter is faster than the release version of React Native.
Please help.
flutter doctor -v
• Flutter version 2.0.3 at C:\src\flutter
• Framework revision 4d7946a68d (3 months ago), 2021-03-18 17:24:33 -0700
• Engine revision 3459eb2436
• Dart version 2.12.2
[√] Android toolchain - develop for Android devices (Android SDK version 30.0.3) • Android SDK at C:\Users\Marcin\AppData\Local\Android\Sdk • Platform android-30, build-tools 30.0.3 • ANDROID_HOME = C:\Users\Marcin\AppData\Local\Android\Sdk • ANDROID_SDK_ROOT = C:\Users\Marcin\AppData\Local\Android\Sdk • Java binary at: C:\Program Files\Java\jdk1.8.0_191\bin\java • Java version Java(TM) SE Runtime Environment (build 1.8.0_191-b12) • All Android licenses accepted.

[√] Chrome - develop for the web • Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

[!] Android Studio (not installed) • Android Studio not found; download from https://developer.android.com/studio/index.html (or visit https://flutter.dev/docs/get-started/install/windows#android-setup for detailed instructions).

[√] IntelliJ IDEA Ultimate Edition (version 2020.3) • IntelliJ at C:\Program Files\JetBrains\IntelliJ IDEA 2020.3.3 • Flutter plugin version 55.1.4 • Dart plugin version 203.7759

Do you have the source code?

Hi @bernaferrari
Can you please provide a complete reproducible minimal code sample, and complete flutter run --verbose logs running the minimal code sample?
Thank you

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


Power user problems

While most of the time CW community stays human, sometimes it so happens that users go off a bit and start becoming a pain.
New users that join are mostly the big problem, they open issues without knowing other things like :

suggestion
Question

can be opened. and some power user closes closes the issue telling them that this isn't an issue.
At this point two problems rise :

Power users tone becomes a little unfriendly (especially true for some power users) and they suggest in a less than friendly way to someone who is more than likely unaware of the system.
The new user if they are child (in general) and some really unreasonable adult start a debate which doesn't end well, since the person on the other end can trash talk equally well (in some cases even better)

The problem on general like this.
While most power users and are friendly (I like these ones 😄) e.g :

Myjinxin2015 (whom I haven't seen raise a single issue in a long time)
ZED.CWT who for the most time does an excellent job of remaining neutral and friendly

Some users are a bit of a problem , users like voile and Blind4basics who comment on a ton of kata's sometimes their comments can become less than friendly (Note for @VoileExperiments :  Please don't start yelling 😃 )
which is less than welcoming (in case of voile it ends with a down vote on every Kata (s)he will solve made by you for the next month or so (this part is from experience)
maybe enforce a stricter policy on be nice
like SO has. Although unlike SO I suggest you actually implement that, they still seem to have trouble on that end :)
Note :
Please don't be offended

I agree on the issue about some power users, especially Voile. His behavior borders on abuse, in a lot of cases.

@Paradoxial-Name @AnvShx This repo is about CW, not about any particular user. If you don't like me and want to get rid of me, go open an issue in this repo with a clear title of "ban Voile from CW", provided with clear reasons why you think banning me from CW would be better (the more detailed the better, obviously). There's no point playing hide and seek in residual issues posting snarky comments. If you want to advocate for something, be straight and honest.
Also, @Paradoxial-Name, we all know you're @Muhammad-Salman-Sheikh aka no one aka ___i. You don't need to be so roundabout just to express your grudge against me and @Blind4Basics. You're not being honest with yourself.

Just reading this... Very interesting.......

@Paradoxial-Name You mentioned two users that are making a great work for our community. I don't agree. My respect for Voile and Blind4Basics


mnbudget vote-alias

There is vote-alias in available commands but it's not available at all.
mnbudget "command"... ( "passphrase" )
Vote or show current budgets

Available commands:
  prepare            - Prepare proposal for network by signing and creating tx
  submit             - Submit proposal for network
  vote-many          - Vote on a Dash initiative
  vote-alias         - Vote on a Dash initiative
  vote               - Vote on a Dash initiative/budget
  getvotes           - Show current masternode budgets
  getinfo            - Show current masternode budgets
  show               - Show all budgets
  projection         - Show the projection of which proposals will be paid the next cycle
  check              - Scan proposals and remove invalid
  nextblock          - Get next superblock for budget system
 (code -1)

yep, that's a known one - budgets rpc will be refactored in 12.1, see #614
(vote-alias is removed there btw)

:


feat: liquidfarming module apply changed spec

Description

This PR applies updated spec version 0.3

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Appropriate labels applied
[ ] Targeted PR against correct branch
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Code follows the module structure standards.
[ ] Wrote unit and integration
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added relevant godoc comments.
[ ] Re-reviewed Files changed in the Github PR explorer
[ ] Review Codecov Report in the comment section below once CI passes

I will merge this PR and continue to update in this #332.


Add Gilt to retail.yml

While our goal is to list as many sites as possible, at the same time we can't list all sites since that would make the list enormous and unbearable to walk through.
I don't know whether this is one of those sites where there's just not enough traffic to be listed on this site.
I think we should put it to a vote.
Let's wait for some other collaborators to give their feedback.

I think Gilt is a pretty legit site. They are rather big in US. :+1:

^

@Carlgo11 any futher thoughts on this? As of 6/29/2015 Gilt is ranked 1604th globally and 654th in US according to Alexa http://www.alexa.com/siteinfo/www.gilt.com, which is higher than Comixology and Everlane in the Retail list.


crashed when use enableSwapOfCxaThrow

I found that the collected crash stack is empty, so I want to try the following method: enableswapofcxathrow.
However, when I use the enableswapofcxathrow method, I find that running on the simulator will crash.
Anyone can help me, please!

+1

I doesn't encounter that, It's normal in my code, my minimum os version is 10.


Temporarily remove @HGWright from the maintainers list

Necessary because @HGWright did not have an opportunity to accept the original invitation.
Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

The build failure would be fixed by SciTools/iris#6036, so perhaps we have to wait for the 3.10.0 release?


Adding Game of Thrones theme

Hi, I created a "Game of Thrones"-inspired theme, based on the opening titles of the show.
I also added some example code for plots using the theme in examples.R

This awesome! I will make a twitter post on this later today!


Request: Notes

Fenrus is my command center and something that is missing is some notes card where I can put some temporary notes so I don't have to open notes app.
Regards.

How do you imagine this being implemented?

A dedicated "Notes" app that you can add to a group, then it would be whatever size you configured (medium, large, larger etc).
Or, floating notes with a delete icon?
a popout panel for notes?
a dedicated page?
would you want this persistent across computers,  or would saving to localstorage so only that browser has access to it sufficient?

I'm thinking a side pane on the left that can open up, saving that to the database.  then it comes down to notes per dashboard or same notes for all dashboards....

added in dotnet version, and available in that now

Hi, @revenz that's great. I didn't expect such good solution.
Regards.


Fix a couple of issues on Windows host

Tested on Windows 7 x64 with Python 3.7.2 64-bit and GitHub Desktop environment (MSYS).
One problem is the Git version string, that contains some text and not only digits, leading to this error message:

Unable to parse Git version "2.14.1.windows.1".

The fix replaces any non-digit segment with 0.
The other problem is that the file paths contain backslashes on Windows, which are not handled correctly by Python codec. I'm not sure but there might be an issue on Linux too, if the backslash is used in some file name.
The fix first removes any backslash and process each segment separately, then joins the output putting back the backslashes.

Should be fixed in 1.20.0


Automated cherry pick of #2264: fix: qcloud storagecache bucket name too long

Cherry pick of #2264 on release/2.11.
#2264: fix: qcloud storagecache bucket name too long

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.11@61e8489). Click here to learn what that means.
The diff coverage is n/a.

@@              Coverage Diff               @@
##             release/2.11   #2265   +/-   ##
==============================================
  Coverage                ?    7.1%
==============================================
  Files                   ?     452
  Lines                   ?   71175
  Branches                ?       0
==============================================
  Hits                    ?    5057
  Misses                  ?   65701
  Partials                ?     417

Flag
Coverage Δ

#aFlag
7.1% <ø> (?)

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 61e8489...0b8a702. Read the comment docs.

/approve
/lgtm


Hide suggestions box if no matches

TASK: https://app.droptask.com/tasks/96226882-6f45-42f7-9573-8aa54a1ace84
RN PR: https://github.com/thinkproductivity/DropTask_React_Native/pull/184
Just mimics web by hiding suggestions box completely if no matches.

:+1:


chore(metrics): log Integration response metric

Provide log that allows us to see reponse time for the particular snapshot
Maintainers will complete the following section

[ ] Commit messages are descriptive enough (hints)
[ ] Code coverage from testing does not decrease and new code is covered (check the PR coverage on codecov)
[ ] Controllers diagrams are updated when PR changes controllers code  (if applicable)

Log example
{"level":"info","ts":"2024-02-01T16:41:13Z","caller":"gitops/snapshot.go:303","msg":"Integration Service Response time (integration_svc_response_seconds)","controller":"snapshot","controllerGroup":"appstudio.redhat.com","controllerKind":"Snapshot","Snapshot":{"name":"application-sample-8zjl7","namespace":"default"},"namespace":"default","name":"application-sample-8zjl7","reconcileID":"4ca4623d-e40f-4f74-8ad3-72fc84855f0c","snapshot.name":"application-sample-8zjl7","pipelinerun.name":"build-pipelinerun-np8xs","duration":4.857376633}


Fix linting issues in codebase

Resolved by https://github.com/cyberark/secretless-broker/pull/370


The updater code for telegram bot resolved

Issue that this pull request solves
Closes: #154  (issue number)
Proposed changes
Brief description of what is fixed or changed:

The Telegram Bot TOKEN entered by the user is saved in a .pkl file, that the user can opt to reuse for the next session. After this change, the user need not keep his TOKEN handy before executing the program each time.
Added telegram_token.pkl to .gitignore to avoid commiting any such TOKENs to the repository.

Types of changes
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update (Documentation content changed)
[ ] Other (please describe):

Checklist
Put an x in the boxes that apply

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings

Screenshots

Other information
Though the first message was sent correctly to the Telegram Bot, unfortunately, further online statuses were not sent when tested. I'm certain this wasn't caused by the changes proposed by this PR. I believe it has something to deal with the status file selected and it's processing, and feel it lies beyond the scope of this issue.
@rpotter12 @xandao6

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 3

Complexity increasing per file
==============================
- wplay/telegram_bot.py  4

See the complete overview on Codacy


✔Implemented Progress Scroll Indicator bar in ALL Pages!

Hey @arghadipmanna101
issue closes #1447
I Have implemented the Scroll Indicator Progress bar in ALL the existing pages in the website.
Please take look..
https://github.com/user-attachments/assets/df8a405b-fc2e-48da-a9d7-f3b09df6d2f6
Type of PR

[x] Feature enhancement

Checklist:

[x] I have performed a self-review of my code
[x] I have read and followed the Contribution Guidelines.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[x] I have commented my code, particularly in hard-to-understand areas.

Additional context:
[Include any additional information or context that might be helpful for reviewers.]

@arghadipmanna101

@arghadipmanna101

@arghadipmanna101 please take a look

@arghadipmanna101

@arghadipmanna101 Please review it


user defined types: The property "value" is not allowed on objects of type "{ }". No other properties are allowed.bicep(BCP037)

Bicep version
Bicep CLI version 0.25.53 (c0ad57dff6)
Describe the bug
The warning in the title appears only if you reference local bicep file with user defined types but it does not appear when referencing container registry for example.
To Reproduce
Steps to reproduce the behavior:
input-types.bicep
@export()
type policyAssignment = {
  @description('''The ID of the policy assignment.''')
  id: string
  @description('Display name for the policy assignment.')
  @maxLength(128)
  name: string
  @description('''The ID of the policy definition.''')
  policyDefinitionId: string
  @description('Pair of name and value to be added.')
  metadata: metadata?
  @description('''The policy definition parameters and values''')
  parameters: parametersPolicyDefinition?
}

type parametersPolicyDefinition = {
  @description('''The name of the parameter.''')
  *: {}
}

type metadata = {
  @description('The value for the metadata name.')
  *: string
}

@export()
type tagsType = {
  @description('''The tag name and value pair.''')
  *: string
}

@description('Deploys Policy Assignments for policy definitions.')
param policyAssignments policyAssignment[] = []

main.bicep
targetScope = 'subscription'

import * as inputSchema from 'input-types.bicep'

param policyAssignments inputSchema.policyAssignment[] = []

resource tenantPolicyDefinitions 'Microsoft.Authorization/policyDefinitions@2023-04-01' existing = [for (policyAssignment, i) in policyAssignments: {
  name: policyAssignment.policyDefinitionId
  scope: tenant()
}]

resource policyAssignmentsRes 'Microsoft.Authorization/policyAssignments@2023-04-01' = [for (policyAssignment, i) in policyAssignments: {
  name: policyAssignment.id
  location: deployment().location
  properties: {
    displayName: policyAssignment.name
    policyDefinitionId: tenantPolicyDefinitions[i].id
    metadata: {}
    parameters: policyAssignment.parameters
  }
}]

test.bicepparam
using 'main.bicep'

param policyAssignments = [
  {
    id: 'require-tag-one'
    name: 'Require a tag on resource groups: [tag-one]'
    policyDefinitionId: '96670d01-0a4d-4649-9c89-2d3abc0a5025'
    parameters: {
      tagName: {
        value: 'tag-one'
      }
    }
  }
  {
    id: 'require-tag-two'
    name: 'Require a tag on resource groups: [tag-two]'
    policyDefinitionId: '96670d01-0a4d-4649-9c89-2d3abc0a5025'
    parameters: {
      tagName: {
        value: 'tag-two'
      }
    }
  }
]

When referencing local file.

When referencing container registry.

Although personally I do not want that warning to appear as basically you have define the type as open object I think there should be consistency in referencing local bicep file and container registry.
Additional context
Add any other context about the problem here.

I agree on the point about consistency, but it seems like the Bicep module is exhibiting the correct behavior. There is an open type object you can use (object); {} is declaring an object type that explicitly has no properties.

ok. I will try with {} to avoid the warning as it appears in our pipeline and could be distracting when you deploy multiple policy assignments.


RN 0.60+ support and Android X

We are looking to update our project to the latest version of RN (v0.60.5) and going through the docs I could not find anything on updating this.
All I know is there are breaking changes with 0.60 in regards to Android X and I was wondering if this is in the pipeline somewhere that may be addressed?
Has anyone run into any issues with v0.60+?
Thanks

Can confirm it works with 0.60.5 version ’2.0.0-rc.0’

@quachsimon Like @pontusab said, version 2.0.0-rc0 have support for RN 0.60. Check the version documentation to install it: https://github.com/react-native-community/react-native-permissions/tree/2.0.0?files=1 🙂


install: Minimum pip version should be specified at 19.0+ for dev envs

Hello, and thanks for the great project and excellent documentation!
I just walked through the development environment setup on Ubuntu 18.04 and I ran into some issues that prevented the environment from successfully being set up when following the documented instructions. I traced it down to a version requirement in pygit2 (see https://github.com/libgit2/pygit2/issues/999#issuecomment-614691503 and https://www.pygit2.org/install.html) that pip needs to be at version 19.0+. In my case, I was using the default Ubuntu 18.04 pip version, which is woefully behind that.
In my case, I simply ran the following in my virtual environment to get things back on track:
pip install --upgrade pip

The minimum pip required version of 19.0 should likely be specified in the development environment setup document in the user guide. Optionally, the above command could be recommended to arrive at an appropriate version.

@gth828r thanks! good catch, we should mention it as a note in docs indeed
@efiop just to let you know about this, may be something should be done on the DVC end - e.g. can we require a specific pip version?

@gth828r thanks! good catch, we should mention it as a note in docs indeed
@efiop just to let you know about this, may be something should be done on the DVC end - e.g. can we require a specific pip version?

@shcheklein I don't think we can, as pip isolates itself from the env of setup.py(or requirements) when installing stuff. Let's just add a note to the docs, same as pygit2 guys. We might need to add it to the docs for regular installation after 2.0 release too.

@shcheklein I don't think we can, as pip isolates itself from the env of setup.py(or requirements) when installing stuff. Let's just add a note to the docs, same as pygit2 guys. We might need to add it to the docs for regular installation after 2.0 release too.

@efiop sounds good, thanks!

@efiop sounds good, thanks!

Added note in https://github.com/iterative/dvc.org/pull/3360. Hoping pip 19 is still the minimum?

According to the pygit2 documentation there is now some type of dependency on pip 20.3+:

This requires pip 20.3 or later, otherwise pip will try to install the source distribution, and likely fail to find a matching version of libgit2.

I tried it out, and I believe you need at least pip 20.3 on a fresh dvc dev environment install to get all of the dvc unit tests to pass.
When installing from pip 20.0.2 (default on Ubuntu 20.04), I saw a lot of red text and some warning messages at the end of the attempted pip install. The unit test summary was as follows:
18 failed, 2450 passed, 14 skipped, 2 xfailed, 3 warnings in 180.76s (0:03:00)

I then uninstalled dvc, upgraded pip to the latest (taking me to version to 22.0.4), and reinstalled dvc. The unit test summary:
2468 passed, 14 skipped, 2 xfailed, 3 warnings in 183.64s (0:03:03)

I once again uninstalled dvc, downgraded to pip 20.3, and reinstalled dvc. The unit test summary:
2468 passed, 14 skipped, 2 xfailed, 3 warnings in 207.47s (0:03:27)

Oh I missed the part about this being needed for dev envs. Updated https://github.com/iterative/dvc.org/pull/3360/files#diff-aebae5b1898c8c22e5acce05e3fa8787ed2711205cfa66ca5c92709c12c8e13b


Unreal Setup.bat (failed to download error)

Hi, I am new to CARLA and trying to install via the Windows Build. In the step where we need to install UnrealEngine, and run the Setup.bat , I get the following error.
Checking dependencies...
Updating dependencies:   0% (0/63485)...
Failed to download 'http://cdn.unrealengine.com/dependencies/UnrealEngine-12372779-e1515af26c634d2a8ade60b1afd1f065/01bb78539fc8dda386d45f9b5615f9a1e8ca5d94': The remote server returned an error: (403) Forbidden. (WebException)
This issue was later submitted on Unreal Forum due to some maintenance which they are trying to fix/or maybe is fixed
https://forums.unrealengine.com/t/upcoming-disruption-of-service-impacting-unreal-engine-users-on-github/1155880
The update was that they added was :
"To remedy the error in the builds, a new Commit.gitdeps.xml file has been attached to each release version as an asset. Please replace the existing Engine/Build/Commit.gitdeps.xml file with the new asset."
Now in order to use CARLA, do I need to simply download via: https://github.com/EpicGames/UnrealEngine/tree/4.26
or will there be any updates made to the:
git clone --depth 1 -b carla https://github.com/CarlaUnreal/UnrealEngine.git .
Thanks
Prakhar

Just saw the post on https://github.com/carla-simulator/carla/issues/6454 . Redownloading the Engine/Build/Commit.gitdeps.xml from https://github.com/EpicGames/UnrealEngine/tree/4.26/Engine/Build fixed it. :)

@pjk19942 Fixed the issue for me

Failed to download 'http://cdn.unrealengine.com/dependencies/UnrealEngine-17152897/03a48e95a11f19cb8c0c2433929369fb8ef5ab4c': The remote server returned an error: (500) Internal Server Error. (WebException)
this error is still showing even after replacing XML file


Fix informer stopper

Signed-off-by: Jorge Padilla<EMAIL_ADDRESS>Related Issue:  open-cluster-management/backlog#16864
Description of changes

When the informer failed to establish a watch, it couldn't listen to the stopper channel. It was impossible to stop a failing informer.

/retest


docs: update CHANGELOG for 2.1.2

SUMMARY
Updates CHANGELOG with 2.1.2 changes.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

Thank you @dpgaspar!


ByteArrayBuffer  cannot be resolved when compiling SDK 6.0 and API 23

I have phonegap app which in google play (compiled against SDK 5.0 and AP22).  Some of the functions fails to work on android Marshmallow.
In eclipse I have changed the compilation to  DK 6.0 and API 23. Now I get the compilation error. ByteArrayBuffer  cannot be resolved. Also using "import org.apache.http.util.ByteArrayBuffer" i get compilation error cannot be resolved. Looks like org.apache.http.util.ByteArrayBuffer has been depreciated. Will you be  fixing this issue and is there a current work around ?

Same issue, but it seams fixed when I updated to newest version.

Yeah that's been removed a while ago :+1: