Fixed implicit mapping can't map nested property with same type

Resolved: #415

link to wrong issue.


ShipIt regularly jumps to 100% CPU usage and stays there

Not sure if this is a good place to put this, but I have this issue with the Splice app. Splice it not my app clearly, I just have it installed. M1 Pro.

Just had ShipIt process max out a core. I felt my M1 MBP was uncharacteristically warm. When I force quit the process, Arduino booted up.
This is not the first time I've caught ShipIt in a loop like this.
Is this something client apps (like Arduino) are doing wrong, or is this a bug with ShipIt?

SlidePad uses Squirrel and I noticed Shipit stuck at 100% after updating yesterday SlidePad v1.4.9


Unable to connect to glue catalog in different AWS project from current AWS project

Describe the bug
I am trying to run dbt model from current AWS project and I am getting AnalysisException: Table or view not found: xxx.yyyy` as my source is in different AWS project glue catalog. Though i have permissions to read other AWS project catalog, still I am unable to read table from different catalog.
Steps To Reproduce
My source looks like as below
version: 2

sources:
  - name: datalake
    schema: secret
    tables:
      # please maintain alphabetical order
      - name: secret1

My model looks like following
{{
  config(
    materialized="incremental",
    file_format='parquet',
    incremental_strategy='insert_overwrite',
    table_properties={'write.target-file-size-bytes': '268435456'}
  )
}}

with base as
(
    select * from {{ source('datalake', 'secret1') }}
    where a=123
)

SELECT *
FROM base

My target connection looks like as follows where iam explicitly passing catalogid to spark conf
dev:
    type: glue
    role_arn: arn:aws:iam::xxxxxx:role/ccoeGlueEDADBTExecution
    region: us-east-2
    workers: 10
    glue_version: "3.0"
    worker_type: G.2X
    idle_timeout: 10
    schema: "{{ env_var('SCHEMA', 'dbt_wsb') }}"
    conf: --conf hive.metastore.client.factory.class=com.amazonaws.glue.catalog.metastore.AWSGlueDataCatalogHiveClientFactory
             --conf  hive.metastore.glue.catalogid=xxxx --conf aws.region=us-east-2
    session_provisioning_timeout_in_seconds: 120
    location: "{{ env_var('LOCATION', 's3://dbt-wsb/models') }}"

When I run dbt model, I get following error
AnalysisException: Table or view not found: `secret.secret1`; line 20 pos 18;
'CreateTable `smullangi_utils`.`datalake_model`, ErrorIfExists
+- 'Project [*]
   +- 'SubqueryAlias base
      +- 'Project [*]
         +- 'Filter ('advertisement_id = 123)
            +- 'UnresolvedRelation [secret.secret1], [], false

Expected behavior
Model should be created as we passed catalogid explicity. We need to know exact way to pass catalogid to source so that my dbt understands and creates table.
Screenshots and log output
If applicable, add screenshots or log output to help explain your problem.
System information
The output of dbt --version:
Core:
  - installed: 1.3.4
  - latest:    1.5.0 - Update available!

  Your version of dbt-core is out of date!
  You can find instructions for upgrading here:
  https://docs.getdbt.com/docs/installation

Plugins:
  - glue:  1.3.12 - Update available!
  - spark: 1.3.1  - Update available!

  At least one plugin is out of date or incompatible with dbt-core.
  You can find instructions for upgrading here:
  https://docs.getdbt.com/docs/installation

The operating system you're using:
macos 13.3.1 (22E261)
The output of python --version:
Python 3.9.7
Additional context
We have run glue job from AWS console using python and is working from our project. We are able to read catalog from different AWS project from current AWS project. This tells us that there is no problem with provided access/policies. The problem is only when we run with dbt-glue adapter locally.
I followed all approaches mentioned here https://repost.aws/knowledge-center/query-glue-data-catalog-cross-account but still its not working (passed all parameters in conf of profiles.yml)
Also we are able to run dbt model using dbt-glue adapter when source table is in current catalog.

Bumping up for visibility

To allow cross-account catalog access in Spark SQL, you needs to provide hive.metastore.glue.catalogid in Glue Interactive Session, and configure permission in Glue catalog policy.
In case customer wants to configure hive.metastore.glue.catalogid through --conf parameter, it needs to be spark.hadoop.hive.metastore.glue.catalogid.
The other config like hive.metastore.client.factory.class and aws.region are not required but region needs to be specified if catalog is in another region.
I have tested --conf spark.hadoop.hive.metastore.glue.catalogid=XXXXXXXXXXX in both job and notebook, both succeeded to read from cross account catalog.

@sandeepmullangi2 as mentioned by @moomindani you can add the --conf spark.hadoop.hive.metastore.glue.catalogid=149307159015

@sandeepmullangi2 as mentioned by @moomindani you need to use
--conf spark.hadoop.hive.metastore.glue.catalogid=XXXXXXXXXXX in your dbt profile, as such, you can have multiple outputs for each of the accounts that you have access to, is that fixing your issue ?

@moomindani @AmineIzanami This did not fix our issue, may be our usecase is bit different. Our usecase is read data from one source catalog and write it to destination catalog.
When I used spark.hadoop.hive.metastore.glue.catalogid=XXXXXXXXXXX iam able to read table from source but not able to write to destination catalog and is trying to write back to source catalog and i got permission issue since i dont have write access to source catalog. So this adapter does not provide source and target catalogs to be passed. Since this was creating issue we started using dbt-athena adapter.

@sandeepmullangi2 indeed the fix that we mentioned is cross account but single tenant, which means that the dbt session will be per account, so the reading and the writing is local to that AWS account, in your case, have you thought of creating resource links in your AWS account with LakeFormation so that the target glue tables are local to your source AWS account ?


CMake: TRY_RUN() invoked in cross-compiling mode

Hi guys,
I'm one of vcpkg maintainers.
When upgrading cpr to the latest version 1.6.2 in vcpkg, it failed with the following errors on uwp:
-- Performing Test THREAD_SANITIZER_AVAILABLE
CMake Error: TRY_RUN() invoked in cross-compiling mode, please set the following cache variables appropriately:
   THREAD_SANITIZER_AVAILABLE_EXITCODE (advanced)
   THREAD_SANITIZER_AVAILABLE_EXITCODE__TRYRUN_OUTPUT (advanced)
For details see D:/buildtrees/cpr/arm-uwp-dbg/TryRunResults.cmake
-- Performing Test THREAD_SANITIZER_AVAILABLE - Failed
-- Performing Test ADDRESS_SANITIZER_AVAILABLE
CMake Error: TRY_RUN() invoked in cross-compiling mode, please set the following cache variables appropriately:
   ADDRESS_SANITIZER_AVAILABLE_EXITCODE (advanced)
   ADDRESS_SANITIZER_AVAILABLE_EXITCODE__TRYRUN_OUTPUT (advanced)
For details see D:/buildtrees/cpr/arm-uwp-dbg/TryRunResults.cmake
-- Performing Test ADDRESS_SANITIZER_AVAILABLE - Failed
-- Performing Test LEAK_SANITIZER_AVAILABLE
-- Performing Test LEAK_SANITIZER_AVAILABLE - Failed
-- Performing Test UNDEFINED_BEHAVIOUR_SANITIZER_AVAILABLE
-- Performing Test UNDEFINED_BEHAVIOUR_SANITIZER_AVAILABLE - Failed
-- Performing Test ALL_SANITIZERS_AVAILABLE
CMake Error: TRY_RUN() invoked in cross-compiling mode, please set the following cache variables appropriately:
   ALL_SANITIZERS_AVAILABLE_EXITCODE (advanced)
   ALL_SANITIZERS_AVAILABLE_EXITCODE__TRYRUN_OUTPUT (advanced)
For details see D:/buildtrees/cpr/arm-uwp-dbg/TryRunResults.cmake
-- Performing Test ALL_SANITIZERS_AVAILABLE - Failed

Can you help me look into this problem? @COM8
Thanks in advance!
Related PR from vcpkg: https://github.com/microsoft/vcpkg/pull/18386

I'd say this is caused by cpr trying to compile a simple program with sanitizers enabled.
https://github.com/whoshuu/cpr/blob/f4622efcb59d84071ae11404ae61bd821c1c344b/cmake/sanitizer.cmake#L11
It looks like in case you want to perform cross-compilation for UWP, this fails.
As a quick and dirty workaround I suggest patching out this line, when building:
https://github.com/whoshuu/cpr/blob/f4622efcb59d84071ae11404ae61bd821c1c344b/CMakeLists.txt#L49
... since the vcpkg packages probably will not need any sanitizers enabled.
For the next release, we should probably find a way to disable those checks for cross-compilation.
@KingKili do you know a way to fix this?

Thanks for your quick response and suggestion. @COM8
So we can make a patch to comment include(cmake/sanitizer.cmake) out in cpr 1.6.2 now and remove the patch when this is fixed in next release.

include(cmake/sanitizer.cmake) is still required on other targets. I add the patch only for uwp. Please take this case in consideration for the new fix in next release.
CMake Error at CMakeLists.txt:110 (message):
  Invalid build type: Debug

Thanks for your fixing @COM8.


Documenting src/redux/movies/movies.actions.js to explain functionality

For the file src/redux/movies/movies.actions.js, write a summary of each function and a summary for the overall file.

I would like to work on this please!

Great! I assigned you (@DimirSignet) to the issue. Have fun working on it!


fix issue #1651: fixed typo for insecureskipverify; set the default value as false

Fix #1651
correct the typo for insecureskipverify in the security-proxy-setup project, and set the default value as false.
Signed-off-by: Tingyu Zeng<EMAIL_ADDRESS>

Codecov Report

Merging #1781 into master will decrease coverage by 0.26%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1781      +/-   ##
==========================================
- Coverage   38.33%   38.06%   -0.27%
==========================================
  Files         149      153       +4
  Lines       11840    12008     +168
==========================================
+ Hits         4539     4571      +32
- Misses       7098     7223     +125
- Partials      203      214      +11

Impacted Files
Coverage Δ

internal/security/secretstore/init.go
0% <0%> (ø)

internal/security/secretstore/certs.go
17.69% <0%> (ø)

internal/security/secretstore/requester.go
30% <0%> (ø)

internal/security/secretstore/config.go
100% <0%> (ø)

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 62ad1ea...83a8b62. Read the comment docs.

recheck


beyond HTTP(S)_PROXY

hello, kong project.
Thanks you for the great project.
Problem
provision.sh  doesn't take care  HTTP_PROXY, HTTPS_PROXY enviroment variable.
so, vagrant up stop after Installing Kong version message inside http proxy.
Proposal
$6 of provison.sh accpets HTTP(S) proxy host.
and provision.sh configure.

Would you mind sending a PR for this?

Of course, not!
I'll do it over the weekend.


Option to add track-by="$index" in client tables

Vue.js version: ^1.0.18
consumed using: (webpack)
relevant code:
trackBy:'track-by="$index"'
Line 18: File v-client-table.js

Good idea. I have added a 'trackBy' option. Default is $index

Perfect!
Skickat från min iPhone

19 apr. 2016 kl. 20:43 skrev Matanya<EMAIL_ADDRESS>Good idea. I have added a 'trackBy' option. Default is $index
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub


Research Python Google Sheets API

Find a way to use Python to send data

update:
Got it working on well on python and iffy on javascript, however currently all operations are done on google sheets, python only reads in and writes data. Two main operations addNew (adds data to next available line) and find (gets the position of data or -1 if doesn't exist)

improved version under branch google-sheetsV2, original may not work correctly as I may have killed the project that the credentials file used there

Functionality tested by @guilleeh


Daksh Events

Removed the old events from json file and updated it with new events. Also uncommented the code in EventsWorkshop.js file that enables events button!

Now made the poster in same row as the text, please review it once before merging


ISPN-8038 java.lang.ClassCastException with compatibility mode and te…

…xt content
https://issues.jboss.org/browse/ISPN-8038

Is this PR causing http://ci.infinispan.org/job/Infinispan/job/PR-5278/3/testReport/junit/org.infinispan.it.compatibility/DistMemcachedEmbeddedTest/setup/ ?

@tristantarrant I don't think so  http://ci.infinispan.org/job/Infinispan/job/master/23/testReport/junit/org.infinispan.it.compatibility/ByteArrayValueReplEmbeddedHotRodTest/setup/

All suggestions applied.

Thanks, looks good. After the latest changes some unused imports were left in ExecTypedTest and CustomMemcachedHotRodTest. I'll fix them and merge.

Merged in master. Thanks @gustavonalle !


Feedback Your Code

Your Code Is Bad Code

add discription and Redme File

A design pattern is a general, reusable solution to a commonly occurring problem within a given context in software design. It is not a finished design that can be directly transformed into code, but a template that guides developers on how to structure their code in a particular situation. Design patterns provide proven development paradigms and best practices, improving code maintainability, scalability, and readability.
There are three main types of design patterns:

Creational Patterns: Deal with object creation mechanisms.

Examples: Singleton, Factory, Abstract Factory, Builder, Prototype.

Structural Patterns: Deal with object composition or how to structure relationships between objects.

Examples: Adapter, Bridge, Composite, Decorator, Facade, Proxy, Flyweight.

Behavioral Patterns: Deal with communication between objects.

Examples: Observer, Strategy, Command, Chain of Responsibility, State, Template Method.

Design patterns help solve complex design problems and make code more flexible and easier to understand.


fix for fsspec 2024.5.0

fsspec==2024.5.0 replaced mv_file with mv. This commits adds compat for both.

Also enable support for Python 3.13,
Uses uv.
Remove safety.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 85.26%. Comparing base (602da4c) to head (0d0909d).

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #34      +/-   ##
==========================================
+ Coverage   85.24%   85.26%   +0.01%
==========================================
  Files           8        8
  Lines         922      923       +1
  Branches      171      148      -23
==========================================
+ Hits          786      787       +1
  Misses        128      128
  Partials        8        8

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


Installer not upgrading as expected

Creating a new issue from old issues #12 and #13 regarding installer

However, there might be a problem with the installer package. I installed the package assuming that it was an upgrade. It did not upgrade and instead 6.0.0 was still there with an option to delete. Version 6.0.2 appears as another extension BUT it does not have a delete option. I thought maybe there was a problem with the extension installation so I deleted 6.0.0 and then I re-installed 6.0.2 and now I have two versions of 6.0.2 showing as installed. But that said the module is authenticating AD.

New version 6.1.2 was tested as an upgrade and new install.  This problem did not occur.


Authentication expired - Unable to log in - _csrf cookie does not exist

Hi there! :)
Thank you for the terrific integration you have put together here, outstanding piece of work!
I'm just reaching to let you know, that there might be some hiccups with the re-authentication and possibly missing _csrf cookie assumed as coming back in response from APIs.
Recently Home Assistant (core ver 2024.4.4 - OS 12.2 ) told me that my Aquarea authentication expired.
Here's what it's thrown:
2024-04-28 23:31:01.788 ERROR (MainThread) [custom_components.aquarea.config_flow] Unexpected exception
Traceback (most recent call last):
  File "/config/custom_components/aquarea/config_flow.py", line 144, in _validate_input
    await self._api.login()
  File "/usr/local/lib/python3.12/site-packages/aioaquarea/core.py", line 274, in login
    await self.__login_production()
  File "/usr/local/lib/python3.12/site-packages/aioaquarea/core.py", line 334, in __login_production
    csrf = response.cookies.get("_csrf").value
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'value'

I've seen your v0.7.1 version linked in Panasonic changed their login system issue and installed it (by overwriting custom_components directory but this didn't help in the end.
So I thought I might just open the issue in here for your tracking :)
Best!

Thanks a lot @mgeeky. If csrf is not coming back on that response probably there was something wrong with the previous request:
https://github.com/cjaliaga/aioaquarea/blob/9348dd47b2c13163c45748ed513853646b5b27dd/aioaquarea/core.py#L328-L332
I'm not sure what's the best way of handling this from a Home Assistants point of view because I'm not sure what's the real error that you're having here (or any user). I already handle when the username/password is incorrect but where it failed... it didn't reach yet into a place where the credentials are being sent, meaning that it shouldn't be related to the account... So, perhaps a retry should help here?
Is the integration working for you right now?

Thanks for getting back to me on this one. So, I'm also clueless as to where it breaks and sadly no, it doesn't work for me at the moment.
I might workaround it in a hacky way by authenticating to the that endpoint then snatching session cookies then substituting them whenever your integration keeps them cached. But to do so, would like to know what could be the best place to to "plant" acquired session cookies (in order to manually authenticate and keep the integration happy)?
Best!

Alright, after toying with the library directly and capturing HTTP flow, I was able to pinpoint it down to "Invalid username or password" which was weird as I was using these creds for a few months now without any issues. It turned out Panasonic demanded me to sign up for a two-factor authentication on that account and they must have marked my account as "disabled" or so. After logging in manually via Web UI and adding my phone as a second factor, I was able to log into the integration as expected.
I think it's fair to close it now as the issue was never related to the codebase :)
Best regards!

@mgeeky believe it or not, I thought about that (not having added the phone to the account) while walking my dog and was about to write that and you just found it 😂
Glad it finally works for you!


Schema Violation: No ValueType defined in Qualifiers in multiple Submodels

According to the specification, ValueType is a mandatory attribute. However, we have noticed that ValueType is missing in the published AASX files for templates that have qualifiers. This issue occurs in several submodels, including Digital Nameplate, Contact Information, Handover Documentation, Provision of Simulation Models, Technical Data, and Time Series Data.

@Rudra-sandeep please check the issue.

@zrgt Please check the latest versions of the SMT's this issue is been resolved
https://github.com/admin-shell-io/submodel-templates/tree/main/published


openshift,istio: switch image to the stable floating tag

This changes the container image reference in the provided templates to the stable floating tag. That should point from now on to the latest stable version as it is released. Note that people actually deploying this might want to change it to specific images and manage this at their own pace, as in cases of breaking changes this will still be updated.
This will close #159.

@roivaz does this look ok as a default? Also, there are some security issues in dependencies in the currently deployed version, so I'll update the images and then someone in ops should ensure the new image is picked up.


HBASE-25186 Addendum fix compile error

@infraio

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 35s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2 Compile Tests _

-1 :x:
mvninstall
2m 19s
root in branch-2 failed.

+1 :green_heart:
checkstyle
1m  5s
branch-2 passed

-1 :x:
spotbugs
0m 37s
hbase-server in branch-2 failed.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 19s
the patch passed

+1 :green_heart:
checkstyle
1m  6s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
12m  0s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1.

+1 :green_heart:
spotbugs
2m 13s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 16s
The patch does not generate ASF License warnings.

30m 52s

Subsystem
Report/Notes

Docker
Client=19.03.13 Server=19.03.13 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2572/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2572

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle

uname
Linux b7bcaade129e 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / aa888f7e38

mvninstall
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2572/1/artifact/yetus-general-check/output/branch-mvninstall-root.txt

spotbugs
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2572/1/artifact/yetus-general-check/output/branch-spotbugs-hbase-server.txt

Max. process+thread count
94 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2572/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  6s
Docker mode activated.

-0 :warning:
yetus
0m  7s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

-1 :x:
mvninstall
2m 36s
root in branch-2 failed.

-1 :x:
compile
1m  3s
hbase-server in branch-2 failed.

-1 :x:
shadedjars
5m 23s
branch has 16 errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 41s
branch-2 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 53s
the patch passed

+1 :green_heart:
compile
1m  6s
the patch passed

+1 :green_heart:
javac
1m  6s
hbase-server generated 0 new + 4 unchanged - 2 fixed = 4 total (was 6)

+1 :green_heart:
shadedjars
6m 41s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 40s
the patch passed

_ Other Tests _

-1 :x:
unit
136m 52s
hbase-server in the patch failed.

162m 19s

Subsystem
Report/Notes

Docker
Client=19.03.13 Server=19.03.13 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2572/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2572

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux c6d5836d815d 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / aa888f7e38

Default Java
2020-01-14

mvninstall
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2572/1/artifact/yetus-jdk11-hadoop3-check/output/branch-mvninstall-root.txt

compile
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2572/1/artifact/yetus-jdk11-hadoop3-check/output/branch-compile-hbase-server.txt

shadedjars
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2572/1/artifact/yetus-jdk11-hadoop3-check/output/branch-shadedjars.txt

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2572/1/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2572/1/testReport/

Max. process+thread count
4254 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2572/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
4m 21s
Docker mode activated.

-0 :warning:
yetus
0m  7s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

-1 :x:
mvninstall
2m 19s
root in branch-2 failed.

-1 :x:
compile
0m 55s
hbase-server in branch-2 failed.

-1 :x:
shadedjars
4m 42s
branch has 16 errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 36s
branch-2 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 20s
the patch passed

+1 :green_heart:
compile
0m 56s
the patch passed

+1 :green_heart:
javac
0m 56s
hbase-server generated 0 new + 4 unchanged - 2 fixed = 4 total (was 6)

+1 :green_heart:
shadedjars
5m 55s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 36s
the patch passed

_ Other Tests _

-1 :x:
unit
138m 21s
hbase-server in the patch failed.

164m 10s

Subsystem
Report/Notes

Docker
Client=19.03.13 Server=19.03.13 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2572/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2572

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux<PHONE_NUMBER>2a 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / aa888f7e38

Default Java
1.8.0_232

mvninstall
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2572/1/artifact/yetus-jdk8-hadoop2-check/output/branch-mvninstall-root.txt

compile
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2572/1/artifact/yetus-jdk8-hadoop2-check/output/branch-compile-hbase-server.txt

shadedjars
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2572/1/artifact/yetus-jdk8-hadoop2-check/output/branch-shadedjars.txt

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2572/1/artifact/yetus-jdk8-hadoop2-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2572/1/testReport/

Max. process+thread count
4297 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2572/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.


Some questions about corner rotation to camera coordinate system

def rotation_3d_in_axis(points, angles, axis=0):
"""Rotate points in specific axis.
Args:
points (np.ndarray, shape=[N, point_size, 3]]):
angles (np.ndarray, shape=[N]]):
axis (int, optional): Axis to rotate at. Defaults to 0.
Returns:
np.ndarray: Rotated points.
"""
# points: [N, point_size, 3]
rot_sin = np.sin(angles)
rot_cos = np.cos(angles)
ones = np.ones_like(rot_cos)
zeros = np.zeros_like(rot_cos)
if axis == 1:
rot_mat_T = np.stack([[rot_cos, zeros, -rot_sin], [zeros, ones, zeros],
[rot_sin, zeros, rot_cos]])
elif axis == 2 or axis == -1:
rot_mat_T = np.stack([[rot_cos, -rot_sin, zeros],
[rot_sin, rot_cos, zeros], [zeros, zeros, ones]])
elif axis == 0:
rot_mat_T = np.stack([[zeros, rot_cos, -rot_sin],
[zeros, rot_sin, rot_cos], [ones, zeros, zeros]])
else:
raise ValueError('axis should in range')
return np.einsum('aij,jka->aik', points, rot_mat_T)

#####################################################
The question is that, I make a standard boxes in camera coordinate system(1, 8, 3). I want to rotate the box by the rotation y.
As I know, I can use the rotation matrix to time the corners. However, I get the different result by using the function. If I replace  np.einsum('aij,jka->aik', points, rot_mat_T) with points@rot_mat_T, I get the same result.

For you problems, we double check the code, we find that it indeed has some problems, the right code should be like this, and you will get the same results:
from pyquaternion import Quaternion
import numpy as np

def rotation_3d_in_axis(points, angles, axis=0):
    """Rotate points in specific axis.
    Args:
    points (np.ndarray, shape=[N, point_size, 3]]):
    angles (np.ndarray, shape=[N]]):
    axis (int, optional): Axis to rotate at. Defaults to 0.
    Returns:
    np.ndarray: Rotated points.
    """
    # points: [N, point_size, 3]
    rot_sin = np.sin(angles)
    rot_cos = np.cos(angles)
    ones = np.ones_like(rot_cos)
    zeros = np.zeros_like(rot_cos)
    if axis == 1:
        rot_mat_T = np.stack([[rot_cos, zeros, -rot_sin],
                              [zeros, ones, zeros],
                              [rot_sin, zeros, rot_cos]])
    elif axis == 2 or axis == -1:
        rot_mat_T = np.stack([[rot_cos, rot_sin, zeros],
                              [-rot_sin, rot_cos, zeros],
                              [zeros, zeros, ones]])
    elif axis == 0:
        rot_mat_T = np.stack([[ones, zeros, zeros],
                              [zeros, rot_cos, rot_sin],
                              [zeros, -rot_sin, rot_cos]])
    else:
        raise ValueError('axis should in range')
    print(rot_mat_T)
    return np.einsum('aij,jka->aik', points, rot_mat_T)

if __name__ == '__main__':
    angles = -1
    x = np.array([1.2, 1.8, 3.2]).reshape(3, 1)
    y = np.array([1.2, 1.8, 3.2]).reshape(1, 1, 3)
    rotation_y = Quaternion(axis=[0, 1, 0], radians=angles)
    a = np.matmul(rotation_y.rotation_matrix, x)
    print(rotation_y.inverse.rotation_matrix)
    print("*"*100)
    a1 = rotation_3d_in_axis(y, np.array(angles).reshape(-1), axis=1)
    print(a)
    print(a1)

The rot_mat_T actually represents the transpose of rotation matrix. For rotation matrix, the transpose equals to the inverse.
When axis=0 and axis=2, the original code of rotation_3d_in_axis is wrong.
About np.einsum, to get a better understanding of it, you can add rot_mat = rot_mat_T.transpose(0, 1), and replace np.einsum('aij,jka->aik', points, rot_mat_T) to np.einsum('aij,kja->aik', points, rot_mat_T), it should get the same results.
the code actually has been deprecated in our now developing branch, you can refer to the new version of the it in here
If you are still confused, just leave comments.

For master branch,
axis=2 will only be used when rotate box in LiDAR coordinates, and in master branch,  we follow the LiDAR coordinate system of SECOND original code which is left-handed, so there is no problem in the original code.
axis=1 will only be used when rotate box in Camera coordinates, which is a right-handed coordinate.
axis=0 is not used in our entire code, although it's indeed not right.
We refactor all the coordinates to be right-hand in v1.0.0.dev0 branch, so the code of axis=2 should be modified like what I change above.
For Quaternion, the default coordinate is right-handed, the default rotation direction should be an counter-clockwise.
Besides, here's a tutorial about the 3D rotation calculation in Chinese, https://zhuanlan.zhihu.com/p/183973440, and you can also find some other English doc. for reference if you don't know Chinese.

Thanks for your help. I can understand that in kitti, rotation_y is about the y axis, so we need to turn the vehicle clockwise to achieve the goal. The default direction of Quaternion is counterclockwise, so we need to reverse its conversion matrix. This rule is in camera coordinates Both the radar coordinate system and the radar coordinate system are applicable.

Close due to inactivity.


Add clearer ratis flush exception logging

Add the debug logging since the actual flush failure will be overwritten by the last meaningless failure like ratis.protocol.AlreadyClosedException or NoMoreRetriesException.
The actual flush failure will sometimes give us helpful information or annoying meaningless logs, that's why i mark it as debug for now. Will be better to have an exception duplication-checking and only log the no-duplicate exceptions. And also link the exception to meaningful configuration suggestions.

@LuQQiu Is there value to make this a WARN or ERROR? Why should this only be in DEBUG?

@gpang I changed it to be WARN. The logging is helpful in understanding the ratis errors. The previous debug is to avoid unnecessary annoying logs

alluxio-bot, merge this please


Cannot use React.ComponentProps

Bug report
Describe the bug
When you want to extend a styled component like this, you get type errors.
To Reproduce
import { styled } from '@stitches/react';

const StyledButton = styled('button', {});

const Button = (props: React.ComponentProps<typeof StyledButton>) => {
  return <StyledButton {...props} />
}

Type 'InternalCSS<TMedias & { initial: ""; }, { colors: { blue: string; }; }, {}, CSSPropertiesToTokenScale> | undefined' is not assignable to type 'InterpolationWithTheme<any>'.

System information

Version of Stitches: 0.0.2
Version of Typescript: 4.3.5

I've encountered this issue as well when first introducing stitches in our design system, and in our case the problem was being caused by Storybook, which internally uses @emotion/core for styling their interface.
The problem is that emotion is adding a type to all JSX and react components for their css prop, which then clashes with Stitches own css prop.
declare module 'react' {
  interface DOMAttributes<T> {
    css?: InterpolationWithTheme<any>
  }
}

declare global {
  namespace JSX {
    /**
     * Do we need to modify `LibraryManagedAttributes` too,
     * to make `className` props optional when `css` props is specified?
     */

    interface IntrinsicAttributes {
      css?: InterpolationWithTheme<any>
    }
  }
}

The workaround is to overwrite the types for the @emotion/core package on your tsconfig.json file, like so:
{
  "compilerOptions": {
     // Other options
    "paths": {
      "@emotion/core": ["./typings/emotion.d.ts"]
    },
}

And then create the file to overwrite the types typings/emotion.d.ts with the following:
declare module "@emotion/core";

This solution might not be the best one, but it allowed us to enable the css prop on our components, without having to access internal types from Stitches.

Based on discussion in https://github.com/modulz/stitches/discussions/213, this now seems to be working with React.ComponentProps in v1.0.0. Would anyone let us know if this is not the case?

Yes, everything works fine. Example on a fresh React + TS install: https://codesandbox.io/s/goofy-hooks-j9c31
More specific details for future visitors searching this error
If you use Storybook, it has Emotion as dependency that messes up the styled typing. The quick workaround is to modify the emotion type definition file like so: https://github.com/emotion-js/emotion/issues/1800#issuecomment-635288990

@jonathantneal as mentionned in #213 , the as prop is not passed from Reac.ComponentProps.

@hrasoa is correct. React.ComponentProps is now working, and this does not include the as prop. See https://github.com/modulz/stitches/discussions/213#discussioncomment-1301865


Is it Flate2 slow?

I am trying to compress ~100Mb file. But it compress 100mb file In 50 seconds.
I wonder if the library is slow or if there's an error in the code I wrote.
The output is
➜ cargo run
   Compiling logwatcher v0.1.1 (/home/kaan/Work/projects/test-oss/logwatcher)
    Finished dev [unoptimized + debuginfo] target(s) in 0.41s
     Running `target/debug/logwatcher`
Rand OK 76.752903ms
File OK 76.821752ms
Gzip OK 77.209878ms
Write OK 53.218462772s
Fnish OK 53.22517111s

Rust version
➜ rustc --version
rustc 1.50.0-nightly (f76ecd066 2020-12-15)

Cargo.toml
[package]
name = "logwatcher"
authors = ["Kaan Karakaya"]
edition = "2018"

[dependencies]
flate2 = "1.0"

Rust code
use flate2::write::GzEncoder;
use flate2::Compression;
use std::fs::File;
use std::io::prelude::*;

use std::fs;
use std::time::Instant;

fn main() -> std::io::Result<()> {
    let start = Instant::now();

    // ? deaa file is 109M file
    let con = fs::read_to_string("deaa")?;
    println!("Rand OK {:?}", start.elapsed());

    let output = File::create("den.gz").unwrap();
    println!("File OK {:?}", start.elapsed());

    // ? Gzip
    let mut gzip = GzEncoder::new(output, Compression::fast());
    println!("Gzip OK {:?}", start.elapsed());

    // ! Slow: 53 seconds for 109 mb
    gzip.write_all(con.as_bytes()).unwrap();
    println!("Write OK {:?}", start.elapsed());
    gzip.finish().unwrap();
    println!("Fnish OK {:?}", start.elapsed());

    Ok(())
}

I found the issue if I run rust with cargo run it takes 50 seconds+.
But if I build with release option it takes 1 second


CI: Delay gather of junit files

Because junit file checking will fail the job completely, we want
to make sure that we delay it to the bottom of the post actions
so we gather the rest of the logs first
Why is this PR needed?
Does it fix an issue? addresses a business case?
add a description and link to the issue if one exists.
Fixes #
Reminder: Add the "fixes bsc#XXXX" to the title of the commit so that it will
appear in the changelog.
What does this PR do?
please include a brief "management" technical overview (details are in the code)
Anything else a reviewer needs to know?
Special test cases, manual steps, links to resources or anything else that could be helpful to the reviewer.
Info for QA
This is info for QA so that they can validate this. This is mandatory if this PR fixes a bug.
If this is a new feature, a good description in "What does this PR do" may be enough.
Related info
Info that can be relevant for QA:

link to other PRs that should be merged together
link to packages that should be released together
upstream issues

Status BEFORE applying the patch
How can we reproduce the issue? How can we see this issue? Please provide the steps and the prove
this issue is not fixed.
Status AFTER applying the patch
How can we validate this issue is fixed? Please provide the steps and the prove this issue is fixed.
Docs
If docs need to be updated, please add a link to a PR to https://github.com/SUSE/doc-caasp.
At the time of creating the issue, this PR can be work in progress (set its title to [WIP]),
but the documentation needs to be finalized before the PR can be merged.
Merge restrictions
(Please do not edit this)
We are in v4-maintenance phase, so we will restrict what can be merged to prevent unexpected surprises:
What can be merged (merge criteria):
    2 approvals:
        1 developer: code is fine
        1 QA: QA is fine
    there is a PR for updating documentation (or a statement that this is not needed)

closing and pushing it to PR-1015 instead to have all fixes together


Added notes for first-time users

Added section 'First Time Running uPortal via uPortal-start'

Checklist

[x ] commit message follows commit guidelines
[x ] documentation is changed or added

Description of change

First time installing/running uPortal5 / uPortal-start and gathered some learning points into this 'first time users' section.

Added some modifications as per @ChristianMurphy


text=True no longer works

I'm running Python 3.6, and got errors like this:
Traceback (most recent call last):
  File "/Users/george/gitdates.py", line 79, in <module>
    main()
  File "/Users/george/gitdates.py", line 29, in main
    exc = sp.run(exargs, stdout=sp.PIPE, stderr=sp.DEVNULL, text=True).stdout.split()
  File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/subprocess.py", line 423, in run
    with Popen(*popenargs, **kwargs) as process:
TypeError: __init__() got an unexpected keyword argument 'text'

It seems like the Popen (and therefore the run) interface has changed in 3.7 to allow just "text=True", rather than 3.6 which requires a specific encoding . Here's a patch that works on 3.6, but I haven't tested it on 3.7 (or pre-3.6):
diff ~/gitdates.py~ ~/gitdates.py
29c29
<     exc = sp.run(exargs, text=True, stdout=sp.PIPE, stderr=sp.DEVNULL).stdout.split()
---
>     exc = sp.run(exargs, stdout=sp.PIPE, stderr=sp.DEVNULL, encoding='ascii').stdout.split()
66c66
<         b = sp.run(args, stdout=sp.PIPE, stderr=sp.DEVNULL, text=True, check=True).stdout
---
>         b = sp.run(args, stdout=sp.PIPE, stderr=sp.DEVNULL, check=True, encoding='ascii').stdout

The thing is that encoding="ascii" is bound to fail with e.g. unicode filenames. I'll change text to universal_newlines. That should work with 3.6.


CSP can break fallback for waitAsync

First of all, big thank you for your work! Your software is always top notch. Many kudos to you ❤
I think in v1 coincident was also prone to such issue unfortunately. The main thing is that I don't want to add data: to my content-security-policy, but without this, Firefox users will be unable to use website, because it sill doesn't support Atomics.waitAsync() and fallback worker:
https://github.com/WebReflection/sabayon/blob/9f3293e1ec14932738fc61f4c65ddcf7b263dc23/src/shared.js#L85
also wont be loaded, because content-security-policy will disallow to run javascript from data:.
So, the reproduction can be as such:

add content-security-policy: default-src 'self' to response headers of the size;
try to make use of function in worker in Firefox;

I thought about how to resolve this and the only thing that came to my mind is to add escape hatch for users via self hosted worker. So fallback will try to load /__sabayon_async_fallback.js (for example) instead of inline data:.... This will be allowed by csp, because it is self resource.

Firefox users will be unable to use website, because it sill doesn't support Atomics.waitAsync()

this is a Firefox issue to me though ... I can't make this portable or more cumbersome for Firefox sake but I like your idea:

add escape hatch for users via self hosted worker

the gotcha is that it MUST do exactly what my data does:
onmessage=e=>postMessage(!Atomics.wait(...e.data))

the last gotcha is how am I supposed to pass that fallback URL to a generic patch, because IIRC CSP doesn't throw in JS, it throws in the browser, and on top of that, /__sabayon_async_fallback.js might be too broad of a scope + people don't usually like js files at the root of their sites ... but, if you have any idea how to feature-detect the fact Firefox will throw ('cause maybe it does already, I haven't tested locally with CSP enabled) I might consider that and provide a best-effort fallback for /__sabayon_wait_async.js and let users find out the best way to provide that.

Aha ... you know what, that fallback is async anyway so actually I could simply fetch that file and provide it as fallback if found, use the data: thing otherwise ... this should work, but it will show weird things on the network panel ... would that work?

@logotip4ik fixed by checking HEAD once for the existence of /__sabayon_wait_async.js ... it fallsback to data:... if that file is nowhere reachable.

Sorry for long delay, checked in my local repo and it works flawlessly, thanks! Glad you liked my idea. Also thanks for investigation and deep messages, it's always a pleasure to read them


Hapi 17

This pulls latest changes from upstream and tweaks the code to work with hapi v17.

@superdav42, any suggestions for how to test this one locally?
Do you think this will break backwards compatibility with older versions of hapi? I just ask because we may want to keep that in mind if we need to roll back the Connect Server change and would then need to roll this back too.

@superdav42, any suggestions for how to test this one locally?

npm run test? Actually see below.

Do you think this will break backwards compatibility with older versions of hapi? I just ask because we may want to keep that in mind if we need to roll back the Connect Server change and would then need to roll this back too.

In that case think it might be best just to leave this as a separate branch. It's possible to tell npm to use a specific branch so we'll just do that for now until we are confident things will work.
So update the package.json require statement to "hapi-statsd": "github:Automattic/hapi-statsd#hapi-17", and then make sure statsd is being triggered in our app as it should be. I'm working an a unit test for it too.

👋 Hi @c-shultz, we are at this time again to upgrade Hapi to 21 and I come across this. I am planning to branch off the Hapi v21 work off this branch and merge that directly to master. If it fails, then I will roll back to the hapi-17 branch.
If all looks good, I will delete this branch since the new code will be in master.


Improving the extensibility of the DefaultClusterRenderer

This would simplify the overriding of the DefaultClusterRenderer rendering behaviour

I signed it!
googlebot<EMAIL_ADDRESS>schrieb am Mo., 11. Apr. 2016 um
13:54 Uhr:

Thanks for your pull request. It looks like this may be your first
contribution to a Google open source project. Before we can look at your
pull request, you'll need to sign a Contributor License Agreement (CLA).
[image: :memo:] Please visit https://cla.developers.google.com/
https://cla.developers.google.com/ to sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll
verify. Thanks.

If you've already signed a CLA, it's possible we don't have your
GitHub username or you're using a different email address. Check your
existing CLA data https://cla.developers.google.com/clas and verify
that your email is set on your git commits
https://help.github.com/articles/setting-your-email-in-git/.
If you signed the CLA as a corporation, please let us know the
company's name.

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/googlemaps/android-maps-utils/pull/271#issuecomment-208307337


Web - Invalid value in Timepicker (input mode) changes input field size.

Steps to Reproduce

Execute flutter run on the code sample or open Dartpad example
When I change the timepicker to manual input mode and then give invalid values like hours > 24 or Minutes > 60 then the size of the invalid box changes and shrinks. (see images)

Expected results:
The expected result would be that the box does not get smaller, when the value is invalid.

Actual results:
The Box gets smaller when an invalid value is used.

Code sample
import 'package:flutter/material.dart';

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter TimePicker',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: MyHomePage(),
    );
  }
}

class MyHomePage extends StatefulWidget {
  @override
  _MyHomePageState createState() {
    return _MyHomePageState();
  }
}

class _MyHomePageState extends State<MyHomePage> {
  TimeOfDay selectedTime = TimeOfDay.now();
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text("Flutter TimePicker"),
      ),
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            ElevatedButton(
              onPressed: () {
                _selectTime(context);
              },
              child: Text("Choose Time"),
            ),
            Text("${selectedTime.hour}:${selectedTime.minute}"),
          ],
        ),
      ),
    );
  }

  _selectTime(BuildContext context) async {
    final TimeOfDay? timeOfDay = await showTimePicker(
      context: context,
      initialTime: selectedTime,
      initialEntryMode: TimePickerEntryMode.dial,
    );
  }
}

Tested on

stable 2.10.5
beta 2.13.0 - 0.3.pre

Thanks for the report. This seems to be only occuring on web and that too using canvaskit, as, using html rendering, it works as expected along with on mobile (ios) and desktop (macos):

Web - canvaskit:

Web - html, mobile and macOS:

 stable, master flutter doctor -v

[✓] Flutter (Channel stable, 2.10.5, on macOS 12.2.1 21D62 darwin-x64, locale
    en-GB)
    • Flutter version 2.10.5 at /Users/dhs/documents/fluttersdk/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 5464c5bac7 (12 hours ago), 2022-04-18 09:55:37 -0700
    • Engine revision 57d3bac3dd
    • Dart version 2.16.2
    • DevTools version 2.9.2

[!] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    ! Flutter recommends a minimum Xcode version of 13.
      Download the latest version or update via the Mac App Store.
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] VS Code (version 1.62.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.21.0

[✓] Connected device (5 available)
    • SM G975F (mobile)       • RZ8M802WY0X • android-arm64   • Android 11 (API 30)
    • Darshan's iphone (mobile)  • 21150b119064aecc249dfcfe05e259197461ce23 •
      ios            • iOS 14.4.1 18D61
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729     •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                    •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                                   •
      web-javascript • Google Chrome 98.0.4758.80

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

[✓] Flutter (Channel master, 2.13.0-0.0.pre.1006, on macOS 12.2.1 21D62
    darwin-x64, locale en-GB)
    • Flutter version 2.13.0-0.0.pre.1006 at
      /Users/dhs/documents/fluttersdk/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision f86dfdd2b7 (69 minutes ago), 2022-05-10 10:24:08 +0530
    • Engine revision 8774c24f65
    • Dart version 2.18.0 (build 2.18.0-99.0.dev)
    • DevTools version 2.13.1

[!] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    ! Flutter recommends a minimum Xcode version of 13.
      Download the latest version or update via the Mac App Store.
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] VS Code (version 1.62.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.21.0

[✓] Connected device (5 available)
    • SM G975F (mobile)       • RZ8M802WY0X • android-arm64   • Android 11 (API 30)
    • Darshan's iphone (mobile)  • 21150b119064aecc249dfcfe05e259197461ce23 •
      ios            • iOS 14.4.1 18D61
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729     •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                    •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                                   •
      web-javascript • Google Chrome 98.0.4758.80

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

According to #103635 this is related to https://github.com/flutter/flutter/issues/75837, possibly a duplicate.

Duplicate of https://github.com/flutter/flutter/issues/110563


Bump ubuntu-next VM image to v49

The new image version includes "Various improvements to cgroup helpers" [1] from @borkmann
[1]<EMAIL_ADDRESS>

test-me-please

Coverage increased (+0.01%) to 45.529% when pulling b4bc6fad71a234c45bc051dddc808a23b5fa8e1f on pr/brb/bump-ubuntu-next into ba0fd4ced4f8d2257b058f2eb0dd7078f0cf14cd on master.

Close in favor of #10775 .


Azure Firewall Manual Scale

ARM (Control Plane) API Specification Update Pull Request

[!TIP]
Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

Purpose of this PR
What's the purpose of this PR? Check the specific option that applies. This is mandatory!

[ ] New resource provider.
[ ] New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been created in adherence to OpenAPI specs PR creation guidance).
[x] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix OpenAPI spec quality issues in S360.
[ ] Other, please clarify:

edit this with your clarification

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[x] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[x] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.

Additional information

 Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.

Getting help

First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
For help with ARM review (PR workflow diagram Step 2), see https://aka.ms/azsdk/pr-arm-review.
If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

Was already approved
https://github.com/Azure/azure-rest-api-specs-pr/pull/17162

The model failure seems due to it being a new version with new enforcement. We can add this to the Firewall backlog to fix.

Was approved and not merged
https://github.com/Azure/azure-rest-api-specs-pr/pull/17162


Send image from server to client

Hello, сan you tell right way to send image+text instead only text from server:
$ws_worker->onMessage = function($connection, $data) {
$connection->send('hello');
};
to client:
ws.onmessage = function(e) {
document.write("recv message from server: " + e.data);
};

You can send img tag like <img src='your_pic.jpg'> to client.
It will be downloaded automatically by HTTP when the browser renderings the img tag.

You mean transfer from the server to the client via the websocket only a link to the file, and on the client through JavaScript to show in the browser. Correctly?

yes


WIP: Adding FFT object factory methods

Draft PR for relying on object factory methods for constructing FFT classes with different backends. Implementation is based on itk::GPUImage.
Note that this draft is a proof of concept, not all FFT classes have been updated yet.

PR Checklist

[ ] No API changes were made (or the changes have been approved)
[ ] No major design changes were made (or the changes have been approved)
[ ] Added test (or behavior not changed)
[ ] Updated API documentation (or API not changed)
[ ] Added license to new files (if any)
[ ] Added Python wrapping to new files (if any) as described in ITK Software Guide Section 9.5
[ ] Added ITK examples for all new major features (if any)

Refer to the ITK Software Guide for
further development details if necessary.

Starting to have success in using object factories to generate a default Vnl backend for itk::Forward1DFFTImageFilter (woo!), but would appreciate extra insight into how ITK handles the CMake / export side of object factory implementation details.
@dzenanz @thewtex @N-Dekker Do you have any thoughts on the above discussions? Thanks in advance for your help.

If you want something accessible in bottom scope, you should define in in parent scope before entering that subdirectory.

Per @thewtex it is valid to require tests to manually register FFT object factories with the understanding that consuming cxx projects will call UseITK.cmake for appropriately injecting factory code and Python projects already run UseITK.cmake for setting up factories at build time by default. Hence we are much closer to a functioning change here than previously thought 😃

Current PR status:

[x] Cxx tests build and pass locally. Factories are manually registered.
[ ] Python tests do not pass locally. Factories are not being registered as expected?
[x] FFT example modified for Forward1DFFTImageFilter builds and passes. Verified with dynamic_cast that default factories are loaded and the first constructed FFT instance has a Vnl backend.

￼ Python tests do not pass locally. Factories are not being registered as expected?

We may want to bite the bullet and inject the factor registration call for wrapped factory classes call in igenerator.py.

@thewtex I can take a look. Do you have any thoughts on how ImageIO default factories may be registered while FFT factories are not?

This may be a side effect of wrapping itk.ImageFileWriter, itk.ImageFileReader.

I was worried about that 😅 I suppose it's not reasonable for object factory classes to always have another class like ImageFileWriter, etc. to handle factory registration. I'll start digging into igenerator.py.

Python wrapping seems to be working now, maybe due to wrapping VnlForward1DFFTImageFilter? Wrapping does not seem to be required for IO factories to work, so... 🤷♂
I've confirmed on my side that the Forward1DFFTImageFilter constructor in Python returns a Vnl backend by default:
>>> import itk
>>> itk.auto_progress(2)
>>> f = itk.Forward1DFFTImageFilter[itk.Image[itk.F,2]].New()
Loading ITKPyBase... done
Loading ITKCommon... done
Loading ITKStatistics... done
Loading ITKImageFilterBase... done
Loading ITKTransform... done
Loading ITKImageFunction... done
Loading ITKImageGrid... done
Loading ITKFFT... done
Loading ITKPyUtils... done
>>> itk.VnlForward1DFFTImageFilter[itk.Image[itk.F,2]].cast(f)
<itk.itkVnlForward1DFFTImageFilterPython.itkVnlForward1DFFTImageFilterIF2; proxy of <Swig Object of type 'itkVnlForward1DFFTImageFilterIF2 *' at 0x00000209EFF4E420> >

Injecting factory calls in igenerator.py and targeting CMake projects for factory default registration with itk_configure_factory would both be directly relevant to FFT object factory registration and can be explored in subsequent PRs.


status: revisualize to enhance UX

Thanks for such a great tool! I have some feedback about the status command.

Use Tree Structure

Currently, status command prints a big table that is slightly complicated and hard to distinguish. It would be great to list all containers in tree structure, for example:
NAMESPACE  NAME                          READY  RUNNING  REASON  AGE
aa         Pod/foo-6f67dcc579-znb55      True   -                10m
aa         └─Container/first-container   -      True
aa         └─Container/second-container  -      True

Timestamp is too detailed

 TIMESTAMP
 2022-06-17 10:34:57 +0300 +03

Do we really need to see date/second details? We can create a new flag called --details to expand timestamp. Otherwise, just current time is fine: 10:34:57

MESSAGE is really necessary?

I am not sure how we can use MESSAGE column since the terminal has limited width. Currently I see all values set to -.
Any thougts?

I agree the status output does look messy, I also like the idea of a tree view, biggest issues are that the sort flag would break the tree view and the table output code would also need a bit of a rewrite to make this possible.
I believe that removing the date will cause confusion but I may be able to remove the time zone info.  I'll have to look into it first though.
the MESSAGE column is populated with the error description when containers fail to start/load, ill have a play with it, I might be worth moving it to the details flag you mentioned

I have added the --tree flag to the status command so you end up with something like the below, I have also moved the message and timestamp columns to the --details flag
$ kubectl-ice status -l app=myapp --tree
NAMESPACE  NAME                      READY  STARTED  RESTARTS  STATE       REASON            AGE
ice        Pod/web-pod               -      -        0         Running     -                 10m
ice        └─Container/app-broken    false  false    6         Waiting     CrashLoopBackOff  -
ice        └─Container/app-watcher   false  false    6         Waiting     CrashLoopBackOff  -
ice        └─Container/myapp         true   true     0         Running     -                 10m
ice        └─InitContainer/app-init  true   -        0         Terminated  Completed         10m

I don't currently pull the extra information needed to be able to display things like that.  Ill add it to the "maybe in the future" list

this has now been updated


How to create one time markup?

When I create a keyboard, it is shown every time. How can I make it so that after pressing the button, the keyboard disappears?
Now I use this code and the keyboard does not disappear after pressing:
let replyMarkup = bot.keyboard([
    ['button1'],
    ['button2']
], {resize: true});

Just add a { once: true } parameter:
bot.keyboard([
    ['button1'],
    ['button2']
], {
    resize: true,
    once: true
});

@mullwar Thanks!


Added a CommitteeFeedMessage entity

Closes EM-46.

Until #174 and #184 review only last commit e328b03.


OpenAPI generation broken at Enum

There is something wrong in my code when i do aqueduct document it fails with this:
-- Aqueduct CLI Version: 3.2.0+1
-- Aqueduct project version: 3.2.0+1
*** Uncaught error
    Bad state: Invalid argument(s): Illegal argument in isolate message : (object is a regular Dart Instance)
  **** Stacktrace
  * #0      _SendPortImpl._sendInternal (dart:isolate/runtime/libisolate_patch.dart:218:70)
  * #1      _SendPortImpl.send (dart:isolate/runtime/libisolate_patch.dart:202:5)
  * #2      main (<data:application/dart>:13:12)
  * <asynchronous suspension>
  * #3      _startIsolate.<anonymous closure> (dart:isolate/runtime/libisolate_patch.dart:296:32)
  * #4      _RawReceivePortImpl._handleMessage (dart:isolate/runtime/libisolate_patch.dart:171:12)
  ****

But aqueduct serve does work and i tried a sample project and there aqueduct document does work. https://github.com/ewoudje/rulers_of_states/tree/master/server

I've found the source from the error it was an enum in a ManagedObject. Is this expected behavior? I thought it was allowed for an enum?

Yes, there is a bug with enums. It will be fixed in 3.2.1

I also got with the same error. Good thing you fixed it. Waiting for release.

3.2.1 release is now available on pub.


Bug fix: 12 words - move cursor position to the end

🗃 Github Issue Or Explanation for this PR. (What is it supposed to do and Why is needed)
#1640
✅ Checklist

[x] Github issue details are up to date for people to QA.
[x] I have tested all my changes.

🕵♂ Notes for Code Reviewer
Fix at UI level
👯♀ Paired with
"nobody"

Thank you! ❤


"Error: 'NoneType' object is not iterable" using sonos-discover

Hello Team!
I am getting the following error while trying to utilize sonos-discover to use soco-cli.
Error: 'NoneType' object is not iterable
(soco-cli)  ~/projects/temp/soco-cli$ sonos-discover -t 256 -n 1.0 -m 16
Error: 'NoneType' object is not iterable

(soco-cli)  ~/projects/temp/soco-cli$ sonos-discover
Error: 'NoneType' object is not iterable

On the first command I was using -m 16 due to my sonos devices being on a different vlan than my computer. I was not able to find a way to manually create a cached set of devices to use in soco-cli.
I setup my env the following way
pipenv install --python 3
pipevn shell
pipenv install soco-cli

Python = Python 3.8.6
OS = POP_OS 20.10
What else can I provide or dig into looking at this?

Hi:
Could you provide the output of the following commands, please?

sonos -v
sonos-discover -t 256 -n 1.0 -m 16 --log=info

Thanks.

I think I know where the exception arises, and I've addressed this in v0.3.30 by providing a more meaningful error message, namely No speakers discovered. No cache data saved or overwritten.
However, this doesn't address your root problem, which is that no devices are found by the network search. Are you sure the speaker IPs are reachable from the computer on which you're running SoCo-CLI?
Please do still provide the outputs (1) and (2) requested above; it will tell us what networks are discovered and searched. Thanks.

Hi @pwt
Here is the info you asked for
(soco-cli)  ~/projects/temp/soco-cli$ sonos -v
soco-cli version: 0.3.29
soco version:     0.21.3
python version:   3.8.6

(soco-cli)  ~/projects/temp/soco-cli$ sonos-discover -t 256 -n 1.0 -m 16 --log=info
2021-04-03 14:37:11,006 discovery.py:550 - _find_ipv4_networks() - Set of networks to search: {IPv4Network('<IP_ADDRESS>/24')}
2021-04-03 14:37:11,032 discovery.py:335 - scan_network() - Created 256 scanner threads
2021-04-03 14:37:12,033 discovery.py:340 - scan_network() - All 256 scanner threads terminated
2021-04-03 14:37:12,033 discovery.py:344 - scan_network() - No Sonos zones discovered
Error: 'NoneType' object is not iterable

I noticed with the log info that it does not seem to be pulling in the cider from -m flag. That might be why it cannot see the devices on 192.168.70.* network which is where my sonos system lives.
I installed the socos library and when I pass in the IP of one of my devices it returns.
(socos)  ~/projects/temp/socos$ socos info <IP_ADDRESS>
zone_name: Office
zone_icon:
uid: None
serial_number: REDACTED
software_version: 62.1-86220
hardware_version: <IP_ADDRESS>-1.1
mac_address: REDACTED

I was also able to get the track info using a python script and soco that I passed in the IP.
#!/usr/bin/env python3
from soco import SoCo
from pprint import pprint

if __name__ == '__main__':
    device = SoCo('<IP_ADDRESS>') # Pass in the IP of your Sonos speaker
    track = device.get_current_track_info()
    print(f"Now Playing {track['title']} By  {track['artist']}")

(soco)  ~/projects/temp/soco$ python track.py
Now Playing Stupid Minds (Polished Chrome Remix) By  Sine

I understand networking troubleshooting can be painful, is there a work around I could use. Maybe creating my own cached discovery list file and using the -l flag when running?

Great, thanks for the info.
Interesting use case; the first example reported where the Sonos speakers reside on a different subnet from the controlling device. Fortunately, when I wrote the recent discovery code in the SoCo library, I included the ability to specify which subnets to search, to override the networks determined from interface inspection.
In SoCo-CLI v0.3.32 (available now), I've added a --subnets option to sonos-discover. In your case you should be able to use: sonos-discover --subnets <IP_ADDRESS>/24 to discover your speakers and cache the results. Let me know if this works.
(You could probably also just specify the IP address of one of your speakers, if you know it, and the others will be discovered too: sonos-discover --subnets <IP_ADDRESS>.)
Incidentally, you can always use IP addresses directly with SoCo-CLI if you want to, e.g.: sonos <IP_ADDRESS> info.
Finally, for completeness, the -m option will only ever constrain the netmask, never increase it. It's there to control the size of the search space.

I'm going to close this issue now. Please reopen if your issue is not resolved.


Uncaught Error: Cannot find module './pages/app'

What version of WebTorrent Desktop? (See the 'About WebTorrent' menu)
Version 0.13.1 (0.96.4) - b93f41f564d2838fa1354d94e55f99aede6cc068
What operating system and version?
Arch Linux x64
What did you do?
Seeded some low-peer torrents and restarted app.
What did you expect to happen?
See the list of torrents.
What actually happened?

I was experiencing #854 so I updated to the latest commit in hopes to fix the issue, however I am presented with the same issue but with a new exception.
Here is my config.json: [REMOVED]
Thanks!

Thanks for reporting, both errors should be fixed in the next release.
Right now you would have to remove all torrent entries with "status": "new" from your config.json.
For future reference I recommend that people do not post their config.json.
@dcposch We may want to release soon, to decrease #854 related errors.

@mathiasvr sounds good, i'll try to ship an 0.14 release later today

Just a heads up, without modifying my current config.json and on the latest commit 11f8e428a0ffcbafc7e598038b36c88fd26f0c22 I'm getting the following error:
Uncaught Error: Cannot find module '../components/heading'

@anoadragon453 are you sure you're on that commit? I recommend quitting WebTorrent completely (make sure you don't have the installed app running), then starting again.
I thought that bug was fixed weeks ago.
Check your working directory. All files under src/ should be all lowercase.
If you do have src/renderer/components/Heading.js (incorrectly uppercase), then try setting the following option:
git config --global core.ignorecase false

I did a fresh install of the webtorrent-desktop-git AUR package which should grab the latest commit every time, but I'll do a manual got clone and build in a bit to make sure.
On September 4, 2016 9:30:50 AM PDT, DC<EMAIL_ADDRESS>wrote:

@anoadragon453 are you sure you're on that commit? I recommend
quitting WebTorrent completely (make sure you don't have the installed
app running), then starting again.
I thought that bug was fixed weeks ago.
Check your working directory. All files under src/ should be all
lowercase.
If you do have src/renderer/components/Heading.js (incorrectly
uppercase), then try setting the following option:
git config --global core.ignorecase false

--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/feross/webtorrent-desktop/issues/875#issuecomment-244613131


Review Comments on Storage Chapter

Storage Maps
https://docs.substrate.io/v3/runtime/storage#storage-items
Not sure we should be calling it hash map.
It's definitely not a hash map as commonly used in programming. (But of course it tries to provide a similar interface and a somewhat similar use case of random lookup.)
Exceeding Block Time
https://docs.substrate.io/v3/runtime/storage#storage-value

Furthermore, iterating over a large list in your runtime may result in exceeding the block production time. If this occurs your blockchain will stop producing blocks, which means that it will stop functioning.

This is only true for parachains.
A sovereign chain will likely not stop producing blocks because of excessive block times. It will just slow down.
Storage N Map
The link to the Storage N Map rust docs is missing here: https://docs.substrate.io/v3/runtime/storage#n-storage-map
Links to NMaps seem to be missing in general, e.g. https://docs.substrate.io/rustdocs/latest/frame_support/storage/trait.IterableStorageNMap.html is not linked in the storage iteration section.
Storage Map Iteration

Substrate Storage Maps are iterable with respect to their keys and values.

This depends on the hasher. It is only really true for the concat and identity hashers.
(Though I guess you could iterate the prefix of a double map that has an opaque hash as its second key, you just wouldn't know what the keys are.)
AFAICT The heading is the wrong size. I cannot link to it.

Substrate's Iterable Storage Map interfaces define the following methods (note that for Iterable Storage Double Maps, the iter() and drain() methods require the first key as a parameter):

This does not seem true to me? The key is necessary for the iter_prefix function that only iterates the (second) keys and values under a (first) key.
Best Practices Note

In general, Substrate focuses on "first principles" as opposed to hard and fast rules of right and wrong.

Suggestion:

In general, Substrate focuses on programming according to principles and best practices as opposed to hard and fast rules of right and wrong.

related to https://github.com/substrate-developer-hub/substrate-docs/pull/211


minor grappler controller bugs

fixed (str.format bug when using HierarchicalController methods with verbose=True
fixed binary str vs str mismatch bug in controller.py and hierarchical_controller.py

Nagging Assignee @benoitsteiner: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

It has been 14 days with no activity and the awaiting response label was assigned. Is this PR still valid? Assigning the stalled label. Please comment to reassure me that this is still being worked on.

It has been 43 days that this pull-request has stalled. Please create a new pull-request with the requested changes.


For the cifar10 example calculate delta function issue

🐛 Bug

I debug the cifar10 example. For '''flsim/clients/base_client.py -> delta = self.compute_delta()''' pass the three-parameter "before", "after" and "model_to_save". And '''after=updated_model, model_to_save=updated_model''' And for the compute_delta function, it is return updated_model, it didn't calculate any difference.
To Reproduce

:warning: We cannot help you without you sharing reproducible code. Do not ignore this part :)
Steps to reproduce the behavior:

Expected behavior

Environment
Please copy and paste the output from our
environment collection script
(or fill out the checklist below manually).
You can get the script and run it with:
wget https://raw.githubusercontent.com/pytorch/pytorch/master/torch/utils/collect_env.py
# For security purposes, please check the contents of collect_env.py before running it.
python collect_env.py

PyTorch Version (e.g., 1.0):
OS (e.g., Linux):
How you installed PyTorch (conda, pip, source):
Build command you used (if compiling from source):
Python version:
CUDA/cuDNN version:
GPU models and configuration:
Any other relevant information:

Additional context

Hey, can you provide a notebook on how we can reproduce this bug? We have a unit test which tested this function.
https://github.com/facebookresearch/FLSim/blob/main/flsim/clients/tests/test_client.py#L288


Remove special case to remove events without SyncID

The synchronization of calendar events current removes events whose metadata contains an empty sourceID.
In https://github.com/inovex/CalendarSync/blob/f20ba800ed273ca111930472ef96872637fad848/internal/sync/controller.go#L204-L208
For Outlook calendars the event metadata is only set if a CalendarSync-specific extension exists in the event. For the Google calendar, the metadata exists if any field in the ExtendedProperties of an event is set. The latter could become a problem if other tools create calendar events and also use the ExtendedProperties field. Thus, I think we should just remove the special case for these calendar events.
To prevent potential naming conflicts, it would also be a good idea to prefix our event metadata in the Google calendar events with e.g. inovex.calendarsync.meta. (the field name just has to stay within a 44 characters limit).

Fixed by https://github.com/inovex/CalendarSync/pull/38


Print message on last line

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I have read the Contribution Guidelines

Issue Description
I have a situation where I'd like to provide instructions to the user after a lane has completed.  Currently I use puts but the message is hidden by the summary.  So nobody sees it.  This could be achieved by either hiding the summary or a custom message shown after the summary.  AFAIK this is not possible.  I'd be happy to submit a PR if you can let me know what option, if any, you'd prefer.  Thanks!

What kind of message is it? Is it always the same one? You could do fastlane beta && echo "Hi"

I'll close this issue for now


[DatePicker] Missing `Date(value,0) to not return to the previous year

