Stuck deleting

I tried creating a terraform object, but it errored out and when I tried deleting it, the delete just hung for ages until my CLI timed out, and when I try to create it again it warns me that I can't as a resource with the same name is being deleted.
How do I get it out of this eternal deletion limbo and just force-delete it?
Specifically, what seems to have happened is I tried specifying a custom backend and it failed because it wasn't able to write to that backend. So there's no state file locking or anything like that at play because it wasn't able to create state files at all.
It seems whenever a TF is deleted, it tries spinning up an "init-delete" container - however that container errors out. Is this why it's stuck?

Hi @tdevopsottawa The resource that is being deleted probably has a "finalizer" in the resource. Here's what that means and how to remove it.
What is means
The finalizer is added automatically when if the user does not add ignoreDelete=true to the resource spec. This means that the user wants TFO to clean up any object created with TFO when the resource is removed.
How to fix it
Since TFO is failing to finish the "cleanup" for whatever reason, you can manually edit the TFO object by running the following command:
kubectl patch tf <tfo-resource-name> -p '{"metadata: {"finalizers": null}}'

The TFO resource should be gone after that.

Thanks @isaaguilar that worked.
It seems that this undeletable problem happens whenever the Terraform Init step fails to run for whatever reason; because the init container failedtheinit-delete` container will fail too and then the TFO resource and the failed pods are stuck on the cluster forever unless you manually delete the finalizers.
Is there a plan to fix this?

Its a known issue(?). When I run into the init failure, it's usually my config that's the problem. I have to tweak the config, or make sure I have good credentials to pull any repos or access any backends.
But to your point, initially failing init will most certainly cause init-delete failures. It's almost inevitable since TFO has to make some sort of assumption that the resource it's supposed to "manage" is supposed to be removed if the k8s resource is removed.  The easiest way to make this not happen is to use ignoreDelete.
...
kind: terraform
spec:
  ...
  ignoreDelete: true

This will not kick off the delete workflow.

I wonder if the patch command is outdated. I pulled it from https://www.howtogeek.com/devops/what-are-finalizers-in-kubernetes-how-to-handle-object-deletions/#:~:text=You can manually remove an object’s Finalizers by,lead to orphaned objects and broken dependency chains.
A way to do the same thing is to do a kubectl edit and manually remove the finalizer. I hope this helps.

A way to do the same thing is to do a kubectl edit and manually remove the finalizer. I hope this helps.

Was just about to edit and comment that I managed to do it this way


Calc needs to add "BASE" as valid ID in the grammar

Related to changes for #292

Look for "REPLACE_MODES" everywhere and add "BASE" as needed.


oc calibration app downloadlink does not work

Hello, we tried to download the oc calibration app. The download for the app is not available via the following link.
https://iorodeo-streamlit-oc-calibration-a-oc-calibration-appapp-vy7s4o.streamlit.app/?ref=blog.iorodeo.com

Yes it looks like there was an issue with the poetry.lock file.  It should be running again.


Do we have react port of ngx-admin template?

Is anybody or Akveo working on the react port of the ngx-admin template?
My project is in react and I like ngx-admin UI template, would love to use the ngx-admin theme with react.

I'd love to use this template with react.

I have a similar enhancement requirement.

would love to see it in React.

I'm also really interested in using this template with react.

me too. is there any new with this template with react js?

it would be great to have this project in react.

i think i got time for this

I'd like know if someone knows if there are some reference of NGX-ADMIN to React.

Can I use at least the Nebular Auth on my ReactJS application?

if anyone decides to start in this project I can help

I have to say I really love this project that it is the only reason for me to still stick with Angular. Really looking forward to see a react version which I believe will be more popular than the existing amazing Angular version.

I'd love to use this template and nebular library with react.

we will all love this theme in react js

I'm also really interested in using this template with react.


SASS indent syntax support

Althrough CSSPlugin test fails I think it's not because of my changes. I did nothing to CSSPlugin. This changes works fine on my PC.
Maybe it fails because project on half way trough?

This indentedSyntax: true might have messed it up. Maybe we don't hardcode it and let user decide?

@nchanged then it should be mentioned in documentation. because without it .sass files can't be parsed.
indentedSyntax: true still allows to parse .scss files.
Do I need to update docs for SASSPlugin and remove indentedSyntax: true ? You decide.

Please, remove indentedSyntax let's leave it for the end user to decide.  Documentation - if it's easy for you, please add a few lines on additional extension support ;-)
And thank you!


Choosing an approach to transfer the dataframe from python to R

The options are:

Parquet file
Feather file
Pandas exchange
Arrow exchange

After a discussion with the team and comparing the results, we decided to go for Parquet method.


Create Toast Notification app

Is your feature request related to a problem? Please describe.
Create a toast notification app using HTML, CSS and JavaScript
Describe the solution you'd like
https://www.youtube.com/watch?v=mkNITfM1gm8&list=PLjwm_8O3suyOgDS_Z8AWbbq3zpCmR-WE9&index=9&pp=iAQB

@Sbiswas001 please assign this issue to me


test: improve performance of formatted.rs

Pull Request
Related issue
Fixes one item from #4840
What does this PR do?

Applies the changes recommended on the issue for meilisearch/tests/search/formatted.rs

PR checklist
Please check if your PR fulfills the following requirements:

[x] Does this PR fix an existing issue, or have you listed the changes applied in the PR description (and why they are needed)?
[x] Have you read the contributing guidelines?
[x] Have you made sure that the title is accurate and descriptive of the changes?

bors merge

bors seems very sick today

bors merge


[AutoPR compute/resource-manager] [Compute] Fix List VM Extension API name, description updates and other fixes.

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/3152

This PR has been merged into https://github.com/Azure/azure-sdk-for-go/pull/1951


Convert tests to JUnit 5

Converts all TCK tests from TestNG to Junit 5. It also modifies the example TCK runner for JBatch to use work with the converted tests.
This PR also removes several public static void setup( methods in some tests  which seemed to be not used at all.
Here's an example how to run the converted TCK on Payara Server using an unofficial JUnit 5 Arquillian extension: https://github.com/OndroMih/Payara-Batch-TCK-Runner/tree/poc-junit5-over-arquillian

This is now obsolete after the master branch was updated. The PR is archived here to show the changes against an older commit in the master branch: #3


Anerdw: Watch livesstream.fun

Anerdw requests the watch of the watch_keyword livesstream\.fun. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

Approved by Jeff Schaller in Charcoal HQ


org.springframework.transaction.CannotCreateTransactionException: in spring boot camunda

Exception while starting ProcessInstanceByKey
org.springframework.transaction.CannotCreateTransactionException: Could not open JDBC Connection for transaction; nested exception is java.sql.SQLNonTransientConnectionException: (conn:7057) Connection is close
Please note that the above exception raised after 8 or 10 hours deploying application.

Please provide more context ... (code, pom, db setup) ... this generally works.

This looks like https://stackoverflow.com/questions/31221877/connection-lost-overnight-spring-boot-mysql where the user has to configure connection handling correctly for the datasource.

Closing, as there is not enough information.
@mbalaas , you can ask the question on forum or create the issues in JIRA where Spring Boot Starter issues are being tracked from now on.


getHtml() can't get the highlight style code.

Describe the bug
alert(this.$refs.editor.invoke('getHtml'))

As shown in the figure, I can't get the complete code highlight style through getHtml(), I think this is abnormal.
Some styles are missinghljs-meta hljs-keyword hljs-string...

Desktop (please complete the following information):

OS:linux
Browser chrome

@codingcn It's right that only the data that goes inside the code block comes out. Because the tags you're talking about are tags created through the renderer.

@seonim-ryu How can I get the complete html after rendering.

@codingcn What is the required purpose? I think there is no way other than the way you get it directly from DOM when the change event fires. 🤔
Or maybe when I look at the screenshot, you are using highlight.js and is there any way to get it through the API of the hljs instance?

I am developing an article editor and want to save the final article html (including these tags hljs-meta hljs-keyword hljs-string) directly into the database instead of markdown. I do not want to rely on highlight.js when displaying One extra rendering, I think this is unnecessary.

I finally solved the problem successfully with the following code, I think this official getHtml() should generate these tags( hljs-meta hljs-keyword hljs-string) by default
let sourceHtml = this.$refs.editor.invoke('getHtml')

let tmpDOM = new DOMParser().parseFromString(sourceHtml, 'text/html').body

tmpDOM.querySelectorAll('pre code').forEach((block) => {
     hljs.highlightBlock(block);
});

let contentHtml = tmpDOM.innerHTML
console.log(contentHtml);

I finally solved the problem successfully with the following code, I think this official getHtml() should generate these tags( hljs-meta hljs-keyword hljs-string) by default
let hljs = require('highlight.js');
let sourceHtml = this.$refs.editor.invoke('getHtml')
let tmpDOM = new DOMParser().parseFromString(sourceHtml, 'text/html').body

tmpDOM.querySelectorAll('pre code').forEach((block) => {
     hljs.highlightBlock(block);
});

let contentHtml = tmpDOM.innerHTML
console.log(contentHtml);

没在框架中使用。咋获取到带高亮标签的内容

I finally solved the problem successfully with the following code, I think this official getHtml() should generate these tags( hljs-meta hljs-keyword hljs-string) by default
let hljs = require('highlight.js');
let sourceHtml = this.$refs.editor.invoke('getHtml')
let tmpDOM = new DOMParser().parseFromString(sourceHtml, 'text/html').body

tmpDOM.querySelectorAll('pre code').forEach((block) => {
     hljs.highlightBlock(block);
});

let contentHtml = tmpDOM.innerHTML
console.log(contentHtml);

没在框架中使用。咋获取到带高亮标签的内容

let sourceHtml = this.editor.getHtml()

I finally solved the problem successfully with the following code, I think this official getHtml() should generate these tags( hljs-meta hljs-keyword hljs-string) by default
let hljs = require('highlight.js');
let sourceHtml = this.$refs.editor.invoke('getHtml')
let tmpDOM = new DOMParser().parseFromString(sourceHtml, 'text/html').body

tmpDOM.querySelectorAll('pre code').forEach((block) => {
     hljs.highlightBlock(block);
});

let contentHtml = tmpDOM.innerHTML
console.log(contentHtml);

没在框架中使用。咋获取到带高亮标签的内容

let sourceHtml = this.editor.getHtml()

直接editor.getHtml()拿到的还是不带highlight的class类

@codingcn
代码大概是这样的
import Editor from '@toast-ui/editor';
import '@toast-ui/editor/dist/i18n/zh-cn';
import 'highlight.js/styles/solarized-dark.css';
import codeSyntaxHighlightPlugin from "@toast-ui/editor-plugin-code-syntax-highlight";
import colorSyntaxPlugin from "@toast-ui/editor-plugin-color-syntax";
import hljs from 'highlightjs'
const editor = new Editor({
    el: document.getElementById('post-content'),
    height: '500px',
    initialEditType: 'markdown',
    previewStyle: 'vertical',
    initialValue:'',
    plugins:[[codeSyntaxHighlightPlugin,{hljs}],colorSyntaxPlugin],
    language:'zh_CN',
    name:'post_content',
    events:{
        change:function(){
            $(".post-content-ele").val(editor.getHtml())
            $("#post-markdown-ele").val(editor.getMarkdown())
        }
    }
});

editor.getHtml()拿到的并没有( hljs-meta hljs-keyword hljs-string)这些标签


CLI: add missing memo in describe workflow

Currently only cadence --do <domain> wf desc -w <wid> -praw will output memo, but basic wf desc doesn't print memo.
This PR print it even though we cannot decode memo.

Coverage decreased (-0.1%) to 66.167% when pulling 4422a4074543807c6bda84bf69ef9038e4746f7f on descmemo into a0058ffe3e882392f5931f2694c53b8bafbd4ef0 on master.


Add interface skeletons for UIServices

Description

Add interfaces required for UIService API into the vnext subpackage of com.adobe.mobile.marketing.services.ui. These will later be moved to the parent package.
Components added :

UIService  - Represents a component capable of creating and managing UI elements
Presentable - Represents a component that can be presented on the screen.
Presentation  - Defines the super type of the different types of presentables that can be managed by AEP SDK. Types will be added as they are implemented.
PresentationDelegate  - Delegate used to observe and control the lifecycle of presentation managed by the SDK.
PresentationUtilityProvider  - Provides the necessary utilities for the UI SDK to function
PresentationEventListener - Mechanism for the component that created the associated [Presentable] to receive events  about a presentation in response to user interaction, system events, or operations performed programmatically.

Related Issue
#525

Motivation and Context

How Has This Been Tested?
N/A

Screenshots (if appropriate):
N/A
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I have signed the Adobe Open Source CLA.
[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

looks good - are we handling access modifiers later?

I did aim to make the PR reflect access modifiers as close as possible to what we'd have when we release. Are there any api's in this PR that you feel should have different visibility/access?


[staging-next] python311Packages.levenshtein: fetch submodules

Description of changes
Fix currently broken build @vcunat @fabaff

https://github.com/NixOS/nixpkgs/pull/281828#issuecomment-1909645851
https://hydra.nixos.org/build/247364986/nixlog/2/tail

This allows access to the vendored dependency rapidfuzz-cpp, which is older (2.0.0) than the nixpkgs version (3.0.0).
The nixpkgs rapidfuzz-cpp is kept in buildInputs, which enables us to seamlessly switch back to it when levenshtein catches up in the future.

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[x] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

The nixpkgs rapidfuzz-cpp is kept in buildInputs, which enables us to seamlessly switch back to it when levenshtein catches up in the future.

I probably wouldn't do that, at least not this way.  But let's hear feedback from others.

The nixpkgs rapidfuzz-cpp is kept in buildInputs, which enables us to seamlessly switch back to it when levenshtein catches up in the future.

I probably wouldn't do that, at least not this way. But let's hear feedback from others.

Indeed, this seems a bit flaky (no pun intended), but upstream has a nice logic to detect system supplied dependencies and only uses vendored ones if they are not found:
https://github.com/rapidfuzz/Levenshtein/blob/main/CMakeLists.txt
find_package(rapidfuzz 2.0.0 QUIET)
if (rapidfuzz_FOUND)
    message(STATUS "Using system supplied version of rapidfuzz-cpp")
else()
    message(STATUS "Using packaged version of rapidfuzz-cpp")
    add_subdirectory(extern/rapidfuzz-cpp)
endif()

So I guess it would be okay, this time? I'll also wait for feedbacks and change accordingly.

Let me merge this PR as is, so that the build is fixed at least.  Further improvements can be done later.

Please add python3.pkgs.levenshtein to rapidfuzz-cpp's passthru.tests .


new Pinout diagram added.

Signed-off-by: Kali Prasad<EMAIL_ADDRESS>

I noticed similar changes has already been made. but the new picture is 4.1MB in size that may take longer on a slower network. my PR has 1.6MB picture and it still a decent resolution.


Extension doesn't work until webpage is fully loaded

There are many service scripts (ads, sync, track, stats, social networks etc.) that are loaded before this extension. So it can take a minute or more to load webpage. And if webpage isn't fully loaded (spinning circle in browser tab) this extension won't work,
Example: http://fieldbitcoins.com (window with SolveMedia captcha)

You probably want to use this: https://addons.mozilla.org/en-US/firefox/addon/ublock-origin/
Nothing much I can do, if the page hasn't loaded yet, I can't inject the autocomplete.


Fix #35 to follow up the API's response changes

Even though it is a "cat-and-mouse" game with the GitHub API but here's the quick fix of the issue #35.

@ekalinin
Should I replace io/ioutil to io ?
Even though make test passes on Go v1.17 and v1.18, on Go v1.19 I get the following error.
golangci-lint(v1.49.0) wants us to use io and os package instead of io/ioutil.
$ make test
cmd/gh-md-toc/main.go:5:2: SA1019: "io/ioutil" has been deprecated since Go 1.16: As of Go 1.16, the same functionality is now provided by package io or package os, and those implementations should be preferred in new code. See the specific function documentation for details. (staticcheck)
	"io/ioutil"
	^
ghdoc.go:6:2: SA1019: "io/ioutil" has been deprecated since Go 1.16: As of Go 1.16, the same functionality is now provided by package io or package os, and those implementations should be preferred in new code. See the specific function documentation for details. (staticcheck)
	"io/ioutil"
	^
internals.go:7:2: SA1019: "io/ioutil" has been deprecated since Go 1.16: As of Go 1.16, the same functionality is now provided by package io or package os, and those implementations should be preferred in new code. See the specific function documentation for details. (staticcheck)
	"io/ioutil"
	^
make: *** [Makefile:14: lint] Error 1

Should I replace io/ioutil to io ?

Yes, let's replace. Thanks!

@ekalinin
Done! Please run the CI when you have time. Hope it passes 🤞

@ekalinin
Additional tests have been added to cover the changes. Please re-run the CIs.
It should bring back the coverage to 88% 🤞

Codecov Report

Merging #36 (c87d1d5) into master (552ceb6) will increase coverage by 1.91%.
The diff coverage is 60.00%.

@@            Coverage Diff             @@
##           master      #36      +/-   ##
==========================================
+ Coverage   80.72%   82.63%   +1.91%
==========================================
  Files           2        2
  Lines         166      167       +1
==========================================
+ Hits          134      138       +4
+ Misses         20       17       -3
  Partials       12       12

Impacted Files
Coverage Δ

ghdoc.go
85.47% <50.00%> (+2.71%)
:arrow_up:

internals.go
76.00% <100.00%> (ø)

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

Thanks a lot!


ApiCalendar.sign is always false on first load.

When refresh while logged in, ApiCalendar.sign will return false on reload, but I am already logged in.
I have a login and logout button but on load it will show the login button:
let button;

if (ApiCalendar.sign) {
	button = <button onClick={(e) => this.handleItemClick(e, 'sign-out')}> sign-out </button>
} else {
	button = <button onClick={(e) => this.handleItemClick(e, 'sign-in')}> sign-in </button>;
}

Are you sure that the ApiCalendar module is loaded when you check ApiCalendar.sign ?
You can check with ApiCalendar.onLoad() if the package is loaded
But I recommend you to use listenSign and onLoad
Exemple:
    import React, {ReactNode} from 'react';
    import ApiCalendar from 'react-google-calendar-api';

    export default class StatusSign extends Component {
        constructor(props) {
            super(props);
            this.state = {
              sign: ApiCalendar.sign,
            };
            this.signUpdate = this.signUpdate.bind(this);
            ApiCalendar.onLoad(() => {
                ApiCalendar.listenSign(this.signUpdate);
            });
        }

        signUpdate(sign) {
            this.setState({
                sign
            })
        }

        render() {
            return (

{this.state.sign}

            );
        }
    }

I added the onLoad and signUpdate but I still have false as first return

I checked a bit your repo,
Can you put the StatusSign component in your main page and check if he is working and updating:
Like:

I moved StatusSign component to my app.js but I still get false. See repo

Ok I will try to build a mini app tonight to see if I got the same problem or not.
Or try on your project directly

You need to use the onLoad method and do nothing before it or update your component when this is loaded.
I'm making a PR on your repo to show you an example.

I didn't know how to send the data back to App.js and then to other child components and my solution was putting the check inside App.js and sending the result as props to other child components. While this does the job, I don't know if this is the 'correct' way of doing it. Still thanks for the example you gave me.
import React, { Component } from 'react';
import ApiCalendar from 'react-google-calendar-api'

import Login from './components/Login'
import Stop from './components/Stop'
import StartButton from './components/StartButton';

class App extends Component {
	constructor(props) {
		super(props)
		this.state = {
			running: false,
			startTime: new Date(),
		}
		this.trackingTime = this.trackingTime.bind(this)
		this.setType = this.setType.bind(this)

		this.signUpdate = this.signUpdate.bind(this);
		ApiCalendar.onLoad(() => {
			this.signUpdate(ApiCalendar.sign);
			ApiCalendar.listenSign(this.signUpdate);
		});
	}

	signUpdate(sign) {
		this.setState({
			sign: sign
		})
	}

	trackingTime(running) {
		this.setState({
			running: running
		})
	}

	setType(name) {
		this.setState({
			type: name,
			running: true
		});
	}

	render() {
		let stopButton;
		let start;

		if (this.state.sign) {

			if (this.state.running) {
				stopButton = <Stop startTime={this.state.startTime} type={this.state.type} click={this.trackingTime}/>
				start = '';
			} else {
				start =

					<StartButton title="Working" setType={this.setType}/>
					<StartButton title="Sleeping" setType={this.setType}/>
					<StartButton title="Gaming" setType={this.setType}/>
					<StartButton title="Eating" setType={this.setType}/>

;
				stopButton = ''
			}
		}

		return(

				<Login sign={this.state.sign}/>
				{stopButton}
				{start}

		)
	}
}

export default App;

Yes you can use the state to do it, and I'm not an expert in react,
But you can take a look at context to store things like that
Context


Shared concurrent heartbeat() promise

All concurrent heartbeat() calls will return the same promise object.  Proposed solution to https://github.com/tulios/kafkajs/issues/1025
Added a test that reproduces https://github.com/tulios/kafkajs/issues/1025 but more tests needed.

Actually this shouldn't be merged until we conclude the issue of what to do with failed heartbeats that @Nevon raises in https://github.com/tulios/kafkajs/issues/1025 .
My thinking is that there's no point in queuing up heartbeat calls that will get issued one-by-one when they fail.  I presume that in most cases, if one fails they are all going to fail.


How to add new token?

Hi,
Can we add new tokens?

Hi,
If you still need help yes you can, you have to edit:
The file token-lists.js which is located at eth-hot-wallet/app/containers/TokenChooser/ you'll find a token list for Local RPC net and Mainnet add your token information there.
Add your token icon on the app.js file at eth-hot-wallet/app/app.js token icon import starts at line 57
And finally add the token image in eth-hot-wallet/app/images/token-icons/ and paste your png file there.
Hope this helps.


watch stream is not aware of network partition

The stream created by Client::watch can not be notified if the endpoint is unavailable (in a minority partition).
Instead, etcdctl does.

fixed with #82


[Watson][4524c5d5-e360-2b86-8385-1b0f94aee5cf]STOWED_EXCEPTION_System.NullReferenceException_80004003_Microsoft.PowerToys.Settings.UI.Runner.dll!Microsoft.PowerToys.Settings.UI.Runner.MainWindow+__c._WindowsXamlHost_ChildChanged_b__2_1

Generated issue from Watson
Watson Link: https://watsonportal.microsoft.com/Failure?FailureSearchText=4524c5d5-e360-2b86-8385-1b0f94aee5cf
ADO Link: None
Process: microsoft.powertoys.settings.ui.runner.exe,
Module: microsoft.powertoys.settings.ui.runner.dll

The stack trace points to a null reference while executing WindowsXamlHost_ChildChanged after pressing the Restart as admin button.

@ryanbodrug-microsoft @crutkas my hunch is that sender might be null for some reason here, so it throws an exception at line 35, but since I don't have a repro I'm not sure if simply adding a null check would fix it.
https://github.com/microsoft/PowerToys/blob/280d1907d831ad08b18efcc72498f3144951f13d/src/core/Microsoft.PowerToys.Settings.UI.Runner/MainWindow.xaml.cs#L31-L51

Added in 0.25.  https://github.com/microsoft/PowerToys/releases/tag/v0.25.0


Add quote to minimal usage example

The minimal example doesn't work without quoting the core NS

Thank you!


Cannot show image

Hi, tedchao
I tried this project locally, but in the QT view, I can't see the image even though I have opened it. How to solved it?

Hi,
Are you importing a '.png' image?
Ted

Yes.
I attempted the '.png' and a '.jpg' formats, but neither worked.

Yes.
I attempted the '.png' and '.jpg' formats, but neither worked.
Sorry that I clicked the 'close issue', I am not very familiar with Github.


Propagate source maps through combine assets step

Allows implementors running custom configs to utilize end to end source-maps.

While not directly impacting #2285, this has some correlation there.

We use this only in production. So, we don't use source-maps here. But this is a nice way of doing it.
Let's see.

The use case driving this is generating production source maps for https://sentry.io (highly recommended, btw). There are other changes that need to happen in the config to fully support that, but wanted to do piecemeal PRs rather than big bang.

Ping.

I've started work with Source maps related changes. That's why I haven't touch this.
Anyway, we use inline source-maps. Even in that case, is there's a .map file?

This will likely generate a source map file if there are inline sources. Should be able to add the conditional for that. I can't tell from your comment if this has a chance of being merged or not. If so, then glad to check those cases.

What state is this PR?
Production sourcemaps are really necessary for popular apps based on NextJS because thousands of visitor do thousands of different workflow which can't be simulated in development mode in small development team.
Different Browser versions, OS, plugins in browsers, way of use (clicking on page). This is many many cases.

Any updates? External source-maps are critical for debugging production apps.

Rebased against latest. @arunoda what are next steps?

@kpdecker I'll try the PR out 👍

Closing as this is stalled and #2990 requires a slightly different (but better!) approach.

@kpdecker so there will be no support for external source-maps in next.js?

@ilionic It's one of the things we're going to focus on for v5.

@timneutkens thanksss, this is super important for running relatively complex next.js apps in production :)


[LAB1]312551004

Description

https://github.com/SQLab/112-spring-software-testing/pull/2

[x] A clear title (name your pr "[LAB{lab_number}] {your_student_id}")
[x] A meaningful message for PR, as well as its commits
[x] From your specific branch (not main or other's branch) merging to your branch
[x] Excluding any irrelevant files, such as binaries, text files, or dot files
[x] Passing tests/CI

Your base branch can't be main. Please remember to develop on your own branch next time.


Update WayOfTheSilhouette-en.txt

Updated text. Looking at the code CustomConditionsContext.cs  I'm not sure if moving OUT of darkness would break the invisibility, but it looks like performing any action outside the darkness would (except teleport and self-bufs).

It should behave exactly like Moonlit. Would you please test that one as well? If so we need to tweak text there

Sure, I'll do that tomorrow

@ThyWoof they both seem to work as writtern - including "stepping into the light removes the invisibility" (that one I wasn't sure about)


undefined reference | cmake | eclipse (IDFGH-3048)

Hei Guys,
I was forced to open this issue because in the forum nobody replies to my question.
I'm a beginner in cmake as I'm working with Visual Studio normally. Now working with esp-idf eclipse plugin.
I'm trying to set up a project with two components, one inherits from the other.
The Structure of the Tree is attached.
The issue is that I get an error "undefined reference" for the Component I want to inherit from.
CMakeLists.txt are:

I2CKeypad:
idf_component_register(SRCS "I2CKeypad.cpp" INCLUDE_DIRS "." "../I2CPeripheral")
I2CPeripheral:
idf_component_register(SRCS "I2CPeripheral.cpp" INCLUDE_DIRS ".")
main:
idf_component_register(SRCS "main.cpp" INCLUDE_DIRS ".")
project:
cmake_minimum_required(VERSION 3.5)
include($ENV{IDF_PATH}/tools/cmake/project.cmake)
project(i2cKeypad)
I2CPeripheral.h is includes in I2CKeypad.h
Hopefully there is a person out there that knows how to solve this.
Please let me know if you need more information.
Thanks.
Edit:
What I did now:
Changed
CMakeLists.txt of I2CKeypad:
idf_component_register(SRCS "I2CKeypad.cpp" INCLUDE_DIRS "." "../I2CPeripheral")
to
idf_component_register(SRCS "I2CKeypad.cpp" INCLUDE_DIRS "." REQUIRES I2CPeripheral)
but the error is still there.
Thanks Guys. Hope you understand why i did open this issue.
Manuel

@su-Koch Thanks for reporting, we will look into.

Hi @su-Koch, when you first asked the question, I thought you were having a linker error. However, with the correction I mentioned, have you tried building the project?

of Course i tryed Building the Project. With no Success.

Try building the project outside of Eclipse using the directions shown in "getting started" from espressif.   I set up the idf toolchain and installed the latest eclipse and eclipse could not find the include files. It was also telliing me it could not find some of the python tools. Once I just used the command line tools from espressif I could build / down load with no problems. I hate getting bogged down trying to figure out why Eclipse didn't work so maybe I will try something else or try an earlier version of eclipse or VSC or Arduino. What ever works.

Try building the project outside of Eclipse using the directions shown in "getting started" from espressif. I set up the idf toolchain and installed the latest eclipse and eclipse could not find the include files. It was also telliing me it could not find some of the python tools. Once I just used the command line tools from espressif I could build / down load with no problems. I hate getting bogged down trying to figure out why Eclipse didn't work so maybe I will try something else or try an earlier version of eclipse or VSC or Arduino. What ever works.

As mentioned here https://github.com/espressif/idf-eclipse-plugin/issues/72, your problem could be with a launch target. As suggested, please create an ESP launch target to fix the unresolved issues.

@renzbagaporo Could you help me to get a sample project similar to this. I would like to import into eclipse and see

@su-Koch Does the same project working from the command-line? Could you please run from the terminal first and see what happens - if it's working fine, can you share the sample project with us.

ok, tell me what i've to run exactly on command line please.

Go to https://docs.espressif.com/projects/esp-idf/en/latest/esp32/ and follow the "getting started"
which is located at the top. It walks you through installing the tools and at the end builds and flashes a project using the command line instead of using an IDE.

Also I would first try just building one of the example projects first before to confirm the tool chain is working properly this is also shown in the "getting started" documentation.

@su-Koch can you post the build logs here?

Another important thing here is - unresolved references will disappear only after the compilation. Not sure if you're able to compile a project?

Hi @su-Koch, any updates on this issue?

Hei Renz, I had no time to investigate that. But now I will get deeper into it once more. Coming back to you if I got new experiences. Thanks for your great support.
Manuel

@su-Koch Thanks for reporting, would you please help share if any updates? Thanks.


Some questions about the second stage training process

This is a very interesting work. May I ask why you need to add a mask during the second stage of training? Will not using a mask greatly reduce network performance? I don't think the paper discusses this issue.

Thank you for your interest in our work. As mentioned in our News, we incorporated MIM to further enhance the performance of the second-stage model; however, we are uncertain about the extent of its impact on the model. MIM will not be discussed in the paper.

Thank you for your interest in our work. As mentioned in our News, we incorporated MIM to further enhance the performance of the second-stage model; however, we are uncertain about the extent of its impact on the model. MIM will not be discussed in the paper.


Bug in RBAbstractClass>>instanceVariableNames:

Reported by John Brant (24 Jul 2015).
I noticed a bug in the RB code while I was
working on SmaCC. In RBAbstractClass>>instanceVariableNames: it sends
"aCollectionOfStrings asOrderedCollection" which in VW & VA copies the
collection. For Dolphin this should be changed to "OrderedCollection
withAll: aCollectionOfStrings".

Fixed in https://github.com/objectarts/Dolphin/commit/925719a08fbf0e2040db5638bead68cd2eb50ba8.


[BUG] image upload for customized-products example doesn't work

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
/store-api/customized-products/upload returns
{
    "errors": [
        {
            "code": "0",
            "status": "400",
            "title": "Bad Request",
            "detail": "The JSON payload is malformed."
        }
    ]
}

but there is no json sent, but multipart form data
Expected Behavior
I'm able to send an image
Acceptance criteria

[ ] an image can be uploaded
[ ] examples is migrated to nuxt

Steps To Reproduce
run an example and try to upload a file
No response
Environment
- OS:
- Node:
- pnpm:

Anything else?
No response

there is an internal MR in the plugin's repository customized-product/-/merge_requests/570 to make it working


Split command path separator windows bug

Describe the bug

In conversing with someone, they had an issue with the split command. They shared their output. It was clear the issue is with the path separator used to construct the refs. Notice the backslashes instead of forward slashes:
$ref: ..\components\parameters\CommunityID.yaml

The $refs do not work on a linux or mac.
To Reproduce
Steps to reproduce the behavior:

Given any OpenAPI file
Split it on the windows machine
See the incorrect path separator used in $refs

Expected behavior

Use forward slashes for the path separator in $refs.
Logs

n/a
OpenAPI definition

3.0
Redocly Version(s)

tbd

Node.js Version(s)

Additional context

For clarity, I don't mean the "separator" argument for the command:

--separator  File path separator used while splitting. [string] [default: "_"]

I mean the literal path separator used in the $refs.

Is this similar enough to #638 that we can consider it a duplicate?

Yes, it's a dup. Thanks @lornajane


Enable property bag for DPG to handle long list of parameters

Mgmt. SDK already has the design and implementation. https://github.com/Azure/autorest.csharp/issues/2951
Please investigate how we could leverage that to handle the long list of paramters for DPG.

duplicate with https://github.com/Azure/autorest.csharp/issues/2476


Add documentation page for Emby

Since we have two media servers, Plex and Emby (actually, three if you count Jellyfin, which should be trivial to add), we might want to add a line or two at some point explaining why there are in fact that many, that is, what the differences are (Plex wants you to register, Emby isn't completely open source any more, etc). For the moment, this is just a basic note on the app itself.

As always, thank you for the awesome docs! Have added few comments that I'd appreciate your thoughts on. :+1:

I'll put this on the back burner for now until I've figured out that PR for moving the configuration to all.yml. It probably also makes more sense to write some ZFS documentation first so we can reference it from here.

I'll rewrite this once #79 is included.

@davestephens Okay, now that we've moved the ZFS stuff out, let's have another go at this.

:boom:


Freeze of ZMQ Dependency to enable compatibility with older version of MM

Problem
In our lab, we settle on a version of MicroManager that suits our needs, and try not to make any updates for ~6months.  This allows us to settle on a version that is less buggy for our needs, or one where we understand small bugs, and enables development of acquisition code, calibration, etc.  Along with this settlement of MicroManager, we also settle on the version of pycromanager accompanied with that specific build.  However, there are often bug fixes and feature additions to pycromanager that we would like to use with our older build of MicroManager but it seems as though the ZMQ mismatch between latest pycromanager build and older MM build makes this difficult.  I wanted to start the conversation on the implications of a version freeze of ZMQ and how this may impact the interplay with MM (I do not know much on this front).

Proposed Solution

I am not sure if pycromanager uses a lot of the newest features of ZMQ, so I propose that the version of ZMQ accompanied with pycromanager is frozen, and only updated when absolutely needed.  This would allow us to use newer versions of pycromanager, but still have compatibility with older builds of MM.
I know there is also a java side to this (although I know much less about this side), and I was wondering if this ZMQ freeze on the python side would affect the java components, or if there is a way to replace/re-arrange .jar files such that everything works well with eachother.  @ieivanov may be able to provide insight on this part of the issue.
Additional context

As biologists start to use this platform widely for acquisition, it will be nice to have stable builds / configurations that work with other tools.  We are developing pipelines in our own repos that use pycromanager / micromanager and it would be great to be able to lay out clear instructions on what versions to use and install.  To do this it would be helpful for us to use newer features of pycromanager, but have pycromanager be compatible with an older stable build of MM that our lab eventually settles on.
Please let me know if I can clarify anything here.

I'm hoping that if we can alleviate the ZMQ version mismatch between MicroManager and pycromanager, then we can use pycromanager with an order version of MicroManager by pulling the latest version of pycromanager from pypi and placing the most recent compiled .jar files for AcqEngJ, NDViewer, and NDTiffStorage in the MicroManager plugin folder. @henrypinkard let us know if you think this will work.

I think there's a straightforward solution to this. I'll explain the architecture and I think this will make sense.
Most of the heavy lifting of Pycro-Manager is actually occurring on the Java side, in the AcqEngJ (Acqusition engine), NDViewer (Image viewer), and NDTiffStorage (Image saving) libraries. These are all independent of one another and depend only on MMCoreJ, the Java wrapper to the Micro-Manager core. There's a fourth library, PycroManagerJava, which provides a tiny bit of glue code to link all of these together (e.g. an acquisition has a viewer + a data storage instance). In addition, it also contains the Java side of the Bridge, which is that transport layer that interconverts Java and Python using ZeroMQ (More about this in the Architecture and design section of the supplement of the PM paper). This probably makes sense to have as its own library independent of Micro-Manager entirely, which may happen in the future.
The ZMQ version mismatch would be better named "transport protocol mismatch", because its not referring to ZMQ itself, but rather how Java objects/functions are serialized into JSON which is then sent over ZMQ sockets. This transport layer only uses a few very basic features of ZMQ which thousands of other projects do as well, so I don't imagine versioning even matters much.
On the Python side, the pip package contains the client side of this zmq transport layer, as well as a layer on top of that that is calling the glue code in PycroManagerJava.
These four java libraries live in the Jar files @ieivanov mentions, and they are entirely independent of the rest of Micro-Manager java layer at present. So if you update all 4 of them to their latest versions by manually replacing the jars (available here) (Note: this url will change sometime in the future as we find a new hosting platform but it will work just the same), and you upgrade to the latest pip version of pycromanager, everything should just the same as if you downloaded the latest nightly build.
If MMCoreJ changes, this would not be true, you'd have to update everything. But this has yet to happen during the existence of Pycro-Manager, and I don't know why it would any time soon.
One final caveat is that I think @nicost might be messing around with switching the Micro-Manager MDA window to rely on AcqEngJ, so in the future you might have to also replace the MMJ_.jar file too for everything to work as expected if you're also using that.

But really I think the best solution for this is to write unit tests for the stuff that ends up being buggy on your end, so that if and when you upgrade you know exactly whats going wrong without manual testing

@henrypinkard thanks for the detailed explanation of the architecture -- I am not sure if I had specifically noticed performance issues when the ZMQ server was mismatched, but it is good to know that this shouldn't matter.  It is also great to know that these pycromanager jar files are only dependent on MMCoreJ and can be replaced.
I think the solution that makes sense for us is to replace the Jar files in our earlier MM builds as well as upgrade pycromanager via pip.  Unit tests are also a good idea for the future to track these bugs.
One clarification question on that final caveat:  If @nicost changes around the MDA engine, this won't affect the older build's interaction with pycromanager correct?  Or are you saying that the pycromanager Jars may also be changed in this case, such that we will need to replace the MMJ_.jar file as well during this pseudo-upgrade procedure?
Thanks for your help on all of this!

I am not sure if I had specifically noticed performance issues when the ZMQ server was mismatched

If it does lead to a problem, it wouldn't be performance, it would be some function in the API not working at all or working in some unexpected way. But I think this code is pretty much stabilized now, so hopefully you won't run into this at all.

I think the solution that makes sense for us is to replace the Jar files in our earlier MM builds as well as upgrade pycromanager via pip. Unit tests are also a good idea for the future to track these bugs.

Yeah makes sense to me

One clarification question on that final caveat: If @nicost changes around the MDA engine, this won't affect the older build's interaction with pycromanager correct? Or are you saying that the pycromanager Jars may also be changed in this case, such that we will need to replace the MMJ_.jar file as well during this pseudo-upgrade procedure?

He would be changing the MDA engine to use AcqEngJ. So this might entail fixing stuff in AcqEngJ as well. Pycro-Manager will always be using the latest version of AcqEngJ, so you'd just want to do as you said and replace MMJ_ as well with a version that you build yourself or grab from a newer build.

Thanks for your help on all of this!

Thanks @henrypinkard!

@henrypinkard the link to the jar files did change, as you said - can you please add the new link here? Is the strategy we discussed in this issue still the best for using older MM versions with the latest pycromanager version?

Yes, the previous repo was discontinued, so they're now here: https://s01.oss.sonatype.org/#nexus-search;quick~micro-manager
This is still how it is set up, but in general, I would strongly encourage you to not use this strategy and instead, if you're going to update anything at all, just stay up to date with the latest nightly builds. I wouldn't expect that the hardware layer is changing much anyway, and this manual way of updating pycromanager is less robust and not guaranteed to be future proof

Thanks Henry!
We have previously experienced problems where sometimes a device adapter would update between different MM builds and our acquisition would not work the same way anymore. For now, our strategy is to stick to a given nightly build that we know works well, and update only if we need to, and after we have done proper testing.
It would be great to have a periodic (say monthly) MM version log summarizing what features have changed. Is there an easy way to construct that, maybe based on commit history, or files changed?

I get that. But I think the same thing could happen if you're updating PM, and you have the additionally possibility of introducing version mismatch bugs that wouldn't otherwise arise. Less work in the long run, I would think, to update everything at once periodically.

It would be great to have a periodic (say monthly) MM version log summarizing what features have changed. Is there an easy way to construct that, maybe based on commit history, or files changed?

I think its a good idea. Maybe @marktsuchida knows?

Run:
git log --since="last month" --pretty=format:'%h,%an,%ar,%s' > log.csv
on both micro-manager and mmCoreAndDevices.

We have previously experienced problems where sometimes a device adapter would update between different MM builds and our acquisition would not work the same way anymore.

Please let the device adapter (or us if unreachable) know.  Sometimes small changes can have unintended and unexpected consequences.  Without feedback, nobody has a change to make things work better.


Fix Travis CI build

It's been 3 months and dozens of builds since a build completed successfully.
https://travis-ci.org/google/primarysources/builds

In order to ease us (the Wikidata dev team) to track the issues of the primary sources tool, we have created a Phabricator ticket for this issue: https://phabricator.wikimedia.org/T148158
Moving forward, please drop your comments onto that Phabricator ticket.


fix get_scratch_devices logical anomaly

https://tracker.ceph.com/issues/59374

Can one of the admins verify this patch?


running iroh add in quick succession makes the daemon lock up

Running iroh provide and then iroh add as a separate process to add multiple individual file paths in quick succession causes the iroh provide process to lock up and refuse connections. Waiting for a bit and then adding more seems to work but locks up easier and easier after the initial halt.
Adding a 1-2 second sleep between the adds seems to avoid the problem entirely.
Debug logs from hitting the lockup:
.
.
.
2023-04-11T12:12:42.706373Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.706461Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.706547Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.706634Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.706720Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.706807Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.706894Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.706980Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.707067Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.707154Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.707242Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.707422Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.707511Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.707605Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.707693Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.707779Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.707867Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.707954Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.708042Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.708131Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.708218Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.708304Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.708391Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.708478Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.708564Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.708651Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.708738Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.708824Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.708913Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.709019Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.709206Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.709294Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.709381Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.709468Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.709557Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.709648Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.709736Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.709823Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.709910Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.709997Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.710083Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.710172Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.710259Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.710348Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.710434Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.710521Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.710608Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.710696Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.710879Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.710983Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.711074Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.711162Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.711250Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.711337Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.711424Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.711511Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.711597Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.711684Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.711770Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.711856Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.711943Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.712030Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.712118Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.712205Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.712292Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.712387Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.712572Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.712661Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.712750Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.712837Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.712925Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.713016Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.713106Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.713195Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.713282Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.713370Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.713457Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.713545Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.713638Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.713726Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.713813Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.713899Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.713988Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.714075Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.714276Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.714367Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.714455Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.714543Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.714633Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:42.719800Z DEBUG quinn_proto::endpoint: refusing connection
2023-04-11T12:12:51.482654Z DEBUG quic_rpc::transport::quinn: Error accepting stream: timed out
2023-04-11T12:12:51.486868Z DEBUG quic_rpc::transport::quinn: Error accepting stream: timed out
2023-04-11T12:12:51.490992Z DEBUG quic_rpc::transport::quinn: Error accepting stream: timed out
2023-04-11T12:12:51.508439Z DEBUG quic_rpc::transport::quinn: Error accepting stream: timed out
2023-04-11T12:12:51.519963Z DEBUG quic_rpc::transport::quinn: Error accepting stream: timed out
2023-04-11T12:12:51.525192Z DEBUG quic_rpc::transport::quinn: Error accepting stream: timed out
2023-04-11T12:12:51.535658Z DEBUG quic_rpc::transport::quinn: Error accepting stream: timed out
2023-04-11T12:12:51.544924Z DEBUG quic_rpc::transport::quinn: Error accepting stream: timed out
2023-04-11T12:12:51.551195Z DEBUG quic_rpc::transport::quinn: Error accepting stream: timed out
2023-04-11T12:12:51.597086Z DEBUG quic_rpc::transport::quinn: Error accepting stream: timed out
2023-04-11T12:12:51.607383Z DEBUG quic_rpc::transport::quinn: Error accepting stream: timed out
2023-04-11T12:12:51.635614Z DEBUG quic_rpc::transport::quinn: Error accepting stream: timed out
2023-04-11T12:12:51.649903Z DEBUG quic_rpc::transport::quinn: Error accepting stream: timed out
2023-04-11T12:12:51.668191Z DEBUG quic_rpc::transport::quinn: Error accepting stream: timed out
2023-04-11T12:12:51.693686Z DEBUG quic_rpc::transport::quinn: Error accepting stream: timed out
2023-04-11T12:12:51.711923Z DEBUG quic_rpc::transport::quinn: Error accepting stream: timed out

Do you have a counter of how many connections you're trying to open at the same time?  This could be a quinn max allowed connections setting, though the default is 100 000, so fairly high.
Is that log output from the provider/server or add commands?

The logs are from the provider. Didn't explicitly count the connections but given its a fresh provider for each sim it should be less then 20 at worst. Even the full suite is less than 100.

@Arqu can you check if this is still the case? I did the following experiment:

run a provider in relase mode: cargo run --release provide
add a file in release mode: while true; do cargo run --release add ../bao/src/lib.rs; done

No issues, I get about 2 adds per second.

OK, when I run the binaries directly and run adds in multiple shells I get this as well. Certainly not a very low limit, but it does happen.
I was able to make it go away entirely by setting MAX_RPC_CONNECTIONS in iroh/src/commands/provide.rs to 64k. I guess what happens is that there is a slight delay or something is not properly cleaned up when a quinn based quic-rpc connection is dropped.
If you want an immediate fix I can just increase the limit. How urgent is this? I will see if I can improve the shutdown code so the dead collections don't linger as long.

I would rather see a "proper" fix, than just increasing the limit.

I'm no longer hung up on this (the delay made things work) and feels like in general things are better for a while already, haven't really hit it in a month or two at least.

So, I pushed yet another small fix. But this does not seem to help. The quinn client does all the right things to make sure the server side is notified when a connection goes away. Here is the Drop for the client endpoint:
it calls close on the endpoint and then even calls wait_idle.
impl Drop for ClientConnectionInner {
    fn drop(&mut self) {
        tracing::debug!("Dropping client connection");
        if let Some(endpoint) = self.endpoint.take() {
            endpoint.close(0u32.into(), b"client connection dropped");
            // spawn a task to wait for the endpoint to notify peers that it is closing
            let span = debug_span!("closing client endpoint");
            tokio::spawn(
                async move {
                    endpoint.wait_idle().await;
                }
                .instrument(span),
            );
        }
        // this should not be necessary, since the task would terminate when the receiver is dropped.
        // but just to be on the safe side.
        if let Some(task) = self.task.take() {
            tracing::debug!("Aborting task");
            task.abort();
        }
    }
}

iroh main calls tokio shutdown_timeout to give the task above that does wait_idle some time to execute.
But still, when I log it I see wait_idle not being executed.
Here is the modified wait_idle thing:
                async move {
                    println!("waiting for idle");
                    endpoint.wait_idle().await;
                    println!("done waiting for idle");
                }
                .instrument(span),

and here is what I see in the output:
2023-07-13T09:51:30.886648Z DEBUG quic_rpc::transport::quinn: Dropping client connection
waiting for idle
2023-07-13T09:51:30.886668Z DEBUG quic_rpc::transport::quinn: Aborting task
Shutting down...
Goodbye!

"done waiting for idle" never comes. the task is not polled to completion. Adding an unconditional delay instead of using shutdown_timeout makes it work, but doing that would just be rate limiting the number of adds you can do per second.

Stale


Fix inconsistent class hash

Problem: for some Cairo0 contracts, computation from class_hash was incorrect. This was preventing from executing some new blocks that use old contracts
Solution: fix the hash computation
Issue Number: #379
Type

[ ] feature
[x] bugfix
[ ] dev (no functional changes, no API changes)
[ ] fmt (formatting, renaming)
[ ] build
[ ] docs
[ ] testing

Description
Breaking changes?

[ ] yes
[x] no

Nice, LGTM. Was there also an issue on the Pathfinder side? If so, can you leave a link to an issue/PR about it here?

I searched the Pathfinder repo but haven't found any issues or PRs related to this


Could not find "Convert to Pull Request Suggestion"

Testing #6160
Perhaps I wasn't in the "working tree diff" as I thought I was?
https://github.com/user-attachments/assets/e3b33a92-e7cf-453d-9d60-7d3003c43697

Yes, I had open https://github.com/joshspicer/almost-empty/pull/1.  I just retried it starting a new PR from scratch https://github.com/joshspicer/almost-empty/pull/6 and it worked as expected.

I suspect it was user-error as I had no problems getting it to work this time 😅


Added specular and opacity to Matte material

Matte material was missing specular and opacity.

Fixed: Removed specular and specularColor and updated color's default value.

Squashed and merged manually (it is not possible with GH web UI to get a proper linear history).


Make GitHub status API context congruous

Tiny change to make the status api message congruous with all the other CI services out there.

 You should sign our Contributor License Agreement in order to get your pull request merged.

LGTM, will merge once the CLA is signed. Thanks!

thanks, will do as soon as I hear back from our legal team :sob:

@bradrydzewski can you get in touch with me over email?

sure, you can email<EMAIL_ADDRESS>

:tada:


How to view backend on self hosted?

Hi guys, The whole point of using parse was to have a simple backend to view and add data aswell as everything else.
So it's great that i was able to easily setup a parse server to heroku. but now how do i view that data?
I setup the example, , but how can i easily use the backend to make a new class? or quickly see if a command i just used worked...
I saw in a post they said i can still use the parse backend with my self hosted db, but no one has mentioned how?

Parse Dashboard let's you have a view into your data https://github.com/ParsePlatform/parse-dashboard
And it's getting better very quickly.

you could also try the adminca.com dashboard for even easier setup, though it doesn't support push notifications yet.

Both answers are great! Closing now! :tada:


Backup / Exporting account info 1.0.5

bug 1:
For some reason I can't export an ERC-20 account info on latest test account I set up. "Account password or keystore file is wrong". Can't open it with TouchID also because of bug where TouchID bug for ERC20 accounts.
I entered the same password I used to create the account. I tried several new accounts to check if I somehow failed with password setup. I didn't.
https://youtu.be/C7s5sclPeqk
bug 2:
when it does work, the account info is not displayed fully in some cases, too much text in the field. Change the text fields to dynamic size. On ERC-20 the seed is longer and doesn't display fully.

Thanks for the detail, bug1 will be fixed in Version1.1.0
bug2 is a display issue, it should be fixed in Version1.1.x

Thanks for the detail, bug1 will be fixed in Version1.1.0
bug2 is a display issue, it should be fixed in Version1.1.x

Fixed in 1.1.0


Full stop is missing.

Full stop missing after wallet.

Verified this issue on dev app v 1.7.9(312)


CLOUD-660 public access to failed tests

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Test name
Status

demand-backup
failed

init-deploy
failed

upgrade
failed

scheduled-backup
failed

scaling
failed

smart-update
failed

recreate
failed

version-service
failed

affinity
failed

monitoring
failed

self-healing
failed

operator-self-healing
failed

clone-cluster
failed

tls-check
failed

users
failed

ns-mode
failed

commit: https://github.com/percona/percona-postgresql-operator/pull/200/commits/acb7e60e3f4529b72938ecbc747bcdbf4fbe6c00
image: perconalab/percona-postgresql-operator:PR-200-acb7e60e-pgo-apiserver
image: perconalab/percona-postgresql-operator:PR-200-acb7e60e-pgo-event
image: perconalab/percona-postgresql-operator:PR-200-acb7e60e-pgo-rmdata
image: perconalab/percona-postgresql-operator:PR-200-acb7e60e-pgo-scheduler
image: perconalab/percona-postgresql-operator:PR-200-acb7e60e-postgres-operator
image: perconalab/percona-postgresql-operator:PR-200-acb7e60e-pgo-deployer

Test name
Status

upgrade
failed

demand-backup
failed

init-deploy
failed

scheduled-backup
failed

scaling
failed

smart-update
failed

recreate
failed

version-service
failed

affinity
failed

monitoring
failed

self-healing
failed

operator-self-healing
failed

clone-cluster
failed

tls-check
failed

users
failed

ns-mode
failed

commit: https://github.com/percona/percona-postgresql-operator/pull/200/commits/acb7e60e3f4529b72938ecbc747bcdbf4fbe6c00
image: perconalab/percona-postgresql-operator:PR-200-acb7e60e-pgo-apiserver
image: perconalab/percona-postgresql-operator:PR-200-acb7e60e-pgo-event
image: perconalab/percona-postgresql-operator:PR-200-acb7e60e-pgo-rmdata
image: perconalab/percona-postgresql-operator:PR-200-acb7e60e-pgo-scheduler
image: perconalab/percona-postgresql-operator:PR-200-acb7e60e-postgres-operator
image: perconalab/percona-postgresql-operator:PR-200-acb7e60e-pgo-deployer

Test name
Status

upgrade
failed

demand-backup
failed

init-deploy
failed

scheduled-backup
failed

scaling
failed

smart-update
failed

recreate
failed

version-service
failed

affinity
failed

monitoring
failed

self-healing
failed

operator-self-healing
failed

clone-cluster
failed

tls-check
failed

users
failed

ns-mode
failed

commit: https://github.com/percona/percona-postgresql-operator/pull/200/commits/acb7e60e3f4529b72938ecbc747bcdbf4fbe6c00
image: perconalab/percona-postgresql-operator:PR-200-acb7e60e-pgo-apiserver
image: perconalab/percona-postgresql-operator:PR-200-acb7e60e-pgo-event
image: perconalab/percona-postgresql-operator:PR-200-acb7e60e-pgo-rmdata
image: perconalab/percona-postgresql-operator:PR-200-acb7e60e-pgo-scheduler
image: perconalab/percona-postgresql-operator:PR-200-acb7e60e-postgres-operator
image: perconalab/percona-postgresql-operator:PR-200-acb7e60e-pgo-deployer

Test name
Status

demand-backup
failed

upgrade
failed

init-deploy
failed

scheduled-backup
failed

scaling
failed

smart-update
failed

recreate
failed

version-service
failed

affinity
failed

monitoring
failed

self-healing
failed

operator-self-healing
failed

clone-cluster
failed

tls-check
failed

users
failed

ns-mode
failed

commit: https://github.com/percona/percona-postgresql-operator/pull/200/commits/acb7e60e3f4529b72938ecbc747bcdbf4fbe6c00
image: perconalab/percona-postgresql-operator:PR-200-acb7e60e-pgo-apiserver
image: perconalab/percona-postgresql-operator:PR-200-acb7e60e-pgo-event
image: perconalab/percona-postgresql-operator:PR-200-acb7e60e-pgo-rmdata
image: perconalab/percona-postgresql-operator:PR-200-acb7e60e-pgo-scheduler
image: perconalab/percona-postgresql-operator:PR-200-acb7e60e-postgres-operator
image: perconalab/percona-postgresql-operator:PR-200-acb7e60e-pgo-deployer

Test name
Status

demand-backup
failed

upgrade
failed

init-deploy
failed

scheduled-backup
failed

scaling
failed

smart-update
failed

recreate
failed

version-service
failed

affinity
failed

monitoring
failed

self-healing
failed

operator-self-healing
failed

clone-cluster
failed

tls-check
failed

users
failed

ns-mode
failed

commit: https://github.com/percona/percona-postgresql-operator/pull/200/commits/acb7e60e3f4529b72938ecbc747bcdbf4fbe6c00
image: perconalab/percona-postgresql-operator:PR-200-acb7e60e-pgo-apiserver
image: perconalab/percona-postgresql-operator:PR-200-acb7e60e-pgo-event
image: perconalab/percona-postgresql-operator:PR-200-acb7e60e-pgo-rmdata
image: perconalab/percona-postgresql-operator:PR-200-acb7e60e-pgo-scheduler
image: perconalab/percona-postgresql-operator:PR-200-acb7e60e-postgres-operator
image: perconalab/percona-postgresql-operator:PR-200-acb7e60e-pgo-deployer

Test name
Status

commit: https://github.com/percona/percona-postgresql-operator/pull/200/commits/17e694c4373f49259ee0d2cf3f5b3bf338175884
image: perconalab/percona-postgresql-operator:PR-200-17e694c4-pgo-apiserver
image: perconalab/percona-postgresql-operator:PR-200-17e694c4-pgo-event
image: perconalab/percona-postgresql-operator:PR-200-17e694c4-pgo-rmdata
image: perconalab/percona-postgresql-operator:PR-200-17e694c4-pgo-scheduler
image: perconalab/percona-postgresql-operator:PR-200-17e694c4-postgres-operator
image: perconalab/percona-postgresql-operator:PR-200-17e694c4-pgo-deployer

Test name
Status

upgrade
passed

demand-backup
passed

init-deploy
passed

smart-update
passed

scaling
passed

version-service
passed

recreate
passed

affinity
passed

scheduled-backup
passed

monitoring
passed

self-healing
passed

operator-self-healing
passed

clone-cluster
passed

tls-check
passed

users
passed

ns-mode
passed

commit: https://github.com/percona/percona-postgresql-operator/pull/200/commits/17e694c4373f49259ee0d2cf3f5b3bf338175884
image: perconalab/percona-postgresql-operator:PR-200-17e694c4-pgo-apiserver
image: perconalab/percona-postgresql-operator:PR-200-17e694c4-pgo-event
image: perconalab/percona-postgresql-operator:PR-200-17e694c4-pgo-rmdata
image: perconalab/percona-postgresql-operator:PR-200-17e694c4-pgo-scheduler
image: perconalab/percona-postgresql-operator:PR-200-17e694c4-postgres-operator
image: perconalab/percona-postgresql-operator:PR-200-17e694c4-pgo-deployer

Test name
Status

upgrade
failed

demand-backup
failed

init-deploy
failed

scheduled-backup
failed

scaling
failed

smart-update
failed

recreate
failed

version-service
failed

affinity
failed

monitoring
failed

self-healing
failed

operator-self-healing
failed

clone-cluster
failed

tls-check
failed

users
failed

ns-mode
failed

commit: https://github.com/percona/percona-postgresql-operator/pull/200/commits/acb7e60e3f4529b72938ecbc747bcdbf4fbe6c00
image: perconalab/percona-postgresql-operator:PR-200-acb7e60e-pgo-apiserver
image: perconalab/percona-postgresql-operator:PR-200-acb7e60e-pgo-event
image: perconalab/percona-postgresql-operator:PR-200-acb7e60e-pgo-rmdata
image: perconalab/percona-postgresql-operator:PR-200-acb7e60e-pgo-scheduler
image: perconalab/percona-postgresql-operator:PR-200-acb7e60e-postgres-operator
image: perconalab/percona-postgresql-operator:PR-200-acb7e60e-pgo-deployer

Test name
Status

commit: https://github.com/percona/percona-postgresql-operator/pull/200/commits/17e694c4373f49259ee0d2cf3f5b3bf338175884
image: perconalab/percona-postgresql-operator:PR-200-17e694c4-pgo-apiserver
image: perconalab/percona-postgresql-operator:PR-200-17e694c4-pgo-event
image: perconalab/percona-postgresql-operator:PR-200-17e694c4-pgo-rmdata
image: perconalab/percona-postgresql-operator:PR-200-17e694c4-pgo-scheduler
image: perconalab/percona-postgresql-operator:PR-200-17e694c4-postgres-operator
image: perconalab/percona-postgresql-operator:PR-200-17e694c4-pgo-deployer

Test name
Status

demand-backup
passed

upgrade
passed

scheduled-backup
passed

smart-update
passed

version-service
passed

init-deploy
passed

scaling
passed

recreate
passed

affinity
passed

monitoring
passed

self-healing
passed

operator-self-healing
passed

clone-cluster
passed

tls-check
passed

users
passed

ns-mode
passed

commit: https://github.com/percona/percona-postgresql-operator/pull/200/commits/17e694c4373f49259ee0d2cf3f5b3bf338175884
image: perconalab/percona-postgresql-operator:PR-200-17e694c4-pgo-apiserver
image: perconalab/percona-postgresql-operator:PR-200-17e694c4-pgo-event
image: perconalab/percona-postgresql-operator:PR-200-17e694c4-pgo-rmdata
image: perconalab/percona-postgresql-operator:PR-200-17e694c4-pgo-scheduler
image: perconalab/percona-postgresql-operator:PR-200-17e694c4-postgres-operator
image: perconalab/percona-postgresql-operator:PR-200-17e694c4-pgo-deployer


New account gets registered to wrong store (when using multistore)

Current behavior
The registration is not working correctly in a multistore setup. The API request made to Magento is missing the website_id property, which causes Magento to use the default store instead of the one it should be using.
See: https://devdocs.magento.com/redoc/2.3/customer-rest-api.html#tag/customers
In my case I tried to create an account to the German store, but I the account got registered into the Polish store causing the welcome email to be in the wrong language.
This was apparently still working in 1.10, but got broken in 1.11.
Expected behavior
Account should get created in Magento into the store that was being used in VSF.
Repository
https://github.com/DivanteLtd/vue-storefront/tree/v1.11.0-rc.2
Can you handle fixing this bug by yourself?

[ ] YES
[x] NO

Which Release Cycle state this refers to? Info for developer.
Pick one option.

[ ] This is a bug report for test version on https://test.storefrontcloud.io - In this case Developer should create branch from develop branch and create Pull Request 2. Feature / Improvement back to develop.
[x] This is a bug report for current Release Candidate version on https://next.storefrontcloud.io - In this case Developer should create branch from release branch and create Pull Request 3. Stabilisation fix back to release.
[ ] This is a bug report for current Stable version on https://demo.storefrontcloud.io and should be placed in next stable version hotfix - In this case Developer should create branch from hotfix or master branch and create Pull Request 4. Hotfix back to hotfix.

I'm not completely sure whether this should be fixed into VSF or VSF-API.
I suppose the missing website_id could be added in either one:

https://github.com/DivanteLtd/vue-storefront/blob/v1.11.0-rc.2/core/modules/user/store/actions.ts#L72-L74
https://github.com/DivanteLtd/vue-storefront-api/blob/v1.11.0-rc1/src/api/user.js#L35-L56

I'm not able to reproduce the problem anymore. I'll reopen if I run into the problem again.

TODO:

send website_id to vsf-api
pass website_id to platform in vsf-api for user endpoints


Release v0.3.2

Version bump for JOSS (journal of open source software) release.

[x] CHANGELOG updated
[x] Tests added to cover contribution
[x] Documentation updated

Can you push the v0.3.2 tag @fredshone ? Package builds won't run without it

Another issue: looks like your local repo isn't quite set up right. None of the notebooks can find the pam module. I would recommend deleting any empty pam directory you now have (a ghostly reminder of the pre src world) and remember to a. run pip install --no-deps -e . to install the pam jupyter kernel ipython kernel install --user --name pam (I think. It's in the docs)

Blocked by: https://github.com/arup-group/actions-city-modelling-lab/pull/18

Another issue: looks like your local repo isn't quite set up right. None of the notebooks can find the pam module.

You are right, i have the old pam directory,  but I'd like to know how you knew this???

You are right, i have the old pam directory, but I'd like to know how you knew this???

Look behind you.

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

Project coverage is 87.58%. Comparing base (07813c8) to head (c293c74).
Report is 171 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #272      +/-   ##
==========================================
+ Coverage   86.84%   87.58%   +0.73%
==========================================
  Files          49       48       -1
  Lines        5496     5751     +255
  Branches     1372     1374       +2
==========================================
+ Hits         4773     5037     +264
+ Misses        462      445      -17
- Partials      261      269       +8

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


Vertica: table columns edit

Version 4.3.2.
I can change, for example, in MySQL, in the existing column column Data Type from the drop-down list.
http://ibb.co/nvf5sR
But in Vertica it does not work, the field is not available for modification,
I can do it  only through the SQL query.
http://ibb.co/bZOx6m

Column editor will be added in 5.0.6


nodes: rename Render* to Draw*

RenderToTexture is not renamed as it is not a drawing node.

You might also want to git ls-files|xargs sed -i 's/render =/draw =/'


Tooling support for Java functions

Should be able to deploy an java function app via functions CLI to Keda cluster

moved here https://github.com/Azure/azure-functions-core-tools/issues/1424


If DB is Postgres and if you restart container, All-projects missing error occurrs

Need to check if All-Projects presents in Postgres. In H2 DB this is done during build time.
https://bugs.chromium.org/p/gerrit/issues/detail?id=1305

Not sure what happened. That bash script should do the thing. Closing this as it's not reproducable with PosgreSQL


Version 2.3 release planning

All versions of django < 1.7 are deprecated, even django 1.7 will be deprecated in a month.
If we plan 2.3 release properly to january 2016, we should be able to drop support for django < 1.8. We'll still have to find a way to support django both 1.9 and 1.8 for the "remove" button of autocomplete choices.
We'll be able to introduce a few backward compatibility breaks that will enable closing other issues.

@jpic jpic changed the title from Version 3 release planning to Version 2.3 release planning 3 minutes ago
Text changed:
All versions of django < 1.7 are deprecated, even django 1.7 will be deprecated in a month.
If we plan 2.3 release properly to january 2016, we should be able to drop support for django < 1.8. We'll still have to find a way to support django both 1.9 and 1.8 for the "remove" button of autocomplete choices.
We'll be able to introduce a few backward compatibility breaks that will enable closing other issues.

Released in 2.3.0


Can not use in Sketch 41.2

Sketch Measure version:2.6.1
Sketch version: 41.2
MACOS 10.10.5
It's no reaction when I press any buttons on the sketch measure plug-in menu

@utom It's likely that this issue can be safely closed now.


Selenide-native way to perform swipe left/right actions

Is it possible to perform swiping actions on SelenideElements somehow?

I've prepared following PoC on how this could be implemented: https://github.com/selenide/selenide/pull/1066

@mszajowskiwr Yes, we could add such a command if we know a universal "algorithm" that stably works in all projects. I am not sure if such an algorithm exists. One implementation can be found in https://github.com/selenide/selenide/pull/1066/files, but is it generic enough? I don't know.
Anyway, you can declare custom command and use it like this:
https://selenide.org/2019/09/02/selenide-5.3.0/


Rule idea: Avoid using '<<' for string concate

In ruby concatenating strings by '<<' over '+' was shown more efficient in a few benchmarking and logically it's lighter because of not creating another copy of the string.
In chef this creates a weird issue.
if I try to put an example:
a='/opt'
directory a
file a<<'/.something'
Result:
Directory would be ‘/opt/.something’
File would be ignored as already exists
I think this wouldn't be considered a bug in chef by the way it works, so I am thinking of a rule to warn of this issue.
Don't use:
a << b
Use:
a + b
Because of said unexpected result.

That is probably better suited to Rubocop which can do things like "warning level cops" :-/ Right now we don't have any good way to have suggestion-y things in FoodCritic so anything added has to be pretty high on the bad idea spectrum.

I agree with @coderanger here.  The current design of Foodcritic is pretty binary.  Something is either good or bad. We lack the concept of "things you probably shouldn't do". We also tend to stick to pure chef DSL issues, with other issues left up to Rubocop (and cookstyle which wraps rubocop).


A Link to Quantum: a collection of video-games

To play the games, you must have the following installed:

pygame (www.pygame.org)
blender (https://www.blender.org)
(as well as pyquil)

For instructions on how to make pyquil work with blender, see "readme_install.txt".
Run "pythonw overworld.py" in the folder grove/grove/link_to_quantum_game. (NOTE the use of "pythonw" instead of the usual "python")
There are 4 games embedded inside the meta-game "Overworld", each of which can (currently) be played only once in each session of "Overworld". To play :-

"Quantum Block-out", move to the top-most cell in the middle;
"Quantum Darts", move to the bottom-most cell in the middle;
"Meyer Penny Classical/Quantum Game", move to the left-most cell in the middle;
"Meyer Penny Quantum/Quantum Game", move to the right-most cell in the middle
(the classical/classical and quantum/classical versions of the Meyer penny game can separately be played by calling "pythonw meyer_classical_classical_game.py" and "meyer_quantum_classical_game.py" respectively.)

@msohaibalam Thanks for the submission! We chatted a bit internally and think that these games would likely be best in their own repository rather than merging into grove. We'd love to link to them though on our website etc.
I'm putting together a list of Forest projects right now so if you do make a separate repo/link then let me know and I can add these games.

@msohaibalam, @willzeng Looks like cool stuff!
It does seem like these should live somewhere else, and it looks like there was a repo made by @msohaibalam  on his account.
Are we all agreed that we'll close this PR then?

@ampolloreno Thanks, and yes! I had earlier shared the link to the stand-alone repo with @willzeng elsewhere, but didn't realize I needed to close this PR. Closing it now.

@msohaibalam would great to add the games repo to this list of Forest software
https://github.com/rigetticomputing/forest-software/blob/master/README.md

@willzeng Done! Just created a PR there.


dongqn

Contributor: [contributor information - Optional]
SSH Public key: [contributor SSH public key (if you don't have one, submit the issue to receive instructions)"- Required]
Attestation: [any form of attestation for contribution (e.g., signature) - Optional]

+--[ED25519 256]--+
|  o..+.         |
| ..+ @ .         |
|  +o O          |
|.*oB = o         |
|+.O.+Eo S        |
|o+ *o. .         |
|+.+.+.           |
|o. =o .          |
|. o.o+           |
+----[SHA256]-----+

ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAILrMixcK2WQxP0/EoOthxPWiYZcbQQmX7m+XzbzcOyNo


Update README.md

Remove demo and mock saml sentence above the videos section. They are now listed in the Demo section
What does this PR do?

Fixes # (issue)
Type of change

[ ] Updated dependencies
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How should this be tested?

[ ] Existing unit tests

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code and corrected any misspellings
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

Let's leave it both places.


unhandled status from server: 400 Bad Request

Copilot Chat Extension Version:v0.17.1
VS Code Version:1.91.1
OS Version:Windows 11
Logs:
2024-07-13 18:38:16.941 [info] [chat fetch] request.response: [https://api.githubcopilot.com/chat/completions], took 202 ms
2024-07-13 18:38:16.941 [info] [chat fetch] Request ID for failed request: , 7fc84446-fed1-47a2-9d1e-2f108bae34c9
2024-07-13 18:38:16.943 [info] [chat fetch] Unhandled status from server:, 400, Bad Request

Steps to Reproduce:

On Every Chat message sent I get the error
this happened after my subscription expired then I entered the card again and renewed it but still had same issue before the renewal

Same here. I just got my Copilot subscription. I get this on every chat query. Everything is the latest version. Same happens in Insiders with just the Copilot extensions installed.
Hopefully it's just a temporary server/networking issue.

A Copilot "degradation" issue is being tracked at https://www.githubstatus.com. Looks like it's just about fixed.

A Copilot "degradation" issue is being tracked at https://www.githubstatus.com. Looks like it's just about fixed.

Thanks I will be checking it 🫡

It's working now.
Maybe when this happens, replace the "400 Bad Request" error with a more informative message that includes a link to GitHub Status. That could prevent bug reports being created for temporary service outages.


Flutter 2.0 Ripple Effect does not dismiss after you click many times in a short time duration.

0
I think it's really puzzling. In flutter 2.0: Click a widget more times in a short time duration, and then the ripple effect does not disappear. How to recover the original status of the widget.
Like this, the button stays the pressed ripple forever. And the more you click, the darker the background-color is.

Hi @yqjroy, please provide a complete minimal reproducible code sample so that we may verify this. Please provide the output of flutter doctor -v as well.
Thank you

@danagbemava-nc
$ fvm flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel unknown, 2.8.0, on macOS 11.6 20G165 darwin-x64, locale
zh-Hans-CN)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
[✓] Xcode - develop for iOS and macOS (Xcode 13.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 4.2)
[✓] IntelliJ IDEA Community Edition (version 2021.3.3)
[✓] Connected device (1 available)
• No issues found!
fvm flutter doctor -v
[✓] Flutter (Channel unknown, 2.8.0, on macOS 11.6 20G165 darwin-x64, locale
zh-Hans-CN)
• Flutter version 2.8.0 at /Users/roy/Library/Application
Support/fvm/versions/2.8.0
• Upstream repository unknown
• Framework revision cf44000065 (4 months ago), 2021-12-08 14:06:50 -0800
• Engine revision 40a99c5951
• Dart version 2.15.0
• Pub download mirror https://pub.flutter-io.cn
• Flutter download mirror https://storage.flutter-io.cn
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
• Android SDK at /Users/roy/Library/Android/sdk
• Platform android-31, build-tools 30.0.2
• Java binary at: /Applications/Android
Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 13.1)
• Xcode at /Applications/Xcode.app/Contents/Developer
• CocoaPods version 1.11.2
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 4.2)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
[✓] IntelliJ IDEA Community Edition (version 2021.3.3)
• IntelliJ at /Applications/IntelliJ IDEA CE.app
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
[✓] Connected device (1 available)
• Chrome (web) • chrome • web-javascript • Google Chrome 100.0.4896.75
• No issues found!
OutlinedButton(                             child: Text(                               SettingMessages.setting_Logout.tr,                               style: TextStyle(                                 fontSize: 14,                               ),                             ),                             style: OutlinedButton.styleFrom(                                 side: BorderSide(width: 0.5, color: LocalColors.mainColor,)                             ),                             onPressed: () {                               ShowUtil.showAlertDialog(context, Messages.information.tr, SettingMessages.setting_LogoutAlert.tr, sure: () {                                 c.logout();                               });                             },                           ),

Uploading QQ20220413-094203-HD.mp4…
@danagbemava-nc Here is the video.

@danagbemava-nc Here is the gif

Hi @yqjroy, you appear to be on an older version of flutter. Kindly upgrade to the latest version of stable, 2.10.4 to see if you still experience this issue.
If you do, please provide the updated flutter doctor -v as well as a minimal complete reproducible code sample
Thank you

Hi, @danagbemava-nc , wrap the MyApp in a GestureDetector Widget.
code as follows:
`import 'package:flutter/material.dart';
void main() {
int touchTime;
runApp(GestureDetector(
child: const MyApp(),
onTapDown: (detail) {
touchTime = DateTime.now().millisecondsSinceEpoch;
},
onTapUp: (detail) {
touchTime = DateTime.now().millisecondsSinceEpoch;
},
onTapCancel: () {
touchTime = DateTime.now().millisecondsSinceEpoch;
},
onTap: () {
touchTime = DateTime.now().millisecondsSinceEpoch;
},
onDoubleTap: () {
touchTime = DateTime.now().millisecondsSinceEpoch;
},
onLongPress: () {
touchTime = DateTime.now().millisecondsSinceEpoch;
},
onVerticalDragStart: (detail) {
touchTime = DateTime.now().millisecondsSinceEpoch;
},
onVerticalDragEnd: (detail) {
touchTime = DateTime.now().millisecondsSinceEpoch;
},
onVerticalDragCancel: () {
touchTime = DateTime.now().millisecondsSinceEpoch;
},
onVerticalDragUpdate: (detail) {
touchTime = DateTime.now().millisecondsSinceEpoch;
},
onForcePressStart: (detail) {
touchTime = DateTime.now().millisecondsSinceEpoch;
},
behavior: HitTestBehavior.translucent,
));
}
class MyApp extends StatelessWidget {
const MyApp({Key? key}) : super(key: key);
// This widget is the root of your application.
@override
Widget build(BuildContext context) {
return MaterialApp(
title: 'Flutter Demo',
theme: ThemeData(
primarySwatch: Colors.blue,
),
home: const MyHomePage(title: 'Flutter Demo Home Page'),
);
}
}
class MyHomePage extends StatefulWidget {
const MyHomePage({Key? key, required this.title}) : super(key: key);
final String title;
@override
State createState() => _MyHomePageState();
}
class _MyHomePageState extends State {
int _counter = 0;
void _incrementCounter() {
setState(() {
_counter++;
});
}
@override
Widget build(BuildContext context) {
return Scaffold(
appBar: AppBar(
title: Text(widget.title),
),
body: Center(
child: Column(
mainAxisAlignment: MainAxisAlignment.center,
children: [
const Text(
'You have pushed the button this many times:',
),
Text(
'$_counter',
style: Theme.of(context).textTheme.headline4,
),
OutlinedButton(onPressed: () {}, child: Text('Button')),
],
),
),
floatingActionButton: FloatingActionButton(
onPressed: _incrementCounter,
tooltip: 'Increment',
child: const Icon(Icons.add),
),
);
}
}
`

Hi @yqjroy, some work was done on the InkWell splashes recently and merged into the current master, can you check on the master channel to see if you're able to consistently reproduce this issue? I could not find a way to consistently reproduce on master although I could consistently reproduce on the stable channel.
To use the master channel, use the following commands
flutter channel master
flutter upgrade --force

Thank you

你好，邮件已收到！谢谢！

ok, i may try if i am free.

Hi @yqjroy, This issue has been fixed on master channel by this PR.

Sample code

import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: const MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({Key? key, required this.title}) : super(key: key);

  final String title;

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  int _counter = 0;

  void _incrementCounter() {
    setState(() {
      _counter++;
    });
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text(widget.title),
      ),
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            const Text(
              'You have pushed the button this many times:',
            ),
            InkWell(
              onTap: () {
                print("Tap Called");
              },
              onDoubleTap: () {
                print("Tap Called");
              },
              onTapCancel: () {
                print("Tap Cancelled");
              },
              child: Container(
                padding: EdgeInsets.all(20),
                child: Text(
                  '$_counter',
                  style: Theme.of(context).textTheme.headline4,
                ),
              ),
            ),
            OutlinedButton(onPressed: () {}, child: Text('Button')),
          ],
        ),
      ),
      floatingActionButton: FloatingActionButton(
        onPressed: _incrementCounter,
        tooltip: 'Increment',
        child: const Icon(Icons.add),
      ),
    );
  }
}

Demo
https://user-images.githubusercontent.com/104349824/167602723-713ed551-daec-4479-ac1c-6e24f30c8627.mov

I'm going to close this issue. If you disagree about this, please drop a comment and I will reopen it.


Does not compile

% idris --install verified.ipkg
Type checking ./Verified/Functor.idr
Type checking ./Verified/Functor/Maybe.idr
Type checking ./Verified/Functor/List.idr
Type checking ./Verified/Functor/Vect.idr
./Verified/Functor/Vect.idr:5:10:
When elaborating type of Verified.Functor.Vect.Vect n instance of Verified.Functor.VerifiedFunctor:
When elaborating argument f to type constructor Verified.Functor.VerifiedFunctor:
        No such variable Vect
./Verified/Functor/Vect.idr:15:1:
No type declaration for Verified.Functor.Vect.lemma2
./Verified/Functor/Vect.idr:21:1:
No type declaration for Verified.Functor.Vect.lemma1
% idris --version
<IP_ADDRESS>-
% git describe --always
a598acd

Thanks for the report! It seems Vect was moved out of Prelude and into Data.Vect. It's now fixed, but there's a new error instead:
...
./Verified/Algebra/Bool.idr:11:10:VerifiedSemigroup is not a type class
./Verified/Algebra/Bool.idr:20:10:VerifiedMonoid is not a type class

It seems VerifiedSemigroup and VerifiedMonoid were removed as well! A fix would be to copy the (old) definition into the repo. I will take a look at it later when I have more time (PRs welcome! ;).

No, they've been moved to Classes.Verified!

It compiles again.


(#194) Update nexus-repository package upgrade instructions

The new Nexus package incorporates the ability to seamlessly update a Nexus configuration that
utilizes SSL. As such, updated the documentation to provide an example one-line command that is
now possible to use to upgrade this package.

NOTE TO REVIEWERS:
Don't switch this off of Draft until the new nexus-repository package changes are merged on the package source repository. That way these docs hit the site at the same time as the package.


mac alt modifier broken

macOS 10.13.3
holding alt + / => | or alt + n => ~ does somehow not work for me anymore

seems to be an issue with german keyboard layout, never noticed it on my US keyboard and if I switch the german one in software it works (like on a normal US keyboard)
can this mapping be added or maybe alt is just not supported?

There's an outstanding bug in winit to properly support non-US-QWERTY layouts. The bug is basically that the keymap is applied for received characters, but not for key codes. I believe this is a duplicate of #458.


chore: DO NOT MERGE chore: test github workflow

Please provide a paragraph or two giving a summary of the change, including relevant motivation and context.
Checklist:
Remove the checklist to signal you've completed it. Enable auto-merge if the PR is ready to merge.

[ ] If the pull request requires a cryptography review (e.g. cryptographic algorithm implementations) I have added the 'crypto' tag.
[ ] I have reviewed my diff in github, line by line and removed unexpected formatting changes, testing logs, or commented-out code.
[ ] Every change is related to the PR description.
[ ] I have linked this pull request to relevant issues (if any exist).

Closing. Not needed.