How to implement on SSR

Hey guys, I'm trying to use this (for vue2 using vue-touch@next) in a project based on Isomorphic Vue and I'm getting an error about window not being defined, so my guess is I'm trying to load this before the client side has been rendered/created. Any tips on how I should use this?
This was my previous code:
// main.js
import Vue from 'vue';
import VueRouter from 'vue-router';
import VueTouch from 'vue-touch';
import { configRouter } from './route-config';
require('es6-promise').polyfill()

Vue.use(VueRouter);
Vue.use(VueTouch);

const router = new VueRouter({
  history: true,
  saveScrollPosition: true,
});

configRouter(router);

const App = Vue.extend(require('./App.vue'));

router.start(App, '#app');

window.router = router;

New main.js file from isomorphic project
// main.js
import { app, store } from './app.js'

// get the initialstate from server-rendering.
store.replaceState(window.__INITIAL_STATE__)

app.$mount('#app')

This is where I tried to use VueTouch without success, getting the error window is not defined
// app.js
import Vue from 'vue'
import VueTouch from 'vue-touch'
import {sync} from 'vuex-router-sync'
import App from './App.vue'
import router from './router/index.js'
import store from './vuex/store.js'

sync(store, router)

const app = new Vue({
  router,
  store,
  ...App
})

Vue.use(VueTouch)
export {app, router, store}

I know this is not related to vue touch but to my project config, so I thought this is good place to ask as any, thanks

Well, your problem is not vue.touch, it's this line:

store.replaceState(window.INITIAL_STATE)

Which should not be in the isomorphic main.js - you need a separate client-entry.js and server-entry.js from which you can build seperate client-side and server-side bundles. and the above code belongs in the client-entry.js
Look at vue-hackernew-2.0 example:
https://github.com/vuejs/vue-hackernews-2.0/blob/master/src/client-entry.js
https://github.com/vuejs/vue-hackernews-2.0/blob/master/src/server-entry.js
Please ask for further support on forum.vuejs.org, not here.


Adding Spotify uri

I started to use this awesome plugin to my personal projects, I find incredibly funny and curious to know which music I was listening while I was developing my classes!
However, I think could be something useful (at least for me) to add the uri of the soundtrack to the comment. We have 2 variables (title and author), could be possible to add the uri link?
{title} - {author} - Play song: {uri} => Welcome to the jungle - Guns n' Roses - Play song: spotify:track:0bVtevEgtDIeRjCJbK3Lmv
Would be incredible if we even can add the functionality to put the URI as a link to spotify. I think there is somewhere in the Spotify API that allows the app to open spotify.
So, in summary, would be add the URI, so we can listening to that song just clicking on the comment on the class. What do you think?
I love the idea of have multiple devs working on my projects and listening the same songs that I listened while I originally develop the classes

Spotify exposes the URL via AppleScript so it's possible to obtain it and add it to the mix. However, I'd argue to add the URL only as additional variable and leaving the default as is to retain simplicity. The config itself adds already some complexity.
We have #2 requesting the possibility to play tracks. Maybe it's worth to also add a parser/link handler to open Spotify with the URL if we discover one. In a future version, we could generate a playlist 😆 from a commit by inspecting which files/comments were introduced by a commit.


Terragrunt source results in error

Is there an existing issue for this?

[X] I have searched the existing issues

Package ecosystem
Terraform
Package manager version
No response
Language version
No response
Manifest location and content before the Dependabot update
No response
dependabot.yml content
No response
Updated dependency
No response
What you expected to see, versus what you actually saw
What I expected: The terragrunt source to be evaluated and if unable to, an error message would be logged and dependabot would continue processing the remainder of the reposititory.
What I saw: The path was incorrectly thought to be a registry source and found invalid.  Dependabot threw an error and stopped processing the remainder of the repository.
/home/dependabot/dependabot-script/vendor/ruby/2.7.0/gems/dependabot-terraform-0.211.0/lib/dependabot/terraform/file_parser.rb:213:in `registry_source_details_from': Invalid registry source specified: '${path_relative_from_include()}/..//.ci/${path_relative_to_include()}' (Dependabot::DependencyFileNotEvaluatable)
--
from /home/dependabot/dependabot-script/vendor/ruby/2.7.0/gems/dependabot-terraform-0.211.0/lib/dependabot/terraform/file_parser.rb:180:in `source_from'
from /home/dependabot/dependabot-script/vendor/ruby/2.7.0/gems/dependabot-terraform-0.211.0/lib/dependabot/terraform/file_parser.rb:145:in `build_terragrunt_dependency'
from /home/dependabot/dependabot-script/vendor/ruby/2.7.0/gems/dependabot-terraform-0.211.0/lib/dependabot/terraform/file_parser.rb:71:in `block (2 levels) in parse_terragrunt_files'
from /home/dependabot/dependabot-script/vendor/ruby/2.7.0/gems/dependabot-terraform-0.211.0/lib/dependabot/terraform/file_parser.rb:68:in `each'
from /home/dependabot/dependabot-script/vendor/ruby/2.7.0/gems/dependabot-terraform-0.211.0/lib/dependabot/terraform/file_parser.rb:68:in `block in parse_terragrunt_files'
from /home/dependabot/dependabot-script/vendor/ruby/2.7.0/gems/dependabot-terraform-0.211.0/lib/dependabot/terraform/file_parser.rb:66:in `each'
from /home/dependabot/dependabot-script/vendor/ruby/2.7.0/gems/dependabot-terraform-0.211.0/lib/dependabot/terraform/file_parser.rb:66:in `parse_terragrunt_files'
from /home/dependabot/dependabot-script/vendor/ruby/2.7.0/gems/dependabot-terraform-0.211.0/lib/dependabot/terraform/file_parser.rb:34:in `parse'
from /home/dependabot/dependabot-script/updater.rb:81:in `update'

Native package manager behavior
Terragrunt will evaluate the path from the method and use it as a local path.
Images of the diff or a link to the PR, issue, or logs
No response
Smallest manifest that reproduces the issue
terraform {
 source          = "${path_relative_from_include()}/..//.ci/${path_relative_to_include()}"
 }

👋 I'm not a terraform expert, but as best I understand it, Terragrunt is a wrapper around Terraform... so will your manifest above not be supported under native Terraform? IE, does it require Terragrunt in order to read that syntax?
I agree that it would be better to throw a nicer error, provided that we definitively knew under native Terraform that this wasn't a registry source... I doubt we'll get to this anytime soon, but as you know a PR is always welcome. 😄

Yes, it is a wrapper and is a terragrunt function, so native terraform wouldn't evaluate it, but if it's an unknown source then dependabot should report error and continue processing IMHO.  Plus, dependabot does support terragrunt at least partially.
In this case it is also incorrectly identifying it as a registry source, which is a bug as well.  I think this is a two part fix, identify it as an unknown source and report "error" and continue.  As this is valid terragrunt and not truly an error, it is just that dependabot cannot evaluate it.
We do plan on working a PR for this as our schedule allows.


ASP.NET Core web application (targeting .NET 4.6.1) not able to reference a class library (targeting  .NET 4.6.1)

I'm using Visual Studio 2015 Update 2 with Microsoft .NET Core Tools (Preview 1) and ASP.NET Core RC2.  I encountered the following issue.
ASP.NET Core web application (targeting .NET 4.6.1) is not able to reference a class library (targeting  .NET 4.6.1).  These are the steps to reproduce the issue:

Create a website project "WebApplication1" using the template "ASP.NET Core Web Appliction (.NET framework)" targeting .NET 4.6.1.
Create a class library project (targeting .NET 4.6.1) named "ClassLibrary1". Build it.
In "WebApplication1", add a reference to the "ClassLibrary1" project.
Add this line in "/Views/_ViewImports.cshtml":
@using ClassLibrary1
Launch the "webApplication1" and you will encounter the following error:

An error occurred during the compilation of a resource required to process this request. Please review the following specific error details and modify your source code appropriately.
/Views/_ViewImports.cshtml
The type or namespace name 'ClassLibrary1' could not be found (are you missing a using directive or an assembly reference?)
@using ClassLibrary1
IntelliSense could detect the existence of the ClassLibrary1 and allowed me to navigate to classes in the library.
If I create an ASP.NET core website targeting .NET core referencing a class library targeting .NET core, I won't have such issue.
I'm wondering if anyone encounters the same issue.

@stevesiu seems like you're running into https://github.com/aspnet/Razor/issues/755. https://github.com/aspnet/Razor/issues/755#issuecomment-220732700 has a possible workaround for this issue in RC2.

@pranavkm  Thank you very much for your prompt reply and pointing me to the workaround.  The issue was resolved after the following AddRazorOptions line was added to the ConfigureServices method in the Startup.cs file.
services.AddMvc()
                .AddRazorOptions(options =>
                {
                    var previous = options.CompilationCallback;
                    options.CompilationCallback = context =>
                    {
                        previous?.Invoke(context);

                        context.Compilation = context.Compilation.AddReferences(Microsoft.CodeAnalysis.MetadataReference.CreateFromFile(typeof(ClassLibrary1.Class1).Assembly.Location));
                    };
                });


High Latency (1800 msec) for message publish, create subscription, topic list, subscription list, create topic

Hello,
I have initiated a pubsub client with the @google-cloud/pubsub  (version: 0.23.0)  npm package in my node app. Problem is, any action I make, ex: (List all topics, List all subscriptions, create topic etc) it takes around 2 secs (1800 ms ) to complete.
Here, is a sample of my snippet.
Please let me know what seems to be the problem
// Initialize App
const express = require('express')
const app = express()

// Initialize PubSub
const { PubSub }  = require("@google-cloud/pubsub");
const pubsubOpts = {
	projectId : process.env.PROJECT_ID,
	keyFilename : path.join(__dirname, "keys/pubsubKey.json"),
	autoRetry : false,
	maxRetries : 5
}
const pubsub = new PubSub(pubsubOpts);

// List all Topics endpoint
app.get('/topics/list', async (req, res) => {
	try {
		const [topics] = await pubsub.getTopics();
		console.log('\nTopics :');
		topics.forEach(topic => console.log("Topic " , topic.name));
	} catch(err) {
		console.error("List Topic Err: ", err)
	}
	return res.status(200).json({ msg : "Check Console" })
})

// List All Subscriptions Endpoint
app.get("/subs/list", async (req, res) => {
	try {
		const [subscriptions] = await pubsub.getSubscriptions();
		console.log('\nSubscriptions:');
		subscriptions.forEach(subscription => console.log(subscription.name));
	} catch(err){
		console.error("\nList Subs Err: ", err)
	}
	return res.status(200).json({ msg : "Check Console"})
})

// Create Topic Endpoint
app.post('/topics/create', async (req, res) => {
	var topicName = req.body.topic
	try {
		await pubsub.createTopic(topicName);
		console.log("Topic ", topicName, " created.");
	} catch(err) {
		console.error("Topic Create Err : ", err)
	}
	return res.status(200).json({ msg : "Check Console"})
})

// Listen on port
app.listen(process.env.APP_PORT, () => console.log("Server Listening on ", process.env.APP_PORT))

Here are some screenshots from my Insomnia client. Any Function I try, it takes a massive amount of time to complete!
List All Topics

List All Subscriptions

Create a Topic

I have also tried by removing autoRetry : false, maxRetries : 5 from the pubsubOpts object but no luck. Please provide me a fix for this. Thanks.

Hi @burningraven06 and thanks for the detailed writeup! Would you be able to provide us with some additional details about your environment?

What OS are you running your application in?
What version of Node are you using?
Are you running your application in GCF, GKE, etc.?

Hi @callmehiphop, @yoshi-automation
Sure I'd be glad to provide any info necessary.

I am using Ubuntu 18.04 (OS)
I am using Node v10.15.1
I am running the app on my local machine

@burningraven06 I've been messing around with your reproduction code and I was hoping you could spare a few more details with me.

