fix(client): Import: error message is not described well for an unknown handler

Made changes to show a descriptive message when an app is imported with unknown handler.
fixes #1070
Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines: TBD
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (check one with "x")
[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

What is the current behavior?
#1070 - Error message is not descriptive when an unknown handler is imported

What is the new behavior?
Added a descriptive error message when an app with unknown handler is imported

@ppaidi the branch has conflicts with master, could you rebase it


[BUG] Furnace has no animation

Please post multiple screenshots on a site like Imgur and post config files on a site like Pastebin or some other alternative.
https://imgur.com/a/umifG3s
Please describe the bug
What is the bug? What do you think the appropriate behavior would be for this feature? (Paste screenshots here)
The /furnace has no furnance animation
How to reproduce the error?
What can I do to reproduce the error you have experienced? Please be detailed.

What version of Spigot are you using? /ver What plugins are you using? /plugins
Tuinity 1.17.1
What is the plugins version?
Please run '/pci version' in your console or in game and paste it here.
1.6.6

Known issue with Paper and forks.

Issue opened https://github.com/PaperMC/Paper/issues/6184

As an update to this: this has been fixed in https://github.com/PaperMC/Paper/commit/501834e57a7a343003c6f81757ec616be95a55dd


Implement Cycle Detection on Account Update

It will only be able to detect cycles within the recursion depth limit. I think this should be done client side and by certain witness nodes. It can be implemented "after the fact" and thus is low priority.

This is a wallet issue.


Avoid creating session path when creating waiters

@hakonhall please review.

I am not sure if I understand the change, won't both the old and the new code create .../sessions/n/waiterPath? create() javdoc says Creates an empty node at a path, creating any parents as necessary.


question on loading fst

Does multiple workers for multiple input streap load fst multiple times, or you just do one load and manage it across all workers.
Regards,
Ananth N

No, it's not implemented (and it would be difficult to do with the current architrecture).


Revert "Revert "Use new implementation of Maven version standard""

Reverts dependabot/dependabot-core#10647
What are you trying to accomplish?
Update Maven to use the newly implemented maven version standard: https://github.com/dependabot/dependabot-core/pull/10524

I added a new implementation of the maven version standard in PR https://github.com/dependabot/dependabot-core/pull/10524. However, to reduce the size of that PR I decided to create a separate PR where I can integrate the new version implementation.

Fixes incorrect version precedence and adds extra tests for version comparisons.
Anything you want to highlight for special attention from reviewers?
The maven spec: https://maven.apache.org/pom.html#version-order-specification is not 100% compatible with the implementation we had before. For example, in the previous implementation, any versions with qualifiers like 'pr', 'pre' or 'dev' were considered prereleases. The maven spec only mentions "alpha", "beta", "milestone", "rc", "cr" and "snapshot" as having lower precedence than ("" | final | ga) i.e. as potential prereleases.
In my view, it's better to strictly follow the spec since standardising is one of our goals. Therefore, I have removed the other tokens from the previous implementation that were being treated as prereleases. However, this could be a breaking change for some users who might expect versions like 1.2.dev to have lower precedence than 1.2.dev, for example.
I've also had to remove some code and update tests to do with dynamic versioning e.g 2.+. This is a gradle feature that the maven specification doesn't support.
Finally, in order to test the new implementation thoroughly, I've grouped similar test inputs together and I loop through these lists to avoid having to manually type in the test cases individually. Inevitably, that's coming up as a huge diff in the test files.

I've merged https://github.com/dependabot/dependabot-core/pull/10664 into this one


<React.Fragment></React.Fragment>  JSX shorthand <></> [standard] Strings must use singlequote. (quotes)

What did you expect to happen?
react v16 <React.Fragment></React.Fragment>  JSX shorthand <></>
[standard] Strings must use singlequote. (quotes)

Related: https://github.com/eslint/eslint/issues/9662

swears to <></>:
[standard] Strings must use singlequote. (quotes)

This is fixed in standard 12.


Collapsible Toolbar with TabBar

Hi All,
Tried to achieve collapsing toolbar with tabbar,
--
referring to --  https://medium.com/appandflow/react-native-scrollview-animated-header-10a18cb9469e
But no luck!!!

Do you mean it is slow? I think it is common pattern. Would you like to share your work?

sure

I had the same issue, in the end I forked this repo and did the changes that fit my specs. I might publish it to npm if there's an interest for it.

@tibbus  can you share the npm link??

@tibbus I would love to add this as a custom tab bar into this repository.

@tibbus can you share your fork? Thanks!

Here is what I did:
https://github.com/binchik/react-native-scrollable-tab-view/commit/524c041d0e111adaa474d4d1415a6d3cc441f432
Then you can just wrap your tab bar inside Animated.View and animate translateY based on scroll value.

Here is the code and PR : https://github.com/skv-headless/react-native-scrollable-tab-view/pull/667

@tibbus  thank you so much,
@skv-headless  please merge the above PR .


Clusterwide lock mode

See https://github.com/samphilipd/rihanna/issues/46 for discussion.
This would bring enhanced performance when run on a single Erlang cluster.

This architecture would need to perform some kind of durable state management that can handle nodes going down, including the master. I'm sceptical that this would be orders of magnitude faster than the same implemented in Postgres, though that's just a baseless hunch.
How do you intend the state management and failure detection to work with this design?

What happens when the global lock process goes down?
What happens when a node is isolated from the global lock process by a network partition?

First case scenario:
A new singleton will be booted which will re-acquire the global lock and start reading jobs again. Some jobs may be executed twice.
Second case scenario:
Erlang's built-in monitoring will realise the network partition, interpret that node as down and assume none of the jobs it was running have been executed. The global lock process will re-dispatch these jobs to a node that is alive. Some jobs may be executed twice.

What happens to the workers? All killed by the exit from the global lock process? In cloud environments network partitions are common (Erlang was designed for more reliable networks) so this may cause some disruption. I'm not sure how fast global links are, would be cool to test this.
In the network partition situation if we're using global processes we'll end up with at least two nodes running the global lock process. Would this be safe? If we're still running the same SQL query to the database it would be but I'm unsure if that was the intention.
All sounds fun so far :) I'd suggest that (at some point) it'd be worth doing some preliminary benchmarking so we can get a better understanding.

Workers on the partitioned node may continue to run, which is why some jobs may execute twice. There was always a conscious design choice in Rihanna to guarantee at-least-once execution, hence this failure mode.
We will never have two nodes running the global lock process, because postgres will only ever grant the advisory lock once.

It's the same guarantee, but the likelihood of multiple delivery would increases substantially, one to document well.

We will never have two nodes running the global lock process, because postgres will only ever grant the advisory lock once. In the event of a netsplit and two master nodes occurring, one of them will fail to take the lock and simply do nothing.

Would there be an additional database lock then? We don't currently do this

Yes, the probability of multiple executions will be slightly higher, but not unmanageably so. Unexpected netsplits and/or node deaths are not that common, especially if a graceful exit with job draining is implemented. I think this is probably an unavoidable cost of increased throughput.
As for the lock, I'm not sure you have fully understood my original proposal. In this new scenario, there will be one and exactly one advisory lock taken by one global dispatcher. Workers will not be required to take any locks at all.
It will not need the same query. There will be some code shared, around enqueuing and deleting jobs. I imagine it to be implemented as a separate dispatcher module, so the user can choose which one they boot in their supervision tree.

especially if a graceful exit with job draining is implemented.

I think that in the event of the dispatcher/lock death we want to brutally kill workers rather than killing them gracefully- otherwise multiple delivery is guaranteed.

As for the lock, I'm not sure you have fully understood my original proposal. In this new scenario, there will be one and exactly one advisory lock taken by one global dispatcher. Workers will not be required to take any locks at all.

I see, much clearer now :)


Avoiding pointer events already used for scrolling

Hello, this seems like a great library! So far it's been very straightforward to integrate into my game.
I do have a problem, though, with interactive objects within the scrollbox. In my case, these are text boxes for which I subscribe to the pointertap event. I don't want the pointertap event to fire, though, in the case that the ScrollBox has already handled it.
Can you think of a way where I could filter out those pointertap events that have been used to scroll? Or perhaps there is some other way to achieve this?
Thanks a lot

