Xcode 12.2 support

Officially support Xcode 12.2 whose beta#2 is available right now. \cc @RainNapper @ob

+1 on this. Under Catalina/Xcode 12/iOS 14, bluepill won't even come up.
bluepill --xctestrun-path /Users/vn50v8w/Library/Developer/Xcode/DerivedData/XXX-gvsecbrvsntufqalpwmusjzuwuns/Build/Products/XXX_AppSharedDefault_iphonesimulator14.1-x86_64.xctestrun \
-o ./bluepill-build/ \
-n 6 \
-L  \
-r  'iOS 14.1' \
--unsafe-skip-xcode-version-check \
-a /Users/vn50v8w/Library/Developer/Xcode/DerivedData/XXX-gvsecbrvsntufqalpwmusjzuwuns/Build/Products/Debug-iphonesimulator/XXX.app

yields...
{94882} 20201102.094140 [  INFO  ] (BLUEPILL) Using xctestrun configuration
2020-11-02 09:41:40.736 bluepill[94882:22030218] -[__NSArrayM objectForKey:]: unrecognized selector sent to instance 0x7fc350c04570
2020-11-02 09:41:40.736 bluepill[94882:22030218] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSArrayM objectForKey:]: unrecognized selector sent to instance 0x7fc350c04570'
*** First throw call stack:
(
	0   CoreFoundation                      0x00007fff350cdb57 __exceptionPreprocess + 250
	1   libobjc.A.dylib                     0x00007fff6df195bf objc_exception_throw + 48
	2   CoreFoundation                      0x00007fff3514cbe7 -[NSObject(NSObject) __retain_OA] + 0
	3   CoreFoundation                      0x00007fff350323bb ___forwarding___ + 1427
	4   CoreFoundation                      0x00007fff35031d98 _CF_forwarding_prep_0 + 120
	5   bluepill                            0x000000010be95d5f +[BPXCTestFile BPXCTestFileFromDictionary:withTestRoot:andXcodePath:andError:] + 107
	6   bluepill                            0x000000010be82003 +[BPApp testsFromXCTestRunDict:andXCTestRunPath:andXcodePath:withError:] + 574
	7   bluepill                            0x000000010be825bb +[BPApp appWithConfig:withError:] + 1049
	8   bluepill                            0x000000010be79639 main + 971
	9   libdyld.dylib                       0x00007fff6f0c1cc9 start + 1
	10  ???                                 0x000000000000000d 0x0 + 13
)

Somewhere we changed test info from an array to a dict. Worth investigating.

Looking into this.

@mcstoufer can you share the XXX_AppSharedDefault_iphonesimulator14.1-x86_64.xctestrun file?

FYI, I think the lack of Xcode 12.2 support is keeping Bluepill 5.4.2 from being upgraded on Homebrew: https://github.com/Homebrew/homebrew-core/pull/66592

@carlocab  the homebrew-core issue seems different from this one.
@mcstoufer  it seems Bluepill wants a dictionary from the xctestrun file for a field but instead it got a NSArray. Like @ob mentioned would you be able to share the xctestrun file so we can find the root cause?

@chenxiao0228 I don't see the difference, I'm afraid. Do you mind elaborating a little?

I think what @chenxiao0228 means is that the error in the Homebrew CI run is:
error: The linked framework 'CoreSimulator.framework' is missing one or more architectures required by this target: arm64. (in target 'bp' from project 'bp')
error: The linked framework 'CoreSimulator.framework' is missing one or more architectures required by this target: arm64. (in target 'bplib' from project 'bp')

which sounds like the Simulators installed on that machine have been stripped of the arm64 target architecture (which is what real iPhones use). We can work around that here by making sure we only build for x86_64 since we are only targeting the Simulators, although with the new M1 based machines it's unclear how this will work out...

@ob Thank you for the explanation. It seems like this

We can work around that here by making sure we only build for x86_64

might help fix the build failure over at Homebrew. I'm not too familiar with bluepill; if you have a quick explanation of how to do this I'd appreciate it. Otherwise, I'll try to figure it out.

I have skipped 12.2 and looking at 12.3 now. There are several issues I have found so far.
Xcode 12.3 builds for Apple Silicon arm64 but CoreSimulator only has arm64e slice. We will have to disable the arm64 target.
Then I also saw some issues with nm. Will get to it soon.

I have skipped 12.2 and looking at 12.3 now. There are several issues I have found so far.
Xcode 12.3 builds for Apple Silicon arm64 but CoreSimulator only has arm64e slice. We will have to disable the arm64 target.
Then I also saw some issues with nm. Will get to it soon.

Fixed in v5.6.0

Fixed in v5.6.0

5.6.0 seems to have also fixed the Homebrew build. Thanks!

5.6.0 seems to have also fixed the Homebrew build. Thanks!


wrong temperatures

any idea on this? the original gui does reflect e.g. the outside temps correctly

I can confirm that these wrong numbers only appeary when the temps are below 0 celsius. Is there any easy way to fix this?

as we are approaching heating times again is there any possible fix to this?


[ci_yaml] Auto roller cc's an oncall group on failures

During bringup, it will cc<EMAIL_ADDRESS>on failures, however, it should be looping in the oncall instead.

go/gwsq-gerrit

/cc @keyonghan

Created<EMAIL_ADDRESS>email sent to this address will be forwarded to the current oncalls.

https://flutter-review.googlesource.com/c/recipes/+/17942


Update shared:akka, shared:core, shared:fs2, ... to 1.3.14

Updates

com.softwaremill.sttp.shared:akka
com.softwaremill.sttp.shared:core
com.softwaremill.sttp.shared:fs2
com.softwaremill.sttp.shared:fs2-ce2
com.softwaremill.sttp.shared:monix
com.softwaremill.sttp.shared:ws
com.softwaremill.sttp.shared:zio
com.softwaremill.sttp.shared:zio1

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

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.softwaremill.sttp.shared" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.softwaremill.sttp.shared" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, version-scheme:semver-spec, commit-count:1

Superseded by #1850.


SalesforceRest connector sObjectGetUpdated action is not working correctly

In the connector implementation, the sObjectGetUpdated is refering to the resource /deleted as shown below
 @doc:Description{ value : "Retrieves the list of individual records that have been updated (added or changed)      within the given timespan for the specified object"}     @doc:Param{ value : "sf: The salesforcerest connector instance"}     @doc:Param{ value : "apiVersion: The api version to send request to"}     @doc:Param{ value : "sobjectName: The relevant sobject name"}     @doc:Param{ value : "startTime: The start time of the time span"}     @doc:Param{ value : "endTime: The end time of the time span"}     @doc:Return{ value : "response message"}     action sObjectGetUpdated(ClientConnector sf, string apiVersion, string sobjectName, string startTime, string endTime) (message)      {         string httpMethod;         string requestURI;         message requestMsg = {};         message response = {};         requestURI = "/services/data/" + apiVersion + "/sobjects/" + sobjectName + "/deleted/?start=" + uri:encode(startTime)         + "&end=" + uri:encode(endTime);         response = oauth2:ClientConnector.get(oauth2Connector, requestURI, requestMsg);         return response;     }
This should be changed to /updated as per the api documentation [1]
[1] https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/resources_getupdated.htm

Fixed in https://github.com/ballerinalang/connectors/pull/120.


fix: minimum amounts

Description
We deprecated minimum in favour of minimumCryptoHuman at some point, but never updated web to match.
This is causing minimum amount issues for quotes in the swapper.
This PR fixes updates all instances of minimum to minimumCryptoHuman, fixing the minimum amount issues we are having (particularly for CoW Swap).
Notice

[x] Have you followed the guidelines in our Contributing guide?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Pull Request Type

[x] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)
N/A - prod bug
Risk
Small.
Testing
Enter a small amount for a CoW swap quote and see that it now correctly prevents the user from proceeding.
Engineering
☝
Operations
☝
Screenshots (if applicable)
N/A

Current dependencies on/for this PR:

develop

PR #4177

PR #4178   👈

PR #4159

This comment was auto-generated by Graphite.


Identify widget does not support version 10.3.1 or project code

Identify widget works within WAB 1.3 and 2.0 on MCS 10.4.0 or greater.  When that same widget is deployed against MCS project code or 10.3.1 it does not return any results.  This is more than likely due to the JS API 3.11 issue that was addressed at 10.4.0 within MCS.
Sudha - what would be the recommended solution for this?
Currently the deployment steps do not include a solution for users of MCS project code or 10.3.1.

closing this as a known limit.  Users can still download a 10.3.1 version of our identify and display widgets.


Modify wrong command

An error occurred when executing the original command. After comparison, it was found that there was a problem with the command on the Chinese document.

/assign @xiangpengzhao

I signed it

the doc is translated from a old version

/lgtm

/approve


Do not consider fees in the payout calculation

Can you make it more clear a bit. I remember it should be equal in the long run. If it was favouring locked on how it was doing that.  Wasn't the existing system does the same. What you outlined here?
Also, I have a proposal to just cut out all the fees generated out instead of just the foundation one. My reasoning is I don't believe these fees never reach any significant amount. When there is some high fee like 500 etc. then we will send it back to the owner which mixes up calculation more. :) From the start, I am just suggesting cutting the fees out of the block when they go significantly towards the coinbase because there is always a possibility of 300-500 snark happening on a block. If there is a significant fee increase where snarks are really ending up to something that we had much more competition on snark marketplace which will drive snark prices up and drop the BP's gainfrom it.
Originally posted by @EmrePiconbello in https://github.com/jrwashburn/mina-pool-payout/issues/58#issuecomment-855887656

