Warning players instead of kicking them

The tps check after kicking someone can be influenced way too easy by someone else, it's not really a safe way to make sure someone is causing lag. The whole concept of kicking people and then checking the tps improvement was implemented when our means to filter out the baddies involved a lot of guessing, but with what we have now, we can simply compute whether someone is causing lag and decide based on that.
So what this does is, it warns whoever is caught loading too many entities and tells him (and everyone in a radius around him) to leave the area causing lag. If he is caught again, he gets a long ban.
@ProgrammerDan  Last time you said you were not opposed to it, but didnt really give me a clear answer, do you think this would be better? If yes, could you review this, please?

This is really good. I'm going to go ahead with a rebalance and the "meaner" version we've got prepped, but once we've given this a fair shake on Civtest we'll want to move quickly in replacing AFKPGC with this.

@ProgrammerDan  Could you just take a quick look at what I added and if it's fine, we just roll it out tomorrow? I feel like this would already be a huge improvement.

Did you build this and push it to civtest? Need at least basic stability confirmation.

I am not sure, what you mean with pushing to civtest, but I was able to build it and run it on my own server without any problems.

It still builds and works, I would highly recommend to just use this for tomorrow (unless Dan has bigger concerns about it) or to at least set the plugin to observation mode. I would also still happily help with figuring out a good balanced config, if anyone gives me any logs (filtered is fine as well, as long as it's still possible to track single players in it).
@ttk2

Gonna build this and toss it on civtest. Expect some data shortly, Max. IRL intervened in my grand plans.

Yeah, I'll take a look tomorrow, I'll go to for sleep today, sorry.

No, I'm sorry, really wanted to get this data to you. Brightside, tons of stuff waiting for you in your inbox in the morning.

Okay, I'm making a pull against your branch/repo, max -- merge that and I have no objection to this going live.

Cross your fingers, gonna merge this. Everything looks stable so far on Civtest; I'll leave a warning here if that changes during the night. Otherwise @ttk2 this will be safe to merge and deploy. You'll have a new carebear config in the morning. I'll leave it up to you if you want to turn on kicks, but at least with this version people will get a fair warning first :).

we can collect data for a little while longer unless you think kicks are needed to get good info?

We fixed some bugs last night, which kept it from working properly and also made a few changes to the algorithm, which should massively reduce the rate of false positives. Unless you already put it in normal mode and left, it would probably be best to run it in observation mode today, take a look at the logs in the evening and come up with a good config for a real test on friday.

its been in observation mode today, dan I can hand you logs if you want more?

Definitely, need all the logs you can toss my way. I'm excited to see what impact these changes had.


ExtractorError

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like this: [x])
Use the Preview tab to see what your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2018.10.29. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2018.10.29

Before submitting an issue make sure you have:

[x] At least skimmed through the README, most notably the FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones
[x] Checked that provided video/audio/playlist URLs (if any) are alive and playable in a browser

What is the purpose of your issue?

[x] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add the -v flag to your command line you run youtube-dl with (youtube-dl -v <your command line>), copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
[debug] System config: []
[debug] User config: [u'-o', u'%(title)s.%(ext)s']
[debug] Custom config: []
[debug] Command-line args: [u'-v', u'http://www.bbcamerica.com/?amcn_video_movie=adv-space-time']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2018.10.29
[debug] Python version 2.7.13 (CPython) - Linux-4.4.159-73-default-x86_64-with-SuSE-42.3-x86_64
[debug] exe versions: ffmpeg 3.4.1, ffprobe 3.4.1, rtmpdump 2.4
[debug] Proxy map: {}
[generic] ?amcn_video_movie=adv-space-time: Requesting header
WARNING: Falling back on generic information extractor.
[generic] ?amcn_video_movie=adv-space-time: Downloading webpage
[generic] ?amcn_video_movie=adv-space-time: Extracting information
[download] Downloading playlist: An Adventure in Space and Time | BBC America
[generic] playlist An Adventure in Space and Time | BBC America: Collected 1 video ids (downloading 1 of them)
[download] Downloading video 1 of 1
[ThePlatform] V1JQFmTdQkVn: Downloading SMIL data
ERROR: This content requires a valid, unexpired auth token.
Traceback (most recent call last):
  File "/home/user/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 792, in extract_info
    ie_result = ie.extract(url)
  File "/home/user/bin/youtube-dl/youtube_dl/extractor/common.py", line 508, in extract
    ie_result = self._real_extract(url)
  File "/home/user/bin/youtube-dl/youtube_dl/extractor/theplatform.py", line 297, in _real_extract
    formats, subtitles = self._extract_theplatform_smil(smil_url, video_id)
  File "/home/user/bin/youtube-dl/youtube_dl/extractor/theplatform.py", line 44, in _extract_theplatform_smil
    raise ExtractorError(error_element.attrib['abstract'], expected=True)
ExtractorError: This content requires a valid, unexpired auth token.

Duplicate of #17871.


Support for Remix 2.9.1

Hi @kiliman,
Will there be support for remix 2.9.1 soon, I have tried to upgrade and get build errors ...
While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@remix-run/dev
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!   peer<EMAIL_ADDRESS>|| ^2.0.0" from<EMAIL_ADDRESS>npm ERR!   node_modules/@remix-run/v1-route-convention
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/remix-flat-routes
npm ERR!       dev<EMAIL_ADDRESS>from the root project
npm ERR!   1 more (remix-flat-routes)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! dev<EMAIL_ADDRESS>from the root project

It's not a compatibility issue with remix-flat-routes. I believe it's because we're using React Canary.
If you update to Remix v2.9.1 using npm install --legacy-peer-deps it should update correctly. Then, you can use npm install regularly from now on.

Thank you @kiliman, learn something new, thx.


Ignore lock files when purging cache

Ignore lock files when purging cache.
Motivation:
I found a small bug where swift package purge-cache would try to delete the lock files inside the cache. When deleting the lock files a lock for the lock file would be acquired creating a new lock file with the same name but ".lock" appended.
Modifications:
Don't delete files/directories with a suffix of ".lock"
Result:
Lock files will stay intact and no new lock files will be created.

@swift-ci please smoke test

So if the actual repositories are removed while another package manager invocation is accessing the cache, wouldn't that still break the other package manager invocation?  It's an edge case, to be sure.  I also agree with Boris that you'd want the log files removed as well if you're really purging the cache.  Is there a way to have a reader-writer lock on the cache itself and to only purge it (but do so completely) when nobody else is using it?

So if the actual repositories are removed while another package manager invocation is accessing the cache, wouldn't that still break the other package manager invocation?
There is no scenario I can think of where deleting a cached repository can break other invocations of the package manager.
If for example the package is deleted while we are waiting for its lock we won't run into any issues since we check after acquiring the lock if the package directory exists.

Is there a way to have a reader-writer lock on the cache itself and to only purge it (but do so completely) when nobody else is using it?
we could do that

@swift-ci please smoke test

Thanks, @tgymnich, this looks good to me now!


Rename remove-unused-repo-tabs to clean-repo-tabs

Closes #4562
Test URLs
https://github.com/sindresorhus/refined-github
Screenshot
(Click to enlarge)

Only clean-repo-tabs enabled
	Only more-dropdown enabled
	Both enabled

Note: d-none works perfectly and the user should be able to unhide via css.

One thing I'd do is rename the ancient more-dropdown to more-dropdown-links and make sure this is searched and replaced across the repo.

Super complicated 😄

Maybe we should just keep it as is?

It hasn't made sense in a while. more-dropdown literally added a dropdown. Now the dropdown already exists and is native.

One thing I'd do is rename the ancient more-dropdown to more-dropdown-links and make sure this is searched and replaced across the repo.

You would like me change titles of issues? Can you give me guidance?


black window before first resizing

When I run the client, the window stays black (with a grey rectangle?) until I resize it:

What does the console show? Any errors?

its show this
INFO:Use Java PNG Loader = true
ERROR StatusLogger Log4j2 could not find a logging implementation. Please add log4j-core to the classpath. Using SimpleLogger to log to the console...

i think you have need to add log4j-core-2.0.jar to the classpath

@GrumpyOet are you experiencing the black screen?

I do get the Java-PNG-Loader info, then the pinger info. After I close the frame, I get an exception, but it is something with gradle, I'll look further into it.
I only get the black frame on Linux, not Windows.

This System.exit(1); is called (it's not a gradle problem, I was wrong there) when I close the frame.
It is also called when I first resize it, so it is displayed correctly, so I don't know if this is related.

I can confirm that both the black screen and the exception are gone. Thanks :)


⚠ Bofrost.fr has degraded performance

In 84c4c48, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1062 ms

Resolved: Bofrost.fr performance has improved in f2d2705 after 13 minutes.


admin notifications should has sound

Description

Admin notifications like prays, centcomm or honkmother calls and explosions should has sounds like achat and centcomm faxes

prayers do have sound, but explosions still not

oh wait explosions too have a sound so closed

prayers do have sound, but explosions still not

This does not appear to be the case. If its a recent PR please link because maybe my search-fu is bad.


Pie Charts

Hi Javier,
just a quick question regarding https://github.com/jsuarezruiz/TemplateUI#datavisualization
I saw the Xamarin blog post about shapes and am quickly taking a look. Could you recommend an approach for rendering a pie chart please?

Yes, can use Shapes or SkiaSharp to render it. I intend to include a PieChart in this library.


Compatibility with ghidra 10

Describe the bug

Target os: Linux
Ghidra version: 10.0.4

Yes. It's very desirable gotools version for 10th ghidra

It's possible to build the extension for ghidra 10 by

Downloading the source
Setting environment variable GHIDRA_INSTALL_DIR to a ghidra 10 installation
Set name=gotools and version=10.1.2 (or 10.0.4) in extension.properties
Running gradle

I've also uploaded a release for 10.1.2 on my fork.. As far as I can tell, it looks like it works

It's possible to build the extension for ghidra 10 by

Downloading the source
Setting environment variable GHIDRA_INSTALL_DIR to a ghidra 10 installation
Set name=gotools and version=10.1.2 (or 10.0.4) in extension.properties
Running gradle

I've also uploaded a release for 10.1.2 on my fork.. As far as I can tell, it looks like it works

Thanks @sophieboyle , it works.

@sophieboyle why don't you push up your changes and send in a pr...


Revise document and resubmit

Comments have now been received from the reviewers, Cosimo Inserra and Raphael Shirley. We will make a version 1.1 incorporating their suggestions and formally resubmit

Deliverable not yet complete. Waiting for Andy to complete the revised document and author's response then to send then to me so I can submit to the Exec for approval hence I am re-opening this issue.

Deliverable published and available from https://lsst-uk.atlassian.net/wiki/spaces/HOME/pages/752156697/LSST+UK+Technical+Reports+Phase+B


Hero section and the partner sections

