Filters on high cardinality dimensions should sometimes use dim index bitset + full scan instead of unioning bitsets of dim values

Sometimes Filters/DimFilters (Like, Regex, Bound, etc.) on dimensions of very high cardinality (thousands of values) end up unioning bitsets of significant fraction of individual dimension values, and the resulting bitset is 50% or more full.
So instead of making a union of 100k bitsets when filtering on a 200k-cardinality dimension, we better make a bitset of matching dimension value indexes (like here), scan all rows in the segment and apply a simple check "matchingDimValuesBitset.get(index)" on each row.

#3775, #3792, #3848 are tangentially related in that they also consider the tradeoff between index-based filtering and cursor-based filtering.

In addition to your idea (converting pre-filters to post-filters) one or both of these may also be an improvement. I haven't tested them though:

unioning larger numbers of bitmaps by adding them one by one into a BitSet and then converting the BitSet to an ImmutableBitmap of whatever type (roaring/concise), instead of directly calling bitmapFactory.union(bitmaps). This mode could trigger after unioning some number of bitmaps.
allowing Filter.getBitmapIndex to return an uncompressed BitSet-based bitmap if it wants to, and use this ability to "fall back" to handling bitmaps in an uncompressed way if there are a lot of them being unioned.

a bitset of matching dimension value indexes (like here)

The link is broken, unfortunately.

Sometimes Filters/DimFilters (Like, Regex, Bound, etc.) on dimensions of very high cardinality

Do queries with simple dim = 'VALUE' fall into that category?

Do queries with simple dim = 'VALUE' fall into that category?

I doubt it, unless you have a lot of them ORed together. Then, maybe.

I wonder whether a lot of them means 10, 100, >1000?

@egor-ryashin experiments should be run to determine that.

