TGC Cookie without "Httponly" Flag

CAS server version: <IP_ADDRESS>
Container/environment type/version : tomcat 8 and Java 1.8
Steps to duplicate the problem along with your CAS settings and properties
Stacktraces and CAS logs where appropriate.
Configuration/Overlay pushed to https://github.com/cas-projects/cas-issues/

By default, the TGC cookie does not have the "HttpOnly" flag. If the application (with CAS) had an
XSS vulnerability, someone could inject JS and read the TGC cookie and send it to the CAS server,
even if it is encrypted and signed, the CAS server will not know that this TGC cookie is from an
attacker. Currently I see a security problem. The ideal would be to have a variable that will
configure whether or not to use the "httponly" flag for the TGC cookie.
Thanks you very much.

The CAS server will know and reject the cookie specially because it's signed and encrypted and specially because the cookie is linked to the server.
This is also handled in 505.


feat(checkout): CHECKOUT-0000 Merge prettier auto fixes

What?
Automatic code formatting improvement by prettier.
Why?
These auto fixes constantly show up when we run npm run lint because we never commit them into the repo.
Testing / Proof
CI.
@bigcommerce/checkout

LGTM. Separate question, why aren't these raised as an error in the first place?

@davidchin I think because they are all auto-fixable, and we run npm run lint with --fix.

@bc-peng we should put in something to fail the build if the autofix changes are not committed. This is to prevent similar things from happening again in the future.

@bc-peng correct me if I am wrong, these are fixes that are suggested but we haven't actioned on till now. Since most of the rules are turned off in core repo it could be a reason why the build doesn't fail.

@bc-peng we should put in something to fail the build if the autofix changes are not committed. This is to prevent similar things from happening again in the future.

@davidchin as we will commit all auto fixes in this PR, maybe we can remove --fix from now on.
https://github.com/bigcommerce/checkout-js/blob/d8a6c79870877788bf21ca6ef6bc9e25a56c7df3/package.json#L23

@bc-peng correct me if I am wrong, these are fixes that are suggested but we haven't actioned on till now. Since most of the rules are turned off in core repo it could be a reason why the build doesn't fail.

@animesh1987 Some of them are errors, some are warnings.
If we run npx nx run-many --target=lint --all without --fix on master branch now, the command will fail.


Compile and publish questions from WCAG inspection workshops

What
We haven't been able to answer every question during the WCAG inspection workshops, however we have recorded all questions raised. We want to publish the questions with answers from the team.
Why
So we can bette support the community. We also committed to doing this in the workshops.
Who needs to work on this
Kelly, David
Who needs to review this
TBC
Done when

[ ] Identified most appropriate place to publish questions
[ ] All questions have a written answer
[ ] Content reviewed
[ ] Published
[ ] Shared with attendees

@kellylee-gds would you or someone else be able to take this on?
I don't know where the first workshop's questions are stored, but I have the 2nd and 3rd workshop's questions:

Target size participant questions
Accessible authentication participant questions


await is only valid in async function

Put the code in the readme in a scrap.js file and then run node scrap.js but been getting the error
const profileScraper = await scrapedin({ email<EMAIL_ADDRESS>password: 'pass' })
                       ^^^^^

SyntaxError: await is only valid in async function

How can I bypass this?

https://hackernoon.com/understanding-async-await-in-javascript-1d81bb079b2c

@isbkch you can do
scrapedin({ email<EMAIL_ADDRESS>password: 'pass' })
.then((profileScraper) => {
 //use profile scraper here
})


can't download the ocid and osd

I can't dowdload The Object Clutter Indoor Dataset (OCID) and Object Segmentation Dataset (OSD) from (https://www.acin.tuwien.ac.at/en/vision-for-robotics/software-tools/object-clutter-indoor-dataset/), do someone have the resource? I would greatly appreciate your assistance in obtaining it.

Same issue.

There is an OCID download link on their webpage.

We provide the backup links for OSD: OSD-0.2.zip and OSD-0.2-depth.zip. Please to adhere to the licensing agreements of the official OSD dataset.
After unzipping two files, you may copy files from OSD-0.2 folder to OSD-0.2-depth folder.


Feature request: Backoff the retry when gateway reports RESOURCE_EXHAUSTED

When the broker signals backpressure, the Kafka sink responds with an immediate retry.
See: https://github.com/camunda-community-hub/kafka-connect-zeebe/blob/master/src/main/java/io/zeebe/kafka/connect/sink/ZeebeSinkFuture.java#L76
It should backoff the retry to give the broker a chance to recover.

