Analysis of validation results on the mobility database

This analysis is part of the 3.0.0 release and is intended to go a step further than what was originally planned in issue #986
The first objective is to evaluate the impact of the 3.0.0 release because it contains a lot of new rules. Do we have datasets that are invalidated with this release? How many? By which rules? How do we let those concerned know?
The second objective is to get an overview of the state of the validation results on all datasets from the mobility database.
To do:
1- Compare validation reports from V2.0.0 to V3.0.0 releases
2- Analyse the state of the validation results on all datasets from the mobility database using validator 3.0.0 release.

I'm curious: What is the result of the analysis?

Hi @derhuerst
We're not quite done with this :) We closed this issue in order to break it down into different parts, but after a discussion with @lionel-nj, we decided to keep everything here in different checkboxes. We'll post the results here.

Here are the first results and insights we had from this analysis. I'll split it into the two parts defined above.
1- Compare validation reports from v2.0.0 to v3.0.0
1.1 Datasets not supported by v2.0.0: none found
1.2 Datasets not supported by v3.0.0: two found

Tram Train's GTFS Schedule source,
Komunikacja Miejska - Płock's GTFS Schedule source

1.3 Datasets that become invalid with v3.0.0 and why
We initially found that there are 485 datasets that were valid under v2.0.0 and invalid under v3.0.0.
Here are the errors that are present in those datasets, and the number of datasets that contain them, among the list of datasets that went from valid to invalid.
{'empty_column_name': 1,
 'invalid_phone_number': 460,
 'missing_level_id': 1,
 'point_near_origin': 2,
 'stop_without_zone_id': 21}

This result was surprising because the invalid_phone_number isn't part of the new rules we added or upgraded as part of the V3.0.0 release.
This led us to ask ourselves the following questions:

🤔  Was the invalid_phone_number triggered by any datasets using v2.0.0?

we found that this notice wasn't triggered at all using v2.0.0, and the logic for this validation was changed between v2.0.0 and v3.0.0, which explains the difference

🤔  How many datasets are triggering this notice in total?

460, more than half the datasets contain it! 😱

🤔  Is this rule too strict?

