Setting this up to work

@GregBrimble this workflow looks amazing, but I'm having trouble setting this up and testing that it works.

I created a private repo with secrets for TAILWINDUI_EMAIL and TAILWINDUI_PASSWORD
I also created a .github/workflows/default.yml file based on the example at https://github.com/GregBrimble/tailwindui-crawler-action

name: Example/Test
on:
  push:
  schedule:
    - cron: "0 0 * * *" # Every day at midnight

jobs:
  test:
    name: Example/Test
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v2
      - name: Run crawler
        uses: gregbrimble/tailwindui-crawler-action@master
        with:
          email: ${{ secrets.TAILWINDUI_EMAIL}}
          password: ${{ secrets.TAILWINDUI_PASSWORD }}

I then set up github notifications for my private repository.

At no time did I clone https://github.com/GregBrimble/tailwindui-crawler-action or https://github.com/kiliman/tailwindui-crawler/
Am I missing a step? Thank you!

Hi @connecteev !
Thanks for trying this out :) Sorry it isn't working for you straightaway.
Have you first tried the example config in the README.md?
# .github/workflows/default.yml

name: Update
on:
  schedule:
    - cron: "0 0 * * *" # Every day at midnight

jobs:
  update:
    name: Update
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v2
      - name: Run crawler
        uses<EMAIL_ADDRESS>        with:
          email: ${{ secrets.TAILWINDUI_EMAIL }}
          password: ${{ secrets.TAILWINDUI_PASSWORD }}

Setting up the secrets sounds good, and notifications sound fine. And you shouldn't need to clone either repo, since this happens in the Action.
Do you have any errors appearing in the Action logs?
If possible, please provide a screenshot/copy-paste of those logs, and of your yml file configuration, and I can dig into this for you :)

Thanks @GregBrimble I got it to work....and it works like magic :)
I had made a really dumb error where my default.yml was not placed within .github/workflows/default.yml (though I thought I had), moving it to the correct place fixed it.

@GregBrimble Quick questions here

Let's say the cron runs every minute of every hour, is that too much? What is the drawback of doing that?
I assume this code will auto-update either when:
tailwindui source code changes
tailwindui-crawler code changes
Is that correct?

Thanks for this repo, it's starting to make me think about what else github actions can be used for!

Every minute of every hour is definitely overkill. TailwindUI is updated relatively infrequently (less than once a week, typically), so there is no need to be checking that frequently, (since no changes would be made). In fact, since the action takes longer than a minute to complete, it may actually cause problems when committing the changes because of conflicts with concurrent committing actions.
Besides, anything too regular is just putting unnecessary strain on both tailwindui.com (and they wouldn't be too happy) and on GitHub Actions itself (and you will quickly overrun your free quota!). I set once a day as a reasonable default example. But feel free to adjust to something like twice a day if you need.

The action will always fetch the latest TailwindUI code. The version of the kilman's https://github.com/kiliman/tailwindui-crawler can be selected by specifying crawlerref (see the Advanced section of the README.md). By default, it uses the latest version, master.
As for the version of this action, if in your config, you have uses<EMAIL_ADDRESS>you will be pinned to version 1.0.0. I do suggest pinning your version, just in case I ever break master, but you can configure this however you wish.
I recommend watching this repository (Releases Only) to be notified when I release a new version.

I'm glad it has inspired you! Check out https://github.com/sdras/awesome-actions for some other excellent projects.

@GregBrimble Very interesting!

I didnt know that github actions had a quota...also great point as each job would take longer than 1 min to run anyway! I have reduced the frequency down to once every 6 or 12 hours...so I can get notified of the update.
Thanks for the tip on the advanced settings, I am going to stick with your defaults for now since they work well! Once I
And, I have pinned the tailwindui-crawler-action version to<EMAIL_ADDRESS>per your recommendation. I am watching this repo for changes as well :)

Both this project and the original one by kiliman are amazing..thanks for doing it.
ps. I have also starred https://github.com/sdras/awesome-actions -- I was wondering if there's an easy and free way to monitor my website's uptime with github actions, but I guess I could just use the free plan of https://uptimerobot.com/pricing !

Just for private repos, I think :) Sounds good 👍
Awesome :)

Great idea! Should be pretty simple to implement. The hardest part would be finding somewhere to dump your data (although I suppose you could commit it to git?) I do have a simpler (unrelated) GitHub Action here, which you might be able to use as a starting point? Good luck!

@GregBrimble thats awesome, thanks for the tip.
Unrelated, do you want to collaborate on any projects I'm working on? Some things I have in progress: Painless saas payments in Laravel (Plan upgrades and downgrades, Free trials both during registration / without payment, and after payment, Plan cancelations, Prorations, Grace periods, etc). The goal is to do this once, make it bullet proof and never have to worry about it again (other than minimal maintenance).
Would be great to get the help of another smart person. Discord handle in bio if interested!

@connecteev , added you!


Add support for OCaml

Examples:

Nice work!
I’m not quite sure about the aliases; is there any semantic meaning in them, or are they purely to get highlighting for the current themes?

I'd say that the directives aliased as functions have some meaning.
But I must admit the type token aliased as variable is purely for visual purpose... I kinda thought that's what aliases were for.

The builtin alias could be the easy alternative (as it does not mean much by itself...), but this is just bypassing the problem, isn't it?


[silgen] Create a function level scope when open coding implicit value initializers.

The Original Bug
In ffbfcfa131465daca2018fbdd34015899a9c0d00, we fixed a bug around implicit
value initializers but did not cherry-pick it to 5.3. While investigating a bug
that turned out to be that same bug (no worries!), I noticed that there is
additional code that is "unsafely" correct in this area and that while
ffbfcfa131465daca2018fbdd34015899a9c0d00 is correct in the small, we can expand
on the fix to prevent future bugs.
The Larger Bug
Here we are still open coding using ManagedValue/Cleanup APIs /without/ a top
level function scope. The code is only correct since we never emit unconditional
cleanups and always manually forward conditional cleanups. If we did not do
either of these things, we would have another instance of this bug, namely a
cleanup that is never actually emitted. So the code on master today is correct,
albeit unsafe, and we already have coverage for this (namely the test case from
ffbfcfa131465daca2018fbdd34015899a9c0d00).
That being said, in general when working with ManagedValue APIs (especially in
utility functions) we assume that we have a scope already created for us by our
caller. So by fixing this issue we are standardizing to safer SILGen invariants.
Building on ffbfcfa131465daca2018fbdd34015899a9c0d00
This commit builds on the shoulders of ffbfcfa131465daca2018fbdd34015899a9c0d00
by adding the function level scope mentioned in the previous section so that we
are now "safely" correct.
While looking at this I also realized that just using a normal scope when open
coding here may be a bit bugprone for open coding situations like this since:

If one just creates a scope in open coding situations, the scope will fire at
end of the c++ function /after/ one has probably emitted a return.

Once one has emitted the return, the insertion point will no longer be set
implying =><=.

To avoid this, I created a move only composition type on top of Scope called
AssertingManualScope. This type just asserts in its destructor if the scope it
contains has not been popped yet.
While, one can pop it by ones self, I added an overload of createReturnInst on
SILGenBuilder that also takes an AssertingManualScope and pops it at the
appropriate time.
So now when performing simple open coding tasks, we have the ability to in code
tie together the function level scope to the actual creation of return inst,
simulating the hand-off of lifetimes/resources from caller/callee that often
happens in the epilog of functions.
rdar://problem/63189210

@swift-ci test

@swift-ci test

@swift-ci test windows platform

@jckarter ping?

Makes sense.


Research projects on GitHub

Found accessibility page on GitHub but unsure of whether this meets specific guidelines.
Emailed Ellen Doyle from ability network asking for support


git trim --help does not show manual entry

❯ git trim --help
No manual entry for git-trim

❯ git-trim --help
usage: git trim [options]

    Removes merged, pruned, untracked, and stale branches within a repository.
    https://github.com/jasonmccreary/git-trim/

Available options are:
    --all                 remove all local branches, except the current branch
    --dry-run             prints branches which will be removed instead of deleting them
    -m, --merged          remove local branches already merged into the current branch
    -p, --pruned          remove local branches where its remote branch no longer exists
    -r, --remote          remove remote branches instead of local branches
    --reset[=...]         remove all local branches except those existing on remote (default: origin)
    -s, --stale           remove local branches without commits in the last 3 months
    -t, --tracked         remove the tracking branch from remote
    -u, --untracked       remove local branches not tracking a remote branch

Yeah, when installing via npm, I don't believe it correctly passes through the --help option to Git and attempts to read its own manual entry.

I installed it by copying the shell script, not npm.

Gotcha. I'm not sure how to register a manual entry for a custom Git command. The -h option works, but not --help. 🤷


Disable if user prefers reduced motion

Motion can be a problem for some users. A media query can determine if the user prefers reduced motion. Should we disable all transitions if that's the case? Or should that be left to the consumer?
Reference:
https://www.joshwcomeau.com/react/prefers-reduced-motion/

Dup #40


Rework how tenant admin works

Currently, the tenant-admin is defined by setting auth.users.raw_app_metadata to
{
   "tenant_access": "write"
}

That works, but I was thinking that it might be better to create a "tenant_admin" postgresql role. And add it to auth.users.role column. This looks like a more native approach. However, if I create this role, it will not have access like the standard users.
And I'm not a PostgreSQL expert. Is this really a better way of doing it? What do you think?

You should be able to grant 'authenticated' to your postgres role and it should then be able to do whatever that role can do.
I think it is grant authenticated to bob   Then if your RLS TO role is authenticated it should work for bob also.  It will not work for the auth.role() or using the role in the jwt calls in RLS.

After a short research, I'm starting to think that using custom Postgres roles, might not be the best way to proceed.
@GaryAustin1 , In the referred chat, you mentioned that

I'll also chime in again on the Supabase has not "blessed" this approach.  It worked last year and then did work for several months when they changed the Postgres role.  In the thread I linked Supabase itself never says this is supported with their REST API.

Do you still believe it? Shall I continue using auth.users.raw_app_metadata instead of migrating to postgresql roles?
References:

https://discord.com/channels/839993398554656828/1108484119626780783
https://github.com/orgs/supabase/discussions/11948

I would say if you know postgres well you have a better shot of dealing with things if something is changed by Supabase.  I was discouraging that user because the did not seem to understand grants and privileges with postgres roles.
Using this method relies on Supabase granting postgres role certain privileges (which they have done after they broke it), but that is also needed for test jwt RLS in the SQL editor so may not have been done for the issue in your github link).
It also relies on using a column in the auth schema that is also not shown to be used by Supabase anywhere that I know of.
I doubt role column will change or be unavailable though.  PostgREST itself is probably fine as it uses that without Supabase.
I'm not sure what storage-api and realtime will do with the role field as far as RLS, have not tested it so may work.


