Add Clifford.from_matrix

Add Clifford.from_matrix method that create a Clifford object from Clifford unitary matrix. More importantly, using this method internally, Clifford.__init__ is updated so that it can take any Gate object up to 3 qubits such as Rz(pi/2), iSwapGate and ECRGate, which were not convertible before. As a result, it fixes an issue in qiskit-experiments.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

59 of 64 (92.19%)  changed or added relevant lines in 2 files are covered.
5 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.09%) to 84.947%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

qiskit/quantum_info/operators/symplectic/clifford.py
47
49
95.92%

qiskit/quantum_info/operators/symplectic/clifford_circuits.py
12
15
80.0%

Files with Coverage Reduction
New Missed Lines
%

src/sabre_swap/mod.rs
2
99.54%

qiskit/pulse/library/waveform.py
3
91.67%

Totals

Change from base Build<PHONE_NUMBER>:
0.09%

Covered Lines:
66810

Relevant Lines:
78649

💛  - Coveralls

Why do you need to add a general method to the Clifford gate? and not add specific additional Clifford gates (like: Rz(pi), ECRGate, iSwapGate) to the equivalence library, where you can add a decomposition of these gates into other Clifford gates?

It's for catching all cases without increasing the maintenance cost.
I just prioritize capability to performance in this commit.
With this, we no longer need to update Clifford class or an equivalence library when we introduce a new gate in future (at least up to 3 qubits). I'm not sure the equivalence library approach works well for parameterized gates (e.g. what should we do for RZGate(5*pi/2)?).
Another good use case for this new function is construction from a custom gate (suggested by @nkanazawa1989). The previous logic rely on the gate name, so for example when we define a custom cx gate subclassing the standard CXGate, class CustomCX(CXGate), and instantiate with a different name, custom_cx = CustomCX(name="custom_cx"), we were not able to do Clifford(custom_cx). With this commit, we can do that since the CustomCX inherits the matrix definition of the standard CXGate.

I've tried a new algorithm suggested by @alexanderivrii in another branch and found it works well (much faster than the naive algorithm currently implemented, see the benchmark results in the link).
So I'll update this pull-request to use the new algorithm.

According to tests we have 3 types of gates to handle:

The gate ECRGate() - this gate can be added to the file clifford_circuits.py as described in #9582

Gates that are not in the clifford_circuits.py but their definition contains only Clifford gates, so they are automatically converted into Cliffords (but we can easily add them to the file if needed):

            CYGate(),
            iSwapGate(),
            SXGate
            SXdgGate

Gates that are Cliffords only for certain parameters (e.g. an integer multiplication of pi or pi/2).
Perhaps they can also be added to the file clifford_circuits.py, defining new lists of gates:
_BASIS_1Q_with_params and _BASIS_2Q_with_params

            RXGate(theta=np.pi / 2),
            RYGate(theta=np.pi / 2),
            RZGate(phi=np.pi / 2),
            CPhaseGate(theta=np.pi),
            CRXGate(theta=np.pi),
            CRYGate(theta=np.pi),
            CRZGate(theta=np.pi),
            RXXGate(theta=np.pi / 2),
            RYYGate(theta=np.pi / 2),
            RZZGate(theta=np.pi / 2),
            RZXGate(theta=np.pi / 2),
            XXMinusYYGate(theta=np.pi),
            XXPlusYYGate(theta=-np.pi),

Only if a gate does not fit anyone of these conventions, one will use the Clifford.from_matrix() method.

@ShellyGarion I think the above comment is a good starting point of the discussion on https://github.com/Qiskit/qiskit-terra/issues/9576, while I think it is beyond the scope of this PR. Let me focus on the addition of Clifford.from_matrix function and its minimal use (fallback function for _append_operation) in this PR.

@ikkoham I've updated based on the review comment. Could you take a final look?


When update the maven repository

The lastest version on maven is 9.0.6, that is not including /transitions/template folder. SO the demo is not working with the maven building.
Pls help updating, many thx!

Hi,
I don't know exactly the release cycle but I think I've read in another issue something about "end of month".
I hope I can do some advertising :wink:
If you are interested in the JFXAnimationTemplate stuff and also the demo, I created a separate project:
JFXAnimation
If the implementation is also included in the next JFoenix release you can remove the JFXAnimation dependency and rename the import packages.
Greetings

So is the new release already near? 😃

Hello,
I just released new JFoenix jars *.*.8 , they will be available in a couple of hours on maven central.
Regards,

I guess that this issue can be closed now. 😉


Pretrained weights for pytorch version

Thanks the sharing the code with the community. Would you share the pretrained weights for pytorch as well?  I'd like to test trained model on images of novel object for example.

Hi @ancorasir
Sorry for the super slow reply, I completely missed this.
Pretrained weights for some different conditions are available here: https://github.com/dougsm/ggcnn/releases/download/v1.0/ggcnn2_weights.zip
Note that if you have a specific application in mind, retraining for that scenario might provide better results, especiall aspects like field of view and data augmentation.

@dougsm
Seem there's something wrong that I cant load your saved file.
Can you specify the pytorch version you used for this project ?


Add Fluent Bit retry configuration

By default Fluent Bit uses a Retry_Limit of 1.
Since senders want to ensure that telemetry data is ingested, even if the observability backend (here SAP Cloud Logging) is temporarily unavailable (e.g. due to network problems), we should recommend at least 3 retries.

Thanks Jannik. I’ve made the changes here:
https://help.sap.com/docs/cloud-logging/sap-cloud-logging/ingest-via-json-api-endpoint?state=DRAFT
If this meets your approval I will push the changes out to PRODUCTION.

Thanks! Approved from my side.

I have pushed the changes out into PRODUCTION. We should see them after the next build, which usually happens on Thursday evenings. Please keep your eye out for the changes here:
https://help.sap.com/docs/cloud-logging/cloud-logging/ingest-via-json-api-endpoint?version=Cloud
I'll be out of the office Thursday-Monday but I'll check when I get back on Tuesday August 27.


[FEATURE] Create Project card design

Description
For the open project we need a design which shows the following information:

Name of the project
Name of the person you created the project
Tech stack
Open positions
Who is currently working on

I am imagine the open position and techstack are like badges, which can be added and removed (with x) easily. Like, you can add tags on youtube videos for example.
Screenshots

I created a first mock up on how the project cards could look like.
Additional information
No response

is it still open

Yes, it is still open.

please let me know if its available and if possible can u assign me?

Sure @parinitapatil I am happy, that you contribute again on this project.

Kindly let me know if any adjustments or revisions are necessary.

Do you know about more uiux projects?

MAM, I would greatly appreciate your feedback on the design. Please let me  know if you have any thoughts or suggestions. Thank you.


fix (config.toml): add .streamlit/config.toml to repo root

config.toml :

Because our app scripts reside in a subdirectory of the repo streamlit/, the usual place for config.toml is the streamlit/.streamlit directory. This works perfectly when the app is deployed locally. However, when deployed in Streamlit Cloud, the .streamlit directory must sit in the repo root. Therefore, this same directory now exists, inelegantly, in two locations.

Error with PR


Assessment Worktype - Federal Involvement Decision Milestone

Describe the bug
2 of the 3 options appear to be identical, both setting FederalInvolvement to "None". The first one gave an error. the 3rd one worked properly.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
we need to change the options to say what the outcome column says instead of the action column. (on the excel)
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

Would this ticket become obsolete if are creating new assessment template @Connor1892 @EAO-App-Admin @maria-kuzmenko

Closing this ticket as the new templates will deal with these issues


ui and color scheme changed and responsive design also added

Hello there,
i have added the new color scheme for your web application and also done some changes in ui as you have metioned.
also added responsive design for mobile.
Hope you like the design.

hey i have added dark and light theme functionality, provide me the color code show i can add them.

Hey, I have added dark and light theme functionality. Please provide the color codes so I can add them.

Color Codes:

All Notes: lightgoldenyellow (Can be dynamically set to any color by the user using JavaScript)
Held Notes: lightseablue  (Can be dynamically set to any color by the user using JavaScript)
Checked Notes: lightgreen  (Can be dynamically set to any color by the user using JavaScript)

and the other colors are okay??

Are the other colors okay?

Yes, they are fine. Just make sure not to comment out components or other imported code, as this can cause issues during the build process on Netlify. Please check your terminal for any possible warnings or errors before submitting a PR.

Hi @Divyverma,
I've recently updated all the file names to improve the directory structure. Could you please close this PR and create a new one? There are several issues that need attention. Please work on a feature branch and submit a new PR.
Note: Make sure to check for any warnings in the terminal beforehand to avoid merge conflicts and issues with the Netlify build.
Thank you!


Fixes 115: Added blocking keyboard player

"Blocking" means the whole game waits for user input.
Test this with:
pom_battle --agents=playerblock::arrows,test::agents.SimpleAgent,test::agents.SimpleAgent,test::agents.SimpleAgent --config=PommeFFACompetition-v0 --render
pom_battle --agents=playerblock::wasd,test::agents.SimpleAgent,test::agents.SimpleAgent,test::agents.SimpleAgent --config=PommeFFACompetition-v0 --render
You can still use the original player (non-blocking):
pom_battle --agents=player::arrows,test::agents.SimpleAgent,test::agents.SimpleAgent,test::agents.SimpleAgent --config=PommeFFACompetition-v0 --render

Still have concerns here @cinjon ?

seems good. i'd appreciate it if you ran it through yapf -i --style google quickly before submitting.

also, please squash the commits together.

Superseded by https://github.com/MultiAgentLearning/playground/pull/208

we can close this, ja?


Zabbix host name instead of visible name variable query.

I'm submitting a ...

[ ] Bug report
[ ] Feature requestdd
[X] Question / Support request

If you don't send bug report, remove sections below
For bug report please include this information:
Software Versions

Grafana
Zabbix
Grafana-Zabbix Plugin

5.0
3.4.8
3.8.1

If there any way to use host name in template queries? Currently query return only Visible name from zabbix.
Sometimes we have long visible names which can break panel layout and it is difficult to use them for variables with "custom" type as visible name ofter changes, while host name is constant.
In zabbix:

Grafana variable:
query:

preview:

Also if in panel metrics query I manually set "Host" field to host name no data available, while setting to visible name work perfectly

Currently query return only Visible name from zabbix

Query editor designed for work with visible names only. So changes in variable query make no sense without changing editor.

opened new issue for query editor #606


OMNeT++ simulation and dataset formatting

Hi,
I would like to generate simulation results from OMNeT++ and compare them with the predictions generated from RouteNet-Fermi. I am having trouble figuring out how to format results into a dataset. I see that for a given dataset like geant, a omnet config file is provided with graphs and routing txt files. How do the graph and routing files correspond to an omnet ned file? Additionally, do values like the lambda min and max have to be defined within the ned file?
Thanks,
Rohin