The majority of them are false positives (more info in #1058). We decided to downgrade it in a warning, and then investigate how we can improve this rule to better reflect the specification.

Without considering the invalid_phone_number, here is the list of datasets that become invalid with the v3.0.0 and the error that they contain (as of November 10, 2021 - the release is in beta and the work in PR #1044 and #1022 might impact this list).
 The missing_required_file appears twice and it should have been triggered by the v2.0.0 because those datasets are indeed missing required files. There have been modifications in the validator that solved this (good news!)

2. Analyse the state of the validation results on all datasets from the mobility database using validator 3.0.0-beta release
Note that this will be updated after PR #1022  is merged.
2.1 Notices that are present
There are 52 notices present and we have 85 in total
errors:  23 ['invalid_phone_number', 'duplicate_fare_rule_zone_id_fields', 'invalid_date', 'decreasing_or_equal_shape_distance', 'point_near_origin', 'decreasing_or_equal_stop_time_distance', 'duplicate_key', 'stop_time_with_arrival_before_previous_departure_time', 'invalid_url', 'missing_required_column', 'number_out_of_range', 'start_and_end_range_out_of_order', 'missing_trip_edge', 'stop_without_zone_id', 'foreign_key_violation', 'missing_required_file', 'missing_required_field', 'invalid_row_length', 'invalid_color', 'empty_column_name', 'block_trips_with_overlapping_stop_times', 'new_line_in_value', 'missing_level_id']
warnings:  27 ['feed_expiration_date', 'stop_too_far_from_shape', 'leading_or_trailing_whitespaces', 'route_color_contrast', 'stop_time_timepoint_without_times', 'stops_match_shape_out_of_order', 'duplicate_route_name', 'platform_without_parent_station', 'fast_travel_between_consecutive_stops', 'fast_travel_between_far_stops', 'stop_without_stop_time', 'unusable_trip', 'unused_trip', 'non_ascii_or_non_printable_char', 'same_route_and_agency_url', 'unexpected_enum_value', 'stop_too_far_from_shape_using_user_distance', 'route_short_name_too_long', 'route_short_and_long_name_equal', 'same_name_and_description_for_stop', 'missing_feed_info_date', 'same_name_and_description_for_route', 'unused_shape', 'stop_has_too_many_matches_for_shape', 'same_stop_and_agency_url', 'same_stop_and_route_url', 'pathway_dangling_generic_node']
infos:  2 ['unknown_column', 'unknown_file']

2.2 Proportion of datasets with errors / warnings
We decided not to take into account the invalid phone number notice.

2.3 Ten most common errors
We decided not to take into account the invalid phone number notice. For each notice, we calculated the total number of times it is present at least once in a dataset, and the results can be seen below.

2.3 Ten most common warnings

After doing the following:

https://github.com/MobilityData/gtfs-validator/pull/1044
https://github.com/MobilityData/gtfs-validator/pull/1068
https://github.com/MobilityData/gtfs-validator/pull/1062

Here are the updated results:
1- Compare validation reports from v2.0.0 to v3.0.0
1.1 Datasets not supported by v2.0.0: none found
1.2 Datasets not supported by v3.0.0: two found

Tram Train's GTFS Schedule source,
Komunikacja Miejska - Płock's GTFS Schedule source

1.3 Datasets that become invalid with v3.0.0 and why
This time we had 176 datasets that went from valid to invalid when comparing the v2.0.0 release and the most up to date 3.0.0 release we have.
{'empty_column_name': 1,
 'missing_level_id': 1,
 'pathway_unreachable_location': 1,
 'point_near_origin': 2,
 'stop_time_timepoint_without_times': 26,
 'stop_without_zone_id': 158}

The invalid_phone_number isn't appearing anymore which was expected, but we had another surprise here: 🤔  why did the stop_without_zone_id number increase? We didn't touch anything with that rule since the last time we ran this analysis.
After investigation, it seems that this might be related to the dataset version that we were getting from the Mobility Database (fixed in #1050), and that the latest analytics is the source of truth. We also noticed that the validator implementation might be too strict, and issue #1075 was opened to follow up.
If we don't consider the stop_without_zone_id notice (because we think that all of them are false positives), the datasets that become invalid with the 3.0.0 release are:
"Allegany County Transit's GTFS Schedule source": ['stop_time_timepoint_without_times'],
 "Annapolis Transit's GTFS Schedule source": ['stop_time_timepoint_without_times'],
 "BWI Airport Shuttle's GTFS Schedule source": ['stop_time_timepoint_without_times'],
 "Blue Lake Rancheria Transit System's GTFS Schedule source": ['stop_time_timepoint_without_times'],
 "CHT's GTFS Schedule source": ['stop_time_timepoint_without_times'],
 "Calvert County Public Transportation's GTFS Schedule source": ['stop_time_timepoint_without_times'],
 "Carroll Transit System's GTFS Schedule source": ['stop_time_timepoint_without_times'],
 "Charles County VanGO's GTFS Schedule source": ['stop_time_timepoint_without_times'],
 "City of Sierra Vista's GTFS Schedule source": ['stop_time_timepoint_without_times'],
 "CityLink's GTFS Schedule source": ['stop_time_timepoint_without_times'],
 "Clovis Transit's GTFS Schedule source": ['stop_time_timepoint_without_times'],
 "DTC's GTFS Schedule source": ['point_near_origin'],
 "DeKalb Public Transit's GTFS Schedule source": ['stop_time_timepoint_without_times'],
 "Delmarva Community Transit's GTFS Schedule source": ['stop_time_timepoint_without_times'],
 "Downtown Alliance's GTFS Schedule source": ['stop_time_timepoint_without_times'],
 "GATRA's GTFS Schedule source": ['stop_time_timepoint_without_times'],
 "Humboldt County's GTFS Schedule source": ['stop_time_timepoint_without_times'],
 "Kern Transit's GTFS Schedule source": ['stop_time_timepoint_without_times'],
 "LVB's GTFS Schedule source": ['empty_column_name'],
 "MBTA's GTFS Schedule source": ['pathway_unreachable_location'],
 "Ocean City Transportation's GTFS Schedule source": ['stop_time_timepoint_without_times'],
 "Palo Verde Valley Transit Agency's GTFS Schedule source": ['stop_time_timepoint_without_times'],
 "Prince George's County TheBus's GTFS Schedule source": ['stop_time_timepoint_without_times'],
 "Rhody Express's GTFS Schedule source": ['stop_time_timepoint_without_times'],
 "San Miguel Authority for Regional Transportation's GTFS Schedule source": ['stop_time_timepoint_without_times'],
 "Subte's GTFS Schedule source": ['missing_level_id'],
 "TART's GTFS Schedule source": ['stop_time_timepoint_without_times'],
 "TER SNCF France's GTFS Schedule source": ['point_near_origin'],
 "Virginia Regional Transit's GTFS Schedule source": ['stop_time_timepoint_without_times'],
 "Washington County Transit's GTFS Schedule source": ['stop_time_timepoint_without_times'],
 "YARTS's GTFS Schedule source": ['stop_time_timepoint_without_times']

1.4 datasets that became valid with v3.0.0 and why
There are a lot more than in the previous analysis because of the fix done with invalid_phone_number, here are the numbers of datasets that went from invalid with v2.0 to valid with v3.0, and which notice made that change happen:
{'duplicate_fare_rule_zone_id_fields': 1,
 'invalid_phone_number': 59,
 'leading_or_trailing_whitespaces': 71,
 'missing_required_file': 6,
 'same_name_and_description_for_route': 5}

2. Analyse the state of the validation results on all datasets from the mobility database using validator 3.0.0-beta release
Note that this will be updated after PR #1022  is merged.
2.1 Which notices are triggered? Which ones aren't?
There are 54 notices present and we have 85 in total.
Here is the list of notices that are NOT triggered by any dataset with the 3.0 release:
csv_parsing_failed
duplicated_column
empty_file
inconsistent_agency_timezone
invalid_currency
invalid_email
invalid_float
invalid_integer
invalid_language_code
invalid_phone_number
invalid_time
invalid_timezone
location_with_unexpected_stop_time
location_without_parent_station
missing_calendar_and_calendar_date_files
overlapping_frequency
route_both_short_and_long_name_missing
start_and_end_range_equal
station_with_parent_station
stop_time_wit_arrival_before_previous_departure_time
stop_time_with_only_arrival_or_departure_time
translation_foreign_key_violation
translation_unexpected_value
wrong_parent_location_type

2.2 Proportion of datasets with errors / warnings

2.3 Ten most common errors
Note that in this section, a specific error will be counted as “one” if present in a dataset, regardless of the times it’s present in the dataset.

The validator behaviour is probably too strict with stop_without_zone_id and decreasing_or_equal_shape_distance. We believe the number of datasets with error will be cut by two when we fix those two rules.
2.3 Ten most common warnings

Closing this issue - we will be publishing a blog post with an article describing those results :)
Doing this type of analysis really helps to design this validator because it can flag potential false positives, and it's also very useful to measure what is the quality of the GTFS datasets.
If you have any questions or would like to know how to run those types of analyses yourself, please get in touch with us!


Checkbox background color is white on all themes

The checkbox background color stays white (#fff) on all themes and in all variants (default, primary, secondary, etc):

Unchecked checkbox has no background color. Example: https://play.tailwindcss.com/7C2kYPZeOU
are you sure you're not using any other CSS code that might set that color (for example @tailwindcss/forms package)?

Only using these css styles (from the latest stable tailwind version):
@import 'tailwindcss/base';
@import 'tailwindcss/components';
@import 'tailwindcss/utilities';

Maybe the issue is in the latest tailwind, I see also some issues with the default styling of inputs (the Chrome browser puts a blue ring all inputs). For which there's an open pull request.

Can you share your tailwind.config.js file?

Found it, in the tailwind.config.js it included the tailwindforms. Didn't know about about that.

Yup. That applies colors and other styles to all form elements

@saadeghi I just ran into this is well, maybe mention this in the documentation?

It's not even a style from daisyUI. Why should it be in daisyUI docs 😅
It's a style from a different plugin (tailwind forms) and it is mentioned in its repo that it applies styles to all form HTML tags.


feat: change from Load Balancer to Cluster IP

:tada: This PR is included in version 0.2.0-develop.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Fix unit-test CI

Currently the GitHub task that runs the unit tests fails with the message mentioning "error code 143".  This turns out to be an acknowledged problem in GitHub, see https://github.com/actions/runner-images/issues/6680#issuecomment-1335778010
The unit tests pass reliably on "normal" computers.
Perhaps restructuring the GitHub tasks and using Go build tags will address this problem.

This problem occurred when we added the borrowed-from-Ruler tests cl2_test.go and generic_machine_test.go.  So the hypothesis is that these tests pushed the GitHub infrastructure into overload. I can see two ways that this could be addressed:

put those tests in a different package - would want to talk about how to structure folders and so on
put a build tag //go:build fromRuler on those tests, and //go:build !fromRuler on all the others, then have two different GitHub tasks workflows, one with -tags=fromRuler and one without.

As an interim measure I guess I can just put the fromRuler tag on the two files and make a little PR to see whether the in the PR validation, the unit-test step actually passes.  I'll do that.

Yay, #173 seems to fix this.  Now, it does mean that two quite useful unit tests are not being run.  We should probably update the instructions in CONTRIBUTING.md to say "please run unit tests with -tags=fromRuler".
Since the unit-test coverage is still excellent without these tests, I think I'd like to go ahead and merge this, and then file a new issue to figure out how to get these back into the CI.

This is OK with me. We could create a second workflow only running specific go tests (since we can't easily exclude those without build tags). Gets a bit tricky if we change the tests in fromRuler, but better than not running them at all IMHO.


add ChakraCoreWindows.h to nuget include path

Header for Windows specific JSRT APIs, currently needed for JsConnectJITProcess

LGTM


Terrain skirts are causing artifacts in terrain shadows

When terrain shadows are enabled, the skirts contribute in casting shadows causing shadows artifacts.

This is better visible when the light source is tangent to surface (e.g. it is near the horizon).
I'm attaching a simple sandcastle example for demonstrating the current behavior: advance the time through the timeline for seeing the shadows artifacts caused by the skirts. Disabling the terrain skirts gets rid of some of those artifacts, but that of course has some other bad side effects, e.g. worse tiles edges connection

Sandcastle example:
Sandcastle
Ideally, I solid shadow should be casted when the light is low and the light source is occluded by a skirt "wall". Something like in the following animation

Browser:
any
Operating System:
any

Thanks for pointing this out @calogeromauceri!
We're reviewing your suggested fix in https://github.com/CesiumGS/cesium/pull/11460.


Check to see if new key for Stripe is needed

Created a Stripe account. I was given two keys:
a public key that I have to use it in the index file in the Cart.
a secret key that I have to use it in the resolvers file.


Is it possible to run a music / sounds generation model?

Question
I'd love to create a browser-based music generation tool, or one that can turn text into sound effects. Is that supported?
I guess my more general question is: can Transformers.js run pretty much any .onnx I throw at it, or does each model require some level of implementation before it can be used?

Well would you look at that plot thickening: https://huggingface.co/Xenova/musicgen-small
Except.. that the repo was created a day ago. Whoa.

Yep! Somehow your feature request came at the perfect time! This is something I've been working on already for a few days. This is all now possible thanks to this PR by @fxmarty.
Stay tuned for updates! This might only be available in v3 due to WebGPU support (I think CPU/WASM-only will be too slow).

I did not implement it in the PR yet, I'll maybe do it with ONNX Runtime (patching some transformers methods to use ORT instead of torch)

I have no idea what that means, except that I should be patient :-)

Whoop! https://github.com/xenova/transformers.js/pull/545#issuecomment-2041205108

It's now possible! e.g. https://flatsiedatsie.github.io/transformers_js_musicgen/


added zenodo badge to readme.

Please check if the PR fulfills these requirements

[x] This PR addresses an already opened issue (for bug fixes / features)
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, etc.)
Added zenodo DOI badge.

Fixes #185

Pull Request Test Coverage Report for Build 767

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 91.366%

Totals

Change from base Build 755:
0.0%

Covered Lines:
1217

Relevant Lines:
1332

💛  - Coveralls


Fix the way cross-site cookies work using the Domain attribute

The issue is that the Heroku web app throws an Cookie “drecruit-session” has been rejected for invalid domain. error.

Done in 30ad22e8b0b84a4c7d363fea00c672a2b8d83359


Adds proto3 encoding

Note: Zipkin server 2.8+ is required to be running for this to work.

tested by setting "spring.zipkin.encoder=PROTO3" in https://github.com/openzipkin/sleuth-webmvc-example using this build. The spans sent were half the size as usual.

Codecov Report

Merging #962 into master will decrease coverage by <.01%.
The diff coverage is 66.66%.

@@             Coverage Diff              @@
##             master     #962      +/-   ##
============================================
- Coverage     71.25%   71.25%   -0.01%
- Complexity      628      629       +1
============================================
  Files           121      121
  Lines          2794     2797       +3
  Branches        289      291       +2
============================================
+ Hits           1991     1993       +2
  Misses          626      626
- Partials        177      178       +1

Impacted Files
Coverage Δ
Complexity Δ

...loud/sleuth/zipkin2/sender/RestTemplateSender.java
62.22% <66.66%> (+0.31%)
10 <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 3e48dec...8543095. Read the comment docs.


ERROR: Head "https://ghcr.io/v2/nsarrazin/serge/manifests/latest": unauthorized

any solution ?

@EvilzCoder edit docker-compose.yml serge image location to ghcr.io/serge-chat/serge:latest

Thanks
PR


2-way TLS throwing bad cert on consul

Hi
I have Consul (0.9.3) as a service/discovery utility for the spring boot micro-services. I was able to enable TLS 1-way, i.e. consul -> microservice.
For that, my consul.json reads:
{
	"ca_file": "C:\\ca.cer",
	"verify_outgoing": true
}

Spring boot configuration reads:
server:
  port: 443
  ssl:
    key-store: C:\spring.p12
    key-store-password: changeit
    key-store-type: JKS

The above works well.
But the moment I try the 2-way, it gives me bad cert on consul logs, empty chain at spring boot application logs. Here is the configuration:
consul.json
{
	"ca_file": "C:\\ca.cer",
	"verify_outgoing": true,
	**"cert_file": "C:\\consul.cer",
        "key_file": "C:\\consul.key",
	"verify_incoming": true**
}

application.yml on spring boot app.
server:
  port: 443
  ssl:
    key-store: C:\spring.p12
    key-store-password: changeit
    key-store-type: JKS
    **trust-store: C:\spring-ts.p12
    trust-store-password: changeit
    trust-store-type: JKS
    client-auth: NEED
    enabled: true**

Any reason why the consul agent is not able to pass the certs to the server?

Please learn how to properly format code and logs.
Can you share the error and when exactly is consul contacting the service?

Consul agent pings the microservice every 30 sec on HTTPS and fails as the 2-way is not working. This works with 1 way though as I mentioned in my initial comment.
Here is the error.
  Rethrowing javax.net.ssl.SSLHandshakeException: null cert chain
https-jsse-nio-443-exec-4, called closeOutbound()
https-jsse-nio-443-exec-4, closeOutboundInternal()

I don't think this has anything to do with Spring Cloud Consul, do you? The ssl configuration is all spring boot and consul.

Well I think the consul agent is not able to present its certs to the service, which is why the certificate chain is empty. The configuration seems good and as per the documentation.

Again, consul agent-> spring boot. This project is not involved there. I'm going to close this. Feel free to reopen if you can show there is a bug in this project.


Update AWS commands SEO pages

Based on feedback provided by Aaron, update the AWS commands SEO pages
https://github.com/pulumi/pulumi-hugo/pull/3775
https://github.com/pulumi/pulumi-hugo/pull/3776

PRs merged last week.


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update readme file

I would like to update the readme by adding some badges. It will look cool

Hey @charu1603 you can update it


Add field to include CC types of licenses

We would ease people.minting with some sort of licences for CC to be easier, with all respect we should add cc4.0 &c and include it into metadata under Copyright field
Can expand on this later
We can test this on minting tetrix stuff
With composable licensing, this will get bit complex.
Metadata and on-chain data can have different license
Questions are
remix/mashups licensing etc

stale


Add function to control sleep activation mode for havok physics

https://github.com/BabylonJS/Babylon.js/issues/14810

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/14816/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14816/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14816/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/14816/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/14816/merge
https://gui.babylonjs.com/?snapshot=refs/pull/14816/merge
https://nme.babylonjs.com/?snapshot=refs/pull/14816/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/14816/merge#BCU1XR#0

WebGL2 visualization test reporter:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14816/merge/testResults/webgl2playwright/index.html

Visualization tests for WebGPU (Experimental)
Important - these might fail sporadically. This is an optional test.
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14816/merge/testResults/webgpuplaywright/index.html

Adding a fix
I'm not sure I can add a "new feature" label myself
Test playground: https://playground.babylonjs.com/#Z8HTUN#880 (the sphere should stay red)

Visualization tests for WebGPU (Experimental)
Important - these might fail sporadically. This is an optional test.
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14816/merge/testResults/webgpuplaywright/index.html

#Z8HTUN#880

The sphere does stay red in the snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/14816/merge#Z8HTUN#880
Please ignore the WebGL2 tests, there is still a formatting issue that needs to be resolved.

WebGL2 visualization test reporter:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14816/merge/testResults/webgl2playwright/index.html

Visualization tests for WebGPU (Experimental)
Important - these might fail sporadically. This is an optional test.
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14816/merge/testResults/webgpuplaywright/index.html


react-native-git-upgrade illegal operation on a directory, read

Running react-native-git-upgrade errors with illegal operation on a directory, read
$ npm install -g react-native-git-upgrade
+<EMAIL_ADDRESS>
$ react-native-git-upgrade
git-upgrade info Check for updates
git-upgrade info Using yarn 1.10.1
git-upgrade info Read package.json files
git-upgrade info Check declared version
git-upgrade info Check matching versions
git-upgrade info Check React peer dependency
git-upgrade info Check that Git is installed
git-upgrade info Get information from NPM registry
git-upgrade info Upgrading to React Native 0.59.5, React 16.8.3
git-upgrade info Setup temporary working directory
git-upgrade info Configure Git environment
git-upgrade info Init Git repository
git-upgrade info Add all files to commit
git-upgrade info Commit current project sources
git-upgrade info Create a tag before updating sources
git-upgrade info Generate old version template
git-upgrade ERR! An error occurred during upgrade:
git-upgrade ERR! Error: EISDIR: illegal operation on a directory, read
    at Object.readSync (fs.js:491:3)
    at tryReadSync (fs.js:330:20)
    at Object.readFileSync (fs.js:367:19)
    at ConfigChainBuilder.addConfig (/Users/user1/.nvm/versions/node/v10.14.1/lib/node_modules/react-native-git-upgrade/node_modules/babel-core/lib/transformation/file/options/build-config-chain.js:146:32)
    at ConfigChainBuilder.findConfigs (/Users/user1/.nvm/versions/node/v10.14.1/lib/node_modules/react-native-git-upgrade/node_modules/babel-core/lib/transformation/file/options/build-config-chain.js:102:30)
    at buildConfigChain (/Users/user1/.nvm/versions/node/v10.14.1/lib/node_modules/react-native-git-upgrade/node_modules/babel-core/lib/transformation/file/options/build-config-chain.js:61:13)
    at OptionManager.init (/Users/user1/.nvm/versions/node/v10.14.1/lib/node_modules/react-native-git-upgrade/node_modules/babel-core/lib/transformation/file/options/option-manager.js:354:58)
    at compile (/Users/user1/.nvm/versions/node/v10.14.1/lib/node_modules/react-native-git-upgrade/node_modules/babel-register/lib/node.js:103:45)
    at loader (/Users/user1/.nvm/versions/node/v10.14.1/lib/node_modules/react-native-git-upgrade/node_modules/babel-register/lib/node.js:144:14)
    at Object.require.extensions.(anonymous function) [as .js] (/Users/user1/.nvm/versions/node/v10.14.1/lib/node_modules/react-native-git-upgrade/node_modules/babel-register/lib/node.js:154:7)
git-upgrade ERR! Restore initial sources
Note: checking out 'project-snapshot'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at b2eda88... Project snapshot

To Reproduce
See above
Expected Behavior
Expected it to work
Environment
$ react-native info

  React Native Environment Info:
    System:
      OS: macOS High Sierra 10.13.6
      CPU: x64 Intel(R) Core(TM) i5-4260U CPU @ 1.40GHz
      Memory: 305.69 MB / 8.00 GB
      Shell: 3.2.57 - /bin/bash
    Binaries:
      Node: 10.14.1 - ~/.nvm/versions/node/v10.14.1/bin/node
      Yarn: 1.10.1 - /usr/local/bin/yarn
      npm: 6.4.1 - ~/.nvm/versions/node/v10.14.1/bin/npm
    SDKs:
      iOS SDK:
        Platforms: iOS 11.4, macOS 10.13, tvOS 11.4, watchOS 4.3
    IDEs:
      Android Studio: 2.3 AI-162.3871768
      Xcode: 9.4.1/9F2000 - /usr/bin/xcodebuild
    npmPackages:
      react: ^16.7.0 => 16.7.0
      react-native: 0.57.0 => 0.57.0
    npmGlobalPackages:
      react-native-cli: 2.0.1
      react-native-git-upgrade: 0.2.7

I am going to ignore that message for obvious reasons.

👋 @AJamesPhillips. Thanks for reporting this.
react-native-git-upgrade has actually been deprecated and replaced with react-native upgrade from 0.59 onwards. To upgrade to that version, I recommend you take a look at the diffs in the rn-diff-purge repository. The one you need is here:
https://github.com/react-native-community/rn-diff-purge/compare/release/0.57.0..release/0.59.8
If you follow the diff and make the changes manually this time, you will be able to use the new upgrade command from 0.59 onwards.
More details about the upgrade process can be found here:
https://facebook.github.io/react-native/docs/upgrading

@kelset Should we keep this open to look into the issue with react-native-git-upgrade or close it?

No, let's close it. react-native-git-upgrade has been "dead" for some time now (we have been saying it both in issues and in the blogposts), so there is nothing actionable.
@AJamesPhillips I'm sorry you have been experiencing pain in upgrading, and I can tell you that we know this has been a long lasting pain for the community so starting v0.59 we have introduced a new flow via the new CLI. So hopefully following @matt-oakes's approach (which is the one I do every time) you'll be able to overcome your issues 🤗


fix: Fix typo

📝 Docs preview for commit 404e63b73fbf7a2e10a95deb2f1dfcbc643a23eb at: https://d650be31.fastapitiangolo.pages.dev

Thanks @hugo-syn! 🍰
This was covered by https://github.com/tiangolo/fastapi/pull/10809, so I'll now close this one.
Thanks for the help, everyone! ☕


trendline options None not works.

Description
using parameter,
px.scatter trendline None  not work.
other lowess, ols works.
Expected behavior
No response
Which package?
vizro
Package version
'0.1.16'
Python version
3.11.5
OS
window
How to Reproduce
yearly_groups = df_korea.groupby(df_korea.index.year)
data = yearly_groups[['Magnitude']].count()
fig = px.scatter(data_frame=data,trendline=None)
fig.update_layout(width=800, height=600)
fig.show()
default trendline is None.
but
page_World_Year = vm.Page(
id="World Year",
title="Year",
components=[
vm.Graph(id="year_world", figure=year_w),
],
controls=[
vm.Parameter(
targets=["year_world.trendline"],
selector=vm.Dropdown(
options=['lowess', 'expanding', 'ols', None],
multi=False,
value='ols',
))
]
)
it doenst work.
---------------------------error message----------------------
ValidationError: 17 validation errors for Dropdown
options -> 0
value is not a valid boolean (type=value_error.strictbool)
options -> 1
value is not a valid boolean (type=value_error.strictbool)
options -> 2
value is not a valid boolean (type=value_error.strictbool)
options -> 3
none is not an allowed value (type=type_error.none.not_allowed)
options -> 0
value is not a valid float (type=type_error.float)
options -> 1
value is not a valid float (type=type_error.float)
options -> 2
value is not a valid float (type=type_error.float)
options -> 3
none is not an allowed value (type=type_error.none.not_allowed)
options -> 3
none is not an allowed value (type=type_error.none.not_allowed)
options -> 0
invalid date format (type=value_error.date)
options -> 1
invalid date format (type=value_error.date)
options -> 2
invalid date format (type=value_error.date)
options -> 3
none is not an allowed value (type=type_error.none.not_allowed)
options -> 0 -> root
OptionsDictType expected dict not str (type=type_error)
options -> 1 -> root
OptionsDictType expected dict not str (type=type_error)
options -> 2 -> root
OptionsDictType expected dict not str (type=type_error)
options -> 3
none is not an allowed value (type=type_error.none.not_allowed)
I think,
through  print(fig),
i can find that,
except trendline=None,
all trendline option append new data to input data.
Output
No response
Code of Conduct

[X] I agree to follow the Code of Conduct.

Hello @hwoarang09, the right way to enter None as an option is to use the string "NONE": https://vizro.readthedocs.io/en/stable/pages/user-guides/parameters/?h=none#basic-parameters.
So you would do this:
selector = vm.Dropdown(
    options=["lowess", "expanding", "ols", "NONE"],
    multi=False,
    value="ols",
)

Does that achieve what you're looking for?

@antonymilne
Thank you.!! it works.
i have some question about vizro...

in vm.Card, i want blank line. like  or \n\n
i tried several things, but it didnt' work...

is there any function that filter index, not columns.
filter, parameter, ...anything.
i think i should use parameter with target data_frame... and option with different premade dataframe.
Thank you.!!

Hey @hwoarang09,
Good to hear! 🎉

If you provide an empty line, it will automatically add space between the following line. If you want an additional blank line, you must use &nbsp. The Card.text is based on markdown, so referencing the markdown syntax of adding blank lines should work 👍

It would look like this:
Example
import vizro.models as vm
from vizro import Vizro

page = vm.Page(
    title="Card",
    components=[
        vm.Card(
            text="""
        # Heading

        This is a paragraph that starts on a new line.

        Here is another paragraph.

        The ` ` followed by a blank line gives a blank line.
        """
        )
    ],
)

dashboard = vm.Dashboard(pages=[page])

if __name__ == "__main__":
    Vizro().build(dashboard).run()

To be clear, would you like to filter the data frame provided to the charts via a row index instead of a column value? If yes, I think the simplest way of doing that is to create a column with row indexes and then continue using the Filter on that column.

Hope that helps! 🤞

oh....make column with index value...good. Thank you!!

Thank you for the questions @hwoarang09 - closing this as completed now but please do raise another issue if you have any more questions!


Question

I have a question, why do you populate the $_SERVER ? Is there a specific reason for this?

Because in PHP, ENV variables end up in both $_ENV and $_SERVER.

aah ok, didn't know that... Thanks


fix: correctly check dry-run requests

In the pod eviction admitter some dry run requests were not caught due to KubeVirt only checking the dry-run field in the admission review but not in the object contained in the admission review.
This was causing dry run requests made through kubectl drain using the '--dry-run=server' flag to be processed as non dry-run requests.
It's possible that this is Kubernetes bug but it should be anyway fixed fixed in the meantime.

What this PR does
Before this PR:
dry run requests made through kubectl drain using the '--dry-run=server' flag are processed as non dry-run requests
After this PR:
dry run requests made through kubectl drain using the '--dry-run=server' flag are processed correctly

Fixes #
Why we need it and why it was done in this way
The following tradeoffs were made:
The following alternatives were considered:
Links to places where the discussion took place:
Special notes for your reviewer

Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note

NONE

/cherrypick release-1.3

/cherrypick release-1.2

/cherrypick release-1.1

/hold
Failures are relevant

/lgtm

/unhold

/retest


Create wheels on Azure

This PR uses a plugin cibuildwheel to build the binary wheels for manylinux and macos on Azure DevOps. The main contribution is our manylinux wheel hasn't been built with azure until now.
Note I kept all of the old pipeline for building and unit testing as it submits coverage and displays the test results in Azure. The new way uses docker compose on linux to build the manylinux wheel and it doesn't seem easy to directly upload the coverage or test results from within the container.
A couple of follow on changes would be good:

The unit test job could depend on and use the wheels built in the newly added stage - or the coverage & test results from the wheel testing could be exported.
A release pipeline should be created to publish the wheels to pypi on tagged commits.

@gusmith thanks for the review.
I've made a template which seems to work okay. Let me know if you can see how to improve it. I'm guessing the strategy.matrix could be used to simplify further?


The train's speed can't be a custom number.

Is your feature request related to a problem? Please describe.
The train's speed can't be a custom number.
Describe the solution you'd like
When we click on a siding of a depot, we can edit both the train's max speed and the acceleration.
If max speed is greater than rail's speed, the train's speed will be the rail's speed.
If max speed is smaller than rail's speed, the train's speed will be that max speed.
Additional Information
No.

A better solution might be: add an "unlimited" rail and configure the maximum speed of the train (in the resource pack or in the siding screen). The existing tracks serve as speed limits. Take the minimum value of the speed-limited track and train maximum speed as the actual train speed.


Review Ticket 6

JavaScript Notebook
Group Project Plan/methodology
SubMenu
javaScript Fragments

Grade: 2.7+
I think Luka deserves a 2.7, he completed all the tasks that were required of him and I like the way he personalized his flask page, I would recommend expirementing with color and other features not just images and text otherwise, good job, cant wait to see how you will improve your site next week

Added something that looked like JavaScript menus, but does not stay.  Added lot of nice visual.  Flask same with visuals and added about me.   JavaScript notebook had minor customizations.
2.7

Fastpages submenu and JavaScript table present
Scrum team planning and collaboration
Customization to local flask home and stub

Had everything and it looked good. 2.7+

2.7, I like how you learned more outside of the javascript tutorial, you et all the requirements

2.7, I liked how you customized your javascript notebook and how you changed the name from stub to about me in your python flask.


Announcement: Project maintainer on vacation

Hi everyone!
Just a heads up that I will be traveling on vacation for the next two weeks. I'll still pop in from time to time and try to address any new issues, but it may be days, or even a week, before I'm able to respond. Development will certainly be slow, if at all existent, during this period. I will resume my regular activity on July 25th. Now, it's time for me to get some REST and relaxation. See what I did there? ;)
Take care!

Should be closed now ? :)


Grafana OCI Metrics plugin page actually has information for Logging

https://grafana.com/grafana/plugins/oci-metrics-datasource
This page explains how to set up the policy for reading logs, not metrics. Please fix it.

Thanks for pointing out

this issue is resolved, so closing.


feat: http template for Quarkus stack

resolves #31

@lkingland note that this won't work yet, since buildpack is to picky and won't build funqy-http (it accepts only funqy-knative-events).

Gotcha. Thanks for the note. We can at least have the template writing part working with that caviat emptor

Now that updated buildpacks have been released this should work.


Toggle button on Qute editor to enable/disable validation

It should be nice to provide a toggle button on the the top right of the editor to enable/disable validation.
We need to know the validation state (eabled or disabled?) of the opened template, and it will require to implement a custom command on Qute LS side. The state of the button will be synchronized with the vaidation state.
Click on button will active/desactive the validation for the Qute template. In other words it will update:

qute.validation.enabled to true in the workspace folder scope
remove the template from qute.validation.excluded pattern.

For getting the validation state of a given template, we must implement an IDelegateCommandHandler like https://github.com/redhat-developer/quarkus-ls/blob/76ab820fd35fa30a9996d460a8f15dd4392b1bc3/qute.ls/com.redhat.qute.ls/src/main/java/com/redhat/qute/services/commands/QuteGenerateCommandHandler.java#L31 on Qute LS side.
This command could returns a boolean or perhaps the settings which says why a qute template validation is disabled?

https://code.visualstudio.com/api/references/when-clause-contexts#check-a-setting-in-a-when-clause may be useful if you need to use 2 commands that have enablement criteria (eg. when caluse) that are negations of each other. You can also set a custom context.


V2 - Project Console - Not able to delete github repositories or github organizations

Observed 400 is returned when trying to delete github repositories or github organizations. Observed same issue from UI as well
Deletion of github repository

Deletion of github organization

UI

@nirupamav this regression was a result of changing the repository delete logic to be an update call - where we instead of deleting the repo we actually just disable it.
Created PR: https://github.com/communitybridge/easycla/pull/1688

Resolved DB update syntax error
Refactored repositories table API and DB logic - renamed service and DB functions, added enabled/disabled options. Changed deleted to disabled. General API cleanup.

If possible, can you perform a thorough review of the repository add/delete logic from both v1 and v2? I have updated many files to clean up the API and the database logic.

Merged PR.  Pushing to DEV.

Verified that able to delete Github repo and github org. Will perform regression and log new tickets for any regression issues. Closing this ticket as the actual issue is fixed


Updated TinyUmbrella to version <IP_ADDRESS>

Fixes #10221.
I used the app-only download. At the moment download links are not handled in a clever way, so for now the url does not contain the version tag. I also did not add a license, because notcom does not provide one.

Why is this new url better? We seem to simply lose the benefit of a clear versioning and gain nothing.

Seeing as url doesn’t point to a specific version, this cask should use version :latest and sha256 :no_check. See an example.

Looks good, could you please squash your commits?
Please @mention me after you do, so I get a warning to check back.

Thank you for the contribution. It needed some fixes, so they were made in the below referenced pull request. Your contribution is still included (and still credited to you), with the appropriate modifications. Please feel free to ask about any of the changes.


JingetMessageBox needs to have async verbose func

In JingetMessageBox the ShowVerboseFunc property needs to be async

resolved in v6.2.0-preview006


feat: sqlalchemy integration

Hey @matveypashkovskiy & @alexey-vyskubov
Here's a version that uses SQLalchemy core. The entire test loop is bundled into a single transaction and primary keys of entries are kept in a dictionary during the run so they're not queried during every test function. Some column names are changed to be more descriptive. Also there were some cases where a source code file was inserted into the mapping database without any coverage and I removed that "feature". Otherwise the mapping database contains the same items. My optimizations helped a little but the performance is significantly worse than in master, taking 1.5x time in pandas/tests/arithmetic compared to current master.
I had to do some refactoring as well to make pylint happy. There's still some weird bug that I can't figure out with tox. After adding a missing __init__.py to pytest_rts/tests/, the pytest run with tox won't pass but works without it. It's complaining that pytest_rts.tests doesn't exist. Maybe you have some idea why that is happening.

A question: how "1.5x time worse" figure was obtained? Was it a single run of all tests from pandas/tests/arithmetic or was it, say 10-20, runs and then mean was selected? Sometimes the second approach shows more realistic results. The same question applies to the performance of code from the master branch.

README.md needs some extra sentence about --rts-db-conn option

Force pushed to fix pytest error with tox and change mapping database column names as they are in master.

Now that I'm working on preparing a demo with pandas I remembered that also the "Update phase" for committed changes suffers from the slowdown that collecting coverage produces. It has slipped my mind during our discussions.

indeed, let's look at pytest-cov database as the next step


LaneDetection and Postprocessing in Apollo 5.0

Hello,
I am trying to understand the LaneDetection and Postprocessing in Apollo 5.0. But not finding any documents which explain this.
Which code to refer to? Is it this one?
What is darSCNN and denseline?
Please guide me!

There is no official document at the moment, I found some information you can refer to.

denseline

In apollo 3.5, the object and the lane line detection network are completely separated, and the lane line model is called denseline

darSCNN

DarkSCNN model, which is based on the backbone Darknet in Yolo and introduces Spatial CNN

Thank you @daohu527

Hello,
How do I understand the working of Lane Detection and Tracking of Apollo 5.0.
I can see that it uses darkSCNN model. But could not understand the working.
Can you help!!


[SPARK-28756][R] Fix checkJavaVersion to accept JDK8+

What changes were proposed in this pull request?
Currently, checkJavaVersion only accepts JDK8 because it compares with the number in SystemRequirements. This PR changes it to accept the higher version, too.
Why are the changes needed?
Without this, two test suites are skipped on JDK11 environment due to this check.
BEFORE
$ build/mvn -Phadoop-3.2 -Psparkr -DskipTests package
$ R/install-dev.sh
$ R/run-tests.sh
...
basic tests for CRAN: SS

Skipped ------------------------------------------------------------------------
1. create DataFrame from list or data.frame (@test_basic.R#21) - error on Java check
2. spark.glm and predict (@test_basic.R#57) - error on Java check
DONE ===========================================================================

AFTER
basic tests for CRAN: .............

DONE ===========================================================================

Does this PR introduce any user-facing change?
No.
How was this patch tested?
Manually, build and test on JDK11.

Test build #109197 has started for PR 25472 at commit 9a3553c.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/14267/
Test PASSed.

Test build #109198 has started for PR 25472 at commit 50f9615.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/14268/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/14273/
Test PASSed.

Test build #109203 has started for PR 25472 at commit 68b0112.

Test build #109203 has finished for PR 25472 at commit 68b0112.

This patch fails R style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/109203/
Test FAILed.

Test build #109197 has finished for PR 25472 at commit 9a3553c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/109197/
Test PASSed.

Test build #109198 has finished for PR 25472 at commit 50f9615.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/109198/
Test PASSed.

Hi, @HyukjinKwon , @srowen , @felixcheung .
Could you review this PR for JDK11 support?

Thank you for review, @HyukjinKwon . I updated the PR.

Test build #109212 has started for PR 25472 at commit d15bd85.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/14282/
Test PASSed.

Test build #109212 has finished for PR 25472 at commit d15bd85.

This patch fails R style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/109212/
Test FAILed.

Test build #109214 has started for PR 25472 at commit 22e11b2.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/14283/
Test PASSed.

Test build #109214 has finished for PR 25472 at commit 22e11b2.

This patch fails R style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/109214/
Test FAILed.

Retest this please.

retest this please

Retest this please.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/14287/
Test PASSed.

Test build #109220 has started for PR 25472 at commit 4531ced.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/14298/
Test PASSed.

Test build #109220 has finished for PR 25472 at commit 4531ced.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/109220/
Test PASSed.

Thank you, @HyukjinKwon and @srowen .
Merged to master.

Note: this is likely going to cause CRAN release to be rejected as CRAN tests run on the latest JDK (like JDK 12)
Also paste() adds spaces between strings so it will add a space before the comma in ", or greater, is required...

Hm, does CRAN counts SystemRequirements? I thought it's just additional metadata. Let me clarify the upper bound as well.
paste(), yes, seems it has to be fixed.

Thank you, @felixcheung ! Got it.

For paste, I'll do follow up .
For SystemRequirements: Java (>= 8), I'll revisit this in this week after the master branch starts to support JDK11 officially~

Actually, I was checking SystemRequirements out of curiosity and made a followup while I am here.

We also found SystemRequirements didn’t work - it didn’t prevent CRAN from running tests on JDK > 8

Hm, OK this may have to be reverted. After all, it's fine for CRAN to verify on Java 8. The build still works on Java 8 of course.


How destroy instance?

Read comment.

Hi, im using markdown-it inside vue component, which placed inside modal, so, it's creating on each click new instance of component -> new instance of mardown-it.
https://hastebin.com/jifuxalagu.xml - component (read comment on destroyed event),
https://hastebin.com/opekicenux.js - additional link attributes.

I didn't found it inside prototypes.
Is this.md = undefined - enought?
@puzrin - ping
И нужно ли вообще здесь destroy, или gc думаете почистит потом это все? (Просто я не уверен с текущими имплементациями браузеров)

JS uses gc, no destroy needed. That's a generic thing, not specific to this package.

;(
That's not nice.
Every package have destroy method. So, ok.


Failed to minify the code

First, let me say what a great library.  It has been a blessing to use it.  Unfortunately, I had to upgrade to 4.0.0-rc5 from 3.2.2 that solved an issue, but when doing a react-scripts build, I get an error as follows:
Creating an optimized production build...
Failed to compile.
Failed to minify the code from this file:
./node_modules/reconnecting-websocket/dist/reconnecting-websocket.mjs:1

I've encountered this once before with another library and I just had to import an ES5 compliant version.  Was wondering what I need to do for this library.
Thank you!

Same here, no './node_modules/reconnecting-websocket/dist' directory indeed.

Next version will target ES5 so you shouldn't have these problems


Tag patch versions

Only major and minor version releases seem to be tagged on github. I'm trying to build a conda recipe which would build every new patch version, so having a patch version tagged is useful.

Including this here for situational awareness.

Oh dang you're right. I just added a tag for v1.1.1 and will tag patch versions properly in the future.

Sounds good. Feel free to close this if it makes sense!


Increase MAX_REQUEST_OBJECTS

Hi,
500 seems kinda low for certain usecases. Would it be possible to increase it to 1000 or maybe even more. (with computers these days, it shouldn't really be that big of a problem for those)
Cheers,
thibault

Even 1000 would be great!


[New Website] Wrong NO. in steps

@BewareMyPower has reported this issue:
I found another bug of the new website again.:wink: See the following screenshot (https://pulsar.apache.org/docs/next/schema-understand). The indexes should be 1,2,3, not 1,11,16.
In other tab pages, the indexes are 1,9 and 1,11,17. It looks like a problem related to the Markdown rendering.

I've found with Github Flavored Markdown / CommonMark that you will get proper renumbering if and only if you indent your code examples three spaces. (I'm not sure what flavor of Markdown is used by Docusaurus.

The example box numbering with the copy icon is getting in the way of the steps. This markdown with html does not seem to be compatible with Docusaurus 2.


Works with recent beet version, basic http auth support

Hi, I wasn't able to use it with beet 1.4.5, now it's working. Also, in order to prevent having my music public on the internet I added a basic HTTP auth support.
Code quality is low, it's just an hack to get it working, if you are still using it you might use some code

Woop woop cool! will look over it tomorrow :) Looks like there is actually some interrest in the music-cyclon app.
And actually I see a usage again in my day-to-day use :)

A couple of comments: the password storage is unsafe (and the input is plain text), I'm passing username/password around and maybe a class "Account" would be cleaner. The library subfolder customization is untested. Right now I'm creating the output dir as /$library/$artist/$title_$id.$(lowercase(extension)), I don't know if it's possible to ask beets for a filename (and probably the string must be converted into a path to fix encodings). Also, I'm removing duplicates from the download list because it happened to me that it was trying to download 10 times the same 10 songs. The list -> set -> list thing I'm doing is stupid, it might word using a set by default.

PS: thanks for the app, that has a clean code. I'm not a java dev but it took me a really short time to fix problems and adding things :)

Also bump the app version so fdroid can update the app :)

I'll fix those in a new commit and squash everything after the review

@nico202 Ok, but dont squash everything. Squash commits that belong together

Btw does the integration with the beets server still work? :P Can't test it right now, maybe in the evening

Btw does the integration with the beets server still work? :P Can't test it right now, maybe in the evening

You mean "does it sync"? The answer is "now yes".
Can't get input type to be a password, fixed other things, let me know what's missing

Just tested it, works good :) Thanks

Fine, small refactor done, thanks!

Perfect! Can you tag the release? :)

Will do when I push the update to fdroid. Btw if you are interrested in supporting another open source project take a look at  https://integreat-app.de/en/
We just won the Google Impact Challange :)