How to change the color filled in the plot area in the LineChart?

The version of the LiveCharts used by me is <IP_ADDRESS>.
The default color of the plot area of LineChart is green.
I wonder how to change the color filled in the plot area in a LineChart.
Changing the background property does not work.
Thank you very much!

<IP_ADDRESS> is the version I am working with to publish 0.6.6 you should not use it, it is a debug version the green color helps me to debug, please use 0.6.5 when 0.6.6 is ready I will announce it here https://github.com/beto-rodriguez/Live-Charts/releases also you will see it in nuget

OK. Thanks very much!


BG music issues

It is currently impossible to control the background music from Esc script.
Discussions from #34
@fleskesvor

There's something strange going on with globals/bg_music.gd too, I think. It seems like set_state() is being called before this assignment happens: https://github.com/StraToN/escoria/blob/3.0/globals/bg_music.gd#L3
which means the function returns on line 19, so it never complains about the errors on lines 28 and 30.

StraToN:

I wonder if this is related to the fact that bg_music.tscn's script inherits item.gd.
This causes this scene to be registered by the VM at launch although the scene is not ready yet. Maybe use call_deferred() ? Besides it causes the presence of an item in top-left corner of the game zone.
(telon.tscn has the same problem)

@fleskesvor

Yeah, that sounds plausible. The behavior is the exact same in the original Godot 2 version anyway, so this is not a regression. Does it cause any issues besides the fact that it's currently not possible to start background music from an .esc script? It's worth investigating, but maybe there should be an issue for it, since the problem is already present.

TL;DR

bg_music.gd 's set_state() in called before the scene is properly instanced. Not sure if it is a bug in Godot.
bg_music.gd and telon.gd inheriting item.gd may be a problem

Not a high priority at all. @reduz told me on reddit, jitter is completely normal for game engines.

This is seriously still an Issue?
May I suggest making a dedicated function for changing the music. It'd be easier.

On Sat, Mar 10, 2018 at 11:00:52PM -0800, lavaduderDev wrote:

This is seriously still an Issue?
May I suggest making a dedicated function for changing the music. It'd be easier.

I am nowhere near having music in anything, so I don't necessarily understand
this. I believe it's common to have an iMuse-like state machine for switching
between songs. This is not true in Escoria?
Tried looking around a bit for Wwise/Fmod for Godot, and apparently Fmod can
be integrated manually. Is this relevant for Escoria?
An explicit function definitely sounds like the easiest solution, so the game
can react to events.

Godot has several nodes for playing audio, including AudioStreamPlayer, which is suitable for background music, and AudioStreamPlayer2D, which can be used for positional audio, like sound effects and speech.
There is bg_music.tscn, which can be used for setting background music, but currently there are some issues with setting music from .esc scripts.
The way it's supposed to work is that you call eg. set bg_sound res://demo/audio/music/music.ogg from an .esc script and then the set_state function of that node is called, since it's registered with the global_id bg_music.
This probably wasn't working in Godot 2.1 either, since the background music there was just added directly to the bg_music.tscn node and set on autoplay.

But basically you're saying that if things worked, triggering music changes on events would be doable?
What a shame it probably wasn't working. The world would be a better place if open-sourced projects actually worked :/ Maybe it's easy to fix.

Yes, once that's fixed, it should just work. I will take another look at it now that the dust from the 3.0 migration has settled.

Hi! The issue seems to be back in the esc2-godot3.2 branch:
I'm not able to change the background music from an .esc scrip using set_state bg_music res://xxx.ogg, while it does work on the main branch.


New update is not working on Julia v.0.4

I cannot identify the issue, it seems it has something to do with IJulia.jl. But I cannot figure it out. I am running the nightly build on Mac OS via command line.
PS: it is working on v.0.3.7
ERROR: LoadError: LoadError: error compiling anonymous: unsupported or misplaced expression "import" in function anonymous
 in include at /opt/local/julia-dev/lib/julia/sys.dylib
 in include_from_node1 at /opt/local/julia-dev/lib/julia/sys.dylib
 in include at /opt/local/julia-dev/lib/julia/sys.dylib
 in include_from_node1 at /opt/local/julia-dev/lib/julia/sys.dylib
 in reload_path at /opt/local/julia-dev/lib/julia/sys.dylib
 in _require at /opt/local/julia-dev/lib/julia/sys.dylib
 in require at /opt/local/julia-dev/lib/julia/sys.dylib
while loading /Users/Randy/.julia/v0.4/RCall/src/IJulia.jl, in expression starting on line 3
while loading /Users/Randy/.julia/v0.4/RCall/src/RCall.jl, in expression starting on line 75

This appears to be due to https://github.com/JuliaLang/julia/issues/8051.
I'll push a fix that can avoid this problem,


Shutdown

log more things, volatile vars for sentinel bool var and thread.join timeout to allow thread to shut down reliably

👍


suggestion: QR Code generation URL for invitation

There are currently 2 main endpoints for generating invitations:

POST /connections/create-invitation
POST /out-of-band/create-invitation

both returns a invitation_url property. Would be possible to also return an invitation_qrcore_url with a link to an endpoint that returns the generate QRCode image (e.g.:png)?

What would be the use-case for this? we found that if the QR Code needs to be displayed in a user interface it is easier to have it generate it and embed it as needed, rather than having to deal with generating and transferring image files. Also keep in mind that the proposed approach would make it impossible to add a URL shortener service - if needed.

Closing as the QR Code generation seems more like a frontend capability.


[8.x] @checked Blade directive

Hi! This PR's only a small one, but something that I thought might be useful. It adds a new @checked Blade directive that can be used in views.
In almost every project I've worked on, I always see this type of approach used for determining whether 'checked' should be placed on a radio button or checkbox:
<input type="radio" name="active" value="1" {{ old('active', $user->active)) ? 'checked' : '' }}/>

<input type="radio" name="active" value="0" {{ old('active', $user->active)) ? '' : 'checked' }}/>

With @checked, you could pass the condition straight to the directive and let it handle it for you. As a quick example, say you had the following Blade in a form that you can use to update a user model:
<input type="radio" name="active" value="1" @checked(old('active', $user->active))/>

<input type="radio" name="active" value="0" @checked(!old('active', $user->active))/>

If the condition resolved as a truthy result, checked would be added to the input field (making the radio button checked as a result). But, if it's a falsey result, nothing will be output.
Of course, this isn't exactly adding any new functionality, but I thought it could be some pretty nice syntactic sugar to neaten up our views.
If it's anything you'd consider merging, please let me know if any changes need making to it 😄

If this was accepted, would it also be sensible to add @selected for <select> elements?

@JayBizzle I had the same idea and was thinking of pitching that, but wanted to see how @checked would do first. That'll be next on my list to PR if Taylor's open to it :)

If this was accepted, would it also be sensible to add @selected for <select> elements?

An attempt to introduce this directive has been made some time ago, but it was rejected.

I've ported this over to Laravel 9 in case people were already defining this as a macro or something. Thanks! ❤

@taylorotwell Sweet! It hadn't actually crossed my mind about anyone who might already be defining it themselves. If it's not already been done, I'll try and get a PR over today to add the @checked and @selected to the docs 😄


wip: refactor: use TypedMpt in the backend

Blocked on #393

CI is being weird

did I just break CI?

Oh it's not the PR


Suggesting main() in incorrect contexts

Description:

Main method should not be suggested in these scenarios.
Steps to reproduce:
int a = 10;
<cur>

public function main() {

}

Affected Versions:
2201.2.0

As per the offline discussion, came to following conclusions.

Assign "Z" as a default sort text for completion items.
Deprioritize main() among functions (default sorting)
Fix sorting for module level for the scenario when we don't have anything typed in the module-level

The sorting order to be finalized:

Types,
Qualifiers,
functions/ variables
module completions

Regarding 3. Fix sorting for module level for the scenario when we don't have anything typed in the module-level

The nodeAtCursor is always identified as a non ModulePartNode except for the case where the source code is empty. The findNode() works to traverse the child node until the it finds a terminal node. When there is a module level declaration/ definition already in the source code, findNode ends up at one of the module level declaration/ definition and returns that particular matched node. So, we will get the nodeAtCursor as ModulePartNode only for the case where the source code is empty. Had an offline discussion with @rdulmina and came to a conclusion to handle these scenarios either inside getCompletions() or onPrevalidation() where we already handle for similar type of scenarios.

findNode API is designed to find the inner most non-terminal node encapsulating the given text range

BTW @rdulmina, for the following two scenarios, findNode() returns an ExternalTreeNodeList of declared module level delns and defns. Can that be handled from the parser side? cause we don't have a completion provider for the List node(and we cannot have either since lists can have different types of child nodes. So might need a fix for findNode() for these two cases).
enum testEnum {
    ONE = "1",
    TWO = "2"
}
// no completions

xmlns "www.wso2.com" as ns;
// no completions


Enable CI for Numba PyOMP

This PR enables running CI testing on both github and LLNL gitlab. LLNL gitlab is used mainly for GPU execution.

Fixes #1


pointer.lua#L40 should use math.huge instead of 1e6

https://github.com/bjornbytes/lovr-pointer/blob/master/pointer.lua#L40

Fixed


Website: Publish workflow will fail until new TypeDoc version released

(￣_￣|||)    I didn't consider that the publish workflow checks out the latest tag, not master, after cloning the TypeDoc repo. So the publish workflow is going to fail because it depends on my tweaks to the example's typedoc.json. I think we can just let it fail until the next time a release is published. Or I can put in a temporary fix. Thanks.
See https://github.com/srmagura/typedoc-site/runs/4060567189 for reference.

I'll just let it fail a bit longer, probably going to publish a release today :)

It works!


When using Wise and the Tagger file, cannot import UTF-8 strings

Elasticsearch version:   git master
Moloch version: 2.1.0
OS name and version: ubuntu 18.04
How was Moloch built/installed: (rpm, deb, easybutton, ...) easybutton
If the tagger file includes (say):
#field:bs.info;kind:termfield;friendly:bsinfo;db:bs.info;help:The IP Information;shortcut:i
<IP_ADDRESS>:i=女宇農系人女族本職味協動公。失浮枝真公室霊奪疑奮発販。
and then Wise tags <IP_ADDRESS> -- the string is not shown correctly. This is becuase the UTF8 flag is not set on the field.

do you think it should be on by default and a new flag to turn off instead?

I'm always nervous about making backwards-incompatible changes. I can't think of any use for the 8-bit mode -- it isn't 8-bit clean in that if you put in (say) 0xa8, you don't get that back.


Add sources as a configurable file

