question: heartbeat: Is connection between the server handled in a separate thread?

I am not proficient in async rust (as well as in general :cry:) so sorry in case I am wrong somewhere in basics.
As I understand by default reactors(tokio, etc.) uses one thread to handle async stuff. If lapin does networking with a rabbitmq server in main thread long sync jobs can cause a timeout of heartbeat.
Does lapin handle networking in a separate thread?
PS: I did go through the code but didn't come to the answer :disappointed:
Thank you for the crate

Did you actually hit such a timeout?
Do you use an external runtime integration such as async-amqp, tokio-amqp or lapinou?
By default the heartbeat is handled by the same thread that handles the IO events, which is a separate thread spawned by lapin.
https://github.com/CleverCloud/lapin/blob/master/src/reactor.rs#L124
The heartbeat.poll_timeout() here sends the heartbeat if necessary, or tells poll not to block for too long to be able to send the next heartbeat just when we should

Did you actually hit such a timeout?

I haven't, that question just naturally came to my mind.

Do you use an external runtime integration such as async-amqp, tokio-amqp or lapinou?

Yes I am using a tokio integration.

By default the heartbeat is handled by the same thread that handles the IO events, which is a separate thread spawned by lapin.

So if it's done in a separate thread I guess there should be no worries :+1:
Here's an example of the concern I had
    consumer.set_delegate(move |delivery: DeliveryResult| async {
         // emulate a long sync work
         //
         // by default heartbeat timeout is 60 seconds so
         // if it would handled in the same thread the connection on the server would be closed?
         thread::sleep_ms(1000 * 60)
    })?;

Yup, that won't run in the same thread.
Do not though that AMQP heartbeat have two particularities:

If you configure the heartbeat to be 60s, the actual time between two heartbeats on idle will be 30s, half the configured time (and if 60s have passed, the connection is considered as failed)
No heartbeat frame is sent as long as other frames are sent. A heartbeat frame will be sent only if we didn't send anything for e.g. 30s if it's configured as 60s.

I might be a bad question but just to be better tuned.
Does all runtime integrations follow the same internal logic as the default runtime?
So Yup, that won't run in the same thread. would be true for each runtime?

I haven't gone over code :disappointed:

Tokio and bastion only switch which executor is used, it's not yet possible to hook properly in their reactor, so yes.
For smol and async-std, we basically spawn a task on the executor which can be summarized as:
loop {
     Timer::new(heartbeat.poll_interval()).await
}

Meaning that this task should get awaken by the executor at the right time to trigger the heartbeat the same way the internal lapin's reactor does. The only caveat here is that if you do blocking stuff inside all the threads of the executor at the same time, you could get in trouble, but the heartbeat won't be your biggest concern when this time comes. Using blocking::unblock for such tasks should always be preferred anyways: https://docs.rs/blocking/0.6.1/blocking/fn.unblock.html

Thank you @Keruspe for these clarifications.
And sorry for bothering.
I will close the issue


add: ajalt/mordant

Fixes #18

changes made as requested in #30
added ajalt/mordant

@jmfayard i have made the requested changes accordingly as mentioned in #30 :)

Thanks @DarthBenro008 !
I merged your changes


redis_address default typo in documentation

https://github.com/kolide/fleet/blob/master/docs/infrastructure/configuring-the-fleet-binary.md#redis_address
has a "localhost:3306" by accident, as well as the correct "localhost:6379"

Verified 6379 as the correct address per https://github.com/kolide/fleet/blob/master/server/config/config.go#L126. PR incoming to fix this.


[e2e]: nodejs push main default slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/5162248145
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.push.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.push.main.default.slsa3.yml
Trigger: push
Branch: main
Date: Sat Jun  3 06:18:50 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/5167615532
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.push.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.push.main.default.slsa3.yml
Trigger: push
Branch: main
Date: Sun Jun  4 06:19:15 UTC 2023
Tests are passing now. Closing this issue.


mkimage-arch.sh failing on armv6h (RPi B+)

Building a docker image on a Raspberry B+ running itself Arch Linux ARM, I encountered a bug preventing packages download from repos (Error 404).
The issue is at line 63, in the sed pattern:
sed "s/Architecture = armv/Architecture = armv${version}h/g" './mkimage-archarm-pacman.conf' > "${PACMAN_CONF}"

which produces as an output the following line
Architecture = armv6h6h
As a quick workaround I changed line 63 into
sed "s/Architecture = armv.*/Architecture = armv${version}h/g" './mkimage-archarm-pacman.conf' > "${PACMAN_CONF}"

I'm not proposing a commit since I'm not sure whether this fix breaks the script for other arm architectures or not.

/cc @justincormack @alexellis

Let me close this ticket for now, as it looks like it went stale.


Accuracy of normal_lccdf much worse than normal_lcdf

Description
The implementation for normal_lcdf has been improved significantly following #1284 by introducing a polynomial approximation of the Mills ratio based on a paper by Cody (1969). It looks like normal_lccdf has not been updated accordingly and instead still uses the older and much less accurate solution.
Incidentally, I also noticed that normal_lcdf and std_normal_lcdf implement the same solution with very similar code. I wonder if one could retain the current implementation of std_normal_lcdf and write std_normal_lccdf, normal_lcdf and normal_lccdf to simply call std_normal_lcdf with appropriate parameters (-x, (x-mu)/sigma,  (mu-x)/sigma, respectively).
Current Version:
v3.2.0

@PhilClemson what do you think?

Sorry, this is something that was mentioned in the original pull request for the normal_lcdf changes but seems it was forgotten about.
@nhuurre mentioned that the functions could be standardised in a log_Phi function (https://github.com/stan-dev/math/pull/1411#issuecomment-544426991) but this would require separate numerical approximations.
It seems std_normal_lcdf was added by @mcol to follow the structure of the other probability distributions. I guess this might be a wider issue since there's also the std_normal sampling statement within stan?
In any case I don't think there's anything to stop us from adding the improvements to normal_lccdf so that should probably be done as a minimum.

call std_normal_lcdf with appropriate parameters

What parameters?  As a distribution, std-normal doesn't have any parameters.  It's just
std_normal_lpdf(y) == normal_lpdf(y | 0, 1).

Accuracy of normal_lccdf much worse than normal_lcdf

lccdf should be more accurate when the cdf is near 1, and the lcdf should be more accurate when the cdf is near 0.
Most of our lcdf and lccdf functions are terrible log(cdf) and log(1 - cdf) implementations.

@bob-carpenter Sorry, I should have been clearer. I meant "parameters" in a CS sense as in arguments. There could be a common C++ function implementing the logCDS of a std normal and all the Stan functions could call that same C++ function under the hood, with appropriate function arguments. For example std_normal_lccdf could call this function with argument -x.
This is a log cdf so I am not sure your argument about the accuracy near 0 or 1 really applies. Th domain is not (0,1) but (-inf,0). We do not need to sacrifice the accuracy on either side.

@nhuurre mentioned that the functions could be standardised in a log_Phi function (#1411 (comment)) but this would require separate numerical approximations.

I think the comment "this would require separate numerical approximations" only applies when you try to extend log_Phi to non-normal distributions (e.g. exp_mod_normal_lpdf etc). Within the four functions std_normal_lcdf, std_normal_lccdf, normal_lcdf and normal_lccdf, the same approximation works fine as these are just affine transformations of the argument.

I meant "parameters" in a CS sense as in arguments.

This gets confusing in stats.  But whatever you want to call it, std_normal_lpdf is a function from real numbers to real numbers.
The move from std_normal to normal is the usual location/scale generalization.  That's also used for most of our other univariate distributions, though we don't have std_logistic or std_student_t.
The whole point of having std_normal was to have a more efficient way of doing things that didn't involve subtracting 0 and dividing by 1.   So presumably we're talking about converting normal to std_normal by (y - mu) / sigma, not the other way around.  That will get the right density for the normal, but the derivatives are the bigger concern.  We don't want to just autodiff (y - mu) / sigma.

I am not sure your argument about the accuracy near 0 or 1 really applies.

As the cdf approaches 0, log(cdf) approaches -infinity and log(1 - cdf) approaches 0.  So you're right that we should be able to get decent accuracy both ways.   I was tied up in our current implementations, which are a mess.
We do need the complementary forms for the arguments, though.  Just consider a beta(y | 0.5, 0.5) distribution.  That's going to go to 0 or 1 as y goes to 0 or 1, but you can't represent a y very close to 1 in floating point, so you have to use
Does that mean we could just get rid of the lccdf functions?  Is there just as much accuracy in lcdf and lccdf as cdf goes to 0 or to 1?

The normal is symmetric around the location parameter, so we can relate
normal_lcdf(y | mu, sigma) == normal_lccdf(mu + -(y - mu) | mu, sigma).

@bob-carpenter

So presumably we're talking about converting normal to std_normal by (y - mu) / sigma, not the other way around.

Yes.

That will get the right density for the normal, but the derivatives are the bigger concern. We don't want to just autodiff (y - mu) / sigma.

I see.

We do need the complementary forms for the arguments, though. Just consider a beta(y | 0.5, 0.5) distribution. That's going to go to 0 or 1 as y goes to 0 or 1, but you can't represent a y very close to 1 in floating point, so you have to use the lcdf or cdf as appropriate just for the arguments. Same with any distribution truncated at 0, which needs the cdf.

I was only referring to the Gaussian case. This is particularly useful for me because I can model an exponential distribution as a Gaussian in unconstrained space and then define my constrained variable just as y=std_normal_lcdf(-x). It works much better in my case (in terms of convergence) than using the default log transformation you get with <lower=0>.


CDN Version

Hi love the project and the work going on, will there be a cdn version for browsers?

Thank you. Yes , you can use<EMAIL_ADDRESS>


[FEAT] Add Ray-based live migration for Transformers backend

Description
This PR implements a Ray-based live-migration feature for the Transformers backend, based on the ServerlessLLM paper. Key features include:

Migration Router: Handles live migration by:

Starting a new inference backend on the target node.
Resuming KV cache for ongoing tokens.
Preempting the source backend.
Resuming inference seamlessly on the target.
Managing potential migration failures.

Enhanced Scheduler: Supports live migration as an option when locality isn't met, including:

A migration planner to minimize total latency.
Latency estimation based on active token counts and storage status.

Store Manager Updates: Enhances the pinned memory pool by allowing models to be cached during deployment (via model configuration), even if not requested.

Resource Allocation API: Updated to support migration workflows.

Miscellaneous Changes: Core module updates for live migration compatibility.

Examples and documentation for live migration.

Test instructions
Refer to the documentation at docs/stable/serve/live_migration.md for detailed testing steps.
Motivation
This feature demonstrates live migration for LLM inference as proposed in the ServerlessLLM paper, enabling more flexible and locality-aware scheduling. Closes #131.
Note: Current support is limited to the Transformers backend. Future PRs will add:

vLLM backend support.
Performance optimizations:

Standby workers for reduced warmup latency.
Parallel and overlapping migrations.
Migration cancellation support.

Type of Change

[x] New feature

Checklist

[x] I have read the CONTRIBUTING guide.
[x] I have updated tests and documentation where applicable.

This PR will be ready for review once PR #168 is merged.


Redirect root path to UI handler at /dashboard

This change proposes sending the client an HTTP 303 to /dashboard when the root path / is requested. This is a convenience feature useful for standalone/non-embedded TiDB dashboard deployments.

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

hi @LINKIWI thanks for your contribution, we will have a test and review soon.

I tested it and it works as expected. hi @breeswish , how do you think about it?


[WIP] Add semicolon after instruction fixer

Fixer that makes sure every instruction is terminated with a semicolon.
(On master only because I need CurlyBraceTransformer.)

missing case:
<?= 1 ?>

Thank you @SpacePossum.

:+1:
btw. it awesome that you delete the branch as well, keeping everything clean and the development cycle fast : D

oh, sorry, it wasn't intended :( just a habit...
I will try to not do that in future, in any case you could restore the branch (eg from github interface)

its all good man :)


Mutating webhook should self-register

MutatingWebhook config existence and lifecycle should be tied to sidecar injector, similar to validating webhook and galley: https://github.com/istio/istio/pull/7234
Otherwise a situation can exist that the webhook config causes pod creating to fail due to temporary or permanent absence of sidecar injector.

After some discussion, the consensus is that we'd rather avoid having the possibility of pods created with sidecar much more than pod creation failing due to sidecar not yet running.


Review for Missing Documentation - at_lookup (API Reference)

[ ] Right nav bar under documentation API Reference .  Check for any missing documentation (samples and examples)
[ ] Do we need a link for documentation?

Please review library links as well (current, samples and examples)
LIBRARIES

[ ] at_lookup

Hi @kalluriramkumar we need to review this very old ticket for accuracy, potentially close it and divert to the new pub.dev publishing issue. Creating new issue cards today.


Use new Faas proto payloads for FaaS implementation.

With the package io.nitri.faas I would recommend renaming the following classes:

ResponseContext to AbastractResponseContext
TriggerContext to AbstractTriggerContext
HttpRequestTriggerContext to HttpTriggerContext
For me this helps me to understand their role and logically groups them

With the package io.nitri.faas I would recommend renaming the following classes:

ResponseContext to AbastractResponseContext
TriggerContext to AbstractTriggerContext
HttpRequestTriggerContext to HttpTriggerContext

For me this helps me to understand their role and logically groups them

Done :)


