How do we know how many split messages are there for particular snapshot

It is difficult to know, how many split messages will be coming for a particular snapshot. I think everytime a message is split, it should also have some sort of indicator that, how many messages will be there in the payload.

Fixed by #114


go: better fetch

[ ] add a cache for sqlite3 db

a github cache volume through a github action
manual github release
automatic github release?

[ ] download feed only if not found in .db or .db not in fs
[ ] before download check with HTTP Last-Modified or something similar
[ ] still inform errors
[ ] save cache back
[ ] rarely fetch, rarely updated feeds

continuation of #5

possible steps

load sqlite into a feeds structure
fetch
save feeds

should be done, added a actions/cache and logic to use Last-Modification and Etag to monitor changes if I need or not to refetch a feed.
Still might be rough edges. Like some feeds not returning those fields.

might be I could add content-length
and/or decide to add better logic based on which fields are present or not
and/or add all header into json column (for easier non-destructive updates on headers logic)


Possible to open other file types ?

Hello thanks for this library
Is it possible to open other file types ? or it will support only TXT files
thanks

Hi, it's my pleasure . Actually yes, you can open , but probably it gonna be unusable.  If the goal is some data logging then best choice is CSV(Comma-separated values), it's easy to open in MS excel or LibreOffice. Which extension are you interested in? Here's an example to see what I'm talking about.

hi sorry to jump in conversation but as topic is still open ;)
I did not dig in code yet but do you mean that reading binary like pictures may be a problem?
I would like to store text based files as well as binaries for images

Hi, i haven't tried  to use for binary files. But that feature can be useful , i will experiment with it

Hi @luc-github , maybe this can be useful for You.

@djuseeq thank you - I am super late to integrate your lib - I will check that when on it


update jest

Jest has recently been updated quite a bit. The goal of this task is to check that jest is up-to-date.

Confirming that jest is up to date:

latest version of jest is 24.9.0
latest version of @types/jest is 24.0.18
our package.json jest section uses the correct preset: react-native

Source: https://jestjs.io/docs/en/tutorial-react-native
No action needed at this time. Closing this issue.


[Popover] absolute positioning

Hi,
One thing that came up in our testing, was that when Popover contains a TextField or input, and when using Mobile Safari, (e.g. ipad) and the keyboard comes up, the fixed positioning causes the popover to lose its position, and become unusable.  Making it absolute should sort this, the downside is that render-to-layer needs to track its position manually via a throttled WindowListener.
Comments welcome.
Thanks,
Chris
Fixes https://github.com/callemall/material-ui/issues/3482.

@chrismcv Any chance we could refactor Popover to not use scroll position? It might take a lot of refactoring but it will super simplify a lot of this.

I can't think of a way to do this.  Happy to invest time into it if you can!

@chrismcv Awesome, honestly I haven't really investigated it much.
I'm wondering if we can learn anything about how to do it using approaches used by these:
https://github.com/HubSpot/tether
https://github.com/souporserious/react-tether
Would you be able to do a preliminary check and see how feasible it would be?

@newoga - I'm pretty sure tether is doing the same thing
https://github.com/HubSpot/tether/blob/master/src/js/tether.js#L86
https://github.com/HubSpot/tether/blob/master/src/js/tether.js#L352

@newoga any more thoughts on this?  (We're currently using a branch on my own repo with this in production, because iPad compatibility is important for us... I'd like to get back on the main tree.)

@newoga any more thoughts on this?

@chrismcv Sorry for the late response! I did have some thoughts but didn't have the time to formulate a response at the time. You're right the library are using listeners, but they're not (always) using fixed positioning based on scroll position. I think we should look into switching the popovers to be absolutely positioned relative to what it's anchored to. That should reduce repaints and fix the "thrashing" that's happen when the user scrolls now.
What do you think?

@newoga no problem.

I think we should look into switching the popovers to be absolutely positioned relative to what it's anchored to.

I'm not sure how to do this.  Popover is using the portal pattern, so is rendered into a different subtree.  This is useful/important/necessary as it allows it to break outside of overflow:hidden in the anchor's tree.  Any thoughts/guidance would be great, as perhaps I'm missing something obvious.

@newoga just a friendly ping on this for your best thoughts!

@chrismcv Thanks for the reminder! I see your point about the portal pattern. I haven't given this too much thought, but I still wonder if we should just make Popover always the root/parent component when its behavior is used so that it doesn't have to worry about the overflow: hidden problem.
@callemall/material-ui Are there any other approaches that we're not considering? I think we should make a goal to not continuously update the Popover's position using inline styles based on scroll position (we can still use scroll/window to determine whether it should pop above/below/left/right on its anchor if necessary).

@newoga - I'm not sure how practical that is - Dialog is also a portal, which can (optionally) sit inside LeftNav (#1669) , and a SelectField (which uses Popover) can sit inside a Dialog, so I'm not sure we can reduce to root/parent that cleanly?
As for other ideas, https://github.com/souporserious/react-measure could be an alternative position detector, but probably won't reduce the layout thrashing much?
What about a container that matches the page dimensions? (With the popover fixed within that page?) At the moment this._layer is 100% by 100%, but if it was "measured width" by "measured height" then we'd only need to listen to onresize...?

@chrismcv Sorry, I'm not disagreeing there aren't valid use cases for the portal pattern. I agree that Dialog is a good use case. But I find that using it for Popover introduces a lot of unnecessary complexity. For example, right now on the material docs website, the version dropdown SelectField's Popover doesn't scroll because it's the window isn't scrolling, an inner div is.

@chrismcv Have you seen this project that react-bootstrap separated and made? It seems like they are able to use the portal pattern without relying on combination of fixed position and scroll state:
https://github.com/react-bootstrap/react-overlays

@newoga Maybe we should use some modules from that instead of re-inventing the wheel. We can contribute back upstream with improvements if needed.

@nathanmarks I agree. I reviewed it in some more detail and it seems well implemented.
@chrismcv @callemall/material-ui Any thoughts on maybe porting our components to react-overlays? It would likely replace our internal/Overlay.js, internal/AutoLockScrolling.js, and internal/RenderToLayer.js.

I don't object to using it... however, I'm pretty sure we want to portal popover in the majority of circumstances, including SelectField e.g. #1621.  I think we should agree on an API as well....
  <SelectField
     PopoverWrapper={PortalisingOverlayTrigger}
     {...props} />

@chrismcv What @newoga is saying is that the portal'd content doesn't have to mean fixed positioning. You can see that in react-bootstrap their popovers aren't spastic when you scroll because they use absolute positioning for them in a portal.

yeah - I understand, but I don't see how this would work....
So if I have a SelectField in a Dialog, I want the DropDown part of the Select to break outside the Dialog, but my dialog body can scroll, so I need to portal out of it.  Their solution requires a ref to be passed into to the portal, so to use a SelectField, I'd then need to pass it a dropdown container ref.
This seems like a substantial complexity to put this on users?  Or am I missing something obvious?

@chrismcv the idea is that we use the modules internally, not expose the API to users

@nathanmarks - I understand, but if we do that, I think we'll end up with a "lowest common denominator" implementation, which will result in being back on position fixed based solutions...

@chrismcv Why is there "lowest common denominator" implementation? The Popover is only used for 1 thing in the entire MD spec, menus.

If we want to use <SelectField /> (which uses popover) in left nav like in the docs, then it needs to break outside <LeftNav /> as it does by default when components menu is collapsed.  As LeftNav has overflow:scroll set on it, SelectField needs the dropdown part to portal to a different part of the DOM without the overflow, as a menu shouldn't be affected by it.
The problem here is the interaction between SelectField and LeftNav. If we were to absolutely position Popover for SelectField relative to the SelectField, LeftNav will still interfere with it, because of the overflow.  (The same applies for dialog.)

@chrismcv
LeftNav would not block it overflowing if it isn't in left nav.
BTW, not suggesting dialog should use absolute positioning.

@chrismcv Sec, I see what you're saying about the nav bar edge case.

@chrismcv Also, with the position: fixed solution we currently have, we're polling for the position under all conditions! With a 100ms throttle for perf reasons, therefore artificially limiting our popover scroll motion to 10 FPS. It looks absolutely terrible when you scroll the page with a popover open.

The same applies in dialog,  it used to be that if we had select fields in
dialogs,  we got scrollbars when opening them, which was non intuitive.
On Mon 4 Apr 2016 19:28 Nathan<EMAIL_ADDRESS>wrote:

@chrismcv https://github.com/chrismcv Sec, I see what you're saying
about the nav bar edge case.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/callemall/material-ui/pull/3144#issuecomment-205436254

@chrismcv Some libraries opt to lock scrolling with menus open (including angular-material and polymer). This is also what the native <select> field does.

Native select triggers a close popup on a scroll for me? (on ubuntu) That would be straightforward to implement...

@chrismcv aha, locks scroll on OS X.
I need to stew on this -- either way I don't think we can stick with a solution that means allowing scroll but capping movement at 10fps.

@chrismcv I'm going to close this for now. It has gotten really old since we removed all uses of isMounted (#3437) and the mixins such as WindowListenable (#3305). We can track the discussion regarding using scroll position for the position in #3917.
If you want to give this another stab in, feel free!

Fine to close, but I'm really keen for there to be a plan for a solution to this.  At this stage, I don't see much point in investing time without a clearly agreed plan.

@chrismcv yeah, there's a bunch of issues with dialogs/popovers/etc that need addressing together.
I'd really like to get the scrolling situation for popovers etc fixed. Right now the 100ms delay between updates is absolutely killing the feel.


fix usage of @ptrCast, should be @intToPtr

Fix as described by commit  message

@mattnite I just ran into this problem when starting up a new project. Could this change get reviewed & merged?
deps/stmicro-stm32/src/chips/STM32F103.zig:115:30: error: expected 1 argument, found 2
            pub const TIM2 = @ptrCast(*volatile types.TIM2, 0x40000000);

@binarycraft007 can you please update the PR by running the 0.11.0 zig fmt on this file? @freiguy1 theres still the inferences typing that was added to builtins.

Sorry for the ignorance, but I'm not sure what you meant by the part of your comment addressed to me. I did a little digging and found this issue: https://github.com/ziglang/zig/issues/5909 with a couple PRs attached to it. Maybe you were just providing context about why this happened. I'd probably be fine on an older version of zig.

@binarycraft007 can you please update the PR by running the 0.11.0 zig fmt on this file? @freiguy1 theres still the inferences typing that was added to builtins.

just rerun zig fmt on it

@binarycraft007 Thanks! @freiguy1 sorry I was just quickly explaining why I couldn't merge yet. I'm away on a trip but the plan is to stabilize on 0.11.0 for microzig. There was a big change to builtins where they infer their return type instead of having them specified in an argument.


added help page with beautiful styling

