ACU entries for D(a)*v5 VMs are missing

The ACU page does not include entries for any of the new D(a)*v5 VMs which are now GA.
The doc pages for the D(a)*v5 VMs are missing ACU values as well, for which I've submitted separate issues.
The Dv5 VM doc pages say:
"Next steps
Learn more about how Azure compute units (ACU) can help you compare compute performance across Azure SKUs." and link to the main ACU page here. Neither
These ACU data points are important to customers looking to compare them to prior generations and other instance families.

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

ID: 568a0854-5b9e-0d79-642f-2775271d0521
Version Independent ID: 876df17a-3a80-8e2d-bb70-c6810df7fd18
Content: Overview of the Azure Compute Unit - Azure Virtual Machines
Content Source: articles/virtual-machines/acu.md
Service: virtual-machines
Sub-service: sizes
GitHub Login: @mimckitt
Microsoft Alias: mimckitt

We are aware we do not have the ACU numbers. We do not currently have them available. When we do, we will update the pages.
#assign: @mimckitt


Modify package generation actions

Description

Issues Resolved

Check List

[ ] All tests pass

[ ] yarn test:jest
[ ] yarn test:jest_integration

[ ] New functionality includes testing.
[ ] New functionality has been documented.
[ ] Update CHANGELOG.md
[ ] Commits are signed per the DCO using --signoff

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 55.16%. Comparing base (f066302) to head (215186a).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##            4.9.0     #157       +/-   ##
===========================================
- Coverage   66.96%   55.16%   -11.81%
===========================================
  Files        3300     1188     -2112
  Lines       63585    23871    -39714
  Branches    10141     3975     -6166
===========================================
- Hits        42582    13169    -29413
+ Misses      18538    10079     -8459
+ Partials     2465      623     -1842

Flag
Coverage Δ

Linux_1
?

Linux_2
55.16% <ø> (ø)

Linux_3
?

Windows_1
?

Windows_2
?

Windows_3
?

Windows_4
?

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


How to use GT 2D pose training.

How to use GT 2D pose training.Can you help me?

I also have the same problem.
Does anyone know the answer?

Setup Alphapose first, the results will be output in a json which is what you feed into this model to get 3D

How to use GT 2D pose training.Can you help me?

@AliasChenYi @OliverSTH Hello， Have you solved this problem and can you share it?

Setup Alphapose first, the results will be output in a json which is what you feed into this model to get 3D

Exactly.
For anyone that wants to train the model for action recognition, you need to extract the 2d poses first using alphapose. These 2d poses will be formatted as json files. Then, write a script that transform jsons into the desired format. You need to read the code from the Dataloader in order to understand how to format your data.


Various fixes

Checklist

[x] I read and understood the contributing guide as well as the code of conduct
[x] My changes generate no new warnings
[x] My code builds and runs on my machine
[x] I documented my code
[x] Review requested

Might want to put tryFocusWindow as a static function in appdelegate so that there aren’t four different instances of the same function. The function doesn’t seem to interact with any class instances so its fine if its static.

@KaiTheRedNinja : You could do it, the project is editable.


Figure out the appropriate size for larger Heroku Dynos

From https://devcenter.heroku.com/articles/dyno-types , the important differences are:

Dyno Type
Memory (RAM)
Relative Compute Performance
$ / month
$ / year

hobby
512 MB
1x-4x
$7
$84

standard-1x
512 MB
1x-4x
$25
$300

standard-2x
1024 MB
4x-8x
$50
$600

performance-m
2.5 GB
11x
$250
$3000

performance-l
14 GB
46x
$500
$6000

Generally, a Django web server should typically not require over 512MB to run. Workers may require more than this, but we want to deploy those to EC2 instead, which has more favorable memory balances and GPU support. One possible source of memory bloat could be the side effects of importing third party modules. Rather than doing these imports at the file level, where the web server will also import them, they could be done only within the functions that actually need them, which will practically only be executed by the worker.

This issue is here for reference. Closing


Use MapView and Google MapView in same ViewGroup

I need to switch between Osmdroid Mapview and Google MapView, here the code I need to change:
// used to add Osmdroid MapView into container - frame layout
container.removeAllViews();
osmMapView = new MapView(container.getContext());
container.addView(mapView);

// used to add Google MapView
container.removeAllViews();
GoogleMapOptions googleMapOptions = new GoogleMapOptions();
googleMapOptions.mapType(GoogleMap.MAP_TYPE_SATELLITE);
mapView = new MapView(container.getContext(), googleMapOptions);
mapView.onCreate(new Bundle());
container.addView(mapView);
mapView.getMapAsync(this);

when I added the Google MapView first, then I can switch to Osmdroid MapView easily without any issue. However, the problem occurs when I try to change from osmdroid to google. Can anyone help? @spyhunter99

strange. what kind of layout are the map views in?

it's FrameLayout:
<FrameLayout
            android:id="@+id/mapContainer"
            android:layout_width="match_parent"
            android:layout_height="match_parent">

        </FrameLayout>

@kingfisherphuoc did you figure this out? I would suggest populating everything from a layout xml file if possible.


Benchmark RTF for all method: Melgan - MBMelgan - Hifigan - StyleGAN

I have 3 questions to confirm my experiment on these vocoder models:
1: Are there anyone have a comparing summaries between all model in RTF (with light and heavy version) ?
2: One more thing is that should we train a multiband hifigan to improve performance of Hifigan (Using stft loss)
3: What is the quality of voice produced by melgan and multiband-melgan, which is better?

Here's an RTF summary: https://github.com/xcmyz/FastVocoder#rtf


Contributing to: us-wa-city_of_spokane.json

Adding/Updating us-wa-city_of_spokane.json

Hey @ingalls @aaronlidman, I'm looking at the points shapefile from http://www.spokanecounty.org/MapLoad/zipdata/parcweb.zip right now and it doesn't seem to have any address data.


Does omniauth support Ruby 2.2?

The README does not mention Ruby 2.2 but Ruby 2.2 was added to the Travis CI test matrix (https://github.com/intridea/omniauth/commit/46938eb5a7539ff1794c7c6f5fd438acc7e4b272) so I assume is supported. There is also a pull request (https://github.com/intridea/omniauth/pull/797).

[ ] Add to the list of supported ruby versions

I'm using omniauth with Ruby 2.3 in production, and have not run into any problems.


Touch up formatting

Import to the module and not the object.
Add appropriate newlines for top-level objects.
Add comments to explain why some bare imports are occurring.
Normalize style of quotes used.

Closing as I'm using only portions of the PR, which I'll submit in a different one.


Add SHARK token for Shark Protocol

Description

Adding token: SHARK from chain Migaloo
Checklist

Adding Assets

If adding a new asset, please ensure the following:

[x] Asset is registered to the Cosmos Chain Registry.

The description and/or extended_description of the asset in the Chain Registry is informative.

[x] Add asset to bottom of zone_assets.json.

The IBC channel referenced in path must be registered to the Chain Registry.
osmosis_unlisted defaults to true (until the respesentation and transferring of the new asset has been validated)
Note that it is recommended to include an X (fka, Twitter) profile URL with each asset.

On-chain liquidity
For each new asset, please provide the plan for on-chain liquidity of the asset: (choose one)

[ ] Ready -- A liquidity pool has been created. The pool ID is: ______
[x] Soon -- A pool will be created. (See: Pool Setup Guilde.)

[ ] (optional) A preview of the Osmosis Zone app with the new asset added is requested for creating the pool. (Supercharged Liquidity pools cannot be created via Osmosis Zone app)

[x] StreamSwap -- The token is, or will be, going through a StreamSwap stream; thus, the token should be listed without requiring on-chain liquidity. A Pool ID will be provided in this PR following the stream's completion once the team has had a chance to create a pool using the earned funds.

Please do not edit the osmosis-1.assetlist directly. Only add to zone_assets.

When is the Stream date?

When is the Stream date?

Early March, would you prefer we open a pool before the StreamSwap? We wanted to use the StreamSwap funds to open a pool. Let me know

When is the Stream date?

Early March, would you prefer we open a pool before the StreamSwap? We wanted to use the StreamSwap funds to open a pool. Let me know

It's typical for teams launching via StreamSwap to use the funds to create their first pool, but in that case we won't enlist the asset until the Stream has begun.

When is the Stream date?

Early March, would you prefer we open a pool before the StreamSwap? We wanted to use the StreamSwap funds to open a pool. Let me know

It's typical for teams launching via StreamSwap to use the bootstrapping funds to create their first pool, but in that case we won't enlist the asset until the Stream has begun.

Will it be visible on StreamSwap? I spoke with them and they said it should be visible on Osmosis to be seen on StreamSwap. I can re-confirm with them. Thanks

Will it be visible on StreamSwap? I spoke with them and they said it should be visible on Osmosis to be seen on StreamSwap. I can re-confirm with them. Thanks

As far as I'm aware, their token listing process is separate and doesn't have any strict technical dependency on its visibility on Osmosis Zone. To this point, I think it's only been important (for better UX) that the token is visible on Osmosis before the Stream ends.

I see SHARK is now in a Bootstrapping phase. Are we planning on adding the token to Osmosis now? Perhaps in another PR?


[Event Request]Application “Tests-VAT”, 134051 "ERM VAT Tool - Sales Doc"

[Event Request]Application “Tests-VAT”, 134051 "ERM VAT Tool - Sales Doc"
Could you please insert the OnTestInitialize Event at the beginning of Initialize procedure:

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Update Makefile for newer Frida DevKit versions

New Frida DevKit versions  must also link IOKit and the Security framework. Otherwise it would not be possible to link the devkit core library

Thank you :)


Increase Memory for Alpha Rancher

Currenty we are hitting a memory limit and need to resize the Rancher Droplet.
@datenbrei @roschaefer

Why do we have a rancher droplet? Is it the wrong repository?

Jep it is 😬


🐛 Bug | Issues with add a link shortcut (ctrl+k)

Description
When using ctrl+k to add links, I noticed two small issues that affect usability.

The modal auto focuses on the link name instead of the link address, so when trying to use ctrl+k then ctrl+v to paste, it lands in the wrong spot. Ideally I would be able to chain ctrl+k, ctrl+v, and enter.