The easiest way to fix this is to use the pointerdown/pointerup events instead of pointertap. By default the scrollbox (which uses pixi-viewport) calls event.stopPropagation on pointerup/pointerdown events that are used by the viewport (e.g., to stop the viewport from scrolling during the decelerate() plugin. Hope that helps!

Thanks for your quick answer @davidfig.
I eventually figured it out- in fact stopPropogation is implemented for dragging the scrollbar, but not for dragging within the window (the dragScroll() function perhaps?).
Also, and this is probably unrelated, I notice that when I scroll using the mousewheel (my laptop trackpad), the contents of the ScrollBox get moved to the right (perhaps being centered?). Would you have any idea on that one?
Thanks again !

Hi @davidfig . I found the issue with the events propagating. In fact, since my text boxes are inside the scrollbox, it's only normal that those boxes get the events first, before the scrollbox does. To get around this problem, I keep track of the drag-start and drag-end events, and ignore pointerup events during dragging.
With regards to the mouse wheel issues, I debugged them and offered a solution in a PR. Let me know what you think! #8


Extension issue

Issue Type: Bug
Extension Name: autolispext
Extension Version: 1.5.0
OS Version: Windows_NT x64 10.0.18363
VS Code version: 1.60.0

:warning: We have written the needed data into your clipboard. Please paste! :warning:
{
	"messages": [],
	"activationTimes": {
		"codeLoadingTime": 485,
		"activateCallTime": 12,
		"activateResolvedTime": 44,
		"activationReason": {
			"startup": false,
			"extensionId": {
				"value": "Autodesk.autolispext",
				"_lower": "autodesk.autolispext"
			},
			"activationEvent": "onLanguage:autolisp"
		}
	},
	"runtimeErrors": [
		{
			"name": "TypeError",
			"message": "Cannot read property 'document' of undefined"
		}
	],
	"runningLocation": 1
}

Hi @szq ,
May I ask what's the use case in problem?


JavaFxInitialiser Test

Test proving very difficult to run, may need forking of some kind. Test currently does not run on Jenkins, but can be run locally.
Note that this functionality was pulled from a private project and will be fixed there first.

Test causing issues again. Seems only useful in manual testing scenarios now. Needs to be refactored and handled properly.

Separated into integration tests.


Add goci lint.

Signed-off-by: xuezhaojun<EMAIL_ADDRESS>

/assign @qiujian16

I guess a lot of errors are ignore, I will fix those soon.

/approve
/lgtm


Run PDL matching patterns once per operatio

Introduce a new helper function that wraps PatternApplicator so that
each pattern (in the case of Transform dialect, only the matching part
is actually relevant) is checked at most once against every operation.
No greedy recursive pattern application or worklist of newly created
operations is needed for this purpose. This allows us to stop relying
on the absence of the "matched" attribute in the IR to stop recursive
matching. The attribute itself is still added as a debugging aid.

Do you see this + previous stuff connecting to #95 or it just being obsolete?

Either obsolete (I pulled some ideas from there) or not-ready-yet (most of stage-1 transformations are not actually a single pattern, but a sequence of patterns+enablers). I'd still keep it for a while.


fix: init config of containerd based on the cgroup version

What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for reviewers:

Does this PR introduced a user-facing change?

Additional documentation, usage docs, etc.:

Codecov Report

Merging #580 (5207ebe) into master (6982d82) will decrease coverage by 0.01%.
The diff coverage is 0.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

@@            Coverage Diff             @@
##           master     #580      +/-   ##
==========================================
- Coverage   14.03%   14.03%   -0.01%
==========================================
  Files         138      138
  Lines       19503    19512       +9
==========================================
  Hits         2738     2738
- Misses      16469    16478       +9
  Partials      296      296

Impacted Files
Coverage Δ

pkg/cli/deploy/deploy.go
5.99% <0.00%> (ø)

pkg/scheme/core/v1/cri/containerd.go
11.91% <0.00%> (-0.41%)
:arrow_down:

/lgtm
/approve

/cherry-pick release-1.3


Unable to boot after upgrading an image with file system customization

The issue is that the osbuild-ostree-mountpoints.service cannot create custom directories as seen in journald.
Aug 05 08:31:59 localhost mkdir[1048]: mkdir: cannot create directory ‘/foo’: Operation not permitted
Aug 05 08:31:59 localhost mkdir[1048]: mkdir: cannot create directory ‘/foo’: Operation not permitted
Aug 05 08:31:59 localhost systemd[1]: osbuild-ostree-mountpoints.service: Main process exited, code=exited, status=1/FAILURE
Aug 05 08:31:59 localhost systemd[1]: osbuild-ostree-mountpoints.service: Failed with result 'exit-code'.
Aug 05 08:31:59 localhost systemd[1]: Failed to start Ensure custom filesystem mountpoints exist.
Aug 05 08:31:59 localhost systemd[1]: foo.mount: Failed to check directory /foo: No such file or directory
Aug 05 08:31:59 localhost systemd[1]: Mounting /foo...
Aug 05 08:31:59 localhost mount[1051]: mount: /foo: mount point does not exist.
Aug 05 08:31:59 localhost systemd[1]: foo.mount: Mount process exited, code=exited, status=32/n/a
Aug 05 08:31:59 localhost systemd[1]: foo.mount: Failed with result 'exit-code'.
Aug 05 08:31:59 localhost systemd[1]: Failed to mount /foo.
Aug 05 08:31:59 localhost systemd[1]: Dependency failed for /foo/bar.
Aug 05 08:31:59 localhost systemd[1]: Dependency failed for Local File Systems.
Aug 05 08:31:59 localhost systemd[1]: Dependency failed for Mark the need to relabel after reboot.

osbuild-ostree-mountpoints.service:
[core@localhost ~]$ sudo cat /etc/systemd/system/osbuild-ostree-mountpoints.service
[Unit]
Description=Ensure custom filesystem mountpoints exist
DefaultDependencies=False
ConditionPathIsDirectory=|!/foo/bar
ConditionPathIsDirectory=|!/foo
After=ostree-remount.service
Before=foo-bar.mount
Before=foo.mount

[Service]
Type=oneshot
ExecStartPre=/bin/sh -c "if grep -Uq composefs /run/ostree-booted; then chattr -i /; fi"
ExecStopPost=/bin/sh -c "if grep -Uq composefs /run/ostree-booted; then chattr +i /; fi"
ExecStart=mkdir -p /foo/bar /foo

[Install]
WantedBy=local-fs.target

fs-image blueprint:
name = "rhel-95-fs-customization"
description = "rhel-95-fs-customization-image"
version = "0.0.1"
packages = []
modules = []
groups = []
distro = "rhel-9.5"

[customizations]

[[customizations.filesystem]]
mountpoint = "/foo/bar"
minsize =<PHONE_NUMBER>

[[customizations.filesystem]]
mountpoint = "/foo"
minsize =<PHONE_NUMBER>

upgrade-container:
name = "rhel-95-gimp-container"
description = "rhel95-gimp-container"
version = "0.0.1"
modules = []
groups = []
distro = "rhel-9.5"

[[packages]]
name = "gimp"

[customizations]

[[customizations.user]]
name = "core"
description = "Administrator account"
password = "$6$ZOU0XIQ9C2DgnKle$RwHmmOORsZjCnDbXIP4skChWuacNs9YFn.CC8xGKq3BYed55ipMPXL7OpTjLIxGjROsY7jw2phTgTIi1sTKp6/"
key = "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQC0rTkBTp+ii0S2XB/Tj3fsAm+wenVdGMZVL6pqtRPq4Qxohe87RtUk+EBt80/XdtrKIotREOR38Gu6vKJMbCfjkwj8pYphTkqaaNLTSXz7ulqDm3FLjOoXW1Lfg5DC4ap3ILfAmkZEgB54h7VC2dn7XJfZxcu1Q7HAFfNrpCHY7zo3XWs81AScpIrSmJAh2Ne3x53TMKqcAIkGGN0ipjY51J3zSivpsGJo5bAQ8DbY+ZXVlmOZvhCTv/UY4MHC+dv7gVy0y6JYQYfdpMRy0u3gGcsI2f9y//L9B9AOf6MzX4nAo1zquW0xKqX5w6eMITtMYP/4zwjtuIuI55d9AMcm7hwf5jWzT3fwTiqQ3dxqRrJp1SJ7tTHAcYwErIuly8bzz/rOhzD2gFuKkM/TqbTQc+MG4Oj6A07MqPqLRkNkR9WPCTxwf6o6BUSnfzVPvs7Xg0RWQlUXOvM3eVtdOB/5X+jbnvASXwaVmuLmv1A0U2sUtf9bP7XoMJwbVGvugmE=<EMAIL_ADDRESS>shell = "/usr/bin/bash"
groups = ["users", "wheel"]

We need to invert the logic here as with composefs we won't need chattr.. if transient rootfs is enabled: https://github.com/osbuild/images/blob/fa9b520763af4fa44fce3a6cf43481c714a91122/pkg/manifest/ostree_deployment.go#L524


Container width in %

Hi,
I am dividing my screen in to 2 parts. First contains timeline, second - other content.
Second part has width param, first uses rest of space.
If second part has fixed size in pixels, timeline works great even when changing size of the browser.
But if second has width set in %, part of timeline disappear  accidentally (everything besides groups names).
Any Idea, how to solve it?
Thanks!

+1 that i have same problem.
i fixed it with calling .resize() method when layout changes. it it dirty hack, but it works in my case
BTW i use mobx
// Subscribe for layout changes
        this.dispose = observe(
            // Subscribe for my updates
            ui.filters.state[types.OVERVIEW_FILTER],
            (change) => {
                // If change is to open/close filter (which require re-painting)
                if (change.name === 'opened') {
                    // If we hide filter -> save initial width of timeline
                    if (!change.newValue) {
                        change.object.memorizedScrollWidth = this.refs.timeline.refs.scrollComponent.offsetWidth;
                        setTimeout(() => this.refs.timeline.resize(), 0);
                    // If we show filter -> restore saved initial width for timeline
                    } else {
                        this.refs.timeline.refs.scrollComponent.style.width = `${change.object.memorizedScrollWidth}px`;
                        setTimeout(() => this.refs.timeline.resize(), 0);
                    }
                    ui.showDebug('Trigger resize of overview');
                }
            });
    }

Any news here?

Hey, while I couldn't reproduce the bug as you described, there is now support to detect changes to the width of the container itself. Here's a demo where it works (source).
Closing this issue. Feel free to reopen if there are still issues.


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-k8s-23-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1210

Questions ?
Please refer to the Backport tool documentation


There is a bug in odysee on upload

There is a bug in odysee, you can only schedule the video upload date in the past and not in the future, which doesn't make any sense.

It's not possible to schedule videos in the future yet.  Hope to have it later this year.


Is there anyway to change a markers height offset from the marker renderer options?

Is it possible to create two layers with this by placing two markers at the same location, but elevating one above the other?

@jabusir, this is not supported (markerOffsetRadiusScale applies to all markers but not individual markers).  It might be possible for me to read this property on each marker and use it as a override to the value set in options, but probably not willing to support this unless it's more broadly needed.
Feel free to fork the repo and adjust this for your needs if it works out!
Another potential option is to render custom markers options.markerRenderer.  The globe will help you place markers in the appropriate places, but you can control rendering using a custom renderer.  You probably have to do some trigonometry on your side to determine how to place the marker at a specific elevated height.

Hi Chris,
Thank you for your response. That was really insightful.
Also had another question, hope you don't mind me dropping it here, but can globeBackgroundTexture and other textures be set to assets that are on my machine or do the assets have to be hosted on the web. Thanks again :)


Add hashnode cms guide

Add a new guide for Hashnode CMS

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File
Note
Locale

src/content/docs/en/guides/cms/hashnode.mdx
Source added, will be tracked.
en

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

Hey @Adammatthiesen ! Just checking in and seeing whether you were still interested in finishing this one! I know we made you wait a while for initial reviews... so, fair.  :sweat_smile:

Hey @Adammatthiesen ! Just checking in and seeing whether you were still interested in finishing this one! I know we made you wait a while for initial reviews... so, fair. 😅

oh nuts, i just noticed this..... heh lots of good notes... and yes its the ghostCMS guide copy pasted... lol

!coauthor


[WIP] Running must gather after each tests

Was trying to run using oc client, but after some research, it may very cumbersome to run oc adm ... commands using oc go client.
Running must gather using shell.

woot... thank you @deepakraj1997 for looking into this!

/hold for https://github.com/openshift/oadp-operator/pull/599

/retest

/test 4.8-operator-e2e 4.7-operator-e2e

https://coreos.slack.com/archives/CFUGK0K9R/p1647955342187699 We are running our tests on build03.

/retest

/test 4.7-operator-e2e

/test 4.8-operator-e2e

/hold for https://github.com/openshift/release/pull/27197