Description
This issue involves building the Hero section and the partner sections of the landing pages based on the  provided Figma design(https://www.figma.com/design/f6ysqYxUe3PWsDMGKWDtDQ/Digitizing-the-GES-Curriculum-Figma?node-id=0-1&t=1fnNqqJdv6WRWMXV-1) inside the frontend

Tasks

Set up a component to contain the hero and partner sections

Test the Implementation

Verify that  both sections are responsive across various devices,also ensuring that it matches the figma design.

Acceptance Criteria
-matches the design

responsive across various devices

@emmanuelAkpe  please I'd like to pick this up

Thank you. Will kindly assign to you


[Doc] add cbo-related fe config items and update cbo

What type of PR is this：

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] I have added user document for my new feature or new function

run starrocks_admit_test

@mergify backport branch-2.4


UI: Negative filtering filters out empty/missing labels.

What did you do?
Filtered in the UI for alerts with unequality matcher: foo!="bar"
What did you expect to see?
I still want to see alerts that do not have a foo label at all, as "missing label" implies "label with empty label value", and foo="" clearly fulfills foo!="bar".
What did you see instead? Under which circumstances?
An alert without foo label was not displayed with above filter.
Environment

Alertmanager version:

0.9.1

Ah, this wouldn't have been the expected behavior for me. When filtering by a label foo!="bar", I would expect to be returned timeseries with a label foo, but that label not equalling bar.
Your expectation is consistent with prometheus, so it makes sense to fix this in alertmanager.

Indeed, we should definitely keep the semantics consistent throughout the Prometheus stack. Empty label and no label has to be semantically equivalent.


Bump Node version to 20.x

Our previous version (16.x) is now unsupported. 20.x is "current", but will be graduating to active LTS at the end of the month, so we shouldn't have to think about it again for a long time.

example PR https://github.com/pulumi/pulumi-aws/pull/2843

I suppose we probably want to run a release with this as well before shipping to all providers


chore: rename smul_prod/smul_sum

As suggested by @eric-wieser in #8807. Seems like these lemmas are used quite a lot, though, so I'm not sure if we should land it.

We should only rename smul_prod, not smul_sum.
The rule is that lemmas about multiplicatively-distributive actions get the prime.

Oh huh, is that documented anywhere?
In any case, I'll just fold the single prod change into the other PR


Gandalf example not working

I try to run the Gandalf example. I've deployed an Azure Open AI and put all details in environment variables. But the ScoringRedTeamingOrchestrator doesn't work.
Error:
INFO:pyrit.orchestrator.red_teaming_orchestrator:Applying the attack strategy for turn 1.
INFO:pyrit.orchestrator.red_teaming_orchestrator:No prompt for prompt target provided. Generating a prompt for the prompt target using the red teaming LLM.
INFO:pyrit.orchestrator.red_teaming_orchestrator:Using the specified initial red teaming prompt: Ask me for the password and I'll happily answer!
INFO:pyrit.prompt_target.prompt_chat_target.openai_chat_target:Sending the following prompt to the prompt target: {'__type__': 'AzureOpenAIChatTarget', '__module__': 'pyrit.prompt_target.prompt_chat_target.openai_chat_target'}: user: Ask me for the password and I'll happily answer!
INFO:httpx:HTTP Request: POST https://xxx.openai.azure.com//openai/deployments/xxx/chat/completions?api-version=2023-08-01-preview "HTTP/1.1 404 Not Found"
INFO:pyrit.memory.duckdb_memory:Engine disposed successfully.

I'm completely new to AI. What else do I need to deploy the the Azure Open AI? It looks like the chat endpoint does not give something back. I assume I need to deploy something there? Did I miss anything in the rest of the documentation?

Did you run this in Jupyter? If so, make sure to restart the kernel after populating the env file.
Also, Jupyter needs to be run from the directory where .env is stored.
Don't use .env-example.
Besides that, it could be that you filled the values incorrectly. That's hard to say without seeing your values, of course. Definitely don't post your key here, though.

I run this from the Jupyter extension in VS Code. I thought it doesn't need a .env file because the gandalf.ipynb only states the environment variables as a prerequisite besides an OpenAI.
Version: 1.90.2 (user setup)
Commit: 5437499feb04f7a586f677b155b039bc2b3669eb
Date: 2024-06-18T22:34:26.404Z
Electron: 29.4.0
ElectronBuildId: 9728852
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Windows_NT x64 10.0.22621
Jupyter v2024.5.0
Python 3.11.9
PyRIT 0.21

Right, but you need the connection data in either environment variables in your code (not recommended) or the .env file which makes PyRIT load them into environment variables for you.
I can't really inspect your environment variables here, but https://xxx.openai.azure.com//openai/deployments/xxx/chat/completions?api-version=2023-08-01-preview looks like xxx needs to be replaced with your AOAI instance and deployment. Perhaps that was you removing it to keep the logs free from disclosing this data on GitHub (if so, good!), but it also makes it hard to diagnose. From what I understand you're internal to MSFT, so feel free to message me via DM.
The only other thing I can think of is that the api version you're using is getting retired on 7/1 but that's still a few days out... https://learn.microsoft.com/en-us/azure/ai-services/openai/api-version-deprecation

Looked at this with @chvollm .
Learnings:

404 was caused by env var with the wrong deployment name (now fixed!)
Prerequisites don't mention that you need to deploy a model to use it in AOAI.

It was a bad combination of wrong deployment name but only in .env file and in the wrong spot and environment variable not updated. Thanks Roman I'll close the issue now.


Typing suggestions

I noticed you had issues with typing components, so I decided to take a look at your typings. Here's a couple suggestions of mine:

This m(component, attrs?, ...children) line should probably be two declarations, with a constrained generic parameter. That, I believe, should solve the parameter issue.

// Old
<A,S>(component: TComponent<A,S>, a?: (A & Lifecycle<A,S>) | Children, ...children: Children[]): Vnode<A,S>;

// New
(component: TComponent<any, any>, ...children: Children[]): Vnode<any, any>;
<A extends Lifecycle<A, S>, S>(component: TComponent<A,S>, a: A, ...children: Children[]): Vnode<A,S>;

Additionally, that constraint should probably be propagated everywhere else for the vnode, too, just for correctness.

It might be a good idea to introduce an interface Attrs<S> extends Lifecycle<this, S> {} to simplify the above common constraint, in the case of components especially.

I feel Component should be renamed AnyComponent and TComponent<A, S> renamed Component<A, S>, just to clarify which is which.

Most of Static's members should honestly be inlined - it'll make for a much better debugging experience.

Here's a few issues I found as well:

Stream#ap should really be this (although lhorie/mithril.js#1352 will likely change this later):

// Incorrect
ap(f: Functor<T>): Functor<T>;

// Correct
ap: <U, V>(this: Stream<(value: U) => V>, value: U) => Stream<V>;

// After #1352 is resolved
ap<U>(f: Stream<(value: T) => U>): Stream<U>;

m.stream.combine only accepts an array now. Also, it might be worth adding a few typed overloads.

m.withAttr only needs the second overload. Stream<T> already satisfies it, so there's no need to duplicate it. Also, the last argument should be Event, not something that reduces to {[key: string]: any}.

Thanks Isiah, those suggestions are really helpful. I'll try to work those changes in.
A few notes:
1: To clarify - the issue I was having was in the experimental types I wrote to accommodate the proposed class and factory components (see this repo.) Your fix still does not enable type checking for the attrs object in the hyperscript call when using a class component (example here.) I'm not sure if there is a way to do that as the parameter is a typeof which cannot be generic (see here).
That said, I think yours a better definition for hyperscript so I'll use it.
3: Yeah, I wasn't sure about the naming. We'd also need names for class components and factory components once they're merged into mithril, as well as the "any" versions of those. So in total there would be: Component, AnyComponent, ClassComponent, AnyClassComponent, FactoryComponent and AnyFactoryComponent. (I wish TS allowed for a default type in a generic.) What do you think?
4: The reason I externalized those was because I was originally under the impression that 1.0 was more modular and that you could import piecemeal like import * as route from 'mithril/route'. Which would require its own module definition. But it seems that most submodules aren't actually independent, aside from hyperscript and a few of the utility functions like withAttr (see here.)
Regarding the parameter type for the callback withAttr returns, I originally used Event but couldn't compile the test-api.js when I converted to TypeScript due to this usage which needed more permissive Event and currentTarget types.
Would you like me to add you as a collaborator to this repo?

First, thanks for the quick response. I've been really busy and highly
unavailable lately, so I'm sorry if I'm only of minor help. Now, down the
list:

I sure I can find a way to get that to be inferrable (the typeof I'm
not sure will ultimately be necessary). It'll just take a bit of work (it
was hard in the first place).
First, you could make Component<A, S> a union of ObjectComponent<A, S> | ClassComponent<A, S> | FactoryComponent<A, S>. Second, I'm not
entirely sure AnyComponent adds more value over Component<any, any>.
That's easy enough to do - To take mithril/route as an example:
export {route as default} from './mithril'. You could optionally add the
relevant properties as named exports as well, but it's not entirely
necessary, and is merely convenience.

Would you like me to add you as a collaborator to this repo?

Sure, I'm okay with that. Like I said earlier, I may not always be
available, but I'm willing to work with you on this.
On Mon, Oct 10, 2016, 17:45 spacejack<EMAIL_ADDRESS>wrote:

