Hash Pin docker images

Also related to https://github.com/tensorflow/tensorflow/pull/62471, would you consider hash pin the docker images?
The security benefit of doing so is that it mitigates the risk of typosquatting attacks since the images are public. If there is a need for them to be updated regularly, I can also submit a .github/dependabot file to update the docker images regularly (weekly or monthly for example).
Besides, AFAIUC, the dockerfiles are used for build and tests, which lead to another benefit of hash pinning: reliability and stability.
Let me know your thoughts about i.
Thanks!

Pinning is a pain when working on these containers. I'm fine with the change as long as you update this PR to alleviate the trouble for developers:

Add a dependabot job to keep the shas updated, and add a sha if there is not one
Add a comment on each affected FROM line that links to the job definition and explains that a sha will be added automatically post-submission

Hi, I can add the dependabot config file to automatically update the digests on the dockerfiles (which is in fact a security practice too), although dependabot has no feature yet to automatically add hash when there is not one.
The renovatebot, although being a third party tool (not GitHub owned), it has an option to pin digests automatically to the given ecosystem (docker images). It would need to be installed on the repo since it is a github app.
Would you be interested on the renovatebot instead (I can submit a config file for it) or the dependabot only updating the hashes and versions periodically would be enough to alleviate the trouble for developers?

Hi @angerson Any update on this PR? Please. Thank you!

Hi @angerson Any update on this PR? Please. Thank you!

I've suggested the configuration file for dependabot to show how it would like to update both the actions and the dockerfiles. Dependabot will automatically update the hashes and comments, but it is not able to automatically add a sha when there is none.

Hi @angerson Can you please review this PR ? Thank you!

Hi @joycebrum Can you please resolve conflicts? Thank you!

Done!

Hi @angerson Can you please review this PR ? Thank you!

Hi @MichaelHudgins Can you please review this PR ? Thank you!

Hi @MichaelHudgins Can you please review this PR ? Thank you!

Hi @MichaelHudgins Can you please review this PR ? Thank you!


Add python 3.12 syntax support

Transcrypt is great but not regularly updated... It would be great to support 3.12 syntax.

There are a number of Python syntax features since 3.7 not yet implemented. Is there a specific feature of 3.12 you need? Or is it just 3.12 compatibility in general (IOW the ability of Transcrypt to properly run with Python 3.12)?


Second batch of GPU

Adds support for cauchy distribution, cbrt, trunc, and round to both CUDA and SYCL

Changes have been cherry picked onto: https://github.com/boostorg/math/pull/1162


unauthorized! method not present in cancancan

I have ability class as follows:
class Ability
include CanCan::Ability
def initialize(role)
@role = role
if @role == "guest_user"
can :read, :all
end
if @role == "business_member"
can :update, Business
end
if @role == "payment_member"
can :update, payment
end
if @role == "admin"
can :manage, :all
end
end
end
And in haml it is
-if can? :update, Business
= link_to 'Edit this Business'
Now this is working properly and hiding the link.
But if I try to hit the URL with ../edit then it opens the page.
I want to restrict the functionality.
i tried using unauthorized! but it says we are not allowed to use it any more.
Any ideas as how can I restrict user to access the edit link (if he tries to hit it manually in absence of edit button from the address bar) if he is not authorized to?

You must use load_and_authorize_resource checks in your controller to enforce your Ability file permissions in the controller. can? is just a view helper.
https://github.com/CanCanCommunity/cancancan/wiki/Authorizing-controller-actions


[JavaScript] Overcomplicated function evaluateConditions

Function evaluateConditions in the PoorCode.html file has an overcomplicated implementation. Please re-write the method so that it's shorter and more readable.
https://github.com/SergeyOvchinnik/open-class/blob/main/web/PoorCode.html#L28

Issue claimed - ake6


Update Readme

Can we update the readme to explain how exactly to use this ?

Updated the readme with instructions. Close the issue if it looks ok.


Android solution get texture id

How can i get texture id on funtion , i want to custom effect
public void renderResult(FaceMeshResult result, ResultGlBoundary boundary)

Hi @zhoujingheng, Could you please elaborate your query with more details. What do you mean by texture id? TextureFrame is an interface here. Are you trying to access TextureFrame

yes, i want to get texture and do more effect

Each solution result object has an acquireInputTextureFrame() method and the TextureFrame object has a getTextureName() method. You can obtain the underlying texture id by doing solutionResult.acquireInputTextureFrame().getTextureName(). Note that since you plan to do more advanced customization with the underlying texture directly, you need to interact with the solution result object in the ResultListener and probably can't use the provided MediaPipe GlRender.

Each solution result object has an acquireInputTextureFrame() method and the TextureFrame object has a getTextureName() method. You can obtain the underlying texture id by doing solutionResult.acquireInputTextureFrame().getTextureName(). Note that since you plan to do more advanced customization with the underlying texture directly, you need to interact with the solution result object in the ResultListener and probably can't use the provided MediaPipe SolutionGlSurfaceViewRenderer.


Display context sources in chat window?

It would be really nice to also display the RAG retrieved context sources after each LLM answer

Hey Nicholas!
That is definitely something that is in the pipeline! I'll create a branch and assign this to myself, I'll have an update for you this weekend.

That’d be awesome!


grpc_extra_deps disallows to define a version of go toolchain

What version of gRPC and what language are you using?
gRPC version : 1.49.1
Go version : 1.18
What operating system (Linux, Windows,...) and version?
Ubuntu 22.04
What runtime / compiler are you using (e.g. python version or version of gcc)
Go version : 1.18
Bazel : 5.3.0
What did you do?
Consider following WORKSPACE file :
workspace(name = "test")

load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")

http_archive(
    name = "io_bazel_rules_go",
    sha256 = "099a9fb96a376ccbbb7d291ed4ecbdfd42f6bc822ab77ae6f1b5cb9e914e94fa",
    urls = [
        "https://mirror.bazel.build/github.com/bazelbuild/rules_go/releases/download/v0.35.0/rules_go-v0.35.0.zip",
        "https://github.com/bazelbuild/rules_go/releases/download/v0.35.0/rules_go-v0.35.0.zip",
    ],
)

load("@io_bazel_rules_go//go:deps.bzl", "go_register_toolchains", "go_rules_dependencies", "go_download_sdk")

go_download_sdk(
    name = "go_sdk",
    version = "1.18",
)

go_rules_dependencies()

go_register_toolchains()

http_archive(
    name = "bazel_gazelle",
    sha256 = "5982e5463f171da99e3bdaeff8c0f48283a7a5f396ec5282910b9e8a49c0dd7e",
    urls = [
        "https://mirror.bazel.build/github.com/bazelbuild/bazel-gazelle/releases/download/v0.25.0/bazel-gazelle-v0.25.0.tar.gz",
        "https://github.com/bazelbuild/bazel-gazelle/releases/download/v0.25.0/bazel-gazelle-v0.25.0.tar.gz",
    ],
)

load("@bazel_gazelle//:deps.bzl", "gazelle_dependencies")
load("//:deps.bzl", "go_dependencies")

# gazelle:repository_macro deps.bzl%go_dependencies
go_dependencies()

gazelle_dependencies()

http_archive(
    name = "com_github_grpc_grpc",
    sha256 = "",
    strip_prefix = "grpc-1.49.1",
    urls = [
        "https://github.com/grpc/grpc/archive/v1.49.1.zip",
    ],
)

load("@com_github_grpc_grpc//bazel:grpc_deps.bzl", "grpc_deps")

grpc_deps()

load("@com_github_grpc_grpc//bazel:grpc_extra_deps.bzl", "grpc_extra_deps")

grpc_extra_deps()

I want to define my own version of the go toolchains and use gazelle to generate bazel build files for my go code.
What did you expect to see?
bazel build //:gazelle
DEBUG:
INFO: Analyzed target //:gazelle (90 packages loaded, 10076 targets configured).
INFO: Found 1 target...
Target //:gazelle up-to-date:
  bazel-bin/gazelle-runner.bash
  bazel-bin/gazelle
INFO: Elapsed time: 18.606s, Critical Path: 9.76s
INFO: 43 processes: 2 internal, 41 linux-sandbox.
INFO: Build completed successfully, 43 total actions

