ovn/docker-overlay: stretch Logical_Switch across multiple clusters

By default this plugin creates a logical switch on per key-value
store basis. The plugin derives the logical switch name from the
NetworkID, which is cluster specific. When this option is enabled,
the logical switch name is derived from IP subnet and the subnet's
context. This way a logical switch may stretch across multiple
clusters managed by different key-value stores. The context
provides for overlapping address space.
Signed-off-by: Paul Greenberg<EMAIL_ADDRESS>

Hi @shettyg , I noticed you wrote the initial version of the plugin. Could you please review this pull request? I would appreciate your feedback and insights.

Hi @shettyg , I noticed you wrote the initial version of the plugin. Could you please review this pull request? I would appreciate your feedback and insights.

I will take a look. Lots of new code, so it will take a few days.

I will take a look. Lots of new code, so it will take a few days.

@shettyg , thank you! :-) There are still some additional work there, e.g. key-value store cleanups and synchronization of ports that were removed without Libnetwork calls, e.g. power off, or kill -9 <docker-PID>. I just want to get a head start, since there is a lot of code 😄

@shettyg , I also tried leaving the original plugin flow intact. The majority of my additions are optional.

Doesn't build:

../Documentation/howto/docker.rst:327:
$ echo -n "default-<IP_ADDRESS>/24" | sha256sum
See above for uses for "echo -n", which is non-POSIX
and does not work with all shells.  Use "printf" instead.

@greenpau
Sorry about the delay. I forgot about this (Not having a good TODO list is to blame). Overall, I see that you have thought long and hard to make driver "local" and changing it to fit your use case.  But a change which modifies OVN flow table out of band is something that cannot be maintained in the repo. The OVN flow tables constantly change. The table numbers change with every new feature.
I wrote the docker driver when docker was all the hype. But, after the initial commit, we found it very hard to make the driver flexible to get more data from docker command-line.  Doing a lot of tricks in the background is a little less sustainable in the long run to maintain and so, we decided against pursuing the idea to make the driver use more OVN features.

But a change which modifies OVN flow table out of band is something that cannot be maintained in the repo.

@shettyg , even when the features are disabled by default? By default, there are no changes to how the plugin works today.

@greenpau
Yeah. The ideal thing for us is to only handle docker APIs and convert it to OVN APIs. Simple tricks like using IP subnets as network names are okay. Using any backdoor to Docker too is bound to create issues as that may change from one version to another. Using backdoor to OVN is definitely bound to create issues.

The primary issue is maintainability of code. We don't want wrong code hanging in.

@shettyg , that's fair. Since this PR has multiple features and other additions (e.g. logging, exit handling, cleanups), which of them you consider not a fit?

The ideal thing for us is to only handle docker APIs and convert it to OVN APIs.

The practical aspect of it is that once a user powers down a host (or the host crashes) without proper shutdown and it will result in OVS port being abandoned, OVN NB database out-of-sync, etc. Thus, any component that is related to the plugin must be in constant sync, i.e. OVS, Docker, OVN NB. It almost always requires a "shim."
From my perspective, the gap in the "overlay" plugin is that it forces a user to adopt Docker Swarm methodology. The same is true about "underlay" plugin, where you have to adopt OpenStack. It is a move away from modular (which I personally prefer) and move towards "being a part of" Docker Swarm, OpenStack, etc.
For example, why would anyone use OVN IPAM when it is available natively from Docker? On the other hand, if OVN IPAM had a Docker LibNetwork plugin of IpamDriver type, then Docker Swarm would not have been necessary and OVN IPAM would have been used instead.

Doesn't build:

@blp , fixed.

pychecker errors:

../python/ovs/util.py:125:1: E302 expected 2 blank lines, found 1
../python/ovs/vlog.py:135:9: E266 too many leading '#' for block comment
../python/ovs/vlog.py:136:9: E266 too many leading '#' for block comment
../python/ovs/vlog.py:143:48: E703 statement ends with a semicolon

that's fair. Since this PR has multiple features and other additions (e.g. logging, exit handling, cleanups), which of them you consider not a fit?

For logging, have you looked at vlog.info, vlog.dbg etc? vtep/ovs-vtep.in has some examples.
There are many enhancements we can take. But, it would be nice, if they are split into multiple commits and it is easy pick them and review them. May be cleanup as a commit first and then slowly add new features?

From my perspective, the gap in the "overlay" plugin is that it forces a user to adopt Docker Swarm methodology. The same is true about "underlay" plugin, where you have to adopt OpenStack. It is a move away from modular (which I personally prefer) and move towards "being a part of" Docker Swarm, OpenStack, etc.

I agree that the plugin as it is now is only useful as a POC for someone to look at then integrate OVN with their inhouse docker infrastructure.

For logging, have you looked at vlog.info, vlog.dbg etc?

@shettyg , yes. My thinking was that since the service is managed by systemd (since added systemd unit file), it would be great to have both vlog and stdout. This way journald has all the entries related to the plugin and related services. Appologies for my not knowing/understanding this, are you saying vlog.info can do stdout/stderr?

But, it would be nice, if they are split into multiple commits and it is easy pick them and review them. May be cleanup as a commit first and then slowly add new features?

@shettyg , I agree, I will split. That's why I want to get feedback on what might be useful for the project. As far as I understand right now, you are not in favor of IP lookups and Docker calls.

is now is only useful as a POC for someone to look at then integrate OVN with their inhouse docker infrastructure.

@shettyg , 💯 , hence all the work to make it to "alpha" 😄

pychecker errors ...

@blp, fixed.
Also, there are other failing tests:
2020: simple idl, initially empty, no ops - Python2 - tcp6 FAILED (ovsdb-idl.at:219)
2031: simple idl, initially empty, various ops - Python2 - tcp6 FAILED (ovsdb-idl.at:226)
2042: simple idl, initially populated - Python2 - tcp6 FAILED (ovsdb-idl.at:304)
2053: simple idl, writing via IDL - Python2 - tcp6    FAILED (ovsdb-idl.at:335)
2064: simple idl, writing via IDL with unicode - Python2 - tcp6 FAILED (ovsdb-idl.at:366)
2077: simple idl, handling verification failure - Python2 - tcp6 FAILED (ovsdb-idl.at:412)
2088: simple idl, increment operation - Python2 - tcp6 FAILED (ovsdb-idl.at:443)
2099: simple idl, aborting - Python2 - tcp6           FAILED (ovsdb-idl.at:455)
2110: simple idl, destroy without commit or abort - Python2 - tcp6 FAILED (ovsdb-idl.at:469)
2121: simple idl, conditional, false condition - Python2 - tcp6 FAILED (ovsdb-idl.at:483)
2132: simple idl, conditional, true condition - Python2 - tcp6 FAILED (ovsdb-idl.at:499)
2143: simple idl, conditional, multiple clauses in condition - Python2 - tcp6 FAILED (ovsdb-idl.at:515)
2154: simple idl, conditional, modify as insert due to condition - Python2 - tcp6 FAILED (ovsdb-idl.at:537)
2165: simple idl, conditional, modify as delete due to condition - Python2 - tcp6 FAILED (ovsdb-idl.at:553)
2176: simple idl, conditional, multiple tables - Python2 - tcp6 FAILED (ovsdb-idl.at:580)
2187: self-linking idl, consistent ops - Python2 - tcp6 FAILED (ovsdb-idl.at:619)
2198: self-linking idl, inconsistent ops - Python2 - tcp6 FAILED (ovsdb-idl.at:663)
2209: self-linking idl, sets - Python2 - tcp6         FAILED (ovsdb-idl.at:711)
2220: external-linking idl, consistent ops - Python2 - tcp6 FAILED (ovsdb-idl.at:761)

I ran once of them, it fails:
## ------------------------------ ##
## openvswitch 2.9.90 test suite. ##
## ------------------------------ ##
2020: simple idl, initially empty, no ops - Python2 - tcp6 skipped (ovsdb-idl.at:219)

## ------------- ##
## Test results. ##
## ------------- ##

0 tests were successful.
1 test was skipped.

The error is caused by:
OVSDB_CHECK_IDL([simple idl, initially empty, no ops],
  [],
  [],
  [000: empty
001: done
])

What is the best way to troubleshoot this? i.e. there is some kind of comparison, how to output what is that baseline being compared to?

@greenpau Tests generate a testsuite.log with details.  You can read that for full information.
Maybe IPv6 is disabled on your test machine in a way that the tests didn't understand until now.  There was just a fix for that: https://github.com/openvswitch/ovs/commit/f7979b1181132619ea591f2c9e76fa8c37adeb54

Maybe IPv6 is disabled on your test machine in a way that the tests didn't understand until now. There was just a fix for that: f7979b1

@blp , it is failing in Travis too.

@blp , nevermind, the change was committed today. Will re-sync.


How to remove the corner layout and row headers?

As of now i have to provide the tableView a corner layout, and row headers which i don't need in some cases. I just want my column headers only which i can populate from my datasets. Can this be done or is there any way to hide the row headers and corner layout ?
Thanks.

Hi @ankurt-optimus
Unfortunately, you can not hide the row headers. Because it helps to the TableView in some calculations.
This issue has already been written in my notes. But I was waiting for some request (like yours) to get rid of from the dependency.
Just wait for the next release.
Thanks

Also be able to hide column headers please.

@DamonChen117  Ok I have written down your request too.

Please have you remove the dependency on the rowheader? can we now hide the row header

I dont know If you want to hide/show it programmatically, but..
Why don't you set default_row_header_width in dimens.xml to 1dp?
   <dimen name="default_row_header_width">1dp</dimen>

I've tried v.rowHeaderWidth = 0 (in Kotlin and v is the table view) and it worked :+1:

@ammaratef45 thank you


[ExplorerService] Error fetching native apps data

I[ExplorerService] init()
[ExplorerService] Error fetching native apps data
[ExplorerService] Error fetching native apps data
Exception: FormatException: Unexpected character (at character 1)
Bad Request

Hello @kishanflutter @LorenzoPorrega, it should be solved already, please let us know!
https://status.walletconnect.com/incidents/btx0p36pywqd


Page Preview like in C/SIDE

Any plans on conceiving a Page Preview in VSCode like we have in C/SIDE?
The question was posed during one of my workshops. The relevance wasn't just the visual display, but more about being able to click on elements in the page object seeing it's visual counterpart and vice versa like in C/SIDE page designer.

This is something we would eventually like to implement but not a high priority at the moment. I will use this issue for tracking progress on this suggestion.

This is actually a duplicate of https://github.com/Microsoft/AL/issues/400


Fix fast tokenizer swallows prefix space when there are too many white spaces

The previous detokenization can not handle many empty tokens for LlamaTokenizer such as upstage/SOLAR-0-70b-16bit model. The incrementally decoding output may lack a white space in this case.
This PR does not introduce BC breaking since a new function named detokenize_incrementally is implemented.
However, full tests are required.

Could you provide an example to reproduce the issue?

Could you provide an example to reproduce the issue?