Great finding (based on https://forum.camunda.io/t/kafka-sink-connector-high-cpu-utilisation/2667/5)!
The biggest question is what strategy to use in case of backpressure 🤔

The easy and obvious one is t = 2 * t. So, 1s, 2s, 4s, 8s, 16s, 32s, 64s ...

Another update: We are looking at it in https://github.com/camunda-community-hub/kafka-connect-zeebe/tree/fm-exponential-backoff

reminder for me: Pile of tasks in memory is no problem because we do not retrieve new tasks before the others are completed at the moment

Waiting for customer to confirm that this solves the issue


npm dependency warning

I've just upgraded to angular 7.0.4 and 6.0.1 and got this npm warning. I have this in my package file
"@markpieszak/ng-application-insights": "^6.0.1"
"@angular/router": "^7.0.4",
this is the warning
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.

Let me create a new version to match with 7.x! Sorry about the delay

Fixed via releasing @markpieszak/ng-application-insights 7.0.0
Hope that helps! Thanks for the heads up 👍


feat: add fastAPI backend generator

(BTW, this is still a WiP since it's missing the ansible part, which i'll complete when we will implement it on our project)


Fix IXFR-out after intermediate update fails verification

This PR is work in progress! Currently it merely adds a test to reproduce faulty behavior reported by an NSD user.

Turns out the problem is not related zone verification, but is actually an issue with handling of IXFRs where consecutive updates are in the same IXFR and RRs added by the former are deleted again by the latter.

Last commit makes the test pass, but the code still needs a little more work.

I've updated the ixfr_store code to set the newserial and oldserial members implicitly, which is more intuitive with the way the code is used in apply_ixfr. I've done the same for the code that creates IXFRs for consistency. I also moved checking for the first RR in apply_ixfr inside the loop. I'd rather have checking for first and second RRs in IXFR outside the loop, but the diff would change too much? Let me know if we want to merge it like this or you want other things changed.


JMS: Responses not properly handled when multiple actions use the same replay queue

It looks like the JMS plugin when used with activeMQ behaves unpredictably, randomnly dropping requests and responses. I've attached a sample test script that will reproduce the issue. What happens is that though the messages are successfully submitted and the responses are successfully dequed the JMS client fails to consistently pass this on to the gatling reporting framework and the tracker simply ticks on waiting to be notified
If all the tasks are commented out of the scenario appart from one then all works fine because only one thread is created. I believe this has something to do with JMS session thread affinity but not certain.
Simulation attached below:
JMSConcurrencyIssue.txt

  private def initExecution(title: String): JmsRequestBuilder = {
    jms(title)
      .reqreply
      .queue("abraham.simulation.in")
      .replyQueue("abraham.simulation.out")
      .textMessage(stringToExpression("Client asking server to: " + title))
      .property("transactionId", java.util.UUID.randomUUID.toString.toUpperCase())
  }

Is it intended that transactionId is static for a given exec type? Are you sure you don't want to pass an Expression instead (one transactionId per message sent)?

Your problem is that all your actions read and write from the same queues.
Trackers keep track of sent ids and are in charge of performing correlation. The thing is there's one tracker per action. But as you have several of them, and they all read from the same queue, there's a very good chance that a given response gets picked up by a different tracker than the one that kept track of the request, hence correlation never happens.

IMO, this is a design issue. There should be only one tracker per replyDestination, or a single one that would use the replyDestination in the tracking key.

Hi Stephane,
Thanks for looking into this. Sounds like a change needs to be made
within the JMS client to ensure that there is one tracker per queue. If
that's so are you able to advise on when a patch might be available?
We'll stand down if that's pretty soon, if not we can take a stab at
fixing it.
rgds
Abraham
Stephane Landelle:

IMO, this is a design issue. There should be only one tracker per replyDestination, or a single one that would use the replyDestination in the tracking key.

Reply to this email directly or view it on GitHub:
https://github.com/gatling/gatling/issues/2913#issuecomment-184353713

Fixed

Brilliant,
Many thanks for the quick turnaround on this one Stephan.

We're keen to integrate with your fix as soon as possible. When will you be in a position to push the changes?

2.2.0 is planned for end of March

Were happy to pull and build a snapshot in the meanwhile if that's ok... just couldn't see the fix in master.

http://gatling.io/#/services

Be glad to start with the "Basic" option and upgrade as necessary if that's sufficient for us to start using this fix today. please advise?

Yes, with Basic would grant you access to the private fixes. Please get in touch at<EMAIL_ADDRESS>and we'll gladly send you an invoice.


How to log Exception.Data

How can I let NLog layout out of the box to log the exception data?
try
{
    var fileNotFoundException = new FileNotFoundException("Can't locate the file");
    fileNotFoundException.Data["FilePath"] = "PATH TO THE FILE";
    fileNotFoundException.Data["UserNmae"] = "MyUserName";
    fileNotFoundException.Data["TimeStamp"] = DateTime.Now.ToString("O");
    throw fileNotFoundException;
}
catch (Exception e)
{
    Logger.Fatal("Unexpected error: " + e.Message, e);
    throw;
}

Your example is good enough and should work. Read about a recommended approach here https://github.com/NLog/NLog/wiki/How-to-log-exceptions

@aturlov this method does not log the [Exception.Data] (https://msdn.microsoft.com/en-us/library/system.exception.data.aspx)

You can also log separate parts of an exception object using different formats with the ${exception} layout renderer like this ${exception:format=Data}. Look here for more information https://github.com/nlog/NLog/wiki/Exception-Layout-Renderer

Thanks @aturlov !

Thank you @aturlov


Accept trade via chatbox notification

Current Behavior
Does not open trade interface
Expected Behavior
Open trade
Steps to Reproduce the Problem

Player 1: Send trade request
Player 2: Attempt to accept trade request by clicking on trade chat notification

This is not related to the server files, is it? I can't realise a way to detect the clicks on a trade notification server sided -> even if one would exist, it's inefficient as it could be done client sided (solely)
Correct me if I'm wrong:
Trading is a right click option, sent from the client
Player 1 right clicks Player 2 and sends a packet to the Server
-> Server receives the packet and finds Player 2 (lets ignore the pre-conditions for the trade request to send)
Now Player 2 has two possibilities in accepting:

Right click -> Trade to accept
Click on the chatbox to accept

How should the server know you're clicking on the chatbox to accept? Exactly! By sending the same packet you'd send when right click -> trade accepting. Client sided.

@YasinY well i dont know much about osrs or how trade works in general but its quite possible that after clicking accept itll send packet to server to let the server know trade was accepted which is obviously important and while it does that it opens up interface server sided. in fact i feel like thats very likely

Yes, and that's what I ment! It'll simply send the identical packet to the server as if you'd have right-click traded.
So this is pretty much out of the range of the server, the server doesn't need to know that the player has clicked the chatbox to accept the trade. Therefore this feature is not "needed" - as it's essentially a client-sided job

It

Yes, and that's what I ment! It'll simply send the identical packet to the server as if you'd have right-click traded.
So this is pretty much out of the range of the server, the server doesn't need to know that the player has clicked the chatbox to accept the trade. Therefore this feature is not "needed" - as it's essentially a client-sided job

It's not client sided. Nothing should ever need to be changed on the client past getting it connected to the server. The server is not sending the player name on chatbox trade request acceptance.

Solved in #119


fix(framework): FunctionInvoker sets the request path

Summary
What's changed?
The FunctionInvoker will now construct a request with a path that matches the one of the incoming event.
Why do we need this?
As of now both local and production function handlers receive an empty path even if the original HTTP request has it. The path is effectively being erased making it hard to reuse standard golang code that needs path-based routing.
How have you tested it?
Wrote a unit test and tested it locally in examples/handler by pointing the framework dependency to a local directory.
Checklist

[x] I have reviewed this myself
[x] There is a unit test covering every change in this PR
[ ] I have updated the relevant documentation

👋  Thank you for adding this missing behaviour and the test 👍
Recently some trouble caused URL paths to do not work in production for some runtimes but fixed it by the way.

No problem, glad that this could help 👍
Do you have a rough estimate on when it will become available on functions that are currently in production?

This is ready in production for runtimes go117, go118, go119, go120.
You can give a try with this sample handler code:
package mypackage

import (
	"encoding/json"
	"net/http"
)

func MyHandler(w http.ResponseWriter, r *http.Request) {
	res, _ := json.Marshal(r.URL)
	w.Write(res)
}

Sounds good, thanks for the update


Dublin DUB

There are multitude of entries in teh Gazetteer for Dublin. Please move the alternatives, together with their search records, to the main entry (source Irish Townlands). Please remove entries that do not follow the greater to smaller rule and move their search records to teh correct entry.
Geoff

Done


DBZ-6188 Allow optional uidList for partitionFunctionKey rule

https://issues.redhat.com/browse/DBZ-6188

@ani-sha Applied, thanks! Could you please create an upstream PR too?

Upstream PR - https://github.com/antlr/grammars-v4/pull/3262


Only one database gets added to database panel if multiple databases are present

Describe the bug
My AppHost project contains more than database on the same PostgreSQL container. Only the first one is accessible from the Database panel.
To Reproduce
var password = builder.AddParameter("DatabasePassword").ExcludeFromManifest();

var database = builder.AddPostgres("postgres", password: password)
    .WithDataVolume("npgsql-experiment");

var dbOne = database.AddDatabase("db1");
var dbTwo = database.AddDatabase("db2");
var dbThree = database.AddDatabase("db3");

Expected behavior
All database should be added to the panel when the application is started.
System information:

OS: Windows
.NET version: 8.0
JetBrains Rider version: 2024.2.3
Aspire plugin version: 1.3.0
Aspire workload version: 8.2.0

@rafaelldi were you able to reproduce this issue?

Here is a simple repro that already shows the behavior, but I'm not sure if this is because the databases are not created yet. If that's the case, I can fix that.
https://github.com/Kralizek/RiderAspireMultipleDatabases

I have three of them:

Having three of them happens 5% of the times (guesstimate)

Thank you for your help! It should be fixed in the next release #283

I gave a quick look at the PR for curiosity. Now, my Kotlin knowledge amounts to the time I've been looking at your PR, but it feels weird it even showed more than one database at all.
Or am I blind to something in the previous code?

There was a race. It depended on the order in which resources and connection strings came to us. Even if three connection strings had already arrived, we always chose one. But if they came one by one, everything was fine.


Populate advisory state for RedHat OVALv2 data

This is a fairly simple PR to add support for ingesting the "State" of an advisory for Red Hat, populated from the OVALv2 data which is already being ingested.
If an advisory (RHSA or CVE) defines a resolution state, such as "Out of support scope" or "Will not fix", then this data will be ingested into the "Red Hat" advisory bucket for the existing advisory entry under the "State" key, part of the existing object schema for advisories.
I have also added a test to ensure this is properly ingested for CVE-2020-11879, a vulnerability which has no Red Hat errata (no RHSA) as it is designated "Will not fix" by Red Hat.
This data is incredibly useful for folks who are using trivy-db in other projects, and I could imagine it would be useful for adding additional data to Trivy container scans as well - however I have not added any functionality to Trivy at this stage to make direct use of this field.

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

Hello @knqyf263 - would you kindly be able to look at this? It is a very small change, I do not believe it will impact anything downstream. I'd really like to avoid maintaining a fork of the trivy-db repository if possible to be able to reference the Red Hat errata status. Thank you!

I've just added one other small fix to the mergeAdvisories function to make sure that advisories for packages with different fix status do not get merged together, the existing behaviour was clobbering fix states. I've updated the merge functionality to treat state like fixVersion when it comes to merging, and this fixed a few edge cases parsing advisories such as CVE-2021-35937 where the packages have different fix states by package name and affected CPE.

Thanks for creating this @jhebden-gl, it would be great to have access to the state data!
@knqyf263 any chance you can take a look at this please? Thanks!

Hi, @krol3. 👋🏽
Would you be able to help us find someone to review this PR? The author is a colleague of mine at GitLab.

Hello @itaysk 👋🏻 Apologies for the direct ping, I was wondering if you could help to find someone who might be able to review this MR? It should be a relatively simple change & I have added tests to cover the modifications.

We're sorry to be late. It looks good, but I'm feeling like string is too flexible for State. What if defining type State string or type State int like enum? We can merge this PR and start this implementation in another PR.

No problem, thank you for reviewing!
I do agree setting known/acceptable values for State would be a sensible iteration to make on the implementation - State however was already present in the schema and I think it would be good to approach changing the type in a supplementary PR. This way the potential uses of this field could be audited and then the State enum/int could be properly defined to include all possible states used by different vulnerability sources - what do you think? I could see this being useful for other vulnerability advisory sources also.

Thanks. I'll merge this PR, then. I just wanted to warn you that the type might change shortly. If you depend on this field, it would be breaking compatibility.

This way the potential uses of this field could be audited

On the trivy side, this field is not used. We added that for future use.

Thanks. I'll merge this PR, then. I just wanted to warn you that the type might change shortly. If you depend on this field, it would be breaking compatibility.

Thank you - I'll definitely watch out for changes to this field & update accordingly. At the moment we use it in some automation but might extend our usage further. I'll add some more tests to our code to make sure the value is the expected format so I can catch the change.

On the trivy side, this field is not used. We added that for future use.

That's really helpful to know, thank you!

Hello @jhebden-gl
I tested these changes and found one case:
I scanned centos image with 2 DBs and got different results:
db from your branch:
centos (centos 8.4.2105)
Total: 465 (UNKNOWN: 0, LOW: 168, MEDIUM: 269, HIGH: 28, CRITICAL: 0)

db from main branch:
centos (centos 8.4.2105)
Total: 465 (UNKNOWN: 0, LOW: 165, MEDIUM: 272, HIGH: 28, CRITICAL: 0)

CVE-2020-21674 (libarchive), CVE-2021-3997(systemd) and CVE-2021-3997(systemd-libs) have different severity.
I am looking into this issue. I'll write to you when I get more information.

Hello @jhebden-gl I tested these changes and found one case:
<...snip...>
I am looking into this issue. I'll write to you when I get more information.

Hello @DmitriyLewen - thank you for testing out these changes. One thing I suspect might be happening, is that the merging code for advisories had to be updated so that the State field was considered as a point of difference between otherwise similar advisories. I'm not 100% sure, but it is possible some advisories were being merged previously which perhaps should not have been merged. Perhaps severity also needs to be added as a point of difference between advisories when merging entries? Comparing the advisories for severity during this merging process might give some clue as to what has changed. I'll also look at this tomorrow to see if I can spot anything.

@jhebden-gl @DmitriyLewen Thanks for your investigation! It reminds me of a known issue.
https://github.com/aquasecurity/trivy/issues/749#issuecomment-775055450
It seems like Red Hat finally added different severities according to platforms (I'm not sure when it happened, though). It would be great to support platform severities in another PR.


scipy.signal.convolve is slower when vectorized

This is a crosspost from https://stackoverflow.com/a/54790908/1214547.
The following code (which uses Python for loop)
C = np.stack([
    scipy.signal.convolve(
        A[i, :, :],
        B,
        mode='same'
    )
    for i in range(N)
], axis=0)

is significantly faster than a vectorized version:
C = scipy.signal.convolve(
    A,
    B[np.newaxis, ...],
    mode='same'
)

Reproducing code example:
The following is supposed to be run in a Jupyter notebook, as it uses the %timeit magic:
import numpy as np
import scipy.signal

import pandas as pd
import seaborn as sns

H, W = 84, 84
h, w = 13, 13

def benchmark(N):
    A = np.random.normal(size=(N, H, W))
    B = np.random.normal(size=(h, w))

    t1 = %timeit -qo np.stack([scipy.signal.convolve(A[i, :, :], B, mode='same') for i in range(N)])
    t2 = %timeit -qo scipy.signal.convolve(A, B[np.newaxis, ...], mode='same')

    return t1.timings, t2.timings

Ns = (10**np.linspace(1, 4, 16)).round().astype(int)

results = [benchmark(N) for N in Ns]

ns = []
timings = []
run_type = []

for N, (t1_timings, t2_timings) in zip(Ns, results):
    cnt = len(t1_timings)
    ns.extend([N] * cnt)
    timings.extend(t1_timings)
    run_type.extend(['stack'] * cnt)

    cnt = len(t2_timings)
    ns.extend([N] * cnt)
    timings.extend(t2_timings)
    run_type.extend(['vectorized'] * cnt)

df = pd.DataFrame({'N': ns, 'timings': timings, 'type': run_type})
sns.lineplot(x='N', y='timings', hue='type', data=df)

Scipy/Numpy/Python version information:
>>> import sys, scipy, numpy; print(scipy.__version__, numpy.__version__, sys.version_info)
1.2.1 1.16.1 sys.version_info(major=3, minor=7, micro=2, releaselevel='final', serial=0)

I'm not sure if it was #10517 and #10518 in particular, but on my machine, the code above results in vectorized calls winning now.

I get this on current master, doesn't seem fixed:

bumping the milestone, just a minor performance issue - shouldn't be blocking

For me it does appear fixed:

I'll close since we have two reports showing vectorized is better, and one (@rgommers) showing it was even at least roughly even, but we can reopen if need be

Here is what I am getting now:

Versions:
>>> import sys, scipy, numpy; print(scipy.__version__, numpy.__version__, sys.version_info)
1.4.1 1.18.4 sys.version_info(major=3, minor=8, micro=2, releaselevel='final', serial=0)

So yeah, probably fixed.


Change symengine requirement to >= instead of ==

Before:
symengine==0.4.0 meant it was not possible to use this library in Python 3.8
Now:
symengine>=0.4.0 means symengine is not keeping this library out of Python 3.8
closes #19

Thank you!


Added missing meta files for FishNet integration

Generated the two missing meta files for the FishNet integration so that it works when installed via the Unity Package Manager

Thanks @SimplicisMirificus! It seems we forgot to push these two :)


how to redrew the chart with options.data.table=domTable

when domTable changed , how to redrew the chart ?
here is my code :
http://admin.koooke.com/systemManage/statistics.aspx
thank you so much !

In general to force refresh the chart just set/increment a dummy variable in the chart options,


Make secret vaults not require use of PowerShell

Summary of the new feature / enhancement
Along with https://github.com/PowerShell/SecretManagement/issues/211 we should make it so that vault authors don't need to use PowerShell at all so this library becomes the abstraction layer for .NET secrets
Proposed technical implementation details (optional)
No response

The only command that doesn't use built-in types is Get-SecretInfo.
The current 0.9.3 version of the nuget package appears to have all the current surface area (metadata being the big one)
https://www.nuget.org/packages/Microsoft.PowerShell.SecretManagement.Library/0.9.1
So it probably just needs to be republished/updated to 1.1.2 and have vault authors instructed to use it with PrivateAssets=true


Add tests and report coverage

@astagi i tried to add back the test but unfortunately it is based on a conversion to local date, so it depends on time zone on the machine where the build is run
On my local machine the test is passing correctly
Maybe it is better to remove it, otherwise i will think about a way to refactor it, if you have any suggestion please let me know
Thank you.

@astagi i tried to add back the test but unfortunately it is based on a conversion to local date, so it depends on time zone on the machine where the build is run
On my local machine the test is passing correctly
I tried a couple of fixes but it seems to fail in any case, the expected time on your machine is 11:03 while on my local machine the test passes with 13:03
Maybe it is better to remove it, otherwise i will think about a way to refactor it, if you have any suggestion please let me know
Thank you.

@Light2288 I tried to force timezone in gradlew script and it works https://github.com/ministero-salute/it-dgc-verificaC19-android/pull/46 WDYT? Better setting it before launching the command?

@astagi i tried to add back the test but unfortunately it is based on a conversion to local date, so it depends on time zone on the machine where the build is run
On my local machine the test is passing correctly
I tried a couple of fixes but it seems to fail in any case, the expected time on your machine is 11:03 while on my local machine the test passes with 13:03
Maybe it is better to remove it, otherwise i will think about a way to refactor it, if you have any suggestion please let me know
Thank you.

@Light2288 I tried to force timezone in gradlew script and it works #46 WDYT? Better setting it before launching the command?

I was thinking if there was some alternative in order to not change this gradle (even if I don't think it has other impacts) , but the conversion to LocalDate made all my tied fixes to fail
I approved #46, i will keep you updated if I find some way to implement everything test side
Thank you

@astagi i tried to add back the test but unfortunately it is based on a conversion to local date, so it depends on time zone on the machine where the build is run
On my local machine the test is passing correctly
I tried a couple of fixes but it seems to fail in any case, the expected time on your machine is 11:03 while on my local machine the test passes with 13:03
Maybe it is better to remove it, otherwise i will think about a way to refactor it, if you have any suggestion please let me know
Thank you.

@Light2288 I tried to force timezone in gradlew script and it works #46 WDYT? Better setting it before launching the command?

I was thinking if there was some alternative in order to not change this gradle (even if I don't think it has other impacts) , but the conversion to LocalDate made all my tied fixes to fail
I approved #46, i will keep you updated if I find some way to implement everything test side
Thank you

Sure! Thank you!


Nested repeats

repeat(repeat(random(0,1),3),2) produces
[[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]]
see
git://gist.github.com/1754754.git

This was just a display issue - the list was being generated properly but not converted to a string sensibly. I've fixed it, but I can't see why you'd want to do what you're doing.


Hard-coded wlan0 interface in device configure modal

Hello,
When I open the device configure modal, to display wifi informations, waveforms send a nicGetStatus request for wlan0 adpater regardless to nicList content.

Hi,
I've looked at the issues you opened. Are you trying to add WFL support for a new device?

Are you trying to add WFL support for a new device?

Yes, I opened those issues mainly for reference. It’s not critic.


Thinkpad 13 gen 1 patches?

Hi, i can't find the thinkpad 13 gen 1, sorry if this a stupid issue but i'm not sure where which patches would work for this laptop.

Use what is appropriate for that generation. Eg xx80 patches if it's a 2017 300 series chipset.


Use path in node_modules to run tsc.

The Makefile used to assume that tsc was on the current path which is not
always true. This change modifies the Makefile to use the tsc script under
the node_modules folder.

Thanks , this got missed by us.


How to access scope / token?

Looking at https://github.com/jaredhanson/oauth2orize/blob/master/examples/all-grants/oauth2.js
The one part that I'm particularly unclear on is that although I see a scope variable in the example code, I don't understand where it gets parsed or passed or where I would store it to a) present it as part of the permission dialog and b) access it later.
I also see that the token is saved (which seems an ideal place to store the scope), but I don't see any place where it is read.

The discussion has been had, the pull request is in. Closing this since the pull requests links to it.


fix: allow certHash to contain upper or lower case characters

Description:
Allow certHash to contain upper or lower case characters
Related issue(s):
Fixes #1904

@matteriben can you share more details what is the purpose of this change? Is ti a chore or is ti actually a fix?

@matteriben can you share more details what is the purpose of this change?

I think its more correct to ignore the case when comparing hex strings, but it's not causing any problem for me.

Closing since it's not mandatory change.


Solar + wind's build cost and expected output should reflect local weather forecast

It's currently based on a single hardcoded capacity factor, obviously not correct

DONE: Update solar output calculation in updateSupplyFacilitiesFinances in Game.tsx to account for lat/long (add lat/long to LOCATIONS in constants) AND month of year...
Build facilities menu should reflect full output calculation (incl weather and lat long) in average output and $/MWh for wind + solar

For simplicity in determining "average output", can use the weather for the full upcoming year as a model year, e.g. don't need to simulate/forecast every year of service life uniquely

Perhaps "capacity factor" is the best way to estimate this
Thought: How much would I expect the climate to meaningfully change in a way that would impact solar/wind capacity factor? Uhhh, without getting into complex climate change modeling, minimally... so, then, I could argue that capacity factor could just be locally-calculated once
Which would also work well since that particular logic of generating facilities isn't used much - only in BuildFacilities and InitGame, so it's ok if it works a bit to actually forecast out.
So, basically, expand the export function GENERATORS in Facilities.tsx to take in (location? weather?) and calculate custom capacity factors for solar and wind — and then, of course, verify that the updates flow through and make sense.
For the record, existing values on master when starting SF 2020 scenario, 200MW:
wind: 62MW/year, $27.4/mwh
solar: 44MW/year, $25.1/mwh


Added test whether unicode is known, see issue 74 for details

Hi, i had an attempt at solving issue #74. I am happy to change the code if you prefer a different solution.

I understand this has also been addressed in pull request 66 in an alternative approach.

Thanks for closing https://github.com/mantl/terraform.py/pull/75 @Cryptophobia! Please could you also merge this PR (once conflicts are resolved by @mjuenema) so terraform.py works with python 3?

Sure, @mjuenema do you want to resolve this so I can get it merged?


Can we get rid of IBackupService.hasTextFileBackup?

I see we only use it to find out if we should load a backup from disk when opening a file. Can we not just always try to load the backup and handle the error case? That should save us 1 IO operation.

It changes in one of my open PRs to hasBackup as it's used for untitled files. Wouldn't that throw a lot of exceptions which are expensive as it's triggered whenever files are opened?

@Tyriar I would bet that any exception is less expensive than talking to a disk. And it will only be one error that will be thrown from here I think: https://github.com/Microsoft/vscode/blob/master/src/vs/base/node/stream.ts#L50
Because the very first call of resolveContent is mime.detectMimesFromFile in https://github.com/Microsoft/vscode/blob/master/src/vs/workbench/services/files/node/fileService.ts#L164

If that's the preferred way when the typical case is it failing  :+1:

Let's not move on this until https://github.com/Microsoft/vscode/issues/14186 is done

@Tyriar actually maybe there is a better solution that could prevent us from always checking for a backup. What I am mainly interested in is to not having to ALWAYS check for backups each time you open a file. Because there is really only 1 time when a backup can be present: That is the very FIRST time you open a file (or am I wrong?).
It seems odd to check for backups all the time when we know it can only be after initial startup. I know for this particular reason you added the restoreResource and I did not like it. But the concept was good, I think it can be achieved without the need for restoreResource.

The original intent was to only ever check for backups on launch as you say using restoreResource, and yes on launch is the only case we care about. So currently backups could theoretically restore in the middle of a session if a backup file doesn't get cleaned up somehow from a previous session (bug) or if it does not get persisted to the workspace state in local storage (crash).


Test server should treat update/poll-update as long-poll

Expected Behavior
Start/poll update long poll timeout should return empty response. This could be updated to just match the get-history call which is hardcoded to 20s or could just be set to 10s before the user-set deadline.
Actual Behavior
Seems at first glance that a timeout exception may occur.

This may relate to https://github.com/temporalio/sdk-java/issues/1903


0.3.40 cannot run on Windows Vista as expected

TravelCam is not effecting, and no any notifications. Exited sliently.
Cheat mode also. Only F1 and F2 work.

0.3.37 has no these problems.

反正就是Vista只能用0.3.37，听说现在也不是原作者负责维护了


Dependencies version validations may be misleading

Let's say you are developing an EVM package and publish a version 1.0.0, but then you noticed that there was a problem with something that has nothing to do with the contracts you are providing, e.g. fixing a deployment script or adding a file that was npm-ignored or so. Then, you will have to bump your package.json and publish again. This will make your package.json and zos.json to get unsynched, which means that people trying to link your package as zos link<EMAIL_ADDRESS>will fail saying you requested version 1.0.1 but the one in its zos.json is 1.0.0, and the way to circumvent this is to link it using a semver as zos link<EMAIL_ADDRESS>Which should be the expected behaviour in this kind of scenario? Should we expect the users to bump their zOS project too? What can be improved from the CLI to avoid users publishing unsynched versions of package.json and zos.json files?

Closing in favour of https://github.com/zeppelinos/zos/issues/308


framework-agnostic

Hello there! THANKS for this awesome project. is it possible for alva to be framework agnostic?
react-native or angular?

Hey @pouyamiralayi – for the moment we only support React. We might explore other frameworks in the future, but for now we are going for better React support. It should be possible to wrap WebComponents in React components to support them in Alva, but this might not be possible with Angular.


Data Portal on home page has incorrect link

Expected: The link to the data portal found:

should direct to data.codefordc.org
What actually happens:
User is directed www.data.codefordc.org

Link to http://www.data.codefordc.org/ on home page is now returning an error for me.

This site can’t be reached www.data.codefordc.org’s server IP address could not be found.
Search Google for data codeforce org
ERR_NAME_NOT_RESOLVED

Should be fixed via this commit: https://github.com/codefordc/codefordc.github.com/commit/78aa975da666c85231af3fdc358cc5d9d8768c8e
(May take a few minutes to go up on the live site)


MeiliSearchApiError. Error code: database_size_limit_reached.

With all of my respect to the great work that has been done on this project, issue that I want to report has been already reported multiple times and I find it quiet dumb that it still exists, compared to the great work that has already been done. I also think it requires immediate fix as if somebody wants to use this for serious amounts of load, than it is really not yet ready for it. However I see great potential of this engine becoming the best search engine in a very near future, but for that to happen it must be ready for the big data!
We have a lot of changing data that is being re-indexed on a daily basis. Our first honey moon with meilisearch went perfect in every possible way, however few days ago she got completely stuck without any warning and now it seems that the only way to fix this is to dump our entire data folder and start our relationships all over again (which we already did yesterday and got in to the same issue again).
So now whenever we try to pass any new task to her, she is throwing this error:
"MeiliSearchApiError: MeiliSearchApiError. Error code: database_size_limit_reached. Error message: MDB_MAP_FULL: Environment mapsize limit reached Error documentation: https://docs.meilisearch.com/errors#database_size_limit_reached Error type: internal"
Since we started all over again by deleting our old indexes, new indexes are not that big yet, takes up ~900 Mb in total.
However I have figured out that tasks folder is at 10GB as it got a lot of tasks to do over the first month of use (all in batches). If I get it correctly all of those tasks are successfully executed, however they are still there, taking up the space, but most importantly it got reached some hard coded 10GB limit (where do we change that limit?). So we have learned the hard way that we must do tasks cleanup ourselves.... that's not really a problem, but if this is the way it works it should be documented on installation and use documentation in red bold text!
Ok, so we got stuck... well let's try and clear some of those tasks up... We use Python, therefore we do:
ms_client.delete_tasks(parameters={'statuses': ['succeeded']})
Good try! Same error! It wont accept a single new task even if it's dedicated to clean her self up... So now how do we go about this? Is there any setting that we can change to increase that 10GB limit?
Now... quick suggestion for an easy fix: Having a limit on tasks queue is a good idea, however users should have an option of changing how much space it takes up (10Gb is a good default value), but most importantly, this task queue should clean it self up on a very regular basis, so that instead of throwing an error it should drop oldest tasks to make up a space for new ones.

Hello @Simanas. Sorry for the inconvenience. What version of meilisearch are you using? In the older version of the engine, reaching the maximum size (10GB) for the task database is indeed the case. However, we have addressed this problem in the latest version by introducing an automatic task deletion feature, as mentioned on the release page.
To resolve the issue and unblock the situation, as far as I know, I am afraid you will need to start fresh since it does not take any tasks into the queue to free up the needed space.
cc @meilisearch/engine-team, perhaps they have alternative suggestions to help unblock it.

O wow! Yes we are on v1.0.2.
These improvements mentioned on v1.2.0 release page really hits the eyeball! Great work guys! Closing the issue and moving up to v1.2.0! :) Sorry for not finding this out by my self. However this might help some other lost older version users to find the proper answer! :)
Brilliant work that you do here! Thank you and bless you all!