Pending: To updated using 'oc' from CLI_DIR

/test 4.8-operator-e2e

/unhold

/retest

/retest

NICE! @hhpatel14  FYI


Building universal 2 on macOS is broken

CMake has a handy way to build Universal (fat) binaries with x86_64 and arm64 chunks. A recent change seems to break it (https://github.com/AcademySoftwareFoundation/openexr/pull/772). This is with Xcode 12.2 beta 2.
I have found that trying to detect compiler support for CPU specific functions is really annoying when building universal binaries with cmake as what you want to ask is not does my compiler support AVX? as this will try to build AVX instructions for both x86_64 (fine) and then arm64 (fail), which then fails. What you needs is does my compiler support AVX in x86_64 mode?, then to use platform #defines to switch in the actual code.
% cmake -DPYILMBASE_ENABLE=OFF -DCMAKE_OSX_ARCHITECTURES="arm64;x86_64" ../
-- The C compiler identification is AppleClang <IP_ADDRESS>00032
-- The CXX compiler identification is AppleClang <IP_ADDRESS>00032
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /Applications/Xcode-beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /Applications/Xcode-beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Configure ILMBASE Version: 2.5.3 Lib API: 25.0.2
-- Setting build type to 'Release' as none was specified.
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
-- Found Threads: TRUE
-- Looking for include file ucontext.h
-- Looking for include file ucontext.h - not found
-- Configure OpenEXR Version: 2.5.3 Lib API: 25.0.2
-- Found ZLIB: /Applications/Xcode-beta.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.0.sdk/usr/lib/libz.tbd (found version "1.2.11")
-- Performing Test OPENEXR_IMF_HAVE_SYSCONF_NPROCESSORS_ONLN
-- Performing Test OPENEXR_IMF_HAVE_SYSCONF_NPROCESSORS_ONLN - Success
-- Performing Test OPENEXR_IMF_HAVE_GCC_INLINE_ASM_AVX
-- Performing Test OPENEXR_IMF_HAVE_GCC_INLINE_ASM_AVX - Failed
CMake Error at OpenEXR/config/CMakeLists.txt:51 (if):
  if given arguments:

    "arm64" "x86_64" "MATCHES" "arm64"

  Unknown arguments specified

If I revert the PR linked above I can build univerally, but the AVX ASM is disabled, which is also not desirable.

Thanks for the report. To start, can I request that if you are on a release version of CMake, could you retest using CMake 3.19, which is now available as a release candidate? https://cmake.org/download/ 3.19 has fixes for Xcode 12, including moving CMake from the Xcode 3 (!!!??!!!!!) build system to Xcode's current build system. They did this specifically to address building universal binaries.
I don't expect this will fix the issues you've encountered, but I think we should start from a version of CMake that's intended to address Apple Silicon, and work with Xcode 12.

I have done some further testing with cmake release and 3.19 and have a PR here.
https://github.com/AcademySoftwareFoundation/openexr/pull/854

Hmmm Universal 2 builds seem to be broken again on master... Maybe something to do with the library split?
Getting the "arm64" "x86_64" "MATCHES" "arm64" when cmaking off of master. If I checkout master at this commit, I can totally cmake Ilmbase with universal 2, and then cmake OpenEXR with universal 2, pointing to the built Ilmbase by exporting IlmBase_DIR.

Can you post the cmake command you are using to generate?

Sure thing (using cmake version 3.19.1):
cmake -DCMAKE_OSX_ARCHITECTURES="arm64;x86_64" ..


Win 11 Pro - 22000.593 Error

''the number of connections to this computer is limited'' this is the error

what .ini should i use to solve the problem ?

Duplicate of https://github.com/stascorp/rdpwrap/issues/1698


Literally Rewrite Entire Overview Page

@ThaiQ

Waiting for #186 and #400 to be completed.

Best if i dont touch it, see this article


Rename 'rdo_use_only' function parameters as 'use_recon_pixel'

Because it has been quite confusing, when its sole effect is
to decide whether doing pixel reconstruction or not.

Seems fine and surely it is easier to understand :)

Thank you for super quick turnaround of review!

Coverage remained the same at 83.226% when pulling 2ec39e87281cd77abebb3ea284fa1692772e8fe1 on ycho:rename_for_rdo_use into 86723c115c94e0ebbdae4ed6171cc8dd5d0badcc on xiph:master.

Testing on AWCY at various speeds, so let's wait until its done.

No change of default option, AWCY
AWCY runs for speed 0, 1 and w/ and w/o psnr will come soon.


Caste to int not via int64

What
See title
How to review
Check changes make sense and tests pass.
Who can review
Anyone

Closing and deleting pr, parent branch contains equivalent changes.


added animations to the about us page

I have made some changes as suggested by @smaranjitghose . Please check it.

text not visible in subheading please remove that
I have made the suggested changes.

Resolve conflict @abhu-A-J @ashishnagpal2498 merge them

Okay. I will merge it once @abhu-A-J will resolve the conflicts.

@kartikeya-123 you can resolve the conflict

You are mixing a whole bunch of CSS properties, which are not required. Kindly open inspect and look for those properties and remove them. Self review your code first.

@kartikeya-123 . If you don't reply to the conversation. Unfortunately I have to close this PR.


docs($resource): describe your change...

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Document update.
What is the current behavior? (You can also link to an open issue here)
The documentation currently reads a bit confusing for $resource actions/cache option.
What is the new behavior (if this is a feature change)?
Add a minor clarification in cache option.
Does this PR introduce a breaking change?
No.
Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit-message-format
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

Other information:

I signed it!


Not all ticked checkboxes are displayed in Acrobat Reader

Affected versions

Latest Nightly 82.0a1

Affected platforms

Ubuntu 18.04 64bit
MacOS 10.15
Windows 10 64bit

Steps to reproduce

Open the following https://www.nta.go.jp/taxes/tetsuzuki/shinsei/annai/joyaku/annai/pdf2/250.pdf
Scroll down to Indirect Ownership column inside the table from 6 and tick all checkboxes.
Save the pdf by download button, save as or open with
Open the saved pdf in Acrobat Reader.

Expected result

Checkboxes are ticked when opening the PDF in Acrobat.

Actual result

Some checkboxes are ticked, some checkboxes are empty, some can be edited/saved some not, some can't be edited anymore.

Regression range

Not a regression since this did not work before as well.

Suggested severity

I my opinion this should have the S2 severity since this is data loss related, not sure how many pdfs are affected though.

This file is encrypted and the resulting string after encryption may contain some \r and according to the spec (<IP_ADDRESS>), this char is interpreted like a \n which avoids to decrypt the string.
Few lines after in the specs, it is written that there is no need to escape such char...
I tested the fix with Acrobat on mac and it's ok.


Feature/licensing server macos

Changes

Added support for licensing server when building unity project on mac.

I do not have ability to verify that the username/password/serial flow still works. So please sanity check the changes, or even better test it if you have ability to. I had to remove sending in username/password in build.sh, but that shouldn't be required as it is activated already, and we do not do that in the ubuntu version of build.sh.
Checklist

[x] Read the contribution guide and accept the
code of conduct
[ x] Docs (If new inputs or outputs have been added or changes to behavior that should be documented. Please make
a PR in the documentation repo)
[x ] Readme (updated or not needed)
[ x] Tests (added, updated or not needed)

Codecov Report

Merging #573 (c14e406) into main (2190fd5) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head c14e406 differs from pull request most recent head cfe4a62. Consider uploading reports for the commit cfe4a62 to get more accurate results

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files

@@           Coverage Diff            @@
##             main     #573    +/-   ##
========================================
  Coverage   36.96%   36.96%
========================================
  Files          77       77
  Lines        3038     3038
  Branches      641      631    -10
========================================
  Hits         1123     1123
+ Misses       1915     1765   -150
- Partials        0      150   +150

see 38 files with indirect coverage changes

Hey there! Apologies for the extreme delay. We can work on getting this merged but there are a few merge conflicts that need to be resolved before we can merge. If you could resolve them then ping for a review here I can make that happen.

+1

for those needing license activation from server licensing on mac. A workaround I'm using is skipping license activation and passing an custom parameter for adquiring the license.
- name: Configure License
      shell: bash
      run: |
        # Define the config file path
        CONFIG_FILE="/Library/Application Support/Unity/config/services-config.json"
        UNITY_LICENSE_PATH="/Library/Application Support/Unity/config"

        # Define the JSON content
        JSON_CONTENT='{
          "licensingServiceBaseUrl": "http://localhost:8080",
          "enableEntitlementLicensing": true,
          "hubEnableWorkOffline": true,
          "clientConnectTimeoutSec": 60,
          "clientHandshakeTimeoutSec": 30
        }'

        if [ ! -d "$UNITY_LICENSE_PATH" ]; then
          echo "Creating Unity License Directory"
          sudo mkdir -p "$UNITY_LICENSE_PATH"
          sudo chmod -R 777 "$UNITY_LICENSE_PATH"
        fi;

        # Write the JSON content to the config file
        echo "$JSON_CONTENT" > "$CONFIG_FILE"

        # Set the correct permissions for the file
        sudo chmod 644 "$CONFIG_FILE"

        echo "License configuration file updated successfully at $CONFIG_FILE"

    - uses<EMAIL_ADDRESS>      name: Execute Unity Build on MacOS
      with:
        unityLicensingServer: 'http://localhost:8080'
        # if using server license
        skipActivation: 'true'
        customParameters: --acquire-floating
        targetPlatform: ${{ inputs.target-platform }}
        projectPath: ${{ inputs.path }}
        buildsPath: ${{ inputs.build-path }}
        allowDirtyBuild: true
        cacheUnityInstallationOnMac: ${{ inputs.cache-unity-installation }}
        versioning: ${{ inputs.version != '' && inputs.version || 'Semantic' }}


Jobs Fail Silently & Return "Job Completed Successfully" to Submitit. Requeue Doesn't Work.

stable-ssl jobs when run into an error still return that the job was completed successfully which prevents submitit from re-queueing the job. If the job is falling, it needs to throw errors properly for submitit to notice.

Fixed with latest version


Run Build Task fails with "Cannot split a terminal without a group"

Type: Bug

Cmd-B in a VS Code project which should launch 3 scripts.
Error notification: Cannot split a terminal without a group (instanceId: 2, title: npm: watch:tsc-extension).
Building … is stuck in loading.

