Document the bevy_render::camera module tree

Objective
Document most of the public items of the bevy_render::camera module and its
sub-modules.
Solution
Add docs to most public items. Follow-up from #3447.

Ping @alice-i-cecile what's the status here? Seems you have approved, is there anything else for me to do? Thanks!

We need a second reviewer. Ping @bevyengine/docs-team.

@alice-i-cecile this PR changed since last review, as several files were deleted in Bevy 0.8. It's now much smaller, and mostly the same, but maybe need a new review. Should I reset your vote?

Yep, I'll re-review now.

bors r+


ci: don't explicitly trigger prepare script

What kind of change does this PR introduce?
CI optimization
What is the current behaviour?
npm run pepare executed twice in CI pipeline.
CI fires consecutively npm run ci and npm run pepare. But npm run ci calls automatically npm run pepare after dependencies are installed
What is the new behaviour?
Call just npm run ci.
Does this PR introduce a breaking change?
No
Other information:
Please check if the PR fulfills these requirements:

[ ] Tests for the changes have been added
[ ] Docs have been added / updated

Coverage remained the same at 100.0% when pulling 0bf42d7a32530ea77f3c473bb34b15873ce15e25 on ci-optimization into 75f3ca006eda7d9b15efa9716828fb5007bc2c62 on master.


Choose new license

As the Apache License may not be the perfect choice for data, we should probably choose a new (better) license.
What about the Creative Commons Attribution 4.0 International license?

https://wiki.creativecommons.org/wiki/Data
http://www.dcc.ac.uk/resources/how-guides/license-research-data

License changed to CC BY 4.0 in https://github.com/delight-im/FreeGeoDB/commit/b627bfb521cb6e0bdee75722623c6a275a54a6bf


Creates New QGRNN Tutorial

Title:
Creates a new and improved version of the QGRNN tutorial in https://github.com/XanaduAI/qml/pull/98
This tutorial is still a work-in-progress, hence the draft PR.
Summary:
Relevant references:
Possible Drawbacks:
Related GitHub Issues:
https://github.com/XanaduAI/qml/pull/98

@ixfoduap The first part of this tutorial deals with generating data to be used in the neural network. I know that part of your feedback for the VQT was that the tutorial should actually dive into implementing the VQT faster, and this tutorial kind of has the same problem. I've done a lot of thinking, and I can't really think of any good way to expedite the process of generating the data. If you have any suggestions, let me know! 🙂

Updated HTML version of the tutorial: https://1077-214003948-gh.circle-artifacts.com/0/_build/html/demos/tutorial_qgrnn.html
Note that the only reason that the number of executions is set to one is to ensure that the website builds in a reasonable amount of time when being reviewed (so please disregard the terrible training results!) 🙂


Element.transform() breaks if given a parameter in scientific notation

Suppose we have an element o. If we call o.transform("s0.5 t2e-11"), this is processed with a translation of (2, -11) instead of the expected (2e-11, 0).
More details on this can be found here.
If scientific notation isn't supported in these strings, then I don't consider this a bug - but I do think it's worth stating somewhere.

Hi @Stickerpants
This is a duplicate of #378
The fix has just been merged, next release will be fixed.

This can be closed


[4/6] Venft token ranges & carousel

What does this PR do and why?
Adds the functionality to fetch veNFT variant data and token metadata. Builds out functionality for the Staking Token Ranges Modal and Carousel. Displays the image of the NFT you will receive on the confirm stake modal.
Note that right now our variants are hardcoded to the IPFS hash of a one-time deploy Tank did, and that in the future it will be an action item to add deployment of variant metadata to the contract deployer.
Also note that loading these images does not currently work with the Juicebox dedicated pinata gateway, and you will need to use the public gateway.pinata.cloud instead.
Screenshots or screen recordings

Acceptance checklist

[ ] I have evaluated the Approval Guidelines for this PR.
[ ] I have tested this PR in all supported browsers.
[ ] I have tested this PR in dark mode and light mode (if applicable).

@jmilldotdev another one!
Left a few super minor questions. The biggest one I have is https://github.com/jbx-protocol/juice-interface/pull/1503#discussion_r928455106
I've started creating follow-up issues for UX here: https://github.com/jbx-protocol/juice-interface/issues/1154

All comments addressed.


Add support for Foundry 0.8.x

In GitLab by @Asacolips on May 22, 2021, 22:26
With Foundry's 0.8.x series entering beta as of the 0.8.4 release, the system needs to have support for 0.8.x added. This will not be dual-compatible with both 0.7.9 and 0.8.x, so future versions of the system will be for 0.8.x
Acceptance Criteria

[x] Dungeon World works on Foundry 0.8.4+

In GitLab by @Asacolips on May 30, 2021, 14:34
marked the checklist item Dungeon World works on Foundry 0.8.4+ as completed


psarips changed url again (psa.pm)