@nico202 I opened a MR for fdroid: https://gitlab.com/fdroid/fdroiddata/merge_requests/3277


Fix encoding in read_annotations_edf

Reference issue
N/A
What does this implement/fix?
The encoding argument was not passed to x.decode() when loading annotations from an EDF file

Thanks for the quick review @larsoner!
I can take a shot at adding a test, is there an boilerplate EDF file with an annotation that you typically use for these small tests?

I would try one from test_annotations like
https://github.com/mne-tools/mne-python/blob/53636038c463cfb13c2fc9c7b072f14fc30930e6/mne/tests/test_annotations.py#L408
Hopefully copying it to a tmp_path and modifying it in place to have UTF8 or some other encoding could work. Or even better use whatever character your problematic file actually has that inspired the fix!

@larsoner I found test_read_latin1_annotations in test_edf.py and added a section to test directly reading from a file


openssl speed fixes and documentation updates regarding legacy provider

This addresses the warnings I noticed in `openssl speed' and reported in #11650.
I also added a note about the "legacy provider" to the EVP_$hash(3) man page.

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

Merged. Thanks!


Typo on virtualNetworkingSubnetId note

It should be "/subscriptions/…" instead of "subscriptions/..."

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

ID: babaec3b-2c19-c6e2-835c-166cb528b222
Version Independent ID: a905991a-70b0-7842-d12e-37b484a1f99a
Content: Virtual Network service endpoints - Azure Event Hubs
Content Source: articles/event-hubs/event-hubs-service-endpoints.md
Service: event-hubs
GitHub Login: @ShubhaVijayasarathy
Microsoft Alias: shvija

@c4rlosmarin Thanks for the feedback and bringing this to our notice. At this time we are reviewing the feedback and will update the document as appropriate.

@c4rlosmarin Thank you so much for bringing this out notice. We greatly appreciate your feedback.
The PR for the fix has been created and it will be merged soon. Thanks again for pointing this out, I am closing the issue based on this update, please let us know if there is something else that we can help you with.


[TEMP] Demonstration of including href directly in components

The Device schema specifies that the project and hardware_reservation properties
are Hrefs.  With the current generator configuration, that means the Project and
HardwareReservation properties are inaccessible even if we add include parameters
to the device request.  (Even with fully OpenAPI spec-compliant code, the Project
and HardwareReservation properties would be accessed via Href additionalProperties
given the current upstream spec, so changing code generation is of minor benefit
here.)
This patches the Device schema so that the project and hardware_reservation
properties are specified as instances of the correct model schema, rather than as
Hrefs.

Taking this out of draft so that it can be reviewed in order to move forward with metal-go adoption in other tools.  IMO the usage laid out in this PR is much better than the alternative of using the HrefOrModel pattern everywhere.
The api_href code was a proof-of-concept to explore options for hydrating an href without using an include, and will be broken out into a separate draft PR.


Revert "New features"

Reverts EFranklyn/semantic-release#4

:tada: This PR is included in version 0.0.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Rename DevFile to Devfile everywhere in the code.

What does this PR do?
This PR ensures that every variable having the name devfile does not contain a capital F for the devfile word. The only two exceptions are the func SelectDevFileFromTypes and func SelectDevfilesFromTypes which remain the same. A deprecation warning has been added in the code. Soon they will have to be removed in favor of recognizer.MatchDevfiles which additionally includes devfileFilters in order to filter the fetched stacks from the registry.
Along with code updates, changes were made in the tests and in the documentation.
Which issue(s) does this PR fix
fixes https://github.com/devfile/api/issues/1173
PR acceptance criteria
Testing and documentation do not need to be complete in order for this PR to be approved. We just need to ensure tracking issues are opened.

[x] Unit/Functional tests

[x] Documentation

How to test changes / Special notes to the reviewer

As the PR is not introducing any new features is good to be merged. For the code coverage warnings I've added a new issue here: https://github.com/devfile/api/issues/1218

FYI, this PR introduced breaking changes by renaming the exported model.DevFileType type (part of the Alizer API) into model.DevfileType.
I was wondering why a minor bump of Alizer from 1.0.1 to 1.2.1 (https://github.com/redhat-developer/odo/pull/7126) was not compiling, and it appears it was due to this refactoring.
go install -mod=vendor -ldflags="-X github.com/redhat-developer/odo/pkg/version.GITCOMMIT=7b6096a6f" ./cmd/odo/
# github.com/redhat-developer/odo/pkg/alizer
pkg/alizer/interface.go:11:23: undefined: model.DevFileType
pkg/alizer/alizer.go:33:19: undefined: model.DevFileType
pkg/alizer/alizer.go:39:31: undefined: model.DevFileType
pkg/alizer/alizer.go:147:35: undefined: model.DevFileType
make: *** [Makefile:101: install] Error 2

As such, this PR should have been released as a major version, I think. Not a big deal that said, but just for awareness.

FYI, this PR introduced breaking changes by renaming the exported model.DevFileType type (part of the Alizer API) into model.DevfileType. I was wondering why a minor bump of Alizer from 1.0.1 to 1.2.1 (redhat-developer/odo#7126) was not compiling, and it appears it was due to this refactoring.
go install -mod=vendor -ldflags="-X github.com/redhat-developer/odo/pkg/version.GITCOMMIT=7b6096a6f" ./cmd/odo/
# github.com/redhat-developer/odo/pkg/alizer
pkg/alizer/interface.go:11:23: undefined: model.DevFileType
pkg/alizer/alizer.go:33:19: undefined: model.DevFileType
pkg/alizer/alizer.go:39:31: undefined: model.DevFileType
pkg/alizer/alizer.go:147:35: undefined: model.DevFileType
make: *** [Makefile:101: install] Error 2

As such, this PR should have been released as a major version, I think. Not a big deal that said, but just for awareness.

Yes I think this should be a major release in the future.  Now I think the situation is better, but for sure we need to treat breaking changes as major releases.


Update cert-manager chart with changes from upstream repo

What this PR does / why we need it:
This updates the cert-manager chart with the latest changes from the upstream jetstack/cert-manager repo.
We've been working on some better versioning strategies for charts, and in future will be syncing this directory from release tags in the upstream repo (with a more regular patch release cadence).
This also updates paths for documentation since moving to readthedocs.

/cc @kragniz


Added link to docs from README #679

Fixes
Checklist

[ ] I have made a material change to the repo (functionality, testing, spelling, grammar)
[ ] I have read the [Contribution Guide] and my PR follows them.
[ ] I updated my branch with the master branch.
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation about the functionality in the appropriate .md file
[ ] I have added in line documentation to the code I modified

Short description of what this PR does:

added link to sendgrid docs in the readme

If you have questions, please send an email to Sendgrid, or file a Github Issue in this repository.
Fixes #679

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Hello @agnesjang98,Thanks again for the PR! We want to show our appreciation by sending                                              you some swag. Could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX


Game end screen

Problem
As a player, I want to see a game end screen so that I know I've beaten the game.
Suggested Solution
Create a new scene End that has a title that congratulates player and a button to restart the game and confetti animation.
Confetti examples:

https://confetti.js.org/more.html
https://phaser.discourse.group/t/confetti-effect/9943

Keywords
screen,scene,end,over,menu

8ff5ac3 7e19a6b


missing word foo

missing word foo created by<EMAIL_ADDRESS>on 2016-12-05 09:11:29

<EMAIL_ADDRESS>replied,

<EMAIL_ADDRESS>replied, whats foo bro?

<EMAIL_ADDRESS>replied, Ignore this one.  It only supports 2 users for free.  We're gonna try the
github.  I'll send a test there too.  'foo' is a generic word that computer
science geeks use to just mean 'example thing'
Thanks,
John

<EMAIL_ADDRESS>replied, oh okay...i thought u turning chinese :-)


Unhelpful deprecation docs

Expected Behavior
When a method or class is deprecated, a replacement should be provided.
Current Behavior
Some methods like Gradle#buildFinished are deprecated, but the javadocs do not indicate what should be used instead:
     * @deprecated This method is not supported when configuration caching is enabled.
     */
    @Deprecated

FTR: Gradle#buildFinished has been improved in 23992c0477f6c2a220e4f622cf31ba4ef8ddb970


Linking to KG-Microbe github release assets for kg-hub

KG-Microbe now has two parallel builds for two of the KGs and then two additional KGs only coming from the merge repo (and duckdb, not KGX).
The transform assets, stored in the core kg-microbe repo are here -- these include all transforms required to build all four KGs:
https://github.com/Knowledge-Graph-Hub/kg-microbe/releases
The core KG merge is still available on the core repo
https://github.com/Knowledge-Graph-Hub/kg-microbe
The duckdb merge assets are here -- these are currently not exactly the same as a KGX merge (most likely due to differences in merge logic, aka networkx vs custom duckdb):
https://github.com/Knowledge-Graph-Hub/kg-microbe-merge/releases

@hrshdhgd it would be great to use the merge from the core repo as the substrate for KG-Hub and the dashboard, any thoughts on how to make that possible? Do we just need to commit a merge in the core repo?

Figure out a solution for #256 and this should be done


[IntegralConstant] Should times be tag-dispatched?

Anything that can be incremented, decremented and compared to some "zero" value can implement a times method with the same semantics. Hence, it might be worthwhile to abstract this into a concept. Maybe the added complexity isn't worth it, though.

Not adding another concept just for this. I think the added complexity isn't worth the conceptual completeness in this case.


BIGTOP-3276. Update supported distros in the toolchain manifests for v1.5.0

This PR adds CentOS 8 (and RHEL 8 for user convenience, as a non-official support), Debian 10, Fedora 31, and Ubuntu 18.04 and drops Fedora 26 and openSUSE 42 to/from bigtop_toolchain.
I confirmed that the following commands worked as expected:
$ sudo bigtop_toolchain/bin/puppetize.sh
$ sudo puppet apply --modulepath=$(pwd):/etc/puppet/modules:/usr/share/puppet/modules:/etc/puppetlabs/code/environments/production/modules -d -e 'include bigtop_toolchain::jdk'
$ ./gradlew toolchain

on the following distros, on an x86_64 arch machine.

CentOS 7, 8
Debian 9, 10
Fedora 31
Ubuntu 16.04, 18.04

Rebased as a single commit.
In addition to the above distros, I confirmed the above commands worked on RHEL 8. I'm going to merge the PR a bit later.

Good job!

Great work! the patch looks good. +1

Thanks! Merged into master.


Update ghostLinks.sh reference

PR Summary
Commit d232d7682a930df6b9cc8f4b859f9bcb05e960e9 renamed ghost.sh to be  ghostLinks.sh. This PR adjusts sources to changes.

Thanks!


[Parse] Attach 'inout' to Swift 2 unparenthesized function params.

This syntax is no longer permitted, but we need to parse it like Swift 2 did in order to produce the fix-it that matches Swift 2 behavior.
rdar://problem/26681485

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    All supported platforms     | @swift-ci Please smoke test and merge
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

A smoke test on macOS does the following:

Builds the compiler incrementally.
Builds the standard library only for macOS. Simulator standard libraries and
device standard libraries are not built.
lldb is not built.
The test and validation-test targets are run only for macOS. The optimized
version of these tests are not run.

A smoke test on Linux does the following:

Builds the compiler incrementally.
Builds the standard library incrementally.
lldb is built incrementally.
The swift test and validation-test targets are run. The optimized version of these
tests are not run.
lldb is tested.

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    All supported platforms     | @swift-ci Please test and merge
    OS X platform               | @swift-ci Please test OS X platform
    OS X platform               | @swift-ci Please benchmark
    Linux platform              | @swift-ci Please test Linux platform

Lint Testing
    Language     | Comment
    ------------ | -------------
    Python       | @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

@nkcsgexi, can you review this?

@swift-ci Please smoke test

LGTM!

Linux tests made it until LLDB, merging


06/18/2018 18:40 : Create Pull Request for branch master -> prTesting1_2018061818

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef1.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Cameras Wont playback

After installation and configuration of the main .conf files, I run the commands to start the streams and it always comes back with an error that omxplayer failed playback on all cameras. We have tested it with the debugging command and it does work with that command. VLC runs the rtsp link perfectly fine, it is purely just the configuration files that run into the issue
the config is not been changed from the already pre-made layout.config.default file, I just added the links and made enabled rotation. The main displaycameras.conf file was not edited since the debugging command worked fine with all 6 streams. I am using a RBPi4 with rasbien buster lite on it. Just ran updates on the OS aswell so there shouldnt be an issue with packages.
Screenshot of the error i get on all cameras

The links are as provided, all are the same format
rtsp://<IP_ADDRESS>:7447/VfQT4hnOpxA7IudM

I am having the same issue. Even after renaming the cameras I am not sure why its pulling up the default cameras.

I'll mark up the repo soon enough, but this project is EOL. I'm not
supporting it anymore.
A
On Mon, Sep 12, 2022 at 7:35 PM DevNDanger @.***> wrote:

I am having the same issue. Even after renaming the cameras I am not sure
why its pulling up the default cameras.
—
Reply to this email directly, view it on GitHub
https://github.com/Anonymousdog/displaycameras/issues/117#issuecomment-1244711885,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHIYIKJSWXC4G6C6VAMURMTV5643LANCNFSM572ALEFQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I get it. I wished I new programming better. I just finished my degree but it was mainly java. I find it odd that Ubiquiti doesn't have more support options.

Ubiquiti support is IMHO a nightmare as are their many of their upgrades.
It's the whole reason we have only one piece of Ubuquiti equipment in our
firm.
Thanks,
A
On Tue, Sep 13, 2022, 8:50 PM DevNDanger @.***> wrote:

I get it. I wished I new programming better. I just finished my degree but
it was mainly java. I find it odd that Ubiquiti doesn't have more support
options.
—
Reply to this email directly, view it on GitHub
https://github.com/Anonymousdog/displaycameras/issues/117#issuecomment-1246098095,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHIYIKMJQ7L2AIVDSBAE62TV6EOORANCNFSM572ALEFQ
.
You are receiving this because you commented.Message ID:
@.***>

@Rogerdoger465 - not sure if you ever resolved this... I spent a good ~20 mins messing around debugging (it was an RTSPS/7441 vs RTSP/7447 issue) but was still getting the same playback issue.
In my case, I was updating the layout.conf.default in my install folder but it seemed to make no difference. Then I realised it was pulling another default file from /etc/displaycameras/layout.conf.default
To resolve this I simply coppied my layout.conf file from my original install directory into the /etc/displaycameras/layout.conf.default location. Restarted the service and that resolved my issue... up and running.
FWIW - I am using the older buster OS as per the readme warning.


fix(remove-exec-depend): add - to the pattern of package names

Description

Resolves #159.
Also, the order of 0-9 and _ was flipped for visibility.
My test result is here: https://github.com/autowarefoundation/autoware-github-actions/issues/159#issuecomment-1149189998
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

CI failed: https://github.com/autowarefoundation/autoware-github-actions/runs/6783082619?check_suite_focus=true#step:5:289
[1.638s] WARNING:colcon.colcon_core.verb.test:Test coverage will not be produced for package 'empty_target_python' since the pytest extension 'cov' was not found

It also fails with the main branch.
https://github.com/autowarefoundation/autoware-github-actions/runs/6783263865?check_suite_focus=true#step:5:294
@KeisukeShima Do you know the cause? :thinking:

CI failed: https://github.com/autowarefoundation/autoware-github-actions/runs/6783082619?check_suite_focus=true#step:5:289
[1.638s] WARNING:colcon.colcon_core.verb.test:Test coverage will not be produced for package 'empty_target_python' since the pytest extension 'cov' was not found

It also fails with the main branch. https://github.com/autowarefoundation/autoware-github-actions/runs/6783263865?check_suite_focus=true#step:5:294
@KeisukeShima Do you know the cause? thinking

We may need to add the pytest-cov package. I assume the package we depend on has recently changed.
https://stackoverflow.com/questions/26589990/py-test-error-unrecognized-arguments-cov-ner-brands-cov-report-term-missi

@kenji-miyake The previous ros:galactic docker image contained pytest-cov.
$ docker images | grep ros | grep galactic
ros                                                                                galactic                     1e1993371ff8   5 months ago    689MB

root@7e2f021257aa:/# dpkg -l | grep python3-pytest
ii  python3-pytest                                      4.6.9-1                              all          Simple, powerful testing in Python3
ii  python3-pytest-cov                                  2.8.1-1                              all          py.test plugin to produce coverage reports for Python3

Related? https://github.com/colcon/colcon-core/pull/508


run Spigot task?

This might be a little controversial, but would you be open to having a run spigot task?
It's helpful for working out whether I should be reporting bugs I encounter to paper's upstream or not.

You can already configure the run classpath and enable legacy plugin loading mode.


Error occurred when executing WD14Tagger|pysssss

Error occurred when executing WD14Tagger|pysssss:
[ONNXRuntimeError] : 1 : FAIL : Load model from D:\AI\ComfyUI\ComfyUI\custom_nodes\ComfyUI-WD14-Tagger\models\wd-swinv2-tagger-v3.onnx failed:C:\a_work\1\s\onnxruntime\core/graph/model_load_utils.h:56 onnxruntime::model_load_utils::ValidateOpsetForDomain ONNX Runtime only guarantees support for models stamped with official released onnx opset versions. Opset 4 is under development and support for this is limited. The operator schemas and or other functionality may change before next ONNX release and in this case ONNX Runtime will not guarantee backward compatibility. Current official support for domain ai.onnx.ml is till opset 3.
ComfyUI using a hand refiner workflow

What version of onnxruntime do you have installed?

all v3 models failed. onnxruntime-1.17.1

I had the same problem

same problem

Same here :/


undefined method `fetch' for nil:NilClass

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I have read the Contribution Guidelines

