[fix](invert index) fix the inaccurate rows_inverted_index_filtered i…

…n the profile
Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Deploy CallWeb API to TEST

After the changes in #20, we need to deploy the CallWeb API to a test instance.

Have forked the API and will now include it as part of the OpenShift deployment. It has been deployed to OpenShift successfully.


feat(back to top): new $back-to-top-icon-margin-left Sass var

Description
This PR introduces in new Sass variable for the back-to-top component: $back-to-top-icon-margin-left.
Types of change

New feature (non-breaking change which adds functionality)

Live previews

https://deploy-preview-2340--boosted.netlify.app/docs/5.3/components/back-to-top/

@louismaximepiton Are we still needing this variable? It seems to be used only in the old use case which is not anymore in the documentation:

  Back to top

Maybe we can drop this variable and the corresponding rule

Note: remove "Even if the rendering could still work, it is recommended to only use the versions presented in the documentation." from the migration guide.


Allow attachments in EmailNotifications

Codecov Report

Merging #29 into master will decrease coverage by 0.03%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #29      +/-   ##
==========================================
- Coverage   84.17%   84.14%   -0.04%
==========================================
  Files          34       34
  Lines        1188     1192       +4
==========================================
+ Hits         1000     1003       +3
- Misses        188      189       +1

Impacted Files
Coverage Δ

universal_notifications/backends/sms/signals.py
100% <ø> (ø)
:arrow_up:

universal_notifications/backends/emails/send.py
100% <100%> (ø)
:arrow_up:

universal_notifications/notifications.py
94.87% <100%> (+0.08%)
:arrow_up:

universal_notifications/backends/sms/utils.py
85.36% <100%> (ø)
:arrow_up:

universal_notifications/backends/push/gcm.py
97.61% <0%> (-2.39%)
:arrow_down:

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 1a2d6a9...7870a79. Read the comment docs.


actions: reinstate validation of schemas and examples, fixes #1739

As promised, following the merging of #1270 / #1897
Note: items related to publishing an npm package containing the schemas will be moved to a new issue.
This PR now reinstates the validation of examples and schemas using GitHub Actions.

We still need to work on a few details.

@MikeRalphson Is there a list of these details / anyway we can help out? Even a pre-release of current state would be great, we're blocked by using the existing swagger-schema-official package by our legal team and getting out an update with valid license would allow us to continue.

@kylef for visibility I've copied your comment here from #1730 as that PR is merged and added the TODO items as I see them now to the initial comment.

Thanks @MikeRalphson.
I'd add one more point to the TODO tasks above, once released we should signal in NPM that the existing swagger-schema-official package is deprecated, this can be done with the npm deprecate command.
I can provide some input on some of the questions above:

determine if Apache-2.0 LICENSE file also needs including in generated packages

I can confirm the LICENSE file in root is picked up by NPM, this can be verified via npm pack which creates the tarball of the package and lists files included:
npm notice 📦<EMAIL_ADDRESS>npm notice === Tarball Contents ===
npm notice 687B   package.json
npm notice 11.3kB LICENSE
npm notice 5.9kB  README.md
npm notice 4.4kB  schemas/jsonSchema/draft-04/metaschema.json
npm notice 1.9kB  schemas/v1.2/apiDeclaration.json
npm notice 1.8kB  schemas/v1.2/authorizationObject.json
npm notice 4.6kB  schemas/v1.2/dataType.json
npm notice 2.6kB  schemas/v1.2/dataTypeBase.json
npm notice 661B   schemas/v1.2/infoObject.json
npm notice 1.0kB  schemas/v1.2/modelsObject.json
npm notice 2.0kB  schemas/v1.2/oauth2GrantType.json
npm notice 2.4kB  schemas/v1.2/operationObject.json
npm notice 1.3kB  schemas/v1.2/parameterObject.json
npm notice 325B   schemas/v1.2/README.md
npm notice 592B   schemas/v1.2/resourceListing.json
npm notice 385B   schemas/v1.2/resourceObject.json
npm notice 248B   schemas/v2.0/README.md
npm notice 40.2kB schemas/v2.0/schema.json
npm notice 890B   schemas/v3.0/README.md
npm notice 35.5kB schemas/v3.0/schema.json
npm notice 22.1kB schemas/v3.0/schema.yaml
npm notice === Tarball Details ===
npm notice name:          oas-schemas
npm notice version:       2.0.0
npm notice filename:      oas-schemas-2.0.0.tgz

which npm org to publish packages to (new/existing)?

For consistency with GitHub, perhaps creating an oai NPM org would make sense.
The prior specifictions package was released under the swagger user on NPM which also contains swagger-editor and other packages.

who will have publish rights

Since there is a TODO for setup automated publishing via Travis deploy, this will be anyone who has GitHub push/write acces?

Action: @MikeRalphson to update package versions.

This PR is now out of date and does not fit with newer schema test workflows or the version requirements of our node environment, and the original submitter is not currently available to rework it.
I have filed issue #3557 to track replacing this PR with a modernized update so we can close out this PR.


Conversions: Non-standard aliases (e.g. kilos for kilograms)

Currently,

1g in kilos

results in

I'm sorry, I don't understand. :/

whereas

1g in kilograms

works just fine; resulting in

1 gram is about equal to 0.001 kilograms. :)

Not even "meters" works instead of "metres" 😅

Not even "meters" works instead of "metres" 😅


Generate different ClientOptions for service clients in a package where multiple services version independently

In some SDK packages, multiple service clients are included for services that version independently.  In these cases, we want to generate different ClientOptions types for those services that version independently, so that they can have separate ServiceVersion enums.
For example, in Purview, the Purview.Administration package holds clients for Account and MetadataPolicy services, but only one ClientOptions type.  It should generate an AccountClientOptions and a MetadataPolicyClientOptions, which each have versions for those services in the ServiceVersion enum.

In CodeModel, versions are applied to the individual operations rather than whole operation groups or collections of operation groups, so we collect them all and take unique values:
context.CodeModel.OperationGroups
    .SelectMany(g => g.Operations.SelectMany(o => o.ApiVersions))
    .Select(v => v.Version)
    .Distinct()
    .OrderBy(v => v)
    .Select((v, i) => new ApiVersion(ToVersionProperty(v), $"Service version \"{v}\"", i + 1, v))
    .ToArray();

To produce one *ClientOptions type per client, I've collected api version in every operation group individually. However, there is no way to group them by input file.

One option is to explicitly specify that some client requires individual *ClientOptions type, e.g:
[CodeGenClient(ClientOptions = "SeparateClientOptions")]
public partial class SeparateClient {}

Since CodeModel (modelerfour) lacks of information to identify which batch of clients belong to one clientOptions, other batch belongs to another, Need additional configuration by manual, It is not available to auto generate different clientoptions in codegen.
There is another manual approach: suspress + subclient can achieve this. e.g generate two client options using “SubClient” feature (it is currently in PR: https://github.com/Azure/autorest.csharp/pull/1563):
https://github.com/Azure/azure-sdk-for-net/pull/24828/files
So We will not implement it in codegen now, close this issue.


font problem

Hello,
I have new windows installed.,
Dled and installed brand new skylobby and placed the custom-css.edn file and it doesnt work. The font size of the chat input doesnt work. Nothing works. Actually it doesnt matter what I do to it...  Nothing matters no user rights nothing.
Odd that I kept other windows and the same config works well with up to date skylobby.
I cannot copy the folder becasue user name is not a match.
Otherwise the lobby works perfectly but the font small..
{".root"
{:-fx-base "rgb(20, 20, 20)",
:-fx-accent "rgb(50, 50, 50)",
:-fx-background "rgb(0, 0, 0)",
:-fx-control-inner-background "rgb(30, 30, 30)",
:-fx-selection-bar-non-focused "rgb(40, 40, 40)"},
".styled-text-area" {:-fx-background-color "rgb(0, 0, 0)"},
".text-field" {:-fx-prompt-text-fill "rgb(180, 180, 180)"},
".skylobby"
{"-normal" {"> .ikonli-font-icon" {:-fx-icon-color "white"}},
"-chat" {"-user-list" {:-fx-text-fill "lightgrey"}
"-input" {:-fx-font-size "34"}}}}

Hello, no news on this please?
There must be a way to increase the font size of the chat window!


HTTPSify links to content

For YouTube, XKCD, Wiki(m|p)edia and Google.
Makes them all consistent: previously a mixture of HTTP and non-HTTPS
URLs were present.

Some of the other sites linked to in the book may well have HTTPS URLs available too; these were just the sites I knew could be changed.

This is a great idea! I need to manually merge this since other PR changed one of the same lines as you fixed. I'm having a break from the CSFG development this week but will merge these together when I can.
Thanks!


How do I remux video to a different format Using the Python yt-dlp invocation?

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm asking a question and not reporting a bug or requesting a feature
[X] I've looked through the README
[X] I've verified that I have updated yt-dlp to nightly or master (update instructions)
[X] I've searched known issues and the bugtracker for similar questions including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Please make sure the question is worded well enough to be understood
I've been looking at the python version of the command at https://github.com/yt-dlp/yt-dlp/blob/9ebac35577e61c3d25fafc959655fa3ab04ca7ef/yt_dlp/YoutubeDL.py, and I noticed there isn't a "remux-video" option. Looking closer at the code, however, it appears there should be a way to remux or recode a video using the 'postprocessors' argument, but it isn't clear to me how this should be used. I've tried using [{"key": "FFmpegVideoConvertor", "when": "post_process"}] or [{"key": "FFmpegVideoRemuxer", "when": "post_process"}], with the extension in the final_ext argument, but there are some issues. Any guidance on what options I should use to get a remux or recode from mp4 to other formats in place of --remux-video in the command line version, like mov and avi?
Provide verbose output that clearly demonstrates the problem

[ ] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[ ] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
No response

use devscripts/cli_to_api.py
ydl_opts = {
    'final_ext': 'mp4',
    'postprocessors': [{
        'key': 'FFmpegVideoRemuxer',
        'preferedformat': 'mp4',
    }],
}


⚠ AVS (kty) has degraded performance

In 4e0f1e0, AVS (kty) (https://avus.com.br) experienced degraded performance:

HTTP code: 200
Response time: 8341 ms

Resolved: AVS (kty) performance has improved in 6cc6a41.


Ensure MachineAPI is enabled before trying to use its resources

Why we need this PR
Currently, NHC only checks if it runs on OCP before trying to access MachineAPI resources, however not all OCP clusters have MachineAPI enabled and the controller fails to start in such conditions.
Changes made
Verify if MachineAPI is in the list of the Cluster's EnabledCapabilities
Which issue(s) this PR fixes
https://issues.redhat.com/browse/ECOPROJECT-1902
Todo

[x] Fix CI tests

/test 4.15-openshift-e2e

/test 4.15-openshift-e2e

/test 4.15-openshift-e2e

/retest

I've been allucinated here. I merged the branch without noticing the failed tests :facepalm:

I've been allucinated here. I merged the branch without noticing the failed tests 🤦

Since 4.14 + passed, you are most likely in the clear.
To make sure let's keep an eye on unrelated  #303 and see that all the tests are clear.


Calling all people using rendr!!

Hey - if you're using rendr in a production environment let me know! I'm working on documentation and would love to be able to link to some example sites!
i know @bigethan and truilia are... anyone else that wants to get a shout-out on rendr docs?

Fun! We're using it only for our mobile site (m.trulia.com). And our flavor is require.js based.

@growlsworth @lo1tuma @crwang @alexindigo @c089 are you all interested in describing your project / posting a screen cap and i'll add the projects to the examples for rendrjs? the examples page will probably be very similar to backbones: http://backbonejs.org/#examples
Trying to release a documentation site along-side v1.0.0 later this week :)

I've built two sites with rendr. One using handlebars and one using React. Happy to write a little blurb for you @saponifi3d. Let me know what you're thinking.

@growlsworth fancy! just a blurb about some of the features you have used, advantages you got with using it, and a screen cap of your sites (or i can do the screen caps if you want).  Also, let me know if you used any other tools like requirejs or if you built the js bundle with browserify and all that jazz. something like: http://backbonejs.org/#examples-delicious
I might also start buggin' ya about how you integrated React w/ Rendr.  I'm probably going to build out an example in the examples app and rework the views around the idea of being able to use any view framework or templating engine.

Unfortunately the project @lo1tuma and I have been working on was cancelled before going live last year, and we've both moved on, so I fear we can't contribute to the showcase :)