Yes, the case is already covered in unit tests now. This is an example for main branch:
def test_tokenizer(model_path, input):
    from lmdeploy.tokenizer import HuggingFaceTokenizer
    tokenizer = HuggingFaceTokenizer(model_path)
    encoded = tokenizer.encode(input, False)
    output = ''
    offset = 0
    for i in range(1, len(encoded) + 1):
        decoded = tokenizer.decode(encoded[:i], offset)
        if decoded.endswith('�'):
            continue
        output += decoded
        offset = i
    assert input == output, 'input string should equal to output after enc-dec'

test_tokenizer('01-ai/Yi-34B-Chat', 'a    b')

Did not influence the performance of profile_throughput.py.


Support for comma separated multiple version requirements

Hi, thanks for the great project -- really awesome tool!
I encountered an error because in my pyproject.toml I specify some dependency ranges using the comma separated syntax which is supported by poetry as well as pdm and documented in PEP440. For example, this is a valid PDM pyproject.toml:
[project]
name = "test_pcu"
version="0.0.1"
dependencies = [
    "svglib>=1.5.0,<2.0.0",
]
requires-python = ">=3.11"
license = {text = "MIT"}

However, pip-check-updates fails to parse this, giving this error:
Traceback (most recent call last):
  File "/usr/local/bin/pcu", line 8, in <module>
    sys.exit(run())
             ^^^^^
  File "/usr/local/lib/python3.11/site-packages/pip_check_updates/__main__.py", line 70, in run
    deps = load_dependencies(req_path, not no_recursive, extra)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/pip_check_updates/parser.py", line 167, in load_dependencies
    load_toml(deps, f, p, pyproject=True, extras=extras)
  File "/usr/local/lib/python3.11/site-packages/pip_check_updates/parser.py", line 111, in load_toml
    packages = parse_requirements_lines(config.get(package_key, []))
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/pip_check_updates/parser.py", line 101, in parse_requirements_lines
    requirements = [
                   ^
  File "/usr/local/lib/python3.11/site-packages/pip_check_updates/parser.py", line 102, in <listcomp>
    get_current_version(clean_requirements_line(requirement_line))
  File "/usr/local/lib/python3.11/site-packages/pip_check_updates/version.py", line 52, in get_current_version
    name, current_version = split_line
    ^^^^^^^^^^^^^^^^^^^^^
ValueError: too many values to unpack (expected 2)

@all-contributors please add @radusuciu for bug

Workaround in the meantime: specify dependencies with ~= instead.


3 Minute Limit Workaround?

Thanks for porting this. Much appreciated.
Is there any way to get around the 3 minute maximum for inputs?

Hi!
Currently no, but we could increase it as this value quite arbitrary.
If you're building from source you can easily modify it by setting mMaxDuration in NeuralNote/PluginSources/PluginProcessor.h to suit your need.

I second that! The 3 minutes limit is frustrating, especially when your song is 3m01 long, lol.
Could this limit be removed altogether? There are songs that are longer than 10 minutes.
For now, the easy workaround is to cut the original audio in two and work with each part.

Hi, Yes I'm currently working on it in #38. The limit will be removed both for recorded audio and dropped files.
This specific point should be ready soon but I want to add more improvements/features before the next release that is scheduled for sometime in July/August

There is no 3 minute limit anymore.


Typo in getting-started

There's a typo in the sentence with the word "anything":
It could be a new encrypted chat message, a folder-from-a-friend. It could be practically anyting.

https://keybase.io/getting-started

Thank you for your report!


[component]: Back to top

Description
No response
Design
https://www.figma.com/design/JIT5AdGYqv6bDRpfBPV8XR/Foundations-%26-Components-Next-Level?node-id=18-11
Tokens

[ ] Tokens for this component are ready

Tasks
### 💻 Tasks
- [ ] Review Design (All states present? Possible to implement?)
- [ ] HTML/CSS implementation
- [ ] Web component implementation
- [ ] Documentation in Storybook
- [ ] Unit tests
- [ ] End to end tests
- [ ] Visual regression tests
- [ ] Design review

Resolution: build back to top button for the moment, other use cases are interesting but need to be requested or discovered in a later step.

@gfellerph I'd recommend to generate specific tokens for that one as it might look different than a secondary icon button somewhen. We can just connect them semantically to whatever we used for the secondary icon button so it looks the same for now. Further there is atm no such thing as a foundations/elevation.

@Vandapanda I would strongly recommend to reuse where we have the possibility. Dedicated tokens can be added whenever necessary.

post-floating-button-size-outer: 56px,
post-floating-button-size-icon: 24px,
post-floating-button-position-right: 40px,
post-floating-button-position-bottom: 40px,
post-floating-button-border-radius-round: 100%,
post-floating-button-border-width: 2px,
post-floating-button-enabled-border: #050400,
post-floating-button-enabled-fg: #050400,
post-floating-button-enabled-bg: white,
post-floating-button-hover-border: #504f4b,
post-floating-button-hover-fg: #504f4b,
post-floating-button-hover-bg: white,
post-floating-button-translate-y: 8rem

@sandra-post Ready for Design Review -> https://preview-3991--swisspost-design-system-next.netlify.app/ :)

Icon used is not the final one
Animation is indicative


trigger type components compositions doesn't work

it's impossible to use the same element to trigger both a tooltip and a dropdown menu.
(see attacked code sandbox)
to make it work you need to put pass refs to the children (which means wrapping tooltip/dropdown each in separate components)
option 1 doesn't work. option 2 works but it seems like 1 should work as well.
live example

These examples are behaving correctly because you have applied asChild to the Dropdown.Trigger and its child is the Tooltip.Root so it will become the Tooltip.Root.
The reason your option 2 example works is because you are redirecting those props that asChild forwards onto your Tooltip.Trigger which is the correct way to achieve it. You don't need to do React.cloneElement yourself though because asChild does that for you https://codesandbox.io/s/suspicious-noether-uclyg?file=/src/App.js
In future if you're having trouble with syntax, please can you raise a Discussion instead? We can convert it to an issue if necessary from there.


Bug in rules 980120 and 980150: TX:MONITOR_ANOMALY_SCORE does not exist

Describe the bug
The Rule 980120 and Rule 980150 only match if the chained rule SecRule TX:MONITOR_ANOMALY_SCORE "@gt 1" matches. However, I could not find where that variable is set.
This basically breaks rules 980120 and 980150 as the chained condition is never satisfied.
Aside from these two rules, I could not find any other reference to or usage of the variable TX:MONITOR_ANOMALY_SCORE.
Your Environment

CRS version (e.g., v3.2.0): v3.3.0

Seems leggit. Thank you for reporting. Closing this in favor of PR #1898.


Delete coalesceSR, coalesceEJ, coalesceTJ

Depends on #3919

From what I saw yesterday, I figured we can also delete a large part of coalesceQC in Coalesce[QScriptCore] here.
We mostly need to keep the LeftShift(Reduce(...), ...)  rewrite since this rewrite removes UnshiftMap. The other rewrites are not doing much and its are green without them..

@jsantos17 agreed, that's exactly what I've already done locally :) PR incoming shortly.