Intermittent issues with volumes loading for W1KG26281

Checking https://library.bdrc.io/show/bdr:W1KG26281 occasionally results in certain volumes failing to load, showing as "loading manifest..." in the IIIF viewer and staying stuck there.  Sometimes by refreshing the page the issue will go away completely, or other volumes will exhibit the issue.

probably the same as #76


npm install fails: 'TS2349: This expression is not callable'

Version:

0.33.0

Platform:

Linux trout-dev 5.11.0-34-generic #36~20.04.1-Ubuntu SMP Fri Aug 27 08:06:32 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Subsystem:

N/A
Severity:

High
Description:

Trying to install the master branch (commit a335fda) as well as the latest release (v0.33.0) commit, both fail on npm install
Node version: v14.17.6
npm version: 7.23.0
OS: Ubuntu 20.4
Steps to reproduce the error:

git clone the repository.
(optional) git checkout v0.33.0
Run npm install and notice the following error:

npm ERR! code 1
npm ERR! path /home/trout/tmp/js-libp2p
npm ERR! command failed
npm ERR! command sh -c aegir build --no-bundle
npm ERR! [06:03:45] Clean ./dist [started]
npm ERR! [06:03:45] Clean ./dist [completed]
npm ERR! [06:03:45] Generate types [started]
npm ERR! src/nat-manager.js(118,11): error TS2349: This expression is not callable.
npm ERR!   Type 'typeof import("/home/trout/tmp/js-libp2p/node_modules/private-ip/lib/index")' has no call signatures.
npm ERR! [06:03:55] Generate types [failed]
npm ERR! [06:03:55] → Command failed with exit code 1: tsc --build /home/trout/tmp/js-libp2p/tsconfig-types.aegir.json
npm ERR! Command failed with exit code 1: tsc --build /home/trout/tmp/js-libp2p/tsconfig-types.aegir.json

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/trout/.npm/_logs/2021-11-10T14_04_00_258Z-debug.log