Datepicker views={['year']} you need put new Date(value,0) only for this view if you not put that return always previus year, i create a custom value and custom on change for this reason, thanks for this amazing ui

Hey @angelqva, thanks for the input. I'm afraid you need to elaborate a bit more on your request. I tried to change the issue title to something that makes more sense but feel free to update it. Also, make sure you follow the bug report issue template for better identification of what's wrong.


(Metrics User Guide) Fix link to stackdriver metrics

The old link here: https://github.com/kubernetes-sigs/multi-tenancy/blob/master/doc/metrics/stackdriver-gke.md
Is not a 404, need to find where it went and update the docs to point to it here:
https://github.com/kubernetes-sigs/hierarchical-namespaces/blob/master/docs/links.md

Looks like it's here:
https://github.com/kubernetes-sigs/multi-tenancy/blob/master/incubator/hnc/docs/user-guide/how-to.md#admin-metrics
On Tue, May 4, 2021 at 5:33 PM Ryan Bezdicek @.***>
wrote:

The old link here:
https://github.com/kubernetes-sigs/multi-tenancy/blob/master/doc/metrics/stackdriver-gke.md
Is not a 404, need to find where it went and update the docs to point to
it here:
https://github.com/kubernetes-sigs/hierarchical-namespaces/blob/master/docs/links.md
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes-sigs/hierarchical-namespaces/issues/7, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AE43PZAKBGEIMEKNJSRNVBLTMBR27ANCNFSM44DPRLQA
.