pipx installation incompatible with external lib dependencies in commands

I don't know if it is an issue, but if I installed click-project through pipx, I cannot execute a command with dependencies that are not already embedded with pipx.
E.G if I have a command that imports pandas, the command fails.
Is there a way to add a directory to the clk python path ? maybe in some parameters ?

Indeed, to take advantage of the features provided by click-project, the command needs to have the click-project packages available. Also, click-project basically imports the commands like it would import any other package.
Naively, it makes sense that both must be in the same virtualenvironment for this to work. Actually, this issue is the sign that pipx did well its job in the first place, meaning isolating the python runtime of the installation of click-project.
Yet, this seems like a sensible request. I guess we need to find a good way to make a command access third party libraries.
So far, I guess that we could add a way to install third party libraries where clk is installed, either by providing a function that the command would call
It would look like:
from click_project.lib import install_package
install_package("pandas")
import pandas as pd

or
from click_project.lib import install_package
pd = install_package_import("pandas", pandas)

Otherwise, we could add a command in clk to access pip from inside the virtualenv, like clk pip..., this would allow clk pip install pandas
Most likely we could benefit from providing both :-P.

I've added the command clk pip that run the pip command inside the virtualenv of the installed clk.
When the 0.14.0 is out, you could try using it.
Actually, I would suggest otherwise: try to install click-project with pipx install --system-site-packages click-project
This will let clk have access to pandas installed outside of the venv. IMHO, it is the most elegant way of using click-project. Since most likely your commands will naturally depend on globally installed dependencies.

I updated the documentation to help people paliate this kind of issue. https://github.com/Konubinix/click-project#why-cannot-i-run-my-command-that-needs-library-x-that-is-installed-on-my-computer
I don't think of anything else to be done in the scope of this issue. So I am closing it now. Feel free to reopen it if you think the subject might need more attention.
Thanks for your report.


[Chaos-Module]: Add steps to use named profile for AWS faults

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the maintainers.
What Type of PR is This?
This PR contains:

Steps to use the named profiles to run the AWS faults - this will help the user to choose different profiles (credentials) to run specified fault in HCE.

Restructure the credentials instructions.

[ ] Issue

[ ] Feature

[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Preview environment: https://ci.pr.harness.io/pr-604

Working on fixing the build error. Will approve and merge this once the build is fixed.

Preview environment: https://ci.pr.harness.io/pr-604


Conversations API deprecation - Get-SlackGroup

Not going to have time to do this, but the following will likely break on Feb 24:
https://github.com/RamblingCookieMonster/PSSlack/blob/master/PSSlack/Public/Get-SlackGroup.ps1
Not sure if anything else will go.  https://api.slack.com/changelog/2020-01-deprecating-antecedents-to-the-conversations-api#methods Contains the list of endpoints that will be removed Feb. 24th.

Fixed in PR #115


One or more enabled YUM repo are currently unsupported.

I have no idea what to do to resolve a notice I received about an obstacle to update to Almalinux, an unsolicited event.  The notice says:
Elevate | The system detected the following issues which   would prevent cPanel ELevate from upgrading the system to AlmaLinux 8:        One        or more enabled YUM repo are currently unsupported. You should disable        these repositories and remove packages installed from them before        continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues            Issue        with sshd configuration
Also:
Issue with sshd configuration
Which issue?  What to do?

Hi, We don't have enough information to advise you here. What repositories are missing?

Hi, I recommend you open a ticket with cPanel support for further assistance. Thanks!


Command Error

Command that caused the error
@esmBot bandicam
Image that caused the error
i don't know :/
Steps to reproduce

Go to '...'
Click on '....'
Scroll down to '....'
See error

Self-hosted instance?
No
Error file

error.txt
Additional context
No response

Duplicate of #178


how to config vscode to show autocomplete

there is no autocomplete suggestion

Hey @agileago did you add this configuration to your vscode settings.json ?
{
  "tailwindCSS.experimental.classRegex": [
    ["tv\\(([^)]*)\\)", "[\"'`]([^\"'`]*).*?[\"'`]"]
  ]
}

Here's you can find more details: https://www.tailwind-variants.org/docs/getting-started#intellisense-setup-optional

perfect !! thanks for your work !!!


add osx support

Looking into what would be necessary for osx support
fix https://github.com/conda-forge/qe-feedstock/issues/17

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

Hi! This is the friendly automated conda-forge-linting service.
I was trying to look for recipes to lint for you, but it appears we have a merge conflict.
Please try to merge or rebase with the base branch to resolve this conflict.
Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug.

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.

I think you might have to rerender to enable OS X CI?
@conda-forge-admin, please rerender

thanks! yes, I'd done that but in the rebase I removed the commit to avoid conflicts - thanks for putting it back :-)

hmmm, the build errors at linking libpw.a because the fft libs are not found
libpw.a
mpif90 -fopenmp -Wl,-pie -Wl,-headerpad_max_install_names -Wl,-dead_strip_dylibs -Wl,-rpath,$PREFIX/lib -L$PREFIX/lib -o pw.x \
   pwscf.o  libpw.a ../../Modules/libqemod.a ../../KS_Solvers/libks_solvers.a ../../upflib/libupf.a ../../FFTXlib/libqefft.a ../../LAXlib/libqela.a ../../UtilXlib/libutil.a ../../dft-d3/libdftd3qe.a $SRC_DIR//clib/clib.a $SRC_DIR//LIBBEEF/libbeef.a    -L$PREFIX/lib -llapack -L$SRC_DIR//FoX/lib  -lFoX_dom -lFoX_sax -lFoX_wxml -lFoX_common -lFoX_utils -lFoX_fsys   -L$PREFIX/lib -lblas
mpif90 -fopenmp -Wl,-pie -Wl,-headerpad_max_install_names -Wl,-dead_strip_dylibs -Wl,-rpath,$PREFIX/lib -L$PREFIX/lib -o pw.x \
   pwscf.o  libpw.a ../../Modules/libqemod.a ../../KS_Solvers/libks_solvers.a ../../upflib/libupf.a ../../FFTXlib/libqefft.a ../../LAXlib/libqela.a ../../UtilXlib/libutil.a ../../dft-d3/libdftd3qe.a $SRC_DIR//clib/clib.a $SRC_DIR//LIBBEEF/libbeef.a    -L$PREFIX/lib -llapack -L$SRC_DIR//FoX/lib  -lFoX_dom -lFoX_sax -lFoX_wxml -lFoX_common -lFoX_utils -lFoX_fsys   -L$PREFIX/lib -lblas

and indeed there is no -lfftw in this link line... I'll check the configure output

@jan-janssen @wolfv looks like we have a MacOS version - please review :-)
Also fixes #17
Please "squash" this one - no need to pollute the commit log.