...instead of having each script hard-code the name of the source and/or other associated information, like the sitemap URL.
Also, I should use the word source instead of post. Not sure why that happened.

Closed by https://github.com/eigenfoo/cryptics/commit/63e56884eb4f180e30f211e0147b156dc668b0fc


Tree traversal.

More tree traversal methods are needed. Potentially:

parent - select parent node.
previous - select previous sibling.
next - select next sibling.
firstChild - select first child.
lastChild - select last child.
children - select all (immediate) children.

Some convenience filtering method might also be useful:

first - filter selection to the first node.
last - filter selection to the last node.
slice(start[, end]) - filter selection to the given subset by index.

Looks like it's undocumented that we can pass arbitrary function to select and selectAll.


Dimension mismatch when using SHAP to explain ResNet50

File "C:\Users\lenovo\AppData\Local\Programs\Python\Python38\lib\site-packages\torch\autograd_init_.py", line 202, in grad
return Variable._execution_engine.run_backward(
File "C:\Users\lenovo\AppData\Local\Programs\Python\Python38\lib\site-packages\shap\explainers_deep\deep_pytorch.py", line 226, in deeplift_grad
return op_handler[module_type](module, grad_input, grad_output)
File "C:\Users\lenovo\AppData\Local\Programs\Python\Python38\lib\site-packages\shap\explainers_deep\deep_pytorch.py", line 358, in nonlinear_1d
grad_output[0] * (delta_out / delta_in).repeat(dup0))
RuntimeError: The size of tensor a (512) must match the size of tensor b (2048) at non-singleton dimension 1

I'm getting this same error with ResNet152

Is this resolved yet. I am getting the same error.

I tried investing it and it seems this happens when a non-linearity is reused. I saw that the original resnet50 implementation of pytorch reuses the ReLU non-linearity over the layers which results in the input/output shapes (x/y)s to be replaced for each consecutive ReLU. Maybe the workaround could be to replace attributes x with a list of x's in case the same activation function is replaced in many places?


overwrite line classes in stepper stepConnector

The component Step should have a class for overwite the style of the line even without the need for adding the StepConnector component.

[ ] This is a v1.x issue (v0.x is no longer maintained).
[ ] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

Current Behavior

Steps to Reproduce (for bugs)

Context

Your Environment

Tech
Version

Material-UI
v1.?.?

React

browser

etc

@ninjasun I have added the waiting for users upvotes tag. I'm closing the issue as I'm not sure people are looking for such abstraction. So please upvote this issue if you are. We will prioritize our effort based on the number of upvotes.


Tópicos junho/2024

Local para adicionar os tópicos para o próximo bitdevs

Bitcoin no centro da política americana.
https://www.youtube.com/watch?v=tL9UvFKnFO0
28m10: "I'll also stop Joe Biden's crusade to crush crypto; we're going to stop it. I'll ensure that the future of crypto and the future of Bitcoin will be made in the USA, not driven overseas. I'll support the right to self-custody to the nations 50 million crypto holders. I'll keep Elizabeth Warren and her goons away from your Bitcoin. And I'll never allow the creation of a central bank digital currency.

Bitcoin vai consertar a dívida americana?
https://news.bitcoin.com/trump-inquired-if-bitcoin-could-aid-in-solving-the-35-trillion-us-national-debt-problem/
https://www.binance.com/en/square/post/8743243008866

Empty blocks por causa de falha proposital no hardware?
https://x.com/GrassFedBitcoin/status/1796311998466003418?utm_source=substack&utm_medium=email


forest-cli db clean shouldn't fail if there's nothing to clean

Issue summary
Running forest-cli db clean twice always fails (ie. forest returns error code 1) because the database folder cannot be deleted if it is missing. Forest-cli shouldn't fail in this case. We should either ignore it silently or print a message saying the database was already cleaned.
Other information and links

I'm not able to reproduce the issue. Any more detailed repro steps?
➜  forest git:(main) cargo run -p forest-cli -- --chain calibnet db clean --force
    Finished dev [unoptimized] target(s) in 0.37s
     Running `target/debug/forest-cli --chain calibnet db clean --force`
Aborted. Database path /home/me/.local/share/forest/calibnet is not a valid directory
➜  forest git:(main) cargo run -p forest-cli -- --chain calibnet db clean --force
    Finished dev [unoptimized] target(s) in 0.39s
     Running `target/debug/forest-cli --chain calibnet db clean --force`
Aborted. Database path /home/me/.local/share/forest/calibnet is not a valid directory
➜  forest git:(main) cargo run -p forest-cli -- --chain mainnet db clean --force
    Finished dev [unoptimized] target(s) in 0.37s
     Running `target/debug/forest-cli --chain mainnet db clean --force`
Aborted. Database path /home/me/.local/share/forest/mainnet is not a valid directory
➜  forest git:(main) cargo run -p forest-cli -- --chain mainnet db clean --force
    Finished dev [unoptimized] target(s) in 0.38s
     Running `target/debug/forest-cli --chain mainnet db clean --force`
Aborted. Database path /home/me/.local/share/forest/mainnet is not a valid directory
➜  forest git:(main)

Hmm, indeed. I could have sworn it exited with code 1 on my droplet. Guess I must have been confused.


integrate annotations in ALERTS metric

For using the (templated) annotations from the alert rules in external Tools like Grafana it would be nice if the annotations are exporter not only to the alertmanager but are also accessible in the ALERTS Metric.

This wouldn't work out, as annotations can vary from evaluation to evaluation so it'd cause cardinality issues. Annotations can only exist for long enough to send them to the alertmanager.

Ok, i understand that. Maybe it make sense to still think about it for using the annotations outside the alertmanager. So at the moment the annotations are only usable outside prometheus and i would think it should be possible to use all "output" that prometheus produces als use inside prometheus (could be an wrong sight).
So maybe the ALERS Metric could be split to some smaler parts (maybe alert Group, or if this makes sense to per Rule) and include then the annotations?

It doesn't make sense to have the annotations inside the tsdb at all, as they are event logging rather than metrics.

But labels do? :smile:
Whats the difference in this case? Don't get me wrong, but the annotations are something like the labels in this case.
So if this makes no sense, you can close this issue. I just thougt it might be an good idea...maybe i'm wrong :grin:

Labels are the identify of an alert, if they're varying from evaluation to evaluation you have a problem.


feat: Add TryFrom implementations for MetadataValue

Motivation
As described in the issue there are several adhoc methods that say "This function is intended to be replaced in the future by a TryFrom implementation once the trait is stabilized in std." Well, TryFrom is stable in std now, so let's use it :)
Solution
I looked at which TryFrom impls http::HeaderValue has, and copied those where it made sense. Seems like MetadataValue is mostly a copy of http::HeaderValue, so I thought it was a good guide.
I tried to avoid repeating code, so often various TryFrom implementations either call into each other, or into the underlying http::HeaderValue TryFrom implementations. I kept the #[inline] attribute when the original call had it, and added a deprecation warning to the original adhoc methods.
Apparently MetadataValue already implements From for all numeric types >= 16 bits. They just don't show up in rustdoc, which is surprising, but I didn't dive in to figure out why. So I only implemented TryFrom around different string and byte representations.

As requested, tagging @LucioFranco for a review.

Thanks!


Wildcard in route parameter regexp

Route '/:username([a-z][a-z-]*)'
Route '/:username([a-z][a-z-]*)/:project([a-z][a-z0-9-]*)'
URL /someone/project
Expectation is that the second route should match.
Actual result is the first route matches because the * is considered as all the things rather than "zero or more" [a-z-].

It's a limitation of the current version of path-to-regexp we use. A work-around would be to use the following route: /:username([a-z][a-z-]{0,}) (i.e. use {0,} in place of *).

I'm going to check if the most recent (non-backwards-compatible) version of path-to-regexp handles this better.

It does. So this should be fixed in 5.0, but as for 4.x, you'll probably have to just use the old syntax :/

Thanks for the quick feedback.

Thanks for the quick feedback.

No problem :) Especially for @bevacqua

So is path-to-regexp not going to be updated until version 5.0? That's something I would really like to see as soon as possible. Also the website is misleading because it points to path-to-regexp and its regexp tester but it is currently very out of date.

It's not that we don't want to upgrade path-to-regexp before 5.0, but all versions above where we are at have breaking changes and thus must wait until 5.0. We cannot upgrade path-to-regexp is a 4.x minor release if people's existing 4.x routes break.
As for website issues, please file them at https://github.com/strongloop/expressjs.com

For what it's worth, I've been using {0,} without any inconvenients for a long while now.

I want the upgrade to path-to-regexp for named parameters that can include slashes /assets/:asset+. Do you know of a good workaround for that?

Don't you need to use /assets/:asset(*) for that use case?

Perfect, thank you @bevacqua

So I looked really hard at this issue for Express 4.x, and it can actually be fixed in path-to-regexp 0.1.x series. I'll look into issuing a PR there, but even then, the current 0.1.5 is buggy, so unless the buggyness is reverted or fixed, even if said PR is accepted, we still wouldn't be able to upgrade until the "index issue" is addressed.