Issue Description
While using watchbuild I keep getting undefined method fetch' for nil:NilClass`
Complete output when running fastlane, including the stack trace and command used
[12:29:08]: Starting login with user<EMAIL_ADDRESS>[12:29:11]: Successfully logged in
[12:29:13]: undefined method `fetch' for nil:NilClass
[12:29:13]: Something failed... trying again to recover```

Configuration Files
Please copy the complete content of your Fastfile and any other configuration files you use below:
My command is:
bundle exec watchbuild --app_identifier="<APP_ID>"

Environment
watchbuild v0.1.3

Do you use bundler to execute fastlane (i.e. bundle exec fastlane)?
YES
Do you use a Ruby environment manager (e.g. chruby, rbenv, rvm)?
NO

As a first step, can you please try updating watchbuild to 0.1.4? Thanks!


Node reimaged due to expired heartbeat

Information

Onefuzz version: 2.27.0
OS: Windows

Provide detailed reproduction steps (if any)
Scheduled job 2056f74a-d2c3-478b-a6f5-e8335d33543c to run for 1 week. However after a day it was stopped with the error:
    {"code": 468, "errors": ["node reimaged due to expired heartbeat", "scaleset_id:8ab21c8b-a504-4d78-b185-681c55d00fe9 machine_id:97da016a-10db-4b25-bd0a-d4830727bbbf", "last heartbeat:2021-07-20 21:23:11+00:00"]}

