stats.weightedtau([1], [1.0]) SEGFAULTs

stats.weightedtau SEGFAULTs when used with arrays of different types with len == 1. I suspect this is due to an uninitialized variable i in its helper, _toint64().
Reproducing code example:
from scipy.stats import weightedtau
# In my tests, this only repros in optimized builds after calling the function twice.
weightedtau([1], [1.0])
weightedtau([1], [1.0])

Error message:
Segmentation fault

Scipy/Numpy/Python version information:

SciPy 1.1.0
NumPy 1.15.1
Python 3.6.3

@evgenyzhurko would you be interested in send a pull request?

Just found this because after I was able to isolate this issue.
stats.weightedtau([np.nan],  [52])
will also segfaults.
(base) [mr85p01ad-hadoop408 ~]$ pip freeze | grep scipy
scipy==1.4.1


FixedAddress: "Name" field is not filled in when searching

Hello,
Starting with version 0.5.0 the FixedAddress struct contains a "Name" field which I had use for. I noticed however that the Name field will always be empty when searching. This is because at least in my WAPI version the wapidoc states that only "ipv4addr" and  "network_view" is included in the basic object and NewFixedAddress() does not include "name" when filling in the returnFields slice:
func NewFixedAddress(fixedAddr FixedAddress) *FixedAddress {
        res := fixedAddr
        res.objectType = "fixedaddress"
        res.returnFields = []string{"extattrs", "ipv4addr", "mac", "network", "network_view"}

        return &res
}

Since returnFields is unexported I can not add "name" from my own code. I noticed there seemed to exist some basic idea of having a function to modify this slice because of a commented out SetReturnFields() function:
type IBObject interface {
        ObjectType() string
        ReturnFields() []string
        EaSearch() EASearch
        //SetReturnFields([]string)
}

... but I see no further traces of such code.

@jkraj: I guess you should have more input on this since you added the "Name" field in the struct.

@eest Since name is not searchable I didn't add that into returnFields slice. If I include it will solve your issue.

https://github.com/infobloxopen/infoblox-go-client/pull/69


Failing to import openssl/ssl.h

Cannot get around an error with this package on Windows 11 or 10 when trying to install sslpsk.
sslpsk/_sslpsk.c(19): fatal error C1083: Cannot open include file: 'openssl/ssl.h': No such file or directory
Not sure what should I add on where to satisfy this error.

have the same problem :(


[CXF-6792] Some STS tests fails locally and on CI server

Hi all,
This PR is related to:
https://issues.apache.org/jira/browse/CXF-6792
Andrea

The errors in the build seems to be sporadic.


Feature proposal: Accessibility Assistant - text over an image test case

Problem: Using the Accessibility Assistant, my team has encountered a scenario where text placed over an image is not being tested for accessibility. It is only testing text against shapes and various objects with a solid color. I understand that there might be technical constraints preventing this feature to be developed as it heavily depends on the information of the image, placement of text, and several other complex conditions, but it is something that is desired and longed for.
Proposal: Add a testing case to the accessibility assistant that will cover the color contrast of text that is placed over an image (raster such as jpg or png or vectors such as SVG and eps).

Thank you for the request, it's something we've seen others asking for, too. Indeed, it's due to technical reasons that Assistants currently don't have access to the rendered context, something we hope to provide in the future.

Thanks for getting back on this, are there any other tools that you might recommend as an intermediate substitution/workaround?

Not 💯 sure they cover this specific use case but if you haven't tried yet:

https://www.getstark.co
https://cluse.cc (from the maker of the Accessibility Assistant)


Upgrade to clickhouse-go/v2

We upgrade Flow Aggregator to use ClickHouse go client v2 to better assist future supports. In terms of the method of creating connection, we replace DSN with OpenDB in database/sql interface.
Fixes: #4901

Put this PR on hold as we will have to upgrade clickhouse-server version first. The current clickhouse-server is v22.6, which is incompatible with the upgraded clickhouse-client. I'm fixing some issues in Theia while upgrading clickhouse-server.

Put this PR on hold as we will have to upgrade clickhouse-server version first. The current clickhouse-server is v22.6 in Theia, which is incompatible with the upgraded clickhouse-client. I'm fixing some issues in Theia while upgrading clickhouse-server.

We decided to remove the dependency from Antrea to Theia - by using official clickhouse-server images in e2e tests, instead of using theia/clickhouse-server images, which includes data schema management plugin.

/test-all

/test-e2e

I realized the jenkins test is not testing on FlowAggregator overall, no need to trigger it. Although I don't remember when we added --flow-visibility flag into kind test in PR https://github.com/antrea-io/antrea/pull/3673 , why we didn't do the same for jenkins, worth revisit later.
http://<IP_ADDRESS>:8080/job/antrea-e2e-for-pull-request/2107/consoleFull
=== RUN   TestFlowAggregator
    fixtures.go:54: Skipping when not running flow visibility test
--- SKIP: TestFlowAggregator (0.00s)

jenkins-e2e is broken apparently, so I'll go ahead and merge this


System parameters out of order

I declared a system
#[system(group=render)]
fn render(
    world: &mut World,
    rl: &mut RaylibHandle,
    thread: &RaylibThread,
    camera: &Camera2D,
    query: Query<(&Position, &Orientation)>,
) {

but the generated systems_render() as signature
#[allow(private_interfaces)]
pub fn systems_render(
    camera: &Camera2D,
    rl: &mut RaylibHandle,
    thread: &RaylibThread,
    world: &mut World,
) {
    render(world, rl, thread, camera, Query::new());
}

Notice that camera was put behind thread in render() declaration, but in systems_render() the camera parameter comes before rl
Is there anyway to keep the original parameter order?

No, the idea is that there could be multiple systems with different parameters.. Maybe I should change how parameters are provided. Probably using a builder pattern would be better.
Something like
systems.render_with().world(world).rl(rl).thread(thread).camera(camera).run();

?
I am not completely satisfied with 0.2.x of this library and am working on 0.3, so I very much appreciate the feedback.

Good to hear the project is still in development! Looking forward to version 0.3!


In D3 'enter' sequence 'selectAll' accepts any non-empty string. Could design be improved?

In the D3 'enter' sequence the 'selectAll' method accepts any non-empty string. See the following example:
https://bl.ocks.org/quantbo/45b98a10e42aa6656d0aa3aaaaf1a971
This suggests that 1) a method with an empty signature might be more appropriate for use at this point; or 2) the selectAll could be completely eliminated.

Interesting. I would have expected the selection would return empty since there are no children which would match the string.
On Dec 23, 2016, at 6:30 AM, quantbo <notifications<EMAIL_ADDRESS>wrote:
In the D3 'enter' sequence the 'selectAll' method accepts any non-empty string. See the following example:
https://bl.ocks.org/quantbo/45b98a10e42aa6656d0aa3aaaaf1a971
This suggests that 1) a method with an empty signature might be more appropriate for use at this point; or 2) the selectAll could be completely eliminated.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/d3/d3/issues/3042, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AUBnYuXQhcrhXTz17gPZf958rM2D6opLks5rK8zogaJpZM4LU0cl.

The selection returned by selectAll is empty (since nothing matches the string). Then, the data/enter/append combo creates three new circle elements, one for each row in the data set.

I'm not arguing about the functionality, which is fine. The syntax, though, is peculiar and potentially misleading. If a function with a string argument does not care which string is submitted then a better syntax would utilize a function with an empty signature or fold the function into another function. In the present case the elegant solution might be to fold selectAll into the data function.
To be clear, this is a user interface issue. Most of the examples that I have seen concerning the paradigm under discussion provide an argument to selectAll that appears meaningful. If circles are being generated then the author will provide selectAll with an argument such 'circle' or 'dot' or something similar. This conveys the impression that the argument has some meaning and  will have some effect on the execution of the program. In fact, the argument is completely irrelevant. If an argument is completely irrelevant then the function taking said argument should be rewritten or eliminated so as not to cause programmers to struggle with it.

I would prefer if you discuss D3’s API on the d3js Slack or the d3-js Google group. I use these issues to tract bugs and active feature requests. As noted in the issue template, no new issues should be filed in this repository; issues should be filed in an appropriate submodule instead. (See the D3 organization.)
That said, to attempt a quick answer to your question, consider an analogy with the W3C Selector API’s element.querySelectorAll. Your argument suggests that if the element is empty, it is pointless for element.querySelectorAll to take an argument, because the return value will always be an empty NodeList.
<body></body>

But obviously element.querySelectorAll takes a selector argument because if the element does have descendants, then element.querySelectorAll can return a non-empty NodeList. So element.querySelectorAll is a general-purpose method.
The selection.selectAll method functions similarly. You’ve constructed a situation (admittedly a common one!) where the svg selection is empty, so you know that calling svg.selectAll(…) will always return an empty selection. Yet if the svg selection were not empty, then it would not return an empty selection. And that is why selection.selectAll always takes a selector.
If you wanted, you could special-case an idiom like selection.appendMany from d3-jetpack. But D3 instead encourages you to implement a data-join that is independent of the current state of the DOM. That is, one that works regardless of whether you are starting from an empty empty or a non-empty empty, and one that should make the document match your current data regardless of its initial state.
To learn more about the design of the API, I suggest reading the General Update Pattern example thread, Thinking with Joins, and How Selections Work for more on selections.
Thanks for the feedback!


AnalysisJobPlacer should not require metadata

Not all gears produce metatdata

LGTM!

In this ticket I also corrected an "error" caused by #399 where we were previously silently not loading a missing schema analysis.json but now erroring when it was not found. The long term fix would be adding an analysis.json schema, tracked by #394.


Consume new @influxdata/vis library

The histogram visualization has been designed from the start to exist in an external module. This module has now been extracted and published to npm. This PR updates this repo to consume the pacakge from npm.

@chnn the repo, https://github.com/influxdata/vis, is private.  Should this be made public?

Absolutely, thanks for the heads up.


Fullscreen parallax transitions are janky on Firefox, on UHD display

This is a (multiple allowed):

[x] bug

[ ] enhancement

[ ] feature-discussion (RFC)

Swiper Version: 6.0.2.

Platform/Target and Browser Versions: Windows 10, Firefox 78.0.2 (64-bit), 3840x2160 @ 2dppi.

Initialised a single, full-screen slider, with parallax, as recommended by the guide:

        ...

const swiper = new Swiper('.swiper-container', {
    speed: 1000,
    loop: true,
    parallax: true,
})

Expected Behavior
EXPLAIN WHAT IS TO BE EXPECTED, HERE.
I expected (as observed on Chrome) smooth animations when transitioning between slides.
Actual Behavior
EXPLAIN WHAT IS ACTUALLY HAPPENING, HERE.
The animation appears very janky, I'd argue that it's pretty much unacceptable by current standards. At smaller sizes the issue disappears, but at full-screen it's highly noticeable.

