Webcrypto import errors in 0.29.1

Summary
Problem
webcrypto cannot be imported or is undefined with some bundlers/build tools with webnative 0.29.1.
Impact
Some applications will not be able to use webnative at 0.29.1, depending on the build system or bundler they use if any.
Solution
Unknown. The issue appears to be related to the change over to one-webcrypto and there may be something we can change there.
Detail
Describe the bug
Parcel 2, Webpack 5, and Create React App report errors in the console. (See the screenshots below.)
To Reproduce
Steps to reproduce the behavior:

Clone https://github.com/fission-suite/react-todomvc
Upgrade webnative to 0.29.1 on each branch
npm start for local dev and npm run build for a build in each
Vite should work, but the parcel, webpack, and main branches should fail (main is CRA)

Expected behavior
No errors in the console. The app works and can do TodoMVC things.
Screenshots
CRA local development

CRA build (fails at build time)

Parcel 2 local development

Parcel 2 build

Webpack 5 local development and build

I'm able to fix issues with parcel and webpack with this commit: https://github.com/fission-suite/one-webcrypto/commit/a95b889887ffa557cdaddd2f19cc14a4bec79e56
CRA remains a problem. I'm not sure why it can't import webcrypto at all :zany_face:

"Progress" on CRA:
Directly importing one-webcrypto doesn't work as well (so the issue is not related to a dependency chain like react-todomvc -> webnative -> one-webcrypto, but also happens with react-todomvc -> one-webcrypto).
Importing files within one-webcrypto seems to fix the issue. That is:

import { webcrypto } from "one-webcrypto" fails with "Attempted import error: 'webcrypto' is not exported from 'one-webcrypto'."
import { webcrypto } from "one-webcrypto/dynamic.cjs" fails with an error unrelated to this line
import { webcrypto } from "one-webcrypto/node.cjs" fails with an error unrelated to this line
import { webcrypto } from "one-webcrypto/node.mjs" fails with an error unrelated to this line
import { webcrypto } from "one-webcrypto/browser.mjs" fails with an error unrelated to this line

So it seems like react-scripts just fail to resolve the correct file given one-webcrypto. I have no clue what could cause this. Esp, since if it did resolve anything it would work fine, and it surely isn't package exports related, since we're including both an exports field and a main field in one-webcrypto/package.json.

Okay, more updates. I removed the import "webnative" imports temporarily (leaving all other code & disabling eslint).
Then I added various forms of one-webcrypto imports to see whether CRA can import them:

:x: import { webcrypto } from "one-webcrypto" fails with "Attempted import error: 'webcrypto' is not exported from 'one-webcrypto'."
:x: import { webcrypto } from "one-webcrypto/dynamic.cjs" fails with "Attempted import error: 'webcrypto' is not exported from 'one-webcrypto/dynamic.cjs'."
:x: import { webcrypto } from "one-webcrypto/node.cjs" fails with "Attempted import error: 'webcrypto' is not exported from 'one-webcrypto/node.cjs'."
:white_check_mark: import { webcrypto } from "one-webcrypto/node.mjs"
:white_check_mark: import { webcrypto } from "one-webcrypto/browser.mjs"
:x: import * as oneWC from "one-webcrypto" fails with "Attempted import error: 'webcrypto' is not exported from 'one-webcrypto' (imported as 'oneWC')." (?????)
:white_check_mark: import oneWC from "one-webcrypto" works ????? although it shouldn't?

When I run this:
import oneWC from "one-webcrypto"

console.log(oneWC)

It just prints /static/media/dynamic.30e18fbe.cjs to the console. So oneWC is initialised to a string :raised_eyebrow:

Since react-scripts uses webpack 4, I've tried to get the webpack branch with webpack downgraded to version 4 working.
However, webpack 4's version of acornjs (the javascript parser they use) doesn't understand export * as X from "..." syntax that's used in webnative.
react-scripts probably uses babeljs liberally to transpile the javascript down so that it can be understood by webpack 4. I haven't been able to get that working.

I really want to get 0.29.1 out there, and I still think one-webcrypto is an improvement over what we had before, because now we can use parts of keystore-idb and webnative in nodejs and it might open the door for sveltekit. It also makes it easier for new libraries (e.g. ucans) to adopt webcrypto in a way such that they're already quite "isomorphic" out of the box and in the future we can change one-webcrypto in one place and everyone benefits.
The big downside is not supporting CRA anymore. :confused:
What do you think?

I think the benefits outweigh support for CRA. A future release of CRA might use webpack 5 or another bundler, and we could re-evaluate it then.
Create React App is by their own admission slow to release new versions. In the meantime, we can recommend Vite, Parcel, and Webpack 5, and we have good examples of how to migrate from CRA to these bundlers in the React TodoMVC repository.

I may have prematurely closed this issue, because we may need a new version of one-webcrypto! Feel free to close it if we are good to go.

We have a new version of one-webcrypto: 1.0.3. I've already released it.
We need to merge PRs to upgrade the one-webcrypto version into keystore-idb and webnative, though.
Here's the one for keystore-idb: https://github.com/fission-suite/keystore-idb/pull/61
I'm waiting to merge&release that one so that we can get that into webnative.

https://github.com/fission-suite/webnative/pull/321 fixes the webcrypto import errors.
Turns out the Webpack error was something else. Documented it in a new issue: https://github.com/fission-suite/webnative/issues/323

Closing this, because #321 is merged now.


Add new spinel property THREAD_NEIGHBOR_TABLE and its support in Ncp

This commit adds a new spinel property THREAD_NEIGHBOR_TABLE and its get handler in NcpBase class.

Current coverage is 68.39% (diff: 0.00%)

Merging #742 into master will decrease coverage by 0.85%

@@             master       #742   diff @@
==========================================
  Files           102        101     -1
  Lines         15502      15511     +9
  Methods        2110       2107     -3
  Messages          0          0
  Branches       1858       1863     +5
==========================================
- Hits          10735      10608   -127
- Misses         4173       4314   +141
+ Partials        594        589     -5

Powered by Codecov. Last update c3fc8fb...76194b5


The command 'sfdx commerce:search:start' is not working anymore

Hello,
The sfdx commerce:search:start  command is not working anymore (hitting "not a sf command" error). It was useful for us in the context of our CI.
I have @salesforce/cli/2.36.8 version and I can't downgrade.
I also did not manage to find any updated version in the "sf" command list.
Is there any workaround (else than manually running the search index :) )
Regards,
JP

Hello @JPGrandclementMirakl, can you post the full error message? commerce:search:start is under our plugin so it should still work if you install the plugin. I wonder if it is an internal command that commerce:search:start uses raises this issue.


[FLINK-33463][Connector/JDBC] Revert "[FLINK-33463][Connector/JDBC] Support the implementation of dynamic source tables based on the new source"

Revert "[FLINK-33463][Connector/JDBC] Support the implementation of dynamic source tables based on the new source" based on discussion result of https://github.com/apache/flink-connector-jdbc/pull/117#issuecomment-2139538600

CC @1996fanrui


Allow setting a custom attachments host other than Heroku, which is more convenient for development

When you are running mobile_workflow and testing an App Rail app in your local machine is more convenient to have the option to set a custom attachments host (i.e pointing to your local machine) rather than point to Heroku.

Nice fixture file

Nice fixture file

I will have to remove the Doge regretfully 🐶 😢  because it's a leftover of a test I was trying to implement but I couldn't achieve because I cannot create ActiveStorage::Attachments since there is no database


Add support for CosmosDB emulator

Fixes #140

This PR is in draft state until https://github.com/Azure/azure-cosmos-db-emulator-docker/issues/56 is resolved: we cannot ship a feature we know is broken on some OS. In particular, I can't even test that on my own laptop because I'm facing this bug.


Removing cookies in AJAX response fails

Describe the Bug
When attempting to remove a cookie using Remove-PodeCookie, but from an AJAX request, the Set-Cookie is set but AJAX doesn't update the cookie on the frontend. This is due to Remove-PodeCookie not setting the cookie's Path; A browser will ignore this and treat it as /, but AJAX requires it to be set.
Related Issue
https://github.com/Badgerati/Pode.Web/issues/13
Steps To Reproduce

Set a cookie on the frontend
Wire up a button to use AJAX
In the request's route use Remove-PodeCookie
Note the cookie isn't remove in dev tools

Expected Behavior
The cookie should be expired/removed
Platform

OS: Windows
Browser: Chrome
Versions:

Pode: v2.0.3
PowerShell: v5.1

LGTM

LGTM


Reactome release 85 models

Drop-n-reload of all Reactome models using latest release 85 BioPAX data. More details in https://github.com/geneontology/reactome-go-cams/pull/11.

Will start reviewing these. Thanks @dustine32


sideNav: rename md-sidenav-layout

Bug, feature request, or proposal:
Current implementation uses md-sidenav-layout as the smart container for content and md-sidenav components. The -layout suffix is ambiguous and conflicts with names and concepts for the Material Layouts API and features.
What is the expected behavior?
Please rename to md-sidenav-container
What is the current behavior?
What are the steps to reproduce?
Providing a Plunker (or similar) is the best way to get the team to see your issue.
Plunker template: http://plnkr.co/edit/o077B6uEiiIgkC0S06dd
What is the use-case or motivation for changing an existing behavior?
The -layout suffix is ambiguous and conflicts with names and concepts for the Material Layouts API and features.
Which versions of Angular, Material, OS, browsers are affected?
Is there anything else we should know?

@hansl @kara any thoughts on this? I'm not convinced on the name change since we don't have any layout concepts in material2 for this to conflict with. I like the name now because I see it as more accurately capturing the intent of setting up a sidenav layout for your app (sidenav + main content area).

I'd rather have a proper layout engine in material2 and get rid of md-sidenav-layout. In the meantime, I agree with Thomas that container is more proper.

@jelbourn - Also Angular Layouts is in active development and will be ready in the fall for Angular 2 apps and Angular Material 2.

@mmalerba I want to follow up on this with some more discussion

Agreed with Thomas & Hans that container > layout. I'd also like to switch sidenav to drawer. A sidenav is only one possible use of the drawer component, so I propose: md-drawer-container and md-drawer

renamed to md-sidenav-container in #2183


Request - Add a license file to this repository

Please add a license to your code so we can try using it

Done, thanks for your suggestion.


Rails is not loaded in my spec_helper.rb

