[BUG] Invoke-PnPSPRestMethod not working with PATCH method

Reporting an Issue or Missing Feature
Issue: We are trying to use Invoke-PnPSPRestMethod to update Site name for group connected SharePoint sites, but this doesn't work in this specific API call.
Expected behavior
The response should be 204 No Content.
Actual behavior
This throws the following error:
Invoke-PnPSPRestMethod : {"odata.error":{"code":"-1, Microsoft.SharePoint.Client.ClientServiceException","message":{"lang":"en-US","value":"The HTTP method 'Patch' cannot be used to access the resource 'Update'. The operation type of the resource is specified as 'Default'. Please use correct HTTP method to invoke the resource."}}}
Steps to reproduce behavior
Please use the following script to reproduce (replace the placeholders):
$SiteCollectionUrl = "xxx"
$OfficeUnifiedGroupId = "xxx"
$SiteTitle = "xxx"
$url = "/_api/SP.Directory.DirectorySession/Group('" + $OfficeUnifiedGroupId + "')"
$body = @{
__metadata = @{
type="SP.Directory.Group";
};
displayName= $SiteTitle;
}
Connect-PnPOnline -Url $SiteCollectionUrl -Interactive
Invoke-PnPSPRestMethod -Url $url -Method Patch -Content $body -ContentType "application/json;odata=verbose" -Raw
What is the version of the Cmdlet module you are running?
1.12.0
Which operating system/environment are you running PnP PowerShell on?

[x] Windows
[ ] Linux
[ ] MacOS
[ ] Azure Cloud Shell
[ ] Azure Functions
[ ] Other : please specify

@GuopingSun it works fine here with exactly the script sample you provide. Could there be something on your network connection interfering? Or perhaps a temporary glitch on the server side causing this? Can you run a Fiddler trace and see what happens over the wire when you execute this script?

@KoenZomers I just tested again. It's still throwing that same error, but it works fine when fiddler is running. Do you have any idea why this works with fiddler?

Not sure. Only think I can think of is that your machine could be using a proxy that messes with the traffic? When enabling Fiddler, that will function as the proxy on your machine instead.

Closing as it might be related to the local environment and couldn't be reproduced.


Port Tidal Modeling notebook to DEAfrica Sandbox

Proposed changes

Pull in the coastaltools script from GA and rename to deafrica_coastaltools. This script contains changes necessary for the notebook to run.
Correct import error in deafrica_datahandling which causes the notebook to fail with an error when loading data.
Localize constructed datetime to eliminate naive/non-naive date comparison which causes the notebook to fail with an error when loading data.

Checklist (replace [ ] with [x] to check off)

[x] Remove any unused Python packages from Load packages
[x] Remove any unused/empty code cells
[x] Remove any guidance cells (e.g. General advice)
[x] Ensure that all code cells follow the PEP8 standard for code. The jupyterlab_code_formatter tool can be used to format code cells to a consistent style: select each code cell, then click Edit and then one of the Apply X Formatter options (YAPF or Black are recommended).
[x] Include relevant tags in the final notebook cell and re-use tags if possible
[x] Clear all outputs, run notebook from start to finish, and save the notebook in the state where all cells have been sequentially evaluated

The if block on line 247 of deafrica_datahandling looks like it is intended to be temporary code. Since I have changed it to fix errors perhaps it is worth evaluating whether or not it still belongs there.

@robbibt @cbur24 @uchchwhash @caitlinadams For some reason I can't add reviewers this time so this is my workaround. I checked the GA repository and all of you at one point worked on one or more of the files I changed so I figured you would be good candidates for reviewers. Thanks!

Thanks @jdh-ama , I'll review this this morning!


Feature Request -- Custom Auth

I'd love the ability to do a custom authorization header for requests.
At my current employer we use a private key authorization strategy and it would be great to be able to read a local private key file and then create the signature.

This will likely be accomplished by #51 (plugin framework).

Closing this for now and have made a note on #51 that this should be a supported use case.

@gschier thanks.
Maybe i'll just fork it for now and add our internal Auth header implementation.

@fzakaria sounds good 👍


Several MQTT messages are unable to decode

Problem/Motivation
The log shows several messages were not decoded due to a "UnicodeDecodeError".
Expected behavior
The log do not show any MQTT decode error messages.  Doing so, a potential message is from one device to another device is getting discarded.
Actual behavior
The log is showing the MQTT decode error messages.
Steps to reproduce

Install Appdaemon Add-on.
Install the "Qolsys Gateway - qolsysgw" through HACS.
Configure the Appdaemon to run the Qolsys Gateway.
Observe the Appdaemon log shows several error messages.

Log
2024-09-28 20:16:31.285018 INFO AppDaemon: New client Admin Client connected
2024-09-28 20:16:52.383142 INFO MQTT: Unable to decode MQTT message
2024-09-28 20:16:52.384120 ERROR MQTT: Unable to decode MQTT message, with Traceback: Traceback (most recent call last):
  File "/usr/lib/python3.11/site-packages/appdaemon/plugins/mqtt/mqttplugin.py", line 271, in mqtt_on_message
    payload = payload.decode()
              ^^^^^^^^^^^^^^^^
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 0: invalid start byte

2024-09-28 20:16:52.469429 INFO MQTT: Unable to decode MQTT message
2024-09-28 20:16:52.469850 ERROR MQTT: Unable to decode MQTT message, with Traceback: Traceback (most recent call last):
  File "/usr/lib/python3.11/site-packages/appdaemon/plugins/mqtt/mqttplugin.py", line 271, in mqtt_on_message
    payload = payload.decode()
              ^^^^^^^^^^^^^^^^
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 0: invalid start byte

2024-09-28 20:17:11.707325 INFO AppDaemon: Client disconnection from Admin Client
2024-09-28 20:17:22.250166 INFO MQTT: Unable to decode MQTT message
2024-09-28 20:17:22.251115 ERROR MQTT: Unable to decode MQTT message, with Traceback: Traceback (most recent call last):
  File "/usr/lib/python3.11/site-packages/appdaemon/plugins/mqtt/mqttplugin.py", line 271, in mqtt_on_message
    payload = payload.decode()
              ^^^^^^^^^^^^^^^^
.
.
.

Version

This is a duplicate issue which was already reported here  #350 and it was open.  Hence closing this issue.


ciao-controller: datastore: use Fatal() for test errors

In all cases, if a test fails a check we should terminate the test
instead of continuing. Replace use of Error() with Fatal() in unit
tests.
Signed-off-by: Kristen Carlson Accardi<EMAIL_ADDRESS>

Coverage increased (+0.02%) to 66.361% when pulling 8a71b51d02a70d1938a1cf9d718254d9aef26ce2 on kaccardi:topic/fix-datastore-tests into 584885ad45c33aa18fbebd89de9a758215cf15da on 01org:master.

In addition to going from Error() to Fatal(), can you make them consistent?  Ie: all either Fatal(err) or Fatal("string")?  Unless there's a reason for the mixing around of different arguments to Fatal() that was already there.

Coverage increased (+0.02%) to 66.361% when pulling ece2208b47cf40c125c4b9c7b5cf0fc9d78bb962 on kaccardi:topic/fix-datastore-tests into 584885ad45c33aa18fbebd89de9a758215cf15da on 01org:master.


Bug Report 'Game Mode' or 'Editor Mode' button in UI doesn't show completely

Describe the bug | Bug描述
Latest version (e5d43bc
Incomplete presentation of 'Game Mode' or 'Editor Mode' Button
Steps to reproduce | 如何复现

Just open the Pilot Engine

Expected behavior | 预期行为
It shall show the complete text.
Screenshots/Logs | 截图/日志

Desktop | 桌面环境

OS: Windows
Version: 10
CPU: 15-9400H
GPU: NVIDIA GeForce GTX 1660Ti
Memory: 16GB
Compiler: MSVC2019
Screen resolution: 1920x1080

What is your resolution scale at 1080p?
Is that 100% or something like 150%?

What is your resolution scale at 1080p? Is that 100% or something like 150%?

it's 125%, recommand by windows for my laptop, I think I shall use 100% instead of 125%, thanks.

Should be fixed by #118, plz reopen if still exists


all proxies are invalid

when i finish putting the amount and every other thing. it just says "all proxies are invalid" with checkers on.
please help...

and i dont know if this is supposed to happen but it says...
If no, every check will be on random proxy.
[ > ] Multiple checks for proxy (yes or no):

That's beacuse you used proxy scraper, which is not that good. To make it work fast and properly you must find or buy some good HTTPS proxies

thanks, it didnt work for me, but thank you!!

Throws a list index out of range, when proxies.txt is empty https://github.com/lnxcz/nitro-generator/blob/4251c5e2f4b998b6b7fa72d9d373c948dee3357c/main.py#L91
Throws a Not supported proxy scheme (proxies=proxies) https://github.com/lnxcz/nitro-generator/blob/4251c5e2f4b998b6b7fa72d9d373c948dee3357c/main.py#L110

@luissilva1044894 Make a separate issue. I will be working on it in the meantime :)

@CTRL-ALT-EXIST Well... I just reported cuz there are some exceptions being handled by those try/catch, and isn't directly related to using proxy scraper.
I'm not using this project and I don't want to.

@Robatortas if this issue is solved please close it


feat: new SearchBar with vuetify Toolbars (#17)

Tasks:

[x] Modify Search bar to use vyetify toolbar
[x] Add Search Bar in HeaderDetailPage
[ ] Test

Tasks for #16

[x] Update containers
[x] Update code

Tasks for #15

[ ] Implement VariantDetailPage
[x] Add routes/stores/etc.
[ ] Test

Notes:

Clinvar does not show data, as it's not clear, which data does it need
isVariantMtHomopolymer in FreqMitochondrial does not work, as it's not clear, how to retrieve smallVar start and end positions.


Add Aeotec ZW141-A EU firmware version 3.6

@Aeotec-ccheng, can you review this please?
File link obtained from: https://aeotec.freshdesk.com/support/solutions/articles/6000229404-nano-shutter-zw141-update-z-wave-firmware-

Sent some changes that needed changes

File name and model number should be ZW141-C
SHA hash needs to be updated

This looks good with the changes, i can add in -A and -B later on.


[MINOR] Fix some project construction problems about test sources

Fix some project construction problems about test sources

"src/test/org.apache.eagle.xxx" -> "src/test/java/org.apache.eagle.xxx"

Involved modules:

eagle-hbase-web
eagle-hdfs-web

@asdf2014 what's the changes? If no, could you please help close it?

@haoch Done


refactor: add filter keyword function to replace spaces with %20

I added filterKeyword.js in utils folder to filter all spaces in the keyword (/src/controller/api/twitterAPIController) and also a test file to make sure that it does work properly!
And all double quotes inside files that I opened are changed in single quote by prettier. Sorry about that :sweat:
Close #119

Seems like there is some issues with the actions.
@MizouziE am I missing some configurations to make the deployment pass or?
I found this interesting issue about the action.
Perhaps we need to add another step?
Let me know what do you think about it

@TAKANOME-DEV Ah sorry! No it's my fault cos I was messing with other options for hosting and started playing with new CI/CD stuff. It's perfectly fine to ignore at the moment as it doesn't actually deploy anywhere. I have a solution in the pipeline that will be able to make use of the actions, so I didn't bother removing it as I'll just need to update it once my server is in place.
We'll soon be saying bye-bye to heroku! 🙌


Requesting the key, I found the firmware but don't know how to get the password, can you help me? Thank you so much

http://data.onyx-international.cn/api/firmware/update?where={"buildNumber":0,"buildType":"user","deviceMAC":"","lang":"zh_CN","model":"SP_PokeL","submodel":"","fingerprint":""}
This is my firmware address，it is SuperStar (chaoxing) verison，model is SP_POKEL
it's not in the list
My device stopped turning on because I tried to use RKDevTool to modify the system.
Please help me unpack it. I hope I can extract the correct system files and repair the device. Thank you very much.

Can you access /system in recovery? You'll probably have to mount it.
Without a copy of /system/priv-app/OnyxOtaService/OnyxOtaService.apk we can't do much.
If you can use Rockchip tools to copy the entire system partition we can probably find that apk.
The  update is encrypted.
Model:  SP_PokeL
Finger: Onyx/SP_PokeL/SP_PokeL:4.4.4/2019-04-30_20-20_super-star_cde7b0b/828:user/dev-keys
Link:   http://onyx-firmware.oss-cn-shenzhen.aliyuncs.com/1bb3b432698e18fdb1fb97aa5f347e7d.upx
Size:   304,028,566
MD5:    1bb3b432698e18fdb1fb97aa5f347e7d

I extracted the system partition from POKEL that others can run normally. These are all the priv-apps. Which one is needed?

https://drive.google.com/file/d/18GzRCcsqv-6vFQ2rz8RqWWyjPCfneSpR/view?usp=drive_link
This is the extracted system

That isn't public, I can't view it.

https://drive.google.com/file/d/18GzRCcsqv-6vFQ2rz8RqWWyjPCfneSpR/view?usp=sharing
Sorry, I use Google Cloud Drive less, but it should be fine now, thank you very much

Oh, it was in /system/app/OnyxOtaService.apk
SP_PokeL,SP_PokeL,6E01CB5A77A96F675561AE7CB7CAF6AC,DEAEF764C4290B4039EA7DDC2110A7B2
There's a PR in for this.

Thank you very much. You are really a very enthusiastic and kind person. Thanks to your help, the file can be decrypted normally.


get input randomly returns 110

The get input method doesn't appear particularly reliable: I randomly see 110 when calling the method on two different monitors from two different vendors.

+1
./m1ddc display list detailed works fine.
./m1ddc display 1 get c should display the contrast of display 1 but always shows "110", same on other parameters.

+1
Working around it by retrying until value is <= 100


Flickering Black Screen With Multiple Monitors

Microsoft PowerToys version
0.83.0
Installation method
PowerToys auto-update
Running as admin
Yes
Area(s) with issue?
FancyZones
Steps to reproduce
Turn on Power Toys.  Move Application Window from One Fancy Zone to Another or from one monitor to another.
✔ Expected Behavior
No flickering when moving items between zones or moving application windows around on the monitor/screen.
❌ Actual Behavior
When PowerToys is enablabled, and I attempt to move application windows around on screen or betwen Fancy Zones, the monitor starts flickering from black and then back to normal operation and at times disconnects from the the system and then reconnects.  This behavior does not seem to occur when PowerToys is disabled or turned off.  This only seems to happen on one monitor that I have -- the largest monitor on my system.  I have 8 total monitors connnected to my systemas shown below:

The monitor that starts to flicker (#2 above) is Onn TV/Monitor that has the following specifications:

Resolution set to 4096x2160
150% scale and layout
Refresh rate is set to 30.000 Hz
Bit Depth:  8-bit
Color format:  RGB
Color space:  Standard dynamic range (SDR).).

Again, only the large monitor flickers when moving applications between zones and only when PowerToys is enabled.
I have attached a video to this ticket so you can see the actual behavior.  In the video, I drag a window from another monitor (monitor #8) onto the larger monitor (monitor #2) and you will see the screen goes black.  After a bit of time the screen comes back.  I then start dragging the window into different zones and after some time when moving between zones, the screen goes black again and finally comes right back.
https://github.com/user-attachments/assets/c42c7a3d-aad9-47b6-84f9-e79749d28f33
Other Software
Windows 10, Version 22H2 (OS Build 19045.4651).  PowerToys v0.83.0
Generic PnP Monitor and Intel HD Graphics 4600 Properties:
Chip Type:  Intel HD Graphics Family
DAC Type:  Internal
Bios Info:  Intel Video BIOS
Total Available Graphics Memory:  2176 MB
Dedicated Video Memory:  128 MB
System Video Memory:  0 MB
Shared System Memory:  2048 MB.
===========Problematic Monitor Specifications:===========
Onn. TV/Monitor Model Number:  100133204
Hardware ID:  G829X
Software Version:  13.0.0, Build 24062-CT

/reportbug

wondering if this is the dwm crash from pt run


Add unit tests for warning offline user

Summary

Two new unit tests for anonymous and identified EvilRequest when the recipient is offline
Move recipientSession into the test table
Some misc cleanup of existing tests/comments

Testing Done
All icbm foodgroup unit tests pass. Running all unit tests for the project also pass, and verified building ras was successful.
 Codecov will compare coverage reports and display results in all future pull requests.
Thanks for integrating Codecov - We've got you covered :open_umbrella:

Updated sessions to nil, rerean and tests pass
Running tool: /opt/homebrew/bin/go test -timeout 30s -run ^TestICBMService_EvilRequest$ github.com/mk6i/retro-aim-server/foodgroup

ok  	github.com/mk6i/retro-aim-server/foodgroup	0.227s


lxd/device: Adds arp check for nic routed device.

When adding a routed nic device, check that the given ip address is
not in use during input validation via ping.
Closes #9547

I realise this is draft, but in case you've not already figured it out, this won't be sufficient to handle the IPv6 NDP scenario, as the package you've used (which looks fine for IPv4 from what I can quickly see) won't work for IPv6 addresses.

Thanks! I marked as draft because the integration test for container_devices_nic_routed is failing with an IPv4 address though. I'll look into that first then handle the v6 case.

All tests appear to be failing.

Testsuite passed

Testsuite passed

I'd like to merge this early tomorrow in preparation for LXD 4.22.
Given the timeline and our setup for routed tests, I think it'll be easier to merge this one without a test in place.
So I'd say drop the test for now, address the existing feedback (concurrent validation of addresses) and we should be good to go.

So structurally, I think I'd prefer to have a isIPAavailable(address net.IP, parentInterface string, timeout time.Duration) error which then does either ARP or NDP depending on the address passed. That function would be blocking for up to the timeout.
The the caller function can do a loop through all IPv4 and IPv6 addresses, create a channel and spawn one go routine per address, that go routine would run isIPAvailable and put the error in the channel.
The parent then checks for errors on the channel and return it if one.

@markylaing bit of code reshuffle to do, shouldn't take too long. Let me know if you don't have time to do it before you EOD and I'll take it over.

So structurally, I think I'd prefer to have a isIPAavailable(address net.IP, parentInterface string, timeout time.Duration) error which then does either ARP or NDP depending on the address passed. That function would be blocking for up to the timeout.
The the caller function can do a loop through all IPv4 and IPv6 addresses, create a channel and spawn one go routine per address, that go routine would run isIPAvailable and put the error in the channel.
The parent then checks for errors on the channel and return it if one.

Rather than timeout it should take a context. Then we can cancel any ongoing routine if one fails.


Host::call_account_contract_check_auth requires Contract ID as a BytesN<32> instead of as an Address

What version are you using?
20.0.0-rc2
What did you do?
Call Host::call_account_contract_check_auth with a contract Address.
What did you expect to see?
🥳
What did you see instead?
Compile error because the function requires the contract to be given as a BytesObject.
Discussion
This issue is blocking:

https://github.com/stellar/rs-soroban-sdk/issues/1109

This has been resolved - https://github.com/stellar/rs-soroban-env/blob/74c3c045b7e607cfda9155c1bc00e897b5e5a19f/soroban-env-host/src/auth.rs#L2255


How do I disable JavaScript prefetch?

Hi, There is too much prefetch in the project, hoping to disable this function?
Now, what should I do!!! please help!!! thx!

What do you mean by prefetch? The service worker downloading things in the background?
If yes, just disable the service worker.
https://github.com/vuejs/vue-hackernews-2.0/blob/master/src/entry-client.js#L67

Manual Asset Injection
<html>
  <head>
    <!-- use triple mustache for non-HTML-escaped interpolation -->
    {{{ renderResourceHints() }}}
    {{{ renderStyles() }}}
  </head>
  <body>
    <!--vue-ssr-outlet-->
    {{{ renderState() }}}
    {{{ renderScripts() }}}
  </body>
</html>

@valentinvieriu , @daliborgogic
thank for your help!
question has been solved!!


Cache Busting on Webpack Chunks

Laravel Mix Version: 4.0.16 (npm list --depth=0)
Node Version (node -v): v10.15.3
NPM Version (npm -v): 6.9.0
OS: Windows 10 WSL

Description:
There does not seem to be a good cache-busting mechanism for webpack chunks that plays nicely with Git.
Steps To Reproduce:

Create a standard laravel/mix project the with the mix.version() option.
Create a dynamic import:
import(./dashboard.js /* webpackChunkName: "js/dashboard" */);
just put console.log('version1') in the imported file.
npm run dev -- This creates the following
js/app.js
js/dashboard.js
Go to site, observe version1 in the console
Change the chunk to console.log('version2')
Go to site, observe version1 in the console

The issue:
The mix-manifest file will get versioning, but the webpack chunk mechanism ignores it:
eg
{
    "/js/app.js": "/js/app.js?id=68f34ebc16f9097ba774",
    "/dashboard.js": "/dashboard.js?id=77a5c8ae270db4d8cf2d",
}

Workaround:
Add [hash] to the chunkName, but this causes files to be added/deleted in Git constantly, which is not ideal.
Ideal Solution:
There is a way to make webpack chunks use query-string cache busting like Laravel Mix currently does.

I found out how to do this, but I will leave the solution here for the next person to try to solve this.
First add this to your webpack config:
mix.webpackConfig({
    output: {
        chunkFilename: '[name].js?id=[chunkhash]',
    }
});

Then, when you specify the chunk name using this: /* webpackChunkName: "js/dashboard" */
You will get this as a result: js/dashboard.js?id=0791710073c12eff5a3d in the webpack output dialog.
The file will be saved as js/dashboard.js but referenced in the browser as  js/dashboard.js?id=0791710073c12eff5a3d.

Will the id be identical to the one generated by the mix.version() function (the one you see in mix-manifest)?

Will the id be identical to the one you see in mix-manifest?

I have checked and the ids are different, but even with different ids we verified that cache busting is working with this approach.

Have you tested on mobile? I had to move away from ids/cache busted laravel mix feature as often on mobile it would not actually fetch the new version.

Yes it worked also on mobile. Now we have completely removed Laravel Mix from the project but at the time there were no issue on mobile.

Hmmm, I've tested this out locally and find that once production files are built, dev no longer works. Did you have this also?

Or maybe a better question is, how are you separating out production/local builds?

No. But we had very customized settings: three settings for development (css, js and js for legacy browsers) and three settings for production. Now we have a very different setup so I can't help much.

No worries, thanks @gtempesta !

In my case the [chunkhash] value also differs from the one in mix-manifest.json file, but it seems the correct id is only needed to generate link using mix() function in blade templates.

I faced the same problem today after a deploy to production. Thought the solution above works, what I didn't like is that that is overriding the core Mix chunkFilename() function. So I took similar but slightly different approach to make sure that the core Mix behaviour was kept:
mix.override(webpackConfig => {
    const chunkFileName = webpackConfig.output.chunkFilename;

    webpackConfig.output.chunkFilename = (pathData, assetInfo) => {
        return `${chunkFileName(pathData, assetInfo)}?id=[chunkhash]`;
    };
}


[Support] The library does not support the older digest protocol

Question
The library fails when connecting to an older RFC 2069 API.  Was it intentional that the library doesn't support connecting to legacy digest APIs?  If it was intentional, then IMO the library would benefit by providing a clear error message when the server fails to provide a QOP value.  What happens now is that the AllDataCorrectFilled() method returns false, so the resulting error is: Cannot load all required data from {AuthenticateHeaderName}. Data: {AuthenticateHeader}.  This is not a very clear response and since RFC 2617 does specify that qop is optional (to be backwards compatible to 2069) which makes it hard to understand why it's being flagged as required.
Also, from reading the spec it defines that the h2 hash is built differently depending on the value in the QOP field (as well as whether it is provided at all), and the library does not appear to be supporting all the permutations (specifically, it only appears to support the QOP value of "auth" and not missing, "auth-int", or "auth-conf").  I am not an expert on digest authentication, so maybe there is a nuance here that I'm not seeing (maybe "auth-int" and "auth-conf" are not found in the wild).
I have modified the library for my own use to support RFC 2069, and I started the process of adding differences based on the value of qop, but I lack a test environment that supports the different processes to validate that I'm doing that right (my current requirements are to support the legacy version of digest, the rest was just curiosity).  The main addition that I made is in GetDigestHeader():
    public string GetDigestHeader(string digestUri, Method method)
    {
       if (null == _qop)
        {
            var hash1 = GenerateMD5($"{_username}:{_realm}:{_password}");
            var hash2 = GenerateMD5($"{method.ToString().ToUpperInvariant()}:{digestUri}");
            var digestResponse = GenerateMD5($"{hash1}:{_nonce}:{hash2}");
            return $"Digest username=\"{_username}\"," +
                   $" realm=\"{_realm}\"," +
                   $" nonce=\"{_nonce}\"," +
                   $" uri=\"{digestUri}\"," +
                   $" response=\"{digestResponse}\"";
        }
        else if ("auth" == _qop)
        { <original code here> }

As well as changing AllDataCorrectFilled() to not require the QOP.
Thanks for creating the library!

Hi @42degrees!
I'm sorry for not getting back to you sooner.
I don't see a reason why we shouldn't support older protocol versions. I'll take a look at adding support to the old protocol version compatibility.
Thanks for the feedback!


fix: remove const from parameters in Vector3Length functions

When trying to build the 2d_camera example, there's a build error due to the parameter in the Vector3Length functions having the type const Vector3 instead of Vector3. I don't think const Vector3 is valid Zig.

Are you on Zig 0.10?

Yes, however 0.9.1 produces the same error.

Tested 0.9.0, 0.9.1, 0.10.0 - same error.


WebSocket connections don't seem to upgrade correctly under HTTPS

Do you want to request a feature or report a bug?
Bug
Did you try using a 1.7.x configuration for the version 2.0?

[ ] Yes
[x] No

What did you do?
Tried to create a WebSocket connection through SocketIO over HTTPS.

What did you expect to see?
A successful connection.
What did you see instead?
An unsuccessful connection.
Output of traefik version: (What version of Traefik are you using?)

I've created a minimal example using Flask-SocketIO's example and forced it to use a WebSocket transport. The repo for it is here.
Accessing the app directly (:5000) or through Traefik's HTTP route (:80) works fine, but accessing it through Traefik's HTTPS route (:443) gets stuck where it appears to upgrade and then immediately drops the connection.

You need to add sslheader middleware. Solution can be found here: https://community.containo.us/t/websockets-not-working-after-migrating-to-traefik-2-0/1912

Hmm, it looks like X-Forwarded-Proto is already being set to https in the Traefik logs.
I added the middleware in anyways, but it doesn't appear to have changed anything.
I added these two labels to the service in docker-compose.yml:
- "traefik.http.middlewares.sslheader.headers.customrequestheaders.X-Forwarded-Proto=https"
- "traefik.http.routers.app-secure.middlewares=sslheader@docker"

Hi @Kazakuri , did you solve the issue with the instructions given by @rostikL (thanks!) ?

@Kazakuri That's strange. I have implemented the fix in our application and with the sslheaders middleware it works very well.
I tried your example and can't get it to work there either. Maybe it has something to do with cipherSuites configuration?

I did a lot of research about this problem, I think it is more about Rancher.
Below is the research I did with one of my colleague. Hope it also helps you guys.
Why will we get 302, 403, or even 404 instead of 101 when we delegate Secure WebSocket of Rancher 2.x deployed under HA strategy?
It's a fairly long story, I will keep it short as soon as possible.
If you are using Rancher single node, you shouldn't encounter these problems.
Well, if you are delegating Rancher HA installed under the guide of the official website. You may have these problems, to be more clearly specified, I will start from the very beginning. The whole transfer router will be like bellow when you delegate Rancher HA.

There are three major steps in this situation.

Proxy to External Loadbalancer of Rancher
Switch from https to http by Nginx Ingress Controller to finish the SSL Termination
Hit port 80 of Rancher Container

To answer the first question of why we get 302
First, we need to better understand how Rancher determines if a request should be treated as Https or Http. Because we all know that 302 will be returned if Rancher thinks you are requesting as Http.
If you access 80 of Rancher directly, you will get a redirect to 443, which are handled by the function httpRedirect Below, these logics will only be applied when you hit Rancher on Port 80. I will explain more below.
Below are the source codes of Rancher to handle this logic
located on pkg/dynamiclistener/server.go

From the Line 505) to Line 508, we get to know that Rancher will detect the value of X-Forwarded-Proto to determine if your request should be redirected to a port of **443(According to the function starting from Line 518] )or not, besides personally I have no idea why they mangle port  like this, it’s kind of wired in this situation.  Because if your proxy server run on port 30002, you will get a 302 response which redirect you to port 30443, that's because the calculation in (Line 529). That's what I encountered in my case, in order to find out what's going on here, it cost me and my colleague a whole day.
Ok, now, we can start to explain why you will get 302 in your case. Definitely, it has something with the parameter X-Forwarded-Proto. If your proxy added an extra wss to this parameter or any other, it will fail at Line 505. Then, 302 returned.
Unfortuanately, a lot of wss proxy package will add wss to the X-Forwarded-Proto request header before redirect the request. Like what http-node-proxy(node-http-proxy/ws-incoming.js at 9bbe486c5efcc356fb4d189ef38eee275bbde345 · http-party/node-http-proxy · GitHub) did. In your case, I believe traefik also add something to X-Forwarded-Proto when delegating wss.
Now, I think all the enigma about 302 is resolved. you can verify my explanation by sending ws to 80 of rancher, while with X-Forwarded-Proto to Https, you will find that it was connected successfully. I recommend you test ws with the tool wscatGitHub - websockets/wscat: WebSocket cat and test it like the command below
wscat -c "ws://<IP_ADDRESS>:32273/v3/subscribe” -n -H Authorization:”Bearer token-qt999:kcw55kqgkwsgsj55q2ps6gmpvw99c5vfp5mt4sh8kkwz5mnmk55x2s” -H x-forwarded-proto:”https”

Here my rancher’s 80 port was exposed as 32273, and you should create a Bearer token to test it.
you will find even though you hit the 80 of Rancher, you can still successfully connect to it as long as x-forwarded-proto is set to https, otherwise, it will return 302.
Next, I will explain other problems you may encounter when you delegate Rancher HA behind Proxy, if you are interested in, you can continue to read, just to avoid more people confusing here.
To answer the second question of why we get 403
We all know that 403 returned If your request is invalid. You may ask here why is that all of the https requests are proxied normally, while the wss returned 403. The short answer is that Rancher didn’t disable the Same Origin Policy for wss, while for http request they disabled it.  What’s more, Rancher also need the parameter x-forwarded-host match, I have no idea why they design like this so far. I will give my case why  I triggered the same-origin policy here. Hope it will help others to address the problem they may have.
In my case, my proxy is served on, for example, localhost:3000, and I want it proxy to Rancher at www.test.com. Then, what my proxy does is that set the request like origin:”https://www.test.com”; host:www.test.com; x-forwarded-host:localhost, and then send it to Rancher at  www.test.com. I did this because rancher/ui did the same thing. ui/api.js at fa1b05dc25124aecd175b8f5fdbe18dcdc065fdc · rancher/ui · GitHub. Yes, you are right, even rancher’s developer, they face the same problem if they connect their front-end to HA instance. But I guess they won’t develop UI based on HA.
After I tried a lot of times using wscat, the results below tell me what happened in Rancher.

Maybe someone from Rancher can give a more specified explanation here.
To answer the second question of why we get 404
This is the easiest one to understand, because in step 2 above.  Under the HA strategy, your https request is terminated on Nginx Ingress Controller,  if your ‘host’ didn’t match the domain you set in Ingress rule, the Ingress controller have no idea where you wanna go. The screenshot below showed this case.

I was playing with this a bit more this morning, and the browser shows the 101 Upgrade response fine, but somewhere within the internals of SocketIO there's some sort of internal request bouncing around that fails and closes the WebSocket connection.
From a quick look at it, it's returning a 400 BAD REQUEST because it checks the HTTP_ORIGIN: https://app.docker.local header and it doesn't match http://app.docker.local.
There was a commit to the EngineIO repo recently that added a check against HTTP_X_FORWARDED_PROTO, but there hasn't bee a release for that yet.
In either case, that internal request sends a HTTP_X_FORWARDED_PROTO header with the value wss (despite my attempts to modify it with Traefik middleware) which still doesn't match what it's looking for from the HTTP_ORIGIN header...

I was playing with this a bit more this morning, and the browser shows the 101 Upgrade response fine, but somewhere within the internals of SocketIO there's some sort of internal request bouncing around that fails and closes the WebSocket connection.
From a quick look at it, it's returning a 400 BAD REQUEST because it checks the HTTP_ORIGIN: https://app.docker.local header and it doesn't match http://app.docker.local.
There was a commit to the EngineIO repo recently that added a check against HTTP_X_FORWARDED_PROTO, but there hasn't bee a release for that yet.
~In either case, that internal request sends a HTTP_X_FORWARDED_PROTO header with the value wss (despite my attempts to modify it with Traefik middleware) which still doesn't match what it's looking for from the HTTP_ORIGIN header...~
Edit: Manually updating the EngineIO package to that git commit and applying the Traefik middleware for customRequestHeaders appears to have fixed the issue.

Still facing this issue using Socket.io, can you provide the specific commit that fixed it for you.

Sure, the commit that fixed it for me was 3c221a in python-engineio here.
It got released in v3.11.0

Hi! I'm Træfiker :robot: the bot in charge of tidying up the issues.
Thanks again for your interest in Traefik!
I'm glad to close the issue because I think that the question has been answered (Yes, I'm quite an advanced AI :smile:)
Join our Community Forum for more support.


Windows Firewall is blocking access of entire WSL distro to network after update to the Store version on Windows 11 Dev ring

Version
10.0.22518.1012
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>
Distro Version
Arch WSL (rolling distro)
Other Software
Windows Firewall apparently
Repro Steps
After upgrading WSL to the Store version (through wsl --update) on the most recent Windows 11 Dev ring update, the WSL distros lost access to the internet. Running any command that requires network access times out, unless I manually deactivate Windows Firewall on the host for Public networks (I'm being connected to the Private network though).
Basically, following steps reproduce it for me:

Update WSL to the Store version on the most recent Windows 11 Dev update (wsl --update).
Open any distro.
Run any command requiring network access (i.e. sudo pacman -Syu)

Expected Behavior
All network traffic should go through, just like before the update to the Store version.
Actual Behavior
The commands requiring network access just time out. After deactivating Windows Firewall on the host machine for the Public networks (regardless of the network type the host is currently connected to), everything works as expected, and without any issues.
Diagnostic Logs
No response

Thanks for reporting this @dckface.
Can you please follow the 'networking issues' section and share the script output ?


Copy CSS print query from link to minified CSS

For example, fullcalendar includes a separate CSS file for printers like this:
<link href="fullcalendar.print.css" rel="stylesheet" media="print">

The media="print" part currently gets lost, so CSS which is intended for printers only is applied on screen view.
The patch puts wraps such CSS with @media print {} so it only applies on printers.

Hi, thanks for the pull request. For approval you need to add unti test for this case.

Added test case and made it more general (apply to type=screen, etc. as well), thanks

Thanks.


Cannot update a multivalued custom schema

Describe the bug
When attempting to update a custom schema attribute i receive the error:
Update-GSUser : Exception calling "Execute" with "0" argument(s): "Google.Apis.Requests.RequestError
Invalid Input: custom_schema [400]
Errors [
Message[Invalid Input: custom_schema] Location[ - ] Reason[invalid] Domain[global]
]
"
To Reproduce
Steps to reproduce the behavior:
Have tried to follow the documentation here to create a custom schema multiple ways.

Attempts return the same error.
Expected behavior
Its possible I simply don't understand the proper way to update this particular value but i have been able to update other values just fine. If the documentation showed a picture of the custom schema it was updating it could be helpful at figuring out the proper way to format the hashtable for the user reading the doc.
Environment (please complete the following information):

OS:  Windows 10 1809
PowerShell Version:  PowerShell 5.1
PSGSuite Version:  2.36.4

Additional context
Thanks in advance!

I have a similar issue, I am trying the same format of commands as @hematic with the same results. My Powershell is a little rusty so it could be my understanding.


get_quadratic_approximation_of_cubic should also use bezier and classic_bezier should be removed

The implementation of get_quadratic_approximation_of_cubic caused some headache: when I tried to replace the current implementation of bezier, a test using get_quadratic_approximation_of_cubic started to fail because the points  used in that function are not just 1d-numpy arrays as usual, but instead 2d ones. If someone wants to take a stab at fixing this, please go ahead -- then this classic_bezier function could also just be removed.
Originally posted by @behackl in https://github.com/ManimCommunity/manim/pull/2421#discussion_r777780913

PR #3829 had the side effect of removing calls to bezier. Thus, in the future, if someone wants to continue with PR #2421, they should now be able to rewrite the bezier function without having to move the old code into classic_bezier.
Closing this issue.


A native Windows option?

Installing Docker on Windows is exhausting! You may even need to change BIOS settings to enable hardware assisted virtualization. (I just helped a user get through this this morning.) Reboot. Then you have to install WSL. You have to choose a Linux distribution! I would never go through this for a program.
There's Java for Windows. We could build the Go code for Windows. I suppose building NetworKit would take some effort. For Python support we could leave it up to the user. If they install Python, they will have Python. If they install PyTorch, they will have PyTorch. call_spark_submit.sh would have to be ported somehow. (We can check how Spark works on Windows. Or we rewrite it in Go.)
Instead of downloading many gigabytes and rebooting several times, they could just download a few 100 MB and run it like a normal application.
All this is only important if we have enough potential Windows users. If you are a potential Windows user, please :+1: this issue! Thanks!

The situation is a bit better now. We now use Conda for installing all dependencies. Perhaps that would work on Windows? And we run with normal spark-submit, which may also work on Windows. Sphynx can be disabled through KITE_DOMAINS. Any feedback on this from Windows users would be appreciated.


No Link Inserted to contact the support Team

Hi!
I'm an outreachy Applicant.
In the OLS application guidelines, I noticed in the paragraph where applicants were asked to contact the support team if any help is needed. I think a link should be inserted in the "OLS team" for easy accessibility so applicants do not have to go looking for how to reach the team.
Thank you

I can fix the issue

I assigned this issue to you @Chimatara

Thank you.

Hello @bebatut I have fixed the issue, here is a link to the PR Chimatara:My-Changes

Hello @bebatut
I have fixed the issues and made a pull request, here is a link to review the changes made.
https://github.com/open-life-science/application-forms/pull/6


Remove inference mode check in getNarrowableTypeForrReference

Fixes #54405
After some digging, it seems the problem is we call getNarrowableTypeForReference on the return type of the anonymous function while inferring the generic parameter of the call to bug.  This call has the CheckMode.Inferential flag set which means the substituteConstraints check returns false and the return type is just T[keyof T] which the flow checker can't narrow. This result is cached as the resolved return type function and is used when attempting to check whether the type of the function matches the first parameter of bug.  Since we've already calculated the return type to be T[keyof T] which is string | number, the assignment fails.  Allowing for type narrowing in inference mode means we get back string | number as the narrowed type which the flow checker can then narrow to number.
This did end up changing slightly one of the error messages in the output for controlFlowGenericTypes .  Originally, it mentioned Box<T> but returns Box<unkown> now since we are resolving the generic type to the constraint rather than using T directly.  Since this behavior seems to be consistent with other similar failure modes (see the g3 and g4 functions in the test), I believe this behavior change is OK.

Hmm, I'm pretty sure the CheckMode.Inferential check is there for a reason, though it is odd the test suite doesn't seem to reveal it.

@typescript-bot test this
@typescript-bot user test this inline
@typescript-bot run dt
@typescript-bot perf test faster
@typescript-bot test top100

There's one change in the Definitely Typed suite. A test in the ramda library contains code similar to the following:
declare function foo<F extends (...args: readonly any[]) => any>(f: F): F;

// Type before PR: <T extends string | number>(x: T) => T
// Type after PR:  <T extends string | number>(x: T) => string | number
const fx = foo(<T extends string | number>(x: T) => x);

We definitely don't want this new behavior.

I suspect the proper solution here could be to only apply the !Inferential condition when the reference is a generic type. (In the repro case, the return value is number and the generic type is unused. In the failing ramda case, the return value is a generic type.)
It looks like hasContextualTypeWithNoGenericTypes already does the generic check, so perhaps just moving the CheckMode.Inferential condition would do it:
const substituteConstraints = someType(type, isGenericTypeWithUnionConstraint) &&
            ((isConstraintPosition(type, reference) && !(checkMode && checkMode & CheckMode.Inferential)) ||
              hasContextualTypeWithNoGenericTypes(reference, checkMode));

Thank you Russel for the pointer as that seems to have resolved the issue.  I also added the rambda example that broke to the test cases to make it easier to detect similar regressions in the future.

@typescript-bot test this
@typescript-bot user test this inline
@typescript-bot run dt
@typescript-bot perf test faster
@typescript-bot test top100

Quick link to the above failure: https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/ramda/test/tryCatch-tests.ts#L75-L76


Added support for Swift Package Manger

Hi Florian! Thank you for this work, we just merged it to the master version.


Plugin should format json files it updates

When adding a function or running sync generator, the plugin modifies project.json and firebase.json files, but does not format them. They should be formatted.

This seems to be ok now.


Detailed schedule from last workshop

Let's place it somewhere close to guides so that we won't forget.
Day 6

8:50 - 9:00 Getting started
9:00 - 10:45 Software testing

9:00-9:05 Short info about today's exercise sessions and possible questions from yesterday
9:05-9:10 Motivation
9:10-9:20 Concepts
9:20-9:45 Testing locally

5 minutes talking
15 minute exercises
5 going over exercises and discussion

9:45-9:55 Break
9:55-10:20 Automated testing

type-along session

10:20-10:45 Test design

discussion: 5 minutes
Exercises: 10 minutes.  Any of exercises Design-1 to Design-8 that learners want to do.
discussion and type-along of advanced exercises: 10 minutes

10:45-11:00 Break

11:00 - 12:15 Modular code development

break around 11:40, at a good breakpoint
all as demo on stream, participating via document
no exercise groups

12:15 - 12:30 Summary and where to go from here

Re-opening because we need a new detailed schedule also.


Wrong dependency python-ffmpeg. Should be: ffmpeg-python

Otherwise, an attempt to run gpmf.io.extract_gpmf_stream("GX010028.MP4") will result in the following error:
~/.pyvenv/py38/lib/python3.9/site-packages/gpmf/io.py in find_gpmf_stream(fname)
     23         RuntimeError: If no stream found.
     24         """
---> 25         probe = ffmpeg.probe(fname)
     26
     27         for s in probe["streams"]:

AttributeError: module 'ffmpeg' has no attribute 'probe'

Nice project by the way. I like it a lot!

I found this too. I uninstalled python-ffmpeg, and installed ffmpeg-python and don't hit the "no attribute 'probe'" error.

I found this too. I uninstalled python-ffmpeg, and installed ffmpeg-python and don't hit the "no attribute 'probe'" error.

Yup fixed it for me too!


Prepare README.md file

Hi @andreasbalsiger I created this pull request for the documentation.
Could you please have a look on this README.md file and the logo for this utils? It describes the key features, set up step of advanced process analyzer.
Thank you so much.


Call receipt is missing from field

Call receipts are not currently compliant with the ABI specs, specifically the from and to fields are not being used correctly which is preventing SDK estimation from working.
Current impl:
pub enum Receipt {
    Call {
        id: ContractId,
        to: ContractId,
        amount: Word,
        asset_id: AssetId,
        gas: Word,
        param1: Word,
        param2: Word,
        pc: Word,
        is: Word,
    },

Specs:
https://github.com/FuelLabs/fuel-specs/blob/master/specs/protocol/abi.md#call-receipt
{
  "type":"Call",
  "from":"0x39150017c9e38e5e280432d546fae345d6ce6d8fe4710162c2e3a95a6faff051",
  "to":"0x1c98ff5d121a6d5afc8135821acb3983e460ef0590919266d620bfc7b9b6f24d",
  "amount":"10000",
  "asset_id":"0xa5149ac6064222922eaa226526b0d853e7871e28c368f6afbcfd60a6ef8d6e61",
  "gas":"500",
  "param1":"0x28f5c28f5c28f5c",
  "param2":"0x68db8bac710cb",
  "pc":"0xffffffffffffffff",
  "is":"0xfffffffffffffffe"
}

blocks: https://github.com/FuelLabs/fuels-rs/issues/595

actually, it looks like we are using call receipt mostly correctly, we just treat from as id since id has the same behavior in most other receipts.


Finish migration to AssertJ

The PR is intended to make use assertj wherever possible

It seems to also happen on Linux:
https://github.com/codecov/codecov-action/issues/586
Maybe we should revert to version 1?

On 22 Apr 2022, at 17:43, Sergey Nuyanzin @.***> wrote:

Hi @bodiam
do you have an idea why codecov fails on windows like that
https://github.com/datafaker-net/datafaker/runs/6126356932?check_suite_focus=true#step:5:12
may be leave codecov only on one platform, e.g. linux?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.

Looks it was a temporary issue, now it starts working again....
Let's keep an eye to see how stable it will behave


Inheritance problem

see https://scrutinizer-ci.com/g/victormech/ditesto/inspections/c626e9de-9283-43cf-800f-b94af4111a85/issues/files/src/TextFileWriter.php?status=new&orderField=path&order=asc&honorSelectedPaths=0#inspectioncomment-17886395

Fixed


Resolving checkstyle issues

Build finished.

Build finished.

Build finished.

Build finished.

Build finished.

Build finished.

Build finished.

Build finished.

Build finished.

retest this please

Build finished.

Build finished.

retest this please

Build finished.

retest this please

retest this please

Build finished.

Build finished.


Fix thumbsticks for 'flat' overlays

Issue https://github.com/libretro/common-overlays/issues/72

Made thumbsticks same as on image below. Outer black circle is actual hitbox. Touch outside inner black circle cause 100% tilt. Set range_mod to 2 as button hitbox become bigger.

.


Rename sqlitebrowser to db-browser-for-sqlite

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

>>> No casks modified, skipping
Not sure why Travis is skipping the Cask.


"Measurements for single-qubit systems" kata content feedback

This issue aggregates feedback related to the content of the "Measurements for single-qubit systems" kata.
Feedback includes, but is not limited to, any of the following:

Correctness (e.g. solutions are checked correctly, math is right, examples compile and run).
Clarity of content (e.g. descriptions for exercises, explanations of solutions).
Organization of content (e.g. ordering of sections, length of sections, titles).
Formatting (e.g. consistency of formatting, unaligned content).
Typos.

Please add a comment with your feedback, preferably as TODO items or bullet points.

[ ] Rename kata to "Measurements on single-qubit systems".
[ ] Use "kata" instead of "tutorial" consistently.

PR for suggested changes: #553

The biggest issue I see is the LaTex spacing isn't right. Here is what the answer to the question under the Arbitrary basis measurements implementation section looks like:

Other feedback:

Formatting under (Lesson: Measurements in arbitrary orthogonal bases) seems broken with the bulleted list breaking out of the Note syntax that I think it is supposed to be in.
Reference to an unknown "problem 6" in the solution section of the Measurement in the |A〉, |B〉 basis exercise.
I don't believe punctuation should be included when equations are not in-line, i.e. putting a period at the end of an equation.

Places where I noticed the LaTex syntax spacing was off:

The question section under Lesson: Computational Basis Measurements
Under Measurements as projection operations
Under Arbitrary basis measurements implementation
The answer section for the second question under Arbitrary basis measurements implementation
The solutions to the last 3 exercises

Lesson: Computational Basis Measurements
where $\alpha$ and $\beta$ are complex numbers, and the state is normalized, $|\alpha|^2 + |\beta|^2 = 1$. (avoid “i.e.”)
To get some information about the qubit state, we can measure the qubit. Similar to the classical case of measuring a bit, the outcome of a measurement can be 0 or 1. However, unlike the classical case, quantum measurement is a probabilistic process.

Lesson: Measurements in the Pauli Bases
So far, we have discussed measurements done in the computational basis, that is, the {|0⟩,|1⟩} basis. (avoid “i.e.”)

Lesson: Measurements in Arbitrary Orthogonal Bases
Measurements as Projection Operations
As well as qubits are represented by vectors and quantum gates are represented by matrices, quantum measurements are represented by orthogonal projection operators.
As the name implies, orthogonal projection operators project the state of the qubit onto an orthogonal subspace. Using the ket-bra representation, one can represent a projection matrix in the Dirac notation.

Lesson: Conclusion
Congratulations!  In this Katas you learned how to apply measurements on single-qubit systems. Here are a few key concepts to keep in mind:

Measurements are always done in an orthogonal basis. By default, we choose the computational basis $\lbrace \ket{0}, \ket{1} \rbrace$.
Measurements are represented as projector operators, which are matrices.
Unlike quantum gates, measurements are neither unitary nor reversible. When we measure a qubit, the state of the qubit collapses to one of the basis states, and the initial state is lost.
In Q#, you can implement measurements in the computational basis using the M operation, and in the Pauli basis using the Measure operation.

Next, you will learn about measurements in multi-qubit systems in the "Measurements in Multi-Qubit Systems" Kata.


During normal autosummary use (not relevant to fixtures), sphinx_autofixture crashes when a dataclass is present

Description
When applying autosummary to a dataclass, sphinx_autofixture crashes.
Steps to Reproduce

Download bug.tar.gz.
Run pip install sphinx-autofixture.
Run PYTHONPATH=. sphinx-build -v -d "./_build" docs "_build/html" -b html -W --color

bug.tar.gz:
├── docs
│   ├── conf.py
│   └── index.rst
└── myproject.py

index.rst:
Welcome to myproject's documentation!
=====================================

.. currentmodule:: myproject

.. autosummary::
   :toctree:

   A

conf.py:
project = 'myproject'
copyright = '2020, someone'
author = 'someone'
extensions = [
    'sphinx.ext.autosummary',
    'sphinx_autofixture'
]
html_theme = 'alabaster'

autosummary_generate = True

myproject.py:
from dataclasses import dataclass

@dataclass(frozen=True)
class A:
    "A class."

Actual result:
...
[app] connecting event 'config-inited' (500): <function validate_config at 0x7fe2f6934400> [id=62]
making output directory... done
[app] emitting event: 'config-inited'(<sphinx.config.Config object at 0x7fe2f72be7f0>,)
[app] emitting event: 'builder-inited'()
[autosummary] generating autosummary for: index.rst

Traceback (most recent call last):
  File "/home/hong/tmp/.venv/lib/python3.7/site-packages/sphinx/events.py", line 110, in emit
    results.append(listener.handler(self.app, *args))
  File "/home/hong/tmp/.venv/lib/python3.7/site-packages/sphinx/ext/autosummary/__init__.py", line 806, in process_generate_options
    encoding=app.config.source_encoding)
  File "/home/hong/tmp/.venv/lib/python3.7/site-packages/sphinx/ext/autosummary/generate.py", line 430, in generate_autosummary_docs
    modname, qualname)
  File "/home/hong/tmp/.venv/lib/python3.7/site-packages/sphinx/ext/autosummary/generate.py", line 320, in generate_autosummary_content
    get_members(obj, {'method'}, ['__init__'])
  File "/home/hong/tmp/.venv/lib/python3.7/site-packages/sphinx/ext/autosummary/generate.py", line 257, in get_members
    documenter = get_documenter(app, value, obj)
  File "/home/hong/tmp/.venv/lib/python3.7/site-packages/sphinx/ext/autosummary/__init__.py", line 210, in get_documenter
    classes = [cls for cls in app.registry.documenters.values()
  File "/home/hong/tmp/.venv/lib/python3.7/site-packages/sphinx/ext/autosummary/__init__.py", line 211, in <listcomp>
    if cls.can_document_member(obj, '', False, parent_doc)]
  File "/home/hong/tmp/.venv/lib/python3.7/site-packages/sphinx_autofixture/__init__.py", line 152, in can_document_member
    return is_fixture(member)[0]
  File "/home/hong/tmp/.venv/lib/python3.7/site-packages/sphinx_autofixture/__init__.py", line 109, in is_fixture
    visitor.visit(ast.parse(inspect.getsource(function)))
  File "/usr/lib/python3.7/inspect.py", line 973, in getsource
    lines, lnum = getsourcelines(object)
  File "/usr/lib/python3.7/inspect.py", line 955, in getsourcelines
    lines, lnum = findsource(object)
  File "/usr/lib/python3.7/inspect.py", line 786, in findsource
    raise OSError('could not get source code')
OSError: could not get source code

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/hong/tmp/.venv/lib/python3.7/site-packages/sphinx/cmd/build.py", line 279, in build_main
    args.tags, args.verbosity, args.jobs, args.keep_going)
  File "/home/hong/tmp/.venv/lib/python3.7/site-packages/sphinx/application.py", line 278, in __init__
    self._init_builder()
  File "/home/hong/tmp/.venv/lib/python3.7/site-packages/sphinx/application.py", line 337, in _init_builder
    self.events.emit('builder-inited')
  File "/home/hong/tmp/.venv/lib/python3.7/site-packages/sphinx/events.py", line 118, in emit
    (listener.handler, name), exc) from exc
sphinx.errors.ExtensionError: Handler <function process_generate_options at 0x7fe2f699b840> for event 'builder-inited' threw an exception (exception: could not get source code)

Extension error:
Handler <function process_generate_options at 0x7fe2f699b840> for event 'builder-inited' threw an exception (exception: could not get source code)

Removing sphinx_autofixture from the list of extensions stops the crash.
Expected result:
No crash.
Version

Operating System: Debian 10
Python: 3.7.3
sphinx-autofixture: 0.2.2

Installation source
PyPI

Hi @xuhdev,
Apologies for not looking at this sooner. I have found the issue - the way dataclasses generate their code means that inspect.getsource can't find it, causing the crash.
I believe I have now fixed it. Can you try the issue-6 branch, which you can install with:
python3 -m pip install git+https://github.com/sphinx-toolbox/sphinx-autofixture/@issue-6 --force-reinstall --no-deps

If you're using a recent version of pip you'll need the  --force-reinstall --no-deps flags.
Let my know if that fixes it for you, and if it does I will release the fix to PyPI.

Hi @xuhdev,
Apologies for not looking at this sooner. I have found the issue - the way dataclasses generate their code means that inspect.getsource can't find it, causing the crash.
I believe I have now fixed it. Can you try the issue-6 branch, which you can install with:
python3 -m pip install git+https://github.com/sphinx-toolbox/sphinx-autofixture/@issue-6 --force-reinstall --no-deps

If you're using a recent version of pip you'll need the  --force-reinstall --no-deps flags.
Let my know if that fixes it for you, and if it does I will release the fix to PyPI.

Thanks for the fix! It works now.

Thanks for the fix! It works now.

Wonderful. I will publish a new release to PyPI

Wonderful. I will publish a new release to PyPI


Add object and feature Influxdb2Writer

Ref #83 feature Influxdb2 was added. Thanks for the PR @afeefghannam89


Double to Int conversion fails with error

Version
0e2d31cbf718cc31bb2f80a65760439ecc3ee7fc
Environment
macOS 10.12.1, XCode 8.2.1, Swift 3
Description
When calling Int64.randomInRange (and Int on 64 bit) with a range of (Int64.max, Int64.max) I get an error. The conversion Int64(Double(UInt64.max)) in Random.swift fails, because Double(Int64.max) > Int64.max
(Same for UInt64 (and UInt on 64 bit))
Steps To Reproduce
Just run Int64.randomInRange((Int64.max, Int64.max), gen: StdGen(1))
Expected Result
Should return Int64.max
Actual Result
fatal error: Double value cannot be converted to Int64 because the result would be greater than Int64.max
Additional information

I knew this could come back to bite me at some point.
I'm at a loss here.  There is a range of 512 unconvertible-yet-representable Int64 values subject to this crash because of the preconditions in the initializer getting tripped here.

Resolved by the merge of #208.  Please point your package manager at master until I put out a new point release.


Specify custom table name in one to one relation

I have 2 tables, each one of them containing a reference to the other one (with a one-to-one relationship):
type Engine struct {
    ID int64 `json:"id"`
    CarID int64 `json:"car_id"`
    .....
}

type Car struct {
    ID int64 `json:"id"`
    EngineID Engine `json:"engine_id"`
    .....
}

In my PostgreSQL database, I have the following tables and fields:
map_engine (table name)
id, car_id

map_car (table name)
id, engine_id

However, when I want to retrieve a list of cars with their engines, gorm tries to look in the engines table, and not in the map_engine table.
I am currently doing this:
db.Table("map_car").Preload(clause.Associations).Where("id > 1950").Order("id desc").Find(&cars)
How can I specify the table name for the second model?

@adrien3d  You can set the table name as:
type Engine struct {
	ID    int64 `json:"id"`
	CarID int64 `json:"car_id"`
}

func (Engine) TableName() string {
	return "map_engine "
}

type Car struct {
	ID       int64  `json:"id"`
	EngineID Engine `json:"engine_id"`
}

func (Car) TableName() string {
	return "map_car"
}

So your query would be:
db.Preload(clause.Associations).Where("id > 1950").Order("id desc").Find(&cars)

// With debug to see the SQL script in the console
db.Debug().Preload(clause.Associations).Where("id > 1950").Order("id desc").Find(&cars)

More information in the link: https://stackoverflow.com/questions/57645143/golang-orm-name-of-table

Thank you very much @luisgomez29 works like a charm!


Log message in response

Yuo just want it on success?

Seems to me that the message is added to exception on failures, so that will just log it twice?

Sure, I didn't check that :)


Hapi: export hapiRequestInfoExtractor

(this is a feature request so I don't think the regular questions would help)
We log error is hapi sometimes with an error tag
request.log(['user', 'create', 'error'], new Error('failed creating user'))
To capture this now I do
const HapiRequestExtractor = require('@google-cloud/error-reporting/build/src/request-extractors/hapi.js');

server.on('request', (request, event, tags) => {

    if (tags.error) {
        const requestInfo = HapiRequestExtractor.hapiRequestInformationExtractor(request);
        requestInfo.url = request.path; // see https://github.com/googleapis/nodejs-error-reporting/issues/196
        ErrorReporter.report(event.data || event.error, requestInfo);
    }
});

While I don't mind setting up custom logging it would be nice to not have to hack in the hapiRequestInformationExtractor
Another solution would be to support this use case out of the box.
Whichever you like I can do a PR for any/both.

Thanks for opening this issue.  Just do double check, you are using Hapi 17 right?  Also, if issue #196 is resolved, the suggestion of this issue is to use event.data || event.error instead of just event.error (which is what the plugin currently uses).  This is correct?  Thanks

I'm using hapi 16, sorry for not mentioning that 😅
The suggestion is to log logs logged with the error tag to stackdriver error reporting.
#196 will just make this logging more correct.
Atm doing request.log(['user', 'create', 'error'], new Error('failed creating user')) in hapi 16 does not log it to stackdriver afaik.

@AdriVanHoudt is this still needed now that #196 is fixed? I'm not a hapi user, so I don't know – without researching – how hapi error tags work.

With #196 fixed, I'm going to close this for now.  If this issue is not resolved via the fix for #196 please let us know.


Add back explicit -pthread flags when available

It turns out that we do actually need the -pthread flag when using the Cray compiler, so I'm adding it back here for both compilation and linking (#5420 is responsible for the timeouts on the clang-cuda configuration and I missed this before merging). The flag also now gets passed on to consuming projects unlike before #5420.
@kordejong I know you may be tired of rebuilding HPX, but if you have the time I'd be very grateful if you could also test this on your system to ensure that I haven't brought things back to before #5420...

This will be the last regular PR (I'm not counting #5417) for 1.7.0 unless there's a really critical regression or bug that still pops up.

@kordejong I know you may be tired of rebuilding HPX, but if you have the time I'd be very grateful if you could also test this on your system to ensure that I haven't brought things back to before #5420...

@msimberg No problem. My builds succeeded. Your updates seem fine.

retest cscs


Pin message in supergroups

Forgive me if it's something that I need to learn from telegram api myself, but I wonder how can I pin a message in supergroups using this method:
https://core.telegram.org/bots/api#pinchatmessage
How can I get id of my chat to pin it?
And further just pin it if it's a problem and when it gets resolved unpin message using this method:
https://core.telegram.org/bots/api#unpinchatmessage
Of course I have administrator rights in the group.

@aminvakil you need to store somewhere the information about pinned messages to unpin it.
It's not possible right now.

@ableev  for use  pinchatmessage need save message_id.
I think it posebly. Maybe over save tag (or flag) in zbx_tg_tmp_dir.
zbxtg;tag_act
zbxtg;save_mesg
and next step in action
zbxtg;tag_act
zbxtg;pin_mesg
Tag tag_act should be unique for action.


Adding insecure flag to CONFIG_PARAM_TYPE in conf.py

Hello Maintainer
This is my first ever PR fixing https://github.com/ansible/tower-cli/issues/710
Thank you very much for your valuable work! I would be honored if this small fix makes it into 3.3.5.
Best regards,
Wainaxman

sorry to have bothered you - i will attempt to fix this before re-submitting it again. it's a steep learning curve but i am motivated to get this through. thank you very much for all you work - see you later.

Coverage remained the same at 64.318% when pulling 68170b6669fd1e7a5650e8cc433c831833896647 on wainaxman:master into a2b151fed93c47725018d3034848cb3a1814bed7 on ansible:master.

Coverage remained the same at 64.318% when pulling 68170b6669fd1e7a5650e8cc433c831833896647 on wainaxman:master into a2b151fed93c47725018d3034848cb3a1814bed7 on ansible:master.


Failed sign out on brave browser

Hi,  first I'm really thank you for making this full example
it's really helpful to understand phoenix live view .
I have a question  the sign out doesn't work for brave browser with error:
This page isn’t workingIf the problem continues, contact the site owner.
HTTP ERROR 431
I've tried in chrome and firefox browser and it works, is there any additional settings  I should add for brave browser case ?
Thank you

Works just fine for me, 431 is 431 Request Header Fields Too Large, which is weird because the only thing we store in the cookie session is the user ID, so perhaps it's something on your side. Let me know if you can provide more information. Thanks!

Thanks , and yes the problem is my brave browser has many cookies for http://localhost:4000 site,
it works after I cleaned up the cookies
Thank you very much


bionic: use fetchzip for everything

Since the hashes of the remaining two archives that used fetchurl broke,
now as good a time as any to switch the remaining fetchurls to fetchzip.

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Doesn't build unfortunately.

/rebase master

The bionic-prebuilt dir thing is new in staging.

I saw this was build by ofborg previously, but for some reason the download doesn't work for me:
# cat test.nix
with import <nixpkgs> { };
[
  (
    fetchzip {
      url = "https://android.googlesource.com/kernel/common/+archive/48ffcbf0b9e7f0280bfb8c32c68da0aaf0fdfef6.tar.gz";
      sha256 = "1y7cmlmcr5vdqydd9n785s139yc4aylc3zhqa59xsylmkaf5habk";
      stripRoot = false;
    }
  )
  (
    fetchzip {
      url = "https://android.googlesource.com/platform/bionic/+archive/00e8ce1142d8823b0d2fc8a98b40119b0f1f02cd.tar.gz";
      sha256 = "10z5mp4w0acvjvgxv7wlqa7m70hcyarmjdlfxbd9rwzf4mrsr8d1";
      stripRoot = false;
    }
  )
]
# nix build -f test.nix -L
source> trying https://android.googlesource.com/platform/bionic/+archive/00e8ce1142d8823b0d2fc8a98b40119b0f1f02cd.tar.gz
source>   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
source>                                  Dload  Upload   Total   Spent    Left  Speed
source> 100 6018k    0 6018k    0     0  2509k      0 --:--:--  0:00:02 --:--:-- 2509k
source> unpacking source archive /private/tmp/nix-build-source.drv-0/00e8ce1142d8823b0d2fc8a98b40119b0f1f02cd.tar.gz
error: --- Error --------------------------------------------------------------------------------------------------------------------------- nix
hash mismatch in fixed-output derivation '/nix/store/ka54372nq9qjlz2qa78rlc9qcvfzr926-source.drv':
  specified: sha256-oaGscyXu85za6o42WbPyDIJTj8KUn93flpspwMmt5YM=
     got:    sha256-x17xkM9TfbJdFyUT5E3lpDpumSiJCu+oe2bimm9A1KU=
source> trying https://android.googlesource.com/kernel/common/+archive/48ffcbf0b9e7f0280bfb8c32c68da0aaf0fdfef6.tar.gz
source>   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
source>                                  Dload  Upload   Total   Spent    Left  Speed
source> 100  166M    0  166M    0     0  2471k      0 --:--:--  0:01:09 --:--:-- 2538k
source> unpacking source archive /private/tmp/nix-build-source.drv-0/48ffcbf0b9e7f0280bfb8c32c68da0aaf0fdfef6.tar.gz
warning: --- Large path -------------------------------------------------------------------------------------------------------------------- nix
dumping very large path (> 256 MiB); this may run out of memory
error: --- Error --------------------------------------------------------------------------------------------------------------------------- nix
hash mismatch in fixed-output derivation '/nix/store/m56dqkiv0lfxcd8n4y07qww8b9fkb0ss-source.drv':
  specified: sha256-cylYnJqVet1TURj+wahXhPk0gi7o2NSax22XzCqt7Pg=
     got:    sha256-fY1PDi494RES+shh25KvyJ/yD8V70kQsF+zRh4MtD3k=
# nix hash to-base32 sha256-oaGscyXu85za6o42WbPyDIJTj8KUn93flpspwMmt5YM=
10z5mp4w0acvjvgxv7wlqa7m70hcyarmjdlfxbd9rwzf4mrsr8d1
# nix hash to-base32 sha256-cylYnJqVet1TURj+wahXhPk0gi7o2NSax22XzCqt7Pg=
1y7cmlmcr5vdqydd9n785s139yc4aylc3zhqa59xsylmkaf5habk

Interesting, so maybe not only the archive hash is unstable, but its contents as well?

Interesting, so maybe not only the archive hash is unstable, but its contents as well?

If you want to look into this:
cachix use pr123010
nix-store -r /nix/store/26axwvyslbxd4jvx7x4iyn1p2rm5q6gq-source
nix-store -r /nix/store/fcydcc3fzpvpi65l3b00ilqfxwkcy4h5-source

I think this might be because of the case-insensitive filesystem

I can reproduce the hashes of your test.nix.
nix-build test.nix --check
checking outputs of '/nix/store/5b89ra6sl2wih65sbdwakwp8xx0bx989-source.drv'...
checking outputs of '/nix/store/vayl3g3ri1b07pc1jixm2vpjwj84didn-source.drv'...

trying https://android.googlesource.com/platform/bionic/+archive/00e8ce1142d8823b0d2fc8a98b40119b0f1f02cd.tar.gz

trying https://android.googlesource.com/kernel/common/+archive/48ffcbf0b9e7f0280bfb8c32c68da0aaf0fdfef6.tar.gz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 6018k    0 6018k    0     0  2382k      0 --:--:--  0:00:02 --:--:-- 2382k
unpacking source archive /build/00e8ce1142d8823b0d2fc8a98b40119b0f1f02cd.tar.gz
100  166M    0  166M    0     0  3269k      0 --:--:--  0:00:52 --:--:-- 3435k
unpacking source archive /build/48ffcbf0b9e7f0280bfb8c32c68da0aaf0fdfef6.tar.gz
/nix/store/md870bmi589116igv8py89zw0nls98qk-source
/nix/store/pq5jz0zr6dvhq9c14nwn0mpjy32b38vk-source

Not sure what you are getting at with the binary cache, of course I can successfully download already built fixed output derivations…

Seems like there is indeed a case collision
# ls /nix/store/pq5jz0zr6dvhq9c14nwn0mpjy32b38vk-source/libc/versioner-dependencies/common/kernel_uapi/linux/netfilter/xt_[cC][oO][nN][nN][mM][aA][rR][kK]*
/nix/store/pq5jz0zr6dvhq9c14nwn0mpjy32b38vk-source/libc/versioner-dependencies/common/kernel_uapi/linux/netfilter/xt_CONNMARK.h
/nix/store/pq5jz0zr6dvhq9c14nwn0mpjy32b38vk-source/libc/versioner-dependencies/common/kernel_uapi/linux/netfilter/xt_connmark.h~nix~case~hack~1
# ls /nix/store/26axwvyslbxd4jvx7x4iyn1p2rm5q6gq-source/libc/versioner-dependencies/common/kernel_uapi/linux/netfilter/xt_[cC][oO][nN][nN][mM][aA][rR][kK]*
/nix/store/26axwvyslbxd4jvx7x4iyn1p2rm5q6gq-source/libc/versioner-dependencies/common/kernel_uapi/linux/netfilter/xt_connmark.h

The ~nix~case~hack~ comes from https://github.com/NixOS/nix/blob/7c90552879da4d1df99b50c85e94201981e60123/src/libutil/archive.cc#L259


GuestAgent failed with log "[WARN]  Error state triggered for caller:GAPluginPinger"

OS 2012 R2 windows server
agent no ready
extension:
IaaSAntimalware
MicrosoftMonitoringAgent
"GAPlugin" can not be searched in any document. Guestagent is not ready so I'm thinking whether reinstall guest agent can solve this problem.
The following warn log is repeating in the whole log.
WaAppAgent.log:
[00000013] [11/11/2022 06:34:12.06] [INFO]  WriteGAPluginHeartbeat: HostGAPluginServiceClient is not initialized so setting isCurrentlyHealthy as false
[00000013] [11/11/2022 06:34:12.06] [WARN]  Reached Maximim error count:1000 so not incrementing the count anymore
[00000013] [11/11/2022 06:34:12.06] [WARN]  Error state triggered for caller:GAPluginPinger
[00000086] [11/11/2022 06:39:12.14] [INFO]  WriteGAPluginHeartbeat: HostGAPluginServiceClient is not initialized so setting isCurrentlyHealthy as false
[00000086] [11/11/2022 06:39:12.14] [WARN]  Reached Maximim error count:1000 so not incrementing the count anymore
[00000086] [11/11/2022 06:39:12.14] [WARN]  Error state triggered for caller:GAPluginPinger
[00000005] [11/11/2022 06:44:12.23] [INFO]  WriteGAPluginHeartbeat: HostGAPluginServiceClient is not initialized so setting isCurrentlyHealthy as false
[00000005] [11/11/2022 06:44:12.23] [WARN]  Reached Maximim error count:1000 so not incrementing the count anymore
[00000005] [11/11/2022 06:44:12.23] [WARN]  Error state triggered for caller:GAPluginPinger
[00000023] [11/11/2022 06:49:12.32] [INFO]  WriteGAPluginHeartbeat: HostGAPluginServiceClient is not initialized so setting isCurrentlyHealthy as false
[00000023] [11/11/2022 06:49:12.32] [WARN]  Reached Maximim error count:1000 so not incrementing the count anymore
[00000023] [11/11/2022 06:49:12.32] [WARN]  Error state triggered for caller:GAPluginPinger
TransparentInstaller:
[00000018] [11/11/2022 05:44:01.57] [INFO]  Generated the temp VMAgent logs file 'C:\WindowsAzure\CollectGuestLogsTemp\0d99db5c-6731-4f7c-a007-9f4d35bffa77.zip' with file size 172693 KB.
[00000018] [11/11/2022 05:44:01.57] [WARN]  The log file size '176838125' exceeds the max file size limit '104857600' for upload, not uploading the file.
[00000018] [11/11/2022 05:44:01.57] [WARN]  The log file size exceed the max file size limit to keep it in local disk, remove it.
[00000018] [11/11/2022 05:44:02.14] [INFO]  Deleted the temp GuestLogs folder 'C:\WindowsAzure\CollectGuestLogsTemp'.
[00000018] [11/11/2022 05:44:02.14] [WARN]  Failed to collect the VMAgent logs file.
[00000017] [11/11/2022 06:04:03.51] [TRACE] Going to check for new NetAgent Target version.
[00000017] [11/11/2022 06:04:03.51] [INFO]  NetAgent going to get its target version from wireserver.
[00000017] [11/11/2022 06:04:03.51] [INFO]  NetAgent Retrieving target version from wireserver @ http://<IP_ADDRESS>/machine/plugins?comp=netagent&type=getpackageversion
[00000017] [11/11/2022 06:04:03.51] [INFO]  NetAgent Received VM Interfaces as: <IP_ADDRESS>
[00000017] [11/11/2022 06:04:03.52] [TRACE] NetAgent version received from Host is same as that in VM: <IP_ADDRESS>. Existing: <IP_ADDRESS>
[00000012] [11/11/2022 06:10:01.06] [ERROR] The collector Accounts failed. Exception: System.Collections.Generic.KeyNotFoundException: 指定されたキーはディレクトリ内に存在しませんでした。
場所 System.ThrowHelper.ThrowKeyNotFoundException()
場所 System.Collections.Generic.Dictionary`2.get_Item(TKey key)
場所 Microsoft.Azure.Internal.InVMHealth.HealthCollectors.AccountInfoCollector.Get()
場所 Microsoft.Azure.Internal.InVMHealth.HealthCollectors.HealthReportCollector.<>c__DisplayClass8.<.ctor>b__4(HealthReport x)
場所 Microsoft.Azure.Internal.InVMHealth.HealthCollectors.HealthReportCollector.CollectHealth()
[00000012] [11/11/2022 06:10:02.85] [ERROR] IsEmsEnabled() failed with Exception System.Runtime.InteropServices.COMException (0xD0000225)
場所 System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
場所 System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
場所 Microsoft.Azure.Internal.InVMHealth.HealthCollectors.BootEntryReader.GetBcdOSLoaderElement(UInt32 elementType)
場所 Microsoft.Azure.Internal.InVMHealth.HealthCollectors.BootEntryReader.IsEmsEnabled()
[00000012] [11/11/2022 06:10:02.85] [INFO]  VmHealthCollectorThread: Finalized Health Report:
======== Microsoft Azure VM Health Report - Start 2022-11-11T06:10:02.8506342Z ========
{"reportTime":"2022-11-11T06:09:58.5374291Z","networkAdapters":[{"name":"イーサネット 2","status":"Up","macAddress":"00-0D-3A-40-3E-36","ipProperties":[{"protocolVersion":4,"address":"<IP_ADDRESS>","isDhcpEnabled":true}]},{"name":"Loopback Pseudo-Interface 1","status":"Up","macAddress":"","ipProperties":[{"protocolVersion":4,"address":"<IP_ADDRESS>","isDhcpEnabled":false},{"protocolVersion":6,"address":"::1","isDhcpEnabled":false}]},{"name":"isatap.reddog.microsoft.com","status":"Down","macAddress":"00-00-00-00-00-00-00-E0","ipProperties":[{"protocolVersion":6,"address":"fe80::5efe:<IP_ADDRESS>%12","isDhcpEnabled":false}]}],"remoteAccess":{"windows":{"rdpPort":3389,"rdpEnabled":true,"rdpTcpListenerSecurityConfiguration":{"nlaUserAuthenticationRequired":true,"authenticationSecurityLayer":"Negotiate","protocolNegotiationAllowed":true},"rdpTcpListenerMaxConnections":2,"rdpFirewallAccess":"Allowed","rdpAllowedUsers":["ruadmin","Enterprise Admins","Domain Admins","aadsadmin","progadmin","sbtadmin"],"rdpCertificateDetails":{"subject":"CN=O365-ad-01.o365.ritsumei.ac.jp","thumbprint":"78280982D4E631ECDD3FA8B36661ADC06335ECC5","validFrom":"2022-10-22T03:22:20Z","validTo":"2023-04-23T03:22:20Z"},"rdsLicensingStatus":null}},"accounts":null,"services":[{"errorControl":"Normal","exitCode":0,"name":"TermService","processId":2848,"serviceType":"Share Process","startMode":"Manual","startName":"NT Authority\NetworkService","state":"Running","status":"OK"},{"errorControl":"Normal","exitCode":0,"name":"BFE","processId":1112,"serviceType":"Share Process","startMode":"Auto","startName":"NT AUTHORITY\LocalService","state":"Running","status":"OK"},{"errorControl":"Normal","exitCode":0,"name":"MpsSvc","processId":1112,"serviceType":"Share Process","startMode":"Auto","startName":"NT Authority\LocalService","state":"Running","status":"OK"},{"errorControl":"Normal","exitCode":0,"name":"WindowsAzureGuestAgent","processId":1892,"serviceType":"Own Process","startMode":"Auto","startName":"LocalSystem","state":"Running","status":"OK"},{"errorControl":"Normal","exitCode":0,"name":"WindowsAzureTelemetryService","processId":1328,"serviceType":"Own Process","startMode":"Auto","startName":"LocalSystem","state":"Running","status":"OK"},{"errorControl":"Normal","exitCode":0,"name":"RdAgent","processId":1804,"serviceType":"Own Process","startMode":"Auto","startName":"LocalSystem","state":"Running","status":"OK"},{"errorControl":"Normal","exitCode":0,"name":"nsi","processId":336,"serviceType":"Share Process","startMode":"Auto","startName":"NT Authority\LocalService","state":"Running","status":"OK"},{"errorControl":"Normal","exitCode":0,"name":"Dhcp","processId":952,"serviceType":"Share Process","startMode":"Auto","startName":"NT Authority\LocalService","state":"Running","status":"OK"},{"errorControl":"Normal","exitCode":0,"name":"Dnscache","processId":584,"serviceType":"Share Process","startMode":"Auto","startName":"NT AUTHORITY\NetworkService","state":"Running","status":"OK"},{"errorControl":"Normal","exitCode":0,"name":"LanmanWorkstation","processId":584,"serviceType":"Share Process","startMode":"Auto","startName":"NT AUTHORITY\NetworkService","state":"Running","status":"OK"},{"errorControl":"Normal","exitCode":0,"name":"Netlogon","processId":548,"serviceType":"Share Process","startMode":"Auto","startName":"LocalSystem","state":"Running","status":"OK"}],"systemInfo":{"windows":{"osVersion":"Microsoft Windows NT 6.2.9200.0","isOsEval":true,"realTimeIsUniversal":true,"domainRole":"PrimaryDomainController","emsEnabled":false,"safeBoot":-1,"featureSettingsOverride":-1,"featureSettingsOverrideMask":-1,"minVmVersionForCpuBasedMitigations":""}},"firewallPolicy":{"localPolicy":{"domainProfile":{"blockAllInboundConnections":-1,"enable":1},"publicProfile":{"blockAllInboundConnections":-1,"enable":1},"standardProfile":{"blockAllInboundConnections":-1,"enable":1}},"domainPolicy":{"domainProfile":{"blockAllInboundConnections":-1,"enable":-1},"publicProfile":{"blockAllInboundConnections":-1,"enable":-1}}}}
======== Microsoft Azure VM Health Report - End 2022-11-11T06:10:02.8506342Z =========
[00000012] [11/11/2022 06:10:02.85] [TRACE] VmHealthCollectorThread: Opening serial port
[00000012] [11/11/2022 06:10:02.85] [TRACE] VmHealthCollectorThread: Writing health report - START
[00000012] [11/11/2022 06:10:17.99] [TRACE] VmHealthCollectorThread: Writing health report - END
[00000012] [11/11/2022 06:10:17.99] [TRACE] VmHealthCollectorThread: Closing serial port
WaAppAgent.exe Information: 0 : Versions supported by the HostGAPlugin are 2015-09-01
[00000018] [11/11/2022 06:44:02.17] [INFO]  Created the temp GuestLogs folder 'C:\WindowsAzure\CollectGuestLogsTemp'.
[00000018] [11/11/2022 06:44:02.17] [INFO]  Start VMAgent log collector CollectGuestLogs.exe with arguments: -Mode:ga -FileName:C:\WindowsAzure\CollectGuestLogsTemp\0d99db5c-6731-4f7c-a007-9f4d35bffa77.zip.
[00000017] [11/11/2022 07:04:03.83] [TRACE] Going to check for new NetAgent Target version.
[00000017] [11/11/2022 07:04:03.83] [INFO]  NetAgent going to get its target version from wireserver.
[00000017] [11/11/2022 07:04:03.83] [INFO]  NetAgent Retrieving target version from wireserver @ http://<IP_ADDRESS>/machine/plugins?comp=netagent&type=getpackageversion
[00000017] [11/11/2022 07:04:03.83] [INFO]  NetAgent Received VM Interfaces as: <IP_ADDRESS>
[00000017] [11/11/2022 07:04:03.83] [TRACE] NetAgent version received from Host is same as that in VM: <IP_ADDRESS>. Existing: <IP_ADDRESS>
[00000018] [11/11/2022 07:04:59.06] [INFO]  VMAgent log collector exit code is 0.
[00000018] [11/11/2022 07:04:59.06] [INFO]  VMAgent log collector output:
2022/11/11 6:44:03	Determined mode of execution: IAAS
2022/11/11 6:44:03	Looking for config at: C:\WindowsAzure\GuestAgent_2.7.41491.901\CommonAgentConfig.config and Exist: True
2022/11/11 6:44:03	Using Config from file: rootPath: %systemdrive%\WindowsAzure, configPath: %systemdrive%\WindowsAzure\Config, resourcesPath: %systemdrive%\WindowsAzure\Resources, logPath:%systemdrive%\WindowsAzure\Logs packagePath: C:\WindowsAzure\GuestAgent_2.7.41491.901
2022/11/11 6:44:03	ExpandedPaths: RootPath: C:\WindowsAzure\ LogPath: C:\WindowsAzure\Logs ConfigPath: C:\WindowsAzure\Config\ ResourcesPath: C:\WindowsAzure\Resources\ PackagePath: C:\WindowsAzure\GuestAgent_2.7.41491.901
***** Collecting required data (this will take time - DO NOT CLOSE) *****
2022/11/11 6:44:03	KvPRegFile name is 'KvpRegKey.xml'
2022/11/11 6:44:03	GARegFile name is 'GuestAgentRegKey.xml'
2022/11/11 6:44:03	waRegFile name is 'WindowsAzureRegKey.xml'
2022/11/11 6:44:03	Collecting registry information
2022/11/11 6:44:03	Getting KVP values
2022/11/11 6:44:04	Getting GuestAgent values
2022/11/11 6:44:05	Getting Windows Azure Values
2022/11/11 6:44:05	Collecting wireserver information
Attempting to discover fabric address on interface イーサネット 2.
Discovered fabric address on interface イーサネット 2. IP: <IP_ADDRESS>
Query Supported versions from: http://<IP_ADDRESS>
Query Goal state from: http://<IP_ADDRESS> over protocol version: 2015-04-05
Querying goal-state using client version '2015-04-05'
Goal state found: 15
Container Id: 0d99db5c-6731-4f7c-a007-9f4d35bffa77
Number of roles: 1
Querying role config using client version '2015-04-05'
Query Host plugin supported versions from: http://<IP_ADDRESS>
Querying host plugin versions: http://<IP_ADDRESS>:32526/versions
Host plugin versions: ["2015-09-01"]
2022/11/11 6:44:33	Getting plugin json files from C:\Packages\Plugins
2022/11/11 6:44:33	Getting plugin settings files from C:\Packages\Plugins
2022/11/11 6:44:33	Getting plugin status files from C:\Packages\Plugins
2022/11/11 6:44:33	Getting plugin xml files from C:\Packages\Plugins
2022/11/11 6:44:33	Getting file list of plugins from C:\Packages\Plugins
2022/11/11 6:44:40	Generating output: C:\WindowsAzure\CollectGuestLogsTemp\0d99db5c-6731-4f7c-a007-9f4d35bffa77.zip
2022/11/11 6:44:40	Add files to RuntimeAndAgent ...
2022/11/11 7:04:47	Add files to Config ...
2022/11/11 7:04:49	Add files to Panther ...
2022/11/11 7:04:52	Add files to EventLogs ...
2022/11/11 7:04:52	Skip the large file C:\Windows\System32\winevt\EventLogs\Application.evtx with length 134221824.
2022/11/11 7:04:54	Skip the large file C:\Windows\System32\winevt\EventLogs\System.evtx with length 134221824.
2022/11/11 7:04:54	Skip the large file C:\Windows\System32\winevt\EventLogs\Security.evtx with length 134221824.
2022/11/11 7:04:59	Generating output completed.

@RaymonZh, If you have questions or need help about installing GuestAgent, you can create a support request, or ask Azure community support.


Can't locate module: SWANK-IO-PACKAGE::SWANK-MACROSTEP

when i use M-x slime, it comes

Can't locate module:  SWANK-IO-PACKAGE::SWANK-MACROS

how could i fix it?
what's more, how can I change the themes? (I have try to build a file named init-local.el as the README.md said.)

when i use M-x slime, it comes
Can't locate module: SWANK-IO-PACKAGE::SWANK-MACROS

Not completely sure about that, sorry, but it's almost certainly a problem with slime, and not with this config. Someone has reported a similar issue previously (in #237) but didn't provide any details: at that time, a new contrib module had been added to Slime, and macrostep also seems to be new.
My suggestion would be to delete ~/.emacs.d/elpa/slime-2*, then restart Emacs, and ensure that any Common Lisp process you're connected to is also restarted.

what's more, how can I change the themes? (I have try to build a file named init-local.el as the README.md said.)

First install the extra themes, either via M-x list-packages or by adding a (require-package 'some-new-theme) in your init-local.el. Then select and save a new preferred theme using M-x customize-themes.
Hope that helps!

I know this is old, but adding to what Purcell said: swank/slime in quicklisp don't coexist well with swank/slime in elpa.  If your going to use quicklisp and slime use the quicklisp version and make sure to remove all slime and swank related packages you've downloaded via elpa.


EF Core provider gap: CreateContainerIfNotExistsAsync call is required for getting CosmosItem

In the new SDK, if you need to get CosmosItems you first need to call CreateContainerIfNotExistsAsync().
For SDK customers in general, this means there is no way to get the CosmosItems object without creating a container as a side effect, even if that isn't the intent.
For EF Core it means that some existing APIs will have unexpected semantics.
This issue was found while adapting EF Core provider to work with Cosmos SDK version <IP_ADDRESS>-preview.
cc @AndriySvyryd @ajcvickers @kirillg

@AndriySvyryd we are changing the API to make it easier to discover. I'm closing this issue please look at https://github.com/Azure/azure-cosmos-dotnet-v3/issues/333


Release version 1.0.0

Due to the release of inspec version 1.0.0 and changes in the json formatter, we are bumping the audit cookbook to version 1.0.0
The ['audit']['inspec_version'] cookbook attribute is also defaulting to 1.0.0 now.

Got verbal 👍  from @chris-rock on bumping the version to 1.0.0


added tor support

Is there any interest in adding Tor support? If not, I can close the PR.

The commit looks good - I am interested in having it - lets see what the maintainer thinks

Merging, thanks!


feat(select): add support for custom errorStateMatcher

Allows for the md-select error behavior to be configured through an @Input, as well as globally through the same provider as md-input-container.
Simplifies the signature of some of the error option symbols.

@kara and @mmalerba please take a look

@mmalerba I ended up splitting the ErrorOptions and MdError directive into a separate module to make the DI a little simpler and since we'll probably end up needing the MdError for MdSelect at some point anyway. Can you take another look?

Updated again @mmalerba.

Addressed the feedback @mmalerba.

@jelbourn would you rather move md-error into core/error/ or form-field/ as #6331 currently does.

@mmalerba form-field is good

In that case let's defer this PR until the form field gets in.

I think we can resume work on this one now

@mmalerba a lot changed since we parked this PR. I re-did it, excluded the mat-error changes and resubmitted as https://github.com/angular/material2/pull/7443.


Create Magic_Spells.cpp

Description
Added solution for Magic Spells, a hard level problem from Hackerrank
Fixes #1460
Type of change

[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have created a helpful and easy to understand README.md
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests/screenshots(if any) that prove my fix is effective or that my feature works

@Ayush7614 @Amit366 Kindly review the code and accept this pull request.


Drop dependency on Apache Commons Codec

This is effectively the same as #13, but only requires Java 1.6.
The dependency was only needed for Base64 conversion, which is now done by javax.xml.bind.DatatypeConverter which is part of JAXB 1.0+. As JAXB 2.0+ is part of the Java platform since Java 1.6, a minimum Java version of 1.6 is required.

JAXB is gone in Java 11 so it would be a very bad idea to merge this one now. @floscher can you please close it?


Question / Doc: Expose TCP services

I'm unable to figure out using the documentation if/how tcp-based services can be exposed to mesh-external or cluster-external sources or if that szenario is even supported.
This includes:

Gradually onboarding services to the cluster but still allowing inbound TCP connections (SMTP and AMQP in my case)
Exposing TCP-based services (IngressBackend with protocol: tcp doesn't seem to work)

Hi @dasMulli this can help https://release-v1-1.docs.openservicemesh.io/docs/demos/egress_policy/#tcp-egress ?

@mudit-01 this is about egress, i'm looking for TCP ingress

What would be needed for TCP ingress? As in: does it interfere with mTLS config in other lesteners / filter chains etc, parts of work that would need to be done etc.


Repo rename: s/pack-images/builder/

I also found these references:
https://github.com/heroku/languages-team/search?q=pack-images
https://github.com/heroku/procfile-cnb/search?q=pack-images
https://github.com/heroku/maple/search?q=pack-images
I feel like the procfile-cnb section should probably be removed and just link to the languages-team guide instead.

Related PR to fix compliance check after the rename: https://github.com/heroku/changeling/pull/995