@EmrePiconbello I'm separating this out to a new issue where we can clarify further. I'm not sure if you are suggesting that we should simply ignore fees -- which would have the effect of leaving the fees (positive or negative) for the block producer and just payout the pool on the coinbase, regardless of fees. Is that what you mean?
Or do you mean reduce the coinbase by the snark fee amount, and then payout on the remainder? If the snark fees are high (e.g. 500) and their is a MF/O1 delegation, the BP is still required to payout the foundation. Here are a couple of examples, assuming a foundation delegation which is 40% of the pool, and there are unlocked keys for 5% of the pool. These scenarios also ignore pool fees.
1 - "Normal" scenario
Coinbase: 720
Snark Fees: 0.1
Transaction Fees: 0.2
MF/O1 paid: 288
Common paid: 432.1
2 - "Unfair" scenario where current foundation rules hurt the pool
Coinbase: 720
Snark Fees: 500
Transaction Fees: 0.2
MF/O1 paid: 288
Remainder is -67.8 - no payouts should be made?
Are you suggesting in Scenario 1, the Common should be paid 432.0 instead of 432.1?
And what are you suggesting would be best to happen in scenario 2?
Here is a real example - block 26406:
"blocks": [
{
"blockHeight": 26406,
"canonical": true,
"creator": "B62qoRsqqfdfDb3s4nTgTVUQGLep77ZcoKjjWoyxspTn4CEbtBknDek",
"dateTime": "2021-06-02T06:33:00Z",
"snarkFees": "556493109432",
"stateHash": "3NKCYYHBzBSo9qMdEUKkp34m7LY1pZca3h19YBgGriHnDrZbkhux",
"txFees": "2008242050"
},

A less annoying example - block 29884
https://minaexplorer.com/block/3NK9WXPQW4SwEnBwv2yVyyP73quoBim5RVK26YprghceZ4SjP1kq
"blockHeight": 29884,
"canonical": true,
"snarkFees": "25000000",
"coinbase": "720000000000",
"txFees": "21000000"
This one only goes negative by 0.004, but again, with current payout methods, that may be deducted from the payout.

Perhaps the block producer should bear the risk - and reward - for block production.
Meaning there would be no "common" pool - all accounts would be treated just like MF/O1 delegators and would receive their simple pro-rata share of the 720 coinbase, and the unlocked accounts would get their relative pro-rata share of the supercharged 720 coinbase, and the pool operator would simply keep any gains or losses from the block fees for snarks and transactions.
I think that is probably what Emre is proposing, and given the snark fee issues, this probably makes the most sense.

After thinking more about this, the block producer / pool have to be the ones to take the loss -- they are begin compensated for that risk by the 5% of earnings on all the other MF/O1 delegations. I think the best solution is to have the block producer take all risk/reward for fees as suggested above.

I agree with the update it's going to be a limit for coinbase snark so producers can set their limit and take their risk as they prefer. My only concern was mostly about the small producers getting hit by the random high snark fees since that can cause issues for them while it's not likely it happens from time to time.

Closing - will revisit if pool operators request / are really looking for this feature.


Fix jest-hoist for react-native.

Because the Object in the hoist transform had Object.prototype as its prototype, lookups like FUNCTIONS[foo] will break for some keys foo like __defineGetter__. This fixes it.

@facebook-github-bot import

@facebook-github-bot import


Matching Service: Partitioned TaskList for higher throughput

Guys, what's the status of this feature?
From what I understand, currently a single matching service node distributes all the work belonging to a TaskList. What's the impact of this? Does anybody have some throughput measurements? How many tasks per sec can a matcher distribute?
Are there any workarounds for this? A simple one I can think of is duplicating TaskLists into and then starting their workflows in a round robin fashion. Are there such setups supported directly by the cadence client library?

@rpasea This task is currently not funded on our side nor we have an ETA on when we can start working on it.  Fortunately there is a very straightforward workaround as you pointed out.  When starting workers specify multiple tasklist and start a worker for each of them.  For example:
{application}-tasklist-0
{application}-tasklist-1
{application}-tasklist-2

When starting workflow you can randomly pick a tasklist and pass it in as parameter to workflow execution.  Then use this tasklist for scheduling activities from that workflow execution.  We don't have a high level client abstraction which does this automatically but it should be pretty easy to built.
Answer to throughput measurements for a single tasklist depends on what kind of hardware you are using for the deployment.  Here are some numbers which see on our production cluster:
Number of tasks dispatch (with SyncMatch): 400/sec
Number of tasks dispatch (without SyncMatch): 100/sec
Specs:
MatchingHost Memory: 8GB
MatchingHost Cores: 4
Cassandra Memory: 32 GB
Cassandra Cores: 28

Thanks for the thorough response, Samar!
On Mon, Mar 11, 2019, 22:31 Samar Abbas - Uber<EMAIL_ADDRESS>wrote:

@rpasea https://github.com/rpasea This task is currently not funded on
our side nor we have an ETA on when we can start working on it. Fortunately
there is a very straightforward workaround as you pointed out. When
starting workers specify multiple tasklist and start a worker for each of
them. For example:
{application}-tasklist-0
{application}-tasklist-1
{application}-tasklist-2
When starting workflow you can randomly pick a tasklist and pass it in as
parameter to workflow execution. Then use this tasklist for scheduling
activities from that workflow execution. We don't have a high level client
abstraction which does this automatically but it should be pretty easy to
built.
Answer to throughput measurements for a single tasklist depends on what
kind of hardware you are using for the deployment. Here are some numbers
which see on our production cluster:
Number of tasks dispatch (with SyncMatch): 400/sec
Number of tasks dispatch (without SyncMatch): 100/sec
Specs:
MatchingHost Memory: 8GB
MatchingHost Cores: 4
Cassandra Memory: 32 GB
Cassandra Cores: 28
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/uber/cadence/issues/52#issuecomment-471716871, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADxAL7jA2CcL0vJnJ5QnfGEPE6Q1XcBfks5vVr0ugaJpZM4MTrUG
.

Implemented as part of #2229. Assigned to @yux0 for testing and rollout.

core functionality is implemented and rolled out
remaining issue is tracked in #2473 #2483


[CLOUDBREAKER ALLIANCE] Minor Bugfix Fixing images paths

Submission Checklist
Required

[x] The pull request title clearly contains the name of the sheet I am editing.
[x] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[x] The pull request makes changes to files in only one sub-folder.
[x] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

Changes / Description

Fixing path to attunement images. Path was pointing to an inexisting branch. Changed to master.

Character Sheet Info Roll20 Internal Use only.


suggest extracting forward declaration of stan::math::var_value into its own header

Currently (as of version 4.0.1) there's a forward declaration of the templated stan::math::var_value inside vari.hpp:
https://github.com/stan-dev/math/blob/040d515a6551af3aeb046b4816c1eb3a9e6ba527/stan/math/rev/core/vari.hpp#L18
If however I want to also forward declare var_value in my code that builds against Stan-math (because I actually want to forward declare the typedef'd stan::math::var, because I have some custom types templated over both stan::math::var and double, and these types get pushed around into a lot of other headers; #include stan/math/rev.hpp slows compilation times down a lot), I can't just copy-paste that code into my own headers. If I try,  because var_value has a default template parameter, gcc throws
vari.hpp:20:7: error: redefinition of default argument for ‘class<template-parameter-1-2>’
 class var_value;

After some poking around, I discovered this solution on a StackOverflow question, which seems pretty reasonable---put the forward declaration in its own header, which can then be #included wherever necessary.  Because it's then protected by an #ifdef over a #define, the forward declaration will only ever be read a maximum of once.
I have a branch in my fork of Stan-math with a minimal change to implement this:
https://github.com/chenel/math/commit/1dfd0fe1e322e03e866ad8e80b238e1cdb4b6fc3
But I was scared off from making a pull request by the testing requirements (this is my first contribution here and I'm not very familiar with the tests). :sweat_smile:
I also don't know whether there are any other places a similar change ought to be made.
I don't think there are likely any side effects, but you can judge for yourselves...

Thanks for the report.
If the change is simple and is just moving some code around, then just open a PR and it will run all the tests automatically.
i would suggest opening a PR and we can discuss the changes there more easily.

I think this would be nice a PR would be much appreciated! There's def a few spots where we do this and if it's easier for people to fix this then I'm 100% about it

Ok!  pull request created, see above.

Pull request merged, so closing.  Thanks everyone for getting this looked at so fast!


Add ...For Q3D, we would like to obtain the solution data for all the passes, not just the last one. Can you show us the syntax to get it using API? For example, there are three passes in below screenshot.

Description of the feature
For Q3D, we would like to obtain the solution data for all the passes, not just the last one. Can you show us the syntax to get it using API? For example, there are three passes in below screenshot.

@obrienpja , @Samuelopez-ansys , @ThomasGM4
Steps for implementing the feature
No response
Useful links and references
Issue #1650 has helpful snippets to get the last pass.
#1676, #1677

Hi @priti-ashvin-shah-ibm
Sorry for the delay.
The only way I found to obtain this info is:
from pyaedt import Q3d
app = Q3d(specified_version="2022.2")
a = app.post.get_solution_data(expressions=all_C_matrices, context="Original", setup_sweep_name="Setup1: AdaptivePass",
variations={"Pass": ["All"]})
a.active_intrinsic["Pass"] = 2
c2 = a.data_real()
a.active_intrinsic["Pass"] = 3
c3 = a.data_real()
You will get the data at different passes.
In a.intrinsics you will get all possible variations (Passes) so I think it is very easy to implement a loop to obtain all the data at different passes.
Let me know if it is what you need.
Regards

Can you share the link/documentation for syntax to use get_solution_data?
Since the data could converge before max_pass is reached.  Is there a way to determine how many passes are available before entering the loop for each pass?  I am guessing that  cap_data.intrinsics['Pass'] will do that.
When  I execute the below code.  Then compare the different passes, unfortunately, all_cap_data[pass_int] give the same data.  I used the information from both issue threads to write the below method.  Do you have some insight???
def get_capacitance_all_passes(self, setup_name: str):

        all_C_matrices = self.current_app.matrices[0].get_sources_for_plot()

        setup_sweep_name = f'{setup_name}: AdaptivePass'
        cap_data = self.current_app.post.get_solution_data(
            expressions=all_C_matrices,
            context="Original",
            setup_sweep_name=setup_sweep_name,
            variations={"Pass": ["All"]})

        cap_data.active_intrinsic['Freq']  # Is 5.0

        all_cap_data = Dict()
        for item in cap_data.intrinsics['Pass']:
            pass_int = int(item)
            cap_data.active_intrinsic["Pass"] = int(pass_int)
            all_cap_data[pass_int] = cap_data._solution_data_real()

Also, I would like to have for each pass the entire matrix as shown in image.

Hi @priti-ashvin-shah-ibm ,
Indeed, cap_data.intrinsics['Pass'] will give you the passes, in my dummy example:

The usage of "active_intrinsic" is only valid for the current active results. For example this operation:
cap_data.active_intrinsic["Pass"] = 1
It is only applied to the current value:
cap_data.data_real()
The method __solution_data_real(_) is a private method that should not be used. Private methods are methods that public methods are used for some operations. In this case, is the only way to get with one single command all the data, but we are going to expose it as a public method in future releases, but we are starting now the enhancement, I will let you know once we finish.
In summary, _solution_data_real() gets all the results and you could access this info with a similar loop (you see how the first row correspond to the frequency and the second to the passes):

But again, we are going to develop a new method to get all the results in a more simple way.
The documentation of this method is:
https://aedt.docs.pyansys.com/API/_autosummary/pyaedt.modules.AdvancedPostProcessing.PostProcessor.get_solution_data.html?highlight=get_solution_data
But it is a 'complex' method because it can be used in all AEDT apps (Icepak, HFSS...) so it is very general, I found useful debugging to find the best way of using it for each specific case.
Please let me know if my answer was clear.
Regards

Also, what would be expected behaviour if the data converges before getting to max_pass?

Hi @priti-ashvin-shah-ibm,
Checking the picture, I see a different value for each pass. I can see it on this line for example:

It is a dictionary where each key is a different Pass, (5.0, 1.0) is the Freq 5.0 and Pass 1, (5.0, 2.0) is the Freq 5 and pass 2....
For that reason a public method will give easier access to this info, if we wait for the last PR Massimo did, I think accessing this data will be much easier. I will give you the commands for using it once the PR is closed.
About your second question, it is returning nan. In my previous message, you could see the nan values.
Regards

Hi @Samuelopez-ansys ,
Thank you for finding the difference.  I missed that.
I will hold off until Massimo's pull request is merged.  Thank you for your offer regarding, "I will give you the commands for using it once the PR is closed."  Hopefully documentation will also updated with examples.
Regarding convergence, nan works for me.

Hi @priti-ashvin-shah-ibm,
The PR is merged in the main.
Let me describe the new features.
First of all, you could check the available reports using:
current_app.post.available_quantities_categories()
current_app.post.available_report_quantities()
I think it is interesting to check which reports are available for each application.
Now, again doing:
current_app = Q3d(specified_version="2022.2")
all_C_matrices = current_app.matrices[0].get_sources_for_plot()
cap_data = current_app.post.get_solution_data(expressions=all_C_matrices, context="Original", setup_sweep_name="Setup1: AdaptivePass", variations={"Pass": ["All"]})
You will get 2 new properties "full_matrix_mag_phase" and "full_matrix_real_imag":

This will give you all available data directly without accessing to the private method.
And finally... you could activate pandas :)
By default is deactivated, but you have 2 options to activate it:

Before opening the application:
from pyaedt import settings
settings.enable_pandas_output = True

Ant then perform all data obtained with get_solution_data will have pandas format.

Activate it on the current data:
cap_data.enable_pandas_output = True

Please let us know if is what you expected, and close the issues.
Regards,
Samuel

Thank you for your update.  This looks very promising.  I am going to a conference next week.  I may not get to it before I leave.  If not, please understand if there is a delayed response.

Hi @Samuelopez-ansys , I got a chance to look at this merge.  I have two lines of thoughts.  I used the below method:
def get_capacitance_all_passes(self, setup_name: str):

        all_C_matrices = self.current_app.matrices[0].get_sources_for_plot()

        setup_sweep_name = f'{setup_name}: AdaptivePass'
        cap_data = self.current_app.post.get_solution_data(
            expressions=all_C_matrices,
            context="Original",
            setup_sweep_name=setup_sweep_name,
            variations={"Pass": ["All"]})

        # Pandas output should have been set prior to opening Ansys,
        # however, just confirming if changed by user through GUI.
        cap_data.enable_pandas_output = True
        confirm_freq = cap_data.active_intrinsic['Freq']  # Is 5.0

        all_cap_data = Dict()
        for item in cap_data.intrinsics['Pass']:
            pass_int = int(item)  #float to int
            cap_data.active_intrinsic["Pass"] = pass_int
            #all_cap_data[pass_int] = cap_data.full_matrix_real_imag
            all_cap_data[pass_int] = cap_data.full_matrix_mag_phase

        c1_units = cap_data.units_data
        _ = 5  # for breakpoint

I just want to confirm that I don't need the for loop when using enable_pandas_output = True. The current example, has dataframe with three rows.  Which I believe represent each pass.

The image below shows all_cap_data  for my example I am working on.   Based on image I shared  at the start of this issue,  the data appears to be originally, in some kind of table like numpy or dataframe,

The latest commit, returns a dataframe which appears to be, one line for each pass. I would like a 2d format for each pass, which is similar to what one would see in the GUI. It seems like someone took the 2D data and made it 1D for pandas output.
Can I make a request for different format?
For example a list:  zeroth entry is the freq, the 1st entry is 2-d dataframe for 1st pass , 2nd entry is 2-d dataframe for 2nd pass.  I am requesting this since it appears the data appears to be originally in 2-D in Ansys.  The current commit on repo would require every user to receive one row for each pass, then build a 2-d dataframe based on the column names.

Hi @priti-ashvin-shah-ibm ,
For now, we can not perform this modification because it is very specific for Q3D.
When you activate Pandas, pyaedt return the same data but with pandas format, for now we can not refactor the output format because this method is used in many AEDT apps (Icepak, Maxwell...).
If you need this format, you will need for now to reorganize the data. For example, the following code tries to define the format as you suggested:
_all_cap_data_magnitude = []
all_cap_data_magnitude_dict = {}
cont = 0
for f in cap_data.intrinsics['Freq']:
all_cap_data_magnitude.append(f)
for item in cap_data.intrinsics['Pass']:
all_cap_data_magnitude.append(cap_data.full_matrix_mag_phase[0].iloc[int(item)-1])
all_cap_data_magnitude_dict[cont] = all_cap_data_magnitude
cont += 1_
I defined a dictionary in which each key will correspond to a frequency (if more than 1 exists). Then on each frequency, you will have a list, the first element is the frequency, the 2nd a Serie (Pandas format) with the first pass data, 3rd with the second Pass....

I think it is the format you need to make your script easier to use, but for now, PyAEDT can not add new formats because we are still maintaining IronPython.
Of course, PyAEDT is opensource code and you are free (and I would like to see it 👍 ) to modify PyAEDT and improve this part if you see it could be implemented in a general way.
Let me know if you need anything else :)

@Samuelopez-ansys , thank you for giving pandas output and explaining your reasoning .  I wanted to, at least, request what would be helpful for us.  For now we can close this issue.

I think you had indents in the code snippet.  For others, you may want to edit post to format as code, vs text.


TES3MP - stats recorded on login get restored on skill tick

When player logs in to the server that player is going to have X of magicka and Y of fatigue. On each successful spellcast those stats get reverted to their initial values of X and Y respectively. Attaching the video demonstration below. This is probably true for any skill tick, but it's easier to reproduce with spells.
I suspect this LOC is the cause, but I don't know the lua APIs at all.
Players[pid]:LoadAttributes()

Mind that this is with client side mods, but the bug is reproducible on vanilla Morrowind too. Toggling the script on the server is the only thing that causes this.
https://user-images.githubusercontent.com/33513522/210175322-edd29e1e-d6e8-49cd-bc53-4bf4c98bc4ba.mp4
I'm using latest v0.8.1 version of TES3MP.

I was wrong but I was moving into a right direction 😄
This line with Players[pid]:LoadStatsDynamic() causes this issue to appear. Disabling retroactive health fixed that for me for the moment.
Removing the call to recalculate_health from here will probably fix that problem for good, albeit for the price of having to wait till next level for the recalculation to happen.
What do you think?

You're indeed correct on the issue and that line was the cause. I changed it to specifically send the base health value instead of all dynamic stats, this seems to fix the issue, but please double check me on that.
I think the other loads I do (of attributes) should be fine, since base attributes shouldn't be changing client side except on events I listen for?  I'm still not 100% certain I understand tes3mp's network model, though, so I could be wrong.

Looking at the latest change I'd expect to see HP increase in case when skill tick happens and increases owed Endurance by +1, but it does not seem to trigger in real time. I increased Endurance by 10 that way (to be able to see any numbers since we divide Endurance by 10), but it only updated when I re-connected, although I didn't count if the value was correct. It updated and increased again on the next level-up, even though I selected x5 Willpower, x1 Luck and x1 Intelligence.
Looks a bit fishy, but I can't see anything wrong in the code.
Absence of immediate update not a huge problem for me personally though.

I think the other loads I do (of attributes) should be fine, since base attributes shouldn't be changing client side except on events I listen for? I'm still not 100% certain I understand tes3mp's network model, though, so I could be wrong.

Not familiar with it at all, but events look reasonable.

I just pushed a commit, that adds a call to SendStatsDynamic, which might fix that.  I think the issue is that the health isn't being updated client side, and it seemed to work after a quick test on my end.

That does it. Thank a lot.

Yay! I'm glad it's working now, I'll close this issue for now then.


[Bug] [connector-cdc-postgres] Table public.postgres_cdc_table_1 does not exist in Catalog Postgres

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
The following error occurs when testing postgres locally to the cdc of postgres. The configuration is as follows: plugins have been added in plugin-mapping.properties and pom.xml
Is it a configuration problem？
thanks

In addition, the error of running Times on linux is different, please also help to check that the version of seatunnel in linux is 2.3.3

SeaTunnel Version
2.3.4-SNAPSHOT
SeaTunnel Config
env {
  # You can set engine configuration here
  execution.parallelism = 1
  job.mode = "STREAMING"
  checkpoint.interval = 5000
  read_limit.bytes_per_second=7000000
  read_limit.rows_per_second=400
}

source {
  Postgres-CDC {
    result_table_name = "customers_mysql_cdc"
    username = "postgres"
    password = "123456"
    database-names = ["postgres"]
    schema-names = ["inventory"]
    table-names = ["postgres.inventory.postgres_cdc_table_1"]
    base-url = "jdbc:postgresql://<IP_ADDRESS>:5432/postgres?loggerLevel=OFF"
  }
}

transform {

}

sink {
  jdbc {
    source_table_name = "customers_mysql_cdc"
    url = "jdbc:postgresql://<IP_ADDRESS>:5432/postgres?loggerLevel=OFF"
    driver = "org.postgresql.Driver"
    user = "postgres"
    password = "123456"

    generate_sink_sql = true
    # You need to configure both database and table
    database = postgres
    table = inventory.sink_postgres_cdc_table_1
    primary_keys = ["id"]
  }
}

Running Command
./bin/seatunnel.sh --config ./config/postgrescdc_to_postgres.conf -e local

Error Exception
1.java.lang.RuntimeException: Plugin PluginIdentifier{engineType='seatunnel', pluginType='source', pluginName='Postgres-CDC'} not found.

2.org.apache.seatunnel.api.table.catalog.exception.TableNotExistException: ErrorCode:[API-05], ErrorDescription:[Table not existed] - Table public.postgres_cdc_table_1 does not exist in Catalog Postgres.

Zeta or Flink or Spark Version
No response
Java or Scala Version
1.8
Screenshots
No response
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

What version of the code are you using?

What version of the code are you using?

Use the code of your pg-cdc branch

Is 2.3.4 going to be updated soon? Do you know if pg-cdc is supported and when？

Is 2.3.4 going to be updated soon? Do you know if pg-cdc is supported and when？

Will be updated recently, pg cdc is in release planning,I updated the pg-cdc code so you can try it out and it is currently available, config may refer to https://github.com/apache/seatunnel/pull/5986/files#diff-7bb4d909661d759ac77cfe15a0a5fcefb6004c3ef0bf7b18e36d081b4d3868bd

Using SeaTunnelEngineExample testing requires adding a dependency to the pom


chore: fix demo links in readme

The links to the demo files were broken in the readme.

reopening separately after signing CLA.


Introducing the $filter functionality

Hello,
Following #5, This is our simple implementation for the $filter in OData.

Made a few tweaks in #11 and merged. Will release in a sec. Thanks @hozan23 !

Hello @sergiimk
Thanks for that, next time you don't need to create a new PR, you can just push to my PR, it's fine :).


