FINERACT-724 Upgrade Spring Boot, Spring and Spring Security to their latest stable version

This is upgrade of Spring Boot, Spring, Spring Security, OpenJpa and other related libraries to their latest versions.
All Integrations tests are passing with the new commits. But I would like to describe issues I have encountered during development:

Spring security does not support custom SaltSource. it is now random generated. So I used MessageDigestPasswordEncoder and V353__migrate_passwords_to_ss_5.sql for password migration.

There is huge trobule with OpenJpa and Spring5 compatibility. OpenJpaVendorAdapter was removed from Spring5. (See:  https://jira.spring.io/browse/SPR-16035?redirect=false&focusedCommentId=160186&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel) So I have upgraded OpenJpa and moved some code from spring 4 to fineract project. This solution has to be reviewed twice. I do not like it but this is the only way I have made it works. I have tried without jpaVendorAdapter but it leads to:
"SQLException: Lock wait timeout exceeded; try restarting transaction"

Alot of issues I had with dependencies.gradle and dev-dependencies.gradle they have alot of duplicates and dev is out of date. I think after Tomcat removal we could will leave only dependencies.gradle.

WOW! Real nice. -- I'll try to find time to review this properly ASAP; say coming 1 week. (The security related changes in particular probably deserve a closer look.)

@conradsp @awasum @Anh3h @vishwasbabu have you seen this one?  Really cool, no?
Perhaps any of you'd like to chime in & help review this as well?

@ivan333m thanks for your updates! I'll re-review as soon as I have more than a quick moment like now. (BTW @awasum @conradsp @awasum @Anh3h @vishwasbabu would you also like to review this, or shall I just go ahead and merge it when it Looks Good To Me? No stress, just checking if any interest from any of you. Specifically, there is some security related changes here which I would welcome more eyes on.)
On the last build, the integrationTest failed (only) below, will you have a look at that? If you suspect that it's some intermittent issue which you can not reproduce locally, then just rebase this PR so that a new build runs:
org.apache.fineract.integrationtests.RecurringDepositTest > testRecurringDepositAccountWithPrematureClosureTypeTransferToSavings_WITH_HOLD_TAX FAILED

    java.lang.AssertionError at RecurringDepositTest.java:643

„...I'm also hoping that we get a few more eyes from the community to review this - let's see...“

This looks like a job tailor-made for SonarQube's Cloud-based security vulnerability analysis.
 For free!
Here's an example of the sort of vulnerabilities it detects:

ProcessorHelper - HostNameVerifier
TrustModifier - TrustHostnameVerifier
ProcessorHelper - checkServerTrusted
ProcessorHelper - checkClientTrusted
TrustModifier - checkServerTrusted
TrustModifier - checkClientTrusted

As you probably already know: Whether or not the things it reports are real-world security concerns for your particular system, is your call. SonarQube just tells you what it detects. Then you have to determine — out of all the different things it reports — which ones are false positives and which ones are actual vulnerabilities, in the particular context of your specific system.
HTH

@lingocoder that is a great suggestion. @vorburger I don't have access to the Apache org on Github to enable SonarCloud - do you have sufficient access to do so?

@ivan333m thanks for your updates! I'll re-review as soon as I have more than a quick moment like now. (BTW @awasum @conradsp @awasum @Anh3h @vishwasbabu would you also like to review this, or shall I just go ahead and merge it when it Looks Good To Me? No stress, just checking if any interest from any of you. Specifically, there is some security related changes here which I would welcome more eyes on.)
On the last build, the integrationTest failed (only) below, will you have a look at that? If you suspect that it's some intermittent issue which you can not reproduce locally, then just rebase this PR so that a new build runs:
org.apache.fineract.integrationtests.RecurringDepositTest > testRecurringDepositAccountWithPrematureClosureTypeTransferToSavings_WITH_HOLD_TAX FAILED

    java.lang.AssertionError at RecurringDepositTest.java:643

I can't reproduce the fail locally. So I have made a rebase. But build failed again. In logs I have found
BUILD SUCCESSFUL in 18m 8s  and a batch of deadlocks. It a little bit confusing. :)

@vorburger once we merge this, will we be able to also merge https://github.com/apache/fineract/pull/649

Hi All,
Looks like the Travis result shows the health endpoint is not available. I checked locally, the build is Ok but the health endpoint which is called in Travis is not available. I even added an exception in Spring Security configuration locally and it did not solve the problem. See:

When I add basic auth credentials, I get 401: Unauthorized..See:

Secondly, when I connect this upgraded version of the backend to the Mifos Front end here: https://github.com/openMF/community-app, I am unable to log in to the App with credentials mifos/password.
Does anyone have an idea why this is happening? Maybe, I am missing something.

„...I'm also hoping that we get a few more eyes from the community to review this - let's see...“

This looks like a job tailor-made for SonarQube's Cloud-based security vulnerability analysis.
 For free!
Here's an example of the sort of vulnerabilities it detects:

ProcessorHelper - HostNameVerifier
TrustModifier - TrustHostnameVerifier
ProcessorHelper - checkServerTrusted
ProcessorHelper - checkClientTrusted
TrustModifier - checkServerTrusted
TrustModifier - checkClientTrusted

As you probably already know: Whether or not the things it reports are real-world security concerns for your particular system, is your call. SonarQube just tells you what it detects. Then you have to determine — out of all the different things it reports — which ones are false positives and which ones are actual vulnerabilities, in the particular context of your specific system.
HTH

Looks like Apache Infra has a process to enable this: https://cwiki.apache.org/confluence/display/INFRA/SonarQube+Analysis
We might look at this in a separate PR/issue.

@ivan333m , @vorburger . I think the Health Actuator endpoint changed in recent version of spring boot(2.1.7) which this PR is using. So in Travis, we might need to change the http test call to: https://localhost:8443/fineract-provider/actuator/health. This should hopefully solve the failing Travis test. @ivan333m will you be able to help with this? Here is the travis file/line: https://github.com/apache/fineract/blob/23c3f23e12ad04563b2c0d5353b143cdf70911de/.travis.yml#L65
I would have done a PR but I like it to be done here so the review comments are in one place...I might send a test PR to see if am right, but go ahead and make the change here on your branch.

Thank you, Awasum!!!
I have just committed the change to my branch.
Ivan.
чт, 21 нояб. 2019 г. в 12:22, Awasum Yannick<EMAIL_ADDRESS>
@ivan333m https://github.com/ivan333m , @vorburger
https://github.com/vorburger . I think the Health Actuator endpoint
changed in recent version of spring boot(2.1.7) which this PR is using. So
in Travis, we might need to change the http test call to:
https://localhost:8443/fineract-provider/actuator/health. This should
hopefully solve the failing Travis test. @ivan333m
https://github.com/ivan333m will you be able to help with this? Here is
the travis file/line:
https://github.com/apache/fineract/blob/23c3f23e12ad04563b2c0d5353b143cdf70911de/.travis.yml#L65
I would have done a PR but I like it to be done here so the review
comments are in one place...I might send a test PR to see if am right, but
go ahead and make the change here on your branch.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/fineract/pull/642?email_source=notifications&email_token=AMQZIK3Z5VB26XTPZTPZRRLQUZOPZA5CNFSM4I7ZF742YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEZW6LA#issuecomment-557018924,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMQZIK7VYPXKTRP2VOO3WYDQUZOPZANCNFSM4I7ZF74Q
.

If you log into sonarcloud.io with your apache linked github ID you should be able to access the Apache Fineract instance to configure.

@awasum @ivan333m I opened a ticket on Apache Infra for sonarcloud.io - it's now there for Apache Fineract and needs to be configured. I'm waiting for them to enable it across the Fineract CN repos - would it be all of them?

Yes, I think.

I have found that the upgrade has broken oauth authentication.
I will try to fix this issue.

@ivan333m again I want to thank you for this contribution - this is incredible work!
I've now done a fairly detailed code review, and think this looks great, from my side. I did have a few minor suggestions and questions which perhaps you would like to take into account.
I'm also hoping that we get a few more eyes from the community to review this - let's see.

I have done a quick review of this PR. It looks good to me. I have connected this upgraded backend with mifos community app and tested that login works. Most major CRUD operation works as far as I can tell. I have not done a security audit to see how the upgrades affects security. We can do that later. @vorburger I wont know if this resolves the conversation for you as your review here is the only red flag preventing me from merging this.

I have found that the upgrade has broken oauth authentication.
I will try to fix this issue.

Ok..Go ahead.

I have committed fix for oauth authentication and some refactoring for
basic.
It would be nice additionally check oauth authentication (I have made some
checks, but due to lack of integration tests, it should be checked twice)
I think the PR could be merged if there are no probs with these cases.
@Michael, please, let me know if I miss (leave unanswered) the points from
your review.
Best regard,
Ivan
пт, 22 нояб. 2019 г., 13:44 Awasum Yannick<EMAIL_ADDRESS>
I have found that the upgrade has broken oauth authentication.
I will try to fix this issue.
Ok..Go ahead.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/fineract/pull/642?email_source=notifications&email_token=AMQZIK6M5HO2Y62XE6BYADLQU7A2XA5CNFSM4I7ZF742YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEE5MZBQ#issuecomment-557501574,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMQZIKZYZD5WXZJ3NSM5ULTQU7A2XANCNFSM4I7ZF74Q
.

Hello! I'm alive, was just really busy at work.. I'll re-review and
hopefully (likely) merge this some time over this weekend..

Hm, this isn't trivial to clean up... I'll have another go at this may be tomorrow or Monday night.  @awasum  or @ivan333m if you can figure out how to make this have a cleaner commit and change list, go for it...

FTR: This was merged in #653.


i18n(fr): add guides/overriding-components.md & reference/overrides.md

What kind of changes does this PR include?

Changes or translations of Starlight docs site content

