fix : for issue 606 : exclude stale containers from counting and add remove add remove staled work containers function in ProcessingShard

Description...
This is the fix for https://github.com/confluentinc/parallel-consumer/issues/606
The issue happens when rebalancing and partitions got re-assigned:

The workcontainer will be marked as stale container since its epoch is mismatch between partitionsAssignmentEpoch of PartitionState and epoch from WorkContainer
https://github.com/confluentinc/parallel-consumer/blob/master/parallel-consumer-core/src/main/java/io/confluent/parallelconsumer/state/PartitionState.java#L655

inFlight of WorkContainer will be stay false since they will be filtered to be selected in runUserFunction in AbstractParallelEoSStreamProcessor
https://github.com/confluentinc/parallel-consumer/blob/master/parallel-consumer-core/src/main/java/io/confluent/parallelconsumer/internal/AbstractParallelEoSStreamProcessor.java#L1256

The consumer paused will be triggered since if the number of staled messages are big enough isSufficientlyLoaded  in WorkManager will return true.
https://github.com/confluentinc/parallel-consumer/blob/master/parallel-consumer-core/src/main/java/io/confluent/parallelconsumer/state/WorkManager.java#L232C1-L232C1
https://github.com/confluentinc/parallel-consumer/blob/master/parallel-consumer-core/src/main/java/io/confluent/parallelconsumer/state/WorkContainer.java#L230

Since the staled workcontainer can never be selected to run user function. The consumer will be paused infinitely until next-time rebalancing
https://github.com/confluentinc/parallel-consumer/blob/master/parallel-consumer-core/src/main/java/io/confluent/parallelconsumer/internal/BrokerPollSystem.java#L304

Meanwhile, while getWorkIfAvailable in WorkManager will try to extract active workcontainers, but since the staled containers have the lower offsets, they will be extracted always earlier than the new ones. (if the same partitions have been assigned to the consumer again). Then the new records have no chances to be processed since the it will break out of the while loop.
https://github.com/confluentinc/parallel-consumer/blob/master/parallel-consumer-core/src/main/java/io/confluent/parallelconsumer/state/ProcessingShard.java#L134

The proposed solution:

We should exclude those stale work containers from calculation
remove staled work containers from shard when partition assigned and revoke happen

Checklist

[ ] Documentation (if applicable)
[x] Changelog

@eddyv Thanks a lot for your quick response. Actually we are kind of blocked by this issue, when could we expect this fix merged?
And when could we have a snapshot version or release version to use?

Thank you!

@eddyv  Thank you so much for your help here! We are rolling out parallel consumer to company wide usage, this fix is very crucial for us.
Thanks again and looking forward to more interaction in the future.


very long search time >30 sec for canned search

I am trying to use your canned example class=Actinopterygii and it takes very long , already > 1 minute
https://ocellus.info/?resource=images&class=Actinopterygii

this should be very fast now. In fact, it is very fast now. Please check and let me know if you experience the slowness


SMP Mix frontend changes

This is a subtask of #239
Do frontend changes required to get the backend api working and integrated with frontend.

Already implemented!


Redesign shadows

The Infima shadows are not very convenient to use currently.
The lw shadow is not very visible, and the difference between --lw and --md is huge:

In practice, Docusaurus almost only use --lw, so it seems safe to re-adjust other shadows
Good resource on shadow design:

https://www.joshwcomeau.com/css/designing-shadows/
https://twitter.com/JoshWComeau/status/1458813277056688139

We also need a way to highlight surfaces (like cards) on dark mode, as dark shadows are not very visible.
Using a scale anim does not always look good, but using a lighter background is quite common.

See also Material design dark mode guidelines: https://material.io/design/color/dark-theme.html#properties


Update docs for capability rework

Mostly adapted from the blog post, but keeping some of the old content where that made sense.
Beyond the two main changed files, I also fixed references to capabilities elsewhere. Some of the other pages will still need an update, but at least everything related to caps should be clean now.

Preview URL: https://pr-34.neoforged-docs-previews.pages.dev

Looks good to me overall, just a few minor points

It might be worth mentioning that the fluid capability for items is slightly special due to the way buckets hold fluids
The remark regarding why block caps are looked up from the level now should explicitly mention why (i.e. that blocks without BEs can have caps now as well)
If the holder of a data attachment requires it, is it automatically marked dirty when a non-existent attachment is retrieved and therefore default-initialized?

Other than that: :shipit:


Updated tessellation text interface

Examining the tessellation code I realized there was a built-in toggle for the wireframe which is hidden due to lack of text overlayed so quickly added it.

Thx 👍


Opnav cleanup

Summary

This PR addresses Jira tickets CISLUNAR-105, CISLUNAR-106, CISLUNAR-107, CISLUNAR-109, CISLUNAR-110, CISLUNAR-111
This PR makes many quality of life changes to the opnav module, most important of which is the refactoring of the observe functions defined in opnav.py into their own module, as well as making the data flow more understandable. Ephemeris code was also resurrected and changed to use unix timestamps instead of datetimes.
Testing

Code was tested using the test_pipeline.py script and was ensured that the results were the same. Additionally, ephemerides using unix timestamps were compared against the datetime results for similarity (there was some difference presumably due to the change in timestamp units).
Notes

@adamrnasir , @andxu282 :

Make sure you understand the data flow in opnav.py and observe_functions.py
I think find_algos utils file CISLUNAR-110 should just be tiled_remap.py which is already in find_algos/. Use functions in here from now on.
There are still some files that need to be removed from the ignore section of pyrightconfig.json CISLUNAR-112. Once these files are entirely tested, we can look at resolving the pyright errors.

Comments

[x] Add an x between the brackets if you commented your code well!

What does the ephemeris code do exactly?

We need to know where the Earth/Moon/Sun are in space at the time of an opnav run in order for us to "triangulate" where we are with respect to those bodies. The ephemeris codes calls astropy to calculate the location of these bodies at a point in time. Knowing the angular separation between the bodies is not enough information to determine where our spacecraft are - we also need to know the positions of these bodies in order to "invert" the system and figure out where we are in it. I'm honestly not sure where this "inversion" occurs (is it part of the Kalman filer?).
It's situations like this where solid, high-level documentation is really valuable!

What does the ephemeris code do exactly?

We need to know where the Earth/Moon/Sun are in space at the time of an opnav run in order for us to "triangulate" where we are with respect to those bodies. The ephemeris codes calls astropy to calculate the location of these bodies at a point in time. Knowing the angular separation between the bodies is not enough information to determine where our spacecraft are - we also need to know the positions of these bodies in order to "invert" the system and figure out where we are in it. I'm honestly not sure where this "inversion" occurs (is it part of the Kalman filer?).
It's situations like this where solid, high-level documentation is really valuable!

It's worth noting that we only get the ephemerides for the Moon and Sun because our measurements are taken in the ECI (Earth Centered Intertial) frame


Where is the source code for the NuGet package?

I have an interest in interacting with Gitea for one of my projects, and I stumbled across your NuGet package:
https://www.nuget.org/packages/Gitea.NET
And I was curious about taking it for a spin, however, when I came over to this source code repository, I found that there wasn't any 😄
Is there a reason for this?

Hi @gep13,
The source code itself is generated through the open api generator from Giteas OpenAPI definition.
This package was mainly made for a PoC for building DevOps Pipelines with nuke.build and Gitea.
I'll share the source code to generate the clients later.

@xTamasu said...
I'll share the source code to generate the clients later.

That would be great! Thank you!


Updating Adwords to v201806

Hi @mkmayur19,
thanks for your contribution and sorry for taking so long to merge.
I'll build and release a new version asap.


Produce logs during test runs (integration, smoke) and publish as artefacts

This PR fixes https://github.com/microsoft/vscode/issues/125815

As part of this PR, could we also remove these stream forwarders and let those go into downloadable assets instead?

https://github.com/microsoft/vscode/blob/5aaa5d424fbfb77a1545a9aa6be93c6d77bd70a8/test/automation/src/playwrightDriver.ts/#L121-L122
https://github.com/microsoft/vscode/blob/5aaa5d424fbfb77a1545a9aa6be93c6d77bd70a8/test/integration/browser/src/index.ts/#L113-L117

They currently pollute the build output:


Neos 7.x compatibility

Currently – as per composer.json – this package is not compatible with Neos 7.
Therefore we need to check / fix / update it.

I just added a PR https://github.com/code-q-web-factory/neos-passwordprotectedcontent/pull/3

Thanks! Tested, everything works. Just did a new release.

Thanks! Tested, everything works. Just did a new release.


Update scoreboard

Hello, Danijar.
Thanks for developing such a comprehensive and challenging environment.
I kindly request an update to the scoreboard, reflecting my recent paper accepted at NeurIPS.

Thanks for the PR and congrats on the paper! Do I understand correctly that your method is using underlying information about the accomplished achievements from the environment that are not normally exposed to the agent via the observation space? In that case, I would be happy to add your method to the External Knowledge scoreboard and also add your impressive plain PPO baseline to the Reinforcement Learning scoreboard.

Thank you for your response! To clarify further, my method relies solely on temporal information about when a new achievement is unlocked, identifiable directly from the reward signal (when the reward is greater than 0.1). However, considering there will be another auxiliary rewards and that isolating the achievement reward signals requires the knowledge of the reward structure, I agree with your suggestion to categorize my method under the External Knowledge scoreboard. Also, I am pleased to have the PPO baseline included on the Reinforcement Learning scoreboard. I have created a new commit to reflect this update.
Thanks again for your amazing work on Crafter and Dreamer.

Awesome, thanks!


Adding nonblocking network client to ReplicaThread

Passing a network client to ReplicaThreaad.

Codecov Report
Base: 14.81% // Head: 14.81% // Decreases project coverage by -0.00% :warning:

Coverage data is based on head (a1ae10c) compared to base (88a2053).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #2313      +/-   ##
============================================
- Coverage     14.81%   14.81%   -0.01%
  Complexity     2365     2365
============================================
  Files           757      757
  Lines         58241    58249       +8
  Branches       7152     7153       +1
============================================
  Hits           8628     8628
- Misses        49097    49105       +8
  Partials        516      516

Impacted Files
Coverage Δ

...va/com/github/ambry/replication/ReplicaThread.java
0.00% <0.00%> (ø)

...om/github/ambry/replication/ReplicationEngine.java
0.00% <0.00%> (ø)

...m/github/ambry/replication/ReplicationManager.java
0.00% <0.00%> (ø)

...main/java/com/github/ambry/server/AmbryServer.java
0.00% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


[YUNIKORN-1337] Application state stuck in Accepted when placeholders are running and the job is deleted

What is this PR for?
YUNIKORN-1205 introduced a bug which causes an Application to stuck in "Accepted" state when the placeholders are running and the job is deleted.
What type of PR is it?