P.S. To start a good practice:
linux configure output
The following libraries have been found:
  BLAS_LIBS=-lblas
  LAPACK_LIBS=-llapack
  SCALAPACK_LIBS=-lscalapack
  FFT_LIBS=-lfftw3_omp -lfftw3 -lm

Please check if this is what you expect.

If any libraries are missing, you may specify a list of directories
to search and retry, as follows:
  ./configure LIBDIRS="list of directories, separated by spaces"

Parallel environment detected successfully.\
Configured for compilation of parallel executables.

macos configure output
The following libraries have been found:
  BLAS_LIBS=-lblas
  LAPACK_LIBS=-llapack
  SCALAPACK_LIBS=-lscalapack
  FFT_LIBS=-lfftw3_omp -lfftw3 -lm

Please check if this is what you expect.

If any libraries are missing, you may specify a list of directories
to search and retry, as follows:
  ./configure LIBDIRS="list of directories, separated by spaces"

Parallel environment detected successfully.\
Configured for compilation of parallel executables.

@conda-forge-admin, please rerender

@jan-janssen @wolfv looks like we have a MacOS version - please review :-)
Also fixes #17
Please "squash" this one - no need to pollute the commit log.

Thanks a lot - great work - looks fine to me.


Fixed bug with multiple validation errors at one field

Why @NotNull instead of @NotBlank on User.password field?

@Schema?

Where did the diffence come from on UserCreationDto(left) and UserUpdateDto(right)

not the topic of the pr, but add @Schema here as well please
And maybe copy validation for password & login(if prossible) from UserCreationDto to avoid redundant requests & burden on the server?


Improved deno provider support

Currently the deno provider throws when it resolves an npm: package specifier. This makes some sense, since denoland doesn't host npm packages, but it's a bit annoying because whenever an installed package has an npm package as a transitive dependency it's basically unusable with jspm (see https://deno.land/manual@v1.31.2/node/npm_specifiers).
Not sure what to do here - perhaps we should direct the user to the providers option docs and advise them to configure a non-deno provider to resolve npm:-registry stuff? At the moment the error is very obscure unless you understand generator internals.

Agreed we should definitely not throw on this - we can treat it the same as we do for node: URLs (in Node.js of course).


Font size issues