Thanks for reporting this @christroutner
Likely some dependency creating this issue. I will get it fixed today

Temporarily added a ts ignore on our end until private-ip module gets fixed


[DCOS-57064] Bump DC/OS Signal

High-level description
What features does this change enable? What bugs does this change fix?
This PR bumps DC/OS Signal to the latest version. Also, we now always provide the licensing socket to use since this package is also used for DC/OS Enterprise. When the socket doesn't exist, a warning is logged but that doesn't harm the functionality of Signal.
Corresponding DC/OS tickets (required)

DCOS-57064 Bump signal in dcos and remove it from dcos-enterprise

Related tickets (optional)

DCOS-ID JIRA title / short description.

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[x] Change log from the last version integrated (this should be a link to commits for easy verification and review): changes
[x] Included a test which will fail if code is reverted but test is not. If there is no test please explain.
[] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

can an owner pls run
@mesosphere-mergebot override-status teamcity/dcos/test/terraform/aws/onprem/static/group1 https://jira.mesosphere.com/browse/DCOS-51211

Very much appreciated!

@mesosphere-mergebot override-status teamcity/dcos/test/terraform/aws/onprem/static/group1 https://jira.mesosphere.com/browse/DCOS-51211

@jgehrcke Please don't apply overrides for DCOS-51211. As I responded in the ticket:

Hi [~adamdangoor], it looks like the build was cancelled by the restarter script and triggered again.
If you click into the build you can see that it is marked "cancelled":
Canceled by build-restarter with comment: canceled due to Terraform SSH failures (DCOS-54805)
And then it was re-run automatically which succeeded: https://teamcity.mesosphere.io/viewLog.html?buildId=2096503&tab=buildResultsDiv&buildTypeId=DcOs_Open_Test_IntegrationTest_AwsOnpremWStaticBackendGroup1TerraformSpotBlock&logTab=
Commented by build-restarter 5 hours ago: restarted due to Terraform SSH failures (DCOS-54805)
We restart the build as I'm not sure how we can debug this further when the instances do not even have SSH start.

I recognize the brief flash of red is annoying on a PR, but they get automatically retried and we are aware of the ticket as it is open. This PR specifically introduces new flaky tests that were ignored because this override was applied:

https://teamcity.mesosphere.io/viewLog.html?buildId=2124926&tab=buildResultsDiv&buildTypeId=DcOs_Open_Test_IntegrationTest_AwsOnpremWStaticBackendGroup1TerraformSpotBlock&logTab=
https://teamcity.mesosphere.io/viewLog.html?buildId=2125304&buildTypeId=DcOs_Enterprise_Test_Inte_AwsOnpremWStaticBackendAndSecurityStrictGroup3Terraf_2&tab=buildResultsDiv

Can we please be reasonable about what overrides we are applying?
cc @cgawron1  @orsenthil

@mesosphere-mergebot request-review @janisz @drewvanstone

I'd prefer to have a single service

I haven't found a way to do this. Timers don't have any conditionals.

@mesosphere-mergebot changelog-not-required no user-facing changes, only better repo org.


The FIR filtering seems to not work with Complex32 signals

I have tried to implement a 2-FSK transmitter using the FutureSDK pieces (+ a VCO of my own), but whatever I try I cannot get a clean signal output.

Please check out the code here https://github.com/MarSik/debug-futuresdr-fsk-filtering/tree/no-filtering-issue
The debug outputs all show proper modulation at +/- 45 kHz, but the harmonics are still there. Comparing the output pre-filtering and post-filtering shows no difference.
The filter (140 kHz low pass with 50 kHz transition bw) I use:
let roofing_filter_taps = futuredsp::firdes::kaiser::lowpass::<f32>(140e3_f64 / SAMPLE_RATE, 50e3_f64 / SAMPLE_RATE, 0.01);
    let roofing_filter = FirBuilder::new::<Complex32, Complex32, f32, Vec<f32>>(roofing_filter_taps);

Sampling rate is 8 MHz.
I might be doing something wrong, but I can't figure out what that is.
The same approach (VCO + low pass filter) works just fine in GNURadio.

Hi, I spent some time looking into this problem.
In the end, I realized that Inspectrum treats the ".c32" extension as signed integer samples.
You get comparable results if you use ".cf32" :-)
See more here: https://github.com/miek/inspectrum
Note, however, that there can be some differences in the outputs produced by FutureSDR and GNU Radio, since the filter taps are generated using different techniques.

Oh, .. thank you very much for figuring that out. I totally missed that part of the inspectrum README. I did not want to transmit noise to the air.

Thanks a lot once more, all seems to work as it should indeed.


Changed µ to u in BumbleBench.java

Compiling with µ gives unmappable character for encoding ASCII error
Issue not happening on all systems
Issue spotted on a docker image downloaded from openj9 with jdk11
Signed-off-by: samasri<EMAIL_ADDRESS>

The character is only used to display the unit of time, i.e. microseconds so changing it is fine.


inconsistent documentation with respect to code, for margin top/right/bottom/left

](url)
Hi everyone,
I had been using tachyons for a while, and i have encountered this issue-
mt3=1rem -true
mt4!=2rem instead it is 1.5 rem, i have attached the screenshot code for the same above.,
the scale grows with 0.5 rem at a time(which i feel is actually better than the current scale), but i do not understand why is that happening.

Every "mt" have the double that the previous "mt"


Add missing TINYINT to MonetTypeCompiler

Add missing TINYINT to the Type Compiler and add a test.

Test failures on sqlalchemy 1.2 look to be due to new tests added upstream by sqlalchemy that were previously failing and are unrelated to this change.

thanks! good work


--with-separate-debug-dir="$PREFIX/lib/debug:/usr/lib/debug"

Hi @isuruf, @gqmelo, @msarahan, @nehaljwani, @jjhelmus, @conda-forge/core
It would be nice if AD could provide GDB (someone ran into trouble using, I guess, their system GDB recently on the Anaconda Community mailing list).
I think we may want to align the subject line with:
https://github.com/AnacondaRecipes/aggregate/blob/master/ctng-compilers-activation-feedstock/recipe/activate-gcc.sh#L87

CFLAGS_USED=" .. -fdebug-prefix-map=\${SRC_DIR}=/usr/local/src/conda/\${PKG_NAME}-\${PKG_VERSION} -fdebug-prefix-map=\${PREFIX}=/usr/local/src/conda-prefix"

My plan was to modify (I think it exists, never tried it!) conda-debug so you can pass it a package tarball or a package name in the current env and it unpacks the source code, applies patches and launches gdb (optionally).
I selected /usr/local/src but some have stated a preference for /opt/conda/src or something like that. The problem as I see it is that we don't really want a path that's in the prefix, as that would risk serious clobbering opportunities. Also, I am not really confident that we can do binary prefix replacement inside some (seperated by now, hopefully) debug information, therefore I think a fixed path is safer and easier (yes, gdb can remap source paths but it's a pain in the you know what and debugging needs to be as easy as we can make it .. I am willing to cencede that requiring things to get put in an absolute path isn't going to be possible for everyone, on that point could/should we use /tmp/conda/src instead?)
Also, we need to be packaging bin/pythonX.X-gdb.py in our python builds.

Hi @mingwandroid,
It would be great to have an out-of-the-box debugging solution.
Initially I set --with-separate-debug-dir this way just because I wanted to add /usr/lib/debug, which is the path used by most Linux distros. This made it possible to use conda-forge's gdb to debug system's python. Sometimes this may be desirable when you are working on an old system or where you can't install gdb system-wise. And $PREFIX/lib/debug was added just because it is gdb's default when --with-separate-debug-dir is not given.
So I think it would be good to keep both paths, but I totally agree with adding other ones that can be used to unpack conda sources.
But if you don't want to remap source paths in gdb, you have to always build packages in one of the paths you mentioned (/usr/local/src or /opt/conda/src), right? Do you plan to change the build path (in the docker image, for example)?

No we use debug-prefix remapping. This is specifically to avoid the issue with build paths being somewhat random.
I'm not sure which way to go, /opt/conda/src is my new preferred directory for this remap.. I do want a great debugging experience fwiw!


tsconfck module cannot be found

