New high-level Graph/Dataset API

I'd like to migrate from RDFLib and start using pyoxigraph, but I have multiple issues with the Triple/Quad/Store-based API:

it does not provide representations of RDF graph and RDF dataset
it's too low-level. Jena contains a low-level/internal Node/Triple/Graph API, but also a high-level/end-user Resource/Statement/Model/Dataset API, which is much more intuitive IMO
it does not provide an easy migration path for users familiar with RDFLib's Graph and Dataset

Describe the solution you'd like
I propose creating Graph and Dataset interfaces, and modeling their API contracts using a builder pattern (after Jena's Model and Dataset) while retaining Python idioms. It's based on a similar proposal I made for RDFLib.
For example (not an exhaustive list):
Graph

add(graph: Graph) -> Graph
add_statement(stmt: Statement) -> Graph
create_resource(uri: str) -> Graph
create_property(uri: str) -> Graph
create_literal(value, datatype: Resource) -> Graph
triples() -> List[Statement]
...

Dataset

add_named_graph(resource: Resource, graph: Graph) -> Dataset
has_named_graph(resource: Resource) -> bool
remove_named_graph(resource: Resource) -> Dataset
replace_named_graph(resource: Resource), graph: Graph) -> Dataset
graphs() -> List[Resource]
get_default_graph() -> Graph
get_named_graph(resource: Resource)

A simpler API version could introduce only Graph and Dataset without introducing Resource, Statement etc., instead reusing pyoxigraph's existing NamedNode/BlankNode (or their superclass?) and Triple.

@Tpt any comments?

it does not provide representations of RDF graph and RDF dataset

A Store is more or less a Dataset imho with extra methods related to the database considerations.
About your Dataset API I tend to think the most important pieces are already there:

add_named_graph(resource: Resource, graph: Graph) -> Dataset: Store.add_graph without the second parameter
has_named_graph(resource: Resource) -> bool: Store.contains_named_graph
remove_named_graph(resource: Resource) -> Dataset Store.clear_graph and Store.remove_graph
replace_named_graph(resource: Resource), graph: Graph) -> Dataset not there directly. It seems a combination of remove+add
graphs() -> List[Resource] Store.named_graphs
get_default_graph() -> Graph and get_named_graph(resource: Resource): not there, no graph API yet

What might be nice would be to add a "Graph" view on top of Store that would allow to easily manipulate a graph from an underlying store.
What we might have is:
class Store:
   ...
   def graph(self, name: NamedNode | BlankNode | DefaultGraph) -> StoreGraph: ...

class StoreGraph:
   def add(self, triple: Triple): ... # Your add_statement function
   def clear(self): ...
   def remove(self, triple: Triple): ...
   def extend(self, triples: Iterable[Triple]): ... // Your add function
   def  triples_for_pattern(subject, predicate, object) -> Iterator[Triple]: ...
   def __iter__(self) -> Iterator[Triple]: ... // Your triples function

What do you think?

In Jena, this is the Graph-like Model implementation which implements the higher-level resource/property API using lower-level triples:
https://github.com/apache/jena/blob/main/jena-core/src/main/java/org/apache/jena/rdf/model/impl/ModelCom.java
This is probably a better illustration than I could come up with :)

I made the following sketch that introduces a new high-level API and implements it using the existing lower-level API:

new abstract classes Resource, Property, Graph, Dataset are introduced together with their implementations. Very much inspired by Jena's API.
Literal is reused
Store is never directly exposed in the high-level API
Triple and Quad are only exposed occasionally (i.e. resource.list_properties(), graph.list_triples() and dataset.list_quads()) and generally avoided in favor of Resource, Property etc.

class Resource(BlankNode, NamedNode):
class Property(Resource):
class Graph:
class Dataset:

class ResourceImpl(Resource):

    def __init__(node: Node, graph: GraphImpl):
        self.node = node
        self.graph = graph

    def add_property(self, property: Property, value: Node) -> Resource:
        self.graph.store.add(Quad(self, property, value, None))
        return self

    def list_properties(self, property: Property) -> Iterator[Triple]:
        quads = list(self.graph.store.quads_for_pattern(self, property, None, None))

        triples = []
        for quad in quads:
            triples = quad.triple

        return iter(triples)

class GraphImpl(Graph):

    def __init__(store: Store):
        self.store = store

    def create_resource(self) -> Resource:
        return Resource(BlankNode())

    def create_resource(self, uri: str) -> Resource:
        return Resource(NamedNode(uri))

    def create_property(self, uri: str) -> Property:
        return Property(NamedNode(uri))

    def list_triples(self) -> Iterator[Triple]:
        quads = list(self.graph.store.quads_for_pattern(None, None, None, None))

        triples = []
        for quad in quads:
            triples = quad.triple

        return iter(triples)

class DatasetImpl(Dataset):

    def __init__(store: Store):
        self.store = store

    def graph_names(self) -> Iterator[Resource]:
        graph_names = self.store.named_graphs()

        graph_name_resources = []
        for graph_name in graph_names:
            graph_name_resources.append(Resource(graph_name))

        return iter(graph_name_resources)

    def add_named_graph(self, name: Resource, graph: Graph) -> Dataset:
        self.store.add_graph(name)
        return self

    def list_quads(self) -> Iterator[Quad]:
        return self.graph.store.quads_for_pattern(None, None, None, None)

@Tpt LMK whether this helps.

@Tpt I personally think Dataset and Graph would be the best names that align with both RDFLib and the RDF spec.
I see them as abstract interfaces that should not know or care where they came from, whether it was the DB or an HTTP response - concrete implementations or separate classes should take care of that.

Agreed! That definitely make sense.

Should I try to create a PoC in userspace to show what I mean?

That would be amazing! This POC can even become the real use "high level" API. Writing Python APIs in Rust is a bit cumbersome, it might be relevant to have all these high level API and keep only the bits interacting with the Rust implementations in Rust (SPARQL querying, storage I/Os, parsers...). WDYT?
Your proposal seems to go into a great direction. Thank you!
Some suggestions:

I would tweak how GraphImpl work to reuse the same underlying store and have a graph_name. This way it would allow to be able to interact with a given named graph of a specific store while still enabling the "single graph" use case (with store = Store() and graph_name = DefaultGraph()). WDYT?
self.store.add_graph(name) # is it necessary? indeed it's not necessary. Just like SPARQL graph store protocol, a named graph is created automatically if a triple in this graph (aka quad) is added to the store.

Are you suggesting that Graph should have an inherent URI name? I think that was one of the reasons that RDFLib API and implementation was so weird, but I would really like @aucampia's input on that.
In RDF graphs don't have a name before they become part of a dataset. Maybe in a quad-based implementation it would be acceptable, but it shouldn't be exposed publicly. But how about the same graph being added to different datasets under different names?
I guess this is a friction point between a graph-based API and a quad-based storage. If you look at Jena's implementation, adding a graph to a dataset involves copying quads:
https://github.com/apache/jena/blob/main/jena-arq/src/main/java/org/apache/jena/sparql/core/DatasetGraphQuads.java#L47
Can't find how getting a graph looks. Maybe @afs can help.
Am I right that currently Store is always DB-backed? There is no in-memory option?
I agree about the rest BTW :)

Jena's Model API is called "model" and has "Resources" and "Statements" because  that was the language back in RDF 1.0 times. Jena has Dataset/DatasetGraph due to a lack of a better second name.
"Statement", "Model"  is term-typed, (no literals as subjects!)
"Triples" "Graph" is "generic RDF" - also Triples can hold variables.
RDF1.1 is more concrete in its view of the world - "graph", "RDF term" and "triple".
It does usefully give a separation between the application code API and the Graph level SPI which is focuses on implementation.
The Model/Graph, API/SPI, separation goes back to the original Jena2.
DatasetGraphQuads is rarely used. DatasetGraphTriplesQuads, which separates triples/default graph and quads/named graphs, is more common. This runs through TDB2 and the DBOE framework (database transaction and storage code) as well. Graphs from the storage units are dynamic views of the data.  Talking about "Database" is typically reserved for concrete storage implementations.
Adding a graph is a copy - this gives the isolation for the change. Once the call is done or transaction finished, the added graph argument is unconnected with the storage.
There is an exception - there is a dataset that links to its graphs - then graphs can be any implementation and implementations can be mixed in the dataset.

Writing Python APIs in Rust is a bit cumbersome, it might be relevant to have all these high level API in Python and keep only the bits interacting with the Rust implementations in Rust (SPARQL querying, storage I/Os, parsers...).

That sounds similar to the Model/Graph. It can be cumbersome to write graph level code - there is a slowly growing function library "called G -- assumes static import in Java) for working with Graphs. It's not so much an API (yet?) as conveniece for implementers.
Apache CommonsRDF might be worth a look. The idea was to have an common API that application libraries could target to produce portable (across Java :-) algorithms.

It seems that we would also need something like Jena's GraphView which combines dataset and graph name.

I put together a PoC implementation and an example that shows it usage. Seems to work correctly.
https://github.com/namedgraph/oxijen/blob/main/example.py

It seems that we would also need something like Jena's GraphView which combines dataset and graph name.

The Jena NamedGraph interface is a concept that hasn't got much usage. In fact, there is only one usage I can find and its in jena-text. The text index can be dataset centric and recored the graph name,
Always beware of legacy!

@afs thank you for your input. If we were to implement an in-memory dataset, which of Jena's classes should we look at?

First - decide what feature you want. Multithreaded? Transactions? These influence the choice of datastructures

Maybe DatasetGraphSimpleMem as a start?

That's an extremely basic implementation - very simple so its easy to see whether its functionally correct or not. note it's in "src/test".
It scans on any find() operation - no indexes.
It does inherit from DatasetGraphTriplesQuads whichmight be inspiration of you want storage in graphs (rather than triples (dft graph) and quads).
The transactional, in-memory DatasetGraph is DatasetGraphInMemory which uses Dexx for maps that allow readers and a writer at the same time to get ACID (well, no real D!) transactions.


@conda-forge-admin, please rerender

Additional comment:
No response

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I rerendered the recipe in conda-forge/finance_enums-feedstock#2.


Correct ECR credential provider example

The example credential provider config file is misleading in a few ways:

The image pattern for ECR China has the wrong domain name.
The args section implied that get-credentials is used by the ECR credential provider. It isn't.
The name of the credential provider does not match the name of the executable produced from: https://github.com/kubernetes/cloud-provider-aws/tree/master/cmd/ecr-credential-provider

If this example is not intended to be for the ecr-credential-provider implemented in kubernetes/cloud-provider-aws -- the second two points are arguable; but the first is not in my opinion.

/approve
/lgtm
thanks @cartermckinnon

deploy/netlify timed out after an hour 🤷
/retest