Description
This pull request adds the french translation of the guides/overriding-components.md and reference/overrides.md pages (including the fix from #833).
Regarding the translation of override in french, there are multiple possibilities:

remplacer which would be the most accurate translation for the common replace verb.
surcharger which would be the most accurate translation for overload in the context of programming, e.g. Java method overloading.
redéfinir which would be the most accurate translation for override in the context of programming, e.g. Java method overriding.

Considering the definitions of overloading and overriding in the context of programming, I went with redéfinir (verb) and redéfinition (noun) for the translation of override in the context of Starlight components.
A small note about render too which is used a lot in these pages, as far as I know, we do not really use the translation of the verb render in french in this context. This is also visible in the french React docs where rendre is never used compared to the english version. We have the word rendu that can be used but it is a noun, so in this translation, when a verb is needed I often fallback to utilisé (used) or affiché (displayed).
I am also taking part in Hacktoberfest.

Add myself the hacktoberfest-accepted tag before merging, hope that is ok.


feat: add a schema for serialization

Starting a schema for serialization as discussed at PyHEP dot dev.

@HDembinski, what you do think? Rendered version is at https://uhi--105.org.readthedocs.build/en/105/serialization.html. Main focus currently is on names, etc. @aryamanjeendgar is going to start working on the HDF5 Python backend based on this proposal soon.


Record logs when Dashboards plugin integration test fails

Is your feature request related to a problem? Please describe
Currently we can see the video if a cypress test fails, but it is still difficult to debug if the UI doesn't show the root cause and we cannot reproduce the failure on our side. An example, one cypress test failed with UI showing an object is not found while the same object is found before and after page load, and the test succeeded after rerun. It would be helpful to have some backend logs to debug.
Describe the solution you'd like
Record OpenSearch and Dashboards logs as well, so we can determine and fix any flaky test or environment setup issue.
Describe alternatives you've considered
No response
Additional context
No response

We are now recording all logs for Dashboards plugins as a part of #1274


Feature request: Improve performance by SIMD

Maybe it would be a way to accelerate serde-rs/json using SIMD¹ like the following C++ project does: simdjson.
[1]: Single Instruction Multiple Data

Closing as a duplicate of #120.


Could you remove /vars in favor of /defaults?

Thank you for this role!
My one issue is that nix_commands is hard to override because it is defined in /vars. Ansible only has a few ways to override vars defined this way: https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_variables.html#understanding-variable-precedence
It would be great if I could override this with var_files or group_vars for example.

Thanks!


Port the program to HIP

Hi,
I tried to port the CUDA program to HIP. On AMD GPUs, the warpSize is 64.  Could you please point out the code changes required for your large codebase ?
For example, I found the code
template <int STACK_SIZE>
__global__ void getCutTruthTableConsecutive(const int * pFanin0, const int * pFanin1, const int * vNumSaved,
                                            const int * vIndices, const int * vCuts, const int * vCutRanges,
                                            unsigned * vTruth, const int * vTruthRanges, const unsigned * vTruthElem,
                                            int nIndices, int nPIs, int nMaxCutSize, int * vNode2ConeResynIdx = NULL) {
    typedef cub::WarpScan<int> WarpScan;
    __shared__ typename WarpScan::TempStorage temp_storage[THREAD_PER_BLOCK / 32];
    __shared__ unsigned * vTruthMemAlloc[THREAD_PER_BLOCK / 32];

    int nThreads = NUM_BLOCKS(nIndices, 32) * 32;
    int idx = blockIdx.x * blockDim.x + threadIdx.x;
    int warpIdx = threadIdx.x / 32, laneIdx = threadIdx.x % 32;
    int stack[STACK_SIZE], stackRes[STACK_SIZE], visited[STACK_SIZE];

  assert(nIndices <= nThreads && nThreads - nIndices < 32);

Is it right that all "32" values should be replace with 64 ?
Thanks

For the case you have shown, you can replace 32 with 64.
We do not use warp-level parallelism very often in this project, so it is possible that the case you have shown is the only one. If you have further encountered warp-level code snippets that you are not sure of, you can publish in this issue and I will take a look.

Okay. I made the changes. However, running the program shows assertion errors. I have no idea of the causes.
./main -c "read ./benchmarks/arithmetic/hyp.aig; resyn2; write hyp_resyn2.aig"
refactor: perform MFFC covering algorithm
Refactor: setting hipLimitStackSize = 65536
Refactor: checked hipLimitStackSize = 65536
Gathered 128 POs
...
...
Level 78, global list len 1149
Level 79, global list len 270
Level 80, global list len 28
Level 81, global list len 0
Total number of cones to be resyned: 51560
Truth table computation time: 0.00 sec
refactor_core.cu:287: void factorFromTruth(const int *, const int *, uint64 *, int *, int *, int *, const unsigned int *, const unsigned int *, const int *, const unsigned int *, int): Device-side assertion `vSubgLens[currRowIdx] > 0' failed.
./alg_factor.cuh:175: int sop::sopFactorTrivialCubeRec(unsigned int, int, int, subgUtil::Subg<SUBG_CAP> *): Device-side assertion `uCube' failed.
./alg_factor.cuh:183: int sop::sopFactorTrivialCubeRec(unsigned int, int, int, subgUtil::Subg<SUBG_CAP> *): Device-side assertion `iLit != -1' failed

If I understand correctly, the error was triggered when you ran the translated HIP code, is that right?
May I know whether you have tried running our original CUDA code on a NVIDIA GPU? I cannot reproduce the error with our hardware.

Yes, it was triggered by the HIP code on an AMD GPU only.  I think your domain knowledge may shed some light on potential causes.

It is difficult to find out what goes wrong by looking at the log only. However, one possible error in factorFromTruth is due to insufficient stack size for recursive device function calls. Although I could see from your log that the stack size was successfully set to 65536 which is sufficient on our NVIDIA GPU, I am not sure whether this is the case on an AMD GPU. Besides, note that the error(s) might also reside in previous kernels, which produce wrong data but do not trigger any assertion until factorFromTruth.


Error of ' No module named 'cyber.proto.unit_test_pb2' ' when trying to get data from cyberRT with pythonAPI

System information

OS Platform and Distribution (e.g., Linux Ubuntu 18.04):18.04
Apollo installed from (source or binary):
Apollo version (3.5, 5.0, 5.5, 6.0):6.0
Output of apollo.sh config if on master branch:

Steps to reproduce the issue:

run listener.py inside docker to get data from cyberRT:

Supporting materials (screenshots, command lines, code/script snippets):

Please run bazel-bin/cyber/python/cyber_py3/examples/listener instead. In Apollo 6.0, all Python libraries/binaries were managed by Bazel also.

Please run bazel-bin/cyber/python/cyber_py3/examples/listener instead. In Apollo 6.0, all Python libraries/binaries were managed by Bazel also.

Thx for your reponse! Do you mean I could run the existing listen.py from the path you indicated in docker?
Actually I have both apollo-6.0 and apollo-5.0 on my computer. And there is no bazel-bin under Apollo-6.0. I can only find following stuffs under apollo-5.0 ducument.
There is no such a listener.py file in this path but only py_listener_cpplint  in similar path.


WIP: docs: #1277 document strict and sensitive option

[x] Add section to documentation like requested in #1277  https://next.router.vuejs.org/guide/essentials/route-matching-syntax.html
[x] Link documentation between new documentation and migration guide from Vue 2 router
[ ] Update examples in documentation to match the correct implementation and configuration in router

Hi @posva
I have two open points that I would need your feedback on:

Is the example with setting strict true on the top level and setting sensitive on a specific route enough or should I add more examples? Or do you prefer a different example?
In the corresponding closed issue it's mentioned that  documentation should also be on the API docs for the RouteRecordRaw - is this needed from your perspective?

I will complete this change once I have your response.
Thanks and regards!

About your questions:

Yes, 2 examples are better
Yes, it should be in the API docs too if it isn't there already

@posva thanks for the quick reply and review then I will review the RouteRecordRaw API docs and extend them if it's not there yet + add another example where I set strict only on a specific route level


Error regenerating results from supplementary material

Many .vec files failed when running the following script to regenerate the results from supplementary material
python3 tools/run_batch.py data/inputs_train+validate.yml

Hello,
You can use run_pipeline.py on the individual file to see what the issue is:
python tools/run_pipeline.py "data/bcloud/LMA test__6.vec" --root . --tmpdir tmp

It seems like the version of pybind11 we used has some bug(?) relating to overload resolution on Python 3.8 and 3.9 (and won't even compile on later versions):
Traceback (most recent call last):
  File "C:\...\SketchConnectivity\tools\run_pipeline.py", line 418, in <module>
    main()
  File "C:\...\SketchConnectivity\tools\run_pipeline.py", line 400, in main
    _s.save_pdf(graph_v7, entry['v7_annotations_conn_all'],
TypeError: save_pdf(): incompatible function arguments. The following argument types are supported:
    1. (graph: sketching::StrokeGraph, path: str, params: _sketching.PlotParams, predictions: List[sketching::ClassifierPrediction] = [], face_colors: numpy.ndarray[numpy.int32[m, 1]] = array([], dtype=int32), highlighted_faces: List[int] = []) -> None
    2. (stroke: sketching::Stroke, path: str, params: _sketching.PlotParams, pred_info: sketching::StrokeSnapInfo = None) -> None
    3. (d: sketching::Drawing, path: str, params: _sketching.PlotParams) -> None

Invoked with: StrokeGraph(
  Vertex 0: { p: (904.11, 541.555),  he: 543 }
  ...
), 'tmp\\LMA test__6_v7_annotations_conn_all.pdf', <_sketching.PlotParams object at 0x00000248D99965B0>; kwargs: predictions=[]

However, it works with Python 3.7.16.

Thank you for the response! I have successfully built the project on my Mac. You're right, I need to update pybind11 when compiling. (Python 3.11 + gurobi11.0.0_macos_universal2.pkg + pybind11 v2.10.1)
The problem seems to be the timeout threshold, maybe my Mac is too slow. It takes almost one hour for some files.


Please make sure to use dist folder and NOT uxp folder.

If I use manisfest inside dist folder it fails due invalid json. Howver if I use uxp folder it loads in UXP but when going to PS I just see a window saying: "are you sure you want to use uxp instead of dist folder?" but I cannot accept or refuse, just close the dialog

Same issue here. The manifest.json file in the dist folder seems like invalid JSON.

Ahh, I think I found the solution:
Download the source from the releases https://github.com/jardicc/alchemist/releases/tag/2.7.0
...not from the zip download on the front page of the repo.
In the releases download, dist/manifest.json is actual JSON, and loading it in UXP seems to actually launch the expected plugin in Photoshop.

I wanted to make repo more performant using LFS... but people are installing repo link files instead plugin itself... so I will probably change it back.

https://docs.github.com/en/repositories/working-with-files/managing-large-files

So I changed setting in this repo and hopefully it should work now same as before.


Question for mariadb

I want to manage mariadb replication by orchestrator.Can support?

version:mariadb10.4.18
When switch ,report error on slave as fallow:
Last_IO_Error: Fatal error: Invalid (empty) username when attempting to connect to the master server. Connection attempt terminated.

I'm told orchestrator works well with MariaDB; just not with multisource replication.

When switch ,report error on slave as fallow:

I do not understamd what it was you were trying to do. Please elaborate as much as you can.

I think the replication account could not be found when switching. In mysql env,the system table is slave_master_info,but mariadb doesn't.

I think the replication account could not be found when switching. In mysql env,the system table is slave_master_info,but mariadb doesn't.

orchestrator print the errer log:
2021-04-02 15:24:40 ERROR Error 1142: SELECT command denied to user<EMAIL_ADDRESS>for table 'slave_master_info'

I'm sorry, this is not a description I can work with. For your convenience, when you create a new issue there's a clear set of instructions: https://github.com/openark/orchestrator/issues/new ; please follow those if you wish to submit a bug.
I'm still not sure what it is you're reporting, but it feels to me like your configuration may be lacking.

Ok,think you very much.

Orchestrator is working fine for us with 10.4 and some 10.1 hosts as well on the replication chains.


Flink component version selection problem

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened

Repeat back to version <1.10 when reopening  When going online or offline
What you expected to happen
change it
How to reproduce
Repeat back to version <1.10 when reopening  When going online or offline
Anything else
No response
Version
3.0.0-beta-1
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

@Amy0104 @songjianet Could you please take a look at this issue?

I will fix it.

It is not reproduced on branch 3.0.0-beta-1-release. Could you provide more details on the operation? @Achilles1996


OnAfterGetAvailabilityFilter2 in the Codeunit 99000845 "Reservation Management" should return a Result

Describe the request
Ther Event OnAfterGetAvailabilityFilter2 should return Result as var.
local procedure GetAvailabilityFilter2(AvailabilityDate: Date; SearchForSupply: Boolean) Result: Text[80]
var
    ReservEntry2: Record "Reservation Entry";
begin
    if SearchForSupply then
        ReservEntry2.SetFilter("Expected Receipt Date", '..%1', AvailabilityDate)
    else
        ReservEntry2.SetFilter("Expected Receipt Date", '>=%1', AvailabilityDate);

    Result := ReservEntry2.GetFilter("Expected Receipt Date");
    OnAfterGetAvailabilityFilter2(ReservEntry2, AvailabilityDate, SearchForSupply, Result);
end;

[IntegrationEvent(false, false)]
local procedure OnAfterGetAvailabilityFilter2(var ReservationEntry: Record "Reservation Entry"; AvailabilityDate: Date; SearchForSupply: Boolean; Result: Text[80])
begin
end;

Additional context
We subscribe to this IntegrationEvent and it is currently not possible to return a different result.
Internal work item: AB#540043

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


Release 0.6.2

#130 says, this package should be updated in PyPI
On the AUR, there is to comments regarding the python 3.10 incompatibility which is fixed by 1e9047bec739dbc9d6ab337fc1a111a8b1090244
What would stop us from bumping this package to the next release?
Then we could ping the repo maintainers to point to this.

who's "we" it's just me.
You need to fix all the code rot. which generally means setting up a lot of
CI/testing configuration.
On Tue, Jun 28, 2022 at 5:21 PM Joel @.***> wrote:

#130 https://github.com/harvimt/quamash/issues/130 says, this package
should be updated in PyPI
On the AUR https://aur.archlinux.org/packages/python-quamash, there is
to comments regarding the python 3.10 incompatibility which is fixed by
1e9047b
https://github.com/harvimt/quamash/commit/1e9047bec739dbc9d6ab337fc1a111a8b1090244
What would stop us from bumping this package to the next release?
Then we could ping the repo maintainers to point to this.
—
Reply to this email directly, view it on GitHub
https://github.com/harvimt/quamash/issues/131, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA5CQVZ2WTYZMNN5TM3N5DVROJIBANCNFSM52D5WB4Q
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Thought with 'we'/'us' as the community.
I mean from the last release and the current state, the only changes that I see is a change in the Readme, and the said fix for python 3.10.
So my idea was to tag this current commit with 0.6.2, and publish this then on the PyPI (I am unfamiliar with how the CD for this typically goes).
After that, the AUR package can be updated, as it gets the package from the PyPI.

I have the password to the PyPI account. I don't understand how you think
this works.
On Wed, Jun 29, 2022 at 12:16 AM Joel @.***> wrote:

Thought with 'we'/'us' as the community.
I mean from the last release and the current state, the only changes that
I see is a change in the Readme, and the said fix for python 3.10.
So my idea was to tag this current commit with 0.6.2, and publish this
then on the PyPI (I am unfamiliar with how the CD for this typically goes).
After that, the AUR package can be updated, as it gets the package from
the PyPI.
—
Reply to this email directly, view it on GitHub
https://github.com/harvimt/quamash/issues/131#issuecomment-1169620682,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA5CQX2KKFW6ZXDG752VDDVRPZ4TANCNFSM52D5WB4Q
.
You are receiving this because you commented.Message ID:
@.***>

Okay maybe I ask differently:
Can you publish the current master as the next version on PyPI?

Not in its present form.
On Wed, Jun 29, 2022 at 9:34 PM Joel @.***> wrote:

Okay maybe I ask differently:
Can you publish the current master as the next version on PyPI?
—
Reply to this email directly, view it on GitHub
https://github.com/harvimt/quamash/issues/131#issuecomment-1170751095,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA5CQTX7ICA74OAZUKGYOTVRUPVVANCNFSM52D5WB4Q
.
You are receiving this because you commented.Message ID:
@.***>


Add schema.imported_elements so we can find those imported elements

Many schemas that use imported schemas for other targeted namespaces allow those other namespace elements to appear within the original targeted namespace.   However, it is not currently possible to find an imported schema type for one of those imported elements without having a list of the imported element names.
Also, it is impossible to distinguish during test whether a value being returned is an elemDecl or a typeDecl when the test names are the same.  Hence the change of the type name for 'shiporder' to be 'shiporderType'.   This allows the test to distinguish whether the element or the type name was returned.

Okay, I corrected the prototype as well as fixed the other prototypes being used with xmlHashScanner.    This got me in a bit of clean-up mode and I couldn't help but also fix/correct the init functions to raise an error if there is a parse error.    Hopefully that doesn't make this too big of a change.   I do have another change for switching some of the simpler accessor methods to use instance variables stacked up behind this for another PR.   Sometimes it is hard to just stop when I'm in clean-up mode...

Note: this is an example of why using instance variables for some things is nice:
Debugging without instance variables:
(byebug) schema_elem
#<LibXML::XML::Schema::Element:0x0000562ceedd4c00>

With instance variables:
(byebug) schema_elem
#<LibXML::XML::Schema::Element:0x000056226531b2c0 @name="manifest", @value=nil, @namespace="http://www.imsproject.org/xsd/imscp_rootv1p1p2", @type=#<LibXML::XML::Schema::Type:0x000056226531ad48 @name="manifestType", @kind=5, @namespace="http://www.imsproject.org/xsd/imscp_rootv1p1p2">>

Note: I'm pretty sure this last commit is the segfault occurring under windows in test_namespace.rb.   When I debugged that test line (test_namespace.rb:41), there is a latent xml error in xmlLastError and is referencing a node that has been freed.   I added the xmlResetLastError() and it no longer has that latent xml error.
Of course, this then begs the question whether there should be more places that call xmlResetLastError().

Note: I added further tests for test_schema.

Added new tests for loading the schema Schema.from_string and Schema.new (from a URI).
Added a new test for an exception being thrown for an invalid schema document (eg, invalid schema elements).
Added an xs:import to the shiporder.xsd that then imports shiporder_import.xsd.
Tweaked tests to expect appropriate behavior for including another (imported) schema. Basically, deal with additional namespaces, elements, and types.

Thanks working on this!


which sdxl base model do you use for training

hi, may I know which sdxl base model do you use for training? sd_xl_base_1.0 or Realistic_Vision_V4.0_noVAE?

sd_xl_base_1.0

sd_xl_base_1.0

got it. thanks for your quick reply :)


Fix Naming convention error

Hmm, bunch of merge commits we don't want.

@spencergibb  I close this PR and resubmit one?（So no bunch of merge commits）

Codecov Report

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

@@             Coverage Diff              @@
##             master    #2845      +/-   ##
============================================
- Coverage     65.16%   65.05%   -0.12%
+ Complexity     1408     1405       -3
============================================
  Files           179      179
  Lines          6692     6673      -19
  Branches        800      797       -3
============================================
- Hits           4361     4341      -20
- Misses         2031     2033       +2
+ Partials        300      299       -1

Impacted Files
Coverage Δ
Complexity Δ

...tflix/ribbon/okhttp/OkHttpRibbonConfiguration.java
80% <ø> (ø)
2 <0> (ø)
:arrow_down:

.../netflix/zuul/filters/post/SendResponseFilter.java
75.65% <0%> (-4.2%)
32% <0%> (-3%)

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 2420963...0d2b3f8. Read the comment docs.

Yes


Add more docstrings

This PR adds a lot of docstrings for functions that didn't have them and add/updates some comments for easier future reading of the code.

Thanks a lot for reviewing this @haesleinhuepf!


Human reads filter method

coverage: 92.821% (+0.007%) from 92.814%
when pulling e23ef693ebcda4cfdde35c214a10d124e1e27ca6 on antgonza:human_reads_filter_method
into b28670d7255d85cd80e8cf88b318428388df3119 on qiita-spots:dev.

coverage: 92.822% (+0.008%) from 92.814%
when pulling d3c9dfd37838689cb43bb15045cccaf11f84c0f1 on antgonza:human_reads_filter_method
into b28670d7255d85cd80e8cf88b318428388df3119 on qiita-spots:dev.


Add custom S3 endpoint CA Certificate option

Note: requires rke-rools with https://github.com/rancher/rke-tools/pull/51
rancher/rancher#19222

LGTM


[dart2js] Add support for goldening JS to test infrastructure

Currently we have a number of ways to write tests that need to verify generated JS, ie regexps, the absent / present checker, etc. However, all of these methods use inline strings of dart code, and the expectations need to be manually managed. We currently have annotation tests, but none of them verify generated Javascript. As a strawperson, imagine something like:
/* member: """
function foo(param) {
  return param & 15;
}"""*/
int foo(int param) {
  return param & 15;
}

Such goldens would greatly improve our test coverage and verify exactly when we do optimizations or not. In addition, they will be easy to regenerate, and we will be able to see goldened results from multiple configurations side by side with the dart code.
The only open question is will such goldens be too noisy? My intuition is that small functions will probably be pretty stable, and since it will be easy to update goldens, the additional test coverage will be worth the hassle of regenerating goldens when trivial changes change the generated JS but not the logic. We can also experiment with wildcard matching to reduce superfluous changes to the goldens.

Whatever you do, just make sure that when a golden-file test fails, the error message displays the exact command needed to regenerate the file correctly. And that script should work on Windows too.
As someone who routinely breaks test assumptions by changing the platform libraries (people test exact stack traces!), if the error message doesn't have that command line, I'll try to commit with the test failing and file an issue for you to fix it. Life is too short to fiddle manually with expectation files.


More aggressive tick checking

Currently, we check for a tick whenever the plugin starts up, detects a jump to a new system or detects a carrier jump (Location, FSDJump, CarrierJump events).  This can lead to problems if you hang around in the same system for a long time, spanning a tick, because the plugin still thinks we're in the previous tick.
What we ought to do is check on a regular timer.
However, to do this we need to solve the problem of clearing state properly (which will also solve #48), because just wiping all state means that the next time the CMDR lands at a station after the tick, there is no system information so the plugin will bork.

Intelligent state clearing would involve:

Zero-ing, but not completely wiping the state for the current system
Zero-ing, but not completely wiping the state for all systems for which the CMDR has a currently active mission
Wiping the state for all other systems.


[JavaDoc]   ConfigurationClientBuilder's connectionString is not throwing IllegalArgumentException

Currently, the connetionString() is only throw NullPointerException but it has other Exception to throw
like IllegalArgumentException.

not any other sdk throw IllegalArgumentException in the connetionString() api.


Auto-Commenting Feature for PR Raised

To enhance our communication and acknowledgment process, we're implementing an auto-commenting feature for specific events within our project repository. This feature will automatically generate comments under the following circumstances:
PR Raised: When a contributor raises a pull request (PR), an auto-comment will be posted to provide acknowledgment and any relevant instructions or feedback regarding the PR.
Message: "[Auto-Comment]: Thank you for submitting your pull request! 🙌 We'll review it as soon as possible. In the meantime, please ensure that your changes align with our CONTRIBUTING.md. If there are any specific instructions or feedback regarding your PR, we'll provide them here. Thanks again for your contribution! 😊
"

Idea Contribution
I have read all the feature request issues.
Explain feature request
The feature request is to implement an automated acknowledgment system for contributors who submit pull requests to our project repository.
Explain your solution
I propose leveraging GitHub Actions to automatically comment on pull requests, acknowledging the contributors and providing relevant feedback or instructions. This solution will streamline our communication process and enhance the contributor experience.
Any alternative approaches/features
Alternatively, we could explore using webhooks to trigger a custom script that handles pull request events and automatically posts comments based on predefined criteria. This approach offers flexibility and can integrate with external services or workflows.

Hello, @jfmartinz
As a contributor to GSSoC'24, I would like to contribute this resource to your already very useful and significant repository. If you gave me this problem to handle.

Assigned to you! :)

Hi @jfmartinz, I am facing some issue with GITHUB_TOKEN, and for that I've contacted the mentor of this repository, he is asking for some admin access.

Hi @jfmartinz, I am facing some issue with GITHUB_TOKEN, and for that I've contacted the mentor of this repository, he is asking for some admin access.

I'll take care of creating the token for you. Once it's ready, you can give me  the instruction on how to set it up in the repository. Ive done this before but I forgot to do it. Your role can then focus on creating the YAML file for the auto comment. If  you have clarification or question dont hesitate, thank you

Okay, I will provide you the instruction to setup the secret token, also I would like to do all the autocommenting issue for you. could you please assigned them to me?

Okay, I will provide you the instruction to setup the secret token, also I would like to do all the autocommenting issue for you. could you please assigned them to me?

Okay, thank you. Sure I will.


[WIP] hive uri qr codes support

What does this PR?
Added support for parsing hive uri based QR codes and decoding the codes into hive transactions.
Currently it only supports two transaction types i-e vote and transfer
It can extended to support other transaction types in future
Issue number
fixes #2688
Screenshots/Video
https://github.com/ecency/ecency-mobile/assets/48380998/8500521e-25e2-4633-a160-522b7fa10d47

@noumantahir PR updated.
https://github.com/ecency/ecency-mobile/assets/48380998/73c3eed6-b311-4fbe-9d6e-a2354d8cdd1d

preview of transaction confirmation for private key based users.

@noumantahir this change is done
https://github.com/ecency/ecency-mobile/pull/2713/commits/d7a7a347fa4c8f3c6f72cbaa9498c1056c909dae
https://github.com/ecency/ecency-mobile/pull/2713/commits/0d22a37d966b51d44ff3704fe9e0c4ac1a12971d


Descriptions for dividing subscription should be generated after related localizations was synced.

What type of PR is this?
bugfix
What this PR does / why we need it:
Descriptions for dividing subscription should be generated after related localizations was synced.
Which issue(s) this PR fixes:
Fixes #688
Special notes for your reviewer:

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

Comparison is base (e2ffa5f) 13.60% compared to head (2b0d8be) 14.09%.
Report is 129 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #772      +/-   ##
==========================================
+ Coverage   13.60%   14.09%   +0.48%
==========================================
  Files          66       79      +13
  Lines        7492     9070    +1578
==========================================
+ Hits         1019     1278     +259
- Misses       6391     7694    +1303
- Partials       82       98      +16

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

After offline discussions with @abstractmj, we've got some clues that may help us find a way out of this dilemma.
This dilemma only exists in dividing scheduling. This is the context for the below content.
The goal is to avoid updating twice, no matter it is due to the replicas or other fields changing. In Clusternet, Manifest, FeedInventory, Subscription, Localization are closely related.

We need to ensure that clusternet-scheduler starts scheduling only if FeedInventory is up to date.
We need to ensure Base objects are enqueued only if the status of Subscription get changed.
We need to ensure Localization objects are up to date before updating Description.
Clusternet generated Localizations DO NOT trigger the updates of Descriptions. The updates of Descriptions could only be triggered by

user-defined Localizations
updates of base objects (including base.spec.feeds, base.spec.finvHash)

Below fields could be added.
finv.spec.feeds[i].feedHash (manifest hash)

sub.status.finvHash
sub.status.feedHashes

base.spec.finvHash


[Android]  0.28.0 weex scroller does not support scrollstart & scrollend

https://weex.incubator.apache.org/zh/docs/components/scroller.html#事件
The document has listed that wxscroller has events : scrollstart & scrollend. But the actual is that it doesnot support.

The demo: http://dotwe.org/vue/63a8d2e2d3e41dd7f1fa994517046586

It worked well on my phone with Weex 0.28.

https://weex.incubator.apache.org/zh/docs/components/scroller.html#事件
The document has listed that wxscroller has events : scrollstart & scrollend. But the actual is that it doesnot support.

The Demo run on Web. And the doc means it does not work in Web.
You should try to run it on IOS/Aos


feature: AOI interface

In general, I also think this is a good start!
I commented on a few minor things but they're mainly code styling and namings things, so it's ultimately up you to decide :)

In general, I also think this is a good start!
I commented on a few minor things but they're mainly code styling and namings things, so it's ultimately up you to decide :)

testing slack integration

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Matt Walsh seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Add files via upload

Added dark-light toggle theme template

Could you please accept my pull request for hacktober 2020?


Font loading doesn't work for me

And in my port i don't get font loading to work. That is, my icons show up as question marks. I have tried adding
imgui_backends.opengl3_destroy_fonts_texture()
imgui_backends.opengl3_create_fonts_texture()

after the calls to imgui.font_atlas_add_font_from_file_ttf which i think should be needed because else the new font texture doesn't get built (not needed in your demo though, as you call these before the very first frame is rendered, and fonts are set up in ImGui_ImplOpenGL3_CreateDeviceObjects() which is called the first frame). So adding those calls didn't help. Guess i am doing something wrong as your demo does work. But what i have now worked with pyimgui, so i am wondering what the difference/my oversight is...
Also, when i try to use the ImFont returned from imgui.font_atlas_add_font_from_file_ttf with imgui.push_font, it asserts, probably because the font isn't loaded? I may be missing something here. Code is around here: https://github.com/dcnieho/glassesValidator/blob/imgui_bundle/src/glassesValidator/GUI/_impl/gui.py#L982

Please inform me about the status when you have time. I will be happy to help :-)

Well I made some test on my side with your code, since I wanted to be sure there is no issue on the library side.
You can find my tests in this zip:
sandbox_fonts.zip
Content:
sandbox_fonts/
├── IconsFontAwesome4.py
├── fonts/                                   # your fonts + fontawesome
│   ├── Karla-Regular.ttf
│   ├── NotoSans-Regular.ttf
│   ├── fontawesome-webfont.ttf
│   ├── materialdesignicons-webfont.7.0.96.ttf
│   └── materialdesignicons-webfont.ttf
├── icons_material_design.py
├── imgui.ini
└── sandbox_glassv_fonts.py  # my test

sandbox_glassv_fonts.py is just an adaptation of the bare imgui example where I copy-customized your code.
Results:

I was able to reproduce your font loading error:

            # MsgBox type icons
            # This line alone leads to IM_ASSERT( font && font->IsLoaded() )   ---   imgui.cpp:7795
            # self.icon_font = \
            #     imgui.font_atlas_add_font_from_file_ttf(imgui.get_io().fonts,str(mdi_path),   size_69,                       glyph_ranges_as_int_list=msgbox_range)

            # However, if you load before karla, then merge mdi, the error message disappears
            # it seems you cannot have a font without basic character set
            self.icon_font = \
                imgui.font_atlas_add_font_from_file_ttf(imgui.get_io().fonts,str(karla_path), size_69, glyph_ranges_as_int_list=karla_range)
            self.icon_font = \
                imgui.font_atlas_add_font_from_file_ttf(imgui.get_io().fonts,str(mdi_path), size_69, font_cfg=mdi_config, glyph_ranges_as_int_list=msgbox_range)

the material design does not display icons on my side. I'd be interested in how you get it to display anything.

Thank you VERY much for looking into this! I will hopefully be able to
study and run this tomorrow, else saturday. I will study it carefully.
Let me already reply: My ultimate aim is to move to hello_imgui, which
should be possible now that you have exposed glfw callback so i can put my
own. That should solve these problems if i understand you correctly?
The code as is worked with pyimgui, also with font reloading with an open
window due to dpi change. Perhaps pyimgui doesn't just cleanly wrap but has
some extra code in their for convenience. I do wonder why it no longer
loads.
For the material design font, icons are far in unicode space. With your
code things do work for me if i provide the right unicode code points in my
input strings, e.g. "󰌠 Python". Or i should say worked for me with
pyimgui, i also get question marks now...

Good news!
I found the reason why the icons would not show. The answer was buried in imgui changelog:
CHANGELOG.txt:

VERSION 1.76 (Released 2020-04-12)

Added optional support for Unicode plane 1-16 (#2538, #2541, #2815) [@cloudwu, @samhocevar]
Compile-time enable with '#define IMGUI_USE_WCHAR32' in imconfig.h.

I was using the default version of ImWChar (16 bits), and your icons go beyond this range. This is now solved.
By the way I did some more changes:
f78e7a4 Correct fonts issues if far unicode planes: define IMGUI_USE_WCHAR32
Where I solve the issues with 32 bits glyphs.
ce50192 Add sandbox fonts
I added the font sandbox to the demos.
04a6fe9 AddFontFromFileTTF patched for python inside imgui
ImFontAtlas.add_font_from_file_ttf() is now available under python (I patched imgui)
(and I removed the free function version)
01d51b8 ADAPT_IMGUI_BUNDLE: add SetIniFilename & SetLogFilename
ImGuio..set_ini_filename() replaces the free function version.

Hi Pascal,
super you managed to figure this out! I was just looking through the
patches a bit (hopefully I can play with them properly tonight, just trying
to build a new pull of the dev branch now in the background. I like the
idea of doing the patches as you do, that keeps the interface clean and
simple for the users of your library. Will you do the same
for font_atlas_get_tex_data_as_rgba32?
More generally, I see that in litgen setup for imgui, you added
the RegexReplacementList. Do you think that can also be used to clean up
that dirty enum hack of imgui for some of the extensions in internal (like
what is now
imgui.internal.SelectableFlagsPrivate_.im_gui_selectable_flags_select_on_click
and
should more ideally be
imgui.internal.SelectableFlagsPrivate_.select_on_click)?
I also noted that you are wrapping the materialdesign font so that glyphs
can be accessed by name instead of some arbitrary unicode codepoint. That
is super!
Cheers,
Dee

Message ID: @.***>

Hi Dee,

super you managed to figure this out! I was just looking through the
patches a bit (hopefully I can play with them properly tonight, just trying
to build a new pull of the dev branch now in the background

Keep me informed about the status once you have more info :-)

I like the idea of doing the patches as you do, that keeps the interface clean and simple for the users of your library.

Yes, it makes the python interface simpler. I think some people at ImGui will cringe when seeing #include <vector> in my patched imgui.h. May be I'll change to ImVector someday.

Will you do the same for font_atlas_get_tex_data_as_rgba32?
This one would require imgui to depend on pybind11/numpy, which is not a good idea. So, no.

I also noted that you are wrapping the materialdesign font so that glyphs
can be accessed by name instead of some arbitrary unicode codepoint. That
is super!

Beware that does not work at the moment for material design, only for font awesome. I guess the font and the python file are out of sync.

More generally, I see that in litgen setup for imgui, you added
the RegexReplacementList. Do you think that can also be used to clean up
that dirty enum hack of imgui for some of the extensions in internal (like
what is now
imgui.internal.SelectableFlagsPrivate_.im_gui_selectable_flags_select_on_click
and
should more ideally be
imgui.internal.SelectableFlagsPrivate_.select_on_click)?

I'll note it in another issue

More generally, I see that in litgen setup for imgui, you added
the RegexReplacementList. Do you think that can also be used to clean up
that dirty enum hack of imgui for some of the extensions in internal (like
what is now
imgui.internal.SelectableFlagsPrivate_.im_gui_selectable_flags_select_on_click
and
should more ideally be
imgui.internal.SelectableFlagsPrivate_.select_on_click)?

Fixed in #40

This is super, font loading and the icons work for me as well now!
No need to change to ImVector, all's good!
Ok on the other points, i'm happy. I'll revisit the better way of
using material font icons once im making the next switch, over to
hello_imgui
On Fri, Dec 9, 2022 at 2:10 PM Pascal Thomet @.***>
wrote:

Hi Dee,
super you managed to figure this out! I was just looking through the
patches a bit (hopefully I can play with them properly tonight, just trying
to build a new pull of the dev branch now in the background
Keep me informed about the status once you have more info :-)
I like the idea of doing the patches as you do, that keeps the interface
clean and simple for the users of your library.
Yes, it makes the python interface simpler. I think some people at ImGui
will cringe when seeing #include  in my patched imgui.h. May be
I'll change to ImVector someday.
Will you do the same for font_atlas_get_tex_data_as_rgba32?
This one would require imgui to depend on pybind11/numpy, which is not a
good idea. So, no.
I also noted that you are wrapping the materialdesign font so that glyphs
can be accessed by name instead of some arbitrary unicode codepoint. That
is super!
Beware that does not work at the moment for material design, only for
font awesome. I guess the font and the python file are out of sync.
More generally, I see that in litgen setup for imgui, you added
the RegexReplacementList. Do you think that can also be used to clean up
that dirty enum hack of imgui for some of the extensions in internal (like
what is now
imgui.internal.SelectableFlagsPrivate_.im_gui_selectable_flags_select_on_click
and
should more ideally be
imgui.internal.SelectableFlagsPrivate_.select_on_click)?
I'll note it in another issue
—
Reply to this email directly, view it on GitHub
https://github.com/pthom/imgui_bundle/issues/35#issuecomment-1344292649,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AANUOGP74NYQLMCRIICTA43WMMVUBANCNFSM6AAAAAASUZ4E6I
.
You are receiving this because you authored the thread.Message ID:
@.***>

Regarding the material design font, this is the one i am using, not the one
from google itself: https://github.com/Templarian/MaterialDesign

Message ID: @.***>

https://raw.githubusercontent.com/Templarian/MaterialDesign/master/meta.json
contains info about all codepoints in the font and associated names

Message ID: @.***>

https://github.com/juliettef/IconFontCppHeaders could help you greatly


Python's virtual environment can't view pip list

Issue Type: Feature Request
(hospital_venv) C:\Users\zhangxiaorui\Desktop\items_set\hospital_venv\Scripts>pip list
Fatal error in launcher:
#python 的虚拟环境不能查看pip list
Extension version: 2019.4.12954
VS Code version: Code 1.33.1 (51b0b28134d51361cf996d2f0a1c698247aeabd8, 2019-04-11T08:27:14.102Z)
OS version: Windows_NT x64 10.0.17763

please speak English

Unfortunately, pip list works fine in the virtual environment I created. So it looks like a issue with your environment.
Either try creating a new environment, or please list the steps to reproduce this issue in english.

Closing this issue as pip list is a python specific command and not something the extension controls.


Search results show reST markup

See, for example, https://docs.readthedocs.org/en/latest/search.html?q=welcome&check_keywords=yes&area=default
This can make the "context" part of the results mostly just a sea of special characters used to make the headers and links and other things.
The global search on readthedocs.org/search doesn't seem to do this, though.

This is actually using the Sphinx search, not Read the Docs -- so it's a bug with Sphinx and not us. This should be raised with the Sphinx devs here: https://github.com/sphinx-doc/sphinx

Facing the same problem with locally built sphinx docs (no matter if using the sphinx-rtd-theme or a custom theme) I came across a related sphinx issue (https://github.com/sphinx-doc/sphinx/issues/1618) and was able to solve this problem by using https://github.com/TimKam/sphinx-pretty-searchresults as suggested over there.


[BUG] rename is equal -> equal_to + follow naming conventions for the std

std has some of the predicates that we cave but in scalar. I think we should name our versions the same way

I do not agree with the change

all our element-wise predicates are homogeneously named is_xxx. and return a logical
our real predicates as all, any etc. do not share this property
std::equal_to is a function object supposed to return a bool (i.e. a real predicate) by :

bool operator()( const T& lhs, const T& rhs ) const;
If we want to have an equal_to to follow standard, its semantic on wide could be
all(is_equal_to(a,b))
because equal_to is a global equality of two variables
However std has also a equal algorithm
template< class InputIt1, class InputIt2 >
constexpr bool equal( InputIt1 first1, InputIt1 last1,
InputIt2 first2 );
this could be an alias for is_equal an also an algorithm for eve

@jtlap - this is a suggestion.
My argument is

I suggest that we rename all of the relevant ones: equal_to, not_equal_to, greater, less, greater_equal, less_equal - this will be following std conventions
I don't quite understand
Well fundamentally operator== should return a bool. Since we are already breaking that, breaking the predicates doesn't seem like much.

I see these functors as predicates for algorithms. In the stl we'd write smth like:
std::sort(f, l, std::greater);

However for eve we'll write:
eve::sort(wide, eve::is_greater);

Ok, but I this case I suggest to have the std names as alias of our names, so eve::sort(wide, eve::is_greater);
and eve::sort(wide, eve::greater); will be equivalent.
example of doing so is is_pow2 and has_single_bit

@jtlap
I prefer as is to 2 different functions doing the same thing.
I don't have a strong enough opinion tbh, I just saw that and figured it was weird.
@jfalcou - can you weigh in, what do you think?

The naming of wide predicate as is_ was the result of a long discussion ages ago for  1/ be homogeneous 2/ not giving the false sens to users that it was indeed the equivalent of the std functor.
I would like if we keep the is_* naming in place. In the old code base we had functor that did all(is_equal) etc in one scoop and they were called compare_equal, compare_less etc.
What we can do is :
1 - having eve::greater maps to the combo of all + the is_*, some can be optimized via top bits btw
2 - having aliases like @jtlap proposed, thing we already have for other functions we had before std standardized them
3 - stay as we are
My preferences in order are 2, 3, 1

I'd won't touch it then - I don't think 2 versions are terribly helpful.
I just assumed this was an oversight, my bad.

No problems :)


Small changes in Contributing.md

Add Additional requirements for OS X users.
Issues was:
➜  crystal git:(master) make spec
PATH=`brew --prefix llvm36`/bin:$PATH LIBRARY_PATH=`brew --prefix crystal`/embedded/lib ./bin/crystal build  -o .build/all_spec spec/all_spec.cr
ld: library not found for -lgmp
...

➜  crystal git:(master) make spec
.build/all_spec
ld: library not found for -lgc
...

Thanks!
Based on this I created this wiki page: https://github.com/manastech/crystal/wiki/All-required-libraries
I also added a link to it in the Contributing guide: https://github.com/manastech/crystal/commit/1d1c67ba1102e99ebcefb7d1aec41e61c3154955


fix docker portable build

📝 Summary
Fixes the Docker portable image build

✅ I have run these commands

[x] make lint
[x] make test-race
[x] go mod tidy

Codecov Report

Merging #282 (ce7a76a) into main (77c33ff) will increase coverage by 1.11%.
The diff coverage is n/a.

:exclamation: Current head ce7a76a differs from pull request most recent head 6269ce6. Consider uploading reports for the commit 6269ce6 to get more accurate results

@@            Coverage Diff             @@
##             main     #282      +/-   ##
==========================================
+ Coverage   83.17%   84.28%   +1.11%
==========================================
  Files           5        5
  Lines         630      630
==========================================
+ Hits          524      531       +7
+ Misses         78       74       -4
+ Partials       28       25       -3

Flag
Coverage Δ

unittests
84.28% <ø> (+1.11%)
:arrow_up:

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

Impacted Files
Coverage Δ

server/service.go
84.46% <0.00%> (+1.90%)
:arrow_up:

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


Prateek

Added Email verification after registration.
Once user clicks on link the user account gets activated

@coding-geek21  I resolved the teacher account problem.
But when the user clicks in login , where should I display the message check your mail to activate your account
According to me it will be better if I redirect the user to the login page and show the message there, Then once the user clicks on mail activtaion link I will forward user to dashboard

Yeah you can display the message in login page itself

@coding-geek21  check now , I have resolved all the issues.
And also applied the changes you asked for.

Currently I can't test how the code is working!!. But the usual procedure should be
Whenever a new user signup , a flash shows up at the top of the same page stating that the user has check email to verify account
Whenever the user clicks on the link , it has to redirected to login page and display a flash message stating that the user account is verified and kindly login
Directly logging the user after verification could be a possible scenario too but it couldn't be considered as a security best practice coz any person only having credentials is only considered authorized to access the account and any other person with access to user mail should not be able to login to this account.

@prateekmohanty63 , as u mentioned in the issue , the smtp creds (and other API secrets) have to be moved to env variables . I would create an issue for it once this was merged!!
@coding-geek21 , review this pr further!!

@prateekmohanty63 , as u mentioned in the issue , the smtp creds (and other API secrets) have to be moved to env variables . I would create an issue for it once this was merged!! @coding-geek21 , review this pr further!!

@yaswanthsaivendra so should i move them to env variables?

Yaa, I m thinking of an optimized soln. We couldn't instruct everyone to create a new smtp account for local setup.
What we could do is to provide demo creds for them while local setup. This we have to do :

make use of django-environ
place the demo creds in a file named .env_template ( as placing .env file in VCS is not a gud idea)
Later we can instruct them to do a copy of this .env_template file to a file named .env while local setup

something like cp .env_template .env in any bash like shell or manual copying.
@prateekmohanty63 , If u think of any better solution lemme know.

@coding-geek21 @yaswanthsaivendra  I have also added the env files and now the credentials are not visible
And all the requirements are also implemented and working
Can you now please merge the pr

I checked the working of the code.. When i sign up as a student it gives me link like this

I think it's the link for teachers verification and when I clicked on this link it's showing the teachers dashboard Instead of showing students dashboard

@prateekmohanty63  Did you check this?

@coding-geek21  when I am putting the urls here it is working

but when i put here , its not working . Can you tell me why is that?

@coding-geek21 check now I have fixed it

@coding-geek21 did you check it out?
For students it forwarding to student dashboard  and for teachers to teacher dashboard

Added Email verification after registration. Once user clicks on link the user account gets activated

@yaswanthsaivendra Can you check that env part?

These are the env variables

I have also made a env.example file , so if anyone uses the code they can define the variables easily

ok fine.. one change make email field as unique

:) okay

@coding-geek21 done

 I have also made a env.example file , so if anyone uses the code they can define the variables easily

Move the EMAIL_HOST to env variable.
Rename the file .env.example to .env_tempalte(as the name suggests its a tempalte for creating .env file)
Place the values for env variables in .env_template(other than ones which are related to email)
@coding-geek21 , If possible register for any smtp mail service like mailgun, mailjet or sendinblue and place those creds in .env_template file

@yaswanthsaivendra  any more changes you want , apart from this?

@yaswanthsaivendra  How can I place the value of env variables into env_template , then what is the point of making an env,
and git ignoring it?

@yaswanthsaivendra any more changes you want , apart from this?
That's all
update the requirements file , if neccessary

@yaswanthsaivendra How can I place the value of env variables into env_template , then what is the point of making an env, and git ignoring it?

@yaswanthsaivendra  can you please explain this?

@yaswanthsaivendra How can I place the value of env variables into env_template , then what is the point of making an env, and git ignoring it?

The creds we are placing in .env_template file are like creds of demo services we are providing for development. we won't be using the same ones for production. If we keep them directly in .env file, when we push the code to any deployment service then they will be added as values for the env variables in our code automatically due to name conventions. To avoid using api keys and secret keys of development in production by mistakenly , we do this!!

@yaswanthsaivendra  so like what value should I assign here, can you please tell me

@yaswanthsaivendra so like what value should I assign here, can you please tell me

For now, place the same values, we were using earlier . We will update them , When it comes to prod.

but what about email name and password , those are my personal credentials
can you give me your organiztion credentials?

Yaa that's way I mentioned @coding-geek21 , for doing this. She will be adding those values before merging your pr. You just keep them empty.

oh ok sure thanks @yaswanthsaivendra I will do it

@yaswanthsaivendra  check now , I have made the suggested changes

looks great!! please be patient , ur pr will be merged soon!!

sure @yaswanthsaivendra  , take your time
And one more request @yaswanthsaivendra  @coding-geek21  , Like if you guys do any project based on django .
Do let me know if I can join you guys ever in the future.
And do ping me if I can help solving any more issues

Looks Perfect merging it!

sure @yaswanthsaivendra , take your time And one more request @yaswanthsaivendra @coding-geek21 , Like if you guys do any project based on django . Do let me know if I can join you guys ever in the future. And do ping me if I can help solving any more issues

sure :)

Yaa that's way I mentioned @coding-geek21 , for doing this. She will be adding those values before merging your pr. You just keep them empty.


Cache charmcraft pack container, skip unstable tests except on schedule

Ported from https://github.com/canonical/mysql-k8s-operator/pull/146

These changes have been addressed on #80. Thanks!


Discrepancy in Reproduced Results (Zuco Dataset)

Hi Lukas,
Thank you for the valuable work and for making the code and datasets publicly available. Your research is very innovative and inspiring!
I recently went through your paper DETRtime and tried to reproduce the results using the code from this repository and the provided Zuco dataset. While I followed the steps as described in the README and the paper, the validation results I obtained were notably different from those reported in the paper.
Hyperparameter setup follows the table 6 in the paper appendix:

Obtained results for zuco:

Below are the f1 scores for each class (0, 1, 2), orange for training, blue for validation.

 Orange for training, blue for validation.

Reported result for zuco in the paper:

I'm reaching out to see if there might be any additional steps, configurations, or updates that I might have missed. I'm eager to understand the potential reasons for this discrepancy. Any insights or suggestions would be highly appreciated.
Thanks.
Yicen

Hi Lukas,
Thank you for the valuable work and for making the code and datasets publicly available. Your research is very innovative and inspiring!
I recently went through your paper DETRtime and tried to reproduce the results using the code from this repository and the provided Zuco dataset. While I followed the steps as described in the README and the paper, the validation results I obtained were notably different from those reported in the paper.
Hyperparameter setup follows the table 6 in the paper appendix:
Obtained results for zuco:

Below are the f1 scores for each class (0, 1, 2), orange for training, blue for validation.

2.  Orange for training, blue for validation.

**Reported result for zuco in the paper:**
I'm reaching out to see if there might be any additional steps, configurations, or updates that I might have missed. I'm eager to understand the potential reasons for this discrepancy. Any insights or suggestions would be highly appreciated.
Thanks. Yicen

Hello,I have meet the same problem with you!

Hi Lukas,
When I was replicating your article using the zuco dataset, I found that all the final prediction boxes were overlapping in one place, and I couldn't reproduce the experimental results as effectively as you did in your paper. May I ask if there are any specific training techniques you can recommend?


Adjust Channel Create Tx serialization

Newest version of Epoch's node implements a new field: delegate_ids in Channel Create Tx structure, this issue is blocked until this field is implemented. Here is a link

@cytadela8 does this overlap with some of the tasks you did create? If not, could you discuss an estimate together?


update to INTERVAL type documentation

This PR updates the INTERVAL type documentation to cover the SQL standard format.
Fixes #559

This change is

HTML version: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/45559a5b73d5da8b27fc9d6066aaeae7e9e4c5ca/interval.html

LGTM

LGTM

Review status: 0 of 1 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


JsonApiSerializer always includes all available includes in the response

It looks like that since version 0.19, for the JsonApiSerializer, all relationship links for available includes are always included in the response even when not requested.
This part seems to have introduced it:
https://github.com/thephpleague/fractal/blob/d4097540089f6e7e740bb07297257ba20e3eef91/src/Serializer/JsonApiSerializer.php#L594-L606
In this example I don't expect the airline to be included in the relationships. The relationships object shouldn't even be returned.
GET /flights HTTP/1.1
{
  "data": [
    {
      "type": "flights",
      "id": "1",
      "attributes": {
        ...
      },
      "links": {
        "self": "api/flights/1"
      },
      "relationships": {
        "airline": {
          "links": {
            "self": "api/flights/1/relationships/airline",
            "related": "api/flights/1/airline"
          }
        }
      }
    }
  ]
}

ruh roh! we will take a look at this and see what went sideways.

This is an intended change, see #331. Are you running into any particular issues?

The problem occurred in combination with this package, related to this issue. It basically throws an error when a relationship doesn't contain any data.
Another thing is that endpoints send unnecessary amounts of data. One of our responses grew in size from 30 KB to 170 KB which seems kinda excessive.
In the end It's not that big of a deal since we can extend the serializer and make sure only relationships that are requested are returned. I just wasn't sure if this was intended, or if it was a mistake. If I would have looked a little better I would've have found the answer myself I guess.

That makes sense. The thinking behind this change was that including the links to relationships would make it clear what relationships are available to request. Definitely extending and replacing is the way to go :+1:


(Add option to) translate  to \mkbibemph instead of \emph

Debug log ID
PBZR687T-refs-euc/6.7.263-7
What happened?
Currently, Better BibTeX translates  tags to \emph rather than \mkbibemph, even when using the BetterBibLaTeX translator. This is inconsistent with some of BetterBibLaTeX's other behavior, for example that BetterBibLaTeX translates matching quotes into \mkbibquote when the csquotes option is set. It also generally seems like a best practice to use the biblatex commands like \mkbibemph rather than plain \emph in citations or bibliography entries, if only because it's considered desirable to use commands that denote a more specific purpose (I think Lamport uses the example of defining a macro \genus to italicize genus names rather than using \textit or \emph). So it would be great if Better Bibtex translated from  to mkbibemph by default, or provided some option to do so.
(This isn't a bug – it's clearly intentional and has no effect on the citations and bibliography entries that biblatex ultimately generates, but I generated a debug log, as requested, using an entry with  tags in its title field.)
I have read the documentation thoroughly and can't find a way to call into the translator, and I don't see any hidden options or scripting possibilities to customize behavior. (If I'm not mistaken, one could do this by writing a postscript, but you would have to do it for every field, which would be very tedious.) That doesn't mean I didn't miss anything, and I'm sorry if I have.
All that said, I'm well aware that converting to \mkbibemph will have no effect whatsoever (well, at least that I know of) on the citations and bibliographies that biblatex will ultimately generate, so it might be that this feature request isn't worth whatever time it would take to implement it. If you feel that way, feel free to close. Thanks for your work on this excellent plugin – it is a joy to use.

A very belated thank you for this! Much appreciated, and sorry I didn't thank you sooner.


[match] Ignore force_for_new_devices for App Store profiles

Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.

Motivation and Context
This pull request implements the change detailed in issue #10103.
I've tested my changes by running fastlane match appstore --force_for_new_devices true --app_identifier "com.coolcompany.foo" and verified both that the App Store provisioning profile is not renewed and that the new warning message is displayed.
If the fastlane maintainers feel that this should be covered by an rspec test, I would appreciate some help in writing one (having no prior experience with rspec) 🙂
Description
This pull request changes the behaviour of Match to ignore force_for_new_devices when running Match for App Store profiles. Before this change, invoking Match for appstore profiles with force_for_new_devices set would always renew the App Store provisioning profiles, even if there were no new devices on the developer portal.
Even if there would have been new devices on the developer portal, renewing the App Store provisioning profile would be unnecessary since they don't contain any device information.
Since the App Store profiles don’t contain any devices, the device_count_different? method would always return true (if there were at least 1 device on the developer portal), resulting in the observed behaviour. This method is no longer invoked for App Store profiles.

The CLA has been signed! 🙂

@ohayon: Sorry to poke you, but do you have any thoughts on what @casz and I discussed in their approval? TL;DR: To avoid the nested conditional in runner.rb we'd need to use UI.user_error! in the verify_block. Is having one less nested conditional worth a breaking change? Neither @casz nor I think so 🙂

@ohayon

I agree that it might not be totally necessary, but I do like that it lets people know not to add no-op params to tools because if something changes down the road we will always have to be aware of that.
That being said, I think this could be moved into a verify_block on the option itself and it can print the same message. 🚀

I don't think it can, as we can't check for other values of other ConfigItems in a verify_block, so this part of the code should be ok to use 👍
As we fill in the values for each config item, and then immediately call the verify block, it means that we can't know if the other value is already provided, so in other tools we also check for this somewhere in the runner code or similar :)


Undefined symbols for architecture arm64

New Issue Checklist
🚫 If this template is not filled out your issue will be closed with no comment. 🚫

[ ] I have looked at the Documentation
[ ] I have read the F.A.Q.
[ ] I have filled out this issue template.

Issue Info
Undefined symbols for architecture arm64:
"nominal type descriptor for SnapKit.Constraint", referenced from:
_symbolic _____y_____G s23_ContiguousArrayStorageC 7SnapKit10ConstraintC in SAlertManager.o
"SnapKit.ConstraintViewDSL.prepareConstraints((SnapKit.ConstraintMaker) -> ()) -> [SnapKit.Constraint]", referenced from:
SEngine.ConstraintArrayDSL.prepareConstraints((SnapKit.ConstraintMaker) -> ()) -> [SnapKit.Constraint] in ConstraintArrayDSL.o
"type metadata accessor for SnapKit.Constraint", referenced from:
SEngine.ConstraintArrayDSL.prepareConstraints((SnapKit.ConstraintMaker) -> ()) -> [SnapKit.Constraint] in ConstraintArrayDSL.o
generic specialization <SnapKit.Constraint> of Swift._ArrayBuffer._getElementSlowPath(Swift.Int) -> Swift.AnyObject in SAlert.o
"protocol witness table for __C.CGSize : SnapKit.ConstraintRelatableTarget in SnapKit", referenced from:
closure #5 (SnapKit.ConstraintMaker) -> () in SEngine.SPopUpgradeAlert.setSubUI() -> () in SPopAlert.o
closure #5 (SnapKit.ConstraintMaker) -> () in SEngine.SPopWXAlert.setSubUI() -> () in SPopAlert.o
closure #1 (SnapKit.ConstraintMaker) -> () in SEngine.STab.resetMenu() -> () in STab.o
closure #1 (SnapKit.ConstraintMaker) -> () in closure #1 () -> () in SEngine.STab.resetSelected() -> () in STab.o
closure #2 (SnapKit.ConstraintMaker) -> () in SEngine.SReloadView.(setupUI in _C385F6BF54429932FC138C069CFBA008)() -> () in SHUD.o
merged closure #4 (SnapKit.ConstraintMaker) -> () in SEngine.SWaitView.(setupUI in _C385F6BF54429932FC138C069CFBA008)() -> () in SHUD.o
partial apply forwarder for closure #1 (SnapKit.ConstraintMaker) -> () in static SEngine.SHUD.(screenInfo in _C385F6BF54429932FC138C069CFBA008)(Swift.String) -> () in SHUD.o
...
"(extension in SnapKit):SnapKit.ConstraintBasicAttributesDSL.left.getter : SnapKit.ConstraintItem", referenced from:
closure #2 (SnapKit.ConstraintMaker) -> () in static SEngine.SHUD.(screenInfo in _C385F6BF54429932FC138C069CFBA008)(Swift.String) -> () in SHUD.o
closure #9 (SnapKit.ConstraintMaker) -> () in SEngine.SDKReceiveAlert.setupUI() -> () in SDKReceiveAlert.o
"(extension in SnapKit):SnapKit.ConstraintBasicAttributesDSL.top.getter : SnapKit.ConstraintItem", referenced from:
closure #5 (SnapKit.ConstraintMaker) -> () in SEngine.SPopAlert.setupUI() -> () in SPopAlert.o
closure #2 (SnapKit.ConstraintMaker) -> () in static SEngine.SHUD.(screenInfo in _C385F6BF54429932FC138C069CFBA008)(Swift.String) -> () in SHUD.o
closure #7 (SnapKit.ConstraintMaker) -> () in SEngine.SH5Alert.setupUI() -> () in SH5Alert.o
"static SnapKit.ConstraintPriority.low.getter : SnapKit.ConstraintPriority", referenced from:
closure #3 (SnapKit.ConstraintMaker) -> () in SEngine.SReloadView.(setupUI in _C385F6BF54429932FC138C069CFBA008)() -> () in SHUD.o
"static SnapKit.ConstraintPriority.high.getter : SnapKit.ConstraintPriority", referenced from:
closure #2 (SnapKit.ConstraintMaker) -> () in SEngine.SReloadView.(setupUI in _C385F6BF54429932FC138C069CFBA008)() -> () in SHUD.o
"(extension in SnapKit):SnapKit.ConstraintBasicAttributesDSL.bottom.getter : SnapKit.ConstraintItem", referenced from:
closure #2 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #3 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #4 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #6 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #7 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #8 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #3 (SnapKit.ConstraintMaker) -> () in SEngine.SImageAlert.setupUI() -> () in SPopAlert.o
...
"(extension in SnapKit):SnapKit.ConstraintBasicAttributesDSL.centerX.getter : SnapKit.ConstraintItem", referenced from:
closure #1 (SnapKit.ConstraintMaker) -> () in SEngine.STab.resetMenu() -> () in STab.o
closure #1 (SnapKit.ConstraintMaker) -> () in closure #1 () -> () in SEngine.STab.resetSelected() -> () in STab.o
"protocol witness table for Swift.Int : SnapKit.ConstraintOffsetTarget in SnapKit", referenced from:
closure #2 (SnapKit.ConstraintMaker) -> () in SEngine.SNavWithSubTitle.init(frame: __C.CGRect) -> SEngine.SNavWithSubTitle in SNavBar.o
closure #1 (SnapKit.ConstraintMaker) -> () in SEngine.SCoinAlert.setupUI() -> () in SCoinAlert.o
"protocol witness table for __C.UIView : SnapKit.ConstraintRelatableTarget in SnapKit", referenced from:
closure #4 (SnapKit.ConstraintMaker) -> () in SEngine.SPopEvaluateAlert.setSubUI() -> () in SPopAlert.o
closure #5 (SnapKit.ConstraintMaker) -> () in SEngine.SPopEvaluateAlert.setSubUI() -> () in SPopAlert.o
closure #3 (SnapKit.ConstraintMaker) -> () in SEngine.SPopContentAlert.setSubUI() -> () in SPopAlert.o
closure #4 (SnapKit.ConstraintMaker) -> () in SEngine.SPopContentAlert.setSubUI() -> () in SPopAlert.o
closure #5 (SnapKit.ConstraintMaker) -> () in SEngine.SPopNotificationAlert.setSubUI() -> () in SPopAlert.o
closure #6 (SnapKit.ConstraintMaker) -> () in SEngine.SPopNotificationAlert.setSubUI() -> () in SPopAlert.o
closure #6 (SnapKit.ConstraintMaker) -> () in SEngine.SPopUpgradeAlert.setSubUI() -> () in SPopAlert.o
...
"protocol witness table for CoreGraphics.CGFloat : SnapKit.ConstraintOffsetTarget in SnapKit", referenced from:
closure #2 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #3 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #4 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #3 (SnapKit.ConstraintMaker) -> () in SEngine.SImageAlert.setupUI() -> () in SPopAlert.o
closure #1 (SnapKit.ConstraintMaker) -> () in SEngine.SPopAlert.setupUI() -> () in SPopAlert.o
closure #3 (SnapKit.ConstraintMaker) -> () in SEngine.SPopAlert.setupUI() -> () in SPopAlert.o
closure #5 (SnapKit.ConstraintMaker) -> () in SEngine.SPopAlert.setupUI() -> () in SPopAlert.o
...
"SnapKit.ConstraintViewDSL.updateConstraints((SnapKit.ConstraintMaker) -> ()) -> ()", referenced from:
(extension in SEngine):Swift.Array.snp_updateConstraints((SnapKit.ConstraintMaker) -> ()) -> () in ConstraintArray+Extensions.o
SEngine.ConstraintArrayDSL.updateConstraints((SnapKit.ConstraintMaker) -> ()) -> () in ConstraintArrayDSL.o
"protocol witness table for Swift.Double : SnapKit.ConstraintRelatableTarget in SnapKit", referenced from:
closure #5 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #7 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #1 (SnapKit.ConstraintMaker) -> () in closure #1 () -> __C.UIView in SEngine.SNavBar.barView.getter : __C.UIView in SNavBar.o
closure #4 (SnapKit.ConstraintMaker) -> () in SEngine.SAlert.layout() -> () in SAlert.o
closure #6 (SnapKit.ConstraintMaker) -> () in SEngine.SAlert.layout() -> () in SAlert.o
closure #6 (SnapKit.ConstraintMaker) -> () in SEngine.SFivePlateView.setupUI() -> () in SFivePlateView.o
"protocol witness table for SnapKit.ConstraintViewDSL : SnapKit.ConstraintBasicAttributesDSL in SnapKit", referenced from:
closure #2 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #3 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #4 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #6 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #7 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #8 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #3 (SnapKit.ConstraintMaker) -> () in SEngine.SImageAlert.setupUI() -> () in SPopAlert.o
...
"type metadata for SnapKit.ConstraintViewDSL", referenced from:
closure #2 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #3 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #4 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #6 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #7 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #8 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #3 (SnapKit.ConstraintMaker) -> () in SEngine.SImageAlert.setupUI() -> () in SPopAlert.o
...
"SnapKit.ConstraintViewDSL.makeConstraints((SnapKit.ConstraintMaker) -> ()) -> ()", referenced from:
SEngine.SInputAlert.layout() -> () in SInputAlert.o
(extension in SEngine):Swift.Array.snp_makeConstraints((SnapKit.ConstraintMaker) -> ()) -> () in ConstraintArray+Extensions.o
SEngine.SImageAlert.setupUI() -> () in SPopAlert.o
closure #1 () -> __C.UIView in SEngine.SPopAlert.close.getter : __C.UIView in SPopAlert.o
SEngine.SPopAlert.setupUI() -> () in SPopAlert.o
SEngine.SPopEvaluateAlert.setSubUI() -> () in SPopAlert.o
SEngine.SPopContentAlert.setSubUI() -> () in SPopAlert.o
...
"(extension in SnapKit):SnapKit.ConstraintBasicAttributesDSL.right.getter : SnapKit.ConstraintItem", referenced from:
closure #2 (SnapKit.ConstraintMaker) -> () in static SEngine.SHUD.(screenInfo in _C385F6BF54429932FC138C069CFBA008)(Swift.String) -> () in SHUD.o
closure #1 (SnapKit.ConstraintMaker) -> () in SEngine.ConstraintArrayDSL.distributeViewsAlong(axisType: __C.UILayoutConstraintAxis, fixedSpacing: CoreGraphics.CGFloat, leadSpacing: CoreGraphics.CGFloat, tailSpacing: CoreGraphics.CGFloat) -> () in ConstraintArrayDSL.o
closure #1 (SnapKit.ConstraintMaker) -> () in SEngine.ConstraintArrayDSL.distributeSudokuViews(fixedLineSpacing: CoreGraphics.CGFloat, fixedInteritemSpacing: CoreGraphics.CGFloat, warpCount: Swift.Int, edgeInset: __C.UIEdgeInsets) -> () in ConstraintArrayDSL.o
closure #7 (SnapKit.ConstraintMaker) -> () in SEngine.SDKReceiveAlert.setupUI() -> () in SDKReceiveAlert.o
closure #10 (SnapKit.ConstraintMaker) -> () in SEngine.SDKReceiveAlert.setupUI() -> () in SDKReceiveAlert.o
closure #13 (SnapKit.ConstraintMaker) -> () in SEngine.SDKReceiveAlert.setupUI() -> () in SDKReceiveAlert.o
closure #14 (SnapKit.ConstraintMaker) -> () in SEngine.SDKReceiveAlert.setupUI() -> () in SDKReceiveAlert.o
...
"type metadata accessor for SnapKit.ConstraintItem", referenced from:
closure #2 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #3 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #4 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #6 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #7 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #8 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #3 (SnapKit.ConstraintMaker) -> () in SEngine.SImageAlert.setupUI() -> () in SPopAlert.o
...
"protocol witness table for SnapKit.ConstraintItem : SnapKit.ConstraintRelatableTarget in SnapKit", referenced from:
closure #2 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #3 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #4 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #6 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #7 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #8 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #3 (SnapKit.ConstraintMaker) -> () in SEngine.SImageAlert.setupUI() -> () in SPopAlert.o
...
"SnapKit.ConstraintViewDSL.remakeConstraints((SnapKit.ConstraintMaker) -> ()) -> ()", referenced from:
SEngine.SInputAlert.layout() -> () in SInputAlert.o
(extension in SEngine):Swift.Array.snp_remakeConstraints((SnapKit.ConstraintMaker) -> ()) -> () in ConstraintArray+Extensions.o
closure #1 () -> () in SEngine.STab.resetSelected() -> () in STab.o
SEngine.ConstraintArrayDSL.remakeConstraints((SnapKit.ConstraintMaker) -> ()) -> () in ConstraintArrayDSL.o
SEngine.SAlert.layout() -> () in SAlert.o
"SnapKit.ConstraintViewDSL.removeConstraints() -> ()", referenced from:
(extension in SEngine):Swift.Array.snp_removeConstraints() -> () in ConstraintArray+Extensions.o
SEngine.ConstraintArrayDSL.removeConstraints() -> () in ConstraintArrayDSL.o
"protocol witness table for CoreGraphics.CGFloat : SnapKit.ConstraintRelatableTarget in SnapKit", referenced from:
closure #1 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #2 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #3 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #4 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #5 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #6 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #8 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
...
"(extension in SnapKit):__C.UIView.snp.getter : SnapKit.ConstraintViewDSL", referenced from:
SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #2 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #3 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #4 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #6 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #7 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #8 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
...
"protocol witness table for CoreGraphics.CGFloat : SnapKit.ConstraintMultiplierTarget in SnapKit", referenced from:
closure #1 (SnapKit.ConstraintMaker) -> () in SEngine.ConstraintArrayDSL.distributeViewsAlong(axisType: __C.UILayoutConstraintAxis, fixedItemLength: CoreGraphics.CGFloat, leadSpacing: CoreGraphics.CGFloat, tailSpacing: CoreGraphics.CGFloat) -> () in ConstraintArrayDSL.o
closure #2 (SnapKit.ConstraintMaker) -> () in SEngine.ConstraintArrayDSL.distributeViewsAlong(axisType: __C.UILayoutConstraintAxis, fixedItemLength: CoreGraphics.CGFloat, leadSpacing: CoreGraphics.CGFloat, tailSpacing: CoreGraphics.CGFloat) -> () in ConstraintArrayDSL.o
closure #1 (SnapKit.ConstraintMaker) -> () in SEngine.ConstraintArrayDSL.distributeSudokuViews(fixedItemWidth: CoreGraphics.CGFloat, fixedItemHeight: CoreGraphics.CGFloat, warpCount: Swift.Int, edgeInset: __C.UIEdgeInsets) -> () in ConstraintArrayDSL.o
"protocol witness table for Swift.Int : SnapKit.ConstraintRelatableTarget in SnapKit", referenced from:
closure #2 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #5 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #6 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #7 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #8 (SnapKit.ConstraintMaker) -> () in SEngine.SInputAlert.layout() -> () in SInputAlert.o
closure #2 (SnapKit.ConstraintMaker) -> () in SEngine.SImageAlert.setupUI() -> () in SPopAlert.o
closure #2 (SnapKit.ConstraintMaker) -> () in SEngine.SPopEvaluateAlert.setSubUI() -> () in SPopAlert.o
...
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Info
Value

Platform
e.g. ios/osx/tvos

Platform Version
e.g. 10.0

SnapKit Version
e.g. 5.0.1

Integration Method
e.g. carthage/cocoapods/manually

Issue Description
⚠ Replace this with the description of your issue. ⚠

I've tried a few ways to solve the problem

Remove DerivedData,pod install does not work
2.Add arm64 to "exclamated Architectures" that solve the problem of unable to find the compiled files

pods的原因

pods的原因

你好，请问可以详细说明一下吗？我也遇到了这个问题，谢谢

你好 有解决方案吗


Add a "notifications bar" for messages

We can also make the game more interactive by giving a notification to the player from Diddi (who modified the spaceship, as in your story), that the player has unlocked a secret function of the ship....
Originally posted by @HarshNarayanJha in https://github.com/DiddiLeija/diddi-and-the-bugs/issues/13#issuecomment-1019032635

If we want to do this, it will be after cutting a release to save our latest modifications.

I already have an idea to do this. I'll post a PR soon. By now, I self-assign this issue.

Uh, well... this is what I have now:

There's a bar below the game. It is still present when you loose, win, pause or restart. Now I have to move the messages part.

Here are a few messages:

And some others. I currently have these messages:

Game start (initialization)
Pause / Resume
Restart
Continous bullets
Win / Loose

Should we notify something else?

Great... Is this system stable now?, if it is push the changes then we will think about other notifications and/or message improvements.

I actually added some secret messages (available via an undocumented M key) at #38. You can add messages to it, or generate messages on other events.