Looking through they related PR (https://github.com/pillarjs/path-to-regexp/issues/57), it looks like it would not be possible to fix this in 4.x in a back-compatible way. Is that correct? Or is it just a matter of fixing it in express rather than path-to-regexp?

Sorry, I never updated this issue. Yes, that is correct in that we can't get it fixed in Express 4.x. If you want to take a stab at it, please go ahead! A fresh look never hurts, because it feels like something that should be possible to fix.

So if I understand correctly, to fix the original issue we want to prevent translation of * within the () part of a token definition so that it will work as expected within the regexp (instread of taking the special meaning of applying to the token).
However, we can't do this because we found an example that documents /files/:file(*) as a valid usage where the * applies to the token, and we don't want to break anyone that reasonably expects documented and working behaviour not be broken by a minor or patch release.
Is that a correct summary?

Yes.

The only reasonable way to make a back-compatible fix that I can think of would be to add an option you could enable to make Express replace *s inside the () with {0,} before sending it to path-to-regexp.
You could push that option up into a patch on path-to-regexp version 0.x instead if that sits better.
I'm happy to have a stab at that change if it's something that we think is desirable. There is a bit of a philosophy question there -- how keen are we on adding options that will be removed next major version to fix bugs that may cause breakage?
Otherwise, perhaps we should label this issue with something like "wontfix", "limitation" or "low-priority" to indicate we can't fix it in 4.x?

The labels are accurate: it's a bug in 4.x, but wont be fixed until 5.0 due to limitations of the implementation we have in 4.x, for better or worse. We keep this issue open for two reasons:

To remind us it needs to be addressed until there is a 5.0 release on npm with this addressed.
Capture the conversation regarding an active bug for users to find when they have the same issue. They can also subscribe to this issue to know when it is fixed in a published version.

As for the potential solution above, any changes to building a regular expression need to land in our own dependency, otherwise we are not only defeating the purpose of owning our own dependencies, but we are cheating the community out of building complex applications, since they would have to copy and paste into their code instead of updating a dependency.
An option, to me, sounds crazy, because if the change would have to be behind a flag, then it sounds like it's not backwards compatible. The way the paths work is an intrinsic property of express, and so a flag to change this behavior at runtime means a community module can no longer know it's routes will just work on a major version of Express, rather they have to instruct users to change this flag or tough luck.

I wasn't thinking we would remove any labels or close the issue, I just wanted to add an extra label so it is easier to see the status/use in a query. Perhaps something like "fix-in-next-release" would capture it?
For the potential solution, yes, it was a bit of a stretch idea and certainly far from ideal and on reflection the simple workaround makes it unattractive.
I discounted other potential solutions (like special casing (*) or some subset of regexp-likes containing *) since I didn't find docs or tests that explained clearly how * should work inside (). So a reasonable user could form a conclusion about how it works (which would be backed up by the implementation) that would be broken by changing it at all by default.
It's a shame, because I think it is quite surprising behaviour.

Thanks for documenting this in the issue, that helps a lot
What is the best workaround: using {0,} or (*) ?
both work but which one is a smaller technical debt ?

Using {0,} should work the same with 5.x comes out while (*) will likely change meaning in 5, I believe.

I should just note that {0,} doesn't scale as well as (*)  on the input size to match.
e.g.
{0,}
time node -e "require('path-to-regexp')(process.argv[1]).exec('/foo/alskalskaslakslaksal21222/bar/xyzzy')" '/foo/:a{0,}/bar/:b{0,}/xyzzy'
node -e  '/foo/:a{0,}/bar/:b{0,}/xyzzy'  3.81s user 0.04s system 96% cpu 3.973 total

(*)
time node -e "require('path-to-regexp')(process.argv[1]).exec('/foo/alskalskaslakslaksal21222/bar/xyzzy')" '/foo/:a(*)/bar/:b(*)/xyzzy'
node -e  '/foo/:a(*)/bar/:b(*)/xyzzy'  0.04s user 0.01s system 98% cpu 0.051 total

This adds a security/performance vs maintainability tradeoff to the decision.

@joaosa I have deleted your comment. Please follow https://github.com/expressjs/express/blob/master/Security.md for security issues.

@dougwilson @bevacqua
I recently had to make a similar decision. It seems like {0,} yields a regex whose runtime is less scalable than (*).
e.g. using path-to-regexp 0.1.7
{0,}
time node -e "require('path-to-regexp')(process.argv[1]).exec('/foo/alskalskaslakslaksal21222/bar/xyzzy')" '/foo/:a{0,}/bar/:b{0,}/xyzzy'
node -e  '/foo/:a{0,}/bar/:b{0,}/xyzzy'  3.81s user 0.04s system 96% cpu 3.973 total

(*)
time node -e "require('path-to-regexp')(process.argv[1]).exec('/foo/alskalskaslakslaksal21222/bar/xyzzy')" '/foo/:a(*)/bar/:b(*)/xyzzy'
node -e  '/foo/:a(*)/bar/:b(*)/xyzzy'  0.04s user 0.01s system 98% cpu 0.051 total

This adds a security/performance vs code maintainability tradeoff to the decision :)

@joaosa im sorry i am banning uou from this tepo for now since you continue to post the security issue multiple time, ifnoring my ask to report it responsibly.

I spent hours debugging until I found this issue. I understand the reasoning behind leaving the bug in 4.x, but maybe it (and the {0,} workaround) could at least be documented on http://expressjs.com/en/4x/api.html#path-examples or some other appropriate place?

Hi @ttencate nothing wrong with documenting! At the bottom of every page on the site, there is a "Edit this page on GitHub." link; just click it and make the edit you think should be good and open a pull request : ) ! Alternatively, you can also file an issue on the website issue tracker.

Thanks, I somehow overlooked that link :) https://github.com/expressjs/expressjs.com/pull/809

So what's horrible here is not the "bug". Either syntax is fine. It's the fact that if you follow the documentation, it says to look at path-to-regexp and express-route-tester to for more information, but those are both at a much newer version that behaves differently.
The documentation should be updated to point at this version of express-route-tester which lets you select different versions and defaults to the one that express 4 is currently using.
For the next versions of express, (both 4 and 5) there should be an option to select the old or new style routing.

Why doesn't .* work?
From reading this thread, I understand that * matches everything rather than just zero or more of the preceding character, but shouldn't .* match a single character followed by everything else in the same way that [a-z][a-z-]* matches a [letter] followed by a [letter or a dash] followed by [everything else]?
Does this represent a separate bug from path-to-regexp for the .?
I used the following to test:
https://gist.github.com/VAggrippino/796114a27fe449fff7c45b278d9de74b

@rjmunro I really like the express route tester you linked to, but it doesn't help me understand this problem. In express routes, * and . don't work as they do in regular expressions. Why isn't this considered a bug, or at least a documentation error? ... but I suppose that's really a question for the path-to-regexp folks.
If this is the intended functionality, maybe the description of the path argument in the documentation should be changed? The route tester you linked to makes this more clear. It doesn't call the route a regular expression pattern as it does in the documentation. It says "will compile your route into the following regular expression".

@VAggrippino I read the page you linked to as saying you can either specify "A string representing a path" or "A path pattern" (which is presumably passed to path-to-regexp), or you can specify a "A regular expression pattern" which I interpret to mean a regular expression object, i.e. something like:
app.get(/foo/, func);

Which I have never tried, but I guess could work.

This issue still exist in express 5.x in spite not being exist in Path-to-RegExp

app.get('/:number(\\d*\\d*)', (request, response) => {
  response.send(request.params.number)
})

