Branch 1.0 cannot import name resnet_v1_block

Hi, guys, I have a problem.
I am using unbuntu14.0, python  2.7 tensorflow 1.0. When I try to train my own model, its hows
from tensorflow.contrib.slim.python.slim.nets.resnet_v1 import resnet_v1_block
ImportError: cannot import name resnet_v1_block
I have down loaded branch r1.0, why I still have this problem Could you give me some advice?

./experiments/scripts/train_faster_rcnn.sh 0 pascal_voc vgg16

set -e
export PYTHONUNBUFFERED=True
PYTHONUNBUFFERED=True
GPU_ID=0
DATASET=pascal_voc
NET=vgg16
array=($@)
len=3
EXTRA_ARGS=
EXTRA_ARGS_SLUG=
case ${DATASET} in
TRAIN_IMDB=voc_2007_trainval
TEST_IMDB=voc_2007_test
STEPSIZE='[50000]'
ITERS=70000
ANCHORS='[8,16,32]'
RATIOS='[0.5,1,2]'
++ date +%Y-%m-%d_%H-%M-%S
LOG=experiments/logs/vgg16_voc_2007_trainval__vgg16.txt.2017-08-30_20-15-09
exec
++ tee -a experiments/logs/vgg16_voc_2007_trainval__vgg16.txt.2017-08-30_20-15-09
echo Logging output to experiments/logs/vgg16_voc_2007_trainval__vgg16.txt.2017-08-30_20-15-09
Logging output to experiments/logs/vgg16_voc_2007_trainval__vgg16.txt.2017-08-30_20-15-09
set +x
'[' '!' -f output/vgg16/voc_2007_trainval/default/vgg16_faster_rcnn_iter_70000.ckpt.index ']'
[[ ! -z '' ]]
CUDA_VISIBLE_DEVICES=0
time python ./tools/trainval_net.py --weight data/imagenet_weights/vgg16.ckpt --imdb voc_2007_trainval --imdbval voc_2007_test --iters 70000 --cfg experiments/cfgs/vgg16.yml --net vgg16 --set ANCHOR_SCALES '[8,16,32]' ANCHOR_RATIOS '[0.5,1,2]' TRAIN.STEPSIZE '[50000]'
I tensorflow/stream_executor/dso_loader.cc:135] successfully opened CUDA library libcublas.so.8.0 locally
I tensorflow/stream_executor/dso_loader.cc:135] successfully opened CUDA library libcudnn.so.5 locally
I tensorflow/stream_executor/dso_loader.cc:135] successfully opened CUDA library libcufft.so.8.0 locally
I tensorflow/stream_executor/dso_loader.cc:135] successfully opened CUDA library libcuda.so.1 locally
I tensorflow/stream_executor/dso_loader.cc:135] successfully opened CUDA library libcurand.so.8.0 locally
Traceback (most recent call last):
File "./tools/trainval_net.py", line 22, in
from nets.resnet_v1 import resnetv1
File "/home/zy/DL/frcnn-py27-tf10/tf-faster-rcnn/tools/../lib/nets/resnet_v1.py", line 16, in
from tensorflow.contrib.slim.python.slim.nets.resnet_v1 import resnet_v1_block
ImportError: cannot import name resnet_v1_block
Command exited with non-zero status 1
1.94user 2.40system 0:01.95elapsed 222%CPU (0avgtext+0avgdata 266500maxresident)k
0inputs+32outputs (0major+40277minor)pagefaults 0swaps

I tested with ubuntu 16.04 and python 2.7 and tensorflow-gpu=1.0.1(installed by conda) in conda environment. By open python and type the following command:
'''Shell
(tensorflow_1_0) jiwen@bigo:~$ python
Python 2.7.13 |Continuum Analytics, Inc.| (default, Dec 20 2016, 23:09:15)
[GCC 4.4.7 20120313 (Red Hat 4.4.7-1)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
Anaconda is brought to you by Continuum Analytics.
Please check out: http://continuum.io/thanks and https://anaconda.org

import tensorflow
from tensorflow.contrib.slim.python.slim.nets.resnet_v1 import resnet_v1_block

'''
It works.
Not a completely same environment as yours but hope this can give you some alternatives.

close as of now. thanks @JRCondeNast !


Update to ruby 2.2.2

Ruby 2.1.5 has a security vulnerability [1]. It is not clear whether it can
be exploited in smartanswers, but perhaps it's easier to upgrade the ruby
version than to investigate the ways to exploit the app.
I also had to switch to psych for YAML parsing as syck does not seem to be compatible with Ruby 2.2.2 at the moment. It's been deprecated for a long time anyway.
Minor syntax changes were required to make smartanswers work with psych,
namely, interpolation can only happen if the string value is surrounded by
quotes. I've ran all regression tests after making the change and the outcomes
have not changed so I'm confident no more changes are required.
[1]- https://www.ruby-lang.org/en/news/2015/04/13/ruby-openssl-hostname-matching-vulnerability/

Is there a reason you chose to upgrade to Ruby 2.2.2 rather than 2.1.6? I'd have been inclined to upgrade to 2.1.6 to resolve the potential vulnerability and then separately upgrade to 2.2.x.

Is there a reason you chose to upgrade to Ruby 2.2.2 rather than 2.1.6?

I was upgrading anyway so why not go with the latest and greatest? :) Based on the commits notes using Syck was just technical debt, so it's good removing it too.

I don't have an issue with upgrading to 2.2.2, but I think you're doing that for a different reason and I prefer to make changes like this as small as possible. Could we not have one PR to address the vulnerability which upgrades to 2.1.6 and another which is effectively the upgrade from 2.1 to 2.2?

Could we not have one PR to address the vulnerability which upgrades to 2.1.6 and another which is effectively the upgrade from 2.1 to 2.2?

What's the benefit of doing that after the fact?

I agree with @floehopper. I'd personally upgrade to 2.1.6 separately to 2.2.2.
Upgrading to 2.1.6 should protect us from any potential vulnerabilities found in the older version and I'd hope the upgrade itself would be uncontroversial and very easy.
The upgrade to 2.2.2 is then a further improvement that's unrelated to any known security vulnerabilities. It also requires other changes in the codebase that I can imagine have the potential to cause us other problems. Should we discover such problems then it'll be useful to be able to rollback to a known good commit that uses 2.1.6.

Is changing the value in '.ruby-version' good enough to start using the new Ruby in CI, preview, staging and production, or do we have to change some puppet/chef recipes somewhere?

Ok, I'll open a new PR with 2.1.6. I'll also investigate in more depth if there are any other required changes for syck -> psych migration. I was told ruby 2.2.2 is already installed on all servers.
Thanks for all comments :)

I was told ruby 2.2.2 is already installed on all servers.

Do you know if we're using rbenv on all the servers too? Presumably we'll have to be for this change to have the desired effect.

Yes we use rbenv and both 2.2.2 and 2.1.6 are currently in use :)

I've opened a PR for 2.1.6 https://github.com/alphagov/smart-answers/pull/1846
and have manually checked some smartanswers that interpolate in question titles and bodies, all appears to look unchanged.

LGTM. It would be good to explain that the motivation behind this upgrade is to use the latest & greatest version of Ruby and not to address the security vulnerability which was done in #1846.
The fact that all the regression tests pass is comforting, but I guess there might still be hidden issues with gems which aren't compatible with Ruby 2.2. Hopefully any serious ones would come to light during the staging deployment.

@tadast: Are you planning to merge this?

My plan was to merge and deploy it after all important things that need to go live have been deployed. This is to reduce the risk of rolling back due to unexpected bugs in the new ruby version.
I will try to deploy this tomorrow if there's anyone from the 2nd line in the office.

@tadast: Sounds good.


Fix centering and spacing of reaction-avatars count

Some work to improve the rendering of reaction counts in the reaction-avatars feature.
Test URLs
https://github.com/microsoft/vscode/issues/124901
Screenshot
Before:

After:

@fregante threw out a bunch of lines with only a 1px regression
I did copy code from flash.scss in #4763 but that was a mistake in retrospect

When sending PRs it's best to avoid reordering CSS properties or else I have to check all those lines unnecessarily. Most lines don't need to be changed here

Sorry, in the habit of sorting alphabetically - almost automatic for me :)

The current code is still wrong. Please don't open more PRs on this issue.
The avatars are no longer overlapped
 <-- before
 <-- after
The -1px margin just messes with the image

While I understand the 4-review limit applies here, it turns out this was a simple matter of:
:root .social-reaction-summary-item .social-button-emoji,
:root .social-reaction-summary-item span:nth-child(2) {
	align-self: center;
	box-sizing: content-box;
}

:root .rgh-reactions span:nth-child(2):not(:last-child) {
	min-width: 16px;
}


[INTERNAL] Travis: Activate Windows and Mac builds

@codeworrior there seems to be an issue with the ComponentAnalyzer tests on Windows:
https://travis-ci.org/SAP/ui5-builder/jobs/454019734#L315
If you find the time, maybe you could have a look?

@codeworrior there seems to be an issue with the ComponentAnalyzer tests on Windows:
https://travis-ci.org/SAP/ui5-builder/jobs/454019734#L315
If you find the time, maybe you could have a look?

Fixed with
https://github.com/SAP/ui5-builder/pull/100/commits/623c5ca3cbc6907cb9b41db30735031dfeeb51d8

Pull Request Test Coverage Report for Build 535

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 53.201%

Totals

Change from base Build 491:
0.0%

Covered Lines:
1473

Relevant Lines:
2506

💛  - Coveralls


Missing messenger_extensions property in Botkit Studio button template

As per facebook's documentation: https://developers.facebook.com/docs/messenger-platform/webview

If your bot uses the Messenger Extensions described in this section, remember to set the messenger_extensions parameter to true in the menu item or button you are invoking it from!

It's currently impossible to add such parameter in the button template in Botkit Studio, and the webview cannot load the messenger extension sdk.
Thanks!

You should be to do this now with customer fields, and custom code in your bot.


implement GetTransactions

TL;DR
Refactored transaction and log querying logic to improve code reusability and add support for aggregations.
What changed?

Introduced a new executeQuery function in the ClickHouseConnector to handle both transaction and log queries.
Added buildQuery and executeAggregateQuery functions to construct and execute queries more efficiently.
Updated GetTransactions and GetLogs methods to use the new query execution logic.
Modified the QueryResult struct to use []interface{} for the Data field, allowing for more flexible result types.
Implemented scanTransaction and scanLog functions to handle row scanning for each data type.

How to test?