[x] - Bug Fix
[ ] - Improvement
[ ] - Feature
[ ] - Documentation
[ ] - Hot Fix
[ ] - Refactoring

Todos

[ ] - Task

What is the Jira issue?
https://issues.apache.org/jira/browse/YUNIKORN-1337
How should this be tested?
Screenshots (if appropriate)
Questions:

[ ] - The licenses files need update.
[ ] - There is breaking changes for older versions.
[ ] - It needs documentation.

codecov/patch can be ignored


vue/valid-v-else false positive with nested element and text node

I have a v-if with an element and a text node inside, and it's causing a false positive for vue/valid-v-else.
Here's my minimal repro:
<template lang="pug">
div
  section(v-if="true")
    div
      div
    | text
  section(v-else)
    div Checking dependencies...
  footer
</template>

<script lang="ts">
export default {}
</script>

Here are the lint errors:
  7:11  error  'v-else' directives require being preceded by the element which has a 'v-if' or 'v-else-if' directive  vue/valid-v-else
  9:3   error  The template root requires exactly one element                                                         vue/no-multiple-template-root

I tried using the eslint-plugin-vue demo and wasn't able to reproduce there, so I'm guessing the issue is from this plugin?

Variations:
<template lang="pug">
div
  div
    div
      div
    | text
  div(v-if="true")
  div(v-else)
</template>

<script lang="ts">
export default {}
</script>

  8:3  error  The template root requires exactly one element  vue/no-multiple-template-root

<template lang="pug">
div
  page-header
    template
      div
        div
      | TEXT

    template(#custom)
</template>

<script lang="ts">
export default {}
</script>

  9:14  error  'v-slot' directive must be owned by a custom element, but 'div' is not  vue/valid-v-slot

Pipes after an outdent closing parent elements early has been fixed in 0.6.2.
The patch also fixes this issue.


Access violation when using registry.clear()

Hi there,
I am using entt 3.13.1 from vcpkg with MSVC 19.37.32825.0 and I get sometimes an access violation when using .clear():
registry.clear<Component>();

Unfortunately, it only happens sometimes and I couldn't reproduce it yet with a minimal example. It runs thousands of times without a problem and suddenly crashes.
According to debug info, it fails in sparse_set.hpp, line 258:
packed[static_cast<size_type>(entt)] = packed.back();

I use the vanilla entt types and pools without any specific customisation, etc.
I am trying to reduce it down but it is quite difficult. If you have any ideas or tips, I would be very happy :-)

Yeah, a repro would help a lot, you know.
Judging by the error, it looks as if you were using a moved from storage but it's hard to confirm it.
Do you happen to move the registry in your codebase? You can try to redefine its move ctor/op and assert in there to start with.
Can you provide more details on how you create and use these storage instances? It could also happen because of a dangling pointer due to a concurrent access to the same storage but it would be gross and easy to spot probably.
Let me know if you have more details to share. 👍

Thank you for your response! I don't think I move the registry anywhere but I will check later by using your assert method.
I create and clear the storage like this:
registry.clear<Renderable>();

std::vector<entt::entity> layer_entities;
for (auto entity: layer_entities)
{
  if (not registry.valid(entity) or not registry.all_of<Position, Drawable>(entity))
    continue;

  registry.emplace<Renderable>(entity, ...);
}

Then I use it via registry.view<...>().each(...) at many places in my codebase, e.g.
registry.view<Renderable, Drawable>().each(
[](auto entity, auto &renderable, auto &drawable){
  // do something ...
  // but neither create or remove any components from the registry
});

Side note:

I create and clear the storage like this:

I suggest creating a view<entt::get_t<Position, Drawable>> and use it with your if. It's much faster because it avoids the storage lookup otherwise performed by the registry. Similarly:
registry.emplace<Renderable>(entity, ...);

Get the storage once and use it again and again as in storage.emplace(entity). Same reason as above. In a tight loop, it can help. 👍
As for your problem, do you happen to use a registry from multiple threads? Consider that pool creation isn't thread safe and could quickly lead to UB if you don't create pools in a warm-up tick or function.
If it's not the case, well, I'm trying to think aloud and guess since I don't have a repro. I hope it helps. 👍

I suggest creating a view<entt::get_t<Position, Drawable>> and use it with your if. It's much faster because it avoids the storage > lookup otherwise performed by the registry.

Oh, I didn't know that. So i could write this?
auto storage = world.view<entt::get_t<CT::Position, CT::DrawableInfo>>();
for (auto entity: entities) {
    if (not storage.contains(entity))
        continue;
    // ...
}

As for your problem, do you happen to use a registry from multiple threads? Consider that pool creation isn't thread safe and
could quickly lead to UB if you don't create pools in a warm-up tick or function.
If it's not the case, well, I'm trying to think aloud and guess since I don't have a repro. I hope it helps. 👍