After closing the modal to save the link, it jumps to the top of the page. Since I write really long blog posts this means scrolling back down and trying to find my place again. :nerd_face:

Screenshots
None.
Device

OS: Linux Mint
Browser: Vivaldi
Version: not in front of it atm but can check if needed.

Let me know if you need any additional info!

@whoabuddy I was able to reproduce the point 2, I will try to fix this behavior it can be pretty annoying :D
For point 1 indeed that would be a nice improvement, thanks for reporting :)

@pradel Happy to help, sometimes it's the little things! :microscope:

Fixed in the new editor


[EXOD-000] Improve readability througout the application and fix some small styling bugs

The Issue(s)

Add sEXOD ticker wasn't the correct sizing
OHM and sOHM was still refferenced in areas of the dashboad
Font size in the bonding section on the navbar is a little small

Personally found this an issue due to the font in-use even in v1, still present in v2.

Tooltip on the dashboard wouldn't seperate field from value in some certain cases
White font on green button wasn't quite bright enough

Note: I understand that some of these changes may be objective, in that respect I am happy to omit a few if there are disagreements.
Changes
Fix sEXOD ticket

before
after

Fix OHM references

before
after

Bump up font sizes in bond area on the navbar

before
after

Fix tooltip field/value spacing

before
after

Whiten the white font on green buttons
Hardly noticeable but it does help!

before
after

Great, thank you!


