Decompose VibeServerCodec

Into one for HTTP exchange, VibeHttpServerCodec, and one for WebSocket, VibeWebSocketServerCodec. If it's possible to decompose, doing that is preferred like Grizzly.

Hmm, I'm not sure the current work matches well with Netty. This will be done after asking their community for help.


[plugin-federation] compatibility with plugin-errors

When attempting to combine the plugin-federation and plugin-errors there appears to no way of applying the error handling to any entities defined with the asEntity function.
The function does not accept errors amongst the options passed in, eg:
builder.asEntity(DemoProductType, {
    key: builder.selection<{ upc: string }>('upc'),
    errors: {}, // Compilation error here because `errors` is not a property of `options`
    resolveReference: (parent, context, info) =>
        demoProducts.find((demoProduct) => demoProduct.upc === parent.upc),
});

nor can asEntity be called with a union reference if a union type for the response was created some other way, eg
const EntityQueryDemoProductResult = builder.unionType('EntityQueryDemoProductResult', {
    types: [DemoProductType, Error],
});

builder.asEntity(EntityQueryDemoProductResult, { // compiler error here becasue `asEntity` requires an `ObjectRef` not a `UnionRef`
    key: builder.selection<{ upc: string }>('upc'),
    resolveReference: (parent, context, info) =>
        demoProducts.find((demoProduct) => demoProduct.upc === parent.upc),
});

I see that I am able to add errors: {} to individual fields within the entity, but obviously that becomes hopelessly messy and impractical very quickly on any reasonably large entity and I'm sure it is not what would be intended as a way of using this.
plugin-errors works perfectly for our ordinary queries; it would be great to be able to provide the same quality to our federated consumers for error cases. Is it something you would expect we are able to do?
Thanks

Can you elaborate on what you are hoping to achieve with this?  As far as I know this would not work with federation.  resolveReferrnce and asEntity don't really define a field in your schema that could be updated to return a union.  They just help describe how to load an entity for federation.

More specifically, can you show me what the expected change in the resulting schema might look like

Thanks for your quick response to this. 👍
There's every chance that this is a misunderstanding on my part, so forgive me if I am going down the wrong path here if it's not making sense to you.
Presumably a schema along these lines is no more sensible? Below, I've basically I've changed the SDL for the _entities query that is introduced with the plugin-federation to accommodate the union with an error type. (This is just to try to illustrate what I'm getting at rather than any request to produce this schema specifically).
type BaseError implements Error {
  message: String
}

type DemoProduct {
  name: String
  price: Float
  upc: String
  weight: Float
}

interface Error {
  message: String
}

type Query {
  _entities(representations: [_Any!]!): [_Entity]!
  _service: _Service!
  topProducts(first: Int = 5): QueryTopProductsResult
}

union QueryTopProductsResult = BaseError | QueryTopProductsSuccess

type QueryTopProductsSuccess {
  data: [DemoProduct!]!
}

scalar _Any

union DemoProductEntityResult = DemoProduct | BaseError

union _Entity = DemoProductEntityResult

I guess, taking a step back from the specifics of the schema, I was thinking that when an entity is being resolved, either by a normal query or through federation, it could either return what is being requested or it could fail with an error for any reason. I would have thought that the federation case is just as likely to benefit from a deterministic response in the case of failure. But perhaps this is where my misunderstanding lies 😄

Federation is defined by a specification, and we can't just change the semantics of how things like _Entity work.  Federation schemas need to be compatible with schemas defined using things other than pothos, so this likely wouldn't work.
To go into a little more detail here, if you had a field in another schema that returns a DemoProduct, there is no way for the federation process to know that whole type needs to be replaced with a DemoProductEntityResult.
_entites would never be queried directly by a client, the only thing using that query should be your federated schema, and would only be used when trying to load a DemoProduct.  If it gets back a DemoProductEntityResult when it asks for a DemoProduct it wouldn't know how to parse that result to get the requested details for whatever other field it was resolving.

_entites would never be queried directly by a client, the only thing using that query should be your federated schema

OK - that's the part I'd missed.
Thanks again for getting back to me on this - sorry for diverting your time away from the great stuff you're doing here 👍


google Pubsub - thread_name_prefix error

Hi !
I have installed and upgraded google cloud (Im' working on Python 2.7), but whenever I try to create a SubscriberClient object, I get the following error : TypeError: init() got an unexpected keyword argument 'thread_name_prefix'
This happens on my machine but also on Google Compute engines. This error comes from the fact that the concurrent.futures.ThreadPoolExecutor class does not have a "thread_name_prefix" argument.
Do you have a solution for my error ? Can you reproduce it ? Thank you very much for your help !

Can you please provide the complete traceback?  Also, the output from pip freeze?

The release notes for google-cloud-pubsub 0.29.3 note (in the "Dependencies" section):

Upgrading google-api-core dependency to latest revision (0.1.2) since we rely on the latest version of the concurrent.futures backport to provide the thread_name_prefix argument for thread pool executor (#4521, #4559).

Please try in a fresh virtual environment, or else upgrade the dependencies in your current environment.


Eval works wrong

Please answer the following before submitting your issue:
Note: Please include any substantial examples (debug session output,
stacktraces, etc) as linked gists.

What version of Delve are you using (dlv version)?
The latest master
What version of Go are you using? (go version)?
1.9
What operating system and processor architecture are you using?
macos
What did you do?

I have a simple program
package main
func main() {
	var err error = nil
	a := err == nil
	print(a) // but breakpoint here
}

and try to evaluate err == nil
5. What did you expect to see?
true
6. What did you see instead?
false
JSON RCP log:
OUT: {"method":"RPCServer.Eval","params":[{"Scope":{"GoroutineID":1,"Frame":0},"Cfg":{"FollowPointers":true,"MaxStructFields":-1,"MaxVariableRecurse":3,"MaxStringLen":100,"MaxArrayValues":100},"Expr":"err == nil"}],"id":13}
IN: {"id":13,"result":{"Variable":{"name":"err == nil","addr":0,"onlyAddr":false,"type":"","realType":"","kind":1,"value":"false","len":0,"cap":0,"children":[],"unreadable":""}},"error":null}

The original request – https://youtrack.jetbrains.com/issue/GO-4067


Create a pull request from "develop" to "main" branch

Add title: "First release to production".
Define metadata (assignees, labels, projects).

Opened a pull request. Switched from "Todo" to "In Progress".

Added assignees, labels, milestones and linked the project than merged pull request. Switched from "In Progress" to "Done"


kubernetes, docker, CI/CD

corresponding kubernetes helm chart - https://github.com/Midburn/midburn-k8s/tree/master/charts-external/dreams#dreams-helm-sub-chart

the chart is deployed on staging environment and has continuous deployment - once you merge this PR it will work, please check the .travis.yml for the environment matrix - regarding which branch deploys to which environment
needs some more work to expose publically, add DB web UI, import data from production, test etc.. documented what needs to be done in Midburn/midburn-k8s#13

@OriHoch Can you squash the travis so we can merge this nicely?

you can squash and merge from github

@OriHoch It says that all the commits will be merged into one, I was hoping to keep the logical ones and get read of the .travis fixes.

thanks, deployment after the merge looks good
https://travis-ci.org/Midburn/Dreams/builds/339218003
this is the relevant log of the deployment to staging -
https://travis-ci.org/Midburn/Dreams/jobs/339218004#L1166


preview appearance improvement

center the page horizontally
add a background color or border to page

reported by enivex on typst discord


5 a 1

Ready for review. Hopefully, the ReadME file is easy to follow, but if it is not (likely) then please comment where so. Important the update can be ran using the ReadMe file alone.
When comparing to old data please note that this update includes a change in data source from a no-longer produced ONS survey to NOMIS data. Therefore, there are expected discrepancies.
Hopefully the QA file produces something useful!

Trying to add Ali (alicampbell2) to review this, but it won't let me. Any idea @uzzelk @ANikolova22 ?

I can't find ali on the list of possible reviewers, not sure what Fren's user name is, but I don't see her either. May be that they were not added to the repository and don't have permissions. I'll check how this is done

@ANikolova22 - Fren's username is Frensisbras


Bump build number

Just debugging with no changes which build fail.
Checklist

[ ] 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.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

The win64 fails with an error in installing the conda deps, let's try to rerender.

@conda-forge-admin, please rerender

Closing as the problem was solved in https://github.com/conda-forge/mumps-feedstock/pull/75#issuecomment-1063823075 .


Modernize the webserver code (part 2)

The commit messages contain more details about the individual changes. This second part completes the extraction of self-contained functionality from the large handler method to make it more manageable and to get rid of using variables from the outer scope, and enables the ESLint no-var rule for this file.
The first commit should be reviewed with the ?w=1 flag for an easier diff.

/botio unittest

There's one more thing I'd suggest improving here, and that's the WebServer constructor; note how the parameters are set after initialization which seems a bit backwards:

https://github.com/mozilla/pdf.js/blob/f1a225889be50ee2d00d080449bce7f2f92a4d96/gulpfile.mjs#L2070-L2073
https://github.com/mozilla/pdf.js/blob/f1a225889be50ee2d00d080449bce7f2f92a4d96/test/test.mjs#L1018-L1023

It'd be much nicer if we directly passed in necessary parameters on initialization, by writing the constructor as follows:
class WebServer {
  constructor({ root, host, port, cacheExpirationTime }) {
    this.root = root || ".";
    this.host = host || "localhost";
    this.port = port || 0;
    this.server = null;
    this.verbose = false;
    this.cacheExpirationTime = cacheExpirationTime || 0;
    this.disableRangeRequests = false;
    this.hooks = {
      GET: [crossOriginHandler],
      POST: [],
    };
  }

/botio unittest


[FLINK-28612] [FLINK-28612][runtime] SpeculativeScheduler cancels pending slot allocation after canceling pending executions

What is the purpose of the change
Canceling pending slot allocation before canceling executions will result in execution failures and pollute the logs. It will also result in an execution to be FAILED even if the execution vertex has FINISHED, which breaks the assumption of SpeculativeScheduler#isExecutionVertexPossibleToFinish().
This PR changes SpeculativeScheduler to cancel pending slot allocation after canceling pending executions.
Verifying this change

Added units test in SpeculativeSchedulerTest

Does this pull request potentially affect one of the following parts:

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

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

Thanks for reviewing! @wanglijie95
Merging.


Members middleware extraction

WIP :construction:
This changeset gets members related code out of site/app.js and cleans up how member flags are used.

@allouis would like to hear your thoughts about this approach. Have left comments in the commit messages. One other thing that left it site/app.js is members specific cache-control - https://github.com/TryGhost/Ghost/blob/9a2719a/core/server/web/site/app.js#L237-L243
Not sure if we'd want to give any control over this to the members' service? Think it's a very specific case which is fine to leave there.

@allouis have made the changes discussed above. Let me know what you think about the naming and new structure. Otherwise happy to merge after a little local spin-test :+1:


HHH-10760 Add a getter to Index to expose the columnOrderMap

@dreab8 done!

Thanks @gsmet ,
rebased and pushed on master.


feature request: when outputting png files, also output srtx file

Hey there! I use your software as part of a process to get subtitles into srt text format. It would make that process easier if you could extend your xml+png output by also (or maybe depending on a switch) output a srtx file that can be used by srttool to join together the OCRed text snippets into one srt file.
The format of this srtx file should be like so:
1
00:01:01,15 --> 00:01:02,16
eng1_0001.png.txt

2
00:01:02,18 --> 00:01:06,03
eng1_0002.png.txt

3
00:01:06,05 --> 00:01:07,07
eng1_0003.png.txt

As a workaround for now I have written myself a little java processer for your xml format that outputs this srtx format (see attachment)
BDNXmlToSrtx.java.txt

I appreciate BDSup2Sub's current capabilities and second @kaefert's request, SRTX output would be beneficial. My workaround is to export with BDSup2Sub (to get XML+PNG) and subtitle2pgm (to get the SRTX), then manipulate as necessary.
#! /bin/bash
subtitle2vobsub -p file.ps1 -o file
# Unfortunately, subtitle2pgm skips, doubles or blanks some frames.
subtitle2pgm -P -i file.ps1 -o file
# Thankfully, BDSup2Sub exports all frames correctly.
java -jar BDSup2Sub.jar -o file.xml file.idx
rename file_ file *png
sed -i 's/pgm/png/g' file.srtx
for subs in *.png; do tesseract $subs $subs; done
srttool -s -i file.srtx -o file_ready_for_editing.srt
rm file*{png,pgm,idx,xml,srtx,txt,sub}


Helm tests fail on distroless

Failure: https://gubernator.k8s.io/build/istio-prow/pr-logs/pull/istio_istio/15395/e2e-simpleTests-distroless-master/1
Logs from pods:
container_linux.go:247: starting container process caused "exec: \"sh\": executable file not found in $PATH"
Root cause: https://github.com/istio/istio/blob/f91f99e169c0a4a3ca25fc8aa678d1416d2390da/install/kubernetes/helm/istio/charts/prometheus/templates/tests/test-prometheus-connection.yaml#L24
(this happens on security test as well not just prometheus)

Fixed! Thanks https://prow.istio.io/view/gcs/istio-prow/pr-logs/pull/istio_istio/15608/e2e-simpleTests-distroless-master/3

And made to always run in https://github.com/istio/test-infra/pull/1443


Typescript support?

Is there typescript support planned?

In what sense? This should just use your existing TypeScript confguration.

My guess would be question comes from older lib.dom.d.ts and lib.webworker.d.ts only specifying one argument to Worker constructor?
https://github.com/microsoft/TypeScript/commit/40bd7c89abbdf79493e2ea20dd80d9eb657dc82e#
If I'm not mistaken, it seems to be 3.1 and earlier.

I'm going to close this one out - from what I can tell, TypeScript's dom.d.ts has supported WorkerType for at least 2 years.


Consider inverting tsc line number's fg/bg rather than setting the fg/bg colors to ensure contrast

Tested on<EMAIL_ADDRESS>Light+ in VS Code (bad):

A dark theme in VS Code (fine):

Terminal.app (fine):

Feel free to send a PR! You probably know more about PTTYs than I do at this point ;)

@DanielRosenwasser I spent a while looking for where this line number is printed but couldn't see it, I'd be happy to if you could you give me a pointer to the file where the line number is rendered?

Check out the usages of gutterStyleSequence in program.ts:
https://github.com/Microsoft/TypeScript/blob/6fb0f6818ad48bf4f685e86c03405ddc84b530ed/src/compiler/program.ts#L253

@DanielRosenwasser done 😃


Table Data tab filter expression filter results datetime column ordering improper

System information:

Operating system (distribution) and version: macOS Catalina 10.15.7
DBeaver version: Version <IP_ADDRESS>104181339
Additional extensions

Connection specification:

Database name and version: MySQL 5.7
Driver name: Whatever DBeaver prompted me to install during connect, the typical/normal/default I guess.
Do you use tunnels or proxies (SSH, SOCKS, etc)? No, it's a local database.

Describe the problem you're observing:
In the schema table's Data tab, a datetime column's results do not order properly after clicking the Sort by buttons (up or down).

Steps to reproduce, if exist:
Open the Data tab on a table, type datetime_column_name <= 'YYYY-MM-DD' in the expression filter, then order the results of the column (which would be a datetime column), then click the column's sort button for up or down (ascending or descending).
Include any warning/errors/backtraces from the logs

There are no relevant warning/errors/backtraces from the logs that I'm aware of.
Additional info:
If I instead open a new SQL tab (from the schema name right-click) then type out my own SQL, the datetimes order properly:
SELECT received_date FROM file
WHERE received_date <= '2020-05-03'
ORDER BY received_date DESC

Results ordering mode was set to Smart (Adaptive).
What was yours set to?

Mine was set to Adaptive too.
I noticed that I mixed up the labels, but after further research I'm still not able to reproduce your issue using MySQL and MariaDB drivers.

I stumbled on what the issue is...
I had another column ordered by its tab click, like this:

I wasn't aware (accidental click) or had forgotten, so it screwed with what I expected from the received_date column filter order.
Sorry about that! I was not aware that the Data tab allowed multi-column click sorting... but that's a very nice feature that I can use effectively now.

That's okay. I'm glad your issue was solved!


Linting and formatting

Thoughts on running black and isort on all files within torchaudio? I am suggesting we do so manually (and not automatically through a post-commit hook).

(+) contributors can simply run black/isort to ensure the formatting is standardized.
(-) git blame will show most files modified by the same PR (assuming the change is done in one PR)
(+) contributors were already correcting lint/formatting as part of unrelated work, and doing this may reduce the occurrences (as noticed by both @mthrok and myself).

Thoughts @cpuhrsch @mthrok?

I do not think there is an automatic way to perform formatting/linting as commit hook has to be installed manually by each user.
Also I found commit hook not helpful, because it prevents from pushing WIP, which I have no intention to format.
If you want an automatic way, you need a pusher job that does formatting and commit to master branch.

As I mention in the description, I did not mean "automatic" in the sense of post-hook commits, and I would not want that. :) I meant "automatic" in the sense of encouraging people to use black when they want. This is not possible right now just because of all the side effects that would happen.
That being said, we do check for flake8, so that is probably enough for my taste :)

I'm happy enough for now with enforcing flake8. Let's keep it as it is then :) I'm closing the issue, but feel free to re-open if you'd actually like to use black/etc applied to all files.