MCMP Prevent Nested Plan Reqs from linking to Parent Plan

Update 5/29/2019:
MCMP wants to ensure the Plan Requirements that descend from a given Program Plan can't be associated with a different Program Plan from its parent/grandparent(s).
Analysis
RE: MCMP ticket -- off the top of my head:

Create Program Plan (via the UI)
Create Program Plan Requirement (via the UI)
Select Program Plan for the requirement (via the UI) (Optional)
CODE: Since this is the first plan requirement, its Plan_Requirement__c field should be blank, so exit, there's nothing for us to enforce.
Now create a CHILD requirement from the first plan requirement. (via the UI)
This is a CHILD of the first Plan Requirement (its Plan_Requirement__c field is not blank)
5/21 Update: CODE: Since this is a CHILD of the first Plan Requirement, Program Plan must not be populated if the new setting is enabled.

Outdated:
Description:
Regardless of where a "Plan Requirement" falls (either parent requirement or a child requirement in a thread of requirements), at the end of the day should only roll up to ONE "Program Plan". This creates less confusion in the long-run and makes the use-case of the deep clone more valid. This is cleaner to handle architecturally and makes the Deep Clone feature more useful/efficient.
This work in this ticket should make sure an Admin cannot affiliate the same Plan Requirement record (ex: Biology 101a) to both the "Bachelors in Biology" program plan and the "Biomedical Engineering" program plan. Each program plan would have it's own. If they attempt to affiliate the same plan requirement with 2 different program plans, it would be nice if they received an error message along the lines of "You cannot affiliate the same plan requirement with 2 different Program Plans, would you like to clone this requirement?" (this latter part is a nice-to-have, not a must-have).
Acceptance Criteria:
1.) As an Admin you attempt to take an existing Plan Requirement and affiliate it with 2 (or more) different Program Plans. Should not be allowed, receive clean error message.
2.) As an Admin you attempt to create a new Plan Requirement and affiliate it with 2 (or more) Program Plans. Should not be allowed, receive clean error message.

