We should publish the GoDoc for Terratest

This will make it easier to see what modules/functions are available.

Found it here terratest GoDoc

Oh, how cool! Great find, thanks!
I've added a link to the README: https://github.com/gruntwork-io/terratest#godoc. Browsing through it, our docs could use some work to make the GoDoc more useful, but it's a start.


Purge children from view registry when UIManager is invalidated

Summary:

Talking about Paper & iOS here.
In standard RN applications when a native component is removed permanently from view hierarchy it is invalidated (if it implements RCTInvalidating). Components that implement RCTInvalidating such as RNSScreenView of react-native-screens library rely on RCTInvalidating#invalidate method being called in adequate moment to release retained resources (in my case the RNSScreenView holds a strong reference to it's view controller preventing it from being garbage collected).
However in case of brownfield applications (React Native is used only for a particular view & loaded on demand, see: https://github.com/software-mansion/react-native-screens/issues/1754 for discussion & app example) when view controller holding RCTRootView is dismissed and whole React Native managed view / controller tree gets deallocated, RCTInvalidating#invalidate method is not called on the dismissed components, thus in my particular use case, leading to memory leak.
Right now I've added call to RCTUIManager#_purgeChildren:fromRegistry: (which internally invalidates all components which implement RCTInvalidating) in RCTUIManager#invalidate.
Changelog:

[IOS][FIXED] - Purge children from view registry on RCTUIManager invalidation.
Test Plan:

You can run the demo provided in the issue.
Following screenshots show that memory leak in brownfield application is resolved.
Without the change (invalidate method is not being called on native components)

With the change:

Hey @kkafar, thanks for opening this PR! Could you please rebase and check if CI tests are passing?
Also, can someone who is more familiar with this part take a look?
cc @javache @sammy-SC

Yeah, sure, done.
Waiting for CI.

Hey, CI fails but it does not like my change affects it -- rather some kind of build issue.

Seems reasonable. I'm surprised we don't have another codepath which does this.
One other way you could get the right behaviour here is to make sure you stop each root before you tear down React Native, that will cause all views to be unmounted and also will allow useEffect destructors to run.

Can you rebase? The pod error should've been resolved by https://github.com/facebook/react-native/commit/ce39931bc2b02f13cbc5751ba4d4a6dbc07bc91a

@javache, yeah sure, rebased


bootstrap with jquery ui sortable

I have that issue that then i am dragging item it is not in right place.  Also i find out that was because that
html {
overflow-y: scroll; // this line had that issue
font-size: 100%;
-webkit-text-size-adjust: 100%;
-ms-text-size-adjust: 100%;
}
fix was.
html {
overflow-y:visible;
}

interesting - we can't change overflow-y to be universally visible because that would result in some odd behavior for regular scrollable pages. That said, if it works for you - do it :)


Report failures <1%

For example, the 'procuring entity organization reference' check reports no failures on the compiled release screen:

But clicking through to the check shows that there are actually 3 failures:

Similarly, on the field checks screen, if the failure rate is <1% the check reports 100% success.

https://dqt.datlab.eu/resource/352
I'd expect that, when it's exactly 0%, that it's the same grey in any column, not just the middle column.


Reenable getprogname on NuttX & rename to px4_get_taskname

@julianoes can you review this?

Looks good. And doesn't break Snappy.

rebased & applied


DashDB upload function via DashDB API

Hey Alex & Snowplow gang,
I added a Shredded HDFS -> DashDB feature inside of emr_job.rb. The uploading/transferring will be done inside the public custom jar, https://s3.amazonaws.com/snowplow-dashdb-connector/snowplow-emr-etl-runner.jar, which the CustomJarStep points to (line 281: hdfs_to_dashdb = Elasticity::CustomJarStep.new('s3://snowplow-dashdb-connector/sp_dashdb_connector.jar')).
The DashDB target details is pulled from the config.yml file for the EmrEtlRunner and will require the following fields: name, type (dashdb), host, port, table, username, and password. The database field is currently nonfunctional (assumes the database name is the same as username), but I can make that an optional field when the need is there.
As mentioned before, Storage-Loader would fail at the moment if using the same config.yml as the EmrEtlRunner since the 'dashdb' target is unrecognized. Please let me know if and when you want me to fix it.
Thanks as always!
Steven

Great to see this land @ironsideshu ! We'll reach out to you once the intervening Snowplow releases have gone out and will ask you to rebase in due course, hope that's okay.
In the meantime - can you sign our CLA: https://github.com/snowplow/snowplow/wiki/CLA

Refer to #2908


[ aarch64 ] minimal example run error: BPF program load failed: Invalid argument

Platform:

ARCH: aarch64
system: ubuntu 20.04
kernel version: 5.10.104

we can not run the minimal sample correctly. before running, we modifid kernel config.
git clone --recurse-submodules https://github.com/libbpf/libbpf-bootstrap.git
cd ./example/c
make
sudo ./minimal -v

$$ sudo ./minimal -v
libbpf: loading object 'minimal_bpf' from buffer
libbpf: elf: section(2) tp/syscalls/sys_enter_write, size 104, link 0, flags 6, type=1
libbpf: sec 'tp/syscalls/sys_enter_write': found program 'handle_tp' at insn offset 0 (0 bytes), code size 13 insns (104 bytes)
libbpf: elf: section(3) license, size 13, link 0, flags 3, type=1
libbpf: license of minimal_bpf is Dual BSD/GPL
libbpf: elf: section(4) .bss, size 4, link 0, flags 3, type=8
libbpf: elf: section(5) .rodata, size 28, link 0, flags 2, type=1
libbpf: elf: section(6) .BTF, size 611, link 0, flags 0, type=1
libbpf: elf: section(7) .BTF.ext, size 160, link 0, flags 0, type=1
libbpf: elf: section(8) .symtab, size 216, link 13, flags 0, type=2
libbpf: elf: section(9) .reltp/syscalls/sys_enter_write, size 32, link 8, flags 0, type=9
libbpf: looking for externs among 9 symbols...
libbpf: collected 0 externs total
libbpf: map 'minimal_.bss' (global data): at sec_idx 4, offset 0, flags 400.
libbpf: map 0 is "minimal_.bss"
libbpf: map 'minimal_.rodata' (global data): at sec_idx 5, offset 0, flags 480.
libbpf: map 1 is "minimal_.rodata"
libbpf: sec '.reltp/syscalls/sys_enter_write': collecting relocation for section(2) 'tp/syscalls/sys_enter_write'
libbpf: sec '.reltp/syscalls/sys_enter_write': relo #0: insn #2 against 'my_pid'
libbpf: prog 'handle_tp': found data map 0 (minimal_.bss, sec 4, off 0) for insn 2
libbpf: sec '.reltp/syscalls/sys_enter_write': relo #1: insn #6 against '.rodata'
libbpf: prog 'handle_tp': found data map 1 (minimal_.rodata, sec 5, off 0) for insn 6
libbpf: map 'minimal_.bss': created successfully, fd=4
libbpf: map 'minimal_.rodata': created successfully, fd=5
libbpf: prog 'handle_tp': BPF program load failed: Invalid argument
libbpf: prog 'handle_tp': failed to load: -22
libbpf: failed to load object 'minimal_bpf'
libbpf: failed to load BPF skeleton 'minimal_bpf': -22
Failed to load and verify BPF skeleton

Maybe you can check if your kernel is compiled with CONFIG_FTRACE_SYSCALLS enabled.

i have the same problem.
have you solved it?

Try using https://github.com/anakryiko/retsnoop to pinpoint where the error is originating in the kernel.

@anakryiko
hello, i want to know :
if every program in examples/c can be run correctly without rebuilding kernel, which kernel version should i select?
i found that:
when kernel version is 4.19, bootstrap and minimal can't  run, minimal_legacy is ok.
when kernel version is 5.10, bootstrap can't  run,   minimal and minimal_legacy are ok.
when kernel version is 5.15, bootstrap, minimal and minimal_legacy all are ok.
can i find more info about this?

@hangsz, Now we can run minimal sample correctly.
The reason why failed is we do not open the kernel config option:
CONFIG_BPF_EVENTS=y
however, when I enable the config option: CONFIG_DEBUG_INFO_BTF=y,  we make kernel image failed.
Error: FAILED unresolved symbol udp6_sock
# error log
 DESCEND  bpf/resolve_btfids
  CALL    scripts/atomic/check-atomics.sh
  CALL    scripts/checksyscalls.sh
  CHK     include/generated/compile.h
  GEN     .version
  CHK     include/generated/compile.h
  UPD     include/generated/compile.h
  CC      init/version.o
  AR      init/built-in.a
  LD      vmlinux.o
  MODPOST vmlinux.symvers
  MODINFO modules.builtin.modinfo
  GEN     modules.builtin
  LD      .tmp_vmlinux.btf
  BTF     .btf.vmlinux.bin.o
  LD      .tmp_vmlinux.kallsyms1
  KSYMS   .tmp_vmlinux.kallsyms1.S
  AS      .tmp_vmlinux.kallsyms1.S
  LD      .tmp_vmlinux.kallsyms2
  KSYMS   .tmp_vmlinux.kallsyms2.S
  AS      .tmp_vmlinux.kallsyms2.S
  LD      vmlinux
  BTFIDS  vmlinux
adding symbol seq_file
adding symbol btf_allowlist_d_path
adding symbol security_file_permission
adding symbol security_inode_getattr
adding symbol security_file_open
adding symbol vfs_truncate
adding symbol vfs_fallocate
adding symbol dentry_open
adding symbol vfs_getattr
adding symbol filp_close
adding symbol path
adding symbol btf_sleepable_lsm_hooks
adding symbol btf_non_sleepable_error_inject
adding symbol __add_to_page_cache_locked
adding symbol should_fail_alloc_page
adding symbol should_failslab
adding symbol bpf_map
adding symbol task_struct
adding symbol file
adding symbol bpf_prog
adding symbol bpf_ctx_convert
adding symbol sk_buff
adding symbol xdp_buff
adding symbol inet_sock
adding symbol inet_connection_sock
adding symbol inet_request_sock
adding symbol inet_timewait_sock
adding symbol request_sock
adding symbol sock
adding symbol sock_common
adding symbol tcp_sock
adding symbol tcp_request_sock
adding symbol tcp_timewait_sock
adding symbol tcp6_sock
adding symbol udp_sock
adding symbol udp6_sock
adding symbol netlink_sock
adding symbol fib6_info
patching addr    96: ID   23245 [xdp_buff]
patching addr   144: ID  127196 [udp_sock]
FAILED unresolved symbol udp6_sock
make: *** [Makefile:1211: vmlinux] Error 255

here is our config file.
defconfig.log
thanks.

@ziyangfu  to recompile kernel is not  a good choice. i build my dev env on vm(vagrant) and ubuntu2204, everything works correctly.

@anakryiko Thank you for your reply. It's quite useful to me.


Clean Promise in RPC.js, + Some code style for network selection

Description
Starting a small refactor on the way promise are handled in rpc.js file. instead of creating some Promise over and over just chain it as many time you want.
Motivation and Context
It doesn't fix an open issue, but it simplify a lot of current rpc.js file. Note that the call function should be defined before everything to ease the reading.
Next step is to refacto storage.js aswell.
How Has This Been Tested?
I've just run the test and all are passing atm
Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

(none, just styling)
Checklist:

[x] My code follows the code style of this project. (eslint compliant)
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

These changes conflict with some concurrent improvements to enabled private networks in mesh.js  Could you take a look and rebase?  The change should be relatively minor.  Everything else looks great.  Also consider removing the seed nodes out into your const (can talk to @rockacola about this) instead of how we currently dynamically generate the domain.

Hey !
Did the rebase, and did some tweak to the mesh constructor to to ease the reading.
About the node seeds, I did some changes too, i didn't keep the order in the nodes array but I didn't found anything in the code if order has a meaning or not.

Not a problem, the order doesn't matter. :)


Redis dev

Make changes based on the proposal in  #561 .

Besides new features in Redis cache, this pr also makes changes on the lifecycle test framework based on @zhongyi-zhang 's code. That's, add preProvisionFns in serviceLifecycleTestCase struct to provision necessary resources before executing the provisioning steps.

Hey @krancour @jeremyrickard  , could you please have a review on it?

#561 proposes a lot of different changes and per this comment, it would be nice if we could break this PR up into smaller, more discrete PRs. I'd like to consider each new feature individually instead of having one all-or-nothing PR with many features.

Hi @krancour , thanks for the advise. I'm going to break this pr into several small PRs.

Going to close this PR, smaller PRs will be opened later.


Access clearing house logs

Hello I am testing the integration between the DSC and the clearing house and I am having a problem accessing the data of the clearing house. I have asked the clearing house team and they told me it is the user (the DSC) the one in charge of saving the metadata of the transactions and requesting based on them.
Is there any way to access the logged information on the clearing house through the DSC? I have been searching for API functions but couldn't see any of them related to the clearing house.
Let me know how it is supposed to be accessed the clearing house information through the DSC.
Thanks for the help.

Hi,
information logged to the Clearing House can be queried using the DSC's /api/ids/query endpoint. For this request, set the recipient parameter to <clearing-house-url>/messages/query/<agreement-uuid> and the request body to "". The agreement-uuid in the URL has to be replaced with the UUID of a contract agreement on provider side, as both provider and consumer log under that ID.
Currently, there is a bug in the communication between DSC and Clearing House (see this issue), which prevents the connectors from correctly logging and querying messages to/from the Clearing House. This issue is solved on branch 885-clearing-house-interaction, but has not yet been merged into the main branch.

https://international-data-spaces-association.github.io/DataspaceConnector/CommunicationGuide/v6/IdsEcosystem/ClearingHouse


how to change media device target?

first at all thank you for develop this perfect tool its help a lot..
My question is how to change camera source or mice source daring stream because i cant find any guide about that..

You'll get small arrow in camera/webcam icon. By click on that arrow you'll see all your media devices. You can change to any device.


Application of config settings when installing package depends on content of uv cache

We use uv to build the python environments that we run pyright against for our large codebase Dagster. Pyright environments do not handle Python import hooks correctly. It is therefore important that all editables installs in the environment use a "legacy" style, where the pth file contains a static path instead of an import hook.
Modern style:
### __editable__.foo-0.1.0.pth

import __editable___foo_0_1_0_finder; __editable___foo_0_1_0_finder.install()

Legacy style:
### __editable__.foo-0.1.0.pth

/path/to/foo

The way you force a legacy style when setuptools is used as build backend (which is what our packages use) is to pass editable_mode=compat as a config option. So this should work, and has worked in the past:
uv pip install --config-setting editable_mode=compat -e my_package

However, it seems like the cache is interfering in this command working properly. If the package has already been installed as editable without editable_mode=compat in one environment, then attempting to install it into a new environment with editable_mode=compat does not work.
uv version
uv 0.4.3 (Homebrew 2024-09-02)

Repro
Create a toy package foo:
mkdir foo
mkdir foo/foo
touch foo/__init__.py

cat >foo/pyproject.toml <<EOF
[project]
name = "foo"
version = "0.1.0"
EOF

Create a venv and install foo as an editable:
uv venv .venv-1
uv pip install --python=.venv-1/bin/python -e foo
cat .venv-1/lib/python3.12/site-packages/__editable__.foo-0.1.0.pth

# => import __editable___foo_0_1_0_finder; __editable___foo_0_1_0_finder.install()

Notice the content of the above pth is an import hook. That's expected.
But now create another venv and install foo as an editable using --config-setting editable_mode=compat. This should cause the content of the pth file to be a straight path instead of an import hook:
uv venv .venv-2
uv pip install --python=.venv-2/bin/python --config-setting editable_mode=compat -e foo
cat .venv-2/lib/python3.12/site-packages/__editable__.foo-0.1.0.pth

# => import __editable___foo_0_1_0_finder; __editable___foo_0_1_0_finder.install()

It looks like editable_mode=compat was ignored because we still have an import hook. Now repeat the above but with --no-cache:
uv venv .venv-3
uv pip install --python=.venv-3/bin/python --config-setting editable_mode=compat --no-cache -e foo
cat .venv-3/lib/python3.12/site-packages/__editable__.foo-0.1.0.pth

# => /path/to/foo

Now it works. So it looks like --config-setting editable_mode=compat is being passed through dependent on whether we are using the uv cache.

Yeah, I think these definitely aren't included in the cache key.

I think using --reinstall would also work here (or --reinstall-package foo).

I think using --reinstall would also work here (or --reinstall-package foo).

Thanks, this is working and has enabled a workaround

👍 I’m still looking into fixing it as part of some other caching improvements.


Add the value properties.dnsConfiguration to the Resource format.

The value properties.dnsConfiguration was added to the documentation relatively recently, but is not yet listed in the following docs.
https://learn.microsoft.com/en-us/azure/templates/microsoft.web/sites
It would be helpful for users managing configurations in ARM templates and/or Bicep to add properties.dnsConfiguration to the Resource format.

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

ID: 692c2a68-3726-f164-d983-a99e886a16e6
Version Independent ID: 2c5fcf0b-da9e-e2e0-7e2e-ffa5ef365a80
Content: Name resolution in App Service - Azure App Service
Content Source: articles/app-service/overview-name-resolution.md
Service: app-service
GitHub Login: @madsd
Microsoft Alias: madsd

@kogepanh
Thanks for your feedback! We will investigate and update as appropriate.

Hi @kogepanh - we have a PR out to add this to our next API revision. https://github.com/Azure/azure-rest-api-specs/pull/27378
#pleaseclose


Add OpenShift distro in cluster api

Support the following field in our Cluster object
status:
  distribution: OPENSHIFT

Testcases pass
go test .
ok      github.com/cisco-open/cluster-registry-controller/pkg/clustermeta       0.409s

Example

Update (02/09)

Test passed
go test .
ok      github.com/cisco-open/cluster-registry-controller/pkg/clustermeta       0.693s

lgtm

thanks for reviewing folks.

Thanks for review @Laci21


How to access files from the binary

I have built RustPython for DOS, https://github.com/coolcoder613eb/RustPython
And I want to know how make the binary accept files from the command line.
right now it says:

[ERROR rustpython_vm::vm::compile] Failed reading file 'PYBASIC.PY': No such file or directory (os error 44)

Are you sure you are providing the WASI environment with a file descriptor (capability) to the directory? See e.g. https://github.com/turbolent/w2c2/blob/2e9c86f70f2fcf3374d57020389f35ea082fc018/examples/python/main.c#L211-L214
Note that paths are assumed to be WASI paths, which are Unix/POSIX paths (e.g /foo/bar).
What compiler are you using? DJGPP automatically translates Unix paths to the native format (\foo\bar)

Yes, DJGPP, and i think i have fixed it, my solution also means you do not need to write out the full path.
my code in main.c:
#ifdef __MSDOS__
    if (!wasiFileDescriptorAdd(-1, "C:\\", NULL)) {
        fprintf(stderr, "failed to add preopen\n");
        return 1;
    }
#endif
    if (!wasiFileDescriptorAdd(-2, ".", NULL)) {
        fprintf(stderr, "failed to add preopen\n");
        return 1;
    }

    if (!wasiFileDescriptorAdd(-3, "/", NULL)) {
        fprintf(stderr, "failed to add preopen\n");
        return 1;
    }

Not really related, but how would I compile for windows 2000?
CPython3.11, and RustPython without freeze-stdlib, don't work on DOS through w2c2 because of 8.3, is there any solution?

I dont know, haven't tried.


Drops Django upper bound limit

This change facilitates integrating this project into others by removing the Django < 4 restriction. 3.2.16 is LTS though, at the time of writing. Looking particularly at https://github.com/surface-security/surface/pull/38
If we need the pin for a particular reason, please let's document that need in the project somewhere.

Codecov Report
Base: 88.64% // Head: 89.00% // Increases project coverage by +0.35% :tada:

Coverage data is based on head (39dd21f) compared to base (e85810c).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #13      +/-   ##
==========================================
+ Coverage   88.64%   89.00%   +0.35%
==========================================
  Files          14       12       -2
  Lines         511      500      -11
==========================================
- Hits          453      445       -8
+ Misses         58       55       -3

Impacted Files
Coverage Δ

dkron/__init__.py

dkron/urls.py

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

This goes against #6
Major version bumps in Django are usually filled with breaking changes.
We should try to allow packages only to be installed with major versions that we did test (and not necessarily trust test coverage) otherse we'll have open bug reports like #5

Thanks! No, I didn't know these issues. Perhaps it makes sense to document these incompatibilties in the README. Do you know which specific changes are backward incompatible? While on it, is incompatible from upstream (Django) or this app? If the latter, perhaps we can do the necessary changes to make it work? 🤷♂

I only meant in general, having gone through django 1to2 and 2to3 migrations.
I haven’t tried django 4 yet, only that issue (which doesn’t really provide details).
I would say that for any given app, if we’re happy with the test coverage, we could rely on it; but in this case it’s clear coverage wasn’t enough.
I suppose we’d have to try django 4 with the test app and understand what is not working exactly. And then create a regression test for that, in case we make the changes to support django 4

Dropping this PR for now, as discussed above, until we have some form of integration tests.
For the time being, I'll just try to add support for python 3.11 and stick with the Django <4 pin.


Create hook to auto-scale font size to fit into the parent container

Created a hook that takes two refs (parent container & text container). And then checks if the text container is overlapping the parent, then some action is required (resizing). And it will resize the font until 6px, as it will be impossible to read after that. Instead, it informs the text container to break anywhere when there is a text overflow, while adding hyphens for more clarity of the word break.
I have tested it with the longest known name (according to google, it is "Hubert Blaine Wolfeschlegelsteinhausenbergerdorff Sr."). And even Mr. Hubert can now see his name displayed properly on our profile page.
I have not added any tests for it, as TDD and css can get really messy; add hooks & refs into the blunder and you have a very hard test.
Closes #1730.

Web frontend checklist

[x] Formatted my code with yarn format && yarn lint --fix
[x] There are no warnings from yarn lint
[x] There are no console warnings when running the app
[ ] Added any new components to storybook
[ ] Added tests where relevant
[ ] All tests pass
[x] Clicked around my changes running locally and it works
[x] Checked Desktop, Mobile and Tablet screen sizes

This is a really cool hook, but I think word-break: break-word (god css wrapping is a mess) might do the trick?

A simple word-break does the trick yes, I believe it has to be anywhere
though not break-word.
I think i misunderstood the requirements as I took it too literal maybe,
because the ticket mentioned being able to scale down font size dynamically
when it overflows.
In that case I'll do the required changes and do another review request.
On Sun, Feb 6, 2022, 23:57 Lucas Levin @.***> wrote:

This is a really cool hook, but I think word-break: break-word (god css
wrapping is a mess) might do the trick?
—
Reply to this email directly, view it on GitHub
https://github.com/Couchers-org/couchers/pull/2509#issuecomment-1030944649,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB3CD5AMJ7AUVRU7GOD3OQ3UZ4DGTANCNFSM5NV4EYSQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

just make sure to check caniuse.com - from memory the most "correct" option isn't supported on mobile ios or something (typical 🤣 )

I've removed the created hook, and replaced it with simple CSS properties word-break: 'break-word'; overflow-wrap: 'break-word';.
This should do the trick, it is supported across all browsers.


flex_layout_test.dart in layers example is flaky on Windows

First seen in presubmit on AppVeyor for https://github.com/flutter/flutter/pull/16307
00:06 +10 -1: C:\projects\flutter sdk\examples\layers\test\smoketests\rendering\flex_layout_test.dart: layers smoketest for rendering/flex_layout.dart [E]
  'package:flutter/src/rendering/flex.dart': Failed assertion: line 439 pos 18: 'textDirection != null': Horizontal RenderFlex with multiple children has a null textDirection, so the layout order is undefined.
  smoketests\rendering\flex_layout_test.dart 12:60       main.<fn>.<fn>
  package:flutter/src/foundation/assertions.dart 408:14  FlutterError.reportError
  package:flutter/src/scheduler/binding.dart 992:20      _RenderingFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding._invokeFrameCallback
  package:flutter/src/scheduler/binding.dart 930:9       _RenderingFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding.handleDrawFrame
  package:flutter/src/scheduler/binding.dart 842:5       _RenderingFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding._handleDrawFrame

  This test failed after it had already completed. Make sure to use [expectAsync]
  or the [completes] matcher when testing async code.
  smoketests\rendering\flex_layout_test.dart 12:60       main.<fn>.<fn>
  package:flutter/src/foundation/assertions.dart 408:14  FlutterError.reportError
  package:flutter/src/scheduler/binding.dart 992:20      _RenderingFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding._invokeFrameCallback
  package:flutter/src/scheduler/binding.dart 930:9       _RenderingFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding.handleDrawFrame
  package:flutter/src/scheduler/binding.dart 842:5       _RenderingFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding._handleDrawFrame

Ran into this twice in the past day


Web UI not showing position updates

Expected Behavior
Seeing updated position on the web ui as bot runs
Actual Behavior
Nothing moves
Web browser reported many errors with
socket.io-1.4.5.js:1 GET http://localhost:8110/socket.io/?EIO=3&transport=polling&t=LPyOSX0 404 (File not found)
Is it something to do with greenlet and socket.io not working? (It was working yesterday though)
###userdata.js
var userInfo = {
users<EMAIL_ADDRESS>userZoom: true,
zoom: 16,
userFollow: true,
gMapsAPIKey: "KEY",
botPath: true,
actionsEnabled: false
};
Steps to Reproduce
I am on the dev branch.
Run bot and open the web ui
I did find some error around socket.io
<IP_ADDRESS> - - [11/Aug/2016 21:27:17] code 404, message File not found
<IP_ADDRESS> - - [11/Aug/2016 21:27:17] "GET /socket.io/?EIO=3&transport=polling&t=LPyN4Vz HTTP/1.1" 404 -
I already tried pip install -r requirements.txt and don't see anything on dev that can break this...
It was working on commit 0f2bddd26675c5232b2e9f4e83dc6525c41a842d but broken on 138b66413e45efcef1ae015388b80a2725e7a7d8
Other Information
OS: Ubuntu
Git Commit: 138b66413e45efcef1ae015388b80a2725e7a7d8
Python Version: 2.7.11

#3622

#3546


Implement load template utilities to load workflow templates

Rename this PR to something like Implement load template utilities to load workflow templates. Also, add some comments and description about this PR, similar to what you have done for PR #686

This PR was used to make users more convenient to load the whole workflow instead of drag and drop the operators one by one. When the user clicks on the corresponding button attached on the navigation bar. There will be a whole connected workflow shown in the paper automatically.


Update README.md

add Prepare development environment details
add Preparation for Ubuntu installation details
add Setup Dualboot details

This PR close https://github.com/ye-sumteng/development-setup/issues/1


site: Tab in-app example theme setting

Bug
Expected behavior
Tab "in-app example" on the site should be visible in the default 'dark' region.
Actual behavior

Looks like the 'light' theme is on

Fixed. deployed.


remove unused plugin for Spring

Description
Remove unused plugin for Spring
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

API change check
API changes are not detected in this pull request.

Hi @mssfang @JonathanGiles @alzimmermsft @srnagar , could one of you help approve the changes in code-quality-reports?


ci(binding/swift): Don't use release build for develop

It takes up to 10 mins to build swift binding in CI. Maybe we don't need to use release build for develop.
cc @unixzii, what do you think?

Yep, I think we can use debug build for CI.
By the way, I feel like macOS host is slower than Ubuntu host almost every time the pipeline is triggered. Do you think we should remove it?

By the way, I feel like macOS host is slower than Ubuntu host almost every time the pipeline is triggered. Do you think we should remove it?

I'm fine with this change. We can add it back if we have users from macOS.

Ok, I will file a PR for that.

Ok, I will file a PR for that.

Thanks!


Create form-groups-email-form-group.html

Here is the component I have built-

Good job @rohan9024
Congrats 🎉, your PR got merged. To be eligible for the swags from ClueLess. Follow this steps.

Star this repository. ⭐
SignIn / SignUp in [ClueLess Website](https://www.clueless.tech/) .
Go to profile section from the top right hand corner.

Comment your profile URL under this comment tagging the person who merged your PR.

That’s it. Follow the leaderboard !
And don’t forget to share your achievement with your friends.


use Null for NaN in Double::to_json()

Fixes #1235

Pull Request Test Coverage Report for Build 3930
Details

0 of 2 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.01%) to 79.872%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

builtin/json.mbt
0
2
0.0%

Totals

Change from base Build 3927:
-0.01%

Covered Lines:
4357

Relevant Lines:
5455

💛  - Coveralls


Reload integration from UI & bugfix

A small update for the integration that should make using it a lot more convenient:
init.py

Implement async_unload_entry to enable reloading the integration
Add remove_unavailable_entities and remove_unused_devices to avoind orphaned devices/entities when function blocks are removed in Config.
Removed loading the SCENE platform and let it load as a standard platform from const.py

api.py
Add reconnect try/catch to avoid connecting to MS after the connection was closed
climate.py
Solve this warning:
Entity None (<class 'custom_components.loxone.climate.LoxoneAcControl'>) implements HVACMode(s): off, auto and therefore implicitly supports the turn_on/turn_off methods without setting the proper ClimateEntityFeature. Please create a bug report at https://github.com/JoDehli/PyLoxone/issues

I tested this on my system and works when removing/adding function blocks in Config and then reloading the integration instead of rebooting HA.
Maybe someone else can try and test?

@gigatexel thanks for your help. But can you make one pull request for one feature. For example one only for the reload and one for removing entities and so on. I try to make branches from your pull request and cherry pick your commits.

@gigatexel I think in the newest pyloxone this was already fixed:
Entity None (<class 'custom_components.loxone.climate.LoxoneAcControl'>) implements HVACMode(s): off, auto and therefore implicitly supports the turn_on/turn_off methods without setting the proper ClimateEntityFeature. Please create a bug report at https://github.com/JoDehli/PyLoxone/issues

@gigatexel why do we need this:

Add remove_unavailable_entities and remove_unused_devices to avoid orphaned devices/entities when function blocks are removed in Config

If something changes you can manually delete it from the entities and devices menu. I think it is not a good idea to delete it automatically without the user interaction. Sometimes a platform has an error an all devices a unavailable. And if you delete them automatically I do not know what happen with the history of this device. Maybe the user wants this entity or device and all the data which the system collected for this devices.
An option could be to provide a service for both or one service which triggers both functions in a row. So the user can decide to call it once or even in a automation.

@gigatexel maybe you can make another pull request with a service for both functions.

@gigatexel for now I will not include the reloading as it is not stable at all. I tried it a view times to implement and could get to work reliable. What I learned from the last 12 years of maintaining this small integration is that if it is not working reliable do not implement it. You have much more trouble and work.


Basic binary tree with traversals.

Basic binary tree with traversal algorithms working. Hardcoded inputs for now, will be adding more functions and custom input in the following days.

% python3 trees/python/binary_tree.py
Traceback (most recent call last):
  File "/Users/cclauss/Python/binary_tree.py", line 65, in <module>
    tree.pre_order_traversal(tree.root)
  File "/Users/cclauss/Python/binary_tree.py", line 17, in pre_order_traversal
    self.PreOrderTraversal(self,nnode.leftchild)
AttributeError: 'BinaryTree' object has no attribute 'PreOrderTraversal'

Sorry bout that, fixed now.

Let’s not be in rush to merge a PR that has failing tests.
When I run the program, I expect to see 1, 2, 3 or 1, 3, 2 or 2, 1, 3, or 2, 3, 1 or 3, 1, 2 or 3, 2, 1 for each traversal.  I just see 1s so the results are unclear to me.

Let's make sure that the output matches https://www.geeksforgeeks.org/tree-traversals-inorder-preorder-and-postorder or some other trusted source.

Hi @cyberwizard1001,
Sorry about this, please move the file to algorithms/Python/tree folder

Sure. I'm not sure why this doesn't work, was working before I pushed and altered. I haven't changed the algorithm or how it works so not sure what the issue is. Will close this commit, work out the issues and reupload when I'm sure it works.

We have had changed it by this discussion #206

tree = BinaryTree(1)
tree.root.left = Node(2)
tree.root.right = Node(3)
...
tree = BinaryTree(1)
tree.root.left_child = Node(2)
tree.root.right_child = Node(3)


Unable to approve permission request when widget is blocked by pop-up window

Precondition: your account shouldn't have permissions to post reactions on selected website

Login on the published website through nsec.app (ex. https://leafes47.npub.pro/)
Try to post reaction using actions menu

expected: pop-up window with permission request is open
actual: permission request is sent, but need to open nsec.app manualy to allow requested permissions
UPD: Now i see there is a request on the login module but its impossible to press while reaction select and postiong reaction pop-up is present (it's blurred and unavaliable to click). So when user try to post reaction he will face endless load on the reaction post.

Due to the way the dialog works, we can't simply open our own dialog on top of the dialog, as this will block clicks on the document.
We need to learn to detect an already open dialogue and open your own on top of it.

@a-fralou, is it possible to trigger a pop-up browser window for a signature request without the user clicking a button in the widget? If so, what problems could this potentially cause?

@nostrband now after login  tag is still active and cover all the elements on the site and make it impossible to interact with a website until a page reload
Steps to reproduce:

Login using login widget
Observe that site is covered behind  tag

https://jam.dev/c/f8b2d893-3c85-4307-a939-1464384456cd

Fixed with nostr-login 1.6.11, please check on the same site.

Fixed with nostr-login 1.6.11, please check on the same site.

The overlay issue has been resolved. I propose closing this issue.


Fix argument passed to WriteGuidToBuffer

Fixes https://github.com/Azure/azure-sdk-for-net/issues/34834

/azp run net - servicebus - tests

/azp run net - servicebus - tests

/azp run net - servicebus - tests

API change check
API changes are not detected in this pull request.


FAQ intra-links problem when using search

Where to find the issue
On the FAQ page (English and German).
Describe the issue
If you enter a search-term (e.g. "matches") you will be presented with a selection of FAQ entries matching this keyword. If those entries (e.g. the one for "What do the exposure check logs show?") contain a link to another FAQ entry, left-clicking this link will not open the linked FAQ entry if the linked entry is not also part of the search results selection (opening the link in a new tab works though).
Suggested change
Clicking (or tapping on a smartphone) should bring you to the linked FAQ entry.

Thanks for your report @daimpi! In my eyes, this was a critical issue and I did publish a hotfix to restore this basic functionality.


travis: apache2 xsendfile installation

FIX Adds apache2 xsendfile package to installation process.
(addresses #2857)

Signed-off-by: Leonardo Rossi<EMAIL_ADDRESS>

/home/travis/virtualenv/python2.7.9/lib/python2.7/site-packages/nose/plugins/manager.py:395: RuntimeWarning: Unable to load plugin pylons = pylons.test:PylonsPlugin: No module named pylons.test

@jirikuncar  Do we need to add this module on setup.py?

@hachreak: I think that's an instance of this bug: https://github.com/nose-devs/nose/issues/874.
In fact, removing the second stanza in lib/python2.7/site-packages/fixture-1.5.1-py2.7.egg-info/entry_points.txt removes this warning.


jamiepg3

VSCode Version: Code 1.8.1 (ee428b0eead68bf0fb99ab5fdc4439be227b6281, 2016-12-19T14:49:23.350Z)
OS Version: Windows_NT ia32 10.0.14393
Extensions:

Extension
Author
Version

csharp
ms-vscode
1.6.2

vscode-icons
robertohuertasm
7.0.1

Steps to Reproduce:

What issue are you experiencing @jamiepg ?

Needs more info


new: add capture_open/capture_close hooks

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area plugin-sdk

/area tests

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

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: mrgian
Once this PR has been reviewed and has the lgtm label, please assign leodido for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

There is not a label identifying the kind of this PR.
Please specify it either using /kind <group> or manually from the side menu.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

/hold

LGTM label has been added.  Git tree hash: ae9739c3f1de4cfb03db68c37c71e63fb003c068

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP, mrgian
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/unhold
Since this relies upon libs 0.18.1 we can go now :)


Enable export of selections

As an user, I would like to be able to export selected code as a pdf document. Multiple selections should be joined together.

This issue has been fixed in #20. If anyone encounters any issues, they are kindly asked to open an issue.


HYPR Authenticator UI doesn't align with the UI

Describe the issue:

How to reproduce:

Configure HYPER Authenticator https://docs.google.com/document/d/13Y3h9k3d1WSLOHwSuRx4JLbe9c3MahSxjhtfv5D92lI/edit#heading=h.b6b5qscuf6a3
Add the authenticator to the sign-in flow.

Expected behavior:
The UI should be aligned with the rest of the login pages.

Environment information (Please complete the following information; remove  any unnecessary fields) :

Product Version: [e.g., IS 5.10.0, IS 5.9.0]
OS: [e.g., Windows, Linux, Mac]
Database: [e.g., MySQL, H2]
Userstore: [e.g., LDAP, JDBC]

Optional Fields
Related issues:

Suggested labels:

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


time logging via tago

@rultor release, tag is 0.0.49

@rultor release, tag is 0.0.49

@yegor256 OK, I will release it now. Please check the progress here

@rultor release, tag is 0.0.49

@yegor256 Done! FYI, the full log is here (took me 8min)


Unhandled exception

I tried to obfuscate a multiple of libraries and Obfuscar ends with this unhandled exception:
Saving assemblies...Unhandled exception. System.ArgumentException: Member 'System.String {3E2C000D-8452-4A5D-97AD-A33B5C7FF3A5}.D49B2F18-BFB2-4609-B9D1-53B45A0174B1:: ()' is declared in another module and needs to be imported
at Mono.Cecil.MetadataBuilder.LookupToken(IMetadataTokenProvider provider)
at Mono.Cecil.Cil.CodeWriter.WriteOperand(Instruction instruction)
at Mono.Cecil.Cil.CodeWriter.WriteInstructions()
at Mono.Cecil.Cil.CodeWriter.WriteResolvedMethodBody(MethodDefinition method)
at Mono.Cecil.Cil.CodeWriter.WriteMethodBody(MethodDefinition method)
at Mono.Cecil.MetadataBuilder.AddMethod(MethodDefinition method)
at Mono.Cecil.MetadataBuilder.AddMethods(TypeDefinition type)
at Mono.Cecil.MetadataBuilder.AddType(TypeDefinition type)
at Mono.Cecil.MetadataBuilder.AddTypes()
at Mono.Cecil.MetadataBuilder.BuildTypes()
at Mono.Cecil.MetadataBuilder.BuildModule()
at Mono.Cecil.MetadataBuilder.BuildMetadata()
at Mono.Cecil.ModuleWriter.<>c.b__2_0(MetadataBuilder builder, MetadataReader _)
at Mono.Cecil.ModuleDefinition.Read[TItem,TRet](TItem item, Func3 read)    at Mono.Cecil.ModuleWriter.BuildMetadata(ModuleDefinition module, MetadataBuilder metadata)    at Mono.Cecil.ModuleWriter.Write(ModuleDefinition module, Disposable1 stream, WriterParameters parameters)
at Mono.Cecil.ModuleWriter.WriteModule(ModuleDefinition module, Disposable`1 stream, WriterParameters parameters)
at Mono.Cecil.ModuleDefinition.Write(String fileName, WriterParameters parameters)
at Mono.Cecil.AssemblyDefinition.Write(String fileName, WriterParameters parameters)
at Obfuscar.Obfuscator.SaveAssemblies(Boolean throwException) in C:\Users\lextudio\source\repos\obfuscar\Obfuscar\Obfuscator.cs:line 296
at Obfuscar.Obfuscator.RunRules() in C:\Users\lextudio\source\repos\obfuscar\Obfuscar\Obfuscator.cs:line 137
at Obfuscar.Program.Main(String[] args) in C:\Users\lextudio\source\repos\obfuscar\GlobalTools\Program.cs:line 115

Any issue was reported earlier but I didn't have time to finish reviewing/testing it, https://github.com/obfuscar/obfuscar/pull/341
See if it resolves the exception for you.

Hello Lex, thank you very much for your response. The case #341 was closed as solved at 13 Sep 2021 and I am using latest nuget package 2.2.33 from the 15th of January 2022. So, it should be solved in this version or not?

No. 2.2.33 does not include the changes from #341, and that's why I asked you to try it out.

Hello Lex, sorry for delay, I downloaded the obfuscar repository, dependencies and made succesfull build. I added also build result path into path system variables, so I am able to run obfuscar from there. I have still postbuild activity for release build like in the case of trial, where original issue happened. The obfuscar behaviour is different now. It has some problem with paths.This is build output I have now:
20>Note that Rollbar API is enabled by default to collect crashes. If you want to opt out, please run with -s switch
20>Loading project Obfuscar.xml...
20>An error occurred during processing:
20>Unable to find assembly:  .\bin\Release\net6.0-windows\AppName.dll
20>Failed to resolve assembly: 'PresentationFramework, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
Is there some special settings needed if I do not install obfuscar from nuget? I tried also to start obfuscar outside VS from console in project folder (where is the "bin" placed). Then in the build folder and result is stil the same. These two backslash characters in the error message seems suspicious to me. But do not know where they come from. XML file is the same as in the beginning :(

Instead of compiling from source code you can now use 2.2.35 release which contains the patch from #341 .

Hi Lex, thank you for information.


Why I can't initialize rtcEngine?

Hi there,
i got task to implement voice calling using react-native-agora, i have try the documentation instruction
https://docs.agora.io/en/voice-calling/get-started/get-started-sdk?platform=react-native
and this example https://github.com/AgoraIO-Extensions/react-native-agora/blob/main/example/src/examples/basic/JoinChannelAudio/JoinChannelAudio.tsx
but still, i get an error like this

You should disable the debug mode

you can refer to https://reactnative.dev/docs/next/native-modules-android#synchronous-methods


PATH and other environment variables convolute between sessions

It seems the terminal when opened under subsequent, but concurrent Visual Studio sessions gets environment from the first one that was open.
Reproduction:

On cmd, set PATH=c:\foo\bar;%PATH%, run devenv
Open Whack Whack on VS, and notice the PATH is as expected.
Leave it open.
On ANOTHER cmd, set PATH=c:\bar\grill;%PATH%, run devenv
Open Whack Whack on that new VS, while the other unrelated VS session is running. And notice the PATH has c:\foo\bar, but not c:\bar\grill.

Note: Issue #6 is talking about a similar symptom (I think). However, typing exit on the terminal of the second devenv does not fix this issue. When the terminal comes back open, it is still using the environment from the first session.

This might be an issue with servicehub. I'll look into it.


Switch from fprobe to softflowd

Softflowd seems to be the more reliable tool compared to fprobe.
Use softflowd now as a more or less straight replacement. Change
some of the comments in the code to not reflect the tool fprobe
anymore but either refer to a 'flow probe' or 'softflowd' if it's
about the program name.
Only use one timeout parameter for softflowd, the 'maxlife' timeout
parameter that expires all flows after a few seconds. This avoids
having to provide at least 6 individual parmeters for controlling
timeouts for TCP, UDP, etc. Since softflowd produces netflow V{1,5,9},
we need to adjust this as well from fprobe's V{1,5,7}.
Address some pylint complaints about import order.
Make the building of the container more efficient by reversing the
order of commands.
Signed-off-by: Stefan Berger<EMAIL_ADDRESS>

Codecov Report

Merging #285 into master will decrease coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master    #285      +/-   ##
=========================================
- Coverage   89.31%   89.3%   -0.01%
=========================================
  Files         113     113
  Lines        4229    4228       -1
=========================================
- Hits         3777    3776       -1
  Misses        452     452

Impacted Files
Coverage Δ

...rawler/plugins/systems/fprobe_container_crawler.py
81.9% <100%> (-0.09%)
:arrow_down:

Continue to review full report at Codecov.

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

@stefanberger: added an issue for this as well, as per policies.

Thanks for the changes, will merge when travis completes.


Fix now-dev routes support

Test binary:
https://latest-now-cli.now.sh/download?branch=fix/now-dev-routes

Codecov Report

Merging #2194 into canary will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           canary   #2194   +/-   ##
======================================
  Coverage    4.33%   4.33%
======================================
  Files         245     245
  Lines        8863    8863
  Branches      939     939
======================================
  Hits          384     384
  Misses       8462    8462
  Partials       17      17

Impacted Files
Coverage Δ

src/commands/dev/lib/dev-builder.ts
0% <ø> (ø)
: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 c0ee3f0...b693d62. Read the comment docs.


Add tips for Supervisor user

When configuring Supervisor program to run with Pipenv, for example:
[program:bluelog]
command=pipenv run gunicorn -w 4 wsgi:app
directory=/home/greyli/bluelog
user=greyli

You will get Click's RuntimeError due to the locale issue:
supervisor> tail bluelog stderr
n(*args, **kwargs)
  File "/usr/local/lib/python3.5/dist-packages/pipenv/vendor/click/core.py", line 676, in main
    _verify_python3_env()
  File "/usr/local/lib/python3.5/dist-packages/pipenv/vendor/click/_unicodefun.py", line 118, in _verify_python3_env
    'for mitigation steps.' + extra)
RuntimeError: Click will abort further execution because Python 3 was configured to use ASCII as encoding for the environment.  Consult http://click.pocoo.org/python3/for mitigation steps.

This system supports the C.UTF-8 locale which is recommended.
You might be able to resolve your issue by exporting the
following environment variables:

    export LC_ALL=C.UTF-8
    export LANG=C.UTF-8

It can be fixed by adding enviroment setting in Supervisor's config file:
[supervisord]
environment=LC_ALL='en_US.UTF-8',LANG='en_US.UTF-8'

✨🍰✨


Minimal example test for ProVerif backend

Include a test in the toolchain test harness that checks whether extraction works for the output of  cargo new --lib proverif-minimal.

Ready for review now that I could test locally that the test is correctly picked up by the harness.


Preset loadable profiles

Could be useful to have preset profiles for different phases/experiments

Going to call these "Experiments" or "Experiment Schemas". Select these in the web interface or have a modal to create a new one on the spot, saved in DB


Hovering over bone age tooltip causes chart to crash

Hi team,
Have found a bug when rendering a height chart. When a bone age measurement is present but has a 'null' value comment, the chart throws the following error:
I've fixed this temporarily in our implementation by sending an empty string value to the 'bone_age_text' param of the API.
File: src\functions\tooltips.ts
Proposed fix: check bone_age_label is not null before checking length property.
The error:

Before hovering over bone age:

After hovering over bone age:

Thanks for the contribution @dmc-cambric! Looks great, will release asap

Released in v7.0.5:

https://github.com/rcpch/digital-growth-charts-react-component-library/releases/tag/v7.0.5
<EMAIL_ADDRESS>


only allow secure websockets on transport

This is a bug report/feature or change request/support request
Problem
js-waku currently filters and tries to dial all peers that support websockets on the transport level. this leads to a lot of failures when dialing from browsers.
Proposed Solutions
we can perhaps limit that to only allow secure websockets (wss), but allow non-secure websockets (ws) on localhost if possible.
Notes

ref: https://github.com/orgs/waku-org/projects/2/views/1?pane=issue&itemId=37511644

Moving to in progress as some work has been done by @adklempner:

https://github.com/waku-org/js-waku/pull/1989
https://github.com/waku-org/js-waku/pull/1983


Resolve key error and generate valid geoJSON

From @genhernandez in https://github.com/CityofSantaMonica/mds-provider/pull/63 (which is included in this PR, with some modifications to generate valid geoJSON):

According to http://geojson.org/, the Feature geojson expects
that coordinates be nested under geometry. to_feature was originally
creating objects where the coordinates were not nested, leading to
KeyErrors when extract_point is called.

Before this change:
import shapely
from mds.json import parse_boundary, to_feature, extract_point
from mds.fake import geometry
boundary = parse_boundary('https://gist.githubusercontent.com/rgangopadhya/6b38d2a7af5c75ebda68ce2aa7393f79/raw/be047c39d4e11454fda58abc747aeba30bf88a8c/sm.geojson')
point = geometry.point_within(boundary)
feature = to_feature(point, properties=dict())
extract_point(feature)

Results in:
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/raja/dev/external/mds-provider/mds/json.py", line 44, in extract_point
    coords = feature["geometry"]["coordinates"]

In addition, the resulting feature was invalid geoJSON: type needs to be at the top level as Feature AND in geometry as whatever it needs to be.
After this change:
<shapely.geometry.point.Point object at 0x121005208>

@thekaveman I believe this blocks all users from using this (at least, it did for me) so would be great to get a look over this. It's possible that the simpler fix is to pin a version of shapely.

This looks good pending that minor quotes change. Thanks for the catch, and the patience in awaiting review.

Thanks @thekaveman, done!


Bug with interface derivation references

class Foo : ITypeParams, IBar
Both IBars are recognized as interface derivation. The first should just be reference.

Verified this is not an issue with e6f055b732710bad7f30c7ddf5aaacc568246d0c


Performance of transitivity checks

The new ValidatedTransaction provides schema validation at commit time.
Among others the transitivity property must be validated for every property of type owl:TransitiveProperty.
This leads to very high delays when committing and thus validating a transaction, because for each node reachable from any node directly accessed by the transaction object, every node reachable through a transitive property path must be checked.
To make things worse SPARQL does not support property path expressions for unbound variables, which results in a lot of subsequent queries.
Also a single LDPath expressions can't be used, because they are not expressive enough.
In order to improve the performance of the validation, I will try the following:
Instead of the normal ObjectConnection the transaction could use a TrackedObjectConnection which duplicates every modification made into a special context (graph).
For SPARQL UPDATE queries the same query is also executed again for the special context.
SPARQL DELETE queries can be transformed to an INSERT query to the special context.
At commit time the set of all nodes in the special context should be exactly the set of nodes modified by the transaction (directly or with setter-methods).
Then for each modified node an iteration backward and one forward until the next unmodified node is necessary in order to check transitivity.
This procedure doubles the cost for every modification done with the transaction, but drastically reduces costs for checking transitivity in only partially modified regions of the graph.

The time needed for validating a graph was reduced by two improvements to the transaction:
First special "working" contexts were introduced in order to be able to determine the set of affected resources at commit time. ContextAwareConnection (base class of ObjectConnection) features the definition of a context, which receives all inserted statements regardless of their actual context. Furthermore a archive context can be defined, receiving all triples that were removed from any other context.
Currently this approach comes with a drawback: Because statements from any context are inserted into the working graph, information about their actual context is lost. So after commit all statements from the working context are copied to the default graph of the repository.
Second  a new approach was used to improve performance of the transitivity check.
Instead of recursively checking all edges using multiple queries, the check now uses a single query.
The query performs the transitivity check inductively and its runtime is linear dependent on the number of actually affected resources (not the graph size as before).

It turned out that tracking removed statements using a archive context does not work out in Anno4j.
Thus the tracking of resources affected by a transaction is now implemented (see feb8292d8fa7d1754d876e4ad0ae9bae5e7ea4ff) using the set of cached resources of the ObjectConnection (which is probably even more elegant).
These cached resources and their direct neighbours are considered for validation, which enables short validation times.
Note:
Unfortunately the ValidatedTransaction inherits the ignoring of context from the normal Transaction (see #140).

Short node on the implementation of the transitivity check for later reference:
The check is performed inductively and requires that the repository was consistent regarding the schema before the transaction started.
At commit time all affected resources and their direct neighborhood are identified (s.a.).
Now for each node X with a transitive property p the following is checked:
∀ Y : (X, p, Y) ⇒ p(Y) ⊆ p(X) with p(X) the set of objects of triples (X, p, ?o).
If the check is satisfied for X then for any Y holds:

Y was not affected by the transaction and thus is valid by assumption.
Y was affected by the transaction and
-- Y is valid then X is also valid, because X it has all further edges plus the one to Y
-- Y is invalid then the condition is satisfied for X but will fail for Y (induction)


Increase target peers to 100, max peers to 110

Problem description
Gradually all nodes will subscribe to exactly 2 subnets per node due to https://github.com/ethereum/consensus-specs/pull/3312 so it'll not easy to find enough subnet peers
Solution description
We should track different things:

Is it over 110 peers at some time, what's the consequence of that #5732
Network volume, especially when we join a sync committee, only do it once we resolve #5741 ?
Track time to publish a message, especially messages on core topics. See https://github.com/ChainSafe/js-libp2p-gossipsub/pull/451

Additional context
Also other clients already increased to 100 peers (lighthouse, nimbus), lodestar should do the same

@tuyennhv we should review the flood publish strategy into publishing to only a subset of subscribed peers. Can you review other clients strategies? Nimbus runs nodes with 2500 peers and has very reasonable outbound bandwidth

blocked on #5732

need to figure out if it causes more delay when publishing block or not when increasing to 100 peers because we send published messages to all peers, see #6596

need to also take heap snapshot of network thread (when it's >= 2GB) + main thread (after increase target peers to 100). See https://github.com/ChainSafe/lodestar/pull/6556#issuecomment-2017692440


After adding this code, popup of mobile number selection is not displaying.

I have added the your code in my project, but not able to extract the mobile number
I have aded below files at below location android/app/src/main/java/com/xxx/yyy/
DeviceNumberActivity.java
DeviceNumberModule.java
DeviceNumberPackage.java
android/app/src/main/res/layout/
activity_device_number.xml
not able to extract mobile number, please guide me to fix it. if anything is missing please let me know

Try to install the package & follow the doc or the video. It will work. thanks


Simple copy on write skeleton

Aims to eventually close #10954 , alternative to #10973
In the interest of advancing the discussion on this, here's a skeleton of a different copy on write implementation.
Currently
When setting on a view, converts to copy.
 df = pd.DataFrame({'col1':[1,2], 'col2':[3,4]})
 intermediate = df.loc[1:1,]
 intermediate['col1'] = -99

intermediate

Out[8]:
   col1  col2
1   -99     4

df

Out[9]:
   col1  col2
0     1     3
1     2     4

Chained-indexing will ALWAYS fail.
df = pd.DataFrame({'col1':[1,2], 'col2':[3,4]})
df.loc[1:1,]['col1'] = -99
df

Out[11]:
   col1  col2
1     2     4

SettingWithCopy warning disabled, thought not fully removed (figure this is too early stage to really chase that down).
Forward Protection for loc setting (proof of concept, added oct 2):
 df = pd.DataFrame({'col1':[1,2], 'col2':[3,4]})
 intermediate = df.loc[1:1,]

 df.loc[1,'col1'] = -99
 intermediate

  Out[11]:
   col1  col2
0     1     3
1     2     4

Goals / Places I'd love help

We've discussed keeps full-column slices as views, since we can guarantee these will always be views. I created an attribute called _is_column_view that can be set to True when a slice is a full column (e.g. new = df['col1'], but I'm not sure how to actually figure out if a slice is a full column, so right now it's initialized as False and just stays that way.
This has no protection against forward propagation -- situations where one sets values on a Frame and they propagate to views of that Frame. There IS a framework to address it, but it's incomplete. As it stands:

Frames now have a _children list attribute to keep references to their child views.
Before setting, there's a call to a function to try and convert the children from views to copies.
But as it stand, I don't know how to really manage those references (i.e. how to put references to children in that _children list).

@jreback
@shoyer
@JanSchulz
@TomAugspurger

u need to have tests
doesn't matter if it's a demo or not
these are the first things u should write to demonstrate the API

@jreback ok, added!

Added an example of forward protection. NOT generalizable or at all robust, just illustrative for one setting.

This might work in a reasonably efficient way if you make _children a WeakValueDictionary (keyed by object id?). Certainly seems better than using garbage collection in totally ad-hoc ways...

@shoyer would you mind explaining a little more? You mean just a floating global dictionary as opposed to an object attribute?
Main problem I'm having now (love suggestions @jreback @shoyer ): where to place _convert_children() call. Is there a single function that's always called when data is changed where I can put it? Or a short list of functions where it should be put?

The problem with making _children a list is that you can't efficiently remove items from a list.  Great!

this list of _children would only be a very small number of items, so it won't make much difference

I'm still a fan of using WeakValuesDictionary rather than rolling our own
solution.
On Fri, Oct 2, 2015 at 2:52 PM, Jeff Reback<EMAIL_ADDRESS>wrote:

this list of _children would only be a very small number of items, so it
won't make much difference
—
Reply to this email directly or view it on GitHub
https://github.com/pydata/pandas/pull/11207#issuecomment-145164341.

well if you get it to work, all ears.
if you do
a = df['foo']

you don't have a ref, so not really sure what you are trying to track

That's the one case we wanted to stay as a view (full column slices) right?
So that might be a feature not a bug...
On Fri, Oct 2, 2015 at 3:06 PM Jeff Reback<EMAIL_ADDRESS>wrote:

well if you get it to work, all ears.
if you do
a = df['foo']
you don't have a ref, so not really sure what you are trying to track
—
Reply to this email directly or view it on GitHub
https://github.com/pydata/pandas/pull/11207#issuecomment-145167299.

Also: I don't yet understand the internals well enough to know where all I
need to put self._children.append() and _convert_children() -- this is just
an attempt to figure out the machinery in one specific case of subsetting
and setting. Guidance on bottlenecks for where to put those calls to cover
all cases would be much appreciated.
On Fri, Oct 2, 2015 at 3:10 PM Nick Eubank<EMAIL_ADDRESS>wrote:

That's the one case we wanted to stay as a view (full column slices)
right? So that might be a feature not a bug...
On Fri, Oct 2, 2015 at 3:06 PM Jeff Reback<EMAIL_ADDRESS>wrote:

well if you get it to work, all ears.
if you do
a = df['foo']
you don't have a ref, so not really sure what you are trying to track
—
Reply to this email directly or view it on GitHub
https://github.com/pydata/pandas/pull/11207#issuecomment-145167299.

@jreback @shoyer OK, I think this is getting close to working... Will keep working on this, but if anyone has any input or sees problems, input appreciated!

@shoyer @jreback OK, now keeps dictionary-like column slices (v = df['col1']) as views as our one special case.

Moving to new thread:


java.net.SocketTimeoutException: Read timed out

When querying a view using db.queryview api, intermittently, the api returns SocketTimeoutException: Read timed out
Expected Behavior

In a 6 cpu/2G RAM server with ~90K documents (individual document size is small, <1k bytes),  when a view is queried,
the view result shall return
Current Behavior

Intermittently, the api returned SocketTimeoutException: Read timed out.
When looked at couchdb log, we noticed a couple of logs around that time frame:

Update index started (in some cases, for a ~90K document database, the index took more than 30 seconds)
Compaction started (in some cases, compaction seems to start frequently)

Possible Solution

Steps to Reproduce (for bugs)

Context

Your Environment

Version used:
Browser Name and version:
Operating System and version (desktop or mobile): coreOS
Link to your project:

couchdb-short.log

This is not a CouchDB bug.
You have five options:

Using the stale=ok option to querying your view, the response will not wait for the view to finish building.
Improve system performance (faster CPU, more RAM, HDD --> SSD --> NVMe)
Force index updating ASAP on a cronjob or similar so that when queries are made to the view, it is already built
Delay compaction so that it only occurs outside of application usage hours. Put the setting in your local.ini file, here is the documentation in default.ini.
Consider moving to Mango from JavaScript views, as these do not require an external process and are much faster than their equivalent JS view.

Thanks for the recommendations, Joan.
Jimmy
On Fri, Nov 2, 2018 at 1:26 PM Joan Touzet<EMAIL_ADDRESS>wrote:

This is not a CouchDB bug.
You have five options:

Using the stale=ok option to querying your view, the response will
not wait for the view to finish building.
Improve system performance (faster CPU, more RAM, HDD --> SSD -->
NVMe)
Force index updating ASAP on a cronjob or similar so that when
queries are made to the view, it is already built
Delay compaction so that it only occurs outside of application
usage hours. Put the setting in your local.ini file, here is the
documentation in default.ini
https://github.com/apache/couchdb/blob/master/rel/overlay/etc/default.ini#L457-L533
.
Consider moving to Mango
http://docs.couchdb.org/en/stable/api/database/find.html from
JavaScript views, as these do not require an external process and are much
faster than their equivalent JS view.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/apache/couchdb/issues/1707#issuecomment-435448212,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Aac_y5A-MN-42MGpkLyv01NJcY2P_Kc7ks5urI5vgaJpZM4YKZ9l
.


Metro bundler should not watch src folder

Metro bundler is currently watching src folder and will trigger a live-reloading event when there is a ts file being saved. However, we are expecting the event to be only fired after tsc watch compiled src to dist. This conflict causes inconsistency between src and dist until the user saves the file again.
Need to exclude the src folder or only watch dist folder, whichever is more appropriate

since metro bundler supports typescript source files,  all we need to do is (pirateship and actual projects):

not emitting dist folder in tsconfig
set entry point to import src instead of dist folder
And the issue above can be fixed


Egress gateway default is incorrect under NAT port forward auto-associated firewall rules on wireguard interfaces

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[X] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[X] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue
(older report of issue was only closed automatically, not because this was determined not to be a bug or otherwise resolved)

Describe the bug
Port forward NAT firewall rules auto-generated for wireguard interfaces do not route return traffic out of the wireguard interface as they should by default. Instead, they egress using the default gateway which will always result in a broken connection attempt for clients. Interfaces for other vpn protocols such as openvpn have their auto-generated port forward firewall rules egress through the same interface as ingress which is the proper and expected behavior.
To Reproduce
Steps to reproduce the behavior:

Configure wireguard in line with OPNSense official documentation and assign an interface to it along with an associated gateway.
Create a NAT port forward on the newly assigned wireguard interface to any target IP and choose the "Add associated filter rule" option for the "Filter rule association".
Attempt a client connection to the associated wireguard endpoint on the forwarded port. It will time out.

Expected behavior
When "Add associated filter rule" is chosen in the port forward creation, default 'reply-to' behavior should be to egress via the same interface gateway which ingress already traversed, i.e. the wireguard interface. This would align wireguard in feature parity with other vpn protocols such as openvpn.
Describe alternatives you considered
The only alternative at present is to choose "None" for "Filter rule association" during port forward creations on wireguard interfaces and then manually create a firewall rule for the same with 'reply-to' explicitly set to the wireguard interface gateway.
Screenshots
See previously auto-closed issue report: https://github.com/opnsense/core/issues/4389 .
Relevant log files
Can provide packet captures on request which clearly show this behavior but the auto-closed issue 4389 referenced above already had a wealth of information provided so I doubt such additional information would be necessary.
Additional context
N/A
Environment
OPNsense 21.7.3_3 (amd64, OpenSSL).
os-wireguard 1.7
AMD RX-427BB (HP T730)
Intel® I350 (Quad port, copper)

Maybe wireguard isn't the only thing affected by this. I didn't see any specific code for setting the gateway in the source at all, so I would assume that any filter rule created from this would use the default gateway. I could easily be mistaken though. There is even a bit of help text which mentions something similar:

NOTE: The "pass" selection does not work properly with Multi-WAN. It will only work on an interface containing the default gateway.

Regardless, I put this together:
https://github.com/agh1467/core/commit/0ccbcf2d3a46d7865e12064f8370aeb6a161926a
It sets the gateway value for the rule to a (first one found) gateway which is configured on the same interface using the same ipprotocol, otherwise no gateway is set. It has limited scope, and it may be more of a guess, than deterministic. I don't have much experience with the gateways, but I imagine that there are scenarios that are possible which would prevent this from working as expected.
Just an idea for now unless someone wants me to PR.

So this and the other bug referenced here fixed my issue but it is stale? Is this a bug or is this a problem with how we tried to set this up?


Messages with multiple attachments will only return one of the attachments

I think I found the issue --
MessageRepository.getAttachment() accepts an attachment GUID but discards the attachment prefix to perform a lookup based on the "actual" guid. It then queries the database and then calls query.getOne() which return the same attachment every single time.

Moved. I'll fix it

Thanks. I submitted a possible solution here
https://github.com/BlueBubblesApp/bluebubbles-server/pull/546
I haven't tested it yet because I can't get things to build on my system.

PR merged. Should be good now. Hard to officially test, but it was working normally

You can test by sending a message with multiple attachments. It should
return individual images and not the same image multiple times
On Mon, Jul 17, 2023, 6:12 PM Zach Shames @.***> wrote:

PR merged. Should be good now. Hard to officially test, but it was working
normally
—
Reply to this email directly, view it on GitHub
https://github.com/BlueBubblesApp/bluebubbles-server/issues/547#issuecomment-1639124824,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABIRCLCJLOTCLIIL267PVXDXQXPJRANCNFSM6AAAAAAZ63YR6M
.
You are receiving this because you authored the thread.Message ID:
@.***>

The issue was not fixed. And I think the changes broke something more than I thought. Gonna have to revert some of the code and retry it

Fixed again. It's cuz the for loop used "in" instead of "of" and it caused the list of GUIDs to improperly be iterated over. It was iterating over the indexes, not the values.
Just JavaScript things 😁


feat(remove-pr-from-merge-queue): remove non-pending and stale PRs

:pencil: Description
update remove pr from merge queue if the status is not pending and stale
:link: Related Issues

:tada: This PR is included in version 1.56.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


feat req: show password on update:

passes current value to the field if it exists
closes #20

just need to make sure it doesnt overwrite the current password whens saving if nothings changed


kind: Bump kindest/node image to support testing on arm64

Bump kindest/node to v1.19.11 (latest for k8s 1.19) to support testing
on arm64, as arm64 native images have are available with these versions:
v1.14.10
v1.15.12
v1.16.15
v1.17.17
v1.18.19
v1.19.11
v1.20.7
v1.21.1 - v1.21.2
v1.22.0 - v1.22.4
Signed-off-by: Jarno Rajahalme<EMAIL_ADDRESS>

Tests passed on Kind. The AKS test failure looks like an infra issue, so merging the PR.


Quantitative/Text States

Currently, we allow quantitative states which allow users to type anything into the quantitative field (numerical or text).
To allow the customization we promised early on, we "just" need to tweak this.

Continue to provide quantitative fields but allow users to enter their own name to the field instead of just calling it quantity. Restrict to numerical data?
Duplicate quantity field and call it text instead of quantity and allow users to enter text. No numerical restriction.

I have listed this as enhancement, but should be considered core feature for V2 to provide customization we promised.

I agree this is a V2 matter the value of labeling all quantities as quantity has implications for how queries/searches work.


Remove Reactor dependency and context accessor

This commit removes the dependency the ReactorContextAccessor as well as
the whole optional dependency to Reactor, since reactor-core 3.5.0
snapshots now include a copy of said ReactorContextAccessor.
Users shouldn't be impacted, as the accessor is discovered via service
loader.

NB: this PR depends on reactor/reactor-core#3098. It also includes a bump of
spring-javaformat in the gradle.lockfile that was written there by Gradle.


orderByKey not working !!!

so when  I orderByKey(true) then I get error-->  Supplied parameters do not match any signature of call target.
when i remove boolean its okay but its  not sorting my data

Hi @zuandre have you upgraded to version 5 of AF2 yet?

my package json got ----->"angularfire2": "^5.0.0-rc.3",
the orderby key is not taking any parameters but in documentation it takes a boolean parameter

Can you provide some code or a Stackblitz of what's going on?


UF-6122

Adds a new entity for categories with a corresponding controller class.

'CodeQL / Analyze' check is failing. Everything is working as intended locally.

You have compilation errors at IncidentServiceTest (row 180 + 181)
You are using Strings as method parameters. It should be LocalDateTime.
That is why CodeQL is failing.


Modify: TheDocumentFoundation.LibreOffice version <IP_ADDRESS>

Microsoft Reviewers: Open in CodeFlow

Why was the link changed again to downloadarchive, since downloadarchive is not backed by CDN.
Usually same versions which are the latest are usually in https://download.documentfoundation.org/ which is backed by CDN and https://downloadarchive.documentfoundation.org/ isn't backed by it. So there were multiple complaints about abuse of downloadarchive which makes it sometimes painfully slow if you try to download some other version.

Why was the link changed again to downloadarchive, since downloadarchive is not backed by CDN. Usually same versions which are the latest are usually in download.documentfoundation.org which is backed by CDN and downloadarchive.documentfoundation.org isn't backed by it. So there were multiple complaints about abuse of downloadarchive which makes it sometimes painfully slow if you try to download some other version.

I think downloadarchive is also backed by CDN, as I was redirected to a CDN when accessing the installer and there is also mirror list page like https://downloadarchive.documentfoundation.org/libreoffice/old/<IP_ADDRESS>/win/x86_64/LibreOffice_<IP_ADDRESS>_Win_x86-64.msi.mirrorlist which shows all the CDNs supporting the downloadarchive. 🤔

This is quite weird because there where multiple complaints like this #137666 in issues.

This is quite weird because there where multiple complaints like this #137666 in issues.

It might be because the files of the last two versions on archive server are somehow linked to the non-archive server so the former appears to be mirrored. Looking at the mirrorlist page mentioned above, although the file is located on the archive server, all the mirror links go to (the mirrored version of) https://download.documentfoundation.org/libreoffice/testing/24.2.2/win/x86_64/LibreOffice_<IP_ADDRESS>_Win_x86-64.msi, which is on the non-archive server. And since there are also only 4 versions (2 for LTS and 2 for non-LTS) available in the _testing folder, the files of all the other versions on the archive server are no longer mirrored, for example there is only one mirror left for <IP_ADDRESS>.
So users should always be able to download from the mirrors if the package is updated in time, and we no longer have to worry about the links becoming expired.

@SpecterShell So today it got was removed from mirrors for downloadarchive so I already created new PR for the latest version which was released today #151943 151943

@SpecterShell So today it got was removed from mirrors for downloadarchive so I already created new PR for the latest version which was released today #151943

OK thanks! (My automation on this package failed for some reasons 🤔).


Snake-case and kebab-case transformations are slow.

Snake-case and kebab-case transformations are slow.
There is a linked pull request on this topic (https://github.com/circe/circe/pull/940) that still has to be accepted.

That solution is about pre-compiling regular expressions
This solution is about using a fast implementation which can improve the performances x6 at least.

I've tried out jsoniter-scala but it does not support Scala.js at the moment.
Benchmarks:
Current:
[info] KeyCasingBenchmark.snakeCase thrpt 10 ~ 829 556 ± 59956.575 ops/s
With regular expressions pre-compilation:
[info] KeyCasingBenchmark.snakeCase thrpt 10 ~ 1 861 369 ± 52228.706 ops/s
With Jsoniter-Scala:
[info] KeyCasingBenchmark.snakeCase thrpt 10 ~ 10 457 001 ± 52228.706 ops/s
Please feel free to suggest another solution/library.
Thanks

@waiter-melon these functions uses only Java String API and should work with Scala.js.
Feel free to copy code from jsoniter-scala and adopt to your requirements. It's license is compatible with Circe's Apache License just need to leave "License and copyright notice".

Fixed in #940 / #1035.


⚠ SceneTime has degraded performance

In fd8652c, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 3904 ms

Resolved: SceneTime performance has improved in a72cd93 after 6 minutes.


More forgiving syntax

Problem:
It's a bad experience for users every time they encounter a syntax error. It breaks they flow and concentrating cycle.
Solution:
Make the syntax more forgiving: we can have multiple ways to represent the same semantics. Then in the formatter, we format them to the same "suggested" syntax.
Example:
We can support both
 switch x {
  | A => 1
  | B => 2
  };

and
 switch x {
  | A -> 1
  | B -> 2
  };

But in the formatter, we format both of them to
 switch x {
  | A => 1
  | B => 2
  };

I believe there are more cases where we can do this trick.

Mmmmh I'd be more inclined to make the parser a bit smarter to have better errors messages. We could successfully parse -> and error saying it's => that people meant :)

@bsansouci Yes, that's one approach that I was doing before:

But I somehow realize it is a much better experience (at least for me) to have a gentle hand that helps me correct my mistakes every time I save my file (which invokes refmt automatically in emacs) instead of being presented an error saying I'm wrong.

But there are an infinite number of ways to imagine syntax (similar to NLP). Based on my experience in other languages I prefer rigid syntax but forgiveness in types (like Haskell's deferred type errors).

@texastoland My hope is that this can cover some equivalent set for some mostly common mistakes (like mistakenly wrote "->" for "=>").
Haven't really used deferred type errors before. I think they are more for debugging purpose so one can have an easier run-debug-change cycle without fixing all type errors first. A forgiving syntax gives people an easier editing cycle by implicitly fixing user's errors.

I think I originally got this experience from Go's formatter -- trailing semicolon is automatically removed instead of being reported as an error.
As an example, try click the "format" button here: https://play.golang.org/p/k0mVyIKiFO

@yunxing I really don't enjoy optional semicolons... I don't think it's helpful to have optional things / multiple syntaxes for the same thing because you're putting the burden of choice on the user. Here the burden of having to fix syntax errors is greatly reduced because of the tooling anyway. Accepting -> and transforming it to => seems too loose. It also doesn't necessarily help you learn that you should just use =>.

Perhaps we could make some exceptions, at least in areas where common mistakes are made. I'm actually more interested in how we are going to figure out these mistakes or if we are going to base everything on a hunch.

@bsansouci Good point on multiple syntaxes. I agree that multiple syntaxes for the same thing are bad because users will have the burden of choice. However I somehow feel in a language with first-class formatter support this won't be a problem. In this special case, instead of providing negative feedback and asking users to remember: "->" is for pattern machining in ocaml and "=>" is for pattern matching in reason, we can tell users (implicitly) that "just keep writing your program, either -> or => is fine, we will correct it to the right syntax for you whenever you save".
Users will learn to use the right syntax eventually because: 1. All the tutorials and examples and even their own codebase will have the right syntax (since the code are formatted) 2. Whenever people run refmt, presumably when they save their file, there will be a visual change on the screen that helps user to notice and remember.

I think this can be uncontroversial if the "forgiven" syntax isn't considered part of the official grammar, and we keep a clear separation between forgiven syntax, and the official syntax. For example, when compiling, we'd want to have an error for -> arrows, but inside the IDE we can tell refmt/merlin to parse forgivingly, and we can tell the user to hit a certain command to automatically fix them. It's a really good teaching/learning opportunity. We just have to find a way to keep the two grammars separate (because, for example, we would always reserve the right to remove any of the forgiving parsings if they end up making the parsing too complicated/conflict-prone ).

We probably should not tell people "you can continue to use this alternative syntax", because we very well may want to use that syntactic pattern for something else in the future, or some other pattern that conflicts with it - we want to manage user expectations that we might not always catch this common mistake, but we'll try for now. Conflict-free syntactic real estate is a limited resource and we can lend it out to allow some errors to be automatically correctable, but we should be able to take it back if needed.

@jordwalke Yes, if we ever do this, we need to be careful to not let user grow the habit of using the alternative syntax. The whole purpose of here is to educate user to user the in a gentle way instead of a way that would break their flow. So hopefully this can indeed educate users.
@bsansouci I hear what you are saying. From my personal experience syntax error is actually an effective way to learn: I remembered to use "=>" after spent x minutes staring at my screen before figuring out "->" is not the right way to do pattern matching in reason. The downside is that I was quite annoyed then and started questioning the syntax.
@SanderSpies Good point. I think in this case it is more from my personal experience and mistakes people around me have made.
Honestly don't know which approach is better. Maybe we can try this trick for one version or two, and see what users think about it?

I think I can be convinced that the formatter should transform -> into => but the parser/compiler should error. That would be nice, but it might make people never really learn and heavily rely on it... The same way I totally rely on my Mac's autocorrect because I got used to it being very good and predictable.

Alright, people have accustomed to => now I think, so I'll close this.
But we should have this spirit for other new syntax we introduce!


Where is the script to preprocess the own dataset

Hello, have you been able to release the script to process our dataset for the OFA model, like the ActivityNet Entity dataset? Thanks for your help.

We don't provide the preprocessing scripts. You can prepare the dataset yourself according to the readme.


[OLD] Simple knots

Creating some simple knots with ascii art and clojure / java graph libraries.

Not created with GH api!


Use Clock#realTime for Open#startedAt

I was trying to debug an issue where a circuit breaker appeared to be stuck open and got confused by the started timestamp.
The documentation says:

startedAt is the timestamp in milliseconds since the epoch when the transition to Open happened

But with monotonic / System.nanoTime() we get an arbitrary duration.
The Timestamp comment also says:

Type-alias to document timestamps specified in milliseconds, as returned by Clock.realTime

In CircuitBreaker#of we could use cachedRealTime by passing the F[FiniteDuration] to SyncCircuitBreaker, but we can't do that in CircuitBreaker#in (we would need F[G[FiniteDuration]].


Update mdoc, sbt-mdoc to 2.2.21

Updates

org.scalameta:mdoc
org.scalameta:sbt-mdoc

from 2.1.5 to 2.2.21.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta" } ]

labels: library-update, semver-minor

Superseded by #210.


generator: PRIVATE GPT / FastAPI + OpenAI

I have installed GARAK tool on kali linux. I want to scan "Private GPT" (LLM Model), which is locally installed on my system and running on local host. Is it possible to scan "Private GPT" for security vulnerabilities using GARAK.
Link for Private GPT:  github.com/imartinez/privateGPT?tab=readme-ov-file
I would really appreciate if anyone can guide/help me.
Thanks

This should work via the REST generator -- you just need to specify the calling convention and point it to the location of your FastAPI endpoint.


Feature 206 sechub analyzer cli

SecHub Analyzer CLI is command line tool, which searches for SecHub markers in files. The markers are:

Start: NOSECHUB
End: END-NOSECHUB

The Analyzer CLI markers are programming language agnostic.

Jeremias Eppler<EMAIL_ADDRESS>Daimler TSS GmbH, imprint

Accidentally opened the pull request before rebasing.


⚠ ClamAV has degraded performance

In 6a74b93, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 531 ms

Resolved: ClamAV performance has improved in f7d5d76.


Remove JSCS check - it's deprecated and replaced by ESLint

cc @wikimedia/services

Coverage remained the same at 88.539% when pulling b1953164aa52ed6a436605662ff1eb0a03dc842e on Pchelolo:deprecate_jscs into 7bacc72ffe9f40a71d47af93f12f88ad0b181314 on wikimedia:master.


fix zipper

In its current state, yarn zip returns zip is not defined. This quick PR fixes that issue by bringing in gulp-zip as zip.

Nice one, thanks!


Remove MPI requirement from logging/replay

MPI is now initialized by the user calling umpire::initialize(MPI_Comm comm) - once it's initialized, MPI information is added to the logging and replay output.
MPI rank is no longer included in filenames.
MPI must be initialized before using any other Umpire resources if using a custom directory for log/replay output.

Looks good!

Also, nothing is lost provided that the first thing you do is access the ResourceManager (which initializes everything).
I would like to address the buffering issue another time - please create a JIRA issue with this concern.


quick fix up for 4.25.0

Fixes compile errors due to some minor changes that came with 4.25
Not sure you want to merge this into 4.24, but this is the default branch atm, so just making a PR for awareness.

Looks nice!


module size

@quasar/quasar-ui-qcalendar 372.0kB
how can I get this down, the umd.min.js is only 53kb, im not sure why my vue cli version is so much larger

import QCalendar from '@quasar/quasar-ui-qcalendar';
import<EMAIL_ADDRESS>
Vue.use(Quasar, {
	config: { dark: true },
	components: {
		...
		QCalendar
		...
	}
 })

These are the released files. I am not sure where you are getting your values from.

vue ui build dashboard

Yes, but you have the UI component installed. This includes the dist folder and the src (in case you want to go that way and use your own transpiler), but that doesn't mean it's all being bundled into your app. Those things are looking at everything in the folder, not what is actually getting included.

webpack visualizer does that yes, but not the build dashboard, its actual bundle size
I only need the month view, could just import that?

No, because the parent QCalendar provides critical methods for calculating start and end dates.

I will think about separating them out and using those methods as a mixing, but it will be a while before with careful consideration.

before adding quasar-ui-qcalendar

with index.css and index.umd.min.js

moving the qcalendar source to my project folder and importing QCalendar directly leads to the correct size
import<EMAIL_ADDRESS>import QCalendar from './qcalendar/components/QCalendar.js';
Vue.component(QCalendar.name, QCalendar);

Interesting why it's like that then. I'll have to consult with @rstoenescu on what's happening. :(

bump, im still using qcalendar by copying the content of the src folder to a qcalendar folder in my project/src folder.
import './qcalendar/css/QCalendar.sass';
import QCalendar from './qcalendar/components/QCalendar.js';
Vue.component(QCalendar.name, QCalendar);

last time i had tried again to use the npm module it still imported all of quasar and qcalendar, creating unnecessary bloat.

I have plans to make things smaller. That would be v3.0. Probably around December. Sorry it has to be delayed until then, but it'll get a good rewrite with tighter optimizations.


Add checking of length of secret before pushing it.

This PR is to fix a bug that has been occurring in #6711 .
If there is a large file in the chart directory, it is now prevented from pushing past the maximum number of characters in Secret.
And, returns an error message.
Note: If you have set the object limit in etcd to 1 MB or more, this change may cause problems.
I don't think it happens very often...

I see, you're right.
I'm sorry for not knowing this.


Missing serialization of extension and extras in SerializeGltfCamera

The function SerializeGltfCamera() is missing the following serialization:
  if(camera.extras.Type() != NULL_TYPE)
  {
    SerializeValue("extras", camera.extras, o);
  }
  SerializeExtensionMap(camera.extensions, o);

Good catch! Now fixed in the master!


Autostopping Proxy with ALB use case

Added a new markdown file to document the use case to configure Autostopping proxy as a downstream of ALB.
The local build is successful.

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


error: cannot convert 'const xsimd::fma3xsimd::avx' to 'const xsimd::sse4_1&'

Describe the bug
Hi,
When I was trying to follow the following docker_ubuntu page to compile the Gluten project.
https://github.com/oap-project/gluten/blob/e012b50e3dc2f082c82b324f0be2b1d6f277511b/docs/developers/docker_ubuntu22.04.md, after running this command ./dev/buildbundle-veloxbe.sh.
I got the following error:
ep/build-velox/build/velox_ep/./velox/common/base/SimdUtil.h:333:63: error: cannot convert 'const xsimd::fma3xsimd::avx' to 'const xsimd::sse4_1&'

Issue was solved by editing the .sh file.

Issue was solved by editing the .sh file.

which file? and how?


⚠ Bofrost.es has degraded performance

In 242b2c7, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1557 ms

Resolved: Bofrost.es performance has improved in 9aeabf7 after 8 minutes.


Simplify resource requirements for load test

This should help a bit with variance of pod-startup times - a bit more context can be found in:
https://github.com/kubernetes/perf-tests/issues/1311#issuecomment-1077405626
It also makes our configs a bit simpler.
/assign @mborsz

/lgtm

@mborsz  - PTAL (I fixed the test by adding default values to simple-deployment.yaml)

/lgtm

/retest


Problem with whitelists/blacklists

If the whitelisted/blacklisted items are named XXX YYY, then any item that matches the YYY in its name gets used.
As an example, setup an exporter for Advanced Processor and it will export every refined storage processor. You can replicate this with most items that are named similarly from the same mod.
After working on this for a long time I did finally figure out that if I turned on Compare Damage in the importer/exporter it then seemed to work correctly when it came to the items name.

Whitelists/blacklists don't compare on name, they compare on the actual item.
Sometimes, several items share the same item ID, thats why it would take the wrong item & thats why you have to compare on damage.