cc #854


trx recipients in bee to catch errors

Atm bee nodes are not catching properly outputs of errors/reverts and although we catch the revert status, we do not catch the reason. (https://github.com/ethersphere/bee/blob/08904602476619187091f826e7b12344ca2e623b/pkg/storageincentives/agent.go#L374)
An example of error on goerli, and we need to see how to do this with the bee nodes as well:
https://goerli.etherscan.io/tx/0x74a2577db1c325c41e38977aa1eb32ab03dfa17cc1fa0649e84f3d8c0f0882ee
Let's proceed with this so that we know why functions are failing.

I would give more context to this. So this was discussed here
https://github.com/ethersphere/bee/pull/4358
and there is a link to docs about custom errors from solidity with revert statement
https://docs.soliditylang.org/en/latest/control-structures.html#revert
This link also might help as it explains the basics of it.
https://soliditylang.org/blog/2021/04/21/custom-errors/
I couldn't find any golang solutions but there is JS/TS library here https://github.com/superical/ethers-decode-error
that solves this so some logic could be modeled on it.
@mrekucci @acha-bill


Processing data in models

In this pull request I updateded  model classes for all entities as shown in the ERD diagram. and created a custom methods  for models.

Hello @fobadara , this pull request for processing data in models, and I submitted for validation by mistake, thank you.

Thank you @rotimiazeez.


Support cli running from console_scripts

Is your feature request related to a problem? Please describe.

Project tree

.
├── hello
│   ├── __init__.py
│   └── main.py
├── hello.egg-info
│   ├── dependency_links.txt
│   ├── entry_points.txt
│   ├── PKG-INFO
│   ├── SOURCES.txt
│   └── top_level.txt
├── Pipfile
├── Pipfile.lock
├── requirements-dev.txt
└── setup.py

setup.py

from setuptools import setup

setup(
    name="hello",
    packages=["hello"],
    entry_points = {
        "console_scripts": [
            "myscript = hello.main:main",
        ]
    }
)

./hello/main.py

def main():
    print("Hello world!")

if __name__ == "__main__":
    main()

A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
pipenv install -e . --dev
or
pipenv run pip install -e .
hello is expected installed and executable, but so far it's not available.
I'd like hello bin can be executed from command line.
hello should be installed under ./.venv/bin/hello
May be pipenv run hello is available to the user.

hello is expected installed and executable, but so far it's not available.

No, it isn't, according to your setup.py, the executable name should be myscript and it is available with pipenv run myscript.

Thanks, it is my fault.
It's OK to run pipenv run myscript.


netlify-cms-app.js:54 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'filter')

Describe the bug
All forms working fine on local development stack but on live CMS, creating new collections throws an error and does not display any fields at all. Previous created content, shows all the fields perfectly fine. It seems it only effects the new view.
To Reproduce
I have no idea but I am getting the following error and the page stays on loading.
Using config file path: "https://luxury-marzipan-bd9173.netlify.app/admin/config.yml"
netlify-cms-app.js:54 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'filter')
at listFiles (netlify-cms-app.js:54:81030)
at async Promise.all (index 0)
at async V.processEntry (netlify-cms-app.js:34:37125)
at async netlify-cms-app.js:34:46856
const news = {
    name: "news",
    label: "News",
    label_singular: "News Article",
    description: "News collection",
    show_preview_links: true,
    folder: "site/content/news",
    path: '{{slug}}/index',
    //filter: { field: "hidden", value: false },
    summary: "{{title}} - {{day}}/{{month}}/{{year}}",
    //sortable_fields: [ 'news/categories' ],
    //media_folder: "" ,
    //public_folder: "",
    create: true,
    editor: {
        preview: false
    },
    fields: [
       // { label: "lfs", name: "lfs", widget: "hidden", default: false },
       // { label: "hasRelations", name: "hasRelations", widget: "hidden", default: true },
        //{ label: 'summary_button', name: 'summary_button', widget: 'hidden', default: "Read more" },
        {
            label: "Title",
            name: "title",
            widget: "string"
        },
        //...meta,
        //categories('news'),
        //tags('news'),
        //featureImage,
        {
            label: "Body",
            name: "body",
            widget: "markdown"
        },
        //...seo
    ],
}

When i remove  path: '{{slug}}/index' it works again. Something not quite working with path settings.

Closing as stale


Resharding