@jsantos17 actually don't merge this PR. The InterpretedRead rewrite isn't getting hit :(

We need to add a test suite to make sure we generate InterpretedRead in cases when we should be. Else it will be all too easy to accidentally introduce regressions.


Fixes two problems, needing to use indexers on a dynamic, and a logic…

… error that prevented the durable log files from being processed.
This PR fixes two issues in ElasticsearchLogClient.cs.

The first is similar to PR #264 to address the properties on a dymanic using index access instead of properties.  For some reason this property access doesn't work.
The second is a logic error the stops the log files from being processed.

The first problem is with how the code uses dynamic.
A dynamic variable is just something that can hold any type of object.  It is not automatically an ExpandoObject, which you can access with both indexer and property syntax.
In this case the type of the object in the dynamic variable is a Dictionary<string, object>, so only indexers can be used, not property syntax access.

Thanks for the PR!

When the will be the release of 8.1 version?

This seems not to be in 8.2 either - @mivano do you have an ETA for release of this fix?  Thanks

Due to some versioning issue, this will be 8.4, which is just pushed to nuget.


Tooltip Blinking

Every single time I hover over something that has a tooltip, it blinks. The tooltip like magically disappears, this is so odd I have no idea.
https://i.gyazo.com/c57b3c1746e0f490ec78a6f37484bdea.gif
I am using the latest stable build:
Godot_v2.0.3_stable_win64.exe
I also changed the tooltip delay to 3 seconds, 0.7 seconds, to any value.. It doesn't seem to have any effect. Not sure what else to report :P

Funny, I get the same thing but for me the tooltip at least hangs around for maybe 10 seconds before it goes off, then back on for another 10.

@vjrossi. Haha, I just had it where the tooltips were showing instantly even though I had it set to 0.7. And it started to lag the screen. I just re-started Godot and it went back to the normal blinking. Weird as heck!

Not sure if this issue is related to windows build, but can't reproduce on Ubuntu 16.04

Releated/dupe of #3835?

@bojidar-bg Yeah, sorry I forgot to  search :( I applied a gif though.
I just restarted my computer and it's NOT happening now. I'm stumped!

archiving because it's duplicate of https://github.com/godotengine/godot/issues/3835


Refactoring of use of Throwables.propagate.

As guava's document says, adding throw to Throwables.propagate can let
compilers know that following statements after the call are unreachable.
Behavior doesn't change because Throwable.propagate never returns.

👍


Loading an email template doesn't seem to work

I'm trying to send an email from the controller of a single page and I can not get the mail template to be sent. I've tried to load it using the following code:
$mailService = $this->app->make('mail');

$mailService->addParameter('donnees', $donnees);
$mailService->load('template');

$mailService->setTesting(false);
$mailService->setSubject(t('Subject'));
$mailService->to('mail@text.fr');
<EMAIL_ADDRESS>'Email');

echo $mailService->sendMail();

But the body of the mail is empty. Setting the body by using $mailService->setBodyHTML('Body'); does work. Is there something I can do to solve this issue?
C5 installation:

Core Version - 8.6.0a2
Version Installed - 8.6.0a2
Database Version -<PHONE_NUMBER>0000
Apache/2.4.46 (Unix) OpenSSL/1.1.1d
PHP 7.4.13

Sorry for keeping this issue open, I solved it like so:
<?php
ob_start();
?>
    HTML template
<?php
$bodyHTML = ob_get_clean;

Thanks for the help.


Is there a way to close Room and Kick every one out?

Hi,
Just wanted to know if there is a way for creator of the room to close room, shut the entire session and kick every participants out??

Did you set connection.autoCloseEntireSession to true?
Here is a link to the usage

I need a user to be able to close Room and force every out, even if this user has not created the room, but only a participant!

Does the function you want make all users leave the room if any participants leave the room?
If it is, try this.

connection.onleave = function(event) { connection.send({type: "allUsersKick"}); };
connection.onmessage = function(event) {      if(event.data.type === "allUsersKick"){           connection.closeSocket();           connection.getAllParticipants().forEach(function(pid) {                 connection.disconnectWith(pid);           });      }  };
I hope it helps.


Configuring and starting a Wash cycle

I am not sure if I just overlooked something, but I would like to start a washing cycle directly though home assistant and maybe also be able to set the finish time.

Yes, I would like something like this too. I tried to make an script with home assistant visual editor but I cannot not getting anything else than a "beep" on my washing machine with no effect. This means I'm on the right way but some help would be fine!
I tried to set on my machine, synthetic program with 40ºC and 1200rpm but it doesn't make any change on the washing machine panel (deleted ids for security)
`alias: alias
sequence:

device_id: ...
domain: select
entity_id:  ...
type: select_option
option: device_state_on
device_id:  ...
domain: select
entity_id:  ...
type: select_option
option: program_synthetics
device_id:  ...
domain: select
entity_id:  ...
type: select_option
option: temperature_40
device_id:  ...
domain: select
entity_id:  ...
type: select_option
option: 1200rpm
icon: mdi:washing-machine
mode: single
`

Are you able to start the washing cycle or set a finish time in the mobile app?

Yes it's possible. You need to select the remote control mode, it's basically like starting a program from the Maschine but without selecting all options. Then in the app you can basically choose as if you would use the dial or even tell what's kind of clothes are in the drum and it gives you some options for programs.
But even just starting a program would be a great addition to the integration. The other features are not really needed.
tldr: yes a core feature of the app.

I would appreciate this feature, too. I'd use it for starting the washing machine once the solar panels begin feeding power into the grid.
In the app you can set the program with all the options you already have in there (switch and select options). Maybe the select.waschmaschine_zusatnd (this is how it is called in my configuration) would do the job already?

I really want this for my dishwasher as well, and in fact I noticed with the dishwasher when I set a program on the app with time delay, some of the controls change in HA. In the screenshot, you can see “State” is set to “time delay active” but what I have noticed is that if I turn on and place the dishwasher into app mode, but then try to change these control settings on in HA instead of opening the app, nothing happens.

Any suggestions welcome!

So I tried with my Beko laundry. When I set it in the remote control state I can set the program etc like pet hair removal (Tierhaarentfernung) on the controls. And when I set the state (Zustand) to "Running" (Läuft) it starts immediately.

So I tried with my Beko laundry. When I set it in the remote control state I can set the program etc like pet hair removal (Tierhaarentfernung) on the controls. And when I set the state (Zustand) to "Running" (Läuft) it starts immediately. But setting the laundry first into the remote control sate is essential.

This does work you are right, but only useful to start the cycle at that time, I was hopping to be able to use the delay function on the dishwasher. I can select the state to Time Delay Active, but there is no way of setting the time delay. I tried building an automation to set and Start the cycle, the pause it. Then at a set time (when my electricity is cheaper) start it, but when paused for more than 3min the dishwasher turns off and Wi-Fi connection is lost.
any other suggestions are welcome! Is there a way to set the time delay?

I have a beko washing machine with bluetooth connection, I use this workaround and it works for me, I use an script that configure the wash program settings, then the script sets the state in running mode,  waits 3 seconds and the script changes the state to pause mode, at this moment I can wait all the time I want to set the washing machine state in running mode and the selected program will continue his process ( I did this last step changing the state manually and automatically with an script and both ways work).

You're right. On my Beko laundry I even can't set a delay time in the controls. Just see in the sensors if one is set. Although in the Homewhiz app I can't set a delay time just a time when it should be finished.

I'll close this, as you seem to all have found a solution 😊


panic on merge of date term in a json field with indexed position

thread 'merge_thread_0' panicked at 'assertion failed: `(left == right)`
  left: `0`,
 right: `1`', /home/trinity/dev/tantivy/bff7c58/src/postings/serializer.rs:203:13
stack backtrace:
   0: rust_begin_unwind
             at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/std/src/panicking.rs:593:5
   1: core::panicking::panic_fmt
             at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/core/src/panicking.rs:67:14
   2: core::panicking::assert_failed_inner
   3: core::panicking::assert_failed
             at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/core/src/panicking.rs:229:5
   4: tantivy::postings::serializer::FieldSerializer::write_doc
   5: tantivy::indexer::merger::IndexMerger::write_postings_for_field
             at /home/trinity/dev/tantivy/bff7c58/src/indexer/merger.rs:626:29
   6: tantivy::indexer::merger::IndexMerger::write_postings
             at /home/trinity/dev/tantivy/bff7c58/src/indexer/merger.rs:658:17
   7: tantivy::indexer::merger::IndexMerger::write
             at /home/trinity/dev/tantivy/bff7c58/src/indexer/merger.rs:766:9
   8: tantivy::indexer::segment_updater::merge
             at /home/trinity/dev/tantivy/bff7c58/src/indexer/segment_updater.rs:125:20
   9: tantivy::indexer::segment_updater::SegmentUpdater::start_merge::{{closure}}
             at /home/trinity/dev/tantivy/bff7c58/src/indexer/segment_updater.rs:518:19
  10: <core::panic::unwind_safe::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once
             at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/core/src/panic/unwind_safe.rs:271:9
  11: std::panicking::try::do_call
             at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/std/src/panicking.rs:500:40
  12: std::panicking::try
             at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/std/src/panicking.rs:464:19
  13: std::panic::catch_unwind
             at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/std/src/panic.rs:142:14
  14: rayon_core::unwind::halt_unwinding
             at /home/trinity/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-core-1.12.0/src/unwind.rs:17:5
  15: rayon_core::registry::Registry::catch_unwind
             at /home/trinity/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-core-1.12.0/src/registry.rs:366:27
  16: rayon_core::spawn::spawn_job::{{closure}}
             at /home/trinity/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-core-1.12.0/src/spawn/mod.rs:97:13
  17: <rayon_core::job::HeapJob<BODY> as rayon_core::job::Job>::execute
             at /home/trinity/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-core-1.12.0/src/job.rs:169:9
  18: rayon_core::job::JobRef::execute
             at /home/trinity/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-core-1.12.0/src/job.rs:64:9
  19: rayon_core::registry::WorkerThread::execute
             at /home/trinity/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-core-1.12.0/src/registry.rs:859:13
  20: rayon_core::registry::WorkerThread::wait_until_cold
             at /home/trinity/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-core-1.12.0/src/registry.rs:793:26
  21: rayon_core::registry::WorkerThread::wait_until
             at /home/trinity/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-core-1.12.0/src/registry.rs:768:13
  22: rayon_core::registry::WorkerThread::wait_until_out_of_work
             at /home/trinity/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-core-1.12.0/src/registry.rs:817:9
  23: rayon_core::registry::main_loop
             at /home/trinity/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-core-1.12.0/src/registry.rs:922:5
  24: rayon_core::registry::ThreadBuilder::run
             at /home/trinity/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-core-1.12.0/src/registry.rs:52:18
  25: <rayon_core::registry::DefaultSpawn as rayon_core::registry::ThreadSpawn>::spawn::{{closure}}
             at /home/trinity/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-core-1.12.0/src/registry.rs:97:20

with some printf debugging I found the document causing the crash to be
{
  "id": "21559270770",
  "type": "IssueCommentEvent",
  "actor": {
    "id": 26881592,
    "login": "cenk1cenk2",
    "display_login": "cenk1cenk2",
    "gravatar_id": "",
    "url": "https://api.github.com/users/cenk1cenk2",
    "avatar_url": "https://avatars.githubusercontent.com/u/26881592?"
  },
  "repo": {
    "id": 320717183,
    "name": "cenk1cenk2/nestjs-tools",
    "url": "https://api.github.com/repos/cenk1cenk2/nestjs-tools"
  },
  "payload": {
    "action": "created",
    "issue": {
      "url": "https://api.github.com/repos/cenk1cenk2/nestjs-tools/issues/675",
      "repository_url": "https://api.github.com/repos/cenk1cenk2/nestjs-tools",
      "labels_url": "https://api.github.com/repos/cenk1cenk2/nestjs-tools/issues/675/labels{/name}",
      "comments_url": "https://api.github.com/repos/cenk1cenk2/nestjs-tools/issues/675/comments",
      "events_url": "https://api.github.com/repos/cenk1cenk2/nestjs-tools/issues/675/events",
      "html_url": "https://github.com/cenk1cenk2/nestjs-tools/pull/675",
      "id":<PHONE_NUMBER>,
      "node_id": "PR_kwDOEx3Bf84yF0kH",
      "number": 675,
      "title": "chore(deps): update dependency @webundsoehne/nestjs-util to v5 [skip ci]",
      "user": {
        "login": "renovate[bot]",
        "id": 29139614,
        "node_id": "MDM6Qm90MjkxMzk2MTQ=",
        "avatar_url": "https://avatars.githubusercontent.com/in/2740?v=4",
        "gravatar_id": "",
        "url": "https://api.github.com/users/renovate%5Bbot%5D",
        "html_url": "https://github.com/apps/renovate",
        "followers_url": "https://api.github.com/users/renovate%5Bbot%5D/followers",
        "following_url": "https://api.github.com/users/renovate%5Bbot%5D/following{/other_user}",
        "gists_url": "https://api.github.com/users/renovate%5Bbot%5D/gists{/gist_id}",
        "starred_url": "https://api.github.com/users/renovate%5Bbot%5D/starred{/owner}{/repo}",
        "subscriptions_url": "https://api.github.com/users/renovate%5Bbot%5D/subscriptions",
        "organizations_url": "https://api.github.com/users/renovate%5Bbot%5D/orgs",
        "repos_url": "https://api.github.com/users/renovate%5Bbot%5D/repos",
        "events_url": "https://api.github.com/users/renovate%5Bbot%5D/events{/privacy}",
        "received_events_url": "https://api.github.com/users/renovate%5Bbot%5D/received_events",
        "type": "Bot",
        "site_admin": false
      },
      "labels": [
        {
          "id":<PHONE_NUMBER>,
          "node_id": "MDU6TGFiZWwyNTc4NDAwMjE5",
          "url": "https://api.github.com/repos/cenk1cenk2/nestjs-tools/labels/renovate",
          "name": "renovate",
          "color": "ededed",
          "default": false,
          "description": null
        },
        {
          "id":<PHONE_NUMBER>,
          "node_id": "MDU6TGFiZWwyNTc4NDAwMjI3",
          "url": "https://api.github.com/repos/cenk1cenk2/nestjs-tools/labels/automerge",
          "name": "automerge",
          "color": "ededed",
          "default": false,
          "description": null
        },
        {
          "id":<PHONE_NUMBER>,
          "node_id": "MDU6TGFiZWwyNjExOTAxMDE2",
          "url": "https://api.github.com/repos/cenk1cenk2/nestjs-tools/labels/peer-deps",
          "name": "peer-deps",
          "color": "ededed",
          "default": false,
          "description": null
        }
      ],
      "state": "closed",
      "locked": false,
      "assignee": null,
      "assignees": [],
      "milestone": null,
      "comments": 1,
      "created_at": "2022-02-04T15:53:10Z",
      "updated_at": "2022-05-01T00:00:01Z",
      "closed_at": "2022-02-04T15:53:12Z",
      "author_association": "NONE",
      "active_lock_reason": null,
      "draft": false,
      "pull_request": {
        "url": "https://api.github.com/repos/cenk1cenk2/nestjs-tools/pulls/675",
        "html_url": "https://github.com/cenk1cenk2/nestjs-tools/pull/675",
        "diff_url": "https://github.com/cenk1cenk2/nestjs-tools/pull/675.diff",
        "patch_url": "https://github.com/cenk1cenk2/nestjs-tools/pull/675.patch",
        "merged_at": "2022-02-04T15:53:12Z"
      },
      "body": "[![WhiteSource Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)\n\nThis PR contains the following updates:\n\n| Package | Change | Age | Adoption | Passing | Confidence |\n|---|---|---|---|---|---|\n| @webundsoehne/nestjs-util | [`>= 2.3.2 < 5` -> `>= 2.3.2 <<EMAIL_ADDRESS>| [![age](https://badges.renovateapi.com/packages/npm/@webundsoehne%2fnestjs-util/5.0.1/age-slim)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://badges.renovateapi.com/packages/npm/@webundsoehne%2fnestjs-util/5.0.1/adoption-slim)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://badges.renovateapi.com/packages/npm/@webundsoehne%2fnestjs-util/5.0.1/compatibility-slim/4.3.2)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://badges.renovateapi.com/packages/npm/@webundsoehne%2fnestjs-util/5.0.1/confidence-slim/4.3.2)](https://docs.renovatebot.com/merge-confidence/) |\n\n---\n\n### Configuration\n\n📅 **Schedule**: At any time (no schedule defined).\n\n🚦 **Automerge**: Enabled.\n\n♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.\n\n🔕 **Ignore**: Close this PR and you won't be reminded about this update again.\n\n---\n\n - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, click this checkbox.\n\n---\n\nThis PR has been generated by [WhiteSource Renovate](https://renovate.whitesourcesoftware.com). View repository job log [here](https://app.renovatebot.com/dashboard#github/cenk1cenk2/nestjs-tools).",
      "reactions": {
        "url": "https://api.github.com/repos/cenk1cenk2/nestjs-tools/issues/675/reactions",
        "total_count": 0,
        "+1": 0,
        "-1": 0,
        "laugh": 0,
        "hooray": 0,
        "confused": 0,
        "heart": 0,
        "rocket": 0,
        "eyes": 0
      },
      "timeline_url": "https://api.github.com/repos/cenk1cenk2/nestjs-tools/issues/675/timeline",
      "performed_via_github_app": null
    },
    "comment": {
      "url": "https://api.github.com/repos/cenk1cenk2/nestjs-tools/issues/comments/1114074806",
      "html_url": "https://github.com/cenk1cenk2/nestjs-tools/pull/675#issuecomment-1114074806",
      "issue_url": "https://api.github.com/repos/cenk1cenk2/nestjs-tools/issues/675",
      "id":<PHONE_NUMBER>,
      "node_id": "IC_kwDOEx3Bf85CZ262",
      "user": {
        "login": "cenk1cenk2",
        "id": 26881592,
        "node_id": "MDQ6VXNlcjI2ODgxNTky",
        "avatar_url": "https://avatars.githubusercontent.com/u/26881592?v=4",
        "gravatar_id": "",
        "url": "https://api.github.com/users/cenk1cenk2",
        "html_url": "https://github.com/cenk1cenk2",
        "followers_url": "https://api.github.com/users/cenk1cenk2/followers",
        "following_url": "https://api.github.com/users/cenk1cenk2/following{/other_user}",
        "gists_url": "https://api.github.com/users/cenk1cenk2/gists{/gist_id}",
        "starred_url": "https://api.github.com/users/cenk1cenk2/starred{/owner}{/repo}",
        "subscriptions_url": "https://api.github.com/users/cenk1cenk2/subscriptions",
        "organizations_url": "https://api.github.com/users/cenk1cenk2/orgs",
        "repos_url": "https://api.github.com/users/cenk1cenk2/repos",
        "events_url": "https://api.github.com/users/cenk1cenk2/events{/privacy}",
        "received_events_url": "https://api.github.com/users/cenk1cenk2/received_events",
        "type": "User",
        "site_admin": false
      },
      "created_at": "2022-05-01T00:00:01Z",
      "updated_at": "2022-05-01T00:00:01Z",
      "author_association": "OWNER",
      "body": ":tada: This PR is included in version 4.0.0 :tada:\n\nThe release is available on [npm package (@latest dist-tag)](https://www.npmjs.com/package/@cenk1cenk2/nestjs-transactions/v/4.0.0)\n\nYour **[semantic-release](https://github.com/semantic-release/semantic-release)** bot :package::rocket:",
      "reactions": {
        "url": "https://api.github.com/repos/cenk1cenk2/nestjs-tools/issues/comments/1114074806/reactions",
        "total_count": 0,
        "+1": 0,
        "-1": 0,
        "laugh": 0,
        "hooray": 0,
        "confused": 0,
        "heart": 0,
        "rocket": 0,
        "eyes": 0
      },
      "performed_via_github_app": null
    }
  },
  "public": true,
  "created_at": "2022-05-01T00:00:02Z"
}

and more specifically its term payload.comment.created_at:2022-05-01T00:00:01Z, which is actually stored as a d (date == signed integer; you have to flip the 1st bit to decode it): [150, 234, 210, 20, 254, 193, 202, 0]
doc mapper is:
#
# Index config file for gh-archive dataset.
#
version: 0.4

index_id: gh-archive

doc_mapping:
  field_mappings:
    - name: id
      type: text
      fast: true
    - name: type
      type: text
      fast: true
      tokenizer: raw
    - name: public
      type: bool
      fast: true
    - name: payload
      type: json
      record: position
      tokenizer: default
    - name: body
      type: text
      record: position
      tokenizer: default
    - name: org
      type: json
      tokenizer: default
    - name: repo
      type: json
      tokenizer: default
    - name: actor
      type: json
      tokenizer: default
    - name: other
      type: json
      tokenizer: default
    - name: created_at
      type: datetime
      fast: true
      input_formats:
        - rfc3339
      precision: seconds
    - name: repo.id
      type: u64
      indexed: true
      stored: true
  timestamp_field: created_at

indexing_settings:
  commit_timeout_secs: 10
  merge_policy:
    type: "stable_log"
    min_level_num_docs: 100000
    merge_factor: 2
    max_merge_factor: 3
    maturation_period: 6h

build with quickwit 163ed7ef50051dd5cc1709675421a64102047cda and tantivy bff7c58497964f947dc94e2e45dfe9962e1d10c3
To reproduce: ingest enough of github archive to trigger a merge, the 1st document of type IssueCommentEvent will cause a panic (or possibly some other kind of document before)
this looks a lot like a variant of https://github.com/quickwit-oss/tantivy/issues/2251, which is supposed to be fixed by https://github.com/quickwit-oss/tantivy/pull/2253

Minimal Error Case:
    #[test]
    fn test_json_date_with_id_regression() {
        let mut schema_builder = Schema::builder();
        let json = schema_builder.add_json_field("json", TEXT);
        let schema = schema_builder.build();
        let index = Index::create_in_ram(schema);
        let mut writer = index.writer_for_tests().unwrap();
        let doc = json!({"date": "1-12-01T00:00:01Z", "id": 1});
        writer.add_document(doc!(json=>doc)).unwrap();
        writer.commit().unwrap();
        let doc = json!({"date": "1-12-01T00:00:01Z"});
        writer.add_document(doc!(json=>doc.clone())).unwrap();
        writer.add_document(doc!(json=>doc.clone())).unwrap();
        writer.commit().unwrap();

        // Force Merge
        writer.wait_merging_threads().unwrap();
        let mut index_writer: IndexWriter = index.writer_for_tests().unwrap();
        let segment_ids = index
            .searchable_segment_ids()
            .expect("Searchable segments failed.");
        index_writer.merge(&segment_ids).wait().unwrap();
        assert!(index_writer.wait_merging_threads().is_ok());
    }


Fix jar.setCookie

Hi,
While I was consolidating the TypeScript version of this module, I noticed an possible issue with the current use the jar.setCookie. jar.setCookie expects a callback(err, cookie) but currently we are not using this handler so it swallows errors. We should use jar.setCookieSync to keep the current behaviour.
Documentation
Occurences:

index.js#144
index.js#272
index.js#330-334
src/listen.js#66
utils.js#554-555
utils.js#571
utils.js#574

I am inspecting it further, looks like I made a mistake.


MS Docs vs MS Support conflicting content

There are some minor discrepancies between this document and the Virus scanning recommendations for Enterprise Computers support article.  Does one supersede the other and, if not, what's the difference?

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

ID: 7c9b6379-e575-9819-eca1-a0952f66b655
Version Independent ID: 34d81602-ffa2-5be6-67ef-b42b3b6f17ee
Content: Configure Microsoft Defender Antivirus exclusions on Windows Server 2016 or 2019 - Windows security
Content Source: windows/security/threat-protection/microsoft-defender-antivirus/configure-server-exclusions-microsoft-defender-antivirus.md
Product: w10
GitHub Login: @denisebmsft
Microsoft Alias: deniseb

@aydeisen : I think it is important to keep in mind that the support.microsoft.com page contains general advice for virus scanning regardless of AV Software solution, whereas the MS Docs page deals with Microsoft Defender for Endpoint specifically. In this regard, neither page supersedes the other, you just need to use the one that matches your AV Software solution.
Please also note that the support.microsoft.com page links to the MS Docs page specifically for Microsoft Defender, for Microsoft Defender-specific advice.
My advice is to use the page that matches your scenario.

Thank you @aydeisen for posting your feedback here. And thank you @illfated and @MaratMussabekov for your help. I am going to close this issue, but if you still have any questions, please let us know.

@denisebmsft @illfated @MaratMussabekov
Thank you for your responses.  Just one follow-up:  While I respect the note in the support article, according to a note in docs, the automatic exclusion rules only apply during an RTP scan and not during a scheduled scan.  So, if a scheduled scan is implemented, which list would be used for the explicit exclusions that are needed?

To me, it appears somewhat obvious (after reading the full document page) that any other exclusion lists are available to a scheduled scan. Only the Automatic exclusions are omitted during a Full/Quick or On-demand scan. See also the quoted paragraph below:
A few points to keep in mind

Custom exclusions take precedence over automatic exclusions.

Automatic exclusions only apply to Real-time protection (RTP) scanning. Automatic exclusions are not honored during a Full/Quick or On-demand scan.

Custom and duplicate exclusions do not conflict with automatic exclusions.

Microsoft Defender Antivirus uses the Deployment Image Servicing and Management (DISM) tools to determine which roles are installed on your computer.


Adds Kubernetes

Finally got around to creating this.
I want to embed the image at https://en.wikipedia.org/wiki/Kubernetes#Support, but I'm not sure if there's a way to hotlink it and keep it updated.

Preview link: https://deploy-preview-126--endoflife-date.netlify.app/kubernetes

All okay and ready for merge from my side.


Create a funding account for us to do the top-ups

Make an account, shared within EngAutomation, that we'll use for topping up the faucets.
Related: https://github.com/paritytech/devops/issues/2617

@mutantcornholio i failed to find related info on how should we top up accounts, if we need.
Could you please share?
I'd imagine some page for this in our wiki?


[1.21] World Corruption? Idk what to call it

I ran into a strange issue with the mod, after choosing an origin (Shulk in my case) and trying to reenter a world it won't load the world and get stuck on the loading screen or kick me to the server selection. At the same time the log in the curseforge app freaks out and gives me a server log. The world won't show up in the world selection screen until i restart the game and the screen background turns black. Disabeling the mod allows me to load into the world again without issues.
I do currently use the skip launcher function of curseforge because microsoft broke them for me.
The logs:
crash-2024-07-26_18.15.53-server.txt
crash-2024-07-26_18.18.16-server.txt
crash-2024-07-26_18.24.43-server.txt

Try removing Origins and see if the issue still persists. Looking at the crash report, it doesn't seem like Origins is the one causing the crash at all, but it could be an incompatibility 🤔

As written in my report the world loads up perfectly fine after disabeling Origins. Since the crash reports dont indicate which mods might be causing the issues i have no idea where to start with disabeling other mods to test for any incompatabilities

The first and second crash report seems to be caused by Villager Names and the third crash report seems to be caused by Biolith. It's strange that these issues only occur when Origins is installed, even though the crash report don't have anything else related to Origins at all 🤔

The issue seems to be fixed with the most recent update. I asume it was the same issue as #764


One small question about PDF to epub conversion

Hey sorry to bother you once again. I have one small question. I have a few PDF comics which (I was honestly surprised to find) have actual text layer that is selectable. I was just wondering what happens to those during conversion to epub? Do they just hide underneath the image with embedded text. Or do they just get removed completely. Thank You

PDF pages are rendered and saved as images during the conversion, so the output files don't have selectable text anymore.

Oh I understand. I had an interesting experience the other day that's why I'm asking. For class we use these smart whiteboards which basically are oversized (like 75+ inch) Android tablets. So I was like let's try running a normal ebook reader app in it like moon+ or play books. My mind was literally blown. I opened Moon and Ba's Daytrppier. And it looked soo good. But I noticed that text although looks good but not like crystal shap. But then I opened something else and it was great. Thats why I was trying to figure out what was going on. Anyways it might be a good feature to implement if you have time. But no pressure. As always thank you and keep up the good work.

Thanks for the feature suggestion, they are always appreciated but in these case, PDF reading and conversion is not likely to change. ACBR is focused on comic books and simplicity (of usage/features and, as much as possible, of development :)), converting them to images fits the goals of the project and the formats it outputs to, so I'm happy leaving it as it is.