Closing as not related to Swiper. If it is slow in some browser, then you can open issue for that browser asking why it is slow


root: 6.28.06 -> 6.28.08

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/root/versions.
meta.description for root is: A data analysis framework
meta.homepage for root is: https://root.cern.ch/
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 6.28.08 with grep in /nix/store/6gy2jdgjla06vxxkvp4lrmwff50g0560-root-6.28.08
found 6.28.08 in filename of file in /nix/store/6gy2jdgjla06vxxkvp4lrmwff50g0560-root-6.28.08

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

7 total rebuild path(s)

7 package rebuild(s)

First fifty rebuilds by attrpath
hepmc3
ns-3
python310Packages.hepmc3
python311Packages.hepmc3
root
xfitter
yoda-with-root

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/0ce0f0f55733dc67941e1410f1b8b7cede366a92#root

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/6gy2jdgjla06vxxkvp4lrmwff50g0560-root-6.28.08
ls -la /nix/store/6gy2jdgjla06vxxkvp4lrmwff50g0560-root-6.28.08/bin

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

7 packages built:

hepmc3
ns-3
python310Packages.hepmc3
python311Packages.hepmc3
root
xfitter
yoda-with-root

Maintainer pings
cc @veprbl for testing.

cc @ShamrockLee


Ignore js___jb_old___ files in the watchers

[17:51:14] add: Deploy\Config\Development\Templates\Shared\JS\Configuration.js___jb_old___
[17:51:14] File copied: Deploy\Config\Development\Templates\Shared\JS\Configuration.js___jb_old___
[17:51:29] File changed: Deploy\Config\Development\Templates\Shared\JS\Configuration.js, compiling js
[17:51:29] change: Deploy\Config\Development\Templates\Shared\JS\Configuration.js
[17:51:29] Babel: Deploy\Config\Development\Templates\Shared\JS\Configuration.js
[17:51:29] JavaScript compiled.
[17:51:29] unlink: Deploy\Config\Development\Templates\Shared\JS\Configuration.js___jb_old___

Perhaps we should just ignore the _jb_ (JetBrains) files in total instead of only the _jb_tmp_ files.
https://github.com/studyportals/product-deploy/blob/0421aad928fb2658ee7b998290ea2a050651b245/lib/deploy.js#L228


[Ratio Calculator] Calculate greatest common divisor based on width/height

Extension
https://www.raycast.com/justiniscoding/ratio-calculator
Description
It would be great if you could input a width and a height and get the greatest common divider being the ratio.
For example, inputting something like: 1920px/1080px (or maybe even just 1920/1080) would output 16/9.
Who will benefit from this feature?
I may not be the only one trying to get a proper ratio based on some image size.
Anything else?
Nope, hope you're interested in making it happen...

Extension
https://www.raycast.com/justiniscoding/ratio-calculator
Description
It would be great if you could input a width and a height and get the greatest common divider being the ratio.
For example, inputting something like: 1920px/1080px (or maybe even just 1920/1080) would output 16/9.
Who will benefit from this feature?
I may not be the only one trying to get a proper ratio based on some image size.
Anything else?
Nope, hope you're interested in making it happen...

Sure, I'll start working on it now!

Done, pull request here:
https://github.com/raycast/extensions/pull/10748


Not correctly detecting Mac platform

LibGpio.GetGpioPath() is not picking up that the code is running on a Mac.  The issue seems to be that the Environment.OSVersion.Platform is not returning PlatformID.MacOSX but is instead returning PlatformID.Unix.
Need to also check for PlatformID.Unix
See discussion here http://www.mono-project.com/docs/faq/technical/#how-to-detect-the-execution-platform

Thanks for the detailed info. I've updated as per your link.
Andy


Crash after opening user card

using nightly-win version 1.0.679

Unable to reproduce this with the latest commit, which should be nightly 1.0.682


http://freecodecamp.com/challenges/waypoint-use-hex-code-to-color-elements-green

Challenge http://freecodecamp.com/challenges/waypoint-use-hex-code-to-color-elements-green has an issue. Please describe how to reproduce it, and include links to screenshots if possible.
As I was going through it did not five me credit for completion in the MAP (not checked as completed)

Hey @dgoran thanks for posting this issue.
Its been a couple of weeks, has this been resolved?  If not can you post a screenshot and maybe the code that is not passing for that challenge?


Fully delete user

Separate from deactivate
Confirm dialog
Also add confirm dialog for deactivate

Originally created by Tom Smyth at 2015-08-23 04:10, migrated from redmine-#2940

Status changed from New to Closed

By Tom Smyth at 2015-09-20 06:03

Description updated (diff)

By Tom Smyth at 2015-08-23 08:16


Revert "begin updating webhook documentation"

Reverts kubernetes/website#6368
@tengqm Please don't merge PRs in the 1.9 project! #6368 was passing only 1 of 3 tests and still has work outstanding.

This change is

@zacharysarah I merged this because I can feel the frustration from the author doing find/replace. Since the author wanted to address the comments in a separate PR, I merged it to keep the balls rolling.
I'm fine with reverting this.


Make CORS work for oauth2 handlers

Fix #25473
Although there was m.Post("/login/oauth/access_token", CorsHandler() ... ,it never really worked, because it still lacks the "OPTIONS" handler.
After the fix:
$ curl -v -X OPTIONS --header "Access-Control-Request-Method: POST" http://localhost:3000/login/oauth/access_token
*   Trying <IP_ADDRESS>:3000...
> OPTIONS /login/oauth/access_token HTTP/1.1
> Accept: */*
> Access-Control-Request-Method: POST
>
< HTTP/1.1 200 OK
< Vary: Origin
< Vary: Access-Control-Request-Method
< Vary: Access-Control-Request-Headers
< X-Frame-Options: SAMEORIGIN
< X-Gitea-Debug: RUN_MODE=dev
< Date: Thu, 23 Nov 2023 11:45:36 GMT
< Content-Length: 0

$ curl -v -X OPTIONS http://localhost:3000/login/oauth/access_token
> OPTIONS /login/oauth/access_token HTTP/1.1
> Accept: */*
>
< HTTP/1.1 400 Bad Request
< Vary: Origin
< X-Frame-Options: SAMEORIGIN
< X-Gitea-Debug: RUN_MODE=dev
< Date: Thu, 23 Nov 2023 11:45:32 GMT
< Content-Length: 0

ps: I haven't fully tested the "oauth2 cors client", we can make further fixes if there are still problems.

I don't quite understand, why do we need these routes?

Because the "OPTIONS" is a separate request before "POST"

Still observing a similar problem:

Request URL: https://gitea-instance/login/oauth/userinfo
Request Method: OPTIONS
Status Code: 405 Method Not Allowed

Server side log:
2023/12/18 20:52:13 cmd/web.go:111:showWebStartupMessage() [I] Gitea version: 1.21.2 built with GNU Make 4.4.1, go1.21.5 : bindata, timetzdata, sqlite, sqlite_unlock_notify
...
2023/12/18 21:11:36 ...eb/routing/logger.go:102:func1() [I] router: completed OPTIONS /login/oauth/userinfo for XXX.XXX.XXX.XXX, 405 Method Not Allowed in 0.2ms @ web/goget.go:20(web.goGet)
Any help would be appreciated.

Because /login/oauth/userinfo was never covered by CORS.
This PR only fixes the access_token handler.
It could simply add a new line m.Options("/login/oauth/userinfo", CorsHandler(), misc.DummyBadRequest)  to make userinfo work, you can try to build your own binary to see whether it works well (I don't use it so my test doesn't mean it really works as your expectation)


StreamCache not being resetted after read

org.apache.camel.StreamCache can be read only once, so if we want to extract the payload of the same message on more than one step, we need to reset the stream.
This fix makes sure we will be able to re-read the body on future steps (if possible, as described on StreamCache): https://github.com/apache/camel/blob/master/core/camel-api/src/main/java/org/apache/camel/StreamCache.java#L25
The reset is done after the read in case the reset throws some error that makes the stream unusable (because it may really be a only-one-read stream) so it is prepared for future calls.

@igarashitm is it fine to fix the issue here or should we look for some fix more internal to AtlasMap?

@Delawen This looks very fishy, as we don't need to explicitly invoke reset() in camel2. Shouldn't it be camel3 that requires a fix or just a configuration issue?
At least doc doesn't say reset() is required
https://camel.apache.org/manual/latest/stream-caching.html
But I found the doc says
Stream caching is from Camel 2.12 onwards intended to be configured using org.apache.camel.spi.StreamCachingStrategy. The old kind of configuration using properties on the CamelContext has been marked as deprecated.
One guess is that the old configuration might have been removed in camel3? Does syndesis configure it via StreamCachingStrategy?

Syndesis does use the StreamCachingStrategy indeed. Why it did work before, I don't know. But this payload function is already on AtlasMap and, afaik, Syndesis does never get the reference to that message instances ever again. So it falls on AtlasMap and/or Camel to make sure we can read it more than once.

Checking the reset documentation, I understand you have to explicitly call it to be able to read more than once the same stream:
https://github.com/apache/camel/blob/master/core/camel-api/src/main/java/org/apache/camel/StreamCache.java#L42

Or maybe we can always copy the message before read:
https://github.com/apache/camel/blob/master/core/camel-api/src/main/java/org/apache/camel/StreamCache.java#L32-L33

@oscerd do we need to explicitly invoke reset() to make camel StreamCache re-readable in camel3? I think it was completely transparent in camel2 so that StreamCache implementation detail doesn't leak into endpoint.

Worst case scenario if we don't want to drag this into AtlasMap: we wrap that StreamCache on Syndesis side to call reset after each read.
But this looked more transparent to me.

@oscerd do we need to explicitly invoke reset() to make camel StreamCache re-readable in camel3? I think it was completely transparent in camel2 so that StreamCache implementation detail doesn't leak into endpoint.

There is a MessageHelper method for this purpose, you can use the resetStreamCache method.

@oscerd thanks, OK so it was changed by design. Then I'm OK to have this change in AtlasMap. But @Delawen please keep in mind that in Syndesis, any step that leverages Data Buckets (or anything that access old message later) will have to do the same.

Ugh forgot to ask @Delawen, can you take one more step and use MessageHelper.resetStreamCache() instead like @oscerd suggested?

Sure, will correct this :)


codegen: Fix segfault of CodegenLLVM::generateProbe()