It also depends on whether those filters match anything or not (not-matching means it doesn't add any union work, just index-search work). So it can be very hard / impossible to predict which one is better without doing a lot of the work, and the algorithm is going to need to make some guesses.

I've also been lightly experimenting with this, as an offshoot of #6633, to try to get enough of a feel for things to put together a proposal for a more generic solution than in that PR. But I have been rather side tracked with some other things and haven't got back to it yet, so I can at least share my thoughts so far in case they are useful to you or someone else wants to run with it before I can pick it back up.
Besides selectivity, my limited experiments lead me to think that the type of filter can also drive whether or not a filter should be done as a pre or a post filter, since not all filter value matching is equal. Particularly, things like bloom filters which need to compute a hash per value and test each hash against the bloom filter, the match itself is very expensive for high cardinality dimensions before it even gets to combining the bitmaps. #6633 illustrates that it can be useful in that case to always push to a post filter if the cardinality is high, even if the filter is highly selective.
The hard part of this then would be figuring out how to encode this somehow so that the threshold can be a function of how expensive the filter is, assuming such classification is possible or useful in practice and that other filters exhibit a similar patterns to what I was observing with bloom filters which was my main focus so far. By side effect, introducing the idea that filters have some sort of cost value additionally opens up another optimization for evaluating 'and' filters, by giving a sensible mechanism to control the order in which filters are evaluated so that cheaper filters can be evaluated first and non-matches potentially shake out faster.
It looks like some effort has gone into selectivity estimation for use with search queries in the past, but my gut tells me many of these estimates look fairly expensive, so i'm unsure of their utility for all query types. I have not verified this however, nor am I super familiar with these estimators, so it's possible I'm wrong. I was hoping experimentation would shake out whether or not knowing filter selectivity directly is even necessary. It might be well enough that we know that certain types of filters (selectors and combinations of selectors) should rarely if ever not be pre-filters, while others should generally always skip bitmaps if the cardinality is high enough, perhaps with the threshold adjusted based on how expensive the filter is or not. However, I suspect it's not actually that simple either, but hard to say without further experiments.
I don't really know what this looks like yet implementation wise, too many unknowns at this point. All testing I have done so far has been very manual. For my next steps, I was planning on setting up a test harness that would let me manually control whether or not filters should use bitmap indexes similar to #6633, but maybe as an option to all filters, and then benchmark with parameters to run under a variety of conditions to find if there is indeed a 'break even' point and how it varies between filter types, overall dimension cardinality, and filter selectivity. But like I said, I'm not sure when I'll get to this, so if this interests you, I say have at it and I'll be more than happy to support with further discussion or review instead in order to see this get done :+1:

@gianm @clintropolis it seems to me that you are talking about more general problems. This issue is about a very specific problem: unionDimensionValueBitmaps() calls in BoundFilter.getBitmapResult(), LikeFilter.getBitmapResult() and Filters.matchPredicate(), when they literally union 100k bitsets, each of cardinality 1 (in other words, the dimension values are unique). It's just always a very bad idea. Properly in such cases bitmap indexes should be disabled for such columns (see #5402), but sometimes they are not disabled, e. g. in old segments produced by Druid versions that didn't have #5402 yet.
There are also less extreme cases when bitmaps are generally shouldn't be disabled, but union should be avoided for particular queries. Imagine that LikeFilter or BoundFilter ends up unioning bitmaps corresponding to 90% (99? 100?) of values in the dimension in the segment. There is also little doubt that unioning should be skipped in such case. The question is where is that threshold. Even if threshold-based heurstic leads to a suboptimal decision sometimes, it's anyway better to have it than not having any threshold at all. (All query planners generate suboptimal plans sometimes; it's not the reason not to use them.)

Eh, I think the problem I encountered with bloom filters is more or less the same problem you describe, if not even simpler because it only depends on cardinality, not even selectivity matters, so a threshold based approach would likely almost always do the right thing if the threshold is set correctly.
The filters you describe experience bad performance when those filters match a large percentage of overall rows, which is why I brought up selectivity in the first place, but I too am hoping that just a threshold based approach would be good enough or at least better than what there is now.


Hover stylings

Made it easier to pass in stylings, and added hover state param to 'value', 'nestedNode' and 'rootNode' stylings.

@mclin thanks for PR! There are some minor code style issues, otherwise looks fine for me.


Third party cookie TTL is passed incorrectly to stealth script

Testing info for QA: make sure that #1021 and #1034 is resolved.


Declaration request migration

Migration to change printout_request column type to text in declaration_request table to be in par with schema

Changes Unknown when pulling df0299b22795e5bc2fc9385e7af9a549fc633d64 on Declaration-Request-Migration into ** on master**.


Support for YAML tags like Dataview (use ::)

Would be great when YAML tags (might strictly not be a correct name) with :: are supported. Like dataview plugin introduced them. Something like : location:: lat, long
This is specially usefull when (another enhancement request) it is possible to use an address for example as the location point. Then you can place the address in a normal place in the note and not specific in the YAML frontmatter.

Can you elaborate more on how you'd use these YAML tags? Especially with relation to textual addresses which I want to add soon?

Let me explain ... Most of my person notes like something like this:
John Doe
tags:: #person/work, #2021
birthday:: 1971-01-01
address:: Main street 1
zipcode :: 123456
company:: Google
company_role:: consultant
department::
and some more fields that you can read with dataview plugin ... like
known_from:: where did I meet this person
work_life:: short summary about work situation
personal_life:: short summary about personal situation
Not all fields are always filled in and sometimes not all fields are even there (started using template later on so I still have to fix thats.
Depending on my needs I can create a very specific dataview query based on the fields above. Like when I visit a company who do I know and what role and work_life information do I have on those people. Or if I need a carpenter for example who do I already know that has the role carpenter.
Plotting this information is very usefull. The reason that I do not have all of this information in the YAML section is
a. I really do not like the YAML presentation at the top of the page
b. It does not show above but these fields are seldom all grouped at the top of the page. Specially the work_life and personal_life fields can be on different places in the note. And I like it that way... makes for more natural notes style.
writing this I think I might have underestimated the work needed to be done to facilitate that specially if you also want to add a filter based on those fields. Like role:: carpenter to see all the carpenters you know.
And then there is the fact that you currently only use location: to find that datapoints for the map. If that could be made configurable that would be great. In my case ... address:: would be the datapoint you are looking for. But that might be a whole new FR.

That would be extremely useful, and is also important for my attempt of Map View to fit as a complementary view of notes in the complete ecosystem next to graph view.
The main difficulty with what you're suggesting is that it would currently require the map view plugin to parse all notes and cache the results, while using frontmatter tags (as I'm currently doing) does that work already.
Seems like the Dataview plugin has plugin-facing API in plan but it's not available yet. If this becomes available, Map View can ask Dataview for a query on its already-cached data rather than read all notes by itself and mimic the syntax.
I'll ask the Dataview developer for if and when this can be accessed.

Update: the API is there (https://github.com/blacksmithgu/obsidian-dataview/blob/master/src/api/plugin-api.ts) and seems like it has all the building blocks that I need.

Wow ... that was fast !
I am not familiair with API's and stuff but it looks like you want to use the dataview index (generated at the start of obsidian if I understand correctly) to ask for all notes you need. That would be great.


table attribute not available

In the current documentation, a table attribute is available to the class.

However, when running the model, this attribute is not available... The occurrence is available, but this is not documented and provided as a dict.

The table attribute was added in https://github.com/inbo/niche_vlaanderen/commit/4e0bd41d49688db8185f0b8e7eaabe9f97dca329
Are you using the version from pypi?

yup

This was caused because the documentation was ahead of the released version on pypi. I have now released another version. After upgrading the installation, you should be able to use the table function as intended


Define the goals and boundaries of each module

The goal for this PR is continue the discussion about the goal/stakeholder and boundaries of each module provided by the uyuni-tools repository.
@cbosdo @juliogonzalez @admd @mmmmmmpc please feel free to contribute

As a test for these rules: where should we add a command to generate the proxy configuration and how should it be called? This requires access to the server container for podman  and the cluster for kubernetes since we have to generate SSL certificate pair.

I have updated the content with the feedback. Please let me know what you think about it.

Looks good to me.
I think we are good to merge.

I will merge this PR, since no more comments were added. Remember that this is not written in stone, and can be changed in any time in the future.


added README.md file explaining how to get DataWarrior file

##Description
Create a README.md file to explain how to get the DataWarrior file
##Todos

[ ] Create README.md
[ ]  when README.md okay -> delete instructions in nb 1_3

##Questions

[ ]  Question1

Status

[ ] Ready to go

Hi @sonjaleo,
Great README with all the details needed, well done! I suggest a few format changes but that's it.
You could link to your notebook as an example if you want.

@dominiquesydow not sure which notebook you mean? Because the steps that are now in the README should be deleted in the notebook. Or do you mean linking the notebook where the DataWarrior file is used?

@dominiquesydow not sure which notebook you mean? Because the steps that are now in the README should be deleted in the notebook. Or do you mean linking the notebook where the DataWarrior file is used?

Good point... you do have a notebook or script that you use to prepare the input fragments for DataWarrior, right? I would probably write something like

Please find the notebook used to prepare the KinFragLib fragment library for the DataWarrior input at notebooks/XXX.ipynb.

@dominiquesydow not sure which notebook you mean? Because the steps that are now in the README should be deleted in the notebook. Or do you mean linking the notebook where the DataWarrior file is used?

Good point... you do have a notebook or script that you use to prepare the input fragments for DataWarrior, right? I would probably write something like

Please find the notebook used to prepare the KinFragLib fragment library for the DataWarrior input at notebooks/XXX.ipynb.

I wrote a function for the prefiltering which is done in every notebook. The only thing (which I would delete from ne notebook now that it is in the readme) is to safe the smiles without dummy atoms in a file.
I would think the only notebook I could mention is something like
"The created DataWarrior file is used in notebooks/custom_filters/1_3_custom_filters_synthesizability.ipynb"

I would think the only notebook I could mention is something like
"The created DataWarrior file is used in notebooks/custom_kinfraglib/1_3_custom_filters_synthesizability.ipynb"

Edit: I could add a link to notebooks/kinfraglib/3_1_fragment_library_reduced.ipynb where the prefiltering is explained?

Perfect! Yes to both; then the user can find more information on (a) the pre-filtering [before DataWarrior] and (b) what can be done with the new dataset [after DataWarrior].


Intermediate certificate is not updated in child certificates

Describe the bug:
This is duplicate of #5114 as the issue still persists and has not been addressed in the meantime.
Child certificates tls.crt contains both the certificate itself as well as all intermediate certificates for verification purposes on the peer side. Please see the referenced issue on how to setup a basic chain for reproduction.
I can also reproduce this by not forcing a renewal but rather by a "natural" renewal of the intermediate certificate due to expiration. This may lead to the entire certificate chain not being verifyable until the child certificates expire as well.
Expected behaviour:
Forcing a reissuing of the intermediate certificate shall also replace the intermediate certificate in all child certificates and childs-of-child etc...
Steps to reproduce the bug:

Make a certificate chain as described in the referenced issue
Force reissuing intermediate certificate or let it expire while the child certificate is not expired yet
Compare secrets of leaf and intermediate certificates, leaf certificate will have the old intermediate.

Anything else we need to know?:
Environment details::
I can also reproduce this for the latest minor version of cert-manager (1.13.2).

Kubernetes version: 1.27.3
Cloud-provider/provisioner: None/k3s/Embedded
cert-manager version: 1.13.2
Install method: e.g. helm/static manifests: helm

/kind bug

/remove-lifecycle stale

Hi,
this weekend I was able to observe exactly the same thing as the topic creator in one of my clusters.
My cluster has the following certificate chain: root ca->intermediate ca->server certificate. The intermediate CA certificate has expired and has been renewed. In my opinion, the certificates signed by the previous intermediate CA should have been reissued or there should have been a configuration option for this to enable re-issuing child certificates.
Other applications, such as the enix/x509-certificate-exporter, are currently failing because the intermediate CA certificate in the TLS secrets is <30 days and will soon expire. The server certificate must be renewed, although it is still valid for longer than the intermediate CA certificate.


Move this repo under sbt/sbt-jmh

The "more official place" for sbt plugins.
And add it to the list on the sbt site as well.

@ktoso I assume you're less interested in maintaining this these days :-)
would you agree to transferring it to the sbt org? if so, I think @eed3si9n could work with you to make it happen

If you transfer the ownership to me, I can move it to sbt org and make a team with you and whoever you want in it.

@ktoso I assume you're less interested in maintaining this these days :-)

Very interested but legally forbidden from doing so 😢
Yeah I can add folks as owners, help is very welcome due to my unfortunate employer's rules about oss... Thanks! I'll add you both.

And done!
Thanks @eed3si9n and @SethTisue.
Sorry for the trouble from my end on the in-ability to maintain this nowadays...

Repo is moved, and sbt-jmh is created with admin rights to this repo.

@ktoso this plugin is enormously valuable — thanks for the effort you put in on it, it's really helped a lot of people.

Thanks a lot Seth, I'm very happy that it continues to be useful and maintained :) Thank you all


Update service instance provision parameter to foo bar

Remove all content from the parameter json

This issue was moved to kubeapps/kubeapps#159


DeepOnion-cli does not compile on Ubuntu 16.04

Hi,
I have compiled many times but the cli daemon won't compile. How can I make the cli compile? I need it to do anything with the daemon. The DeepOnion-qt also doesn't work even though it did compile. Why not compile the daemons and put them in releases for download?

Also there are no errors at all while compiling. Just get DeepOniond that does work, but no DeepOnion-cli and DeepOnion-qt aborts and exits immediately

With this version you don't need deeponion-cli, you can do everything with deeponiond.
what's your problem with qt client? I can compile and execute it with out any problems.


Prefer FirstOrDefaultAsync  to SingleOrDefaultAsync

The scaffolder generates calls to FirstOrDefaultAsync .  Per @ajcvickers comment here
It's usually best to use FirstOrDefaultAsync unless the code specifically needs to check that there really is no more than one entity returned, because doing that check fetches more data and does more work.

@ajcvickers given we have the PK, wouldn't it be even better to use FindAsync(id) ?

@Rick-Anderson There are pros an cons:

Find is simple and concise if all you need is to look up a single entity.
Find can have perf benefits in some situations, but they rarely come into play for normal web scenarios.
Find implicitly does First instead of Single.
But if you want to Include other entities, then Find is no longer appropriate. This means that you may need to abandon Find and move to a query as your app progresses.

So then the main question is whether or not it is worth increasing the concept count and creating a pivot point in the learning process for the relatively minor benefits in the first three bullet points. If I'm put on the spot, I would say start with query in the first place because the grow up story is better, but I think a strong case could be made either way. /cc @divega

Closing because FirstOrDefaultAsync is appropriate. cc @tdykstra


Cant Start - Missing careconnect-ri.war?

Hi, I am getting the below error when trying to start the latest release?
ERROR: Service 'ccri' failed to build: ADD failed: stat /var/lib/docker/tmp/docker-builder404952759/target/careconnect-ri.war: no such file or directory

Could you let me know how you resolved this @dollis-developer, we're seeing the same issue.
Tried doing a maven build before running docker-compose up but doesn't seem to resolve the issue.

I'm presuming you are using the docker-compose in the repository?
We use that in jenkins but a different one on our demo server. I'll have a look.

Note: this is using postgres unlike the previous docker-compose.
You might want to leave off the ccri-smartonfhir section. The ccridl is a work in progress, it loads in reference data for the server (mostly codes), it should work though.

Thanks for the replies, sorry didn't notice them until now.
The Docker Compose file above let me get the containers running thanks (I just commented out the network sections). I've only looked at the db container so far, but hopefully the other containers are running ok too.

Great, will spin this up tomorrow, thanks for your help!

This all appeared to be going well until attempting to connect to postgres, I still have the environment variables set from the

Heres the full log:
https://pastebin.com/3RDCSQP7

It’s looking like a database connection issue, I think Postgres isn’t picking up the username and password from the enivironment variables.
I’ll see if I can get a colleague to look at it.

Closing as new docker-compose files have been produced and instructions updated.


[🐛 Bug]: npx vercel build for edge runtime causing ReferenceError: document is not defined

next-on-pages environment related information
System:
Platform: darwin
Arch: x64
Version: Darwin Kernel Version 22.5.0
Binaries:
Node: 18.16.0
Yarn: 1.22.10
npm: 9.5.1
pnpm: N/A
Package Manager Used: yarn (classic)
Relevant Packages:
@cloudflare/next-on-pages: 0.10.1
vercel: N/A
next: 13.4.2
Description
I'm facing a little hiccup while trying to build a Vercel app for Cloudflare Pages. The good news is that the application build goes smoothly and completes successfully. However, I hit a roadblock when I try to run npx vercel@latest build as it throws an error.
I use app directory.
I use route segmented config
export const runtime = 'edge';

build command:
npx @cloudflare/next-on-pages@latest

▲  - info Collecting page data...
▲  /app/***/.next/server/edge-runtime-webpack.js:196
▲  /******/ 		__webpack_require__.b = document.baseURI || self.location.href;
▲       		                        ^
▲
▲  ReferenceError: document is not defined
▲  at /app/***/.next/server/edge-runtime-webpack.js:196:36
▲  at /app/***/.next/server/edge-runtime-webpack.js:245:13
▲  at /app/***/.next/server/edge-runtime-webpack.js:250:12
▲  at Script.runInContext (node:vm:141:12)
▲  at runInContext (node:vm:291:6)
▲  at evaluateInContext (/app/***/node_modules/next/dist/server/web/sandbox/context.js:361:38)
▲  at getRuntimeContext (/app/***/node_modules/next/dist/server/web/sandbox/sandbox.js:68:9)
▲  at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
▲  at async /app/***/node_modules/next/dist/build/utils.js:975:29
▲  at async Span.traceAsyncFn (/app/***/node_modules/next/dist/trace/trace.js:103:20)
▲  /app/***/.next/server/edge-runtime-webpack.js:196
▲  /******/ 		__webpack_require__.b = document.baseURI || self.location.href;

I checked everything in my application and I'm sure I'm using use client for all the client components which uses dom functionalities. I hadn't this issue before and my app was working after upgrading to latest version of next and @cloudflare/next-on-pages I get this errors.
Reproduction
No response
Pages Deployment Method
Pages CI (GitHub/GitLab integration)
Pages Deployment ID
No response
Additional Information
No response
Would you like to help?

[ ] Would you like to help fixing this bug?

Also the not-found.js doesn't seems to be working with edge runtime,
import dynamic from 'next/dynamic';

export const runtime = 'edge';

const Error404 = dynamic(() => import('@/components/404/Error404'));

export default function NotFound() {
  return <Error404 />;
}

error:
⚡ ERROR: Failed to produce a Cloudflare Pages build from the project.
⚡
⚡ 	The following functions were not configured to run with the Edge Runtime:
⚡ 		- _error.func

Hello, your document is not defined error is occurring during the Next.js build step from the Vercel CLI. This is indicated by the little triangles at the start of the messages.
I'm afraid we won't really be able to help much because of that 🙁 - it's something out of our control and would indicate that there's either a bug with Next.js or an issue with your code, because it's occurring while Next.js tries to build.
Does your app build fine when you just use npx vercel build instead of npx @cloudflare/next-on-pages?
p.s. I noticed that you environment information says you are using v0.10.1. Please double check that you are using the latest version of next-on-pages (v1.0.1) 🙂
(I'll leave discussion about the _error.func problem for the other issue you opened)

after a lot of investigations I found that web worker causing this issue, it wasn't easy since I'm converting a large project to cloudflare pages.

@anonymouscatcher awesome to hear that you solved it :smiley:
Please let us know if you find anything DX related that you think we could do to make such type of conversions easier :slightly_smiling_face:

Hi @anonymouscatcher, how did you solve this issue? I am facing the same issue when trying to import @ffmpeg/ffmpeg in an edge runtime route.

@clmnin I think @ffmpeg/ffmpeg uses Web Workers, which aren't supported in edge runtime environments


zoom-in/out image by pinch gesture(It doesn't work when one finger is on the picture and the other is on the black background)

[x] bug

[x] enhancement

[ ] feature-discussion (RFC)

Swiper Version: 4.5.1

Platform/Target and Browser Versions: android / Chrome 79

Live Link or JSFiddle/Codepen or website with isssue: official demo

What you did
try zoom-in/out image by pinch gesture.
It doesn't work when one finger is on the picture and the other is on the black background
Expected Behavior
zoom-in/out image by pinch gesture
Actual Behavior
none

img{pointer-events: none} can solve this problem, but it will lead to other problems, such as the inability to long press to save pictures in webView


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-yml-archive-non-versioning-archive/pull/40 is merged into live branch.
Auto archive content to https://github.com/VSC-Service-Account/docs-yml-archive-non-versioning-archive.git

Docs Build status updates of commit ea4c46d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/TOC.yml
:white_check_mark:Succeeded
View

docs/index.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-3.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-3.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Break and Continue Statment

Description 📜
I have made documentation  on break and continue statements used in cpp. I have also included code snippets in md file. Please Review
Batch-2
Fixes #2589

Type of change 📝

[X] Documentation (Content Creation in the form of codes or tutorials)

Domain of Contribution 📊

[ ] Android Dev #(Flutter)
[ ] Android Dev #(Java)
[ ] Android Dev #(Kotlin)
[ ] Backend Dev #(Java)
[ ] Backend Dev #(.NET)
[ ] Backend Dev #(PHP)
[ ] Backend Dev #(Python)
[X] C/CPP
[ ] Competitive #Programming
[ ] Cyber #Security
[ ] DS#A
[ ] Data#base
[ ] Datascience with #Python
[ ] Datascience with #R
[ ] Frontend Dev #HTML/CSS/JS
[ ] Frontend Dev #React/Angular/Vue
[ ] Go#lang
[ ] Interview #Prep
[ ] Java_#Domain
[ ] Java#Script
[ ] ME#RN
[ ] Machine #Learning
[ ] Open #Source
[ ] Python_#Domain
[ ] Ru#st
[ ] Statis#tics
[ ] UI/#UX

Checklist ✅

[X] I follow Contributing Guidelines & Code of conduct of this project.
[X] I have performed a self-review of my own code or work.
[X] I have commented my code, particularly in hard-to-understand areas.
[X] My changes generates no new warnings.
[X] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

@Saviour1001 @Suvraneel this topic is already present in repo

@gunjan-g   there are 2 files that are already been merged on the same topic, then what's wrong here? And I think yesterday in meeting sir told they are looking for content because there 1000+ contribution

This topic already exists here. Thus closing this PR, you can provide the content you wrote in form of audio/video format and make a new PR.


PHP 7 Compatibility

Hello!
Could you please make it compatible with php7.
Class name Resource is not allowed.

Not true, it's a soft reserved word. From the PHP manual:

The following list of words have had soft reservations placed on them. Whilst they may still be used as class, interface, and trait names (as well as in namespaces), usage of them is highly discouraged since they may be used in future versions of PHP.

Going to close as this appears to not be an issue. Feel free to open a new issue if you observe other problems with PHP 7 support. Thanks!


Added a down caret to getting started link

Fixes #1655
Describe the changes you have made in this PR -
Added a downward caret to getting started link in the header to indicate that it is a dropdown.

Coverage remained the same at 88.045% when pulling 53183db34e0df6c1cabe46a95d72d221de4bd739 on HADES-01:HADES-01-patch-1 into 438f12ef516a25cc99816de18016e6a692541ace on CircuitVerse:master.

Please add screenshots

@HADES-01 It must have been hidden somewhere in the classes defined there. Can you check and rather remove that additional css property?

@aayush-05 I think I've found the faulty class which is navbar-dropdown-toggle-hidden in the parent element. Removing it brings the caret back but its position is all messed up like this

I've found the cause of this fault as well, It is happening because the  dropdown-toggle::after has been override in the application's CSS because otherwise the caret adjacent to the name of logged-in user gets messed up. Should I make both changes ?

@HADES-01 limiting overriding css to only the username dropdown caret should do

@HADES-01 limiting overriding css to only the username dropdown caret should do

@aayush-05 I already did that and it works just fine.

@aayush-05 First solution was not working now but I have fixed it.
Screenshot


Refactored code and created tensorflow backend

This is a big change, but I think it is for the better. (See https://github.com/google/TensorNetwork/issues/51 for details).
The next backend we will add will be a pure numpy implementation, then JAX, and then leave torch to the community.

This is a big design change so I would appreciate your inputs.

Also, I'm not sure how switching backends will be implemented.

Two ways (I'm waiting on stavros building the numpy backend before trying it).

Doing tensornetwork.TensorNetwork(backend='numpy')
Defaulting to the global backend, and changing the global backend with tensornetwork.set_backend('numpy')

but it seems conceivable that someone could try to merge two networks created using two different backends. How do we deal with that?

Easiest thing to do is throw an error. We can check that the backends are the same before merging, which is pretty easy. We could have a converter by changing each node's tensor by doing torch.Tensor -> np.array -> tf.Tensor, but I expect that would get messy and I'm not sure people would use it often enought to justify the complexity.
All 4 backends we plan on supporting right now (JAX/PyTorch/TF/numpy) allow tensors to be created by converting a np.array to their own Tensor type. All higher level network creators we build would just have to build nodes using numpy and they would get converted internally.

network_components and ncon_interface need to be updated as well, right?

Yes they do,


Change volume through alexa_media_player

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
It will be great to be able to change the volumen of a device before sending an announce. I have not found it implemented so I have scrapped the json code of a routine that makes it.
Describe the solution you'd like
A clear and concise description of what you want to happen.
I would like to change volume through a command or service.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
Here it is the code I have scrapped from an Alexa routine:
sequence: {
@type: "com.amazon.alexa.behaviors.model.Sequence",
sequenceId: "amzn1.alexa.sequence.my_id",
startNode: {
@type: "com.amazon.alexa.behaviors.model.OpaquePayloadOperationNode",
type: "Alexa.DeviceControls.Volume",
skillId: "amzn1.ask.1p.alexadevicecontrols",
operationPayload: {
customerId: "",
deviceType: "",
deviceSerialNumber: "",
value: 62,
locale: ""
},

Use the media_player.volume_set service. Example.

Thank you! I will use it.
El vie., 4 oct. 2019 a las 4:14, Alan Tse<EMAIL_ADDRESS>escribió:

Use the media_player.volume_set service. Example
https://github.com/custom-components/alexa_media_player/wiki/Automation-examples#text-to-speech-tts
.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/custom-components/alexa_media_player/issues/405?email_source=notifications&email_token=AHRXVD5MI4PRKATG6F2DNKDQM2RG7A5CNFSM4I5BVXU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAKEKUA#issuecomment-538199376,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHRXVD2T5MNOCYY57PIPYLTQM2RG7ANCNFSM4I5BVXUQ
.


Unexpected token: name (SVG)

2.0.0-alpha.1
My webpack loader config is the default one
{
    test: /\.(svg)$/,
    use: [{
      loader: 'react-svg-loader'
    }]
  }

Which outputs
class SVG extends __WEBPACK_IMPORTED_MODULE_0_react___default.a.Component {
  render() {
    return __WEBPACK_IMPORTED_MODULE_0_react___default.a.createElement(
      "svg",

And the error is:
[19:53:28] Error: Fix the following webpack build errors:

main.2de7c4a952203664e4cf.js from UglifyJs
Unexpected token: name (SVG)

So it doesn't compile class to ES5 syntax.
What is the Webpack loader config for the default behaviour with ES5 transpilation?
Perhaps it would make sense to make it the default behaviour since no one would use classes in their JS currently.

You should use babel-loader to transpile to es5
An example with webpack 2 and above is here - https://github.com/boopathi/react-svg-loader#webpack-2x ..

This is still not resolved.
And this is still not a "question" and is a bug instead.
Not to mention that it should transpile to ES5 by default without adding any additional options, it throws yet another error.
./assets/images/close.svg
Module build failed: SyntaxError: Unexpected token (4:11)

  2 | export default class SVG extends React.Component {
  3 |   render() {
> 4 |     return <svg viewBox="0 0 22 21" xmlns="http://www.w3.org/2000/svg" {...this.props}><title>0ECB348C-8E50-4195-AB44-FDEF7D1C0481</title><g stroke="#555A5E" strokeWidth="2" fill="none" fillRule="evenodd" strokeLinecap="round"><path d="M1.808 1.308l18.384 18.384M20.192 1.308L1.808 19.692" /></g></svg>;
    |            ^
  5 |   }
  6 |
  7 | }

Error
    at transpile (/Users/kuchumovn/work/JITUApp/node_modules/babel-loader/lib/index.js:61:13)
    at Object.module.exports (/Users/kuchumovn/work/JITUApp/node_modules/babel-loader/lib/index.js:163:20)

For non-default Webpack loader configuration
{
    test: /\.(svg)$/,
    use: [{
      loader: 'babel-loader'
    }, {
      loader: 'react-svg-loader'
    }]
  }

I'm migrating back to svg-react-loader.

Oh, I got it now, it seems to work – the latest 2.0.0-alpha.1 version has to be used, not @latest which is 1.x.
Ok, this is still more verbose than svg-react-loader and also svg-react-loader handles <style/> tags (and this library gave me errors so I migrated <style/> tags inside SVG to inline styles by hand).
This issue is resolved then.

900% agree was very confused as well

I ended up changed to another loader as well.

Oh, I got it now, it seems to work – the latest 2.0.0-alpha.1 version has to be used, not @latest which is 1.x.
And the correct Webpack config is:
{
    test: /\.svg$/,
    use: [{
      loader: 'babel-loader'
    }, {
      loader: 'react-svg-loader'
    }]
  }

This is still more verbose than svg-react-loader and also svg-react-loader handles <style/> tags and CSS classes (and this library gave me errors so I migrated <style/> tags inside SVG to inline styles by hand).
But at the same time the author of svg-react-loader doesn't communicate at all in the issues and PRs.
This issue is resolved then.
UPDATE
Migrating back to react-svg-loader because svg-react-loader has a filename bug
jhamlet/svg-react-loader#72

Thanks!! I was able to solve issue.


Introduce new API for debouncer and Async

This PR is aimed to provide fine-tuning for scheduling async work without breaking any of the legacy APIs.
Why?
Polymer 1 includes a few utility methods for scheduling async work and debouncing functions. These methods come in the form of Polymer.Base.debounce and Polymer.Base.Async. They both allow to schedule work that runs in either the next micro task or when a timer fires if a wait time is provided. One great thing about this implementation is the ability to flush all the async work at any given time for testing, debugging, or managing async dependencies.
However, in many cases [1], [2], [3], async work needs to happen after browser layout or when the main threat is idle. Similarly, some debounce functions should run during these periods to ensure correctness and improve performance.
[1] Measuring DOM elements.
[2] Incremental rendering.
[3] Expensive work in general (no DOM related).
In Polymer, there are a few relevant cases:

rAF: Layout needs to happen before doing work on the connected callback, the "resizeHandler"(responding to the iron-resize event) or some observer to a property.

Incremental rendering in iron-list where the timing for the debouncer is changed depending on these factors:

Rendering work on the attached callback goes after rAF.
Similarly, iron-resize work is done after rAF.
on-screen items is done within a micro task.
off-screen items is done during idle periods.

Changes for consideration

Polymer.Async.run -> Polymer.Async.microTask.run or Polymer.Async.timeOut.run Potentially avoidable by adding a run and cancel method to Polymer.Async

Polymer.Debouncer.debounce(debouncer, callback, wait, context) -> Polymer.Debouncer.debounce(debouncer, asyncModule, callback) Also potentially avoidable if checking arguments.length

Fixes https://github.com/Polymer/polymer/issues/3895

I'm a little confused by the chaining API you have proposed here. Would it ever make sense to make a debouncer and not call after or run on it?
If not, we could just make an API that looks more like the older API, but just take an object for the wait field that corresponds to what you have in after.
You could also drop context by requiring users write() =>{} notation or function binding for the callback.
Example:
Polymer.Debouncer.debounce(
  job: object,
  callback: fn,
  asyncModule: {run: fn, cancel: fn},
  ...moduleArgs: passed to asyncModule.run
);

WDYT?

@azakus That is a fair point. I think the only reason for such change was "it's more readable". I originally intended to make Polymer.Debouncer.debounce().after() "thenable".

PTAL @azakus @sorvell

LGTM from @sorvell

yay 🎉 🙌


Remove fromArray, fromPromise in favor of just from

Now that from does exactly the same thing as fromArray or fromPromise if an array or a promise is passed to it, perhaps we can remove those two methods to reduce the API surface area.
This is similar to the removal of just, value and return in favor of just using of.

@blesh I am in favor of this

After @kwonoj generously made a PR around this, and some experimentation with performance, from(array) has proven to be much slower than fromArray(array). So much so that I'm going to close this issue.
Thanks @kwonoj, if not for your PR, we wouldn't have known.

It is glad I could find out this :) Will continue effort on other topics. Thanks!


better-sqlite3: migrations with consecutive changes to same table fail with “SQL logic error”

Environment
Knex version: 1.0.1
Database + version: sqlite3 3.34.1
OS: Linux
Bug
Migrations with multiple consecutive changes to the same table (workaround to #4450) fail with the error message SQL logic error when using the new better-sqlite3 driver support. For the below code:
const Knex = require('knex');

const knex = Knex({
  client: 'better-sqlite3',
  connection: 'test.db'
});

(async function run() {
  // first migration
  await knex.schema.createTable('events', t => {
    t.string('id').primary();
    t.enu('action', ['activation']);
  });

  // second migration
  await knex.schema.alterTable('events', t => {
    t.dropColumn('action');
  });
  await knex.schema.alterTable('events', t => {
    t.enu('action', ['activation', 'cancellation'])
  });
})();

the following  output is produced:
knex:query create table `events` (`id` varchar(255), `action` text check (`action` in ('activation')), primary key (`id`)) undefined +0ms
knex:query PRAGMA table_info(`events`) undefined +1ms
knex:query BEGIN; trx2 +1ms
knex:query SELECT type, sql FROM sqlite_master WHERE (type='table' OR (type='index' AND sql IS NOT NULL)) AND tbl_name='events' trx2 +0ms
knex:query COMMIT; trx2 +0ms
knex:query PRAGMA foreign_keys trx2 +4ms
knex:query PRAGMA foreign_keys = OFF trx2 +0ms
knex:query BEGIN; trx3 +0ms
knex:query CREATE TABLE `_knex_temp_alter138` (`id` varchar(255), PRIMARY KEY (`id`)) trx3 +0ms
knex:query INSERT INTO "_knex_temp_alter138" SELECT "id" FROM "events"; trx3 +0ms
knex:query DROP TABLE "events" trx3 +1ms
knex:query ALTER TABLE "_knex_temp_alter138" RENAME TO "events" trx3 +0ms
knex:query PRAGMA foreign_key_check trx3 +0ms
knex:query COMMIT; trx3 +0ms
knex:query PRAGMA foreign_keys = ON trx3 +0ms
knex:query alter table `events` add column `action` text check (`action` in ('activation', 'cancellation')) trx3 +0ms
(node:41249) UnhandledPromiseRejectionWarning: SqliteError: alter table `events` add column `action` text check (`action` in ('activation', 'cancellation')) - SQL logic error
    at Database.prepare (/tmp/abc/node_modules/better-sqlite3/lib/methods/wrappers.js:5:21)
    at Client_BetterSQLite3._query (/tmp/abc/node_modules/knex/lib/dialects/better-sqlite3/index.js:30:34)
    at executeQuery (/tmp/abc/node_modules/knex/lib/execution/internal/query-executioner.js:37:17)
    at Client_BetterSQLite3.query (/tmp/abc/node_modules/knex/lib/client.js:146:12)
    at Runner.query (/tmp/abc/node_modules/knex/lib/execution/runner.js:130:36)
    at Runner.queryArray (/tmp/abc/node_modules/knex/lib/execution/runner.js:224:21)
    at ensureConnectionCallback (/tmp/abc/node_modules/knex/lib/execution/internal/ensure-connection-callback.js:11:19)
    at Runner.ensureConnection (/tmp/abc/node_modules/knex/lib/execution/runner.js:307:20)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

This used to work with knex 0.95 and the old sqlite3 driver. For comparison, here is the output for a successful run of the same migration code with 0.95+sqlite3:
knex:query create table `events` (`id` varchar(255), `action` text check (`action` in ('activation')), primary key (`id`)) undefined +0ms
knex:query PRAGMA table_info(`events`) undefined +1ms
knex:query BEGIN; trx2 +1ms
knex:query SELECT type, sql FROM sqlite_master WHERE (type="table" OR (type="index" AND sql IS NOT NULL)) AND tbl_name="events" trx2 +1ms
knex:query CREATE TABLE `_knex_temp_alter307` (`id` varchar(255), PRIMARY KEY (`id`)) trx2 +5ms
knex:query INSERT INTO _knex_temp_alter307 SELECT "id" FROM events; trx2 +1ms
knex:query DROP TABLE "events" trx2 +0ms
knex:query ALTER TABLE "_knex_temp_alter307" RENAME TO "events" trx2 +0ms
knex:query COMMIT; trx2 +0ms
knex:query alter table `events` add column `action` text check (`action` in ('activation', 'cancellation')) trx2 +1ms

gonna go ahead and +1 this, just started using knex, and am hesitant to try out migrations.
I usually use Joshua's better-sqlite3 on its own, manually i guess you can say, and usually handle migrations by hand or using custom scripts.
I went to research and see how well knex migrations are handled, but seeing this year old issue basically regarding my concern, having no dev interaction at all even though the project is actively maintained, makes me think my time is better spent handwriting migration scripts than learning knex migrations.
I REALLY hope the dev jumps in and gives some feedback, I simply don't have the time to write a bunch of tests to verify myself, and I believe testing is an authors responsibility anyways. I have a knex/better-sqlite3 requirement for this project, and this ignored issue is gonna be the reason I give my client why I wont include knex migrations
again, HOPEFULLY, the devs get to this and clear the air up, I do get quite tired of handwriting migrations, but to me, I'd rather do that and ensure functionality than deal with annoying integration bugs later on

Issue is old and slipped through the cracks as there wasn't any activity around it. We'll take a look at it, thank you for the ping.


ScoreboardM Project

Thanks for the PR. Could you please update your script file so the header matches the format:
// Script example for ScriptAPI
// Author: GamerFile <https://github.com/GamerFile>
// Project: https://github.com/JaylyDev/ScriptAPI

Also I believe the script has some errors. This must be fixed.
scripts/ScoreboardM/index.js(93,21): error TS2322: Type 'number' is not assignable to type '{ setObj: (id: string, v: string) => ...; hasObj: (id: string) => boolean; getObj: (id: string) => any; newObj: (id: string, v: string) => ...; setScore: (target: any, Objective: string, score: number) => ...; ... 7 more ...; setDisplaySlot: (id: string, opt: any) => ...; }'.
scripts/ScoreboardM/index.js(96,13): error TS2322: Type 'number' is not assignable to type '{ setObj: (id: string, v: string) => ...; hasObj: (id: string) => boolean; getObj: (id: string) => any; newObj: (id: string, v: string) => ...; setScore: (target: any, Objective: string, score: number) => ...; ... 7 more ...; setDisplaySlot: (id: string, opt: any) => ...; }'.

Ye i see
I'll fix

@bot174 What's up with those workflows?

the name has capital letters


EXSWCPHIPT-98 - [catch2] Added testing for hipFree API's

Closing since changes are a part of #2750


view home page

Describe the bug
the project runs without any problem detected. but when i enter my details and click on login an error page come with this massage (ip : http://localhost:8080/index) There was an unexpected error (type=Internal Server Error, status=500).
Error resolving template [fragments/headerinc], template might not exist or might not be accessible by any of the configured Template Resolvers (template: "index" - line 8, col 16). but i have check, the template exist and it is accessible.
please i help me to understand the problem.

Label is help!!  Not BUG

Please use template to describe bug ---> DON 'T Break your own  rules!! ..
Label here is help


Is it okay to remove compile flags?

Or does your plugin depend on them? For example out of -
SQLITE_ENABLE_FTS5
SQLITE_ENABLE_JSON1
SQLITE_ENABLE_RTREE
SQLITE_DEFAULT_CACHE_SIZE=-16000
SQLITE_DEFAULT_FOREIGN_KEYS=1
SQLITE_USE_URI=1
SQLITE_MAX_SCHEMA_RETRY=0

I really don't want - SQLITE_ENABLE_FTS5 & SQLITE_ENABLE_JSON1 so can I safely remove them? If yes, what would be the procedure of doing so? Or how about if I want to add some new compile time flags?

The only two compile flags that are required are SQLITE_USE_URI=1 and SQLITE_MAX_SCHEMA_RETRY=0. The rest of the flags are simply for convenience. Currently there's no way to override these flags, but it should be an easy feature to add. Give me an hour and I'll see what I can do.

It turns out that it would be a substantial effort to provide this functionality without breaking windows support, due to limitations with the gyp file format. I also noticed that sqlite3 doesn't allow this either. I'd like to add support for overriding configuration flags at some point, but I don't have time to attempt to solve it right now. If you're proficient with gyp files and cross-platform shell scripting, feel free to submit a pull request.

@JoshuaWise is there a manual way to do that so I could change something before building the plugin npm install?

To do it manually you would have to:

npm install
edit the file better-sqlite3/deps/sqlite3.gyp
node-gyp rebuild

Alternatively you can fork better-sqlite3 and change the better-sqlite3/deps/sqlite3.gyp directly in the repo. Of course, if you do that, you'll need to make sure to merge your fork with the official better-sqlite3 whenever I release patches

@JoshuaWise btw thankyou for creating and maintaining this plugin :)


enhancement: add clickable support on onClick

Description
add clickable support on onClick for CoreChip

Need to add href and target valid props.


wasmparser: Derive Hash for TypeDef

And everything transitively contained inside a TypeDef.

Actually nevermind, this doesn't handle equivalent module types whose entries are provided in different orders.


Add line & column info to errors

Ref: #332
Curently error has only .marker, making difficult to generate details for alternate formats.
Need to add .line and .column fields.

Ups... all info exists in mark.


Pre-select the scope with useGoogleLogin

Is it possible to pre-select (or make them mandatory) the scopes specified in the hook:
const googleLogin = useGoogleLogin({scope: "...", onSuccess: () =>{} }, flow: "auth_code")

No we can't make them mandatory, google doesn't provide that option
But you can check for accepted scopes to alert the user if missing some of them

I've found some services that does this, using the same scopes that I use.
Here is an example:

Then I found that hasGrantedAllScope(tokenResponse, "...") doesn't work with the onSuccess callback of useGoogleLogin (the type is different)

As I can remember token response has scopes property with accepted scopes
Try to log token response too see what inside it,
If it has accepted scopes you can compare them with your scopes manually

Try using overrideScope: true in the useGoogleLogin config, maybe that'll solve your issues. 🤷


Linear Search in C

This Pull Request resolves Issue #412
Description:
This PR implements a linear search in C language.

Thanks for Contributing!


fixed: a typo

Fixed a very tiny typo :D

LGBTM

May i have your explicit permission to re-license your contribution here to CC-BY-4.0?
https://creativecommons.org/licenses/by/4.0/deed.en

Yes, you may re-license my contribution. 😄


Add API to set timeout on requests towards the K8s API server

What this PR does / why we need it:
This PR adds a new flag --kube-apitimeout <duration> and the environment variable HELM_KUBEAPITIMEOUT
that can be used to set the timeout on requests towards the Kubernetes API server.
This enables users with problematic K8s cluster to override the default timeout and let the sent requests finish successfully.
Examples usage:
> helm --kube-apitimeout=45s install ...
I0325 18:11:02.994044 1138565 round_trippers.go:463] GET https://<IP_ADDRESS>:42357/version?timeout=45s
I0325 18:11:02.994051 1138565 round_trippers.go:469] Request Headers:
I0325 18:11:02.994060 1138565 round_trippers.go:473]     Accept: application/json, */*
I0325 18:11:02.994068 1138565 round_trippers.go:473]     User-Agent: Helm/3.13+unreleased

> helm env
...
HELM_KUBEAPITIMEOUT=""
...

> HELM_KUBEAPITIMEOUT=45s helm env
...
HELM_KUBEAPITIMEOUT="45s"
...

Closes #9805
Special notes for your reviewer:

[x] this PR contains unit tests

Just let me know if there are anything I should change.


IBC links are incorrect in README

Describe the feature
Hey there, you have mentioned in READM

NOTE: IBeam is not designed to automate logging into TWS or IB Gateway (also known as TWS Gateway). Use IBC for that. There are also Docker image projects that include TWS/Gateway and IBC.

But  both URLs are not found

@b3kan many thanks for pointing it out! Forgot to swap () for [] in markdown. Thanks! Already fixed 👍


Introduce new Quantinuum proj/app templates and remove Honeywell

Context
In November 2021, Honeywell became Quantinuum: Press release: Quantinuum is a result of the combination of two global leaders in quantum computing: Honeywell Quantum Solutions and Cambridge Quantum
In February/March 2022, Azure Quantum started supporting the Quantinuum provider and targets.
This PR
This PR adds new Quantinuum .NET/C#/Q# project templates, removes the project templates and other obsolete code related to Honeywell.
Also uses the latest target names from https://learn.microsoft.com/en-us/azure/quantum/provider-quantinuum

/azp run

Approving to unblock.
I would recommend more approvals for the renaming that is not evident for me.
-   <ExecutionTarget>honeywell.hqs-lt-1.0</ExecutionTarget>
---
+   <ExecutionTarget>quantinuum.qpu.h1</ExecutionTarget>

Thanks. These are the new Quantinuum targets that just got renamed.
@warren-jones worked on them and the documentation is here: https://learn.microsoft.com/en-us/azure/quantum/provider-quantinuum

Closed in favor of #1565


Add Azure AD B2C integration package

/cc: @Eilon

FYI. Merging right away

@javiercn this broke the build. PR checks were red for valid reasons. If you can't fix this soon (~next 10 min or so), we'll need to revert to unblock ProdCon.


Update DataflowRunner fnapi environment version

R: @tvalentyn
cc: @mdvorsky

Closing this, we may not be ready for this change.


Add initial PSNeo4j page

Hiyo!
Let me know if there's anything that should change - if not, will go ahead and add some other modules : )  Some have blog posts, others like this don't (yet).
Guessing you have some way to parse the files and generate an index, looking at your blog? : )
Cheers!

It's perfect @RamblingCookieMonster thank you for your contribution!
Feel free to add other modules.
No problem if they don't have blog posts/videos yet. let the world know that it will be a thing 😄
Thank you


Add model directories to the source directories

Background

What do these changes do?

Marks model directories as the sources directories in gradle.build files

Why are they important?

This helps IntelliJ to identify those directories as sources and use the Smithy IntelliJ plugin on those smithy files in those directories.
Testing

How did you test these changes?

Manually loading the project in IntelliJ.
Links

Links to additional context, if necessary
Issue #, if applicable (see here for a list of keywords to use for linking issues)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

This should be fixed in the IntelliJ plugin, we are looking into that.


Add InplaceInputRequirement

[ ] conformance tests
[ ] cwltool support
[ ] cwl-upgrader support

What is the syntax if I want to try this out?

@SpheMakh This is available in v1.0 as an extension in the CWL reference implementation and those that extend it (toil-cwl-runner, Arvados, possibly REANA): https://github.com/common-workflow-language/common-workflow-language/issues/380#issuecomment-349598366


Discord invite link expired

Strange, this is the current link: https://discordapp.com/invite/dMYfDPM
From what I see, the invite link has not expired yet (was set to never expire). Where did you notice an expired link?

Closing this for now, though let me know if there are any updates.


Forbid use of {} for object construction

Feature request:
Bad:
kids = {
  brother:
    name: "Max"
    age: 11
  sister:
    name: "Ida"
    age: 9
}

Good:
kids =
  brother:
    name: "Max"
    age: 11
  sister:
    name: "Ida"
    age: 9

The issue is that sometimes you have to have {}. For example, in return:
return {
  brother:
    name: "Max"
    age: 11
  sister:
    name: "Ida"
    age: 9
}

It does not work without.

+1

another consideration is inline / single line object construction, as well as taking into account object the syntactic sugar used for shorthand construction / deconstruction
red = 'stop'
green = 'go'
{ red, green } #=> {red: 'stop', green: 'go'}

as well as
example =
  red: 'stop'
  green: 'go'
{red, green} = example
red #=> 'stop'
green #=> 'go'


Run

Command Name
"Run"
Git Command(s)
run any command
Dialog Input (if applicable)

a single line input to type a command to run
maybe even list all files like Commit All so they could select which files the command should apply to

Input Validation
none?

will need some interpolation variables like %files%

would be nice if there was an auto complete on commands and options

implemented in v0.15.9


custom metrics in skill table

Hi,
As was discussed here https://github.com/DHI/modelskill/issues/226 I needed to have some custom metrics in the skill table, so I implemented an option to "add metrics" on demand, just by appending them to the sets DEFINED_METRICS and METRICS_WITH_DIMENSION if that is the case.
The code that was failing in issue/226 now works like this (I added two metrics one with units and one without for this example)

I added some tests as well

In your example you refer to the custom metrics as python functions. Is it a requirement that the function is in scope, i.e. global scope or can you also refer to it by string, e.g. 'pr'?

I have it implemented as python function, since that is the only way I can think of to add a custom metric.
And then I am looking at the name of the function when adding it to the list. For instance if I define:
def pr(obs,model):
    return mean(obs/model)
then when adding pr to the defined metrics I actually add pr.__name__
which I understand is the same that is being done here https://github.com/DHI/modelskill/blob/6dc27ec270849f19ce7573a749d7f97c569c8ab4/modelskill/metrics.py#L605
I have not actually tried to then just use 'pr' as a str

I think it's great that you guys are working on custom metrics and we probably need that. Great. But if you have some metrics that you use over and over again I also think we should add these to the metrics module (in another PR).

@jsmariegaard: that's exactly what I suggested in my last comment!
If the user finds him/herself reusing a metric time and time again, it is better to add it to metrics.py, but it is also important to have this feature of custom metrics available :)

@jsmariegaard: that's exactly what I suggested in my last comment! If the user finds him/herself reusing a metric time and time again, it is better to add it to metrics.py, but it is also important to have this feature of custom metrics available :)

TL;DR 😳
But @daniel-caichac-DHI why didn't you make that PR with your favorite metrics then 🤔?

I will do it, after this PR is merged, otherwise the "custom metric" will not be added! Which I also need for other projects

Is it peak-ratio and explained variance?

Explained variance == $R^2$ ?

Is it peak-ratio and explained variance?

Explained variance == R2 ?

It gives very different results to R2 as is implemented in modelskill

Is it peak-ratio and explained variance?

Explained variance == R2 ?

 It gives very different results to R2 as is implemented in modelskill

R2 is often referred to as explained variance which is why I think it is pretty confusing with another metric with a similar name giving other results, do you have any authoritative reference other than the screenshot🤨?


Getting Stackoverflow error when compiling my project in android studio

Describe the bug
Currently, I'm using these many HMS-core libraries along with some google libraries in my project.
    implementation 'com.google.android.gms:play-services-base:17.6.0'
    implementation 'com.google.android.gms:play-services-maps:18.0.0'
    implementation 'com.google.android.gms:play-services-location:18.0.0'
    implementation 'com.google.android.gms:play-services-oss-licenses:17.0.0'
    implementation 'com.google.android.gms:play-services-auth:19.2.0'

    implementation 'com.huawei.hms:location:<IP_ADDRESS>0'
    implementation 'com.huawei.hms:site:<IP_ADDRESS>1'
    implementation 'com.huawei.hms:maps:<IP_ADDRESS>1'
    implementation 'com.huawei.hms:push:<IP_ADDRESS>0'
    implementation 'com.huawei.hms:scan:<IP_ADDRESS>0'

and In my app->Build.gradle these many plugins I'm using
apply plugin: 'com.android.application'
apply plugin: 'com.google.gms.google-services'
apply plugin: 'com.google.android.gms.oss-licenses-plugin'
apply plugin: 'kotlin-android'
apply plugin: 'kotlin-parcelize'
apply plugin: 'com.huawei.agconnect'

When compiling and installing apk in the emulator at that time I'm getting this error. please check the attached screenshots.
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:getDependencies'.
> java.lang.StackOverflowError (no error message)

Screenshots

Desktop (please complete the following information):

Gradle version: 7.0.3
Android Studio version: Android Studio Arctic Fox | 2020.3.1 Patch 3

Additional context
Note:  If I'm commenting out this line or using older versions of gms libraries in that case it works fine.
// apply plugin: 'com.google.android.gms.oss-licenses-plugin'
implementation 'com.huawei.hms:location:<IP_ADDRESS>3'
implementation 'com.huawei.hms:site:<IP_ADDRESS>0'
implementation 'com.huawei.hms:maps:<IP_ADDRESS>1'
implementation 'com.huawei.hms:push:<IP_ADDRESS>1'
implementation 'com.huawei.hms:scan:<IP_ADDRESS>0'

Is there a workaround for this issue? kindly, suggest.

May i ask will there still facing this issue if you do not reference the HMS libraries ?

Yes, even with
implementation 'com.huawei.hms:location:<IP_ADDRESS>3'
implementation 'com.huawei.hms:site:<IP_ADDRESS>0'
implementation 'com.huawei.hms:maps:<IP_ADDRESS>1'
implementation 'com.huawei.hms:push:<IP_ADDRESS>1'
implementation 'com.huawei.hms:scan:<IP_ADDRESS>0'

these versions working fine,
but when I'm using the latest versions of HMS libraries at that time facing issues,
Here, attaching your mapkit demo for your reference.
kotlin.zip

Please try to update the AppGallery Connect Plugin, the latest version is classpath 'com.huawei.agconnect:agcp:<IP_ADDRESS>0'

yes, I have tried that one also but didn't work.

Try to add implementation ‘com.huawei.hms:network-common:<IP_ADDRESS>0’ before all HMS dependencies

yes, by using
implementation ‘com.huawei.hms:network-common:<IP_ADDRESS>0’
I can able to create Build but, I want to ask by using this lib is there a Knock-on effect on other functionality?
Because after using this solution my site query suggestion searching API always gives errors.
HMSSDK_TaskApiCall: doExecute, uri:site.querySuggestion, errorCode:1212, transactionId:101677875estion20211206113837991921108
HmsSiteKit_QuerySuggestionTaskApiCall_70: responseErrorCode errorCode = 1212 errorReason = need update kit

If I use the old version build everything works fine, I can get proper response from site query suggestion searching API.
Please let me know.

Sorry, it's a bug. We will fix that in 6.3.0 version. The next version will be released in the end of December or the middle of January.

yes, by using
implementation ‘com.huawei.hms:network-common:<IP_ADDRESS>0’
I can able to create Build but, I want to ask by using this lib is there a Knock-on effect on other functionality?
Because after using this solution my site query suggestion searching API always gives errors.
HMSSDK_TaskApiCall: doExecute, uri:site.querySuggestion, errorCode:1212, transactionId:101677875estion20211206113837991921108
HmsSiteKit_QuerySuggestionTaskApiCall_70: responseErrorCode errorCode = 1212 errorReason = need update kit

If I use the old version build everything works fine, I can get proper response from site query suggestion searching API.
Please let me know.

About the errorCode:1212, please try to update the hms core version, you can reference this document

Okay, will wait for new updates, Thank you for your support.

@dixitpTheaa This issue have been sloved in the latest release, please try again.

Okay, thank you, for your support.


Clean up and indenting

Stylesheet and JavaScript is changed too. Making pulls for those now.

Kindly rebase with master and take a look into the conflicts.

Also checkout #150 that looks more aesthetic. Maybe you can add some of these changes to that.

Hmm. This is my first time with a conflict in github. I'm clicking random buttons right now.

All right, I think I've got it now. Onclick animated scroll was added to the nav in the header, and a h3 title was placed in the header too. That's all the changes that was made, I think.

Okay I'll help you out here. So basically between the time when you cloned your branch to the time when you submitted your PR, some PRs got accepted and it changed the code. So for eg. here you can see that home.html got changed. This happens often when you are making changes to important files which are very frequently being developed. First save whatever changes you made in some other file out of the repo. I'll take a look into your new patch here, but I hope you have made your changes in accordance with the new site. Otherwise do a git pull for the updates take a look at the changes and then make suitable commits.

I say remove the header, make sure the contact form has enough margin and there is a bounding box around it. Other smaller changes are fine for merging.

I agree, the hacking animation do belong on the top instead of the footer for sure. Nicer up there.
I just examined #150 more closely, it appears that I only missed the hacking animation in the footer with my newbie merge. Removing the title from the footer now.

I am not sure what you're saying about the header. The h3 title should fit nicely in the header and be easier to read due to the single color background than it would be on the start pictures.

The sun is up, and I'm quickly becoming too tired to stay awake any longer. I should be back online in about seven to nine more hours. My red-eyed merging might have caused more bad merges than otherwise.

Well. Your efforts have been valiant, I am trying to run all your changes locally. I'll try my best to merge it. sleep tight!

See #175


fix(report): text contrast and consistent yellow traffic light

Fix contrast in text of alert section
Use consistent yellow/orange throughout the report for traffic lights

Is there any visual change that I should observe here? Did not see much difference after the visual inspection.

Yes, see it now - looks good! Thanks for the elaboration.


Clean up controller classes

Additional clean ups of the controllers
Change List

Move map-specific rotation logic into MapController
Support keyboard navigation and transition in both OrbitController and OrthographicController

Coverage increased (+0.009%) to 61.409% when pulling 2adb4b667530ad819fa23a79e5e3b4e400ea57a4 on controllers-cleanup into 77d8742e822b02a04f49edb52d4940270269803d on ortho-view-commonspace.


无法运行 sudo pip3 install git + https：//github.com/Xilinx/QNN-MO-PYNQ.git命令

无法运行 sudo pip3 install git + https：//github.com/Xilinx/QNN-MO-PYNQ.git命令
显示错误：
Invalid requirement: '+'
Traceback (most recent call last):
File "/usr/share/python-wheels/packaging-17.1-py2.py3-none-any.whl/packaging/requirements.py", line 93, in init
req = REQUIREMENT.parseString(requirement_string)
File "/usr/share/python-wheels/pyparsing-2.2.0-py2.py3-none-any.whl/pyparsing.py", line 1632, in parseString
raise exc
File "/usr/share/python-wheels/pyparsing-2.2.0-py2.py3-none-any.whl/pyparsing.py", line 1622, in parseString
loc, tokens = self._parse( instring, 0 )
File "/usr/share/python-wheels/pyparsing-2.2.0-py2.py3-none-any.whl/pyparsing.py", line 1379, in _parseNoCache
loc,tokens = self.parseImpl( instring, preloc, doActions )
File "/usr/share/python-wheels/pyparsing-2.2.0-py2.py3-none-any.whl/pyparsing.py", line 3395, in parseImpl
loc, exprtokens = e._parse( instring, loc, doActions )
File "/usr/share/python-wheels/pyparsing-2.2.0-py2.py3-none-any.whl/pyparsing.py", line 1379, in _parseNoCache
loc,tokens = self.parseImpl( instring, preloc, doActions )
File "/usr/share/python-wheels/pyparsing-2.2.0-py2.py3-none-any.whl/pyparsing.py", line 3717, in parseImpl
return self.expr._parse( instring, loc, doActions, callPreParse=False )
File "/usr/share/python-wheels/pyparsing-2.2.0-py2.py3-none-any.whl/pyparsing.py", line 1379, in _parseNoCache
loc,tokens = self.parseImpl( instring, preloc, doActions )
File "/usr/share/python-wheels/pyparsing-2.2.0-py2.py3-none-any.whl/pyparsing.py", line 3378, in parseImpl
loc, resultlist = self.exprs[0]._parse( instring, loc, doActions, callPreParse=False )
File "/usr/share/python-wheels/pyparsing-2.2.0-py2.py3-none-any.whl/pyparsing.py", line 1383, in _parseNoCache
loc,tokens = self.parseImpl( instring, preloc, doActions )
File "/usr/share/python-wheels/pyparsing-2.2.0-py2.py3-none-any.whl/pyparsing.py", line 2689, in parseImpl
raise ParseException(instring, loc, self.errmsg, self)
pyparsing.ParseException: Expected W:(abcd...) (at char 0), (line:1, col:1)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/pip/req/req_install.py", line 82, in init
req = Requirement(req)
File "/usr/share/python-wheels/packaging-17.1-py2.py3-none-any.whl/packaging/requirements.py", line 97, in init
requirement_string[e.loc:e.loc + 8]))
pip._vendor.packaging.requirements.InvalidRequirement: Invalid requirement, parse error at "'+'"

No space needed, the command is git+https.


fix: support more combinations of volumes and bind mounts for docker compose transpiler

@tedim52  this is super janky at the moment
so the logic is
mount everything to /tmp/volume-name/<folder/file name>
then change the entrypoint + cmd to overwrite the target dir with contents.
appreciate any feedback & improvement to this logic

this can be merged even with the git guardian secrets error - i need to make a PR to update our git history to remove the fake env var PASSWORD secrets I used in testing but there are no actual secrets in git history

merged in https://github.com/kurtosis-tech/kurtosis/pull/2320


Build of PR #499 fails

Build PR #499 fails because of 1 test. This test locally succeeds.
Test output on Travis
--- FAIL: TestPruneNodeThreshold (50.87s)
    nodes_test.go:305: peers are not sharing nodes with eachother
FAIL
FAIL	github.com/threefoldtech/rivine/modules/gateway	72.452s

Closing this as it seems no longer relevant


Contradictory info in CA description for ZeroSSL

https://acmeclients.com/certificate-authorities/   section for ZeroSSL shows support community in both Pros and Cons sections.  Can't be both, but I don't know which is correct so can't submit a PR to fix.

Well spotted! Fixed now. No, they don't have any support community that I know of.


⚠ SkipTheCommericals has degraded performance

In bbb8af2, SkipTheCommericals ($STC) experienced degraded performance:

HTTP code: 200
Response time: 10553 ms

Resolved: SkipTheCommericals performance has improved in cce4d6e.


S3 PutObject Content Type Issue

Description

Documented by Kotlin here: https://github.com/awslabs/aws-sdk-kotlin/issues/193

We've added two changes to address this.

ContentTypeMiddleware is now changed to:

   if !input.builder.headers.exists(name: "Content-Type") {
            input.builder.withHeader(name: "Content-Type", value: contentType)
        }

We are applying .after to ContentTypeMiddlware in the chain of middlewares

The above approach is somewhat brittle in that a previous value must not have been set in order for this code to execute.  This is something in code generation that is not yet strongly modeled, and we'll need to revisit this when we go to figure out how middlewares should play nicely with each other.
Closing for now, with the intent of opening another ticket to address this broader issue.


[cinder / cinder-ceph] upgrading cinder will cause its subordinate cinder-ceph to failed on relation changed

Wait for up to 300s for app 'cinder' to reach the idle state ✖
2024-06-24 04:45:08 [ERROR] Timed out waiting for model:
  cinder/0 [executing] maintenance: Running openstack upgrade
2024-06-24 04:45:08 [ERROR] See the known issues at https://canonical-charmed-openstack-upgrader.readthedocs-hosted.com/en/stable/reference/known-issues/
unit-cinder-ceph-0: 05:24:20 WARNING unit.cinder-ceph/0.storage-backend-relation-changed Traceback (most recent call last):
unit-cinder-ceph-0: 05:24:20 WARNING unit.cinder-ceph/0.storage-backend-relation-changed   File "/var/lib/juju/agents/unit-cinder-ceph-0/charm/charmhelpers/core/strutils.py", line 94, in __init__
unit-cinder-ceph-0: 05:24:20 WARNING unit.cinder-ceph/0.storage-backend-relation-changed     self.index = self._list.index(item)
unit-cinder-ceph-0: 05:24:20 WARNING unit.cinder-ceph/0.storage-backend-relation-changed ValueError: tuple.index(x): x not in tuple
unit-cinder-ceph-0: 05:24:20 WARNING unit.cinder-ceph/0.storage-backend-relation-changed
unit-cinder-ceph-0: 05:24:20 WARNING unit.cinder-ceph/0.storage-backend-relation-changed During handling of the above exception, another exception occurred:
unit-cinder-ceph-0: 05:24:20 WARNING unit.cinder-ceph/0.storage-backend-relation-changed
unit-cinder-ceph-0: 05:24:20 WARNING unit.cinder-ceph/0.storage-backend-relation-changed Traceback (most recent call last):
unit-cinder-ceph-0: 05:24:20 WARNING unit.cinder-ceph/0.storage-backend-relation-changed   File "/var/lib/juju/agents/unit-cinder-ceph-0/charm/hooks/storage-backend-relation-changed", line 469, in <module>
unit-cinder-ceph-0: 05:24:20 WARNING unit.cinder-ceph/0.storage-backend-relation-changed     hooks.execute(sys.argv)
unit-cinder-ceph-0: 05:24:20 WARNING unit.cinder-ceph/0.storage-backend-relation-changed   File "/var/lib/juju/agents/unit-cinder-ceph-0/charm/charmhelpers/core/hookenv.py", line 963, in execute
unit-cinder-ceph-0: 05:24:20 WARNING unit.cinder-ceph/0.storage-backend-relation-changed     self._hooks[hook_name]()
unit-cinder-ceph-0: 05:24:20 WARNING unit.cinder-ceph/0.storage-backend-relation-changed   File "/var/lib/juju/agents/unit-cinder-ceph-0/charm/hooks/storage-backend-relation-changed", line 348, in storage_backend_changed
unit-cinder-ceph-0: 05:24:20 WARNING unit.cinder-ceph/0.storage-backend-relation-changed     storage_backend()
unit-cinder-ceph-0: 05:24:20 WARNING unit.cinder-ceph/0.storage-backend-relation-changed   File "/var/lib/juju/agents/unit-cinder-ceph-0/charm/hooks/storage-backend-relation-changed", line 320, in storage_backend
unit-cinder-ceph-0: 05:24:20 WARNING unit.cinder-ceph/0.storage-backend-relation-changed     subordinate_config = CephSubordinateContext()()
unit-cinder-ceph-0: 05:24:20 WARNING unit.cinder-ceph/0.storage-backend-relation-changed   File "/var/lib/juju/agents/unit-cinder-ceph-0/charm/hooks/cinder_contexts.py", line 71, in __call__
unit-cinder-ceph-0: 05:24:20 WARNING unit.cinder-ceph/0.storage-backend-relation-changed     if CompareOpenStackReleases(os_codename) >= "icehouse":
unit-cinder-ceph-0: 05:24:20 WARNING unit.cinder-ceph/0.storage-backend-relation-changed   File "/var/lib/juju/agents/unit-cinder-ceph-0/charm/charmhelpers/core/strutils.py", line 96, in __init__
unit-cinder-ceph-0: 05:24:20 WARNING unit.cinder-ceph/0.storage-backend-relation-changed     raise KeyError("Item '{}' is not in list '{}'"
unit-cinder-ceph-0: 05:24:20 WARNING unit.cinder-ceph/0.storage-backend-relation-changed KeyError: "Item 'zed' is not in list '('diablo', 'essex', 'folsom', 'grizzly', 'havana', 'icehouse', 'juno', 'kilo', 'liberty', 'mitaka', 'newton', 'ocata', 'pike', 'queens', 'rocky', 'stein', 'train', 'ussuri', 'victoria', 'wallaby', 'xena', 'yoga')'"

Environment: OpenStack deployed by stsstack-bundle: ./generate-bundle.sh --name cou -r yoga -s jammy --ceph --run
Step to reproduce: you can run cou upgrade on the environment mentioned above. Or do it manually following the cou plan
juju refresh cinder --channel zed/stable
juju config cinder openstack-origin=source:jammy-zed
# and wait until this error happens

If the we ignore the error in cinder-ceph, and force upgrading cinder-ceph
juju refresh cinder-ceph --channel zed/stable

The error in cinder-ceph will go away.
Relevant information:

“zed” was not presented during upgrade: https://opendev.org/openstack/charm-cinder-ceph/src/branch/stable/yoga/charmhelpers/fetch/ubuntu.py#L250

“zed“ exists after the upgrade: https://opendev.org/openstack/charm-cinder-ceph/src/branch/stable/zed/charmhelpers/fetch/ubuntu.py#L263

Note: This happens on a openstack cloud delpoyed by stsstack-bundle, and it happens for upgrading from Jammy/Yoga or above .

I somehow think this is not the issue we can handle in the charm.
The options we can have is either:

Handle two applications' upgrade together.
Ignore the status of cinder-ceph until we run the upgrade for it.

For me option 2 is too tricky.
@gabrielcocenza Is there is a way I can combine those two apps' upgrade together?

Possible solution 1: Make sure the upgrading is in right order
We make sure the order of the upgrading is been followed, for example. The cinder-ceph is always upgrade after cinder. And remove the checking of cinder-ceph's status in cinder upgrading. So it's like a series of steps to upgrade both cinder and cinder-ceph.
Possible solution 2:
We decouple the steps and application logic in OpenStackApplication.
A class to generate the upgrade steps shouldn't belong to one single application.
This may need a lot of refactor and a lot of cou plan logic need to be re-created.

We should take care to not try to cover all the issues doing workarounds on COU.
There are issues on the charms itself and this looks like one of then. If you see the latest version of charmhelpers zed is there but looking at the  yoga/stable branch the list is not updated, so it seems that is a simple update on charmhelpers will fix that

The message from @ajkavanagh:

In general subordinates probably should be switched to the next OpenStack track before the principle charm, as the 'next' track always supports the current track.  However, charms come from different eras, and the latest charms that were subordinates tried very hard not to 'upset' the principle.  Older charms could be a bit hit and miss.  In general, I'd still say that subordinates should have their track switched first, followed by principle charms.

The easiest way to resolve the issue maybe reverse the order of upgrading now, we upgrade subordinate first then principle.

The issue to trace document updating: [OpenStack upgrade advice around subordinates and principle charms needs to be updated Edit

After reading https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/yoga/upgrade-overview.html#channels more, it makes sense that subordinate charms must be refreshed to the target release before upgrading principle charms.

With the channels type, a channel is dedicated to a single OpenStack release (release N-1 will be technically supported to assist with upgrades).

In this case, the situation begins with:

cinder yoga/stable (officially supporting yoga and xena) running on yoga release
cinder-ceph yoga/stable (officially supporting yoga and xena) running on yoga release

After upgrading cinder completely (refresh to new channel + update openstack-origin config), the situation is:

cinder zed/stable (officially supporting zed and yoga) running on zed release
cinder-ceph yoga/stable (officially supporting yoga and xena) running on zed release

So immediately cinder-ceph is running on an unsupported release base.
I agree that the documentation must be updated as described in LP: #2072311.
Something else that isn't clear is whether all charms should be refreshed to the target release channel, then the actual upgrades happen?  As in, instead of the current situation:

juju refresh X --channel zed/stable
juju config X openstack-origin=cloud:jammy-zed
juju refresh Y --channel zed/stable
juju config Y openstack-origin=cloud:jammy-zed
juju refresh Z --channel zed/stable
juju config Z openstack-origin=cloud:jammy-zed

We could do:

juju refresh X --channel zed/stable
juju refresh Y --channel zed/stable
juju refresh Z --channel zed/stable
juju config X openstack-origin=cloud:jammy-zed
juju config Y openstack-origin=cloud:jammy-zed
juju config Z openstack-origin=cloud:jammy-zed

I wonder what's best

The general approach would be, for a single machine.
a) Make sure all the charms are up to date for their channel first.  juju refresh
b) Make sure that openstack-origin/source is pointing to the current version (i.e. is not the 'default' unset state).
c) Switch charms to the next channel (subordinates and principles) - juju switch
d) Switch the openstack-origin/source of the principle charms juju config (and perhaps juju run ... openstack-upgrade.
This would ensure the best chance of success.  I think with this approach, any errors are then a bug that should be fixed.


fully replace drone with actions

this builds binaries and docker images for tags

@techknowlogick Is it ready now?

@denyskon yup, all ready for review now :)

Remove this please:
https://github.com/go-gitea/gitea/blob/50166d1f7c6df41c79561b094e29c9698c0000d5/.yamllint.yaml#L27-L28

@silverwind removed, thanks :)


I want to contribute to the fluttertemplates.dev!

Want to contribute
I'm inspired by your awesome project and want to start open source.
About
Hello! My name is Adii. I'm a intermediate flutter dev.
I'm really inspired by your project and want to contribute by adding some widget snippets
Can you guide me how can I?
Thank you for this awesome project and I wish you'll have a good day ahead

You can start by adding proposals for widgets that you would like to be added here.
I am also working on adding documentation for the project and contributing docs.


problem with scrolling on google chrome

hi. got this strange problem when scrolling in google chrome only. sometimes it scrolls to infinity and can't scoll to footer. here is an example - https://www.stelmet.com/relacje-inwestorskie/notowania/

I'm having the same issue -- it looks like you were able to fix it on your site. Would you mind telling me how?


AUTOCV : Build Object Detection YoloV5s using AWS Ground Truth as an input

Issue #, if available:
First PR of auto CV solution using Code Pipeline, AWS Sagemaker. This solution uses a ground truth job as a input to automatically build a Custom YoloV5s solution
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Closed for now


Consume opamp-spec as a submodule and use protos from it

Depends on https://github.com/open-telemetry/opamp-go/issues/133
This is similar to what we do with OTLP protos in https://github.com/open-telemetry/opentelemetry-proto-go
We need a makefile to re-generate the files every time protos are updated. Generated files should be stored in this repo.
Ideally also a github action that verifies that protos match the generated file.

@jlegoff can you help with this?

@tigrannajaryan yes, I can take it when the protos are moved to opamp-spec

Sounds good, assigned to you.
In meantime if you want to start with https://github.com/open-telemetry/opamp-java/issues/3 it would be great.

Protos are in the spec now: https://github.com/open-telemetry/opamp-spec/pull/126
If you need anything to be changed in proto files for Java (e.g. java_ options) please create a PR against the spec repo.

I have started to work on this issue here - I'm struggling with a few build issues but I'm getting help from @jack-berg

I have started to work on this issue here - I'm struggling with a few build issues but I'm getting help from @jack-berg

Sounds good. Please move incrementally, keep the PRs small so that they are easy to review.

Please move incrementally, keep the PRs small so that they are easy to review

I've made a first PR and kept is as small as I could, even though there's a lot of boiler plate code with the gradle scripts 😅

Generated files should be stored in this repo.

@tigrannajaryan why store the files in the repo?

We need a makefile to re-generate the files every time protos are updated.

Why use a makefile instead of standard java tooling with gradle?
I think the opentelemetry-proto-java and opentelemetry-java gets this right:

Its published artifacts contain the classes generated from the protos, but the classes are not checked into source code. If desired, test code could be written that asserts their presence along with any other behavioral invariants we want to guarantee.
The current version of the referenced protos can live in source code. Updating to the latest only requires bumping one number in source code, like we do with the otlp protos in opentelemetry-java.

@tigrannajaryan why store the files in the repo?

I find it helpful to look at diffs in generated file in PRs. For example if we change generation options diffs are very important to see the effect of the change. If the files are not stored in the repo there is no way to do it. Also if generated files are not stored in the repo ensuring reproducing build is more difficult  - you have to ensure you generation process is also reproducible, which is doable but adds one more thing to worry about.

Why use a makefile instead of standard java tooling with gradle?

Ignore that. Use whatever tool makes sense for java.

I find it helpful to look at diffs in generated file in PRs. For example if we change generation options diffs are very important to see the effect of the change. If the files are not stored in the repo there is no way to do it.

I don't disagree with that. However, it does break convention with opentelemetry-java. In my experience, the tooling we use to generate proto classes is very reliable. Having modules that depend on the generated classes like the eventual opamp client / server and corresponding test files improves confidence.
I'm neutral overall, given that there will be no change in experience for someone consuming the artifact whether or not the generated classes are checked into source code.

If you don't see the need to have the diffs of generated files in PRs then go with whatever you prefer. It should be long-term maintainers' decision and I am only a temporary maintainer here. It is also possible to change this decision later and start storing generated files in the repo, so no big deal, start with what you prefer now.


We got a GROOVY-3456 zoombie here.

It seems this got broken again in a code cleanup.
Present in the 2.5 branch, as well.

Merged, thanks! See also GROOVY-9584.

@paulk-asert just for my personal curiosity how does that .context property get overwritten through bindings, I wasn't able to find it in the code.


[Event Request] Table 39 Purchase Line - OnValidate "Unit of Measure Code" - OnValidateUnitOfMeasureCodeOnBeforeValidateQuantity

Please add an Event OnValidateUnitOfMeasureCodeOnBeforeValidateQuantity in OnValidate "Unit of Measure Code" in Table 39 Purchase Line
[Event Request] Table 39 - Purchase Line - OnValidate "Unit of Measure Code"
field(5407; "Unit of Measure Code"; Code[10])
{
    trigger OnValidate()
    var
        Item: Record Item;
        UnitOfMeasureTranslation: Record "Unit of Measure Translation";
        Resource: Record Resource;
        IsHandled: Boolean;
        ShouldUpdateItemReference: Boolean;
    begin
        TestStatusOpen();
        ...
        OnValidateUnitOfMeasureCodeOnBeforeValidateQuantity(Rec, xRec, Item); // <-- NEW EVENT

        Validate(Quantity);
        UpdateDirectUnitCostByField(FieldNo("Unit of Measure Code"));
    end;
}

[IntegrationEvent(false,false)]
local procedure OnValidateUnitOfMeasureCodeOnBeforeValidateQuantity(var PurchaseLine: Record "Purchase Line"; xPurchaseLine: Record "Purchase Line"; Item: Record Item)
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 46009.


Handle CLI tagging when latest tag is of n-1 branch

Description of changes:
When a 'n-1' version of eks-a is released, the script responsible for tagging the dev CLI pulls in the latest tag, bumps it by 1 to arrive at the next Dev tag for the CLI. This had worked fine until we supported for release branch n. With n-1 support, we need to factor in if the latest release is of 'n-1' and ignore it during the dev tagging.
Testing:
Ran the make eks-a command before and after this change to see the Dev CLI tag.
Before:
/Library/Developer/CommandLineTools/usr/bin/make eks-a-binary GIT_VERSION=v0.20.0-dev+latest
After:
/Library/Developer/CommandLineTools/usr/bin/make eks-a-binary GIT_VERSION=v0.21.0-dev+latest
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/hold

This issue has been fixed in a separate PR


ERR. Backup failed. Cyrillic?

> Backing up the file(Personal account archive)...
	. Setting the download behavior...
	> Saving a local copy of the file(Personal account archive)...
		. Opening up the figma command palette...
		. Typing down the download command...
		. Execute the download command...
		. File (Personal account archive) successfully downloaded.
		  (You are seeing this message because the bot has detected network idleness and assumes the download has finished)
> Backing up the file(Reports.file)...
	. Setting the download behavior...
	> Saving a local copy of the file(Reports.file)...
		. Opening up the figma command palette...
		. Typing down the download command...
		. Execute the download command...
		. File (Reports.file) successfully downloaded.
		  (You are seeing this message because the bot has detected network idleness and assumes the download has finished)
> Backing up the file(Флоу)...
	. Setting the download behavior...
	> Saving a local copy of the file(Флоу)...
		. Opening up the figma command palette...
		ERR. Couldn't open the figma command palette.
		. Typing down the download command...
ERR. Backup failed | Protocol error (Input.dispatchKeyEvent): Session closed. Most likely the page has been closed.
> Stopping the bot...

May cyrillic word "Флоу" be the issue for this error? This happens every time I run this script (via npm or via docker - it doesn't matter)

Closing the issue due to the project being archived.


Add link to KubeCon Europe talk

What type of PR is this?
/kind documentation
What this PR does / why we need it:
Add the link to the KubeCon talk.
Which issue(s) this PR fixes:

None
Does this PR have test?
None

Special notes for your reviewer:
None
Does this PR introduce a user-facing change?

None

:tada:


draw-tools.jsを分割

This change is

Reviewed 4 of 4 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Deserialize an array of references

Suppose I have a firestore field that is an array of references, for example in a post document I have a comments field:

In my Ember data model I can't simply do
@hasMany('comment') comments;

because that's not how this adapter works, it expects the comment document to have a @belongsTo reference to the post. I'm thinking that a custom transform is needed, like a docref-array or something, but before I dive into that I wanted to check and see if there's an easier way to do this using this adapter, or if anyone has suggestions as to how this might be accomplished.

I don't think hasMany would work for your case if you store it in an array. In fact, I would advise you not to do so.
In your example, comments in a post could be an infinite amount. If you don't store it in a sub-collection then every time you fetch your post, it will include the comment references. That could be potentially slow down your app and cause your billings to spike as well because of the size of the response.

🤦
Putting ids in a subcollection just works™.
@hasMany('post', { inverse: null }) topPosts;
dailyDashboard.topPosts gives me what I need. Thank you 👍

I mean it depends on your use-case. If you want to model it where topPosts is a hasMany, then it's something that's lazily loaded so it should be in a sub-collection to match that behavior.
If you're taking the hasMany approach, you can either set an attribute referenceTo to the corresponding post doc or your duplicate the post data itself to the topPosts sub-collection.

You are indeed correct, I needed to add the referenceTo field to the sub collection doc. Now everything resolves beautifully 🎉 Thanks again.


support sdxl turlbo

do you have plan to support sdxl turlbo?

You may find an implementation here: https://github.com/GaParmar/img2img-turbo/issues/9