Describe the bug
tsconfck as a module cannot be found for some reason.
Originally discovered when this workflow started failing in one of our repos: https://github.com/mitre/saf_action/actions/runs/7285825454/job/19853410684.  The specific issue there was that jest started segfaulting.  Tracing the code showed that the crash occurred when trying to dynamically import tsconfck here.
I originally thought that the issue might have had something to do with using dynamic imports, so I tried to statically import the library using the following patch:

patch to src/util/fs.ts

diff --git a/src/util/fs.ts b/src/util/fs.ts
index 0e09e7c..3b5022f 100644
--- a/src/util/fs.ts
+++ b/src/util/fs.ts
@@ -1,6 +1,7 @@
 import {Stats, existsSync as fsExistsSync, readFileSync} from 'node:fs'
 import {readFile, stat} from 'node:fs/promises'
 import {join} from 'node:path'
+import {parse as tsparse} from 'tsconfck'

 import {mergeNestedObjects} from './util'

@@ -73,8 +74,7 @@ export function existsSync(path: string): boolean {
 }

 export async function readTSConfig(path: string) {
-  const {parse} = await import('tsconfck')
-  const result = await parse(path)
+  const result = await tsparse(path)
   const tsNodeOpts = mergeNestedObjects(result.extended ?? [result], 'tsconfig.ts-node')
   return {...result.tsconfig, 'ts-node': tsNodeOpts}
 }

When trying to build the project, it gave the following error: Cannot find module 'tsconfck' or its corresponding type declarations..

Full `yarn pack` output

$ yarn pack
yarn pack v1.22.21
$ yarn run build
yarn run v1.22.21
$ shx rm -rf lib && tsc
src/util/fs.ts:4:32 - error TS2307: Cannot find module 'tsconfck' or its corresponding type declarations.

4 import {parse as tsparse} from 'tsconfck'
                                 ~~~~~~~~~~

Found 1 error in src/util/fs.ts:4

error Command failed with exit code 2.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 2.
info Visit https://yarnpkg.com/en/docs/cli/pack for documentation about this command.

Presumably this inability to resolve the module is also occurring when we try to do the dynamic import in the original code.
To Reproduce
Steps to reproduce the behavior:
Variant 1:

Apply the patch provided above to the repo.
Run yarn pack

Variant 2:

Run npx ts-node in a clone of oclif/core after having run yarn install --frozen-lockfile.
Sanity test by running import {basename, dirname, join} from 'node:path' to see that you can import modules.
Run import {parse} from 'tsconfck' and see it error out.

ts-node output

$ npx ts-node
> import {basename, dirname, join} from 'node:path'
undefined
> import {parse} from 'tsconfck'
<repl>.ts:5:21 - error TS2307: Cannot find module 'tsconfck' or its corresponding type declarations.

5 import {parse} from 'tsconfck'

Expected behavior
The library should be able to be found.
Environment (please complete the following information):

OS & version: MacOS Venture 13.6.3
Shell/terminal & version:  bash-5.2.21
Node version: 18.18.2
Yarn version: 1.22.21

Additional context
Looks like folks are having other problems with tsconfck as well: https://github.com/oclif/core/issues/878.
Looks like tsconfck removed support for cjs exports: https://github.com/dominikg/tsconfck/releases/tag/tsconfck%403.0.0

@Amndeep7 Do you have any logs or stack traces that the indicate the dynamic import of tsconfck is the issue? I'm leaning towards this being specific to jest and/or your testing setup
Regardless, we're working on removing the tsconfck dependency so this may not be an issue for you anymore in a couple of weeks

@mdonnalley I believe the issue is with trying to import tsconfck at all.  It fails during both static and dynamic imports as detailed above.  In any case, it being removed as a dependency should ideally resolve the issue.


fix: fixed workflow pnpm version

#238  👈
develop

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @bob-obringer and the rest of your teammates on  Graphite


Add sensor setting: Unclaim ownership

On sensor settings page:
When a use has claimed the ownership of a sensor, menu shouldn't change. User should be able to see the subpage.
On subpage the button should change from "Claim ownership" to "Unclaim ownership".

Already implemented

Similar subpage as in Force Claim but when ownership is assigned to signed in account then
Show arrow on Owner field after email address
Tap on arrow to forward to Unclaim page

QA passed


Add base deps to pub.yml

Update environment instructions in warehouse.md
Replace yaml with pyyaml

Hey @TonyB9000, this PR should fix the warehouse_pub missing Python imports.
Can you checkout this branch and try the publishing operation to make sure no other dependencies are missing?
Here are the commands to follow:
cd esgfpub
git fetch
git checkout devops/pub-env-deps
conda env create -f conda-env/pub.yml
conda activate warehouse_pub

You should also probably delete the existing warehouse_pub env that you already created (conda env remove -n warehouse_pub).

"warehouse publish --help" no longer bombs.  Good sign.  Now we test with a real dataset.


Running VerneMQ as a systemd service

Hello,
How running VerneMQ as a systemd service in centOS 7 ?
Thanks

@AnHellTe  thanks, does this help? https://github.com/erlio/vernemq/wiki/Running-VerneMQ-as-a-systemd-service
or is your point that this is docs for Ubuntu?

I guess it would be similar on CentOS. You'll have to figure it out. But if there is a difference, it would be great to document it on the Wiki too.

@AnHellTe did you manage to get it to work? if not, what step exactly seems to cause problems?

glad to hear ;)


EVDI kernel 5.11/5.12 support

Hello, everyone. Again, sorry for the wait.
Current evdi has been pushed to Github. It is however, NOT a complete driver and will require new DLM in order to work correctly. It should be up on our website in a couple of days (it may vary because of the holidays).
I will update this thread when it goes up.
I'll also be closely monitoring our Github, so if you'll be having any issues with the new kernels, I hope we'll be able to resolve them in a more timely manner. 😇
Thank you for your patience.

Thanks for the update!
I noticed that the changes have been pushed to the devel branch, but not the 1.7.x branch. Does this mean that the new DisplayLink Manager version will work with evdi 1.9.x?

does this update bring better support/performance for AMD Ryzen 4650?

It should be up on our website in a couple of days (it may vary because of the holidays).

Looking forward to this! I was wondering why my SideTrak stopped working, though I assumed it was a system update. Kernel update makes perfect sense. Hopefully the upcoming update will fix it!

Can't wait for the update!  For now I just set my default kernel in grubby to 5.10.23

Sounds great!
DisplayLink 5.4 is on the website, but we still need a evdi release, which supports 5.11/5.12.  It's not working for me on Xorg unfortunately, 5.11, testing 5.12 though

I hope that it solve my problems with evdi :)
i'm on pop'os 20.04 and update to kernel 5.11 without know that issue .... I've turn on 1 output screen instead of 3 :cry:
Thanks for your support !

@bnavigator are you using Wayland or X? It's not working for me on Xorg unfortunately, 5.11, testing 5.12 though

X11 on Archlinux with my displaylink package from AUR and evdi-git from AUR. Kernel 5.11.11-arch1-1

It's worth noting that on Archlinux I'm affected by #274 , downgrading mesa may resolve the problem.

It's also worth noting that DisplayLink 5.4.0-55.153 comes with a bundled evdi.tar.gz from https://github.com/DisplayLink/evdi/commit/0f1ad2153de1bc144f2359afa91fbe3fa07e9e7a
Just found out and I am considering changing the AUR and openSUSE package to not require a separate evdi at all...

Just found out and I am considering changing the AUR and openSUSE package to not require a separate evdi at all...

As DLM and evdi are two separate projects, with separate releases and separate versions, I prefer keeping them as separate AUR packages. In my opinion, that is the least confusing w.r.t. what is actually installed on your system.

It is totally confusing with all the different old and recent AUR packages for evdi. Some work, some don't and it's always a new situation for every new release (or lack of it).

It is totally confusing with all the different old and recent AUR packages for evdi. Some work, some don't and it's always a new situation for every new release (or lack of it).

That's a very good point. However, all those different AUR packages are necessary because every new kernel update breaks evdi in someway and evdi requires a patch. As DisplayLink does not add these patches into the DLM releases (as far as I am aware), you would need some other way to patch the bundled evdi. How would you deal with such a scenario without a separate evdi package that can be patched and updated regardless of DLM releases?

After installing current dev (f703808d1bc6) and DLM 5.4, I can finally detect displays :) But when trying to assign the display, I get the below in my Xorg log. I will wait for new evdi release or devel updates as @bnavigator stated above. Thanks
[  1247.149] (II) modeset(0): Allocate new frame buffer 3840x1080 stride
[  1247.245] failed to add fb -22
[  1247.245] (EE) modeset(G0): failed to set mode: Invalid argument
[  1247.455] (II) modeset(0): Allocate new frame buffer 1920x1080 stride
[  1247.697] (II) modeset(0): EDID vendor "AUO", prod id 8813
[  1247.697] (II) modeset(0): Printing DDC gathered Modelines:
[  1247.697] (II) modeset(0): Modeline "1920x1080"x0.0  141.00  1920 1936 1952 2104  1080 1083 1097 1116 -hsync -vsync (67.0 kHz eP)
[  1247.821] (II) modeset(0): EDID vendor "AUO", prod id 8813
[  1247.821] (II) modeset(0): Printing DDC gathered Modelines:
[  1247.821] (II) modeset(0): Modeline "1920x1080"x0.0  141.00  1920 1936 1952 2104  1080 1083 1097 1116 -hsync -vsync (67.0 kHz eP)
[  1247.955] (II) modeset(0): EDID vendor "AUO", prod id 8813
[  1247.955] (II) modeset(0): Printing DDC gathered Modelines:
[  1247.955] (II) modeset(0): Modeline "1920x1080"x0.0  141.00  1920 1936 1952 2104  1080 1083 1097 1116 -hsync -vsync (67.0 kHz eP)
[  1248.080] (II) modeset(0): EDID vendor "AUO", prod id 8813
[  1248.081] (II) modeset(0): Printing DDC gathered Modelines:
[  1248.081] (II) modeset(0): Modeline "1920x1080"x0.0  141.00  1920 1936 1952 2104  1080 1083 1097 1116 -hsync -vsync (67.0 kHz eP)
[  1248.428] (II) modeset(0): EDID vendor "AUO", prod id 8813
[  1248.428] (II) modeset(0): Printing DDC gathered Modelines:
[  1248.428] (II) modeset(0): Modeline "1920x1080"x0.0  141.00  1920 1936 1952 2104  1080 1083 1097 1116 -hsync -vsync (67.0 kHz eP)
[  1248.552] (II) modeset(0): EDID vendor "AUO", prod id 8813
[  1248.553] (II) modeset(0): Printing DDC gathered Modelines:
[  1248.553] (II) modeset(0): Modeline "1920x1080"x0.0  141.00  1920 1936 1952 2104  1080 1083 1097 1116 -hsync -vsync (67.0 kHz eP)

@nckrse  did you try to inspect reported modes and assing a valid mode with xrandr? Did 3840x1080 work with DL 5.3 and evdi 1.7?

After installing current dev (f703808)

That's not a commit in current dev

Perhaps someone can help me out. Using Pop!_OS 20.10 with GNOME 3.38.3 on Xorg. I installed the new Ubuntu driver version 5.4 from the DisplayLink site and rebooted. The service is running, seemingly without error:
$ systemctl status displaylink-driver.service
● displaylink-driver.service - DisplayLink Driver Service
     Loaded: loaded (/lib/systemd/system/displaylink-driver.service; static)
     Active: active (running) since Tue 2021-04-06 10:50:53 CDT; 3min 21s ago
    Process: 1275 ExecStartPre=/bin/sh -c modprobe evdi || (dkms install $(ls -t /usr/src | grep evdi | head -n1  | sed -e "s:-:/:") && modprobe evdi) (code=exited, status=0/SUCCESS)
   Main PID: 1278 (DisplayLinkMana)
      Tasks: 27 (limit: 38060)
     Memory: 20.5M
     CGroup: /system.slice/displaylink-driver.service
             └─1278 /opt/displaylink/DisplayLinkManager