I'm using simplecov with my rspec suite, so I want to eager load all my application code so that my coverage stats actually include all the code in my application. Knapsack worked fine before I added the eager loading to my spec_helper, but once I added this, my test suite crashes because Rails is not defined:
in spec_helper.rb
if ENV['UPLOAD_CODECOV']
  require 'simplecov'
  require 'codecov'
  SimpleCov.start 'rails' do
    formatter SimpleCov::Formatter::Codecov
  end

  Rails.application.eager_load!
end

I get this error: uninitialized constant Rails (NameError).
I'm running Knapsack like this: bundle exec rake knapsack:rspec. Also tried with knapsack_pro, with the same results.
Any idea why Rails would not be defined here? Without this line, the specs will run, so at some point in the process Rails does get loaded, just not in my spec_helper.rb.
Thanks!

 Wonder why it worked before, perhaps in the standard configuration it happens to load the app earlier anyway.


Fix #16593 and fix bug introduced in #16607

The regex now handles array syntax, with/without 'or' nicely.
I've added tests to verify that this fixes #16593 .

👏 That was quick.
I see that you are testing for both
$name["key or space"] or "foo"
$name["key"] or "foo"

Seems good.

Can you explain this regex in plain English?

Are you sure the two greedy .+ you have added aren't problematic?

@vlakoff There are unit tests which cover all possibilities, and they pass, so I dont think they're going to cause any problems now. If there are more cases in your head, let me know.

