IPP System Service Test Suite

Develop an ipptool test suite for PWG 5100.22-2019: IPP System Service v1.0.
Specific tests:

[ ] Allocate-Printer-Resources (icons, printer ICC profiles, strings files, template job attributes)
[ ] Cancel-Resource
[ ] Cancel-Subscription for Resource subscription
[ ] Cancel-Subscription for System subscription
[ ] Create-Job with a template-job resource
[ ] Create-Printer with a template-printer resource
[ ] Create-Resource for static-icc-profile resource
[ ] Create-Resource for static-image resource
[ ] Create-Resource for static-strings resource
[ ] Create-Resource for template- resource
[ ] Create-Resource for static-job resource
[ ] Create-Resource for static-printer resource
[ ] Create-Resource-Subscriptions
[ ] Create-System-Subscriptions
[ ] Deallocate-Printer-Resources
[ ] Delete-Printer
[ ] Disable-All-Printers
[ ] Enable-All-Printers
[ ] Get-Notifications for Resource subscription
[ ] Get-Notifications for System subscription
[ ] Get-Printer-Attributes for default printer
[ ] Get-Printer-Resources
[ ] Get-Printers
[ ] Get-Resource-Attributes for static-icc-profiles resource
[ ] Get-Resource-Attributes for static-image resource
[ ] Get-Resource-Attributes for static-strings resource
[ ] Get-Resource-Attributes for template-job resource
[ ] Get-Resource-Attributes for template-printer resource
[ ] Get-Resource-Attributes with requested-attributes='all'
[ ] Get-Resource-Attributes with requested-attributes='resource-description'
[ ] Get-Resource-Attributes with requested-attributes='resource-status'
[ ] Get-Resource-Attributes with requested-attributes='resource-description','resource-status'
[ ] Get-Resource-Attributes with requested-attributes=list of attributes
[ ] Get-Resources
[ ] Get-Resources with requested-attributes='all'
[ ] Get-Resources with requested-attributes='resource-description'
[ ] Get-Resources with requested-attributes='resource-status'
[ ] Get-Resources with requested-attributes=list of attributes
[ ] Get-Subscription-Attributes for Resource subscription
[ ] Get-Subscription-Attributes for System subscription
[ ] Get-Subscriptions for Resource
[ ] Get-Subscriptions for System
[ ] Get-System-Attributes with no requested-attributes
[ ] Get-System-Attributes with requested-attributes='all'
[ ] Get-System-Attributes with requested-attributes='system-description'
[ ] Get-System-Attributes with requested-attributes='system-status'
[ ] Get-System-Attributes with requested-attributes='system-description','system-status'
[ ] Get-System-Attributes with requested-attributes=list of attributes
[ ] Get-System-Supported-Values
[ ] Install-Resource for static-icc-profile resource
[ ] Install-Resource for static-image resource
[ ] Install-Resource for static-strings resource
[ ] Install-Resource for template-job resource
[ ] Install-Resource for template-printer resource
[ ] Pause-All-Printers
[ ] Pause-All-Printers-After-Current-Job
[ ] Print-Job with template-job resource
[ ] Print-URI with template-job resource
[ ] Register-Output-Device (if supported)
[ ] Restart-One-Printer
[ ] Restart-System
[ ] Renew-Subscription with System subscription
[ ] Resume-All-Printers
[ ] Send-Resource-Data
[ ] Set-Resource-Attributes
[ ] Set-System-Attributes
[ ] Shutdown-All-Printers
[ ] Shutdown-One-Printer
[ ] Startup-All-Printers
[ ] Startup-One-Printer

This will be a VERY LARGE test file, so feel free to split into logical parts and then have a single "top level" test file that includes the parts.