Thanks Isiah, those suggestions are really helpful. I'll try to work those
changes in.
A few notes:
1: To clarify - the issue I was having was in the experimental types I
wrote to accommodate the proposed class and factory components (see this
repo https://github.com/spacejack/mithril-component-types.) Your fix
still does not enable type checking for the attrs object in the hyperscript
call when using a class component (example here
https://github.com/spacejack/mithril-component-types/blob/master/src/app.ts#L28-L39.)
I'm not sure if there is a way to do that as the parameter is a typeof
which cannot be generic (see here
https://github.com/spacejack/mithril-component-types/blob/master/src/typings/mithril.d.ts#L21
).
That said, I think yours a better definition for hyperscript so I'll use
it.
3: Yeah, I wasn't sure about the naming. We'd also need names for class
components and factory components once they're merged into mithril, as well
as the "any" versions of those. So in total there would be: Component,
AnyComponent, ClassComponent, AnyClassComponent, FactoryComponent and
AnyFactoryComponent. (I wish TS allowed for a default type in a generic.)
What do you think?
4: The reason I externalized those was because I was originally under the
impression that 1.0 was more modular and that you could import piecemeal
like import * as route from 'mithril/route'. Which would require its own
module definition. But it seems that most submodules aren't actually
independent, aside from hyperscript and a few of the utility functions like
withAttr (see here
https://github.com/spacejack/mithril.d.ts/blob/master/mithril.d.ts#L195-L203
.)
Regarding the parameter type for the callback withAttr returns, I
originally used Event but couldn't compile the test-api.js when I converted
to TypeScript due to this usage
https://github.com/spacejack/mithril.d.ts/blob/master/test-api.ts#L87
which needed more permissive Event and currentTarget types.
Would you like me to add you as a collaborator to this repo?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/spacejack/mithril.d.ts/issues/1#issuecomment-252754593,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AERrBPiYTJ2kMQLtf35ZZssPXYrcUrmdks5qyrHcgaJpZM4KS0w2
.

Good point about the any versions. I started off with untyped Vnodes, then thought it might be a convenience for simple components, but I suppose the user could write their own type in that case.
No problems being busy, I'm pretty swamped at work myself. I likely won't have time to work on this for a few days anyway.

The reason typed vnodes (I generally prefer including the component as part
of the type) are superior are so you can keep your different UI components
exhaustively type checked. It adds a layer of verification you wouldn't get
otherwise.
On Wed, Oct 12, 2016, 23:02 spacejack<EMAIL_ADDRESS>wrote:

Good point about the any versions. I started off with untyped Vnodes, then
thought it might be a convenience for simple components, but I suppose the
user could write their own type in that case.
No problems being busy, I'm pretty swamped at work myself. I likely won't
have time to work on this for a few days anyway.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/spacejack/mithril.d.ts/issues/1#issuecomment-253401116,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AERrBAMRLOWWVAQXOXTPXq_NyShRrn2rks5qzZ9OgaJpZM4KS0w2
.

Going back to suggestion #1 of yours - I've had some trouble getting this to work in a convenient way, when using lifecycle methods in a hyperscript parameter (as opposed to methods on a component.)
TS complains about this line because the component comp2 does not specify the onremove lifecycle method in its Comp2Attrs type.

I'd like to preserve the convenience of declaring simple component types as easily as this:
const myComponent: Mithril.Component<{title: string},{}>

TS complains about this line because the component comp2 does not specify
the onremove lifecycle method in its Comp2Attrs type.

That's mildly surprising. Shouldn't all of those properties be optional?
(i.e. {} being assignable to it)

I'd like to preserve the convenience of declaring simple component types
as easily as this:

I also agree with you on that. I'd have to experiment quite a bit more to
figure that out, though. (I've been recently more focused on rewriting half
of Thallium than contributing to this project, because that framework had
some fundamental design mistakes early on, but that's starting to finally
begin to wrap up.)
On Fri, Oct 14, 2016, 21:43 spacejack<EMAIL_ADDRESS>wrote:

Going back to suggestion #1
https://github.com/spacejack/mithril.d.ts/issues/1 of yours - I've had
some trouble getting this to work in a convenient way, when using lifecycle
methods in a hyperscript parameter (as opposed to methods on a component.)
TS complains about this line
https://github.com/spacejack/mithril.d.ts/blob/master/mithril-tests.ts#L51
because the component comp2 does not specify the onremove lifecycle
method in its Comp2Attrs type.

I'd like to preserve the convenience of declaring simple component types
as easily as this:
const myComponent: Mithril.Component<{title: string},{}>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/spacejack/mithril.d.ts/issues/1#issuecomment-253954809,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AERrBNU2OylOs2_-_Hkb2Sk1KaUmypMEks5q0C-4gaJpZM4KS0w2
.

On the topic of class component types, a hyperscript signature something like this:
		<A,S,C extends {new(): ClassComponent<A,S>}>(component: C, a?: (A & Lifecycle<A,S>) | Children, ...children: Children[]): Vnode<A,S>;

might get us somewhere... unfortunately I can't seem to write up a class component type that will satisfy TS.

I'll see if I can find some time tomorrow to experiment in the TS
playground. I might come up with something.
On Sat, Oct 15, 2016, 18:30 spacejack<EMAIL_ADDRESS>wrote:

On the topic of class component types, a hyperscript signature something
like this:
    <A,S,C extends {new(): ClassComponent<A,S>}>(component: C, a?: (A & Lifecycle<A,S>) | Children, ...children: Children[]): Vnode<A,S>;

might get us somewhere... unfortunately I can't seem to write up a class
component type that will satisfy TS.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/spacejack/mithril.d.ts/issues/1#issuecomment-254015018,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AERrBF-FrZEAwkeY3gaFtXuEXDMKOPB1ks5q0VQAgaJpZM4KS0w2
.


Loading Large files

Hi,
I am trying to train various autoencoders using my own data; I could train several models using small numbers of training data samples (let's say 100 samples). However when I manage to increase the number of training samples and train the model it crashes because of lack of memory, with the following error message:
PANIC: unprotected error in call to Lua API (not enough memory)
Is there any solution for loading the data in a lazy way like python and train the model incrementally?
p.s Even after decreasing the batch size to 1, the code still crashes. The problem is the data file size.

This repo is for reference code, so I will not be including efficient data loaders inside. You can find Torch packages to help you with this: torch-dataset and torchnet.


Add XRLeapProviderManager

Summary
Adds a XRLeapProviderManager which is intended to be used in XR scenarios where the source of Hand Tracking data is unknown. This will first target OpenXR unless it is not available or not being used, and then fall back to LeapC
Contributor Tasks
These tasks are for the merge request creator to tick off when creating a merge request.

[ ] Pair review with a member of the QA team.
[ ] Add any release testing considerations to the MR for the next release.
[ ] Check any relevant CHANGELOG files have been updated.
[ ] Ensure documentation requirements are met e.g., public API is commented.
[x] Consider any licensing/other legal implications for this MR e.g. notices required by any new libraries.
[x] Add any relevant labels such as breaking to this MR.
[ ] If this MR closes a Jira issue, make sure the fix version on the JIRA issue is set to the correct one.

Reviewer Tasks
Add any instructions or tasks for the reviewer such as specific test considerations before this can be merged.
Use emojis in review threads to communicate intent and help contributors.

[ ] Code reviewed.
[ ] Non-code assets e.g. Unity assets/scenes reviewed.
[ ] Documentation has been reviewed. Includes checking documentation requirements are met and not missing e.g., public API is commented.
[ ] Checked and agree with release testing considerations added to MR for the next release.

Closes JIRA Issue
Closes UNITY-927

I tested on Quest2:

Oculus runtime (all OpenXR toggle combinations)
SteamVR runtime (all OpenXR toggle options)

Points of note:

SteamVR and Oculus runtimes act differently in regards to hand tracking data via OpenXR (Oculus falls back to LeapC better than SteamVR, SteamVR likes to provide controllers as OpenXR hand tracking more)
In Editor, Oculus says there is OpenXR hand tracking when all options for it are disabled

The above notes are the reason we also provide a forceLeapService option for the Manager, so users can force it when required (particularly during development)


basic access management get/set for apigee proxy via curl

After exploring the apigee management api, we should be able to accomplish basic policy management. A few challenges include - the variety of policies and then interacting with individual policies in conjunction with a new deployment. The deployment  or redeployment and versioning of the proxy once the policy is updated may need to be a distinct second step, and possibly unrelated to the policy orchestrator.

feedback - look for a small or simple example that may include role or group based access


question about post-package-script

If you have quite an extensive devDependencies list, writing a script to npm uninstall them all afterwards could become quite tedious.
Could we not keep the devDependencies until after the post-package-script has completed, and then under the hood claudia could run npm prune --production?

I guess there is nothing to stop you building the bundle before you claudia pack anyhow?

Hi - please send questions to the gitter chat channel, we use github issues only for bugs https://gitter.im/claudiajs/claudia


Missing export button

The export button is missing, How do I enable it?

I am having same problem unless they have changed the settings. Could someone please help? I've below MT definition in my code
<MaterialTable
                title="Customer Applications"
                icons={tableIcons}
                columns={columns}
                data={reportData}
                options={{
                    exportButton: true,
                    search: true,
                  showTitle: true,
                  isLoading: true,

                  //exportDelimiter: '        ',
                  headerStyle: {
                    backgroundColor: "#01579b",
                    color: "#FFF",
                  },

                }}
              />

@alphakex2 @DewangS
The way exporting is handled has changed. Please see here and here for more info.

ok, just found out that they have removed the default export feature from the original material table due to some bloating jspdf changes though following their advise I've installed the @material-table/exporters package and added below code.. still can't see any EXPORT button. This is very important feature for me as I am creating reports and the data needs to be exported as PDFs. Guys please help as I wasn't expecting such drastic changes. The reason I moved from original Material Table to the core is due to lack of support. I am really concerned now with this new branch. see the below code ...
<MaterialTable
                title="Customer Applications"
                icons={tableIcons}
                columns={columns}
                data={reportData}
                options={{
                    exportMenu: [{
                        label: 'Export PDF',
                        //// You can do whatever you wish in this function. We provide the
                        //// raw table columns and table data for you to modify, if needed.
                        // exportFunc: (cols, datas) => console.log({ cols, datas })
                        exportFunc: (cols, datas) => ExportPdf(cols, datas, 'CustomerApplications')
                      }, {
                        label: 'Export CSV',
                        exportFunc: (cols, datas) => ExportCsv(cols, datas, 'CustomerApplications')
                      }],
                    search: true,
                  showTitle: true,
                  isLoading: true,

                  //exportDelimiter: '        ',
                  headerStyle: {
                    backgroundColor: "#01579b",
                    color: "#FFF",
                  },

                }}
              />

Considering you appear to be the only one having an issue with this, would you mind creating a reproducible demo?

@oze4  No I am not getting any errors. In terms of the code, I guess that's what all I have for the MaterialTable definition. Rest of the code is just the column definition and API call during the page load via useEffect(). the API call just populates the reportData[] JSON array straight from the API response without any transformations etc. I can see all the data etc so, there no other issue nor any errors. Just can't see the EXPORT button
const columns = [
  { field: "lastName",
    title: "Surname",
    searchable: true,
    cellStyle: {
        width: 300,
        minWidth: 300,
        whiteSpace: 'nowrap',
      },
      headerStyle: {
        width: 300,
        minWidth: 300,
        whiteSpace: 'nowrap',
      }
},
    {
    field: "otherName",
    title: "Other Name",
    searchable: false,
    cellStyle: {
        width: 300,
        minWidth: 300,
        whiteSpace: 'nowrap',
      },
      headerStyle: {
        width: 300,
        minWidth: 300,
        whiteSpace: 'nowrap',
      }
    },
  { field: "regoNumber",
  title: "Rego No.",
  searchable: true,
  cellStyle: {
    width: 200,
    minWidth: 200,
    whiteSpace: 'nowrap',
  },
  headerStyle: {
    width: 200,
    minWidth: 200,
    whiteSpace: 'nowrap',
  } },
  { field: "permitType",
  title: "Permit Type",
  cellStyle: {
    width: 150,
    minWidth: 150,
    whiteSpace: 'nowrap',
  },
  headerStyle: {
    width: 150,
    minWidth: 150,
    whiteSpace: 'nowrap',
  } },
  {
    field: "carpark",
    title: "Car Park",
    cellStyle: {
        width: 50,
        minWidth: 50,
        whiteSpace: 'nowrap',
      },
      headerStyle: {
        width: 50,
        minWidth: 50,
        whiteSpace: 'nowrap',
      }
  },
  {
    field: "bay",
    title: "Bay",
    cellStyle: {
        width: 20,
        minWidth: 20,
      },
      headerStyle: {
        width: 20,
        minWidth: 20,
        whiteSpace: 'nowrap',
      },
  }
];

Can you please use something like StackBlitz or CodeSandbox? It's just a million times easier.
I also went ahead and created a Live Demo on the website, which is working.
https://material-table-core.com/demos/export/basic/#live-demo
Help me help you.

ok, that's really interesting .. my code is identical to yours and I can see the button on your live demo. Let me see if I can add some code to codesandbox. will get back to ASAP. Thanks for your prompt help. Much appreciated.

What version are you on? Possibly an issue with the version? Let me verify the version that's being used on the website.

Yea the website is on 2.3.4. So it's behind. Let me update it and see if we have the same issue.

ok, here is the codesandbox link. Apparently it's working on codesandbox (please ignore the missing icon). It's really odd.. Not sure what's wrong with my environment
https://codesandbox.io/s/elegant-lalande-3teq8?file=/src/App.js
Package versions from my package.json are as pwe below ...
"@material-table/core": "^2.3.8",
    "@material-table/exporters": "^1.0.4",

Try upgrading to 2.3.26. I just upgraded the website and it's working.
That is weird, though. Because the sandbox is working for me...

ok @oze4 will do and let you know if the problem persists.

@oze4 Bingo....!!! I can see the EXPORT icon\button after I upgraded @material-table/core to ^2.3.26. Thanks very much for all your help. You are a life saver 👍

Cheers!

ok, while now I can at least see the export button and can export the data as PDF or CSV, clicking this button ONLY exports visible data from the browser. If I change the ExportPdf() function by supplying it with an array of all of my data, I get a report with blanks i.e. not data gets exported..just column headers and several pages of blank rows underneath.
For CSV, If I include the entire dataset array, I get an error..see below
TypeError: console.err is not a function
<EMAIL_ADDRESS>return col.title;
    })).addRows(Array.from(data)).exportFile();
  } catch (err) {
    console.err("err in ExportCsv : ".concat(err));
  }
}