Expected result
Task to run to completion
Actual result
Node to which task was assigned was reimaged before task completion.

This was due to a "503 Service Unavailable" error coming back from the service after multiple retries.
Investigating why the service had issues.

The Azure Functions integration into SignalR failed, which caused the agent-commands to fail, which caused the supervisor to stop.
At the moment, we're using the Azure Functions integration for SignalR, rather than handling the communication ourselves.
We'll investigate making the supervisor more resilient to the service having issues as well as making the SignalR integration more resilient.


Compatibility LiipImagine filters

I'm trying to add a LiipImagine filter to a media image
<div style="background-image: url({{ image.path|imagine_filter('sylius_small') }});">

However, BitBag seems to add /media/image/ as prefix to the image URL, while Sylius doesn't; which make the resolve path invalid.
Is BitBagCMS compatible with LiipImagine image size filters ?

@qvasdoria I am having the same issue. Did you find a solution to this?

@qvasdoria you can change or remove the media/image/ but the bitbag code still appends a / in the code. It's hardcoded. Which then either creates a folder with no name // or fails.
In my AWS S3 it creates a folder with no name.

@qvasdoria I believe I solved your issue. You just need to override the bitbag cms services with your own in your own project, and then the configuration files and remove the hardcoded / if you're uploading to AWS S3 with knp_gaufrette and while overriding the config files you can remove or change /media/image as well.
I'll try to solve the LiipImagine filter as well or just not use it myself but I imagine the solution is similar.

