Convert serial number to string on RetrieveVASP

Scope of changes
In the admin ui the serial number for a VASP's identity certificate is currently displayed in the base64 encoding. In order to be more useful, this PR changes the return value on RetrieveVASP so that it returns the serial number as a capital hex encoded string in the JSON, matching the format that Sectigo displays.
SC-5793
Type of change

[ ] bug fix
[x] new feature
[ ] documentation
[ ] other (describe)

Acceptance criteria
In the admin ui the serial numbers should now be displayed in capital hex encoding, e.g., something like DFD0460B63FA147F6E671CF45AF6369E.
Author checklist

[x] I have manually tested the change and/or added automation in the form of unit tests or integration tests
[ ]  I have updated the dependencies list
[ ]  I have recompiled and included new protocol buffers to reflect changes I made
[x]  I have added new test fixtures as needed to support added tests
[x]   Check this box if a reviewer can merge this pull request after approval (leave it unchecked if you want to do it yourself)
[x]  I have moved the associated Shortcut story to "Ready for Review"

Reviewer(s) checklist

[ ] The serial number modification does not have any external side effects.
[ ] TestRetrieveVASP is sufficient for verifying that the serial number was changed correctly.

Codecov Report

Merging #636 (ea30fd5) into main (a859adc) will decrease coverage by 7.90%.
The diff coverage is n/a.

:exclamation: Current head ea30fd5 differs from pull request most recent head 507d76e. Consider uploading reports for the commit 507d76e to get more accurate results

@@            Coverage Diff             @@
##             main     #636      +/-   ##
==========================================
- Coverage   46.00%   38.10%   -7.91%
==========================================
  Files         550      155     -395
  Lines       16162     2433   -13729
  Branches     1201      615     -586
==========================================
- Hits         7435      927    -6508
+ Misses       7597     1330    -6267
+ Partials     1130      176     -954

Impacted Files
Coverage Δ

...user-ui/src/components/Membres/Members.stories.tsx

...r-ui/src/components/Section/IntegrateAndComply.tsx

web/gds-user-ui/src/hooks/useQuery.ts

web/gds-user-ui/src/utils/address-utils.tsx

...ds-user-ui/src/components/Icon/TrisaNetworkSvg.tsx

...hub.com/trisacrypto/directory/pkg/sectigo/creds.go

.../YourImplementation/YourImplementation.stories.tsx

...s-user-ui/src/components/ui/ErrorMessage/index.tsx

...s-user-ui/src/constants/national-identification.ts

...er-ui/src/components/StatCard/StatCard.stories.tsx

... and 385 more

Continue to review full report at Codecov.

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


EDU-1379 Fix shape change not persisted

Closes https://educandu.atlassian.net/browse/EDU-1379

Aaaahhhhh :monocle_face:


Identity Management component

This issue can be divided into sub-issues for smaller components

Closing this for smaller more specific issues


Fix issues in registration due to missing environment

We were never setting the environment in init.
Another tragic only possible in objc bug.
This adds a test to ensure that analytics fire when we register, which
will also only work if the env is setup.

PR Cover Letter

[ ] A detailed description of the changes in the body of the PR
[ ] If available, a link to the relevant JIRA ticket in the body of the PR