**lurch: attach W-026118

Tracking W-026118

Included in beta release 1.79 (Beta 2)

Included in production release 1.79


Add support for MeshConfig.ProxyConfig.Trace.Sampling

When both PILOT_RANDOM_SAMPLING and MeshConfig trace sampling is used,
have the later override the environmental variable. Log accordingly.

@rshriram had asked for random sampling to be a part of the PR to add better tracing support in istio 1.6
My thoughts are to still support PILOT_RANDOM_SAMPLING, log when it is overridden (this may be too verbose) and in documentation mark PILOT_RANDOM_SAMPLING as deprecated in favor of using MeshConfig. Then in istio 1.7 we will remove support for PILOT_RANDOM_SAMPLING.

@jacob-delgado: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
39d0969f6b987322698cb484ffdee017bd30f8d0
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

How are you incorporating @howardjohn PR #23082 so that we use the correct ProxyConfig from node metadata?

Regarding my pr, I think the usage for tracing landed at the same time so I can send out a pr to make it use the correct config from meta.

Regarding my pr, I think the usage for tracing landed at the same time so I can send out a pr to make it use the correct config from meta.

I will fix this as part of my PR.

@jacob-delgado: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
0f49d1fd4c5c8d6841f027d34f9b9afc8052fce7
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jacob-delgado: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
0f49d1fd4c5c8d6841f027d34f9b9afc8052fce7
link
/test unit-tests_istio

integ-local-tests_istio
0f49d1fd4c5c8d6841f027d34f9b9afc8052fce7
link
/test integ-local-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn added support for https://github.com/istio/istio/pull/23081 with PR https://github.com/istio/istio/pull/23119

I will fix this as part of my PR.

Sorry didn't see this!

@jacob-delgado: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
98275d7962061780a94971e5038cd100ca3e66a7
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jacob-delgado: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
6081b097f61f10891f9dfcaee0223dfb74a01754
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jacob-delgado: PR needs rebase.

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

@jacob-delgado: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
6081b097f61f10891f9dfcaee0223dfb74a01754
link
/test lint_istio

release-test_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test release-test_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jacob-delgado: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
6081b097f61f10891f9dfcaee0223dfb74a01754
link
/test lint_istio

release-test_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test release-test_istio

unit-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jacob-delgado: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
6081b097f61f10891f9dfcaee0223dfb74a01754
link
/test lint_istio

release-test_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test release-test_istio

unit-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test unit-tests_istio

integ-multicluster-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-multicluster-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jacob-delgado: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
6081b097f61f10891f9dfcaee0223dfb74a01754
link
/test lint_istio

release-test_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test release-test_istio

unit-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test unit-tests_istio

integ-multicluster-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-distroless-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jacob-delgado: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
6081b097f61f10891f9dfcaee0223dfb74a01754
link
/test lint_istio

release-test_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test release-test_istio

unit-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test unit-tests_istio

integ-multicluster-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-distroless-k8s-tests_istio