Sorry to hear that @c089, thanks for the update!!

How's this @saponifi3d:
Giving Stage
Giving Stage is a virtual venue where artists perform in order to raise money for causes. Giving Stage uses rendr, rivets, and primus to deliver a real-time concert experience. The use of rendr allows Giving Stage to optimize the time to first paint and speed of subsequent browsing. This is especially important for the mobile experience. Giving Stage also takes advantage of serving multiple rendr apps within one node application.

For the screenshot, I recommend: https://www.givingstage.com/demo. I'm pretty proud of creating a runner that demonstrates the live experience with timed random data.
cine.io
cine.io is the first developer focused video cloud, providing APIs and SDKs for live video broadcasting and peer-to-peer video communication. cine.io uses rendr and React to serve the front-facing web site and logged-in dashboard. The use of rendr allowed cine.io to develop the logged-in dashboard and public API simultaneously. Reuse of the models and libraries made it significantly easier to ensure consistent application logic between the API, web apps, and background workers.

For the screenshot, I recommend: https://www.cine.io/products/broadcast. The front-facing site doesn't do a whole lot, but this hero image shows off my sweet CSS.

I have 2 Rendr websites in production:

Tebla, a German-based restaurant reservation platform.
Questionmark, a Dutch consumer goods research platform.

How fun to see these!

