Alexa app can't discover my Alexa Dot (2nd Gen) device

I've uploaded the .ino file to the Wemos board. I can see it connected to my WiFi, and I can connect to the IP address it's connected too but my Alexa app isn't finding the device. Below is my code, does anything look wrong?
https://pastebin.com/d2BQVjYu

This project does not support Alexa app. If you want to use app, try my other project https://sinric.com

Project is working for me, but problem is every time nodemcu restarts, alexa is not able to recognise the device giving the error, unable to respond. After pushing the RST Button, device is back and recognisable.

Do you habe GPIO-9 in use? This one must not be used. Also consider a pullup resistor on reset. Just 4 + 5 work stable.
Best regards
Sascha
Am 15.12.2018 um 21:32 schrieb sabhay1996 <notifications<EMAIL_ADDRESS>This project does not support Alexa app. If you want to use app, try my other project https://sinric.com
Project is working for me, but problem is every time nodemcu restarts, alexa is not able to recognise the device giving the error, unable to respond. After pushing the RST Button, device is back and recognisable.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/kakopappa/arduino-esp8266-alexa-wemo-switch/issues/33#issuecomment-447595943, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKwM-2VPdW5Gf9wGFi9ygm2QG2cqIP2tks5u5VxQgaJpZM4THhwT.

Do you habe GPIO-9 in use? This one must not be used. Also consider a pullup resistor on reset. Just 4 + 5 work stable. Best regards Sascha Am 15.12.2018 um 21:32 schrieb sabhay1996 <notifications<EMAIL_ADDRESS>This project does not support Alexa app. If you want to use app, try my other project https://sinric.com Project is working for me, but problem is every time nodemcu restarts, alexa is not able to recognise the device giving the error, unable to respond. After pushing the RST Button, device is back and recognisable. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#33 (comment)>, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKwM-2VPdW5Gf9wGFi9ygm2QG2cqIP2tks5u5VxQgaJpZM4THhwT.

I am still using 5 as it is pre defined in the project.

Which Module do you use (esp - sure... which concrete model?) any special circuit?
Best regards
Sascha
Am 16.12.2018 um 06:30 schrieb sabhay1996 <notifications<EMAIL_ADDRESS>Do you habe GPIO-9 in use? This one must not be used. Also consider a pullup resistor on reset. Just 4 + 5 work stable. Best regards Sascha Am 15.12.2018 um 21:32 schrieb sabhay1996 <notifications@github.commailto:notifications<EMAIL_ADDRESS>This project does not support Alexa app. If you want to use app, try my other project https://sinric.com Project is working for me, but problem is every time nodemcu restarts, alexa is not able to recognise the device giving the error, unable to respond. After pushing the RST Button, device is back and recognisable. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#33 (comment)https://github.com/kakopappa/arduino-esp8266-alexa-wemo-switch/issues/33#issuecomment-447595943>, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKwM-2VPdW5Gf9wGFi9ygm2QG2cqIP2tks5u5VxQgaJpZM4THhwT.
I am still using 5 as it is pre defined in the project.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/kakopappa/arduino-esp8266-alexa-wemo-switch/issues/33#issuecomment-447619018, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKwM-yaN6b97Q-U5P-aRKMnSwxn-u7cHks5u5dp5gaJpZM4THhwT.

Which Module do you use (esp - sure... which concrete model?) any special circuit? Best regards Sascha Am 16.12.2018 um 06:30 schrieb sabhay1996 <notifications<EMAIL_ADDRESS>Do you habe GPIO-9 in use? This one must not be used. Also consider a pullup resistor on reset. Just 4 + 5 work stable. Best regards Sascha Am 15.12.2018 um 21:32 schrieb sabhay1996 <notifications@github.commailto:notifications<EMAIL_ADDRESS>This project does not support Alexa app. If you want to use app, try my other project https://sinric.com Project is working for me, but problem is every time nodemcu restarts, alexa is not able to recognise the device giving the error, unable to respond. After pushing the RST Button, device is back and recognisable. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#33 (comment)<#33 (comment)>>, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKwM-2VPdW5Gf9wGFi9ygm2QG2cqIP2tks5u5VxQgaJpZM4THhwT. I am still using 5 as it is pre defined in the project. — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#33 (comment)>, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKwM-yaN6b97Q-U5P-aRKMnSwxn-u7cHks5u5dp5gaJpZM4THhwT.

I am using nodemcu lolin v3.
Flash Size: 4M (1M SPIFFS)
IwIP: 2v Higher Bandwidth
Upload Speed: 115200
Board: NodeMCU 1.0
VTable: Flash

Ah ok. Lolin v3 often comes up with reset issues and I was able to reproduce your issue. So GPIO0 should be pulled up to 3.3V using a 10k resistor AFTER being programmed. Keep in mind that re-programming using USB is only possible when removing this pullup resistor. So a jumper makes sense here.
Best regards
Sascha

Am 16.12.2018 um 12:08 schrieb sabhay1996<EMAIL_ADDRESS>lolin v3

Please correct me if did something wrong, I tried using 2 jumper and 10k between them, from gpio 0/D3 to 3.3v.
I have configured the project with gpio 4/D2 and using alternative 3.3V and GND for the relay.
But still I need to press the reset button.

Please Check if there is a soldered resistor on your board. If so either remove it or try an 3k3 instead of the 10k... good luck!
Am 16.12.2018 um 16:09 schrieb sabhay1996 <notifications<EMAIL_ADDRESS>Please correct me if did something wrong, I tried using 2 jumper and 10k between them, from gpio 0/D3 to 3.3v.n
I have configured the project with gpio 4/D2 and using alternative 3.3V and GND for the relay.
But still I need to press the reset button.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/kakopappa/arduino-esp8266-alexa-wemo-switch/issues/33#issuecomment-447650323, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKwM-w1LXzDbsfCftTYi0wui5evBEe43ks5u5mILgaJpZM4THhwT.

Thanks buddy for promptly replying to help me.
Still no success, after uploading the sketch, it connects to the wifi, when I reboot, it doesn't connect I need to manually press the reset switch.
I tried 3K3 resistance from GPIO0 to 3.3V
I tried 10K resistance from GPIO0 to 3.3V
GPIO5 to GND as well.
Tried same with another boards as well no success.
Maybe I am doing something please help?


adguardhome: 0.107.50 -> 0.107.51

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for adguardhome is: Network-wide ads & trackers blocking DNS server
meta.homepage for adguardhome is: https://github.com/AdguardTeam/AdGuardHome
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.107.51 with grep in /nix/store/5yr2i7qgqbrdabdplzidcl0cgvzhjgkq-adguardhome-0.107.51
found 0.107.51 in filename of file in /nix/store/5yr2i7qgqbrdabdplzidcl0cgvzhjgkq-adguardhome-0.107.51

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

adguardhome

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/5yr2i7qgqbrdabdplzidcl0cgvzhjgkq-adguardhome-0.107.51 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A adguardhome https://github.com/r-ryantm/nixpkgs/archive/91e7a2dfb45091cf7df6eb1d212939bfb3213b99.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/91e7a2dfb45091cf7df6eb1d212939bfb3213b99#adguardhome

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/5yr2i7qgqbrdabdplzidcl0cgvzhjgkq-adguardhome-0.107.51
ls -la /nix/store/5yr2i7qgqbrdabdplzidcl0cgvzhjgkq-adguardhome-0.107.51/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

adguardhome

Maintainer pings
cc @numkem @iagocq @rhoriguchi for testing.

Result of nixpkgs-review pr 318568 run on aarch64-darwin 1

1 package built:

adguardhome


conan is not working after pip install

When I install conan using pip3, my PC could not found conan command .
this is solution.

find conan command
$python3 -m site --user-base
/home/younlea/.local

update path .
export PATH=$PATH:/home/younlea/.local/bin

conan install . -s build_type=Release -b missing -of build

this issue is only share solution with you . ^^


[migration-guide] from-gatsby initial page draft

This is a first draft of a Migrate from Gatsby to Astro guide.
It is not a step-by-step walk-through, because it would be difficult to predict what someone's existing project looks like. So it's more, "things to think about, probably roughly in this order" with varying degrees of explicit instruction.
It may need significant work, and is open to any and all suggestions!
It is intentionally longer than shorter, because it's easier to cut out whatever we decide is unnecessary. For the sake of starting this draft, some of it is a little hand-wavy with the knowledge that if things aren't explicit enough or don't capture the right nuance, someone's gonna speak up. Not all links to related docs sections are yet in place, because I could be linking forever. So, a comprehensive "linking enough but not too much" audit is yet to come.
The goals of this page are:

To highlight the key differences and similarities to prepare the reader for switching frameworks
To guide a little more explicitly through initial project creation, offering two suggestions for getting started:

create-astro, then bring existing Gatsby files over
update dependencies in package.json, install Astro manually, and edit files in place.

To explain astro.config in relation to Gatsby's configuration files, and to help the reader extract any existing configuration and put it into the appropriate places
To provide general but comprehensive guidance on converting existing .js(x) Gatsby files into .astro components, including:

a before (Gatsby)/after (Astro) example of a component
SEVERAL examples of walk-through conversions
a list of several key syntax differences (e.g. className, {children}, <Link to="" /> style={{}}) and their Astro equivalents

To suggest a migration path starting with converting Layouts (so that pages will be complete HTML documents when using a Layout), then importing existing pages and posts.

The challenges of this page are:

To fulfill the goals without overwhelming the reader. I'm less concerned about page length itself and more concerned that the sidebar doesn't make people say, "Yikes!"
To write section headings that will not confuse our Algolia search results and send people to this page for "normal docs things" (e.g. Image Integration, Site Configuration). This is why the headings are now intentionally long-ish, because shortening them runs the risk of Algolia mistaking the section for regular docs.
Gatsby components are HUGE!  😅 It's admittedly visually overwhelming to have SUCH LARGE code examples as "before" models, when they include one (or more!) functions, and GraphQL queries that take so many lines to format etc. It's making this page look long, but the actual process for converting the files is entirely manageable, and I'd love to be able to show that here.