/retest

@sftim can you add ok-to-test so I can get this mergeable?


merge from template-coveralls

package.json

chore(deps): add ^8.3.16 remove ^8.3.15 (devDependencies.npm-pkgbuild)

.github/workflows/openapi.yml

chore: add actions/download-artifact@v2 (jobs.publish_doc.steps.uses)

.github/workflows/ci.yml

chore(actions): merge from template .github/workflows/ci.yml

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

npm package (@latest dist-tag)
v5.0.100
GitHub release

Your semantic-release bot :package::rocket:


Why did this great project stop development?

There is some real good work here.

Just a heads up, it's alive again!


saveConfig fails if config file location and /tmp/ are on different filesystems

This is another problem I've noticed, while debugging #4.
On many OpenWRT device /etc/config is a read-only filesystem overlaid with a writable filesystem, while/tmp/ is usually an actual tmpfs/ramdisk.
Consider saveConfig() being called for network.
The call to  ioutil.TempFile in saveConfig creates a temporary file in\tmp\.
A subsequent call to os.Rename() tries to hardlink the file to /etc/network.
While this a considered best practice to ensure atomic file changes it will fail for this case as the hardlink crosses filesystem boundaries.
A typical error looks like this:
rename /tmp/network012772557 /etc/config/network: invalid cross link
As the user can't choose a different location for the temporary files, this bug renders this library useless on many OpenWRT installations.

Huh. I didn't think of that (or misremembered how os.Rename operates).

saveConfig now places a temporary file in /etc/config (or whatever the config root is), named /etc/config/.012772557.network, before writing the config to it and renaming it to /etc/config/network. OverlayFS does support hardlinks, does it?
While this may leave dot files behind if (for whatever reason) the cleanup mechanism fails, I'd prefer those files being present over half-written config files if we directly write to /etc/config/network.
As far as I can tell, UCI itself ignores dot files in /etc/config. I didn't find the C source responsible for this behaviour, but I've empirically tested this on one of our OpenWRT devices.

Works on our system and looks okay to me.


An INCLUDE_AWS_LINKS true/false env var to indicate preferred parser behavior

Many of the parsers assume the Slack receiver has AWS Console access to the resources mentioned and include back-links into AWS. Even generic SNS messages assume the receiver can view/manage SNS topics.
Sometimes the people at the Slack target don't have any access to the AWS resources generating the events. It would be nice to have the option to either

have parsers include or omit back-links to AWS (as a per-deployment preference)
in that parser list have two parsers for the same event with/without links (first selector decides)

I suggest an INCLUDE_AWS_LINKS environment variable that tells that deployment whether or not including back-links is preferred.
Multiple deployments for different targets works fine, and I can set this global preference so that I don't have to fork the code-base for internal/external audiences. I've implemented something like this to test it out, and could extract a PR later if this is a desirable feature.

Seems like it could be helpful!
We've had some requests for even more links (like "See Logs" that links to the time of alert for log-metric-based CloudWatch alarms). As parsers are added, links might "leak".  Do you see a danger there?
The average user of this repo probably has access to the Console, but a feature-add to make them optional would be welcome as long as the default is true. :)

No, no danger I think @homeyjd, as the links don't confer any access. They will just be useless (and/or confusing) for users without suitable AWS access. That's why I called it a 'preference' setting and 'preferred parser behavior', I don't expect every parser will comply, only the ones that support the preference.
Once the preference exists, it would nice if new/updated parsers considered it, and just left out the links if  INCLUDE_AWS_LINKS=false. But if INCLUDE_AWS_LINKS=true then go to town and link all the things 😄
I just added to eventdef.js:
/** Whether to include links to AWS resources in Slack messages **/
const includeAwsLinks = (_.isString(process.env.INCLUDE_AWS_LINKS) && _.lowerCase(process.env.INCLUDE_AWS_LINKS) === 'true');
global.includeAwsLinks = includeAwsLinks;

And then in parsers I just wrap linked chunks or alternatives in if (includeAwsLinks):
        if (initiator) {
                fields.push({
                        title: "Triggered By",
                        value: initiator,
                        short: true
                });
        }

        if (includeAwsLinks) {
                fields.push({
                        title: "Logs",
                        value: `<${logsUrl}|View Logs>`,
                        short: true
                });
                fields.push({
                        title: "Build",
                        value: `<${phaseUrl}|View Build>`,
                        short: true
                });
        }

Since the intent is to leave default=true, I might suggest changing that behavior to HIDE_AWS_LINKS.
global.HIDE_AWS_LINKS = /true|1/i.test(process.env.HIDE_AWS_LINKS || "");

The feature-gate could be written in a less-brittle way:
// brittle, if variable is not defined (such as during a test?), script will always fail
if (!HIDE_AWS_LINKS) { /* add link */ }
// less brittle
if (!global.HIDE_AWS_LINKS) { /* add link */ }

As a possible alternative, eventdef.js could have a getConsoleLink(urlPath, urlQuery) method that returns undefined if when inactive.  That would eliminate the need for another global. :)
    getConsoleLink(urlPath, urlQuery, region = "us-east-1") {
        if (/true|1/i.test(process.env.HIDE_AWS_LINKS || "")) return undefined;
        return `https://${region}.console.aws.amazon.com${urlPath}?${urlQuery}`;
    }

I prefer a simple boolean test (as well), but that could be a method.
   isHideAwsLinks() {
        return (/true|1/i.test(process.env.HIDE_AWS_LINKS || ""));
   }

You could have getConsoleLink too but that might not cover all possible URLs and then you'll be adding more and more for variations. Though link creating methods that automatically handled thing like amazonaws.cn regions etc. could be handy.

I added this for now.  Open to a PR if you'd like. https://github.com/arabold/aws-to-slack/commit/62bd18178f761b619ce6be43b8285a597d9d876c


NUnit wrong/missing test results !?

At https://github.com/reportunit/reportunit/blob/master/ReportUnit/Parser/NUnit.cs#L123
the test-case result attribute is checked. Ok.
But when the test-case is
executed="True" result="Success" success="False"

Then??

Hmm.. it will only view the result attribute.  When would this happen though?
Node: Version 3 does not have the success attribute.


Chart release failed: heavy-pigeon: context.deadlineExceededError{}

Okay, now i've managed to install and to sync flux helm with my private git repo
I've tried a simple installation of sonarqube, got the release with helm fetch --untar directly in the git helm charts repo
But now i've got the following error from the operator logs :
ts=2018-07-16T11:54:55.16597311Z caller=operator.go:171 component=operator debug="PROCESSING item [\"sonarqube/heavy-pigeon\"]"
ts=2018-07-16T11:54:55.166004052Z caller=operator.go:228 component=operator debug="Starting to sync cache key sonarqube/heavy-pigeon"
ts=2018-07-16T11:55:00.476575709Z caller=status.go:75 component=annotator err="context deadline exceeded"
ts=2018-07-16T11:55:00.62039208Z caller=release.go:154 component=release info="releaseName= heavy-pigeon, action=CREATE, install options: {DryRun:false ReuseName:false}"
ts=2018-07-16T11:55:05.6330603Z caller=release.go:196 component=release error="Chart release failed: heavy-pigeon: context.deadlineExceededError{}"
ERROR: logging before flag.Parse: E0716 11:55:05.633180       7 operator.go:219] error syncing 'sonarqube/heavy-pigeon': context deadline exceeded

Here is the yaml file describing the release :
---
apiVersion: v1
kind: Namespace
metadata:
  name: sonarqube
---
apiVersion: helm.integrations.flux.weave.works/v1alpha2
kind: FluxHelmRelease
metadata:
  name: sonarqube
  namespace:  sonarqube
  labels:
    chart: sonarqube
spec:
  chartGitPath: sonarqube
  releaseName: heavy-pigeon

If I'm reading that log correctly, it'll keep trying to install the chart (on a period of a few minutes). Are there repeated failures?

Yep, it tries to reinstall again and again... Always failing

At a scan, it looks like it's a timeout inside the Helm client that's firing. It's also in a "side-effecting" bit of code, in which the operator goes back after a release and annotates all the resources that were updated. If you look at the Helm releases via helm, has it actually released the chart?
There may be reasons that's it's failing this step that we can do something about, but either way, it shouldn't end up looking like the release failed.

Nope, helm list doesn't show any release...

OK I was being too optimistic in my reading of the log there. We can bump the Helm client timeout up, if we can pin the problem on that. Does using helm install work OK? Sorry to keep bouncing this back at you.

No problem, I'm very glad to have support =)
helm install works and ends in 2.2s, the containers are deployed and created and the release is listed by helm list

Hmm, it's possible that it times out trying to install the packages, but also plausible that it just can't connect.  Is there anything in the log to suggest that it's succeeded at connecting (to Tiller) at all? It's pretty chatty so I'd expect to see some info or debug entries, if it was getting something done.

I was just typong that I've looked at the tiller logs and that there is no trace of the deployments in the logs, so it seems that it can't even connect

Hmm, if I telnet the cluster IP of tiller on the port 44134 I've got a connection refused

If I add the 44135 port to the service I can reach the http server though, so it seems that the connexion between the service and the deployment is not broken

Ah got it... Tiller lauche command was tiller --listen=localhost:44134, changed it to tiller --listen=<IP_ADDRESS>:44134 and now I have an other error =) :
ts=2018-07-16T16:01:03.652496839Z caller=release.go:154 component=release info="releaseName= heavy-pigeon, action=CREATE, install options: {DryRun:false ReuseName:false}"
ts=2018-07-16T16:01:03.671799918Z caller=release.go:196 component=release error="Chart release failed: heavy-pigeon: &status.statusError{Code:14, Message:\"transport is closing\", Details:[]*any.Any(nil)}"
ERROR: logging before flag.Parse: E0716 16:01:03.671932       7 operator.go:219] error syncing 'sonarqube/heavy-pigeon': rpc error: code = Unavailable desc = transport is closing
ts=2018-07-16T16:01:03.671953621Z caller=operator.go:168 component=operator debug="Processing next work queue job ..."
ts=2018-07-16T16:01:04.013234416Z caller=release.go:154 component=release info="releaseName= heavy-pigeon, action=CREATE, install options: {DryRun:false ReuseName:false}"
ts=2018-07-16T16:01:04.029040737Z caller=release.go:196 component=release error="Chart release failed: heavy-pigeon: &status.statusError{Code:14, Message:\"transport is closing\", Details:[]*any.Any(nil)}"
ERROR: logging before flag.Parse: E0716 16:01:04.029643       7 operator.go:219] error syncing 'sonarqube/sonarqube': rpc error: code = Unavailable desc = transport is closing
ts=2018-07-16T16:01:04.029681721Z caller=operator.go:168 component=operator debug="Processing next work queue job ..."