Closed all terminals and still doesn't work
TRACE Found terminal to split for group watch
log.ts:439   ERR Cannot split a terminal without a group (instanceId: 2, title: npm: watch:tsc-extension): Error: Cannot split a terminal without a group (instanceId: 2, title: npm: watch:tsc-extension)
    at Kv.Sb (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2431:115280)
    at Kv.createTerminal (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2431:114088)
    at async IE.Cb (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2503:15746)
    at async IE.Fb (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2503:18379)
    at async IE.xb (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2503:8110)

VS Code version: Code - Insiders 1.95.0-insider (490dc3da779118d14a16d3b149d8c44edb9b1e07, 2024-10-10T05:09:29.500Z)
OS version: Darwin x64 23.6.0
Modes:

System Info

Item
Value

CPUs
Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz (16 x 2400)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabledwebgpu: enabledwebnn: disabled_off

Load (avg)
5, 6, 6

Memory (System)
64.00GB (13.49GB free)

Process Argv
--log trace --crash-reporter-id 4cf0a6f0-aaf8-4da3-9b2b-81f6c639c12b

Screen Reader
no

VM
0%

Duplicate of #226494

/duplicate https://github.com/microsoft/vscode/issues/226494


Establish GRPC connection in plaintext

--plaintext Establish GRPC connection in plaintext

[ ] When providing naked URL, add http:// instead of https://
[ ] When providing HTTPS URL, throw error

Implemented via https://github.com/pinax-network/substreams-sink/pull/31


The error : 'std::runtime_error'

Hello.When I ran the ./visualize and selected the data file, the runing window disappeared. But I can run the rangenet_lib correctly. The following are the tips from command window.
/********************************************/
OpenGL Context Version 4.5 core profile
GLEW initialized.
OpenGL context version: 4.5
OpenGL vendor string  : NVIDIA Corporation
OpenGL renderer string: GeForce RTX 2060/PCIe/SSE2
Extracting surfel maps partially.
Performing frame-to-model matching.
terminate called after throwing an instance of 'std::runtime_error'
what():  Can't open cfg.yaml from ~/test/darknet53/arch_cfg.yaml
/**********************************************/
Hope someone can help me solve this problem! Thanks.

Hey @ONMEKEEP,
As the error msg says it cannot find the yaml file. Could you please check the path to the model in the config file?

Hey @ONMEKEEP,
As the error msg says it cannot find the yaml file. Could you please check the path to the model in the config file?

Thank you for your reply. The model is located in /home/test/darknet53. And I modified the last line of default.xml with ~/test/darknet53. But it got the above error.

You could try with the full name rather than '~'. The tilde sometimes will not be parsed correctly.

Thank you for using our code. If you like it, you could star, watch and fork our code.
Since the problem is solved, I'm going to close this issue.


Add example workflow

Here is a screenshot of an example workflow.
After you have responses from different systems/models you can open a Pairwise Comparison Node that will run an evaluation LLM on all possible pairs (forward and backward).

Looking at it now I realize I need to make some changes to how the rubric is set, because the A and B responses are hard-coded in the scoring code. I also could improve settings for saving different rubrics and options for forward-backward pairings or not, and for random subsets or not. It does not integrate well with the progress bar, not tell you how many requests will be sent to the LLM. I suppose it could also choose the best several instead of just a pair. And the response options could be expanded, perhaps matching the lm-sys/FastChat approach of A, B, tie, bad. And could implement flexibility in scoring, perhaps within settings or an optional additional Python/JS evaluation node. I'd also like to implement a hint or ground-truth flow, perhaps with a node that aggregates all responses and is checked by a human before entering into the Comparison Node as a hint. Note: I'm intending this particularly for testing generative web search systems, so I haven't been thinking about other goals.
Here is the Pairwise Comparison Inspector Grouped List tab

and the Scores tab:

[x] I will make another repo with my custom providers (very rudimentary at this moment).
[ ] I'll make a more careful write-up of my process and learnings.

See here: ChainForge_SearchProviders

Wow!!! I love the idea and the Scores tab. It’s incredible awhat you’ve been able to do! Please keep me updated.
Some thoughts:

How do you know the scores are ‘correct’? Maybe its an example here, so the rubric is fairly general, but I still think verification may be an issue for users. It was my main issue w “prompt royale.”
The LLM scorer node is the worst designed node IMO in ChainForge —it should be much better UI with locked output types. I implemented it under time pressure. I see an inherited design problem w the pairwise scorer node —would be nice to think of how to improve this UI design for users, later on.


cant assign the network interface to the BPF handle

trying run simple_IMSI-catcher.py script on
OS X High Sierra 10.13.6 (17G65)
Python 2.7.16
scapy 2.4.2
scipy 1.2.1
numpy 1.16.2
sudo python simple_IMSI-catcher.py -s
Traceback (most recent call last):
  File "simple_IMSI-catcher.py", line 533, in <module>
    sniff(iface=options.iface, filter="port {} and not icmp and udp".format(options.port), prn=find_imsi_from_pkg, store=0)
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/scapy/sendrecv.py", line 836, in sniff
    *arg, **karg)] = iface
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/scapy/arch/bpf/supersocket.py", line 72, in __init__
    raise Scapy_Exception("BIOCSETIF failed on %s" % self.iface)
scapy.error.Scapy_Exception: BIOCSETIF failed on lo

found this in src scapy/supersocket.py
https://github.com/secdev/scapy/blob/master/scapy/arch/bpf/supersocket.py#L68
sudo python immediate_assignment_catcher.py
gives the same result..
thks for your attention

please answer me if my question is incomprehensible

Have you try ? :
python scan-and-livemon
(no sudo)


[Samples][Java] Fix disparities of 17.multilingual-bot sample

Related to microsoft/botbuilder-java1165
Proposed Changes
We compared the documentation/code migration/behavior of the 17.multilingual-bot sample between Java and C# and we found disparities and fixes that this PR includes.

Update README
Clean-up autogenerated files/folder related to Eclipse (e.g. target/.classpath)
Add missing comments
Add package-info.java file

Testing
Multilingual Bot sample working as expected

Merged in MS


Which database do you use?

Anyone happy to share which DB they find runs Gekko the fastest and has the least oddities?
For example with Gekko running on Windows Bash (to get talib working on Windows) I've had to set the Pragma journal_mode to "Del" rather than WAL....no idea why, but there we go.

Sqlite on raspbian creates multiple options on even a simple one week
import and have to choose between them when backtesting. Postgresql won't
go back to command prompt after a backtest,  you have to control-c out of
it.
On Apr 18, 2017 9:09 AM, "thegamecat"<EMAIL_ADDRESS>wrote:

Anyone happy to share which DB they find runs Gekko the fastest and has
the least oddities?
For example with Gekko running on Windows Bash (to get talib working on
Windows) I've had to set the Pragma journal_mode to "Del" rather than
WAL....no idea why, but there we go.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/askmike/gekko/issues/699, or mute the thread
https://github.com/notifications/unsubscribe-auth/ATXpPLotqETtHQjgy2wx3OaZSaS5ESJyks5rxMQEgaJpZM4NAZcO
.

Sqlite on raspbian creates multiple options on even a simple one week
import and have to choose between them when backtesting.

Not sure if this is the DB, what exchange is this? I will try to investigate!

When using poloniex  both problems with sqlite and postgresql prevent backtest from being ran and parsed by an external script or program for charting data analysis etc

Would you have a market and a date for such a gap? That way I can try to replicate.

What's the error?

The market was pink date was 2017-04-04 with sqlite

put that in #700. Will try to fix asap!

2017-04-18 11:18:53 (INFO):     Scanning local history for backtestable dateranges.2017-04-18 11:18:53 (DEBUG):    Available 19129 2017-04-18 11:18:53 (DEBUG):    Optimal 20356 2017-04-18 11:18:53 (INFO):     The database has 1228 candles missing, Figuring out which ones... 2017-04-18 11:18:53 (INFO):     Gekko detected multiple dateranges in the locally stored history. Please pick the daterange you are interested in testing: 2017-04-18 11:18:53 (INFO):                      OPTION 1: 2017-04-18 11:18:53 (INFO):              from: 2017-04-04 00:22:00 2017-04-18 11:18:53 (INFO):              to: 2017-04-16 08:22:00 2017-04-18 11:18:53 (INFO):                      OPTION 2: 2017-04-18 11:18:53 (INFO):              from: 2017-04-16 09:22:00 2017-04-18 11:18:53 (INFO):              to: 2017-04-16 10:22:00 2017-04-18 11:18:53 (INFO):                      OPTION 3: 2017-04-18 11:18:53 (INFO):              from: 2017-04-16 11:22:00 2017-04-18 11:18:53 (INFO):              to: 2017-04-16 12:22:00 2017-04-18 11:18:53 (INFO):                      OPTION 4: 2017-04-18 11:18:53 (INFO):              from: 2017-04-16 13:22:00 2017-04-18 11:18:53 (INFO):              to: 2017-04-16 14:22:00 2017-04-18 11:18:53 (INFO):                      OPTION 5: 2017-04-18 11:18:53 (INFO):              from: 2017-04-16 18:22:00 2017-04-18 11:18:53 (INFO):              to: 2017-04-16 19:22:00 2017-04-18 11:18:53 (INFO):                      OPTION 6: 2017-04-18 11:18:53 (INFO):              from: 2017-04-16 20:22:00 2017-04-18 11:18:53 (INFO):              to: 2017-04-16 21:22:00 prompt: option:

I switched to mongodb after i had problems (e.g. gaps in data) with sqlite.


Refactor agent: split code in subfunctions

towards  #1430,  #833 ...