Unit test cases need to be added, will work on them next.
It's a bit of duplication from the rpc unit test cases at go/vt/vtgate/vtgateclient, but it's more of a user's view of the API than a low level RPC test.
Also need to fix python_client_test.py to have matching test cases. At least these two implementations should cover all cases. Then java, php, and C++ should follow eventually...
@aaijazi @enisoc @yaoshengzhe

LGTM


Fix issues related to ellipsis logic for recordedit inputs (foreign key, boolean, file, iframe)

For the inputs that users are not directly typing the input value (foreign key, boolean, file, iframe), we've used the ellipsis class. This way when the displayed text is longer than the available width, we would truncate the content.
But there are two issues:

[ ] When the "select some/all" row is opened, we're removing the max-width on the row so the new row can span across the entire view. But this means that the ellipsis logic will no longer truncate the content, and therefore, the "select some/all" row will be lengthier than other rows.

You can test this by going to this page. On the "Data Provider" column pick "Northwestern University and Jesse Brown VA Medical Center". Then clone the form multiple times so the horizontal scrollbar shows up. After you click on the "select some/all" toggle, you can see that the "Data Provider" row is lengthier than the other rows.

[ ] When showing the ..., we're supposed to show the full content as a tooltip. But we didn't implement it.

You can see an example of it on ResultsetTableHeader component. Since we will do this in multiple places, we should create a reusable component for this.
In other components (like RelatedTableHeader) the displayed tooltip has some conditional logic. If possible, the reusable component should be able to handle that, so we can also replace these with the new component (for the first implementation just stick with simpler use cases and then we can expand it)

