docker_installation_package fails to install 18.06.0.ce-3.el7 on centos 7

Cookbook version
4.4.1
Chef-client version
13.10.0
Platform Details
Centos 7.4
Scenario:
when only the version property is passed into this resource for 18.06.0.ce-3.el7, package_version is determined by #version_string in the resource. This fails to install the correct version, because https://github.com/chef-cookbooks/docker/blob/master/libraries/docker_installation_package.rb#L157 hardcodes the trailing part of the version string.
Steps to Reproduce:
The yum repo is configured by the chef-yum-docker cookbook in our scenario.
docker_installation_package 'docker-ce' do
  setup_docker_repo false
  version 18.06.0
end

Expected Result:
This is a bit tricky, in that one would never know ahead of time what series in the release of the specified version is available. The 18.06.0.ce-1 version doesn't seem to exist in the yum repo anymore, so it would need to look at all available versions of that series and pick one (maybe the latest).
Actual Result:
           ================================================================================
           Error executing action `create` on resource 'docker_installation_package[docker-ce]'
           ================================================================================

           Chef::Exceptions::Package
           -------------------------
           yum_package[docker-ce] (/tmp/kitchen/cache/cookbooks/docker/libraries/docker_installation_package.rb line 42) had an error: Chef::Exceptions::Package: Version ["18.06.0.ce-1.el7.centos"] of ["docker-ce"] not found. Did you specify both version and release? (version-release, e.g. 1.84-10.fc6)

           Resource Declaration:
           ---------------------
           # In /tmp/kitchen/cache/cookbooks/my_docker/recipes/docker.rb

            76: docker_installation_package node['my_docker']['docker']['package_name'] do
            77:   setup_docker_repo false
            78:   # package_version node['my_docker']['docker']['package_version']
            79:   version node['my_docker']['docker']['version']
            80: end
            81:

           Compiled Resource:
           ------------------
           # Declared in /tmp/kitchen/cache/cookbooks/my_docker/recipes/docker.rb:76:in `from_file'

           docker_installation_package("docker-ce") do
             action [:create]
             default_guard_interpreter :default
             declared_type :docker_installation_package
             cookbook_name "my_docker"
             recipe_name "docker"
             version "18.06.0"
             package_name "docker-ce"
             package_version "18.06.0.ce-1.el7.centos"
           end

Workaround
instead of using the version property, use the package_version property and be very specific about it, such as:
docker_installation_package 'docker-ce' do
  setup_docker_repo false
  package_version '18.06.0.ce-3.el7'
end

I'm not sure why there needs to be two properties indicating version. Can we settle on version, since that is how the package resource works.

I ran into this issue as well with Ubuntu, it was something to do with the number 3 in the package name: 18.06.0~ce~3-0~ubuntu. I wanted to lock my wrapper cookbook to a specific version of docker-ce, versus it always updating it when run.


Error when generating sample from copula

There is something going on with the interpolation.
using BivariateCopulas
using Random

Random.seed!(123)

τ = 10
K = Clayton(τ)

samplecop = rand(K, 10)
# ERROR: LoadError: knot-vectors must be unique and sorted in increasing order

If you want, I can implement another sampler for the Clayton copula:
function _clasample(n, τ)
    r = rand(n, 2)
    for i in 1:size(rng, 1)
        v = r[i, 2]
        u = r[i, 1]
        r[i, 2] = (1 - u^(-τ) + (u^(1 + τ)*v)^(-(τ/(1 + τ))))^(-1/τ)
    end
    return r
end

Then in sample in line 91 of copulas.jl we call that sampler, similar to what you already do for the Gaussian copula in line 97.

Hi, thanks for raising this issue and giving the solution!
That would be wonderful. Thanks :D


A question about the read more feature

What triggers a post to be minimized and only showing the first paragraph and not showing the full story on the front page?

If you check this template https://github.com/barryclark/jekyll-now/blob/master/index.html
---
layout: default
---

  {% for post in site.posts %}

{{ post.title }}

        {{ post.excerpt }}

      Read More

  {% endfor %}

here post.excerpt will only show first paragraph of the post content.
and Read More this will add Read More link.


Dia::IDiaSourceFile::get_checksum implementation does not work properly

I am trying to leverage the DIA SDK in rust using this crate (Thank You!).
I have been able to flawlessly use it, except for when I tried to leverage Dia::IDiaSourceFile::get_checksum(...).  I was unable to find any variation that allowed that API to work properly.
I ended up using something like:
let mut checksum = Vec::<u8>::new();
unsafe {
    // Get the size of the checksum buffer
    let mut cbdata = 0;
    (windows::core::Interface::vtable(&self.source_file).get_checksum)(
        windows::core::Interface::as_raw(&self.source_file),
        0,
        &mut cbdata,
        std::ptr::null_mut()).unwrap();

    // Create a buffer to hold the checksum
    checksum.resize(cbdata as usize, 0);

    // Retrieve the checksum into the buffer
    (windows::core::Interface::vtable(&self.source_file).get_checksum)(
        windows::core::Interface::as_raw(&self.source_file),
        cbdata,
        &mut cbdata,
        checksum.as_mut_ptr()).unwrap();
}

To workaround the issue.
I saw that this method was implemented by windows-bindgen and I was curious if this is a bug, or if it would be worthwhile to investigate this issue for bindgen?
Thank you again for all of this great work!

Hey @JeromySt, here's a sample. It's slightly inefficient; it allocates a 256 byte buffer up front, due to get_checksum not accepting a null pbdata. (This is a crate metadata issue, this method parameter isn't marked as [Optional]. I'll get this fixed.)
[package]
name = "sample_checksum"
version = "0.1.0"
edition = "2021"
publish = false

[dependencies.windows]
version = "0.53"
features = [
    "implement",
    "Win32_Foundation",
    "Win32_System_Com",
    "Win32_System_LibraryLoader",
    "Win32_System_Com_StructuredStorage",
    "Win32_System_Ole"
]

[dependencies.microsoft-dia]
version = "0.10.0"

use microsoft_dia::{nsNone, DiaSource, IDiaDataSource, SymTagCompiland};
use windows::{
    core::*,
    Win32::System::Com::{CoInitializeEx, COINIT_MULTITHREADED},
};

fn main() -> Result<()> {
    unsafe {
        // Initialize COM and DIA
        CoInitializeEx(None, COINIT_MULTITHREADED).ok()?;
        let source: IDiaDataSource = microsoft_dia::helpers::NoRegCoCreate(
            s!(
                r#"C:\Program Files\Microsoft Visual Studio\2022\Enterprise\DIA SDK\bin\amd64\msdia140.dll"#
            ),
            &DiaSource,
        )?;

        // Open session against own symbols
        let executable = std::env::current_exe().unwrap();
        source.loadDataForExe(&HSTRING::from(executable.as_os_str()), None, None)?;
        let session = source.openSession()?;

        // Get compilands
        let symbols =
            session
                .globalScope()?
                .findChildren(SymTagCompiland, None, nsNone.0 as u32)?;

        // Get source files
        for i in 0..symbols.Count()? {
            let symbol = symbols.Item(i as u32)?;
            let files = session.findFile(&symbol, PCWSTR::null(), nsNone.0 as u32)?;

            // Find files with a checksum and print out details
            for j in 0..files.Count()? {
                let file = files.Item(j as u32)?;
                if file.checksumType()? == 0 {
                    continue;
                }

                let mut byte_count = 0u32;
                let mut bytes = vec![0; 256];
                file.get_checksum(&mut byte_count, &mut bytes)?;
                bytes.set_len(byte_count as usize);

                println!("File: {}", file.fileName()?);
                println!(
                    "{:02x}: {}\n",
                    file.checksumType()?,
                    bytes
                        .iter()
                        .map(|b| format!("{:02x}", b).to_string())
                        .collect::<String>()
                );
            }
        }

        Ok(())
    }
}

Thank you for the example!
Quite helpful.  I was iterating over quite a few different methods (new to Rust, so sorry about the simple questions), but could not get Vec::u8::new() to do the same thing that you just did with vec![0; 256].  Trying to figure out how to get a &mut [u8] from Vec was driving me up a wall, but I also was trying to use the API, like I did from C#.
I leveraged your example below and all seems in order.
I will close the issue, unless you'd like to use it to track the missing [Optional] metadata issue.
tx
Jeromy Statia

From: Rafael Rivera @.>
Sent: Tuesday, March 26, 2024 8:26 PM
To: microsoft/dia-rs @.>
Cc: Mention @.>; Author @.>
Subject: Re: [microsoft/dia-rs] Dia::IDiaSourceFile::get_checksum implementation does not work properly (Issue #18)
Hey @JeromySthttps://github.com/JeromySt, here's a sample. It's slightly inefficient; it allocates a 256 byte buffer up front, due to get_checksum not accepting a null pbdata. (This is a crate metadata issue, this method parameter isn't marked as [Optional]. I'll get this fixed.)
[package]
name = "sample_checksum"
version = "0.1.0"
edition = "2021"
publish = false
[dependencies.windows]
version = "0.53"
features = [
"implement",
"Win32_Foundation",
"Win32_System_Com",
"Win32_System_LibraryLoader",
"Win32_System_Com_StructuredStorage",
"Win32_System_Ole"
]
[dependencies.microsoft-dia]
version = "0.10.0"
use microsoft_dia::{nsNone, DiaSource, IDiaDataSource, SymTagCompiland};
use windows::{
core::*,
Win32::System::Com::{CoInitializeEx, COINIT_MULTITHREADED},
};
fn main() -> Result<()> {
unsafe {
// Initialize COM and DIA
CoInitializeEx(None, COINIT_MULTITHREADED).ok()?;
let source: IDiaDataSource = microsoft_dia::helpers::NoRegCoCreate(
s!(
r#"C:\Program Files\Microsoft Visual Studio\2022\Enterprise\DIA SDK\bin\amd64\msdia140.dll"#
),
&DiaSource,
)?;
    // Open session against own symbols
    let executable = std::env::current_exe().unwrap();
    source.loadDataForExe(&HSTRING::from(executable.as_os_str()), None, None)?;
    let session = source.openSession()?;

    // Get compilands
    let symbols =
        session
            .globalScope()?
            .findChildren(SymTagCompiland, None, nsNone.0 as u32)?;

    // Get source files
    for i in 0..symbols.Count()? {
        let symbol = symbols.Item(i as u32)?;
        let files = session.findFile(&symbol, PCWSTR::null(), nsNone.0 as u32)?;

        // Find files with a checksum and print out details
        for j in 0..files.Count()? {
            let file = files.Item(j as u32)?;
            if file.checksumType()? == 0 {
                continue;
            }

            let mut byte_count = 0u32;
            let mut bytes = vec![0; 256];
            file.get_checksum(&mut byte_count, &mut bytes)?;
            bytes.set_len(byte_count as usize);

            println!("File: {}", file.fileName()?);
            println!(
                "{:02x}: {}\n",
                file.checksumType()?,
                bytes
                    .iter()
                    .map(|b| format!("{:02x}", b).to_string())
                    .collect::<String>()
            );
        }
    }

    Ok(())
}

}
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/dia-rs/issues/18#issuecomment-2021855508 or unsubscribehttps://github.com/notifications/unsubscribe-auth/AC7XYFPH2RQBJLNLKT4YVGLY2I36VBFKMF2HI4TJMJ2XIZLTSOBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLLDTOVRGUZLDORPXI6LQMWWES43TOVSUG33NNVSW45FGORXXA2LDOOJIFJDUPFYGLKTSMVYG643JORXXE6NFOZQWY5LFVE2DEOJVGA4TKMZUQKSHI6LQMWSWS43TOVS2K5TBNR2WLKRSGIYDSNBTGY3TSNNHORZGSZ3HMVZKMY3SMVQXIZI.
You are receiving this email because you were mentioned.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Constants: Set Pulse Input Ratio

I think these should be called Pulse1, Pulse2 and Pulse3, not Ln1, etc.

Per conversation changing to Pulse.In1, Pulse.In2...

Change described above complete closing


Fixed anchor link hover effect design issue

Reference Issue: https://github.com/develodesign/vsf-wp/issues/29
Fixed anchor link hover effect behaviour
Before fix:

After fix:

Thank you.

Thank you


Fix DG features sequence diagrams

Modified the sequence diagrams, added logging statements. Closes #224.
This PR does not include (as of latest commit):

any changes to activity diagrams

This PR includes:

logging
DG sequence diagrams
changes to DG implementation content for add, addnote, find

@jiahui0309 why do the XYZCommandParser have crosses for object deletion but some of the other things (like the XYZCommand objects) do not? Should we add object deletions for the XYZCommand too after r is returned?

@drustanyjt okay! initially i was following the diagram they provided, but it seems reasonable to delete the obj after returning the result


Fix getLastBackup

Fixes #378

Pull Request Test Coverage Report for Build 1687

9 of 9 (100.0%)  changed or added relevant lines in 2 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.02%) to 88.222%