If it is dummy, then the visit() operation should not be executed. For example, on aarch64, there is no syscalls:sys_{enter,exit}_open tracepoint, however, opensnoop.bt tool will try to attch them and visit args's field. We expect to get a warning, but instead we get a segmentation fault. As follows:
    $ sudo gdb bpftrace
    ...
    (gdb) set args opensnoop.bt
    (gdb) r
    opensnoop.bt:22-24: WARNING: tracepoint not found: syscalls:sys_enter_open
    opensnoop.bt:28-30: WARNING: tracepoint not found: syscalls:sys_exit_open

    Thread 1 "bpftrace" received signal SIGSEGV, Segmentation fault.
    0x000000000052bbd8 in __gnu_cxx::__normal_iterator<bpftrace::Field const*, std::vector<bpftrace::Field, std::allocator<bpftrace::Field> > >::__normal_iterator (this=0xffffffffb0b8, __i=<error reading variable: Cannot access memory at address 0x10>)
        at /usr/include/c++/14/bits/stl_iterator.h:1068
    1068	      : _M_current(__i) { }
    (gdb) bt
    #0  0x000000000052bbd8 in __gnu_cxx::__normal_iterator<bpftrace::Field const*, std::vector<bpftrace::Field, std::allocator<bpftrace::Field> > >::__normal_iterator (this=0xffffffffb0b8,
        __i=<error reading variable: Cannot access memory at address 0x10>) at /usr/include/c++/14/bits/stl_iterator.h:1068
    #1  0x0000000000525bdc in std::vector<bpftrace::Field, std::allocator<bpftrace::Field> >::begin (this=0x10)
        at /usr/include/c++/14/bits/stl_vector.h:884
    #2  0x000000000059ce8c in bpftrace::Struct::GetField (this=0x0, name="filename")
        at /home/rongtao/Git/bpftrace/bpftrace/src/struct.cpp:131
    #3  0x00000000005a70a0 in bpftrace::SizedType::GetField (this=0xe9b998, name="filename")
        at /home/rongtao/Git/bpftrace/bpftrace/src/types.cpp:538
    #4  0x00000000007c7178 in bpftrace::ast::CodegenLLVM::visit (this=0xffffffffc650, acc=...)
        at /home/rongtao/Git/bpftrace/bpftrace/src/ast/passes/codegen_llvm.cpp:1973
    #5  0x0000000000847db0 in bpftrace::ast::FieldAccess::accept (this=0xe9be30, v=...)
        at /home/rongtao/Git/bpftrace/bpftrace/src/ast/ast.cpp:31
    #6  0x00000000007d2404 in bpftrace::ast::CodegenLLVM::accept (this=0xffffffffc650, node=0xe9be30)
        at /home/rongtao/Git/bpftrace/bpftrace/src/ast/passes/codegen_llvm.cpp:3778
    #7  0x00000000007c8bec in bpftrace::ast::CodegenLLVM::visit (this=0xffffffffc650, assignment=...)
        at /home/rongtao/Git/bpftrace/bpftrace/src/ast/passes/codegen_llvm.cpp:2218
    #8  0x0000000000847eb4 in bpftrace::ast::AssignMapStatement::accept (this=0xffffe4429250, v=...)
        at /home/rongtao/Git/bpftrace/bpftrace/src/ast/ast.cpp:36
    #9  0x00000000007d2404 in bpftrace::ast::CodegenLLVM::accept (this=0xffffffffc650, node=0xffffe4429250)
        at /home/rongtao/Git/bpftrace/bpftrace/src/ast/passes/codegen_llvm.cpp:3778
    #10 0x00000000007ca4c4 in bpftrace::ast::CodegenLLVM::generateProbe (this=0xffffffffc650, probe=..., full_func_id="dummy",
        name="dummy", func_type=0xff2b50, usdt_location_index=std::optional [no contained value], dummy=true)
        at /home/rongtao/Git/bpftrace/bpftrace/src/ast/passes/codegen_llvm.cpp:2539
    #11 0x00000000007cb4e4 in bpftrace::ast::CodegenLLVM::visit (this=0xffffffffc650, probe=...)
        at /home/rongtao/Git/bpftrace/bpftrace/src/ast/passes/codegen_llvm.cpp:2734
    #12 0x00000000008480f0 in bpftrace::ast::Probe::accept (this=0xffffe4427650, v=...)
        at /home/rongtao/Git/bpftrace/bpftrace/src/ast/ast.cpp:47
    #13 0x00000000007d2404 in bpftrace::ast::CodegenLLVM::accept (this=0xffffffffc650, node=0xffffe4427650)
        at /home/rongtao/Git/bpftrace/bpftrace/src/ast/passes/codegen_llvm.cpp:3778
    #14 0x00000000007cb7a4 in bpftrace::ast::CodegenLLVM::visit (this=0xffffffffc650, program=...)
        at /home/rongtao/Git/bpftrace/bpftrace/src/ast/passes/codegen_llvm.cpp:2752
    #15 0x000000000084818c in bpftrace::ast::Program::accept (this=0xe90f50, v=...)
        at /home/rongtao/Git/bpftrace/bpftrace/src/ast/ast.cpp:50
    #16 0x00000000007d2404 in bpftrace::ast::CodegenLLVM::accept (this=0xffffffffc650, node=0xe90f50)
        at /home/rongtao/Git/bpftrace/bpftrace/src/ast/passes/codegen_llvm.cpp:3778
    #17 0x00000000007d03fc in bpftrace::ast::CodegenLLVM::generate_ir (this=0xffffffffc650)
        at /home/rongtao/Git/bpftrace/bpftrace/src/ast/passes/codegen_llvm.cpp:3450
    #18 0x0000000000478138 in main (argc=2, argv=0xfffffffff4c8) at /home/rongtao/Git/bpftrace/bpftrace/src/main.cpp:898

We can simplify opensnoop.bt to:
    tracepoint:syscalls:sys_enter_open_not_exist,
    tracepoint:syscalls:sys_enter_openat
    {
        @ = args.filename;
    }

This will produce the following error:
    stdin:1:1-45: WARNING: tracepoint not found: syscalls:sys_enter_open_not_exist
    tracepoint:syscalls:sys_enter_open_not_exist,tracepoint:syscalls:sys_enter_openat {@ = args.filename;}
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Segmentation fault

Because 'args' of 'syscalls:sys_enter_open_not_exist' is NULL, we should avoid dummy access to any field.

This is not a good solution and still has errors. I will try to fix it.
$ sudo bpftrace -e 'kprobe:zzzzz { probe; $a = arg0; printf("asdf\n") } BEGIN { printf("_%s_\n", "success"); exit() }'
stdin:1:1-13: WARNING: zzzzz is not traceable (either non-existing, inlined, or marked as "notrace"); attaching to it will likely fail
kprobe:zzzzz { probe; $a = arg0; printf("asdf\n") } BEGIN { printf("_%s_\n", "success"); exit() }
~~~~~~~~~~~~
LLVM ERROR: Invalid size request on a scalable vector.
Aborted

Thanks for catching this problem!
I believe that we need to generate the dummy probe only for cases when none of the probe attach points exists.
This should fix it:
diff --git a/src/ast/passes/codegen_llvm.cpp b/src/ast/passes/codegen_llvm.cpp
index cc625e80..85d61c92 100644
--- a/src/ast/passes/codegen_llvm.cpp
+++ b/src/ast/passes/codegen_llvm.cpp
@@ -2700,6 +2700,7 @@ void CodegenLLVM::visit(Probe &probe)
   // We begin by saving state that gets changed by the codegen pass, so we
   // can restore it for the next pass (printf_id_, time_id_).
   auto reset_ids = create_reset_ids();
+  bool generated = false;
   for (auto *attach_point : *probe.attach_points) {
     reset_ids();
     current_attach_point_ = attach_point;
@@ -2729,16 +2730,18 @@ void CodegenLLVM::visit(Probe &probe)

         auto match_ap = attach_point->create_expansion_copy(match);
         add_probe(match_ap, probe, match, func_type);
-      }
-      if (matches.empty()) {
-        generateProbe(probe, "dummy", "dummy", func_type, std::nullopt, true);
+        generated = true;
       }
     } else {
       if (probe.index() == 0)
         probe.set_index(getNextIndexForProbe());
       add_probe(*attach_point, probe, attach_point->name(), func_type);
+      generated = true;
     }
   }
+  if (!generated) {
+    generateProbe(probe, "dummy", "dummy", func_type, std::nullopt, true);
+  }

   current_attach_point_ = nullptr;
 }

Feel free to update your PR or I can open a new one.

Thanks for catching this problem!
I believe that we need to generate the dummy probe only for cases when none of the probe attach points exists.
This should fix it:
diff --git a/src/ast/passes/codegen_llvm.cpp b/src/ast/passes/codegen_llvm.cpp
index cc625e80..85d61c92 100644
--- a/src/ast/passes/codegen_llvm.cpp
+++ b/src/ast/passes/codegen_llvm.cpp
@@ -2700,6 +2700,7 @@ void CodegenLLVM::visit(Probe &probe)
   // We begin by saving state that gets changed by the codegen pass, so we
   // can restore it for the next pass (printf_id_, time_id_).
   auto reset_ids = create_reset_ids();
+  bool generated = false;
   for (auto *attach_point : *probe.attach_points) {
     reset_ids();
     current_attach_point_ = attach_point;
@@ -2729,16 +2730,18 @@ void CodegenLLVM::visit(Probe &probe)

         auto match_ap = attach_point->create_expansion_copy(match);
         add_probe(match_ap, probe, match, func_type);
-      }
-      if (matches.empty()) {
-        generateProbe(probe, "dummy", "dummy", func_type, std::nullopt, true);
+        generated = true;
       }
     } else {
       if (probe.index() == 0)
         probe.set_index(getNextIndexForProbe());
       add_probe(*attach_point, probe, attach_point->name(), func_type);
+      generated = true;
     }
   }
+  if (!generated) {
+    generateProbe(probe, "dummy", "dummy", func_type, std::nullopt, true);
+  }

   current_attach_point_ = nullptr;
 }

Feel free to update your PR or I can open a new one.

Sorry for the late response, i just  update this PR according your patch, and add  update your PR, thanks again!!

Needs rebase onto the current master. Also a CHANGELOG entry would be nice.

We should also consider if this is worth another patch release.
Among other things, it breaks opensnoop.bt on aarch64.

Needs rebase onto the current master. Also a CHANGELOG entry would be nice.

Rebase to master already. Thanks!

Thanks!


Add RawContactDataRows. Implements #1

This adds a convenience class to read all data rows belonging to a specific raw contact, identifed by a RowSnapshot or a RowReference.
No tests added yet. Waiting for RowSet test utilities.

Codecov Report

Merging #112 into master will increase coverage by 0.13%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #112      +/-   ##
==========================================
+ Coverage   31.48%   31.61%   +0.13%
==========================================
  Files         126      126
  Lines        1045     1047       +2
  Branches       40       40
==========================================
+ Hits          329      331       +2
  Misses        715      715
  Partials        1        1

Impacted Files
Coverage Δ

...mfs/android/contentpal/predicates/ReferringTo.java
100% <100%> (ø)
:arrow_up:

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 291134a...6c16bcd. Read the comment docs.


Can't catch specific exception in Interceptor

@AroundCall
    public void intercept(SimpleInterceptorStack stack) throws InterceptionException {
        try {
            stack.next();
        } catch (MyException e) {
            System.out.println("error");
        }
    }