Just to make sure, I understand you correctly. I am not allowed (or rather I shouldn't) to do things like this:
// Create a new component while iterating over the same component pool:
auto view = registry.view<Position>();
std::for_each(std::execution::par_unseq, view.begin(), view.end(),
  [&registry](auto entity, auto &position){
    // DON'T DO THIS
    auto new_entity = registry.create();
    registry.emplace<Renderable>(new_entity);
  });

Oh, I didn't know that. So i could write this?
auto storage = registry.view<entt::get_t<Position, Drawable>>();
for (auto entity: entities) {
    if (not storage.contains(entity))
        continue;
    // ...
}

Yeah, exactly. The view doesn't have to lookup the storage, so the check is faster overall and the lookup costs don't sum up.

Just to make sure, I understand you correctly. I am not allowed to (or rather I shouldn't) do things like this:

Yes and no.
Of course, creating instances of the same component type from different threads is risky. It's as if you were pushing at the end of a vector from different threads. Bad things will happen for sure sooner or later. 🙂
What I mean is this though:
thread 1: registry.emplace<T>();
thread 2: registry.emplace<U>();

This is ok in general but only if the pools already exist, so only after the first time.
If you're in doubt, I suggest running a single threaded warmup tick or forcing pool creation on the main thread before spawning other threads. All you have to do is registry.storage<T>() on a non-const registry.
That said, I don't think this is your issue actually. You said that it runs fine a thousand times, then it breaks, right?
It's hard to tell you the root cause without a repro. Is your project public? Do you have a more detailed stack trace?
At first glance, it really seems as if the storage was invalidated and you were accessing a dangling reference but 🤷♂ cannot confirm it without debugging it unfortunately, you know.

Can I assume it was fixed? I don't have a repro nor other info since two weeks ago and I don't know how to help you further otherwise. So, I'm tempted to close the issue.

Yes, thank you. It can be closed. I am sorry for not responding with proper info. I redesigned my code and probably eliminated my error, even though I don't know where it was exactly. Thank you very much for your suggestions.

I'm glad you fixed it. Thanks for the quick turnaround. 👍


Mast: Watch search\sengine\smarketing

Mast requests the watch of the watch_keyword search\sengine\smarketing. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

search\sengine\smarketing has been seen in 27 true positives, 1 false positive, and 0 NAAs.


Not able to parse Cancel Order Response from Openfinex

Response_handle is throwing error while parsing response:-
[2021-08-31T07:03:24Z ERROR substratee_worker_enclave::openfinex::openfinex_api_impl] Sending order to openfinex: [1,0,"admin_cancel_order",["btcusd",["86a36f48-0a29-11ec-9287-0242ac170002"]]]
[2021-08-31T07:03:24Z ERROR substratee_worker_enclave::openfinex::response_lexer] Response from openfinex: "[2,0,\"admin_cancel_order\",[]]"
[2021-08-31T07:03:24Z ERROR substratee_worker_enclave::openfinex::response_handler] Failed to map response to objects: ResponseParsingError("Unknown or unsupported request type (CancelOrder), cannot map to response")
[2021-08-31T07:03:24Z ERROR substratee_worker_enclave::openfinex::response_lexer] Response from openfinex: "[5,\"oc\",[\"ALICE\",\"5GrwvaEF5zXb26Fz9rcQpDWS57CtERHpNehXCPcNoHGKutQY\",\"btcusd\",1,\"86a36f48-0a29-11ec-9287-0242ac170002\",\"sell\",\"c\",\"l\",\"0.001\",\"0\",\"0.005\",\"0.005\",\"0\",0,1630393401]]"

And as mentioned in Issue #149. Which message we should treat as Success response?

Update
This message should be treated as Success response:-
[2021-08-31T07:03:24Z ERROR substratee_worker_enclave::openfinex::response_lexer] Response from openfinex: "[5,\"oc\",[\"ALICE\",\"5GrwvaEF5zXb26Fz9rcQpDWS57CtERHpNehXCPcNoHGKutQY\",\"btcusd\",1,\"86a36f48-0a29-11ec-9287-0242ac170002\",\"sell\",\"c\",\"l\",\"0.001\",\"0\",\"0.005\",\"0.005\",\"0\",0,1630393401]]"
Document for Reference
https://open-finance.org/private-events.html

@zktony is this issue still up to date?


UAT| Case Filling | Litigant raises the case ,Case got admitted but still not displaying in Litigant screen

Describe the bug
Litigant raises the case ,Case got admitted but still not displaying in Litigant screen
To Reproduce
Steps to reproduce the behaviour:

Login as Litigant
Click on 'File Case' button
Fill all mandatory details submit case
Login as the Nya Mitra accept the payment
Login as the FSO register the case
Login as judge admit the case
Now login as Litigant

Expected behaviour
Case should display in Litigant screen
Actual behaviour
Case got admitted but still not displaying in Litigant screen
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: windows
Browser: chrome

Hi @mustakim-egov Please check with new user.
I think this issue occurred due to new role mapping.
If you still facing this issue let me know.


Google Docs Viewer

Hello!
Is it possible to adjust the size of IFrame to the full lenght(height) of the PDF document rendered by https://docs.google.com/viewer?url= ???
Best regards

Not without getting Google to host one of the JS files.
Failing that I recommend using https://viewerjs.org/ instead.


SLURMCluster - number of tasks requirement

Hi,
I've got a question/problem - what is the reason of hard-coding the number of tasks to 1?
This is problematic in some way for me because in my scenario I want to run multiple-node jobs and it is impossible with current generation of job_header.
Example:
I have a cluster of nodes with 24 CPUs per each and initialize my SLURMCluster like that
from dask.distributed import Client
from dask_jobqueue import SLURMCluster
cluster = SLURMCluster(name='dask_test',
                       queue='qwe123',
                       memory='1GB',
                       processes=48, # 2 times 24 since I want double-node job
                       threads=2, # combined with number of processes gives 96 cores
                       interface='ib0',
                       walltime='00:10:00',
                       job_cpu=1, # 1 CPU per each task
                       job_extra=['--nodes=2', '--ntasks-per-node=24'])

Such declaration gives me following job header:
In [22]: cluster.job_header
Out[22]: '#SBATCH -J dask_test\n#SBATCH -e dask_test.err\n#SBATCH -o dask_test.out\n#SBATCH -p qwe123\n#SBATCH -n 1\n#SBATCH --cpus-per-task=1\n#SBATCH --mem=45G\n#SBATCH -t 00:10:00\n#SBATCH --nodes=2\n#SBATCH --ntasks-per-node=24'

And because of -n argument it won't create double-node jobs. So I've got to remove that from job header manually.
Maybe the number of tasks should be also an argument for cluster initialization and if it will be None the -n sbatch argument would not appear in job header? What I mean is a more flexible way of job_header creation.

The keywords that you specify at construction time are per-node.  If you
want two nodes then you specify this when you ask for workers with
cluster.scale(2)
On Fri, May 18, 2018 at 6:54 AM, AdamWlodarczyk<EMAIL_ADDRESS>wrote:

Hi,
I've got a question/problem - what is the reason of hard-coding the number
of tasks to 1?
This is problematic in some way for me because in my scenario I want to
run multiple-node jobs and it is impossible with current generation of
job_header.
Example:
I have a cluster of nodes with 24 CPUs per each and initialize my
SLURMCluster like that
from dask.distributed import Client
from dask_jobqueue import SLURMCluster
cluster = SLURMCluster(name='dask_test',
queue='parrtition123',
memory='1GB',
processes=48, # 2 times 24 since I want double-node job
threads=2, # combined with number of processes gives 96 cores
interface='ib0',
walltime='00:10:00',
job_cpu=1, # 1 CPU per each task
job_extra=['--nodes=2', '--ntasks-per-node=24'])
Such declaration gives me following job header:
In [22]: cluster.job_header
Out[22]: '#SBATCH -J dask_test\n#SBATCH -e dask_test.err\n#SBATCH -o dask_test.out\n#SBATCH -p devel\n#SBATCH -n 1\n#SBATCH --cpus-per-task=1\n#SBATCH --mem=45G\n#SBATCH -t 00:10:00\n#SBATCH --nodes=2\n#SBATCH --ntasks-per-node=24'
And because of -n argument it won't create double-node jobs. So I've got
to remove that from job header manually.
Maybe the number of tasks should be also an argument for cluster
initialization and if it will be None the -n sbatch argument would not
appear in job header? What mean is more flexible way of job_header
creation.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask-jobqueue/issues/62, or mute the thread
https://github.com/notifications/unsubscribe-auth/AASszOzbXmUug9dJ5z7vm1AdDnIGQmL2ks5tzqhPgaJpZM4UEiC0
.

I see. Well, thanks for clarification. Issue can be closed.
Great package BTW!

What @AdamWlodarczyk is trying to describe is the case where each we want a single Dask worker for a set of nodes attached to a single job. Our use case is a task that forks out an srun process which can consume the entire resources allocated to the job. The current syntax doesn't allow us to do this since we would need to overwrite the #SBATCH -n 1\n#SBATCH --cpus-per-task=1...but come to think of it, I wonder if we can just override the default values via job_extra

As @mrocklin mentionned, this was not the initial idea of dask-jobqueue to launch multi nodes job at once. I believe this is also because initial development was done with PBS if I am not mistaken.
From the few I've seen, Slurm is much more powerfull and versatile, and it is probably possible to easily launch jobs that spawn dask-worker processes on multiple nodes at once. By easily I mean just by slightly modifying the job script.
Feel free to work on a pull request doing this 🙂 ! This could be a nice option.

Is there an advantage to running few jobs that launch multiple dask-workers vs many jobs that launch one dask-worker each?

The case I can think of is if you want to be sure to have a given computing power for a known amount of time. Dask-jobqueue is great for interactive analysis, where we can varry the number of workers. But in some production cases, we may want to know for sure we have a


medfile: 4.1.1 -> 5.0.0, fix darwin build and refactoring

Description of changes

Update to 5.0.0
Replace rec with finalAttrs
Replace patch for hdf5 1.14 with postPatch
Fix build on darwin (wondering which of the changes should be reported upstream)

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/4000

Friendly ping to @gebner on this 🙂

Friendly ping to @SuperSandro2000 on this 🙂

Thanks for merging this, @SuperSandro2000. 🙂👍


after upgrading ubuntu to 14.04.3, I can not build docker image.

When I try to build a docker image with my simple Dockerfile, my ubuntu desktop hangs even for all the input interfaces.
1.
$ docker build -t myname/devops:v1 .
$ cat Dockerfile
FROM ubuntu:14.04.3
MAINTAINER myname<EMAIL_ADDRESS>ENV DEBIAN_FRONTEND noninteractive
RUN sed -i 's/archive.ubuntu.com/kr.archive.ubuntu.com/' /etc/apt/sources.list
RUN echo 'Acquire::http::Proxy "http://<IP_ADDRESS>:3142";' > /etc/apt/apt.conf.d/01proxy
RUN apt-get update && apt-get -y dist-upgrade
RUN apt-get install -y
man
vim
ssh
git
build-essential
ipython
python-keystoneclient
python-novaclient
python-glanceclient
python-cinderclient
python-heatclient

After upgrading OS kernel and replacing the public Ubuntu image to 14.04.3, it has been resolved.


Missing details for some regions (e.g. westus3)

Document missing details for some regions where aci is available like westus3.
Note: I recently tried deploying 1c/2gb ram to westus3 and received a failure due to capacity.

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

ID: 4153e809-a854-ff58-3d1e-31770c36a1f9
Version Independent ID: e37b5834-9174-5ea2-567c-7b2628ed9eeb
Content: Resource availability by region - Azure Container Instances
Content Source: articles/container-instances/container-instances-region-availability.md
Service: container-instances
GitHub Login: @tomvcassidy
Microsoft Alias: tomcassidy

yes, that looks correct.

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

@Karishma-Tiwari-MSFT Thanks for validating this info. I'll make this change right away.
By the way, where did you get that screenshot of the region availability from?
Thanks.

@stewartadam @Karishma-Tiwari-MSFT Judging by a query on the Azure Data explorer, there actually is not region availability for West US 3. That could also be why a "failure due to capacity" was returned. There is no capacity. Still strange that it wouldn't just say the region is unavailable.
I'm continuing to look into this with the product team, but this is likely a case of the Azure products by region table being incorrect. If that is the case, I'll get that changes ASAP.
Thanks for the feedback. #please-close


[Feature request] Add wormhole type to signature and link destination

Hey there,
I'd love to be able to attach a wormhole ID to a signature for easier reference.
Another thing I'd love to see would be, related to this, would be linkability to a destination system.

From #119 :
Hi,
are there any plans on creating a logical connection between the signature IDs and the corresponding WH connections? So that deleting a WH signature would for example automatically get rid of the correspoding connection.


Split up tests so that non-lattices can be tested

It would be good to split up the test function latticeLaws so that, for example, just the join semilattice laws could be tested, without requiring all the other instances.

There's some ok-ish split in the tests


Google Drive link does not work

Thank you for your great works.
I want to use your pretrained weights but your given google drive link does not work.
And I also tried to download the Baidu file, but the program is all chinese and I failed to download it.
Can you check the google drive link?
Thank you!

Sure, the correct link has been updated!

Thank you!

Thank you!


Setup CI

could be TravisCI, CircleCI or Github Actions, or all of them (yay, free stuff)
I would love to play around with Jenkins X and Tekton, but that can happen later

Closed in #16


"Help me choose" help link incorrect (again)

At the moment it points to the Getting Started page. Instead it should point to Advanced Topics. It probably has been moved in the past, I think. :thinking:

I just noticed, right after submitting this issue... there's already a PR pending (#90) :man_facepalming:
But maybe you could merge it. :upside_down_face:


Theming nested components

New to react-toolbox, thanks for all the hard work! I'm finding it fairly straightforward to compose components, but I'm having trouble with theming nested components, e.g. <ListItem /> → <ListItemLayout /> → <ListItemContent /> → <ListItemText />.
My understanding is that react-css-themr provides a way to define default styles for components, but does not address overriding styles for particular components. For this, we must pass the theme prop to RT components with a class definition that matches the documented root class, e.g. .item { ... }.
This works great one level deep, but I do not understand how to style nested RT components. For example, how do I change the text color of a ListItemText component, when all I'm rendering in my component is <ListItem theme={theme} ... />? Of course, I could just select the correct elements by name (.item > span > span { color: red; }), but this seems to defeat the point of CSS modules, and is brittle.
From the docs, it looks like you should be able to provide top level class definitions for nested components in the theme of the the component you are rendering, i.e. defining a .itemText { ... } block in the theme passed to <ListItem />. However, in this case the theme doesn't appear to be passed through to the <ListItemText /> component. How are these theme names/classes intended to be used? Thanks!

Is this perhaps specific to list items? I could submit a PR that passes the this.props.theme through on this line and this line (and others). It seems like this would have the desired effect, but I want to make sure this is the intent and I'm not missing something.

Hi @slindberg! You got it right from what I read :) In this approach subcomponents are intended to use the same theme object than the parent. A caveat is that they can't share the same classNames and that's why some of them are namespaced. The theme is not directly passed down because by default it can be passed in the export definition. So the overrides can be provided straight when you use the subcomponents.
If a component catches and render the subcomponent if should spread the props. If not, it should be considered a bug.

Great, submitted #669 to address the issue.


Various minor improvements

This PR adds a number of small improvements to build with pedantic build settings using clang-cl on MSVC. The changes are:

cmake should try not to override the CMAKE_BUILD_TYPE or the -march, if any of those are given by the user. This is so that users can easily compile for a specific build type or target architecture (i.e. distributors may set -march to an older target).
Removed the EXCLUDE_FROM_ALL from building tests, benchmarks and examples. There are cmake options like -DBUILD_TESTS=ON/OFF to enable or disable these targets, so they may as well be built by default?
A few cases of shadowed parameters have been fixed by renaming the parameter with a prefix 'a'
Fixed two cases where parameters were not valid for clang or generally not valid on MSVC

I finally had the time to review it, thanks very much this is very neat!


video from new DSP collection fails to play on both DAI and dev1

THE LAST ONE ABOVE DOES NOT PLAY.

At least 1 RB sign is  also not playing, and also missing thumbnails.

All issues above have been resolved, except for the last one:

This last one - BREAK - is still a problem.


Idmap fix

Per email discussion with @LFDM .  We are still not sure why we are losing newly added artificial tokens even with the fixes in the ellipsis_fix branch,  but at least one symptom is that  sourceids are being reassigned. We decided it would be a good idea to make the idhandling code more robust by refusing to reassign already assigned sourceids when creating/updating IdMaps for tokens.
Originally I was thinking we should throw some sort of notification if we try to do this but it's not clear to me what  form that should take. So the change in this pull request so far just silently fails to steal an already mapped sourceId.
Note that this idmap_fix branch was on master, which doesn't yet have the ellipses fix in the treebank persister, and so would normally be stealing tokens if you try to persist a doc with newly added artificial tokens twice (because of the reassignment to the lastId at https://github.com/latin-language-toolkit/arethusa/blob/master/app/js/arethusa/treebank_persister.js#L135). This token stealing no longer occurs with the change in this pull request, because the reassignment no longer has any effect.
I'm not sure we want to merge this request as-is without doing something more with the notifications, but sending it on as-is for some feedback on what I've done so far.
Thanks!

this request was superceded by and addressed with #572


org.osgi.framework.BundleException on GlassFish server statup

On the startup of Jakartafied GlassFish 6.0.0-SNAPSHOT domain following exceptions are thrown, during the deployment of admin console app:
org.osgi.framework.BundleException:
Unable to resolve org.glassfish.main.security.webservices.security [279](R 279.0):
missing requirement [org.glassfish.main.security.webservices.security [279](R 279.0)]
osgi.wiring.package; (&(osgi.wiring.package=com.sun.xml.ws.api.message)(version>=3.0.0)(!(version>=4.0.0)))
	[
	caused by: Unable to resolve org.glassfish.metro.webservices-osgi [278](R 278.0):
	missing requirement [org.glassfish.metro.webservices-osgi [278](R 278.0)]
	osgi.wiring.package; (&(osgi.wiring.package=com.sun.istack.logging)(version>=3.0.0.M2))
		[
		caused by: Unable to resolve com.sun.xml.bind.jaxb-osgi [161](R 161.0):
		missing requirement [com.sun.xml.bind.jaxb-osgi [161](R 161.0)]
		osgi.wiring.package; (osgi.wiring.package=org.glassfish.jaxb.core.v2.runtime.output)
		]
	]
Unresolved requirements: [
[org.glassfish.main.security.webservices.security [279](R 279.0)]
osgi.wiring.package; (&(osgi.wiring.package=com.sun.xml.ws.api.message)(version>=3.0.0)(!(version>=4.0.0)))
]

Unable to resolve org.glassfish.main.security.webservices.security [279](R 279.0):
missing requirement [org.glassfish.main.security.webservices.security [279](R 279.0)]
osgi.wiring.package; (&(osgi.wiring.package=com.sun.xml.ws.api.message)(version>=3.0.0)(!(version>=4.0.0)))
	[
	caused by: Unable to resolve org.glassfish.metro.webservices-osgi [278](R 278.0):
	missing requirement [org.glassfish.metro.webservices-osgi [278](R 278.0)]
	osgi.wiring.package; (&(osgi.wiring.package=com.sun.xml.bind)(version>=3.0.0)(!(version>=4.0.0)))
	]
 Unresolved requirements: [[org.glassfish.main.security.webservices.security [279](R 279.0)] osgi.wiring.package; (&(osgi.wiring.package=com.sun.xml.ws.api.message)(version>=3.0.0)(!(version>=4.0.0)))]

Classes from package org.glassfish.jaxb.core.v2.runtime.output are moved to runtime module hence refactoring need to be done in XMLStreamWriterOutput.java#L174.

well, short version is - IF jaxb gets updated in GF, Metro MUST (in 98% cases) be updated too
longer version - see https://github.com/eclipse-ee4j/metro-jax-ws/pull/137, https://github.com/eclipse-ee4j/metro-wsit/pull/82, https://github.com/eclipse-ee4j/metro-wsit/pull/84 and https://github.com/eclipse-ee4j/glassfish/pull/23034

btw: that missing refactoring must be done not because of OSGi failure but because one jax-ws specific feature failing with M3 - huge file upload - and this was fixed in #1448

closing this as this is very likely caused by an attempt to wire incompatible jaxb/jaxws versions together


Immutable as State in JSBin

I took the sample from the WIKI page and pasted it into a JSBin.  I added script tags with CDN links to React, and Immutable.js.  So the only changes I made to this code removes Common JS and prefixes Map and List with Immutable.
Link to sample on Bin
The issue is when I run the sample the count does not update.  Is this sample supposed to work this way?  The count always being 0?
Sample Output
Count: 0
Saved counts:

Saved: 0
Saved: 0
Saved: 0
Save count

var Component = React.createClass({

  getInitialState() {
    return {
      data: Immutable.Map({ count: 0, items: Immutable.List() })
    }
  },

  handleCountClick() {
    this.setState(prev => ({
      data: prev.data.update('count', v => v + 1)
    }));
  },

  handleAddItemClick() {
    this.setState(prev => ({
      data: prev.data.update('items', list => list.push(prev.data.get('count')))
    }));
  },

  render() {
    var data = this.state.data;
    return (

          Count: {data.get('count')}

        Saved counts:

          {data.get('items').map(item =>

Saved: {item}

          )}

Save count

    );
  }

});

React.render(<Component />, document.body);

Clicking on "Count: ##" will increment the count. Clicking "Save Count" will add the current count to a List.
The example is supposed to work in this way. It may be better to have "Count: ##" and "Save Count" be hyperlinks or buttons to make it more clear if this functionality wasn't apparent from the code.

Thanks for this feedback! I wanted to keep the example as simple as possible but understand why this was confusing. I made some modifications to make them buttons, https://github.com/facebook/immutable-js/wiki/Immutable-as-React-state


chore: fix on final_chain crash

Purpose
So recently lot of test were crashing and this is cause as we returned nullptr when block was not finalized yet
How does the solution address the problem

Changes made

prnet cleaned-up successfully


Add local ratelimit example

Title: Add local rate limit example
Description:
Now we have an implement for global rate limit, but no examples for local rate limit.
I want to add one under the sandbox in the doc web if possible.

sounds like a good plan, i would be happy to review

/assign

Fixed by #19471


test_image.py error

I got the following error when I run test_image.py on a test image
COMMAND:
E:\Projects\RFB_ESRGAN-PyTorch>python test_image.py -a rfb --lr E:/Projects/ESRGAN/LR/baboon.png --pretrained --gpu 0
RESULT:
##################################################

Run Testing Engine.

[ WARNING ] Directory `E:\Projects\RFB_ESRGAN-PyTorch\tests` already exists!
[ INFO ] TestingEngine:
        API version .......... 0.2.0
        Build ................ 2021.04.15
##################################################

[ INFO ] Using pre-trained model `rfb`.
Traceback (most recent call last):
  File "test_image.py", line 136, in <module>
    main()
  File "test_image.py", line 68, in main
    main_worker(args.gpu, args)
  File "test_image.py", line 77, in main_worker
    model = configure(args)
  File "E:\Projects\RFB_ESRGAN-PyTorch\rfb_esrgan_pytorch\utils\common.py", line 48, in configure
    model = models.__dict__[args.arch](pretrained=True)
  File "E:\Projects\RFB_ESRGAN-PyTorch\rfb_esrgan_pytorch\models\generator.py", line 122, in rfb
    return _gan("rfb", 16, pretrained, progress)
  File "E:\Projects\RFB_ESRGAN-PyTorch\rfb_esrgan_pytorch\models\generator.py", line 100, in _gan
    state_dict = load_state_dict_from_url(model_urls[arch], progress=progress, map_location=torch.device("cpu"))
  File "E:\Programs\Anaconda3\envs\yolact\lib\site-packages\torch\hub.py", line 517, in load_state_dict_from_url
    cached_file = os.path.join(model_dir, filename)
  File "E:\Programs\Anaconda3\envs\yolact\lib\ntpath.py", line 115, in join
    genericpath._check_arg_types('join', path, *paths)
  File "E:\Programs\Anaconda3\envs\yolact\lib\genericpath.py", line 155, in _check_arg_types
    raise TypeError("Can't mix strings and bytes in path components") from None
TypeError: Can't mix strings and bytes in path components

Sorry , RFB_ESRGAN not have pretrained weights.....


[VS Code] Joining collaboration session: Unable to connect to Live Share cloud relay. Check your proxy, firewall and network settings and try again.

<!--
For Visual Studio problems/feedback, please use the Report

@nikamanthab Thanks for reporting. Could you attach logs for investigations? In VSCode you can open command palette and type Live Share: Export Logs, it will give you logs zip file. Thanks!


Identify case of string?

Would be nice to identify case of string, eg:
change-case.identifyCase("Love"); -> titleCase
change-case.identifyCase("LOVE"); -> All Uppercase
etc

That would definitely be interesting to see. Not sure the best way to achieve it though. The naive approach is just to build this from scratch. I'll definitely consider it for the next release (but I'm not sure when that'll be)!

Just found this lib that identifies case too :) https://www.npmjs.com/package/case