[x] Font atlas is generated/cached only once per font (and not per font-size; so if you need a higher resolution, you're out of options);
[x] The SpaceComponent is completely ignored w.r.t. the size / area in which to draw the text. font.Size is the only thing that currently defines the size of the text.

#488 is a duplicate of part two of this

Fixed in #499


[!] CocoaPods could not find compatible versions for pod "hermes-engine":

Build/Submit details page URL
https://expo.dev/accounts/djordan218/projects/395AB/builds/3ef888ab-d120-49a0-bae2-b2006694be68
Summary
I am trying to use EAS CLI to send my iOS build to the app store and keep getting this error. The Google Play Store build went just fine. Would love to find a solution.
I have tried clearing the cache and building again.
I have tried npx pod install.
Still getting the same error.
Managed or bare?
Bare
Environment
expo-env-info 1.0.5 environment info:
System:
OS: macOS 13.3.1
Shell: 5.9 - /bin/zsh
Binaries:
Node: 19.6.1 - /opt/homebrew/bin/node
Yarn: 1.22.19 - /opt/homebrew/bin/yarn
npm: 9.6.0 - /opt/homebrew/bin/npm
Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.12.0 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 22.4, iOS 16.4, macOS 13.3, tvOS 16.4, watchOS 9.4
IDEs:
Android Studio: 2022.1 AI-221.6008.13.2211.9619390
Xcode: 14.3/14E222b - /usr/bin/xcodebuild
npmPackages:
expo: ~48.0.4 => 48.0.12
react: 18.2.0 => 18.2.0
react-native: 0.71.6 => 0.71.6
npmGlobalPackages:
eas-cli: 3.9.3
expo-cli: 6.3.2
Expo Workflow: bare
✔ Validating global prerequisites versions passed
✔ Checking for incompatible packages passed
✔ Checking for conflicting global packages in project passed
✔ Verifying prebuild support package versions are compatible passed
✔ Checking dependency versions for compatibility with the installed Expo SDK passed
✔ Validating Expo Config passed
✔ Checking package.json for common issues passed
Didn't find any issues with the project!
Error output
Using Expo modules
[Expo] Enabling modular headers for pod ExpoModulesCore
Auto-generating .xcode.env.local with $NODE_BINARY=/Users/expo/.nvm/versions/node/v16.18.1/bin/node
Auto-linking React Native modules for target 395AB: RNCAsyncStorage, RNDateTimePicker, RNGestureHandler, RNReanimated, RNScreens, react-native-date-picker, react-native-safe-area-context, and react-native-webview
Framework build type is static library
[stderr]
[!] The version of CocoaPods used to generate the lockfile (1.12.0) is higher than the version of the current executable (1.11.3). Incompatibility issues may arise.
[Codegen] Generating ./build/generated/ios/React-Codegen.podspec.json
Analyzing dependencies
Fetching podspec for DoubleConversion from ../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec
[Codegen] Found FBReactNativeSpec
Fetching podspec for RCT-Folly from ../node_modules/react-native/third-party-podspecs/RCT-Folly.podspec
Fetching podspec for boost from ../node_modules/react-native/third-party-podspecs/boost.podspec
Fetching podspec for glog from ../node_modules/react-native/third-party-podspecs/glog.podspec
Fetching podspec for hermes-engine from ../node_modules/react-native/sdks/hermes-engine/hermes-engine.podspec
Adding spec repo trunk with CDN https://cdn.cocoapods.org/
CocoaPods 1.12.1 is available.
To update use: gem install cocoapods
For more information, see https://blog.cocoapods.org and the CHANGELOG for this version at https://github.com/CocoaPods/CocoaPods/releases/tag/1.12.1
[!] CocoaPods could not find compatible versions for pod "hermes-engine":
In snapshot (Podfile.lock):
hermes-engine (from ../node_modules/react-native/sdks/hermes-engine/hermes-engine.podspec)
In Podfile:
hermes-engine (from ../node_modules/react-native/sdks/hermes-engine/hermes-engine.podspec)
It seems like you've changed the version of the dependency hermes-engine and it differs from the version stored in Pods/Local Podspecs.
You should run pod update hermes-engine --no-repo-update to apply changes made locally.
Error: Compatible versions of some pods could not be resolved.
You are seeing this error because either:

Versions in the cached Podfile.lock do not match required values in Podspecs of some installed libraries. To fix this, you can re-run build command with "--clear-cache" option, or select "Clear cache and retry build" on the build page.
Some of the pods used in your project depend on different versions of the same pod. See logs for more information.

 I corrected it to match (from 0.71.6 to 0.71.3) and got it to build.


Support Microsoft Outlook

Outlook is widely used in most company, when it can be supported ?

In case it helps, linking in someone else's effort here too - though it appears to trample the existing formatting of an email (eg signature) and doesn't support emoji.
🔗 https://github.com/mmanela/MarkdownOutlook
Agree with @jeffason would be nice to have various efforts consolidated into Markdown-Here.

This would be awesome.

@adam-p said on 5/31/13:

This is not probable in the short term.

Problems: a) I don't own a copy of Office/Outlook newer than 2003 or so. (I have the Office 2013 trial installed. It's expired, but maybe it would work.) b) After some research and trying It seems like VS2012 Express can't be used to create Outlook addins.

Both of those are basically monetary hurdles, but expensive ones. (I haven't done the technical research to see how easy or hard the actual code would be.)

Is there any  update on this? Are the monetary hurdles still the gating factor? I have an idea if the author is interested. This is such a great idea - it pains me to see it languish. I'd like to help; please advise.
As a side note: I've posted a related question in the discussion group, but that group appears to be inactive. Is it?

As a follow up, I just found a tutorial published by MS on the subject of add-ins for Outlook.
Here's the relevant passage:

Outlook Add-ins are comprised of HTML, CSS, and JavaScript files, so technically the only absolute prerequisite is some sort of web server to host the files.

There's also a link to a GitHub page for the "Microsoft Office Add-in Project Generator".

Tried the markdown plugin and it has issues. Is there anything new about this issue?


First, I was hovering over a cerulean bucket of...something in creative mode when it crashed. I believe Stupid Things adds liquid rubber into the game, so it was probably that.
Second, I tried to read The Aurorian patchouli book, and it crashed while opening the book. I saw the book for a split-second, and then I crashed.
Both crashes' logs look nearly identical, but here they both are. They mention something about tooltip text and hovering over items.
1st Crash Log: https://paste.dimdev.org/arivuyolul.mccrash
2nd Crash Log: https://paste.dimdev.org/xemeqezowu.mccrash

Seems like a NullPointerException with their mod right here. I'm not sure what I can change to fix it at the moment.

Oh, you're right! I see a couple of comments on Stupid Things' CurseForge page complaining of other crashes, also caused by a NullPointerException. That has to be their problem. I guess I'll have to remove that mod from my pack then.


Add a new NINJA_STATUS format: %E for ETA time.

'%E' prints a time remaining to complete the build.
Now '%e' and '%E' both print not just seconds, but h:mm:ss.

@nico, ping :-)

This assumes that all edges run at the same rate, right? I think previous discussions about this suggested using historical times from .ninja_log if present, which someone said makes the ETA much more precise.

This assumes that all edges run at the same rate, right? I think previous discussions about this suggested using historical times from .ninja_log if present, which someone said makes the ETA much more precise.

OK, so I close this PR. Thanks.

Superseded by #1963.


Migrate to 2021 edition

Closes str4d/age-plugin-yubikey#52.

Codecov Report