Description
@thestarsahil
[Feature] : Add Help page #644
Please include a summary of the change and which issue is fixed. List any dependencies that are required for this change.
Fixes #644(issue_no)
Replace issue_no with the issue number which is fixed in this PR

added new route /help
when user click on help option from footer they will redirected to /help route
where user got required help

Screenshots

Checklist

[x] Tests have been added or updated to cover the changes
[x] Documentation has been updated to reflect the changes
[x] Code follows the established coding style guidelines
[x] All tests are passing

@thestarsahil
kindly please check this and merge it

This the color theme : For Bold -> #3C38B9
For Paragraph and semibold -> #00073e

@thestarsahil
as per you theme, i changed font color
please check this and merge it

Do with other pages also and make another PR
Great work !

sure


Pre-training on UCF101

Hi, I wonder if you can provide the model checkpoints for pre-training on UCF-101, and the pre-train hyperparameters/instruction of it.
Thank you so much!

Hi! Check here for the pre-trained model: 3D-ResNet18-UCF101-128x128. Let me know if you cannot load it properly.
My hyperparameter setting is identical to the command provided for K400 pre-train, but I reduce lr by 1/10 at epoch 300 and 400, totally trained for 500 epochs. Actually, the pre-training is not sensitive to this schedule. Others have re-produced even better results than our paper submission (https://github.com/TengdaHan/DPC#dpc-results). Hope it works well on your side.


Update Cargo.toml http => https

It would redirect, but it is nicer to have the secure link there

Thank you, Merge now

You are welcome. I am building the rust digger in order to catch such small (and some bigger) things that can be improved.


Proper error message when loading a template fails

There are all kinds of reasons loading a template might fail, e.g., wrong Cicero version, missing package.json, etc.
We should provide an error message when that happens.

Fixed in PR #45


Select event

You package is very easy to use. Congrats for that.
But, could you update it to support select event? Or even more events...

The JQuery plugin used has the event


cleanup: replace oneWay with toView, add toView + fromView binding behavior

We have some binding behaviors that set the binding mode. Now that we have toView and fromView binding modes we should add the corresponding binding behaviors:
https://github.com/aurelia/templating-resources/blob/0cef07a8cac8e99146d8e1c4b734491bb3dc4724/src/binding-mode-behaviors.js
Also need to standardize the internals on toView now that it has landed. We still need to support oneWay but the internals should use toView where possible.
related to https://github.com/aurelia/binding/issues/629 and https://github.com/aurelia/templating-binding/issues/118

https://github.com/search?l=JavaScript&q=org%3Aaurelia+.one-way&type=Code
not that much to change.. I can get PRs for code and .md


Remove third_party

Use Bazel fetching capacity instead. After this change, one needs
to bazel build //com.google.devtools.bazel.e4b in order to have
the runfiles for the plugin resolved (and the jar fetched).

I Noticed that the version from p2 update site is version 0.0.2. And get a Option 'experimental_interleave_loading_and_analysis' is deprecated. warning, which is no longer there in current source code.
How should I build and use the new version built from bazel? I tried the build commend above and add the output "com.google.devtools.bazel.e4b_0.0.3.qualifier.jar" to eclipse dropins subdir, and restart eclipse, but nothing happened.
did I miss some procedure like deploying?

Hi,
I usually loads the plugin in Eclipse directly as an eclipse project then run it under test.
To actually load it, I use the //:p2updatesite target that I unzip and load but I haven't tested that path with the new architecture yet.


I'm working on the blackbox verifier so was asked by my research team not to look at your code until I'm done so it won't influence my design decisions (even subconsciously) and so we communicate all interfaces via the spec and don't assume things we see in each other code... let's connect on Gitter to discuss next steps...


I want take my choice but i can't

This is the error-message:
File "C:/workspace/RockPaperScissor/app.py", line 52, in player_against_computer
self.computer_2.make_choice()
AttributeError: 'Game' object has no attribute 'computer_2'

this fixes #6
but cause #7


Module is not working on HyperOS (<IP_ADDRESS> Android 14)

Module is not working on HyperOS. It is installed correctly after applying https://github.com/j-hc/FlagSecurePatcher/pull/9.
It looks like Xiaomi is doing something different. When I used this LSPosed module https://github.com/LSPosed/DisableFlagSecure it was working correctly.
They are doing some special magic for HyperOS Android 14:
https://github.com/LSPosed/DisableFlagSecure/blob/fd0b56f651810a2ed0268e639279c385f4425165/app/src/main/java/io/github/lsposed/disableflagsecure/DisableFlagSecure.java#L57
https://github.com/LSPosed/DisableFlagSecure/blob/fd0b56f651810a2ed0268e639279c385f4425165/app/src/main/resources/META-INF/xposed/scope.list
magisk_install_log_2024-08-04T20.33.20[1].log

upload the fw.zip to google drive and link it here after executing this command in termux
pkg install zip && cd /system/framework/ && su -c $(command -v zip) -r9 /sdcard/fw.zip .

Here it is: fw.zip

also uploading zip of /system_ext/framework: fw_ext.zip - there is miui-services.jar, where is method notAllowCaptureDisplay, which returns boolean (we need false?) used in services.jar.

Does this work?
flag-secure-patcher-r12.zip

Still not working, miui-services.jar is patched, but screenshot still cannot be captured.
magisk_install_log_2024-08-11T10.21.48.log

It is working after manual fix - system_ext ($MODPATH/system_ext) folder from $MODPATH needs to be moved into system in $MODPATH ($MODPATH/system/system_ext). Also oat files of miui-services.jar needs to be stored in system_ext, not system ($MODPATH/system/system_ext/framework/oat/arm64/ miui-services.odex and miui-services.vdex ... i deleted miui-services.art because it is not used in original system_ext)

Also FlagSecureDetector (from 5ec1cff - https://t.me/real5ec1cff/211 ) detects something abnormal

flag-secure-patcher-r12.zip
how about this one

flag-secure-patcher-r12.zip
how about this one

It failed during installation: magisk_install_log_2024-08-11T14.13.35.log
But I found /system_ext is mounted on /system/system_ext... so in first first zip (https://github.com/j-hc/FlagSecurePatcher/issues/10#issuecomment-2282223433) i now changed path from /system_ext/miui-services.jar to /system/system_ext/miui-services and it is working same as here: https://github.com/j-hc/FlagSecurePatcher/issues/10#issuecomment-2282720208, and FlagSecureDetector still showing abnormal: https://github.com/j-hc/FlagSecurePatcher/issues/10#issuecomment-2282722458

flag-secure-patcher-r12.zip
should be fine now

Still not working
magisk_install_log_2024-08-11T14.39.07.log

new one
flag-secure-patcher-r12.zip

new one
flag-secure-patcher-r12.zip

new one
flag-secure-patcher-r12.zip

Installation works, and can take screenshots. FlagSecureDetector still abnormal
https://github.com/user-attachments/assets/aebf5a0f-1f37-443c-8c5e-1bd58fa31d1b

that doesnt matter. virtually no app tries to detect that.


Can the API version be adjusted to 21?

As I remember aom could not be compiled against 21, it is possible to adjust by removing all libraries that could not be linked against 21 API. Btw I don’t remember exactly highly likely x265 or de265 also cannot be linked against 21

Ofc you will lose part of functionally

As I remember aom could not be compiled against 21, it is possible to adjust by removing all libraries that could not be linked against 21 API. Btw I don’t remember exactly highly likely x265 or de265 also cannot be linked against 21

what is aom?

As I remember aom could not be compiled against 21, it is possible to adjust by removing all libraries that could not be linked against 21 API. Btw I don’t remember exactly highly likely x265 or de265 also cannot be linked against 21

Where can I obtain relevant info?  I tried to looking for answers at https://aomedia.googlesource.com/aom#microsoft-visual-studio-builds but found nothing about this

I think you won't find the relevant info. I have build scripts in repository (or if you have experience with compiling C++ for NDK you may write your own) you have to modify target API version from 24 to 21 and try to compile libs and try to solve all the issues that y'll face

thanks for the info


Binders have no access to the config

I cannot find a way to get the config passed into the verticle to be available in the binders.

Can you provide an example of what you are trying to do?
One option is to use bindFactory() in your binder.  The HK2 Factory  can have the Vertx instance injected in the constructor allowing you to access the JSON configuration.

Vertx.currentContext().config() should be sufficient. A thread maintained by Vert.x always has a reference to a processing context and its configuration.

+1 @meshuga


Press enter key to apply node finder filters

Which package/s are you suggesting this feature for?
Dashboard
Is your feature request related to a problem? Please describe
Every time I am setting filters on the node finder, I instinctively press enter to apply them but nothing happens.
Describe the solution you'd like
Enter key should engage the "Apply" button on the node finder. Probably there are some other places in the UI where this make sense, but I didn't go looking for all of them at the moment.

Work completed:
Added an event to apply filters on enter.

verified on devnet
version : db2daf4
https://github.com/threefoldtech/tfgrid-sdk-ts/assets/110984055/5c0107a9-9469-4b37-a99d-116d1f17048c
verified on all fields and filters

Verified:

Devnet
d44ca11


Use ecmascript module for take advantage of the export/import mechanism

Hey, Im not entirely sure as to the aim of this PR. Is it to allow functions to be called from external modules ?
There is a quite major re-work in https://github.com/kandashi/Custom-Token-Animations/tree/0.1.14, if this is something that can be pulled into that that would be great

Hi sorry, I have not put any description because I have a closed mind on ecmascript modules, it is my fault to automatically think that others consider it a good idea.
Yea i'm trying to upgrade this module  target-enhancements and i want to try to use your module for add animation on targeted token.
I hadn't seen the branch in development, do I close this  request and open a new one on the branch ?

oh yeah, thats no problems, just wanted to confirm

I hadn't seen the branch in development, do I close this request and open a new one on the branch ?
That would be good yea :)


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/30663

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/31243

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/32478

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/35377

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/37053


Types of parameters 'props' and 'props' are incompatible.

There is no @types/react-redux for react-redux 7.2.0 and higher.
Probably this is the cause for the error:
Types of parameters 'props' and 'props' are incompatible.

I don't know what error you're referring to here, because you haven't provided any code or the actual error.
We don't maintain the React-Redux TS typings ourselves - those are kept in Definitely Typed.  Also, the current @types/react-redux package covers our API correctly, including the v7.2.1 release.


Idea: Make Invoke-Build available as dotnet new template (mostly slated towards f#).

This is how it could be done:
https://bitbucket.org/da9l/invokebuildtemplate/src/master/
It's pretty unpolished especially the bootstrap functions but to test it,
clone repo
.\template.build.ps1 InstallLocally #installs template from local folder into local dotnetsdk template library
md mytestproject | cd
dotnet new console -lang f#
dotnet new invokebuild
.\mytestproject.build.ps1

.\mytestproject.build.ps1 #to build project.
This can be done on any machine with just dotnetsdk installed. (have only tested on windows with powershell 7)

Thank you for the interesting idea and the sample of using it.
I did not think of using dotnet new for bootstrapping, yet.

Feel free to use it or follow up with ideas on how I could rewrite it as a PR to your repo.
The doubts I have is around the bootstrapping and the dependency to paket. As a F# dev I use paket but it´s not a given for C# dev.
In a template you could add a parameter that tells if it should use default nuget solution or paket.
I'm just unsure/haven't given it much thought how one would in-place bootstrap Invoke-Build using the default dotnet nuget.

Please do not go for a PR or similar moves yet. The idea is promising but there is so much to think about. It is very difficult to get bootstrapping and/or scaffolding right, so that it suites at least many users ("majority" is not realistic, IMHO). Everybody has it's own way of using IB, I believe.

Yeah, I figured that much. I realized too that this idea is not quite ready for PR yet. I do however think this could get pretty close to a pit of success for many both F# and C# projects and in my experience, ease of getting started often win the day. The added support for gitversion might or might not be a good thing.
Generally I really prefer the idea of each dotnet new template being functionally speaking - composable. You should be able to add it where ever you are in your project creating process.
Thanks for your feedback!

I have doubts that the template should be designed for paket or nuget in the first place. In PowerShell world packages are delivered by PowerShellGet (Install-Module). paket is good, no doubts. But I believe many PowerShell and IB users do not use it.
PowerShellGet (Install-Module) based template does not require anything but PowerShell, given it comes with PowerShellGet nowadays. This does not exclude use of packet or nuget, but it's up to a user. The template takes care of just InvokeBuild.

Fair enough. PowerShellGet should probably be the default to resolve the invokebuild dependency as long as it can be done as non-intrusively as possible for a dotnet project in the dotnet new template. My whish here is that if a CI server have access either directly to nuget.org, powershellgallery.com a dev setting up a project should not have to do anything but installing the template and configuring the script. I.E. no or close to no CI-server configuration.
If that can be achieved I guess I'm fine with any solution.
Regards, Daniel

OK, let's start with something. Here is the temp (?) repository https://github.com/nightroman/Invoke-Build.template
See its root build script for available tasks/actions.
It makes/installs ib-basic template. It is a self-invoking build script with automatic bootstrapping of InvokeBuild module, with a pinned version.

Please review the latest changes in the temp (?) repository https://github.com/nightroman/Invoke-Build.template
See the README for options.

And it is on nuget.org -- https://www.nuget.org/packages/Invoke-Build.template/
I am closing the issue as resolved.
@da9l You are welcome to give your feedback here or open issues in the new repository.
(for now I would like to have the template in a separate repository)

Wow! Thanks Roman!
I'm sorry but I haven't found time to give any feedback on this but this
looks really promising! I like that you removed all the project creation
stuff.
It is totally in line with the thought that project composition actions
should be outside any dotnet new template.
Regards, Daniel Hegner
On Sat, Oct 10, 2020 at 1:46 PM Roman Kuzmin<EMAIL_ADDRESS>wrote:

Closed #172 https://github.com/nightroman/Invoke-Build/issues/172.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nightroman/Invoke-Build/issues/172#event-3862679305,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABD23M4CMHETPOGLMLVZ73SKBCSPANCNFSM4RXM2Y7A
.

--
mail &<EMAIL_ADDRESS>twitter.com/8DH


[KYUUBI#5467] Integrate Intel Gluten with Spark engine

:mag: Description
Issue References 🔗

This pull request fixes #5467
Describe Your Solution 🔧

Add Gluten UTs.
Setup CI for Gluten testing
Write docs to guide users in setting up Kyuubi with Spark plus Gluten.

Types of changes :bookmark:

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

Test Plan 🧪
Behavior Without This Pull Request :coffin:
Behavior With This Pull Request :tada:
Related Unit Tests
github action ci tests: Gluten Test CI

Checklists
📝 Author Self Checklist

[ ] My code follows the style guidelines of this project
[x] I have performed a self-review
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] This patch was not authored or co-authored using Generative Tooling

📝 Committer Pre-Merge Checklist

[ ] Pull request title is okay.
[ ] No license issues.
[ ] Milestone correctly set?
[ ] Test coverage is ok
[ ] Assignees are selected.
[ ] Minimum number of approvals
[ ] No changes are requested

Be nice. Be informative.

thanks, merged to master. We shoule keep check nightly build to see if the workflow work well.

late LGTM. thanks.


(testing): Bump K8S_VERSION for testing to 1.26.0

Description of the change:

Bumps K8S_VERSION in Makefile to 1.26.0 so that our testing environment uses k8s 1.26
Bumps kind version in Makefile to 0.17.0 so that it is up to date with the latest release
Bumps golangci-lint version in Makefile to 1.51.2 to fix a problem I had locally where running make lint resulted in my terminal or editor crashing.

Motivation for the change:

K8s 1.26 bump

Checklist
If the pull request includes user-facing changes, extra documentation is required:

[ ] Add a new changelog fragment in changelog/fragments (see changelog/fragments/00-template.yaml)
[ ] Add or update relevant sections of the docs website in website/content/en/docs

/cc @rashmigottipati

/hold remove


Adding tutorial based on hello-kubernetes

This PR adds a tutorial that uses the same example as the official quickstart title hello-kubernetes but introducing Dapr Shared. To merge this PR first we need to make sure that those examples support setting a remote Dapr Endpoint -> https://github.com/dapr/quickstarts/pull/1030

@yaron2 @alicejgibbons I need someone to approve this PR :)

This good to be merged? @salaboy

I was waiting for an approval


[Help] Is there a way to completely disable selection/activation?

My grid is read-only and I have call-to-actions on the right. I don't use the selection feature at all. How can I not have a row/cell selected in blue?
Things I tried:
PlutoGridSelectingMode.none doesn't do anything 🤔
PlutoGrid(
  ...
  mode: PlutoGridMode.readOnly,
  onLoaded: (PlutoGridOnLoadedEvent event) {
    event.stateManager.setSelectingMode(PlutoGridSelectingMode.none);
  },
)

Hiding the selected state by declaring the same color as normal, it "works" in the sense that there is no color change when selecting a row, but still the vertical border disappears because the selected call border is bigger and hides the normal border
  configuration: PlutoGridConfiguration(
    style: PlutoGridStyleConfig(
      activatedBorderColor: Colors.white,
      activatedColor: Colors.white,
    ),
  ),

There are currently no features mentioned.
However, it seems that the intended purpose can be achieved by setting the widget to ignore updates as shown below.
The code below sets the internal widget _CellContainer to ignore updates.
Even if an event such as cell selection occurs, it is not updated.
thank you
PlutoGrid(
  columns: columns,
  rows: rows,
  notifierFilterResolver: _CustomNotifierFilter(),
),

class _CustomNotifierFilter extends PlutoNotifierFilterResolverDefault {
  @override
  Set<int> resolve(PlutoGridStateManager stateManager, Type type) {
    print(type.toString());
    // Set to ignore updates of internal widget _CellContainer.
    if (type.toString() == '_CellContainer') {
      return {-1};
    }
    return super.resolve(stateManager, type);
  }
}

Additionally, when the app is built, the name of _CellContainer may be changed.
If that's the case, I don't think this code will work.
I haven't tested whether it works after build.

@bosskmk the snippet above doesn't remove the row selection, but it does remove the cell selection: the one that adds the thick border.
So used in conjonction with the style property activatedColor: Colors.white, it does hide the visual effect of selection.
I'll go with that 👍 so thank you, but maybe can you consider this issue as a feature request?


Using getPublishMessages method problem

Hi
I have some missunderstanding of using sendSubscribe and getPublishMessages methods.
I need to recieve messages that subscribed, if they exist, and i don't need for waiting messages, if they are not still published by another program.
So i do the following:
Unsubscribing all and subscribing to 4 topics:
$client->sendUnsubscribe(array("username/#"));
$res[] = $client->sendSubscribe("username/current");
$res[] = $client->sendSubscribe("username/status");
$res[] = $client->sendSubscribe("username/temperature");
$res[] = $client->sendSubscribe("username/humidity");
In $res array i have all 4 topics with ["success"]=>bool(true) and ["qosGiven"]=>int(1)
Next trying different variants:

$messages = $client->getPublishMessages() - recieve all messages, but very slow and always "MQTT: Read timeout" in debug.
$messages = $client->getPublishMessages(0) - recieve only 3 messages (always all subscribed, but not last subscribed), fast and no timeout.
$messages = $client->getPublishMessages(1) - recieve 4 messages fast and no timeout.

So, what is the right and fastest method in my case ?
And so on, if i skip sendUnsubscribe calling before sendSubscribe and getPublishMessages methods in first variant, then i recieve more than 4 messages with duplicates.
For example, i recieve 2 "username/current" topics, that different with ["retain"]=>bool(true) and ["retain"]=>bool(false).
If i use variant 3 and subscribe to absent topics, then also have duplicates of existing topics different with ["retain"]=>bool(true) and ["retain"]=>bool(false), even if use sendUnsubscribe, slowly and sometimes with "MQTT: Read timeout"

Hi,
I'm not actively using this package myself any longer and there is also a newer MQTT-standard since a while back, so I expect there are/will be some other package supporting that. Anyway, it should work for MQTT version 3 (check what version your message server uses).
Regarding the 3 variants you tried.

Sounds normal - this package is not async, so when there is nothing left to be read a timeout is the only way to proceed. The debug message of "MQTT: Read timeout" is exactly that and will happen after the timeout you set (default is 5000 ms).
Will attempt to read 0 messages from the stream, ie nothing should be returned, unless some messages have been queued. Then all those will be returned, which will happen without any timeouts as theses message already have been fetched from the stream. Seems like this is happening to you.
Will attempt to read 1 message from stream. If there is at least one message it will be fast (like in your case), otherwise there will be a timeout. Finally all messages queued from previous calls will be returned as well. (Which is why there are more than 1 message returned.)

In general I would try to use  $client->getPublishMessages() with a shorter timeout if you need to poll the stream often. Just set  a different timeout when connecting to the server. Syntax is:
sendConnect($clientId, $cleanSession=false, $keepAlive=10, $timeout=5000)
Hope that helps.


feat(op-reth): [Core] TxPool cost updates

Describe the feature
Diff Category: Core | TxPool cost updates
Overview
Transaction queueing and inclusion in the transaction needs to account for the L1 cost function, defined in #3740.
Where should this feature live?
Crate: reth-transaction-pool
Completion Criteria

[ ] Deposit transactions are prohibited from existing in the transaction pool, the engine API authenticates deposits.
[ ] The transaction pool considers the l1 info gas overhead and the l1 cost function when determining if the sender has enough ETH to not overdraft.

Additional context
Resources

op-geth diff
op-erigon diff
Optimism Specs

Deposit transactions are prohibited from existing in the transaction pool, the engine API authenticates deposits.
This is implicitly handled by this matcher, which we can codify via a unit test addition.

Deposit transactions are prohibited from existing in the transaction pool, the engine API authenticates deposits.

This rule implicitly enforced by this matcher, which we can codify via a unit test addition.


Frees alpn_selected before reassigning it

To avoid memory leaks.
I am not sure if a memory leak can really happen now but :

code and comments do not explain how memory leaks are avoided
it is the only calls to OPENSSL_memdup which were not following a OPENSSL_free

For server side, I found no leaks as :

tls_handle_alpnassumes we only have one client hello by handshake
tls_parse_ctos_alpnassigns alpn_proposed only on first handshake

The extension is permitted to be present only once in the Server/Client Hello, which is why it's assumed to already be NULL. I'm not sure if/how the extensions are checked for duplicates.

The extension is permitted to be present only once in the Server/Client Hello, which is why it's assumed to already be NULL.
Well, I am not sure that the code enforces this (+ there may be multiple server/client hellos with renegotiation for instance)
If the code enforces that the pointer is NULL at the start of the function, the comments should explain how, so that it does not get broken in the future.

I'm not sure if/how the extensions are checked for duplicates.
Done by function tls_collect_extensions with thisex->present == 1

code and comments do not explain how memory leaks are avoided

Either we have resumed or we haven't. If we resumed then s->hit is true and we do not go down this code path. If we have not resumed then we have a new session and alpn_selected is guaranteed to be NULL on return from SSL_SESSION_new(). This is true regardless of whether this is a reneg handshake or not.
Perhaps this is appropriate?
/* This is a new session and so alpn_selected should have been initialised to NULL */
if (!ossl_assert(s->session->ext.alpn_selected == NULL)) {
    SSLfatal(...);
    return 0;
}

Closing this in favour of #5715.


Where is the cct source code

Where is the cct source code

Is you blind? It is in 'src' folder for 'source.'


riscv toolchain build failed

use the same .config with buildroot can successful build in my local ubuntu 18.04. but Error in the github actions' runner
action's log:
logs_42.zip

As of February 2019, gdbserver has not been ported to RISC-V yet. As a result it won't build.

@zhangyoufu

https://stackoverflow.com/questions/54298210/building-gdbserver-for-riscv

As of February 2019, gdbserver has not been ported to RISC-V yet. As a result it won't build.

gdb 8.3.1 which this repo used already supports RISC-V . quote from https://lists.gnu.org/archive/html/info-gnu/2019-09/msg00006.html

GDB 8.3 includes the following changes and enhancements:

Support for new native configurations (also available as a target
configuration):

RISC-V GNU/Linux (riscv*--linux)
RISC-V FreeBSD (riscv*--freebsd)

.The workflow failed on building buildroot's toolchain, not gdb. On my local machine, both can build without any problem.


Add clipped shape test for broadcast_arrays and unary ufunc

 add clipped shape test for broadcast_arrays

 add clipped shape test for unary ufunc


[Request] sp_spaceused  output with sp_helpme would be useful

Always wanted to see how much of space used by the table and number for rows in it with  cmd
so plugging the output of sp_spaceused  as second row in sp_helpme  would be a huge helpful..

I'm not sure I see the value in either directly or indirectly combining sp_spaceused information into sp_helpme, when one can just run the stored procedures back to back to fetch the info. You can always write your own wrapper to call them both if the input is a table, too.
This stored procedure is intended to be an enhanced version of sp_help, not a kitchen sink. If there are parts of sp_spaceused that are lacking, creating a new version might be a worthwhile effort, though I haven't found myself wishing it behaved differently to be honest.


Labels per Issue

I'm trying to run some analysis tasks over the labels an issue gets attached. I started running this query on BigQuery:
SELECT repo.name, JSON_EXTRACT_SCALAR(payload, '$.issue.labels') labels
FROM [githubarchive:day.20150101]
WHERE type IN ('IssuesEvent')
AND JSON_EXTRACT_SCALAR(payload, '$.action') = 'opened'
AND JSON_EXTRACT_SCALAR(payload, '$.issue.labels') is not null
LIMIT 50

And I obtained no results, even if I remove the action filter. Does this information get mined in the dataset?

Carlos, have you verified that issue labels are present in the data? The Events API does not (unfortunately) surface all the issue metadata (see related discussion in https://github.com/igrigorik/gharchive.org/issues/183) so I wouldn't be surprised if this data is missing.
/cc @annafil

@cptanalatriste wanted to follow up here and echo what @igrigorik said in case you are still working on this issue -- I believe issue labels are not included in the /events API feed coming from GitHub (just webhooks), so I would not expect to see them in the GHArchive data set.

Sorry this reply is coming late.. I will check it out tomorrow,  please
On Tue, 5/29/18, raghavsehtia<EMAIL_ADDRESS>wrote:
Subject: Re: [igrigorik/gharchive.org] Labels per Issue (#184)
To: "igrigorik/gharchive.org"<EMAIL_ADDRESS>Cc: "Subscribed"<EMAIL_ADDRESS>Date: Tuesday, May 29, 2018, 5:56 PM
Hey!
I believe the information is there (at least some of it),
however since it's nested, you must index into the field
in order to get the actual values. I ran the following
query
SELECT repo.name, JSON_EXTRACT_SCALAR(payload,
'$.issue.labels[0].name') label1,
JSON_EXTRACT_SCALAR(payload,
'$.issue.labels[1].name') label2,
JSON_EXTRACT_SCALAR(payload,
'$.issue.labels[2].name') labels3 FROM
[githubarchive:day.20150101] WHERE type IN
('IssuesEvent') AND JSON_EXTRACT_SCALAR(payload,
'$.action') = 'opened' LIMIT 50
and my result is attached.
Please let me know if this is incorrect or if I may have
misunderstood the problem!
—
You are
receiving this because you are subscribed to this thread.
Reply to this email directly, view
it on GitHub, or mute
the thread.


Parallel tests

Type of change

Enhancement / new feature

Description

Added annotation for Parallel tests
Only tests within class can run in parallel
move + rename some classes to framework package

Checklist

[ ] Update/write design documentation in ./documentation/design
[ ] Write tests and make sure they pass
[ ] Update documentation
[ ] Check RBAC rights for Kubernetes / OpenShift roles
[ ] Try your changes from Pod inside your Kubernetes and OpenShift cluster, not just locally
[ ] Reference relevant issue(s) and close them after merging
[ ] Update CHANGELOG.md

@lulf I tried to run MessagingEndpointTest class in parallel and I see that operator blocks removing resources for example {"level":"error","ts":1593942164.1223986,"logger":"controller-runtime.controller","msg":"Reconciler error","controller":"messagingendpoint-controller","request":"enmasse-tenant/app-ws6","error":"Failed processing finalizers: resource still in use by addresses","errorVerbose":"resource still in use by addresses\nFailed processing finalizers\ngithub.com/enmasseproject/enmasse/pkg/util/finalizer.ProcessFinalizers\n\t/home/runner/work/enmasse/enmasse/pkg/util/finalizer/finalizer.go:148\ngithub.com/enmasseproject/enmasse/pkg/controller/messagingendpoint.(*ReconcileMessagingEndpoint).reconcileFinalizer\n\t/home/runner/work/enmasse/enmasse/pkg/controller/messagingendpoint/messagingendpoint_controller.go:324\ngithub.com/enmasseproject/enmasse/pkg/controller/messagingendpoint.(*ReconcileMessagingEndpoint).Reconcile.func2\n\t/home/runner/work/enmasse/enmasse/pkg/controller/messagingendpoint/messagingendpoint_controller.go:174\ngithub.com/enmasseproject/enmasse/pkg/controller/messagingendpoint.(*resourceContext).Process\n\t/home/runner/work/enmasse/enmasse/pkg/controller/messagingendpoint/messagingendpoint_controller.go:921\ngithub.com/enmasseproject/enmasse/pkg/controller/messagingendpoint.(*ReconcileMessagingEndpoint).Reconcile\n\t/home/runner/work/enmasse/enmasse/pkg/controller/messagingendpoint/messagingendpoint_controller.go:173\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/home/runner/work/enmasse/enmasse/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:256\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/home/runner/work/enmasse/enmasse/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:232\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).worker\n\t/home/runner/work/enmasse/enmasse/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:211\nk8s.io/apimachinery/pkg/util/wait.JitterUntil.func1\n\t/home/runner/work/enmasse/enmasse/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:152\nk8s.io/apimachinery/pkg/util/wait.JitterUntil\n\t/home/runner/work/enmasse/enmasse/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:153\nk8s.io/apimachinery/pkg/util/wait.Until\n\t/home/runner/work/enmasse/enmasse/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:88\nruntime.goexit\n\t/opt/hostedtoolcache/go/1.13.1/x64/src/runtime/asm_amd64.s:1357","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/home/runner/work/enmasse/enmasse/vendor/github.com/go-logr/zapr/zapr.go:128\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/home/runner/work/enmasse/enmasse/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:258\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/home/runner/work/enmasse/enmasse/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:232\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).worker\n\t/home/runner/work/enmasse/enmasse/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:211\nk8s.io/apimachinery/pkg/util/wait.JitterUntil.func1\n\t/home/runner/work/enmasse/enmasse/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:152\nk8s.io/apimachinery/pkg/util/wait.JitterUntil\n\t/home/runner/work/enmasse/enmasse/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:153\nk8s.io/apimachinery/pkg/util/wait.Until\n\t/home/runner/work/enmasse/enmasse/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:88"}

@kornys I think that particular error is because address has not been removed, so it cannot remove endpoint yet. Make sure resources are created/removed in order.
Regarding the PR in general, although I think its useful to be able to execute test methods in parallel, I think a greater speedup could be achieved if test classes could also be run in parallel.
I think the following would allow for some great speedups:

Test classes marked as "@Concurrent" can run in parallel with other test classes within the same installation type
Test methods marked "@Concurrent" can be run in parallel with other test methods
When any of the "default" annotations are used, test orchestration will ensure that it:

If default infra: reuse the same infra if it has already been created by test framework . I predict a large number of the 'test feature X of address types' will fall into this category.
If default tenant: create a namespace + tenant in a namespace with random UUID . This will ensure that the test gets an isolated namespace for its addresses and don't have to care about address names etc.

For any test that is marked concurrent and that explicitly creates an infra or tenant with a specific name, its the test writer responsibility to ensure that it does not conflict.
The parallelism level can be used to tune how many tests are run in parallel at a given time - depending on the underlying cluster capabilities.

@lulf so resource manager is stack, so I just use what is written and I expect address is creatated before endpoint so in delete part it firstly removes endpoint and then address.

Anyway I agree with changes you request, but I want to make PR with initial parallel run and do not implement that in one PR. I think it would be better to do it one by one, for example es next step implement class parallelism.

@kornys Oh, yes, I didn't mean you should change this PR, just wanted to discuss overall direction.
Re address vs endpoint, you should create address last always, at least until the router that allows making the address prefix be the namespace instead of the endpoint host as it is now.

@lulf I have just checked that resource manager firstly tries to remove address and then endpoint, and it stuck.

@lulf another point of parallel tests at this moment is, that logs are mixed, so if 4 tests are running in same time we are not sure which log line is for which test :(

@kornys you can add thread id to log output and/or log to file per execution which should make it easier to analyze after the fact .

@lulf ok makes sense, I will try to ask on junit5 community if surefire can buffer logs and print it in sync mode per thread/test. Anyway before I merge this PR we should more investigate why operator dont want to delete resources even if I remove them in right order

@kornys I will look into that teardown issue, but I think it would be good to get the per-thread logging first to simplify debugging.

@lulf ok I will do it ASAP, but not sure if I can do it today

rebased on master, resolved merge hell due to renaming to messagingproject and pushed

@lulf I have an idea, what about resource manager instance for every test and test class. Then we wont struggle with removing resources. There will be hashmap of stacks and every test and class can temove only own resources

@kornys Yeah, but I'd keep one instance of the resource manager, and refactor it to create a "test context" for each test which the test uses to create resources. The context and all resources created in it would be deconstructed after test completion.

We can discuss it tomorrow, I was thinking about singleton resource manager and change stacks to one hashmap of string,stack where string is identifier of test or test class, we can pass it with create/delete method vie TestContext which contains testname, displayname etc...

deprecated, I opened another PR with parallel extension


All tetrad-related work, GR Maxwell equations, and coupled fluid-Einstein equations

This branch contains several core additions to Gkeyll's burgeoning GR framework, with the principal ones being:

New functionality for handling Maxwell's equations in curved spacetime (in strongly hyperbolic form) with wv_gr_maxwell. Initial prototyping work has been done to try to introduce a fully covariant version of the hyperbolic divergence cleaning approach to the curved spacetime Maxwell equations, although this remains incomplete, and has been disabled at present;
New functionality for evolving general relativistic Euler equations with an ultra-relativistic equation of state with wv_gr_ultra_rel_euler (in contrast to the existing functionality for handling ideal gas equations of state, since in the ultra-relativistic case the fluid density and pressure are no longer algebraically independent, and so the baryonic number density equation does not need to be evolved, and the conservative-to-primitive variable reconstruction algorithm may be dramatically simplified using the approach of Neilsen and Choptuik);
Tetrad-basis representations of all general relativistic equation objects, alongside their standard curved spacetime variants (thus allowing for direct comparison between the two), namely wv_gr_euler_tetrad, wv_gr_ultra_rel_euler_tetrad, and wv_gr_maxwell_tetrad. These equation systems work by calculating a flat spacetime form of the flux and then applying a post-hoc geometric correction, rather than calculating the curved spacetime fluxes directly;
Initial prototyping work on coupled fluid-Einstein equations in plane-symmetric Gowdy spacetimes using the so-called "Medium" formalism of Barnes, Lefloch, Schmidt and Stewart, with wv_gr_medium. This has primary been done as a proof-of-concept demonstration that the kinds of finite-volume numerical algorithms currently implemented within the g0 moment app can indeed be used to evolve the Einstein equations in addition to hydrodynamic and electromagnetic ones, and that we need not restrict ourselves only to stationary spacetime metrics going forward. There is much more to be done here, but initial validation of the approach has been successful.

All of the new equation systems described above have been validated using both new unit tests (for instance, allowing one to compare the fluxes obtained through the tetrad-first flat spacetime flux correction approach vs. the fluxes obtained using the direct curved spacetime flux calculation approach) and new regression tests. There has also been substantial cleanup of various aspects of the GR code, including simplification of our Roe solver code (since, thanks to the tetrad-first approach, we need only worry about having an SR Riemann solver working in most cases) and streamlining of our handling of source terms thanks to the new moment source refactor.
In the medium-term, although Roe and Lax fluxes have been useful for initial prototyping and validation of these algorithms, I would ideally like for us to start transitioning to using some kind of intermediate approximate Riemann solver (Lax is typically too diffusive, Roe is typically too fragile and oscillatory), such as HLL, for our general relativistic equation systems. However, I wanted to open a PR for this functionality sooner rather than later, lest the branch become too far out-of-sync with main.

My only concern is that there are still a number of places in the GR code where we are doing internal mallocs, and I feel like we should avoid this at all costs. Is there a reason we do not allocate these arrays on the stack? https://github.com/ammarhakim/gkylzero/blob/2c9c1047337cf61060900936180c90bd5956f843/zero/wv_gr_euler.c#L23
I understand there are a couple of places, like with the inverse spatial metric, where right now it might still make sense to do a malloc and we can fix this later, but in these functions I do not understand why we are doing mallocs.

@JunoRavin Thanks! Most of the internal mallocs used in things like flux computations, source computations, and primitive variable reconstruction, have now been replaced with stack-allocated arrays. You're correct that there are still a few places, such as in the computation of inverse spatial metric tensors, where it still makes sense to use dynamically allocated memory - eventually I would like to wrap all of these in some kind of gkyl_tensor object that handles the memory management automatically (allocating on the stack wherever possible). We should revisit this soon, but for now I think this will do.


python3Packages.wikipedia: init at 1.4.0; python3Packages.langchain: enable wikipedia

Description of changes

add python3Packages.wikipedia
A Pythonic wrapper for the Wikipedia API
https://github.com/goldsmith/Wikipedia

add wikipedia to the dependencies of python3Packages.langchain

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

@ofborg eval

@ofborg build python310.pkgs.wikipedia
@ofborg build python311.pkgs.wikipedia


[ODS-5037] Force bash script to LF only

This change will not build correctly until ODS-5038 is solved.

works in git bash and bash in  Windows Subsystem for Linux (WSL))


Docs/minor fixes

Summary
This PR fixes the documentation-related issues #560 (missing arXiv link), #561 (broken appendix links), and #562 (Figure overflow)
Details
1. Missing arXiv link (#560)
The Introduction page refers to a forthcoming paper that will discuss the motivation behind the OpenQASM3 language specifications, even though the paper has already been released.
Fix: Rewrote "Scope" section to include link to arXiv paper arXiv:2104.14722
2. Broken appendix links (#561)
The Language page contains three references to appendices summary, grammar, and semantics. All three links seem to be broken, and I was only able to locate the grammar appendix page. Have the other two pages been removed?
Fix: Removed summary and semantics links, modified grammar link.
3. Figure overflow (#562)
The Built-in quantum instructions contains two figures. In the last figure, the bottom middle subfigure overflows into the caption. This issue seems to be specific to chromium-based browsers as it could not be reproduced by @hodgestar using Firefox, nor locally using Safari. It would be good if someone could independently verify this using Chrome.
Fix: Slightly increase max figure height.
Bonus: Rename OpenQasm → OpenQASM
I found two instances of OpenQasm (no capitalized ASM).
Fix: Rename OpenQasm → OpenQASM.

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


fix: ensure app.builder.outdir is a Path object

Fix #564 by ensuring the app.builder.outdir is a Path object.

Finally working in https://github.com/ansys/pydpf-core/actions/runs/11477549649/job/31942226295?pr=1787

Once merged, I will cherry-pick this into v1.1 and perform a patch so PyDPF can update.


Fixed crash when doing completion of :setfiletype

This PR fixes a crash in Vim-8.2.86 and older
when doing completion of :setfiletype and
dynamic allocation fails in vim_strnsave()
in globpath().
There actually no need to dynamically allocate there.

Codecov Report

Merging #5438 into master will decrease coverage by 0.06%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #5438      +/-   ##
==========================================
- Coverage    82.7%   82.63%   -0.07%
==========================================
  Files         134      134
  Lines      147806   147768      -38
==========================================
- Hits       122248   122115     -133
- Misses      25558    25653      +95

Impacted Files
Coverage Δ

src/cmdexpand.c
81.65% <100%> (-0.02%)
:arrow_down:

src/libvterm/src/vterm_internal.h
50% <0%> (-50%)
:arrow_down:

src/libvterm/src/rect.h
79.31% <0%> (-17.25%)
:arrow_down:

src/libvterm/include/vterm.h
25% <0%> (-12.5%)
:arrow_down:

src/libvterm/src/unicode.c
84.09% <0%> (-5.04%)
:arrow_down:

src/libvterm/src/encoding.c
72.91% <0%> (-3.13%)
:arrow_down:

src/libvterm/src/keyboard.c
81.7% <0%> (-2.44%)
:arrow_down:

src/libvterm/src/vterm.c
69.41% <0%> (-2.43%)
:arrow_down:

src/ui.c
70.69% <0%> (-1.72%)
:arrow_down:

src/libvterm/src/parser.c
89.07% <0%> (-1.1%)
:arrow_down:

... and 28 more

Continue to review full report at Codecov.

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


JUnit

Sync with develop
Made some syntax changes (will implement SwiftLint in the future so that we're all on the same page on how we write code for this project)
Reorganised the project a little bit
Added some logs in main.swift

Looks good to me! I'll think I'll merge this and then rebase on top of develop.


Using multiple API sources

Just wondered if there was an idiomatic way to configure one Admiral frontend instance to talk to multiple backend APIs?

The best way I've found is to do something like the following:

const multiDataProvider = (resourceMap: { [key: string]: DataProvider }) : DataProvider => {
  return {

    getList: (resource: string, params: object) => resourceMap[resource].getList(resource, params),

    getOne: (resource: string, params: GetOneParams) => resourceMap[resource].getOne(resource, params),

    getCreateFormData: (resource: string) => resourceMap[resource].getCreateFormData(resource),

    getFiltersFormData: (resource: string) => resourceMap[resource].getFiltersFormData(resource),

    create: (resource: string, params: CreateParams) => resourceMap[resource].create(resource, params),

    getUpdateFormData: (resource: string, params: GetOneParams) => resourceMap[resource].getUpdateFormData(resource, params),

    update: (resource: string, params: UpdateParams) => resourceMap[resource].update(resource, params),

    deleteOne: (resource: string, params: DeleteParams) => resourceMap[resource].deleteOne(resource, params),

    reorderList: (resource: string, params: ReorderParams) => resourceMap[resource].reorderList(resource, params)
  }
}

const usersDataProvider = dataProvider(usersUrl);
const replaysDataProvider = dataProvider(replaysUrl);

const mdp = multiDataProvider({
    'users': usersDataProvider,
    'replays': replaysDataProvider,
    'errors': replaysDataProvider
})

then supplying mdp to <Admin> as its dataProvider prop.
Is there a better/easier/more Admiral-ish way?

Thank you for your message!
We really didn't set the goal to support multiple APIs at the same time.
Admiral's logic initially involves passing a prefix for server-side URLs, e.g.: '/api', which would be substituted at the beginning of all URLs for requests.
The way you suggested looks good. I think this is the way to go.


Odst 217 workflows streamlining

We're done testing this for now, opened a PR on the upstream repo and wrote up some tickets based on the findings / next steps.


implement lists

A list section is different from other markup sections because it has sub-elements that are not markers.
A normal markup section has (a linked-list of) markers:
markupSection -> markers
But a list section has list items which have markers:
listSection -> listItems -> markers
To accommodate lists, the Abstract Tree (AT) will need to be able to traverse the leaf nodes (markers) of the tree — for semantic actions like splitting/joining sections and markers — without assuming that the max depth of children is always going to be 1.

[ ] editor-dom renderer can render list sections and list items
[ ] mobiledoc parser can parse list sections and list items
[ ] mobiledoc dom renderer can render list sections and items
[ ] mobiledoc html renderer can render list sections and items
[ ] Post parser must be able to reparse list sections
[ ] Actions on the post editor like splitMarkers must be able to handle markers that have a depth > 1

WIP on the lists branch


NoSuchMethodError with SuggestionsBuilder.getRemainingLowerCase()

CommandAPI version: 8.4.0
Minecraft version: 1.16.5
What I did:

Wrote a custom argument that has a StringArgument as a base. It uses the string to get a "profile" from the sender (basically in my plugin all players have profiles and you can get these by name (player.getProfile("name")).
The problem happens with ArgumentSuggestions.replaceSuggestions(ArgumentSuggestions.strings()).

The only other plugin I have is ViaVersion
Actual result:
Server shuts down with this error
Encountered an unexpected exception
java.lang.NoSuchMethodError: 'java.lang.String com.mojang.brigadier.suggestion.SuggestionsBuilder.getRemainingLowerCase()'
	at io.github.beefdev.profiles.plugin.commandapi.arguments.ArgumentSuggestions.toSuggestions(ArgumentSuggestions.java:110) ~[?:?]
	at io.github.beefdev.profiles.plugin.commandapi.arguments.ArgumentSuggestions.lambda$strings$2(ArgumentSuggestions.java:59) ~[?:?]
	at io.github.beefdev.profiles.plugin.commandapi.CommandAPIHandler.lambda$toSuggestions$7(CommandAPIHandler.java:861) ~[?:?]
	at com.mojang.brigadier.tree.ArgumentCommandNode.listSuggestions(ArgumentCommandNode.java:71) ~[spigot.jar:3096a-Spigot-9fb885e-af1a232]
	at com.mojang.brigadier.CommandDispatcher.getCompletionSuggestions(CommandDispatcher.java:596) ~[spigot.jar:3096a-Spigot-9fb885e-af1a232]
	at com.mojang.brigadier.CommandDispatcher.getCompletionSuggestions(CommandDispatcher.java:579) ~[spigot.jar:3096a-Spigot-9fb885e-af1a232]
	at net.minecraft.server.v1_16_R3.PlayerConnection.a(PlayerConnection.java:720) ~[spigot.jar:3096a-Spigot-9fb885e-af1a232]
	at net.minecraft.server.v1_16_R3.PacketPlayInTabComplete.a(SourceFile:35) ~[spigot.jar:3096a-Spigot-9fb885e-af1a232]
	at net.minecraft.server.v1_16_R3.PacketPlayInTabComplete.a(SourceFile:9) ~[spigot.jar:3096a-Spigot-9fb885e-af1a232]
	at net.minecraft.server.v1_16_R3.PlayerConnectionUtils.lambda$0(PlayerConnectionUtils.java:28) ~[spigot.jar:3096a-Spigot-9fb885e-af1a232]
	at net.minecraft.server.v1_16_R3.TickTask.run(SourceFile:18) ~[spigot.jar:3096a-Spigot-9fb885e-af1a232]
	at net.minecraft.server.v1_16_R3.IAsyncTaskHandler.executeTask(SourceFile:144) ~[spigot.jar:3096a-Spigot-9fb885e-af1a232]
	at net.minecraft.server.v1_16_R3.IAsyncTaskHandlerReentrant.executeTask(SourceFile:23) ~[spigot.jar:3096a-Spigot-9fb885e-af1a232]
	at net.minecraft.server.v1_16_R3.IAsyncTaskHandler.executeNext(SourceFile:118) ~[spigot.jar:3096a-Spigot-9fb885e-af1a232]
	at net.minecraft.server.v1_16_R3.MinecraftServer.bb(MinecraftServer.java:1061) ~[spigot.jar:3096a-Spigot-9fb885e-af1a232]
	at net.minecraft.server.v1_16_R3.MinecraftServer.executeNext(MinecraftServer.java:1054) ~[spigot.jar:3096a-Spigot-9fb885e-af1a232]
	at net.minecraft.server.v1_16_R3.IAsyncTaskHandler.awaitTasks(SourceFile:127) ~[spigot.jar:3096a-Spigot-9fb885e-af1a232]
	at net.minecraft.server.v1_16_R3.MinecraftServer.sleepForTick(MinecraftServer.java:1038) ~[spigot.jar:3096a-Spigot-9fb885e-af1a232]
	at net.minecraft.server.v1_16_R3.MinecraftServer.w(MinecraftServer.java:970) ~[spigot.jar:3096a-Spigot-9fb885e-af1a232]
	at net.minecraft.server.v1_16_R3.MinecraftServer.lambda$0(MinecraftServer.java:273) ~[spigot.jar:3096a-Spigot-9fb885e-af1a232]
	at java.lang.Thread.run(Thread.java:831) [?:?]

What should have happened:

The suggestion should have been shown in chat.

Fixed in 8.5.0.


Generate Source from az cli call

Is your feature request related to a problem? Please describe.
The problem which I try to resolve is the dynamic assign of Egress-IPs in OpenShift on Azure.
OCP 3.11: https://docs.openshift.com/container-platform/3.11/admin_guide/managing_networking.html#admin-guide-automatic-egress-ip
OCP 4: https://docs.openshift.com/container-platform/4.3/networking/openshift_sdn/assigning-egress-ips.html#nw-egress-ips-automatic_egress-ips
My current solution is manually assign the IP to a NIC which is not really HA friendly
az network nic ip-config create \
  --name ocpcp003-nic-egressip \
  --nic-name ocpcp003-nic \
  --resource-group ocp-rg \
  --private-ip-address <THE-EGRESSIP> \
  --private-ip-address-version IPv4 \
  --subscription <your-subscription>

Describe the solution you'd like
I would like to contribute to https://github.com/redhat-cop/egressip-ipam-operator which is written in golang. My Feature request is about two paramters in the cli which is able to create a source code from the az cli similar to curl --libcurl which creates a source code file from curls cli call.
My suggestion is the following.
az network nic ip-config create \
  --name ocpcp003-nic-egressip \
  --nic-name ocpcp003-nic \
  --resource-group ocp-rg \
  --private-ip-address <THE-EGRESSIP> \
  --private-ip-address-version IPv4 \
  --subscription <your-subscription> \
  --generate-code my-source-file.go \ # new parameter 1
  --programming-language golang # new parameter 1

Describe alternatives you've considered
Not alternatives considered
Additional context

I have tried to use the https://github.com/Azure-Samples/azure-sdk-for-go-samples/blob/master/network/ipaddress.go with https://github.com/Azure/azure-sdk-for-go and https://godoc.org/github.com/Azure/azure-sdk-for-go/services/network/mgmt/2019-11-01/network#NewInterfaceIPConfigurationsClient but I was not able to use the interface.

add to S170

add @jiasli  and @Juliehzl  for awareness.

@git001 Did you try terraform or ansible?

@MyronFanQiu nope because I need golang code to implement the ip-config create command

Azure CLI is written in Python. Besides it is impracticable to include all languages like Go, Ruby, C, etc. Also, curl --libcurl only supports C. 😉
You may be interested in Azure SDK for Go.
Another solution is to dump HTTP requests with --debug and make an HTTP call with any tools you like, including az rest:
> az group list --debug

msrest.http_logger : Request URL: 'https://management.azure.com/subscriptions/0b1f6471-1bf0-4dda-aec3-cb9272f09590/resourcegroups?api-version=2019-07-01'
msrest.http_logger : Request method: 'GET'
msrest.http_logger : Request headers:
msrest.http_logger :     'Accept': 'application/json'
msrest.http_logger :     'accept-language': 'en-US'
msrest.http_logger :     'User-Agent': 'python/3.8.1 (Windows-10-10.0.18362-SP0) msrest/0.6.10 msrest_azure/0.6.3 azure-mgmt-resource/9.0.0 Azure-SDK-For-Python AZURECLI/2.5.0 (PIP)'

Let's me know if this suits your needs.

@jiasli "at libcurl" I know ;-)
I'm on the way to learn the go sdk but it's quite difficult because I'm new to go.
Okay so you mean we should close this issue?

Hi @git001, I agree that SDK may be difficult to start with.
If the Azure management call is a one-time operation, I will go with the http REST API approach, which is more general and not language-specific. As for the authorization and authentication part, we recommend using a Service Principal, which can be created with az ad sp create-for-rbac, then follow OAuth 2.0 client credentials flow to get the access token for the request.
Another easier solution is to subprocessing az and call it from your program with exec.
So to summarize we have 3 approaches:

Azure SDK for Go
http
exec

Hope it helps.

thanks for the answers.


Doesn't "work" with all SMTP servers

Some institutional SMTP servers don't reply to the HELO command, nor does iCloud which knocks out much of the Apple world... is that right, or am I doing something wrong?

Yep, that's possible, and it's why email checking is tricky. This package unfortunately can't overcome those limits.


Add backing volumes to prometheus instances

This will be an update to our helm charts. Need to configure prometheus to use a pv. There should be a config flag to turn this on and off.

Implemented and documented. Closing:
https://pelorus.readthedocs.io/en/latest/GettingStarted/configuration/PelorusCore/#prometheus-persistent-volume
and
https://pelorus.readthedocs.io/en/latest/GettingStarted/configuration/ProductionBestPractice/


Malformed documentation on Subreddit.submit()

The documentation for the submit method of the Subreddit class has a note that is malformed due to the corresponding docstring which includes the sequence \n\n
I'm not too familiar with the way the documentation is generated as to provide a PR but it's probably an easy fix for anyone in the knows.
https://praw.readthedocs.io/en/latest/code_overview/models/subreddit.html#praw.models.Subreddit.submit
https://github.com/praw-dev/praw/blob/3acc5eb53c87898f8da00d842f13920511428f5b/praw/models/reddit/subreddit.py#L897

Just noticed another on https://praw.readthedocs.io/en/latest/code_overview/models/submission.html#praw.models.Submission.flair

Thanks for this! It will be fixed with #1618.


Performance Enhancement for Ember Store

During runtime the Ember Store is growing and consumes more and more memory.
Idea: Cleanup the store and keep only important data, possibly can be triggered via JS?

Can we now safely remove old data?

Todo: Try to use the unloadRecord function of an Ember model and report back if it works.  Use this in landscape-listener.

https://github.com/emberjs/data/issues/
closed issue number: 1849


Documentation presents second order sections as the correct choice where there is an engineering decision to be made

With commit aef60c7591f4c3feb2f2dc8db11fa3f1f0a909e1 the documentation takes a stance on the use of 'sos' over the 'ba' form of the IIR-filter without providing motivation. In the issue itself the stance is motivated as providing 'less numerical error'. However, in my use case the 'sos'-form takes twice the computation time of the 'ba'-filter. Developing for an IoT application this is a major concern, so it would be fair if the documentation states the reason for the recommendation and the potential costs involved.

From roots to polynomial coefficients mapping and vice-versa is quite well-known to be ill-conditioned (the poster child example is the Wilkinson polynomial). There are many examples for this and actually you can try it yourself. Especially when implementing digital filters transfer functions are broken down to their biquads etc. for this reason if for some reason cannot be avoided. This is not only relevant for this particular issue but also elsewhere see working with different representations section of https://nl.mathworks.com/help/control/ug/conversion-between-model-types.html
If you have a particular example to improve you can ask in StackExchange networks both in EE and SO. But without seeing any particular example, my gut feeling says that in context of evaluating the response this difference can't be significant.

The issue is about computation time at deployment, not the calculation of the filter coefficients.
Passing 100 seconds of 44.1 kHz data these are the differences in processing time (repeated 20 times see code):
time elapsed  for ba-filter: 0.05151940584182739 s
time elapsed for sos-filter: 0.11865202188491822 s
I see no qualitative differences between the outputs.
`import numpy as np
import scipy.signal
from matplotlib import pyplot as plt
import time
fs= 44100
dt=100
Generate some random data
timeseries = np.random.randn(dt*fs)
lp_numerator, lp_denominator = scipy.signal.iirdesign(0.2,0.3,2,80)
lp_sos  = scipy.signal.iirdesign(0.2,0.3,2,80, output='sos')
Apply BA filter
t = time.time()
for N in np.arange(0,20):
timeseries_lp = scipy.signal.lfilter(lp_numerator, lp_denominator, timeseries)
elapsed = time.time() - t
print(f'time elapsed  for ba-filter: {elapsed/20}')
Apply SOS filter
t = time.time()
for N in np.arange(0,20):
timeseries_lp_sos = scipy.signal.sosfilt(lp_sos, timeseries)
elapsed = time.time() - t
print(f'time elapsed for sos-filter: {elapsed/20}')
plt.figure(figsize=(30,20))
plt.plot(timeseries[int(4.95fs):5fs],'+')
plt.plot(timeseries_lp[int(4.95fs):5fs],'^-')
plt.plot(timeseries_lp_sos[int(4.95fs):5fs],'.-')
plt.show()
`

What version of scipy do you have?

Originally it ran under:
scipy.version: 1.3.2,   Ubuntu 16.04 on VM
time elapsed  for ba-filter: 0.05, filtertype = ellip, len_num: 8, len_denom: 8
time elapsed for sos-filter: 0.12, filtertype = ellip
time elapsed  for ba-filter: 0.056, filtertype = cheby2, len_num: 14, len_denom: 14
time elapsed for sos-filter: 0.2, filtertype = cheby2
time elapsed  for ba-filter: 0.055, filtertype = cheby1, len_num: 14, len_denom: 14
time elapsed for sos-filter: 0.2, filtertype = cheby1
I tested with a more recent version:
scipy.version: 1.5.0,   Ubuntu 18.04  on VM
scipy.version: 1.5.0
time elapsed  for ba-filter: 0.053, filtertype = ellip, len_num: 8, len_denom: 8
time elapsed for sos-filter: 0.056, filtertype = ellip
time elapsed  for ba-filter: 0.058, filtertype = cheby2, len_num: 14, len_denom: 14
time elapsed for sos-filter: 0.099, filtertype = cheby2
time elapsed  for ba-filter: 0.066, filtertype = cheby1, len_num: 14, len_denom: 14
time elapsed for sos-filter: 0.096, filtertype = cheby1
So it seems with the more recent version the differences in computational load are reduced. For elliptic filters they have become neglible in this case. So the point remains there is a trade-off to be made which requires the user to do some research, and this also implies there is a reason to keep 'ba'-filters around in the mind of the person reading the documentation.
Reproduction notes:
In all cases 100 s of 44.1kHz whitenoise (np.random.randn) was passed through the filters, repeated 100 times to compensate for fluctuations due to background processes. Times stated are averages.
Butterworth is not included because it is not numerically stable at the given settings. I guess that proves the point of @ilayn . But I think I am happy with cheby2, which doesn't suffer from this problem.
I can try to propose a text change:

Current: Default is 'ba' for backwards compatibility, but 'sos' should be used for general-purpose filtering.
Proposed: Default is 'ba' for backwards compatibility. In general 'sos' is recommended because inferring the 'ba' coëfficients suffers from numerical instabilities. Using the 'sos' filter  is sometimes associated with additional computational costs, for data-intense use cases it is therefore recommended to also investigate the 'ba'-filter format.

r = 5
ripple = 0.05
suppression = 50
lp_numerator, lp_denominator = scipy.signal.iirdesign(0.8/r,1.0/r, ripple, suppression, ftype=filtertype)
lp_sos  = scipy.signal.iirdesign(0.8/r,1./r,ripple, suppression, output='sos', ftype=filtertype)

Ah sorry for misunderstanding earlier. Yes this looks a bit strange that SOS evaluation takes x2 longer. Documentation fix is fine but I'm curious why it is costing that much. I'll try to have a look

The first build had problems due to an offending character. But the current problems seem to go beyond my span of control.
Something to do with build environment it seems to my untrained eye.

@ilayn Can you advise on how to get this passing the build tests?


release of the template package for v1.0

[ ]  Clean up the README
[ ] Explain difference between original template branch

Needs to be citable too, like maybe a Zenodo DOI.

This was reportedly done in Jan 2019 but not tagged.

This is separate from what I mentioned and this is related to the STScI package template -- it was requested to update that with more information in line with what is in the style guide.

Ah, okay. Thanks for the explanation!


Add dungeon crawl stone soup tiles and console version.

This adds manifests for the ASCII version and graphical version of the roguelike Dungeon Crawl Stone Soup.

Hold on, actually. I noticed running the exes creates two folders in the directory where it is run. I'll see if there is a way around this


Support JavaScript inter-operation in Node environment

Describe the solution you'd like
To be able to directly run JavaScript code from Insitux, as the web environment currently can.
Describe alternatives you've considered
There is no real alternative for normal Insitux users.
Additional context
It might be good to be able to disable this and the other system IO available for security.

An extremely hacky workaround has arisen with the introduction of the exec command in the Node environment, but it really does not satisfy this issue.


changing setting doesn't work in firefox

Changing any setting won't affect output on Firefox, Safari works fine.

Well, I lookup on this later.

Fixed.

Working now, thanks


Simplify rotate functionality

Added degrees option to enable the page(s) to be rotated either 90, 180 or 270 degrees in one go.  Also fixed a bug in the logic where pages that weren't specified were getting excluded or exhibiting other weird behaviour.

Updated.  Also made a small tweak to preserve compatibility with the original.

Thanks for this :)


Include copyright info in LICENSE

Hello, I'm building a project using your library (thanks for the work btw) and wish to include it in binary form.
In documenting licensing, I'd like to point to your LICENSE file, but the info on this line isn't filled in: https://github.com/WalkerKnapp/devolay/blob/254336497a3f48ef6b5b5a9c1ec637aa572c2446/LICENSE#L189
Not urgent, but I just thought you should be aware.  Thanks again!

Hello! Thanks for your interest in the project.
If I am understanding the text of the license correctly, I believe that section is supposed to serve as a template for headers on specific files (i.e. https://github.com/tensorflow/tensorflow/blob/d314c2e738bffe292d0b09eb87e1d43d90b8996d/tensorflow/init.py#L1), which I felt were unnecessary for this project. I don't believe it's supposed to be filled in for the LICENSE file.
I know that a lot of projects use this header blurb as the copyright notice, but that doesn't seem right to me personally. As far as I can tell, the license wants users to include it verbatim. I would prefer if a binary included text like this in the licenses disclaimer:
*********************************************************************************
Devolay (https://github.com/WalkerKnapp/devolay)
Licensed under the Apache License 2.0

                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

< ... the remainder of the LICENSE file ... >

Or if space is limited, a reference to the distribution by Apache seems like a common way to acknowledge it.
Devolay (https://github.com/WalkerKnapp/devolay)
Licensed under the Apache License 2.0 (http://www.apache.org/licenses/LICENSE-2.0)

Honestly, my binaries should probably include a copy of the license themselves so this becomes a non-issue. I'll try to resolve that in a future version.
Also, make sure you have read over https://github.com/WalkerKnapp/devolay#licensing-considerations and are staying within NewTek's licensing requirements. Apache 2.0 is fairly permissive, and I'm not going to be causing any problems over the use of this project, but NewTek definitely cares more.
Let me know if I can help any more with this! I always love to hear about projects that find my code useful :)

Thanks for the suggestions and quick response!
I placed your license alongside the jar file in my repo and linked to it in the readme (as well as following the Newtek licensing info as much as possible).
https://github.com/nocarryr/ndiMultiview-pde
For now, I'm only including the dynamically linked version of the library until I'm sure I've got everything right with Newtek's requirements.
Thanks again


Bump version to 0.1.0

Preparation for first release of this crate.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 78.315%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
632

Relevant Lines:
807

💛  - Coveralls


set "relativeurls" to true in the registry config

This allows your registry to work correctly if you're making the TLS
termination on a frontend. Not compatible with docker 1.7 and earlier.

See https://github.com/docker/distribution/issues/970#issuecomment-363606424 and https://docs.docker.com/registry/configuration/

This is available in cs:~containers/docker-registry-85 and higher.


Using .First instead of .Single

.Single() returns the only element of a sequence, and throws an exception if there is not exactly one element in the sequence. It is better to use .First() instead which only returns the first element in the sequence and does not throw an exception.

I know that First() is faster than Single(), but I used Single() in order for the code to break if the count is greater than 1.
What is your consideration for using First()?

Thank you for the sample of the md file
I will look into why there are more than one elements and fix the issue

most of the cases are solved in #19 (I was able to render your md file without errors)
At the first glance there are no rendering mistakes. Please open an issue if something still persists.
For the time being the only issue #18 (Blazor does not navigate to anchor-links out-of-the-box)
When the issue is fixed I plan to create a new NuGet release. Quite a lot has been done so far


Oracle solaris version

Do you have any plans to make php client library compatible to Oracle Solaris ? Currently it does not build without minor changes in code, but when built it randomly crashes php memory, leading to segaults.

We honestly get few requests for Solaris and PHP. We're happy to accept pull requests that solve any issues, or work together to fix any issues you find.
We're working pretty hard on PHP7 and HHVM, though !


IsEmaBullishCross Or IsEmaBearishCross Always false

Hello I am trying to figure out how to know if the Ema is Bullish or Bearish.
I did a backtesting using IsEmaBullishCross  and IsEmaBearishCross  and they are working fine
` var buyRule = Rule.Create(ic => ic.IsEmaBullishCross(21, 55));
var sellRule = Rule.Create(ic => ic.IsEmaBearishCross(21, 55));
        var runner = new Trady.Analysis.Backtest.Builder()
            .Add(candles)
            .Buy(buyRule)
            .Sell(sellRule)`

The problem is when I am trying to get the buy signal and sell signal from the exchange always is False.
I am using the IndexedCandle like this:
`
var ic = new IndexedCandle(candles, candles.Count - 1);
var buyRule =(ic => ic.IsEmaBullishCross(21, 55));
var sellRule = (ic => ic.IsEmaBearishCross(21, 55));
`
Maybe I am doing something wrong.
I would appreciate some help.
I did my own testing and I found something very interesting
I implemented my own indicator called TemaIndicator
I followed the examples and I did thisd
//public static bool IsTemaBullishCross(this IIndexedOhlcv ic, int periodCount1, int periodCount2)
// => ic.Get(periodCount1, periodCount2).ComputeNeighbour(ic.Index)
//      .IsTrue((prev, current, _) => prev.Tick.IsNegative() && current.Tick.IsPositive());
    //public static bool IsTemaBearishCross(this IIndexedOhlcv ic, int periodCount1, int periodCount2)
    //    => ic.Get<TemaIndicatorOcillator>(periodCount1, periodCount2).ComputeNeighbour(ic.Index)
    //         .IsTrue((prev, current, _) => prev.Tick.IsPositive() && current.Tick.IsNegative());

Same as many extensions when I use them with back testing is working fine but with real data never always they return false like macd crossing, emabearishcross, emabullishcross etc..
I modified this extension like this:
public static bool IsTemaBullishCross(this IIndexedOhlcv ic, int periodCount1, int periodCount2)
    {

// original code
var test = ic.Get(periodCount1, periodCount2).ComputeNeighbour(ic.Index)
.IsTrue((prev, current, _) => prev.Tick.IsNegative() && current.Tick.IsPositive());
//  traditional way
var tema1 = ic.Get(periodCount1).Compute()[ic.Index];
var tema2 = ic.Get(periodCount2).Compute()[ic.Index];
if (tema1.Tick.Value > tema2.Tick.Value)
{
return true;
}
else
{
return false;
}
    }

and finally the cross was fired ....
there is a bug with the extensions.
I would like to help to fix the problem but for now is the only way I found to fix them.
Thank you!

@RikardoPons Sorry for late response. I have double checked and tested the code on IsEmaBullishCross, and it should be correct for the result.
You have mentioned that you have changed the logic from the original one to your traditional one, and works. But they are different in concept, my code is determining if an "intersection point" exists when ema10 cross ema30 upwards for IsEmaBullishCross, similar for IsEmaBearishCross. But your code is determining if ema10 is larger than ema30 which includes the case of "intersect", so you may find a larger set of result when using this logic.
I've also included a test case "TestBullishCrossAlwaysFalseAsync" and the verification excel for the case for the reference. Thanks.

Thank you for your answer.
I think I found a possible issue but it is not from your code. I am getting data from som Exchanges like Bittrex and Binance but I realized there are missing candles in the request sometimes. I guess this is affecting the interection when I use IsEmaBullishCross for example.

okay. May I close the issue as it's a fixed issue?

The issue should have fixed, but no response from @RikardoPons . Close.

I am sorry for the late reply. I could not fix the problem. I mean when I do backtesting the method is working fine but... when I do a request to get the candles the result is always false. I am struggling with this issue now..

Do you mean you want to get all the candles that should fulfill a condition or not?

I am getting the candles from the exchange  trying to find a buy signal or sell signal.. If I download these candles and I do a backtesting everything is fine I can get the buy and sell signals only when I do backtesting.. If I get the candles from the exchange and I apply the algo using this method Always is false.

May I know how you are trying to apply the algo to determine the condition in code level? It may be misuse of the determine method. Could you paste the code to let me test it?

For example I want to apply this algo just it is working when I use backtesting.
`
var ic = new IndexedCandle(candles, candles.Count - 1);
var buyRule = (ic.IsEmaBullishCross(21, 55) && ((ic.Ema(8) > ic.Ema(13)) && ic.Ema(21)> ic.Ema(55)));
var sellRule = (ic.IsEmaBearishCross(21, 55) && ((ic.Ema(8) < ic.Ema(13)) && ic.Ema(21) < ic.Ema(55)));`

Is the Ema method declared by you?

Yes I did  my own extension. It's forking fine. You can try just using IsEmaBullishCross  and IsEmaBearishCross and I got the same result for example trying to get a buy signal and sell signal using Emas strategy 12,26 whatever always raturn false. But did some testing and your code looks fine my theory is the candles I'm requesting each period of time  must be synchronized with the exchange and get the candles few seconds after the exchange update the their feed. I will try to do that. Just I'm thinking  why just in backtesting your methods are working fine and they don't work when I am requesting the candles from the exchange

Okay. I have to check it first as I am now busy with another project, I will get back to you later.

@RikardoPons I've just checked the logic, the index you use in transaction differs the actual index by 1. The buy/sell procedure should be
Hit buy/sell rule (current timeframe) -> Buy/Sell stock (current timeframe + 1)
So, if you need to verify the condition you should use new IndexedCandle(candles, index - 1) to check rather than new IndexedCandle(candles, index)

If I understand my code should be like this
var ic = new IndexedCandle(candles, candles.Count - 2);
I will try it!
Thank you!

@RikardoPons Once you've tested ok, it would be good to help to close this issue. Thanks.

@lppkarl  thank you  Now is working properly!


Filter sobel plugin

Pull Request for the first version of the imagej-filter-sobel-plugin which was automatically generated with the imagej plugin generation pipeline.

Note that this PR is downstream of the currently open imagej-ui PR, which is the current iteration of the ImageJ pipeline. This PR will show changes to the entire pipeline (not just the plugin files) until the imagej-ui PR has been merged into PolusAI:dev.


dev mode

How can i open nuterra in dev mode?

There is no dev mode for Nuterra

But what about this? Why os it then in  the wiki?https://github.com/maritaria/nuterra/wiki

If he says no Dev-Mode there is No Dev-Mode

That is a seperate mode for the installer to use, will be more documented later on


Feature Request: Paste Special

I would like the ability to paste special, such as paste add, paste multiply, and other custom formulas.
Thanks

why not give pr

It is a whole new implementation, not just a modification to this repository.


MaxPooling2d error?

Hi,
I have an issue with the MaxPooling2d layers in Keras using theano (and in theano itself).
I fail to run my code when I use a MaxPooling2d layer in Keras (using theano). I have my own neural network code using theano which also fails when I use the theano maxpooling:
from theano.tensor.signal import pool
pool_layer = pool.pool_2d()
Perhaps there is an issue in this new maxpooling version in theano? I believe that it was recently changed, previously being:
from theano.tensor.signal import downsample
Basically running the MNIST convolutional example fails with the maxpooling layer in Keras, but works without. You can see the simple code here:
https://github.com/fchollet/keras/blob/master/examples/mnist_cnn.py
I would very much appreciate any help. Since everything else is working for me, I have an idea that this is a general issue.
Thanks,
Marco

What is the error message? Without that it is hard to help.
Make sure to use Theano dev version.
On Sat, Oct 22, 2016 at 1:43 PM, marcohekla<EMAIL_ADDRESS>wrote:

Hi,
I have an issue with the MaxPooling2d layers in Keras using theano (and in
theano itself).
I fail to run my code when I use a MaxPooling2d layer in Keras (using
theano). I have my own neural network code using theano which also fails
when I use the theano maxpooling:
from theano.tensor.signal import pool
pool_layer = pool.pool_2d()
Perhaps there is an issue in this new maxpooling version in theano? I
believe that it was recently changed, previously being:
from theano.tensor.signal import downsample
Basically running the MNIST convolutional example fails with the
maxpooling layer in Keras, but works without. You can see the simple code
here:
https://github.com/fchollet/keras/blob/master/examples/mnist_cnn.py
I would very much appreciate any help. Since everything else is working
for me, I have an idea that this is a general issue.
Thanks,
Marco
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/fchollet/keras/issues/4145, or mute the thread
https://github.com/notifications/unsubscribe-auth/AALC-3tBdQUYMIfRnzun03sHVGFTJWnTks5q2ksmgaJpZM4Kd69-
.

Hi, the error is the following:

Everything is working fine in my conv network, except the maxpooling. Any suggestions would be great - thanks.

This is a partial error message. Can you redirect the output of the python
script to a file and send this? The current error don't have enough
information.
On Wed, Oct 26, 2016 at 1:40 PM, marcohekla<EMAIL_ADDRESS>wrote:

Hi, the error is the following:
[image: maxpool_error]
https://cloud.githubusercontent.com/assets/23002157/19737472/ea86a7c8-9bb3-11e6-89e3-480f218b8aa2.png
Everything is working fine in my conv network, except the maxpooling. Any
suggestions would be great - thanks.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/fchollet/keras/issues/4145#issuecomment-256423271,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AALC-xPSBPr_38ydezW9oHIKEPgbT1Ccks5q35CpgaJpZM4Kd69-
.

Hi Nouiz,
Thanks for taking the time to help me out!
One question before I attempt getting the full error message; can you make maxpooling work? An easy way to test it would be to use the following code example on the MNIST data set:
https://github.com/fchollet/keras/blob/master/examples/mnist_cnn.py
If you (or anyone else in here?) can use the maxpooling, then there is something wrong with my setup..
I just tried to redirect the error message using the following code:

import sys
sys.stderr = open('errorlog.txt', 'w')
#do stuff
sys.stderr.close()
sys.stderr = sys.stderr

It gave me the errorlog.txt attached here.
Best regards,
Marco
errorlog.txt


feature: Paragraph Indentation

I'd like a way to set the indentation for a paragraph. From an initial run through the code, it looks like there's not currently support for such a thing, but it wouldn't be too hard to add. I'm willing to make the needed changes, but want to make sure I go about it correctly.
Most of the needed functionality already exists as a result of having paragraph justification/alignment. The needed xml is pretty simple:
<w:pPr>
    <w:ind w:left="XX" w:hanging="XX" w:right="XX"/>
</w:pPr>

It would mostly just be a matter of adding the necessary fixtures to the API to let the user pass an integer in for the desired indentation values.

Added with release v0.8.0 on Feb 8, 2015.