Site Infrastructure Note: Uses the CMS Guides templating for now. By the time we have 3 guides ready for publishing, we will have also created a proper Migrations Guide landing page and stubs as placeholders for other guides.

This is amazing @sarah11918! There’s just so much detail and content — awesome work.
First impression is that this feels pretty good. Quick thoughts although I suspect you’re already aware of/on this for editing:

Some of the examples can probably be more minimal to help focus what they’re illustrating (e.g. the .banner styles in the first example).
Relatedly, can’t decide if the blog starter examples are helpful because some folks might be literally coming from there, or more cluttered than what we might be able to do if we tailored or before/after examples a little more.
In the “Switch to Astro” section, it might be helpful to make clear which of the two migration paths (create-astro vs install manually) each sub-section relates to.

In terms of UI, I’m wondering if this is a case where a 2-up component that lets us show the Gatsby JSX and the Astro component side by side might be helpful. This is only really helpful on larger screens where there’s space, but would probably really ease comparison.

Adding Corbin's Question from his pull request to this branch:

A few questions I had along the way:

Is the code highlighting/naming correct in all code blocks?

Are we happy with the current iteration of the  component? It's one of the only instances without a before/after

Are we happy with the length? It got long quick.

D'oh! On my phone! This should still be marked as a draft! As soon as I can figure out how to do that, I will remark it as draft lol

I'm wondering if we should add a section for "interactive content" and a few small guidances towards how to replace React code with vanilla JavaScript and/or use preact/compat for a smaller bundle size.
Is this too prescriptive for our docs?

I wouldn't consider that something for these guides, since that is more all-purpose re: write React into Astro script that is useful even outside of a migration context. (e.g. Someone built their Astro project using a lot of React components, since that's what they know and it was easy to get up and running. But now, they want to try to convert some of those components to Astro. I think THAT is a much broader framing of it, and I honestly think that's a path a lot of people have taken/are taking!
So, I think it could be a great addition to docs somewhere, and then we link to it from here. We've been discussing something more like a "Recipes" page (not full-blown "tutorial", but guided walk-through) and that could be and interesting place for this. Or, an entire "Rewriting X as Astro" landing page with set of individual pages... like the Deploy/CMS/Migration Guide. If only we knew someone who could approach Astro from a set of other frameworks....

Closing, because we've picked this up in #2170 🚀


Error with repos.updateKey

Hello,
When i call repos.updateKey, i got an error 404. I checked my parameters, but it seems like everything is right.
Any idea why is it happening ?

Public keys are immutable. If you need to update a public key, remove the key and create a new one instead.


Enable interactivity inside notebook for pyvista backend

What does this implement/fix?
Add basic interactivity inside a jupyter notebook for the PyVista backend. Please note that panel is required to achieve this.
Additional information
We obtain the following:

And this is the code used in the notebook:
from mne.viz import set_3d_backend
set_3d_backend("pyvista")

import mne
from mne.datasets import sample
data_path = sample.data_path()
raw_fname = data_path + '/MEG/sample/sample_audvis_raw.fif'
subjects_dir = data_path + '/subjects'
subject = 'sample'
trans = data_path + '/MEG/sample/sample_audvis_raw-trans.fif'
info = mne.io.read_info(raw_fname)
mne.viz.plot_alignment(info, trans, subject=subject, dig=True,
                       meg=['helmet', 'sensors'], subjects_dir=subjects_dir,
                       surfaces=['head-dense'])

What do you think @larsoner , @agramfort ?

Otherwise LGTM (but I did not test it)

your example above works great for me in the notebook with interaction.
+1 for MRG

Thanks @GuillaumeFavelier !


[help wanted] service-worker file is not server from top level

Hey,
my problem is probably cause of my lack of knowledge of the topic, but I'm struggling with it since yesterday and thought I might ask for a help eventually ;)
I use pretty standard configs, however I cannot force webpack to serve generated service worker at top level of my app during development. In normal case I would just add new entry to the webpack configuration, but here I have no entry point for a service-worker file as it is generated from the scratch by a plugin. Is there any option to allow that now?
my webpack.config.js (important parts)
const SWPrechaceConfig = require('./sw-precache-config')
const config = {
	context: __dirname,
	entry: {
		app: ['./src/app/index'],
	},
	output: {
		path: path.resolve(__dirname, './dist'),
		filename: '[name].js',
	},
	resolve: {
		extensions: ['', '.es6', '.js', '.json'],
	},
	module: {
		preLoaders: [
			{test: /\.jsx?$/, loader: 'eslint', exclude: /node_modules/},
		],
		loaders: [
			{test: /\.jsx?$/, loaders: ['react-hot', 'babel'], exclude: /node_modules/},
			{test: /\.html$/, loader: 'raw'},
			{test: /\.css$/, loader: 'css'},
			{test: /\.styl$/, loader: 'style!css!postcss!stylus'},
			{test: /\.json$/, loader: 'json'},
			{test: /\.svg$/, loader: 'babel!svg-react'},
		],
	},
	plugins: [new SWPrecacheWebpackPlugin(SWPrechaceConfig)],
}

and my SWPrechaceConfig:
module.exports = {
	cacheId: "local_app",
	maximumFileSizeToCacheInBytes: 4194304,
	runtimeCaching: [{
		handler: "cacheFirst",
		urlPattern: /[.]mp3$/,
	}],
	staticFileGlobs: [
		"dist/app.js"
	],
	stripPrefix: "dist/",
	verbose: true,
}

@Andarist I if you want to pass a set of sw-precache options into the plugin you just need to add it as an options key:
const SWPrechaceConfig = require('./sw-precache-config');

const config = {
    ...
    },
    plugins: [
        new SWPrecacheWebpackPlugin(
            {
                options: SWPrechaceConfig,
            }
        )
    ],
}

Also currently the output path is going to be compiler.options.output.path. In your situation, that would put the file here: path.resolve(__dirname, './dist') as specified in your output in your config.
I will update and allow you to just pass SWPrecacheConfig, the way you are using it, that makes more sense than having the options requirement.

And the plugin will automatically determine the files to cache based on your bundles being built if you omit the staticFileGlobs argument.

Hah, I even didn't realize it wasn't using my custom config cause I was focused on not being able to serve it through localhost.
My problem was (and still is) that I don't know how to serve generated output file (which is generated at path I wanted - which is /dist). I can access my localhost:3070/app.js but cannot access localhost:3070/service-worker.js without adding second entry in webpack's main configuration, but such solution is wrong, cause it needs to have service-worker.js generated first before running webpack and I would like to have it done dynamically.

So this shouldn't be an entry point, the service worker is generated after the build because it needs the bundled files in order to build.
This file should be added to your dist/ folder after the build is done (which it sounds like it is).
Are app.js and service-worker.js in the same folder?
Also did you add:
<script>
navigator.serviceWorker.register('/service-worker.js');
</script>

to your index.html file somewhere?

This file should be added to your dist/ folder after the build is done (which it sounds like it is).
Yes, it is.
Are app.js and service-worker.js in the same folder?
Yes, they are.
Also did you add:

<script>
navigator.serviceWorker.register('/service-worker.js');
</script>
to your index.html file somewhere?

Yes, although I'm calling it from my js files, not html - which shouldn't make any difference.
Could you maybe make an example available on github in this repo? It would be really appreciated to see if we are even on the same page.

@Andarist here you go: https://github.com/goldhand/sw-precache-webpack-plugin/tree/master/examples

Ok, I know what's the difference between our setups :P You are using vanilla express here and I have WebpackDevServer configured

Yeah, Webpack dev server won't work with this because it is serving bundles from memory.  I should note that in the docs.  Would be cool to figure out a way to get it to work nicely with HMR too.


The external system terminal close after running script if the Python console exits due to an exception

Issue Report Checklist

[x] Searched the issues page for similar reports
[ ] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[x] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[x] Could not reproduce inside jupyter qtconsole (if console-related)
[x] Tried basic troubleshooting (if a bug/error)

[x] Restarted Spyder
[x] Reset preferences with spyder --reset
[x] Reinstalled the latest version of Anaconda
[x] Tried the other applicable steps from the Troubleshooting Guide

[x] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
Especially when testing code involving PyQt or PySide, I often like to execute my code using an external system terminal on Windows with the option Interact with the Python console after execution checked.

However, very often when an exception is raised during execution, the Python console and the external system terminal both close, so that it is impossible to see the traceback of the error.
Below is a minimal working example I've put together that allow to reproduce this behavior on my system:
import sys
from PyQt5.QtWidgets import QPushButton, QWidget, QApplication, QGridLayout

class SomeClass(QWidget):
    def __init__(self):
        super().__init__()
        layout = QGridLayout(self)
        btn_crash = QPushButton('Crash')
        btn_crash.clicked.connect(self.crash)
        btn_crash2 = QPushButton('Crash2')
        btn_crash2.clicked.connect(self.crash2)
        btn_close = QPushButton('Close')
        btn_close.clicked.connect(self.close)
        layout.addWidget(btn_crash)
        layout.addWidget(btn_crash2)
        layout.addWidget(btn_close)

    def show(self):
        super().show()

    def crash(self):
        raise ValueError

    def crash2(self):
        return self.crash2()

if __name__ == '__main__':
    app = QApplication(sys.argv)
    window = SomeClass()
    window.show()
    sys.exit(app.exec_())

What steps reproduce the problem?

Run the script in an external system terminal in Spyder with the option  Interact with the Python console after execution
Click on Close button
Run the script again
Click on Crash or Crash2 button

What is the expected output? What do you see instead?
When clicking on the Close button, the Python console and the terminal do not close and it is indeed possible to interact with the Python console after execution. When either the Crash or Crash2 button is clicked, the Python console and the external system terminal both close, so that it is impossible to see the traceback of the error.
What I have done to go around this behavior on my system is to change the way the external system terminal is started in Windows from (see here) :
cmd = 'start cmd.exe /c "cd %s && ' % wdir + ' '.join(p_args) + '"'