[PROJ-XXXX](https://openedx.atlassian.net/browse/PROJ-XXXX)

Sandbox

[ ] Build a sandbox for your branch and add a link here

Testing

[ ] i18n
[ ] RTL
[ ] Unit, integration, acceptance tests as appropriate
[ ] Analytics
[ ] Performance
[ ] Database migrations are backwards-compatible

Reviewers
If you've been tagged for review, please check your corresponding box once you've given the :+1:.

[ ] Code review #1
[ ] Code review #2
[ ] UI strings/error msgs review
[ ] UX review
[ ] Accessibility review
[ ] Product review

DevOps assistance
If it's needed, or even if you suspect it might be needed, do any/all these things as early as possible. Don't surprise devops right before merging! For example, touching envs/aws.py or or envs/common.py are dead giveaways that you'll need assistance when pushing your changes out. Things that require devops attention include, but are not limited to:

configuration changes
feature flags
migrations
Ways to get devops attention, pick-and-choose whichever is most appropriate for your specific PR:
[ ] Tag devops on your PR (@edx/devops), either for review (more specific to devops = better) or just a general FYI
[ ] File a support ticket

FYI: Tag anyone who might be interested in this PR here.
Post-review

[ ] Squash commits

@mikekatz please review

:+1:

Current coverage is 45.83%

Merging #660 into master will increase coverage by +0.74% as of d970df7

@@            master    #660   diff @@
======================================
  Files          417     418     +1
  Stmts        30900   30919    +19
  Branches         0       0
  Methods
======================================
+ Hit          13934   14172   +238
  Partial          0       0
+ Missed       16966   16747   -219

Review entire Coverage Diff as of d970df7

Uncovered Suggestions

+0.52% via ...deosViewController.m#1265...1424
+0.50% via ...ideoPlayerControls.m#1416...1568
+0.46% via ...tionViewController.m#986...1127
See 7 more...

Powered by Codecov. Updated on successful CI builds.


Read book not looking attractive

Reproduction steps
In the front section the read book is not looking attractive

Expected behavior
It should look better as it is on the main page
Actual Behavior
I can change its appearance so that it looks better.Can you assign this issue to me?
👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Please assign me this issue under GSSOC'23.

@rohanbabbar04 Can you assign this task to me?


Fix excludes being ignored when using available-at

This commit fixes a regression introduced by a bugfix
about available-at (see 4be5952141fc64f0f1f754807730b1b18bfb32b5).
Basically the problem is that if an exclude from an incoming edge
is supposed to exclude the target of an available-at variant, then
the exclusion would be ignored. In fact, instead of allowing all
dependencies like we did in the previous fix, we should only allow
non excluded variants, which corresponds to the union of the
"transitive exclusions" of all the incoming edges to a node.

@bot-gradle test this

OK, I've already triggered ReadyForMerge build for you.

@bot-gradle test this

OK, I've already cancelled the old build and triggered a new ReadyForMerge build for you.


How do i use userManager helper methods?

like User.IsInRole("Admin") is there any of those methods work?

Hi,
HttpContext.Current.User.IsInRole("admin") comes from the HttpContext and the user claims. So it should be working fine, nothing to do with MongoDB implementation.


Add github name and link

The following took place in this PR:

I added my github username
I added my github link

@techEmprez , thanks for your PR and contribution!
Don't forget to follow me or this organization to staytuned to upcoming updates to this project :)
Take care, and have a good day ahead 😄


Update Firebase pod to lock subspecs to minor versions instead of patch versions

We're planning to make this change in Firebase 6 to change its subspec dependencies to be allow patches without a Firebase pod rev for at least the open source libraries.

Done internally in cl/241938501 and will be available with 6.0.0


map seems unaware of size change after switching view

After clicking the Switch View button and the view is reoriented (horizontally/vertically), the map contains an area that is empty, and zooming to full extent no longer works correctly (i.e., the map behaves as if its size has not changed).  Determine how to make the map aware of the size change and behave accordingly.
(Note that even though this is entered as a bug, it is expected that view switching will not happen very often, so this may be considered a relatively low priority.)

Resolved with commit 211d333560d98c33ba7fd37dcea621f4d8a1551b.


Values file not adding ports

The generated values file is no longer adding the ports from the docker-compose.yaml file.

Fixed in release 1.3


Question: Status of 7.2?

The README.md says that 8.x is beta and 7.1 is stable. What is the status of 7.2?

It should be good, but it has had some big changes to support high DPI monitors. I thought that would be a simple thing when I started on it, but fairly soon discovered that it wasn't. Once I discovered that I then intended to go for a simpler option in 7.x than the full per-monitor support I added in 8.x, but that wasn't practical. Obviously all the tests pass, but there is a lot that isn't covered so apps and individual use cases may be broken. So over to you: Does it work for Jadeite?

I'm able to build and run Jade on 7.2 without any issues so far, so I'll use that going forward. Thanks!


Generation of new descriptor_elabbook files

This issue is a one of the 3 steps of V4A pipeline that should include.
Idea is to generate the descriptor_elabbook.csv file based on the the full_elabbook.csv file.
Function : conversion_to_odml_table_descriptor(full_elabbook_csv, session_number)

Args :
     full_elabbook_csv
     session_number

Return : descriptor_elabbook_csv

This function will take the full_elabbook_csv file to make all of the descriptor_elabbook file that we need to create BIDS structure.

ok, this looks good to me! what's missing is the specification of whether this function is designed to handle one or several sessions.... the most simple is to write this function for one session, and therefore a session_id should be added as an input...
(and then, the snakemake part can call this function, and loop over all sessions for which the descriptor needs to be generated)
WDYT @killianrochet @JuliaSprenger ?

Hi @killianrochet Can you use odmltables instead of odml_table, as this is the name of the piece of software that does the conversion csv -> odml?


Change CICD to run clippy on all tests

TODO

[x] Use cargo fmt
[ ] Add necessary tests
[ ] Add changelog entry
[ ] Update default config/theme in README (if applicable)
[ ] Update man page at lsd/doc/lsd.md (if applicable)

Codecov Report

Merging #710 (4d9f9d0) into master (425e515) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #710   +/-   ##
=======================================
  Coverage   88.36%   88.36%
=======================================
  Files          41       41
  Lines        4546     4546
=======================================
  Hits         4017     4017
  Misses        529      529

Impacted Files
Coverage Δ

src/config_file.rs
70.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us.


run arrow-datafusion/datafusion/sql failed

at the arrow-datafusion/datafusion/sql directory, and run cargo build .
Following error report:
➜ cargo build
   Compiling arrow-array v43.0.0
   Compiling comfy-table v7.0.1
   Compiling bstr v0.2.17
   Compiling regex v1.9.0
   Compiling serde_json v1.0.85
   Compiling flatbuffers v23.5.26
   Compiling strum_macros v0.25.1
   Compiling log v0.4.17
error[E0432]: unresolved import `num::complex::ComplexFloat`
  --> /Users/edison/.cargo/registry/src/index.crates.io-6f17d22bba15001f/arrow-array-43.0.0/src/arithmetic.rs:21:5
   |
21 | use num::complex::ComplexFloat;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^ no `ComplexFloat` in `complex`

   Compiling sqlparser v0.35.0
   Compiling csv v1.1.6
error[E0599]: no method named `powi` found for struct `f16` in the current scope
   --> /Users/edison/.cargo/registry/src/index.crates.io-6f17d22bba15001f/arrow-array-43.0.0/src/arithmetic.rs:351:25
    |
351 |                 Ok(self.powi(exp as i32))
    |                         ^^^^ method not found in `f16`
...
380 | native_type_float_op!(f16, f16::ZERO, f16::ONE);
    | ----------------------------------------------- in this macro invocation
    |
    = help: items from traits can only be used if the trait is in scope
    = note: this error originates in the macro `native_type_float_op` (in Nightly builds, run with -Z macro-backtrace for more info)
help: the following traits are implemented but not in scope; perhaps add a `use` for one of them:
    |
18  + use num::Float;
    |
18  + use num::traits::float::FloatCore;
    |
18  + use num::traits::real::Real;
    |

error[E0599]: no method named `powi` found for struct `f16` in the current scope
   --> /Users/edison/.cargo/registry/src/index.crates.io-6f17d22bba15001f/arrow-array-43.0.0/src/arithmetic.rs:356:22
    |
356 |                 self.powi(exp as i32)
    |                      ^^^^ method not found in `f16`
...
380 | native_type_float_op!(f16, f16::ZERO, f16::ONE);
    | ----------------------------------------------- in this macro invocation
    |
    = help: items from traits can only be used if the trait is in scope
    = note: this error originates in the macro `native_type_float_op` (in Nightly builds, run with -Z macro-backtrace for more info)
help: the following traits are implemented but not in scope; perhaps add a `use` for one of them:
    |
18  + use num::Float;
    |
18  + use num::traits::float::FloatCore;
    |
18  + use num::traits::real::Real;
    |

Some errors have detailed explanations: E0432, E0599.
For more information about an error, try `rustc --explain E0432`.
error: could not compile `arrow-array` (lib) due to 3 previous errors
warning: build failed, waiting for other jobs to finish...

➜ cargo --version
cargo 1.70.0 (ec8a8a0ca 2023-04-25)

➜ rustc --version
rustc 1.70.0 (90c541806 2023-05-31)

I wonder if it works if you do cargo update?

(datafusion might need to have its declared version of num updated)

I wonder if it works if you do cargo update?

Yes, it's fixed after cargo update, thanks for your help, I will close this issue.


Dev test: States of Matter 1.2.0-dev.4

@KatieWoe and @arouinfar - States of Matter 1.2.0-dev.4 is ready for dev testing. This is being done in preparation for releasing the phet-io version of States of Matter Basics to a customer, hopefully within the next couple of weeks.  Testing the non-basics version should help to vet all changes that have been made in the process of adding phet-io to this sim. Please document issues in https://github.com/phetsims/states-of-matter/issues and link to this issue.
A lot of changes were made to the code over the course of adding PhET-iO support, so this testing is intended to make sure that no problems were introduced to the primary (i.e. non-PhET-iO) functionality and that the basic PhET-iO functionality works.  The structure and naming of the tandems are being reviewed by others, no need to do that as part of this testing.
Assigning @ariel-phet for prioritization.

General Dev Test

What to Test

Click every single button.
If there is sound, make sure it works.
Make sure you can't lose anything.
Play with the sim normally.
Try to break the sim.
Try to include browser version numbers
If there is a console available, check for errors and include them in the Problem Description.
Wrung through the string tests on at least one platform, especially if it is about to go to rc.

Focus and Special Instructions
This is intended to be release as a dev version to a customer who has plans to integrate it into a learning environment where they take advantage of PhET-iO features.  Because the addition of PhET-iO support has caused a lot of code to change, there will need to be a thorough regression test of the basic functionality on all platforms as well as testing of PhET-iO functionality.  Since we have made previous releases of PhET-iO-enabled simulations to this customer, those previous test tasks may also provide guidance.

General Dev Test Platforms

[ ] Latest macOS, Chrome and Safari
[ ] Latest iOS, Safari
[ ] Windows 10, all browsers
[ ] Latest Chrome OS, Chrome

Link(s)

Simulation

PhET-iO Dev Test

What to Test

Make sure that public files do not have password protection. Use a private browser for this.
Make sure that private files do have password protection. Use a private browser for this.
Make sure standalone sim is working properly.
Make sure the wrapper index is working properly.
Make sure each wrapper is working properly.
Launch the simulation in Studio with ?stringTest=xss and make sure the sim doesn't navigate to youtube
For newer PhET-iO wrapper indices, save the "basic example of a functional wrapper" as a .html file and open it. Make sure the simulation loads without crashing or throwing errors.

General Dev Test Platforms

[ ] Latest macOS, all browsers
[ ] Latest iOS, Safari
[ ] Windows 10, all browsers, including IE
[ ] Latest Chrome OS, Chrome

Link(s)

Wrapper Index

FAQs for QA Members

There are multiple tests in this issue... Which test should I do first?
Test in order! Test the first thing first, the second thing second, and so on.

How should I format my issue?

We typically assign the developer who opened the issue in the QA repository.

My question isn't in here... What should I do?
You should:

Consult the QA Book.
Google it.
Ask Katie.
Ask a developer.
Google it again.
Cry.

Marking high priority for now since this project is part of fulfilling a customer requirement

@KatieWoe bumping to current top priority

QA is done

Thanks QA team!  I'll close this one and we will tackle the individual issues from here.


Added note about a feature being PostreSQL-applicable only

Summary
Added a note about a feature being PostgreSQL only (i.e. does not apply to Cassandra users).
Reason
Seems this feature is applicable to PostgreSQL only, based on comments in https://github.com/Kong/kong-ee/pull/2839.

We have deprecated Cassandra support in 2.7(ie, no more new features, eventually won't support it at all in 3.x). So starting from that point, shouldn't everything new be assumed to not be supported in Cassandra? We could pretty much say the same thing for all new features in 2.8 - Cassandra-backed? You won't get the new stuff.

I think that's a fair assumption, but we should also explicitly call it out to reduce the number of support questions raised

We have deprecated Cassandra support in 2.7(ie, no more new features, eventually won't support it at all in 3.x). So starting from that point, shouldn't everything new be assumed to not be supported in Cassandra? We could pretty much say the same thing for all new features in 2.8 - Cassandra-backed? You won't get the new stuff.

Agreed, however it raises some support requests while customer's don't quite understand why something isn't working as they expect it to, and seems easy to avoid with a quick note. If we're able to add notes periodically until 3.0 or something, that'd be helpful to both customers and CRE. :-)
For context, this whole thing was discovered because of a customer seeing that filtering / searching broke completely and we narrowed it down to their use of Cassandra. We found the feature in GitHub and it was clear they didn't intend to support Cassandra for it, which is understandable, however by implementing the new feature they inadvertently broke the existing filtering for Cassandra users. I filed an FTI in Jira for that and it's been resolved already by the looks of it: https://konghq.atlassian.net/browse/FTI-3276


Make host name configurable

I'd like to use this module while debugging a memory leak on a non-public, but deployed environment.
Following the node.js spec, you can specify an IP, but this module doesn't provide configurability for that layer.
Is it possible to make this configurable?

Yes, this is possible, although its use will be limited to making heapdumps and cpu profiles on demand (haven't tested this in a remote setting though). The best part (at least, to me) is creating heapdumps on OoM situations. This won't work when the module is not running in the same process.
So, it's possible, but i'm wondering if you actually need this module at all? When exposing the inspector port in your deployed environment, can't you just connect to it with something like Chrome devtools?
Or am I missing the point here?

Closing due to no activity.
Reopen if you have more info.


Update edit command in UserGuide.md

Describe your changes
update user guide with edit
Issue ticket number and link
partially resolves #140
Checklist before requesting a review

[x] I have performed a self-review of my code.
[x] If it is a core feature, I have added thorough tests.

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

This PR will be superseded by my PR due to an incoming UI redesign, try not to merge


How to monitor django deployed by uwsgi+nginx?

I can monitor the project started with the httpserver that comes with django, but when I deploy the project with nginx+uwsgi, I encountered a permission problem, but I don't know how to solve it. The error message is as follows:
*MyMiddleware request
[pinpoint] [52739] [52739]#0 pinpoint_start start
[pinpoint] [52739] [52739]#128 add clue key:appname value:<IP_ADDRESS>-Django-8888
[pinpoint] [52739] [52739]#128 add clue key:appid value:APM-0100280001008888
[pinpoint] [52739] [52739]#128 add clue key:name value:BaseDjangoRequest request
[pinpoint] [52739] [52739]#128 add clue key:uri value:/favicon.ico
[pinpoint] [52739] [52739]#128 add clue key:client value:<IP_ADDRESS>
[pinpoint] [52739] [52739]#128 add clue key:server value:<IP_ADDRESS>
[pinpoint] [52739] [52739]#128 add clue key:stp value:1700
[pinpoint] [52739] [52739]pre_init_shared_object: open address with:Permission denied
uwsgi: /tmp/pip-install-gzeq51ez/pinpointpy_84ec1378330b4d799049fa3092f41d5d/common/src/Cache/SharedObj.c:196: fetch_shared_obj_addr: Assertion `object.region' failed.**
Can anyone help me? thank you very much!

ho, nice catch!
Does it working when use "python manage.py runserver"?

ho, nice catch!
Does it working when use "python manage.py runserver"?

Yes, "python manage.py runserver" is OK!

Grant the access to your uwsgi user to /dev/shm
how to set user ?

Grant the access to your uwsgi user to /dev/shm
how to set user ?

When I changed the permissions of /dev/shm/pinpoint-php.shm(from 640 to 646), uwsgi+nginx was OK.
But pinpoint-web displays ‘’no data’’, but the graphics in REAL TIME has real-time data. It’s so strange. Let me see what the reason is. thank you very much!

Hmm, shared your collector-agent log  to us?

Hmm, shared your collector-agent log to us?

MyMiddleware response*
[pinpoint] [45085] [45085]#128 add clues:46:200
[pinpoint] [45085] [45085]this span:({"E":42,"FT":1700,"S":1609318386403,"appid":"APM-0100280001008888","appname":"<IP_ADDRESS>-Django-8888","calls":[{"E":1,"S":4,"SQL":"SELECT COUNT() AS `__count` FROM `requirement_requirementquotation` WHERE (`requirement_requirementquotation`.`trade_status` = %s AND `requirement_requirementquotation`.`web_display` = %s)","dst":"socket <IP_ADDRESS>:3306","name":"Cursor.execute","stp":"2101"},{"E":1,"S":7,"SQL":"SELECT COUNT() AS `__count` FROM `message_usermessage` WHERE (`message_usermessage`.`receiver` = %s AND `message_usermessage`.`state` = %s AND `message_usermessage`.`web_display` = %s)","dst":"socket <IP_ADDRESS>:3306","name":"Cursor.execute","stp":"2101"},{"E":2,"S":10,"SQL":"SELECT `website_websiteinfo`.`id`, `website_websiteinfo`.`website_name`, `website_websiteinfo`.`short_name`, `website_websiteinfo`.`index_title`, `website_websiteinfo`.`index_state`, `website_websiteinfo`.`website_icon`, `website_websiteinfo`.`website_logo`, `website_websiteinfo`.`weixin_ewm`, `website_websiteinfo`.`website_description`, `website_websiteinfo`.`website_keywords`, `website_websiteinfo`.`service_TEL`, `website_websiteinfo`.`service_time`, `website_websiteinfo`.`company_email`, `website_websiteinfo`.`recruit_email`, `website_websiteinfo`.`email_banner`, `website_websiteinfo`.`office_short`, `website_websiteinfo`.`address_short`, `website_websiteinfo`.`detail_address`, `website_websiteinfo`.`address_dest`, `website_websiteinfo`.`website_time`, `website_websiteinfo`.`copyright_ownership`, `website_websiteinfo`.`copyright_hyperlink`, `website_websiteinfo`.`record_number`, `website_websiteinfo`.`record_hyperlink`, `website_websiteinfo`.`add_time`, `website_websiteinfo`.`update_time`, `website_websiteinfo`.`web_display` FROM `website_websiteinfo` WHERE `website_websiteinfo`.`web_display` = %s ORDER BY `website_websiteinfo`.`update_time` DESC LIMIT 1","dst":"socket <IP_ADDRESS>:3306","name":"Cursor.execute","stp":"2101"},{"E":2,"S":24,"SQL":"SELECT `website_websiteseomate`.`id`, `website_websiteseomate`.`siteadmin_name`, `website_websiteseomate`.`meta_sign`, `website_websiteseomate`.`add_time`, `website_websiteseomate`.`update_time`, `website_websiteseomate`.`web_display` FROM `website_websiteseomate` WHERE `website_websiteseomate`.`web_display` = %s ORDER BY `website_websiteseomate`.`update_time` DESC","dst":"socket <IP_ADDRESS>:3306","name":"Cursor.execute","stp":"2101"},{"E":1,"S":29,"SQL":"SELECT `website_indexslideshow`.`id`, `website_indexslideshow`.`title`, `website_indexslideshow`.`image`, `website_indexslideshow`.`priority_level`, `website_indexslideshow`.`hyperlink`, `website_indexslideshow`.`activity_id`, `website_indexslideshow`.`add_time`, `website_indexslideshow`.`update_time`, `website_indexslideshow`.`web_display` FROM `website_indexslideshow` WHERE `website_indexslideshow`.`web_display` = %s ORDER BY `website_indexslideshow`.`priority_level` ASC, `website_indexslideshow`.`update_time` DESC","dst":"socket <IP_ADDRESS>:3306","name":"Cursor.execute","stp":"2101"},{"E":2,"S":32,"SQL":"SELECT `requirement_requirementquotation`.`id`, `requirement_requirementquotation`.`title_id`, `requirement_requirementquotation`.`appoint`, `requirement_requirementquotation`.`username_id`, `requirement_requirementquotation`.`price`, `requirement_requirementquotation`.`quote_time`, `requirement_requirementquotation`.`trade_status`, `requirement_requirementquotation`.`select`, `requirement_requirementquotation`.`select_time`, `requirement_requirementquotation`.`trade_time`, `requirement_requirementquotation`.`cancel_time`, `requirement_requirementquotation`.`outbid_time`, `requirement_requirementquotation`.`update_time`, `requirement_requirementquotation`.`web_display` FROM `requirement_requirementquotation` WHERE (`requirement_requirementquotation`.`trade_status` = %s AND `requirement_requirementquotation`.`web_display` = %s) ORDER BY `requirement_requirementquotation`.`trade_time` DESC LIMIT 25","dst":"socket <IP_ADDRESS>:3306","name":"Cursor.execute","stp":"2101"},{"E":3,"S":36,"SQL":"SELECT `requirement_userrequireme
[pinpoint] [45085] [45085]7 send size 4084
[pinpoint] [45085] [45085]7 send size 1012
[pinpoint] [45085] [45085]7 send size 1328
[pinpoint] [45085] [45085]#128 pinpoint_end_trace Done!
[pid: 45085|app: 0|req: 10/11] <IP_ADDRESS> () {48 vars in 1057 bytes} [Wed Dec 30 16:53:06 2020] GET / => generated 10683 bytes in 43 msecs (HTTP/1.1 200) 4 headers in 125 bytes (1 switches on core 0)
MyMiddleware request*
[pinpoint] [45085] [45085]#0 pinpoint_start start
[pinpoint] [45085] [45085]#128 add clue key:appname value:<IP_ADDRESS>-Django-8888
[pinpoint] [45085] [45085]#128 add clue key:appid value:APM-0100280001008888
[pinpoint] [45085] [45085]#128 add clue key:name value:BaseDjangoRequest request
[pinpoint] [45085] [45085]#128 add clue key:uri value:/favicon.ico
[pinpoint] [45085] [45085]#128 add clue key:client value:<IP_ADDRESS>
[pinpoint] [45085] [45085]#128 add clue key:server value:<IP_ADDRESS>
[pinpoint] [45085] [45085]#128 add clue key:stp value:1700
[pinpoint] [45085] [45085]#128 add clue key:tid value:APM-0100280001008888^1609314791099^232
[pinpoint] [45085] [45085]#128 add clue key:sid value:1122446265
[pinpoint] [45085] [45085]#128 add clues:206:GET
MyMiddleware response*
[pinpoint] [45085] [45085]#128 add clues:46:301
[pinpoint] [45085] [45085]this span:({"E":1,"FT":1700,"S":1609318386856,"appid":"APM-0100280001008888","appname":"<IP_ADDRESS>-Django-8888","client":"<IP_ADDRESS>","clues":["206:GET","46:301"],"name":"BaseDjangoRequest request","server":"<IP_ADDRESS>","sid":"1122446265","stp":"1700","tid":"APM-0100280001008888^1609314791099^232","uri":"/favicon.ico"})
[pinpoint] [45085] [45085]7 send size 322
[pinpoint] [45085] [45085]#128 pinpoint_end_trace Done!
[pid: 45085|app: 0|req: 11/12] <IP_ADDRESS> () {46 vars in 930 bytes} [Wed Dec 30 16:53:06 2020] GET /favicon.ico => generated 0 bytes in 2 msecs (HTTP/1.1 301) 4 headers in 162 bytes (1 switches on core 0)

https://github.com/pinpoint-apm/pinpoint-c-agent/issues/282#issuecomment-752380794
Not these, from collector-agent

Hmm, shared your collector-agent log to us?

I feel that the server side is very unstable!
I just tried to stop all dockers first, then start, and then the django project returned to normal, data can be received, and the topology diagram is also normal, like this:

Hmm, shared your collector-agent log to us?

I feel that the server side is very unstable!
I just tried to stop all dockers first, then start, and then the django project returned to normal, data can be received, and the topology diagram is also normal, like this:

hmm,  please let us know if the problem comes out again!

Hmm, shared your collector-agent log to us?

I feel that the server side is very unstable!
I just tried to stop all dockers first, then start, and then the django project returned to normal, data can be received, and the topology diagram is also normal, like this:

hmm, please let us know if the problem comes out again!

Okay! Tks. The collector-agent log that may cause the error just now is as follows:
[2020-12-28 11:22:22,605] [61539] [ERROR] [GrpcAgent.py:116] handleCommand channel  <_MultiThreadedRendezvous of RPC that terminated with:
status = StatusCode.INTERNAL
details = "Exception serializing request!"
debug_error_string = "None"

error
[2020-12-30 15:46:24,209] [3758] [ERROR] [GrpcAgent.py:116] handleCommand channel  <_MultiThreadedRendezvous of RPC that terminated with:
status = StatusCode.INTERNAL
details = "Exception serializing request!"
debug_error_string = "None"
error
[2020-12-30 15:49:43,529] [41597] [ERROR] [GrpcAgent.py:116] handleCommand channel  <_MultiThreadedRendezvous of RPC that terminated with:
status = StatusCode.INTERNAL
details = "Exception serializing request!"
debug_error_string = "None"
error
[2020-12-30 16:51:45,081] [42795] [ERROR] [GrpcAgent.py:192] ping response abort with exception: [hostname: "localhost.localdomain"
ip: "<IP_ADDRESS>"
ports: "80"
serviceType: 1700
pid: 42795
endTimestamp: -1
]  <_MultiThreadedRendezvous of RPC that terminated with:
status = StatusCode.UNAVAILABLE
details = "Socket closed"
debug_error_string = "{"created":"@1609318305.080919174","description":"Error received from peer ipv4:<IP_ADDRESS>:9991","file":"src/core/lib/surface/call.cc","file_line":1062,"grpc_message":"Socket closed","grpc_status":14}"

[2020-12-30 16:51:45,082] [42795] [ERROR] [GrpcAgent.py:116] handleCommand channel  <_MultiThreadedRendezvous of RPC that terminated with:
status = StatusCode.UNAVAILABLE
details = "Socket closed"
debug_error_string = "{"created":"@1609318305.080893075","description":"Error received from peer ipv4:<IP_ADDRESS>:9991","file":"src/core/lib/surface/call.cc","file_line":1062,"grpc_message":"Socket closed","grpc_status":14}"

error

...
...
...
[2020-12-30 16:56:05,127] [42795] [ERROR] [GrpcAgent.py:116] handleCommand channel  <_MultiThreadedRendezvous of RPC that terminated with:
status = StatusCode.UNAVAILABLE
details = "failed to connect to all addresses"
debug_error_string = "{"created":"@1609318565.126249174","description":"Failed to pick subchannel","file":"src/core/ext/filters/client_channel/client_channel.cc","file_line":4142,"referenced_errors":[{"created":"@1609318479.578852258","description":"failed to connect to all addresses","file":"src/core/ext/filters/client_channel/lb_policy/pick_first/pick_first.cc","file_line":397,"grpc_status":14}]}"

error
[2020-12-30 16:56:15,129] [42795] [ERROR] [GrpcAgent.py:116] handleCommand channel  <_MultiThreadedRendezvous of RPC that terminated with:
status = StatusCode.UNAVAILABLE
details = "failed to connect to all addresses"
debug_error_string = "{"created":"@1609318575.128495046","description":"Failed to pick subchannel","file":"src/core/ext/filters/client_channel/client_channel.cc","file_line":4142,"referenced_errors":[{"created":"@1609318479.578852258","description":"failed to connect to all addresses","file":"src/core/ext/filters/client_channel/lb_policy/pick_first/pick_first.cc","file_line":397,"grpc_status":14}]}"
error
[2020-12-30 16:56:25,130] [42795] [ERROR] [GrpcAgent.py:116] handleCommand channel  <_MultiThreadedRendezvous of RPC that terminated with:
status = StatusCode.UNAVAILABLE
details = "failed to connect to all addresses"
debug_error_string = "{"created":"@1609318585.130018647","description":"Failed to pick subchannel","file":"src/core/ext/filters/client_channel/client_channel.cc","file_line":4142,"referenced_errors":[{"created":"@1609318479.578852258","description":"failed to connect to all addresses","file":"src/core/ext/filters/client_channel/lb_policy/pick_first/pick_first.cc","file_line":397,"grpc_status":14}]}"
error
[2020-12-30 16:56:35,132] [42795] [ERROR] [GrpcAgent.py:116] handleCommand channel  <_MultiThreadedRendezvous of RPC that terminated with:
status = StatusCode.UNAVAILABLE
details = "failed to connect to all addresses"
debug_error_string = "{"created":"@1609318595.131493850","description":"Failed to pick subchannel","file":"src/core/ext/filters/client_channel/client_channel.cc","file_line":4142,"referenced_errors":[{"created":"@1609318479.578852258","description":"failed to connect to all addresses","file":"src/core/ext/filters/client_channel/lb_policy/pick_first/pick_first.cc","file_line":397,"grpc_status":14}]}"
error

https://github.com/pinpoint-apm/pinpoint-c-agent/issues/282#issuecomment-752386546
It looks the network unavailable !
How about now?

#282 (comment)
It looks the network unavailable !
How about now?

Since restarting the server, everything is normal, and the collector-agent log has no errors. I am worried that after adding a new app, if no data appears, the server may have to be restarted.  ^.^

The collector-agent or the pinpoint ?

The collector-agent or the pinpoint ?

There is no error in both.

collector-agent will automatic register new application. But you must choose the different applicationName and applicationID

collector-agent will automatic register new application. But you must choose the different applicationName and applicationID

We have paid attention to this. There are special naming rules to ensure that ID and NAME are unique.

collector-agent will automatic register new application. But you must choose the different applicationName and applicationID

Hi!
Excuse me, how to configure tomcat started with daemon.sh?
I know that in catalina.sh:
JAVA_OPTS="$JAVA_OPTS -javaagent:/usr/local/pinpoint-agent/pinpoint-bootstrap-1.8.0.jar"
JAVA_OPTS="$JAVA_OPTS -Dpinpoint.agentId=APM-01002800806880"
JAVA_OPTS="$JAVA_OPTS -Dpinpoint.applicationName=<IP_ADDRESS>-tomcat8-80"
But after copying to daemon.sh, pinpoint-web still reports the error "There are no running agents.". Try to modify several parameters by yourself, and the problem remains.

@373836411
I'm confusing, if no running agents, why?

@373836411
I'm confusing, if no running agents, why?

@373836411
I'm confusing, if no running agents, why?

Sorry, the tomcat problem should not be asked here, because it has nothing to do with Django (Python).
In addition, I have solved the above problem:
↓↓↓  daemon.sh   ↓↓↓
Pinpoint 20201231
JAVA_OPTS="-javaagent:/usr/local/pinpoint-agent/pinpoint-bootstrap-1.8.0.jar
-Dpinpoint.agentId=APM-01002800806880
-Dpinpoint.applicationName=<IP_ADDRESS>-tomcat8-80"
But when monitoring tomcat started in daemon mode, I encountered the "No data" problem. Restarting the server this time did not help. I am still looking for a solution.

@373836411
I'm confusing, if no running agents, why?

Sorry, the tomcat problem should not be asked here, because it has nothing to do with Django (Python).
In addition, I have solved the above problem:
↓↓↓  daemon.sh   ↓↓↓
Pinpoint 20201231
JAVA_OPTS="-javaagent:/usr/local/pinpoint-agent/pinpoint-bootstrap-1.8.0.jar
-Dpinpoint.agentId=APM-01002800806880
-Dpinpoint.applicationName=<IP_ADDRESS>-tomcat8-80"
But when monitoring tomcat started in daemon mode, I encountered the "No data" problem. Restarting the server this time did not help. I am still looking for a solution.

Glad to hear that !!!

Glad to hear that !!!

It's looks done


Switching from SendAppleNativeNotificationAsync

In our product we are currently using SendAppleNativeNotificationAsync(string payload, string tagExpression)
This method provides no way to set the header. When switching over to SendNotificationAsync like the example above it lists the Tag attribute as being obsolete. What is the correct method for setting both the Header and the tags, and why has tags been marked obsolete?

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

ID: 5fa4b158-79fb-e664-3604-0c8a2ef925d1
Version Independent ID: 33d2079e-1cd9-7933-b9fd-f57aeb0794fc
Content: Azure Notification Hubs iOS 13 updates
Content Source: articles/notification-hubs/push-notification-updates-ios-13.md
Service: notification-hubs
GitHub Login: @sethmanheim
Microsoft Alias: sethm

@kyle-thomas-TT , Thanks for raising the issue. I am investigating this and will update you.

@kyle-thomas-TT , Apologies for delay in response. We discussed internally and here is the update.
Essentially, while the tag attribute is itself marked obsolete, the SendNotificationAsync method accepts tags as a parameter (tagexpression) instead.
So, for example if the user wanted to send header and a tag (“some-tag”) they can do so as shown in the example below. If they have multiple tags, they can send those in the tag expression with logical groupings such as AND/OR, etc.
var hub = NotificationHubClient.CreateFromConnectionString(...);
var headers = new Dictionary<string, string>
{
{"apns-push-type", "background"},
{ "apns-priority", "5" }
};
var message = "{ "aps": { "content-available": 1 }";
var tagExpression = "some-tag";
var notification = new AppleNotification(message, headers);
await hub.SendNotificationAsync(notification, tagExpression, CancellationToken.None);
Please let me know if you have further queries.

@kyle-thomas-TT , Just wanted to understand if we can go ahead and close the issue for now?

Yes, thanks for the response.


ImageTable.show does not support an image variable not named image

I have a CAS table with id, label and LayerAct_0_IMG_0
I have create the image table
data = ImageTable.from_table(outTbl3, image_col='LayerAct_0_IMG_0')
however,  data.show(nimages=10, ncol=5, randomize=False) has errors about image variable not found; data.show does not have an image option that parses in the image variable.

Which DLPy version?
Best,
XQ
On Feb 4, 2019, at 9:44 AM, xinmwu <notifications<EMAIL_ADDRESS>wrote:
EXTERNAL
I have a CAS table with id, label and LayerAct_0_IMG_0
I have create the image table
data = ImageTable.from_table(outTbl3, image_col='LayerAct_0_IMG_0')
however, data.show(nimages=10, ncol=5, randomize=False) has errors about image variable not found; data.show does not have an image option that parses in the image variable.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/sassoftware/python-dlpy/issues/103, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AkXhu3l7MNB8qAMNzOsZJkMM_4JOfPI0ks5vKEdJgaJpZM4ahVqH.

It is 1.0.1
From: sasxianhu<EMAIL_ADDRESS>Sent: Tuesday, February 05, 2019 7:49 AM
To: sassoftware/python-dlpy<EMAIL_ADDRESS>Cc: Xinmin Wu<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [sassoftware/python-dlpy] ImageTable.show does not support an image variable not named image (#103)
EXTERNAL
Which DLPy version?
Best,
XQ
On Feb 4, 2019, at 9:44 AM, xinmwu <notifications@github.com<mailto:notifications@github.commailto:notifications<EMAIL_ADDRESS>wrote:
EXTERNAL
I have a CAS table with id, label and LayerAct_0_IMG_0
I have create the image table
data = ImageTable.from_table(outTbl3, image_col='LayerAct_0_IMG_0')
however, data.show(nimages=10, ncol=5, randomize=False) has errors about image variable not found; data.show does not have an image option that parses in the image variable.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/sassoftware/python-dlpy/issues/103, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AkXhu3l7MNB8qAMNzOsZJkMM_4JOfPI0ks5vKEdJgaJpZM4ahVqH.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/sassoftware/python-dlpy/issues/103#issuecomment-460625864, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AtIhNeva5wS49AihoXWlfBb0v1urfNxuks5vKX3CgaJpZM4ahVqH.

@xinmwu I am still cleaning up the hard codings from the very initial version. I will be adding this feature shortly.

@xinmwu I am about to push some changes. In order you to get these changes you have two options: 1) wait until the next release, hoping to have one late February or early March, or 2) git clone and point out to that version.
When I push the code, this issue will be closed, if you still have issues. feel free to re-open it.

@xinmwu I just check the source code again and I believe you might have a different issue. I am looking into this.

I fixed this with another push. Seems like the problem was coming from a different place. I tested with a scenario very close to yours and it is working. But again, in order to get this change you should get a local copy or wait until the next release and do an update.


Hip82 keith 20230604

Changes made to opt-out v opt-in, deleted the cutoff rate calculation paragraph, and added in a requirement for a yearly subscriber usage report.  This should be done after Boris's changes are implemented.

resolved the conflict as you asked.


Expand all nodes

HI,
How is it possible to expand all nodes programaticaly ?

Hi,
I would like to know is that possible as well.

Not possible atm


Add missing formatter file

By doing {"ecto", "~> 2.2.9", override: true} in my mix.exs and  import_deps: [:ecto] in my own formatter, I was expecting to have the ecto rules set in my project.
However, it seems that the file .formatter.exs is missing from the package on hex.
I then make the assumption that it should be present in the branch v2.2.
This commit aims to complete this one https://github.com/elixir-ecto/ecto/commit/9463e1c9564cd971754e3324033cdc5546ac428f

:heart: :green_heart: :blue_heart: :y...


Update packages.json

change package name,

You should keep the old name IMO.

I saw an example of how to add an alias in-order to let users to download the packages using the alias name and just did the follow,
here is an example from inside the package.json
  {
    "name": "monad",
    "alias": "maybe"
  },
  {
    "name": "maybe",
    "url": "https://github.com/superfunc/maybe",
    "method": "git",
    "tags": [
      "library",
      "functional",
      "optional",
      "monad"
    ],
    "description": "basic monadic maybe type for Nim",
    "license": "BSD3",
    "web": "https://github.com/superfunc/maybe"
  },

Why do you want to rename it? I think the current name is fine.
On 17 Sep 2017 12:59, "Benny Elgazar"<EMAIL_ADDRESS>wrote:

I saw an example of how to add an alias in-order to let users to download
the packages using the alias name and just did the follow,
here is an example from inside the package.json
{
"name": "monad",
"alias": "maybe"
},
{
"name": "maybe",
"url": "https://github.com/superfunc/maybe",
"method": "git",
"tags": [
"library",
"functional",
"optional",
"monad"
],
"description": "basic monadic maybe type for Nim",
"license": "BSD3",
"web": "https://github.com/superfunc/maybe"
},
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/nim-lang/packages/pull/583#issuecomment-330038870,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAPDexXUL7kxItHLa8QSAubAkHUuYFnmks5sjQmfgaJpZM4PY7QM
.

@dom96 Because I want everyone install it nimble install db_presto
and use it import db_presto

Okay, but why do you want this name and not "presto", what's wrong with import presto?

because I wanted to save the conversion of importing databases in nim.
db_mysql
db_postgres
db_...

Alright, for this case you can just rename the package directly (there is no need to alias since your package is very new). I'll do it for you.


Escape markdown link name

To fix messages with \, [ and ] in the link name.

Coverage decreased (-0.1%) to 64.838% when pulling 91d52aee3a68c9d19ffd18e0cdbf55676c9f5c23 on FYPetro:frenzyli-markup-escape into 4204aa4cd33040a66d122f745e0fa2a361fa491d on Charcoal-SE:master.


vee-validate rejects scoped IPv6 address.

Versions

vee-validate: 2.5.6
vue: 2.0.3

Describe the bug
Vee-validate will not accept scoped IPv6 addresses.  That is, addresses terminated by '%X' or '%ethX' where X is the interface number.
To reproduce
Steps to reproduce the behavior:
Create an  with v-validate="'ip:6'".
Enter a valid IPv6 address, with scope (e.g. '%1')
VeeValidate indicates it is an error.
Expected behavior
IPv6 with scope should pass validation.
Demo link
https://codesandbox.io/s/j42zv5v3p9
Desktop (please complete the following information):

OS: Windows
Browser: Firefox
Version: 64.0.2

closing since this is not fixable by vee-validate at the moment.


Update Netty to 4.1.72.Final

Update Netty to 4.1.72.Final

@ffang would you mind please taking a look, the change is trivial but new dependency has been introduced by Netty (https://github.com/netty/netty/pull/11745) and led to OSGi features update, thank you!


the workspace path can't include whitespace on Mac and Linux for Python

VSCode Version: 1.17.2
OS Version: Mac high Sierra, Ubuntu 16.04

Steps to Reproduce:

Reproduces without extensions: Yes/No

@diuming I am assuming you are using a extension providing the Python support. Please file the issue there. Thanks.

If you think it is a VS Code issue, please provider steps on how to reproduce the problem.


fixes #421 add last handler to Handler class for handler chain inject…

… in the beginning

Codecov Report

Merging #422 into develop will decrease coverage by 0.01%.
The diff coverage is 0%.

@@              Coverage Diff              @@
##             develop     #422      +/-   ##
=============================================
- Coverage      49.51%   49.49%   -0.02%
- Complexity      1649     1650       +1
=============================================
  Files            240      240
  Lines          10424    10432       +8
  Branches        1497     1498       +1
=============================================
+ Hits            5161     5163       +2
- Misses          4646     4653       +7
+ Partials         617      616       -1

Impacted Files
Coverage Δ
Complexity Δ

...va/com/networknt/handler/OrchestrationHandler.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...r/src/main/java/com/networknt/handler/Handler.java
41.7% <0%> (-0.86%)
23 <0> (ø)

.../src/main/java/com/networknt/utility/HashUtil.java
63.33% <0%> (+3.33%)
11% <0%> (+1%)
:arrow_up:

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 a60c9b2...bc744f4. Read the comment docs.

#421


[BUG] Linux chip-tool : Memory may leak when try to control device after subscription

Reproduction steps
step 1.start linux chip-tool in interactive mode
./chip-tool interactive start
step 2.use chip-lighting-app as TH, and commission it using linux chip-tool
pairing onnetwork 10 20202021
step 3.send on/off command to chip-lighting-app
on-off on 10 1
step 4.Repete step 4 maybe 10 or 20 times. Compare memory difference
ps aux | grep chip-tool
Then you can see that the VMRSS will grow instantly， or you can use cat /proc/[pid]/status, you will see that the vmdata keep growing after every command
Bug prevalence
Whenever I do this
GitHub hash of the SDK that was being used
e2fa6baefcf63cb3e4f7060ccd34480254bb842e
Platform
other
Platform Version(s)
ubuntu 22.04
Anything else?
Actually, I tried it on Nov 2022 sdk version, which has the same result of the version above.
I don't know if I missed some key points.
We are now developing the controller program based on the chip-tool program. It will be appreciated if you can answer this issue!

Finally I find that it's related with the pesistentstorage that will be init every time.
So I add a member value to record the name. If init next time, compare name with the record name first, and return directly if they are same. I dont know if this is a right way to solve this problem......

Finally I find that it's related with the pesistentstorage that will be init every time. So I add a member value to record the name. If init next time, compare name with the record name first, and return directly if they are same. I dont know if this is a right way to solve this problem......

I find the following code comment:
// TODO: It's pretty weird that we re-init mCommissionerStorage for every
// identity without shutting it down or something in between...


Add test for map overlap ordering

See https://github.com/dask/dask/issues/3554
cc @jakirkham
This doesn't resolve the issue in 2d though, and may be just a hack.

[x] Tests added / passed
[x] Passes flake8 dask

cc also @TomAugspurger

Actually, as discussed in the original issue, this does seem to have a significant effect in 2d

Interesting, thanks for sharing Matt. Will give this a closer look.
Hmm...does it have negligible impact Tom or does it make things worse?
As you can imagine, we care about optimizing both of these cases as we do use both. :)

AFAICT, it has no effect on the other case.

From a first principles point of view, this will only improve things, however it may add to the cost of calling order.

OK, I tested the increased number of steps through order due to this change by looking at test_gh_3055 and it's something around 5%, which I'm ok with.  Merging this.


XML specified is not syntactically valid

This is autogenerated. Please review and update as needed.
Describe the bug
az storage logging update command when used to update table storage logging, generates an invalid XML error
Command Name
``az storage logging update --connection-string $sa --log rwd --retention 120 --services t --version 2.0 --verbose
Errors:
XML specified is not syntactically valid.
``<m:error xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata"><m:code>InvalidXmlDocument</m:code><m:message xml:lang="en-US">XML specified is not syntactically valid.
RequestId:17fbe858-f002-0090-4d79-1d4bb3000000
Time:2020-04-28T16:27:45.6607274Z</m:message></m:error>
To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Set the storage account connection string variable
`` $sa=''

Expected Behavior
Logging is provisioned as it is for both blog and queue storage
Environment Summary
Windows-10-10.0.19041-SP0
Python 3.6.6
Installer: MSI

azure-cli 2.4.0 *

Extensions:
application-insights 0.1.1
azure-devops 0.13.0
dev-spaces 1.0.3

Additional Context

"--version 2.0" cannot be specified for table storage. Removing this parameter eliminates the error.

@Juliehzl  to  help confirm this is by design behavior

add to S169

add to S171

@philspokas for table service, the supported version is 1.0 not 2.0.


fix: target incompatibility with armv6 package for raspberry pi

Proposed changes

Switch the armv6 package from using arm-unknown-linux-musleabihf to arm-unknown-linux-musleabi due to an issue being discovered with the format.
When using tedge compiled with the target arm-unknown-linux-musleabihf, an "illegal instruction" error whilst running tedge connect c8y.
Types of changes

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
[ ] Documentation Update (if none of the other choices apply)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Paste Link to the issue

Checklist

[x] I have read the CONTRIBUTING doc
[x] I have signed the CLA (in all commits with git commit -s)
[ ] I ran cargo fmt as mentioned in CODING_GUIDELINES
[ ] I used cargo clippy as mentioned in CODING_GUIDELINES
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

Further comments

@didier-wenzek sorry the PR was meant to be in draft status as I want to build the new images on the CI and test it locally on the same device before merging it.


IgnoreFiles for static folder

As discussed here
http://discuss.gohugo.io/t/slow-to-work-with-large-number-of-static-files/2046
Update IgnoreFiles to also affect files in the static folder.

I'll work to fix that issue.
But I would like to discuss if is better create a separated method or I just use the hugo.copyStatic and checking if we need ignore file or not.

Will this also cover the /static folder of themes?

From my understanding this has already been merged. However, I have the following in my config.toml ignoreFiles = [ "\\.less$"] and Hugo still detect changes. What am I doing wrong?

I'm wondering what is meant exactly for ignoreFiles. If I specify a.md there, do I mean content/a.md or a.md in the root?
BTW, I'm considering whether we should split ignoreFiles into 3 parts: ignoreContent, ignoreStaticFile and ignoreForWatch (files in there are not watched for site rebuilds).

I can't manage to make Hugo ignore static/css and static/js folders with ignoreFiles: ["static//css//.*.css$", "static//js//.*.js$"]... the regex is right according to regex101, is this a Hugo bug?

@inwardmovement, please use the Discussion Forums.

I would really like to some progress on this issue / request. Here's an example. I have SASS folder under theme, which is precisely where it should live, and I need it to be ignored from the build. However, the poorly documented "ignoreFiles" options only seems to target specific folders, again undocumented. It would be incredibly helpful, if this feature were simply broadened to accept any particular path.

I'm happy to have a go at contributing a pull request for this, if there's any general will to make the ignoreFiles option a little more versatile.

If this is still live, should it not be re-opened?

Please...Could someone address this issue or feature request for us? As it has been reflected in all above discussions, it is super anoying.

I'm also in need of this feature. I'm using a submodule inside static and Hugo copies the whole submodule instead of only its contents.

Was this ever implemented?

@jsphpndr
This issue was automatically closed as "stale" on Jan 24, 2018.
Comments on closed issues are typically ignored. You are more likely to get a response by posting your question to the forum.
The ignoreFiles configuration setting has no effect on the static/ directory. But the next release (version number TBD) will allow you to do this:
[[module.mounts]]
  source='static'
  target='static'
  excludeFiles = 'bar.txt'

Or this:
[[module.mounts]]
  source='static'
  target='static'
  includeFiles = 'foo.txt'

More info here:
https://github.com/gohugoio/hugo/commit/471ed91c60cd36645794925cb4892cc820eae626


Version 2.0 metadata rules

I have metadata that passes the version 1.3 validator, but fails the version 2.0 beta validation. See this report:
http://inspire.ec.europa.eu/validator/v2/TestRuns/EIDb9471602-09f3-49da-817a-00b53224326c.html
Should valid 1.3 metadata expected to be valid 2.0 metadata? Or will everyone across Europe have to rework their metadata to be compliant again?

We discussed this aspect in the scope of Dutch metadata profile update, leading to questions like:

should archived inspire records also be updated (our conclusion was yes)
should the metadata date be updated to the current date due to update (our conclusion was yes)

Both quite undesirable from an archiving perspective

archived inspire records

Paul - do you mean by this, "INSPIRE metadata records which have been archived" or "INSPIRE metadata records describing archived datasets"?
I'm assuming the second, as I can see reason to updte those - but not to update metadata records which have been archived (and presumably aren't therefore being made available to harvest to the EC's portal?)

 Or will everyone across Europe have to rework their metadata to be compliant again?

Our view in UK is that metadata valid to the 1.3 TG isn't likely to be valid to the 2.0 TG. All "live" metadata will need to be reworked. We understand the target date for this is December 2019.

I wonder about how realistic this timeline is since the 2.0 validation tools are all still beta. This could be a massive undertaking for mandated organizations...

Undoubtedly. But with two years notice, they shouldn't have been waiting for the validation tools.
For example, in the UK we have updated our national guidelines, and the schematron rules that support them. They have been available to organisations since last September. Our weak link is that for those who created the records manually, the two parallel software implementation (upgrade) projects are running slower than I would have hoped.

@PeterParslow are your schematrons publicly available,  can other NSDI use them?
Did you check the conformity with current ETS, e.g. Inspire metadata, or WFS/Atom download service?
Many thanks,
Tomas

The are available - published under CC-BY - at https://github.com/AGIGemini/Schematron and https://www.agi.org.uk/about/resources/category/125-schematron
They were a separate development effort, based on the TG. Do note that they also enforce constraints that are specific to the UK e.g. to ensure the metadata works within the UK Discovery Service (data.gov.uk). The design goal, which has been tested by samples, is that a record which conforms to the UK constraints will conform to the current TG & therefore - by design, and hopefully in truth! - the ETS.
The relevant version of the UK guidance is at https://www.agi.org.uk/40-gemini/


I would like to get the usage of firebase storage, how can i implement , there is no auth provided , i am talking about with the security rules (  allow read, write: if request.auth != null )

I signed with phone auth , I get only auth token id and user details. what if i would like to access , fireebase storage  with the security enabled something like ( allow read, write: if request.auth != null ). i need Auth() of the signed user! , is there is any workaround here, i can remove security rules but i dont want to lose security. any help from your end ?

my question is , how can i access my firestore and storage with this rules setted up!

I found a solution in your docs , after reading full doc! 👍


v0.12: specify parameter type as object

I addresses https://github.com/cloudposse/terraform-aws-ecs-container-definition/issues/33
Reading https://github.com/hashicorp/terraform/issues/21384 I believed we should use object type in this case.
It's working in our environment, with v0.12, incompatible with v0.11 though.

Thanks @limitusus ! We are working towards 0.12 compatibility. We're in the process of updating our tooling to support it.

If the change isn't backwards compatible I think we should wait for a solution that works for both v0.11-v0.12.

Of course agree with @pydo, though I don't expect there would be a v0.11-v0.12 compatible solution for this issue, as it's caused by a breaking syntax change point between v0.11-v0.12 😞
Our workaround is just forking this repo.

Just wanted to add, I am waiting on this too! :-D


iOS10 issue with playback fail error handler called - works in iOS9!

Now I don't know if this is specific to our setup - example on your site does play.
What I'm finding is that iOS9 is fine, iOS10 is not fine...
More detail...
Site is serving video over HTTPS - is setup securely so there may be config issues there... Playback is also fine in all other browsers we have tested.
When we use the player the error handler is triggered on iOS10 only.
Using Safari to debug we can see the same headers/responses as local browser to debugging browser (attaching safari to the device).
Direct linking to the asset doesn't work either (on the phone) which lead us to check codec settings though it does work in iOS9 - settings are h264 baseline profile 3.0.
Really at a bit of a loss at the moment so posting this here incase anyone else has experienced this...
We've pulled the current release (master branch) from the project (were on an older version) and it's made no difference - currently checked out on 2.32.2 tag which also is not playing.
I suspect this is server configuration or codec but have had no joy so far pinning this down for sure - any ideas / pointers appreciated.

@web-engineer Yes definitely sounds like an issue with server configuration or how the media was encoded. I'm not expert in that area but mostly when I've heard about these types of situations it's always related to those 2 topics

Trouble with this is that I can also remove all the secure settings/headders stuff and try over plain HTTP and same problem.
Codec should not be a problem - what is frustrating us is that this all works fine in iOS9 so something has changed but what it is we're struggling to work out.
We only use MP4, h256 media - baseline profile 3, FFMPEG encoder settings as follows -
ffmpeg -threads 0 -i SOURCE -c:v libx264 -pix_fmt yuv420p -movflags +faststart -bufsize 3000k -profile:v baseline -level 3.0 -preset slow -crf 26 -maxrate 1500k -video_size hd480 -vf scale=642:360  -c:a aac -strict -2 -ac 2 -ab 128k -ar 44100 -r 25
So far tweaking these has made no difference either.

This sounds similar on the apple forum -
https://forums.developer.apple.com/message/158745#158745
Looks like this is a bug with apple - I'll chase them also and raise with them. Will post response if I get one... note - were using aac encoding too...

Another observation - in chrome the player does show, and it tries to play - but gets stuck buffering.

OK - last ditch attempt, just uploaded one of these videos to a test server and linked direct - it worked therefore it's go to be Apache... Was preparing an example to report to Apple, but this kinda points back to configuration still...

Well made some progress that further proves the problem is apache, completely mimicked the script setup on the other host (so its a stream in video tag) and it works so much be config.
When Ive worked it out I'll post the solution - if we can pinpoint it!

@web-engineer Thanks for digging into this.

Oh dear.... i've just inverted my test and tried this a few ways around ... my latest test has taken me full circle...
When i disable mediaelement and just use the video tag I am getting playback, as soon as i use this enhancement it breaks and gets an error...
I'm going to try and script a fallback to improve this - putting a simple shell together to prove the problem was not reproducing the error, this latest test I just disabled MJS and the HTML5 built in player worked ...

When running alongside the framework to retrieve the video stream (rather than separating out the stream code) it doesn't work - looks like the framework may be influencing the output of the http stream (its a Laravel project).
This has been tricky to debug - I think the trick for anyone having trouble with MJS is to try without it first and make sure your video tags would have worked - if they do then you can wag the finger, otherwise its likely, like its looking like for me, to be the video stream itself causing the problem.

To confirm - i reckon the reason it looks broken in my case with MJS is that MJS is validating the resource and telling us its not playable (by that device), which is why we get the error trapped - in this instance that is correct and MJS is doing its job. In iOS9 and every other browser we've tested the media does play - this still doesn't mean the problem is with the player, there must be something different about the way the stream is being interpreted by mobile Safari.

Solved - the fix was at the script side...
Basically - at some point suspect it may be because of an older version (just upgraded recently to the latest tagged release) the player wasn't working and our application uses localstorage to store if the player has thrown an error and falls back to the shim player when this happens.
Problem being that when iOS10 started not liking the player the fallback player definately wont work.
Fix was to having upgraded to current release to alter the check for fallback player use to include a timer check and to toggle the mode back if enough time had elapsed since the last fallback. This for us means that our UI should get the right player - need to investigate if/why we added this fallback code - we've quite a range of browser support so suspect there is some quirk that needed it...
Anyway - there it is, if it helps anyone else with a similar problem...

Also since found the issue was related to the framework we're using not understanding the seek data sent with the requests initially, somehting has changed in iOS 9.3 or newer - we've now coded around it - if you experience the videos not playing this may be because the requests for video are subtly the latest version of iOS and in our instance this caused the server to not understand the request. The fallback issue described above was further salt in the wound as our player handler then forced the shim player too - further making it tricky to debug.


Improve database and pipelines management

Added db.py providing:

DatabaseManager() : Containing Connection Management to Database with additional utilities: urlExists() getSiteId() getUrlsScraped() and Helper Database Queries insert_site_str insert_item_str
LogsManagaer() : Maintains Logs for Spider Run, Provides 4 utitlity functions, start_log() end_log() get_log() get_logs()

Distributed and Automated Pipelines Based on Work They Perform.

ScrapeNewsPipeline() : Assigns SiteId and LogId to the Spider.
DuplicatesPipeline() : Drops any duplicate item based on url
DataFormatterPipeline() : Removes Unnecessary Space and Line Endings. Formats Date Automatically to common date format defined in settings.py
DatabasePipeline() : Stores Items into Database

settings.DB_INFO : Stores Database Credentials from Environment

custom_settings : Spider Dictionary, Stores MetaData, stats and other required info for the spider.

site_name: String, Site Name as/to be stored in Database
site_url: String, Site Address  as/to be stored in Database
site_id: Int, Default: -1, Stores SiteId assigned by pipeline
log_id: Int, Default: -1, Stores LogId Assigned by Pipeline
url_stats:  Dictionay, Stores Spider Stats: {'parsed': 0, 'scraped': 0, 'dropped': 0, 'stored': 0}

schdeuler.py : Custom Scheduling Script for Scrapyd, Server-Side, Intelligent Scheduling Based.

Requires Each Spider to have custom_settings and this:

def closed(self, reason):
        LogsManager().end_log(self.custom_settings['log_id'], self.custom_settings['url_stats'], reason)

Tested with Existing Spiders.

(1) All Changes Needs to be in PR for the system to Work.
(2) Biggest Reason, removing all those redundant lines on spiders (connecting to databases, etc), following a more modular approach to make migrations easier and automated. And yeah, Making it ready for Scrapyd (I'm gonna kill cronjob to schedule spiders, it's completely ridiculous  [perspective])
(3) These all make the pipelines flexible to tackle all kinds of spiders (there may be a few exceptions). Provides Spiders with Additional Utilities as mentioned, to make sure they don't mess with the database.

I'm out


O4B - Fleet-Footed

@stopfstedt I hope you do not mind me taking this to clear the milestone :)

@stopfstedt I hope you do not mind me taking this to clear the milestone :)

all good, sorry for hogging this one. i'm struggling to find some time these weeks.


no function named is_image_file

from opensora.utils.dataset_utils import is_image_file
I can't find a function named is_image_file.

Sorry, we fixed that.


Implementing node-portfinder

Implemented node-portfinder to dynamically get a free port.

Have you added it to dependencies?

No hadn't, my bad. Corrected it in a new commit.

Can you version bump this to 2.0.6?
Update the Readme, package.json, etc, still on this PR.

Updated readme, package.json and the git tag version. Hope i didnt miss one.

I'm merging now, please make this PR again to the develop branch.

Develop updated :smiley:
Nice work @kevinchevallier

Just updated the readme. Should i create a new PR or can you still merge?

New PR.

And please @Nipher do git push --tags.


Show number of players this week/month/season/all time for league/tournaments somewhere

A little start at this with some matches stats in e5dfd551.


No matching distribution found

Hello, I am having trouble with installing the latest version of itk-tubetk.
When I create a new conda environment with python 3.9, pip install itk-tubetk==1.3.5 throws this error
ERROR: Could not find a version that satisfies the requirement itk-tubetk==1.3.5 (from versions: 0.9.0, 1.0.0, 1.1rc1, 1.1, 1.2, 1.2.1, 1.3, 1.3.1)
ERROR: No matching distribution found for itk-tubetk==1.3.5

When I create a new conda environment with python 3.10,  pip install itk-tubetk==1.3.5 throws this error
ERROR: Could not find a version that satisfies the requirement itk-tubetk (from versions: none)
ERROR: No matching distribution found for itk-tubetk

Strangely, when I try  pip install itk-tubetk==1.3.5, I am able to install the latest version. Could you please let me know how I can install v1.3.5 locally? Thank you.

We do not currently support aarch64 on TubeTK in newer builds.  What
processor are you using?
On Fri, Nov 17, 2023 at 9:46 PM soojinpren @.***> wrote:

Hello, I am having trouble with installing the latest version of
itk-tubetk.
When I create a new conda environment with python 3.9, pip install
itk-tubetk==1.3.5 throws this error
ERROR: Could not find a version that satisfies the requirement itk-tubetk==1.3.5 (from versions: 0.9.0, 1.0.0, 1.1rc1, 1.1, 1.2, 1.2.1, 1.3, 1.3.1)
ERROR: No matching distribution found for itk-tubetk==1.3.5
When I create a new conda environment with python 3.10, pip install
itk-tubetk==1.3.5 throws this error
ERROR: Could not find a version that satisfies the requirement itk-tubetk (from versions: none)
ERROR: No matching distribution found for itk-tubetk
Strangely, when I try pip install itk-tubetk==1.3.5, I am able to install
the latest version. Could you please let me know how I can install v1.3.5
locally? Thank you.
—
Reply to this email directly, view it on GitHub
https://github.com/InsightSoftwareConsortium/ITKTubeTK/issues/150, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AACEJLZHSJA4JYS7D6W5OH3YFAOQXAVCNFSM6AAAAAA7QUP6E2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGAYDAMJXGQ4DKNI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

--
Stephen R. Aylward, Ph.D.
Chair, MONAI Advisory Board
Senior Director, Strategic Initiatives, Kitware

Hi @aylward, thank you for your reply. The OS and CPU of my computer are:
Ubuntu 18.04.6 LTS (GNU/Linux 5.4.0-1103-aws x86_64v)
Architecture:        x86_64
CPU op-mode(s):      32-bit, 64-bit
Byte Order:          Little Endian
CPU(s):              8
On-line CPU(s) list: 0-7
Thread(s) per core:  2
Core(s) per socket:  4
Socket(s):           1
NUMA node(s):        1
Vendor ID:           GenuineIntel
CPU family:          6
Model:               85
Model name:          Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz
Stepping:            7
CPU MHz:             3114.548
BogoMIPS:            4999.99
Hypervisor vendor:   KVM
Virtualization type: full
L1d cache:           32K
L1i cache:           32K
L2 cache:            1024K
L3 cache:            36608K
NUMA node0 CPU(s):   0-7

Yes - but I'm working on it!   I just switched the build system to the base approach used by ITK's core.  I hope to have new builds within a week, for a full range of platforms.

New versions of the wheels with support for ubuntu and new Macs are now available on Pypi as itk-tube 1.4.0
Note that there are know issue for these for select functions, due to requiring changes to ITK now in the current release of ITK wheels (5.4).  The next ITK wheels (with the required changes) won't be release for several months, so if you encounter a crash, it might be due to this incompatibility.   I've uploaded new ITK wheels to the PyPI TEST server for Windows running Python 3.11, and this week for Ubuntu 22.04.  See this issue for more details: https://github.com/InsightSoftwareConsortium/ITKTubeTK/issues/160#issuecomment-2198675116
I'll update the README with this info.  Sorry for the inconvenience, but I'm doing what I can.  Fairly large changes had to be made to get things working again!   Thanks for your patience.


Add percona-server56

This is a straight copy of
https://raw.githubusercontent.com/Homebrew/homebrew-core/367439579ece4ae429e56fc3fd24ae7b36ecbca0/Formula/percona-server.rb

The homebrew-core formula recently got bumped to 5.7

Actually I will amend this a bit...

I'm curious about how the brew-bot works? Does it run after every commit?

Yup!

OK I believe this should be good now.

Merged in https://github.com/Homebrew/homebrew-versions/commit/bc95d6822bc2d22312a49681cf052c52677614d9. Thank you for your contribution to Homebrew @magneland; we appreciate it! :smiley_cat:


Testnet #38

Testnet Release
Testnet name: Kalyke
Release date: 2022-12-12
Testnet release manager: @aubrika
Testnet Release Manager Checklist
Preceding Friday (sprint planning day):

[x] Create GitHub project column, work with team to populate the milestone with tickets targeted for the release.

Tuesday (or after release of previous testnet):

[x] Construct the genesis data for the release: https://github.com/penumbra-zone/penumbra/pull/1738

[x] Create new testnet directory with initial genesis allocations for this testnet by running cd testnets && ./new-testnet.sh

This genesis data will be used for testnet-preview with a randomized version of the future testnet's chain ID.

Thursday:

[x] Check in with team again in a release meeting and update the GitHub milestone to ensure it represents what will make it into the testnet.
[ ] Draft an announcement for peer review to ensure major changes included are comprehensive.

Following Monday (release day):

[x] Verify that testnet-preview.penumbra.zone is operational; it is redeployed on every push to main, and is an exact preview of what is about to be deployed.

:heavy_check_mark:  We had a release blocker, now resolved: https://github.com/penumbra-zone/penumbra/issues/1744

[ ] Create new git tag e.g. 006-orthosie on main (tags created on any other branches will not transfer when merged in) and push to shared remote: git tag -a <tag_name> - must be annotated tag, i.e. git tag -a for Vergen build. This will create a Waiting GitHub Action for deployment.
[ ] You must manually review the Waiting deployment in the GitHub Action UI before the deployment will begin. Monitor the GitHub action to ensure it completes after it is approved.
[ ] Update the User Guide to mention the newly created git tag.
[ ] Delegate to the Penumbra Labs CI validator
[ ] Make GitHub release object and include the announcement
[ ] Make the announcement to Discord! 🎉🎉🎉

TODO: add to checklist issue template:

Update Galileo according to readme steps in https://github.com/penumbra-zone/galileo/

Note to self for docs update: a regex like this will find the rg  -i '\d{3}\-[\w.]+' -l docs/guide/src/ files for "Update the User Guide to mention the newly created git tag."

Looks like Galileo CI started breaking 3 days ago: https://github.com/penumbra-zone/galileo/actions/runs/3651002144 that was likely related to testnet-preview bug, still serving testnet tag, fixed in https://github.com/penumbra-zone/penumbra/commit/17a3267f63e1765d40cd5d3d071292b8bd4f7fbe.

Posted the announcement, as 038-kalyke is available at testnet.penumbra.zone. Unfortunately, it's not using the new deployment pipeline, but I'll follow-up separately about that in #1659 this week. Also, galileo is still down, presumably needs some code changes to work well again.

All set. Followed up with some CI improvements in https://github.com/penumbra-zone/penumbra/pull/1763, and testnet-preview is live once more.

galileo is still down, presumably needs some code changes to work well again.

Fixed in https://github.com/penumbra-zone/galileo/commit/c10e75ea7fcd19e762ed9ba1d0aa58fdde93ba24 That wraps up the 038-Kalyke release, so I'm closing this ticket.


Re-add Bandwidth Manager in CI

One of the limitations of GH actions is the inability of running Bandwidth Manager feature on our CI as described in the "cons" section in https://github.com/cilium/cilium/pull/25713
To provide the same coverage we should add a test for this functionality in the connectivity tests of cilium-cli as it would be nice to test this feature.
The ginkgo test can be found in https://github.com/cilium/cilium/blob/ad36a8c65cd944cd8cbf227e383304f9c14c0ab8/test/k8s/bandwidth.go

Can I be assigned this issue?

Yes, sounds good. Do you have a PR in mind? @Jack-R-lantern

Not yet, But I'll try to fix that as soon as possible.
Can I add test here? @aanm

Ideally the test would be part of the cilium-cli as a connectivity test. Similar to https://github.com/cilium/cilium-cli/tree/main/connectivity/tests

I know you're busy and I'm really sorry.
But I need confirmation, I'm trying to implement it here, did I understand your intention correctly?

@Jack-R-lantern yep, that would be the right place.


Add filter async methods, move to Swift 5.7, and some refinements for current funcs

Add filter methods accepting async closures
Update README with the new filter methods
Add tests for the new filter methods
Some fixes for existing functions
Move to Swift 5.7
Enable swift-concurrency=complete on 5.9+
Update CI

i could also remove the Filter method and add it to another PR, so there is 2 PRs, one with some general refinements and one with the new function(s), if you care.

Codecov Report
Attention: 7 lines in your changes are missing coverage. Please review.

Comparison is base (736f7bd) 97.67% compared to head (c731ae7) 96.67%.
 Consider uploading reports for the commit 11b812e to get more accurate results

Files
Patch %
Lines

Sources/AsyncCollections/Filter.swift
93.97%
5 Missing :warning:

Sources/AsyncCollections/Map.swift
93.10%
2 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main       #2      +/-   ##
==========================================
- Coverage   97.67%   96.67%   -1.00%
==========================================
  Files           4        5       +1
  Lines         215      301      +86
==========================================
+ Hits          210      291      +81
- Misses          5       10       +5

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

@adam-fowler for the record i've also tried this for concurrentFilter: Filter.swift#L62
    let array = Array(0 ..< 1_000_000).map { (element: $0, isIncluded: Bool.random()) }
    let result = await array.concurrentFilter { value -> Bool in
        try! await Task.sleep(nanoseconds: 1000)
        return value.isIncluded
    }
    _ = result.count

even for 1 million items, the current implementation is faster by ~7-10%.
so i think we're good with the current implementation.


Change gitignore so we get our gen folders

Removed gen folder from .gitignore in the root and added .gitignore files in the gen folders. This ensures the gen folders are part of our repository and get created when the repository is cloned but none of the generated files are added to the repository.

Fixes #154


Retries may be done using broken connections from the pool

Expected Behavior
When restarting the Redis server, due to the default of MaxRetries: 3, I'd expect go-redis to attempt to reconnect to the server and retry the query.
Current Behavior
If there are enough old connections in the connection pool, all retry attempts are done on broken connections and an error is returned without even attempting to reconnect.
Possible Solution
Some options:

Perform a ping on the connection before reusing it (adds latency if the connection is fine)
Don't count retries on connections from the pool towards the retry limit (might lead to a huge number of retries for a single query)
Clear the pool on errors (might be overly pessimistic)
Always use a fresh connection for retries

Steps to Reproduce
The following code reproduces the issue. Instead of restarting the server, it sets a dialer that simply closes each connection after 5 seconds.
package main

import (
	"context"
	"github.com/go-redis/redis/v8"
	"log"
	"net"
	"time"
)

func main() {
	ctx := context.Background()

	// Redis client with a dialer that kills connections after 5 seconds (to simulate a server restart).
	client := redis.NewClient(&redis.Options{
		Dialer: func(ctx context.Context, network, addr string) (net.Conn, error) {
			log.Print("Dialer called")
			conn, err := net.Dial(network, addr)
			if err == nil {
				go func() {
					time.Sleep(5 * time.Second)
					conn.Close()
				}()
			}
			return conn, err
		},
	})

	// Function to ping the server and log errors if they occur.
	ping := func() {
		_, err := client.Ping(ctx).Result()
		if err != nil {
			log.Print(err)
		}
	}

	// Perform some pings to fill the connection pool.
	for i := 0; i < 10; i++ {
		go ping()
	}

	// Wait for connections to die.
	time.Sleep(10 * time.Second)

	// Perform another ping and log pool stats before and after.
	log.Printf("%#v", client.PoolStats())
	ping()
	log.Printf("%#v", client.PoolStats())
}

Example output (note that the dialer is not called for the last ping and the hit count in the pool stats increases by 4, i.e. the initial attempt and all 3 retries were done using stale connections from the pool):
2021/04/23 13:40:50 Dialer called
2021/04/23 13:40:50 Dialer called
2021/04/23 13:40:50 Dialer called
2021/04/23 13:40:50 Dialer called
2021/04/23 13:40:50 Dialer called
2021/04/23 13:40:50 Dialer called
2021/04/23 13:40:50 Dialer called
2021/04/23 13:40:50 Dialer called
2021/04/23 13:40:50 Dialer called
2021/04/23 13:40:50 Dialer called
2021/04/23 13:41:00 &redis.PoolStats{Hits:0x0, Misses:0xa, Timeouts:0x0, TotalConns:0xa, IdleConns:0xa, StaleConns:0x0}
2021/04/23 13:41:00 set tcp <IP_ADDRESS>:45526: use of closed network connection
2021/04/23 13:41:00 &redis.PoolStats{Hits:0x4, Misses:0xa, Timeouts:0x0, TotalConns:0x6, IdleConns:0x6, StaleConns:0x0}

You get similar behavior when you restart Redis at the right time instead of using this dialer. In this case, the error will be EOF instead.
When adding MaxRetries: 20 to the redis.Options, the last 3 lines of the output look like this instead (note that there were 10 hits and then 1 miss that called the dialer):
2021/04/23 13:48:46 &redis.PoolStats{Hits:0x0, Misses:0xa, Timeouts:0x0, TotalConns:0xa, IdleConns:0xa, StaleConns:0x0}
2021/04/23 13:48:49 Dialer called
2021/04/23 13:48:49 &redis.PoolStats{Hits:0xa, Misses:0xb, Timeouts:0x0, TotalConns:0x1, IdleConns:0x1, StaleConns:0x0}

Context (Environment)
I want my application to gracefully handle Redis starts and had hoped that this was handled automatically by go-redis due to the default of MaxRetries: 3.

Perform a ping on the connection before reusing it (adds latency if the connection is fine)
Don't count retries on connections from the pool towards the retry limit (might lead to a huge number of retries for a single query)
Clear the pool on errors (might be overly pessimistic)
Always use a fresh connection for retries

All these options look worse than the current behavior. Even with large pools like 100 connections we are talking only about 100/3 = 33 failed commands.

Please could you explain why exactly you don’t prefer them, especially the first one?
Why not to check whether a connection is sane before using it "in production"?

Because that means executing a ping command for each command we want to process. That means 2x lantency and 2x number of commands.

And the last suggested solution?

Always use a fresh connection for retries

If and only if something went wrong and we have to retry, do it with a new connection to avoid the risk of this issue?

That is the most reasonable option if you can provide arguments why we should add some special logic to handle retries. As I said we are talking about 100/3 = 33 failed commands. In practice even than is an exaggeration, because there is a small delay before command is retried. So it is unlikely that the command will be retried using bad connections.

Maybe I don't get the purpose of the retry functionality in go-redis. I'd expect it to handle situations like a Redis restart where all existing connections fail simultaneously, so that I don't have to handle this in my application code. The current implementation leads to errors returned from go-redis in situations where I would not expect them.

In practice even that is an exaggeration, because there is a small delay before command is retried. So it is unlikely that the command will be retried using bad connections.

That's only the case if you perform lots of concurrent actions on the pool. If there are situations were only a few goroutines interact with Redis, it is quite likely to receive an error from go-redis even though an attempt on a fresh connection would have worked perfectly fine. Reducing the pool size is not an option if the amount of concurrent Redis queries changes with time.

Well... unlikely != impossible. So I'd like to reduce 33 or even 3 to 0.

if you can provide arguments why we should add some special logic to handle retries

Pro: on Redis restart commands are not likely, but definitively not re-tried using bad connections. Increases app stability. Also apps don’t have to use pool size + x for max retries and Redis restart recoveries don’t take much longer.
Contra: you possibly re-dial unnecessarily, but if one connection breaks, the others likely do as well – Redis restart or similar. This should not hurt much as:

Redis should be operational the most time
if you’re going to retry, you've already got more latency

Shall I make a PR?

This is what database/sql does - https://github.com/golang/go/blob/master/src/database/sql/sql.go#L1808-L1816. You will have to

introduce cachedOrNewConn/alwaysNewConn when retrieving a conn
introduce ErrBadConn
refactor retry loop (in multiples places)

It is going to be non-trivial, but feel free to give it a try :)