Files with Coverage Reduction
New Missed Lines
%

broker/lib/fabrik/DBManager.js
1
98.86%

Totals

Change from base Build 1686:
-0.02%

Covered Lines:
8194

Relevant Lines:
9006

💛  - Coveralls


Build the /forecast endpoint

We need a forecast endpoint that takes the following parameters:

station: the station id.
object: the forecast object, either dock or bike.
minutes: an integer with the number of minutes to forecast.

object has to be a specific variable. The available forecasting variables are:

docksAvailableRatio: ratio of docks available
bikesAvailableRatio: ratio of bikes available
docksAvailable: number of docks available
bikesAvailable: number of bikes available


[WIP] refactor: atoms

Related issue
Closes #1322
Waiting for new SfDropdown
Scope of work
Atoms with new design

Excellent work. I found few bugs, but they are not necessarly connected with what you made in these issue:

SfButton as link in storybook doesn't change to link so it should be changed in vue file and in also disabled state should be prepared for it, I'll prepare fix fot that,
SfCircleIcon - there is version of that component for mobile marked as "MOBILE ADD TO CART BUTTON" with changed size to 66px, so I wonder if it should be changed only for these type of icon all in generall, wdyt?
SfColor - there is no boreder for white color picker so when it is on white background it is not visible, there should be some prop to set border for certain color dependaing on current background.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: AdamPawlinski:x: justyna-13You have signed the CLA already but the status is still pending? Let us recheck it.


Calling BlockPos.stream(BlockPos Start, BlockPos End) and using a forEach loop that copies the elements into a list or array makes previous elements in that list/array return previous elements.

Not to sure that this is a yarn thing or not or a bug within Minecraft itself or with yarn, but I feel like its yarn that is causing the issue so here's my hot take on this:
So the title should explain it all, might mind boggle some people on what I'm talking about. Feel free to change the title if my keywording is inaccurate.
So, we need placeholder code for a little bit of context.
        BlockPos[] someArray = new Blockpos[64];
        Stream<BlockPos> someBlockPosStream = BlockPos.stream(someBlockPos, someOtherBlockPos);
        AtomicInteger i = new AtomicInteger();
        boardStream.forEach(e -> {
            someArray[i] = e;
            System.out.println(Arrays.deepToString(someArray));
            i.getAndIncrement();
        });

This code with the system.out.println is Expected to return the following output (if you used (new BlockPos(-5, 66, -5), new BlockPos(-12, 66, -12)) as your input):
[class_2339{x=-12, y=66, z=-12}, null, null, null, null, null, null, null]
[class_2339{x=-12, y=66, z=-12}, class_2339{x=-11, y=66, z=-12}, null, null, null, null, null, null]
[class_2339{x=-12, y=66, z=-12}, class_2339{x=-11, y=66, z=-12}, class_2339{x=-10, y=66, z=-12}, null, null, null, null, null]
this goes on until all of the BlockPos positions from the stream has been copied.

But instead returns this
[class_2339{x=-12, y=66, z=-12}, null, null, null, null, null, null, null]
[class_2339{x=-11, y=66, z=-12}, class_2339{x=-11, y=66, z=-12}, null, null, null, null, null, null]
[class_2339{x=-10, y=66, z=-12}, class_2339{x=-10, y=66, z=-12}, class_2339{x=-10, y=66, z=-12}, null, null, null, null, null]
...

Im not exactly why this is happening, but seems to be an issue with blockpos itself
my yarn mappings is 1.19.2+build.8 if anything helps.
A workarround i found is to use an int[x][3] matrix, using GetX() Y, and Z methods and then reconstruct the BlockPos positions from there. (x is how many BlockPositions you want, and 3 is the blockpos itself, one for each dimension)
If theres anything else i need please let me know.

Yarn doesn't change the behaviour of game code, it just gives it human-readable names and documentation.

As Juuz said, all Yarn does is make Minecraft's code human-readable. It does not alter any functionality. This does not look like an issue that relates to Yarn.

Minecraft uses BlockPos.Mutable to optimize logic that would otherwise require large amounts of object allocation, such as iterating over a box of positions. You can get around this behavior through workarounds like the one you mentioned or by calling BlockPos#asLong.


pythonPackages.flask-jwt-extended: 3.17.0 -> 3.23.0

Motivation for this change
Things done

[ ] 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 nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build python2Packages.flask-jwt-extended python3Packages.flask-jwt-extended


Delete all uuids of type blogPost or attachement

Delete those uuids:
mysql> select count(*) from uuid where discriminator in ("attachement", "blogPost");
+----------+
| count(*) |
+----------+
|      152 |
+----------+
1 row in set (0.00 sec)

(Also some tests in DB layer must be deleted afterwards)

Done in https://github.com/serlo/db-migrations/pull/206


[Bug] Could not find expected browser (chrome) locally after next start

Environment
next-api-og-image: 2.1.1
next: 11.1.2 / 12.0.4
node: 16.13.0

MacOS 12.0.1 (M1 Chip)
VS Code
Bug Description
This package works fine in dev mode when using next dev. But if I try to run next build & next start I'm getting this error when trying to access the API route:
Error: Could not find expected browser (chrome) locally. Run `npm install` to download the correct Chromium revision (901912).
    at ChromeLauncher.launch (/Users/romanzhuravlov/Documents/GitHub/next-api-og-image/example/node_modules/puppeteer-core/lib/cjs/puppeteer/node/Launcher.js:88:27)
    at async Object.apiResolver (/Users/romanzhuravlov/Documents/GitHub/next-api-og-image/example/node_modules/next/dist/server/api-utils.js:101:9)
    at async Server.handleApiRequest (/Users/romanzhuravlov/Documents/GitHub/next-api-og-image/example/node_modules/next/dist/server/next-server.js:770:9)
    at async Object.fn (/Users/romanzhuravlov/Documents/GitHub/next-api-og-image/example/node_modules/next/dist/server/next-server.js:661:37)
    at async Router.execute (/Users/romanzhuravlov/Documents/GitHub/next-api-og-image/example/node_modules/next/dist/server/router.js:205:32)
    at async Server.run (/Users/romanzhuravlov/Documents/GitHub/next-api-og-image/example/node_modules/next/dist/server/next-server.js:841:29)
    at async Server.handleRequest (/Users/romanzhuravlov/Documents/GitHub/next-api-og-image/example/node_modules/next/dist/server/next-server.js:292:20)

Tried both with my own project and examples from the repo example folder.
npm install doesn't help:

Hello, thanks for reporting this 😀 It certainly should not happen. The problem is most likely related to invalid env detection (NODE_ENV). There was similar issue before but i thought I fixed it and as far as I can remember everything was working. It seems that I missed something
I will take a look on this in my free time 😇 Thanks 👍🏻

@neg4n Hey! Do you have any estimations on when this issue will be resolved? It's a serios blocker, and I'm thinking whether to wait for the fix or try another solution

Hey @snelsi, I suggest u just downgrading next-api-og-image to the 2.0.0 version. Regarding the issue fix ETA - I think i will have free time at the weekend to inspect and fix that. Cheers!

Neither version 2.0.0 nor version 1.1.7 works for me  🤔
I'm getting the same "Could not find expected browser (chrome) locally" error

I've just checked and these versions (also the latest one) works for me. I also have the M1 chip 🤔

The following code from next-og-image worked for me.
import React from 'react'
import { renderToString } from 'react-dom/server'
import chromium from 'chrome-aws-lambda'

const getContent = () => `<html><body>Hello</body></html>`

const GenerateThumbnail = async (req: NextApiRequest, res: NextApiResponse) => {
  const html = getContent()
  const browser = await chromium.puppeteer.launch({
    args: chromium.args,
    defaultViewport: chromium.defaultViewport,
    executablePath: await chromium.executablePath,
    ignoreHTTPSErrors: true,
  })
  const page = await browser.newPage()
  await page.setContent(html)
  await page.setViewport({ width: 1200, height: 630 })
  const imageBuffer = await page.screenshot()
  await browser.close()
  res.setHeader('Content-Type', 'image/jpg')
  res.setHeader('Cache-Control', `public, immutable, no-transform, s-maxage=2592000, max-age=2592000`)
  res.send(imageBuffer)
}

export default GenerateThumbnail

Hey @snelsi, I've just inspected the issue and im afraid that the error is on your side 😕 Works flawlessly for me on my local machine + hosted remotely on Vercel
https://test-nextjs-project-ebon.vercel.app/api/ogimage?test=hello

I think you might be overcomplicating things a little bit.
Here's a couple of suggestions:

You don't need Puppeteer to send plain html in Dev inspect mode

let html =
      htmlTemplate && !reactTemplate
        ? await htmlTemplate({ ...params } as StrategyAwareParams<Strategy, StrategyDetails>)
        : renderToStaticMarkup(
            await reactTemplate({ ...params } as StrategyAwareParams<Strategy, StrategyDetails>),
          )
html =  emojify(html);

// Lauch puppeteer and get a screenshot
if (isProductionLikeMode(envMode) || !inspectHtml) {
    response.setHeader('Content-Type', contentType)
    response.setHeader('Cache-Control', cacheControl)
    response.write(await browserEnvironment.createImage(html))
}
// Send plain html
else {
  response.setHeader('Content-Type', 'text/html')
  response.write(html))
}

Hardcoding ChromiumExecutable is probably not a good idea

You can call puppeteer in chrome lambda directly. Swap

import core from 'puppeteer-core'
import chrome from 'chrome-aws-lambda'

const browser = await core.launch({
  args: chrome.args,
  executablePath: await chrome.executablePath,
  headless: chrome.headless,
})

to
import chrome from 'chrome-aws-lambda'

// Use chrome.puppeteer directly
const browser = await chrome.puppeteer.launch({
    args: chrome.args,
    defaultViewport: chrome.defaultViewport,
    executablePath: await chrome.executablePath
})

