MB-11102: openapi client queue workflow hhg example

Description
We want our load tests to simulate a move going through an entire workflow with service member, service counselor, TOO, TIO, and prime all interacting with the move.
We also want our load tests to generate data in the system so we can simulate what happens when we have large numbers of moves in the system.
Finally, we want our load tests to be easy to write.
This is an experiment generating a python openapi client from our mymove swagger files and then using that API to simulate a simple HHG move going from service member -> service counselor -> TOO -> Prime as a proof of concept.
The move flow can be developed out outside of locust and once it works, can be easily added to our locust tests.
The users/flows/simple_hhg.py file and the utils/flows/steps/*.py files are the meat of the experiment.
Reviewer Notes
Setup
If you have the API running locally, you can run
PYTHONPATH=$PWD python utils/flows/simple_hhg.py

It won't actually produce any output to the screen, but you can see in the API logs that actions have been run.
To run locust via the browser, do
locust -f locustfiles/queue.py --host local -u 10

You can the run the test and see the results.
Or you could do
locust -f locustfiles/queue.py --host local -u 10 -t 30s --headless

and see that there are 0% failures

The users/flows/simple_hhg.py file and the utils/flows/steps/*.py files are the meat of the experiment.

502788ecc7601ec89464ee67c208335865a7c40a is the commit that is probably the most signal

I will continue debugging this tomorrow, but a few issues up front.
I'm unable to run the command in the initial comment due to not having the correct dependencies. I rectified this by running make install_python_deps to get things past ModuleNotFoundError. After that, I tried the * python * command from the initial comment again and got the following exception Exception: Cannot create user: UserType.MILMOVE.
I can investigate further on my own, but I wanted to capture these somewhere so I can remember what I say. I've seen the server error reported back to me when I've gone from working between the MilMove and MilMove Load Testing repositories. I'm not sure if it's related, so I'll have to further investigate and ask around in the #g-database channel.

💻 ❌ Error after running initial command.
Command
>_ PYTHONPATH=$PWD python utils/flows/simple_hhg.py

Output
Traceback (most recent call last):
  File "/Users/rsr/Developer/transcom/milmove_load_testing/utils/flows/simple_hhg.py", line 30, in <module>
    f.run_entire_flow(milmove_env)
  File "/Users/rsr/Developer/transcom/milmove_load_testing/utils/flows/__init__.py", line 98, in run_entire_flow
    while self.run(flow_session_manager):
  File "/Users/rsr/Developer/transcom/milmove_load_testing/utils/flows/__init__.py", line 84, in run
    flow_step_callback(self.flow_context, flow_session_manager)
  File "/Users/rsr/Developer/transcom/milmove_load_testing/utils/flows/steps/milmove.py", line 44, in do_hhg_create_move
    api_client = flow_session_manager.internal_api_client(UserType.MILMOVE)
  File "/Users/rsr/Developer/transcom/milmove_load_testing/utils/openapi_client.py", line 165, in internal_api_client
    raise Exception(f"Cannot create user: {user_type}")
Exception: Cannot create user: UserType.MILMOVE

💻 ❌ Server logs after running initial command.
Server logs output
[POP] 2022/03/02 05:25:29 sql - SELECT users.id,
                                users.login_gov_email AS email,
                                users.active AS active,
                                sm.id AS sm_id,
                                sm.first_name AS sm_fname,
                                sm.last_name AS sm_lname,
                                sm.middle_name AS sm_middle,
                                du.id AS du_id
                        FROM service_members as sm
                        JOIN users on sm.user_id = users.id
                        LEFT OUTER JOIN dps_users AS du on du.login_gov_email = users.login_gov_email
            WHERE users.login_gov_email !=<EMAIL_ADDRESS>                        ORDER BY users.created_at LIMIT $1 | [100]
[POP] 2022/03/02 05:25:29 sql - select distinct gbloc from transportation_offices
2022-03-02T05:25:29.200Z        INFO    middleware/request_logger.go:78 Request {"git_branch": "master", "git_commit": "c376447ef5fa64ab50882d911f87e8da43ae4ea4", "host": "milmovelocal:8080", "milmove_trace_id": "db39e220-c6f9-4290-94ea-c866369f3b27", "accepted-language": "", "content-length": 0, "host": "milmovelocal:8080", "method": "GET", "protocol-version": "HTTP/1.1", "referer": "", "source": "<IP_ADDRESS>:61532", "url": "/devlocal-auth/login", "user-agent": "python-requests/2.27.1", "protocol": "http", "headers": 4, "duration": "14.49702ms", "resp-size-bytes": 1977, "resp-status": 200}
2022-03-02T05:25:29.229Z        INFO    auth/cookie.go:183      Existing session found  {"git_branch": "master", "git_commit": "c376447ef5fa64ab50882d911f87e8da43ae4ea4", "host": "milmovelocal:8080", "milmove_trace_id": "14f68b47-b650-4421-bba9-c2f2e227d16c"}
[POP] 2022/03/02 05:25:29 sql - INSERT INTO "users" ("active", "created_at", "current_admin_session_id", "current_mil_session_id", "current_office_session_id", "id", "login_gov_email", "login_gov_uuid", "updated_at") VALUES (:active, :created_at, :current_admin_session_id, :current_mil_session_id, :current_office_session_id, :id, :login_gov_email, :login_gov_uuid, :updated_at)
[POP] 2022/03/02 05:25:29 sql - INSERT INTO "service_members" ("affiliation", "backup_mailing_address_id", "created_at", "duty_station_id", "edipi", "email_is_preferred", "first_name", "id", "last_name", "middle_name", "personal_email", "phone_is_preferred", "rank", "requires_access_code", "residential_address_id", "secondary_telephone", "suffix", "telephone", "updated_at", "user_id") VALUES (:affiliation, :backup_mailing_address_id, :created_at, :duty_station_id, :edipi, :email_is_preferred, :first_name, :id, :last_name, :middle_name, :personal_email, :phone_is_preferred, :rank, :requires_access_code, :residential_address_id, :secondary_telephone, :suffix, :telephone, :updated_at, :user_id)
2022-03-02T05:25:29.242Z        ERROR   authentication/devlocal.go:445  Error creating service member for user  {"git_branch": "master", "git_commit": "c376447ef5fa64ab50882d911f87e8da43ae4ea4", "host": "milmovelocal:8080", "milmove_trace_id": "14f68b47-b650-4421-bba9-c2f2e227d16c", "error": "pq: syntax error at or near \"$3\""}
github.com/transcom/mymove/pkg/auth/authentication.createUser
        /Users/rsr/Developer/transcom/mymove/pkg/auth/authentication/devlocal.go:445
github.com/transcom/mymove/pkg/auth/authentication.CreateUserHandler.ServeHTTP
        /Users/rsr/Developer/transcom/mymove/pkg/auth/authentication/devlocal.go:341
        /Users/rsr/Developer/transcom/mymove/.gopath/pkg/mod/go.opentelemetry.io/contrib/instrumentation/github.com/gorilla/mux/otelmux@v0.29.0/mux.go:145
github.com/transcom/mymove/pkg/middleware.NoCache.func1.1
[POP] 2022/03/02 05:25:29 sql - SELECT users.id,
                                users.login_gov_email AS email,
                                users.active AS active,
                                sm.id AS sm_id,
                                sm.first_name AS sm_fname,
                                sm.last_name AS sm_lname,
                                sm.middle_name AS sm_middle,
                                ou.id AS ou_id,
                                ou.first_name AS ou_fname,
                                ou.last_name AS ou_lname,
                                ou.middle_initials AS ou_middle,
                                ou.active AS ou_active,
                                au.id AS au_id,
                                au.role AS au_role,
                                au.first_name AS au_fname,
                                au.last_name AS au_lname,
                                au.active AS au_active,
                                du.id AS du_id,
                                du.active AS du_active
                        FROM users
                        LEFT OUTER JOIN service_members AS sm on sm.user_id = users.id
                        LEFT OUTER JOIN office_users AS ou on ou.user_id = users.id
                        LEFT OUTER JOIN admin_users AS au on au.user_id = users.id
                        LEFT OUTER JOIN dps_users AS du on du.login_gov_email = users.login_gov_email
                        WHERE users.login_gov_uuid  = $1 | ["6bb24195-f6f6-4e88-bd71-be6c4759dbe0"]
[POP] 2022/03/02 05:25:29 sql - SELECT * FROM roles
                                                                        WHERE id in (select role_id from users_roles
                                                                                where deleted_at is null and user_id = $1) | [351bb6f9-5948-46dd-8eca-6cfb650a44a8]
2022-03-02T05:25:29.248Z        INFO    authentication/devlocal.go:910  logged in       {"git_branch": "master", "git_commit": "c376447ef5fa64ab50882d911f87e8da43ae4ea4", "host": "milmovelocal:8080", "milmove_trace_id": "14f68b47-b650-4421-bba9-c2f2e227d16c", "session": {"ApplicationName":"mil","Hostname":"milmovelocal","IDToken":"devlocal","UserID":"351bb6f9-5948-46dd-8eca-6cfb650a44a8","Email":"20220302052529-8d513ef8675a@example.com","FirstName":"","Middle":"","LastName":"","ServiceMemberID":"00000000-0000-0000-0000-000000000000","OfficeUserID":"00000000-0000-0000-0000-000000000000","AdminUserID":"00000000-0000-0000-0000-000000000000","AdminUserRole":"","DpsUserID":"00000000-0000-0000-0000-000000000000","Roles":null}}
2022-03-02T05:25:29.248Z        INFO    middleware/request_logger.go:78 Request {"git_branch": "master", "git_commit": "c376447ef5fa64ab50882d911f87e8da43ae4ea4", "host": "milmovelocal:8080", "milmove_trace_id": "14f68b47-b650-4421-bba9-c2f2e227d16c", "accepted-language": "", "content-length": 136, "host": "milmovelocal:8080", "method": "POST", "protocol-version": "HTTP/1.1", "referer": "", "source": "<IP_ADDRESS>:61532", "url": "/devlocal-auth/create", "user-agent": "python-requests/2.27.1", "protocol": "http", "x-csrf-token": "2SZ0BsQKUAp2/V47G9MY1SuCh4KvYT+/KsxYggZVEHyWgEOrZj2Ee6QBw1E7Vp3P4ZpC+owJgf6cNwhPfa30xA==", "headers": 8, "duration": "18.878122ms", "resp-size-bytes": 385, "resp-status": 500}

I will continue debugging this tomorrow, but a few issues up front.
I'm unable to run the command in the initial comment due to not having the correct dependencies. I rectified this by running make install_python_deps to get things past ModuleNotFoundError. After that, I tried the * python * command from the initial comment again and got the following exception Exception: Cannot create user: UserType.MILMOVE.
I can investigate further on my own, but I wanted to capture these somewhere so I can remember what I say. I've seen the server error reported back to me when I've gone from working between the MilMove and MilMove Load Testing repositories. I'm not sure if it's related, so I'll have to further investigate and ask around in the #g-database channel.
💻 ❌ Error after running initial command.
💻 ❌ Server logs after running initial command.

@rogeruiz there's no way for the load testing API client to create a PostgreSQL exception in the server, so it must mean your server code / database is out of sync somehow.

Taking a look again at this today. The fix for my error was patched here transcom/mymove#8230


add support for babel-jscs

monkeypatch (specifically use of Module._resolveFilename) fails
on linux without symlink
removed monkeypatch method on babel-jscs and moved patching estraverse
to jscs itself.
Ref #1446
Pinning babel-jscs to PR to make it pass.

Ok wow it's all passing now - @markelog @zxqfox @mrjoelkemp

Thank you @hzoo Hooray!

I can merge https://github.com/jscs-dev/babel-jscs/pull/10/files so we can change jscs-dev/babel-jscs#remove-monkeypatch. Would that be a major version so 2.0.0 or just 1.0.4?

It's a major bump since folks using babel-jscs will hit errors without the
latest jscs master since you removed the monkeypatch.
On Jul 8, 2015 8:28 AM, "Henry Zhu"<EMAIL_ADDRESS>wrote:

I can merge https://github.com/jscs-dev/babel-jscs/pull/10/files so we
can change jscs-dev/babel-jscs#remove-monkeypatch. Would that be a major
version so 2.0.0 or just 1.0.4?
—
Reply to this email directly or view it on GitHub
https://github.com/jscs-dev/node-jscs/pull/1515#issuecomment-119558521.

I was thinking that although I put in the readme to use master for jscs anyway since no release yet - ok thanks major then.

Also @markelog - can we update estraverse now?
https://github.com/jscs-dev/node-jscs/blob/master/lib/tree-iterator.js#L65 So when you remove add handler as well some tests fail.
We won't need https://github.com/jscs-dev/node-jscs/blob/master/lib/tree-iterator.js#L39-L49 since it would be covered in babel keys already. I don't know if we need the XJS ones since that's deprecated.


Provide minified version

Description
Provide minified version of JS dist file.
Are you interested in working on this improvement yourself?

Yes, I am.

Additional Context
I tried to use rollup-plugin-terser, but this results in broken model tensors unserialization.
So it needs some more research why.

I have tried to reproduce the issue from various angles, but everything seems to be working fine. I have tried stopping the training and then restoring from checkpoint and all seems fine. Perhaps the issue was fixed somewhere in dependencies? Added a PR to add minification here: https://github.com/OpenMined/syft.js/pull/235


Middlewares all call same data object - would like it to act as a pipe.

  Documentation didn't specify that, but I think it's typically more intuitive than the current implementation.  Currently:
const storeData = getStore();
if (Array.isArray(middleWaresArray) && middleWaresArray.length) {
  middleWaresArray.forEach((callback) => {
    callback(storeData);
  });
}
updateStore(storeData);

Proposal
const storeData = getStore();
let pipeData;
if (Array.isArray(middleWaresArray) && middleWaresArray.length) {
  pipeData = middleWaresArray.reduce((currentValue, currentFunction) => {
    return currentFunction(currentValue);
  }, storeData);
}
updateStore(pipeData);

love it! let's go with that. feel free to send a PR.


Strength HashiCorp Vault KMS HTTP interactions against failure cases such as HTTP timeout

          We could set a hardcoded [timeout](https://docs.oracle.com/en/java/javase/17/docs/api/java.net.http/java/net/http/HttpRequest.Builder.html#timeout(java.time.Duration)) here to match the connect timeout on the client.

Sets a timeout for this request. If the response is not received within the specified timeout then an HttpTimeoutException is thrown from HttpClient::send or HttpClient::sendAsync completes exceptionally with an HttpTimeoutException. The effect of not setting a timeout is the same as setting an infinite Duration, i.e. block forever.

Though it looks like there's some problems with it in that the request timeout is cancelled when the headers are received, so a slow/blocked response body can still block it up foreverJDK-8258397. The suggested workaround we might want to do later is ensure we set up a scheduled timeout for our own Future and cancel the request on timeout.
Originally posted by @robobario in https://github.com/kroxylicious/kroxylicious/pull/749#discussion_r1417931251

My gut feel is we can defer this until post 0.5.0

@k-wall is this a duplicate?


Project manager crashes when opening in 4.1.dev4 due to OpenGL regression (Windows, AMD)

Godot version
Godot_4.1.dev4
System information
windows10
Issue description
I tried to open godot_4.1.dev4 on my windows10 machine and found it crashed. The godot console did not have any valid error messages. I have two Windows 10 machines and both crashed

p1 configuration:
AMD Ryzen 7 5800X
32.0 GB
AMD Radeon RX6600

pc2 configuration:
AMD Ryzen 7 5800H
32.0 GB
NVIDIA GeForce RTX 3070 Laptop

Steps to reproduce
Run editor
Minimal reproduction project
none

same issue on my side

Do any previous Godot versions work? Do you think this is a regression or is this the first time you are trying out Godot?

Do any previous Godot versions work? Do you think this is a regression or is this the first time you are trying out Godot?

I've been trying the latest versions, from dev1 to dev4, and the first three are all working

Looks like a regression then

same issue on my side

I found that I couldn't open the project list, but I was able to just drag the. godot file into godot.exe and the editor worked fine

godot file into godot.exe and the editor worked fine

crashes while recompiling gles3 cached shaders

The Godot project manager uses OpenGL renderer by default, so if things work better by running the editor directly (and the actual project uses Forward Plus or Mobile renderer) it might have something to do with OpenGL renderer.
You can try to bypass the project manager and edit project directly by drag-and-dropping or using --editor and --path command line arguments and see if the project editor starts directly: https://docs.godotengine.org/en/stable/tutorials/editor/command_line_tutorial.html Or maybe even test with different --rendering-method command line arguments. See also check out --help.

Drag and drop worked for me also

I made it work with  --rendering-driver vulkan.
you can create a shortcut to Godot_v4.1-dev4_mono_win64.exe and in Properties add --rendering-driver vulkan => functioning Project Manager

This may be a regression from https://github.com/godotengine/godot/pull/76092, even though https://github.com/godotengine/godot/pull/77163 was already merged in 4.1.dev4.

This may be a regression from #76092, even though #77163 was already merged in 4.1.dev4.
Can you reproduce this issue in 4.0.3? Also, can you reproduce the issue in 4.1.dev4 without Mono?

I've just tried 4.1dev4 without mono and behaves the same (crashes on normal run, works with --rendering-driver vulkan)
I'm currently working on a project on 4.0.3 and works as expected

This may be a regression from #76092, even though #77163 was already merged in 4.1.dev4.

Both were already merged in 4.1.dev3, so if the regression happened between dev3 and dev4, it should be a different PR.
This is more likely to be caused by one of these changes to drivers/gles3/ between dev3 and dev4:
commit f2e91eae639406a5fccea0210042a3e79760d502
Merge: aa739bae4f 391a1bf60e
Author: Rémi Verschelde<EMAIL_ADDRESS>Date:   Mon May 29 10:29:08 2023 +0200

    Merge pull request #77224 from patrickdown/implement_texture_2d_layered_initialize

    Implemented texture_2D_layered_initialize

commit 391a1bf60e757c59cfd32e9e1dd851b57cc7c1d1
Author: patrickdown<EMAIL_ADDRESS>Date:   Thu May 18 11:41:17 2023 -0400

    Implemented texture_2D_layered_initialize

commit f6dcd7f51a65f9fbc4c98583016bc85d130b3106
Merge: 08fcf27038 43b0702a02
Author: Yuri Sizov<EMAIL_ADDRESS>Date:   Sat May 27 17:28:29 2023 +0200

    Merge pull request #75181 from dalexeev/fix-light-only-mode

    Fix "Light Only" mode of `CanvasItemMaterial`

commit 6d3634e29f32d1d481a2d71e3eb7cc0718bde0a9
Author: Dani Frank<EMAIL_ADDRESS>Date:   Sat Mar 25 12:46:33 2023 +0300

    fix gles texture uniform array binding

commit 43b0702a0266a823ae42d0c048a6d6baeaceaa06
Author: Danil Alexeev<EMAIL_ADDRESS>Date:   Tue Mar 21 12:18:15 2023 +0300

    Fix "Light Only" mode of `CanvasItemMaterial`

@akien-mga sadly I don't have a mono setup here (really should rectify this) but a normal master build runs fine so it has to be a mono specific regression.
Having a look at the commits you mentioned, nothing stands out. Anything in 391a1bf60e757c59cfd32e9e1dd851b57cc7c1d1 would have resulted in console output, 43b0702a0266a823ae42d0c048a6d6baeaceaa06 doesn't seem to structurally change anything, I'm not entirely sure what 6d3634e29f32d1d481a2d71e3eb7cc0718bde0a9 is about but nothing stands out that would cause mono to panic.
We have had issues in the past with parts of the system calling into the mono system before mono is ready, if we're logging errors early that could explain things, but I would expect those errors to be logged in a normal build too.
I'll see if I can get a mono setup working tomorrow.

@BastiaanOlij The report above suggests that the issue is reproduceable without mono as well. Although...
@miketgv Do you use the self-contained mode? Can you try each version (with mono, without mono) in that mode?

Chiming in as another AMD user with the same issue, although did not try Mono, just regular version.
Launching it immediately gives a grey screen, then crashes. All previous versions work fine, and nothing about my system has changed.

Specs:

AMD Ryzen 7 5800x
AMD Radeon RX 5700 XT
16Gigs of ram
Windows 11 Pro 64-bit

Setting the rendering driver to Vulkan in the launch parameters resolves the issue, same as above posters.

same issue here. (windows 10, AMD ryzen 5900x, Radeon 6950xt ,driver: 23.5.2 ==> last driver).

I tried earlier versions and worked well.
I tried this version (Godot 4.1 dev4) on linux with this pc and it works fine.
I tried this version on my laptop (intel core i7 + intel iris xe) and it works fine.

maybe AMD issue.
https://github.com/godotengine/godot/assets/121864036/c6f16ce4-a525-4d1d-ada3-84b1da72c0b6

OP has mentioned that it crashes on a NVIDIA setup, although they may have used the AMD integrated graphics if they overrode the selection (Godot requests the dedicated GPU by default).

To help narrow down the issue, could someone with this issue go though these builds and report which cause a crash and which start into the project manager without problems: https://mega.nz/folder/AjYRiTga#jyCIWuI_MW1HOic89VEozg

To help narrow down the issue, could someone with this issue go though these builds and report which cause a crash and which start into the project manager without problems: https://mega.nz/folder/AjYRiTga#jyCIWuI_MW1HOic89VEozg

f6dcd7f51a65f9fbc4c98583016bc85d130b3106
6d3634e29f32d1d481a2d71e3eb7cc0718bde0a9
43b0702a0266a823ae42d0c048a6d6baeaceaa06
a67d37f7cffe7f31c68e971280950d487ea99e2c

All of these worked.

Maybe related to https://github.com/godotengine/godot/pull/73450.

Reading up on this, yeah must be AMD related then, for me the same thing, testing on NVidia I have no issues.
Has anyone been able to run this on a full debug build with --gpu-validation and --verbose switches?

Maybe related to #73450.

Unlikely, a round of remote bisection (https://github.com/godotengine/godot/issues/77760#issuecomment-1574231922) points at #77224 tho it hasn't been confirmed yet
(Again if someone with this issue could please run these https://github.com/godotengine/godot/issues/77760#issuecomment-1574259301 and report back if they crash or open the project manager)
Either way the currently remaining commits that may have caused this are:
f2e91eae639406a5fccea0210042a3e79760d502 (refs/bisect/bad) Merge pull request #77224 from patrickdown/implement_texture_2d_layered_initialize
aa739bae4f84fc2b7a57692896aad29b843b07fa Merge pull request #76616 from TokageItLab/implement-anim-node-sub2
c97201babcb76e6fb0e7558074dfe7808982eb00 Merge pull request #76545 from JoNax97/gradient_color_spaces
990943782a80e47b4a46587c298a338e9a2c119c Merge pull request #74959 from MewPurPur/nice-curves
9f05e16727a6776c0bf27c18d5ce0d016542494a Merge pull request #70940 from MewPurPur/better-gradient2d-editor
6dcd490d03ac98b9759ceac1dddbe9b67f6ea74a Merge pull request #66763 from MewPurPur/remove-bookmark-hiding
a3c4a4b039e9c0c5947744bbaf7f9a9bc123982c Overhaul the Curve Editor
28cca66d2cfe25d6d7bf5a2a26ab7bd366029669 Merge pull request #77541 from TokageItLab/remove-outdated-docs-from-skeleton
06ccbfe8eec6e840db3df2360dc2804386f940b8 (HEAD) Merge pull request #77534 from aaronfranke/gltf-node-index
c670c4334a6901410128f8b66a0ce7d097e66e5d Merge pull request #65902 from MJacred/editor/copysysteminfo
391a1bf60e757c59cfd32e9e1dd851b57cc7c1d1 Implemented texture_2D_layered_initialize
5e139c2ab927f0546a5f6b6a974a931b53013978 Add a get_node_index method to GLTFState
9e5bf3d589fec3f342231fd9e0a16b03b83469d3 Copy system info to clipboard + Update bug_report.yml
9a3221f1edb057d8ec3dfe55f9966d3ae5c8acb1 Merge pull request #77419 from MewPurPur/remove-unused-svgs
36e7800679e406ac79e6865cabaf0e7e69bc81d8 Merge pull request #77511 from KoBeWi/destroy_size()
c87dc07fdd52de4437f828b26eb0c958168efdb0 Merge pull request #77514 from bruvzg/fix_dup_breaks
9128ed47198630026737366d788a4a2478853750 Merge pull request #77517 from KoBeWi/TranslateThisRightNow
26cc4bbd82e991de7fdd4a44cadcbc1558e16205 Remove out-dated lines from class reference of Skeleton3D
c9c8205644253e5aea712dfd893a39499fc773de Implement NodeSub2 to AnimationTree & improve mathematical Nodes
c07b2fcf4dd9bc60f6d7ead81b8de8ee19178729 Add Linear SRGB and OKLab color spaces to Gradient.
adf427c806b902123e722e86fda55aa173ec5aa2 Translate inspector changes indicator
8a4a883854d24f864ab39be1a152f58d754db91e [TextServer] Prevent duplicate line breaks on virtual spaces when line width is significantly smaller than character width.
05663b8633f470ad4baefa896fb9a14596bf5d93 Minor improvements to sub-resource list
860f51b0503879c72553736f65ad15f4b45387e7 Remove unused SVG icons
39b79bbd1e83d1ac46a1dacdd17cd4b05a0000de Improvements to Gradient2D Editor
e0e236edfc75cb4d9999d619edac3cec8e3ea323 Remove editor setting for hiding bookmarks

Thanks, which confirms this to be a regression from #77224, as one of them was master with just that PR reverted.

Has anyone reproduced the bug on a debug build and can post a stack trace?

I've got this but I don't know if it's useful:
Exception thrown at 0x00007FF8BA27236A (atio6axx.dll) in godot.windows.editor.x86_64.exe: 0xC0000005: Access violation reading location 0xFFFFFFFFFFFFFFFF.

atio6axx.dll!00007ff8ba27236a()	Unknown
atio6axx.dll!00007ff8ba272a06()	Unknown
atio6axx.dll!00007ff8ba271f75()	Unknown
atio6axx.dll!00007ff8ba1e5d3e()	Unknown
atio6axx.dll!00007ff8ba3208fe()	Unknown
atio6axx.dll!00007ff8b9efb79e()	Unknown
atio6axx.dll!00007ff8b9e8c4d0()	Unknown
atio6axx.dll!00007ff8b9e8e488()	Unknown
atio6axx.dll!00007ff8b9e4a4ce()	Unknown
atio6axx.dll!00007ff8b99e6991()	Unknown
atio6axx.dll!00007ff8b9dd46ed()	Unknown
atio6axx.dll!00007ff8b9d65f36()	Unknown
atio6axx.dll!00007ff8b9d5ce58()	Unknown
atio6axx.dll!00007ff8b9aca84f()	Unknown
atio6axx.dll!00007ff8bb7f5096()	Unknown
kernel32.dll!00007ff9780b26ad()	Unknown
ntdll.dll!00007ff978f8a9f8()	Unknown

Reading up on this, yeah must be AMD related then, for me the same thing, testing on NVidia I have no issues.
Has anyone been able to run this on a full debug build with --gpu-validation and --verbose switches?

It shows this:
$ ./godot.windows.editor.x86_64.exe --gpu-validation --verbose
Godot Engine v4.1.dev.custom_build.db5113de3 - https://godotengine.org
TextServer: Added interface "Dummy"
TextServer: Added interface "ICU / HarfBuzz / Graphite (Built-in)"
Using "winink" pen tablet driver...
Shader 'CanvasSdfShaderGLES3' SHA256: 72cda41890bce2f09217c172023d31e735a3fee605bad83c8e63f1a981a36a77
Shader 'SkeletonShaderGLES3' SHA256: add3f03e6eebdffdf0073fae42195857307eddada333b82998642329511917a2
Segmentation fault

Reading up on this, yeah must be AMD related then, for me the same thing, testing on NVidia I have no issues.
Has anyone been able to run this on a full debug build with --gpu-validation and --verbose switches?

It shows this:
Godot Engine v4.1.dev4.official.5c2295ff5 - https://godotengine.org TextServer: Added interface "Dummy" TextServer: Added interface "ICU / HarfBuzz / Graphite (Built-in)" Using "winink" pen tablet driver... Shader 'CanvasSdfShaderGLES3' SHA256: 72cda41890bce2f09217c172023d31e735a3fee605bad83c8e63f1a981a36a77 Shader 'SkeletonShaderGLES3' SHA256: add3f03e6eebdffdf0073fae42195857307eddada333b82998642329511917a2 Shader 'ParticlesShaderGLES3' SHA256: 9bf432d37b0b4792d67aa9f577258845d4047e3f98e990aeca6fd20a868c4db2 Shader 'ParticlesCopyShaderGLES3' SHA256: c778843b0cd1c7ce4c621fa2b924f703ac4001faef0555114b81a76c264a6908 Shader 'CopyShaderGLES3' SHA256: b1bc5a355ed9bda23f291956f121e0535b4e81b54cdac398412d200e6133161f Shader 'CanvasShaderGLES3' SHA256: 007cddfcf35f7d57b219cffec53f6a7d9fe7a1979be4db64c6450cfac6000053 Shader 'CanvasOcclusionShaderGLES3' SHA256: 968915a469db9a7d505be274e8060c8288c15a5865baeb8362b3b0e2cacb16f3 Shader 'SceneShaderGLES3' SHA256: 7978059ed235406c8eb185f813778475d9fb0316458c2782764a5e2dd98e930d Shader 'SkyShaderGLES3' SHA256: 1fe105946e63973aecf5198091930c2bdb17778012ef0253e325ade3a297e6c8 Shader 'CubemapFilterShaderGLES3' SHA256: 2b651c285a02b7d4221af1827e1613c03e73e600ebc40b9e6a0b22bb855bd75f OpenGL API 3.3.0 Core Profile Context <IP_ADDRESS>523 - Compatibility - Using Device: ATI Technologies Inc. - AMD Radeon RX 6950 XT WASAPI: Activated output_

I think I have the same issue, the Project Manager just doesn't work when I open it.

Godot 4.1-beta1 official
Windows 10 22H2
i5 7600k
16gb ram DDR4
AMD RX 6800 16gb

https://github.com/godotengine/godot/assets/64472605/fef3b532-ba0d-45ca-a7ff-1a1ca73deea4

As mentioned in https://godotengine.org/article/dev-snapshot-godot-4-1-beta-1/#known-issues, the fix is only merged in the upcoming 4.1.beta2, not 4.1.beta1. There's a workaround listed in the link.


Cost Explorer API (4/n): A Grafana dashboard with one functional panel, processing JSON responses from the Python webserver

With #4672, we should have a Python webserver deployed/deployable to try use as a backend for Grafana dashboard development.
Definition of done

One dashboard panel from https://github.com/2i2c-org/infrastructure/issues/4453 is presenting data correctly visually
The dashboard panel is presenting the right data - adjusting the dashboard's current time period window

[x] research: Figure out how Grafana will adjust requests based on UI configured time ranges
By passing Grafana built-in global variables as query parameters in the URL, such as http://ce-test.ce-test.svc.cluster.local/?from=${__from:date:iso}&to=${__to:date:iso}.
[x] webserver: omit group_by SERVICE for now
[ ] webserver: truncate from/to to the relevant from/to dates

When querying the CE API, the To part is exclusive, so it should be the date after.

[ ] webserver: adjust the response to be a list of dates with associated cost

From https://grafana.openscapes.2i2c.cloud/d/edw06h7udjwg0b/testing-dashboard?orgId=1.


Pop transition now works great

I ended up having to modify Plaid's FabTransform quite a bit, but I'm pretty happy with the results. Any comments/changes before merging? If not, can you merge this into your PR so we can get it in the demo?

@EricKuck Any1 super awesome that you figured it out! Kudos to you. If you have time to "clean" it up feel free to do so, otherwise I'll make the changes we discussed tomorrow and do the PR to Conductor.

Just cleaned it up! Thanks for catching those issues.
There were a few things that made this all work. First, I had to make a copy of the dialog's view drawing cache and put that on top of the overlay. This was required because there doesn't seem to be a way to change the z-order of views during a transition. I don't love that this is the way it works, but faking the z-order seems to work well enough.
Second, the transition was messing with the fab's translations (x, y, and z), so I had to reset those. It also forced a remeasure and layout with the size of the dialog rather than the size of the fab. Since it added clipping at the end this wasn't super obvious. I re-remeasured the fab to be the correct size, and again forced a layout and it began to work correctly.
The last step was to remove the outline clipping, as this apparently makes Android stop drawing shadows (hasShadow = false in the hierarchy inspector). Since this caused a pretty ugly frame or two while it was being resized, I waited until the size was correct before applying it using a OnPreDrawListener.

Thanks for the explanation! It kinda makes sense now that all the pieces fell together. It definitely was a puzzler.


Closing Data Adventures 1 sprint

@sdumitriu #167 doesn't appear to be merged, is that intentional?


accessibility on how to connect page

#REF: #MOBILEAPPS-1508

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


IF you CHANGE a PRODUCT then YOU need to CHANGE the Documentation and step by steps

PLEASE CREATE A STEP BY STEP THAT REFLECTS THE NEW METHOD.  We CANNOT wing it infront of customers and clients!  POST A STEP BY STEP ON SETTING UP UPGRADE READINESS FROM STEP 1 set up azure portal all the way through to ANALYZING the results!

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

ID: 24771310-237e-adf7-be33-59355a87f243
Version Independent ID: e2792588-8318-98a2-a5bd-ff5cbba75e0e
Content: Get started with Upgrade Readiness (Windows 10)
Content Source: windows/deployment/upgrade/upgrade-readiness-get-started.md
Product: w10
GitHub Login: @jaimeo
Microsoft Alias: jaimeo

@officedocsbot assign @mypil

@jaimeo I would love your input on this issue as one of the page contributors, thanks!

Hey @rzecchino,
I've reviewed this page, and it looks like it's already been updated to reflect the onboarding changes that resulted from Log Analytics' move to the Azure portal.
In terms of Analyzing results, this will be a process that is unique for each customer/workspace.  As a rule of thumb, we document what we've built so that you can get acquainted with the tool.  However, we're unable to document processes like data analysis as this will be heavily dependent upon the unique insights that you're seeing.
If you find specific steps of the product that are not properly described or reflected in the docs, please let us know!
Thanks,
Zach

@rzecchino After spending some time looking into this and going through some other documentation, I can also confirm that @zdvorak 's comment is correct.  If you do happen to find something that you think could be improved or mentioned in the document to improve people's experiences using this, feel free to comment back with your suggestion and we'll be happy to re-open this issue and look at your suggestions and even add them if we think they are a good fit.  Thank you again for posting this and have a nice day!

@officedocsbot close


Change sentiment analysis library

ml5 has numerous vulnerable dependencies, and the developers have decided to create a next-gen version. However, that isn't ready yet.
Alternatively, directly use the Sentiment Analysis task from Tensorflow.js.

The perennial curse of frontend development: trying to figure out what a gibberish Vite/npm/whatever stack trace means.

Failed to resolve entry for package "@tensorflow-models/tasks". The package may have incorrect main/module/exports specified in its package.json.
09:55:08 [vite] Internal server error: Failed to resolve entry for package "@tensorflow-models/tasks". The package may have incorrect main/module/exports specified in its package.json.
Plugin: vite:import-analysis
File: path/to/sydfjords/src/sentiment/sentiment.ts
at packageEntryFailure (path/to/sydfjords/node_modules/.pnpm/vite@4.5.2_@types+node@20.11.17/node_modules/vite/dist/node/chunks/dep-52909643.js:28725:11)
at resolvePackageEntry (path/to/sydfjords/node_modules/.pnpm/vite@4.5.2_@types+node@20.11.17/node_modules/vite/dist/node/chunks/dep-52909643.js:28722:5)
at tryNodeResolve (path/to/sydfjords/node_modules/.pnpm/vite@4.5.2_@types+node@20.11.17/node_modules/vite/dist/node/chunks/dep-52909643.js:28453:20)
at Context.resolveId (path/to/sydfjords/node_modules/.pnpm/vite@4.5.2_@types+node@20.11.17/node_modules/vite/dist/node/chunks/dep-52909643.js:28212:28)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Object.resolveId (path/to/sydfjords/node_modules/.pnpm/vite@4.5.2_@types+node@20.11.17/node_modules/vite/dist/node/chunks/dep-52909643.js:44276:32)
at async TransformContext.resolve (path/to/sydfjords/node_modules/.pnpm/vite@4.5.2_@types+node@20.11.17/node_modules/vite/dist/node/chunks/dep-52909643.js:43992:23)
at async normalizeUrl (path/to/sydfjords/node_modules/.pnpm/vite@4.5.2_@types+node@20.11.17/node_modules/vite/dist/node/chunks/dep-52909643.js:41836:34)
at async path/to/sydfjords/node_modules/.pnpm/vite@4.5.2_@types+node@20.11.17/node_modules/vite/dist/node/chunks/dep-52909643.js:41998:47
at async Promise.all (index 0)

The issue seems to be with the @tensorflow-models/tasks package. Loading the @tensorflow-models/toxicity package works fine.
This seems to be a more specific form of sentiment analysis than what I was expecting - it checks for toxicity (insults, threats, obscenity). That might be more useful than a generic "is this a positive message?"


Azure Kinect on Jetson Orin

Azure Kinect - ROS in Nvidia Jetson
I need to use azure kinect with ros in jetson nano. Currently I use ubuntu 20.04 in Jetson.
Actually I followed this  link which is working fine (standalone) when I run the SDK with command ./bin/k4aviewer in the Azure-Kinect_Sensor_SDK/build directory. But I need to use azure kinect with ROS. So then I seach k4a in terminal, I don't see it.
Then, I look for this website(Offical GitHub)
ARM64 users, please use the same instructions, but use https://packages.microsoft.com/ubuntu/18.04/multiarch/prod for the repository path instead of the default https://packages.microsoft.com/ubuntu/18.04/prod.
But I use ubuntu 20.04. So, I look for https://packages.microsoft.com/ubuntu/20.04/prod which is available but for ARM64 user https://packages.microsoft.com/ubuntu/20.04/multiarch/prod is not there.
So in short I am able to use SDK standalone but not with ROS. I need .../20.04/multiarch/prod or another way to run this SDK in ROS with ./bin/k4aviewer
Also I am open for all suggestions...

Hey dude,
You probably won't get the help you need from here.
Binaries from ubuntu 18.04 should work on 20.04,  i built my binaries from source.
If you want to execute in headless (without desktop) in the future:
You will need to "mock" desktop environment to populate DISPLAY variable.


fix(elements|ino-datepicker): only validate if value is set

Closes #356
Proposed Changes

Trigger validation logic only if value is truthy

Currently the min/max changes are already validated if no value is present (storybook: value: null, default-date: null & required true -> change min date in Dev-Tools DOM).

Currently the min/max changes are already validated if no value is present (storybook: value: null, default-date: null & required true -> change min date in Dev-Tools DOM).

That's expected because in that case, null is just handled as a string. If you want to provide an empty value to the ino-datepicker you should use '' instead of null like this:
<InoDatepicker ... value={this.myDate || ''} />

Currently the min/max changes are already validated if no value is present (storybook: value: null, default-date: null & required true -> change min date in Dev-Tools DOM).

That's expected because in that case, null is just handled as a string. If you want to provide an empty value to the ino-datepicker you should use '' instead of null like this:
<InoDatepicker ... value={this.myDate || ''} />

This is not an issue of handling the Datepicker. In Storybook you may observe this behavior if you adjust the Date Config  Knob (Delete initial value, ino-default-date as well as setting required in Standard Knob

Additionally i observe some error logs in React context using the datepicker in form on initalization:

Additionally i observe some error logs in React context using the datepicker in form on initalization:

I see. These errors might be related to the initialization of the validator which happens after the component rendered in the DOM (concrete in componentDidLoad). I moved the initialization of the validator to the componentWillLoad lifecycle. Can you check again @Sl1nd?

Additionally i observe some error logs in React context using the datepicker in form on initalization:

I see. These errors might be related to the initialization of the validator which happens after the component rendered in the DOM (concrete in componentDidLoad). I moved the initialization of the validator to the componentWillLoad lifecycle. Can you check again @Sl1nd?

Still present. I found a solution as i realized that the errors occure in all Watchers on setting the state for the validator. So checking if validator is present before setting state did fix the errors: e.g.

Currently the min/max changes are already validated if no value is present (storybook: value: null, default-date: null & required true -> change min date in Dev-Tools DOM).

That's expected because in that case, null is just handled as a string. If you want to provide an empty value to the ino-datepicker you should use '' instead of null like this:
<InoDatepicker ... value={this.myDate || ''} />

I think this is not an issue of handling the Datepicker. In Storybook you may observe this behavior if you adjust the Date Config Knob (Delete initial value, ino-default-date as well as setting required in Standard Knob
Refer to issue description #356

Still the minimum and maximum validation is triggered if no value is set. We need to adjust the  min/max validation methods
e.g.:
private validateMinSingle = (value: string): boolean => {
    if(!value) return true;
    const parsedDate: Date = this.parseDate(value);
    return (
      isEqual(parsedDate, this._minDate) || isAfter(parsedDate, this._minDate)
    );
  };```

@janivo  Works as expected. From my perspective this PR may be merged.


Add Arabic

This took me so long to get commited and stuff. I hope the translation is good.

still doesn't have Arabic...

misclick

Thanks for the contribution!


fail gracefully when there is no exact-dependencies.json

Instead of showing this:
A web handler threw an exception. Details:
elm-stuff/exact-dependencies.json: openBinaryFile: does not exist (No such file or directory)

Also, this is more work, but it would be nice to offer a button triggering elm-package install if there's an elm-package.json but not an exact-dependencies.json.

I fixed this


Bug: can you update dependency for vite 3?

@waynebrantley please test out v1.1.0 and report any issues (I haven't tested myself ^^')
If something broke, please re-open this issue and say what's wrong
Otherwise have a nice day :)

@Shinigami92 would you consider adding vite 4 now?

There is a breaking change in the warning
https://github.com/Shinigami92/vite-plugin-time-reporter/blob/2cf106d836555888394cfca3d6495c40ce9bcc20/src/index.ts#L44
Therefore I do not have time this evening to investigate

@Shinigami92 ok no problem - FYI - I am using the current version with V4 successfully
[vite:dts] Start generate declaration files...
┌─────────┬──────────┐
│ (index) │   time   │
├─────────┼──────────┤
│  build  │ '0.5[24] │
│ render  │ '0.093s' │
│  full   │ '0.798s' │
└─────────┴──────────┘
[vite:dts] Declaration files built in 3685ms.

@Shinigami92 ok no problem - FYI - I am using the current version with V4 successfully
[vite:dts] Start generate declaration files...
┌─────────┬──────────┐
│ (index) │   time   │
├─────────┼──────────┤
│  build  │ '0.5[24] │
│ render  │ '0.093s' │
│  full   │ '0.798s' │
└─────────┴──────────┘
[vite:dts] Declaration files built in 3685ms.

That's good to know, but it might fail if in any kind of way an error would be thrown, logging the error as warning now might be broken due to underlying API changes
Or the Error might be converted to a string and might result in e.g. [object Object]

@waynebrantley to keep you up to date: I reported an issue at https://github.com/rollup/rollup/issues/4754
Feel free to subscribe to that one
I will wait on an answer there, and want to omit to introduce an unneeded breaking change, so that I can still support Vite 2-4 with the same code base

@waynebrantley I released 2.1.0
Please report and open new issues when new problems occur


Dashboard node details SSD and HDD are wrong

Description
On dashboard, if you open the details of individual nodes, there are "Node resources" at the top which show the percentage of utilization of resources on the node. In these graphs, it seems as if the graph labeled SSD shows HDD utilization, and the graph labeled HDD shows SSD utilization
Checked on both mainnet and devnet

Verified on devnet.
By checking the resources of multiple nodes from the gridproxy and comparing them to the values in the node details it appears to be fixed.


Switch to shiny new fast, RLP-less trie

Also expunges RLP from the codebase. There's not really any new logic outside of the substrate-trie crate.
The codebase is no longer generic over NodeCodec; the reason for this twofold: firstly, trie node format allows for much less opinionated selection than the hashing algorithm. Formats do not significantly change in terms of security. Performance tweaks are non-controversial and are easily folded in over time. Secondly, it would require a two generic parameters, not one as before.

@svyatonik quite a few of the change-trie tests include raw roots. there's little i can do except to replace with the expected root. i don't know how to ensure these trie changes haven't broken their logic.

@gavofyork The same is true for Header::state_root - it always changes when storage is altered => https://github.com/paritytech/substrate/blob/master/node/executor/src/lib.rs is updated often too. I'll take a look at the reason of "I had to change this to make the tests work. any idea why?", but generally I assume that the same steps should be taken with changes_trie_root.

@svyatonik yeah the hashes i'm less bothered about (though it is rather tedious). however, those four changes i pointed to above are switching out some of the structure's values, which is concerning.


Allow users to open more types of scripture links.

Issue:
The choose version dropdown should accept links from Door43-catalog, catalog next, and scripture that is in a subfolder.
Door43-catalog:

[x] https://git.door43.org/unfoldingWord/en_ult
[x] https://door43.org/u/unfoldingWord/en_ult/ - Note this will map to https://git.door43.org/unfoldingWord/en_ult/
[x] https://git.door43.org/Door43-Catalog/en_ust.git
[x] git@git.door43.org:unfoldingWord/en_ult.git

Catalog Next:

[x] https://git.door43.org/unfoldingWord/el-x-koine_ugnt/src/tag/v0.20

DoD:
Users can successfully add scripture using URLs copied through the various methods of getting links from door43.
Details:

@elsylambert The fix is in GWE v1.0.0 build 2d0b620

Looks good in v1.0.0 build 1c04778. Able to add scriptures using the links. Not seeing the app crash when there is no scripture for a GL resource for some books, e.g ru.


Enabled 'chrony' service instead of 'chronyd'.

I tried the following configuration in file 'all.yml':
ntp_service_enabled: true
ntp_daemon_type: 'chronyd'

but it fails with the following message:
TASK [ceph-infra : enable chronyd] ************************************************************************************************************************************************
Friday 07 June 2019  09:05:52 +0200 (0:00:00.664)       0:02:01.979 ***********
fatal: [ceph-monitor03]: FAILED! => changed=false
  msg: 'Could not find the requested service chronyd: host'
fatal: [ceph-monitor02]: FAILED! => changed=false
  msg: 'Could not find the requested service chronyd: host'
fatal: [ceph-monitor01]: FAILED! => changed=false
  msg: 'Could not find the requested service chronyd: host'
[...]

With the change proposed it works fine.
OS: Ubuntu 18 bionic.
Ansible: 2.8
Branch: stable-4.0

@rishabh-d-dave I know you've worked a bit on this part of the playbook, do you mind reviewing this PR please?
Thanks!

I guess this one is now duplicate of https://github.com/ceph/ceph-ansible/pull/4089


Configuration to follow redirect method after http redirect

Summary.
Basically HTTP 301 redirection replaces POST method with a GET.
More Info: https://softwareengineering.stackexchange.com/questions/99894/why-doesnt-http-have-post-redirect
Need an config option in python requests to override this behavior and follow redirect method after http redirection.
Thanks
Raja

For overriding our redirect logic we have a coarse grained switch: allow_redirecte, which can be set to False. Failing that, more modern versions of Requests have a Session.rebuild_method method that can be overridden to change the behaviour to get what you're looking for.
There is no plan to add an additional config option for this behaviour.


[BEAM-1740] GCP-IO: manage Bigtable versions in top level pom

R: @davorbonaci @tgroh or anyone else

Coverage increased (+0.01%) to 70.536% when pulling cb5d1d37e96110892d681901bd58f46e80ebc66f on dhalperi:version-fixup into 6a95e5eeccccaf591d5d87091dfc7bb6919ecdd0 on apache:master.


Chainmail app UI

Special attention for:

Did I update CMakeLists.txt properly?

In this PR

Chain now boots with webmail UI
Home page lists "Chain mail" as an app
Slight improvements to home layout/responsiveness
Drafts supported in localstorage

Limitations

3 hard-coded accounts: alice, bob, and webmail
alice alone can send; all three accounts can receive
Emails cannot be deleted. Support for that in plugin/service forthcoming

Future work

Delete emails
zod.parse incoming messages with strict on (https://github.com/gofractally/psibase/pull/798#discussion_r1702299492)
Mark read/unread?
Support for threading replies?
Dark mode
Empty UI states
Send from accounts other than alice
More control bar options for markdown editor
Splash page/dialog explaining to the user it's just for demonstration purposes (until it's not)
Additional (potential) fields on message: id, datetime, status, read, inReplyTo: id, etc.

 Credit for that name goes to @swatanabe.


DF Template Enhancement: When using Walled Templates and 5e style templates the edges aren’t blocked by walls

Module
DF Template Enhancement 1.0
Walled Templates 0.0.4
Describe the issue
When 5e style templates is turned on, the border squares of a template are not blocked by walls using Walled Templates. The inside of the template is still blocked though. It works without 5e style templates turned on.
Screenshots (Optional)

This is a known thing. I don't really know how I can prevent this as the math to calculate those tiles is very complex and would not be easy to constrain to walls.


Discord invite?

The Discord invite is expired. Does anyone have a new one?

This project is dead.


Add document describing progress and problems encountered during development of SPI interface

@arturkow2000 Let' s add it to the mkdocs.yml please, so it's visible on the rendered page

Please also do that for the missing documents you added last time - like the TPM specification overview.


Dashboard to view daily job applications

Describe the task
We need a dashboard to show daily new job applications.
Expected behavior

[x] SQL Query to fetch daily job applications
[x] Use a graph library to show a bar-graph
[x] By default it will show for the past 7 days. But there will be a filter to adjust the report duration and graph should update.

References
Designs to be worked on in ColoredCow/portal#810

Changes need to be  done
Change the bar to vertical
Make the file code file smaller
Center align
Dates format To date should be less than From date

@kickb71 here are the design files:

Prototype
Design guide

Please make sure you build the basic functionality and finish this. The download option, filter by option and other graphs can be worked on later as a separate issue.

@rathorevaibhav & @kickb71 while testing this I am getting this error on clicking view button.

There are some updates required here but I think we can close this. Will target separately in #943


SSR compatibility

Hi Chen !
Is this lib ssr compatible ? All dist files have references to document which choke up node.js when I try to run server-side ...
Thanks

This is just a simple Vue component as all others. If you want to know how to use it by SSR, you may need to search the official documentation of Vue.js for a common solution.


Added visual extension link buttons

Fixes #73
Is complementary to #69

might hold fire until we can get it on the app store, or maybe remove the mac app store + safari links for now?

might hold fire until we can get it on the app store, or maybe remove the mac app store + safari links for now?

It can still be merged and the other Opera button can be made to point to the github readme instructions and the apple one can be removed


Fix compatibility problems with GA

Ease GA integration by allowing to use the name ga for the tracker function returned by MozillaResearch.telemetry.ga.create method since that's the popular name used in the Google Analytics guides. Also, allow to use routed messages.

Fixed by #200


Update an example to use a more accurate abbreviation.

"I.e." is short for "id est", which means "that is". It should be used to clarify something, perhaps by rephrasing. Unfortunately, here, it serves to limit the what it means for the header to grow complex. Using "e.g." makes it clear that the hypothetical suggestion is merely an example of how the header may grow to be more complex.

Indeed


Could not install it on Laravel 9

Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires asantibanez/livewire-calendar ^2.1 -> satisfiable by asantibanez/livewire-calendar[2.1.0].
- asantibanez/livewire-calendar 2.1.0 requires illuminate/support ^6.0|^7.0|^8.0 -> found illuminate/support[v6.0.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev] but these were not loaded, likely because it conflicts with another require.

If I try to add "illuminate/support" to composer.json I get a conflict with laravel framework, what is the correct way to fix this?

Same issue here

Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires asantibanez/livewire-calendar ^2.1 -> satisfiable by asantibanez/livewire-calendar[2.1.0].
- asantibanez/livewire-calendar 2.1.0 requires illuminate/support ^6.0|^7.0|^8.0 -> found illuminate/support[v6.0.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev] but these were not loaded, likely because it conflicts with another require.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.

Same issue here :(

Same issue.  Would love to us this!

Facing the same issue, I reported this on the sample app, glad to see I'm not alone with this issue on L9.
I get the below when I do a composer require same as reported by @kaizerenrique:
Problem 1

Root composer.json requires asantibanez/livewire-calendar ^2.1 -> satisfiable by asantibanez/livewire-calendar[2.1.0].
asantibanez/livewire-calendar 2.1.0 requires illuminate/support ^6.0|^7.0|^8.0 -> found illuminate/support[v6.0.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev] but these were not loaded, likely because it conflicts with another require.

When will this package be upgraded to L9?

If you fork the repo, then you can make the change to support 9.x yourself until it's sorted, just edit composer.json
Where it reads:        "illuminate/support": "^6.0|^7.0|^8.0",
Replace with:        "illuminate/support": "^6.0|^7.0|^8.0|^9.0",
It'll then work as expected.  Currently waiting on @asantibanez to merge @Butochnikov pull request which does exactly that.

How do I install a forked repo in L9?

Rather than forking it yourself, you may as well take advantage of
In your composer.json add the following which will use the repository which @Butochnikov has already forked and updated.
"repositories": [{     "type": "package",     "canonical": false,     "package": {         "version": "master",         "name": "asantibanez/livewire-calendar",         "source": {             "url": "https://github.com/Butochnikov/livewire-calendar.git",             "type": "git",             "reference": "master"         }     } }]
Then run
composer require asantibanez/livewire-calendar:*
It'll then install for you.
Just remember to undo that and use the original when @asantibanez gets around to accepting the pull request.

It worked, thank you so much! I had been looking for quite a while trying to figure this out.

Now it says asantibanez/livewire-calendar class not found.  I give up.

Same issue. I Would love to use this!

@abbasmashaddy72 @lrljoe this one also works:
Add in composer.json
    "repositories": [         {             "type": "vcs",             "url": "https://github.com/Butochnikov/livewire-calendar"         }     ],
and then composer require asantibanez/livewire-calendar
Works in php 8.0, 8.1 + Laravel 9

Thanks Installed Without any issues

Now it says asantibanez/livewire-calendar class not found. I give up.

I got this too, add the following to composer.json:
"autoload": {
        "psr-4": {
            "Asantibanez\\LivewireCalendar\\": "vendor/asantibanez/livewire-calendar/src/"
        }
    }

@rabol
You follow the above instruction
https://github.com/asantibanez/livewire-calendar/issues/32#issuecomment-1172882028

Is this package abandoned?

No
But Currently Not Yet Compatible with Laravel 9
You follow the below instruction
You Can Install without any issues
@kurucu
https://github.com/asantibanez/livewire-calendar/issues/32#issuecomment-1172882028

I have it installed and working, but the last code to be committed was in  January 2021. All that’s needed is a PR to be merged and tested, so it seems abandoned.

the described solution is just a work-around - if one do this, then one is ,issing out on any new updates!
Either the original author make the changes or someone has to clone and maintain

You are right @rabol

I have cloned this repository and will apply all PR's within the next 1-2 days

Hi Steen, will submit some PRs for some of the features I've added in later in the week.
Joe
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Steen Rabol @.>
Sent: Wednesday, November 16, 2022 10:51:04 PM
To: asantibanez/livewire-calendar @.>
Cc: Joe McElwee @.>; Mention @.>
Subject: Re: [asantibanez/livewire-calendar] Could not install it on Laravel 9 (Issue #32)
I have cloned this repository and will apply all PR's within the next 1-2 days
—
Reply to this email directly, view it on GitHubhttps://github.com/asantibanez/livewire-calendar/issues/32#issuecomment-1317511754, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZATUOXVIWGYXUNXPUIAEW3WIUUJRANCNFSM5TADHBTQ.
You are receiving this because you were mentioned.Message ID: @.***>

I have cloned this repository and will apply all PR's within the next 1-2 days

Great News

Rather than forking it yourself, you may as well take advantage of someone else's fixed fork.
In your composer.json add the following which will use the repository which @Butochnikov has already forked and updated to work with Laravel 9.
"repositories": [{ "type": "package", "canonical": false, "package": { "version": "master", "name": "asantibanez/livewire-calendar", "source": { "url": "https://github.com/Butochnikov/livewire-calendar.git", "type": "git", "reference": "master" } } }]
Then run composer require asantibanez/livewire-calendar:*
It'll then install for you.
Just remember to undo that and use the original when @asantibanez gets around to accepting the pull request.

In the terminal I had to use.
composer require asantibanez/livewire-calendar:dev-master

Works with PHP 8.2.3 Laravel 10.11.0

Rather than forking it yourself, you may as well take advantage of someone else's fixed fork.
In your composer.json add the following which will use the repository which @Butochnikov has already forked and updated to work with Laravel 9.
"repositories": [{ "type": "package", "canonical": false, "package": { "version": "master", "name": "asantibanez/livewire-calendar", "source": { "url": "https://github.com/Butochnikov/livewire-calendar.git", "type": "git", "reference": "master" } } }]
Then run composer require asantibanez/livewire-calendar:*
It'll then install for you.
Just remember to undo that and use the original when @asantibanez gets around to accepting the pull request.

In the terminal I had to use.
composer require asantibanez/livewire-calendar:dev-master

i want to laravel 10 support. who can help me please ?

i want to laravel 10 support. who can help me please ?

Run:
composer require asantibanez/livewire-calendar:dev-master

This should give you L10 support.

same issue ( i tried the  solutions above )

same issue ( i tried the solutions above ) laravel 10.35.0

for me worked updating the composer.json as noted from shanerbaner82 (in his merge pull request):
 "php": "^7.2|^8.0|^8.1|^8.2", "illuminate/support": "^6.0|^7.0|^8.0|^9.0|^10.0",
Then i run : `composer require asantibanez/livewire-calendar -W


Meta processor - allows undocumented leading spaces

The RE for matching the start of a meta data entry allows for 0-3 leading spaces.
This does not appear to be documented.
Also I wonder why is it permitted?
It would help to explain this.

That was implemented many years ago so I can't recall exactly what the thinking was. However, there are a few different reasons why we might have made that choice.

The syntax was copied from other implementations. It is very likely that those implementations had the same behavior.
Markdown syntax is intentionally very forgiving. Four spaces of indent would make for an indented code block. Therefore any less that four spaces would not be a code block. It seems odd to allow three spaces of indent for a paragraph, but not other elements. Therefore, for consistency with the rest of the syntax, the same flexibility was implemented for meta-data.

So then, why not document it? Because it is not documented for the other elements either. While the parser is permissive in what is allows, such sloppy Markdown is not actually encouraged. Therefore, the documentation covers how to form well-formed Markdown.
I should note that I am aware that not everyone agrees with this approach. However, this approach is based on the view of the original creator of Markdown (John Gruber). We try to stay true to his approach even if we personally disagree and would prefer to do things differently.
Of course, if you would prefer your Markdown parser to work differently, then you can create your own extensions which work how you want. Or you are free to use a different parser.


Model outputs are not able to export into the robyn_object directory after update to 3.8.2

Project Robyn
Describe issue
Robyn is not able to plot the model outputs into the robyn_object directory. The following error is thrown:
`>>> Running Pareto calculations for 6000 models on auto fronts...

Automatically selected 2 Pareto-fronts to contain at least 100 pareto-optimal models (144)
Pareto-Front: 1 [65 models]
00:00:08 [===========================================================] 100% | 65
Pareto-Front: 2 [79 models]
00:00:10 [===========================================================] 100% | 79

Calculating clusters for model selection using Pareto fronts...
Auto selected k = 4 (clusters) based on minimum WSS variance of 5%
Collecting 144 pareto-optimum results into: /Users/jss/Desktop/Ollies/Ollies_Robyn/PROS_v_RMK/Robyn_202211232105_init/
Exporting general plots into directory...
Exporting pareto results as CSVs into directory...
Exporting pareto one-pagers into directory...
Generating only cluster results one-pagers (4)...
Plotting 4 selected models on 1 core (MacOS fallback)...
|                                                                                |   0%Failed exporting results, but returned model results anyways:
Error in {: task 1 failed - "Problem while computing aesthetics.
ℹ Error occurred in the 1st layer.
Caused by error in .data$channels:
! Column channels not found in .data."`

Provide reproducible example
The error was encountered with real time data. A run with out-of-the-box demo.R confirms the error.
Environment & Robyn version

Robyn 3.8.2
R version 4.2.2

I've just pushed a fix. could you please update and test it again?


Trim feature

So I'm using this library, and it's working great!
I noticed there wasn't a trim feature, so I've started hacking a workaround:
#!/bin/sh

TEXPACK="/home/seppi/repos/texpack/bin/texpack"
TEMP=`mktemp -d`
NAME="ships"
CWD=`pwd`

rm $NAME*.png
rm $NAME*.json

for file in *.png
do
  convert $file -trim +repage $TEMP/$file
done

cd $TEMP
ls $TEMP/*.png > image_list.txt
$TEXPACK --padding=2 -e image_list.txt --output=$NAME --max-size=512x512
mv $NAME* $CWD
cd $CWD

rm $TEMP -rf

While this works well enough for my purposes, the ships.json output doesn't have the images original size (due to convert trimming it).
What would be amazing is if there was a --trim flag of some sort that I could use, that would mention the images original size, and it's current dimensions in the atlas.
Otherwise I can probably hack something together, but it wouldn't be pretty :cry:

I'm glad you found this little tool useful :)
I had this trim feature in mind as well so I decided to implement it. I tested it rather quickly so let me know if you find any problems. With the --trim flag it should remove transparent borders and you will get these additional properties in the output json file: real_width, real_height, xoffset and yoffset.

Oh my god you have made my day.... <3
It works fantastically!

http://pastebin.com/raw.php?i=TYGCrBuH


Npm run build error: MV2&3, Vue, TS

npm init @samrum/vite-plugin-web-extension@latest vite-web-extension

√ Manifest version: » Manifest V2 & V3
√ Framework: » Vue
√ Add TypeScript? ...  Yes

npn install

npm WARN deprecated<EMAIL_ADDRESS>WARNING: This project has been renamed to @johnsoncodehk/html2pug. Install using @johnsoncodehk/html2pug instead.
npm WARN deprecated<EMAIL_ADDRESS>this library is no longer supported
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated<EMAIL_ADDRESS>WARNING: This project has been renamed to @volar/pug-language-service. Install using @volar/pug-language-service instead.
npm WARN deprecated<EMAIL_ADDRESS>WARNING: This project has been renamed to @volar/typescript-language-service. Install using @volar/typescript-language-service instead.
npm WARN deprecated<EMAIL_ADDRESS>WARNING: This project has been renamed to @volar/vue-language-service. Install using @volar/vue-language-service instead.
npm WARN deprecated<EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.

added 680 packages, and audited 681 packages in 2m

73 packages are looking for funding
  run `npm fund` for details

10 vulnerabilities (9 moderate, 1 high)

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.

npm run build

><EMAIL_ADDRESS>build
> vue-tsc --noEmit && vite build

src/components/PageContent.vue:2:14 - error TS2304: Cannot find name 'imageUrl'.

2   <img :src="imageUrl" height="45" alt="" />
               ~~~~~~~~

src/entries/contentScript/primary/App.vue:3:16 - error TS2304: Cannot find name 'logoImageUrl'.

3     <img :src="logoImageUrl" height="50" alt="" />
                 ~~~~~~~~~~~~

src/components/PageContent.vue:6:33 - error TS2304: Cannot find name 'increment'.

6   <button type="button" @click="increment">Clicks: {{ count }}</button>
                                  ~~~~~~~~~

src/components/PageContent.vue:6:55 - error TS2304: Cannot find name 'count'.

6   <button type="button" @click="increment">Clicks: {{ count }}</button>
                                                        ~~~~~

node_modules/@vue/runtime-core/dist/runtime-core.d.ts:1846:33 - error TS2344: Type 'HostElement' does not satisfy the constraint 'RendererElement'.
1846     transition: TransitionHooks<HostElement> | null;
                                     ~~~~~~~~~~~

  node_modules/@vue/runtime-core/dist/runtime-core.d.ts:1828:57
    1828 export declare interface VNode<HostNode = RendererNode, HostElement = RendererElement, ExtraProps = {
                                                                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    This type parameter might need an `extends RendererElement` constraint.

Found 5 errors in 3 files.

Errors  Files
     3  src/components/PageContent.vue:2
     1  src/entries/contentScript/primary/App.vue:3
     1  node_modules/@vue/runtime-core/dist/runtime-core.d.ts:1846

Thanks. Seems like vue-tsc needs to be updated in the templates and the tsconfig needs to be tweaked.
If you want to get it working with what you have:

npm install -D vue-tsc@latest
Add "skipLibCheck": true, to tsconfig.json

I'll update the templates as part of the next release.

This should now be fixed with the latest versions of create-vite-plugin-web-extension and vite-plugin-web-extension


Update error checking of uuid generate

Found an error while attempting to build. UUID returns UUID, error
type Generator interface {
...
	NewV4() (UUID, error)

Thank you for this PR, but we've merged #369 instead.


Updated method of modelchain.ModelChain.prepare_inputs in modelchain.py

#523
Added weather data arguments in get_solarpostion method of modelchain.ModelChain.prepare_inputs as part of the Pull request.

[x] Closes #523
[x] I am familiar with the contributing guidelines
[x] Pull request is nearly complete and ready for detailed review.
[x] Maintainer: Appropriate GitHub Labels and Milestone are assigned to the Pull Request and linked Issue.

This issue closes #523

@Ahanmr thanks for the contribution. Looking at the test failures, the code needs to handle the case where pressure or temp_air is not in weather. @wholmgren suggested using pvlib.tools._build_kwargs here, which I think would work nicely. There's an example here.
In this context, the code would be like:
    kwargs = _build_kwargs(['pressure', 'temp_air'], weather)
    kwargs['temperature'] = kwargs.pop('temp_air')
    self.solar_position = self.location.get_solarposition(self.times,
        method=self.solar_position_method, **kwargs)

@wholmgren note the unfortunate need to rename.

@cwhanse I've made the necessary changes. Thank you for letting me know about the pvlib.tools._build_kwargs which help me pass keyword arguments in case some are missing. But I still feel I missed something, I'll try fixing it meanwhile.


test/runtime: fix flake on non-ready endpoints

See commit messages for details.
Fixes #18625

/test-runtime

The PR is only affecting runtime tests and these passed. Review is in, so marking as ready to merge.


Technical Demo video from readme not working

Request URL: https://translation.io/videos/rails.mp4
Request Method: GET
Status Code: 401 Unauthorized

Hi Christi,
Thanks for your issue. We had removed the video from our website a few months ago, but we forgot to update the README file in this repository.
I'm posting a copy of the video here below, for you to watch it:
https://github.com/translation/rails/assets/2227137/06442618-c220-412d-8a9d-15e0ad3dc75c
If you have any question, feel free to reach out to us on<EMAIL_ADDRESS>Also, you can try all features on Translation.io for free during your trial period (no credit card required.


Changed intent priority from a distance from root node priority (brea…

Changed priority ordering of intents as per #27
Related Issue
Fixes #27

Pull Request Test Coverage Report for Build 117

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 110:
0.0%

Covered Lines:
1041

Relevant Lines:
1041

💛  - Coveralls

I explored doing that and it looks like we will have to completely change the way our selection process for categorical and numerical intents works (right now numerical almost always matches and categorical only matches in some circumstances) I think making that change is a bit out of scope for this exact issue. We can open a new issue for reversing that.
I would also like to consult @adithyabsk before making a change as he wrote that selection code.

@robocoder99 Can you open that new issue and put in what you find so that we can track the discussion with @adithyabsk ? Thanks.


Overlapping LLR + ADMM update scheme

Hi,
I implemented a few things in this PR (sorry for not separating them):

I implemented a proximal function for overlapping LLR
I multi-threaded the LLR proximal
I added a second update scheme for the ADMM algorithm which has proofen more robust for our use-case.

The first two changes are non-breaking and there should not really be any downside. The last one is breaking as I changed the keyword argument vary_rho from type Boolean to Symbol to facilitate the 3-way option. Also, this update scheme does come at a small price: we have to store a "old" version of x and u--a reasonable price if IMHO, but that is, of course, subjective.
LMK what you think!

Regarding multi-threading I don't use Polyester anymore since it can lead to issues with the regular Julia thread pool. In particular it can make FFTW slower: https://github.com/JuliaSIMD/Polyester.jl/issues/63. Instead please use https://github.com/JuliaFolds/FLoops.jl, which makes no problems und uses the regular Julia thread pool. I already use it in NFFT.jl and we will soon switch in MRIReco.jl as well.

@migrosser: Could you please have a look at the interface change (point 3) and comment if this breaks code somewhere? By bumping the version number this can be handled without too much problems IMHO.

I think the interface change looks fine and I am not aware of any code that it would break.
A small proposal from my side would by to document the possible values for vary_rho in the doc-string of the solver. I know that we are often somewhat lazy when it comes to documentation, but this would make it easier to grasp the possible options.

@tknopp : The point re Polyester is interesting I will keep that in mind for all packages. The problem with Threads.@threads is that this actually caused reproducible segfault errors in BLAS (I am assuming during the SVD, the error message is not clear though). I can try out Floops, but if it uses Threads, I would assume it has the same problems.
@migrosser : Yes, documentation is definitely not great yet. I am swamped for next month, but I add it some time in June, but feel free to add it if you want it earlier! I was contemplating about a change of the interface anyways to a) harmonize it with InterativeSolvers.jl and b) allow calculating the back projection a-priori. Essentially, I was thinking--in line with InterativeSolvers.jl, that it might make sense to consider only AHA operator within the algorithm. I think this would a) make sense from a mathematical perspective and b) would allow one to, calculate the back projection, delete the data, and then calculate, e.g. Toeplitz kernel, which minimizes memory usage. Further, it means that one does not have build the operator A and implement or fake its forward multiplication if one has an implementation for AHA. But again, from my end we are talking at least June....

Threading situation is complicated right now. As far as I recall, Threads.@threads does not work with the new threading runtime (partr), which might cause the issue. FLoops uses the partr and hopefully should be fine. I actually consulted people in the multi-threading slack of Julia when investigating this.


Redirect root route to /index.yaml, fix issue comparing Azure timestamps

Fix for issues #46 and #47

FYI: Helm CLI doesn't currently follow the redirect just 404s.
See https://github.com/kubernetes/helm/issues/3531

I am having second thoughts about this. If the use case is user driven, could a simple html be served to help the user about the usage of the service ? This way chartmuseum keeps ownership of the format as opposed to deciding that the root will forever serve the index.yaml...

closing this for now until we agree on #46 . Going to open a new one that just fixes #47


[PdrDashboard] Post v0.5 improvements

TODOs / DoD

[x] #1560 - Norbert Improvements around the queries to have less and reuse data between pages.
ex: use the same function to get all predictoors related data before the app starts in one place instead of using 1 method for home page predictoors table(payouts_stats) and Predictoors page table (predictoor_payouts_stats). The 2 table should have the same data source
[ ] #1571 - NorbertDisplay available lake date period at the top of the page and allow date period selection by button click
[ ] Switch from payouts to bronze_predictions which are incrementally updated
[ ] Identify wallets( up and down )  that are part of the same manager contract and display them as 1 wallet
[ ] Improve gas fee costs to better reflect boundled tx or other improvements to save fees
[ ] Integrate remote lake data to easily visualize all historic data without taking a lot of time fetching the data locally
[ ] Add more columns to home page feeds table: Avg Accuracy, Sales and fix column sorting for both tables from home page - #1572 - Mustafa

 Switch from payouts to bronze_predictions which are incrementally updated
Do we need it? The current queries rely on the payouts and are well tested.

Do we need it? The current queries rely on the payouts and are well tested.

If we want to have more accurate/up to date data then yes.
Right now we relay on certain calculations only on payout data and that could be outdated(User has to claim), for example there were cases where people were only calling the payout for right predictions( on this case, we also have to also look to predictions and consider those where there was no payout as loss or wrong ).

I am okay with this explanation, so I look at it


Sould be WindowsError not WinError

This fixes issue when trying to run unit tests on 64bit python in visual studio 2015.
https://docs.python.org/2/library/ctypes.html states that WinError is a wrapper that raises WindowsError which is the builtin python exception that is trying to be trapped.
I have opened a bug #1032, which this pull request should fix.

Hi @zwing99, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

:+1:

Thanks for the fix @zwing99 !


Fix incorrect word

See complimented vs. complemented.
This is such a cool project, excited to learn more about it! :)

Thanks for the contribution, @jhgilbert! Happy to have you around.


Backport "Skip all ruby distrib tests that use ruby 2.2" to 1.22.x

Backports https://github.com/grpc/grpc/pull/19414

Merging early to fix the package build

C# linux: 503 fetching from github
portability tests linux: 503 fetching from github
Basic tests C/C++ macos: fatal: protocol error: bad pack header fetching Cocoapods from github
Objc mac/ios/examples not showing results but marked as failed
Interop tests: dart failed to build

Merging early to fix the package build