And the much simpler suggestion (https://github.com/go-redis/redis/issues/1737#issuecomment-825703168) is not an option for you?

If and only if something went wrong and we have to retry, do it with a new connection to avoid the risk of this issue?

database/sql does a similar thing but only as an extra last retry. The implementation will not be any different and it will match the database/sql behavior which is a nice thing.

It is going to be non-trivial

Problems aren’t stop signs, but signposts (for me). :)

Hm... the command processing process is kinda complex (cmdable -> process -> _process -> withConn -> With* -> ...).
Where would you like to see the check whether the just returned error is X/Y/Z along with the returning of ErrBadConn?
I'd not like to just shoot in the dark by myself as you may say afterwards: err... no.
Or: do we even need that and ErrBadConn itself? Can't we just say retryable error -> bad conn?

FWIW I can very reliably reproduce this issue on AWS ElasticCache using a small redis instance w/ primary and replica in non-clustered mode with the default parameter group.  Importantly this sets close-on-replica-write to true.  I then have multiple goroutines reading and writing from the redis server and initiate a failover.  In variably this leads to read only commands like HKEYS failing with EOF error, presumably since they are reusing connections that were closed due to the close-on-replica-write setting but left in the pool.

What about adding a user-supplied OnReuseConnection hook like OnConnect that is called before a connection is reused from the pool?