Run existing tests for transaction and log queries to ensure functionality is maintained.
Create new test cases that include aggregations in the query filter.
Verify that the QueryResult structure correctly contains both data and aggregates.
Test edge cases with various combinations of filters, sorting, and pagination.

Why make this change?
This refactoring improves code maintainability and reduces duplication by centralizing query logic. It also adds support for aggregations in both transaction and log queries, enhancing the flexibility of the data retrieval process. The changes make it easier to extend functionality for future query types and improve overall code organization.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#48  👈
#44
#43
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @AmineAfia and the rest of your teammates on  Graphite

Merge activity

Sep 26, 6:12 AM EDT: @AmineAfia started a stack merge that includes this pull request via Graphite.


Possible ways to support estargz / improve pull speed

Is there a way support for estargz could be added to the eks AMI? Especially for large images (~12GB) , e.g. for ML training, pulling a private image from the ECR in the same region can take quite long (~2min).

This seems like the gist of the necessary changes: https://github.com/containerd/stargz-snapshotter/blob/main/docs/INSTALL.md#install-stargz-snapshotter-for-containerd-with-systemd
@john-zielke-snkeos If you can share your experience using this feature, it'd be helpful.

Looked like AWS was doing some work in this space: https://github.com/awslabs/soci-snapshotter

I have not yet worked with the estargz, but our ML images can be >10GB in size and this will cause them to take >2 minutes to pull from an ecr in the same region. To reduce latency for training runs, we could either optimize images (which every team would have to deal with), or just implement this and enable faster startup times.
Therefore support for this would be nice.
I saw that AWS is developing soci, but it looks like it's still in an early phase, so I am wondering if that will be ready for use soon. Maybe someone has more insight into how stable that feature is already.

The SOCI snapshotter folks have a doc now that walks through using it on our AL2023 AMI's: https://github.com/awslabs/soci-snapshotter/blob/main/docs/eks.md
We may (eventually) ship the SOCI snapshotter in our AMI, but that's TBD. At this time we have no plans to include the stargz snapshotter.


Add clip to the specification

This PR

resolves https://github.com/data-apis/array-api/issues/482 by adding clip to the Array API specification for clamping each element of an input array to a specified range.
requires that the output data type be the same as the input array. One could argue that the output data type follow type promotion rules (between x, min, max). This would be in the spirit of earlier efforts to ensure that type promotion rules are applied consistently throughout the specification. However, in contrast to https://github.com/data-apis/array-api/pull/201, min and max are kwargs, and we do not have, TMK, any precedent for array kwargs influencing the data type of the output array. Furthermore, when clamping, users are more likely to want an output array of the same data type as the input array (this was also raised on the NumPy issue tracker: https://github.com/numpy/numpy/issues/24976).
allows the input array x to be broadcast, thus allowing the output array to have a rank greater than the input array. This differs from TensorFlow, which requires that the output array shape be the same as the input array shape. NumPy, however, supports such broadcasting behavior. Note that x can be broadcast is somewhat at odds with not allowing type promotion. For the output data type, I argued that min and max should not affect the output data type, but, in allowing x to be broadcast, this would mean that min and max should affect the output array shape. This is likely fine and consistent with the rest of the specification, where we have plenty of kwargs which affect the output array shape, although this would be the first, TMK, involving broadcasting.
specifies that if min > max, behavior is unspecified. NumPy et al set output values to max; however, other implementations should be free to raise an exception or support alternative behavior.
allows both min and max to be optional. When both min and max are None, the function is essentially a no-op. This follows PyTorch, but differs from NumPy which allows min and max be None, but not at the same time.
does not prohibit mixed data types, but leaves behavior unspecified (e.g., when x is an integer data type and min or max is a floating-point data type), which is consistent elsewhere in the specification. TensorFlow raises an exception in such a scenario.
makes min and max keyword-only arguments.
Follows NumPy, JAX, CuPy, and Dask in naming the API clip. TensorFlow uses the name clip_by_value. PyTorch also includes clip, but this aliases to clamp.

Note that this PR would introduce changes to existing clip functionality in NumPy et al. Namely,

min and max are keyword-only arguments; whereas, in NumPy, a_min and a_max are positional.
deviates from NumPy's naming convention of a_min and a_max.
NumPy requires that only one of min or max be allowed to be None at the same time.

I've updated this PR based on feedback from the 30 November 2023 workgroup meeting. Namely,

I renamed the API from clamp to clip. Given widespread usage of this API, it was considered undesirable to rename and deprecate clip in NumPy et al. Even though this PR introduces behavior which differs from NumPy (e.g., kwargs, output data type, etc), it was considered better if NumPy simply moved to adopt specified behavior.
I updated the guidance regarding the output data type to be the same as the input array x and not the result of type promotion. An argument could be made either way; however, as discussed during the workgroup meeting, user expectation is most likely to be that the output data type matches x, and the specification does not have precedent (TMK) for array kwargs influencing the output data type. As such, specification was guidance was updated accordingly. Note, however, that this differs from current behavior in, e.g., NumPy.

@rgommers I've updated min and max to be both positional and kwarg. And I added a note stating that arguments having different data type kinds will result in implementation-dependent behavior.

As this PR has received the OK and has not received any further comments, will go ahead and merge. Thanks all!


[BUG] Network config lost during upgrade from v1.0.3 to v1.1.0

Describe the bug

In upgrade progress, after the first node reboot, I found that I lost the network connection to this node and got an error at harvester GUI Host IP are inconsistent.

And then, I found that I have lost all network scripts in /etc/sysconfig/network.

To Reproduce
Steps to reproduce the behavior:

Click Upgrade at harvester GUI

Expected behavior

Support bundle

Environment

Harvester ISO version: v1.1.0
Underlying Infrastructure: Baremetal with PowerEdge R740 64C64G with 2x 512G SSD

I have exactly the same problem - installed with 1.0.3 and upgraded to 1.1.0 - first node got rebooted and now is stuck here without network:

Related issue: https://github.com/harvester/harvester/issues/2962
cc @guangbochen @ibrokethecloud

@tjjh89017 Do you know if any OS change could lead to this?

I don't think OS will cause this problem. Could you provide /oem/99_custom.yaml for us to debug? Thanks a lot

Send you a PM with a link to my supportbundle - is this sufficient?

I don't think OS will cause this problem. Could you provide /oem/99_custom.yaml for us to debug? Thanks a lot

Send you a PM with a link to my supportbundle - is this sufficient?

You could send it to me first. Let me check it.
But I think the better way is using Linux command to connect the server and then SCP those files to me

@W0n9 can u check if the following workaround would mitigate the issue in your env, thanks

ssh to the harvester0 node
run sudo su and  create a config file under the /usr/local/lib/sysctl.d/ path.

net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1

reboot the node and check if the IPv4 is resumed

@W0n9 Do you use harvester-mgmt as VLAN network interface?
and provide cluster_networks config in deploy stage

@W0n9 Do you use harvester-mgmt as VLAN network interface? and provide cluster_networks config in deploy stage

In v1.0.3, I use harvester-mgmt(bond-alb eno0 and eno1) for Management Network, And harvester-vlan(bond-alb eno2 and eno3) for VLAN Network.
Finally, I did not notice cluster_networks config in upgrade progress, can you share where it should be?

@W0n9 can u check if the following workaround would mitigate the issue in your env, thanks

ssh to the harvester0 node
run sudo su and  create a config file under the /usr/local/lib/sysctl.d/ path.

net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1

reboot the node and check if the IPv4 is resumed
follow the same steps for all of your nodes if it works

I have tried this, but it doesn't recover.
I think the network configuration file was lost during the upgrade.

@W0n9 Could you try this workaround step?
https://github.com/harvester/harvester/issues/3045#issuecomment-1292685394

@W0n9 Could you try this workaround step?
https://github.com/harvester/harvester/issues/3045#issuecomment-1292685394

It seems work for me.
Network recovered.

This looks like possibly the same issue as #3045

net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1

FYI - this is required in any case if there is a IPv6 DHCP server available..
And I am not sure if usr/local/lib/sysctl.d/ is the right place.
I would expect this in /etc/sysctl.d/99-no-ipv6.conf or similar and after creating this fine - execute sysctl -p /etc/sysctl.d/99-no-ipv6.conf

I was able to repro this in a libvirt virtualized environment with two pairs of bonded NICs setup during install. The workaround here brought back up the network and the upgrade seemed to be fixed. However I actually used the script for replacement from here

Close this issue with:

https://github.com/harvester/harvester/issues/2962: Track the IPv6 issues.
https://github.com/harvester/harvester/issues/3047 and https://github.com/harvester/harvester/issues/3045: Track the network interruption issue.

Should we use /usr/local/lib/sysctl.d/  or /etc/sysctl.d/?

@Martin-Weiss yeah, somehow I can't make /etc/sysctl.d/ work even adding it to persistent path in elemental toolkit, thus suggest using usr/local/lib/sysctl.d/  since it's in the man page.


Breakpoint Bug Fixes

Resolves #575 and adamdriscoll/poshtools#254
Summary of changes:

Breakpoints are now removed from the _psBreakpointTable when we remove breakpoints via debugging commands (see RemoveBreakpointById in PowerShellDebuggingService.cs)
Breakpoints are added to the breakpoint manager's _breakpoints table when they are set
_breakpoints is cleared when ClearBreakpoints is called
Call to GetTrueFileName is now in each breakpoint manager method
Added code for breakpoint counting
BreakpointRemoved is actually called now!

@HuanhuanSunMSFT @AndreSayreMSFT

Intentional that _node is part of the hash code but not part of equality?

Just wanted to give the hash code some more randomness. That's all. No good reason to not have _node in equality though, so I'll update that real quick.

Good work.