Apr 06 10:50:53 caelum systemd[1]: Starting DisplayLink Driver Service...
Apr 06 10:50:53 caelum systemd[1]: Started DisplayLink Driver Service.

I have evdi 1.9.1 installed from this PPA because the regular repos only have 1.7:
$ apt search evdi
Sorting... Done
Full Text Search... Done
evdi-dkms/groovy,groovy,now 1.9.1+master~202104011348~rev320~pkg9~ubuntu20.10.1 all [installed]
  Extensible Virtual Display Interface driver kernel module

libevdi0/groovy,now 1.9.1+master~202104011348~rev320~pkg9~ubuntu20.10.1 amd64 [installed,automatic]
  Extensible Virtual Display Interface driver client library

GNOME detects that there is a second monitor plugged in:

However, it won't let me switch away from "single display". If I select "mirror" or "join displays" and click apply, it automatically goes back to "single display".

After installing current dev (f703808)

That's not a commit in current dev

@bnavigator , sorry, i was trying separate forks a few days ago. I re-installed on dev b0b3d131b26df and run into the same issue. I have tried different xrandr modes also. My issue is the same exact as @echosa , but I had tailed the logs during doing so.

You should move your questions to the displaylink support forum. This is out of scope for "EVDI kernel 5.11/5.12 support"

Perhaps someone can help me out. Using Pop!_OS 20.10 with GNOME 3.38.3 on Xorg. I installed the new Ubuntu driver version 5.4 from the DisplayLink site and rebooted. The service is running, seemingly without error:
$ systemctl status displaylink-driver.service
● displaylink-driver.service - DisplayLink Driver Service
     Loaded: loaded (/lib/systemd/system/displaylink-driver.service; static)
     Active: active (running) since Tue 2021-04-06 10:50:53 CDT; 3min 21s ago
    Process: 1275 ExecStartPre=/bin/sh -c modprobe evdi || (dkms install $(ls -t /usr/src | grep evdi | head -n1  | sed -e "s:-:/:") && modprobe evdi) (code=exited, status=0/SUCCESS)
   Main PID: 1278 (DisplayLinkMana)
      Tasks: 27 (limit: 38060)
     Memory: 20.5M
     CGroup: /system.slice/displaylink-driver.service
             └─1278 /opt/displaylink/DisplayLinkManager

Apr 06 10:50:53 caelum systemd[1]: Starting DisplayLink Driver Service...
Apr 06 10:50:53 caelum systemd[1]: Started DisplayLink Driver Service.

I have evdi 1.9.1 installed from this PPA because the regular repos only have 1.7:
$ apt search evdi
Sorting... Done
Full Text Search... Done
evdi-dkms/groovy,groovy,now 1.9.1+master~202104011348~rev320~pkg9~ubuntu20.10.1 all [installed]
  Extensible Virtual Display Interface driver kernel module

libevdi0/groovy,now 1.9.1+master~202104011348~rev320~pkg9~ubuntu20.10.1 amd64 [installed,automatic]
  Extensible Virtual Display Interface driver client library

GNOME detects that there is a second monitor plugged in:

However, it won't let me switch away from "single display". If I select "mirror" or "join displays" and click apply, it automatically goes back to "single display".

Same issue for me on my external monitors, detected but no way to display ang get it working with DLM 5.4, think it's mainly mesa 21 problems... Downgrading on popos is very dangerous but if it's the only way ... i will try as soon as i'll have time and get back here to give you feedback.

@Nillu I find myself in the same situation, Pop!_OS 20.04 and kernel 5.11.0-7612-generic. After upgrading kernel, one of my screens became completely useless.
I was thinking of downgrading kernel but I don't want to break my install at this point as it is my work PC. If you are able to get it working let me know! :)

I have evdi 1.9.1 installed from this PPA because the regular repos only have 1.7:

Note that the PPA says "evdi 1.9.1+master". master does not have the fixes for kernel >=5.11.
DisplayLink 2.4 comes with evdi bundled. Did you try to uninstall the PPA evdi and reinstall DisplayLink from the official installer?

I know it was recommended to go to the displaylink support, but when I contacted them, they only support Ubuntu. So, to update here since it was mentioned: I used Timeshift to rollback to before kernel 5.11. Then I used the previous driver installer to completely remove the old version of the driver and its evdi. (I was having issues with not being able to remove evdi completely). Once that was uninstalled and all clean again, I upgraded back to 5.11 again. I then installed the latest displaylink driver that was just released, including its bundled evdi, without having evdi installed via apt (whether PPA or not). Same issue. Everything seems fine. Service is running. Display is detected by GNOME. Still can't get it to actually display.
Just wanted to update, since "Did you try to uninstall the PPA evdi and reinstall DisplayLink from the official installer?" didn't work.

When you say PPA, I suspect Pop!_OS is close enough to Ubuntu. The "official" support might not be willing to help, but the forums are probably a better place to discuss this issue with then DisplayLink Manager than the GitHub issue tracker for evdi:
https://www.displaylink.org/forum/forumdisplay.php?f=29

Thank you for that link. I've reached back out to the official support, but having access to that forums is nice too. I'll avoid cluttering this GitHub issue anymore.

Just to reiterate, DLM 5.4 has since been released. 😇
It works with the current devel, at last.
No updates for AMD-specific bugs yet.
We're aware of the issues on Pop!_OS and we'll be promptly investigating what has happened over there. 😉

Thanks, @displaylink-emajewsk! Regarding:

We're aware of the issues on Pop!_OS and we'll be promptly investigating what has happened over there. wink
Is there somewhere we can track progress of that other than just watching for messages here?

@displaylink-emajewsk Thank you for the updates.  I can confirm that it is working on Fedora 33.
Question: Are there any plans to re-tag 1.9.1 from the current devel branch?
This would be helpful for packaging.  Otherwise, we need to make changes over on https://github.com/displaylink-rpm/displaylink-rpm
Thanks again for keeping us updated.

On my side, I only have 1 external monitor working on 2. The other one is not detected on xrandr. When plug/unplug it can switch from one to another randomly, but I can't get both working at the same time.
Here eDP1 is the laptop monitor and DVI is one of the 2 external:
xrandr --listmonitors
Monitors: 2
 0: +*eDP1 1920/340x1080/190+5120+180  eDP1
 1: +DVI-I-1-1 2560/596x1440/335+0+0  DVI-I-1-1

Any idea?
Thanks

I try to get 5.4 in running on devuan chimaera
I get EVDI compiled and loaded as dkms on the 5.10.0-5-amd64 kernel.
But inserting fails with:
dmesg | grep evdi
[   85.702974] evdi: [I] Initialising logging on level 5
[   85.702975] evdi: [I] Atomic driver: yes
[   85.703024] evdi: [D] evdi_platform_add_devices:158 Increasing device count to 4
[   85.703073] evdi: [D] evdi_crtc_init:413 drm_crtc_init: 0 p0000000032537284
[   85.703083] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[   85.703088] evdi evdi.0: [drm] Cannot find any crtc or sizes
[   85.703097] evdi: [W] evdi_painter_send_update_ready_if_needed:706 Painter does not exist!
[   85.703199] [drm] Initialized evdi 1.9.1 20210126 for evdi.0 on minor 1
[   85.703205] evdi: [I] Evdi platform_device create
[   85.703235] evdi: [D] evdi_crtc_init:413 drm_crtc_init: 0 p00000000a7cad1e5
[   85.703240] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[   85.703242] evdi evdi.1: [drm] Cannot find any crtc or sizes
[   85.703245] evdi: [W] evdi_painter_send_update_ready_if_needed:706 Painter does not exist!
[   85.703474] [drm] Initialized evdi 1.9.1 20210126 for evdi.1 on minor 2
[   85.703480] evdi: [I] Evdi platform_device create
[   85.703507] evdi: [D] evdi_crtc_init:413 drm_crtc_init: 0 p0000000043467b57
[   85.703510] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[   85.703512] evdi evdi.2: [drm] Cannot find any crtc or sizes
[   85.703515] evdi: [W] evdi_painter_send_update_ready_if_needed:706 Painter does not exist!
[   85.703681] [drm] Initialized evdi 1.9.1 20210126 for evdi.2 on minor 3
[   85.703689] evdi: [I] Evdi platform_device create
[   85.703728] evdi: [D] evdi_crtc_init:413 drm_crtc_init: 0 p00000000c48faaa7
[   85.703736] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[   85.703740] evdi evdi.3: [drm] Cannot find any crtc or sizes
[   85.703747] evdi: [W] evdi_painter_send_update_ready_if_needed:706 Painter does not exist!
[   85.705042] [drm] Initialized evdi 1.9.1 20210126 for evdi.3 on minor 4
[   85.725138] evdi: [I] Evdi platform_device create
[   85.801299] evdi: [D] evdi_driver_postclose:230 (dev=0) Process tries to close us, postclose
[   85.801972] evdi: [I] Task 4066 (Xorg.wrap) of process 4066 (Xorg.wrap)
[   85.802641] evdi: [D] evdi_driver_postclose:230 (dev=0) Process tries to close us, postclose
[   85.802642] evdi: [I] Task 4066 (Xorg.wrap) of process 4066 (Xorg.wrap)
[   85.802646] evdi: [D] evdi_driver_postclose:230 (dev=0) Process tries to close us, postclose
[   85.802646] evdi: [I] Task 4066 (Xorg.wrap) of process 4066 (Xorg.wrap)
[   85.802651] evdi: [D] evdi_driver_postclose:230 (dev=0) Process tries to close us, postclose
[   85.804697] evdi: [I] Task 4066 (Xorg.wrap) of process 4066 (Xorg.wrap)
[   85.834554] evdi: [D] evdi_driver_postclose:230 (dev=0) Process tries to close us, postclose
[   85.836303] evdi: [I] Task 4066 (Xorg) of process 4066 (Xorg)
[   85.838188] evdi: [D] evdi_driver_postclose:230 (dev=0) Process tries to close us, postclose
[   85.840605] evdi: [I] Task 4066 (Xorg) of process 4066 (Xorg)
[   85.842700] evdi: [D] evdi_driver_postclose:230 (dev=0) Process tries to close us, postclose
[   85.843966] evdi: [I] Task 4066 (Xorg) of process 4066 (Xorg)
[   85.844761] evdi: [D] evdi_driver_postclose:230 (dev=0) Process tries to close us, postclose
[   85.845557] evdi: [I] Task 4066 (Xorg) of process 4066 (Xorg)
[   85.894930] evdi: [D] evdi_driver_postclose:230 (dev=0) Process tries to close us, postclose
[   85.894935] evdi: [I] Task 4066 (Xorg) of process 4066 (Xorg)
[   85.894961] evdi: [D] evdi_driver_postclose:230 (dev=0) Process tries to close us, postclose
[   85.894963] evdi: [I] Task 4066 (Xorg) of process 4066 (Xorg)
[   85.894979] evdi: [D] evdi_driver_postclose:230 (dev=0) Process tries to close us, postclose
[   85.894980] evdi: [I] Task 4066 (Xorg) of process 4066 (Xorg)
[   85.894993] evdi: [D] evdi_driver_postclose:230 (dev=0) Process tries to close us, postclose
[   85.894994] evdi: [I] Task 4066 (Xorg) of process 4066 (Xorg)
[   86.067434] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[   86.067519] evdi: [D] evdi_painter_framebuffer_size:594 Scanout buffer not set.
[   86.067521] evdi: [D] evdi_painter_mark_dirty:621 (dev=0) Skip clip rect. Scanout buffer not set.
[   86.067534] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[   86.067820] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[   86.067878] evdi: [D] evdi_painter_framebuffer_size:594 Scanout buffer not set.
[   86.067879] evdi: [D] evdi_painter_mark_dirty:621 (dev=0) Skip clip rect. Scanout buffer not set.
[   86.067887] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[   86.068128] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[   86.068183] evdi: [D] evdi_painter_framebuffer_size:594 Scanout buffer not set.
[   86.068185] evdi: [D] evdi_painter_mark_dirty:621 (dev=0) Skip clip rect. Scanout buffer not set.
[   86.068192] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[   86.068417] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[   86.068466] evdi: [D] evdi_painter_framebuffer_size:594 Scanout buffer not set.
[   86.068468] evdi: [D] evdi_painter_mark_dirty:621 (dev=0) Skip clip rect. Scanout buffer not set.
[   86.068474] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[   86.138127] evdi: [D] evdi_painter_dpms_notify:715 (dev=0) Notifying dpms mode: 3
[   86.138131] evdi: [W] evdi_painter_send_event:321 Painter is not connected!
[   86.138927] evdi: [D] evdi_painter_dpms_notify:715 (dev=0) Notifying dpms mode: 3
[   86.138930] evdi: [W] evdi_painter_send_event:321 Painter is not connected!
[   86.139653] evdi: [D] evdi_painter_dpms_notify:715 (dev=0) Notifying dpms mode: 3
[   86.139657] evdi: [W] evdi_painter_send_event:321 Painter is not connected!
[   86.140331] evdi: [D] evdi_painter_dpms_notify:715 (dev=0) Notifying dpms mode: 3
[   86.140333] evdi: [W] evdi_painter_send_event:321 Painter is not connected!
[   86.873706] evdi: [D] evdi_painter_dpms_notify:715 (dev=0) Notifying dpms mode: 3
[   86.873712] evdi: [W] evdi_painter_send_event:321 Painter is not connected!
[   86.873729] evdi: [D] evdi_painter_dpms_notify:715 (dev=0) Notifying dpms mode: 3
[   86.873732] evdi: [W] evdi_painter_send_event:321 Painter is not connected!
[   86.873743] evdi: [D] evdi_painter_dpms_notify:715 (dev=0) Notifying dpms mode: 3
[   86.873745] evdi: [W] evdi_painter_send_event:321 Painter is not connected!
[   86.873755] evdi: [D] evdi_painter_dpms_notify:715 (dev=0) Notifying dpms mode: 3
[   86.873757] evdi: [W] evdi_painter_send_event:321 Painter is not connected!
[   86.874800] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[   86.874818] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[   86.874868] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[   86.874877] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[   86.874924] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[   86.874934] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[   86.874981] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[   86.874992] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
Any ideas?
Jan