Initial attributes/values tests are checked in:
[master bc88168] Initial 5100.22 tests (Issue #176)

All done!


[Bug] Viewing profiles as Guest

An error is thrown:
ErrorException in profile_basic.twig line 6:

 An exception has been thrown during the rendering of a template ("Argument 1 passed to
MyBB\Core\Database\Repositories\Eloquent\UserProfileFieldRepository::hasForProfileField() must
 be an instance of MyBB\Core\Database\Models\User, null given, called in C:\xampp\htdocs\mybbv2
\app\Presenters\ProfileField.php on line 135 and defined") in "user.profile_basic" at line 6.

If the user logs in, he can view them just fine.

Again, looks like a lack of permission checking.

I think I see what's wrong. We're getting the currently authenticated user (null for guest) from the guard and trying to fetch its profile field repository.

Yes, the past version of the auth package returned a default User for guests. We need to fix the conditions elsewhere to handle the new default case (null).

On 16 Jun 2016, at 21:12, Josh Harmon<EMAIL_ADDRESS>wrote:
I think I see what's wrong. We're getting the currently authenticated user (null for guest) from the guard and trying to fetch its profile field repository.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.


Sanitize IP zookeeper/enable_and_wait.py

Description
This PR fixes a minor security issue that can lead to os code injection.
Verification
The function was tested locally with various valid and invalid inputs and it produced the appropriate results.

PS: Can the maintainers please reserve a CVE for this is they deem the issue fit?

Hey @robbederks fixed the bug and even passed the test cases 😀
Also, can you please look into #24015? I am a part of the said community of security researchers and the SECURITY.md would be really helpful 😄

Hey @robbederks fixed the bug and even passed the test cases grinning
Also, can you please look into #24015? I am a part of the said community of security researchers and the SECURITY.md would be really helpful smile

Feel free to email me or robbe for now (first_name@comma.ai).

With regards to #24015, it was to share the contents of this vulnerability report, i.e. alluding to code injection in enable_and_wait.py.
The report can be found here (submitted by @whokilleddb):
https://www.huntr.dev/bounties/8c089464-637c-49a6-9839-0929740f605c
It is currently private and is only visible to maintainers with repository write permissions. Let me know if you would like me to make it publicly visible 👍

Furthermore, we can arrange a CVE for you (@robbederks @adeebshihadeh) if required, as the vulnerability was initially reported via huntr.dev 👍

It doesn't make sense to open a CVE for this issue, and you probably damage your credibility as a security researcher with your approach.  It might be a good idea to put some effort into better understanding the software you are looking at before popping the CVE question.  Join our discord server if you care to learn more.


Deprecate None return value on Reddit.user.me()

Back in issue #962 a choice of whether to raise a better exception or return None was put forward. I think the wrong decision was made.
See my reasoning in #963.

Very well. I put a warning in instead for now.

@Pyprohly can you rebase this?

I'm going to fix this up and get it in.

Closing in favor of #1684.


Incorrect Information for "Show welcome screen on sign in"

"Show welcome screen on sign in" has the description from "Show dashboard cards in expanded state" which is incorrect!

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

ID: d941b293-2873-2c2c-6f44-9a4c28aa98e5
Version Independent ID: e704ed8d-7769-b9ff-7028-d684044788c0
Content: Manage behavior settings - Power Platform
Content Source: power-platform/admin/settings-behavior.md
Service: power-platform
GitHub Login: @jimholtz
Microsoft Alias: jimholtz

@Marksatx23
Thanks for bringing this to our attention. I'll remove the incorrect text for now and replace the replace with text when I hear back from the product team.


Add dependabot with monthly schedule

Codecov Report

Merging #39 (de67d6c) into master (60186bd) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head de67d6c differs from pull request most recent head 00a005c. Consider uploading reports for the commit 00a005c to get more accurate results

@@           Coverage Diff           @@
##           master      #39   +/-   ##
=======================================
  Coverage   86.20%   86.20%
=======================================
  Files           7        7
  Lines         145      145
=======================================
  Hits          125      125
  Misses         20       20

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 60186bd...00a005c. Read the comment docs.


Compilation failing on macOS

When trying to compile using make build on macOS, the Rust component compiles successfully however the following fails.
make -C lucet-builtins
cc --std=gnu99 -Ofast -Wall -Werror -march=native -fPIC -I../lucet-runtime/include -c src/memcpy.c -o build/memcpy.o
In file included from src/memcpy.c:1:
In file included from src/common.h:8:
In file included from ../lucet-runtime/include/lucet.h:9:
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk/usr/include/ucontext.h:43:2: error: The deprecated ucontext routines require _XOPEN_SOURCE to be defined
#error The deprecated ucontext routines require _XOPEN_SOURCE to be defined
 ^
1 error generated.
make[1]: *** [build/memcpy.o] Error 1
make: *** [build] Error 2

macOS 10.14 Mojave with
clang --version
Apple LLVM version 10.0.1 (clang-1<IP_ADDRESS>)
Target: x86_64-apple-darwin18.5.0
Thread model: posix
InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

This will be fixed as soon as #138 lands. If you have time, could you check out that branch and see that its fixed there?

Using that branches looks like it works
make -C lucet-builtins
cc --std=gnu99 -Ofast -Wall -Werror -march=native -fPIC -I../lucet-runtime/include -c src/memcpy.c -o build/memcpy.o
cc --std=gnu99 -Ofast -Wall -Werror -march=native -fPIC -I../lucet-runtime/include -c src/memmove.c -o build/memmove.o
cc --std=gnu99 -Ofast -Wall -Werror -march=native -fPIC -I../lucet-runtime/include -c src/strcasecmp.c -o build/strcasecmp.o
cc --std=gnu99 -Ofast -Wall -Werror -march=native -fPIC -I../lucet-runtime/include -c src/strchr.c -o build/strchr.o
cc --std=gnu99 -Ofast -Wall -Werror -march=native -fPIC -I../lucet-runtime/include -c src/strcmp.c -o build/strcmp.o
cc --std=gnu99 -Ofast -Wall -Werror -march=native -fPIC -I../lucet-runtime/include -c src/strlen.c -o build/strlen.o
# -U is not supported by the GNU linker. Retry without this option if the first command fails.
cc -Wl,-U,_lucet_vmctx_current_memory -Wl,-U,_lucet_vmctx_get_heap -shared build/memcpy.o build/memmove.o build/strcasecmp.o build/strchr.o build/strcmp.o build/strlen.o -o build/libbuiltins.so 2> /dev/null || \
        cc -shared build/memcpy.o build/memmove.o build/strcasecmp.o build/strchr.o build/strcmp.o build/strlen.o -o build/libbuiltins.so

make install or sudo helpers/install.sh generates the following error.
readlink: illegal option -- e
usage: readlink [-n] [file ...]
Unable to find the current script base directory

Hi,
And thanks for your feedback!
The macOS port (and actually, making Lucet work outside the Docker environment) is still a work in progress.
make install should not be used outside this environment, and there is more than just fixing the readlink issue to have it work.
For example setting LD_LIBRARY_PATH doesn't do anything on macOS.
I'll eventually make a Homebrew tap to properly install Lucet of macOS.


Spell check on article

systme -> system

Hey @ali-ahsan-ali , thank you for your PR! We're rendering the HTML based on markdown. Could you make the proposed changes inside the markdown file in the same directory? The reason we commit the HTML artifacts is because those are used by github pages

I've applied the fix in #45 as well now

Thanks for bringing it up and the PR :)

Nice, sorry I didn't follow through with this


Gradle fails config if a publication repo has colon in the name

Expected Behavior
Gradle should not fail or fail with helpful message.
Current Behavior
Gradle fails with unhelpful error message.
Context
I am setting up an enterprise build and we are managing repo managers centrally, allowing each project to configure repository by a pair of managerId and repoId.
Later in the configuration, we look for the best-matching credentials in hierarchical manner that allows to specify different credentials for release/integration, as well as for each project or each manager. Ideally, we would have had ext properties on the repo, but right now we tunnel this information with structured names. The initial separator was colon, which lead to the discovery of this bug.
Fixing Gradle to strip the colon when it creates the task, or not allow colons in the repo names are both acceptable solutions. The current error is confusing to build users.
Steps to Reproduce (for bugs)
If we configure a project as follows:
apply plugin: 'java-library-distribution'
apply plugin: 'maven-publish'
publishing.repositories.maven {
            name = "bro:ken"
            url "$buildDir/repo"
}

The build would fail with:
Could not determine the dependencies of task ':publish'.
> Task with path 'publishMavenJavaPublicationToBro:kenRepository' not found in root project 'foobar'.

That is, Gradle would search for project publishMavenJavaPublicationToBro and task kenRepository
Your Environment
Gradle 4.7

Thanks for reporting this issue! I think not allowing colons with a good error message is the way to go. Publication names are probably affected as well.


Fix task failure when multiple attempts are run

Fixes https://github.com/kestra-io/plugin-airbyte/issues/33
Currently if Airbyte sync fails and ends up with status INCOMPLETE, flow will return failed even though Airbyte is triggering a new attempt which could succeed.
Even worse, duration calculation can end up with negative value and make the plugin fails.
State machine of Airbyte Job Status is available here.

In order to fix,

removed INCOMPLETE status from the list of Ending ones.
removed duration computation to make sure no error will be thrown. Rather display the number of attempts.
Warn user when sync is running a new attempt

Also :

Allowed extra properties in payload like enabledStreams which is returned in Airbyte 0.50.13

Thanks a lot!


Remove unnecessary qubit property conversions

Summary
The apply_prefix method here in BackendProperties is already converting to seconds and hz
Details and comments
Fixes #

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

-4 of 4 (0.0%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-2.8%) to 59.628%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

qiskit_ibm_runtime/utils/backend_converter.py
0
4
0.0%

Files with Coverage Reduction
New Missed Lines
%

qiskit_ibm_runtime/utils/backend_converter.py
1
14.61%

Totals

Change from base Build<PHONE_NUMBER>:
-2.8%

Covered Lines:
2756

Relevant Lines:
4622

💛  - Coveralls


Show liger-kernel and rocm version in env_report

🚀 The feature, motivation and pitch
https://github.com/linkedin/Liger-Kernel/blob/d58510f79d0c13f72cc38e62707a5a5fe500b4b3/src/liger_kernel/env_report.py#L5
Add liger-kernel and rocm version
Alternatives
No response
Additional context
No response

https://github.com/linkedin/Liger-Kernel/pull/456


Combine compound child components with compound parent component

Motivation
The current README shows that related components are not part of the parent export:
import { createRoot } from "react-dom/client";
import {
  Button,
  Dialog,
  DialogHeading,
  DialogDescription,
  useDialogState,
} from "ariakit";

function App() {
  const dialog = useDialogState();
  return (
    <>
      <Button onClick={dialog.toggle}>Open dialog</Button>
      <Dialog state={dialog}>
        <DialogHeading>Welcome</DialogHeading>
        <DialogDescription>Welcome to Reakit!</DialogDescription>
      </Dialog>
    </>
  );
}

createRoot(document.getElementById("root")).render(<App />);

It would be nice to import just the parent component of a compound instead of importing the parent component + the child components of that compound.
Usage example
import { createRoot } from "react-dom/client";
import {
  Button,
  Dialog,
  useDialogState,
} from "ariakit";

function App() {
  const dialog = useDialogState();
  return (
    <>
      <Button onClick={dialog.toggle}>Open dialog</Button>
      <Dialog state={dialog}>
        <Dialog.Heading>Welcome</Dialog.Heading>
        <Dialog.Description>Welcome to Reakit!</Dialog.Description>
      </Dialog>
    </>
  );
}

createRoot(document.getElementById("root")).render(<App />);

Requirements
When importing the parent component of a compound, all child components of that parent should be part of that imported object.
Workaround
Currently no workaround as we are forced to import the desired components of a compound instead of just the parent.
Possible implementations
No response

See https://github.com/ariakit/ariakit/issues/894#issuecomment-894523032


Proposing Doxygen Docs for NS3-GUI-HELPER

Example Docs of How-much-of-NEWS-are-you
it requires basic installation steps, refer screenshot below

official site - https://www.doxygen.nl/ , since its an automated code documentation, suits best for open source projects.
Issue Tags - enhancement

Thank you for showing off with this tool! Hopefully it will add great benefit to this project!

Yeah, I totally agree with you. Other than doxygen, what are your thoughts on using

Javadoc Tool
NaturalDocs
Sphinx
DocFx
ROBODoc
Or some markdown based tools

ns3's doxygen documentation adoption is good since they are also using it - https://www.nsnam.org/doxygen/ making this software follow a standardized docs.

Sure then, we'll match with the NS3.


location.inventory_levels

Hello,
Firstly, thanks for you work ;)
We have a problem when retrieve location and get inventory_levels foreach location.
ActiveResource::ForbiddenAccess (Failed.  Response code = 403.  Response message = Forbidden.)
gems/shopify_api-4.11.0/lib/shopify_api/resources/location.rb:5:in `inventory_levels'
Our scope config :
config.scope = "read_orders, read_products, read_fulfillments, write_fulfillments"
Have you got the same problem ? How can we fix it
All the best,
ToM

Hey Tom,
I believe you'll need to add the OAuth scope for read_inventory.
At some point in the future, I believe that all apps with read_products will inherit that scope but I'm not sure if that work has been completed yet.
This feature is only intended to be used as a beta as of right now.
Cheers.

Hello,
Thanks for your reply.
With read_inventory scope it works fine 👍
We implement this because we read inventory_quantity in productVariant Deprecated on this link -->  https://help.shopify.com/api/reference/product_variant
So we must get inventory_quantity by inventory_level API.
What do you think about this.
All the best,
ToM

Hey Tom,
You're right – inventory_quantity will be removed from the Variant model and going forward, you must determine inventory quantity using the InventoryLevel API.
Hope this helps.


Secretnav and Anchor Tags

When using Secretnav with anchor points on the same page. The page jumps back up to the top.

Hi @ChandlerVS,
Thanks for the GIF, that makes it very clear!
The plugin is programmed to scroll back to where the menu was opened. When the perspective on the content is changed, the scroll moves to the top (I don't know why), so the plugin reverses this behavior when you close the menu.
A quick solution would be to modify line 112 to be window.docscroll = self.scrollY(); and line 147 to be document.documentElement.scrollTop = window.docscroll;. Then, add a click event on your anchors to update that variable as follows:
// Not tested
$(".anchor").on("click", function(e){
    var anchor = $(this).attr("href");
    window.docscroll = $("#" + anchor).offset().top;
});

If you have the time, you could also modify the plugin and propose a pull request :)


Add load function

I have added a load function for Chart and StyleManager. The function basically can load values of multiple variables from a single string. The load function will call the setter function for a variable (e.g. setVariable(String sValue)) if it exists or otherwise use java reflection to set the value.
Here is an example:
chart.load("xAxisTitle=loaded x title SIN(width)+height:#SIN($width$)+$height$#;yAxisTitle=loaded y title;");

$xxx$ can be used to get variable values or get function returns, #xxxxx# can calculate expression.
I have written a small demo called LoadDemo in xchart-demo\src\main\java\com\xeiam\xchart\demo.
I am not sure if you like it. It might be able to help you write less lines of settings. Also the variables and expressions in load function are checked, and it will raise exceptions if there problems in the settings.

@mleoking The following project might be what you were trying to accomplish:
https://github.com/cardillo/joinery
, or at least in the right direction. I've decided to focus XChart strictly on plotting and not data management or manipulating.


[Feature] Outro Clip

Hey, it would be great, if some kind of Outro-clip could be added to the video (either self-made clips or pre-generated ones), so the video just doesnt stop right away, but maybe it shows a short clip with something like "like the video and subscribe/follow" or something

Make sense, I think we have two options to do this:

For the long term, we can provide the capabilities for editing the final generated videos;
Currently, we can add an extra parameter "outroClipUrl" to the VideoParams for pre-generated video, and add some logic to deal with it in the "## Combining Video" part.

What do you think? @harry0703

That's a great suggestion and very flexible, considering adding it.


[Fix] Milee urdf origin and scale

Status
DEVELOPMENT
Description
The Milee urdf model in current develop branch has wrong parameters, so I fixed the origin and scale.
Steps to Test or Reproduce

Set Autoware/ros/src/.config/model/milee.urdf to Vehicle Model path in Setup tab.
Launch Vehicle Model
You can see correct Milee 3D model on Rviz.

@yn-mrse Thanks! Just as you said, this model has a little rough shape. Let's continue to discuss details at #1688 .


Improve basic usage example.

Can discuss here more as to how.
One simple way would be to add explanation how given a stealthMetaAddress we can create addresses for that user without their involvement.
Also fill in all 0x... fillers with actual an actual stealthMetaAddress.

Can discuss here more as to how.
One simple way would be to add explanation how given a stealthMetaAddress we can create addresses for that user without their involvement.
Also fill in all 0x... fillers with actual an actual stealthMetaAddress.

Will do on showing an actual stealth meta-address.
Re: basic usage:
Was thinking basic usage would show a simple function import and use.
And the meat of the example usage will be under "Guides", where there will be a walkthrough on how to use all of the functions in a systematic way.
I.E: the guide will start by generating a stealth meta address randomly, but talk bout the limitations quickly, then show how to use a message sig to get a stealth meta address. Then show how to generate a stealth address, and the process to announce the addie so that a recipient can listen for it (getAnnouncementsForUser) and what that means.
Still thinking bout how to keep the guide page tidy/impactful.
Can chat through it more too.


Status Count

Add a status count to each of the status labels "approved, pending, etc.."

Tasks

[ ]  Add api /api/ner/status in backend to return labeling status progress
[ ] Add labeling progress component in frontend to show current labeling progress status


Stack overflow on OS X 10.10.5 (mid-2014 macbook pro)

When building and running the noise example, the stack overflows:
$ cargo run --example noise
    Updating registry `https://github.com/rust-lang/crates.io-index`
 Downloading gcc v0.3.21
   Compiling winapi-build v0.1.1
   Compiling libc v0.2.4
   Compiling winapi v0.2.5
   Compiling gcc v0.3.21
   Compiling kernel32-sys v0.2.1
   Compiling minifb v0.2.3 (file:///Users/yupferris/dev/projects/rust_minifb)
   Compiling time v0.1.34
     Running `target/debug/examples/noise`

thread '<main>' has overflowed its stackAn unknown error occurred

To learn more, run the command again with --verbose.

This has been happening for a couple months since I first tried the lib on os x, but I didn't report it as I thought you'd be working on stuff further and it might be known.
This happens in both debug and release builds.

Found the problem.
In the example, buffer will be placed on the stack, which in my case isn't large enough. The easiest way to fix this is to Box it and use rust's box syntax to make sure the buffer is allocated on the heap, but the box syntax is experimental and only available on the nightly. As far as I know there's no other way to solve this with the current stable feature set.
In any case, this commit on my fork shows the working (albeit only on nightly) box solution.

Perhaps a temporary solution is to provide a second noise example utilizing box for cases like mine.

Well.. I can support that you can send in a &Vec which is heap allocated and not experimental.

Well now that you mention Vec, since you already take an array, this works:
let mut buffer: Vec<u32> = vec![0; WIDTH * HEIGHT];

...

window.update(&*buffer);

Ah right. I can update the example with that.

Actually, since Vec implements AsRef directly, you don't seem to need the * either; just changing buffer to a Vec seems to be sufficient.

Cool. Will do.

(I think I'm wrong about AsRef being the secret sauce here, but it works nonetheless :) )

Ok :) I will fix this when I get back home later today.


Some improvements about Docker

These some improvements about Docker, including:

Update to run with JRE 11 by default
Update to use gcr.io/distroless/java11-debian11 image as base by default. This image is currently supported image for Java 11.
Enable docker buildkit cache to speed up building
Download bash-static to the image so that scripts that require bash can be executed(Fixes #13057 )
bump builder image from 3.8.4-jdk-11-slim to the latest 3.8.6-jdk-11-slim
switch busybox from amd64/busybox:1.30.0-glibc to busybox:1.35.0-glibc
Support to build arm64-based image

This PR has:

[X] been self-reviewed.

[ ] using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)

[ ] added documentation for new or modified features or behaviors.
[ ] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
[ ] added or updated version, license, or notice information in licenses.yaml
[ ] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[ ] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
[ ] added integration tests.
[X] been tested in a test Druid cluster.

After switching to JRE 11, we need to use run-java in the druid.sh to start Druid services.
Making as draft temporarily till this change is done.

I have built and run the image on my intel MacBook and M1 MacBook, both are OK.

@gianm Do you have any comments on these changes? If no, I will merge it once the CI finishes.

@FrankChen021 you can go ahead and merge this, I don't think there is anything controversial about it. Adding bash-static is  already backported as part of #13063. The biggest change is the switch to JDK 11, so we should probably mention that fact in the PR description and also make sure we add it to the release notes.

Thank you @xvrl very much for you helpful review.


Composer installation issue

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Installation request for deployer/deployer ^3.0 -> satisfiable by deployer/deployer[v3.0.0].
    - deployer/deployer v3.0.0 requires phpseclib/phpseclib dev-master#2c96af214bf1b5e29b707249108504b4e0041a21 -> no matching package found.

Either switch the require to dev-master or the packages version tag.

Please try with this composer.json file:
{
    "require": {
        "php": ">=5.4.0",
        "phpseclib/phpseclib": "dev-master#2c96af214bf1b5e29b707249108504b4e0041a21",
        "deployer/deployer": "~3.0.0"
    },
}

And run composer clear-cache command before composer install command.
Good luck !

This will gone away, when phpseclib do release. Or i will implement ssh in php myself :fist:

It worked with what was said by @oanhnn

I have the same issue, but @oanhnn solutin don't work for me.
In composer.json file:
        "phpseclib/phpseclib": "dev-master#2c96af214bf1b5e29b707249108504b4e0041a21",
        "deployer/deployer": "~3.0.0"

Problem:
  Problem 1
    - deployer/deployer v3.0.0 requires elfet/pure ~1.1 -> satisfiable by elfet/pure[v1.1.0].
    - deployer/deployer v3.0.1 requires elfet/pure ~1.1 -> satisfiable by elfet/pure[v1.1.0].
    - deployer/deployer v3.0.2 requires elfet/pure ~1.1 -> satisfiable by elfet/pure[v1.1.0].
    - Conclusion: don't install elfet/pure v1.1.0
    - Installation request for deployer/deployer ~3.0.0 -> satisfiable by deployer/deployer[v3.0.0, v3.0.1, v3.0.2].

Without phpseclib/phpseclib i have:
Problem 1
    - The requested package phpseclib/phpseclib could not be found in any version, there may be a typo in the package name.
  Problem 2
    - deployer/deployer v3.0.2 requires phpseclib/phpseclib dev-master#2c96af214bf1b5e29b707249108504b4e0041a21 -> no matching package found.
    - deployer/deployer v3.0.1 requires phpseclib/phpseclib dev-master#2c96af214bf1b5e29b707249108504b4e0041a21 -> no matching package found.
    - deployer/deployer v3.0.0 requires phpseclib/phpseclib dev-master#2c96af214bf1b5e29b707249108504b4e0041a21 -> no matching package found.
    - Installation request for deployer/deployer ~3.0 -> satisfiable by deployer/deployer[v3.0.0, v3.0.1, v3.0.2].

Now it's working. I forgot about:
    "minimum-stability": "dev",

I don't mean to be "that guy" but a stable package shouldn't really be requiring an unstable dependency, even if it is a specific commit.

I don't quite get this.
The phpseclib package has a lot of releases: https://packagist.org/packages/phpseclib/phpseclib
What do you mean by "when phpseclib do release" @elfet ?
Are you waiting for a 0.4.x version?

See the date of the commit: https://github.com/phpseclib/phpseclib/commit/2c96af214bf1b5e29b707249108504b4e0041a21
It is  23 Feb. There is no release containing the commit: https://github.com/phpseclib/phpseclib/releases

I see.
Then this solution should be noted on the website until it gets fixed somehow.
Now the tool basically seems broken from an outsider's point of view, if he tries to install it via Composer.
Even if he stumbles upon this thread, it will still leave a bad taste in his mouth, the tool loses some of it's credibility.

@ZeeCoder :+1:

I thinking about ugly hack, until phpseclib release. Include phpseclib to project. What do you think?
ping @ZeeCoder @oanhnn  @kenjis @gordalina @nspyke

I personally wouldn't include a dependent package into this one. That's a short sighted fix for what could become a bigger issue later on.
I tried to track down where this referenced commit was merged into, but have had no luck.
What is in this commit's tree that is required and not in the master branch? Has anyone tried running this using the phpseclib master branch?

I'm more curious about why Deployer needs such a recent version of phpseclib in the first place. What essential feature was added in 2c96af214bf1b5e29b707249108504b4e0041a2 that isn't available in the 0.3.10 tag?
The phpseclib repository is difficult to grasp - '1.0' and '2.0' branches that are both being merged into master, yet the latest tag is 0.3.10. Ugh.

Same questions here.

@elfet :+1:

The next release might be next year. Until then all users using Composer have  to set the version of phpseclib to composer.json. Or might be github issue will be reported again and again.
dev-master won't work if a bug will be introduced.

Dear all,
Fix version of phpseclib as a commit is my idea. It is temporary solution for issue #228 .
As commit 2c96af214bf1b5e29b707249108504b4e0041a21, deployer was run good.
I'm not sure a current stable version of phpseclib is good for deployer. it must be tested. I'm happy if someone can do it.
Thank you!

I think fork phpseclob and release it myself, until phpseclib will release.

It's better than nothing.
Not an elegant solution but still better than including the whole project in Deployer.

Yep, better than nothing

v3.0.5 still has this problem. I hope fixed soon.

The fork already exists, I think it will be in the next release.

If I'm not mistaken, Deployer v3.0.6 includes the above mentioned fix.
Could you check if it works as expected @kenjis?

Good! No problem.
By the way,

Package guzzle/parser is abandoned, you should avoid using it. Use guzzle/guzzle instead.

What's using guzzle/parser?

This is it: https://github.com/reactphp/http/issues/24#issuecomment-96585142

There were some new releases on phpseclib/phpseclib on August 3rd. Is the code you guys wanted in any of their releases now?

Hmm, I think so, based on the commit: https://github.com/phpseclib/phpseclib/commit/2c96af214bf1b5e29b707249108504b4e0041a21
I think v2.0 should be the thing Deployer needs.
Can you confirm this @elfet ?

Yes! Can anyone place new release?

2 окт. 2015 г., в 0:28, Hubert Viktor<EMAIL_ADDRESS>написал(а):
Hmm, I think so, based on the commit: phpseclib/phpseclib@2c96af2
I think v2.0 should be the thing Deployer needs.
Can you confirm this @elfet ?
—
Reply to this email directly or view it on GitHub.

This bug still occurs.
I was not able to install deployer from composer, and the standalone phar version cannot self-update.

@loranger Can you try run and show ouput to here:
$ composer init
$ composer require deployer/deployer

Using version ^3.0 for deployer/deployer
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - deployer/deployer v3.0.5 requires phpseclib/phpseclib dev-master#2c96af214bf1b5e29b707249108504b4e0041a21 -> no matching package found.
    - deployer/deployer v3.0.4 requires phpseclib/phpseclib dev-master#2c96af214bf1b5e29b707249108504b4e0041a21 -> no matching package found.
    - deployer/deployer v3.0.3 requires phpseclib/phpseclib dev-master#2c96af214bf1b5e29b707249108504b4e0041a21 -> no matching package found.
    - deployer/deployer v3.0.2 requires phpseclib/phpseclib dev-master#2c96af214bf1b5e29b707249108504b4e0041a21 -> no matching package found.
    - deployer/deployer v3.0.1 requires phpseclib/phpseclib dev-master#2c96af214bf1b5e29b707249108504b4e0041a21 -> no matching package found.
    - deployer/deployer v3.0.0 requires phpseclib/phpseclib dev-master#2c96af214bf1b5e29b707249108504b4e0041a21 -> no matching package found.
    - Conclusion: don't install deployer/deployer v3.0.10
    - Conclusion: don't install deployer/deployer v3.0.9
    - Conclusion: don't install deployer/deployer v3.0.8
    - Conclusion: don't install deployer/deployer v3.0.7
    - Conclusion: remove symfony/yaml v3.0.2
    - Installation request for deployer/deployer ^3.0 -> satisfiable by deployer/deployer[v3.0.0, v3.0.1, v3.0.10, v3.0.2, v3.0.3, v3.0.4, v3.0.5, v3.0.6, v3.0.7, v3.0.8, v3.0.9].
    - Conclusion: don't install symfony/yaml v3.0.2
    - deployer/deployer v3.0.6 requires symfony/yaml ^2.6 -> satisfiable by symfony/yaml[v2.6.0, v2.6.1, v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.2].
    - Can only install one of: symfony/yaml[v2.8.0, v3.0.2].
    - Can only install one of: symfony/yaml[v2.8.1, v3.0.2].
    - Can only install one of: symfony/yaml[v2.8.2, v3.0.2].
    - Can only install one of: symfony/yaml[v2.6.0, v3.0.2].
    - Can only install one of: symfony/yaml[v2.6.1, v3.0.2].
    - Can only install one of: symfony/yaml[v2.6.10, v3.0.2].
    - Can only install one of: symfony/yaml[v2.6.11, v3.0.2].
    - Can only install one of: symfony/yaml[v2.6.12, v3.0.2].
    - Can only install one of: symfony/yaml[v2.6.13, v3.0.2].
    - Can only install one of: symfony/yaml[v2.6.2, v3.0.2].
    - Can only install one of: symfony/yaml[v2.6.3, v3.0.2].
    - Can only install one of: symfony/yaml[v2.6.4, v3.0.2].
    - Can only install one of: symfony/yaml[v2.6.5, v3.0.2].
    - Can only install one of: symfony/yaml[v2.6.6, v3.0.2].
    - Can only install one of: symfony/yaml[v2.6.7, v3.0.2].
    - Can only install one of: symfony/yaml[v2.6.8, v3.0.2].
    - Can only install one of: symfony/yaml[v2.6.9, v3.0.2].
    - Can only install one of: symfony/yaml[v2.7.0, v3.0.2].
    - Can only install one of: symfony/yaml[v2.7.1, v3.0.2].
    - Can only install one of: symfony/yaml[v2.7.2, v3.0.2].
    - Can only install one of: symfony/yaml[v2.7.3, v3.0.2].
    - Can only install one of: symfony/yaml[v2.7.4, v3.0.2].
    - Can only install one of: symfony/yaml[v2.7.5, v3.0.2].
    - Can only install one of: symfony/yaml[v2.7.6, v3.0.2].
    - Can only install one of: symfony/yaml[v2.7.7, v3.0.2].
    - Can only install one of: symfony/yaml[v2.7.8, v3.0.2].
    - Can only install one of: symfony/yaml[v2.7.9, v3.0.2].
    - Installation request for symfony/yaml == <IP_ADDRESS> -> satisfiable by symfony/yaml[v3.0.2].

Potential causes:
 - A typo in the package name
 - The package is not available in a stable-enough version according to your minimum-stability setting
   see <https://getcomposer.org/doc/04-schema.md#minimum-stability> for more details.

Read <https://getcomposer.org/doc/articles/troubleshooting.md> for further common problems.

Installation failed, reverting ./composer.json to its original content.

@wesleywesley You are using symfony component >= 3.0
Current deployer has problem with symfony 3.x
Please #495

@oanhnn this issue exists for 1 year and still not fixed? Wow..


Last Node and Edge when export json

I export a json not a dot, and it generates a json file successfully.
However, when I try to read the json file using below codes, it shows an error JSONDecodeError: Expecting value
with open("Test1-CFG.json", 'r') as f:
          data = json.load(f)

I try to fix it. When I remove each comma in the list of nodes and edges, I can read the json file correctly.
From
  "nodes": [
    {
      "id": "n1",
      "line": "4",
      "code": "void main(String[] args)"
    },
    {
      "id": "n10",
      "line": "14",
      "code": "System.out.println(\"End\")"
    },
  ],
 "edges": [
    {
      "id": "e1",
      "source": "n1",
      "target": "n2",
      "label": ""
    },
    {
      "id": "e2",
      "source": "n2",
      "target": "n3",

to
  "nodes": [
    {
      "id": "n1",
      "line": "4",
      "code": "void main(String[] args)"
    },
    {
      "id": "n10",
      "line": "14",
      "code": "System.out.println(\"End\")"
    }
  ],
 "edges": [
    {
      "id": "e1",
      "source": "n1",
      "target": "n2",
      "label": ""
    },
    {
      "id": "e2",
      "source": "n2",
      "target": "n3",

Can you fix this in the code?
I think it is maybe in nodes and edges
If it is a last node or a last edge, it does not have to write ,(comma)

I will check this out and return with an answer ASAP.

I pushed a fix for this issue, and this is now fixed in master.
It will take me some more time (maybe 10 days) to publish a new release with the latest changes.

I just released PROGEX-v3.4.0 which includes the fix for this issue and some other improvements.


How should I understand "all query patches within a  winodw share the same key set"?

Hi, there. I have a little trouble in understanding the shared key set concept. I can't find any relative implementations, like fixing the key set, in codes.
Could you tell me how should I understand "all query patches within a  winodw share the same key set which facilitates memory access in hardware"?
Hope to hear from you soon.

Have the same question, hope to have a detailed description

This is compared with the traditional sliding window method. The following figure shows the difference:

In traditional sliding window method. Different querys, q and q', will have different neighboring windows, which indicates different key sets. The computation is unfriendly to memory access and the real speed is thus not good.
In non-overlapping window method used in Swin Transformer. Different queries within a same red window, for example, q and q', will share a same key set.

Thanks for your explanation. It helped me a lot.

Hi there,
Thanks for the explanation! How are these keys computed?
For a window, there is a shared key; is it preset? or computed over the window?
Thanks!


Advice set/getAllKeys in batches

Hello,
I would like to setKey / getAllKeys in batches, because I have a lot of data, and in the case where user loses internet connection I want to be able to store/access at least some portion of the data.
Are there any methods I could access in order to set and get keys in batches?

Great, thank you for your answer!
One last question: Is there any function to return all entries (key value pairs)?.
We are using mmkv for persistent caching (like a database) and we would like to fetch all entries.

Hey! See this issue for an explanation on why "getting all values" is not possible unless you know their type. (If you know that all values are strings, it's possible).

Awesome! We’ll save everything in string format using JSON.stringify and then parse it and validate it when fetching.
Is there any limit set for the stored value (nr of chars, KBs) or it does not matter?


Add filter alias for attributes

Add attribute filter, this way, on the frontend I can just get the variant.attributes.format without looping over the attributes like so: variant.attributes.find(attr => attr.slug === 'format')
  product(id: "UHJvZHVjdDoyMzYxOTU=", channel: "gb") {
    variants {
      id
      attributes {
        format: attribute(slug: "format") {
          attribute {
            id
            name
            slug
          }
          values {
            name
          }
        }
      }
    }
  }
}```

Hello, I'm interested in working with this issue.
Can you please guide me through, I'm new to open source :D

Like could you please tell the directory where the filter alias for attribute needs to be added


Kinesis Firehose Processors array only accepts one processor

Just checking this is correct? processingConfiguration accepts an array of processors, but then when passing multiple processors I get the following error.

Exactly 1 Processor needs to be supplied when processing is enabled

      processingConfiguration: {
        enabled: true,
        processors: [
          {
            type: 'Lambda',
            parameters: [
              {
                parameterName: 'LambdaArn',
                parameterValue: inputValidator.arn,
              },
              ...pulumiParameterFix,
            ],
          },
          {
            type: 'Lambda',
            parameters: [
              {
                parameterName: 'LambdaArn',
                parameterValue: newLineAdder.arn,
              },
              ...pulumiParameterFix,
            ],
          },
        ],
      },

Thanks for reporting this. This appears to be how Kinesis itself works. That error message is coming from the Kinesis API. You can see that the API itself does take an array (https://docs.aws.amazon.com/firehose/latest/APIReference/API_CreateDeliveryStream.html)
I tried removing enabled: true which allowed the creation to succeed. Oddly, I couldn't find anything in the Kinesis documentation describing this behavior. Unfortunately, I don't know enough about Kinesis on what the best way to do what you're doing to do is, but I'm going to close this out as the correct behavior.


Release notes 0.20

Release notes for 0.20 (#708)
Changes since 0.19
IMPORTANT: When you write your release note addition and you mention an issue or pull request with the # syntax, please write before whether it is an issue or a pull request. It help me later writing the release notes.

Format all soco main, test and example code with the black code formatter and make it mandatory going forward including a TravisCI check. Pull request #706.

Add support for creating and separating stereo pairs of speakers. Note: works with dissimilar Sonos speakers if required. PR #704.

Fix bug where data_structures_upgrade would fail on items that has no uri #702

Add support for autogenerating vendor extended DIDL-Lite classes (PR #713). This should fix all the problems we have with SoCo crashing if some vendor spedific data type is unkonwn.

Process share browsing correctly #717.

Categorise Sonos Amp as a playbar in order to provide support for 'night sound' and 'speech enhancement' https://github.com/SoCo/SoCo/pull/721

Improve test_remove_playlist_bad_id() to handle the case of no existing playlists.
PR #726, fixes issue #725.

If port 1400 is in use, the next available 100 ports will be tried.  #724

Is the pairing functionality from #704 not merged in yet? I did an install of the latest version (0.19) and those two functions aren't in core.py.

It's merged for inclusion in 0.20, but the 0.20 release seems to be stuck.

Any idea what the hold up is?

Any idea what the hold up is?

No, sorry. I asked in Gitter (https://gitter.im/SoCo/SoCo) about three weeks ago, but no responses so far.

0.20 is finally out. Thanks to everyone who contributed.


Babylon GUI's HolographicSlate doesn't support linked nodes

https://www.babylonjs-playground.com/#Q1R5XX#1
The documentation here (https://doc.babylonjs.com/divingDeeper/gui/gui3D#controls) seems to imply that controls can be 'linked' to objects in the scene, and in fact this can be seen to be true for almost every 3D control. But if a HolographicSlate is linked to an object, either by calling linkToTransformNode() or setting node.parent, then the slate position's z-axis will perpetually increase over time, sending the slate off into the distance. Additionally, if the slate is scaled in any way, it will travel off either diagonally up-left (for a larger slate) or down-right (for a smaller slate).
I think it might have something to do with the fact that the slate uses a custom pivot point, but I'm not familiar enough with pivots, parenting, or the original implementation of the slate to look further.

some pointers for whomever may take this issue : the pivot point is set to the center, whereas the slate's origin is the topleft corner. This is done so the slate's handles (to resize and rotate) are just changing the pivot point and not the position

Narrowed it down to the follow behavior's _updateLeashing function, which sets the parent to null and back again on each frame.
This seems to be an issue with computeWorldMatrix, when the mesh has a pivot and scaling (and not directly with the follow behavior / holographic slate):
https://playground.babylonjs.com/#2J03YY#1
@CraigFeldspar - A general question regarding the follow behavior - is there a reason this function is running even when the follow behavior is not turned on?

@RaananW I can't remember precisely, but _updateLeashing should be only used for an activated followBehavior

@RaananW I can't remember precisely, but _updateLeashing should be only used for an activated followBehavior. Maybe this is a bug ?

I've fixed it in the linked pull request. It now only runs when the feature is enabled. Thanks for confirming!


B-20948 SSW Calculations INT

Agility ticket
Summary
Final SSW Member-paid and GTCC-paid expenses erroneously including counselor excluded and/or rejected expenses.  If an expense is excluded or rejected by the Closeout Counselor, they should not appear on the Final SSW.
Previously, there was no status check on the moving expenses. Now we check if the expense is in the PPMDocumentStatusRejected or PPMDocumentStatusExcluded status and if it is, we don't include it in the totals for either the Member-paid or GTCC-paid totals on page 2 of the SSW.
How to test

Create a new move with a PPM shipment as the customer (make sure you request an advance!)

Login as the SC and submit the move.

As the customer, upload PPM documents. When you get to the page where you can add expenses, add 2-3

Login as the SC and find the move to complete closeout

Reject or exclude some (but not all) of the expenses that the customer submitted

After generating the AOA or Payment packet as the office user, verify that you do NOT see the expenses that you rejected/excluded on page 2 of the SSW report.

Check out the screenshots below for a few more test cases.

Screenshots
Test Case A, no GTCC used, customer submitted two expenses

SC approved $100 and excluded $50

Total does not include the excluded/rejected expenses, for a total of $100:

Test Case B, GTCC used, customer submitted two expenses

SC approved $80, rejected $20

Total on the SSW is $80, rejected $20 not included

Screenshots
Before changes, incorrectly excluded/rejected expenses for a total of $150:

After fix, total does not include the excluded/rejected expenses, for a total of $100:

No 508 compliance screenshot needed as this only impacts text fields on the generated SSW PDF.

Failing test is flaky


Home Set Up and Methods

This PR has all the steps followed to develop the Home Page of the Capstone Project including:

Header, navigation bar, layout, and styles.
Footer layout, and styles.
Developed a method to hit the meals API and retrieve data from it.
Built a method to display the list of meals on the home page.
Did method to add like to a specific meal.
Add a method to display likes on each meal on the home page.
Developed a method to calculate the 'all items counter' on the home page.
Add unit test on Jest for the method above.

Highlight
Hello @jmonto55  I pull this branch into mine and the interface looks good and the like counter counter works well. Good job. I also ran npm test to test the function for the likes counter and it passed :100:

to avoid repetition in the api.js  file you can consider saving the api urls in variables.


Can not switch cameras

On my device, the camera is the user facing camera and all input on the facingMode prop does not make a difference. From the code it also looks like, different than the docu in the README, the default is user facing:
https://github.com/BlackBoxVision/react-qr-reader/blob/450f49e6d60b0eccf7548086721fa7c5cf26f3a0/src/QrReader/index.tsx#L39-L40

Would you mind trying v4?
You can install it by doing npm i<EMAIL_ADDRESS>We've made a bigger change in the way of customizing the access to the camera, we now let you pass directly the MediaTrackConstraints so you can configure the best options for your use case.

Sure, how would I configure the camera facing direction with v4?

Passing a prop called constraints, if you want to use the rear or back camera you can pass the prop like this constraints={{ facingMode: 'environment' }}

Thanks, that worked!

Could you publish with the new peerDependencies for v4, too? That would solve all my problems for the day :)

I'll check it out, I think I've already updated before making v4 release. Cool that worked! You're welcome, I'm closing this issue. We'll improve documentation on the usage of the library soon by launching a docs website. If you liked you can help us recommending it, and giving us a star!

I've checked the peerDependencies by running npm view @blackbox-vision/react-qr-reader peerDependencies and it prints out the following output:
{
  '@zxing/browser': '0.0.7',
  '@zxing/library': '^0.18.3',
  react: '^16.8.0 || ^17.0.0',
  'react-dom': '^16.8.0 || ^17.0.0'
}

Maybe you've something cached.


Angular tests

I got unit tests working with Karma. They work the same way they would with the original boilerplate.

Just finished up E2E testing, I believe. Going to make coverage reporting work next, then I'll try to write up an E2E test to make sure it worked.


Fixed alias lab dell 740xd interface naming

Addressing #186

Can one of the admins verify this patch?


AI loses vision when cameras lose power.

About the PR

The AI will now properly lose vision granted by cameras when those cameras lose power.
Media

Requirements

[x] I have read and I am following the Pull Request Guidelines. I understand that not doing so may get my pr closed at maintainer’s discretion
[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:cl:

fix: The AI will now properly lose vision granted by cameras when those cameras lose power

Perhaps a happy compromise would be giving cameras a small internal battery similar to flashing alert lights?

do EMPs affect cameras? I haven't messed with them enough to know

Yes EMP does affect cameras

Perhaps a happy compromise would be giving cameras a small internal battery similar to flashing alert lights? Gives a buffer of time before the ai gets completely blinded station wide

I'd rather just have APC channels implemented instead. I don't want us to get into the habit of adding ever more batteries to machinery around the station.

Maybe just reduce the vision or something? If a full power outtage happens when nukies attack for example the AI is blind for the rest of the round. I don't think it would be fun to be unable to see anything because of minor power issues or a singulo going off.

The AI should be able to see if there is a disabled camera in the room, maybe highlight the camera in red over the AI overlay?

How about instead this will be like an optional thing in AiVisionComponent?
Like requiresPower, changeWhenUnpowered and rangeWhenUnpowered or something?
Could also be put on other things that way

Right now it only applies to AiVisionComponents that are attached to Surveillance Cameras. The vision component that is (for example) attached to the AI core isn't affected by this.

Right now it only applies to AiVisionComponents that are attached to Surveillance Cameras. The vision component that is (for example) attached to the AI core isn't affected by this.

Yeah, im just putting this down as a possible idea

Wasn't there talk about the AI being able to see through borgs as well?
That would help with the "no power = no vision" problem, depending on how it gets implemented.

ai needs a way to move its camera and know where it is without vision, and also should not HAVE to see something to do something, or know that something its connected to is there.

How about instead this will be like an optional thing in AiVisionComponent? Like requiresPower, changeWhenUnpowered and rangeWhenUnpowered or something? Could also be put on other things that way
this is a great idea for versatility, admeme events would be very happy too im sure.

could just change it to not be able to interact with things in dead cams range if people dont want loss of vision and just tie vision to decon/wire cutting or something

Just an idea: what if instead of completely shrouding a room with static, it could be partially covered. The static system appears to tile based, so maybe it could randomly tiles to cover with static? Maybe like 70% reduced visibilty? Which tiles are concealed could be random and refresh every couple seconds. Thus making the AI have to watch the unpowered camera for longer or risk missing something.

We discussed this among maintainers and at the moment it's not really good for gameplay because if there's a power outage, the AI can't see or do anything and just sits there with no agency (e.g. powergridcheck, station loses power over time). If there were navmap overlay or borg vision it might be more interesting but would need to reassess then.


Exceptions thrown in a function scheduled with run_every are not scrolled on the display

For example, with this programme:
from microbit import *

@run_every(s=1)
def foo():
    raise Exception

while True:
    if button_a.is_pressed():
        foo()
    sleep(200)

An exception is thrown every second, which can be seen on the serial output, but nothing is scrolled on the micro:bit display.
When button A is pressed and the foo() function is called directly the exception is scrolled on the display correctly.

I have a working patch that scrolls exceptions from run_every on the display.  It does this asynchronously, ie in the background, otherwise the run-every function blocks everything else if it has an error.
Also, I think that functions that raise should have their run-every cancelled so they only display the error once.  If you have an error in your run-every function then it's very unlikely that you want it to keep running and keeping erroring out.

I have a working patch that scrolls exceptions from run_every on the display. It does this asynchronously, ie in the background, otherwise the run-every function blocks everything else if it has an error.

Could that interact with the rest of the user code in a way in which the exception is not scrolled? e.g., if the user code happens to scrolls something on the display immediately after the exception is thrown, will the exception text stop and the other message take its place?

Also, I think that functions that raise should have their run-every cancelled so they only display the error once. If you have an error in your run-every function then it's very unlikely that you want it to keep running and keeping erroring out.

Yes, I think that's a good idea! I assume if there is a try/except capturing the exception the function would not be cancelled, right?
This would avoid having to have code like this:
continue_logging = True

@run_every(s=10)
def log_data():
    global continue_logging
    if continue_logging:
        try:
            log.add(temp=temperature())
        except OSError:
            continue_logging = False


Fix jar path and add missing ones for spark jobs

Fix path of jars / add missing jars in spark job
remove print, reduce clutter
Description
Path of jar files in tests for MXNet on Spark are incorrect. This PR fixes it.
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[x] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[x] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

@mxnet-label-bot add [pr-awaiting-review, Scala]
@aashudwivedi could you re-trigger the CI?

I've re-triggered the CI, all tests have passed now.
Thanks for having a look.

Looks okay to me!
Thanks for fixing this and welcome to the MXNet community :)
Thanks you :)

@lanking520 ping for review/merge.


Fails slow with incorrect Postgres credentials

Right now, Photon tries to connect for 10s to the query engine when starting the engine.
If the query engine throws connection errors due to incorrect credentials, Photon should immediately fail.

Fixed in latest version.


[Bug]: Game crashes whenever I open the game

All of the following criteria must be met

[X] All Requirements must be installed.
[X] Changed the title so that it doesn't just says "[Bug]: "
[X] I have searched the GitHub issues for my bug, even in the closed issues.

All of the following are optional to answer

[ ] Tried reinstalling the Game.
[X] Tried reinstalling MelonLoader.
[X] Tried restarting PC.
[ ] Was able to see the Start Screen.

Describe the issue.
I just put melonloader into Bloons td 6. I checked, it was opening completely fine before. but all I did was add melonloader (I didn't do anything else I just hit the button to install the most recent version of melonloader on to btd6) and the game now wont launch. I get the error il2cpp_init detour failed: Failed to load hostfxr. Please make sure you have installed the .NET 6.0 runtime.
[15:39:45.156] [ERROR] il2cpp_init detour failed: Failed to load hostfxr. Please make sure you have installed the .NET 6.0 runtime.  I Tried downloading that .net 6.0 thing and have no idea what it is or what it even does.
Did you attach your log file?
No, I could not find a log file at {Game_Directory}\MelonLoader\Latest.log

.NET 6 is a C# runtime. You need to have it installed. You can get it here

Tysm! That worked


[Eldon] Pinning of contacts in AddressBook PR (In progress)

Work in progress. Can add and remove pin tags now

Coverage decreased (-3.8%) to 88.365% when pulling 0ac5c9dc637e208f50a58833a6b8df39ced76788 on eldonng:new_v1.1Eldon into d6280a2a06e49728b2e596b8a586d95f104e85c1 on CS2103T-T17-B3:master.

Coverage decreased (-4.1%) to 88.041% when pulling b3164e80f6daa7ad8f42565e6d8c79c43477f092 on eldonng:new_v1.1Eldon into d6280a2a06e49728b2e596b8a586d95f104e85c1 on CS2103T-T17-B3:master.

Coverage decreased (-5.0%) to 87.206% when pulling 85f8a6803cc050c6fbe3e62adafb9befcad6b2be on eldonng:new_v1.1Eldon into d6280a2a06e49728b2e596b8a586d95f104e85c1 on CS2103T-T17-B3:master.

Coverage decreased (-3.8%) to 88.387% when pulling 52e4ca1f65adb0a8236337405cebde8c5a8f83a9 on eldonng:new_v1.1Eldon into d6280a2a06e49728b2e596b8a586d95f104e85c1 on CS2103T-T17-B3:master.

Coverage decreased (-1.8%) to 90.313% when pulling c3b188110a266a2f4c29f23e99e9de002a9af51a on eldonng:new_v1.1Eldon into d6280a2a06e49728b2e596b8a586d95f104e85c1 on CS2103T-T17-B3:master.

Coverage decreased (-0.5%) to 91.637% when pulling ddf7f937420f18dbaba7e5cf8e5bb4b37b842b0a on eldonng:new_v1.1Eldon into d6280a2a06e49728b2e596b8a586d95f104e85c1 on CS2103T-T17-B3:master.

Coverage decreased (-0.3%) to 91.877% when pulling 30c7ddaf31e16244b528eb802e3225919c8a363a on eldonng:new_v1.1Eldon into d6280a2a06e49728b2e596b8a586d95f104e85c1 on CS2103T-T17-B3:master.

Coverage decreased (-0.3%) to 91.877% when pulling 69f6f155068d6884ae650c89a5b8ac49eec3c84b on eldonng:new_v1.1Eldon into d6280a2a06e49728b2e596b8a586d95f104e85c1 on CS2103T-T17-B3:master.


Mobile phone: image discrepency

Brad: Re: Tradeblock Founders Story, did we change the banner image? Noticing we have a different selection here than what’s showing in desktop.
Phil note: I prefer the desktop image to the image in Brad's comment.

Just for clarity: Phil's preferred image is

Went ahead and replaced the image ---- Brad had that other one in there because it was taller height wise. This one is shorter. So if you're okay with it, here's what it looks like on small screen:

Yes, looks good.

Updated!


add new PR template with tasks for each required section

Problem

[x] We want to raise the bar and encourage our standard processes in our GitHub repos

Solution

[x] Use a modified PR template that matches expected

Additional Notes
Open to feedback on this format. Making heavy use of the tasklist formatting since github renders them as checkboxes, but the overall completion counts are not useful since we'd only expect at least one check in the automated tests section instead of all checked.
Also, shifting emphasis onto github issues for tracking work related to this repo since I don't believe we want to link to internal/private ticketing systems here.
Links
Ticket

[ ] GitHub issue _____

Other links
Verification
Manual tests

[x] template was copied into this PR body and filled out as an example since it does not exist in main branch yet.

Automated tests

[x] Automated tests added
[x] Automated tests updated
[x] N/A - change only includes PR template
[ ] deferred - (provide GitHub issue for tracking)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Codecov Report

Merging #918 (26b8661) into main (32c435e) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more

@@           Coverage Diff           @@
##             main     #918   +/-   ##
=======================================
  Coverage   92.99%   92.99%
=======================================
  Files         118      118
  Lines        5094     5094
  Branches     1500     1500
=======================================
  Hits         4737     4737
  Misses        336      336
  Partials       21       21

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 32c435e...26b8661. Read the comment docs.

What do you think of not having checkmarks for Problem and Solution?
For the verification section, can we have separate checkmarks for unit and e2e tests?


(runner-playwright) Command test not found in 2.10.0

the output in 2.10.0 version :
Running npx playwright test --project=chromium -c uuv/playwright.config.ts  --reporter=@uuv/playwright/uuv-playwright-reporter
error: unknown command 'test'
the output in 2.8.0 version :
Running npx playwright test --project=chromium -c uuv/playwright.config.ts  --reporter=@uuv/playwright/uuv-playwright-reporter
Starting the run with 7 tests
Feature: uuv\e2e\accueil.feature
✓ Page Accueil - Test1  (4555ms)
✓ Page Accueil - Test2  (2450ms)
✓ Page Accueil - Test3  (2440ms)
✓ Page Accueil - Test4 (2445ms)
✓ Page Accueil - Test5 (2408ms)
Feature: uuv\e2e\test.feature
✓ Connexion OK  (2285ms)
✓ Connexion Impossible  (2257ms)
End of the tests execution
Test Execution Report :
+----+-------------------------+--------+---------+--------+
| Id | File                    | Passed | Skipped | Failed |
+----+-------------------------+--------+---------+--------+
| 1  | uuv\e2e\accueil.feature | 5      | 0       | 0      |
| 2  | uuv\e2e\login.feature   | 2      | 0       | 0      |
+----+-------------------------+--------+---------+--------+

Cannot reproduce this bug


Fix donation badges not being spaced out from the license message

...at the bottom of the file.

fixed by adding an extra <br> tag in https://github.com/inttter/md-badges/commit/ca4face34cd93f60afb36e25c7b809468efa604b


Make FluentBundle abstract and do some API refactoring

Fix #49
Fix #44

@ElectroJr is this what you had in mind?


@DynamoDBTable(tableName = <should also get value from @Value annotation>)

May be like
@DynamoDBTable(tableName = @Value("${amazon.dynamodb.tableName}"))
I tried this but it does not works.

You can use a MapperConfig.
For example, to have a standard prefix to all you table names (we had "test." and "prod.") use:
@Value("${amazon.dynamodb.tablename-prefix}")
private String tableNamePrefix;
@Bean
public DynamoDBMapperConfig dynamoDBMapperConfig() {
DynamoDBMapperConfig.Builder builder = new DynamoDBMapperConfig.Builder();
builder.setTableNameOverride(
DynamoDBMapperConfig.TableNameOverride.withTableNamePrefix(tableNamePrefix));
return builder.build();
}
This way, we could access "test.tableName" in our test-environment and "prod.tableName" in production.
HTH,
Mohamed

can we still not do this @DynamoDBTable(tableName = @value("${amazon.dynamodb.tableName}")) ?

can we still not do this @DynamoDBTable(tableName = @value("${amazon.dynamodb.tableName}")) ?

Thanks @mmaza , however I throw nullPointerException DynamoDBMapperConfig.typeConverterFactory.
To solve it add this line to the dynamoDBMapperConfig () method:
builder.setTypeConverterFactory(DynamoDBTypeConverterFactory.standard());
Remaining the method like this:
	@Bean 	public DynamoDBMapperConfig dynamoDBMapperConfig() { 		DynamoDBMapperConfig.Builder builder = new DynamoDBMapperConfig.Builder(); 		builder.setTypeConverterFactory(DynamoDBTypeConverterFactory.standard()); 		builder.setTableNameOverride(DynamoDBMapperConfig.TableNameOverride.withTableNamePrefix(tableNamePrefix)); 		return builder.build(); 	}


FloatingToolbar component

This is kind of like a floating action button but with multiple buttons in one floating element:

Should just render the children as contents, not necessarily the buttons in that mock.
Props

[ ] position: string, one of topStart, topEnd, bottomStart, bottomEnd to set the position of toolbar
[ ] `marginX: int, margin in the x dimension
[ ] marginY: int, margin in the y dimension

Visuals:

[ ] Should float above other elements on the screen
[ ] Casts a shadow like box-shadow: 0px 4px 8px rgba(0, 0, 0, 0.25);
[ ] White background
[ ] Should anchor to screen position specified in position

Shouldn't be too hard to get this done.


Add veBAL table to portfolio page

Description
Addresses an issue: https://github.com/balancer-labs/frontend-v2/issues/1695

Remove "Incl." text from veBal banner
Add veBAL protocol liquidity table with Expiry date column to portfolio page
Rename "Stake" column of PoolsTable to "Actions" column. Add lock/stake action button.

Type of change

[x] New feature (non-breaking change which adds functionality)

How should this be tested?
Please provide instructions so we can test. Please also list any relevant details for your test configuration.

Your locked veBal show on the "veBAL protocol liquidity" table
Not-locked veBal should show on the "Unstaked pools" table and have a "Lock" action

Visual context

Portfolio Page Now
Portfolio Page  Before

Checklist:

[x] I have performed a self-review of my own code
[x] I have requested at least 2 reviews (If the PR is significant enough, use best judgement here)
[x] I have commented my code where relevant, particularly in hard-to-understand areas
[x] The base of this PR is master if hotfix, develop if not

I'm seeing "Stake" instead of lock on the 80/20 pool on Goerli.

I'm seeing "Stake" instead of lock on the 80/20 pool on Goerli.

@timjrobinson I also see 'Stake' on Goerli and Kovan. I believe this is due a bug due to that specific pool being set up incorrectly on Kovan.
I have tested this on Mainnet and I see the correct 'Lock' button:


One Hot Encoding Keras?

Is it possible to include one hot encoding in a keras model for pmml?

Hi @1samwatkins3005, it is not possible. Using keras exporter, you can export only the keras model into pmml.


How to trigger select on user-specified input

I'm using paper-autocomplete as a "suggestion" service in a search box, where we show guesses for what the user wants to search for in the suggestions, but still want to allow the user to submit their own search query.
What's the easiest way to get this functionality, where either we trigger a select when the user selects an item from the dropdown, or we trigger a select when the user hits Enter, for instance?
Currently, I'm doing the following:
inputRemote.querySelector("input").addEventListener('change', function(e) {
      if (document.activeElement == this) {
        if (inputRemote.querySelector("paper-item[aria-selected=true]") != null) {
          return false;
        }
        inputRemote._fireEvent({
          text: inputRemote.text,
          value: inputRemote.text
        }, 'selected');
        inputRemote.reset();
        return true;
      }
    });

You could do something like this. If the user's input matches something you've got in your list of suggestions it will return true, otherwise, it will return false.
function guessSelected(element) {
  if(element.source.indexOf(element.text) >= 0) {
    return true
  } else {
    return false
  }
}

to call it you'd have to do something like.
if(guessSelected(inputRemote)){
  // what you want to happen if they selected an option
} else {
  // what you want to happen if they input their own
}


fix: API documentation for Task Result type

Description
Fix documentation about the type of task result in the
/api/v1/tasks.
The type was moved to Dict[str, Any]
It adds more consistency on task result in the API.
Verifying the message and status and error (in case of FAILURE)
Types of changes

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

Additional requirements

[ ] Tests have been added for the bug fix or new feature
[x] Docs have been added for the bug fix or new feature

Code of Conduct
By submitting this PR, you agree to follow our Code of Conduct.

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

I'm including #528 in this PR in another commit as it is related to this PR.

Summarising a chat with Kairo:

API results should be designed with the user in mind.
Case-handling of different results should be as easy as possible.
The user shouldn't need parse strings to make decisions.
If the user generally doesn't care for the difference between certain response types, or doesn't handle them differently, it might be okay to summarise those response type.
For now we stick to the existing response types coming and forward them mostly as they come from celery/worker.

Maybe we can consider some simplifications, if they don't disrupt existing clients:

Exclude redundant status field from task result.
Only mandate task results with message field for SUCCESS, ERROR, FAILURE  state responses, and do not add them if they are missing in any of the other state responses.
Consolidate message and error fields for ERROR and FAILURE.
For ERROR the message could be a combination of what's currently in both fields, and error could be omitted.
For FAILURE the message could be the exception message, and error could be omitted or show the exception type.

Did you consider any of those? I suppose they are improvements that should be done in the worker first.

Yes, most of them are how the RSTUF Worker sends the task result, not in the API.
We should file issues to do there, as a polishing result.
I noticed also that removing status from result is a breaking change for the CLI :)
I mean, we will need changes there.

I noticed also that removing status from result is a breaking change for the CLI :)
I mean, we will need changes there.

Damn. I guess it's also okay to leave it, and ignoring it in the cli first?

Damn. I guess it's also okay to leave it, and ignoring it in the cli first?

Yes, I will revert it and file issues so we can do it without breaking operability.

I opened the following issues:

https://github.com/repository-service-tuf/repository-service-tuf-cli/issues/508
https://github.com/repository-service-tuf/repository-service-tuf/issues/622
https://github.com/repository-service-tuf/repository-service-tuf-api/issues/537
https://github.com/repository-service-tuf/repository-service-tuf-worker/issues/454


calicoctl documentation

Hello,
In our project I would like to link to the calicoctl documentation but I'm not able to find one. Is it something that you'd want to add? It could go here, for example: https://github.com/Metaswitch/calico-docker/tree/master/docs
Right now, I am referring to calicoctl help for more details.
Thank you.

Yes, it's something we'd love to add. It's on our plan, but not likely to happen this week. Pull requests are of course welcome! The location you mention is the right place for it.

Current work in progress is in a PR - https://github.com/projectcalico/calico-docker/pull/438
Comments are welcome!

PR #532 Should cover this when it goes in.

Fixed by #532

Awesome, thank you!


Export from file system should take a file not a directory

At the moment 'duffle export foo' treats foo as a directory, and looks for a bundle.json or bundle.cnab according to whether the '--insecure' flag is passed.  For consistency with othe commands, I suggest:

export foo: exports from local store (and supports version)
export -f path: exports from filesystem and treats path as a file name not a directory and infers signedness from file format
--insecure flag skips signature verification for signed bundles, does nothing on unsigned bundles

Thoughts?  cc @michelleN

+1 to all of this

Having a required arg or flag is a bit confusing. We decided to be able to take an arg that is either a bundle reference or a path to a signed or unsigned bundle file as the arg. The -f is no longer needed in this scenario and duffle is responsible for figuring out whether the given arg is a file path or a bundle reference.

In that case you must provide a way to override Duffle's strategy.  Consider:

Local store contains bundle foo
Current directory contains file foo

What does duffle export foo do?  Let's say it chooses the bundle reference.  But in an IDE scenario the user could right-click the file foo and issue the export command.  How can I tell Duffle to export the foo file instead of the bundle reference?
Possible strategy:

Positional parameter for the bundle/file name as you suggest.
By default, pick whichever one exists.
If both exist, by default prompt or error.
Allow a flag to control how the name is interpreted e.g. duffle export foo --source=file vs duffle export foo --source=bundle.
If the flag is present, then do not check for the other source.  E.g. if source is file and the file doesn't exist but the bundle does, then error instead of using the bundle.  Never prompt if the flag is present.

"Pick whichever exists" as a default still feels slightly dangerous because users forget what context they're in ("aargh no I didn't mean THAT foo"), but bundle references and file names will usually be distinct enough that this shouldn't be an issue for us.

At the moment, it checks if the name passed in is pathy (does is contain/) and if not, then find bundle in local store.

I really like your idea of adding the source flag and will add that to the PR
I was under the impression before that you had to export a bundle that follows the convention name:version and that is not currently the case. I think if you're trying to export a bundle from the local store then we should require the user to provide the bundle name and version. That way if we are in the case that we have a bundle called foo and a directory called foo, then a user cannot expect that the bundle from local store will be exported bc it they are not using a valid bundle reference. If we like this idea, then I can also change the algorithm to first identify whether the bundle reference looks like a bundle. I'll also need to update the current algorithm to do more than just check if the arg looks pathy and actually go and see if foo is a directory in the current directory.

What do you think @itowlson ?

I'm not sure about requiring a version - think that one needs to be raised to the team/community for discussion.  But I don't think requiring one helps you distinguish - isn't the colon a legal filename character on Unix, i.e. you can have a file called foo:bar?  (Even on Windows, c:foo could mean "bundle c version foo" or "file foo in the current directory on drive c... though both of those would be pretty weird!)
I am doubtful about using / as an "it's a file" indicator - won't bundles have scopes like itowlson/helloworld:0.0.1?  Again could be wrong here.
My feeling is if we have a source flag then what we should do is:

If the source flag is present, respect that.
If the source flag is NOT present, check BOTH file and store.

If only one exists, use that.
If both exist, prompt (or fail).

If we try to guess which it is based on the 'look' of the name, then can become one more thing users have to understand to avoid surprises.  I suspect collisions will be rare enough that a naive 'check both' strategy will work just as well as a clever algorithm anyway.
Except... except if the bundle is named a:something and you're on Windows... urgh...

I hear ya. I'd like to avoid prompting the user if we can here. The less human interaction, the better to get to the end result, the better.
How about we just make the default behavior checking the local bundle store? If you want to pass in a path instead then just use the --source-is-file flag or some flag with a better name?

I like the complete unambiguousness of that.  It's like the -f flag but without the confusing "you need a positional argument if X but the option argument if Y".  :shipit:

I don't see the usability problem with duffle export -f bundle.json. It is similar to for example kubectl apply -f doughnuts.yaml.
It's unambiguious and people are used to it from other CLIs. I like that the flag is explicit and doesn't require contextual explaining, "Sometimes the positional argument mean this, except when this flag is set, then it means this". The logic spelled out in the above comemnts is (to me) more confusing than using a flag, no?

@carolynvs But I feel there's a difference in that kubectl apply doesn't have an alternative semantics for names.  If we go with duffle export -f bundle.json then I feel the alternative (referring to the local store) should be e.g. duffle export -b itowlson/helloworld, not duffle export itowlson/helloworld.  I.e. if we are going to pass the bundle under a flag then arguably we should always use a flag rather than sometimes use a flag and sometimes a positional argument.  To be honest that ends up pretty similar to duffle export foo --source=file vs duffle export foo --source=bundle but I see your point that it's clearer to have the 'what it means' be right there on the name argument rather than on a separate flag.
I'd be perfectly happy with a -f/-b where you must pass one or the other.

If we can follow the mantra args are required and flags are optional, then using a flag for every instance of this command would not be ideal.
I also don't think we should follow kubectl as a canonical example cli UX. Let's take a look at more common package management examples like brew, helm, apt and the comparison of commands section in [this wiki](Comparison of commands) as examples to follow.


Typeahead wrong style

Hi. I am using last Angular 2 and last Bootstrap 4. When I created typeahead I noticed that style is terrible:

And rendered DOM is different than on yours site:

Simple code:
<input class="form-control" [(ngModel)]="studentToAdd" [typeahead]="students"                  [typeaheadOptionField]="'surname'">
Thanks!

Same issue here.

Can you please provide a plunkr?

@Dinistro hi. For a what? I anly add <input class="form-control" [(ngModel)]="studentToAdd" [typeahead]="students" [typeaheadOptionField]="'surname'"> and have wrong styles. And for ng-select I have the same issue. Thanks!

@Dinistro any ideas about that?

@AndersonDev I can't reproduce this issue. This is why I asked for a plunkr.

@AndersonDev The problem is because
import { Ng2BootstrapConfig, Ng2BootstrapTheme } from 'ng2-bootstrap/ng2-bootstrap';
Ng2BootstrapConfig.theme = Ng2BootstrapTheme.BS4;

The walkaround way is using

in your html file.

Dup with https://github.com/valor-software/ng2-bootstrap/issues/507

Working on simpler way for theming
Closing as duplicate


Version - v1.2.5 missing from the version list

I'm trying to flash tuya - generic ir remote from manufacturer - HomeMate.
Chipset is BK7231N.
Tuya smart app shows the version as v1.2.5 which is missing from the version list in tuya-cloudcutter. With other versions/profiles i get this error - The profile you selected did not result in a successful exploit.
I was successfully able to flash same device but with version v2.0.0 earlier. Is there any anything that I can do as a workaround.
Any help would be great. Thank you

@Cossid How can I generate a firmware dump? if you could please help out with the steps I'll share the dump


docs: Improve perf of Prettier recipe

Codecov Report

Merging #26 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master       #26   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            4         4
  Lines          109       109
  Branches        25        25
=========================================
  Hits           109       109

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 1a9e731...05a8b10. Read the comment docs.

:tada: This PR is included in version 1.1.7 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[Event Request] codeunit 5343 "CRM Sales Order to Sales Order" - multiple publishers

Hello, would it be possible to add OnAfterCopyShipToInformationIfNotEmpty event to codeunit 5343 "CRM Sales Order to Sales Order", like this:
    local procedure CopyShipToInformationIfNotEmpty(CRMSalesorder: Record "CRM Salesorder"; var SalesHeader: Record "Sales Header")
...
          if not IsHandled then
             SalesHeader.Validate(
               "Ship-to Country/Region Code", CopyStr(CRMSalesorder.ShipTo_Country, 1, MaxStrLen(SalesHeader."Ship-to Country/Region Code")));
         SalesHeader.Validate("Ship-to County", CopyStr(CRMSalesorder.ShipTo_StateOrProvince, 1, MaxStrLen(SalesHeader."Ship-to County")));
>         OnAfterCopyShipToInformationIfNotEmpty(SalesHeader, CRMSalesorder); //New Event
     end;

     local procedure SetLineDescription(SalesHeader: Record "Sales Header"; var SalesLine: Record "Sales Line"; var CRMSalesorderdetail: Record "CRM Salesorderdetail")
     var

     [IntegrationEvent(false, false)]
     local procedure OnAfterCopyShipToInformationIfNotEmpty(var SalesHeader: Record "Sales Header"; CRMSalesorder: Record "CRM Salesorder")
     begin
     end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 53936.


minor doc fixes

minor doc fixes in overview.md, index.md

Thanks for the fixes

Your welcome- great project by the way


Improve 'decrypt' function when 'Expand selection to whole line' is disabled

At present, if the 'Expand selection to whole line' option is disabled, then one has to select the entire encrypted text (including the bracketing doubled %s) -- otherwise the Meld Encrypt commands don't appear in the Command Palette.[^1]
It would be better if, when the keys to bring up the Command Palette were pressed, the plug-in

detected when the cursor was located within a block of encrypted text,
selected that block of encrypted text, and then
brought up the Command Palette.

[^1]: I see that this previously was referenced in the following comment in a now-Closed issue: https://github.com/meld-cp/obsidian-encrypt/issues/20#issuecomment-952701683

fixed in v1.5.2

Thank you!  This much- improved functionality -- and the support for password hints -- have inspired me to nominate Obsidian Encrypt as a 'Gem of the Year'.

No problem, it was a good idea.  Thanks for your support too 👍


Add reannotator command

This change adds the reannotator command and Dockerfile to build the image that will be run as part of a k8s Job, to be added in a future PR.

This change is

Thank you!

Part of:

https://github.com/m-lab/uuid-annotator/issues/48


[Backport 1.6.latest] Test ddtrace dependency range (#733)

Backport #733

This is only needed for older versions


feat: introduce system tables about table fragment info

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Resolve #8803 , introduced system tables rw_table_fragments, rw_fragments and rw_actors to expose status, type and distribution information about streaming jobs.
rw_table_fragments

Field
Type
Description

table_id
Int32
Unique identifier of the table fragment

status
Varchar
Status of the table fragment

rw_fragments

Field
Type
Description

fragment_id
Int32
Unique identifier of the fragment

table_id
Int32
Identifier of the associated table

distribution_type
Varchar
Type of distribution for the fragment

state_table_ids
List (Int32)
List of state table identifiers associated with the fragment

upstream_fragment_ids
List (Int32)
List of upstream fragment identifiers

rw_actors

Field
Type
Description

actor_id
Int32
Unique identifier of the actor

fragment_id
Int32
Identifier of the associated fragment

parallel_unit_id
Int32
Identifier of the parallel unit the actor belongs to

status
Varchar
Status of the actor

Checklist

[x] I have written necessary rustdoc comments
[x] I have added necessary unit tests and integration tests
[x] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[x] All checks passed in ./risedev check (or alias, ./risedev c)

Documentation

[x] My PR contains user-facing changes.

Click here for Documentation
Types of user-facing changes
Please keep the types that apply to your changes, and remove the others.

SQL commands, functions, and operators

Release note
Introduce system tables rw_table_fragments, rw_fragments and rw_actors.

Examples in a local run:
dev=> select * from rw_actors;
 actor_id | fragment_id | parallel_unit_id | status
----------+-------------+------------------+---------
     2001 |        2001 |            11000 | RUNNING
     2002 |        2001 |            11001 | RUNNING
     2003 |        2001 |            11002 | RUNNING
     2004 |        2001 |            11003 | RUNNING
     2005 |        2002 |            11000 | RUNNING
     2006 |        2002 |            11001 | RUNNING
     2007 |        2002 |            11002 | RUNNING
     2008 |        2002 |            11003 | RUNNING
(8 rows)

dev=> select * from rw_fragments;
 fragment_id | table_id | distribution_type | state_table_ids | upstream_fragment_ids
-------------+----------+-------------------+-----------------+-----------------------
        2001 |     3001 | HASH              | {3001}          | {2002}
        2002 |     3001 | HASH              | {}              | {}
(2 rows)

dev=> select * from rw_table_fragments;
 table_id | status
----------+---------
     3001 | CREATED
(1 row)


docker info doesn't show Backing Filesystem

Problem:
docker info only shows Backing Filesystem the first time you start a daemon. Every later restart makes the value became empty.
First time you run a daemon:
[root@localhost docker]# docker info
Containers: 0
Images: 0
Server Version: 1.10.0-dev
Storage Driver: devicemapper
 Pool Name: docker-252:3-8464477-pool
 Pool Blocksize: 65.54 kB
 Base Device Size: 107.4 GB
 Backing Filesystem: xfs
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 53.74 MB
 Data Space Total: 107.4 GB
 Data Space Available: 3.213 GB
 Metadata Space Used: 606.2 kB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.147 GB
 Udev Sync Supported: true
 Deferred Removal Enabled: false
 Deferred Deletion Enabled: false
 Deferred Deleted Device Count: 0
 Data loop file: /var/lib/docker/0.0/devicemapper/devicemapper/data
 Metadata loop file: /var/lib/docker/0.0/devicemapper/devicemapper/metadata
 Library Version: 1.02.113 (2015-12-05)
Execution Driver: native-0.2
Logging Driver: journald
Plugins:
 Volume: local
 Network: bridge null host
Kernel Version: 4.4.0-0.rc4.git2.1.fc24.x86_64
Operating System: Fedora 24 (Rawhide)
OSType: linux
Architecture: x86_64
Number of Docker Hooks: 0
CPUs: 1
Total Memory: 973.2 MiB
Name: localhost.localdomain
ID: 4G4C:VRMN:JJSZ:2MVU:PCQD:WQI3:ZD7Y:DBN5:XMMV:UH6G:KX2J:KYPR
Experimental: true
Registries: <IP_ADDRESS>/8 (insecure), docker.io (secure)

Restart the daemon (notice how Backing Filesystem is emtpy):
[root@localhost docker]# docker info
Containers: 0
Images: 0
Server Version: 1.10.0-dev
Storage Driver: devicemapper
 Pool Name: docker-252:3-8464477-pool
 Pool Blocksize: 65.54 kB
 Base Device Size: 107.4 GB
 Backing Filesystem:
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 53.74 MB
 Data Space Total: 107.4 GB
 Data Space Available: 3.213 GB
 Metadata Space Used: 606.2 kB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.147 GB
 Udev Sync Supported: true
 Deferred Removal Enabled: false
 Deferred Deletion Enabled: false
 Deferred Deleted Device Count: 0
 Data loop file: /var/lib/docker/0.0/devicemapper/devicemapper/data
 Metadata loop file: /var/lib/docker/0.0/devicemapper/devicemapper/metadata
 Library Version: 1.02.113 (2015-12-05)
Execution Driver: native-0.2
Logging Driver: journald
Plugins:
 Volume: local
 Network: bridge null host
Kernel Version: 4.4.0-0.rc4.git2.1.fc24.x86_64
Operating System: Fedora 24 (Rawhide)
OSType: linux
Architecture: x86_64
Number of Docker Hooks: 0
CPUs: 1
Total Memory: 973.2 MiB
Name: localhost.localdomain
ID: 4G4C:VRMN:JJSZ:2MVU:PCQD:WQI3:ZD7Y:DBN5:XMMV:UH6G:KX2J:KYPR
Experimental: true
Registries: <IP_ADDRESS>/8 (insecure), docker.io (secure)

Reproduction
OS: Fedora Rawhide which just use devmapper as default and xfs

dnf install docker (this will install out latest fedora-1.10 branch)
systemctl start docker
docker info (this will show xfs as backing filesystem)
systemctl restart docker
docker info (this WON'T show xfs as backing filesystem)

You can actually reproduce it even after the very first daemon startup:

systemctl stop docker
rm -rf /var/lib/docker
systemctl start docker
docker info (this will show xfs as backing filesystem)
systemctl restart docker
docker info (this WON'T show xfs as backing filesystem)

Thoughts
My patch basically is recording the base device filesystem bacause upon code inspection it seems it isn't recorded anywhere so I put it in the metadata and for backward compatibilty I do some checks at initialization time. This patch IS fixing this problem
But
Building and running a docker dynbinary from docker/docker master branch doesn't have this issue, and this is so weird because our fedora-1.10 branch is based on that official branch.
I first thought some of the patches we're carrying are breaking this but I can't find why (if any)

ping @rhatdan @rhvgoyal should I open a bugzilla?

EDIT
This problem is present in docker/docker master as well, I'll move the discussion there at https://github.com/docker/docker/pull/18606
I'll close this one

yes open a bugzilla on RHEL so we can track this.

PR merged upstream, does this still need a bugzilla?

Yes just to let qe know to test it.

After you make the bugzilla, mark it as modified and fixed in docker-1.10.  Is this worth back porting to docker-1.9?  I doubt it.

@rhatdan same, I don't think it needs a backport..It's something pretty specific to people mounting docker socket


Provide Better Exception Message When Serializer is Not Found for Parameterized Content

This issue is for the case when a serializer is not found when parameterized content is enabled on the configuration container.
For reference/context, these default rules were borrowed from this article when I originally developed this feature.  For completeness, the rules are:

Each member must not already be marked as an explicit contract
Must be a public fields / property.
Any public fields (spit) must be readonly
Any public properties must have a get but not a set (on the public API, at least)
There must be exactly one interesting constructor, with parameters that are a case-insensitive match for each field/property in some order (i.e. there must be an obvious 1:1 mapping between members and constructor parameter names)

This issue will serve not only the official spot for discussion/documentation, but also a reference for the exception that is thrown when these rules are not met.

Closing this as this in the current preview.


⚠ Bofrost.at has degraded performance

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

HTTP code: 200
Response time: 2389 ms

Resolved: Bofrost.at performance has improved in 1e5726a.