You can define isProductionLikeMode prop once as a global variable instead if calling it as a function every time. Env variables can't change after the build:

const isProductionLikeMode = process.env.NODE_ENV !== 'development'

Hey there @neg4n ! I was trying to use this library to see how it worked, but I'm unfortunately running into a very weird error. I've tried to solve this by searching it up on Google, but to no avail.
Whenever I visit the route /api/hello in my browser, I get the following message:

I downloaded the library as told to from readme.md , and copied the code given in the TailwindCSS example section. It looks like:
import { withOGImage } from 'next-api-og-image'

export default withOGImage({
  template: {
    react: ({ myQueryParam }) => `

          <link<EMAIL_ADDRESS>rel="stylesheet">

${myQueryParam}💻

    `,
  },
})

Is there anything I'm doing wrong? I'm quite new to this, and thought asking this here would help. Thank you, have a good day!

Hi @neg4n!
Sorry for the late reply. Just busy with school.
Thank you so much for your response. Installing Google Chrome worked.
However, I'm not stuck on displaying that value on the frontend, or rather how the image formation would work. Could you please help me understand? I'm sorry if this is a lot to ask, but I'm just quite new to this.
Thanks!

Related:
https://github.com/alixaxel/chrome-aws-lambda/wiki/HOWTO:-Local-Development
If you are facing the same issue, try the following workaround:
npm install puppeteer-core chrome-aws-lambda --save-prod
npm install puppeteer --save-dev

https://github.com/neg4n/next-api-og-image/releases/tag/4.2.1


Read only users for educational.

It would be useful manage read only users that will be able just to visualize the plugin results execuded by trainer.
In this way we can avoid the overload of the server to execute many time the same task. 😀

@garanews
We could implement this in two ways:

Default ReadOnly role: in this case we decide what a read only user can do and it's the same for all readonly user. eg we decide that a readonly user cannot download dump or can create bookmarks this will be valid for any member of the group.
Pro: easy to implement - Cons: low flexibility

Single permissions: we define a list of permission (see below) and we add a page to add/remove single permission to each user
Pro: high flexibility - Cons: more check need to be added

In any case must be create a list of permission, and for first option must be selected if granted or not:

create dump

launch plugin

add bookmarks

download dump

show reports [vt/maxmind/regipy]

export dump

manage plugins *

manage symbols *

manage rules *


How to make menubar dark?

I build demo using vs 2019 community and test it on win 10 (buildnumber = 19042, add it as supported).
Test result is ok for demo excerpt menubar are light , menu items are darked.
Because of we don't have 19041 env, is it same light in 19041? If yes, how to make it dark?

Because Microsoft doesn't provide a dark menu bar. The only way to make it dark is to owner draw.

I actually figured out how to custom draw the menubar even with themes enabled, using some undocumented window messages and structures, but this whole project is that so I imagine that part is not a problem. https://github.com/adzm/win32-custom-menubar-aero-theme

Also PR #17 adds this to the sample application


How to set auth proxies?

I have a set proxies without banned by PTC and a set proxies without banned by POGO.
Is it possible to set different proxies for PTC and POGO API?

To answer the title, I assume<EMAIL_ADDRESS>would work?
To answer the body, I don't know. Probably a bad idea to ping PTC and POGO with separate IPs, I'd guess.


Roundup: [oss-security] subscription-manager: CVE-2017-2663 unsafe dbus interface

Here is a report from the oss-security mailing list for Vulnerability Roundup 27.
Skip to First Email
Instructions:
Identification
Identify if we have the software, in 16.09, 17.03, and unstable. Then determine if we are vulnerable, and make a comment with your findings. It can also be helpful to specify if you think there is a patch, or if it can be fixed via a general update.
Example:
unstable: we are not vulnerable (link to the package)
17.03: we are vulnerable (link to the package)
16.09: we don't have it packaged

IMPORTANT: If you believe there are possibly related issues, bring them up on the parent issue!
Patching
Start by commenting on this issue saying you're working on a patch. This way, we don't duplicate work.
If you open a pull request, tag this issue and the master issue for the roundup.
If you commit the patch directly to a branch, please leave a comment on this issue with the branch and the commit hash, example:
fixed:

release-16.09: abc123

Skip to First Email
Upon Completion ...

[ ] Update Graham's database

Info
Triage Indicator:
-needs-triage +roundup27 thread:00000000000042fe

File Search: https://search.nix.gsc.io/?q=dbus&i=fosho&repos=nixos-nixpkgs
GitHub Search: https://github.com/NixOS/nixpkgs/search?utf8=✓&q=dbus+in%3Apath&type=Code

Should the search term be changed from dbus? Suggest a new package search by commenting:
-suggested:dbus +suggested:correctPackageName thread:00000000000042fe

Known CVEs: CVE-2017-2663

Skip to End
Tue, 21 Mar 2017 20:34:17 +0100 Cedric Buissart <cbuissar-at-redhat.com><EMAIL_ADDRESS>Hi,

CVE-2017-2663 has been assigned for the following issue :

Subscription-manager's new DBus interface provides methods that can be used
for malicious usage. It allows an unprivileged local user to have access to
information known to root only, and/or to modify subscription-manager
configuration file, allowing, for example, privilege escalation.

-> Upstream patch :
 * Lock down Facts object to be accessible to root only.
https://github.com/candlepin/subscription-manager/commit/882bb587a
-> Followed by this one :
 * 1434094: Deny D-BUS Config.Set from non-root
https://github.com/candlepin/subscription-manager/commit/afa0f7afee

Affected versions : from subscription-manager-1.19.0-1 (information
disclosure) & subscription-manager-1.19.3-1 (configuration modification)

Fixed version : subscription-manager-1.19.4-1

Thanks,

--
Cedric Buissart,
Product Security

Skip to End

unstable: unpackaged
release-16.09: unpackaged
release-17.03: unpackaged


Update docker registry to cr.l5d.io

This PR updates the docker registry to be cr.l5d.io to make
it consistent with that of the main docker images.
Signed-off-by: Tarun Pothulapati<EMAIL_ADDRESS>

My bad, branch is in sync, I was confused by changes we had done in the release workflow that were not synced against the integration tests workflow.

@alpeb, To remove confusing around docker image tags in workflows. I updated it to be the following in the latest commit.