I found another error myself.
DisplayLink(R) && Lennart implicitly assume that /opt is part of the root filesystem which is mounted when /etc/udev/rules.d/99-displaylink.rules is executed.
I oversaw the error in dmesg about /opt/displaylink/udev.sh could not be executed (because it was not mounted at that time.....).
Additionally executing
/opt/displaylink/udev.sh /dev usb-004-003-DisplayLink_USB-C_Triple-4K_Dock_DGWC00110028635 /dev/bus/usb/004/003
(for my computer) from within the /etc/init.d/displaylink.sh script didn't help. (Even with the evdi module loaded later - not via /etc/modules-load.d/evdi.conf ....).
Adapting 99-displaylink.rules with /sbin instead of /opt/displaylink and copying udev.sh to /sbin solved that problem.
I am still stuck with
....
[   77.396608] evdi: [D] evdi_platform_add_devices:158 Increasing device count to 4
[   77.399153] evdi: [D] evdi_crtc_init:413 drm_crtc_init: 0 p000000000dedf4d6
[   77.399949] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[   77.400744] evdi evdi.0: [drm] Cannot find any crtc or sizes
[   77.402867] evdi: [W] evdi_painter_send_update_ready_if_needed:706 Painter does not exist!
[   77.407206] [drm] Initialized evdi 1.9.1 20210126 for evdi.0 on minor 0
[   77.408026] evdi: [I] Evdi platform_device create
[   77.408898] evdi: [D] evdi_crtc_init:413 drm_crtc_init: 0 p00000000f68ea074
[   77.409670] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[   77.410433] evdi evdi.1: [drm] Cannot find any crtc or sizes
[   77.411200] evdi: [W] evdi_painter_send_update_ready_if_needed:706 Painter does not exist!
[   77.411654] [drm] Initialized evdi 1.9.1 20210126 for evdi.1 on minor 1
[   77.413197] evdi: [I] Evdi platform_device create
[   77.414002] evdi: [D] evdi_crtc_init:413 drm_crtc_init: 0 p00000000314633ec
[   77.414777] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[   77.415538] evdi evdi.2: [drm] Cannot find any crtc or sizes
[   77.416310] evdi: [W] evdi_painter_send_update_ready_if_needed:706 Painter does not exist!
[   77.416382] [drm] Initialized evdi 1.9.1 20210126 for evdi.2 on minor 2
[   77.418017] evdi: [I] Evdi platform_device create
[   77.418829] evdi: [D] evdi_crtc_init:413 drm_crtc_init: 0 p00000000a94bae34
[   77.419615] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[   77.420393] evdi evdi.3: [drm] Cannot find any crtc or sizes
[   77.421214] evdi: [W] evdi_painter_send_update_ready_if_needed:706 Painter does not exist!
[   77.421280] [drm] Initialized evdi 1.9.1 20210126 for evdi.3 on minor 3
.....
evdi 1.9.1 does not like the 5.10.0-5-amd64 #1 SMP Debian 5.10.26-1 kernel.
This should be the same kernel as in bullseye.
Anybody having displaylink on bullseye running?

Hi,
it works with Ubuntu Hirsute (5.11.0)  and Displaylink 5.4 (displaylink-driver-5.4.0-55.153.run)

NAME="Ubuntu"
VERSION="21.04 (Hirsute Hippo)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu Hirsute Hippo (development branch)"
VERSION_ID="21.04"
VERSION_CODENAME=hirsute
UBUNTU_CODENAME=hirsute
uname -a
Linux swoopla 5.11.0-13-generic #14-Ubuntu SMP Fri Mar 19 16:55:27 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

dmesg
[   58.009718] evdi: [I] Attaching to usb:2-1.4
[   58.010893] evdi: [D] evdi_painter_connect:851 (dev=0) Process is trying to connect
[   58.010896] evdi: [I] Task 2380 (DesktopManagerE) of process 2372 (DisplayLinkMana)
[   58.011043] evdi: [D] evdi_add_i2c_adapter:813 (dev=0) Added i2c adapter bus number 11
[   58.011045] evdi: [D] evdi_painter_connect:903 (dev=0) Connected with 00000000f441ac4f
[   58.011049] evdi: [D] evdi_detect:90 (dev=0) poll connector state: connected
[   58.011736] evdi: [I] Attaching to usb:2-1.4
[   58.012741] evdi: [D] evdi_painter_connect:851 (dev=0) Process is trying to connect
[   58.012743] evdi: [I] Task 2380 (DesktopManagerE) of process 2372 (DisplayLinkMana)
[   58.012808] evdi: [D] evdi_add_i2c_adapter:813 (dev=1) Added i2c adapter bus number 12
[   58.012810] evdi: [D] evdi_painter_connect:903 (dev=1) Connected with 000000000f7351f1
[   58.012813] evdi: [D] evdi_detect:90 (dev=1) poll connector state: connected
[   58.086479] evdi: [D] evdi_detect:90 (dev=0) poll connector state: connected
[   58.086481] evdi: [D] evdi_painter_get_edid_copy:242 (dev=0) EDID valid
[   58.086566] evdi: [D] evdi_detect:90 (dev=0) poll connector state: connected
[   58.086567] evdi: [D] evdi_painter_get_edid_copy:242 (dev=0) EDID valid
[   58.086661] evdi: [D] evdi_detect:90 (dev=1) poll connector state: connected
[   58.086662] evdi: [D] evdi_painter_get_edid_copy:242 (dev=1) EDID valid
[   58.086857] evdi: [D] evdi_detect:90 (dev=1) poll connector state: connected
[   58.086858] evdi: [D] evdi_painter_get_edid_copy:242 (dev=1) EDID valid
[   58.087056] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[   58.087060] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[   58.087064] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[   58.087067] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[   58.105959] evdi: [D] evdi_painter_framebuffer_size:594 Scanout buffer not set.
[   58.105962] evdi: [D] evdi_painter_mark_dirty:621 (dev=1) Skip clip rect. Scanout buffer not set.
[   58.105964] evdi: [D] evdi_painter_framebuffer_size:594 Scanout buffer not set.
[   58.105964] evdi: [D] evdi_painter_mark_dirty:621 (dev=1) Skip clip rect. Scanout buffer not set.
[   58.105966] evdi: [D] evdi_painter_framebuffer_size:594 Scanout buffer not set.
[   58.105967] evdi: [D] evdi_painter_mark_dirty:621 (dev=0) Skip clip rect. Scanout buffer not set.
[   58.105968] evdi: [D] evdi_painter_framebuffer_size:594 Scanout buffer not set.
[   58.105968] evdi: [D] evdi_painter_mark_dirty:621 (dev=0) Skip clip rect. Scanout buffer not set.
[   58.185434] evdi: [D] evdi_detect:90 (dev=0) poll connector state: connected
[   58.185437] evdi: [D] evdi_painter_get_edid_copy:242 (dev=0) EDID valid
[   58.185522] evdi: [D] evdi_detect:90 (dev=0) poll connector state: connected
[   58.185523] evdi: [D] evdi_painter_get_edid_copy:242 (dev=0) EDID valid
[   58.185610] evdi: [D] evdi_detect:90 (dev=1) poll connector state: connected
[   58.185611] evdi: [D] evdi_painter_get_edid_copy:242 (dev=1) EDID valid
[   58.185808] evdi: [D] evdi_detect:90 (dev=1) poll connector state: connected
[   58.185810] evdi: [D] evdi_painter_get_edid_copy:242 (dev=1) EDID valid
[   58.186017] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[   58.186021] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[   58.186025] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[   58.186028] evdi: [D] evdi_detect:94 (dev=0) poll connector state: disconnected
[   58.198062] evdi: [D] evdi_painter_framebuffer_size:594 Scanout buffer not set.
[   58.198065] evdi: [D] evdi_painter_mark_dirty:621 (dev=1) Skip clip rect. Scanout buffer not set.
[   58.198066] evdi: [D] evdi_painter_framebuffer_size:594 Scanout buffer not set.
[   58.198067] evdi: [D] evdi_painter_mark_dirty:621 (dev=1) Skip clip rect. Scanout buffer not set.
[   58.198069] evdi: [D] evdi_painter_framebuffer_size:594 Scanout buffer not set.
[   58.198070] evdi: [D] evdi_painter_mark_dirty:621 (dev=0) Skip clip rect. Scanout buffer not set.
[   58.198071] evdi: [D] evdi_painter_framebuffer_size:594 Scanout buffer not set.
[   58.198071] evdi: [D] evdi_painter_mark_dirty:621 (dev=0) Skip clip rect. Scanout buffer not set.
[   58.274820] evdi: [D] evdi_painter_dpms_notify:715 (dev=0) Notifying dpms mode: 3
[   58.274824] evdi: [W] evdi_painter_send_event:321 Painter is not connected!
[   58.274830] evdi: [D] evdi_painter_dpms_notify:715 (dev=0) Notifying dpms mode: 3
[   58.274831] evdi: [W] evdi_painter_send_event:321 Painter is not connected!
[   58.289755] evdi: [D] evdi_painter_dpms_notify:715 (dev=0) Notifying dpms mode: 0
[   58.289763] evdi: [D] evdi_painter_mode_changed_notify:762 (dev=0) Notifying mode changed: 1920x1080@60; bpp 32;
[   58.289765] evdi: [D] evdi_log_pixel_format:741 pixel format XR24 little-endian (0x34325258)
[   58.289767] evdi: [D] evdi_painter_dpms_notify:715 (dev=0) Notifying dpms mode: 0
[   58.305406] evdi: [D] evdi_painter_dpms_notify:715 (dev=1) Notifying dpms mode: 0
[   58.305414] evdi: [D] evdi_painter_mode_changed_notify:762 (dev=1) Notifying mode changed: 1920x1080@60; bpp 32;
[   58.305417] evdi: [D] evdi_log_pixel_format:741 pixel format XR24 little-endian (0x34325258)
[   58.305418] evdi: [D] evdi_painter_dpms_notify:715 (dev=1) Notifying dpms mode: 0

