Nightly Rust issue: method read has an incompatible type for trait

This compiler error is happening in nrf-softdevice/src/flash.rs:105:24
For rustc 1.53.0-nightly (42816d61e 2021-04-24)
It may be worthwhile to put the last known working nightly build in the toolchain file (even if it's commented out)

This is because nrf-softdevice works with an older version of embassy. Include the Cargo.lock from this repo in your project, it'll ensure the right embassy version is used.
I'm aware of it, was going to update nrf-softdevice soon :)

Got it, thanks. That fixed it. :)


Allow ChromaClient to be initialized outside Chroma Vector Store

While trying out Chroma integration I stumbled upon the following error:
Error: Please install chromadb as a dependency with, e.g. `npm install -S chromadb`

Even though I had already installed chromadb.
When I dug into the source, I was surprised to see that ChromaClient is being required and initialized directly here: https://github.com/hwchase17/langchainjs/blob/main/langchain/src/vectorstores/chroma.ts#L10-L15
This doesn't work well with cli tools like tsx.
Any reason why this is the case? Why can't we just pass our own initialized ChromaClient to fromDocuments? Also, this would cause an issue when ChromaDB has a different basePath and is hosted on a remote machine as currently there is no way to configure parameters that are passed to ChromaClient.
This is already being done with PineconeStore where we pass in the index initialized outside the PineconeStore itself.
Keeping the API consistent with PineconeStore, my suggestion would be to have this function signature for fromDocuments (and fromTexts too):
static fromDocuments(
  client: ChromaClient,
  docs: Document[],
  embeddings: Embeddings,
  collectionName?: string,
  url?: string
): Promise<Chroma>;

And of course remove the need to initialize ChromaClient directly and let us pass the initialized client instead.

I am currently doing it this way though I prefer using Chroma.fromDocuments instead:
const client = new ChromaClient();

const chroma = new Chroma(
  {
    collectionName,
    numDimensions,
  },
  embeddings,
  client
);

await chroma.addDocuments(docs);

hi @shripadk thanks, this was something we missed when converting the library to ESM, thanks for pointing it out, fixing it here #220

@nfcampos Thank you!


rootCA official list supported on Azure is NOT correct

CSC Root CA (names "The USERTRUST Network") is NOT supported on Azure CA TrustStores: https://learn.microsoft.com/en-us/azure/security/fundamentals/azure-ca-details?tabs=root-and-subordinate-cas-list
==> please confirm
https://learn.microsoft.com/en-us/azure/frontdoor/domain#certificate-requirements
leads to
https://ccadb-public.secure.force.com/microsoft/IncludedCACertificateReportForMSFT
long story short : the RootCA list are NOT the same on Azure docs vs SalesForce link .....
==> please update the docs immediatley and tell me which list is the correct one ?

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

ID: 2f62b7b9-f841-b6b2-4190-b0a589b41972
Version Independent ID: 4b6a351b-35e6-8865-c622-94e82d98d9a7
Content: Azure Certificate Authority details
Content Source: articles/security/fundamentals/azure-CA-details.md
Service: security
Sub-service: security-fundamentals
GitHub Login: @shlipsey3
Microsoft Alias: sarahlipsey

@ezYakaEagle442
Thanks for your feedback! We will investigate and update as appropriate.

@ezYakaEagle442
I've delegated this to @shlipsey3, a content author, to review and share their valuable insights.

I'm checking with the team and will report back.

The intent of this article is to delineate the CAs utilized by Azure’s service endpoints. It is provided so customers can anticipate the CAs encountered when establishing connections to Azure resources. This list does not, however, represent the CAs universally trusted on Azure VMs or by Azure services for validation. So this list won't match the trust anchors provided on Azure VMs or other hosted services.
Sorry for any confusion - we're going to update to hopefully provide a clarification.

#please-close


enhancement: group speech script lines together by event number

These speechscripts are shown out of order making it very hard to decipher which character says which line w/o constantly
referring to the script text file.
Is it possible to group line_01_event, line_01_character, line_01_delay(if present), etc., together so it makes it more logical to read?
If creating a new speechscript it actually these in the correct order.
The only issue is that in some cases the character speaking is not referenced within the speechscript, but still has a line.
So this would need to be compensated for as leaving the character parameter blank or not created for that event.
In any case this is more of a quality of life enhancement that I hope is not too too complex to add.

As a possible alternative to grouping. Maybe a 'move up' and 'move down' setting for them so they can be re-ordered.
not sure which is easier to implement.

I'd really like to change the entity view to be node-based eventually so that it's easier to visualise their connections - but yeah something like this would be a nice stop-gap.

I've solved this by sorting parameters alphabetically - will push up to staging when I have some more changes to go with it 👍

Impressive! Thank you!

I've just pushed this out to staging - let me know if you encounter any issues!

Not sure it's an "issue", but the speech and speechscript windows have a short pause.
Barely noticible on myI7-9700F, but it's there.
To me I don't find it an issue though . It is functional and readable.
Thank you for doing this extra work.

I might have found a minor bug.  I'm not sure if it's from #158  or sorting but when I edited a speech script event in BSP_Torrens and happened to click on the center window it refreshed the edit I just made to the previous version.
This happened even if I saved the file.     I'm going to duplicate this message on the #158 since I'm unsure which is actually at fault.


Publish this module in the Terraform registry

In order for users to more rapidly take advantage of this Terraform configuration, it should be packaged as a Terraform module (or set of modules).
https://www.terraform.io/docs/modules/publish.html
https://www.terraform.io/docs/registry/modules/publish.html
The modules should fit the best practices: https://www.terraform.io/docs/modules/index.html
https://registry.terraform.io/browse/modules?provider=packet
Modules should be reusable as the base of new projects:
terraform init --from-module=packet/openshift/packet packet-openshift
And modules should allow for reuse as dependencies in more complex projects:
module "openshift" {
  source = "packet/openshift/packet"
  version = "0.1.0"
  packet_token = "..."

  ...
}

provider "kubernetes" {
  config_path = module.openshift.kube_config
  // this does not exist, but it could be a new output ${abspath(path.root)}/auth/kubeconfig (maybe path.module)
}

Steps to publish:

[ ]  Adopt file naming conventions (main.tf, outputs.tf, variables.tf)
[ ] Ensure paths are module safe (path.module + “/assets/foo.sh“)
[ ] Ensure that all variables and outputs have a description
[x] Ensure that the README.md is present and in good shape (mentions module install and use)
[ ] All sub-modules must also adhere to the previous four bullets as if they were root modules
[ ] Include examples/ showing how to use this project as a module
[x] Rename the project (terraform-packet-openshift) (or terraform-packet-redhat-openshift) (github automatically redirects visitors and git users using the old name)
[ ] Tag the project
[ ] Publish the project: registry.terraform.io/sign-in