@por would you be able to make a quick blurb about it similar to the one above? (along these lines http://backbonejs.org/#examples-delicious). Thanks!!

@bigethan Can you share some thoughts what should be done to get rendr + requirejs working?

@pcompassion here is somewhat working example – https://github.com/rendrjs/rendr-examples/tree/master/05_requirejs it's a good starting point.

Hi, I'm using rendr for our site.
Politas
Politas is a Japanese political news & discussion site.
http://politas.jp/

@pcompassion we're looking to release some internal NPM modules that we have (written by @alexindigo) that really help requireizing a rendr app and templates.  We're also working on upgrading to 1.0.0 in a couple weeks - the modules might have incompatibilities as they are only tested with our 0.5 version of Rendr.

ViaMichelin
ViaMichelin website provides map, address and route search.
http://www.viamichelin.ie/

@bigethan - i'm going to be upgrading the examples today to use 1.0.0 - there shouldn't be any really big changes - the biggest stuff is breaking change w/ the deprecation of postInitialize and dropping express 3. Here's the complete change set.  Let me know if you have any problems upgrading to 1.0.0 - if you're using handlebars, i'd also highly suggest updating to rendr-handlebars @ 0.2.4

The lone issue we ran into when upgrading all the things was the latest grunt-contrib-handlebars  requiring handlebars expecting 2.x handlebars.   Otherwise it's been smooth sailing for our small test app.

I've always had issues packaging up the assets. I've only had success using rendr_stitch. Updating to 1.0.0 didn't play nicely with my rendr_stitch config, so I though I would try the move to browserify again. So far unsuccessful. :(

@growlsworth :'( FYI: i'm planning to add an example of gulp + browserify to the rendr-examples (i'm working on updating all the examples to use 1.0.0 as well)

That would be awesome! I have 4 things which make my life awesome, but asset compilation challenging:

I use a global loader. This means I don't require files like: require('../../../models/user'). I have a single global object which is responsible for loading files. That makes requiring super easy when it looks like Loader.model('user') or Loader.lib('tracker'). That works from any location.

I use coffeescript.
I'm using react and no client .hbs files.
I use multiple rendr apps with a shared base app, base view, base app view, and base router. like this:

apps/
 home/
 admin/
 shared/
   base_app.coffee
  …
…
   ```

We are now starting a new application using rednrjs, it will be the management and B2B frontend for https://clubjudge.com
And soon until the end of the year we hope to redesign our frontend using rendrjs also, I did a small proof of concept and since we already use backbone and handlebars the migration is less painfull, the poc give us really good indications about page speed.

we just built a new site that uses rendr. the site is http://autoinsurancey.com and it gives estimated rates for all the major auto insurance carriers, with as little input as just a zip code or age. as the user enters is more info about themselves or their vehicle, the estimated rate is refined in real-time.

FYI we use Rendr to power http://www.themid.com

I use Rendr for this simple image to base64 converter http://imagetobase64.com/
That´s my first Rendr app, I have two more in the pipe :+1:

We're using Rendr for http://motto.time.com/. Great library :)

:D Awesome thanks for all the links, all of your projects look great!! I'm going to update the docs in the next few days to include screen caps of your home pages and links to the apps themselves so people can see all the cool apps built on rendr!


RFM - diskdump

I DON'T Want To Become The Maintainer

[x] I have followed the Package Triage Process and I do NOT want to become maintainer of the package;
[x] There is no existing open maintainer request for this package;

Checklist

[x] Issue title starts with 'RFM - '

Existing Package Details
Package URL: https://chocolatey.org/packages/diskdump
Package source URL:
Date the maintainer was contacted (in YYYY-MM-DD): 2021-12-13
How the maintainer was contacted: Email

This software has a dtgm's package and not updated since it's first push, so i think it won't be updated anymore.


Bug: Extension Field Filter

Expected: Filtering by extensions.programmingLanguage:Go does produce some outputs in the demo data.
Result: No matching output found.

Fixed in 2f931e7cb2f4d47fb0ea65392de2e2a5f938b9d8


*: fix the race issue in ResetTS

Signed-off-by: nolouch<EMAIL_ADDRESS>
What problem does this PR solve?
Fix https://github.com/pingcap/pd/issues/1953
What is changed and how it works?
make it safely.
Check List
Tests

Unit test

/rebuild

Codecov Report

Merging #1972 into master will increase coverage by 0.17%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master   #1972      +/-   ##
=========================================
+ Coverage   77.73%   77.9%   +0.17%
=========================================
  Files         174     174
  Lines       17573   17573
=========================================
+ Hits        13661   13691      +30
+ Misses       2847    2825      -22
+ Partials     1065    1057       -8

Impacted Files
Coverage Δ

server/tso/tso.go
80.29% <100%> (-0.73%)
:arrow_down:

server/kv/etcd_kv.go
75.32% <0%> (-6.5%)
:arrow_down:

server/region_syncer/client.go
78.94% <0%> (-3.95%)
:arrow_down:

server/schedule/operator_controller.go
84.6% <0%> (+0.18%)
:arrow_up:

client/client.go
69.18% <0%> (+0.41%)
:arrow_up:

server/grpc_service.go
57.97% <0%> (+0.64%)
:arrow_up:

server/config/option.go
93.08% <0%> (+0.92%)
:arrow_up:

server/server.go
84.01% <0%> (+0.97%)
:arrow_up:

server/core/storage.go
76.04% <0%> (+1.19%)
:arrow_up:

... and 5 more

Continue to review full report at Codecov.

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

/merge


SteamCMD error

###########################################################################
valheim_1  | [Valheim][root] : Valheim Server - Mon Feb 15 23:57:36 EST 2021
valheim_1  | [Valheim][root] : Initializing your container...
valheim_1  | [Valheim][root] : ###########################################################################
valheim_1  | [Valheim][root] : Switching UID and GID
valheim_1  | [Valheim][root] :
valheim_1  | usermod: no changes
valheim_1  | [Valheim][root] :
valheim_1  | [Valheim][root] : Auto Update Enabled...
valheim_1  | [Valheim][root] : Auto Update Schedule: 0 5 * * *
valheim_1  | rm: cannot remove '/home/steam/valheim/logs/auto-update.out': No such file or directory
valheim_1  | [Valheim][root] : Auto Backup Enabled...
valheim_1  | [Valheim][root] : Auto Backup Schedule: "*/15 * * * *"
valheim_1  | rm: cannot remove '/home/steam/valheim/logs/auto-backup.out': No such file or directory
valheim_1  | [Valheim][root] : Setting up file systems
valheim_1  | [Valheim][root] : Launching as steam...
valheim_1  | [Valheim][steam]: ###########################################################################
valheim_1  | [Valheim][steam]: Valheim Server - Mon Feb 15 23:57:37 EST 2021
valheim_1  | [Valheim][steam]: STEAM_UID 1000 - STEAM_GUID 998
valheim_1  | [Valheim][steam]: Installing Valheim via Odin...
valheim_1  | [Valheim][steam]: ###########################################################################
valheim_1  | [Valheim][steam]: Variables loaded.....
valheim_1  | [Valheim][steam]:
valheim_1  | Port: 2456
valheim_1  | Name: Test
valheim_1  | World: Dedicated
valheim_1  | Public: 1
valheim_1  | Password: (REDACTED)
valheim_1  |
valheim_1  | [Valheim][steam]: Running Install...
valheim_1  | [ODIN][INFO]  - Installing 896660 to /home/steam/valheim
**valheim_1  | [ODIN][ERROR] - Failed to find steamcmd in path
valheim_1  | [ODIN][ERROR] - Checking for script under steam user.**
valheim_1  | [ODIN][INFO]  - Executing: /home/steam/steamcmd/steamcmd.sh .....
valheim_1  | [ODIN][INFO]  - Using steamcmd script at /home/steam/steamcmd/steamcmd.sh
valheim_1  | WARNING: setlocale('en_US.UTF-8') failed, using locale: 'C'. International characters may not work.
valheim_1  | Redirecting stderr to '/home/steam/Steam/logs/stderr.txt'
valheim_1  | /tmp/dumps is not owned by us - delete and recreate
valheim_1  | [  0%] Checking for available updates...
valheim_1  | [----] Downloading update (151 of 16258 KB)...
valheim_1  | [  0%] Downloading update (2636 of 16258 KB)...
valheim_1  | [ 16%] Downloading update (4400 of 16258 KB)...
valheim_1  | [ 27%] Downloading update (5641 of 16258 KB)...
valheim_1  | [ 34%] Downloading update (6886 of 16258 KB)...
valheim_1  | [ 42%] Downloading update (8274 of 16258 KB)...
valheim_1  | [ 50%] Downloading update (9559 of 16258 KB)...
valheim_1  | [ 58%] Downloading update (10832 of 16258 KB)...

Do we need to be concerned about the steamcmd error "Failed to find steamcmd in path"?

No, it tries to find it in your path first its something you can ignore <3
It is to maintain compatibility for people who purely use Odin on a dedicated linux server. This repo is highly versatile and designed to be run on a menagerie of environments. You might see some errors but as long as you get to Game Connected (sometimes before DungeonDB Start) than you are all good :)
The repo is built to handle failure cases and halt loading if it encounters a real error.


Add ability to init and teardown classes when user scoped services change

Consumers often want the ability to register for events when user scoped services are created.  Some examples of this might be uploading user files, notifications, etc.  We currently have a callback system with teardown, but we can improve this.
We could use Dagger's IntoSet to allow components to register classes to instantiate and call when the scoped services are created.  Similarly, we could do this for teardown classes as well.

This is similar to https://github.com/dropbox/kaiken/issues/29


Detecting Anomaly

Hi, thank you for your wonderful project!
I've got a question on detecting anomaly, so how can I use the output to detect anomaly in my data? Is there any code that I can measure the distances?
Again, thank you for sharing your great work!

Hi @imurs34, thank you for your interest in our project!
Regarding anomaly detection, I had uploaded slides and paper to the repo, detailing applications on how to use HON for specific types of anomalies.
Note that HON itself is not meant to be an anomaly detection algorithm; what was illustrated in the paper is that there are certain types of anomalies (change-points, or sophisticated attacks, whichever way you see it) that, once represented as the first-order network, can no longer be detected using standard anomaly detection algorithms for dynamic networks.
You can choose any distance metric you want. Equation (1) is the most commonly used weight distance. I have uploaded an old snippet of the implementation of graph diff for your reference link. The code was written a couple of years ago (read: bad implementation) and has hard-coded paths (read: you need to update). Still, hope it can be helpful. Mandana Saebi @msaebi has implemented other distance measures in a recent revision.
A better way to handle graph operations is using packages like NetworkX, which has many functions built-in. Link
Let us know if this answers your question.

Oh, thank you for your kind and prompt reply! The code you provided is really helpful! NetworkX seems powerful and relevant to my project as well. I'll come back if I need additional explanation in implementing your code, I cannot thank you enough! I'm very impressed by your continuous effort to make your project more accessible and available to more people.
Thanks agian :)!


Publish Docker image to GitHub repository and/or Docker Hub

Summary
When the Docker image is satisfactory then publish it to the GitHub repository.
See e.g.

Publishing Docker images
https://dev.to/github/publishing-a-docker-image-to-githubs-container-repository-4n50

@regebro Shall we just publish to GitHub Packages or also Docker Hub? If it is the latter then someone of us needs to create an account at Docker Hub. And it needs the "Open Source Software Project" status.
I personally GitHub Packages is sufficient - at least initially.

@regebro I need more permissions to complete this task as well.
docker login ghcr.io
Username: jimisola
Password:
WARNING! Your password will be stored unencrypted in /home/jimisola/.docker/config.json.
Configure a credential helper to remove this warning. See
https://docs.docker.com/engine/reference/commandline/login/#credentials-store

Login Succeeded
jimisola@turing:~/cloud/dev/clones/github/unoconv/unoserver-docker (feature/create_docker_image)$ docker push ghcr.io/unoconv/unoserver-docker:0.1.0-beta
The push refers to repository [ghcr.io/unoconv/unoserver-docker]
357c49e58e8a: Preparing
0beb6c373949: Preparing
df7ba8c99eea: Preparing
a68f53ff4728: Preparing
d202972c9376: Preparing
c2db65e77a8c: Waiting
41573c240793: Waiting
a1a273a33cc7: Waiting
597500ab4e75: Waiting
ded7a220bb05: Waiting
denied: permission_denied: create_package

I don't know anything about Docker packages, so I have no opinion.
It seems that to create packages you have to be an organization member, so I sent invites.

@regebro Yes. I could push now, so I pushed 0.1.0-beta manually. This issue is about adding GitHub Actions to automate the deployment.
For some reason Packages is not public and the "Setting is disabled by organization administrators."
I don't have enough privileges to change the settings since I can't access package settings for this organization (I think that this would be the direct link comparing with other open source projects that I'm involved in).
Can you activate it or give me permissions to do it? That said, I think there are other settings under "Code, planning, and automation" that needs change as well. Not sure yet though as I'm new to this part of GitHub.

OK, you should be able to publish it now.


[FIX] Root-finding issue

Tickets addressed: None
Review: By commit
Merge strategy: Merge (no squash)

Description

@mattdailis and @pranav-super encountered an issue with root-finding. The case involved a 0-duration uncontrollable activity and a non-singleton start interval (and no end-time constraint).
Although the secant method might diverge or not find a zero, a review of the code has shown room for improvements and necessary fixes. I am gonna comment on the changes directly below.
I have replicated these changes to the double version of the algorithm.
Verification

A test has been added to illustrate the specific case where no solution was found. Other tests have been modified.
Documentation

None.
Future work

None.

FYI, hoping to dust off this PR and give it a review today :+1:

I have integrated the changes to tests that @pranav-super made (thanks!) on https://github.com/NASA-AMMOS/aerie/tree/origin/FIX--uncontrollable-activity-wo-end-constraint-and-updated-tests and made the requested changes.


LVGL port should not block rendering thread in display flush callback

Is your enhancement proposal related to a problem? Please describe.
Zephyr's LVGL port currently calls display_write from the display flush callback. This API blocks the calling thread until the display framebuffer is written. Since LVGL calls the flush callback from the rendering thread, this results in the rendering itself being blocked while the framebuffer is written to the display.
Describe the solution you'd like
Our LVGL port should ideally do the following:

spawn a background thread or workqueue at init
in the display flush callback, submit the provided LVGL buffer to the workqueue
the workqueue should call display_write, then call lv_disp_flush_ready when the write is completed.
we should additionally provide a wait_cb to LVGL, that waits for the workqueue to call lv_disp_flush_ready (this can be achieved with a semaphore)

Describe alternatives you've considered
We could modify the display API to add some form of async API, which takes a callback to notify of render completion. This method would potentially complicate the display API, and LVGL would need a way to fallback to the traditional display_write API if there was no ASYNC API available.

cc @pdgendt


Windows: dropping the archive contents (folders with files inside) from outside creates folders, but not files

The same works fine when dropping into Explorer or Total Commander.

Looks like the copying must be done synchronously inside the drop event handler. Once the handler returns, the files are deleted.

Related to #79


Interesting

I hope you know what you are doing. I hope you realize that if you release this that apple will patch the exploits when 10.3 is officially released If they notice and or are smart enough.

some one have tested ?

i agree dumb to public this till 10.3 is public.

i will test to day

Would love to test on my iPhone 7 plus
Sent from my iPhone

On Mar 3, 2017, at 12:02 PM, TiMb3rLanD<EMAIL_ADDRESS>wrote:
i will test to day
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I want to test this how i can test this on my iphone 6 plus which is on ios 10.3 beta 3 . Please i want to test .

Not worcking on iPhone 7 i just tested

@TiMb3rLanD Did you see next to the xcode project it says yalu102 code for now.
In the commits. Thats why it doesn't work.

Hopefully you get this running the real dev seems to be some type of child that cares more about his crappy music that anyone could make instead of stabilizing his jailbreak code. I respect him for releasing what he did but he also told people that it would be coming to 10.2 on their iphone 7's and people purposely updated and they got screwed because of it.
Wait a bit till it's outta beta though and then release if you do have anything legit

The offsets are for iOS 1.2

iOS 10.2

Once I have finished the project, I plan to pass the project to a different team that is more dedicated to the project with stability and device support.
I don't plan to release 10.3 BETA jailbreak.

@devapple Yeah I know what you will do. Tell people you have an exploit, wait for a jailbreak to release, tell them this was the team that you sent the exploits. 😂

@jakeajames xd

Hey,
I just signed the petition "federal government of canada: Cancel rent and
mortgage payments during Covid-19" and wanted to see if you could help by
adding your name.
Our goal is to reach 1,000,000 signatures and we need more support. You can
read more and sign the petition here:
http://chng.it/DmcjBr9cKP
Thanks!
Adam


Clarify initialProps in withHandlers

What is the purpose of initialProps? When is it expected to be different from the props passed to individual handlers? And when should library user care / use it? Could you please provide a bit of clarification?

initialProps are the props that are passed to you component for the first time and props passed to handler are the ones that will be passed in each consecutive render.
In given example:
const Counter = compose(
    withState('counter', 'changeCounter', 0),
    withHandlers(initialProps => {
        return {
            handleEvent: props => event => changeCounter(props.counter + 1)
        }
    })
)(CounterComponent);

<Counter title="My Counter" />

initialProps will be always { counter: 0, title: "My Counter" }
so if you would use it for changeCounter call you would always get 0 + 1 .

initialProps is passed just for convenience. You can use it to bootstrap handlers.

Gotcha. Thank you for the clarification!


Add score

Fixes #96

I know you didn't mark this for review, but I wanted to just chime in! 😬

Please do :) I want to give it another pass in the morning, because I’m not happy how updateStatus is now setting status, processingStage, and score. I’ll probably at least want to rename this to updatePackage but I ran out of time to wrap all that up :)

Oh, and I might also just tack on the oder by clause in the search query.

Ok, this is good to go now!

That's good to go now!


Getting Started Tutorial

Need to add at least a "getting started" tutorial

Done! https://www.youtube.com/watch?v=49ilsmKkVkA


pass configured input filter plugin manager to generated input filter factories

pass configured input filter plugin manager to generated input filter factories to allow for complex input filter nesting. this enables reuse of named input filter services within nested input filter contexts.
i added more logic in the factory than i had originally intended, in order to preserve backwards compatibility.

You've added 3 new conditions however there's only 1 test.  Should be at least 5.

We are adopting SM v3 across all repositories and I'll wait to this task to be over before merge this

@Maks3w thanks for pointing out the lack of path coverage. i was able to reduce a bit of the complexity and i think my update now includes the line and path coverage you expect.
since it sounds like this must wait, would you like me to open a new pull request to develop instead of master?
do you know where i can find information on when SM v3 will be completed? i'm interested in reviewing the changes and contributing, if possible. do you anticipate that the new major version of this dependency will require a major version change for this package as well?

Target branch not affect to this PR to be on hold after the SM upgrade is done.
If you want you can forward that task proposing the SM adoption
Examples
https://github.com/zendframework/zend-serializer/pull/2
https://github.com/zendframework/zend-cache/pull/22
https://github.com/zendframework/zend-mvc/pull/36

#3, merged today, accomplishes this, and will release with a forthcoming 2.7.0.

excellent! thanks @weierophinney : )


[Impeller] Vulkan fidelity: gaussian blur text shadows.

Current working theory is this is a failure in render pass concurrency. We should verify that we're either using the correct synchronization primitives or that we are setting up implicit dependencies via subpasses.

Worth checking if we're getting any validation errors on this. Otherwise an example of using subpass dependencies is here: https://github.com/SaschaWillems/Vulkan/blob/master/examples/offscreen/offscreen.cpp

Locally I can "fix" this by disabling MSAA entirely (including the root surface). Unclear why that fixes things, but maybe there is a problem with the MSAA config?

Disabling MSAA fixes both the text shadows and all sorts of other rendering problems. i suspect there is a misconfiguration here which is causing most of the rendering problems.
Of note, the color resolve attachment is configured with store dontcare, which is incorrect, though fixing that did not seem to fix the overall issue. Though it does fix the issue in renderdoc...


tplimpl: isset should return an error on unsupported type

switch should have a default case that returns an error when an unsupported reflect.Kind is encountered.
See https://discuss.gohugo.io/t/help-understanding-isset/5577/2

Related: https://github.com/spf13/hugo/issues/3089
Thanks for fixing this!

Confirmed the fix.. now if I do isset .Site "DisqusShortname", I get:

ERROR 2017/03/01 18:19:13 Error while rendering "page posts/installing-go-toolchain.md": template: /home/kmodi/hugo/kaushalmodi.gitlab.io/themes/refined/layouts/_default/baseof.html:45:10: executing "after_main" at <isset .Site "DisqusS...>: error calling isset: unsupported type "ptr"

Reopened -- as this breaks lots of themes and the theme site. Will have to be re-evaluated.

Looks like this affects the "Casper" theme.

In "hugo-coder" theme, when I start to building site, in the command line there is this warning:
WARNING: calling IsSet with unsupported type "invalid" () will always return false.


Avoid Python in shell-scripts (e.g., kube-addons.sh) to be compatible with CoreOS.

Kubernetes v0.19.0 breaks kube-addons.sh on CoreOS because it includes some Python code. I am running a setup where Fleet installs Kubernetes on CoreOS from the official tar-ball, basically extracting and installing Kubernetes similar to how Salt does it. This works fine in Kubernetes v0.18.2, but kube-addons.sh now fails on CoreOS because of the use of Python. It would be good if system services avoid Python and other heavy interpreted languages that require big installs that might not be available on all platforms.

@yifan-gu @kelseyhightower do coreos setups include kube-addons?

/cc @bakins

@mikedanese when using kube-up.sh, we still use Debian (or Ubuntu) for the master node which handles the add-ons.

We really want to rewrite kube-addons.sh in Go, but it's not going to land until after 1.0. cc @marekbiskup .

We really want to rewrite kube-addons.sh in Go, but it's not going to land until after 1.0. cc @marekbiskup .

Good to know. But CoreOS production image does not have go binaries either...

You don't need Go binaries. If we rewrite it in Go, we'll compile it and
ship it as an executable like everything else.
On Jun 16, 2015 5:50 PM, "Yifan Gu"<EMAIL_ADDRESS>wrote:

We really want to rewrite kube-addons.sh in Go, but it's not going to land
until after 1.0. cc @marekbiskup https://github.com/marekbiskup .
Good to know. But CoreOS production image does not have go binaries
either...
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/9849#issuecomment-112615201
.

@zmerlynn Awesome! :+1:

@erimatnor, we will get rid of this python by #9470, but surely after 1.0 (this will be one of my first tasks after 1.0).
Is this issue a blocker for 1.0? If so we'll have to workaround it quickly.
Python is used in bash to extract fields from yamls. Maybe by writing a small binary that does the same job.
Could you also tell me how I can reproduce the problem? (So far I used GCE installations only.)

@thockin @lavalamp

Here are the relevant places where we currently use Python (i.e. stuff that might be used on CoreOS):

https://github.com/GoogleCloudPlatform/kubernetes/blob/41545d0a66e79e5747302f81400b5909514b6276/cluster/gce/util.sh [in get-password]
https://github.com/GoogleCloudPlatform/kubernetes/blob/5520386b180d3ddc4fa7b7dfe6f52642cc0c25f3/build/json-extractor.py [this is a Python script; I'm not sure how this is used]
https://github.com/GoogleCloudPlatform/kubernetes/blob/82aa8f998445ec49bf9756f77d2ffadf317965c6/cluster/aws/coreos/util.sh [in detect-minion-image]
https://github.com/GoogleCloudPlatform/kubernetes/blob/5520386b180d3ddc4fa7b7dfe6f52642cc0c25f3/cluster/saltbase/salt/_states/container_bridge.py [IIUC this is a pretty core part of running containers; how does it work without Python?]
https://github.com/GoogleCloudPlatform/kubernetes/blob/5aa0219adad149353c0b3fbd5c18c0e5fbd5c7ad/cluster/gce/configure-vm.sh [this is used for some simple text processing--we should be able to replace it with shell or awk?]
https://github.com/GoogleCloudPlatform/kubernetes/blob/5596e6f789c92ff8589ce84e30cd5c82d7214966/cluster/saltbase/salt/kube-addons/kube-addons.sh [same as above]
https://github.com/GoogleCloudPlatform/kubernetes/blob/8a9e0e00bfeb938d7e701268dfd70b8f5641e5e8/cluster/saltbase/salt/kube-addons/kube-addon-update.sh [same as above]

cc/ @kelseyhightower @philips @brendandburns It is pretty bad at the last minutes we break coreos on different cloud providers. I believe it still works on GCE since I leave the master node using Debian by default. Supporting CoreOS on different cloud providers is required for 1.0 release or not?

Yeah, it would be good if someone could explain the scope of this issue, because I'm very confused. As you can see, we already have python code that surely is running even on CoreOS setups. I don't understand what's special about the kube-addons scripts, or (like @dchen1107 asked) which cloud providers (and/or bare metal) this issue affects. Would be good to get more details ASAP.

Just to be clear, if we don't figure this out Kubernetes v1.0 might be broken on CoreOS.  We really REALLY don't want to do that, but we clearly do not have enough coverage to call CoreOS a first-tier supported distro right now.  Help us, CoreOS folks.

@davidopp Thanks for find all places in the code using python.
Actually only last two listed by https://github.com/GoogleCloudPlatform/kubernetes/issues/9849#issuecomment-112940384: kube-addons.sh and kube-addon-update.sh has the issues since both are required to run on coreos node. The fix should be simple similar to what I did for running minion-node with coreos.
I am busy for now. But if it is required for 1.0 and CoreOS folks cannot get to it, I could take care of it sometimes tomorrow.

Thanks for the details. But I don't understand what is special about the kube-addons* scripts. They run on the master, right? Likewise doesn't cluster/gce/configure-vm.sh (which uses python) also run on the master? It is called from here
https://github.com/GoogleCloudPlatform/kubernetes/blob/4d251212065ffa6b797f3991fb572e4d3522294a/cluster/gce/coreos/helper.sh

@davidopp that is why I am asking earlier coreos on which cloudprovider? Obviously it is not on gce, because like what i said above, I didn't spend time on converting master node earlier because my goal is demo coreos + rkt, and rkt is ready for running complicated container like master components back then.
With GCE cloud provider including GKE, configure-vm.sh are running on every debian node, but no need for coreos node since I provided a cloud_init.yaml to take care the same functionalities.
On some other cloud providers, like aws, master node is using coreos dist, which tries to run kube-addons.sh. We just need to convert those into some cloud_init services ...

For CoreOS in ./cluster, none of the python ever runs on a CoreOS system. It either runs on the client calling kube-up or on the master, which is still Ubuntu/Debian when using the cluster scripts.  All of the CoreOS setup is done via cloud-config using shell scripts and systemd units.
I'll go back through the GCE and AWS cluster scripts ASAP.

FYI, I am not running the "official" cloud-init that comes with Kubernetes. The reason is that those do not support security and tokens, addons, etc, which means less security and modifying official pod specs that includes things like tokens. To solve this, I hacked together some fleet unit files that installs Kubernetes on CoreOS by copying the relevant components from the tar ball, including the kube-addons.sh script that ensures that addon services work (with token support). This works fine with Kubernetes v0.18.2, but broke with v0.19.0.
It would be nice if Kubernetes supported CoreOS fully down-the-line, and not only as a showcase without the extra security, etc. That's why it would be good to keep components clean from things that do not work well on CoreOS, if possible.

Erik,
Agree 1000% - we need to get CoreOS to be a fully-supported platform on
some set of cloud provider modules.
On Wed, Jun 17, 2015 at 4:43 PM, Erik Nordström<EMAIL_ADDRESS>wrote:

FYI, I am not running the "official" cloud-init that comes with
Kubernetes. The reason is that those do not support security and tokens,
addons, etc, which means less security and modifying official pod specs
that includes things like tokens. To solve this, I hacked together some
fleet unit files that installs Kubernetes on CoreOS by copying the relevant
components from the tar ball, including the kube-addons.sh script that
ensures that addon services work (with token support). This works fine with
Kubernetes v0.18.2, but broke with v0.19.0.
It would be nice if Kubernetes supported CoreOS fully down-the-line, and
not only as a showcase without the extra security, etc. That's why it would
be good to keep components clean from things that do not work well on
CoreOS, if possible.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/9849#issuecomment-112981013
.

Btw, the reason I didn't use kube-up.sh for CoreOS is that it is a mixed environment with the master still running Salt, etc. (correct me if I am wrong). I prefer a pure CoreOS environment with the master also running CoreOS and management via Fleet for configuration (the "CoreOS way"). This keeps things simple and unified. Using Fleet has also the benefit of making Kubernetes easier to upgrade without rebooting the machines and making changes to the cloud-init. I wouldn't mind sharing my Fleet unit files if that helps, but the installation is a bit of a hack at this point. However, if a Fleet deployment would become an officially supported way of running Kubernetes I am sure things could be cleaned up without too much work.

We (CoreOS) are working on "official" Kubernetes on CoreOS documentation, scripts, configs, and recommendations. This will cover initial install, upgrades, etc.  The current scripts in ./cluster were the fast path to get the e2e tests running on CoreOS.  The add-ons do work on CoreOS, just not using the current tooling in this repo. An official recommended way of deploying the add-ons will be included in our work.
@philips @kelseyhightower any comments?
@erimatnor I'd like to see your Fleet unit files.  I'm interested in what the community is doing with the toolset.

@bakins I think the first step here is to highlight what is broken on CoreOS as of 0.19.0 so we can possibly workaround it before 1.0.

@thockin @dchen1107 @davidopp Say we are able to find the areas where the kube-addons.sh script does not work on CoreOS, what is deadline to get a fix in place to remain a fully support OS?

@thockin @dchen1107 @davidopp It would also help if we clarify what being a supported OS means. Does that mean kubeup.sh and kube-addons.sh scripts must work for each supported OS? I would also imagine a requirement for all the e2e tests to pass as well. Thanks.

@bakins and those interested.
Put my scripts, cloud-init and Fleet files here:
https://github.com/iobeam/coreos-kubernetes

@kelseyhightower, @erictune is working a suite of conforming tests for cloud providers based on our current e2e-test suites, but not limited to it, so we and kubernetes community can maintain so many different cloud providers. We should have that as soon as possible, but I don't think that is in 1.0 scope.
CoreOS distro makes the problem even more interesting, since each provider can have different OS distros available. Today GCE and GKE by default are using Debian, and AWS has CoreOS support, but not default either. But fully supporting CoreOS definitely in our roadmap, if we could shoot for 1.0 roadmap, that is great, but I don't think it is required for 1.0 though.
For this particular issue, since it is pretty safe to other cloud providers and OS distros, I can accept the workaround by end of this week.
cc/ @brendandburns

Until we have conformance "supported" really means one of two things:  a)
That people use and develop on it every day b) that some specific
kubernetes binary release works with some specific set of
tools/instructions to reliably bring up a cluster
On Thu, Jun 18, 2015 at 1:57 PM, Dawn Chen<EMAIL_ADDRESS>wrote:

@kelseyhightower https://github.com/kelseyhightower, @erictune
https://github.com/erictune is working a suite of conforming tests for
cloud providers based on our current e2e-test suites, but not limited to
it, so we and kubernetes community can maintain so many different cloud
providers. We should have that as soon as possible, but I don't think that
is in 1.0 scope.
CoreOS distro makes the problem even more interesting, since each provider
can have different OS distros available. Today GCE and GKE by default are
using Debian, and AWS has CoreOS support, but not default either. But fully
supporting CoreOS definitely in our roadmap, if we could shoot for 1.0
roadmap, that is great, but I don't think it is required for 1.0 though.
For this particular issue, since it is pretty safe to other cloud
providers and OS distros, I can accept the workaround by end of this week.
cc/ @brendandburns https://github.com/brendandburns
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/9849#issuecomment-113287858
.

Do we consider this a 1.0 blocker? By "this" I mean
https://github.com/GoogleCloudPlatform/kubernetes/issues/9849#issuecomment-113161032
("We (CoreOS) are working on "official" Kubernetes on CoreOS documentation, scripts, configs, and recommendations. This will cover initial install, upgrades, etc. The current scripts in ./cluster were the fast path to get the e2e tests running on CoreOS. The add-ons do work on CoreOS, just not using the current tooling in this repo. An official recommended way of deploying the add-ons will be included in our work.")
Do we have an ETA for that work?
The reason I ask is that we have been letting this issue (and related issue #9470) wallow in 1.0-candidate for several days. It does sound like we can move #9470 to 1.0-post though, since @erimatnor implied they will make everything work.

@davidopp I wouldn't I'd let any docs work we are doing hold up those PR's.

Sorry to be pedantic, but I still don't understand the status of this issue.
@marekbiskup 's PR (listed above) looks too risky to me for us to push in at this point. But it's also not clear to me (1) whether we're actually broken on CoreOS or we just broke clusters created by @erimatnor 's custom scripts, and (2) if we're broken on CoreOS, do we need to fix it and if so what is the plan for doing so?
@bakins @kelseyhightower could one of you please clarify?

(And by broken, I mean for addon pods only, of course.)

@davidopp From my understading,
(1) Having python scripts in addon.sh (as the last two cases you mentioned here) will break the master node if it is using CoreOS. We are not breaking the current CoreOS cluster on gce/aws as the master node is still ubuntu (I am glad to dive into it and make the cluster fully CoreOS).
(2) As @jlowdermilk pointed out (https://github.com/GoogleCloudPlatform/kubernetes/pull/10223#issuecomment-114620736) Rewriting kube-addon.sh sounds better and easier to me.

Edit: CoreOS on gce has python installed, so won't break anyway. And @bakins is working on this.

@yifan-gu Not quite accurate. In the list of Python candidates that was dumped above, I see at least one shebang that expects Python in-path, because it shebangs via env. My comment to you about Google vendoring Python on GCE is related to their internal stuff, and any Python code needs to reach that interpreter directly or rewrite a shebang. Google does this; their daemons are shebanged /usr/bin/env python but they are working around it by invoking the interpreter at /usr/share/oem/python/bin/python2.7 directly.
Anything that does #!/usr/bin/env python will absolutely break on CoreOS out-of-the-box because of the nature of /usr, Python's usual home at /usr/bin/python, Python not in path under OEM, etc...

I'm with David - I don't know the status of this - is it a real issue right now for the currently supported platforms?

@yifan-gu @bakins @kelseyhightower
Could one of you verify that CoreOS on GCE and AWS currently works, including the addons? If so, we can move this issue to post-1.0. We're getting really down to the wire for 1.0, so if we need to do something to make this work, it would be really good to know now.

@davidopp Currently, ./cluster/kube-up.sh can create worker nodes on CoreOS for AWS and GCE if certain env vars are set. The master is still Debian and add-ons are set up there. Kubelet, kube-proxy, and the pods for the add-ons run just fine on the CoreOS nodes.

@bakins Thanks. So IIUC the only thing that's critical for 1.0 is to document the env vars you need to set for CoreOS before running kube-up.sh? I didn't see any env vars mentioned in the first few docs at
https://github.com/GoogleCloudPlatform/kubernetes/blob/8813c955182e3c9daae68a8257365e02cd871c65/docs/getting-started-guides/coreos.md

I'm moving this to the post 1.0 category.  Scream if I am misinterpreting.

Wasn't @dchen1107 saying there was something to do, and she would do it?

It looks like the stuff alluded to earlier in the thread is released now?
https://coreos.com/blog/official-kubernetes-on-coreos/
We should link to this from
https://github.com/kubernetes/kubernetes/blob/master/docs/getting-started-guides/coreos.md
I would think.

cc @robszumski

@davidopp discussing this in https://github.com/kubernetes/kubernetes/issues/14205

@dchen1107 @bakins Can we close this issue?

@davidopp Not yet, I am working on this.

Suggest we close this now:

kube-addons runs in a container
kube-up is in maintenance mode
GCI is very similar to CoreOS, and is now under e2e testing, so we know it is possible.

Agree.


[BUG] Trace working but logs not

I have configured as documentation and the metrics and trace is working, but I don´t see logs
Agent Environment
This error ocorrs on my linux machine but also on azure app service container
docker exec {MY_CONTAINER} agent status
OCI runtime exec failed: exec failed: unable to start container process: exec: "agent": executable file not found in $PATH: unknown
Below my docker file
FROM python:3.8-buster

ARG VERSION

RUN mkdir -p /root/.opencensus/.azure/gunicorn

COPY --from=datadog/serverless-init:1 /datadog-init /usr/bin/datadog-init

ADD requirements.txt .
RUN pip install -r requirements.txt

ENTRYPOINT ["/usr/bin/datadog-init"]

RUN mkdir /code
WORKDIR /code
ADD src /code/
ADD . /code/

RUN echo ${VERSION}
ENV DD_VERSION=${VERSION}
ENV DD_SERVICE={MY_SERVICE}
ENV DD_ENV=production
ENV DD_VERSION=test-log-dd2
ENV DD_API_KEY={MY_KEY}
ENV DD_TRACE_ENABLED=true
ENV DD_LOG_LEVEL=debug
ENV DD_LOGS_CONFIG_CONTAINER_COLLECT_ALL=true
ENV DD_LOGS_ENABLED=true

COPY init.sh /usr/local/bin/

RUN chmod u+x /usr/local/bin/init.sh

CMD ["/usr/local/bin/init.sh"]

And in init.sh
#!/bin/bash

ddtrace-run gunicorn --worker-tmp-dir /dev/shm --max-requests $GUNICORN_MAX_REQUESTS --bind <IP_ADDRESS>:$PORT -k gevent --chdir src wsgi:app

These are my logs when I start the app
WARNING: Published ports are discarded when using host network mode
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | INFO | Loading proxy settings
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | DEBUG | 'use_proxy_for_cloud_metadata' is enabled: adding cloud provider URL to the no_proxy list
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | INFO | Starting logs-agent...
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | INFO | logs-agent started
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | DEBUG | Adding Datadog Agent Log Source
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | INFO | Starting to load the configuration
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | WARN | Error loading config: Config File "datadog" Not Found in "[]"
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | INFO | 0 Features detected from environment:
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | DEBUG | Error loading config: Config File "datadog" Not Found in "[]"
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | DEBUG | Using a SyncForwarder with a 5s timeout
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | INFO | Retry queue storage on disk is disabled
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | INFO | Starting to load the configuration
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | WARN | Error loading config: Config File "serverless" Not Found in "[/var/task/datadog.yaml]"
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | INFO | Creating TimeSampler #0
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | INFO | 0 Features detected from environment:
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | DEBUG | Forwarder started
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | DEBUG | Demultiplexer started
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | INFO | Loaded configuration: /var/task/datadog.yaml
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | DEBUG | Setting DefaultEnv to "production" (from 'env' config option)
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | DEBUG | 'telemetry.dogstatsd.aggregator_channel_latency_buckets' is empty, falling back to default values
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | DEBUG | 'telemetry.dogstatsd.listeners_latency_buckets' is empty, falling back to default values
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | DEBUG | 'telemetry.dogstatsd.listeners_channel_latency_buckets' is empty, falling back to default values
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | DEBUG | dogstatsd-udp: <IP_ADDRESS>:8125 successfully initialized
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | INFO | Dogstatsd workers and pipelines count:  10  workers,  1  pipelines
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | INFO | Dogstatsd configured to run with 10 workers and 1 pipelines
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | DEBUG | DogStatsD will run 10 workers
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | INFO | dogstatsd-udp: starting to listen on <IP_ADDRESS>:8125
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | INFO | Dogstatsd workers and pipelines count:  10  workers,  1  pipelines
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | INFO | Dogstatsd configured to run with 10 workers and 1 pipelines
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | INFO | Dogstatsd workers and pipelines count:  10  workers,  1  pipelines
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | INFO | Dogstatsd configured to run with 10 workers and 1 pipelines
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | INFO | Dogstatsd workers and pipelines count:  10  workers,  1  pipelines
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | INFO | Dogstatsd configured to run with 10 workers and 1 pipelines
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | INFO | Dogstatsd workers and pipelines count:  10  workers,  1  pipelines
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | INFO | Dogstatsd configured to run with 10 workers and 1 pipelines
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | INFO | Dogstatsd workers and pipelines count:  10  workers,  1  pipelines
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | INFO | Dogstatsd configured to run with 10 workers and 1 pipelines
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | INFO | Dogstatsd workers and pipelines count:  10  workers,  1  pipelines
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | INFO | Dogstatsd configured to run with 10 workers and 1 pipelines
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | INFO | Dogstatsd workers and pipelines count:  10  workers,  1  pipelines
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | INFO | Dogstatsd configured to run with 10 workers and 1 pipelines
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | INFO | Dogstatsd workers and pipelines count:  10  workers,  1  pipelines
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | INFO | Dogstatsd configured to run with 10 workers and 1 pipelines
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | INFO | Dogstatsd workers and pipelines count:  10  workers,  1  pipelines
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | INFO | Dogstatsd configured to run with 10 workers and 1 pipelines
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | INFO | Dogstatsd workers and pipelines count:  10  workers,  1  pipelines
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | INFO | Dogstatsd configured to run with 10 workers and 1 pipelines
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | DEBUG | otlp endpoint disabled
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | DEBUG | Launching subprocess [/usr/local/bin/init.sh]
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | INFO | Starting Agent with processor trace buffer of size 0
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | DEBUG | Stats writer initialized (climit=20 qsize=83)
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | INFO | Receiver configured with 6 decoders and a timeout of 1000ms
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | INFO | Trace writer initialized (climit=100 qsize=1)
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | DEBUG | [pipeline_stats] Creating proxy handler
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | DEBUG | [pipeline_stats] Intake URL %s https://trace.agent.datadoghq.com/api/v0.1/pipeline_stats
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | DEBUG | [pipeline_stats] Creating reverse proxy
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | INFO | Listener started with 1000 maximum connections.
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | INFO | Listening for traces at http://localhost:8126
2024-07-15 18:41:07 UTC | SERVERLESS_INIT | DEBUG | Starting concentrator
[2024-07-15 18:41:08 +0000] [20] [INFO] Starting gunicorn 19.9.0
[2024-07-15 18:41:08 +0000] [20] [INFO] Listening at: http://<IP_ADDRESS>:5000 (20)
[2024-07-15 18:41:08 +0000] [20] [INFO] Using worker: gevent
/usr/local/lib/python3.8/os.py:1023: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used
return io.open(fd, *args, **kwargs)
[2024-07-15 18:41:08 +0000] [25] [INFO] Booting worker with pid: 25
INFO       2024-07-15 18:41:08,345 server          register_blueprints                  39  : Registering blueprints
INFO       2024-07-15 18:41:08,359 server          register_blueprints                  48  : Blueprints registered
2024-07-15 18:41:09 UTC | SERVERLESS_INIT | INFO | Container metrics provider discovery process finished
2024-07-15 18:41:10 UTC | SERVERLESS_INIT | DEBUG | Received a Flush trigger
2024-07-15 18:41:10 UTC | SERVERLESS_INIT | DEBUG | Demultiplexer: sendIterableSeries: start sending iterable series to the serializer
2024-07-15 18:41:10 UTC | SERVERLESS_INIT | DEBUG | Sending sketches payload : {"metric":"datadog.serverless_agent.enhanced.cold_start","tags":["datadog_init_version:1.2.2","_dd.compute_stats:1","env:production","service:rc-contracts-api-us","version:test-log-dd"],"host":"","interval":10,"points":[{"sketch":{"summary":{"Min":1,"Max":1,"Sum":1,"Avg":1,"Cnt":1}},"ts":1721068860}]}
2024-07-15 18:41:10 UTC | SERVERLESS_INIT | DEBUG | The payload was not too big, returning the full payload
2024-07-15 18:41:10 UTC | SERVERLESS_INIT | DEBUG | The payload was not too big, returning the full payload
2024-07-15 18:41:11 UTC | SERVERLESS_INIT | INFO | Successfully posted payload to "https://7-54-0-app.agent.datadoghq.com/api/v1/series" (202 Accepted), the agent will only log transaction success every 500 transactions
2024-07-15 18:41:11 UTC | SERVERLESS_INIT | DEBUG | SyncForwarder has flushed 1 transactions
2024-07-15 18:41:11 UTC | SERVERLESS_INIT | DEBUG | Demultiplexer: sendIterableSeries: stop routine
2024-07-15 18:41:11 UTC | SERVERLESS_INIT | DEBUG | SyncForwarder has flushed 1 transactions
2024-07-15 18:41:12 UTC | SERVERLESS_INIT | DEBUG | Send messages for pipeline logs (msg_count:8, content_size=2792, avg_msg_size=349.00)
2024-07-15 18:41:12 UTC | SERVERLESS_INIT | INFO | No data received
2024-07-15 18:41:13 UTC | SERVERLESS_INIT | DEBUG | Received a Flush trigger
2024-07-15 18:41:13 UTC | SERVERLESS_INIT | DEBUG | Demultiplexer: sendIterableSeries: start sending iterable series to the serializer
2024-07-15 18:41:13 UTC | SERVERLESS_INIT | DEBUG | The payload was not too big, returning the full payload
2024-07-15 18:41:13 UTC | SERVERLESS_INIT | DEBUG | SyncForwarder has flushed 1 transactions
2024-07-15 18:41:13 UTC | SERVERLESS_INIT | DEBUG | Demultiplexer: sendIterableSeries: stop routine
2024-07-15 18:41:16 UTC | SERVERLESS_INIT | DEBUG | Received a Flush trigger
2024-07-15 18:41:16 UTC | SERVERLESS_INIT | DEBUG | Demultiplexer: sendIterableSeries: start sending iterable series to the serializer
2024-07-15 18:41:16 UTC | SERVERLESS_INIT | DEBUG | The payload was not too big, returning the full payload
2024-07-15 18:41:16 UTC | SERVERLESS_INIT | DEBUG | SyncForwarder has flushed 1 transactions
2024-07-15 18:41:16 UTC | SERVERLESS_INIT | DEBUG | Demultiplexer: sendIterableSeries: stop routine
2024-07-15 18:41:19 UTC | SERVERLESS_INIT | DEBUG | Received a Flush trigger

More one information
I see logs when the app shows internal error (500), like this code:
import logging
import flask_restful as restful
from flask_restful import reqparse
from flask import jsonify

from helpers import authentication_required

FORMAT = ('%(asctime)s %(levelname)s [%(name)s] [%(filename)s:%(lineno)d] '
          '[test] '
          '- %(message)s')
logging.basicConfig(format=FORMAT)
log = logging.getLogger(__name__)
log.level = logging.INFO

class GetAllContracts(restful.Resource):
    @authentication_required
    def get(self, **kwargs):
        print('test 343')
        log.info('Hello, World!')

        zero = 0
        um = 1
        divisao = um / zero
        print(divisao)

This is exactaly what the log shows when the app is started
2024-07-15 18:41:11 UTC | SERVERLESS_INIT | INFO | Successfully posted payload to "https://7-54-0-app.agent.datadoghq.com/api/v1/series" (202 Accepted), the agent will only log transaction success every 500 transactions

Hey @StephanyBatista 👋  Apologies for the inconvenience here but I suspect this is related to a bug introduced in v1.2.3. We recognized the bug and released v1.2.4 based on the previous working version. Since you are using COPY --from=datadog/serverless-init:1 I suspect you pulled in the version with the bug before we recognized it. Could you confirm if you are still missing logs after the update?
https://github.com/DataDog/datadog-agent/issues/27502.

Hi, Thanks for help me.
Now I'm seeing the log just on live search screen, but as one error, not info, do you know what could be?

Reading the documentation, I understood that this just work on azure container ou GCP, so in my local machine is normal this error?
If I publish to these clouds will work?

Hey @StephanyBatista I'm not sure I understand the error you are seeing. If you continue to have issues with that, feel free to reach out to support. I think the original reason this issue was opened was addressed and I'm going to close this for now. Thanks again for reaching out and sorry for the inconvenience.


bug: running Move2Kube transform on Windows machine throws an error about qamapping file not being present

Overview
Running the Move2Kube CLI in a Windows 11 machine (inside Cygwin and Powershell) causes a crash.
https://github.com/konveyor/move2kube/blob/c1a0f8a4db1014370e39d15a27a022a019e0e9c6/cmd/utils.go#L89-L125
Steps to reproduce

Run move2kube transform

Actual behavior
Crash saying the qamappings.yaml file doesn't exist.
Expected behavior
Should print the usage info
Environment

OS: Windows 11
Version: https://github.com/konveyor/move2kube/releases/tag/v0.3.14

Related https://github.com/konveyor/move2kube/commit/c8164a0733989ac93ef68bb8cc2431cbdc80e115#diff-d23edd34a745e08894f91860da46601946a8f0ae3a970d794c981d4014f30614L57-L61

The error could be due to this hard coded path built-in/qa https://github.com/konveyor/move2kube/blob/c1a0f8a4db1014370e39d15a27a022a019e0e9c6/cmd/utils.go#L116

https://github.com/golang/go/issues/45230#issuecomment-806554753


Taking everything to live.

Docs Build status updates of commit 1766691:
:warning: Validation status: warnings

File
Status
Preview URL
Details

advocates/index.html.yml
:warning:Warning
View
Details

advocates/brandon-minnick.yml
:white_check_mark:Succeeded
View

advocates/map.yml
:white_check_mark:Succeeded
View

advocates/maxime-rouiller.yml
:white_check_mark:Succeeded
View

advocates/media/profiles/pierre-roman.jpg
:white_check_mark:Succeeded

advocates/media/profiles/pierre-roman.png
:white_check_mark:Succeeded
View

advocates/pierre-roman.yml
:white_check_mark:Succeeded
View

validation/AdvocateValidation.csproj
:white_check_mark:Succeeded

validation/CloudAdvocateYamlModel.cs
:white_check_mark:Succeeded

validation/ImageService.cs
:white_check_mark:Succeeded

advocates/index.html.yml

Line 10, Column 8: [Warning-file-not-found] Invalid file link: './map'.
Line 12, Column 8: [Warning-file-not-found] Invalid file link: './tweets'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 35d4819:
:warning: Validation status: warnings

File
Status
Preview URL
Details

advocates/index.html.yml
:warning:Warning
View
Details

advocates/brandon-minnick.yml
:white_check_mark:Succeeded
View

advocates/map.yml
:white_check_mark:Succeeded
View

advocates/maxime-rouiller.yml
:white_check_mark:Succeeded
View

advocates/media/profiles/pierre-roman.jpg
:white_check_mark:Succeeded

advocates/media/profiles/pierre-roman.png
:white_check_mark:Succeeded
View

advocates/pierre-roman.yml
:white_check_mark:Succeeded
View

advocates/toc.yml
:white_check_mark:Succeeded
View

validation/AdvocateValidation.csproj
:white_check_mark:Succeeded

validation/CloudAdvocateYamlModel.cs
:white_check_mark:Succeeded

validation/ImageService.cs
:white_check_mark:Succeeded

advocates/index.html.yml

Line 10, Column 8: [Warning-file-not-found] Invalid file link: './map'.
Line 12, Column 8: [Warning-file-not-found] Invalid file link: './tweets'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Where is my Static Website Content stored?

** Which Category is your question related to? **
Amplify Console Hosting
If I'm using the Amplify Console to host a Static Website, where is it stored? It doesn't look like there is an S3 bucket being used by the Amplify Console to host the website?
If we use the Amplify CLI add hosting, it will use an S3 bucket, does the Amplify Console do something similar, but we just can't access it?

The Amplify Console provides fully managed hosting so you get features such as instant cache invalidation, atomic deploys, branch-based deployments, easy custom domain setup and more.
 See:https://aws.amazon.com/amplify/console/pricing/

Do we have any control over the CloudFront distribution? Am I able to utilize AWS Web Application Firewall rules or anything like that?
I am just curious about the security details of the "Managed Hosting".


I love hexo, and your client, but would really like...

... it to be in english. Is this possible? I don't mind helping with translations if you need it. We could translate through a service and I can check for proper language use?

hi，I have already supported the English version.
I18n files:  https://github.com/gaoyoubo/hexo-client/tree/master/src/locales
You can switch language in Settings


Microk8s config get should return configuration with containing all servers with multi node deployment

Hi I'm using microk8s 1.28 and noticed that config get returning configuration only for the node it is executed.
Which means if this node goes down client with this config will lost access to k8s cluster.
It would be more convenient to generate multi server configuration to avoid such issue

Found https://github.com/kubernetes/kubectl/issues/1121


GH #113: stop_name isn't required

Logs w/o change:
2024-04-23 10:23:06.336 [main] INFO  c.conveyal.gtfs.model.Entity$Loader - Loading GTFS table stop_times from stop_times.txt
2024-04-23 10:23:08.005 [main] INFO  c.conveyal.gtfs.model.Entity$Loader - Record number 500.0k
2024-04-23 10:23:09.571 [main] INFO  c.conveyal.gtfs.model.Entity$Loader - Record number 1.0M
2024-04-23 10:23:10.733 [main] INFO  c.conveyal.gtfs.model.Entity$Loader - Record number 1.5M
2024-04-23 10:23:11.782 [main] INFO  c.conveyal.gtfs.model.Entity$Loader - Record number 2.0M
2024-04-23 10:23:12.757 [main] INFO  c.conveyal.gtfs.model.Entity$Loader - Record number 2.5M
2024-04-23 10:23:14.027 [main] INFO  c.conveyal.gtfs.model.Entity$Loader - Record number 3.0M
2024-04-23 10:23:15.106 [main] INFO  c.conveyal.gtfs.model.Entity$Loader - Record number 3.5M
2024-04-23 10:23:16.401 [main] INFO  c.conveyal.gtfs.model.Entity$Loader - Record number 4.0M
2024-04-23 10:23:17.401 [main] ERROR com.conveyal.gtfs.GTFSFeed - stops line 104, field 'stop_name': No value supplied for a required column.
[more of the same errors, omitted]
2024-04-23 10:23:17.405 [main] ERROR com.conveyal.gtfs.GTFSFeed - stops line 1481, field 'stop_name': No value supplied for a required column.
2024-04-23 10:23:17.420 [main] INFO  com.graphhopper.gtfs.GtfsStorage - Calendar range covered by all feeds: 2019-09-30 till 2099-12-31

Logs w/change:
2024-04-23 10:54:38.041 [main] INFO  c.conveyal.gtfs.model.Entity$Loader - Loading GTFS table stop_times from stop_times.txt
2024-04-23 10:54:39.225 [main] INFO  c.conveyal.gtfs.model.Entity$Loader - Record number 500.0k
2024-04-23 10:54:40.458 [main] INFO  c.conveyal.gtfs.model.Entity$Loader - Record number 1.0M
2024-04-23 10:54:41.526 [main] INFO  c.conveyal.gtfs.model.Entity$Loader - Record number 1.5M
2024-04-23 10:54:42.542 [main] INFO  c.conveyal.gtfs.model.Entity$Loader - Record number 2.0M
2024-04-23 10:54:43.654 [main] INFO  c.conveyal.gtfs.model.Entity$Loader - Record number 2.5M
2024-04-23 10:54:44.812 [main] INFO  c.conveyal.gtfs.model.Entity$Loader - Record number 3.0M
2024-04-23 10:54:46.262 [main] INFO  c.conveyal.gtfs.model.Entity$Loader - Record number 3.5M
2024-04-23 10:54:47.571 [main] INFO  c.conveyal.gtfs.model.Entity$Loader - Record number 4.0M
2024-04-23 10:54:48.746 [main] INFO  com.graphhopper.gtfs.GtfsStorage - Calendar range covered by all feeds: 2019-09-30 till 2099-12-31

Code looks good, thanks!
What's happening with the git history? Can you get rid of those 4 extra commits? Or just squash and merge would work I guess

Yeah I'm not sure, might be something to do with how I made the branches locally. In any case I was just going to do a squash & merge.


Javascript Debug preview for package.json will on use the root directory??

Javascript Debug preview for package.json will on use the root directory. It should be what file is active.

VSCode Version: 1.45.1
5763d909d5f12fe19f215cbfdd29a91c0fa9208a
x64
OS Version: Windows 10

Steps to Reproduce:
https://giphy.com/embed/THrfY15EbFtiwdz9IT

Goto nested package.json
Click debug
Bug. See the list for debugging root/package.json and not root/nested/package.json

Does this issue occur when all extensions are disabled?: Yes/No

Thanks for the issue!


Fix flush argument clash with async keyword

The argument is named async - conflicts in newer versions of Python.

The commit message misses one of the required keywords hence manual close.


Add machinery to read more than one manifest file

This patch sets the stage to parse all the manifest files in a bag (not just the SHA256 manifest). Another stepping stone towards https://github.com/wellcomecollection/platform/issues/4277
In brief:

The CombinedManifest trait can store the information from all the manifests in a bag, not just one. It then has two instances (terminology?) – PayloadManifest and TagManifest, so we can distinguish these at the type level.
It stores data as Map[BagPath, VerifiableChecksum] rather than List[BagFile], which has nicer semantics and reduces the amount of duplicated information.

The CombinedManifestParser object can parse all the manifests in a bag, check their file lists are consistent, combine the information and return enough info to build a CombinedManifest.
Plus it improves the validity checking we do on manifest files, and comes with shiny tests!

This patch drops in the new parser behind the scenes of the existing BagManifest model; if that works I need to go through and plumb in the new types.

Closing as outdated; will be replaced by another PR.


Fix alias and port mapping configuration

these are sent in the form, but not used in the container config yet

Partially resolved in #26

i disabled aliasing for now #43


Release 3.0.0

Coverage decreased (-64.2%) to 35.84% when pulling 8a0480a1d7ff84ba3ef34b3415eeefb43620d95a on fixVersion into c089501834c9f8536ba6c64a86c4988da14d5ba8 on master.


Datasearch: Add ability to search for moves not in a Pokemon's moveset

Main use of this feature would be to compare the movesets of two Pokemon. For example, a user comes into Trainer Academy and asks why to use X mon over Z. Now room staff could show them the kinds of moves that X does get that Z doesn't.
I feel like this is also a readability improvement over the previous code.

Don't merge. Gonna modify to use only IDs until necessary.

Alright, uses only IDs until necessary now.

This is looking a lot better to me. My one remaining complaint is the Set operations - I know /datasearch is already a performance mess, but can we replace the cutesy one liners with for loops which are much more efficient? One example:
// lsetData = new Set([...lsetData, ...Object.keys(template.learnset)]);
for (const move of Object.keys(template.learnset)) {
  lsetData.add(move);
}

Spread syntax and all of the implicit array creation just ends up creating a lot of object churn IME.

Object.keys isn't implicit array creation? Maybe for (const move in template.learnset)?

True, it also is! I even missed one! Where's my performance dunce hat? :D

This is looking a lot better to me. My one remaining complaint is the Set operations - I know /datasearch is already a performance mess, but can we replace the cutesy one liners with for loops which are much more efficient? One example:
// lsetData = new Set([...lsetData, ...Object.keys(template.learnset)]);
for (const move of Object.keys(template.learnset)) {
  lsetData.add(move);
}

Spread syntax and all of the implicit array creation just ends up creating a lot of object churn IME.

Yeah, I can replace the one liners. I had benchmarked them beforehand, but made a call of readability (imo) over perf.

Got rid of all the implicit array creations..

diff --git a/server/chat-plugins/datasearch.js b/server/chat-plugins/datasearch.js
index 2af80d785..aec264509 100644
--- a/server/chat-plugins/datasearch.js
+++ b/server/chat-plugins/datasearch.js
@@ -1084,10 +1084,7 @@ function runMovesearch(target, cmd, canAll, message) {

        const getFullLearnsetOfPokemon = (template) => {
                if (!template.learnset) template = Dex.getTemplate(template.baseSpecies);
-         let lsetData = new Set();
-         for (const move in template.learnset) {
-                 lsetData.add(move);
-         }
+               const lsetData = new Set(Object.keys(template.learnset));

                while (template.prevo) {
                        template = Dex.getTemplate(template.prevo);
@@ -1101,10 +1098,7 @@ function runMovesearch(target, cmd, canAll, message) {

        // Since we assume we have no target mons at first
        // then the valid moveset we can search is the set of all moves.
- let validMoves = new Set();
- for (const move in Dex.data.Movedex) {
-         validMoves.add(move);
- }
+       const validMoves = new Set(Object.keys(Dex.data.Movedex));
        validMoves.delete('magikarpsrevenge');
        for (const mon of targetMons) {
                const template = Dex.getTemplate(mon.name);

For some reason I get:
error: src refspec movesearch-not-feature-implementation does not match any
error: failed to push some refs to 'git@github.com:jmclemo6/Pokemon-Showdown'

When trying to push to the branch.


Use evented list in dims take 2

Description
This PR supersedes #1486 by using the evented list in the dims.
This is a WIP right now, tests are broken, but it also seems to be quite a bit slower so I will do some performance monitoring to see what's going on.
Type of change

[x] Refactor

This PR is getting close, but I have some doubts about it. There are some nice things it does, for example you can now do
viewer.dims.point[0] = 22
viewer.dims.point[:] = [22, 0, 0]

to change the location of the sliders.
You can't do
viewer.dims.point = [22, 0, 0]

anymore, but @jni if you'd like me to I can support that (by making the setter just call viewer.dims.point[:])
You could do all sorts of weird things like try and edit the length of the list, insert, or remove elements and things would break. We could get more intense and add something like a keyword arg to our EventedList called fixed_length or something that would prevent that, though there are times when we do want to do that ourselves.
I also had to change the default behavior of the EventedList when editing like my_list[:] and how events get emitted, and now a number of tests are failing. I could revert but then the viewer.dims.point[:] =  behavior might not be supported.
Guidance here from @jni is needed

but @jni if you'd like me to I can support that (by making the setter just call viewer.dims.point[:])

I think viewer.dims.point = [...] should be supported, it's super convenient, probably my favourite way to interact with point!

I also had to change the default behavior of the EventedList when editing like my_list[:] and how events get emitted, and now a number of tests are failing. I could revert but then the viewer.dims.point[:] = behavior might not be supported.

I'm not sure about what the changes are or whether they make sense, just want to give you some quick feedback before I'm back at work next week, but imho the key is whether you can detect viewer.dims.point[:] = ... and raise a meaningful error, or whether it'll just succeed but not emit any events. The latter would be bad.
What is the current behaviour, and what would be the new behaviour? If it makes sense generally then the tests should be fixed. To me it seems that this should work and emit events and the tests should be modified to reflect that.

This is supeseded by #1919 which doesn't use the EventedList but we could add one day


Fixed bug that was preventing quoted integers from treated as integers.

I'm not sure this is needed. The "simple search" and "query documents" functions allows for quoted integers (strings).
Can you explain further about the bug? Provide an example?


Elaborate Dependencies

Hey there,
I forked the project and I'm currently building a .deb package generator (like the one for lycheeJS) for it.
What dependencies do the two commands have? Currently I depend on python-bs4, is that everything they need? Or is there sth. like curl also required?

I saw your pull request. Unless there's something I don't know, that should be the only dependency.
Thanks!


Time input field cuts AM/PM text due to short width

The default width for the time input field when showTimeInput=true is currently set to 85px in the src seen here which cuts the AM/PM text as seen in the screenshots below.
Screenshots
Firefox: 81.0.2 (64-bit)

Chrome: Version 88.0.4324.96 (Official Build) (x86_64)

To Reproduce

Go to https://reactdatepicker.com/#example-input-time
Click on the Date Picker
Inspect the time input and compare to the screenshots above

Expected behavior
Input field displays all its content without cutting out any of its text.
I would suggest removing the 85px and let the browser decide the width necessary. This is what I'm doing in my override of the CSS using inline styles with
<style>{`
  .react-datepicker__input-time-container
  .react-datepicker-time__input-container
  .react-datepicker-time__input input {
     width: unset
  }
`}</style>

I am wondering if anyone else is experiencing this issue.
Desktop

OS: macOS Catalina, Version 10.15.7
Browsers

Chrome  Version 88.0.4324.96 (Official Build) (x86_64)
Firefox 81.0.2 (64-bit)

Additional context

This seems to affect Firefox and Chrome. Safari V.14.0.1 shows a 24 hour clock so the AM/PM text is never there.
On mobile(iPhone SE) Chrome and Safari display the native time picker and 85px is more than enough to show all text content + it seems the iPhone has a smaller font-size for inputs.
This feature/variant was introduced in PR #1591 by @gautam-pahuja

Thank you for the temporary fix.  I'm am seeing the same issue after PR #1591

Thank you for the temporary fix.  I'm am seeing the same issue after PR #1591


adding my lcu project files

Description
My PR contains:

code for generating taylorization LCU circuits for hamiltonian simulation of Fermi-HUbbard. Located in src/benchq/algorithms/_taylorization_lcu.py
Test file located in tests/benchq/algorithms/test_taylorization_lcu.py
Interactive Jupyter notebook which explains LCU algorithm and how to use code, located in /other_code/Hamiltonian_Simulation_LCU.pynb

Include description of feature this PR introduces or a bug that it fixes. Include the following information:

Context: why is it needed? In case of bug, what was the cause for the bug?
Concise description of the implemented solution.
If any dependencies are added, list them and justify why they are needed.

Please verify that you have completed the following steps

[x ] I have self-reviewed my code.
[ x] I have included test cases validating introduced feature/fix.
[ x] I have updated documentation.

😍 Thanks Michał 🤩


Entertainment form for SWC spring

Need to get it started.

yo, are you on waffle yet?

had it before, but wasn't getting updates. just authorized to GH

Susan was notified for planning.  Ent form started , waiting to add dates for workshop.

requesting help to submit to RRAS AA. (i think that's what we talked about doing, instead of Susan this time?) Susan mentioned we have some $ left over from the last one, need to see how we can use the funds

Notified Susan about event.  Will get David to sign form.


updated metadata for current templates dev -> master

nice work! @KiriHoy , just a few small things to reconsider?


gopkg.toml: upgrade to client-go v8.0.0 / kubernetes v1.11.3

Fixes #693
Signed-off-by: Dave Cheney<EMAIL_ADDRESS>

This increases the number of transitive dependencies to 52 :(


Make block id type consistent in the status returned from executor status polling

Description
This PR refactors the key types in status returned from executor status polling method executor.status().
Before this PR, executor status returns a status dict, where the key of a normal running block is a provider job id, but the key of a failed block is the block id counter in executor internally. This inconsistency in block id type causes errors in monitoring (issue #1948 ). This PR addresses this inconsistency in block id type---for all blocks, their keys are the block id counter in executor internally.
This PR also renames external_block_id to block_id, and internal_block_id to job_id for ease to understand.
Note: it does not fix the issue in #1948 completely yet---upcoming PRs along with this PR will fix that.
Type of change

Bug fix (non-breaking change that fixes an issue)

@benclifford Are there any other changes you want in this PR?

@benclifford Are there any other changes you want in this PR?

This PR gives job IDs type str, but providers can return any type as a job ID, not only string.

@benclifford Are there any other changes you want in this PR?

This PR gives job IDs type str, but providers can return any type as a job ID, not only string.

I changed the HTEX one to Any

I'm a little unclear about what is going on with scale_out and scale_in in PollItem in task_status_poller.py vs the ID types that ParslExecutor is documented as returning in the docstrings.

I'm a little unclear about what is going on with scale_out and scale_in in PollItem in task_status_poller.py vs the ID types that ParslExecutor is documented as returning in the docstrings.

Fixed the docstrings in the latest commits

I've been merging this repeatedly against my benc-mypy branch to look for relevant conflicts, and it looks like they are happy together now, which is good.