Domain
https://psa.pm/
Link
https://psa.pm/
Version
0.0.0
What browsers are you seeing the problem on?
Brave
What OS are you seeing the problem on?
No response
Anything else?
hrefBypass(/((psarips\.(com|net|org|eu|in|one|xyz|uk))|(psa\.one))\/exit\//,()=>ifElement("form[name='redirect']",f=>{
should be:
hrefBypass(/((psarips\.(com|net|org|eu|in|one|xyz|uk))|(psa\.(one|pm)))\/exit\//,()=>ifElement("form[name='redirect']",f=>{
Code of Conduct

[X] I agree to follow this project's Code of Conduct

If you're still following this, I implemented this change in this PR:
https://github.com/FastForwardTeam/FastForward/pull/619
But FastForward still fails to bypass psa.pm exit links after the commit (3b9c441). Can you check whether there are further changes that we need to do to successfully bypass psa.pm?


Develop a tutorial using a polygon dataset #1

Create a new page (.md) in the repository that provides a step-by-step tutorial on how to use the library with a polygon dataset.
The following needs to be done:

Find a South Africa point dataset to be used
Create a step-by-step tutorial on how to generate report for the dataset using autoESDA
Document any issues you encountered

There are a few possible variations of this task, and you can only do one.

Hi @vrautenbach, I would like to be assigned to this issue, however I am having problems with installing autoesda package.
This is the error I get when installing it using pip in my command prompt:
Microsoft Windows [Version 10.0.22000.1098]
(c) Microsoft Corporation. All rights reserved.
C:\Users\Nombasa More>pip install autoesda
Collecting autoesda
Using cached autoesda-0.0.6-py2.py3-none-any.whl (9.1 kB)
Collecting splot>=1.1.4
Using cached splot-1.1.5.post1-py3-none-any.whl (39 kB)
Collecting pysal==2.3.0
Using cached pysal-2.3.0.tar.gz (108 kB)
Preparing metadata (setup.py) ... done
Collecting seaborn==0.11.2
Using cached seaborn-0.11.2-py3-none-any.whl (292 kB)
Collecting geopandas==0.8.1
Using cached geopandas-0.8.1-py2.py3-none-any.whl (962 kB)
Collecting esda
Using cached esda-2.4.3.tar.gz (116 kB)
Preparing metadata (setup.py) ... done
Collecting matplotlib==3.4.2
Using cached matplotlib-3.4.2.tar.gz (37.3 MB)
Preparing metadata (setup.py) ... done
Collecting libpysal==4.4.0
Using cached libpysal-4.4.0-py3-none-any.whl (2.4 MB)
Collecting pandas>=0.23.0
Using cached pandas-1.5.0-cp310-cp310-win_amd64.whl (10.4 MB)
Collecting pyproj>=2.2.0
Using cached pyproj-3.4.0-cp310-cp310-win_amd64.whl (4.8 MB)
Collecting shapely
Using cached Shapely-1.8.5.post1-cp310-cp310-win_amd64.whl (1.3 MB)
Collecting fiona
Using cached Fiona-1.8.21.tar.gz (1.0 MB)
Preparing metadata (setup.py) ... error
error: subprocess-exited-with-error
× python setup.py egg_info did not run successfully.
│ exit code: 1
╰─> [1 lines of output]
A GDAL API version must be specified. Provide a path to gdal-config using a GDAL_CONFIG environment variable or use a GDAL_VERSION environment variable.
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
I then tried installing the package with conda and conda-forge. I have Anaconda on my PC and got this error when using the anaconda prompt:
(base) C:\Users\Nombasa More>conda install autoesda
Collecting package metadata (current_repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Collecting package metadata (repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
PackagesNotFoundError: The following packages are not available from current channels:

autoesda

Current channels:

https://repo.anaconda.com/pkgs/main/win-64
https://repo.anaconda.com/pkgs/main/noarch
https://repo.anaconda.com/pkgs/r/win-64
https://repo.anaconda.com/pkgs/r/noarch
https://repo.anaconda.com/pkgs/msys2/win-64
https://repo.anaconda.com/pkgs/msys2/noarch

To search for alternate channels that may provide the conda package you're
looking for, navigate to
https://anaconda.org

and use the search bar at the top of the page.


Replace sqlite libary to https://github.com/logoove/sqlite

Hi !
Do you have plan to use https://github.com/logoove/sqlite? This libary without cgo, make things better.

直接把官方的替换了就行


CACTUS GUST SIMULATION

Hi everyone,
I was wondering how do one correctly model the gust simulation correctly in CACTUS? I have played around with the igust, gustamp, gusttime, gustX0 parameters but I get no difference in the result. Would be grateful for some tips and suggestions!
Best Wishes,
Sadman Sakib
The University of Texas at Dallas

I have also been having issues with the gust simulation. By monitoring the fieldData output, I am able to observe that setting igust = 1 overrides the free stream to be uniform, even when slex  is non zero. I have tried a variety of physically relvant values of gustamp, gusttime, and gustX0 , but am not able to observe the gust in the free stream or induced velocity fields.

There appears to be a bug in the implementation of the gust velocity. See the snippet below.
https://github.com/SNL-WaterPower/CACTUS/blob/4e7db1112ffa34f7e62d154e12eaa83e342d63c3/src/CalcFreestream.f95#L20-L40
Here, the gust velocity is clearly being overwritten by the shear profile when really they should be added together.
As with many other things in CACTUS, the gust module is quite immature. It only supports the "EOG" gust. If you intend on modeling other DLCs, you'd likely want to develop a more modular way to specify the inflow, i.e., U(x,y,z,t)

Actually, that's not quite right, I didn't see the return. Let me look into this a bit more.

It looks like shear is ignored when igust = 1.
After some experimentation, I was able to see gust effects in the exported field data. Can you share the gust parameters you are using?

Glad to hear it is working for you! My gust parameters were  gustamp = 2, gusttime = 0.5, gustX0 = -5. The gust starting location, gustX0, was chosen to be upstream of the rotor and my gusttime  corresponded to half a rotation of the turbine. The nominal free stream velocity was 8 m/s so I would have expected a 2 m/s gust to be noticeable.
For my field data, I was recording 20 points vertically spaced at the X-Z position 2 diameters upstream of the rotor.

I've attached a modified TestCase1/TestHAWT.in which applies a gust and also samples field data every timestep at the (0, 0, 0) using the Probe feature.
Here is a plot of Ufs/Uinf from the probe data.

TestCaseGust.zip
Unzip this into [CACTUS source]/test/ to run.

Thanks for sharing this example. I was able to replicate it on my machine. Additionally, I was able to change the gust parameters and have the gust profile change as expected.

Great! The confusing part for me was the gusttime parameter, which needed to be much longer than what I had originally set when I was just messing around. Closing this issue.


Fix color_never test

Which component is your feature related to?
Forge
Feature Request
Output from compiling snforge_scarb_plugin is colored, but this is only the case in CI.

Duplicate #2356


update basic Colab example

end of file issue, favoring https://github.com/sparks-baird/matbench-genmetrics/commit/ecedcd63cd55d6f66c2a5d3c1e803457315f3a06


ScriptFinder logic temporary update to use correct integtest.sh

ScriptFinder logic temporary update to use correct integtest.sh  until #497 is fixed in plugin repos
Signed-off-by: Himanshu Setia<EMAIL_ADDRESS>Issues Resolved
#469
Check List

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #499 (974e29a) into main (9032bdc) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #499   +/-   ##
=======================================
  Coverage   69.31%   69.31%
=======================================
  Files          58       58
  Lines        1509     1509
=======================================
  Hits         1046     1046
  Misses        463      463

Impacted Files
Coverage Δ

bundle-workflow/src/paths/script_finder.py
100.00% <ø> (ø)

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 9032bdc...974e29a. Read the comment docs.


TAJO-1711: Add basic monitoring page

Add basic monitoring page

@hyunsik
nv.d3.js license seems to apache 2.0. Should we add d3 license to LICENSE file ?
https://github.com/novus/nvd3/blob/master/LICENSE.md

@jinossy We don't need to add d3 license to LICENSE file if it is under ASF 2.0.

For clear, it would be better if you add this license (https://github.com/novus/nvd3/blob/master/LICENSE.md) into LICENSE file.

Hi @yeongeon,
This work looks great to me. But, it includes per-node monitoring feature. But, it is not fit in Tajo web page because Tajo basically aims at a number of nodes.
If you want to put a single page monitoring to Tajo, it would be great if the page is a summary page to give an overview of cluster, query, and scheduling information.
So, this work needs more work to remove worker parts and add some more information for an overview of them. For this, it would be great if you continue this work in a separate branch because 0.11.0 release is approaching.
I'll look forward to your comments. Thanks.


ddev_bash_completions.sh missing from release tarball

The Getting Started CLI docs (cli-usage.md, very last section) say that ddev_bash_completions.sh should be in the release tarball, however I don't see it in the 0.18.0 release:
 ddev-0.18.0 $ find . -name ddev_bash_completions.sh
 ddev-0.18.0 $

If this is intentional, I'm happy to create a PR to update the docs.
I do have the bash completions present on OS X installed via brew, so no problem there.

You don't say which tarball you downloaded. The macos tarball has it,
$ tar -tzf ddev_macos.v0.18.0.tar.gz
ddev
ddev_bash_completion.sh

And the linux tarball has it:
$ tar -tzf ddev_linux.v0.18.0.tar.gz
ddev
ddev_bash_completion.sh

I see - you're looking for it with an 's' in the name.  And I see that https://github.com/drud/ddev/blob/f9a31bb7e33727eed8f238efd64ae9968b5a36e6/docs/users/cli-usage.md does have it wrong. Thanks! And a docs PR removing the 's' would be lovely! Of course we can get that done pretty easily too. Low hanging fruit!

Thanks for checking @rfay! I was mistakenly looking within the source tarball, which is why I didn't see it. Docs clearly say release tarball...
I created #882 to remove the 's' from the filename in the docs.


Python 2 compatibility

There is a problem that I think it is not fixable without breaking changes.
======================================================================
FAIL: test_is_png (__main__.Main) [file name]
----------------------------------------------------------------------
Traceback (most recent call last):
  File "test.py", line 28, in test_is_png
    assert is_png(str(file))
AssertionError

----------------------------------------------------------------------

In Python 2, bytes is identical to str, so these code would fail:
if isinstance(file, bytes):
  png_head = file[:8]
else:
  with open(file, "rb") as f:
    png_head = f.read(8)

@robmcmullen Any ideas?

The only thing that comes to mind is to use try/except blocks, so instead of checking with isinstance, you just keep trying stuff based on the methods you need rather than the specific object types.

If we use try/except, whenever a bytes object is sent to this library, the library would make a request to the file system. It doesn't make sense IMHO.
Here is a breaking change solution:

Just always use bytes for input/output and leave file system/type conversion logic to users.

Provide some shortcuts to create APNG from files:
# read the file into bytes and convert it to PNG automatically.
APNG.from_files(["1.jpg", "2.jpg", "3.jpg"], delay=100).save("result.png")

# also accept a list of options
APNG.from_files([
  {
    "filename": "1.jpg",
    "delay": 100
  },
  {
    "filename": "2.jpg",
    "delay": 200
  },
  {
    "filename": "3.jpg",
    "delay": 300
  }
])


Merge pull request #1 from aclist/main

Get on their level

I'm clicking too many things. Ignore this.


added support to disable feign parent configurations, fixes gh-132

Adds support to disable feign parent configurations.
Can be controlled with the inheritParentContext parameter on @FeignClient.
fixes gh-132

I wonder if there is a way to do this without adding a new attribute on @FeignClient. Maybe an optional FeignClientConfigurer bean with the new boolean as well as the primary boolean from the annotation. That one could be deprecated and removed in 3.0.0. This could go in the 2.2.x branch as well.

@matt62king thanks for the PR. After addressing @spencergibb 's comment above, could you submit it against the 2.2.x branch so that it gets into the Hoxton release train?

@OlgaMaciaszek made changes and switched to 2.2.x. Lots of conflict. Would I pulling in things that don't belong?
Would it be better off to rebranch and cherry pick?

@OlgaMaciaszek Made new pr pointing to 2.2.x
https://github.com/spring-cloud/spring-cloud-openfeign/pull/326
can fix the conflicts here if one point to master is needed

We merge forward

made new pr to 2.2.x https://github.com/spring-cloud/spring-cloud-openfeign/pull/326


is it possible to add thi as navbar button?

figured it out!. used   self.navigationController!.view.addSubview(downMenuButton)


Explain federal plugin structure better

I'm currently migrating a plugin to the new federal plugin structure.
I have two (somewhat interconected) problems:
How does federal plugin registration actually work?
Developing packages & plugins on flutter.dev refers to How To Write a Flutter Web Plugin: Part 2. There we are walked through the porcess of creating a federal plugin structure. But it is never explained, how flutter actually sets UrlLauncherPlatform.instance. And for web, the impelmented UrlLauncherPlugin  contains a misterious, not documented function
  /// Registers this class as the default instance of [UrlLauncherPlatform].
  static void registerWith(Registrar registrar) {
    UrlLauncherPlatform.instance = UrlLauncherPlugin();
  }

My guess is, that the pubspec.yaml tells flutter to look into the  url_launcher_web.dart file for a UrlLauncherPlugin class, which should have a register function by this:
flutter:
  plugin:
    platforms:
      web:
        pluginClass: UrlLauncherPlugin
        fileName: url_launcher_web.dart

Could you please point me to where plugin registration is documented?
Am I forced to use a class in Android and iOS?
While the Android and iOS versions of my plguin contain platform specific code (in form of native c code), they don't contain java or swift code. I don't want to be forced to have a java (or swift) class in my plugin, but it seems if I remove the generated one building fails. I also removed
flutter:
  plugin:
    platforms:
      android:
        package: eu.epnw.opus_flutter_android
        pluginClass: OpusFlutterAndroid

from my pubspec.yaml, and replaced it with
flutter:
  plugin:
    platforms:
      android:
        pluginClass: OpusFlutterAndroid
        fileName: opus_flutter_android.dart

like in the example above, but now flutter packages get complains about
Invalid plugin specification opus_flutter_android.
Invalid "android" plugin specification.

I guess Android is not allowed to use a dart file for plugin registration?
I could live with just erasing all the content from the generated java class like here, but then again: How is my plugin registered?
Lastly I want to mention while How To Write a Flutter Web Plugin: Part 2 states

Before we walk through how to actually implement a plugin, it’s worth discussing how we structure multi-platform plugins on the Flutter team. We intend for the plugins owned by the Flutter team to be models showing best practices for implementing Flutter plugins.

flutters own plugins don't follow the recommended approach for Android and iOS. Android and iOS code seem to be part of the app-facing package and not delegated to a platform specific plugin.
Edit: What I mean by this: Does that mean that we should not use the federal system for Android and iOS, or have you just not migrated yet 😅?

Most of your questions are not actually specific to federation, so the title here doesn't actually reflect the information you are looking for, FYI.

And for web, the impelmented UrlLauncherPlugin  contains a misterious, not documented function

It's not documented because the plugin docs don't currently cover web. I've filed https://github.com/flutter/flutter/issues/83139 for this.

Am I forced to use a class in Android and iOS?

Currently, yes. Plugins have historically been specifically for native code using the plugin APIs and method channels; support for alternate "plugin-ish" approaches, such as FFI implementations, is still in early stages.

I also removed [...] from my pubspec.yaml, and replaced it with [...] like in the example above, but now flutter packages get complains

The structure of those sections are platform-specific; you cannot copy and paste between them.

How is my plugin registered?

Native code is registered in platform-specific ways generated by the build system. There is currently no way to automatically do it for Dart code on mobile, per the issue linked above.

flutters own plugins don't follow the recommended approach for Android and iOS

See https://github.com/flutter/flutter/issues/68498
I'm going to close this since there are specific issues covering different aspects of what's raised here. The overall point that docs and examples currently haven't caught up with all the recent changes (new platforms, federation, FFI) is certainly valid, and something we plan to address via those issues (and others).


Moving cursor while zooming leads to cursor position mismatch

See this screen capture.

I figured out what is wrong here. Will try to create a fix tomorrow, the DM Section still uses the old implementation of the pan-zoom view which is performing a bit poorly and is also clumsy to sync state with react. The whole replacement will probably not make it into 1.6 but a quick fix should be possible.


dont support to judge the table exist?

Send a Get request to the table you want to check and see if it returns TableNotFound ( https://godoc.org/github.com/tsuna/gohbase#pkg-variables)

thanks !


ACDC EventBased is also broken

For my record :), Julian mentioned ACDCs using EventBased job splitting are creating duplicate lumis. It seems it also creates less jobs than what it should. I'll investigate it

It seems we need to change how we upload information to the ACDC server, if we want to make it to work for MC from scratch. This is the - important - information currently uploaded:
fileset['events'] which is the same value as 'RequestNumEvents'. Instead, it should contain EventsPerJob for this job.
fileset['first_event'] which is always 1.
fileset['last_event'] which is always 0.
fileset['runs'] which also contains a list of lumis. Since this can change, it seems useless to me.
If we properly upload the first and last event, then it should be enough to recover the correct events.

Ok, I did some more progress on this (btw, feel free to assign it to me and don't bother reading it for now :)).
Here is the place that we get the right information about first/last things:
https://github.com/dmwm/WMCore/blob/master/src/python/WMComponent/ErrorHandler/ErrorHandlerPoller.py#L193
e.g.:
{'LastRun': 1L, 'FirstRun': 1L, 'inclusivemask': True, 'runAndLumis': {1L: [[529L, 533L]]}, 'LastEvent': 133001L, 'FirstEvent': 132001L, 'LastLumi': 533L, 'FirstLumi': 529L}

Then it gets inside this if
https://github.com/dmwm/WMCore/blob/master/src/python/WMCore/ACDC/CouchFileset.py#L106
which uses a "wrong" info from oracle:
https://github.com/dmwm/WMCore/blob/master/src/python/WMComponent/ErrorHandler/ErrorHandlerPoller.py#L354
e.g.:
>>> tmpJob['input_files']
[{'lfn': 'MCFakeFile-amaltaro_MonteCarlo_Ext_MonteCarlo_300jobs_testACDC_Alan_150421_155605_676-Production-e9e0b314815afb0e6cd451c154b8d795', 'locations': set(['storage01.lcg.cscs.ch', 'red-srm1.unl.edu']), 'first_event': 1L, 'se_name': 'cms-se.hep.uprm.edu', 'checksums': {}, 'id': 641L, 'size': 0L, 'runs': 'WMCore.DataStructs.Run.Run object', 'last_event': 0, 'newlocations': set([]), 'jobid': 497L, 'newRuns': 'WMCore.DataStructs.Run.Run object', 'parents': set([]), 'events': 250000L, 'merged': 0L}]

Closed by #5860


AZJSON writer: get_total_write API

Current JSON writer API when used with non-contiguous memory only allow user to get the amount of bytes written in the last block of memory. If user wants to write a JSON and want to know the total number of bytes written by JSON writer, then additional state is required via application, which needs to be updated when allocation callback is called by writer and then at the end call az_json_writer_get_bytes_used to know size used in last block. This causes additional state management/updates for application side. If we have API, which application can call at the end of json writer, then application does not need to track of this state or only update at the end when all write is completed.
I see that az_json_writer has an internal field that keep track of this information. Can this field be exposed as a public field.

@ahsonkhan This api sounds nice to have but not required for GA.  Was this requested by a customer?

Based on discussion with @hihigupt, moving this issue back to October, but it can be done post-GA.
This will be needed for the upcoming PNP support.

JSON writer when used with chunk memory requires additional state/logic to keep track of number of bytes written by JSON writer. This additional state and logic required by caller can be removed if JSON writer exposes the API around existing field total_bytes_written.

We'll work to add this for the Feb milestone.


[Transforms] Update baselines: remove parenthesis around comma expression in for l…

Fix #8046

:+1:


Add opentelemetry/node-tracer package and implementation

Originates from https://github.com/open-telemetry/opentelemetry-js/issues/6.
Add an automatic tracer (automatically patches well-known modules) with CLS or https://github.com/open-telemetry/opentelemetry-js/tree/master/packages/opentelemetry-context-async-hooks package.
OpenCensus implementation: https://github.com/census-instrumentation/opencensus-node/tree/master/packages/opencensus-nodejs-base/src/trace

Closed via #107 and #140.


Adding Cloud 66 project and products to the landscape

We would like to add our open source project Habitus in the CI/CD box
Project name: Habitus
Category: CI/CD
Git: https://github.com/cloud66/habitus
Web: http://www.habitus.io/
Logo: https://cloud66.com/images/habitus-by-cloud66-logo.png
(Habitus is the open core of Skycap, below)

We would like to add our commercial product Cloud 66 Skycap, a Continuous Delivery Pipeline built for containers, in CI/CD
Product name: Cloud 66 Skycap
Category: CI/CD
Web: https://cloud66.com/containers/skycap
Logo: https://cloud66.com/images/cloud66-skycap-logo-c.png

We would like to replace the generic Cloud 66 logo in Platforms, with our commercial product Cloud 66 Maestro, an application lifecycle management tool built for containers
Product name: Cloud 66 Maestro
Category: Platforms
Web: https://cloud66.com/containers/maestro
Logo: https://cloud66.com/images/cloud66-maestro-logo-c.png

Closing as these updates were included in the most recent version https://github.com/cncf/landscape#current-version

Thank you!


Revisit schemas to make validation stricter.

Our jsonschemas had never been actually tested on our real Documents either on the ophyd side or the metadatastore side, and I took some liberties to get things going because less-than-perfectly-strict validation is better than no validation.
Here's what I remember removing:

Validate the type of shape to be an array or null. If I understood correctly, it seems that tuples don't get interpreted as arrays. @tacaswell
Validate the details of some of the nested Dynamic Documents.

There might be others that I forgot, so to be thorough we should diff these against the documented ones. I also updated a bunch of names. Our docs should be updated there.
#128

This should include ripping the schema out into a stand-alone repo.

[bump] Schema is in its own repo now. What's the status on the validation, @arkilic? (this is assigned to you for whatever reason)

bluesky and mds informally uses this validation scheme via json validation. @danielballan and I are planned to be using event-model by next downtime in bs and mds

@arkilic I don't think @klauer was asking what the event-model repo is about, I think he's wondering if any work has been done on making the schemas stricter. AFAIK no work has been done. Would you be willing to take a careful look at the schemas and see if we can be doing more to validate, @arkilic?

@klauer, @tacaswell has done some work making the schema stricter by enforcing data keys and ensuring one run_stop per run_start during the migration. I need more details on Validate the details of some of the nested Dynamic Documents. This is something I can take care of if I have more details. Let's discuss what needs to be tackled tmrw.
 We could touch base on this.

Wfh Wednesday (also down with @tacaswell plague) are you in tomorrow?

The goal as I recall is to understand jsonschema and its limitations and capabilities and more detail and then read our schemes carefully and make them more specific where appropriate.


Bug: Link button to GitHub Repo

Description

Currently, we have nowhere to go from the button in our landing section

Proposed Solution

A link can be added to the landing sections button so that on clicking it we can go to the GitHub page

Screenshots

Browser 🥦
Google Chrome
Checklist ✅

[X] I checked and didn't find similar issue
[X] I have read the Contributing Guidelines
[ ] I am participating in JWOC
[ ] I am participating in IWOC
[ ] I am willing to work on this issue (blank for no).

I would like to work on this issue.

Hi Tamal, I recently discovered this project and was truly captivated by its concept. I'm eager to lend my support and contribute to its development by tackling this specific issue. Could you please confirm whether I can proceed to start working on it? 😊


Allow Submit query text without trigger query changes

I have the use case, that when filling the suggestion list using values that come from OnQueryTextListener when user click on a suggestion i want to trigger a full search, like Google Play and other apps using
 searchView.setOnItemClickListener(new AdapterView.OnItemClickListener() {
     @Override
     public void onItemClick(AdapterView<?> parent, View view, int position, long id) {
         searchView.setQuery(suggestion, true);
     }
 });

but with this trigger an OnQueryTextListener.onQueryTextChange() before OnQueryTextListener.onQueryTextSubmit() and that trigger is unnecessary in mostly cases
Digging in the code i see the function onSubmitQuery(); just allowing a String as parameter and provide a public method submitQuery(String query) that call onSubmitQuery internally that not trigger OnQueryTextListener.onQueryTextChange() solve the problem.
I could do it, but first i want to know your opinion.

searchView.setSubmitOnClick(true);

Wow, I totally missed this issue, sorry @ffgiraldez .
As @phamvansy posted, you can do this from last update by:
searchView.setSubmitOnClick(true);


WIP: IMA: Implement support for an internal text-based IMA policy based on rules

This PR implements support for an internal text-based IMA policy based on rules rather than the hardcoded evaluation that we currently have. The idea is that this will provide more flexibility for evaluating IMA log entries in the future where the user gets control over adding such rules to the IMA runtime policy. For now we need an internal policy that provides (ideally) 100% compatibility to the hard coded evaluation. The current internal policy looks like this:
LEARN-KEYS: ignore-keyrings-ref=ignored_keyrings allowed-hashes-ref=keyrings
DEVICE-MAPPER-CHECK
FILE-NAMES: regex-ref=excludes
IMA-SIGNATURE-CHECK
FILE-HASHES: map-ref=digests target=ACCEPT

Before we try to invent our own policy language, I think it makes sense to look if we then take it a step further and implement something like Rego (https://www.openpolicyagent.org/docs/latest/policy-language/) fully.
I know that @galmasi has some experience with this and ran some experiments regarding measured boot.

Before we try to invent our own policy language, I think it makes sense to look if we then take it a step further and implement something like Rego (https://www.openpolicyagent.org/docs/latest/policy-language/) fully.

I had at least looked at it before but it wasn't clear to me how to use this for what we have so far, such as list with regular expressions and maps with filenames and list of hashes and verification of signature and handling of device mapper and the learning of keys. I would be curious to see how these things would be dealt with in this language.

Other format of rules introduced in this PR look like these here:
FILE-HASHES: target=ACCEPT filename=/usr/bin/dd hash=sha256:d33d5d13792292e202dbf69a6f1b07bc8a02f01424db8489ba7bb7d43c0290ef
FILE-HASHES: target=ACCEPT filename=/usr/bin/zmore hash=sha256:b8ae0b8dd04a5935cd8165aa2260cd11b658bd71629bdb52256a675a1f73907b

FILE-NAMES: regex=ACCEPT:/usr/bin/dd
FILE-HASHES: target=ACCEPT filename=/usr/bin/zmore hash=sha256:0000000000000000000000000000000000000000000000000000000000000000 hash=sha256:b8ae0b8dd04a5935cd8165aa2260cd11b658bd71629bdb52256a675a1f73907b

FILE-NAMES: regex=ACCEPT:/usr/bin/dd regex=ACCEPT:/usr/bin/zmore

Other format of rules introduced in this PR look like these here:
FILE-HASHES: target=ACCEPT filename=/usr/bin/dd hash=sha256:d33d5d13792292e202dbf69a6f1b07bc8a02f01424db8489ba7bb7d43c0290ef
FILE-HASHES: target=ACCEPT filename=/usr/bin/zmore hash=sha256:b8ae0b8dd04a5935cd8165aa2260cd11b658bd71629bdb52256a675a1f73907b

FILE-NAMES: regex=ACCEPT:/usr/bin/dd
FILE-HASHES: target=ACCEPT filename=/usr/bin/zmore hash=sha256:0000000000000000000000000000000000000000000000000000000000000000 hash=sha256:b8ae0b8dd04a5935cd8165aa2260cd11b658bd71629bdb52256a675a1f73907b

FILE-NAMES: regex=ACCEPT:/usr/bin/dd regex=ACCEPT:/usr/bin/zmore

I don't know if I'm the only one with this feeling, but the proposed language doesn't look very intuitive, meaning that is not clear for someone to read it and immediately understand what is happening. I understand the focus is for machines to read and generate the policies, but it would be nice to keep the language sufficiently simple that allows manual adjustment.
I think we should discuss the format a bit further with the community before implementing it.
Are we considering how policies will be combined, or extended? For example, a policy that uses a base policy and adds more rules on top of it.
Also we should consider the case where a system is updated as the main use case as that is probably the most common case when the policies need to be adjusted.

I don't know if I'm the only one with this feeling, but the proposed language doesn't look very intuitive, meaning that is not clear for someone to read it and immediately understand what is happening. I understand the focus is for machines to read and generate the policies, but it would be nice to keep the language sufficiently simple that allows manual adjustment.

I think we should discuss the format a bit further with the community before implementing it.

Sure, make a proposal for a language.

Are we considering how policies will be combined, or extended? For example, a policy that uses a base policy and adds more rules on top of it.

Rules need a processing order so just concatenating them from two different policies is certainly not possible. They would need to be merged in some 'right' way. It may not always be possible for a machine to do it.

Also we should consider the case where a system is updated as the main use case as that is probably the most common case when the policies need to be adjusted.

Right, we need tools to be able to get a handle on the policy.

Are we considering how policies will be combined, or extended? For example, a policy that uses a base policy and adds more rules on top of it.

My gut feeling is that something like that may become handy in the future. The advantage of separate excludelist, allowlist, rejectlist etc. processing is that each of these lists can be extended and the result still makes sense. Once we start combining allow/exclude/reject rules within a single file then making such extensions won't be "guaranteed", although such a format would be more "rich". ATM I can't decide which benefits out-weights. Would the ability to freely combine rules really provide benefits for real deployments? It would be nice to have those backed up by some "user stories".

My gut feeling is that something like that may become handy in the future. The advantage of separate excludelist, allowlist, rejectlist etc. processing is that each of these lists can be extended and the result still makes sense.

For as long as you have good tools to manage these lists and don't want to do fancy things. Moving all those packages with recent CVEs from an allowlist into a rejectlist obviously needs a lot more involvement than what one would like and basically means starting over with a new policy, though I wouldn't know where to get the hashes for the packages with CVEs from. Or adding those packages I just installed from EPEL/pypy/etc. to the allowlist while the rest is covered by signature verification is another interesting challenge -- or removing those old packages' hashes from the allowlist that I just upgraded. Policy management is going to be the ultimate challenge.

Having worked on the measured boot policy evaluation language, I share @ansasaki concern about ease of use and applicability (I do not think what we have done on mb is particularly usable and maintainable).
While I do not have a proposal for a language ready at hand (I know for a fact that @galmasi and @niteeshkd have been looking into this), I do believe that a crucial property is the ability to combine different policies - as in "layers" - in order to form "meta-policies".
Our (at least myself @galmasi @niteeshkd) grand vision has always been to provide keylime with the ability of offloading the analysis of a "fully checked" (i.e., replayed against a virtual PCR and compared with the quote) IMA log to an "custom policy engine" capable of evaluating the contents (which could be even an external engine). Following this vision, I believe if we could keep the old "built-in" evaluation and have this one as the first example implementation of this "pluggable" policy, the barriers for acceptance would be lowered.

While I do not have a proposal for a language ready at hand (I know for a fact that @galmasi and @niteeshkd have been looking into this), I do believe that a crucial property is the ability to combine different policies - as in "layers" - in order to form "meta-policies".

Then let's see what others have.

Following this vision, I believe if we could keep the old "built-in" evaluation and have this one as the first example implementation of this "pluggable" policy, the barriers for acceptance would be lowered.

I would try to avoid enabling multiple pluggable policies if possible. The policies need to be reflected not just in keylime verifier but also in all the tools and the more different policies we have the more we need to maintain... My, $0.02.

Rules need a processing order so just concatenating them from two different policies is certainly not possible. They would need to be merged in some 'right' way. It may not always be possible for a machine to do it.

TL;DR: I was thinking if the processing order is fixed and the order of the entries in the "new language" doesn't matter.
Considering the expected order of processing:

Process exclude list
Process reject list
Process signature verification
Process allow list
Reject everything else

Is there a reason, for example, to accept some entry before checking if it should be ignored?
I was thinking that maybe it doesn't make sense to allow the policy to change the order of operations, which means that the entries of the policy should not be executed in the order they are declared.
This would remove the importance of the order in which the entries appear in the new policy format, as all excluded entries would be processed first, followed by rejected entries, and so on. If this is the case, it would be easy to combine 2 policies by simply concatenating them.

Rules need a processing order so just concatenating them from two different policies is certainly not possible. They would need to be merged in some 'right' way. It may not always be possible for a machine to do it.

TL;DR: I was thinking if the processing order is fixed and the order of the entries in the "new language" doesn't matter.

If we give users control over the language they can put the policy 'commands' in any order they want to. If we don't give them control over it we don't have to deal with the issue of potentially having to merge such rules. Maybe we should just hard code a reject list into the current code and be done with it.

Considering the expected order of processing:
1. Process exclude list

2. Process reject list

I would actually revert the order of the first two now so that an entry that is rejected will never be just accepted by the exclude list.

3. Process signature verification

4. Process allow list

5. Reject everything else

Is there a reason, for example, to accept some entry before checking if it should be ignored?

Not that I would know a reason atm.

I was thinking that maybe it doesn't make sense to allow the policy to change the order of operations, which means that the entries of the policy should not be executed in the order they are declared.

If we give users control over the policy language then they should also have control over the processing order. Otherwise let's not give them control over it at all. As mentioned, a valid choice is to continue with the current hard coded processing and not even go near a policy language. Unless we want to give users control over the language there's probably no need to persue it.

This would remove the importance of the order in which the entries appear in the new policy format, as all excluded entries would be processed first, followed by rejected entries, and so on. If this is the case, it would be easy to combine 2 policies by simply concatenating them.

When I look at a list of rules I look at the ordering as well. I don't think it's very intuitive that the rules wouldn't be processed in the order they are shown.

Let's aim for a simpler approach.


Add a QC check to prevent OMIM SubClassOf OMIM

See #730
In general OMIM IDs be equivalenced only to "gene-level" disease classes. This needs to be written up in the docs and a check added. We should also consistently use subset tags to denote levels in the ontology.
The gene-level metaclass is classes that are defined according to a single gene
If we see a case where we infer one OMIM to be subclass of another this is likely a mistake, see docs on the "prototype" problem (in which a disease "Foo" is later split into "Foo 1" and "Foo 2" with the label "Foo" being ambiguous wrt whether it denotes the "classic" form "Foo 1" or a superclass).
There are cases where some OMIM IDs may still represent something above the gene level, and this is also tied in with susceptibility

@cmungall , is this going to implemented globally?  I just encountered https://monarchinitiative.org/disease/MONDO:0008947 where
bilateral striopallidodentate calcinosis  has a synonym of basal ganglia calcification, idiopathic, type 1 which is gene-specific.  basal ganglia calcification, idiopathic, 1 MONDO:0024538 differs only by the term 'type'

And Trichohepatoenteric syndrome type 1 a synonym of tricho-hepato-enteric syndrome MONDO:0009105 when trichohepatoenteric syndrome 1 MONDO:0024541 also exists  (that pesky 'type')

@nicolevasilevsky
Here is an up-to-date list:
https://docs.google.com/spreadsheets/d/1CJPJ8VasB-kGaUqY0jBBvFf2IwW5xbd3ZiZazx67eHo/edit?usp=sharing
Let me know how you want to go about this.

FYI, This is the check:
SELECT ?term ?term_label ?p ?pn ?xc ?xp {
   ?term rdfs:subClassOf ?p .
   ?exp owl:annotatedSource ?term ;
        owl:annotatedProperty oboInOwl:hasDbXref ;
        owl:annotatedTarget ?xref;
        oboInOwl:source ?source .
   ?exp_p owl:annotatedSource ?p ;
       owl:annotatedProperty oboInOwl:hasDbXref ;
       owl:annotatedTarget ?xref_p;
       oboInOwl:source ?source_p .
   ?term rdfs:label ?term_label .
   ?p rdfs:label ?pn .
   FILTER (isIRI(?term) && regex(str(?term), "^http://purl.obolibrary.org/obo/MONDO_"))
   FILTER (isIRI(?p) && regex(str(?p), "^http://purl.obolibrary.org/obo/MONDO_"))
   FILTER(regex(str(?xref), "^OMIM:"))
   FILTER(regex(str(?xref_p), "^OMIM:"))
   FILTER(str(?source)="MONDO:equivalentTo")
   FILTER(str(?source_p)="MONDO:equivalentTo")
}

I eyeballed some and some of these equivalencies come from Orphanet.

(The important thing here is to identify a systematic mistake we can just break in one go, or just keep going through the table until its done)

I'll take a look at this and think about it.
Some of these are being addressed in this ticket:
https://github.com/monarch-initiative/mondo/issues/962

There are some cases where terms like this (https://omim.org/entry/109100) are used as grouping classes, which I don't necessarily think is wrong, but it is going to flag errors for this check.

And Trichohepatoenteric syndrome type 1 a synonym of tricho-hepato-enteric syndrome MONDO:0009105 when trichohepatoenteric syndrome 1 MONDO:0024541 also exists (that pesky 'type')

[ ] This needs to be fixed. I'll fix this.

The other example above from @maglott has been resolved. (Thanks for your comments @maglott!)


remove Button undefined variable name.

in Laravel 5.2
I have the same issue than
#180
and I did the following to make it work:
public function removeButton($name)
    {
        $this->buttons = $this->buttons->reject(function ($button) use (&$name){
            return $button->name == $name;
        });
    }

Oh i see this was solved already but my composer has this package fixed,
	"backpack/crud": "^3.0",

Hi @Darival ,
Yes, follow this upgrade guide and you issue should be fixed.
Cheers!


AlignDoubleArrowFixer - fix new buggy case

fixes #953

Could you help with it @dericofilho , please ?

Is my solution correct @dericofilho ?

LGTM

merged


Add DW UI test to Verify CPU and Memory resource usage Exceeds warning threshold

Closes https://issues.redhat.com/browse/RHOAIENG-16160

Added test to Verify that CPU and memory resource usage surpass the warning threshold when the requested resources exceed 150% of the shared quota.
Enhanced the Kueue workload script to support parallelism specifications for threshold warning verification
Updated the teardown step for  Verify Requested resources When Multiple Local Queue Exists to make sure resources deleted

Tested the all DW UI tests here /job/rhoai-test-flow/2137


Any particular reason cudamat isn't on PyPI?

Quite possibly the most trivial issue ever to be opened on github, but is there any particular reason cudamat isn't on PyPI? It seems like an excellent package and would be a great addition to the index.

Mhm, I'm the one who should probably do that, but there were two points holding me back: a) I'm not the original author and b) I wanted to include Windows support. For a), I'll try contacting Vlad to see if he's fine with it, and b) has been solved in #42, but in a very hackish way; I'd prefer to implement #53.

I'd be happy for cudamat to be included on PyPI.
On Mon, Sep 14, 2015 at 11:28 AM, Jan Schlüter<EMAIL_ADDRESS>wrote:

Mhm, I'm the one who should probably do that, but there were two points
holding me back: a) I'm not the original author and b) I wanted to include
Windows support. For a), I'll try contacting Vlad to see if he's fine with
it, and b) has been solved in #42
https://github.com/cudamat/cudamat/pull/42, but in a very hackish way;
I'd prefer to implement #53 https://github.com/cudamat/cudamat/issues/53
.
—
Reply to this email directly or view it on GitHub
https://github.com/cudamat/cudamat/issues/55#issuecomment-140030468.

Ah, hello, good to see you're still watching :)
I've set up a milestone for 0.4 and tagged some issues I'd like to have resolved before releasing it. We can't simply register the previous release (0.3) because it didn't have a setup.py yet, and I wouldn't want to register the current state of the repository because the setup.py is very hackish in terms of Windows support. I'm currently not actively using cudamat (let alone Windows), so it may be a while until I get around doing that -- but any help is welcome!

:+1: on adding cudamat to PyPI


Wrong added_in version for "handshake" variations with a single skin tone.

These are listed as 3.0, but 3.0 didn't have skin toned handshakes. The multi skin tone versions are correctly listed as 14.0.
This prevents correct browser support detection in our fork of the js lib.

This actually looks like a bug in the unicode source files, they versioned as 3.0 here too.
https://www.unicode.org/Public/emoji/14.0/emoji-sequences.txt
This looks like it crept in for a lot of other emoji since version 13 of those files. e.g.
index pointing up: light skin tone                             # E1.0

v12 looks more correct:
https://www.unicode.org/Public/emoji/12.0/emoji-sequences.txt
index pointing up: light skin tone                             #  8.0

I think this is only manifesting as an issue now because it's hitting brand new versions of quite old emojis. The other emojis this affects have old enough skin tones that our lib is already treating them as universally supported.

Handshakes with skin tones are listed in version 3.0.

Looks like they were never included in the RGI (Recommended for General Interchange) list until 14.0. They're listed as being introduced in 14.0 here https://emojipedia.org/emoji-14.0/
Some more info here https://www.unicode.org/reports/tr51/tr51-21.html#multiperson_skintones

OK, that's kind of awkward. I'd say the data should reflect the most recent version for cases like this. Might need to be special cased in the build if that info isn't available from any unicode.org source files.

Pay attention to this:

As of version 13.0, data file comments use the labeling convention “Ex.x”. This label corresponds to the Emoji version when the emoji character or emoji sequence was first defined in associated data files.

I understand, but that's not helpful in this case for anyone trying to determine compatibility of native emoji rendering while supporting a range of different OS versions.


JsonPath.read() ignores REQUIRE_PROPERTIES config option when AS_PATH_LIST is set

Description
When I specify this (Note: REQUIRE_PROPERTIES is NOT set):
Configuration jsonCfg = Configuration.builder().options( Option.AS_PATH_LIST ).build();
And do this:
String jsonStr = "{ \"foo\": { \"bar\" : \"val\" }, \"moo\": { \"cow\" : \"val\" } }";
Predicate[] predicates = {};
DocumentContext dCtx = JsonPath.using( jsonCfg ).parse( jsonStr );
readPaths = dCtx.read( JsonPath.compile( "$.*.bar", predicates ) );

Actual Behaviour
I get this:
Exception in thread "main" com.jayway.jsonpath.PathNotFoundException: No results for path: $['moo']['bar']
	at com.jayway.jsonpath.internal.token.PathToken.handleObjectProperty(PathToken.java:53)
	at com.jayway.jsonpath.internal.token.PropertyPathToken.evaluate(PropertyPathToken.java:44)
	at com.jayway.jsonpath.internal.token.PathToken.handleObjectProperty(PathToken.java:71)
	at com.jayway.jsonpath.internal.token.WildcardPathToken.evaluate(WildcardPathToken.java:32)
	at com.jayway.jsonpath.internal.token.RootPathToken.evaluate(RootPathToken.java:53)
	at com.jayway.jsonpath.internal.CompiledPath.evaluate(CompiledPath.java:53)
	at com.jayway.jsonpath.internal.CompiledPath.evaluate(CompiledPath.java:61)
	at com.jayway.jsonpath.JsonPath.read(JsonPath.java:176)
	at com.jayway.jsonpath.internal.JsonReader.read(JsonReader.java:146)

Expected Behaviour
I expected a List result containing a single path: $[foo].[bar] because I did not have the REQUIRE_PROPERTIES option set.  I would only expect to see PathNotFoundException if REQUIRE_PROPERTIES was set.

Forgot to mention, stepping through with the debugger, it is clear that REQUIRE_PROPERTIES is not being set by default.  When I submit the ReadContext.read() request, there is only a single config option in the list - AS_PATH_LIST.

I tried this in version 2.0.0 and 2.1.0 and it works as expected
@Test
public void issue_143() {
    String json = "{ \"foo\": { \"bar\" : \"val\" }, \"moo\": { \"cow\" : \"val\" } }";

    Configuration configuration = Configuration
              .builder()
              .options( Option.AS_PATH_LIST )
              .build();

    List<String> pathList = JsonPath
              .using(configuration)
              .parse(json)
              .read("$.*.bar");

    assertThat(pathList).containsExactly("$['foo']['bar']");
}

What version are you using?

I am using 2.0.0.

And the test I provided fails?
Sent from my iPhone

On 26 nov. 2015, at 19:28, bradleymorris<EMAIL_ADDRESS>wrote:
I am using 2.0.0.
—
Reply to this email directly or view it on GitHub.

Yes, this test fails.  I had to refactor the assertThat() line to:
Assert.assertThat(pathList, hasItem("$['foo']['bar']"));
...but it does not matter. I get precisely the same Exception and stack trace that I provided in the initial bug description when read() is called.
For the record, 'configuration.jsonProvider().getClass().getName()' tells me I am using the com.jayway.jsonpath.spi.json.JsonSmartJsonProvider.

The test works for me too both from Eclipse and shell. @bradleymorris, how do you run the test?

I am running the test with a JUnit-natured run configuration in Eclipse.

I cannot reproduce this. Here's what I do (with current git master):

open json-path project in eclipse
open com.jayway.jsonpath.old.IssuesTest
right-click on the class name and choose Run As -> JUnit Test
The test completes successfully, including the issue_143 method.

Can not reproduce


security/acme-client: add support for deSEC.io API

Implements deSEC.io API
Took request #2057 as template. Unfortunately not testet, because no test infrastructure available here.
Thanks for merge!

my editor "corrected" wrong idents on AcmeClient.xml, hope this is not a problem?

I have no idea why you (incorrectly) renamed the file again in https://github.com/opnsense/plugins/pull/2120/commits/e26760021b9c9003a74af8845fb4cd03919f2c26, but I'll fix this post-merge ;)

Merged, thanks for your contribution!

@fraenki, I was confused about the whole desec/dedyn thing. Thanks for your help!


requesting support for tensor concatenation (torch.cat)

torch.cat is an essential function for many models. It would be good to have support for tensor concatenation

It is there, it's just really, really non-discoverable and should be redone as torch.cat
It's an extension method to IList<Tensor>, e.g. arrayOfTensor.cat(dimension)
https://github.com/xamarin/TorchSharp/blob/8adf8326b2eb998a0998d5b0235b8bb48b324a37/src/TorchSharp/Tensor/TensorExtensionMethods.cs#L172

thanks for clarifying @dsyme. I agree something like torch.cat would be easier to find, especially if you are porting an existing model

With #302, 'torch.cat' is indeed where this function is to be found.


DBZ-4027: Make signalling channel configurable

related to https://github.com/debezium/debezium/pull/4477

Seems very unstable..tests passing locally


⚠ 5.0.0 to 5.1.1 Deprecated - These version may be blocked or rate limited. Please update to 5.1.2 or newer ⚠

What's on your mind?
Notice
As we continue to improve our systems with the new User Model updates, we found a bug in our Android SDK 5.0.0 to 5.1.6 versions that is causing exceptional load on our API. Some API requests might be blocked during peak load on these versions of SDKs used in Android apps. This means new users may not be created and current user data may not be updated (like tags, last session, session count, etc) during peak times. The impacted SDK versions are:

OneSignal-DotNet-SDK 5.0.0 to 5.1.1
OneSignal-Android-SDK 5.0.0 to 5.1.6

To ensure your Android app isn't impacted, we ask that you upgrade to the latest version of our SDKs and release the updated version of your app as soon as possible. Please make sure you update to at least one of the following versions or newer:

OneSignal-DotNet-SDK 5.1.2
OneSignal-Android-SDK 5.1.8

Apps on SDKs older than 5.0.0 are not affected.

Ok we who use Xamarin.Forms cannot update it if it no longer works.
What must we do


Considerations before 1.0 release

In this issue we can keep track of issues that arose in reviews, the resolution of which might affect our public API.

ThingPersisted/ThingLocal - might be better to rename these, since the former needn't actually be persisted.
"metadata" - the code refers to metadata, when really it's referring to our specific metadata (e.g. where a LitDataset was fetched from). Thus, maybe we need to rename it to differentiate it from other types of metadata that the user might add to a Dataset by calling it, say "LitMetadata"? (And LitMetadataStruct and hasLitMetadata, etc.)
*Struct - I'm not sure if that's an appropriate name for the properties that an object might have (e.g. DiffStruct).

The API has been subjected to a review, including the points mentioned above, so I'm closing this.


The popup cannot be closed by clicking the icon multiple times

Phenomenon：
The first time you click on the icon, the popup will appear. If you click on the icon again, it will first close and then be displayed again. As a result, the popup cannot be hidden.

Closure of the popup when the expected behavior icon is clicked again, right? @giantss

https://github.com/SalihCanBinboga/info_popup/assets/13778798/bbbfbf0b-9add-48d3-b575-08f55b32792f
When the pop information is expanded and the user clicks pop again, I guess the user's purpose should be to close the current pop instead of popping it up again after closing.


Question: is it possible to have async helpers?

I extract the following from the docs.
Note that beyond inlining a utility function like in this example, you can require and use any piece of code in your project here and export it for Hygen to use.
module.exports = {
    helpers: {
        extended: s => s.toUpperCase()
    }
}

Seems like extended expected to have a return value, how could I create an async helper?

I will add a ticket for feature request, to support async helpers.


Integration tests: test that builds take a reasonable amount of time

From https://github.com/openshift/source-to-image/pull/648#discussion_r90856995
Tests that take too long (e.g. more than DefaultDockerTimeout), might indicate synchronization issues or other subtle bugs.
We should also introduce a test for a build that runs longer than the docker timeout, to ensure none of our timeout-based logic will fail a build when it is proceeding normally (but takes a long time to clone source, or commit the image, or some other step), from: https://github.com/openshift/source-to-image/pull/648#discussion_r90856704

i don't see us getting to this and if it were an issue i'd sort of expect to see it show up in the form of test flakes given all the builds we run as part of tests.


Remove coredns from istio-images-mirror

core-dns needs a multi-arch build and can't be included in the istio mirror images script

https://github.com/rancher/rancher/pull/27122 will be used for coredns and similar images in the future


Add support for primitive types

Add support for numeric, boolean and string types for use in input and output expressions. Specifically the types: string, bool, uint, uint8, uint16, uint32, uint64, int, int8, int16, int32, int64, float32, float64.
The types complex64 and complex128 are not supported by the Scan method of database/sql and I see no strong need to add them here. The type byte and rune are aliases for uint8 and int32 respectively and cannot be distinguished from the aliases using the reflect library so are not added here.
This change will allow queries such as SELECT name AS &string FROM ... and SELECT id AS &int FROM .... Previously these queries would have required a struct or map to extract the result into.
A limitation of being able to reference primitive types in I/O expressions is that each type can only be referenced once in the inputs and once in the outputs. For example the query SELECT name AS &string, address AS &string FROM ... is not valid. This is because when the user calls db.Query(...).Get(str1, str2) there is no way for SQLair to tell which column corrosponds to which variable. To get around this one can define new types that have the same underlying type.
For example:
type string1 string
type string2 string
stmt, err := sqlair.Prepare(
    "SELECT name AS &string1, address AS &string2 FROM ...",
    (string1)(""),
    (string2)(""),
)
var str1 string1
var str2 string2
err := db.Query(ctx, stmt).Get(str1, str2)

This PR also includes #98 which fixes a bug in detecting duplicate types.

From a conceptual perspective, I don't have any problem with the awkwardness around multiple base types. And this is because you really want to be using mappings that have more meaning to them.
Put a different way, you could write a function that is myfunc(bool, bool, bool), but that is usually a terrible function, because for an end user what is the difference between myfunc(true, true, false) and myfunc(true, true, true). You almost always would rather have:
is_open := true
check_size := true
verbose := false
myfunc(is_open, check_size, verbose)

Similarly here, having a SQL statement that just returns a 'string' makes it hard to be clear that you've lined them up correctly.
SELECT name, address FROM people;
db.Query().Get(&name, &address)

With only plain string types it would be:
SELECT name as &string, address as &string FROM people;

But both of these lines work without errors:
db.Query().Get(&name, &address)
db.Query().Get(&address, &name)

So it is clearly better to have
type address string
type name string
...
SELECT name as &name, address as &address

I think it makes sense to have a fast path for "I just have 1 string value to return", but as soon as there is confusion, it is better to be clear rather than rely on position to disambiguate.
In fact, I would probably document the type aliasing with something more realistic than 'string1' and 'string2' because it is fairly likely that people might actually think they should be using those integer variants.


Create "cleartext" backend for secrets

Secrets with GPG and especially automatic generation of secrets is very powerful.
However for some low-security setups (i.e. minikube or example folder) a user is required to have configured GPG and have the right key to decrypt secrets.
This forces the user to 2 choices:

reveal the secret in plaintext by overriding the target file
store a "shared" gpg key in the repository to allow for low security situations

The first option will force users to have alternative setups for demo/personal and prod environments
The second option will still force the user to setup gpg, and make more difficult to understand if an encrypted key is "unsecure" and auditing
I would like to encourage a healthy use of secrets that does not force users to diverge from the standard way for convenience.
My proposal is to create a new backend as an alternative to the gpg backend: a plaintext secret.
This enfoces a similar workflow but proving the benefit of a gpg-less setup.
Also, explicit use of this backend are easier to audit
example:
?{gpg:targets/prod/mysql/my_user_password}
?{plain:targets/example/mysql/my_user_password}
ultimately this can easily be templated with
?{${encryption_backend}:targets/${target_name}/mysql/my_user_password}

This is now possible with the ?{ref:file/path} backend.

As of KAP-5, this is now ?{base64:file/path}


Can't add multiple secrets to the same KMS string

I can add the first secret with no issues:

sls encrypt -n DB:USERNAME -v testUser

But when trying to add the second one:

sls encrypt -n DB:PASSWORD -v testPass

I get the following error:
UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 3): TypeError: Cannot read property 'decrypt' of undefined.
Thank you

@mzuniga84 Fixed in version 1.0.2. Thanks for the feedback!


Linking to particular slide index from external URL

Could a link be created such that slick would advance the slider to a particular index? Such as:
http://example.com/slide?index=8

Hi creativearc,
Your URL will actually trigger a server request. Within this request handler, make sure you set the "initialSlide" option in your output.
Example: when using .Net MVC, make sure the View you render will set the initialSlide option either within the .slick() initializer:
$('.slicker').slick({
  initialSlide: 8,
  <your_other_options>
});

Or - and that's what I prefer - to place it in the slick data attribute, so you don't have to place the variable within your javascript that you have probably separated in a .js or .min.js:
(html)

all my slides

I even took this one step further in one my .Net MVC projects and added "slick presenter" behaviour to my (partial) view models that should render a slick-slider. I can set options like 'centerMode', 'slidesToShow', 'centerPadding' and 'initialSlide' and then call its SlickDataAttribute() method from within the view that returns me a System.Web.HtmlString:
(html)

all my slides

Good luck

thanks @lhpderckx
https://github.com/kenwheeler/slick/issues/152#issuecomment-233948114
^^ this is a JS way to achieve it.

@simeydotme
You're right that you can use the slick function 'gotoSlide' for that, but for sake of clarity and good practice:

Handle query string parameters server side. Don't go parsing your url client-side, because maybe in about three months someone else or perhaps yourself changes the url to http://example.com/slide/8 and you wonder why it's no longer working.
If you wish to use 'gotoSlide' by means of an url, try to respond to the url hash #, like http://example.com/pagewithslides#slide4. You may also use in-page hyperlinks to select a particular slide like that. I just googled it and I believe there are ways to do that, but I don't have a readily available solution here.

Maybe that'd actually be a nice feature for slick, to incorporate #-behaviour so you can bookmark each slide and use hyperlinks and urls to display an initial slide by url.


Whether there are plans for scripting language development?

This project looks like a calculator, but if you introduce other operations such as IO (network, file, etc.) it is a scripting language! Because in fact there are already basic operators (+-*/), variables, function definitions (lambda) and calls, currently there may be a lack of logical judgments (if) and other operations.

Perhaps adding IO operations is unnecessary, but it is suggested that a logical operation function could be added, such as 3 > 2 results in true, true & false results in false, etc. Then it might be necessary to add an if-else or ternary operator x?y:z with a similar function for logical judgments, at least to allow others to write lambda functions with recursive exit calls.

It would definitely be nice to extend the scripting functionality of fend!
The only difficulty is finding the right balance between having an intuitive calculator-like syntax vs. having advanced scripting support, so while scripting features would be great to have I just want to be careful to preserve the ease-of-use of just using fend as a calculator. But yeah, I’ve definitely also been considering adding if statements and comparison operators eventually, since those would probably have the biggest benefit.


--

Hi!
Please, consider supporting '--'. Any stuff after '--' should go to arguments, even if it looks like an option
TIA,
--Vladimir

yup! we have an issue open for this, thanks man

doh! I thought this was commander.js haha... my bad


Tweak the editor log selection color to match the current editor theme

This overrides the default blue color.
For the record, this was already done in the editor help's RichTextLabel.

Thanks!

Cherry-picked for 3.2.2.


Bigquery: Allow optional function vectorization

Since bigquery batches up calls before sending them to cloud functions / cloud run, you could get better performance for certain async tasks by allowing the called function to deal with lists, rather than goblet using its for-loop.
I suspect there's many applications where the remote function is really just doing an API call - in these situations, letting the called function use asyncio.gather or whatnot can result in significant (10x) performance improvements.
This PR introduces a new vectorize_func argument for bqremotefunction. With it enabled, the called function should take a list for each argument, and also return a list.
It also includes the max_batching_rows argument, to fine-tune sizing of this vectorization

@AdeelK93 this is great and can see many use cases where this feature would provide a large benefit!

thanks @anovis - added an example - went with one using asyncio, to highlight that that's where the real performance gains can be achieved

Thank you!!


ha-bridge will not discover on certain networks, even though the origional ha-bridge will

Hi...
I hope you can help me out.  For clarity, I will refer to the BWS bride as the BWS bridge, and the HA bridge as the first HA-Bridge that this was based off of by Armzilla:
https://github.com/armzilla/amazon-echo-ha-bridge
I have 2 locations I used HA-Bridge at.
Location A has a full size origional Echo, and a dot v2.
Location B has a Echo dot v2.  It runs HA-Bridge on port 8081 because of a web server on port 80.  It runs version 0.2.1 of this old software .jar file because there is a bug in .4 where you cant discover devices if you change the port number.  I opened a case, but the author of this is MIA.
I've been wanting to switch to the BWS systems bridge for some time now, since it's maintained and has a whole lot of nice new features.  The other day, the HA-Bridge at location 2 threw a tantrum and refused to start, I don't remember why.  No problem, I wanted to switch to BWS bridge and this was my oppurtunity!  So I made a directory, started it up, followed the directions for configuring it, added 1 item, and did a discovery.  No joy with either the dot nor the web app from the computer.  (both worked fine with the old HA-bridge).  I decided ok, I'll set it up on a PI zero by itself and come back (it's not my primary residence).  I went home, set up a new PI zero at location A, installed BWS bridge + a test item, starts right up!  Happyness, so I configure the rest of the items, print me a nice case for the PI and take off for location B.  This is where my happyness ends.
I cannot get it to work.  In the meantime, the HA bridge started working again so at least I'm back in business there (go figure).  I cleaned out alexa, stopped the HA bridge, ran discovery and still nothing.  Here is what I tried:
-Changed the webserver port to 8081.  This makes the dot lock up half way through discovery, and also the web app fail.  So I went back to 80, because on this SBC, there is nothing else running.
-tried UPNP delay at 100,500,650,1000 as suggested in another post
-I made sure UPNP is not disabled on the router, but I'm not sure this is a point because HA bridge works fine.
-I dont have "use link button" turned on, but I did try your suggestion from the other post about using that.
-I tried the suggestion from the other post with discover, press reinitialize while it's discovering
-Changed webserver from all addresses (<IP_ADDRESS>) to specific address of the wifi interface(<IP_ADDRESS>)
-Wiped out the data directory, and started over.
At any time, I can start the HA-bridge service for the old one on the origional SBC and it rediscovers fine.  Leads me to believe it's not a problem with the dot nor the router.  But at the same time, the BWS bridge worked at location A???
bridge logs-both.txt
I put the startup and discovery logs from HA bridge, and the logs and discovery request from both bridges, marked with banners.
I've also copied the whole thing to my Ubuntu laptop, changed the IP's in the config file, started it and nothing.  removed the config file, restart, reconfigure, still nothing.
I've ran out of troubleshooting ideas.  Any help is appreciated.

Ok, I don't know if this means anything, but I made location A EXACTLY as location B, with just one Gen 2 Echo Dot.  It discovers fine.  This comes with a bit of a note as follows:
I took the time to see what bridge discovers what, and the results are interesting.  See table below:
_____________HA BRIDGE_________BWS BRIDGE
ECHO GEN 1______YES_______________YES *2
DOT GEN 2_______YES________________YES *2
SPOT____________NO________________YES *1
FIRE TV CUBE_____NO________________NO
FIRE TABLET 7____NO________________NO
*1 - SPOT discovers with BWS bridge, but only with 2 repeat attempts, one right after another
*2 - HA Bridge discovers this ALWAYS as a "Hue Light",  BWS bridge discovers it as a "Dimmable Light" if only 1 Echo is present on the network.  If 2 Echo's are present, it discovers as "Royal Phillips Electronics Smart Device".  Go Figure.
I was actually going to bet on DOT giving problems, but you see there is still differences.
All discovery was done with the web app.  With no Echo plugged in, of course nothing was detected because it's obvious it proxys out the discovery request to the local Echo to find devices.
My conclusion:
-The echo device still matters, but maybe not as much as we might think
-The BWS and HA bridge obviously have different discovery mechanisms.
-UPNP is not enabled on the router, and this should not matter nor is it a good practice to keep this protocol enabled.  The Echo requests are stateful.
I think my next step is WireShark. I will also take the Gen 2 Dot to location B over the weekend to see if there is discovery success, as multiple Echo's seem to make a difference with this bridge!  Maybe even Echo HW or FW levels within the device it'self...
I'd really like to see this BWS bridge working properly - it's such a slick piece of software and one heck of an upgrade.  But as it stands, I'm having trouble trusting it.  If I can provide anything else that may lead to a resolution, please feel free to ask.

So, I need some logfiles with upnp trace turned on so I can see what ip addresses are talking to each other.

Ok..Sorry I forgot to check back.  I'll give that a shot and let you know.
Best regards,

Not sure if it is related, but I have had trouble like this when the device running ha-bridge has more than one IP address in use. See https://github.com/bwssytems/ha-bridge/issues/980

Yes, that is in issue and will be resolved with the next release.

This will be fixed with #980


fix: global watcher may lead sharedTicker nil panic

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


Implement Tsallis versions for all probability estimators

What do you mean by this?

What do you mean by this?

We currently have entropy_renyi(x::Probabilities) and entropy_renyi(x, est), but only entropy_tsallis(x::Probabilities). The latter should also have the ...(x, est) signature, since it also operate on probabilities.

Oh okay, but that's a 3 lines of code addition, right?

Oh okay, but that's a 3 lines of code addition, right?

Yep, it is :D

This is solved by the new API in #101.


Make it possible to use a single key for mapped shortcuts (currently you need to use two keys for that)

Description of the new feature / enhancement
In the shortcut manager you can remap shortcuts, but you have to use at least two keys to trigger it.
I want to e.g. map undo/redo to single keys. This is not possible, because I have to use e.h. shift or alt in additon.
Scenario when this would be used?
To make complicated shortcuts easier to use, e.g. by mapping them to a single key. On many keyboards there are additional keys that could be used for that.
Supporting information
No response

Please use remap key for remap key to shortcut :)


feat: Make source code origin priority configurable

Make the source code origins configurable via the
ScannerJobConfiguration. Previsouly, the configuration was hardcoded to prefer SourceCodeOrigin.ARTIFACT over SourceCodeOrigin.VCS.

Typo in "Previsouly" -> "Previously". Maybe also "hardcoded" -> "hard-coded"?

There should be tests for the new functionality. At least the test for 'ScannerRunner` should be updated.

The way the parameter is used makes it difficult to test this without refactoring the scanner runner. How about we merge this as is to make the functionality available and I make a separate PR to improve the scanner tests in general?

There should be tests for the new functionality. At least the test for 'ScannerRunner` should be updated.

The way the parameter is used makes it difficult to test this without refactoring the scanner runner. How about we merge this as is to make the functionality available and I make a separate PR to improve the scanner tests in general?

Without a test, how can we be sure that the functionality is available?
Ok, I am going to approve, but I hope you keep your promise.


103 transit priority

Current coverage is 87.65% (diff: 97.14%)

Merging #125 into master will increase coverage by 1.01%

@@             master       #125   diff @@
==========================================
  Files            20         20
  Lines          2993       3005    +12
  Methods           0          0
  Messages          0          0
  Branches        434        439     +5
==========================================
+ Hits           2593       2634    +41
+ Misses          303        281    -22
+ Partials         97         90     -7

Powered by Codecov. Last update 361952f...d992c8c


tsconfig.json  set strict false,  vue props has a any type

Version
2.6.14
Reproduction link
https://codesandbox.io/s/wonderful-fast-bnksk
Steps to reproduce
test.vue
<template>

</template>

tsconfig.json
{
  "compilerOptions": {
    "strict": false
  }
}

What is expected?
hover  on  type props,  get (property) type: PropValidator<NameType[]>
What is actually happening?
hover  on  type props,  get (property) type: PropValidator<any[]>

value of strict effect typescript, wants to know why ?

See the note at https://v3.vuejs.org/guide/typescript-support.html#recommended-configuration

Note that you have to include strict: true (or at least noImplicitThis: true which is a part of strict flag) to leverage type checking of this in component methods otherwise it is always treated as any type.


Issue with Greek characters & searchNormalize

Hi,
i seem to face an issue with Greek characters and searchNormalize. In Greek we have accents as well, so, if i set searchNormalize to true no result at all is returned from the list. If i set searchNormalize to false, search results are returned, as long as accented vowels are entered with corresponding accent.
example
Ένα
Δύο
Τρία
Τέσσερα
if i set searchNormalize to true and search with "α" i get no results
if i set searchNormalize to false and search with term "α" i get (correctly)
Ένα
Τρία
Τέσσερα
but with searchNormalize to false, if i search with term Ε (no accent) i ll get only
Τέσσερα
and not Ένα (as well)
So searchNormalize set to true seems (in my case) to break completely the search

Hello @nikolasr200
I've run a couple of tests in order to change the function normalizeString to:
static normalizeString(text) {
const NON_WORD_REGEX = /[\u0300-\u036f]/g;
// Normalize the text to lowercase and remove accents
let normalizedText = text
    .toLowerCase()
    .normalize('NFD')
    .replace(NON_WORD_REGEX, '');

// Define a mapping of characters to remove accents for
const accentMappings = {
    'a': ['à', 'á', 'â', 'ã', 'ä', 'å'],
    'e': ['è', 'é', 'ê', 'ë','έ','ε'],
    'i': ['ì', 'í', 'î', 'ï'],
    'o': ['ò', 'ó', 'ô', 'õ', 'ö'],
    'u': ['ù', 'ú', 'û', 'ü'],
    'c': ['ç'],
    'g': ['ğ'],
    'n': ['ñ'],
};

// Replace accented characters with their non-accented equivalents
for (const baseChar in accentMappings) {
    const accentedChars = accentMappings[baseChar].join('');
    const regex = new RegExp(`[${accentedChars}]`, 'g');
    normalizedText = normalizedText.replace(regex, baseChar);
}
return normalizedText;   }

Could you run some tests on top of this in order to make sure it won't break the current use cases and fulfil the requirements you mentioned? I'm also worried about performance in these scenarios.
cc: @sa-si-dev

IMHO, it would be probably a good idea to allow to pass a searchCompareValues function, to be able to fully customize the search.
Thus one could implements fuzzy search, custom normalization, etc...

IMHO, it would be probably a good idea to allow to pass a searchCompareValues function, to be able to fully customize the search. Thus one could implements fuzzy search, custom normalization, etc...

I personally will see that as a new feature (even to be able to be backwards compatible) and here just try to include new use cases without further impacts.
But feel free to propose that via PR.

Hi @nikolasr200
Did you got the chance to test the alternatives I suggested?
I would lik more inputs before moving forward with a PR.
Cheers

Hi @gnbm, sorry i didn't have the time to do any tests so far. I believe your approach is to the right direction, and i ll try to test it asap.

I think it's more complex to handle all diacritics, and it would be better to not reinvent the wheel : for example, this package is well maintained and tested https://github.com/motss/normalize-diacritics
It's why I would prefer to be able to apply a custom normalization function

I think it's more complex to handle all diacritics, and it would be better to not reinvent the wheel : for example, this package is well maintained and tested https://github.com/motss/normalize-diacritics It's why I would prefer to be able to apply a custom normalization function

Feel free to add that to the library~via PR so that we can avoid breaking changes and @sa-si-dev might be able to review it


"packages pub" doesn't release flutter lock

When running flutter packages pub run build_runner watch to generate model classes and keep the generated code up to date with the change I make. I can't build or install or hot reload the project I'm working on.
When I pressed the run button in intellij to compile and install the app I get the following error:
Waiting for another flutter command to release the startup lock...

When I kill the build_runner process it starts compiling and installing the project.
If I start the build_runner watch when the project is already running on a device or simulator/emulator
I get the follow error when I make a change to the code:
Initializing hot reload...
Your application could not be compiled, because its dependencies could not be established.
The following Dart file:
  /Users/user/projects/project/lib/value_models/models.dart
...refers, in an import, to the following library:
  /Users/user/projects/project/lib/value_models/models.g.dart
Unfortunately, that library does not appear to exist on your file system.

Is there a way to start a separate process for the code generation so we can keep compiling and running our apps during development?

@aegis123 I have faced this problem too.
As a workaround, you could set FLUTTER_ROOT and then you can use flutter run and pub run build_runner watch(without flutter prefix) simultaneously

We need to release the lock before running pub.

@lfkdsk fixed this! Thanks!


Rename cn.yml to zh.yml

Most SC language pack code is zh

ok

Here is what  i posted on flarum
"I use a third wechat OAuth2.0
As wechat has not provide email, here using a random string as email(fake email),
Then the scene appeared
Changing your password requires a valid email to send the password reset link to.
Changing your email to a valid email requires knowing your password." looks like a dead loop
Is there any way to add a custom email dialog when login form none email OAUTH? Thanks"
你有没有好的方案，谢谢

sorry i was so busy these days, i know this issue, i will think over about it.


Download Aborted [System Error] - Unable to save to network drives

Since updating to the 3.x's I have been unable to save anything to any network folders (as i normally do). tested on both Windows 11 and Windows Server 2019.
Tested saving to folders with correct permissions. Saving locally works fine.
Both mapped drives and UNC do not work
relevant lines of log:
[2023-08-22 15:26:45,497][INFO] Download Failed
[2023-08-22 15:26:45,498][WARNING] Download failed for the following reason.
[2023-08-22 15:26:45,498][ERROR][BaseEngine.py:41] File System Error: Temporary Directory Error
This security ID may not be assigned as the owner of this object.
TwitchLink_Download_2023.08.22_15-26-45#ae22ce29-0982-47a9-8b2b-1ea8068f1e2e.log

Duplicate of #127

i also can't download network drive
normal mode is can browse network drive but, can't save.
run as administrator mode is can't browse.


chore: update to typings 1.x

Changes:
New typings with its breaking changes.
I removed the postinstall. A library shouldn't have it because that will force all consumers to have typings installed globally and that is a no-no, so from now one, manual install for us (this doesn't involve anything for the end user).
Please delete your typings folder and install them again.

I don't know much about this stuff but looks good to me on pronciple


test: add test for header stage two step download

Linked: https://github.com/paradigmxyz/reth/issues/418
This PR adds a test for HeaderStage where more than commit_threshold headers are downloaded, requiring a second call to HeaderStage::execute.

Hey! When opening up a PR that closes an issue, you can use special words to link the PR and the issue, which auto-closes the issue when it is merged. For example:
Closes #418 or fixes #418
It helps keep the issue tracker clean :smile: Thanks for taking this on!

Sorry for that! Will do!


Terraform trivy configuration excludes .trivyignore files, forcing repetitive ignore statements

Describe the bug
The code in the pre commit config excludes trivyignore files:
- id: terraform_trivy
  name: Terraform validate with trivy
  description: Static analysis of Terraform templates to spot potential security issues.
  require_serial: true
  entry: hooks/terraform_trivy.sh
  files: \.tf(vars)?$
  language: script

How can we reproduce it?
Add a trivyignore file and try to use the hook.
Environment information
repos:
  - repo: https://github.com/antonbabenko/pre-commit-terraform
    rev: v1.88.1 # Get the latest from: https://github.com/antonbabenko/pre-commit-terraform/releases

currently this can be overriden with
files: '.tf(vars)?$|.trivyignore$'
but it would be nice if it didn't exclude it as the standard

@ramongalate Would you please elaborate on what "forcing repetitive ignore statements" means and what makes you think pre-commit-terraform "excludes trivyignore files"?

@yermulnik when running a trivy command usually there are issues that give errors that you can ignore .
in cases where these issues happen several times, you can use a .trivyignore file to state the code to be ignore globally, instead of writing an ignore statement for every case.
since you specified to use only files that match files: \.tf(vars)?$, the global trivyignore file does not get included, like you would with pass_filenames: false or a more permissive regex.

since you specified to use only files that match files: \.tf(vars)?$, the global trivyignore file does not get included

The file: parameter is not about which files are passed to trivy hook, but about changes to which files trigger trivy hook run (files location also infers the directory where trivy is run). If .trivyignore file, that you want trivy to take into account, is located in any of parent to TF-file(s) directory, then trivy obviously will not include it. In such case one option would be to configure hook to run an all files no matter which file(s) were chenged.

I have the same issue:
trivy config . => .trivyignore is considered
pre-commit run --all-files => .trivyignore is NOT considered
@yermulnik what does it mean "one option would be to configure hook to run an all files no matter which file(s) were chenged."? I already sopecify --all-files in pre-commit run, what should I add to the hook config?
With terraform_tfsec I exclude checks using the args:
      - id: terraform_tfsec
        args:
          - "--args=-e aws-ssm-secret-use-customer-key,\
            aws-ecr-repository-customer-key,\
            aws-dynamodb-table-customer-key"

How does it work with terraform_trivy? I don't finy any hint in the documentation.

If .trivyignore is just one file in repo root (or in one place in the repo) and should be used everywhere, try
 - --args=--config-file=__GIT_WORKING_DIR__/.trivyignore

@MaxymVlasov It works! Many thanks!


Skip anonymous classes, fixes #1153

Review @laughedelic

@olafurpg thanks for keeping me in the loop, but i'm not sure how I could be helpful here. To be honest I have almost no idea what you have changed in this PR 😅
Can I help testing it or something else? I'd like to get a better than no at all understanding of how Scalameta works in general, but so far I didn't have enough time (and courage) to dive into the code..

No worries @laughedelic there's a lot going on in Scalameta and it took me a long time to understand how the pieces fit together 😄
new Foo {} gets desugared by the compiler into { class $anon extends Foo; new $anon} and the go to definition bug was caused by the symbol of Foo getting resolved to $anon (which doesn't have a position in the source) when it should resolve to Foo in the extends Foo part. This commit just adds a guard that we don't resolve symbols to $anon classes.

@olafurpg Thanks for the explanation! It makes sense to me now.


Add a LICENSE file

Even though the “readme.md” file contains a statement that says “Distributed under the MIT License”, there is no text of the license or a link to that text, which could probably limit some people on the use of the project.
I'm not a lawyer to provide legal advice, but ideally a file with the text of the license should be included instead of a link, the file would contain the name of the author and also is easier to access (cause a website could have downtimes).

@schemetastic Thank you for you issue! That's what I've forgot to do!

You're welcome, maybe I should keep an eye on this project 😉


chat demo sam directions do not work for launching

Demo
Directions here do not work: https://github.com/aws-samples/amazon-chime-sdk/tree/main/apps/chat#using-aws-sam
Describe the bug
The s3 bucket name is already in use.  In addition once launched (if random name provided) you can't delete the stack with out hand holding.
To Reproduce
Steps to reproduce the behavior:

Follow directions here: https://github.com/aws-samples/amazon-chime-sdk/tree/main/apps/chat#using-aws-sam.
See failures
Override values here: https://github.com/aws-samples/amazon-chime-sdk/blob/main/apps/chat/src/backend/serverless/samconfig.toml#L10
Try to delete stack, it doesn't work

Expected behavior
create and delete stack happens
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

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

Additional context
Add any other context about the problem here.

The SAM change (https://github.com/aws-samples/amazon-chime-sdk/pull/200/files) also broke credential exchange service and likely other APIs as browsers don't allow authenticated calls (at least on localhost) to * anymore:

some fixs are in https://github.com/aws-samples/amazon-chime-sdk/pull/226


websocket stream - error 403

Problem Description
websocket stream isnt passed corectly
Steps to reproduce the behavior:
I'am checking IOT device websocket data stream to Cloud and get 403 error doing this mitmproxy. Steps to reproduce the behavior: IOT application has 3 pem files: cacert.pem, newcert.pem, newkey.pem
launch mitmproxy --mode transparent --showhost --ssl-insecure --cert *=/tmp/ssl/cert.pem
(cert.pem has both newcert.pem and newkey.pem inside)
error:
Server Error
403 - Forbidden: Access is denied.
You do not have permission to view this directory or page using the credentials that you supplied.
Seems it wants to accees like simple webpage instead passing IOT application websocket traffic.....
System Information
System Information Mitmproxy: 5.0.1 Python: 3.6.8 OpenSSL: OpenSSL 1.1.1 11 Sep 2018 Platform: Linux-4.18.0-25-generic-x86_64-with-Ubuntu-18.10-cosmic

Can you provide a minimal, reproducible example of the issues you are encountering? "It doesn't work" isn't specific enough to fix it.


Update windows_data_json.md

link update

@MancunianBandit : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

#sign-off


Add to Yeoman-x-VSCode

This pull request is centered around VSCode's extension building documentation.
Reasons to make this change
This gitignore file will contain all necessary files to ignore to increase the productivity of any project while using git to build an extension
documentation to the vscode extension building will be linked here:
https://code.visualstudio.com/api/get-started/your-first-extension
(this is my first pull request sorry if i did something wrong or something)

could also be added to the file Yeoman.gitignore


Feature Request: Windows Support

Since there's growing support for Windows in Kubernetes and Docker community it'd be nice to get a Windows build for the node-problem-detector. This has been discussed on sig-windows before. I'd like to start a discussion here on what's necessary.
I've been looking on what's necessary to bring multi-arch building to this project and what dependency detanglement is necessary to build Windows binaries. It's possible with a few patches and dependency upgrades to build Windows binaries.
Multi-arch building would also unlock ARM support requested from https://github.com/kubernetes/node-problem-detector/issues/135.
Design Document: https://docs.google.com/document/d/1eiK6KAp_TFR0PgBMu2WCf49fMZcg-HHnBHMc9fALquU/edit

/remove-lifecycle stale

Design Doc: https://docs.google.com/document/d/1eiK6KAp_TFR0PgBMu2WCf49fMZcg-HHnBHMc9fALquU

/remove-lifecycle stale

/reopen

/reopen
need to update the readme: https://github.com/kubernetes/node-problem-detector#windows

@jeremyje - Is this work planned?

/reopen
need to update the readme: https://github.com/kubernetes/node-problem-detector#windows

/remove-lifecycle rotten