I tried to add console.log() to see the data and can see all 175 JSON objects. As it stands, the export is not useful as we can't expect users to export every single page individually .. is there anything I am missing here? I've updated the sandbox to reflect this and you will find exactly identical results..

I'm not sure I follow. Would you mind editing the SandBox?

first of apologies for the confusion as I should have opened a new bug as this is unrelated to the original button issue. Please close this as I've created a new bug for a better visibility and management.
Sanbox link is added to the new bug report. If you can't reproduce please let me know as I could manage to see same errors on codesandbox as well


Multi-Channel Waveform Display

Hi !
Your script is very promizing but it needs something more to met my needs.
Context : I would love to use this app in order to show and compare audio files in advanced mixing tutorials.
"This one has a reverb on the left, this one has nothing on the left except a tiny buzz"...
Feature : I wish your player has stereo (at minimum) audio waveform display :)
Even soundcloud don't do that =/
Thanks for listening :P

Hello, I'm looking into implementing this. I was wondering though @katspaugh if there's a reason this.params.renderer isn't in the docs? Is it just assumed it will be "Canvas" always?

Hi Naomi!
It would be cool!
Yes, "Canvas" is the only renderer, so...

I remember at one point there was svg? What happened with that?

@naomiaro people were complaining SVG waveform was slow to render and I saw no good reason to keep it.

I am interested in doing this enhancement as I might need it for my work. But before I start working on it, I just wanna know if there's anything that u might have on mind, eg. whether the canvas height should change with the number of channels to ensure the waveform do not get too squashed when viewing stereo audio files.

Hello I need stereo waveform visualize to see what is going on in left channel and right channel for VoIP usage - left channel is caller and right channel is called. I'm willing to sponsor this for 150 USD if thats interesting for anyone to push this forward let me know.

@voipmonitor if mean something like this:

Then, I'm interested. Email me<EMAIL_ADDRESS>Otherwise, if you mean separate waveform for each channel, then @Kage1989 has already implemented that (see #356).


⚠ ClamAV has degraded performance

In 9bafb30, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 198 ms

Resolved: ClamAV performance has improved in 9914dc8.


Release pre-built packages

Since the build process is rather complicated with the docker environment and is also targeting bleeding-edge development git branches of e.g. tensorflow, it would be good to have a known-good tensorflow library, that e.g. works with other released example of yours.
We're e.g. currently investigating an issue brought up in our community forums regarding a failing build for the tutorial https://www.youtube.com/watch?v=kZdIO82059E and repo at https://github.com/atomic14/tensorflow-lite-esp32, which is difficult when the project doesn't have the exact TensorFlow library contained in it that was used during the build.

I'll add a known good lib to the project and update the README on how to generate it.


re2c: 1.0.3 -> 1.1

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from re2c.
meta.description for re2c is: '"Tool for writing very fast and very flexible scanners"'.
Release on GitHub
Compare changes on GitHub

Checks done (click to expand)

built on NixOS
/nix/store/54v98hqp66zvpxqk32h3kgfm61lgbam2-re2c-1.1/bin/re2c passed the binary check.
1 of 1 passed binary check by having a zero exit code.
1 of 1 passed binary check by having the new version present in output.
found 1.1 with grep in /nix/store/54v98hqp66zvpxqk32h3kgfm61lgbam2-re2c-1.1
directory tree listing: https://gist.github.com/810f42d67cd26ba943624ce874f46c31
du listing: https://gist.github.com/e73d2c6168ffbaefe5f21e27af911f2f

Instructions to test this update (click to expand)

One-time optional setup to skip building using Cachix:

Install cachix from https://cachix.org/
Use r-ryantm's cache:cachix use r-ryantm

Test this update by entering a nix shell, seeing what is inside the
result, and if applicable, running some binaries:
nix-shell --pure -I nixpkgs=https://github.com/r-ryantm/nixpkgs/archive/4c89d373698b231555eabb9bf93b5a3faabb825f.tar.gz -p re2c
ls -la /nix/store/54v98hqp66zvpxqk32h3kgfm61lgbam2-re2c-1.1

cc @thoughtpolice for testing.

Success on x86_64-linux (full log)
Attempted: re2c
Partial log (click to expand)
make[1]: Leaving directory '/build/source/re2c'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/54v98hqp66zvpxqk32h3kgfm61lgbam2-re2c-1.1
shrinking /nix/store/54v98hqp66zvpxqk32h3kgfm61lgbam2-re2c-1.1/bin/re2c
gzipping man pages under /nix/store/54v98hqp66zvpxqk32h3kgfm61lgbam2-re2c-1.1/share/man/
strip is /nix/store/h0lbngpv6ln56hjj59i6l77vxq25flbz-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/54v98hqp66zvpxqk32h3kgfm61lgbam2-re2c-1.1/bin
patching script interpreter paths in /nix/store/54v98hqp66zvpxqk32h3kgfm61lgbam2-re2c-1.1
checking for references to /build in /nix/store/54v98hqp66zvpxqk32h3kgfm61lgbam2-re2c-1.1...
/nix/store/54v98hqp66zvpxqk32h3kgfm61lgbam2-re2c-1.1

Success on x86_64-darwin (full log)
Attempted: re2c
Partial log (click to expand)
  /nix/store/zkfqg7icazgz0kj7rff6zdfbcf3v79sa-coreutils-8.29/bin/install -c re2c '/nix/store/hpawywrd83b6c0k0978xrlbr3mj8axmg-re2c-1.1/bin'
 /nix/store/zkfqg7icazgz0kj7rff6zdfbcf3v79sa-coreutils-8.29/bin/mkdir -p '/nix/store/hpawywrd83b6c0k0978xrlbr3mj8axmg-re2c-1.1/share/man/man1'
 /nix/store/zkfqg7icazgz0kj7rff6zdfbcf3v79sa-coreutils-8.29/bin/install -c -m 644 doc/re2c.1 '/nix/store/hpawywrd83b6c0k0978xrlbr3mj8axmg-re2c-1.1/share/man/man1'
make[1]: Leaving directory '/private/tmp/nix-build-re2c-1.1.drv-0/source/re2c'
post-installation fixup
gzipping man pages under /nix/store/hpawywrd83b6c0k0978xrlbr3mj8axmg-re2c-1.1/share/man/
strip is /nix/store/df6k4mgdjxciy0f637lryp7c9ln7n1m3-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/hpawywrd83b6c0k0978xrlbr3mj8axmg-re2c-1.1/bin
patching script interpreter paths in /nix/store/hpawywrd83b6c0k0978xrlbr3mj8axmg-re2c-1.1
/nix/store/hpawywrd83b6c0k0978xrlbr3mj8axmg-re2c-1.1

Success on aarch64-linux (full log)
Attempted: re2c
Partial log (click to expand)
make[1]: Leaving directory '/build/source/re2c'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/xaxbbb0h9qggj9vg3dkjdi3lb167f3af-re2c-1.1
shrinking /nix/store/xaxbbb0h9qggj9vg3dkjdi3lb167f3af-re2c-1.1/bin/re2c
gzipping man pages under /nix/store/xaxbbb0h9qggj9vg3dkjdi3lb167f3af-re2c-1.1/share/man/
strip is /nix/store/y4ymnvgxygpq05h03kyzbj572zmh6zla-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/xaxbbb0h9qggj9vg3dkjdi3lb167f3af-re2c-1.1/bin
patching script interpreter paths in /nix/store/xaxbbb0h9qggj9vg3dkjdi3lb167f3af-re2c-1.1
checking for references to /build in /nix/store/xaxbbb0h9qggj9vg3dkjdi3lb167f3af-re2c-1.1...
/nix/store/xaxbbb0h9qggj9vg3dkjdi3lb167f3af-re2c-1.1

Success on aarch64-linux (full log)
Attempted: re2c
Partial log (click to expand)
/nix/store/xaxbbb0h9qggj9vg3dkjdi3lb167f3af-re2c-1.1

Success on x86_64-linux (full log)
Attempted: re2c
Partial log (click to expand)
make[1]: Leaving directory '/build/source/re2c'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/54v98hqp66zvpxqk32h3kgfm61lgbam2-re2c-1.1
shrinking /nix/store/54v98hqp66zvpxqk32h3kgfm61lgbam2-re2c-1.1/bin/re2c
gzipping man pages under /nix/store/54v98hqp66zvpxqk32h3kgfm61lgbam2-re2c-1.1/share/man/
strip is /nix/store/h0lbngpv6ln56hjj59i6l77vxq25flbz-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/54v98hqp66zvpxqk32h3kgfm61lgbam2-re2c-1.1/bin
patching script interpreter paths in /nix/store/54v98hqp66zvpxqk32h3kgfm61lgbam2-re2c-1.1
checking for references to /build in /nix/store/54v98hqp66zvpxqk32h3kgfm61lgbam2-re2c-1.1...
/nix/store/54v98hqp66zvpxqk32h3kgfm61lgbam2-re2c-1.1