@ladukaraniket If you don't have access to the page that I mentioned above, you can use the table I just added to ermestdatautils.
In this commit I added a test-table to defaults.json. So you can use the node createDefaults  for creating this (like you've been doing for array before). You can then to the recordedit page for this table and test this.

For foreign key make sure to pick the new row that I added.
For asset columns make sure you pick a file that has a long name something like a_file_w_a_very_long_name_that_will_trigger_ellipsis.txt


Fix Condition check for Reconcile InstallPlan status

Fix #3151
The Reason check for CatalogSourcesUnhealthy does not take into account that CatalogSourcesAdded may overwrite the AllCatalogSourcesHealthy reason because the number of catalog sources changed. So, depending on when reconcilliation happens relative to the catalog sources being added, the initial Reason may be either Added or Healthy.
At the end of the test, also depending on when reconcilliation happens, the new Reason may be Added or Healthy.

Both could be the same (Added or Healthy)
Or, the original could be Added and the new could be Healthy

New can't be Added after the original is Healthy because no additional catalog sources are added once the test starts.
However, the Status and Message (which is the real indicator of health) must match. And because of the possible update, don't check the timestamps.
Also:

Clean up some looping log messages
Clean up some logging added when comments were converted

These comments/logs are at the beginning of the test, and are also part of the test sequence, so they are redundant (and possibly confusing)

Description of the change:
Motivation for the change:
Architectural changes:

Testing remarks:

Reviewer Checklist

[ ] Implementation matches the proposed design, or proposal is updated to match implementation
[ ] Sufficient unit test coverage
[ ] Sufficient end-to-end test coverage
[ ] Bug fixes are accompanied by regression test(s)
[ ] e2e tests and flake fixes are accompanied evidence of flake testing, e.g. executing the test 100(0) times
[ ] tech debt/todo is accompanied by issue link(s) in comments in the surrounding code
[ ] Tests are comprehensible, e.g. Ginkgo DSL is being used appropriately
[ ] Docs updated or added to /doc
[ ] Commit messages sensible and descriptive
[ ] Tests marked as [FLAKE] are truly flaky and have an issue
[ ] Code is properly formatted

That should be including the (new) finalizer code in the merge. AFAICT, it's failing on the delete of the CSV (not on the removal of the CRBs/CRs/SA), as in the original failure.
The merge queue was also failing on unit test, so something was wonky.


adapter linkeddevices added

Please add to latest.

Please fix the adapter tests first and check outpur from https://adapter-check.iobroker.in/

@Apollon77
Adapter test ok:
https://adapter-check.iobroker.in/?q=https://github.com/Scrounger/ioBroker.linkeddevices
Travis test ok:
https://travis-ci.org/Scrounger/ioBroker.linkeddevices

Cool, thank you!


I'd like to use GitHub Student Developer's Pack to apply educational product, but got refused

I have a valid GitHub Student Developer's Pack, and this is my first time to apply for JetBrains fantastic products, but I got refused by system.
Have already tried to change my primary email of my GitHub, but seems to be not working at all.
I need someone for help, could anyone help me?
Thanks in advance.

@DevOpProgrammer I am sorry, the domain ncku.edu.tw is removed from our trusted domains list because it was abused in the past. If you are the student of this school, please enroll to GitHub Student Developer Program. Then apply for JetBrains educational subscription with your GitHub account (GitHub tab at https://www.jetbrains.com/shop/eform/students).

Please wait a minute, the point is: I can't use "GitHub Student Developer Program" to apply, The reason I open this request is  due to this reason.
PLEASE HELP!!!


outlook: fix temporary memory leak while listing events

As the whole request body is read using io.ReadAll, thus the request can be freed immediately afterwards.
Might help with https://github.com/inovex/CalendarSync/issues/180 .

good catch! 👍🏼


Added wrapper for gwt SuggestBox.

Can you throw this into the demo too please?

Yup.  In progress....

Nice, man. Thanks for the work.


UPS Hat SoC

Hi!
UPS Hat SoC is still 0% - where to look for the cause?

Solved.
batteries_count: 3  - i my case 2 baterry


[BUG Report]: Proxy docs not correct, please fix wasted hours on bad docs

Version
2.4 (Default)
Which section is the problem?
L7 (DDoS Attack Layer 7)
Please complete the following information
<Type>://<Host>:<Port>@<User=Optional>:<Password=Optional>

on this page https://github.com/MHProDev/MHDDoS/wiki/Proxy-Files

The '@' should be a ':'

https://github.com/MHProDev/PyRoxy/blob/master/PyRoxy/__init__.py#L68

What happened (Describe the bug) ?
Bad docs
Screenshots
https://i.imgur.com/wl7VRUR.jpeg
Please provide a link to a minimal reproduction of the bug
docs
Relevant log output
docs

Additional context
No response
Your code
No response

Would be nice to have an example with user/pass

Thank you


fix: opentelemetry logging configuration

Fix OpenTelemetry logging configuration
With the current version of OpenTelemetry recipe, if configuration keys for monolog main handler are being merged with monolog configuration from docker, end config for main handler contains keys not supported by OpenTelemetry monolog handler.
Updated version extracts opentelemetry monolog handler to a separate recipe, that is executed only when open-telemetry/opentelemetry-logger-monolog package is installed. Configuration is based on configuration from the docker recipe, making them compatible.

Can you fix the Filename ad the Pipeline failed. Replace - with _
Updated, thank you.


sk_buff's cb should be cleared in the entry point for both incoming and outgoing  packets at each layer.

At bridge, it is already handled in the outgoing path,
but not in the incoming path. We have seen cases where proxyarp_replied was 1
on sk_buffs coming from the WLAN driver and they were getting dropped in forwarding path.
Signed-off-by: Venkat Chimata<EMAIL_ADDRESS>

merged, Thanks !


Docs.MS Release Script - Stability Improvements

Resolves the following issues:

[x] Service not populating appropriately
[x] Extra Space breaking h1 title line of the readme
[x] Unparsable readme (aka been added to .docsettings ignore to ignore a readme) still generates a PR w/ the untouched readme.

@Azure/azure-sdk-eng

/check-enforcer override


Inconsistent errors for lack of snake_case

Errors for lack of snake_case are inconsistent.
Some suggest corrections:
 91 | ERROR   | Method name "getDelegatableMethods" in class RPBChessboardAbstractModel is not in snake case format, try "get_delegatable_methods"
    |         |     (WordPress.NamingConventions.ValidFunctionName.MethodNameInvalid)

Others do not:
  92 | ERROR   | Object property "methodIndex" is not in valid snake_case format
     |         |     (WordPress.NamingConventions.ValidVariableName.NotSnakeCaseMemberVar)
  29 | ERROR   | Member variable "methodIndex" is not in valid snake_case format.
     |         |     (WordPress.NamingConventions.ValidVariableName.MemberNotSnakeCase)
 128 | ERROR   | Variable "subPage" is not in valid snake_case format (WordPress.NamingConventions.ValidVariableName.NotSnakeCase)

The error names are inconsistently named:

ValidFunctionName.MethodNameInvalid
ValidVariableName.NotSnakeCaseMemberVar
ValidVariableName.MemberNotSnakeCase
ValidVariableName.NotSnakeCase

@paulschreiber While I appreciate the suggestion, renaming those error code would be a BC-break as all custom rulesets which reference these errorcodes would need to be adjusted.
I agree that the codes are inconsistent, this is historically grown, however, to create a BC-break just for cosmetic reasons is not something I can justify.
Suggest: close.

This isn't just cosmetic. It's both a usability problem (what does that rule mean?) and makes parsing output more difficult.
Since the project is still so early on (<0.2, << 1.0), I wouldn't expect backwards compatibility to be guaranteed.

It's both a usability problem (what does that rule mean?)

The errorcodes are not intended for human consumption, that's what the error messages are for. If you think the text of the error messages could be improved, feel free to open a PR to that effect.

and makes parsing output more difficult.

What do you mean ? How and why are you parsing the output ? And considering that's probably a usecase for less than 0.01% of the WPCS users, why should it be a concern of ours ?

Since the project is still so early on (<0.2, << 1.0),

The next release will be version 1.0.0, and while not on 1.0.0 yet, this project is and has been well-established for quite a while now and is very widely used already.

I wouldn't expect backwards compatibility to be guaranteed.

It's not, but that doesn't mean BC should be broken just because we can. There needs to be a good reason, more than just cosmetics or a one-person use-case.

The errorcodes are not intended for human consumption

Humans are consuming them. Your software is being used in ways you didn't anticipate. It would be good to account for that, especially given the cost is so low.

There needs to be a good reason, more than just cosmetics or a one-person use-case.

This isn't cosmetic.
If you don't don't do it now, you really won't want to do it after 1.0.

What, specifically will this break?

Humans are consuming them

I see no prove of that anywhere. You are talking about "parsing" the codes, so that's still machines, not humans.

What, specifically will this break?

Asked & answered already: https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/issues/1280#issuecomment-369495998

Does PHPCS support ruleset aliasing? Can you have a period where you support both the old names (flagging them as deprecated) and the new names? You can remove support for the old names after a transition period.

Does PHPCS support ruleset aliasing?

I suppose you mean sniff name aliasing ? In that case, no, it does not.

Can you have a period where you support both the old names (flagging them as deprecated) and the new names?

Not without throwing the error messages twice, so no.

I don't see anything especially problematic with issue as reported.

Error codes are often not even displayed and need to be opted in for. Even then I don't think they rise to a level of major inconsistency here.
Error messages here, that are meant for humans, seem fine.

AFAIK, we likely don't have any consistency across all of the sniff error codes, and possibly nor does PHPCS. Taking two examples:

ValidFunctionName.MethodNameInvalid
ValidVariableName.MemberNotSnakeCase

The latter is a very specific case - either it follows snake_case or it does not. The former just says it's invalid, but that doesn't specify how it's invalid.
I think before worrying about these four items are consistent, we'd need to look at all of the error codes and see if they are checking for single types of violation, or more than a single type of violation, and have that accurately reported in the error code.
If BC is going to be broken (sniff changing categories, ruleset naming etc.) then maybe this would be worth doing, but it should cover more than just the four items here, and it would need a plan and purpose of why an error code naming schema has value. A naming schema's usual benefit is guessability. The sheer inconsistency between what things the sniffs check, means I don't think one could guess what an error code would be (to exclude it, for instance), without needing to look it up anyway.

If we do want to address this issue, the moment is now (WPCS 2.0.0). Alternatively the issue should be closed. Opinions ?

PR #1612 addresses this issue. @paulschreiber It would be great if you had a chance to look the PR over this addresses your concerns sufficiently.


FormBuilder doesn't inject hidden fields on GET requests

I made this little change to prevent FormHelper to inject the csrf_token hidden field on GET requests, like search forms or button links.
Please consider to merge to master. Tks

:+1:

@rpanachi Thanks for this PR, it looks good. :+1:
There is one thing to modify: we override Object#method. This can be annoying, for debugging, can you please stick to #verb instead? Thanks.
/cc @joneslee85

@jodosha @joneslee85 Done in https://github.com/lotus/helpers/pull/40


Update cross-media-measurement-api dep for type URLs.

This change is

Depends on world-federation-of-advertisers/consent-signaling-client#47, which in turn depends on world-federation-of-advertisers/cross-media-measurement-api#185 and world-federation-of-advertisers/common-jvm#219


Add username check to doctor

Add a new breaking change detector to Gitea's doctor, which checks if all users still have a valid username according to Gitea. Given from time-to-time we need to make changes, either due to new routes or due to security, it's for a instance's admin to check if all users still have a valid username.

User with invalid username:

All users have a valid username:

This command is mentioned in our 1.17 release notes, but is only in 1.18 currently.
Does this need a backport?


[BUG] Spring application.properties azure-spring-boot-sample-keyvault-certificates uses camel case. Others use hyphens

Describe the bug
Consider sdk/spring/azure-spring-boot-samples/azure-spring-boot-sample-keyvault-certificates/src/main/resources/application.properties.  This file uses camel case for property names, while the other samples use hyphens in the same context.

Examples
            app.property("azure.activedirectory.client-id", clientId);
./azure-spring-boot-test-aad/src/test/java/com/azure/test/aad/groups/AADGroupsCountIT.java
            app.property("azure.keyvault.client-id", CLIENT_SECRET_ACCESS.clientId());
            app.property("azure.keyvault.client-id", CLIENT_SECRET_ACCESS.clientId());
./azure-spring-boot-test-keyvault/src/test/java/com/azure/test/keyvault/ActuatorIT.java

See also this related change in the end-to-end sample

Hello @mnriem  here is another question. Even with adjusting for using the hyphenated instead of camel case, I have a question about this property:
azure.keyvault.client-secret

Other places use client-key to represent this property.  For example:
KeyVaultCertificatesEnvironmentPostProcessor.java
azure.keyvault.client-id=<the client ID with access to Azure Key Vault>
azure.keyvault.client-secret=<the client secret associated wit the client ID>
azure.keyvault.client-id=<the client ID with access to Azure Key Vault>
azure.keyvault.client-secret=<the client secret associated wit the client ID>
./azure-spring-boot-starter-keyvault-certificates/README.md
        testProperties.put("azure.keyvault.client-id", "aaaa-bbbb-cccc-dddd");
./azure-spring-boot/src/test/java/com/azure/spring/keyvault/KeyVaultEnvironmentPostProcessorTest.java
#azure.keyvault.client-id=put-your-azure-client-id-here
#azure.keyvault.client-key=put-your-azure-client-key-here
./azure-spring-boot-test-application/src/main/resources/application.properties
azure.keyvault.client-id=put-your-azure-client-id-here
azure.keyvault.client-key=put-your-azure-client-key-here
azure.keyvault.client-id=put-your-azure-client-id-here
./azure-spring-boot-starter-keyvault-secrets/README.md
azure.keyvault.client-id=put-your-azure-client-id-here
azure.keyvault.client-key=put-your-azure-client-key-here
azure.keyvault.client-id=put-your-azure-client-id-here
./azure-spring-boot-starter-keyvault-secrets/javadocTemp/README.md
azure.keyvault.client-id=put-your-azure-client-id-here
azure.keyvault.client-key=put-your-azure-client-key-here
azure.keyvault.client-id=put-your-azure-client-id-here
./azure-spring-boot-starter-keyvault-secrets/sourceTemp/README.md
            app.property("azure.keyvault.client-id", CLIENT_SECRET_ACCESS.clientId());
            app.property("azure.keyvault.client-key", CLIENT_SECRET_ACCESS.clientSecret());

So might it not be better to do the same for certificates?

@jialindai wrote:
Hi Ed,
To use data binding, one simple approach is to use @ConfigurationProperties annotation, some explains can be found at:
https://www.baeldung.com/configuration-properties-in-spring-boot
https://www.baeldung.com/spring-enable-config-properties
The underlying API is data binder: https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/validation/DataBinder.html
It has one bind() API to bind PropertyValues into an object.
In general, the @ConfigurationProperties approach is preferred.
Regards,
Jialin

Hello @jialindai
Thanks for your suggestion about using @ConfigurationProperties.  Due to the layered nature of this feature, with the proprietary Spring support on top of the standard JCA KeyStore, using @ConfiurationProperties will only benefit those using the feature from Spring.  I think this is acceptable, but I want to explicitly mention it.
I am unsure if the approach you suggest of using @ConfigurationProperties is feasible. I would like @mnriem to offer his opinion.  As far as I can tell, we must continue to use system properties directly because the underlying JCA KeyStore does not know anything about Spring, as it is a proprietary non-standard technology.
If this is true, I am happy to do the little bit of coding work.
Rationale
Here is my sketch of the proposed modifications to enable the tolerance
of property names supported by @ConfigurationProperties, as described
in the Baeldung article you cited.
With these modifications, we can support Spring property declarations
that treat the following as identical.
azure.keyvault.client-id
azure.keyvault.client_id
azure.keyvault.CLIENT_ID
azure.keyvault.CLIENT-ID
azure.keyvault.clientId
azure.keyvault.clientid

The JCA entry point will still use the single preferred usage of
azure.keyvault.client-id as a system property.  They will not have the
benefit of this tolerance.
Proposed Modifications
Consider this code, in KeyVaultCertificatesEnvironmentPostProcessor.
String aadAuthenticationUrl = environment.getProperty("azure.keyvault.aad-authentication-url");
if (aadAuthenticationUrl != null) {
    systemProperties.put("azure.keyvault.aad-authentication-url", aadAuthenticationUrl);
}

I propose we use the @ConfigurationProperties mechanism to cause a
properties pojo bean, say certProperties to be made available to the
KeyVaultCertificatesEnvironmentPostProcessor and used like so:
if (null != certProperties.getAadAuthenticationUrl()) {
    systemProperties.put("azure.keyvault.aad-authentication-url", aadAuthenticationUrl);
}

with a similar usage for the other properties.
I would like comments from @jialindai  and @mnriem  on this before I proceed.

@edburns, I think above is a good idea. It makes Spring config file more flexible in property names.

@edburns Go for it. Make sure you test the variations ;)

We may want to keep both camel case and hyphen case in system properties, so that we don't break customers using our beta version.

@jialindai We can keep this closed because I am working on it now in #18273 .


Simplify document types

We currently have to make one request per document_type to find the example pages for each type.
Since https://github.com/alphagov/rummager/pull/743 we can request examples for each facet. This saves us a lot of requests when building the pages.
cc @rubenarakelyan

🎉


Allow edit functionality for choosing a user icon

In this commit, the profile pictures were integrated with the server, which allows users to select profile pictures and persist them:
ccfc9ac687139d483012aeb222e8d74343402a52


[FEATURE]:  Improve in the cart delete button

Improvement in the UI of the cart delete button which make the cart more beautiful and user friendly.
Problem Screenshot:-

Solution Screenshot:-

@codervivek5 Please assign this issue to me i want to work on it .  #GSSoc'24

@codervivek5 Hello
please assign this issue to me under GSSOC24


refactoring: Use trailing arguments directly as inputs

Still thinking about how to better indicate the trailing arguments as inputs. Not sure that this is something that argparse can do in its automatically generated help-text. (thats why i went for --inputs as option, but now with trailing arguments its nicer from a commandline perspective!).

In the Epilog, you can add some custom text.
I'll mess with the help-message generation tomorrow, because so-far that is indeed a good reason to use --input.

I think I found a nicer way now with positional argument .. you can have a look tomorrow...


Fix CI failing due to npm run lint failing in prebuild script

Describe the bug A clear and concise description of what the bug is.
Great work from @jdwilkin4 in #43! Love those new docs! I approved and merged it on mobile not realizing that the build was failing due to a formatting issue.
@jdwilkin4 or anyone else, feel free to grab this.
To fix this, from the root of the project, run npx prettier README.md --write.
To Reproduce Steps to reproduce the behavior:

Run npm run lint
A warning about forgetting to run prettier on the ReadME appears

Expected behavior A clear and concise description of what you expected to
happen.
No formatting errors when running npm run lint
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context Add any other context about the problem here.

assign it to me please.


chore: use acvm to solve bb functions when possible

Related issue(s)
(If it does not already exist, first create a GitHub issue that describes the problem this Pull Request (PR) solves before creating the PR and link it here.)
Resolves (link to issue)
Description
Summary of changes
Use ACVM instead of calling the backend for solving blackbox functions, for the bb functions which do not use barretenberg for solving (the low hanging fruits).
Checklist

[ ] I have tested the changes locally.
[ ] I have formatted the changes with Prettier and/or cargo fmt with default settings.
[ ] I have linked this PR to the issue(s) that it resolves.
[ ] I have reviewed the changes on GitHub, line by line.
[ ] I have ensured all changes are covered in the description.

Additional context
Once this PR is merged, I will remove the related solve traits from pwg so that backends do not need to implement these solvers.

This PR is still leaving dead code on the PartialWitnessGenerator trait.

Yes, the idea is to remove this in another PR when this one is merged, we will be able to remove corresponding solves in the backend safely since they will not be called after this PR is merged.

I think we could rename the PR to feat!: Solve blackbox functions in ACVM instead of backends and then remove the functions from the PWG trait in this same PR. It'd communicate to implementors accurately, as this chore would be excluded from the changelog currently.

Since we want to have small PRs, I think it makes sense to have this one which does not call the backend and implement the solve methods, but does not break anything (and so it is a chore), and then have another one which will be a feat! and will break the interface, but it will only do that. This way there is no confusion between implementing the solvers and modifying the PWG trait.

Agreed with renaming PR, I don't really see the logic in doing this in two steps. We should only have one implementation of the black box functions in use at any one time.

I don't think this PR is non-breaking. If a backend was relying on their implementation of backend.schnorr_verify but you switch it in this PR, then they are broken. If we remove the PWG functions in the same PR, it is very clear that there isn't 2 separate implementations.

If a backend was relying on their implementation of backend.schnorr_verify but you switch it in this PR, then they are broken

No they are not be broken if I switch-in this PR, the schnorr verification should work for both implementations, if not that means their implementation was already broken.

Another example would be HashToField128Security, if a backend were using a hash function other than blake2s then this would be breaking.

If a backend was not doing the correct behavior for functions like hash_to_field etc, then I think thats on them -- and us for not having a spec.
I'm impartial as to this PR being breaking, but we should not release a version without the accompanying breaking change which removes the duplicates.


Bump timeout on remote.download test

I think sometimes the tests will just fail.    That could be FS timeout.  It sucks, but these have always really been integration tests.  It may make sense to bump the timeout globally.  You'll notice it died on 2sec, we can override the global default and make it 18sec or so.

This is not really worth keeping around at this point, and can be revisited if needed.


Missing git tags

How to know which commit is which release?
Usually, people use tags for that purpose. It would be nice if you could add those tags, as for now there is only 1 tag called "v1.18" while the documentation mentions v3.2 already.

Yeah, thanks for giving me the push I needed to do this properly  :)
I added a bunch of scripts to automate this process (in /build folder) so from now on it should be tagged properly, and the releases section should contain a bunch of different downloads.