It donot work with one digit parameter (http://localhost/2) but works with more than one digit parameters (http://localhost/22)
Thanks

This is now resolved in 5.0.0-beta.1

您好，您所发的邮件我已收到！我会尽快给予回复！


Version: 0.98.1,why the msg parameter of enterbox method display Traditional Chinese

we use command "pip install easygui" on python2.7.15, please see below screenshot
`#-- coding:utf-8 --
'''
Created on 2018年8月15日
@author: xxoo
'''
import easygui as g
g.enterbox(msg = "请说出你的名字",title = "请说出你的名字")`

Hello @wsj0794 I'm afraid that I don't quite understand. What is the issue with the message parameter? Thanks!


Launch /tokens/* on Next.js

This removes most of the Gatsby code as well. We can't remove all of the Tokens related Gatsby code since Gatsby dynamically creates the tokens groups and sections in the left sidebar.

Turns out the failing build is a cache issue. I'll clear the deploy cache after merging.


AWS authorization is getting expired for the next request

AWS authorization seems getting expired for next request

ElasticDump version
3.3.7
Elasticsearch version
6.2
Node.js version (note that nodejs v8+ is required for this tool)
v8.11.1
Full command you are having issue with (with inputs and outputs)
elasticdump --input=https://xxxxxx.us-east-1.es.amazonaws.com --input-index=aaa_index --output=https://yyyy.us-east-1.es.amazonaws.com --output-index=aaa_index --awsAccessKeyId= --awsSecretAccessKey= --type=data

Seems the authorization is getting cached one time . For AWS does it need to be regenerated every time
Fri, 08 Jun 2018 06:21:34 GMT | starting dump
Fri, 08 Jun 2018 06:21:38 GMT | got 100 objects from source elasticsearch (offset: 0)
Fri, 08 Jun 2018 06:21:46 GMT | sent 100 objects to destination elasticsearch, wrote 100
Fri, 08 Jun 2018 06:21:47 GMT | Error Emitted => {"message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details."}
Fri, 08 Jun 2018 06:21:47 GMT | Total Writes: 100
Fri, 08 Jun 2018 06:21:47 GMT | dump ended with error (get phase) => Error: {"message":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details."}

Each time AWS is queried the header is signed. No caching is performed. Error above doesn't reflect expiration, seems the signature between client/host does not match. Try signing into aws first then using the profile mechanism to see if that works, then retry using the key+secret.


KOGITO-7421 kswf runtime tools quarkus dev ui docs

JIRA: https://issues.redhat.com/browse/KOGITO-7421
depends on : https://github.com/kiegroup/kogito-docs/pull/33 (rebase required)
Please make sure that your PR meets the following requirements:

[x] Pull Request title is properly formatted: KOGITO-XYZ Subject
[x] Pull Request title contains the target branch if not targeting main: [0.9.x] KOGITO-XYZ Subject
[x] The nav.adoc file has a link to this guide in the proper category

It's great content! Many thanks for your contribution.
I'm just not too convinced about the transition from the main guide to the children. But I don't have a better idea yet. I'll give some thoughts on it. sweat_smile

Agreed, Please do let me know if you have a better idea :smile:

@AjayJagan @ricardozanini Merging this PR.


add soundcloud support

should be able to get tracks from sound cloud

@jspear29 elaborate more.
look at this: https://developers.soundcloud.com/docs/api/guide#authentication
Search fetches both youtube and soundcloud or user has option to choose?
Results back have youtube/soundcloud tag or is that irrelevant.

At least with the youtube api there's an api key embedded... I think the desired state is having a settings menu which allows the user add their API key.  Thinking that soundcloud should work the same way.  But until we approach that feature I think its cool for now just to hardcode one in.
Not sure on the user experience for soundcloud vs. youtube.  Gut feeling is that its a unified search and the results have a youtube/soundcloud tag.


No ESLint configuration file for the project

When attempting to run npm run start, it fails with

ESLint couldn't find a configuration file. To set up a configuration file for this project, please run:
eslint --init

It seems like a configuration file needs to be added, I'm guessing everyone who maintains this happens to have one in their home folder and it is falling back to that.

Thank you for this! Actually I'm refactoring the entire project to get rid of oclif and lift the entire project on new feet's to ensure further enhancements. I guess the new version will be available next year.


Remove require functionality with dynamic application functions

Feature Request
Is your feature request related to a problem? Please describe.
I would like to propose to remove the require functionality in https://github.com/probot/probot/blob/master/src/helpers/resolve-app-function.ts#L10.
This functionality breaks bundling tools. Bundling tools (such as webpack) make NodeJS apps much smaller, better contained (a single file without node_modules, and allow tree-shaking the final Javascript program.
Currently, webpack gives the following warning when compiling a probot app:
 [ snip ]

WARNING in ../../node_modules/probot/lib/apps/default.js 11:18-77
Critical dependency: the request of a dependency is an expression
 @ ../../node_modules/probot/lib/index.js 31:23-48
 @ ./index.ts 4:17-34

WARNING in ../../node_modules/probot/lib/helpers/resolve-app-function.js 11:11-50
Critical dependency: the request of a dependency is an expression
 @ ../../node_modules/probot/lib/index.js 21:31-72
 @ ./index.ts 4:17-34

WARNING in ../../node_modules/probot/lib/manifest-creation.js 16:18-77
Critical dependency: the request of a dependency is an expression
 @ ../../node_modules/probot/lib/apps/setup.js 10:28-59
 @ ../../node_modules/probot/lib/index.js 14:16-39
 @ ./index.ts 4:17-34

 [ snip ]

As you can see there are more problems (manifest creation and default app). Those problems are a big issue, because there is a graceful failure when the require() of the package.json file fails.
Describe the solution you'd like

Deprecate defining a string as an application function
In time, remove the functionality
Users can replace their required app function by requiring themselves, and calling createProbotApp on the result.

Describe alternatives you've considered

Do not remove this feature, and ignore the bundler warning when bundling a probot app.
Document these warnings and the limitations of using probot with a bundler.

Teachability, Documentation, Adoption, Migration Strategy

Adoption strategy: First deprecation, then removal.
Documentation: I am not aware that there is any documentation except the types that refer to a string main function.

If such a feature request is against the wishes for this project, feel free to close this issue :).

I would like to propose to remove the require functionality in https://github.com/probot/probot/blob/master/src/helpers/resolve-app-function.ts#L10.

It's removed from usage within the Probot class in v11, see the pull request here: https://github.com/probot/probot/pull/1438. We still use it when you run the probot binary, but that shouldn't affect bundling.
Could you give it a try with npm install probot@beta? Make sure to update to the latest probot v10 version first and address all deprecation notices

@gr2m Thanks you for the quick response. I did not notice that pull request for the next probot version. I will gladly try it out tomorrow!

OK we still need to solve some deprecations. I will close this issue and make use of the beta (or released) v11 version to solve the bundling issue. Thank you!


Deleting a bunch of files freezes vscode

Not sure if that's the intended behavior or not.

Select 100-200 files 70Kb+ in file explorer
Delete them (Confirmation dialog disabled)
Interface is frozen for about 5s

Not a permanent deletion (recycle bin enabled).

OS version: Windows_NT x64 10.0.16299

On my mac I have deleted 100 files of 100kb in size and it took less than a second
On my windows this took around 2 seconds using vscode. Doing the same operation from the windows explorer also takes 2 seconds and the explorer is blocked.
In a perfect scenario we would do this in the background and vscode would not freeze.
However not sure if we can do something about this since I call the fileService api asyncly from the explorer
fyi @bpasero

Unfortunately if the trash is used, that operation blocks the UI thread and is not async. So VSCode will freeze as long as Windows is busy moving the files to the trash.

@bpasero Is this a duplicate of #43508 then?

Yeah sounds like it, let's close as dup. Thanks!


pipx: support features

pipx has a concept of optional features upon package installation, via pipx install package[feature,…].  This is used, for example, by Harlequin.
To my knowledge, mise has no support for this.  Would it be possible to add it?
As a work-around, for the example of Harlequin, one can install things via pip install harlequin parlequin-postgress etc. instead.

It would be nice to support the --preinstall option also, which allows you to inject additional packages to the environment that aren't explicitly covered by a declared extra. Note: this option can be specified multiple times, also.
This is equivalent to running pipx inject some-tool some-package on an existing tool, but nicer since it does it at install-time.


WIP: Update runc to v1.2.1 and crun to v1.18.2

What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Update the runtimes to their latest releases.
Which issue(s) this PR fixes:

None
Does this PR have test?
None

Special notes for your reviewer:
Does this PR introduce a user-facing change?

None

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 41.30%. Comparing base (11d77f4) to head (9605eca).
Report is 461 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2535      +/-   ##
==========================================
- Coverage   45.50%   41.30%   -4.20%
==========================================
  Files          79      109      +30
  Lines        7782    18220   +10438
==========================================
+ Hits         3541     7526    +3985
- Misses       4099    10198    +6099
- Partials      142      496     +354


[Request] Persona 5 Royal, Game Pass version

Xbox or PC Game Pass version of Persona 5 Royal:
https://www.xbox.com/games/persona-5-royal

Never mind, it works with the Game Pass version as well.


Replace icon with descriptions

The icons on the page may seem nice, but filtering or searching based on them is impossible unless you go directly to the markdown.
![Open-Source Software][OSS Icon] means **open source**, click to enter **open source** repo;
![Freeware][Freeware Icon] means **free** to use, or **free** personal license;
![hot][hot Icon] means **hot** app;
![tuijian][tuijian Icon] means **recommended** app;
![must-have][bibei Icon] means **must have** app;
![App Store][app-store Icon] means **App store** hyperlink;
![1 star][red Icon] means highly recommended must have app, the number of stars represents how strong I recommend;

I propose we either change these, or add the actual text of what they mean into the line. This would allow to search based on a keyword as if it where a label.

This proposal is good, but there is workload. You can RP.
thx!

I can work on a PR for this. Thinking of a script to be able to update it before it's merged.
The only thing I would like to brainstorm here is format. Not sure if something in the form of:

Atom - A hackable text editor for the 21st Century by GitHub. Atom Plugins. — * * * * — Open-Source Software — Freeware — hot — recommended — must-have —

Or,

Atom - A hackable text editor for the 21st Century by GitHub. Atom Plugins.
— * * * * — Open-Source Software — Freeware — hot — recommended — must-have —

Ideas or recommendation?

@radarhere English list can do so, but the Chinese list I do not want to do that.
Chinese list I have tried, Not beautiful.
I would like to vote.

@jaywcjlove I'm guessing you meant @rubenvarela

What about adding an ALT text to the icons? Hover over the icon to get a tooltip of what it means.
 Lorem ipsum
 Lorem ipsum
 Lorem ipsum
 Lorem ipsum
 Lorem ipsum
 Lorem ipsum
 Lorem ipsum
 Lorem ipsum
 Lorem ipsum
 Lorem ipsum
 Lorem ipsum
 Lorem ipsum
 Lorem ipsum

Could be done. Not too hard at all. It's just adding the title to the bottom images in the README.md
But, at least my issue, was more in regards to the actual finding them via Ctrl/Cmd+F. They're small icons, I can't easily read them, I'm not visually familiar with them.
So I was looking to search/highlight them to visually identify them.

I am ready to develop an APP to solve, how?

@jaywcjlove I can script the process for the English version.
For your app, would you have a preference on one of the formats above? First one is on the same line. The second one is just the next line down.

@rubenvarela I would like to use the Chinese and English form of the switch.

My plan was match based on the markdown images.
I don't see why it wouldn't work on the Chinese version as well, but previously there was a concern. I can go ahead and work on a preliminary version and upload it.

You can creat a branch,  push to the repository. Work together to solve the problem.
@rubenvarela

@rubenvarela #237


Incorrect hoo-dlg sidebar height on mobile devices

Describe the bug
The hight of sidebar dialogs is too high in the case of browsers where the chrome overlays the viewport. This is very common on touch devices.
To Reproduce
Steps to reproduce the behavior:

Create a .hoo-dlg.sidebar.right
Fill it up with content
The last content will be covered by the browser chrome at the bottom

Expected behavior
Sidebar dialogs should have the same height as the visible viewport.
Smartphone (Android)

Device: Samsung Galaxy S20
OS: Android 13
Browser: Samsung Internet
Version: 25

Smartphone (Apple)

Device: iPhone 15
OS: iOS 17
Browser: Safari

Additional context
One recommendation is to use height: 100% together with position: fixed, rather than height: 100vh. See Chrome for Developers.
My workaround:
.hoo-dlg.sidebar {
    position: fixed;
    height: 100%;
}

100% most of the case is not reliant. I only had support in the dialogs for vw, vh.
I added now the more common and better useable viewport height and widht using svw and svh.
Which will give you the smalles view port that matches the quasi "real browser" window.

🛳 Shipped in 2.5.0 - https://lab.n8d.studio/htwoo/changelog/htwoo-core-cl/

In my scenario the sidebars are sometimes stacked on top of eachother and/or are scrollable. I find that postion: fixed; height: 100%; works better in my case.
1: Without postion: fixed, the scrollbar will push the content to towards the center of the viewport, on Windows for example. Different browsers have the scrollbars either overlapping or to the side.
2: Without postion: fixed; height: 100%;, overlaying sidebar may get less height than the one below when stacking them.


Python and the Holy Grail of Causal Inference - Dennis Ramondt, Huib Keemink

https://www.youtube.com/watch?v=HPC42U9xtQY
0:00 Introduction
0:36 What is Causal Inference
1:18 "Slogan" for the Talk
1:35 Typical Randomized Testing
2:15 Use Case 1: Heat Pump Savings
2:45 Measurement Data: Daily Gas Usage ~ Outside Temp
3:32 Experiment Setup: Heat Pump Savings
5:40 Fixing Group Imbalance
6:50 Propensity Score Matching
7:47 Recap of Heat Pump Use Case (Correcting Assumptions and Limitations)
9:07 Use Case 2: Effect of Cooler Placement
9:40 Experiment Setup: Cooler Placement
11:47 Problem 1: Test and Control Groups are Statistically Different
13:17 Code Example: Single Covariate Simulated Example
14:01 Treatment Effect Correction
16:14 Code Example: Treatment Effect Correction
16:28 Assumptions: Conditional Mean Independence & Conditional Independence
18:44 Tree Ensemble: Virtual Twins
20:21 Results: Cooler Placement
22:18 Talk Recap
24:50 Q&A 1
26:38 Q&A 2
27:32 Q&A 3
29:00 Q&A 4
30:29 Q&A 5

Thanks so much!


Long line goes out of screen

When I enter a long linux path to the markdown file, the line displayed in marp goes beyond the screen, how to solve the problem? The problem can be seen here
This is my configurations in the head of the markdown file:
marp: true
theme: uncover
paginate: true
_paginate: false

Thank you so much!

You can tweak style to set word-break css property as break-word or break-all. Marp default theme hasword-break: break-word; definition but it seems not to be defined in others.
Try to add <style> tag like this:
---
marp: true
theme: uncover
---

<style>
section {
  word-wrap: break-word;
}
</style>

/xxxx/xxxx/xxxx/xxxx/xxxx/xxxx/xxxx/xxxx/xxxx/xxxx/xxxx/xxxx/xxxx/xxxx/xxxx/xxxx/xxxx/xxxx/xxxx/xxxx

It worked! Thank you so much! @yhatt

@taianguo My pleasure. You may contribute for adding CSS declaration to our built-in themes if you have interested. https://github.com/marp-team/marp-core/issues/108


Server behind Cloudflare proxy gives SSL handshake failed

I just upgraded a server to Kamal 2.0. I reimaged the VPS and the below is my config:
# Name of your application. Used to uniquely configure containers.
service: robertritz

# Name of the container image.
image: robertritz/robertritz-website

# Deploy to these servers.
servers:
  - ip goes here

registry:
  username: robertritz
  password:
    - KAMAL_REGISTRY_PASSWORD

builder:
  arch: amd64

proxy:
  app_port: 3000
  host: robertritz.com
  ssl: true

Everything is deployed correctly and when I set Cloudflare to DNS only (bypassing their proxy) everything works great. When I add Cloudflare proxy I get an SSL Handshake Failed error.

Ah I figured out the issue. I needed to set forward-headers to true. It's working now! Here my the config file for posterity.
# Name of your application. Used to uniquely configure containers.
service: robertritz

# Name of the container image.
image: robertritz/robertritz-website

# Deploy to these servers.
servers:
  - ip address goes here

registry:
  username: robertritz
  password:
    - KAMAL_REGISTRY_PASSWORD

builder:
  arch: amd64

proxy:
  app_port: 3000
  host: robertritz.com
  ssl: true
  forward_headers: true


ROCm 4.3+docker - using a different driver version?

Hi @ROCmSupport ,
I would like to use ROCm 4.3 with docker, but using a different driver that's usually provided for bare-metal (non-docker) machines, e.g., the 21.20 driver https://www.amd.com/en/support/kb/release-notes/rn-amdgpu-unified-linux-21-20
I tried installing it myself on a docker container, but clinfo doesn't seem to detect the instances, and there's also the issue of update-initramfs command not found, which seems to be used by the driver installer there. Is there any way I can use the 21.20 driver within a docker container setup with ROCm ?

Hi @jammm
Thanks for reaching out.
As per the definition of docker, all user space/mode components can be kept in a docker container, because docker container also runs on kernel. So we can not install/use kernel components/packages inside docker container, which is not possible.
So recommend to use stock kernel + install any kernel driver like amdgpu-pro or rocm kernel (rock-dkms and rock-dkms-firmware) on top of it and then run the docker container.
hope this helps.
Thank you.

Alternatively, you could run ROCm in a KVM virtual machine instead of in docker, and passthrough the AMD GPU to the KVM instance with vfio-pci. This is fairly involved though, and on top of what is usually required e.g. for passing through an nvidia gpu to CUDA, it also requires code changes and some monkeying with setpci after booting the virtual machine, described here: https://github.com/RadeonOpenCompute/ROCK-Kernel-Driver/issues/100. If you can, installing the desired driver on host and using it from docker is much simpler.

Thanks @ROCmSupport !
So if I understood correctly, I can install say, driver version 21.20 on the host machine, and then run a docker container with rocm 4.3 on it?

Yes, you can. But I have not tried like 21.20 on host + 4.3 docker container so far. Most likely it works, you can give a try.
Instead I tried 4.3 on host + 4.3 docker container.

Hi @jammm
Feel free to close this ticket, if you feel that you have gotten the desired solution.
Thank you.

Thanks!

Thanks!


Crash of production bundle with custom preset

Environment
Nitro 2.9.4 (and probably earlier) on Node 18 (and probably others)
Reproduction
https://stackblitz.com/edit/unjs-nitro-starter-rok6dt?file=package.json
Describe the bug
Problem
When adding a rule with cache in routeRules and adding a custom preset, the resulting production bundle crashes with a ReferenceError.
What's happening?
There are various circular dependencies between modules in Nitro core.
For some reason, the warnings, that Rollup spits out about them, have been suppressed in e5f9900bc73456ddcb8a4c25649ed2d4f797c099 a long time ago...
Specifically, one of these circular dependencies is between app.ts and cache.ts.
Because of this, the order, in which they are assembled by Rollup in the output bundle, is not well-defined, and may change...
However, the resulting bundle only works reliably, if cache is included before app, because of a reference to cachedEventHandler from within createNitroApp.
This reference is only hit, if a cache route rule is defined for some handler, but I think that's a common occurrence (see additional context).
Reproducibility
Now, a plain Nitro 2.9.4 project with a cache route rule always seems to build a working bundle (with cache before app) for me. As soon as I include a custom preset though - the repro just has the example from the docs - it stops working.
If I'm right about the module order not being well-defined, this may be very fragile, though. I don't know much about the internals of Rollup and how it orders modules within its chunks.
Additional context
This has originally surfaced in a larger project with a more complex custom preset when upgrading from Nuxt 3.7 to Nuxt 3.11 with Nitro being updated from 2.8.0 to 2.9.4.
Because of the nature of the problem (see above), this does not mean that Nitro 2.8.0 didn't already have the problematic circular reference. It probably just worked by chance...
That project uses @nuxtjs/sitemap, which specifies cache via routeRules internally for its own routes ➡ I guess this is a common setting.
Logs
No response

Hi. You can fix it by importing useNitroApp explicitly from #imports in entry:
import { useNitroApp } from '#imports';

PS: I would not recommend custom preset usage in anyway. If you are facing any limitation with built-in presets, please raise an issue for them and best luck.

Hi. You can fix it by importing app directly:  (make sure to use >=2.9.5)
import { nitroApp } from 'nitropack/runtime/app';

PS: I would not recommend custom preset usage in anyway and above usage might get broken. If you are facing any limitation with built-in presets, please raise an issue for them and best luck.

How do you ensure the order of modules in the bundle, though? Doesn't this seem a bit fragile to you, too?

Yes that's why we never exposed entry usage yet for stable custom presets.


Mockup UI for DKG/Eggnet Statistics Page

feat: add the dkg/eggnet statistics tab
feat: add statistics overview section
feat: add dkg signers table
feat: add chart section
chore: add label color for statistic card
feat: add progress bar for uptime value
chore: update width of child tab on sidebar and add border for header button on dark mode

PR Checklist
Please check if your PR fulfills the following requirements:

[x] Tests for the changes have been added (for bug fixes/features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[x] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

What is the current behavior?
We don't have the statistic tab on the sidebar and no existing statistics for DKG/Eggnet.
Issue Number: Closes https://github.com/webb-tools/webb-dapp/issues/434
What is the new behavior?
https://user-images.githubusercontent.com/60747384/175298145-00f9a843-71fa-4b8e-8ba3-be7e084c85f1.mp4
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information
Data on the page is seeding randomly. Need to implement the API query to get real data.

New UI update
https://user-images.githubusercontent.com/60747384/175349606-bf597036-e571-4d5a-bfe1-2f354d4e6a03.mp4


awesimsoss outputs only one integration, one group in multi-integration simulations in v.0.3.3

Hey @hover2pi,
This is tangentially related to #80. The same code that was set there, but for nresets=0, fails on creating a multi-integration exposure. In other words, the following code:
import numpy as np

import astropy.units as q

from awesimsoss import ModelTSO
import batman

rprs = 0.02037
wavelength, transit_depth = np.linspace(0.4,3.5,1000), (rprs**2)*np.ones(1000)

# First, define effective temperature, log(g), [Fe/H] and
# 2MASS J-magnitude of the host star (the latter obtained from Simbad):
teff, logg, feh, jmag = 4599, 4.62, -0.06, 9.086

# Now define orbital properties of K2-141b, the exoplanet. First, orbital period and time-of-transit center:
P, mid_transit_time = 0.2803244, 57743.5716 + 2400000.5
# Scaled semi-major axis and planet radius (in units of stellar radius), inclination, eccentricity and
# argument of periastron passage:
a, rp, inc, ecc, omega = 2.264, rprs, 86.3, 0., 90.

nintegrations, ngroups, start_time = 308, 3, '2022-12-6T23:14:44.87'

tsoframes = ModelTSO(ngrps=ngroups, nints=nintegrations, nresets = 0, teff = teff, logg = logg,
                     feh = feh, jmag = jmag, stellar_model = 'ATLAS', obs_date = start_time,
                     target = 'K2-141', run = False)

params = batman.TransitParams()
params.t0 = mid_transit_time # time of inferior conjunction
params.per = P # orbital period (days)
params.a = a # semi-major axis (in units of stellar radii)
params.rp = rp # radius ratio for Jupiter orbiting the Sun
params.inc = inc # orbital inclination (in degrees)
params.ecc = ecc # eccentricity
params.w = omega # longitude of periastron (in degrees) p
params.limb_dark = 'quadratic' # limb darkening profile to use
params.u = [0.1,0.1] # limb darkening coefficients; just initializations for now
supersample_factor = 10

tmodel = batman.TransitModel(params, tsoframes.time.jd,
                             supersample_factor = supersample_factor,
                             exp_time = tsoframes.frame_time*(1./(3600.*24.)))

# Stellar parameters --- will be useful to generate limb-darkening coefficients internally in
# awesimsoss:
tmodel.teff = teff
tmodel.logg = logg
tmodel.feh = feh
# Define ATLAS9 as the model grid:
tsoframes.model_grid = 'ATLAS9'

transit_spectrum = [wavelength*q.um, transit_depth]
tsoframes.simulate(planet=transit_spectrum, tmodel=tmodel, params = params, supersample_factor = supersample_factor)
tsoframes.export('data_k2-141_uncal.fits')

Runs and creates a file, but the output exposure only has one integration, and one group (i.e., dimension is (1,1,256,2048)). Even more, that group is just a file with ones in it. Also, for some reason even though nresets was set to zero, the header defines it to 1.
Néstor

Should be fixed in #82

Indeed, fixed! Thanks @hover2pi!


[rv_timer DV] Reduce rv_timer smoke test runtime

rv_timer_smoke is the longest running test in the private CI,
consuming a whopping 6 minutes of runtime.
In this change, the existing smoke vseq is renamed to random vseq and a
smoke_test switch is added to it. If set, it significantly reduces the
scope and runtime of the CI test so that we can continue to stay within
the 20 minute timeout.
The original rv_timer_smoke test entry is duplicated to
rv_timer_random, with both running the same random vseq. For the smoke
test version, the above plusarg is set to 1 and it is also reseeded only
once, since there is no need to run it multiple times.
This brings the rv_timer_smoke test runtime down from 6 minutes to 52
seconds, which will enable us to add more DUTs to the regression list
without blowing the 20 minute timeout.
Signed-off-by: Srikrishna Iyer<EMAIL_ADDRESS>

The overall private CI runtime went down from ~16 minutes to ~13 minutes, a 19% improvement!

The overall private CI runtime went down from ~16 minutes to ~13 minutes, a 19% improvement!


seed data population in database tables.

Fixes #115
With this we would want to populate seed data in our above mentioned tables during facilitator init.
For populating data in gateway table we would need to go to chain for fetching bounty/activated for Gateway & bounty for CoGateway contract.
Before we run our integration tests, this would need

dev chains for origin & auxiliary to be setup.
contracts to be deployed on them
mosaic config to be populated with these addresses

As we currently do not have this setup scripts, we can not integrate the code to populate seed data in
facilitator init.
With this PR I am proposing an implementation for the population logic and its unit test cases. Once we have the about code available we can plug this code in facilitator init.

Started reviewing 🥗


'SyntaxError: Decorators cannot be used to decorate parameters.' - Angular tests could be updated with correct combination of importOrderParserPlugins

Discussed in https://github.com/trivago/prettier-plugin-sort-imports/discussions/122
the Angular unit test fails due to an error SyntaxError: Decorators cannot be used to decorate parameters. if the example includes parameters with decorators.
the unit test could be updated and an FAQ added if different plugins are required to support this.

I don't know what's the "correct" way to fix this issue. It is working for me with
"importOrderParserPlugins": ["typescript", "decorators-legacy"]

Just in case if somebody else stumbles over this bug.

I don't know what's the "correct" way to fix this issue. It is working for me with
"importOrderParserPlugins": ["typescript", "decorators-legacy"]

Just in case if somebody else stumbles over this bug.

Where did you define that?

Where did you define that?

In .prettierrc

I'm still seeing this error, even with
  importOrderParserPlugins: [
    'typescript',
    'classProperties',
    ['decorators', { version: 'legacy' }],
  ]

Any advice?

Could you try a prettier config below? It's worked for me with the same issue.
{
  ...
  "plugins": ["@trivago/prettier-plugin-sort-imports"],
  "importOrder": [
    "<THIRD_PARTY_MODULES>",
    "^rxjs(.*)$",
    "^lodash(.*)$",
    "^[./]"
  ],
  "importOrderSeparation": true,
  "importOrderSortSpecifiers": true,
  "importOrderParserPlugins": ["typescript", "classProperties", "decorators-legacy"]
}

I had the decorators in importOrderParserPlugins option, but it didn't work. I had to replace it with decorators-legacy


[FLINK-2094] [ml] implements Word2Vec for FlinkML

This pr implements Word2Vec for FlinkML - addressing Jira Issue Flink-2094
Word2Vec is a word embedding algorithm that generates vectors
to reflect the contextual and semantic values of words in a text.
find out more detail about word2vec here:
https://arxiv.org/pdf/1411.2738v4.pdf
This implementation uses an abstracted embedding algorithm
which I've called a ContextEmbedder - based on the original Word2Vec algorithms -
to allow users to extend embedding to reflect problems outside of words.
Word2Vec is an implementation of the ContextEmbedder

Thank you for your contribution Kalman!
I just took a brief look, this is a big PR so will probably take some time to review.
For now a few things that jump to mind:

We'll need to add docs for the algorithm, which should be example heavy. Here's a simple example for another pre-processing algorithm. I see you already have extensive ScalaDoc's we could prolly replicate those in the docs.
 Ideally in a distributed setting where the input files are on HDFS. This way we test the scalability of the implementation, and problems usually arise.
Have you compared the output with a reference implementation? My knowledge of word2vec is not very deep but as far as I understand the output is non-deterministic, so we would need some sort of proxy to evaluate the integrated correctness of the implementation.
Finally I see this introduces a new nlp package. I'm not sure how to treat this (and relevant algorithms, say TF-IDF), as they are not necessarily NLP specific, even though they stem from the field you could treat any sequence of objects as a "sentence" and embed them. I would favor including them as pre-processing steps and hence inheriting from the Transformer interface, perhaps by having a feature pre-processing package.

Regards,
Theodore

Hey Theodore,
Thanks for taking a look at my PR!

I'll add docs shortly, per the examples you posted.
I've tested against datasets in the hundreds-of-megabytes size (using the preprocessed wikipedia articles available here) in a distributed, HDFS supported environment. The implementation worked well as the scale of the data increased - although I was experiencing some frustrating memory issues as I increased the number of iterations performed.
I can show that the vectors generated show good results along the lines of the original paper - that they show semantic similarity in line with cosine similarity and that difference vectors can be used to create 'analogy' relationships that make sense. But you're right that it's non-deterministic and surveying how it's tested in other libraries is inconclusive. I've included some toy datasets in the integration tests that show good results and exercise these qualities.
I know what you mean about the new package. I included it because the feature requests was specifically for Word2Vec. But - similar to your suggestion - the class in the nlp package is really just a wrapper around a generic embedding algorithm that can perform on any data that is word-in-sentence-like. The ContextEmbedder class, in the optimization package, is where the actual embedding is occurring.
That said, optimization might not be the right home either (although we are optimizing toward some minima)

Best,
Kalman

@kateri1 - I agree that seeking a solution with Flink's data structures is valuable.
I also think that Flink-ML is in a unique position to implement streaming-first, iterative implementations of this algorithm. They are fairly novel on the web, but in theory have been implemented in Gensim's word2vec.
Having an initial, offline implementation of word2vec in flink could be considered as a foundation for an online word2vec that Flink would be in a unique position to implement and be of great use to the community looking for a scaling solution to this class of problem

Closing since flink-ml is effectively frozen.


Enable importing takeouts from polar

Unfortunately this needs to go up in priority as fixing polar import seems hard with the new login mechanism.


Copilot Chat confabulation: `"github.copilot.editor.enableTypeAnnotations": true

This is to report Copilot Chat's confabulation as to its own settings. All information is below.
Chat transcript

bartoncreek: /vscode is it possible to set some default instructions for copilot that specify codpilot's generated python code include type annotations whenever possible

GitHub Copilot: Yes, it is possible to set default instructions for Copilot to include type annotations whenever possible. You can enable this feature by setting the following setting in your VS Code settings.json file:

{
    "github.copilot.editor.enableTypeAnnotations": true
}

This will instruct Copilot to generate Python code with type annotations whenever possible.

bartoncreek: Can you doublecheck the accuracy of this setting. Does it really exist?

GitHub Copilot: I apologize for the confusion. The setting I mentioned earlier,
"github.copilot.editor.enableTypeAnnotations", does not actually exist. I made a mistake in my previous response. However, Copilot does generate type annotations in Python code when it is able to infer the types. So, while there is no setting to enable this behavior, Copilot will automatically include type annotations when it can.

My System and Versions

Copilot Chat ext version: v0.7.2023080
Copilot extension version: v1.101.317
VS Code Version: 1.81.0
Date: 2023-08-02T12:36:11.334Z
Electron: 22.3.18
ElectronBuildId: 22689846
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 6.4.4-arch1-1

Steps to Reproduce:

Well, given the well-known stochastic nature of LLM confabulations, this is just a "ONE-SHOT" report for the experts to suss out.

Chat Screenshot

I was able to replicate this report in a slightly different way using the /vscode shortcut:


Migrate back to Ubuntu 14

Once the gcloud beta is supported there with installation and auth.

Done.  curl works fine.  I wonder if this will be an issue if we go to gcloud.


[For help] Failed to process the incoming request: unsupported protocol version

2021/11/09 12:01:55 [ERROR] Failed to process the incoming request: unsupported protocol version: 69 => server.go:261
2021/11/09 12:01:55 [ERROR] Failed to process the incoming request: unsupported protocol version: 84 => server.go:261
2021/11/09 12:01:55 [ERROR] Failed to process the incoming request: unsupported protocol version: 49 => server.go:261
2021/11/09 12:01:55 [ERROR] Failed to process the incoming request: unsupported protocol version: 116 => server.go:261
2021/11/09 12:01:55 [ERROR] Failed to process the incoming request: unsupported protocol version: 101 => server.go:261
2021/11/09 12:01:55 [ERROR] Failed to process the incoming request: unsupported protocol version: 105 => server.go:261
2021/11/09 12:01:55 [ERROR] Failed to process the incoming request: unsupported protocol version: 115 => server.go:261

Hi,
Sometime it's happen in my standalone deployment env,  could you give me an idea about the above error output, what's  the reason that cause protocol read version incorrect?

Hi @ShawnHsiung
I have never seen that error before. Which version do you use? The current production version is v0.4.0. Maybe you use a different version on the client-side? Do you have any procedure to reproduce that error?

Hi @ShawnHsiung
I have never seen that error before. Which version do you use? The current production version is v0.4.0. Maybe you use a different version on the client-side? Do you have any procedure to reproduce that error?

Hi  @buraksezer
thanks for your reply. the output log incorrect protocol version was caused by our service scanner to do some security things. But, I have an question about why not to close the conn actively when handle message failed,  and may we output more detail log while client using unknown protocol version, it's useful to  position error.
for {
    // handleMessage waits to read a message from the TCP socket.
    // Then calls its handler to generate a response.
    err := s.handleMessage(conn, &connStatus, done)
    if err != nil {
	  // The socket probably would have been closed by the client.
	  if errors.Is(errors.Cause(err), io.EOF) || errors.Is(errors.Cause(err), protocol.ErrConnClosed) {
		  s.log.V(6).Printf("[DEBUG] End of the TCP connection: %v", err)
		  break
	  }
	  s.log.V(5).Printf("[ERROR] Failed to process the incoming request: %v", err)
    }
}

But, I have an question about why not to close the conn actively when handle message failed,

Olric implements connection pooling. Closing the socket due to a message processing error is not useful at all. Because the underlying TCP socket would be healthy.

and may we output more detail log while client using unknown protocol version, it's useful to position error.

It's possible to improve the logging. Could you please send a PR or snipped to clarify the idea?

But, I have an question about why not to close the conn actively when handle message failed,

Olric implements connection pooling. Closing the socket due to a message processing error is not useful at all. Because the underlying TCP socket would be healthy.

It's might be better to distinguish protocol error  from errors while handleMessage,  close the connection if the protocol.ReadMessage returns error, because it would be a bad client with high probability, and there is a problem that olric not read until the EOF from conn that keep sending data.

and may we output more detail log while client using unknown protocol version, it's useful to position error.

It's possible to improve the logging. Could you please send a PR or snipped to clarify the idea?

yes, I'd like to make a PR to improve the logging readability.  let's talk about the first question, is it possible to close conn if  protocol read error?  if it's possible, I 'd like to include it in the PR.

I am closing this issue due to a lack of activity.


Remove new relic setup from wsgi file.

@akatsoulas r?

Coverage remained the same at 92.556% when pulling bee484445378e052c27506680a98645afa19d477 on johngian:wsgi-issue into 2fe3be9a3fbbcbf9ba498ad86c959dc4d5443153 on mozilla:master.


Transport auto not working on 'option' mode

Issue description:
If your config is set to option mode, the transport auto feature is not working. Tried it using the color field.
Version used:
2.3.0
Using theme_mods or options?
option. It works on theme_mod mode.

I think the problem is when your postmessage.js trying to create the style tag.
When on option mode. Your localized jsvars's keys has format like this: option_name[option_key]. This caused issue when your script trying to create the style tag:
jQuery( '#kirki-customizer-postmessage' + setting )

jQuery would accept the selector as #kirki-customizer-postmessageoption_name[option_key]. And you would never found that element.
Can you simply replace the brackets ([ ]) with dash (-). OR you change how you localize the settings into jsvars. Perhaps by striping the option_name and only use the option_key.

:+1: fixed.


With my Mnemonic is oppened other wallet

I have written my Mnemonic and it has not been oppened my wallet, but other without founds. Please I need help to solve this

how did you get the first wallet? is there any evidence that the first one was associated with the mnemonic?
report seems the same as #491

I got the first wallet as ussual I think from oasis protocol. I can see the first wallet by the link and I see the funds, but when I want to oppen the wallet in order to make transactions, I writte the Mnemonic and another wallet is oppened with different adress and without funds.
I do not know what to do. how is possible this has happened?
Many thanks

can you perform these steps with a newly generated wallet and get this same wrong-account behavior? it would help if you could post a video of that, if you're able to reproduce this behavior


Support external source of router config

For now the router config looks like this:
"routing": {
    "strategy": "rules",
    "settings": {
      "rules": [
        {
          "type": "field",
          "ip": [
            "<IP_ADDRESS>/8",
            "<IP_ADDRESS>/8",
            "<IP_ADDRESS>/10",
            "<IP_ADDRESS>/8",
            "<IP_ADDRESS>/16",
            "<IP_ADDRESS>/12",
            "<IP_ADDRESS>/24",
            "<IP_ADDRESS>/24",
            "<IP_ADDRESS>/16",
            "<IP_ADDRESS>/15",
            "<IP_ADDRESS>/24",
            "<IP_ADDRESS>/24",
            "::1/128",
            "fc00::/7",
            "fe80::/10"
          ],
          "outboundTag": "direct"
        }
      ]
    }
  }

It is not easy for one to manage a list of IPs (or domains) that are private to his usage, especially in the multi-instance scenario.
It would be better that the list of IPs (or domains) can be stored in a separate source (such as a text file).

Change of plan. It doesn't seem to be necessary after protobuf change.


get_material_scalar_parameter returns inaccurate value for MaterialExpressionStaticSwitchParameter

Win 10
UE-4.14.3
UnrealEnginePython_20170117_4_14_python27.zip
Hi,
In #103, I missed the fact that get_material_scalar_parameter always returns 0.0 when querying params of the MaterialExpressionStaticSwitchParameter class type regardless of the actual value. The material instance was created from a material that was built from blueprint.
I can't send a full repro, but this is essentially what I'm doing:
        all_components = actor.get_components()
        component = all_components[0]
        material_instance = component.get_property('Material')
        material_parent = material_instance.Parent
        expr = material_parent.Expressions[0]
        for expression in material_parent.Expressions:
            parameter_group = expression.Group
            parameter_name = expression.ParameterName
            expression_type = expression.get_class().get_name()
            if expression_type == 'MaterialExpressionStaticSwitchParameter':
                parameter_value = material_instance.get_material_scalar_parameter(parameter_name)

Do you think that this another case of the default class values being accessed, instead of the class instance?
Thanks!
MK

Hi, i have added get_material_static_switch_parameter(name) for accessing 'MaterialExpressionStaticSwitchParameter'

That's working well for 'MaterialExpressionStaticSwitchParameter'. And it also seems to work for 'MaterialExpressionStaticBoolParameter' as well.
Thanks!


Follow up fix for positive for Rails/ActionControllerFlashBeforeRender in rescue block

This PR fixes a false positive for Rails/ActionControllerFlashBeforeRender when using flash in multiline begin...rescue branch before redirect_to.
I ran into the same situation as #844 but within the begin ... rescue branch.

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[ ] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[ ] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.
[ ] If this is a new cop, consider making a corresponding update to the Rails Style Guide.

@gurix This looks good to me. Can you refactor with the above review comment and squash your commits into one?


oidcng no longer takes the "sub" value from the epTID

This issue is imported from pivotal - Originaly created at Nov 5, 2020 by Bart Geesink
The value of the "sub" claim should come from the epTID attribute. That doesn't seem to be the case anymore.

https://github.com/OpenConext/OpenConext-oidcng/commit/945b8636a3bd3fc8b11f919eaa3cc9ef96940868 (Okke Harsta - Nov 5, 2020)


Redux branch

Working redux example (tests not updated yet).
Let's correct me if files are not placed correctly or against mantra specs.

@ShockiTV, thanks for doing this! I'm learning Redux at the moment. How's your experience with Redux? Is it better than using ReactiveDict? ReactiveDict-based localstate gets a little messy for me now. I'm looking to switch to redux. Would love to hear about your experience first before I switch.

It is my first redux experience :D
Still I am little confused form this, as mantra actions are quite complex.
And in Redux naming Actions are something else.
But if I put only redux Actions as Mantra actions, there would have to be very ugly high level reducers calling smaller reducers.
I did not feel very good with that.
Let's wait for maintainers will think :D

@ShockiTV regarding actions/reducers etc. You could take a look at using the redux-ducks concept > https://github.com/erikras/ducks-modular-redux

Maybe also relevant: https://github.com/kadirahq/mantra/issues/103
I'm also looking for the correct way to integrate Redux with MantraJS. Maybe we can learn something from each other.

I've been working on a boilerplate (work in progress) using React-Router, Redux, React-Router-Redux, and React Helmet, take a look here. It has a working example. Feedback welcome.

@cheersjosh I'm looking forward to a more comprehensive example, using containers, data fetching etc. I'm happy to discuss it :)


Creating MariaDB strored procedure with DBeaver generates unclear error.

System information:

Linux Mint 19.3
DBeaver version 6.1.3
Java version
openjdk version "11.0.3" 2019-04-16
OpenJDK Runtime Environment (build 11.0.3+7-Ubuntu-1ubuntu218.04.1)
OpenJDK 64-Bit Server VM (build 11.0.3+7-Ubuntu-1ubuntu218.04.1, mixed mode, sharing)

Connection specification:

Database name and version: MariaDB 10
Driver name: ?
Do you use tunnels or proxies (SSH, SOCKS, etc)? no

Describe the problem you're observing:
See also:
Steps to reproduce, if exist:
I created an SQL Query, which works fine in DBeaver.
Now I would like to change it to a stored procedure but still without success.
Following is my code:

DELIMITER //
CREATE PROCEDURE hibiscus.findAllForPivot
 (
     IN jahr varchar(4),
     IN kontos VARCHAR(500)
 )
   BEGIN
select
 VCT.l1_Id,
 VCT.l1_GroupName,
 VCT.l2_Id,
 VCT.l2_GroupName,
 sum( case when (VCT.monat = 1) then dbetrag end ) AS `jan`,
 sum( case when VCT.monat = 2 then dbetrag end ) AS `feb`,
 sum( case when VCT.monat = 3 then dbetrag end ) AS `mrz`,
 sum( case when VCT.monat = 4 then dbetrag end ) AS `apr`,
 sum( case when VCT.monat = 5 then dbetrag end ) AS `mai`,
 sum( case when VCT.monat = 6 then dbetrag end ) AS `jun`,
 sum( case when VCT.monat = 7 then dbetrag end ) AS `jul`,
 sum( case when VCT.monat = 8 then dbetrag end ) AS `aug`,
 sum( case when VCT.monat = 9 then dbetrag end ) AS `sep`,
 sum( case when VCT.monat = 10 then dbetrag end ) AS `okt`,
 sum( case when VCT.monat = 11 then dbetrag end ) AS `nov`,
 sum( case when VCT.monat = 12 then dbetrag end ) AS `dez`
 from hibiscus.V_HibCrosUmsGiroOpaOmaReport VCT
 where  VCT.jahr = jahr and VCT.konto_id in (kontos)
 group by VCT.L1_id, VCT.L1_GroupName, VCT.L2_id, VCT.L2_GroupName;
 END
 //
 DELIMITER ;

I got always the following error:
SQL-Fehler [1064] [42000]: (conn:26) You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '' at line 26
Query is : CREATE PROCEDURE hibiscus.findAllForPivot

If I remove the group by line, the same error is at line 25 If I use the complete select statement with where and group by alone, everything works fine! I check double the fields in the table.
I thought will get mad because I can't find the reason.
The fields in the table are (entered by copy&paste):
dBetrag
id
Jahr
JahrMonat
konto_id
L1_GroupName
L1_id
L2_GroupName
L2_id
Monat
I did the same with PhpMyAdmin and did not get this error. Everything was fine, the procedure was created.
I assume that the reason is something around DBeaver.
Thank you in advance
Schwabenheinz

is it still actual against the recent version (7.0)?

Thank you for asking!
Yes, i tried it with Version <IP_ADDRESS>003021717.
I got:
SQL-Fehler [1064] [42000]: (conn:33) You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '' at line 26
Query is : CREATE PROCEDURE hibiscus.findAllForPivot.........

It is still actual in new versions?
Some changes have been added to the query parsing in the SQL Editor

there is no update on the issue for a long time.
If the issue is still actual for you - feel free to reopen it

there is no update on the issue for a long time.
If the issue is still actual for you - feel free to reopen it


Listen for mouseUp outside of the ripple item

This prevents bugs from ripples that gets triggered in the container but receives the mouseUp event outside of it and so it gets ignored. Resulting in an ever-lasting ripple.
Related to #25

Closed in a86bb10ea39c4511428470d2a980a7bb1135dc5a


Add and validate logic for string concatenation

Took logic code out of commenting one line at a time, confirmed that each line worked correctly.


Dehumanize() leaves question mark intact

Maybe this is by design, but:
"Hey?".Dehumanize() will equal "Hey"
"Hey ?".Dehumanize() will equal "Hey?"
Tried with 1.33.7.

That's a bug. Thanks for reporting.

Fixed in #381


Missing Spaces After The Line Ends

Describe the bug

After the line ends, the next line starts without any space
Expected behavior

There should be one space
Screenshots (optional)

Additional context (optional )

can you tell me where I can its code

@pranjay-poddar


Pytest_asyncio event loop replacement deprecated

In the conftest.py the event loop is being replaced with a new one. This is no longer supported with pytest_asyncio and results in this warning:
Replacing the event_loop fixture with a custom implementation is deprecated
  and will lead to errors in the future.
  If you want to request an asyncio event loop with a scope other than function
  scope, use the "scope" argument to the asyncio mark when marking the tests.
  If you want to return different types of event loops, use the event_loop_policy
  fixture.

Thank you!
I have just dropped the test examples and now this won't be a problem :)