Merging #56 (5afec28) into main (6fd6a20) will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##            main     #56   +/-   ##
=====================================
  Coverage   5.41%   5.41%
=====================================
  Files          4       4
  Lines        203     203
=====================================
  Hits          11      11
  Misses       192     192

Impacted Files
Coverage Δ

src/format.rs
0.00% <ø> (ø)

src/key.rs
7.74% <ø> (ø)

src/p256.rs
0.00% <ø> (ø)

Continue to review full report at Codecov.

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


Warn when importing vanilla contracts package

Users should only install contracts from oz/contracts-eth-package, not oz/contracts. Warn about this when an import for the vanilla contracts package is found.
Fixes #1297

@frangio updated!


Tool to diff the generated benchmarks

As we are going to generate the benchmarks with python scripts. It will be good to have a tool to show the diff after changing the benchmark generators. So we can check what benchmarks are added/removed and make sure we don't generate exploded numbers of benchmarks.

Close as not planned


feat: add why-every-platform-engineer-should-care-about-kubernetes-operators blog

Proposed changes

Unreleased product version (optional)

Related issues (optional)

@asaf title thoughts?

For search engine optimization's sake, whatever your primary keyword/term you wish to rank for, include it in the title (and preferably in H1 and meta description). Reference slides 3 to 6 here: https://docs.google.com/presentation/d/1OvdLR_25BXrAvozYt5XzMNGBVuy9a_NL4gsnEz1_uZA/edit#slide=id.g3164f0b88d5_0_35.


npm dependencies

Being dependent on GitHub repos for this package dependencies making it hard to use in an internal network.
Is there a possibility of using the published npm packages of your dependencies?

Not possible without sacrificing the latest updates from CodeMirror. Often they patch bugs and commit those fixes to GitHub without creating a new version.


feature request - AC temperature

First of all I'd like to say thank you for this software.
I see the temperature of the AC side in the app, so the inverter must have it as information.
Can this information be provided in the deye-read output ?

Hi,
The registers are already in the master branch and will be listed by deye-read in the next version. The AC temp should correspond to the HeatsinkTemp

Version 0.1.5 has been published, the heatsink temp should be visible after upgrade.

@githubDante thank you for your very fast response. Works perfect


add switchMap

Signed-off-by: Frederik Krautwald<EMAIL_ADDRESS>

Yes, I wanted to do so, just forgot it.


[CI - test_optimizer] GitHub Actions, Melos, very_good test lead sometimes to cache error

Description
We use GitHub Actions with the caching support of the subosito/flutter-action@v2 together with Melos and every now and then we run into the following error:
cache/bundled/test_optimizer_0.1.0+1_e324e538d331470906db7fbaea6b8d957bcce68d/hooks/build/hooks/pre_gen/pre_gen_7389adb0f4462262bdd04123d3826c0231f89ed6.dart': No such file or directory
Melos config looks like this:
  ci:test:
    run: |
      melos exec -c 4 -- \
        very_good test --coverage --test-randomize-ordering-seed random

Steps To Reproduce

Create a minimal project with melos multiple packages
Add a CI with GitHub Actions
Run very_good test with 4 concurrencies via melos in all packages

Expected Behavior
No error
Additional Context
I know that is not a perfect issue, but any help is much appreciated.

Hi @md-weber 👋 Thanks for opening up an issue.
Would you be able to provide a sample project that can clearly demonstrate this? We don't tend to work with a lot of projects using Melos so want to make sure we are not spinning our wheels or trying something different then what your putting together. One other thing to ask is if you have tried this without the concurrency flag. We have seen some issues with that in the past and would like to be able to rule that out quickly if possible.
Thanks in advance and looking forward to your reply.

Hi @tomarra thanks for your answer, I will work on a demo example this weekend and hope that I can provide you an example till next week.
At the moment we did exactly that to at least not see the warning anymore. As soon the concurrency is out, it works flawless. If that just mean we cannot use concurrency in Melos it is still good to have that issue so that people know about it 👍


Ensure order in decoder

Currently "decodeFuncJSON" will not maintain key order when decoding data. For example the following JSON
{ "x":1,"y":2 }

Could be decoded as either { x: 1, y: 2} or { y: 2, x: 1}.

This is an issue with the mongopb library, not gidari.


[ENHANCEMENT] Automatically parse name of SSH key

Is your enhancement related to a problem? Please describe.
When creating SSH key, it will be conveient if Name can be automatically parsed from key content just like the behavior in image creating.

[!NOTE]
It will work only when the name contains "@" , e.g<EMAIL_ADDRESS>
Describe the solution you'd like

Describe alternatives you've considered
n/a
Additional context
n/a

Hi @Yu-Jack ,
Can we test this on non v1.4.0 branch or w/ specific ui-source?

@albinsun yes, it's nothing related to backend, it's just frontend.

Provide test result on v1.2-f414942f-head, close as fixed.
Environment

Harvester

Version: v1.2-f414942f-head
Profile: QEMU/KVM, single nodes (8C/16G/500G)
ui-source: Auto

Test Steps

Go to Settings -> ntp-servers

Provide test result on master-ba586eaf-head, suffix w/o @ still not parse.
Should I use other ui-index sourse?
Please help to check, thanks.
Environment

Harvester

Version: master-ba586eaf-head
Profile: QEMU/KVM, single nodes (8C/16G/500G)
ui-source: Auto

Test Cases
Read from File

 :green_circle:  Mail suffix

 :red_circle: Name suffix

:white_circle: Empty suffix

Paste

:white_circle: Mail suffix

:white_circle: Name suffix

:white_circle: Empty suffix