to (see https://stackoverflow.com/a/46882828/4481445) :
cmd = 'start cmd.exe /K "cd %s && ' % wdir + ' '.join(p_args) + '"' + ' ^&^& exit'

This prevents the external system terminal from closing when the Python console exit with an error code other than 0. If there is no error though, then the terminal is closed automatically like before.
Versions

Spyder version: Spyder 4.0.0.dev0
Python version: Python 3.7.1 64-bit
Qt version: Qt 5.9.6
PyQt version: PyQt5 5.9.2
Operating System name/version: Windows 10

@jnsebgosselin I guess this is also happening for 3.x?

@jnsebgosselin I guess this is also happening for 3.x?

Yes, It should do the same thing in 3.x. However, I do not consider the current behavior to be a bug per se, though I think that implementing the change I'm proposing, either as the default or as an additional option, would be a great Ux-usability improvement.

I think this could go then on the 3.x series @ccordoba12 ?

Yes, It should do the same thing in 3.x. However, I do not consider the current behavior to be a bug per se, though I think that implementing the change I'm proposing, either as the default

I would prefer default, I do not see how useful is the current behavior, nor providing an option for that (also it makes it easier to buble up the change to master :-p)
But I would like to hear opinions :-) @spyder-ide/core-developers

I agree, @goanpeca ; I don't see how immediately closing the terminal window if an error occurs (thus hiding the error, and possibly even that an error occurred at all) would ever be what a user would want or expect. In the worst case, they can spend a second closing it themselves, which is nothing compared to the cost of the alternative in the most likely case.

@jnsebgosselin could you work on a fix aimed at the 3.x branch? No configuration needed :-)

Cool, I'll prepare a PR  then.


Rya-307 MongoDB Rya DAO Batch Writer

Description
Improved Rya MongoDB ingest of statements through the Sail Layer and Rya DAO by queueing up multiple inserts at a time so can be written as a single batch. If no statements in the batch have been written after a set time limit then they are flushed out into the datastore. The size of the batch and the time limit are configurable.
Tests
Unit Tests/Integration Tests
Links
Jira
Checklist

[ ] Code Review
[ ] Squash Commits