And still no trace in tiller's logs

Okay, reinstalled tiller and now it works, sorry for the inconvenience =/


Feature/126 firefox tab container support

Uses the cookieStoreId from Firefox to sandbox the different container tabs. This API is described in https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/tabs/Tab and https://wiki.mozilla.org/Security/Contextual_Identity_Project/Containers.
I am just testing this in Chrome now to ensure it also works. I have tested this in Firefox and it works as expected. This makes the tab containers incredibly useful in an organisation where you have many roles.
Resolves #126

Could we get this in? @tilfin

I'm sorry that this feature is difficult to maintain for me.


fix(test/{ Change - change }): merge the files test/Change and test/change

The motivation is that on case-insensitive system, the files overwrite each other.
The bash command
# uniq -D: print all duplicate lines
git ls-files | sort --ignore-case | uniq -D --ignore-case

lists all the paths that are identical when upper/lower case is ignored.
Zulip

bors merge p=10


Add auto merge

Additional comment:
@conda-forge-admin, please add bot automerge

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added bot automerge in conda-forge/colmena-feedstock#2.


fix(versions): update Activiti/activiti-cloud-full-chart-security versions

UpdateBot pushed helm dependency: activiti-cloud-full-example to: 7.1.332

UpdateBot commands:
updatebot push-version --kind helm activiti-cloud-full-example 7.1.332


feat: Sequence integration tests

Fixes: ####
[Describe your change here]
Test Plan
[Describe test plan here]
Deployment instructions
[Add any special deployment instructions here]

Done for both


fixed clusterInstallParameters (POSTINSTALLSCRIPTURI Script param was…

The template did not work correctly. The Swarm cluster was not created after deployment because of missing parameter value for the shell script.
I change the following and now the Swarm cluster is up and running after deployment:

Fixed clusterInstallParameters in ARM template. Script Parameter POSTINSTALLSCRIPTURI (value disabled) was not present and therefor the shell script for Docker Swarm setup did not worked correctly

Changed comments and echos in the shell script to reflect Docker Swarm instead of mesos

Changed  Windows Jump Host VM to Server 2016 Image  because Azure Stack ist a modern platform... :-)

@J0F3,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot


feat: support vue3

How can you build a plugin? I cloned PR and am trying to build with npm run build but get various errors. Is there any way to get an already assembled plugin?

How can you build a plugin? I cloned PR and am trying to build with npm run build but get various errors. Is there any way to get an already assembled plugin?

It looks a little bit hard, if u wanna build a plugin to hack with this problem, I'm not sure the Author is still alive or not or he just forgot his pwd.
but here is my solution, replace rete.min.js during the Deploy processing
//   ./index.js

const { exec, spawn, execSync } = require('child_process');
const path = require('path');
const fs = require('fs');

function log(msg) {
  console.log(`deploy: ${msg}`);
}

log('update node_modules');
let installCMD = exec(`npm install`, { cwd: path.resolve(__dirname, '../') });
installCMD.stdout.pipe(process.stdout);
installCMD.stderr.pipe(process.stderr);
installCMD.on('exit', function () {
  //  replace rete.esm.js
  log('replace ete.esm.js');
  let targetFile = path.resolve(__dirname, '../', 'node_modules/rete/build/rete.esm.js');
  let sourceFile = path.resolve(__dirname, './rete.esm.js');
  fs.writeFileSync(targetFile, fs.readFileSync(sourceFile));

  log('npm run build');
  let buildCMD = exec(`npm run build:no-cache`, { cwd: path.resolve(__dirname, '../') });
  buildCMD.stdout.pipe(process.stdout);
  buildCMD.stderr.pipe(process.stderr);
  buildCMD.on('exit', function () {
    log('start deploy');
    process.exit();
  });
});