Is this resolved with #1824 being merged?

Is this resolved with #1824 being merged?

We still can't solve this problem perfectly, because the redis-server startup time is uncertain, and there may be a short-term failure to connect to the redis-server.
If redis is in the startup process, we use Dial (tcp), it will still return an error, but I think this is normal, we can not make the client wait for redis-server
With #1824, we can let us discard the damaged connection, but the loss of redis-server restart should be handled by the user.
I think we can close this issue, there seems to be no better solution, what do everybody think of this?

@monkey92t we can probably will eventually do something like https://github.com/golang/go/blob/master/src/database/sql/sql.go#L1808-L1816 , but it is not an easy refactoring. Perhaps for v9.

@monkey92t we can and probably will eventually do something like https://github.com/golang/go/blob/master/src/database/sql/sql.go#L1808-L1816 , but it is not an easy refactoring. Perhaps for v9.

We can improve #1824,  example:
func (p *ConnPool) Get(ctx context.Context) (*Conn, error) {
	if err := p.waitTurn(ctx); err != nil {
		return nil, err
	}

	for {
		p.connsMu.Lock()
		cn := p.popIdle()
		p.connsMu.Unlock()

		if cn == nil {
			break
		}

		// Skip GetConn and directly dial the new connection.
		if p.isStaleConn(cn) {
			_ = p.CloseConn(cn)
			break
		}

		atomic.AddUint32(&p.stats.Hits, 1)
		return cn, nil
	}

	atomic.AddUint32(&p.stats.Misses, 1)

	newcn, err := p.newConn(ctx, true)
	if err != nil {
		p.freeTurn()
		return nil, err
	}

	return newcn, nil
}