What did you see instead?
bazel build //:gazelle
Starting local Bazel server and connecting to it...
ERROR: Traceback (most recent call last):
	File "/home/lucas/projects/grpc-deps-minimal-demo/WORKSPACE", line 58, column 16, in <toplevel>
		grpc_extra_deps()
	File "/home/lucas/.cache/bazel/_bazel_lucas/03e5ee3de23111152f8b4bc57e72dd15/external/com_github_grpc_grpc/bazel/grpc_extra_deps.bzl", line 56, column 27, in grpc_extra_deps
		go_register_toolchains(version = "1.18")
	File "/home/lucas/.cache/bazel/_bazel_lucas/03e5ee3de23111152f8b4bc57e72dd15/external/io_bazel_rules_go/go/private/sdk.bzl", line 409, column 13, in go_register_toolchains
		fail("go_register_toolchains: version set after go sdk rule declared ({})".format(", ".join([r["name"] for r in sdk_rules])))
Error in fail: go_register_toolchains: version set after go sdk rule declared (go_sdk)
ERROR: error loading package 'external': Package 'external' contains errors
INFO: Elapsed time: 1.489s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (0 packages loaded)

This issue is a slightly simplified version of #30965

Richard, would you take a look at this?

I am also curious what is the best practices here when meet such a conflicts (use go_register_toolchains multiple times). https://github.com/bazelbuild/rules_go/issues/2761 mentioned a workaround that use go_download_sdk and unset version in go_register_toolchains. However, that still requires remove the version of go_register_toolchains in grpc/bazel/grpc_extra_deps.bzl.
For now, I simply create a patch file ignore_version_in_go_register_toolchains.patch:
diff --git a/bazel/grpc_extra_deps.bzl b/bazel/grpc_extra_deps.bzl
index 4d8afa3131..514189f9a5 100644
--- a/bazel/grpc_extra_deps.bzl
+++ b/bazel/grpc_extra_deps.bzl
@@ -53,7 +53,7 @@ def grpc_extra_deps(ignore_version_differences = False):
     api_dependencies()

     go_rules_dependencies()
-    go_register_toolchains(version = "1.18")
+    go_register_toolchains()
     gazelle_dependencies()

     # Pull-in the go 3rd party dependencies for protoc_gen_validate, which is

Then I patch it to com_github_grpc_grpc deps in WORKSPACE file:
http_archive(
  name = "com_github_grpc_grpc",
  patch_args = ["-p1"],
  patches = ["//tools:ignore_version_in_go_register_toolchains.patch"],
  sha256 = "76900ab068da86378395a8e125b5cc43dfae671e09ff6462ddfef18676e2165a",
  strip_prefix = "grpc-1.50.0",
  urls = ["https://github.com/grpc/grpc/archive/v1.50.0.tar.gz"],
)

This works as a workaround, but not sure if it is just a hacky way. Probably a better behavior is inside grpc_extra_deps if it detects the go_sdk version is set, just call the go_register_tools() instead of go_register_tools(version = "1.8").

We met the same issue in gVisor. Right now, we worked around it with this patch https://github.com/google/gvisor/blob/master/tools/grpc_extra_deps.patch.
Cc: @lidizheng

I can confirm that the patch approach worked for us.


Typescript doesn't recognize the shorthands set in the tamagui.config

Current Behavior
I configured tamagui in a project that was using native-base before, and the shorthands from @tamagui/shorthands, were added to the config following the documentation and the expo-next-template from tamagui create. The shorthands work as expected but typescript in my project cannot detect them and now I have ts error everywhere in my code :/

I also tried to use the recommendation from @aawalton here https://github.com/tamagui/tamagui/issues/145#issuecomment-1368106211 but didn't work for me.
Expected Behavior
Typescript should recognize the shorthands as available props for the component.
Tamagui Version
1.23.0

Reproduction
Here is an example of the project I'm having issues with, you can check `screens/InitialScreen.tsx` I put there some example code.
https://github.com/joseortiz9/storange-template-tamagui-rn

System Info
System:
    OS: macOS 13.3.1
    CPU: (8) arm64 Apple M1
    Memory: 53.05 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.12.0 - ~/.nvm/versions/node/v18.12.0/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v18.12.0/bin/yarn
    npm: 8.19.2 - ~/.nvm/versions/node/v18.12.0/bin/npm
    Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
  Browsers:
    Chrome: 112.0.5615.137
    Firefox: 107.0.1
    Safari: 16.4
  npmPackages:
    expo: ^48.0.16 => 48.0.16
    react: 18.2.0 => 18.2.0
    @tamagui/animations-react-native: ^1.23.0 => 1.23.0
    @tamagui/babel-plugin: ^1.23.0 => 1.23.0
    @tamagui/config: ^1.23.0 => 1.23.0
    @tamagui/theme-base: ^1.23.0 => 1.23.0
    tamagui: ^1.23.0 => 1.23.0

It does recognize them, this means you have something set up wrong. Usually a mismatched package version or just a clean and install is necessary.

No same here. Followed installation and been through it twice now, all versions matching, code runs fine but shorthands throwing errors

@Seamus1989 It could be related to tsconfig misconfiguration, check how it looks in the monorepo template from tamagui.

@joseortiz9 I've tried all of this, any more specific ideas?