@carl-jin I'm unable to build the plugin with these changes even after updating rollup and rollup vue plugin
(node:9553) UnhandledPromiseRejectionWarning: SyntaxError: Unexpected token (10:13) in /home/ni55an/Workflow/retejs/vue-render-plugin/src/Node.vue?vue&type=script&lang.js
    at Parser.pp$4.raise (/home/ni55an/Workflow/retejs/vue-render-plugin/node_modules/rollup/dist/shared/rollup.js:16954:13)
    at Parser.pp.unexpected (/home/ni55an/Workflow/retejs/vue-render-plugin/node_modules/rollup/dist/shared/rollup.js:14462:8)
    at Parser.pp.expect (/home/ni55an/Workflow/retejs/vue-render-plugin/node_modules/rollup/dist/shared/rollup.js:14456:26)
    at Parser.pp$2.parseBindingList (/home/ni55an/Workflow/retejs/vue-render-plugin/node_modules/rollup/dist/shared/rollup.js:15682:17)
    at Parser.pp$3.parseMethod (/home/ni55an/Workflow/retejs/vue-render-plugin/node_modules/rollup/dist/shared/rollup.js:16719:22)
    at Parser.pp$3.parsePropertyValue (/home/ni55an/Workflow/retejs/vue-render-plugin/node_modules/rollup/dist/shared/rollup.js:16641:23)
    at Parser.pp$3.parseProperty (/home/ni55an/Workflow/retejs/vue-render-plugin/node_modules/rollup/dist/shared/rollup.js:16626:8)
    at Parser.pp$3.parseObj (/home/ni55an/Workflow/retejs/vue-render-plugin/node_modules/rollup/dist/shared/rollup.js:16572:21)
    at Parser.pp$3.parseExprAtom (/home/ni55an/Workflow/retejs/vue-render-plugin/node_modules/rollup/dist/shared/rollup.js:16307:17)
    at Parser.pp$3.parseExprSubscripts (/home/ni55an/Workflow/retejs/vue-render-plugin/node_modules/rollup/dist/shared/rollup.js:16126:19)
    ```

https://github.com/retejs/rete/issues/513#issuecomment-892944094

1.0.0-rc1 is published. Based on these changes with a couple of fixes

in the thread https://github.com/retejs/vue-render-plugin/issues/39 you can find more information


UI for inspecting build logs and failed builds from the artifact cache

See original issue on GitLab
In GitLab by [Gitlab user @LaurenceUrhegyi] on Aug 1, 2018, 12:50
Background
Now that we have landed Caching Failed Builds https://gitlab.com/BuildStream/buildstream/merge_requests/475 we need to add UI for users to interact with the failed build logs.
An assumption:

We only ever store one build (failed or successful) per artifact cache key.

Potential future optimisation:

We can introduce a way of marking the artifacts as "failed" in the remote cache, in such a way that we don't need to download the whole artifact before knowing if it's failed.

Task description

[ ] bst checkout {--hardlinks} for failed build, which checks out failed build tree and stages dependencies
[ ] bst shell for failed build, which sets up shell environment with SafeHardlinks wrapper around the failed build checkout
[ ] bst show able to indicate 'failed' vs. 'successful' status, in addition to existing 'cached' vs. 'downloadable' states
[ ] bst show --logs to view build logs embedded in an artifact
[ ] Integration tests
[ ] Documentation

Acceptance Criteria

[ ] Have a user manually test that the above commands work as expected when inspecting the failed build logs.

In GitLab by [Gitlab user @LaurenceUrhegyi] on Aug 1, 2018, 12:52
marked this issue as related to #76

In GitLab by [Gitlab user @franred] on Aug 1, 2018, 14:56

Now that we have landed Caching Failed Builds https://gitlab.com/BuildStream/buildstream/merge_requests/475 we need to add UI for users to interact with the failed build logs.

I would say that this task is part of the one described in: https://mail.gnome.org/archives/buildstream-list/2018-July/msg00051.html
It does not only need to interact with failed build logs but with any log, which currently are not available to the user unless manually inspecting the cache directory ~/.cache/buildstream.

In GitLab by [Gitlab user @tristanvb] on Aug 2, 2018, 09:22
This appears to be a duplicate to #234, in fact, according to the headline.
Also this ignores the bst artifact command subgroup which is discussed on the mailing list as [Gitlab user @franred] accurately points out.
The summary seems to lump a lot of stuff into the same bucket, so I ask [Gitlab user @LaurenceUrhegyi] to please triage this more clearly into closable, separate issues.
We can keep this one open if you want to have a flagship issue, but the individual tasks would be better suited to block on the closing of separately filed individual issues. I think we don't really need this one in this case, though. For instance #234 is an issue regardless of whether builds have failed or not.

In GitLab by [Gitlab user @tristanvb] on Aug 2, 2018, 09:34
For the debugging of failed builds parts of this, I have filed #539

In GitLab by [Gitlab user @tristanvb] on Aug 2, 2018, 09:35
I'm not sure what the bst checkout part of this is intended for, maybe this part needs to have a coherent proposal on the list.

In GitLab by [Gitlab user @LaurenceUrhegyi] on Aug 2, 2018, 17:09
closed


AjaxFileUpload: can't clear queue / Max Files Exceeded message results

Possible bug, otherwise unable to get a known action to work.
Summary:
ajaxToolkit:AjaxFileUpload, maxfiles=1 is on web form, within ContentTemplate, which is within UpdatePanel.
User cancels out of upload after selecting a file, thereby placing it into queue but not uploading it.
The next time the AjaxFileUpload form is shown, it won't accept another file selection, throwing "Maximum number files exceeded" message, even though I have verified that I have programmatically cleared the queue area via:
$(".ajax__fileupload_queueContainer").empty();
and also:
$(".ajax__fileupload_queueContainer").html("").change();

The AJAX Control Toolkit \18.1
The installation method

[ ] Installer
[x ] NuGet package
[ ] A custom build from the source code

Minimal steps to reproduce the bug
place this into VS web forms project:
<asp:ScriptManager ID="ScriptManager1"
EnablePageMethods="true" runat="server">
</asp:ScriptManager>
<asp:UpdatePanel ID="UpdatePanel1" runat="server" UpdateMode="Conditional">

<ajaxToolkit:AjaxFileUpload ID="FileUpload1" runat="server"
Width="100%"
BackColor="#cceeff"
OnUploadComplete="FileUpload1Complete"
AllowedFileTypes="doc,docx"
MaximumNumberOfFiles="1"
ClearFileListAfterUpload="true"
MaxFileSize="20000"
OnUploadStart="FileUpload1Start"
OnClientUploadComplete="uploadComplete"
OnClientUploadError="uploadError"
/>

</asp:UpdatePanel>
Step 1: Select a file. Don't upload, and don't click remove.
Step 2: User clicks cancel button outside of updatePanel which runs following code.
Tried both these statements to clear queue within the cancel button code
$(".ajax__fileupload_queueContainer").empty();
$(".ajax__fileupload_queueContainer").html("").change();
The div containing the above ajaxFileUpload control is then hidden via jquery's .hide() method.
Step 3: show the div again.
Actual result
The upload button continues to show, but no file shows in the queue and the remove button is missing.
A file can't be selected (maximum number of files exceeded)
Expected result
Clearing the queue via the above method should reset the queue to no files selected.
Note that I'm unable to force user to gracefully click remove, and unable to keep them from clicking something that will close the upload div, so I'm needing to clear the queue when the user takes an action such as canceling or showing the enclosing div again.
[General questions: is there some better way to re-set the AjaxFileUpload control, possibly even re-writing it to the DOM, as a solution? Is there some other command to re-set AjaxFileUpload's queue, so that it re-sets what it thinks are the current number of files in the queue ?
tnx
Browser(s) used
Chrome, latest
A site deployment method

[x ] VS development web-server,
[ ] IIS

Hi @StringTheory2
When you clear the queueContainer div, you remove graphical representation of files in the file queue.
AjaxFileUpload stores the file queue internally, and there is no way to manipulate it other than interacting with a control's UI.
I don't completely understand your scenario, because I do not see problems with removing selected files from the file queue even if the control was hidden and re-shown.
Would you please provide a sample project that illustrates the user workflow?


Question: Why does Zappa call unschedule/schedule when calling update?

I see that zappa update invokes self.schedule() https://github.com/zappa/Zappa/blob/bb5834fa2f7c31f56cdc39fa883b96f9a99408e3/zappa/cli.py#L1232  which in turn invokes self.zappa.schedule_events() https://github.com/zappa/Zappa/blob/bb5834fa2f7c31f56cdc39fa883b96f9a99408e3/zappa/cli.py#L1429 which calls self.unschedule_events https://github.com/zappa/Zappa/blob/bb5834fa2f7c31f56cdc39fa883b96f9a99408e3/zappa/core.py#L3002
It looks like that on every update, Zappa unschedules all event handlers, removes permissions and creates them again.
Could someone explain the reasoning behind this implementation choice?
Specifically, if I comment out the call to schedule() while doing an update, would there be any negative consequence? I prefer to explicitly control events with schedule and unschedule.

I guess this is a trick to make sure all periodic scheduled event ( rate xxxxxxx) are run once immediately.

I believe that currently there no way to detect a change in the schedule, so the schedule is re-created on each deployment.
closing.


Documentation link is not working.

I want the list of events but documentation link is not working

sorry for this, now it should be fixed https://itsjavi.com/bootstrap-colorpicker/


How to share to facebook with featured Image?

You can't choose the image of a Facebook share with vue-social-sharing, Facebook will use it's graph API to fetch the image directly on the link you used. So if you share the link "http://myproject.com/" the page http://myproject.com/ should define the following og meta tag, allowing you to choose which image will be displayed:
<meta property="og:image" content="http://myproject.com/myimage.jpg" />

more info here: https://developers.facebook.com/docs/sharing/best-practices

Can you dynamically change this inside a Single Page Application?

@kgrosvenor Sure, you just need to change the meta according to the URL of your SPA.
Here is a tutorial that covers the subject:
https://code.tutsplus.com/tutorials/adding-social-sharing-in-a-nodejs-single-page-application--cms-25530


Safir Helm chart 0.2.0 - Remove Apache httpd

Do not merge (yet)!
See:  BRF-Solutions/brf-kubernetes-services#294
Essentially, instead of apache serving (some) static files and redirecting the remaining queries to tomcat, all will be handled by tomcat. Now tomcat listens only on port 80.

lgtm

lgtm


Remove the BackendData generic argument of VaapiBackend

The BackendData generic argument of VaapiBackend has been introduced by the H.265 code, and is used exclusively by it.
It would be preferable (and more readable) to keep VaapiBackend codec-agnostic and remove that argumment. The H.265 BackendData has two members:
last_slice set and used in submit_last_slice and replace_last_slice.
va_references set in handle_picture and used in decode_slice.
It should be possible to replace them by generic associated types of the H265 stateless backend, and have the H.265 decoder manage and pass them to the needed functions.

At a first glance, I don't think V4L2 stateless actually uses these. Don't you think it's advantageous to have some space to save backend-specific data for a given codec?

If this can be avoided without complicating the API too much, then I think we should avoid it and keep the backend code simple. V4L2 could just ignore the information it doesn't need. But let me reconsider now that the H.265 code is in a more complete state.


gh-2683: Remove text from execute spring headers

Related Issue

Resolve #2683

Codecov Report

:exclamation: No coverage uploaded for pull request base (v2-alpha@f612826). Click here to learn what that means.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             v2-alpha    #2684   +/-   ##
===========================================
  Coverage            ?   65.75%
  Complexity          ?     2438
===========================================
  Files               ?      862
  Lines               ?    27122
  Branches            ?     3128
===========================================
  Hits                ?    17834
  Misses              ?     7930
  Partials            ?     1358

Continue to review full report at Codecov.

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


Current instance is not unset after error in data() on SSR

Vue version
3.2.47
Link to minimal reproduction
https://stackblitz.com/edit/github-qw7apw-58cjm8
Steps to reproduce
Click 'Trigger error in data'. it will try to load a component where there is a JS error inside the data function on the component.
Then click 'click here to see stale instance'  - it will perform a hard reload, calling getCurrentInstance() on the server and revealing that the instance was not unset.
What is expected?
I expect the current component instance to be unset if there is an error inside data.
What is actually happening?
The current component instance is not unset.
System Info
No response
Any additional comments?
This is very similar to https://github.com/vuejs/core/issues/6110 which has already been fixed. The difference is that the error happens in data instead of during rendering.
I had some troubles with our SSR setup and Pinia using the wrong instance after an error. Pinia looks for getCurrentInstance and uses that instance to inject the current pinia instance.

Similarly, throwing an error in created and then also throwing inside errorCaptured also leaves getCurrentInstance set. You can see this in the same reproducing example.

Here are two testcases that can be added to server-renderer/__tests__/render.spec.ts.
      // #7733
      test('reset current instance after error in data', async () => {
        const prev = getCurrentInstance()
        expect(prev).toBe(null)
        try {
          await render(
              createApp({
                data() {
                  throw new Error();
                },
                template: `<div>hello</div>`
              })
          )
        } catch {}
        expect(getCurrentInstance()).toBe(null)
      })
    })

    test('reset current instance after error in errorCaptured', async () => {
      const prev = getCurrentInstance()
      expect(prev).toBe(null)
      try {
        await render(
            createApp({
              errorCaptured() {
                throw new Error();
              },
              template: `<div>hello</div>`,
              created() {
                throw new Error();
              }
            })
        )
      } catch {}
      expect(getCurrentInstance()).toBe(null)
    })


cmd/compile: Biobuf duplication

There are two copes of Biobuf in the compiler, cmd/internal/obj/util.go and cmd/internal/ld/util.go. Both are in various stages of decomposition, for example 05d53165 was applied to the latter, but not the former. The former has sort of had 05d53165 applied accidentally, and now Bungetc is inconsistent, some methods check the unget buffer, others do not.

If there must be a wrapper around bufio.Buffer, then there should be at most one in the compiler.
Preferably we should be using bufio.Buffer directly everywhere.

@rsc @robpike thoughts ?

I'm all for deleting code, using bufio.Buffer everywhere sounds great.
For 1.5, however, it is a bit late.  That's a lot of lines to change after the freeze.

That's fair, but please consider at least applying https://go-review.googlesource.com/#/c/9529/

I think the original issue was resolved if we are just talking of the copies of Biobuf.
After:

@mdempsky's CL https://go-review.googlesource.com/#/c/21644 to make package cmd/internal/bio
@davecheney's CL https://go-review.googlesource.com/#/c/21720 to replace bio.Buf with bio.Reader and bio.Writer
we now use "cmd/internal/bio" in both.

However, in @davecheney's CL https://go-review.googlesource.com/#/c/21720 he noted at https://github.com/golang/go/commit/8f2edf11998a30b497586ac0e9f75036a318280a#diff-c6708995b52ed026c5e6632418f7a3b6R247 that the logic of bio.Writer was duplicated in a small internal struct. Perhaps a new issue to refactor/replace that unexported code can then be opened since the original duplication issue was solved?
Any thoughts?

I think when gri deletes the old importer code from the compiler in 1.8
this should expose a few more places where bio is not used and will
probably seal its fate.
On Fri, Aug 5, 2016 at 6:33 PM, Emmanuel T Odeke<EMAIL_ADDRESS>wrote:

I think the original issue was resolved if we are just talking of the
copies of Biobuf.
After:

@mdempsky https://github.com/mdempsky's CL https://go-review.
googlesource.com/#/c/21644 to make package cmd/internal/bio
@davecheney https://github.com/davecheney's CL https://go-review.
googlesource.com/#/c/21720 to replace bio.Buf with bio.Reader and
bio.Writer we now use "cmd/internal/bio" in both.

However, in @davecheney https://github.com/davecheney's CL
https://go-review.googlesource.com/#/c/21720 he noted at 8f2edf1#diff-
c6708995b52ed026c5e6632418f7a3b6R247
https://github.com/golang/go/commit/8f2edf11998a30b497586ac0e9f75036a318280a#diff-c6708995b52ed026c5e6632418f7a3b6R247
that the logic of bio.Writer was duplicated in a small internal struct.
Perhaps a new issue to refactor/replace that unexported code can then be
opened since the original duplication issue was solved?
Any thoughts?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/10652#issuecomment-237788472, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAAcA96EG36LQHrx837d45Elx0uv00xkks5qcvVUgaJpZM4ENOEP
.

This no longer seems to be the case:
$ git grep -i Biobuf
cmd/link/internal/ld/ldpe.go:// TODO(brainman): maybe just add ReadAt method to bio.Reader instead of creating peBiobuf
cmd/link/internal/ld/ldpe.go:// peBiobuf makes bio.Reader look like io.ReaderAt.
cmd/link/internal/ld/ldpe.go:type peBiobuf bio.Reader
cmd/link/internal/ld/ldpe.go:func (f *peBiobuf) ReadAt(p []byte, off int64) (int, error) {
cmd/link/internal/ld/ldpe.go:   sr := io.NewSectionReader((*peBiobuf)(input), input.Offset(), 1<<63-1)
cmd/vendor/golang.org/x/arch/x86/x86asm/testdata/libmach8db.c:  Biobuf bstdout;


Java archives not from Maven

This issue is meant to be a discussion on how to handle Java archives that aren't from Maven, and Syft handles in a strange manner.
Let's use this image as our example
https://hub.docker.com/r/atlassian/confluence-server/
If I scan this with Syft
syft docker:atlassian/confluence-server:latest

I end up with output that looks like this (it's a huge image, this is just a few lines)
com.atlassian.activeobjects_activeobjects-dbex                                     5.2.1                                      java-archive
com.atlassian.activeobjects_activeobjects-spi                                      5.2.1                                      java-archive
com.atlassian.analytics.analytics-client                                           8.3.0                                      java-archive
com.atlassian.analytics.analytics-whitelist                                        3.102                                      java-archive
com.atlassian.analytics_analytics-api                                              8.3.0                                      java-archive
com.atlassian.annotations_atlassian-annotations                                    4.0.0                                      java-archive
com.atlassian.applinks.applinks-basicauth-plugin                                   9.1.3                                      java-archive
com.atlassian.applinks.applinks-cors-plugin                                        9.1.3                                      java-archive
com.atlassian.applinks.applinks-oauth-plugin                                       9.1.3                                      java-archive

Looking at the dbex finding there, here is the JSON that is generated
  {
   "id": "241e9eb015975d0d",
   "name": "activeobjects-dbex",
   "version": "5.2.1",
   "type": "java-archive",
   "foundBy": "java-cataloger",
   "locations": [
    {
     "path": "/opt/atlassian/confluence/confluence/WEB-INF/lib/com.atlassian.activeobjects_activeobjects-dbex-5.2.1.jar",
     "layerID": "sha256:af99e879cc4838a22d008c5ab1892b50ccc8942b8333f1e95ac61fbff7bf8e9d",
     "annotations": {
      "evidence": "primary"
     }
    }
   ],
   "licenses": [],
   "language": "java",
   "cpes": [
    "cpe:2.3:a:activeobjects-dbex:activeobjects-dbex:5.2.1:*:*:*:*:*:*:*",
    "cpe:2.3:a:activeobjects-dbex:activeobjects_dbex:5.2.1:*:*:*:*:*:*:*",
    "cpe:2.3:a:activeobjects_dbex:activeobjects-dbex:5.2.1:*:*:*:*:*:*:*",
    "cpe:2.3:a:activeobjects_dbex:activeobjects_dbex:5.2.1:*:*:*:*:*:*:*",
    "cpe:2.3:a:activeobjects-dbex:activeobjects:5.2.1:*:*:*:*:*:*:*",
    "cpe:2.3:a:activeobjects:activeobjects-dbex:5.2.1:*:*:*:*:*:*:*",
    "cpe:2.3:a:activeobjects:activeobjects_dbex:5.2.1:*:*:*:*:*:*:*",
    "cpe:2.3:a:activeobjects_dbex:activeobjects:5.2.1:*:*:*:*:*:*:*",
    "cpe:2.3:a:atlassian:activeobjects-dbex:5.2.1:*:*:*:*:*:*:*",
    "cpe:2.3:a:atlassian:activeobjects_dbex:5.2.1:*:*:*:*:*:*:*",
    "cpe:2.3:a:activeobjects:activeobjects:5.2.1:*:*:*:*:*:*:*",
    "cpe:2.3:a:atlassian:activeobjects:5.2.1:*:*:*:*:*:*:*"
   ],
   "purl"<EMAIL_ADDRESS>   "metadataType": "JavaMetadata",
   "metadata": {
    "virtualPath": "/opt/atlassian/confluence/confluence/WEB-INF/lib/com.atlassian.activeobjects_activeobjects-dbex-5.2.1.jar:com.atlassian.activeobjects:activeobjects-dbex",
    "pomProperties": {
     "path": "META-INF/maven/com.atlassian.activeobjects/activeobjects-dbex/pom.properties",
     "name": "",
     "groupId": "com.atlassian.activeobjects",
     "artifactId": "activeobjects-dbex",
     "version": "5.2.1"
    }
   }
  },

I want to start this discussion as these particular packages aren't part of Maven, so we can't extract the name and groupId from a remote API based on a file hash for example.

It looks like there are some opportunities to attempt to guess if the name is a combined group-id/artifact-id and parse out these fields. For instance the package com.atlassian.gadgets.atlassian-gadgets-api is missing a pom.xml, however, the resolved name is the combined group-id and artifact id (see https://mvnrepository.com/artifact/com.atlassian.gadgets/atlassian-gadgets-api). In an offline capacity we could at least attempt to detect this, split it, and fix the names to be more accurate.
Additionally, based on the manifest:
  "metadata": {
    "virtualPath": "/opt/atlassian/confluence/confluence/WEB-INF/atlassian-bundled-plugins/com.atlassian.gadgets.atlassian-gadgets-api-8.1.1.jar",
    "manifest": {
      "main": {
        "Atlassian-Build-Date": "2023-06-14T08:11:33+0000",
        "Bnd-LastModified": "1686730294094",
        "Build-Jdk": "1.8.0_282",
        "Built-By": "root",
        "Bundle-Description": "Public Atlassian Gadgets API",
        "Bundle-DocURL": "https://www.atlassian.com/",
        "Bundle-License": "https://www.atlassian.com/customer-agreement/",
        "Bundle-ManifestVersion": "2",
        "Bundle-Name": "Atlassian Gadgets API",
        "Bundle-SymbolicName": "com.atlassian.gadgets.atlassian-gadgets-api",
        "Bundle-Vendor": "Atlassian",
        "Bundle-Version": "8.1.1",
        "Created-By": "Apache Maven Bundle Plugin",
        "Export-Package": "com.atlassian.gadgets;version=\"8.1.1\";uses:=\"com.atlassian.gadgets.dashboard,com.atlassian.gadgets.view,com.atlassian.plugin,io.atlassian.fugue,javax.annotation,javax.servlet.http,net.jcip.annotations\",com.atlassian.gadgets.dashboard;version=\"8.1.1\";uses:=\"com.atlassian.gadgets,com.atlassian.gadgets.plugins,com.atlassian.plugin,io.atlassian.fugue,javax.annotation,net.jcip.annotations\",com.atlassian.gadgets.dashboard.view;version=\"8.1.1\";uses:=\"com.atlassian.gadgets,com.atlassian.gadgets.dashboard,com.atlassian.gadgets.view,javax.annotation\",com.atlassian.gadgets.directory;version=\"8.1.1\";uses:=\"com.atlassian.gadgets,com.atlassian.plugin,javax.annotation\",com.atlassian.gadgets.plugins;version=\"8.1.1\";uses:=\"com.atlassian.gadgets.directory,com.atlassian.plugin,com.atlassian.plugin.web,io.atlassian.fugue,javax.annotation\",com.atlassian.gadgets.spec;version=\"8.1.1\";uses:=\"com.atlassian.gadgets,com.atlassian.gadgets.view,net.jcip.annotations\",com.atlassian.gadgets.view;version=\"8.1.1\";uses:=\"com.atlassian.gadgets,net.jcip.annotations\",com.atlassian.gadgets.opensocial;version=\"8.1.1\",com.atlassian.gadgets.opensocial.model;version=\"8.1.1\";uses:=\"net.jcip.annotations\",com.atlassian.gadgets.event;version=\"8.1.1\",com.atlassian.gadgets.feed;version=\"8.1.1\"",
        "Import-Package": "com.atlassian.gadgets;version=\"[8.1,9)\",com.atlassian.gadgets.directory;version=\"[8.1,9)\",com.atlassian.gadgets.plugins;version=\"[8.1,9)\",com.atlassian.gadgets.view;version=\"[8.1,9)\",com.atlassian.plugin,com.atlassian.plugin.util,com.atlassian.plugin.web,com.atlassian.plugin.web.conditions,com.google.common.base,com.google.common.collect,io.atlassian.fugue,javax.annotation,javax.servlet.http,net.jcip.annotations,org.apache.commons.lang3,org.apache.commons.lang3.builder",
        "Manifest-Version": "1.0",
        "Tool": "Bnd-<IP_ADDRESS>709291849"
      }
    },

We should take a closer look at the Apache Maven Bundle Plugin tool to see if we can depend on this behavior and extract this combined field from the Bundle-SymbolicName field.

Ah, so a good catch that these are actually packaged as maven artifacts, just not from maven central but rather from atlassians own maven repositories, so at least trying using groupid and artifactid is still the correct way to attempt to identify them

I also found this image that still reports a lot of the namespace package names (I tried it with this PR)
docker.io/bitnami/spark:latest


Add provider declaration

Pull Request
Description
Adds the required_providers block which declares a dependency on the AWS provider version >= 4.
Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist

[x] terraform fmt and terraform validate both work from the root and examples/ directories (look in CI for an example)
[x] Provide an updated example that utilizes newly created resources, or for more advanced additions a new example under the examples directory.
[ ] Example plan output in this PR (in lieu of CI)
[x] Docs have been added/updated (for bug fixes/features)
[x] Any breaking changes are noted in the description above
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] My code follows the style guidelines of this project
[x] Any dependent changes have been merged and published in downstream modules

Hei @nicolaei og/eller @arnhaa
Jeg klarer ikke finne ut av hvorfor test-trinnet for terraform init feiler. Det fungerer når jeg kjører kommandoen lokalt. Har dere noen tips?


26 - Update credit/copyright statement

After consultation with National Records Scotland
Economic 0, Urgency 10, strategic 8, Cost 8: Priority = 26
needs #246

Need to get clarification on what to include in the statement (Pat).

What needs to be changed and to what?

Don't know yet - waiting to hear back from Na tional Records of Scotland (see dependency)

Hi @DeniseColbert do you still need me to action this? If so maybe we could pick it up after tomorrow's scrum?

Wrote to onlineresources@ nrs 13 Dec 2023

@PatReynoldsFUG to let us know reply (when it comes in)

@PatReynoldsFUG to chase


Tool-tip for lids on beakers and bottles is inverted

Description
Tool-tip for lids on beakers and bottles is inverted. It says it has a lit when its open.
Screenshots

yeah this is my bad, the text needs to be inverted to say it doesn't have any lid or something.


lib.logger module overwrites time.time and time.clock

In pscf version 1.7.6,  pyscf.lib.logger line 82-85
if sys.version_info >= (3,6):     time.clock = time.process_time     if sys.version_info >= (3,8):         time.time = time.perf_counter
Notice, the logger module is imported whenever you import pyscf.
This changes the base functionality of the python time module and interferes with other packages which rely on time module and functionality which is not good...
A simple solution is to create a local module named time which alias functions from python time.

This has been fixed in pyscf v2.0, and there will be a release soon.


Added blog post on inclusivitiy at schools

Suggested tags:

Inclusivity
Special educational needs

Images to include:
At the top:

Before the section called: "How have the students responded?"

Ignore this, was used for recording a demo


Default login admin:admin for docker doesnt work

Hello,
I deployed papermerge through docker on a completly new server. admin:admin doesnt work for login, it tells me it is wrong. I deployed it on another server, same issue.
You got an idea how I can login anyway?
Thanks

Just updated the container and can't update at all, maybe it's linked

Don't know for sure if this is related, but I did some changes to the papermerge config file and this occurred to me as well, after recreating the containers.
I solved it by removing everything with
docker-compose rm -sv
docker volume prune

then rebuilt the images before starting the containers by running
docker-compose up -d --build

and then admin:admin worked as it should again.

Thank you, worked!

Glad I could help!
Isn't this still considered a bug though? Maybe it's already reported in another open issue but if not I suggest reopening this again.

Since this issue is still open, let me chime in.
I was also unable to login, but in my case the admin didn't even exist, so the solution was simple. Just run python3 manage.py createsuperuser inside the container.


Develop

I have created this change, as we use OracleLinux here at WilliamHill.  Due to the facter ($::operatingsystem) call looking for a result of Redhat, Centos or Amazon Linux the agent was defaulting to the following even though OracleLinux is a RedHat family member.
fail('New Relic Infrastructure agent is not yet supported on this platform')
I have added OracleLinux to the agent.pp and tested. This resolves the issue for OracleLinux.

Please check with a linter since that's making the Travis build faild.
manifests/agent.pp - ERROR: trailing whitespace found on line 92
Thanks.


⚠ Minecraft has degraded performance

In 19956af, Minecraft (https://www.minecraft.net) experienced degraded performance:

HTTP code: 200
Response time: 1352 ms

Resolved: Minecraft performance has improved in 20acbd7.


nuxt.config.ts hooks listen not working

Environment

Operating System: Windows_NT
Node Version:     v18.16.1
Nuxt Version:     3.6.5
Nitro Version:    2.5.2
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      devServer, hooks, devtools
Runtime Modules:  -
Build Modules:    -

Reproduction
https://stackblitz.com/edit/github-y8kzzg?file=nuxt.config.ts
Describe the bug
Using dev is normal

Use npm run build node .output/server/index.mjs  is not executed, hooks No longer execute
Listening http://[::]:3000

not any more...
Additional context
No response
Logs
No response

accroding to old issues, the nitro node-server preset didnot fire a listen hook when server created just because of the dev mode using a local socket. But for real usse case, developer known the difference. In some cases, we will make a patch to nitro preset to fire the exact event or just make a custom preset. It's not easy to handle websocket request for now.

Yes, I checked the official guidelines carefully. nitro preset works for this situation, but how to launch nitro preset in nuxt dev mode, that's the question.  https://nitro.unjs.io/deploy/custom-presets

This hook is only run in dev mode: https://nuxt.com/docs/api/advanced/hooks


Automatically translate WP and extensions

[X] I've read the guidelines for Contributing to Roots Projects
[X] This request isn't a duplicate of an existing request
[X] This is not a personal support request that should be posted on the Roots Discourse community

Summary
Hi,
I would like to know if it is possible to implement the functionality so that WP and extensions translate directly during a composer update?
Motivation
Facilitate the update to avoid having to go back to the backoffice to perform the translation
Thx,
Cédric

Closing since this isn't related to Bedrock itself? Might be useful to discuss on our forums: https://discourse.roots.io/


Funny bot reactions

I want to make the bot's response fun.
ボットの応答を楽しいものにしたい

Outdated bacause / slash commands can not respond to all messages. https://github.com/kawaguti/mogiri/releases/tag/2022.04.15


syntax_test failing on IE

 Issue by justinfagnani
Originally opened as dart-lang/sdk#19138

bots are red.

 Comment by sgjesse

Added AssumedStale label.


Fixes the syntax error

If you have "oc" in your master api URL it spits out the following error
/usr/bin/cns-deploy: line 414: [[: 5
172: syntax error in expression (error token is "172")

This change is

@christianh814 I am just trying to find the exact cause for the error.
In my setup This works fine
➜  ssh git:(master) oc version | grep oc | head -1 | awk '{ print $2 }' | cut -d '.' -f2
5
➜  ssh git:(master) oc version | grep oc | awk '{ print $2 }' | cut -d '.' -f2
5

Can you paste the output of
# oc version | grep oc
for future reference of how else the output can be?
Also we can add the output to test in our CI.

This is the output.
# oc version | grep oc
oc v<IP_ADDRESS>
Server https://ocp.<IP_ADDRESS>.nip.io:8443

The error happens when I connect to an installation that has oc somewhere in the name of the master.
# oc version | grep oc | awk '{ print $2 }' | cut -d '.' -f2
5
172

Using head -1 gives me the proper version
# oc version | grep oc | head -1 | awk '{ print $2 }' | cut -d '.' -f2
5

@christianh814 I can't believe I've missed this for so long! My apologies. If possible, could you rebase your change? It looks pretty straightforward, so I'd be happy to merge them. :)

This needs to be rebased.
In starting to rebase, I noticed that the current master version should already be safe for this:
It greps for "oc v" in the output of "oc version" instead of grepping for "oc".
It might still be worthwile adding the head -1 even though I'm not sure whether "oc v" can be part of a host name -- what do you think, @jarrpa ?

@christianh814 after careful reconsideration, your issue (which is #259) is already fixed by #261.
Hence closing this PR. If you feel it's still needed, please let us know. The rebase is easy. But I doubt it will be necessary. Thanks for your contribution!


onSortChange return cannot read property 'field' of undefined An error

Issue Type

[x] question

Specs
What version are you using?
^2.16.3
What browser?
Google Chrome	73.0.3683.103 (Official Build) (64-bit)
Expected Behavior
What did you expect to happen?
I want it to work sort
Actual Behavior
What actually happened?
Steps to Reproduce the Problem
Please detail your steps here
 onSortChange(params) {
      this.updateParams({
        sort: {
          type: params.sortType,
          field: this.columns[params.columnIndex].field,
        },
      });
      this.loadItems();
    },

return error Cannot read property 'field' of undefined
because params is array
[{
field: "title"
type: "asc"
}]

when click to column not work with params.sortType and params.columnIndex
sort: {
     type: params.sortType,
     field: this.columns[params.columnIndex].field,
},

How can it work properly with sever side render

hey @hoanghiep1x0 vue-good-table was enhanced to support sort by multiple columns a while back. This is why sort event now emits an array instead of object. However, the example document isn't updated to reflect this. To make this work, you simply need to update sort with an array:
onSortChange(params) {
      this.updateParams({
        sort: [{
          type: params.sortType,
          field: this.columns[params.columnIndex].field,
        }],
      });
      this.loadItems();
    },

closing.

Update your onSortChange to the following
onSortChange(params) {
this.updateParams({
sort: [{
type: params[0].type,
field: params[0].field,
}],
});
this.loadItems();
},

I too ran into this issue, the docs still reference the old format https://xaksis.github.io/vue-good-table/guide/advanced/remote-workflow.html#set-mode-to-remote

Update your onSortChange to the following
onSortChange(params) {
                this.updateParams({
                    sort: [{
                        type: params[0].type,
                        field: params[0].field,
                    }],
                });
                this.loadItems();
},

cool, it's work, why hasn't the documentation been changed

If you see something missing, you can always create a PR


RHBPMS-4241 - Throw exception when deploymentId is null

@mswiderski following up the discussion on https://github.com/droolsjbpm/jbpm/pull/577 for master.

+1


⚠ SolarOscp has degraded performance

In 96a50f5, SolarOscp ($SOLAROSCP_URL) experienced degraded performance:

HTTP code: 200
Response time: 371 ms

Resolved: SolarOscp performance has improved in 5a667e1 after 11 minutes.


build: updated deriv-api-hooks to the latest version

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
4635

Relevant Lines:
5597

💛  - Coveralls


Change the Perception Range

Thanks for your solid work on collaborative perception!
I have a question about the perception range. Is there a way to modify the perceived range （default [-32,32]）？
But if it is impossible to modify it, it doesn't matter.
I am looking forward to your answer.  Thanks a lot!

Hi @lianggroup, to change the perceived range, please change voxel_size and area_extents in Config.py:
https://github.com/coperception/coperception/blob/f8fa120b579643d141c4a5d0e8cd2b0b7ec7c913/coperception/configs/Config.py#L73-L82
When changing the range, please make sure to change the voxel_size accordingly so that the generated BEV-based pseudo-image has a length and width of 256 (e.g. (32 + 32) / 0.25 = 256).
The lines commented out showed the config of a perceived range of [-48, 48]).

OK. I see. Thanks again for your answer. This answer helped me a lot.


No regularization as default

See discussion on https://github.com/Quantco/glum/issues/728.
Checklist

[x] Added a CHANGELOG.rst entry

Sorry for the late review, but I've just noticed that this line became a bit cryptic now that the default alpha is 0. Wouldn't it be a bit clearer if instead of
elif getattr(self, "alpha", 1) == 0 and not self.alpha_search:

we did
elif hasattr(self, "alpha") and self.alpha == 0 and not self.alpha_search

?


Merge for the new enum in case of loadbalancers

See detailed description in the commit message.

this was discussed with @horadla23


Dropping more support for vts / encrypted port.

@dumbunny for the python changes.
@enisoc for the rest.

Something seems to be broken in sharded.py according to Travis. LGTM otherwise.


FileNotFoundError error when trying to execute using docker

The script run_logbert_hdfs.sh looks for
train_vocab: /root/.output/hdfs/train
vocab_path: /root/.output/hdfs/vocab.pkl
model_path: /root/.output/hdfs/logbert_mask_ratio_0.65_num_candidate_6/best_model.pth
These are not found.
root@7a564a5a1a6e:/workspace/logbert/scripts# sh run_logbert_hdfs.sh
tee: /root/.logs/hdfs_logbert_mask_ratio_0.65_num_candidate_6.log: No such file or directory
Save options parameters
Traceback (most recent call last):
File "../main_logbert.py", line 102, in
main()
File "../main_logbert.py", line 89, in main
with open(options["train_vocab"], "r") as f:
FileNotFoundError: [Errno 2] No such file or directory: '/root/.output/hdfs/train'

Please try to process data before run models sh process_bgl.sh


Upgrade MaxPool and AveragePool to handle SAME_LOWER/UPPER with dynamic sizes

Upgraded the shape inference of the MaxPoolSingleOutOp and AveragePoolOp to use the same shape helper as convolutions, merging a slightly different set of features

Conv has an optional kernel_shape, the others do not
Pool have ceil_mode, Conv does not
dilations is optional for Conv and MaxPool, but not available for AveragePool

Just like for Conv, the operations itself does not carry the non-default attribues as some (kernel size and pad) may now be dynamic values, carried as arrays of IndedExpr.
Verifiers are now also used for Max & Average Pool operations.
Because of this new support, all of the backend tests now use '-1:{-1}' pattern.
Note that the code generation scheme remains practically identical as the previous one. I did not upgrade it to the newer scheme. Just used SymbolIndexExpr for kernelShape and pads.

@jenkins-droid test this please

@jenkins-droid test this please


Credo fixes

Changelog
Bug Fixes

Fix credo warnings that cause a non-zero exit status.  You can now turn on credo --strict to stop the build when it exits non-zero if you want.

While fixing @moduledocs in those modules, also document their types and functions, so that most undocumented functions are now documented too with @doc and @spec.
Fix lines > 120 characters
Remove () from function definitons

All change requests have been addressed with fixups and rebased in.


Update plasma_applet_org.kde.plasma.qalculate_es.po

I added some missing Spanish translations

Thanks for your contribution.


feat: Apply distinct() on role arns to ensure no duplicated roles in aws-auth configmap

Description
Apply distinct() on role arns to ensure no duplicated roles in aws auth configmap
Motivation and Context

Created a cluster with a couple of eks managed node groups which shared the same iam role names

module "eks" {
  source  = "terraform-aws-modules/eks/aws"
  version = "~> 18.21"

  # other fields...

  eks_managed_node_groups = {
    "dummy_cpu" = {
      "ami_type" = "AL2_x86_64"
      "desired_size" = 1
      "instance_types" = [
        "t3.small",
      ]
      "max_size" = 1
      "min_size" = 0
      # other fields...
    }
    "dummy_gpu" = {
      "ami_type" = "AL2_x86_64_GPU"
      "desired_size" = 0
      "instance_types" = [
        "g4dn.xlarge",
      ]
      "max_size" = 1
      "min_size" = 0
      "taints" = [
        {
          "effect" = "NO_SCHEDULE"
          "key" = "nvidia.com/gpu"
          "value" = "true"
        },
      ]
      # other fields...
    }
    "dummy_testapp_cpu" = {
      "ami_type" = "AL2_x86_64"
      "desired_size" = 1
      "instance_types" = [
        "t3.small",
      ]
      "max_size" = 1
      "min_size" = 0
      # other fields...
    }
    "platform" = {
      "desired_size" = 1
      "instance_types" = [
        "t3.medium",
      ]
      "max_size" = 6
      "min_size" = 0
      # other fields...
    }
  }

  eks_managed_node_group_defaults = {
    "ami_type" = "AL2_x86_64"
    "capacity_type" = "SPOT"
    "create_iam_role" = false
    "iam_role_arn" = "arn:aws:iam::01234567890:role/eks-dummy-worker"
    # other fields...
  }

  manage_aws_auth_configmap = true
  aws_auth_roles            = var.map_roles
  aws_auth_users            = var.map_users
}

When the module creates the aws auth configmap, there will be duplicates:

# module.eks.kubernetes_config_map_v1_data.aws_auth[0] will be created
  + resource "kubernetes_config_map_v1_data" "aws_auth" {
      + data  = {
          + "mapAccounts" = jsonencode([])
          + "mapRoles"    = <<-EOT
                - "groups":
                  - "system:bootstrappers"
                  - "system:nodes"
                  "rolearn": "arn:aws:iam::01234567890:role/eks-dummy-worker"
                  "username": "system:node:{{EC2PrivateDNSName}}"
                - "groups":
                  - "system:bootstrappers"
                  - "system:nodes"
                  "rolearn": "arn:aws:iam::01234567890:role/eks-dummy-worker"
                  "username": "system:node:{{EC2PrivateDNSName}}"
                - "groups":
                  - "system:bootstrappers"
                  - "system:nodes"
                  "rolearn": "arn:aws:iam::01234567890:role/eks-dummy-worker"
                  "username": "system:node:{{EC2PrivateDNSName}}"
                - "groups":
                  - "system:bootstrappers"
                  - "system:nodes"
                  "rolearn": "arn:aws:iam::01234567890:role/eks-dummy-worker"
                  "username": "system:node:{{EC2PrivateDNSName}}"
                - "groups":
                  - "dummy"
                  "rolearn": "arn:aws:iam::01234567890:role/dummy"
                ...
            EOT
          + "mapUsers"    = <<-EOT
                - ...
            EOT
        }
      + force = true
      + id    = (known after apply)

      + metadata {
          + name      = "aws-auth"
          + namespace = "kube-system"
        }
    }

Although there may not be any effect, but it is probably undesirable to have duplicate role configuration. So this PR addresses this.

Breaking Changes

No breaking changes as it is a minor fix.
How Has This Been Tested?

[ ] I have updated at least one of the examples/* to demonstrate and validate my change(s)
[x] I have tested and validated these changes using one or more of the provided examples/* projects

[x] I have executed pre-commit run -a on my pull request

This PR is included in version 18.22.0 :tada:


The @base attribute is only used if the remote contexts list is empty.

Describe the bug
The @base attribute is only used if the remote contexts list is empty.
To Reproduce
Populate the @base attribute along with one or more entries in the remote contexts.
For example, I would expect this to result in one triple when going to RDF:
{
  "@id": "1",
  "test": "some-test",
  "@context": [
    "https://fhircat.org/fhir-r5/original/contexts/careplan.context.jsonld",
    {
      "nodeRole": {
        "@type": "@id",
        "@id": "fhir:nodeRole"
      },
      "@base": "http://hl7.org/fhir/",
      "owl:imports": {
        "@type": "@id"
      },
      "owl:versionIRI": {
        "@type": "@id"
      }
    }
  ]
}

Expected behavior
I believe the correct interpretation of this spec is that @base should be considered if the context is not a remote context (not necessarily if the remote contexts list is empty). See linked issue below.
Additional context
https://github.com/w3c/json-ld-api/issues/505

Hi,
thank you for reporting this.
<http://hl7.org/fhir/1> <http://example.com/UNKNOWN#test> "some-test" .

@kevinpeterson please, can you confirm this is the expected output?

duplicate #61

Quite, confusing, I'll go with removing @base from a remote context after <IP_ADDRESS> as suggested.


Use Kinto as Distributed Database

Hey man,
Love the project! Already learning stuff I didn't know by browsing the source code.
Just an idea, but have you thought of adding kinto as the database? People using github pages for their sites could add a contact form or w/e, without having to create and maintain a server, which is my primary goal.
Just an idea.
Thanks for the great project!

Hey, thanks for the suggestion! Kinto looks really interesting, I like it. As far as i understand it requires installing some server-side service on your server?
RSB is promoting a serverless architecture, where you can plug some existing API provided in a form of SaaS. For example Firebase, Auth0, or Reindex.
Have you checked the latest version? It's pre-configured with Firebase hosting (node run publish), and might be a good starting point to plug in Firebase or Reindex backend.


more geocode providers, not used yet

Adding support to geocoding providers Maptiler, TomTom, Photon, Nominatim and OpenCage in addition to existing Mapbox.
This is already too big change for work-in-progress. But I thought that I push it before it gets too big and unmanageable. Current geolocation provider (Mapbox) still works as before. This is dead code, i.e.: code that won't be executed yet. Enabling it will happen when all edge cases are covered and working as expected.

Looks good!


Libp2p fixes QA

https://github.com/MinaProtocol/mina/pull/5934

Move seed -> -enable-flooding
Start one of the large block producers with isolation=on
Do this for all deploys and it will ensure this doesn't break.

Investigating issues with isolation
Working on a script to get more information
Helper crash from QA net


Please help!! OTG Plugin crashing my Forge server.

OTG Plugin or Mod

[x ] OTG Mod for Forge
[ ] OTG Plugin for Spigot

OTG Version

[ ] 1.12.2_v8_r1
[ ] 1.12.2_v7_DEV_r26
[ x] 1.12.2-v6
[ ] 1.12.2-v5
[ ] 1.11.2-v8
[ ] 1.11.2-v9
[ ] 1.10.2-v21
[ ] Other - specify here

Forge or Spigot Versions
1.12.2-forge-<IP_ADDRESS>54
Server/Client Log
https://pastebin.com/Eh1aXChg
What other plugins are you running?
[List of your Mods or Plugins installed, ideally with versions]
Description
When I start up the server using a run.bat file it will run and stop with this crash.

Have you tried replicating the issue on OTG v8

Have you tried replicating the issue on OTG v8

yes i did. it still caused the same issue :(

Hey xinkalta, one of the .txt files in your world save's /OpenTerrainGenerator/ folder has been corrupted, likely the server crashed while writing to it. You can try deleting StructureData.txt and NullChunks.txt, this may lead to some structures being cut off in your world. If you have backups, you can try using an old StructureData.txt or NullChunks.txt.
For v9 i've recently added an auto-backup and restore feature to prevent this problem, a dev version is available on the OTG Discord, v9 will be released asap.


[BEAM-13972] Update documentation for run inference

Update runinfernce documentation to let users know that it is still under development.
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

R: @yeandy
R: @TheNeuralBit

Would it also be useful to add something like @experimental(since='v.2.39.0')?

@ryanthompson591 - What is the next step on this PR?

@TheNeuralBit Can you merge this PR?

Run Python_PVR_Flink PreCommit

@TheNeuralBit Can you merge this PR?

Yes I can merge when CI is green.

It looks green.  I'm getting "All checks have passed".  Was the flink test flakey?

Yes it had flaked, it just finished another run.


[release/1.4] backport: ci: run test-integration target for all runtimes

cc @mikebrow @AkihiroSuda

/retest

The Kubernetes e2e failures here do not look related to my change; the same failures occur on https://github.com/containerd/cri/pull/1600.

the e2e node issue is a well known problem should be good to merge


The IEnumerable<Object> DependencyInjectionMvcDependencyResolver.GetServices(Type serviceType) causes an NRE

The GetServices call causes an NRE to happen when nothing can be resolved from the container.
This issue is similar; coalescing an empty enumerable appears to resolve the issue.

Thank you for the contribution.
Looking at the code, I see that closedGenericType is unused - so I wonder if I should have passed that as the parameter argument to GetService instead... or if I left that-in as a reference.
I do remember (during my development of support for ASP.NET MVC) that I broke DI by returning a non-null, but empty, IEnumerable<T> instead of null.
I need to take a quick look at how ASP.NET MVC consumes the result of IEnumerable<Object> GetServices(Type serviceType) to verify your fix.
I see in the linked SimpleInjector thread that @dotnetjunkie writes (emphasis mine):

Although Simple Injector 3 contains both methods, GetAllInstances does not match the expectations of MVC, because MVC expects that method to return an empty collection in case no collection is registered.

I assume he's correct on this though.
Do you have a bug repro scenario for this issue? And do you have a unit-test or integration-test that proves this fixes it?
Thanks again!

To reproduce the issue, #17 would need to be resolved, and then visiting one of the basic routes in the SampleMvcWebApplication will demonstrate this issue. It is happening, if I recall, in the bowels of the Mvc pipeline. I will explore creating an integration test soon.

I can confirm that the closedGenericType parameter is necessary and is what needs to be passed to the GetService call, assuming you actually want to take advantage of dependency injection for supplying the providers.  Technically passing in the raw type itself works so long as you don't ever register one of the providers via dependency injection, but immediately causes a cast error if you do.

fix in fa60c05

I've just published version 5.0.0-beta01 which solves this issue. Can you give it a try to confirm it fixed it for you?
https://www.nuget.org/packages/Jehoel.AspNetDependencyInjection/5.0.0-beta01
https://www.nuget.org/packages/Jehoel.AspNetDependencyInjection.Mvc/5.0.0-beta01

I would, but I am not on that project anymore. I'm sorry.


'Issue templates' and 'Pull request template' in awesome-electron-alternatives?

Hi @sudhakar3697, how are you?
What an incredible project!
I noticed something interesting, there is a feature on GitHub called 'Issue templates' and 'Pull request Templates', this allows you to automate the process of opening and closing issues, pull-requests. Read more About issue and pull request templates
Please see this: PR: add 'Issue Template' and 'Pull request template' in awesome-electron-alternatives

img-before
img-after

Have you all ever thought about adding the Issue templates' and 'Pull request Templates' feature here to automate the process of opening and closing issues, pull-requests?

Hi @nichdemos,
Thanks for the effort, but this repo is just an informative repo. I do not think these templates would make sense for this repo containing just a markdown file.
Thank you.


Prepare release 4.27.2

[x] run unit tests in dev
[x] update version to "4.27.2" in setup.py and hxl/__init__.py
[x] check CHANGELOG
[x] install and test in clean virtualenv
[x] commit changes
[x] merge to test and push
[x] merge to main and push
[x] create libhxl PyPi release: pip install twine && python setup.py sdist && twine upload dist/libhxl-4.27.2*
[x] wait until the new release is visible on PyPi https://pypi.org/project/libhxl/4.27.2/
[x] add git tag "4.27.2"
[x] create GitHub release

https://github.com/HXLStandard/libhxl-python/releases/tag/4.27.2
https://pypi.org/project/libhxl/4.27.2/


Fix mixed received and transmitted packages with same transfer id can not be parsed correctly

When same kind of packages are send and received at the same time, the parser might not be able to parse the message since the header or the tail of the messages might belong to messages with different directions.
This PR fixes this issue.

Here is an example to reproduce the issue.

Indeed, thanks for review.


Vickel: Watch kenstrat.com

Vickel requests the watch of the watch_keyword kenstrat\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

kenstrat\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Makyen in Charcoal HQ


syntax highlighting fails on large c++ files

The files are fairly large, from about 500,000 to slightly over 1,000,000 lines. Cpptools intellisense appears to have no issue parsing these files, and i can click on "go to declaration/definition" and jump into these files. However, syntax highlighting seems to have failed completely on these files, no coloring at all, and i didn't find any process running at high cpu usage either so doesn't look like anything is even trying.

At this time, this is as designed. Certain features are turned off for files over 30MB or over 300K lines in order to reduce memory usage and be able to open those files.
Please see https://code.visualstudio.com/updates/v1_15#_large-file-support

Any file that is over 30MB or over 300K lines will now be considered a large file and will be handled specially in some circumstances. By disabling certain features for large files, for example tokenization, line guides, and wrapping or folding, we were able to optimize memory usage, in some cases, by as much as 50%. Additionally, large files will never travel to our web worker, which computes diff information, link detection, or word based completions. This helps in reducing the memory pressure on the operating system.


chore(datastore): update composeMaterial3Version

Overview [📝]
A few sentences describing the overall goals of merge request

update composeMaterial3Version
OutlinedTextField:colors method signature

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


zef: 0.9.4 -> 0.11.4

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/ugexe/zef/releases.
meta.description for zef is: "Raku / Perl6 Module Management"
meta.homepage for zef is: "https://github.com/ugexe/zef"
meta.changelog for zef is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 0.11.4 with grep in /nix/store/n77wc2sjgi58q0c5cp41m6n78z3yj40k-zef-0.11.4

directory tree listing: https://gist.github.com/15cc9347fd9e75be73faf5c3bc6a2c1d

du listing: https://gist.github.com/b437fdb6ebcf573056f8024258f7d1d7

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
zef

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/n77wc2sjgi58q0c5cp41m6n78z3yj40k-zef-0.11.4 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A zef https://github.com/r-ryantm/nixpkgs/archive/26488dcb0709e86650a5edce2e99cc63a4c424c3.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/n77wc2sjgi58q0c5cp41m6n78z3yj40k-zef-0.11.4
ls -la /nix/store/n77wc2sjgi58q0c5cp41m6n78z3yj40k-zef-0.11.4/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

zef

Maintainer pings
cc @stigtsp for testing.

@GrahamcOfBorg eval

Result of nixpkgs-review pr 112578 at 26488dcb run on aarch64-linux 1

1 package built:

zef

1 suggestion:

warning: missing-phase-hooks
installPhase should probably contain runHook preInstall and runHook postInstall.
Near pkgs/development/interpreters/rakudo/zef.nix:16:3:
   |
16 |   installPhase = ''
   |   ^


questions about code

Whether the code is incomplete or not, can you give specific methods for encrypt () and decrypt () in the Chirkov map encryption decryption section?

Added the files for both functions. Please cite my paper if you are using the script.

您好，邮件已收到


linux_install.sh has CR line endings, causing it to error

Expected Behavior
Running linux_install.sh should cause the shebang to be parsed correctly.
Current Behavior
The shebang in linux_install.sh is not parsed correctly. (error: bad interpreter: /bin/bash^M: no such file or directory)
Steps to Reproduce

Run linux_install.sh on a shell which is sensitive to line ending type, such as zsh.

Possible Solution
Save linux_install.sh with LF line endings, rather than CR LF (the DOS/Windows default) or CR (the MacOS default). This is achievable in all major text editors, alternatively dos2unix can be used.
Context
If encountered, this issue can be worked around by users without leaving the terminal by using the dos2unix utility, installable from the repos of all major distributions (and Brew on MacOS, if encountered there.)
Screenshots
Not applicable.

Hi. Thanks for your remark. I only have windows and wrote the linux code blindly without testing.
I'll try to fix this issue when I can.

I had to run the following command to fix this issue.
sed -i -e 's/\r$//' ./linux_install.sh

You are right.
This is the problem when someone codes blindfolded. I don't have a linux machine to test my codes and windows keeps changing the end of line. That's horrible.
I can accept pull requests, if you want to do that for me.

You should be able to set the file's line endings in most text editors that are worth using. Git should also be converting to LF automatically. So I'm not entirely certain what the problem is, but I have a feeling it's in your dev environment.
You can also use WSL to test Linux implementations on Windows.

I had to run the following command to fix this issue.
sed -i -e 's/\r$//' ./linux_install.sh

dos2unix is also a standard feature of most distros AFAIK, probably easier than fiddling with sed.

You are right. This is the problem when someone codes blindfolded. I don't have a linux machine to test my codes and windows keeps changing the end of line. That's horrible.
I can accept pull requests, if you want to do that for me.

The problem is that you didn't select the correct line endings when you installed git.  You should reinstall it and select the default option.

Under no circumstances should Git be converting LF-saved files to CRLF; this is simply not a thing Git does. It should only go the other way around.
Git might be preserving the old config, or the config might be saved somewhere in the repository.
Try this.
Try it from inside the repository folder as well, with and without --global. If the culprit is an override having been set wrong when the repo was created, that might do it.
You can check the line endings by cloning the repo from GitHub on your own machine and opening it in Notepad, since modern Notepad indicates line endings on the bottom.
Push comes to shove, a nuclear option would be to recreate the repo, ensuring core.autocrlf is set to true globally, and copy your code over by hand, perhaps running dos2unix on everything from a WSL2 container for good measure.
Git is also a bit of a beast to me, so I can't say for sure that this'll help, but it's something.

I have changed all crlf to lf in linux scripts and then pushed them.

Awesome, apologies for the delay in my response but I'll give it a shot soon.
It also appears I owe you an apology. Git does convert to CRLF when checking out text files when core.autocrlf is set to true. But it should also be converting them to LF again when you commit.
Are you committing from Git, or are you uploading the files right to GitHub? (No shame intended, I do that too even though I probably shouldn't...)

hi. Oh not again. I'm sorry for that, just use dos2unix to convert it. i always forget that when I add a new release lol.
I'll fix this.

Oh, no, I haven't tested it yet. I was just thanking you for the update!
It still feels like this should be worked around in your development environment, but again, I'm not you. You might want to bring this up with the Git for Windows folks, see if they can help you figure out what's gone wrong.


More summary information: broken out by facility,  Have emissions summarized by source, by facility, fuel gas volumes?

I'm putting this in the icebox for now. I think emissions summary data will be captured via ticket #142 and if users want additional disaggregated information we can consider that for future iterations. Not required at this time though.


How to access robots.txt file ?

Hi Team,
I am new in universal. How to access robots.txt file  like  we are accessing sitemap.xml?

Thanks for reporting. You are right, I overlooked this. Will update today.

@ggarg2 please check the fix, straightforward!

@patrickmichalina thanks boss. This issue is fixed.

@ggarg2 i will be updating this again to use
app.use('/robots.txt', express.static('dist/robots.txt', staticOptions));

just a heads up!

okay. Commit the code i will test it.


Add all Remaining Looks Blocks

This include Backdrop Exclusive Blocks ( I can remove them if you want)

Thanks @joaoh1!! :)


Add Azure/EntraID route for SAML

Adds support for SAML via the optional azure extra. This can be configured with the config.auth.azure options.

Wow, that was fast. Great, thanks a lot! However, I am not (yet) in a position to actually test this. We (@easybe, @tsagadar , worst case... I) will need to talk to our IT department first.

It's actually not even ready yet, it will need some fixing, I think the requests I'm trying from the msal lib are probably not right, I will need someone with an actual AzureAD account to try them out and add the proper handling.  For now this is just a button, some settings, some checks, and dependency handling.


[User Profile - Design] Design for when user has no trees on account

when a new user opens an account. there will be no data for trees. we need a design for that which will most likely have a button to go to the map / or give directions on how to use the planting / adopting feature. Will have a message about "GO PLANT SOME TREES ? GO WATER THE TREES"


diffoscope: 278 -> 279

Changes: https://diffoscope.org/news/diffoscope-279-released/

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 347231 run on x86_64-linux 1

6 packages built:

diffoscope
diffoscope.dist
diffoscope.man
diffoscopeMinimal
diffoscopeMinimal.dist
diffoscopeMinimal.man


Emoji in Swift 4

Can it be used in swift 4?

Yes. You'll get a few warnings about String, but it works fine.