Thank you for the change.
It would be nice to have the tags of the previous versions too.


Cleanup NodeBuilder

NodeBuilder uses rawNode to apply metadata. Optional parameters location and code are not in the rest of the codebase used and removed to cleanup the NodeBuilder code.

The remaining failing tests are in the python frontend. Since we are re-writing this anyway, we are not fixing this in the old frontend, but are blocked by https://github.com/Fraunhofer-AISEC/cpg/pull/1282, which we will merge soon.


Bug 2060968: Add delay between ironic-agent restart, but restart forever

With this change, if the ironic-agent fails, it will restart forever,
until success. Adds 5 seconds between each restart attempt to avoid
spamming the system.

/cc @bfournie

/test e2e-metal-ipi-serial-ipv4

/lgtm

/test e2e-metal-ipi

/approve

we'll backport after https://github.com/openshift/image-customization-controller/pull/43

alright, I'll backport it manually


Loadable Components SSR with React Router v3

💬 Questions and Help
I've successfully set up this package with SSR and react-router v3 and it is working. However, I wanted to move away from the old require.ensure syntax and use import() so that I could dynamically load chunks the recommended way and be able to add Webpack prefetching for some of my route-based code chunks.
I'm getting an SSR error when attempting this. Please see below. Any help would be much appreciated.
Old, working code:
<Route path="/" component={App}>
  <IndexRoute
    getComponent={(nextProps, cb) =>
      require.ensure([], require =>
        cb(null, require('./HomePage/HomePage').default)
      )
    }
  />
</Route>

Attempt at using dynamic imports:
const HomePage = loadable(() => import('./HomePage/HomePage'));
<Route path="/" component={App}>
  <IndexRoute component={HomePage} />
</Route>

Error on SSR:
Warning: Failed prop type: Invalid prop `component` supplied to `IndexRoute`.

Apparently the contents of HomePage is:
{ '$$typeof': Symbol(react.forward_ref),
  render: [Function],
  preload: [Function],
  load: [Function] }

Side note: I had to add babel-plugin-dynamic-import-node to my .babelrc in order to stop my Node server complaining that import() wasn't supported. 🤷♂

Probably v3 has no idea about forwardRef, and, probably, you dont need it.
const RealHomePage = loadable(() => import('./HomePage/HomePage'));
const HomePage = (props) => <RealHomePage {...props} />;

<Route path="/" component={App}>
  <IndexRoute component={HomePage} />
</Route>

@theKashey Thanks for the tip. Whilst that fixed the error and let my page render, it seems to have caused the HomePage component to be included within the main entry bundle that Webpack creates instead of its own chunk. It used to be its own chunk when using require.ensure.

With default settings, webpack might not create a real chunk if it is, for example, too small. You can tune it in a various ways.
See:

https://webpack.js.org/configuration/optimization/#optimizationsplitchunks
https://webpack.js.org/plugins/split-chunks-plugin/

@theKashey Yeah, I had thought that too but that doesn't seem to be the case either. I tried with the minSize all the way down to 1kb without luck. Here is my webpack config..
const path = require('path');
const webpack = require('webpack');
const config = require('config');
const CleanWebpackPlugin = require('clean-webpack-plugin');
const MiniCssExtractPlugin = require('mini-css-extract-plugin');
const LoadablePlugin = require('@loadable/webpack-plugin')
const packageJson = require('./package.json');

const appName = config.get('machineTitle');

module.exports = {
  entry: {
    main: './applications/responsive/browser.js',
  },
  output: {
    path: path.resolve(__dirname, 'static'),
    publicPath: config.get('app.assetPath'),
    filename: path.join('generated', `${appName}-responsive.js`),
    chunkFilename: path.join(
      'generated',
      'chunks',
      `${appName}-[name]-${packageJson.version}.js`
    ),
  },
  plugins: [
    new LoadablePlugin(),
    new CleanWebpackPlugin(['static/generated']),
    new MiniCssExtractPlugin({
      filename: path.join('generated', `generetic.css`),
    }),
    new webpack.IgnorePlugin(/^\.\/locale$/, /moment$/),
    // Use condensed list of timezones from moment-timezone-with-data-2012-2022
    new webpack.NormalModuleReplacementPlugin(
      /moment-timezone\/data\/packed\/latest\.json/,
      path.join(__dirname, '/static/scripts/timezones.json')
    ),
    new webpack.HotModuleReplacementPlugin(),
  ],
  module: {
    rules: [
      {
        test: /\.js$/,
        exclude: [/node_modules/, /NBCD_AppMeasurement/],
        use: {
          loader: 'babel-loader',
          options: {
            cacheDirectory: true,
          },
        },
      },
      {
        test: /\.css$/,
        use: [MiniCssExtractPlugin.loader, 'css-loader', 'postcss-loader'],
      },
      {
        test: /\.(woff|woff2|ttf|svg)$/,
        exclude: [/images/],
        use: [
          {
            loader: 'file-loader',
            options: {
              name: '[name].[ext]',
              outputPath: 'generated/fonts/',
            },
          },
        ],
      },
      {
        test: /\.(gif|png|jpe?g|svg)$/i,
        exclude: [/fonts/],
        use: [
          {
            loader: 'url-loader',
            options: {
              limit: 2000,
              outputPath: 'generated/images/',
            },
          },
          'image-webpack-loader',
        ],
      },
    ],
  },
  resolve: {
    alias: {
      config: path.join(__dirname, '/webpack-alias/config.js'),
      'park-logger': path.join(__dirname, '/webpack-alias/park-logger.js'),
    },
  },
  optimization: {
    splitChunks: {
      minSize: 1000,
    },
  },
};

splitChunks: {
      chunks: 'all',
},

@theKashey That did cause a different chunking strategy, with node_modules going into a vendors chunk but it still kept the HomePage within the initial entry bundle. 🤔
I tried bumping maxInitialRequests and maxAsyncRequests to make sure it wasn't that too. No luck.

So it turns out that having babel-plugin-dynamic-import-node in my .babelrc was causing the issue. I removed it from there, and instead made sure it only ran as part of my SSR build, e.g:
require('@babel/register')({
  plugins: [
    'dynamic-import-node'
  ]
});

Yay 🎆

JFYI: A new babel (7.4?) was released today, with a "proper" dynamic import support.

@theKashey Amazing, thanks for the heads up.
https://babeljs.io/blog/2019/07/03/7.5.0


Problem Matcher Annotations are not de-duplicated

Blocked on https://github.com/actions/runner/issues/504
https://github.com/actions/runner/issues/504#issuecomment-647903579
/remind me To check if 504 is resolved in 1 week

Closed https://github.com/actions/runner/issues/504#issuecomment-649057776


Add daemon for jewel

I have an experimental working version for jewel at https://github.com/ivotron/ceph-docker/tree/jewel . I've only tested this as a mon, osd and mds. This has only one commit https://github.com/ivotron/ceph-docker/commit/b072724935e23ad90ad56155cd250a6dc9de0d9c

I have an experimental working version for jewel at https://github.com/ivotron/ceph-docker/tree/jewel . I've only tested this as a mon, osd and mds

Neat! Would you mind pushing a PR for this?

Should this be against master or a new jewel branch?
On Sun, May 1, 2016 at 6:53 AM Leseb<EMAIL_ADDRESS>wrote:

Neat! Would you mind pushing a PR for this?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/ceph/ceph-docker/issues/254#issuecomment-216043291

New jewel branch please

@leseb Oops, sorry, I can't push a new branch. Can you please create one and then I open a pull request against it? Or can I request a pull against master and then you merge it as a new jewel one? I've never done that, not sure if github has that feature

I see, I will do that tomorrow. I don't have my laptop with me at the moment.

@ivotron done!

fixed by #255


update to latest lib version

github.com/Azure/azure-storage-blob-go/2016-05-31/azblob is outdated

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

ID: 3402293d-ac39-abd4-55ae-a3fc55180883
Version Independent ID: 832abbb0-5588-fadc-b413-4ad3f2a870bc
Content: Azure Quickstart - Create a blob in object storage using Go
Content Source: articles/storage/blobs/storage-quickstart-blobs-go.md
Service: storage
GitHub Login: @seguler
Microsoft Alias: seguler

@ben-st Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.
@seguler link seems to be not working: https://godoc.org/github.com/Azure/azure-storage-blob-go/2016-05-31/azblob

Fixed! Thanks for raising this.
#please-close

@ben-st We will now proceed to close this thread. If there are further questions regarding this matter, please respond here and @YutongTie-MSFT and we will gladly continue the discussion.

The URL on the repo of the example has not been updated yet. @seguler @ben-st


Refactor poetry tilde caret operators remove semver

Description
Refactor poetry tilde ~ and caret ^ operators to make them work with a PEP 440 version. Remove
Close #534 by @jan-janssen
Close  #593
I've removed the dependency semver because it is not used anymore and updated the pixi.lock file. The version of the lock file is unfortunately higher than the one currently on main, therefore there are a lot of differences just to adapt to the new format. I could not find a way to produce an older version of the file lock. Probably installing the same version of pixi would work. Let me know if this is relevant or we can update the version as it is.

in regards of the pixi.lock, that is alright, thanks for updating it!
The PR looks good to me, thanks again for your contribution! :)


Enable single-precision state files