Update lib.dom.d.ts, MutationObserverInit.attributeFilter can accept an iterator

I have a feeling this is in the wrong place, but figured I'd get started and then redirected. Iterators work fine in this location:
const obs = new MutationObserver(...)

const m = new Map()
// ... set some keys on the map ...

obs.observe(el, {
  attributeFilter: m.keys() // it works
})

Further explanation: https://github.com/whatwg/dom/issues/1092

Fixes #

This is still an issue. How do we fix it?


castShadows property not working

The castShadows property in a material doesn't affect the rendering of the entities. It always casts a shadow, with or without it
example:
https://playground.decentraland.org/?code=CmNvbnN0IG1lc2hFbnRpdHkgPSBlbmdpbmUuYWRkRW50aXR5KCkKVHJhbnNmb3JtLmNyZWF0ZShtZXNoRW50aXR5LCB7IAogIHBvc2l0aW9uOiBWZWN0b3IzLmNyZWF0ZSg0LCAzLjUsIDQpLApzY2FsZTogVmVjdG9yMy5jcmVhdGUoNCwgNCwgNCkgfSkKCgpNZXNoQ29sbGlkZXIuc2V0Qm94KG1lc2hFbnRpdHkpCk1lc2hSZW5kZXJlci5zZXRCb3gobWVzaEVudGl0eSkKCmNvbnN0IHRleHR1cmVTb3VyY2U6IEdlbmVzaXNQbGF6YUNvbnRlbnQgPSAnaW1hZ2VzL3BvcnRyYWl0cy9iZXR0eS5wbmcnCk1hdGVyaWFsLnNldFBick1hdGVyaWFsKG1lc2hFbnRpdHksIHsKICAgIHRleHR1cmU6IHsKICAgICAgIHRleDogewogICAgICAgICAkY2FzZTogInRleHR1cmUiLAogICAgICAgICB0ZXh0dXJlOiB7CiAgICAgICAgICAgIHNyYyA6IHRleHR1cmVTb3VyY2UsCiAgICAgICAgICAgIHdyYXBNb2RlOiAwCiAgICAgICAgIH0KICAgICAgIH0KICB9LAogIGNhc3RTaGFkb3dzOiBmYWxzZSwKICBhbGJlZG9Db2xvcjogIHtyOiAxLCBnOjAuNSwgYjogMC41fSwKfSApCgo%3D