Dear Rohin,
In the context of RouteNet-F simulations, it's worth noting that the comparison with OMNeT++ results is inherently integrated into the execution process. However, if you aim to recreate simulations based on the existing dataset, it's important to note that translating this dataset into an OMNeT NED file isn't a straightforward task and often involves complexities.
If your objective is to generate a customized dataset for further analysis, I highly recommend exploring our simulator, BNNetSimulator. This tool provides a comprehensive guide to constructing and generating network modeling datasets. In it, you will find an input_parameters_glossary and a quick_start where you will find how to define and which parameters need to be specified.
Best regards,
Miquel

Thank you. Can you explain what you mean when you say the BNNetSimulator is built on the OMNeT++ framework? Does BNNetSimulator act as an interface to OMNeT++ to make network dataset generation easier?

Hell Rohin,
When We say that BNNetSimulator is built on the OMNeT++ framework, it means that we have implemented various modules within the OMNeT++ environment using its tools. These modules include traffic generators, scheduling policies, routing algorithms, and others, which we have developed within the OMNeT++ environment to conduct network simulations.
Best regards
Albert


[FLINK-14912][Table] create, drop catalog functions through catalog manager

What is the purpose of the change
Create, drop and alter catalog functions through catalog manager.
Brief change log

Add create, drop, alter function operation
Add SqlNode to Operation conversion logic SqlToOperationConverter
Add the catalog function registration and drop logic in table envrionments
add CatalogFunctionITCase for end to end testing function DDL to create and drop catalog function.

Verifying this change
It is end to end tested in new added CatalogFunctionITCase.
Does this pull request potentially affect one of the following parts:

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

Documentation

Does this pull request introduce a new feature? (yes)
If yes, how is the feature documented? (not documented)

@bowenli86 @xuefuz Please review the PR at your most convenient time. Currently, only SqlCreateFunction and SqDropFunction are added in SqlKind, but none of them is actually included in the DDL enum. In this case, I have to change the calcite first, then wait for the new calcite release. Do you have a better strategy to handle it?

@bowenli86 @xuefuz Please review the PR at your most convenient time. Currently, only SqlCreateFunction and SqDropFunction are added in SqlKind, but none of them is actually included in the DDL enum. In this case, I have to change the calcite first, then wait for the new calcite release. Do you have a better strategy to handle it?

I'm not familiar with calcite. @danny0405 @KurtYoung what do you think?

Thanks for your nice job @HuangZhenQiu ~ Reviewing now ~

Do you mean CALCITE-3349 ? I think we do not need to wait for CALCITE-3349 in the release, we can use Sqlkind.OTHER_DDL instead first. After all, we should always implement the SqlCreateFunction and SqlDropFunction in flink-sql-parser. We can use the DDL as SqlKind if we upgrade to Calcite 1.22.0.(You should logger a JIRA issue under the 1.22 version Calcite upgrade umbrella issue).

Thank for the PR @HuangZhenQiu , the PR overall looks good, can you also add the cases for Blink planner ? Even though the code path looks the same, we still need the tests to make sure the logic works correctly.

@bowenli86 @danny0405 @xuefuz I resolved your comments. In the meantime, CatalogFunctionITCase is also added into blink planner. Please take one more round of review.

@bowenli86 I changed my local code for each of those lines. I didn't touch them.
It is in the right format from beginning rather than I did any change.

@danny0405 @bowenli86 The PR attached to the wrong ticket due to I mistakenly used wrong ID. I created another PR to correct it.


update: save pipelinerun result to annotation

What type of PR is this?
/kind bug
What this PR does / why we need it:
save pipelinerun stage data to configmap
Which issue(s) this PR fixes:

Fixes #853
Special notes for reviewers:

Please check the following list before waiting reviewers:

[ ] Already committed the CRD files to the Helm Chart if you created some new CRDs
[ ] Already added the permission for the new API
[ ] Already added the RBAC markers for the new controllers

Does this PR introduce a user-facing change??

save pipelinerun result to annotation

/lgtm

/cherry-pick release-3.3

/approve

/cherry-pick release-3.3


⚠ Bofrost.de has degraded performance

In d62f9be, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1400 ms

Resolved: Bofrost.de performance has improved in 311af83 after 16 minutes.


add .absolute_url field to all models

This PR adds a new field, .absolute_url, to all (non-User) models. In doing so, it clears the way for implementing the change in #529 - this way, all the data needed to render the template will be present in the database, and we will no longer need to load Python objects into memory in order to call their .get_absolute_url methods.
The PR adds a new hook to signals.py, which ensures that whenever an object is saved, its absolute_url field is up-to-date (we don't expect objects' ids to change often (perhaps while syncing data with OldCantus?), but this ensures that nothing breaks if it occurs). In order to populate these fields initially, a new management command, save_all_objects, has been added to load and save all objects in the database, thus triggering the new on_object_save hook. This command will need to be run when these changes are added to our staging and production servers.
If I got all my git checkouts correct, these changes pass all tests introduced in #539.

hold off on approving this for a moment - all the tests are passing, but there's still a problem with some of the links on the chant search page...

@dchiller, can you take a close look at the save_all_objects script? I tried to run it yesterday, and it seems not to have touched certain chants. Out of the ~500,000 chants, there were at least 73851 for which their absolute_url was None. I tried running it again today (my computer fell asleep several times yesterday as the script ran into the evening, so I thought that might have been the culprit), and after a second pass, the number of chants without absolute_urls is now 33425. It's skipping chants at random, and I don't understand why.
Similarly, out of our 17,000 sequence objects, 6192 had been missed in the first pass, and 2185 remained after the second pass.
If you can't see what's going wrong, I may try to rewrite the script to simply update the specific field rather than loading and saving the entire chant object. But I would like to figure out what's going wrong!

Could you explain a bit more about the motivation for this?
Django can construct a url for any route given only a PK. This means that you just need to get a single field from the db to construct a URL. Moreover, if you have a set of FKs you can also constuct URLs for them too.
So I guess I’m missing the motivation for why you’re storing the full URL string in the database as well. You say something about not needing to load the database objects in memory, but you’ll need to do that if you want to retrieve the URL from there.

Django can construct a url for any route given only a PK.

Aha! Thank you for this! I can replace {{ chant.get_absolute_url }} with {% url 'chant-detail' chant.id %} in all templates to link to a chant detail page, and adapt this to link to feast, source, etc. detail pages as necessary. A much better solution - again, thank you!
I should get this set up everywhere in the codebase, and then get rid of our models' .get_absolute_url method, so future developers aren't misled as I was - I spent a while trying to figure out how to annotate querysets using django.urls.reverse, but now it's clear that there's a much simpler way.


feat: make  preamble configurable in ChatCohere

As in https://github.com/langchain-ai/langchain/pull/19825, this PR make preamble configurable for ChatCohere.

@GangGreenTemperTatum Please help me approve the CI workflow, thanks!

@kaijietti
Sincere apologies for the delay in reviewing this. Thanks a lot for your contribution!
We plan on releasing another version later today, and I'll make sure this is merged and included.
Thanks once again!

Nervermind, thanks for your review!

@kaijietti this is now released in 0.1.3rc0, on PyPI it's marked as a pre-release but we'll aim to release it as 0.1.3 next week.
Incase you haven't seen it, we have documentation on preambles here. Please reach out to let us know how things go!


Sanitize tax code and account

This PR goal is to implement sanitize methods for tax code and account entities.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Flag
Coverage Δ

unittests
87.56% <100.00%> (+1.00%)
:arrow_up:

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

Files with missing lines
Coverage Δ

pyledger/ledger_engine.py
79.84% <100.00%> (+3.05%)
:arrow_up:


Modified ecma string to utf8 string conversion to reduce binary size.

JerryScript-DCO-1.0-Signed-off-by: László Langó<EMAIL_ADDRESS>

Binary sizes (bytes)
6fce323fa5:134344
c5c5db8f57:133852

@zherczeg thanks for the review. I've updated the PR.

@zherczeg rebased to the current master. The measurement results are still good on RPi2. There is no negative side effect of the patch.

@zherczeg Thanks for the review. I've updated the PR.


AppController - statefull app deployments

Description
AppController will allow to work with statefull applications that involve many components (openstack for example) more easy and more native. AppController will understand dependencies between kubernetes objects and therefore it will create them in correct order.
kubernetes/kubernetes issue: https://github.com/kubernetes/kubernetes/issues/29453
cc @kubernetes/sig-openstack @kubernetes/sig-apps
Progress Tracker

[ ] Before Alpha

[ ] Write and maintain draft quality doc

[ ] During development keep a doc up-to-date about the desired experience of the feature and how someone can try the feature in its current state. Think of it as the README of your new feature and a skeleton for the docs to be written before the Kubernetes release. Paste link to Google Doc: DOC-LINK

[ ] Design Approval

[ ] Design Proposal.  This goes under docs/proposals.  Doing a proposal as a PR allows line-by-line commenting from community, and creates the basis for later design documentation.  Paste link to merged design proposal here: PROPOSAL-NUMBER
[ ] Initial API review (if API).  Maybe same PR as design doc. PR-NUMBER

Any code that changes an API (/pkg/apis/...)
cc @kubernetes/api

[ ] Identify shepherd (your SIG lead and/or<EMAIL_ADDRESS>will be able to help you). My Shepherd is<EMAIL_ADDRESS>(and/or GH Handle)

A shepherd is an individual who will help acquaint you with the process of getting your feature into the repo, identify reviewers and provide feedback on the feature. They are not (necessarily) the code reviewer of the feature, or tech lead for the area.
The shepherd is not responsible for showing up to Kubernetes-PM meetings and/or communicating if the feature is on-track to make the release goals. That is still your responsibility.

[ ] Identify secondary/backup contact point. My Secondary Contact Point is<EMAIL_ADDRESS>(and/or GH Handle)

[ ] Write (code + tests + docs) then get them merged.  ALL-PR-NUMBERS

[ ] Code needs to be disabled by default.   Verified by code OWNERS
[ ] Minimal testing
[ ] Minimal docs

cc @kubernetes/docs on docs PR
cc @kubernetes/feature-reviewers on this issue to get approval before checking this off
New apis: Glossary Section Item in the docs repo: kubernetes/kubernetes.github.io

[ ] Update release notes

[ ] Before Beta

[ ] Testing is sufficient for beta
[ ] User docs with tutorials
- Updated walkthrough / tutorial in the docs repo: kubernetes/kubernetes.github.io
- cc @kubernetes/docs on docs PR
- cc @kubernetes/feature-reviewers on this issue to get approval before checking this off
[ ] Thorough API review

cc @kubernetes/api

[ ] Before Stable

[ ] docs/proposals/foo.md moved to docs/design/foo.md
- cc @kubernetes/feature-reviewers on this issue to get approval before checking this off
[ ] Soak, load testing
[ ] detailed user docs and examples

cc @kubernetes/docs
cc @kubernetes/feature-reviewers on this issue to get approval before checking this off

FEATURE_STATUS is used for feature tracking and to be updated by @kubernetes/feature-reviewers.
FEATURE_STATUS: IN_DEVELOPMENT
More advice:
Design