@decemvre would it be possible for you to share how you had solved this issue? What services need to be overwritten and changed?
I have stumbled across this open issue and it is the exact problem I am trying to solve, I have managed to alter the knp_gaufrette configuration to get uploads working correctly, but I have been unable to fix retrieval.

The code is in a private repo and I can't share it however these are the services you need to override; simply create these files in your project and then override the exact service names in a configuration file in packages.

In UploadEditorImageAction I passed it the aws s3 region and bucket in the constructor using the service dependency injection configuration and the in the JsonResponse I appended those values before $media->getPath()
This will make the WYSIWYG Editor in the CMS load the preview after you've uploaded the file in the Admin panel

In MediaUploader remove the hardcoded '/' in the call to $media->setPath('/' . $path)
That will prevent folders with empty names being created in the aws bucket.

And finally in GenericProvider pass it the aws s3 region and bucket again in the constructor and then modify the render method and add a new property to the $media object on the fly like $media->s3Path = .. (I did this because I didn't want to override the Entity too) where  you append the those values before the $media->getPath.
Don't use $media->setPath() as that will on occasion also save the path to the database and you don't want that.
Finally override the image.html.twig template that the bundle uses and change .path to src="{{ media.s3Path }}"

Obviously this is a bit of a hack fix but because there are hardcoded bits of code in the bundle already clearly it's not designed to upload to aws S3 in this version; so this worked for me until the next version comes around.

I simply "fixed" it this way:
liip_imagine:
    loaders:
        default:
            filesystem:
                data_root:
                    - "%kernel.project_dir%/public"

It specifies where the filesystem is so liip knows where to start loading images.

It works, thank you !

I simply "fixed" it this way:
liip_imagine:
    loaders:
        default:
            filesystem:
                data_root:
                    - "%kernel.project_dir%/public"

It specifies where the filesystem is so liip knows where to start loading images.

It works, thank you !

fixed with 3.0.0 release

My final problem is that the WYSIWYG editor in the admin panel doesn't link to images in AWS S3.

Hi, did you find a solution ? i have the exact same problem

My final problem is that the WYSIWYG editor in the admin panel doesn't link to images in AWS S3.

Hi, did you find a solution ? i have the exact same problem

I honestly don't remember if I fixed it or just left it as a known bug; the project went bust after a few months.


Use Multi JSON gem instead of requiring explicit 'json' gem dependency

instead of explicitly using to_json calls, use the multi-json gem so that host appilcations can choose their json encoder.
ex: I use yajl for all of my applications due to the drastic performance improvements compared to the basic to_json library.

That's good idea.
Can you tell me some gems which use multi-json gem instead of requiring json gem explicitly?
I'll follow those gem's way.
Thanks

the multi_json gem is really easy to use.  just require it and call MultiJson.encode(hash) and you're done.
https://github.com/intridea/multi_json
here's an example from one of my gems:
https://github.com/socialcast/elastic_searchable/blob/master/lib/elastic_searchable.rb#L29


modify webhook img to independent image

What type of this PR

Bug fixes

modify webhook img to independent image since webhook affects kube-ovn-controller/kube-ovn-cni metrics
Which issue(s) this PR fixes:
Fixes #1424

已回合release-1.9 分支，release-1.8 分支不需要回合


findbugs warnings

./gradlew findbugsMain

Thanks. We'll fix them.

fixed by https://github.com/TestArmada/flank/commit/d624f3dffe3103a5a85af499419890be4ea758ca


Incorrect error of use of unassigned variable

TypeScript Version:  2.1.5
strictNullChecks: true
Code
let a: {};

if (!a) { // <!-- Error
   ....
}

Expected behavior:
Code compiles fine.
Actual behavior:
Use of unassigned variable.

a has the type of {}, and has no value assigned.
so what you wanted:
let a = {}; // not let a: {}

@devdoomari It is not what I want.
I want to have it undefined and assign it only if it is undefined.
Full code:
let a: {};

for (const x of y) {
  if(x.q) {
    a =x.q;
    break;
  }
}

// Assign default value if couldn't assign before
if (!a) {
  a= {};
}

The control flow checker (in strict null checks mode) assures that you'll never accidentally observe undefined in a variable unless the type of the variable allows it. Your program logic is constructed such that undefined is actually a permitted value (at least in parts of the logic), so I'd recommend including undefined in the type of a:
let a: {} | undefined;

The problem with your suggestion is that we'd no longer catch this:
let a: string;
// Intended to have assignment here, but forgot
if (!a) {
    // Think I have an empty string, but I have undefined
}

@ahejlsberg What about this case ?
I would expect it compiling fine since I am checking against undefined.
let a: number;
if (typeof a !== "undefined") {
	a = 1;
}

I think the same argument holds. If the declared type of a variable does not include undefined, the control flow analyzer takes it to mean you never want to observe the variable in an uninitialized state (in any way). I think the consistency of that is important, particularly since the type number | undefined in cases where you want to do those types of checks.

That's what I ended with.
Thanks.

@ahejlsberg
I feel that there is a need for language construct or helper which tests for null or undefined.
Currently I use "if(a) {..}" but if type of 'a' changes to string or number, this test will not be correct.
I feel more safe using this helper now.
function isNullOrUndefined<T>(obj: T | null | undefined): obj is null | undefined {
	return typeof obj === "undefined" || obj === null;
}

if (!isNullOrUndefined(a)) { ... }

But prefer to have something in the language like:
iff (a) { ... }

Adding entirely new statements beyond what JavaScript has is definitely out of scope for TypeScript. To check if a value is null or undefined in JavaScript, just use x == null. See more discussion here.

Thanks.
Didn't think about this pattern


fix API behavior for SpaceManager and SpaceAuditor to receive 403

this PR is to fix the bug of both SpaceManager and SpaceAuditor should
receive 403 when list keys for a service instance, not 0 results.
[#87481016]
Signed-off-by: Hua Zhang<EMAIL_ADDRESS>

Thanks for your response, the organization is more clear now. I see the test coverage in service_keys_controller_spec.rb for the enumerate endpoint, and the rest is covered in service_key_access_spec.rb. Looks good! Will merge when the pipeline is ready for new commits.


position

can i get position x,y or velocity vx,vy without the ultrasonic ?

No. The ground distance is required to be able to convert a motion in pixels to an absolut distance in meter per seconds. Without the sonar, the only information you'll have is the flow of pixels.

Thanks


python38Packages.wadllib: 1.3.5 -> 1.3.6

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python38Packages.wadllib is: "Navigate HTTP resources using WADL files as guides"
meta.homepage for python38Packages.wadllib is: "https://launchpad.net/wadllib"
meta.changelog for python38Packages.wadllib is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 1.3.6 with grep in /nix/store/17az70vwfja69k46g2bykzihmvhhssav-python3.8-wadllib-1.3.6

found 1.3.6 in filename of file in /nix/store/17az70vwfja69k46g2bykzihmvhhssav-python3.8-wadllib-1.3.6

directory tree listing: https://gist.github.com/5131fce78614519f704455bb1924e146

du listing: https://gist.github.com/8f36f33bcb37e3472b37e55148963539

Rebuild report (if merged into master) (click to expand)

82 total rebuild path(s)

21 package rebuild(s)

21 x86_64-linux rebuild(s)
21 i686-linux rebuild(s)
19 x86_64-darwin rebuild(s)
21 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
breezy
cabal2nix
dep2nix
devpi-client
flatpak-builder
haskellPackages.cabal2nix-unstable
hydra-unstable
nix-prefetch-bzr
nix-prefetch-scripts
nix-update-source
python38Packages.breezy
python38Packages.check-manifest
python38Packages.launchpadlib
python38Packages.lazr-restfulclient
python38Packages.wadllib
python39Packages.breezy
python39Packages.check-manifest
python39Packages.launchpadlib
python39Packages.lazr-restfulclient
python39Packages.wadllib
vcstool

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/17az70vwfja69k46g2bykzihmvhhssav-python3.8-wadllib-1.3.6 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python38Packages.wadllib https://github.com/r-ryantm/nixpkgs/archive/ff2ffa346d4d0adcc91d768ee31006377577caaf.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/17az70vwfja69k46g2bykzihmvhhssav-python3.8-wadllib-1.3.6
ls -la /nix/store/17az70vwfja69k46g2bykzihmvhhssav-python3.8-wadllib-1.3.6/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

Maintainer pings
cc @marsam for testing.

@GrahamcOfBorg eval

addressed by https://github.com/NixOS/nixpkgs/pull/139091


Whitespace handling in triple-quoted strings is broken

toml.loads('''foo = """
I expect newlines to be preserved?

Newlines please?
"""''')

returns
{ 'foo': 'I expect newlines to be preserved?\nNewlines please?\n' }

Where I'd expect a
{ 'foo': 'I expect newlines to be preserved?\n\nNewlines please?\n' }

Hi,
Are you running the latest master? It looks like it is fixed there although it may be present in the latest pip release. This may be a dup of #80 or #68.

Not master. pip.
On Sep 1, 2017 7:54 AM, "Will Pearson"<EMAIL_ADDRESS>wrote:
Hi,
Are you running the latest master? It looks like it is fixed there although
it may be present in the latest pip release. This may be a dup of #80
https://github.com/uiri/toml/issues/80 or #68
https://github.com/uiri/toml/issues/68.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/uiri/toml/issues/119#issuecomment-326487073, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AApc0odPdzbb0O1LqS7rDY5IFrzOUxSTks5sd44CgaJpZM4PHSQU
.

Closing as dup of #90


Per these docs we should be able to add callouts to markdown files.

Per these docs we should be able to add callouts to markdown files.
https://github.com/github/docs/blob/main/contributing/content-style-guide.md#callouts
{* note *}

**Note:** This is a note

{* endnote *}

But in my usage it shows this text as is; no callout or formatting. See gist:
https://gist.github.com/samuelneff/eac051f64b15b635811b5ee1149eeb51
Am I doing something wrong? Are the docs wrong? Does this only work in certain contexts?
Originally posted by @samuelneff in https://github.com/github/docs/discussions/20727

@Msalgado1988 Thanks for opening an issue and discussion!
The syntax for callouts includes a % where the * appears in your example. However, please note that the style guide referenced in your issue is specifically for contributing to the Docs repo. These callouts are customized for use in the Docs and won’t work in gists or Markdown files outside of the repo.
Hope that clarifies some things. I'll go ahead and close out this issue. Thank you again! 💛