This code does not work because VRaptor is encapsulating MyException in one ApplicationLogicException.

I've just oppened a PR https://github.com/caelum/vraptor4/pull/945 with this suggestion.
What do you think @lucascs @nykolaslima @everyone?

@Turini it doesn't have been released in the RC2 version?
which is the most recent available version?

@nykolaslima I'm so sorry about my delay to answer this thread. That was an insane week.
It'll be released as soon as possible -- I'm planning to do that this week, I'll let you know ;)

No problem @Turini. Thank you!
On Sat, Jul 18, 2015 at 9:16 PM Rodrigo Turini<EMAIL_ADDRESS>wrote:

@nykolaslima https://github.com/nykolaslima I'm so sorry about my delay
to answer this thread. That was an insane week.
It'll be released as soon as possible -- I'm planning to do that this
week, I'll let you know ;)
—
Reply to this email directly or view it on GitHub
https://github.com/caelum/vraptor4/issues/911#issuecomment-122608005.

Hi caelum/vraptor4,
I'd like to include you in my network to share updates and stay in touch.

Renan

Confirm that you know Renan: https://www.linkedin.com/e/v2?e=0-ihdt1q2v-a&t=ssuw&tracking=eml-guest-invite-cta&ek=invite_guest&sharedKey=1XiVMCa4&invitationId=6075009319286427648
You received an invitation to connect. LinkedIn will use your email address to make suggestions to our members in features like People You May Know. Unsubscribe here: https://www.linkedin.com/e/v2?e=0-ihdt1q2v-a&t=lun&midToken=AQFmrFVhGEd36Q&ek=invite_guest&loid=AQH51ye9wZFQqQAAAVE7E2ACL-axGo6togc6AmJDKlUYqJ1xuRJSMdSJgkiJyzKw3PjGINLi1AzvzqbKtyo3H1Tm0HA5x1NIeXZ6j-MQcP7eJX-POLleRTYGd1SZg1ima_hM45F3HSzur3QEbNaxm0DZEijtRbononR5WvpighScUCaPOMZE1GdhWFjUu0qXveCi&eid=0-ihdt1q2v-a
This email was sent to<EMAIL_ADDRESS>If you need assistance or have questions, please contact LinkedIn Customer Service: https://www.linkedin.com/e/v2?e=0-ihdt1q2v-a&a=customerServiceUrl&ek=invite_guest
© 2015 LinkedIn Corporation, 2029 Stierlin Court, Mountain View CA 94043. LinkedIn and the LinkedIn logo are registered trademarks of LinkedIn.

Renan Montenegro would like to connect on LinkedIn. How would you like to respond?
Accept: https://www.linkedin.com/e/v2?e=-vkbt7q-ihncxxup-25&a=preRegInvite&ek=first_guest_reminder_01&li=14&m=hero&ts=accept_text&sharedKey=1XiVMCa4&invitationID=6075009319286427648
View Renan Montenegro's profile: https://www.linkedin.com/e/v2?e=-vkbt7q-ihncxxup-25&a=preRegInvite&ek=first_guest_reminder_01&li=3&m=hero&ts=profile_text&sharedKey=1XiVMCa4&invitationID=6075009319286427648
You received an invitation to connect. LinkedIn will use your email address to make suggestions to our members in features like People You May Know. Unsubscribe here: https://www.linkedin.com/e/v2?e=-vkbt7q-ihncxxup-25&t=lun&midToken=AQFmrFVhGEd36Q&ek=first_guest_reminder_01&li=16&m=unsub&ts=HTML&eid=-vkbt7q-ihncxxup-25&loid=AQE4E1DLaAeFRgAAAVFeHogdxtow1U1H1wIZzBjYt0Lk27sJtqmeYQ24FP8EsgmjpRmlKverBbzp1z5tqHeI2lGtITD_z3KGWvmi4kIFGo252hx1kpDqIYWGD_TsKqHva2cnXRxpjCqNpe6Z9XVv2vFKQcXAh-RhZOnrVsnet3sBSlpwd19me7CRGFjMh2iTsXfe
This email was sent to<EMAIL_ADDRESS>If you need assistance or have questions, please contact LinkedIn Customer Service: https://www.linkedin.com/e/v2?e=-vkbt7q-ihncxxup-25&a=customerServiceUrl&ek=first_guest_reminder_01
© 2015 LinkedIn Corporation, 2029 Stierlin Court, Mountain View CA 94043. LinkedIn and the LinkedIn logo are registered trademarks of LinkedIn.

Renan Montenegro would like to connect on LinkedIn. How would you like to respond?
Accept: https://www.linkedin.com/e/v2?e=-vkbt7q-ihxd610w-gl&a=preRegInvite&ek=second_guest_reminder_01&li=13&m=hero&ts=accept_text&sharedKey=1XiVMCa4&invitationID=6075009319286427648
View Renan Montenegro's profile: https://www.linkedin.com/e/v2?e=-vkbt7q-ihxd610w-gl&a=preRegInvite&ek=second_guest_reminder_01&li=3&m=hero&ts=profile_text&sharedKey=1XiVMCa4&invitationID=6075009319286427648
You received an invitation to connect. LinkedIn will use your email address to make suggestions to our members in features like People You May Know. Unsubscribe here: https://www.linkedin.com/e/v2?e=-vkbt7q-ihxd610w-gl&t=lun&midToken=AQFmrFVhGEd36Q&ek=second_guest_reminder_01&li=15&m=unsub&ts=HTML&eid=-vkbt7q-ihxd610w-gl&loid=AQGr70i5ZX9ewgAAAVGClveMC5pmneKLcJkmVsxXiOaw1yR9DYoE5-qt-CcF0PulX4zskNbONFPwchLdYBmSWXYVaOCMwoW8FhxLsQkaZ4JWflZKAGfUW2FkzN_FrltxLGsbj5a7XUuaSWjpKrv0qWxzUzW6ovvuJgtNt2tgi4U57p6efr5V6FNDYdrqFIDaAhcl
This email was sent to<EMAIL_ADDRESS>If you need assistance or have questions, please contact LinkedIn Customer Service: https://www.linkedin.com/e/v2?e=-vkbt7q-ihxd610w-gl&a=customerServiceUrl&ek=second_guest_reminder_01
© 2015 LinkedIn Corporation, 2029 Stierlin Court, Mountain View CA 94043. LinkedIn and the LinkedIn logo are registered trademarks of LinkedIn.


To check if batch is closed if you need to return a pointer to the type the wrong code is generated

Version
v1.16.0 or 3623ec87fd3015f00cdc9e2c29c45d5557a12473, version v1.15.0 has the correct behavior, since there is no batch closeness check
What happened?
To check if batch is closed if you need to return a pointer to the type the wrong code is generated

SQL queries
:batchone

Configuration
version: "2"
engine: "postgresql"
sql_package: "pgx/v4"
emit_db_tags: true
emit_result_struct_pointers: true

What operating system are you using?
macOS
What database engines are you using?
PostgreSQL
What type of code are you generating?
Go

Nothing really wrong in the original PR, it's just that the emit_result_struct_pointers feature flag did not exist when the PGXv5 support was originally submitted.

It certainly is a regression though,it probably means we moved "old" code to a new place.

This flag was also for v4. Generally, with this flag there is an error in codogeneration

would be great to merge this :)


Support for expected "crashers"

Description
It should be possible to test that some code triggers process termination with a nonzero exit code and optionally certain output to standard output and error.
Expected behavior
No response
Actual behavior
No response
Steps to reproduce
No response
swift-testing version/commit hash
No response
Swift & OS version (output of swift --version && uname -a)
No response

Tracked internally as rdar://111625303.

Is there an issue one can subscribe to, in order to track the completion & release of this feature (it's not in the current release AFAICT)?

The draft pitch is here: #324
If/when that gets merged, the feature's been approved.


ur: make decode public

Unless there is another way to decode a single part message?

Thanks for the PR! I used your commit on #112 so I could add some documentation there. Will close this once the other PR is merged.


feat(logger): add critical log level

Current dependencies on/for this PR:

main

PR #119   👈

This comment was auto-generated by Graphite.

@pevisscher queued this pull request to merge with Graphite.

@pevisscher queued this pull request to merge with Graphite.


Breadcrumbs when exploring a repository

When exploring a repository, having breadcrumbs somewhere at the top of the page can be help in keeping track of the current position in the folder structure of the repository and easy relative navigation.

Added a while ago.  Closing.

coolio :metal:


Add attribute to ssh.command, that in tells return code of the command, that indicates 'no change'

In the "ssh.command", there may be situations when I can check, whether the system is already in the desired state or not.

If the system is in the desired state, I won't perform any action, only inform the caller (i.e. pyload in this case) that I did nothing.
In the other case, I can apply desired changes and return normal status code (zero for the success, non-zero for an error).

In case of 1., I can return special return code and simultaneously I can inform pyload, that this code means "no change".
Let we have (for example) such SSH command:
snap list helm || ( snap install helm && exit 0 ) && exit 200
This command returns status 200 if there is no change (i.e. helm is already installed) and normal status - i.e. 0 if helm was installed or non - zero except 200 (I must guarantee that there is no other 200 than my check) in case of error.
It would be perfect to be able to instruct pyload, that the status 200 means "no change".
It could be done by additional attribute of the "ssh.command" command , it can be named for example "no_change_status", so in such case the "ssh.command" can look like this:
ssh.command(     name="Install heml via snap",     command="snap list helm || ( snap install helm && exit 0 ) && exit 200",     no_change_status=200 )

For your particular example, you can write a custom Fact that checks whether a snap package is installed and only runs snap install if needed.

Thank you to pointing out, but - according to my knowledge - the result will not be the same. By my proposed solution, in the result list will be seen that there is some desired state but the opertion made no change (i.e. the system is already in the required state), in your proposal there will not to be a trace about the operation in such case. Am I correct?
Btw for my particular examle, the best solution would be to implement "snap" operation :) I looked how the operations are programmed, but my Python knowledge are too few and I don't feel like to be able to do i well. So I will fill new request, so I will make new feature request.

You are right, if the control flow is a part of the top-level file, the skipped operations won't show up. You can however wrap it in a simple operation just calling other operations.
the general idea is
import pyinfra

class SnapPackageInstalled(pyinfra.api.FactBase):
  pass # TODO check whether a package is installed

@pyinfra.api.operation
def install_snap_package(name):
  exists = pyinfra.host.get_fact(SnapPackageInstalled, name)
  if not exists:
    yield from pyinfra.operations.server.shell(f"snap install {name}") #TODO escape better

install_snap_package("helm")


Optimize first loading of current user

For now, the current user takes a certain moment to be retrieved from the server by next-auth.
The UI is then displayed in two times:

One: the current user is not loaded and the UI is displayed as if the user has no rights (some parts of the UI are missing).
Two: the current user is loaded and the UI is refreshed displaying all the parts the user has the rights to see.