Once you get LGTM from a @kubernetes/feature-reviewers member, you can check this checkbox, and the reviewer will apply the "design-complete" label.

Coding

Use as many PRs as you need.  Write tests in the same or different PRs, as is convenient for you.
As each PR is merged, add a comment to this issue referencing the PRs.  Code goes in the http://github.com/kubernetes/kubernetes repository,
and sometimes http://github.com/kubernetes/contrib, or other repos.
When you are done with the code, apply the "code-complete" label.
When the feature has user docs, please add a comment mentioning @kubernetes/feature-reviewers and they will
check that the code matches the proposed feature and design, and that everything is done, and that there is adequate
testing.  They won't do detailed code review: that already happened when your PRs were reviewed.
When that is done, you can check this box and the reviewer will apply the "code-complete" label.

Docs

[ ] Write user docs and get them merged in.
User docs go into http://github.com/kubernetes/kubernetes.github.io.
When the feature has user docs, please add a comment mentioning @kubernetes/docs.
When you get LGTM, you can check this checkbox, and the reviewer will apply the "docs-complete" label.

Generally we prefer to only open features once we have rough consensus from one or more SiGs and a workable proposal.  Since you've already started an issue, we can converse and discuss the feature proposal there and then come back and reopen this later.  Adding a proposal describing your use cases to the issue is a good next step.
Thanks!

@smarterclayton I was instructed by @idvoretskyi (sig-openstack lead) to do it that way.

@smarterclayton we have discussed that with @pigmej and I've proposed him to open the new feature as the soft deadline for 1.4 features is today.
I feel this feature useful in the scope of Kubernetes-OpenStack integration, so I'm advocating to reopen it to continue working on it. Other SIG's are welcome for further discussion.
cc @philips @aronchick to discuss it.

If the SIG is good, then I'm good. @smarterclayton - were there some
specific concerns?
On Fri, Jul 22, 2016 at 8:08 AM, Ihor Dvoretskyi<EMAIL_ADDRESS>wrote:

@smarterclayton https://github.com/smarterclayton we have discussed
that with @pigmej https://github.com/pigmej and I've proposed him to
open the new feature as the soft deadline for 1.4 features is today.
I feel this feature useful in the scope of Kubernetes-OpenStack
integration, so I'm advocating to reopen it to continue working on it.
Other SIG's are welcome for further discussion.
cc @philips https://github.com/philips @aronchick
https://github.com/aronchick to discuss it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/features/issues/42#issuecomment-234569813,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADIdZ4qDqJES9WS-O342oMK1ymrtogSks5qYNz2gaJpZM4JSzwl
.

@idvoretskyi @pigmej Thinking through the spirit of the consensus building I don't think this feature has met the bar. I think generally SIG consensus can be documented a few different means:

Mailing list discussion
Notes from a SIG meeting
Issue or proposal that gets buy in

Right now it appears we have one other person from the SIG and a very young issue (https://github.com/kubernetes/kubernetes/issues/29453) talking about this feature. I agree with closing this issue on those grounds. Lets try and get a bit more documentation on what this feature is and the problems it might be solving for folks before proceeding with a new feature.

@philips, thank you for clarifying. We will handle it within the SIG-OpenStack and I'm asking @kubernetes/sig-apps  to support  it.
I'm expecting to reopen the issue later, after clarifying within the SIG(s). Also, I'd like to reserve an exception for adding it to 1.4 after the criteria will be met.

@philips @aronchick I'd like to propose to define the criteria for submitting the "feature" with more details, I suppose, not all the Kubernetes community members are completely aware of it.

Since this is discussing the meta-issue of how features should be used, I'll comment here.
Please be aware that SIG buy-in may not be sufficient for all features. For example, API changes require approval of API owners, and entirely new APIs must meet a higher bar.
I also commented on this specific proposal on https://github.com/kubernetes/kubernetes/issues/29453.

I can't tell if you are saying that you have someone in line to implement
it, or if you are asking sig-apps to find someone to implement it.
People should file feature issues once they have high confidence they have
found people who will implement (and support for some period) the feature.
On Fri, Jul 22, 2016 at 9:22 AM, Brian Grant<EMAIL_ADDRESS>wrote:

Since this is discussing the meta-issue of how features should be used,
I'll comment here.
Please be aware that SIG buy-in may not be sufficient for all features.
For example, API changes require approval of API owners, and entirely new
APIs must meet a higher bar.
I also commented on this specific proposal on kubernetes/kubernetes#29453
https://github.com/kubernetes/kubernetes/issues/29453.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/features/issues/42#issuecomment-234589277,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHuudiUBbZ75E5pmkb55CSnAwUL94r_uks5qYO47gaJpZM4JSzwl
.

@erictune We ( @kubernetes/mirantis ) do have team to implement and support that. This is part of our contribution to k8s world.

Great, thanks for the clarification.

@erictune sorry that it wasn't clear from the start.

Reopening the feature request.
@kubernetes/mirantis have presented the feature demo at the @kubernetes/sig-apps meeting, have received the positive feedback and a "green light" to move forward.
@pigmej please, update and fill the necessary fields in the Progress tracker.

per the feature burndown meeting today: this will land in kubernetes-incubator first and be promoted based on the criteria in - https://github.com/kubernetes/community/blob/master/incubator.md

@sarahnovotny we have discussed the ability to make this feature available in Kubernetes codebase and have decided to continue working with the feature implementing. To extend the feature functionality and make it tightly bound with Kubernetes codebase we have decided to continue the development of AppController in Kubernetes 1.5 scope.

Is the goal to replace kubernetes/helm with whatever is worked on here? Or is this merely orthogonal/related to what tiller does?

I had a user ask on slack today whether he/she should wait for AppController or use something else, after seeing this issue,
I think that shows there is a cost to having issues in the feature repo for ideas which are still at the concept stage.

Speaking about this issue, I'm closing this one, because for now we're not joinning k8s core. AppController development will be continued at https://github.com/Mirantis/k8s-AppController, we will prepare design docs etc to discuss it with Kubernetes audience (we had some meetings on sig-apps). AppController will have 3week release cycle (we're going to form more formal roadmap etc in near future, and publish it on our repository)
@numbsafari (sorry for late reply), it's not going to replace helm, we're currently looking and searching for possible areas of cooperation between AppController and Helm.

I forgot to click "close and comment" instead of "comment".


URL in Prisma Client's error message has a typo

Bug description
When Prisma Client encounters a Rust Panic, it crashes like so:

Here's the URL is supposed to be clickable, but isn't, because there's an h missing in the beginning (in https://)
How to reproduce
Use this (incorrect) schema:
model User {
  id    Int
  name  String
  email String

  @@unique([name, name])
}

Use this script:
await prisma.user.findOne({
      where: {
        name_name: {
          name: "Something",
        },
      },
    })

Expected behavior
The URL should be valid, which will make it clickable.
Environment & setup

OS: macOS
Database: Postgres
Prisma version: @prisma/cli          : 2.0.0-alpha.1299
Current platform     : darwin
Query Engine         : query-engine d88852ac341cdf3c7379a08fa1ebc5c444a4aa67
Migration Engine     : migration-engine-cli d88852ac341cdf3c7379a08fa1ebc5c444a4aa67
Introspection Engine : introspection-core d88852ac341cdf3c7379a08fa1ebc5c444a4aa67
Format Binary        : prisma-fmt d88852ac341cdf3c7379a08fa1ebc5c444a4aa67
Node.js version: v12.16.3

I am unable to reproduce this error.
I tried out both alpha.1299 and 2.1.0-dev.4 and it doesn't reproduce this error :/

The runtime rejects that query. I described it more in detail here: https://github.com/prisma/prisma/issues/2668


Light Tracker tour doesn't work unless "Track Inactive User Light Sources" is checked

Need to enable for the tour and revert to its original value once its completed.

Yeah, that shouldnt be a problem. I'll take a look at it!


Intentions about SalesforceDX support/configuration?

Questions for @afawcett, @dfruddffdc, and @phardakerffdc:

Now that SalesforceDX is GA, what is the intention on supporting or reconfiguring the project to a SalesforceDX approach?
Would that fork include the code from the ApexMocks project?
Will the code base move to a packaged model when 2nd Generation Packaging goes GA so that we could include in our code base simply as a package installation?

I can certainly change my fork to support SalesforceDX but I would rather avoid doing that if you are going to convert to SalesforceDX approach or spin off a SalesforceDX branch.
Any input on your thoughts and plans for this codebase would be appreciated.
Cheers!

I'm a fan of a SalesforceDX branch, but I think that it's going to be a long time before we can turn our back on the MDAPI project structure. First-generation packaging is going to be around a while and any of us with existing packages that want to migrate to second-generation will have to wait until at least Summer '18, probably longer, before those projects can be converted.

@daveespo, that makes sense.


[QA] Emotes can be played when typing in inputs

If you go to an input and press B+n, te emote will be played.

Unable to reproduce on v0.14


Feature/cicd

I have added cicd pipeline code and readme doc to set it up for migrating agent under examples folder. I would like contribute this to SCRAPI library. Please review the changes

@kmaphoenix I have addressed all the lint issues you have mentioned and also fixed most of the lint errors that i ran in my IDE. Please re review it and do the needful.

Hi @sridharvikram , did you perform a git rebase with main branch?
It's showing many edits to files that are not related to your CICD code and should not have been modified.
If you did not perform a rebase, you should do this first.
If you're not familiar with running a rebase, you can consider starting a new branch from the latest main branch.
Otherwise it makes it very difficult to review all of your code.

@sridharvikram yeah after looking at the branch some more there are many merge conflicts.
Best course of action:

Start a new branch from main
Add your changes for CICD code
Submit PR

Otherwise we're going to have a lot of back and forth to get this fixed and you'll need to fix all of the merge conflicts locally.

@kmaphoenix I have created this new PR https://github.com/GoogleCloudPlatform/dfcx-scrapi/pull/239 as suggested. Hence closing this one. Thanks


Build problems

Hello I am following:
https://github.com/davideas/FlexibleAdapter#setup
and I am still unable to build my project.
build.gradle:
repositories {
jcenter()
maven { url 'https://maven.fabric.io/public' }
}
dependencies {
....
// flexible adapter
compile 'eu.davidea:flexible-adapter:5.0.0-rc1'
compile 'eu.davidea:flexible-adapter-databinding:1.0.0-b1'
.....
}
and it does NOT work. It's driving me crazy. The error message I am getting is:
Error:(95, 13) Failed to resolve: eu.davidea:flexible-adapter-databinding:1.0.0-b1
Seems that eu.davidea:flexible-adapter-databinding:1.0.0-b1 is not published in jcenter!

@pavelkryl, thank you for the message, actually I missed to request the pubblication in JCenter too, I did it now. Temporary, you can use maven { url "http://dl.bintray.com/davideas/maven" }.
But probably there's another issue of undefined version. Need to investigate.

I was having the same issue but even after changing the repository URL I still receive "failed to resolve: com.android.support:design:25.4.0"

For that you must add the new google maven repo url. Read support realease note.

@davideas Thank you; I've never run into that before so I guess it's a new change as of 25.4.0? I added the following line to my gradle file:
compile 'eu.davidea:flexible-adapter-databinding:1.0.0-b1'
but I'm receiving the following:
Failed to resolve: FlexibleAdapter:flexible-adapter:unspecified
I don't mean to sidetrack this discussion; thank you again for your help!

I should try to put provided and publish it again. Now I'm out, I will do it by tomorrow.

OK, I do not know why Gradle doesn't like, but the following line will make it compile successfully:
compile 'eu.davidea:flexible-adapter-databinding:1.0.0-b1@aar'

And for the moment, until it is not published to jCenter, add this repository as well:
maven { url "http://dl.bintray.com/davideas/maven" }

It is published.


Push v0.11.0 podspec to Cocoapods

I sent an email to Luis about getting added as a maintainer on the CocoaPod.

Thank you!


Expose service annotations

Allows users to set service annotations to service pipelines.
Closes #3754

I am having problems with passing tests in travis. From some point, an error is thrown:
No error is expected but got transport is closing

Hi Pachyderm team,
I have a problem running tests for this PR. The goroutine at pachyderm/src/server/pachyderm_test.go:8846 does not  stop its execution after the test is finished and blows up after successful test pass (does kafka go down?). It is also present in the last build for this PR: https://github.com/pachyderm/pachyderm/pull/3751. Would not it be better to stop this goroutine? Did not dig really deep into this, but this looks wrong.
=== RUN   TestKafka
--- PASS: TestKafka (9.60s)
=== RUN   TestDeferredProcessing
--- PASS: TestDeferredProcessing (7.59s)
=== RUN   TestPipelineHistory
panic: Fail in goroutine after TestKafka has completed
goroutine 1946 [running]:
testing.(*common).Fail(0xc0001bac00)
	/home/travis/.gimme/versions/go1.11.1.linux.amd64/src/testing/testing.go:546 +0x135
testing.(*common).FailNow(0xc0001bac00)
	/home/travis/.gimme/versions/go1.11.1.linux.amd64/src/testing/testing.go:568 +0x2b
testing.(*common).Fatal(0xc0001bac00, 0xc00008df18, 0x1, 0x1)
	/home/travis/.gimme/versions/go1.11.1.linux.amd64/src/testing/testing.go:628 +0x6f
github.com/pachyderm/pachyderm/src/server.TestKafka.func1(0xc00039f860, 0xc0003852c0, 0xc0001bac00)
	/home/travis/gopath/src/github.com/pachyderm/pachyderm/src/server/pachyderm_test.go:8852 +0x1ef
created by github.com/pachyderm/pachyderm/src/server.TestKafka
	/home/travis/gopath/src/github.com/pachyderm/pachyderm/src/server/pachyderm_test.go:8846 +0xc0d
FAIL	github.com/pachyderm/pachyderm/src/server	851.943s
Makefile:489: recipe for target 'test-pps-helper' failed
make: *** [test-pps-helper] Error 1

BTW, does this PR have something to do with the problem? Seems related
https://github.com/pachyderm/pachyderm/pull/3752

Overall, looks like it fails randomly

Yeah, that's a bug -- thanks for catching that!

Code all looks good to me. The only thing I'd like to see added to this is some test coverage. Should be as simple as adding an annotation in the TestService and then checking to make sure that it's present. After that this should be good to merge.

@jdoliner Done!

@jdoliner no problem! rebased & regenerated the proto file

Just thought that it might be a good idea to exclude the generated proto files from the repo altogether, as this approach is somewhat error-prone in general and also spoils the picutre on additions/deletions in this particular case. What do you think?

Not in this PR, of course =)

