Hero Image in the Box Error

JSON:
{
  "type": "bubble",
  "size": "mega",
  "direction": "ltr",
  "hero": {
    "type": "box",
    "layout": "vertical",
    "contents": [
      {
        "type": "box",
        "layout": "horizontal",
        "contents": [
          {
            "url": "https://scdn.line-apps.com/n/channel_devcenter/img/fx/01_1_cafe.png",
            "flex": 1,
            "size": "full",
            "type": "image",
            "action": {
              "type": "uri",
              "label": "action",
              "uri": "https://line.me/R/home/public/post?id=665xzprl&postId=1168603399615311352"
            },
            "gravity": "center",
            "aspectMode": "cover",
            "aspectRatio": "1:1"
          }
        ]
      }
    ],
    "paddingAll": "0px"
  }
}

Thx for your report. It already fixed

Thank you! You're very efficient. Have a beautiful day.

I apologize for bothering you again.
While I have resolved my own issue, I recently stumbled upon an error that occurs with a sample hero.

I believe this is something that may affect many users and wanted to bring it to your attention.
Also, feel free to reach out if you need any assistance.
JSON:
{
"type": "bubble",
"hero": {
"type": "image",
"url": "https://scdn.line-apps.com/n/channel_devcenter/img/fx/01_1_cafe.png",
"size": "full",
"aspectRatio": "20:13",
"aspectMode": "cover",
"action": {
"type": "uri",
"uri": "http://linecorp.com/"
}
}
}

already fixed krab please pull again.
thankyou for your help me to test. please feel free to send feedback to me
^^
On Tue, Jun 20, 2023 at 3:13 PM albert20699 @.***>
wrote:

I apologize for bothering you again.
While I have resolved my own issue, I recently stumbled upon an error that
occurs with a sample hero.
https://developers.line.biz/flex-simulator/
I believe this is something that may affect many users and wanted to bring
it to your attention.
Also, feel free to reach out if you need any assistance.
JSON:
{
"type": "bubble",
"hero": {
"type": "image",
"url": "
https://scdn.line-apps.com/n/channel_devcenter/img/fx/01_1_cafe.png",
"size": "full",
"aspectRatio": "20:13",
"aspectMode": "cover",
"action": {
"type": "uri",
"uri": "http://linecorp.com/"
}
}
}
—
Reply to this email directly, view it on GitHub
https://github.com/PamornT/flex2html/issues/10#issuecomment-1598321511,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEPPYYBKSCDUKO67NPNVG3XMFLSXANCNFSM6AAAAAAZLLUZCQ
.
You are receiving this because you modified the open/close state.Message
ID: @.***>


gui: bug with "Select All Nets" button

Describe the bug
When selecting instances on the gui, clicking with right mouse button and going to "Select All Nets" nothing happens, this is also the case with the highlight option.
Expected Behavior
Show the nets connected to the instance.
Environment
[WARNING] Your current OpenROAD version is outdated.
It is recommened to pull the latest changes.
If problem persists, file a github issue with the re-producible test case.
kernel: Linux 6.8.0-1015-gcp
os: Ubuntu 22.04.5 LTS (Jammy Jellyfish)
cmake version 3.24.2
-- The CXX compiler identification is GNU 11.4.0
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- OpenROAD version: v2.0-17475-gf6a30a60b
-- System name: Linux
-- Compiler: GNU 11.4.0
-- Build type: RELEASE
-- Install prefix: /usr/local
-- C++ Standard: 17
-- C++ Standard Required: ON
-- C++ Extensions: OFF
-- The C compiler identification is GNU 11.4.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Performing Test C_COMPILER_SUPPORTS__-Wall
-- Performing Test C_COMPILER_SUPPORTS__-Wall - Success
-- Performing Test CXX_COMPILER_SUPPORTS__-Wall
-- Performing Test CXX_COMPILER_SUPPORTS__-Wall - Success
-- Performing Test C_COMPILER_SUPPORTS__-Wno-array-bounds
-- Performing Test C_COMPILER_SUPPORTS__-Wno-array-bounds - Success
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-array-bounds
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-array-bounds - Success
-- Performing Test C_COMPILER_SUPPORTS__-Wno-nonnull
-- Performing Test C_COMPILER_SUPPORTS__-Wno-nonnull - Success
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-nonnull
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-nonnull - Success
-- Performing Test C_COMPILER_SUPPORTS__-Wno-maybe-uninitialized
-- Performing Test C_COMPILER_SUPPORTS__-Wno-maybe-uninitialized - Success
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-maybe-uninitialized
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-maybe-uninitialized - Success
-- Performing Test C_COMPILER_SUPPORTS__-Wno-format-overflow
-- Performing Test C_COMPILER_SUPPORTS__-Wno-format-overflow - Success
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-format-overflow
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-format-overflow - Success
-- Performing Test C_COMPILER_SUPPORTS__-Wno-unused-variable
-- Performing Test C_COMPILER_SUPPORTS__-Wno-unused-variable - Success
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-unused-variable
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-unused-variable - Success
-- Performing Test C_COMPILER_SUPPORTS__-Wno-unused-function
-- Performing Test C_COMPILER_SUPPORTS__-Wno-unused-function - Success
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-unused-function
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-unused-function - Success
-- Performing Test C_COMPILER_SUPPORTS__-Wno-write-strings
-- Performing Test C_COMPILER_SUPPORTS__-Wno-write-strings - Success
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-write-strings
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-write-strings - Success
-- Performing Test C_COMPILER_SUPPORTS__-Wno-sign-compare
-- Performing Test C_COMPILER_SUPPORTS__-Wno-sign-compare - Success
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-sign-compare
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-sign-compare - Success
-- Performing Test C_COMPILER_SUPPORTS__-Wno-deprecated
-- Performing Test C_COMPILER_SUPPORTS__-Wno-deprecated - Success
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-deprecated
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-deprecated - Success
-- Performing Test C_COMPILER_SUPPORTS__-Wno-c++11-narrowing
-- Performing Test C_COMPILER_SUPPORTS__-Wno-c++11-narrowing - Failed
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-c++11-narrowing
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-c++11-narrowing - Failed
-- Performing Test C_COMPILER_SUPPORTS__-Wno-register
-- Performing Test C_COMPILER_SUPPORTS__-Wno-register - Failed
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-register
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-register - Success
-- Performing Test C_COMPILER_SUPPORTS__-Wno-format
-- Performing Test C_COMPILER_SUPPORTS__-Wno-format - Success
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-format
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-format - Success
-- Performing Test C_COMPILER_SUPPORTS__-Wno-reserved-user-defined-literal
-- Performing Test C_COMPILER_SUPPORTS__-Wno-reserved-user-defined-literal - Failed
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-reserved-user-defined-literal
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-reserved-user-defined-literal - Failed
-- Performing Test C_COMPILER_SUPPORTS__-fpermissive
-- Performing Test C_COMPILER_SUPPORTS__-fpermissive - Failed
-- Performing Test CXX_COMPILER_SUPPORTS__-fpermissive
-- Performing Test CXX_COMPILER_SUPPORTS__-fpermissive - Success
-- Performing Test C_COMPILER_SUPPORTS__-x
-- Performing Test C_COMPILER_SUPPORTS__-x - Failed
-- Performing Test CXX_COMPILER_SUPPORTS__-x
-- Performing Test CXX_COMPILER_SUPPORTS__-x - Failed
-- Performing Test C_COMPILER_SUPPORTS__c++
-- Performing Test C_COMPILER_SUPPORTS__c++ - Failed
-- Performing Test CXX_COMPILER_SUPPORTS__c++
-- Performing Test CXX_COMPILER_SUPPORTS__c++ - Failed
-- Performing Test C_COMPILER_SUPPORTS__-std=c++17
-- Performing Test C_COMPILER_SUPPORTS__-std=c++17 - Failed
-- Performing Test CXX_COMPILER_SUPPORTS__-std=c++17
-- Performing Test CXX_COMPILER_SUPPORTS__-std=c++17 - Success
-- Performing Test C_COMPILER_SUPPORTS__-Wno-unused-but-set-variable
-- Performing Test C_COMPILER_SUPPORTS__-Wno-unused-but-set-variable - Success
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-unused-but-set-variable
-- Performing Test CXX_COMPILER_SUPPORTS__-Wno-unused-but-set-variable - Success
-- TCL library: /usr/lib/x86_64-linux-gnu/libtcl.so
-- TCL header: /usr/include/tcl/tcl.h
-- TCL readline library: /usr/lib/x86_64-linux-gnu/libtclreadline.so
-- TCL readline header: /usr/include/x86_64-linux-gnu
-- Found SWIG: /usr/local/bin/swig (found suitable version "4.1.0", minimum required is "4.0")
-- Using SWIG >= 4.1.0 -flatstaticmethod flag for python
-- Found Boost: /usr/local/lib/cmake/Boost-1.80.0/BoostConfig.cmake (found version "1.80.0")
-- boost: 1.80.0
-- Found GTest: /usr/local/lib/cmake/GTest/GTestConfig.cmake (found version "1.13.0")
-- GTest: 1.13.0
-- Found Python3: /usr/include/python3.10 (found version "3.10.12") found components: Development Development.Module Development.Embed
-- Found ZLIB: /usr/lib/x86_64-linux-gnu/libz.so (found version "1.2.11")
-- Found Threads: TRUE
-- spdlog: 1.8.1
-- Found BISON: /usr/bin/bison (found version "3.8.2")
-- Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE)
-- STA version: 2.6.0
-- STA git sha: aa598a2f14c5c142e90391a69988523505e7db3d
-- System name: Linux
-- Compiler: GNU 11.4.0
-- Build type: RELEASE
-- Build CXX_FLAGS: -O3 -DNDEBUG
-- Install prefix: /usr/local
-- Found FLEX: /usr/bin/flex (found version "2.6.4")
-- TCL library: /usr/lib/x86_64-linux-gnu/libtcl.so
-- TCL header: /usr/include/tcl/tcl.h
-- TCL readline library: /usr/lib/x86_64-linux-gnu/libtclreadline.so
-- TCL readline header: /usr/include/x86_64-linux-gnu/tclreadline.h
-- CUDD library: /usr/local/lib/libcudd.a
-- CUDD header: /usr/local/include/cudd.h
-- SSTA: 0
-- Found SWIG: /usr/local/bin/swig (found suitable version "4.1.0", minimum required is "3.0")
-- STA executable: /home/gudeh/masterCode/tools/OpenROAD/src/sta/app/sta
-- Found re2: /opt/or-tools/lib/cmake/re2/re2Config.cmake (found version "11.0.0")
-- Found Clp: /opt/or-tools/lib/cmake/Clp/ClpConfig.cmake (found version "1.17.7")
-- Found Cbc: /opt/or-tools/lib/cmake/Cbc/CbcConfig.cmake (found version "2.10.7")
-- Found SCIP: /opt/or-tools/lib/cmake/scip/scip-config.cmake (found version "9.0.0")
-- Found OpenMP_CXX: -fopenmp (found version "4.5")
-- Found OpenMP: TRUE (found version "4.5")
-- Found OR-Tools: /opt/or-tools/lib/cmake/ortools (version: 9.10.4067)
-- TCL library: /usr/lib/x86_64-linux-gnu/libtcl.so
-- TCL header: /usr/include/tcl/tcl.h
-- Found OpenMP_C: -fopenmp (found version "4.5")
-- Found OpenMP: TRUE (found version "4.5")
-- Found OpenMP: TRUE (found version "4.5")
-- GUI is enabled
-- Charts widget is enabled
-- Found Boost: /usr/local/lib/cmake/Boost-1.80.0/BoostConfig.cmake (found version "1.80.0") found components: serialization
-- Could NOT find VTune (missing: VTune_LIBRARIES VTune_INCLUDE_DIRS)
-- Found Boost: /usr/local/lib/cmake/Boost-1.80.0/BoostConfig.cmake (found suitable version "1.80.0", minimum required is "1.78")
-- TCL library: /usr/lib/x86_64-linux-gnu/libtcl.so
-- TCL header: /usr/include/tcl/tcl.h
-- Found Boost: /usr/local/lib/cmake/Boost-1.80.0/BoostConfig.cmake (found version "1.80.0") found components: serialization system thread
-- Found Boost: /usr/local/lib/cmake/Boost-1.80.0/BoostConfig.cmake (found version "1.80.0")
-- Found Eigen3: /usr/local/share/eigen3/cmake/Eigen3Config.cmake (found version "3.4.1")
-- TCL readline enabled
-- Tcl Extended disabled
-- Python3 enabled
-- Configuring done
-- Generating done
-- Build files have been written to: /tmp/tmp.1pDoPWXDOu