Fix issue with month and year picker in scroll mode

Types of changes
What types of changes does your code introduce?
Put an x in the boxes that apply

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

Description
When the showDate, minDate and maxDate are set, the showDate does not show as focused, hence the month and year at the to of the calendar displayed the minimum date.
This was due to the focusedDate being set later.
Adding more delay to the call to focusToDate solves this issue.

Related Issue: https://github.com/Adphorus/react-date-range/issues/215

The same issue is resolved in the latest version. Thank you for your Pull Request on the issue. I'm closing this.


Bossbar API

An API to get the message shown in the bossbar.
Or a method to get a boss (enderdragon, wither) from its name.

And vice versa


refatcor: make test case write much easier

Signed-off-by: Allen Sun<EMAIL_ADDRESS>1.Describe what this PR did
I think we need to prepare to reduce the cost of contributors to write test case as much as we can. Maybe contributors are very familiar with your code, but not so familiar with your test case code. While I think test is the same important as the software implementation code.
In go's design, we need to always do error checking which has already evoked lots of debate in the community. This PR reduces lots of useful but redundant err checking and asserting.
In pkg request, I introduces a global checker to detect error in function's implementation. So in the detailed test cases, they do not need to assert error to be nil frequently.
When our test cases grows very fast. I think this way will reduce much test code in pouch.
WDYT? @Letty5411 @sunyuan3 @0x04C2
2.Does this pull request fix one issue?
NONE
3.Describe how you did it
In pkg request, I introduces a global checker to detect error in function's implementation. So in the detailed test cases, they do not need to assert error to be nil frequently.
4.Describe how to verify it
NONE
5.Special notes for reviews

Hi, @allencloud , I agree with you. But I run this patch in my local and it paniced.
And I do some investigation about github.com/go-check/check. Ref is here
It's hard to make global check.C variable, because it needs caller context.
If we want to reduce the error check, it seems that we should add new argument in every request method, some thing like:
Delete(c *check.C, endpoint string, opts ...Option) *http.Response {
...
}

But it makes the method weird....😅

It's hard to make global check.C variable, because it needs caller context.

Thank for the details you provides.
Yeah, unfortunately the CI fails. And I also agree with weird saying. @0x04C2
Let me consider more if we can find out a solution.

Let me consider more if we can find out a solution.

OK. We can find it out during writing the cases! :)

@0x04C2 Add argument "check.c" in every lib function is a little wired. Another method maybe that we add a wrapper in lib function. Something may like this , not accurate:
func CallPostOk (c *check.c, args ...interface{}){
    err := request.Post(args)
    c.Assert(err, check.IsNil)
}

But it is not straightforward to understand.

But to users, they are the same.

Hi, @allencloud  and @Letty5411 , if we use check.C as first argument, which one will be better?
one:
type testingT interface {
    Fatal(args ...interface{}) // fail now
}

func XXX(t testingT, ....)

two:
func XXX(c *check.C, ...)

The first one is better?

 @Letty5411 FYI


Can we use this for walkthrough or get started screen animations using slide animation

How to implement walkthrough animations like slide or pager - This should be interactive animations
How to achieve this.. can anyone help ?

Yes, definitely. Just setup multiple view controller that have the same base class. Setup the interactive transition inside the base class. Checkout the AppleHomePageExample for some idea.