It may affect some unit tests...

In addition, I believe we have multiple locations that need to be changed, I will try it out and feel its complexity.


Virtual Keyboard crashes on iOS after calling show_virtual_keyboard

Godot version:
3.3
OS/device including version:
iPhone 8, iOS 14.4.2
Issue description:
After calling OS.show_virtual_keyboard(), typing anything into the virtual keyboard on iOS causes the app to crash.
Steps to reproduce:

In a gdscript, call OS.show_virtual_keyboard
Export to iOS (note if you use my repro project you'll have to set a valid Apple Team ID)
In Xcode, build and deploy to an iOS device (iPhone 8 in my case)
When the keyboards show, press any button

Minimal reproduction project:
KbdCrashTest.zip
I have traced this to https://github.com/godotengine/godot/blob/3.3/platform/iphone/keyboard_input_view.mm#L96, where if start and end are both -1 then it sets the range to (-1, 0), which later causes the crash. Possible fix is to set the range to (0,0) if start < 0.
https://github.com/godotengine/godot/blob/3.3/core/bind/core_bind.cpp#L1091 calls this function without the start/end arguments, leaving them to be -1.

cc @naithar

Here's the error in the logs:
*** Terminating app due to uncaught exception 'NSRangeException', reason: '*** -[__NSCFConstantString substringToIndex:]: Index<PHONE_NUMBER>3709551615 out of bounds; string length 0'
terminating with uncaught exception of type NSException


GSC confusion damage doesn't apply damage boost from type boosting items

It does in the original game: confusion damage calls HitSelfInConfusion which sets up attack/defense after Reflect/level/move power, then calls the normal DamageCalc routine. This routine will, among other things, look at the move type of the currently used move and potentially apply type boosting items (despite the damage originating from a confusion self-hit!). Note that only type boosting items are affected by this quirk; the only other thing DamageCalc looks at that confusion shouldn't apply is critical hits, but CriticalHit isn't set at this point.

@Marty-D, if you can confirm, add this to Mechanics Bugs?

Also, one thing I wasn't sure if I read correctly from this engine's source code, but something PO did incorrectly in a similar bug on their end was apply damage rolls (which is incorrect in at least 2gen) and also ignored Reflect (which is wrong). I found this engine's code a bit less straightforward to follow here so I'm not sure how PS handles it, but just to make it clear: GSC confusion accounts for Reflect in defense, stat changes, type boosting items, but not damage rolls.


Feat aging indicator

This implements Aging Indicator and filter/report

In all views that list grants, the danger modifier (red background) is applied to close dates on or before the current date. The warning modifier (yellow background) is applied to close dates less that X days in the future, where X is coded to a default value of 21 but should override that with an environment variable's value if present.
Help needed

I can't get the environment variable to work. I'm new to Vue, and I think the code is okay but that I'm not setting up the environment correctly? Resolved; thanks, Michael.
I have added the "Aging" view shown above but that's probably not the right place, and maybe not all the content. I need some help interpreting:

Additionally, if a grants administrator had a view or report that showed all grants across agencies closing in the same period as above, it would be very helpful for following up before it's too late.

The aging indicator is shown no matter where the table is displayed, correct? If so what is the different between My Grants interested and aging tabs?
Other than that looks really good. The aging indicator at the agency level is a good idea

Per partner feedback, I have stored close date thresholds for each partner (currently, each record in the agencies table.). Default values are 30 days for warning and 15 days for danger. Admin users can modify these values for the agencies that they can access. A user's agency (as indicated in their users table record) determine what threshold values are used in their display.

I would appreciate feedback on UI clarity and if there are better Vue ways to do this.
Also, I removed the "aging" view that I had added since that didn't seem to be what the partners had in mind.

Dialog looks perfect and Vue code is very clean.
I would prefer a put agencies/:id instead of put agencies/:id/thresholds just in case in the future we add more fields to the dialog but we should leave it like we have it now. No need to change it until we have new fields to add.

I would prefer a put agencies/:id instead of put agencies/:id/thresholds just in case in the future we add more fields to the dialog but we should leave it like we have it now. No need to change it until we have new fields to add.

I agree, so I will go ahead and change that. I usually try to stick to this as closely as I can, but I saw
fetchApi.put(`/api/eligibility-codes/${code}/enable/${enabled}`); for example, and wrote it more "specifically".

This looks awesome! Maybe you already addressed with the partners, but I'm thinking that anywhere you say "Warning" or "Danger" you could replace or include the actual color to be clear to users. So, "Close Date Warning (Yellow) Threshold" for example.

@Rapol I just changed the URL as you described. I did not change any of the function names, etc.

This looks awesome! Maybe you already addressed with the partners, but one UI suggestion from me: anywhere you say "Warning" or "Danger" you could replace or include the actual color to be clearer to users. So, "Close Date Warning (Yellow) Threshold" for example.

@hcdeng I see your point, and I made a change to apply the styles to the description text:

Unfortunately, it's kind of small.
I'm no expert, but I feel that using color names might not be good for accessibility. The same argument applies to using the colors themselves to reflect status, but strictly speaking I'm not using the colors-- I'm applying the text-warning or text-danger classes, which could be styled in various ways and (I hope) could be useful to accessibility tools.

@smattingly Great point - makes sense to me!

@Rapol I just realized that the Agencies view shows the user all agencies; I thought it showed only the user's own agency plus its ancestors and/or descendants via the parent association.
So, should an admin user be able to change the thresholds for all/any agencies? (If not, I think this is related or even identical to some of what @Michael-Stanford has described for centralization.)

I think we can tackle that later. User and agencies right now are both global, meaning that an admin can modify them.

There are some merge conflicts with yarn.lock. Lets accept the changes from develop

There are some merge conflicts with yarn.lock. Lets accept the changes from develop

As mentioned in Slack, I can't cleanly merge develop due to lint errors.


FEATURE: awx_team_role, awx_organization_role, awx_job_template_role, awx_credential_role

Hello,

can you add the Data Source awx_team_role to add a Team the grant of "Member" of another team?
This is supported by Ansible AWX APIs (even if not shown in AWX UI) and useful for RBAC management

can you add the Data Source awx_organization_role to add a Team or a User a specific grant to a Job Template (e.g. Inventory Admin, Credentials Admin, Project Admin, Execute etc. roles)?
This is supported by Ansible AWX APIs and UI

can you add the Data Source awx_job_template_role to add a Team or a User a specific grant to a Job Template (e.g. Execute role)?
This is supported by Ansible AWX APIs and UI

can you add the Data Source awx_credential_role to add a Team or a User a specific grant to a Credential (e.g. Use role)?
This is supported by Ansible AWX APIs and UI

Useful ref. of Ansible AWX collection: https://docs.ansible.com/ansible/latest/collections/awx/awx/role_module.html#ansible-collections-awx-awx-role-module
Thank you!
Claudio

Hello @kladiv ,
I know the terraform provider is not complete for now but we will add the others resources by opportunity when we will need them.
If you need them feel free to submit a PR and contribute to this provider!
Thank you


[Attachments] It's impossible to upload file into nested folder

Open Attachment window
Create several nested folders
Upload any file in any nested folder -> file isn't appeared. Please see the video

https://github.com/epam/ai-dial-chat/assets/111180458/953dafee-d9e8-4a86-8ddd-6b57f0e9e937

Verified on staging server successfully.