People To Review
@amihalik
@meiercaleb
@DLotts
@jessehatfield
@isper3at

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/273/Build result: ABORTED[...truncated 6.49 MB...][INFO]                                                                         [INFO] ------------------------------------------------------------------------[INFO] Building Apache Rya PCJ Fluo Demo 3.2.11-incubating-SNAPSHOT[INFO] ------------------------------------------------------------------------[INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ rya.pcj.fluo.demo ---[WARNING] Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy: java.util.concurrent.ExecutionException: Invalid object ID 12 iota=55[INFO] [INFO] --- apache-rat-plugin:0.11:check (check-licenses) @ rya.pcj.fluo.demo ---[INFO] 51 implicit excludes (use -debug for more details).[INFO] Exclude: /resources/META-INF/services/[INFO] 4 resources included (use -debug for more details)[INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0 approved: 4 licence.[WARNING] Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy: java.util.concurrent.ExecutionException: Invalid object ID 12 iota=55[INFO] [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-mvn) @ rya.pcj.fluo.demo ---[WARNING] Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy: java.util.concurrent.ExecutionException: Invalid object ID 12 iota=55[INFO] [INFO] --- maven-remote-resources-plugin:1.5:process (default) @ rya.pcj.fluo.demo ---Build was abortedchannel stoppedSetting status of 154e589a082b91c4556079be4fabd55d37480360 to FAILURE with url https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/273/ and message: 'FAILURE 'Using context: Jenkins: clean package -Pgeoindexing

asfbot build

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/274/Failed Tests: 2incubator-rya-master-with-optionals-pull-requests/org.apache.rya:rya.geoindexing: 2org.apache.rya.indexing.geotemporal.MongoGeoTemporalIndexIT.ensureInEventStore_Testorg.apache.rya.indexing.geotemporal.MongoGeoTemporalIndexIT.constantSubjQuery_Test

looks good to me -- @isper3at are you ok with this pr?

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/320/Build result: ABORTED[...truncated 6.54 MB...][INFO]                                                                         [INFO] ------------------------------------------------------------------------[INFO] Building Apache Rya PCJ Fluo Demo 3.2.11-incubating-SNAPSHOT[INFO] ------------------------------------------------------------------------[INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ rya.pcj.fluo.demo ---[WARNING] Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy: java.util.concurrent.ExecutionException: Invalid object ID 12 iota=55[INFO] [INFO] --- apache-rat-plugin:0.11:check (check-licenses) @ rya.pcj.fluo.demo ---[INFO] 51 implicit excludes (use -debug for more details).[INFO] Exclude: /resources/META-INF/services/[INFO] 4 resources included (use -debug for more details)[INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0 approved: 4 licence.Build was aborted[WARNING] Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy: java.util.concurrent.ExecutionException: Invalid object ID 12 iota=55[INFO] [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-mvn) @ rya.pcj.fluo.demo ---channel stopped[WARNING] Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy: hudson.remoting.Channel$OrderlyShutdown[INFO] [INFO] --- maven-remote-resources-plugin:1.5:process (default) @ rya.pcj.fluo.demo ---Setting status of 89d0f104522fd1c17ed61a6d2f6bb7bbb85d48eb to FAILURE with url https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/320/ and message: 'FAILURE 'Using context: Jenkins: clean package -Pgeoindexing

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/340/

@pujav65 sounds good.  We've been testing out #186 and that's about to be merged.  Hold off on merging #181 until #186 (and perhaps #182) is on master.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/344/

@isper3at Thanks for taking a look at it.  I'm testing it out now before I merge it


'timelapse' crashes my pi

hi -- new user with a ZWO and allsky is fantastic. I had it running overnight last night, and early manual timelapses ran fine and looked great.  This morning I have about 3000 images, and when I run the timelapse script it runs for a while and then the pi restarts.  I have run it with the allsky service not running, and I was wondering about heat so I put some heatsinks on and then ran ffmpeg nice -20, and put on all the ffmpeg debugging.  No errors in allsky.log or syslog or from ffmpeg -- it just restarts, after about 15 seconds, and it rarely gets to 500 frames before it does.
Any thoughts on how to debug or what the bottlenecks might be?  Thanks.

Use a swap file on youre pi works great

Samgribley,
Did you try using a swap file?  If so, did it work?
Eric

I use pi 3B+ and I tired with both ZWO (asi120mc) and v1.3 camera module. For me, timelapse process crashed my pi too and when I ran the timelapse script manually I noticed the pi crashed when it processed to copy up until certain image file.
So I went and change timelapse width and height in the config.sh using the GUI editor. And now it works fine. I also noticed that the image copy process completed successfully without getting stuck at certain file.

pimmoon, are you using a swap file?  If not, try using one and see if it works with full-sized files.
Eric

I have not tired swap file but I really want to try. Is there any particular settings you recommend to run allsky on Pi 3B+?
Also, I plan to get a new Pi Zero WH to run allsky as well, but on Pi Zero, I plan to use basic v1.3 camera module with wide angle lense. Is there settings for Pi Zero I should be aware of?
Thank you!

I can’t help with either question.  I’m pretty sure other people with Pi 3 are using swap files – search the issues and Google.
The same for the Pi Zero.  I also think others have said it’s slower, so creating a timelapse, for example, will take longer.
Eric
From: pimmoon @.>
Sent: Tuesday, August 10, 2021 1:05 AM
To: thomasjacquin/allsky @.>
Cc: EricClaeys @.>; Comment @.>
Subject: Re: [thomasjacquin/allsky] 'timelapse' crashes my pi (#314)
I have not tired swap file but I really want to try. Is there any particular settings you recommend to run allsky on Pi 3B+?
Also, I plan to get a new Pi Zero WH to run allsky as well, but on Pi Zero, I plan to use basic v1.3 camera module with wide angle lense. Is there settings for Pi Zero I should be aware of?
Thank you!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/thomasjacquin/allsky/issues/314#issuecomment-895753159 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AT2PYK65GCD5LC3ZCDS3GYTT4C6PJANCNFSM4WQW65ZA .
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675  or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .  https://github.com/notifications/beacon/AT2PYK2GJE5QBB6NHRQ5UWTT4C6PJA5CNFSM4WQW65ZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOGVSBXRY.gif


Update rx-recompose's recompose dependency to ^0.14.0

Is that safe to do so?

Or perhaps not peerDependency? In my case I want to use the latest version of recompose and rx-recompose at the same time.

The newest versions of all packages are always tested against each other, despite what the peerDependency says.
I need to update the release script to automatically bump dependencies when they change.

How is this issue going? I would like to help if there is still no progress.

Vote +1

Fixed (manually) in latest release


openchain.org offers smart contracts, docs do not?

is it implemented? if so, where can i find any docs on that?
and there were no commits for months, wondering if the project is alive at all.

How are smart contracts used? Can't find any reference to them in the source code or documentation?

Smart contracts are simply scripts that use the API to read data and submit transactions to the chain. This is the simplest and most efficient way to build smart contracts. You can use the programming language of your choice for that.

Thanks for the clarification

And where is the documentation for creating smart contracts and creating custoem function adn calling it ? Please let me know.


Update license-acceptance gem to handle users specifying mixlib version as a channel

Description
☝
Related Issue
N/A
Types of changes

[ ] 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 change)
[ ] Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

[ ] I have read the CONTRIBUTING document.
[ ] I have run the pre-merge tests locally and they pass.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
[ ] All commits have been signed-off for the Developer Certificate of Origin.

closing in favor of #8595


CodeLens debugging using global tool

@gep13 I did two things different to what you did in the video:

I removed the windows property from settings and added an object with default and win32 like I've done with the launchCommand.
I fixed the reason debugging did not work during the video: I removed the quotes (") from the target. Not sure why this is a problem but debugging does not work (any longer) when they are present.

@gep13 I've also started adding the global tool to the "install debug dependencies" - however currently not in this PR, as I had the impression that it would be a bit much :-)
Also, that's probably not done, as installing CoreCLR is done in quite some places..
The work is currently here: https://github.com/nils-a/cake-vscode/compare/feature/debug-core-tool...nils-a:feature/install-global-tool (as a branch, based on the branch from this PR)

@nils-a is this ready for review, or is it still in draft?

@gep13 I removed the draft status and included the installation of the NET core global tool. So feel free to review.

@nils-a thank you very much for getting this added!


Email verification

Create email verification mechanism throe Twilio SendGrid.

When verifying here who is the verifying entity? When we are talking about a P2P setting an email would have to be verified for each peer individually so this must be for some central peer registry or other trusted entity.

@tompro all right, usually such functionality is implemented on server side, which is trusted by all clients. However our server part is not created yet (looking for a Dev). Thats why for prototype we decided to implement client side validation only. Validation request is initiated by our client and email is sent with localhost confirmation callback. So it can be validated only when User clicks Confirm button at the same host where client is installed. (We realize that in such edition its not really a reliable validation)

Don't get me wrong, we could do P2P verification using a second (eg. the push channel) comms to send back the token but this would only be valid between two parties and need a third mechanism (eg. WOT) to populate to other parties.

Correct, thats base identity mechanism in our system, key exchange process happens between two Users only after that they become mutually trusted. The same procedure User needs to perform with all his contacts. But as I mentioned email validation its not an identity process, its not relevant and not trusted by other Users.


Unexpected Token L

[Enter steps to reproduce below:]

Open python or julia file
alt-cmd-enter or command pallet - Hydrogen: Run

After this, hydrogen is disabled and won't run without restarting.
Atom Version: 1.5.3
System: Mac OS X 10.11.4
Thrown From: Hydrogen package, v0.7.0
Stack Trace
Failed to activate the Hydrogen package
At Unexpected token L

SyntaxError: Unexpected token L
    at Object.parse (native)
    at Object.<anonymous> (/Users/KBLaptop/.atom/packages/hydrogen/lib/kernel-manager.coffee:11:22)
    at Object.memoized [as getAvailableKernels] (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/babel-core/node_modules/lodash/index.js:7912:27)
    at /Users/KBLaptop/.atom/packages/hydrogen/lib/autocomplete-provider.coffee:6:37
    at Object.<anonymous> (/Users/KBLaptop/.atom/packages/hydrogen/lib/autocomplete-provider.coffee:5:41)
    at Object.<anonymous> (/Users/KBLaptop/.atom/packages/hydrogen/lib/autocomplete-provider.coffee:1:1)
    at Module._compile (/Applications/Atom.app/Contents/Resources/app.asar/src/native-compile-cache.js:103:30)
    at Object.defineProperty.value [as .coffee] (/Applications/Atom.app/Contents/Resources/app.asar/src/compile-cache.js:208:21)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (/Applications/Atom.app/Contents/Resources/app.asar/src/native-compile-cache.js:50:27)
    at Object.<anonymous> (/Users/KBLaptop/.atom/packages/hydrogen/lib/main.coffee:13:24)
    at Object.<anonymous> (/Users/KBLaptop/.atom/packages/hydrogen/lib/main.coffee:1:1)
    at Module._compile (/Applications/Atom.app/Contents/Resources/app.asar/src/native-compile-cache.js:103:30)
    at Object.defineProperty.value [as .coffee] (/Applications/Atom.app/Contents/Resources/app.asar/src/compile-cache.js:208:21)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (/Applications/Atom.app/Contents/Resources/app.asar/src/native-compile-cache.js:50:27)
    at Package.module.exports.Package.requireMainModule (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:720:27)
    at Package.module.exports.Package.activateNow (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:172:16)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/package.js:800:25
    at Function.module.exports.Emitter.simpleDispatch (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/event-kit/lib/emitter.js:25:14)
    at Emitter.module.exports.Emitter.emit (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/event-kit/lib/emitter.js:125:28)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:241:20)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:3:61
    at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:536:16)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:359:22)
    at WindowEventHandler.module.exports.WindowEventHandler.handleDocumentKeydown (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:97:36)

Commands
     -0:40.7.0 core:save (atom-text-editor.editor.is-focused)
  7x -0:15.5.0 core:backspace (atom-text-editor.editor.is-focused)
     -0:03.3.0 editor:newline (atom-text-editor.editor.is-focused)
     -0:02.2.0 core:move-up (atom-text-editor.editor.is-focused)
     -0:00.8.0 hydrogen:run-and-move-down (atom-text-editor.editor.is-focused)

Config
{
  "core": {},
  "Hydrogen": {
    "grammarToKernel": "{\"python\":\"Python 3\"}"
  }
}

Installed Packages
# User
Hydrogen, v0.7.0
jupyter-notebook, v0.0.9
language-julia, v0.5.0

# Dev
No dev packages

@kescobo Here we go again. Please paste here output of this two commands:
ipython kernelspec list --json```

I think I should add ignoring of stderr.

Heh, yeah - no kidding. It worked for a sec after I upgraded, then the next day... Ugh. Sorry for the bother.
KBonham:~ KBLaptop$ jupyter kernelspec list --json
{
  "kernelspecs": {
    "julia-0.5": {
      "resources_dir": "/Users/KBLaptop/Library/Jupyter/kernels/julia-0.5",
      "spec": {
        "env": {},
        "argv": [
          "/Users/KBLaptop/julia/usr/bin/julia",
          "-i",
          "-F",
          "/Users/KBLaptop/.julia/v0.5/IJulia/src/kernel.jl",
          "{connection_file}"
        ],
        "language": "julia",
        "display_name": "Julia 0.5.0-dev"
      }
    },
    "julia-0.4": {
      "resources_dir": "/Users/KBLaptop/Library/Jupyter/kernels/julia-0.4",
      "spec": {
        "env": {},
        "argv": [
          "/Users/KBLaptop/julia/usr/bin/julia",
          "-i",
          "-F",
          "/Users/KBLaptop/.julia/v0.4/IJulia/src/kernel.jl",
          "{connection_file}"
        ],
        "language": "julia",
        "display_name": "Julia 0.4.3-pre"
      }
    },
    "python3": {
      "resources_dir": "/Users/KBLaptop/Library/Jupyter/kernels/python3",
      "spec": {
        "env": {},
        "argv": [
          "/Users/KBLaptop/miniconda3/bin/python",
          "-m",
          "ipykernel",
          "-f",
          "{connection_file}"
        ],
        "language": "python",
        "display_name": "Python 3"
      }
    }
  }
}

And...
{
  "kernelspecs": {
    "julia-0.4": {
      "spec": {
        "display_name": "Julia 0.4.3-pre",
        "env": {},
        "argv": [
          "/Users/KBLaptop/julia/usr/bin/julia",
          "-i",
          "-F",
          "/Users/KBLaptop/.julia/v0.4/IJulia/src/kernel.jl",
          "{connection_file}"
        ],
        "language": "julia"
      },
      "resources_dir": "/Users/KBLaptop/Library/Jupyter/kernels/julia-0.4"
    },
    "python3": {
      "spec": {
        "display_name": "Python 3",
        "env": {},
        "argv": [
          "/Users/KBLaptop/miniconda3/bin/python",
          "-m",
          "ipykernel",
          "-f",
          "{connection_file}"
        ],
        "language": "python"
      },
      "resources_dir": "/Users/KBLaptop/Library/Jupyter/kernels/python3"
    },
    "julia-0.5": {
      "spec": {
        "display_name": "Julia 0.5.0-dev",
        "env": {},
        "argv": [
          "/Users/KBLaptop/julia/usr/bin/julia",
          "-i",
          "-F",
          "/Users/KBLaptop/.julia/v0.5/IJulia/src/kernel.jl",
          "{connection_file}"
        ],
        "language": "julia"
      },
      "resources_dir": "/Users/KBLaptop/Library/Jupyter/kernels/julia-0.5"
    }
  }
}

Please, could you open the dev console in atom (shift-ctrl-i), run the following code and see whether you get the same error?
> var out = require("child_process").spawnSync('jupyter',['kernelspec','list', '--json']).stdout.toString()
undefined
> JSON.parse(out)

Doesn't seem to.
>  var out = require("child_process").spawnSync('jupyter',['kernelspec','list', '--json']).stdout.toString()
<- undefined

>  JSON.parse(out)
<- Object {kernelspecs: Object}
     kernelspecs: Object
     __proto__: Object

Looks like I can expand kernelspecs and __proto__, not sure how to send along all of the info.

No need to post all the info. The fact that doesn't throws an error is confusing enough.
Your first log indicates that the error is happening somewhere in this lines more specifically in the parse function.
Could you confirm that you can still reproduce this issue despite the above code running fine?

Confirmed. I opened a new python file, typed 2+2 and then Hydrogen: Run and it pops up.

@kescobo If you need a workaround for the time being, I would revert to Hydrogen version 0.6.5:
$ apm install<EMAIL_ADDRESS>Installing<EMAIL_ADDRESS>to /home/user/.atom/packages ✓

That works, though now I need to figure out a way to select the python kernel again :-).

Will fix when merged https://github.com/nteract/hydrogen/pull/177

@kescobo Hydrogen v0.7.1 has just been released. Could you test whether it works in your machine?

#177 already merged

@n-riesco Sorry I missed your comment from a month ago - it just popped up again with your most recent comment.
Just installed 0.7.2 and python kernels works like a charm (including switching between 2 and 3). I've having issues with my julia kernel but I'm pretty sure that's on my end. Will open up another issue if I can't solve it.

@kescobo Thanks!


local variable 'stdout' referenced before assignment

Appears in console when a new window is opened since updating to ver 1.2.0

@alextegelid - sorry about that, 1.2.1 will fix the issue once its picked up by package control.

Thanks, I'll pull it from GitHub right away!

There was a typo, so use 1.2.2.  Thanks for giving me the heads-up.

Will do, thanks!


Need little Help to implement something small

Hey @ all,
i gaved the source a little look. i thought i could implement something easy, because i know a little bit C (last time used in School 20 years ago lol).
There is a nice Distro, called CachyOS. One of the benefits is, thats automatic gets detected if the used Hardware is capable to use a specific, optimized Repo (actually -v3 called). In there are Packages wich are optimized for specific CPU Flags/Feature to improve Speed, loadingtime, etc pp.
If the Hardware support that, this repo gets enabled (but without the notification for the user, or a Info or somewhat similar).
I already "created" something like that, with few Lines of bash/fish. See here:

But instead of figure out how to format it correctly so it looks uniform (pipes, cat, sed, what_ever). i thought  i could create a plugin/module/edit_somewhere_in_the_source_directly (my first try was simply to pipe the output through a script, wich replace the "Packages:" entry with "Packages: 1234 (v3 Repo enabled)". Wich works, but isnt so "beauty" and a quick n dirty solution).
But to be honest, in my head this sounded easier as thought, because i dont know where to start in the source.
Could somebody give me a example, or a hint how to realize this?
Thanks very much!

Take a look here. Note that pacman on Manjaro already gets some info appended, you can implement yours the same way.

So Manjaro forked fastfetch? or what do you mean?
Thanks for the link. I give it a look and try it to understand :D

No, on manjaro the output is either (pacman)[stable] or (pacman)[unstable] depending on the enabled repo. I suppose you want to do something similar, so i figured the code for that might help you.


Keywords with embedded variables are not completed correctly

If I have this keyword:
| Embedded "${var}" keyword |
Then automatic completion show's this:
Embedded "" keyword
It should show this:
Embedded "${var}" keyword

It looks like data is scanned in indexed correctly but completion does not work proporly

Fixed in https://github.com/andriyko/sublime-robot-framework-assistant/commit/9e159b68d59857f7193aa73a93c59cc04167c688


Ruby completions via IRB completion library

Easy enough given IRB is already in there. No type information is present like Python, but this at least brings it up to parity with a basic IRB session.
I also added ghidra as a easy way to reference classes using java-style package names, as org, com, java, javax, and javafx do today in stock JRuby.
Before: Java::GhidraAppPluginCoreConsole::CodeCompletion
After: ghidra.app.plugin.core.console.CodeCompletion

Hold on to this for a moment, I need to add some error handling due to IRB bugs that I helpfully found nearly a year ago: https://github.com/ruby/irb/issues/295

No problem, thanks for putting this together! I'll hold off on a review and CI run until you're ready to go.

Ok, working well with new changes. I'm also working on making the methods top level like python, but am running into some weird issues: https://github.com/byteit101/ruby-dragon/tree/top-level-ruby I'll open a PR when that's fixed up a bit

Thanks again for putting this together! I suspect tab completion will be a huge quality of life improvement for folks (including myself). If you'd like a personal shoutout on Twitter please feel free to send me your handle, or I can just use the @jruby group one?

As a tab completion addict: I totally agree. Note that due to the linked bugs in IRB/JRuby you can't do more that one dot in most cases I think?
I don't have a personal twitter, but I know headius always loves it when he hears of projects using JRuby, so please do tag @jruby


PHPStan 2.0

Fixed failing tests from https://github.com/carlosas/phpat/pull/299

@carlosas  For some reason I'm not able to add reviewers. Could you please review it? Feel free to merge this PR into https://github.com/carlosas/phpat/pull/299

Thank you for the contribution ❤


Remote Desktop Connection closes almost immediately when trying to connect to Debian via WSL

xrdp version
0.9.21
Detailed xrdp version, build options
Paste the result between `~~~`.  Please DO NOT remove `~~~`!

Operating system & version
Debian 12
Installation method
dnf / apt / zypper / pkg / etc
Which backend do you use?
Xvnc, Xfce4, Tigervnc
What desktop environment do you use?
No response
Environment xrdp running on
WSL
What's your client?
No response
Area(s) with issue?
No response
Steps to reproduce
am not quite sure but it's somthing like this:

Start a Windows 10 PC.
Ensure WSL2 is installed and functioning correctly.
Open an XRDP session from the Windows PC to the Debian 12 server.
Attempt to authenticate and establish a remote desktop connection.
Observe intermittent connectivity issues during the session establishment.
Check the XRDP logs (/var/log/xrdp.log and /var/log/xrdp-sesman.log) for any error messages or warnings.
Repeat steps 3-6 multiple times to confirm the intermittent nature of the bug.

✔ Expected Behavior
to login to my debian session and observe the debian GUI on RDP
❌ Actual Behavior
black screen after login in with the linux black cursor and it usualy just quits
Anything else?
thanks in advance hope you help me with this issue

@RenoL911 - thanks for raising this.
Reading the above and #3097, it seems to me that you're not entirely comfortable troubleshooting this setup.
The first thing to do is to eliminate the possibility that you've got two graphical sessions running under the same user on the Debian machine - this isn't supported, but I'd imagine it's an easy state to get into with WSL.
Please create a new user on the Debian machine which will ONLY be used for logging in via xrdp.
Once you've done that, log in over xrdp with your new user and report back what happens.


Detect placeholders in pre-formatted strings

I would love it if Tree-sitter handled placeholders in regular strings:
'My name is %12s' % 'Slim Shady'
'My name is %(name)12s' % {'name': 'Slim Shady'}
'My name is {:>12}'.format('Slim Shady')
'My name is {name:>12}'.format(name='Slim Shady')
'My name is {names[0]:>12}'.format(names=['Slim Shady'])

More examples:
https://pyformat.info
MagicPython output with Atom's One Dark theme:

sounds ok, but not 100% sure this is a good idea, there's a small chance it could be a regular string. then again, #27 is a similar issue

I think this could be possible with an injection (contrary to support this in the grammar itself). So we would need to write a small grammar for the string placeholders, the queries to detect were to inject it should be easy.


When will the API changes actually take place?

This documentation specifies:
"The deprecation process for TeamsInfo.getMembers and TeamsInfo.GetMembersAsync APIs have started."
However, I can't find an actual date for when these changes will take effect. What is this date and/or where can I find it?
Also, on this same page, the doc states:
"By late 2022, bots can't proactively retrieve the userPrincipalName or email properties for members of a chat or team"
What is the date in "late 2022" or where can I find it when this change will take effect?
[Enter feedback here]

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

ID: c780d605-b1b2-716f-5888-503608769b5a
Version Independent ID: 53c724f8-d9a2-4af6-6d75-ddeaef084137
Content: Bot API changes for team and chat members - Teams
Content Source: msteams-platform/resources/team-chat-member-api-changes.md
Service: msteams
GitHub Login: @ojasvichoudhary
Microsoft Alias: ojchoudh

We are closing this issue, please feel free to reach out to us if you have any questions. Thank you.


[Enhancement] @EventMeshSPI eventMeshExtensionType attribute is not clear purpose

Search before asking

[X] I had searched in the issues and found no similar issues.

Enhancement Request
@EventMeshSPI eventMeshExtensionType attribute is only used for the case of the jar package extension spi path, here can be perfected comment, it is best to modify the property name, I am not literally every time I understand what this property is used for, only know the type used to represent the spi
Describe the solution you'd like
add commont or update name of @EventMeshSPI eventMeshExtensionType attribute
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

@mroccyen nice~


The output of removal of taint should be untainted

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
For 1.8 Features: set Milestone to 1.8 and Base Branch to release-1.8
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
NOTE: Please check the “Allow edits from maintainers” box (see image below) to
allow reviewers to fix problems on your patch and speed up the review process.
Please delete this note before submitting the pull request.

This change is

@zacharysarah I signed the CLA, is there anything else I should do?

@IrinaAndronachi Nope, looks like everything is in order. Thanks for signing the CLA!

For the record, the output of the command is "untainted". I understand that executing
kubectl taint nodes --all node-role.kubernetes.io/master-
will remove the taint.


data-plane: enable contract validation rule

What this PR changes/adds
As #1227 fixed date serdes, this PR enable ContractValidationRule.
Why it does that
To verify that the contract is still valid before transferring data.
Further notes

Linked Issue(s)
Closes #1127
Checklist

[x] added appropriate tests?
[x] performed checkstyle check locally?
[x] added/updated copyright headers?
[x] documented public classes/methods?
[x] added/updated relevant documentation?
[x] added relevant details to the changelog? (skip with label no-changelog)
[x] formatted title correctly? (take a look at the CONTRIBUTING and styleguide for details)

Codecov Report

Merging #1239 (a989be4) into main (39aa066) will increase coverage by 0.07%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##               main    #1239      +/-   ##
============================================
+ Coverage     59.19%   59.26%   +0.07%
- Complexity     2830     2835       +5
============================================
  Files           719      719
  Lines         15705    15707       +2
  Branches       1036     1037       +1
============================================
+ Hits           9296     9309      +13
+ Misses         5989     5978      -11
  Partials        420      420

Impacted Files
Coverage Δ

...taplane/sync/api/rules/ContractValidationRule.java
86.66% <100.00%> (+86.66%)
:arrow_up:

Continue to review full report at Codecov.

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


Use unique payloads for partyinfo validation

This maintains security if the sender has multiple keys, as it prevents the result of one validation check being reused for the validation check of another key.

Codecov Report

Merging #1057 into master will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##             master    #1057   +/-   ##
=========================================
  Coverage     99.43%   99.43%
  Complexity     2298     2298
=========================================
  Files           349      349
  Lines          6327     6327
  Branches        365      365
=========================================
  Hits           6291     6291
  Misses            5        5
  Partials         31       31

Flag
Coverage Δ
Complexity Δ

#unittests
99.43% <100.00%> (ø)
2298.00 <2.00> (ø)

Impacted Files
Coverage Δ
Complexity Δ

...java/com/quorum/tessera/p2p/PartyInfoResource.java
100.00% <100.00%> (ø)
15.00 <2.00> (ø)

Continue to review full report at Codecov.

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

Fixes #1058


MINOR: Update docs for producer callbacks to reflect current behaviour

Originally, Callback would return a null metadata value when an error occurred.
This was partially changed by KAFKA-3303, where in some cases Callback would return an 'empty' metadata. In this empty metadata TopicPartition is set correctly but all other fields are set as -1.
The docs were later updated by KAFKA-7412, but it incorrectly states that Callback will always return this 'empty' metadata when an error occurs. However in the case of any exceptions that are a subclass of ApiException, Callback will still return a null value (see here).
This change aims to clarify the docs to accurately reflect the behaviour of producer callbacks.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

cc @junrao as you were involved in earlier PRs / threads on this topic

@junrao I've created a second PR #11482 that updates the behaviour when ApiException is thrown to align with other exceptions / documented behaviour.
Depending on whether you think we should change the current behaviour to align with the docs, or change the docs to align with the current behaviour, I will close one of these two PRs and we can continue the discussion in the relevant PR.

@soceanainn : I agree that it makes sense to change the behavior of ApiException to be more consistent with other places. Since it's a user facing change, we probably need to do a KIP.

I'll close this PR in favor of #11482 and we can discuss the creation of the KIP there


Loader docs return value for source from transform?

I think the most current docs for the loader hooks are here:
https://github.com/nodejs/node/blob/master/doc/api/esm.md#loadurl-context-defaultload
In the section above in the table for formats, it has a column called

Acceptable types For source returned by resolve or load

This leads me to believe that resolve somehow would be capable of returning source but I think it is not? Is this an error in the docs or have I misunderstood something?

It should probably say acceptable values for format; @JakobJingleheimer ?

The format is specified in the first column so I think it the resolve part should just be removed?
Acceptable types For source returned by ~resolve or~ load

It should probably say acceptable values for format; @JakobJingleheimer ?

@GeoffreyBooth no, the 3rd column is indeed types for source. That table is saying when format is foo, source can be bar. I'm not sure how much value the table provides (it existed before though) as in most circumstances, the choice is made for you.

Acceptable types For source returned by ~resolve or ~load

Yes! resolve does not return a source property. Thank you for the catch @jonaskello. PR incoming.

nodejs/node#40234


Fully automated mode documentation

A fully automated mode is also available: insert a DVD or Blu-ray disc into an optical drive and let MakeMKV rips it without any user interaction.

Could this point be clarified in the README? I didn't see any information on automating MakeMKV with Bluray HD or UHD discs.
Thanks!

See the Automatic Disc Ripper section of the readme: https://github.com/jlesage/docker-makemkv#automatic-disc-ripper


Some unit tests failed on MacOS

The following tests failed when running cargo test server:
test_server_ipv6_multicast
test_server_ipv6_unicast
The following test failed when running cargo test client:
test_client_socket_stream_multicast_ipv6

The Failed Tests Identified Two Key Issues with MacOS:

Internet interface selection
Unspecified IP Address usage

I've written a blog post discussing the potential errors associated with unspecified IP addresses on MacOS ([::] and <IP_ADDRESS>).

Thanks for testing this out! Can you try out the fixes in the development branch "testing_no_socket2" and see if this fixes it for you? This fixed the failed tests for me when using MacOS 13.3.1.
I'd still like to be able to use the unspecified address when setting the listening socket to indicate that incoming data may be received from any address. When using the unspecified address as the target socket address, it fails with "No route to host" as described in your blog post. It does appear that other OS will redirect to the loopback address, so I've attempted to find a solution that doesn't rely on this behaviour.
One part I still don't understand is which socket interface to use for MacOS when setting the client outbound target IP. In my testing I found that interface with index 12 works but I don't know why (https://github.com/matt24smith/mproxy-dispatcher/blob/ef22097d8977e67d40aa691d5329c879d694ad1b/client/src/lib.rs#L114)

@Jinnkunn Thanks for your suggestion to use the default_net crate, I've added this when building for macos to determine the correct network interface


PandasTools.LoadSDF -- read performance

Hello!
I think that the PandasTools.LoadSDF code can be optimized to avoid iterative deletion of properties when reading the file (by default embedProps = False). Instead it will be nice to have a method that resets the entire property map.
The changes are rather small, while the speedup in reading large files can be significant (about 25% for a file with only ten thousand compounds with four properties).
I will be glad to hear your opinion on this proposal.

My bad, found serious issues with this solution.

My bad, found serious issues with this solution.


Remove depreceated InSAR golden test functionality

Removes the code related to the old InSAR golden test strategy, now that we have the new one in place.

The PR looks good to me. I approved the PR.


[Feature]: Implement Skeleton Loading Animation

Description
Objective: Enhance user experience by implementing a skeleton loading animation for the "Daily Best Sellers" and "Popular Products" sections on the home page and all category pages. This will replace the current "Loading" text displayed while the API fetches data, providing a more visually appealing and seamless transition for users.
Details

Current Behavior: When data is being fetched from the API, the text "Loading" is displayed, which disrupts the visual experience.
Proposed Solution: Introduce a skeleton loading animation that mimics the structure of the product cards in these sections. The skeleton should visually represent where the product images and details will appear once the data is loaded.
Implementation Steps:

Design and create skeleton loading components using suitable library.
Integrate the skeleton loading components into the existing codebase for the "Daily Best Sellers" and "Popular Products" sections.
Ensure the skeleton loading animation is responsive and adjusts well to different screen sizes.
Test the implementation to verify that the skeleton loading provides a smooth and visually appealing experience during data fetching.
Update documentation and provide instructions for future maintenance and customization of the skeleton loading feature.

Benefits

Improves user perception by reducing the perceived loading time with a more engaging visual transition.
Enhances overall user experience by providing a polished and professional appearance.
Aligns with modern UX practices to maintain user interest and satisfaction.

Screenshots

Are you interested in contributing?

[X] I'd like to work on this issue

Code of Conduct

[X] I have used the search function to check if an issue already exists
[X] I agree to follow this project's Code of Conduct

Which program are you contributing in?
ssoc'24

Hey @harmeetsingh11,
Great idea. Assigning you the issue.


docs: add example for wrapping generic classes

This is a small update to the documentation to demonstrate how to wrap a generic class with a macro (something I had to figure out myself ;-)) . Let me know if this is of interest to the pyo3 community.
I used these discussions as an input:
https://github.com/PyO3/pyo3/discussions/2149#discussioncomment-2119302
https://github.com/PyO3/pyo3/discussions/2660#discussion-4445396

thanks a lot for approving my MR! and thanks for making pyo3!!


Update faculty.js to work with new image sourceUrl values

This issue has been fixed in wp-graphql https://github.com/wp-graphql/wp-graphql/issues/468
Now it will be easier to get the urls for all image sizes. We no longer need the regex to create image urls in faculty.js

For now I reverted back to a previous version of faculty.js that works, but does not use srcset. Ideally we would use sreset, but this will work for now.


v1.4.1 - Error: Cannot find module 'lie/polyfill'

I believe this is a bug in v1.4.1 (nopromises), specifically at line 105.
_dereq_('lie/polyfill');
I suspect this line expects the client to be running CommonJS. On web browsers, this fails and localforage fails to load.
Once line 105 is removed, localforage appears to work.

Maybe we could add a ternary operator to check wether the Promise object is
already available.
Cc: @nolanlawson

--
Thodoris Greasidis
Computer, Networking &
Communications Engineer

Just opened PR #563, please check.

I am still experiencing this issue in IE11 :|

Are you using localforage.js or localforage.nopromises.js ?
IE11 needs the Promise polyfill so please ensure that you are using localforage.js (or the min version).


bind: 9.16.13 -> 9.16.15

Motivation for this change
https://kb.isc.org/docs/cve-2021-25214
https://kb.isc.org/docs/cve-2021-25215
https://kb.isc.org/docs/cve-2021-25216
Fixes: CVE-2021-25214, CVE-2021-25215, CVE-2021-25216
In 20.09 we have 9.14, which is sadly not a supported release, so we have to fish the commit log for the relevant patches.  They are not mentioned in the KB, but there are patches for 9.11.x and 9.16.x mentioned on oss-security.
https://www.openwall.com/lists/oss-security/2021/04/29/1
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

Result of nixpkgs-review pr 121106 at 84b65960 run on aarch64-linux 1

1 package failed to build:

dwm-status

2 packages skipped due to time constraints:

bind
dig (dnsutils)

20 packages built successfully:

autofs5
bashSnippets
blueberry
cinnamon.cinnamon-common
cinnamon.cinnamon-screensaver
cinnamon.cinnamon-session
cinnamon.cjs
cinnamon.nemo
cinnamon.warpinator
cinnamon.xapps
cinnamon.xviewer
host
inxi
monitoring-plugins
python38Packages.xapp
python39Packages.xapp
sssd
twa
xed-editor
xplayer

3 suggestions:

warning: unused-argument
Unused argument: fetchpatch.
Near pkgs/servers/dns/bind/default.nix:1:34:
  |
1 | { config, stdenv, lib, fetchurl, fetchpatch
  |                                  ^

warning: missing-patch-comment
Please add a comment on the line above, explaining the purpose of this patch.
Near pkgs/servers/dns/bind/default.nix:24:5:
   |
24 |     ./remove-mkdir-var.patch
   |     ^

warning: missing-patch-comment
Please add a comment on the line above, explaining the purpose of this patch.
Near pkgs/servers/dns/bind/default.nix:23:5:
   |
23 |     ./dont-keep-configure-flags.patch
   |     ^

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement.


feat(db): remove postgres cleanup timer and use postgres triggers instead

Summary
This is alternative to #10331. @windmgc please check this out. What do you think? If ok, please take over and do the rest of the changes (aka add migrations so that cleanup is in other entities too, similar to what I did for oauth2_tokens here).

This is a clever approach.  Are we fine with the random response time increase that we see for those insertions that perform a garbage collection?

This programs the database in a way that is very hard to control when something goes wrong or needs tweaking.
Is creating such stored procedures and then invoking them from control-plane nodes a better balance? That helps us invoke the procedure on a schedule and connection that can be controlled by the CP and we (developers) can fine-tune that based on the feedback we receive.
Kong is sensitive to database latencies, especially when there is a short burst of write traffic, and such a change could potentially worsen database performance and increase the time it takes for the configuration of Kong to propagate across the cluster in hybrid mode.
I must say that the cleverness is appealing especially since it offloads all the work to the database server!

Is creating such stored procedures and then invoking them from control-plane nodes a better balance? That helps us invoke the procedure on a schedule and connection that can be controlled by the CP and we (developers) can fine-tune that based on the feedback we receive.

I think that if we have a mechanism for that, scheduling the garbage collection from th CP instead of randomly invoking it from insertions is better.  The concern that I have is that when we'd piggyback the GC onto insertions, we'd see the additional cost as latency increases in our proxy path.  I'm sure that we have other non-obvious contributing factors, but I'd generally want to keep clear of adding cost to the proxy path that'd be very difficult to analyze when looking at the latency profile.

Is creating such stored procedures and then invoking them from control-plane nodes a better balance? That helps us invoke the procedure on a schedule and connection that can be controlled by the CP and we (developers) can fine-tune that based on the feedback we receive.

I think that if we have a mechanism for that, scheduling the garbage collection from th CP instead of randomly invoking it from insertions is better.

All this needs to be measured. Perhaps we don't have any problems with the solution I am proposing. Perhaps having cluster of 50 data planes that are scheduled to bombard database is a way worse. Perhaps adding cluster mutex lock there only makes it more complex and complicated (the cluster mutex is still an additional query to database and then you need to deal with possible situations when lock is not released).

The concern that I have is that when we'd piggyback the GC onto insertions, we'd see the additional cost as latency increases in our proxy path.

Data planes and DBless proxy nodes don't insert anything. CP inserts and there we don't have the latency issue that much (on CPs insertions are a low factor). The only problem we have is OAuth2 plugin in TRADITIONAL mode.

I've been thinking about this the whole day, and so far I still have some concerns here:

The backporting problem. I'm okay with the trigger way if we're going to fix it in a new version but it's hard to backport this to an older version when solving FTI problems. Manually creating triggers on the older versions seems not sustainable enough and might cause problems when upgrading to newer versions.
The latency increase, which needs some test(haven't got time to do that yet, will do)

Do you think it is a good idea that we remove the RANDOM call and just DELETE two rows on every INSERT? Since we already have proper indexes

@hanshuebner and @hbagdi, thanks for great feedback from @windmgc I modified this PR so that now on each insert statement the trigger removes maximum of 2 rows. I also removed usage of RANDOM. The penalty of deleting maximum of 2 rows per insert statement should be miniscule.

The penalty of deleting maximum of 2 rows per insert statement should be minuscule.

I have forever been told my DBA to not use triggers or use them minimally and be careful with them. I've never found a good reason when I push for why not.
Provided that the overhead of running on the trigger on every insert is low, we are good. If that is not the case, we may be adding cost. I'm out of depth with my knowledge of databases here.

Inserting new access tokens and authorization codes is not that frequent. It usually means one per user per certain amount of time (e.g. session). If there are say 100-1000 logins per second (which is quite a bit already).

I could be wrong but isn't this change about all tables that have TTLs? At least that was what the original PR (#10331) was about.

CP inserts and there we don't have the latency issue that much

Write traffic via CP is generally bursty in nature and latency differences do matter. I do see your point that the latency matters less.
Anyways, this change looks much better than it was before.
Should this move out from Draft at this point?

I have forever been told my DBA to not use triggers or use them minimally and be careful with them. I've never found a good reason when I push for why not.
It is basically a matter of architectural choice whether you use or don't use triggers in a database.  Using them has benefits (fewer DB interactions with the application, business-level constraints can be enforced on all database clients) and downsides (cost of insertions/updates becomes non-obvious due to the triggered activity, hence making analysis and capacity planning more difficult, triggers are not portable across database systems).

It should be a conscious decision to use or not use triggers in an application.  It seems that we're already using them to maintain the tags table.  If that implementing that functionality using triggers was a concious decision, I see no reason why this cleanup task can't be implemented using triggers as well.

I could be wrong but isn't this change about all tables that have TTLs? At least that was what the original PR (#10331) was about.

Yes, we need to add triggers to all the tables where entity says ttl=true and to cluster_events too which does not have ttl=true but it has column expire_at (the batch_delete_expired_rows function expects ttl column, so for cluster_events I think we just re-create this or rename cluster_events column to ttl). I cannot think of any other entity than oauth2 plugins two entities that are constantly created by external users. Most other entities are admin managed, so those don't have this issue of potentially huge amounts of rows. The cluster events may also be plenty especially if creating oauth2 entities also creates cluster event. The OAuth 2.0 plugin is not supported in DP and DBless so its surface is smaller, but important to those that use it.

One thing worth noting is that I am not sure if Kong cache is currently aware of entity ttl, but this problem is with current cleanup too. Aka when it cleans it will just delete rows on db, but cache of those entities is not invalidated.

Tables covered in this PR:
cluster_events, clustering_data_planes, acme_storage, keyauth_credentials, oauth2_authorization_codes, oauth2_tokens, ratelimiting_metrics, sessions

I labeled this as "do not merge" for now as the migrations tests are failing.

There may have a potential behavior change in the Database trigger solution.
Kong not only collects the TTL schemas from the DAO of bundled plugins, but also from the enabled custom plugins. If a custom plugin is relying on the built-in TTL scheduled task to clean up the expired data of itself, then it won't work like the previous. Although adding a plugin migration to add a trigger(like we're creating), or even creating a timer task to do so could avoid the behavior change, Both options require manual action. This may be something that needs to be considered.

There may have a potential behavior change in the Database trigger solution.
Kong not only collects the TTL schemas from the DAO of bundled plugins, but also from the enabled custom plugins. If a custom plugin is relying on the built-in TTL scheduled task to clean up the expired data of itself, then it won't work like the previous. Although adding a plugin migration to add a trigger(like we're creating), or even creating a timer task to do so could avoid the behavior change, Both options require manual action. This may be something that needs to be considered.

For brainstorming. I was thinking an alternative solution, which is still using the database trigger, and isn't triggered by the INSERT statement, but is triggered by UPDATE statement which is called by the previous timer.
Let's say we have a new table, and a trigger triggered by the UPDATE statement. And also a function delete_expired_rows is called by trigger to clean up the expired data.
create table ttl_task (
    execute_time int,
    ttl_schemas text
);
insert into ttl_task values(0); -- a default row

-- create function delete_expired_rows
CREATE OR REPLACE FUNCTION delete_expired_rows() RETURNS TRIGGER
LANGUAGE plpgsql
AS $$
DECLARE
    v_table text;
BEGIN
    -- TODO "oauth2_tokens,oauth2_authorization_codes" should be fetched from ttl_task.ttl_schemas
    foreach v_table in array STRING_TO_ARRAY('oauth2_tokens,oauth2_authorization_codes', ',') loop
        EXECUTE format('delete from %s WHERE ttl < (CURRENT_TIMESTAMP AT TIME ZONE ''UTC'')' , v_table);
    end loop;
    return NULL;
END;
$$;

The postgres clean up timer can be simplified to the following without any lock or cluster mutex consideration. Because the database layer will take care of the rest.
return timer_every(60, function(premature)
    -- execute SQL
    -- sending a collected_ttl_schemas is for to be used by a trigger
    local collected_ttl_schemas = "oauth2_tokens,oauth2_authorization_codes,...."
    local sql = "update ttl_task set execute_time = floor(EXTRACT(epoch FROM current_timestamp)), ttl_schemas = " .. collected_ttl_schemas .. " where execute_time < floor(EXTRACT(epoch FROM current_timestamp)) - 60"
    execute_sql(sql)
end

Here is the whole sql script, which is very rough.
drop table if exists ttl_task;
create table ttl_task (
    execute_time int,
    ttl_schemas text
);
insert into ttl_task values(0); -- insert a default row

-- create function delete_expired_rows
CREATE OR REPLACE FUNCTION delete_expired_rows() RETURNS TRIGGER
LANGUAGE plpgsql
AS $$
DECLARE
    v_table text;
BEGIN
    -- TODO "oauth2_tokens,oauth2_authorization_codes" should be fetched from ttl_task.ttl_schemas
    foreach v_table in array STRING_TO_ARRAY('oauth2_tokens,oauth2_authorization_codes', ',') loop
        EXECUTE format('delete from %s WHERE ttl < (CURRENT_TIMESTAMP AT TIME ZONE ''UTC'')' , v_table);
    end loop;
    return NULL;
END;
$$;

-- define ttl_task_trigger
DROP TRIGGER IF EXISTS "ttl_task_trigger" ON "ttl_task";
DO $$
BEGIN
CREATE TRIGGER "ttl_task_trigger"
		AFTER UPDATE ON "ttl_task"
		FOR EACH ROW
		WHEN (OLD.execute_time <> NEW.execute_time)
		EXECUTE PROCEDURE delete_expired_rows();
EXCEPTION WHEN UNDEFINED_COLUMN OR UNDEFINED_TABLE THEN
        -- Do nothing, accept existing state
END$$;

delete from oauth2_tokens;
insert into oauth2_tokens(id, ttl) values('00000000-0000-0000-0000-000000000000', '2022-11-14 18:45:17');
insert into oauth2_tokens(id, ttl) values('00000000-0000-0000-0000-000000000001', '2022-11-14 18:45:17');

delete from oauth2_authorization_codes;
insert into oauth2_authorization_codes(id ,ttl) values('00000000-0000-0000-0000-000000000000', '2022-11-14 18:45:17');
insert into oauth2_authorization_codes(id ,ttl) values('00000000-0000-0000-0000-000000000001', '2022-11-14 18:45:17');

update ttl_task set execute_time = floor(EXTRACT(epoch FROM current_timestamp)), ttl_schemas = 'oauth2_tokens,oauth2_authorization_codes,not_exist' where execute_time < floor(EXTRACT(epoch FROM current_timestamp)) - 60;

select * from oauth2_tokens;
select * from oauth2_authorization_codes;

-- insert again
delete from oauth2_tokens;
insert into oauth2_tokens(id, ttl) values('00000000-0000-0000-0000-000000000000', '2022-11-14 18:45:17');
insert into oauth2_tokens(id, ttl) values('00000000-0000-0000-0000-000000000001', '2022-11-14 18:45:17');

-- insert again
delete from oauth2_authorization_codes;
insert into oauth2_authorization_codes(id ,ttl) values('00000000-0000-0000-0000-000000000000', '2022-11-14 18:45:17');
insert into oauth2_authorization_codes(id ,ttl) values('00000000-0000-0000-0000-000000000001', '2022-11-14 18:45:17');

-- run update again, and should not trigger the delete_expired_rows() function
update ttl_task set execute_time = floor(EXTRACT(epoch FROM current_timestamp)), ttl_schemas = 'oauth2_tokens,oauth2_authorization_codes,not_exist' where execute_time < floor(EXTRACT(epoch FROM current_timestamp)) - 60;
select count(*) from oauth2_tokens; -- should be 2
select count(*) from oauth2_authorization_codes; -- should be 2

@hanshuebner @bungle  Could you please review again? I've add the triggers that CE needs and fixed the migration test.

Let's avoid the breaking change for custom plugins, our bar for breaking change is much higher and there are far too many custom plugins in the world and it is hard to know the impact of such a breaking change. And, I also don't see a big enough risk that keeping the old logic around.
Is it possible to check the DB for custom tables and then fire up the timer only if there are custom tables?

@windmgc could you check how possible that is? @hbagdi it is not that easy to detect whether custom table by a custom plugin has added a trigger or should it do timer cleanup. Perhaps we could still have timer (only on custom entities) as it just does almost nothing if there is a trigger.

This is exactly what I meant.

Is it possible to check the DB for custom tables and then fire up the timer only if there are custom tables?

I'd like to keep all of the origin timer running in the background after consideration. It seems a bit hard to tell if the entity is a "custom" one, from Kong's perspective the "oauth2_tokens" is also a custom entity loaded by plugin. And it also seems not reliable to judge by bundled_plugins since the custom entity may not be provided by plugins. I can tell for sure if the entity we're cleaning is a core entity(based on CORE_ENTITES) but running the timer on non-core entities sounds the same as running it on all entities to me.
@bungle @hbagdi If you all agree with keeping the original timer code I'll go this way

Is it possible to check the DB for custom tables and then fire up the timer only if there are custom tables?

I'd like to keep all of the original timer running in the background after consideration. It seems a bit hard to tell if the entity is a "custom" one, from Kong's perspective the "oauth2_tokens" is also a custom entity loaded by plugin. And it also seems not reliable to judge by bundled_plugins since the custom entity may not be provided by plugins. I can tell for sure if the entity we're cleaning is a core entity(based on CORE_ENTITES) but running the timer on non-core entities sounds the same as running it on all entities to me.
And SKIP LOCKED is really a good improvement here, it can prevent us from potentially conflicting when running multiple cleanup logic on one table. With batch query and SKIP LOCKED I think it should be relatively safe to keep both the trigger and the timer.
@bungle @hbagdi If you all agree with keeping the original timer code I'll go this way

Yes, I approve this approach. Now that we don't need it that much for core anymore, perhaps also change that it runs less often. I do not know what would be a good value. Once per 5 mins? Once per hour? But I feel once per minute is too much.

I don't have strong opinions either way.
If making the timer run less frequently can result in a large behavior change then we should publicly document it. Otherwise, this is ok.

I think increasing it to per 5min is enough, and it won't cause a huge behavior change.
One thing to note that is from 3.X we replaced timer library to timer-ng which can also guarantee that, if a timer is created by timer.every, only one will run at the same time. Before 3.X we don't have such a guarantee.

@bungle  Could you please review it again?
I've restored the original timer code and increase the interval to 300s.

@windmgc Please cherry pick this PR to EE.

ping @windmgc

ping @windmgc

As not yet cherry-picked, now covered by CE2EE master merge.

@outsinre notice that this has now been cherrypicked to ee

@kikito noticed. Thanks to @bungle on the debug for CE2EE master merge.


CreateFile() Error: 5 after open powershell

CreateFile() Error: 5

There's not enough information to diagnose your problem. In general, please fill in the issue template as provided.

Windows PowerShell is not maintained in this repository. Please file a ticket with UserVoice or consult with community forums for assistance. 🙂

updated, see:#12859


Child Templates?

I was wandering if there is a way to access child templates. This extension and Blaze only talk about parent templates. Is there a reason for that?
Thanks!

What do you mean by "child template"? What does this mean to you?
Blaze Components do not operate around templates, but around components. You have both componentParent and componentChildren calls to traverse components up and down.

@mitar What I mean is to be able to access from the parent template to it's children templates, the ones that are inside the parent. To be able to search for example which is the last child template, etc.
Thanks for the tip about the components, I'll see if I use those, but do you know a way of doning this in simple blaze?

You could create that in onCreated of children templates, your children templates register themselves with the parent template.

Thanks Mitar. I'll add references of the children to the parent in the
onCreated callback.

Santiago Puente.
2015-05-28 17:57 GMT-03:00 Mitar<EMAIL_ADDRESS>
You could create that in onCreated of children templates, your children
templates register themselves with the parent template.
—
Reply to this email directly or view it on GitHub
https://github.com/aldeed/meteor-template-extension/issues/34#issuecomment-106595728
.

Or maybe in onRendered. Not exactly sure when template.parent() is available. But with this package you get template.parent(), which you can then use to store children into.

I was able to create something that works very well using onCreated to create the array to hold the children, onRendered to register to the parent and onDestroy to clear everything. To find the parent I use a while on the views to finde the first one with the name that starts with "Template."
All this done extending the prototype with registerChild, unregisterChild, getChildAt, etc.. I'll create a package and post it if I can create a more general, robust and tested solution because right now I have to call the init and destroy functions manually for every type of template.
Thanks for the help!

Yea. You just reimplemented part of Blaze Components. ;-)

lol, Oh, I'll check the blaze components when I have more time!

I'll have to learn coffeescript too..

So the next problem is exactly the one you are mentioning: how to make this feature reusable across multiple templates. This is when I gave up on templates and decides to make Blaze Components. :-)

You do not have to know CoffeeScript to use Blaze Components. Only if you would like to contribute to its development.

Thanks man, I think I'll use that library a lot.

Santiago Puente.
2015-05-28 20:25 GMT-03:00 Mitar<EMAIL_ADDRESS>
You do not have to know CoffeeScript to use Blaze Components. Only if you
would like to contribute to its development.
—
Reply to this email directly or view it on GitHub
https://github.com/aldeed/meteor-template-extension/issues/34#issuecomment-106626252
.

Do you know if there are any official plans to support this? Or where I
could post the request?

Santiago Puente.
2015-05-28 20:26 GMT-03:00 Santiago Puente<EMAIL_ADDRESS>
Thanks man, I think I'll use that library a lot.

Santiago Puente.
2015-05-28 20:25 GMT-03:00 Mitar<EMAIL_ADDRESS>
You do not have to know CoffeeScript to use Blaze Components. Only if you
would like to contribute to its development.
—
Reply to this email directly or view it on GitHub
https://github.com/aldeed/meteor-template-extension/issues/34#issuecomment-106626252
.

Support what? Request for what? For feature requests for Blaze, you should open them at Meteor repository.

For some kind of display hierarchy. I'll post this on the repo. Thanks
again!

Santiago Puente.
2015-05-28 20:28 GMT-03:00 Mitar<EMAIL_ADDRESS>
Support what? Request for what? For feature requests for Blaze, you should
open them at Meteor repository.
—
Reply to this email directly or view it on GitHub
https://github.com/aldeed/meteor-template-extension/issues/34#issuecomment-106627008
.


subctl gather needs to be able to retrieve secrets to access the broker

Once we start deploying Submariner using only secrets to store access tokens, subctl gather won’t be able to directly use the information in the Submariner CR to access the broker. It will either have to retrieve the appropriate secret itself, or check to see whether one of the contexts it has access to corresponds to the broker.

This blocks https://github.com/submariner-io/subctl/issues/631 and https://github.com/submariner-io/submariner-operator/issues/1869.


irmin-mirage-graphql: avoid pin-depends now that git 3.4.0 is in opam-repository

it would be nice to get a release of irmin (from master -- so that a released irmin is compatible with the most recent git) -- thanks a lot! :)

Thanks @CraigFe 👍🏾


The directory shows large amounts of no contents on desktop, yet pages items

My screen can fit many more apps and yet the app splits them into various pages with few items.
Lazy loading into one "infinite" list is probably a better UI paradigm

@kenchris great feedback and idea, thank you!

We want to implement a Material Design UI, we will change it then.

I have increased the number of PWAs per page for now, we will change it later to an infinite scroll.


Is it possible to upload vsix files to GitHub release?

Thanks for this language server!
Can I ask you to upload a vsix file to GitHub release when I version up?
e.g. vscode-eslint: https://github.com/microsoft/vscode-eslint/releases/tag/release%2F2.1.4-next.1
I mainly use Vim and use lua-language-server built, but would like to use the pre-built version if possible.
The vsix files for VSCode that come with bin/lua-language-server and server directories are very useful.

I'll try to do this, thanks for your suggest!

If you can, please upload the current and latest version of vsix to the GitHub release first.

I use the LSP client plugins vim-lsp and coc.nvim in vim.
Thanks to uploading to the GitHub release, installation and use of Language Server is now easier.