@jdoliner is there smth else up for a fix?

@cfga nope, sorry for the delay. I'll get this merged today.


Update front-door-wildcard-domain.md

modifying the second contoso to endpoint to create less confusion as when you mention contoso twice it seems as though it is the same DNS host name when in fact in this example they are different.

#sign-off


GITLAB - Erroring when trying to adopt gitlab

Overview
Error on gitlab install:
LOG: 2022/09/09 16:17:32.282347 /home/developer/app/pkg/shell.go:20: Error executing command: exit status 1
LOG: 2022/09/09 16:17:32.282813 /home/developer/app/pkg/shell.go:22: Command Execution: /home/developer/.k1/tools/kubectl
LOG: 2022/09/09 16:17:32.283273 /home/developer/app/pkg/shell.go:23: OUT:
LOG: 2022/09/09 16:17:32.283639 /home/developer/app/pkg/shell.go:24: ERR: error: the path "/home/developer/.k1/gitops/components/helpers/registry.yaml" does not exist

LOG: 2022/09/09 16:17:32.283874 /home/developer/app/cmd/createGitlab.go:138: failed to call execute kubectl apply of argocd patch to adopt gitlab: exit status 1

Panic:
Deploy CI/CD                  ... done! [5 in 1m40.216s]
panic: failed to call execute kubectl apply of argocd patch to adopt gitlab: exit status 1

goroutine 1 [running]:
log.Panicf({0x1c5776e?, 0x21?}, {0xc000125b38?, 0x7?, 0x7?})
	/usr/local/go/src/log/log.go:392 +0x67
github.com/kubefirst/kubefirst/cmd.glob..func11(0xc000187520?, {0xc00057e870, 0x0, 0x1})
	/home/developer/app/cmd/createGitlab.go:138 +0x992
github.com/kubefirst/kubefirst/cmd.glob..func9(0x2b8d800, {0xc00057e870?, 0x0, 0x1})
	/home/developer/app/cmd/create.go:49 +0x1d6
github.com/spf13/cobra.(*Command).execute(0x2b8d800, {0xc00057e860, 0x1, 0x1})
	/go/pkg/mod/github.com/spf13/cobra@v1.4.0/command.go:856 +0x67c
github.com/spf13/cobra.(*Command).ExecuteC(0x2b8da80)
	/go/pkg/mod/github.com/spf13/cobra@v1.4.0/command.go:974 +0x3b4
github.com/spf13/cobra.(*Command).Execute(...)
	/go/pkg/mod/github.com/spf13/cobra@v1.4.0/command.go:902
github.com/kubefirst/kubefirst/cmd.Execute()
	/home/developer/app/cmd/root.go:26 +0x25
main.main()
	/home/developer/app/main.go:65 +0x41d

It seems to be related to recent changes on gitops templates.

A small fix seems to be missing here for github:
https://github.com/kubefirst/kubefirst/blob/3041d5f4226fd3705a4d521cce96be6da7963996/internal/argocd/argocd.go#L292
And gitlab:
https://github.com/kubefirst/kubefirst/blob/3041d5f4226fd3705a4d521cce96be6da7963996/cmd/createGitlab.go#L136
After all the changes on templates, I believe we should only have 1 single registry file and from there all is unfolded.

Templates seems to be as expected: https://github.com/kubefirst/gitops-template/compare/1.8.6...main

merged. :)


When is division of money by money a valid case?

I understand that multipying money by money is not possible. Why is division implemented? I must be missing something.

Hi, to get the ratio between two values, e.g. when calculating a profit margin.

Thank you for the quick response and all your work on this class. I want to extend the class into a double entry bookeeping system.
I understand your response above but the result is a ratio not a monetary value and the money type as I read the code returns the division as an instance of money.

I'm very glad! let me know if you find any issue in the process.
It really should return a number:
https://github.com/carlospalol/money/blob/1.2.1/src/money/tests/mixins.py#L261
https://github.com/carlospalol/money/blob/1.2.1/src-py2/money/tests/mixins.py#L264

Have a great day Carlos! Thanks for the link to the test code. I'll shut-up now ;-)


Error in plugin version check algo?

I seem to have stumbled on a bug in puppet-jenkins' version comparison logic for jenkins plugins - when I tried to install the "build-monitor-plugin" version "1.5+build.120" puppet-jenkins would always download the plugin (and restart jenkins).
On digging further I found that jenkins::plugin uses $version to construct a regexp $search = "${name} ${version}(,|$)" to determine whether or not a plugin occurs in the list of plugins. Therefore if $version contains special regexp characters (like "+") then the version will never be found in the plugin list because the special character will never be matched.
The solution to this, I suppose would be to quote $version when constructing $search. But since puppet doesn't give any direct function to do so I guess we'd need to jump into Ruby to do it:
$search = inline_template('<%= Regexp.escape(@version) %>') or something like that.
Is my understand correct?
Thanks.
PS: Puppet & Ruby noob.

I'm closing this due to its age.


Controllers

Highlights

[x] Create the following:

Controllers with the appropriate methods
Routes
View files

After running the rails routes, this is the outcome:

@thecodechaser Thanks for reviewing and approving the project


tests: fix shrink_mon scenario

since the node names have changed recently (the 'ceph-' prefix has been
removed), we must change the name in the shrink_mon playbook command
here.
Signed-off-by: Guillaume Abrioux<EMAIL_ADDRESS>

jenkins test luminous-centos-non_container-shrink_mon

jenkins test luminous-centos-container-shrink_mon


QR code Scanner

A scanning feature to mark attendance.

I would like to contribute to this.
Open Source Program: JWOC 2023

I would like to contribute to this. Open Source Program: JWOC 2023

You can start the work and do share your email so that i can add you to the firebase project

I can work on this issue under JWOC to make a QR code scanner page to help scan qr codes


Update dependencies and fix mockfs call

test this

Codecov Report

Merging #1027 into master will decrease coverage by 0.2%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1027      +/-   ##
==========================================
- Coverage   94.97%   94.77%   -0.21%
==========================================
  Files          39       39
  Lines        3484     3673     +189
  Branches      302      544     +242
==========================================
+ Hits         3309     3481     +172
- Misses        175      180       +5
- Partials        0       12      +12

Impacted Files
Coverage Δ

browser/pages/install/controller.js
71.3% <0%> (-2.91%)
:arrow_down:

browser/pages/location/controller.js
92.3% <0%> (-2.86%)
:arrow_down:

browser/model/helpers/downloader.js
94.7% <0%> (-1.85%)
:arrow_down:

browser/services/credentialManager.js
93.02% <0%> (-1.72%)
:arrow_down:

browser/main.js
95.58% <0%> (-1.39%)
:arrow_down:

browser/model/devstudio.js
96.8% <0%> (-0.97%)
:arrow_down:

browser/pages/selection/controller.js
98.52% <0%> (-0.47%)
:arrow_down:

browser/model/jdk-install.js
96.61% <0%> (-0.42%)
:arrow_down:

browser/services/data.js
97.43% <0%> (-0.23%)
:arrow_down:

browser/model/jbosseap.js
100% <0%> (ø)
:arrow_up:

... and 25 more

Continue to review full report at Codecov.

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


Add parallelism to continuous queries

Required for all non-trivial PRs

[x] Rebased/mergable

[x] Tests pass

[ ] CHANGELOG.md updated

[x] Sign CLA (if not already signed)

Previously, a long running CQ would prevent others from running, essentially
hanging the CQ system until the original returned