I've taken this effort over to https://github.com/equinix/terraform-metal-openshift-on-baremetal/issues/1
The repo is private until I have merged in the PR that incorporates many of these changes. (I don't want users to stumble upon a Packet provider in the Equinix repo until it is ready to be used on Metal).


Unescaped ampersand in river/window

(waybar:203895): Gtk-WARNING **: 09:26:25.466: Failed to set text 'Nerd Fonts - Iconic font aggregator, glyphs/icons collection, & fonts patcher - qutebrowser' from markup due to error parsing markup: Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character without intending to start an entity — escape ampersand as &

Thanks for the quick review


Add support for Actions / ActionClients / ActionServers from ActionLib

Note: This requires ROSMOD-Actor >= v0.40 ROSMOD-Actor


Should share storyboard is paused between all ControlStoryboardAction instances.

Hi @h82258652, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

Please ensure that all line endings are the same. Looking at the diff, it's hard to tell what changed.

@skendrot
Sorry, I use codemaid and turn on auto format when saving.
I will pull another request soon.

You can just push more commits your branch and the PR will update.


Show Tree-sitter grammars in grammar selector

Requirements for Adding, Changing, or Removing a Feature

Fill out the template below. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
The pull request must contribute a change that has been endorsed by the maintainer team. See details in the template below.
The pull request must update the test suite to exercise the updated functionality. For guidance, please see https://flight-manual.atom.io/hacking-atom/sections/writing-specs/.
After you create the pull request, all status checks must be pass before a maintainer reviews your contribution. For more details, please see https://github.com/atom/atom/tree/master/CONTRIBUTING.md#pull-requests.

Issue or RFC Endorsed by Atom's Maintainers

Fixes #17029 (I endorse it...)
Description of the Change

Adds an optional argument to atom.grammars.getGrammars to allow Tree-sitter grammars as well. It defaults to false to avoid any backwards compatibility issues, though I'd be fine with making it true or removing it entirely, given that Tree-sitter is now on by default for widely used languages like JS, C, etc.
Tests have not been added yet. Still need to style the grammar selector and fix my Dev mode ideally.
Alternate Designs
Aside from the above, the grammar selector element constructor also needs additional styling to mark the type of grammar. Leaving TextMate grammars as they are is fine and least confusing, but Tree-sitter grammars often share a name with these, so they look like duplicate entries. I was thinking of adding Ts before the scope, but I would ask @simurai or someone to show me how to do it (my attempt  failed miserably...).
Possible Drawbacks
Current design - making the argument a direct parameter could be awkward if we decide to add more options in future. Making it an object would future proof it.
If we enable it by default, it may break some community packages that ... handle grammars? That aren't already somewhat broken if they are ignoring Tree-sitter anyway? I'm not convinced this is an issue, so would like some thoughts on it.
Verification Process
Manually overrided it in my init script. Dev mode currently does not open for me, and I have not worked out why.
Release Notes

Show Tree-sitter grammars in grammar selector

Leaving TextMate grammars as they are is fine and least confusing, but Tree-sitter grammars often share a name with these, so they look like duplicate entries. I was thinking of adding Ts before the scope

Or write Ts out to Tree-sitter?

Although I wonder... For users that don't follow Atom development or read the Atom blog, do they know what "Tree-sitter" means? We could also be more descriptive and say that there is a normal and an "advanced" version:

@simurai Writing our the full Tree sitter is fine, but I don’t like calling it advanced; that would also be just as confusing IMO. They are already referred to as Tree-sitter in the core setting, and “advanced” is a generic word that could refer to anything, including potential future supported grammar engines.
E.g., if the Sublime grammar engine gets ported successfully (even a community package), there could end up be three types of grammar.
It would be best if there was a reliable way to tell users about Tree-sitter vs TextMate grammars, and why they’d pick one over the other. Unfortunately, they’re unlikely to go to the grammar selector package README for this. Maybe a small description somewhere on the prompt could link to an explanation?

Did not mean to close

Is it possible for the Grammar Selector to hide grammars that also have a tree-sitter variant?

@50Wliu Yes, there should be a setting for that (normal users don’t need TextMate, but there are still cases where I would want to specify the TextMate one without disabling things)

Ohh.. It just occurred to me that JavaScript (Tree-siter) might also be confusing because it looks like it's some sort of "flavor" of JavaScript and not the parsing system used. How about having green badges that just say Tree-sitter in front of the scopes. I'll push that.

Maybe a small description somewhere on the prompt could link to an explanation?

That would be helpful. Not sure how to describe it in the very small space left. Without, users that are curious would have to google it and hopefully find a blog post like https://github.blog/2018-10-31-atoms-new-parsing-system/.

That would be helpful. Not sure how to describe it in the very small space left.

Can those Tree-sitter badges have alt-text added on hover?

Can those Tree-sitter badges have alt-text added on hover?

Yes, here with a title attribute:

Does the following description make sense?
A fast parsing system with improved syntax highlighting, code folding, syntax-aware selection.

My suggestion:
(Recommended) A faster parser with improved syntax highlighting & code navigation support.

Shorter and, in case the user can't tell from the listed improvements, explicitly says it's recommended.

OK, couple of outstanding issues I think can be fixed in this PR:

Order of TS and TM grammars is random when both have same name. E.g., C has TS first, but C++ has TM first.
Choosing TM grammar does not actually choose the TM grammar.

Added specs for most behaviour (aren't checking the order of Tree-sitter / TextMate when both show).
The specs are quite rigid, expecting specific ordering and nesting of the DOM nodes, but they should not be flakey.
I also refactored getting the list node into it's own function for some quality-of-life improvement.

@simurai The button text is smaller than the label text

I'm using a different monitor now, and the high pixel density means app components look really tiny, especially text. In the image, the list items are 15px, but the badge text is 12px. Would it be possible to make the badge text inherit from the list by default?

Hey! 👋
We have recently started using prettier and this has caused major style changes on the Atom JS codebase (you can check the related PR).
This is good news: now the Atom code is more consistent and it's much easier to re-format the code to follow the codestyle (now you only need to run script/lint --fix).
This change caused conflicts on your PR that we have automatically solved, hope you don't mind 😄
With ❤, the Atom team.

I've been considering returning Tree-sitter grammars by default, or explicit opt in. I've gone with by default, because they are supposed to be the preferred grammar now. There were a couple of hitches with other parts of GrammarRegistry that expose grammars, but I think everything works (the specs pass).
The failing specs seem completely unrelated; the mac build failed to load, throwing
[command]/bin/bash --noprofile --norc /Users/vsts/agent/2.153.1/work/_temp/d77d45f0-4dd1-4d72-a48e-8ec869406f78.sh
internal/modules/cjs/loader.js:596
    throw err;
    ^

Error: Cannot find module 'colors'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:594:15)
    at Function.Module._load (internal/modules/cjs/loader.js:520:25)
    at Module.require (internal/modules/cjs/loader.js:650:17)
    at require (internal/modules/cjs/helpers.js:20:18)
    at Object.<anonymous> (/Users/vsts/agent/2.153.1/work/1/s/script/test:5:1)
    at Module._compile (internal/modules/cjs/loader.js:702:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:713:10)
    at Module.load (internal/modules/cjs/loader.js:612:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:551:12)
    at Function.Module._load (internal/modules/cjs/loader.js:543:3)

I think this is ready to be reviewed and tried in beta.

The CI failure is really odd.

Okay, I merged master into this branch after merging #19580, so hopefully we get better behavior out of the tests.

Before we merge, I'm going to spend some time seeing if we can actually return tokens from the methods on grammar. The current shims won't break the current API, but I also think they don't really perform as we advertise in the documentation, which could be surprising. Let's see what I can come up with.

Sorry. After digging into this I really don't think we can sanely shim tokenizeLine. It's intended to carry the state of the first-mate parser across calls, and my scan of all the package code out there shows that people are indeed using it. I think we should avoid returning objects that violate the documented interface of Grammar without an explicit option. And maybe we leave that option undocumented for now. I can take care of making the relevant changes.

OK, it's now set back up to require opt in for Tree-sitter. The change took a few tries, because there are a couple of places grammars are exposed, and it wasn't consistent to begin with (see forEachGrammar, which exposed TS grammars for the auto assignment methods).

Thanks so much! It will be really nice to be able to select these grammars via the UI. Really, the functionality was incomplete without this.

A nice next step would be to start thinking about how we can expose the unique capabilities of TreeSitter grammars and language modes in our official API.

Nice work @Aerijo and @simurai. Looks great.


Transaction retries and annotations

@ddietterich back to you, I think I addressed most of your comments. I tried to remove the linked hash map but ended up needing the map functionality


setup.py issue for tensorflow (known issue -- to keep track)

This is just to keep track that the current setup.py throws an error when trying to install tensorflow:
No local packages or working download links found for tensorflow>=2.0
The workaround is something like:
pip install --upgrade tensorflow
And actually in a cluster environment you will usually want something like:
module load ml/tensorflow/2.1.0-py37

This seems to be working now, at least in virtual env's. Can we close or if the issue persists should we just add this to the README? @realmarcin

Closing this issue as deprecated in the new version of Embiggen. Please feel free to reopen as need be.


FatalErrorException in Container.php line 702

Hi there,
I installed your app according your Installation notes. Front-end works fine, but when I go to /public/admin/ I get this error: FatalErrorException in Container.php line 702: Maximum function nesting level of '100' reached, aborting!
Stacktrace: http://pastebin.com/RmNYQxpg
What might be wrong?

Hi,
I think it's a xdebug issue. Try change max value or remove it.

Thanks a lot. It helped to resolve the issue.


Contact diary: Add icons of the kind of meeting

It would be great to have icons, indicating

if masks were used, by how many participants,

whether distance was kept.

moreover an icon for a cluster event would be helpful.

Internal Tracking ID: EXPOSUREAPP-3034

Maybe you would like to comment on #305 since this is nearly the same idea.

Something like this will be added with version 1.14 (Source):

Sie können zu jedem Eintrag angeben, unter welchen Umständen die Begegnung stattfand.  Sollten Sie sich tatsächlich anstecken, können diese Angaben dem Gesundheitsamt bei der Nachverfolgung möglicher Infektionsketten helfen.

@ouboub
Do you want to leave this issue open (because in-app, there are no icons) or is the current implementation sufficient and you can close this issue?

"T" == Tim  @.***> writes:

@ouboub
Do you want to leave this issue open (because in-app, there are no
icons) or is the current implementation sufficient and you can close
this issue?

@Tim:
a question: did you try out, any of the other contact diaries, like
cluster diary or cornonika (Kontakt Tagebuch has been removed
unfortunately)??
Don't you think the corona warn app is very hm basic concerning the
contact diary?
I do and that is why I would like to keep the issue open, if nobody
disagrees.

@ouboub
First of all, sorry, your issue here is not only about masks but also reg. cluster situations.
Second, yes I used "Dein Tagebuch" until CWA 1.14 has been released. It has much more features than CWA... But, I think, with version 1.14 CWA did a great jump in regard to the functions of the diary.

"T" == Tim  @.***> writes:

@ouboub
First of all, sorry, your issue here is not only about masks but also reg. cluster situations.

Right since I think that is important.

Second, yes I used "Dein Tagebuch" until CWA 1.14 has been released.

Thanks for pointing that one out, seems even better than the one I
mentioned, however you cannot delete single meetings, if you create one
by mistake say

It has much more features than CWA... But, I think, with version 1.14
CWA did a great jump in regard to the functions of the diary.

It is better than nothing but still not enough.  That of course seems a
decision taken by Apple not by the team.
However, I have the feeling sometimes, that at the end these feature
protect your data but not necessarily your health!


Next and Previous Arrow

Could the component have its labels (currently hard-coded to Next and Previous) injectable, by some prop?
I need to translate some buttons.

You could override the prevArrow and nextArrow props with components of your making, like this:
class NextButton extends React.Component {
render() {
return (
<button {...this.props}>{this.props.nextText}
);
}
}
class PrevButton extends React.Component {
render() {
return (
<button {...this.props}>{this.props.prevText}
);
}
}
sliderSettings = {
arrows: true,
prevArrow: PrevButton,
nextArrow: NextButton
};
<Slider {...sliderSettings}>
{ slides }

Oh, now I see, thank you


WIP: Deprecating access_ssdl argument

Ref discussion related to #540 and other issues
Proposing to deprecate the access_ssdl input argument in favor of classification and rep_include.
This PR does:

Deprecate access_ssdl argument, introduces classification and rep_include arguments
This is a follow-up from non-merged PR https://github.com/equinor/fmu-dataio/pull/320 which was only partially made
Stops modifying the config during runtime. Read it, then use the elements from it further.
Moves some of the logic related to the config from dataio.py to global_configuration.py.

Might not be merged as-is, but perhaps elements or principles from it will be useful.
Purpose:

Make the classification argument a bit more intuitive and readable
Remove impression that this is something specific to SSDL when it is in fact not.

History:
Initially, the access.ssdl block was specific to SSDL and inherited from early versions of metadata when SSDL defined the FMU metadata (largely). Then, the access.ssdl.access_level was used also for access control outside SSDL (i.e. Sumo). Then, we decided to deprecate it - but only go half-way there, because of multiple challenges. Essentially, it stopped after adding access.classification to outgoing metadata (temporarily synchronized with access.ssdl.access_level.
The (milestone) goal should be to remove access.ssdl.access_level completely in favor of access.classification and then us this also in the config.
In short, we want to go from this:
exp = ExportData(access_ssdl={"access_level": "internal", rep_include=False})

...to this:
exp = ExportData(classification="internal", rep_include=False)

And we want to do the same in the config, i.e. from:
access:
  ssdl:
    access_level: internal
    rep_include: True

to:
access:
  classification: internal
  ssdl:
    rep_include: True

Complicating factors:

We still need the rep_include parameter, so the access.ssdl block will remain for now
We allow missing or non-valid config, and must handle that throughout fmu-dataio. This complicates things.
We make changes to the config during runtime, which complicates things. (Changed in this PR.)
We allow arguments to be given both to the initialization of ExportData and to the call to .generate_metadata(). This makes it a bit tricky to keep things in synch, particularly when we change things as we check them. (And then check them again later.)

Todo:

[x] Deprecate access_ssdl from input argument and from config (not discontinue it)
[ ] Make support for using access.classification also in the config (and test it).
[ ] Rewrite tests to primarily use the updated pattern (classification)
[x] Stop altering the config during runtime. Parse it, check it, then just read it.
[ ] Discussion, and some more discussion

⚠ This is work in progress, and not ready for merging. Perhaps it will never be.

Auch, major changes in main since this morning so some huge conflicts. Will have a look.

Just sketching at this point, but some sort of pattern is perhaps starting to emerge

ref discussion @tnatt
Possible "carve-out" from this:

Better handling of config.
Explicitly set the keys we need from config into class variables (Pydantic objects??), then not carry config further.

@tnatt: rep_include does not have to be in the config, it will always be false as default anyway. I agree.

Replaced by #628


Comments inside expression causing unexpected formatting

When using the CQL Formatter on the following CQL Library:
library Test version '0.0.000'

using QDM version '5.3'

parameter "Measurement Period" Interval<DateTime>

context Patient

define "Test":
	// some coment here
	 exists (
		 ["Laboratory Test, Performed"]E
		 	where E.result > @2016-05-06
	 )

results in:
library Test version '0.0.000'

using QDM version '5.3'

parameter "Measurement Period" Interval<DateTime>

context Patient

define "Test":

	// some coment here
	  exists (["Laboratory Test, Performed"]E where E.result > @2016-05-06 )

Similarly, multi line comments have the same issue.
library Test version '0.0.000'

using QDM version '5.3'

parameter "Measurement Period" Interval<DateTime>

context Patient

define "Test":

		/* some coment here
			and another comment here
			and one more
		 */
	  exists (
			["Laboratory Test, Performed"]E
				where E.result > @2016-05-06
		)

results in:
library Test version '0.0.000'

using QDM version '5.3'

parameter "Measurement Period" Interval<DateTime>

context Patient

define "Test":

		/* some coment here
			and another comment here
			and one more
		 */
	   exists (["Laboratory Test, Performed"]E where E.result > @2016-05-06 )

@brynrhodes  and @c-schuler:
Pull Request https://github.com/cqframework/clinical_quality_language/pull/211 was pushed to correct this issue. However, the comment in the pull request is not consistent with what is in CQL if we understand the comment correctly. The comment in the pull request is below.
Comment support is limited (comments within expressions will cause syntax issues - keep comments above or below expressions).

We do not understand what is intended by this comment, but it seems to imply that comments internal to a definition are not supported. If this is the case, then it is not consistent with the CQL standard.
In addition, we have found that the use of a comments provided internally in a definition will sometimes cause an error to return even when the CQL syntax is correct. For example, when the formatter operates on this code...
library Test version '0.0.000'

using QDM version '5.3'

valueset "Dapsone and pyrimethamine": 'urn:oid:2.16.840.1.113883.3.464.1<IP_ADDRESS>2' version 'urn:hl7:version:eCQM%20Update%202017-05-05'
valueset "Leucovorin": 'urn:oid:2.16.840.1.113883.3.464.1<IP_ADDRESS>5' version 'urn:hl7:version:eCQM%20Update%202017-05-05'

parameter "Measurement Period" Interval<DateTime>

context Patient

define "CD4+ Count With Results and Medications 2":
                ["Medication, Order": "Leucovorin"] MOL
                                with ["Medication, Order": "Dapsone and pyrimethamine"] DapsoneOrder

                                // fdafds this statement
                                                such that DapsoneOrder.authorDatetime occurs 1 days or less after MOL.authorDatetime
                                with ["Medication, Order": "Dapsone and pyrimethamine"] MODP
                                                such that MODP.authorDatetime occurs 1 day or less after MOL.authorDatetime
                                where MOL.authorDatetime is not null

...the following output is received:
Encountered syntax errors:
[14:2]: mismatched input 'with' expecting {<EOF>, '<', '>', 'define', 'context', 'in', 'is', 'as', 'properly', 'between', 'and', '<=', '>=', '=', '!=', '~', '!~', 'contains', 'or', 'xor', 'implies', '|', 'union', 'intersect', 'except', 'less than', 'more than', 'on or', 'before', 'after', 'starts', 'ends', 'occurs', 'same', 'includes', 'during', 'included in', 'within', 'meets', 'overlaps', NUMBER}

Input CQL:
null

On the other hand, when the CQL expression is run through the CQL-to-ELM translator, it passes validation.

Addressed in v1.2.12-SNAPSHOT.


[Publish] Add public documentation for GCS to Spanner teamplate

Done https://cloud.google.com/dataproc-serverless/docs/templates/storage-to-spanner


How auto transfer XDAG

Transfers XDAG to other wallet address，./xdag -i then xfer S A，
that's the only to do it.？Is it possible to not enter xdag>?

Currently, yes, this is the only way to transfer.


Fix external renderer

as title

demos:

https://codeberg-test.org/6543/reStructuredText_ReST
https://codeberg-test.org/6543/asciidoc-test

might be unrelated, but the demo links you provided give a 500 Internal Server Error

@noerw no its related, external renderer are broken, ot test clome mentioned repos to your test instamce and setup restructured text renderer.


Can't install on OSX

Any ideas how to resolve this error?
Installing globally without sudo fails as well.
➜  sms git:(inline-style-fix) sudo npm install -g requiresafe

><EMAIL_ADDRESS>install /usr/local/lib/node_modules/requiresafe/node_modules/git-validate
> node bin/install

fs.js:500
  return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
                 ^
Error: EACCES, permission denied '/usr/local/.git/hooks/pre-commit'
    at Error (native)
    at Object.fs.openSync (fs.js:500:18)
    at Object.fs.writeFileSync (fs.js:1099:15)
    at Object.exports.installHooks (/usr/local/lib/node_modules/requiresafe/node_modules/git-validate/lib/utils.js:248:12)
    at Object.<anonymous> (/usr/local/lib/node_modules/requiresafe/node_modules/git-validate/bin/install.js:3:7)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Function.Module.runMain (module.js:501:10)
npm ERR! Darwin 14.5.0
npm ERR! argv "node" "/usr/local/bin/npm" "install" "-g" "requiresafe"
npm ERR! node v0.12.7
npm ERR! npm  v2.11.3
npm ERR! code ELIFECYCLE

npm ERR<EMAIL_ADDRESS>install: `node bin/install`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node bin/install'.
npm ERR! This is most likely a problem with the git-validate package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node bin/install
npm ERR! You can get their info via:
npm ERR!     npm owner ls git-validate
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/chrisfosterelli/workspace/memoryleaf/sms/npm-debug.log
➜  sms git:(inline-style-fix)

What version of OS X is this?

@bear 10.10.5

thanks, we are looking into this

@chrisfosterelli if you try and npm i requiresafe -g outside of a directory with a .git in it does it work?

@evilpacket Nope, has the same behaviour

@chrisfosterelli Thanks. We'll track down the issue. We have a bit of an idea.

Not sure if this is relevant, but it appears to be trying to write to /usr/local/.git/pre-commit but /usr/local/.git is not root-writable so that might explain the permission issue.
➜  workspace  ls -al /usr/local/
total 96
drwxrwxr-x  23 root             admin    782 21 Jul 10:24 .
drwxr-xr-x@ 12 root             wheel    408  6 May 22:19 ..
drwxr-xr-x  14 chrisfosterelli  admin    476  6 May 22:19 .git
-rw-r--r--   1 chrisfosterelli  admin    301  6 May 22:19 .gitignore
-rw-r--r--   1 chrisfosterelli  admin    261  6 May 22:19 .yardopts
-rw-r--r--   1 chrisfosterelli  admin   3160  6 May 22:19 CODEOFCONDUCT.md
-rw-r--r--   1 chrisfosterelli  admin   1103  6 May 22:19 CONTRIBUTING.md
drwxr-xr-x  23 chrisfosterelli  admin    782 26 Sep 12:52 Cellar
-rw-r--r--   1 chrisfosterelli  admin   1241  6 May 22:19 LICENSE.txt
drwxr-xr-x  11 chrisfosterelli  admin    374 14 Aug 10:55 Library
-rw-r--r--   1 chrisfosterelli  admin   2064  6 May 22:19 README.md
-rw-r--r--   1 chrisfosterelli  admin  23781  6 May 22:19 SUPPORTERS.md
drwxr-xr-x  89 chrisfosterelli  admin   3026 26 Sep 12:52 bin
drwxr-xr-x   5 chrisfosterelli  admin    170 24 Jun 14:36 etc
drwxr-xr-x   6 chrisfosterelli  admin    204 22 Jun 10:39 foreman
drwxr-xr-x  22 root             wheel    748 17 Feb  2015 go
drwxr-xr-x   7 65535            65535    238 22 Jun 10:39 heroku
drwxr-xr-x  27 chrisfosterelli  admin    918 24 Jun 14:36 include
drwxr-xr-x  53 chrisfosterelli  admin   1802 24 Jun 14:36 lib
drwxr-xr-x  23 chrisfosterelli  admin    782 26 Sep 12:52 opt
drwxr-xr-x  10 chrisfosterelli  admin    340 21 Jul 10:24 sbin
drwxr-xr-x  14 chrisfosterelli  admin    476 26 Aug 15:34 share
drwxr-xr-x   3 chrisfosterelli  admin    102 24 Jun 14:36 var
➜  workspace

If I go into that directory and run git remote -v it looks like the .git directory is being initialized and setup by homebrew.

@chrisfosterelli just published 2.0.3 which I think will resolve the issue

@evilpacket Works great now! Thanks guys!


 Would be better to get the --help output pointing out what is missing
http://click.pocoo.org/5/options/#values-from-environment-variables

Done 👍


Update Links & Go Module Path to New Github Org: Svix

We'll want a new release before we start telling people to use github.com/svix/svix-libs in go as modules are pretty particular about module declarations matching go get paths.

Could you please change the title to be more descriptive?
Other than that, ready to be merged?

Could you please change the title to be more descriptive?
Other than that, ready to be merged?

Done, ready to merge


Firebase 6.16.0 + Unity 2020.1 + UPM = not generating the AndroidManifest.xml

[REQUIRED] Please fill in the following fields:

Unity editor version: 2020.1.7f1
Firebase Unity SDK version: 6.16.0
Source you installed the SDK: UPM
Problematic Firebase Component: App
Other Firebase Components in use: Auth, Database
Additional SDKs you are using: None
Platform you are using the Unity editor on: Windows
Platform you are targeting: Android
Scripting Runtime: Mono

[REQUIRED] Please describe the issue here:
With the latest 6.16 update a lot of my issues and workarounds to get firebase working on android have been cleared up but one thing remains, if I use the UPM to install Firebase, I can't get the androidManifest to generate which means that there is no
/Plugins/Android/Firebase* being generated either
Steps to reproduce:
Have you been able to reproduce this issue with just the Firebase Unity quickstarts (this GitHub project)? Yes
What's the issue repro rate?100%
What happened? How can we make the problem occur?

Make sure that google-services.json is present inside of assets folder.

Add the scoped registries to the manifest.json

"scopedRegistries": [
    {
      "name": "Game Package Registry by Google",
      "url": "https://unityregistry-pa.googleapis.com",
      "scopes": [
        "com.google"
      ]
    }
  ]

Then install the Firebase App, Auth, whatever, modules via UPM.
Verify that after all resolutions are complete, it is still missing the AndroidManifest as well as everything inside of Plugins/android/Firebase*
StreamingAssets folder is also not created

I notice that when I go import the sdk via unitypackage, that the Plugin/Android/Firebase structure is present, but not from using the UPM. Is there a step I'm missing here?
Additonally, is there anything I can do, when on Android, to stop the iOS.Extensions.Xcode from getting installed?
I'd like to stop getting the Assembly 'Packages/com.google.firebase.app/Firebase/Editor/Firebase.Editor.dll' will not be loaded due to errors: Unable to resolve reference 'UnityEditor.iOS.Extensions.Xcode'. Is the assembly missing or incompatible with the current platform? Error.

Hi @bauervision
I found that Unity 2020 is getting more and more aggressive in searching any reference to UnityEditor.iOS.Extensions.Xcode in the assemblies.  I think we removed all of the reference from class properties and function parameters a while ago but I did occasionally saw the error message you mentioned on Windows.
This usually goes away after I restarted Unity.  Could you try to restart Unity and see if that helps?
Shawn

Yep, a restart did in fact generate the folder structure, and removed the Xcode error.
All errors are now cleared, and it is deploying successfully to the phone.
Maybe we can throw in a pop up that tells the user Unity needs to restart after Firebase sdk is installed? @chkuang-g

Actually... @chkuang-g I'm now getting a Unity crash when I try to Play in the editor.
Deploying to the device went flawlessly, but continuing development and testing in the editor proves impossible. Bug has been reported to Unity as well.

FYI, there is an issue with Database in editor https://github.com/firebase/quickstart-unity/issues/807
The temporary fix is to create the proper folder as mentioned by the folder.


Check if the Upgradeability functionality works in the Smart Contracts in the T network

Check if the Upgradeability functionality works in the Smart Contracts in the T network.
For this task, it is needed to perform the following steps:

Check the actual data in the Smart Contracts (DIDs, roles, public keys and hashes)
Run the update_logic script.

Note: If the script does not work, we should fix it.

Execute the examples to test the persistence of the data (DIDs, roles, public keys and hashes)

I tries to execute just that script but i got this:
Compiling your contracts...
===========================
> Everything is up to date, there is nothing to compile.

Starting migrations...
======================
> Network name:    'red-t-identity-admin'
> Network id:<PHONE_NUMBER>8
> Block gas limit: 700000000 (0x29b92700)

6_update_logic.js
=================

Error:  *** Deployment Failed ***

"Eidas" has no address. Has it been deployed?

    at Object.link (/home/anthares/Projects/alastria/alastriaID-truffle-contracts/node_modules/truffle/build/webpack:/packages/deployer/src/linker.js:29:1)
    at /home/anthares/Projects/alastria/alastriaID-truffle-contracts/node_modules/truffle/build/webpack:/packages/deployer/src/actions/link.js:5:1
    at Migration._deploy (/home/anthares/Projects/alastria/alastriaID-truffle-contracts/node_modules/truffle/build/webpack:/packages/migrate/Migration.js:68:1)
    at Migration._load (/home/anthares/Projects/alastria/alastriaID-truffle-contracts/node_modules/truffle/build/webpack:/packages/migrate/Migration.js:55:1)
    at Migration.run (/home/anthares/Projects/alastria/alastriaID-truffle-contracts/node_modules/truffle/build/webpack:/packages/migrate/Migration.js:171:1)
    at Object.runMigrations (/home/anthares/Projects/alastria/alastriaID-truffle-contracts/node_modules/truffle/build/webpack:/packages/migrate/index.js:150:1)
    at Object.runFrom (/home/anthares/Projects/alastria/alastriaID-truffle-contracts/node_modules/truffle/build/webpack:/packages/migrate/index.js:110:1)
    at runMigrations (/home/anthares/Projects/alastria/alastriaID-truffle-contracts/node_modules/truffle/build/webpack:/packages/core/lib/commands/migrate.js:264:1)
    at /home/anthares/Projects/alastria/alastriaID-truffle-contracts/node_modules/truffle/build/webpack:/packages/core/lib/commands/migrate.js:231:1
Truffle v5.1.53 (core: 5.1.53)
Node v12.18.2
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>updateRedT: `truffle migrate --f 6 --to 6 --network=red-t-identity-admin`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>updateRedT script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/anthares/.npm/_logs/2021-07-05T09_57_31_630Z-debug.log

Is it necessary to execute the rest of the scripts in order to execute this @VictorNS69 ?

Hi!
I made some changes in the script (https://github.com/alastria/alastriaID-truffle-contracts/commit/eae5812e2ed637278ec456844dc8a50a9d69cf20). These changes worked locally, so you can work on the branch I created, along with the T network.
I still have some questions about this script. Maybe  @nefera606 can answer some of them.

At the moment, neither Eidas, nor AlastriaIdentityIssuer, nor AlastriaIdentityServiceProvider are being deployed. What happens if we need to iterate any of them?
Do we want to create another json file with the updated address or we just overwrite the actual one (addresses.json)?
If only one of the contracts is modified, they will all be deployed again, right? Is this the way you want it to work?

Also, I'm not sure if all the changes I made are correct, so please @nefera606 do not hesitate to tell me which aspects we need to correct.

Mmmm looks like the node is having problems:
Compiling your contracts...
===========================
> Everything is up to date, there is nothing to compile.

Starting migrations...
======================
> Network name:    'red-t-identity-admin'
> Network id:<PHONE_NUMBER>8
> Block gas limit: 699999958 (0x29b926d6)

6_update_logic.js
=================
Error [ERR_UNHANDLED_ERROR]: Unhandled error. ({
  code: -32603,
  message: 'socket hang up',
  data: { originalError: { code: 'ECONNRESET' } },
  stack: 'Error: socket hang up\n' +
    '    at connResetException (internal/errors.js:609:14)\n' +
    '    at Socket.socketOnEnd (_http_client.js:453:23)\n' +
    '    at Socket.emit (events.js:327:22)\n' +
    '    at endReadableNT (_stream_readable.js:1221:12)\n' +
    '    at processTicksAndRejections (internal/process/task_queues.js:84:21)'
})
    at Web3ProviderEngine.emit (events.js:304:17)
    at /home/anthares/Projects/alastria/alastriaID-truffle-contracts/node_modules/@trufflesuite/web3-provider-engine/index.js:57:14
    at afterRequest (/home/anthares/Projects/alastria/alastriaID-truffle-contracts/node_modules/@trufflesuite/web3-provider-engine/index.js:151:21)
    at /home/anthares/Projects/alastria/alastriaID-truffle-contracts/node_modules/@trufflesuite/web3-provider-engine/index.js:176:21
    at /home/anthares/Projects/alastria/alastriaID-truffle-contracts/node_modules/@trufflesuite/web3-provider-engine/index.js:238:9
    at /home/anthares/Projects/alastria/alastriaID-truffle-contracts/node_modules/async/internal/once.js:12:16
    at replenish (/home/anthares/Projects/alastria/alastriaID-truffle-contracts/node_modules/async/internal/eachOfLimit.js:61:25)
    at /home/anthares/Projects/alastria/alastriaID-truffle-contracts/node_modules/async/internal/eachOfLimit.js:71:9
    at eachLimit (/home/anthares/Projects/alastria/alastriaID-truffle-contracts/node_modules/async/eachLimit.js:43:36)
    at /home/anthares/Projects/alastria/alastriaID-truffle-contracts/node_modules/async/internal/doLimit.js:9:16
    at end (/home/anthares/Projects/alastria/alastriaID-truffle-contracts/node_modules/@trufflesuite/web3-provider-engine/index.js:217:5)
    at Request._callback (/home/anthares/Projects/alastria/alastriaID-truffle-contracts/node_modules/@trufflesuite/web3-provider-engine/subproviders/rpc.js:36:21)
    at self.callback (/home/anthares/Projects/alastria/alastriaID-truffle-contracts/node_modules/request/request.js:185:22)
    at Request.emit (events.js:315:20)
    at Request.onRequestError (/home/anthares/Projects/alastria/alastriaID-truffle-contracts/node_modules/request/request.js:877:8)
    at ClientRequest.emit (events.js:327:22)
    at Socket.socketOnEnd (_http_client.js:453:9)
    at Socket.emit (events.js:327:22)
    at endReadableNT (_stream_readable.js:1221:12)
    at processTicksAndRejections (internal/process/task_queues.js:84:21)

Ok after the node is up this is the result:
Compiling your contracts...
===========================
> Everything is up to date, there is nothing to compile.

Starting migrations...
======================
> Network name:    'red-t-identity-admin'
> Network id:<PHONE_NUMBER>8
> Block gas limit: 699999958 (0x29b926d6)

6_update_logic.js
=================

Error: Eidas has not been deployed to detected network (network/artifact mismatch)
    at Object.checkNetworkArtifactMatch (/home/anthares/Projects/alastria/alastriaID-truffle-contracts/node_modules/truffle/build/webpack:/packages/contract/lib/utils/index.js:249:1)
    at Function.deployed (/home/anthares/Projects/alastria/alastriaID-truffle-contracts/node_modules/truffle/build/webpack:/packages/contract/lib/contract/constructorMethods.js:84:1)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at module.exports (/home/anthares/Projects/alastria/alastriaID-truffle-contracts/migrations/6_update_logic.js:36:3)
    at Migration._deploy (/home/anthares/Projects/alastria/alastriaID-truffle-contracts/node_modules/truffle/build/webpack:/packages/migrate/Migration.js:73:1)
    at Migration._load (/home/anthares/Projects/alastria/alastriaID-truffle-contracts/node_modules/truffle/build/webpack:/packages/migrate/Migration.js:55:1)
    at Migration.run (/home/anthares/Projects/alastria/alastriaID-truffle-contracts/node_modules/truffle/build/webpack:/packages/migrate/Migration.js:171:1)
    at Object.runMigrations (/home/anthares/Projects/alastria/alastriaID-truffle-contracts/node_modules/truffle/build/webpack:/packages/migrate/index.js:150:1)
    at Object.runFrom (/home/anthares/Projects/alastria/alastriaID-truffle-contracts/node_modules/truffle/build/webpack:/packages/migrate/index.js:110:1)
    at runMigrations (/home/anthares/Projects/alastria/alastriaID-truffle-contracts/node_modules/truffle/build/webpack:/packages/core/lib/commands/migrate.js:264:1)
    at /home/anthares/Projects/alastria/alastriaID-truffle-contracts/node_modules/truffle/build/webpack:/packages/core/lib/commands/migrate.js:231:1

Could be a problem with the inheritance from the Eidas lib, let us review the Eidas update logic in the script

We have also detected that it works on my computer, but not on @anthares101's computer. What can this be due to? I did the previous deployments, is that why?

I was able to execute the process with no errors in my computer but looks like the contracts are not getting updated. The process i followed:

npm run compile
npm run migrateToRedT
npm run initRedT
git checkout addresses.json
npm run updateRedT

Im not sure about stet 4, maybe im not supposed to do that but i understood that was necessary to avoid problems.

After some @VictorNS69 feedback looks like i was updating a non upgradable contract so i tried again modifying the AlastriaPublicKeyRegistry this time. I edited this function to return just a fixed string instead of the public key:
function getCurrentPublicKey(address subject) view public validAddress(subject) returns (string memory) {
    if (publicKeyList[subject].length > 0) {
        return publicKeyList[subject][publicKeyList[subject].length - 1];
    } else {
        return "";
    }
}

function getCurrentPublicKey(address subject) view public validAddress(subject) returns (string memory) {
    return "Hellojusttesting";
}

After this change i did the upgrade process:

npm run compile
npm run migrateToRedT
npm run initRedT
git checkout addresses.json
npm run updateRedT

And tested the function with the examples:
node 1.getSubject1CurrentPublicKey.js
RESULT -----> Hellojusttesting

I reverted the changes to the contract, upgrade it again and tested the same example one more time:
node 1.getSubject1CurrentPublicKey.js
RESULT -----> 2e507af01167c98a6accc0cd46ab2a256dd6b6c69ec1c0c28f80fb62e1f7d70233768b0c58dbbdac1fc358b8141c075a520483cf9779e4ea98d13df2833f3767

So looks like everything is working as it should

That's a good test for me!
@nefera606  do you think we need to test something more deeper? Or maybe we can close this issue and mark it as complete?
PS: very good job @anthares101

The evidences have been deemed sufficient and we therefore close this issue.


Agenda and MoM for 2023-10-10

What type of PR is this?

documentation

What this PR does / why we need it:
Agenda for next meeting. to be updated with minutes

Duplicated in https://github.com/camaraproject/DeviceLocation/pull/99


Do not throw an error for malformed URI sequence

For example such usage will throw an error:
queryString.parse('?%');
queryString.parse('?key=%AF');
queryString.parse('#key%1=value');

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/URIError#Catching_an_URIError
What do you think about adding try catch statement?
P.S.: https://github.com/ljharb/qs/blob/master/lib/utils.js#L78-L84

Duplicate of https://github.com/sindresorhus/query-string/pull/65#issuecomment-225350914.

There are a lot of misspelled links in the internet.
Do you think it is a good idea to not handle them at all?
Please compare:

https://www.google.com/?#newwindow=1&q=cats%
http://www.bing.com/search?q=cats%


JedisPubSub, why private on process?

The problem is firstly due to proceed(Client, String ... channels) requiring you to supply a channel when you proceed, which is rarely the case.
client.subscribe(channel) can be called later.
Howerver,

Requires you to pass at least a channel. So one would like to override the class, in order to not to subscribe unless there are channels indeed.
However, for some reason, you guys have decided to make that method private.
I can create a git pull request, but last one have not yet been approved or commented on.
The code base is not great to be honest, and for Jedis to be truly and fully a core library, one does need to hook into and override most basic things in it, including the iterators, and the stuff it generates on input streams such as an alternative StreamEntry and what not.
Otherwise we would have to iterate twice to generate a structure from your generated Structures to something we find more suitable.

If you look at the method proceed(client, ... channels), the goal in this case would have been to ignore the subscribe call and flush and just call process(client);


[RESOLVED] Interface eth0(): High error rate (>2 for 5m)

Problem started at 16:09:29 on 2023.04.17
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Operational data: errors in: 3, errors out: 0
Original problem ID: 18505
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23483&eventid=18505

Problem has been resolved in 9m 0s at 16:18:29 on 2023.04.17
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Original problem ID: 18505


Disable symlinks

If I'm doing .use(express.static('/var/www/html')) and some attacker manages to ln -s /etc/passwd /var/www/html, then http://host/passwd will serve up /etc/passwd. Is there any way to tell serve-static not to follow symlinks, or to restrict them so that they're only followed to files within the directory being served?
I'm essentially asking for Apache's FollowSymLinks or nginx's disable_symlinks.

No, this is not a feature currently, but a pull request to add such a feature would definitely be welcome!

I submitted a pull request that provides this behavior via a new option called followsymlinks which defaults to true.  If it's set to false, it will cause paths that contain symlinks to be forbidden.


Support crop images

I am aware that aves is a excellent image viewing app, but not editing software. While mobile apps are not suitable to do extensive image processing, some easy and quit editing like crop is feasible and handy if aves can do. Using a third app is somehow complicated.
I found several image cropping libraries in pub.dev including image_cropper and image_crop. Both libraries are open sourced and sufficient for image cropping. I am wondering if you can use anyone of them or your own library to allow image cropping directly in aves.
Thanks.

Using a third app is somehow complicated

Please elaborate.

Well, the user experience are different. Most importantly, you will have to install one more app that can read and write external storage.

Funny you should say that, because using an external app for edition is so
smooth that several people have mistakenly thought that Aves included an
editor. Aves was opening the file with another app installed on their
device and they didn't realize it.
On Fri, 23 Dec 2022, 11:57 atbest, @.***> wrote:

Well, the user experience are different. Most importantly, you will have
to install one more app that can read and write external storage.
—
Reply to this email directly, view it on GitHub
https://github.com/deckerst/aves/issues/460#issuecomment-1363849451, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ADKBEXMIKCD4TYR44KFFYHDWOWATFANCNFSM6AAAAAATHS27QA
.
You are receiving this because you commented.Message ID:
@.***>

Maybe they cannot, but I can clearly see the difference.

Anyway, I was interested in your point of view, but this is a duplicate of #17.


CICD for advanced features of OpenStack

What does this PR do?
Provides support to test advanced features of OpenStack in CI/CD
Do you have any concerns with this PR?
No
How can the reviewer verify this PR?
By Testing it in CI/CD environment.
Any background context you want to provide?
No
Screenshots or logs (if appropriate)
NA
Questions:

Have you connected this PR to the issue it resolves?
#191
Does the documentation need an update?
Yes
Does this add new Python dependencies?
No
Have you added unit or functional tests for this PR?
No
Does this patch update any configuration files?
No

Run Tests

Aricent needs help integrating it with github and Jenkins, and get it running with SNAPS at CableLabs while trying to get more resources.


implemented  get all blog post api

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 58.06452% with 26 lines in your changes missing coverage. Please review.
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

Files
Coverage Δ

..._platform/unit_tests/services/test_user_service.py
98.71% <100.00%> (+0.16%)
:arrow_up:

...platform/database_services/blog_post_db_service.py
42.85% <66.66%> (+2.23%)
:arrow_up:

blog_platform/services/blog_post_service.py
96.96% <66.66%> (-3.04%)
:arrow_down:

blog_platform/services/user_services.py
89.13% <80.00%> (-4.99%)
:arrow_down:

blog_platform/manage.py
0.00% <0.00%> (ø)

blog_platform/api/v1/blog_post.py
65.78% <31.25%> (-25.52%)
:arrow_down:


Workflow Jenkins Plugin builds support

It would be great to provide Workflow Jenkins Plugin builds compatibility.

Ah, interesting! What functionality would you like to see exactly?

Overall compatibility. Your plugin provide ability to add workflow jobs to the list, but unfortunately these builds are not visible on diagram.
Workflow plugin authors say: (https://github.com/jenkinsci/workflow-plugin/blob/master/COMPATIBILITY.md): "For architectural reasons, plugins providing various extensions of interest to builds cannot be made automatically compatible with Workflow. Typically they require use of some newer APIs, large or small."
Workflow plugin is absolutely hot now and it would be great to monitor workflow tasks with your software.

Closing for now as Build Monitor now allows for Workflow Projects to be displayed.

It does not work for me, I get this error:
javax.servlet.ServletException: java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowJob cannot be cast to hudson.model.AbstractProject

Hey @RudolfVonKrugstein - what version of Jenkins, Build Monitor and the Pipeline plugin are you using? Also, would you mind pasting the full stack trace as well as it would help with trying to understand the problem?
Thanks!
J


Make it work with JSON streams

Hi,
the readme says that the func in st.stdout.match(func) gets the whole output as argument. But before that it gets partial output every time output is written. So when testing a program which streams JSON the thing crashes and burns with cryptic error messages.
This PR fixes it.
But it makes two other tests fail. I don’t quite understand the use case for these tests. If I’m not sure if a process I’m spawning ends, I just stab it with a st.timeout. A non-ending process is often a bug anyway.

Hi,
The current behavior is actually intended. Here is how I handle JSON: https://github.com/maxogden/dat/blob/4635127989229bdee28d9fe83edd653f28c3f97e/tests/diff.js#L34-L42
I want to support so called 'early return' testing where you dont wait for the entire output to buffer before calling the match function. This means match will be called multiple times. I should make that more clear in the readme.

I get your point. That’s how I handled it at first as well.
I’m just having second thoughts about performance. We all know try/catch is slowish. Even if it weren’t, if a program writes a 100 000-char JSON sequence letter by letter, it could take 5 seconds instead of 0.5 to test it.
And how about outputs like this (written line by line):
[]
not valid JSON!

False positive!
Perhaps we should make a separate function for the early return case? Or make it an option?

Closing to remove clutter 🙂
Feel free to open if you think this is mergeable.


Create a toil-standalone-box for cgcloud

Automate the setup of a single-machine Toil cluster with cgcloud.

Obsoleted by https://github.com/BD2KGenomics/cgl-docker-lib/issues/105 https://github.com/BD2KGenomics/cgl-docker-lib/issues/115


feat: find function

Goals:
Create find() function:
from docarray import DocumentArray, Document
from docarray.utility import find, find_batched
from docarray.typing import TorchTensor

class MyDoc(Document):
    tensor: TorchTensor

da = DocumentArray[MyDoc](MyDoc(tensor=torch.rand(128)) for _ in range(10))

matches, scores = find(da, MyDoc(tensor=torch.rand(128)), embedding_field='tensor', metric='cosine_sim')

batched_query = DocumentArray[MyDoc](
    [MyDoc(tensor=torch.rand(128)) for _ in range(3)]
)
results = find_batched(da, batched_query, embedding_field='tensor', metric='cosine_sim')
assert len(results) == 3
for matches_i, socres_i in results:
    ...

TODO

[x] implement find

[x] for torch
[x] for numpy
[x] allow docarray as query

[ ] refactor: Create classes for backend operations. Edit: Separate PR
[ ] refactor: let types define the backend they belong to. Edit: Separate PR
[x] consider having find and find_batched explicitly
[ ] user defined callable as distance function. Edit: not doing in first iteration
[x] tests
[x] Documentation (docstrings)
[ ] Optional: batching Edit: not in this PR
[ ] Optional: nested find.Edit: not doing in first iteration
[ ] Optional: other features from current docarray. Edit: not doing in first iteration

Note that the file structure is not great atm, this will also change with the PR about computational backends


Add updateAtIndices and modifyAtIndices

Does this look good to you @gabejohnson?

Now that I think of it I actually think the implementation should use foldl instead of foldr. I've just pushed a commit to change it.
The implementation of updateAtIndices in purescript-array looks like this:
updateAtIndices :: forall t a. Foldable t => t (Tuple Int a) -> Array a -> Array a
updateAtIndices us xs =
pureST (withArray (\res -> traverse_ (uncurry $ pokeSTArray res) us) xs)

And if I'm correct then traverse_ executes the actions from left to right which corresponds to using foldl in the implementation in this PR.
Is that correct @gabejohnson?

I don't think it matters though, as the results are ignored.

You're right. I was thinking that it would change the order in which the effects in the applicative was evaluated.


UI: Delete incoming references

Is your feature request related to a problem? Please describe.
The reference editor allows for the management of outgoing references from an instruction in the listing. From a given address, we can use the "Show References to Address" action in the UI, but this does not allow for deletion of the references. The incoming references do not show in the reference editor either.
This was annoying when working with small base addresses as ghidra almost always infers that operands like 0x1000 (typically used as flags/masks) are references to the code.
Describe the solution you'd like
A convenient way from the UI to manage and delete references to an address.

Users can currently show all refs to a place by double-clicking the 'XREF' text.    However, this table does not allow for deleting.  It should be possible to make this a custom table that would allow for deleting.

Any update on this? It's a real chore when the address finder/analysis goes hog wild and creates hundreds of references to somewhere like 0xa0

No updates.  This is in the queue to be done.


Confusing error message when using Set.fromList in a context expecting Dict

Trying to compile this
module SSCCE exposing (sscce)

import Dict
import Set

sscce : Dict.Dict Int {}
sscce =
    Set.fromList [ ( 0, {} ) ]

causes the following error message:
-- TYPE MISMATCH ------------------------------------------------- src/SSCCE.elm

The 1st argument to `fromList` is not what I expect:

9|     Set.fromList [ ( 0, {} ) ]
                    ^^^^^^^^^^^^^
This argument is a list of type:

    List ( number, {} )

But `fromList` needs the 1st argument to be:

    List ( number, {} )

Replacing the {} type with String and giving a string argument gives the helpful error:
-- TYPE MISMATCH ------------------------------------------------- src/SSCCE.elm

Something is off with the body of the `sscce` definition:

9|     Set.fromList [ ( 0, "zero" ) ]
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This `fromList` call produces:

    Set.Set ( number, String )

But the type annotation on `sscce` says it should be:

    Dict.Dict Int String

EDIT: I just noticed that in the first case Elm actually produces two error messages, including the helpful one.

I made a fix in https://github.com/elm/compiler/commit/545b1784695500e822c2d044b6b5ed2ab6689552, so my development build is now producing:
-- TYPE MISMATCH ------------------------------------------------------ temp.elm

Something is off with the body of the `sscce` definition:

7|     Set.fromList [ ( 0, {} ) ]
       ^^^^^^^^^^^^^^^^^^^^^^^^^^
This `fromList` call produces:

    Set.Set comparable

But the type annotation on `sscce` says it should be:

    Dict.Dict Int {}

-- TYPE MISMATCH ------------------------------------------------------ temp.elm

The 1st argument to `fromList` is not what I expect:

7|     Set.fromList [ ( 0, {} ) ]
                    ^^^^^^^^^^^^^
This argument is a list of type:

    List ( number, {} )

But `fromList` needs the 1st argument to be:

    List comparable

Hint: Only ints, floats, chars, strings, lists, and tuples are comparable.

I am going to try to make the hint more specific. I'm hoping it can specifically mention that records are not comparable, but I'm not sure if it'll be doable!

I tried making the hint really extra specific, but I ended up needing to rewrite some code that would be a bit too risky to change this close to a release. I ended up with some logic that should improve the hints on comparable clashes, but not in cases where a comparable constraint is having trouble with a type within a list or tuple.
Anyway, thank you for reporting the error here!


containerd and nerdctl

is there a recommended way to use dive with nerdctl and containerd ?

Any updates or future plan on this? @wagoodman 🙏

Might be related to https://github.com/containerd/nerdctl/issues/473#issuecomment-953548961 Also hoping for support.

any progress here?

bump

You can use nerdctl.sock from nerdctld, with dive v0.12.0 (needed for OCI support)


Wire up the mapper to the project generation.

Codecov Report

Merging #320 into master will decrease coverage by 11.38%.
The diff coverage is 75%.

@@              Coverage Diff              @@
##             master     #320       +/-   ##
=============================================
- Coverage     44.75%   33.37%   -11.39%
+ Complexity      216       72      -144
=============================================
  Files           128       57       -71
  Lines          1879      749     -1130
  Branches        192       57      -135
=============================================
- Hits            841      250      -591
+ Misses          978      480      -498
+ Partials         60       19       -41

Impacted Files
Coverage Δ
Complexity Δ

...aas/project/converter/DefaultProjectGenerator.java
88.49% <75%> (-2.42%)
27 <5> (+2)

...om/redhat/ipaas/model2/ActionInstanceProperty.java

.../com/redhat/ipaas/rest/v1/handler/BaseHandler.java

...ain/java/com/redhat/ipaas/runtime/Application.java

...ava/com/redhat/ipaas/model2/ConnectorProperty.java

...hat/ipaas/rest/v1/handler/exception/RestError.java

.../java/com/redhat/ipaas/runtime/SimpleEventBus.java

...n/java/com/redhat/ipaas/rest/v1/V1Application.java

...redhat/ipaas/rest/v1/handler/user/UserHandler.java

...java/com/redhat/ipaas/rest/v1/V1Configuration.java

... and 62 more


Selected fragment state is lost on rotation in master-child case

The displayed fragment remains the correct fragment, but when using BackPattern BACKPATTERN_BACK_TO_FIRST (and possibly other back patterns too), if you rotate the device, then the drawer forgets its "backstack" and shows Drawer button instead of Up, and also pressing Back button closes app.
This is in case of MASTER-CHILD example. The Child Fragment Stack is not preserved upon orientation change.

Hi, I have the same issue, any solution ?

The variables that would need to be preserved in onSaveInstanceState() are private, therefore I did not bother with coming up with a fix myself.

@Zhuinden Could you give an example? Do you handle the back stack some way?

It's been ages since I tried this, I've just implemented my own stuff since and my own backstack / state persistence lib.


Execution failed for task ':pusher_channels_flutter:compileDebugKotlin'.

Running Gradle task 'assembleDebug'...
e: /Users/madiyar/development/flutter/.pub-cache/hosted/pub.dartlang.org/pusher_channels_flutter-2.0.0/android/src/main/kotlin/com/pusher/channels_flutter/PusherChannelsFlutterPlugin.kt: (25, 7): Redeclaration: PusherChannelsFlutterPlugin
e: /Users/madiyar/development/flutter/.pub-cache/hosted/pub.dartlang.org/pusher_channels_flutter-2.0.1/android/src/main/kotlin/com/pusher/channels_flutter/PusherChannelsFlutterPlugin.kt: (25, 7): Redeclaration: PusherChannelsFlutterPlugin
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':pusher_channels_flutter:compileDebugKotlin'.

Compilation error. See log for more details

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 4s
Exception: Gradle task assembleDebug failed with exit code 1
who got this error please help

Have you tried to clean project and then rebuild?
If you are still encountering the issue could you try one of the suggested option to get more log info and share the output with us?
Try:
Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.

Hi, we need reproduction steps in order to troubleshoot this. As there's been no response to this issue, I will close it.


remove ucsm-ip to disable UCS tests

This is a temporary fix for https://rackhd.atlassian.net/browse/RAC-5184.  The Docker and OVA tests are failing the UCS tests because the UCS-service is not included in either of these builds.  This change will disable the UCS tests.  They will be re-enabled once the UCS-service is include in the RackHD Docker and OVA builds.
@RackHD/corecommitters

👍


Replace disabled stderr redirection char ^ with 2>

Since Fish 3.3.0, redirection to standard error with the ^ character has been disabled by default.
Reference: oh-my-fish/oh-my-fish#585
p.s.: this is the result of an automated process. Apologies if there is already another pull request that addresses this issue.

Ping @er0 🙂

Any thoughts on this one, @er0? This is still affecting users.

thanks for information about this
error messages are below:
Welcome to fish, the friendly interactive shell Typehelpfor instructions on how to use fish sed: ^/dev/null: No such file or directory fatal: Not a git repository (or any of the parent directories): .git jobs: '^/dev/null' is not a valid process id date: illegal time format usage: date [-jnRu] [-I[date|hours|minutes|seconds]] [-f input_fmt]             [-r filename|seconds] [-v[+|-]val[y|m|w|d|H|M|S]]             [[[[mm]dd]HH]MM[[cc]yy][.SS] | new_date] [+output_fmt] date: illegal time format usage: date [-jnRu] [-I[date|hours|minutes|seconds]] [-f input_fmt]             [-r filename|seconds] [-v[+|-]val[y|m|w|d|H|M|S]]             [[[[mm]dd]HH]MM[[cc]yy][.SS] | new_date] [+output_fmt]


feat(view): add region for layout

Checklist

[x] npm test passes
[x] view.region options, used to layout viewBBox
[x] commit message follows commit guidelines

Description of change

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

35 of 41 (85.37%)  changed or added relevant lines in 3 files are covered.
12 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.8%) to 65.806%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/types/g.ts
0
1
0.0%

src/util/bbox.ts
27
32
84.38%

Files with Coverage Reduction
New Missed Lines
%

src/util/bbox.ts
1
79.71%

src/chart/view.ts
11
87.26%

Totals

Change from base Build<PHONE_NUMBER>:
0.8%

Covered Lines:
1327

Relevant Lines:
1904

💛  - Coveralls


Added unit tests based on the example provided in the README.md document based on four different input criteria: api alone; api and city; api, longitude, and latitude; api, zip code, and country. Also fixed a print function typo in the weathermap.py script

Seeking Help: Creating Test Cases for Error Checking #3

Decided to focus on the example provided which is writing some simple test cases for the Weather function. In order to get weather information, you are asked to input a minimum of either:

city
long, lat
zip code and country

In the example, you can just input the apikey to do based on location tracking which is shown in these lines
# Initialize Weather without location to enable location tracking
weather_info_for_current_ip = Weather(apikey='YOUR_API_KEY')

For the zip_code and just api inputs, the tests failed. I just found a zip code from Tampa, Florida and used that. I don't know if there are specific criteria to choosing a zip code. I also don't know if the location tracking is working in the correct context.

I just wanted to give you a quick shout-out and a huge "thank you" for creating the test case for our Weathermap project. 🌦 Your contribution is a big step toward making our code even better and more reliable.
Your dedication to improving our library is awesome, and your willingness to help out is truly appreciated. Thanks for being an integral part of our open-source community! @rqnguyen100


Expose code as an AMD module

I wanted to use this with Ember but without an AMD module, there wasn't a good way to import it.  This change just avoids only exporting through module.exports and adds the ability to export that or an AMD module (or a global variable, if neither of those options are available).
I didn't explicit add an automated test for the AMD export, but I was able to pull it into Ember with these changes present.

Hey @alexlafroscia, thanks for the PR! Sorry it took me so long to get to it; I was on vacation without Internet access. Let me take a look real quick and then I'm sure I'll merge it in :)

No worries! Glad it made it in 😁


Still have issues with Override All Other Styles by using Important

I followed the video of how to override with !important. However, it still shows that I my H1 element should have pink-text and blue-text.
My work:

Hello World!

Update: I had a probelm with google and switched to firefox. I was able to get passed it. Hope this helps other people.

Hi.
Thanks for reaching out.
We require you to fill in the template presented to you when you opened this issue. That helps us help you, and take an issue report seriously.
Please add details like a link to the affected page, your system details etc. That will help us reproduce the error and help resolve it.
Thanks & happy coding.

There’s a typo in the HTML which may or may not be part of the issue:
class:"pink-text blue-text"

should be:
class="pink-text blue-text"

Thanks for clarifying, @danfarrow
The original issue is better suited for our community in the ask for the help section. I am going to go ahead and close this issue.
Happy coding!


Add more functional to cloudstack driver:

work with firewall rules more flexible
keypair work
fix poolling driver
register as provider

Thanks for this patch and a bug report!
While reviewing and testing your patch I also found some bugs myself and I have merged your bug fixes and mine into trunk today - https://github.com/apache/libcloud/commits/trunk.
I also wanted to include this fixes in the next release so I have canceled a vote for Libcloud 0.6.0 and started a new one for Libcloud 0.6.1 which includes those bug fixes.
For now I have also only merged essential bug-fixes, because I didn't want to introduce any new possible bugs which could creep in through the new features.
I will merge new features into trunk as soon as you add tests for them.
If you need help with writing the tests, let us know (Writing tests and using the fixture framework page should also help you).

Ok, I'm write tests.
Thank You for fast reaction


Docs Overhaul

Feature description
Complete rewrite of the docs, including both the markdown and mkdocs theme. Should hopefully look something like NextJS or Tailwind when done.
Feature example API
N/A
Anything else?
No response

Hello! I'm new to GitHub contributions. Found this Open Issue and I'd like to give it a try. Never really worked with mkdocs, but I'll have an in-depth look at how the docs currently work and provide a solution to this Open Issue. I see it still uses CSS, so it seems to be fine by me.
Do you require Figma prototypes before development or could I jump straight to styling?
Thank you in advance!

I don't use Figma, so you can jump right in. If you need any help with MkDocs, they have a good documentation on designing themes. This is a big issue, so I'll work on it alongside you. Be sure to join the discord if you have any questions.

I think it might be possible to build the docs in Next, would that be helpful if I set that up?

Sure thing! Thanks a lot! Whichever you think would better fit your preferences. I can get into the MkDocs documentation without an issue, but I can jump into Next as well. Whatever works for you.

I think let's stick with MkDocs for now, since it's really easy to write documentation for it. If you want to use Next, be sure to let me know.

No worries, bud!
Having that already set up is great and I'd rather accomodate myself around what you have, than force you to use something else.
Cheers, I'll keep you posted on Discord with the progress.

Vue and Nuxt are also both good examples of how this could turn out.

I highly encourage you people to stick to the MkDocs, it's great and it's python 😎


ARROW-9810: [C++] Generalized nested reconstruction helpers

This adds helper methods for reconstructing all necessary metadata
for arrow types.  For now this doesn't handle null_slot_usage (i.e.
children of FixedSizeList), it throws exceptions when nulls are
encountered in this case.
The unit tests demonstrate how to use the helper methods in combination
with LevelInfo (generated from parquet/arrow/schema.h) to reconstruct
the metadata.

Refactors necessary APIs to use LevelInfo and makes use of them in
column_reader
Adds implementations for reconstructing list validity bitmaps
(one uses rep/def levels.  one uses greater then bitmap generated
from rep/def levels).
Adds implementations for reconstruction list lengths
(one uses rep/def levels.  one uses greater then bitmap generated
from rep/def levels).
Adds dynamic dispatch for level comparison algorithms for AVX2
and BMI2.
Adds a pextract alternative that uses BitRunReader that can be
used as a fallback.

Hmm... I don't know if this is easy to tear apart, but I'd appreciate if the PR concentrated on the functionality, and micro-optimizations (SIMD or otherwise) separated into later PRs. Would that be reasonably doable?

Hmm... I don't know if this is easy to tear apart, but I'd appreciate if the PR concentrated on the functionality, and micro-optimizations (SIMD, BMI or otherwise) separated into later PRs. Would that be reasonably doable?

How about I remove the net new bitmap related code?  The SIMD/BMI code was already present hidden behind compiler flags instead of runtime dispatched.  The runtime dispatch is cleaning up technical debt to allow users to make use of these in prepackaged binaries (the PR that introduced them showed a 20% improvement on our end to end parquet->Arrow reading benchmarks).

@pitrou I've removed the code for reconstructing list information based on bitmaps, I would appreciate keeping the rest of the in this PR.

Closing in favor of: https://github.com/apache/arrow/pull/8177


Select-Object -ExpandProperty and -Property should be mutually exclusive

-ExpandProperty makes Select-Object return a single property value, which is mutually exclusive with -Property, which outputs a custom object with the specified properties.
Currently, -Property is quietly ignored when -ExpandProperty is also specified.
Steps to reproduce
[pscustomobject] @{ one = 1; two = 2; three = 3 } |
  Select-Object -ExpandProperty one -Property three

Expected behavior
A statement-terminating error complaining about mutually exclusive parameters should be issued.
Actual behavior
1

That is, the -Property argument was silently ignored.
Environment data
PowerShell Core v6.0.1
Windows PowerShell v5.1

That is not entirely correct and making it mutually exclusive would be a breaking change.

-ExpandProperty on a Property containing a PSObject it will add a row for each -Property and include the expanded properties that matched to that row.
Using your example, I embed PSObject called three containing values 3 and 4 and it gets added :
[pscustomobject] @{ one = 1; two = 2; three = [pscustomobject] @{ three = 3; four = 4 } }|
    Select one, two -ExpandProperty three

three four one two
----- ---- --- ---
    3    4   1   2

This is very useful for flattening data rom nested objects so that you have it all in the main record. For example, I took custom fields that were embedded in a ticket and expanded it this way so that the custom field would look like a regular field alongside the others.
This is one of the things I do a lot so the proposed change would break half my scripts.

Thanks, @dragonwolf83 - I forgot about the many subtleties of -ExpandProperty.
The current Select-Object docs are woefully inadequate (incomplete, and partially misleading).
Here's what actually happens, and from that perspective the behavior is consistent in all 3 cases you mention:

The single property you pass to -ExpandProperty becomes the output type. That is, instances of whatever type the referenced property is are output.

Any properties you pass to -Property are added as  note properties to those output-type instances.
Often, the output formatting may not show these note properties, which makes it look like they're not there (ignored), but they are there.

In short: The real problem is one of poor documentation, and I'll add an issue in the docs repo.

I've created a documentation issue: https://github.com/PowerShell/PowerShell-Docs/issues/2130


Accessibility Issue - Menus

**WCAG Criterion 1.3.1 Info and Relationships (Level A) **
There’s no non-visual indication/separation between the search/filter, spaces list, and map sections. I wonder if an accessibly hidden heading structure may be an option here, which would also mean all the spaces headings would need to be dropped down by one.

Fixed by adding headings on each of the sections in 45c8656b6dcf3dc0eb03347bfeaa5f59bdeab33a


Tdarr plugin

Good day,
I am experiencing a pluggin error with the tdarr plugin.
It used to work flawlessly before. It doesn't really give me much info but is this plugin this working with the latest version of tdarr?
https://pastebin.com/93xn4xGW

Hello??


set up meeting with janki/jack to see if there any SEO tricks we should do on the github README pages or other ways to ensure google leads people to the SDKs

just need an owner to drive this and document any suggestions.
test google searches for C# vs dotnet.

Notes:

Searching "dotnet momento" or "c# momento" or "csharp momento" results in first page results all for the design pattern "memento". Not hits for Momento

Hannah is tracking baseline metrics in a tool now. We will revisit later and iterate to improve the metrics.


i want image to fitxy, you can help me? thank you !

my work is need to fitxy image, so can you help me ?. I'm try set Image scale to fit center but it not give what i looking. Thank you anyway ! this is amazing library.
sorry for my english !

Hi Arthur,
Very nice and handy library to use. Do you have any work around for this. Where I would like to do fitXY for my camera captured Image


[WIP] Implement the supporting structure for switching to the tasks model

Implements the structure, but no business logic yet, of the CLI and the individual tasks.
Maintainers will complete the following section

[ ] Commit messages are descriptive enough
[ ] Code coverage from testing does not decrease and new code is covered
[ ] JSON/YAML configuration changes are updated in the relevant schema
[ ] Changes to metadata also update the documentation for the metadata
[ ] Pull request has a link to an osbs-docs PR for user documentation updates
[ ] New feature can be disabled from a configuration file

Removed some plugins as per https://github.com/containerbuildsystem/osbs-client/pull/1033

PTAL, I realize some unit tests are failing but I can't be bothered with anything older than F33 :smile:
(I might look into why F32 is failing at some point)

PTAL, I realize some unit tests are failing but I can't be bothered with anything older than F33 smile
(I might look into why F32 is failing at some point)

Fixed, argparse on python3.8 cannot handle a required subparser without a metavar

atomic-reactor now requires python3.8 or greater

Nice PR! Separate commits with explanation <3

Removed unused logger, fixed flake8 problem and removed redundant assert

I found out just now (from #1663) that we have a separate user_params schema for source containers :O
Fixed


docs: remove code sprint announcement from README

title says it all...

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


hasSearchString fails on post creation

When trying to create a post it fails with the following console log:
TypeError: Cannot read property 'length' of undefined
    at e.value (create-post.js:271)
    at e.value (create-post.js:245)
    at fn (eval at compile (angular.js:15551), <anonymous>:4:169)
    at i (angular.js:27341)
    at l.$eval (angular.js:18423)
    at l.$apply (angular.js:18523)
    at HTMLButtonElement.<anonymous> (angular.js:27346)
    at $t (angular.js:3771)
    at HTMLButtonElement.n (angular.js:3759)

This seems to be caused by the merging work done in #1993.
Before the merge, the seeks part of a draft would not exist when hasSearchString was called, and it would therefore immediately return false:
https://github.com/researchstudio-sat/webofneeds/blob/aa219a6f50d28c7c7da6441222a99a4b2baed4aa/webofneeds/won-owner-webapp/src/main/webapp/app/components/create-post.js#L251-L253
The function then checks the length of tags on seeks, which does not exist, and fails with a type error:
https://github.com/researchstudio-sat/webofneeds/blob/f167445b0a4044d6f9df37d50f83eeb6c7ffdd6a/webofneeds/won-owner-webapp/src/main/webapp/app/components/create-post.js#L271-L273
@m0ru @maxstolze

The check wether the object is a "is" or "seeks" object, was removed, because it was depending on the title. Now we need to implement a new way to check the "type" before creating the need.


Update Contributors.md

If you're adding your profile, the title of this PR should be: [Add profile] -> [Your Name]
Add Winner Umeh

This is a duplicate @winniffy. You have already made a PR to add your profile here.
Kindly close the one you don't want merged

done. @Evavic44

done. kindly check, @Evavic44


site-search-360-react loads multiple times in Gatsby apps. Missing cleanup code?

Visit https://www.software-express.de/ and open Developer Tools

Now visit other page. Each page appends new loaders/themes.

Fixed in v14.1.95, please make sure to clear the cache and that the latest version is loading before retesting.


Fixes some minor thread safety violations

Motivation
Reading latest changes through pulsar code I found some minor thread safety
violations.
Modifications

When possible, prefer using final fields. fixed for initialStartMessageId
and startMessageRollbackDurationInSec fields.
Fix issue accessing timeout field within inner lock on UnAckedMessageTracker.

run java8 tests


LogFactory - GetLogger should null-check logger name

Throw ArgumentNullException instead of throwing NullReferenceException here (When Name is null):
https://github.com/NLog/NLog/blob/3c16e69ae0bd6e33d16d1580882dce354c02d51c/src/NLog/LogFactory.cs#L1015
Could also consider doing fallback to string.Empty.

Codecov Report

Merging #3332 into dev will increase coverage by <1%.
The diff coverage is 100%.

@@          Coverage Diff           @@
##             dev   #3332    +/-   ##
======================================
+ Coverage     80%     80%   +<1%
======================================
  Files        356     356
  Lines      28101   28103     +2
  Branches    3743    3744     +1
======================================
+ Hits       22517   22535    +18
+ Misses      4503    4486    -17
- Partials    1081    1082     +1

Thanks!

Could also consider doing fallback to string.Empty

Doubted also about this, but I think the change in this PR is good enough


Questions to address

This is a collection of miscellaneous questions we need to address for the package:

Is there a complete list of Characteristic Name that I can use to check if entries are correct? https://github.com/massbays-tech/MassWateR/blob/d959b4cbbd51ddf7e70f4d6df1afcfedd7e64d5d/R/check_results.R#L46
Similarly, are there acceptable Result Unit values for each Characteristic Name?
What about entries in the Relative Depth Category column?  It currently checks for Surface, Bottom, and < 1m / 3.3ft https://github.com/massbays-tech/MassWateR/blob/d959b4cbbd51ddf7e70f4d6df1afcfedd7e64d5d/R/check_results.R#L45
Parameter names in DQO file do not match those in Results file, should they?  The names in DQO files were changed to match.
Do I have the correct activity types subsetted for the completeness checks in qc_completeness? https://github.com/massbays-tech/MassWateR/blob/d959b4cbbd51ddf7e70f4d6df1afcfedd7e64d5d/R/qc_completeness.R#L109

Regarding the activity types in the completeness check...
One lab spike activity type is missing ("Quality Control Sample-Reference Sample"), but this will only be in the WQX output file.   Also note that the field duplicate activity types will not show up in the Results file.  They will only be in the WQX output file.
In the code where you are doing sum(), I assume you are getting the count of records not the sum of values.  The completeness check is a count of records.
I tried to make some edits directly in the code, but I got a message saying I must be on a branch to make or propose changes.  I'm not sure what that means.

Regarding the Relative Depth Category column...
I think the actual name for this column in WQX is "Activity Relative Depth Name", so we should probably change to that.
The allowable values are "Surface", "Midwater", "Bottom", and many others.  But we are only planning to analyze "Surface".  "< 1m / 3.3ft" is not an option for Relative Depth.  That was referring to values in the Activity Depth/Height Measure Column.  If we see values that are less than 1m or 3.3 ft, then they will be considered the same as "Surface" and included in our analysis.  Though, I'm thinking we might need to change this to <=0.5m/2ft, because 1m/3ft is sometimes a non-surface measurement.

Here is a file of parameter names and mappings, but it may not be the full list yet
Parameter Mapping.xlsx
.

@fawda123 standby for an updated Parameter Mapping file.
Re: Relative Depth, users' data can include Surface, Bottom, Near Bottom and Midwater. As Ben said the tool will most likely use data that are either (a) logged as Surface in the Relative Depth column, or (b) recorded as < 1m / 3.3ft in the Activity Depth column.
Re: DQO file parameter names, I do think these should match the results, especially now that we're providing simplified options. I can't see how Marcus would map every possible user-provided format to the Results.
@ben-wetherill We should keep the 1m / 3.3ft depth limit because it is the standard for EPA and DPH bacteria sampling programs. Renaming the Relative Depth column now to match WQX is fine, or we can do it in the WQX template package step which will involve a lot of additional column naming.

Here is an updated Parameter Mapping file.  You can probably ignore the Parameter Group column for now.  That is primarily just to help us organize our thinking, but it might come in handy when we are thinking about analysis graphs.
Parameter Mapping_4-29-22.xlsx

Thanks @ben-wetherill and @carrjill, I'm trying to digest all of the comments in this thread.  In hindsight, one question/comment should match to one issue so we're not tracking multiple problems in one thread.  That's my fault for adding multiple questions in the original issue.
For the list of characteristic names, I've added a new dataset to the package that uses the Parameter Mapping file from 4/29 that Ben posted in his last message.  The parameters in the "Simple Parameter" column are now used as the common set that are checked on data import of the results file.  I also went through and changed the results and DQO files (using the new ones Ben sent on via email on 4/26) to have consistent parameters names that match the parameter mapping file.  If I'm understanding correctly, we are now allowing our template to use these simple names with the hopes that users will follow suit when they're importing their own data.  I'll have to map the names to the WQX format for any data intended for upload after going through the package workflow.  Will do that later...
I also added "Gage" and "Air Temp" to the parameter mapping file because these variables were included in the original results file.  So, now these are "acceptable" entries from our master list.

I also added some additional checks in check_results() for the result unit values.  Importing the results file will also now check for:

Missing values in the Result Unit column (excluding pH)
More than one Result Unit entered for each parameter.  We may want to chat about whether this is approriate, this is more a check for any downstream analyses, but I realize groups may have different units for the same parameter.
The Result Units match those in the parameter mapping file.  I had to change the entries in the original results file so the checks would pass.  We should chat about whether or not this is appropriate, i.e., are we expecting users to follow the conventions in the parameter mapping file for all results and DQO inputs.

Clarification on parameter mapping - Jill and I were thinking that the mapping between Simple and WQX parameters should be just like synonyms.  In other words, in any file, the users should be able to use either form and R should convert to the preferred form for each output.  So, users' input files (Results and DQOs) would have either Simple or WQX names (no other names allowed), depending on user preference.  This could even be a mixture, meaning users might use Simple names in the DQO files and WQX names in the results file.  R should think of them as synonyms.  Our QC Review output and analytical outputs should probably use the Simple names, and our WQX output must use the WQX names.  Is that reasonable?
Regarding Gage and Air Temp - I sort of left these out on purpose, because these are in that gray area of parameters that we might load into WQX but we don't track them for data quality.  They are low priority and probably useless to DEP, but OARS includes them in the WQX file just because they always have.  My guess is that many groups may have a parameter or two like this.  It wouldn't be hard to argue to remove them completely from the WQX upload, but I'm thinking it might be simplest for us to just allow them to pass through.  Maybe it's okay not to have them in the DQO file and just have a warning.  What do you think?
Regarding Result Units - I think your checks are good.  I'm thinking it is reasonable to expect users to stick to a single unit of measure for each parameter.  For example, if their DO DQO is in mg/L, then their results file can't be in ug/L.  If we didn't require this then we would need to maintain all of the conversion factors.  Some are easy, but some are not.

I guess this issue can be closed, right?


add information about the file size limit

Signed-off-by: Batuhan Apaydın<EMAIL_ADDRESS>
Summary

This PR aims to add information about the file size limit for uploads in public instance of Rekor provided by Sigstore.
Release Note

docs: add information about the file size limit
Documentation

PTAL @bobcallaway

Codecov Report

Merging #1313 (1d790ea) into main (18c81d9) will decrease coverage by 20.29%.
The diff coverage is n/a.

:exclamation: Current head 1d790ea differs from pull request most recent head 7753435. Consider uploading reports for the commit 7753435 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff             @@
##             main    #1313       +/-   ##
===========================================
- Coverage   63.22%   42.93%   -20.29%
===========================================
  Files          82       74        -8
  Lines        7863     7415      -448
===========================================
- Hits         4971     3184     -1787
- Misses       2260     3903     +1643
+ Partials      632      328      -304

Flag
Coverage Δ

e2etests
?

unittests
42.93% <ø> (+0.05%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

 Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


How to disable an specific Node dynamically?

How can I make an specific node disable using click event? I'm adding isDisabled = true to the Node but treeselect does not refresh and react at all.

Same problem here. I wanted to limit selected nodes disabling all unselected when length matches the limit.
Solved setting all nodes as isDisabled = false on treeselect options load (in my case, I'm using Delayed Loading), and after that, it reacts on changing dynamically the isDisabled prop of the node.
Hope this solution can help you.

Same problem here. I wanted to limit selected nodes disabling all unselected when length matches the limit.
Solved setting all nodes as isDisabled = false on treeselect options load (in my case, I'm using Delayed Loading), and after that, it reacts on changing dynamically the isDisabled prop of the node.
Hope this solution can help you.


Add a tag to top-level span to allow identifying endpoint in APM metrics

What does this PR do?
Same as https://github.com/DataDog/datadog-api-client-java/pull/348, just for this Go client.
Additional Notes

Review checklist
Please check relevant items below:

[ ] This PR includes all newly recorded cassettes for any modified tests.

[ ] This PR does not rely on API client schema changes.

[ ] The CI should be fully passing.

[ ] Or, this PR relies on API schema changes and this is a Draft PR to include tests for that new functionality.

Note: CI shouldn't be run on this Draft PR, as its expected to fail without the corresponding schema changes.

/azp run

Thanks for the review! Merging.