I try to catch the issue (https://github.com/6543-forks/woodpecker/compare/refactor_agent...6543-forks:woodpecker:fix_cancle-status-overwride_WIP?expand=1)  but did not had success for now :/
at least now the logs of a killed pipeline are stored


ESET Protect Platform solution 3.0.0.

Required items, please complete
Change(s):

Add ESET Protect Platform solution 3.0.0.

Reason for Change(s):

New solution allows to send custom data to MS Sentinel.

Version Updated:
Testing Completed:

Yes

Checked that the validations are passing and have addressed any issues that are present:

Need Help

@microsoft-github-policy-service agree company="ESET, spol. s r.o."

Hello @eset-enterprise-integration, Could you please try to resolve CodeQL errors

Hello @v-prasadboke I will try to resolve CodeQL errors.
I am afraid that there are two issues with the changes you made in the function app zip files/dirs:

You removed the 'app' folder without updating the imports.
You changed the location of 'config.yml' without updating the code that loads this file (function get_config_params).

What is the reason for the changes you applied?
If those changes are necessary - could you please fix the mentioned issues: 1 & 2?
Is it intentional to store the config.yml file only in zip?

Hello @eset-enterprise-integration, I tried deploying the function app but it was failing due to access


Unable to resolve tsconfig.json.

I have a monorepo project, and its structure looks like this:
project
├── packages
│  ├── packageA
│  └── packageB
└── index.mjs

project/packages/packageA/index.ts:
// tsconfig alias
import app from '@/app';

// do something
// ...

project/index.mjs:
import { ESLint } from 'eslint';

const eslint = new ESLint({
    cwd: '/workspace/project/packages',
    extensions: ['.ts', '.tsx', '.mts', '.cts'],
});

const result = await eslint.lintFiles('/workspace/project/packages/packageA/index.ts');

console.log('result---', result);

Run index.mjs in root directory path:
node /workspace/project/index.mjs

And ESLint will give an error message like this:

If I run index.mjs in the packageA path instead of the root directory, there is no problem:
cd /workspace/project/packages/packageA
node /workspace/project/index.mjs

I tried adding tsconfigRootDir to be able to find the tsconfig.json file:
new ESLint({
    cwd: '/workspace/project/packages',
    extensions: ['.ts', '.tsx', '.mts', '.cts'],
    overrideConfig: {
      parserOptions: {
        tsconfigRootDir: '/workspace/project/packages/packageA'
      },
    },
  })

But it doesn't seem to work...
Here is some debugging information:

Sorry, I thought tsconfig.json would be searched based on the cwd of eslint. After reading the documentation, I found that tsconfig.json is based on the project configuration of import/resolver. The problem has been solved.


Adds asynchronous search plugin's main branch to 1.2 manifest

Signed-off-by: Surya Nistala<EMAIL_ADDRESS>Description
Adds asynchronous search plugin's main branch to 1.2 build manifest
Issues Resolved
https://github.com/opensearch-project/asynchronous-search/issues/42
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@gaiksaya @dblock Can you plz review this.

Codecov Report

Merging #854 (c983cb3) into main (3787942) will decrease coverage by 0.22%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #854      +/-   ##
==========================================
- Coverage   91.60%   91.37%   -0.23%
==========================================
  Files          81       81
  Lines        2250     2250
==========================================
- Hits         2061     2056       -5
- Misses        189      194       +5

Impacted Files
Coverage Δ

src/system/temporary_directory.py
82.75% <0.00%> (-13.80%)
:arrow_down:

src/system/os.py
92.30% <0.00%> (-7.70%)
:arrow_down:

Continue to review full report at Codecov.

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

Reverting in https://github.com/opensearch-project/opensearch-build/pull/876 because of #864.


HSEARCH-2906 Unable to extend NumericFieldBridge

https://hibernate.atlassian.net//browse/HSEARCH-2906

thanks! merged


Add androidLayerType as prop

Summary
This PR is to add a new React prop, androidLayerType, that allows setting the layer type for Android using props. It also deprecates androidHardwareAccelerationDisabled prop, as the use of both of them at the same time might cause undefined behaviour.
Motivation:
The general motivation is to be able to control the layer type through props.
It would also solve the problem of rendering big pieces of HTML in a WebView when the hardware acceleration is disabled.
When we use HA, all drawing operations that are performed on a View's canvas use the GPU, so the layer is set to LAYER_TYPE_HARDWARE. Disabling HA means setting the view to LAYER_TYPE_SOFTWARE, which uses a drawing cache with a specific amount of available memory. If we want to render big pieces of HTML, they might not fit in memory and so they won't be displayed. The problem can be solved by using LAYER_TYPE_NONE, meaning the view is not backed-up by any buffers.

Test Plan
Tested in my app by linking my fork to it. Worked as expected.

Compatibility

OS
Implemented

iOS
❌

Android
✅

Checklist

[X] I have tested this on a device and a simulator
[ ] I added the documentation in README.md
[ ] I mentioned this change in CHANGELOG.md
[X] I updated the typed files (TS and Flow)
[ ] I added a sample use of the API in the example project (example/App.js)

Hey @Titozzz, any chance I could have a review for this any time soon? :)
I think the tests should be rerun, but I can't do that. The failed tests don't seem related to my changes


--bash: argo-cli: command not found

Summary
What happened/what you expected to happen?
Installing argo for mac in my macOS Moneterey (M1), and it failed. The error is: --bash: argo-cli: command not found
I believe this command:
# Move binary to path
mv ./argo-darwin-amd64 /usr/local/bin/argo

Should be:
# Move binary to path
mv ./argo-darwin-amd64 /usr/local/bin/argo-cli

After changing the binary file name it worked.
What version of Argo Workflows are you running?
v3.2.6

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

This was a login bash alias that was causing the issue.


"You don't have permissions to add Hello World to this team."

When I click Install under Test and Distribute, this is what I see:

The dialog UI appears to have changed since this tutorial was written, so I'm not quite sure of the issue. There is no option for "Add for you", nor is there even a place to search for a team. "This team" implies that I chose a team, but I didn't.

@norachuga Are you trying to upload the app from App Studio? Could you please try downloading the manifest and sideload it?

There is no option for "Add for you", nor is there even a place to search for a team

Clicking on Add directly adds the app in your personal scope. If you want to add the app to a team, you could choose "Add to a team" from the dropdown and you will get an option to search for the team you want to add the app to.

Yes, I was trying to add through the Apps Studio.
My UI does not match what is shown in the sideload doc either, and I do not have the options it offers.
In the first option, there is not a Store icon. Instead, it says Apps (as well as Help instead of a Feedback option). As you can also see, there is no "Upload a custom app" option.

The screenshot is from the desktop app (<IP_ADDRESS>774), but the same is true of the webapp as well.
In the second option, there is no "Upload a custom app" option on the Apps tab either.

@norachuga Could you please check if Sideloading is enabled in Setup Policies?

Please follow this document to enable sideloading if you haven't done it already.

There appears to be a very long delay between enabling/disabling "Allow uploading custom apps" and the functionality appearing/disappearing.
The features eventually showed up with no further action from myself, but I did not keep track of how long it took. It could be more than a day.
I have now disabled sideloading, but the features remain completely available. It has been 2 hours since I disabled it, and I was still able to upload a new custom app, as well as update an existing one.
I have made note of when I disabled it and will be keeping an eye on it. I will update when it actually becomes disabled.

It seems that the features appear to appear/disappear at different rates from each other as well.
6 hours after disabling:

Teams > Apps tab - Upload a custom app option is no longer visible
App Studio > Test and Distribute > Install > Add is disabled

23 hours after disabling:

Apps > Upload a custom app is still available. I was able to upload a new app using it.

@norachuga App setup policies usually take some time to update. Were you able to add the app to the Team? Is your issue resolved?

Sure, I guess my issue is resolved.
I feel like it should probably be made clear on any or all of these pages that it takes more than entire day for a change in settings to take effect. Otherwise, a reasonable person would assume the documents are wrong, they have done something wrong, or there was a bug.
https://docs.microsoft.com/en-us/microsoftteams/platform/get-started/get-started-dotnet-app-studio
https://docs.microsoft.com/en-us/microsoftteams/platform/get-started/get-started-configure-teams
https://docs.microsoft.com/en-us/microsoftteams/platform/get-started/get-started-tenant

@norachuga Thanks for the feedback!

Same problem here

I have same issue and tried to enable Sideloading in Setup Policies. However the toggle button is disabled in the "First Line Worker" policy section. I am logged in with tenant admin credentials.
(I was able to to enable the upload custom apps to ON for "Global (Org-wide default)" policies).
Am I missing something here? please guide. Thank you.

Maybe someone will help this link.
https://techcommunity.microsoft.com/t5/teams-developer/you-don-t-have-permissions-to-add-for-adding-a-bot/m-p/918612

When I click Install under Test and Distribute, this is what I see:

The dialog UI appears to have changed since this tutorial was written, so I'm not quite sure of the issue. There is no option for "Add for you", nor is there even a place to search for a team. "This team" implies that I chose a team, but I didn't.

For following a tutorial , this is way too involved, not sure why a walkthrough would be posted without vetting that it's working properly

I am having the same message "you don't have permissions to add MyApp to this teams". I have system administrator role. I have created a policy with "Upload custom apps" turned on and wait for about half day and still I am having the same issue. Some advise please. Thanks.

Im having this issue too.

I have the same problem

Same here..

I'm having the same issue.

Please how do you watch the live sessions?


Optimize the canMatch phase on the data node

Description
Two changes here:

short circuit can match check, respond with CanMatchResponse(false, null) if cannot match(minMax value is useless if corresponding shard is not match);
only primary searchAfter field will be evaluated if exists.

Related Issues
Resolves #[Issue number to be closed when this PR is merged]

Check List

[x] Functionality includes testing.
[x] API changes companion pull request created, if applicable.
[x] Public documentation issue/PR created, if applicable.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Is there any way to quantify the impact of this change? Also, are the existing tests sufficient to catch any regressions?

No, this optimization is just for reducing unnecessary computation or IO. Currently, I am unable to accurately measure the impact of this change.

If not, can we add test cases for the missing code paths?

Sure.

@jainankitk friendly ping

@bugmakerrrrrr - While the changes look okay, I am still unsure about the impact and need of this code change. Even if not using some benchmark, having some idea of potential improvement with this change will be good!

Also can you add entry in CHANGELOG.md, before this change can be reviewed by maintainer and merged!

@bugmakerrrrrr - Can you resolve the failing CHANGELOG verifier and codecov check while one of the maintainer reviews this PR?


Assignee gets removed

See CAL-729

Still happening for @Jaibles - see CAL-922

Found and fixed a potential problem here @Jaibles. Can you replicate the assignee loop?


Mark log output from BuildOperations with the task that generated it

Blocks #1610 — with the removal of task execution logging in the main area, users need to get some additional context when warnings or errors occur.
User Visible Changes
Logs from any given build operation are buffered and output all at once upon completion of the operation.
Before:
:util:compileJava
Note: Some input files use unchecked or unsafe operations.
Log message from build logic
:util:compileJava
Note: Recompile with -Xlint:unchecked for details.

After:
[:util:compileJava]
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

[task execution listener]
Log message from build logic

Implementation
Generalize what the TaskExecutionLogger does and apply it to all BuildOperations that generate output. We should buffer the output for a build operation until the end (if attached to a Terminal).
Test Coverage

Log messages are flushed upon failure of a build operation
Log messages are flushed if build is stopped prematurely (via user command or process kill)
Log messages are only output after operation completes