Currently double-precision forecast and analysis files are used across all cycles, which is quite expensive as we move toward higher resolution and more ensemble members.
It is OK to keep read double-precision first-guess and initial condition files in the first cycle as we have now, although the precision of the first cycle and the ensemble B files should be configurable in case they are only available in single-precision.
Besides the first cycle reading, make the precision of written (forecast/analysis) and read (first-guess, initial condition, and ensemble B) files configurable.  For EDA cycling, the precision of the ensemble B after the first cycle will be the same as the forecast files, but not necessarily in the first cycle.
D = double-precision
S = single-precision
3denvar
Currently:
FirstCycleBackground (D)
=(variational)=> FirstCycleAnalysis (D)
=(forecast)=> FirstCycleForecast/SecondCycleBackground(D)
=(variational)=> SecondCycleAnalysis (D)
...
All cycles use GEFS cold-start forecasts: EnsForCov (D)
OR
All cycles use previous MPAS-JEDI EDA forecasts (D)
Fix in this issue:
FirstCycleBackground (D)
=(variational)=> FirstCycleAnalysis (D)
=(forecast)=> FirstCycleForecast/SecondCycleBackground(S)
=(variational)=> SecondCycleAnalysis (S) ...
...
All cycles use GEFS cold-start forecasts: EnsForCov (D)
OR
All cycles use previous MPAS-JEDI EDA forecasts (S)
eda_3denvar
Currently:
FirstCycleBackgroundEnsemble (D)
=(variational)=> FirstCycleAnalysisEnsemble (D)
=(forecast)=> FirstCycleForecastEnsemble/SecondCycleBackgroundEnsemble(D)
=(variational)=> SecondCycleAnalysisEnsemble (D)
...
First cycle uses GEFS cold-start forecasts: EnsForCov (D)
OR
Second and subsequent cycles use previous MPAS-JEDI EDA forecasts (D)
Fix in this issue:
FirstCycleBackgroundEnsemble (D)
=(variational)=> FirstCycleAnalysisEnsemble (D)
=(forecast)=> FirstCycleForecastEnsemble/SecondCycleBackgroundEnsemble(S)
=(variational)=> SecondCycleAnalysisEnsemble (S)
...
First cycle uses GEFS cold-start forecasts: EnsForCov (D)
OR
Second and subsequent cycles use previous MPAS-JEDI EDA forecasts (S)
The precision of the input/output streams can be set in streams.atmosphere for each application using the precision stream key (i.e., https://www2.mmm.ucar.edu/projects/mpas/mpas_atmosphere_users_guide_7.0.pdf).
For example,
<immutable_stream name="da_state"
                  type="output"
                  precision="single"
                  clobber_mode="truncate"
                  filename_template="mpasout.$Y-$M-$D_$h.$m.$s.nc"
                  io_type="pnetcdf,cdf5"
                  output_interval="0_06:00:00" />

<stream name="background"
        type="input;output"
        precision="single"
        io_type="pnetcdf,cdf5"
        filename_template="background.nc"
        input_interval="none"
        output_interval="none"
        clobber_mode="overwrite">
        <file name="stream_list.atmosphere.background"/>
</stream>

<stream name="analysis"
        type="output"
        precision="single"
        io_type="pnetcdf,cdf5"
        filename_template="analysis.nc"
        output_interval="none"
        clobber_mode="overwrite">
        <file name="stream_list.atmosphere.analysis"/>
</stream>

<stream name="ensemble"
        type="input;output"
        precision="single"
        io_type="pnetcdf,cdf5"
        filename_template="ensemble.nc"
        input_interval="none"
        output_interval="none"
        clobber_mode="overwrite">
        <file name="stream_list.atmosphere.ensemble"/>
</stream>

The main challenge of this issue is to set the precision correctly for each combination of workflow application (variational, forecast, hofx, and rtpp), stream name (da_state, background, analysis, ensemble, control), and cycle (generally, first or after the first).

My suggestion is to NOT link an output file to bg file and set clobber_mode="replace_files", then setting precision="single" in all stream should be able to still read double-precision input and have single-precision output.

My suggestion is to NOT link an output file to bg file and set clobber_mode="replace_files", then setting precision="single" in all stream should be able to still read double-precision input and have single-precision output.

That is interesting.  I did not know that one could still read double-precision when precision="single".  Thank you for that very useful piece of info.  For my own record, I'm going to make the solution a little more verbose, but basically just reiterating what @jamiebresch is suggesting in the following.
Previously the bg file was different from the forecast file, because cldfrac needed to be appended before mpasjedi_variational.  Now we include cldfrac in the forecast file via the da_state stream.  As long as the first cycle backgrounds (including EDA members) also include cldfrac, we can have the bg file link to the forecast output (mpasout) and copy (instead of link) the bg file to the an file before mpasjedi_variational.  The copying of bg to an is consistent with our current approach to ensure we have a full IC file for the following forecast without writing all of the fields required by the forecast from the DA application.  We only write the fields associated with the analysis stream as described in https://github.com/JCSDA-internal/mpas-jedi/pull/647.
One edge case that may still need a unique precision solution is the reading of SST and XICE variables.  Ideally we would read those through a separate stream instead of overwriting the values already in the forecast output files.


Huawei T1-821L tablet is not working with the newest release

Describe the bug
With the newest release, the wallpanel only shows the header for a home assistant/tileboard instance (see screenshot below).
To Reproduce
N/A
Expected behavior
I pulled the latest legacy update (v0.8.4-beta.7) and now it has the same issues as when I try with the non-legacy version. I was expecting to have the updates.
Screenshots
https://www.dropbox.com/s/zabl19jfbfn1ng1/wallpanel_screen.jpeg?dl=0
Smartphone (please complete the following information):

Device: Huawei T1-821L tablet
OS: Android 4.4.4
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
It was working flawlessly with one of the previous releases. I tried to find earlier version apk files but couldn't. Thanks in advance!

Nothing has changed in the way web pages are rendered.  The application uses Googles WebView component which is solely responsible for rendering the web page.  The version of this component is based on your devices OS version.   What probably happened is that the page was refreshed after the update and changes that were recently made changed the rendering of the page.  There is nothing I can offer to fix the situation since it’s a compatibility issue with the page and Googles WebView component.

Thanks, @thanksmister for the explanation! I'll investigate on my end what could have caused this. Cheers to your good work!


Migrate code base to use "github.com/stretchr/testify/assert"

Currently there are parts of the code base that still use the pattern
if <some property> != <expected property> {
  t.Fatalf("...")
}

Migrate these instances to use
assert.* in place of this pattern.

It doesn't need to be done all at once, PRs doing it partially are helpful.

Hi, @ccaraman @pjanotti , I'd like to try working on this issue. If no one has taken it, please assign it to me. Thanks.

@huikang assigned to you, thank you.

@huikang Let us know if you have any questions!


remove string casting to int

@solarkennedy now that we have merged https://github.com/solarkennedy/puppet-consul/pull/156 we can remove all this string casting business :smile:

Ah. So great :)


[Regression] - V1 - Contributor Console - Company Not In List? Click Here button is displayed on the top and X(close) icon is not displayed

Prerequisite

Create CLA Group with CCLA enabled
Connfigure githuborg and add repo to the CLA Group
In corporate console sign cla for the CLA Group

Steps to follow

Login to github repo as contributor
Edit file and create PR
User is gated by CLA
Click on CLA NOT SIGNED
Click Corporate
Observed that Company Not In List? Click Here button is displayed on the top and X(close) icon is not displayed in the popup

Verified that the issue is fixed


monitorContainerExit is just a huge go routine

The function monitorContainerExit is just a huge anonymous function that gets called asynchronously:
https://github.com/docker-slim/docker-slim/blob/d6220ea5f2b91ee44e557a75a4123a246da2d13e/pkg/app/master/container/execution.go#L412
This is quite confusing from an API/usage perspective, as this function stays running in the background. I would suggest to refactor it a little bit, so that itself has to be called via go monitorContainerExit making the asynchronous nature more obvious.

finally :) https://github.com/slimtoolkit/slim/commit/502a2e34109d6e39647eaa4f8a4320cdb2186c09


Set up CI/CD pipelines for automated testing and deployment

Configure CI/CD pipelines to automate the testing and deployment process
Use GitHub Actions to setup workflows that run tests and deploy the application automatically upon successful builds

I found that we can use github actions for this issue


PP-8804 Stripe setup: Add controller for director

WHAT

Added new controller (GET) for director page
Unit and cypress test for new page
Updated routes, paths and navigation for director page

Thanks @stephencdaly. Good spots! Didn't realise email has different width. Will update it in next PR and also the order


English version

Could we get an english version? Thanks.

No problem, It's actually translated from http://www.catb.org/~esr/faqs/smart-questions.html


vscode: 1.22.1 -> 1.22.2

Motivation for this change
Wanted latest vscode.
Things done
Incremented version and updated hashes.
Extra
This is my first commit to this project, let me know if I botched anything

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-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 nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build vscode

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: vscode
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.

No attempt on x86_64-linux (full log)
The following builds were skipped because they don't evaluate on x86_64-linux: vscode
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: vscode
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.


Add support for create metadata added on initial import

What does this PR do and why?
Provide a description of what this PR does. Link to any relevant GitHub issues, Notion tasks or Discord discussions.
Screenshots or screen recordings
If applicable, provide screenshots or screen recordings to demonstrate the changes.
Acceptance checklist

[ ] I have evaluated the Approval Guidelines for this PR.
[ ] I have tested this PR in all supported browsers.
[ ] I have tested this PR in dark mode and light mode (if applicable).

Current dependencies on/for this PR:

main

PR #2587

PR #2565

PR #2588   👈

This comment was auto-generated by Graphite.

Graphite Merge Job
Current status: ⏳ Queued to merge
This pull request is currently queued to be merged as part of a stack.
This comment was auto-generated by Graphite.

Job Reference: KTjpsSDz0BFJe3qmHJyZ

Graphite Merge Job
Current status: ⏳ Queued to merge
This pull request is currently queued to be merged as part of a stack.
This comment was auto-generated by Graphite.

Job Reference: P70qfCBH4OQiNOT7PvLg


BAU - Slack changed the link

Thanks @yahoopete for spotting this!

It's here too... https://github.com/alphagov/pay-product-page/blob/master/source/features.html.erb


Fix and test perlcritic plugins

This adds proper unit tests to our perlcritic plugins and fixes some of them.
It also adds the OpenQA namespace to the plugin names.
I ran it on openQA and os-autoinst now.
For RedundantStrictWarning we will need a couple of ## no critic comments. there's no way to disable a plugin from the config file apparently. Reducing the severity will still exit with non-zero.
Issue: https://progress.opensuse.org/issues/155188

https://progress.opensuse.org/issues/155188

I was too late. But if you dont mind take a look on my comments


Features rework

Massively re-worked the connections page:

re-wrote for conciseness
Added the "Import SSH config" section
Added a screenshot
shortened the tooltip
added link to waveshell in GitHub

Re-worked the history page:

re-wrote for conciseness
Separated out into both ways to use history (ctrl + r and cmd + h)
Added screenshots for history

Re-organized sidebar (dropped SSH Import as it's now in connections)

Closing because deploy didn't trigger...grr


Kale enabled kubeflow pipeline giving error during execution

jupyterlab==2.3.2
kubeflow-kale==0.7.0
K8s = v1.19.3
The very first pipeline component's pod is giving the following error:
Error: error while running "VolumeBinding" prebind plugin for pod "fraud-detection-ssfbx-3356273866": Failed to bind volumes: provisioning failed for PVC "fraud-detection-ssfbx-kale-marshal-pvc"

any fixes for above issue?

i have the same issue...

any fixes for above issue?

The problem is likely the storage class you are using, when you run:
kubectl -n  describe pvc  you can see details on the problem. In my case it was this:
Failed to provision volume with StorageClass "gp2": invalid AccessModes [ReadWriteMany]: only AccessModes [ReadWriteOnce] are supported
So I guess you either have to change the accessmode or the storageclass, havent figured this part out yet ;)


Run standalone tests on travis

Also moved cluster test to standalone so hooks can be run in the same mocha invocation as unit tests.

LGTM.

Switched over to $(npm bin)/mocha


error: invalid request

This problem started today.
I'll upload an image, check the captcha, and then when I hit convert I'm led to an image that states "Error: Invalid Request" with a link to waifu2x beneath it. I can repeatedly clear the captcha until it finally gives me the image I'm trying to convert, but it takes anywhere from three to seven tries to get my image instead of the error.

Fixed. waifu2x.udp.jp is running on two api servers, but one of them had a problem.


JIRA_PKey matching query does not exist.

Please use the following template when submitting issues:
Issue Template
Issue Type

[ x] Bug
[ ] Enhancement

Description
JIRA_PKey matching query does not exist. is occurring again  See
This is occurring -> https://github.com/DefectDojo/django-DefectDojo/issues/276
If the issue is a bug, please also include the following:
Operating System
Please include the version number (ex: Ubuntu 16.04)
Centos 7.4
Install

[ x] setup.bash
[ ] docker