feat(protocol): upgrade to endguard 0.0.2 (#4)

There should be tests for both encryption algorithms. Error cases should be covered as well.


Warp Drive PyCuda Error

I am currently running a training script using warp-drive.
I have my environment initialized in this dockerfile.
When running my training_script, I get the following error:
python training_script.py --env simple_wood_and_stone
Inside training_script.py: 1 GPUs are available.
Inside env_wrapper.py: 1 GPUs are available.
/home/miniconda/lib/python3.7/site-packages/torch/cuda/__init__.py:120: UserWarning:
    Found GPU%d %s which is of cuda capability %d.%d.
    PyTorch no longer supports this GPU because it is too old.
    The minimum cuda capability supported by this library is %d.%d.

  warnings.warn(old_gpu_warn.format(d, name, major, minor, min_arch // 10, min_arch % 10))
Initializing the CUDA data manager...
Initializing the CUDA function manager...
WARNING:root:the destination header file /home/miniconda/lib/python3.7/site-packages/warp_drive/cuda_includes/env_config.h already exists; remove and rebuild.
WARNING:root:the destination runner file /home/miniconda/lib/python3.7/site-packages/warp_drive/cuda_includes/env_runner.cu already exists; remove and rebuild.
Traceback (most recent call last):
  File "training_script.py", line 109, in <module>
    customized_env_registrar=env_registry,
  File "/home/miniconda/lib/python3.7/site-packages/ai_economist/foundation/env_wrapper.py", line 208, in __init__
    self.cuda_function_manager.initialize_functions([step_function])
  File "/home/miniconda/lib/python3.7/site-packages/warp_drive/managers/function_manager.py", line 330, in initialize_functions
    self._cuda_functions[fname] = self._CUDA_module.get_function(fname)
pycuda._driver.LogicError: cuModuleGetFunction failed: named symbol not found

was wondering if someone ran into this before or has any idea how to fix it?

I think your running env looks good. The error is here, basically warpdrive does not find your environment step source code in .cu so it cannot initialize your step function
self._cuda_functions[fname] = self._CUDA_module.get_function(fname)
pycuda._driver.LogicError: cuModuleGetFunction failed: named symbol not found

Inside the code, it happens here
In the Foundation wrapper you had
self.cuda_function_manager.compile_and_load_cuda(
                env_name=self.name,
                template_header_file="template_env_config.h",
                template_runner_file="template_env_runner.cu",
                customized_env_registrar=customized_env_registrar,
            )
            print("initialize_functions...")
            # Register the CUDA step() function for the env
            # Note: generate_observation() is a part of the step function itself
            step_function = f"Cuda{self.name}Step"
            self.cuda_function_manager.initialize_functions([step_function])
            self.env.cuda_step = self.cuda_function_manager.get_function(step_function)

Please let me know if you have any problem, I am more than happy to help.

Thanks for your question, @mhelabd
Adding on @Emerald01 's response
For running the simple-wood-and-stone environment with WarpDrive, you would first need to create a CUDA version of the environment. To get started, please see our tutorial: https://github.com/salesforce/ai-economist/blob/master/tutorials/multi_agent_gpu_training_with_warp_drive.ipynb. That shows how to build and train your environment end-to-end with WarpDrive, and also points out nuances like how to name your GPU kernels.
Also, in your current training script, you are pointing to "../foundation/scenarios/covid19/covid19_build.cu", which only contains the paths to the source files for the covid and economy environment, but not the simple_wood_and_stone.
In fact, we do not yet have a CUDA C version of the wood-and-stone environment that can run on a GPU with WarpDrive. If you would like to contribute to that environment, we would love to add it to the repository.
Happy to answer any other questions. Thanks.


Semantic versioning not followed

Thank you for this library. It seems helpful. However there were some breaking API changes between versions 0.4.4 and 0.4.5. This causes builds that rely on CocoaPods to break because it is common to automatically accept patch-version updates. It would be helpful in the future to update the major or minor point versions (e.g., 0.5.0) whenever there are changes to the public API.

Apologies, this duplicates #81 . I will close it.


[SPARK-21195][CORE] Dynamically register metrics from sources as they are reported

What changes were proposed in this pull request?
MetricSystem picks up new metrics from sources that are added throughout execution. If you do measurements via dynamic proxies you might not want to redeclare all metrics that the proxies will create and you'd prefer them to get populated as they're being produced. Right now all sources are processed only onceat startup and metrics are picked up only if they have been registered statically at compile time. Behaviour I am proposing lets you not have to declare metrics in two places.
This had been previously suggested in #18406, #29980,  #31267, #35357 and #36889.
Why are the changes needed?
Currently there's no way to access MetricRegistry that MetricsSystem uses to hold its state and as such it's not possible to reprocess a source. MetricsSystem throws if any metric had already been registered previously.
n.b. the MetricRegistry is added as a constructor argument to make testing easier but could as well be accessed via reflection as a private variable.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Added tests

Can one of the admins verify this patch?

Not stale :/


KAFKA-3664: Commit offset of unsubscribed partitions of the new consumer on a subscription change

When users are using group management, if they call consumer.subscribe() or consumer.unsubscribe() to change the subscription, the removed subscriptions will be immediately removed and their offset will not be committed.
This pull request fixes this issue by performing a commitAsync() in subscribe() and unsubscribe() methods to trigger an offset commit.
Special thanks to @hachikuji and @becketqin for helping out and sharing their feedback along the way.

@becketqin @hachikuji I tried to follow @becketqin's design to implement this PR. A quick test on my side shows that the offsets are being committed now. Would love to have your feedback as I may have missed something here.

@vahidhashemian Can you add some unit tests?

@hachikuji Thanks for reviewing the PR. It is updated as per your suggestion and now includes a unit test.

@vahidhashemian Thanks for the patch. I think there's some details we should sort out as far as how this patch affects commit semantics. For example, if the user changes their subscription and immediately calls commitSync(), do we expect that offsets for the unsubscribed partitions should be committed? Or do we expect this patch to only affect autocommits?
I'm also wondering about an alternative implementation which avoids the additional complexity in SubscriptionState by sending an asynchronous commit in KafkaConsumer.subscribe() prior to changing the subscription when autocommit is enabled. Maybe that would be a simpler if we only expect this patch to affect autocommit behavior?
@becketqin Thoughts?

@hachikuji Thanks for sharing your thoughts and your feedback on the PR. I'll wait until a decision is made on which implementation option we should go with. I am wondering what you see as the issue with committing the unsubscribed offsets even when the autocommit is disabled. I am likely overlooking the details, but to me whether we are autocommitting or not we would want to properly keep track of whatever is consumed and so their offsets (former and current subscriptions alike) should be committed every time.

@vahidhashemian As long as the expectation is clear to the user, I think either way can be OK, but I find it a little bit weird that we would commit offsets for partitions which are no longer contained in the user's assignment. We'll have to be very careful in the documentation to make sure this expectation is clear. I would slightly prefer keeping the assignment consistent with the offset commits so that user can always tell exactly which offsets will be committed in a given call to the commit API.
This is why I suggested the change to use an async commit in subscribe() when autocommit is enabled. It maintains the current invariants as far as consistency between the assignment and offset commits, and it addresses the main problem from this JIRA, which is basically that users will see duplicates when they change subscriptions with autocommit enabled. For users who are using manual commit, they will have to call commitSync() prior to changing their subscription, but that seems reasonable to me.

@hachikuji Thanks for your detailed explanation. They way I understand your alternate approach (and correct me if I'm wrong please) is that the subscribe() method would be changed to something like this:
    @Override
    public void subscribe(Collection<String> topics) {
    	if (!subscriptions.assignedPartitions().isEmpty())
    		commitAsync(subscriptions.allConsumed(), null);
        subscribe(topics, new NoOpConsumerRebalanceListener());
    }

Except that the auto commit status has to be checked there too (I haven't figured out yet how the consumer can see the auto commit status, which is in the coordinator).

@vahidhashemian Yeah, that's what I was thinking, though the check in subscribe() would probably just look like this:
if (autoCommitEnabled)
  commitAsync();

The autoCommitEnabled flag comes from configuration.

Thanks @hachikuji. The reason I added that check in subscribe() is it seems during the first subscribe() call when the consumer is just starting I get this exception:
ERROR Offset commit failed. (org.apache.kafka.clients.consumer.internals.ConsumerCoordinator:515)
org.apache.kafka.clients.consumer.RetriableCommitFailedException: Commit offsets failed with retriable exception. You should retry committing offsets.
Caused by: org.apache.kafka.common.errors.GroupCoordinatorNotAvailableException: The group coordinator is not available.

But if we somehow exclude that one, things seem to work as expected.

@vahidhashemian Ah, I see. It looks like we're missing a check in ConsumerCoordinator.commitOffsetsAsync(). We have the check in commitOffsetsSync(), so perhaps we just need to add it.
@becketqin What do you think about this approach?

@hachikuji I think use commitAsync() is a better approach.
I am thinking about a corner case and not sure if it is possible. The case I am thinking is the following:

User called subscribe() and changed the subscription, an OffsetCommitRequest was put into the queue and not sent out yet.
When user call poll(), a rebalance finished before the OffsetCommitRequest in (1) is sent out. Now the OffsetCommitRequest will fail because it contains the partition that the consumer does not own anymore.

Could this happen?

@becketqin That case may be possible, but I think it might be OK. If a rebalance is already underway and the consumer has sent its JoinGroup (which can actually happen if wakeup() is used in the middle of a rebalance), then any commit is already guaranteed to fail since it won't be handled by the coordinator until the JoinGroup has returned. Alternatively, if a rebalance has begun and the consumer has not yet sent its JoinGroup, then the network layer should guarantee that the commit is sent first. Does that seem right?

@hachikuji Agreed. I think it is working as design like you said. And it probably does not have a big impact either. I checked the code and it looks the entire rebalance process will not be interrupted unless user call wakeup(), so we can probably just do commitAsync().

@hachikuji @becketqin I am trying to write unit tests for the updated approach, but am having some issues. It would be great if you could take a look, as you might spot the problem right away. The unit test is here and the issue I am having is this last line does not run properly and the test hangs there. I am basically trying to change subscription and make sure the last read offset is committed. I hope I am not far off. Thanks.

@vahidhashemian Since the commit was async, it looks we should do a poll() after changing the subscription. But even with the current code, hanging on line 560 still seems unexpected. Usually I would enable logging to see what is going on. @hachikuji Any idea?

@becketqin Thanks for the suggestion. I enabled logging but did not see anything suspicious. If I use consumer.poll(0) it hangs forever in this while loop. If I use consumer.committed(partition) it hangs forever in this other while loop.
And the changes I've made in the branch mentioned above seem to be irrelevant. The updated unit test seems to fail with the current trunk too.

@vahidhashemian It looks like you haven't mocked the offset commit response. This test uses MockClient which requires you to manually setup request expectations and the responses.

@hachikuji Thank you for the pointer. I have not been able any documentation on how to use MockClient. So I'm trying to make sense of it by looking at the existing code.

@vahidhashemian There probably isn't any documentation, but the usage should hopefully be clear enough based on other test cases. The consumer tests are a little tricky because there are multiple sockets which we're trying to mock without needing to depend on the relative order of the calls (since it doesn't matter). The offset commit should come from the coordinator connection, so if you follow the template of the other tests, you should just need to add something like this:
Struct offsetCommitResponse = buildOffsetCommitResponse();
client.prepareResponseFrom(offsetCommitResponse, coordinator);

And you can look in ConsumerCoordinatorTest to figure out how to build the offset commit response.

@hachikuji Thanks again for your help. I looked at ConsumerCoordinatorTest and it seems to me that OffsetCommitResponse does not deal with actual offset value, but rather with committing the offset and making sure the commit is successful. Is it possible that OffsetFetchResponse is what's needed here? I actually tried OffsetFetchResponse in the unit test here without an error; but, even if the answer to my question above is "yes", I'm thinking I'm not doing everything right there. The reason is I am making up the offset fetch result, while I actually want to check what the offset value of partition1 is as a result of running the unit test and changing consumer1's subscription.

@vahidhashemian You may need both. You definitely need the OffsetCommitResponse to avoid retrying the commit forever, and you may need the OffsetFetchResponse as well since the current behavior may be to send an offset fetch after every successful commit.

@hachikuji In the meantime I'm trying to run a successful build, I managed to add two unit tests to verify the impact of the change when auto commit is enabled or disabled. Hopefully they are close to what you expected.

@hachikuji @becketqin I would appreciate your feedback on the latest update (which has two unit tests for when the auto-commit is enabled or disabled). Thanks.

@vahidhashemian Sorry for the delay. Left a few comments.

Thanks @hachikuji for the feedback. Will respond shortly.

@hachikuji I updated the pull request. Hopefully I was able to address your comments. Thanks in advance for taking another look.

@hachikuji I modified the unit tests and did some cleanups as you suggested, plus some extra cleanup that I thought would make unit tests more consistent. Thanks for your thorough reviews again.

@vahidhashemian This mostly looks good, but left a few minor comments.

@hachikuji Thank you for the recent feedback. I updated the PR based on your suggestion.

@vahidhashemian Thanks for the iterations. LGTM.

@hachikuji Thanks again for your time reviewing the PR multiple times.
cc @ewencp @ijuma

@vahidhashemian Sorry for the delay. This version LGTM given the current state of semantics for the consumer and how it modifies the assignment immediately upon subscription changes. I think having to handle this stuff both in the expected place (on revoke) and immediately in each subscription is a bit messy, but the right solution when preserving today's semantics.
I'm ready to commit this, but I think we should also consider whether those semantics should change before doing this (if we changed the semantics, some of this code would not be necessary). Here's my reasoning:

I can't actually think of a pattern for application development that would rely on the current behavior where the assignment is filtered immediately.
Current behavior seems error prone wrt resource cleanup since it isn't unreasonable for a user to expect symmetric calls to onPartitionsAssigned and onPartitionsRevoked.
The behavior today is inconsistent between subscriptions that are a list of topics and regex subscriptions: when you set a regex subscription, the assignment is not filtered immediately after the subscription change.
Very few people probably rely on the intersection of functionality that would be affected: they would have to both pass in a ConsumerRebalanceListener, make subscription changes, and rely on the callback returning the filtered list.

I think it might be worth doing a quick KIP and trying to clean up the semantics if nobody objects. It would be an incompatible change which isn't great, but it is a semantic change (no API compatibility issues to worry about) and as mentioned above, I think in practice it likely doesn't affect many people directly now. Kafka Connect actually could be affected by this if we get some config changes (like subscription) to pass through without requiring a full rebalance. It looks like we actually happen to track the necessary info such that this isn't a problem (because of some offset info we track in its own HashMap instead of relying on the assignment in the consumer), but minor changes to the code could easily break things.

+1 on @ewencp's comment. I think this patch is worth keeping if we think the current (confusing) assignment semantics are worth preserving or if we don't think we have time to change the behavior before the next release. @vahidhashemian If you have time to take on a short KIP, I'd be happy to lend some help.

@ewencp Thank you for reviewing this PR and the thorough explanation.
@hachikuji Sure, I'm up for taking on a KIP and definitely need some help.

@vahidhashemian Awesome :) It's more work to get the KIP through, but I really think it is the right solution.
I would just start with the KIP template, copy it, allocate a KIP number (on the main KIP page) and then just start filling in the text. I think the motivation will be clear given the discussion in this thread, but probably needs to be condensed to be very concise. The proposal is, I think, mostly straightforward. I think the compatibility section may need the most thorough discussion because we are talking about making a breaking semantic change in an interface that has been marked stable. In this section, we'll want to very clearly argue that the number of impacted users will be minimal to zero.
Both @hachikuji and I will be more than happy to review before sending out to the general kafka-dev list so we can try to iron out any kinks before circulating it more broadly.

@ewencp @hachikuji I started a KIP as you suggested, and filled the section based on some of the recent discussions on this PR. I'll publicized the KIP in the main KIP page once you've had a chance to take a look and advise whether I'm on the right track. Thanks.

@vahidhashemian What's the status on this? Do we just need to run a KIP-70 vote thread?

@ewencp There was some positive feedback on the KIP. I could start a vote tomorrow if you think it's time to do that.

@vahidhashemian Yeah, definitely just push the KIP through with a vote if there weren't any objections or unanswered questions left.

@ewencp Forgot to mention that I had informed Spark and Storm users about this potential change and except for one did not receive any feedback on those mailing lists. Not sure if we need to do anything further for that.

@vahidhashemian I think if we've made a best effort to solicit feedback from them, that's all we can really do.

The fix for this defect was provided as part of a PR for KIP-70 (KAFKA-4033). Closing this PR.


No more silly O(N)+ unindexed operations

Done in 451a4904111c23d439cf5b05d8d4ad4a44b48c69, improving performance moderately, but it's still not as fast as we'd like -- possibly because we're returning a very excessive amount of data in the benchmark example request.


Also attempted to solve this in the YAML frontmatter,
which I guessed may work if applied globally, to no avail:
---
transition: none
mermaid:
  init:
    gitGraph:
      showBranches: false
---

All of the above attempts render like this:

Expected behavior
I expect it to render like this, when init.gitGraph.showBranches=false

mermaid live editor example

I see the same thing. Removing the comment %% Add more tasks as necessary in this Mermaid.js block allows Advanced Slides to render it correctly, but with the comment, I get this error.

Parse error on line 18: ...lors of the sectionssection Installatio -----------------------^ Expecting 'taskData', got 'NL'

    ```mermaid
gantt
    title share obsidian notes with zrok

    dateFormat  YYYY-MM-DD
    axisFormat  %m-%d

    section Installation
    Install cross-platform zrok install with Obsidian plugin              :done,    install10, 2023-04-01, 1d

    section Public Share
    Share entire vault                            :done,    public10, after install10, 1d
    Share exports folder                          :done,    public15, after public10, 1d
    Share selected folder                         :done,    public20, after public15, 1d
    Share selected note                           :done,    public30, after public20, 1d

    section Private Share
    Set up private share with authentication      :done,    private10, after public30, 2d

    %% Add more tasks as necessary

    %% Set the colors of the sections
    section Installation   #ff8080
    section Public Share   #ffc166
    section Private Share  #83c995
    ```

This is something essential for me to work out more advanced git graphs. The directives only work outside this (awesome) plugin!

For anyone in the same situation, the issue here is that you don't need the init level in the YAML front matter, for example, this works:
---
transition: none
mermaid:
  gitGraph:
    showBranches: false
---


refactor!: remove nvim-ts dependency

[x] I have read CONTRIBUTING.md
[x] I have read CODE_OF_CONDUCT.md

The new nvim-ts main branch removes a lot of the functionality and brings many performance improvements, but it is not the default branch for now, and won't be for a while. Though, after 0.10 master is pretty much deprecated, and plugins should not depend on nvim-ts utilities besides locals...this will also allow users to use the main branch without these plugins breaking. Thanks!

Note: locals.lua is also not guaranteed to be kept in nvim-treesitter 1.0; only the queries will (most likely) be maintained.
If there are (widely) useful utility functions missing, they should be considered for inclusion in the core API.

The new nvim-ts main branch removes a lot of the functionality and brings many performance improvements, but it is not the default branch for now, and won't be for a while. Though, after 0.10 master is pretty much deprecated, and plugins should not depend on nvim-ts utilities besides locals...this will also allow users to use the main branch without these plugins breaking. Thanks!

Thanks the PR!
To be honest, I am not keen on making braking changes for the not stable work-in-progress branch which is not the default yet. Besides, all proposed changes address tree-sitter based functionality which can choose what approach to use through opts.use_nvim_treesitter. If users want/need to use main 'nvim-treesitter' branch, I'd recommend using opts.use_nvim_treesitter = false for now.
@clason, the one utility function used in 'mini.ai' and 'mini.surround' which I can not find in Nightly is require('nvim-treesitter.query').get_capture_matches_recursively(). Is this considered to be a (widely) used utility function?

Is this a breaking change though? The user-facing behavior should not change, except that users can (but don't have to) drop nvim-treesitter if the "bring their own parser".

require('nvim-treesitter.query').get_capture_matches_recursively(). Is this considered to be a (widely) used utility function?

Not sure; if someone were to make a PR, a quick GH search would tell them. It would also depend on whether this can be easily replicated using already provided functions.

Is this a breaking change though? The user-facing behavior should not change, except that users can (but don't have to) drop nvim-treesitter if they "bring their own parser".

I would assume that such change would require new tree-sitter utilities ported from 'nvim-treesitter' into Neovim core, which makes it a hard dependence on nightly (hence breaking for others Neovim versions). The code in PR seems like a direct copy-paste from 'nvim-treesitter' source code, so can't judge beyond that.

It is just copy-pasted, so it wouldn't be breaking for now

That being said, there's no particular urgency; the deprecation of the legacy nvim-treesitter won't be happening until after the Nvim 0.10 release, probably sometime (late) this summer.

It is just copy-pasted (slightly adjusted), so it wouldn't be breaking for now

Yeah, that's not good enough; you need an actual refactor of the calling code based on current Neovim API. I'd recommend closing this PR and trying again later.

the adjusted bit is adjusted for the current Neovim API

You did not adjust the actual code at all (or sufficiently, it looks like); just a copy-paste leaving references to internal nvim-treesitter code...

oh yeah...I relied on lsp too much, will close for now, my bad

@amaanq If you permit me to be blunt: this PR is a bit of an ill-considered hip shot. The first step should be to look at our own nvim-treesitter-textobjects and do a proper refactor of this (in a separate main branch). After this is done (possibly including upstreaming utility functions), we can take the lessons learned to the broader ecosystem.

yeah that's a good idea, that'd also give me a better sense of how to refactor for nvim-ts main going forward


Exporting slider

SUMMARY:
Exporting slider
GITHUB ISSUE (Open Source Contributors)
JIRA TASK (Eightfold Employees Only):
CHANGE TYPE:

[X] Bugfix Pull Request
[ ] Feature Pull Request

TEST COVERAGE:

[X] Tests for this change already exist
[ ] I have added unittests for this change

TEST PLAN:

Skip for release

Closing this fix commit message and create a pr @darora-eightfold


cleanup(tests,vm_test): Use client instead of virtctl

What this PR does
Use the KubeVirt client instead of using virtctl through a NewRepeatableVirtctlCommand where applicable in tests/vm_test.go.
Internally virtctl uses the same client call, so using virtctl does not provide any additional value.
There are more test cases in this file using virtctl which are not changed in this commit because they need to be moved to subresource_api_test.go or should be dropped entirely.
The correctness of API calls made by virtctl start / stop/ restart is already covered in
unit tests specified in pkg/virtctl/vm/{start,stop,restart}_test.go.
The goal of this and further PRs is to reduce the amount of unnecessary uses of
virtctl in the e2e tests to stabilize tests, to reduce the number of flakes and to
remove redudant tests.
Before this PR:
NewRepeatableVirtctlCommand is used unnecessarily.
After this PR:
The KubeVirt client is used instead.

Fixes #
Why we need it and why it was done in this way
The following tradeoffs were made:
The following alternatives were considered:
Links to places where the discussion took place:
Special notes for your reviewer

Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note

None

/sig code-quality

/retest-required

@xpivarc Addressed

/lgtm


Add release notes for v1.4.9

Add release notes for v1.4.9
Signed-off-by: David Enyeart<EMAIL_ADDRESS>

All comments addressed!

Ok, I'll go ahead and merge... any final fixes can be added in subsequent PR.


New version bump?

I just noticed that the kpi changes[1] are not included in the latest gem version. Do you have plans to release a new version to rubygems soon?
[1] https://github.com/seatgeek/sixpack-rb/pull/21

Absolutely. I can do this later today/early tomorrow.

Wow! Thanks for the fast response :+1:

Figured I'd just do this now and push v1.3.0 to rubygems.


SQLDatabase.from_uri connection to PostgreSQL

Hello everyone,
I am trying to connect to postgresql using:
...
db = SQLDatabase.from_uri('postgresql+psycopg2://user:password@RemoteIP:1234/postgres')
...

Bear in mind that user, password, RemoteIP(like: <IP_ADDRESS>) and 1234 (the port) are dummy data here.
I also installed langchain and psycopg2 on my python environment.
But get two errors:
...
conn = _connect(dsn, connection_factory=connection_factory, **kwasync)
psycopg2.OperationalError: connection to server at "RemoteIP", port 1234 failed: FATAL:  password authentication failed for user "user"

The above exception was the direct cause of the following exception:

...

sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at "RemoteIP", port 1234 failed: FATAL:  password authentication failed for user "user"

I was procedding just as specified in the LangChain documentation and SQLAlchemy documentation but still getting same error.
I hope you can help me please.

Hi there!
Are we able to confirm a connection with just plain-old SQLAlchemy?
from sqlalchemy import create_engine
engine = create_engine('postgresql+psycopg2://user:password@RemoteIP:1234/postgres')

That should tell you if the issue is with the SQLDatabaseWrapper Llama Index uses from LangChain, or if the issue is with connection details such as:

user/pw combo incorrect
hostname incorrect
port incorrect
credentials are correct, but your machine can't talk to the Postgres instance due to network rules

More details:

Helpful guide: https://www.geeksforgeeks.org/connecting-postgresql-with-sqlalchemy-in-python/
Official docs - see box for ""Transaction Isolation Level": https://docs.sqlalchemy.org/en/20/dialects/postgresql.html

If you can't connect via the above, the issue is not with Llama Index but with your SQLAlchemy connection


Process terminal view

Refactoring of Terminal View

move the scroller from TerminalControl into TerminalView
added visual padding around the terminal content
added ability to change fonts and recalculate the terminal dimensions
fixed a couple is miscellaneous layout issues
reduced some of the duplicated layout logic to a class to track cell dimensions
added ability to change fonts and recalculate the terminal dimensions
added ability to change font colors
changed caret view to use a mask

Rename TerminalControl to LocalProcessTerminalView
Introduce a LocalProcess class that sends and receives data from a process

Fixes #53 #54 #52

Fixes an issue where changes are not shown because of a mismatch between the UpdateRange and where the caret is on screen. (add content to the view so that it scrolls, 'clear', then scroll back. The caret will be visibly down the view but the update range will be row 0. this results in invisible text and output on the view).
Implements "userScrolling" in Terminal
Implements SelectedRange (but not 100% sure how to test this)

The thought occurs to me that LocalProcess could have an abstract ancestor "TerminalProcess" (?) and remote / connections could derive from that. LocalProcessTerminalView could be ProcessTerminalView (? ugh) or something nicer sounding.
LocalProcessTerminalView.Process could even be just "Connection" and we could loosely describe a terminal view being connected to something (a local process, a remote process, etc).

Might need to come back and take another look at text selection. We also need to implement double click to select word etc


[FLAVA]Use the ckpt loading helper function instead of PretrainedMixin

Stack from ghstack (oldest at bottom):

#373
-> #372

@deankita has imported this pull request.  If you are a Meta employee, you can view this diff on Phabricator.


Missing ENV variables with Azure Workload Identity Configuration

Describe the bug
I'm trying to get Azure Workload Identity authentication to work. I'm following the documentation for mounted service account. The service account used for the deployment (SA name is external-secret) is configured correctly and its token is mounted to the pod. However, I'm getting the following error in the log:
could not get provider client: missing environment variables. AZURE_CLIENT_ID, AZURE_TENANT_ID and AZURE_FEDERATED_TOKEN_FILE must be set.

I couldn't find any documentation regarding these env variables. From the docs my impression was that setting up the federated identity credentials for the default SA should work.
To Reproduce
Here's the manifest for my SA:
apiVersion: v1
kind: ServiceAccount
metadata:
  annotations:
    azure.workload.identity/client-id: xxxxxxx
    azure.workload.identity/tenant-id: xxxxxxx
  labels:
    app.kubernetes.io/instance: external-secrets
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: external-secrets
    app.kubernetes.io/version: v0.8.3
    argocd.argoproj.io/instance: external-secrets
    helm.sh/chart: external-secrets-0.8.3
  name: external-secrets
  namespace: external-secrets

Secret Store:
---
apiVersion: external-secrets.io/v1beta1
kind: ClusterSecretStore
metadata:
 name: azure-kv-store
 namespace: default
spec:
 provider:
   azurekv:
     authType: WorkloadIdentity
     vaultUrl: "https://yadda-yadda-yadda.vault.azure.net/"
status:
 conditions:
 - lastTransitionTime: "2023-06-19T16:51:58Z"
   message: unable to create client
   reason: InvalidProviderConfig
   status: "False"
   type: Ready

I can see this SA being used in the deployment, too.
Expected behavior
I'd expect the ESO to connect to the KV.
Workaround
Edit: It works, if I pass the serviceAccountRef as follows:
apiVersion: external-secrets.io/v1beta1
kind: ClusterSecretStore
metadata:
  name: azure-kv-store
  namespace: default
spec:
  provider:
    azurekv:
      authType: WorkloadIdentity
      environmentType: PublicCloud
      serviceAccountRef:
        name: external-secrets
        namespace: external-secrets
      vaultUrl: "https://yadda-yadda-yadda.vault.azure.net/"
status:
  capabilities: ReadWrite
  conditions:
  - lastTransitionTime: "2023-06-19T17:55:22Z"
    message: store validated
    reason: Valid
    status: "True"
    type: Ready

I found the solution by searching for AZURE_FEDERATED_TOKEN_FILE on the Azure Workload Identity documentation.
I have forgot to add the required label to the pod:
kind: Pod
metadata:
  name: external-secrets
  labels:
    azure.workload.identity/use: "true"

or in my case adding it in the helm chart:
podLabels:
  azure.workload.identity/use: "true"

I think adding this to the documentation would help many people.

I still have a question though. After adding the pod label I thought I could remove the following annotations since these values are now available through the env variables provided by azure (by adding the pod label). Why is it still necessary to set these on the service account?
    azure.workload.identity/client-id: xxxxxxx
    azure.workload.identity/tenant-id: xxxxxxx

Hey @mruoss, thank you for your PR, regarding your question: this is a Azure Workload Identity specific thing, ESO just uses what is provided by the azwi webhook that injects the env vars into the pod.
There are some docs around the annotations/labels, that should help you. Otherwise, the component is open source, see here. The maintainers are also very helpful and happy to help if you run into issues, just open an issue or ask in Kubernetes slack.

Hey @moolen
Yeah but the thing is: If I don't add the annotations to the ServiceAccount, it does not work. If ESO just uses the ENV vars injected into the pod, then why are the annotations on the SA still required?

Are the env vars the same if you have the Kind=ServiceAccount with or without these annotations? ESO pulls all information from ENV and doesn't even read the Kind=ServiceAccount resource:
https://github.com/external-secrets/external-secrets/blob/51e309258f1637159368459885a0c9783f90783c/pkg/provider/azure/keyvault/keyvault.go#L759-L777
The docs say, there's a default/fallback value used if it is not provided with an annotation. I suspect this could be the culprit.

No, you're right, AZURE_CLIENT_ID is not set. AZURE_TENANT_ID is probably taken from the AKS cluster...


added .env.example for projects generated with laravel new command

Thanks!

@shiftkey My mistake! Just now, I cloned a laravel repo and realized it was mistake to ignore .env.example, because without '.env' and '.env.example', it becomes hard to create .env file. I had to get the file from elsewhere paste it into my workspace.


python3Packages.regenmaschine: 3.1.2 -> 3.1.3

Motivation for this change
Update to latest upstream release 3.1.3
Change log: https://github.com/bachya/regenmaschine/releases/tag/3.1.3
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 128911 run on x86_64-linux 1

3 packages built:

home-assistant
python38Packages.regenmaschine
python39Packages.regenmaschine

@ofborg eval
(Sorry, ofborg's certs recently had an issue, meaning that it was unable to
react to PRs. This has been fixed, but all PRs filed in this period will need
ofborg to be manually kicked off.)


[NPU] add aclnn of tril/bitwise/masked_select/fill_diagonal

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.cai_huan seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Contributed with helpful link

I'm including a link that discusses C++ and I hope it will benefit your repository and help your readers learn more about the subject. I hope you will find this worthy. Thank you.
What does this PR do?
Add resource(s) | Remove resource(s) | Add info | Improve repo
For resources
Description
Why is this valuable (or not)?
How do we know it's really free?
For book lists, is it a book? For course lists, is it a course? etc.
Checklist:

[ ] Read our contributing guidelines.
[ ] Search for duplicates.
[ ] Include author(s) and platform where appropriate.
[ ] Put lists in alphabetical order, correct spacing.
[ ] Add needed indications (PDF, access notes, under construction).
[ ] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

duplicate - in the interactive tutorials list


is this support both side swipe?

hello , did you find a solution to make it swipe from left to right ?
if yes , please share it here

Just implemened that feature https://github.com/baoyongzhang/SwipeMenuListView/pull/48


Confirm deployment

Ref https://github.com/wellcomecollection/catalogue/issues/927
Once a deployment has occurred, we'd like to know when and if it was successful.

Looking good so far.

Looking good so far.
Thinking about how we tag "deployments" as good ... do deployments have unique IDs we can reference (do we store them)?

Looking good so far.
Thinking about how we tag deployments as good ... do deployments have unique IDs we can reference (do we store them)?

Could we not have a field on the deployment as confirmed and have that as a boolean?

@kenoir after looking at the structure, I get what you mean by the ID. We could use the date_created property as it is nano-seconds to do the check?

@kenoir after looking at the structure, I get what you mean by the ID. We could use the date_created property as it is nano-seconds to do the check?

You can find the actual ecs deployment ID amongst the deployment details also which would provide a way to connect ECS deployment to a deployment in the DB.
I'm thinking it might just be better to change the format we store and create a unique deployment ID to look up, then add that to the propagated tags on a deployment.


[#1350] Minimum Roll for skills, abilities and attacks

Allows the global attack, ability or skills to have minimum roll modifier defined and applied.
https://user-images.githubusercontent.com/19979839/174321154-5a558619-a0b6-41bd-ac28-d1521ae580aa.mp4
Resolves #1350

Haven't tested those changes in latest Foundry, but I did my best to fix the merge issues.

One thing to consider, and I'm not sure of a good solution at the moment, is if you have a ability check minimum defined (e.g. minimum 5 on dex checks), and you roll a skill that is normally rolled with that ability, but you change the ability in the configuration dialog. So if you roll a charisma-based Sleight of Hand check, right now it still applies the dex minimum, not whatever minimum charisma ability checks have.
Not sure the best way to fix that at the moment, it might be okay to just leave it to a later patch unless you have an idea.

One thing to consider, and I'm not sure of a good solution at the moment, is if you have a ability check minimum defined (e.g. minimum 5 on dex checks), and you roll a skill that is normally rolled with that ability, but you change the ability in the configuration dialog. So if you roll a charisma-based Sleight of Hand check, right now it still applies the dex minimum, not whatever minimum charisma ability checks have.
Not sure the best way to fix that at the moment, it might be okay to just leave it to a later patch unless you have an idea.

Honestly I don't have a good fix for this currently, as the Formula would have to update after changing the Ability Modifier, to represent the Minimum defined for each of them.
From the look of it, it would have to be done in _onDialogSubmit method in d20-roll.mjs. However I don't think I can manage that. 😕

I found a possible solution for the issue. Please let me know what you think about it!

@szefo09 has created a rebased version at #1760


Basis gate set with RXX gate converted with QASM3 and run with Aer simulator results in 'unknown instruction: rxx_139974866104288'

Environment

Qiskit Terra version: 0.45.1
Python version: 3.10.1

What is happening?
Creating a circuit that results in an RXX gate after being transpiled with a basis set of rx, ry, and rxx and then converting with QASM3 and running on an Aer simulator results in the following error:
Traceback (most recent call last):
  Cell In[79], line 18
    counts = simulator.run(qc, shots=100).result().get_counts(qc)
  File /opt/conda/lib/python3.10/site-packages/qiskit_aer/jobs/utils.py:42 in _wrapper
    return func(self, *args, **kwargs)
  File /opt/conda/lib/python3.10/site-packages/qiskit_aer/jobs/aerjob.py:114 in result
    return self._future.result(timeout=timeout)
  File /opt/conda/lib/python3.10/concurrent/futures/_base.py:458 in result
    return self.__get_result()
  File /opt/conda/lib/python3.10/concurrent/futures/_base.py:403 in __get_result
    raise self._exception
  File /opt/conda/lib/python3.10/concurrent/futures/thread.py:58 in run
    result = self.fn(*self.args, **self.kwargs)
  File /opt/conda/lib/python3.10/site-packages/qiskit_aer/backends/aerbackend.py:435 in _execute_circuits_job
    aer_circuits, idx_maps = assemble_circuits(circuits)
  File /opt/conda/lib/python3.10/site-packages/qiskit_aer/backends/aer_compiler.py:675 in assemble_circuits
    aer_circuits, idx_maps = zip(*[assemble_circuit(circuit) for circuit in circuits])
  File /opt/conda/lib/python3.10/site-packages/qiskit_aer/backends/aer_compiler.py:675 in <listcomp>
    aer_circuits, idx_maps = zip(*[assemble_circuit(circuit) for circuit in circuits])
  File /opt/conda/lib/python3.10/site-packages/qiskit_aer/backends/aer_compiler.py:530 in assemble_circuit
    num_of_aer_ops += _assemble_op(
  File /opt/conda/lib/python3.10/site-packages/qiskit_aer/backends/aer_compiler.py:646 in _assemble_op
    raise AerError(f"unknown instruction: {name}")
AerError: 'unknown instruction: rxx_139974866104288'

Having the basis gate set, the QASM3 conversion, and the aer simulator are all required to reproduce the bug in this manner.
How can we reproduce the issue?
Run the following:
import qiskit
from qiskit import QuantumCircuit, ClassicalRegister, QuantumRegister
from qiskit.circuit.library.standard_gates import *
qr = QuantumRegister(2, name='qr')
cr = ClassicalRegister(2, name='cr')
qc = QuantumCircuit(qr, cr, name='qc')
qc.append(RXXGate(3.1067098743999053), qargs=[qr[0], qr[1]], cargs=[])
qc.measure(qr, cr)

from qiskit import transpile
qc = transpile(qc, basis_gates=['rx', 'ry', 'rxx'])

from qiskit import qasm3
qc = qasm3.loads(qasm3.dumps(qc))

from qiskit_aer import AerSimulator
simulator = AerSimulator()
counts = simulator.run(qc, shots=100).result().get_counts(qc)

What should happen?
The circuit should  be able to run without error.
Any suggestions?
No response

Yeah that's because the RXX gate gets reloaded as Gate and not as RXXGate. That may be because RXXGate is not explicitly listed in the Qiskit standard gates in the exporter and the importer. It would be good if we could automatically populate these using the qiskit.circuit.library.standard_gates.
You can prevent this by re-transpiling before the execution, but that of course takes additional time.


Closure in async lambda throw InvalidOperationException

The following snippet throws InvalidOperationException with message Cannot close over byref parameter '' referenced in lambda ''
        var lambda = CodeGenerator.AsyncLambda<Func<Task<string>>>(_ =>
        {
            var hello = CodeGenerator.DeclareVariable<string>("hello");
            var foo = CodeGenerator.DeclareVariable<Func<string>>("foo");
            CodeGenerator.Statement(Expression.Assign(hello, Expression.Constant("hello")));
            CodeGenerator.Statement(Expression.Assign(foo, Expression.Lambda<Func<string>>(hello)));
            CodeGenerator.Return(Expression.Invoke(foo));
        });

        var compiled = lambda.Compile();

I want to use the AsyncLambda to generate async code from my own DSL but I havn't been able to work around the above issue yet.

Hi @Cooke , thanks for information. At the moment, closures inside of async lambdas are not supported. It's hard to implement this feature because it requires full transformation of inner lambda body and Expression Trees have no information about closure of ParameterExpression.

Thanks for looking into it. Can it be done without changes to Linq Expressions?
I will want to continue my DSL anyhow and need to decide if I should implement it myself (maybe a PR) or switch to transpile to C# then use Roslyn. Any hints on a path forward are appreciated.

I'm working on this change (it is actually committed). However, inner async lambdas will never by supported (at least from my side).

So, the fix is ready. @Cooke , could you please check it from develop branch? And don't forget what I mentioned in my comment above.

Cool thanks. Looks good. I have tested a basic async lambda inside another async lambda and it seems to work, maybe it will become an issue with more complex expressions are involved?

It works only if you don't have closures.

@Cooke , can you confirm that everything is working as expected? If so, I'll publish the package.

@sakno it works as expected. Thank you.

A new package has been published: https://www.nuget.org/packages/DotNext.Metaprogramming/4.7.5


Can't import Bestiary 4 - Centaur Greenspeaker

Can't import statblock:
Centaur Greenspeaker      CR 4
XP 1,200
Centaur shaman 2 (Pathfinder RPG Advanced Class Guide 35, Pathfinder RPG Bestiary 42)
NG Large monstrous humanoid
Init +6; Senses darkvision 60 ft.; Perception +11
Defense
AC 16, touch 12, flat-footed 13 (+3 armor, +2 Dex, +1 dodge, +1 natural, -1 size)
hp 39 (6 HD; 2d8+4d10+8)
Fort +2, Ref +6, Will +11
Offense
Speed 50 ft.
Melee mwk sickle +8 (1d6+3), 2 hooves +2 (1d6+1)
Ranged javelin +6 (1d6+3)
Space 10 ft.; Reach 5 ft.
Special Attacks channel positive energy 3/day (DC 13, 1d6), hex (ward[APG])
Shaman Spells Prepared (CL 2nd; concentration +6)
1st—entangle (DC 15), goodberry, sleep (DC 15); detect undead[S]
0 (at will)—detect poison, guidance, purify food and drink (DC 14), resistance
S spirit magic spell; Spirit Life
Statistics
Str 16, Dex 14, Con 12, Int 14, Wis 18, Cha 14
Base Atk +5; CMB +9; CMD 22 (26 vs. trip)
Feats Combat Casting, Dodge, Improved Initiative
Skills Acrobatics +2 (+10 to jump), Diplomacy +9, Handle Animal +9, Heal +10, Knowledge (geography) +3, Knowledge (nature) +9, Knowledge (planes) +7, Knowledge (religion) +7, Perception +11, Spellcraft +11, Survival +13
Languages Auran, Common, Elven, Sylvan, Terran
SQ spirit animal (owl named Spirit Animal), undersized weapons
Combat Gear wand of burning hands (CL 3rd, 11 charges), wand of charm animal (23 charges), healer's kit; Other Gear +1 leather armor, javelin (4), mwk sickle
Special Abilities
Combat Casting +4 to Concentration checks to cast while on the defensive.
Darkvision (60 feet) You can see in the dark (black and white only).
Empathic Link with Familiar (Su) You have an empathic link with your Arcane Familiar.
Familiar Bonus: +3 to sight-based Perception checks in shadows You gain the Alertness feat while your familiar is within arm's reach.
Shaman Channel Positive Energy 1d6 (3/day, DC 13) (Su) Positive energy heals the living and harms the undead; negative has the reverse effect.
Share Spells with Familiar Can cast spells with a target of "You" on the familiar with a range of touch.
Spirit Animal (spirit animal (owl named Spirit Animal)) If spirit animal is slain, cannot use spirit magic or prepare new spells.
Undersized Weapons (Ex) The creature uses manufactured weapons as if it were one size category smaller than the creature's actual size.
Ward +2 (1 at a time) (Su) Ward another, granting +2 to AC and saves until hit or fail a save.
Hidden deep within the heart of most centaur lands lies their most sacred territory, a place these hybrid creatures call the First Pasture. Centaur greenspeakers hold sway in these spaces, delivering sermons in open fields under both the midday sun and the twilight sky. Here tribes celebrate weddings, harvests, and births under the sun's warm glow, and perform rites of adulthood, rituals to bring luck before a battle, and homages to the tribe's ancestors under the sparse light of the moon and stars. Of these celebrations, centaurs revere none more than the death rites their greenspeakers provide for fallen clan members. When the sun sets, the greenspeakers light a great pyre to release the deceased's spirit from her mortal flesh. After the pyre burns through the night and the sun's first rays crest the horizon, the fallen centaur's kin collect the ashes and fertilize the fields with them so that the dead may serve the world anew.
Centaur greenspeakers who cultivate the fields of the First Pasture are known as "Sowers of the Ash." Centaur clans trust these holy preachers to tend to the sacred meadows, where a kaleidoscope of wild flowers blooms from spring to the fading days of autumn. Centaurs use the blossoms as central decorations for their celebrations and ceremonies, and greenspeakers weave the remaining flowers into fragrant mantles that signal their rank in society; the more ornate a greenspeaker's mantle, the more experienced and venerated he is.

Used your latest module that was available as of about 10:30 am. I used Hero Lab to produce this statblock. For greater accuracy, you might want to use one of the online resources. Hero Lab can truncate some of the text -- or inject errors due to a lack of data. All the other statblocks from Bestiary 4 imported -- a total of more than 85% imported!

[ ] Added Support for Spirits

[ ] Reworked Parsing of Spellgroup Contexts (e.g. Spirit, Mystery, Domain etc.)


[RFC]: Add @stdlib/random/array/gumbel

Description
This RFC proposes adding support for creating an array containing pseudorandom numbers drawn from a Gumbel distribution. This is the array creation analog of @stdlib/random/base/gumbel.
Package: @stdlib/random/array/gumbel
Alias: gumbel
Related Issues
None.
Questions
No.
Other

A package with a similar implementation/API design is @stdlib/random/array/beta.

Checklist

[X] I have read and understood the Code of Conduct.
[X] Searched for existing issues and pull requests.
[X] The issue name begins with RFC:.

can I work on this?


Add parameter to feed_meta for selecting a feed

As a developer of a website that has multiple feeds, I would like to call {% feed_meta %} with an argument so that I can select which of the defined feeds is linked from which pages. For example, on my events overview page I would like to link the feed of events (built from the events collection) and not include the default feed of posts.
I made this suggestion in a comment on #334 and do know of workarounds, so this is not high priority for me. I would have tried to help with a solution, but I do not understand enough about Ruby at this point. Thanks for your consideration.

This seems like a nice idea, though I'm not sure about implementation details either.
{% feed_meta %} => same as today
{% feed_meta all %} => unified feed
{% feed_meta events %} => feed for events collection only

WIP Design draft
Community is free to leave feedback in subsequent comments.

Usage examples
{% feed_meta %}                                             // default; current behavior; backwards-compat;
{% feed_meta collection = <label> %}                        // meta tag for /feed/<label>.xml or config override
{% feed_meta collection = <label> category = <category> %}  // meta tag for /feed/<label>/<category>.xml
{% feed_meta category = <category> %}                       // meta tag for /feed/<post-category>.xml
{% feed_meta tag = <tag> %}                                 // meta tag for /feed/by_tag/<tag>.xml or config override

Notes
The plugin has not stabilized  with a v1.0 release. So technically, backwards incompatibility is permissible.
On that note, the primary step forwards would be to streamline how feeds for tags and categories are generated even though the attribute genesis at Jekyll Core is similar for both site.tags and site.categories.

In other plugins, we do key:value Not key = value, is that right? For highlight for example.

The plugin has not stabilized with a v1.0 release. So technically, backwards incompatibility is permissible.

This plugin is used on GitHub Pages and other platforms so it would be fantastic to maintain compatibility with the current behavior wherever possible.


Added my repo with a quick description

Just adding my unorganized repo to your list. The more the merrier!

Glad to have you around @dcplaya !


support for attaching a programattic screenshot

See examples for what's up!
A next step would be optionally allowing the user to decide whether to include the screenshot, for privacy reasons that can be important. At the moment we don't have a need for it, otherwise I'd have jumped on the functionality!

@yoiang Thank you for your modifications!

@rizumita My pleasure, thanks for the great library!


Document api

I am interested in contributing documentation. Do you still need help with this?

Yes, there is no documentation yet.


move test requirements into build requirements

Checklist

[x] Used a 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.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

requirements: run: keras==2.3.0 must contain a space between the name and the pin, i.e. keras ==2.3.0

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.

Hi! This is the friendly automated conda-forge-linting service.
I was trying to look for recipes to lint for you, but it appears we have a merge conflict.
Please try to merge or rebase with the base branch to resolve this conflict.
Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug.

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.

@bw4sz can you re run this, Keras-resnet is merged

@bw4sz these files should be in the source distribution
tests/data/
I do not see them in the distribution
We can add the paths here
https://github.com/weecology/DeepForest/blob/master/MANIFEST.in

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

The recipe must have some tests.

@bw4sz I think We can put imports in the test section, with no command to run

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.

Hi! This is the friendly automated conda-forge-linting service.
I was trying to look for recipes to lint for you, but it appears we have a merge conflict.
Please try to merge or rebase with the base branch to resolve this conflict.
Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug.

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.

@henrykironde i'm merging into master since this actually has a install of deepforest with dependencies. I think we should move the other questions on python 3.8 and (windows?) to a new PR.


No matching processes belonging to you were found, when trying to kill rcssserver

When I run my code, I get
HFO/src/strategy.cpp 198: already initialized.
***ERROR*** Failed to read team strategy.

Then I found out from this issue https://github.com/LARG/HFO/issues/75, that it was because of rcssserver.
I tried to manually kill the process using killall -9 rcssserver, but then it shows.
No matching processes belonging to you were found.
If anyone can help me in this, i would be greatly appreciated.

The issue was that I was not running the server first.
To start the server run the command.
./bin/HFO --offense-agents=1 --defense-npcs=1 --no-sync

Keep in mind there are 2 options in command one is --offense-agents and other is --offense-npcs, npcs means non player character, which HFO provides and agents means the agent which you will connect. You can connect it using any example file like ./example/hfo_example_agent and check the port before connecting.


Refine storage settings screens

We discussed (call #37) that the settings need to be improved (based on PR 158):

Do the two storage setting options need to show the progress bar (which were meant to indicate percentage of hard drive used)?
Storage location can be accessed in duplicate ways (big button and in detailed settings) - remove one of them?
UI elements that open the file picker do not clearly indicate so (they look like regular buttons)
Should "Storage" title be changed to "Storage amount"?

This issue is stale and I think we have a clear design for this. If there are still design discussions to be had, let's open a new issue. Closing this one down, rest in peace, old friend.


Fix payment_provider_id null behavior

SaaSquatch behaves differently when payment_provider_id is explicitly null, rather than omitted. This restores a previous behavior where the user could pass the string 'null' and we would replace it with a null.

LGTM, we should fix the old behaviour so we don't equate null to 'null' though.


Overriding default message for pattern "email"

Here is explained how to override messages:
https://github.com/thedersen/backbone.validation#overriding-the-default-error-messages
_.extend Backbone.Validation.messages, // coffescript
  required: '{0} is required'
  rangeLength: '{0} must be between {1} and {2} characters'

how can specify the message for specific patterns (like "email")?
EDIT: found solution for pattern "email" (you could add it to docs)
_.extend Backbone.Validation.messages,
  required: '{0} is required'
  rangeLength: '{0} must be between {1} and {2} characters'
  email: 'text here'

but what about a custom validator (myPattern)?
_.extend Backbone.Validation.messages,
  required: '{0} is required'
  rangeLength: '{0} must be between {1} and {2} characters'
  myPattern: 'my text here' // <=== This doesn't work

I want to override that cause I want to handle all messages in the same place.

If you want to customize the messages of your own pattern, you should do it in the pattern itself, like:
_.extend(Backbone.Validation.messages, {
  myPattern: 'This is an error message'
});

Keep this in mind:

The validator should return an error message when the value is invalid, and nothing (undefined) if the value is valid.

Hi @chiefGui
there is no way to override message for my pattern outside them? I'd like to manage all the messages in the same place, among the default ones

Do you want this, right?
_.extend(Backbone.Validation.messages, {
  required: '{0} is required',
  myPattern: 'This is an error message'
});

So, you already did this. What's going on? What's the error?
You said:

myPattern: 'my text here' // <=== This doesn't work

But, what's happening?

It gets the message specified inside the custom validator instead of the one specified in the _.extend


Add workflow to rebuild on comments

Add a workflow that will re build the code so that we can do it from the PR

\build


Display asset filesize + link to asset metadata

Display asset filesize and link to asset metadata in the file browser.

Will take a look once I get my dev environment set up again (new laptop).


Is it possible to call pickers directly from Lua?

Pretty much what it says on the tin. vim.cmd is proving unhelpful when it comes to setting variables in lua (always returns nil before the picker actually executes, as far as I can tell.)

Hi! No, but it would be very easy to implement. Just export the one function from the init module. Would you be willing to submit a PR?


Bot crash on errors

Bot crashing due to HTTPError or APIError - When sheet cannot be accessed

Also probably make sheets in constants py optional and therefore make modules optional? (New issue?)

Closed in favor of #44


How to make this work with File scalar in graphql-yoga?

My project requires working with multi-part uploads and I would like to use graphql-yoga's scalar File feature.  I don't see how I can suppress the creation of a File resolver with this plugin though scalarOverrides and instead use the built-in File type that graphql-yoga is passing in.
Am I missing something or is this not possible at this point in time?

I think the fix is to add File to isNativeNamedType().

Hi @taybin , could you please try out this alpha version?
yarn add -D @eddeee888/typescript-resolver-files@pr240-run411-1

And the new definteConfig for your use case may look like this:
defineConfig({
  resolverGeneration: {
    query: '*',
    mutation: '*',
    subscription: '*',
    scalar: '!*.File', // Generate: all Scalar resolvers in all modules, except for the scalar named `File`
    object: '*',
    union: '',
    interface: '',
  },
})

Here's the WIP PR: https://github.com/eddeee888/graphql-code-generator-plugins/pull/240
I'll follow up with more documentation, examples and use cases soon

Will do, thanks!

@eddeee888 Can you explain what the object, union, and interface settings do?  I don't get the link between those and resolvers.

Sure! Maybe the name resolverGeneration is misleading (something we can change before v1). This is the option that tells preset what files to generate (maybe fileGeneration is a better name).

Given this schema:
# src/schema/base/schema.graphql
interface Error  {
  # ...
}

# src/schema/user/schema.graphql
type User {
  # ...
}

# src/schema/book/schema.graphql
type BookError implements Error {
  # ...
}

union BookResult = BookOk | BookError

Then, object option will be responsible for:

src/schema/user/resolvers/User.ts. Normalized name (*) of this file is user.User
src/schema/book/resolvers/BookError.ts. Normalized name is book.BookError
src/schema/book/resolvers/BookOk.ts. Normalized name is book.BookOk

interface option be be resonspible for:

src/schema/base/resolvers/Error.ts. Normalized name is base.Error

union  option will be responsible for:

src/schema/book/resolvers/BookResult.ts. Normalized name is book.BookResult

'*' will generate every file of the relevant type. '' won't generate any files.

(*) Normalized name is important (and will be documented ) as we use can use wildcard to choose what we want to generate.
Example: some graphs have a standard to wrap results in wrappers e.g. object types ending with Ok or Error. These usually don't have logic in them but are generated anyways by the preset. resolverGeneration allows us to avoid generating these wrapper types:
resolverGeneration: {
  // ... other config
  object: ['!*Result', '!*Error']
}

Right now, the default resolverGeneration option is recommended which generates all files except for unions and interfaces i.e.
resolverGeneration: {
  query: '*',
  mutation: '*',
  subscription: '*',
  scalar: '*',
  object: '*',
  union: '',
  interface: '',
},

This suppresses the File resolver generation.  I haven't tested it yet, but:
      scalarsOverrides: {
        File: {
          type: 'File',
        },
      },

seems to be how to get the appropriate type generated for graphql-yoga.

Oh, last bit of feedback, typescript didn't know the new type for resolverGeneration.  Not sure if you've set that up yet or not.

Thanks @taybin !
Once this is released, I'll look into adding File-related config into GraphQL Yoga guides.
For types, I can see options being recommended if an object is used:

I cannot find an easy way to type the expected values of each option though as it's a globby pattern for our GraphQL types. If you know how, let me know!

Hi @taybin ,
This is now available in v0.8. Thank you for collaborating with me!


Using Kotlin DSLs for creating CompletionRequest, ImageCreationURL, ...

As I mentioned on Twitter, your design is close to what I would have done, except that I like DSL-style builders instead of constructors.
It does require a bit of boilerplate code, but I think the experience for the user is nicer.
Would you be open to something like that? Note that it is completely backwards compatible, i.e. you can still write the old constructor code if you want to.
import FooFactory.Companion.Foo
data class Foo(val bar: String, val baz: String)
class FooFactory {
lateinit var bar: String ; lateinit var baz: String
private fun build(init: FooFactory.()->Unit): Foo { this.init(); return Foo(bar, baz) }
companion object { fun Foo(init: FooFactory.()->Unit): Foo = FooFactory().build(init) }
}
fun main() {
val foo1 = Foo {
    bar = "Bar"
    println("hi")
    baz = "Baz"
}

val foo2 = Foo (
    bar = "Bar",
    baz = "Baz",
)

println(foo1 == foo2)

}
// hi
// true

Hi @headinthebox 👋

Would you be open to something like that?

Yes, sure, why not! I like the idea!

Note that it is completely backwards compatible

That's a big plus indeed! I am also considering making a major (because of this PR), so I think it's right time to enhance the APIs! :)

Cool. You can probably generate all the code using chatGPT since it is so structured ;-)

Hi again 👋  I've created a new release 3.0.0-alpha01 with the new DSL, please give it try :)


DELIA-48037 : revert some changes

Reason for change: Fix LinkType. Recent changes break callsign.
Test Procedure: See ticket.
Risks: Low
Signed-off-by: Nikita Poltorapavlo<EMAIL_ADDRESS>

I know there is a pull request open to avoid this "seemingly" unnecessary dot in the version (https://github.com/rdkcentral/Thunder/pull/387) but that pull request has not yet been merged as a discussion is ongoing.
So I am a bit lost where this "revert some changes" is coming from ?
Could you please eleborate what commit it is reverting?

I know there is a pull request open to avoid this "seemingly" unnecessary dot in the version (https://github.com/rdkcentral/Thunder/pull/387) but that pull request has not yet been merged as a discussion is ongoing.
So I am a bit lost where this "revert some changes" is coming from ?
Could you please eleborate what commit it is reverting?

The change was added in https://github.com/rdkcentral/Thunder/commit/bbc9e011fc39a32ec5d747eb263f922f1668c042#diff-3e2803855ede8078d10ef85f75f1ad93fb59a0937de9d0ee97b00c52cad36302
_callsign unlike callsign is without the version part so _versionstring is empty.

The change was added in https://github.com/rdkcentral/Thunder/commit/bbc9e011fc39a32ec5d747eb263f922f1668c042#diff-3e2803855ede8078d10ef85f75f1ad93fb59a0937de9d0ee97b00c52cad36302
_callsign unlike callsign is without the version part so _versionstring is empty.

@pwielders , waiting code review

@pwielders , waiting code review


Update for OmnisciDB release 5.3.0

Checklist

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

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.

The omniscidb sanity tests fail due to https://github.com/conda-forge/omniscidb-feedstock/issues/7

Skipping 5.3 due to https://github.com/conda-forge/omniscidb-feedstock/pull/14


If max prop changes dynamically, marker one would not get to the end of the track

[x] I have searched existing issues
[x] I am using the latest multi slider version

If you're going to set the max prop dynamically, probably based on a state change and you only have one marker, it would not go until the maximum value and/or position.
Test code to reproduce the issue: https://snack.expo.io/BkX6n6iV7
Steps to Reproduce

Set up one Multislider component with one marker
Initialize a state with two possible values (e.g.: DAYS, HOURS)
Set max prop dynamically based on the above state (e.g.: max={this.state.type === 'DAYS' ? 7 : 12})
Change state, check to see marker's position at maximum value

Expected Behavior
Marker should go all the way to the end of the track.
Actual Behavior
Marker stays at the value and position before the maximum one.
Testing findings
It looks like marker one calculates the maximum position based on this.state.positionTwo. By default positionTwo is undefined which is fine. When the max prop is set, it gets into componentWillReceiveProps where positionTwo gets some values regardless if it is enabled or not - which therefore, breaks the first one.

First good bug report I've ever received, will try to fix this but it on be until end of August since i'm currently on vacation. Thanks for providing a example repo

@ptomasroos Because I had to make it work as I have a short deadline, I solved it like this:
if (nextProps.values[1]) {
  var positionTwo = valueToPosition(
    nextProps.values[1],
    this.optionsArray,
    nextProps.sliderLength,
  );
  nextState.valueTwo = nextProps.values[1];
  nextState.pastTwo = positionTwo;
  nextState.positionTwo = positionTwo;
}

BUT, I would like you to implement something that you think it works best in all scenarios because you know your project better and how it would affect things.

Thanks for the feedback!

Yes, it should be fine to render the updated min/max values. I only checked the issue for the max prop.
It would be nice to be able to set dynamic values based on state changes instead of just constrain it to what it is set when the component is first rendered, which actually work now, but it breaks for the max value as described above.
Sorry for my very late response

For me I fixed it with allowOverlap={true}.

@Dror-Bar Yes, that indeed seems to fix it. Tested on the initial test code above.
Though, I still think there's a small issue in there and I think it shouldn't require that flag in order to work correctly.


notification are not available, IE11 + Windows7

Hi,
I would like to use try this feature but seems not made available for IE11+Windows7.
could there be any settings needed to make it works? because I see that you have tested this in similar environment. should there be steps needed prior working on this, please help me to do it.
#IE11 #Windows7
thanks
regards,
asy

Hello,
In order to try and use it in Internet Explorer one has to firstly install the addon extending Internet Explorer with this functionality.

could you tell the addon name?

This project is that addon.


[Week 8] DG User Stories

Update DG
Added low-priority user stories.
Going forward, we can refer to the DG for user stories (and not the user
stories board).
Closes #53.

I have closed our old user stories project.


Prepare featured launch of OptMeowt

As we just discussed with @asoltani, we will have the various browser and extension launches featured on Twitter, at which point the extension and landing page should be polished. There is nothing concretely to do at this point. I am opening this issue in case there are any launch-specific things that we should discuss.

Seems we have not discussed anything.


Handle skip_stmt in a systematic way

The current implementation uses HardcodedFilter() in postgres_protocol_handler to filter the query types that are not supported in our system. This is hacky and does not take into account some corner cases such as empty query. Besides, it also mixes non-supported query type with nested query prevention.
The correct way to do this is probably to filter in traffic_cop. As this is not only relevant to Postgres protocol but also potentially other protocols.
Also, I am wondering if we want to support nested txn @apavlo ? We may do this now since traffic_cop can support it, and the protocol_handler is blocking it in HardcodedFilter(). @yingjunwu Would this violate any design with txn_manager? If we do not want it then I would change the code in traffic_cop to block it.

Are you asking whether supporting nested transactions requires any major changes to the current transaction manager?

Or any changes?

We do not support nested transactions for now as (1) I am not sure how read/write set could be tracked; (2) Some synchronization between inner and outer transactions must be added; (3) logging must be aware of this type of transaction.
I will think about it later. Let's make logging happen first.


I have some problems with the implementation of backward code

I noticed that the backward part using xyz directly from mean4D. But in my opinion, in forward flow, the conditional xyz,  which is inferenced from xyz(from mean4D) by eq(9) in your paper , is used in later work(projection, calculate depth). So I am doubt why don't use condional xyz in backward flow.

Hi, @Ma1hn,
Great observation! The information required for calculating the gradient from depth is already written in geomState during forward process, so it's not related to the 3D means. However, the updated 3D means should indeed be involved in computation of the gradient of the 3D means from the 2D means. I ignored it as I stopped debug until I found the current version was already enough to reproduce the performance of the python version, and the gradients were also very close to those in the python version. This might be because the gradient of the 3D means is mainly dominated by other parts, and the difference between the 3D means at different time is relatively small.  I’ve fixed it in the latest commit. Thanks for your reminder!


Kestrel config binder should understand * and localhost

From @Tratcher on April 27, 2017 17:0
The templates are going to enable SSL via config in dev and production. They need to set up the rest of the endpoints when they do this. https://github.com/aspnet/MetaPackages/pull/44 added the ability to bind to IPs and ports, but that makes for a poor user experience. In dev the templates want localhost, but will have to specify <IP_ADDRESS> (and ::1) if they want IPv6 support. In production they'll need to specify a public IP (<IP_ADDRESS> and ::0).
Config should allow localhost that binds to <IP_ADDRESS> and ::1, and * that binds to <IP_ADDRESS> and ::0, using the same logic that kestrel applies to UseUrls values. Even better, implement this in Kestrel with a Listen that takes the string ip/host so you don't have to duplicate all of the logic.
Copied from original issue: aspnet/MetaPackages#73

From @Tratcher on April 27, 2017 17:14
@danroth27

@muratg @DamianEdwards @Eilon We chatted about this one and we think we need to get this into preview1. @muratg please assign.

We chatted even more and the fix is more complicated than we want to take right now. We'll have to tell folks to browse to localhost.

From @muratg on May 25, 2017 22:14
Assigning to @cesarbs for post preview2.

From @Tratcher on June 1, 2017 16:15
Note this code is moving to Kestrel. https://github.com/aspnet/KestrelHttpServer/pull/1878

@glennc This issue is also the first in a series of issue that prevents enabling docker for out templates that use authentication.

@glennc This issue is also the first in a series of issue that prevents enabling docker for out templates that use authentication.

I'm also seeing a port forwarding issue with the "dotnet new web" template and the current docker image "microsoft/dotnet"
I also see the warning with "Unable to bind to http://localhost:5000 on the IPv6 loopback interface: (Error -99 EADDRNOTAVAIL address not available)".
root@24cf43adf652:~# dotnet new web -o www
Content generation time: 74.6508 ms
The template "ASP.NET Core Empty" created successfully.
root@24cf43adf652:~# cd www/
root@24cf43adf652:~/www# dotnet restore
  Restoring packages for /root/www/www.csproj...
  Generating MSBuild file /root/www/obj/www.csproj.nuget.g.props.
  Generating MSBuild file /root/www/obj/www.csproj.nuget.g.targets.
  Writing lock file to disk. Path: /root/www/obj/project.assets.json
  Restore completed in 680.72 ms for /root/www/www.csproj.

  NuGet Config files used:
      /root/.nuget/NuGet/NuGet.Config

  Feeds used:
      https://api.nuget.org/v3/index.json
root@24cf43adf652:~/www# dotnet run
warn: Microsoft.AspNetCore.Server.Kestrel[0]
      Unable to bind to http://localhost:5000 on the IPv6 loopback interface: (Error -99 EADDRNOTAVAIL address not available)
Hosting environment: Production
Content root path: /root/www
Now listening on: http://localhost:5000
Application started. Press Ctrl+C to shut down.

My current solution is amending the Program.cs file to include .UseUrls("http://*:5000") which fixes port forwarding and removes the warning
public static void Main(string[] args)
{
    var host = new WebHostBuilder()
        .UseUrls("http://*:5000")
        .UseKestrel()
        .UseContentRoot(Directory.GetCurrentDirectory())
        .UseIISIntegration()
        .UseStartup<Startup>()
        .Build();

    host.Run();
}

@pflannery try using the microsoft/aspnetcore image instead. This image is designed to host web apps, and contains settings, such as ASPNETCORE_URLS, that solve this issue for you.

@natemcmaster Thanks. I just tried that and get blocked when running dotnet --info
root@29095298643c:~# dotnet --info
Did you mean to run dotnet SDK commands? Please install dotnet SDK from:
  http://go.microsoft.com/fwlink/?LinkID=798306&clcid=0x409

Following that link didnt seem to solve my issue so I tried to run through the linux debian sdk commands here https://www.microsoft.com/net/core#linuxdebian but still same problem.
Following https://www.microsoft.com/net/core#dockercmd gets me as far as the EADDRNOTAVAIL error I reported above.

@pflannery If you need to build an app in the container, use microsoft/aspnetcore-build. Let's continue this discussion here https://github.com/aspnet/aspnet-docker as this is separate from the intent of this issue.

This issue was moved to aspnet/AspNetCoreModule#136

I think this was closed in error, the EADDRNOTAVAIL issue was unrelated to the original configuration issue.


Add Wren support to Ace Editor

I suppose we're going to need to do this ourselves also?  Do we have anyone who might be able to assist with that?  They could use my Highlight.js grammar as a starting point...

I guess you should. I have no idea if there is anyone that has any previous experience with this. You could ask on Slack.


fix spelling

http://www.future-perfect.co.uk/grammar-tip/is-it-targetted-or-targeted/ :wave:

This is included in #180


snapshot_test throwing lots of "Error starting node1"

This test loads up a multitude of failures from a few tests, repeating the same errors "Error starting node1" and "Unexpected error in node1 node log: ['ERROR [main] ... CassandraDaemon.java: Detected unreadable sstables ..."
http://cassci.datastax.com/job/trunk_dtest/62/testReport/snapshot_test/

Merging with #102


Add IBM Plex

Hi there, IBM Plex was just released and looks to be a really nice programming font, it would be cool to have this included!
https://ibm.github.io/type/

fixed in a8134b9