With the introduction of the "parallel by default" API that @ghale is working on, this is even more important. It will allow tasks to run concurrently (e.g. one task is waiting for background work to complete, while another starts snapshotting its inputs). This means that their output could be interleaved. This is already a problem with --parallel today, but will now also affect builds without --parallel.

Some discussion on Slack.

I looked at this a bit more as part of trying to get BuildOperation working with the console. I was able to hack together two branches that forward all BuildOperation to the console and that attach an OperationIdentifier to all logs. Both solutions are hideous and need cleaning which is the reason for this comment. Here are the open questions:

To attach OperationIdentifier to each log, we require access to the current running ProgressLogger. Exposing it through the ProgressLoggerFactory interface leads to passing the factory to lots of separate places. It's also not possible to pass a reference to the factory in some code path as they are statically constructed. The question is around how we can pass the OperationIdentifier around to all log generating classes? Note that this problem also exists with raw BuildOperation as we need to attach the id to the generated logs (e.g. System.out, System.err).
The worker process has some added complexity. The thread receiving the log events isn't the thread that started the BuildOperation (and, by definition, ProgressLogger). The OperationIdentifier isn't accessible. To access it, you need to jump through some hoops. It's more complicated when the worker process is reused. We could use a general solution if the worker process could know his OperationIdentifier.

For issue 1, we could have a registry that contains the OperationIdentifier for all thread. We could pass around this lightweight object around and access a singleton reference where we can't pass a reference.
For issue 2, we could pass the OperationIdentifier to the worker process and set it in the registry so that all log generated code can retrieve it and attach it on the log.
I would appreciate suggestions on other solutions for those two issues.

This is also addressed in #1855


Fixing wrong css selector

A dot is missing in the ui css, here the fix 🤓

Released in https://github.com/joeldenning/import-map-overrides/releases/tag/v2.3.2


Add Meetings pages for annual workshops and other CF related meetings.

@davidhassell and @erget  - Here's a PR for the Meetings pages we discussed in Thursday's call. For the 2020 Workshop page, I mostly just pulled the text from your draft announcement.
I made it a sub-directory (thought about sub-dirs for each year, maybe later if we need them) but I'm not sure I got the navigation stuff right. I tried to follow the patterns I found but don't have Jekyll setup to run locally so haven't tested that it will build properly. I guess Travis builds on PRs and we can see success or failure but not sure we can look at resulting pages.

@davidhassell I fiddled with this and failed - something's up with the build system and the best I could do was undo my own damage by reverting my commits :D Could you have a look? There's lots of files in the branches that the build process goes down to that I think would need updating in order to get it to build properly, but I couldn't find the proper way to do that and am pressed for time today.

The PR looks good to me. (I'm afraid that I have absolutely no time for looking at the build stuff today, as I'm not in the office.)

Thank you, David. Who is able to merge in this repo? Yes, I noticed the build problem too. I don't see how I could have caused it.

Sorry, my comment was actually referring to David's on my pull request, but the same applies about the build problem.

@JonathanGregory I could merge this request, however it's not building so I think something's broken. Unfortunately I'm in briefings all day today so I haven't had a chance to investigate it further. My best guess is that it has something to do with changes made during the publishing process of 1.8, as when this is pushed it tries to build the 1.8 documentation and fails. It looks like some build assets need to be copied and adapted to 1.8 before this will succeed, but as I'm not familiar with that part of the build system I prefer not to touch it while I'm not able to investigate more closely.

In cf-convention.github.io/Data/cf-conventions/cf-conventions-1.7/ there are many files, notably a makefile, which look like they are used for automatically building documents.  In another branch, add-build-tools-1.8, I copied them to Data/cf-conventions/cf-conventions-1.8/.  There are two directories (besides xxl/) which look like they are only for working data.  I did not copy them  I haven't tried to see whether all this will help; I will look at that tomorrow if possible..

Hi @painter1 - thanks for looking at this. I fiddled with this as well and was able to get the build to work, but instead of deploying 1.8 as the latest document it deployed 1.7, so I reverted the commits. It'd be worthwhile to understand and document the build system and I'd be willing to contribute to that later on this year. This week unfortunately I'm pretty swamped.


Sort SKU List Items by position attribute

Closes @commercelayer/issues-app#97

What I did

I refactorized the SkuListProvider and some other helpers to avoid the usage of include of has_many relationships according to new internal policies
I fixed the sorting of sku_list_items to sort them by position ascending

Notes
Having splitted the included relationships into separate requests could lead into pagination issues. At the moment I did not managed any pagination for sku_list_items because they seem to be limited to 12 by business logic. Instead I paginated the results of skus and prices. Eventually we could set a custom maximum amount of pages that we want to fetch.
Checklist

[x] Make sure your changes are tested (stories and/or unit, integration, or end-to-end tests).
[ ] Make sure to add/update documentation regarding your changes.

Hello, is there any update on this? Is there any way I could help?

Hello, is there any update on this? Is there any way I could help?

Hi!
I am going to close this PR, since this has been solved here and will be released soon:
https://github.com/commercelayer/mfe-microstore/pull/64


canca