But i don't have evdi package installed on my system:
swoopla@swoopla:~$ dpkg -l |grep evdi
swoopla@swoopla:~$ dpkg -l |grep dkms
ii  dkms                                       2.8.4-4                                                     all          Dynamic Kernel Module Support Framework

If you use the official standalone installer from DisplayLink, it comes with evdi bundled. It won't install any package into the dpkg database.
Once again, please: The title of this page is "EVDI kernel 5.11/5.12 support". For anything else, please either use the displaylink support forum, or if it is specific to the evdi driver, open a new issue.

I have Arch Linux with Kernel 5.11.12 on a Cinnamon Desktop and latest evdi & Displaylink commit. So every change of resolution  or master screen ends up on a freeze also zoom isn‘t possible.

@displaylink-emajewsk Thank you for the updates.  I can confirm that it is working on Fedora 33.
Question: Are there any plans to re-tag 1.9.1 from the current devel branch?
This would be helpful for packaging.  Otherwise, we need to make changes over on https://github.com/displaylink-rpm/displaylink-rpm
Thanks again for keeping us updated.

Just following up on this question.
Thanks

@displaylink-emajewsk Thank you for the updates.  I can confirm that it is working on Fedora 33.
Question: Are there any plans to re-tag 1.9.1 from the current devel branch?
This would be helpful for packaging.  Otherwise, we need to make changes over on https://github.com/displaylink-rpm/displaylink-rpm
Thanks again for keeping us updated.

Just following up on this question.
Thanks

@displaylink-emajewsk @displaylink-dkurek
Sorry to ask once more.  Can we expect to get a proper EVDI release that works with Kernel 5.11/5.12?  The current 1.9.1 tag is not compatible with those kernels.  You are bundling with the DisplayLink 5.4 drivers an unreleased version of EVDI.
Thank you for your help and support.

FYI for Pop!_OS users having issues, follow this thread instead: https://github.com/DisplayLink/evdi/issues/279

@displaylink-emajewsk Thank you for the updates.  I can confirm that it is working on Fedora 33.
Question: Are there any plans to re-tag 1.9.1 from the current devel branch?
This would be helpful for packaging.  Otherwise, we need to make changes over on https://github.com/displaylink-rpm/displaylink-rpm
Thanks again for keeping us updated.

Just following up on this question.
Thanks

@displaylink-emajewsk @displaylink-dkurek
Sorry to ask once more. Can we expect to get a proper EVDI release that works with Kernel 5.11/5.12? The current 1.9.1 tag is not compatible with those kernels. You are bundling with the DisplayLink 5.4 drivers an unreleased version of EVDI.
Thank you for your help and support.

How about we create a downstream repo of this EVDI devel branch on https://github.com/displaylink-rpm/ and then tag it ourselves. That way we not dependent on any tags here.

I'm back from holiday. Thanks for the patience. 😇
@elguero The release has been retagged. Someone must've tagged the version incorrectly before pushing and we did not notice. I'll be more vigilant in the future. 😅
Is there anything else I can do to make packaging easier?

@displaylink-emajewsk Thank you!
One thing that would be helpful is to have support for newer kernels done at a quicker pace.  I know it all comes down to resources.  Some in the community are quick to help test the release candidates and they point out when changes are needed for upcoming kernel releases.  If those items could be taken care of before the official release or at least before the distros start to use the newer kernel that causes issues, that would be helpful.
This is probably a no go as far as being resolved but the DisplayLink manager binary complicates being able to put something up on Fedora copr or even considered for inclusion in Fedora, if we are understanding things correctly (https://github.com/displaylink-rpm/displaylink-rpm/issues/125).  There was a request to add it to Fedora copr but we think that the DisplayLink manager binary prevents this from being done according to the current policies.  Work is being done by contributors to try and get the displaylink-rpm project included in RPMFusion.  One contributor has submitted a PR to help work towards this (https://github.com/displaylink-rpm/displaylink-rpm/pull/97).
Thank you for asking and for your responses.

It might be even more out of scope, but IMHO the best solution would be to commit the opensource kernel module into the official linux kernel tree. It's the recommended way to keep all the drivers in sync with kernel development as it draws on the resources of kernel developers. See amdgpu vs nvidia drivers and how their approaches are received within the Linux community.

I'm back from holiday. Thanks for the patience. innocent
@elguero The release has been retagged. Someone must've tagged the version incorrectly before pushing and we did not notice. I'll be more vigilant in the future. sweat_smile
Is there anything else I can do to make packaging easier?

You should probably also update your Releases page to indicate that v1.9.1 is the latest release, it's still showing v1.9.0 as being the latest release.
https://github.com/DisplayLink/evdi/releases

One thing that would be helpful is to have support for newer kernels done at a quicker pace.

@elguero Unfortunately, we only officially support Ubuntu LTS releases. Other Linux releases are being put in the "nice to have if there's time" category as of now. 😢
Actually, in regards to your second question, probably the best way to have support done earlier would be to message DisplayLink as a distro representative and offer to work together to bring support on both ends, or something similar, I think.
Fedora's policies indeed prevent us from being included. RPMFusion sounds like a good idea though. Ideally, there will soon be some improvement in our driver distribution. At least it'd seem my nagging has worked for once. 😀
@bnavigator This is out of my hands, sorry.
@ztoufie Ah, thanks! 😇

Fix in Xserver is done!  Needs to built for Ubuntu from master: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1931547

Discussion on this issue deviated from 5.12 kernel to that Pop!_OS issue:
https://github.com/DisplayLink/evdi/issues/279 that is fixed now.
If there is any 5.11/5.12 kernel issue please raise new issue.
This one is to be closed.


Cannot install the Plugin

Your Environment

Plugin version:3.1.0
Platform: Android
OS version:
Device manufacturer and model:

Running in Simulator:
Cordova version (cordova -v): 9.0.0<EMAIL_ADDRESS>Cordova platform version (cordova platform ls): android 8.1.0, ios 5.1.1
Plugin configuration options:
Link to your project:

Context

When I try to run the command "cordova plugin add @mauron85/cordova-plugin-background-geolocation", I get the following error.
gurjitghangura@gghangura:~/Documents/git/Owlshead$ cordova plugin add @mauron85/cordova-plugin-background-geolocation
Installing "cordova-plugin-background-geolocation" for android
Error during processing of action! Attempting to revert...
Failed to install 'cordova-plugin-background-geolocation': CordovaError: Uh oh!
"/Users/gurjitghangura/Documents/git/Owlshead/platforms/android/cordova-plugin-background-geolocation/gpsapp-dependencies.gradle" already exists!
at copyNewFile (/Users/gurjitghangura/Documents/git/Owlshead/platforms/android/cordova/lib/pluginHandlers.js:234:45)
at install (/Users/gurjitghangura/Documents/git/Owlshead/platforms/android/cordova/lib/pluginHandlers.js:80:17)
at ActionStack.process (/Users/gurjitghangura/Documents/git/Owlshead/node_modules/cordova-common/src/ActionStack.js:56:25)
at PluginManager.doOperation (/Users/gurjitghangura/Documents/git/Owlshead/node_modules/cordova-common/src/PluginManager.js:112:24)
at PluginManager.addPlugin (/Users/gurjitghangura/Documents/git/Owlshead/node_modules/cordova-common/src/PluginManager.js:142:21)
at /Users/gurjitghangura/Documents/git/Owlshead/platforms/android/cordova/Api.js:210:74
at _fulfilled (/Users/gurjitghangura/Documents/git/Owlshead/node_modules/q/q.js:854:54)
at /Users/gurjitghangura/Documents/git/Owlshead/node_modules/q/q.js:883:30
at Promise.promise.promiseDispatch (/Users/gurjitghangura/Documents/git/Owlshead/node_modules/q/q.js:816:13)
at /Users/gurjitghangura/Documents/git/Owlshead/node_modules/q/q.js:877:14
Uh oh!
"/Users/gurjitghangura/Documents/git/Owlshead/platforms/android/cordova-plugin-background-geolocation/gpsapp-dependencies.gradle" already exists!
Expected Behavior
The command should install the plugin

Actual Behavior
The command does not install the plugin and throws an error

Possible Fix

Steps to Reproduce

I am not too sure how to reproduce it
1.
2.
3.
4.
Context

I am trying to use this plugin to test the location features in Android. And update the UI of the User Location.
Debug logs

Hey,
you just need to delete the platforms folder, then reinstall (If you haven´t already)


you are the reference implementation, PR?

Hi,
your implementation seems to have become the de facto reference. At least you are maintaining it, google isn't.
Any plan to PR all your improvements?

Hi. It was a very hot summer, both literally and figural - was working hard on PIK, preparing it for JPEG-XL proposal. Starting from September, I'm back to brotli & co.
I plan to grab appropriate PRs from google/nginx_brotli, and some useful stuff from other branches, when I have time.
Also I plan to negotiate with google/nginx_brotli to get control over it, so it will be a less confusing story for users.

Great news, and welcome back ;)

The CLA may be a problem for merging back in the older project. Imho they could update their README to point to this repository.

There are 3 commits / authors I need to check / ask for signing CLA.
Technically, it is possible to rewrite the commit history in a way, that places commits of all authors who does not sign CLA at the end of the chain, and tag / pull at the "clean" commit... hopefully, we would not need to do this.

At last, reordered the commit sequence and merged the "approved" part of fork to google/ngx_brotli =)


Automated cherry pick of #6746

Cherry pick of #6746 on release-1.56.
/cc  @enahum
NONE

The file .circleci/config.yml is in the blocklist for external contributors. Hence, these changes are not tested by the CI pipeline active until the build is re-triggered by a core committer or the PR is merged. Please be careful when reviewing it.
/cc @mattermost/core-security @mattermost/core-build-engineers


[QNEBE-X] Fix requests.auth typing issue

MyPy complaining about some Optional types lead to pipeline breaking.

Had to fix it in  https://github.com/QuTech-Delft/qne-adk/pull/53
After accepting PR53 this pull request can be closed


Add extra requested parameters

Add extra params as requested in #91 #95 and #103.
Some of them may not be very common but I don't think they harm.

@mcliment Is there anything left to do? Or are we good to merge?

@HofmeisterAn Not for the time being.