Adding Wagtail version to Settings sub-nav (#2248)

Added Wagtail version into the bottom of the settings sub-nav, requested in issue #2248

Looks good, thanks! Just one nitpick... as it stands, the version number will be displayed on any submenu derived from SubmenuMenuItem (of which Settings is the only one in the out-of-the-box install, but it's possible to add others through e.g. ModelAdmin). I think it's better for it to only show on Settings.
This can hopefully be fixed fairly easily by subclassing SubmenuMenuItem as SettingsMenuItem, with a custom template. I'll do that now, actually :-)

Merged in daf68f5e2eb6d6995ed0336c4b818c921bb8c171


[Feature Request] expose GUI open event

I want to detect when player "acquire" important items and their functionality.
I found, that if I want to detect complicated stuff like EnderIO Conduits I cannot propertly do this with already existed events:

I cant detect from crafting because player can autocraft it.
I cant detect from placing since player could just use block placers.
I should not detect from PlayerInteractBlockEvent since it would cause false-positive when you accidentally clicked conduit on spawn or just stand too far from block and GUI cancelled.
I cannot detect when player using some weird mechanics that opening GUIs on trigger.

I think, event that expose gui name or something similar would be cool.
I dont know if its possible to expose more information, like if its Inventory GUI and such, but would be good for the future too.

Try this?
https://docs.blamejared.com/1.12/en/Vanilla/Events/Events/PlayerOpenContainer

Oh, yes, its working.. I cant cancel it through, but i think i could use this. Thank you. I really looked through every event possible several times, but somehow missed it 😅

In v1.19.0, you can subscribe all forge events.
#sideonly client
// this a client only event, your script should be client only too.

events.register(function(event as native.net.minecraftforge.client.event.GuiOpenEvent) {
    // your code
});

It is a forge issue. GuiOpenEvent cancellation doesn't work for gui that contains data sync (e.g. item slots). The event only denies the gui from displayed, but it doesn't stop data sync. Server still try to sync the gui contents to client. After you cancel the event, the gui of server and client is different: furance on server side while player invenrory on client side, then the data sync logic produces desync instead. (yea, gui is client only exactly, the thing on server side is called container, to deal with data sync)
So I suggested to PlayerOpenContainer event previously, but it is not cancelable :(
I tried send packet to notify server to close the gui connection. But it takes time, the gui still displayes in one tick.
So even I expose GuiOpenEvent, there still isn't a good way to deny opening a gui. It's better to find a reliable way to use PlayerInteractBlockEvent

I tried to send packet to notify server to close the gui connection. But it takes time, the gui still displayes in one tick.

This solution is actually sounds reliable. Glitchy but players will understand that this happened intentionally. How i could do that with CT?

import mods.zenutils.NetworkHandler;

// in client only script
events.register(function(event as native.net.minecraftforge.client.event.GuiOpenEvent) {
    val guiClass = typeof(event.getGui());
    if ( guiClass == 'net.minecraft.client.gui.inventory.GuiFurnace') {
        NetworkHandler.sendToServer("close_container");
    }
});

// in a plain script
NetworkHandler.registerClient2ServerMessage("close_container", function(server, byteBuf, player) {
    player.native.closeScreen();
});

Oh, wait, PlayerOpenContainerEvent + closeScreen works prefectly
events.register(function(event as crafttweaker.event.PlayerOpenContainerEvent) {
    if (event.container.asString().startsWith("net.minecraft.inventory.ContainerFurnace")) {
        event.player.native.closeScreen();
    }
});


Configure column name

Added option to configure column name, I need to support a table schema created from a different app and need to configure the column name.

@tezmaster that's cool - the only thing I 'd add is to escape the columnName using sqlstring. See, the tableName is automatically escaped using the ?? notation, but columnName isn't.
I shall merge the PR for now and add the escape functionality later.
Cheers,

FYI this is now published on npm under v.1.3.0


[Proposal] Throttling for segment loading in druid coordinator

Scenario - In our metrics cluster, we keep super old data on icy tier without any replication, where we have ~15K+ segments on a single historical node, which accounts to ~ 20K segments on single node. When we reboot these beefy historical nodes, the coordinator tries to load all the segments present on that node onto other available nodes. Since the number of segments is too high, it takes around 4-5 hours for the coordinator to complete single iteration over all the segments while computing cost and finding the best server to load those segments . This delays segment handoff as the coordinator takes snapshot of available segments and iterates over those segments.
As per the current implementation we have a replication throttling limit only while segments are being replicated in the cluster, but since we don't have replication configured for the data in icy tier, the replication throttling does not helps in this case.
The proposal is to add another throttling limit for segments loaded in each tier which would define the maximum number of new segments that the coordinator will try to load in a tier at one time.
Implementation would include -

Adding loadingThrottleLimit to coordinator dynamic config
Modifying loadRule to follow this limit while loading new segments to a tier
proposed Default value for loadingThrottleLimit is 5000. (Its high in order to not alter any existing behavior by default)

I think in general this proposal makes sense but the loadingThrottleLimit should be unlimited by default to keep with the current impl of things.

@fjy if default behavior breaks or has bad side effects over a certain size, it is not clear to me we should keep it.

highly useful and needed feature !!
Speaking about dynamic coordinator configs, there are two further things that would allow for handling many useful usecases:

having the dynamic configs per tier
being able to set a tier's priority dynamically in the coordinator

If something like this is doable and considered reasonable, I would like to create a feature request for this too.

I don't understand why this proposal hasn't been taken up yet. I've been running a large scale Druid cluster and the use case  that nishantmonu51 described in his proposal is a real one and it can cause really big issues.
I haven't been working with Druid in recent years. If the issue raised by nishantmonu51 has become void because of some other feature or change introduced to Druid, then it might make sense to close the issue, but in this case I would appreciate it, if a short comment could be added in here as to how to resolve the stated issue.
If the issue described in the proposal is still valid, I highly recommend to re-open this ticket and prioritise it, as the implementation would be a small effort having a high impact.


support iterative user input of git remote as discussed in #27

@KostyaEsmukov @ahakanbaba I've made the changes as discussed in #27 , I'd appreciate if you guys can review the changes

updated and merged to master, thank you again for your help!


Feat: Secure Sign-Up: Double-Check Your Password / Confirm Password field for registering new user

Describe the feature
Upon entering their desired password, users will be prompted to re-enter it in a  "Confirm Password" field. This will reduce input errors and will ensure the accuracy of user's  credentials, and  further in login section there is no need for this field.
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Hey, if no one is currently there for this issue.
Kindly assign this issue to me.

Have you tried "npm i" first?

yes, even its showing that server is running on localhost 3000 but getting error of routings : cannot get/

@RishabhDhawad
@anuragverma108
please help me in this error , dont  know why its showing like this


Split out VPN troubleshooting topic

OPS Build status updates of commit b9178ea:
:warning: Validation status: warnings

File
Status
Preview URL
Details

toc.json
:warning:Warning

Details

building-blocks/extending-templates/toc.json
:warning:Warning

Details

bread/toc.json
:warning:Warning

Details

docs/reference-architectures/hybrid-networking/hub-spoke.md
:white_check_mark:Succeeded
View

docs/reference-architectures/hybrid-networking/troubleshoot-vpn.md
:white_check_mark:Succeeded
View

docs/reference-architectures/hybrid-networking/vpn.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

toc.json

[Warning] Error happen when converting toc.json to Pdf. Details: Could not find file 'T:\hcbl\toc.json'.

building-blocks/extending-templates/toc.json

[Warning] Error happen when converting building-blocks/extending-templates/toc.json to Pdf. Details: Could not find a part of the path 'T:\hcbl\building-blocks\extending-templates\toc.json'.

bread/toc.json

[Warning] Error happen when converting bread/toc.json to Pdf. Details: Could not find a part of the path 'T:\hcbl\bread\toc.json'.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

OPS Build status updates of commit 8677153:
:warning: Validation status: warnings

File
Status
Preview URL
Details

bread/toc.json
:warning:Warning

Details

toc.json
:warning:Warning

Details

building-blocks/extending-templates/toc.json
:warning:Warning

Details

docs/reference-architectures/hybrid-networking/hub-spoke.md
:white_check_mark:Succeeded
View

docs/reference-architectures/hybrid-networking/troubleshoot-vpn.md
:white_check_mark:Succeeded
View

docs/reference-architectures/hybrid-networking/vpn.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

bread/toc.json

[Warning] Error happen when converting bread/toc.json to Pdf. Details: Could not find a part of the path 'T:\kgvl\bread\toc.json'.

toc.json

[Warning] Error happen when converting toc.json to Pdf. Details: Could not find file 'T:\kgvl\toc.json'.

building-blocks/extending-templates/toc.json

[Warning] Error happen when converting building-blocks/extending-templates/toc.json to Pdf. Details: Could not find a part of the path 'T:\kgvl\building-blocks\extending-templates\toc.json'.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

OPS Build status updates of commit 20b947a:
:warning: Validation status: warnings

File
Status
Preview URL
Details

bread/toc.json
:warning:Warning

Details

toc.json
:warning:Warning

Details

building-blocks/extending-templates/toc.json
:warning:Warning

Details

docs/reference-architectures/hybrid-networking/hub-spoke.md
:white_check_mark:Succeeded
View

docs/reference-architectures/hybrid-networking/troubleshoot-vpn.md
:white_check_mark:Succeeded
View

docs/reference-architectures/hybrid-networking/vpn.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

bread/toc.json

[Warning] Error happen when converting bread/toc.json to Pdf. Details: Could not find a part of the path 'T:\xo3g\bread\toc.json'.

toc.json

[Warning] Error happen when converting toc.json to Pdf. Details: Could not find file 'T:\xo3g\toc.json'.

building-blocks/extending-templates/toc.json

[Warning] Error happen when converting building-blocks/extending-templates/toc.json to Pdf. Details: Could not find a part of the path 'T:\xo3g\building-blocks\extending-templates\toc.json'.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

OPS Build status updates of commit cae1d06:
:warning: Validation status: warnings

File
Status
Preview URL
Details

toc.json
:warning:Warning

Details

building-blocks/extending-templates/toc.json
:warning:Warning

Details

bread/toc.json
:warning:Warning

Details

docs/reference-architectures/hybrid-networking/hub-spoke.md
:white_check_mark:Succeeded
View

docs/reference-architectures/hybrid-networking/troubleshoot-vpn.md
:white_check_mark:Succeeded
View

docs/reference-architectures/hybrid-networking/vpn.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

toc.json

[Warning] Error happen when converting toc.json to Pdf. Details: Could not find file 'T:\y3ty\toc.json'.

building-blocks/extending-templates/toc.json

[Warning] Error happen when converting building-blocks/extending-templates/toc.json to Pdf. Details: Could not find a part of the path 'T:\y3ty\building-blocks\extending-templates\toc.json'.

bread/toc.json

[Warning] Error happen when converting bread/toc.json to Pdf. Details: Could not find a part of the path 'T:\y3ty\bread\toc.json'.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

OPS Build status updates of commit 067ee0d:
:warning: Validation status: warnings

File
Status
Preview URL
Details

toc.json
:warning:Warning

Details

building-blocks/extending-templates/toc.json
:warning:Warning

Details

bread/toc.json
:warning:Warning

Details

docs/reference-architectures/hybrid-networking/hub-spoke.md
:white_check_mark:Succeeded
View

docs/reference-architectures/hybrid-networking/troubleshoot-vpn.md
:white_check_mark:Succeeded
View

docs/reference-architectures/hybrid-networking/vpn.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

toc.json

[Warning] Error happen when converting toc.json to Pdf. Details: Could not find file 'T:\nh1v\toc.json'.

building-blocks/extending-templates/toc.json

[Warning] Error happen when converting building-blocks/extending-templates/toc.json to Pdf. Details: Could not find a part of the path 'T:\nh1v\building-blocks\extending-templates\toc.json'.

bread/toc.json

[Warning] Error happen when converting bread/toc.json to Pdf. Details: Could not find a part of the path 'T:\nh1v\bread\toc.json'.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Degraded performance querying multi-multi map table

Waterline version: 0.11.2
Node version: 5.10.1
NPM version: 3.8.3
Operating system: OSX v10.11.4

This is using sails-mongo as the adapter, but the source of the performance issue seems to come from waterline, not the adapter:
I noticed in our production application that when we query a table generated by waterline for a multi-to-multi association, it was taking quite a bit of time compared to doing a native query. We see roughly 100x improvement in some queries by using a native query over waterline's find(). The reproduction that I made doesn't show that much of a difference, but it does illustrate the issue. Maybe this is just a side effect of using an ORM, but we haven't noticed this large of a performance difference when doing a query on a normal model table.
I traced things down to /query/finders/basic.js in the returnResults function. Specifically, the following code seems to consume the most amount of time:
 data.models.forEach(function(model) {
   models.push(new self._model(model, data.options));
 });

I started losing focus trying to track it down further - so hopefully someone more familiar with the waterline code can help describe what is going on. I'm wondering if it has to do with translating the column name to the model property name, but I wasn't able to get to that code to verify.

ok, fixed!

Repository to reproduce the issue: https://github.com/jgeurts/waterline-issue-1346-multimulti-query-perf

@jgeurts it could be similar to sails-mongo #369. That should probably not be synchronous but would need to keep sort order.


Blank screen causing issues on Windows 11

I’ve been experimenting with flex-launcher on Windows 11, and the default blank screen that appears when launching an application is causing issues with various programs and emulators. These issues range from a black screen accompanied by background sounds to the inability to run an emulator and revert back to the frontend (this occurs with RetroBat). Generally, these issues are resolved when the application is simply run without blanking flex-launcher. This suggests that the problem may lie with the blanking technique used to conceal the launcher.

I just noticed the same thing on my Windows 10 machine running Steam. I'll investigate a solution.

I just changed the blanking code to something I believe is more correct. It's had to tell for sure because I think this issue may be hardware/driver dependent.
Please give v2.2 a try, and if the issue still persists I can reopen.


reverted changes to adaptedPredicate

Codecov Report

Merging #166 into develop will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             develop     #166   +/-   ##
==========================================
  Coverage      72.44%   72.44%
  Complexity      1155     1155
==========================================
  Files            167      167
  Lines           3419     3419
  Branches         361      361
==========================================
  Hits            2477     2477
  Misses           764      764
  Partials         178      178

Impacted Files
Coverage Δ
Complexity Δ

...k/gov/gchq/koryphe/predicate/AdaptedPredicate.java
90% <ø> (ø)
6 <0> (ø)
:arrow_down:

...java/uk/gov/gchq/koryphe/adapted/InputAdapted.java
80% <0%> (ø)
4% <0%> (ø)
: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 d9617b2...fac11e5. Read the comment docs.


Modal Positioning

Prerequisites

[X] I have not leaked any internal company information.
[X] I have not posted internal links or code snippets.

Suggestion / feature request
It would be nice to have the possibility of positioning the modal by passing in a value into the service.
For example passing in position="top left", which would result in the Modal being placed at the top left of the screen.

Internal ref [IX-890]


Attempt to set credentials from secrets files

Hi, I'm using your code in Rancher, and made the modification in this PR to grab the credentials from Rancher secrets rather than environment variables or directly. I thought you might find it useful to merge, though no offence if you don't want the cruft.
n.b. it looks as though the contrib/k8s* files now in the repo achieve the same goal for k8s for the st0vg container image. It would be better not to have to build my own image as I do now, but I don't think the k8s config works for Rancher.
The secrets files are:

/run/secrets/garmin_username — Garmin Connect username
/run/secrets/garmin_password — Garmin Connect password
/run/secrets/trainerroad_username — TrainerRoad username
/run/secrets/trainerroad_password — TrainerRoad password

Sorry, hadn't got round to reviewing this but looks like you've made the changes and merged now. I love a picky comment and totally agree with the 'log in' verb change so 👍
Thanks for accepting.


v1.7.2 release

Pre-release

[x] Check that there are no release blockers for the targeted release version
[x] Ensure that outstanding backport PRs are merged
[x] Create a new project for the next release version

v1.7.2 project
v1.7.3 project
[ ] Move any unresolved issues/PRs into the newly created release project

[ ] Push a PR including the changes necessary for the new release:

[ ] Update the VERSION file to represent X.Y.Z
[ ] Update helm charts via make -C install/kubernetes
[x] (If applicable) Update the cilium_version and cilium_tag in
examples/getting-started/Vagrantfile
[ ] Update AUTHORS via make update-authors
[ ] Use Cilium release-notes tool to generate CHANGELOG.md
[ ] Point .github/cilium-actions.yml to the newly created project
[ ] Commit all changes with title Prepare for release vX.Y.Z

[ ] Run CI
[ ] Merge PR
[x] Add build targets for the new release on Docker Hub

cilium
operator
docker-plugin

[ ] Create and push both tags to GitHub (vX.Y.Z, X.Y.Z)
[ ] Wait for docker builds to complete

cilium
operator
docker-plugin

[ ] Create helm charts artifacts in Cilium charts repository
[ ] Create a release for the new tag vX.Y.Z, using the release notes
from above
[ ] Announce the release in #general on Slack (only [@]channel for vX.Y.0)

Post-release

[ ] Prepare post-release changes to master branch

[ ] Update Stable releases section of the README
[ ] Update the project pointers in .github/cilium-actions.yml

[ ] Update the stable tags for each Cilium image on Docker Hub (if applicable)
[ ] Update external tools and guides to point to the new Cilium version:

[ ] kops
[ ] kubespray

Waiting on merge / backport of https://github.com/cilium/cilium/pull/10727.


Cargo.toml: upgrade dependencies

In particular, tokio isn't pinned to 1.15 now. Pinning tokio was making it hard for us to use goose in projects which use other dependencies that require a newer version of tokio.

Please see https://github.com/tag1consulting/goose/pull/420 -- there's a known issue preventing this update, as tests fail. The work in  https://github.com/tag1consulting/goose/pull/509 will solve this once it lands.


Bug with property serializers

I was trying to implement enums #1082 , and I discovered a bug with serializers.
Here's a test that demonstrates it:
describe Neo4j::ActiveNode do
  before(:each) do
    # This serializer adds a text when the data is saved on the db,
    # and removes it when deserializing
    class MySerializer
      def initialize(text)
        @text = text
      end

      def converted?(value)
        value.is_a?(db_type)
      end

      def db_type
        String
      end

      def convert_type
        Symbol
      end

      def to_ruby(value)
        value.gsub(@text, '').to_sym if value
      end

      alias_method :call, :to_ruby

      def to_db(value)
        "#{value}#{@text}" if value
      end
    end

    stub_active_node_class('MyData') do
      property :polite_string, serializer: MySerializer.new(', sir.')
      property :happy_string, serializer: MySerializer.new(' :)')
    end
  end

  it 'serializes correctly' do
    data = MyData.new
    data.polite_string = :hello
    data.happy_string = :hello
    data.save!
    expect(MyData.as(:d).pluck('d.polite_string, d.happy_string')).to eq([['hello, sir.', 'hello :)']])
  end
end

Here's the test output:
1) Neo4j::ActiveNod serializes correctly
     Failure/Error: expect(MyData.as(:d).pluck('d.polite_string, d.happy_string')).to eq([['hello, sir.', 'hello :)']])

       expected: [["hello, sir.", "hello :)"]]
            got: [["hello :)", "hello :)"]]

       (compared using ==)
     # ./spec/e2e/enum_spec.rb:50:in `block (2 levels) in <top (required)>'

EDIT:
After exploring the code, I noticed that the convert_type output is used as a key to determine what is the correct TypeConverter for a certain type, and it's used for ALL properties.
https://github.com/neo4jrb/neo4j/blob/77190ab416d219f230dc86eb71e3b7b92df65b0b/lib/neo4j/shared/declared_property.rb#L115
It's a bit strange, since I'm passing the serializer setting only to a specific property, not as a global setting.
My question is: it's really a bug? or a design choice?
I'm a bit confused.

I'm not very familiar with serializers.  @subvertallchris is this an ActiveAttr thing, or something we put in?

It's ours, I will look over this today.
On Friday, February 12, 2016, Brian Underwood<EMAIL_ADDRESS>wrote:

I'm not very familiar with serializers. @subvertallchris
https://github.com/subvertallchris is this an ActiveAttr thing, or
something we put in?
—
Reply to this email directly or view it on GitHub
https://github.com/neo4jrb/neo4j/issues/1128#issuecomment-183281790.

Yesterday was a bit busy so I'm finally taking a look now. I'm pretty sure that the serializer option (originally called type_converter) came from someone who was contributing for a short time. I don't have time right this minute to figure out how it's supposed to work -- it seems a little vague to me and we have other ways of accomplishing this -- but I found another way to get your test passing. It might not be the solution but I think it might point us in the right direction.
Check out #1134. I fixed the serialize class method to get your test passing and allow us to define serializers that do not dominate an entire primitive type. If we want to keep using the serialize property option, we can just have it delegate to serializer so they can share that code and behavior, just as we do for the index option and class methods.

This is pretty old, closing!


Delayed requests (up to 20 seconds)

Since upgrading to the latest build I have been experiencing big delays on particular requests. The request sits in the client for up to 20 seconds before it attempts it. Again, this only happens with particular calls. After using wireshark I have this to show:

After every delay a [SYN, ACK] appears..

I can confirm this only started in the newest release.I just reverted everything back and it's perfect.


Group chat - Cursor appears disabled briefly when opening user profile from group member view

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.3.97-2
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:

Navigate to staging.new.expensify.com
Open a group chat
Click on the group chat header
Click Members
Click on any user

Expected Result:
The cursor will not appear disabled during the transition from group member view to user profile
Actual Result:
The cursor appears disabled briefly when transitioning from group member view to user profile
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/fc0905f3-7f8a-4875-9663-6ea183d5a011
View all open jobs on GitHub

:wave: Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

Identify the pull request that introduced this issue and revert it.
Find someone who can quickly fix the issue.
Fix the issue yourself.

I can reproduce - this seems small though so I wouldn't make this a  deploy blocker

@Li357 I don't see an obvious cause for this when I'm looking through the list here Am I missing an obvious connection here?

We should not revert the change for useSingleExecution it was removed for web because it was causing a lot of bugs due to it's usage of InteractionManager.

Taking a look now!

I agree we shouldn't do a revert here @dukenv0307. Are there other ways to ensure certain actions that have immediate results to not show as disabled?

chill Melvin - we're just back from the weekend

@dukenv0307 I'm not a huge fan of the new prop, does adding !props.isDisabled && styles.cursorPointer cause other regressions?

Ok, let's go with that then. I'll go ahead an assign you!

@Li357 i am interested in reviewing this

I see @thesahindia was assigned as C+ reviewer in PR. I think he can go ahead.

Sorry about the delay! @allroundexperts I've selected @dukenv0307's revised proposal. Let me know if you agree

@Li357 Since @thesahindia reviewed the PR they should be assigned as a C+ here.

@Li357 @dukenv0307's revised proposal looks good to me as well. I can help with the review as well if needed.

Got it, I'll remove you @allroundexperts and assign @thesahindia -- sorry about the confusion.

Payouts due:
Contributor: $500 @dukenv0307 (Upwork)
Contributor+: $500 @thesahindia (NewDot)
@dukenv0307 jusy hired you for the job in Upwork - @thesahindia will you check the checklist to see if there are any next steps here?

@thesahindia bump on the checklist

Also removing Andrew as he's no longer handling issues and re-adding the engineering label

$500 payment approved for @thesahindia based on this comment.


[Bug]: image in css (css-loader) removes from dev-server after update some file

System Info
System:
OS: Linux 6.8 Ubuntu 22.04.5 LTS 22.04.5 LTS (Jammy Jellyfish)
CPU: (16) x64 11th Gen Intel(R) Core(TM) i9-11900K @ 3.50GHz
Memory: 22.65 GB / 31.21 GB
Container: Yes
Shell: 5.8.1 - /usr/bin/zsh
Binaries:
Node: 20.15.0 - ~/.nvm/versions/node/v20.15.0/bin/node
Yarn: 1.22.22 - ~/.nvm/versions/node/v20.15.0/bin/yarn
npm: 10.7.0 - ~/.nvm/versions/node/v20.15.0/bin/npm
bun: 1.1.24 - ~/.bun/bin/bun
Browsers:
Chrome: 128.0.6613.137
npmPackages:
@rspack/cli: ^1.0.0 => 1.0.5
@rspack/core: ^1.0.0 => 1.0.5
Details
In example repo I have import of css file that contains link to local image
After any change in dev mode (for example change "Hello" text to "Hello!") image is removes from dev-server
Image also removes from /webpack-dev-server list
Reproduce link
https://github.com/krutoo/rspack-image-in-css-bug
Reproduce Steps

npm i
npm run dev
see block with image as background in browser
change "Hello, world!" to "Hello, world!123" in ./src/components/app/app.tsx
update browser tab
see that now image is 404

You can try to set output.clean to false to avoid this problem. Rspack will not generate unchanged assets during incremental building

@LingyuCoder is this a bug or expected behavior?

@LingyuCoder is this a bug or expected behavior?

This is a bug caused by the design of rspack's incremental building. We will have a new incremental building scheme in the future, which will solve this problem.

Bump


documentation for 'import-name' needs clarification for more complex names

The import-name rule is awesome and the override configuration is pretty slick.
However, it took me a while to figure out how to use it for request-promise-native which is usually imported as request since it simply wraps the request package.
I think the documentation could be updated with this additional note:
Note that the name of the package is the expected camelCase name of the package. For example, to allow `request-promise-native` to be imported as `request`, add this configuration: `'import-name': [true, { 'requestPromiseNative': 'request'}]`

I forked the project and wanted to create a PR, but I couldn't find any contribute.md file or something similar describing the project's expectations regarding PRs. I figured posting it here might be the fastest way for someone involved with the project to make that change.

Hey @ericsnap it'd be great to have a PR from you! There's no contribute.md or equivalent, yes, but there should be. Filed #589.
In general, if you want to make a change to the rule's .ts file or README.md, please do send those our way in the form of a pull request.

@JoshuaKGoldberg filed PR #590 (I think...)


Domain transfer FAQ

https://developers.cloudflare.com/registrar/faq
I'd appreciate adding the following information to the Registrar FAQ:
Other registrars allows purchasing domain renewals for up to 10 years in advance.

Do you allow the same? Sorry I see this has an answer here
What would happen when transferring a domain that already has 10 years? Will it become 11? (It says "Time purchased is never lost." but also "up to 10 years".)

Another small issue - this page says:

Cloudflare Registrar does not currently support email forwarding

But I saw that Cloudflare now offers email routing.

Hi @aelij. Thanks for your input. This was corrected in PR-3329. We removed the reference to email forwarding as we now have Email Routing. And the FAQ also answers your question regarding the 10 years. Thanks! :)


🚀 Feature: VertexAI Instrumentation

Which component is this feature for?
All Packages
🔖 Feature description
Instrument calls to Google's Vertex AI, including adding attributes for input parameters, model, etc. - similarly to our OpenAI instrumentation. The instrumentation should support all types of calls - streaming, non streaming, async, etc.
Instrumentation should support all models supported in our Python instrumentation including the new Gemini AI model.
This should specifically work with Google's new Gemini model.
🎤 Why is this feature needed ?
Completeness of OpenLLMetry
✌ How do you aim to achieve this?
Similar to other instrumentations we have in this repo.
🔄 Additional Information

Make sure to initialize this in Traceloop SDK.
Add proper tests.
Add a sample in the sample app.
Upload a screenshot from Traceloop with how your instrumentation works.

👀 Have you spent some time to check if this feature request has been raised before?

[X] I checked and didn't find similar issue

Are you willing to submit PR?
None

/bounty $100

/attempt #31
can i get assigned?

/attempt https://github.com/traceloop/openllmetry-js/issues/31


fix: remove redundant assets reference

Description
Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes #47
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] Manual Testing