To Reproduce
Just run the gui with a loaded design. I tried on stages 3-3 and final
Relevant log output
No response
Screenshots
No response
Additional Context
No response

I talked about this with @AcKoucher and @LucasYuki

I ran into something similar and fixed it in https://github.com/The-OpenROAD-Project/OpenROAD/pull/6292.  Please update and see if it is resolved.

I updated my branch and the issue persists. I also noticed this message:
[WARNING GUI-0076] QXcbConnection: XCB error: 3 (BadWindow), sequence: 7758, resource id: 11500146, major code: 40 (TranslateCoords), minor code: 0

Indeed, the issue was resolved with latest version.

@AcKoucher FYI

@LucasYuki FYI


Cannot Use Ctrl+V Shortcut for Paste Function in New Brackets Window

Steps to Recreation:

Open Brackets.
Use Debug Menu > Select "New Brackets Window"
Inside text editor, Try to paste something in plain-text using Ctrl+V

What Happens:

Clipboard contents are not pasted into editor.
No error messages are displayed in console.

Did This Work in a Previous Version:

Unknown

Brackets Version:
Release 1.2 build 1.2.0-15697 (release 8f82e2a97)
OS:
Windows 8.1 Pro w/ Media Center (x64)
Occurs Without Extensions loaded:
Yes
Workarounds:

Use Shift+Insert
Use Edit Menu > Paste

UPDATE:
This seems to occur with several shortcuts (tested with F5, Shift+F5), not just Ctrl+V. Did not test with others.

This is a duplicate of #8135.  Virtually all shortcuts will be broken in the second window, which is one of several important reasons to avoid using this unofficial testing feature -- see notes in the original bug for details.


Add additional entry-points for deployWorkspaceProject

deployWorkspaceProject currently only exists as a workspace and command-palette command.

This PR adds additional entry-points to the following tree items:

ContainerAppItem

Updated:

ManagedEnvironmentItem

It also checks to ensure no conflicts exist between existing workspace settings vs. the tree item selected (else it throws an error).
I also separated out some of the code that originally existed in getDefaultContainerAppResources into separate files.

New pop-up confirmation:

New pop-up confirmation:

I think it'd be good to have a button to override old settings.

New pop-up confirmation:

I think it'd be good to have a button to override old settings.

Already got it covered with ShouldSaveDeploySettingsPromptStep :)


Chess: Move D2 to D3

Please do not change the title. Just click "Submit new issue". You don't need to do anything else :D

@BengalPirate done! Successfully played move d2d3 for current game.
Thanks for playing!


Out of flow elements

Attach (recommended) or Link to PDF file here:
https://www.listcorp.com/asx/mnf/mnf-group-limited/news/2017-ceos-agm-presentation-1732903.pdf
Configuration:

Web browser and its version: any
Operating system and its version: any
PDF.js version: any
Is a browser extension: no

Steps to reproduce the problem:

open pdf
drag text selection from first page across to second page
footer page number is not selected or is selected out of flow

What is the expected behavior? (add screenshot)
I understand this has much to do with the pdf standard. Just wondering if there was a reason why we could just simply do an insertion sort on the div nodes when rendering the text layer so that they are ordered by their top then left position? If there was prior discussion about this I apologise - I only found the discussion pertaining to improving text selection but nothing seems to have been resolved there beyond just expanding the div dimensions.
I also note that Chrome's in built viewer also presents this symptom, so it may simply be a matter of consistency regarding the pdf standard, in which case I do understand.
At this point, I'm planning to do a hack involving the reordering of text nodes after rendering, to get more consistent text selection results.
Kind Regards,
Daryl

Just wondering if there was a reason why we could just simply do an insertion sort on the div nodes when rendering the text layer so that they are ordered by their top then left position?

Please keep in mind that PDF files can contain text in languages using e.g. right-to-left or top-to-bottom reading order. Hence doing what you're suggesting would most likely (significantly) regress text-selection in anything but left-to-right text, and it might not even work too well there in the general case.

I also note that Chrome's in built viewer also presents this symptom, so it may simply be a matter of consistency regarding the pdf standard, in which case I do understand.

I even get the same behaviour in Adobe Reader, and as you suspect this is caused by the PDF file itself since it specifies the text in that particular order.
Closing as answered, since this isn't something that we can (generally) fix.

Thanks for taking the time to reply!


unable to start binary on Rocky Linux 8 (GLIBC_2.29 missing)