Everything uses cr.l5d.io, which is the default in ./bin/docker-buildand updated *only* thedocker_buildjob inreleaseworkflow to useghcr.io` registry so that it can push images.


Fix the documentation for find.byElementPredicate

At one point there was something which analyzed all our dartdoc code to make sure it compiled?  Does that still exist?  Do we need to do something to make it apply to flutter_test and not just flutter?

That happens for our website (thanks to @devoncarew ! :) but wasn't aware that we did it for our docs. Maybe that's what you're thinking of?


Significant performance impact in VSCode

If this issue is already be worked on and tracked in #3531 or #3801 feel free to close this.
I experience a huge downgrade in VSCode performance caused by the vue language-tools. This applies to the insider version 2.0.14 as well as to the 2.0.11.
For this test I disabled every other extension in VSCode and even started with a completely new isolated instance of VSCode, but as soon as the language-tools are enabled, the performance impact is clearly visible.
Enabled language-tools:

Disabled language-tools:

This can be reproduced with every vue project, by opening it in VSCode and disabling every extension except the vue language-tools. The impact in probably different by the size of the project, but always significant.
OS: Windows 11 23H2 (22631.3447)
VSCode: 1.88.1

Thanks for the clarification. The problem is that emmet completion should not be affected by TS performance, fixed by https://github.com/microsoft/vscode-html-languageservice/pull/187, https://github.com/vuejs/language-tools/commit/65d38a18081e66f04ff56547997adbaaeaf40a79.


Identify location of AOE questions in FHIR bundle

User Story:
As a data analyst, I want to have ask on entry (AOE) questions in the FHIR bundle, so the data is complete
Description/Use Case
AOE questions are part of COVID reports. For HL7 v2, they show up as separate observations with specific LOINC codes. We need to figure out where they would go in FHIR.
Risks/Impacts/Considerations

I have not seen any direction of where to put this on FHIR, so there is the possibility this can change in the future.

Dev Notes:

Keep in mind that AOE questions belong to an order, so they must stay within the proper ORC/OBR segment in HL7 v2

Acceptance Criteria

Determine and document where we will place AOE questions in a FHIR bundle.

AOE questions - There is no predetermined way to represent AOE questions in a FHIR bundle. Let’s implement this in a simple way while we gather more information from the FHIR community. Using observations will get it closer to what an HL7 v2 message looks like. Use ServiceRequest.supportingInfo to link the AOEs. Alternatively, we could just leave it as a regular Observation in results, but the consensus is that this is not appropriate.
"supportingInfo": [
                    {
                        "reference": "Observation/xxxxxx"
                    }
                ]
            }
        },
        {
            "fullUrl": "Observation/xxxxxx",
            "resource": {
                "resourceType": "Observation",
                "id": "xxxxxx",
                "identifier": {
                    "use": "official",
                    "type": {
                        "system": "http://loinc.org",
                        "code": "81959-9",
                        "display": "Public health laboratory ask at order entry panel"
                    }
                },
                "status": "final",
                "subject": {
                    "reference": "Patient/3aaba67c-bd90-4b41-a820-816bfd9e9d77"
                },
                "code": {
                    "coding": [
                        {
                            "system": "http://loinc.org",
                            "code": "95417-2",
                            "display": "Is this the patient’s first test for COVID-19? - free text - do not use for matching"
                        }
                    ],
                    "text": "Is this the patient’s first test for COVID-19?"
                },
                "valueCodeableConcept": {
                    "coding": [
                        {
                            "system": "http://terminology.hl7.org/ValueSet/v2-0136",
                            "code": "Y",
                            "display": "Yes"
                        }
                    ]
                }
            }
        },


Android: Missed call notification is not cleared when Call back button is tapped

From the code, it looks like whenever ACTION_CALL_CALLBACK action is tapped, clearMissCallNotification is called, which should hide missed call notification. It's not happening in the latest version.

I think this is related to #533 as well.
I tried clicking on the "callback" button on the notification when avatar is null, and it correctly clears the notification.


Cyt 640 web UI

Summary

If merged this pull request will add a web UI for running Surfactant.
Proposed changes

The UI runs on top of other Surfactant code and does not modify any underlying functionality.  It provides a simple UI for running generate and merge commands using a web GUI.

I'll try to find some time to review and try out these changes either this coming week if I can find some time and have decent internet access for a while -- otherwise I'll get it done March 11.


Fix issue #42

Hi,
This branch fixes issue #42.
I tested it on Linux x86_64 (Ubuntu 19.10) and OpenBSD amd64 (6.6).
I served a local document root containing an executable gophermap:
#!/usr/bin/env sh
/usr/bin/env | sort

and tried various requests: regular request, HTTP GET/POST, TCP PROXY, non-existent name.
The log messages are printed to /var/syslog on Linux, and /var/daemon on OpenBSD.
When the -d option is used, the debug messages also appear in the syslog, and all messages are printed to stderr.
I checked the implementation of non-standard LOG_UPTO with this test program:
#include <stdio.h>
#include <syslog.h>

#define _LOG_UPTO(pri)							\
	(								\
	((pri) == LOG_EMERG)   ? (LOG_MASK(LOG_EMERG)) :		\
	((pri) == LOG_ALERT)   ? (LOG_MASK(LOG_EMERG) | LOG_MASK(LOG_ALERT)) : \
	((pri) == LOG_CRIT)    ? (LOG_MASK(LOG_EMERG) | LOG_MASK(LOG_ALERT) | LOG_MASK(LOG_CRIT)) : \
	((pri) == LOG_ERR)     ? (LOG_MASK(LOG_EMERG) | LOG_MASK(LOG_ALERT) | LOG_MASK(LOG_CRIT) | LOG_MASK(LOG_ERR)) : \
	((pri) == LOG_WARNING) ? (LOG_MASK(LOG_EMERG) | LOG_MASK(LOG_ALERT) | LOG_MASK(LOG_CRIT) | LOG_MASK(LOG_ERR) | LOG_MASK(LOG_WARNING)) : \
	((pri) == LOG_NOTICE)  ? (LOG_MASK(LOG_EMERG) | LOG_MASK(LOG_ALERT) | LOG_MASK(LOG_CRIT) | LOG_MASK(LOG_ERR) | LOG_MASK(LOG_WARNING) | LOG_MASK(LOG_NOTICE)) : \
	((pri) == LOG_INFO)    ? (LOG_MASK(LOG_EMERG) | LOG_MASK(LOG_ALERT) | LOG_MASK(LOG_CRIT) | LOG_MASK(LOG_ERR) | LOG_MASK(LOG_WARNING) | LOG_MASK(LOG_NOTICE) | LOG_MASK(LOG_INFO)) : \
	((pri) == LOG_DEBUG)   ? (LOG_MASK(LOG_EMERG) | LOG_MASK(LOG_ALERT) | LOG_MASK(LOG_CRIT) | LOG_MASK(LOG_ERR) | LOG_MASK(LOG_WARNING) | LOG_MASK(LOG_NOTICE) | LOG_MASK(LOG_INFO) | LOG_MASK(LOG_DEBUG)) : \
	0)

int main(int argc, char *argv[])
{
	(void) argc, (void) argv;
	printf("LOG_UPTO(LOG_EMERG):    %d\n", LOG_UPTO(LOG_EMERG));
	printf("LOG_UPTO(LOG_ALERT):    %d\n", LOG_UPTO(LOG_ALERT));
	printf("LOG_UPTO(LOG_CRIT):     %d\n", LOG_UPTO(LOG_CRIT));
	printf("LOG_UPTO(LOG_ERR):      %d\n", LOG_UPTO(LOG_ERR));
	printf("LOG_UPTO(LOG_WARNING):  %d\n", LOG_UPTO(LOG_WARNING));
	printf("LOG_UPTO(LOG_NOTICE):   %d\n", LOG_UPTO(LOG_NOTICE));
	printf("LOG_UPTO(LOG_INFO):     %d\n", LOG_UPTO(LOG_INFO));
	printf("LOG_UPTO(LOG_DEBUG):    %d\n", LOG_UPTO(LOG_DEBUG));
	puts("");
	printf("_LOG_UPTO(LOG_EMERG):   %d\n", _LOG_UPTO(LOG_EMERG));
	printf("_LOG_UPTO(LOG_ALERT):   %d\n", _LOG_UPTO(LOG_ALERT));
	printf("_LOG_UPTO(LOG_CRIT):    %d\n", _LOG_UPTO(LOG_CRIT));
	printf("_LOG_UPTO(LOG_ERR):     %d\n", _LOG_UPTO(LOG_ERR));
	printf("_LOG_UPTO(LOG_WARNING): %d\n", _LOG_UPTO(LOG_WARNING));
	printf("_LOG_UPTO(LOG_NOTICE):  %d\n", _LOG_UPTO(LOG_NOTICE));
	printf("_LOG_UPTO(LOG_INFO):    %d\n", _LOG_UPTO(LOG_INFO));
	printf("_LOG_UPTO(LOG_DEBUG):   %d\n", _LOG_UPTO(LOG_DEBUG));

	return 0;
}

The values printed are the same. I also had a look at the generated assembly using Godbolt for x86_64 and AArch64 (with clang and gcc) and it's identical; the level mask is a compile time constant.
@vext01 could you please check if this fixes the issue you reported?

Forgot a couple spots in src/file.c, and added missing mapfile for executable/static gophermap message.

Why was the automatic function generation removed?

For the most part, this is fine. I will review more indepth tomorrow.

My opinion about the generated functions.h is that it creates more problems than it solves.
Maintaining an up-to-date list of function declarations isn't difficult, especially because the compiler will immediately complain about a missing or out-of-date declaration.
Main problem for me is that it creates a circular dependency, which is a bad thing; in particular it makes incremental compilation impossible.
Also, it makes it more difficult to hide the internals of a compilation unit. I think it's better to expose the strictest minimum, in order to reduce coupling and keep parts independent.
Looking forward to reading your thoughts about this :slightly_smiling_face:

Hmm, would you mind splitting the removal of auto-func generation out into a different PR so we can talk about that seperatly to this issue?

I cherry-picked the auto-func generation out and pushed it.

I rebased the commit that should fix issue #42.
Thanks for having split the branch.
Sorry for the having disappeared.

I have only one small comment, otherwise it looks good.
I can confirm that adding -d causes gophernicus to log to /var/log/daemon on OpenBSD.
I also like that this if (st->opt_syslog) idiom goes away as the level is checked in the logging function.
Thanks

LGTM!
On Sat, 3 Oct 2020, 19:38 Augustin Fabre<EMAIL_ADDRESS>wrote:

@augfab commented on this pull request.
In src/log.c
https://github.com/gophernicus/gophernicus/pull/77#discussion_r499171581
:

va_start(ap, fmt);

if (errno) {

int en = errno;

char buf[BUFSIZE];

vsnprintf(buf, sizeof(buf), fmt, ap);

_log(LOG_CRIT, "%s (%s)", buf, strerror(en));

} else {

_vlog(LOG_CRIT, fmt, ap);

}
va_end(ap);

+}
+
+#define X(FCT_LVL, LOG_LVL)			\
You're right, fixed in new commit 406d254
https://github.com/gophernicus/gophernicus/commit/406d2548fc5f52534d4d6241fd487a22f23187e6
.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gophernicus/gophernicus/pull/77#discussion_r499171581,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAETWG6WWMYGCEN2RRSKU23SI5VSPANCNFSM4MQYXCGA
.

I will test and merge tomorrow, after my exam...

Hi @fosslinux,hope your exam went well. Would you have some time for the review now?


segfault when using fio benchmarks (seq. writes)

Describe the bug
When running fio benchmarks with sequential writes (rw=write) and filename=/dev/nvme0n1, I get a segfault in the simulated environments after the writes are finished. I'm not able to see the results of running fio benchmark due to this segfault.
This only happens with sequential writes, it doesn't happen with other type of reads and writes.
I have tested in case of using filename=/dev/sda, and this segfault doesn't show up.
To Reproduce
I have used the same kernel and disk image for X86 environment that is provided by simpleSSD website
I'm using the config file of intel750 where I have changed the LBASize=512 and UseCopyOnWriteDisk = 1
this is the command I have used to run SimpleSSD:
./build/X86/gem5.opt ./configs/example/fs.py --cpu-type=TimingSimpleCPU --num-cpus=1 --cpu-clock=2GHz --caches --l2cache --mem-type=DDR4_2400_8x8 --mem-size=8GB --kernel=x86_64-vmlinux-4.9.92 --disk-image=x86root.img --script=fio_write10s.sh --ssd-interface=nvme --ssd-config=./src/dev/storage/simplessd/config/intel750_400gb.cfg --root-device=/dev/nvme0n1p1
this is the command in the script to be executed inside the simulated environment
 ./fio --direct=1 --ioengine=libaio --iodepth=1 --bs=4096 --rw=write --filename=/dev/nvme0n1 --numjobs=1 --name=test --time_based --runtime=10s --randseed=13425
Here is the segfault I'm receiving:

I'm not sure why this problem shows up and only with sequential writes. I would also appreciate advices to debug this issue effectively.

Another thing which I should pinpoint is getting this output from the simulator in case of sequential writes which I did not see for other types of reads and writes:

Hi,
I assumed you booted x86root.img with DiskImageFile1 = <your path to x86root.img>.
As you specified --root-device=/dev/nvme0n1 parameter, Linux kernel uses SimpleSSD's NVMe disk as OS disk. But in fio script, you are overwriting contents of OS disk!
This should lead unexpected behavior -- file system is now corrupted.
Thanks.

thank you for your reply.
The main purpose of the experiment is to monitor the performance of writes to NVMe disk, so I aught to define the filename as /dev/nvme0n1.  How can I solve the issue? Also why this is happening with seq writes and not random writes?

Hi,
I don't know that why are you trying to wipe out OS disk. What you are doing is, install Linux on /dev/nvme0n1p1 and writing random binary data into /dev/nvme0n1 from beginning.
If you want to measure performance of NVMe disk, boot gem5 with /dev/sda1 (default IDE disk) and perform fio test on /dev/nvme0n1.
If you want to measure performance of filesystem + NVMe disk, boot gem5 with /dev/sda1 and perform fio test on --filename=<temporary file to I/O>. Mount /dev/nvme0n1p1 and store temporary file.
Separating OS disk and target disk removes interference between them.
Thanks.
P.S. I don't know why fio die with segfault -- but there are some candidates:

As you overwrite MBR, there is no partition information anymore.
As you overwrite first partition (OS disk), there is no filesystem information anymore.
Maybe fio executable file lies on very beginning of disk and you may overwrite the program itself -- but this does not impact running process though.
Maybe directory dev lie on very beginning of disk (as dev directory stores all device nodes).

P.S. 2
For random write, probability to overwrite critical filesystem/partition metadata become lower (as these metadata lie on very beginning of disk).
P.S. 3
If you still want to overwrite OS disk, please start overwriting from middle of disk using --offset option. If you really want to know why the segfault occurs, use addr2line or objdump to find the source line (or assembly) that generates SIGSEGV.


[ITensors] [BUG] AD numerical error when calling apply on MPS/MPO multiple times

Description
Fixes the gradient of apply. The gradient d MPS2 * apply(gates, MPS) / dMPS was wrong leading to wrong derivatives when applying the function 'apply' more than once.
Fixes #(issue)
#924
Minimal demonstration
using PastaQ
using ITensors
using Zygote

N = 1
hilbert = siteinds("Qubit", N)

os = OpSum()
os += -1, "Y", 1
H = MPO(os, hilbert)

ψs = productstate(hilbert, fill(0, N))

function evolve(ρs, θ)
    gates = ITensor[]
    for i in 1:length(θ)
        if mod1(i, 2) == 1
            g = gate("Rx", siteind(ρs, 1), (θ=θ[i]))
        else
            g = gate("Ry", siteind(ρs, 1), (θ=θ[i]))
        end
        gates = vcat(gates, g)
    end
    ρ = apply(gates, ρs)
    return ρ
end

function evolve2(ρs, θ)
    ρ = ρs
    for i in 1:length(θ)
        if mod1(i, 2) == 1
            g = gate("Rx", siteind(ρs, 1), (θ=θ[i]))
        else
            g = gate("Ry", siteind(ρs, 1), (θ=θ[i]))
        end
        ρ = apply([g], ρ)
    end

    return ρ
end

function loss(θ)
    Uψ = evolve(ψs, θ)
    return real(inner(Uψ', H, Uψ))
end

function loss2(θ)
    Uψ = evolve2(ψs, θ)
    return real(inner(Uψ', H, Uψ))
end

θ = π .* 0:0.1:2

println(loss(θ))
#0.7218500130938642

println(loss2(θ))
#0.7218500130938642

loss_grad1 = gradient(loss, θ)
@btime gradient(loss, θ)
#24.040 ms (37236 allocations: 4.23 MiB)

loss_grad2 = gradient(loss2, θ)
@btime gradient(loss2, θ)
#25.280 ms (35459 allocations: 4.12 MiB)

loss_grad1 == loss_grad2
# true  was false before

Todo
Add Tests to verify behaviour
Checklist:

[x] My code follows the style guidelines of this project. Please run using JuliaFormatter; format(".") in the base directory of the repository (~/.julia/dev/ITensors) to format your code according to our style guidelines.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[ ] I have added tests that verify the behavior of the changes I made.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] Any dependent changes have been merged and published in downstream modules.

Much appreciated!

@danielalcalde could you add the code from your first comment as a test?

Codecov Report

Merging #981 (10e2096) into main (3ac6859) will decrease coverage by 0.67%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #981      +/-   ##
==========================================
- Coverage   64.88%   64.20%   -0.68%
==========================================
  Files          97       97
  Lines       10176     9536     -640
==========================================
- Hits         6603     6123     -480
+ Misses       3573     3413     -160

Impacted Files
Coverage Δ

src/ITensorChainRules/mps/abstractmps.jl
87.95% <100.00%> (-1.30%)
:arrow_down:

src/ITensorChainRules/ITensorChainRules.jl
84.61% <0.00%> (-7.70%)
:arrow_down:

src/ITensorChainRules/NDTensors/tensor.jl
28.57% <0.00%> (-3.25%)
:arrow_down:

src/ContractionSequenceOptimization/utils.jl
61.14% <0.00%> (-2.86%)
:arrow_down:

src/ITensorChainRules/mps/mpo.jl
80.55% <0.00%> (-2.38%)
:arrow_down:

src/mps/abstractprojmpo.jl
85.71% <0.00%> (-2.32%)
:arrow_down:

src/mps/projmpo_mps.jl
46.42% <0.00%> (-2.06%)
:arrow_down:

src/physics/site_types/qudit.jl
79.16% <0.00%> (-1.97%)
:arrow_down:

src/mps/diskprojmpo.jl
78.12% <0.00%> (-1.88%)
:arrow_down:

...SequenceOptimization/breadth_first_constructive.jl
72.07% <0.00%> (-1.70%)
:arrow_down:

... and 62 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

I'm going to merge this since I'm trying to clear out some open issues, I'll add some simple tests in a follow-up PR.


Setup / Update of sensor platform ecowater_softener is taking over 10 seconds

Hi,
I have recently installed the ecowater-softener integration for Home Assistant 2022.2.9 via HACS.  Although integration seems to be working within Home Assistant, I do see the follow errors logged which comes up now and then.
Logger: homeassistant.components.sensor
Source: /usr/local/lib/python3.9/asyncio/events.py:80
Integration: Sensor (documentation, issues)
First occurred: 9:00:29 AM (1 occurrences)
Last logged: 9:00:29 AM
Setup of sensor platform ecowater_softener is taking over 10 seconds.
Logger: homeassistant.helpers.entity
Source: helpers/entity.py:728
First occurred: 9:31:07 AM (1 occurrences)
Last logged: 9:31:07 AM
Update of sensor.ecowater_######### is taking over 10 seconds

I can see the same error log after a fresh install

These are just warnings and can be ignored. This is just due to the EcoWater website being slow.
Thanks 👍


a way to ensure that camera is disabled

closes #17570
I think this is the most straightforward way to implement this feature. This pr adds a default parameter to Camera.clear_current(boolean enable_next_camera = true). It can be used to discourage camera from enabling another camera.

You are not conforming your code with the clang style which is enforced. If you check out the details of the fail, it states the automatic clang formatter want to do this changes for you:
-		if(enable_next){
+		if (enable_next) {

To be short, you MUST separate with a space the parenthesis from the braces.
It is practical add the hooks in git to have your local clang check the code before commiting to ensure The Travis CI never fail building. For more info, check the misc/hooks/ directory in godot source code tree.

That's quite strange since I have hooks configured and the check said that Files in this commit comply with the clang-format rules. Did many prs on this config in the past... will need to investigate this. Thank you

Now that Godot 3.1 has been released, we don't plan to cherry-pick new features and enhancements to the 3.0 branch, unless there is very strong support in favor of it. Removing cherrypick label for 3.0.


Entity unavailible

After a few weeks of no problems the entity for my hiveOS rig shows as unavailible

Tried disabling then enabling the integration but cant get the miner to show as availible. And yes the rig is online and showing in the hiveos dashboard.
Following error can be found in the system logs:
custom_components.hiveos.exceptions.HiveOsApiException: Failed response: 403 {'message': 'Cannot use API keys to access free farms', 'code': 403}

So it seems to be an issue after the recent payed plan changes

Looks like HiveOS only allows subscribed farms to access the API. Not much I can do about that unfortunately. You'll have to pay for HiveOS to use this integration.


bug can't export model _packed problems

Description

t2t-exporter won't export models trained as _packed.

TensorFlow and tensor2tensor versions

tensor2tensor==1.5.5
tensorboard==1.5.0
tensorflow==1.5.0
tensorflow-gpu==1.5.0
tensorflow-serving-api==1.5.0
tensorflow-tensorboard==1.5.0

In case of bug report: Steps to reproduce the problem
t2t-exporter \
  --model=transformer \
  --hparams_set=transformer_big_adafactor \
  --problems=translate_ende_wmt32k_packed \
  --data_dir=/home/t2t_data \
  --output_dir=/home/t2t_train/translate_ende_wmt32k_packed/transformer-tr$

In case of bug report: Error log
Traceback (most recent call last):
  File "export.py", line 75, in <module>
    tf.app.run()
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/platform/app.py", line 126, in run
    _sys.exit(main(argv))
  File "export.py", line 71, in main
    checkpoint_path=tf.train.latest_checkpoint(ckpt_dir))
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/contrib/learn/python/learn/export_strategy.py", line 98, in export
    return self.export_fn(estimator, export_path, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/contrib/learn/python/learn/utils/saved_model_export_utils.py", line 455, in export_fn
    strip_default_attrs=strip_default_attrs)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/estimator/estimator.py", line 592, in export_savedmodel
    config=self.config)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/estimator/estimator.py", line 793, in _call_model_fn
    model_fn_results = self._model_fn(features=features, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/tensor2tensor/utils/t2t_model.py", line 874, in wrapping_model_fn
    use_tpu=use_tpu)
  File "/usr/local/lib/python2.7/dist-packages/tensor2tensor/utils/t2t_model.py", line 919, in estimator_model_fn
    return model.estimator_spec_predict(features)
  File "/usr/local/lib/python2.7/dist-packages/tensor2tensor/utils/t2t_model.py", line 1037, in estimator_spec_predict
    decode_length=decode_hparams.extra_length)
  File "/usr/local/lib/python2.7/dist-packages/tensor2tensor/utils/t2t_model.py", line 523, in infer
    top_beams, alpha)
  File "/usr/local/lib/python2.7/dist-packages/tensor2tensor/models/transformer.py", line 230, in _beam_decode
    features, decode_length, beam_size, top_beams, alpha)
  File "/usr/local/lib/python2.7/dist-packages/tensor2tensor/models/transformer.py", line 291, in _fast_decode
    features=features)
  File "/usr/local/lib/python2.7/dist-packages/tensor2tensor/utils/expert_utils.py", line 254, in __call__
    outputs.append(fns[i](*my_args[i], **my_kwargs[i]))
  File "/usr/local/lib/python2.7/dist-packages/tensor2tensor/models/transformer.py", line 85, in encode
    hparams, nonpadding=features_to_nonpadding(features, "inputs"),
  File "/usr/local/lib/python2.7/dist-packages/tensor2tensor/models/transformer.py", line 536, in features_to_nonpadding
    return tf.minimum(features[key], 1.0)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/ops/gen_math_ops.py", line 2717, in minimum
    "Minimum", x=x, y=y, name=name)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/framework/op_def_library.py", line 519, in _apply_op_helper
    repr(values), type(values).__name__))
TypeError: Expected int32 passed to parameter 'y' of op 'Minimum', got 1.0 of type 'float' instead.

Thanks, with the latest release _packed probles can be exported!

Hi @mehmedes,
So what you did actually to solve this issue? is it change the _packed to non-packed or what? Thanks

@dyngts : Exporting it and running it as PROBLEM=translate_ende_wmt32k instead of PROBLEM=translate_ende_wmt32k_packed helped me.


Add 2d diffusion model bundle

Fixes # .
Description
Add 2d diffusion model bundle
Status
Ready/Work in progress/Hold
Please ensure all the checkboxes:

[x] Codeformat tests passed locally by running ./runtests.sh --codeformat.
[ ] In-line docstrings updated.
[ ] Update version and changelog in metadata.json if changing an existing bundle.
[ ] Please ensure the naming rules in config files meet our requirements (please refer to: CONTRIBUTING.md).
[ ] Ensure versions of packages such as monai, pytorch and numpy are correct in metadata.json.
[ ] Descriptions should be consistent with the content, such as eval_metrics of the provided weights and TorchScript modules.
[ ] Files larger than 25MB are excluded and replaced by providing download links in large_file.yml.
[ ] Avoid using path that contains personal information within config files (such as use /home/your_name/ for "bundle_root").

please refer to https://github.com/Project-MONAI/model-zoo/pull/390 (I pushed multiple commits) and update the format of README file and config files.

Hi @Can-Zhao , may also need to modify bundle_custom_data.py, and put this bundle into the list exclude_verify_shape_list and exclude_verify_torchscript_list

please refer to #390 (I pushed multiple commits) and update the format of README file and config files.

Thank you so much Yiheng! I just modified readme and pretrain setting in config

please also prepare a file like:
https://github.com/Project-MONAI/model-zoo/blob/dev/ci/install_scripts/install_brats_mri_generative_diffusion_dependency.sh
for this bundle, thanks in advance!

Hi @Can-Zhao , may also need to modify bundle_custom_data.py, and put this bundle into the list exclude_verify_shape_list and exclude_verify_torchscript_list

Done! Thank you!

please also prepare a file like: https://github.com/Project-MONAI/model-zoo/blob/dev/ci/install_scripts/install_brats_mri_generative_diffusion_dependency.sh for this bundle, thanks in advance!

I reused this one. They have same dependency

/build


feat: add base model for forum interactions (FC-0033)

This adds fact_forum_interactions, which pulls course name and course run into the forum interaction dataset. This model can be used to answer questions like "how many learners were active on a course's forums" and "how much do individual learners interact with the forum".

Thanks for the pull request, @SoryRawyer!  Please note that it may take us up to several weeks or months to complete a review and merge your PR.
Feel free to add as much of the following information to the ticket as you can:

supporting documentation
Open edX discussion forum threads
timeline information ("this must be merged by XX date", and why that is)
partner information ("this is a course on edx.org")
any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.
Please let us know once your PR is ready for our review and all tests are green.

@SoryRawyer 🎉 Your pull request was merged!  Please take a moment  to answer a two question survey so we can improve your experience in the future.


list events from DB(#19)

first try

Current coverage is 83.84% (diff: 0.00%)

Merging #57 into master will decrease coverage by 4.41%

@@             master        #57   diff @@
==========================================
  Files            19         19
  Lines           247        260    +13
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits            218        218
- Misses           29         42    +13
  Partials          0          0

Powered by Codecov. Last update 73c28f5...efc03a0


Prompt to reset settings when settings.json cannot be read

Currently the GUI shows a confusing error message when settings.json can't be read. This is the cause of two reported issues: bitcoin/bitcoin#21340 and bitcoin/bitcoin#21974. Current error message looks like:

This PR tries to clarify the error dialog, and adds an option to just clear the settings and reset them to default:

Additionally the PR also shows a slightly better error message when there is an error trying to write the settings file. This error probably should occur less frequently, but it is easy to improve, and it should be good to make the write error consistent with the read error. The new write error dialog looks like:

Note: Screenshots above are from linux and I think the button placement Qt chooses there is pretty strange. I think it's weird that the default button is on the left in the read error dialog, but the default button is on the right in the write error dialog. I also think it's weird that the show details toggle is between two other buttons that dismiss the dialog. None of this is very bad, but I'm hoping maybe it looks a little better on other platforms, since it makes probably doesn't make sense to hardcode a button order if conventions vary across platforms.
Also, the following patch is an easy way to test the PR, and it's what I used to make the screenshots:
--- a/src/util/settings.cpp
+++ b/src/util/settings.cpp
@@ -65,7 +65,7 @@ bool ReadSettings(const fs::path& path, std::map<std::string, SettingsValue>& va
     if (!file.is_open()) return true; // Ok for file not to exist.

     SettingsValue in;
-    if (!in.read(std::string{std::istreambuf_iterator<char>(file), std::istreambuf_iterator<char>()})) {
+    if (1 | !in.read(std::string{std::istreambuf_iterator<char>(file), std::istreambuf_iterator<char>()})) {
         errors.emplace_back(strprintf("Unable to parse settings file %s", path.string()));
         return false;
     }
@@ -102,7 +102,7 @@ bool WriteSettings(const fs::path& path,
     }
     fsbridge::ofstream file;
     file.open(path);
-    if (file.fail()) {
+    if (1 | file.fail()) {
         errors.emplace_back(strprintf("Error: Unable to open settings file %s for writing", path.string()));
         return false;
     }

Updated cf472050f232dfac0f923ea99993fb7b607b955c -> ebfd619e3cfef148fd0e93ca00505d635636ac34 (pr/badset.1 -> pr/badset.2, compare) to fix appveyor error https://ci.appveyor.com/project/DrahtBot/bitcoin-core-gui/builds/39921403

I've tried reproducing using permissions like this:
sudo chown root:root /tmp/datadir/regtest/settings.json
sudo chmod a-rwx  /tmp/datadir/regtest/settings.json

bitcoin-qt just silently (both master and PR) overwritten that file after experiencing EACCES (Permission denied):
$ strace -efile src/qt/bitcoin-qt -regtest -datadir=/tmp/datadir 2>&1 | fgrep settings.json
openat(AT_FDCWD, "/tmp/datadir/regtest/settings.json", O_RDONLY) = -1 EACCES (Permission denied)
openat(AT_FDCWD, "/tmp/datadir/regtest/settings.json.tmp", O_WRONLY|O_CREAT|O_TRUNC, 0666) = 9
rename("/tmp/datadir/regtest/settings.json.tmp", "/tmp/datadir/regtest/settings.json") = 0

(it's probably allowed to rename because process is still owner of the directory).
Not saying it's this PR's issue, just interesting find...

I've created AppArmor profile /etc/apparmor.d/bitcoin that attaches to the built binaries (master and pr) and allows (almost) everything, except access to the settings.json:
profile bitcoin /home/vincas/code/bitcoin/379-bitcoin-core-gui.git/_build_{master,pr}/src/qt/bitcoin-qt {

    /{,**} rwmklux, # allow reading/writing/locking/mmaping/linking/executing... everything

    # allow various other kernel api stuff:
    capability,
    network,
    dbus,
    ptrace,
    signal,
    unix,

    # ..except this one
    audit deny /tmp/datadir/regtest/settings.json rwmkl,
}

I do get dialog Failed renaming settings file... but the fact that reading has failed was "skipped":
$ strace -efile src/qt/bitcoin-qt -regtest -datadir=/tmp/datadir 2>&1 | fgrep settings.json
openat(AT_FDCWD, "/tmp/datadir/regtest/settings.json", O_RDONLY) = -1 EACCES (Permission denied)
openat(AT_FDCWD, "/tmp/datadir/regtest/settings.json.tmp", O_WRONLY|O_CREAT|O_TRUNC, 0666) = 9
rename("/tmp/datadir/regtest/settings.json.tmp", "/tmp/datadir/regtest/settings.json") = -1 EACCES (Permission denied)
- Failed renaming settings file /tmp/datadir/regtest/settings.json.tmp to /tmp/datadir/regtest/settings.json

audit.log shows that AppArmor denied reading and then writing:
type=AVC msg=audit(1627499280.531:631): apparmor="DENIED" operation="open" profile="bitcoin" name="/tmp/datadir/regtest/settings.json" pid=39084 comm="bitcoin-qt" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000FSUID="vincas" OUID="vincas"
type=AVC msg=audit(1627499280.531:632): apparmor="DENIED" operation="rename_dest" profile="bitcoin" name="/tmp/datadir/regtest/settings.json" pid=39084 comm="bitcoin-qt" requested_mask="wc" denied_mask="wc" fsuid=1000 ouid=1000FSUID="vincas" OUID="vincas"

Concept ACK.

Concept ACK. Will test this weekend.

Tested on Windows with src/util/settings.cpp from https://github.com/bitcoin/bitcoin/pull/22591/
Post merge tACK https://github.com/bitcoin-core/gui/pull/379/commits/1ee6d0b01a517893967379677029fb5417978247

nit:
-Settings file could not be read
+Failed to open settings file

-Do you want to reset settings to default values, or to abort without making any changes?
+Do you want to reset settings to default values, or abort without making any changes?

nit:
DetailedText can be better if it was something like this:
File: E:\regtest\settings.json
Error: Please check permissions

If DetailedText is changed above, can follow the same format for write error as well.


Move to vertx 4.x

Move vertx dependency from 3.x to 4.x
FYI @jflo

Dependency on Besu metrics service dependency to move Vertx to 4.x

Depends on @hyperledger/besu#3073


kafka ssl authentication error

Info
Hi
The article is very much helpful. after the broker setup  section, the broker started, but when finished client setup (with/without authentication) sections, and try it with the command showed in Verification section, but it has  ERROR log . is there any fault i've made？
Regards
broker properties
security.inter.broker.protocol=SSL
listeners=SSL://<IP_ADDRESS>:9092
advertised.listeners=SSL://<IP_ADDRESS>:9092
sasl.mechanism.inter.broker.protocol=SSL
ssl.endpoint.identification.algorithm=
ssl.client.auth=none
ssl.truststore.location=/data/tmp/server/<IP_ADDRESS>/kafka.server.truststore.jks
ssl.truststore.password=MyServerPassword123
ssl.keystore.location=/data/tmp/server/<IP_ADDRESS>/kafka.server.keystore.jks
ssl.keystore.password=MyServerPassword123
ssl.key.password=MyServerPassword123
...

client config
security.protocol=SSL
ssl.truststore.location=/root/tmp/current/client-ssl/tmp/server/<IP_ADDRESS>/kafka.client.truststore.jks
ssl.truststore.password=MyClientPassword123

broker start log
[2021-01-26 11:29:07,692] INFO Registered broker 1 at path /brokers/ids/1 with addresses: ArrayBuffer(EndPoint(<IP_ADDRESS>,9092,ListenerName(SSL),SSL)), czxid (broker epoch): 162 (kafka.zk.KafkaZkClient)
[2021-01-26 11:29:07,747] INFO [ExpirationReaper-1-topic]: Starting (kafka.server.DelayedOperationPurgatory$ExpiredOperationReaper)
[2021-01-26 11:29:07,747] INFO [ExpirationReaper-1-Heartbeat]: Starting (kafka.server.DelayedOperationPurgatory$ExpiredOperationReaper)
[2021-01-26 11:29:07,747] INFO [ExpirationReaper-1-Rebalance]: Starting (kafka.server.DelayedOperationPurgatory$ExpiredOperationReaper)
[2021-01-26 11:29:07,759] INFO [GroupCoordinator 1]: Starting up. (kafka.coordinator.group.GroupCoordinator)
[2021-01-26 11:29:07,763] INFO [GroupCoordinator 1]: Startup complete. (kafka.coordinator.group.GroupCoordinator)

client producer log
root@i-xxxxxx:~/tmp/current# ./bin/kafka-console-producer.sh --broker-list <IP_ADDRESS>:9092 --topic test --producer.config ./config/producer.properties
>[2021-01-26 11:40:23,054] ERROR [Producer clientId=console-producer] Connection to node -1 (/<IP_ADDRESS>:9092) failed authentication due to: SSL handshake failed (org.apache.kafka.clients.NetworkClient)

broker ssl log
[2021-01-26 11:30:57,637] INFO [SocketServer brokerId=1] Failed authentication with /<IP_ADDRESS> (SSL handshake failed) (org.apache.kafka.common.network.Selector)

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

ID: c117dccb-22e3-b6b3-ae19-9e2b6ec477a8
Version Independent ID: 4c0a71c1-e367-e103-2839-beb08348b2d6
Content: Apache Kafka TLS encryption & authentication  - Azure HDInsight
Content Source: articles/hdinsight/kafka/apache-kafka-ssl-encryption-authentication.md
Service: hdinsight
GitHub Login: @hrasheed-msft
Microsoft Alias: hrasheed

kafka version 2.3.1, scala 2.11

kafka version 2.3.1, scala 2.11

Hello @spwangxp
Thanks for the feedback! We are currently investigating and will update you shortly.

Hello @spwangxp
Thanks for the feedback! We are currently investigating and will update you shortly.

@spwangxp I notice in the broker properties you supplied, one was left unfinished
ssl.endpoint.identification.algorithm=
Was this intentional?

@spwangxp  Since we have not heard back from you we will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly reopen the issue and continue the discussion.


feat: document-token-limit

Codecov Report

Merging #168 (0dd9f59) into main (e6b75e7) will decrease coverage by 0.77%.
The diff coverage is 92.30%.

@@            Coverage Diff             @@
##             main     #168      +/-   ##
==========================================
- Coverage   99.53%   98.75%   -0.78%
==========================================
  Files          15       16       +1
  Lines         215      241      +26
  Branches       50       54       +4
==========================================
+ Hits          214      238      +24
- Misses          1        3       +2

Impacted Files
Coverage Δ

packages/plugins/document-token-limit/src/index.ts
92.30% <92.30%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Improve route deploy messaging, add --dry-run flag

several things can happen when you publish to a route:

a new route is created
the same route is maintained (it already pointed to the worker you are publishing)
the route was already assigned and was not changed
some kind of error occurred.

unfortunately only one route can be updated at a time, so there's no way to do an atomic update of all routes, or any kind of a forced overwrite for case 3, so it's up to users to correct these issues. we should:

add a command or flag that shows the likely outcome of publishing to the routes in question; this output should give the appropriate instructions for correcting instances of case 3. it should also indicate existing routes that are no longer specified in the wrangler.toml as part of this list that can be removed with wrangler route delete <route>.
include the same output on normal publishes to instruct users to wrangler route delete <route> for those cases and, in the case of 3, re-run wrangler publish.

Isn't item 2 just a subset of 3? That is, the worker is updated but the route's assigned worker is not adjusted in either case.
If a user of wrangler is going to be notified to delete the route to then publish to it aren't we creating a potential for an application to be down between delete and publish of the worker at the re-created route?
Surely the question here is why isn't the route, if existing, simply adjusted to use the newly published worker?  The user has defined the route in the wrangler.toml so why shouldn't it be updated? Assuming it can, shouldn't the operation be:

worker updated (as current) - note, all routes that use this worker continue to use the now updated worker.
specified route (created or existing) is set to use this route

Deploy message then lists the defined route with the former worker name (if changing) and the new worker name.   And, since we are talking about route messages, it would be great if the response could also list all other routes that use the published worker.
This could scale with this same logic should the route variable one day allow multiple routes (delimited list), but this is for another issue.
If it can't be permitted to update an existing route's assigned worker then isn't the "route" field incorrectly titled, and should be renamed to something like "route_create" instead, as this is all its permitted to do.  Then, should this field be present in the wranger.toml file and run where the route exists the suggested message instructions, as per end of first post, would be great to include.  Again, it would be great if the response could also list all other routes that use the published worker.

hey @glen-au these  are  some great questions. I'll go a  little out of order and start with saying that we actually do support specifying multiple routes as of 1.8.0. I believe that change lists the routes the worker is deployed on, as well.

Isn't item 2 just a subset of 3? That is, the worker is updated but the route's assigned worker is not adjusted in either case.

because one is a positive and one is a negative, they are presented as distinct.

If a user of wrangler is going to be notified to delete the route to then publish to it aren't we creating a potential for an application to be down between delete and publish of the worker at the re-created route?

yes. however this has a lot more to do with the design of the api, as routes cannot be atomically overwritten even at that level, wrangler (or any client) has to make two distinct calls to overwrite a route: one to explicitly delete, and the second to create. i have my eyes on a request to improve the api, but it has not been prioritized by the platform as of yet.

Surely the question here is why isn't the route, if existing, simply adjusted to use the newly published worker? The user has defined the route in the wrangler.toml so why shouldn't it be updated?

the reason i didn't immediately implement this solution is that a wrangler.toml is not representative of all workers and routes in use at any given time. the route list can give insight, as can the --dry-run option listed here, but to add the destructive step of automatically deleting an existing route would be a breaking change, and one I don't intend to make lightly. I would, however, be open to introducing a flag, such as --overwrite-routes to unlock this behavior for users, but it should be noted that until the API changes, the downtime issue you pointed out before will still exist, if only for moments.


Kubectl link updated

Kubectl link updated to the latest version (1.2.2)

Hi @idvoretskyi - Thanks for the PRs!
Before we can accept them we'll need you to fill out our contributors agreement: http://docs.projectcalico.org/en/latest/contribute.html
Other than that I see no reason we shouldn't merge these.  Thanks!

@caseydavenport have signed, review it again please!

@idvoretskyi Got the CLA and I've merged the PRs, thanks again!


Implement cudf construction with adapters.

This PR updates DMatrix creation from device memory to use adapters.
I will remove old code in a separate PR for clarity.

I haven't looked into this yet.  Please help adding a missing header <dmlc/data.h> to adaptor.h .


Problems with Dispose of WasapiOut and WasapiCapture

Hi,
I have developed a class that acquires audio data on a capture device using a WasapiCapture object and reproduces them on a render device using a WasapiOut object. I use it to record the signal coming in through an external device and to reproduce it through the PC's headphones output. I've also created a class that implements IMMNotificationClient to handle and raise again the events of connection and disconnection of the headphones cable to warn the user and to respectively setup and release the resources.
Firstly, I encountered some problems at disconnection, when I tried to release the WasapiOut object: the execution flow interrupted in correspondence to the call to the Dispose() method until the ContextSwitchDeadlock was raised. Sensing that this was due to a synchronization failure, I tried to change the invocation of the DeviceStateChanged event from Invoke() to BeginInvoke() and it worked.
Then, other problems appeared at reconnection, when I tried to create a new instance of the WasapiOut object: the COM MMDevice object raised in rapid succession three events with these state changes: Active - NotPresent - Active. I figured out that by the time the flow arrived to the creation point after the first 'Active' event, the device was already in the 'NotPresent' state. So, I solved this issue by wrapping the creation in a try-catch to skip the first 'Active' and to succeed in the second call.
Now, I have discovered that the first problem appears again when the MMDevice associated to the WasapiOut object is the default render device for Windows: at disconnection the execution flow is blocked in correspondence of the Dispose() call. So, I have decided to not dispose the WasapiOut object at disconnection, basing on the supposition that I was trying to dispose an object that did not exist anymore for the PC (the headphones endpoint disappears if the cable is disconnected).
However, I found out that the same problem (execution flow is interrupted to the Dispose() call) appears when I try to release the WasapiCapture object, which not only is a different endpoint from the one that raised the event, but it also belongs to another device.
When the flow blocks, the AudioClient associated either to the WasapiOut or the WasapiCapture objects is not accessible and raises System.Runtime.InteropServices.COMException. This might be explained for the output unplugged device, but I cannot find a reason for the input connected device that should be disposed.
All the instructions that operate on these objects are wrapped in a call passed to the main thread SynchronizationContext, so they are executed on the main thread (I had other problems at the very beginning due to the access from a background thread).
Could you give any hint about this problem?
Thank you in advance!

To add some more information, I encountered this problem with the latest release of NAudio installed as NuGet package. Then, I tried to import an older version (1.8.4) directly as dll and this problem disappeared.
I don't know if this is related with the fact that my solution is WPF and NAudio 1.9.0 is UWP or there is actually a problem in the latest release. Hope this helps!

Any updates on this? I'm struggling to get audio device to be changed upon OnDefaultDeviceChanged, and made sure for the functions to use main thread. But it seems that WasapiOut does not dispose after all.
I also tried downgrading NAudio to 1.8.4 as mentioned above, but it still does not work.


NTR for glycosylphosphatidylinositol biosynthesis defect 16   MONDO:0040500

EEG
psychologist evaluation
speech therapy

addressed in the last release #244 . Closing.


(BKR-1010) Fix Cygwin install_package helper

Newer Windows templates in vmpooler have been produced through a
Packer process, and install packages differently than earlier
templates based on how Cygwin was installed.
Two additional switches must now be passed for package installs to
succeed using Cygwins package manager.
See https://tickets.puppetlabs.com/browse/IMAGES-424 for more detail
This fixes a bug where cmdline_args passed to Cygwins setup*.exe
are injecetd into the wrong location.  When specify a -R, the
rootdir value must be passed next.  Previously, additional args
were injected in between the -R and the rootdir value.

Verified as fixed after running:
TEST=./acceptance/tests/base/host/packages.rb bundle exec rake test:base TEST_TARGET=windows2012r2-64a

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/3275/


Language output

Why always generate the uz-Latn-UZ and de dll? How to disable that?

@seanmars

The resource files are necessary for the file system controls. I do not like to make different builds with and without localization support. It will be confusing and the next issue asks why the user interface is not in German like the demo app.

The .csproj file lists resources and build actions for them. It is a XML file so you can open it with any text editor. You may conditionally include or exclude the files from the build, if a specified symbol is set inside the build configuration. Please look for tutorials on conditional builds.

Yes. It's too many unnecessary Folders. Just Include this in your CSProj File.
<PropertyGroup>
    <SatelliteResourceLanguages>en</SatelliteResourceLanguages>
</PropertyGroup>


fix(storeFreeze): remove double error log

This fixes a problem where any error inside a reducer will lead to the State mutation message, even when that's not the case. Default error reporting already prints an error message to console with the actual error.
Also, state mutation can also happen outside reducers (selectors, etc, subscribers, etc), so there's no point in handling this case as special.

@awerlang correct, there is already a default TypeError
$ node
> const f = require('deep-freeze-strict')
undefined
> const obj = { a: 1, b: 2 }
undefined
> f(obj)
{ a: 1, b: 2 }
> Object.assign(obj, {c: 3})
TypeError: Can't add property c, object is not extensible
    at repl:1:8
    at sigintHandlersWrap (vm.js:22:35)
    at sigintHandlersWrap (vm.js:96:12)
    at ContextifyScript.Script.runInThisContext (vm.js:21:12)
    at REPLServer.defaultEval (repl.js:346:29)
    at bound (domain.js:280:14)
    at REPLServer.runBound [as eval] (domain.js:293:12)
    at REPLServer.<anonymous> (repl.js:545:10)
    at emitOne (events.js:101:20)
    at REPLServer.emit (events.js:188:7)
>

one question:
why const nextState = nextState = reducer(state, action); instead of const nextState = reducer(state, action);

That's a mistake, can you fix that? I won't have access to a computer till next week.

@awerlang merged, bumped version and published to npm


x86 patch

closes #22

Current coverage is 73.11% (diff: 91.30%)

Merging #39 into master will not change coverage

@@             master        #39   diff @@
==========================================
  Files            25         25
  Lines          2604       2604
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           1904       1904
  Misses          700        700
  Partials          0          0

Powered by Codecov. Last update 6aab88c...acd59a1


Makefile errors out when GOPATH has multiple dirs

What version of Delve are you using (dlv version)?
Latest git (as of 7th March 2017)
What version of Go are you using? (go version)?
go version go1.8 darwin/amd64
What operating system and processor architecture are you using?
OSX 10.11.6, 64 bit Intel
What did you do?
Ran "make install" from a clone of the git repo
What did you expect to see?
Successful run of make install
What did you see instead?
Make errors out due to incorrect assumption that GOPATH will only contain one path:
$ make install
go install -ldflags="-s -X main.Build=bb07fc36b9df2b9baec074ee8a48b1941f049f55" github.com/derekparker/delve/cmd/dlv
codesign -s "dlv-cert"  /Users/jc/go:/Users/jc/git_repos/bin/dlv
/Users/jc/go:/Users/jc/git_repos/bin/dlv: No such file or directory
make: *** [install] Error 1

It's not hard to work around by setting GOBIN first, but it should probably be fixed at some point. :wink:

As a thought towards fixing this, it might be useful to figure out the installed path to delve by using something like this:
OLDPATH=$PATH
PATH=$GOPATH
hash -r
DELVEBIN=`which dlv`
if [ "$DELVEBIN" != "" ]; then
  # Delve was found, so sign it
  PATH=$OLDPATH
  hash -r
  codesign -s "$(CERT)" $DELVEBIN
fi

That's untried, concept only code, but it seems like a reasonable approach.

I have similar error
scripts/gencert.sh || (echo "An error occurred when generating and installing a new certicate"; exit 1)
go install -ldflags="-s -X main.Build=2c0e31160de8cba2a4351dcf39486d05313b4da1" github.com/derekparker/delve/cmd/dlv
codesign -s "dlv-cert"  /bin/dlv
/bin/dlv: No such file or directory
make: *** [install] Error 1


When adding new short code click counter stucks

Steps to reproduce:

Go to url http://apptest.admin.olhub.com/shortUrl/
Add some short code
Watch that counters are stuck

This has been corrected.

looks ok!


Initial LESS changes to Bootstrap 3 UI

After #18, make a first pass at updating LESS variables and re-generating the Bootstrap 3 UI to bring it more inline with branding standards.
https://lesscss.org
https://getbootstrap.com/docs/3.4/customize/#less-variables
Acceptance is sign-off by John and Jason.

Closed by #4691


[google_maps_flutter] Replace Robolectric.setupActivity

Currently the GoogleMapControllerTest.java file uses a deprecated method, Robolectric.setupActivity, to set up the test activity. Since replacing wasn't trivial (ComponentAcitivity has a different structure and setup requirements) I'm suppressing the warning for now as part of turning on -Werror, but it should be updated to something non-deprecated.
@reidbaker FYI as the current CODEOWNER of the Android implementation of this plugin. I wouldn't imagine that this is high priority, but presumably the deprecated API will eventually be removed.

@gmackall low priority but lets talk about this when it is time to pick new tasks.

@reidbaker I currently have this still on my backlog, behind the issue regarding insets/dismissing keyboard, and the debug signing key flake.
No reply needed if that sounds fine, but can talk if you think this should be picked up soon!


Roadmap for releasing a new web application based on autogen.

Very excited for this! How can I contribute?

^ Same here!

Thanks for your interest. The goal is to release a research assistant that allows you to do q & a on papers, aggregate results, create visualizations/artifacts, skills that can be reused.
Tagging @sonichi @victordibia
@gagb @afourney

I working on implementing AutoGen in GPT-Academic:  https://github.com/binary-husky/gpt_academic/

I know two options: register a callback function using register_reply or use web sockets. @victordibia do you have a better answer?

In https://github.com/microsoft/autogen/pull/322 , I remap callback by :
agent_handle._print_received_message = lambda a,b: self.gpt_academic_print_override(agent_kwargs, a, b)
if agent_kwargs['name'] == 'user_proxy':
    agent_handle.get_human_input = lambda a: self.gpt_academic_get_human_input(user_proxy, a)
    user_proxy = agent_handle
if agent_kwargs['name'] == 'assistant': assistant = agent_handle

In #322 , I remap callback by :
agent_handle._print_received_message = lambda a,b: self.gpt_academic_print_override(agent_kwargs, a, b)
if agent_kwargs['name'] == 'user_proxy':
    agent_handle.get_human_input = lambda a: self.gpt_academic_get_human_input(user_proxy, a)
    user_proxy = agent_handle
if agent_kwargs['name'] == 'assistant': assistant = agent_handle

register_reply is a good idea, however, several flag variables are probably required inside autogen code.

It looks to be on the right track. What flag variables are you referring to?

Hey @sonichi @pcdeadeasy @binary-husky, we have just released a web app based on autogen. You can find the repo here. It is still early days, but we intend to build out a lot of features to help accelerate uptake and also to help non-technical users get the most out of autogen

Sure @pcdeadeasy so you're after an arch diagram to show how the messages are being passed from agent-backend to webapp?

Where can we make contributions and what tech stack is going to be used?

@GoldenWind8 would you like to review #509 ?

New relevant PR: https://github.com/pcdeadeasy/autogen-oss/pull/2

An initial commit on this has been made to the autogen repo in /samples/apps/autogen-assistant .
Some next steps
### Requested Features
- [ ] Make agent selection persistent and based on db entries.
- [ ] Change subtitle to by Multi-Agents
- [ ] Save/export logs from interactions.
- [ ] Use function calling to register and execute functions instead of putting them in prompt
- [ ] Stream messages from agents to UI as they are generated
- [ ] Add other contributed agents: teachable agent, compressible agent, gptassistant agent

@gagb

Moving the task list to new issue here: https://github.com/microsoft/autogen/issues/737

Closing this due to inactivity.
References

AutoGen studio is the emerging reference example of using AutoGen with a web interface.
Roadmap for AutoGen Studio is here #737


Add Config File + Webroot Support + 404 Handling

Config file is config.json at the root of project actually we can define :
API port (9002 by default)
Docker socket emplacement (/var/run/docker.sock by default)
Webroot (/ by default)

👍

👍


flutter_attach integration test is flaky

Seen this a couple of times while running all the tests on my fork trying to repro other flakiness.
We try to send stop to both the run instance and the attach instance. However the second one often fails saying it can't find the app (which I think is valid, because they were the same running app, so sending a stop should stop!).
[+ 38597]    [{"event":"app.start","params":{"appId":"a13fe6c4-f623-47ef-8243-e4ae024f0627","deviceId":"flutter-tester","directory":null,"supportsRestart":true}}]
[+ 39036]    Error 1001 received from application: File system already exists
[+ 39062]    [{"event":"app.debugPort","params":{"appId":"a13fe6c4-f623-47ef-8243-e4ae024f0627","port":49446,"wsUri":"ws://<IP_ADDRESS>:49446/ws","baseUri":"file:///var/folders/xb/469gd9j941bc7v3mltn7zgb40000gn/T/flutter_attach_test.J5PDkPzZS2gg/flutter_attach_test.J5PDkP/"}}]
[+ 40921]    [{"event":"app.progress","params":{"appId":"a13fe6c4-f623-47ef-8243-e4ae024f0627","id":"0","progressId":null,"message":"Syncing files to device Flutter test device..."}}]
[+ 51887]    [{"event":"app.progress","params":{"appId":"a13fe6c4-f623-47ef-8243-e4ae024f0627","id":"0","progressId":null,"finished":true}}]
[+ 51913]    [{"event":"app.started","params":{"appId":"a13fe6c4-f623-47ef-8243-e4ae024f0627"}}]
[+ 51920]    [{"id":1,"method":"app.restart","params":{"appId":"a13fe6c4-f623-47ef-8243-e4ae024f0627","fullRestart":false,"pause":false}}]
[+ 51932]    [{"event":"app.progress","params":{"appId":"a13fe6c4-f623-47ef-8243-e4ae024f0627","id":"1","progressId":"hot.reload","message":"Initializing hot reload..."}}]
[+ 52938]    [{"event":"app.progress","params":{"appId":"a13fe6c4-f623-47ef-8243-e4ae024f0627","id":"2","progressId":null,"message":"Syncing files to device Flutter test device..."}}]
[+ 53139]    [{"event":"app.progress","params":{"appId":"a13fe6c4-f623-47ef-8243-e4ae024f0627","id":"2","progressId":null,"finished":true}}]
[+ 53498]    [+18374 ms] topLevelFunction
[+ 53664]    [{"event":"app.progress","params":{"appId":"a13fe6c4-f623-47ef-8243-e4ae024f0627","id":"1","progressId":"hot.reload","finished":true}}]
[+ 53668]    Reloaded 0 of 403 libraries in 1,732ms.
[+ 53670]    [{"id":1,"result":{"code":0,"message":"Reloaded 0 of 403 libraries"}}]
[+ 53687]    Closing VM service
[+ 53698]    Stopping app
[+ 53698]    [{"id":1,"method":"app.stop","params":{"appId":"91f5f452-f3ec-4b68-9980-99547ea191f5"}}]
[+ 53713]    [ +215 ms] DevFS: Deleting filesystem on the device (file:///var/folders/xb/469gd9j941bc7v3mltn7zgb40000gn/T/flutter_attach_test.J5PDkPt4kxeI/flutter_attach_test.J5PDkP/)
[+ 53715]    [   +1 ms] _deleteDevFS: {fsName: flutter_attach_test.J5PDkP}
[+ 53722]    [   +6 ms] DevFS: Deleted filesystem on the device (file:///var/folders/xb/469gd9j941bc7v3mltn7zgb40000gn/T/flutter_attach_test.J5PDkPt4kxeI/flutter_attach_test.J5PDkP/)
[+ 53727]    [   +5 ms] ext.flutter.exit: {isolateId: isolates/232555921}
[+ 53783]    [  +42 ms] Service protocol connection closed.
[+ 53784]    Lost connection to device.
[+ 53966]    [ +195 ms] Application finished.
[+ 53967]    [{"id":1,"result":true}]
[+ 53968]    Waiting for process to end
[+ 53970]    [{"event":"app.stop","params":{"appId":"91f5f452-f3ec-4b68-9980-99547ea191f5"}}]
[+ 54003]    [  +36 ms] "flutter run" took 52,412ms.
[+ 54079]    Process exited (0)
[+ 54079]    Stopping app
[+ 54080]    [{"id":2,"method":"app.stop","params":{"appId":"a13fe6c4-f623-47ef-8243-e4ae024f0627"}}]
[+ 54092]    [{"event":"app.stop","params":{"appId":"a13fe6c4-f623-47ef-8243-e4ae024f0627"}}]
[+ 54116]    [{"id":2,"error":"app 'a13fe6c4-f623-47ef-8243-e4ae024f0627' not found","trace":"#0      AppDomain.stop (package:flutter_tools/src/commands/daemon.dart:508:7)\n<asynchronous suspension>\n#1      Domain.handleCommand.<anonymous closure> (package:flutter_tools/src/commands/daemon.dart:189:34)\n#2      new Future.sync (dart:async/future.dart:224:31)\n#3      Domain.handleCommand (package:flutter_tools/src/commands/daemon.dart:187:9)\n#4      Daemon._handleRequest (package:flutter_tools/src/commands...
53:00 +434 ~1 -4: test/integration/flutter_attach_test.dart: attached process can hot reload [E]
  Unexpected error response
  [{"id":2,"error":"app 'a13fe6c4-f623-47ef-8243-e4ae024f0627' not found","trace":"#0      AppDomain.stop (package:flutter_tools/src/commands

Maybe easier to understand with the app ID highlighted:

Seen again in https://cirrus-ci.com/task/4673346587328512

This should've been fixed by the swap to detaching correctly (#21154). If anyone sees it again, lmk.


Interface unions type checking

TypeScript Version:  2.4.0
Code
interface Foo {
  a: string;
}

interface Bar extends Foo {
  b: string;
  c: string;
}

// d is neither foo nor bar!
const d: Foo | Bar = {
  a: 'lol',
  b: 'kek',
};

Expected behavior:
You would expect the code above to throw an error as d can not be resolved to type foo or type bar.
Actual behavior:
Code compiles without error.

duplicate of #14383?

Yeah, thanks.


[Bug]: pysmi's mibdump no longer supports generating PySNMP code for MIB instances

Expected behavior
I expect the mibdump tool to be able to generate code for MIB instances, as explained at https://docs.lextudio.com/snmpresponder/mib-implementation/.
Actual behavior
The flag used in the docs (--destination-template) no longer exists in the current implementation of mibdump (pysmi-lextudio 1.4.2). The source for mibdump which converts to PySNMP output still shows the use of a dstTemplate variable, but there's no longer any way to set it through the regular mibdump tool.
Is it still possible to generate code for MIB instances at all with mibdump or is it advised to simply write it yourself?
Python package information
1.4.2
Operating system information
Ubuntu 22.04.04 LTS
Python information
3.12.1
(Optional) Contents of your test script
No response
Relevant log output
No response

We found this both a documentation issue and code merge issue. Will work on it later.

PySMI 1.4.3 was just released with the missing command line switch. You might test if that helps.
The documentation is still out-of-date, and we will see into that in the coming weeks.