Checklist:

[x] I have performed a self-review of my code
[x] My changes generate no new warnings

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


Lcqsigi patch 1

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@adbc59c). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #7   +/-   ##
=========================================
  Coverage          ?   94.92%
=========================================
  Files             ?        5
  Lines             ?      315
  Branches          ?        0
=========================================
  Hits              ?      299
  Misses            ?       16
  Partials          ?        0

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 adbc59c...201ddb9. Read the comment docs.


Fix Windows NVTX support.

This PR follows #2423, which is already merged to the master.
In #2423, reference to nvToolsExt.h is alive even when NVTX is not found on a Windows environment and it prevents cupy.cuda module from being built when check_library function is called.
This PR removes the reference to nvToolsExt.h in such a case.

LGTM!


[Feature request]: Respect dangerouslyIgnoreUnhandledErrors

Is your feature request related to a problem? Please describe.
I have a test that simulates a 500 error from the server, and shows that we handle it with an error boundary in our app.  The story fails in the interaction test, however, so I added the suggested test.dangerouslyIgnoreUnhandledErrors parameter, which makes it green in the browser, but the test still fails in CI due to the test-runner seemingly not respecting it.
Describe the solution you'd like
Tests should not fail due to unhandled errors if dangerouslyIgnoreUnhandledErrors is set.
Describe alternatives you've considered
I can also disable the test and use a chromatic snapshot to validate that the correct screen is shown, which is what I'll do as a workaround for now.
Are you able to assist to bring the feature to reality?
yes, I can
Additional context
I marked yes i can above, but it's more of a "maybe".  :-D