j2objc(Podspec|Xcode) disabled for translateOnlyMode

Necessary when running on Windows & Linux

@advayDev1 - I haven't tried this on Windows or Linux but since we moved j2objcXcode to part of the build, it must be possible to disable it on that platform.

lgtm + comment

That'll spew out a lot of noise in the build. The user will already see shared:j2objcXcode SKIPPED anyway, so I don't feel this adds value. I've add a single info log that translateOnlyMode is enabled but that will only be shown once.


diff algorithm puts  after  instead of replacing it

see 8-state.glass

it has to do with state getting added to the document while request is also being removed/replaced. if you don't have the setState lines in Init, it doesn't do it


[ci] Enable more usage of the bitstream cache

Add a manifest fragment target for the cached CW340 bitstream.
Consolidate the various FPGA build scripts into a template. This is largely copied from the other repo, and moving to the template for chip_earlgrey_cw310_hyperdebug and chip_earlgrey_cw340 enables them to use the same logic for using cached bitstreams and skipping Vivado builds.
Exempt more files from triggering bitstream builds when they change, such as hjson files and templates. Because we check in generated RTL, checking for changes to the generated code is sufficient. Checking only that code also prunes unrelated changes.

Hopefully this will relieve some pressure from the CI FPGA builders.

Nice change, this definitely makes the pipeline easier to read!


Usage with TypeScript raises error in as.d.ts

Hello!
I tried to add your library to my project, which was bootstrapped with create-react-app and TypeScript. When I try to use your Button component (import { Button } from 'reakit';), the following error appears:
path/to/project/node_modules/reakit/ts/as.d.ts
(1,8): Module '"path/to/project/node_modules/@types/react/index"' has no default export.

This are my dependencies:
{
  "dependencies": {
    "react": "^16.4.2",
    "react-dom": "^16.4.2",
    "react-redux": "^5.0.7",
    "react-scripts-ts": "2.17.0",
    "reakit": "^0.14.2",
    "rebass": "^2.0.0-10",
    "redux": "^4.0.0",
    "redux-persist": "^5.10.0",
    "reselect": "^3.0.1",
    "styled-components": "^3.4.2",
    "tslint": "^5.11.0"
  },
  "devDependencies": {
    "@commitlint/cli": "^7.0.0",
    "@commitlint/config-conventional": "^7.0.1",
    "@types/jest": "^23.3.1",
    "@types/node": "^10.5.8",
    "@types/react": "^16.4.9",
    "@types/react-dom": "^16.0.7",
    "@types/react-redux": "^6.0.6",
    "@types/rebass": "^0.2.23",
    "husky": "^0.14.3",
    "lint-staged": "^7.2.2",
    "prettier": "^1.14.2",
    "typescript": "^3.0.1"
  }
}

Is the error on my side? Do I need to do additional steps to use your components?

Could you try to add "allowSyntheticDefaultImports": true to your tsconfig.json?
@wordofchristian Do you know if we can use our own tsconfig.json for our files, even when people are consuming them?

Constate will have types soon. I'm working on it right now and should be finishing it by this weekend.
We'll fix the Cannot find module issue. Actually, that happens because not all of our components are written in TS yet. We're gradually transforming them. I'll see if we can add empty declaration files for those that are still in JS.
In the meanwhile, I guess you can fix those problems adding it to your tsconfig.json:
"skipLibCheck": true

Thanks! Sounds good - if I find some time, maybe I can try to support you with transforming your components. Let me know if there's a good place to start!

That would be definitely helpful. You can start by the simple ones in https://github.com/reakit/reakit/tree/master/packages/reakit/src

Hey, @ca057. We've released v0.14.3 with a fix for this issue. Could you try it?

The issue is resolved, thanks for the fast resolution!
But now I get an error due to two versions of styled-components, as I have it as well as a dependency. Seems related to #180 :
Running yarn list styled-components returned with<EMAIL_ADDRESS>yarn why v1.9.4
[1/4] Why do we have the module "styled-components"...?
[2/4] Initialising dependency graph...
[3/4] Finding dependency...
[4/4] Calculating file sizes...
=> Found<EMAIL_ADDRESS>info Has been hoisted to "styled-components"
info Reasons this module exists
   - Specified in "dependencies"
   - Hoisted from "reakit#styled-components"
info Disk size without dependencies: "4.19MB"
info Disk size with unique dependencies: "10.43MB"
info Disk size with transitive dependencies: "19.68MB"
info Number of shared dependencies: 24
Done in 2.73s.

Now it's returning:
yarn list v1.9.4
warning Filtering by arguments is deprecated. Please use the pattern option instead.
├─<EMAIL_ADDRESS>│  └─<EMAIL_ADDRESS>└─<EMAIL_ADDRESS>Done in 1.75s.

Well, we probably bumped the styled-components dependency ahead of you. What is the error?

Well, I could've figured that out by myself... It's just styled-components raising a warning in the console.
Thanks for the feedback here!