@Seamus1989 noup :( I solved my issue by migrating the project to the monorepo template


New version: Flow-Launcher.Flow-Launcher version 1.11.0

Pull request has been automatically created using 🛫 WinGet Releaser.
Microsoft Reviewers: Open in CodeFlow

Duplicate of #92600


Add PropertiesConfig integration test

Coverage decreased (-0.1%) to 88.61% when pulling a0a752979cb92abd12200fe8a2b440ebbf6ca2c4 on mprimi:properties-integration-test into f9c8a61e8c611bbf1b11f2b9ad92e442c876514c on Netflix:master.

@tgianos Small change ready for review

How did I manage to reduce coverage by adding a test??

Cause coveralls is weird with rounding errors it seems.

Coverage decreased (-0.1%) to 88.61% when pulling be209d85bb586dce314b2bfcd3de45436b6e9906 on mprimi:properties-integration-test into f9c8a61e8c611bbf1b11f2b9ad92e442c876514c on Netflix:master.

@tgianos moved the file, but kept everything else the same (as i couldn't get loading via profile to work).


Use of variables in internal ACL rules

Would it be possible to support the use of %c in the ACL rules used by the internal ACL module without sacrificing efficiency?
I'm implementing a scheme like the one found on Amazon IoT where each device subscribes to a bunch of device-specific topics – such as /devices/{clientId}/# – and publish to a subset thereof. Of course it is not desirable to put all these algorithmic rules in a database.
I've tried the new emqttd_auth_http plugin, and that works just fine. However,  variables in the internal ACL rules would be my first choice if supported.

@teifip, Yeah, the ACL supports '%c', '%u' variables. For example, the 'etc/acl.config' used by the internal ACL module:
{allow, all, subscribe, ["/devices/%c/#"]}.
{allow, all, subscribe, ["/devices/%u/#"]}.
{deny, all}.

@emqplus, wonderful! Thanks a lot for following up!


[BUG] Unclear description of --docker_build option

The help text for --docker_build currently says...
NOTE: When the --docker_build flag is used, all arguments with paths
      should be relative to the directory containing open-ce.

The command for starting a build as documented in README.md is:
./open-ce/open-ce/open-ce build env open-ce/envs/opence-env.yaml

To which of these three directory levels does "open-ce" in the help text refer?
In README.open_ce_build.txt, there are still two levels to choose from:
./open-ce/open-ce build env envs/tensorflow-env.yaml

open-ce  referred in the doc refers to the root open-ce folder which comes when we clone https://github.com/open-ce/open-ce and not the sub-directories of cloned open-ce repo.
We will precisely mention that in the doc.

This has been fixed in https://github.com/open-ce/open-ce/pull/296


Fix device clock sync bug

Description
Fix a bug where users were allowed to continue using Valora despite their device clocks being off. I first noticed this when debugging an issue with ODIS where pepper requests were failing due to outdated timestamps coming from the client. I suspect this may be having negative impacts on other services such as the Attestation service.
The package we were using react-native-clock-sync had a couple of issues filed for it and hadn't been updated in two years so I moved us to a better maintained package react-native-npt-client.
Other changes
Refreshed the design on the SetClock screen as the formatting looked broken.
Tested
Manually
Related issues

Fixes #285

Backwards compatibility
Yes

From what I remember, the main reason we need to enforce correct time was because of geth itself which can't sync properly when the clock is not right. But we are now using forno by default.

Other services may rely on the user's device having an accurate time. For example, ODIS was throwing errors if the user's time was off by more than 10 mins.

I guess it would be nice if we checked on app open if the clock thing was fixed and navigate home. It still gets fixed by restarting and this probably doesn't affect a lot of users, so it's fine not to do that too though.

You're right. If it's easy to make the UX a little better, might as well do it. Thanks for the suggestion!

Other services may rely on the user's device having an accurate time. For example, ODIS was throwing errors if the user's time was off by more than 10 mins.

Yes the point is this should be invisible to the user. We can measure the drift and provide the adjusted "real" time for services that need it.
The current solution to ask for user to adjust their clock and come back to the app is not great.

Yes the point is this should be invisible to the user. We can measure the drift and provide the adjusted "real" time for services that need it. The current solution to ask for user to adjust their clock and come back to the app is not great.

That's true and I agree. It's a bit complicated because some of the services (e.g., ODIS directory of the SDK) use Date.now() in their packages rather than asking for the timestamp or using an NTP service. If we find all the places where an accurate time is needed, then we can collaborate with the necessary parties to make this more friendly UX


[BUG] Hello World app gives javascript syntax error

Describe the bug
The hello world app from the quickstart gives this error:

Uncaught SyntaxError: export declarations may only appear at top level of a module fasthtml.js:1:1

No functionality I can tell is affected.
Minimal Reproducible Example
from fasthtml.common import *

app, rt = fast_app()

@rt("/")
def get():
    return Titled("FastHTML", P("Let's do this!"))

serve()

Environment Information
Please provide the following version information:

fastlite version: 0.0.11
fastcore version: 1.7.8
fasthtml version: 0.6.1

Hey @leifmetcalf,
I haven't been able to reproduce with the same versions on my Linux machine. Are you still having this problem with the latest version?

I can't reproduce it on fasthtml 0.8.0.


Autocomplete for NPM is outputting "garbage" when nvm plugin is installed

Originally opened as a fish-shell issue: https://github.com/fish-shell/fish-shell/issues/3152

After installing the nvm plugin, I get garbage printed out when trying to get auto-completions for npm.
Removing nvm plugin makes everything work fine.

Operating system: OS X El Capitan 10.11.5 (15F34)
Fish version: 2.3.0
Fish installed: using the official DMG.

Thanks.
Just wanted to let you know that if I install omf nvm, it works well.
Also, I tried installing only bass, following the advice from here https://github.com/creationix/nvm/issues/303#issuecomment-121086278
function nvm
    bass source ~/.nvm/nvm.sh ';' nvm $argv
end

was enough to make everything work without the whole nvm package.

You don't need this plugin at all, as you said just putting that on your config.fish is enough. What I don't like is if you do that slows your shell initiation by a couple of seconds, because it sources nvm everytime. That's why I created this plugin, to only source nvm when you use npm, or node or nvm

If I add this as a new file, nvm.fish in the functions directory, shouldn't it do the same - source nvm only when the command is actually called?

@nomaed Can you use a different plugin manager or do you have to use nvm?
Some people have to use nvm, so this exists, but as you can see setting it up requires knowledge and some work which is why fnm also exists.

@brj I want to use nvm. I need to test stuff on different node versions and it makes the job much easier than I would be otherwise.

So, I installed fnm (fisher install fnm), got the latest node.

I was able to repro the problem with npm completions.
It does seem to work okay with verman though. Would you mind trying out verman too and see if npm completions work okay? That would help me determine this is a problem with how fnm creates the npm shim.

With verman

I think the problem may be simply that fnm's npm shim is not inheriting npm completions. This should be doable adding --wraps=npm to the function definition, maybe.

I think it has to do with fish-shell npm completions https://github.com/fish-shell/fish-shell/blob/master/share/completions/npm.fish

@nomaed It seems after all that the problem was not with the plugin, but with the official completions from fish shell, you can read more about it here https://github.com/fish-shell/fish-shell/pull/3159
And the commit that fixes it https://github.com/fish-shell/fish-shell/commit/10661bb024cd87fdb5452b86fcc74a58f7f678f1 :
The next release of fish shell will have the completions fixed but until then you can fix them manually by doing this:
wget https://raw.githubusercontent.com/fish-shell/fish-shell/master/share/completions/npm.fish
and then do sudo mv npm.fish /usr/share/fish/completions/

That is great, thank you for following it up!


Add ufunc promoter for equal

This adds a promoter implementation for the equal ufunc. This makes it so that if you pass a fixed-width unicode string dtype and a StringDType array to np.equal, numpy will automatically cast the Unicode to StringDType.
@seberg is there a way to do this without adding the promoter twice? If not, would it make sense for PyUFunc_AddPromoter to add two promoters, one with the input arguments switched? I tried only doing it once and the promoter only kicked in for when StringDType was the first parameter, so I think the order does matter currently.
default_ufunc_promoter is copy/pasted from numpy. Should I be doing something a little more precise?

If not, would it make sense for PyUFunc_AddPromoter to add two promoters, one with the input arguments switched?

I guess this would only work for ufuncs where the order of the inputs don't matter, so PyUFunc_AddPromoter can't always just do it.

I guess this would only work for ufuncs where the order of the inputs don't matter, so PyUFunc_AddPromoter can't always just do it.

Exactly, multiple-dispatching is complicated :/.  There could be a point in signalling "I don't care about order", but...  In the end for anything but simple binary cases like this one, the only good solution right now I have is the abstract dtype.
(Which is also tricky, cause you can't say "one of them must be mystring", so your promoter has to do the right thing for NumPy strings also in principle...)


feat(tui): edit entry

Codecov Report

Merging #32 (a2221b6) into master (06da6eb) will increase coverage by 0.08%.
The diff coverage is 45.07%.

@@            Coverage Diff             @@
##           master      #32      +/-   ##
==========================================
+ Coverage   74.34%   74.43%   +0.08%
==========================================
  Files          59       62       +3
  Lines        4413     4439      +26
==========================================
+ Hits         3281     3304      +23
- Misses       1132     1135       +3

Impacted Files
Coverage Δ

quake_tui/src/lib.rs
4.54% <ø> (ø)

quake_tui/src/widgets.rs
2.40% <8.33%> (+1.14%)
:arrow_up:

quake_tui/src/app.rs
76.35% <20.00%> (+3.24%)
:arrow_up:

quake_tui/src/entry_action.rs
59.18% <59.18%> (ø)

quake_core/src/markdown/references.rs
84.21% <0.00%> (-15.06%)
:arrow_down:

quake_core/src/markdown/md_processor.rs
69.58% <0.00%> (-1.22%)
:arrow_down:

src/pagedump.rs
100.00% <0.00%> (ø)

src/usecases/pagelink_usecases.rs
100.00% <0.00%> (ø)

quake_core/src/markdown/entry_reference.rs
98.75% <0.00%> (ø)

quake_wasm/src/lib.rs
71.92% <0.00%> (+2.69%)
:arrow_up:

... and 1 more

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 06da6eb...a2221b6. Read the comment docs.


provide build-in module version

Currently, we can us some build-in nginx modules in  OS pacakges  and docker images  . but don't known which nginx module it use
maybe provide some module version  docs for better to  write  nginx directives (diffrent nginx  module maybe provide diffrent directives )

@rongfengliang please see here: https://angie.software/en/install/#install-dynamicmodules - for links to all the modules we provide in packages with Angie

@VBart Thanks, I have see this links . maybe provide some information  version information about  thirdpart modules maybe better

Hello @rongfengliang ,
Thanks for the good idea.
We are going to think about best approach of adding an original module version into each package.

Hello @rongfengliang ,
We have added the README file into each module package which contains information about its sources.
The below is the example location of that file within brotli module package:
/usr/share/doc/angie-module-brotli/README


FIXES: SwipeListExample: Unable to resolve module SwipeListView - could not be found #554

FIXES: SwipeListExample: Unable to resolve module SwipeListView - could not be found #554

Hey @chriswayg this is actually by design. If you're developing on this you can run yarn run dev to copy the components into the local `examples folder


CSS file not included anymore when switching _app.js to _app.mdx

I have the following code in pages/_app.mdx
// These styles apply to every route in the application
import '../styles/globals.css'

export default function App({ Component, pageProps }) {
  return <Component {...pageProps} />
}

the following in styles/globals.css:
@tailwind base;
@tailwind components;
@tailwind utilities;

and this in pages/index.mdx:

Hello

Doing next dev, the text "Hello" is not red. When I rename pages/_app.mdx to pages/_app.js, it works correctly.
What am I doing wrong? Thanks.
You can find the full repo there: https://github.com/leruaa/stapifaction-website

seems https://github.com/leruaa/stapifaction-website/blob/62bdedd56f18e6eadb4dd4f4a902cf8538ae2198/pages/_app.mdx#L1 is illegal comment in mdx files (use {/* some-comment */} syntax), also _app.mdx will be removed in v3

Oh thanks I'll try.
By what will it be replaced?

It's working now, thanks!

@archform-eng-wjsong just remove the comment in _app.mdx

i clone your repo, and remove _app.mdx, text "Hello" is not red, it not works. @leruaa


CLAP: add macro to use MIDI MPE dialect

This is related to #441
In the end I could not help but try a little something. At first I wanted to let people select any of the different dialects, but I was not sure how to properly retrieve the definitions in DPF (include the corresponding CLAP header or duplicate its #define somewhere? Neither seemed pretty). So I settled with just the "MPE" option for now, especially considering that the other dialects (MDI 2 or CLAP) might need to be properly parsed to reach the plugin.
Then I started to add flags to let user configure MPE for input or output separately, to declare it as supported only (and not "preferred")... but that started to look bloated without other use cases.
Hence the trivial modification. I still hope that can be of some help. I tried my best to mimic how the flags are set. Tell me if I can improve something.

While I agree with the base idea, I think making this clap specific is wrong.
Best to me seems to have a generic hint (0/off by default if unset) to report a plugin as supporting MPE. Then DPF takes care that the host knows about this, which is already covered here for CLAP.
The value is only a hint anyway, so it is fine to be generic.

While I agree with the base idea, I think making this clap specific is wrong.
Best to me seems to have a generic hint (0/off by default if unset) to report a plugin as supporting MPE. Then DPF takes care that the host knows about this, which is already covered here for CLAP.
The value is only a hint anyway, so it is fine to be generic.

also please make the PR target develop branch, not main.
new commits should always go into develop first. thanks

actually I think the best is to have default value as "undefined", where we do nothing special if unset.
but plugins can manually specify through 0 or 1 value that they support MPE (or not)
most plugin specs dont have a way to report this property anyhow

Thanks for the feedback. I rebased on develop and used a generic name for the macro -- maybe there is a better name for that (DISTRHO_PLUGIN_USE_MIDI_MPE  ?), maybe you wanted no default value in DistrhoInfo.hpp.

sorry it took a while to get to this, I want to add a few little things on top but never had the time for it, so best to merge it as-is.
I just now need to handle it similar to the other flags
thanks!

No worries, thank you for getting back to that :) Now I definitely have to polish and publish the plugins I have been working on!

No worries, thank you for getting back to that :) Now I definitely have to polish and publish the plugins I have been working on!

yes! then please update https://github.com/DISTRHO/DPF/wiki/Plugins-made-with-DPF to mention those too

Sure will!


can tangram support openlayers?

can tangram support openlayers as leaflet?
thanks

No, Tangram-JS is technically a Leaflet plugin, and draws raster and vector data in a Leaflet layer, while OpenLayers provides both drawing and interaction functions. So I don't know of any way to use Tangram and OpenLayers together.
OpenLayers does support Mapzen's vector tiles – for more information check out our vector tiles product page: https://mapzen.com/projects/vector-tiles/
Here's an example of OpenLayers drawing Mapzen vector data: https://mapzen.github.io/openlayers-mapzen-vector-tile-example/
Example code: https://github.com/mapzen/openlayers-mapzen-vector-tile-example/


Wait for elements to be visible

The max wait time should probably be configurable...

Do we want to use this implicitly inside of the finders as well? Or should we always expect people to do explicit waiting? I'm fine with just saying that for now it needs to be explicit and then maybe adopting the implicit waiting later if it makes sense.

Chatted with Christian this morning... he made the case for waiting inside the normal finders as it reads more naturally and it separates knowledge of how the front-end works. I've been convinced but still wish waiting wasn't necessary

It would be fine with me to expose the waiting helper and just use it internally inside the finder as well. That way you can be more explicit if you choose.

Cool. How do you imagine :count works? My interpretation is 'find this exact number or fail'. all needs to raise an error to trigger the retry...so with a specific count, find count or raise an error. Without a count, should it find at least one or raise? As it's implemented now, all can return an empty list

I would imagine that in the case of all it just finds all the matches on the page currently. If you want to wait until you have a specific amount then you would use find('#some-selector, count: 3) or whatever. If it never finds that many then it throws the error. I don't think that all should find an error.  It definitely brings up the issue of consistency though. Is it semantically OK for all to just return you an empty list in that scenario?

you're thinking all doesn't have the wait_until behavior? there could be a separate any function that keeps checking until at least one node is found

Yeah I don't think we can wait for anything in all. Maybe any should be a matcher? So you would chain things like so:
session =
  |> visit("/some_page.html")

assert any?(session, '.users')

What do you think about something like that?


Add persistent link to the demo on README

And/or in the title/url section of the viv landing page on GH.

@ngehlenborg Do you want to put this behind an actual domain name? vitessce-image-viewer.com seems to be free.

Could also do a subdomain of vitessce.io like image-viewer.vitessce.io or viv.vitessce.io

We could also wait until it's integrated into vitessce.

I'd prefer to use a subdomain.

I can see it in Route 53 - I can probably set that up (assuming that I have the right privs).

I just want to be able to quickly get a link to the demo :100: :-D

Let's go for viv.vitessce.io.

done with that name @ngehlenborg


Expose AnalyzeResult Errors

Per internal Teams discussion, we'll throw RequestFailedException when errors come back in AnalyzeResult.Errors for Preview 1 and re-evaluate based on further information from the service team about errors and the documents that generate them, as well as customer feedback.

@ctstone , @bojunehsu , @maririos

When users analyzes a multi-page PDF, it is possible that only 1 page failed.  In such case, I believe the current behavior is to return the results for the remaining pages and add an error message for the page that failed.  If we throw, the user loses the ability to examine the rest of the processed results.  Since I believe we currently bill customers in this case, it would be even more frustrating not to be able to access any of the results.  @ctstone Can you please correct any of my misunderstanding?

FYI @kristapratico

@bojunehsu could we possibly get a sample form like you described that would generate a page-based error and return the successfully processed results? This would really help us design how to expose errors for the SDKs.

ErrorPdf.pdf
Untested, but this file should trigger the error conditions described above.  Specifically, the first page is okay, but the second page has dimension outside the supported range.  Even if it doesn't trigger errors today, we may modify the implementation to behave that way in the future.

For Preview 1, we will throw an exception when LRO.Status == failed, and if LRO.Status == succeeded, return AnalyzeResult equivalent with no errors on it.  Per discussions with the service team, we are not currently aware of any cases when the LRO.Status is succeeded and AnalyzeResult.Errors is populated with values.
Thanks to everyone who contributed to this investigation!  @kristapratico, @ctstone, @bojunehsu

Fixed by #11460.


Waiting for drone to connect...

I was trying to run some simple examples with gazebo.
I launch iris in gazebo  with px4 autopilot it works perfectly but when I run any example / my code following is seen:
Waiting for mavsdk_server to be ready...
Connected to mavsdk_server!
Waiting for drone to connect...
I wanted to use mavsdk for multi drone simulation but for some reason My connection is not being set up.
Help please!

I am not using QGC .
when I run SITL instance  directly
-- make px4_sitl_default gazebo_iris
everything works fine and I am able to control things..
what I want to do is to launch multiple bots .. when I do that with
roslaunch px4 multi_uav_mavros_sitl.launch
mavsdk server connects but Drones dont get connected.
For ex.
I launched multiple drones but tried to connect to udp 14540  with drone id 0 and mavsdk isnt able to find drone.
I am new at this so  maybe doing some trivial mistake.

When you run make px4_sitl_default gazebo_iris, it will broadcast mavlink messages to udp 14540 (that's the default for MAVSDK) and udp 14550 (that's the default for QGC).
Now when you run multiple drones with that ROS command, I don't know what it does. Did you read what multi_uav_mavros_sitl.launch does? Where is that file?

The file is located  /PX4-Autopilot/launch
here are the contents of the file

https://github.com/PX4/PX4-Autopilot/blob/8c4b900f9ac6aa48c60def3d1cda04ee22e59777/launch/multi_uav_mavros_sitl.launch#L1

Yeah I took a look at it but didn't think of a reason it should not work.
udp is clearly defined for each drone.
Launch file for your Reference :
https://github.com/PX4/PX4-Autopilot/blob/8c4b900f9ac6aa48c60def3d1cda04ee22e59777/launch/multi_uav_mavros_sitl.launch#L1

But do you run mavsdk to listen on 14560, 14561 and 14562? Isn't that where your launch file says that mavlink will be broadcasted?

drone = System()
await drone.connect(system_address="udp://:14560")

yes I am ,
for starters I just want to connect to one drone in the whole swarm. but when I run
Waiting for mavsdk_server to be ready...
Connected to mavsdk_server!
Waiting for drone to connect...
I am stuck here as drone is not being discovered.

The example that I am running is like this :
async def run():
drone = System()
await drone.connect(system_address="mavlink_udp_port://:14560")

print("Waiting for drone to connect...")
async for state in drone.core.connection_state():
    if state.is_connected:
        print(f"Drone discovered!")
        break

print("Waiting for drone to have a global position estimate...")
async for health in drone.telemetry.health():
    if health.is_global_position_ok:
        print("Global position estimate ok")
        break

print("-- Arming")
await drone.action.arm()

print("-- Taking off")
await drone.action.takeoff()

await asyncio.sleep(5)

print("-- Landing")
await drone.action.land()

if name == "main":
loop = asyncio.get_event_loop()
loop.run_until_complete(run())

You need to make sure that your drone (SITL or not) sends mavlink packets that reach MAVSDK. If it is your first time using MAVSDK, a quick way to try with a headless gazebo is documented here:
docker run --rm -it jonasvautherin/px4-gazebo-headless:1.11.0

And if the docker container does not run on the same host as mavsdk, you can specify the IP where mavsdk runs, for instance:
docker run --rm -it jonasvautherin/px4-gazebo-headless:1.11.0 <IP_ADDRESS>

If this works, then it means that you need to look into what your SITL does, and make sure it can reach mavsdk.

@JonasVautherin  Thanks for your help. Actually I found out the problems through one of your answer in #931
The PX4 launch files launch Mavros in the file itself and hence Mavsdk  is not able to connect to the ports.
For  Connecting multiple vehicles I did was this :

Run  multiple vehicles with no ROS  in Gazebo (follow this )
Launch mavsdk_severs :
cd  /Path_to_mavsdk/bin
./mavsdk_server -p 50040 udp://:14540
./mavsdk_server -p 50041 udp://:14541
./mavsdk_server -p 50042 udp://:14542

Everything works fine after that.


Cache range requests plugin injects range related headers when it should not

Currently the cache range requests header will blindly inject range related client headers into a response without checking whether or not the response is a 206. This can lead to range headers appearing in negative cases such as 4xx responses.

Closing this for now; after further testing locally, I believe I may have had an environmental/configuration issue that led to poor interaction between cache range requests and the slice plugin.


Footprint still misleading

The minified/gzipped version of angular-ui-bootstrap has sat at 28KB for a long time now. The 20KB claim at the top of this repo should be updated and/or removed.

Take care of.


Temporary fix to work around the LetsEncrypt CA expiry for pact broker

Temporary fix to work around the LetsEncrypt CA expiry for pact broker on cloud platform services.
This involves disabling SSL verification until the proper fix is in place.
Without this fix our pact tests can not progress due to certificate failure.

Trello card is here: https://trello.com/c/fG1V2pZr/82-re-enable-ssl-verification-for-pact-broker


Add Spark 2.2 to travis build

Adds Spark 2.2 to the travis build.

@jkbradley Tests pass with Spark 2.2 -- is there anything else I should check before we publish a new sklearn release (or RC?)

Thanks!  LGTM


x/build/cmd/coordinator: use maintner to start trybots, not polling gerrit API

Currently Trybots start by a goroutine loop in the coordinator (findTryWorkLoop) running a Gerrit query every 60 seconds:
func findTryWorkLoop() {
        if errTryDeps != nil {
                return
        }
        ticker := time.NewTicker(60 * time.Second)
        for {
                if err := findTryWork(); err != nil {
                        log.Printf("failed to find trybot work: %v", err)
                }
                <-ticker.C
        }
}

func findTryWork() error {
        query := "label:Run-TryBot=1 label:TryBot-Result=0 status:open"
...
        cis, err := gerritClient.QueryChanges(context.Background(), query, gerrit.QueryChangesOpt{
                Fields: []string{"CURRENT_REVISION", "CURRENT_COMMIT", "CURRENT_FILES"},
        })
...

This sucks for two reasons:

It runs every 60 minutes, wasting on average 30 seconds and at worst 60 seconds of our overall 5 minute goal for Trybots.
If a new CL is uploaded in the meantime, Gerrit removes +1 votes and the CL is treated as if it's no longer desired to be a trybot job. (see confusion in @shurcooL's https://golang.org/cl/46715).

We should fix both at the same time by watching maintner instead and using the live Gerrit data and knowing the history of the vote.
/cc @andybons @shurcooL

It runs every 60 minutes

60 seconds, yes?

Yes, 60 seconds

@SCKelemen

This is mostly done, but it turns out Gerrit doesn't have enough information in its NoteDb git structure for us to do our own vote counting reliably.
So the implementation of the MaintnerService.GoFindTryWork ends up using a mix of maintner & Gerrit API calls to get this data.
If we wanted to hard-code the Run-TryBot vote policy in maintner we could get rid of the API call altogether but I had got sidetracked trying to make label counting work in the generic case. The problem is that Gerrit has this option:
https://gerrit-review.googlesource.com/Documentation/config-labels.html#label_copyAllScoresOnTrivialRebase

label.Label-Name.copyAllScoresOnTrivialRebase
If true, all scores for the label are copied forward when a new patch set is uploaded that is a trivial rebase. A new patch set is considered as trivial rebase if the commit message is the same as in the previous patch set and if it has the same code delta as the previous patch set. This is the case if the change was rebased onto a different parent, or if the parent did not change at all.

But it doesn't record in NoteDb whether something's trivial and computing that by hand is not trivial. So when we're walking the NoteDb structure and counting votes, we don't know whether to reset something unless we have the same "trivial rebase" policy as Gerrit.


[MenuList] Ignore disableListWrap for text focus navigation

[x] I have followed (at least) the PR section of the contributing guide.

Addresses issues noted here.

Native select behavior wraps the navigation when doing text matching but not for arrow keys, so the text matching now ignores the disableListWrap property.

This makes an attempt to regression test focus-visible logic for MenuList, however it is difficult to do this robustly since the simulate function does not bubble events up the same way as dispatchEvent, so events never reach the document event listeners set up by focusVisible.js. I added a couple usages of dispatchEvent to cause changes to hadKeyboardEvent in focusVisible.js and verified that the focus visible class gets added or not appropriately after focus change.

To quickly summarize this for me: Do we wrap or not?
Because not wrapping is only a mac feature. Windows and linux wrap when navigating through items in a list. The WAI-ARIA authoring practices also recommend wrapping. Mac is the clear outlier here and we shouldn't match their behavior.

@eps1lon 👍, there is a precedent for ignoring Mac OS behavior:
https://github.com/mui-org/material-ui/blob/e36d33a0f3148a21065885a1d91b6fe800153a4c/packages/material-ui/src/Select/SelectInput.js#L156-L157

Do we wrap or not?

@eps1lon Before this change, if disableListWrap: true, text navigation would not wrap. For a select with "ten", "twenty", "thirty", typing "tttt" would stop at "thirty". After this change, text navigation always wraps regardless of the disableListWrap value, so "tttt" would wrap back around to "ten". The arrow key navigation is unchanged -- it always honors disableListWrap. Also unchanged, SelectInput sets disableListWrap to true.
Far as I can tell, this is the behavior for <select> elements in the browser on both Mac and Windows -- arrow keys do not wrap, but text matching does wrap.

Far as I can tell, this is the behavior for  elements in the browser on both Mac and Windows -- arrow keys do not wrap, but text matching does wrap.

That's not matching the WAI-ARIA recommendations: Open the listbox and press "f" repeatedly. It will stop at the last item and not wrap.

Maybe the question is if our Select is actually implementing the listbox pattern.

Open the listbox and press "f" repeatedly. It will stop at the last item and not wrap.

@eps1lon Where is this quote from. This doesn't seem to be in sync with the behavior here: https://www.w3.org/TR/wai-aria-practices/examples/listbox/listbox-collapsible.html. In their example arrow keys don't wrap, but text matching does.

That was github not properly formatting my comment. This was the behavior I observed. The issue was that wrapping is debounced. Press is semi-quickly and it won't work. You need to explicitly pause. Not sure if it is just laggy or intended.

Oh now I understand it. It buffers the input:

Type multiple characters in rapid succession: focus moves to the next item with a name that starts with the string of characters typed.

My implementation is modeled off of the browser select behavior which is slightly more sophisticated. They buffer in a similar way, but if the buffer only contains a single repeated character then it just matches against the first character. This, for example, allows for quickly getting to Minnesota in a select of states by repeatedly typing “m” without having to wait for the buffer reset. Once a non-repeating character is entered, the full buffer is honored for matching. My tests cover these conditions pretty thoroughly leveraging “aardvark” to test the transition from repeating to non-repeating mode.

I think the WAI-ARIA example works similarly but I find it pretty unintuitive since the buffer is invisible. Thanks for clearing this up.

The WAI-ARIA example seems to always honor the full buffer, so you can’t do fast repeated characters. Instead you have to wait for a buffer reset after each key in order for repeated characters to advance to the next one.


[SHIRO-691] Upgrade to maven-jar-plugin 3.1.1

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Shiro-pr/79/


Possible to change blue of selected date and gray of placeholder?

Hi React datepicker,
Is it possible to change the blue color of the selected date in the calendar? In addition, I would like to change the shade of gray for the placeholder text. I did not see the examples doing it, so was just wondering if it was possible. Thanks!
Sincerely,
Laura

Yes, you can change it in css file, which is included.

hi, thanks for the libray, i'm trying to change color of selected day, i notice the react-datepicker.css under /dist, and also sass files. i tried to copy the datepicker's stylesheet and add some changes, then i tried to import it in my code, but it's not working.
whats the process for changing the color of selected day? @flaurida @alex-shamshurin

@lejoss Without knowing exactly what you did, it could be any number of things... It sounds like you're on the right track though. If you're including both the default style and your custom style, you may need to check on ordering or specificity. https://developer.mozilla.org/en-US/docs/Web/CSS/Specificity
If you need help learning CSS, there are plenty of resources throughout the web.


touchosc: <IP_ADDRESS> -> <IP_ADDRESS>

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for touchosc is: Next generation modular control surface
meta.homepage for touchosc is: https://hexler.net/touchosc
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found <IP_ADDRESS> with grep in /nix/store/vh2mrnpxmx5rll5q4sj7jch6ahws8n6d-touchosc-<IP_ADDRESS>
found <IP_ADDRESS> in filename of file in /nix/store/vh2mrnpxmx5rll5q4sj7jch6ahws8n6d-touchosc-<IP_ADDRESS>

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
touchosc

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/vh2mrnpxmx5rll5q4sj7jch6ahws8n6d-touchosc-<IP_ADDRESS> \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A touchosc https://github.com/r-ryantm/nixpkgs/archive/2d2e120103cf4c4410c87534cfe26e5b3cde866b.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/2d2e120103cf4c4410c87534cfe26e5b3cde866b#touchosc

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/vh2mrnpxmx5rll5q4sj7jch6ahws8n6d-touchosc-<IP_ADDRESS>
ls -la /nix/store/vh2mrnpxmx5rll5q4sj7jch6ahws8n6d-touchosc-<IP_ADDRESS>/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

touchosc

Maintainer pings
cc @lilyinstarlight for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for touchosc is: Next generation modular control surface
meta.homepage for touchosc is: https://hexler.net/touchosc
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found <IP_ADDRESS> with grep in /nix/store/r3jw67bgsp8n7ybw4kwjsn9frgyqzvyk-touchosc-<IP_ADDRESS>
found <IP_ADDRESS> in filename of file in /nix/store/r3jw67bgsp8n7ybw4kwjsn9frgyqzvyk-touchosc-<IP_ADDRESS>

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
touchosc

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/r3jw67bgsp8n7ybw4kwjsn9frgyqzvyk-touchosc-<IP_ADDRESS> \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A touchosc https://github.com/r-ryantm/nixpkgs/archive/910af54b6c7824377074bba956a550ed6762f105.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/910af54b6c7824377074bba956a550ed6762f105#touchosc

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/r3jw67bgsp8n7ybw4kwjsn9frgyqzvyk-touchosc-<IP_ADDRESS>
ls -la /nix/store/r3jw67bgsp8n7ybw4kwjsn9frgyqzvyk-touchosc-<IP_ADDRESS>/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

touchosc

Maintainer pings
cc @lilyinstarlight for testing.


Update development.md

Just adding some clarifying language and screenshots, mostly in reference to things I remember I didn't do right the first time.

Would love a +1 from @probot/maintainers ☺


forking for other markets/countries

great work on this, love the simplicity and overview, I have understood mostly how it works - the only thing leaving me baffled is the map generation.
so instead of just assuming things, i thought i would ask - to adapt this for another market (thinking of Kenya/Somali/Ethiopia etc. What is required? happy to do the work, would be glad for topline advice.

@shaksi Please do join the dev group in Telegram to discuss more regarding this :)
Another effort here : https://github.com/covid19india/covid19india-react/issues/590

where is the dev group telegram? i have only been able to find the Ops group.

@shaksi apologies about the late response, here you go https://t.me/joinchat/Mb0ZhVRvI-VZyGuE8uvMbA :)


Refactor the qf_parse_match() and qf_list() functions in quickfix.c

The qf_parse_match() and qf_list() functions are too long.
Refactor and simplify the functions. No new functionality
is introduced in this patch.

Codecov Report

Merging #2950 into master will increase coverage by 0.01%.
The diff coverage is 87.91%.

@@            Coverage Diff             @@
##           master    #2950      +/-   ##
==========================================
+ Coverage   75.74%   75.75%   +0.01%
==========================================
  Files          92       92
  Lines      135080   135111      +31
==========================================
+ Hits       102315   102356      +41
+ Misses      32765    32755      -10

Impacted Files
Coverage Δ

src/quickfix.c
93.27% <87.91%> (+0.03%)
:arrow_up:

src/if_xcmdsrv.c
84.17% <0%> (-0.36%)
:arrow_down:

src/gui_gtk_x11.c
47.98% <0%> (-0.05%)
:arrow_down:

src/window.c
82.17% <0%> (-0.04%)
:arrow_down:

src/syntax.c
78.38% <0%> (+0.02%)
:arrow_up:

src/eval.c
81.55% <0%> (+0.04%)
:arrow_up:

src/gui.c
49.4% <0%> (+0.05%)
:arrow_up:

src/term.c
59.79% <0%> (+0.05%)
:arrow_up:

src/channel.c
83.07% <0%> (+0.07%)
:arrow_up:

src/ex_cmds.c
79.46% <0%> (+0.08%)
:arrow_up:

... and 2 more

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 833093b...67faba1. Read the comment docs.


Use of unresolved identifier 'CBC' - build fails

Commit https://github.com/BANKEX/web3swift/commit/8bbde2ea49d02cf98ae16c5717089f8b6bac8851 leads to build failure:
BIP32Keystore.swift:165:71: use of unresolved identifier 'CBC'
EthereumKeystoreV3.swift:90:71: use of unresolved identifier 'CBC'
....

Such dependency works tho (points to a commit before the above one):
pod 'web3swift', :git => 'https://github.com/BANKEX/web3swift.git',
                     :commit => '8d7a985f93b3a5259366ae00606ff622cbc7fe5f' # Next commit breaks the build

0.8 tag is buildable, please specify a tag version in your podfile.

From: Elias Ovchynnikov<EMAIL_ADDRESS>Sent: Saturday, June 2, 2018 5:12:21 PM
To: BANKEX/web3swift
Cc: Subscribed
Subject: [BANKEX/web3swift] Use of unresolved identifier 'CBC' - build fails (#135)
Commit 8bbde2ehttps://github.com/BANKEX/web3swift/commit/8bbde2ea49d02cf98ae16c5717089f8b6bac8851 leads to build failure:
BIP32Keystore.swift:165:71: use of unresolved identifier 'CBC'
EthereumKeystoreV3.swift:90:71: use of unresolved identifier 'CBC'
....
PS: Can you move towards more reliable release process? This dependency pod 'web3swift', :git => 'https://github.com/BANKEX/web3swift.git' is not appropriate for prod use unless you will follow gitflow branching model and all master commits are realeasable. At least, please tag stable releases.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/BANKEX/web3swift/issues/135, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AGKv95G9Wo54jUae0_cdwvrLGoTIlv1Pks5t4p1FgaJpZM4UXs-9.

I met the same error. I've solved this by following @shamatar 's instruction.
pod 'web3swift', :git => 'https://github.com/BANKEX/web3swift.git', :tag => '0.8.0'

Hi @runryan, why did in encryptDataToStorage function on BIP32keystore.swift you set cipher : "aes-128-cbc" static! I want use it  as "aes-128-ctr" and I should edit pod library! Can I sent it via parameters?

Regarding the original issue - it should be fixed in 0.8.1 with CryptoSwift dependency bumped and written in requirements.
@MrShafiee
This behavior corresponds to one in original go-ethereum implementation for plain keystores (KeystoreV3 in web3swift). There is no standard for HD (BIP32) key trees storage, so in principle it can be changed. I'll add this option eventually, please write the corresponding feature request in separate issue.
Sincerely, Alex


fix(curriculum): remove an unneccessary preposition

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

Affected page: College Algebra with Python - Learn How to Graph Systems of Equations - Graphing Systems

Nice catch @mmatsumoto1026 👍 Thanks for contributing to freeCodeCamp 🎉


unable to run tasks

I was trying to execute the tasks but doesn't seem working, is it an issue with the ansible version ?
my ansible version:
ansible 2.9.6
  config file = /etc/ansible/ansible.cfg
  configured module search path = ['/home/ubuntu/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python3/dist-packages/ansible
  executable location = /usr/bin/ansible
  python version = 3.8.10 (default, Nov 26 2021, 20:14:08) [GCC 9.3.0]

logs:
ERROR! this task 'ansible.builtin.shell' has extra params, which is only allowed in the following modules: meta, import_tasks, include_tasks, win_command, add_host, win_shell, raw, shell, import_role, include_vars, set_fact, group_by, include, command, include_role, script

The error appears to be in '/home/ubuntu/.ansible/roles/alf149.crowdsec/tasks/main.yml': line 144, column 3, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:

- name: Crowdsec cscli bash completion
  ^ here

Sorry for the late answer. Hope this information helps.
On my pop_os test PC
I installed ansible with
sudo apt update && sudo apt install python3-pip
sudo pip3 install ansible
running ansible --version
gives me this output:
ansible [core 2.12.1]
config file = /home/USER/Documents/git/ansible/lab/ansible.cfg
configured module search path = ['/home/USER/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /usr/local/lib/python3.9/dist-packages/ansible
ansible collection location = /home/USER/Documents/git/ansible/lab/collections
executable location = /usr/local/bin/ansible
python version = 3.9.7 (default, Sep 10 2021, 14:59:43) [GCC 11.2.0]
jinja version = 3.0.3
libyaml = True


Add class-level docblock declaration with a couple of available fields accessible for a Jira issue

This list is not full, but your IDE will still benefit from it. It will also help you phpspec-ing when using this class.

Thank you for this request! :)
I think merging this is not a easy decision. E.g. in my use cases, no JIRA is ever used. Hence the getJiraId method does not return anything and the method-docs will mislead developers.
In addition to this, you don't provide return types for the methods.
Do you have any other pro-arguments on this?

Hi @nepda !
Well, hahah, sorry about that. It looks like I somehow left rubbish methods which doesn't even required. I declared the return values as mixed, however it would be string|null in most cases.
Let me fix that and let's continue the discussion.

Hi there - I've added the field doc blocks as per current documentation. I guess this looks a lot better now.
Regarding not-so-commonly used fields: as this is a general library for the YouTrack REST API, I think adding the method declarations (with an explanation for each field) will definitely avoid confusion.
Also, without this change it's impossible to mock the Issue object in a phpspec test. This is due to a limitation in phpspec/prophecy, which only allows you to use magic methods when they are defined as @method declarations.
There were some fields which I wasn't able to check properly, like the permittedUserGroup or the tag. I would appreciate any further advise on this :)
I hope this explanation convinces you somewhat better :) Cheers

I've discovered tags don't work at all currently :(
Yes, this looks much better. I'll just merge this and  wait for further feedback of the community.

Nice one, thanks!
Happy to resolve if something comes up.

You're welcome, thank you too! :)


Not refresh current page at update

Which OS ?
Android
Version
Which versions are you using:

react-native-swiper v1.6.0-nightly.5
react-native v0.61.5

Expected behaviour
If index prop is changed, current swipe-page should be scrolled to the updated page
Actual behaviour
On initial load Swiper is behave ok, display page that should be displayed by index.
When index updated Swiper doesn't scroll to the new position, despite of fact, that he is receive new offset in the Swiper components
How to reproduce it>
To help us, please fork this component, modify one example in examples folder to reproduce your issue and include link here.
import React, { useMemo, useRef, useState } from 'react';
import Swiper from 'react-native-swiper'
import { View, Text, Button } from 'react-native';

const ChannelScreen = () => {
  const ref = useRef ( null )
  const [ index, setIndex ] = useState ( 0 )

  const channelsList = useMemo ( () => [ '1', '2', '3', '4' ], [] )

  return (
    <View style={styles.wrapper}>
      <Button
        title="Press me"
        onPress={() => setIndex ( index + 1 )}
      />
      <Swiper loop={false}
              ref={ref}
              showsButtons={false}
              showsPagination={false}
              index={index}
      >
        {
          channelsList.map ( ( ch ) => {
            return (
              <View style={styles.slide1}>
                <Text style={styles.text}>{ch}</Text>
              </View>
            )
          } )
        }
      </Swiper>
    </View>
  );

};

export default ChannelScreen

const styles = {
  wrapper: {
    flex: 1,
  },
  slide1: {
    flex: 1,
    justifyContent: 'center',
    alignItems: 'center',
    backgroundColor: '#9DD6EB'
  },
  slide2: {
    flex: 1,
    justifyContent: 'center',
    alignItems: 'center',
    backgroundColor: '#97CAE5'
  },
  slide3: {
    flex: 1,
    justifyContent: 'center',
    alignItems: 'center',
    backgroundColor: '#92BBD9'
  },
  text: {
    color: '#fff',
    fontSize: 30,
    fontWeight: 'bold'
  }
}

Steps to reproduce
Here is very basic example.
I have array of channels.
On screen load, i define index based on some parameters, that receive from outside.
On Initial mount, Swiper works ok and display right page based on index.
If i press button, to change index (emulation of index update), i want that Swiper will display new Page based on index.
But this isn`t happen

i got same behavior, using scrollby() method change the index props but dont change the actual swiper view.

Which versions are you using:
react-native-swiper v1.6.0-nightly.5
react-native v0.61.5
issue coming for ios only to me

same issue.
has not it been resolved yet?
only android issue.

any update on this???


Request Multipart Image Error

I try to upload image to the server.
multipart.
but I got a message(console log)
[boringssl_session_write] SSL_ERROR_SYSCALL(5): operation failed externally to the library
<1> HTTP load failed (error code: -998 [2:0])

  case .editChannel(_, let logo, let banner, let name, let desc):
            var multipartData = [MultipartFormData]()
            if let logoData = logo {
                let logoMultipartData = MultipartFormData(provider: .data(logoData),
                                                          name: "logo",
                                                          fileName: "logo1",
                                                          mimeType: "image/png")
                multipartData.append(logoMultipartData)
            }

            if let bannerData = banner {
                let bannerMultipartData = MultipartFormData(provider: .data(bannerData),
                                                            name: "banner",
                                                            fileName: "banner1",
                                                            mimeType: "image/png")
                multipartData.append(bannerMultipartData)
            }

            if let nameData = name.data(using: .utf8) {
                let nameMultipartData = MultipartFormData(provider: .data(nameData),
                                                          name: "name")
                multipartData.append(nameMultipartData)
            }

            if let descData = desc.data(using: .utf8) {
                let desMultipartData = MultipartFormData(provider: .data(descData),
                                                         name: "desc")
                multipartData.append(desMultipartData)
            }

            return .uploadMultipart(multipartData)

what am I do?
Thank you.

The SSL_ERROR_SYSCALL log doesn't seem to be important in your case, see this post on SO.
Also, i've also searched for the urlerror using the code -998 but didn't find it :(

Yes, the error seems to be kCFURLErrorUnknown which doesn't help, unfortunately. @Leedongjin-nbt is this reproducible all the time? Is this a custom server? Does an upload without multipart data work (Task.upload(...))?

Could you please try to write your filenames with extensions?
I mean instead of writing fileName: "logo1",, write fileName: "logo1.png",.

Hi!! Thank you for your answers.
Unfortunately,  Change my filename with extensions doesn't work for me.
But, I try to change a file format Using jpegData Method.
guard let image = info[.editedImage] as? UIImage else { return }
guard let imageData = image.jpegData(compressionQuality: 0.5) else {
            // Error
            return }

It is work!!!
So My question is How can I set an available image size Moya multi-part upload?


Open external app without UrlScheme

Hello,
I am trying to open an external app from my Flutter app on iOS.
The external app does not provide URLSchemes in its info.plist.
The idea is just to open the app without deep linking.
How can I do that?
thanks

I would say its not possible.
The called app needs so accept this call.
Even if no data is given, it has to implement a call handler.


no results returned

Hi
Thank you for providing this package! I ran the following script but got nothing returned. Any idea what caused it?

@yudeng2022 thank you for opening this issue 👍
Could you please tell:

what's your OS.
your Python version.

Could you try running %pip install scrape-google-scholar-py before imports? Although not sure if it makes a difference.
Running locally on Python 3.11 via VSCode Jyputer plugin from fresh virtual environment:

Worked without %pip install scrape-google-scholar-py on a fresh environment:

CLI process
/c/Workspace/Programming/SerpApi/projects/scrape-google-scholar-py
› python -m venv env

/c/Workspace/Programming/SerpApi/projects/scrape-google-scholar-py
› source env/Scripts/activate
(env)

/c/Workspace/Programming/SerpApi/projects/scrape-google-scholar-py
› pip install scrape-google-scholar-py

Collecting scrape-google-scholar-py
  Using cached scrape_google_scholar_py-0.3.3-py3-none-any.whl
Collecting google-search-results>=2.4.2
  Using cached google_search_results-2.4.2.tar.gz (18 kB)
  Preparing metadata (setup.py) ... done
Collecting selectolax>=0.3.12
  Using cached selectolax-0.3.13-cp311-cp311-win_amd64.whl (2.0 MB)
Collecting parsel>=1.7.0
  Using cached parsel-1.8.1-py2.py3-none-any.whl (17 kB)
Collecting selenium-stealth>=1.0.6
  Using cached selenium_stealth-1.0.6-py3-none-any.whl (32 kB)
Collecting pandas>=1.5.3
  Using cached pandas-2.0.1-cp311-cp311-win_amd64.whl (10.6 MB)
Collecting webdriver-manager>=3.8.5
  Using cached webdriver_manager-3.8.6-py2.py3-none-any.whl (27 kB)
Collecting requests
  Using cached requests-2.29.0-py3-none-any.whl (62 kB)
Collecting python-dateutil>=2.8.2
  Using cached python_dateutil-2.8.2-py2.py3-none-any.whl (247 kB)
Collecting pytz>=2020.1
  Using cached pytz-2023.3-py2.py3-none-any.whl (502 kB)
Collecting tzdata>=2022.1
  Using cached tzdata-2023.3-py2.py3-none-any.whl (341 kB)
Collecting numpy>=1.21.0
  Using cached numpy-1.24.3-cp311-cp311-win_amd64.whl (14.8 MB)
Collecting cssselect>=0.9
  Using cached cssselect-1.2.0-py2.py3-none-any.whl (18 kB)
Collecting jmespath
  Using cached jmespath-1.0.1-py3-none-any.whl (20 kB)
Collecting lxml
  Using cached lxml-4.9.2-cp311-cp311-win_amd64.whl (3.8 MB)
Collecting packaging
  Using cached packaging-23.1-py3-none-any.whl (48 kB)
Collecting w3lib>=1.19.0
  Using cached w3lib-2.1.1-py3-none-any.whl (21 kB)
Collecting Cython>=0.29.23
  Using cached Cython-0.29.34-py2.py3-none-any.whl (988 kB)
Collecting selenium
  Using cached selenium-4.9.0-py3-none-any.whl (6.5 MB)
Collecting python-dotenv
  Using cached python_dotenv-1.0.0-py3-none-any.whl (19 kB)
Collecting tqdm
  Using cached tqdm-4.65.0-py3-none-any.whl (77 kB)
Collecting six>=1.5
  Using cached six-1.16.0-py2.py3-none-any.whl (11 kB)
Collecting charset-normalizer<4,>=2
  Using cached charset_normalizer-3.1.0-cp311-cp311-win_amd64.whl (96 kB)
Collecting idna<4,>=2.5
  Using cached idna-3.4-py3-none-any.whl (61 kB)
Collecting urllib3<1.27,>=1.21.1
  Using cached urllib3-1.26.15-py2.py3-none-any.whl (140 kB)
Collecting certifi>=2017.4.17
  Using cached certifi-2022.12.7-py3-none-any.whl (155 kB)
Collecting trio~=0.17
  Using cached trio-0.22.0-py3-none-any.whl (384 kB)
Collecting trio-websocket~=0.9
  Using cached trio_websocket-0.10.2-py3-none-any.whl (17 kB)
Collecting colorama
  Using cached colorama-0.4.6-py2.py3-none-any.whl (25 kB)
Collecting attrs>=19.2.0
  Using cached attrs-23.1.0-py3-none-any.whl (61 kB)
Collecting sortedcontainers
  Using cached sortedcontainers-2.4.0-py2.py3-none-any.whl (29 kB)
Collecting async-generator>=1.9
  Using cached async_generator-1.10-py3-none-any.whl (18 kB)
Collecting outcome
  Using cached outcome-1.2.0-py2.py3-none-any.whl (9.7 kB)
Collecting sniffio
  Using cached sniffio-1.3.0-py3-none-any.whl (10 kB)
Collecting cffi>=1.14
  Using cached cffi-1.15.1-cp311-cp311-win_amd64.whl (179 kB)
Collecting exceptiongroup
  Using cached exceptiongroup-1.1.1-py3-none-any.whl (14 kB)
Collecting wsproto>=0.14
  Using cached wsproto-1.2.0-py3-none-any.whl (24 kB)
Collecting PySocks!=1.5.7,<2.0,>=1.5.6
  Using cached PySocks-1.7.1-py3-none-any.whl (16 kB)
Collecting pycparser
  Using cached pycparser-2.21-py2.py3-none-any.whl (118 kB)
Collecting h11<1,>=0.9.0
  Using cached h11-0.14.0-py3-none-any.whl (58 kB)
Installing collected packages: sortedcontainers, pytz, w3lib, urllib3, tzdata, sniffio, six, python-dotenv, PySocks, pycparser, packaging, numpy, lxml, jmespath, idna, h11, exceptiongroup, Cython, cssselect, colorama, charset-normalizer, certifi, attrs, async-generator, wsproto, tqdm, selectolax, requests, python-dateutil, parsel, outcome, cffi, webdriver-manager, trio, pandas, google-search-results, trio-websocket, selenium, selenium-stealth, scrape-google-scholar-py
  DEPRECATION: google-search-results is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed. pip 23.1 will enforce this behaviour change. A possible replacement is to enable the '--use-pep517' option.
Discussion can be found at https://github.com/pypa/pip/issues/8559
  Running setup.py install for google-search-results ... done
Successfully installed Cython-0.29.34 PySocks-1.7.1 async-generator-1.10 attrs-23.1.0 certifi-2022.12.7 cffi-1.15.1 charset-normalizer-3.1.0 colorama-0.4.6 cssselect-1.2.0 exceptiongroup-1.1.1 google-search-results-2.4.2 h11-0.14.0 idna-3.4 jmespath-1.0.1 lxml-4.9.2 numpy-1.24.3 outcome-1.2.0
packaging-23.1 pandas-2.0.1 parsel-1.8.1 pycparser-2.21 python-dateutil-2.8.2 python-dotenv-1.0.0 pytz-2023.3 requests-2.29.0 scrape-google-scholar-py-0.3.3 selectolax-0.3.13 selenium-4.9.0 selenium-stealth-1.0.6 six-1.16.0 sniffio-1.3.0 sortedcontainers-2.4.0 tqdm-4.65.0 trio-0.22.0 trio-websocket-0.10.2 tzdata-2023.3 urllib3-1.26.15 w3lib-2.1.1 webdriver-manager-3.8.6 wsproto-1.2.0

[notice] A new release of pip available: 22.3 -> 23.1.2
[notice] To update, run: python.exe -m pip install --upgrade pip

Closing as Google itself doesn't return any results. Feel free to add additional info.

@yudeng2022

I meant to get all the results containing the keyword 'dynamic risk prediction'

What do you mean by "all results containing the keyword 'dynamic risk prediction'"? All results from searching Google Scholar profiles? Could you please clarify or give an example link?
Thank you 👍

Hi
Thank you for your reply! I tried to use the following code to get results

serpapi_parser_get_organic_results = SerpApiGoogleScholarOrganic().scrape_google_scholar_organic_results(
    #query= '("longitudinal data" OR "repeated measurements" OR "longitudinal measurements" OR "time series data") AND ("cardiovascular disease prediction" OR "cardiovascular disease risk prediction" OR "prediction of cardiovascular disease")' ,
    query='blizzard',
    api_key='##myapikey##', # https://serpapi.com/manage-api-key
    lang='en',
    pagination=True,
)

However, I got the error message:

Do you know what caused it by any chance?