Hey @IanVS as we spoke before, I was not able to reproduce this issue. The test-runner is not aware of that option because it doesn't have to, as it just listens to events from Storybook. So if your option is set, then Storybook should not emit the event to the test-runner

Thanks for the reminder, I'll try to figure out what was happening.

Sure enough, I can no longer reproduce the issue I was seeing before.  I have a test that fails without dangerouslyIgnoreUnhandledErrors, both in test-runner and the UI, and it passes in both spots when I enable the flag.  Something else must have been erroring before.  Sorry for the false alarm!


Crossgen

More preparation for cross platform build.

Remove Proto Projects.
Build Proto from Product projects - targeting coreclr
Remove unused PlatformTargets / some Silverlight stuff from targets file
Publish proto and lkg using dotnet publish
Crossgen the proto compiler

Could you adjust DEVGUIDE.md to describe how the build works?  Thanks
There are various bits and pieces I don't understand here.  I'll take another look when the lights are green.

@dsyme ...
I will add a switch too build proto for windows, we still don't need the old project files for that.  However, the coreclr compiler does need to be every bit as functional and fast as the desktop compiler.  So we shouldn't really consider this as cutting us off from the "Good Windows Desktop developer world".  The desktop clr build just makes debugging and testing a bit more convenient right now.
We do need the proto to build on coreclr to ensure that:

We can use the coreclr build of FSC to run a large application
In order to build on OSX and Linux

Kevin

@KevinRansom super


(AI85/AI87) Support MXC_LP_EnterSleepMode on RISC-V

All this really does is __WFI() since there is more non-trivial work needed to synchronize the RISC-V core and M4 core sleep mode entry - the details of which are beyond the scope of a PR comment.  The SEMA peripheral needs additional work to expose the required functions to the LP peripheral, and a mailbox signaling protocol needs to be designed to indicate which sleep mode the M4 core should initiate entry into.
This at least gets the latest izer output to build for the RISC-V projects as of https://github.com/MaximIntegratedAI/ai8x-synthesis/pull/273

Let's just get this merged in so the ai8x-synthesis builds at least work for the RISC-V.  A better implementation is on the backlog


✨ Support for legacy Camera1 devices

Type

[ ] I'm cannot build my project with VisionCamera
[ ] I'm experiencing a full app crash
[x] A feature is not working correctly
[ ] Other: __________________

What
Hi Team,
We are using you library to capture images. When using getAvailableCameraDevices() function from Camera, it returns the length 0 or if we use the 'useCameraDevices' hook, the value returned in undefined, Referring the same code as mentioned from the Sample in the API docs.

Platform(s):