This change parallelizes each CQ and adds a lock for its unique database:name
combination, where it will attempt to get the lock, but timeout after
a configurable amount of time

This is sort of a WIP, and I've been running it for a bit without issue (but we all know that doesn't always mean it is good for everyone). Thought I'd throw it up here in case anyone is interested in commenting/improving.

I was thinking as well that the locking timeout should be relative to the interval that the CQ runs on

@e-dard Wondering if you've had a chance to take a look at this. I've been running the most recent version in a staging environment to ensure the CQs no longer hang or any that hang don't block the rest. I'll continue to run for a while just to ensure there are no other issues, but I wouldn't mind some feedback whenever convenient.

@oldmantaiter I don't have anything against this, but CQs are not really on my radar much. Maybe @jwilder, @dgnorton or @jsternberg have some thoughts?

@oldmantaiter  Thanks for the PR! Looks like it runs all CQs at once. I think we may need a way to limit the number of CQs running at any one time. Possibly a way to limit based on the current CQ load but currently I don't think there's a way to do that.

@e-dard thanks!
@dgnorton : I can add another config option for concurrent CQs and limit it that way, maybe with a sane default of 2 so if a single "worker" slot is blocked, the other ones can rotate through.
Was the reasoning behind the serial approach to CQs to reduce resource consumption and not have these interfere as much with normal operation?

I wasn't around at the time, but I would guess it was just because it was easier to implement and nobody ever did the work to make a worker pool for CQs to work off of.
I think making the worker pool contain a default of maybe the number of goroutines or half the number of goroutines (with a minimum of 1) to be best.

@oldmantaiter there is a limiter type in influxdb/pkg that might be useful.

@e-dard @jsternberg Great, I'll take another look. Thanks for the feedback!

The original plan was to distribute CQ's around the cluster so that a single node was loaded down with all of them. In the meantime, we ran them sequentially on a single node.

@dgnorton Understood, will this cause issues with CQs and clustering that is not open-sourced?

@dgnorton @jsternberg - I've been testing it for a bit locally and it looks good so far, I'll continue to watch for a day or so

Log sample:
[continuous_querier] 2016/07/27 19:14:00 executing continuous query cq_haproxy_incoming_sum_1m (2016-07-27 19:13:00 +0000 UTC to 2016-07-27 19:14:00 +0000 UTC)
[continuous_querier] 2016/07/27 19:14:00 executing continuous query cq_haproxy_incoming_ps_1m (2016-07-27 19:13:00 +0000 UTC to 2016-07-27 19:14:00 +0000 UTC)
[continuous_querier] 2016/07/27 19:14:07 finished continuous query cq_haproxy_incoming_ps_1m (2016-07-27 19:13:00 +0000 UTC to 2016-07-27 19:14:00 +0000 UTC) in 7.382141879s
[continuous_querier] 2016/07/27 19:14:07 executing continuous query cq_cpu_telegraf_1m (2016-07-27 19:13:00 +0000 UTC to 2016-07-27 19:14:00 +0000 UTC)
[continuous_querier] 2016/07/27 19:14:07 finished continuous query cq_haproxy_incoming_sum_1m (2016-07-27 19:13:00 +0000 UTC to 2016-07-27 19:14:00 +0000 UTC) in 7.382851606s
[continuous_querier] 2016/07/27 19:14:07 executing continuous query cq_mem_telegraf_1m (2016-07-27 19:13:00 +0000 UTC to 2016-07-27 19:14:00 +0000 UTC)
[continuous_querier] 2016/07/27 19:14:07 finished continuous query cq_mem_telegraf_1m (2016-07-27 19:13:00 +0000 UTC to 2016-07-27 19:14:00 +0000 UTC) in 24.20589ms
[continuous_querier] 2016/07/27 19:14:07 executing continuous query cq_incoming_ps_1m (2016-07-27 19:13:00 +0000 UTC to 2016-07-27 19:14:00 +0000 UTC)
[continuous_querier] 2016/07/27 19:14:08 finished continuous query cq_incoming_ps_1m (2016-07-27 19:13:00 +0000 UTC to 2016-07-27 19:14:00 +0000 UTC) in 186.832932ms
[continuous_querier] 2016/07/27 19:14:09 finished continuous query cq_cpu_telegraf_1m (2016-07-27 19:13:00 +0000 UTC to 2016-07-27 19:14:00 +0000 UTC) in 1.393895881s

I haven't forgotten about this, just have some other work to finish up before I can get back to this.
One thing of note in the suggested changes is that if two CQs light up at the same time (it happens in testing), then one will always fail, instead of potentially waiting for the previous to finish. The timeout might be useful in this case where, as suggested, it could be based off GROUP BY or RESAMPLE FOR.

@oldmantaiter that's ok. I don't think we're going to add this before 1.0 because it ends up being a substantial change in behavior, so we are thinking of having the default parallelism value being set to 1. After thinking about your comment for a bit, it might be better to have the continuous queries just block the worker pool rather than trying to figure out timeouts or the race condition you pointed out. You can still use a channel in the way I suggested without a default case as a semaphore for managing the worker pool.

@jsternberg I'll be doing some more testing over the next few days, I was thinking though that we'd still want to put in some parallel CQ limit that users can adjust, that defaults to something like 10 but can never go above the number of cores, so that installations with a ton of CQs can't potentially overwhelm the disks by default. As for the timeout, instead of blocking I've made it so that it will wait until the expected next run and error out. If we still want to just block the worker pool, I can implement that instead.
I'll report back in a few days after this has run for a while.

@oldmantaiter thanks for this. As you can see, it's been a long while since this PR was submitted so we're going to close it.
We're certainly interested in approaches to improving the performance of continuous queries
but I think it needs some more though about how they should work—a proposal would
be a good way to do this.

@e-dard Yeah, that makes sense.


Using Terraform Data Sources as a method to determine current state

@Pryz,
Great work putting this module together. Have you considered using the Terraform Data Sources method to obtain the current state of an OU and its attributes? This would make for a smoother transition to target state.
This LDAP provider project seems to be one of the better ones but could really use this feature.
Greg

Hey @MnrGreg that's a pretty good idea.
I'm not really working with this provider anymore but feel free to send a PR :)


Thunder Scans Paid Chapters Causing Issues

Source information
Thunder Scans 1.4.35
Source language
English
Steps to reproduce