How many Topics are returned via pubsub.getTopics()
How many Subscriptions are returned via pubsub.getSubscriptions()

My initial testing actually showed very similar latency, but it turned out I had quite a few lingering subscriptions and topics from various testing I've done previously. After I deleted the topics/subs associated with my project I saw significantly less latency

/topics/create: 200ms~
/topics/list: 100ms~
/subs/list: 100ms~

This leads me to wonder how many pages of subscriptions and/or topics you might have. Both getTopics and getSubscriptions will make 1 request per page of resources you have, so in my case the latency came from requesting several pages worth of resources.
Of course this doesn't explain why it takes so long for your app to create a topic, I'm wondering if there could be any other outside factors contributing to the latency you're seeing.

HI, @callmehiphop
Thanks for checking out my code.
I have 2 subscriptions.
I have 3 topics.
It's still taking around 2 seconds (1900 msec) for LIST (list topics,subs) operation.
For Creating a topic, it took nearly 7 seconds.
I'm not sure what else could be wrong, I ran it from another machine...

Out of curiosity have you tried using Insomnia to hit the PubSub REST API directly? I'm curious what kind of latency you see from that.

Haven't heard anything here in a while so I'm going to close this one out. If anyone experiences a similar issue or can provide new info, let us know! Thanks


Added Google Trends Integration

Description:
This PR introduces the Google Trends Tool from SerpAPI, allowing users to use the integrate a tool for Google Trends API with Langchain to retrieve and analyze search interest data. The tool supports viewing trends for specific search queries and exploring related queries to gain deeper insights.
 Thank you for your time!

Hi @jacoblee93 thanks for reviewing our PR. I have renamed GoogleTrendsAPI to SERPGoogleTrendsTool everywhere and changed to .invoke as suggested, as well as fixing some lint warnings I missed before.


Revise console view for task based API

In the console, might it be nice to differentiate between the requests being made to start tasks versus the requests being made to get data? (both in terms of the count and the way they are displayed) It would make it much easier to see how many tasks have been started, versus just showing the total number of API requests, which lumps apples and oranges together.

Yes agreed @samaybar - definitely a good addition. I will get it added.

Closed via f7b92dd07b0131037e90c1fbf70317ac87919547


[Feature Request] OpenTelemetry HTTP API support

Describe the solution you'd like
Currently we only support OTLP over gRPC, but users like https://github.com/temporalio/sdk-python/issues/647 use systems that (surprisingly) don't support OTLP gRPC.