integ-galley-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-galley-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jacob-delgado: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
6081b097f61f10891f9dfcaee0223dfb74a01754
link
/test lint_istio

release-test_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test release-test_istio

unit-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test unit-tests_istio

integ-multicluster-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-distroless-k8s-tests_istio

integ-galley-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-galley-k8s-tests_istio

integ-security-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-security-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jacob-delgado: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
6081b097f61f10891f9dfcaee0223dfb74a01754
link
/test lint_istio

release-test_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test release-test_istio

unit-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test unit-tests_istio

integ-multicluster-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-distroless-k8s-tests_istio

integ-galley-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-galley-k8s-tests_istio

integ-security-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jacob-delgado: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
6081b097f61f10891f9dfcaee0223dfb74a01754
link
/test lint_istio

release-test_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test release-test_istio

unit-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test unit-tests_istio

integ-multicluster-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-distroless-k8s-tests_istio

integ-galley-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-galley-k8s-tests_istio

integ-security-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-pilot-k8s-tests_istio

integ-conformance-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-conformance-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jacob-delgado: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
6081b097f61f10891f9dfcaee0223dfb74a01754
link
/test lint_istio

release-test_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test release-test_istio

unit-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test unit-tests_istio

integ-multicluster-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-distroless-k8s-tests_istio

integ-galley-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-galley-k8s-tests_istio

integ-security-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-pilot-k8s-tests_istio

integ-conformance-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-conformance-k8s-tests_istio

gencheck_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jacob-delgado: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test release-test_istio

unit-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test unit-tests_istio

integ-multicluster-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-distroless-k8s-tests_istio

integ-galley-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-galley-k8s-tests_istio

integ-security-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-pilot-k8s-tests_istio

integ-conformance-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-conformance-k8s-tests_istio

gencheck_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test gencheck_istio

lint_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jacob-delgado: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test release-test_istio

unit-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test unit-tests_istio

integ-multicluster-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-distroless-k8s-tests_istio

integ-galley-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-galley-k8s-tests_istio

integ-security-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-pilot-k8s-tests_istio

integ-conformance-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-conformance-k8s-tests_istio

gencheck_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test gencheck_istio

lint_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test lint_istio

integ-local-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-local-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jacob-delgado: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test release-test_istio

unit-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test unit-tests_istio

integ-multicluster-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-distroless-k8s-tests_istio

integ-galley-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-galley-k8s-tests_istio

integ-security-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-pilot-k8s-tests_istio

integ-conformance-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-conformance-k8s-tests_istio

gencheck_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test gencheck_istio

lint_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test lint_istio

integ-local-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-local-tests_istio

integ-telemetry-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jacob-delgado: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test release-test_istio

unit-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test unit-tests_istio

integ-multicluster-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-distroless-k8s-tests_istio

integ-galley-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-galley-k8s-tests_istio

integ-security-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-pilot-k8s-tests_istio

integ-conformance-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-conformance-k8s-tests_istio

gencheck_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test gencheck_istio

lint_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test lint_istio

integ-local-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-local-tests_istio

integ-telemetry-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-telemetry-k8s-tests_istio

integ-mixer-k8s-tests_istio
677e71f0812bae32c2fcc3413ef314fefe2e1a93
link
/test integ-mixer-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Independently release cost insights

Hey, I just made a Pull Request!

Bump the Cost Insights plugin to 0.5.1 independently. Includes two small bug fixes, for breakdown sorting as well as for the bar chart legend for unlabeled dataflow alerts

Releases
<EMAIL_ADDRESS>Patch Changes

64c9fd84c: fix breakdown sorting
Fix bar chart legend label bug for unlabeled dataflow alerts

:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)

[error] Vale.Spelling
Did you really mean 'dataflow'?

lol


[Task]: Add Shimmer EVM Support

We should add to the project ShimmerEVM support.
Until the EVM launches, we should work with a a testnet chain, provided in slack (should not be pushed)

[ ] Display the faucet tab or not based on if the selectedNetwork has faucet or not configured
[ ] Update encoding (new encoding only for shimmer evm, not for shimmer evm testnet)
[ ] Add final ShimmerEVM details when ready (blocked by release date)

Details about the new encoding:
ShimmerEVM (production) encoding change:
basically we changed the way we identify "sender contracts" on  L1 requests
how does firefly encode this right now?
I'm guessing at this time is a uint32 (4 bytes) as 0s, right?
now just 1 byte (as 0) is needed, that's it

a single 0 byte (means  no contract)
a single byte with value 1, followed by 4 bytes (hname) - (this is the same as it was before, just with the "kind" byte added as a prefix)
a single byte with value 2, followed by 20 bytes (EVM address)

Closed by https://github.com/iotaledger/evm-toolkit/pull/21


[javalin-4x][context] Handle invalid urlencoding in bodies

Bodies may exist but not contain valid form params for some requests, and we should handle trying to read params from those requests gracefully.
"backport" of https://github.com/javalin/javalin/pull/2245 for javalin 4x.

I think you probably want to target 5x @norrs 😄


Add table aws_health_affected_entity closes #1410

Integration test logs

Logs
Add passing integration test logs here

Example query results

Results
Add example SQL query results here (please include the input queries as well)