Add a series with multiple paid chapters to your library such as Growth-type Superhero (https://en-thunderscans.com/comics/growth-type-superhero/)

Expected behavior
Either all chapters should be shown or preferably all paid chapters hidden (this preference due to the issue in the Other Details section below).
Actual behavior
Only the latest paid chapter is shown followed by the latest free chapter. The ones in between are listed as missing.

Mihon/Tachiyomi version
Tachiyomi Stable 0.15.3
Android version
Android 14
Other details
This also causes another issue in Tachiyomi when using Auto download while reading. When it goes to download a paid chapter it buggs the download queue and all downloads are stuck waiting on it until you manually clear the paid chapter that keeps failing from the queue.
This could be avoided by including a toggle option like some extensions have (Animated Clitched Comics is one example) which allows all paid chapters to be shown/hidden.
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 0.15.3.
[X] I have updated all installed extensions.
[X] I have tried the troubleshooting guide.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

Add a :+1: reaction to issues you find important.

你们都是怎么问问题的，为什么我找不到问题按钮呢，
How did you ask for problem？I cannot look for question button？

请增加空白问题按钮。
pleaseadd blanket issue button.thanks

probably related to #5908
https://github.com/keiyoushi/extensions-source/issues/5908#issuecomment-2466734304

Duplicate of #5908


Make Pulumi version a required parameter in CI build.

Partially fixes #73.   Will do the release build once this burns in a little.


Scavenge method

I would like to be able to run scavenge after hard deleting streams when automating unit tests so the streams are fully removed.

I can implement the method but it will not have the desired effect. Running a scavenge won't delete the latest data.
"Scavenges only affect completed chunks, so deleted events in the current chunk will still be there after you run a scavenge." from http://docs.geteventstore.com/server/3.9.0/scavenging/

Great! I would love to see this.
It is just a way to clearly clear the store between tests and works for me when running manually after a delete so works for me.

It wasn't a suggestion it's a fact stated in the documentation, the url and quote I posted in my previous post. Adding screen capture of the warning. The fact that scavenging worked once is a fluke, it's not guaranteed to work because of that warning and how scavenging/$all work. I did the same tests myself and running a scavenge did not remove the events from $all.

Hmmmm. I guess the documentation is inconsistent then and it's not the solution I'm looking for.
I opened an issue with event store and hopefully they can be convinced that there should be a way to do a clean and deterministic reset of the event store.
Thank you for checking and doublechecking this Nic!
Closing...


Admin color palette: Sass variables / design tokens renaming

Follow-up to #8824, in particular Scott’s comment. Now that almost all of Wagtail’s colors are defined from our design tokens, we need to refine our approach to Sass variables, so their usage makes sense with our design tokens. And maybe review the naming of our design tokens.
Sass variables
Particularly problematic sets of variables are the teals (secondary) and greys:
$color-teal: theme('colors.secondary.DEFAULT');
$color-teal-darker: theme('colors.secondary.400');
$color-teal-dark: theme('colors.secondary.600');

$color-grey-1: theme('colors.grey.600');
$color-grey-2: theme('colors.grey.400');
$color-grey-3: theme('colors.grey.200');
$color-grey-4: theme('colors.grey.100');
$color-grey-5: theme('colors.grey.50');

Those are two sets of variables with non-semantic names that differ from the design tokens’ names. Some of the options to resolve this are to:

Rename those variables to use the same naming scheme as design tokens
Remove those variables and use non-semantic design tokens directly
Replace those variables with semantic ones (for example $color-teal-dark would be replaced by $color-button-bicolor-hover.
Remove those variables, replace non-semantic design tokens with semantic ones, and use semantic design tokens directly (theme('colors.button.bicolor.hover')

Design tokens
There are a couple points we need to solidify:

Usage of numeric scales for the shade of each color – whether the current numbers make enough sense, or whether we should change them (if so how)
How (and whether) to use "default" shades for given colors

Additional areas to consider
As part of this we could also consider:

The addition of more design tokens for the remaining colors that aren’t customisable: addition and deletion highlights, and the focus outline.
Changes to other Sass variables / design tokens than the above two sets.
How we use fades/transparencies of white/black
How we use shadows

Ideally I think we should also think of how those types of setups can help support the introduction of a dark theme, and high-contrast light/dark themes (WCAG 2.1 AAA 7:1 contrast or above).

I’d like to work on this as part of #10056, making sure we end up with one set of variables that supports multiple themes.

Implemented as part of #10056. I went for: Replace those variables with semantic ones.
There is room for improvement on the set of semantic icons – we’ve defined them based on future designs of Wagtail with consolidated colors, rather than the as-is CMS with more variations. So there was some consolidation already but potentially too much.


Preferences page - work in progress - for review

Fixes #441 .
Changes proposed in this PR:

Closing draft to prevent GHA failure alerts


createTerminal with message option doesn't seem to work

Testing #124712
I tried modifying the terminal sample to specify a message in TerminalOptions:
	// vscode.window.createTerminal
	context.subscriptions.push(
		vscode.commands.registerCommand('terminalTest.createTerminal', () => {
			vscode.window.createTerminal(`Ext Terminal #${NEXT_TERM_ID++}`, {
				message: 'Hello World',
			} as any);
			vscode.window.showInformationMessage('Hello World 2!');
		})
	);

But I couldn't get it to output anything

calling vscode.window.createTerminalFromOptions with a message works. not sure if it should also work for vscode.window.createTerminal

Ugh, I knew I was doing something wrong, was specifying the name in addition to the args. Thanks! :)


Use openSSL for windows to get root cert:

Switched from using .NET to openSSL windows binary to extract root certificate due to issues in some cases with .NET

I got the openSSL binary from https://wiki.openssl.org/index.php/Binaries, more specifically the first windows link https://slproweb.com/products/Win32OpenSSL.html


Look into moving release script into its own repository

I want to use it for some other repositories. 😇

Previous related issue: https://github.com/sonarwhal/sonarwhal/issues/536


Multi-dex APKs not completely processed

Hi,
I'm trying to use LibScout with an APK containing 100+ dex files. I found out (after increasing the log levels) that currently only the first 10 classes.dex files are processed, resulting in an incomplete package tree for APKs with 10+ dex files.
The cause of this is the regex in the WALA code: classes[1-9]{0,1}\\.dex.
I think it might be a good idea to get rid of this limitation.
I changed the regex in the DexFileModule.class file to classes[0-9]{0,9}\\.dex and every dex file is successfully processed now. But now I get an exception when exporting to JSON:
ERROR TplCLI                    : [FATAL EXCEPTION] analysis aborted: null
ERROR TplCLI                    : java.lang.NullPointerException
        at de.infsec.tpl.profile.ProfileMatch$Export.<init>(ProfileMatch.java:120)
        at de.infsec.tpl.profile.ProfileMatch.export(ProfileMatch.java:132)
        at de.infsec.tpl.stats.AppStats$Export.<init>(AppStats.java:130)
        at de.infsec.tpl.stats.AppStats.export(AppStats.java:48)
        at de.infsec.tpl.utils.Utils.obj2JsonFile(Utils.java:487)
        at de.infsec.tpl.LibraryIdentifier.identifyLibraries(LibraryIdentifier.java:207)
        at de.infsec.tpl.TplCLI.main(TplCLI.java:155)

Also, I know that you use Joana's WALA fork but any plans to publish your patches?

Ah, I anticipated that this would happen at some point. I will remove this limitation.
As for the Export error, do you have an apk or l <package name, versioncode> that I can test?
Regarding the WALA patches, yes I think it's a good idea to make them available. I will also open a new issue regarding checking LibScout's WALA version against WALA master to see whether patches are already included or can be merged. In the longterm it's certainly preferable to not rely on a custom fork (see also discussion here: https://github.com/reddr/LibScout/issues/16).

Unfortunately I can't share the apk, but thanks anyway.

If you can provide a similar/stripped apk with many dex files that trigger this exception, I can have a look into the problem, otherwise it's pure guessing.

Ok no more reply here.  10+ dex files work now and probably the NPE in the profile export was fixed with the commit https://github.com/reddr/LibScout/commit/88ec8207318ca16aba395c5a17dd1ed964db8fc5


VirtualNetworkRules getting overwritten when running Bicep on existing resource (Storage Account)

Bicep version
Bicep CLI version 0.20.4 (c9422e016d)
Describe the bug
Using the following Bicep code, if I have an existing storage account with a virtual network rules defined, say VNet-One/Subnet-1. It will remove the subnet and add the Vnet/Subnets in VirtualNetworkRules only. Is there a way to apply the new subnets without removing the existing ones?
var addVnets = [
    {
      id: '${vnetid1-id}/subnets/subnetname1'
      action: 'Allow'
      state: 'Succeeded'
    }
    {
      id: '${vnetid2-id}/subnets/subnetname2'
      action: 'Allow'
      state: 'Succeeded'
    }
  ]
...
resource storageAccount 'Microsoft.Storage/storageAccounts@2022-09-01' = {
  name: storageName
  location: location
  sku: {
    name: storageSkuName
  }
  kind: 'StorageV2'
  identity: {
    type: 'None'
  }
properties: {
...
    networkAcls: {
      bypass: 'AzureServices'
      defaultAction: 'Deny'
      virtualNetworkRules: [for subnet in addVnets: {
        id: subnet.id
        action: subnet.action
        state: subnet.state
      }]
    }

Similarly, IPRules will get overwritten.
To Reproduce
Run Bicep against an existing storage account with 1 or more Virtual Networks defined.
Additional context
We have existing storage accounts provisioned with a set of firewall Vnet/Subnets and IPs. As we add more common Vnet/Subnets and/or IPRules, we'd like to run Bicep against the existing storage accounts to add any missing values. Using the code above, it just overwrites the exiting ones. Some storage accounts have specific subnets and IP Rules in place that should remain.

Bring in the existing resource and "patch" it?
So, something like this:
resource storageAccount 'Microsoft.Storage/storageAccounts@2022-09-01' existing = {
  name: storageName
}

var currentRules = storageAccount.properties.networkAcls.virtualNetworkRules

var newRules = union(currentRules, addVnets)

//Re-use existing params (where no change) and apply new params (where change)
module patchedStorage 'storage.bicep' = {
  name: storageName
  params: {
    publicNetworkAccess: storageAccount.properties.publicNetworkAccess
    virtualNetworkRules: newRules
  }
}

I haven't tested this exact piece of code working, but I would attempt to see if it produces something to work off from.

Thanks. I was hoping to have one module (New/Existing) for storage accounts, though. We moved from Terraform because  Bicep handles current state much better. My thought was it would only add new items if they didn't exist. But I can understand how it wouldn't know if you want the Defined VNets Only or the Defined plus any existing. Some TF modules supported Resource child properties using a separate Resource like "Resource VnetProps VirtualNetworkRules" so I could manipulate them and apply them to an existing StgAcct (or KeyVault).
We recently switched to Bicep so I am still trying to understand its techniques.
Thanks, again. I'll consider how to best incorporate your suggestions.

@DevonK3 This is a by-design limitation of the ARM service. A principle that ARM tries to adhere to is that a given template should describe the desired state of a resource following a successful deployment, regardless of the prior state of the resource. You could use the insert resource feature in the VS Code extension or export a template for the storage account in the Azure portal; either way would capture the current state and make your Bicep template authoritative.

Thanks for confirming.

What if you deploy this and the storage account doesn't exist yet ?

Bring in the existing resource and "patch" it?
So, something like this:
resource storageAccount 'Microsoft.Storage/storageAccounts@2022-09-01' existing = {
  name: storageName
}

var currentRules = storageAccount.properties.networkAcls.virtualNetworkRules

var newRules = union(currentRules, addVnets)

//Re-use existing params (where no change) and apply new params (where change)
module patchedStorage 'storage.bicep' = {
  name: storageName
  params: {
    publicNetworkAccess: storageAccount.properties.publicNetworkAccess
    virtualNetworkRules: newRules
  }
}

I haven't tested this exact piece of code working, but I would attempt to see if it produces something to work off from.


CPM: sort charities by amount raised

hmmm.. the sort isn't working on the preview even though it works on local

force pushed because I didn't realized this was reviewed lool


API add nightly param

like title
/cc @hugomrdias

@hugomrdias for CI you need to specify the x-ipfs-benchmarks-api-key
Do you have a keybase account I could use to send the api key to?

yeah just sent you a follow

This  PR adds the nightly parm to the API


Best design for plugins?

Currently, the annotation tools are all implemented using separate functions that duplicate quite some functionality.
It would be better to find a design that enables sharing more of the common functionality between them.
There are two different approaches:

Using a class and inheritance design.

It's a bit unclear to us how exactly this would work with magicgui, but maybe we could use https://github.com/hanjinliu/magic-class

Use auxiliary functions that refactor the common functionality. This is the current approach, but many things are not refactored yet. The util functions are in https://github.com/computational-cell-analytics/micro-sam/blob/master/micro_sam/sam_annotator/util.py

It's a bit unclear to us how exactly this would work with magicgui

also consider dataclasses: https://pyapp-kit.github.io/magicgui/dataclasses/

We have decided now to go with a "normal" class design and use inheritance, see #304. I decided against dataclasses because the logic for initializing the plugins here is a bit more complex and requires a full fledged init.


Non-blocking reads

Updates almost all comms code between the z80 and VDP to be non-blocking, and to timeout.
(The only blocking read commands that remain are those inside hexload.h)
Adds a readIntoBuffer call, which is used for all places that read data from the VDU stream into a buffer.  This call is given a buffer pointer and the number of bytes we're expecting to read, and will return zero when the buffer has been read successfully, or if the read times out the number of bytes that were missing.  The timeout is based on the time from when data was last received, rather than when the call was made.  This way larger transfers shouldn't timeout unless there is a genuine delay.
The performance of readIntoBuffer in testing is identical to @astralaster's earlier comms performance enhancement code.  (It uses a very similar technique.)
discardBytes has also been updated to be non-blocking.
A great plus with these changes is that the VDP will no longer hang waiting for data that will never come on dodgy/flakey VDU calls.  For example, attempting to use an "upload bitmap" or "upload sample" call from the CLI often/usually results in a command that doesn't include all the expected data.  (Sending a byte instead of a word for one of those calls typically results in the VDP expecting far more data than the user intended.)  When this happens the VDP would be left in a state waiting for data that could never come, requiring the user to press the "reset" button to recover.
With these changes the command times out, the data will be discarded, and the computer is usable again.
(NB typically when such faulty commands are sent, the VDU system will also be sent other data such as the > prompt in BASIC, which will be captured as part of the data stream.  If the user has sent a duff command from the BASIC CLI they'll be left on an empty line with no visible prompt, but they can enter commands.)

an added bonus of this PR is that I'd experienced some strange issues with the new version of the Arduino IDE with reads on the comms channel stalling.
this revised approach, coupled with using the latest version of the ESP board manager (2.0.13) appears to fix that issue.  the new board manager version offers improved comms performance and leaves enough free internal memory for all the screen modes to work (which 2.0.11 didn't).


In testing: toMatchImageSnapshot does not take image dimensions (width/height) into account when diffing images.

These two images is considered the same:

A proposed solution is to also use https://www.npmjs.com/package/image-size to measure width and height on .toMatchImageSnapshot.


question about protein complex scaffold

GO:0032947
Name	protein complex scaffold
is defined
Functions to provide a physical support for the assembly of a multiprotein complex.
and is a descendant of
GO:0005198 structural molecule activity
The action of a molecule that contributes to the structural integrity of a complex or assembly within or outside a cell.
I have therefore always used this for a "protein complex scaffold" which forms an integral part of the final protein complex when assembled. Like, for instance
SIN component scaffold protein, centriolin ortholog Cdc11
onto which the other complex subunits assemble
like this:

However, I see it is also used for ecm29
http://www.pombase.org/spombe/result/SPAC1782.01
which is a "chaperone" it is used as a scaffold "during assembl" but is not part of the final complex.
These are quite functionally different.
Should "protein scaffold" be used for both (in which case the parentage is not really correct)?
Do we need a term to represent an assembly chaperone ?

It seems to me that the assembly chaperone's function is just protein complex assembly. It is not a stable scaffold.

So you would say it should not be used for ecm29 ? I can see how it could be based on the current def...

Maybe ecm29 should be annotated to both assembly and scaffold.

But it isn't a scaffold in the sense  of a structural molecule. I think the term "protein complex scaffold" is ambiguous....
It isn't part of the final complex.

Is it a structural molecule during assembly? It seems to me that a scaffold encompasses both of these.

but the parent term is
The action of a molecule that contributes to the structural integrity of a complex or assembly within or outside a cell.
(assembly is a noun here not a verb!)
The definition changes in the "protein scaffold term" and it could be interpreted as being a structural molecule "during" the assembly process.
But what does this mean? Isn't this what an assembly chaperone does?

How about:
The action of a molecule that contributes to the structural integrity of a complex or its assembly within or outside a cell.
Then the child:
A structural molecule activity that provides a physical support for the assembly of a multiprotein complex.

Should make it clear that the structural molecule may or may not be part of the final complex. This is the part which flummoxed me.....

name: structural molecule activity
namespace: molecular_function
-def: "The action of a molecule that contributes to the structural integrity of a complex or assembly within or outside a cell." [GOC:mah]
+def: "The action of a molecule that contributes to the structural integrity of a complex or its assembly within or outside a cell." [GOC:mah, GOC:vw]
subset: goslim_aspergillus
subset: goslim_candida
subset: goslim_chembl
id: GO:0032947
name: protein complex scaffold
namespace: molecular_function
-def: "Functions to provide a physical support for the assembly of a multiprotein complex." [GOC:mah]
+def: "A structural molecule activity that provides a physical support for the assembly of a multiprotein complex. The scaffold may or may not be part of the final complex." [GOC:mah, GOC:vw]
is_a: GO:0005198 ! structural molecule activity
is_a: GO:0005515 ! protein binding

Hi @ukemi and @ValWood
This seems like an ontology issue that we should at least alert curators to on the next annotation call, as the meaning may have slightly changed.  I think I also usually interpreted the term def the same way as Val, i.e., the scaffold stuck around as part of the final complex.  Perhaps others did as well?

OK. Let's put it on the agenda. We can change back if necessary.


Nested SegmentGroups With Same Starting Name

I have to parse an X12 file format which uses the same segment name (TFS) for two purposes:

to define a tax return
to define schedules within the return

A simplified structure looks like this:
ISA
GS
ST
    TFS~T2~900
        REF
        DTM
        TFS~T3~S03A01~PG~160~94~CE
            REF
        TFS~T3~S1~PG~161~94~J
            REF
SE
GE
IEA

This commit is how I propose to solve the issue.  I had to make this kind of adjustment to prevent the return from being popped off the stack.
The return class is defined like so:
[EdiSegmentGroup("TFS", SequenceEnd = "SE", AllowNestedGroupWithSameStartSegment = true), EdiCondition("T2", Path = "TFS/0")]
public class FuelTaxReturn
{
     public DateSegment DateSegment { get; set; }
     public ReferenceSegment Reference { get; set; }
     public List<TaxSchedule> TaxSchedules { get; set; }
}

The declaration of the schedule starts with
[EdiSegmentGroup("TFS"), EdiCondition("T3", Path = "TFS/0")]
public class TaxSchedule
{
   public ReferenceSegment Reference { get; set; }
}

There is a bit more to these classes in my real code but I think this adequately describes my situation.  Any thoughts?

This seams reasonable, although I recently made some changes to the code you are referring to. I will check if I can make a failing test with this.

FYI, I discovered in further testing my modification doesn't handle more than one return in the same file properly.
TFS~T2~CCR
  TFS~T3
  TFS~T3
TFS~T2~SDR
  TFS~T3
  TFS~T3

When the second return is reached, two items need to be popped off the stack and only one is getting popped off.  The logic surrounding my new boolean property will need to change.  I think the answer is to move the break inside closeThisLevel like so:
  if (closeThisLevel) {
    level.Close();
    index = level.Index + 1;
    break;
  }

Seconding this issue...

This was tricky to resolve but I believe this second commit I made to my branch gets the job done.  It introduces more complexity than I had hoped would be necessary but I don't think it is excessive.  Am I making this harder than it ought to be?
If you are satisfied with the direction I am taking, I can turn this into a pull request.

Why not use multiple condition data annotations instead?
Example for EDI 810 with multiple uses for BAL segment with P as the first value.
BAL*P*YB*6.66~
BAL*P*TP*5.55~

[EdiCondition("P", Path = "BAL/0"), EdiCondition("YB", Path = "BAL/1")]
public EdiBalance PriorBalance { get; set; }

[EdiCondition("P", Path = "BAL/0"), EdiCondition("TP", Path = "BAL/1")]
public EdiBalance TotalPaymentsAndRefunds { get; set; }

@cleftheris let me know if there is anything you need from me.

@cleftheris I added a new commit to my feature branch which makes a slightly altered version of your test pass.  I added some comments to your commit explaining what I had to change and why.

@richardwalenga Please proceed and make a pull request. Before you do so, you will have to fork the repo again or pull the latest changes. The only thing I am not comfortable with, is I believe the extra setting AllowNestedGroupWithSameStartSegment  on the Attribute. I think it will introduce some confusion and I am already struggling to make some of the Library features more intuitive. That said can we live without this? Furthermore the mare existence of a Condition attribute is a good indicator that there might be a chance of nesting. Thanks for taking the time to give back.

@cleftheris I can understand your reservations about AllowNestedGroupWithSameStartSegment.  I did consider instead checking for the presence of at least one EdiCondition on the level in place of that attribute, but that in itself wouldn't be enough information to know this current segment group could be a child of the existing segment group, a sibling of its parent, etc.
I am thinking with the way things are currently structured, the only way viable way to accommodate this need without a new EdiSegmentGroup attribute is to have new instances of EdiStructure get a reference to the parent EdiStructure passed in via the constructor at the end of EdiSerializer's TryCreateContainer like so:
stack.Push(new EdiStructure(newContainer, propValue, index, current));

The EdiStructure class would have to be changed to include this new field and constructors:
private readonly EdiStructure _Parent;

public EdiStructure(EdiStructureType container, object instance)
        : this(container, instance, 0, null) {

public EdiStructure(EdiStructureType container, object instance, int index, EdiStructure parent) {
       ValidationUtils.ArgumentNotNull(instance, "instance");
       _Container = container;
       _Instance = instance;
       _Index = index;
        _Descriptor = typeStore.Get(instance.GetType());
        _Parent = parent;
        _CachedReads = parent?.CachedReads ?? new Queue<EdiEntry>();
}

What do you think of that?  I am not sure the logic inside the main foreach loop which descends the stack will get much simpler but it would save on having to keep a reference to the child structure and the use of at least one boolean.

@richardwalenga in the end I had to pass the parent level reference since I had to check for a level siblings before moving deeper inside the hierarchy. I am pushing a release right now. I am always open to improvements so I would like to see aditional test scenarios.


"CollectionViewWaterfallLayoutDelegate is not defined" for waterfall plugin on IOS, Angular

Issue appear on device for IOS, it does not appear on android emulator.
Tbh, I wanted to recreate stackblitz for completely different issue ( when we have large list of items with different height with waterfall plugin - opening detail view of item after scrolling a bit and then getting back to the list - opens list on scrolled state, ordering the list only for this specific viewport and then scrolling up it reorders list dynamically, items are jumping from place to place )
Which platform(s) does your issue occur on?

iOS v17.5.1
device

Please, provide the following version numbers that your issue occurs with:

Plugin<EMAIL_ADDRESS>

Please, tell us how to recreate the issue in as much detail as possible.
https://stackblitz.com/edit/nativescript-stackblitz-templates-ceomer?file=package.json,src%2Fapp%2Fapp.module.ts&title=NativeScript Starter Angular

@EugeneHerasymchuk It works fine here. Seems like a cocoapod issue. Make sure cocoapod is run correctly and that the plugin pod dependency is installed. You can try to clean and build again


dts: bindings: timer: Correct compatible name of riscv,machine-timer

dts/bindings/timer/riscv,machine-timer must have compatible name
riscv,machine-timer. nuclei,machine-timer is wrond, correct it.
Due to the wrong compatible name, the properties defined in riscv,machine-timer not applied.
At this time, only affect GD32VF103 SoC using this dts node.
Due to the wrong compatible name, the properties defined in riscv,machine-timer not applied.
At this time, only affect GD32VF103 SoC using this dts node.

@gmarull ,
I think this problem perhaps actualized on the gd32vf103v-eval board.
Could you please tell me your board whether working correctly?
(If work not correctly, sample/basic/blinky probably work very slowly with 4 seconds.)


Import promises from a Google sheet

Existing promises are now updated

Current coverage is 80.87% (diff: 72.16%)

Merging #15 into master will decrease coverage by 4.36%

@@             master        #15   diff @@
==========================================
  Files            14         17     +3
  Lines           244        319    +75
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            208        258    +50
- Misses           36         61    +25
  Partials          0          0

Powered by Codecov. Last update fefc146...41260f7

Fixes #13


⚠ Bofrost.com has degraded performance

In fec74a6, Bofrost.com (https://www.bofrost.com) experienced degraded performance:

HTTP code: 200
Response time: 909 ms

Resolved: Bofrost.com performance has improved in 6edccac after 6 minutes.


Have no more than 3 participants in a row in the carousel

More than 3 people makes the aspect ratio look really weird, even on a 16:9 screen.  Suggest we start stacking them vertically beyond that point.
A nicer solution to #37 might be to always put the local video on top, too.

Addressed in #49


Change donation button color to green

Green would look better for a donate button

The current language is already displayed in green. Two green texts won't look better.


Distribution request: rocrate on conda forge

As an academic distributing software, I've just found myself making a conda environment (instead of a pip requirements.txt file). I'd like to be able to conda install -c conda-forge rocrate instead of:
dependencies:
  - python=3.10
  - pip
  - pip:
    - "rocrate"

A search https://anaconda.org/search?q=rocrate doesn't show rocrate as available inside the anaconda ecosystem.

Hi @Denubis , I guess you should also open this issue about having a conda package for rocrate Python package at https://github.com/ResearchObject/ro-crate-py , which is the repo behind the python implementation

Can do. Should I close it here?

Can do. Should I close it here?

Yes, your request is specifically about ro-crate-py.


Chaneg Event for Tabs click

Version
Tell us which versions you are using:

react-native-router-flux v4.?.? (v3 is not supported) - "^4.0.0-beta.28"
react-native v0.?.?  - "0.52.0

Tabs Navigation
Steps to reproduce
I have Three tabs
like Home,Search,Settings
In Home Tab
- homeScreen
- SectionOne
- SectionTwo
In Search Tab

SearchScreen

In Settings Tab

A
B
C

Issue is
Here the issue when I click on Home Tab it redirects to  homeScreen then clicked on item in homeScreen it redirects to SectionOne.Then I  click on Search Tab.it redirects to SearchScreen.Then again Click on Home Tab.it redirects to SectionOne Scene(Actually i need to redirect homeScreen ).And am not using Redux Guys

Could you please help Me guys @Blapi @aksonov  . and Sorry for bad English

Sorry, it is not supported


Melody Pottery Sherd Pattern doesn't work properly on 1.20.1

Hi I'm on version dwdsb-1.5.1 on 1.20.1 and whenever I use the melody pottery sherds, the normal side texture is displayed instead of the pattern.

Nvm on further research its because I didn't have the sherd api installed. Ideally the sherd api should be marked as a dependency in the fabric.mod.json to stop the game from loading without it

(As you know) working on an update for 1.20.1 that removes the need for the SherdAPI. Thanks for the heads up!


Add AC-3 boxes

@sunfish-shogi
This adds support for the AC-3 codec by adding the ac-3 and dac3 boxes, defined in ETSI TS 102 366.
By the way, AC-3 can now be used without any restriction since all its patents expired some years ago.

LGTM!
Thanks!


http2: reenables oghttp2 by default

Flips the runtime feature envoy_reloadable_features_http2_use_oghttp2 to be true by default.
Commit Message:
Additional Description:
Risk Level:
Testing: ran unit and integration tests locally, ran load tests exercising Envoy with oghttp2
Docs Changes:
Release Notes: Changes the default HTTP/2 codec from nghttp2 to oghttp2. Can be reverted by setting "envoy_reloadable_features_http2_use_oghttp2" to false.
Platform Specific Features:

/assign @RyanTheOptimist

This should probably have a release note (similar to #31086).

Oh, that's a very good point. @birenroy can you add one?

This should probably have a release note (similar to #31086).

Oh, that's a very good point. @birenroy can you add one?

Done, thank you both.


Changing 'static/media/' path?

Hi,
I can't see the build path where media gets stored as a configured anywhere. Is it possible to override this?
Thanks

You can modify it by altering the file loader rule in razzle.config.js I can show some code tomorrow.

As per the comment from @fivethreeo, you can adjust the loader configuration by defining a razzle.config.js file. Not very clean, but it does the job. Just a side note, the static folder will still be inside the main build folder.
module.exports = {
  modify: (config) => {
    config.module.rules[2].options.name = "static/[name].[hash:8].[ext]";
    config.module.rules[3].options.name = "static/[name].[hash:8].[ext]";

    return config;
  }
};

fixed in dev


Set up Elasticsearch & openly available kibana with complete Loc-instances-Bibframe dataset

While the solution provided in a) https://github.com/hbz/lobid-resources/issues/851 is not proper enough but b) https://github.com/hbz/swib18-workshop/issues/2 not fast enough we go again with a) using java-jsonld, facing some issues which must be resolved, see https://github.com/hbz/lobid-resources/issues/940.

@dr0i is now able to convert the LOC data with the Java JSON-LD library and the output looks much like what we generate in the workshop. Here is the current status with the same example that we use in the workshop:

Example record: https://github.com/hbz/lobid-resources/blob/523-addLanguageTagSupport/src/test/resources/jsonld-loc/c000101650
JSON-LD context: https://github.com/hbz/lobid-resources/blob/523-addLanguageTagSupport/web/conf/context-loc.jsonld

The current differences to the JSON-LD from the workshop (at least those I have found) are:

all types have an array (which is intended but we will have to think about whether we actually want it for the LoC data)
http://id.loc.gov/ontologies/bflc/EncodingLevel is mapped to EncodedLevel in the context (instead of EncodingLevel), see https://github.com/hbz/lobid-resources/blob/523-addLanguageTagSupport/web/conf/context-loc.jsonld#L65
Also, the pending fix for the missing datatypes in the context (https://github.com/hbz/swib18-workshop/pull/30) has to also be implemented in lobid-resources.

Thanks for indexing. Will soon take a look.

so it takes roughly the same time as the ETL of lobid-resources.

\o/ This is good to hear.

Just took a look at the data. Here is what I noticed.

Some things are missing in the context as MADS classes are not compacted: http://www.loc.gov/mads/rdf/v1#ComplexSubject, http://www.loc.gov/mads/rdf/v1#GenreForm, http://www.loc.gov/mads/rdf/v1#Temporal, http://www.loc.gov/mads/rdf/v1#Geographic etc. also the MADSproperty http://www.loc.gov/mads/rdf/v1#isMemberOfMADSScheme. Also some bflc properties: http://id.loc.gov/ontologies/bflc/consolidates, http://id.loc.gov/ontologies/bflc/relatorMatchKey, http://id.loc.gov/ontologies/bflc/applicableInstitution where the first two are also missing in the workshop context (see https://github.com/hbz/swib18-workshop/issues/32).
Why not use the context at https://github.com/hbz/swib18-workshop/blob/master/data/context.json (It would be easier for me to work with one context anyway.)
Kibana is quite helpful for finding other errors. When I got to "Management" -> "Index Patterns" -> select "loc_works" and then filter by http:// I get all fields with a "http" in them. There are those already noted in 1.) and some more that have in common that they have "@language": null in the context at https://github.com/hbz/lobid-resources/blob/523-addLanguageTagSupport/web/conf/context-loc.jsonld

I guess, nearly all errors will be fixed with using the workshop context. The rest will be fixed with https://github.com/hbz/swib18-workshop/issues/32.

For documentation: Some records are not indexed in ES because they have no valid date as value of adminMetadata.changeDate.

BTW, a lessons learned for Kibana: At "Management" -> "index patterns" -> "loc_works" I had to refresh the field list. Otherwise the fields from the previous index would be shown there and also in the field autosuggests for creating a visualization.

@acka47 I indexed loc-works-bibframe with the workshop's json-context. You have to set the index-alias to use it for kibana. 3k more documents are missing now, you will get the lobid-admin mail complaining about [MapperParsingException[object mapping for [language] tried to parse field [null] and some more for subject etc. and the known adminMetadata.changeDate.

Taking a look at the new index, some of the property/type URIs are now compacted but some others are still missing:

[x] http://www.loc.gov/mads/rdf/v1#ComplexSubject
[ ] http://www.loc.gov/mads/rdf/v1#GenreForm -> missing in context as there is also bf:GenreForm
[ ] http://www.loc.gov/mads/rdf/v1#Temporal -> missing in context as there is also bf:Temporal
[x] http://www.loc.gov/mads/rdf/v1#Geographic
[ ] http://www.loc.gov/mads/rdf/v1#isMemberOfMADSScheme
[ ] http://id.loc.gov/ontologies/bflc/consolidates
[ ] http://id.loc.gov/ontologies/bflc/relatorMatchKey
[x]  http://id.loc.gov/ontologies/bflc/applicableInstitution

For bflc:consolidates and bflc:relatorMatchKey see https://github.com/hbz/swib18-workshop/issues/32#issue-380149286. I also found the problem with mads:GenreForm and mads:Temporal. What I do not understand is why mads:isMemberOfMADSScheme is not compacted as it is in the current context, see https://github.com/hbz/swib18-workshop/blob/master/data/context.json#L1114


[CARBONDATA-2363][branch-1.3] Add CarbonStreamingQueryListener to SparkSession

Be sure to do all of the following checklist to help us incorporate
your contribution quickly and easily:

[x] Any interfaces changed?

[x] Any backward compatibility impacted?
no

[x] Document update required?
no

[x] Testing done
Please provide details on
- Whether new unit test cases have been added or why no new tests are required?
- How it is tested? Please attach test report.
- Is it a performance related change? Please attach the performance test report.
- Any additional information to help reviewers in testing this change.

[x] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.
small

LGTM

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/5215/

@jackylk @QiangCai I raise a hotfix pr to fix import error after this pr was merged. The 'CarbonStreamingQueryListener' is in the package 'import org.apache.spark.sql.execution.streaming' on branch-1.3, not the package 'org.apache.carbondata.streaming'.


Fix error code on declaration validation

There is a declaration validation on  GET-methods in Medical Events that respond with 401 in case of failure.


vendor:publish states Nothing to Publish

php artisan vendor:publish --provider=rigor789/airbrake-laravel
Nothing to publish.

Do you have an airbrake.php in your configs folder? If all fails, just create it manually, and put these in there: https://github.com/rigor789/airbrake-laravel/blob/master/src/config/airbrake.php

Thanks - didn't have airbrake.php in my config folder; just copied manually which works - thanks!

I got the same error, but thanks for the fix


mac没问题  win好像有个路径报错。[Bug]

Search before asking

[X] 我在 issues 列表中搜索，没有找到类似的内容。
I searched in the issues and found nothing similar.

Pake version
最新的版本[version  2.3.3]
System version
macOS Sonoma 版本14.0 Beta版(23A5301h)
Node.js version
我用的Github在线生成
Minimal reproduce step

What did you expect to see?

What did you see instead?

Anything else?
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

同样的问题，蹲一下

这个issuehttps://github.com/tw93/Pake/issues/541是同样的问题，我把中文文件名改了就好了，希望对你有帮助

while building Linux artifacts and having similar issue, I found out that the build is silently failing, thus not producing any artifacts. Looking through the logs I discovered that the --resize argument is irrelevant and causing the error. I removed the relevant block from the workflow script and it is working now

这个issue #541 是同样的问题，我把中文文件名改了就好了，希望对你有帮助

我用的是英文的包名。

你应该重新打开这个问题


Allow Chatterino Nightly auto-updating

Allow Chatterino Nightly users to auto update.  Having enabled "Receive beta updates" in settings, I noticed that my Nightly Chatterino never updated. I suppose it's intentional though seeing as there was a commit (7cbbd72) that disabled Nightly updates. I was wondering if we could get this feature back, or was it removed for a specific reason?

I suppose it's intentional though seeing as there was a commit (7cbbd72) that disabled Nightly updates.

The reason for this commit was to remove the arrow offering the ability to update for nightly builds, as the updater does not work for them, see #1310.
IIRC "receive beta updates" are not synonymous with the newest commits that nightly gets, I believe they still have to be manually pushed on @fourtf 's side.
Since I'm unable to find any other threads suggesting this, you can probably leave it open until somebody else who knows the coding aspect reason for why nightly doesn't update, has commented positively or negatively towards it.

Receive beta updates relates to beta builds, not nightly builds
I like the idea of this, but nightly releases on EVERY commit. We should time nightly released to every night UTC as opposed to on every commit.
Unless someone has a better option, I think auto-updating nightly would be nice.

If we create an update stream for nightly it would be quite useful for #2641