I'm interested in this as well. We're trying to publish SDK metrics to Datadog using Otel. We have an OTLP endpoint set up but for reasons unknown (we've been working with Temporal and Datadog support for some time to figure this out with no success), the integration is not working, so we would like to use HTTP to publish SDK metrics instead. thanks.

I just discovered (was reminded) that Temporal only uses gRPC for metrics. We recently switched over to HTTP collectors to start collecting data from browsers. We wanted to avoid maintaining two collectors/pathways to debug, so opted to update all internal services to use HTTP. It's taken me two weeks to realize we missed something...Temporal. 🤦🏾
It would be great if Temporal supported both HTTP and gRPC so we can simplify our configuration and have more flexibility around how we deploy collectors (e.g., sidecars vs gateways).

That's not an accurate statement to my knowledge. Tracing also works with gRPC for at least some languages. Source: I am the Haskell ecosystem OTel maintainer.

That's not an accurate statement to my knowledge. Tracing also works with gRPC for at least some languages. Source: I am the Haskell ecosystem OTel maintainer.

@iand675 who are you responding to? No one is denying that tracing doesn’t work via gRPC. We are requesting additional support for HTTP.


Rudimentary fluid.polynomialregressor object

Simple N-to-N polynomial regressor, N parallel monovariate polynomial regressors.

DataClient-inherited member functions all work, including print, read, write etc.
same interface as fluid.MLPRegressor, with fit, predictpoint, predict etc. iface
regressors parameter sets input and output dataset size, namely the number of parallel regressors
degree parameter sets the degree of the polynomial regression, currently all regressors are set to the same degree at once

@weefuzzy Potential for discussion on and rethinking of the implemented regression algorithm e.g. Gaussian regression may be more appropriate instead of simple polynomial regression, this is just a proof of concept and initial posit for a deterministic alternative to the artificial neural network objects.
tested in max against lewardo/flucoma-max@02d3b22
current issues:

when reading from json, the parameters update in the algorithm but not in the client so you have to set the parameters (degree, number of regressors) correctly before reading for it to be recognised by the client

patch used to test new object

----------begin_max5_patcher----------
1806.3oc2assaaiCD84Tf9OPXzBjtqq.ueI+JKVTHayjnt1RBRxsIaw1u8kj
RJwwlVlpkVtMEAwUzzdl4vCOb3Plu812b0rEEOnqmAtA7Wfqt5alVtx0lskq
5a3pYaReX45zZWGmsrXyFcdyr4cuYi9gF2abM6CIfk2mlemFrJsIsV2.pzqS
axJxquOq7oOw5rb8xhs4tOFtu0xJcs46008O4uK4a2TrsYstw4Iv9lyV4rew
hO+QJ9IqTl1r79r769TkdYSaHREpDnfBUHk.pvPFmLGfj3DNR.wPEmxwXpRZ
ZjASfyADZBD726X9r7dqibM9eu8M1WMuLOB.nv.fU5zUfaqJ1.9bcQ9rQD5n
gBckhjvPRFFyfPkxDzHSTZhOIhZ9+BLDgIXE5oPGCmxPmNGbsxD82Y3Ll3rb
aCXSZYoIFpmEWBBbHTRJkGhRhVPBwULjv7CTY.IkLw1Fky3JAVJYnoFxtlXv
quVk0nAMEikrPTCRVvXOjEDJgRPRhPg3DAECEWHxB1PVjlf+1rFmPyXhawPw
s.ScipLLU.YRIWR8O7KQIRK.QgRlArvzy0neZSS01riDfn9laaq4wRcabLa1
yNRYZU5Fcit5S57zEq0u.Yre8N6TouyL6ptn54oa6hZrwKsvUIT6+3JrQlQx
D3mYK3ojsXblq4F1x0U5ObmNWWk17z5S0ig5PGBDvbbBFgMKgvfTESfTJG0A
Z0JnsPAVIEleCQheyYKqrrEsOlBlLZlBFR7nuRkmMlxFCQO8N8gLEmX5OC5s
KaAMdAVeqFSnm.GvwGGrofDIX.O75LLYnv.4rAC45uZ7zCQA8CkUf2cKB7Gc
+FAgwBUFjbPwrDAyFslWwbqvAkRjTAm2tJ74ZhwoPhHE8nAyQGIPsQOhaCTF
d50AJqx1Ygjexg5AS3fK3IXdHBhD7jOAnAr.r3Hv.9nvvBy9+lMu6U+PxfYS
H4POZBX0O.j7iSMVrso4n4SiFN1CbwzcAD5nADeIkhaWpf96OdLn.gDJt33w
wlxb65sYqR5Rt76.yNVWM5IP1IOGYhCb7ZILlmjqfxKgnpdU1xFPV9PvxnWK
QM5oNdkWkrIWdskqTVr9w7hMYoqeZKXeGrPmlWGQhCYzym7yaNIJ8K9hwngS
JmJBjsbFWLdR1bhbvDvb4cQX79BfN0QZuRQLkIDidF.Ax8ssT0ziG1xbYTMM
gZjPC13kC7MKfglbMyZmZvs.cdS0ie78Y2.d+slehEKYPcRBRztwDFMwHORP
JybDC9PHLaBphS.FjnCF1IIIkoK+GW0rtArrXc8M3QiE1ulrh7zpGOBpPCAU
HXWo8P3omT3vg6pJ1VF+XmEDiP5TI47oe0w0Eoq.OGEf2gmCh5Jl7fF7aWr.
cApRyYVQ.N3VQ3jNEgNt+qVM.AJ.X30oDf.FBC30qB.kDxP+kS.Xusbe7rj9
Q13DBFh7GE5xJDAgSdoY2K5yxiXvqBXfuKzUjKVQo6JO+eBhU4oGbqBjtpS6
+RibFI.SaE3FbUeL1MlKdp7ZSbQ1h7wQL7oQzmh2Y+zHNVzt8eyLdA3XG8DI
rBwad0tjfeQt.FrQP237IO+9802a6l6Fes+0LyYL6arGpTWrsZYePz4e.7y1
akttIK2cKf1sSlgQvNd0lrUkElPtt+34UIr1qsi8hcfITHmq3D6kRPhL6my2
6872VQ0Jc0IxfK73YOW8HAjM0SabGAKZu+Fm1hjAQPi3lQj+fClQgOrv.Je2
hpv6IlB8ciaDGZcO8LJ3ElbtvKLEGbrgOKwVDnBg5uSbjYuxE+rglxVZ2Cnt
ROm9nv6sdJ3dd4I4AwwsENEfFISP4oXg1hqGROiy7WUDXBboGl.yy3qh6oho
inmuJYWnHLDHEveE0YPwPmg8KoDpLjHSMblVLahVDkKeYAwkZk6IOYSglJW1
tO9P8YBVLnSCifSKBhBQ63PwvfvPLXuaECCFzvBoc0kHXOdP1KZgGkLhYJwX
EsfvSLLdFLn7D22sBQ.26pXbIKQvOcOiWrgNIYYXcNojDXrEJJDmXiFz3FKd
Dkf1MaDsGJXkk3r44Qra83Hkg3iYIsXXvflqinwyfAQR6wgXXvv1rCavY78I
FfkjcySv8Xb7RXPbMwvIyzkyUmWt6SwwICQ6Tbp7s59CiwcOD4vCd.K1M8Q2
SmozGCp3hhfpsH2E.j9xIZe7R5z6KT52qwHW8coDVKTae7LkzaXdcvkws8.2
epxsdbZ5TQ2OgvwNzcImIYDNTvYT2eRbDH7TuGVndgdi3BODgHAQrHhW301G
8303IyqgigZ0o7bLlEy+wbjVV9EcUcmgac3YaR+bg6CIm29bVd6yr1mqzeIq
+iz0TZ0x6yZzKa1V4hyYOv6tDVy1TXbg7sY8RIVHyZZ2AIkmtQWWl1BNtCb5
suwzg+G.nuC+O
-----------end_max5_patcher-----------

I've implemented some of the changes you mentioned, and am working on various others as of writing
Changes I've implemented:

the regressors parameter is no longer, it as been axed in favour of automatic setting, when saving or fitting the object
the client parameters now update to reflect the algorithm's state on load and read messages

I will look into a b-spline regressor to implement as well as this polynomial regressor, as it seems to be more appropriate and have less statistical issues when dealing with noisy data, but I'm also looking into the ridge regression as you suggested as it also seems to be an interesting path to follow

After a discussion with @tremblap we conjured up a potential UI for 1-N rather than as well as N-N regressors - a simple repeating of the 1 input N times, which could be interesting for the user if they should want to map the same domain to many ranges, let me know what you think of this and I could add it in

I've implemented some of the changes you mentioned, and am working on various others as of writing
Changes I've implemented:

Many thanks. Those changes would seem to bring the object up to readiness, save for all the documentation, testing, help files etc etc etc. If you wanted to be ultra virtuous (and postpone some of the foregoing), you could knock up some C++ tests for this algorithm and add them to the flucoma-core test suite (which, IIRC, would be the first algo to receive such hallowed treatment).
FWIW, adding regularisation for ridge regression should be a very simple change (addition of a single scalar parameter, and an extra term in the linear algebra), at least in the linear case. Anyway, it can be left till later.

After a discussion with @tremblap we conjured up a potential UI for 1-N rather than as well as N-N regressors - a simple repeating of the 1 input N times, which could be interesting for the user if they should want to map the same domain to many ranges, let me know what you think of this and I could add it in

Sounds like Surprising Behaviour to me. Would rather a more explicit workflow with less magic (i.e. user duplicates cols of dataset n times if that's what they want)

I've implemented Tikhonov normalisation into the regressor, currently the Tikhonov matrix can only be $\Gamma$ = $\alpha$ $I$ making the linear factor $\alpha^2$ $I$ (as in ridge normalisation), it is however now very easy to change and/or add different filter matricies like Fourier filters etc.

It might be relevant to have help from / pass over some of the helpfile work to @MattS6464 given that he is very knowledgeable now in that area...

That would be very helpful if @MattS6464 wanted to, I know his helpfile skills leave mine in the dust and he would actually put the help in helpfile as opposed to myself
If it helps, the patch I've been using to test has changed slightly since the original pr so I've pasted it below
No pressure to make one, it's really only if you want to but it would be very appreciated (:

----------begin_max5_patcher----------
1887.3oc2aktaaiCD92o.8cfvnKP5ttZ48QdU1tnP1lIQsVGPVtMYK19rujT
RI9PVlJkRtaBBhAEoLm4iy7MCGx7829lqlsH+A8lYfa.+E3pq9t4IW4dl8IW
09fqlkF+vx0wabCbVbUU41jYya5y1z87pjubedV9Wepmrso4aqVqqbuGp8wE
wkwo5Jc4mzYwKVqscBa6r9EpdrPWKTylA9619RV4lm7Ee9CzYO+sUs79jr69
TodYU86nTjHFRxvXFDpTHIFMGfgjHIhJQbECIL+BUyAHFLBZ5CGAedZLhcR1
SRs6g+6aei8SyGy8FlLeMKzkm.LvuPvXNX1h3r61ATLxZR51z8PXibz9LRGf
GB2G5gwbGlHbPyHBPKySS0YUOIKU5GbhvrqYuOBr7didpAqhqh2nq.k50wUI
4YatOo3o2XcRldY91rp8fz8QZXWVO8B.Ti4CTPgJjxXjfgLNwf.bpEHZLXHz
IEODF7nTGuBbaYdJ3yaxylM.kEMXeEjQ+r9JXj.CQXBVgd1WANkpNcN3ZkQ6
uyXBXzyhsUfz3hBiNrYHP.rOHPJkGCABZGrEJYj8YTNiqDXojglZ73ZhAL9V
YRkFTkOTKAhpWKAiS9wVBHTDkfjDgBwIBJFJtPVBXikfzn72lT4HEFhdK5Su
EXpaUkgoBHSJ4RZ2K+RTjzBPTnjY.KLcxW8MS30bCFbco982oyzkwUOwPND+
ARugOwbbDFgUbJCRULARob.hk9SQin1evJov7WHRLRXPpdyl36zGiANi+ykh
gmYQPPC2gnKpQB8LAIwgGGrwCBDLf6mWfI8EFHiFLjo+lQROFEzOTTBd2sHv
u27WDDFJToWiCJDEAkjm+AQspNKRXxTv3YPoDIUv40TniUJTmz5nnLYGBjeR
fnW5StfGg49jrMAO4lGUfEfEmKE7ifAWF1Gmo8tPBq2DJ3vN7XvpW.j7xMMV
rsp5jYG7B2KVO.Bcv.RWgXw0Doz++iG8tCCITbwwiS4xb65sIqhZRp3GfhR8
pA6.YcdNAt.GNWBi0Qp3P4kfTUuJYYEHIqOXYnzqH0fcc5jdUxlb50Zakh70
OlkmlDutTeWoA7xK+AXgNNaS.MbHC1epa6lyhR+hGLF0eJqTgmVKiXv3II0c
Yev.xUAKBi2VqloVSaYJBIMgXvd.DHuCO.pZ5wC6l1MrlFUMPnAa3zAc4EvP
SNm4FGavs.yF7Ke7C+VxMfe615eCkgRuTkDjHRvrrizHCCIAoLtIFHhPXVai
y4qPCNdX8ShJhW9EWgLtArLe8laFLTX+VRxyhKe7DfB0GPgfcE1BgnStYgCF
tqLeaQ30clWFDRmRy4Se7w04wq.OqEf2gmCBZLStWK90gKPWfpXL9bBvd2OB
mzvITa9+pkEPf7.EdcRBHf9X.75kCfR7Yo+xQAbv1tOclRujMOgf9P.RgtLC
QvQ7Lw8S6SxBnxq7XguQ0UjIWyOn.1+AnLNaUd50l0L3G+na038f+z9ALJPt
B8tQBBSEQQ7m+QZKgsDGwMYLigJNkiwTkz.SDxqjhWx6+5P3LMDOUItItdbs
FHgpX98tuYHa+Eel838pO+BFdx8M19OIlvvfScfND+Jfu4SaXjtIF8XkGAod
cQXNLlP8vb2QkCufUtIy1wAnxl7skKaUhlpb.1Y9Vo2Tkj4tGL6LH09CJMYU
QtQialTLKxFYS4hrIHlM80z542Hubkt7LKggUjsAj7UlIXQuBML.BsMwvyK0
1bHriJDSHzmIrUrBwD50xhUAQAY93dMeAS8X9LcjdM5jlzffGU0HJtqKBhei
LHZFkL.NfPLe+7HoIYERW.jiA8Dfm6NjD.wmf94keks33Gc9sxNN+VQm2dNu
GoUs805BNJVWdYbYK8rkVXPNNpNJ2p83I7YjAQ0vp.XIvkcXIv5X8Uw6nlyC
XjuJstvdE0ACCF4E1q3.GJVGZOau4ydA6bIKRvO+HCmtgNquZ+YCJkDO0MeQ
gvnadE0oc0MDSH1mILfyGx67uviTh4CPDHiTZ1X+1a.deC8mDA7zJB3SmfCh
FoNZexTR8+g.7H1QWLPaei05p+ZDYnZDp9R+Jca.y0bjrLPAHXcmLVW9D3Q7
gri3PLgdEDDQC2D5E6cKNDhIzuzVY8ZtzVWArjraYFbMCiTh8dO9mN4ZLotV
HvZxEdsqnq4Hwm3mX6VyOuXibW2JJFWK11liECRH13G6WxR.TSdedKo9KpVS
s+ZL22sUXDRexNUbt59QaC3XOFR3QMvhcKioq0X4EreB.mPc5Wa3JqOf0m0x
uX9PczAqX66RpAGlTX2p.F4pDNEA6H0FaeikOsWpfWKB0VQclliquNz.xT4U
bl.U63UH4LIivgBNixDXaf.345CKT6EeSbgWuPDuL4Hh8jZayQZKA9I0vgXm
0PPcJKKZ2GUTbQwW0kaZl3ZAdVZ7mycujbdc6jr51r51k5ulz9JMOJtb48IU
5kUaKc54rG3MW+sYo4FQHaaRKIiExrSs6v3xhS0aJhqAG2g1812XFv+AFlUu
S
-----------end_max5_patcher-----------

help and examples are definitely on @MattS6464 todo (with yours truly) indeed.

@weefuzzy I've been reading into spline regression and wanted to know your thoughts on the interface

would the polynomialregressor object be suitable as an interface for the algorithm, or would it be preferable to implement the spline stuff in another object, programatically they are incredibly similar, the spline regression is literally a different design matrix and that's about it
would natural splines be something I should look into, they are very similar except there are the additional edge case constraints to stop overfitting there
Let me know your thoughts for the UI, I'd be glad to implement either a new object or add the algo to the existing object, although in the latter case it might need a rename

My inkling is that knots could end up providing some complex interface decisions (like making it easy to have equidistant knots, vs say using k quantiles w.r.t the independent variable). As such, I'd opt for separate user facing objects with the option to do some elegant code reuse behind the scenes, if it seems to make sense. As such, we can defer thinking too hard about it until this simpler object is more done, and then refactor as desired once a putative b-spline regressor becomes a thing. I certainly wouldn't want to make this object more mysterious-seeming by adding knots, nor have to think through forms of magic to switch modes.

Hello!
So I get an instacrash with the patch above if I do something naughty (the numberbox to 1 to declare 1 dim, yet having 3 dims generated) then fix then predict (= crash) - otherwise it seems to work fine. Also, we spoke about the 1 to many approach - @weefuzzy thought it was magic but did that grow on him? otherwise this is great thanks

@lewardo - is there anything specific you need from me in terms of review? It looks like @tremblap is on testing, so it probably doesn't make sense to double too much, so please direct my attention as needed.

It's unclear to me why Owen would have cried - I see no obvious issues with code formatting.

Yeah, not unduly tearful (though clang-formatting is always appreciated). I didn't warm to the magic, no; much rather we just made it easier to duplicate / 'broadcast' a dataset column instead

@weefuzzy while talking to @AlexHarker we came upon the subject of allocators, and hence the ScopedEigenMap vs raw Eigen object debate for controlled memory allocation - do you think this object requires any custom allocation considerations ? At the moment each object has a raw Eigen matrix for the coefficients, design matrix and filter matrix, would a scoped map be more appropriate ?

The simple (or simple-sounding) guideline is: does it ever need to allocate in the audio thread? Eigen's built-in types are hardcoded to use malloc, so the ScopedEigenMap stuff is there to let us step around that.
However, where you have matrix multiplications, it's not always obvious where allocation is happening because Eigen's default behaviour is to create temporaries behind the scenes on the assumption that there is aliasing. If you know there isn't aliasing, e.g. A = BC then you can signal that with A.noalias() = B*C. For more complex expressions it's not always easy to tell though: Eigen has some utility macros you can use to throw asserts when it tries to allocate, which are useful for working out if you need to, say, make your own class-scope temporaries or whatnot.
(Eventually I'd be inclined to move towards using the ScopedMaps everywhere, so that we can use things like memory arenas for better in-algorithm locality where it makes sense, but that's still a pipedream)

I'll take some time to refactor this to only use ScopedEigenMaps just for paranoid safety then, if it's the goal in the long run anyway
Very interesting read about the eigen aliasing, not something I knew about before...

@tremblap's bug has now been fixed, although the fix will be overwritten when I port the eigen stuffs over to the custom allocator - for now however it seems to be a clean object that works, it could be drip-fed to testers for ui testing and the memory things could be done in the bg while the front-end is road-tested

Thank you @weefuzzy for the message, it really clarified my understanding of the ScopedEigenMap/FluidTensor memory allocation paradigm, I am aware that this code now needs refactoring for best memory practice, especially during the matrix multiplications - it allocates correctly but copies the data when it needn't.
I'll finish this at some point, in the meantime the eureka is really helping me with the LSTM object I'm working on (foreshadowing intended), so thank you for the clarification !!


Suggestion: reference resource containing all Azure AI Vision image modification APIs

I've been reviewing the Azure AI Vision documentation on the v4 APIs and note that there's a few different APIs that help generate new images including:

Smart-cropping
Rectification
Stitching

I noticed that no other pages mentioned that the rectify or stitch APIs exist and wondered what other image modification capabilities existed.

It might be a good idea to include a resource page in the documentation - perhaps a How to or Samples entry - that lists the current APIs that generate new images from provided images. Most people are going to look at the Azure AI Vision offerings for image analysis, but there's now enough present that it might be good to advertise these capabilities - especially in scenarios where someone might want to consider pre-processing an image before sending it to Azure.

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

ID: ef942c5b-b09d-75ca-bb9c-c33cd06a896c
Version Independent ID: f368865e-bd01-c5a7-c117-b72d6eb8bc69
Content: Prepare images for Product Recognition - Azure AI services
Content Source: articles/ai-services/computer-vision/how-to/shelf-modify-images.md
Service: azure-ai-vision
GitHub Login: @PatrickFarley
Microsoft Alias: ginle

@IntegerMan
Thanks for bringing this to our attention.
I'm going to assign this to the document author so they can take a look at it accordingly.

I will bring this suggestion to the PM

#sign-off


Added start_all function which starts all torrents and respects the queue order

This functionality seems to already exist.


Initial snowplow tracking

Signed-off-by: Ian Costanzo<EMAIL_ADDRESS>WIP - initial snowplow tracking, just on the Issuer endpoints initially
@WadeBarnes does this look correct to you, based on the spec?

"Snowplow tracking"? Do tell...

Do we want to add tracking for V3 and V4 endpoints as well?

Yes, I've just done one endpoint so far ...

@WadeBarnes does this look correct to you, based on the spec?
@ianco, Yes.
Would it be possible to wrap the tacking in a middleware component such that the tracking can be done more generically rather than having to discretely implement it on each endpoint?

"Snowplow tracking"? Do tell...
@swcurran, To add API statistics to the GDX analytics  dashboards.

Would it be possible to wrap the tacking in a middleware component such that the tracking can be done more generically rather than having to discretely implement it on each endpoint?

@WadeBarnes  that's what I'm looking into next.  I think in general Yes it can be done, but there is some specific request-specific info that is attached to the tracking event, I'm not sure how generically we can "harvest" this info from the request.

@ianco, The internal_call attribute was included as a flag to indicate whether the call was coming, "internally", from an OrgBook component such as the frontend during regular use, or a direct API call from and external integrating party.  That way we could differentiate between application and integration usage.  We just need to come up with a way to differentiate that for ourselves.

@WadeBarnes  the other things we need to derive dynamically are:

the url (we can get this from the request, but ideally need to map to the url pattern e.g. issuer/{id}/credentialtype vs issuer/1/credentialtype)
the parameters (possible to parse generically from the request?)
the total (count of items in the result - possible to dynamically parse the response stream?)

... and internal_call, as you mention.
My gut feel is that a combination of generic processing/request-specific processing (for some API's) will be required.

Some updates @WadeBarnes  @amanji :

tracking logic moved to middleware
CORS headers are used to determine if call is internal or not (internal = the orgbook app or swagger UI)
parameters are derived from GET or POST parameters
endpoint and item count can be set by the endpoint-specific code (passed to middleware as request attributes)
if endpoint is not provided, the derived django pattern will be used (could be something like api/credential/(?P<credential_id>[^/.]+)/verify, although it may be possible to build some rules to simplify this automatically)
if count is not provided will use count = 0

Only /api endpoints are currently tracked

massage the django endpoint url to make it look nice
add item count to many of the v2/3/4 services

@ianco, Looks good.  I'd recommend squashing your changes into a single commit to clean up the history.


Allow interactor to return multiple polygons

My actions before raising this issue

[x] Read/searched the docs
[x] Searched past issues

I built a custom interactor similar to IOG, bbox + positive points + negative points, that is able to recognize more than one object in the bbox.
I tried integrating my interactor with cvat by following the structure of the existing ones, and it works if in the response call I return only one polygon. If more than one polygon are returned, no polygons are displayed on the cvat interface.
If one Polygon is returned by the interactor:

If multiple Polygons are returned:

I tried returning polygons in the following formats:

a list of polygons:

[
    [[x11, y11], [x21, y21], ... ],
    [[x12, y12], [x22, y22], ... ]
]

a list of dicts with the same structure as the detectors:

[
    {
         "points": [[x11, y11], [x21, y21], ... ],
         "type": "polygon"
    },
   ...
]

Expected Behaviour

When a list of polygons is returned by an interactor, all the polygons should be processed by the cvat interface.
Current Behaviour

If a list of polygons is returned, none of them appear on the cvat interface.
Possible Solution

Edit the function that process the interactor response to detect if there are multiple polygons and process each one of them.
Steps to Reproduce (for bugs)

Not applicable.
Context

In our application, the object we are tying to annotate can be very small and very close to each other. To ease the burden of the annotators, we wanted to build an interactor that is able to segment multiple objects in one run. This allows the annotators to choose a larger bounding box and add many positive / negative guiding points to automatically segment many small objects.
 No
Operating System and version (e.g. Linux, Windows, MacOS): Linux dev-cvat 5.15.0-1019-aws **#23~20.04.1-Ubuntu**
Code example or link to GitHub repo or gist to reproduce problem:
Other diagnostic information / logs:
No logs appear.

Hello, @simone-viozzi Will you be able to contribute?

Yes, I'm following the contributing section to set up the environment.
Once I have a working environment, I will draft a PR and discuss a bit about the implementation.


Crop parameter on image via addSampler method

The texturePosition method which is part of the image module in the wgsl core, has a parameter called crop, a boolean that allows to not show the image tearing in the output when is rendered. If I'm not mistaken this can be done instead via the method from the POINTS library called addSampler, the second parameter is a descriptor, which has a lot of optional parameters, so if this can be made via the descriptor, maybe is better to remove the parameter from the texturePosition wgsl method.
There's also a convenience to do this via the fragment shader with the texturePosition instead of JavaScript, so this should be evaluated.

After looking at the docs for the GPUObjectDescriptorBase they don't have a way to stop the bleeding or crop the image directly there, so the texturePosition approach is correct, and there's no more to do here.


no metrics for cadvisor

What happened:
no metrics for cadvisor due to format issue
What you expected to happen:
https://github.com/splunk/fluent-plugin-kubernetes-metrics/blob/develop/lib/fluent/plugin/in_kubernetes_metrics.rb#L600-L631
it seems it looks for metrics with container_name= but cadvisor only have container=, name=, e.g.
container_cpu_system_seconds_total{container="foo",id="id",name="name",namespace="foo",pod="pod-name"} 2356.13<PHONE_NUMBER>226
Changes related to Kubernetes 1.16 , pod_name and container_name metric labels removed from cAdvisor metrics.
https://github.com/kubernetes/enhancements/issues/1206
https://github.com/kubernetes/kubernetes/pull/80376
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:

Kubernetes version (use kubectl version): 1.19.x
Others:

Hey @fengxx
Thanks for creating the issue.
I have made changes in metric plugin and is already merged. So it will be available on next release.
Closing the issue. Feel free to reopen the issue or create a new one if needed.


Addressing supply chain security-- Standard Issue #222

Update on 11/22. Reviews are now welcomed.

This addresses issue #222 on the Standard

We need two reviews on this.


Index stepID for logEntries so loading time decrease significantly

speedup from 2min loading to 0.01sec :D
got missed by  #1802

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@0c46ba4). Click here to learn what that means.
Patch has no changes to coverable lines.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2006   +/-   ##
=======================================
  Coverage        ?   38.99%
=======================================
  Files           ?      178
  Lines           ?    10636
  Branches        ?        0
=======================================
  Hits            ?     4147
  Misses          ?     6195
  Partials        ?      294

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Channels Integration for Strawberry

It would be great to have built-in support for Channels. Even though closely related to Django, Channels can stand largely on its own, and certainly has a number of features that can make Subscriptions implementation much simpler, especially in a large project by leveraging the Channel Layers and Groups communication features.
What I would like to see in a complete Channels implementation (spoiler alert, I already have a partially completed PR working on this):

[ ] Channels Consumers for the GraphQL websocket subscription protocols; similar to the FastAPI, ASGI, and aiohttp integrations.
[ ] A Channels Consumer for HTTP. Not essential, but it would provide some benefits.
[ ] A higher level API using the Channels Layer to send and receive events in subscription resolvers. I'm not 100% sure about this, but while it is probably easy enough for any dev to build their own, I suspect it will dramatically reduce the learning curve if a simple high-level API exists. In particular for cases where someone uses the Django view for Strawberry, and especially the non-async view, a special-purpose API for sending events to the subscription resolvers would be great.
[ ] A couple of good simple examples for the examples repo (probably a full-async example, and a sync http with async websocket example)
[ ] A more advanced example which could live anywhere (I'm building one for myself in a repo of my own anyway)
[ ] Documentation, of course.
[ ] Unit tests, of course.

I've started building this, and have the Channels Consumers and an example and some unit tests so far. The unit tests are mostly just adapted from FastAPI, so there is definitely more to be added.
While the pull request (#1407) is not done yet, what is already pushed is in a good state and I would love to get feedback on it, or further ideas or expansions for this. I've been a dev for many years but this is my first attempt at a significant OSS contribution, so I'm sure I'm getting some things wrong along the way here!

Upvote & Fund

We're using Polar.sh so you can upvote and help fund this issue.
We receive the funding once the issue is completed & confirmed by you.
Thank you in advance for helping prioritize & fund our backlog.

Thoughts on the high-level API for subscriptions:
In a Django application there's every chance you have sync views, and you want to be able to hand off events to the subscription asyncgenerator for delivery to the client.
In Channels, the way to do this is probably to use Layers and groups. Each websocket consumer has its own channel name in Layers. The most logical approach to publishing an event to a subscription is for the resolver to join a group for that event type, and then any part of the django project (even worker processes, or other servers in a large deployment) can do a group_send() to the Layers group, and the event will be consumed by the subscription.
It's not too crazy to build this yourself, but I think it would be nice to wrap it up and provide a pre-packaged event protocol and so on.
Just thinking on the spot at the moment, but the API for a Django app might look something like for example (contrived example using some stripe webhook code I had handy):
The view:
from django.http import (
    HttpRequest,
    HttpResponse,
)
from django.views.decorators.csrf import csrf_exempt
from django.views.decorators.http import require_POST
from strawberry.channels.sync_events import send_subscription_event
@require_POST
@csrf_exempt
def stripe_webhook(request: HttpRequest) -> HttpResponse:
    payload: bytes = request.body
    sig_header = request.META["HTTP_STRIPE_SIGNATURE"]
    process_stripe_webhook(sig_header, str(payload, "utf-8"))
    send_subscription_event(group="stripe", event="webhook_received", data=payload)
    return HttpResponse(status=200)

The Subscription field:
@strawberry.type
class Subscription:
    @strawberry.subscription
    async def listen_to_stripe(
        self,
        info: Info[StrawberryChannelsContext, None],
        stripe: StripePayload,
    ) -> str:
        """
        Subscribe to stripe webhooks. This is a ridiculous example that no one should ever be doing.
        """
        async for item in info.context.request.receive_subscription_events("stripe"):
            if item.event == "webhook_received":
                yield StripePayload(event)
            # ...

Only just started thinking this part through, thoughts and ideas welcome...there might be a better way or it might not be necessary/worth it at all...

@LucidDan I like it! Do you think we could use ContextVariables to access the receive_subscription method inside a subscription resolver?

@LucidDan I like it! Do you think we could use ContextVariables to access the receive_subscription method inside a subscription resolver?

Hmm, maybe? To be honest, I've never looked at contextvars much. I've done some research and reading just now, and it intrigues me, particularly in that it guarantees to be local to the eventloop task, but I'm not sure what concrete value we'd get from it in this scenario. I'll keep it in mind as I build this bit out though.
Also, thinking about this, a more logical interface might be more like:
from strawberry.channels import receive_subscription_events

# ...

    async for event in receive_subscription_events(info.context.request, "webhook"):
        # ...

Not having the method defined on the context or request is probably better. I'll likely have a prototype of this built today to experiment with, probably in an example repo along with a demo of using the Channels integration that has already been completed in the PR.

Another night going through old issues. Correct me if I'm wrong, but AFAIK most if not all of the points in this issue have been resolved. Mostly be the addition and continues improvement of our channels integration. If something is missing feel free to reopen.

Another night going through old issues. Correct me if I'm wrong, but AFAIK most if not all of the points in this issue have been resolved. Mostly be the addition and continues improvement of our channels integration. If something is missing feel free to reopen.

I think so.
Of course we can always have more docs and more examples, but in general all points in this issue have been fixed! :)


Add BodyPlus1 font token (and Body_2 base token)

Pull Request
🤨 Rationale
Issue #1831 was half completed by adding a token for the BodyEmphasizedPlus1 font in PR #1836. This PR completes the request by adding a token for  BodyPlus1.
👩💻 Implementation
Followed the Theme-aware tokens contributing docs.
🧪 Testing
Manual review of Storybook token stories.
✅ Checklist

[x] I have updated the project documentation to reflect my changes or determined no changes are needed.

@jattasNI skipping review since straightforward change and looks aligned on conventions


Create Documentation Using MkDocs

This PR adds proper documentation using Material for MkDocs.
Most of the docs have just been copied over from the previous .md  files with some small improvements, however with MkDocs, there is lots more possibilities for customisation in the future. Using MkDocs will make it easier for developers to use FlightRadarAPI.
Any suggestions for improvement would be appreciated!
Demo Site
Things to note

If you decide to merge, the site needs to be enabled via GitHub pages. To do this:

Wait until initial run of deploy-docs.yml is complete
Go to the repos settings
Go to the pages section
Set source to Deploy from a branch
Set branch to gh-pages
Leave folder as /root
Click save
This will deploy the site.

The website link on the repo should be changed to https://JeanExtreme002.github.io/FlightRadarAPI/

The wiki should probably be deleted

Future Improvements
While these docs are an improvement on the previous method of using .md files in the repo, they are in a very basic form. Here are some future improvements that could be made:

Implement versioning
Add all API options to the docs (some functions that are available are not currently recorded in the docs)
Design a better logo and favicon
Move different functions onto different pages or find another way to make it more organised rather than having all functions just pasted onto one page, which makes it difficult to read
Take advantage of the many other powerful features available in Material for MkDocs (adding comments to code, improved navigation etc...)

Hi @Hamster45105!
First and foremost, I would like to thank you for your contribution. What you did here was incredible!  The documentation is very well organized and very beautiful. :heart:
I don't have much knowledge in technologies for creating documentation yet, but I intended to start studying and improving the project's documentation later this year. I'm glad you showed up to help.
As for the suggestions for improvements, I will take them into consideration. I still need to learn how to use MkDocs, so it may take some time for me to start editing the files — even because I'm a little busy dealing with some university projects.
I reviewed your PR and I'm merging it now. 😃
Again, thank you very much for your huge contribution to the project. 💯

Hi, thank you for your fast response! I'm glad I could help out in such a meaningful way and thanks for maintaining such an amazing open source project.
Also, good luck with your university studies!

I just published the new version at Pypi and NPM ❤
As for MkDocs, I did some research on it, and it doesn't seem too difficult to learn. I'll dedicate some time to study and practice with it later this week.


Wxfile fix update

Changes
We needed to call AsdfFile.update during writing a tree. This method cleans up unused blocks in the existing asdf file. If the target file (or handle) is empty, then we use AsdfFile.write_to
Thanks @vhirtham for finding this and sharing a minimal example.
Related Issues
Closes #516
Checks

[x] updated CHANGELOG.md
[x] updated tests

Hello @marscher! Thanks for updating this PR.

In the file weldx/asdf/util.py:

Line 1:5: E999 SyntaxError: invalid syntax

Hello @marscher! Thanks for updating this PR.
* In the file [`weldx/asdf/util.py`](https://github.com/BAMWelDX/weldx/blob/8b6928b97b631f77a350c34ae199e415de4f1aa4/weldx/asdf/util.py):

Line 1:5: E999 SyntaxError: invalid syntax

nope :)


Added link to Official AngularJS Documentation

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Hi @hacktober24
It seems that similar changes have already been accepted earlier for this article you're editing, sorry about that. 😓
If you feel you have more to add, please feel free to open up a new PR.
Thanks again! 😊

If you have any questions, feel free to reach out through Gitter or by commenting below. 💬


Crash when opening a file

I've installed your container, but when i try to load a video it just crashes.
I've tried some mp4s and webms with no luck.
Any idea why?
https://user-images.githubusercontent.com/61975168/223448772-b971cafc-1985-4abc-a906-de44bd00988c.mp4
Log file: _handbrake-handbrake-1_logs.txt
Also the permissions on the volumes folders should be ok (container running with pid and gid 1000 which is the same for the folders)

I have the same exact problem. The same log output. The automated encoding from /watch folder works for me, but not if I press and use the web GUI. Have you tried this?

I am also experiencing this restarting problem when opening a file through the UI.  It always seems to crash when generating the 9th of 10 preview images.  The last working version for me is v1.25.1.  Version v23.02.1 and newer seem to be affected.
handbrake-logs.txt

Same Issue for me with the same log file

Can you check the log file located at ghb/Activity.log* under the directory you mapped to /config?
Do you see the crash with all video files ?  Or some are working ?

Hello,
Same problem here :
proxmox/ubuntu/handbrake -> handbrake goes wild and crash on any opened source.
The only "logs" i could find relative to the crash is this :

No nginx error log, neither for hb.
Regards

After some more testing :
There is a problem on QEMU/KVM (proxmox).
If the docker host processors type is set to any QEMU type, like :

-> it will crash.
Resolved (in my case) by setting the "real" processor type (intel/amd/...).
Hope it might help others.

I was experiencing the same issue and @Ysval 's fix worked for me.
My container server is running in proxmox VM and was set to the default processor type of kvm64. Switching it to type "host" fixed the issue.

I also am running in a Proxmox VE VM. After changing the processor type from kvm64 to host, the problem is gone.
Thanks everyone!

Would ofc. still be preferable to not have a crash be expected behaviour ;)

Are you running Docker in a VM ?

Are you running Docker in a VM ?

Via Unraid/Portainer.

Is unRAID running in a VM ?

Are you running Docker in a VM ?

Any ideas on this issue? I am running Docker in a VM with "Default (kvm64)" set due to a complicated QSV issue.
I'm having the exact same symptoms as the people above.
Tdarr and Jellyfin are not having this issue when encoding using ffmpeg, suggesting that there's another issue with this particular container.

Any ideas on this issue?

Yes. A workaround for your concrete issue exists. A fix does not.

a VM with "Default (kvm64)" set due to a complicated QSV issue

I'm sorry, but you just explained why this is happening - it has already been pointed out in this thread. Expected behaviour with this configuration is currently a hard crash on file open. The only known workaround at present is to not use the emulated processor types in your VM configuration.

same error. need change vm cpu ?


Fix defense styles in top section

Realign styles in this section:

@johnlamping - I'll be fixing these issues next.

Great!
(All my time is going to get the next arc ready, so I probably won't be
doing any coding for another couple of months.)
On Sun, Jan 15, 2023 at 2:24 PM Jaz @.***> wrote:

@johnlamping https://github.com/johnlamping - I'll be fixing these
issues next.
—
Reply to this email directly, view it on GitHub
https://github.com/epic-power-rpg/roll20/issues/64#issuecomment-1383269181,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACTV55WNP3XA62RBOOVR4MTWSR2JNANCNFSM6AAAAAAT4DI2VE
.
You are receiving this because you were mentioned.Message ID:
@.***>

Sounds good. I'll keep pushing PR's for review. 👍🏾


fastX explanation

Hi Ed,
Is there any documentation that explains the difference between the X variants ?
Thanks,
Rajesh.

The meaning is explained in the paper that these come from.
All of these FAST detectors run on a 16 pixel circle. The X is how many
contiguous pixels you need in order to form a corner.
-Ed
On Thu, 15 Nov 2018 at 13:37, Rajesh Pradhan<EMAIL_ADDRESS>wrote:

Hi Ed,
Is there any documentation that explains the difference between the X
variants ?
Thanks,
Rajesh.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/edrosten/fast-C-src/issues/4, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABGW6-g5FoO_xfdkj5_ARIURyqoO5XqIks5uvW38gaJpZM4Yfz6q
.


Mention praw.ini requirement for refresh token script

Describe the solution you'd like
The page https://praw.readthedocs.io/en/stable/tutorials/refresh_token.html contains a script to fetch a refresh token. Old versions of the script would prompt you for the client id and client secret, but the new version does not, and expects either praw.ini or environment variables to be set up. Could this be noted somewhere on the page?
Describe alternatives you've considered
No response
Additional context
No response

It mentions that environment variables need to be set before running the script in the module docstring:
#!/usr/bin/env python

"""This example demonstrates the flow for retrieving a refresh token.

This tool can be used to conveniently create refresh tokens for later use with your web
application OAuth2 credentials.

To create a Reddit application visit the following link while logged into the account
you want to create a refresh token for: https://www.reddit.com/prefs/apps/

Create a "web app" with the redirect uri set to: http://localhost:8080

After the application is created, take note of:

- REDDIT_CLIENT_ID; the line just under "web app" in the upper left of the Reddit
  Application
- REDDIT_CLIENT_SECRET; the value to the right of "secret"

Usage:

    EXPORT praw_client_id=<REDDIT_CLIENT_ID>
    EXPORT praw_client_secret=<REDDIT_CLIENT_SECRET>
    python3 obtain_refresh_token.py

"""

I understand, but I think it's better to leave it out of the module docstring and instead put it directly inside the documentation for the script. Maybe sphinx.ext.autodoc would come in useful for this?


fixed note on tenant config

Purpose

fixes A-2118
fixed note on tenant config
https://github.com/wso2/docs-apim/issues/5312

Output

@AnuGayan @ruks  is this needed from 4.0 onwards ?

Yes, We don't need in ELK based analytics

@ruks and @AnuGayan, so is it correct to understand that we can remove this note from 4.0.0 and newer versions?

@ruks and @AnuGayan, so is it correct to understand that we can remove this note from 4.0.0 and newer versions?

yes, this is used in SP-based analytics to view analytics dashboards, APIM 400 onwards we don't have SP dashoards.


[DatePicker] (click) event delay

<datepicker (click)="doSomething">
doSomething function will return the current value of the date and then update to the new selected date.
For example if i click on the 24th (since its first click nothing happens), and then click on 25th, doSomething gets the date of the 24th. Its like its emitting an event and then updating the model

@brandenwagner What do you mean with doSomething function?

<datepicker [(ngModel)]="dt" (click)="doSomething()"></datepicker>
the doSomething function
public doSomething() {
     console.log(this.dt);
}

Is always 1 click behind

@brandenwagner You need to wait until the date is updated. The moment you click, the doSomething() function is called, but the date is not yet updated.

How do I do that?
On Thursday, May 26, 2016, Christian Ulmann<EMAIL_ADDRESS>wrote:

@brandenwagner https://github.com/brandenwagner You need to wait until
the date is updated. The moment you click, the doSomething() function is
called, but the date is not yet updated.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/valor-software/ng2-bootstrap/issues/542#issuecomment-221866476

--
Branden Wagner
PureIntellect.Com
<EMAIL_ADDRESS>http://www.pureintellect.com/

HI @brandenwagner,
You can use like this too
<datepicker [ngModel]="dt" (ngModelChange)="doSomething()"></datepicker>
Thanks,

That worked! i feel like an idiot. i kept tying to do onChange and it wouldn't work.. just had to use the right word. THANKS!


const_cast 2. explicitly  both convert to uint8_t for comparison

I don't think any of these changes are warranted based on my tests with gcc. For assimp, we would consider updating as a separate PR.


Some files are installed into paths that contain build directory

Offending files that are installed into the staged directory:
/usr/ports/cad/surelog/work/.build/runtime/thirdparty/utfcpp/install/include/utf8cpp/utf8.h
/usr/ports/cad/surelog/work/.build/runtime/thirdparty/utfcpp/install/include/utf8cpp/utf8/checked.h
/usr/ports/cad/surelog/work/.build/runtime/thirdparty/utfcpp/install/include/utf8cpp/utf8/core.h
/usr/ports/cad/surelog/work/.build/runtime/thirdparty/utfcpp/install/include/utf8cpp/utf8/cpp11.h
/usr/ports/cad/surelog/work/.build/runtime/thirdparty/utfcpp/install/include/utf8cpp/utf8/unchecked.h
/usr/ports/cad/surelog/work/.build/runtime/thirdparty/utfcpp/install/lib/cmake/utf8cpp/utf8cppConfig.cmake

Punt. No more an issue after switching to use pristine antlr (support for utf8 is now optional/deprecated).


[LS] Suggest methods of a class within method body of methods within the same class

Description:
$subject
Right now, we have to type self.<cursor> to get completions for methods with the class. It will be convenient if we show suggestions for methods of the same class without having to type self..
Describe your problem(s)
See description
Suggested Labels (optional):
Language Server

@TharushiJay


Deleting a rancher secret should delete secret

Rancher versions:
rancher/server: 1.6.10
Steps to Reproduce:
Setup rancher secrets. Run a container service with a created secret.
Results:
Remove secret and observe that services still using the secret can access it.
Goal: deleting a secret should remove it everywhere for current and any subsequent usage.

That is a non-goal, because it breaks existing running applications (either immediately if they re-read the secret into memory regularly, or on restart if they don't).  If that value is no longer valid you create a new secret and upgrade the services using it, which will then have the new value (and not have the old one).
If anything, a secret should refuse to delete while there are active references to it... But once the secret value has been pushed down to containers the cat is out of the bag, you can't push the cat back in by trying to clean it up later.

Secrets are injected as part of the volume create process to ensure they are available before the container starts. The volume driver obtains the secret writes  it once and then stops monitoring it. It does look like there is a bug, when the container is stopped or deleted the volume driver steps in again to clear the contents. It looks like one of the references isn't getting cleaned up and the secret is still available. Need to take a look at that. This would cause the service to break though, as it would no longer have access to data that it needs to startup.
In 2.0 this behavior will change as we build on top of K8s. The K8s secrets update the files when they change. I don't think they do anything to the env vars though.

Thanks guys. @cloudnautique I do believe that bug situation you mentioned exists. In some cases where you'd expect the secret to be gone (not on running/immutable services) it is still there.

I really hope this gets fixed for 1.6

With the release of Rancher 2.0, development on v1.6 is only limited to critical bug fixes and security patches.


THE REAL GAME

Gimme now or else olive ur adderss is
**** SE Ta***r
PLZ I DONt KNOW HOW 2 CODE I WONT DO ANYTHING BAD PLZPLZPLZPPLZ

Only in Texas you wouldn't know how to code ... Nah for real though

https://harvey.ai

6029 SE Taylor Ct With the yellow house and the murphy construction van

🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏🙏


Fix Rivalry boost

https://www.smogon.com/forums/threads/pokémon-showdown-damage-calculator.3593546/page-8#post-8199267 and https://www.smogon.com/bw/articles/bw_complete_damage_formula agree on 0x1400 and 0xC00. I'm not sure about gen 4 but it should be the same.

Verifying this change is accurate.

Thanks! Sorry for the delay on merging; various changes got in the way, and I wanted to verify this.


Wayland

Does it run natively on Wayland or need XWayland? MX Linux is using X11 but I'm planning to switch to another Linux distro that will launch Wayland sessions by default. Some Linux distros even don't ship with X11 nowadays.

It does run negatively on Wayland.

It does run negatively on Wayland.

negatively? Do you mean natively?

:rofl: yes, natively


Build test executables from within the test suite

This gets rid of the requirement to run cargo build --bin cradle_test_helper --features test_executables and cargo build --bin cradle_panic --features test_executables manually before running the test suite. Those commands are now triggered once per test-suite from within the test suite itself. More discussion here: #117

Nice, this looks good to me.


Release a new version of JFR core and deploy the updated FlameGraph service

We will need to release a new version of JFR core with the optimization work and pull it into the Java agent before the 7.0.0 release. We will also need to deploy the latest version of the Flamegraph service supporting these changes.

Jfr Core 1.3.0 has been released - https://search.maven.org/search?q=newrelic jfr


Old docs still up at http://documentcloud.github.io/backbone/

I recently got tripped up by the fact that http://documentcloud.github.io/backbone/ is hosting out-of-date downloads and documentation, and looks just like the new official site at backbonejs.org. I'm not sure how I first stumbled upon the old URL (probably DuckDuckGo search results). The same situation exists for Underscore: http://documentcloud.github.io/underscore/
Perhaps it would be wise to set up a redirect from the old URL to the new one?

Looks like an issue with Github Pages. We changed the repo over to jashkenas/backbone two years ago, and it looks like the Pages branch never got updated.

I'll open a ticket with Github Support.

It was a bug when project moving was first implemented. Support has helpfully unpublished the pages for us.


Custom columns in develocity build scan reports

See https://github.com/hibernate/hibernate-github-bot?tab=readme-ov-file#configuration
Before:

After: let's see :)

https://github.com/hibernate/hibernate-search/pull/4138/checks?check_run_id=24295144756 🥳

Ah, right, we'll need to merge before the configuration is taken into account :/
Well, YOLO.

@marko-bekhta https://github.com/hibernate/hibernate-search/runs/24295814756 :partying_face:

it worked ! it worked ! 😄

Actually, there were problems with amazon-opensearch-serverless and some DBs, so I pushed a few more commits.
Now it works: https://github.com/hibernate/hibernate-search/runs/24297697246


Fixed build error for HelloWorld example.  ('String?' must be unwrapped)

When I was building / exploring the samples, I found that I the HelloWorld sample would fail with the following:
HelloWorld\HelloWorld.swift:17:55: error: value of optional type 'String?' must be unwrapped to a value of type 'String'   guard let message = try? accessor.access(), display(message) else {                                                       ^ C:\repos\swift-build-examples\HelloWorld-CMake\Source\HelloWorld\HelloWorld.swift:17:55: note: coalesce using '??' to provide a default when the optional value contains 'nil'   guard let message = try? accessor.access(), display(message) else {                                                       ^                                                               ?? <#default value#> C:\repos\swift-build-examples\HelloWorld-CMake\Source\HelloWorld\HelloWorld.swift:17:55: note: force-unwrap using '!' to abort execution if the optional value contains 'nil'   guard let message = try? accessor.access(), display(message) else {                                                       ^                                                              !

Thanks for the PR!  Once my internet is restored, I’ll test it locally.  I need to set up CI :(. Seems like this is a change between swift releases.


Allow Users to Update Duplicate Mysql Rows

This branch allows users to choose to update duplicate mysql rows rather than ignore them or throw an error. I also added the change from @varyform's PR to allow support for MySql2 adapters.

I had to code around this as well. Can this be reviewed and (maybe) merged?

Thank you very much! This looks great.


Re-display user's query with an error message if an error occurs

Refs #619

The one test failure here actually illustrates a larger problem: if the user specifies .json?_shape=array but an error occurs, what should we do?
Prior to this change we return the following JSON:
{
    "ok": false,
    "error": "You did not supply a value for binding 1.",
    "status": 500,
    "title": null
}

But this comes from the handle_500 higher level code here: https://github.com/simonw/datasette/blob/eae3084b46e2c3931db12cdef79093ad0e644bce/datasette/app.py#L1251-L1263

This is the current test failure, but it actually another problem that we don't have tests in place for errors with different formats and shapes:
    def test_magic_parameters_cannot_be_used_in_arbitrary_queries(magic_parameters_client):
        response = magic_parameters_client.get(
            "/data.json?sql=select+:_header_host&_shape=array"
        )
        assert 400 == response.status
>       assert "You did not supply a value for binding 1." == response.json["error"]
E       TypeError: list indices must be integers or slices, not str


Bump poetry

Codecov Report

Merging #38 (c55300c) into master (831f4cd) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #38   +/-   ##
=======================================
  Coverage   53.83%   53.83%
=======================================
  Files          18       18
  Lines        1211     1211
  Branches      213      213
=======================================
  Hits          652      652
  Misses        540      540
  Partials       19       19

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 831f4cd...c55300c. Read the comment docs.


Failure to correctly set admin socket permissions.

Bug Report
I intend to configure ceph-ansible to deploy ceph to several bare-metal remote hosts. Deployment, public, and cluster networks are seperate and all machines are reachable over all networks.  All machines are running an unmodified bare installation of ubuntu-server, installed via MAAS. I'm intending to later use this as a backend storage for openstack.
This is a minimal test configuration for ha-ceph, so it has 4 osd machines, 3 of which are to be monitors/managers/etc. as well.
To install ceph to these machines, I run
ansible-playbook site.yml
The operation stalls after about a minute of succeeding every operation with the following error:
TASK [ceph-mon : waiting for the monitor(s) to form the quorum...] *************************************************************************************************
Wednesday 18 November 2020  15:26:46 +0100 (0:00:00.219)       0:01:52.787 ****
FAILED - RETRYING: waiting for the monitor(s) to form the quorum... (10 retries left).
FAILED - RETRYING: waiting for the monitor(s) to form the quorum... (9 retries left).
FAILED - RETRYING: waiting for the monitor(s) to form the quorum... (8 retries left).
FAILED - RETRYING: waiting for the monitor(s) to form the quorum... (7 retries left).
FAILED - RETRYING: waiting for the monitor(s) to form the quorum... (6 retries left).
FAILED - RETRYING: waiting for the monitor(s) to form the quorum... (5 retries left).
FAILED - RETRYING: waiting for the monitor(s) to form the quorum... (4 retries left).
FAILED - RETRYING: waiting for the monitor(s) to form the quorum... (3 retries left).
FAILED - RETRYING: waiting for the monitor(s) to form the quorum... (2 retries left).
FAILED - RETRYING: waiting for the monitor(s) to form the quorum... (1 retries left).
fatal: [st01.hostname.com]: FAILED! => changed=false
  attempts: 10
  cmd:
  - ceph
  - --cluster
  - ceph
  - daemon
  - mon.st01
  - mon_status
  - --format
  - json
  delta: '0:00:00.112282'
  end: '2020-11-18 15:30:09.914318'
  msg: non-zero return code
  rc: 22
  start: '2020-11-18 15:30:09.802036'
  stderr: 'admin_socket: exception getting command descriptions: [Errno 2] No such file or directory'
  stderr_lines: <omitted>
  stdout: ''
  stdout_lines: <omitted>
[WARNING]: Failure using method (v2_runner_on_failed) in callback plugin (<ansible.plugins.callback.mail.CallbackModule object at 0x7fe0b9f1ddc0>): 'in <string>'
requires string as left operand, not int

NO MORE HOSTS LEFT *************************************************************************************************************************************************

PLAY RECAP *********************************************************************************************************************************************************
st01.hostname.com       : ok=113  changed=11   unreachable=0    failed=1    skipped=201  rescued=0    ignored=0
st02.hostname.com       : ok=96   changed=8    unreachable=0    failed=0    skipped=186  rescued=0    ignored=0
st03.hostname.com       : ok=96   changed=8    unreachable=0    failed=0    skipped=186  rescued=0    ignored=0
st04.hostname.com       : ok=47   changed=3    unreachable=0    failed=0    skipped=112  rescued=0    ignored=0

INSTALLER STATUS
Install Ceph Monitor           : In Progress (0:04:06)
        This phase can be restarted by running: roles/ceph-mon/tasks/main.yml

Wednesday 18 November 2020  15:30:09 +0100 (0:03:23.882)       0:05:16.670 ****
===============================================================================
ceph-mon : waiting for the monitor(s) to form the quorum... ----------------------------------------------------------------------------------------------- 203.88s
ceph-config : look up for ceph-volume rejected devices ----------------------------------------------------------------------------------------------------- 10.49s
ceph-infra : update cache for Debian based OSs -------------------------------------------------------------------------------------------------------------- 9.16s
gather and delegate facts ----------------------------------------------------------------------------------------------------------------------------------- 7.66s
ceph-validate : get devices information --------------------------------------------------------------------------------------------------------------------- 2.96s
ceph-config : run 'ceph-volume lvm batch --report' to see how many osds are to be created ------------------------------------------------------------------- 2.88s
ceph-validate : read information about the devices ---------------------------------------------------------------------------------------------------------- 2.55s
ceph-infra : enable chronyd --------------------------------------------------------------------------------------------------------------------------------- 2.40s
check for python -------------------------------------------------------------------------------------------------------------------------------------------- 2.34s
ceph-facts : resolve device link(s) ------------------------------------------------------------------------------------------------------------------------- 1.71s
ceph-validate : resolve devices in devices ------------------------------------------------------------------------------------------------------------------ 1.71s
ceph-facts : resolve device link(s) ------------------------------------------------------------------------------------------------------------------------- 1.66s
ceph-common : install ceph for debian ----------------------------------------------------------------------------------------------------------------------- 1.28s
ceph-infra : install chrony --------------------------------------------------------------------------------------------------------------------------------- 1.27s
ceph-facts : check for a ceph mon socket -------------------------------------------------------------------------------------------------------------------- 1.03s
ceph-mon : start the monitor service ------------------------------------------------------------------------------------------------------------------------ 1.02s
ceph-config : generate ceph.conf configuration file --------------------------------------------------------------------------------------------------------- 1.01s
ceph-common : update apt cache if cache_valid_time has expired ---------------------------------------------------------------------------------------------- 0.94s
ceph-common : install dependencies -------------------------------------------------------------------------------------------------------------------------- 0.94s
ceph-infra : disable time sync using timesyncd if we are not using it --------------------------------------------------------------------------------------- 0.92s
Playbook run took 0 days, 0 hours, 5 minutes, 16 seconds

Diagnosis so far
In order to find out what the admin socket is, I run:
ceph-conf --name mon.st01 --show-config-value admin_socket
which returns
/var/run/ceph/ceph-mon.st01.asok
The user ceph cannot access this file: By editing /etc/passwd and giving ceph access to /usr/bin/bash, I can execute runuser -l ceph -c 'touch /var/run/ceph/ceph-mon.st01.asok'. This prints:
touch: cannot touch '/var/run/ceph/ceph-mon.st01.asok': Permission denied
Checking this: ls -lha /var/run/ | grep ceph prints
drwxr-xr-x  2 libvirt-qemu kvm       40 Nov 17 16:31 ceph
And groups ceph prints
ceph : ceph
So ceph does not have permission to write to this directory. This is likely the cause of the error message above: the program cannot create the admin socket file to connect to the other cluster members and halts, which aborts the testing step.
Workaround
I login to every host separately and execute the following two commands:
usermod -a -G kvm ceph
chmod g+w /var/run/ceph/

Theoretically this would completely solve the issue. I suggest adding the user ceph to the kvm group and modifying permissions on the folder containing the admin socket to allow the group to write.  In my configuration, since openstack will run on separate machines from the storage solution this is irrelevant: no hypervisors are run on the ceph hosts so I used the simple workaround above instead of configuring ACLs.
Unfortunately, if you now re-run the ansible-playbook site.yml command, it will reset this write permission and fail with the same error.
As an alternative, You could install acl as a prerequisite package nd use ACLs to only give the ceph user permission to write to this folder (and still forbid it for members of kvm other than libvirt-qemu, although it is probably unlikely such a user exists.
Configuration
Any configuration related to the admin socket is left to the default.
List of changes made to the group vars (as compared via diff to the standard values):
< # Set to the value reported by apt:
< ceph_release_num: 15
< ceph_origin: distro
< radosgw_num_instances: 2
< openstack_config: true

< dashboard_protocol: https
< dashboard_port: 7481

< ceph_rbd_target_gw_docker_cpu_limit: 2
< ceph_rbd_target_api_docker_cpu_limit: 2

Finally, contents of the hosts file are:
# This is the default ansible 'hosts' file.
#
# It should live in /etc/ansible/hosts
#
#   - Comments begin with the '#' character
#   - Blank lines are ignored
#   - Groups of hosts are delimited by [header] elements
#   - You can enter hostnames or ip addresses
#   - A hostname/ip can be a member of multiple groups

all:
  hosts:
    # Separate hosts
    st01.hostname.com:
      ansible_ssh_user: deploy
      ansible_sudo_pass: secret
      ansible_ssh_private_key_file: /home/ansible/.ssh/id_st01
    st02.hostname.com:
      ansible_ssh_user: deploy
      ansible_sudo_pass: secret
      ansible_ssh_private_key_file: /home/ansible/.ssh/id_st02
    st03.hostname.com:
      ansible_ssh_user: deploy
      ansible_sudo_pass: secret
      ansible_ssh_private_key_file: /home/ansible/.ssh/id_st03
    st04.hostname.com:
      ansible_ssh_user: deploy
      ansible_sudo_pass: secret
      ansible_ssh_private_key_file: /home/ansible/.ssh/id_st04
  children:
# If you have a group of hosts using a pattern you can specify
# them like this:

#www[001:006].example.com

# Here's another example of host ranges, this time there are no
# leading 0s:

#db-[99:101]-node.example.com

# Ceph Monitor Hosts
# Currently set to the 'storage' network.

    mgrs:
      hosts:
        st01.hostname.com:
        st02.hostname.com:
        st03.hostname.com:
    mdss:
      hosts:
        st01.hostname.com:
        st02.hostname.com:
        st03.hostname.com:
    mons:
      hosts:
        st01.hostname.com:
          monitor_address: <IP_ADDRESS>
        st02.hostname.com:
          monitor_address: <IP_ADDRESS>
        st03.hostname.com:
          monitor_address: <IP_ADDRESS>

# Ceph radosgw hosts
    rgws:
      hosts:
        st01.hostname.com:
          radosgw_address: <IP_ADDRESS>
        st02.hostname.com:
          radosgw_address: <IP_ADDRESS>
        st03.hostname.com:
          radosgw_address: <IP_ADDRESS>
        st04.hostname.com:
          radosgw_address: <IP_ADDRESS>

# Ceph data hosts
# nvme0n2 is a separate journal partition on an SSD drive
    osds:
      hosts:
        st01.hostname.com:
          devices: ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/sdf', '/dev/sdg', '/dev/sdh']
          raw_journal_devices: ['/dev/disk/by-label/pjrn1', '/dev/disk/by-label/pjrn2', '/dev/disk/by-label/pjrn3', '/dev/disk/by-label/pjrn4', '/dev/disk/by-label/pjrn5', '/dev/disk/by-label/pjrn6', '/dev/disk/by-label/pjrn7']
          public_network: <IP_ADDRESS>/22
          cluster_network: <IP_ADDRESS>/24
        st02.hostname.com:
          devices: ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/sdf', '/dev/sdg', '/dev/sdh']
          raw_journal_devices: ['/dev/disk/by-label/pjrn1', '/dev/disk/by-label/pjrn2', '/dev/disk/by-label/pjrn3', '/dev/disk/by-label/pjrn4', '/dev/disk/by-label/pjrn5', '/dev/disk/by-label/pjrn6', '/dev/disk/by-label/pjrn7']
          public_network: <IP_ADDRESS>/22
          cluster_network: <IP_ADDRESS>/24
        st03.hostname.com:
          devices: ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/sdf', '/dev/sdg']
          raw_journal_devices: ['/dev/disk/by-label/pjrn1', '/dev/disk/by-label/pjrn2', '/dev/disk/by-label/pjrn3', '/dev/disk/by-label/pjrn4', '/dev/disk/by-label/pjrn5', '/dev/disk/by-label/pjrn6']
          public_network: <IP_ADDRESS>/22
          cluster_network: <IP_ADDRESS>/24
        st04.hostname.com:
          devices: ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/sdf', '/dev/sdg', '/dev/sdh']
          raw_journal_devices: ['/dev/disk/by-label/pjrn1', '/dev/disk/by-label/pjrn2', '/dev/disk/by-label/pjrn3', '/dev/disk/by-label/pjrn4', '/dev/disk/by-label/pjrn5', '/dev/disk/by-label/pjrn6', '/dev/disk/by-label/pjrn7']
          public_network: <IP_ADDRESS>/22
          cluster_network: <IP_ADDRESS>/24

# ISCSI gateways for CEPH Datastores
#    iscsigws:
#      hosts:
#        st01.hostname.com:
#        st02.hostname.com:
#        st03.hostname.com:

Note that here, the by-label accesses are partitions on a fast ssd disk. This disk is split into 7 equally sized partitions for use as journals, a fast cache for the larger and slower spinning drives making up the cluster. Each host has a deploy user. Note: In all examples,  hostnames and passwords are excluded for security reasons.
There are some other changes related to iscsigws, but since ceph-ansible reports this isn't supported via ansible on ubuntu, these are not relevant (I've commented out the [iscsigws] section of the hosts file, so it should not run this playbook.
Environment:

OS (e.g. from /etc/os-release): Ubuntu 20.04.1 LTS
Kernel (e.g. uname -a): 5.4.0-52
Docker version if applicable (e.g. docker version): Not applicable
Ansible version (e.g. ansible-playbook --version): 2.9.6
ceph-ansible version (e.g. git head or tag or stable branch): stable 5.0 (latest, for ansible 2.9).
Ceph version (e.g. ceph -v): As installed by ceph-ansible, 15.2.3 (although the process does not fully complete: the installation is what fails. It may still need to update further).

Checking this: ls -lha /var/run/ | grep ceph prints
drwxr-xr-x 2 libvirt-qemu kvm 40 Nov 17 16:31 ceph

I'm not sure to understand why you have such owner/group because it should be configured with ceph:ceph by default.
Could you share the full ansible logs and variables defined in {group,host}_vars directories ?


fix: Server in subdirectory

Closes #1796

@ura14h Would you mind taking a look at it?

@tassoevan Sure.
I pulled latest master and made sure 'yarn test' and 'yarn start'. And I inspected all URL with using developer tool console and network monitor. And I read code you changed.
Yes, I think that the app is working fine on my environments.


Dismiss kb after posting comment

Version 1.4.0 (1134)
Device: iPhone 7 Plus (iOS 10.3.3)

reverting this, too much motion


pull feature-patch-wordproc to master

This feature patches two bugs in the word processor.

previously, the default save format did not support formatting. The default has been changed.
previously, not all the fonts in the font selection menu were actually available, this has been fixed.

Seems good. Not quite sure how the default file change works, but it does.


👷: Move from kaniko to docker build and push action

We are using docker/build-push-action throughout our projects, this PR introduces this action also in this repo
It also prepares the code for release 0.1.5

Successful building job can be found here

Codecov Report

Merging #8 (b96217f) into main (c38f973) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main       #8   +/-   ##
=======================================
  Coverage   72.72%   72.72%
=======================================
  Files           1        1
  Lines         154      154
=======================================
  Hits          112      112
  Misses         34       34
  Partials        8        8


Unable to create project with Ubuntu

I can't create a new project in Chrome running on Ubuntu 15.04. My version is qiciengine-1.0.3.
Should Linux work or is it currently not supported?
In case it helps here is the log:
Please enter this url in browser:
http://<IP_ADDRESS>:5002/Project.html
New connection.
-----> QUERY_SETTINGS
-----> GET_PLATFORM
-----> GET_USER_HOME_DIR
-----> RECENT_OPEN
-----> GET_USER_HOME_DIR
-----> CHECK_FOR_UPDATES
-----> RECENT_OPEN
New connection.
-----> LIST_DIR
cmd：LIST_DIR，exception：Error: ENOENT, no such file or directory '/Volumes'
Error: ENOENT, no such file or directory '/Volumes'
at Object.fs.readdirSync (evalmachine.:659:18)
at listDir (/home/pablo/Documents/gameprojects/qiciengine-1.0.3/editorservice/cmd/LIST_DIR.js:39:12)
at Object.M.COMMAND.registerCmd.main (/home/pablo/Documents/gameprojects/qiciengine-1.0.3/editorservice/cmd/LIST_DIR.js:87:16)
at clazz.dispatch (/home/pablo/Documents/gameprojects/qiciengine-1.0.3/editorservice/socket/Command.js:121:33)
at Socket. (/home/pablo/Documents/gameprojects/qiciengine-1.0.3/editorservice/socket/Command.js:97:14)
at Socket.EventEmitter.emit (events.js:98:17)
at Socket.onevent (/home/pablo/Documents/gameprojects/qiciengine-1.0.3/node_modules/socket.io/lib/socket.js:330:8)
at Socket.onpacket (/home/pablo/Documents/gameprojects/qiciengine-1.0.3/node_modules/socket.io/lib/socket.js:290:12)
at Client.ondecoded (/home/pablo/Documents/gameprojects/qiciengine-1.0.3/node_modules/socket.io/lib/client.js:193:14)
at Decoder.Emitter.emit (/home/pablo/Documents/gameprojects/qiciengine-1.0.3/node_modules/component-emitter/index.js:134:20)
-----> LIST_DIR
-----> LIST_DIR
-----> LIST_DIR
-----> CREATE_PROJECT
cmd：CREATE_PROJECT，exception：TypeError: Object # has no method 'isAbsolute'
TypeError: Object # has no method 'isAbsolute'
at clazz.createProject (/home/pablo/Documents/gameprojects/qiciengine-1.0.3/editorservice/module/Project.js:32:15)
at Object.M.COMMAND.registerCmd.main (/home/pablo/Documents/gameprojects/qiciengine-1.0.3/editorservice/cmd/CREATE_PROJECT.js:10:29)
at clazz.dispatch (/home/pablo/Documents/gameprojects/qiciengine-1.0.3/editorservice/socket/Command.js:121:33)
at Socket. (/home/pablo/Documents/gameprojects/qiciengine-1.0.3/editorservice/socket/Command.js:97:14)
at Socket.EventEmitter.emit (events.js:98:17)
at Socket.onevent (/home/pablo/Documents/gameprojects/qiciengine-1.0.3/node_modules/socket.io/lib/socket.js:330:8)
at Socket.onpacket (/home/pablo/Documents/gameprojects/qiciengine-1.0.3/node_modules/socket.io/lib/socket.js:290:12)
at Client.ondecoded (/home/pablo/Documents/gameprojects/qiciengine-1.0.3/node_modules/socket.io/lib/client.js:193:14)
at Decoder.Emitter.emit (/home/pablo/Documents/gameprojects/qiciengine-1.0.3/node_modules/component-emitter/index.js:134:20)
at Decoder.add (/home/pablo/Documents/gameprojects/qiciengine-1.0.3/node_modules/socket.io-parser/index.js:247:12)

Currently we just test QICI Engine on Mac OS X and Windows, you can try QICI Engine on those two stystems, we will look into the issue and test QICI Engine on more platforms, thanks for catching the problem.

What's your Node.js version, https://nodejs.org/api/path.html#path_path_isabsolute_path look like you are using the version without path.isAbsolute(path) method.
http://docs.qiciengine.com/manual/Overview/MacInstall.html
If you already have Node.js installed, please update it to latest version. the Node.js versions that QICI Engine supports are:
Any v0.12.x version before io.js merged with Node.js
Any version higher than v4.1 after io.js merged with Node.js

What's your Node.js version, https://nodejs.org/api/path.html#path_path_isabsolute_path look like you are using the version without path.isAbsolute(path) method.
http://docs.qiciengine.com/manual/Overview/MacInstall.html
If you already have Node.js installed, please update it to latest version. the Node.js versions that QICI Engine supports are:
Any v0.12.x version before io.js merged with Node.js
Any version higher than v4.1 after io.js merged with Node.js

yes that was the problem! thank you!


ignore build files and add the pushbuild command

Build files will be pushed to the dist branch: https://github.com/hotosm/OpenMapKitServer/tree/dist

Awesome!


Fix minifb related performance issues on macOS

The crate minifb has some issues on macOS. Due to that the maximum frame rate that can be achieved is about 50 fps.

Related: https://github.com/emoon/rust_minifb/issues/28

I think we should switch to an OpenGL window (using glium and winit) in the long run:

Probably fixes this issue
We get way more accurate and detailed event information via winit
If we want to implement some kind of upscaling, we could do that via shader which is probably a lot faster

#46 Switched from minifb to pixels which works completely different. So I am pretty sure this issue is solved or outdated.

#46 Switched from minifb to pixels which works completely different. So I am pretty sure this issue is solved or outdated.


Added CoinRequest button

Added a CoinRequest button in the RequestAmountView and ReceiveViewModal.
For an example, please see the screenshot of the RequestAmountView:

LGTM.
Thanks for your contribution!


MREC and Native Ads support missing

Please Add MREC and Native Ads support in CAS-Flutter

Hello, thank you for notification of your issue. Our CAS SDK doesn't support native ads for now but we support MREC banners. You can find more information here https://github.com/cleveradssolutions/CAS-Flutter/wiki/Banner-Ads#ad-size
MREC (MediumRectangle) is a 300x250 banner

@Jedures How can i use them as widget in Container?


Fix 1866

It just made sense to fix this over https://github.com/biocore/qiita/pull/2028 so review/merge that one first.

Coverage decreased (-0.02%) to 91.505% when pulling a8743ff0b271b2cdc2202d75b2b7ccec2de62345 on antgonza:fix-1866 into 103e0e5b336583c020257647547eff46b9b558d0 on biocore:master.

@antgonza can you pull from upstream/master? Thanks!

Changes Unknown when pulling 6baaf66477db3989943e75532b889486ac047594 on antgonza:fix-1866 into ** on biocore:master**.

Just FYI, the pull was done.

I don't really understand the context but I also don't see anything that stands out

Not sure if this will help but this solves: https://github.com/biocore/qiita/issues/1866

Changes Unknown when pulling bcb3c2f9806d6404b46bbd0e20d2b004b151821f on antgonza:fix-1866 into ** on biocore:master**.


Submit blocking USART API to embedded-hal

This crate contains a blocking USART API modelled after this proposal. It should be submitted to embedded-hal.

I've submitted the code here: https://github.com/japaric/embedded-hal/pull/34
There's a WIP pull request to update lpc82x-hal to use the upstream code: https://github.com/braun-robotics/rust-lpc82x-hal/pull/35

The pull request has been merged. Waiting for the next crates.io release of embedded-hal now.


Error: Could not consume all of the output of the current ZipFile

Checks

[X] I have checked that this issue has not already been reported.

[X] I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Reproducible example
✨ Pixi task (default): pip install -r requirements.txt
thread 'tokio-runtime-worker' panicked at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/zip-0.6.6/src/read.rs:1008:25:
Could not consume all of the output of the current ZipFile: Custom { kind: Other, error: reqwest::Error { kind: Body, source: hyper::Error(Body, Error { kind: Reset(StreamId(85), INTERNAL_ERROR, Remote) }) } }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Error: The operation was canceled.

Issue description
In our CI, we've seen Pixi die like this a few times. @ruben-arts encouraged me to file if I saw it happen again.
Expected behavior
I'd expect a Pixi error vs. a Rust panic.

Would it be possible to post your pixi.toml :)?

had the same issue pop up in our CI yesterday, @pavelzw and I just suspected a flaky download.

 pixi.toml
[project]
name = "name"
description = "desc"
channels = ["conda-forge"]
platforms = ["osx-arm64", "osx-64", "linux-64", "linux-aarch64"]

[tasks]
postinstall = "pip install --no-build-isolation --no-deps --disable-pip-version-check -e ."

[dependencies]
python = ">=3.11"
polars = ">=0.19.9"
rich = "*"
scikit-learn = "*"
pandas = "*"
pyarrow = "*"

[host-dependencies]
pip = "*"
setuptools = ">=61"
setuptools-scm = "*"
[feature.docs.dependencies]
make = "*"
numpydoc = "*"
sphinx = "*"
sphinxcontrib-apidoc = "*"
sphinx_rtd_theme = "*"
sphinx-book-theme = ">=1.0"
myst-parser = "*"
[feature.docs.tasks]
docs = "cd docs && make html"

[feature.test.dependencies]
pytest = ">=6,<8"
pytest-cov = "*"
pytest-md = "*"
pytest-emoji = "*"
pytest-lazy-fixture = "*"
mypy = ">=1.8,<1.9"
[feature.test.tasks]
test = "pytest"
mypy = "mypy ."

[feature.lint.dependencies]
pre-commit = "*"
[feature.lint.tasks]
pre-commit-install = "pre-commit install"
pre-commit-run = "pre-commit run -a"

[feature.py311.dependencies]
python = "3.11.*"
[feature.py312.dependencies]
python = "3.12.*"

[environments]
default = ["test"]
py311 = ["py311", "test"]
py312 = ["py312", "test"]
docs = ["docs"]
lint = ["lint"]

I think this has to do with .conda files. They contain an outer zip file, and two .tar.zst files inside.
Maybe we should add a retry handler for downloads if we encounter a failed download like this.

Just got the same issue in pixi. https://github.com/prefix-dev/pixi/actions/runs/7913953885/job/21604215025?pr=804

Unfortunately this is a panic inside of the zip crate. It's slightly tricky to fix from the "outside" - we'll send a patch to zip and see if they accept it https://github.com/prefix-dev/pixi/issues/799

I have a PR in rattler that fixes this issue using a workaround: https://github.com/mamba-org/rattler/pull/535

This should be fixed with the latest rattler (and pixi 0.15.1) release. Please let us know if you see this again, and thanks for filing this bug report!

We just got this issue again unfortunately
Run<EMAIL_ADDRESS>  with:
    cache: false
  env:
    AWS_DEFAULT_REGION: eu-central-1
    AWS_REGION: eu-central-1
    AWS_ACCESS_KEY_ID:
    AWS_SECRET_ACCESS_KEY:
    AWS_SESSION_TOKEN:
Downloading Pixi
  Pixi installed to /home/runner/.pixi/bin/pixi
pixi install --locked
  /home/runner/.pixi/bin/pixi install --locked --manifest-path pixi.toml --color always
  thread 'tokio-runtime-worker' panicked at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/zip-0.6.6/src/read.rs:1008:25:
  Could not consume all of the output of the current ZipFile: Custom { kind: Other, error: reqwest::Error { kind: Body, source: hyper::Error(Body, Error { kind: Reset(StreamId(11), INTERNAL_ERROR, Remote) }) } }
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

We just ran this without specifying pixi-version so this should be pixi 0.15.1

I closed this issue too early. We have not yet updated rattler in pixi.

When is the next pixi version with the updated rattler planned? This is currently blocking some things for us 😓


Add access date to the webpage data model

All engines return a Webpage object when asked to get the source of a page.  Currently that object has only the url and the source of the page, it would be helpful to begin adding some extra meta-data to the object for later analysis and debugging.
When a Webpage object is instantiated, it should populate an instance variable with the current unix time in UTC.  A method should be added to the class to update the access_date to either a certain unix time, or to the current time at that call.
Once implemented, tests should be added for both the Webpage object itself (that the access_date is automatically generated on instantiation, and that it can be updated), and on the engines (that they return Webpages with the expected access dates.

:+1: The headers would also be super useful. This could really pay off for 302s

Working on this


The uploading activity cannot complete when uploading files/folder to one blob container using AzCopy

Storage Explorer Version: 1.9.0
Build: 20190821.3
Platform/OS: Windows 10/ Linux Ubuntu 18.04
Branch: master
Architecture: ia32/x64
Regression From: Previous release
Steps to reproduce:

Make sure AzCopy is enabled.
Open one normal blob container -> Try to upload one file to it.
Check the uploading result.

Expect Experience:
The file can be uploaded successfully.
Actual Experience:
The uploading activities cannot complete.

More info:
This issue also reproduces when uploading files/folder to one ADLS Gen2 container.

This issue has been fixed on the latest build master/20190827.12. So we close it.