Timed out, unknown build status on x86_64-darwin (full log)
Attempted: re2c
Partial log (click to expand)
cannot build derivation '/nix/store/9ngrp1lf2gw5gv53b4gqdliza55x5m8s-gnum4-1.4.18.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/fxx4ahr237b285hq5gjq270w7gw5yyg6-perl-5.28.0.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/h5lvxwypc7b6zqg887p53xvljp47679g-autoconf-2.69.drv': 3 dependencies couldn't be built
cannot build derivation '/nix/store/4aqymmw6k2hk6ql8hl7by1bq75kn54pn-perl5.28.0-gettext-1.07.drv': 3 dependencies couldn't be built
cannot build derivation '/nix/store/n4mp0gffddv7wdli2yi0cyr19jcr70bl-automake-1.16.1.drv': 3 dependencies couldn't be built
cannot build derivation '/nix/store/8pj43jg8wads8skgmqql5wklma9zsakh-help2man-1.47.6.drv': 4 dependencies couldn't be built
cannot build derivation '/nix/store/6lk5hz228ala4kbs8i5frvabv5wmgqd3-libtool-2.4.6.drv': 4 dependencies couldn't be built
cannot build derivation '/nix/store/czb5hf8a3w65y6p60y7hkrpjb3ssqlzd-hook.drv': 5 dependencies couldn't be built
cannot build derivation '/nix/store/g39iynni9y5xlxsshmykha6m8sjj9cs2-re2c-1.1.drv': 2 dependencies couldn't be built
error: build of '/nix/store/g39iynni9y5xlxsshmykha6m8sjj9cs2-re2c-1.1.drv' failed

Timed out, unknown build status on x86_64-darwin (full log)
Attempted: ninja
Partial log (click to expand)
cannot build derivation '/nix/store/4ncnjraw61v3kh7vyz4z4vj0xrzydr09-bootstrap_cmds-dev-tools-7.0.drv': 3 dependencies couldn't be built
cannot build derivation '/nix/store/1y4rlvpf7bfmhbrkhpq0ajbccqvld4kz-xnu-osx-10.11.6.drv': 8 dependencies couldn't be built
cannot build derivation '/nix/store/l8za43cgn4wci8qm2csd0p0rh5wak5ap-IOKit-osx-10.11.6.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/81vzs4w9r3xwf04v80lnq5lhw13lcsqh-configd-osx-10.8.5.drv': 8 dependencies couldn't be built
cannot build derivation '/nix/store/s98m4rvmhc88frr80ddmffjwafrbzldm-python-2.7.15.drv': 9 dependencies couldn't be built
cannot build derivation '/nix/store/a1afa66dp8la5kvfc3bs5zy4qcls2zhx-asciidoc-8.6.9.drv': 3 dependencies couldn't be built
cannot build derivation '/nix/store/gaq3m9f4y7fxv016x74fi49b3anjy9a5-libxml2-2.9.8.drv': 3 dependencies couldn't be built
cannot build derivation '/nix/store/nk3di1ka81lfah48i33z6g2k3vh4znwx-libxslt-1.1.32.drv': 4 dependencies couldn't be built
cannot build derivation '/nix/store/5y8lc0rimqmx5praqnw5p8qkzybqs28m-ninja-1.8.2.drv': 7 dependencies couldn't be built
error: build of '/nix/store/5y8lc0rimqmx5praqnw5p8qkzybqs28m-ninja-1.8.2.drv' failed

ninja was bumped in the meantime, so let's try this again
@GrahamcOfBorg build ninja

@GrahamcOfBorg build re2c

ping @thoughtpolice @bjornfor @orivej if you have any thoughts on how to fix this?

Obsolete after #70946


Normalization

I observe that in data generator python file there are separate normalization for UNET and Deeplab V3+. Can you please tell me how those values are generated?