[ ] iOS
[x] Android

react-native version: 0.64
react-native-vision-camera version: latest
react-native-reanimated version: 2.0.1

Why did you not fill out the template? Share your versions. Which Xiaomi Mi is it? There are multiple versions afaik.
I believe that device does not return any Camera2 compatible devices, it's legacy

Updated the issue with template. Xiomi MI Note 6 Pro is where this issue is occuring and use legacy Camera1 API. What should we do for this?

VisionCamera requires Camera2 compatible devices, because a lot of features we have in this library are not compatible with Camera1.
To also add support for Camera1 devices I would have to implement https://github.com/cuvent/react-native-vision-camera/issues/78 first, since Camera1 devices will not support Preview + Photo Capture + Video Capture + Frame Processing. I understand that there are still many phones out there using Camera1, but after all it is a deprecated API and I have a few features that have higher priority than supporting legacy devices (such as the Frame Processors PR).
On second thought, the Xiaomi MI Note 6 Pro was released 2018, that should be using Camera2 by now, no?
Try opening your project in Android Studio, then hit Command + Shift + O (two times) to open the CameraViewModule.kt file. Put a breakpoint in that line:
https://github.com/cuvent/react-native-vision-camera/blob/5e2e9b6912e820708f3888c32d6375e3dcc91273/android/src/main/java/com/mrousavy/camera/CameraViewModule.kt#L127
and try stepping through the code to find out what devices are actually available, and why they don't get returned in that function.

Cannot find the file CameraViewModule.kt

The cameraId returned in 0

is there only a single camera ID? what if you press "continue", does it not hit the breakpoint again with the next camera?

which is legacy

how did you determine that?

Does this get printed in your Logcat console (in Android Studio, hit command + 6):
https://github.com/cuvent/react-native-vision-camera/blob/5e2e9b6912e820708f3888c32d6375e3dcc91273/android/src/main/java/com/mrousavy/camera/CameraViewModule.kt#L136-L140

Yes this gets printed and the debugger gets a second hit with value 1. However, the above statements is executed and printed.

So for both camera devices (0 and 1) the above line ("Skipping Camera #(id) because ....") will be printed? Could you put a breakpoint here:
https://github.com/cuvent/react-native-vision-camera/blob/5e2e9b6912e820708f3888c32d6375e3dcc91273/android/src/main/java/com/mrousavy/camera/CameraViewModule.kt#L135
and hover over the hardwareLevel variable - tell me what value it has (do this for both cameras).
Then put a breakpoint here: https://github.com/cuvent/react-native-vision-camera/blob/5e2e9b6912e820708f3888c32d6375e3dcc91273/android/src/main/java/com/mrousavy/camera/CameraViewModule.kt#L144
and tell me if that breakpoint is getting hit at all.

Hi,
Sorry for the delay in reply. I checked with what you mentioned to check.
Yes, for both the cameras for my phone - the hardware level value is got as 2. -
First snapshot for first breakpoint -

Second snapshot for second breakpoint  -

The line of log gets executed and printed. Not getting any clue how to resolve this.

The issue to get the camera working itselfs stops us at the code point where we call the getAvailableCameraDevices method. Here both the cameras are returning value 0 right? How does the camera view work even without them?

Sorry I don't understand the question, does it still return 0 devices even with my patch/PR?

Tried with the steps mentioned and it dont work. Tried building the app and now shows only white screen. Nothing happens.

A white screen? Are there any errors shown? Are there any logs in the metro bundler? Are there any logs in Android Studio Logcat? Did the breakpoint get hit?

I thing you can merge.

What does that mean? Did you test it or not?

Does anyone know how many Android devices are still on LEGACY level?

I was also interested in this, so I did a bit of research. According to data from http://camera2probe.com (raw) for 3630 unique devices starting at API 23 the split between supported hardware levels (for select minimum API versions) looks like this:
Devices API 23 or newer
All versions with reliable data. 84.90% market share according to Android Studio.

Support

LEVEL_3
22.59%

FULL
19.15%

LIMITED
17.36%

LEGACY
40.91%

Devices API 25 or newer
66.20% market share.

Support

LEVEL_3
29.57%

FULL
22.44%

LIMITED
19.66%

LEGACY
28.33%

Devices API 27 or newer
Officially supported Android versions according to Wikipedia. 53.5% market share.

Support

LEVEL_3
35.05%

FULL
23.96%

LIMITED
20.68%

LEGACY
20.31%

Devices API 29 or newer
"New" Android versions. 8.20% market share.

Support

LEVEL_3
47.20%

FULL
26.24%

LIMITED
20.75%

LEGACY
5.81%

Since React Native and this library currently support Android back to API 21, where almost half the devices have hardware level LEGACY, a feature like described in #78 would definitely be nice to have in the future.

Those numbers are way higher than I expected. Thanks for the insight @yfunk.
It definitely makes sense to support LEGACY devices, whichever solution it is going to be. I want to try to not change a thing for the library/API to support LEGACY devices, since LEGACY devices do support 3 use-cases, even if video recording will be in PREVIEW sized frames:

(at least that's how I interpreted this table)

Also, Snapchat works on LEGACY devices right? Snapchat also has three use-cases; PREVIEW, photo-capture and video-capture. They even have a fourth use-case, in-app-processing for those dog-mask filters, but I think that can be chained to the PREVIEW use-case.

Also, are those market shares realistic values? How many of those phones actually do have e.g. snapchat or other apps installed? What if they're all just drug dealer or old grandma phones? @yfunk

I investigated a bit, taking a look as to how it would be possible with Camera2. We have two approaches:
Prioritize photo-capture

Use normal PREVIEW buffer for the preview use-case
Use PREVIEW sized buffer/frames for video-capture, so video recordings are in poor quality (PREVIEW size is very small on those LEGACY phones)
Use normal MAXIMUM buffers for photo-capture

Prioritize video-capture

Use normal PREVIEW buffer for the preview use-case
Use MAXIMUM or RECORD buffer/frames for the video-capture to achieve good quality video recordings
Use PREVIEW buffers for photo-capture by simply screenshotting the PreviewView (same as takeSnapshot currently) - this does not support flash and results in poor quality still-images.

I have created a ticket at the google issue tracker asking for advice on this, but I think this is going to be a bad situation either way. Again, LEGACY devices aren't going to be around for long, new devices are being built and the percentages go down. Also, not sure how many people with LEGACY devices download modern apps (since VisionCamera is built for the Cuvent mobile app).
#78 would probably be the best solution to this, I'll try to find a clean API for that.

Also, are those market shares realistic values? How many of those phones actually do have e.g. snapchat or other apps installed? What if they're all just drug dealer phones, airport tablets, old grandma phones, etc?

The data I used for this is from the Android Developer Distribution dashboard, which represents all active Android devices during a 7-day period ending on January 8, 2021. This is what Google provides as a guideline for choosing the minSdkVersion, but I agree that this doesn't necessarily reflect actual users who would download modern apps.
I found data from AppBrain SDK (app monetization), which may be better suited for reflecting potential app users and suggests a significantly higher market share of newer devices. I added it in the comment above.

I've implemented this in #168. Try upgrading to 2.2.0 and make sure to check out the docs for the supportsPhotoAndVideoCapture prop - let me know if it works for you!

I just tested it - it looks like this issue isn't solved completely.
react-native-camera for example falls back to Camera1 - which works - Camera2 ist just producing a black image. I even noticed the usage of these "crazy" hardware in newer devices.
Is there any easy method to solve this? (Maybe read the images from Camera1 if necessary)


Please update Wiki

I know, documentation is always a pain. :-)  However, can the wiki be updated with the newest parameters and explaining examples, please?!
Command-Line-Arguments and How-to-Run Examples
Especially the usage of the different e·mail addresses, san and multi manualhosts are very confusing to me.

Good idea, will update when I feel 1.9.4 is stable enough to release. Meanwhile #493 might help.

Thanks, that would be great.

First mayor update is done:
https://github.com/Lone-Coder/letsencrypt-win-simple/wiki/Command-Line-Arguments

Very good, thanks a lot!
I also saw the switch --signeremail somewhere. Does it exist as well, or was it just a suggestion somewhere in the discussions that I took for real?
I stress to enhance the --plugin documentation, maybe as a separate wiki entry. There is a wiki for "Server Plugins", but the whole section is very confusing to me and seems to be more for programmers. So, for most users it would be very helpful to determine which plugin is to be used when, best with examples.

This page has also been updated now:
https://github.com/Lone-Coder/letsencrypt-win-simple/wiki/Application-Settings
--signeremail was in the beta for a while but has been removed because as I was documenting the command line switches I found out there was another one with the same stated function (--emailaddress).
--plugin is a bit of an awkward mechanism for me too, but actually the whole plugin system is. See #507 and #398 among others. IMHO a program called letsencrypt-win-simple should not have a publically exposed plugin architecture. Might be a v2.0 thing though to fix that.

Ok, thanks for clarification. So I can remove --signeremail from my command line.  :-)


help

During testing, my LQ data was 8X3X256X256, and the code could run. However, why is the dimension of the output data 1x3x256x256. Is there any way to make it output 8x3x256x256

Hi! Which model/task are you running? And in testing, we only support batch size to be "1" instead of "8".

If you really want to output the data more than one batch size, you can modify the get_current_visuals function:
change
out_dict["Output"] = self.output.detach()[0].float().cpu()
to
out_dict["Output"] = self.output.detach().float().cpu()


Update network-watcher-analyze-nsg-flow-logs-graylog.md

@mattreatMSFT : Thanks for your contribution to the Azure documentation! The author, @mareat, has been notified to review your proposed change.

#sign-off

@mattreatMSFT Please resubmit via the private repo.


Possible Memory leak on Replication

From @shoaibmerchant on July 17, 2015 11:21
Hi, we have been trying to resolve this issue since quite some time now. I am running an express-pouchdb server and replicating databases from a couchdb server on it. Please note the replication is being triggered from couchdb not express-pouch. The replication gets completed successfully but the express app memory usage shoots up by more than the database size and it doesnt get cleared till I restart the app. Once I restart things are again back to normal.
On the express pouchdb server I am also listening to requests on bulk docs for some custom business logic but I do make sure that 'next()' is triggered.
Let me know if you need any more details. I tried to trace things out, express pouch source seems pretty straightforward, it seems like an issue with pouchdb.
Copied from original issue: pouchdb/express-pouchdb#221

Which version of PouchDB are you using? And yes, it would be very helpful if you could profile it and maybe track down the source of the memory leak. (Hint: this is an open-source project with no commercial backing, so we need all the help we can get. :wink:)