DefectDojo Version
Latest Pull from master (Plus addition of postfixcentos2 and (new) trustwave parser attempt.  Did not touch jira areas.
Steps to Reproduce
Enable (but don't configure jira).  open issue.  Uncheck jira . Try to close via review workflow.
Sample Scan File (if applicable)
Screenshots (optional)
Console Logs (optional)
Environment:
Request Method: POST
Request URL: https://dojo.security.qa.ops.brightcove.com/finding/1415/defect_review
Django Version: 1.11.11
Python Version: 2.7.5
Installed Applications:
('django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.sessions',
'django.contrib.sites',
'django.contrib.messages',
'django.contrib.staticfiles',
'polymorphic',
'overextends',
'django.contrib.admin',
'django.contrib.humanize',
'gunicorn',
'tastypie',
'auditlog',
'dojo',
'tastypie_swagger',
'watson',
'tagging',
'custom_field',
'imagekit',
'multiselectfield')
Installed Middleware:
('django.middleware.common.CommonMiddleware',
'django.contrib.sessions.middleware.SessionMiddleware',
'django.middleware.csrf.CsrfViewMiddleware',
'django.contrib.auth.middleware.AuthenticationMiddleware',
'django.contrib.messages.middleware.MessageMiddleware',
'django.middleware.clickjacking.XFrameOptionsMiddleware',
'dojo.middleware.LoginRequiredMiddleware',
'dojo.middleware.TimezoneMiddleware')
Traceback:
File "/usr/local/brightcove/dojo/lib/python2.7/site-packages/django/core/handlers/exception.py" in inner
41.             response = get_response(request)
File "/usr/local/brightcove/dojo/lib/python2.7/site-packages/django/core/handlers/base.py" in _legacy_get_response
249.             response = self._get_response(request)
File "/usr/local/brightcove/dojo/lib/python2.7/site-packages/django/core/handlers/base.py" in _get_response
187.                 response = self.process_exception_by_middleware(e, request)
File "/usr/local/brightcove/dojo/lib/python2.7/site-packages/django/core/handlers/base.py" in _get_response
185.                 response = wrapped_callback(request, *callback_args, **callback_kwargs)
File "/usr/local/brightcove/dojo/lib/python2.7/site-packages/django/contrib/auth/decorators.py" in _wrapped_view
23.                 return view_func(request, *args, **kwargs)
File "./dojo/finding/views.py" in defect_finding_review
271.                 jira = get_jira_connection(finding)
File "./dojo/utils.py" in get_jira_connection
681.     jpkey = JIRA_PKey.objects.get(product=prod)
File "/usr/local/brightcove/dojo/lib/python2.7/site-packages/django/db/models/manager.py" in manager_method
85.                 return getattr(self.get_queryset(), name)(*args, **kwargs)
File "/usr/local/brightcove/dojo/lib/python2.7/site-packages/django/db/models/query.py" in get
380.                 self.model._meta.object_name
Exception Type: DoesNotExist at /finding/1415/defect_review
Exception Value: JIRA_PKey matching query does not exist.

Fixed in the upcoming 1.4 release. @eik18 will you be able to share the trustwave parser?

Yes. Just debugging a bit. Was also waiting to rebase against new master.
On Tue, Jun 19, 2018 at 7:22 AM Aaron Weaver<EMAIL_ADDRESS>wrote:

Closed #614 https://github.com/DefectDojo/django-DefectDojo/issues/614.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/DefectDojo/django-DefectDojo/issues/614#event-1688361063,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGo2qg3yt7HIddp7G2-wXNi5eLJ9cYaNks5t-N7kgaJpZM4UgsVK
.

Hey Aaron. Just pushed it. Sorry for the two accounts. One is my work one,
one is my personal one.
On Tue, Jun 19, 2018 at 9:21 AM Eric Kelson<EMAIL_ADDRESS>wrote:

Yes. Just debugging a bit. Was also waiting to rebase against new master.
On Tue, Jun 19, 2018 at 7:22 AM Aaron Weaver<EMAIL_ADDRESS>wrote:

Closed #614 https://github.com/DefectDojo/django-DefectDojo/issues/614.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/DefectDojo/django-DefectDojo/issues/614#event-1688361063,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGo2qg3yt7HIddp7G2-wXNi5eLJ9cYaNks5t-N7kgaJpZM4UgsVK
.

Hi @aaronweaver , I think this is a duplicated of "JIRA_Issue matching query does not exist." It's probably a misconfiguration issue.


OTC Editing Values

Several state PHD's want the ability to add default values to fields for OTC records to improve processing.
fysa: @jlusds @Adrian-Brewster

Added a task to the epic!

no more open tickets.... closing this


Issues from gradle/gradle

I discovered this new repository dedicated to the native side of Gradle. Below 3 links to the issues I posted

[x] native: changing the parentDir of a sharedLibraryLinkFile is not honored if different from the parentDir of the sharedLibraryFile
[x] native: add a Locale dimension replacing the Flavor used to specify the locale
[x] native: add SharedLibraryBinary properties for the Export file & the Program Debugging file

Thanks @zosrothko for the reminder, the native team taking care of this board also subscribes to the gradle/gradle board. In the future, you don't need to aggregate the issue here.


Can't use the new performance.reactNativeStartupTiming

Description
Thank you for keep improving RN.
im trying to use the new performance.reactNativeStartupTiming
which in https://github.com/facebook/react-native/commit/c1023c73b010245f2e8182b75cc3bccd112d5e2e
it says 'This diff adds the performance.reactNativeStartupTiming API to the performance global object for RN.'
so when i try to log the global.performance object it just gives me one function {"now": [Function anonymous]}.
there something wrong or the feature is not completed yet?
React Native Version
0.72.3
Output of npx react-native info
System:
OS: Windows 10 10.0.22621
CPU: "(12) x64 AMD Ryzen 5 5600X 6-Core Processor             "
Memory: 2.41 GB / 15.94 GB
Binaries:
Node:
version: 18.12.1
path: C:\Program Files\nodejs\node.EXE
Yarn:
version: 1.22.19
path: ~\AppData\Roaming\npm\yarn.CMD
npm:
version: 8.19.2
path: C:\Program Files\nodejs\npm.CMD
Watchman: Not Found
SDKs:
Android SDK: Not Found
Windows SDK: Not Found
IDEs:
Android Studio: AI-212.5712.43.2112.8609683
Visual Studio:
- 16.11.32510.428 (Visual Studio Community 2019)
wanted: 0.72.2
react-native-windows: Not Found
npmGlobalPackages:
"react-native": Not Found
Android:
hermesEnabled: true
newArchEnabled: false
iOS:
hermesEnabled: Not found
newArchEnabled: Not found
Steps to reproduce
write console.log(global.performance); in App.tsx
Snack, code example, screenshot, or link to a repository
https://github.com/saif-o99/Awesome-project

Same, would be nice if this API is a bit more documented.

Not working indeed... it is like it is not loading...

No news here?

No news here?

Not for me. I just gave up on it

It got renamed from performance.reactNativeStartupTiming to performance.rnStartupTiming and it is still private as mentioned here.


Feature/Banner component

Naming Rules
Name your PR like this: ISSUENUMBER-TITLE-YOURNAME
Description
Write a summary of your change. Explain why you have made it.
Related to
Make sure you include the issue number with a hash sign # so Github can link this PR to the right issue, like this:
Fixes #1
Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have carefully reviewed my own code
[ ] I have commented my code
[ ] I have updated any documentation

section {
display: grid;
justify-content: center;
align-content: center;
}
you can use this code to place the text in center.


HSEARCH-2258 Normalized names conflict

https://hibernate.atlassian.net/browse/HSEARCH-2258

Updated and rebased

Jenkins, test this please

Rebased and merged. Thanks!


[Feature] Add InternalServerWrapper to dist

This PR adds the InternalServerWrapper to the normal dist folder, so that it gets exposed in UNPKG as well

@brapoprod as we chatted, I made a pull request to your branch - see #5
Merge into this, and then I will merge this into main.


Noobaa command to list bucket/account giving trimmed output in pipe

Environment info

NooBaa Version: 5.15.0/1/2/3
Platform: other: RHEL9

Actual behavior

Bucket/account details output getting trimmed when using with pipe

Expected behavior

it should give full output in pipe

Steps to reproduce

More information - Screenshots / Logs / Other output

@madhuthorat could you attach the command you are running and the output ? thanks

Hi @romayalon We are trying to read all the noobaa-cli output through the PIPE.   but after receiveing few bytes, the returned output is 0 and EOF. That means full output is coming through pipe.
},
{
"_id": "6656d6d3585e0a1deb367e9b",
"name": "bucket-bmw",
"owner_account": "6656d6bcf4781cd093acb9e5",
"system_owner": "account-bmw",
"bucket_owner": "account-bmw",
"versioning": "DISABLED",
"creation_date": "2024-05-29T07:18:43.986Z",
"path": "/mnt/gpfs0/account-bmw/bucket-bmw",
"should_create_underlying_storage": false,
"fs_backend": "GPFS"
},
{
"_id": "6656d6d3585e0a1deb367e9b",
"name": "bucket-bmw",
"owner_account": "6656d6bcf4781cd093acb9e5",
"system_owner": "accou
bytes recieved: 0: EOF

@PravinRanjan10 @madhuthorat Could you add the exact command you are running?
Please try following the issue instructions, this creates redundant ping pongs.
@naveenpaul1 @guymguym this seems to me the same as https://github.com/noobaa/noobaa-core/issues/7894
don't we need to take the same changes we did for the health script -https://github.com/noobaa/noobaa-core/pull/7898 and apply them to noobaa-cli?
maybe also this is a repro of https://github.com/noobaa/noobaa-core/issues/7900

@romayalon Here is the command, we are running
Running command: env LC_ALL=C /usr/local/bin/noobaa-cli bucket 2>/dev/null list --wide

@PravinRanjan10 @madhuthorat How many buckets/accounts you have in the system?
I want to try reproduce it

@PravinRanjan10 @madhuthorat How many buckets/accounts you have in the system? I want to try reproduce it

Approx 5k account/buckets.

@romayalon 'as the fix sounds similar to #7894 can we have the fix in 5.15.4 ? currently we are using a workaround which is little cumbersome

@madhuthorat yes, see https://github.com/noobaa/noobaa-core/pull/8120 backport PR to 5.15.4.

@madhuthorat yes, see #8120 backport PR to 5.15.4.

Thank you @romayalon

Re-opening as it's not working as expected. Below is some output:
I have 5k buckets
noobaa-cli bucket list 2>/dev/null |jq
parse error: Unfinished JSON term at EOF at line 4594, column 0

Some other output:

  {
    "name": "bkt4110"
  },
  {
    "name": "bkt1969"
  },
  {
    "name": "bkt3442"
  },
  {

bytes recieved: 0: EOF

@PravinRanjan10 Thanks for the quick verification!
Can you please share with us (off github) the output file of noobaa-cli bucket list &>noobaa-cli-bucket-list.log (we need to capture the output of both stdout and stderr...) Thanks

@PravinRanjan10 Thanks for the quick verification! Can you please share with us (off github) the output file of noobaa-cli bucket list &>noobaa-cli-bucket-list.log (we need to capture the output of both stdout and stderr...) Thanks

output of: noobaa-cli bucket list &>noobaa-cli-bucket-list.log
noobaa-cli-bucket-list.log

output with : noobaa-cli bucket list |jq
[root@node]# noobaa-cli bucket list |jq
load_nsfs_nc_config.setting config.NSFS_NC_CONF_DIR /mnt/cesSharedRoot/ces/s3-config
nsfs: config_dir_path=/mnt/cesSharedRoot/ces/s3-config config.json= {
  ENDPOINT_FORKS: 2,
  ENDPOINT_PORT: 6001,
  ENDPOINT_SSL_PORT: 6443,
  UV_THREADPOOL_SIZE: 16,
  GPFS_DL_PATH: '/usr/lpp/mmfs/lib/libgpfs.so',
  NOOBAA_LOG_LEVEL: 'all',
  NSFS_NC_STORAGE_BACKEND: 'GPFS',
  NSFS_NC_CONFIG_DIR_BACKEND: 'GPFS',
  NSFS_DIR_CACHE_MAX_DIR_SIZE: 536870912,
  NSFS_DIR_CACHE_MAX_TOTAL_SIZE:<PHONE_NUMBER>
}
2024-06-13 05:53:17.527005 [PID-1794896/TID-1794896] FS::GPFS GPFS_DL_PATH=/usr/lpp/mmfs/lib/libgpfs.so
2024-06-13 05:53:17.527117 [PID-1794896/TID-1794896] FS::GPFS found GPFS lib file GPFS_DL_PATH=/usr/lpp/mmfs/lib/libgpfs.so
2024-06-13 05:53:17.530533 [PID-1794896/TID-1794896] [L1] FS::set_debug_level 5
Jun-13 5:53:18.002 [/1794896]   [LOG] CONSOLE:: detect_fips_mode: found /proc/sys/crypto/fips_enabled with value 0
2024-06-13 05:53:18.048957 [PID-1794896/TID-1794896] [L1] FS::FSWorker::Begin: Stat _path=/mnt/cesSharedRoot/ces/s3-config
2024-06-13 05:53:18.049386 [PID-1794896/TID-1794905] [L1] FS::FSWorker::Execute: Stat _path=/mnt/cesSharedRoot/ces/s3-config _uid=0 _gid=0 _backend=GPFS
(node:1794896) NOTE: We are formalizing our plans to enter AWS SDK for JavaScript (v2) into maintenance mode in 2023.

Please migrate your code to use AWS SDK for JavaScript (v3).
For more information, check the migration guide at https://a.co/7PzMCcy
(Use `node --trace-warnings ...` to show where the warning was created)
2024-06-13 05:53:18.050086 [PID-1794896/TID-1794905] [L1] FS::FSWorker::Execute: Stat _path=/mnt/cesSharedRoot/ces/s3-config _uid=0 _gid=0 geteuid()=0 getegid()=0Jun-13 5:53:18.050 [/1794896]   [LOG] CONSOLE:: read_rand_seed: reading 32 bytes from /dev/urandom ...
 getuid()=0 getgid()=0
2024-06-13 05:53:18.051139 [PID-1794896/TID-1794905] [L1] FS::FSWorker::Execute: Stat _path=/mnt/cesSharedRoot/ces/s3-config  took: 0.266377 ms
Jun-13 5:53:18.062 [/1794896]   [LOG] CONSOLE:: read_rand_seed: got 32 bytes from /dev/urandom, total 32 ...

Which version of jq are you using?
Does this work?
noobaa-cli bucket list 2>/dev/null >bucket-list-output
jq <bucket-list-output

Hi @PravinRanjan10 I checked the output file you provided and after stripping off the log prints I can parse it with jq successfully. Which version of jq are you using? Does this work?
noobaa-cli bucket list 2>/dev/null >bucket-list-output
jq <bucket-list-output

@guymguym
Jq VERSION:
jq-1.6-15.el9.x86_64
Yes, if number of buckets are less (around <=2.5k), it works fine with pipe and jq.

@PravinRanjan10 @guymguym
I tried it this way - cat noobaa-cli-bucket-list.log | jq
and it worked, I don't see any issue

Actually, the problem is with PIPE only. In code we are trying to collect the output of noobaa-cli bucket list and parse. The problem is, if size of bucket list increases then we need to use stdout pipe to collect those output and parse.

@PravinRanjan10 I created 6000 buckets and couldn't see your issue, can we have access to your machine?

Updating that I had a call with @PravinRanjan10 and after upgrading to the latest RPM we couldn't see the issue again.
Pravin is currently running some more tests for verifying we can close this one

Closing the issue per @PravinRanjan10 confirmation.


Chat Glitch

What problem did you noticed?
The chat has strange symbols in it
What is the expected result?
The chat looks nomral
What is the current result?
The chaat is unreadable and you cannot send messages
How to reproduce the issue?
I am not sure
Operating System and Version: Ubuntu 16.0

Unturned Version: Latest
Rocketmod Version: Latest

Update to the newest version of RocketMod.

I am pretty sure its updated

No I have updated and it is still happening. It also crashes every time someone types

When I try to type I get this error
NullReferenceException: Object reference not set to an instance of an object - System.String.Concat (System.Object arg0, System.Object arg1)
SDG.Unturned.Block.write (System.Object objects)
SDG.Unturned.Block.write (System.Object[] objects)
SDG.Unturned.SteamPacker.getBytes (Int32 prefix, System.Int32& size, System.Object[] objects)
SDG.Unturned.SteamChannel.getPacket (ESteamPacket type, Int32 index, System.Int32& size, System.Byte[]& packet, System.Object[] arguments)
SDG.Unturned.SteamChannel.send (System.String name, ESteamCall mode, ESteamPacket type, System.Object[] arguments)
SDG.Unturned.ChatManager.askChat (CSteamID steamID, Byte mode, System.String text)
System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture)
Rethrow as TargetInvocationException: Exception has been thrown by the target of an invocation.
System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture)
System.Reflection.MethodBase.Invoke (System.Object obj, System.Object[] parameters)
SDG.Unturned.SteamChannel.receive (CSteamID steamID, System.Byte[] packet, Int32 offset, Int32 size)
SDG.Unturned.Provider.receiveServer (CSteamID steamID, System.Byte[] packet, Int32 offset, Int32 size, Int32 channel)
SDG.Unturned.Provider.listenServer (Int32 channel)
SDG.Unturned.Provider.listen ()
SDG.Unturned.Provider.Update ()

This is an unturned bug; not RocketMod.


[WIP] Updating badge from travis to GH actions

@jaimergp -- thanks for your pointer, I've added the badge (leaving travis badge there too for now)
Going to merge myself as I haven't touched any python


Add command to write out small/structural variants as JSONL

Is your feature request related to a problem? Please describe.
For annonars and display we need to have files with small and structural variants.
Describe the solution you'd like
Write out such files that contain the variant, the RCV, and the assessment and review status.
Describe alternatives you've considered
N/A
Additional context
N/A

There is extract-vars.


Support for old Ruby/Rails versions

The documentation says Camaleon supports Ruby 1.9 and Rails 4.1, but that's not really the case right now.

Some of the dependencies in the gemspec require Ruby 2.0, or even 2.2, so the current version of Camaleon can't be installed with Ruby 1.9.
Running Rubocop reveals multiple cases of syntax in the code that is incompatible with Ruby 1.9.
Rails 4.1 predates ActiveJob. Running the tests when using Rails 4.1 results in this error:

NoMethodError:
       undefined method `deliver_later' for #<Mail::Message:0x0000000a224e80>
     # ./app/helpers/camaleon_cms/email_helper.rb:29:in `cama_send_email'
     # ./app/helpers/camaleon_cms/email_helper.rb:17:in `send_email'
     # ./spec/helpers/email_helper_spec.rb:7:in `block (3 levels) in <top (required)>'
     # ./spec/rails_helper.rb:28:in `block (3 levels) in <top (required)>'
     # ./spec/rails_helper.rb:27:in `block (2 levels) in <top (required)>'

Rails 4.2+ works fine. Ruby 2.2+ works fine.
The versions of Ruby and Rails that aren't currently working with Camaleon have been unmaintained for multiple years now, so I favor dropping them from the documentation for future development. Otherwise, we should manage dependencies so these versions actually work.

Hi @brian-kephart
I agree with you, we can drop old versions and change ruby/rails minimum versions.
Cheers!

Thanks for the fast reply! I’ll submit a PR. What about Ruby 2.2 and Rails 4.2? They are unmaintained as well, but not causing any build problems. Should we keep them or not?

We can keep them, because if we change it we can affect existent projects.