This PR is under review (but difficult to test since we don't have direct access to the API in our accounts).

Hi @joelcox22 based on your feedback, we have added  aws_health_affected_entity in this PR. It would be really appreciated if you could give it a try and share your experience with us. Thanks!

thanks @ParthaI! I'll be back from a holiday and will be able to take a look at assisting with testing this late next week 😄

@joelcox22 we are pushing this table to the hub for now, please let us know if you have any feedback on this PR in terms of invalid data format or others. You could always raise an issue in the event of failures or suggestions 👍 .
Thanks once again for volunteering to test this table 👍.


Move uptime-kuma to new folder

⚠ Please verify that this bug has NOT been raised before.

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

🛡 Security Policy

[X] I agree to have read this project Security Policy

📝 Describe your problem
I am trying to reorganize all my docker data into a common location to simplify management.  I originally ran uptime-kuma with the following:
sudo docker run -d --restart=always -p 3001:3001 -v uptime-kuma:/app/data --name uptime-kuma louislam/uptime-kuma:1
And as a result, the data lives in /var/lib/docker/volumes/uptime-kuma, and I want to move it to /opt/uptime-kuma.
To accomplish the above, I copied all files in /var/lib/docker/volumes/uptime-kuma to /opt/uptime-kuma and then stop and remove the container and then run the following:
sudo docker run -d --restart=always -p 3001:3001 -v /opt/uptime-kuma:/app/data --name uptime-kuma louislam/uptime-kuma:1
This should work in theory, but Uptime Kuma never recognizes the copied files and upon first run, it asks me to create a user versus bringing the old user over.
What am I doing wrong?
🐻 Uptime-Kuma Version
1.19.6
💻 Operating System and Arch
Debian Bullseye
🌐 Browser
Chrome
🐋 Docker Version
20.10.22
🟩 NodeJS Version
No response

Did you open a shell in the container to check if all the files are copied correctly?

So all this happens inside the shell.  I have tried a couple of options including:

Moving the original directory over (e.g. mv /var/lib/docker/volumes/uptime-kuma /opt)
Copy the files inside /var/lib/.... to /opt/uptime-kuma

I had the same problem in each case. It is perplexing to me as I am not sure why the files are not being recognized.

Did you check owership and permissions of the folder and files to be the same?

I am highly confused about this as it just does not make sense. It feels like I am doing something wrong, but I cannot for the life of me figure out what.  (FYI, I verified the appropriate updated path in Portainer and so it should be picking up the moved files.)  To answer other questions:

Have I checked permissions? Yes, original ownership is root and so is the new directory
Stop the container first... -> Correct. I do the following - docker stop, docker rm and then docker run with the new path
Copy the data folder --> I go to the original path (/var/lib/docker/volumes/uptime-kuma) and did a cp -RT this AM. Same problem.

I was poking around the sqllite database in the new location moments ago and everything looks fine.  I just cannot figure out why u-k is not using it. To the extent it matters, I have been playing around with the new u-k location to be /opt/uptime. I don't think that the name should matter.

2. Stop the container first... -> Correct. I do the following - docker stop, docker rm and then docker run with the new path

Not what I wrote.
As per what you have written so far it is understood that you copied the data folder while docker was running.
So again, please verify that you do/did the following steps:

Stop the container
Copy the data folder (including contents; so make sure you cp -R -p /folder/old/ /folder/new/
(-R = recursive, so includes all content in the folder, -p = preserve, and preserves permissions)
then restart the container with new path

Maybe it is helpful for you working with docker compose...
docker-compose.yml files are not just single line in shell, therefore better structured and less confusing.

My apologies for not being clear.  I did what you stated above in each test.  I did it again today with the same result.
You raise a good idea about docker-compse as I am familiar with that approach too and so tried that out this AM. It had exactly the same problem.  In fact, it would not even recognize the existing data even if I put in the full original path in the docker compose file. (e.g. - /var/lib/docker/volumes/uptime-kuma:/app/data
While I first thought that this might be user error, I am now wondering if there is a problem with how u-k interprets the volume path and whether it is hardcoded in the database or app somewhere.

As an update, I captured the logs from running Uptime-Kuma with the new director setting, and you can find it in Pastebin here.
One curiosity is line 18, where it says:
Data Dir: ./data
That path is curious because it matches neither the internal path from docker run (/app/data) or the external path (/var/lib/docker/volumes/).

I guess you was trapped by the volume directory structure, be careful of _data directory.
It should look like this:

That was 100% it.  Thank you!  I really appreciate your jumping in to help @louislam.


Mouse control with fixed camera and physics

Is it possible to drag a physics body around with mouse and a fixed camera?
These are my requirements and current setup, which is not working well:

super-hands (grabbable)
aframe-physics-system (cannon.js)
Mouse/touch as cursor (not gazed based)
Camera fixed without look/orbit controls (placed above movable object, looking down)
Dynamic body attached to static body with hinge constraint (y-axis)

This is the closest demo I've found, but it's not using a fixed camera facing down:
https://wmurphyrd.github.io/aframe-super-hands-component/examples/physics/index-mouse.html

Yeah the problem with that setup is using the movement of the camera to apply force to move the objects. You'd need to move the super-hands component onto a different (invisible) entity that is made to follow the mouse cursor around, or, if you can make it move a static body, use a setup like the non-physics mouse example and grabbable="usePhysics: never"


Scour inserts inappropriate  element when scouring Inkscape multi-line text.

When the  "group collapsing" option is unchecked, and the "create groups for similar attributes" is checked, Scour inserts a  element inside the  element when adjacent s share the same properties. This prevents the rendering of the  elements.
See https://bugs.launchpad.net/inkscape/+bug/1516538
Scour should either leave the s alone or if all s in a  element share the same properties, put the properties on the  element.

Imported from Launchpad using lp2gh.

date created: 2015-11-16T12:40:58Z
owner: tavmjong-free
the launchpad url was https://bugs.launchpad.net/bugs/1516607

(duplicate of #96)
Fixed in #98


Feature/color scheme

I made a little change to HTML file for styling purpose. I also developed CSS file to make project generally less bootstrapy.

Updated the HTML to fix the conflict - it was the h5 to h6 change that conflicted as I had changed the ID of that div.


建议打开软件后可选择自动进入歌曲播放界面（即专辑画报和歌词页）而非只能后太设置界面，打开软件即沉浸式播放很爽的，谢谢

仅仅提交一个建议。Submit just one proposal.
在你提交此建议前请注意：Please note before you submit this proposal:

详细阅读椒盐音乐帮助内容（应用设置-帮助）。Read more about the SaltPlayer help content (app Settings - Help).

反馈时候请注意：When giving feedback, please note:

尽量详细的描述。Be as detailed as possible.
不接收任何 UI 样式调整相关的反馈，出现此类 issue 会被关闭（如 “我不喜欢此设计” 、“我觉得这样设计更好” 、“还没原来好看” 等等类似反馈）。Do not receive any feedback on UI style changes, and the issue will be closed (" I don't like this design ", "I think this design is better", "it's not as good as the original", etc.).

建议内容 The proposals
<在此输入你的建议 Enter your suggestions here>

#382


"Iterate Through An Array With For Loop" not accepting valid assignment

Hi FCC Team,
This is a minor issue, but was brought up by a redditor asking for help with his code.
This is what's not accepted:
for (i = 0; i < myArr.length; i++)
{
total = total + myArr[i];
}
I double-checked the instructions, and didn't see it specifying that it be written as total += myArr[i]
Hope this relieves some frustration! :)

Yeah, the tests look for += explicitly.  We should allow that or total = total +.

My mistake. Should've thought of that. I'll fix this one.

This is already "fixed", but I've found just now that the test for declaring 'total' outside of the 'for' loop will still always fail unless an assignment to total (via the '+=' operator or just '=') is used within the 'for' loop. No problem if the user understands that an assignment should be done instead of, say, a function, but otherwise puts them on a wild goose chase for why 'total' isn't declared when it is. Strangely, once the operator has been used, the check seems to remain valid even if the operator is removed for testing, until the code is reset.

try this
var total = 0;  // here you declare the variable to 0, them the for loop.
for (var x = 0; x.myArr.lenght; x++){
total += myArr.push(x);
};

Hello forks, after struggling for few minutes,  I have manage to come up with a solution.
// Example
var ourArr = [ 9, 10, 11, 12];
var ourTotal = 0;
for (var i = 0; i < ourArr.length; i++) {
ourTotal += ourArr[i];
}
// Setup
// Only change code below this line
var myArr = [ 4, 6, 10];
var  total = 0;
for (var  i = 0; i < myArr.length; i++) {
total += myArr[i];
}


Added equivalence case and tests for String that is locale and case insensitive

Fix for issue #72.  Using Java Collator to resolve... Not sure if this is correct.

@c-schuler - Your use of Collator.getAvailableLocales() appears to be asking for locale sensitive behaviour, taking whatever's available.  Whereas if you specify a locale such as "US" (or better yet, some generic Unicode collation) then that should help ensure we are locale-INsensitive, meaning that every user gets the same behaviour.  We need to be locale-INsensitive or else any tests are non-portable.

I was going to simply use equalsIgnoreCase(), but ran across the following case while researching. If edge cases like that do not concern you, I will go with the simpler equalsIgnoreCase() route.

My leaning is to accept the simpler behavior with the possibility that case mappings could cause edge case behavior.


Move over to the sbt-circe-org plugin

Based on https://discord.com/channels/632277896739946517/877550996191084554/1075463626258915368.
In preparation of upgrading the Monocle dependency, first we want to start using the circe-org plugin. I'm not really sure what I'm doing here, but I tried to look at how circe-yaml and circe-fs2 uses the plugin, and how the corresponding build.sbt files looks: https://github.com/circe/circe-yaml/blob/main/build.sbt & https://github.com/circe/circe-fs2/blob/master/build.sbt.

@ingemaradahl Sorry for the delay, just got to getting this running ci quick.

superseded by #329, Thanks for laying the foundation.


⚠ Bofrost.lu has degraded performance

In 617b50e, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1546 ms

Resolved: Bofrost.lu performance has improved in a75d775.


update the command for creating the faucet container

The specified directory is wrong.

Thanks for the patch.  May I have a Signed-off-by for this patch?  See http://docs.openvswitch.org/en/latest/internals/contributing/submitting-patches/


[0.5pt] Add unit tests for all implemented methods.

The following options should be available:
List all music albums
List all genres (e.g 'Comedy', 'Thriller')
Add a music album

We have done it


SSTV mode robot 36

First thank you for your great work!!!
SSTV modes mt1/sc1 are taking a long time to transmit. Why not using Robot36 mode, it takes shorter time only 36 seconds and more efficiency.
Sorry for my bad English.

UV-K5's MCU (CPU) operates without X-tal, making precise time control
difficult.
Even with time control, the basic clock changes slightly, making
synchronization difficult.
When I have time, I will apply and test Robot36. If possible, I will upload
the experiment results as a video on YouTube.
(There are people who dislike uploading videos without results, so it will
probably be uploaded only when it is usable)
Ian KD8CEC
On Fri, Feb 9, 2024 at 1:36 PM cjinhub @.***> wrote:

First thank you for your great work!!!
SSTV modes mt1/sc1 are taking a long time to transmit. Why not using
Robot36 mode, it takes shorter time only 36 seconds and more efficiency.
Sorry for my bad English.
—
Reply to this email directly, view it on GitHub
https://github.com/phdlee/uvk5cec/issues/13, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE4DZPAWNMJ46KCPPRLNJY3YSWRVDAVCNFSM6AAAAABDA3TMIKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGEZDMNBVGQZDGNI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

祝你成功，龙年大吉！


This  project doesn't work

Unfortunately, this project is broken
This is just a warning to everyone who wants to play around with this PLUGIN
using this command
cfn submit --set-default
You can't  build the Lambda
So you can  build and deploy  two stack
CloudFormationManagedUploadInfrastructure
styra-opa-hook-role-stack
You can build and upload one  zip file to the  S3  (styra-opa-hook-{date}.zip)
But there is a missing step. to deploy lambda and connect that lambda  to the hook
So the effect is that after. hook activation  ALWAYS you will get an error message  during CF deployment that   it's impossible to connect to  your opa server-  hook  is not able to connect to lambda ( lambda doesn't exist)

Hi @donfirst!
And thanks for filing this issue. I'm aware of this issue from before, but unfortunately I haven't had the time to get around to it yet. Planning to set aside some time for this next week, and hopefully we can get things back to a working state then. Could you describe the steps you take and where exactly things break and how?
I'll make sure to keep you in the loop as I try to find out what's changed here since I worked on this the last time.

Hi @anderseknert
Wanted to say that you are doing an awesome job !!!
I have  found a couple of issues
I'm using Mac Sonoma 14..5  and Python 3.12.3

It would be good to put into  README that you have to update .rdpk-config
"language": "python{your_python_version}",
"runtime": "python{your_python_version}",
File validate.py in folder test -> line  109

should be
¯\(ツ)/¯

3)Following  instruction from
https://www.openpolicyagent.org/docs/latest/aws-cloudformation-hooks/
a)
git clone https://github.com/StyraInc/opa-aws-cloudformation-hook.git
cd opa-aws-cloudformation-hook
b)Change the file

c)cd hooks
cfn submit --set-default
c1)

d) So far so good :-)
e) Doing all exports
f)Activate the hook
Now I'm going to lambda -> no  function has been created
CFstack  hook is activated
Deploying any cf

Check lambda and there is no lambda

Have made some test
macOS Sonoma uses ZSH (Z shell)  as default .
For ZSH File validate.py in folder test -> line 109
should be
¯(ツ)/¯
for bash (linux)  validate.py works  as it should