That warning is saying that you're using two different versions of styled-components in your app, which will result in a larger bundle. So we can't ignore that.
I released v0.14.5 changing styled-components version on package.json to ^3.0.0, so it'll probably resolve to the version you're using in your app (if that's v3).


Enhance Layout/EmptyLineBetweenDefs to include macros

Resolves https://github.com/rubocop/rubocop/issues/11738
This pr enhances the Layout/EmptyLineBetweenDefs cop to treat macros in the EmptyLineBetweenMacros config as if they were defs.  See the issue for more detail

Before submitting the PR make sure the following are checked:

[X] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[X] Wrote good commit messages.
[X] Commit message starts with [Fix #issue-number] (if the related issue exists).
[X] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[X] Added tests.
[X] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[X] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

I've got 2 concerns about the PR:

the name of the configuration option, which might be a bit misleading to people as it looks like the boolean names of the existing options
whether or not this is outside the scope of the existing cop

In general I'm leaning towards "this is a good idea", but I'd like to hear what other people from @rubocop/rubocop-core think about the suggestion.

In general I'm leaning towards "this is a good idea", but I'd like to hear what other people from https://github.com/orgs/rubocop/teams/rubocop-core think about the suggestion.

Yeah, I think it's a better approach too.

After thinking about this a bit more I like naming the new option simply DefLikeMacros / DefinitionMacros / DefMacros. It implies we're adding some extra definitions and we already have a config option about empty lines between definitions, so I think that's all we need.
Sorry it took me so much to comment on this!

Thanks!


feat: Numeric/tel keyboard for ui.textbox on mobile devices #2170

The PR fulfills these requirements: (check all the apply)

[x] It's submitted to the main branch.
[x] When resolving a specific issue, it's referenced in the PR's title (e.g. feat: Add a button #xxx, where "xxx" is the issue number).
[x] When resolving a specific issue, the PR description includes Closes #xxx, where "xxx" is the issue number.
[x] If changes were made to ui folder, unit tests (make test) still pass.
[ ] New/updated tests are included

Adds an option to specify keyboard type to be shown on mobile devices. One of 'text' | 'number' | 'tel'. Updated API:
export interface Textbox {
  /** An identifying name for this component. */
  name: Id
  /** The text displayed above the field. */
  label?: S
  /** A string that provides a brief hint to the user as to what kind of information is expected in the field. It should be a word or short phrase that demonstrates the expected type of data, rather than an explanatory message. */
  placeholder?: S
  /** Text to be displayed inside the text box. */
  value?: S
  /** The masking string that defines the mask's behavior. A backslash will escape any character. Special format characters are: '9': [0-9] 'a': [a-zA-Z] '*': [a-zA-Z0-9].*/
  mask?: S
  /** Icon displayed in the far right end of the text field. */
  icon?: S
  /** Text to be displayed before the text box contents. */
  prefix?: S
  /** Text to be displayed after the text box contents. */
  suffix?: S
  /** Text to be displayed as an error below the text box. */
  error?: S
  /** True if the text box is a required field. */
  required?: B
  /** True if the text box is disabled. */
  disabled?: B
  /** True if the text box is a read-only field. */
  readonly?: B
  /** True if the text box should allow multi-line text entry. */
  multiline?: B
  /** True if the text box should hide text content. */
  password?: B
  /** True if the form should be submitted when the text value changes. */
  trigger?: B
  /** The height of the text box, e.g. '100px'. Percentage values not supported. Applicable only if `multiline` is true. */
  height?: S
  /** The width of the text box, e.g. '100px'. Defaults to '100%'. */
  width?: S
  /** True if the component should be visible. Defaults to True. */
  visible?: B
  /** An optional tooltip message displayed when a user clicks the help icon to the right of the component. */
  tooltip?: S
  /** True if the text may be checked for spelling errors. Defaults to True. */
  spellcheck?: B
  /** Keyboard to be shown on mobile devices. Defaults to 'text'. */
  type?: 'text' | 'number' | 'tel'
}

https://github.com/h2oai/wave/assets/23740173/ff57a6fe-8c9a-4f15-a109-451a39f4b064
Closes #2170

LGTM. @marek-mihok please resolve the conflicts so we can merge this in.


[question] Will this work with precompiled esnext to es3?

Will this work with code writen in latest JS, precompiled to ES3 and then converted to C using this tool?

The implementation of ES3 spec is not complete yet. Also e.g. eval is not planned to be supported. And finally, obviously things like DOM are completely outside of the scope. Otherwise, answer is yes.

I want to run the code on an IoT device, but write in JS.

Hey, yes, this is exactly why I am building this project. As I mentioned, it is still work in progress though, some ES3 features aren't supported yet, so this is not yet ready for production usage. Please check README.md & COVERAGE.md for details.


Homebrew Addition

Describe the feature
Same as a stale ticket #85
@cmendible, for the addition of brew I need one change, could you be able to make it?
I am adding the formula, but the build from the archive is failing due to missing files.
 ~  brew install --build-from-source /opt/homebrew/Library/Taps/homebrew/homebrew-core/Formula/a/azqr.rb
Error: Failed to load cask: /opt/homebrew/Library/Taps/homebrew/homebrew-core/Formula/a/azqr.rb
Cask 'azqr' is unreadable: wrong constant name #<Class:0x000000011f7b3ca0>
Warning: Treating /opt/homebrew/Library/Taps/homebrew/homebrew-core/Formula/a/azqr.rb as a formula.
==> Fetching azqr
==> Downloading https://github.com/Azure/azqr/archive/refs/tags/v.2.0.3.tar.gz
Already downloaded: /Users/seppe/Library/Caches/Homebrew/downloads/b93a090309ea4d262a1a20145e881b08b683f775ca5730fc26b1264a92e04a1c--azqr-v.2.0.3.tar.gz
==> go build -ldflags=-s -w -X ./cmd/main.go
Last 15 lines from /Users/seppe/Library/Logs/Homebrew/azqr/01.go:
2024-11-06 22:27:46 +0000

go
build
-trimpath
-o=/opt/homebrew/Cellar/azqr/2.0.3/bin/azqr
-ldflags=-s -w -X
./cmd/main.go

internal/aprl_scanner.go:24:12: pattern aprl/azure-resources/**/**/*.yaml: no matching files found

Is it possible to add the APRL resources from the git submodule to the actual build archive?  Or use an actual resolvable dependency?
This would fix the error's and then the formula can be build!
Kind regards!

Why are you rebuilding the binary?

Why are you rebuilding the binary?

Homebrew has two ways of installing software

formula: Homebrew package definition that builds from upstream sources
cask: Homebrew package definition that installs macOS native applications

Since azqr isn't bundled as native os x application it requires to rebuild!
If this is something we are unable to do we will not be able to add it to homebrew!
Greetings

I see. Have you tried the GitDownloadStrategy? Not sure if it downloads submodules

That works like a charm! Didn't notice it at first.
Here's the pull request that will ask the addition of the formula to the homebrew repository!
Azqr formula
I didn't look into automatic updates for the homebrew repository. I will do this tomorrow and keep you in the loop!
When it's approved I'll update the documentation of the azqr repo to include the homebrew info :)

@vanwinkelseppe the link to the formula is taking me to this issue 😊
Please make sure to build azqr passing the version as in:
https://github.com/Azure/azqr/blob/655239455eec8ac434b9ebc7a68af9c2b117499b/.github/workflows/build.yaml#L145
Otherwise running azqr -v will not give us helpful information.

https://github.com/Homebrew/homebrew-core/pull/197005
Yeah I noticed while writing my test 👍

It's approved!

@cmendible I've added a PR to add the instructions.
I'll look into the bumping of the homebrew version in a few days when I have some more time! If you update it I'll push a manual change in the meantime!


Upgrade helm to 3.11.1

upgrade helm to 3.11.3 to fix https://github.com/helm/helm/security/advisories/GHSA-pwcw-6f5g-gxf8

/cc @zhiweiyin318 @qiujian16

/approve
/lgtm


fix(catch): fixed overload order for catch

Description:
This is a really strange issue that I've been fighting with today.   When returning an Observable<T> to mergeMap I was having the resulting value come out as Observable<any> and I couldn't figure out why.  If I returned a Promise<T> or returned T[] everything was working correctly.
I used git bisect to determine that the issue originated with e55c62df9.  After playing with the commit a little bit I able to reduce the problem down to.
What the full problem comes down to is using TypeScript 2.0+ and rxjs beta11.  With TS1.8 this is not a problem.  The test added in this case only fails in TypeScript 2.0.
export interface CatchSignature<T> {
  (selector: (err: any, caught: Observable<T>) => ObservableInput<T>): Observable<T>;
  <R>(selector: (err: any, caught: Observable<T>) => ObservableInput<R>): Observable<R>;
}

Changing it to the following, solved the problem.
export interface CatchSignature<T> {
  <R>(selector: (err: any, caught: Observable<T>) => ObservableInput<R>): Observable<R>;
  (selector: (err: any, caught: Observable<T>) => ObservableInput<T>): Observable<T>;
}

This is a huge issue for anyone that's currently using TS2.0 with the current RxJS code base, it caused a bunch of my code to suddenly break for no reason.  Would be great if we could another release for this one. :smiling_imp:

Huh, really interesting (and apologies for causing inconvieience). Let me take a look deeper once I get back.
Quick confirmation - so this change's only for 2.0 user and doesn't affect 1.8 users, is my understanding correct?

Yeah its just 2.0 users at the moment.
I'm doing some further testing to make sure it's just the one line.
It seems like the problem is with the resolution of the observable catch
method vs the promise catch method.
The minimal repro may not be all cases as I'm continuing to work with the
changes.
On Sat, Aug 13, 2016 at 4:52 PM OJ Kwon<EMAIL_ADDRESS>wrote:

Huh, really interesting (and apologies for causing inconvieience). Let me
take a look deeper once I get back.
Quick confirmation - so this change's only for 2.0 user and doesn't affect
1.8 users, is my understanding correct?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ReactiveX/rxjs/pull/1880#issuecomment-239640994, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABNdpWE3Gdh_B1Lw6GubvR6Zhe6x9rY-ks5qfi6egaJpZM4Jjwdq
.

--
Thanks,
David

Change itself looks harmless, but it'd be great if it's possible to know what causes original code causes issue.

@kwonoj It is necessary to order overloaded function declaration signatures from greatest to least specificity. See this section of TypeScript Handbook:
https://github.com/Microsoft/TypeScript-Handbook/blob/release-2.0/pages/declaration files/Do's and Don'ts.md#ordering

@aluanhaddad Cool, thanks. Didn't aware of those.
But in this case signature difference is generic <R> for return value, is this considered as general overload as well?

@kwonoj my understanding is that the return type of the function does not take part in overload resolution however, in this instance, <R> is used in the signature of one of the arguments which does make it more specific.

Actually I believe the non generic overload can be removed entirely because R does not have to be different from T.

R does not have to be different from T.

: purpose of <R> is actually to support different return than original <T>, where original observable errors then selector returns other type of observable. Am I may misunderstanding your comment that single signature can support variant of different return type?

R can be inferred to be T if the resulting method returns Observable<T>.
I should be able to make that change shortly... and I think the test is too confusing so I'll drop it unless we have a good place to put it.

I think the test is too confusing so I'll drop it unless we have a good place to put it.

: agreed.

Updated

nitpicking - maybe commit message need to be updated?
otherwise LGTM to me.

not a nitpick, valid comment. :smile:
Was trying to slip it in while working at the same time.

Coverage remained the same at 97.084% when pulling dd0e58602e860273abd41bf7556da4eff076f386 on david-driscoll:fix-catch into a2b2f3dc157b1c81e1a23bb3b286d93cb235872c on ReactiveX:master.

commit updated (and the title too)

LGTM

Coverage remained the same at 97.084% when pulling dd0e58602e860273abd41bf7556da4eff076f386 on david-driscoll:fix-catch into a2b2f3dc157b1c81e1a23bb3b286d93cb235872c on ReactiveX:master.

@kwonoj sorry for any confusion, I meant that the overload without R is unnecessary

@aluanhaddad no worries, I could clarify after seeing @david-driscoll 's update. Appreciate for suggestion / guides, it was great help! :+1:

Thanks. I'm glad I could help.


Test mapping of real to double in MemSQL

Apparently MemSQL does not have real/float data type.

See also TODO in the code (being added in https://github.com/prestosql/presto/pull/5455)


How can I access the value of selected date from console?

Hi,
Great directive first of all. Newbie question: how can I console.log the value of selected date in a very simple way?
plunker https://plnkr.co/edit/n8HlCN?p=preview

Hi @heenaI, try updating your example like this:
<input class="form-control"
       ng-model="ctrl.input"
       ng-model-options="{ updateOn: 'blur' }"
       placeholder="Select a date..."
       id='date'
       moment-picker="ctrl.input"
       change="onchange(newValue, oldValue)">

ctrl.onchange = function (newValue, oldValue) {
   console.log(newValue, oldValue);
};


Does this no longer work?

OnScreenKeyboard.IsOpened() always returns false. OnScreenKeyboard.Show will hide the keyboard if it is on screen. Using WPF.

Ok, I'll check it, when my sister returns me tablet with sensor screen
10 Фев 2018 г. 1:01 пользователь "JohnnyPhoton"<EMAIL_ADDRESS>написал:

OnScreenKeyboard.IsOpened() always returns false. OnScreenKeyboard.Show
will hide the keyboard if it is on screen. Using WPF.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/AlexeiScherbakov/osklib/issues/2, or mute the thread
https://github.com/notifications/unsubscribe-auth/AIQ7O3aWq0SFLZ0jUCIoEG_S-zURSdTVks5tTMAzgaJpZM4SAl4p
.

Thanks. I suspect there is a bug in the latest windows version of the OSK as it doesn't work like it used to.

@JohnnyPhoton , please check new version. If everything is fine - I submit it to NuGet.
Also you can check Osklib.Wpf project for activating Osk for TextBox'es, PasswordBox'es and RichTextBox'es

Hi @AlexeiScherbakov, in the source code IsOpened is hardcoded to return false. I guess there's no way to tell if the keyboard is currently open then?

Ops, I forgot about this stub :-D
Check

I got busy with other stuff and just got back to this. Seems to be working well, thanks. Sometimes my surface pro just doesn't seem to want to use the OSK unless I disconnect all keyboards but that is the situation I wanted this for. My desktop system has no such issues.
Thanks again!

I have detected that in some cases ITipInvocation COM/WinRT object calls
Toggle without error but no keyboard is showed
After I toggle it manually it begin works as expected for a long time.
Because this thing is not documented feature - I don't know where is a
problem.
I think that if sensor keyboard is not used after computer reboot it need
some additional step to activate in application.
Also you can check updated version :-)
23 Июн 2018 г. 21:28 пользователь "JohnnyPhoton"<EMAIL_ADDRESS>написал:
I got busy with other stuff and just got back to this. Seems to be working
well, thanks. Sometimes my surface pro just doesn't seem to want to use the
OSK unless I disconnect all keyboards but that is the situation I wanted
this for. My desktop system has no such issues.
Thanks again!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/AlexeiScherbakov/osklib/issues/2#issuecomment-399699162,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIQ7O-Aec3YJJUic1l3N0Nwi6ritgCseks5t_ojCgaJpZM4SAl4p
.

Much better now. Seems consistent. Thanks! NuGet is not updated though.


Why should the display name match the technical name of the policy?

I am referring to rule apigee-xml:PolicyDisplayNameCheck. It generates messages like `It is recommended that the policy name attribute (AM-DummyResponse) match the display name of the policy (Creates "OK" Response Text).
Would you consider to drop this rule? Based on the Apigee Naming Conventions, the Display Name should actually tell a human what this policy is all about.
See: https://docs.apigee.com/api-platform/fundamentals/best-practices-api-proxy-design-and-development#developmentstandards-namingconventions
"DisplayName should accurately describe the policy’s function to someone who has never worked with that API proxy before."
Requesting to have the display name to be the same as the technical name (which in turn has to be the same as the file name), is violating that Apigee convention in my point of view...
Btw, same issue exists in the "apigeelint" tool, which seems to have been the origin idea for this SonarQube plugin...

Just as a reference - I raised the same request on the apigeelint tool:

Hi @karsten-wagner
You're right with this question... and I don't know the exact reason for this rule.
Just be aware that this Sonar plugin is initially based on all rules of the apigeelint with the same ID, plus some rules useful for my company (IDs upper than 500). This is why you find the same rule PO008 with no clear explaination.
Before considering to droping this rule, I suggest to wait for an answer to apigee/apigeelint#154 coming from people near Apigee team. They should provide a clear advice.
Fortunately, in using this Sonar plugin, you are free to disable any rule (so this one) by creating your custom SonarWay profile.

Thank you, @ntiss - deactivating the rule is the way we currently go. I am looking forward to a response from the Apigee team as well...