*** Error in `/usr/local/bin/uwsgi': corrupted size vs. prev_size: 0x00000000034b9160 ***

When trying to delete any file I get
*** Error in '/usr/local/bin/uwsgi': corrupted size vs. prev_size: 0x00000000034b9160 ***
Error in uwsgi logto file
uwsgi: malloc.c:2394: sysmalloc: Assertion '(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)' failed.
and when it blows the full memory log trace.
*** Error in '/usr/local/bin/uwsgi': corrupted size vs. prev_size: 0x00000000034b9160 ***
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x777e5)[0x7fbb146427e5]
/lib/x86_64-linux-gnu/libc.so.6(+0x82aec)[0x7fbb1464daec]
/lib/x86_64-linux-gnu/libc.so.6(__libc_malloc+0x54)[0x7fbb1464f184]
/usr/lib/x86_64-linux-gnu/libmariadb.so.2(+0x26a49)[0x7fbb0c7a6a49]
/usr/lib/x86_64-linux-gnu/libmariadb.so.2(+0x24797)[0x7fbb0c7a4797]
/usr/lib/x86_64-linux-gnu/libmariadb.so.2(+0x2497a)[0x7fbb0c7a497a]
/usr/lib/x86_64-linux-gnu/libmariadb.so.2(+0x1c9a1)[0x7fbb0c79c9a1]
/usr/lib/x86_64-linux-gnu/libmariadb.so.2(+0x1de2c)[0x7fbb0c79de2c]
/usr/lib/x86_64-linux-gnu/libmariadb.so.2(mysql_real_query+0xcb)[0x7fbb0c79e13b]
/home/krizo/Env/krizo/lib/python3.5/site-packages/_mysql.cpython-35m-x86_64-linux-gnu.so(+0x685d)[0x7fbb0c9d485d]
/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0(PyCFunction_Call+0xc9)[0x7fbb14c7b039]
/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0(PyObject_Call+0x6e)[0x7fbb14d5454e]
/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0(PyEval_CallObjectWithKeywords+0x47)[0x7fbb14e16937]
/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0(+0x117fa8)[0x7fbb14ce4fa8]
/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0(PyObject_Call+0x6e)[0x7fbb14d5454e]
......

django 1.11.13
python3.5
ubuntu 16.04
Tested with latest uwsgi 2.0.17 and <IP_ADDRESS>
I guess this is not a django-filer issue but I was wondering if anyone had this issue in the past.

Seems to be related to mysqlclient and mabriadb.
I've tested the same project but using sqlite and I can't replicate the issue.


Compatibility with Traefik v2

Is this a BUG REPORT or FEATURE REQUEST?:
FEATURE REQUEST
Anything we need to know?:
Traefik v2 alpha was release some weeks ago. They moved from Ingress to CRDs.
This will bring an incompatibility between Kubeless and Traefik.
More info here: https://docs.traefik.io/v2.0/providers/kubernetes-crd/
Maybe you can look into it to eventually bring support for it! 😄

Is there any plan to support traefik v2+ ?


Explicit parent style requirements

ListView requires the parent's style to have the flex property to scroll through the list. That is not stated explicitly and can make it difficult for new users to understand why their listview doesn't scroll. This attempts to make that explicit.
Test plan (required)
This is a documentation change so I don't believe testing is needed
Make sure tests pass on Circle CI.
Code formatting
See the simple style guide.

In order to solve this, one thing I had in mind was to warn if the scrollview is bigger than the screen, which would mean that it overflows. What do you think?

I am the noob that I'm referencing in the docs. I'm not stuck on the flex stuff, I'm just trying to communicate an important part of the ListView. If you just stick it in a view, then it won't scroll. The list will show up, but it won't scroll. It always bounces back to it's starting position. One way that I fixed this is to make the parent flex. I'll try the height part and report back.

So, this is a common problem and we need to find a way to get people unstuck. But i'm not sure that the advice of always wrapping in flex: 1 is a good one. If you are with flex, you need to have all the parents up have flex 1.

Fair enough. Can we just lay out the requirements and present some(not all) ways to fulfill those requirements? Parents all the way up being flex as just one of those?

We could add an onLayout handler to ScrollView (this affects all ScrollViews, not just ListView) and complain if it has a zero dimension.

@vjeux would you mind taking a look at this pull request? It's been a while since the last commit was reviewed.

Let's close this pull request as there hasn't been activity in a long time. Feel free to re-open if you want to continue it!


Why train x->y and y->x for OASIS and abdomenCTCT dataset?

In the training part in train.py, the registration model is trained by (x,y) pair firstly:
for data in train_loader:
    x = data[0]
    y = data[1]
    x_in = torch.cat((x, y), dim=1)
    output = model(x_in)
    ....

And for OASIS and abdomenCTCT dataset, (y,x) pair is also feed into the model:
......
if args.dataset == "OASIS" or args.dataset == "AbdomenCTCT":
    y_in = torch.cat((y, x), dim=1)
    output = model(y_in)
......

Why you do this? Is it for data augmentation?

So for OASIS and AbdomenCTCT, because they are inter-patient registration, there are no absolute definition of a fixed and moving image, in other words, both x and y can be the fixed image, and both x and y can be the moving image. So we take the advantage of this property of the data to perform this two-way registration. We first use x as the fixed image, y as the moving image, and then we inverse them and use x as the moving image and y as the fixed image. This essentially allows the model to learn more robust representations, and this is a common trick used in deep-learning-based image registration.

It's so clear. Thanks.

@yuelinxin 看了你的简历，本科生就这么强了???

@yuelinxin 看了你的简历，本科生就这么强了???

啥呀😂，最近申请phd感觉全凉了。

@yuelinxin 看了你的简历，本科生就这么强了???

啥呀😂，最近申请phd感觉全凉了。

@yuelinxin 加油，确实很强。


Clarify that the latest Python might not work

I wasted a lot of time not realizing Python 3.11 isn't supported because of the lack of clarity in the line I've edited.
Checklist

[x] documentation is changed or added
[x] commit message follows commit guidelines

Description of change
Remove unclear reference to "current" Python version, that does not necessarily mean "current."
Someone please let me know if I need to re-title my PR. I don't see the relevant prefix, but maybe "docs:" ?

Actually, I get the same error no matter what version of Python 3 I use. Why is that? Isn't this issue supposed to be fixed already?
https://github.com/nodejs/node-gyp/issues/2219

As stated above, the problem was not related to the Python version.   This change is not needed because we work with and test pre-release versions of Python to ensure that our installation process is compatible with them on the day that they are released.

@cclauss I looked through the 8 binding.gyp files in our node_modules and none of them appear to specify rU or Ur, and node-gyp is at 9.3.0 which is the latest as of today.
I used Python2.7 to get around this, but I don't understand why the issue is occurring.

Please look thru your error log for the string gyp info using node-gyp@

Can you clarify what you mean by "your error log"? What would this be on a Windows machine? I don't see an npm-debug.log and there doesn't appear to be anything in Event Viewer (not that I expected there would be.)

What command did you type?
What text appeared on your screen after you typed it?

Well, I just realize that node-gyp is installed locally in our node_modules, and that one is not the latest version - so I guess that's the issue.
The failing module was fibers, which our upcoming version doesn't rely on at all - so I guess this is moot. It also explicitly says it's incompatible with Node 16, which I didn't know.
Thanks very much for your help @cclauss!
In case you still had some interest in the output upon failure, here it is. The command we ran was just yarn.
error C:\Projects\MyProject\node_modules\fibers: Command failed.
Exit code: 1
Command: node build.js || nodejs build.js
Arguments:
Directory: C:\Projects\MyProject\node_modules\fibers
Output:
gyp info it worked if it ends with ok
gyp info using<EMAIL_ADDRESS>gyp info using<EMAIL_ADDRESS>| win32 | x64
gyp info find Python using Python version 3.11.0 found at "C:\Python311\python.exe"
gyp info find VS using VS2019 (16.11.33027.164) found at:
gyp info find VS "C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools"
gyp info find VS run with --verbose for detailed information
(node:5036) [DEP0150] DeprecationWarning: Setting process.config is deprecated. In the future the property will be read-only.
(Use `node --trace-deprecation ...` to show where the warning was created)
gyp info spawn C:\Python311\python.exe
gyp info spawn args [
gyp info spawn args   'C:\\Projects\\MyProject\\node_modules\\node-gyp\\gyp\\gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'msvs',
gyp info spawn args   '-I',
gyp info spawn args   'C:\\Projects\\MyProject\\node_modules\\fibers\\build\\config.gypi',
gyp info spawn args   '-I',
gyp info spawn args   'C:\\Projects\\MyProject\\node_modules\\node-gyp\\addon.gypi',
gyp info spawn args   '-I',
gyp info spawn args   'C:\\Users\\Me\\AppData\\Local\\node-gyp\\Cache\\16.18.0\\include\\node\\common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=C:\\Users\\Me\\AppData\\Local\\node-gyp\\Cache\\16.18.0',
gyp info spawn args   '-Dnode_gyp_dir=C:\\Projects\\MyProject\\node_modules\\node-gyp',
gyp info spawn args   '-Dnode_lib_file=C:\\\\Users\\\\Me\\\\AppData\\\\Local\\\\node-gyp\\\\Cache\\\\16.18.0\\\\<(target_arch)\\\\node.lib',
gyp info spawn args   '-Dmodule_root_dir=C:\\Projects\\MyProject\\node_modules\\fibers',
gyp info spawn args   '-Dnode_engine=v8',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
gyp info spawn args   '--generator-output',
gyp info spawn args   'C:\\Projects\\MyProject\\node_modules\\fibers\\build',
gyp info spawn args   '-Goutput_dir=.'
gyp info spawn args ]
Traceback (most recent call last):
  File "C:\Projects\MyProject\node_modules\node-gyp\gyp\gyp_main.py", line 51, in <module>
    sys.exit(gyp.script_main())
             ^^^^^^^^^^^^^^^^^
  File "C:\Projects\MyProject\node_modules\node-gyp\gyp\pylib\gyp\__init__.py", line 670, in script_main
    return main(sys.argv[1:])
           ^^^^^^^^^^^^^^^^^^
  File "C:\Projects\MyProject\node_modules\node-gyp\gyp\pylib\gyp\__init__.py", line 662, in main
    return gyp_main(args)
           ^^^^^^^^^^^^^^
  File "C:\Projects\MyProject\node_modules\node-gyp\gyp\pylib\gyp\__init__.py", line 629, in gyp_main
    [generator, flat_list, targets, data] = Load(
                                            ^^^^^
  File "C:\Projects\MyProject\node_modules\node-gyp\gyp\pylib\gyp\__init__.py", line 150, in Load
    result = gyp.input.Load(
             ^^^^^^^^^^^^^^^
  File "C:\Projects\MyProject\node_modules\node-gyp\gyp\pylib\gyp\input.py", line 3021, in Load
    LoadTargetBuildFile(
  File "C:\Projects\MyProject\node_modules\node-gyp\gyp\pylib\gyp\input.py", line 411, in LoadTargetBuildFile
    build_file_data = LoadOneBuildFile(
                      ^^^^^^^^^^^^^^^^^
  File "C:\Projects\MyProject\node_modules\node-gyp\gyp\pylib\gyp\input.py", line 239, in LoadOneBuildFile
    build_file_contents = open(build_file_path, "rU").read()
                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^
ValueError: invalid mode: 'rU' while trying to load binding.gyp
gyp ERR! configure error
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (C:\Projects\MyProject\node_modules\node-gyp\lib\configure.js:351:16)
gyp ERR! stack     at ChildProcess.emit (node:events:513:28)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:293:12)
gyp ERR! System Windows_NT 10.0.22000
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Projects\\MyProject\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" "--release"
gyp ERR! cwd C:\Projects\MyProject\node_modules\fibers
gyp ERR! node -v v16.18.0
gyp ERR! node-gyp -v v7.1.2
gyp ERR! not ok
node-gyp exited with code: 1
Please make sure you are using a supported platform and node version. If you
would like to compile fibers on this machine please make sure you have setup your
build environment--
Windows + OS X instructions here: https://github.com/nodejs/node-gyp
Ubuntu users please run: `sudo apt-get install g++ build-essential`
RHEL users please run: `yum install gcc-c++` and `yum groupinstall 'Development Tools'`

Line 8:

gyp info using<EMAIL_ADDRESS>
https://github.com/nodejs/node-gyp/releases

Yeah I realized, I mentioned - but I'm sure you're very busy and I know I'm a bit wordy. I appreciate all your help. Thanks again!


SBU download is failing

This is happening since roughly a month (first detection in #6274), but was masked by #6268.
http://www.cs.virginia.edu/~vicente/sbucaptions/
The server is still up, but the path is no longer valid. I'll reach out to the author to see if this can be fixed. In the meantime we should probably disable the test.
cc @pmeier @YosuaMichael

I've contacted the author of the paper and the new link is
https://www.cs.rice.edu/~vo9/sbucaptions/
Will send a PR to update our sources.

The author provided me a link to the actual image archive rather than just an URL list. The website reads

Alternatively, if you're interested in the image collection for research purposes please email<EMAIL_ADDRESS>
I'm checking back if it is ok for us to publish that link. That would simplify the download by quite a bit and would mean the discussion in #5706 is moot for now.


#26 - Implement password encryption and decryption

Implemented password encryption on signup and reset password and password compare on login

branch has conflicts that must be resolved


Plugin sometimes fails to update when I get the master clue

Plugin believes I have 4 clues with Watson even though I just got a master clue from Watson.
Upon checking the stored units the plugin updated normally

And I got this after handing the 4 clues in my inv to Watson

Same experience.  Hopefully I get to this before leagues is over and clues are hard to get again.

Jagex changed some widget ids. Also, it doesn't work with master scroll boxes. Bit late but hopefully that's the issue. https://github.com/runelite/plugin-hub/pull/2452

Outdated, the plugin no longer uses chat dialogue.


Fixed Bluetooth Source pairing so it works with more devices

These lines made it so this code would not pair with a lot of Bluetooth speakers:
/* search for device with MAJOR service class as "rendering" in COD */
if (!esp_bt_gap_is_valid_cod(cod) ||
!(esp_bt_gap_get_cod_srvc(cod) & ESP_BT_COD_SRVC_RENDERING)) {
return;
}
I modified the code so that it only validates against MAJOR DEVICE being AV. I also removed the esp_bt_gap_is_valid_cod check because I found that some of my bluetooth speakers did not pass that check, but they still were detected as valid AV devices. The rest of the changes are just clean up and a slight restructure of the filter_inquiry_scan_result function and ESP_LOG calls
/* search for device with MAJOR DEVICE class as "Audio/Visual" in COD */
if ((esp_bt_gap_get_cod_major_dev(cod) == ESP_BT_COD_MAJOR_DEV_AV))
{

Thanks a lot


DataFrame.mean is broken in case of axis=1 and numeric_only=None

Describe the problem
mean produces an empty frame in case of applying on axis=1, However, other reduction operations works fine with axis=1
Reproducer:
import modin.pandas as pd
import pandas
from modin.pandas.test.utils import (
    test_data_diff_dtype,
    df_equals,
)

pd_df = pandas.DataFrame(test_data_diff_dtype)
md_df = pd.DataFrame(test_data_diff_dtype)

reduction_operation = ["max", "min", "median", "skew", "kurt", "sem", "std", "var"]

for op in reduction_operation:
    df_equals(getattr(md_df, op)(axis=1), getattr(pd_df, op)(axis=1)) # works fine

df_equals(md_df.mean(axis=1), pd_df.mean(axis=1)) # AssertionError

 Traceback

Traceback (most recent call last):
  File "../TESTS/t2.py", line 108, in <module>
    df_equals(md_df.mean(axis=1), pd_df.mean(axis=1))
  File "/localdisk/dchigare/repos/modin_bp/modin/pandas/test/utils.py", line 520, in df_equals
    assert_series_equal(df1, df2, check_dtype=False, check_series_type=False)
  File "/localdisk/dchigare/miniconda3/envs/modin_tests/lib/python3.7/site-packages/pandas/_testing.py", line 1401, in assert_series_equal
    index_values=np.asarray(left.index),
  File "pandas/_libs/testing.pyx", line 67, in pandas._libs.testing.assert_almost_equal
  File "pandas/_libs/testing.pyx", line 182, in pandas._libs.testing.assert_almost_equal
  File "/localdisk/dchigare/miniconda3/envs/modin_tests/lib/python3.7/site-packages/pandas/_testing.py", line 1036, in raise_assert_detail
    raise AssertionError(msg)
AssertionError: Series are different

Series values are different (100.0 %)
[index]: [0, 1, 2, 3]
[left]:  [nan, nan, nan, nan]
[right]: [-2.5, -2.1333333333333333, 6.033333333333334, 8.0]

Before this commit there was the exception.
TypeError: unsupported operand type(s) for +: 'int' and 'str'

After the commit the result is the following:
0   NaN
1   NaN
2   NaN
3   NaN
dtype: float64

May be, it will help somehow.


X-Editable not works with bootstrap 3.3.6

Hi!
I'm interested to use this plugin but it's not working with Bootstrap 3.3.6.
Anyone has solution for this?

its working fine

Plugin works fine on Bootstrap 3.3.6 here.


Exception when close all working files and some are dirty

From @isidorn on March 15, 2016 14:20

VSCode Version: 18ebb4a4f5491af7b16e91e42fc36410bbb2e4d7
OS Version: any

Steps to Reproduce:

Have multiple files open in working files
Have at lease one of those files dirty
Close All Working files by clicking the close action in the working files header, notice the exception
I can not repro this every time, but see it regularly

edited: first exception that I now removed was caused by an unrelated issue
Copied from original issue: Microsoft/vscode#4253

From @bpasero on March 15, 2016 14:30
@isidorn do you get the dialog prompting you to save dirty files before the exception or after?

From @isidorn on March 15, 2016 14:37
I get the dialog and I say 'do not save' - can not always repro, can you please try it out a couple of times

From @bpasero on March 15, 2016 14:49
I dont even know what that handler is as it seems in the extension host, moving to @jrieken / @alexandrudima

From @jrieken on March 15, 2016 16:7
@isidorn The steps don't do it for me, also the message appears nowhere in our sources. Please attach the debugger to the extension host and break on error such that we have a chance to understand this

From @alexandrudima on March 15, 2016 15:47
@isidorn Can you reproduce without installed extensions?
Hint: "Notification handler" string is not in vscode source code.

From @isidorn on March 15, 2016 15:52
@alexandrudima I can repro it if I do not have any extensions installed

From @alexandrudima on March 15, 2016 17:7
@dbaeumer Maybe you use such strings in the language protocol?

From @isidorn on March 15, 2016 17:15
@jrieken when I attach debugger to the extension host I can not seem to get it to break on this error.
I can easily repro so just drop by my table if you are interested in looking into this.

From @isidorn on March 15, 2016 18:34
@jrieken I do not have powershell installed

From @jrieken on March 15, 2016 17:48
harding @alexandrudima assumption about the language protocol (https://github.com/Microsoft/vscode-languageserver-protocol/blob/46dd8c99166b3cbee69a54e6043b99be221d793c/README.md#L654)

From @jrieken on March 15, 2016 17:47
@isidorn Sure you don't have PowerShell tools installed? https://github.com/PowerShell/PowerShellEditorServices/blob/9fa1feaf16d13075c02b420789bbebe9b75c122b/src/PowerShellEditorServices.Protocol/LanguageServer/TextDocument.cs#L59

From @jrieken on March 15, 2016 19:3
maybe tslint?

From @isidorn on March 15, 2016 19:9
I do not have any extensions installed :)
I only use open in github but I uninstalled it to try to repro this issue, and I could repro

The protocol calls a notification handler which causes an exception. The protocol on the lowest level catches the excpetion sends it back to the client which prints it to the console. There is nothing I can do better. The root cause of the exception must be fixed.
The root cause lies in the languge server. I receive an update event for a document that is already closed. The interesting question is why? But I will protect my code against it.

From @jrieken on March 16, 2016 7:58
Yes you have. It's called JSON and uses the language server protocol. Moving to @dbaeumer cos this seems to come from /Users/jrieken/Code/vscode/extensions/json/server/node_modules/vscode-languageserver/lib/protocol.js


[Remote Store] Handle translog upload during primary to primary relocation for remote-backed indexes

Is your feature request related to a problem? Please describe.
Currently, when peer recovery happens for primary-primary relocation, both the older & newer primary bootstraps engine and translog such that the upload happens from both the shards.
Following things need to be ensured -

When index.translog.durability is set as async, the translog sync happens every index.translog.sync_interval periodically. With this change, we decide to upload translog to remote store basis the primary mode. Since translog sync is async, in current status quo state, the upload is not determinstic to happen before primaryMode is marked as false. We need to ensure that the upload happens (successfully or it fails) deterministically before the primaryMode turns false on the old primary and before the new primary resets the engine (resetToWriteableEngine).
Reset the new primary engine after all translogs have been uploaded from the older primary to the remote store. This will ensure that the new primary gets all the translogs from remote store and then only it starts accepting any new write requests. This is already handled with ForceSyncTransportRequestHandler.

There is possible issue with data loss in relocation flow for seg rep based indexes. Issue - https://github.com/opensearch-project/OpenSearch/issues/5848
Describe the solution you'd like
Since the complete handoff process ensures that the primary mode switch happens such that the any inflight request in older primary is first drained off and then the newer primary gets promoted with primary mode set to true as part of handoff.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Fixed in https://github.com/opensearch-project/OpenSearch/pull/5804


ios: sent an event when the http request is unauthorized

Related issue:
https://github.com/mauron85/react-native-background-geolocation/issues/307
Related PR:
https://github.com/mauron85/background-geolocation-ios/pull/5
Library clients will be able to listen for 401 Unauthorized status codes received from http server.

Looking good. Merging. Thank you for you contribution.


Sometimes, at some point s3 hits a lot of 404s and task takes 10+ minutes

See the following log
ledger-service_build_294_upload-test-results.log
It was ok for a while and then suddenly it started to hit a lot of 404s. We had to cancel the task after 10min, because obviously we didn't want to wait forever for it.

Why suddenly the files went missing on s3?
Should we fail early or something, if such scenario [a lot of 404s] happens?

Hi @jtomaszewski, Are you still facing this issue?
If yes, could you send the details along with a sample BUILD URL (where you see this issue) to<EMAIL_ADDRESS>? Thanks!


Question: Do I have a way of finding out why the IP is in the list ?

Hello !
I'd like to be able to "classify" IPs in the list, in other terms being able to use only a subset of the lists, for instance let's say I'm interested only in blocking the IP/domains that tie directly to malware and let go the ads through
Do I have a way of doing that ?

@thomas-maurice you can visit https://github.com/Ultimate-Hosts-Blacklist where all the lists are filtered and get the list's info as well to see which is which but unless you do some custom list on your end where you can skip what you don't need i don't think that there is a simple option to exclude some IP's from the big list provided.

@dnmTX one day people will be eable to create their own list from a Web app 😉

https://hosts.ubuntu101.co.za/app/contents/ Will be documented, improved and probably moved elsewhere soon but if you want to help us with feedback. Please test it! 😊
Cheers,
Nissar
P.S: Please avoid % as much as possible. We still have to optimize but for a beginning. it's still great.


MAJOR Overhaul to data collection system

Data Collection System
Data collection is now handled by a DataCollector, with a set of DataHandlers, which run in a seperate goroutine and listen for events being dispatched to an eventChannel, before giving those events to handlers that listen for that event.
Closes #30 as a main point, also
Closes #31 by using goroutine with eventChannel.
Closes #32 at least twice...

Closed to add go mod tidy up to next pull.


Uncaught exception when setting up openfl (with haxe installed via homebrew)

Attempting to setup openfl on OS X 10.10 (with haxe installed by homebrew) causes this exception:
DeLorean:~ jakob$ haxelib run openfl setup
Called from ? line 1
Called from RunScript.hx line 40
Called from helpers/PathHelper.hx line 197
Uncaught exception - Invalid field access : split

From PathHelper.hx (in lime):
try {
	var cacheDryRun = ProcessHelper.dryRun;
	ProcessHelper.dryRun = false;
	output = ProcessHelper.runProcess (Sys.getEnv ("HAXEPATH"), "haxelib", [ "path", name ], true, true, true);
	ProcessHelper.dryRun = cacheDryRun;
} catch (e:Dynamic) { }

LogHelper.verbose = cache;

var lines = output.split ("\n");
var result = "";

Line 197 is a blank line, but the above lines are what surrounds it (blank lines have been removed for compactness). My HAXEPATH is not set, so that might be a part of it. If something goes wrong in ProcessHandler.runProcess() and it returns null, then that would explain why the output  string a few lines down is missing the split() method. But this is as far as my current haxe-skills take me.
Environment
DeLorean:~ jakob$ haxe -version
3.2.0
DeLorean:~ jakob$ haxelib list
lime: [2.5.2]
openfl: [3.2.2]

Saving clause(s)
I'm also having possibly related problems setting up lime. I've reported a separate issue  about that since it might also be completely unrelated.
I must admit I'm to new to the haxe-ecosystem to tell if this is a problem with homebrew, haxelib or openfl. But since I've not encountered any other haxe-lib with this priblem (yet). Thus I'm thought I'd start here and then work my way "uppstream" if this is not a lime issue.

Not sure if you found your fix for this or not, but I thought I'd leave my solution for anybody else who stumbles this way.
I installed haxe through the standalone installer, uninstalled my brew version of haxe, and everything worked for my openfl setup.

I think the homebrew install might break haxelib path lime, which might be the cause of this error.

Wouldn't surprise me, using homebrew seems to have set me back more than anything last night.
(I had to revert to updating flambe manually as well)

I found with my instance that I had some lingering bins installed in /usr/bin and as soon as I removed them, it instantly started working. I did also run the selfupdate, but it did not fix the problem. It just showed me what was wrong. haxelib was reporting back with the wrong version after the self update, and when it ran I got a permissions denied error, which was odd at the time, but now makes total sense. Folders were missing, libs had the wrong versions, etc.


⚠ Bofrost.at has degraded performance

In cbf3ea2, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2212 ms

Resolved: Bofrost.at performance has improved in 45f12eb.


Benchmark CRs do not have common state definitions

Not all benchmark CRs expose the same state definitions which makes it difficult to handle benchmarks in a uniform way.
The vast majority of the workloads have 3 general states: Building, Running, and Complete. Some workloads may have more than those 3 states (i.e. fiod has StartingServers/StartingClient), but that's fine as they still implement the core 3 states.
However, some benchmarks do not implement those 3 states which makes it difficult to handle the benchmarks in a programmatic fashion. For example,
hammerdb: "Complete" state maps to "DB Workload Complete"
stressng: "Running" maps to "Benchmark running"
Since these benchmarks use the same CRD, they should share the same state definition.

While I do agree we can standardize some of the states it really isn't simple to distill it down to a common 3 or something of the like. If you look in the individual roles those states correspond to varying stages of the workload. For example, ycsb has a load and a run option so there is separation there that is necessary

I agree that extra steps can be a different state, like the fiod example. It's just the "core" states need to have common namings. It's similar to normal K8s Pods, which can have init steps, but they still must have Running/Failed states.
To me the FIOD states are perfectly fine
Building -> StartingServers -> StartingClient -> Running  -> Complete | Failed
But for instance the hammerdb isn't
Starting -> Running -> DB Workload Complete
Realistically the ask here is that "all benchmark types must implement a Running, Complete, and Failed state. They can implement more than that, but they must implement those"


Test as Role when there are multiple reports

Hi, if you have several reports built on top of a dataset, how do you choose which one comes up when you click on "Test as role" in the Service?  The document says that "You'll see reports that are available for this role," but that really doesn't happen.  Thanks!

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

ID: d5505062-94f3-e15d-a52f-ce1ac7f8cb69
Version Independent ID: 34076b73-0ded-2111-ed44-2a31e07deb53
Content: Row-level security (RLS) with Power BI - Power BI
Content Source: powerbi-docs/admin/service-admin-rls.md
Service: powerbi
Sub-service: powerbi-admin
GitHub Login: @paulinbar
Microsoft Alias: painbar

Hi @asocorro, sorry for VERY long delay in answering you. Since you wrote the document has changed somewhat, and I think it now says "You'll be redirected to the report that was published from Power BI Desktop with this dataset, if it exists". If this doesn't answer your question, let me know. In the meantime I am closing this issue. Thanks!

Hi Paul, the issue is when multiple reports are connected to one dataset.  How do you test dataset roles against each report?  The test feature seems to choose one report at random and there does not seem to be a way to select a particular report.
Thanks,
Adolfo

@.***
Adolfo J. Socorro, Ph.D.
President
eSolutions, Inc.
eSolutionsPR.com http://www.esolutionspr.com/
LinkedIn Profilehttps://www.linkedin.com/in/adolfosocorro/
787-553-3200 (Mobile)
.:. Business Intelligence and SQL Server Solutions .:.
The information contained in this message is a private interchange between the sender and the recipient.
Business ideas, proposals, and other such matters may not be disclosed to third parties without prior mutual consent.
From: Paul Inbar @.>
Sent: Thursday, February 9, 2023 9:59 AM
To: MicrosoftDocs/powerbi-docs @.>
Cc: Adolfo J. Socorro, Ph.D. @.>; Mention @.>
Subject: Re: [MicrosoftDocs/powerbi-docs] Test as Role when there are multiple reports (#3277)
Hi @asocorrohttps://github.com/asocorro, sorry for VERY long delay in answering you. Since you wrote the document has changed somewhat, and I think it now says "You'll be redirected to the report that was published from Power BI Desktop with this dataset, if it exists". If this doesn't answer your question, let me know. In the meantime I am closing this issue. Thanks!
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/powerbi-docs/issues/3277#issuecomment-1424232850, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADAAVNEREZHJVM52LTUTJBTWWTZ3RANCNFSM5DGZC7LQ.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

Hi @asocorro, I think the key is in this sentence: "You'll be redirected to the report that was published from Power BI Desktop with this dataset, if it exists". That means if there are multiple reports, you'll be directed to the one that was published with the dataset, not to subsequent reports that were built on top of the dataset. Now, if the dataset was published without a report, or if the report that the dataset was published with has been deleted, I don't know what the logic is there, but there definitely is no report selector. I think the idea isn't so much to see how the report(s) look with RLS applied, but rather whether the rule is working as you designed it. If you think it would be good to have a "report selector", I would suggest writing this as an idea at https://ideas.powerbi.com.
If you find that the behavior is not as described, i.e. that you aren't being redirected to the report that was published with the dataset, let me know and we'll figure out whether there is a bug, either in the engineering or in the docs.
Thanks!

Perfect, I get it now.
Yes, I’ll post an idea for this.
Thanks for you quick reply!

@.***
Adolfo J. Socorro, Ph.D.
President
eSolutions, Inc.
eSolutionsPR.com http://www.esolutionspr.com/
LinkedIn Profilehttps://www.linkedin.com/in/adolfosocorro/
787-553-3200 (Mobile)
.:. Business Intelligence and SQL Server Solutions .:.
The information contained in this message is a private interchange between the sender and the recipient.
Business ideas, proposals, and other such matters may not be disclosed to third parties without prior mutual consent.
From: Paul Inbar @.>
Sent: Sunday, February 12, 2023 10:10 AM
To: MicrosoftDocs/powerbi-docs @.>
Cc: Adolfo J. Socorro, Ph.D. @.>; Mention @.>
Subject: Re: [MicrosoftDocs/powerbi-docs] Test as Role when there are multiple reports (#3277)
Hi @asocorrohttps://github.com/asocorro, I think the key is in this sentence: "You'll be redirected to the report that was published from Power BI Desktop with this dataset, if it exists". That means if there are multiple reports, you'll be directed to the one that was published with the dataset, not to subsequent reports that were built on top of the dataset. Now, if the dataset was published without a report, or if the report that the dataset was published with has been deleted, I don't know what the logic is there, but there definitely is no report selector. I think the idea isn't so much to see how the report(s) look with RLS applied, but rather whether the rule is working as you designed it. If you think it would be good to have a "report selector", I would suggest writing this as an idea at https://ideas.powerbi.com.
If you find that the behavior is not as described, i.e. that you aren't being redirected to the report that was published with the dataset, let me know and we'll figure out whether there is a bug, either in the engineering or in the docs.
Thanks!
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/powerbi-docs/issues/3277#issuecomment-1427043207, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADAAVNCQBE5H6OXCFMI74QTWXDVLPANCNFSM5DGZC7LQ.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

@asocorro, thank you for hanging in there for a year and a half! :)

Im sure at one point I saw the report list as the dropdown where I can choose which one to test. Today I dont see that as an option anymore, a bit disappointed if that feature has been removed :(


Remove all ada-002 references in code + delete previous collection.

Done in https://github.com/dust-tt/dust/pull/5567.


finder = new AStarGridFinder(GridCell.class) ERROR

Hello, I am trying to use this library for a personal project of mine. Problem is that the line
AStarGridFinder finder = new AStarGridFinder(GridCell.class);
makes the following exception
Exception in thread "main" java.lang.ClassCastException: [Ljava.lang.Object; cannot be cast to [Lorg.xguzm.pathfinding.BHeapNode;
Is there something I might be doing wrong?
Thank you.

Hello, not really.. everything looks good.
Is it possible for you to share the code so that I can take a look at it?


Layered effect: extraction failure (Warn 4: subtype mismatch)

Hi,
We are trying to make a layered effect (named BUG here) and extract it with KreMLin, but we face a Warning 4 (subtype mismatch, Bug_context (a.k.a. Bug_context) vs Bug_context -> Bug_context (a.k.a. Bug_context -> Bug_context)) while extracting.
We wrote a minimal example for our bug (the module Bug here https://gist.github.com/W95Psp/f56882379b756ca3f7511000ec6d0969, for which KreMLin gives the following output https://gist.github.com/W95Psp/d05d0fb84afbb4e4d0b1947441072ca2).
Our goal is to have an effect defined as a "proxy" of STATE, and extract it to C (by reifying BUG to STATE).
Our layered effect has the following representation:
type context = | Context

let pair = context & HS.mem

type pre_t = st_pre_h pair
type post_t (a:Type) = a -> pair -> Type0
type wp_t (a:Type) = wp:(post_t a -> pre_t){
  forall p q. (forall x s. p x s ==> q x s) ==> (forall s. wp p s ==> wp q s)
}

type repr (a:Type) (wp:wp_t a) =
  (c: context) -> STATE a (fun (p: st_post_h _ a) (h0: HS.mem) ->
    wp (fun x (c', h1) ->
         c' == c /\
         ( equal_domains h0 h1
         ) ==> p x h1
       )
       (c, h0)
  )

From KreMLin's output, it seems like functions in our effect BUG are reified weirdly: it seems like the context used in our representation is duplicated in type signature.
We're not too sure it's an actual bug or something we did wrong :)
Thanks for your help!

Thanks for the great bug report, I'll take a look at it. I don't know if we've tested extraction of layered effects yet... @aseemr ?

I have tested extraction of layered effects on some example (e.g. examples/layeredeffects/parsing etc.). I can check the F* output to Kremlin first, and then ping @protz if it needs Kremlin debugging.

Thanks for your answers!
@aseemr: yes, I saw the examples, they were quite helpful :)
I think these used to work, but trying to extract them with F* from master (that is: make extract in examples/layeredeffects, removing the Buffers module from that makefile) now leads to that same Warning 4: see https://gist.github.com/W95Psp/f585e258ab272069f76b4081b1f9af5c#file-log-parsing-examples-without-buffers-L344-L357.
I'm currently building F* at the latest commit from examples/layeredeffects/parsing (that is 07a8583a18e38680743c861574a951b883b2d560), to see if it's a newer F* commit that introduced a bug or something; I'll post an update later today about that.

Many thanks @W95Psp, appreciate your help. The extraction is under CI, so it may have regressed.

Happy to help! :)
So, I've tried several F* version, especially the two following:

F*
Kremlin

https://github.com/FStarLang/FStar/commit/381e2f659f0f73e09dff13fe968eeb61f5449e1f (17 Oct 2019)
https://github.com/FStarLang/kremlin/commit/882534387830a4cc259c1a543e0dfc10dcc70f52

https://github.com/FStarLang/FStar/commit/07a8583a18e38680743c861574a951b883b2d560 (06 Nov 2019)
https://github.com/FStarLang/kremlin/commit/882534387830a4cc259c1a543e0dfc10dcc70f52

Sadly, I still some warning 4 (e.g. https://gist.github.com/W95Psp/2ce8cbfb3aa9e5ebe4617331f863f878 with F* rev. 07a8583a18e38680743c861574a951b883b2d560) about type mismatch.
However, with a recent version of F*, looking again at the output I posted the other day (https://gist.github.com/W95Psp/f585e258ab272069f76b4081b1f9af5c#file-log-parsing-examples-without-buffers-L344-L357), the warning 4 are not about subtype any longer, but : Type annotation is not an lid. What is a lid in F*'s AST?
So I'm not too sure about what to conclude here.

sorry for the delay... I'll try to take a look this week

Hi, did you had some time to look a bit?

Sorry for not looking at it earlier @W95Psp , I just debugged it a little.
I first tried to see if the OCaml code generation is working fine. And I saw that there was an Obj.magic in there, which is already a red flag. When I made the repr type as inline_for_extraction, that Obj.magic went away, so somehow F* is not able to type the OCaml expression appropriately, unless the type is inlined.
I then tried the Kremlin extraction, and still got some errors (subtype mismatch errors). So then I also inlined test and then Kremlin extraction also worked. May be Kremlin is not able to properly determine the arity of this function, cc @msprotz.
I had to update the report a bit to make it work with the latest F* master (there were some changes in how the layered effect is typechecked). Please find the latest defn. below, hopefully this should unblock you. I will try to look into the OCaml extraction issue, while happy to discuss the Kremlin issue with @msprotz .
module Test

open FStar.HyperStack.ST
module U32 = FStar.UInt32
module HS = FStar.HyperStack

inline_for_extraction
type context =
  | Context

let pair = context & HS.mem

inline_for_extraction type pre_t = st_pre_h pair
inline_for_extraction type post_t (a:Type) = a -> pair -> Type0
inline_for_extraction type wp_t (a:Type) = wp:(post_t a -> pre_t){
  forall p q. (forall x s. p x s ==> q x s) ==> (forall s. wp p s ==> wp q s)
}

inline_for_extraction
type repr (a:Type) (wp:wp_t a) =
  c:context -> STATE a (fun (p:st_post_h _ a) (h0:HS.mem) ->
    wp (fun x (c', h1) -> (c' == c /\ equal_domains h0 h1) ==> p x h1) (c, h0))

unfold
let return_wp (#a:Type) (x:a) : wp_t a = fun p s -> p x s

inline_for_extraction
let return (a:Type) (x:a)
  : repr a (return_wp x)
  = fun _ -> x

unfold
let bind_wp (#a:Type) (#b:Type) (wp_f:wp_t a) (wp_g:a -> wp_t b)
  : wp_t b
  = fun p -> wp_f (fun x -> wp_g x p)

inline_for_extraction
let bind (a:Type) (b:Type)
  (wp_f:wp_t a) (wp_g:a -> wp_t b)
  (f:repr a wp_f) (g:(x:a -> repr b (wp_g x)))
  : repr b (bind_wp wp_f wp_g)
  = fun c ->
    let x = f c in
    g x c

inline_for_extraction
let subcomp (a:Type)
  (wp_f:wp_t a) (wp_g:wp_t a)
  (f:repr a wp_f)
  : Pure (repr a wp_g)
      (requires forall p s. wp_g p s ==> wp_f p s)
      (ensures fun _ -> True)
  = f

unfold
let if_then_else_wp (#a:Type) (wp_f wp_g:wp_t a) (p:bool)
  : wp_t a
  = fun post s -> (p ==> wp_f post s) /\ ((~ p) ==> wp_g post s)

inline_for_extraction
let if_then_else (a:Type)
  (wp_f:wp_t a) (wp_g:wp_t a)
  (f:repr a wp_f) (g:repr a wp_g)
  (p:bool)
  : Type
  = repr a (if_then_else_wp wp_f wp_g p)

reifiable reflectable
layered_effect {
  BUG : a:Type -> wp_t a -> Effect
  with
  repr           = repr;
  return         = return;
  bind           = bind;
  subcomp        = subcomp;
  if_then_else   = if_then_else
}

inline_for_extraction noextract
let get_ctx () : BUG context (fun p (c, h) -> p c (c, h))
  = BUG?.reflect (fun c -> c)

//We use ulib/FStar.Monotonic.Pure module to assume the monotonicity of pure wps
//But somehow that doesn't work if I add a call to that lemma inside the defn. of lift_pure
//So adding it here for now
assume WP_mono :
  forall (a:Type) (wp:pure_wp a).
    (forall (p q:pure_post a). (forall x. p x ==> q x) ==> (wp p ==> wp q))

unfold
let lift_pure_wp (#a:Type) (wp:pure_wp a)
  : wp_t a
  = fun p s -> wp (fun x -> p x s)

inline_for_extraction
let lift_pure (a:Type) (wp:pure_wp a) (f:eqtype_as_type unit -> PURE a wp)
  : repr a (lift_pure_wp wp)
  = fun s -> f ()

sub_effect PURE ~> BUG = lift_pure

inline_for_extraction
let test () : BUG U32.t (fun p tup -> p 5ul tup)
  = 5ul

let main ()
  : ST U32.t (fun _ -> True) (fun _ _ _ -> True) =
  let ctx = Context in
  let test_ret = reify (test ()) ctx in
  test_ret

sorry for the delay
@aseemr taking your latest iteration of the example, I ran:
jonathan@absinthe:~/Code/kremlin/test (master) $ fstar.exe --include .cache --codegen OCaml --extract Layered Layered.fst

then here's what I got in Layered.ml:
  26 let (test : unit -> (FStar_UInt32.t, unit) repr) =

but repr is inline_for_extraction, so it should never appear anywhere -- it seems like the normalizer is failing to replace repr with its definition
this is a first issue, I'll keep digging a little bit

this is actually the only issue in the current example, but it's compounded by some other unpleasantness:

when trying to generate a (mostly) first-order kremlin AST, F* looks into the type annotation of a top-level binding to find the types of the arguments and the return type... let's look at the OCaml extraction to figure out how things are going:

let (test : unit -> (FStar_UInt32.t, unit) repr) =
  fun uu____407 -> fun s -> FStar_UInt32.uint_to_t (Prims.of_int (5))

F* is trying to interpret this as a first-order function signature before handing it off to KreMLin; however, the type annotation has one arrow, and the fun has two arguments, so there's a mismatch here... giving rise to this error (an F* error):
Attempting to translate module Layered
Not extracting Layered.test to KreMLin (function type annotation has less arrows than the number of arguments; please mark the return type abbreviation as inline_for_extraction)

however, for some reason, the function is extracted nonetheless

Conclusion: there's a genuine F* normalization bug that fails to inline the repr type in the type annotation of test
Some takeways:

if your layered effect has an arrow type, always make that type inline_for_extraction
the error reporting isn't that great, sorry
maybe we should make that warning ("less arrows than arguments on the function") fatal

I hope this helps, @aseemr let me know if you agree with me that there's a normalizer bug and @W95Psp let me know if you're unblocked once that normalization bug is fixed...

Right, we needed one more call to the normalizer after reifying the computation type. I have fixed it in master, and so, test is now extracted as:
let (test : unit -> context -> FStar_UInt32.t) =
  fun uu____18526 -> fun s -> FStar_UInt32.uint_to_t (Prims.of_int (5))

I am all in favor of making ("less arrows ...") fatal.
Closing the issue. Thanks for your patience @W95Psp , hope this unblocks you, and thanks @msprotz for debugging help.

This is now under regression testing in kremlin

That's great, thank you very much! :)
(I'm not able to test this right now on my code, upgrading F* breaks other stuff -- related to stricter subtyping in layered effect I think)


Improve Yarn support in Nixpkgs

Problem Statement
The current state of Yarn support in Nixpkgs has been... shoddy at best, including a severe lack of documentation, lack of lockfile v2 support, year-old build failures, and (ancient) bugs, including but not limited to #140088, #198312, #184965, #144200, #139227, #284157, most of them have been stale for at least 1–2 years.
This is exacerbated by the fact that the fundamental architecture of yarn2nix has not been altered much since its inclusion in Nixpkgs 3 years ago, with literally only one commit made in the past 12 months, which would be acceptable if it were not for Yarn's rapid development as of late, especially regarding yarn-berry.
The current yarn2nix is awfully underequipped to handle codebases that have since migrated to Yarn 4.x, forcing packagers to use prebuilt upstream .deb packages (e.g. Proton Mail) or maintain a fork of an older branch (e.g. Mastodon), neither of which is at all ideal.
As more and more projects move away from Yarn v1, Nixpkgs needs to be ready to include them, and what we have today simply won't do. What's more worrying, however, is that there also appears to be a lack of people who are knowledgeable enough in Yarn to take on the challenge of updating or replacing yarn2nix with something more modern. As I scanned through the issues and PRs created related to Yarn, there seems to be a kind of aversion or self-professed lack of knowledge from prominent committers regarding Yarn, and I have to admit to being in this camp as well.
IMO, this is very problematic, because it indicates that we might just not have people who can tackle Yarn like people who tackled pnpm support in #290715. If that is the case, what should we do with all the Yarn packages we already have in Nixpkgs? They are out there, and we need to be able to build them.
Proposed Solution
Perhaps we can create a parallel to pnpm_{8,9}.fetchDeps, and add an entirely new implementation of yarn2nix that's designed for yarn-berry/Yarn 4.x. Then, we could have packages that use Yarn 1.x use yarn.mkPackage/fetchDeps and packages that use Yarn 4.x use yarn-berry.mkPackage/fetchDeps. However, the time and energy investment in creating that new implementation should not be underestimated.

The current state of Yarn support in Nixpkgs has been... shoddy at best,

I'd be surprised if anyone disagrees with your statement, even without listing out examples, but as with any open source project with practically no funding, someone needs sufficient time and interest, and they would also need to gain the knowledge to address it. JS ecosystem topics are far more difficult to deal with compared to probably any other language available in nixpkgs, and JS tooling seems to change every other week, hence lack of interest...

... someone needs sufficient time and interest, and they would also need to gain the knowledge to address it... JS tooling seems to change every other week, hence lack of interest...

That right there is really the key problem, isn't it? Unlike something like C, the JS ecosystem is constantly changing, with The Next New Best Thing coming out every couple of months. The reality is that unless we have someone who has domain expertise on each of these new technologies, their support in Nixpkgs would stagnate.

No, the key issue is that this is all volunteer work, while still expecting someone to spend dozens of hours a week maintaining JS tooling for infinite years to come. What I'm getting at is, filing this issue is acknowledging a problem - fine, that's what GH issues are for - but the way the description is phrased, it seems more like venting than a productive conversation. Unless you're willing to step up yourself, and are asking for help to get something going - then the conversation can go a different way.

Yeah, I definitely could get how this can come off as venting, but the fact is that while stdenv might have a single digit of people who know how it works, Yarn currently has 0. Nada. And that's just not adequate at all.
I get that keep reiterating this point isn't very productive, and I'm not exactly interested in tackling Yarn myself since I don't even use Yarn, but this problem deserves to be pointed out and categorized so that we can explain people why it's really hard to package Yarn apps in Nixpkgs right now.

Hey @pluiedev the Yarn situation has improved quiet a bit since #318015 . We have now https://github.com/NixOS/nixpkgs/issues/324246 that tracks the packages that need to transition to the new yarn*Hooks. We also have https://github.com/NixOS/nixpkgs/pull/328544 which is pretty developed that adds yarnInstallHook. You are right though that the fact we distribute the too old Yarn v1 is not that good, but we have https://github.com/NixOS/nixpkgs/issues/254369 for that.

That's wonderful news. Thanks for all that work @doronbehar! ❤


Build: Rename pretest to lint and only run once in CI

This allows us to bump beyond ESLint 2.x in the future since it dropped support for Node <4

lgtm


Main keyboard choosing the wrong one, can't set one manually

Already reported ? *

[X] I have searched the existing open and closed issues.

Regression?
No
System Info and Version
 System/Version info
Hyprland, built from branch  at commit 4520b30d498daca8079365bdb909a8dea38e8d55  (version: bump to 0.44.1).
Date: Wed Oct 9 12:54:39 2024
Tag: v0.44.1, commits: 5309
built against aquamarine 0.4.3

flags: (if any)

System Information:
System name: Linux
Node name: maudasusqcom
Release: 6.11.0-1-x1e-g8844062a2d5e
Version: #1 SMP PREEMPT Thu Sep 26 15:58:16 MSK 2024

GPU information:
qcom,adreno-43050c01

os-release: NAME="Arch Linux ARM"
PRETTY_NAME="Arch Linux ARM"
ID=archarm
ID_LIKE=arch
BUILD_ID=rolling
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://archlinuxarm.org/"
DOCUMENTATION_URL="https://archlinuxarm.org/wiki"
SUPPORT_URL="https://archlinuxarm.org/forum"
BUG_REPORT_URL="https://github.com/archlinuxarm/PKGBUILDs/issues"
LOGO=archlinux-logo

plugins:

======Config-Start======

Config File: /home/maud/.config/hypr/hyprland.conf: Read Succeeded

# #######################################################################################
# AUTOGENERATED HYPR CONFIG.
# PLEASE USE THE CONFIG PROVIDED IN THE GIT REPO /examples/hypr.conf AND EDIT IT,
# OR EDIT THIS ONE ACCORDING TO THE WIKI INSTRUCTIONS.
# #######################################################################################

# This is an example Hyprland config file.
# Refer to the wiki for more information.
# https://wiki.hyprland.org/Configuring/Configuring-Hyprland/

# Please note not all available settings / options are set here.
# For a full list, see the wiki

# You can split this configuration into multiple files
# Create your files separately and then link them to this file like this:
# source = ~/.config/hypr/myColors.conf

################
### MONITORS ###
################

# See https://wiki.hyprland.org/Configuring/Monitors/
monitor=eDP-1,preferred,auto,1.8

###################
### MY PROGRAMS ###
###################

# See https://wiki.hyprland.org/Configuring/Keywords/

# Set programs that you use
$terminal = foot
$menu = tofi-drun | xargs hyprctl dispatch exec --
$browser = firefox
$discord = webcord --enable-features=UseOzonePlatform --ozone-platform=wayland

#################
### AUTOSTART ###
#################

# Autostart necessary processes (like notifications daemons, status bars, etc.)
# Or execute your favorite apps at launch like this:

exec-once = waybar
exec-once = nm-applet
exec-once = blueman-applet

#############################
### ENVIRONMENT VARIABLES ###
#############################

# See https://wiki.hyprland.org/Configuring/Environment-variables/

env = XCURSOR_SIZE,24
env = HYPRCURSOR_SIZE,24

#####################
### LOOK AND FEEL ###
#####################

# Refer to https://wiki.hyprland.org/Configuring/Variables/

# https://wiki.hyprland.org/Configuring/Variables/#general
general {
    gaps_in = 5
    gaps_out = 10

    border_size = 2

    # https://wiki.hyprland.org/Configuring/Variables/#variable-types for info about colors
    col.active_border = rgba(33ccffee)
    col.inactive_border = rgba(595959aa)

    # Set to true enable resizing windows by clicking and dragging on borders and gaps
    resize_on_border = false

    # Please see https://wiki.hyprland.org/Configuring/Tearing/ before you turn this on
    allow_tearing = false

    layout = dwindle
}

# https://wiki.hyprland.org/Configuring/Variables/#decoration
decoration {
    rounding = 5

    # Change transparency of focused and unfocused windows
    active_opacity = 1.0
    inactive_opacity = 1.0

    drop_shadow = false
    shadow_range = 4
    shadow_render_power = 3
    col.shadow = rgba(1a1a1aee)

    # https://wiki.hyprland.org/Configuring/Variables/#blur
    blur {
        enabled = false
        size = 3
        passes = 1

        vibrancy = 0.1696
    }
}

# https://wiki.hyprland.org/Configuring/Variables/#animations
animations {
    enabled = false

    # Default animations, see https://wiki.hyprland.org/Configuring/Animations/ for more

    bezier = myBezier, 0.05, 0.9, 0.1, 1.05

    animation = windows, 1, 7, myBezier
    animation = windowsOut, 1, 7, default, popin 80%
    animation = border, 1, 10, default
    animation = borderangle, 1, 8, default
    animation = fade, 1, 7, default
    animation = workspaces, 1, 6, default
}

# See https://wiki.hyprland.org/Configuring/Dwindle-Layout/ for more
dwindle {
    pseudotile = true # Master switch for pseudotiling. Enabling is bound to mainMod + P in the keybinds section below
    preserve_split = true # You probably want this
}

# See https://wiki.hyprland.org/Configuring/Master-Layout/ for more
master {
    new_status = master
}

# https://wiki.hyprland.org/Configuring/Variables/#misc
misc {
    force_default_wallpaper = 0 # Set to 0 or 1 to disable the anime mascot wallpapers
    disable_hyprland_logo = false # If true disables the random hyprland logo / anime girl background. :(
    disable_splash_rendering = true
}

#############
### INPUT ###
#############

# https://wiki.hyprland.org/Configuring/Variables/#input
input {
    kb_layout = us,us,ru
    kb_variant =,intl,
    kb_model =
    kb_options =
    kb_rules =

    numlock_by_default = true
    accel_profile = flat
    follow_mouse = 1

    sensitivity = 0 # -1.0 - 1.0, 0 means no modification.

    touchpad {
        natural_scroll = false
    }
}

# https://wiki.hyprland.org/Configuring/Variables/#gestures
gestures {
    workspace_swipe = false
}

# Example per-device config
# See https://wiki.hyprland.org/Configuring/Keywords/#per-device-input-configs for more
device {
    name = epic-mouse-v1
    sensitivity = -0.5
}

#device {
#    name = hid-over-i2c-0b05:4543-keyboard
#    enabled = false
#    main = true
#}

###################
### KEYBINDINGS ###
###################

# See https://wiki.hyprland.org/Configuring/Keywords/
$mainMod = CTRL SHIFT # Sets "Windows" key as main modifier

# Example binds, see https://wiki.hyprland.org/Configuring/Binds/ for more
bind = $mainMod, T, exec, $terminal
bind = $mainMod ALT, C, killactive,
bind = $mainMod, K, exit,
#bind = $mainMod, V, togglefloating,
bind = $mainMod, R, exec, $menu
bind = $mainMod, W, exec, $browser
bind = $mainMod, D, exec, $discord
#bind = $mainMod, P, pseudo, # dwindle
#bind = $mainMod, J, togglesplit, # dwindle

# Move focus with mainMod + arrow keys
bind = $mainMod, Z, movefocus, l
bind = $mainMod, X, movefocus, r
bind = $mainMod, A, movefocus, u
bind = $mainMod, S, movefocus, d

# Switch workspaces with mainMod + [0-9]
bind = $mainMod, 1, workspace, 1
bind = $mainMod, 2, workspace, 2
bind = $mainMod, 3, workspace, 3
bind = $mainMod, 4, workspace, 4
bind = $mainMod, 5, workspace, 5
bind = $mainMod, 6, workspace, 6
bind = $mainMod, 7, workspace, 7
bind = $mainMod, 8, workspace, 8
bind = $mainMod, 9, workspace, 9
bind = $mainMod, 0, workspace, 10

# Move active window to a workspace with mainMod + SHIFT + [0-9]
bind = $mainMod ALT, 1, movetoworkspace, 1
bind = $mainMod ALT, 2, movetoworkspace, 2
bind = $mainMod ALT, 3, movetoworkspace, 3
bind = $mainMod ALT, 4, movetoworkspace, 4
bind = $mainMod ALT, 5, movetoworkspace, 5
bind = $mainMod ALT, 6, movetoworkspace, 6
bind = $mainMod ALT, 7, movetoworkspace, 7
bind = $mainMod ALT, 8, movetoworkspace, 8
bind = $mainMod ALT, 9, movetoworkspace, 9
bind = $mainMod ALT, 0, movetoworkspace, 10

# Example special workspace (scratchpad)
#bind = $mainMod, S, togglespecialworkspace, magic
#bind = $mainMod SHIFT, S, movetoworkspace, special:magic

# Scroll through existing workspaces with mainMod + scroll
bind = $mainMod, mouse_down, workspace, e+1
bind = $mainMod, mouse_up, workspace, e-1

# Move/resize windows with mainMod + LMB/RMB and dragging
bindm = $mainMod, mouse:272, movewindow
bindm = $mainMod, mouse:273, resizewindow

# Laptop multimedia keys for volume and LCD brightness
bindel = ,XF86AudioRaiseVolume, exec, wpctl set-volume @DEFAULT_AUDIO_SINK@ 5%+
bindel = ,XF86AudioLowerVolume, exec, wpctl set-volume @DEFAULT_AUDIO_SINK@ 5%-
bindel = ,XF86AudioMute, exec, wpctl set-mute @DEFAULT_AUDIO_SINK@ toggle
bindel = ,XF86AudioMicMute, exec, wpctl set-mute @DEFAULT_AUDIO_SOURCE@ toggle
bindel = ,XF86MonBrightnessUp, exec, brightnessctl s 10%+
bindel = ,XF86MonBrightnessDown, exec, brightnessctl s 10%-

bind = , Print, exec, grimblast save output $HOME/pictures/$(date +%Y_%m_%d__%H_%M_%S).png
bind = $mainMod, Print, exec, grimblast save area $HOME/pictures/$(date +%Y_%m_%d__%H_%M_%S).png
bind = $mainMod, SPACE, exec, hyprctl switchxkblayout keyd-virtual-keyboard next; hyprctl notify 5 2000 0 "keyboard layout switched"

# Requires playerctl
bindl = , XF86AudioNext, exec, playerctl next
bindl = , XF86AudioPause, exec, playerctl play-pause
bindl = , XF86AudioPlay, exec, playerctl play-pause
bindl = , XF86AudioPrev, exec, playerctl previous

##############################
### WINDOWS AND WORKSPACES ###
##############################

# See https://wiki.hyprland.org/Configuring/Window-Rules/ for more
# See https://wiki.hyprland.org/Configuring/Workspace-Rules/ for workspace rules

# Example windowrule v1
# windowrule = float, ^(kitty)$

# Example windowrule v2
# windowrulev2 = float,class:^(kitty)$,title:^(kitty)$

# Ignore maximize requests from apps. You'll probably like this.
windowrulev2 = suppressevent maximize, class:.*

# Fix some dragging issues with XWayland
windowrulev2 = nofocus,class:^$,title:^$,xwayland:1,floating:1,fullscreen:0,pinned:0

======Config-End========

Description
The main keyboard is hid-over-i2c-0b05:4543-keyboard
instead of keyd-virtual-keyboard
I've had issues on other laptops aswell where if I plug in a usb keyboard it switches from keyd-virtual-keyboard to the usb keyboard, causing my layout switching to stop working and my keyd keymap to stop working.
I'm not sure if there already is something like this (couldn't find it on the wiki at least) but it would be nice to be able to configure something like:
device {
    name = keyd-virtual-keyboard
    main = true
}

How to reproduce
I don't know if there is a very easy way to reproduce this, it only seems to be this bad on this laptop, on other ones it mostly works fine
Crash reports, logs, images, videos
output of hyprctl devices
mice:
	Mouse at aaaad5446ee0:
		hid-over-i2c-093a:3016-mouse
			default speed: 0.00000
	Mouse at aaaad64a6e70:
		hid-over-i2c-093a:3016-touchpad
			default speed: 0.00000
	Mouse at aaaad61b49d0:
		hid-over-i2c-0b05:4543-keyboard-1
			default speed: 0.00000
	Mouse at aaaad67a5130:
		keyd-virtual-pointer
			default speed: 0.00000

Keyboards:
	Keyboard at aaaad671ef10:
		hid-over-i2c-0b05:4543-keyboard
			rules: r "", m "", l "us,us,ru", v ",intl,", o ""
			active keymap: English (US)
			main: yes
	Keyboard at aaaad61b4d70:
		pmic_pwrkey
			rules: r "", m "", l "us,us,ru", v ",intl,", o ""
			active keymap: English (US)
			main: no
	Keyboard at aaaad65be9c0:
		keyd-virtual-keyboard
			rules: r "", m "", l "us,us,ru", v ",intl,", o ""
			active keymap: English (US)
			main: no

Tablets:

Touch:

Switches:

patch.txt
try this patch. device option main

I'm running into some issues unfortunately, the system on which this is happening seems to be having some graphics issues, so I can't even run hyprland on it right now (its one of the new qualcomm snapdragon powered systems so everything is still a bit eh for now)
I did try it out on another system by simply hooking up a usb keyboard and trying to force it to that one, but was not successful sadly, main stayed the same, tried main = true and main = 1, restarted the WM, but nothing.
I will try to do some more testing debugging when I get the time


true && false String constant

create true && false String constant in order to re use variable, and make the code more readable

Coverage remained the same at 94.957% when pulling be5c63a4cdd0538ec72fe7cb15448c048603ea4b on arturobernalg:feature/boolean_string_const into 5689c91cf2a3a27f0a3a8a362857f2cf0919d4f6 on apache:master.


qpdfview opening delay

Hey,
I'm using Linux Mint Mate 20.1 and whenever I open qpdfview it is very delayed (~30sec.).
That occurs when I double click on a pdf file from the file manager, or when opening qpdfview without opening a pdf.
When qpdf is already open and I open another pdf via Ctrl + O or Ctrl +T it is not delayed.
 You can find information about qpdfview at https://launchpad.net/qpdfview. Sorry for the confusion.

Hello. qpdfview is an entirely unrelated project from qpdf. You can find information about qpdfview at https://launchpad.net/qpdfview. Sorry for the confusion.


EntityManagers

Chapter 7 Entity Managers and Persistence Contexts

Container-managed entity managers and Application-managed entity managers
JTA and RESOURCE_LOCAL

For the moment, I use an application-managed entity manager.


abc import function unavailable

Checks

[x] I have mentioned my abc version in the issue, if applicable.
[x] This issue is not a duplicate.
[x] This issue has a description.

@sgabbiEWF Can you please add the details?

Version: 0.10.1
I used docker to download the latest image. But when i use abc --help I do not see 'import' as one of the commands available.
Anyone else has this issue?

@siddharthlatest: Sorry I was still drafting the issue..

@sgabbiEWF This has been fixed now.


Add Support for PHP 7.4

PHP 7.4 ternary operations works differently (ie. more explicit) with brackets.

Brackets are inserted wrongly as far as I can see. This seems like a harmful thing to do. Why would you insert closing brackets halfway the ternary operation? Clearly they should be around the whole ternary operator in this visibly formatted expression.

@muisit I'm using PHP 7.4 and trying to fix this issue. If you feel i am wrong, then i hope you can help fix it.

As I wrote, the closing parenthesis should be at the end of the expression, not halfway the ternary operator. You have a double closing parenthesis at line 115. Remove one and add it at the very end of that same line (but obviously before the semi-colon...).
Clearly the isset condition check belongs to the expression on that whole line. Where you added the closing parenthesis makes absolutely no sense.

do you invite PR?


Sporadic integration test failure due to KeyError: '/dev/xvda'

The test to fail is AWSStaticAutoscaleTest.testAutoScale.
Example of the trace
Traceback (most recent call last):
  File "/mnt/ephemeral/workspace/toil-pull-request-integration-tests/src/toil/test/provisioners/aws/awsProvisionerTest.py", line 249, in testAutoScale
    self._test(spotInstances=False)
  File "/mnt/ephemeral/workspace/toil-pull-request-integration-tests/src/toil/test/provisioners/aws/awsProvisionerTest.py", line 128, in _test
    self.launchCluster()
  File "/mnt/ephemeral/workspace/toil-pull-request-integration-tests/src/toil/test/provisioners/aws/awsProvisionerTest.py", line 278, in launchCluster
    rootBlockDevice = workers[0].block_device_mapping["/dev/xvda"]
KeyError: '/dev/xvda'

This is happening across multiple branches. This was most likely introduced in #1572 by not waiting for the worker to be running before checking if the volume is mounted.

@joelarmstrong reports still getting this error and suggests a fix. I will call worker.update() up renew the block_device_mapping.


$elemMatch is not reset correctly

Code
const sift = require('sift');

const test = sift({
  groups: {
    $elemMatch: { id: 1, status: 'review' }
  }
});

const items = [
  { groups: [{ id: 1, status: 'review' }] },
  { groups: [{ id: 1, status: 'done' }] },
];

console.log(0, 'expects true', test(items[0]));
console.log(1, 'expects false', test(items[1])); // returns true!!

Explanation
When $elemMatch evaluates to true it will never evaluate to false anymore!!! This is because $ElemMatch  class incorrectly overrides reset method of BaseOperation.
Possible fix
So, reset method of $ElemMatch should be this:
  reset() {
    super.reset(); // <--- added this line
    this._queryOperation.reset();
  }

Importance
It's a critical issue for casl v4, so if you are OK with the suggested fix, I'll send a PR. Related issue https://github.com/stalniy/casl/issues/392

@crcn ping

Fixed! Should be up on NPM as 13.3.4.


onStopTrackingTouch , onStartTrackingTouch

i need onStopTrackingTouch overreade in setOnProgressChangedListener like seekbar , and onStartTrackingTouch

I have added a new Listener by the name OnCrollerChangeListener very similar to the seekbar's listener. It has the required methods. See README for further details.


winget list --source winget should display packages from that source only

Brief description of your issue
When executing winget list --source winget a list of all packages is returned. Even ones that aren't installed via (or from) winget.
Another thing I just noticed writing this: some packages (i.e. "SomePythonThings.ElevenClock" which I just installed using winget) don't even show winget as their source. winget export -o winget.txt also shows a warning, that the package isn't available in any source.
Steps to reproduce
Run winget list --source winget
Expected behavior
A list of packages installed via winget / from the winget repository.
Actual behavior
A list of all applications installed on the system no matter where they came from.
Environment
Windows Package Manager v1.1.12663
Copyright (c) Microsoft Corporation. Alle Rechte vorbehalten.

Windows: Windows.Desktop v10.0.22000.258
Paket: Microsoft.DesktopAppInstaller v1.16.12663.0

Duplicate of #1155


creat icon

i want to add icon in jpanel java swing and thank you

i want to add icon in jpanel java swing and thank you

@marroukihatem seems you have created your PR from the wrong branch... Create a new branch for your change of the izpack:master first and redo your change there. Then create a new PR.


Proper Exit?

How is it expected to close the program on CLI when done?
Closing via Ctrl+c throws a wall of errors.
This information is notably missing from the readme.

How is it expected to close the program on CLI when done?
Closing via Ctrl+c throws a wall of errors.
This information is notably missing from the readme.

Typing 'quit' or 'exit' and then hitting enter will exit the program via the CLI and wrapper.

This information is notably missing from the readme.

Noted. Will add clear instructions on how to exit the program in the ReadMe for clarity and ease of use.
Thanks Az!


Events are not consumed by the Journey

Hi,
Here is the basic Journey setup:

After that:
curl -X "POST" "https://XXXX.com/api/client/events" \
     -H 'Authorization: Bearer ZZZZZ' \
     -H 'Accept: application/json' \
     -H 'Content-Type: application/json' \
     -d $'[
  {
    "name": "user_created",
    "external_id": "06ca2362-7950-4a2a-9a3d-142ea6bd626c"
  }
]'

And nothing happens - the Journey is not triggered... This event is, however, visible on the User:

There are errors in the logs either.

Any ideas? Maybe you can suggest the steps to debug, as currently there are 0 logs or errors...?

@andreieuganox were you checking out the master branch and running it from source per chance? It looks like a previous commit regressed some journey related processes. As far as I can tell this did not affect any releases so none of the docker images were affected but want to confirm. Regardless both the master branch and the latest tag should be up to date now.

Running from docker image, latest Release (1.1.15 if not mistaken, sorry have no laptop now)
Can roll it back one version and check what happens. Can do in around 3 hours, will report back when tested.


LabelSeries with Stacked Vertical Bar Series

Hi, I have some issues with labelSeries when using it with a vertical Bar Series (so stackby="y").
The label  seem to always go way above the bars like that:

I've done a codepen to show my problem.
https://codesandbox.io/s/5kx21nk77l
Is there a way to get around the problem or maybe i'm doing this the wrong way (i used this tutorial ) ?
I've tried negative values and reverse the labelSeries position in the XYplot but i don't have consistent result ...

Hey @tmessaoudi,
I think you are doing what is fine, but you high a good point: stack should only stack like series. It doesn't make sense to stack labels and bars. I would welcome a PR addressing this!
As a workaround you can just put one XYPlot on top of your initial one and put all your labels and stuff in there. Alternatively you can stack the bars yourself (and not use the stack attribute at all) by using the y0 and y property , something like the usage here https://github.com/uber/react-vis/blob/master/showcase/plot/difference-chart.js

hi @mcnuttandrew ,
Got the same scenario in my project, where I've clustered stacked bars and I want to add label for each bar.
I'm wondering what is the correct solution here.
(Got some SW Dev exp, but I'm really new to React/JS/Web Dev)
from my prespective, I think that the best solution would be to add the 'cluster' attribute to Label series.
the problem with this solution is that the user will have to create the Labels series and Bars series in the same order. Otherwise I think that the calculation of stacked series will result in incorrect placing of labels and bars(i think it happens at getStackedData(), right?)
another solution would be to add 'title' or 'content' for Bar Series and to control its position within the Bar.
I guess you don't want to add more and more attributes so the components won't start to look like a giant dirty monsters, but this is what I came up with...
Do you have any other suggestions?

I still think the right long term solution is to make stack only affect common types of series, eg bars only stack with bars labels stack with labels.
Another work around would be to use the CustomSVGSeries and make each placed  contain a block and label. This is pretty close to the pattern you see deployed all over pure d3 visualizations

I still think the right long term solution is to make stack only affect common types of series, eg bars only stack with bars labels stack with labels.

Sure, but it means that:

'cluster' attribute needs to part of Label series, otherwise the stacking will be done on the same "bin"
If a user wants to add bars and to attach labels to them, he would have to create the data for the labels in the same order, the bars were created otherwise some labels would be misplaced.

p.s. - where the shift across x axis takes place? I mean how the clustering happens so that stacked bars of the same cluster are placed next to each other?


114 copy in numpyencoder

Pull Request Test Coverage Report for Build<PHONE_NUMBER>2
Details

11 of 19 (57.89%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-4.2%) to 84.034%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

cvx/json/numpyencoder.py
10
18
55.56%

Totals

Change from base Build<PHONE_NUMBER>1:
-4.2%

Covered Lines:
100

Relevant Lines:
119

💛  - Coveralls


Home Assistant App for MacOS, unsupported browser

The card is not loaded in the MacOS Home Assistant App. Unsupported browser. Any fix?

#5 #76 #248 #344


how to test the model??????

Hello sir, how are you doing, i wanted to ask you the following please : i wanted to test the work you have done, but unfortunately i can't load the file  'model.pth' after the model training is over  so i can execute my images, how can i do that please? hope someone can help me.
greetings.

Hello, have you solved this problem now? I would be very grateful if you could reply to me!

Hello sir, how are you doing, i wanted to ask you the following please : i wanted to test the work you have done, but unfortunately i can't load the file 'model.pth' after the model training is over so i can execute my images, how can i do that please? hope someone can help me. greetings.

Hello, have you solved this problem now? I would be very grateful if you could reply to me!


Getting path issue when trying to load language model

When running the processing using  the language page enricher which I do via adding
    - func: detect_lang_whole_page_enricher
      model: fasttext

to my processing yaml
I get
(process_local_chunk pid=16263, ip=<IP_ADDRESS>)     return FastText(modelpath=path)
(process_local_chunk pid=16263, ip=<IP_ADDRESS>)   File "/home/ubuntu/miniconda3/envs/rapids-22.06/lib/python3.9/site-packages/fasttext/FastText.py", line 93, in init
(process_local_chunk pid=16263, ip=<IP_ADDRESS>)     self.f.loadModel(model_path)
(process_local_chunk pid=16263, ip=<IP_ADDRESS>) ValueError: /tmp/ray/session_2024-07-29_22-57-54_316975_7231/runtime_resources/working_dir_files/_ray_pkg_c26c2eecee54cf21/baselines/mappers/enrichers/language_id_enrichment_models/lid.176.bin cannot be opened for loading!

I specifically made sure to put the model in baselines/mappers/enrichers/language_id_enrichment_models/ before running the script but it doesn't seem to be copied over to the Ray directory when running.
The model expects a specific path when we load. Perhaps it might be better to download the model if it's not there. Can put up a PR if helpful

do you mind trying with the latest version of process.py that just got merged? would allow you to not have to use the ray working_dir

Marking as closed for now. Please reopen if the issue is not fixed by the latest version of the code.


fact(main_manager): allow circular manager dependencies

This reworks dependency management and allows managers to access each other without passing through constructors and allows circular dependency.

Does this prevent webpack/esbuild minifiers from working?

Does this prevent webpack/esbuild minifiers from working?

No idea but I'd assume not? It's just how the managers refer to each other.


ThingML == should compile to == for primitive types and .equals for object

@oysteinh I should be able to fix that quite rapidly, but we decided not to make any new release of the ThingML plugin before Feb 22nd. It is likely that the fix will be available for update from Eclipse shortly after this date (as well as some other improvements).


Redaction ux improvements

This PR contains several smaller UI/UX improvements:

Fixes sporadic white lines in the ImageData table header
ImageData table remains visible during redaction
Alters hover color on 'DE-PHI' button to not look disabled
Resets progress counter to 0 on new redaction
Redaction snackbar closes for new workflow (both new redaction and new input directory selection)
Resets tags when new input directory is selected

One future change would be that when a new input directory is selected, we currently don't replace the table until it is parsed and there isn't any feedback that we are working on the new table.  Maybe the extant table should become greyed out or vanish or there should be some other indicator.


Factfinder

Factfinder was replaced by https://data.census.gov

Factfinder reference removed and replaced by data.census.gov in the current workshop materials.