Fixed part of the bug on the SDK7. Working on this issue, we found out that the SDK7 rendereable are not been culled and we opened an issue.


Inline version of \lim_{x \to c}

Problem
I like to have my {x \to c} right below \lim, but I don't like to use displayed formulas all the time.
Proposed Solution
Will it be possible for me to put {x \to c} right below \lim in inline mode?
Not (not limx -> c)

sry I just found I could do \underset

But it would be nice if $\lim_{x \to c}$ would give the same result as $\underset{x\to c}{\lim}$ in inline mode too. It'll be much easier to type, though I'm not sure if ppl would like to have have subscripts for limits.


adding config button

on https://bim360reports.herokuapp.com (STG) the Config button shows the modal but immediately redirects to autodesk.io...


Alert jumps to top of page (Chrome)

Hey,
When an alert pops up, the page jumps to the top.
I'm using Chrome 56.0.2924.87 (64-bit) and I'm using ES6.
Firefox and Safari have the same behavior.

Sorry, here is the fiddle:
https://jsfiddle.net/gtgLgrhe/1/
When I remove the html, body height and use a .box height of 100vh instead of 100%, then it doesn't jump up: https://jsfiddle.net/gtgLgrhe/2/

Thanks for reporting @ivanvermeyen! Fixed in v6.4.2

https://jsfiddle.net/gtgLgrhe/3/


New test data set for imputation

Here is described how I generated the test data set that I will need for the imputation pipeline as well as for testing the different modules.
Much of the procedure are from the GLIMPSE tutorial and the data are from the 1000GP.

Hi !
Thanks for the comment.
Everything is normally resolved now with the new commits.
Does the files need to be add to the modules branch for testing ?
Or should I use this branch to test the modules ?
Thanks
Louis

Hi ! Thanks for the comment. Everything is normally resolved now with the new commits.
Does the files need to be add to the modules branch for testing ? Or should I use this branch to test the modules ?
Thanks Louis

I think it's OK to use from this branch (I'm not :100: sure though - best to ask on #modules on slack) - if it's IS OK though, you will need to use the raw github links in oyur modules tests - i.e. you won't update the large netxflow map containing the 'standard' test data (I think)

Okay I going to do that !
Thanks again


Wrong content type when using OpenAPI 3

I sadly encountered fairly similar problem to https://github.com/springfox/springfox/issues/1539.
Using Springfox 3.0.0 with OpenAPI 3(DocumentationType.OAS_30)
Example:
@RequestMapping(path = "/apples/", consumes = "application/merge-patch+json", method = RequestMethod.PATCH)
public ResponseEntity<?> storeApples(@RequestBody @Nonnull List<Apple> apples) {
    // some code
}

contentType in generated docs should be only application/merge-patch+json. The thing is, there are two content types:

And unwanted content type(application/json) is default in dropdown.
If I change doc type to Swagger 2(DocumentationType.SWAGGER_2), contentType behaves as expected.

Solution proposed in https://github.com/springfox/springfox/issues/1539 not wok for me, when I use  OpenAPI 3(Swagger 2 works as mentioned).
Therefore I decided to create new issue(solution in original issue works for version used by reporter, this problem seems to be connected only to use of OpenAPI 3).

You can delete the unwanted content types from the specification by implementing WebMvcOpenApiTransformationFilter as a Spring bean (annotate the class @Component). Someting like this:
@Override
public OpenAPI transform(OpenApiTransformationContext<HttpServletRequest> context) {
    OpenAPI specification = context.getSpecification();
    forEachPathOperation(specification, this::restrictRequestsTypes);
    return specification;
}

private void forEachPathOperation(OpenAPI specification, Consumer<Operation> task) {
    specification.getPaths().values().forEach(path -> path.readOperations().forEach(task));
}

private void restrictRequestsTypes(Operation operation) {
    if (nonNull(operation.getRequestBody()) && nonNull(operation.getRequestBody().getContent())) {
        operation.getRequestBody().getContent().remove(APPLICATION_JSON_VALUE);
    }
}


Add cache control to more API endpoints [WIP]

Adding cache control to a few more API endpoints. I realize there's already some caching built into some of these endpoints but this will allow CloudFlare to cache it on the edge layer.

Cloudflare will not cache things unless the path ends in specific extensions - so this does not actually help us much as they are the only things providing cache for us.

I have looked into this fairly extensively and what you say is not how it works. You should try it and see.

I use Cloudflare on a different project I work for and it works exactly like that. We don't need extensions or page rules on the public API endpoints. Just cache control headers.
It is currently working for you as well. For example, on the /worlds endpoint you set the cache control header to 10 minutes and public.
cacheControl(CacheControl.maxAge(10, TimeUnit.MINUTES).cachePublic())
When I make a request to /worlds (not /worlds.js) I hit the cache and receive the expected max-age of 600 seconds.
https://gyazo.com/6b6a0f1a4f1a88644ac66d1245ddaeea

I have a page rule to cache /worlds. I just disabled it, and you can see now it is no longer caching it.