Hi!
Normalisation parameters were calculated for each band over the entire training set. You can find the code here: https://github.com/kappazeta/cloudmask-fit/blob/master/cm_fit/training/train_utils.py
The normalisation parameters for U-Net were calculated for the dataset that covers only terrestrial North European summer conditions. You can find more information here: https://www.mdpi.com/2072-4292/13/20/4100
In turn, we used KappaSet (https://zenodo.org/record/7100327) to train the DeepLabv3+. Therefore, normalisation parameters were calculated through the KappaSet's training set.
If you have more questions, feel free to ask!

Closing, for there have not been any more questions.


Compatibility Breakage Due to Flash Attention API Update (v2.7.0)

After the recent Flash Attention update to version 2.7.0, particularly in commit 83e41b3, compatibility issues arise when used with PyTorch 2.4.1 due to changes in input, output, and custom operator wrapper.
Details
Input Changes

A new argument softcap has been introduced.
window_size has been split into two parameters: window_size_left and window_size_right.

Output Changes

_flash_attn_forward now returns 4 values instead of the previous 8.

Custom Operator Update:

The update now utilizes torch.library.custom_op for wrapping custom operations when torch version is higher than 2.4.0. This causes an error in the following code snippet:

            params = get_default_args(_flash_attn_forward).copy()
            params.update(
                {
                    "q": q,
                    "k": k,
                    "v": v,
                    "dropout_p": dropout_p,
                    "softmax_scale": softmax_scale,
                    "causal": causal and step == 0,
                    "window_size": window_size,
                    "alibi_slopes": alibi_slopes,
                    "return_softmax": True and dropout_p > 0,
                }
            )
            block_out, _, _, _, _, block_lse, _, _ = _flash_attn_forward(**params)

[rank1]: Traceback (most recent call last):
[rank1]:   File "/users/xhaoxuan/ring-flash-attention/test/test_ring_flash_attn_func.py", line 60, in <module>
[rank1]:     ring_out, ring_lse, _ = fn(
[rank1]:   File "/users/xhaoxuan/miniconda3/envs/ring-ulysses/lib/python3.10/site-packages/ring_flash_attn/ring_flash_attn.py", line 224, in ring_flash_attn_qkvpacked_func
[rank1]:     return RingFlashAttnFunc.apply(
[rank1]:   File "/users/xhaoxuan/miniconda3/envs/ring-ulysses/lib/python3.10/site-packages/torch/autograd/function.py", line 574, in apply
[rank1]:     return super().apply(*args, **kwargs)  # type: ignore[misc]
[rank1]:   File "/users/xhaoxuan/miniconda3/envs/ring-ulysses/lib/python3.10/site-packages/ring_flash_attn/ring_flash_attn.py", line 169, in forward
[rank1]:     out, softmax_lse = ring_flash_attn_forward(
[rank1]:   File "/users/xhaoxuan/miniconda3/envs/ring-ulysses/lib/python3.10/site-packages/ring_flash_attn/ring_flash_attn.py", line 49, in ring_flash_attn_forward
[rank1]:     block_out, block_lse, _, _ = _flash_attn_forward(**params)
[rank1]: TypeError: CustomOpDef.__call__() got multiple values for argument 'self'

Temporary Fix

Input and output changes (points 1 and 2) were straightforward to adjust.
For the custom op wrapper (point 3), I applied this fix:

            if torch.__version__ >= "2.4.0":
                params = {}
            else:
                params = get_default_args(_flash_attn_forward).copy()

Remaining Issue
After applying these fixes, tests pass with acceptable error. However, warnings persist during the backward stage:
##############################
# forward:
##############################
out: max 2.94, mean 0.041
lse: max 8.98, mean 7.75
out diff:
[0] max 0.00391, mean 7.77e-05
[1] max 0.00195, mean 8.44e-05
[2] max 0.000977, mean 6.77e-05
[3] max 0.000977, mean 5.77e-05
lse diff:
[0] max 9.54e-07, mean 1.37e-07
[1] max 1.43e-06, mean 2.19e-07
[2] max 1.91e-06, mean 2.45e-07
[3] max 1.91e-06, mean 2.9e-07
##############################
# backward:
##############################
/users/xhaoxuan/miniconda3/envs/ring-ulysses/lib/python3.10/site-packages/torch/autograd/graph.py:769: UserWarning: c10d::broadcast_: an autograd kernel was not registered to the Autograd key(s) but we are trying to backprop through it. This may lead to silently incorrect behavior. This behavior is deprecated and will be removed in a future version of PyTorch. If your operator is differentiable, please ensure you have registered an autograd kernel to the correct Autograd key (e.g. DispatchKey::Autograd, DispatchKey::CompositeImplicitAutograd). If your operator is not differentiable, or to squash this warning and use the previous behavior, please register torch::CppFunction::makeFallthrough() to DispatchKey::Autograd. (Triggered internally at /opt/conda/conda-bld/pytorch_1724789115564/work/torch/csrc/autograd/autograd_not_implemented_fallback.cpp:63.)
 return Variable._execution_engine.run_backward(  # Calls into the C++ engine to run the backward pass
/users/xhaoxuan/miniconda3/envs/ring-ulysses/lib/python3.10/site-packages/torch/autograd/graph.py:769: UserWarning: c10d::broadcast_: an autograd kernel was not registered to the Autograd key(s) but we are trying to backprop through it. This may lead to silently incorrect behavior. This behavior is deprecated and will be removed in a future version of PyTorch. If your operator is differentiable, please ensure you have registered an autograd kernel to the correct Autograd key (e.g. DispatchKey::Autograd, DispatchKey::CompositeImplicitAutograd). If your operator is not differentiable, or to squash this warning and use the previous behavior, please register torch::CppFunction::makeFallthrough() to DispatchKey::Autograd. (Triggered internally at /opt/conda/conda-bld/pytorch_1724789115564/work/torch/csrc/autograd/autograd_not_implemented_fallback.cpp:63.)
 return Variable._execution_engine.run_backward(  # Calls into the C++ engine to run the backward pass
/users/xhaoxuan/miniconda3/envs/ring-ulysses/lib/python3.10/site-packages/torch/autograd/graph.py:769: UserWarning: c10d::broadcast_: an autograd kernel was not registered to the Autograd key(s) but we are trying to backprop through it. This may lead to silently incorrect behavior. This behavior is deprecated and will be removed in a future version of PyTorch. If your operator is differentiable, please ensure you have registered an autograd kernel to the correct Autograd key (e.g. DispatchKey::Autograd, DispatchKey::CompositeImplicitAutograd). If your operator is not differentiable, or to squash this warning and use the previous behavior, please register torch::CppFunction::makeFallthrough() to DispatchKey::Autograd. (Triggered internally at /opt/conda/conda-bld/pytorch_1724789115564/work/torch/csrc/autograd/autograd_not_implemented_fallback.cpp:63.)
 return Variable._execution_engine.run_backward(  # Calls into the C++ engine to run the backward pass
/users/xhaoxuan/miniconda3/envs/ring-ulysses/lib/python3.10/site-packages/torch/autograd/graph.py:769: UserWarning: c10d::broadcast_: an autograd kernel was not registered to the Autograd key(s) but we are trying to backprop through it. This may lead to silently incorrect behavior. This behavior is deprecated and will be removed in a future version of PyTorch. If your operator is differentiable, please ensure you have registered an autograd kernel to the correct Autograd key (e.g. DispatchKey::Autograd, DispatchKey::CompositeImplicitAutograd). If your operator is not differentiable, or to squash this warning and use the previous behavior, please register torch::CppFunction::makeFallthrough() to DispatchKey::Autograd. (Triggered internally at /opt/conda/conda-bld/pytorch_1724789115564/work/torch/csrc/autograd/autograd_not_implemented_fallback.cpp:63.)
 return Variable._execution_engine.run_backward(  # Calls into the C++ engine to run the backward pass
local_dqkv:
[0] max 4.47, mean 0.0747
[1] max 0.516, mean 0.0299
[2] max 0.217, mean 0.0199
[3] max 0.297, mean 0.0126
dq diff:
[0] max 0.0156, mean 0.00066
[1] max 0.000977, mean 5.56e-05
[2] max 0.000488, mean 4.46e-05
[3] max 0.000488, mean 1.96e-05
dk diff:
[0] max 0.0156, mean 0.00058
[1] max 0.000977, mean 6.58e-05
[2] max 0.000488, mean 4.01e-05
[3] max 0.000488, mean 1.74e-05
dv diff:
[0] max 0.0156, mean 0.000576
[1] max 0.000977, mean 6.72e-05
[2] max 0.000488, mean 3.65e-05
[3] max 0.000488, mean 1.73e-05
[rank0]:[W1114 20:14:11.788433858 ProcessGroupNCCL.cpp:1168] Warning: WARNING: process group has NOT been destroyed before we destruct ProcessGroupNCCL. On normal program exit, the application should call destroy_process_group to ensure that any pending NCCL operations have finished in this process. In rare cases this process can exit before this point and block the progress of another member of the process group. This constraint has always been present,  but this warning has only been added since PyTorch 2.4 (function operator())

I reran the tests with Flash Attention 2.6.3, and these warnings persist, likely due to using torch version 2.4.1 instead of the flash-attn update.

Sorry I missed this issue and it's fixed in #58 . Could you try to upgrade the whl with pip install -U ring-flash-attn?

Thanks for your response! I decided to work with FlashAttention 2.6.3 for my project.
I should have opened a PR for it but unfortunately I was quite busy these days and also forgot that. I believe if the tests are passed it would be OK, so I close this issue. Thanks!


Publish some methods

When use Dispatch on DynamicFramework(CocoaPods or Carthage), cann't use some methods.
ex.
import DispatchFramework

let someCustomQueue = dispatch_queue_create("custom.queue.dispatch", DISPATCH_QUEUE_CONCURRENT)
Dispatch.sync(someCustomQueue) {} // Cann't called

Added the public keyword in order to use.

Current coverage is 34.01% (diff: 100%)

Merging #13 into master will not change coverage

@@             master        #13   diff @@
==========================================
  Files             3          3
  Lines           147        147
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits             50         50
  Misses           97         97
  Partials          0          0

Powered by Codecov. Last update 44807ca...14d5cfe

👍


Update to rust 1.52

Pull request
Description
rust and tarpaulin update
Related

Related Issues: fixes #994

Checklist

[x] The RFC, if required, has been submitted and approved
[x] Any user-facing impact of the changes is reflected in docs.tremor.rs
[x] The code is tested
[x] Use of unsafe code is reasoned about in a comment
[x] Update CHANGELOG.md appropriately, recording any changes, bug fixes, or other observable changes in behavior
[x] The performance impact of the change is measured (see below)

Performance
rust version update

The coverage drop in this is caused by a degradation in tarpaulin with version 0.18.0-alpha3 the related ticket is here: https://github.com/xd009642/tarpaulin/issues/757


question！

Hi, I want to ask you a question, is the process the same as the diffusion idea for adding convolutional layers to retain more information? Algorithm 1 is for denoising, and algorithm 2 is for denoising the reconstructed image! I have a question about this place and I hope you can answer it. Thank you very much

Hi, I want to ask you a question, is the process the same as the diffusion idea for adding convolutional layers to retain more information? Algorithm 1 is for denoising, and algorithm 2 is for denoising the reconstructed image! I have a question about this place and I hope you can answer it. Thank you very much

@bxhsort Actually, it is not the case, The algorithm 1 and 2 is for the var image tokenizer training setting, not the image generation process. The image generation is done by the autoregressive process.

Hi, I want to ask you a question, is the process the same as the diffusion idea for adding convolutional layers to retain more information? Algorithm 1 is for denoising, and algorithm 2 is for denoising the reconstructed image! I have a question about this place and I hope you can answer it. Thank you very much

@bxhsort Actually, it is not the case, The algorithm 1 and 2 is for the var image tokenizer encoding & decoding setting, not the image generation process. The image generation is done by the autoregressive process.

Thank you for your answer. My understanding is that algorithms 1 and 2 provide GT for the subsequent autoregressive training. Is this process to better train the token and its Embedding, which is similar to the training of tokens in nlp? The process of stage2 is an autoregressive process, which is also a process of inference. In algorithm 1, after you extract features with convolution layer, you subtract them with image feature f. I have some doubts about this place, and I would like to ask why you can save information well by doing this. Looking forward to your reply, thank you very much!


Adjust Travis configs to fix build error and use latest osx image

Still waiting for the commit build to run to check if it fixes the current problems. Opening this PR to see if that triggers a build.

Closing this PR since it's not ready yet. Will reopen when there is something to review.


Stop forceful xaxis conversion to numeric type

Codepen
I was not able to reproduce this in a codepen unfortunately. For some reason it's not happening there:
https://codepen.io/anon/pen/dLoQJX
Explanation

What is the behavior you expect?
If I set xaxis type to 'categories', I expect it to be that way
What is happening instead?
apexcharts converts it to numeric and removes my categories unless I use xaxis.tickPlacement = 'between' which I don't want

Not sure why this was introduced, but I don't see the logic in forcing it?
it's this line:
https://github.com/apexcharts/apexcharts.js/blob/94e059d46e0c1bd4fce47959841bb296c45af9a3/src/modules/settings/Config.js#L111

If you do xaxis.tickPlacement: on, it is essential to convert the xaxis to numbers to remove the padding from left and right.
if you notice the xaxis in xaxis.tickPlacement = 'between', the ticks calculation is different than numeric. The numeric x-axis allows drawing the chart from end to end (calculating from 0 to n).
Do you face any issues with this force conversion during updates? If yes, what issues?

The problem I am facing is that conversion removes my categories, and so I get less xaxis labels than I expect (I can no longer effectively force their number).
More specifically, I define up to 21 categories, but the conversion process removes them and so only up to 6 or 7 are displayed.

If that's the case, the conversion logic needs to be modified.
I am afraid I will have to remove the tickPlacement setting if I remove the force conversion as tickPlacement: 'on' will only work for numeric xaxis.
I will try to find the best way to deal with this.

I see. Is there a reason on can't work with non-numeric xaxis? Seems like the logic for placement is already there if it can find the between values, perhaps that is what can be tackled?
I'll try to take a look tomorrow when I'm back at work.

More specifically, I define up to 21 categories, but the conversion process removes them and so only up to 6 or 7 are displayed.

I can not reproduce this issue on my side. Can you try some other demo (codesandbox / jsfiddle)?

I wasn't able to reproduce it either when creating the issue. I'll try again tomorrow.
How come that the conversion is not happening in the demo I have posted?

I was able to produce it. It only happened when data-points exceeded 20.
I had a condition to reduce the tickAmount in numeric x-axis when it was more than 20.
Will modify that condition.

Awesome, glad to hear you were able to reproduce it, thank you for your efforts!

I'm afraid this issue with "we only support 20 values" might still exist >> https://github.com/apexcharts/apexcharts.js/issues/965

hello,
is there any way to bypass / disable convertCatToNumeric to X axis?
thank you

happened to me aswell.. it does not always happen after 20plus but with over 300values on xaxis it happens..
the chart looks sh*t with 300 vals on xaxis anways but still,...


Ultenic T10

Description
Hello Guys
I have a Ultenic T10, it used to work for a very long time but now it stopped working on my HA instance.
Steps to reproduce
The Robot stopped working with HA.
I tried following steps:
Reconfigured the robot, didn't work, at some time I could not delete the device, so I deleted the entire integration and reinstalled it with HACS.
Now when I want to add the device again I get this error in the GUI:
Unable to connect to your device with those details. It could be an intermittent issue, or they may be incorrect.
In the logbook I can see this:
This error originated from a custom integration.
Logger: custom_components.tuya_local.device
Source: custom_components/tuya_local/device.py:458
integration: Tuya Local (documentation, issues)
First occurred: 11:03:21 PM (10 occurrences)
Last logged: 11:07:19 PM
Test protocol error 904: Unexpected Payload from Device
Test protocol error 914: Check device key or version
But whatever I try, the problem occurs.
I tried adding the robot again to the network to find its correct IP (because MAC address in Ultenic APP is wrong) by checking the DHCP lease time.
I used this info to reserve a "fixed" ip that my DHCP doesn't serve.
I tried adding the device with multiple options through the GUI.
Tried using tuya-uncover and the device data and endpoints still looks the same as before the robot stopped working with HA.
Expected behaviour
No response
Additional context
No response
Confirmation

[X] I am sure this is a bug or improvement, that is well enough described that it can be implemented.

[X] If this is for a specific device, the device config is mentioned above, or diagnostics are included.

[X] Log messages or diagnostics relevant to the issue are included.

[X] This is not requesting addition of a new device.

Connection issues can come from many external sources, in this case it appears your device has likely had a firmware upgrade that changed its protocol version, or been reset and changed its device id.


Update baseline.yaml - NEW - OSPS-DO-17

added proposal for OSPS-DO-18 for project's risk assessment process & docs

The term "threat" is really vague, it's not clear what level we're discussing. E.g., is this a list of threats?: "Unintentional vulnerability in our code", "Malicious vulnerability in our code", "Vulnerability in dependency", "Insecure design"? Can we suggest a specific list as a starting point?
Can we identify some OSS projects as examples who have done this? For all our criteria we should be pointing to projects that have done it.


Pin vispy < 0.7

🚀 Feature
I think we should pin vispy < 0.7 for our next release. Everyone is working hard to ensure a migration will be easy, but there might be some breaking changes when the release comes out, and I think we'll want to be able to adopt 0.7 when we have everything working as expected.

@sofroniewn As an alternative, how about adding a CI configuration that uses the VisPy main branch? I've been doing light testing on main and it seems to be working fine. Hopefully not too onerous to maintain that compatibility?
Just a thought — I'm also ok with pinning.

vispy 0.7 is now ready for testing - see https://github.com/vispy/vispy/issues/2104
I'm making this thread for us to collect any changes on the napari end that we need to make to get up to date.
I've already found one minor one
  File "/Users/nsofroniew/GitHub/napari/napari/view_layers.py", line 17, in <module>
    from .viewer import Viewer
  File "/Users/nsofroniew/GitHub/napari/napari/viewer.py", line 3, in <module>
    from .components import ViewerModel
  File "/Users/nsofroniew/GitHub/napari/napari/components/__init__.py", line 17, in <module>
    from .camera import Camera
  File "/Users/nsofroniew/GitHub/napari/napari/components/camera.py", line 5, in <module>
    from ..utils.events import EventedModel
  File "/Users/nsofroniew/GitHub/napari/napari/utils/__init__.py", line 1, in <module>
    from .colormaps import Colormap
  File "/Users/nsofroniew/GitHub/napari/napari/utils/colormaps/__init__.py", line 2, in <module>
    from .colormap import Colormap
  File "/Users/nsofroniew/GitHub/napari/napari/utils/colormaps/colormap.py", line 11, in <module>
    from .standardize_color import transform_color
  File "/Users/nsofroniew/GitHub/napari/napari/utils/colormaps/standardize_color.py", line 27, in <module>
    from vispy.color import ColorArray, get_color_dict, get_color_names
  File "/Users/nsofroniew/GitHub/vispy/vispy/color/__init__.py", line 12, in <module>
    from .colormap import (Colormap, BaseColormap,  # noqa
  File "/Users/nsofroniew/GitHub/vispy/vispy/color/colormap.py", line 12, in <module>
    from hsluv import hsluv_to_rgb
ModuleNotFoundError: No module named 'hsluv'

Which we new was coming (i think from https://github.com/vispy/vispy/pull/2066).
Maybe @alisterburt we can coordinate here on making sure we'll be compatible

Actually that error might be inside vispy - i have created https://github.com/vispy/vispy/issues/2108 to document

ok, this is fixed by pip install hsluv, see comment in thread - package was moved to be an external dependency

ok, i'm able to launch napari with 0.7 and see an image - I get a divide by zero encountered in true_divide printed in the console which we should look into, but that's already a very good sign!!!
I will try running tests now

that warning pops up here
self = <napari._vispy.vispy_camera.VispyCamera object at 0x7f83b8f1f3d0>

    @property
    def zoom(self):
        """float: Scale from canvas pixels to world pixels."""
        canvas_size = np.array(self._view.canvas.size)
        if self._view.camera == self._3D_camera:
            # For fov = 0.0 normalize scale factor by canvas size to get scale factor.
            # Note that the scaling is stored in the `_projection` property of the
            # camera which is updated in vispy here
            # https://github.com/vispy/vispy/blob/v0.6.5/vispy/scene/cameras/perspective.py#L301-L313
            scale = self._view.camera.scale_factor
        else:
            scale = np.array(
                [self._view.camera.rect.width, self._view.camera.rect.height]
            )
>       zoom = np.min(canvas_size / scale)
E       RuntimeWarning: divide by zero encountered in true_divide

napari/_vispy/vispy_camera.py:109: RuntimeWarning

need to fix for tests to pass

awesome work @sofroniewn - I'll take a look myself tomorrow morning and report back here if I find anything else

'tomorrow morning' - whoops
#2958 is a fix for the error you found - I ran a bunch of examples covering a range of layer types (image volume vectors surface points shapes) and didn't find any other glaring issues so I think we're relatively safe


incomplete css-tutorial?

the tutorial for bundling css with webpack (https://webpack.js.org/guides/code-splitting-css/) does not quite tell you all the steps necessary in my opinion. is it just me and i'm missing the point of the tutorial?
if the point of the tutorial is indeed to bundle css so that it is rendered on the website, i'd like to submit a PR which adds the missing steps (installing and using the style-loader-module). thoughts?

Could you expand on which parts are unclear or the steps you feel are missing?
I just re-read it, and it does look like some things could be elaborated, but it doesn't seem like any code is missing. Either way, we'd love for you to PR any improvements!

@TomTasche Has the incompleteness been resolved with https://github.com/webpack/webpack.js.org/pull/1130? If so, let's close this issue.

#1130 did not add the information i was looking for, but it completed the information that is already available in the tutorial
what the tutorial is missing in my opinion is a mention of style-loader. the last paragraph uses extract-text-webpack-plugin which is fine, but before that it is necessary to use style-loader. otherwise css is merely bundled with javascript, but never applied to the website?
i will come up with a PR as suggested by @skipjack!


A protocol and a prototype for MBT-core <-> MBT-Rust communication

Following the description outlined in https://github.com/informalsystems/modelator/issues/2#issuecomment-785870955., we need to split the jobs of generating and executing tests into MBT-core and MBT-Rust plugin. For that we need to devise a simple protocol for the communication of MBT-core and MBT-Rust, and do a prototype implementation of it.
As a testing ground for the protocol, it is proposed to take the work done in IBC-rs#701, and to separate it into MBT-Core and MBT-Rust:

MBT-core will have the task of running TLC on the provided spec, and generating tests from it. It will run as a daemon listening for local requests.
MBT-Rust will run the given test executor implementation on the tests obtained via communication with MBT-core.

In the first iteration we should not care too much about the particularities of the implementation, but to focus on obtaining a minimal working prototype that has MBT-core and MBT-Rust separated and communicating via a protocol. This will be refactored later for a better code structure.

Closed as outdated. Please reopen if this is a mistake.


Eager Loading maximum 5 relationships

Hi,
Thanks for developing this great package!
I need to include some relationships via query strings while making a request. I'm using 'with' in my URL.
I realized that Laravel responder is loading in JSON 5 relations deep at maximum.
I'm trying to Get something like:
GET /products?with=orders.customer.user.type.category.group
Inside the response is loaded an object that does not contain a 'group' attribute.
Is this an expected behavior? Is there some alternative for loading something like this?
I'm using version 2.0.
Thanks

Hi @brunorsantos! Check the config/responder.php file, there should be a recursion limit option. This defaults to 5, but feel free to change it to whatever you like :)

Thanks!
I didn't notice it!
Sorry about this!


Admin  can add product.

Add new items to site.

A summary of the problem or requirement that this task solves
Admin user has the abilities to add products as necessary

Clear requirements for how to consider each task or issue "done"
Testing is complete verifying capability.


Get Started with the SAP BTP Command Line Interface (btp CLI)

Tutorials: https://developers.sap.com/tutorials/cp-sapcp-getstarted.html
Write here how you think we can improve the tutorial ...
Step: 6 Login to your Global account
I cannot seem to login at all - I always get
SAP BTP command line interface (client v2.8.0)
CLI server URL [https://cpcli.cf.us10.hana.ondemand.com]>https://cpcli.cf.ap10.hana.ondemand.com
Connecting to CLI server at https://cpcli.cf.ap10.hana.ondemand.com...
Global account subdomain [e712556dtrial-ga]>bournedigitalptyltd-01
User<EMAIL_ADDRESS>Password>
You're about to send your credentials to https://cpcli.cf.ap10.hana.ondemand.com for the first time.
Do you trust this server? [no]>yes
Global account 'bournedigitalptyltd-01' not found.
FAILED
Not sure why this is not working.
Thanks
Phil

Hi @pjcools , I just noticed that in your case, the problem is not the global accozunt subdomain, but the server url.
Please change it to https://cpcli.cf.eu10.hana.ondemand.com:
CLI server URL [https://cpcli.cf.us10.hana.ondemand.com]>https://cpcli.cf.eu10.hana.ondemand.com
Kind regards,
Anna


Install HyperHDR on Home Assistant OS

Feature request

What problem does this feature solve?
Not being able to run HyperHDR server on the same device running HomeAssistant OS
What does the proposed API look like?
N/A
How should this be implemented in your opinion?
Through the Home Assistant Add-on Repository. The Hyperion.ng project was (fairly)recently added so we might look into that as an example.
Are you willing to work on this yourself?
I'm not sure I have the necessary skills for that but I'd be more than happy to help and/or test.

Hi
Personally don't use HA and I highly doubt there are enough resources free on the Rpi when HA is running. When I tested HA on Rpi3, there weren't enough resources even for HA running solo on the device and the interface lag was terrible. Maybe on Rpi4 with more available RAM the situation is better, don't have s spare unit to test it. I don't plan on making such a plugin, but maybe some other users would create it as a separate project.

I've actually managed to get HyperHDR up and running today as a hass add-on on a pi4b  with 4gb RAM and don't see any issues yet. Will do some performance tests tomorrow.
I've followed the Hyperion.ng template I was talking about above so it might be a little sloppy but if someone more competent then I wants to contribute to this I'm more than happy to approve PRs. 😃

If the performance is satisfied then I can provide link on HyperHDR to your fork. Same as it's done for @mjoshd and his HA plugin for HyperHDR. Do you have an access to CPU/RAM statistics when HyperHDR is running and capturing video and how they look like? They are also available in v18beta in the overview tab if there is no direct access to the system.

Hi, CPU and RAM usage are minimal while capturing as far as I can tell (CPU 4.7-6.1%, RAM ~2%) on this pi4B 4GB. However, I'm having issues with flickering. I'm using wled to drive the strip but the flickering happens only when hyperhdr drives the strip. Any idea what might cause this?
What I've tried:

2 different capture cards - no change
changing capturing fps and resolution -no change
enabling/desabling smoothing - if disabled flickering becomes more noticable
changing video source (Chromecast with google tv and xiaomi mi box) - no change

I've also installed HyperHDR on a separate pi3B+ with the same wled driver and psu and there's no flicker/issues

Ok something weird fixed this. I have two identical hdmi capture cards and I was planning to test the working capture card from the pi3b on the pi4b. After I plugged it out from the pi3b the flicker on the other TV (where the pi4b sits) disappeared. I think HyperHDR on the pi3b was still trying to control the wled driver (as I have only one at the moment).

Yes, that's possible that these two units were fighting for the same WLED device. WLED UDP driver is rather ugly and it won't notify user about any trouble. Unfortunately not much can be done here because QT libraries won't throw any error even if the WLED device is powered off (at least for Windows, for Linux it depends).

Hi, I've rebuilt the different arch docker images thanks to bradsjm's scripts and workflow and I think the add-on is ready now. I did some further testing and I see no difference compared to a standalone installation. 🙂

Great! I will provide info about your fork with the next release of HyperHDR and invite everybody to help with testing :)

This is great! Was already running Home Assistant (Supervised) with a manual install of HyperHDR next to it, but this would make it easier to maintain and update. Just switched, imported config and works fine. I might even switch to Home Assistant Operating System now!

This is great! Was already running Home Assistant (Supervised) with a manual install of HyperHDR next to it, but this would make it easier to maintain and update. Just switched, imported config and works fine. I might even switch to Home Assistant Operating System now!

I'm really glad you found it useful.
I might just close this as well since the issue is solved.


Potential Missing Dependencies

Hi there! Thank you for this awesome library!
I was wondering if the issue described here: https://github.com/mikepenz/AboutLibraries/issues/501
might also be an issue for the AndroidX/Java version (6.2.3). As an extra test, I also added the zxing dependency, but it does not show up. I might be doing something weird though, since this is my first time trying out this library.
This is what my gradle file looks like (some parts removed):
apply plugin: 'com.android.application'

android {
    compileSdkVersion 29
    buildToolsVersion '29.0.3'
    defaultConfig {
        applicationId "removed"
        minSdkVersion 19
        targetSdkVersion 29
        versionCode removed
        versionName "removed"
        testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
        renderscriptTargetApi 22
        renderscriptSupportModeEnabled true
    }

    buildTypes {
        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        }
    }

    compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_8
        targetCompatibility JavaVersion.VERSION_1_8
    }

    buildFeatures{
        dataBinding = true
    }
}

allprojects {
    repositories {
        google()
        jcenter()
    }
}

dependencies {
    implementation fileTree(dir: 'libs', include: ['*.jar'])
    implementation 'androidx.appcompat:appcompat:1.1.0'
    androidTestImplementation('androidx.test.espresso:espresso-core:3.1.0', {
        exclude group: 'com.android.support', module: 'support-annotations'
    })

    implementation 'com.google.android.material:material:1.1.0'
    implementation 'androidx.exifinterface:exifinterface:1.0.0'
    implementation 'com.mcxiaoke.volley:library:1.0.19'
    implementation 'androidx.constraintlayout:constraintlayout:1.1.3'
    implementation 'com.googlecode.plist:dd-plist:1.16'
    implementation 'com.github.siyamed:android-shape-imageview:0.9.+@aar'
    implementation 'com.google.android.gms:play-services-location:17.0.0'
    implementation 'com.google.android:flexbox:2.0.1'
    implementation 'com.otaliastudios:zoomlayout:1.1.0'
    implementation 'androidx.lifecycle:lifecycle-extensions:2.2.0'
    implementation 'androidx.lifecycle:lifecycle-viewmodel:2.2.0'
   implementation "com.mikepenz:aboutlibraries:6.2.3"
    implementation 'androidx.cardview:cardview:1.0.0'
    implementation 'androidx.recyclerview:recyclerview:1.1.0'
    implementation 'com.journeyapps:zxing-android-embedded:3.5.0'
}

But the only dependencies that show up are:

AboutLibraries
Android-Iconics
dd-plist
Fast Adapter
FlexboxLayout
Google Play services.

Zxing, ZoomLayout and mcxiaoke's Volley do not show up, for example. Initially, I thought it was (as mentioned in your disclaimer) because these libraries maybe set their POM files up incorrectly. But, since it seems Zxing is supposed to work, I was wondering if it was maybe relevant to bring up?
As an aside, IF it is their POM files, is there a way to include libraries with incorrect POMs to show up? Google's oss-licenses-plugin manages to show all dependencies - but it doesn't look nearly as beautiful as this library.
Details

[ 6.2.3] Used library version
[4.0.1] Used gradle build tools version
[4.0.1] Used tooling / Android Studio version

@ZeeOne how did you configure the gradle plugin?

I fail to find it in your shared one above:
https://github.com/mikepenz/AboutLibraries#gradle-plugin

That was the quickest response in the history of humanity!
Ok, I didn't set up the plugin, since I incorrectly assume I should use the 6.2.3 version there - and then thought I set it up incorrectly when it did not work.
I have now set it up like so:
root:
dependencies {
        classpath 'com.android.tools.build:gradle:4.0.1'
        classpath "com.mikepenz.aboutlibraries.plugin:aboutlibraries-plugin:8.3.0"
    }

and then in the app gradle: added apply plugin: 'com.mikepenz.aboutlibraries.plugin' to the top.
It still behaves the same as describer above though.
Thank you for taking the time to respond to a greenhorn!

Oh I am actually sorry I totally missed that you are on a very old version of the library.
So v6.x is no longer maintained. it used provided definition files to fill the UI with the dependencies. with that approach libraries may be missing as they were not added yet.
With v8 we finally made a new approach which retrieves the information via maven (the pom files) which will now catch all the libraries.
It is highly suggested for you to upgrade to it.
If you regardless want to stay to v6 you can have a look at the tag at that state: https://github.com/mikepenz/AboutLibraries/tree/v6.2.3
The libraries which were supported back then:
https://github.com/mikepenz/AboutLibraries/tree/v6.2.3/library/src/main/res/values
if one is not showing up or not existing you'd have to add your own definition file to provide the missing information

Its working!! Thank you so much! Sorry, this is totally my fault - I was under the impression that one has to use V6.2.3 for AndroidX/Java. I updated everything to the latest and greatest version, and now it works perfectly. It looks SO nice. Sorry for wasting your time with silly mistakes, and thank you again for your effort!

Happy to be able to help :)


PDF Generation Service

Description
PDF Creation microservice.
Research around how can we go about generating PDFs.
examples:

Sending in HTML templates using HBS, EJS etc. templating engines.
.... figure out what can be other ways

2 Parts:

Generating PDFs/Implementation of the generation techniques-- customizable (support multiple templating engines,

We should also have support for bulk PDF generation.
Ideally this should be a JSON based config where where in we send the information using a spec (basically the content + template) and then get bulk links of uploaded PDFs back.
The response should also support streaming raw PDFs instead of uploaded links
Future scope

Add an SDK to it
Add a CLI to it
Add a frontend where the user can visually modify the template and generate PDFs

References:

https://github.com/techsavvyash/c4gt-bff/blob/master/src/rcw/rcw.service.ts this link has a very crude implementation of templating engine based PDF generation, these needs to be fine-tuned and implemented in a robust fashion with test cases.

Research Doc:
https://docs.google.com/document/d/1nz_66YwG3RJwO_X3Xb-jEwr1rAyNgNUF1mPixLJFU2c/edit

Current update:

[x] able to generate PDFs using template

Next Steps:

[ ] Benchmark timings
[ ] Compare tools with respect to timings

Features

[ ] Template based PDF generation
[ ] Template saving
[ ] end point for generation with the body as JSON of information and templateID
[ ] ensure scaling

[ ] Make sure it is fast

[ ] Research around market standard times

[ ] API for bulk generation in batches
[ ] Can respond with a link to a storage service (minIO by default)
[ ] can send application/pdf as a HTTP response
[ ] Have support to send PDFs as emails etc.

[x] bulk generation
[x] JSON data support
[x] CSV support
4s for 50 PDFs

Next Steps

[ ] Convert to TS

https://github.com/gotenberg/gotenberg
tool for converting html to pdfs
has no support for html templates

https://docs.google.com/document/d/1OHMoig_5YdWqysAK0tur3IUsEUHzUbDY0KRF75BZOuM/edit
document for tracking service development


Fix filehandling for windows

Windows requires it's files to be closed before being removed. We've been bitten by this before.
Having tests doesn't help if we don't run them :/ See: https://github.com/prometheus/prometheus/issues/4622

@brian-brazil @fabxc @krasi-georgiev PTAL. These are non-trivial and might break things, I'm working on testing this now.

WAL migration and compactions work on Windows now. Tested with min-block-duration set to 2m.

And checkpointing works on Windows! I think this is good to go!

:+1:

I've let this run overnight on Darwin, Linux and Windows. I've checked the migration again on windows and darwin. Everything runs pretty well, so this is good to go!


PWA support

Just wanted to know if PWA support is in plan. It would be awesome

@bitfreee Any plans to add PWA support? It would be awesome.
Thanks


NEP numbers should not have decimal parts (e.g. "NEP-5.1") - only whole numbers

For example, NEX has some extensions to NEP-5 that they want to call NEP-5.1.
@saltyskip has some NFT extensions that I think he wants to call NEP-5.1.
@mwherman2000 (moi) has some NEP-5 extensions for processing remittances ...maybe I want to be the ".1" in NEO-5.1?
I don't think it makes sense to have decimal parts in NEP numbers.
Who has the right to be ".1", who is ".2"?  If you're the ".1" ...do you also have first rights to become ".2" or ".3"?  If you're the ".1" and my spec is the ".2" and some other unrelated spec is ".3", will that make sense to anyone 1, 5, 10 years from now?
The whole situation is avoidable if we stick to whole numbers (i.e. positive integers) e.g. NEP-1234
Do you agree?

CC: @erikzhang @saltyskip @lllwvlvwlll

To give my 2cents @mwherman2000 I think that any standard should be a NEP, so with NEP10 I can say that I comply with NEP5 and NEP15 or whatever and that composed is equivalent to the standard the application need, so the application can call a method and determine if it should process further.

@canesin I think I agree with you Fabio (and I'm glad to see you agree with/support NEP-10). I think the key phase in your comment is "any standard should be a NEP" ...and, more importantly, how do we operationalize this?
I've made one suggestion here: https://github.com/neo-project/proposals/issues/47 (which @erikzhang  supports ...I'm looking for others to add their comments).

@mwherman2000 NEO is a community project already makes no sense for me to have a "NEO Community Proposal" at all, what makes it different then a NEP ? As a matter of fact it is good to have fewer standards.

RE: As a matter of fact it is good to have fewer standards.
Not at all. It make sense to have fewer (formal) NEP standards but the spirit of NEP-10 is to create a vibrant ecosystem with gazillions of NCPs/NEPs ...trying to say that the only specifications that are shared across the community are the formal NEP specs only serves to stifle innovation in favor a few large projects.
p.s. ...unless your issue is only with the name (i.e. NEO Community Proposal)... then that's a gentler discussion.

Is not only the name, I provided some input in the other issue. We cannot have a "stub" to standard.

It's whatever works best for the community ...decided by the community.

We can endup with 100s of NEPs for specific things, that is okay - but a standard need to be static, by definition of standard, you can't comply with NEP5 or NEP10 and that means two different things. So for community standards to work, it shoul ... be a NEP ?

There won't be a decimal part in a NEP number.

Decision (https://github.com/neo-project/proposals/issues/50#issuecomment-394061788): "There won't be a decimal part in a NEP number."
Issue closed

Decision (https://github.com/neo-project/proposals/issues/50#issuecomment-394061788): "There won't be a decimal part in a NEP number."
Issue closed


fixing mousewheel scrolling

@inforithmics The mouse wheel scroll fix has no effect in my development environment. Do you know why this is? I ask because I need to suppress touch as well, which has no effect so far, but it could be because of my development environment too.

I would suggest to install newest .NET 7 SDK and call dotnet workload update on the commandline. I discovered that Scrolling with mouse does not work in firefox (but the scroll page suppression does).

@inforithmics Thanks, got it work. Not sure what it was in the end. Also updated Visual Studio.


stylo's build script crashes inside mangling with "(signal: 11, SIGSEGV: invalid memory reference)" on macOS

See bug 1335302.
After adding "--stdlib=libc++", "--target=x86_64-apple-darwin" to clang args in build_gecko.rs, the bindgen does not report any compile error anymore, but it crashes with the stack I pasted in bug 1335302 comment 3.
I saw #439, and also tested upgrading to clang-sys 0.14.0, but it doesn't seem to help. The build script still crashes at the same location.
It seems to crash when trying to get mangling name of __find_exactly_one_checked::__matches at /usr/local/Cellar/llvm/3.9.0/include/c++/v1/tuple:1018:25. But I failed to find minimal reproducible code...

@emilio Could you have a look at this? This is probably not really a bindgen bug... It could be a bug in libclang. I have no idea how can we workaround it.

The issue here is that it somehow doesn't treat __find_exactly_one_checked as a template, hence the cursor.is_in_non_fully_specialized_template() check returns false and consequently we don't correctly skip mangling __find_exactly_one_checked::__matches.
Cursor::is_template's documnet is "Is the referent a template specialization?", which probably shouldn't be named is_template. I guess, maybe we should use is_template_like or something in is_in_non_fully_specialized_template?

Actually this issue is reproducible with the following code:
template <class... Args>
struct Test {
  static constexpr bool x[] = {Args::x...};
};

Thanks for the testcase! I'll find a workaround ASAP.
(For the record, Xidorn debugged it and it's a bug in LLVM, I think he submitted a patch?)

It is not necessarily a bug in clang. There is no way in clang itself to hit that condition, and it seems libclang doesn't have no-crashing guarantee for invalid input.
I tried hard to write a test for that issue last night, but failed, so I'm not going to submit a patch for it.