Introduction
Starting the binary il bails that it cannot find GLIBC_2.29 nor in libm.so.6 or libc.so.6
To Reproduce
Start a binary on a v. 8 Red Hat compatible
Actual behavior
Error
$ /opt/sqlpage/sqlpage.bin: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /opt/sqlpage/sqlpage.bin)
   /opt/sqlpage/sqlpage.bin: /lib64/libc.so.6: version `GLIBC_2.29' not found (required by /opt/sqlpage/sqlpage.bin)

Expected behavior
Rely on the current libc version or musl (for AlpineLinux)
Version information

OS: RockyLinux 8

Hello and welcome to SQLPage !
Glibc 2.29 was released almost 6 years ago, I think it is reasonable dependency to have.
If using a more recent os is not an option, I can recommend our docker image: https://hub.docker.com/r/lovasoa/sqlpage
If you need help to get started, do not hesitate to ask here ! What do you want to build with SQLPage ?

Here is a musl-based sqlpage binary I compiled locally, in case it's useful.
sqlpage.0.31.musl.bin.gz

Thank you very much! I will try it on a newer RH compatible distribution, thanks for the musl-based binary.


Bump actions/github to 2.2.0

This adds support for running against GHES by using v2.2.0 of @actions/github. The details of connecting to a GHES instance or github.com are handled internally in the client, so no code changes in this action are necessary.
Tested by pushing this version of the action to an "actions" org on the GHES instance.  I also needed to set NODE_TLS_REJECT_UNAUTHORIZED = 0 temporarily in the action to get around my self-signed (or otherwise not trusted) server cert.

After this, we'll need to move the release tag forward to pick up this change for existing workflows.

@pjquirk I say go for it!


The biggest fix is to apply a bug fix from the cache directory resulting in "nil/nil" responses. These were fixed in https://github.com/bluesky-social/indigo/pull/479, but not copied to the redis directory implementation, which has the same coalescing code. This recently impacted @whyrusleeping's use in discover. This is a backwards-compatible fix.
Another fix handles cached error messages. An empty string was being stored for the DID. Because redis cache serializes, and the de-serialized DID is re-parsed, the empty strings fail to parse, resulting in an error. I guess we could consider having text parsing of DIDs not actually parse the string? but that would break auto-validation when it is expected. The fix was to make that field nullable. this might make the change not-backwards-compatible with existing cached metadata? this only impacts cached errors, which have a shorter TTL, so might not be that big of a deal in practice?
Other smaller cleanups and fixes, which rolled in here to make the code align better with the in-memory caching directory, so that merge/review is easier:

adds invalid handle TTL to redisdir
adds "WithCacheState" variants of methods, for metrics/perf measurement
fix deletion/purging
special-case handling of resolving invalid handle

One remaining issue is that the cached error types come back as generic errors (with error kind/type striped). It would be nice if that wasn't the case, so that code could detect specific types of errors? Considering doing a manual enum/integer hack to encode the type and convert the errors to the actual type on read, for a small set of known identity errors.

Resolved the review things. My disposition is to merge this, but I want to monitor when this gets deployed (in various places), so i'll probably wait until i'm ready to do a controlled deploy and merge it then.


Remove the default tabindex -1

With accessibility in mind you should never change te natural tab order of element son the page. Especially putting items on tabindex -1 ensures that keyboard users won't be able to use these fields properly.
Since there should never be any reason to change the tabindex please remove this from the inputs.

Thanks for your report, I will handle it as soon as possible.

@Jebble Hi, please try v2.2.0 to see if it's fixed.

I'm not actually using this in any project right now. Came across it while searching for a react validator and noticed the tabindex. Thanks for changing it and making the web a bit more accessible!


Fix processing error for s3 stream directory method

Codecov Report
Attention: Patch coverage is 0% with 3 lines in your changes missing coverage. Please review.

Project coverage is 80.32%. Comparing base (0deeec9) to head (70bf55b).

Files with missing lines
Patch %
Lines

io/aws/s3/reader.go
0.00%
3 Missing :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #174   +/-   ##
=======================================
  Coverage   80.32%   80.32%
=======================================
  Files          96       96
  Lines        7238     7239    +1
=======================================
+ Hits         5814     5815    +1
  Misses       1064     1064
  Partials      360      360

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


feat: prefer the local @mdx-js/mdx

..and cache any resolved imports.
⚠  Merge #22 first!

Merged into #22 since both depend on each other


Deploying Release with GH actions fails

@pckroon It seems that triggering the workflows works fine. But the deploy fails, because python -m build does not get the proper version number form the package. The current setup works fine on a local machine but when using it to build a release it fails. I really don't know what is going on here. So I give up for the day.

Interesting... Do you have a log of the build I could stare at? My guess would be that pbr is not being installed.

Interesting... Do you have a log of the build I could stare at? My guess would be that pbr is not being installed.

pbr is installed but PBR fails to get the correct version. This one should do: https://github.com/marrink-lab/polyply_1.0/runs/1763736693?check_suite_focus=true

pbr is installed but PBR fails to get the correct version. This one should do: https://github.com/marrink-lab/polyply_1.0/runs/1763736693?check_suite_focus=true

PBR is not installed: /opt/hostedtoolcache/Python/3.7.9/x64/lib/python3.7/distutils/dist.py:274: UserWarning: Unknown distribution option: 'pbr'.
It should be installed before running python -m build.

PBR is not installed: /opt/hostedtoolcache/Python/3.7.9/x64/lib/python3.7/distutils/dist.py:274: UserWarning: Unknown distribution option: 'pbr'.
It should be installed before running python -m build.

huh, I thought it would be as it is in the requirements but fair enough. That would be an easy fix then

huh, I thought it would be as it is in the requirements but fair enough. That would be an easy fix then

Sure, but nowhere do you install polyply when deploying.

Sure, but nowhere do you install polyply when deploying.

@pckroon It still doesn't want to deploy correctly. Somehow it sets the version to the package name. Do you perhaps find another issue. I stared on this for too long, and tried too many things to see clear.

@pckroon It still doesn't want to deploy correctly. Somehow it sets the version to the package name. Do you perhaps find another issue. I stared on this for too long, and tried too many things to see clear.

Nothing obvious, unfortunately. I'm deep into PEP517 atm. It could be that python -m build doesn't actually call setup.py anymore (?).
Maybe try running python setup.py sdist bdist_wheel instead of build? https://pypa-build.readthedocs.io/en/latest/differences.html
I'll read on a bit further to see what else I can come up with

Nothing obvious, unfortunately. I'm deep into PEP517 atm. It could be that python -m build doesn't actually call setup.py anymore (?).
Maybe try running python setup.py sdist bdist_wheel instead of build? https://pypa-build.readthedocs.io/en/latest/differences.html
I'll read on a bit further to see what else I can come up with

adding pbr to project file solves it

adding pbr to project file solves it


Project Template - Error shown while view page

Service delete ho chuki hai but, project template delete nhi hua so error aa rahi hai sayad

Service was removed,
Fixed- When ever service is removed template will be removed
Previous Template Error cannot be solved,


Fix C++ package on Windows and add test for relocatability

Fix https://github.com/conda-forge/icub-models-feedstock/issues/18 .

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

As expected, the test on the existing repo is working on Linux/macOS and failing on Windows. Now we backport the fix from https://github.com/robotology/icub-models/pull/179 to make it work on Windows as well.

The backport of https://github.com/robotology/icub-models/pull/179 fixed the test.


CurlTransportOptions CAInfo does not appear to work

Describe the bug
Setting the CAInfo in TransportOptions does not appear to work. The CA file name is not passed to libcurl and the connection to microsoft fails raising this error:
Fail to get a new connection for: https://login.microsoftonline.com. SSL peer certificate or SSH remote key was not OK. Underlying error: unable to get local issuer certificate
To Reproduce
-build libcurl with no default CA path. Use options --without-ca-path and --without-ca-bundle
-Set the CAInfo in the option like this. The connection will fail. (Is this the correct way to set the client options? If not please advise! I am not an expert C++ programmer.)
    KeyClientOptions clientOptions;
    Azure::Core::Http::CurlTransportOptions curlOptions;
    // set correct CA path for this machine here
    curlOptions.CAInfo = "/etc/pki/tls/certs/ca-bundle.crt";
    clientOptions.Transport.Transport
        = std::make_shared<Azure::Core::Http::CurlTransport>(curlOptions);
    KeyClient keyClient(keyVaultUrl, credential, clientOptions);
    auto keyWithType = keyClient.GetKey(keyName).Value; <== exception raised here

Code Snippet
See above
Expected behavior
CA info should be passed to libcurl but it is not .
With a debugger (gdb), I can see that in this code the option has not been set:
./sdk/core/azure-core/src/http/curl/curl.cpp
  if (!options.CAInfo.empty())
  {
    if (!SetLibcurlOption(m_handle, CURLOPT_CAINFO, options.CAInfo.c_str(), &result))
    {
      throw Azure::Core::Http::TransportException(
          _detail::DefaultFailedToGetNewConnectionTemplate + hostDisplayName
          + ". Failed to set CA cert file to:" + options.CAInfo + ". "
          + std::string(curl_easy_strerror(result)));
    }
  }

gdb>p options.CAInfo.empty()
true
gdb>

Setup (please complete the following information):

OS: Linux (Centos)
IDE :
Version of the Library used: 1.4.0 (Core)

Additional context
Add any other context about the problem here.
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[ ] Bug Description Added
[ ] Repro Steps Added
[ ] Setup information Added

Bump.
Can anyone help me or comment on this problem? I'm really stuck here. I need a way to set CAInfo in CurlOptions so that it gets used by curl.

Hi @nrgiii, I am sorry for the delay.
I think I have found what needs to be done.
When you set a breakpoint and get CAInfo being an empty string, it is not of the callstack you think it is.
See, KeyClient is a client with its own HTTP pipeline, but a credential is also technically a client with its separate HTTP pipeline, even though we don't normally think of credentials as clients.
So, you'd need to write
    KeyClientOptions clientOptions;

    Azure::Core::Http::CurlTransportOptions curlOptions;
    curlOptions.CAInfo = "/etc/pki/tls/certs/ca-bundle.crt";
    clientOptions.Transport.Transport = std::make_shared<Azure::Core::Http::CurlTransport>(curlOptions);

    // Also set the same options for the credential's pipeline
    Azure::Core::Credentials::TokenCredentialOptions credentialOptions;
    credentialOptions.Transport.Transport = std::make_shared<Azure::Core::Http::CurlTransport>(curlOptions);
    auto credential = std::make_shared<...>(credentialOptions);

    KeyClient keyClient(keyVaultUrl, credential, clientOptions);
    auto keyWithType = keyClient.GetKey(keyName).Value;

You can share the same transport implementation instance between two pipelines
    ...
    auto curlTransport = std::make_shared<Azure::Core::Http::CurlTransport>(curlOptions);
    clientOptions.Transport.Transport = curlTransport;
    ...
    credentialOptions.Transport.Transport = curlTransport;
    ...

Please let me know if it helped.
BTW, based on this doc, you may need to convert .crt certificate into a .pem.


Weird behaviour when container becomes empty

I'm facing weird behaviour for droppable container. When I drop all the items from one container to another, means I emptied first container. After this I'm unable to add back items from second container to first one, the empty one. I'm unable to do so.
Am I missing something? Or it is default behaviour?

No, that's an issue. I need to fix it.

Hi,
I am also facing the same issue. is it fixed in the latest update?

@akserg Hi , is there any fix for this issue?

Hi
That issue was fixed quite a while ago. Please use the latest release.


Streamline Thread Installation by Eliminating Model Rebuild

Describe the bug
Feedback indicates that the process of rebuilding machine learning models during the installation of Thread significantly extends the setup time. This step, inherited from our fork of TRAM, is not necessary as the models are covered under an open source license and contain no proprietary content. Removing this step from the installation process will drastically reduce the time required to get Thread operational on new installations.
To Reproduce
Steps to reproduce the behaviour:

Install Thread by following the instructions here https://github.com/arachne-threat-intel/thread/blob/main/README.md
You will see that as part of the installation, the ML models are rebuilt and this takes a significant amount of time.

Expected behavior
The installation being faster, facilitated by the ML models not being rebuilt each installation.
Thread details (please complete the following information):

config.yml changes
Tagged-version used or output of git rev-parse --short HEAD

Desktop (please complete the following information):

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

Additional context
Acceptance criteria

Modify the installation script for Thread to bypass the machine learning model rebuilding process.
Ensure that pre-built, open source licensed models are included in the installation package and are correctly loaded during setup.
Test the modified installation process to ensure that it works seamlessly and the models are correctly integrated without the rebuild step.
Update the installation documentation to reflect the change in process, specifying the removal of the model rebuilding step and the inclusion of pre-built models.
Conduct a time comparison test to document the time saved by removing this step.

Milestones

Script Modification: Complete modification of the installation scripts to remove the model rebuilding process.
Integration Testing: Test the installation process in various environments to ensure stability and functionality.
Documentation Update: Update the installation documentation post-testing to reflect the changes made.
Deployment and Feedback Collection: Roll out the updated installation process and collect user feedback to gauge impact and detect any unforeseen issues.

Hi @KadeMorton
The linked PR had an updated models file. Submitting a report in my dev environment using that file did not trigger a rebuild.
We don't have any docs that need to be updated; we didn't state model-rebuilds were an installation step. These rebuilds happen because:

Thread uses a dependency for the types of models
This dependency was version x when Tram committed the models file
When you set up a new environment, the dependency is most likely a major-version upgrade from x
The models need to be rebuilt because of this version difference

Given your point about a docs-update, we could add in the installation steps a warning that this rebuild may happen. In the future, we should try to commit ready-to-use models given any dependency-version updates.
As the PR is merged, this linked issue closed automatically but did you want it reopened given this, your acceptance criteria and milestone points may be outstanding (e.g. time comparison tests, user-feedback)?

If it's just time comparison tests and user-feedback I think we can leave this closed. Just ensure that there is an update to the docs  warning that the installation steps may trigger a rebuild, but that it's not intended to rebuild every installation.


Attempting to Resuscitate the Application for VR

I am not a C++ developer but really want this application to work with SteamVR (OpenVR). Working on educated guesses and Google Search results I loaded the Jun 4, 2018 projects into Visual Studio Community 2019 on Windows 10 and did the following:

Went into properties for each project and set the Windows SDK version the the latest installed version (Configuration Properties > General > Windows SDK Version)
Went into properties for each project and set the Language Standard to C++17 (Configuration Properties > C/C++ > Language)
Updated Protocol Buffers, https://github.com/protocolbuffers/protobuf

(Replace \dependencies\x64\protoc.exe with protoc.exe from protoc-x.x.x-win64.zip (and also the Win32 version)
Replaced \dependencies\include\Google with \src\Google from protobuf-csharp-x.x.x.zip

Replaced all instances of "std::tr2::sys" with "std::filesystem" across all files- std::tr2::sys is deprecated and will be removed from C++20

The above steps got me to the following build errors:
1>\trance-master\src\common\session.cpp(256): error C2672: 'std::filesystem::path::append': no matching overloaded function found
1>\trance-master\src\common\session.cpp(256): error C2783: 'std::filesystem::path &std::filesystem::path::append(const _Src &)': could not deduce template argument for '__formal'
1>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.20.27508\include\filesystem(790): note: see declaration of 'std::filesystem::path::append'
This is where Google Search has its limitations. I have not yet updated the OpenVR components, https://github.com/ValveSoftware/openvr. Given the above build errors it would be a bit premature to do so.
Is anyone able to assist with getting the app back on its feet for VR?

I got this working on my fork here https://github.com/AA10D6/trance/commits/master
I updated SFML and OpenVR to latest, and fixed the init and render code for openvr.cpp.
For building, you should just use VS2015 since that's what the project originally targets. You won't get all those build errors you were having if you use it (I had the same problems trying to use 2017 at first which I already had installed). See here for how to get VS2015 since Microsoft doesn't let you download it without jumping through some hoops.

Thanks @AA10D6! I had hoped to get the project updated for 2019 since I know Microsoft is being fairly strict of ending support for older products, but it seems to be too big of a lift.


fix: [Policy Assistant] warn that SameLabels and NotSameLabels are deprecated

Partially addresses #212 until there's a network-policy-api release that includes changes from #196.

Hey @danwinship could you approve the GH action change and add a lgtm? Thanks!

@danwinship do you mind adding a lgtm for this simple change?

/lgtm
(note: you can get any contributor to lgtm this, because you're an approver for policy-assistant)


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/27802

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/27802

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/69489

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/69604


Fixing docker image reference.

Fixes this error caused by using resource path instead of actual docker image.
State
TASK_FAILED
Message
Failed to launch container: Failed to 'docker -H unix:///var/run/docker.sock pull resource.assets.container.docker.hue-docker:latest': exit status = exited with status 1 stderr = Error: image library/resource.assets.container.docker.hue-docker:latest not found

Can I please ask you to re-submit this PR in ca. one week time once we've the new version of the Universe in place? If you've got any questions, happy to discuss it via http://chat.dcos.io

@mhausenblas The fix it pretty trivial. Please consider applying it in the way that works best for you.

OK, thanks @egorpushkin — background is that we're not on version-3.x and GitHub doesn't allow PRs being carried over, so …


Couldn't Log in

Hi
Thx for the effort to make this integration!
I'm new into home assistant and I have troubles to make it work.
I tried different things but I still get errors.
Is it possible to give an example of the credentials of the integration?

Thx in advance!

Which Sagemcom F@st router do you have? And how do you log in to the control panel?
In my example, I login to <IP_ADDRESS> and use a username and password provided by my ISP.

Thx for your quick response!
It’s a sagemcom of Proximus but I don’t find the exact number…When I use the host of my modem, the username en password witch I use to login by the website, I get an unexpected error.

Have you checked your log for any errors? An unexpected error should be visible in the log.
Please note that this integration only supports Sagemcom F@st routers.

Is there a way to see witch type sagemcom it is?
I got this in the log:
[cid:C202D256-5114-4519-9150-CC2BED13A2FA-L0-001]
Op 29 mei 2021 om 01:16 heeft Mick Vleeshouwer @.***> het volgende geschreven:

Have you checked your log for any errors? An unexpected error should be visible in the log.
Please note that this integration only supports Sagemcom @.*** routers.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/iMicknl/ha-sagemcom-fast/issues/23#issuecomment-850716447, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AS7LVYOXYP6NKONKTY4YGOLTQAP5DANCNFSM45XGX3KA.

Is there a way to see witch type sagemcom it is?
I got this in the log:

@Allbruce unfortunately, it seems that your device is not supported by this integration.


Clicking on the overlay should be consumed if the brush was cleared.

If the brush is empty and you click the overlay, the click should not be consumed; but if the brush is not empty, then clicking the overlay clears the selection and should consume the click.

Fixed in #53.


Fixed part dump with timeout opt; Fixed sg delete with email opts

See commit message.
No review needed.

Coverage decreased (-0.007%) to 32.955% when pulling 47a7908039811de020d401f473d9a66493316c52 on andy/fix-operation-timeout into 8ca6cdc6d7aba76592e73511f684f6cf89dea735 on master.


Stop swallowing groupby widgets when passing widgets

This is kind of a follow on to the widget work in #331 and #323 this lets the groupby widget that hvplot creates get through even when other widgets options are used.
import xarray as xr
import hvplot.xarray

import geoviews.tile_sources as gvts
import panel as pn

base_map = pn.widgets.Select(options=list(gvts.tile_sources.keys()), value='EsriImagery')
data = xr.tutorial.load_dataset('air_temperature').air

pn.Column(
    base_map,
    data.hvplot.contour(geo=True, tiles=base_map, widget_type='scrubber',
                        widget_location='top', widget_layout=pn.Row,
                        levels=10, cmap='reds', line_width=2))

Looks great!


Set zone for ES nodes for allocation awareness

@dannyroberts @millerdev @nickpell
Setting up forced allocation awareness for the ES migration:
https://www.elastic.co/guide/en/elasticsearch/reference/current/allocation-awareness.html
(with https://github.com/dimagi/commcare-hq/pull/12041, although they don't need to be merged together)

👍

neat


OnPartitionsAssigned fallback doesn't work

If the application doesn't provide an OnPartitionsAssigned delegate then the Consumer should call Assign() itself, and there's code that attempts to do this in the Rebalance handler.
But since the consumer.OnPartitionsAssigned is always set to a lambda that checks if the application's OnPartitionsAssigned is set it or not, the code that checks for the fallback doesn't actually kick-in so we end up with Assign() not being called automatically.
The best option would be if the Consumer wouldn't register a rebalance_cb at all if the application developer doesn't want On..Assign/On..Revoke but it seems this isn't really possible since those delegates are registered after rd_kafka_t creation.

this was resolved by PR #32


How do you listen for changes to a formik field?

❓Question
I have a UI that I want to respond to the selected values of a formik form.  It's a pricing UI where selecting different options results in a different total price.  I need to be able to connect a listener for when a formik field has setFieldValue() called on it.  I don't see such a function in formik so the way I've gotten around it is to duplicate the form schema as values in the state and every time I call setFieldValue() I also mutate the corresponding state value in the same way.

Can you just move this logic to your render function and determine price/what fields to show based on values?

I need the logic in the render function but I also need it in the handleSubmit() of the formik object so I wrapped the formik object in another component.  My code looks like this
const MyForm = props => {
  const {
    values,
    touched,
    errors,
    handleChange,
    handleBlur,
    handleSubmit,
    getPrice,
  } = props;
  return (
    {getPrice()}
    <form onSubmit={handleSubmit}>
      <input
        type="text"
        onChange={handleChange}
        onBlur={handleBlur}
        value={values.name}
        name="name"
      />
      {errors.name && touched.name &&
{errors.name}
}
      <button type="submit">Submit</button>
    </form>
  );
};

const MyEnhancedForm = withFormik({
  mapPropsToValues: () => ({ name: '' }),
  handleSubmit: (values, { props, setSubmitting }) => {
    sessionStorage.setItem('price', props.getPrice());
    setSubmitting(false);
  },
})(MyForm);

class MyEnhancedFormContainer extends React.Component {
  constructor(props) {
    super(props);

    this.state = {
      mirroredName: null,
    };
  }

  getPrice = () => {
    // does something with this.state.mirroredName
  }

  render() {
    <MyEnhancedForm
      getPrice={this.getPrice}
    />
  }
}

I recently needed to subscribe on some value. My input was editable with handleChange and also manually with setFieldValue. So to avoid multiple listeners, I just used hook like this:
    useEffect(() => {
        if (!isSanitized(values.field)) {
            setFieldValue('radius', sanitize(values.field));
        } else {
            action(values.field);
        }
    }, [values.field]);

Cheers

@lkostrowski In your example, what is action(values.field); doing? I think this may work for my issue... Using recaptcha, if the user waits too long, the value expires. I need to listen for the expiration and simply set the values.recaptcha to blank if it's not a valid token.

It does whatever you like. In my case it's only listening to formik state instead listening to many sources, so I sanitize value if is not. Then, value changes, so hook runs again, but else is running with my action. Don't remember what it was in this example, probably some redux dispatch

Thank you... I was curious if it was dispatching another Formik action. I ended up using your example to handle the recaptcha timeout and it works great.
// if recaptcha times out, an ugly error message is returned
// set the value from null to '' to get the validationSchema message
useEffect(() => {
    if (form.values.recaptcha === null) {
        form.setFieldValue('recaptcha', '')
    }
}, [form.values.recaptcha])

And what if you're working with class components? My initial thought is componentDidUpdate, but the formik values are neither in state, nor props. isSubmitting is close, but not quite what I need.

I came up with this approach:

const HandleFieldChange = connect(
  ({
    name,
    formik: {
      values: { [name]: value },
    },
    onChange,
  }) => {
    useEffect(() => {
      onChange(value);
    }, [onChange, value]);
    return null;
  }
);

That you would use inside a form like this:
<HandleFieldChange
    name="field-name"
    onChange={value => console.log(value)}
/>


fix when-syntax in roles/ceph-common/tasks/installs/install_on_suse.yml

Fixes: #4362
There are two valid combinations of ceph_origin and ceph_repository on
SUSE/openSUSE:

ceph_origin == 'distro'
ceph_origin == 'repository' and ceph_repository == 'obs'

The current when condition would fail even in the valid second combination,
as ceph_origin != distro would be true then
Signed-off-by: Johannes Kastl<EMAIL_ADDRESS>

two observations:
* I'm wondering why we don't move this check in `ceph-validate`

I just fixed what was there, but you are right, this belongs to ceph-validate. I'll move it there.

* I would change the commit title to something shorter :
  `validate: refact method installation check on suse`

Sure, can do that.

@guits Please review again, I moved this to ceph-validate and reworked the checks.
I'll check that this works in the wild...

unrelated failure


tinymediamanager v4

From version 4, tinyMediaManager has changed its licensing model from donationware to subscription based. tinyMediaManager blog:

Since the lion’s share of the work (development, maintenance, deployment, …) remains within the tinyMediaManager team, we decided to charge an annual fee for the ongoing work on the project (starting with v4).

That's their choice and I have no problem with it, but I think the manifest for tinymediamanager should be limited to version 3 as it's essentially a different branch now.

tinyMediaManager v3 will remain available and free, but only serious bugs will be fixed and no new features will be added. A mandatory upgrade to v4 will not be necessary, but we want to provide an easy transition for users which want to upgrade.

I'm not actually sure if version 4 could be added in another manifest. There's no criteria listed for the extras bucket, but I would assume the trial versions exclusion from the main bucket still applies.

the compiled/packaged version of tinyMediaManager has a limitation concerning the number of loaded objects/API calls of the scraper (currently 50 movies, 10 TV series and about 50 API calls) - unlockable with a license

I just put an issue #4875. Not sure if this should be merged.


Code example in the Managed Threading Best Practices topic does not match text

Page: https://docs.microsoft.com/en-us/dotnet/standard/threading/managed-threading-best-practices
Chapter: Deadlocks
Text:

For example, the following code attempts to acquire a lock on the current instance.

C# Code:
if (Monitor.TryEnter(lockObject, 300)) {       try {           // Place code protected by the Monitor here.       }       finally {           Monitor.Exit(this);       }   }   else {       // Code to execute if the attempt times out.   }
VB Code:
If Monitor.TryEnter(lockObject, 300) Then   Try           ' Place code protected by the Monitor here.       Finally           Monitor.Exit(Me)       End Try   Else       ' Code to execute if the attempt times out.   End If
As you can see from above, the code attempts to acquire a lock on lockObject and NOT on the current instance. Either the code snippets have to be changed or text.

Thanks for pointing this out, @alex-groshev. We'll address it sometime next week.


kore-rpc ending normally says user-interupted

Because we're sending SIGINT instead of SIGTERM to the kore-rpc, we're getting a weird message even on normal exit:

Could we instead, either:

Go back to SIGTERM, or
Add an explicit shutdown message to the RPC server that we call?

Related: https://github.com/runtimeverification/pyk/pull/298
Related: https://github.com/runtimeverification/haskell-backend/issues/3557

The proper fix is to undo https://github.com/runtimeverification/pyk/pull/298 , but for that the server needs to handle the SIGTERM signal gracefully.

This is a known issue in the Haskell runtime system which seems unadressed to this day. There appear to be a couple of workarounds like this one: https://github.com/input-output-hk/cardano-node/pull/3641
However, can't tell whether this would actually prevent the error above from being thrown.

The proper fix is to undo #298 , but for that the server needs to handle the SIGTERM signal gracefully.

I think we should keep SIGINT, as only this will clean up all resources in the correct way. Translating SIGTERM to SIGINT internally as in the PR which @goodlyrottenapple found may be an option if for some reason we should not keep SIGINT, but I would not see why.

we're getting a weird message even on normal exit:

If the concern is just the appearance of an error in the logs, we can probably catch UserInterrupt and print something more comforting instead.

we can probably catch UserInterrupt and print something more comforting instead

If there's no simple way to process both SIGINT and SIGTERM on the backend, I'm find with this workaround.

I believe this is addressed at this point? I haven't seen the error message in logs for a while, and I am indeed comforted by that.


Request for docs: Possible to have different read and write types?

Is it possible to have different types for reading & writing? If yes, how does that impact UPDATE statements?
Use-case for different read and write types:

A model has an auto-increment primary key, a created_at and an updated_at, where all three should be coming from the DB, and the Haskell layer should not even be allowed to specify these three columns (for greater type-safety). However, they are required to be read back from PG to Haskell world.

How this can be problem for update transactions

Main idea about this lib is to have same types but different type indexes for most of db operations.
For your scenario, you can configure column key, created_at and updated_at to have default value in the Table instance and the impact of that will be, those columns will become optional during writes (insert & updates). It is possible to void out those column during writes, which totally prevent user from setting the values for those columns, but also would mean that user will not be able to override the auto-gen value. Hence I have chosen to make it optional, rather than voiding it out.
Following code (not type checked btw) provides example for your scenario and I hope this helps
newtype TenantId = TenantId Int
newtype OwnerId = OwnerId
-- Assuming status is a enum in your case
data Status = S1 | S2 ...
data Tenant f = Tenant {
    key                :: Col f "key" TenantId
  , created_at         :: Col f "created_at" UTCTime
  , updated_at         :: Col f "updated_at" UTCTime
  , name               :: Col f "name" Text
  , status             :: Col f "status" Status
  , owner_id           :: Col f "owner_id" OwnerId
  , back_office_domain :: Col f "back_office_domain" Text
}

data Owner f = Owner {
    key :: Col f "key" OwnerId
  , created_at         :: Col f "created_at" UTCTime
  , updated_at         :: Col f "updated_at" UTCTime
}

data MyAppDB

instance Database MyAppDB where
  type Tables MyAppDB = '[Tenant Hask, Owner Hask]
  type Types MyAppDB = '[Status]

instance Table (Tenant Hask) where
  type HasDefault (Tenant Hask) = '["key", "created_at", "updated_at"]

instance Table (Owner Hask) where
  type HasDefault (Owner Hask) = '["key", "created_at", "updated_at"]

insertTenant :: ReaderT (Config a) PG ()
insertTenant = insert (Tab @MyAppDB @Tenant) (
  Tenant
  { key = Nothing -- Key has become (Maybe TenantId) since it is configured to have default value in Table instance
  , created_at = Nothing -- Optional during write due to same reason as above
  , update_at = Nothing  -- Optional during write
  , name = "foo"
  , status = S1
  , owner_id = (OwnerId 1)
  , back_office_domain = "dsdsd"
  })

-- HasDefault setting has effect on update too, as update is about converting a value from tab Op -> Write Op db tab

updateTenant = update (Tab @MyAppDB @Tenant) (
  \ten ->
  (constant ten :: Write Op MyAppDB Tenant) {
    name = "bar"
    }) (\ten -> key ten .== (constant $ TenantId 10))

-- constant can be used to due the required type conversion before performing the record update

Main idea about this lib is to have same types but different type indexes for most of db operations.

Can you elaborate what you mean by "same types but different type indexes"? Do you basically mean "same shape" by polymorphic in f over Col f colname hasktype?
In the following code, isn't is ambiguous to use Nothing to indicate a default value? What happens if I actually want to send a NULL down to SQL for a particular column?
insertTenant :: ReaderT (Config a) PG ()
insertTenant = insert (Tab @MyAppDB @Tenant) (
  Tenant
  { key = Nothing -- Key has become (Maybe TenantId) since it is configured to have default value in Table instance
  , created_at = Nothing -- Optional during write due to same reason as above
  , update_at = Nothing  -- Optional during write
  , name = "foo"
  , status = S1
  , owner_id = (OwnerId 1)
  , back_office_domain = "dsdsd"
  })

Also, is there an easier way to do updates? Doesn't the following piece of code have a lot of boilerplate? If I understand this correctly, you're basically taking a "default" tenant record constructed specially for writing to the DB (is it constant ten :: Write Op MyAppDB Tenant?) and changing a field within it? Also, what happens if the changed field is a custom type, like an Enum? Does it get converted to the PG value automatically or does one have to use ToField or constant on it?
updateTenant = update (Tab @MyAppDB @Tenant) (
  \ten ->
  (constant ten :: Write Op MyAppDB Tenant) {
    name = "bar"
    }) (\ten -> key ten .== (constant $ TenantId 10))

Yes. By changing f, I'm able to alter the field's type to the required one.
Specific eg would be.
 You can pass in NULL only if you configure your column to be optional,
Say for eg. you have following column with Defaults,
foo :: Col f "foo" (Maybe Int)
Even in this case, during Write column foo's type become Maybe (Maybe Int), allowing you to choose DEFAULT value by passing Nothing, or null by passing Just Nothing, or a actual value Just (Just 1)
As of now, this lib support Enums and NewTypes providing automatic marshaling for those (no need for ToField, FromField ..)
For Enum, you are expected to create corresponding enum type in the Postgres.
Eg.  data UserRole = Admin | Guest | Nor'mal
requires
            CREATE TYPE "USERROLE" AS ENUM ('Admin', 'Guest', 'Nor''mal');
For NewType, no extra work is required. Lib will simply throw the newtype wrapper and use the internal type automatically.
As for as update is concerned, the first callback accepts db row (ten :: Tenant Op) that matched the filter predicate and should return Writable row of same type (here Write Op MyAppDB Tenant).
Even more verbose way of doing this is manually copying those info from arg, like,
\ten -> Tenant { key = Just $ key ten
, created_at = Just $ created_at ten
, update_at = Just $ updated_at ten
, name = "bar"
, status = status ten
, owner_id = owner_id ten
, back_office_domain = back_office_domain ten
}
Luckily with constant we are able to avoid these manual copy by first converting it to Write Op MyAppDB Tenant and then use normal record update syntax
I think loosing type inference due to constant is one of the reason for verbosity.
To fix, we can define one function called
toWriteable :: tab Op -> Write Op db tab
toWriteable = constant

with this update would look like
updateTenant = update (Tab @MyAppDB @Tenant) (
  \ten -> toWriteable ten {status = constant S2} -- Enum value can be lifted to DB Value using constant
) (\ten -> key ten .== (constant $ TenantId 10))

I didn't get how it will become ambiguous. You can pass in NULL only if you configure your column to be optional,

So, in the context of an INSERT statement aren't we dealing with three states:

Explicit NULL value
Explicit non-NULL value
Absent from the INSERT statement, which allows DB to use default value, if present

Is it possible to model this with a Maybe, which represents only two states correctly Similarly, in the context of an UPDATE, are't we again dealing with the same three states?
Am I missing something subtle here?

As for as update is concerned, the first callback accepts db row (ten :: Tenant Op) that matched the filter predicate and should return Writable row of same type (here Write Op MyAppDB Tenant).

Okay, so I guessed correctly. The callback needs to return an Op type, and not a Hask type. Is the row passed to the callback a Hask or an Op? Is the constant trick something part of this library, or part of base Opaleye? Also, does this mean that the callback's return value will need to call ToSQL or constant on every field (say I'm updating an ENUM)?

constant fn is from Opaleye lib which is used to convert value from Hask to Op. But I have added couple of instance as part of this lib, which made constant to work for tab Op -> Write Op db tab conversion.
Row passed to callback is Op value, and yes when u have update,you need lift the value from Hask to Op using fn like constant.
That's why in the example i have used constant S2 to update which lift the Haskell's Enum value to PGEnum
As for as ambiguity is concerned,  I will try to explain with different eg.
Eg. say for model
  data User f = User
    { userid   :: Col f "userid" Int
    , gender :: Col f "gender" (Maybe Text)
    , email :: Col f "email" Text
    , age :: Col f "age" (Maybe Int)
    }

In the above code,lets say only col userid and gender has Defaults.
Now Insert for User requires User record to be following shape to capture all the states
 User { userid :: Maybe Int          --- Captures 2 states (Explict NonNull, DB DEFAULT)
          , gender :: Maybe (Maybe Text) -- Captures 3 states (Explicit Null, Explict NonNull, DB DEFAULT)
          , email :: Text
          , age :: (Maybe Int)
          }

insert fn precisely does this by fixing appropriate f  to User.

Say for eg. you have following column with Defaults,
foo :: Col f "foo" (Maybe Int)
Even in this case, during Write column foo's type become Maybe (Maybe Int), allowing you to choose > DEFAULT value by passing Nothing, or null by passing Just Nothing, or a actual value Just (Just 1)

Above eg. explains how (Maybe (Maybe T)) let's you to capture 3 state that you were asking for

Ah, okay. Missed the nested Maybe

So, is stuff like Col f "userid" Int something you implemented or is it coming from Opaleye?

Also, how would you make sure that while writing (or updating) it's not possible to change the id, created_at, and updated_at fields, but they are accessible once the data is read back? Is it possible to constrain these fields to () during write operations alone, easily?

stuff like Col f "userid" Int is something I implemented on top of opaleye to share same models (in turn reducing verbosity) and to improve type inference. If you notice in the Readme, all the sample code work without any explicit type annotation even for type changing operation like projection, left join, aggregation & so on.
It is very much possible to provide an another variant of insert and update which will void out those column by turning its type into VoidF T rather that Maybe T and there by preventing you to set it. But that would mean that you will lose out the ability to override those DEFAULT value as well.
Reading back is unaffected, you will be be able to access the original value as it is and that is the case even now.


ModuleNotFoundError: No module named 'tornet.data'

I have tried to install the module and also uncomment the Sys line, but still ModuleNotFoundError: No module named 'tornet.data', could you help?

I assume you are trying to run one of the notebooks? It seems like a PATH related problem, python can't seem to find tornet.data. This should be taken care of when you run from the tornet root directory:
 pip install .

A quick solution would be to manually add tornet to sys.path at the beginning of your script.
sys.path.append("path/to/tornet")


tests: assert that cgpt does not clobber MBR boot code

In a recent bug report it wasn't clear if cgpt clobbered the MBR boot
code or not when recovering a corrupt GPT table. Add a test case to
verify cgpt behaves properly.

LGTM


Update .travis.yml

Add compilation info for stable rust versions

Do you think it is better to target named Rust version or just test against "stable" which will be the most recent stable version of Rust. I don't know how quickly people are upgrading to new stable Rust versions, but, my thinking is that they are probably doing it quickly. Thoughts?

I don't actually know what's best. I use multirust and stick with the last stable updates but I am not sure what is the common behaviour.
Probably it would be fine to track stable, maybe adding a comment with the releases saying under which minimal stable version that particular release of rust-crypto has been tested.

I think that's a great suggestion. I updated README.md in #322 to specify that the library targets just the most recent stable Rust version, currently 1.3. Thanks!


Update LinodeClient example docs in Python wrapper guide

Since we are importing it as from linode import LinodeClient above, we don't want linode.LinodeClient, I think

Coverage decreased (-0.03%) to 78.826% when pulling 83a7f41b171edfd2705fdc02cf4ba102fe214362 on rmcintosh:patch-6 into 39626e816762d11226f3000199b4f7b3fc5a2e0e on linode:master.

alternatively, we can just import linode in the example, which is arguably better IMO

mind changing base to develop?

@mparke whoops. Good call too... :(


Add timeout argument to commands

We have to input timeout parameters sometime.
raw_log: 'failed to execute message; message index: 0: receiving chain block height
  >= packet timeout height (2-825 >= 1-71613): packet timeout'

we need add  --packet-timeout-height string and --packet-timeout-timestamp uint

fixed this

#36


support for spinner-on attr

Would you support a PR for supporting a 'spinner-on' attr that would essentially start a watch and start/stop the spinner based on the value of that attr?

+1
this would help me too

Yea, a PR for that would be appreciated. I think that adding a new attribute for the existing directive would be a better approach than suggested in #47...
Thanks!


[stable/cluster-overprovisioner] Add app.kubernetes.io/fleetName label

Signed-off-by: Koen van Ingen<EMAIL_ADDRESS>What this PR does / why we need it:
When deploying multiple overprovisioning fleets, it's currently not possible to match on a specific fleet when using affinity/antiaffinity.
Which issue this PR fixes

This PR adds a label (app.kubernetes.io/fleetName) allows to match on a specific
overprovisioning deployment with matchExpressions/matchLabels in
affinity rules. The fleetName label will be unique per deployment fleet.

Special notes for your reviewer:

@max-rocket-internet
@mmingorance-dh

Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/chart])

/ok-to-test

/lgtm


Bump to Recharts V2

Renovate tried to bump Recharts from v1 to v2 but it looks like there's some breaking changes in the library that need fixing up in #12476
Let's bump to the latest library and fix up some of the Typescript errors that have started occurring part of the breaking changes.
It looks like there's absolutely 0 documentation on migration, https://github.com/recharts/recharts/issues/2333 so could be a little bit of trial and error, or maybe if someone has experience with doing this already and would like to help us out! :pray:

Yeah they are I believe, any package that has a hard dependency of recharts will need updating at the same time to work with the new API that they've released without much instruction on how to upgrade 🤷

Alright, I guess I can give this a go over the weekend and see how it goes. Can you assign this to me? 🤞

Of course! 👍

Thanks! 👍

@benjdlambert wasn't able to work on this the previous weekend. Will try to take this up this time around.

@asheerrizvi no worries - It's all good! 👊

@benjdlambert this one's a bit frustrating with the lack of any guide whatsoever lol. So I have got the project running on my local. Have upgraded recharts. For the typescript fixes I wanted to manually check if the graphs are working fine or not. Is there a way to do this on the UI for the plugins which need these upgrades?

Hmm, some of them might have storybook stories, and as a workaround if there isn't any you could always just create a sample story for it and mock out the data that gets passed to the component?

Alright, thanks. Will try that.

@benjdlambert I am not able to find the time to work on this. I am un assigning myself from this, maybe someone else will be able to take this up. :|

@benjdlambert just started working on this, could you please assign me?

Assigned.

@freben @benjdlambert done in https://github.com/backstage/backstage/pull/13517


[BUG] Roblox no longer closes when I leave a game

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.

What problem did you encounter?
It opens the beta app instead of closing like it should
Mainly from kick messages

Duplicate of #2049


Can't reuse dpex.func device functions  with different signatures

This used to work with numba_dpex<=0.18.1 but fails with >=0.19:
import numba_dpex as dpex
import dpctl.tensor as dpt
import numpy as np

@dpex.func
def g(array_in, idx, const):
    array_in[idx] = const

@dpex.kernel
def kernel_a(array_in):
    idx = dpex.get_global_id(0)
    g(array_in, idx, np.int64(0))

@dpex.kernel
def kernel_b(array_in):
    idx = dpex.get_global_id(0)
    g(array_in, idx, np.int32(0))  # NB: call with inputs of different types than in kernel_a

dtype = np.float32
size = 16
array_in = dpt.zeros(sh=(size,), dtype=dtype)

kernel_a[size, size](array_in)
kernel_b[size, size](array_in)

with numba_dpex>=0.19 this snippet gives the following exception:
<...traceback elided...>
LoweringError: Failed in dpex_nopython mode pipeline (step: Custom Lowerer with auto-offload support)
No definition for lowering <function get_global_id at 0x7f47c2edf700>(uint32,) -> int64

File "<ipython-input-14-e32b2bd5f6a0>", line 17:
def kernel_b(array_in):
    idx = dpex.get_global_id(0)
    ^

During: lowering "idx = call $4load_method.1($const6.2, func=$4load_method.1, args=[Var($const6.2, <ipython-input-14-e32b2bd5f6a0>:17)], kws=(), vararg=None, varkwarg=None, target=None)" at <ipython-input-14-e32b2bd5f6a0> (17)

There's a workaround that consists in ensuring that in both kernels the device function is at different memory locations with a different name, e.g.:
import numba_dpex as dpex
import dpctl.tensor as dpt
import numpy as np

def make_g():
    @dpex.func
    def g(array_in, idx, const):
        array_in[idx] = const
    return g

g = make_g()
@dpex.kernel
def kernel_a(array_in):
    idx = dpex.get_global_id(0)
    g(array_in, idx, np.int64(0))

g_ = make_g()
@dpex.kernel
def kernel_b(array_in):
    idx = dpex.get_global_id(0)
    g_(array_in, idx, np.int32(0))

dtype = np.float32
size = 16
array_in = dpt.zeros(sh=(size,), dtype=dtype)

kernel_a[size, size](array_in)
kernel_b[size, size](array_in)

@fcharras #877 fixes the issue along with overall improvements to how we cache and specialize func decorated functions. Can you please test the branch and confirm that the issue you were seeing is addressed?

The cache in https://github.com/IntelPython/numba-dpex/pull/877 looks like it's working. I've checked that there are cache hits here https://github.com/IntelPython/numba-dpex/blob/5c164789d5d361e650c2b0215fac3934ad5ac087/numba_dpex/core/kernel_interface/dispatcher.py#L580 when it's expected.
I have another issue but I don't think it's related to https://github.com/IntelPython/numba-dpex/pull/877 since I checked for cache hit and misses. My user code works fine with numba_dpex==0.19.0. But now it's super slow and some kernels seem to output wrong values, I think it comes from more recent commits on main. I can try to bisect..

The new problems are not related to #877 but to #876 , reported in https://github.com/IntelPython/numba-dpex/issues/816

Thanks @fcharras for your review. I am going ahead and merging #877 and closing this ticket.
I am opening a separate issue to track the performance regression introduced by #816.

But now it's super slow and some kernels seem to output wrong values,

Which kernels are running slow and outputting wrong values?


[QUESTION] [WEB] Font files embedded in bundle

[x] Review the documentation: https://github.com/oblador/react-native-vector-icons
[x] Search for existing issues (including closed ones): https://github.com/oblador/react-native-vector-icons/issues

Environment
React Native Environment Info:
System:
OS: Linux 4.4 Ubuntu 16.04.5 LTS (Xenial Xerus)
CPU: (2) x64 Intel(R) Pentium(R) CPU G630 @ 2.70GHz
Memory: 1.09 GB / 7.69 GB
Shell: 4.3.48 - /bin/bash
Binaries:
Watchman: 4.7.0 - /usr/local/bin/watchman
SDKs:
Android SDK:
API Levels: 23, 24, 25, 26, 27, 28
Build Tools: 23.0.1, 25.0.2, 26.0.1, 26.0.2, 26.0.3, 27.0.0, 27.0.3, 28.0.0, 28.0.2, 28.0.3
System Images: android-16 | Google APIs Intel x86 Atom, android-23 | Intel x86 Atom_64, android-23 | Google APIs Intel x86 Atom_64, android-24 | Google Play Intel x86 Atom, android-25 | Intel x86 Atom_64, android-25 | Google APIs Intel x86 Atom_64, android-27 | Intel x86 Atom_64, android-27 | Google APIs Intel x86 Atom
IDEs:
Android Studio: 3.3 AI-182.5<IP_ADDRESS>14842
npmPackages:
react: 16.6.1 => 16.6.1
react-native: 0.57.5 => 0.57.5
"react-native-vector-icons": "6.1.0",

Description
I want to reduce my bundle.js size by decoupling the font files from it. If I follow the installation from README for web, I end up having the font files embedded in my bundle, using this
import materialCommunityIconsFont from 'react-native-vector-icons/Fonts/MaterialCommunityIcons.ttf';
...
@font-face {
  src: url(${materialCommunityIconsFont});
  font-family: 'MaterialCommunityIcons';
}

but, if I do this:
//import materialCommunityIconsFont from 'react-native-vector-icons/Fonts/MaterialCommunityIcons.ttf'; <----- comment out
...
@font-face {
  src: url(${'./node_modules/react-native-vector-icons/Fonts/MaterialCommunityIcons.ttf'});
  font-family: 'MaterialCommunityIcons';
}

then I notice that a new network request is made to fetch the font from the directory and my bundle no longer contains this file.
Questions:

Is this behaviour (embedding fonts) intended?
Or is there something wrong with my config?

I know that I could create my own Custom font file in order to reduce the bundle size, but, I don't want to because I am not directly using this library but via native-base and react-native-paper and various others.
I am using BundleAnalyzerPlugin to determine whether or not the ttf files are embedded in my bundle or not.
Demo
Since this relates more to config than to rnvi itself, I don't think Snack can help us here.

webpack common config
const path = require('path');
const webpack = require('webpack');
const htmlWebpackPlugin = require('html-webpack-plugin');
const BundleAnalyzerPlugin = require('webpack-bundle-analyzer').BundleAnalyzerPlugin;

const appDirectory = path.resolve(__dirname, '../');

// This is needed for webpack to compile JavaScript.
// Many OSS React Native packages are not compiled to ES5 before being
// published. If you depend on uncompiled packages they may cause webpack build
// errors. To fix this webpack can be configured to compile to the necessary
// `node_module`.
const babelLoaderConfiguration = {
  test: /\.js$/,
  // Add every directory that needs to be compiled by Babel during the build.
  include: [
    path.resolve(appDirectory, 'index.web.js'),
    path.resolve(appDirectory, 'app'),
    // path.resolve(appDirectory, 'node_modules/')
    path.resolve(appDirectory, 'node_modules/@react-navigation/'),
    path.resolve(appDirectory, 'node_modules/native-base/'),
    path.resolve(appDirectory, 'node_modules/native-base-shoutem-theme/'),
    path.resolve(appDirectory, 'node_modules/react-native-collapsible/'),
    path.resolve(appDirectory, 'node_modules/react-native-confirmation-code-field/'),
    path.resolve(appDirectory, 'node_modules/react-native-dialog/'),
    path.resolve(appDirectory, 'node_modules/react-native-drawer/'),
    path.resolve(appDirectory, 'node_modules/react-native-easy-grid/'),
    path.resolve(appDirectory, 'node_modules/react-native-easy-toast/'),
    path.resolve(appDirectory, 'node_modules/react-native-floating-labels/'),
    path.resolve(appDirectory, 'node_modules/react-native-keyboard-aware-scroll-view/'),
    path.resolve(appDirectory, 'node_modules/react-native-material-buttons/'),
    path.resolve(appDirectory, 'node_modules/react-native-material-menu/'),
    path.resolve(appDirectory, 'node_modules/react-native-material-ripple/'),
    path.resolve(appDirectory, 'node_modules/react-native-materialui-textfield/'),
    path.resolve(appDirectory, 'node_modules/react-native-modal-datetime-picker/'),
    path.resolve(appDirectory, 'node_modules/react-native-paper/'),
    path.resolve(appDirectory, 'node_modules/react-native-swiper/'),
    path.resolve(appDirectory, 'node_modules/react-native-vector-icons/'),
    path.resolve(appDirectory, 'node_modules/react-native-web/'),
    path.resolve(appDirectory, 'node_modules/react-navigation-drawer/'),
    path.resolve(appDirectory, 'node_modules/react-navigation-stack/'),
    path.resolve(appDirectory, 'node_modules/react-navigation-tabs/'),
    path.resolve(appDirectory, 'node_modules/react-native-gesture-handler/'),
    path.resolve(appDirectory, 'node_modules/react-native-tab-view/'),
    path.resolve(appDirectory, 'node_modules/react-native-image-picker/'),
  ],
  use: {
    loader: 'babel-loader',
    options: {
      cacheDirectory: true,
      // The 'react-native' preset is recommended to match React Native's packager
      presets: ['module:metro-react-native-babel-preset'],
      // Re-write paths to import only the modules needed by the app
      plugins: ['react-native-web']
    }
  }
};

// This is needed for webpack to import static images in JavaScript files.
const imageLoaderConfiguration = {
  test: /\.(gif|jpe?g|png|svg)$/,
  use: {
    loader: 'url-loader',
    options: {
      name: '[name].[ext]'
    }
  }
};

const fontLoaderConfiguration = {
  test: /\.ttf$/,
  use: {
    loader: "url-loader", // or directly file-loader
    options: {
      name: './fonts/[hash].[ext]',
    },
  },
  include: path.resolve(appDirectory, "node_modules/react-native-vector-icons"),
}

module.exports = {
  entry: [
    // load any web API polyfills
    // path.resolve(appDirectory, 'polyfills-web.js'),
    // your web-specific entry file
    require.resolve('regenerator-runtime/runtime'),
    path.resolve(appDirectory, 'index.web.js')
  ],

  // configures where the build ends up
  output: {
    filename: 'bundle.web.js',
    path: path.resolve(appDirectory, 'dist')
  },

  // ...the rest of your config

  module: {
    rules: [
      babelLoaderConfiguration,
      imageLoaderConfiguration,
      fontLoaderConfiguration
    ]
  },

  resolve: {
    // This will only alias the exact import "react-native"
    alias: {
      'react-native$': 'react-native-web',
      'react-native/Libraries': 'react-native-web/src',
      'react-native-linear-gradient': 'react-native-web-linear-gradient',
      'react-native-fast-image': 'react-native-web/src/exports/Image',
      'react-native-photo-view': 'react-native-web/src/exports/Image',
      'react-native-modal': 'modal-enhanced-react-native-web',
      // 'react-native/Libraries/vendor': 'react-native-web/src/vendor/react-native',
      'app': path.resolve(appDirectory, 'app'),
    },
    // If you're working on a multi-platform React Native app, web-specific
    // module implementations should be written in files using the extension
    // `.web.js`.
    extensions: [ '.web.js', '.js' ]
  },

  plugins: [
    new webpack.DefinePlugin({
      __DEV__: process.env.NODE_ENV !== 'production'
    }),
    new BundleAnalyzerPlugin(),
    new htmlWebpackPlugin({
      template: 'web/index.html',
      inject: 'body',
    }),
  ],

}

index.web.js
import * as React from 'react';
import { AppRegistry } from 'react-native';

import App from './app/index';

import Icon from 'react-native-vector-icons/dist/FontAwesome';
import fontAwesomeFont from 'react-native-vector-icons/Fonts/FontAwesome.ttf';
import materialIconsFont from 'react-native-vector-icons/Fonts/MaterialIcons.ttf';
// import materialCommunityIconsFont from 'react-native-vector-icons/Fonts/MaterialCommunityIcons.ttf';
import ionIconsFont from 'react-native-vector-icons/Fonts/Ionicons.ttf';

const rootEl = document.getElementById('react-root');

const render = () => (
  <App />
);

AppRegistry.registerComponent('wishbook', () => render);
AppRegistry.runApplication('wishbook', {
  rootTag: rootEl,
});

// Generate required css
const iconFontStyles =
`@font-face {
  src: url(${fontAwesomeFont});
  font-family: FontAwesome;
}
@font-face {
  src: url(${materialIconsFont});
  font-family: 'MaterialIcons';
}
@font-face {
  src: url(${'./node_modules/react-native-vector-icons/Fonts/MaterialCommunityIcons.ttf'});
  font-family: 'MaterialCommunityIcons';
}
@font-face {
  src: url(${ionIconsFont});
  font-family: 'Ionicons';
}`;

// Create stylesheet
const style = document.createElement('style');
style.type = 'text/css';
if (style.styleSheet) {
  style.styleSheet.cssText = iconFontStyles;
} else {
  style.appendChild(document.createTextNode(iconFontStyles));
}

// Inject stylesheet
document.head.appendChild(style);

Closing this.
Resolution here https://github.com/peter-jozsa/react-native-web-image-loader/issues/7


update build.py with upstream changes

attempt to re-sync with https://github.com/jupyterhub/zero-to-jupyterhub-k8s/pull/325
The following features are needed here that aren't there:

build args need to derive from last_commit,
so support templating values in image buildArgs
last_commit needs to take a list of paths, not just one directory,
so support path lists at both image and chart level.

These should hopefully be added in a way that still works for the jupyterhub chart.
While working on this I fixed the timestamp issues by using helm repo index --merge to only add new files, not modify already-indexed files. The result is that existing entries will not be modified.

Thanks, @willingc!

Same file pushed to z2jh here: https://github.com/jupyterhub/zero-to-jupyterhub-k8s/pull/350


Connection migration

How to use your quiche project to implement the connection migration function?

Duplicate of #1693, please don't do that.


galley: discard the sync.Pool in api server status

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[x] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

Hi @panjf2000. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

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.

Hi @howardjohn, since you stop by, could you take a look at this?

Hi @hzxuzhonghu, since you stop by, could you take a look at this? this is a tiny but vital fix, it would be totally meaningless to use a sync.Pool if you don't put the object back into the pool after it's released, thanks!

Actually, i could not understand why the sync.Pool is necessary here.

Actually, i could not understand why the sync.Pool is necessary here.

For reusing the status struct when it is being created and released in high frequency?
But the status really doesn't seem like a struct big enough or being created so often to use a sync.Pool.
This is introduced by @ozevren in #17360, anyway, we ought to either add an action of putting objects back into the pool or just remove the sync.Pool directly.

or just remove the sync.Pool directly.

This is what i mean

Currently, the statusPool is nothing but a liability, so I suggest that we just throw it away?
If it is okay with you, I will start working on it in this PR. @hzxuzhonghu

Agree with that

@panjf2000: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
b9831e59a5bf1323f3c75d8fc2ab9740e23b0e9d
link
/test release-notes_istio

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.

/release-note-none

/release-notes-none

@panjf2000: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
b9831e59a5bf1323f3c75d8fc2ab9740e23b0e9d
link
/test release-notes_istio

integ-security-multicluster-tests_istio
b9831e59a5bf1323f3c75d8fc2ab9740e23b0e9d
link
/test integ-security-multicluster-tests_istio

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.

/retest

@panjf2000: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio
b9831e59a5bf1323f3c75d8fc2ab9740e23b0e9d
link
/test integ-security-multicluster-tests_istio

release-notes_istio
b9831e59a5bf1323f3c75d8fc2ab9740e23b0e9d
link
/test release-notes_istio

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.

Is there something wrong with the test environment? The integ-security-multicluster-tests_istio seemed to fail for some uncorrelated causes with this PR.
@hzxuzhonghu Any clues about that?

@panjf2000: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
b9831e59a5bf1323f3c75d8fc2ab9740e23b0e9d
link
/test release-notes_istio

integ-security-multicluster-tests_istio
b9831e59a5bf1323f3c75d8fc2ab9740e23b0e9d
link
/test integ-security-multicluster-tests_istio

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 integ-security-multicluster-tests_istio

Sorry to comment this on every one of your PRs, but please describe what issues this is fixing or we cannot review it appropriately.
Historically, these types of PRs often look innocent then months down the line lead to outages or security regressions.

In the first place, I notice there is missing a pool.Put action for a sync.Pool containing status struct, so I opened a PR adding this action, see here.
However, after discussing with @hzxuzhonghu , we all agree to discard the sync.Pool cuz it doesn't seem to be worth.

Shall we continue this PR? @hzxuzhonghu

@howardjohn This is kind of clean up

/assign @howardjohn

Have a look at this?

PTAL @howardjohn

PTAL @howardjohn

It's been more than a week, so how should we treat this change? any definite decisions?

PTAL @howardjohn

The current code with the sync.Pool is totally bootless and even drags down this part for not putting objects back into pool, if you are not happy with this ultimate change, I think at least we should return to this commit: https://github.com/istio/istio/pull/29240/commits/6d3855d9d4708f45a5846e69079cca0c6ec496cb

The current code with the sync.Pool is totally bootless and even drags down this part for not putting objects back into pool, if you are not happy with this ultimate change, I think at least we should return to this commit: 6d3855d

If there is no user facing bugs as a result of this code, I see no reason to change this. We are planning to completely remove this code in 1.9 (https://github.com/istio/istio/issues/23943)


Expanding instant pickup to all player kills

This is a super useful feature, and I think the only way it could be improved upon is allowing all mob drops caused by player kills to also be vacuumed up. This would be nice QoL for bows and crossbows, tridents too.
Haven't thought about the balance implications, perhaps ranged options could be limited to loyalty tridents? 🤷🏽
edit: It already works as intended if within melee range of the mob.
edit 2: it works on some ranged attacks like botania's terra blade beam or key of the kings law, idk why that's the case

Thought about it a bit more and I think the feature works fine as is - ranged weapons already have the advantage of not needing to get close, doesn't really need a loot delivery system as well.


Bug: Demo does not work in IE

Description:
I was having an issue opening my project in IE, so I wanted to make sure the demo was working in IE 11. Doesn't look like I'm able to do many of the interactions, with the keyboard or the mouse.
Steps to Repro:

Open the demo in an IE11 browser window: https://schne324.github.io/dragon-drop/demo/
Tab to the first example to put the handle in focus
Press the Space bar and either of the arrow keys to move the item, OR
Click and drag with the mouse to move the item

Expected Result:
Item moves up/down, as seen in Chrome
Actual Result:
Handle is in focus, but not selected. Arrow keys scroll browser window.

Thanks for finding this issue. The only IE11 I have access to is through parallels with edge and emulation of IE11 which for whatever reason works as expected. Looking at the source though I do see that some dependencies are using things like arrow functions and const so I will take a look at ensuring everything is transpiled. I'll let you know when the issue is resolved and have you confirm that the demo works in ie11.

@lcecil I just tagged version 3.2.4 which has the fix for this. Please confirm that the demo is working in IE11 now, if its not I will reopen this issue.
Thanks!

Just tried it again, and I'm still getting syntax errors in the console. Looks like either the polyfill isn't working or there are still some fat arrows in there.
One error at this portion of the dragon-drop.js:
const getEnumerableOwnPropertyKeys = value => ...
And this in the demo:
demo3Dragons.forEach(instance => instance.on('announcement', onAnnouncement));

ooops just realized I didn't redeploy the demo site, I just updated the package itself. Sorry about that, let me redeploy and I'll let you know when the demo site has been updated

Alright I just updated the demo, good catch on that arrow function use in the demo3Dragons loop<EMAIL_ADDRESS>has removed the dependency that added the getEnumerableOwnPropertyKeys function so we should be good there.  Please check again and let me know. Again, sorry for the confusion on my end

No problem! Must be difficult to debug without having access to IE :)
Getting a new error now:
Line: 78 Error: Object doesn't support property or method 'from'
Looks like you've got var lists = Array.from(containers);, and I don't think .from() is supported in IE.

Ah ok, I'll take at using a polyfill solution. Thanks for looking into this for me. I will reopen this ticket and let you know when I address this

@lcecil I just added babel-polyfill which should take care of all these problems. Could you check the demo out for me and confirm that stuff works in IE11? If this is resolved I will tag a new release

@schne324 can you ping me when you tag the new release? much appreciated.

@lcecil<EMAIL_ADDRESS>has been published


⚠ Minecraft has degraded performance

In 1ce5371, Minecraft (https://www.minecraft.net) experienced degraded performance:

HTTP code: 200
Response time: 1427 ms

Resolved: Minecraft performance has improved in 3d48c66.


Add optional allocation counter

Add counter of allocations for tracking memory usage - see trezor/trezor-firmware#1324 for more information. The feature is off by default and has to be explicitly enabled at build time.

Updated. Device tests do <100 millions allocations total so there's quite a margin and if we wanted we can detect the counter overflowing -  mp_uint_t is fine.

Merged, thanks!


HTML config "as is"

Hello everyone,
I am not a programmer, but still a happy potree user.
Currently I am looking at how I could move, rotate, change the point budget, point size, attribute, volume clip and so on ... AND THEN SAVE ALL THESE PARAMETERS so that I can edit my HTML quickly and easily before uploading it again.
Any idea?
Thanks All

Hi, please have a look at the http://potree.org/potree/examples/load_project.html demo of the latest version of Potree. It may support at least some of the attributes.


Revert "finish the delegated_bandwidth->self_delegated_bandwidth"

Reverts EOS-Mainnet/eos#31

reverted because it wasn't the appropriate fix


Run tests against Django 3.1 instead of 1.11

Issue #, if available: n/a
Description of changes: Ensure support for Django 3.1, ignore Django 1.11.

Django 1.11 (LTS) reached its EOL on 2020-04-01.  The current LTS release is 2.2.
Django 3.1 was released on 2020-08-04.

The list of supported version is available at https://www.djangoproject.com/download/.
The test failures are unrelated, see aws/aws-xray-sdk-python#239.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

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

@@            Coverage Diff             @@
##           master     #240      +/-   ##
==========================================
- Coverage   79.36%   79.29%   -0.07%
==========================================
  Files          80       80
  Lines        3159     3159
==========================================
- Hits         2507     2505       -2
- Misses        652      654       +2

Impacted Files
Coverage Δ

aws_xray_sdk/core/sampling/local/reservoir.py
88.88% <0.00%> (-11.12%)
:arrow_down:

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 a2e4bc6...ed97723. Read the comment docs.


bug about unicode set

new RandExp(/\p{White_Space}/).gen() // => 'p{White_Space}'

also not support \u{1B000}

hi,
any progress with that?


Sprocket error at install

My app (Rails 6.1.3 / Administrate v0.16) was working before I tried to integrate this plugin.
I just added the gem and bundle, and now I get this error when I load any administrate page :
Sprockets::Rails::Helper::AssetNotPrecompiled in Admin::Users#index

Showing /app_path/app/views/admin/application/_stylesheet.html.erb where line #11 raised:
administrate-field-nested_has_many/application.css
Extracted source (around line #11):

9
10    <% Administrate::Engine.stylesheets.each do |css_path| %>
11      <%= stylesheet_link_tag css_path %>
12    <% end %>
13

Application Trace | Framework Trace | Full Trace
app/views/admin/application/_stylesheet.html.erb:11
app/views/admin/application/_stylesheet.html.erb:10:in `each'
app/views/admin/application/_stylesheet.html.erb:10
app/views/layouts/admin/application.html.erb:24

There is a current PR addressing this issue : https://github.com/nickcharlton/administrate-field-nested_has_many/pull/45
If you have this pb, you can use this workaround by  @pablobm : https://stackoverflow.com/questions/67762580/rails-6-administrate-sprocket-error-when-installing-administrate-field-neste