There is no possibility to get reference to object by it's instance id in GDNative c++

In gdscript you can get instance by it's unique id. But there is not the same method at GDNative C++

Closing, as feature proposals should be discussed on the Godot proposals repository. This repository is now used for bug reports only.
Make sure to follow the proposal template when opening a new proposal.

Closing, as feature proposals should be discussed on the Godot proposals repository. This repository is now used for bug reports only.
Make sure to follow the proposal template when opening a new proposal.


Support for Shelly Gas

Hi,
i have bought a Shelly Gas but this product seems to not be supported from your plugin.
https://shelly-api-docs.shelly.cloud/#shelly-gas
What do you need for implementing it?
This is something of util.
The domoticz log of device:
MQTT message: shellies/shellygas-10521CF29E18/sensor/operation normal
MQTT message: shellies/shellygas-10521CF29E18/sensor/gas none
MQTT message: shellies/shellygas-10521CF29E18/sensor/self_test not_completed
MQTT message: shellies/shellygas-10521CF29E18/valve/0/state not_connected
MQTT message: shellies/shellygas-10521CF29E18/sensor/concentration 0
the log of mosquitto
1611744512: Received PUBLISH from shellygas-10521CF29E18 (d0, q0, r0, m0, 'shellies/shellygas-10521CF29E18/sensor/operation', ... (6 bytes))
1611744512: Received PUBLISH from shellygas-10521CF29E18 (d0, q0, r0, m0, 'shellies/shellygas-10521CF29E18/sensor/gas', ... (4 bytes))
1611744512: Received PUBLISH from shellygas-10521CF29E18 (d0, q0, r0, m0, 'shellies/shellygas-10521CF29E18/sensor/self_test', ... (13 bytes))
1611744512: Received PUBLISH from shellygas-10521CF29E18 (d0, q0, r0, m0, 'shellies/shellygas-10521CF29E18/valve/0/state', ... (13 bytes))
1611744512: Received PUBLISH from shellygas-10521CF29E18 (d0, q0, r0, m0, 'shellies/shellygas-10521CF29E18/sensor/concentration', ... (1 bytes))

fixed in new version


Boomerang emoji

A Boomerang is a traditional Australian Aboriginal hunting weapon, but also a toy and a symbol for always coming back / returning.

🪃 Boomerang


Added Fruit Cutter Game

Added this game under Games folder.
Tech stack: Html5,css,Javascript

Sure I can !!!


reaction MAR03099 is missing a PMID prefix

Description of the issue:
In the human1 excel file the reaction 'MAR03099' is missing a PMID prefix for the last reference in the "REFERENCE" field
Expected feature/value/output:
'PMID:8012501;PMID:8188243;PMID:13295248'
Current feature/value/output:
'PMID:8012501;PMID:8188243;13295248'
I hereby confirm that I have:

[ ] Tested my code on my own computer for running the model
[ ] Done this analysis in the main branch of the repository
[ ] Checked that a similar issue does not exist already

@avlant thanks for reporting this :-)

Through the merging of #428 this issue is resolved.


[English] Serverless Eventing

1. Please describe why this term needs to be added
What this term is about? (briefly)

Serverless Eventing is essentially binding event sources to their sinks in a declarative manner

Why this term needs to be added? (briefly)

With Knative being added to the CNCF, defining serverless eventing (or just eventing) would be of value as this is what Knative Eventing does

2. Checklist

[X] There is no existing issue yet. (shift+click to check existing issues)
[X] I understand that maintainers will assess if the term should be part of the Glossary. (Please be patient)
[X] I want to work on this term. (If not checked, maintainers will assign another volunteer)

(Note)
Maintainers will assign a label after assessment procedure.
(from triage/awaiting to triage/accepted or triage/not accepted)
A contributor can be assigned to this issue after the issue get the triage/accepted label.
The assignee needs to check Style Guide.

@jasonsmithio would you be open to doing simply eventing, or ideally a more fundamental term around event driven architectures? As of right now the glossary is a little light on serverless terms and an entry that talks about the core concepts behind event driven architectures seems important.
Serverless Eventing seems too specific to be added at this time.

@JasonMorgan good point. Serverless Eventing and Eventing are similar yet different architectures. However, I agree on doing general and then doing specific definitions. I would be happy to make this an "Event Driven Architecture" definition first

@jasonsmithio thanks for adding the proposal. I saw that you also created a PR already. In the future, I would like to ask for a little more patience before actually starting. A term has to be accepted for the glossary first (label triage/accepted indicated that). Also, make sure to mention the approvers/maintainers in the slack channel and only work on 1 term at a time :)

Howdy,
Cool, a bit overzealous on my end.

This issue has been resolved by #637 and #976.
@jasonsmithio thank you for your hard work and devotion!


Running Calculator with Geforce Now

I'm using GeForce Now to run Anno. Is there a possibility to get it to work?
Is just says "Anno 1800 window not found"

Thanks for the quick answer.
Now i get another error

I'm running it on my Surface with max. resolution 2736x1824 and the resolution of the game is 1920x1200 if that helps

Can you make two screenshots with global and island population open, as shown here: https://github.com/NiHoel/Anno1800UXEnhancer/blob/master/instructions_0.png
Please set Ubisoft Connect to store .png

and use F12 to take the screenshots.
The server works fine despite the error. The only thing that won't work is extracting the population number from the HUD pop up.

I don't use the Ubisoft Connect. I just login with GeForce Now, so there I can't change anything.
GeForce Now always starts in full screen mode (2736x1824) and I can't change that. The game runs in 1920x1200 but it is not shown in the picture because it's like a remote control.

Redownload the image_recon folder from the link above.

I just gave it a quick try, and it works! Great job!
Thanks you so much for the super quick support. I'll get in touch when I tried the UXEnhancer


Option picker for Masking Patient values

This PR introduces a picker for the mask constructorArg within the patientExtractor config section of the Config Editor. Though they're not currently functional, the mask values that will soon be added to the MEF are included options as well.

DP1 - We could probably update the MEF version now 😄

DP2 - Needs a rebase