@anderseknert
I  spent some time  to discover how that project work -  so now  I know .
You can  close that topic I managed everything to  work
If you. are interested I can participate  in that project - fix documentation and explain. how does it work
Let me know if you are interested in
Best Regards
Pete

That's great! Yes, I'd be very happy for any help I can get here, as it's been quite a while since I worked on this 😃


Types are incorrect for useLocalStorage

Describe the bug
The setter for useLocalStorage has incorrect typing. Instead of itself being a function which takes in a parameter of generic type T, it is a function which takes in a function with a parameter of type T.
I believe this bug was introduced here:
https://github.com/beautifulinteractions/beautiful-react-hooks/commit/9a3804568f977d6ffed6e98e75ba1242773146c5
(as was mentioned in and released in 0.33.4 https://github.com/beautifulinteractions/beautiful-react-hooks/blob/14070e2c41709dbd974493895928c39d60b4c337/CHANGELOG.md#0334---2021-05-09)
To Reproduce
Steps to reproduce the behavior:

Use Typescript

Use the local storage hoook:
const [notificationCount, setNotificationCount] = useLocalStorage<number>('foo', 0);

Attempt to invoke the setter:
setNotificationCount(1);

Notice the error:
Argument of type 'number' is not assignable to parameter of type '(arg: number) => unknown'.

Expected behavior
The setter works as expected, allowing it to take in an argument of the generic type, rather than it expecting a function which takes in that type.

Thanks, and congrats on the TS rewrite! Seems like a solid move!


Add Windows HyperV container mode

Signed-off-by: Dan Ardelean<EMAIL_ADDRESS>Implements 519

Code changes look fine to me.
I was expecting we would need to turn on nested_virtualization in the cirrus configuration to get this to work (https://github.com/containerd/nerdctl/pull/795#issuecomment-1377588311) as well as bump containerd version to 1.7+ (https://github.com/containerd/nerdctl/blob/27b1fef2cc834c55ac02540c6d7cc2635f80a07c/.cirrus.yml#L33) as hyper-v support was only recently enabled in containerd.
@dcantah could you take a look at the test to see if that is the right check?

as well as bump containerd version to 1.7+ (

We should be fine without 1.7 as we're manually toggling the hyper-v field. You'd need 1.7 for Hyper-V through CRI however 😬

Cc @kevpar

I had a merge conflict with #1880 and I had to rebase.

lgtm


Compiled/reflection bindings not consistent with RelativeSource=Self

Describe the bug
When RelativeSource=Self is used in a binding on an element, the resulting source should be the element, as it is in WPF.  This works fine in ReflectionBinding, however CompiledBinding returns the data context instead.
I retested this in a recent PR build for the data binding refactor (https://github.com/AvaloniaUI/Avalonia/pull/13970), but the bug still seems to be present.
To Reproduce
Use this XAML:
<StackPanel x:DataType="x:String" DataContext="Foo">
	<Button x:Name="button" DataContext="Bar">Test</Button>
	<TextBlock Text="{CompiledBinding ElementName=button}" />
	<TextBlock Text="{ReflectionBinding ElementName=button}" />
	<TextBlock Text="{CompiledBinding RelativeSource={RelativeSource Self}}" />
	<TextBlock Text="{ReflectionBinding RelativeSource={RelativeSource Self}}" />
</StackPanel>

The TextBlock controls currently output:
Foo
Avalonia.Controls.Button
Foo
Avalonia.Controls.TextBlock

Expected behavior
The TextBlock controls should output this instead:
Avalonia.Controls.Button
Avalonia.Controls.Button
Avalonia.Controls.TextBlock
Avalonia.Controls.TextBlock

Note that this is very similar to:

https://github.com/AvaloniaUI/Avalonia/discussions/14353

I tried {Binding RelativeSource={RelativeSource Self}} and that did not work either. Decided not to open an issue for it.
@billhenn
Note that a work around is to use the Avalonia syntax in the attached discussion.

@robloo we originally used Binding syntax (it's in a compiled binding enabled project) and noticed the issue.  We ended up flipping that to ReflectionBinding syntax to work around the issue for now.  But as mentioned in the other issue, reflection and compiled should have the same results, so we wanted to report it before the all the great data binding enhancements went out in v11.1.

we originally used Binding syntax (it's in a compiled binding enabled project)

Yes, I should have been clear on my end as well. Binding above is in a compiled binding enabled project. It's ported code from WinUI and was original reflection binding. When everything was switched over to compiled bindings at once (with the project setting) an error was noticed here. Probably the same as how you found this.
Agree that reflection and compiled should have the same results. Since there was such an easy work-around I didn't spend the time to create an issue myself. Just wanted to note the case I saw this here though.

Thanks @grokys, this PR update appears to fix the problem.


Error on install

apm install eslint
No available version compatible with the installed Atom version: 1.7.4

Same problem for me too

@iancmyers

I'm getting no available version compatible with Atom version: 1.8.0

I believe the repository is abandoned. Maybe someone should create a new project.

@carloschneider yes, I think it too; and if you check the last commit, it was done on 31 Jul 2014, so... we should look for another linter tool

FYI.  The new package is linter-eslint.


Should base block rf_freq be 0 by definition

It feels like in the line
https://github.com/INFN-MRI/pulserver/blob/9cb2bd8e6fe267d91706a92ac9d0bdf5f783135f/src/pulserver/_core/_sequence.py#L244
"+= rf_freq" should be "= rf_freq", i.e., the base block should always have rf_freq = 0 by definition so that the designer doesn't have to keep track of frequency change w.r.t. the base block. It could be confusing as is?

Sorry, I did not receive any notification of the issues - that makes sense, I'll fix it, thanks!


During synthesis, the addition of optimization passes such as opt_clean and opt_reduce after ABC optimization has resulted in errors in register assignment.

Version
Yosys 0.30+48
On which OS did this happen?
Linux
Reproduction Steps
I have encountered an inconsistency issue while using Yosys. During synthesis, we did not use the default synthesis flow of Yosys. After ABC optimization, we applied additional optimization passes such as opt_clean and opt_reduce. The specific synthesis flow we followed is as follows:
read_verilog rtl.v
hierarchy
proc; opt_merge; opt_clean; opt_clean; opt_clean; opt_reduce; opt_expr;
memory; opt_clean; opt_clean; opt_reduce;
techmap; opt_clean; opt_clean; opt_reduce;
abc; opt_demorgan; opt_clean; opt_merge; opt_clean; opt_clean; opt_clean; opt_reduce; opt_expr; opt_lut_ins; opt_expr; opt_expr; opt_clean; opt_dff; opt_lut; opt_reduce; opt_clean; opt_share;
write_verilog syn_yosys.v
We aimed to optimize the logical structure by adding these passes, but these modifications should not affect the code consistency. Using the provided design file (rtl.v), we performed synthesis separately with Yosys's default synthesis flow and our modified synthesis flow with additional passes. Subsequently, we conducted simulation verification using the Iverilog simulator. During simulation, we observed inconsistencies in the output signals (at 0sec). This inconsistency arose from erroneous register assignments in module5 of the design file (starting from line 50 in the attached rtl.v file). The waveform comparison chart is presented below:

Figure 1：Default Synthesis（0sec）

Figure 2：Modified Synthesis（0sec）
Please find attached the code of my program.
rtl.txt
yosys_testbench.txt
Thank you in advance for your attention to this matter.
I look forward to hearing from you regarding this issue.
Expected Behavior
We aimed to optimize the logical structure by adding some passes, but these modifications should not affect the code consistency.
Actual Behavior
However, in reality, it did exhibit inconsistent behavior during simulation verification.

Should the discrepancy be visible in the print output from running of the testbench (since it is printing out the y signal)? If so, I am unable to reproduce.
Once I ran the testbench with unmodified rtl.txt, and once on syn_yosys.v that resulted from your synthesis script. In both cases the first line of output is:
000000000000000000000000000000000000010000000100000000000000000000000000000000000000000000000000000000000000

which, if I am not miscounting zeroes, is the same as you get on Figure 1.
What version of Icarus Verilog are you testing this with? Mine is 11.0. Yosys I tested with both versions 0.23 and 0.30+48.

Thank you for your response.

The Icarus Verilog version I am using is Icarus Verilog version 13.0 (devel) (s20221226-221-g272771d18).
Below are the synthesis commands used for the two synthesis processes:
1、Default synthesis process using yosys：
read_verilog rtl.v
synth
write_verilog syn_yosys.v
2、After ABC optimization, we applied additional optimization passes such as opt_clean and opt_reduce. The specific synthesis flow we followed is as follows:
read_verilog rtl.v
hierarchy
proc; opt_merge; opt_clean; opt_clean; opt_clean; opt_reduce; opt_expr;
memory; opt_clean; opt_clean; opt_reduce;
techmap; opt_clean; opt_clean; opt_reduce;
abc; opt_demorgan; opt_clean; opt_merge; opt_clean; opt_clean; opt_clean; opt_reduce; opt_expr; opt_lut_ins; opt_expr; opt_expr; opt_clean; opt_dff; opt_lut; opt_reduce; opt_clean; opt_share;
write_verilog  new_syn_yosys.v
We aimed to optimize the logical structure by adding these passes, but these modifications should not affect the code consistency.
However, the results show that there is inconsistency in the simulation of syn_vivado.v and new_syn_vivado.v when simulated separately using Icarus Verilog.
Default synthesis process ，the first line of output is:
000000000000000000000000000000000000010000000100000000000000000000000000000000000000000000000000000000000000
additional optimization passes in the Synthesis process， the first line of output is:
000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000
Inconsistency occurred at bit 38.
I think this is due to an abnormal behavior caused by some of the optimization passes, resulting in register assignment errors.
I would appreciate your assistance in identifying the root cause of the issue. Thank you very much for your help.

So I was able to reproduce after all once I paired Yosys with the right ABC version (1de4eaf).

This seems to happen on current master with ABC bb64142 too

So the culprit is in opt_share not distinguishing between the inputs of $_ANDNOT_ cells when considering if a mux can be moved in front. So it transforms

into

which of course is wrong.


How to accelerate tensor transferring from host to device (GPU) in TF 2.x?

Describe the current behavior
Hi, I want to train my DNN model with TF. And now the input is from tf.data.Dataset.from_tensor_slices, which will prefetch the numpy value into TF tensors.
Because the training is on GPU, therefore tensor transferring from CPU to GPU is triggerd automatically, which results in bad performance in my training process.
Specifically, one iteration is about 205 ms, while data transfering from CPU to GPU will spend 136 ms.

Describe the expected behavior
Is there any way to change the memory used by tf.data.Dataset to CPU pinned memory rather than pageable? So that tensor transferring from CPU to GPU will be much faster.
Or any other methods I can try to accelerate data reading from numpy to TF tensors on GPU?

Have you already read this to optimize your data pipeline for GPU: https://www.tensorflow.org/guide/data_performance?

Have you already read this to optimize your data pipeline for GPU: https://www.tensorflow.org/guide/data_performance?

Yes, I did.
Currently, my data pipeline is: reading data from numpy values, then prefetch it. No other operations (such as map, interleave).

If you want to control the prefect to GPU device you could try prefetch_to_device. Check if it is not currently broken for your use case https://github.com/tensorflow/tensorflow/issues/43905

If you want to control the prefect to GPU device you could try prefetch_to_device. Check if it is not currently broken for your use case #43905

Thanks for the link.
I changed the last line of my dataset to dataset = dataset.apply(tf.data.experimental.prefetch_to_device(device='/gpu:0', buffer_size=16)), and iteration elapsed time is less than before (dataset.prefetch(buffer_size=16)).
And now, the timeline is:

There are still memcyp H2D, although it is faster than before.
Seems like prefetch does not work?

I think that you can comment after https://github.com/tensorflow/tensorflow/issues/43905#issuecomment-720453284

I think we can close this as It Is tracked in the other ticket.


Clarify "status" on attendee tables

There's a column for status and there are a few different options, but it's not immediately clear what the options are or what they mean. We should add some help text or find another way to clarify it.

I'm closing this since attendee tables no longer have a "status" column.


[Request] Function that can get the DFS info behind a DFS UNC path

Hi
I see that you added support for enumerating shadow copies, that is pretty sweet. This allows a programmatic version of the "Previous Versions" tab.
I was wondering if maybe you can add it so there is a programmatic version of the DFS tab too? DFS shares in Windows allow 1 or more physical shares to back it, (screenshot example I found is not mine, but to illustrate the point)

I found a sample here that wraps around the win32 function, and used it, but it would be pretty sweet to have this in this module too. https://social.technet.microsoft.com/Forums/en-US/26690c4b-fe84-4ae2-b06d-ecc01648d92c/get-dfs-server-name-and-local-path-from-unc-path?forum=winserverfiles

I very much understand your wish to get this info. But this is more a client computer thing and FileShareUtils is more server / administration oriented.
On my job we actually have the same issue, that we like to collect Information about active DFS target for mapped drives on client computers. The targets should change by AD site, but it seams they sometimes don't change when the client changes the site (changing from LAN to VPN or back) without a reboot (or logoff / logon). We also would like that with the detected site (nltest /dsgetsite) Also the functions of the three buttons should be available .
If I dig into this, I will probably create a new repo. Goal is to have a script including all function that could be used on a Windows without any installation of a PS Module, Feature or application.

Sensible, although a good admin case for this could be: sometimes users report that a file (Especially Office files) on a DFSN share might be locked or something, and rather guess what server their workstation selected or checking on each one, enumerating the possible shares, and then Get-NetOpenFiles against all of the members is quicker.
(In theory I guess the dfsn module would also work too I guess...)


tfa.text.crf_log_likelihood is not compatible with tf2.0-beta1

When implement CRF with tf2.0-beta1, got AttributeError: module 'tensorflow' has no attribute 'get_variable' when using tfa.text.crf_log_likelihood.
`AttributeError: in converted code:
relative to /home/xingya:
resume_parser/resume_parser/training/train_ner_bp.py:329 train_step  *
    log_likelihood, _ = tfa.text.crf_log_likelihood(
.conda/envs/tf2/lib/python3.6/site-packages/tensorflow_addons/text/crf.py:191 crf_log_likelihood  *
    transition_params = tf.get_variable("transitions",
.conda/envs/tf2/lib/python3.6/site-packages/tensorflow/python/autograph/impl/api.py:329 converted_call
    f = getattr(owner, f)

AttributeError: module 'tensorflow' has no attribute 'get_variable'`

Accordding to the example in the official migration_guide, It should be tf.Variable.

Thanks for reporting @xuxingya! Yeah get_variable is v1 behavior. Would you like to submit a bug fix PR?


ELBv2 DescribeTargetHealth returns correct response for stopped instance

When an EC2 instance is registered as a target in an ELBv2 target group, and it is stopped, the following should be its health status:
{
     "State": "unused",
     "Reason": "Target.InvalidState",
     "Description": "Target is in the stopped state"
}

Coverage increased (+0.07%) to 93.099% when pulling<PHONE_NUMBER>e10ecf907382d5b5b2e167536336ad on acsbendi:elbv2-stopped-instance-target into 6bc07360a1b44b43bc7d22005559168299d2c1da on spulec:master.

thank you!


Open Search Editor does not always select all existing text in the input field

VSCode Version: 1.48.0
OS Version: macOS 10.15.6

Steps to Reproduce:

Open a search editor and perform a search
Switch to another tab
Run "Open Search Editor" (without selecting any text in an editor) and sometimes all of the existing input text will be re-selected, but not always. I do this many times per day, and often it is selected, but sometimes it isn't. I can't figure out what the exact steps are to reproduce it, as it seems random to me.

Sorry @JacksonKearl but I'm tagging you on this one too ;)

Does this issue occur when all extensions are disabled?: Yes/No

To verify:

Have a search editor with some query in your workspace (open but not visible)
In some other editor, run "Open Search Editor" without any text selected
Expect the search editor to become visible and the query field to be selected and focused.
Try focusing a variety of different elements in search editor (focus results editor, search query inputs, etc.), and repeat to verify that no matter where focus started, it is set to the query input box on running "Open Search Editor" with no selected text, and that the text in the box is selected.

@JacksonKearl sounds exactly as I was imagining! 🚀

@JacksonKearl I was really hoping this would come in 1.48.1 but will I have to wait until 1.49?


Toggling to 'Use an existing persistent volume' option is not working on the 'Create Persistent volume' screen.

Description of the bug
Toggling to 'Use an existing persistent volume' option is not working on the 'Create Persistent volume' screen.
Steps to reproduce

Set up an HA with 3 nodes.
Go to the local cluster explorer.
Deploy longhorn app.
Create a stateful set.
Select the 'Create Persistent volume claim' option.

Select 'Use an existing persistent volume' option.

Result
The volume persistent claim field doesn't get highlighted.

Environment Info
The dashboard version - ec04f78
The setup info - HA setup with k3s v1.1.3

Verified with the latest dashboard - master-head ec04f78, the PVC created by using existing PV stuck in pending state.
There are below issues on selecting 'Use an existing PV'

The capacity doesn't get disabled which is not required now. With capacity 0, the form doesn't get saved.
The 'Persistent field' displays all PVs whereas it should show only Avaialable PVs.
The PVC created on giving some random capacity and selecting an Available PV. PVC stuck in pending state as it has storageclass set to longhorn. The storageclass should be set to "" (empty).

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  creationTimestamp: "2020-09-29T23:25:26Z"
  finalizers:
  - kubernetes.io/pvc-protection
  name: pvc-test-volume-deploy-3
  namespace: default
spec:
  accessModes:
  - ReadWriteOnce
  resources:
    requests:
      storage: "2"
  storageClassName: longhorn
  volumeMode: Filesystem
  volumeName: pv-volume-test-3

Discussed with @mantis-toboggan-md
Ignore the 3rd point from https://github.com/rancher/dashboard/issues/1460#issuecomment-701054802, the setting of storageclass is working fine. The PVC is setting StorageClass with the default storage class of the cluster.

Verified with latest dashboard master head, the deployment works fine but we have issue with statefulset.
The toggling is working for both statefulset and deployment but the below scenario is failing.
Create a stateful set by selecting storage, stateful set fails to attach volume as it adds volumeClaimTemplate  in the YAML.
Note:
Same is working fine with deployment.

Verified with the dashboard master-head 87e7cdf
Validation - Pass
Validated the below scenarios and everything worked perfectly!

Stateful set with 'existing PVC' option.
Stateful set with 'creating PVC' option using storage class.
Stateful set with 'creating PVC' option using existing PV.
Stateful set with 'VolumeClaimtemplate'
Deployment with 'existing PVC' option.
Deployment with 'creating PVC' option using storage class.
Deployment with 'creating PVC' option using existing PV.