@Adam- I added a controller advisor now that will set the cache-control to no-cache on any response that does not already have a cache-control header set. With this, you can use a single page rule for api.runelite.net/* with CacheEverything and Origin Cache-Control on and it will respect any cache control headers you set


Add support for reading Auth data from a file on disk

This commit adds support from reading the authorization section of the
gnatsd config from a JSON file located within the nats-operator container.
This allows secrets the data to be placed on disk using sidecars like
consul-template.
Depends on https://github.com/nats-io/nats-operator/pull/171

Untested, and needs a test.  What do you recommend here @wallyqs ?

Implements https://github.com/nats-io/nats-operator/issues/156 ?

Okay, if this looks good, I'll try to write some tests.  Looks pretty gnarly though.

Also, should I put the sample NatsCluster file somewhere?

Thanks @schancel ! fwiw I think this approach might better than the other one of injecting all the credentials into the same config secret. The test could be a variation of this one maybe: https://github.com/nats-io/nats-operator/blob/master/test/e2e/config_reload_test.go#L100
It would be great to have an example here to include in the release notes too: https://github.com/nats-io/nats-operator/tree/master/example

@wallyqs Well, I finally got it compiling.  I still can't setup the e2e tests locally due to virtualization being disabled on the hardware I'm using.
Do you have any idea what's going on here?

Okay it's failing on:
	// Wait for the single pod to be created.
	ctx1, fn := context.WithTimeout(context.Background(), waitTimeout)
	defer fn()
	if err = f.WaitUntilFullMeshWithVersion(ctx1, natsCluster, size, version); err != nil {
		t.Fatal(err)
	}

Specifically for my test.  There must be something wrong with the manifest being provided to kubernetes.

@wallyqs Yeah, I noticed that.  I'm updating the reloader now to be a bit more generic

Once the multi-reloader branch is merged and this branch is rebased, and updating the reloader command, applying the following to the branch makes things work for me: https://github.com/wallyqs/nats-operator/commit/35ed43536f50ad3b19ab445468c38f5d7d34426f
There was an issue in the reloader test that when decoding JSON it would also accidentally escape >  because by default the Go encoder escapes HTML, only workaround seems to be is to setup manually the encoder to avoid escaping html...
@@ -211,11 +215,24 @@ func ConfigReloadTestHelper(t *testing.T, customizer NatsClusterCustomizerWSecre
 			},
 		},
 	}
-	// Serialize the object containing authentication data.
-	if d, err = json.Marshal(auth); err != nil {
+	// Serialize the object containing authentication data,
+	// we are using wildcard so need to unescape the HTML
+	// which the JSON encoder does by default...
+	buf := &bytes.Buffer{}
+	encoder := json.NewEncoder(buf)
+	encoder.SetEscapeHTML(false)
+	err = encoder.Encode(auth)
+	if err != nil {
+		t.Fatal(err)
+	}
+	buf2 := &bytes.Buffer{}
+	err = json.Indent(buf2, buf.Bytes(), "", "  ")
+	if err != nil {
 		t.Fatal(err)
 	}
+
 	// Create a secret containing authentication data.
+	d = buf2.Bytes()
 	if cas, err = f.CreateSecret(f.Namespace, "data", d); err != nil {
 		t.Fatal(err)
 	}

Merged via https://github.com/nats-io/nats-operator/commit/7ad614fb697fcaaa0b510f97de3f1d412ba3ac3c


Feature request: Put selection checkboxs to right side

Put selection checkboxs to right side will be a nice feature.

...or not have checkbox shown at all, so: rowSelectionBox : left [the default] / right / none


Error thrown when graphql-request 5.2.0 used with Nuxt 3

Screenshot

Description
Using graphql-request 5.2.0 to make arbitrary query requests in the setup function of Nuxt 3 will result in an error, but there is no error if the request is made in the onMounted function. This issue seems to only occur when the setup function is executed during server-side rendering, which may be related to the new feature "Features cb79d67 make package hybrid ESM/CJS closes #192 (#455)" in version 5.2.0, I guess.
Reproduction Steps/Repo Link

init a Nuxt 3 project by:npx nuxi@latest init my-app

add graphql-request by:pnpm add graphql-request

make any request in setupimport { request, gql } from 'graphql-request'

const query = gql`
query {
    message
}
`

// error thrown when any query is requested
// onMounted(async () => {
  const { message } = await request('http://localhost:5000/graphql', query)
  console.log(message)
// })

Repo Link: https://github.com/lity/graphql-request-with-nuxt-demo , please check app.vue.

I have the same problem. Is there any update to fix this on server-side? Thanks.

i  only have this issue in dev mode, production builds work fine

some more information:
there's some weird behaviour with typeof. the document passed to resolveRequestDocument logs to the console as a string, but is 'undefined' to typeof. in production builds, this document is an AST object (kind: 'Document') with the required .definitions.

possibly related: https://github.com/nuxt/nuxt/issues/14235

Define global constant replacements. Entries will be defined as globals during dev and statically replaced during build.

https://vitejs.dev/config/shared-options.html#define

@lity @DaDlugosch a solution suggested by nuxt maintainers works for me, please try this so we can close this issue. as far as i understand, this has nothing to do with graphql-request.
cc @jasonkuhrt

@apttx Thank you. This solution fixed my problem.

@lity @DaDlugosch a solution suggested by nuxt maintainers works for me, please try this so we can close this issue. as far as i understand, this has nothing to do with graphql-request.
cc @jasonkuhrt

Yes, it works, thank you.

graphql-request 5.2.0 and 6.0 works with Nuxt 3 by configing nuxt like this:
export default defineNuxtConfig({
  hooks: {
    'vite:extendConfig' (config, { isServer }) {
      if (isServer) {
        delete config.define!['typeof document']
      }
    }
  }
})

fyi, this solution might give up some optimisations & tree shaking


Support calculating normals for indexed meshes

Currently the PBR renderer requires every mesh to have a normals
attribute, and in case normals are missing there was a
compute_flat_normals() utility.
This utility was documented to panic in case a mesh was based on indices
and so to avoid that there is also a utility to expand a mesh into one
that doesn't depend on an index buffer.
To avoid needing to expand meshes to avoid index buffers, this updates
the utility to be able to calculate normals even for indexed geometry.
Note: this still has the other notable limitations that it assumes a
triangle list topology and will panic for triangle strips or meshes that
don't have vec3 float32 position attributes.
The api was renamed to compute_normals() since they can't be assumed to
be flat in the case that indexed vertices may be shared by multiple
faces. The calculated normals are (naively) averaged without any weighting,
such as by the angle or area of each adjacent face.
The gltf loader has been updated to no longer expand an indexed mesh
via duplicate_vertices before generating missing normals.
Ideally in the future there will be some kind of separation of how
assets like meshes are imported into bevy where there will be
a natural place to configure exactly how missing normals should be
calculated, including choosing what weighting to use for averaging.

thanks for the feedback @mcobzarenco - I've updated the patch with both suggestions.

The Doc comments to compute_flat_normals say:
Panics if [Indices] are set
Did this change?  In my code, it panics if Indices are NOT set.

Do you have a backtrace that shows where it panics for you?
If you're running with this patch then compute_flat_normals is now named compute_normals and it should work with or without indices (in the case without indices it should run the same code as before)
Other (pre-existing) limitations of this code to be aware of are that the position attribute must be float3 format and must have a triangle list topology.

Ah, I see, this Issue is Open, thus not merged in bevy 0.7.0!
I use compute_flat_normals. If I use it before set_indices, it crashes. So the doc of 0.7.0 is wrong, right?
I could make a backtrace. Shall I?
I don't know GitHub that well: If you like, I may test your "force-pushed"? How could I get/build your/that bevy version?

Right, it looks like my patch didn't make it into 0.7 unfortunately.
To test my branch you could potentially add something like this to your Cargo.toml to get bevy from my git branch instead of crates.io:
[patch.crates-io]
bevy = { git = 'https://github.com/rib/bevy.git', branch = 'wip/rib/calc-indexed-normals' }

I think the docs for 0.7 saying "Panics if [Indices] are set" are correct for compute_flat_normals. The first line of the function is this:
assert!(self.indices().is_none(), "`compute_flat_normals` can't work on indexed geometry. Consider calling `Mesh::duplicate_vertices`.");

To avoid that assertion code that needed to call compute_flat_normals would first call mesh.duplicate_vertices() to force any indices to be unpacked and give a larger mesh that doesn't depend on indices.
If you need to use compute_flat_normals directly yourself on 0.7 then yeah, unfortunately, you'll also need to call something like mesh.duplicate_vertices() to ensure your mesh doesn't use indices.
It sounds odd though that you're seeing some kind of panic in a case where you don't have indices... I haven't checked if the original code has changed since I wrote the patch and maybe it was re-written since I last looked at it (I see github is highlighting that the patch has conflicts now) - maybe another change on master (for 0.7) has introduced an issue you're hitting.

It looks like set_attribute was renamed to insert_attribute which is the source of the conflict here.
At first glance it doesn't look like there was any other functional change to calculate_flat_normals since I made this patch but it's worth noting that @cart did land a significant change (e369a8ad5138af28a7e760fac3f07b278c27ebb4) related to supporting various vertex buffer layouts which might be relevant here (though I haven't had a chance to investigate that change yet so can't really suggest anything specific to try)
Certainly a backtrace could help clarify what assertion failure / panic your hitting though, if you're able to get one

Can you rebase and fix the conflicts? The math looks right to me, I wanted to make a PR with something very similar and I saw yours.

Any updates on this one? Has this lost a maintainer? Would be pretty useful to me and I'm sure to others as well. 🤔

heya, sorry that looking at this hasn't been a priority for me recently. I've just done a rebase which I smoke tested with cargo run --examples load_gltf but I haven't actually re-tested the compute_normals code.
It would be good if someone (maybe @galkowskit and/or @IceSentry ?) could give the updated branch a try and check that it's working as intended.

I checked its behaviour in my project and it seems to be doing what it is supposed to do. :)
I think the only nitpick I might have is that it will panic and crash if it is called on a mesh without any indices or vertices added. It would be great if it crashed, but with some error message stating why. thread 'main' panicked at 'called Option::unwrap()on aNone value' is not that developer friendly.

So, one thing I don't like about this PR is that it gives flat normals on indexed meshes and smooth on non-indexed meshes.
I think we should keep the compute_flat_normals() as is, but also have a separate compute_smooth_normals(). Then also have a compute_normals() that just calls the appropriate one. This should all be documented appropriately too.

Also, can you update the PR description by using the default PR template? It makes it much easier to generate the release notes and migration guide when the template is used.

Just to let you know - I updated the PR since it was requested a few times but I have to admit this isn't a priority for me currently so I don't imagine I'm going to have time to make changes (since I'm also not in a good position to test changes currently), sorry.
There are certainly lots of things that could be improved about how Bevy handles various meshes missing data, but I'd also note that this PR was only really intended to make a single specific improvement to support (basic) generation of normals for indexed meshes (that are triangle lists). (I.e. don't panic and generate some reasonable normals)
I'm not so sure it's really necessary here to keep a compute_flat_normals and add a compute_smooth_normals - the renamed function specifically doesn't specify removed "flat" any more because it's now context dependent. The new function is compatible with the old compute_flat_normals in that it generates "flat" normals for non-indexed geometry and it generates basic (averaged) "smooth" normals for indexed geometry.
A more sophisticated solution would do a lot more - including allowing overwriting pre-existing normals, generating smooth normals for non-indexed meshes and supporting additional smoothing algorithms. This would presumably also be architected very differently; part of a pre-processing pipeline for assets, instead of something that's done on-the-fly at runtime like this since some of the algorithms for calculating normals may be relatively costly.
Please feel free to take this patch as a starting point and re-spin it as you like.

I checked its behaviour in my project and it seems to be doing what it is supposed to do. :) I think the only nitpick I might have is that it will panic and crash if it is called on a mesh without any indices or vertices added. It would be great if it crashed, but with some error message stating why.

Thanks for testing it out

thread 'main' panicked at 'called `Option::unwrap()` on a `None` value'

...is not that developer friendly. :D

As far as I recall the patch shouldn't introduce a panic for anything that didn't already panic - or are you maybe seeing that it introduces a new panic that didn't already exist?

To clarify a little what I meant. I understand that this PR is to make the current state a bit easier and not the final solution for all normal generation. I just think that there's no point in removing the current compute_flat_normals() because sometimes you just want to compute flat normals and hiding it behind a function that may or may not compute flat normals depending on the given mesh is a bit of a convoluted way to achieve the intended results. Especially given that the api already existed.
That's why I'm proposing to keep it and just call it from the new compute_normals() and at that point might as well have a compute_smooth_normals().
Anyway, since you can't easily update the PR, I'll tag it as Adopt-Me.

merged https://github.com/bevyengine/bevy/pull/11654 adds the feature, so please close this PR


Package unusable with k8s deployment+ingress+tls termination

Describe the bug
This package cannot be used when Zeebe Gateway is deployed on Kubernetes, exposed via an Ingress secured with TLS, with TLS terminating at the Ingress and not the pod.
When using a K8s Ingress with GRPC protocol, http2 can only be served over port 443 (see this issue or this issue), meaning that the Ingress has to use TLS. The generally accepted solution in this case is that you then terminate TLS at the Ingress and allow plain text communication between the pod and the ingress controller.
This pattern would result in a Zeebe Gateway URL that looks like https://zeebe-gateway-grpc.my.ingress.controller, but the fact we're terminating TLS at the edge means the client needs to be instantiated with .UsePlainText().
However, two pieces of behaviour stop this from working:

The ZeebePlainClientBuilder does not allow plain clients to be created when using a https protocol on the Zeebe URL.
The ZeebeClient always assumes that there are credentials when using https.

The workaround is to expose the Zeebe Gateway using an external Load Balancer so it gets an IP, however in cloud deployments (AWS, AKS, etc) ELBs are much more expensive than Ingress controllers and are generally more hassle.
To Reproduce
Steps to reproduce the behavior:

Deploy the camunda-platform helm chart on a K8s cluster with an ingress controller, in the values.yaml file you'll need to add:

zeebeGateway:
  ingress:
    grpc:
      enabled: true
      className: "YOUR NGINX CONTROLLER CLASS NAME HERE"
      host: "grpc-zeebe-gateway.your.domain.address"
      annotations:
        ingress.kubernetes.io/rewrite-target: "/"
        nginx.ingress.kubernetes.io/ssl-redirect: "false"
        nginx.ingress.kubernetes.io/backend-protocol: "GRPC"
      tls:
        enabled: true
        secretName: camunda-platform-zeebe-gateway-grpc

(this assumes that you have already created a tls secret with correct certs and keys called camunda-platform-zeebe-gateway-grpc)
2. Using the Client.Examples, change the ZeebeUrl to https://<whatever you just put as the ingress host> and leave .UsePlainText().
4. Watch it fail.
Expected behavior
I should be able to configure the client to use both a https URL and plaintext for cases where TLS is terminated at the edge.
Enviroment (please complete the following information):

Kubernetes version: v1.28.2+k3s1
ingress-nginx: 4.10.1
this client version: 2.6.0

Just by curiosity: why do you expose zeebe through the ingress? We also use it in a k8s cluster but we have not this problem because we don't expose zeebe which is restricted to an internal usage.


Support/fix release ref handling call from first workflow test

Test PR for https://github.com/LedgerHQ/ledger-live/pull/8718
Makes:

release-prepare and release-prepare-hotfix impotent (no side-effects)
release-prepare and release-prepare-hotfix call out to this branch's release-final
release-final echo out the inputs.ref value

These workflows can now be run on this branch.

✅ release-prepare successfully triggers release-final with the inputs.ref of main here.
✅ release-prepare-hotfix successfully triggers release-final with the inputs.ref of hotfix here. release-final is red on this job but that's just because there's no hotfix branch active at the moment, so I'm happy with this


Support for version task by default

Currently I have a built-in node CLI for Grommet.
I'm in the process of investigating a framework to handle the CLI for me. I've compared multiple frameworks and yours is the one I liked the most API-wise. Good job!
Our CLI today has a grommet --version. I was wondering if you have something similar that would output the version of the CLI. For now, this is what I did, but I believe this task is generic enough that could be added be default as we have help and exit.
#!/usr/bin/env node
import vorpal from 'vorpal';
import path from 'path';

const cli = vorpal();
const cliPath = path.join(__dirname, '..');
const packageJSON = require(path.join(cliPath, 'package.json'));

cli
  .command('version')
  .action((args, cb) => {
    cli.log(packageJSON.version);
    cb();
  });

cli
  .delimiter(cli.chalk.magenta('grommet~$'))
  .show();

I would be happy to create a PR if you think that this is useful.

FYI, I know we could use NPM itself to handle that, but as you can see here, it is kind of weird the way they do it:
http://stackoverflow.com/questions/10972176/find-the-version-of-an-installed-npm-package

Hey thanks!
That's a good idea. You should write and publish Vorpal extension that does that - I think people would find that very useful! You could call it vorpal-version. It would be implemented like this:
const vorpal = new Vorpal();
vorpal.use(require('vorpal-version')
  .show();

This would simply run the above code sample you wrote and inject a new version command into Vorpal.
Here are the docs on writing extensions, and here are some sample extensions.
Let me know if you need any help!

Thanks, i think i got it. i will write a PR for that early next week.


Run

Description of the new feature / enhancement
Before (IDK what version, sorry)
Run could let me navigate through folders and files like windows search would on other drives than C:\, such as D:\, by showing the content of the folder having it's path currently written in the text box.
Since the last update I made (v0.64.1)
It no longer behaves that way and only shows me an option to search on the internet. What's a shame is that even the windows search option of run doesn't have that expected behavior. Please bring that behavior back !
Scenario when this would be used?
Anytime I want to access a folder using my keyboard only without pressing tab like crazy or without the default windows search that's less ergonomic than Run feels to me.
Supporting information

Cc: @htcfreek

/bugreport

Hi, I fund an easy fix doing a scheduled task on this event:

and this action:

Action's details:
Program/script:  cmd.exe
Arguments: /k (taskkill /im PowerToys.PowerLauncher.exe & start /separate PowerToys.PowerLauncher.exe | start /separate PowerToys.PowerLauncher.exe) & exit
Starts in: C:\Program Files\PowerToys\modules\launcher\
Hope this helps!


[Safari] Safari 10.1 no longer load systems exported in HTML format

Safari 10.1 seems to send now an error when accessing to the localstorage object when running a local file (i.e. file://).
So from this version, Safari no longer load systems exported in HTML format.
note: a workaround is to activate local file access from the developer tool  menu.

The update to System Runtime v1.9.8 fixed the issue.


Add support to format log streaming of structured JSON output

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

[x] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
For the newly added code only.

For new extensions:

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

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

spring cloud


Handle error state for the notification

Description
There was an issue that error state notification appeared as normal and can't be cleared out from the notification panel.
This fixes the issue.

E.g ^ notification errored out but looks fine and wasn't being cleared out when clear notification was clicked.
Resolves #(issue)

What is the difference between error and failed? Is there a reason to keep both around?

Both are from simulation progressState, and it looks like they both are used for failure status.


Usage of allow_blob_public_access no longer supported

Summary
When running "terraform apply", the following error occurs:

Error: Unsupported argument
on .terraform/modules/shared_infra/storage.tf line 21, in resource "azurerm_storage_account" "components":
21:   allow_blob_public_access = true
An argument named "allow_blob_public_access" is not expected here.

Details
From azurerm 3.0 and above, allow_blob_public_access is no longer supported
https://github.com/hashicorp/terraform-provider-azurerm/issues/16128
The fix should simply be to rename it to "allow_nested_items_to_be_public"

Here is also a patch
0002-Rename-allow_blob_public_access-to-allow_nested_item.patch.zip
:


Random Daily Drive no longer working console error 400

Authenticate button works, Generate Playlist doesn't.
In Chrome console I get the error:
   DELETE https://api.spotify.com/v1/playlists/6DVxy9FZF0qS7RpTlsIOQm/tracks 400 (Bad Request)

Since I learned that the app is in fact used by several people on a daily basis, I decided to finally touch the code again, see #22
My time is limited and I'm soon away in summer vacation, but I have it on my radar now.

Found the issue. This happens, if the app tries to remove all tracks from the existing playlist, but it is already empty.
The error is probably a result from a previous failure, where it emptied the playlist but failed to add the tracks.
The issues is now properly handled.
Also released a bunch of improvements.


Question about the WC2014 camera pan,tilt,zoom parameters

So the paper mentions that the images from WC2014 were pre-processed to get the range of these parameters in them:
pan, tilt and focal length ranges
([−35◦,35◦], [−15◦, −5◦] and [1000, 6000] pixels.
Does anyone know more info on how those were got/obtained ?
Also, in synthetic.utils.py, there is the following line:
camera_data = np.asarray([640,	360, 3081.976880,
1.746393,	 -0.321347,	 0.266827,
52.816224,	 -54.753716, 19.960425])
which I think it's exactly those hard-coded parameters out of nowhere. It would be really helpful to know more info/the approach used to get these for the images in the dataset.
Thanks!
cc @lood339

These parameters are estimated from the training dataset. They are used as the prior (known knowledge).

Hi @lood339 Can you please add a license to the PTZ repository?. Thanks.

These parameters are estimated from the training dataset. They are used as the prior (known knowledge).

Hi, could you tell me how to calculate these parameters  from dataset ? or share some advice to me. I’m glad to see your reply.


Fix #570 missing package not resolved

Changes

To support babel macros.
In dev mode, before reinstalling dependencies, do add the missing entry points to knownEntrypoints as reinstall will only install the dependencies from configuration, and imports scanned from the source code.

Testing

Tested here: https://github.com/JennieJi/snowpack/pull/3
I only reproduced this via babel macros, but installing babel plugin will add too many files. And I didn't have a good idea of how to use the current test runners to test the dev mode... Thus I chose not to add in this branch. @FredKSchott need some advice about this.

Another thinking here is whether it's possible to run the reinstallDependencies() after transformFileImports() instead of running in each callback functions

This is a good start, but adding it to the knownEntrypoints config property won't save this back to your config, which means that next time you run any Snowpack command this new dependency name will be gone again. I think instead, we need to warn the user with a nice message so that they can add it to their own knownEntrypoints config and have it persist across runs.

This is a good start, but adding it to the knownEntrypoints config property won't save this back to your config, which means that next time you run any Snowpack command this new dependency name will be gone again. I think instead, we need to warn the user with a nice message so that they can add it to their own knownEntrypoints config and have it persist across runs.

Can, will add a warning in terminal

Hmmm the logs will be cleared somehow, may be related to #558 ?

PS: apologies for the noise, but we just converted this project to a monorepo. We tried to preserve history in the repo, so you should be able to rebase/merge to get the latest changes.

Thanks, I will try later.

Thanks, I will try later.

Hi @FredKSchott ,
I've removed the mutation on config object.
Then I find the reason why missingWebModule was always null because of the reinstalling will pass INSTALL_COMPLETE to message bus and there it will reset the missingWebModule. And it works fine after removal of reinstalling:

And for doesImportExist with rescanning the imports, I don't really get why do we need a rescanning to confirm whether the import exists? In my understanding, this part is under the callback function of transformFileImports(), so it has confirmed the import exists I suppose?

Update: We ended up running into separate issues with this "auto install missing packages" workflow and the new dev output tracked in #648, which forced us to just remove it entirely for now.
I went ahead and added this message about config.install to the new warning that we output (a9d2f4b7fa0f9982750543171231fa07dc47cbb6) which should solve your use-case and is hopefully less complex for everyone.
Thanks again for your work here! if you are able to test against master and see anything still not working, please let me know and I'll take a look. Looking forward to getting this merged and fixing the macros issue!

Noted thanks


Update dependencies

Fixes: #22
Updates all dependencies with known vulnerabilities. npm audit now passes.
Updates CLI to use new inquirer syntax.
Since mocha now requires at least node 6, CI has been updated to use newer versions

This is a useful library with great documentation. Any chance this PR could get merged @nathanbuchar? Thanks!


Testing, please ignore. (wcozpo)

This is a bug bounty test - please ignore.. Please DO NOT APPROVE THIS! (wcozpo)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.wcozpo baxxu seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Refresh getting started images, add package content details

This change updates the getting started article to include images matching 2.2.0 ux as well as tables describing the package contents (with links to relevant overview articles as available).
Fixes #6453

/azp run mrtk_docs

/azp run mrtk_docs


Network connectivity during final report causing test process to exit with non-zero status

Just recently got the free trial set up and using Test Analytics so we can see what our expected usage and value will be for the service. Something we've noticed is that when there are connectivity issues with Buildkite's servers (whether they be connections being disconnected, or DNS resolution breaking) they do not cause tests to fail, but the final report at the end of the test run will fail and cause the process to exit with a non-zero exit status.
This is causing pain in our CI system that's currently running with Test Analytics enabled.
I was able to recreate this when running a test locally by shutting off my WiFi half way through the tests. Minitest will report no test failures (because there aren't any) but exit status will be (1) due to an Errno::ETIMEDOUT error being raised out of socket_connection.
$> CI=true BUILDKITE_ANALYTICS_TOKEN=<redacted> bundle exec rake automated_test:run TEST_FILES="path/to/test/file_test.rb"
** Invoke automated_test:run (first_time)
** Execute automated_test:run
Run options: --seed 29935

# Running:

....

Finished in 60.421516s, 0.0662 runs/s, 0.1324 assertions/s.

4 runs, 8 assertions, 0 failures, 0 errors, 0 skips
#<Thread:0x00007fc585702c70 /Users/jebentier/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/buildkite-test_collector-1.2.5/lib/buildkite/test_collector/socket_connection.rb:64 run> terminated with exception (report_on_exception is true):
Traceback (most recent call last):
        2: from /Users/jebentier/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/buildkite-test_collector-1.2.5/lib/buildkite/test_collector/socket_connection.rb:69:in `block in initialize'
        1: from /Users/jebentier/.rbenv/versions/2.7.5/lib/ruby/2.7.0/openssl/buffering.rb:125:in `readpartial'
/Users/jebentier/.rbenv/versions/2.7.5/lib/ruby/2.7.0/openssl/buffering.rb:125:in `sysread': Operation timed out (Errno::ETIMEDOUT)
Traceback (most recent call last):
        2: from /Users/jebentier/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/buildkite-test_collector-1.2.5/lib/buildkite/test_collector/socket_connection.rb:69:in `block in initialize'
        1: from /Users/jebentier/.rbenv/versions/2.7.5/lib/ruby/2.7.0/openssl/buffering.rb:125:in `readpartial'
/Users/jebentier/.rbenv/versions/2.7.5/lib/ruby/2.7.0/openssl/buffering.rb:125:in `sysread': Operation timed out (Errno::ETIMEDOUT)
rake aborted!
Command failed with status (1): [ruby -I"lib:test" -I"/Users/jebentier/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/rake-12.3.3/lib" "/Users/jebentier/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/rake-12.3.3/lib/rake/rake_test_loader.rb" "test/lib/deploy/health_checks/call_event_worker_test.rb" ]
/Users/jebentier/.rbenv/versions/2.7.5/bin/bundle:23:in `load'
/Users/jebentier/.rbenv/versions/2.7.5/bin/bundle:23:in `<main>'
Tasks: TOP => automated_test:run
(See full trace by running task with --trace)

I noticed that in https://github.com/buildkite/test-collector-ruby/pull/145 a fix was put in to make sure errors raised while failing to connect to Buildkite's server doesn't cause tests to fail. Would it be possible to get a similar protection around the final report at the end of the test run, so that network connectivity issues don't negatively affect test runs?

Thanks for reporting this @jebentier. We're very keen to ensure the ruby collector fails gracefully and doesn't break builds!
I think we have some disconnection exceptions being caught for socket_connection but it would seem this one's been missed. I've scheduled a fix with the Test Analytics team. We'll let you know when the fix is ready 😊

@jebentier the fix is now in main. If you like, you can test it out by installing the gem from git. If not, we'll be releasing a new version of the gem in the next couple of days.

Sorry for the delay on this. I was able to test this out and this issue is resolved. Thank you and your team for the quick turnaround on this. Appreciate it.


Implement CMS for alerts

We should follow through and ship this https://github.com/hirosystems/explorer/pull/1149

:tada: This issue has been resolved in version 1.186.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Personally for WopsS | PawnPlus-Winform

Hello! I know, so much time has passed ... but I personally did not find the answer to this question. There will be a big request for you to help with the error in PawnPlus-Winforms when compiling any SAMP game mod.
Details:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at PawnPlus.Main.compilerWorker_RunWorkerCompleted(Object sender, RunWorkerCompletedEventArgs e)
at System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted(RunWorkerCompletedEventArgs e)
************** Loaded Assemblies **************
mscorlib
Assembly Version: <IP_ADDRESS>
Win32 Version: 4.8.4360.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
PawnPlus
Assembly Version: <IP_ADDRESS>
Win32 Version: <IP_ADDRESS>
CodeBase: file:///D:/PawnPlus/PawnPlus.exe
System.Windows.Forms
Assembly Version: <IP_ADDRESS>
Win32 Version: 4.8.4341.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_<IP_ADDRESS>__b77a5c561934e089/System.Windows.Forms.dll
System
Assembly Version: <IP_ADDRESS>
Win32 Version: 4.8.4360.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_<IP_ADDRESS>__b77a5c561934e089/System.dll
System.Drawing
Assembly Version: <IP_ADDRESS>
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_<IP_ADDRESS>__b03f5f7f11d50a3a/System.Drawing.dll
PawnPlus.Language
Assembly Version: <IP_ADDRESS>
Win32 Version: <IP_ADDRESS>
CodeBase: file:///D:/PawnPlus/PawnPlus.Language.DLL
System.Configuration
Assembly Version: <IP_ADDRESS>
Win32 Version: 4.8.4190.0 built by: NET48REL1LAST_B
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_<IP_ADDRESS>__b03f5f7f11d50a3a/System.Configuration.dll
System.Core
Assembly Version: <IP_ADDRESS>
Win32 Version: 4.8.4360.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_<IP_ADDRESS>__b77a5c561934e089/System.Core.dll
System.Xml
Assembly Version: <IP_ADDRESS>
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_<IP_ADDRESS>__b77a5c561934e089/System.Xml.dll
PawnPlus.Core
Assembly Version: <IP_ADDRESS>
Win32 Version: <IP_ADDRESS>
CodeBase: file:///D:/PawnPlus/PawnPlus.Core.DLL
SharpCompress
Assembly Version: <IP_ADDRESS>
Win32 Version: <IP_ADDRESS>
CodeBase: file:///D:/PawnPlus/SharpCompress.DLL
Newtonsoft.Json
Assembly Version: <IP_ADDRESS>
Win32 Version: <IP_ADDRESS>22
CodeBase: file:///D:/PawnPlus/Newtonsoft.Json.DLL
System.resources
Assembly Version: <IP_ADDRESS>
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.resources/v4.0_<IP_ADDRESS>_ru_b77a5c561934e089/System.resources.dll
mscorlib.resources
Assembly Version: <IP_ADDRESS>
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_<IP_ADDRESS>_ru_b77a5c561934e089/mscorlib.resources.dll
WeifenLuo.WinFormsUI.Docking
Assembly Version: <IP_ADDRESS>
Win32 Version: <IP_ADDRESS>
CodeBase: file:///D:/PawnPlus/WeifenLuo.WinFormsUI.Docking.DLL
PawnPlus.CodeEditor
Assembly Version: <IP_ADDRESS>
Win32 Version: <IP_ADDRESS>
CodeBase: file:///D:/PawnPlus/PawnPlus.CodeEditor.DLL
ThemeVS2012Light
Assembly Version: <IP_ADDRESS>
Win32 Version: <IP_ADDRESS>
CodeBase: file:///D:/PawnPlus/ThemeVS2012Light.DLL
WindowsFormsIntegration
Assembly Version: <IP_ADDRESS>
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/WindowsFormsIntegration/v4.0_<IP_ADDRESS>__31bf3856ad364e35/WindowsFormsIntegration.dll
ICSharpCode.AvalonEdit
Assembly Version: <IP_ADDRESS>
Win32 Version: <IP_ADDRESS>
CodeBase: file:///D:/PawnPlus/ICSharpCode.AvalonEdit.DLL
PresentationFramework
Assembly Version: <IP_ADDRESS>
Win32 Version: 4.8.4360.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/PresentationFramework/v4.0_<IP_ADDRESS>__31bf3856ad364e35/PresentationFramework.dll
WindowsBase
Assembly Version: <IP_ADDRESS>
Win32 Version: 4.8.4360.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/WindowsBase/v4.0_<IP_ADDRESS>__31bf3856ad364e35/WindowsBase.dll
PresentationCore
Assembly Version: <IP_ADDRESS>
Win32 Version: 4.8.4360.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_64/PresentationCore/v4.0_<IP_ADDRESS>__31bf3856ad364e35/PresentationCore.dll
System.Xaml
Assembly Version: <IP_ADDRESS>
Win32 Version: 4.8.4360.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xaml/v4.0_<IP_ADDRESS>__b77a5c561934e089/System.Xaml.dll
PresentationFramework.Aero2
Assembly Version: <IP_ADDRESS>
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/PresentationFramework.Aero2/v4.0_<IP_ADDRESS>__31bf3856ad364e35/PresentationFramework.Aero2.dll
UIAutomationTypes
Assembly Version: <IP_ADDRESS>
Win32 Version: 4.8.4360.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/UIAutomationTypes/v4.0_<IP_ADDRESS>__31bf3856ad364e35/UIAutomationTypes.dll
UIAutomationProvider
Assembly Version: <IP_ADDRESS>
Win32 Version: 4.8.4360.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/UIAutomationProvider/v4.0_<IP_ADDRESS>__31bf3856ad364e35/UIAutomationProvider.dll
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Hello, I remember there were some temporary files written in the application directory, could you try to run it as administrator and see if it works?

I started the program as administrator, but everything works the same way. Here is a screenshot of the program folder, if needed.

Can you try to create a directory named Pawn where the application is installed and extract the Pawn compiler in it?

Again, exactly the same(

Then try to put it in %appdata%/PawnPlus/Pawn.

It helped, thank you very much!

No problem :)