:tada: This issue has been resolved in version 1.11.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Fix dependencies in jenkins-test script to support DB11.3 [databricks]

Signed-off-by: Ahmed Hussein (amahussein<EMAIL_ADDRESS>Fixes #7112
This PR is part of the incremental steps to support DB-11.3.
Changes

Different DB runtimes might have different PYTHON. This PR pulls the correct version from the instance. This takes care of adding the correct site-packages to PYTHONPATH export PYTHONPATH=/databricks/python3/lib/${sw_versions[PYTHON]}/site-packages:$PYTHONPATH
Pull the correct file name py4j-*-src.zip from the instance. Otherwise, the PYTHONPATH would be broken for DB11.3 PY4J_FILE=$(find $SPARK_HOME/python/lib -type f -iname "py4j*.zip")  export PYTHONPATH=$SPARK_HOME/python:$SPARK_HOME/python/pyspark/:$PY4J_FILE
The original  default ICEBERG_VERSION 0.13.2 is sot support on DB11.3. Added 0.14.1 as default to run on DB11.3.
Add instructions on usage, and how to extend the script to support new DB releases.

build

build

build

build

build


[HUDI-6379] [DO NOT MERGE] Pulsar version change to fix snakeyaml CVE

Change Logs
Upgrade Pulsar to 2.10.0 in Hudi, as current Pulsar version brings in snakeYaml < 2.0 which is a security vulnerability.
https://github.com/apache/pulsar/pull/20085
CVE-2022-1471 : https://nvd.nist.gov/vuln/detail/CVE-2022-1471
[Need to run manual testing as we don't have any unit or functional test to check the pulsar functionality.]
Impact
Pulsar version change to fix snakeyaml CVE.
Risk level (write none, low medium or high below)
Low
Documentation Update
Not required
Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

@mansipp is this still WIP?

Closing this PR as the Pulsar version gas been upgraded to 3.0.2 in #10223


When acting as a SAML SP allow configuration of RequestedAuthnContext

This PR allows for setting a RequestedAuthnContext in the SAMLRequest generated when UAA is operating as a SAML SP.  This is accomplished by adding a new property to login.saml.providers named authnContext.
For example:
login:
  saml:
    providers:
      cloud.gov:
        authnContext:
        - foo
        - bar
        - baz
        idpMetadata: |
           ...

Would produce a SAMLRequest with this RequestedAuthnContext:
<saml2p:RequestedAuthnContext Comparison="exact">
	<saml2:AuthnContextClassRef xmlns:saml2="urn:oasis:names:tc:SAML:2.0:assertion">foo</saml2:AuthnContextClassRef>
	<saml2:AuthnContextClassRef xmlns:saml2="urn:oasis:names:tc:SAML:2.0:assertion">bar</saml2:AuthnContextClassRef>
	<saml2:AuthnContextClassRef xmlns:saml2="urn:oasis:names:tc:SAML:2.0:assertion">baz</saml2:AuthnContextClassRef>
</saml2p:RequestedAuthnContext>

If this value is not provided, the previous default behavior of not including any RequestedAuthnContext in the request is preserved.
Update: This PR now includes validation of the context returned by the IDP.
I'm not an expert in Java or the UAA codebase so feedback is appreciated 😁

Coverage increased (+0.001%) to 86.344% when pulling 0b10687f82b0891e746ea8b74e3a6a7acfba5eef on cnelson:authncontext into<PHONE_NUMBER>855f3d2918a010a64a3ac8a944edba on cloudfoundry:develop.

Coverage increased (+0.001%) to 86.344% when pulling 0b10687f82b0891e746ea8b74e3a6a7acfba5eef on cnelson:authncontext into<PHONE_NUMBER>855f3d2918a010a64a3ac8a944edba on cloudfoundry:develop.

Coverage increased (+0.001%) to 86.344% when pulling 0b10687f82b0891e746ea8b74e3a6a7acfba5eef on cnelson:authncontext into<PHONE_NUMBER>855f3d2918a010a64a3ac8a944edba on cloudfoundry:develop.

Coverage increased (+0.001%) to 86.344% when pulling 0b10687f82b0891e746ea8b74e3a6a7acfba5eef on cnelson:authncontext into<PHONE_NUMBER>855f3d2918a010a64a3ac8a944edba on cloudfoundry:develop.

Coverage decreased (-0.2%) to 86.11% when pulling b2fb514a2273bf9859ef4254cf4a5e3bae17b306 on cnelson:authncontext into<PHONE_NUMBER>855f3d2918a010a64a3ac8a944edba on cloudfoundry:develop.

☝ Those test failures seem like travis issues and not related to this PR.  Can someone retry the build?

We have merged this change.


Publish the cadets.ca version of the App.

A new version must be published with Paul's fixes, upgrade to swift 5, new branding, and changes to sample data.


2.0 Sidebar nav styling bug

Link to reproduction
/
To Reproduce
Open payload admin panel and make window smaller (mobile/tablet size)
Describe the Bug
When not opened:

When clicking hamburger:

Payload Version
2.0

Hey @silveltman . Thanks for the report. Unfortunately, I have not been able to reproduce this. What OS and browser are you using? Are you able to make a video reproducing?
https://github.com/payloadcms/payload/assets/65888/bdd477f9-7b5b-471d-96b7-3801f5939970


when getUseDeveloperSupport return true, React-Native don't load NetworkingModule in Android

React Native version:
<!--
  System:
    OS: macOS 10.15.1
    CPU: (4) x64 Intel(R) Core(TM) i5-7267U CPU @ 3.10GHz
    Memory: 67.38 MB / 8.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 12.6.0 - /usr/local/bin/node
    Yarn: 1.17.3 - /usr/local/bin/yarn
    npm: 6.9.0 - /usr/local/bin/npm
  SDKs:
    iOS SDK:
      Platforms: iOS 13.2, DriverKit 19.0, macOS 10.15, tvOS 13.2, watchOS 6.1
    Android SDK:
      Android NDK: 19.2.5345600
  IDEs:
    Android Studio: 3.5 AI-191.8<IP_ADDRESS>91312
    Xcode: 11.2/11B52 - /usr/bin/xcodebuild
  npmPackages:
    react: 16.9.0 => 16.9.0
    react-native: 0.61.4 => 0.61.4
  npmGlobalPackages:
    react-native-cli: 2.0.1

Describe what you expected to happen:
When I was about to publish app, I found that my app could not request the network. This problem bothered me for a long time. Finally, I found that when getUseDeveloperSupport returned false, react native would not load the NetworkingModule. But publish app must return false of getUseDeveloperSupport. How can I solve this problem? Thank you

React Native version:
System:
OS: macOS 10.15.1
CPU: (4) x64 Intel(R) Core(TM) i5-7267U CPU @ 3.10GHz
Memory: 67.38 MB / 8.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 12.6.0 - /usr/local/bin/node
Yarn: 1.17.3 - /usr/local/bin/yarn
npm: 6.9.0 - /usr/local/bin/npm
SDKs:
iOS SDK:
Platforms: iOS 13.2, DriverKit 19.0, macOS 10.15, tvOS 13.2, watchOS 6.1
Android SDK:
Android NDK: 19.2.5345600
IDEs:
Android Studio: 3.5 AI-191.8<IP_ADDRESS>91312
Xcode: 11.2/11B52 - /usr/bin/xcodebuild
npmPackages:
react: 16.9.0 => 16.9.0
react-native: 0.61.4 => 0.61.4
npmGlobalPackages:
react-native-cli: 2.0.1
problem Description:
When I was about to publish, I found that my app could not request the network. This problem bothered me for a long time. Finally, I found that when getUseDeveloperSupport returned false, react native would not load the NetworkingModule. But the publish app must return false of getUseDeveloperSupport. How can I solve this problem? Thank you !

I found that in debug mode, react native can load the networkmodule because it is connected to http:/ / localhost:8037 metro bundle. I want to know when the networkmodule will be loaded


Add information about 2020.3 having Lombok support

Built in support is now available in IntelliJ

Wait... what? I mean, you're right, but, wait.. what???
Um, I guess a sizable chunk of tonight's lombok meeting will discuss this :)

Starting with Intellij 2020.3 the lombok-intellij-plugin (https://github.com/mplushnikov/lombok-intellij-plugin) is now bundled with IntelliJ Ultimate edition, but not with the Community edition.

Actually maybe I am wrong and it is also bundled with the Community edition....

I've just changed jobs and this is going to help me a lot with persuading
my new team to use Lombok. Although the other choice is to move over to
Kotlin so I'm actually not too worried about it. :-)
On Thu, 10 Dec 2020, 16:37 Matthias Kurz<EMAIL_ADDRESS>wrote:

Actually maybe I am wrong and it is also bundled with the Community
edition....
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/rzwitserloot/lombok/pull/2674#issuecomment-742636492,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKPS43FRGS5DZU72VKXYFTSUD2LLANCNFSM4UTS2RDQ
.


fix integration tests for alpine3

Checklist

[x] make test-all (UNIX) passes. CI will also test this
[ ] unit and/or integration tests are included (if applicable)
[ ] documentation is changed or added (if applicable)

Description of change

Apache2 has only one listener by design. Either IPv4 or IPv6.
It seems that the order of the ip addresses has been changed (in CI/docker runtime). Previously IPv4 first to now IPv6 first. If the test with Apache2 should explicitly test IPv4, the service should also explicitly run on IPv4.
Related:

#935
#936
#907

Yeah, I think this is related to https://github.com/goss-org/goss/issues/149
My guess is travis-ci changed that setting in their CI runners. I'm not able to reproduce that behavior on my local machine and the CI used to work just fine.. so that's my theory.
I added some debugging to my branch yesterday which showed that it was indeed listening to tcp6 here:
https://app.travis-ci.com/github/goss-org/goss/jobs/623192771#L5295
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 <IP_ADDRESS>:42279        <IP_ADDRESS>:*               LISTEN      -
tcp        0      0 <IP_ADDRESS>:8888            <IP_ADDRESS>:*               LISTEN      -
tcp        0      0 :::8888                 :::*                    LISTEN      -
tcp        0      0 :::80                   :::*                    LISTEN      164/httpd

This PR is the cleanest fix, so I'll merge this and close out the other ones.
Great find and thanks for the elegant fix!

I had a discussion with my colleague. One alternative is to switch from Apache2 to Nginx. Nginx runs on both ports, IPv4 and IPv6.


peer_basic.Network of Peers.chaincode example02 with 4 peers and 1 membersrvc, test crash fault -- @1.1 Consensus Options - failed with timeout issue

Description

behave test case (peer_basic.Network of Peers.chaincode example02 with 4 peers and 1 membersrvc, test crash fault -- @1.1 Consensus Options) failed while waiting invoke transaction to be committed to all peers. Observed below is the root cause for the above failure:
Build Failing step: Then I wait up to "60" seconds for transaction to be committed to peers ... failed in 60.259s.  Build Reference# 84
Build Failing step: Then I wait up to "60" seconds for transaction to be committed to peers ... failed in 60.272s - Build Reference# 82
Describe How to Reproduce

Jenkins failed build references:
https://jenkins.hyperledger.org/view/fabric/job/fabric-verify-x86_64/84/
https://jenkins.hyperledger.org/view/fabric/job/fabric-verify-x86_64/82/

The test in question stops and restarts peers vp1/vp2.
The peers come back up with different IP addresses while the peer code tries to re-establish connections using the old IP addresses ( as it should , imho ).
The behave test runs fine in my vagrant with docker v1.11.2

Interesting..  Docker version in Jenkins build machine is 1.8.2
+ docker version
00:00:36.920 Client:
00:00:36.920  Version:      1.8.2
00:00:36.920  API version:  1.20
00:00:36.920  Go version:   go1.4.2
00:00:36.920  Git commit:   0a8c2e3
00:00:36.920  Built:        Wed Oct  7 17:48:28 UTC 2015
00:00:36.920  OS/Arch:      linux/amd64
00:00:36.920
00:00:36.920 Server:
00:00:36.920  Version:      1.8.2
00:00:36.920  API version:  1.20
00:00:36.920  Go version:   go1.4.2
00:00:36.920  Git commit:   0a8c2e3
00:00:36.920  Built:        Wed Oct  7 17:48:28 UTC 2015
00:00:36.920  OS/Arch:      linux/amd64

Not observed this issue after merge below patch set in gerrit
https://gerrit.hyperledger.org/r/#/c/371/ --
Will reopen or create a new issue if we observe this issue again.. Closing now.


redis: ring rehash perf

@danielhochman has done some experimentation and with very large ring sizes rehash can take a long time (1+ seconds on a fast processor) which blocks the workers. We also use a lot of memory for the ring which we duplicate on every worker. We should consider calculating the ring on the main thread and then sharing it across all worker threads. This is a bit different from how the other load balancers work so will require some thinking.

I've thought about this a little bit and I think the way to go about this is to actually make the LB owned by the central thread and be responsible for being thread safe. This may mean using TLS, etc. The benefit of this approach is it would also benefit subset LB and other more complicated load  balancers. cc @danielhochman

Can I hear a bit more about your thoughts here?
I think making LB (just picking, not prefetching) makes more sense outside
of the context of subset LB.   Once you scale up you generally want each
worker to have connections to a subset of endpoints, at which point it
makes more sense to have a per-worker LB, not less.
Doing the expensive calculations in another thread (which I think was your
previous plan) made sense to me.  Alternately we can look into other data
structures - internally we use a backend picker which has more expensive
picks but is structured to allow for delta updates, so individual backends
going unhealthy or getting replaced is a cheaper operation.
On Sat, Dec 2, 2017 at 5:52 PM, Matt Klein<EMAIL_ADDRESS>wrote:

I've thought about this a little bit and I think the way to go about this
is to actually make the LB owned by the central thread and be responsible
for being thread safe. This may mean using TLS, etc. The benefit of this
approach is it would also benefit subset LB and other more complicated load
balancers. cc @danielhochman https://github.com/danielhochman
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/envoyproxy/envoy/issues/1941#issuecomment-348726019,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARYFvTuN63LeXAe-1JNaVIZmbDvpqer3ks5s8dSQgaJpZM4QG1A-
.

@alyssawilk my rough plan is as follows:

On a per-LB basis, allow the LB to be a structure that is allocated per worker, or allocated on the central thread and passed by pointer to the workers.
This allows the LB writer to choose which model they want.
For the ring-hash LB specifically, I was planning on rewriting the LB so that it does the ring computations on the central thread, and then posts the rings via TLS slot to all workers. Workers then use the most recent rings via RCU.

I looked into actually doing ring updates in a separate thread, potentially per worker, but it's actually quite complicated and still wasteful from a memory perspective. I think ^ is the best of both worlds. I do think that ^ would work quite well for subset also. Basically, subset calculations can take place on central thread, then get passed to the workers. The workers could take those calculations and do additional calculations if they want.
TL/DR: Make LB flexible so that it can be totally isolated per worker, global, or global w/ TLS (what I will do w/ ring hash).
Let me know if that makes sense.

SG.  If I'm understanding correctly it won't get us any gains for subset lb, but it will substantially help with both CPU and memory for the common case.  As long as we can avoid/minimize lock contention I'm all for it.

Right, in my initial patch, I'm not planning on touch subset LB. However, the subset LB computations are expensive, and I think we should think about refactoring the subset LB in the same way that I am going to refactor ring hash. We can discuss after I'm done w/ the ring hash refactor. cc @zuercher


Type of Promise not unwrapped with useSelector in suspence mode

The example from documentation:
import { ObservableObject } from '@legendapp/state';
import { useObservable, useSelector } from '@legendapp/state/react';
import { Suspense } from 'react';

function Test({ state$ }: { state$: ObservableObject<Promise<string>> }) {
  const value = useSelector(state$, { suspense: true });
  return
{value}
;
}

export default function App() {
  const state$ = useObservable(
    new Promise<string>((resolve) => {
      setTimeout(() => {
        resolve('hello');
      }, 1000);
    })
  );
  return (

Suspense test

      <Suspense fallback={
Loading...
}>
        <Test state$={state$} />
      </Suspense>

  );
}

https://stackblitz.com/edit/vitejs-vite-ehsrz6?file=src%2FApp.tsx
Type of value should be string. Currently it is Promise<string>

Regarding suspence interface. It would be nice to have something like:
.getSuspended()

Turns out the type is different if using observable instead of useObservable:
string & WithState
observable and useObservable are also different  in that only useObservable accepts a function

Currently useComputed/computed works differently with promise:

It has does not return state property
It does unwrap the type
It is not reactive to promise fullfillment
Not sure if it works with suspence

Expect computed to work with promises same as observable of promise:

Return also the state/_state
reactive to fullfillment
unwrap the type
work with suspence

Another problem:
Seems like suspense using useSelector(observer, { suspense: true } does not work within a component which wrapped in observer

I am working on a PR to use promise in computed.

Before you do that can you try it in the @next version (computed-types branch) which will soon be version 3.0? It changes and improves Promise behavior significantly.
Sorry I haven’t replied yet - things have been in flux with finishing that and I haven’t had a chance to check it with the suspense behavior yet.

Reason for suspese not working within observer is this shortcircuit:

3.0 does more changes.
I need to finish fully intergrating legend into our state.
For that enough is to fix current version.
What is left for me is to fix the above suspense issue.

Looks like this is the only change for useSelector

Ah good catch! That seems like a good fix. Would you like to PR that?

Ah good catch! That seems like a good fix. Would you like to PR that?

Yes

https://github.com/LegendApp/legend-state/pull/291
@jmeistrich

I did this in order to easier run from the repo directly

Better to refactor the imports of `@legendapp/state' in repo into relative imports , I think.
And to build into dist folder.

Hmm, I don’t think we want to make such a large change in v2 when we’re just about to release v3. We have a strict rule (especially in v3) that we shouldn’t have have any Promises in observable. v2 was certainly messy and inconsistent with Promise handling, but v3 extracts them out and replaces them with their value, and there’s a syncState that can access its status. I think v3 should solve what you’re trying to do very well, and I’m curious how upgrading to it would go?
See this section of the preview docs: https://preview.legend.pages.dev/open-source/state/v3/usage/observable/#async-observables
I would like to get in the suspense fix with credit to you though :). Would you like to submit a PR for just that and we can merge that in easily?

Ok, I will look more into v3. Which branch is it?
I tried to make a fix only to useSelector,  but it crashes - without fix to computed, but I will try to make it work.

I like the syncState approach, no need to continue adding properties like state.
Just need to make sure that promise works with computed and promised computed works with suspense

How do you setup dev env for developing the lib?
I imported it as a TS into vite app but had to add an alias to babel.

@jmeistrich
PR have been adjusted

@lishine It’s the computed-types branch but I’m about to merge it into main today 😀. And I merged the adjusted PR, thanks!
For a dev env I currently build it and copy the dist folder into the project’s node_modules. My workflow is mainly: when I find a bug in apps I figure out how to reproduce it, write a test in legend-state that reproduces it and fix it so the test passes, then build and copy to the app to make sure it worked. That’s probably not the most effective way to do it… If you have any suggestions for how to do that better I would appreciate it!

That’s merged in and released in the latest 3.0.0-alpha.1. So since that and promise behavior should be working much better now, I’m going to close this issue. But please let me know if it’s still not working correctly and we can re-open this and solve it :).


Bug report - [Short description] temperature and humidity sensor

Describe the bug

A clear and concise description of what the bug is. Can’t anymore tuya zigbee temperature and humidity sensor add to homey 2019. Before it was oké.

To Reproduce
Steps to reproduce the behavior:

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

Expected behavior

A clear and concise description of what you expected to happen.

App and Homey version

What Homey version are you running? Early 2019
What version of Homey firmware do you use? 12.0.0
What version of the Tuya Zigbee App are you using? V0.1.45

Screenshots

If applicable, add screenshots to help explain your problem.

Additional context

Add any other context about the problem here.

Hi @Adri1359, what's the device Zigbee info? (add it as unknown zigbee and check settings)

Hi JohanBendz,It’s working with the test tuya zigbee app, thxGr AdriOp 4 sep 2024 om 12:04 heeft Johan Bendz @.***> het volgende geschreven:
Hi @Adri1359, what's the device Zigbee info? (add it as unknown zigbee and check settings)
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>


Add replace() method

replace() method must be added in Notifications class.

https://docs.ionic.io/api/endpoints/push.html#put-notifications-notification_id


Update py.py

@thisiscoding1234  can we please stop spamming pull request, this one will probably not help.

@thisiscoding1234  can we please stop spamming pull request, this one will probably not help.


Issues while entering OTP.

-Not moving to the next box quickly, after a while.
-Allowing multiple entries in one box. Should allow only one. Sometimes the keyboard covers the text boxes.

Duplicate of #1891


Slim down docs client

The main reason for using favicons-webpack-plugin is to avoid having the same source file in the repo twice, but we don't need to generate a full suite of favicons for a debug page.
We also can avoid bundling in fonts to reduce size further. Worst case is if in a constrainted network fonts don't load, the page will still work fine (and maybe even with correct fonts if the OS contains roboto)
Incidentally, I found out that favicon won't work in most cases since it doesn't support relocation (e.g., mounting at /docs) until https://github.com/jantimon/favicons-webpack-plugin/pull/173
Fixes #2299

Thanks, @anuraaga !


[New Sample] Snap Geometry Edits

Description
This PR is for the Snap Geometry Edits sample in the Edit and Manage Data category.
This sample design aims to showcase feature snapping functionality while editing a geometry using the GeometryEditor.
Links and Data
Design: SnapGeometryEdits
Data: WaterDistributionNetwork
What To Review

Readme, metadata, and resource files.
Review the code to make sure it is easy to follow like other samples on Android.

How to Test

Run the sample prototype on the sample viewer or the repo.

https://github.com/Esri/arcgis-maps-sdk-kotlin-samples/assets/72321786/33317a7a-a90b-4768-acdc-9ba344087bed

Hi all, thanks for the reviews. I have added the suggested changes.


Install kivy in venv failed: windows 10 + python 3.8.1

Software Versions

Python: 3.8.1
OS: windows 10
Kivy: 1.11.1
Kivy installation method: pip install kivy

I just enter my venv, and pip install kivy, and almost downloaded then failed. please see the below screenshots. Thanks very much.

Duplicate of https://github.com/kivy/kivy/issues/6806.


Issue with simple demo

Awesome job and thinking by having this really great library :)
But I'm facing an Issue with just a simple Form demo,
Followed your steps for installation in a new solid-js project  (not SolidStart).
Imported as shown to your examples
import { createForm, Form, Field } from '@modular-forms/solid';
Copy/Pate the form example
`export default function App() {
const loginForm = createForm();
const loginUser = () => {
console.log("TODO: login values")
}
return (

{(field) => <input {...field.props} type="email" />}

{(field) => <input {...field.props} type="password" />}

);
}`
but I get the following error...
Uncaught ReferenceError: React is not defined
at Form (index.esm.jsx:1454:3)
PackageJson:
"devDependencies": {     "@babel/core": "^7.20.5",     "@storybook/addon-actions": "^6.5.13",     "@storybook/addon-essentials": "^6.5.13",     "@storybook/addon-interactions": "^6.5.13",     "@storybook/addon-links": "^6.5.13",     "@storybook/builder-vite": "^0.2.5",     "@storybook/html": "^6.5.13",     "@storybook/testing-library": "^0.0.13",     "@typescript-eslint/eslint-plugin": "^5.43.0",     "@typescript-eslint/parser": "^5.43.0",     "autoprefixer": "^10.4.13",     "babel-loader": "^8.3.0",     "eslint": "^8.28.0",     "eslint-config-airbnb-base": "^15.0.0",     "eslint-config-airbnb-typescript": "^17.0.0",     "eslint-config-prettier": "^8.5.0",     "eslint-plugin-prettier": "^4.2.1",     "eslint-plugin-solid": "^0.8.0",     "postcss": "^8.4.19",     "prettier": "^2.7.1",     "tailwindcss": "^3.2.4",     "typescript": "^4.8.2",     "vite": "^3.2.3",     "vite-plugin-solid": "^2.3.0"   },   "dependencies": {     "@modular-forms/solid": "^0.9.1",     "@solid-primitives/i18n": "^1.1.2",     "@solidjs/router": "^0.5.1",     "@thisbeyond/solid-dnd": "^0.7.3",     "solid-devtools": "^0.23.1",     "solid-js": "^1.6.2"   },   "engines": {     "node": ">=14"   }
viteConfig:
`import { defineConfig } from 'vite';
import solidPlugin from 'vite-plugin-solid';
export default defineConfig({
plugins: [solidPlugin()],
server: {
port: 3000,
},
build: {
target: 'esnext',
},
optimizeDeps: {
extensions: ['jsx', 'tsx'],
},
});
`
I can't locate what I do wrong in the example, also tried to replicate examples from your github but had the same outcome.

I'll take a look at the problem later.  I am sure that we will find a solution.  How exactly did you create the Solid project?  Then I try to do the same steps on my machine.

Hello
I get this error and already check what @fabian-hiller write but still get error. Any solution for this error? maybe because I use NX?

I put '@modular-forms/solid' on optimizeDeps.exclude vite config and it's working again

I recommend asking for help on the SolidJS Discord.


Just a test

What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?:

Just a comment


call connection.connect() to make the connection.

@ikshitiz : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Transport status in title bar

@danielfm Just a thought - With regards to the transport status (mode line stuff) - It might be nice to have the option to put it in the title bar if you're running in GUI mode. It uses a fair bit of space in the modeline, even if you make it as compact as possible. And with multiple windows, it really can clutter things up. Let me know if you'd consider a PR for this. Thank you!

Sounds like a nice addition, although not for me personally since I use emacs either in the terminal, or in a tiling window manager (in which the window doesn't have a title bar like in other desktop environments such as GNOME or KDE).

Ok, I'll go ahead and branch off of your async branch and then sync when that's pushed to master. Thanks for the consideration!

@jkdufair if it helps, what I have in the modeline:
(setq spotify-mode-line-playing-text ">")
(setq spotify-mode-line-paused-text "|")
(setq spotify-mode-line-stopped-text ".")
(setq spotify-mode-line-format  "[%p %a: %t|%r%s]")

It looks pretty short. When splitting into two windows vertically it does get quite busy. I'm using mood-line though, which is relatively compact, so it's not that bad.
To change the frame title you can use frame-title-format. I use a tiling WM at home like Daniel does, but for Windows I find it useful to have the buffer name, I have this in my init: (setq frame-title-format "%b - Emacs").
It seems spotify-update-mode-line is the best place to read the final mode-line string already formatted, since how it's constructed depends on the transport used.


Sites with foreigner characters are shown as gibberish.

Some sites are shown with gibberish characters instead of the correct once, however this doesn't seems to happen consistently.

NRK.no shows the correct characters (æøå) but gamlegjerpen.no does not.
Seems like gamlegjerpen.no does not contain: <meta charset="utf-8">
Not sure if that's why it gets displayed as gibberish on the downloaded copy but it's something.

@xGigaa thanks a lot for reporting an issue. Can you paste the exact command you typed ?

Sure.
./suckit http://www.gamlegjerpen.no/ -j 8 -o /run/media/gigaa/67489829-d767-48c7-aabd-f7c3180f5895/backup/gamlegjerpen
And
./suckit https://www.nrk.no/ -j 8 -o /run/media/gigaa/67489829-d767-48c7-aabd-f7c3180f5895/backup/nrk
(NRK is a large news site so be wary if you try to download the whole site)

The same happens with very basic accented Spanish characters.
e.g.  suckit http://www.spagnolo-online.de/ (2 GB website)

My first approach was to use the the charset="XXX" in http headers fields. But some site does not provide it. So my next bet is to use a regex in the header of the page to fetch charset="XXXX". Is this a good idea ?

I got this working bassed on the regex thing. The code is ugly but it's getting there. #105


Mouse overlay rendering pixellated ?

Hi,
I'm discovering Captura and it's amazing.
The mouse overlay is very cool but the rendering is overly , pixellated
Is there any way to obtain a better rendering ?

This has already been fixed but not released yet.
Please check this dev build: https://ci.appveyor.com/api/buildjobs/m29qt216g8vf8g28/artifacts/Captura-Portable.zip

Works like a charm.
Your software rocks
Congrat


Skip old migrations

Hello
When adding online_migrations on an old project. I have to change previous and old migrations when the database was not populated so without any risk of issue. Is it possible to make check on migration only on migration after a specific date?
I can work on this PR if needed.

Hi. I think, start_after config option is what you are looking for - https://github.com/fatkodima/online_migrations#existing-migrations ?

Oups sorry. It's perfect.


remove sodium oxide

Replaced with https://github.com/RustCrypto/AEADs

as per the sodiumoxide docs: https://docs.rs/sodiumoxide/latest/sodiumoxide/crypto/secretbox/index.html
the secretbox module uses xsalsa20poly1305
As per wikipedia: https://en.wikipedia.org/wiki/ChaCha20-Poly1305 and this SO post: https://crypto.stackexchange.com/questions/27007/why-should-one-prefer-salsa20-over-chacha
chacha20 is an improved version of salsa20
So the use of the chacha20poly1305 is equivalent to the existing sodiumoxide implementation


Internal Server Error

Environment
Docker
Version
0.11.5
Describe the problem
Due to the "authelia_session" cookie used for Authelia authentication, Homarr is experiencing an "Internal Server Error". Removing this cookie resolves the error. This issue seems to occur more frequently on Mozilla Firefox, but it has also been encountered a few times on Google Chrome. Based on the analysis of the request, it appears that the server is unable to process the cookie that is being sent to it.

Additional info
Log from Docker:
    Error [URIError]: URI malformed
    at decodeURIComponent (<anonymous>)
    at parseCookieString (file:///app/.next/server/src/middleware.js:628:22)
    at new RequestCookies (file:///app/.next/server/src/middleware.js:678:28)
    at new NextRequest (file:///app/.next/server/src/middleware.js:851:22)
    at new NextRequestHint (file:///app/.next/server/src/middleware.js:1106:9)
    at adapter (file:///app/.next/server/src/middleware.js:1163:21)
    at next_middleware_loaderabsolutePagePath_private_next_root_dir_2Fsrc_2Fmiddleware_ts_page_2Fsrc_2Fmiddleware_rootDir_2Fhome_2Frunner_2Fwork_2Fhomarr_2Fhomarr_matchers_ (file:///app/.next/server/src/middleware.js:1313:18)
    at <unknown> (file:///app/node_modules/next/dist/server/web/sandbox/sandbox.js:73:30)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

    TypeError: Cannot read properties of undefined (reading '_nextI18Next')
    at AppWithTranslation (/app/node_modules/next-i18next/dist/commonjs/appWithTranslation.js:92:29)
    at Wc (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:68:44)
    at Zc (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:253)
    at Z (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
    at Zc (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:481)
    at Z (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
    at $c (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:78:98)
    at bd (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:77:404)
    at Z (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:217)
    at Zc (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:71:479)

Please tick the boxes

[X] You've read the docs
[X] You've checked for duplicate issues
[X] You've tried to debug yourself

Duplicate of #716


Will it be available again?

SmallCDN's website isn't working , no commits since late 2016. But will it be available again?

probably not, but feel free to clone the repos and make your own cdn!


move (pan?) within the page on UP/DOWN

I want a keyboard-only workflow to read PDF documents. Currently the texpresso viewer enables this in fit-height mode, but not in fit-width mode where I have to use the touchpad to scroll through the page.
This naive PR implements "pan up" and "pan down" actions when pressing up/down key. I can now browse through the document by hitting "down" until the end of the page, and then "right" to get to the next page.
Notes:

I needed to add code to "reset the pan" on {previous,next}_page: when I am at the bottom of a page and press "right", I want to end up at the top of the next page, not at the same position. I briefly tried to understand the size computations to know which value of pan.y to set to be at the top of the page, and gave up; the code use 1. / 0.. Feel free to suggest a better value -- or modify the patch, etc. (Note: previous_page also resets to the top of the page, I am not sure if people would want something different there, maybe start at the bottom of the page?)
Ideally I could keep browsing with just up/down: when we hit the page boundary, "down" again would go to the next page. I am not familiar enough with the geometry stuff to implement this easily.
the "pan down" action does not pan by exactly the viewer height, but by 0.9 times that. This helps provide some continuity in the content to know where to restart reading. It might be even better to smoothly scroll to the next position, but I don't know how to implement it, and it might be disturbing to some people, and I don't think it is necessary.

Thanks for the contribution. I started working on your patch to allow browsing with up/down and to compute the right value for panning (rather than using 1 / 0).
I am not satisfied by the current geometry code but this representation was easy enough for a quick'n'dirty renderer. I would like to implement a "continuous" view at some point, with a stream of all pages that can be scrolled through.
For the 0.9 factor, did you try a few other ones? For the SyncTeX code, after some experiments I decided to use the value 2/3 as I felt it gave a good trade-off between scrolling speed and smoothness. Do you have any thoughts about that?

I tried 1, and I didn't like it, and then 0.9. Please feel free to change to 2/3 if you think this is better or just for consistency.

This looks nice, thanks! (I haven't tested it, but I am sure it is an improvement over my first implementation.)

I just added left/right panning. Now only pageup/pagedown change page immediately. I am not sure whether it is useful or not...
I was also thinking about a two columns panning feature: when reaching bottom and the view is not aligned with the right of the document, it would pan right and scroll to the top of the document.

I think that the two-column panning behavior should be configurable, otherwise it could be confusing / not what we want for some workflow.
(Note: maybe there is an even more structured way to handle two-column modes, by letting people define bounding boxes for the columns for odd and even pages.)

I like the patch as it is.
I removed the left/right pan feature as it is unclear how useful it is, I merge this PR and will open a new one to track future development.
I agree with that the two columns mode should be opt-in, but this probably requires a better UI that will not happen anytime soon.
Thanks!

It should be possible to infer the two column structure from the DVI (as well as improving cropping, focusing, etc). This also requires too much work to be implemented in the short term.

There is something weird with the new implementation where "down" may pan jump to the following page. Sometimes I am at the bottom of the current page, but pressing "down" does not bring me to the top of the next page, it brings me below the top -- there is a thin slice at the top that I cannot see.
Observed behavior:

I am at the top of the page
I press "down", and I get immediately at the bottom of the page
I press "down" again, and I start below the top of the next page

I observe that this occurs when in "crop border" mode, and only on some pages. I believe that this occurs on page that have more whitespace at the top than the other -- they correspond to the beginning of a chapter. When I am at the beginning of such a page in cropped mode, and I press "right", I end up at the same vertical position on the next page (if we think of coordinates before cropping), which is not the beginning of the cropped page but below it. I get the same behavior if I press "down" twice instead of "right", breaking the possibility of continuous reading. I guess that both those behaviors are small bugs.

(Ah, looking at the diff again I see that this corresponds to the FIXME comments in the code.)

Maybe using +/- inf is the simplest fix :).

I remain unsatisfied with the current behavior: when I try to move through the document using "up" and "down" I am often lost, not sure where I am.
I looked at what Okular does (it's my go-to PDF viewer, but I don't want to suggest that it is the only reasonable model to follow):

up/down appears to move the view by a small absolute amount (no sure in which unit this is expressed; viewport coordinates? by default nSteps is 10)
pageup/pagedown move the viewport by its full height, but they use a smooth scroll animation

Source:

key bindings: https://github.com/KDE/okular/blob/38679152b9f42cd6387d5cefae1e2e8529cda25b/part/pageview.cpp#L2028-L2049
ScrollDown function: https://github.com/KDE/okular/blob/38679152b9f42cd6387d5cefae1e2e8529cda25b/part/pageview.cpp#L5217-L5239

Maybe I should try to implement a smooth scroll animation on up/down in Texpresso to feel less lost?


[Docker] Updated Dockerfile's

This PR will allow us to run the up to date code for Overte with the node version provided by VCPKG
Before this is merged I would recommend that @daleglass has a runner with a tag of self-hosted.

We have tested it and it works

I have found a bug regarding ports not binding I will have a look at some point


Add JavaScript to the personal details nationalities page

Context
Candidates need to be able to input multiple nationalities. Paul built the design using some JS.
This should do a few things.
It should have an add nationalities button. When clicked this should display an additional select for candidates to pick an additional nationality. This button should not display once all 3 selects are visible.
It should have a remove link on the second and third select. When clicked it should hide the select and clear its value.
If multiple nationalities are present, when a user goes to edit their nationality they should pre-populate.
If an error occurs, use the non-js solution.
Changes proposed in this pull request

Build the JS functionality. for the nationalities page

Guidance to review
Screenshots of the designs are on the Trello ticket.
Probably easiest to just manually test it and see if you can break it.
Link to Trello card
https://trello.com/c/AsOuRv9u/1760-dev-🌐-international-residency-visa-status
Things to check

[x] This code doesn't rely on migrations in the same Pull Request
[x] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[x] API release notes have been updated if necessary
[x] New environment variables have been added to the Azure config

Thanks for the feedback Steve. I'll sort the bug with the button and link with the flag off now.
Why are English, Welsh and Northern Irish listed as nationalities in the Other autocomplete?
Some people self-identify as Scottish, Welsh etc. I'm pretty sure Paul said that those should be valid options.
I think @tvararu had some thoughts on the other points.


Filter generated classes into non-overlapping groups

As a test manager developing using a continuous integration pipeline
I want to run non-overlapping sets of tests in parallel from separate maven executions
So that I can configure parallelisation at the level of my continuous integration tool
So that I do not need to redesign my continuous integration pipeline.
I've created a first draft for this enhancement, configured as follows:
<groupFilter>
  <currentGroup>1</currentGroup>
  <totalGroups>2</totalGroups>
</groupFilter>

The above configuration will filter half of the generated classes, whereas the other half would be filtered using the following configuration:
<groupFilter>
  <currentGroup>0</currentGroup><!-- N.B. using '2' would give the same result-->
  <totalGroups>2</totalGroups>
</groupFilter>

I used the  order in which the classes are created to divide the groups, but based on the comments in the integration tests about execution order not being stable across environments, this might not be stable. I'm planning to amend it to use a hash of the properties of the current feature and scenario. Let me know if you think you know a better way.

I do not think this is the proper solution.
It tries to solve the problem of which tests to execute in the generate test sources phases. To keep this plugin simple it  should always generate all runners for the cucumber features/scenarios that will be executed. The problem of which tests to execute or how to execute them should be solved in a different lifecycle phase.
I think that the best solution would leverage surefire/failsafe inclusion and exclusion filters to execute different tests in different maven profiles. For example:
Profile A:
<includes>
  <include>*0IT.java</include>
  <include>*1IT.java</include>
  <include>*2IT.java</include>
  <include>*3IT.java</include>
  <include>*4IT.java</include>
</includes>

Profile B:
<includes>
  <include>*5IT.java</include>
  <include>*6IT.java</include>
  <include>*7IT.java</include>
  <include>*8IT.java</include>
  <include>*9IT.java</include>
</includes>

This is of-course very unwieldy. So I would not be opposed to seeing the pattern naming scheme be expanded to include a modulo counter to make this easier.
<namingScheme>pattern</namingScheme>
<namingPattern>Group{m:6}-Parallel{c}IT</namingPattern>

Here m:6 would be interpreted as a new ModuloCounter(6) which counts 0,1,2,3,4,5,0,1,3....

Ok, on reflection I agree that what you describe is better. If the generation order is fixed this should be quick to implement. I will do so.


The current .Net SDK does not support targeting .Net Core 3.1.

Problem encountered on https://dotnet.microsoft.com/learn/dotnet/hello-world-tutorial/create
Operating System: windows
Provide details about the problem you're experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.
C:>dotnet --version
returns
3.1.101
As soon as I open the console project using Visual Studio Enterprise 2019 Version 16.0.4 I get the following error:
Severity	Code	Description	Project	File	Line	Suppression State
Error	NETSDK1045	The current .NET SDK does not support targeting .NET Core 3.1.  Either target .NET Core 2.2 or lower, or use a version of the .NET SDK that supports .NET Core 3.1.	myApp	C:\Program Files\dotnet\sdk\2.2.401\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.TargetFrameworkInference.targets	137

Needed to update to Visual Studio 2019 v16.5+.

Needed to update to Visual Studio 2019 v16.5+.

Needed to update to Visual Studio 2019 v16.5+.

Needed to update to Visual Studio 2019 v16.5+.

Needed to update to Visual Studio 2019 v16.5+.

resolved

resolved

Needed to update to Visual Studio 2019 v16.5+.

Correct! Given that it seems your problem is resolved, I'm closing this issue.


General Performance Issues

Harvest Festival Version: 0.5.14
Forge Version:  2166
So I've been playing with Harvest Festival for a week or so on my server and I've noticed some serious performance problems: dropped ticks, erratic entity movement, etc and I've been trying to figure it out. I removed Harvest Festival today and the problems stopped. I love this mod but I'm guessing it just does too much for it to work nicely with a modestly sized mod pack (70 mods). Such a bummer.
For reference: our server is no slouch, it's a core i-7 2600 with 16gb of RAM dedicated hardware.
Anyway, love the mod, wish we could use it on our server!

You'll have to be more specific about which parts you're having issues
with. By the nature of the mod of course removing it will improve things
slightly since it's affecting how the world looks, with time,and seasons.
And you'll also have a daily performance drop as it does everything it
needs to at once. However it has not impacted playability at all for me.
Any decrease is incredibly minor and unnoticed. So you'd have to inform me
what's affecting you personally the most.  Can't just guess. need the
evidence
On 9 Dec 2016 5:52 pm, "Tehkiah"<EMAIL_ADDRESS>wrote:
Harvest Festival Version: 0.5.14
Forge Version: 2166
So I've been playing with Harvest Festival for a week or so on my server
and I've noticed some serious performance problems: dropped ticks, erratic
entity movement, etc and I've been trying to figure it out. I removed
Harvest Festival today and the problems stopped. I love this mod but I'm
guessing it just does too much for it to work nicely with a modestly sized
mod pack (70 mods). Such a bummer.
For reference: our server is no slouch, it's a core i-7 2600 with 16gb of
RAM dedicated hardware.
Anyway, love the mod, wish we could use it on our server!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/PenguinSquad/Harvest-Festival/issues/113, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AFmWqXJWJvt2Eva553Zmdh9cj1mKsXkHks5rGZVugaJpZM4LJMV4
.

I have to reference my own issue since I believe if seasons are calling that many ticks maybe some users would be better off not running it.
https://github.com/PenguinSquad/Harvest-Festival/issues/114


Fix Tamper Protection checking section

Added try-catch block and -ErrorAction Stop parameter around Get-ItemProperty cmdlet to handle errors during execution. Catch block displays message indicating Tamper Protection is not enabled or detected, providing user with more information about potential issues during installation process.

thanks!