100 mb spike? I have no idea about that; it's news to me. You mean a spike in memory, right?

From @shoaibmerchant on July 18, 2015 23:17
Hi the version was 3.3.1, I upgraded to 3.6.0 ran my tests again saw the initial 100mb spike on replication thought it wasn't resolved and started profiling. Finally after a couple of consecutive tests I realized that the initial 100 mb spike was only the first time and it didnt happen on subsequent replications (which it used to before the update).
So yes the update did resolve it, sometimes you end up thinking too much and forget the basic stuff. Sorry for the false alarm. Just curious, why the 100 mb spike on first replication and it sticks around even if the replication is over but remains constant on further replications. Note: the database I kept replicating to a new db in pouchdb server was also 100 mb
Great work with Pouch by the way :) much appreciated all the hard work.

From @shoaibmerchant on July 19, 2015 4:40
Yes spike in memory and it stays at that. It could also be equal to the database size I replicated which was also 100mb. Let me investigate further and get back to you.

This ought to be fixed by https://github.com/pouchdb/express-pouchdb/pull/426


uv pip install -e and its PEP-660-style editable installs break vscode import resolution (and probably static type checkers)

My context is that I have a main package and some related packages. Everything is installed in editable mode for development.
When using standard pip with setuptools installed, this creates an egg-link file inside site-packages which is looked up just fine by type checkers including Pyright (which powers the vscode Python/Pylance extension).
However, when using uv pip install -e, the package is installed in PEP-660 mode with a __editable__.<pkgname+version>.pth and __editable___<pkgname+version>_finder.py, ie using a dynamic import hook.
Of course static analyzers generally do not understand those, and don't even try to extract the information from the "dynamic" code even though it would be trivial to do (by simply parsing the MAPPING dict from the ..._finder.py).
While this is not directly uv's fault, and I generally agree with not outputting legacy stuff, this is causing a problem when IDEs can no longer properly resolve imports. And at least the pyright/pylance developers don't seem to be willing to add any workarounds on their side, so they'd rather wait for the Python ecosystem to agree on something that does not require dynamic import lookups. But that probably needs someone to be willing to write a PEP and get it accepted which all takes some time.
Some related issues/comments:

https://github.com/microsoft/pylance-release/issues/3473#issuecomment-2133566168
https://github.com/microsoft/pyright/issues/3880#issuecomment-2134083781
https://github.com/microsoft/pylance-release/issues/5894#issuecomment-2133544837

Is there any chance uv can do something about this, such as providing an option to generate an egg-link instead of a PEP660-style __editable__*.pth, even though it's slightly more legacy?

To be honest I am bit confused. Pip passess the implementation responsability of editable installs to the backend:
https://pip.pypa.io/en/stable/topics/local-project-installs/#editable-installs
Doesn't uv does the same?
For packages built with setuptools there are a coupe of configuration options  used at installation time. That said,  I am not sure if the latest version of setuptools works the way that OP proposes here anymore.
For reference, when building with hatch works with the default that allows static analysis tools to work by default:
https://github.com/pypa/hatch/issues/1629#issuecomment-2237849607
I am not sure what uv pip install -e would do if the build backend was hatchling.
Any chance a mantainer could chime in, clarify the state of affairs and say whether this is:

Important but not resources to addres it at the moment.
Not important, unlikely to be addressed.

I agree this issue is not clear. I'm not the expert on this area, but a hatch build backend doesn't use a dynamic .pth
❯ uv venv
Using Python 3.12.3 interpreter at<EMAIL_ADDRESS>Creating virtualenv at: .venv
Activate with: source .venv/bin/activate
❯ grep "build-system" -A 2 ../packse/pyproject.toml
[build-system]
requires = ["hatchling"]
build-backend = "hatchling.build"
❯ uv pip install -e ../packse -q
❯ cat .venv/lib/python3.12/site-packages/_packse.pth
/Users/zb/workspace/packse/src%

This seems like a problem with setuptools? In their documentation they note:

Setuptools offers no guarantee of which technique will be used to perform an editable installation. This will vary from project to project and may change depending on the specific version of setuptools being used.

It seems possibvle that you're getting different versions of setuptools depending on if you're using uv or pip? Having you tried using --config-settings to configure this?

It's unfortunately not something we can do anything about

Why not offer a way to do an editable install using the classic static resolution (egg-link) instead of the dynamic one?
I never really looked into alternative build backends, but I assume this also means changing all the related configs (setup.cfg etc.) in the project, which is a mess if you have many projects and you either end up with one using something different than all the others, or having to update all of them for consistency...

The old egg mechanism was never standardized and is basically pip-setuptools special casing; in uv, we support PEP 660, the standard editable installs that work across build backends. Pip has also deprecated its current behavior and will remove it in the 25.0 release (https://github.com/pypa/pip/issues/11457).

For poeple stumbling on this thread, adding this to pyproject.toml makes pylance happy. https://github.com/pypa/setuptools/issues/3518 suggests the removal of 'compat' has been pushed back, so this will work for now...
[tool.uv]
    config-settings = { editable_mode = "compat" }

Dependencies defined like this:
[tool.uv.sources.activemodel]
path = "pypi/activemodel"
editable = true

Were not recognized by VS Code. This config did fix the issue (underscore, not dash):
[tool.uv]
config_settings = { editable_mode = "compat" }

I'm trying to make UV Workspaces work. I'm using VS Code, and I'm trying to import from one workspace package in another one. Pylance (Pyright) does not recognize the import.
I tried adding
[tool.uv]
config_settings = { editable_mode = "compat" }

to pyproject.toml. This errored out for the root pyproject.toml, and had no effect after adding it in the child configs.
@konstin is this supposed to be broken?


Don't write json in the middle of responses

This will write json directly to the response, which already holds data, making the resulting json invalid:
https://github.com/cloudamqp/avalanchemq/blob/183a65cf7ed6c32094bc54487f551266759a3b47/src/avalanchemq/http/handler/error_handler.cr#L17-L19

I've seen this before, I think we should rewind the response IO on any error and then write the error. Not sure if we could make a general error handler or just do it in all rescue blocks

I don't think you can rewind context.response, it's a socket afaik. I truncate the result set (and log warn) instead in #343


[Bug]: Don't show syntax highlighting when not in double-braces

Is there an existing issue for this?

[X] I have searched the existing issues

Description
We're showing syntax highlighting for text that's not inside double-braces. But only content inside double-braces is actually treated as Javascript. Rest is plain text. So having syntax highlighting there is misleading and confusing.
Steps To Reproduce

Public Sample App
No response
Environment
Production
Severity
Low (Inconsistent UI/UX)
Issue video log
No response
Version
Cloud & Self-Hosted

Trying to reproduce the issue.

Hey @sharat87 ,I wanna work on this issue, can you help in how to replicate this issue?

@rohan-arthur this doesn't seem like an easy to contribute issue to me. Can we remove the inviting contributions label for this issue?


Add reference cards for artifact expansion

This work is blocked by #339.

We aren't 100% if/how we want to do this, so it's no longer release-blocking.


Disabling framework endpoints for certain methods

After configuring
  public void configure(AuthorizationServerEndpointsConfigurer endpoints) {}
with mappings for various apis, I see that by default every http method is supported.
I would expect some way to disable check_token on for a subset of http methods (like GET) so that when access logging is on, access tokens do not appear in logs.

My current workaround is to not define check token mappings via AuthorizationServerEndpointsConfigurer and instead create my own rest controller that extends CheckTokenEndpoint that supports specifically POST and just calls super


MAC version crashed on high resolution screen

Also, TouchBar appeared multiple times in the crash reports.
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libobjc.A.dylib               	0x00007fff6937604c class_conformsToProtocol + 235
1   libobjc.A.dylib               	0x00007fff69375f46 -[NSObject conformsToProtocol:] + 46
2   com.apple.AppKit              	0x00007fff3c8f26b9 -[NSApplication(NSTouchBarFinder) NS_touchBarProviders] + 403
3   com.apple.AppKit              	0x00007fff3c8f37ad _NSTouchBarFinderGatherProvidersForContainer + 64
4   com.apple.AppKit              	0x00007fff3c8f2dd2 ___NSTouchBarFinderSetNeedsUpdateOnMain_block_invoke + 279
5   com.apple.CoreFoundation      	0x00007fff3ec53f28 CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION + 23
6   com.apple.CoreFoundation      	0x00007fff3ec53e5d __CFRunLoopDoObservers + 451
7   com.apple.CoreFoundation      	0x00007fff3ebf5ef9 CFRunLoopRunSpecific + 514
8   com.apple.HIToolbox           	0x00007fff3de551ab RunCurrentEventLoopInMode + 292
9   com.apple.HIToolbox           	0x00007fff3de54ded ReceiveNextEventCommon + 355
10  com.apple.HIToolbox           	0x00007fff3de54c76 _BlockUntilNextEventMatchingListInModeWithFilter + 64
11  com.apple.AppKit              	0x00007fff3c1ed79d _DPSNextEvent + 1135
12  com.apple.AppKit              	0x00007fff3c1ec48b -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1361
13  com.ABC.XYZ        	0x00000001012eb96c main + 5420
14  libdyld.dylib                 	0x00007fff6ab4c3d5 start + 1

I had the same problem in my project an fixed it by using NSResponder as the parent for the app delegate and also add the NSTouchBarProvider protocol to it.
I believe replacing this line: https://github.com/zserge/webview/blob/9c1b0a888aa40039d501c1ea9f60b22a076a25ea/webview.h#L1920
with this:
  Class __NSWindowDelegate = objc_allocateClassPair(objc_getClass("NSResponder"),
                                                    "__NSWindowDelegate", 0);
  class_addProtocol(__NSWindowDelegate, objc_getProtocol("NSTouchBarProvider"));

should fix it.

Hm... I tried what @JBildstein suggested, but so far the crash is still there, even though I use NSResponder as the parent class to my delegate. And he's right, the crash happens only on the devices with the touchbar. I wish I knew macos internals better to debug this.

did you add the NSTouchBarProvider protocol as well (and made sure objc_getProtocol actually returns a valid pointer)?
to debug this I found the XCode touchbar emulator very helpful: open XCode and in the menu select "Window->Show Touch Bar" in XCode 10 or "Window->Touch Bar->Show Touch Bar" in XCode 11.

Unfortunately, still no luck. I only did the following modification:
diff --git a/webview.h b/webview.h
index 19e69b6..821b435 100644
--- a/webview.h
+++ b/webview.h
@@ -585,7 +585,9 @@ public:
                  NSApplicationActivationPolicyRegular);

     // Delegate