This is the regex : ^(\$.+(?:\[[\'"].+[\'"]\])|[^\[\]\'"]*)(?:\s+or\s+)(.+)$
Breaking it into three parts :

(\$.+(?:\[[\'"].+[\'"]\])|[^\[\]\'"]*) : This gets captured in group #1 $1.
Match things that start with a $ then followed by 0 or more characters (.+) then followed by either

(?:\[[\'"].+[\'"]\]) : String that opens with [' or [", then contains characters (using greedy here makes sure the regex doesnt return too early), and then '] or '"]'. This matches the array access statements.
[^\[\]\'"]* : String that is empty, OR, do not contain any of [, ", '. This matches anything except the array access statements.

(?:\s+or\s+)  : Matches or, that is, or with whitespace characters around it.

(.+) : This gets captured in group #2 $2. Matches any characters after or.

Going to hold off on this for now on 5.3 as it's fairly edge case and I don't want to break things again on a minor release.

Another case to think of, and test, would be dynamic variable names:
$foo = new \StdClass;
$foo->bar = 'content';
$dynName = 'bar';

{{ $foo->{$dynName} }}


unable to install library: No such file or directory: 'requirements.txt'

error: subprocess-exited-with-error
× python setup.py egg_info did not run successfully.
│ exit code: 1
╰─> [9 lines of output]
Warning: passing language='c++' to cythonize() is deprecated. Instead, put "# distutils: language=c++" in your .pyx or .pxd file(s)
Traceback (most recent call last):
File "", line 2, in
File "", line 34, in
File "C:...\AppData\Local\Temp\pip-install-syl2p25o\tseries-patterns_1ba9bee249ce4da2b7742e9c39f3411c\setup.py", line 45, in
install_requires=requirements(filename="requirements.txt"),
File "C:...\AppData\Local\Temp\pip-install-syl2p25o\tseries-patterns_1ba9bee249ce4da2b7742e9c39f3411c\setup.py", line 29, in requirements
with io.open(filename, encoding='utf-8') as f:
FileNotFoundError: [Errno 2] No such file or directory: 'requirements.txt'
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.

I have not installed this on windows (only linux and osx).  That said others have been able to install on windows.   Are you using conda as your python distribution?   Also do you have Cython installed?

I was able to install on windows about a year ago using a different environment. I did install Cython this time around following an initial error.
I am using:
conda 4.11.0
Python 3.10.2

Windows environments are very challenging (where this stuff "just works" on unix based systems).   If you have changes you want to make to the library to get it to install for you, happy to accept.   I don't run windows, so I can only guess as to what you might need to change.

ok thanks for offering to update, though I am not sure what needs to be addressed at this stage. If I come up with something I will let you know.


Dependency Updates

Dependencies in lots of the sub-libraries are specified as absolute numbers down to the patch. This can pose problems when new versions of the libraries are released or the downstream user needs to use an older one because of various reasons.
For example, in Cargo.toml of futures-curl, the version string of curl should be changed to 0.3 if that works. If not that then ^0.3.3 since 0.3.4 is already out. At the moment I'm unable to compile by specifying 0.3.4 in the Cargo.toml of my binary because of a version conflict. Similarly, the version of crossbeam in futures-cpupool should be changed to ^0.2.10. Same for scoped-tls and slab in futures-mio. And the Cargo.toml of futures itself specifies the version for various sub-libraries as 0.1.0 whereas the sub-libraries reference futures as 0.1. I think the former should be changed to 0.1.

Thanks for the report! The syntax here is actually I think special to cargo where = "1.2.3" is by default a caret requirement. This means that a dependency of = "0.3.3" is actually the same as = ">= 0.3.3, < 0.4.0".
I'm surprised though that you weren't able to use 0.3.4? If you run cargo update -p curl it should pull it in automatically, but was that not happening?

My bad. I didn't run cargo update but just ran cargo build expecting it to function. Apologies.


Workspaces with Gateway API

Description
Addresses #4849
How Has This Been Tested?

[ ] Test A
[ ] Test B

Checklist

[ ] The PR is tagged with proper labels (bug, enhancement, feature, documentation)
[ ] I have performed a self-review of my own code
[ ] I have added unit tests that prove my fix is effective or that my feature works
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] If new documentation has been added, relative paths have been added to the appropriate section of docs/mint.json

Tasks

[x] [backend] Create HTTP Route
[x] [backend] Delete HTTP Route
[ ] [frontend] Visualise options (Ingress vs. HTTPRoute/GatewayAPI
[ ] [frontend] Form for HTTP Route options
[ ] [frontend] Submit with HTTP Route options

also here is where you would want to update the frontend:
https://github.com/mage-ai/mage-ai/blob/fa8ce2850c0fa1420d64a257d21e4b5ffffa563b/mage_ai/frontend/components/workspaces/ConfigureWorkspace/index.tsx#L203


Add note about async initialisation of tokens in K8S

When used in Kubernetes, I observed a persistent failure with an error message like this:
org.zalando.stups.tokens.AccessTokenUnavailableException: No token available for
tokenId 'someToken'. Tokens are available for the following tokenIds [someToken]

This has the look of a race condition about it. After I raised the issue on an internal Zalando chat channel, Alexey Ermakov provided a helpful explanation:

unfortunately the tokens library initialises asynchronously by default on Kubernetes (but synchronously on STUPS, even though it's much more expensive), so the first couple of calls will fail.

The PR adds an example to the README with a single line of code shared by Alexey which forces the filesystem refresher to initialise and validate the tokens immediately on startup, which avoids this issue.

(Closing since I couldn't set the target to upstream here, and just opened a new PR directly upstream)


feat: Ability to add a SubtitleHeaderComponent to the scrollables that doesn't impact when the HeaderComponent is shown

Feature Request
Hi there 👋 Thank you so much for the great library - really appreciate the work.
Ability to add a SubtitleHeaderComponent that renders underneath the LargeHeaderComponent that doesn't impact when the HeaderComponent is shown.
Use Case
While you can add a subtitle or similar to the LargeHeaderComponent, if it is several lines of text, it can look odd as the HeaderComponent doesn't render until all the subtitle text has scrolled by. Thus, it looks more natural to show the HeaderComponent as per the current expectation but the SubtitleHeaderComponent outside the onLayout changes.
The above impacts primarily the FlatList, FlashList and SectionList components containers as ideally, you would want the subtitle within the ListHeaderComponent, however, I think for consistency of types, it would be very easy to add to ScrollView as well.
Proposed Solution

Update SharedScrollContainerProps to include SubtitleHeaderComponent as an optional React.ReactNode
Update FlatList, FlashList, SectionList and ScrollView to add a fragment around LargeHeaderComponent to add {SubtitleHeaderComponent && SubtitleHeaderComponent} within the same fragment.

Additional Information
I am happy to raise a PR for you to review this if you open to this addition 👍

Hey there, thanks for opening this feature request! For the initial problem, you can use the headerFadeInThreshold prop to render the header a bit earlier.
In order to do this correctly, you will have to do some math:

Compute the height of the large header
Find the y position of the component you want to begin fading the header in at
Interpolate the y position and height of the larger header to produce a value between 0 and 1
Use this as the headerFadeInThreshold prop

This is somewhat complex, I know, but I added the prop for these kinds of use cases. I will think more about this feature request in the meantime.

HI @aharwood9, I have reviewed this change and would love for you to help with this. The proposed solution is fine, I just want to clean up the API if we move forward with this. SubtitleHeaderComponent seems a bit ambiguous as a name - it's not clear that this is under the LargeHeaderComponent. Do you have any suggestions for this?

That's great news! I would love to get rid of my patch. I am happy to raise a PR for you to review. In regards to a name, (I am never good at this) but some ideas -

SubtitleHeaderComponent - current
SubtitleLargeHeaderComponent
LargeHeaderSubtitleComponent?
LowerLargeHeaderComponent
LargeHeaderDetailComponent

I don't love these - do you have any preferences?

Eh, something like LargeHeaderSubtitleComponent or LargeHeaderFooterComponent would be better. Also, an update to the docs will be necessary for understanding the overall visualization of how the library works (some chart with each header type stacked on each other). If you would like to get a PR up, feel free to.
Keep in mind that we should probably supply some properties to this new component:
{SubtitleHeaderComponent && SubtitleHeaderComponent({ showNavBar, scrollY })}

Okay! Will have a crack tomorrow. I am not super familiar with docusaurus so will get a PR up for the code changes and then have a go at updates to the docs.


unmasking value incorrect

THIS:
"<script type="text/javascript">$("#x_B_Offer_Price").maskMoney({thousands:',', decimal:'.', precision: 0, allowZero: true, allowNegative:false, prefix: ' $'});";
example: $900,000 input
when unmasked:
var num = $('#x_B_Offer_Price').maskMoney('unmasked')[0]; alert('type: '+ typeof(num) + ', value: ' + num)
results in: 900 NOT 900000

This is an important issue. Perhaps the most important. I am running into this as well. The problem occurs when there is no decimal point included in the source number. This occurs regardless of whether or not a decimal character has been set up in initialization.
Please see my codesandbox for a working example of the issue: https://codesandbox.io/s/rlq0r8jwwn

Yeah this is some wonky behaviour. Completely unexpected. If the precision is zero, the unmasked output should an integer, always.


Add WSGI support

This PR adds a pure WSGI application to vulnpy. This works a little differently from using a real framework, since routes aren't registered ahead of time - instead, on each request we parse PATH_INFO and delegate to a trigger function accordingly.
To test this out live, stand up the WSGI app with make wsgi.

Good to know the OSSAR scan is doing its job. Safe to say we should not block this merge on that failure, so do what you need to do to make it not fail the pipeline, not sure if you need to update the .yaml file or just some setting in GH UI.

@danilito19 from what I can tell, this is still due to the fact that ossar-action is still using set-env. Should I temporarily disable the action?

@lazorchakp ah yeah looks like you're right (I just saw the warnings for scanning in the run). Disable it and make a ticket for re-enabling them after whatever issue / PR they may have to fix it is done (if there is one). If not we'll have to check in a month or so

oh @lazorchakp you know what, looks like you can still merge sooo just leave it enabled for now? should go away sometime

@danilito19 yeah, it's not merge-blocking. sounds good to me 👍


Airflow scheduler stops when Kubernetes Quota is exceeded

Right now, if a scheduler running the KubernetesExecutor attempts to schedule a pod into a namespace that would put it over a resource quota, the scheduler logs the error, then quits scheduling tasks. The scheduler does not crash or anything, just stops scheduling.
Seems like we need a way to more gracefully deal with situation.

@ashb any thoughts on the behavior here? I believe the exception gets thrown here: https://github.com/apache/airflow/blob/master/airflow/contrib/kubernetes/pod_launcher.py#L59.
I'm not sure if there's a more specific exception we could look for and handle differently or not.

@ashb @schnie
This bug has been fixed using pull/3960 and released in 1.10.3 CHANGELOG.txt#L181
Issue in Jira: https://issues.apache.org/jira/browse/AIRFLOW-2966
I checked status of fork and tag:
https://github.com/astronomer/airflow/blob/v1-10-2/airflow/contrib/executors/kubernetes_executor.py#L651-L653 we don't have this change on production.
Regarding PodOperator - i think behavior is looks correct.
Please let me know what to do next.

@schnie
I think we can close it after releasing https://github.com/astronomer/airflow/tree/v1-10-3


close DATA to prevent strange addendum in subsequent error messages

Summary
As reported on IRC (and indeed I've seen it too, just not had the inclination to look) there is a message appended to error messages saying ", at DATA line 2231".
Motivation
Closing the DATA handle after using it in Mojo::Util suppresses this addendum.
References
http://irclog.perlgeek.de/mojo/2016-08-15#i_13025043

Doesn't the DATA section code in Mojo::Loader still cause the same kind of warnings?


Implement Control Flow

if-then-else
ternary ?:
while
do-while
for
foreach (compounds)
continue
break
switch-case-default (and continue?)

Potential Opcodes:

JUMP
JUMP_CONDITIONAL (true/false)

I'm not sure how a switch statement could be done efficiently, so it'll need research.

I did some thinking about this yesterday.
https://github.com/Ratstail91/Toy/blob/v2/.notes/control-flow-opcodes.txt

I started working on if-then-else a few days ago, but the tests aren't finished yet due to unrelated bug hunts.
34577ecfe11641eabb9bf61f76e026336f32dc89

The control flow for break and continue requires arrays to keep track during compilation, so #155 needs to be finished first.

For break/continue keywords:
instruction:
	ESCAPE opcode
	ADDR   target
	UNWIND number of scopes to unwind

continue data: (point each keyword to the innermost position)
	current depth
	list<(addr, depth)> continues

break data: (wait unto the addr is found, then go back and set the keywords' parameters)
	current depth
	list<(addr, depth)> breaks

Therefore, the following structure is needed:
struct Escape {
	unsigned int addr;
	unsigned int depth;
};

Could wrap this in a reallocate function too, similar to Toy_Array.


vim: add option programs.vim.settings

This option gathers basic Vim settings into a single place. The idea is to allow many options without making the Home Manager documentation too verbose. A screenshot of the man page shows that the documentation is quite compact so it should be possible to squeeze in quite a few settings:

Note, it's been a along time since I used Vim regularly so I cannot vouch for the validity of setExpr.

I don't know whether programs.vim.lineNumbers and programs.vim.tabSize should be deprecated. In the commit above I changed them to use the new settings mechanism.

CC @paluh

Looks very good! I just tested it and it works fine for mine configuration. However, I've encountered a couple of issues:

Seems like options defined by the user in the settings parameter have lower priority than same options defined in external plugins. I would guess that extraConfig is executed before plugins code. If that's the case, it should probably be fixed in nixpkgs and nothing we can do here.
There is interesting behavior when there is line set nocompatible in extraConfig. In this case, it seems like none of the options defined in settings are applied. It works after removing this line though. Interesting that when I added compatible = types.bool to settings and set compatible = false, everything worked as it should.

The configuration I used for testing (setting history to <1000 will result in history=1000 due to sensible.vim#L72, so plugins have higher priority):
  programs.vim = {
    enable = true;
    settings = {
      history = 10000;
    };
    extraConfig = ''
      "set nocompatible " with this line commented history=50, otherwise history=10000
    '';
  };

As for programs.vim.lineNumbers and programs.vim.tabSize parameters, I think we should deprecate them (probably create a news entry with condition programs.vim.enable && programs.vim.tabSize != null && programs.vim.lineNumbers != null), but keep for a while to give users enough time to switch to a new programs.vim.settings parameter.

This looks really great - thanks again @rycee!

Seems like options defined by the user in the settings parameter have lower priority than same options defined in external plugins(...)

I'm not sure about that @uvNikita - I don't fully understand modules structure in nixpkgs/applications/editors/vim, but it seems that finally in vim-utils.nix where customRC is used it is added at the end of a file.

There is interesting behavior when there is line set nocompatible in extraConfig (...)

I've checked it too and it seems that you are right. This behavior is even documented :-)
:help compatible

(...)
This is a special kind of option, because when it's set or reset,
other options are also changed as a side effect.
(...)

I think that it is quite unfortunate, because it shows that even basic config is no really declarative in vim and when we add compatible to settings the place where final nocompatible lands in generated vimrc is significant...
This of course would also interact with plugins setup and this is probably the reason why in vim-utils.nix we can find that final configuration has shape:
" minimal setup, generated by NIX
set nocompatible

${vamImpl}
${pathogenImpl}
${vundleImpl}
${neobundleImpl}
${nativeImpl}

filetype indent plugin on | syn on

${customRC}

I'm not sure why they put syn on after plugin setup, because it can also reset some parts of the config (related to highlighting), but I think that it is topic for separate discussion/question in nixpkgs...
So maybe we should not cover options like compatible and syntax in our settings as their are order dependent and can affect other options and we are not able to order them as user wants to. Probably we should also clearly state how final config would look like - as far as I understand it now goes like that:
''
set nocompatible

${ plugins setup }

filetype indent plugin on | syn on

${ settings setup}
${ extraConfig }
''

I've cleaned up the PR a little and deprecated the programs.vim.tabSize and programs.vim.lineNumbers options. I'm not sure what else to do about this PR, I'm not very motivated to spend more time on it since I'm not actually a Vim user :-)
Please have a look, if it seems OK then can rebase to master. If there are more things to do then feel free to take over this branch and fix any remaining issues.

Sure, thank you for looking into it @rycee! Rebased into master: https://github.com/rycee/home-manager/commit/aa974c0dc3a27c2d68a9777a6554f67be5a80fdd.


APK crashes on startup

Hello, i have been trying to make the app work but it always crashes. I tried this on youtube 2.1.6
I changed the padding and the api like this:
const-string v0, "AES/ECB/ZeroBytePadding"
const-string v0, "http://<IP_ADDRESS>/youtube/accounts/registerDevice?developer=%s&serialNumber=%s"
const-string v1, "http://<IP_ADDRESS>/"
const-string v1, "http://<IP_ADDRESS>"
The port my yt2009 is on is 80 so i dont know what i did wrong

don't put http/full path where "gdata.youtube.com" was. just the ip/domain. in your case
const string v1, "<IP_ADDRESS>"

don't put http/full path where "gdata.youtube.com" was. just the ip/domain. in your case
const string v1, "<IP_ADDRESS>"

Ok i did this. The app doesnt crash anymore but many things dont work like
-things that work
-searching
-visiting channels
-things that dont work
-videos
-homepage
-comments
In cmd when i the homepage tries to load it throws an error but when i try playing a videi it just keeps loading and no error message appears

make sure you've entered your ip in config.json right. the app depends on it to get things like video comments and video playback itself.
it NEEDS to be an ip your device can reach. try experimenting with your local ip/external if public instance.
you can modify the config.json and restart yt2009 to do that. no need to redo yt2009setup.

by the lack of response i'm assuming this isn't a problem anymore. closing. feel free to reply/create a new issue if needed.


⚠ Bofrost.lu has degraded performance

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

HTTP code: 200
Response time: 2044 ms

Resolved: Bofrost.lu performance has improved in df3c7fe after 16 minutes.


Rust rewrite

Just looking, isn't it fun.

Completed via https://github.com/tedious-tools/asdfler/commit/23ea5ec3de974b72d03be34022f109a8fd6454b7


Error: [zephyr reporter] "projectKey" is required when using cypress-multi-reporters

To delete

Hey @leo-coco
Do you have any issues with the plugin? I'll close it. Feel free to reopen with more details


[PE-D][Tester A] Silent ignoring of n/ in edit command

Based on the UG, the edit command should not allow for name changes. However, when i input a name such as the one shown in the command, which does not follow their command format, it still edits the corresponding phone number but not the name. Perhaps this should throw an error instead, to tell the user that they cannot edit the name, instead of silently ignoring it.
Input

Result

Labels: type.FeatureFlaw severity.Medium
original: ChongWeiJie29/ped#4

This issue is fixed by PR #245 .


feat(monitoring): add epsagon tracing

Please ensure your pull request adheres to the following guidelines:

[ ] make sure to link the related issues in this description
[ ] when merging / squashing, make sure the fixed issue references are visible in the commits, for easy compilation of release notes

Related Issues
Thanks for contributing!

Codecov Report

Merging #29 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master    #29   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           1      1
  Lines           3      4    +1
=====================================
+ Hits            3      4    +1

Impacted Files
Coverage Δ

src/index.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Added resource url function + tests

Waiting on an internal change to merge this.

@AaronLaBrie do we raise any errors if a bad url is passed or if the request fails?  I suppose this will bubble up and the dev will be able to .catch() them, but it might be nice to know where the error occured

@tantona It'll just hit the api and throw back whatever it does. This should only be used for resoure_url's returned from our calls, so there shouldn't be issues there.
If people want to do their own thing with it, and it breaks, that's their problem.

:+1:


[task] Requested enhancements to release automation

This issue is simply to track a small set of discrete tasks which emerged from the first attempt to run the release pipeline:

[x] Allow the check for whether or not master branch tests are passing to be skipped via a runtime configuration flag.
[x] If the changelog needs to be updated, allow for that during the pipeline execution.
[x] Review change for git pull in branch creation script and see if they can be improved.

Done via https://github.com/elastic/apm-agent-java/pull/1289


non dll-interface class 'boost::noncopyable_::noncopyable' used as base for dll-interface class 'boost::contract::detail::checking'

This is from a teeks msvc 14.2 build that boost-ci doesn't have in it yet.  Likely all other windows builds are issuing the same warning however.
https://www.boost.org/development/tests/master/developer/output/teeks99-07-v16ml-64onAMD64-boost-bin-v2-libs-contract-test-specify-auto_error-test-msvc-14-2-dbg-adrs-mdl-64-thrd-mlt.html
D:\teeks99-07\run\boost_root\boost/contract/detail/checking.hpp(26): warning C4275: non dll-interface class 'boost::noncopyable_::noncopyable' used as base for dll-interface class 'boost::contract::detail::checking'
D:\teeks99-07\run\boost_root\boost/core/noncopyable.hpp(38): note: see declaration of 'boost::noncopyable_::noncopyable'
D:\teeks99-07\run\boost_root\boost/contract/detail/checking.hpp(24): note: see declaration of 'boost::contract::detail::checking'

I fixed quire a few warnings in develop (but I haven't merged into master yet). Looking at the test matrix for develop I don't see warning for msvc-14.2:
https://www.boost.org/development/tests/develop/developer/contract.html
The link above is from master. Is the warning C4275 above from develop or master?

Looks like it was from master.

This should be fixed in develop.


Clean some "unchecked" warnings

Unhappy compiler 😉

Ok, everything is passing now. Should be good to go


Added qod-0.8.0 API doc

https://github.com/camaraproject/QualityOnDemand/issues/58

Incorrect PR


Errors from validation not structured as expected when using translations

Laravel Version: 6.5.0
PHP Version: 7.2.4
Database Driver & Version: Mysql 5.7

Description:
When a validation fails using a file upload with this constraint :
'document' => 'required|mimes:pdf,jpg,jpeg,gif,png|between:1,2000',

errors in session are stored like this :
debug(\Session::get('errors'));

ViewErrorBag {#2297 ▼
  #bags: array:1 [▼
    "default" => MessageBag {#2298 ▼
      #messages: array:1 [▼
        "document" => array:1 [▼
          0 => "The document must be between 1 and 2000 kilobytes."
        ]
      ]
      #format: ":message"
    }
  ]
}

but when I use translations in resources/lang/en/validation.php file :
'custom' => [
        'document' => [
            'between' => [
                "file" => "My message overide",
            ],
        ],
    ],

Errors are stored like this :
ViewErrorBag {#2298 ▼
  #bags: array:1 [▼
    "default" => MessageBag {#2299 ▼
      #messages: array:1 [▼
        "document" => array:1 [▼
          0 => array:1 [▼
            "file" => "My message overide"
          ]
        ]
      ]
      #format: ":message"
    }
  ]
}

Why 0 is not the key of "My message overide"?

Hi there,
Thanks for reporting but it looks like this is a question which can be asked on a support channel. Please only use this issue tracker for reporting bugs with the library itself. If you have a question on how to use functionality provided by this repo you can try one of the following channels:

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

However, this issue will not be locked and everyone is still free to discuss solutions to your problem!
Thanks.

For me it's a bug, I made a question to be kind..

Found solution, it needs to be write like this :
'custom' => [
        'document' => [
            'between' => "My message overide",
        ],
    ],


Grammar correction

Worlds smallest PR.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Remove references to "sync"

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/excel/custom-functions-json.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


SWARM-1107: Change the type of SecuredArchivePreparer to List<Map<Sting, Object>> for non main() way

[x] Have you followed the guidelines in our Contributing document?
[x] Have you created a JIRA and used it in the commit message?
https://issues.jboss.org/browse/SWARM-1107
[x] Have you checked to ensure there aren't other open Pull Requests for the same issue?
[x] Have you built the project locally prior to submission with mvn clean install?

Motivation
Thanks to SWARM-1047, you can get the data in a full list/tree shape
akin to the YAML itself. Now List of Map in yml is injected as List.
Thus, org.wildfly.swarm.keycloak.runtime.SecuredArchivePreparer.securityConstraints
should be List<Map<String, Object>> instead of List and then it enables
to setup the Security Constraints without main().
Modifications

Change the type of SecuredArchivePreparer.securityConstraints to List<Map<String, Object>>
Remove unnecessary Parser for converting Map in yaml to String

Result
You can setup Keycloak Security Constraints without main().

add to whitelist

add to whitelist

retest this please

retest this please

@gastaldi Thank you for your revewing!
I'd like to think about your comments, please hold this.

Hmm, the failure is weird. I don't think it's related to my changes.
https://ci.wildfly-swarm.io/job/wildfly-swarm-pull-request-windows/org.wildfly.swarm$testsuite-management-console/195/testReport/junit/org.wildfly.swarm.management.console/ManagementConsoleTest/testHomePageShouldHaveCorrectTitle/

you're right @emag it's not.
Do you still want this held or we can merge?

@kenfinnigan Thank you! I got it. Please merge this PR.


WIP: Test Framework logging scopes refactoring.

BLOCKED ON: https://github.com/istio/istio/pull/8729

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: ozevren
If they are not already assigned, you can assign the PR to them by writing /assign @ozevren in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pkg/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ozevren: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
4dafe6dbd441f2fbd76684c129c0e59d5040051c
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ozevren: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests.sh
8287cadd8c26a35db6ae7b399b71e2779a3737af
link
/test e2e-simple

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ozevren: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
a464e22eac41d3ed2146ea224ad41ba50a44fe48
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ozevren: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
616c34191736bdaa1735599db8337b4ea3da5dc8
link
/test e2e-bookInfo-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test e2e-bookInfo-envoyv2-v1alpha3

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: nmittler
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pkg/OWNERS [nmittler]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ozevren: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
cd71dbc683301ba0dc2584398a73f5ee829368ca
link
/test e2e-bookInfo-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test e2e-bookInfo-envoyv2-v1alpha3

@ozevren that test appears to be broken for everyone ATM.

sigh

yup ... I just posted to oncall on slack

@ozevren: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
cd71dbc683301ba0dc2584398a73f5ee829368ca
link
/test e2e-bookInfo-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Design a new preloader for CodeIN Community

Description
Design a new preloader CodeIN Community's theme
Screenshots
No response

I would like to take this issue. Please assign it to me .

heyy.. i would love to work on this preloader.

@sanvisharma003 Go for it!

can you send me the current preloader of the community so that i could start working?
i cant find one.

There is a preloader folder there in our repository, Also while reloading the website you can see the preloader.

For support join our discord server: https://discord.com/servers/codein-community-831388874118660156


Added Cmdlet reference for Portal Launch Scheduler Commands

The addition is for the following Cmdlets which are used to schedule a portal launch waves
Get-SPOPortalLaunchWaves
New-SPOPortalLaunchWaves
Remove-SPOPortalLaunchWaves
Set-SPOPortalLaunchWaves
Also update the TOC under SharePoint-Online

Docs Build status updates of commit d98cb67:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOPortalLaunchWaves.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/New-SPOPortalLaunchWaves.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOPortalLaunchWaves.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Set-SPOPortalLaunchWaves.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/sharepoint-online.md
:white_check_mark:Succeeded
View (sharepoint-ps)

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

Docs Build status updates of commit 28fb97c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOPortalLaunchWaves.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/New-SPOPortalLaunchWaves.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOPortalLaunchWaves.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Set-SPOPortalLaunchWaves.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/sharepoint-online.md
:white_check_mark:Succeeded
View (sharepoint-ps)

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

Waiting more review on the rollout of the commands.

Docs Build status updates of commit 28fb97c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOPortalLaunchWaves.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/New-SPOPortalLaunchWaves.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOPortalLaunchWaves.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Set-SPOPortalLaunchWaves.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/sharepoint-online.md
:white_check_mark:Succeeded
View (sharepoint-ps)

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


v-model variable updated after @update event is sent

If I have:
    <VueDraggable
      v-model="list"
      @update="listUpdate"
    >

I expect to see the updated list in my listUpdate method. But list gets updated after listUpdate is called, forcing me to use a setTimeout(func, 0) or Vue.nextTick(func) hack to see the updated variable. It would be better if the new updated variable was available when @update fires.
So I expect this to show what is now the first element, but in fact it will show the first element before i sorted them:
  methods: {
    listUpdate() {
      this.firstElementInUpdate = this.list[0]
    }
  },

And this will show the new first element as I expect:
  methods: {
    listUpdate() {
      nextTick(() => {
        this.firstElementInUpdate = this.list[0]
      })
    }
  },

See https://vue-pys8h3.stackblitz.io for a full reproduction.
Some other way to get the new value of list from listUpdate would also be good. The sortable doc says to access it as evt.to, but then I get the updated DOM node, where I want the Vue model variable.
This reproduces in 0.1.3 and 0.1.5. 0.1.4 didn't work.

Some other way to get the new value of list from listUpdate would also be good. The sortable doc says to access it as evt.to, but then I get the updated DOM node, where I want the Vue model variable.

Hi, I have fixed this issue in 0.1.6, thanks for your feedback.


v4.0

Design
Module
// ESM
import { nwbuild, options } from "nw-builder";
// CJS
const { nwbuild, options } = require("nw-builder");

const { run, build, package } = nwbuild({ ...options, version: "0.64.1" });

run()
  .then()
  .catch()
  .finally();

build()
  .then()
  .catch()
  .finally();

package()
  .then()
  .catch()
  .finally();

CLI
nwbuild ./path/to/nwapp --version=0.64.1

package.json
"nwbuild": {
  "version": "0.64.1"
}

The nwbuild function would check package json and default to it if the nwOptions field exists in a package.json. If no package.json exists, then the default is API/CLI (in the order it is executed).

version: 0.64.1 is a syntax error, I assume it should be version: '0.64.1'.

version: 0.64.1 is a syntax error, I assume it should be version: '0.64.1'.

Yup, fixed

What is options in this example. It is provided by the nw-builder module, and then passed back in to it? Is it just an object of the default options used internally? Why pull it out, just to pass it back in? Ultimately, you'll still need to validate what inputs are passed in by the user, and default options not passed in. So why not handle that in the same step?
My process for library API's is usually:

Create a dummy object with all default options already set
Take in the user's object
Validate each part of the user's object is correct
If a user option is valid, then override the property on the dummy object
If it isn't valid, then use the default, and log helpful, human readable message explaining why their input was invalid (must be a number, must be an array of booleans, must be one of these 3 specific strings, etc)
Then carry on trying to perform the operation based on whatever properties are in the dummy object (if possible).

I usually just put all that in a validation.js file that always returns a valid options object, and have that be the first thing called. From that point on, all of my library code is free from safety checks and can safely assume that all values exist, are the correct type, and compatible with the logic in the library. It's a lot of extra work upfront, but it separates this validation step and the unit tests for it from the rest of the code. Often times this validation step ends up with more code than the rest of the actually library code, which just goes to show how much complexity there is involved with taking inputs from unknown sources. It's worked well for me on my libraries. Ultimately, the only way to be sure something will work in JavaScript, is to validate it at runtime.
Example:

library.js = 308 lines
validation.js = 644 lines

What is options in this example.

The current design is a draft. I agree that there's no point in passing options in again. But before changing it I wanted to come up with something better. For example:
const { run } = nwbuild(
  version = "0.64.1",
  flavor = "normal" // default value of "sdk"
  ...
);

Something like this with reasonable defaults. I like separating the validation and library logic approach - I've seen it in a few places and it's worked well.

It's a lot of extra work upfront, but it separates this validation step and the unit tests for it from the rest of the code.

Feeling that rn lol. It's definitely more work but worth the effort.

Most of the code is based on the assumption that you download from dl.nwjs.io. How can we make the code independent of this?


i have added two different cluster but only one seem to be effective , why? is it like this

https://github.com/Leaflet/Leaflet.markercluster/blob/master/CONTRIBUTING.md#reporting-bugs


menu scene + backspace interaction

hold colors don't reset when going back to the menu scene. going from music -> menu, all the holds are teal

This is related to several issues. There is a new flow for the holds. The Hold GameObjects that are passed from scene to scene should be essentially containing only position and scale. Add child game objects to the hold in order to add more functionality. This would include rendering the display of the hold (Line Renderer or Sprite Renderer) and putting specific hit boxes (colliders). This style is very standard Unity as it keeps functionality separated so it doesnt interfere.
That said for now and for the demo we are going to start by using this method to abstract the sprite rendering to a child object. This is in fact a necessity in order to get the sprite to display properly without affecting the colliders.
To work with the current set up, expect hold game objects to have a line renderer (to display the circles as we usually do) and the necessary colliders. Nothing here has changed!!!!
If we have time and certainly in the future we should work to move thjis functionality into child objects.
If you want to add a sprite you must explicitly to so by adding a child object. There will be no Sprite Renderer attached to a hold itself. You can use a prefab and we can write a helper method for this.
IMPORTANT!!!
This method means that at the end of a scene, all children of a hold object are destroyed, the line renderer is disabled, and all scene specific scripts attached to the hold are destroyed. The developer must ensure these tasks are handled as they do not happen by themselves.
At the beginning of a new scene, it is up to the developer to enable the line renderer and set the color if they desire a circle drawn for a particular hold.
SEE Menu.cs for an example of how things should be called
The drawing of the circle should also eventually be made a separate explicit task, but for now the line renderer will be initialized with the circle and we will simply toggle its display and its color.


A Trio of Speed Improvements

This code does 3 things:

rebases @jagthedrummer to master. This makes a huge difference in docker mode
prevents rebuilding the image unless the Gemfile or Gemfile.lock has changed
Allows changing the name of the docker image via docker_image_name option. The goal of this change is to be able to pass a built image around via a registry, speeding up builds even more. The default remains ruby-layer:docker

Please let me know if there is anything I can do to help get these improvements merged in =-)

Thanks for this PR. Just noticed this PR. I will look into it next


Add travis-ci bindings for continuous integration testing

Create a travis-ci binding to run tests on pull request and git push
Done criteria:

Connect travis-ci to github repo
Create .travis.yml file for travis config

Already done with initial commit #3


Validators package not being included for test run builds

When running Velocity or TinyTest test suites for a local package which uses the astronomy-validators package, the build file does not include the exported Validators object. As such a ReferenceError is thrown for the Astronomy classes that have validators defined for them.
If you need I also have a small test project setup where this issue can be reproduced, I can create a repo for your access if you need.

Here is the test project if needed https://github.com/rhomes-wcd/validators-test

It's not a problem with astronomy. You have to add:
api.imply('jagi:astronomy-validators');

in the Package.onUse.
Exports are visible in the application. If you want to see exports in the local package you have to use imply.

Thank you for the quick response, after reading more on imply and adding both use & imply to the package I am still seeing this error with the below changes. Please let me know if I am missing something...
Package.onUse(function (api) {
    api.versionsFrom('<IP_ADDRESS>');

    packages = [
        'mongo',
        'jagi:astronomy',
        'jagi:astronomy-validators'];

    api.use(packages);
    api.imply(packages);

    api.addFiles('lib/model.js', ['client', 'server']);

    api.export('testpackage', ['client', 'server']);
});

Package.onTest(function (api) {
    api.use('testproj:testpackage');
    api.imply('testproj:testpackage');

    api.use('sanjo:jasmine@0.15.5');

    api.addFiles('tests/jasmine/server/integration/server.js', 'server');
});

Hmm strange. I will take a look at it few hours. I see that you've updated your repo so I will run it. However, after such changes in my test case it worked.

Sounds great, I appreciate it.

Sorry, I apparently was wrong. The imply method is not necessary. What you have to do is provide exact packages versions.
Package.describe({
  name: 'testproj:testpackage'
});

Package.onUse(function(api) {
  api.versionsFrom('<IP_ADDRESS>');

  api.use([
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>  ], ['client', 'server']);

  api.addFiles('lib/model.js', ['client', 'server']);

  api.export('testpackage', ['client', 'server']);
});

Package.onTest(function(api) {
  api.use('testproj:testpackage');
  api.use('sanjo:jasmine@0.15.5');

  api.addFiles('tests/jasmine/server/integration/server.js', 'server');
});

I don't remember why you have to do it, but now I remember that I've read about this and you have to do it. It should work. Let me know.
There should be a detailed section in the Meteor docs about creating packages.

Maybe it's because in the Astronomy Validators package I use Astronomy in the version 0.10.5 what is wrong. With the next astronomy version I will correct all version numbers.

Interesting, I was not aware of this requirement when setting up package.js files. I will test this and get back to you.

No problem :)


feat(data_classes): add support for Bedrock Agents events

Issue number: #3261
Summary
Changes

Please provide a summary of what's being changed

This PR adds event data class support for the Bedrock Agent events and response payloads.
Official docs: https://docs.aws.amazon.com/bedrock/latest/userguide/agents-create.html
User experience

Please share what the user experience looks like before and after this change

Before:
def handler(event: dict):
    print(event["inputText"]) # are you sure you've spelled it correctly? what is the return type?

After this PR, we could start writing Lambdas for Bedrock Agents like this:
from aws_lambda_powertools.utilities.data_classes import BedrockAgentEvent, event_source

@event_source(data_class=BedrockAgentEvent)
def handler(event: BedrockAgentEvent):
    print(event.input_text) # fully typed and filled by the IDE

Checklist
If your change doesn't seem to apply, please leave them unchecked.

[x] Meet tenets criteria
[x] I have performed a self-review of this change
[x] Changes have been tested
[x] Changes are documented
[x] PR title follows conventional commit semantics

Is this a breaking change?
RFC issue number:
Checklist:

[ ] Migration process documented
[ ] Implement warnings (if it can live side by side)

Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

any chance for parser schema too?

any chance for parser schema too?

Yeah @ran-isenberg! We will add support for Parser and Event Handler.

Update: As of October 31, 2023, the payload structure of the Lambda input event and response format is changing. So I'm updating this PR to reflect the changes

Codecov Report
Attention: 7 lines in your changes are missing coverage. Please review.

Comparison is base (b3c9ee0) 95.09% compared to head (5d5ce0a) 95.03%.
Report is 3 commits behind head on develop.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #3262      +/-   ##
===========================================
- Coverage    95.09%   95.03%   -0.07%
===========================================
  Files          202      203       +1
  Lines         9408     9503      +95
  Branches      1719      788     -931
===========================================
+ Hits          8947     9031      +84
- Misses         341      350       +9
- Partials       120      122       +2

Files
Coverage Δ

...mbda_powertools/utilities/data_classes/__init__.py
100.00% <100.00%> (ø)

...ools/utilities/data_classes/bedrock_agent_event.py
92.55% <92.55%> (ø)

... and 1 file with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

@leandrodamascena ready for another review


Outdated dependency not detected

<EMAIL_ADDRESS>It points to a tag that isn't latest and does not warn that v7 is out

Also broken on<EMAIL_ADDRESS>


meta-data

Could you please provide some more information on the published model files (where available)?

training material
evaluation material / results
input format/workflow dependencies (raw/bin, normalization/dewarping/deskewing)
output text characteristics (canonicalization/normalization, special characters for line/paragraph separators or quotes etc)

I'm just stumbling across this issue so it's probably not relevant anymore but all models which are contained in this repo are sourced from here or here and it looks like their respective README now contains some information about the models.


Deploy fails if GIT user.name contains a single quote

Deployer version: 7.0.0
Deployment OS: MacOS 12.5

If GIT user.name config property contains a single quote (e.g. "Erik D'Ercole", as my full name), Deployer exits with an error:
[staging] run cd /__OMISSIS__/project-folder && (echo '{"created_at":"2022-08-16T16:46:26+0000","release_name":"13","user":"Erik D'Ercole","target":"staging"}' >> .dep/releases_log)
[staging] bash: line 1: unexpected EOF while looking for matching `"'
[staging] bash: line 2: syntax error: unexpected end of file
[staging]  error  in release.php on line 119:
[staging] exit code -1 (Unknown error)

Thank you

Hmm, true)

@antonmedv Thanks! Have you already planned a release including this commit?

Yes, coming.


Update github.com/go-git/go-git to v5.11.0

I wonder what is the reason for the change since go-git is not a direct dependency.
However this looks fine.

The reason was this dependabot alert.
It's probably not something we would run into, but better safe than sorry :+1:


Test "640_proxy_restart_reattaches_test.sh" fails from time to time

The output from the build https://circleci.com/gh/weaveworks/weave/5115 :
>>> Test ./640_proxy_restart_reattaches_test.sh finished after 84.4 secs with error: exit status 1
Proxy restart reattaches networking to containers
59f0768f7c59fe50b7c231aca844983f724cd75ed1aff57c48287b344ddc7621
f32c5b5654850e6424b3619dcb7fac44dbad3e8b0d63b50f6dfa6173f0cbe22b
c2
weave
sudo: systemctl: command not found
host4-5115-0.us-central1-a.positive-cocoa-90213> docker stop/waiting
host4-5115-0.us-central1-a.positive-cocoa-90213> docker start/running, process 18202
Waiting for proxy to start
Waiting for proxy to start
120348873ce8f40d196db51c4a8457684320a401bcc082460e09fd875280223b
e313062d93bd0638d3bf9943659aad4d15004d76b3d8905e02101c3fa4e21e0d
test #7 "exec_on host4-5115-0.us-central1-a.positive-cocoa-90213 c2 grep ^1$ /sys/class/net/ethwe/carrier" failed:
	program terminated with code 1 instead of 0
test #8 "exec_on host4-5115-0.us-central1-a.positive-cocoa-90213 c1 getent hosts seetwo.weave.local | grep -q '<IP_ADDRESS>'" failed:
	program terminated with code 1 instead of 0
test #9 "exec_on host4-5115-0.us-central1-a.positive-cocoa-90213 c1 getent hosts <IP_ADDRESS> | tr -s ' ' | tr '[:upper:]' '[:lower:]'" failed:
	expected "<IP_ADDRESS> seetwo.weave.local"
	got nothing
3 of 14 tests failed in 83.633s.

The test script has a check for the existence of the systemctl command. However, for some reasons systemctl gets executed regardless the check.

I think the systemcl issue is a red herring. I reckon on our test VMs that always gets printed. Looks like there is something weird going on with user vs sudo envs, which makes systemctl available to the user but not in sudo. BUT it falls back to upstart, which still works, as evidenced by the "docker stop" and "docker start" lines.
I've just committed a change that should get rid of the "command not found" message.
The real cause of the test failure is the failing tests, as indicated.

Now seems to be consistently failing:
>>> Test ./640_proxy_restart_reattaches_test.sh finished after 14.1 secs with error: exit status 1
Proxy restart reattaches networking to containers
5c1ec8f480ef0827115d104504931b60cd84c678f134f22dfdc2617b627c934e
14b1f1ddbc2bb11e08ab7c010c5dd777e4d5464beede1175a35b31add56d770c
c2
weave
bash: systemctl: command not found
stop: Rejected send message, 1 matched rules; type="method_call", sender=":1.56" (uid=1003 pid=13893 comm="stop docker ") interface="com.ubuntu.Upstart0_6.Job" member="Stop" error name="(unset)" requested_reply="0" destination="com.ubuntu.Upstart" (uid=0 pid=1 comm="/sbin/init ")
start: Rejected send message, 1 matched rules; type="method_call", sender=":1.57" (uid=1003 pid=13887 comm="start docker ") interface="com.ubuntu.Upstart0_6.Job" member="Start" error name="(unset)" requested_reply="0" destination="com.ubuntu.Upstart" (uid=0 pid=1 comm="/sbin/init ")

My first guess is that increasing sleep time at line 51 might fix the failures of tests 7-9.

Note the sleep used to be 10 seconds, e.g. at #1609 (which also noted the systemctl problem), and we still had trouble.

@bboreham has figured out what is going on here. It's another docker event issue...
The proxy sees the killed container (re)start and attempts a weave attach --or-die. IPAM checks whether the container is alive but because the 'start' event gets issued before the container has transitioned out of the 'restart' to the 'running' state (see #1775), and we deliberately treat 'restarting' as 'not running', IPAM can consider the container dead and cancel the request.


Update Reason
Due to the harmonization from WeekBasedMaterialDemand to the new MaterialDemand aspect model with PURIS the property weekBasedMaterialDemand in the RfU aspect needs to be changed to materialDemand:
{
  -- "weekBasedMaterialDemand" : [ {
  "materialDemand" : [ {
    "materialDemandId" : "0157ba42-d2a8-4e28-8565-7b07830c3456",
    "changedAt" : "2023-03-10T12:27:11.320Z"
  } ],
  "weekBasedCapacityGroup" : [ {
    "capacityGroupId" : "0157ba42-d2a8-4e28-8565-7b07830c1110",
    "changedAt" : "2023-03-10T12:27:11.320Z"
  } ]
}

MS1 Criteria

[ ] The model that should be updated exists
[ ] The referenced use case exists
[ ] The potential updates are discussed with all stakeholders
[ ] A decision on versioning was made in consensus with the affected parties according to the guidelines.
[ ] The potential update will be either

[ ] backward compatible or
[ ] a (chain of) migration strategy(-ies) from all non-deprecated previous versions to the new model will be developed

[ ] A modeling steward has been assigned

@modeling_team

This will add a new major version 2.0.0


sails-postgresql adapter doesn't work with new Node v14

Node version: 14.0.0
DB adapter & version<EMAIL_ADDRESS>
Hi<EMAIL_ADDRESS>dependency in machinepack-postgresql doesn't work with new Node v14 (https://github.com/brianc/node-postgres/issues/2170).

@meltyshev Thanks for the heads up!  This is on our list to address in upcoming weeks.

@mikermcneil , I have the same problem. Pls. it is pretty urgent having a fix. I see that the latest update in sails-postgresql is about one year ago.  Will the new versions of node be supported?

@robertomarega Yes, the new versions of node will be supported eventually (and inevitably).  If you don't mind sharing, what is your urgent use case?  This will help us further understand. Thanks!
In the meantime, we're developing the sails-sql adapter to ultimately take over sails-postgresql support.  It will share a combination of support for MySQL, PostgreSQL (under construction), and Microsoft SQL Server (MSSQL)). 👍

Is there some kind of workaround? I'd need Node 14 support because I'm updating an old app and I would like to move it to the same server where another app is running which is already using features of Node 14

@Allain55 https://github.com/balderdashy/sails/issues/7022#issuecomment-669192460


Can't install elasticsearch plugins

Issue description
There is an error in install stage when configuring plugins for elastic search. It is present in 18.09 channel and on master branch of nixpkgs.
Steps to reproduce

Put in /etc/nixos/configuration.nix

    services.elasticsearch = {
      package = pkgs.elasticsearch-oss;
      enable = true;
      listenAddress = "<IP_ADDRESS>";
      plugins = with pkgs.elasticsearchPlugins; [ search_guard ];
    };

run nixos-rebuild switch --upgrade and watch the error

# nixos-rebuild switch --upgrade
unpacking channels...
building Nix...
building the system configuration...
these derivations will be built:
  /nix/store/1japx4r2c62bg73lcliqym2cdv6rs1jy-elastic-search-guard-6.5.1-23.2.drv
  /nix/store/h6ix04i05f4phq1iw5pgfv85pqz2flp4-elasticsearch-plugins.drv
  /nix/store/06fappd5hvca2pnwacp44c79dmiqnq02-unit-script-elasticsearch-pre-start.drv
  /nix/store/n21q7p1bd0c4d06rgqc92c0zpnx5xyjl-unit-elasticsearch.service.drv
  /nix/store/5yqg22vjg8kab686lqh89975pmvnc4bg-system-units.drv
  /nix/store/0dfi2vk99dqnrsnj5rdw2s982c1fzmz7-etc.drv
  /nix/store/svljia18z1s7g4dkiyr83ydlkvcjg11j-nixos-system-bonsai-18.09.2292.4c0be408155.drv
building '/nix/store/1japx4r2c62bg73lcliqym2cdv6rs1jy-elastic-search-guard-6.5.1-23.2.drv'...
unpacking sources
patching sources
configuring
no configure script, doing nothing
building
no Makefile, doing nothing
installing
Error: Could not find or load main class org.elasticsearch.tools.java_version_checker.JavaVersionChecker
builder for '/nix/store/1japx4r2c62bg73lcliqym2cdv6rs1jy-elastic-search-guard-6.5.1-23.2.drv' failed with exit code 1
cannot build derivation '/nix/store/h6ix04i05f4phq1iw5pgfv85pqz2flp4-elasticsearch-plugins.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/06fappd5hvca2pnwacp44c79dmiqnq02-unit-script-elasticsearch-pre-start.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/n21q7p1bd0c4d06rgqc92c0zpnx5xyjl-unit-elasticsearch.service.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/5yqg22vjg8kab686lqh89975pmvnc4bg-system-units.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/0dfi2vk99dqnrsnj5rdw2s982c1fzmz7-etc.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/svljia18z1s7g4dkiyr83ydlkvcjg11j-nixos-system-bonsai-18.09.2292.4c0be408155.drv': 1 dependencies couldn't be built
error: build of '/nix/store/svljia18z1s7g4dkiyr83ydlkvcjg11j-nixos-system-bonsai-18.09.2292.4c0be408155.drv' failed

Or from master:

[root@bonsai:~/nixpkgs]# git pull --rebase
Already up to date.
Current branch master is up to date.

[root@bonsai:~/nixpkgs]# git status
On branch master
Your branch is up to date with 'origin/master'.

nothing to commit, working tree clean

[root@bonsai:~/nixpkgs]# nix-build /root/nixpkgs/ -A pkgs.elasticsearchPlugins.search_guard
these derivations will be built:
  /nix/store/vis8n7i9b9w8pxd5wzqvdmzsf3b2by9d-elastic-search-guard-6.5.1-23.2.drv
building '/nix/store/vis8n7i9b9w8pxd5wzqvdmzsf3b2by9d-elastic-search-guard-6.5.1-23.2.drv'...
unpacking sources
patching sources
configuring
no configure script, doing nothing
building
no Makefile, doing nothing
installing
Error: Could not find or load main class org.elasticsearch.tools.java_version_checker.JavaVersionChecker
builder for '/nix/store/vis8n7i9b9w8pxd5wzqvdmzsf3b2by9d-elastic-search-guard-6.5.1-23.2.drv' failed with exit code 1
error: build of '/nix/store/vis8n7i9b9w8pxd5wzqvdmzsf3b2by9d-elastic-search-guard-6.5.1-23.2.drv' failed

Technical details
Please run nix-shell -p nix-info --run "nix-info -m" and paste the
results.
[root@bonsai:~]# nix-shell -p nix-info --run "nix-info -m"
these paths will be fetched (0.05 MiB download, 0.28 MiB unpacked):
  /nix/store/ial8a56ys2rswfq4j2abm3cl99li5b6p-bash-interactive-4.4-p23-dev
copying path '/nix/store/ial8a56ys2rswfq4j2abm3cl99li5b6p-bash-interactive-4.4-p23-dev' from 'https://cache.nixos.org'...
error: restoring parent mount namespace: Invalid argument

[root@bonsai:~]# nix-info -m
 - system: `"x86_64-linux"`
 - host os: `Linux 4.14.104, NixOS, 18.09.2292.4c0be408155 (Jellyfish)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.2`
 - channels(root): `"nixos-18.09.2292.4c0be408155, nixpkgs-19.03pre161900.61c3169a0e1"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

i have been playing around with this a little.
What i have found so far:
it can made to work by symlinking elasticsearch-oss when building the package.
this has to be done here: https://github.com/NixOS/nixpkgs/blob/master/pkgs/servers/search/elasticsearch/plugins.nix#L9
resulting in:
    installPhase ? ''
      mkdir -p $out/config
      mkdir -p $out/plugins
      ln -s ${elasticsearch-oss}/lib $out/lib
      ES_HOME=$out ${elasticsearch-oss}/bin/elasticsearch-plugin install --batch -v file://$src
      rm $out/lib
    ''

BUT:
the elasticsearch-service-modules symlinks the plugins into ${cfg.dataDir}/plugins here
this results in elasticsearch trying to load the plugins but failing with access denied ("java.io.FilePermission" just as mentioned here in the case of symlinking the elasticsearch-config.
this can be worked around by copying the plugins instead of symlinking here.
resulting in:
        mkdir -p ${cfg.dataDir}/plugins
        for plugin in  ${concatStringsSep " " cfg.plugins}; do
          cp -r $plugin/plugins/* ${cfg.dataDir}/plugins
        done

but this kind of seems crappy.
the root cause might be this:
https://www.elastic.co/guide/en/elasticsearch/reference/2.1/breaking_20_plugin_and_packaging_changes.html#_symbolic_links_and_paths

changing the module to
  esPlugins = pkgs.stdenv.mkDerivation {
    name = "elasticsearch-plugins";
    buildCommand = ''
      mkdir -p $out/plugins
      for plugin in  ${concatStringsSep " " cfg.plugins}; do
        cp -r $plugin/plugins/* $out/plugins
      done
    '';
  };

seems to work, which lets me believe that the aforementioned link is relevant here.

A configured path may itself be a symbolic link, but no symlinks under that path will be followed.

Any news? It's almost a year.


Implemented NthPrime (nth-prime) exercise for objective-c

Implemented NthPrime (nth-prime) exercise for objective-c.

Thanks for this, much appreciated! Our Objc track doesn't get as much love as our Swift one :)


Fix #73 : if protocol is not http or https, default to http

Previous was using the wrong base #74

Shall I merge?

Will handle it today. If you need it now, can you npm install SHA --save?


[Bug?]: Hydration not fired with cascading deferStream

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
I have an app shell, with menu and footer navigation which are loaded using createAsync they deferStream. My page content is also loaded via an API with createAsync in a route. It deferStream.
Representation:
- app.tsx
    - RootContexts.tsx <— 2 createAsync deferStream
        - PageCom
            - index.tsx (route) <— 1 createAsync deferStream

If index.tsx has deferStream at the same time that upper component RootContexts has deferStream, hydration does not happen.
Expected behavior 🤔
Hydration works even if the stream is held at different levels.
Steps to reproduce 🕹
Repro: https://github.com/jchatard/defer-hydration

pnpm i
pnpm dev
http://localhost:3000/
click the Counter (from index.tsx) nothing happens on page load (hmr make it work)
Remove deferStream from src/routes/index.tsx reload the page: it works.

Using ssr: "async"also has the bug, which makes sense.
Context 🔦
I need to hold the stream for as long as possible to have the website crawlable by SEO robots with no javascript.
Your environment 🌎
No response

Yeah this looks like a Solid bug. It's responding before the final JSON blob makes it to the client. This doesn't happen when streaming for some reason. Probably related to changes I made recently. I will see what is exactly causing this timing issue.


Bounding_box  from aiy.vision.inference

How would I get the bounding box of the detected face from CameraInference.
I see that annotator was invoked but have no idea how to st up the code to get the bounding box.
I have modified the camera trigger demo to return images with faces in them as detected but want to extract bounding box to save just the face.
Any ideas?

Each face object has bounding_box attribute, check the example code: https://github.com/google/aiyprojects-raspbian/blob/e48363018e37b1fdc22d5ddc4b221db97c2cf47b/src/examples/vision/face_detection_camera.py#L80

Thanks Dimitri,
I have played with aiyprojects-raspbian/src/examples/vision/face_detection_camera.py but it locks out camera.capture("filename") as the Vision Bonnet is running a real time video stream.
I want to add getting the bounding box in the  face.camera.trigger example.
I have modified it to capture a face when detected, save it to a file,  and then use it as a label scale it and place the images in a grid.
What I wasnt is the bounding box here.
I am having difficulty understanding the relationship with annotator and the bounding box. Is bounding_ box a property?
with CameraInference(face_detection.model()) as inference:
for result in inference.run():
if len(face_detection.get_faces(result)) >= 1:
camera.capture('faces.jpg')
How do I get the bounding box before camera.capture ??
Is there a real API description for main vision libraries (aiy.vision.inference) .
More documentation would probably get a lot of people productive.
Thanks!

In this example face_detection.get_faces(result) returns a list of detected faces.  You can access bounding boxes in the following way:
with CameraInference(face_detection.model()) as inference:
  for result in inference.run():
    faces = face_detection.get_faces(result)
    if len(faces) >= 1:
      for face in faces:
        print(face.bounding_box)  # <-- bounding box object
      camera.capture('faces.jpg')

Please look at the source code and examples to check how everything works, that's the best way for now. We are going to provide better API documentation soon.

Thanks!!!!  Got it going.  If you want a reviewer for the API I'd be glad to put in some time.

Well almost got it.
The data type returned is float (?) Yes or no.
The data is x, y, height, width
where (x,y) is the lower or upper left hand corner??
I want to pass the data to image.crop(x,y,height width) to extract the recognized face.
Can you define what x and y are giving me so I can specify the crop.
I'm probably being dense here.

That's correct, bounding box is (x, y, w, h) tuple of integer numbers, coordinate system origin is at top-left corner.  We run inference on image coming from the sensor, you can access its width as result.width and height as result.height. If you want to save image which has different size (e.g. downscaled or upscaled) you need to recalculate coordinates of bounding box, for example:
x = int(your_width  * (face.bounding_box[0] / result.width))
y = int(your_height * (face.bounding_box[1] / result.height))
w = int(your_width  * (face.bounding_box[2] / result.width))
h = int(your_height * (face.bounding_box[3] / result.height))

Now I got it
My issue was not understanding image.crop((x,y, x+width,y+height))  seems to crop out the bounding box!

Perfect! Closing this issue.


 Especially on longer timers, it sometimes just gets stuck on vMix even tho it keeps running on Clockotron itself.

Found the issue. Clocktron doesnt seem to be preventing certain ethernet adapters from going into powersaving or sleep mode. Manually disabling all powersaving and sleep features in device manager fixed the issue.


fix: rename rule no-empty-enum-servers to no-server-variables-empty-enum

What/Why/How?

rename no-empty-enum-servers to no-server-variables-empty-enum and adjust corresponding code and docs. The current live docs are completely incorrect and wouldn't function, so it is safer to rename (the actual working one would have been no-servers-empty-enum but it wasn't documented that way due to the strange naming in the source code: https://redocly.com/docs/cli/rules/no-empty-enum-servers/ -- the changelog should note the rename.
docs: fix no-server-example.com docs

Reference

Fixes #812

Testing
Passed.
Check yourself

[x] Code is linted
[ ] N/A Tested with redoc/reference-docs/workflows
[x] All new/updated code is covered with tests

Security

[x] Security impact of change has been considered
[x] Code follows company security practices and guidelines

Are we sure we don't want to add a commit to the CHANGELOG in an unreleased section at the top? Anyway, here is what I propose for simplicity during the release.
Changes

Renamed no-servers-empty-enum to no-server-variables-empty-enum and fixed incorrect docs of no-empty-enum-servers.

Fixes

Fixed docs for no-server-example.com


Simplified PCH fix to support PCH containing value which needs to be subst()'d

Initial checkin of simplified support for PCH needing to be subst()'d to resolve. In particular when PCH evaluates to a generator
Possible alternative to PR #3984 Based of work done by @dmoody256
Contributor Checklist:

[x] I have created a new test or updated the unit tests to cover the new/changed functionality.
[x] I have updated CHANGES.txt (and read the README.rst)
[x] I have updated the appropriate documentation

@dmoody256  - please review.

recently:

When you create a new project in Visual Studio, a precompiled header file named pch.h is added to the project. (In Visual Studio 2017 and earlier, the file was called stdafx.h.)


remove border

Removed the border around code in Markdown for aesthetic reasons.

Codecov Report
Base: 98.64% // Head: 98.64% // No change to project coverage :thumbsup:

Coverage data is based on head (abb691b) compared to base (7d126c8).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #2532   +/-   ##
=======================================
  Coverage   98.64%   98.64%
=======================================
  Files          73       73
  Lines        7840     7840
=======================================
  Hits         7734     7734
  Misses        106      106

Flag
Coverage Δ

unittests
98.64% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

rich/markdown.py
100.00% <100.00%> (ø)

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

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


Add an option to read Host ID from node annotation if ExternalID is not available

What this PR does
Fixes a bug where HostID is not populated starting with Kubernetes 1.11. ExternalID which was originally a source of HostID label was deprecated and is no longer set in Kubernetes 1.11. Starting with this version, host ID can be provided via node annotation.

If this is a bugfix, what's the actual bug here?  What was the issue being caused?

This causes Heapster to label metrics incorrectly with empty host id. For Stackdriver sink, this causes a majority of metrics to not be exported.

Isn't that specific to the stackdriver sink, though?  Shouldn't we just have a workaround there?  It feels heavy-handed and hacky to add an entire new option and pull this from a completely optional label.  Kubernetes did remove that field for a reason, and I don't think it's a particularly good idea to hack it back in in the general case in Heapster.

I don't think this is relevant to any other sink, but it could be. I would argue that this is a bug in Heapster sources, because the metric labels are set there. One of them is HostID, and the summary source assigns to it an incorrect value.
I have to agree that using a node annotation for this is hacky, the problem is that there is no environment-agnostic source of this information now. I identified this way to be least disruptive, as it's optional to annotate nodes and it doesn't change the default Heapster behavior. The Summary API source doesn't propagate information about node annotations to the sinks, therefore fixing this in Stackdriver sink would require either

Propagating all node annotations to sinks
Calling API Server again just to fill the missing annotations for the nodes

From my discussions about removing this field, it is key that it was a part of node spec, which is immutable. Therefore on a cloud providers where this value changed during the node update, it forced a node recreation. The optional annotation doesn't have the same problem.

Hmm... I'd argue the fix should have been to remove the HostID label, then, since Kubernetes removed the HostID field.  /me shrugs
Separately, if a change is adding a new flag, there should be discussion, or at least time for discussion.  Merging within a couple hours of the change landing on GitHub is not acceptable for Heapster-wide changes.  It's fine if you want to do that within the Stackdriver sink, but for this kind of thing, other people should have a chance to comment.

Sorry for that, I considered it a small change with no effect on performance and transparent to anyone that doesn't depend on HostID label. I'll make sure to give more time for others to comment for any other PRs, for this one we can continue a discussion here whether to accept this fix or replace with something else.
Wrt. to removing HostID label completely, I wouldn't consider it as an option because it's already used by some (Stackdriver) sink. It does cause significant breakage for Stackdriver integration, i.e. all node metrics have now indistinguishable labels, Stackdriver API doesn't accept duplicate timeseries for the same period, so it rejects them. Because Heapster sends metrics in batches, this causes a rejection of the whole batch. Same thing for kubelet and docker-daemon metrics - they are identified by the instance.

Sorry for that, I considered it a small change with no effect on performance and transparent to anyone that doesn't depend on HostID label.

No worries, I'm just more concerned about new config flags, etc.

Wrt. to removing HostID label completely, I wouldn't consider it as an option because it's already used by some (Stackdriver) sink. It does cause significant breakage for Stackdriver integration, i.e. all node metrics have now indistinguishable labels

hmm... could we possibly choose a replacement to plumb through?  Is NodeName insufficiently unique there, or is there some wrinkle in stackdriver that makes that not work?

Thanks for your suggestion. We considered that path, but turns out that Stackdriver relies on the instance_id matching the actual ID and there are several things that can break with such Heapster upgrade, as Stackdriver has other channels that export data as well and they need to match labels for metrics. Other problem is that the upgrade will cause too much alerts to fire due to not matching labels.

Ok, since this is already in, and that's a reasonable explanation, I think it's fine to keep it as-is.  As much as I would like an alternate path, I also don't want to cause too much of a headache for you guys.  In the future, please include that explanation in the PR as well.


Can we have a new distribution build with the updateItemAt fix?

[UICollectionView cellForRowAtIndexPath:]: unrecognized selector sent to instance 0x7927b800

Yeah will nice to download to a new build dist :)

same request, because compiling the module manually generates an error after compiling the app:
[ERROR] :  ** BUILD FAILED **
[ERROR] :  The following build commands failed:
[ERROR] :  	Ld build/Trending.build/Debug-iphonesimulator/Trending-universal.build/Objects-normal/i386/Trending normal i386
[ERROR] :  	Ld build/Trending.build/Debug-iphonesimulator/Trending-universal.build/Objects-normal/x86_64/Trending normal x86_64

Version 1.3.1 is now available


How to use https?

How to make it support https?

Could you give more info on this?
Usually, we don't terminate on Node.js level.
We do it using a SSL terminator (Nginx, bud or stud) or usually using a method supported by the cloud hosting provider.

@nkzawa do you we any other plans to support HTTPS?


Fix overflow property controls functionality of Breadcrumb

There are three properties in Breadcrumb by names of

OnRenderOverflowIcon
OverflowIndex
OverflowAriaLabel

There functionality is not working fine. by setting OverflowIndex icon is appeared for that index and all previous indexes
and all items are shown.
We have a property by name of OverflowAriaLabel  , but it is not using in code :|
https://developer.microsoft.com/en-us/fluentui#/controls/web/breadcrumb

This is closed by #1661

This is closed by #1661


FileopenPicker (UWP) throws error when PickSingleFileAsync() called

"WinRT information: The FileTypeFilters property must have at least one file type filter specified."
There is no way to set the filter... it is read only, and not virtual.
FileOpenPicker.cs
Am I missing some other initialization step?

You can add file type filters like so:
var singleFilePick = new FileOpenPicker(this);
            singleFilePick.FileTypeFilter.Add(".jpg");

var pickedFile = await singleFilePick.PickSingleFileAsync();

Let me know if this solves your issue.

Duh, I’m being dense… thank you.  End of a long day...

James,
maybe you have some more insight into a problem I'm having now... have you used this code on UWP, or only on Droid/iOS?
I am trying to open a file on UWP, but keep getting error stating file does not exists.  I think the source is line#62 here: StorageFile.cs
I would expect SystemIO.File.Exists() to work on Dorid/iOS, but not UWP (always returns false due to difference in sec vs. desktop API on windows).
I am interested in using several of your libs with Xamarin.Forms to support multiplatform, but I suspect you have not designed for use on UWP.

I have proven that the issue is with File.Exists() on UWP.  It no work like expected =( .  Sad that .NetStandard provides an API that doesn't behave... but that's why we have the PCL mess we have … anyway, that's a different topic.
If you were to replace line #62 in StorageFile.cs
public bool Exists => this.Originator != null && File.Exists(this.Path);
with something like:
public bool Exists => this.Originator != null && CheckFileExists(this.Path);
.
.
.
protected virtual bool CheckFileExists(string path) => File.Exists(this.Path)
I could then provide a different impl for UWP.   Is supect there is similar code in StorageFolder.cs  (line 65)

@jasells I will take a look into this. It has previously been working but as you've mentioned, changes in .NET Standard may have broken this and as you've pointed out, this is because File.Exists doesn't work if the file in UWP is outside of the scope of the application's storage location.

The only way I've been able to accomplish the File.Exists fuctionality (even in a pure UWP app) is to do something like:
`public async Task<System.IO.Stream> OpenFileForRead(XPlat.Storage.IStorageFile file)
{
var dir = await file.GetParentAsync();
Windows.Storage.IStorageFile nativeFile;
Windows.Storage.IStorageFolder parentDir = null;
        if (dir.Path.ToLower().Contains("c:"))
        {
           //check all the known folders
        }
        else //it is removable drive
        {
            var fldrs = (await Windows.Storage.KnownFolders.RemovableDevices.GetFoldersAsync()).ToList();

            parentDir = fldrs.FirstOrDefault(fldr => fldr.Name == dir.Name);

            var name = parentDir.Name;
        }

        nativeFile = (await parentDir.GetItemAsync(file.Name)) as Windows.Storage.IStorageFile;

        return (await nativeFile.OpenReadAsync()).AsStream();
    }`

This is basically what I did using Xamarin's Dependency service to provide a plugin, and then I used an extension method in my portable code to add it back to Xplat.Storage.IStorageFile and just not using  OpenReadAsync() provided.
It might be more a function of the target/min UWP version, not .NetStandard, if you say it has been working?  I am targeting min of 1709 (SDK v. 16299).

I think the appropriate thing to do here is close this issue, and open a new one with a more appropriate title/focus.


Fix typo in documentation

in section Accessing only a single container/file-system change FileSystemHandler to FilesystemHandler:
handler = pyarrowfs_adlgen2.FilesystemHandler.from_account_name(
   "STORAGE_ACCOUNT", "FS_NAME", azure.identity.DefaultAzureCredential())
```

Thanks! This is fixed now.


Prevent tree-shaking of polyfills

If assumeNoImportSideEffects is set to true, then imports for side effects will be tree-shaken (per https://github.com/webpack/webpack/issues/6571 effectful imports are not considered side effect free by webpack).
Because the API of core-js relies on import side effects (rather than some actual polyfill method) this means polyfills are erroneously never included.
This PR avoids this behavior by changing the polyfill imports to use require instead.

!merge


Even if I set to 50 for above values, I'm getting Connection Refused. Any complete example to use above code appropriately?

PR: https://github.com/go-gorm/playground/pull/68
Even if I set to 50 for above values, I'm getting Connection Refused.
Any complete example to use above code appropriately?
I'm not getting it working on v2.
I think I've to revert back to v1.

The connection pool usage looks good, have you make sure you only SetupDB once for your application? not for every request, looks like a bug in your application.


LocalCall

Description:
This PR provides implementation of the signer.call method in the Wallet class.
Added:

getHederaClient() in provider
call() in Wallet

Deprecated call in abstract signer - now throws

Related issue(s):
Fixes #
Notes for reviewer:

Checklist

[ ] Documented (Code comments, README, etc.)
[ ] Tested (unit, integration, etc.)

Let's merge contract-interactions in develop before reviewing this, as local-call is based on it.


Removing some dead links from Decorators section

Just removing two dead links @kirang89

Looks good, thanks for catching this! 🎉

No worries :+1:


Remove meshzoo

It's no longer open source, and code has been moved to a private repo.
https://github.com/meshpro/meshzoo

1d8f75f521f643021a7d1b7ba60824aebadb4626


stackbit issue

Loading site /tmp/909d8133-b79c-4a9c-8e88-07760ab1d1e0
Error loading theme at /tmp/909d8133-b79c-4a9c-8e88-07760ab1d1e0
To get this error, click the 'Create with Stackbit' button.
Fails during validation with those 2 errors.
Great theme though. Especially the new look.

Thanks for the report, I definitely want to keep supporting Stackbit so I will get a fix fo this as soon as I can. I'll let you know once I'm done.

should be a few more days before this is fixed

@stephenajulu should be working now