Awesome! I'll close this issue out as-is. I'm always happy if someone wants to add something like this, but it's not something I'm planning to add myself.


Bug or Design?  Noticed that unexport() leaves given pin in a floating state?  This is typically not a best practice?

Bug or Design?  Noticed that unexport() leaves given pin in a floating state?  This is typically not a best practice?  If I explicitly set the pin for output, the floating condition is avoided.  It is my understanding that the default state for most pins on Pi hardware start up is set for output, no?  This avoids pin floating.

Noticed that unexport() leaves given pin in a floating state?

I don't believe this to be the case.

Please provide a short and complete program which can be used to reproduce this behaviour.
Please explain how you verified that the given pin is floating.

It is my understanding that the default state for most pins on Pi hardware start up is set for output, no? This avoids pin floating.

This is not my understanding. My understanding is that most pins are configured as input pins by default and have either their internal pullup or pulldown resistor activated. It is also my understanding that calling unexport for a pin will configure the pin as an input without modifying the state of it's pullup or pulldown resistor which implies that it should not be floating.

It is not a matter of providing anything. I am watching the GPIO pins, and the voltage is floating, the default state at power up, most GPIO pins on a Pi device are floating, unless explicitly assigned as in or out mode.  My point or question is, should you code not explicitly default to out mode, so the given pins are not floating.  If I use you code, I explicitly see the given pins in question return to a floating state, when I call unexported() to release the pins from control.  It would be better to not allow the pins return to a floating state, IMHO.

the default state at power up, most GPIO pins on a Pi device are floating, unless explicitly assigned as in or out mode.

This is not the case. As already mentioned above, most pins on a Pi are explicitly configured as in pins on power up.

My point or question is, should you code not explicitly default to out mode, so the given pins are not floating.

No, the code should definitely not explicitly default to out mode. This is highly likely to result in short circuits. For example, assume GPIO17 (or any other GPIO) is connected to a 3V3 power source. If GPIO17 is configured as an output and it's value is set to 0V we have a short circuit.

It is not a matter of providing anything.

I see this a little differently.

If I use you code, I explicitly see the given pins in question return to a floating state, when I call unexported() to release the pins from control.

You need to see this from my perspective. All I know is that you are having an issue with some circuit. Regarding this circuit and the code that is used to control it I am completely in the dark. I have no idea what the concrete problem is. If you explain what the circuit should do and what it does do we may be able to resolve the issue.

I noticed the behavior using your code, and then used volt meter, checking the given GPIO pin, with and without using unexported().  This was where the surprise was, I could see the unstable voltage, i.e. floating.  If I left the given GPIO pin set for output, et the end of script execution, I no longer saw the float (of course).
True, the short-circuit issue is significant, my comments are in the context of the topic and testing, I realize I should have qualified that better.
I was trying to drive a MAX7219 based LED strip (8 7-segment LEDs).  Using rpi-led-control (on git).  It may be the actual GPIO pins I have been watching have non-typical behavior.  This all started when I was watching a bit-bang based script using GPIO 8, 10, 11... in other words overriding the SPI0 group of GPIO pins.  The original script I updated to work with current versions of required modules.  The original version of the project will not compile under npm.  Nor execute on current node js with current versions the required modules.  For example, it was trying to use a very old version of onoff module.
The long and short, you did qualify my question... onoff is doing what it does... by design.
Given I am using bit-band based module to drive the MAX7219 based device, if unexported() is never called there is little risk of a short circuit per se, pins are not exposed.   Moreover, what is odd is the original script... never called unexported.  Which struck me as odd, if not a bad practice.  The old C programming mantra... if you allocate, you must de-allocate it.
I plan to further update the solution to use true SPI, and avoid the bit-banging, this will avoid the issue as well, in due course.

In this case it's ok to allow the program to terminate without calling unexport. The sysfs files located at /sys/class/gpio that are used to control the pins will remain there after the program has terminated. On program termination, outputs will remain configured as outputs and inputs will remain configured as inputs.

Cool... Somehow it feels wrong... (my old C experience influence)... But makes sense.  Thanks for taking the time to answer my question, and moreover, doing active support of the 'onoff' module.

Thanks for taking the time to answer my question, and moreover, doing active support of the 'onoff' module.

You're welcome :smile:


[REMOVED]

I have been attacked on my laravel app. The AWS report says it's a dotenv leak attack.Please suggest to me how to stop this. All my security keys were compromised.Below are the details. Please reply for more details.

Laravel version:6.0
PHP Version: 7.3
Server: aws ubuntu ec2 server
Issue : dot_env_leak

Event log in ec2 report
 {"timestamp":<PHONE_NUMBER>,"source_ip": "<IP_ADDRESS>","source_domain": "ec2-3-112-12-175.ap-northeast-1.compute.amazonaws.com","destination_ip": "<IP_ADDRESS>","destination_port": 443,"destination_service": "dotenv","protocol": "tcp","payload_class": "exploit:gen/dot_env_leak","payload_data": "R0VUIC8uZW52IEhUVFAvMS4xDQpob3N0OiAxMy4yMzIuMTI3LjE5OTo0NDMNCmNvbm5lY3Rpb246IGtlZXAtYWxpdmUNCmFjY2VwdC1lbmNvZGluZzogZ3ppcCwgZGVmbGF0ZQ0KYWNjZXB0OiAqLyoNCnVzZXItYWdlbnQ6IE1vemlsbGEvNS4wIChYMTE7IExpbnV4IHg4Nl82NCkgQXBwbGVXZWJLaXQvNTM3LjM2IChLSFRNTCwgbGlrZSBHZWNrbykgQ2hyb21lLzgxLjAuNDA0NC4xMjkgU2FmYXJpLzUzNy4zNg0KDQo="},

Please read our Readme and security policy and don't disclose security vulnerabilities publicly. This should also be reported to the dotenv repo and not Laravel.

Please read our Readme and security policy and don't disclose security vulnerabilities publicly. This should also be reported to the dotenv repo and not Laravel.

Please do not create an issue on that repo if you think there is an issue, either. Follow the security disclosure process: https://github.com/vlucas/phpdotenv/security/policy#reporting-a-vulnerability.

Please do not create an issue on that repo if you think there is an issue, either. Follow the security disclosure process: https://github.com/vlucas/phpdotenv/security/policy#reporting-a-vulnerability.


Adding a \ in the search bar breaks the website

Thanks for your work 👍
Adding a \ in the search bar breaks the website

Hello Abdullah @abumalick
Thank you for having reported the problem.
A fix has been released.
Could you reload and try again? (and if possible try any combination that could break the things!)
Example of URL that used to break the site: https://bestofjs.org/projects?query=&tags=framework

I'm closing the issue but I'm still waiting for your feedback Abdullah @abumalick
Thank you in advance!

Oh, I thought I answered.
Yes I tested when you pushed the fix and it worked well.
Thank you very much for your work 👍


validation set

Hi
Thank you for your excellent fundamental work in the robust SSL.
I have a question regarding the experiment setting in your paper:
In Table1 of your paper, https://arxiv.org/pdf/2007.11330.pdf, for different labeled data setting, you use validation set of 5000 for the validation set, and you tune hyperparameters for the different labeled data setting, is this correct?
Looking forward to hearing from you!

Hi. For each dataset, we used the validation set to tune the hyperparameters. But we used the same hyperparameters when only the number of labeled data is changed.


server lag when power is out

Issue description: When the system is out of power the server lag is very significant
What happens: power runs out
                              system flickers
                              server's tps is at 2%

What you expected to happen:This not to happen and it to just shut off
Steps to reproduce:
1.make a system
2. give it power
3.cut off power
...
Version (make sure you are on the latest version before reporting):

Minecraft: 1.10.2
Forge: 1.10.2-<IP_ADDRESS>1-universal
Refined Storage:1.2.26

Does this issue occur on a server? yes
If a (crash)log is relevant for this issue, link it here:
[pastebin/gist/etc link here]

1.10.2 is unsupported.

why is it unsupported in 1.10.2 that makes running a server with that mod nearly impossible
it is in fool craft please try to fix it

Unfortunately, I don't care. It is fixed in RS for 1.11 and 1.12 though.


Polyline 'edit' event does not fire on touch devices

With Leaflet-draw 0.3.2, the 'edit' event does not fire on iOS simulator with iOS 9.3. It works fine on desktop.
How to reproduce:

Open: file:///..../GitHub/Leaflet.draw/examples/edithandlers.html in Safari in iOS simulator.
Open the Safari console on Desktop to see the iOS Simulator console output.
Touch drag a point on the polyline.
The console does not output "Polyline was edited!"

		polyline.on('edit', function() {
			console.log('Polyline was edited!');
		});

Neither does draw:editvertex
    map.on('draw:editvertex', function (e) {
      console.log('draw:editvertex');
    });

Are you using leaflet v1.0+ or v0.7.7?

LL 0.7.7
The events fire fine when adding or removing points along the polyline. It's when dragging a point that it does not work.

LL 0.7.7
The events fire fine when adding or removing points along the polyline.
It's when dragging a point that it does not work.
--
Nicolas Hinze
<EMAIL_ADDRESS>On October 4, 2016 at 12:58:11 PM, DeanoFino<EMAIL_ADDRESS>wrote:
Are you using leaflet v1.0+ or v0.7.7?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Leaflet/Leaflet.draw/issues/604#issuecomment-251447585,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABGkL4QS_z7byHygfIdy72UAEQiHcRw8ks5qwoWhgaJpZM4KMczG
.

I noticed that the events fire correctly when testing on Chrome and using the mobile device touch simulator in the Dev tools. However, the events do not fire on iOS or Android. From some online research, it seems that the touchend event is a bit unreliable. Hopefully a workaround can be found.

I just tested Leaflet-draw 0.4 and I can report the following:

Events do not fire with LL 0.7
Events fire as expected with LL 1.0
To reproduce, I simply opened the edithandlers.html examples in the iOS Simulator.

@nhinze Hi, did you ever come to any sort of resolution for this issue? I'm running into some problems with iOS/Android editing and I think its the same problem. I'm about to dig into the code but if you've already found a solution then I'd like to get a PR together and hopefully get it merged into master.

I found that the event fires for draw:edited but that the layers array is empty. This makes it difficult to persist changes to a server.

edited flag is not being toggle appropriately on dragend

I never found a fix. I think the problem is at LL level. Touch end does not get fired for some reason.

I have a fix for it; basically just comment out the if (leaflet.edited) check in the save function for EditToolbar.Edit. This is appropriate for our project but I'm guessing a deeper fix will be necessary to correct the underlying issue with touchscreens. The fix is present in the master branch of z0d14c/Leaflet.draw


Bug: Mis-formatted error diagnostics for incorrect function use

Repro:
$ srcd sql
mysql> select split("a,b", ",", 1);

Observed:
ERROR 1105 (HY000): unknown error: %!s(int=2): expecting 3 arguments for calling this function, %!d(MISSING) received

Expected:

Since it turns out that split only accepts two arguments, I would expect the diagnostic to report that 2 arguments are expected, not 3 (I assume the latter is because the implementation has a receiver or something hidden from the query API).

The error should not be classified as "unknown": It's either a syntax error or invalid parameters, but it is fully under the control of the CLI.

I expect the format strings to match their type, so that it says something like

ERROR: split: expected 2 arguments, received 3.

instead of having the auto-generated fallbacks from the fmt package like %!d(MISSING).

I expect the error string to mention the name of the function I got wrong. In this case it is obvious, but in a bigger query it would not be.

ERROR 1105 (HY000): unknown error: comes from vitess.
We can fix invalid argument argument description as suggested .

🤘#666


Get notified if node disconnects/shuts down

Is there a way to get notified if a node becomes unavailable?
I'd like to try reconnecting when a node has to restart or network is not reliable

This might be worth adding some "Node events" channel on the NodeServer actor. Such that you could subscribe to node change events.

I'd love to try to implement this but I'm still a bit of a rusty novice. So if I open a PR for this feel free to give it a healthy dose of criticism

I've identified that https://github.com/slawlor/ractor/blob/d79ea281cbd8af26cd3416c085a60bf3a56fc44c/ractor_cluster/src/node/mod.rs#L434 would be the place to emit an event
I was just wondering what you thought would be the best channel/method to notify any listeners to these events? @slawlor

You could use something like an output port, but their syntax still isn't ideal to me (it's the least "clean" aspect of ractor imho right now). Otherwise I'd say a "broadcast" actor would make sense. It's message structure might look like
enum BroadcastMessage<TMessage, F>
// this function is what actually sends the message to the subscribing actor
where F: Fn(ActorCell, TMessage) -> () + 'static,
{
  Subscribe(ActorCell, F),
  SendMessage(TMessage),
}

There's probably some weird lifetime stuff, but I "think" this would work?


How to change parser?

It seems it uses the first parser it can find - or at least, it's not using my custom parser. Any way to change this?

Okay, it seems to be loading my parser - but not using my format for some reason?
registerFileType((fileExt, filePath, fileData) => {
    if (['lib', 'g.lib'].includes(fileExt)) {
        return true;
    }

    return false;
});

registerParser(() => {
    read(1);
    addRow('Type', getHexOxValue(), 'Record Type');

    read(2);
    const recordLength = getNumberValue();
    addRow('Length', recordLength, 'The full length of the record');

    read(recordLength);
    addRow('Data', getStringValue(), 'Data');
});

Trying to create a parser for this:
http://www.azillionmonkeys.com/qed/Omfg.pdf

In the problems area you should find the hint:

Actually you used a 'O' instead of a '0' (zero) inside getHex0xValue.
If you change it and save, you should see your parsed file:

Which highlighting? the red squiggles?
They come from the binary file viewer extension. Any errors are also written to the PROBLEMS pane.
Is it not working for you?
You need to save the js file before it is analyzed.

For me it displays the correct suggestion:

You can see the text 'Binary File Viewer' to the right of the suggestions which shows the origin.
The others are probably from intellisense
Maybe you chose the wrong auto-completion.

Is not working for me - do I need to select a specific format? Or do I need to edit the parser file from a window where the extension itself is also being used? Auto completion works though
It does for me too - but it doesn't show the errors

I also found the source for my error, see: https://github.com/maziac/binary-file-viewer/blob/204b98100ecf7be0689ac41795d62df43c1dd6b3/assets/local/help/help.md?plain=1#L100

Yes, while developing a parser file you need to have the parser file and the parsed file in the same vscode window.
The cause of this is explained a little bit here: filewatcher

Thanks for the hint. I will correct that.

Thanks, good to know
You're welcome!

Another question - as you can see in http://www.azillionmonkeys.com/qed/Omfg.pdf the binary file contains multiple records - I was under the impression I could show each record as a separate line through the parser - but it only works with rows - not columns - is this possible at all?

" I was under the impression I could show each record as a separate line through the parser - but it only works with rows - not columns "
Could you elaborate a bit. I don't understand the problem.

No elaboration needed - I was mistaken how Binary files work 🤣


dynamic environment for Cortex, TheHive, MISP

Changes for PR: https://github.com/frikky/Shuffle/pull/96
Add support of dynamic environment with these variables:
TheHive:

SHUFFLE_ENV_THEHIVE_KEY (param apikey in api.yaml)
SHUFFLE_ENV_THEHIVE_URL (param url in api.yaml)

Cortex:

SHUFFLE_ENV_CORTEX_KEY (param apikey in api.yaml)
SHUFFLE_ENV_CORTEX_URL (param url in api.yaml)

MISP:

SHUFFLE_ENV_MISP_KEY (param apikey in api.yaml)
SHUFFLE_ENV_MISP_URL (param url in api.yaml)

Denying this, since the Shuffle request wasn't merged into Shuffle


Dual monitor issue - Secondary monitor goes black when primary focus on runelite

This is a crazy one but, for whatever reason whenever I open up RuneLite (And only RuneLite), my entire second monitor will go black. It won't turn off, and i can still drag things over too it, but it will be black. If i open any other app up I'm able to get the monitor back, but the second I open runelite, my secondary monitor goes black. I tested if it was a CPU/Power issue by launching significantly more CPU intensive and powerful games, but it doesn't occur. This didn't occur on any previous release, only after updating  Any suggestions?
Environment

OS: Windows
RuneLite version: 1.6.26
Launcher Version: 2.1.0

Issue was resolved by uninstalling and reinstalling the newest version of RuneLite.


Support editing datetime

In the admin, a time.Time field uses a date selector as the editor, there's no way to edit the time portion of the field.

@bodhi I guess you already know this, the form type has date, datetime, the datetime could be used to edit time, but the js plugin doesn't support this.
@jasonweng we need to update the datepicker plugin to handle time, I remember we have researched some choices, not sure what's the decision.
http://simeonc.github.io/sc-date-time/material.html
This one looks good to me, but seems like based on AngularJS, not sure if we could port it to mdl. could you research this?

Ah, I didn't notice that Go doesn't have a date type!


BatteryPool should stream soc and capacity independent of inverter status

I just remembered that this is behaving as designed, when writing the issue, so decided to write this note instead.  BatteryPool is expected to report only the usable SoC and Capacity of the pool.  And if a corresponding inverter is out of order,  then that capacity and SoC are not usable,  so the batterypool should not consider these.
I will keep this issue open until the next SDK meeting, just in case.

I think this should be clearly document in case this isn't yet.

And if a corresponding inverter is out of order, then that capacity and SoC are not usable
That totally makes sense imho

This wasn't mentioned in the last meeting, maybe you want to add it to the agenda @shsms ?


Update NotebooksLocalExperience.md

Updated the kernel install instructions.  The current version didn't work, but the instructions on https://www.hanselman.com/blog/AnnouncingNETJupyterNotebooks.aspx do, so copied over some of those instructions here.

@TheDarkTrumpet Thanks!
We didn't make this at all clear, but this change was intentional. We've moved development of these features over to dotnet-interactive. I updated the installation instructions to include the MyGet feed where the latest builds can be found.


feat(server): migrate Zalando rule 171 to use the new context object …

Related to #714

Codecov Report

Merging #800 into master will decrease coverage by 0.05%.
The diff coverage is 50%.

@@             Coverage Diff              @@
##             master     #800      +/-   ##
============================================
- Coverage     84.89%   84.83%   -0.06%
+ Complexity     1020      996      -24
============================================
  Files           171      172       +1
  Lines          2754     2744      -10
  Branches        421      416       -5
============================================
- Hits           2338     2328      -10
  Misses          210      210
  Partials        206      206

Impacted Files
Coverage Δ
Complexity Δ

...zalando/zally/rule/zalando/CommonFieldTypesRule.kt
90.47% <ø> (+17.74%)
10 <0> (-9)
:arrow_down:

...n/java/de/zalando/zally/util/OpenAPIObjectUtils.kt
41.66% <41.66%> (ø)
0 <0> (?)

...zalando/zally/rule/zalando/FormatForNumbersRule.kt
63.63% <62.5%> (-17.32%)
11 <8> (-15)

Continue to review full report at Codecov.

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

👍

:+1:


introduce LaunchId to identify process restarts

This patch adds a LaunchId type, libmetric_ Prometheus metric, and response header for the pageserver's management API.
The idea is to generate a unique string upon process launch, and expose that string in places where an outside observer needs to identify a process restart.
The motivation for this is that we plan to scrape the pageserver's /v1/tenant/:tenant_id/timeline/:timeline_id/layer
HTTP endpoint over time. It will soon expose access metrics (#3496) which reset upon process restart. We will use the pageserver's launch ID to identify a restart between two scrape points.
However, there are other use cases for the launch ID. For example, we could use the Prometheus metric to annotate Grafana plots.
Or, we could add it to the tracing span to enable filtering logs by process.

ulid looks nice, will switch this PR to that. It should address most of your review comments as well.

If we only want metrics, I think we could do with the 64-bit epoch millis, and not wrap that as a string, it might be useful for keeping other in-session calculations later on -- for a year or so with u32 :)

Not really sure what you mean by this.
I think with the switch to ulid, I'd just keep LaunchId a newtypre around ulid::Ulid.

If we only want metrics, I think we could do with the 64-bit epoch millis, and not wrap that as a string, it might be useful for keeping other in-session calculations later on -- for a year or so with u32 :)

Not really sure what you mean by this.

As in have a metric which just sets a counter/gauge to millis since epoch at startup. That cannot be mixed with any other value because how our ... who ever scrapes it enhances the metrics with additional labels. So we don't need any randomness. We could add a millisecond sleep before "generating" this 64-bit millis value, which would guarantee we wont see duplicates.
This is to say, we don't need any randomness, because other parts provide a replacement for that.
With the latter part:

it might be useful for keeping other in-session calculations later on -- for a year or so with u32

I meant that if we were to need relative timestamps within pageserver, we could in some cases represent them with u32 since our own epoch (pageserver startup), which could help in certain situations like trying to keep message payloads smaller. Well, perhaps that'd still be too small for millis, but over a year with 0.01s.

As in have a metric which just sets a counter/gauge to millis since epoch at startup. That cannot be mixed with any other value because how our ... who ever scrapes it enhances the metrics with additional labels. So we don't need any randomness. We could add a millisecond sleep before "generating" this 64-bit millis value, which would guarantee we wont see duplicates.
This is to say, we don't need any randomness, because other parts provide a replacement for that.

Ok, now I get it.
Sounds appealing, especially in combination with the 1ms of sleep to guarantee uniqueness.
Problems I see:

clock drift
a human looking at just timestamps has a harder time deciding whether they're the same or different compared to ulids

Still against for putting this into all-span though :) There has to be a better way.

As discussed on Slack, changed this PR to just use a timestamp (LaunchTimestamp).
Using that in the metric, startup log message, and header.