-    auto cls = objc_allocateClassPair((Class) "NSObject"_cls, "AppDelegate", 0);
+    auto cls = objc_allocateClassPair((Class) "NSResponder"_cls, "AppDelegate", 0);
+    printf("%p\n", objc_getProtocol("NSTouchBarProvider"));
+    class_addProtocol(cls, objc_getProtocol("NSTouchBarProvider"));
     class_addProtocol(cls, objc_getProtocol("NSApplicationDelegate"));
     class_addProtocol(cls, objc_getProtocol("WKScriptMessageHandler"));
     class_addMethod(cls, "applicationShouldTerminateAfterLastWindowClosed:"_sel,

And I get a crash, although the protocol for NSTouchBarProvider is non-zero.

ok I figured it out. I forgot about one small detail (and actually thought it would behave differently with c/c++):
both NSApplicationDelegate and WKScriptMessageHandler return null in objc_getProtocol and adding null with class_addProtocol causes weird problems with the internal conforms_to_protocol check that's causing the exception.
So the solution is to remove the class_addProtocol calls with NSApplicationDelegate and WKScriptMessageHandler
I had the same issue in C# but I figured those protocols simply aren't available at runtime but they would be at compile time. seems I was wrong.

@JBildstein Sir, you are a genius! Thanks a lot :tada:


v0.3.7

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

update 0.3.7

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender


Add Share App scenes (optional) to ineligible and eligible signup workflows

This PR accomplishes the following:

Connects the APCShareViewController to the APCInEligible signup scene, along with a short label and a button.
Hides the back button from the InEligible scene, to discourage the user from simply tapping back and changing their selection criteria.
Connects the APCShareViewController in the eligible workflow as an option while waiting to verify email in the APCEmailVerify controller along with a short label and button. This will not be shown on old (3.5") phones due to space issues.

These new buttons/labels to get to the share scene are optional and off by default. Any app can show them by toggling showShareAppInOnboarding to true. The removal of the back option from the APCInEligibleViewController is universal.

share setting moved out of AppDelegate and into APCOnboardingManager per @p2 's suggestion.


Allow modifying and deleting rules

I should be able to edit a rule as well as delete it.

Deletion is a thing, just need to edit rules/filters now.


chore: clean up dead terraform code from testinfra

Removes old terraform e2e provisioning code that has been replaced by the refactored new
terraform code in infra/*

/gcbrun

/gcbrun


Stacked bar charts force 'beginAtZero' behavior

Expected vs Current Behavior
When using stacked bars, the graphs always begin at zero despite setting beginAtZero to be false manually. See https://jsfiddle.net/2wsxLrej/1/ for an example of expected behavior when not stacked, and uncomment the stacked options to see erroneous behavior.
Environment

Chart.js version: v2.6, v2.4
Browser name and version: Chrome
Link to your project: https://jsfiddle.net/2wsxLrej/1/

Resolved: removing "stacked: true" on Y Axis resolved this issue


eisvogel 2.0.0 lang error (fr : French)

When I set langage to French lang : fr  or lang : fr-FR I get the folowing error
updating tlmgr
updating existing packages
compilation failed- error
Argument of \str_uppercase:n has an extra }.

\par
l.270   \setmainlanguage[]{}
How to fix that.
Sorry I'm new to latex.

duplicate of #278


Problem installing gnina with make command - Building CUDA object

Issue summary
I cannot succeed in installing gnina. I get the following error:
[ 14%] Building CUDA object src/CMakeFiles/libmolgrid_shared.dir/grid_maker.cu.o
/usr/include/c++/11/bits/std_function.h:435:145: error: parameter packs not expanded with ‘...’:
  435 |         function(_Functor&& __f)
      |                                                                                ^
/usr/include/c++/11/bits/std_function.h:435:145: note:         ‘_ArgTypes’
/usr/include/c++/11/bits/std_function.h:530:146: error: parameter packs not expanded with ‘...’:
  530 |         operator=(_Functor&& __f)
      |                                                                                ^
/usr/include/c++/11/bits/std_function.h:530:146: note:         ‘_ArgTypes’
make[5]: *** [src/CMakeFiles/libmolgrid_shared.dir/build.make:188 : src/CMakeFiles/libmolgrid_shared.dir/grid_maker.cu.o] Erreur 1
make[4]: *** [CMakeFiles/Makefile2:930 : src/CMakeFiles/libmolgrid_shared.dir/all] Erreur 2
make[3]: *** [Makefile:146 : all] Erreur 2
make[2]: *** [CMakeFiles/libmolgrid.dir/build.make:86 : libmolgrid-prefix/src/libmolgrid-stamp/libmolgrid-build] Erreur 2
make[1]: *** [CMakeFiles/Makefile2:413 : CMakeFiles/libmolgrid.dir/all] Erreur 2
make: *** [Makefile:146 : all] Erreur 2

I succeeded in installing openbabel with the command listed in gnina repo but with adding a sudo to the make install command. Otherwise I had a permission error. But when doing the gnina install, it seems it doesn't find the openbabel module.
-- Dependencies:
--   BLAS              :   Yes (Atlas)
--   Boost             :   Yes (ver. 1.74)
--   glog              :   Yes
--   gflags            :   Yes
--   OpenBabel         :   No
--   protobuf          :   Yes (ver. ..)
--   CUDA              :   Yes (ver. 11.5)

But is I type the obabel command, it perfectly work:
No input file or format spec or possibly a misplaced option.
Most options must come after the input files. (-i -o -O -m can be anywhwere.)

Open Babel 3.1.0 -- Jun  1 2023 -- 15:03:02
Usage:
obabel [-i<input-type>] <infilename> [-o<output-type>] -O<outfilename> [Options]
Try  -H option for more information.

And I'm not sure it is somehow related to the error I get here as it seems to be related to CUDA. Any idea?
By the way, I checked the other Issues where it was mentioned a similar error but couldn't find the solution yet :-(
Your system configuration
Operating system: Ubuntu 22.04
Compiler:
CUDA version (if applicable):
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 525.105.17   Driver Version: 525.105.17   CUDA Version: 12.0     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  NVIDIA RTX A300...  Off  | 00000000:01:00.0 Off |                  Off |
| N/A   32C    P3    N/A /  55W |      6MiB / 12288MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|    0   N/A  N/A      2537      G   /usr/lib/xorg/Xorg                  4MiB |
+-----------------------------------------------------------------------------+

And
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2021 NVIDIA Corporation
Built on Thu_Nov_18_09:45:30_PST_2021
Cuda compilation tools, release 11.5, V11.5.119
Build cuda_11.5.r11.5/compiler.30672275_0

CUDNN version (if applicable):
Python version:
Python 3.10.6 (main, Mar 10 2023, 10:55:28) [GCC 11.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>

This looks like a problem with the gcc compiler.  The version I would expect on Ubuntu 22.04 is 11.3.  Is that the version you are using?

Sorry for my late reply, I left the computer at the office.
True, I'm using the 11.3.0 version of gcc.
gcc (Ubuntu 11.3.0-1ubuntu1~22.04.1) 11.3.0
Copyright (C) 2021 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Shall I downgrade to a specific version? I didn't find any upgrade for it.

Hmm ok, too bad... I'll have a look when I have some time :-)

Closing due to lack of activity - please close issues when they are resolved.


missing dependencies:  blots/block/embed

Hi,
There seem to be some dependencies missing. Or am I missing something?
`ERROR in The target entry-point "ngx-quill-upload" has missing dependencies:

blots/block/embed`

 "dependencies": {     "@angular/animations": "~10.0.5",     "@angular/common": "~10.0.5",     "@angular/compiler": "~10.0.5",     "@angular/core": "~10.0.5",     "@angular/forms": "~10.0.5",     "@angular/platform-browser": "~10.0.5",     "@angular/platform-browser-dynamic": "~10.0.5",     "@angular/router": "~10.0.5",     "ngx-quill": "^12.0.1",     "ngx-quill-upload": "^1.0.3",     "quill": "^1.3.7",     "quill-image-resize": "^3.0.9",     "quill-image-resize-module": "^3.0.0",     "rxjs": "~6.5.5",     "tslib": "^2.0.0",     "zone.js": "~0.10.3"   },

Hi @zwaldeck 'blots/block/embed' is supposed to be imported from the Quill itself. Apparently this was a false warning and has been fixed now

@ayush013 Thanks for the quick response & update.
It works now!


Docs page: Example code wrong?

The example in the JSHint.com docs for relaxing and enforcing rules proposes:

Take the following code as an example:

function main(a, b) {
   return a == null;
 }

This code will produce the following warning when run with default JSHint options:

line 2, col 14, Use '===' to compare with 'null'.

Let's say that you know what you're doing and want to disable the produced warning but, in the same time, you're curious whether you have any variables that were defined but never used. What you need to do, in this case, is to enable two options: one relaxing that will suppress the === null warning and one enforcing that will enable checks for unused variables. In your case these options are unused and eqnull.

/*jshint unused:true, eqnull:true */ // <-- Don't you mean "eqnull:FALSE"?
 function main(a, b) {
   return a == null;
 }

After that, JSHint will produce the following warning while linting this example code:

demo.js: line 2, col 14, 'main' is defined but never used.
demo.js: line 2, col 19, 'b' is defined but never used.

at XPath "/html/body/div/div/div[1]/pre[12]/code" (I wish I could insert a simple link; the doc could use some IDs; at least for every heading)
If it is about enabling unused and DISABLING eqnull, shouldn't it be
/*jshint unused:true, eqnull:false */
instead of
/*jshint unused:true, eqnull:true */
?

Thanks for the report! That example is incorrect in more ways than one. As of gh-3109, JSHint no longer reports the referenced warning, ever. To resolve this, we'll need to demonstrate "relaxing" options with a different example.
Want to try fixing this, @svArtist?
Note that the documentation in question currently resides in the project website repository.

Want to try fixing this, @svArtist?

I'm having a hard time understanding what exactly happened with eqeqeq vs eqnull, so I steered clear of that and replaced the example entirely, while trying to highlight how the two different options work in conjunction with current default settings
https://github.com/jshint/jshint.github.io/pull/58
Is that okay?

...but as a side note: I think I my original issue is invalid, because I found eqnull under the relaxing options.
I may have misunderstood that before; now I've had a closer look


Add basic angular test bed configuration

The basic setup code to configure the angular test bed was missing.

:shipit: