rust: 1.29.1 -> 1.30.0

Motivation for this change
builds on x86_64 linux
Things done

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

[x] 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 nox --run "nox-review wip"
[x] 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)
[x] Fits CONTRIBUTING.md.

Success on x86_64-darwin (full log)
Attempted: rustc
Partial log (click to expand)
these derivations will be built:
  /nix/store/c6y5nyc90yyf6grcyp6basd2xz54afmy-rustc-1.30.0.drv
waiting for locks or build slots...
/nix/store/9mlgmipqar210mkaiqz3c5il0lxdyrl6-rustc-1.30.0

Timed out, unknown build status on x86_64-linux (full log)
Attempted: rustc
Partial log (click to expand)
   Compiling rustc_data_structures v0.0.0 (file:///build/rustc-1.30.0-src/src/librustc_data_structures)
   Compiling arena v0.0.0 (file:///build/rustc-1.30.0-src/src/libarena)
   Compiling syntax_pos v0.0.0 (file:///build/rustc-1.30.0-src/src/libsyntax_pos)
   Compiling rustc_errors v0.0.0 (file:///build/rustc-1.30.0-src/src/librustc_errors)
   Compiling proc_macro v0.0.0 (file:///build/rustc-1.30.0-src/src/libproc_macro)
   Compiling syntax_ext v0.0.0 (file:///build/rustc-1.30.0-src/src/libsyntax_ext)
   Compiling rustc_metadata_utils v0.0.0 (file:///build/rustc-1.30.0-src/src/librustc_metadata_utils)
   Compiling rustc_typeck v0.0.0 (file:///build/rustc-1.30.0-src/src/librustc_typeck)
building of '/nix/store/j1yzzw5jg9dpxlrcp5mj8awfgh755byb-rustc-1.30.0.drv' timed out after 3600 seconds
error: build of '/nix/store/j1yzzw5jg9dpxlrcp5mj8awfgh755byb-rustc-1.30.0.drv' failed

aarch64-linux works!

@LnL7 from my side everything looks good. You can merge it, when your other builds work.

Looks like cargo failed, working on a fix.

Cargo was working fine for me on linux. Was that cargo failure specific to darwin?

Yeah, linux is fine.

Success on aarch64-linux (full log)
Attempted: cargo, rustc
Partial log (click to expand)
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/b6m5awq2vjfa430pwbj9pqz3gg8y5cnj-cargo-1.30.0
shrinking /nix/store/b6m5awq2vjfa430pwbj9pqz3gg8y5cnj-cargo-1.30.0/bin/.cargo-wrapped
strip is /nix/store/p9akxn2sfy4wkhqdqa3li97pc6jaz3r1-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/b6m5awq2vjfa430pwbj9pqz3gg8y5cnj-cargo-1.30.0/bin
patching script interpreter paths in /nix/store/b6m5awq2vjfa430pwbj9pqz3gg8y5cnj-cargo-1.30.0
checking for references to /build in /nix/store/b6m5awq2vjfa430pwbj9pqz3gg8y5cnj-cargo-1.30.0...
/nix/store/b6m5awq2vjfa430pwbj9pqz3gg8y5cnj-cargo-1.30.0
/nix/store/ichjgdq9pznhcbqpdw1b9wspq416bbgz-rustc-1.30.0

Timed out, unknown build status on x86_64-linux (full log)
Attempted: cargo, rustc
Partial log (click to expand)
[ 62%] Building CXX object lib/Target/ARM/CMakeFiles/LLVMARMCodeGen.dir/ARMOptimizeBarriersPass.cpp.o
[ 62%] Building CXX object lib/Target/ARM/CMakeFiles/LLVMARMCodeGen.dir/ARMRegisterBankInfo.cpp.o
[ 62%] Building CXX object lib/CodeGen/CMakeFiles/LLVMCodeGen.dir/RegisterCoalescer.cpp.o
[ 62%] Building CXX object lib/Target/ARM/CMakeFiles/LLVMARMCodeGen.dir/ARMSelectionDAGInfo.cpp.o
[ 62%] Building CXX object lib/Target/ARM/CMakeFiles/LLVMARMCodeGen.dir/ARMSubtarget.cpp.o
[ 62%] Building CXX object lib/CodeGen/CMakeFiles/LLVMCodeGen.dir/RegisterPressure.cpp.o
[ 62%] Building CXX object lib/Target/ARM/CMakeFiles/LLVMARMCodeGen.dir/ARMTargetMachine.cpp.o
building of '/nix/store/j1yzzw5jg9dpxlrcp5mj8awfgh755byb-rustc-1.30.0.drv' timed out after 1800 seconds
cannot build derivation '/nix/store/amvxhnkmn7szrbgp5k6zrd9nrms8i7cj-cargo-1.30.0.drv': 1 dependencies couldn't be built
error: build of '/nix/store/amvxhnkmn7szrbgp5k6zrd9nrms8i7cj-cargo-1.30.0.drv', '/nix/store/j1yzzw5jg9dpxlrcp5mj8awfgh755byb-rustc-1.30.0.drv' failed


takeLatest is not accepting args

Description
Hello! I'm migrating from<EMAIL_ADDRESS>to v1.1.3 (the latest one) and I found that using takeLatest is giving me this error: Expected 2 arguments, but got 3 ... this is one of the lines with that error
function* watchCurrentContextItem(featureId: string) {
    yield takeLatest(ContextTypeKeys.SET_CURRENT_QTI_CONTEXT_ITEM, setDetailsPanelContextValue, [ featureId ]);
}

// AdDed [ featureId ] as an array because of the `args` param of takeLatest but was inly `featureId` without the array before

The docs says clearly that I can pass an array of args after the saga, so I don't understand what I'm I doing wrong ???
BTW I'm importing the takeLatest from import { takeLatest } from 'redux-saga/effects';

Could you prepare a TS playground with the problem depicted there?


Remaining perl process on MacOS

Etcher version: v1.0.0
Operating system and architecture: MacOS 10.12.4

After quitting Etcher, I noticed a perl process remains and seems to drain CPU like crazy. I thought that wasn't related to Etcher in any way, but inspecting the process proved me wrong.

I have no idea what triggers this, but flashing image went right, and no error was reported at any moment.
Sorry if this is an Electron related issue, but I couldn't find anything related to perl on their repository either.

Yeah, duplicate of #1288 and we've no idea yet what causes this :-S
Please feel free to add any extra comments you might have to that other issue.


runtimeChunk: single is not being honored for first entrypoint

Operating System: macOS 10.13/Arch Linux
Node Version: 10.3.0
NPM Version: 6.1.0
webpack Version: 4.10.1
webpack-serve Version: 1.0.2

This issue is for a:

[x] bug
[ ] feature request
[ ] modification request

Code
https://github.com/whs/wps-issue
How Do We Reproduce?

Run npm start
Go to http://localhost:8080/a.js . This URL has the runtime code even though there is /runtime.js already. Somehow, the chunk b and c does not have the runtime code.
Run npm run build (or just use the prebuilt files)
Look in dist/{a,b,c}.js. The files does not have any runtime code.

👉🏽 Need support, advice, or help? Don't open an issue.
Head to StackOverflow or https://gitter.im/webpack/webpack.

Not sure what a 'runtime code' is in this context (or in the context of webpack). webpack-serve doesn't modify your config or compiler (outside of webpack-hot-client adding an entry to allow for HMR). You may also be experiencing the same effects as #114

I'm pretty sure this is a bug in webpack stack, but it may or may not be a bug of webpack-serve. I'll try looking into webpack-hot-client.
In the minimal example I posted, I'm not using --content nor having any static content so I believe this is not the same case as #114.
The runtime is this piece of code which is described in webpack docs. In this bug, the runtime code appears in some entrypoints despite turning on the option to split it to another chunk. This is not the case when the same configuration is used with webpack-cli.

With regard to --content (or more specifically the content option) the default value is process.cwd() if no value is specified. It looks like the README doesn't have that correct, so I'll update it. As for the build, we pass things directly onto webpack-dev-middleware, which passes the config directly onto webpack proper.

Here's what I found:

I could isolate the issue to somewhere in webpack-hot-client's hotEntry. If I set WHC_TARGET to something else then the problem will not exists.
From what I understand the function injects webpack-hot-client/client?random into the first entrypoint.
So I run with WHC_TARGET set to disable autoinject and manually injectwebpack-hot-client/client?random into my entrypoint. The issue still does not happen.
With some breakpoints, I found that MultiEntryPlugin ran twice, one with original entrypoints and one with modified entrypoint. I modified EntryOptionPlugin to ignore the first call and the issue was resolved.

In summary, I believe the issue is that webpack-hot-client injected itself too late in the process.
Should I open an issue in webpack-hot-client?

You could, but the point at which hot-client is injecting the entries is literally the only place in the process that it can. A better route for your environment might be to use autoConfigure: false and add the entries and HMR Plugin as needed.

Submitted as https://github.com/webpack/webpack/issues/7452

@whs Did you ever resolve this? I'm not familiar with how all these libs tie together and I've had a hell of a time with trying to figure this out. I had to revert to webpack-dev-server so I could continue working.
I'm pretty sure my issue is the same, except I'm seeing the runtime chunk get inserted at the top of all my entry points. So, two scripts that should be sharing a single instance of a 3rd party module are both getting their own individual instances of it, causing errors.
With optimization: { runtimeChunk: single, ....... }, my production webpack build spits out a runtime.js that I include before other scripts. It looks like webpack-dev-server is doing the same (in-memory), but webpack-serve isn't.

We have moved back to webpack-dev-server


lecture06

made by Rakhlinskii Vlad

Changes Unknown when pulling 144376a88e89ac77052f998561250d6837c986b6 on vic0din:lecture07 into ** on rybalkinsd:lecture07**.


Empty element of type xsd:string results in empty object instead of empty string

I get a SOAP response looking like this:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
   <soap:Body>
      <!-- … -->
         <AccountData>
            <!-- … --->
            <Name></Name>
            <!-- … --->
      </AccountData >
      <!-- … -->
   </soap:Body>
</soap:Envelope>

and here is the definition of the reply from the WSDL:
<s:complexType name="AccountData">
  <s:sequence>
    <!-- … -->
    <s:element minOccurs="1" maxOccurs="1" name="Name" type="s:string" />
    <!-- … -->
  </s:sequence>
</s:complexType>

When <Name> is not empty I get a String in the resulting JavaScript object but when <Name> is empty I don't get an empty string as I would expect but an empty object ({}). Or in other words:

<Name>Foo</Name> => 'Foo'
<Name></Name> => {} expected: '' (empty string since type is xsd:string)

Is this intended behavior?

Any status update on this? Still in 0.6.1

Unfortunately there is no update on this issue @vincic - I'm sorry.

I'm having the same issue.
I wonder if we could use a 3rd party xmlToJson module to do the parsing?

@spock123 do you have some specific module in mind? Right now, we're using the sax library for parsing XML - are there better alternatives out there in the npm universe?

@herom not as I seed.. I've been looking into the code a little bit and found about about Sax...
So far I've ended up "parsing" the returned Json and replacing empty objects with empty strings, for the values I know are supposed to be strings. But this is not a good solution, would be awesome if we somehow to solve this. But as I see it, it's somewhere in the Sax module

I made one solution in commit https://github.com/vincic/node-soap/commit/421a9ba1b1149d5c8419bb3f882943853a9e909d but I had  problems creating a proper test. I tried with the request-response-samples way but my element always had undefined schema so my fix didn't work in the test.
Beside a missing test I am only worrying about the performance penalty for this fix, comments are welcome.
Anyway the fix breaks three tests. From what I can see, they should be changed since the expected value should be empty string and not an empty object.

Request Response Sampling Messages suffixed with In Out:

Uncaught AssertionError: "{\"return\":\"-1\",\"bstrError\":\"\"}" == "{\"return\":\"-1\",\"bstrError\":{}}"
     + expected - actual

     +{"return":"-1","bstrError":{}}
     -{"return":"-1","bstrError":""}

Request Response Sampling Messages suffixed with Input Output:

  Uncaught AssertionError: "{\"return\":\"-1\",\"bstrError\":\"\"}" == "{\"return\":\"-1\",\"bstrError\":{}}"
    + expected - actual

    +{"return":"-1","bstrError":{}}
    -{"return":"-1","bstrError":""}

Request Response Sampling Messages suffixed with Request Response:

      Uncaught AssertionError: "{\"return\":\"-1\",\"bstrError\":\"\"}" == "{\"return\":\"-1\",\"bstrError\":{}}"
      + expected - actual

      +{"return":"-1","bstrError":{}}
      -{"return":"-1","bstrError":""}

All tests passes now and the fix works for our production. Anyone looked at the pull request?

@vincic, could you provide a link to pull request you are referring to?

@shine-on
#637 is referenced above his comment

@shine-on any feedback on the #637 pull request?


Micro guide: NetNewsWire ❤ FreshRSS setup

Thank you for NetNewsWire, I've been a user for many years. Today, I came here to throw some moneys at you, and found out you do this out of love. Amazing. I don't know you but I love you.
I just setup NewsNetWire + FreshRSS.
I think I've tried before, but couldn't figure it out, and gave up.
But a comment on HN made me confident it does indeed exist and it works great.
I had to fiddle around a little. I'm reporting some feedback from the experience.
Also, I'm writing down the steps I wish I had found somewhere else documented.
Here's the 30-second version:

Assuming you have set up FreshRSS and you can login in the web UI

Open NetNewsWire > Preferences > Accounts > Add > FreshRSS

To sign in use:

Login: username same as the FreshRSS web UI
Password: API token created in: FreshRSS web UI > Profile > API Management
API URL: https://example.com/api/greader.php (try opening this in a browser, it should show something)

Done.
--
This took some fiddling. Initially I tried all combinations of (myuser | myuser@mydomain ) x (password) x (/api/, /rss/, /rss/api/greader.php). None worked. Creating a new user, retried all combinations. Still not working. 😅
Some extra notes for NNW
🌈 Note 1: It took me a while to find how to add a FreshRSS account to NNW.
Finally found it in settings>accounts>add
🌈 Note 2: Sign-in spits out a generic error message: Network Error.
It seems to me like it's the same message for every kind of error:

hostname not resolving
server not reachable/listening
bad certificates
wrong URL path
wrong credentials
probably more

This can be a red herring. A little more details in the error message would be helpful.
🌈 Note 3: FreshRSS API Token.
The FreshRSS user's password won't work for the API.
One has to go into FreshRSS Settings > Profile > API Access and create a new token.
It would be great to point users there, in some way.
Even just renaming the Password field to API token field would maybe point people the right direction.

Thanks so much, it saved me a lot of time!

Hello, I'm +1ing the Note 2.
I'm still struggling at the auth step doing exactly as said and still having this Network Error I can't diagnose.

@Thoscellen My URL was https://FQDN/api/greader.php, without the rss in it, just the api in the URL
this works flawlessy

My URL was https://FQDN/api/greader.php, without the rss in it

Ah indeed. /rss/ is for my own setup, because I'm hosting multiple applications on the same web server. Updated the original comment. Thank you @seraphyn

As an additional note you have to enable "Allow API access (required for mobile apps)" in FreshRSS before "API management" shows up.

Chiming in with what worked for me when setting up NetNewsWire (6.1.2 on macOS and iPadOS) with FreshRSS (1.21.0). This is the same as @mprimi's instructions, but there is an additional directory in the path to the API endpoint and I suspect some of the FreshRSS interface labels have changed.

In FreshRSS, go to settings menu (the cog icon) > Authentication
Check the Allow API access box
Click the Submit button
Go to Profile
In the API Management section, create an API password
Click the Submit button immediately below
In NetNewsWire, go to Settings > Accounts, then click the button to add an account
Select FreshRSS, then click the Continue button
Enter your FreshRSS username
Enter the user-specific API password
Enter your domain name with the format: https://domain.name/p/api/greader.php

Of course your path to FreshRSS will have to change if you have installed it in a subdirectory.

@membranophonist For me the following format works :https://domain.name/api/greader.php If I add /p/, I am getting the The API URL wasn't found.
The sync appears to be working but when i check out the docker logs, I see the following warning message. Does anyone know why?
[warning] --- Invalid POST token: 5a3ba2f980c74187abdf02772c8a886485aff3efZZZZZZZZZZZZZZZZZ
[warning] --- GReaderAPI::unauthorized

HUGE thank you to you all! This was a massive help, especially the instructions in https://github.com/Ranchero-Software/NetNewsWire/issues/3731#issuecomment-1524015039.

Stupid question maybe: after connecting to a self-hosted FreshRSS via API, does NNW then display all of FreshRSS' feeds separately including categories? Or does it just get one single feed from the self-hosted FreshRSS?
(Note: I'm kinda content with NNW standalone, but since I'll be having my own home server soon, I'd want to install FreshRSS, because there are some feeds that broadcast a lot of message, some of which I regularly miss when away from home.)


Bump-go-sdk to v1.0.1

What
updated go-sdk dependency to v1.0.1
Why
new go-sdk has breaking changes, but more simpler to maintain and extend
Notes

/e2e

/e2e

/e2e


Fix double attach which could prove difficult for certain probes

This should fix the double attach issue #199.
I am not sure if this is the right way to do it. Maybe someone else has a stronger opinion on it?
Best,
Yatekii

I tried to test this on a Nucleo board and something is wrong with attach: it returns a Probe(NotAttached) error.
Here is my code:
fn main() {
    pretty_env_logger::init();

    let probes = Probe::list_all();
    println!("Available probes: {:?}", probes);
    if probes.len() == 0 {
        return;
    }

    let probe: Probe = match probes[0].open() {
        Ok(probe) => probe,
        Err(e) => {
            println!("Failed to open the probe: {:?}", e);
            return;
        }
    };
    println!("Probe opened");

    let session = probe.attach("stm32f042").unwrap();
    let mem = session.attach_to_memory(0).unwrap();

    let v = mem.read32(0x0000_0000).unwrap();
    println!("read32: {:08x}", v);
}

I just fixed the NotAttached issue :)

Heh, now it works! Checked on NUCLEO-F042 and DWM1001-DEV boards.


Add more Mac homebrew dependencies

Following the "macOS with vcpkg" build instructions on my system (Mac OS 13.2.1, Intel cpu), I got a couple build failures, which were resolved by installing autoconf and automake via homebrew. This adds those dependencies to the appropriate command in the readme.

Thanks!


Vessel Viewer Continued UI modules not being installed

These three netkan files:
VesselView.netkan
VesselView-UI-RasterPropMonitor.netkan
VesselView-UI-Toolbar.netkan
used to work.  After a change suggested by Politas, to use a "find_matches"files" rather than excluding, and coinciding with the release of the latest ckan.exe, they don't work.
What happens is that the main mod gets installed, and then it says it's installing the other (ie: UI), and finishes, but the UI part doesn't get installed.
Here is the output from a command line install, on Windows:
`C:\Windows\System32>"D:\KerbalInstalls\1.1 Turbo Charged\ckan.exe" install VesselView VesselView-UI-Toolbar
About to install...

Vessel Viewer Continued 2:0.8.3(cached)
VesselView-UI-Toolbar 1:0.8.3(cached)

Continue? [Y/n] y
Installing mod "VesselView 2:0.8.3"
Installing mod "VesselView-UI-Toolbar 1:0.8.3"
Updating registry
Commiting filesystem changes
Rescanning GameData
Done!`
When I look at the relationships in the GUI for one of the UIs, it says that the VesselView-UI is provided by the other one, see the attached picture

I marked this a critical because there wasn't anything else which was relevent.  I'm not sure if this is a bug in ckan.exe, or just the netkan files aren't good.

Don't worry about the "Provided By" in that view - it's biased to showing an alternate, it seems. The installation works fine for me. I get both DLLs installed when I select both UI mods for installation.

Well, yes, so I'll get that fixed.
Wow, that's really strange.  When those dlls aren't in the same directory, they aren't loaded properly.  So this is the problem.
Thanks


Translation Improvement：code-of-conduct.md

1）修改了错别字
2）修改了显示不正常的一处markdown语法
3）对部分翻译进行改进，使其更易理解（至少我觉得更好理解了）

[x] Have you followed the contributing guidelines?
[x] Have you explained what your changes do, and why they add value to the Guides?

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

Thanks so much for your first contribution!  You rock, @taskmgr!


allow functions in bench_env to own the parameter

I saw that bench_env and gen_env both give the function to be benchmarked a mutable reference, not the actual value. Is there a reason for this?

If we passed ownership of the environment to the closure, the environment would be dropped before the closure returns, and the time taken to run the destructor would be included in the results.  For large environments, this can be significant.


Facing An Issue Of Teams

Hi,i deployed Frontend

and Backend as docker on the server ,

frontend proxy x.x.x.x:3000 as post.xlink-xxxx.com
backend proxy x.x.x.x:8989 as postapi.xlink-xxxx.com
this is my .env below .SDK admin doployed as well

This is [Firestore Rules]

apis feature working fine , login feature working fine

actually i deploy backend for the feature "TEAM"
but seems still not working , wonder where did i do wrong

And seems in the datebase has no data

kingly enlight me? thanks for your time

Can you tell me how you configured the proxy? It might be due to websocket misconfiguration on the proxy.
Do you see any calls being made to the backend?

Here is the nginx conf FIle sample
server {
listen 443 ssl;
server_name post.xlink-xxxx.com;
            ssl_certificate /etc/nginx/cert/xlink_cert.pem;
            ssl_certificate_key /etc/nginx/cert/xlink_key.pem;
            ssl_session_timeout 5m;

            gzip on;
            gzip_min_length 1k;
            gzip_buffers 4 16k;
            gzip_comp_level 2;
            gzip_types text/plain application/javascript application/x-javascript text/css application/xml text/javascript application/x-httpd-php image/jpeg image/gif image/png;
        gzip_vary off;
            gzip_disable "MSIE [1-6]\.";

            error_log /var/log/nginx/post_xlinkxxxx_com_error.log;

            location / {
            proxy_http_version 1.1;
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection 'upgrade';
            proxy_set_header Host $host;
            proxy_cache_bypass $http_upgrade;
            proxy_pass http://<IP_ADDRESS>:3000;
            }

server {
listen 443 ssl;
server_name postapi.xlink-xxxx.com;
            ssl_certificate /etc/nginx/cert/xlink_cert.pem;
            ssl_certificate_key /etc/nginx/cert/xlink_key.pem;
            ssl_session_timeout 5m;

            gzip on;
            gzip_min_length 1k;
            gzip_buffers 4 16k;
            gzip_comp_level 2;
            gzip_types text/plain application/javascript application/x-javascript text/css application/xml text/javascript application/x-httpd-php image/jpeg image/gif image/png;
        gzip_vary off;
            gzip_disable "MSIE [1-6]\.";

            error_log /var/log/nginx/postapi_xlinxxxx_com_error.log;

            location / {
            proxy_http_version 1.1;
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection 'upgrade';
            proxy_set_header Host $host;
            proxy_cache_bypass $http_upgrade;
            proxy_pass http://<IP_ADDRESS>:8989;
            }

}

Do you see any traffic reaching the backend? You could try to remove the connection upgrade and add a separate block that contains the upgrade, like:
location / {
            proxy_set_header Host $host;
            proxy_cache_bypass $http_upgrade;
            proxy_pass http://<IP_ADDRESS>:8989;
}

location /graphql/ws {
            proxy_http_version 1.1;
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection 'upgrade';
            proxy_set_header Host $host;
            proxy_cache_bypass $http_upgrade;
            proxy_pass http://<IP_ADDRESS>:8989;
}

Thank you , now is almost perfect working
Now only having an issue with the team invite fuction
seems cant recive the email

here is the config setting of email below
smtp: # SMTP information to send invite mails.
host: "smtp.gmail.com"
port: 587
username<EMAIL_ADDRESS>password: "Aa12345"
from:
name: "RAYNE"
email<EMAIL_ADDRESS>firewall has opened for port 587
but cant recive the email yet

Do you see anything in the logs regarding the sending of mails?
Please be aware that if you have 2FA on your Google account that you can't use SMTP with the normal password, you need to use app-passwords: https://support.google.com/accounts/answer/185833?hl=en

hmm seem no logs relate send email

umm about 2FA i think is not active

Can you check if you see the error in the GraphQL response?

looks like this


Town of Salem implementation

https://www.blankmediagames.com/gameplay/

We are going to skip this for the time being.


[Feature Request] Ability to take multiple pictures before exiting the camera app.

Please fill out either the bug or feature request section and remove whatever section you are not using.
Bug
Version Number of Plugin:
Device Tested On:
Simulator Tested On:
Expected Behavior
Actual Behavior
Steps to reproduce the Behavior
Feature Request:
It would be useful to be able to take several pictures in a row before returning to the calling method. Rather than doing: Tap "Take a Photo" button; take a picture; accept it (tap the check mark - on android); Tap "Take a Photo" button; etc until done. It would be preferable to avoid the [Tap "Take a Photo" button; ] step for subsequent pictures. When done, we could tap the back button.
Thanks for considering this request

No plan to ever implement sorry.


Create dm+d version of pen needles measure

Preview shows slightly more costs (approx £7200 out of £693k) and no negative values compared with non-dm+d version,so we should move to this version.


[PECO-1541] Optimize UC Volume ingestion

Currently, when we upload file to volume (SQL PUT) file is fully loaded into memory and then sent to a storage. Similarly, when downloading a file (SQL GET) the file is fully downloaded into memory, and only then stored on disc.
To optimize large file handling, Nodejs streams should be used instead.

Codecov Report
Attention: Patch coverage is 75.00000% with 3 lines in your changes are missing coverage. Please review.

Project coverage is 93.02%. Comparing base (c84ef8a) to head (6ab0178).

Files
Patch %
Lines

lib/DBSQLSession.ts
75.00%
2 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #247      +/-   ##
==========================================
- Coverage   93.18%   93.02%   -0.17%
==========================================
  Files          63       63
  Lines        1525     1533       +8
  Branches      266      267       +1
==========================================
+ Hits         1421     1426       +5
- Misses         41       43       +2
- Partials       63       64       +1

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

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

Project coverage is 93.19%. Comparing base (c00f72e) to head (44c5d62).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #247      +/-   ##
==========================================
+ Coverage   93.18%   93.19%   +0.01%
==========================================
  Files          63       63
  Lines        1525     1529       +4
  Branches      266      266
==========================================
+ Hits         1421     1425       +4
  Misses         41       41
  Partials       63       63

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

Do we have a similar issue in the python one?  I've been wondering about this for a while.

Do we have a similar issue in the python one? I've been wondering about this for a while.

Just checked - in PySQL everything is fine there.


1213 domain cgiservlet

The purpose of this sample is to help our devops people to debug issues related with this servlet (e.g. 3-14340994281).

This PR seems to have stalled.
@lurodrig have you signed an OCA: http://www.oracle.com/technetwork/community/oca-486395.html
@mriccell can you please review this PR?

Hello @Djelibeybim,
mmm, nope I did not sign it. I will the and let you know
Cheers,
Luis

Thanks Luis for submitting this PR, it looks good.

Thanks @mriccell. Once the OCA is signed, I'll merge this PR.

@lurodrig can you please sign OCA so that we can merge your changes?

I am closing this PR due to lack of CLA submission.


compileOnSave by default

Anyone feel strongly about defaulting to true ?

It's on a different PR :)


Update install.sh to fix bug in demo command

mentioned in DMs

Please install the CLI and try the recommended demo command for review


PSII photo processing: open questions for discussion

Are we saturating the PSII? does it matter for comparison across genotypes?

LEDs are (much) more powerful than Danforth
can we experimentally determine saturating light?

Can we map 3D structure (distance + angle) to the PSII output ( @solmazhajmohammadi ?)

can a 3d point cloud be used to identify leaves and distance of leaves from imager?
and can we use this to correct?
how does F relate to distance (See inverse square law F ~ (1/distance^2) this should be applied to fluorescence from leaf to sensor; can we ignore it from LEDs to leaf (if it is still saturating? otherwise we may need to measure / empirically derive the nonlinear function.

need to segment leaves

How to plot data?
Lemnatec sent test data to Noah to compare hand measurements with camera data.  They put the leaves parallel to the ground / sensor, which will not be relevant for field measurements.
TODO:

[ ] process test data from Lemnatec to determine if the camera values are relevant. ( @nfahlgren )
[ ] evaluate segmenting ( @ZongyangLi ) and doing a rough calculation of Fv/Fm

Fmax and Fmean look the same
frame 1=fdark, frame2=fmin, frame3=fmax.  Only use these frames.

[ ] decide how to evaluate / correct for whether illumination is saturating

@smarshall-bmr have you run tests with lights at different intensity?

Completion criteria?

[ ] protocol for using PSII camera
[ ] convert protocol into next steps toward generating Fv/Fm as a phenotype

Currently covered by #152; that issue may need to be split up into separate issues.

While giving tours we had a specialist in Photosystem II express doubt that we would be able to saturate the system @TinoDornbusch knows more about this then I do though. Theoretically we should see saturation as "clipping" on the response curve.
I have taken data sets at varying light intensities, exposure times, different distances apart (to characterize leakover distances) and different times apart (to asses dark adaption times.)
Much of this will change however, I'm planning on modifying the focal distance of the camera in order to give us a bit larger margin of error when it comes to scanning the field, currently the scanner box must be within 30cm of the plants to take a measurement, too close for me to comfortably allow the system to run autonomously.

@smarshall-bmr the question of how to address this criticism should be captured in the first bullet point in the issue 'Are we saturating the PSII? does it matter for comparison across genotypes?'
What do you mean by 'clipping'? Can you link (or give the dates of) the datasets that you generated at varying light intensities and propose a method of testing if we are saturating PSII?

PS the specialist was Steve Long. Noah said that this concern was pointed out many times with respect to the system at Danforth.

@ZongyangLi and @nfahlgren can you please summarize the results of your meeting, update this isssue, and create new ones as necessary?

From discussion with @nfahlgren , I am planning to create 2 extractors for this:

[ ] convert bin files into gray scale images,

[ ] create pseudocolored Fv/Fm image using F-images and create a Fv/Fm histogram.

@ZongyangLi @nfahlgren LemnaTec prepared an Octave script for me to use in order to check data that produces a Fv/Fm image as well as a response histogram. Would this be helpful for you?

@smarshall-bmr Thanks a lot! Is this the LemnaTec script you mentioned:
https://github.com/terraref/computing-pipeline/blob/master/scripts/PS2/GetPS2.m
I think I am writing script like this, except the way of determining a Fmax.

@nfahlgren  @ZongyangLi   I am in the Loop now and happy to contribute to write the Extractor. Can anyone help me to get Clowder running and briefly Show me how it works?
I would then share this Knowledge with my colleagues.

@TinoDornbusch: @ZongyangLi and @max-zilla created a version 1 extractor for PSII that converts the raw images to PNG and generates a histogram of Fv/Fm on the whole field-of-view. The code is here: https://github.com/terraref/extractors-multispectral/tree/master/psii. Right now it doesn't subset the plant pixels or generate any traits (e.g. mean Fv/Fm, etc.) but the plan was to extend the extractor after getting the basic infrastructure in place. We are happy to work with you on it.

@nfahlgren @ZongyangLi @max-zilla  Thanks, I will be in Maricopa during the next two weeks and plan to work on the PSII analysis. lets discuss some "trial experiments". I had treatment with PS2 blocking herbicide in mind and to monitor the PS2 efficiency over time.

@smarshall-bmr  Stuart you think it might be possible to get some herbicide containing DCMU. In Europe this is not available anymore.
https://en.wikipedia.org/wiki/DCMU

https://terraref.ncsa.illinois.edu/clowder/datasets/5936a3ad4f0c0ead2da27389 example output


What does‘ todo: per location and per camera’ mean？

Hi, @Skydes
I ran the pipeline on the robotCar dataset and compared the results on visiuallocalization.net, and found that the result data differed a lot in the night scene.
I see "per location and per camera" in the comment info, I guess it's because of this.
Could you please tell me in more detail what this means?
(Sorry, my English is bad.😭 )
Hope to hear from you soon. Thank you so much!

There are 2 tricks to improve image retrieval on RobotCar:

Retrieve per camera: global descriptors of the right/left/rear camera are queried only against other descriptors of the corresponding camera.
Retrieve per location: RobotCar provides the list of query corresponding to each subset of the 3D model so we can narrow down the set of database descriptors for each query.

These improvements are actually already public in an older branch that contain an earlier version of the pipeline: https://github.com/cvg/Hierarchical-Localization/blob/robotcar/pipelines/RobotCar/robotcar_pairs_from_retrieval.py#L60-L107
I don't have the time right now to clean it up and add it to the new RobotCar pipeline - feel free to submit a PR :)

There are 2 tricks to improve image retrieval on RobotCar:

Retrieve per camera: global descriptors of the right/left/rear camera are queried only against other descriptors of the corresponding camera.
Retrieve per location: RobotCar provides the list of query corresponding to each subset of the 3D model so we can narrow down the set of database descriptors for each query.

These improvements are actually already public in an older branch that contain an earlier version of the pipeline: https://github.com/cvg/Hierarchical-Localization/blob/robotcar/pipelines/RobotCar/robotcar_pairs_from_retrieval.py#L60-L107
I don't have the time right now to clean it up and add it to the new RobotCar pipeline - feel free to submit a PR :)

Thank you for your reply!😃
I'll try to retrieve per camera.
Retriveve per location... Is it perhaps not reasonable to use the sum of the localization results on the submaps to represent the localization results on the whole large-scale map?😶

There are 2 tricks to improve image retrieval on RobotCar:

Retrieve per camera: global descriptors of the right/left/rear camera are queried only against other descriptors of the corresponding camera.
Retrieve per location: RobotCar provides the list of query corresponding to each subset of the 3D model so we can narrow down the set of database descriptors for each query.

These improvements are actually already public in an older branch that contain an earlier version of the pipeline: https://github.com/cvg/Hierarchical-Localization/blob/robotcar/pipelines/RobotCar/robotcar_pairs_from_retrieval.py#L60-L107
I don't have the time right now to clean it up and add it to the new RobotCar pipeline - feel free to submit a PR :)

Thank you for your reply!smiley
I'll try to retrieve per camera and retriveve per location.😃
(Does this also suggest that I can narrow down the matches by dividing the subgraphs to solve the problem of duplication of some scenes?😶)

Image retrieval defines the image pairs that will be matched, so yes these improvements should reduce the number of incorrect matches.

Image retrieval defines the image pairs that will be matched, so yes these improvements should reduce the number of incorrect matches.

Thank you for your reply! You are my role model.


Not download Unreleased apps

Thank you very much for your great script. I want to say something that will make the script work more complete, And it's possible to download (Unreleased) apps and games. Please make this possible. Thank you

can't.
we can't download unreleased apps.
because that app is "unreleased".

But it can be downloaded with the phone from the Google Play Store app


Do not hold timelines lock while calling update_gc_info to avoid recu…

…srive mutex lock and so deadlock

Not safe, there's a race condition with branch creation. A new branch might be created, after you have collected the list of all branch points, but before you update gc info. You might then garbage collect away data that is needed by the new branch.
See discussion at https://github.com/neondatabase/neon/pull/2101

Not safe, there's a race condition with branch creation. A new branch might be created, after you have collected the list of all branch points, but before you update gc info. You might then garbage collect away data that is needed by the new branch.
See discussion at #2101

Hmm, we do hold the gc_cs lock, though. I'm confused, I thought we would no longer. So maybe it's OK? WDYT @aome510 ?

https://github.com/neondatabase/neon/pull/2154 actually allows getting rid of the tenant_mgr::get_local_timeline_with_load call, so that also fixes the deadlock-hazard. But if this PR is safe, it makes sense to commit it in any case, to avoid holding locks longer than necessary.


AENS Bid history page is broken

https://aeternity-blockchain.atlassian.net/browse/SW-1257
Describe the bug
On Bid history page are not displaying the full history of bids. Example: https://develop.wallet.z52da5wt.xyz/account-details/names/auctions/coolname.chain/history
Steps to reproduce

Choose a name
Check Bid history page

Environment selector
Chrome
Extension
Firefox
MacOS
iOS
Web wallet

@CedrikNikita To recheck with MDW team about the status.

https://github.com/aeternity/ae_mdw/issues/1666


[Discussion] Microsoft Security Advisory 4010983 : Vulnerability in ASP.NET Core MVC 1.1.0 Could Allow Denial of Service

Microsoft Security Advisory 4010983
Vulnerability in ASP.NET Core MVC 1.1.0 Could Allow Denial of Service
Executive Summary
Microsoft is releasing this security advisory to provide information about a vulnerability in the public versions of ASP.NET Core MVC 1.1.0. This advisory also provides guidance on what developers can do to update their applications correctly.
Microsoft is aware of a security vulnerability in the public version of ASP.NET Core MVC 1.1.0 where a malformed HTTP request could lead to a denial of service.
Developers are advised to update all apps to use package version 1.1.1 or greater.
Mitigating Factors
Only applications targeting ASP.NET Core 1.1.0 are affected. Applications targeting ASP.NET Core 1.0.0, 1.0.1, 1.02 and 1.0.3 are not affected.
Affected Packages and Versions

Package Name
Package Version

Microsoft.AspNetCore.Mvc.Core
1.1.0

Advisory FAQ
How do I know if I am affected?
ASP.NET Core has two different types of dependencies, direct and transitive. If your project has a direct or transitive dependency on any of the affected packages listed above you may be affected.
Direct Dependencies
Direct dependencies are dependencies where you specifically add a package to your project. For example, if you add the Microsoft.AspNetCore.Mvc package to your project then you have taken a direct dependency on Microsoft.AspNetCore.Mvc.
Direct dependencies are discoverable by reviewing your project.json or csproj file.
Transitive Dependencies
Transitive dependencies occur when you add a package to your project that in turn relies on another package. For example, if you add the Microsoft.AspNetCore.Mvc package to your project it depends on the Microsoft.AspNetCore.Mvc.Core package (among others). Your project has a direct dependency on Microsoft.AspNetCore.Mvc and a transitive dependency on the Microsoft.AspNetCore.Mvc.Core package.
Transitive dependencies are reviewable in the Visual Studio Solution Explorer window, which supports searching, or by reviewing the project.lock.json file contained in the root directory of your project for project.json projects or the project.assets.json file contained in the obj directory of your project for csproj projects. These files are the authoritative list of all packages used by your project, containing both direct and transitive dependencies.
Any ASP.NET Core MVC 1.1 application will have a dependency on the affected package, either direct or transitive.
How do I fix my affected application?
You will need to fix both direct dependencies and review and fix any transitive dependencies. Version 1.1.1 of the vulnerable package contains the fixes required to secure your app.
Fixing Direct Dependencies – project.json/VS2015
Open your project.json file in your editor. Look for the dependencies section. Below is an example dependencies section:
  "dependencies": {
    "Microsoft.NETCore.App": {
      "version": "1.1.0",
      "type": "platform"
    },
    "Microsoft.AspNetCore.Server.Kestrel": "1.1.0",
    "Microsoft.AspNetCore.Mvc.Core": "1.1.0",
  }

This example has three direct dependencies, Microsoft.NetCore.App, Microsoft.AspNetCore.Server.Kestrel and Microsoft.AspNetCore.Mvc.Core.
Microsoft.NetCore.App is the platform the application targets, you should ignore this. The other packages expose their version is to the right of the package name, in our example our non-platform packages are version 1.1.0.
Review your direct dependencies for any instance of Microsoft.AspNetCore.Mvc.Core version 1.1.0, in the example above there is a direct dependency on the vulnerable package.
To update to the new package, change the version number to be 1.1.1. After updating the vulnerable package version save your project.json file.

Note: As part of patching ASP.NET Core MVC we update every Microsoft.AspNetCore.Mvc.* package. If, for example, you have a dependency on Microsoft.AspNetCore.Mvc you should update its version to 1.1.1, and it will also update the vulnerable Microsoft.AspNetCore.Mvc.Core package.

The dependencies section in our example project.json would now look as follows:
  "dependencies": {
    "Microsoft.NETCore.App": {
      "version": "1.1.0",
      "type": "platform"
    },
    "Microsoft.AspNetCore.Server.Kestrel": "1.1.0",
    "Microsoft.AspNetCore.Mvc.Core": "1.1.1",
  }

If you are using Visual Studio and save your updated project.json file Visual Studio will restore the new package version. You can see the restore results by opening the Output Window (Ctrl+Alt+O) and change the “Show output from” drop down to Package Manager.
If you are not using Visual Studio open a command line and change to your project directory. Execute the dotnet restore command to restore your new dependency.
Once you have addressed all your direct dependencies you must also review your transitive dependencies.
Fixing Direct Dependencies – csproj/VS2017
Open your projectname.csproj file in your editor, or right click on the project in Visual Studio 2017 and choose Edit projectname.csproj from the content menu, where projectname is the name of your project. Look for PackageReference nodes. Below shows an example project file:
<Project ToolsVersion="15.0" Sdk="Microsoft.NET.Sdk.Web">
  <PropertyGroup>
    <TargetFramework>netcoreapp1.1</TargetFramework>
  </PropertyGroup>
  <PropertyGroup>
    <PackageTargetFallback>$(PackageTargetFallback);portable-net45+win8+wp8+wpa81;</PackageTargetFallback>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="Microsoft.AspNetCore" Version="1.1.0" />
    <PackageReference Include="Microsoft.AspNetCore.Mvc.Core" Version="1.1.0" />
  </ItemGroup>
  <ItemGroup>
    <DotNetCliToolReference Include="Microsoft.VisualStudio.Web.CodeGeneration.Tools" Version="1.0.0-msbuild3-final" />
  </ItemGroup>
</Project>

The example has two direct package dependencies, as seen by the two PackageReference elements. The name of the package is in the Include attribute, and the package version number is in the Version attribute expose their version is to the right of the package name. The example shows two packages Microsoft.AspNetCore and Microsoft.AspNetCore.Mvc.Core and each package is version 1.1.0.
Review your PackageReference elements for any instance of Microsoft.AspNetCore.Mvc.Core version 1.1.0.
If a reference is present update to the new package by change the Version attribute value to be 1.1.1. After updating the vulnerable package version save your csproj file.

Note: As part of patching ASP.NET Core MVC we update every Microsoft.AspNetCore.Mvc.* package. If, for example, you have a dependency on Microsoft.AspNetCore.Mvc you should update its version to 1.1.1, and it will also update the vulnerable Microsoft.AspNetCore.Mvc.Core package.

The example csproj would now look as follows:
<Project ToolsVersion="15.0" Sdk="Microsoft.NET.Sdk.Web">
  <PropertyGroup>
    <TargetFramework>netcoreapp1.1</TargetFramework>
  </PropertyGroup>
  <PropertyGroup>
    <PackageTargetFallback>$(PackageTargetFallback);portable-net45+win8+wp8+wpa81;</PackageTargetFallback>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="Microsoft.AspNetCore" Version="1.1.0" />
    <PackageReference Include="Microsoft.AspNetCore.Mvc.Core" Version="1.1.1" />
  </ItemGroup>
  <ItemGroup>
    <DotNetCliToolReference Include="Microsoft.VisualStudio.Web.CodeGeneration.Tools" Version="1.0.0-msbuild3-final" />
  </ItemGroup>
</Project>

If you are using Visual Studio and save your updated csproj file Visual Studio will restore the new package version. You can see the restore results by opening the Output Window (Ctrl+Alt+O) and change the “Show output from” drop down to Package Manager.
If you are not using Visual Studio open a command line and change to your project directory. Execute the dotnet restore command to restore your new dependency.
Once you have addressed all your direct dependencies you must also review your transitive dependencies.
Reviewing Transitive Dependencies
There are two ways to view transitive dependencies. You can use Visual Studio’s Solution Explorer, or by reviewing your project.lock.json (project.json/VS2015) or project.assets.json (csproj/VS2017) file.
Using Visual Studio Solution Explorer (VS2015)
If you want to use Visual Studio 2015 open your project in Visual Studio 2015 then press Ctrl+; to activate the search in Solution Explorer. Search for Microsoft.AspNetCore.Mvc.Core and make a note of the version numbers of any results you find.
For example, searching for Microsoft.AspNetCore.Mvc.Corein an example project that contains a reference toMicrosoft.AspNetCore.Mvc` shows the following results in Visual Studio 2015;

Figure 1: Searching references in Visual Studio 2015
The search results appear as a tree. In these results, you can see we have found references to Microsoft.AspNetCore.Mvc.Core, version 1.1.0, the vulnerable version.
The first entry under the References heading refers to the target framework your application is using. This will be .NETCoreApp, .NETStandard or .NET-Framework-vX.Y.Z (where X.Y.Z is an actual version number) depending on how you configured your application. Underneath your target framework will be the list of packages you have directly taken a dependency on. In this example the application takes a dependency on Microsoft.AspNetCore.Mvc. Microsoft.AspNetCore.Mvc in turn has leaf nodes that list its dependencies and their versions. In this case the Microsoft.AspNetCore.Mvc package takes a dependency on a vulnerable version of Microsoft.AspNetCore.Mvc.Core and numerous other packages.
Manually reviewing project.lock.json (project.json/VS2015)
Open the project.lock.json file in your editor. We suggest you use an editor that understands json and allows you to collapse and expand nodes to review this file; both Visual Studio and Visual Studio Code provide this functionality.
If you are using Visual Studio the project.lock.json file is “underneath” the project.json file. Click the right pointing triangle, ▷, to the left of the project.json file to expand the solution tree to expose the project.lock.json file. Figure 1 below shows a project with the project.json file expanded to show the project.lock.json file.

Figure 2: project.lock.json file location
Search the project.lock.json file for the string “Microsoft.AspNetCore.Mvc.Core/1.1.0”. If your project.lock.json file includes this string, you have a dependency on the vulnerable package.
Fixing transitive dependencies (project.json/VS2015)
If you have not found any reference to Microsoft.AspNetCore.Mvc.Core/1.1.0 this means none of your direct dependencies depend on the vulnerable version of Microsoft.AspNetCore.Mvc.Core or you have already fixed the problem by updating the direct dependencies.
If your transitive dependency review found references to the vulnerable Microsoft.AspNetCore.Mvc.Core/1.1.0 you must add a direct dependency to the updated package to your project.json file to override the transitive dependency. Open your project.json and find the dependencies section. For example:
  "dependencies": {
    "Microsoft.NETCore.App": {
      "version": "1.1.0",
      "type": "platform"
    },
    "Microsoft.AspNetCore.Server.Kestrel": "1.1.0",
    "Microsoft.AspNetCore.Mvc": "1.1.0"
  }

The results of our transitive package search showed us that Microsoft.AspNet.Mvc depends on Microsoft.AspNet.Mvc.Core version 1.1.0. To fix this you must add a direct dependency by adding it to the project.json file. You do this by adding a new line to the dependencies section, referring the fixed version. For example, to pull in the fixed version of Microsoft.AspNet.Mvc.Core, version 1.1.1 you edit the project.json file as follows;
  "dependencies": {
    "Microsoft.NETCore.App": {
      "version": "1.1.0",
      "type": "platform"
    },
    "Microsoft.AspNetCore.Mvc.Core": "1.1.1",
    "Microsoft.AspNetCore.Server.Kestrel": "1.1.0",
    "Microsoft.AspNetCore.Mvc.Core ": "1.1.0"
  }

Once you have added direct dependencies to the fixed packages save your project.json file.
If you are using Visual Studio and save your updated project.json file Visual Studio will restore the new package versions. You can see the restore results by opening the Output Window (Ctrl+Alt+O) and change the “Show output from” drop down to Package Manager.
If you are not using Visual Studio open a command line and change to your project directory. Execute the dotnet restore command to restore your new dependencies.
Using Visual Studio Solution Explorer (VS2017)
If you want to use Solution Explorer open your project in Visual Studio 2017, then press Ctrl+; to activate the search in Solution Explorer. Search for Microsoft.AspNetCore.Mvc.Core and make a note of the version numbers of any results you find.
For example, searching for Microsoft.AspNetCore.Mvc.Core in an example project that contains a package that takes a dependency on Microsoft.AspNetCore.Mvc shows the following results in Visual Studio 2017;

Figure 3: Searching references in Visual Studio 2017
The search results appear as a tree. In these results, you can see we have found references to Microsoft.AspNetCore.Mvc.Core version 1.1.0.
Underneath the Dependencies node will be a NuGet node. Under the NuGet node will be the list of packages you have directly taken a dependency on and their versions. In this example the application takes a direct dependency on Microsoft.AspNetCore.Mvc. Microsoft.AspNetCore.Mvc in turn has leaf nodes that list its dependencies and their versions. In the example the Microsoft.AspNetCore.Mvc package takes a dependency on a version of Microsoft.AspNetCore.Mvc.ApiExplorer which in turn takes a dependency on a vulnerable version of Microsoft.AspNetCore.Mvc.Core. You can see that other packages also take a dependency on the vulnerable version of Microsoft.AspNetCore.Mvc.Core.
Manually reviewing project.assets.json (VS2017)
Open the project.assets.json file from your project’s obj directory in your editor. We suggest you use an editor that understands json and allows you to collapse and expand nodes to review this file; both Visual Studio and Visual Studio Code provide this functionality.
Search the project.assets.json file for the string “Microsoft.AspNetCore.Mvc.Core/1.1.0”. If your project.assets.json file includes this string then you have a dependency on the vulnerable package.
Fixing transitive dependencies (csproj/VS2017)
If you have not found any reference to Microsoft.AspNetCore.Mvc.Core/1.1.0 this means none of your direct dependencies depend on the vulnerable version of Microsoft.AspNetCore.Mvc.Core or you have already fixed the problem by updating the direct dependencies.
If your transitive dependency review found references to the vulnerable Microsoft.AspNetCore.Mvc.Core/1.1.0 you must add a direct dependency to the updated package to your csproj file to override the transitive dependency. Open your projectname.csproj file in your editor, or right click on the project in Visual Studio 2017 and choose Edit projectname.csproj from the content menu, where projectname is the name of your project. Look for PackageReference nodes, for example;
<Project ToolsVersion="15.0" Sdk="Microsoft.NET.Sdk.Web">
  <PropertyGroup>
    <TargetFramework>netcoreapp1.1</TargetFramework>
  </PropertyGroup>
  <PropertyGroup>
    <PackageTargetFallback>$(PackageTargetFallback);portable-net45+win8+wp8+wpa81;</PackageTargetFallback>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="Microsoft.AspNetCore" Version="1.1.0" />
    <PackageReference Include="Microsoft.AspNetCore.Mvc" Version="1.1.0" />
    <PackageReference Include="Microsoft.AspNetCore.StaticFiles" Version="1.1.0" />
  </ItemGroup>
  <ItemGroup>
    <DotNetCliToolReference Include="Microsoft.VisualStudio.Web.CodeGeneration.Tools" Version="1.0.0-msbuild3-final" />
  </ItemGroup>
</Project>

In the example csproj file above there are 3 PackageReference nodes. The results of our transitive package search showed us that our application depends on the vulnerable Microsoft.AspNet.Mvc.Core version 1.1.0. To fix this you must add a new direct dependency by adding it to the csproj file. You do this by adding a new PackageReference at the top of the PackageReference list, referring the fixed version. For example, to pull in the fixed version of Microsoft.AspNet.Mvc.Core, version 1.1.1 in the example csproj file it would be changed as follows:
<Project ToolsVersion="15.0" Sdk="Microsoft.NET.Sdk.Web">
  <PropertyGroup>
    <TargetFramework>netcoreapp1.1</TargetFramework>
  </PropertyGroup>
  <PropertyGroup>
    <PackageTargetFallback>$(PackageTargetFallback);portable-net45+win8+wp8+wpa81;</PackageTargetFallback>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="Microsoft.AspNetCore.Mvc.Core" Version="1.1.1" />
    <PackageReference Include="Microsoft.AspNetCore" Version="1.1.0" />
    <PackageReference Include="Microsoft.AspNetCore.Mvc" Version="1.1.0" />
    <PackageReference Include="Microsoft.AspNetCore.StaticFiles" Version="1.1.0" />
  </ItemGroup>
  <ItemGroup>
    <DotNetCliToolReference Include="Microsoft.VisualStudio.Web.CodeGeneration.Tools" Version="1.0.0-msbuild3-final" />
  </ItemGroup>

Once you have added the direct dependency reference save your cspro file.
If you are using Visual Studio save your updated csproj file and Visual Studio will restore the new package versions. You can see the restore results by opening the Output Window (Ctrl+Alt+O) and change the “Show output from” drop down to Package Manager.
If you are not using Visual Studio open a command line and change to your project directory. Execute the dotnet restore command to restore your new dependencies.
Rebuilding your application
Finally rebuild your application, test as you would do normally and redeploy using your favored deployment mechanism.
Other Information
Support
You can ask questions about this issue on github, in the ASP.NET Core MVC repo. This is located at https://github.com/aspnet/Mvc.
Reporting Security Issues
If you have found a potential security issue in .NET Core please email details to<EMAIL_ADDRESS>Reports may qualify for the .NET Core Bug Bounty. Details of the .NET Core Bug Bounty including Terms and Conditions are at https://aka.ms/corebounty.
Disclaimer
The information provided in this advisory is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
Revisions
V1.0 (January 26, 2017): Advisory published.
KB4010983 on TechNet

What's the vulnerability? Is there a PoC and/or a commit that fixes it? This post just explains how to upgrade and doesn't explain what the vulnerability actually is 😕

And that's on purpose. We haven't pushed the source yet, so I couldn't link even if I wanted to.

Applications targeting ASP.NET Core 1.0.0, 1.0.1 or 1.02 are not affected.

I assume this also includes 1.0.3?

Ah it does indeed

Do we need to update .NET Core Windows Server Hosting bundle? Where to get a new .exe file?

@aspifycom I don't believe so (but I'll check Monday when those folks are in the office).
From the docs it looks like the bundle gives you everything necessary to host ASP.NET Core apps, but not ASP.NET itself - that's provided by the app deployment. It's up to the apps themselves to get updated, and each app needs to update itself, as they all carry the MVC pieces themselves, in isolation (This was a deliberate decision on our part - if every we introduced something breaking it'd only affect apps who choose to take that version)

That's correct.

@blowdart BTW I'm putting this in the Discussions milestone because we don't leave bugs open in product milestones (that would imply they still have bugs 😄).

Fixed by https://github.com/aspnet/Mvc/commit/5885feb7c01014236503b52dbd2aa6e84c0f32a9

After update to 1.1.1 I´m having problem with IActionContextAccessor injection.
What changes about its utilization?

@rynowak - I had to include this line at ConfigureServices to fix:
services.AddSingleton<IActionContextAccessor, ActionContextAccessor>();

We are closing this issue because no further action is planned for this issue. If you still have any issues or questions, please log a new issue with any additional details that you have.


Typeset non-existent DOM id

Making the call MathJax.Hub.Queue(["Typeset", MathJax.Hub, <bad-id>]) causes the entire document to be typeset.  I'm not sure if this is a "bug" or a "feature".  Still, for me, I'd prefer the call to fail to do anything to the document.  Through my debugging, via Firebug, I found that the relevant call stack is as follows: document.getElementById/MathJax.js: 2374, elementCallback/MathJax.js:2366, Typeset/MathJax.js:2020.  The call to the DOM for the element with the bad Id returns null, resulting in the element array in elementCallback being exactly [null].  So elementCallback returns { count: 1, elements: null, callback: {}}, which causes Preprocess and Process to be called on null.  And as I understand the documentation, this causes the document to be typeset.

        \(x^{2}+y^{2}=z^{2}\)

(20:30 UTC) Edit to correct HTML and grammar

Thanks for the report. We'll look into it.


Provide DocumentClient constructor for a connection string

The DocumentDB SDK does not provide a DocumentClient constructor that simply takes a connection string like other Azure SDKs, e.g. the Azure Storage SDK. It would be really nice to just store a connection string in the application settings or an environment variable and use that to instantiate a DocumentClient. At the moment you have to parse the endpoint uri and key from that yourself to provide it to the client.

@stefan-akelius Please upvote: https://feedback.azure.com/forums/263030-documentdb/suggestions/17777323-connection-string
It's a fair ask from the consistency point of view for an Azure service.
We also provide the URI and Keys as separate properties in the Azure portal, so you shouldn't need to parse that and just use it as 2 different properties.
Anyways, I'll add this to our backlog and use the UserVoice one for gauging interest and close this GitHub issue.

Ok, would have liked to help out if the source code was available here. Yes, it does not block any scenario and is mainly desirable from a consistency point of view, but it would be much less of a hassle in some situations like in Azure Functions. Those guys do use the DocumentDB connection string for their binding. Unfortunately for some operations (like delete) you need a DocumentClient. And in that case you either put the url and key into the app settings - which means you have the same credentials in there twice - or you manually parse the connection string and feed that to the DocumentClient yourself. Both not that nice.

@stefan-akelius Sounds good. We will get this prioritized.

Here is an implementation similar to CloudStorageAccount.
public static class DocumentDbAccount
{
	public static DocumentClient Parse(string connectionString)
	{
		DocumentClient ret;

		if (String.IsNullOrWhiteSpace(connectionString))
		{
			throw new ArgumentException("Connection string cannot be empty.");
		}

		if(ParseImpl(connectionString, out ret, err => { throw new FormatException(err); }))
		{
			return ret;
		}

		throw new ArgumentException($"Connection string was not able to be parsed into a document client.");
	}

	public static bool TryParse(string connectionString, out DocumentClient documentClient)
	{
		if (String.IsNullOrWhiteSpace(connectionString))
		{
			documentClient = null;
			return false;
		}

		try
		{
			return ParseImpl(connectionString, out documentClient, err => { });
		}
		catch (Exception)
		{
			documentClient = null;
			return false;
		}
	}

	private const string AccountEndpointKey = "AccountEndpoint";
	private const string AccountKeyKey = "AccountKey";
	private static readonly HashSet<string> RequireSettings = new HashSet<string>(new [] { AccountEndpointKey, AccountKeyKey }, StringComparer.OrdinalIgnoreCase);

	internal static bool ParseImpl(string connectionString, out DocumentClient documentClient, Action<string> error)
	{
		IDictionary<string, string> settings = ParseStringIntoSettings(connectionString, error);

		if (settings == null)
		{
			documentClient = null;
			return false;
		}

		if (!RequireSettings.IsSubsetOf(settings.Keys))
		{
			documentClient = null;
			return false;
		}

		documentClient = new DocumentClient(new Uri(settings[AccountEndpointKey]), settings[AccountKeyKey]);
		return true;
	}

	/// <summary>
	/// Tokenizes input and stores name value pairs.
	/// </summary>
	/// <param name="connectionString">The string to parse.</param>
	/// <param name="error">Error reporting delegate.</param>
	/// <returns>Tokenized collection.</returns>
	private static IDictionary<string, string> ParseStringIntoSettings(string connectionString, Action<string> error)
	{
		IDictionary<string, string> settings = new Dictionary<string, string>();
		string[] splitted = connectionString.Split(new char[] { ';' }, StringSplitOptions.RemoveEmptyEntries);

		foreach (string nameValue in splitted)
		{
			string[] splittedNameValue = nameValue.Split(new char[] { '=' }, 2);

			if (splittedNameValue.Length != 2)
			{
				error("Settings must be of the form \"name=value\".");
				return null;
			}

			if (settings.ContainsKey(splittedNameValue[0]))
			{
				error(string.Format(CultureInfo.InvariantCulture, "Duplicate setting '{0}' found.", splittedNameValue[0]));
				return null;
			}

			settings.Add(splittedNameValue[0], splittedNameValue[1]);
		}

		return settings;
	}
}

@rnagpal You have this issue marked as planned here but on on August 29th it was set to Unplanned  on the link https://feedback.azure.com/forums/263030-documentdb/suggestions/17777323-connection-string you provided with no comment.
Is this still going to be done? It is a very useful feature and promotes constancy with the connection methods of CloudServiceAccount for blob storage.

@rnagpal Any update on this issue?

ping @rnagpal

@rnagpal any update?

@Jameskmonger latest V3 CosmosClient has connection-string constructor.
ref: https://docs.microsoft.com/en-us/azure/cosmos-db/sql-api-sdk-dotnet-standard
Connection string constructor


Implement Image Fetching Function

Write a function to fetch the weekly menu image from the specified URL.

WIP with facebook-business-sdk and Graph API, will need more time to set the permissions and try not to reinvent the wheel


jaq: 1.6.0 -> 2.0.1

Things done
Changelog: https://github.com/01mf02/jaq/releases/tag/v2.0.1

jaq: format
jaq: 1.6.0 -> 2.0.1

cc @figsoda @siraben

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[x] x86_64-darwin
[x] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 363868

x86_64-linux

:white_check_mark: 1 package built:

jaq

aarch64-linux

:white_check_mark: 1 package built:

jaq

x86_64-darwin

:x: 1 package failed to build:

jaq

aarch64-darwin

:white_check_mark: 1 package built:

jaq

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 363868

x86_64-linux

:white_check_mark: 1 package built:

jaq

aarch64-linux

:white_check_mark: 1 package built:

jaq

x86_64-darwin

:white_check_mark: 1 package built:

jaq

aarch64-darwin

:white_check_mark: 1 package built:

jaq

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 363868

x86_64-linux

:white_check_mark: 1 package built:

jaq

aarch64-linux

:white_check_mark: 1 package built:

jaq

x86_64-darwin

:white_check_mark: 1 package built:

jaq

aarch64-darwin

:white_check_mark: 1 package built:

jaq


refactor portal meta server address logic a little bit

What's the purpose of this PR
Refactor #2953 a little bit
Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Read the Contributing Guide before making this pull request.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit tests to verify the code.
[x] Run mvn clean test to make sure this pull request doesn't break anything.

Coverage decreased (-0.003%) to 54.922% when pulling aa08a7ff88f1d493e3545ca9d6d6012ee4369676 on nobodyiam:refactor-db-meta-server-address into a81d7287014ab8bfc327040a66ac8a5d5510b7e9 on ctripcorp:master.


[FEATURE REQ] Page and Response should implement or inherit from a common ancestor

Library or service name.
What library or service is this request related to? Azure.Core
Is your feature request related to a problem? Please describe.
Currently, Page<T> is a basic class that has no inheritance or implementation chain. However, it is in fact very similar to a Response<T> - it is a page of results that come down through a Response. Accordingly, both types have the GetRawResponse() method. Therefore, there should be some common ancestor between the two so that methods can accept an argument that matches either of these types. Currently, there is no clean way of achieving this behavior.

//cc: @pakrym, @KrzysztofCwalina

What would be an example of a method you would accept the common type into?

We have an "observer" method that receives the responses for all Cosmos DB requests, and updates Prometheus metrics based on the request charge for that response.

But you can achieve the same thing by having a method that takes Response and calling .GetRawResponse() on pageable when needed.

Sorry, I probably should have elaborated a bit more - this method takes in the delegate of the asynchronous task to be executed (eg, Func<Context, CancellationToken, Task<T>> where T : Azure.Response<R>). It then executes that delegate, monitors it, and records Prometheus metrics accordingly (along with some other operations). So, this method doesn't know what exact return type it's working with - whether it is a Page, or an ItemResponse, or a StoredProcedureResponse, etc. All it needs to know is that the return type has a raw Response object on it that it can use to get the request charge. It then records that, and passes the result up the chain.

So would adding a couple overloads for this method that know how to inspect [Async]Pageable help? E.g. Func<Context, CancellationToken, Task<T>> where T : Azure.Pageable<R> and another that takes Func<Context, CancellationToken, Task<T>> where T : Azure.AsyncPageable<R>

Page<T> has a 'IReadOnlyList Values { get; }' property. Response<T> has a 'T Value { get; }' property. If Page<T> inherits from Response<T>, what would the Value property return when called on Page<int>?, i.e. which int would it return?

I'm proposing that Page<T> and Response<T> implement/inherit a common ancestor, and not that Page<T> inherit Response<T>.
One possible solution is to introduce something like an IResponseEnvelope interface that has a GetRawResponse() method on it, and have Page<T> and Response<T> both implement that interface.

'm proposing that Page and Response implement/inherit a common ancestor, and not that Page inherit from Response.

Ah, sorry, I missed that.

Don't think the use case is common enough to motivate adding this feature.


Laser Scan rotates with robot ------- [ERROR] [1716697697.080277840] [rviz2]: Lookup would require extrapolation into the future. Requested time<PHONE_NUMBER>.040514 but the latest data is at time<PHONE_NUMBER>.039929, when looking up transform from frame [laser_frame] to frame [odom] #4369

Required Info:
Operating System: Ubuntu 22.04 LTS
ROS2 Version: ROS2 Humble
The LaserScan rotating with robot when I use teleop_twist_keyboard to manually rotate the robot. I am using the rplidar_ros package to run the lidar I am unable to perform navigation and mapping I tried mapping
Screencast from 05-14-2024 01:27:45 PM.webm
Map when lidar frame is rotating with robot
Tf tree
frames_2024-05-26_00.17.45.pdf

It's not clear to me that this is a bug in Rviz.
I think it'd be better to ask this question on the Robotics Stack Exchange.


Notify command joins user tags with extra comma

Describe the bug
Each message with user tags will always end with a comma. It should look a bit more polished if that's not the case.
To Reproduce
Steps to reproduce the behavior:

Run a notify command with people subbed to that list

Expected behavior
No trailing comma

Wasn't this fixed by #98 ?

Wasn't this fixed by #98 ?


Move away from wille/osutil

Note: the opensuse test failures are not a regression; these are failing on the master branch as well.


refactor!: component addresses are indexed

Description

Changed the component addresses to be composed of template addresses + index
Added a new field new_component_outputs in transactions, with the addresses for the new components that are going to be created:

If multiple components are going to be created for the same template in the same transaction, only the first new output is required to be specified.
Updated all clients and CLI applications to include this new field

The IdProvider scans the incoming transaction for the new_component_outputs field, so the engine calls that create new components will use those addresses.

Motivation and Context
We want the component addresses to be deterministic and also be able to list all components of an specific template. For that, the new component address schema needs to be H(template_address || index), were index is an incremental u64
How Has This Been Tested?
The existing unit and integration tests pass
What process can a PR reviewer use to test or verify this change?
Submit a transaction that creates a new component, specifying the address in the new_component_outputs field
Breaking Changes

[ ] None
[ ] Requires data directory to be deleted
[x] Other - Needs full Tari network reset, as the component addresses are now completely different

Abandoned as the new approach for component addresses is to be composed of template_address + user defined id (https://github.com/tari-project/tari-dan/pull/489)


[BUG] remotedialer peer connections break with many downstream clusters

Rancher Server Setup

Rancher version: 2.7.9 with cherry picked changes from https://github.com/rancher/rancher/pull/43582
Installation option (Docker install/Helm Chart): Helm / EKS

Information about the Cluster

Kubernetes version: v1.23.17-eks-508b6b3

Describe the bug
On a setup with many downstream clusters (~3800) many of them do not become active (.state field from /v3/clusters) and are hardly reachable with kubectl (/k8s/clusters/c-ID).
With the remotedialer metrics (session_server_total_*_websocket_session) we see that there is a connection to the downstream clusters.
In the logs most of the errors are failed to start cluster controllers errors. The majority of these are caused by some sort of timeout or by cluster agent disconnected error (probably happening during the initial sync of the controllers).
We scaled Rancher from three nodes to a single instance as we suspect that the peer connections of remotedialer are unable to handle this amount of connections/data.
This solved the problem with the connectivity to the downstream clusters and after a longer period of time (~1h) all running downstream clusters became active.
But now our single instance is barely able to handle the load and frequently restarts. Even though we have a node with 192 cores. And of course it is not really a solution to run Rancher only with a single pod in the long run.
To Reproduce
We only observed this in a production environment and weren't able to reproduce this yet.
What is probably required are a lot of downstream clusters (~3.8k). Not exactly sure where this starts to become a problem.
And maybe you also need a slow connections to the downstream clusters. But this is not entirely sure.
Result
Downstream clusters are not active and hardly reachable.
Expected Result
All online downstream clusters become active and are reachable with multiple running rancher pods.
Additional context
In our setup downstream clusters are imported K3S clusters running in edge locations. These are connect over the internet to the rancher instance.
A number of clusters (~500) are always offline for longer periods of time (days, weeks).
We suspect that the problem could be caused by:

Lock contention in the peer logic of remotedialer which becomes a problem with this amount of clients (downstream clusters)
Some potentially slower internet connections of downstream clusters which are maybe causing backpressure on the remotedialer peer connections

One of the indicators which made us aware of potential problems in the remotedialer peer connections was the metric session_server_total_peer_ws_connected which sometimes was growing constantly (constant reconnects).

@dvob Is there anything at all in the rancher logs that gives any indication of errors?

@bigkevmcd in the logs there are tons of errors. Around 90% of them are failed to start cluster controllers (code) errors. Of theses failed to start cluster controllers errors the majority is caused by some sort of timeout or by cluster agent disconnected error:

Timeout

29% Get "https://REDACTED:443/api/v1/namespaces/kube-system?timeout=45s": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
22% Get "https://REDACTED:443/api/v1/namespaces/kube-system?timeout=45s": net/http: TLS handshake timeout
7% Get "https://REDACTED:443/api/v1/namespaces/kube-system?timeout=45s": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
7% Get "https://REDACTED:443/api/v1/namespaces/kube-system?timeout=45s": context deadline exceeded
...

27% cluster agent disconnected

As mentioned this is likely because remotedialer system is completely overloaded/broken and the initial request to the downstream clusters to their kube-system namespace fails (code). This probably happens either because the remotedialer connections are too slow (timeout) or the clients (downstream clusters) are not properly distributed via the remotedialer peer system (cluster agent disconnected).

In the logs most of the errors are failed to start cluster controllers errors.

jfyi @aruiz14

@moio Thank you for the response. Unfortunately we have only 10 days of metrics and we switched to a single pod more then 10 days ago. I check if we can switch back to 3 replicas during off-peak hours and then I can report metrics from this setup (memory, number of goroutines, ...?).
Also I check if we can use the remotedialer fix in our rancher build as soon as it is ready.
We observed another strange thing this morning which is maybe related to the remotedialer bug.
We tried to write a query to get the number of connected clients (>0 active sessions).
First this was harder than we thought, because you can't just do the following as this only returns clients which already have at least one removed session:
session_server_total_add_websocket_session - session_server_total_remove_websocket_session

Then we used this which for one client returnd -1 which shouldn't be  the case?
session_server_total_add_websocket_session - (session_server_total_remove_websocket_session or (session_server_total_add_websocket_session * 0))

How is memory consumption going when this phenomenon happens?

@moio We ran rancher with 4 replicas for 7 hours during off-peak hours. For two of the pods the goroutine count went up steadily. For one pod it went to 3.6m go routines until we switched back to a single pod.

With 4 replicas of the 3.3k connected clusters (session_server metric) the number of active clusters stalled after 3h at around 1.3k clusters.
Currently with a single node it takes around 2h until all clusters (3.3k) become active (also see https://github.com/rancher/rancher/issues/45164).

I cannot tell without a goroutine profile, but it sure looks a lot like the symptoms we've seen in those remotedialer issues mentioned upthread.
So first of all I would recommend trying with https://github.com/rancher/remotedialer/pull/74 then seeing if goroutines look better (definitely expected) and CPU usage looks better (possible). Then continue from there.
JFYI: the PR is currently being reviewed from our engineers.


bug: Popup overlay click causes modal to close.

Type: bug
Platform: all
When using a modal, and then opening a popup (for an alert or something), clicking on the overlay causes the modal to close.
Example here using code from the docs site: http://codepen.io/elebetsamer/pen/swnzr

Thanks a lot i have same problem and wondering how to solve it . it was fantastic guys.

tx

still a solid fix all these years later drewrygh. I had an alert that popped up over a modal, then if you pushed to close the alert and immediately click the screen again the modal would close. If I just added
$scope.modal['backdropClickToClose'] = false;   $scope.modal['hardwareBackButtonClose'] = false;
The issue went away.


Upgrade to Rails 4.2.1

Upgrade Rails to 4.2.1

This is ready for review now.

@dsingleton @evilstreak @tekin @benilovj anyone feeling to take the challenge? :trollface:

:+1: Looks good to me

This all looks ok to me. :+1:

Okay, this is going to be QAed. Thank you for reviewing it!

Looking at this from a SA-specific angle, looks good :+1:

@tadast added two extra commits to the list of the ones you've already reviewed. Would you mind taking a look? @dsingleton @boffbowsh

Looks ok to me :+1:

QA process did not find any issues. I'm away Fri and Mon so will merge and deploy this on Tuesday
:shipit:
Thanks for reviewing all :star:

:+1: :fireworks:


Implement AVX xsave/xstor to avoid workaround when checkpointing

Describe the bug
The AVX / YMM register state is not saved or restored in gem5 with the X86KvmCPU leading to crashes on checkpoint restoration when AVX is enabled in CPUID.
Affects version
develop @ 141b06d335
gem5 Modifications
No modification
To Reproduce
This is easiest to reproduce using a full system GPU configuration as it enables AVX be default and supports checkpoint/restore.  This requires the VEGA_X86 build. The application doesn't really matter here, so for the application one can simply use a blank shell script.

scons build/VEGA_X86/gem5.opt -j
touch hello.sh
build/VEGA_X86/gem5.opt configs/example/gpufs/vega10_kvm.py --disk-image x86-gpu-fs-20220512.img --kernel vmlinux-5.4.0-105-generic  --gpu-mmio-trace gem5-resources/src/gpu-fs/vega_mmio.log --app hello.sh --checkpoint-dir hello_cpt
build/VEGA_X86/gem5.opt configs/example/gpufs/vega10_kvm.py --disk-image x86-gpu-fs-20220512.img --kernel vmlinux-5.4.0-105-generic  --gpu-mmio-trace gem5-resources/src/gpu-fs/vega_mmio.log --app hello.sh --restore-dir hello_cpt

Terminal Output
If applicable, add the terminal output here. If long, only include the relevant lines.
Please put the terminal output in code blocks. I.e.:

[    8.736510] ------------[ cut here ]------------
[    8.736510] Bad FPU state detected at switch_fpu_return+0x7d/0x120, reinitializing FPU registers.
[    8.736510] WARNING: CPU: 0 PID: 461 at /build/linux-hwe-5.4-utjlqf/linux-hwe-5.4-5.4.0/arch/x86/mm/extable.c:114 ex_handler_fprestore+0x65/0x70
[    8.736510] Modules linked in: ib_uverbs ib_core amdgpu(OE) amd_iommu_v2 amd_sched(OE) amdttm(OE) amdkcl(OE) drm_kms_helper drm i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt pata_acpi input_leds mac_hid edac_mce_amd serio_raw sch_fq_codel ip_tables x_tables autofs4
[    8.736510] CPU: 0 PID: 461 Comm: check-new-relea Tainted: G           OE     5.4.0-105-generic #119~18.04.1-Ubuntu
[    8.736510] Hardware name:  , BIOS  06/08/2008
[    8.736510] RIP: 0010:ex_handler_fprestore+0x65/0x70
[    8.736510] Code: 00 00 00 5d c3 48 0f ae 0d 78 30 bc 01 b8 01 00 00 00 5d c3 48 89 c6 48 c7 c7 20 87 34 82 c6 05 80 97 b8 01 01 e8 1b ea 01 00 <0f> 0b eb b9 0f 1f 80 00 00 00 00 66 66 66 66 90 55 48 89 e5 e8 e2
[    8.736510] RSP: 0018:ffffc9000042fde0 EFLAGS: 00010086
[    8.736510] RAX:<PHONE_NUMBER>000000 RBX: ffffc9000042fe48 RCX:<PHONE_NUMBER>000000
[    8.736510] RDX:<PHONE_NUMBER>000005 RSI: ffffffff82f965f5 RDI:<PHONE_NUMBER>000046
[    8.736510] RBP: ffffc9000042fde0 R08: ffffffff82f965a0 R09:<PHONE_NUMBER>000055
[    8.736510] R10:<PHONE_NUMBER>000000 R11:<PHONE_NUMBER>0001cd R12:<PHONE_NUMBER>00000d
[    8.736510] R13:<PHONE_NUMBER>000000 R14:<PHONE_NUMBER>000000 R15:<PHONE_NUMBER>000000
[    8.736510] FS:  00007f4cdc05b740(0000) GS:ffff8880bca00000(0000) knlGS:0000000000000000
[    8.736510] CS:  0010 DS: 0000 ES: 0000 CR0:<PHONE_NUMBER>050033
[    8.736510] CR2:<PHONE_NUMBER>4e5ef0 CR3: 00000000b8f9a000 CR4:<PHONE_NUMBER>0406f0
[    8.736510] Call Trace:
[    8.736510]  fixup_exception+0x4a/0x60
[    8.736510]  do_general_protection+0x4e/0x150
[    8.736510]  general_protection+0x28/0x30
[    8.736510] RIP: 0010:switch_fpu_return+0x7d/0x120
[    8.736510] Code: 74 67 49 8d bc 24 00 14 00 00 48 89 7d d0 66 66 90 66 90 db e2 0f 77 db 45 d0 66 66 90 66 90 b8 ff ff ff ff 89 c2 48 0f c7 1f <65> 4c 89 2d 0b d7 fd 7e 66 66 66 66 90 45 89 b4 24 c0 13 00 00 65
[    8.736510] RSP: 0018:ffffc9000042fef8 EFLAGS: 00010086
[    8.736510] RAX: 00000000ffffffff RBX: ffff8880b8190000 RCX:<PHONE_NUMBER>0004dd
[    8.736510] RDX: 00000000ffffffff RSI: 7133cdb5d72e6598 RDI: ffff8880b8191400
[    8.736510] RBP: ffffc9000042ff28 R08:<PHONE_NUMBER>000068 R09:<PHONE_NUMBER>000001
[    8.736510] R10:<PHONE_NUMBER>000068 R11:<PHONE_NUMBER>00ba5a R12: ffff8880b8190000
[    8.736510] R13: ffff8880b81913c0 R14:<PHONE_NUMBER>000000 R15:<PHONE_NUMBER>000000
[    8.736510]  ? schedule+0x33/0xa0
[    8.736510]  prepare_exit_to_usermode+0x98/0xa0
[    8.736510]  retint_user+0x8/0x8
[    8.736510] RIP: 0033:0x7f4cd9d7cbf5
[    8.736510] Code: 49 8b b7 80 00 00 00 4c 89 7c 24 48 c7 44 24 50 00 00 00 00 48 8d 04 80 48 8d 04 86 48 85 c0 48 89 44 24 40 0f 84 91 00 00 00 <8b> 10 48 c1 e2 04 49 03 97 88 00 00 00 48 39 c6 48 89 54 24 58 74
[    8.736510] RSP: 002b:00007fffb0954620 EFLAGS: 00000206 ORIG_RAX: ffffffffffffff13
[    8.736510] RAX: 00007f4cd3f2980c RBX: 00007fffb0954640 RCX: 00007f4cd2fe8000
[    8.736510] RDX:<PHONE_NUMBER>001281 RSI: 00007f4cd2fe8000 RDI:<PHONE_NUMBER>1b7f83
[    8.736510] RBP: 00007f4cd1ca850e R08: 00007f4cd30762fd R09: 00007f4cd9d62e00
[    8.736510] R10:<PHONE_NUMBER>34bcf0 R11: 00007f4cdbc0eb20 R12: 00007fffb0954660
[    8.736510] R13:<PHONE_NUMBER>60c4b0 R14: 00007f4cd3f1b4a0 R15:<PHONE_NUMBER>34bcf0
[    8.736510] ---[ end trace b5790e806846cb11 ]---

Expected behavior
There should be no kernel backtrace dumps.
Host Operating System
Ubuntu 20.04
Host ISA
amd64
Compiler used
gcc 9.4.0
Additional information

Likely need to implement the AVX xsave/xrstor support documented in Intel SDM value 1, chapter 13.5.3: https://www.intel.com/content/www/us/en/developer/articles/technical/intel-sdm.html
There are other "optimized" xsave variants such as xsaveopt, xsavec, xsaves. It might be easier to focus on the basic xsave version. The other variants will have to be disabled by modifying configs/example/gpufs/system/system.py and changing line 250 (the second EAX value of CPUID.0Dh) from 0x000000F to 0x0.
The following website is useful for seeing the kernel code. The printk error is here:  https://elixir.bootlin.com/linux/v5.4/source/arch/x86/include/asm/fpu/internal.h#L265
Called from here: https://elixir.bootlin.com/linux/v5.4/source/arch/x86/include/asm/fpu/internal.h#L343 ... etc.

Manual "backtrace" from Linux KVM call:
https://elixir.bootlin.com/linux/v5.4/source/arch/x86/kvm/x86.c#L3442
https://elixir.bootlin.com/linux/v5.4/source/arch/x86/kernel/fpu/core.c#L338
https://elixir.bootlin.com/linux/v5.4/source/arch/x86/include/asm/fpu/internal.h#L534
https://elixir.bootlin.com/linux/v5.4/source/arch/x86/include/asm/fpu/internal.h#L457
https://elixir.bootlin.com/linux/v5.4/source/arch/x86/include/asm/fpu/internal.h#L445
https://elixir.bootlin.com/linux/v5.4/source/arch/x86/include/asm/fpu/internal.h#L338
https://elixir.bootlin.com/linux/v5.4/source/arch/x86/include/asm/fpu/internal.h#L260
https://elixir.bootlin.com/linux/v5.4/source/arch/x86/include/asm/asm.h#L153
https://elixir.bootlin.com/linux/v5.4/source/arch/x86/mm/extable.c#L106

@abmerop : Just so I know if this is assignable or not: are you just reporting this or are you working on this fix?

Just reporting for now.  If I have time to look into this i'll self-assign

Accidentally duplicated this... Will use new ticket #958


v3.1.1(schema): update empty security array constraint

based on discussions

https://github.com/OAI/OpenAPI-Specification/issues/3938#issuecomment-2308874884

https://github.com/OAI/OpenAPI-Specification/pull/4007

@jeremyfiel as with the other one this needs to go to main, but also I'm not sure why you have added this as [] is allowed.

I also commented in a slack discussion today that I believe the security requirement spec text is the only reference to an actual JSON structure where is recommends [{}] rather than only descriptive text.
https://open-api.slack.com/archives/C1137F8HF/p1725479409881939?thread_ts=1725473300.217419&cid=C1137F8HF

@jeremyfiel all of that was about defining what [] means, so that means it is a legal value and the schema cannot forbid it.

I suppose the wording To remove a top-level security declaration, an empty array can be used. contradicts the recommendation To make security optional, an empty security requirement ({}) can be included in the array.

the wording To remove a top-level security declaration, an empty array can be used. contradicts the recommendation To make security optional, an empty security requirement ({}) can be included in the array.

No.
The top-level declaration in the OpenAPI Object is the default applying to all operations, and this may state "no authentication required" by including {} in the array.
An operation can opt out of this default in two ways:

with a non-empty array listing all mechanisms this operation supports
with an empty array saying "I don't tell you how to authenticate here", which probably implies that unauthenticated access allowed by the top-level default will probably not work

Should we need to elaborate this in the specification text?

There are some problems with this pull request, but having discussed the proposed change (the newest commit), this isn't a useful change to make to our existing validation schemas since it is valid to have an empty security array. Please keep an eye on the project for more discussion about linting schemas in addition to our validation schemas.


'Specify IP Address' section description is not clear

If you would like to use a specific IP address with the internal load balancer, add the loadBalancerIP property to the load balancer YAML manifest. In this scenario, the specified IP address must reside in the same subnet as the AKS cluster but can't already be assigned to a resource. For example, an IP address in the range designated for the Kubernetes subnet within the AKS cluster shouldn't be used.

There's no clarity over the last sentence in the description.
By following the requirement specified IP address must reside in the same subnet as the AKS cluster we can choose an arbitrary free IP address from the subnet. The last sentence guides us that IP address in the range designated for the Kubernetes subnet within the AKS cluster shouldn't be used.
What does Kubernetes subnet within the AKS cluster mean? Is it equivalent to Kubernetes service address range / Service CIDR? If it is, then what is the rationale for having it right after specified IP address must reside in the same subnet as the AKS cluster?
If it isn't, then what does it mean? Is there anything else that should be taken into consideration?

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

ID: 25afcc19-0998-3583-f6d8-e2a619c0e071
Version Independent ID: 7629191a-6b3b-fb22-8b70-fa84fd785f38
Content: Create an internal load balancer - Azure Kubernetes Service
Content Source: articles/aks/internal-lb.md
Service: container-service
GitHub Login: @zr-msft
Microsoft Alias: zarhoads

@serhii-kapchynskyi-at-cantire Thank you for your feedback!  We've assigned this to the document author for further review.

Thank you @serhii-kapchynskyi-at-cantire for the feedback!
We've added an item to our backlog and will prioritize accordingly.
#please-close


Fix pipe errors (141, etc.)

Fixed by https://github.com/karel-brinda/samsift/commit/092484ba93c955d30e92da9d76fa53015bd437f9


Create sample communcation between frontend and backend

Reopened because of new worklfow for closing issues during sprint review

Closed during Sprint Review 1


Documentation update

What is the expected enhancement?
Update the documentation relative to new src-layout.

The IEEE notebook and install directions need to be updated relative to this src-layout change.


bugfix: redeploy api when a function name changes

Issue #, if available:
Description of changes:
Description of how you validated changes:
Checklist:

[ ] Write/update tests
[x] make pr passes
[ ] Update documentation
[ ] Verify transformed template deploys and application functions as expected
[ ] Add/update example to examples/2016-10-31

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #1134 into develop will decrease coverage by 0.03%.
The diff coverage is 88.23%.

@@             Coverage Diff             @@
##           develop    #1134      +/-   ##
===========================================
- Coverage     94.8%   94.76%   -0.04%
===========================================
  Files           71       71
  Lines         3486     3498      +12
  Branches       680      683       +3
===========================================
+ Hits          3305     3315      +10
- Misses          93       94       +1
- Partials        88       89       +1

Impacted Files
Coverage Δ

samtranslator/model/sam_resources.py
95.51% <100%> (+0.01%)
:arrow_up:

samtranslator/translator/translator.py
99.08% <100%> (+0.08%)
:arrow_up:

samtranslator/model/api/api_generator.py
96.71% <100%> (ø)
:arrow_up:

samtranslator/model/apigateway.py
96.72% <33.33%> (-1.07%)
:arrow_down:

Continue to review full report at Codecov.

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


Allow users to easily define LS_COLORS and LSCOLORS

Fixes #1539
Proposed Changes

Only set LSCOLORS and LS_COLORS if not already set

I'm not sure if there's a better solution, but this should allow users to define LS_COLORS and LSCOLORS while still falling back to our settings.

Sorry, it took so long to merge this. I forgot it was still open.


Java.lang.NullPointer when importing data in Version 7.0.3

<!--
Thank you for reporting an issue.

*IMPORTANT* -  *before* creating a new issue please look around:
 - DBeaver documentation: https://github.com/dbeaver/dbeaver/wiki
 and
 - open issues in Github tracker: https://github.com/dbeaver/dbeaver/issues

If you cannot find a similar problem, then create a new issue. Short tips about new issues can be found here: https://github.com/dbeaver/dbeaver/wiki/Posting-issues

Please, do not create issue duplicates. If you find the same or similar issue, just add a comment or vote for this feature. It helps us to track the most popular requests and fix them faster.

when importing CSV data using version 7.0.3, the java.lang.NullPointer occurs

It works well in 7.0.1

DBeaver version: 7.0.3
OS : Linux
when importing data from CSV to MySQL database, the Java.lang.NullPointer occurs. It worked well in Version 7.0.1.

seems to be duplicate of #8520
tickeet will be close das duplicate.
Anyway, thanks for the bug report


No UVC backend selected. Please #define exactly one of RS2_USE_LIBUVC_BACKEND, RS2_USE_WMF_BACKEND, or RS2_USE_V4L2_BACKEND

when I try to install librealsense SDK 2 with python,
the ditctory is  ../wrapper/python
I have followed the guides  which says
mkdir build
cd build
cmake ../ -DBUILD_PYTHON_BINDINGS=bool:true

make -j4                                 <----error occurs
sudo make install

error:No UVC backend selected. Please #define exactly one of RS2_USE_LIBUVC_BACKEND, RS2_USE_WMF_BACKEND, or RS2_USE_V4L2_BACKEND
After I have checked the ../librealsense/src/backend.cpp file,
It seems if I install libusb-1.0 or libuvc may be useful , but it's failed to solve the error.
Thank you for your time.

OK  I have solve the problem:
the problem occurs when I run “cmake -D。。。。” under the path which is "wrapper/python/build",
but  it's incorrect at all,
the guides says like this：
“Run the top level CMake command with the following additional flag -DBUILD_PYTHON_BINDINGS=bool:true:”
SO，I should run cmake under the /librealsense/build and pass the flag -DBUILD_PYTHON_BINDINGS=bool:true
rather than under the /librealsense/wrapper/python/build.
Check your path clearly.

Hi @xufeifeiWHU
Sorry for the confusion but glad you figured it out. Feel free to suggest modifications to the guide via a pull-request.

[Realsense Customer Engineering Team Comment]
Hi @xufeifeiWHU ,
Glad you figured out your problem.  We will close this request and please open a new one if you have any other issues.

Hi, I have a problem with the installation of the pyrealsense2 package for python.
I make the librealsense construction with the appopriate flag, and everything work, but when I want to use it in python:
import pyrealsense2
or
import pyrealsense
I got: "no module named .."
Do you have any suggestion?
I'm on the Jetson TX2 and the camera is the D435 RealsSense.
Thanks in advance
C. Chappey

You can review the instructions:
https://github.com/IntelRealSense/librealsense/tree/master/wrappers/python