DP3 - Small thing, but I noticed that if you click on the label of a checkbox (e.g. the text-label telecom next to the checkbox) it alternates the checked-value for the wrong field. After doing some digging, I learned that providing an id prop to the Form.Check component will solve this issue (see https://github.com/react-bootstrap/react-bootstrap/issues/4056#issuecomment-755458634).
tl;dr let's add an id prop to the Form.Check component that's identical with the key prop.


Rust 1.61 in Linux does no add resources to the EXE

Since Rust 1.61 1, the linker no longer includes the static libraries with the --whole-archive flag. This means that the resource.o file is only added to the final EXE if it defines any symbol undefined elsewhere. But resource objects do not define any symbol at all!
There are several solutions for this that I can think of:
Solution n.1: The fancy one.
-        println!("cargo:rustc-link-lib=static=resource");
+        println!("cargo:rustc-link-lib=static:+whole-archive=resource");

This forces the --whole-archive flag for this particular library, restoring the old behavior. The drawback is that I think it will not be backwards compatible, it will require Rust 1.61.
Solution n.2: The classic.
-        println!("cargo:rustc-link-lib=static=resource");
+        println!("cargo:rustc-link-args={}", output.display()); // .../resource.o

By passing the name of the object file instead of the library it will link the given object into the EXE, unconditionally. The nice thing is that it is backwards compatible. And the call to AR is not longer needed.
Solution #3: The hack.
-        let output = PathBuf::from(output_dir).join("resource.o");
+        let output = PathBuf::from(output_dir).join("libresource.a");

And then removing the call to AR. Then when linking the static library resource the linker will find the libresource.a, that is not an archive but an object, thus it is included unconditionally. It is similar to n.2 but it still uses the static flag.

The drawback is that I think it will not be backwards compatible, it will require Rust 1.61.

You can use https://crates.io/crates/version_check to do it conditionally.
That's better than hacks, at least.

i just downgraded to 1.60 because i wasted 2.5 days with this cross compilation problem

I probably run into the same problem with my tp-note/build.rs.
Could you please publish a (minor) version upgrade?

This also affects Windows/MINGW.
(This issue's title happens to be too narrow, I almost not looked here before submitting a duplicate :) )
@rodrigorc's solution 1 does not seem to work:
error: overriding linking modifiers from command line is not supported
rustc 1.64.0-nightly (4493a0f47 2022-08-02)
From this comment by @petrochenkov I think this will be fixed by #94962, though I can be wrong.
Trying to use a link attribute:
#[link(name="resource", kind="static", modifiers="+whole-archive")]
extern {}

produces the same error: overriding linking modifiers from command line is not supported.
I only found this to work:
	println!("cargo:rustc-link-arg=-Wl,--whole-archive");
	println!("cargo:rustc-link-arg=-Wl,-Bstatic");
	println!("cargo:rustc-link-arg=-lresource");
	println!("cargo:rustc-link-arg=-Wl,--no-whole-archive");

It is ugly but could do as a stop-gap solution until a fix is available.

This bug breaks this crate completely for up to date Rust toolchains.
@mxre would it be possible to accept PR #41 and publish the fix on crates.io? The crate silently stops working whenever someone updates their toolchain to Rust 1.61 or higher, leading to unexpected outcomes and troubleshooting for every person who uses it.

A temporary solution until the crate gets fixed would be to add @Nilstrieb's repo to Cargo.toml instead:
winres = { git = "https://github.com/Nilstrieb/winres", branch = "linking-flags" }

A temporary solution until the crate gets fixed would be to add @Nilstrieb's repo to Cargo.toml instead:
winres = { git = "https://github.com/Nilstrieb/winres", branch = "linking-flags" }

I know. But then you cannot publish it on crates.io. Ultimately, if this bug is not fixed, a fork is required.

In early November 2022, I wrote an email to @mxre with the question whether he could accept PR #41 or give a short feedback on how to proceed. I did not receive an answer.
Hence, with utmost respect for the original work, I forked the repository and created a new crate that is maintained again.
https://github.com/BenjaminRi/winresource
https://crates.io/crates/winresource
Everything is identical, except that this bug is fixed and the name is winresource. I will also continue to maintain the crate to the best of my ability and available time. Whether you switch to the new crate or use a workaround for the time being is up to you, of course.


nativefier --upgrade saves upgraded app in current working directory instead of directory where app currently is located

Homework

[x] I looked at nativefier --help and https://github.com/nativefier/nativefier/blob/master/API.md
[x] I checked the Troubleshooting section of the README.
[ ] I searched existing issues, open & closed. Yes, my bug is new.
[x] I'm using the latest version available at https://github.com/nativefier/nativefier/releases

Bug description
nativefier --upgrade saves upgraded app in current working directory instead of directory where app currently is located.
Steps to reproduce
❯ nativefier --upgrade ~/Applications/Example\ Domain-darwin-x64/Example\ Domain.app --verbose
Running in verbose mode! This will produce a mountain of logs and is recommended only for troubleshooting or if you like Shakespeare.

Performing async options post-processing.
mozilla/5.0 (macintosh; intel mac os x 10_12_5) applewebkit/537.36 (khtml, like gecko) chrome/89.0.4389.82 safari/537.36 not found in [ 'edge', 'firefox', 'safari' ]
Got icon from options. Using it, no inferring needed
Got name Example Domain from options. No inferring needed
Sanitized filename for Example Domain : Example Domain
options {
  packager: {
    appCopyright: undefined,
    appVersion: undefined,
    arch: 'x64',
    asar: false,
    buildVersion: undefined,
    darwinDarkModeSupport: true,
    dir: '/Users/USER/.n/lib/node_modules/nativefier/app',
    electronVersion: '12.0.10',
    icon: '/Users/USER/Applications/Example Domain-darwin-x64/Example Domain.app/Contents/Resources/electron.icns',
    name: 'Example Domain',
    out: '/Users/USER',
    overwrite: true,
    platform: 'darwin',
    portable: false,
    targetUrl: 'https://example.com/',
    tmpdir: false,
    upgrade: true,
    upgradeFrom: '/Users/USER/Applications/Example Domain-darwin-x64/Example Domain.app',
    win32metadata: { ProductName: '', InternalName: '', FileDescription: '' }
  },
  nativefier: {
    accessibilityPrompt: true,
    alwaysOnTop: false,
    backgroundColor: null,
    basicAuthPassword: null,
    basicAuthUsername: null,
    blockExternalUrls: false,
    bookmarksMenu: null,
    bounce: false,
    browserwindowOptions: {},
    clearCache: false,
    counter: false,
    crashReporter: undefined,
    disableContextMenu: false,
    disableDevTools: false,
    disableGpu: false,
    diskCacheSize: null,
    disableOldBuildWarning: false,
    enableEs3Apis: false,
    fastQuit: false,
    fileDownloadOptions: {},
    flashPluginDir: null,
    fullScreen: false,
    globalShortcuts: null,
    hideWindowFrame: false,
    ignoreCertificate: false,
    ignoreGpuBlacklist: false,
    inject: [],
    insecure: false,
    internalUrls: null,
    lang: undefined,
    maximize: false,
    nativefierVersion: '44.0.0',
    processEnvs: {},
    proxyRules: null,
    showMenuBar: false,
    singleInstance: false,
    titleBarStyle: null,
    tray: false,
    userAgent: 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.82 Safari/537.36',
    userAgentHonest: false,
    verbose: true,
    versionString: undefined,
    width: 1280,
    height: 800,
    minWidth: undefined,
    minHeight: undefined,
    maxWidth: undefined,
    maxHeight: undefined,
    widevine: false,
    x: undefined,
    y: undefined,
    zoom: 1
  }
}

Preparing Electron app...
Copying electron app from /Users/USER/.n/lib/node_modules/nativefier/app to /var/folders/x4/d6xhrn615_15s2bdvqp7rtw80000gr/T/nativefier-16-52-34-app--38131-223qXQkZDU4B
Writing app config to /var/folders/x4/d6xhrn615_15s2bdvqp7rtw80000gr/T/nativefier-16-52-34-app--38131-223qXQkZDU4B/nativefier.json
No files to inject, skipping copy.
Updating /var/folders/x4/d6xhrn615_15s2bdvqp7rtw80000gr/T/nativefier-16-52-34-app--38131-223qXQkZDU4B/package.json 'name' field to example-domain-nativefier-182cce

Converting icons...
Building for macOS and icon is already a .icns, no conversion needed
Copying icons if necessary
No copying necessary on macOS; aborting

Packaging... This will take a few seconds, maybe minutes if the requested Electron isn't cached yet...
  electron-packager Electron Packager 15.2.0
  electron-packager Node v16.3.0
  electron-packager Host Operating system: darwin 17.7.0 (x64) +0ms
  electron-packager Packager Options: {"arch":"x64","asar":false,"darwinDarkModeSupport":true,"dir":"/var/folders/x4/d6xhrn615_15s2bdvqp7rtw80000gr/T/nativefier-16-52-34-app--38131-223qXQkZDU4B","electronVersion":"12.0.10","icon":"/Users/USER/Applications/Example Domain-darwin-x64/Example Domain.app/Contents/Resources/electron.icns","name":"Example Domain","out":"/Users/USER","overwrite":true,"platform":"darwin","portable":false,"targetUrl":"https://example.com/","tmpdir":false,"upgrade":true,"upgradeFrom":"/Users/USER/Applications/Example Domain-darwin-x64/Example Domain.app","win32metadata":{"ProductName":"","InternalName":"","FileDescription":""}} +1ms
  electron-packager Target Platforms: darwin +0ms
  electron-packager Target Architectures: x64 +0ms
  electron-packager Inferring appVersion from version in /var/folders/x4/d6xhrn615_15s2bdvqp7rtw80000gr/T/nativefier-16-52-34-app--38131-223qXQkZDU4B/package.json +0ms
  electron-packager Application name: Example Domain +15ms
  electron-packager Target Electron version: 12.0.10 +0ms
  electron-packager Ignored path regular expressions: [
  '/package-lock\\.json$',
  '/yarn\\.lock$',
  '/\\.git($|/)',
  '/node_modules/\\.bin($|/)',
  '\\.o(bj)?$'
] +0ms
  electron-packager Downloading Electron with options {"platform":"darwin","arch":"x64","version":"12.0.10","artifactName":"electron"} +0ms
Packaging app for platform darwin x64 using electron v12.0.10
  electron-packager Creating /Users/USER/darwin-x64-template +5ms
  electron-packager Extracting /Users/USER/Library/Caches/electron/fe82eb0272a083ac9c8100be1631e54e7199d39ec5441c611bd374f326bddbaa/electron-v12.0.10-darwin-x64.zip to /Users/USER/darwin-x64-template +1ms
  electron-packager Initializing app in /Users/USER/Example Domain-darwin-x64 from /Users/USER/darwin-x64-template template +0ms
  electron-packager Ignored paths based on the out param: [
  '/Users/USER/Example Domain-darwin-x64',
  '/Users/USER/Example Domain-darwin-arm64',
  '/Users/USER/Example Domain-linux-ia32',
  '/Users/USER/Example Domain-linux-x64',
  '/Users/USER/Example Domain-linux-armv7l',
  '/Users/USER/Example Domain-linux-arm64',
  '/Users/USER/Example Domain-linux-mips64el',
  '/Users/USER/Example Domain-mas-x64',
  '/Users/USER/Example Domain-mas-arm64',
  '/Users/USER/Example Domain-win32-ia32',
  '/Users/USER/Example Domain-win32-x64',
  '/Users/USER/Example Domain-win32-arm64'
] +4s
  electron-packager Copying icon "/Users/USER/Applications/Example Domain-darwin-x64/Example Domain.app/Contents/Resources/electron.icns" to app's Resources as "electron.icns" +0ms
  electron-packager Renaming Electron to Example Domain in /Users/USER/Example Domain-darwin-x64/Electron.app/Contents/MacOS +92ms
  electron-packager Renaming Electron Helper to Example Domain Helper in /Users/USER/Example Domain-darwin-x64/Electron.app/Contents/Frameworks/Electron Helper.app/Contents/MacOS +1ms
  electron-packager Renaming Electron Helper (Renderer) to Example Domain Helper (Renderer) in /Users/USER/Example Domain-darwin-x64/Electron.app/Contents/Frameworks/Electron Helper (Renderer).app/Contents/MacOS +1ms
  electron-packager Renaming Electron Helper (Plugin) to Example Domain Helper (Plugin) in /Users/USER/Example Domain-darwin-x64/Electron.app/Contents/Frameworks/Electron Helper (Plugin).app/Contents/MacOS +0ms
  electron-packager Renaming Electron Helper (GPU) to Example Domain Helper (GPU) in /Users/USER/Example Domain-darwin-x64/Electron.app/Contents/Frameworks/Electron Helper (GPU).app/Contents/MacOS +0ms
  electron-packager Renaming Electron Helper.app to Example Domain Helper.app in /Users/USER/Example Domain-darwin-x64/Electron.app/Contents/Frameworks +0ms
  electron-packager Renaming Electron Helper (Renderer).app to Example Domain Helper (Renderer).app in /Users/USER/Example Domain-darwin-x64/Electron.app/Contents/Frameworks +0ms
  electron-packager Renaming Electron Helper (Plugin).app to Example Domain Helper (Plugin).app in /Users/USER/Example Domain-darwin-x64/Electron.app/Contents/Frameworks +1ms
  electron-packager Renaming Electron Helper (GPU).app to Example Domain Helper (GPU).app in /Users/USER/Example Domain-darwin-x64/Electron.app/Contents/Frameworks +0ms

Finalizing build...
App built to /Users/USER/Example Domain-darwin-x64, move to wherever it makes sense for you and run the app bundle.

Expected behavior
Saves updated app to ~/Applications
Actual behavior
Saves updated app to home folder ~/
(current working directory)
Debug info

Console logs of your nativefier build command, with --verbose flag
If the bug happens at app run time, the in-app DevTools console logs (open it with F12)
Error messages
Screenshots
Anything else relevant!

Context
Where I discovered this:
https://github.com/mattruzzi/nativefier-gui/tree/feat--Upgrade-existing-apps
I was trying to add a menu to nativefier-gui update existing nativefier apps and was running the nativfier programmatic API and got the following:
Preparing Electron app...

Converting icons...

Packaging... This will take a few seconds, maybe minutes if the requested Electron isn't cached yet...
Packaging app for platform darwin x64 using electron v12.0.10
Error: Invalid package /Users/USER/Documents/github2/nativefier-gui-2/darwin-x64-template/Electron.app/Contents/Resources/default_app.asar
    at createError (electron/js2c/asar_bundle.js:5:1585)
    at Object.t.<computed> [as open] (electron/js2c/asar_bundle.js:5:2419)
    at _openWriteFs (internal/fs/streams.js:370:15)
    at new WriteStream (internal/fs/streams.js:343:5)
    at createWriteStream (fs.js:2008:10)
    at Extractor.extractEntry (/Users/USER/Documents/github2/nativefier-gui-2/node_modules/electron-packager/node_modules/extract-zip/index.js:132:34)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at ZipFile.<anonymous> (/Users/USER/Documents/github2/nativefier-gui-2/node_modules/electron-packager/node_modules/extract-zip/index.js:65:11)

function updateApp(path) {
    const appPath = dialog.showOpenDialogSync(null, {
        properties: ["openFile", "openDirectory"],
        buttonLabel: "Update Nativefier App",
    })[0];
    console.log("Upgrading " + appPath);
    const args = { "upgrade": appPath }
    nativefier(args, function (error, appPath) {
        if (error) {
            console.error(error);
            return;
        }
        console.log("App has been nativefied to", appPath);
    });
}

Nativefier: 44.0.0
Node.js: v16.3.0
Npm: 7.16.0
OS: Mac OS X 10.13.6
Is it a regression? If yes, what's the last working / first broken version?
Additional context: (for example: "I'm behind a proxy, with configuration X and protocol Y")

I noticed this yesterday as well. Looking into a fix but am currently at the "how did this ever work?" stage of debugging.

@TheCleric @ronjouch This still is an issue on<EMAIL_ADDRESS>cd /tmp
git clone https://github.com/mattruzzi/nativefier-gui.git --branch feat--Upgrade-existing-apps
cd nativefier-gui
npm install
npm start

Then choose File > Update Existing App and select a nativefier app. It will create a folder called darwin-x64-template (or whatever your platform is) in /tmp/nativefier-gui.
❯ ls
README.md           node_modules        package.json        src
darwin-x64-template package-lock.json   screenshot.png

Now I am seeing a slightly different issue where it keeps the old app and places the upgraded version inside a folder in the same folder as the old app:
❯ nativefier --upgrade /Users/USER/Applications/Duolingo-darwin-x64/Duolingo.app

Preparing Electron app...

Converting icons...

Packaging... This will take a few seconds, maybe minutes if the requested Electron isn't cached yet...
Packaging app for platform darwin x64 using electron v13.1.7

Finalizing build...
App built to /Users/USER/Applications/Duolingo-darwin-x64/Duolingo-darwin-x64, move to wherever it makes sense for you and run the app bundle.

~ 33s
❯

Now I am seeing a slightly different issue where it keeps the old app and places the upgraded version inside a folder in the same folder as the old app:

Weird. I don't think I've even touched any of this yet...


Add CS50x to README.md

thanks for the great link michelle !!

My pleasure! I started my computer science journey with CS50. 🙌


Fixing non-awsvpc networking issue #39 and add volumes and mount points

This pull request fixes issue #39 where non-awsvpc network modes will not deploy
The problem
	func (p *Plugin) setupServiceNetworkConfiguration() *ecs.NetworkConfiguration {
	netConfig := ecs.NetworkConfiguration{AwsvpcConfiguration: &ecs.AwsVpcConfiguration{}}

	if p.NetworkMode != ecs.NetworkModeAwsvpc {
		return &netConfig
	}

When we aren't using awsvpc mode, we return a ecs.NetworkConfiguration{AwsvpcConfiguration: &ecs.AwsVpcConfiguration{}} which looks like essentially a bunch of nil structs, but we have a non nil AwsvpcConfiguration pointer field pointing to an empty AwsVpcConfiguration struct.
When NewtworkConfiguration calls its Validate() method:
	if s.AwsvpcConfiguration != nil {
		if err := s.AwsvpcConfiguration.Validate(); err != nil {
			invalidParams.AddNested("AwsvpcConfiguration", err.(request.ErrInvalidParams))
		}
	}

AwsvpcConfiguration is not nil so AwsvpcConfiguration.Validate() is called.
and AwsvpcConfiguration.Validate() checks for required field Subnets
func (s *AwsVpcConfiguration) Validate() error {
	invalidParams := request.ErrInvalidParams{Context: "AwsVpcConfiguration"}
	if s.Subnets == nil {
		invalidParams.Add(request.NewErrParamRequired("Subnets"))
	}

and therefore we get the error:
2020/01/11 05:48:15 InvalidParameter: 1 validation error(s) found.
- missing required field, UpdateServiceInput.NetworkConfiguration.AwsvpcConfiguration.Subnets.

Therefore instead of:
	func (p *Plugin) setupServiceNetworkConfiguration() *ecs.NetworkConfiguration {
	netConfig := ecs.NetworkConfiguration{AwsvpcConfiguration: &ecs.AwsVpcConfiguration{}}

	if p.NetworkMode != ecs.NetworkModeAwsvpc {
		return &netConfig
	}

We should return a nil if p.NetworkMode != ecs.NetworkModeAwsvpc like so:
	func (p *Plugin) setupServiceNetworkConfiguration() *ecs.NetworkConfiguration {
	netConfig := ecs.NetworkConfiguration{AwsvpcConfiguration: &ecs.AwsVpcConfiguration{}}

	if p.NetworkMode != ecs.NetworkModeAwsvpc {
		return nil
	}

So we should only pass a NetworkConfiguration if the networktype is awsvpc
Per this ECS API page networkConfiguration is not a required parameter to pass for UpdateServiceRequest()

I was going to separate out the fix for #39 and the addition of mount_points and volumes for #21 but I guess they're all coming through in one pull request now.

Thanks @joescharf I'll merge and tag for a new release :)


Add docs for prometheus metrics

We offer a way for prometheus to grab metrics. We should document that somewhere (e.g. github wikis or a designated readme.md file)

Everything related to prometheus and grafana is documented in the GitHub wiki here: https://github.com/d-Rickyy-b/certstream-server-go/wiki/Collecting-and-Visualizing-Metrics


EVEREST-384 Validate DatabaseCluster name

EVEREST-384 Validate DatabaseCluster name

@oksana-grishchenko please merge it to the release branch as well


Add PigeonExt

Adds support for parallel tempering for a PEtabODEProblem.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 95.55556% with 2 lines in your changes missing coverage. Please review.

Project coverage is 83.14%. Comparing base (8ad99bf) to head (a650d52).
Report is 35 commits behind head on main.

Files
Patch %
Lines

ext/PEtabPigeonsExtension.jl
92.59%
2 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #186      +/-   ##
==========================================
+ Coverage   83.02%   83.14%   +0.12%
==========================================
  Files          57       59       +2
  Lines        4836     4877      +41
==========================================
+ Hits         4015     4055      +40
- Misses        821      822       +1

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


Introduce logging facilities?

There are certain cases where it might be nice to warn with a logger (e.g. network ambiguity during decoding). Is using the logging module consistent with design goals here?

Yes. I would love that.

I am proposing the integration of the Python logging module into the codebase to introduce logging capabilities with various levels (DEBUG, INFO, WARNING, ERROR). This will enable us to enhance debugging, provide important warnings when needed and ultimately improve the overall robustness of our code and support for users.


How to get a client ID?

It is not clear how to get a client ID to run the getting started program. I tried assigning the variable clientIDFromAzureAppRegistration using a client ID from an app  that I already had from https://apps.dev.microsoft.com/#/appList. When I ran the getting started program, I was able to go through most of the authentication windows, but it failed with a window that said
"Sign In
Sorry, but we’re having trouble signing you in.
We received a bad request.
Additional technical information:
Correlation ID: 63b87501-9df5-44dd-9c74-de9f470bed12
Timestamp: 2016-11-21 20:07:14Z
AADSTS65005: The client application has requested access to resource 'https://api.azuredatacatalog.com'. This request has failed because the client has not specified this resource in its requiredResourceAccess list."
I do not know what to do next.

Have you resolved your issue? I am getting the same message, thx.


Electron Cash 2.9.4 - not sure i can access BCH...

So i decided to wait a while before trying to claim BCH from my electron cash wallet as I could see there were some teething problems at the beginning, particularly relating to wallets created in Electrum using TrustedCoin 2fa (like mine).
Am I right in saying that on the latest Electron Cash release there is still no way to get around this?
I have the seed for my original Electrum wallet and have even figured out a way to access a 'watching only' version of my Electron Cash wallet, but I cant do a full restore using my seed...
When I enter in Seed on Electron Cash wallet for either standard or multisig, the 'next' box remains greyed out..presumably because it identifies it as a 2fa seed which seems to not be compatible.
I would very much appreciate some guidance or even just an explanation to say its not ready yet but we're working on it at least.
Many thanks

#41

Thanks to Jonald Fyookball for responding, however, I would like to add specifically which advice on #41 worked as I went through every suggestion before eventually finding solution at very bottom
Credit to D412
Here is what i did presumably not the only method but it worked.

Use 2.9.2 and create a new 2FA wallet.
Select I already have a seed and put in your wallet´s seed.
Click next and Disable 2FA at the next site.
Open 2.9.4 and create a new standart wallet on 2.9.4
Copy the receiving address from the 2.9.4 wallet.
Open your restored wallet on 2.9.2 and make a transaction to your new 2.9.4 wallet address. Be carefull and sent the full amount, it looks like the old versions have connection problems after one TX (I had to use 2.9.3 for this step since the TX was invalid and did not came through with 2.9.2.)

If someone having trouble with finding the older versions of the Wallet: https://github.com/fyookball/electrum/releases

weird that 2.9.2 worked and not 2.9.3... anyway its nice to have old versions :)  I should put a link to them on the wesbite

It worked for a test tx in 2.9.2 then stopped connecting. The final full tx was done with 2.9.3
However, I believe I still would have needed to create the 2fa wallet in 2.9.2, to be able to disable 2fa as the option to create a 2fa wallet in 2.9.3 didnt appear to exist. I had to open the 2.9.2 created wallet via 2.9.3 to get it to work eventually.
Thanks for the good work @fyookball

@fyookball followed the above with a 2fa wallet in 2.9.2 I see the correct balance, but receiving a Server did not answer error when attempting to send to a 2.9.4 wallet, using electroncash.casharia.com server
any advice on next steps


problem while installing grpc via vcpkg on Apple M1

Host Environment

OS: [macOS Big Sur 11.2.3 Apple M1]
Compiler: Clang 12.0.0

To Reproduce
Steps to reproduce the behavior:
./vcpkg install --recurse --clean-after-build --triplet=arm64-osx grpc
Failure logs
Konstantin, [16 Apr 2021, 02:54:36]:
limarev@MacBook-Air-Konstantin vcpkg % vcpkg install --recurse --clean-after-build --triplet=arm64-osx grpc
Computing installation plan...
The following packages will be built and installed:

abseil[core]:arm64-osx -> 2021-03-24
abseil[core]:x64-osx -> 2021-03-24
c-ares[core]:arm64-osx -> 1.17.1#1
c-ares[core]:x64-osx -> 1.17.1#1
grpc[core]:x64-osx -> 1.33.1#3
grpc[core]:arm64-osx -> 1.33.1#3
openssl[core]:x64-osx -> 1.1.1j
re2[core]:x64-osx -> 2020-10-01
re2[core]:arm64-osx -> 2020-10-01
upb[core]:x64-osx -> 2020-08-19
upb[core]:arm64-osx -> 2020-08-19
zlib[core]:x64-osx -> 1.2.11#9
Additional packages (*) will be modified to complete this operation.
Detecting compiler hash for triplet arm64-osx...
Detecting compiler hash for triplet x64-osx...

-- Using community triplet arm64-osx. This triplet configuration is not guaranteed to succeed.
-- [COMMUNITY] Loading triplet configuration from: /Users/limarev/local/vcpkg/vcpkg/triplets/community/arm64-osx.cmake
-- Downloading https://github.com/abseil/abseil-cpp/archive/997aaf3a28308eba1b9156aa35ab7bca9688e9f6.tar.gz -> abseil-abseil-cpp-997aaf3a28308eba1b9156aa35ab7bca9688e9f6.tar.gz...
-- Extracting source /Users/limarev/local/vcpkg/vcpkg/downloads/abseil-abseil-cpp-997aaf3a28308eba1b9156aa35ab7bca9688e9f6.tar.gz
-- Applying patch fix-cxx-standard.patch
-- Using source at /Users/limarev/local/vcpkg/vcpkg/buildtrees/abseil/src/ca9688e9f6-e4cda1d679.clean
-- Found external ninja('1.10.2').
-- Configuring arm64-osx-dbg
-- Configuring arm64-osx-rel
-- Building arm64-osx-dbg
-- Building arm64-osx-rel
-- Installing: /Users/limarev/local/vcpkg/vcpkg/packages/abseil_arm64-osx/share/abseil/copyright
-- Performing post-build validation
-- Performing post-build validation done
Stored binary cache: /Users/limarev/.cache/vcpkg/archives/d6/d6c93035aef8e62fef02c4bbde35558b706941ff.zip
Building package abseil[core]:arm64-osx... done
Installing package abseil[core]:arm64-osx...
Installing package abseil[core]:arm64-osx... done
Elapsed time for package abseil:arm64-osx: 14.35 s
Starting package 2/12: abseil:x64-osx
Building package abseil[core]:x64-osx...
-- Downloading https://github.com/abseil/abseil-cpp/archive/997aaf3a28308eba1b9156aa35ab7bca9688e9f6.tar.gz -> abseil-abseil-cpp-997aaf3a28308eba1b9156aa35ab7bca9688e9f6.tar.gz...
-- Extracting source /Users/limarev/local/vcpkg/vcpkg/downloads/abseil-abseil-cpp-997aaf3a28308eba1b9156aa35ab7bca9688e9f6.tar.gz
-- Applying patch fix-cxx-standard.patch

-- Using source at /Users/limarev/local/vcpkg/vcpkg/buildtrees/abseil/src/ca9688e9f6-e4cda1d679.clean
-- Found external ninja('1.10.2').
-- Configuring x64-osx-dbg
-- Configuring x64-osx-rel
-- Building x64-osx-dbg
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:146 (message):
Command failed: /usr/local/bin/cmake --build . --config Debug --target install -- -v -j9
Working Directory: /Users/limarev/local/vcpkg/vcpkg/buildtrees/abseil/x64-osx-dbg
See logs for more information:
/Users/limarev/local/vcpkg/vcpkg/buildtrees/abseil/install-x64-osx-dbg-out.log
Call Stack (most recent call first):
scripts/cmake/vcpkg_build_cmake.cmake:105 (vcpkg_execute_build_process)
scripts/cmake/vcpkg_install_cmake.cmake:45 (vcpkg_build_cmake)
ports/abseil/portfile.cmake:32 (vcpkg_install_cmake)
scripts/ports.cmake:142 (include)
Error: Building package abseil:x64-osx failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with ./vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: abseil:x64-osx
Vcpkg version: 2021-01-13-unknownhash

abseil/abseil-cpp#945
grpc/grpc#26000
Additional context
I compile gcc-10 and compile cmake with gcc-10. Then reinstalled vcpkg and tried to install grpc again.
limarev@MacBook-Air-Konstantin ~ % vcpkg install --recurse --clean-after-build --triplet=arm64-osx grpc
Computing installation plan...
The following packages will be built and installed:

grpc[core]:x64-osx -> 1.33.1#3
grpc[core]:arm64-osx -> 1.33.1#3
openssl[core]:x64-osx -> 1.1.1j#1
openssl[core]:arm64-osx -> 1.1.1j#1
protobuf[core]:x64-osx -> 3.15.8
protobuf[core]:arm64-osx -> 3.15.8
re2[core]:x64-osx -> 2020-10-01
re2[core]:arm64-osx -> 2020-10-01
upb[core]:x64-osx -> 2020-08-19
upb[core]:arm64-osx -> 2020-08-19
zlib[core]:x64-osx -> 1.2.11#10
zlib[core]:arm64-osx -> 1.2.11#10
Additional packages (*) will be modified to complete this operation.
Detecting compiler hash for triplet x64-osx...
Detecting compiler hash for triplet arm64-osx...

-- Using cached /Users/limarev/local/vcpkg/downloads/openssl-1.1.1j.tar.gz
-- Extracting source /Users/limarev/local/vcpkg/downloads/openssl-1.1.1j.tar.gz
-- Using source at /Users/limarev/local/vcpkg/buildtrees/openssl/src/1.1.1j-ff1006361a.clean
-- Found external ninja('1.10.2').
-- Configuring x64-osx-dbg
-- Configuring x64-osx-rel
-- Building x64-osx-dbg
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:146 (message):
Command failed: /opt/homebrew/Cellar/cmake/3.20.1/bin/cmake --build . --config Debug --target install -- -v -j9
Working Directory: /Users/limarev/local/vcpkg/buildtrees/openssl/x64-osx-dbg
See logs for more information:
/Users/limarev/local/vcpkg/buildtrees/openssl/install-x64-osx-dbg-out.log

Call Stack (most recent call first):
scripts/cmake/vcpkg_build_cmake.cmake:105 (vcpkg_execute_build_process)
scripts/cmake/vcpkg_install_cmake.cmake:45 (vcpkg_build_cmake)
ports/openssl/unix/portfile.cmake:33 (vcpkg_install_cmake)
ports/openssl/portfile.cmake:21 (include)
scripts/ports.cmake:142 (include)
Error: Building package openssl:x64-osx failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with ./vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: openssl:x64-osx
Vcpkg version: 2021-01-13-unknownhash
Additionally, attach any relevant sections from the log files above.
install-x64-osx-dbg-out.log

duplicate of #17436


rdkit 2023.03.2

Changelog:
License:
Requirements:
Actions:

Clean up the recipe:

Add missing setuptools & wheel to host

Skip py>310 because py-boost hasn't been built for Python 3.11 yet. At the same time, boost 1.82.0 is waiting for review https://github.com/AnacondaRecipes/boost-feedstock/pull/14 and will enable py311 support.
Replace numpy with {{ pin_compatible('numpy') }} in run as we use numpy in host

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_3ekq7dz1s4/clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_3ekq7dz1s4/clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_3ekq7dz1s4/clone/recipe/meta.yaml:82: invalid_url: https://rdkit.org : Not reachable: 406
ERROR: /tmp/abs_3ekq7dz1s4/clone/recipe/meta.yaml:91: invalid_url: https://www.rdkit.org/docs/index.html : Not reachable: 406
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_a2qukmijwu/clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_a2qukmijwu/clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_a2qukmijwu/clone/recipe/meta.yaml:82: invalid_url: https://rdkit.org : Not reachable: 406
ERROR: /tmp/abs_a2qukmijwu/clone/recipe/meta.yaml:91: invalid_url: https://www.rdkit.org/docs/index.html : Not reachable: 406
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_53af2hdfxt/clone/recipe/meta.yaml:37: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_53af2hdfxt/clone/recipe/meta.yaml:38: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_53af2hdfxt/clone/recipe/meta.yaml:39: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_53af2hdfxt/clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_53af2hdfxt/clone/recipe/meta.yaml:45: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_53af2hdfxt/clone/recipe/meta.yaml:46: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_53af2hdfxt/clone/recipe/meta.yaml:84: invalid_url: https://rdkit.org : Not reachable: 406
ERROR: /tmp/abs_53af2hdfxt/clone/recipe/meta.yaml:93: invalid_url: https://www.rdkit.org/docs/index.html : Not reachable: 406
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:38: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:39: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:40: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:46: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:47: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:85: invalid_url: https://rdkit.org : Not reachable: 406
ERROR: clone/recipe/meta.yaml:94: invalid_url: https://www.rdkit.org/docs/index.html : Not reachable: 406
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:38: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:39: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:40: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:46: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:47: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:85: invalid_url: https://rdkit.org : Not reachable: 406
ERROR: clone/recipe/meta.yaml:94: invalid_url: https://www.rdkit.org/docs/index.html : Not reachable: 406
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:38: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:39: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:40: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:46: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:47: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:85: invalid_url: https://rdkit.org : Not reachable: 406
ERROR: clone/recipe/meta.yaml:94: invalid_url: https://www.rdkit.org/docs/index.html : Not reachable: 406
Errors were found

Details

Yes, that file could cause issues if we will upload package before approvals

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:38: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:39: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:40: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:46: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:47: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:85: invalid_url: https://rdkit.org : Not reachable: 406
ERROR: clone/recipe/meta.yaml:94: invalid_url: https://www.rdkit.org/docs/index.html : Not reachable: 406
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:38: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:39: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:40: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:46: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:47: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:85: invalid_url: https://rdkit.org : Not reachable: 406
ERROR: clone/recipe/meta.yaml:94: invalid_url: https://www.rdkit.org/docs/index.html : Not reachable: 406
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:38: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:39: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:40: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:46: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:47: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: clone/recipe/meta.yaml:85: invalid_url: https://rdkit.org : Not reachable: 406
ERROR: clone/recipe/meta.yaml:94: invalid_url: https://www.rdkit.org/docs/index.html : Not reachable: 406
Errors were found


[REQUEST] NodeMCU ESP8266

Name of Board
NodeMCU ESP8266
Board Architecture (i.e: SAMD51, ESP32-S2, ESP32, ...)
ESP8266
Hardware URL
https://www.amazon.com/HiLetgo-Internet-Development-Wireless-Micropython/dp/B010O1G1ES

This issue is marked for Hacktoberfest 2022. If you are participating in Hacktoberfest and want to take on this issue, please first fully read through the guide for adding a new board to Adafruit IO WipperSnapper.
First, make sure you have the required hardware.
Next, for this issue, you must add both the board definition and update WipperSnapper firmware to support this new board.
If you have any questions, comments, or concerns, please feel free to tag me in the comments here, or in your pull request for review.
Happy Hackin'!

https://www.aliexpress.us/item/3256804341678576.html?spm=a2g0o.productlist.0.0.188e10c5WS0hi1&algo_pvid=c41e057e-1a4e-42a3-8feb-a81073ee4167&algo_exp_id=c41e057e-1a4e-42a3-8feb-a81073ee4167-0&pdp_ext_f={"sku_id"%3A"12000030765703491"}&pdp_npi=2%40dis!USD!4.86!0.01!!!!!%402101d8f416681041200348517e47e0!12000030765703491!sea&curPageLogUid=YIgWcGQ19cPA


yes

Is this a bug report?
(Yes)

Did you try recovering your dependencies?

(npm 6.4.1)
Which terms did you search for in User Guide?

(Write your answer here if relevant.)
Environment

(paste the output of the command here)
Steps to Reproduce

(Write your steps here:)

I have removed  node_modules folder and package.lock.json file
updated the npm@latest and installed the package
But the problem persists

Expected Behavior

(to successfully run the program in localhost)
Actual Behavior

(

)
Reproducible Demo

(Paste the link to an example project and exact instructions to reproduce the issue.)

Did you delete the path it's specifying? This is talking about your user directory, not your application directory.


skip available update

Every Few Minutes we get a new VSCode update available message and it would be nice to have a skip version or Do not show until next update option available in drop down menu of Latter button of the popup message (but it currently does not have any drop-down menu).
although it is very good to have VS Code by it's self up to date but inside of a large project we never do any update except when something is broken, but we do update once the project is done.

You can disable updates by changing the setting update.channel: none. You can reenable it when you want to update.


Fix color_mode deprecated

Fixes: https://github.com/wez/govee2mqtt/issues/280

Can we get this merged please ?

Please merge this and publish a new release. The error message is very anoying.


Xcode 10.2 compile error

UITableView.swift line 398
Argument type 'TableViewBondBinder' does not conform to expected type 'TableViewBond'

Have you updated to v7.3.2?

Upgrading to 7.3 was a breaking change with lots of rework due to API changes. I'm on the 6.x version. Using Bond (6.10.2)

@ahamel Looks like you can resolve the issue by adding the TableViewBond protocol to TableViewBondBinder. https://github.com/jonathanfoster/Bond/commit/f1242e65ea3c8c5bae7716cfbc9ab1e7cf9c4d17

I'll try to make a fix release for v6.x.

The fix is released as 6.10.3. Thanks @jonathanfoster for helping out!

Still Have problem with compile On Xcode 10.2

It seems like you are not using version 7.3.2 or 7.3.3 @marek-hajducak .

Thanks so much, this solve it 👍

I ended up using the fix in 6.10.3. Thanks guys!


feat(metadata): Implement Metadata GET /device/name/{name} V2 API

Fix #2804
PR Checklist
Please check if your PR fulfills the following requirements:

[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-examples/blob/master/.github/CONTRIBUTING.md.
What is the current behavior?

Issue Number: #2804
What is the new behavior?
Implement Core Metadata GET /device/name/{name} V2 API according to the API doc
Does this PR introduce a breaking change?

[ ] Yes
[x] No

New Imports
Are there any new imports or modules? If so, what are they used for and why?
Specific Instructions
Are there any specific instructions or things that should be known prior to reviewing?
Other information

Codecov Report

Merging #2811 into master will increase coverage by 0.05%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##           master    #2811      +/-   ##
==========================================
+ Coverage   39.40%   39.46%   +0.05%
==========================================
  Files         166      166
  Lines       13016    13045      +29
==========================================
+ Hits         5129     5148      +19
- Misses       7577     7587      +10
  Partials      310      310

Impacted Files
Coverage Δ

internal/pkg/v2/infrastructure/redis/client.go
0.00% <0.00%> (ø)

internal/pkg/v2/infrastructure/redis/device.go
0.00% <0.00%> (ø)

...nternal/core/metadata/v2/controller/http/device.go
100.00% <100.00%> (ø)

.../core/metadata/v2/controller/http/deviceservice.go
95.12% <100.00%> (ø)

Continue to review full report at Codecov.

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

recheck

Rebased.


Suggested development environment for react-native

I'm struggling to find a good development environment for React Native. Obviously Nuclide is the way to go, but in the meantime, is it possible to have an small guide of the recommended tools for React Native development?
My list of needed items is:

JSHint/JSLint with support for ES6 syntax
Flow checker
JSX support

Currently I'm using Atom with a couple of plugins (atom-ide-flow, jshint) but there are a lot of inconsistencies between those tools or they lack documentation in order to set-up a good React Native development environment. For instance, I can have Flow support but JSHint is always displaying them as errors.

Maybe this is a too broad question, but I think that having a small guide of this can help a lot.

Maybe i'm too old school, but Generic sublime text, Xcode, Google Debugger seem to work. just fine.

@alvaromb I recommend using eslint + babel-eslint + eslint-plugin-react. It handles flow syntax and matches the same linting and transformer used by the react-native packager.

@ide: want to stick something in the docs?

Hi there! This issue is being closed because it has been inactive for a while.
But don't worry, it will live on with ProductPains! Check out it's new home: https://productpains.com/post/react-native/docs-suggested-development-environment-for-react-native


Update component docs

Describe the desired behavior
All of our components should have classes and sx global class names definitions in the individual component docs.
There should be a top level document showing the various ways to style our components (inline styles, className, classes, sx)
Describe the current behavior
Each individual file is expressing how to use sx and there's no guide showing how to use all various styling options.

Is this done now with the updated docs site?

Already been adressed.


Clean up ci config; Fix node-version newline character

Removes an unnecessary npm 3 install from the circle config. We used to need this for API but we no longer do.
We still had a newline character issue with the .node-version file so I'm switching to a template file to fix it.

LGTM

LGTM


Update config wiki

Description
Config wiki page is outdated. Attached draft below.
Additional Information
Known bug:

missing default value
missing all possible options and explanation
shareBasedBanning is replaced by banning

{

  "logging":{

    // Logging level
    // @options "info", "debug"
    // @default "info"
    "level":"info",

    // Enable console log
    // @default
    "enableConsoleLog":true,

    // Enable color in console log
    // @default
    "enableConsoleColors":true,

    // Log file name (full log)
    // @default
    "logFile":"",

    // Folder to store log file(s)
    // @default
    "logBaseDirectory":"",

    // If enabled, separate log file will be stored for each pool as <pool id>.log
    // in the above specific folder.
    "perPoolLogFile":false
  },

  "banning":{

    // Banning manager
    // @options "integrated" or "iptables"
    // @default "integrated"
    // @note "iptables" is linux only option - not yet implemented
    "manager":"integrated",

    // Ban user when junk received
    // @default
    "banOnJunkReceive":true,

    // Ban user when invalid shares received
    // @default
    "banOnInvalidShares":false
  },

  "notifications":{

    // Enable notifications
    // @default
    "enabled":true,

    // Enable email notifications
    "email":{

      // SMTP mail server host
      "host":"smtp.example.com",

      // SMTP mail server port
      "port":587,

      // SMTP mail server user name
      "user":"user",

      // SMTP mail server password
      "password":"password",

      // Email will send from this address
<EMAIL_ADDRESS>
      // Email will send from this name
      "fromName":"pool support"
    },

    "admin":{

      // Enable email notifications to admin
      // @default
      "enabled":false,

      // Email will send to this address
<EMAIL_ADDRESS>
      // Notify when new block found
      // @default
      "notifyBlockFound":true
    }
  },

  // Where to persist shares and blocks to
  "persistence":{

    // Persist to postgresql database
    "postgres":{

      // Postgres server host
      // @default
      "host":"<IP_ADDRESS>",

      // Postgres server port
      // @default
      "port":5432,

      // Postgres server user name
      "user":"miningcore",

      // Postgres server password
      "password":"yourpassword",

      // Postgres server database name
      "database":"miningcore"
    }
  },

  // Donate a tiny percentage of the rewards to the ongoing development of Miningcore
  // @options 0-100
  // @default
  "devDonation":0.1,

  // Generate payouts for recorded shares and blocks
  "paymentProcessing":{

    // Enable payment processing
    // @default
    "enabled":true,

    // How often to process payouts, in milliseconds
    // @default
    "interval":600,

    // Path to a file used to backup shares under emergency conditions, such as
    // database outage
    // @default
    "shareRecoveryFile":"recovered-shares.txt"
  },

  // API Settings
  "api":{

    // Enable API
    // @default
    "enabled":true,

    // API binding address
    // @default "<IP_ADDRESS>"
    "listenAddress":"<IP_ADDRESS>",

    // API binding port
    // @default 4000
    "port":4000
  },

  "pools":[
    {

      // Pool ID
      // @note DON'T change the id after a production pool has begun collecting shares!
      "id":"dash1",

      // Enable this pool
      "enabled":true,

      "coin":{

        // Pool coin type
        "type":"DASH"
      },

      // Address to where block rewards are given (pool wallet)
      "address":"yiZodEgQLbYDrWzgBXmfUUHeBVXBNr8rwR",

      "z-address":"",

      // Block rewards go to the configured pool wallet address to later be paid out
      // to miners, except for a percentage that can go to, for examples,
      // pool operator(s) as pool fees or or to donations address. Addresses or hashed
      // public keys can be used. Here is an example of rewards going to the main pool
      // "op"
      "rewardRecipients":[
        {

          // Reward receipient type
          // @options "op", ""
          "type":"op",

          // Reward receipient wallet address
          "address":"yiZodEgQLbYDrWzgBXmfUUHeBVXBNr8rwR",

          // What percent of the reward will go to this reward receipient
          // @options 0-100
          "percentage":1.5
        }
      ],

      // How often to poll RPC daemons for new blocks, in milliseconds
      // @default
      "blockRefreshInterval":400,

      // Some miner apps will consider the pool dead/offline if it doesn't receive
      // anything new jobs for around a minute, so every time we broadcast jobs,
      // set a timeout to rebroadcast in this many seconds unless we find a new job.
      // Set to zero to disable.
      // @default 0
      "jobRebroadcastTimeout":10,

      // Remove workers that haven't been in contact for this many seconds.
      // Some attackers will create thousands of workers that use up all available
      // socket connections, usually the workers are zombies and don't submit shares
      // after connecting. This features detects those and disconnects them.
      // @default
      "clientConnectionTimeout":600,

      // If a worker is submitting a high threshold of invalid shares, we can
      // temporarily ban their IP to reduce system/network load. Also useful to fight
      // against flooding attacks. If running behind something like HAProxy be sure to
      // enable 'tcpProxyProtocol', otherwise you'll end up banning your own IP address
      // (and therefore all workers).
      "shareBasedBanning":{

        // Enable share based banning
        // @default
        "enabled":true,

        // How many seconds to ban worker for
        // @default
        "time":600,

        // What percent of invalid shares triggers ban
        // @default
        "invalidPercent":50,

        // Check invalid percent when this many shares have been submitted
        // @default
        "checkThreshold":50
      },

      // Each pool can have as many ports for your miners to connect to as you wish.
      // Each port can be configured to use its own pool difficulty and variable
      // difficulty settings. 'varDiff' is optional and will only be used for the ports
      // you configure it for.
      "ports":{

        // Binding port for your miners to connect to
        "3052":{

          // Binding address
          // @default <IP_ADDRESS>
          "listenAddress":"<IP_ADDRESS>",

          // Pool difficulty
          "difficulty":0.02,

          // Variable difficulty is a feature that will automatically adjust difficulty
          // for individual miners based on their hash rate in order to lower
          // networking overhead
          "varDiff":{

            // Minimum difficulty
            "minDiff":0.01,

            // Maximum difficulty. Network difficulty will be used if it is lower than
            // this. Set to null to disable.
            "maxDiff":null,

            // Target time that try to get 1 share every this many seconds
            // @default
            "targetTime":15,

            // Retarget time that check to see if we should retarget every this many seconds
            // @default
            "retargetTime":90,

            // Variance precentAllow time to very this % from target without retargeting
            // @default
            "variancePercent":30,

            // Do not alter difficulty by more than this during a single retarget in
            // either direction
            // @default
            "maxDelta":500
          }
        }
      },

      // Recommended to have at least two daemon instances running in case one drops
      // out-of-sync or offline. For redundancy, all instances will be polled for
      // block/transaction updates and be used for submitting blocks. Creating a backup
      // daemon involves spawning a daemon using the "-datadir=/backup" argument which
      // creates a new daemon instance with it's own RPC config. For more info on this,
      // visit:https:// en.bitcoin.it/wiki/Data_directory and
      // https:// en.bitcoin.it/wiki/Running_bitcoind
      "daemons":[
        {

          "host":"<IP_ADDRESS>",

          "port":15001,

          "user":"user",

          "password":"pass",

          // Enable streaming Block Notifications via ZeroMQ messaging from Bitcoin
          // Family daemons. Using this is highly recommended. The value of this option
          // is a string that should match the value of the -zmqpubhashblock parameter
          // passed to the coin daemon. If you enable this, you should lower
          // 'blockRefreshInterval' to 1000 or 0 to disable polling entirely.
          "zmqBlockNotifySocket":"tcp://<IP_ADDRESS>:15101",

          // Enable streaming Block Notifications via WebSocket messaging from Ethereum
          // family Parity daemons. Using this is highly recommended. The value of this
          // option is a string that should  match the value of the --ws-port parameter
          // passed to the parity coin daemon. When using --ws-port, you should also
          // specify --ws-interface all and
          // --jsonrpc-apis "eth,net,web3,personal,parity,parity_pubsub,rpc"
          // If you enable this, you should lower 'blockRefreshInterval' to 1000 or 0
          // to disable polling entirely.
          "portWs":18545,
        }
      ],

      "equihashMaxThreads":"",

      // Generate payouts for recorded shares
      "paymentProcessing":{

        "enabled":true,

        // Minimum payment in pool-base-currency (ie. Bitcoin, NOT Satoshis)
        "minimumPayment":0.01,

        // Payment scheme
        // @options "PPLNS"
        "payoutScheme":"PPLNS",

        "payoutSchemeConfig":{

          // PPLNS payment factor that used to calculate share window
          // @default
          // @note This option only valid when payoutScheme is set to "PPLNS"
          "factor":2.0
        },

        // @note This option only valid with Parity daemons
        "coinbasePassword":""
      }
    }
  ]
}

Missing "minersPayTxFees": true.


[vtk] Build error

Host Environment

OS: Windows10
Compiler: VS2019

To Reproduce
Steps to reproduce the behavior:
./vcpkg install  vtk[opengl]:x64-windows
Failure logs
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:134 (message):
    Command failed: C:/src/vcpkg/downloads/tools/cmake-3.25.1-windows/cmake-3.25.1-windows-i386/bin/cmake.exe --build . --config Debug --target install -- -v -j9
    Working Directory: C:/src/vcpkg/buildtrees/vtk/x64-windows-dbg
    See logs for more information:
      C:\src\vcpkg\buildtrees\vtk\install-x64-windows-dbg-out.log

Call Stack (most recent call first):
  installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_build.cmake:74 (vcpkg_execute_build_process)
  installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_install.cmake:16 (vcpkg_cmake_build)
  ports/vtk/portfile.cmake:235 (vcpkg_cmake_install)
  scripts/ports.cmake:147 (include)

error: building vtk:x64-windows failed with: BUILD_FAILED
error: Please ensure you're using the latest port files with `git pull` and `vcpkg update`.
Then check for known issues at:
    https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+vtk
You can submit a new issue at:
    https://github.com/microsoft/vcpkg/issues/new?template=report-package-build-failure.md&title=[vtk]+Build+error
Include '[vtk] Build error' in your bug report title, the following version information in your bug description, and attach any relevant failure logs from above.
    vcpkg-tool version: 2023-01-24-8a88d63f241d391772fbde69af9cab96c3c64c75
    vcpkg-scripts version: 1c48ec7f4 2023-02-07 (25 hours ago)

In  C:\src\vcpkg\buildtrees\vtk\install-x64-windows-dbg-out.log
FAILED: bin/vtkCommonMisc-9.2d.dll lib/vtkCommonMisc-9.2d.lib
cmd.exe /C "cd . && C:\src\vcpkg\downloads\tools\cmake-3.25.1-windows\cmake-3.25.1-windows-i386\bin\cmake.exe -E vs_link_dll --intdir=Common\Misc\CMakeFiles\CommonMisc.dir --rc=C:\PROGRA~2\MICROS~2\2019\COMMUN~1\VC\Tools\MSVC\1429~1.301\bin\Hostx64\x64\rc.exe --mt=C:\PROGRA~2\WI3CF2~1\10\bin\100220~1.0\x64\mt.exe --manifests  -- C:\PROGRA~2\MICROS~2\2019\COMMUN~1\VC\Tools\MSVC\1429~1.301\bin\Hostx64\x64\link.exe  Common\Misc\CMakeFiles\CommonMisc.dir\vtkContourValues.cxx.obj Common\Misc\CMakeFiles\CommonMisc.dir\vtkErrorCode.cxx.obj Common\Misc\CMakeFiles\CommonMisc.dir\vtkExprTkFunctionParser.cxx.obj Common\Misc\CMakeFiles\CommonMisc.dir\vtkFunctionParser.cxx.obj Common\Misc\CMakeFiles\CommonMisc.dir\vtkHeap.cxx.obj Common\Misc\CMakeFiles\CommonMisc.dir\vtkPolygonBuilder.cxx.obj Common\Misc\CMakeFiles\CommonMisc.dir\vtkResourceFileLocator.cxx.obj  /out:bin\vtkCommonMisc-9.2d.dll /implib:lib\vtkCommonMisc-9.2d.lib /pdb:bin\vtkCommonMisc-9.2d.pdb /dll /version:9.2 /machine:x64  /nologo    /debug /INCREMENTAL  lib\vtkCommonMath-9.2d.lib  lib\vtkCommonCore-9.2d.lib  lib\vtksys-9.2d.lib  ws2_32.lib  dbghelp.lib  psapi.lib  lib\vtkkissfft-9.2d.lib  kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib  && cd ."
FINAL LINK: command "C:\PROGRA~2\MICROS~2\2019\COMMUN~1\VC\Tools\MSVC\1429~1.301\bin\Hostx64\x64\link.exe Common\Misc\CMakeFiles\CommonMisc.dir\vtkContourValues.cxx.obj Common\Misc\CMakeFiles\CommonMisc.dir\vtkErrorCode.cxx.obj Common\Misc\CMakeFiles\CommonMisc.dir\vtkExprTkFunctionParser.cxx.obj Common\Misc\CMakeFiles\CommonMisc.dir\vtkFunctionParser.cxx.obj Common\Misc\CMakeFiles\CommonMisc.dir\vtkHeap.cxx.obj Common\Misc\CMakeFiles\CommonMisc.dir\vtkPolygonBuilder.cxx.obj Common\Misc\CMakeFiles\CommonMisc.dir\vtkResourceFileLocator.cxx.obj /out:bin\vtkCommonMisc-9.2d.dll /implib:lib\vtkCommonMisc-9.2d.lib /pdb:bin\vtkCommonMisc-9.2d.pdb /dll /version:9.2 /machine:x64 /nologo /debug /INCREMENTAL lib\vtkCommonMath-9.2d.lib lib\vtkCommonCore-9.2d.lib lib\vtksys-9.2d.lib ws2_32.lib dbghelp.lib psapi.lib lib\vtkkissfft-9.2d.lib kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib /MANIFEST /MANIFESTFILE:Common\Misc\CMakeFiles\CommonMisc.dir/intermediate.manifest Common\Misc\CMakeFiles\CommonMisc.dir/manifest.res" failed (exit code 1168) with the following output:
LINK : fatal error LNK1168: cannot open bin\vtkCommonMisc-9.2d for writing

LINK : fatal error LNK1168: cannot open bin\vtkCommonMisc-9.2d for writing

Could you please try clone vcpkg to other disks and rebuild vtk? I guess maybe a permission problem that caused the failure to write the file.

LINK : fatal error LNK1168: cannot open bin\vtkCommonMisc-9.2d for writing

Could you please try clone vcpkg to other disks and rebuild vtk? I guess maybe a permission problem that caused the failure to write the file.

I have tried to give powershell manager permission. And just now I did as you advise,it still didn't work.
the terminal shows
CMake Warning at scripts/cmake/vcpkg_execute_build_process.cmake:65 (message):
  Please ensure your system has sufficient memory.
Call Stack (most recent call first):
  installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_build.cmake:74 (vcpkg_execute_build_process)
  installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_install.cmake:16 (vcpkg_cmake_build)
  ports/vtk/portfile.cmake:235 (vcpkg_cmake_install)
  scripts/ports.cmake:147 (include)

-- Restarting build without parallelism
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:134 (message):
    Command failed: D:/src/vcpkg/downloads/tools/cmake-3.25.1-windows/cmake-3.25.1-windows-i386/bin/cmake.exe --build . --config Debug --target install -- -v -j9
    Working Directory: D:/src/vcpkg/buildtrees/vtk/x64-windows-dbg
    See logs for more information:
      D:\src\vcpkg\buildtrees\vtk\install-x64-windows-dbg-out.log
      D:\src\vcpkg\buildtrees\vtk\install-x64-windows-dbg-out-1.log

Call Stack (most recent call first):
  installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_build.cmake:74 (vcpkg_execute_build_process)
  installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_install.cmake:16 (vcpkg_cmake_build)
  ports/vtk/portfile.cmake:235 (vcpkg_cmake_install)
  scripts/ports.cmake:147 (include)

And the log file:
install-x64-windows-dbg-out.log

It still can't find bin\vtkCommonSystem-9.2d.dll, could you please try the following steps?

Open a x64 cmd as below:

Run command pushd D:\src\vcpkg\buildtrees\vtk\x64-windows-dbg

Run command C:\PROGRA~2\MICROS~2\2019\COMMUN~1\VC\Tools\MSVC\1429~1.301\bin\Hostx64\x64\link.exe Common\System\CMakeFiles\CommonSystem.dir\vtkClientSocket.cxx.obj Common\System\CMakeFiles\CommonSystem.dir\vtkDirectory.cxx.obj Common\System\CMakeFiles\CommonSystem.dir\vtkExecutableRunner.cxx.obj Common\System\CMakeFiles\CommonSystem.dir\vtkServerSocket.cxx.obj Common\System\CMakeFiles\CommonSystem.dir\vtkSocket.cxx.obj Common\System\CMakeFiles\CommonSystem.dir\vtkSocketCollection.cxx.obj Common\System\CMakeFiles\CommonSystem.dir\vtkTimerLog.cxx.obj /out:bin\vtkCommonSystem-9.2d.dll /implib:lib\vtkCommonSystem-9.2d.lib /pdb:bin\vtkCommonSystem-9.2d.pdb /dll /version:9.2 /machine:x64 /nologo /debug /INCREMENTAL lib\vtkCommonCore-9.2d.lib lib\vtksys-9.2d.lib ws2_32.lib dbghelp.lib psapi.lib kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib /MANIFEST /MANIFESTFILE:Common\System\CMakeFiles\CommonSystem.dir/intermediate.manifest Common\System\CMakeFiles\CommonSystem.dir/manifest.res

Please provide the output content, thanks.

It still can't find bin\vtkCommonSystem-9.2d.dll, could you please try the following steps?

Open a x64 cmd as below:

Run command pushd D:\src\vcpkg\buildtrees\vtk\x64-windows-dbg
Run command C:\PROGRA~2\MICROS~2\2019\COMMUN~1\VC\Tools\MSVC\1429~1.301\bin\Hostx64\x64\link.exe Common\System\CMakeFiles\CommonSystem.dir\vtkClientSocket.cxx.obj Common\System\CMakeFiles\CommonSystem.dir\vtkDirectory.cxx.obj Common\System\CMakeFiles\CommonSystem.dir\vtkExecutableRunner.cxx.obj Common\System\CMakeFiles\CommonSystem.dir\vtkServerSocket.cxx.obj Common\System\CMakeFiles\CommonSystem.dir\vtkSocket.cxx.obj Common\System\CMakeFiles\CommonSystem.dir\vtkSocketCollection.cxx.obj Common\System\CMakeFiles\CommonSystem.dir\vtkTimerLog.cxx.obj /out:bin\vtkCommonSystem-9.2d.dll /implib:lib\vtkCommonSystem-9.2d.lib /pdb:bin\vtkCommonSystem-9.2d.pdb /dll /version:9.2 /machine:x64 /nologo /debug /INCREMENTAL lib\vtkCommonCore-9.2d.lib lib\vtksys-9.2d.lib ws2_32.lib dbghelp.lib psapi.lib kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib /MANIFEST /MANIFESTFILE:Common\System\CMakeFiles\CommonSystem.dir/intermediate.manifest Common\System\CMakeFiles\CommonSystem.dir/manifest.res

Please provide the output content, thanks.

It seems there is no output.

If there is no error after running command line, please try install vtk on x64 cmd as below:

Open a x64 cmd as previous comment.
Run command pushd D:\src\vcpkg.
Run command vcpkg.exe install vtk[opengl]:x64-windows.

Ping @QiuYilin for response, does this issue resolved?

Thanks for posting this issue. Please reopen this issue if this is still a problem for you.

I met this problem again. But this time I found "Run Build Command(s): "C:/Program Files/Microsoft Visual Studio/2022/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" -v -v -j9 install" in log. My computer use i7 7700HQ which only has 8 threads. Sometimes the build process will fail directly and sometimes it will suceess by restarting build without parallelism.


perf: minify css only when needed

Description
Avoid minifying CSS if it isn't going to be used.

What is the purpose of this pull request?

[ ] Bug fix
[ ] New Feature
[ ] Documentation update
[x] Other

Good catch @Shinigami92, corrected the code to avoid minification when not inlined


Option for setting ELB arn is no longer available?

Hi! I'm trying to upgrade to the newest version due to the improvements but I can't find how to set the ELB arn like in the previous versions using the --elb flag
This option is no longer available?
I would like to use it because I have several services that uses the same ALB and I can't find a workaround because ECS won't allow to change load balancing settings after creation of the service

Handled by #166. Please community forums for questions. Thanks.


Evaluate loading mask implementation, as compared to desired implementation in sl-panel

should be resolved by #1217

i think this has been resolved

Resolution will need to be confirmed before this issue can be closed.


n+1 / batching

Hello!
I'm considering using this gem for a graphql-ruby / packwerk project. The idea of having in-process graphql stitching is compelling. I'm curious if you have thoughts about how I could avoid n+1 problems. I don't have a great understanding about how gateways / schema stitching tools handle this in general.

Hi @zekenie – sorry for the delay in reply, I missed your issue coming in. You can find the primary batching code here: https://github.com/gmac/graphql-stitching-ruby/blob/main/lib/graphql/stitching/executor.rb#L87-L130. It uses a query batching strategy to combine all requests bound for the same location into a single request.
TL;DR – what this means is that stitching will make one request per location per generation of data... "per generation" is key note, because there's no real optimization for getting data from A, joining that to B, then joining B's data back to A... it's a hard constraint that you're going to have to visit A twice.
Have a look at this chapter in my stitching book for best practices and to understand merging better: https://github.com/gmac/schema-stitching-handbook/tree/main/type-merging-arrays. Distilled action item would be: stitching using list queries whenever possible, and stitching will surprise you about how efficient it can be.

Oh, one other tip I forgot to mention that's general GraphQL but highly relevant to stitching: make sure that your root fields are batched. This anticipates multiple calls to the same root fields in a request will resolve without N+1.


Consider using a more full-featured web framework

Currently Smeagol uses hyper for HTTP and askama for templates. I assume more full featured web frameworks exist for Rust.
A non-exhaustive listen of reasons why a web framework might be useful:

Built in form persistence.
Perhaps the ability to have static type checking when constructing links to different controllers or pages

Another approach would be to only write an API in Rust and make a fancy JavaScript frontend.

Fixed in 7e1b90b392cb7dcffe8fa49cfb035a06202eae8f


fix index

What problem are we solving?
fix https://github.com/seaweedfs/seaweedfs/issues/4144
How are we solving the problem?
How is the PR tested?
Checks

[ ] I have added unit tests if possible.
[ ] I will add related wiki document changes and link to this PR after merging.

Add unit tests for these operations?

Add unit tests for these operations?

Sure.
I'll add tests case these days.

yes, refactoring is necessary.


Connection failure affects all follow-on operations in REPL session

If Redshift closes the connection, execution state is not cleaned up well because every other attempt to use spark-redshift in the same REPL session results in a connection timeout error. Meanwhile, other REPL sessions have no problem connecting to Redshift.
Here is an example error that leads to this behavior:
java.sql.SQLException: [Amazon][JDBC](10060) Connection has been closed.
	at com.amazon.jdbc.communications.InboundMessagesThread.close(Unknown Source)
	at com.amazon.jdbc.communications.InboundMessagesThread.run(Unknown Source)
Caused by: com.amazon.jdbc.communications.exceptions.InboundErrorMessage: [Amazon][JDBC](10060) Connection has been closed.
	at com.amazon.jdbc.communications.InboundMessagesThread.close(Unknown Source)
	at com.amazon.jdbc.communications.InboundMessagesThread.run(Unknown Source)

I have observed this problem consistently in the Databricks environment but I cannot reproduce it locally doing simple things like breaking the network connection to Redshift.
I am using the Redshift JDBC driver.

Do you still observe this issue? I'm going to close this issue as unreproducible for now, but please comment if you see this again.


Linux build fails with clang on ARM

When building with clang on an armhf system, I get:
[ 61%] Building CXX object src/CMakeFiles/sfizz_internal.dir/sfizz/Synth.cpp.o
In file included from /home/redacted/sfizz/src/sfizz/Synth.cpp:30:
In file included from /home/redacted/sfizz/src/sfizz/Interpolators.h:68:
In file included from /home/redacted/sfizz/src/sfizz/Interpolators.hpp:8:
In file included from /home/redacted/sfizz/src/sfizz/WindowedSinc.h:121:
In file included from /home/redacted/sfizz/src/sfizz/WindowedSinc.hpp:11:
/home/redacted/sfizz/external/simde/simde/x86/sse2.h:2633:21: error: use of undeclared identifier 'vcvtnq_s32_f32'; did you mean
      'vcvtq_s32_f32'?
      r_.neon_i32 = vcvtnq_s32_f32(a_.neon_f32);
                    ^~~~~~~~~~~~~~
                    vcvtq_s32_f32
/usr/include/clang/7.0.1/include/arm_neon.h:4571:16: note: 'vcvtq_s32_f32' declared here
__ai int32x4_t vcvtq_s32_f32(float32x4_t __p0) {
               ^
1 error generated.

I'm using a Debian 10 variant called Armbian and a backported clang-11:
$ clang-11 -v
Debian clang version 11.0.1-2~bpo10+1
Target: armv7l-unknown-linux-gnueabihf
Thread model: posix
InstalledDir: /usr/bin
Found candidate GCC installation: /usr/bin/../lib/gcc/arm-linux-gnueabihf/8
Found candidate GCC installation: /usr/lib/gcc/arm-linux-gnueabihf/8
Selected GCC installation: /usr/bin/../lib/gcc/arm-linux-gnueabihf/8
Candidate multilib: .;@m32
Selected multilib: .;@m32

Interestingly it works on an arm64 system (otherwise same Linux distribution).
Could this be a simde issue? I already tried the current master, but it doesn't fix the issue. Or maybe clang is at fault?

Hi, I just notice you have indeed a clang-11 backport, but your trace refers to the header arm_neon.h from clang 7.0.1. This seems like an anomaly.
Can you recheck your installation, or that your build uses the actually proper compiler.
(This might help: cmake -DCMAKE_C_COMPILER=clang-11 -DCMAKE_CXX_COMPILER=clang++-11)
Although, if this produces errors with clang7, this likely would be a simde bug.

Sorry, I just mixed up the outputs. clang-7 and clang-11 produce the exact same result. I upgraded to clang-11 after clang-7 failed to see if this is a clang-7 issue. Here is the output of clang-11:
[ 59%] Building CXX object src/CMakeFiles/sfizz_internal.dir/sfizz/Synth.cpp.o
In file included from /home/redacted/sfizz/src/sfizz/Synth.cpp:30:
In file included from /home/redacted/sfizz/src/sfizz/Interpolators.h:68:
In file included from /home/redacted/sfizz/src/sfizz/Interpolators.hpp:8:
In file included from /home/redacted/sfizz/src/sfizz/WindowedSinc.h:121:
In file included from /home/redacted/sfizz/src/sfizz/WindowedSinc.hpp:11:
/home/redacted/sfizz/external/simde/simde/x86/sse2.h:2633:21: error: use of undeclared identifier 'vcvtnq_s32_f32'; did you mean 'vcvtq_s32_f32'?
      r_.neon_i32 = vcvtnq_s32_f32(a_.neon_f32);
                    ^~~~~~~~~~~~~~
                    vcvtq_s32_f32
/usr/lib/llvm-11/lib/clang/11.0.1/include/arm_neon.h:5698:16: note: 'vcvtq_s32_f32' declared here
__ai int32x4_t vcvtq_s32_f32(float32x4_t __p0) {
               ^
1 error generated.

Does the intrinsic vcvtnq_s32_f32 appear in your file arm_neon.h?
I've got clang 11.1.0 here, and it does.
That file which according to your log is located at: /usr/lib/llvm-11/lib/clang/11.0.1/include/arm_neon.h
If it's not, this problem has to be reported at simde.

It's expected to be fixed in the latest, following the simde update.

Cool, thanks! I was about to compile the simde test suite, but 256 MByte of RAM was just not enough...


Formatting urls properly when using websockets

The web sockets transport should format urls to establish web sockets connections properly.
Issue: https://github.com/aspnet/SignalR/issues/2570

Updated to use Junit's parametrized tests feature


Add "open in streamlink" to tab contextual menu

What should be added?
"Open in streamlink" should be added as a contextual-menu item when clicking tabs, or possibly clicking a tab with a modifier key (alt-click or something) could open the stream in streamlink.
If tab has multiple splits open, then either "open all in streamlink" or disable functionality and only let it be used on single-split tabs.
Why should it be added?
To save a click!  Clicking on the tab and then clicking on the top bar of the tab is just a little annoying.

I dislike the idea of adding a very specialized option to tabs, which is also not related to tabs (but channels or only to single channel tabs). Seems a bit over the top just to go from a 3-Click interaction to a 2-Click interaction. The current interaction works really well for me personally, especially in multi-channel tabs. You'd also need to consider, that not everyone is using streamlink.

This issue does not provide enough useful features. As such there is a likely chance of this never being implemented. I will close this so it doesn't become a stale issue that never gets closed.


Example combining wasm + simplejit

I'd like to use CraneLift as a JIT backend for a standalone WebAssembly embedding. However, from browsing the documentation I'm not sure how to do this, or even if it's fully possible yet. An example showing how to use cranelift_wasm and cranelift_simplejit together would be really helpful.

I think Wasmtime has subsumed this issue. Especially now that it supports no_std.


Rescan Account: Icon and Navigation

We need to have appropriate assets for the hard refresh functionality(icon and text). Also, the navigation needs to be sorted, right now clicking on hard refresh does dispatch the corresponding action, however, it doesn't navigate back to the account details screen.

Related to #2333
Refer to https://github.com/bithyve/hexa/issues/2547 for UX

@Arpanjainson We need the UX for hard refresh

@Arpanjainson We need the UX for hard refresh

@Arpanjainson @antuz123 Can we have the link to the xd file please so that we can make the UI screen.

This is the screen I found in the Hexa Wallet UI document. Is that the correct design @Arpanjainson @antuz123?

@CypherPoet
Yes thats the one

Nice. In the screenshot above, though, the title says "Hard Refresh". In the design, it's Full Rescan. The design is also using Lorem ipsum for the subtitle. Is there any additional clarity on how we want to present this?

ok, refer to this https://bithyve-workspace.slack.com/archives/CN7K6RY9Z/p1612184750109100

for the account sync and full resync/scan please change the call to action icon - for sync can be the same as the one we have for the sync on the home screen cards, as these are  all sync actions

Refer to https://github.com/bithyve/hexa/issues/2547 for UX info.


Error with Jewel DataGrid after upgrade to last nightly build

After I upgrade to the last nightly build, I started to have the following error with a simple Jewel DataGrid use case.
Isolated simple use case with a Jewel DataGrid:
<j:DataGrid>
    <j:columns>
        <j:DataGridColumn label="Test"/>
    </j:columns>
</j:DataGrid>

Error in console:
null: Uncaught TypeError: Cannot read property 'rowHeight' of null
: org.apache.royale.jewel.beads.views.DataGridView.createLists @ /Users/hugo/Desktop/GC/bin/js-debug/org/apache/royale/jewel/beads/views/DataGridView.js:176:93
org.apache.royale.jewel.beads.views.DataGridView.createChildren @ /Users/hugo/Desktop/GC/bin/js-debug/org/apache/royale/jewel/beads/views/DataGridView.js:103:10
org.apache.royale.jewel.beads.views.DataGridView.set__strand @ /Users/hugo/Desktop/GC/bin/js-debug/org/apache/royale/jewel/beads/views/DataGridView.js:402:8
org.apache.royale.core.ElementWrapper.addBead @ /Users/hugo/Desktop/GC/bin/js-debug/org/apache/royale/core/ElementWrapper.js:115:15
org.apache.royale.core.HTMLElementWrapper.addBead @ /Users/hugo/Desktop/GC/bin/js-debug/org/apache/royale/core/HTMLElementWrapper.js:43:65
org.apache.royale.core.UIBase.addBead @ /Users/hugo/Desktop/GC/bin/js-debug/org/apache/royale/core/UIBase.js:372:53
org.apache.royale.utils.loadBeadFromValuesManager @ /Users/hugo/Desktop/GC/bin/js-debug/org/apache/royale/utils/loadBeadFromValuesManager.js:41:16
org.apache.royale.core.UIBase.addedToParent @ /Users/hugo/Desktop/GC/bin/js-debug/org/apache/royale/core/UIBase.js:554:27
org.apache.royale.jewel.supportClasses.group.GroupBase.addedToParent @ /Users/hugo/Desktop/GC/bin/js-debug/org/apache/royale/jewel/supportClasses/group/GroupBase.js:58:84
org.apache.royale.jewel.Group.addedToParent @ /Users/hugo/Desktop/GC/bin/js-debug/org/apache/royale/jewel/Group.js:67:59
org.apache.royale.core.UIBase.addElement @ /Users/hugo/Desktop/GC/bin/js-debug/org/apache/royale/core/UIBase.js:398:5
org.apache.royale.jewel.supportClasses.group.GroupBase.addElement @ /Users/hugo/Desktop/GC/bin/js-debug/org/apache/royale/jewel/supportClasses/group/GroupBase.js:154:81
org.apache.royale.utils.MXMLDataInterpreter.initializeStrandBasedObject @ /Users/hugo/Desktop/GC/bin/js-debug/org/apache/royale/utils/MXMLDataInterpreter.js:235:12
org.apache.royale.utils.MXMLDataInterpreter.generateMXMLArray @ /Users/hugo/Desktop/GC/bin/js-debug/org/apache/royale/utils/MXMLDataInterpreter.js:121:53
org.apache.royale.utils.MXMLDataInterpreter.generateMXMLInstances @ /Users/hugo/Desktop/GC/bin/js-debug/org/apache/royale/utils/MXMLDataInterpreter.js:265:49
org.apache.royale.jewel.View.addedToParent @ /Users/hugo/Desktop/GC/bin/js-debug/org/apache/royale/jewel/View.js:63:49
org.apache.royale.jewel.Application.addElement @ /Users/hugo/Desktop/GC/bin/js-debug/org/apache/royale/jewel/Application.js:136:5
org.apache.royale.jewel.Application.initialize @ /Users/hugo/Desktop/GC/bin/js-debug/org/apache/royale/jewel/Application.js:282:10
org.apache.royale.jewel.Application.start @ /Users/hugo/Desktop/GC/bin/js-debug/org/apache/royale/jewel/Application.js:251:10
 @ /Users/hugo/Desktop/GC/bin/js-debug/index.html:903:13

I looked into this quickly today, but I could not repro the issue yet.
My test was simply to paste your code into a new GridCell in Tour De Jewel DataGridPlayGround.mxml, like so:
<j:GridCell desktopNumerator="1" desktopDenominator="2" tabletNumerator="1" tabletDenominator="2" phoneNumerator="1" phoneDenominator="1">
	<j:Card>
		<j:CardPrimaryContent>
			<j:DataGrid>
				<j:columns>
					<j:DataGridColumn label="Test"/>
				</j:columns>
			</j:DataGrid>
		</j:CardPrimaryContent>
	</j:Card>
</j:GridCell>

I tested the above in debug build of Tour de Jewel, and did not see the problem yet. I will come back to it tomorrow or the following day and investigate more. I am not using nightly build, I am using my local Royale build, so I will try to see if there is any difference there too.

Hi, I tried the same and worked right in my local.
Maybe could be a problem in the nightly build? please download the new one from this night and let us know if it continue failing. If that's the case we'll take a look. In the meantime you'll need to build from sources (if that's the case)
Thanks for reporting

Hi Hugo,
I can almost ensure you're not running latest code since DataGridView line reported is empty in the actual version, so I think something is wrong with your development Royale SDK.

I was my fault.
Very sorry for that.
I saw your post today and I tried now to do a clean before build and that action put everything to working again and also the original bug fixed with the nighlty build (DataGrid don't allow the propor use of TextInput) are all fixed.


How to Finetune BLIP2 Captioning Model on custom dataset?

I'm looking for any resource that will get me the closest to try this. I've had poor luck finding a notebook and/or tutorial on how to finetune the BLIP2 captioning model, so I thought this was the place to ask.

me too

Hello,
I am currently working on a project that requires fine-tuning BLIP2 image caption with a custom dataset. Based on my interpretation of the documentation, the process involves modifying the captation_builder.py and coco_captation_dataset.py files to include any special conditions for the new dataset. Following this, we can add different transformations to the vis_processor, especially the blip_processor. Finally, we need to adapt our dataset to conform to the standard Coco caption format, or at least that is my current understanding.
Since I just started reading and understanding the documentation for this custom training project, I would appreciate it if a LAVIS developer could confirm or correct any mistakes in my assumptions. Thank you.

@GMBarra Your understanding is correct. Either you can adapt your dataset format, or you create a new dataset builder and dataset class, do which one fits best.

Does finetuning BLIP-2 require the frozen vision model and language model to be on the same GPU has the Q-former?

你好，
我目前正在开发一个项目，需要使用自定义数据集微调 BLIP2 图像标题。根据我对文档的解释，该过程涉及修改captation_builder.py和coco_captation_dataset.py文件以包含新数据集的任何特殊条件。接下来，我们可以向 vis_processor 添加不同的转换，尤其是blip_processor。最后，我们需要调整我们的数据集以符合标准的 Coco 字幕格式，或者至少这是我目前的理解。
由于我刚刚开始阅读和理解这个自定义培训项目的文档，如果 LAVIS 开发人员能够确认或纠正我的假设中的任何错误，我将不胜感激。谢谢。

Hello!
May I ask if I also want to use BLIP2 for caption operations? How can I achieve this? In the future, Eternal Island's own dataset is also needed for fine-tuning. How can we achieve this?
I need your help, thank you!

我正在寻找任何能让我最接近尝试这个的资源。我很不幸地找到了关于如何微调 BLIP2 字幕模型的笔记本和/或教程，所以我认为这是提问的地方。

请问 BLIP2的微调您成功了吗？我希望能在您这获得一些帮助


Explore improvindg accessibility for inline completions

began with https://github.com/microsoft/vscode/pull/175823

This has happened


MAJOR CHANGE: uTimeout API.

A new common API, uTimeout, is added and all timeouts are routed through it.  This API performs time comparisons correctly with unsigned 32 bit arithmetic to ensure that timeouts are not affected if they happen to cross the 32-bit wrap point, which will occur every 50 days for a millisecond tick; otherwise there were instances where a timeout could potentially get "stuck" for 25 days (the unsigned 32-bit wrap length for a millisecond tick).
The implementation of the API includes the ability to speed up the apparent wrap-rate of the underlying tick; this is used on test instance 23 (which includes cellular, GNSS and short-range module types) to give it a good thrashing.
Our thanks to warasilapm for raising this issue and my thanks to mazgch for providing the solution.
NOTE: this PR will not be merged it is simply posted here to make it possible for warasilapm to comment on it directly and for him to be able to see any comments made by mazgch.

@RobMeades in the latest commit where you removed the durationMs in at client test aroud lines 950-970 you are once using utimeoutStop.timeoutStart and in the timeoutStart to replace the similar durationMs timeoutCheck

@mazgch: yes, well spotted, the subset of tests I ran on that branch didn't include ones that ran that particular AT test, when I ran a more complete test that one failed; fixed on my local branch, didn't bother pushing it back here.


fixup java pack

When referencing multiple files in a COPY operation, you must end the
argument with a directory name. This fixes the java pack.

@bacongobbler,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

Codecov Report

Merging #164 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #164   +/-   ##
=======================================
  Coverage   33.06%   33.06%
=======================================
  Files          18       18
  Lines        1104     1104
=======================================
  Hits          365      365
  Misses        690      690
  Partials       49       49

Continue to review full report at Codecov.

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


About the timeout problem

I think this is a great work and i want to run this model to see the performence, but i met several problem and it's all about "timeout", "failed to  establish a new connection " and so on like this:
_0it [00:00, ?it/s]Traceback (most recent call last):
File "/home/lzqing/anaconda3/envs/allennlp/lib/python3.6/site-packages/urllib3/connection.py", line 171, in _new_conn
(self.dns_host, self.port), self.timeout, **extra_kw)
File "/home/lzqing/anaconda3/envs/allennlp/lib/python3.6/site-packages/urllib3/util/connection.py", line 79, in create_connection
raise err
File "/home/lzqing/anaconda3/envs/allennlp/lib/python3.6/site-packages/urllib3/util/connection.py", line 69, in create_connection
sock.connect(sa)
TimeoutError: [Errno 110] Connection timed out
It's seem that the model can't get the squad dataset from the url.I don't know it's because of the firewall or some other reason.If you know how to solve it please tell me and i will really appreciate that!

I can open the url by the firefox, and i can choose the plan B that rewrite the path to the local file, maybe it's not a big problem.But i still wish your feedback if you know how to solve it.

I guess you have difficulty in download the dataset from aws s3?
I think it is because of the network environment of your GPU server.
Since the downloading is handled by allennlp.common.file_utils.cached_path,  I wonder if you can run the following snippet in python.
from allennlp.common.file_utils import cached_path
p =cached_path("https://s3-us-west-2.amazonaws.com/allennlp/datasets/squad/squad-train-v1.1.json")

Thank you and i will try it.(It seems that the model works great, it's really fast.I think it's time to learn to use allennlp.Nice work! XD  )

Closing due to lack of update.