Final commit message:
    introduce LaunchTimestamp to identify process restarts

    This patch adds a LaunchTimestamp type to the `metrics` crate,
    along with a `libmetric_` Prometheus metric.

    The initial user is pageserver.
    In addition to exposing the Prometheus metric, it also reproduces
    the launch timestamp as a header in the API responses.

    The motivation for this is that we plan to scrape the pageserver's
    /v1/tenant/:tenant_id/timeline/:timeline_id/layer
    HTTP endpoint over time. It will soon expose access metrics (#3496)
    which reset upon process restart. We will use the pageserver's launch
    ID to identify a restart between two scrape points.

    However, there are other potential uses. For example, we could use
    the Prometheus metric to annotate Grafana plots whenever the launch
    timestamp changes.


LastTimestamp, update vs create

I understand that I could get the time stamp for created by looking at the "first" event and inspect that time stamp, but I think it would be nice to have this on the StreamState. Or is the recommendation to track this in a separate model if I have a need for it, e.g. for getting the streams that where created during a certain period?

Just an oversight. Shouldn't be that big of deal to add that to StreamState.

@jeremydmiller I am looking to get my first commit and this looks a good candidate. How were you envisaging doing this - add a timestamp column to mt_streams for created time or join with mt_events to get the earliest timestamp?

@jamesfarrer I think it'd be a lot easier to query on to just write it to the mt_streams table. Can you do this against the 2.0 branch? I think I need to finally get onto the better story for database schema change detection before we can roll this out and that's going to happen in the 2.0 branch.


Where is nuget package?

Hi. When typing "Results.Net" into VS2022, yields no match result for your library as you can see in the image below

look for "Result.Net" not "Results.Net"

My bad, looks like I was tired 😄


lib-xdocreport: rendering a PDF using XDocreport can be very slow

org.incode.module.docrendering.xdocreport.dom.impl.AbstractFieldsMetadataClassSerializer#process called recursively and can become very costly.
A work-a-round is creating DTO (for example as Innerclass) of the object(s) you are using for rendering.

@johandoornenbal where can i find org.incode.module.docrendering.xdocreport.dom.impl.AbstractFieldsMetadataClassSerializer. I thought there is only AbstractFieldsMetadataClassSerializer from xdocreport it self?


Insufficient info

What is .EXP and where does one find it?

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

ID: 142bb8a9-d18a-1e94-653d-c5d4c8a64ecc
Version Independent ID: 40d6607d-8df0-1185-dc0a-fac2c3d4fab5
Content: Linker Tools Warning LNK4070
Content Source: docs/error-messages/tool-errors/linker-tools-warning-lnk4070.md
Product: visual-cpp
Technology: cpp-diagnostics
GitHub Login: @corob-msft
Microsoft Alias: corob

@ianclarke1422
For information, see Building an import library and export file. We assume people who run into this particular error are familiar with this material, and aren't looking for a tutorial here.

Thank you for the quick reply, and the link below, but I was able to figure it out on my own, by referencing other internet posts.
I find it surprising that you think that people who run into errors are not looking for a tutorial on how to fix them? If I know how the system works and how to fix it, why would I ever reference the documentation?  Having a page that more or less reiterates the output from the linker is really pretty useless.
But really, thanks for the quick reply.  I was surprised to receive it!
From: Colin Robertson<EMAIL_ADDRESS>Sent: Friday, May 10, 2019 4:06 PM
To: MicrosoftDocs/cpp-docs<EMAIL_ADDRESS>Cc: Ian Clarke<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/cpp-docs] Insufficient info (#1001)
@ianclarke1422https://github.com/ianclarke1422
For information, see Building an import library and export filehttps://docs.microsoft.com/en-us/cpp/build/reference/building-an-import-library-and-export-file?view=vs-2019. We assume people who run into this particular error are familiar with this material, and aren't looking for a tutorial here.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/cpp-docs/issues/1001#issuecomment-491453665, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALZAHRIBD7AMISDALPA77EDPUX5XLANCNFSM4HMGKPPA.


[WIP][experimental] Embed assertion's AST and tokens to make runtime side parser unnecessary

This pull-request aims to embed assertion's AST and tokens to make runtime side parser unnecessary.
Context
The runtime side of power-assert (not a transpilation side) depends on ECMAScript parser (currently acorn) to parse canonical assertion expression at runtime. Browserify embeds the parser into built bundle for web browsers.
Problems
ECMAScript parser is huge. Therefore,

it slows require time down
power-assert built bundle for browsers is huge too

Bundled parser is an ECMA standard compliant one. Therefore,

Cannot handle dialects such as JSX, Flow, etc...
When JSX expression exists inside of assert(), parser causes parse error, power-assert runtime explodes immediately.

Solution

Embed assertion's AST, tokens and its visitor keys to output code, means that they are passed to runtime side.
Now runtime side doesn't have to parse canonical assertion expression since they already have AST, tokens and its visitor keys.

Advantages

Reduce runtime side dependencies and its bundle size. Make runtime loading much faster.
Can handle any dialects such as JSX, Flow, etc... anything we can parse could be visualized on the runtime side

When this pull-req lands, you can write JSX tags inside assertions.
assert(shallow(<ToDoItem item={item} />).find('.item-mark').text() === '✓');

TODO

[x] rough initial design
[x] JSX testcase
[x] spike implementation
[x] reorganize runtime side
[ ] maint other tests
[ ] benchmarking
[ ] brutal refactoring
[ ] a little optimization

This feature might be released with power-assert 2.0.0 (if there are some breaking changes)

Reorganization of runtime side has done. Time to move forward.


error when trying to pip install

I receive the following error when I try to pip install this package:
Building wheels for collected packages: regex  Building wheel for regex (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py bdist_wheel did not run successfully.
  │ exit code: 1
  ╰─> [13 lines of output]
      running bdist_wheel
      running build
      running build_py
      creating build
      creating build\lib.win-amd64-3.10
      creating build\lib.win-amd64-3.10\regex      copying regex_3\__init__.py -> build\lib.win-amd64-3.10\regex
      copying regex_3\regex.py -> build\lib.win-amd64-3.10\regex
      copying regex_3\_regex_core.py -> build\lib.win-amd64-3.10\regex
      copying regex_3\test_regex.py -> build\lib.win-amd64-3.10\regex
      running build_ext
      building 'regex._regex' extension
      error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
      [end of output]

I realize the fix has something to do with some Microsoft C++ libraries, but I couldn't pin point which ones to download and I have limited drive space.  It was easier for me to just download your package manually and use it locally since the regex dependency never came up.  I'm still not sure where you're using it, but maybe consider removing it?

Hey everyone. Took a break from this project but will continue with fixes and new features starting next week!

Yeah, I'm getting the same thing when I try to install, I think we have to download Visual Studio. At least that's what I think.  Not sure though.

It seems like this is a windows specific issue. @V3AI-Seven are you getting the same issues with the regex dependencies?

Yeah, it says stuff about "Building Regex Wheel" and then it says something about Regex and failure. It then mentions that I need to install Microsoft Visual C++ 14.

It also says something about setup.py not being supported.

So did you install the required dependency that the error mentions?
https://visualstudio.microsoft.com/visual-cpp-build-tools/

I have Microsoft Visual C++14, and I'm still getting this error.

I also encountered this problem
So how to solve it?


⚠ Bofrost.lu has degraded performance

In a2f9a92, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1660 ms

Resolved: Bofrost.lu performance has improved in 87338b5 after 6 minutes.


Creating dependabot for dependency updating

Adding dependabot for updating dependencies.

Looks cool, I don't have time to test it but the code looks ok

Approve this PR @guyluz11

Approve this PR @guyluz11

You didn't change the pr to deb branch.
And I can't approve a PR like that if I don't test that it works first.
So just merged it if you testes it

@guyluz11 how come just changing the branch added more files. I didn't added these files. I'll remove soon

Because those files were added to master and not Dev branche
And you forked your brach from master

Ohh okay then I will remove these files in local and push again

This is not the correct way to fix it, you need to resolve the conflicts

I'll resolve conflicts. No problem.

@guyluz11 does it looks fine now.

Looks good good 👍
I think interval: "weekly" will be a lot of work to test it each time manually.
But I guess you are prepared for that and we can always change that


REST API documentation

As a developer and integrator I want to have uptodate API documentation for REST API to integrate DemocracyOS content to other systems.

Although we have a publicly accessible API, we are not currently supporting a Public API. We are planning to do this in the future, in order to easily integrate DemocracyOS data with other systems. Until then, we are not going to make any effort in API documentation.


Updated Maintenance RP extension for GA

Fixed bugs in help and style
Updated index to release instead of preview

This checklist is used to make sure that common guidelines for a pull request are followed.
General Guidelines

[X] Have you run azdev style maintenance locally? (pip install azdev required)
[X] Have you run python scripts/ci/test_index.py -q locally? (executed azdev test maintenance)

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

add to S165.

@gautamd-ms, I saw maintenance RP for CLI command has already been released before https://docs.microsoft.com/en-us/cli/azure/ext/maintenance/maintenance?view=azure-cli-latest. What's the difference between this PR and previous release? I cannot find the source of previous release in this repo, where is the source code repo for the previous release?

@jsntcy, this PR includes fixes in command help docs. The initial code exits in the fork  that @abkmr created but was not merged into the main repo so merging that as part of this PR as well.

@gautamd-ms, thanks for the information. Is it possible that I can just saw what you changed in this PR as reviewers just want to care that part?

@gautamd-ms, could you help answer the questions above?

@jsntcy Please find my responses inline.

@gautamd-ms, thanks for the information.

Is it possible that I can just saw what you changed in this PR as reviewers just want to care that part? (maybe you can split this PR into two PRs, one is just for merging previous release code, the other is for the changes for fix.)
[GD] The previous fork was targeting private preview release and was allowed to publish without the source that did not succeed the static analysis and help validations (see build for details). This release fixes them so splitting into two would result in the same PR. Feel free to review the code as the first checkin if needed.
Do you know why the source code was not merged into this repo last release, but want to merge into this repo this time?
[GD] Previous package was targeting private preview release and our RP is now graduating to GA so adding successfully validated code in this release to primary repo.
I saw currently your wheel file is stored in your storage account, one your source code is merged into this repo, in the future release, your wheel file will be stored in our storage account because our release pipeline will take over it. Is it acceptable for you?
[GD] Yes, that should be fine.

�

what's the usage of res.json?

Refers to: src/maintenance/res.json:22 in 13153ec. [](commit_id = 13153ec10a718a11562b964f8f545742dca0f023, deletion_comment = False)

@gautamd-ms, I added some comments in PR, could you help take a look?

@gautamd-ms, did you have a chance to take a look at the comments?

@jsntcy, @haroldrandom I have updated the PR and made necessary changes. Please take a look when you get a chance. Thanks!

@jsntcy some of the new feedback could have been caught in the initial review itself. Can you confirm that you haven't missed anything else?


[PR] The proj files have been updated to enable SourceLink

CSProj files have been updated to enable SourceLink in your nuget
[This pull request was created with an automated workflow]
I noticed that your repository and Nuget package are important for our .NET community, but you still haven't enabled SourceLink.
We have to take 2 steps:

Please approve this pull request and make .NET a better place for .NET developers and their debugging.
Then just upload the .snupkg file to https://www.nuget.org/ (now you can find the snupkg file along with the .nuget file)

You can find more information about SourceLine at the following links
https://github.com/dotnet/sourcelink
https://www.hanselman.com/blog/ExploringNETCoresSourceLinkSteppingIntoTheSourceCodeOfNuGetPackagesYouDontOwn.aspx
If you are interesting about this automated workflow and how it works
https://github.com/JTOne123/GitHubMassUpdater
If you notice any flaws, please comment and I will try to make fixes manually

Looks interesting. I'm on vacation and won't return till Tuesday. I'll look at this then.


Having the timer on the tab

Description
Currently, when you're using the app, if you want to check the remaining time, you need to go on the webpage.
Improvement
Somtheing cool would be to be able to see the timer on the tab.

i fixed it


Adjusting canvas height based GenotypeTrack height

Not using props on this one so we don't have to spread our code out over classes, as discussed

Can one of the admins verify this patch?

Fixed in the latest PR

Sorry @snaheth , that was a test PR for some build testing and will not be merged.

Can one of the admins verify this patch?


Feature: Support ssh-agent

Fixed #108, implemented new API `SessionBuilder::ssh_auth_sock
Signed-off-by: Jiahao XU<EMAIL_ADDRESS>

This change is

Codecov Report

Merging #109 (6a73631) into master (84e1fab) will decrease coverage by 0.59%.
The diff coverage is 23.07%.

Additional details and impacted files

Impacted Files
Coverage Δ

src/builder.rs
81.99% <23.07%> (-3.09%)
:arrow_down:

Ah, would you mind updating the changelog as well?

Ah, would you mind updating the changelog as well?

Sure, I forgot about that


Theme select

I have added all theme-names to my configuration.yaml file among all my other themes because i have a theme select on my dashboard. These themes are shown on the list, but does not appear when i select it. Is it possible to do this?

What the heck do you mean by

I have added all theme-names to my configuration.yam

This repo is outdated. Please use lovelace-soft-theme instead. It doesn't have different colors, but it's more maintained.


Default branch on Github now is "main"; this conflicts with some links in the repo

Since October 2020 the default branch for Github repositories is main instead of master. Since in the repo and articles there are a few links that rely on "master" this could cause confusion for new users since some things won't work as expected:

release-drafter.yml
test-pypi.yml
The codecov badge in README.md

Perhaps these should be updated to main instead? However on gitlab.com the default branch still remains master so if someone creates the repo there they face the same issues. In any case, a comment in the article would be helpful too.

Thank you for reporting the issue! You are correct that some of the project cruft assumes that default branch is named master, and therefore needs to be fixed when used as a template for repositories using another branch name, like GitHub's new default. There are plans to update the blog and its companion repository for 2021, and this issue will be addressed as a part of that update.
In the meantime, I would like to point you to https://github.com/cjolowicz/cookiecutter-hypermodern-python, which (unlike this repository) was designed as a project template, and is regularly updated. Since 2020.10.15, the project template also works with repositories using the new main branch.


Improve user-defined feature layers performances by creating appropriate indices

We should automatically add/remove indices based on layer schema in MongoDB to improve performances of e.g. table, charts, etc.

Starting from MongoDB v4.2 we can rely on https://docs.mongodb.com/manual/core/index-wildcard/.


Any plans to support Ctrl+C on Windows?

I will be the first to admit that I am not aware of what would be involved to add this signal. 😬
Any one that is more versed in Windows want to chime in?

With a couple minutes of Google.... https://stackoverflow.com/a/52941752

Using windows api like in the example looks like a nice solution.

@danieldaeschle does CTRL-Break work?

I have to test it.
Adam Hopkins<EMAIL_ADDRESS>schrieb am Do., 9. Jan. 2020, 19:17:

@danieldaeschle https://github.com/danieldaeschle does CTRL-Break work?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/huge-success/sanic/issues/1753?email_source=notifications&email_token=AHKTWHFNL2KXNS443FY63ITQ45S3JA5CNFSM4KCOHVV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIRIDCA#issuecomment-572686728,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHKTWHCKMIECAYCZP4YUKNDQ45S3JANCNFSM4KCOHVVQ
.

I don't really feel like adding this functionality into sanic core would be greatly beneficial when there are already widely known alternatives.
Especially when the code solution to this is adding in a special case just for windows.

I had planned to fix this but recently I don't have much time to work on Sanic at all. The problem might be that of terminating the worker processes, so it might already be resolved if you don't use workers or autoreload, and if that is the case, the thing needing implementation is better killing logic (because Windows doesn't have proper signals), e.g. closing child process stdin from parent.


Automatically install dependencies if not installed

To make it nicer for our users, install autocomplete-plus or linter if they aren't installed.
See atom-typescript for ideas https://github.com/TypeStrong/atom-typescript/blob/eec59e111de711653d686794a872730d6994da0d/lib/main/atomts.ts#L237

:+1:

Can we leverage something like:
https://atom.io/packages/update-package-dependencies
?


Specified IP Address Port Mapping Not Working

Describe the bug
I am encountering a problem with port mapping in Docker. In my docker-compose.yml file, I have specified an IP address for port mapping, using the format <IP_ADDRESS>:80:80. However, this configuration does not seem to be working as expected. The port mapping is not successfully redirecting traffic from the specified host IP address to the Docker container. I am looking for assistance to understand why this specified IP address port mapping is not functioning correctly.
However, it works as intended in Docker Desktop.
To Reproduce
First case
version: '3.9'

services:
  web:
    image: nginx
    ports:
      - "<IP_ADDRESS>:80:80"
    networks:
      mynet:

networks:
  mynet:
    driver: bridge
    ipam:
      driver: default
      config:
        - subnet: <IP_ADDRESS>/24
          gateway: <IP_ADDRESS>

$ docker-compose up -d

Connect to http://<IP_ADDRESS>
Second case
version: '3.9'

services:
  web:
    image: nginx
    ports:
      - "<IP_ADDRESS>:80:80"

# Add an alias IP address <IP_ADDRESS> to the loopback interface (lo0)
$ sudo ifconfig lo0 alias <IP_ADDRESS>
$ docker-compose up -d

Expected behavior
No response
Diagnostic report (REQUIRED)
OrbStack info:
Version: 1.3.0
Commit: c7cc1bd78adc76441a91befa2a50c0119c9d4703 (v1.3.0)
System info:
macOS: 14.3 (23D56)
CPU: amd64, 16 cores
CPU model: Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
Model: MacBookPro16,1
Memory: 64 GiB
Full report: https://orbstack.dev/_admin/diag/orbstack-diagreport_2024-01-27T19-14-08.728527Z.zip

Screenshots and additional context (optional)
No response

Duplicate of #291
Consider using OrbStack domains instead, as suggested in that issue.


Project Cars 2 demo has black screen then crashes

Project Cars 2 demo
The game starts with a black screen and crashes a short while later.
System information

GPU: GTX 1080
Driver: 391.35
Wine version: Native Windows 10
DXVK version: 75c928f

Apitrace file(s)
apitrace
Log files
d3d11.log
dxgi.log
vulkanlog.txt
There are 2 graphics pipelines not compiling.

While almost certainly doesn't cause the crash, there's a bug in my GenerateMips implementation. Guess I'll have to create and use render passes manually instead of relying on Vulkan's blitting.
The messages about format mismatches should be irrelevant, Final Fantasy XIV has that issue as well and seems to render properly on Nvidia (see #208).

Looking at your trace again it seems that either apitrace doesn't pick it up or something is really broken. The game never actually writes any data to its constant buffers for some reason, which is why nothing gets rendered.

It's the apitrace that is broken. The game itself on DXVK renders fine until I get to the map loading screen where it will crash near the end. So, I'm not sure how we are going to fix this without an apitrace.

does dxvk 0.60 make a difference?

Closing for duplicate issue https://github.com/doitsujin/dxvk/issues/375


STATUS_BREAKPOINT error in newer versions of Chromium

Hi there! Somewhere in the last few months Chromium seems to be upset with the module and dumps the browser out to a
STATUS_BREAKPOINT error. You can't catch anything in the console or the server side to support the problem.
Chrome: Version 128.0.6613.114 (Official Build) (64-bit)
Edge: Version 128.0.2739.54 (Official build) (64-bit)
I had a laptop with an old version of Edge (125) and it seemed to be working fine.
Also, you can seem to keep reloading the browser and 1 out of 4 times it will load.
I finally disabled this module and it seems to launch Foundry every time. THIS MODULE IS AMAZING BTW!

Just wanted to bump this; I am also experiencing the same issues. In the mean time I was able to get around it using Brave as my browser.

Same as above, just a bump, the module is great but it crashes foundry, now i haven't used in firefox

Let me know if these issues persist on the newer version of the module.

Strangely enough, I am still on v1.5.3 of the mod, and I refreshed the world about 10 times and don't run into the issue any more. Perhaps it was a problem with particular versions of Chrome's browser.


Minitest for ISERDES (networking SDR and DDR)

This is a minitest for operation of ISERDES primitives. It tests networking SDR and DDR modes (see the README.md file).
Due to specific timing requirements of ISERDES primitives the design has to use BUFRs to generate divided clock. Generating this clock using logic led to faulty data reception.

@mkurc-ant : Can you try the suggestion in https://github.com/SymbiFlow/prjxray/issues/996#issuecomment-529526113 and see if we can avoid the loopback!

I've been trying it today while creating OSERDES minitest. But I'm still playing with BUFR etc. to make Vivado P&R successfully.


Update webui to 1.6.5

No fix required.
Your adapter fails std tests due to reasons discussedxearluer.

RE-CHECK!


InputNumber: assign new value before change event firing

fixs:#13981
Please make sure these boxes are checked before submitting your PR, thank you!

[ ] Make sure you follow Element's contributing guide (中文 | English | Español).
[ ] Make sure you are merging your commits to dev branch.
[ ] Add some descriptions and refer relative issues for you PR.

先nextTick凑合一下吧。 https://github.com/ElemeFE/element/issues/13981#issuecomment-464727520
input-number彻底修要重构，currentValue那一系列都要删掉。并且允许绑定 undefined/null/'' ，现在绑定这些值会强制设置成0: https://jsfiddle.net/vs6knzrd/


Restore on deactivate restore wrong state

"restore on deactivate" feature store states after a state change event causing problems with scenes where a entity do more than one state change resulting in integration restoring a "bad" state. (Example, a bulb that informs two state changes for turn on and color change).
A better approach could be grab and store state just before a scene is applied. This may need more tweaks like check what attributes may be changed by the scene and grab those attributes to further restore action.

I was actually thinking it might be better to have a configuration for the 'off' state of the stateful state switch that optionally invokes another scene so that restoring can never be wrong.   Maybe there is a bug but some of these scenes can get quite complicated and having an off transition would make things simpler.
@hugobloem, if this is something you think would be useful I'd be happy to push a PR time permitting.

You're right restoring to a previous state is quite complicated and produces some unwanted results with some hardware. The problem is that some lights (or other entities) report their state when they are still transient, causing the integration to think that is the last state of the entity. This is entirely dependent on the hardware and is thus quite hard to solve.
Having a pre-defined state that is returned to (rather than the current off or previous-state) could be a good addition to solve this issue.
I am happy to work on this or the other the rounding you mentioned in #106 and I have time to develop it this weekend. Let me know if you would like to develop either issue and we can split up the development.

Hi Hugo, I don't have tine this weekend but if you need something later, I can help.  BTW, this custom integration is awesome and something sorely missing in HA, a huge Hugo thank you to you!

Hi Hugo, please pick one of the issues and I'll do the other, let me know so we don't duplicate. For this one WRT to returning to a state on off I would think we would have an option to set a scene and pick a scene from a dropdown.  There may also be an adjacent task if the integration doesn't refresh its list if a scene is added/removed in order to not require complete reload manually.

Hi Bill, busy week here sorry. I can work on #106 you could do this one, if you're still interested.

Sounds good Hugo

Fixed in 1.60+