enhrebtn[oerno[

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a0047ac3-d92a-dcb0-18ba-a0a8db2331db
Version Independent ID: 8a479a1b-f3c8-a627-97a8-3d9e1f8573ee
Content: Time Picker - Xamarin
Content Source: docs/android/user-interface/controls/pickers/time-picker.md
Product: xamarin
GitHub Login: @mgmclemore
Microsoft Alias: mamcle

Hi @Veinder55: perhaps you opened this in error (not sure what enhrebtn[oerno[ means)? Closing -- please reopen if you need to re-comment. Thanks!


Make local lambda server configurable

Motivation
We want to be able to mock different aws service behaviors with the Lambda.LocalServer.
Changes

The Lambda.LocalServer now opens two ports: One for incoming requests (InvokeHandler) and one for the control plane API (ControlPlaneHandler)
The ServerState (please hand me ideas for better names) encapsulates all the "business" logic: Queueing incoming requests, ensuring control plane state, ...
The user can implement the LocalLambdaInvocationProxy protocol to mock the behavior of different aws services
a default InvokeProxy is included
The server has been moved to the AWSLambdaTesting target, since we want to be able to access AWSLambdaEvents, if we implement an APIGatewayV2Proxy

what is the status of this PR? It would be useful to have it...

@pokryfka the work on this pr has stopped, since we chose to go a different route with configuring the LocalServer. Since the LocalServer is now automatically started if the ENV variable is set, we need to find a different way. One idea is to provide a bootstrap method like in swift-logging to configure the LocalServer before actual startup. Does this make sense?

@pokryfka the work on this pr has stopped, since we chose to go a different route with configuring the LocalServer. Since the LocalServer is now automatically started if the ENV variable is set, we need to find a different way. One idea is to provide a bootstrap method like in swift-logging to configure the LocalServer before actual startup. Does this make sense?

So the bootstrap function (static method) and LocalLambdaInvocationProxy protocol would be public and remain in AWSLambdaRuntimeCore, something like:
public protocol LocalLambdaInvocationProxy {
 // ...
}

public enum LocalLambda {
    public static func bootstrap(_ proxyType: LocalLambdaInvocationProxy.Type) {
      // ...
    }
}

Now APIGatewayV2Proxy depends on AWSLambdaEvents and needs JSON encoder and decoder. It would be defined in AWSLambdaTesting.
Then if user wants to mock API Gateway he would need to import AWSLambdaTesting (?):
#if DEBUG
import AWSLambdaTesting

LocalLambda.bootstrap(APIGatewayV2Proxy.self)
#endif

// this will run LocalLambda.Server if DEBUG and LOCAL_LAMBDA_SERVER_ENABLED is "true"
Lambda.run(APIGatewayProxyLambda())

@fabianfett is that what you had in mind?
on top of that, it would probably be convenient to have a few proxies (API Gateway V1 and V2) defined (in AWSLambdaRuntime?) and configurable using env variable:
 LOCAL_LAMBDA_SERVER_PROXY_TYPE=invoke // or api, api2

I just noticed MockLambdaServer and HTTPHandler in LambdaRuntimeClientTest look very much the same as the LocalLambda:Server and LocalLambdaInvocationProxy is almost the same as LambdaServerBehavior (with one using NIO future and the other Result).
Perhaps one more advantage of the approach in the PR could be (a possibility of) an implementation of a MockProxy used in tests instead of MockLambdaServer which in turn would make the local lambda server better tested.
public protocol LocalLambdaInvocationProxy {
     init(eventLoop: EventLoop)

      /// throws HTTPError
     func invocation(from request: HTTPRequest) -> EventLoopFuture<ByteBuffer>
     func processResult(_ result: ByteBuffer?) -> EventLoopFuture<HTTPResponse>
     func processError(_ error: ByteBuffer?) -> EventLoopFuture<HTTPResponse>
 }

 internal protocol LambdaServerBehavior {
     func getInvocation() -> GetInvocationResult
     func processResponse(requestId: String, response: String?) -> Result<Void, ProcessResponseError>
     func processError(requestId: String, error: ErrorResponse) -> Result<Void, ProcessErrorError>
     func processInitError(error: ErrorResponse) -> Result<Void, ProcessErrorError>
 }

Perhaps one more advantage of the approach in the PR could be (a possibility of) an implementation of a MockProxy used in tests instead of MockLambdaServer which in turn would make the local lambda server better tested.

I really like this approach. imo the priority is:

come up with a good system to inject middleware for LocalLambda:Server to ore easily test scenarios like API Gateway.
refactor the testing the facilities to use LocalLambda:Server instead of MockLambdaServer

@pokryfka @fabianfett wdyt?

@fabianfett what are your thoughts on that?
I could help with that and:

sync the branch with master,
create static LocalLambda.bootstrap function as described above
implement APIGatewayProxyLambda  using APIGatewayMapping from https://github.com/swift-server/swift-aws-lambda-runtime/pull/138

@pokryfka I'd excited if you could help out here. Go ahead! Maybe we should try to split the changes in small prs so we don't end up with such a big one like the one we have here.

@fabianfett @tomerd please check the change on https://github.com/swift-server/swift-aws-lambda-runtime/pull/138
(I dont think I could push to feature/ff-local-invoke-configurable and It would probably not make sense to make a PR to a branch which is not in sync with master?)

@fabianfett could you please update this PR to be against the main branch so we can delete the old master branch

closing in inactive PRs, feel free to re-open if still relevant


when I return a page directly, this.props.navigation is does't work

in root.js

in Index.js

Is it because you put "dataVlaue" instead of "dataValue" in the second image?

@zckly I corrected，but it does't work

Can you confirm that this.props.navigation isn't undefined in root.js? When you say it doesn't work are you seeing an error or is it just not doing anything?

@spencercarli that's it, in root.js I import react-navigation, and init a StackNavigator, all pages in this StackNav like this

in render method I return  directly, but  in Index page alert the 'navigation' is undefined

Can you try to put together a reproduction on Snack? Without it I'm struggling to see what the issue could be, other than the typo previously pointed out.

Index.js.zip
root.js.zip
@spencercarli they are my source code profile

Index.js.zip
root.js.zip
@spencercarli they are my source code file

Hi! In an effort to get the hundreds of issues on this repo under control I'm closing issues tagged as questions. Please don't take this personally - it's simply something we need to do to get the issues to a manageable point. If you still have a question I encourage you to re-read the docs, ask on StackOverflow, or ask on the #react-navigation Reactiflux channel. Thank you!


Add support for extending head block on dashboard

By default, Block::put('key') & Block::endPut() defaults to overwriting instead of appending.
This change means calls to Block::append('head', $content) will function correctly for the dashboard.

The endPut() method was changed to accept a boolean parameter.
If the value of this parameter is true, then it will render the block immediately instead of waiting for all blocks to be rendered at once in Block::end().

Bad bot


Better support for nested inference with SVI

The internals of our SVI code need a bit of cleanup to better support nesting SVI inside other inference algorithms, a necessary component of several projects including contrib.oed.
Tasks:

[ ] Make infer.SVI a TracePosterior instance again so that it works with EmpiricalMarginal and can be interchanged with other methods like MCMC
[ ] Split side effect-free differentiable_loss methods, which would only compute surrogate losses, out of the various *ELBO.loss_and_grads methods, which both compute surrogate losses and call backward, so that gradients aren't computed twice in SVI.step when using pyro.optim.multi.PyroMultiOptimizer.  Related: #628
[ ] Have step update the parameter store with new values instead of updating parameter tensors in place as pyro.optim.PyroOptim optimizers do

Note regarding #628 and https://forum.pyro.ai/t/checkpoint-in-pyro/303:
There are some disadvantages of using grad instead of .backward() (at least in Trace_ELBO):

grad has less jit support at the moment
grad has no checkpointing support at the moment
grad is slightly more expensive for tiny tensors (since it traverses the graph twice)

However these are minor and could be outweighed by code simplification.


Add installation instructions for m4 on mac

Problem
Building on MacOS failed due to missing m4. Although a window was popping up claiming to install m4, this was not helping.
Summary of changes
Add instructions to install m4 using brew and link it (thanks to Folke for helping).

Thanks, VS Code sometimes adds this :(. Fixed.

LGTM -- @davidgomes also added this in one of his PR, anyways, we can get this merged first

Just merge this, I will rebase and fix conflicts because my PR will take a while to get merged.

m4 comes with command line tools (CLT, installed via xcode-select --install), @stradig / @davidgomes could you guys share your brew config output (it shows which CLT version is installed)

It didn't for me, for sure. Anyway, here's my brew config output:
HOMEBREW_VERSION: 4.3.19
ORIGIN: https://github.com/Homebrew/brew
HEAD: 1f9bd2de89883ec9a59db3eab0f5475bce06d5bc
Last commit: 3 days ago
Core tap JSON: 05 Sep 14:13 UTC
Core cask tap JSON: 05 Sep 14:13 UTC
HOMEBREW_PREFIX: /opt/homebrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_MAKE_JOBS: 11
Homebrew Ruby: 3.3.4 => /opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/bin/ruby
CPU: 11-core 64-bit arm_lobos
Clang: 15.0.0 build 1500
Git: 2.45.2 => /opt/homebrew/bin/git
Curl: 8.6.0 => /usr/bin/curl
macOS: 14.5-arm64
CLT: <IP_ADDRESS>.1.1708646388
Xcode: N/A
Rosetta 2: false

m4 comes with command line tools (CLT, installed via xcode-select --install), @stradig / @davidgomes could you guys share your brew config output (it shows which CLT version is installed)

No, it's a known issue for a few months now and Apple is working on a fix supposedly. https://github.com/Homebrew/homebrew-core/issues/165388#issuecomment-2029794821
I wonder if they initially did that because of M4 branding.

Thanks!
Here is my output
HOMEBREW_VERSION: 4.3.19
ORIGIN: https://github.com/Homebrew/brew
HEAD: 1f9bd2de89883ec9a59db3eab0f5475bce06d5bc
Last commit: 3 days ago
Core tap JSON: 05 Sep 13:16 UTC
Core cask tap JSON: 05 Sep 13:16 UTC
HOMEBREW_PREFIX: /opt/homebrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_MAKE_JOBS: 12
Homebrew Ruby: 3.3.4 => /opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/bin/ruby
CPU: dodeca-core 64-bit arm_lobos
Clang: 15.0.0 build 1500
Git: 2.39.3 => /Library/Developer/CommandLineTools/usr/bin/git
Curl: 8.7.1 => /usr/bin/curl
macOS: 14.6.1-arm64
CLT: <IP_ADDRESS>.1.1708646388
Xcode: N/A
Rosetta 2: false

m4 comes with command line tools (CLT, installed via xcode-select --install), @stradig / @davidgomes could you guys share your brew config output (it shows which CLT version is installed)

No, it's a known issue for a few months now and Apple is working on a fix supposedly. https://github.com/Homebrew/homebrew-core/issues/165388#issuecomment-2029794821 I wonder if they initially did that because of M4 branding.

Thanks for the link!
My knowledge was outdated 😅


Bug: Kafka records are lost when an exception happens while being processed by SolRecordProcessorIF

Description of the bug
Currently, the SolaceSinkSender catches any exception thrown by a call to SolRecordProcessorIF#processRecord leading to data-loss.
https://github.com/SolaceProducts/pubsubplus-connector-kafka-sink/blob/29abade80dd0d359b8e51b43bd6b1a584d2abb62/src/main/java/com/solace/connector/kafka/connect/sink/SolaceSinkSender.java#L128-L140
Expected behavior
By default, the SolaceSinkSender should adopt a fail-fast strategy by rethrowing exceptions thrown by the configured SolRecordProcessorIF.
Ideally, it should be possible to configure a global config property (e.g., halt.on.error) to indicate if the the task should halt when it encounters an error or continue to the next record. By default, the connector should be safe so the default value for this property should true.

Hi @Nephery, I don't think the RetriableException mechanism is suitable for handling exceptions from the SolRecordProcessorIF.  In fact, if the configured implementation fails to handle a record, there is a high probability that it is due to a bug or an invalid/corrupted input record. In any case, it will not be possible to retry to process the record.
Even, if it seems to be OK to use the built-in errors.tolerance=all mechanism to skip bad records will should keep in mind this strategy will apply to all the exceptions thrown from the SinkTask#put() method. Thus, we will also skip records, for example, due to a connection lost with Solace. Maybe, the new halt.on.error property should be named halt.on.process.error because this property will only be used to ignore exception thrown by the SolRecordProcessorIF.
Also, using halt.on.process.error=false will still allow using the Kafka Connect error tolerance mechanism.


Nothing happening and 'forEach' error on using instance.check()

Installed the plugin through npm i --save layzr.js
In my app.js file i include the module like so
import Layzr from 'layzr.js'
const lazy = Layzr()
lazy.check()

When I added the lazy.check() the following error popped up:
Uncaught TypeError: Cannot read property 'forEach' of undefined
    at Object.check (eval at ../node_modules/layzr.js/dist/layzr.module.js (bundle.js:761), <anonymous>:186:10)

in my index.php I have images like so:
<img data-normal="test.jpg">
I'm using Webpack 2.2.0

Had to do something with my paths of which the views where served

const lazy = Layzr()

lazy
    .update()
    .check()

in this way?


Make sure tfutils is python 3.5 compatible

Haven't examined this at all.

what's the right test suite for me to run to deal with this?

I think the most correct thing to do is to have the tests compatible in python 3.5 as well.

@chengxuz in doing this I'm finding the error
ModuleNotFoundError: No module named 'easy_batch_allreduce'
this has something to do with faster multi_gpu stuff I think.  What's going on?

Here's the full error trace
Traceback (most recent call last):
File "test_base.py", line 30, in
import tfutils.base as base
File "/home/yamins/tfutils/tfutils/base.py", line 10, in
from tfutils.train import train_from_params
File "/home/yamins/tfutils/tfutils/train.py", line 13, in
import tfutils.utils as utils
File "/home/yamins/tfutils/tfutils/utils.py", line 20, in
from tfutils.multi_gpu.easy_variable_mgr import
File "/home/yamins/tfutils/tfutils/multi_gpu/easy_variable_mgr.py", line 11, in
import easy_batch_allreduce as batch_allreduce
ModuleNotFoundError: No module named 'easy_batch_allreduce'

this is a genuine python3 compatibility issue am working on it

@chengxuz @damro (or anyone) does anyone object to my making six a requirement of tfutils?  It enables python2-and-3 compatible checking of stuff like string types

@chengxuz in db_interface.py around line 131 there's an assignment:
total0 = None

Later, around line 144 we call
  range(total0)

This will error out in python2 or 3 unless total0 is reset in the for loop starting "for f in notindexfiles".
Is it guaranteed that this loop be executed (e.g. that notindexfiles be nonempty)?

Hmm, I don't fully know the purpose or logic of this function. But based on my reading, it cannot be guaranteed that notindexfiles is nonempty.

@damro @chengxuz can you guys test my PR on this and merge if ready?


Preview(s) of Coq between official releases?

For discussion of @MSoegtropIMC's comment in #14354

Maybe I should do a monthly best pick preview Coq Platform. For me it is quite hard to test all the debugger enhancements from @jfehrle in my daily work, because I need so much stuff to compile, which usually doesn't compile right at the spot I want to test it.

We could also consider creating preview branches for code changes for which we'd like more user feedback. They could omit any incompatible code changes that go into master meant for the next release.

For some features, that might be doable, especially if they are merged early into the release cycle, while for some others it might be more difficult to extract them without the earlier backward-incompatible changes. That being said, it might be worthwhile to do both (monthly snapshots and feature previews).

But all in all this must be something living in the extra-dev branch of the Coq opam repo, so that it is easily installable. I rather imaging that one creates preview version packages and sets these to s specific commit and updates these opam packages as needed. Even tracking a dedicated feature branch is likely not appropriate, because this also might sometimes work and sometimes not - unless one considers to have release branches of feature branches ...

How would you write the version numbers for all these packages?

This needs to be discussed, but I would say that these packages should be deleted after a release, so that it shouldn't get too bad.

OK, if eventual deletion is in order, then an idea would be to use a .dev version scheme which points to a commit that is manually updated instead of pointing to a branch. That way, we guarantee that the package set is compatible together at any point, however, we do allow for updates.

@jfehrle : one can point an opam package to any commit - potentially even on a fork. So e.g. in case of a debugger preview, it could be a commit or even a tag of a branch on your fork.
@Zimmi48 : regarding naming: I guess it could be ~feat-xyz for a preview of feature xyz and ~prev-mm for a preview of month mm.

potentially even on a fork. So e.g. in case of a debugger preview, it could be a commit or even a tag of a branch on your fork.

It could point to a jfehrle fork of elpi, for example?  That would make it pretty simple for the debugger example.
For monthly releases from master, you might be forced to use the latest version of the package (incorporating merged overlays since the last Coq release), which may be less stable.

It could point to a jfehrle fork of elpi, for example? That would make it pretty simple for the debugger example.

Not sure what elpi has to do with it, but I don't see a good reason for not providing feature preview opam packages in extra-dev, which point to forks, as long as it is ensured that nobody gets such a package without explicitly asking for it, which is mostly a question of package version naming.
I think one has to ensure that all feature preview packages have a version which is "older" than "dev". Unfortunately I don't see a way to avoid that opam would upgrade from one feature to another because the name of the other feature is "newer" in terms of version ordering, but I think this is OK, if one knows it.

I assumed you were familiar with the overlay mechanism used in CI, which is described here.
coq/coq/pull/14354 has this breaking change to loc.mli:

so elpi won't compile with coq/coq/pull/14354 in Coq without the overlay PR LPCIC/coq-elpi/pull/248.
You think there's a way to include the elpi patch in opam without affecting users who want to stay on the official release?  The switch mechanism and the "pinning" mechanism look promising, maybe that's what you had in mind?

@jfehrle : I know the overlay mechanism, but I was not aware that the debugger has changes affecting elpi.
One could e.g. create in the opam extra-dev repo a patched elpi opam package (say elpi.overlay-pr14345) and state in the opam file that this version is compatible with your specific version of coq, but no other. Since elpi.overlay is "newer" than elpi.dev according to opam's version comparison rules, it would pick this elpi version for your coq. For other coq.dev versions it would still pick elpi.dev, since the elpi.overlay package explicitly says that it is only compatible with your branch of coq.
So the trick would be to have an "overlay version space" which is always newer than the "dev version space" and overlay versions always require a specific patch version of coq.
The downside is that if someone already has elpi.dev installed, it would keep it. One can either live with this - I guess people trying this anyway would always create a fresh opam switch - or find a way to state that your version of coq is incompatible with the normal dev version of elpi without requiring it (not sure if this is possible).
Another option would be that you simply require this version of elpi in your version of Coq. The downside of this would be that elpi would always be installed, but one could be sure that it is the correct version.
So yes, there are ways of doing this, and indeed I think supplying such packages would bring us forward. If you want, I can create such packages as a test (independent of Coq platform).

If we're not sure of the behavior, then testing is a good idea.  Unless you're especially eager, I think we could wait 3-4 weeks before trying to create a debugger preview, which will give me time to add some additional essential features to the debugger (e.g. display of the stack and variable values).

I am sure of the behavior, but I am not sure what behavior users would appreciate most. Of cause this also needs testing. 3-4 weeks fits my timeline well.

I think with the multi-version support it is sufficiently easy to create preview releases by supplying an additional pick. I also plan to have besides the dev pick a "coqci" pick which mimics coqci and should be more stable than dev, but in a later release.


calling convention / ABI

Calling convention ABI support required for better static type / dataflow through function calls.

Fixed in development.


manual: drop grsecurity documentation for 17.09

Issue description
Since grsecurity is no longer supported, the documentation should probably be dropped for the most part (except, perhaps, for the existing note explaining that it has been dropped and why), I think this is important-ish to get done for 17.09.
I'm happy to do the PR if there's a consensus on how this should be handled, or anyone who's confident about this (was there a maintainer for grsec in NixOS?) has my blessing to do so directly :).

I intend to purge all grsec bits for the release.


Separate breaking changes from other changelog sections

Description
Pass breaking changes to components in a separate list to the changelog.
Use cases

Allows breaking changes to be more easily displayed using a separate component, e.g. breaking changes in a list but the changelog in a table.

Possible implementation
Remove the breaking section from the changelog and give it to components as a separate list. Internally it can remain within the changelog dictionary.

No updates yet, still in the backlog, open for help from the community.

This has been templated for v10 default changelog. Stay tuned.

Almost ready to be released, hopefully later this week.

:tada: This issue has been resolved in version 9.15.0 :tada:
The release is available on:

PyPi package
GitHub release


All-encompassing QR code scanner

So that QR code scanner can be available in various screens and "jump" to the right screen depending on what is scanned instead of the ones we have now which only allows users to scan what is supported in the current screen.
Let’s make the scanner functionality configurable with options - for handling EIP681, WalletConnect etc -, mirroring how UIImagePickerController allows us to choose from photo, library, all, etc.
There’s a Zeplin screen which has the button, but let’s assume it’s a button available in the Wallets tab navigation bar (because: see Out of Scope below).
Out of scope
—-
When this is available, we should probably also make it available in the quick action list accessibly by tapping and holding the app icon in the iOS home screen.

Possible dup of #1214

https://github.com/AlphaWallet/alpha-wallet-ios/issues/1738
Dup?

@hboon  As i undarstand right, for this task i need update QRCodeReaderViewController add there my qr button. Right? but what the next? as i undarstand right if user tap my qr button it will start Wallet Connect client's session to get URL to connect.  What else i need to do here?

Oh. No. This is to add a button eg like the wallet tab. Tap the button and the QR scanner appears. If we scan an EIP681 payment link, go to the send screen, prefilled (like scanning the QR code in the send screen which you worked on recently). Or scan something else and another appropriate screen appear.
If you added My QR button, that’s fine too as a separate PR (I think you pushed that). But that’s another issue. We might have that issue somewhere I think.
Makes sense?

EIP681

Got it. Also i have a few questions:
what should happen when we tap on each action from didScanQRCode alert?
https://user-images.githubusercontent.com/51817359/75242825-19bbc300-57c9-11ea-862d-cf5e688b8aed.png
as i undastand when we tap it opens send token screen
but what should happens when we tap on watch, i need manually add it through keystore.importWallet(type: importType)
or show import wallet screen and fill it with scanned qr code?
also what should happen when we tap on add to address book?

Oh, I forgot to link to #1738. You can refer to it :) Would you verify if the flows are correct?

Oh, I forgot to link to #1738. You can refer to it :) Would you verify if the flows are correct?

@hboon i already added ability to watch wallet and open URL, now i want to work on "select asset" flow. do i need to add it in current PR, or it will be in separate one?

also i am not able to open this link
https://drive.google.com/a/alphawallet.com/file/d/14ge8G3pIM513myKZbDrUyjA2bvRGzFXR/view?usp=sharing

Oh, I forgot to link to #1738. You can refer to it :) Would you verify if the flows are correct?

@hboon i already added ability to watch wallet and open URL, now i want to work on "select asset" flow. do i need to add it in current PR, or it will be in separate one?

Up to you, if you think the entire PR including the flow wouldn't touch too many files (and thus hard to merge, especially if we don't merge it quickly) then you can build it together if you like.
Otherwise you can break it up and we can just disable the new QR scanner button first and merge the rest in (with some of the other functionality still complete, though not exposed to the user).

also i am not able to open this link
https://drive.google.com/a/alphawallet.com/file/d/14ge8G3pIM513myKZbDrUyjA2bvRGzFXR/view?usp=sharing

There you go: QR_Code_Scanner.pdf

QR_Code_Scanner.pdf

thx!

@hboon one more question
how could i determine whether it "Add Custom Token" or token for "Scan Ethereum Address" flow? also what does it mean "add to address book", does application has this ability?

@hboon just few questions: ...

@vladyslav-iosdev we can’t tell if the user wants to add a custom token or watch wallet etc give just an Ethereum address. Will have to ask the user with an actionsheet.
You can ignore the “address book” functionality for now across all issues/PRs. It’s not designed completely yet.

book

ok, so i can replace addToAddressBook action with addCustomToken, right?

@hboon just few questions: ...

@vladyslav-iosdev we can’t tell if the user wants to add a custom token or watch wallet etc give just an Ethereum address. Will have to ask the user with an actionsheet.
You can ignore the “address book” functionality for now across all issues/PRs. It’s not designed completely yet.

ok, so i can replace addToAddressBook action with addCustomToken, right?

@hboon this one seems like is ready for review.


Hard Coded Ports for Lightning Apps

🐛 Bug
Currently we hard code the ports for lightning apps with the following snippet:
APP_SERVER_PORT = 7501 from the constants.py here

To Reproduce
Try running more than 1 lightning app at a time
Expected behavior
You're allowed to run more than one lightning app at a time
Environment
-->

CUDA:
- GPU:
- available:         False
- version:           None
Packages:
- numpy:             1.21.4
- pyTorch_debug:     False
- pyTorch_version:   1.9.0+cpu
- pytorch-lightning: 1.6.3
- tqdm:              4.64.0
System:
- OS:                Windows
- architecture:
- 64bit
- WindowsPE
- processor:         Intel64 Family 6 Model 140 Stepping 1, GenuineIntel
- python:            3.9.7
- version:           10.0.22000

Additional context
Believe this can be fixed by using the network utility here
Hypothesis:
I think using in src/lightning_app/core/constants.py for the APP_SERVER_PORT and then src/lightning_app/cli/lightning_cli.py would do the trick
Reality:
It seems making those changes on my local branch was not enough and then you get a site cannot be reached error. Is there another place a change needs to be made?
Code:
https://github.com/oojo12/lightning/tree/bug/13599_hard_coded_ports

@tchaton is there someone that can help me with this?

This has been addressed in #15819, closing 🎉


Provide a spring-boot-starter-lightadmin

Integrating lightadmin with spring-boot looks already quite simple.
In order to fit better in the overall spring-boot concept, a spring-boot-starter-lightadmin should be provided.
A first implementation could just include the dependencies.
An advanced implementation would do the basic configuration work, too, thus activation lightadmin in a SB project would be just adding spring-boot-starter-lightadmin to the pom.

How're things going on this item?

+1 for this feature

is this still under dev, or dead?

Dead I guess