The typescript types don't seem to be working correctly

This will take some debugging, but it seems like there was a regression with the TS types at some point.

Currently the equality function is typed as:
equality?: (pastState: TState, currentState: TState) => boolean;

However, I think it should instead be typed as
equality?: (pastState: PartialTState, currentState: PartialTState) => boolean;

Since pastState and currentState are always retrieved with the partialized get() like here:
// temporal.ts
const currentState = options?.partialize?.(userGet()) || userGet();

And partialize is typed like:
partialize?: (state: TState) => PartialTState;

When not using partialize, PartialTState will be identical to TState, so this should still be accurate even when users don't use partialize.
I also think it may(?) be helpful to include an explicit example in the documentation of typing when using partialize re useTemporalStore -- specifically that the TemporalState's generic should be PartialTState and not TState when using partialize:
export const useTemporalStore = <T,>(
  selector: (state: TemporalState<PartialTState>) => T,
  equality?: (a: T, b: T) => boolean,
) => useStoreWithEqualityFn(usePageEditorStore.temporal, selector, equality

I don't know if this is the source of the typing issues you are referring to, or if there may be others. But if helpful, I'd be happy to make a PR with these changes. Thank you!

Hey @pstrassmann, thank you for the detailed write-up! I think this is related to the type issues I was seeing on your recent code sandbox.
Would you be willing to make a PR? I would be happy to give a review.

I tested this locally, and I think the only update that needs to be made is in types.ts change which you suggested! Having the docs updated to reflect how to use the hook would be fantastic. If you'd like, you could also make a PR to include the useTemporalStore hook. Thanks!

Fixed in v2.0.3


ServiceWorker: Use networkFirst caching strategy for samples & AMP runtime

...to avoid problems like this.

FYI @kmh287 ran into this today with version skew on his cached version of amp-selector.


RetrievableTask implementation of Void as viable alternative to NonRetrievableTask

Is your feature request related to a problem? Please describe.
There should be RetrievableTask support for the Void class type in order to make RetrievableTasks.java essentially a non-retrievable task.
Describe the solution you'd like
This could be further expanded by removing the seperation between Retrievable and NonRetrievableTasks; Tasks can simple have an abstract execute() method which returns T - a attribute which is explicitly provided at compile-time. If a user does not want to return back a value, they can supply the Void type instead of a proper concrete class.
Note that this implies that the execute() method would be the blocking method, instead of the getVal() method. The getVal() method would be eliminated.
Describe alternatives you've considered
RetrievableTasks and NonRetrievableTasks are the current solution.
Additional context
This could either be done via have two paths to creating Retrievable and NonRetrievableTasks.

Users can simply use a RetrievableTasks (or some variation of it created specifically for this... RetrievableTask could be further abstracted) for both returning and on-returning concurrent operations.
Users can have both ^ and the current setup of RetrievableTasks and NonRetrievableTasks. The drawback with this approach is that this could create ambiguity between which is the "correct" approach for the library.

Ticket Status
This ticket's status has been updated to: ACTIVE
Remarks
Active development has commenced in branches "issue-2" and "issue-15"

Development in issue-2 has made major improvements. There are now two types of RetrievableTasks:

ObjectBlockingRetrievableTask
MethodBlockingRetrievableTasks
In addition, the "obj" has been set to private, and now the only way to set its value is via a setVal() method which has been mandated (via the abstract modifier).

Development is now shifting towards writing the unit and functional tests necessary before this can be rolled out into a development release.


[Service List] Added filter functionality

This pr adds the filter by the ownership to the service list component.
More can be found here:- https://web-components-beta.vercel.app/docs/components/service-list

Also added manage permission component in this pr.


Add New Metadata for Existing Unit Set Aside Accounts and Transactions

Existing Unit Set Aside accounts are being added for CSOSG3 states with Indian Country.
Changes for this (made via https://camddevelopment.atlassian.net/browse/CG-293) include the addition of a new account type code (SESARES - Existing Unit Set Aside Reserve Account) and a new transaction type code (EUSAALL - Existing Unit Set Aside Allocation).
These changes will be deployed on CAMDBSP by early April.
Updates for the cloud.gov PG databases will need to be made at the same time.

MERGE INTO CAMDMD.ACCOUNT_TYPE_CODE A
         USING (SELECT 'SESARES' AS ACCOUNT_TYPE_CD,
                       'RESERVE' AS ACCOUNT_TYPE_GROUP_CD,
                       'Existing Unit Set Aside Reserve Account'
                           AS ACCOUNT_TYPE_DESCRIPTION
                  FROM DUAL) B
            ON (A.ACCOUNT_TYPE_CD = B.ACCOUNT_TYPE_CD)
    WHEN NOT MATCHED
    THEN
        INSERT     (ACCOUNT_TYPE_CD,
                    ACCOUNT_TYPE_GROUP_CD,
                    ACCOUNT_TYPE_DESCRIPTION)
            VALUES (
                       B.ACCOUNT_TYPE_CD,
                       B.ACCOUNT_TYPE_GROUP_CD,
                       B.ACCOUNT_TYPE_DESCRIPTION)
    WHEN MATCHED
    THEN
        UPDATE SET
            A.ACCOUNT_TYPE_GROUP_CD = B.ACCOUNT_TYPE_GROUP_CD,
            A.ACCOUNT_TYPE_DESCRIPTION = B.ACCOUNT_TYPE_DESCRIPTION;

MERGE INTO CAMDMD.TRANSACTION_TYPE_CODE A
         USING (SELECT 'EUSAALL' AS TRANS_TYPE_CD,
                       'Existing Unit Set Aside Allocation'
                           AS TRANS_TYPE_DESCRIPTION,
                       1         AS ALLOCATION_IND
                  FROM DUAL) B
            ON (A.TRANS_TYPE_CD = B.TRANS_TYPE_CD)
    WHEN NOT MATCHED
    THEN
        INSERT     (TRANS_TYPE_CD, TRANS_TYPE_DESCRIPTION, ALLOCATION_IND)
            VALUES (
                       B.TRANS_TYPE_CD,
                       B.TRANS_TYPE_DESCRIPTION,
                       B.ALLOCATION_IND)
    WHEN MATCHED
    THEN
        UPDATE SET
            A.TRANS_TYPE_DESCRIPTION = B.TRANS_TYPE_DESCRIPTION,
            A.ALLOCATION_IND = B.ALLOCATION_IND;

New metadata has been added on dev, test, and staging.   It will be added to prod on Friday 5/9 after the associated CAMDBSP migration is completed.


1.x Wrapping RemoteRegionFetch in TimedSupervisorTask

Wrap around the TimedSupervisorTask for better reliability.
The remoteRegionFetchExecutor can have a max of 2 concurrent threads executing a remote region fetch.

NetflixOSS » eureka » eureka-pull-requests #150 SUCCESS
This pull request looks good

Looks good.

NetflixOSS » eureka » eureka-pull-requests #151 SUCCESS
This pull request looks good


ICA is still getting poor recognition accuracy

I don't know if the bug has resurfaced or if it was never fixed, but ICA still tends to classify images under s10 with the ORL dataset. An example run:
$ ./face-rec --train train_images/ --test test_images/ --ica --ica_num_ic=50 --loglevel=2
Hyperparameters
PCA
  n1                            -1
LDA
  n1                            -1
  n2                            -1
ICA
  num_ic                        50
  max_iterations              1000
  epsilon                 0.000100
kNN
  k                              1

Training
  PCA
    compute surrogate of covariance matrix L
    compute eigenvectors of L
    compute PCA projection matrix
  ICA
    subtract mean from input matrix
    compute principal components of input matrix
    compute whitening matrix and whitened input matrix
    compute mixing matrix
    compute ICA projection matrix
Recognition
  ICA
    s10_2.pgm  -> s10
    s10_4.pgm  -> s10
    s10_5.pgm  -> s10
    s11_2.pgm  -> s10  (!)
    s11_4.pgm  -> s10  (!)
    s11_5.pgm  -> s10  (!)
    s12_2.pgm  -> s12
    s12_4.pgm  -> s10  (!)
    s12_5.pgm  -> s12
    s13_2.pgm  -> s10  (!)
    s13_4.pgm  -> s10  (!)
    s13_5.pgm  -> s10  (!)
    s14_2.pgm  -> s10  (!)
    s14_4.pgm  -> s10  (!)
    s14_5.pgm  -> s10  (!)
    s15_2.pgm  -> s10  (!)
    s15_4.pgm  -> s10  (!)
    s15_5.pgm  -> s10  (!)
    s16_2.pgm  -> s10  (!)
    s16_4.pgm  -> s10  (!)
    s16_5.pgm  -> s10  (!)
    s17_2.pgm  -> s12  (!)
    s17_4.pgm  -> s10  (!)
    s17_5.pgm  -> s1   (!)
    s18_2.pgm  -> s10  (!)
    s18_4.pgm  -> s10  (!)
    s18_5.pgm  -> s10  (!)
    s19_2.pgm  -> s12  (!)
    s19_4.pgm  -> s10  (!)
    s19_5.pgm  -> s10  (!)
    s1_2.pgm   -> s10  (!)
    s1_4.pgm   -> s10  (!)
    s1_5.pgm   -> s10  (!)
    s20_2.pgm  -> s10  (!)
    s20_4.pgm  -> s10  (!)
    s20_5.pgm  -> s10  (!)
    s21_2.pgm  -> s10  (!)
    s21_4.pgm  -> s10  (!)
    s21_5.pgm  -> s10  (!)
    s22_2.pgm  -> s10  (!)
    s22_4.pgm  -> s10  (!)
    s22_5.pgm  -> s10  (!)
    s23_2.pgm  -> s10  (!)
    s23_4.pgm  -> s10  (!)
    s23_5.pgm  -> s10  (!)
    s24_2.pgm  -> s10  (!)
    s24_4.pgm  -> s10  (!)
    s24_5.pgm  -> s10  (!)
    s25_2.pgm  -> s10  (!)
    s25_4.pgm  -> s12  (!)
    s25_5.pgm  -> s12  (!)
    s26_2.pgm  -> s10  (!)
    s26_4.pgm  -> s12  (!)
    s26_5.pgm  -> s12  (!)
    s27_2.pgm  -> s12  (!)
    s27_4.pgm  -> s12  (!)
    s27_5.pgm  -> s12  (!)
    s28_2.pgm  -> s10  (!)
    s28_4.pgm  -> s10  (!)
    s28_5.pgm  -> s10  (!)
    s29_2.pgm  -> s10  (!)
    s29_4.pgm  -> s10  (!)
    s29_5.pgm  -> s10  (!)
    s2_2.pgm   -> s10  (!)
    s2_4.pgm   -> s10  (!)
    s2_5.pgm   -> s2
    s30_2.pgm  -> s10  (!)
    s30_4.pgm  -> s10  (!)
    s30_5.pgm  -> s10  (!)
    s31_2.pgm  -> s10  (!)
    s31_4.pgm  -> s10  (!)
    s31_5.pgm  -> s10  (!)
    s32_2.pgm  -> s10  (!)
    s32_4.pgm  -> s10  (!)
    s32_5.pgm  -> s10  (!)
    s33_2.pgm  -> s10  (!)
    s33_4.pgm  -> s10  (!)
    s33_5.pgm  -> s10  (!)
    s34_2.pgm  -> s10  (!)
    s34_4.pgm  -> s10  (!)
    s34_5.pgm  -> s10  (!)
    s35_2.pgm  -> s12  (!)
    s35_4.pgm  -> s10  (!)
    s35_5.pgm  -> s10  (!)
    s36_2.pgm  -> s10  (!)
    s36_4.pgm  -> s10  (!)
    s36_5.pgm  -> s10  (!)
    s37_2.pgm  -> s10  (!)
    s37_4.pgm  -> s10  (!)
    s37_5.pgm  -> s10  (!)
    s38_2.pgm  -> s10  (!)
    s38_4.pgm  -> s10  (!)
    s38_5.pgm  -> s10  (!)
    s39_2.pgm  -> s10  (!)
    s39_4.pgm  -> s10  (!)
    s39_5.pgm  -> s10  (!)
    s3_2.pgm   -> s10  (!)
    s3_4.pgm   -> s12  (!)
    s3_5.pgm   -> s12  (!)
    s40_2.pgm  -> s10  (!)
    s40_4.pgm  -> s12  (!)
    s40_5.pgm  -> s10  (!)
    s4_2.pgm   -> s10  (!)
    s4_4.pgm   -> s10  (!)
    s4_5.pgm   -> s12  (!)
    s5_2.pgm   -> s10  (!)
    s5_4.pgm   -> s10  (!)
    s5_5.pgm   -> s10  (!)
    s6_2.pgm   -> s12  (!)
    s6_4.pgm   -> s10  (!)
    s6_5.pgm   -> s10  (!)
    s7_2.pgm   -> s10  (!)
    s7_4.pgm   -> s10  (!)
    s7_5.pgm   -> s12  (!)
    s8_2.pgm   -> s10  (!)
    s8_4.pgm   -> s12  (!)
    s8_5.pgm   -> s10  (!)
    s9_2.pgm   -> s10  (!)
    s9_4.pgm   -> s10  (!)
    s9_5.pgm   -> s10  (!)
    6 / 120 matched, 5.00%

ICA seems to be working properly during training, it produces similar matrices as the MATLAB code. I'm going to investigate db_recognize and the kNN classifier.

When I use the L2 distance for ICA I get similar recognition accuracy to the MATLAB code, which is good. However, I have found a bug with how kNN sorts neighbors by distance when using COS distance, so I will fix this first and then compare the distance functions for ICA.

The problem with the COS distance was actually with the kNN classifier; when comparing neighbors it would take the difference in distances and cast it to an integer, which means that differences between -1 and 1 would be rounded to 0. Since the COS distance returned values between -1 and 1, this case happened a lot, which caused the COS distance to yield poor results for all of the algorithms. I changed kNN to compare floating point values properly, and I also changed the COS distance to range from 0 to 2 so that it's more like a "distance".
At this point it seems that the COS distance might give comparable results to L2 for all three algorithms (at least for easy cases), so we'll definitely want to run some experiments that compare the distance functions across each algorithm.


Additional Data in the Tooltip

My calendar only takes in four values (0,1,2,3). The four values correspond to days in my local school calendar year (0 - Regular Days, 1 - Holidays, 2 - Teacher Days, 3 - School Meeting) I would like the tooltip to label them more discretely (i.e. the type of Holiday or the type of School Meeting). I've looked through 'subDomainTitleFormat' but can't seem to find a solution. Is it possible to represent data other than date and value?
Hopefully I'm being clear enough. Here are a few examples though of my ideal tooltip:

Christmas, December 25, 2015
New Teacher Orientation, May 26, 2015

Thanks!

I created a pull request that allows for this functionality #169

You can.
subDomainTitleFormat expects a string with placeholders which is then executed against overloaded String.propotype.format().
If you hack this and pass subDomainTitleFormat: {format: function(params){}} you can do whatever you want in the custom function.

#169 merge into V4 branch


cannot hide elevation of the appbar

I need a consistent gradient color as a whole, but I can't hide the elevation of the appbar.
  @override
  Widget build(BuildContext context) {

    Widget regionalSelectionContainer = Container(
      decoration: BoxDecoration(
          gradient: LinearGradient(colors: [
            Color(0xff1AB99D),
            Color(0xff2E2888)
          ])
        )
      );

    return Scaffold(
      backgroundColor: Color(0xfff2f1f8),
      appBar: GradientAppBar(
        gradientStart: Color(0xff1AB99D),
        gradientEnd: Color(0xff2E2888),
        elevation: 0, // -----------invalid------------
        title: Text('Regional Selection', style: TextStyle(fontSize: 14)),
        centerTitle: true,
      ),
      body: Container(child: regionalSelectionContainer,)
    );
  }

GradientAppBar is not a standard Flutter component. You should probably ask here.

GradientAppBar is not a standard Flutter component. You should probably ask here.

Thank you. but GradientAppBar just copy, no modification

@itAlvy Please provide your flutter doctor -v and also specs what the emulator you use.

Hello @itAlvy !
Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the issue, if you have any more information for us; we will reopen it right away!
Thank you for your contribution.
P.S. If anyone still experience the same problem, please file a new issue with the information required in the template.
All system setups can be slightly different so it’s always better to open new issues and reference related issues.

Hello
Did anyone get the solution for this?


NodeJs compatibility

Hey all, I was working with this plugin on the node version 12.15.0 and over there it wasn't working... by downgrading to 12.4.0 it did work. Met me post more details soon, but any suggestions where this is coming from?
The issue I encountered was that the webpack build kept spinning reaching some of the first encountered styled-components. repeatedly the same file. (implementation of the component made no difference). simple for example: styled.div with background color
also running the test directly in the repo seems to be broken?

after this test i downgraded to node 11.9.0 via nvm. result is that jest is run within seconds!

checking versions it seems like version 12.10 is correct, higher is broken. confirmed 12.11.0 is not working, (12.11.1 also broken )

locally I updated all packages (including jest, and styled components helpers for version 5) but didn't help me any further...

looks like postcss.process.then neither . catch is being triggered:

https://github.com/trevorburnham/babel-plugin-namespace-styled-components seems to be having the same issue

Same issue here, seems to come from deasync loopWhile.
Removing deasync and forcing postcss to use synchronous process (replacing process(...).then(...) by formattedCss = process(...). css) seems to fix the problem but is highly discouraged by postcss documentation ...

Deasync is no longer a dependency.
Commit on Jun 3


Improve test coverage

Test coverage very spotty currently. No reason it can't be >90%

100% test coverage since v0.3.0


Allow use of default aiven token instead of authSecretReference on resources

This will allow running the operator with a default token, instead of having to add a secret in every namespace where resources are created.
We had some trouble deciding on how to test this, so we made only a minimal change adding an additional test to redis_controller_test.go. This doesn't really cover the different cases properly, but we were unable to find a suitable way to do it. We are unfamiliar with Ginkgo, so might be some tricks we didn't find that would have solved it.
Since the test is mostly a simple cut&paste and minor change, we didn't want to do it for all controllers, when the actual logic change is in common code.
We tried running make test-e2e to get a proper check that it worked, but that didn't seem to run even before our changes.
make test-acc works as it should.
Fixes #183

hey 👋
thank you for your contribution! our team will evaluate your PR soon and will reach out with feedback, if any!


[BUG] Solid Infuser REI Steel Dust recipe error

Description:
To make Steel Dust, it should be coal dust + iron dust, but this is not shown in the recipe
Steps to Reproduce:

Open the Steel Dust REI recipe GUI

Technical Information:

Minecraft: 1.17
Fabric API: 0.36.0
Industrial Revolution: 1.10.0-alpha.7

What's the bug?

The recipe displayed in REI is coal dust (TechReborn) + coal dust (Industrial-Revolution), but it should be coal dust + iron dust in order to make it.

This is fixed as of alpha 12. Thanks for reporting.


RFC: switch metrics map to cilium/ebpf

With this PR I'd like to start the conversation on migrating the logic to handle
eBPF maps to the cilium/ebpf library (and also get a sense of the effort
required for the switch).
This PR focuses on one specific map, the metrics map. We don't do anything too
complicated with it so I figured it would be a good first candidate.
The changes are split into 3 commits:

the first one introduces a new ebpf package which wraps cilium/ebpf
and re implements a minimal set of functionalities of the bpf package (the bare
minimum required by the metricsmap package).
My proposal would be to incrementally port features from the bpf package to
the ebpf one on a map-by-map basis, but I wanted to hear your thoughts first
regarding other strategies
the second commit actually switches maps/metricsmap to use the ebpf
package
the third one gets rid of all the logic used to serialize and deserialize the
metricsmap keys and values as to my understanding there's no need to do that
(we can just access the actual map's keys and values).

Other questions:

ebpf package design: should this new wrapper around cilium/ebpf expose roughly
the same interface as the bpf package or are there shortcomings of the bpf
package that should be addressed taking advantage of this rewrite? (Or
alternatively we could do a first dumb rewrite and then once we are happy
with the switch focus on the actual API of the ebpf package? Maybe that could
help also with backports during the transition?)
exporting cilium/ebpf: currently the ebpf package re-exports the
cilium/ebpf identifiers that are required to use it (for example MapNew()
expects an argument of type ebpf.MapSpec{}).
I think in this way we could keep the ebpf package self contained (i.e. we
don't require the user to import both ebpf and cilium/ebpf) at the cost of
slightly increasing the complexity of the ebpf package as we need to manually
reexport every identifier but I don't have strong opinions on that

Nice work, this is a great start for adopting the lib! I'd like to suggest an alternative to the callback-based approach taken here. An example is implemented here: https://github.com/mdlayher/netlink/blob/8014f9a7dbf4fd7b84a1783dd7b470db9113ff36/attribute.go#L144 (AttributeDecoder)
Instead of making the caller specify a callback, put the caller in charge of controlling the iterator (e.g. calling Next()). The iterator  pulls the key and the value into the respective key, value fields of the map and returns control to the caller. This has some advantages:

If the caller is already aware of the contents of the map (or just wants bytes), the cost of reflect doesn't need to be paid on each step
If the caller found the value they're looking for in this particular iteration, they can break the loop and yield the lock without being forced to scan all the way to the end
If the caller is only interested in only keys or only values, we don't do any unnecessary processing

Of course, convenience wrappers can be added (like what IterateWithCallback() does), but the lower-level ops should be exposed for callers that don't need a full iteration.

Nice work, this is a great start for adopting the lib! I'd like to suggest an alternative to the callback-based approach taken here. An example is implemented here: https://github.com/mdlayher/netlink/blob/8014f9a7dbf4fd7b84a1783dd7b470db9113ff36/attribute.go#L144 (AttributeDecoder)
Instead of making the caller specify a callback, put the caller in charge of controlling the iterator (e.g. calling Next()). The iterator  pulls the key and the value into the respective key, value fields of the map and returns control to the caller. This has some advantages:

If the caller is already aware of the contents of the map (or just wants bytes), the cost of reflect doesn't need to be paid on each step
If the caller found the value they're looking for in this particular iteration, they can break the loop and yield the lock without being forced to scan all the way to the end
If the caller is only interested in only keys or only values, we don't do any unnecessary processing

Of course, convenience wrappers can be added (like what IterateWithCallback() does), but the lower-level ops should be exposed for callers that don't need a full iteration.

Nice work, this is a great start for adopting the lib! I'd like to suggest an alternative to the callback-based approach taken here. An example is implemented here: https://github.com/mdlayher/netlink/blob/8014f9a7dbf4fd7b84a1783dd7b470db9113ff36/attribute.go#L144 (AttributeDecoder)
Instead of making the caller specify a callback, put the caller in charge of controlling the iterator (e.g. calling Next()). The iterator pulls the key and the value into the respective key, value fields of the map and returns control to the caller. This has some advantages:
* If the caller is already aware of the contents of the map (or just wants bytes), the cost of `reflect` doesn't need to be paid on each step

* If the caller found the value they're looking for in this particular iteration, they can break the loop and yield the lock without being forced to scan all the way to the end

* If the caller is only interested in only keys or only values, we don't do any unnecessary processing

Of course, convenience wrappers can be added (like what IterateWithCallback() does), but the lower-level ops should be exposed for callers that don't need a full iteration.

I totally agree that lower-level ops should be exposed too :+1:
For this specific case I went for the callback approach (even though I usually try to avoid them, mostly for readability reasons) since that map requires to be fully iterated every time anyway and also because that's the approach we are currently following by using DumpWithCallback().

Nice work, this is a great start for adopting the lib! I'd like to suggest an alternative to the callback-based approach taken here. An example is implemented here: https://github.com/mdlayher/netlink/blob/8014f9a7dbf4fd7b84a1783dd7b470db9113ff36/attribute.go#L144 (AttributeDecoder)
Instead of making the caller specify a callback, put the caller in charge of controlling the iterator (e.g. calling Next()). The iterator pulls the key and the value into the respective key, value fields of the map and returns control to the caller. This has some advantages:
* If the caller is already aware of the contents of the map (or just wants bytes), the cost of `reflect` doesn't need to be paid on each step

* If the caller found the value they're looking for in this particular iteration, they can break the loop and yield the lock without being forced to scan all the way to the end

* If the caller is only interested in only keys or only values, we don't do any unnecessary processing

Of course, convenience wrappers can be added (like what IterateWithCallback() does), but the lower-level ops should be exposed for callers that don't need a full iteration.

I totally agree that lower-level ops should be exposed too :+1:
For this specific case I went for the callback approach (even though I usually try to avoid them, mostly for readability reasons) since that map requires to be fully iterated every time anyway and also because that's the approach we are currently following by using DumpWithCallback().

test-me-please

test-me-please

test-me-please

test-me-please

test-gke

test-gke

I didn't get a chance to review just yet, but I was wondering one thing - whether you have been able to do integration/runtime testing of the new version here? I'm not sure we have coverage of this. I'm guessing it's probably fine but if we suddenly broke the metrics CLI that would be suboptimal ;-)

I didn't get a chance to review just yet, but I was wondering one thing - whether you have been able to do integration/runtime testing of the new version here? I'm not sure we have coverage of this. I'm guessing it's probably fine but if we suddenly broke the metrics CLI that would be suboptimal ;-)

I didn't get a chance to review just yet, but I was wondering one thing - whether you have been able to do integration/runtime testing of the new version here? I'm not sure we have coverage of this. I'm guessing it's probably fine but if we suddenly broke the metrics CLI that would be suboptimal ;-)

There's a test case (for fragmented IPv4 packets) which uses GetBPFPacketsCount so at least indirectly we are testing it in the CI (and in addition to that I manually tested in the dev VM both the bpf metrics list command and the Prometheus exporter).
I agree that we should have better/proper coverage for this, I'll try to add something :+1:

I didn't get a chance to review just yet, but I was wondering one thing - whether you have been able to do integration/runtime testing of the new version here? I'm not sure we have coverage of this. I'm guessing it's probably fine but if we suddenly broke the metrics CLI that would be suboptimal ;-)

There's a test case (for fragmented IPv4 packets) which uses GetBPFPacketsCount so at least indirectly we are testing it in the CI (and in addition to that I manually tested in the dev VM both the bpf metrics list command and the Prometheus exporter).
I agree that we should have better/proper coverage for this, I'll try to add something :+1:

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

retest-gke

retest-gke

retest-gke

retest-gke

retest-netnext

retest-netnext

test-me-please

test-me-please

retest-netnext

retest-netnext

retest-netnext

retest-netnext

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

retest-gke


kibana: fix url and hash

the package now builds successfully on linux x86_64.
but i don't know if it's actual usable. i don't know the software and how to use it.
$ kibana
/nix/store/sdi8713i9av6rx4pkydggqyidp7mdc08-kibana-4.1.2/libexec/kibana/bin/kibana: Zeile 20: /nix/store/sdi8713i9av6rx4pkydggqyidp7mdc08-kibana-4.1.2/libexec/kibana/bin/../node/bin/node: No such file or directory

it seams it needs nodejs as a dependency.
build:
unpacking source archive /nix/store/kmx1sr29nnji0h76845qqj9r3n8b54f8-kibana-4.1.2-snapshot-linux-x86.tar.gz
source root is kibana-4.1.2-snapshot-linux-x86
patching sources
configuring
no configure script, doing nothing
building
no Makefile, doing nothing
installing
post-installation fixup
patching ELF executables and libraries in /nix/store/sdi8713i9av6rx4pkydggqyidp7mdc08-kibana-4.1.2
/nix/store/sdi8713i9av6rx4pkydggqyidp7mdc08-kibana-4.1.2/bin/kibana
not an ELF executable

@offlinehacker @rickynils

cc @offlinehacker


Uniform Mutation trying to mutate genes outside of the chromossome array

I am using Genetic Sharp to generate the Best team of Drones for a mission. Each gene in my chromossome stores the amount of a specific type of drone. The algorithm works perfectly fine except sometimes when performing a Uniform mutation it will try to change a gene outside of the chromossome. How could this happen? Am I doing something wrong?
Here is my code:

Chromossome

public class TeamChromosome : ChromosomeBase
{
    private readonly int[] _maxAmounts;

    public TeamChromosome(int[] maxAmounts) : base(maxAmounts.Length)
    {
        _maxAmounts = maxAmounts;
        CreateGenes();
    }

    public override IChromosome CreateNew()
    {
        return new TeamChromosome(_maxAmounts);
    }

    public override Gene GenerateGene(int geneIndex)
    {
        // Generate random gene value within the maximum amount for the type
        return new Gene(RandomizationProvider.Current.GetInt(0, _maxAmounts[geneIndex] + 1));
    }
}

And my fitness Function
public class DroneTeamFitness : IFitness
{
    private MissionPlanner missionPlanner;
    private List<int> quantities;
    private List<List<Drone>> capableDrones;
    private bool basedOnTime;

    public DroneTeamFitness(MissionPlanner missionPlanner, List<int> quantities, List<List<Drone>> capableDrones, bool basedOnTime)
    {
        this.missionPlanner = missionPlanner;
        this.quantities = quantities;
        this.capableDrones = capableDrones;
        this.basedOnTime = basedOnTime;
    }

    public double Evaluate(IChromosome chromosome)
    {
        var genes = chromosome.GetGenes();
        List<Drone> team = new List<Drone>();

        int droneIndex = 0;
        for(int i = 0; i < quantities.Count; i++)
        {
            int count = 0;
            foreach(Drone drone in capableDrones[i])
            {
                count += (int)genes[droneIndex].Value;
                for(int j = 0; j < (int)genes[droneIndex].Value; j++)
                {
                    team.Add(drone);
                }
                droneIndex++;
            }
            if(count > quantities[i])
            {
                return 0;
            }
        }
        // Check if the team is empty
        if(team.Count == 0)
        {
            return 0;
        }

        (List <Drone> teamOverWater, List <Drone> teamUnderWater) = missionPlanner.assignDroneToWorkingArea(team);

        // Check if the team can perform the mission
        Mission mission = missionPlanner.mission;
        if ((mission.HeigthLimit.upperLimit > 0 && teamOverWater.Count == 0) || mission.HeigthLimit.lowerLimit < 0 && teamUnderWater.Count == 0)
            return 0;

        List<List<DronePath>> missionPaths = missionPlanner.PlanMission(teamOverWater, teamUnderWater);
        double missionCost = PathEvaluation.calculateMissionCost(missionPaths);
        double missionTime = PathEvaluation.calculateMissionTime(missionPaths);
        // You can add more criteria to evaluate the fitness

        if (basedOnTime)
        {
            return 1 / missionTime;
        }
        return 1 / missionCost;
    }
}

Managed to fix it by changing the UniformMutation constructer from UniforMutation(true) to UniformMutation(mutableGenesIndexes) with the indexes of the chromossome.


fix(linter): fix useDateNow false positive when new Date has arguments

Summary
Fixes https://github.com/biomejs/biome/issues/3133
Test Plan
Added failing cases

@minht11 Sorry to tag you here, I didn't find a way of contacting you: have you a Discord handle?

@Conaclos sent you a DM.


Create chart for powerdns and powerdns-admin

There's a bunch of charts out there, however there is only one on helm hub:
https://github.com/halkeye-helm-charts/powerdns
https://github.com/halkeye-helm-charts/powerdnsadmin
It would be nice to merge these into one like https://github.com/aescanero/helm-charts

Partially resolved by #308 ?

@onedr0p -- I think it'd make sense to add the powerdns-admin to this chart and have it toggle on/off with a .Values.powerdnsadmin.enabled switch.
However we end up doing it though, the configuration of PowerDNS-Admin will be manual as the app itself doesn't expose the PowerDNS API configuration per this issue: https://github.com/ngoduykhanh/PowerDNS-Admin/issues/783

I agree we can have an option to enable and maybe in the readme have some small instructions on how to configure it.


Building iOS app invalidates provisioning profile when using document picker

Build/Submit details page URL
No response
Summary
I've migrated to EAS build and in the same time I've used iCloud service with expo DocumentPicker.
So I'm no sur which is causing this issue...
But each time I launch a new build I'm facing Provisioning profile (id: *******979) is no longer valid

If I answer Yes to Generate a new Provisionning Profile it generate a new one correctly and it works ... But if I run the command again (like 10 sc later) the previous (freshly generated) provisionning profil is now invalid ...
It may be linked to iCloud.
I've added  "usesicloudstorage": true in my app.json
I also have this configured in my app identifier :

With an container named  iCloud.<your_bundle_identifier> as mentionned in the documentPicker docs
$ eas --version
eas-cli/0.50.0 win32-x64 node-v16.13.1

Managed or bare?
Managed
Environment

   npx expo-env-info
expo-env-info 1.0.2 environment info:
    System:
      OS: Windows 10 10.0.19041
    Binaries:
      Node: 16.13.1 - C:\Program Files\nodejs\node.EXE
      npm: 8.1.2 - C:\Program Files\nodejs\npm.CMD
    SDKs:
      Android SDK:
        API Levels: 30
        Build Tools: 30.0.3
        System Images: android-30 | Google APIs Intel x86 Atom
    IDEs:
      Android Studio: Version  <IP_ADDRESS> AI-202.76<IP_ADDRESS>51085
    npmPackages:
      expo: ^43.0.0 => 43.0.5
      react: 17.0.1 => 17.0.1
      react-dom: 17.0.1 => 17.0.1
      react-native: 0.64.3 => 0.64.3
      react-native-web: 0.17.1 => 0.17.1
    Expo Workflow: managed

Error output
No response
Reproducible demo or steps to reproduce from a blank project
I think it happens with any blank project

I've been having basically the exact same issue, but do not use iCloud in our app

This sth we are aware of, We don't have any plans to fix it in the near future, as far as I understand the only problem here is that profile is regenerated every time which is not a problem (you do not need to login to apple for every build)

Well as far as I know I DO have to login for each build I want to send to testflight :/
And btw the certificat page will be a huge mess in a while ...

Well as far as I know I DO have to login for each build I want to send to testflight :/

You don't need to login when building for appstore(for ad-hoc builds you do) if your have credentials already configured. For submitting you need to login only if you don't have ascAppId specified in eas.json.

Can we reopen this? This problem still happens to me with latest CLI versions.

@wkozyra95 Could you reopen this please? It's still an issue

Can you please reopen this issue. It does not appear to be solved yet.

👍 same issue here. Any news on that?

thanks, we'll investigate. you can work around this with EXPO_NO_CAPABILITY_SYNC=1 eas build for now. more info

This same thing started happening to us after following OneSignal's instructions for enabling Push Notifications when doing our next TestFlight build.
Note: I built for the simulator and for the dev-client without running into this issue and both builds correctly include the OneSignal packages - and the dev-client receives notifications from OneS correctly.
Now it's a bit unclear whether the workaround (EXPO_NOCAPABILITY_SYNC=1) should be used immediately or after the first capability sync. E.g. will I have our new push capability in a new build without doing the sync.
And if I get asked again, is Y or n the correct answer for the workaround?

Now it's a bit unclear whether the workaround (EXPO_NOCAPABILITY_SYNC=1) should be used immediately or after the first capability sync. E.g. will I have our new push capability in a new build without doing the sync.

No workaround is strictly necessary, the only problem with the current state is that it regenerates a new profile even if it's not necessary. You should set EXPO_NO_CAPABILITY_SYNC when you know that there is nothing new to sync, so you need to run without that env only when changing entitlements in app.json or if are changing/adding/removing config-plugin that might modify entitlements.

And if I get asked again, is Y or n the correct answer for the workaround?

Answering no to login to apple prompt will also stop syncing profile, but e.g. internal distribution build requires login to apple, so it will not work in every case.

Every time I run EXPO_DEBUG=true eas build --platform ios --profile profilename it figures out (incorrectly) that Provisioning profile (id: 6BJB75X655) is no longer valid, however it was created just seconds earlier using the same command and is listed as valid in the expo GUI until next year. This breaks our CI builds. I guess we'll have to resort to EXPO_NOCAPABILITY_SYNC=1 for now

Will this work properly if we update expo-document-picker?

Still an issue, not stale

I'm not using expo-document-picker but i am using with-rn-image-crop-picker.

Same issue here every single time.

Issue is still here

This is definitely an issue. Every time I have to change/select a certificate using the eas-cli, Certificates on Apple Developers get disabled.

Still a problem, not stale

still not stale :|

Same problem as @pkreipke once adding OneSignal to the mix, now every build incorrectly says provisioning file is invalid and generates a new one, next build the exact same thing. We need a fix as it is very annoying and adding the env var is likely to cause issues for some when changing entitlements as https://github.com/expo/eas-cli/issues/1069#issuecomment-1277391690 mentions and not knowing/remembering this is the "fix"

Not stale

Not stale

same here.

very fresh and not stale

I am getting this same issue. If anyone have solution for this please let me know.

Same with OneSignal extension

we'll certainly investigate this at some point, however because this doesn't actually cause any issues that we were aware of, it's not a top priority. you can do one of the following options:

re-generate the profile as prompted to do, and there will be no negative side effects
set EXPO_NO_CAPABILITY_SYNC=1 to opt out of automatic capability syncing
run eas build -p ios --non-interactive to skip validating profiles until you need to re-generate one (eg: to add a new device uuid)

Still an issue, as far as I'm aware.

@brentvatne this is a huge issue if we manage our own certificates with Fastlane that we share across the team. This bug basically makes the whole system useless unless we run it with --non-interactive which means we can't take advantage of some of the interactive features.

I'm seeing this also

Getting this same error after adding push notification capabilities.

Not stale. Still facing this issue.

Same here, definitely still an issue

This is extremely annoying and error-prone - CI builds are failing due to this. Is there any plan to fix this at all?

I had to delete my provisional profiles and certificates and create a new one while creating the build. Only then did this issue get resolved, but for that build only, in the new build again I am having the same issue. Expo needs to address this right now.

I had to delete my provisional profiles and certificates and create a new one while creating the build. Only then did this issue get resolved, but for that build only, in the new build again I am having the same issue. Expo needs to address this right now.

Yes, it's rather confusing how it works with different combinations of actions as well. I wish the expo team would prioritise this. Right now, I'm using EXPO_NO_CAPABILITY_SYNC=1 for CI, and hoping that it all works consistently. That's not a solution though.

I had to delete my provisional profiles and certificates and create a new one while creating the build. Only then did this issue get resolved, but for that build only, in the new build again I am having the same issue. Expo needs to address this right now.

Yes, it's rather confusing how it works with different combinations of actions as well. I wish the expo team would prioritise this. Right now, I'm using EXPO_NO_CAPABILITY_SYNC=1 for CI, and hoping that it all works consistently. That's not a solution though.

Sometimes that, too, is not working for me. For instance I had to try 3 times yesterday only on 4th attempt I got proper working build in TestFlight.

Yea we are facing this issue with my team too, it complicates all of our processes, solutions mentioned so far are avoiding the issue :(

Not stale

Not stale

Still not stale

Just started realizing that this is happening — why is invalidating the provisioning profile with every build? Seems egregious

Yep @chrysb It should not happen and they are not responding in any manner that why this is happening or when they are planning any fix.

I'm having this problem too!

I started having this problem after enabling signin with apple in firebase console (not sure if even related).

hey folks, here's where we're at on this:

you can opt out of having EAS manage your capabilities (which is what is leading to this behavior) with EXPO_NO_CAPABILITY_SYNC=1 eas build (original comment docs).
we are aware of the issue but aren't sure what the right approach is to fix it, and invalidating the provisioning profile doesn't have any negative side effects as far as we are aware, so we are focusing on higher priority work and will come back to this in the future when we have bandwidth to deal with it. please correct me if i am wrong and this is actively causing issues for your project.
if you would like to investigate and suggest a solution, it'd be much appreciated!

Not stale

Having the same issue after adding document-picker

Yet another team experiencing this for the first time. It ate a few days of my time, and the fix is elusive. I've spent two whole days adding debug statements to eas-cli, checking GraphQL requests with ProxyMan, the openssl CLI, fiddling with Apple Connect and certificates and capabilities, and lots more.
Capability syncing seems like a red herring at first because, why would I touch our app's capabilities if they haven't changed in years? I ignored that part of the docs for a while.
How about a breadcrumb for people in the same situation as me? Possibly change the error message after "no longer valid" to say something like, "If this seems like an error, please refer to [URL to this issue]"
<3

This is widespread issue, why expo team is not replying or helping us to guide in direction that can fix this issue.
I am not sure what is causing this issue and how to fix this.

@kuldip-simform et. al,

Erase all (or at least all app-related) credentials and provisioning profiles from Apple Connect here and here
Run eas credentials and recreate all the credentials you need
Only run eas build with a EXPO_NO_CAPABILITY_SYNC=1 prefix so that eas-cli no longer touches and invalidates provisioning profiles

Not stale

I'm guessing this is about to be stale'd again: not stale.

Hello and thanks for commenting,
I do plan to look into this but I'm currently dealing with other tasks and don't have a clear timeline for this.
Let me also reiterate that if someone were to investigate and suggest a solution or pinpoint where the problem is happening, it'd be much appreciated!
Another way to help would be to give step-by-step instruction on how to reproduce the problem from a clean state - I haven't found these in the discussion.
Either of these will enable a faster issue resolution.
If anyone's interested, the code is open source and has a contributor guide.
Thank you! 🙂


Revert some codemirror tweaks, disable code folding in style tab

Disable code folding in style tab, disable active line highlight and whitespace visibility.
Issues: #1905, #1907

Do we need to disable active line highlight now, given https://github.com/naturalcrit/homebrewery/issues/1905#issuecomment-998398811 ?

@ericscheid There were some other complaints on Reddit as well.


LE Audio: TBS optional notification Bearer URI Schemes list

Is your enhancement proposal related to a problem? Please describe.
The TBS Bearer URI Schemes Supports list is optionally notifiable and this should be reflected in the implementation.
Describe the solution you'd like
The TBS server and client implementations should optionally support handling the notification.
Describe alternatives you've considered
N/A
Additional context
N/A

This is still valid


Intermittent Tests Timeout

This happens occasionally on CI. Seems to happen w some frequency on my local machine.
Because this is so sporadic, its hard to pin down reproduction steps or draw many conclusions. I'll be as precise as I can about what I know:

this happens when running just the fuse tests  ... a la `$ CGOENABLED=0 GO15VENDOREXPERIMENT=1 go test -v -cover -timeout 20s $(go list ./src/server/... | grep -v '/src/server/vendor/' | grep '/src/server/pfs/fuse')'
the tests either pass quickly (in ~3s) or timeout (in 20s)
it seems that either a single test runs (and hangs) or many run (and we fail in a similar # of tests)
sometimes we see the issues reported in #344 or #345

Because sometimes a single test runs and hangs, its hard to point at any test parallelism as a culprit. Last time around I tried to reproduce (this is anecdotal) I had se the -p and -parallel flags to guarantee serial tests running (and even repeatedly ran a single test) and saw the same behavior. So ... I don't think test parallelism is to blame.
Another interesting failure pattern (this seems to happen more when multiple tests end up running ... not just a single one) is that the testFuse helper calls its defer function ... but the actual test callback never seems to complete? At least based on the stdout.
And based on the attached logs (each number is a run # corresponding to a failed run), we can see that it hangs in some different places.
4 - MountCachingViaWalk // missing 'callback ran' print statement
7 - ??? waiting after unmount?
8 - TestRootReadDir (of note ... this was the only test run in this iteration ... so hard to conclude it was a RC btw tests)
9 - Same test / same in that only one running
12 - TestMountCachingViaShell // all print statements look normal
13 - TestMountCachingViaShell // missing 'callback ran' print statement
Our best working theory is that there is some issue w the number / frequency of mounts/unmounts you can do w OS X fuse.
intermittent-failures.tar.zip

This is really old, and I don't think we have intermittent timeout/failures w the FUSE test suite anymore.


Added attrsOr, attrs, and object

See question on Gitter.

Codecov Report

Merging #173 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #173   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           1      1
  Lines        1146   1187   +41
=====================================
+ Hits         1146   1187   +41

Impacted Files
Coverage Δ

dist/partial.lenses.cjs.js
100% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


eliminate_stim_artifact for evoked

eliminate_stim_artifact only accepts raw objects. It makes more sense to remove the artifact on evoked.
eliminate_stim_artifact should accept evoked object.
any taker?

I think its solution is that copy notch_filter method in .io.base.py to evoked.py.

what do you mean the solution?

If you copy notch_filter method in .io.base.py to evoked.py, you can eliminate stim_artifact for evoked, I think.

? stim artifact is not corrected with notch_filter. See how it is done with
raw files.

Oops.. Sorry for my mistake.. I have misunderstood about this issue..

issue should be simpler than dealing with notch filter

It's eliminate_stim_artifact not eliminate stim_artifact :)
Take a look here: https://github.com/mne-tools/mne-python/search?utf8=✓&q=eliminate_stim_artifact

@agramfort Now we can close this issue.


Update README.md

Rock Paper Scissors is available now

@randall-Mysten This one didn't merge because of the failed 'devnet' check? Or it's waiting for a second approval of Ronny?

I just neglected to click the button


[$500]  IOU - It shows a location permission denied error

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

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

Start creating a distance request in a workspace chat
Tap on the Start
Tap on the "Use current location" button

Expected Result:
It should be showing my location on my map or ask for permission
Actual Result:
It shows a location permission denied error. Safari location setting can be "Ask" or "Allow"
Workaround:
Unknown
Platforms:

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

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

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/47d43b9d-7563-4d3e-a50f-de4edaad8eed
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0199b0f95a9b2d0ac2
Upwork Job ID:<PHONE_NUMBER>301574144
Last Price Increase: 2024-02-22

@bz FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

I think this can be external

It looks like it's actually default behavior to require a refresh after changing from allow to disallow or disallow to allow.. I think in this ticket the tester had it as disallow, and is not getting it to be allowed ( unless he would refresh)
I found some hacky workarounds, such as doing the location fetching in an iframe, so that it doesn't require a refresh, but this is not ideal.

For me it was never asking for location permission as Safari had location permission set to "never" under Settings> Privacy> Location Services > Safari". I don't remember setting it. After switching it to Ask next time or Allow while using seems to fix the issue. However there is no indication on the map screen that location permission is denied. I think this needs a UI fix.

For me it was never asking for location permission as Safari had location permission set to "never" under Settings> Privacy> Location Services > Safari". I don't remember setting it. After switching it to Ask next time or Allow while using seems to fix the issue. However there is no indication on the map screen that location permission is denied. I think this needs a UI fix.

I observed that Mapview uses default coords instead of showing permission denied, but kept it out of scope of this ticket

Thanks for investigation here! I agree the current behavior is not optimal, but I also think that location permission denied is not terrible -- it does get the message across that location permissions need to be allowed (which seems to fix the issue). So given that this doesn't really fit anywhere on our roadmap at the moment I am going to close this, we may fix it later when we get into polishing distance requests but this seems pretty low priority at the moment.


[BYOC][DNNL] Enable layer normalization in DNNL byoc.

This patch is to enable layer normalization in DNNL BYOC by providing an out-of-box rewrite pattern for combining the operators into a single relay layer normalization operator as well as its implementation in dnnl json codegen.
After applying the rewrite pattern, we will observe the following dnnl function:
6202 def @tvmgen_default_dnnl_main_108(%dnnl_108_i0: Tensor[(1, 784, 128), float32], Inline=1, Compiler="dnnl", global_symbol="tvmgen_default_dnnl_main_108", Primitive=1) -> Tensor[(1, 784, 128), float32] {
6203   nn.layer_norm(%dnnl_108_i0, meta[relay.Constant][56] /* ty=Tensor[(128), float32] */, meta[relay.Constant][57] /* ty=Tensor[(128), float32] */) /* ty=Tensor[(1,  784, 128), float32] */
6204 }

Once you enable DNNL_VERBOSE flag, more informations are shown in log file as below:
onednn_verbose,exec,cpu,layer_normalization,simple_layer_normalization:any,forward_inference,data_f32::blocked:abc:f0 stats_undef::undef::f0 diff_undef::undef::f0,,flags:CH,1x784x128,0.0551758

Thanks for contributing to TVM!   Please refer to guideline https://tvm.apache.org/docs/contribute/ for useful information and tips. After the pull request is submitted, please request code reviews from Reviewers by @ them in the pull request thread.

Thanks for your contribution for BYOC-DNNL. And my suggestions are listed below:

I wonder if we can get better performance via running layernorm on dnnl codegen than running consecutive ops on native codegen. Could you please provide some performance numbers?
Lint has failed. Please run task_lint.sh to check the code style.
UT is required. You can add your test cases in tests/python/contrib/test_dnnl.py to ensure the functionality of the enabled ops.

Hi @apeskov , please take a look at the latest version here. Feel free to comment more.

Hi @masahi Please take a look.

Hi @comaniac , @trevor-m , @mbaret , Could you take a look at this pr? Thanks!

You need to resolve the conflict in test_dnnl.py, but since it will be modified in #11513, let's merge #11513 first.

Hi @masahi , Thanks for pointing out this. I have resolved the conflict in test_dnnl.py.


US618048: Updating copyright headers

https://internal.almoctane.com/ui/entity-navigation?p=131002/6001&entityType=work_item&id=618048

A developer build has not yet been created for this branch. Click here to go ahead and create the build...

Inception year has changed in this one.

I think this is correct as I did not change the inception year I just added it to the copyright notice. I think previously someone must have updated the copyright year without adding the inception year to copyright notice which is why it was 2022 in the header. However in the pom the inception year is 2021.


Live Updating Upcoming Departures

Summary of changes
Asana Ticket: ⏱Schedule Finder | Upcoming Departures not updating live
This is a pretty chonky refactor of this component. Notable things include:

new utility hooks / functions:

useProvider
useAwaitInterval
fetchJson

utilizing the above ^ to simplify the existing data fetching in the schedule finder (i.e. removing the reducers, different states, etc.)

Also, the network fetching code now just raises an exception since it's only done in one place and the previous code didn't really do anything particularly smart with the errors anyways.

Behavior changes:

Instead of lazily fetching trip info data for non-bus modes, all modes now fetch the trip info data up front
The departure information and trip details in the modal should continually update while the modal is open (but not when the modal is closed)
ANYTHING ELSE IS A BUG (I think 😄)

Please ask questions about things that don't make sense. I've tried to keep the changes clear, but I'm happy to clarify anything.
I've also set the refresh rate to be ~once per second, but I think this could probably be extended. Let me know what you think!

Nick and I observed what seems like a bug on https://dev-green.mbtace.com/schedules/1/line: more than one prediction is visible in the line diagram, but when the Schedule Finder is opened only one upcoming departure is listed. It also seems to be an issue in prod. 😬 We should fix it, but if it's too different from the current PR or messy we can split into a different task & PR.

I didn't notice that in the schedules I was looking at, that's interesting! Let's address that separately.

Nick and I observed what seems like a bug on https://dev-green.mbtace.com/schedules/1/line: more than one prediction is visible in the line diagram, but when the Schedule Finder is opened only one upcoming departure is listed. It also seems to be an issue in prod. grimacing We should fix it, but if it's too different from the current PR or messy we can split into a different task & PR.

I didn't notice that in the schedules I was looking at, that's interesting! Let's address that separately.

I think this may be a temporary API blip or something like that. We don't render table rows for trips without predictions, and for this particular route this morning, 4 out of the 5 trips we received from the backend didn't have predictions for some reason. Either way, I don't think this bug was introduced by this work so it makes sense to address it separately :+1:

Bigger picture question—and caveat up front that I haven't actually looked at these code changes yet, I just read the PR note, so apologies if I could have answered my own question if I was a better reader…
I'm curious about the impetus behind using polling. I guess I tend to think of polling as (often) an anti-pattern (or a term one degree less severe than that) in Phoenix given that Channels are one of Phoenix's most awesome features. Would channels work here? I.e. could the client subscribe to updates and when the data changes on the server the changes are pushed to the client immediately? I don't know this example very well, but just at a quick glance, it looks like the Map is one place we already use this.

I'm curious about the impetus behind using polling. I guess I tend to think of polling as (often) an anti-pattern (or a term one degree less severe than that) in Phoenix given that Channels are one of Phoenix's most awesome features. Would channels work here? I.e. could the client subscribe to updates and when the data changes on the server the changes are pushed to the client immediately? I don't know this example very well, but just at a quick glance, it looks like the Map is one place we already use this.

I was not aware of Phoenix channels :) do you have any thoughts on how this would work? How would the backend know when to "push"? Since there are many permutations of this data possible (e.g. each individual route, the user selecting the start/end station, etc), I wouldn't want to maintain open connections for polling each possible combination of these from the API on the backend. Otherwise, if we're just lazily initializing polling on the backend and forwarding the result of that polling to the frontend, that doesn't seem like a huge difference vs. just polling from the front end.
Definitely open to exploring this direction more though! (this is good to keep in mind for the upcoming predictions work as well)

Can Dotcom handle this many requests?

@thecristen
For context, I'm not fully aware of exactly how often this feature is used, or of any existing performance concerns. Also, the behavior you are seeing of the multiple network requests is currently what happens in production with bus routes (since we need to fetch the crowding information up front to render the icons), aside from the reloading.
That said, I would be pretty surprised if this had a noticeable performance impact, since:

I believe these endpoints are fairly performant, at least no more taxing than the existing line diagram stuff
We're only ever sending up to 6 requests / refresh interval / page, since the endpoint that returns the departures only returns a maximum of 5, and there can only be one instance of the modal on each page.

If we're concerned about users potentially accidentally DoSing us by having multiple pages open or something, that sounds like something we should fix globally :)
Before I merge this, I can also adjust the refresh interval to be something more like 5-10 seconds if that seems more reasonable.
I think if anything, this could be something that gets addressed when we about the prediction unification work as well.
Anyways, let me know if that eases any of your concerns. I personally think the risk of deploying this is low enough that we should just try it out and eyeball any existing hardware performance metrics to see if there's any noticeable change.

Re: Channels: I think that's a great way to go ultimately! @zovt: to see how it works you can look at apps/vehicles/lib/stream.ex as an example. The API handles streaming new vehicle info, and we handle processing that here. The web application can subscribe to this stream via Phoenix channel, and there's a Javascript mechanism to hook into that.
It's very neat and I think we should totally use it for predictions, probably at a later point. I leave it up to you whether you want to follow that thread now or later! :)
With respect to this PR in its current state, I will note we've gotten burned in the past by polling implementation attempts that had to be hastily reverted. 😉 I'm happy to take a deploy-and-see approach here but we still need the Live icon.

It's streaming all the way down!

Interesting, thanks for the information! I think for now I'll opt to stick with the polling since this PR is already quite large and will probably end up getting gobbled up in the predictions rework work. But I do like the idea of moving to the push-based channels as part of that work!
W/r/t the other outstanding feedback, I'm planning on getting that all set today before merging :) thanks!

@thecristen @lund5000 I think this should be good to go for another round of review

My bad, looks like there was a lot more to the old "live" icon 🤦🏼♀ I'll submit a fix in a moment.


Network manager leaking memory

The network manager holds a strong reference to its delegates. so the class assigned as a delegate to network manager is never released due to strong memory reference. I'm attaching profiler screenshots supporting for my issue.

I opened the DetailsViewController 3 times while profiling, you can see 3 persistent and 0 transient objects. this means the DetailViewController is never released.

This screenshot is from memory Graph debugger indicating the leaked objects

Assign me. I'll make a PR solving this issue


design: fix dead image links

/kind cleanup
NONE

/assign @irbekrm

Thanks @maelvls , I was planning to fix this before merging, but obviously that didn't happen 😆
/lgtm
/approve


ci: run clang-tidy as a part of CI

Signed-off-by: Lizan Zhou<EMAIL_ADDRESS>Description:
Run clang-tidy as a part of CI.
Risk Level: Low
Testing: CI, manual
Docs Changes: N/A
Release Notes: N/A
Fixes #921.

@lizan did you mean to push a change?

re: https://github.com/envoyproxy/envoy/pull/4666#discussion_r224260237 @mattklein123
OK Now I cleaned up .clang-tidy a lot, now it fails on certain checks that we've been seen in code reviews, which is actionable. (e.g. use make_unique/make_shared, side-effect ASSERT calls)
The remaining warning checks are also valid, but hard to fix in short time. I'll explore if diff check will make more sense for those
Here is the latest result: https://gist.github.com/lizan/23b289b977e4d85c140d61b187a08e03
If we agree on errors checks, we need a single sweep to all source to fix existing errors in another PR.
cc @envoyproxy/maintainers

Can we ignore warnings in thirdparty code?
In general yes these warnings seem reasonable to me. Can we do diffs and then turn it on as failing? Then we can potentially have someone go through and clean up the existing code as a background exercise.

Can we ignore warnings in thirdparty code?

The default header filter already filtered out many of them, but some of them are still raised regardless what I specify for header filter, I guess some of them are in macro expansion etc. The compilation database doesn't contain third party cc files so they are not checked at all.
Added readability-braces-around-statements, fixes #4706.

#4835 addressed the CI failure, @mattklein123 PTAL again.

@lizan I don't see clang-tidy running in the checks. Will it only run when merged to master? I thought it should run as part of this PR?

@lizan can you introduce a temporary clang-tidy failure into this PR (that we can then revert) just so we can see what the CI output/failure looks like?

@lizan nice this is awesome. If you revert the test commit this LGTM!


SwiftCSV has no shared framework schemes for osx

➜  GameChooser git:(master) ✗ carthage update --platform osx
*** Cloning SwiftCSV
*** Checking out SwiftCSV at "0.3.2"
*** xcodebuild output can be found in /var/folders/l0/0cslmcg90kl7zbmw2w22dhvr0000gn/T/carthage-xcodebuild.vzeVAq.log
*** Skipped building SwiftCSV due to the error:
Dependency "SwiftCSV" has no shared framework schemes for any of the platforms: Mac

If you believe this to be an error, please file an issue with the maintainers at https://github.com/naoty/SwiftCSV/issues/new

weird...i see them when i manually clone the project, but not when carthage does...

@mikehaney24  did you get this working?

Closed due to no response


oom problem

ref_img_camera_id = 0
mask_img_camera_id = 0

view = cameras[ref_img_camera_id]
img = view.original_image * 255
img = cv2.resize(img.permute([1,2,0]).detach().cpu().numpy().astype(np.uint8),dsize=(1024,1024),fx=1,fy=1,interpolation=cv2.INTER_LINEAR)
predictor.set_image(img)
sam_feature = predictor.features
# sam_feature = view.original_features

start_time = time.time()
bg_color = [0 for i in range(FEATURE_DIM)]
background = torch.tensor(bg_color, dtype=torch.float32, device="cuda")
rendered_feature = render_contrastive_feature(view, feature_gaussians, pipeline.extract(args), background)['render']
time1 = time.time() - start_time

H, W = sam_feature.shape[-2:]

print(time1)
plt.imshow(img)

in this block  when using prompt_segmenting
i got this oom error
how can i avoid oom problem??
my laptop is asus and rtx 2080super with 8gb vram
window 11, wsl2 ubuntu 22.04, anaconda envirioment
Details
OutOfMemoryError                          Traceback (most recent call last)
Cell In[15], line 7
      5 img = view.original_image * 255
      6 img = cv2.resize(img.permute([1,2,0]).detach().cpu().numpy().astype(np.uint8),dsize=(1024,1024),fx=1,fy=1,interpolation=cv2.INTER_LINEAR)
----> 7 predictor.set_image(img)
      8 sam_feature = predictor.features
      9 # sam_feature = view.original_features
File ~/SuGaR/SegAnyGAussians/third_party/segment-anything/segment_anything/predictor.py:60, in SamPredictor.set_image(self, image, image_format)
57 input_image_torch = torch.as_tensor(input_image, device=self.device)
58 input_image_torch = input_image_torch.permute(2, 0, 1).contiguous()[None, :, :, :]
---> 60 self.set_torch_image(input_image_torch, image.shape[:2])
File ~/anaconda3/envs/seggau/lib/python3.9/site-packages/torch/utils/_contextlib.py:115, in context_decorator..decorate_context(*args, **kwargs)
112 @functools.wraps(func)
113 def decorate_context(*args, **kwargs):
114     with ctx_factory():
--> 115         return func(*args, **kwargs)
File ~/SuGaR/SegAnyGAussians/third_party/segment-anything/segment_anything/predictor.py:89, in SamPredictor.set_torch_image(self, transformed_image, original_image_size)
87 self.input_size = tuple(transformed_image.shape[-2:])
88 input_image = self.model.preprocess(transformed_image)
---> 89 self.features = self.model.image_encoder(input_image)
90 self.is_image_set = True
File ~/anaconda3/envs/seggau/lib/python3.9/site-packages/torch/nn/modules/module.py:1501, in Module._call_impl(self, *args, **kwargs)
1496 # If we don't have any hooks, we want to skip the rest of the logic in
1497 # this function, and just call forward.
1498 if not (self._backward_hooks or self._backward_pre_hooks or self._forward_hooks or self._forward_pre_hooks
1499         or _global_backward_pre_hooks or _global_backward_hooks
1500         or _global_forward_hooks or _global_forward_pre_hooks):
-> 1501     return forward_call(*args, **kwargs)
1502 # Do not call functions when jit is used
1503 full_backward_hooks, non_full_backward_hooks = [], []
File ~/SuGaR/SegAnyGAussians/third_party/segment-anything/segment_anything/modeling/image_encoder.py:112, in ImageEncoderViT.forward(self, x)
109     x = x + self.pos_embed
111 for blk in self.blocks:
--> 112     x = blk(x)
114 x = self.neck(x.permute(0, 3, 1, 2))
116 return x
File ~/anaconda3/envs/seggau/lib/python3.9/site-packages/torch/nn/modules/module.py:1501, in Module._call_impl(self, *args, **kwargs)
1496 # If we don't have any hooks, we want to skip the rest of the logic in
1497 # this function, and just call forward.
1498 if not (self._backward_hooks or self._backward_pre_hooks or self._forward_hooks or self._forward_pre_hooks
1499         or _global_backward_pre_hooks or _global_backward_hooks
1500         or _global_forward_hooks or _global_forward_pre_hooks):
-> 1501     return forward_call(*args, **kwargs)
1502 # Do not call functions when jit is used
1503 full_backward_hooks, non_full_backward_hooks = [], []
File ~/SuGaR/SegAnyGAussians/third_party/segment-anything/segment_anything/modeling/image_encoder.py:174, in Block.forward(self, x)
171     H, W = x.shape[1], x.shape[2]
172     x, pad_hw = window_partition(x, self.window_size)
--> 174 x = self.attn(x)
175 # Reverse window partition
176 if self.window_size > 0:
File ~/anaconda3/envs/seggau/lib/python3.9/site-packages/torch/nn/modules/module.py:1501, in Module._call_impl(self, *args, **kwargs)
1496 # If we don't have any hooks, we want to skip the rest of the logic in
1497 # this function, and just call forward.
1498 if not (self._backward_hooks or self._backward_pre_hooks or self._forward_hooks or self._forward_pre_hooks
1499         or _global_backward_pre_hooks or _global_backward_hooks
1500         or _global_forward_hooks or _global_forward_pre_hooks):
-> 1501     return forward_call(*args, **kwargs)
1502 # Do not call functions when jit is used
1503 full_backward_hooks, non_full_backward_hooks = [], []
File ~/SuGaR/SegAnyGAussians/third_party/segment-anything/segment_anything/modeling/image_encoder.py:234, in Attention.forward(self, x)
231 attn = (q * self.scale) @ k.transpose(-2, -1)
233 if self.use_rel_pos:
--> 234     attn = add_decomposed_rel_pos(attn, q, self.rel_pos_h, self.rel_pos_w, (H, W), (H, W))
236 attn = attn.softmax(dim=-1)
237 x = (attn @ v).view(B, self.num_heads, H, W, -1).permute(0, 2, 3, 1, 4).reshape(B, H, W, -1)
File ~/SuGaR/SegAnyGAussians/third_party/segment-anything/segment_anything/modeling/image_encoder.py:358, in add_decomposed_rel_pos(attn, q, rel_pos_h, rel_pos_w, q_size, k_size)
354 rel_h = torch.einsum("bhwc,hkc->bhwk", r_q, Rh)
355 rel_w = torch.einsum("bhwc,wkc->bhwk", r_q, Rw)
357 attn = (
--> 358     attn.view(B, q_h, q_w, k_h, k_w) + rel_h[:, :, :, :, None] + rel_w[:, :, :, None, :]
359 ).view(B, q_h * q_w, k_h * k_w)
361 return attn
OutOfMemoryError: CUDA out of memory. Tried to allocate 1024.00 MiB (GPU 0; 8.00 GiB total capacity; 5.93 GiB already allocated; 0 bytes free; 7.19 GiB reserved in total by PyTorch) If reserved memory is >> allocated memory try setting max_split_size_mb to avoid fragmentation.  See documentation for Memory Management and PYTORCH_CUDA_ALLOC_CONF

In such situation you may have to reduce the rendering resolution of both image and mask. But I think 8GB seems too small for these codes. You may also need to use a much smaller SAM model for extracting masks, features and inference.

In such situation you may have to reduce the rendering resolution of both image and mask. But I think 8GB seems too small for these codes. You may also need to use a much smaller SAM model for extracting masks, features and inference.

Thankyou use smaller pretrained vit model?

Yeah, but this may still not solve this problem totally.


try to define > 1000 symbols, error not reported

Reported by ansley b manke on 31 Jan 2013 23:29 UTC
There's an upper limit of 1000 symbols that can be set with DEFINE SYMBOL, and with internal commands such as pplus that define symbols such as PPL$XORG.  This limit is set in ppl/symlib/dbmsubs.F, parameter VSHORT.
If we define more than 1000 symbols, the commands are accepted by Ferret but the symbol is just not defined. Ran into this in an LAS request for property-property plots fora a dataset containing 60 variables.
dbmsubs.F has logic that thinks it's going to detect too many symbols; there's a line,
if(mxshort.gt.VSHORT)stop 'exceeded symbol storage'
but that STOP is never executed.
First fix, just increase the parameter to 2000.
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/2035

Comment by ansley.b.manke on 1 Feb 2013 00:57 UTC
Fixed this in ppl/symlib/dbmsubs.F, increasing the limit to 2000 symbols.
I'll leave this open - still should fix the test for whether we are out of space.

Comment by steven.c.hankin on 1 Feb 2013 01:06 UTC
We don't want PLOT+ to run out of symbol space.  If we have already encountered an example where 1000 symbols won't cut it, then shouldn't we increase this to something much larger -- say 5000 at a minimum?  Or is there a lot of memory usage impled by doing so?


[foundation 4 of ?] DCOS-14745: Remove foundation from PluginSDK

List of PRs: https://github.com/pulls?utf8=✓&q=is%3Aopen+is%3Apr+author%3AnLight+foundation
Decided to extract this as a separate PR so that we can ship plugins and dcos separately.
This PR removes foundation from the PluginSDK so the only way to get it is to use is as a package.

retest this please 🍬

No need in this one anymore


on policy files

Added SFT training notebook and related files. SFT Qwen0.5B (Student) on Qwen7B (Teacher) generated completions dataset.

Hi, can you explain a bit more what is the need that you're trying to address here? Why do you need a dedicated "onpolicy" directory?


Access to fetch at 'https://xxxx.cloud.looker.com/api/4.0/queries/741/run/json_detail' from origin 'http://localhost:3000' has been blocked by CORS policy:

Dear, author,
I have just followed your tutorial but it does not work for me.
https://developers.looker.com/components/getting-started/
I see this error message.
Access to fetch at 'https://xxxx.cloud.looker.com/api/4.0/queries/741/run/json_detail' from origin 'http://localhost:3000' has been blocked by CORS policy:
I would be thankful if you give me any hint for this error

Have you made sure to follow this section from the article:
Configure CORS in your Looker instance
Cross-Origin Resource Sharing (CORS) is controlled by the same domain allowlist as embedding.
This is documented in more detail on the Single Sign-on (SSO) Embedding documentation page.
Navigate to Admin > Platform Embed on your Looker instance. This requires Admin privileges.
The React app runs by default at http://localhost:3000. By adding this address to the Embedded Domain Allowlist you are telling Looker to allow requests from the app and respond to those requests via the same address. This step is mandatory since the app will be making API requests to the Looker instance else there won’t be communication between Looker and the app.


Headless mode

This is the start of an idea for headless mode. I am curious if a complete example would get merged?
My goal is to be able to run this automatically on CI and have the job commit all successful updates.
Currently this is not possible due to the interactive nature of the cli.
This requires a few more changes (ie git rebase -i), but is pretty close to all that is needed.

Thanks :+1:


[BUG] When an input object has an optional enum argument, one of the generated values is "EnumValueNode"

There is a bug that occurs when a GraphQL schema has an optional enum argument on an input object. One of the values that hypothesis-graphql generates is: EnumValueNode. I'm guessing that this is happening during the case when the enum value is supposed to be null.
To demonstrate, run the following with pytest -s:
import schemathesis

schema = schemathesis.graphql.from_file(
    """
    enum MyEnum {
        FOO
        BAR
        BAZ
    }

    input MyInput {
        value: MyEnum
    }

    type Query {
        hello(i: MyInput!): String
    }
    """
)

@schema.parametrize()
def test_schema(case):
    print(case.body)

The printed output is the following:
{
  hello(i: {value: FOO})
}

{
  hello(i: {value: EnumValueNode})
}

{
  hello(i: {value: BAZ})
}

{
  hello(i: {value: FOO})
}

{
  hello(i: {value: BAR})
}

I am using:
schemathesis 3.6.3
hypothesis-graphql 0.4.1
graphql-core 3.1.4

Thanks for a great report! I will take a look at it today/tomorrow

As far as I understand, the following query will be valid, right?
{
  hello(i: {value: null})
}

As far as I understand, the following query will be valid, right?
{
  hello(i: {value: null})
}

Yes that's correct.
Thanks for the quick fix!

You're welcome :) I'll make a release today / tomorrow


Style tweaks

Updates a few comments
Uses dot notation to get __incrementalDOMData
Moves getKey and getNodeName into the node_data module

__incrementalDOMData needs to stay behind quotes unless we create an extern
for the closure compiler. We really need a closure compiler based test in
the open source project.
(Phone)
On Jul 13, 2015 8:56 PM, "Justin Ridgewell"<EMAIL_ADDRESS>wrote:

Updates a few comments
Uses dot notation to get __incrementalDOMData
Moves getKey and getNodeName into the node_data module

You can view, comment on, or merge this pull request online at:
https://github.com/google/incremental-dom/pull/54
Commit Summary

Update comments
Use dot notation
move get* data functions into node_data module

File Changes

M src/alignment.js
https://github.com/google/incremental-dom/pull/54/files#diff-0 (5)
M src/attributes.js
https://github.com/google/incremental-dom/pull/54/files#diff-1 (4)
M src/namespace.js
https://github.com/google/incremental-dom/pull/54/files#diff-2 (4)
M src/node_data.js
https://github.com/google/incremental-dom/pull/54/files#diff-3 (28)
M src/nodes.js
https://github.com/google/incremental-dom/pull/54/files#diff-4 (25)

Patch Links:

https://github.com/google/incremental-dom/pull/54.patch
https://github.com/google/incremental-dom/pull/54.diff

—
Reply to this email directly or view it on GitHub
https://github.com/google/incremental-dom/pull/54.

__incrementalDOMData needs to stay behind quotes unless we create an extern
for the closure compiler.

I figured something funny was happening with one of the minifiers. I popped that commit off the PR.


[Feature request] Open JSON saves from OpenPose Editor

In the title. It would be really cool if we could open saved JSON files generated from OpenPose Editor. Then we could fine tune hands and poses in general. This would be awesome. :)

This idea is cool, but we may meet tech problems that convert 2d point to 3d points. I will try to implement it if possible.

Maybe it's enough to estimate the Z depth OR set it to 0 as default value and we work from there. Maybe this works.
Thanks for the consideration.

For now, we supported  "Detect From Image", I think you can make an image from a 2D skeleton map by stable diffusion.
Then detect it in this editor to get a 3D skeleton map.


Use SDK with personal access token

Hi,
i'm trying to get the sdk running with personal access token but it seems not to work.
Is this a bug?
Or should it be just not be possible to use the access token for the real-time api?
At least this seems not be document anywhere
Thanks

At least in the Golang SDK i found an option to use the userId and token directy.
Seems like this is missing here?

Hi @eloo
It's weird and just workaround but you can use setAuth  from api file after that call get/post functions to check your token.
https://github.com/RocketChat/Rocket.Chat.js.SDK/blob/master/src/lib/api.ts#L57


Implement network policy engine

Related PRs are merged

Related PRs merged
https://github.com/Huawei-PaaS/CNI-Genie/pull/84
https://github.com/Huawei-PaaS/CNI-Genie/pull/91


Miniplex 2.0 Release Checklist

Time to get 2.0 out of the door. Here's a list of things I want or need to do — not all of them need to be done before the actual release:

[x] Upgrade to Typescript 5.x
[x] Upgrade most/all dependencies
[x] Change packages so miniplex is just the core and miniplex-react is the React bindings
[x] Documentation

[x] Check and update core package documentation
[x] Check and update React package documentation

[x] Write release notes (probably just copy & amend the 2.0 Beta release notes)
[x] Fix the Vercel deployment issues for the demo apps
[x] Figure out why the React demo breaks with the newest Three.js/R3F bits. I won't have time to look into this (or build a new demo), so maybe someone else can investigate?
[ ] Blog about the release, and the future of the package (and my web gamedev work in general)

Not 100% critical for a 2.0 release, but should do these too:

[x] Resolve the dependency to @hmans/event 0.2.0. There's Eventery now, maybe use that?
[ ] Publish @miniplex/bucket as bucketeer

Closing, as 2.0 has now been released.


Moved assertions from ListViewAssert to AbstractListViewAssert.

I noticed this while working on another project: These assertions look like they were in the wrong place as they won't be inherited by subclasses like ExpandableListViewAssert. If they were there for a reason feel free to reject this PR (I'm curious to know what that reason might be though).

Looks like a simple oversight! Can you sign our CLA?

Is there a privacy policy associated with the CLA?
On 07/03/2015 5:06 am, "Jake Wharton"<EMAIL_ADDRESS>wrote:

Looks like a simple oversight! Can you sign our CLA
http://squ.re/sign-the-cla?
—
Reply to this email directly or view it on GitHub
https://github.com/square/assertj-android/pull/153#issuecomment-77610997
.

No. It's all private, not shared.
On Fri, Mar 6, 2015 at 6:45 PM Fr Jeremy Krieg<EMAIL_ADDRESS>wrote:

Is there a privacy policy associated with the CLA?
On 07/03/2015 5:06 am, "Jake Wharton"<EMAIL_ADDRESS>wrote:

Looks like a simple oversight! Can you sign our CLA
http://squ.re/sign-the-cla?
—
Reply to this email directly or view it on GitHub
<
https://github.com/square/assertj-android/pull/153#issuecomment-77610997>
.

—
Reply to this email directly or view it on GitHub
https://github.com/square/assertj-android/pull/153#issuecomment-77657045
.

Ok, your word is good enough for me. Done.

Thanks for this!


Social Sharing content

Since each housing type deep dive section has a unique url, we can allow for sharing the links to socials along with predrafted copy.
Content needed:

[x] Tweet copy, hashtags, etc.
[x] Facebook copy

Closing as Twitter is pre-populated with definitions and link and Facebook with link (note facbeook is also pulling a site wide image for social card)


Not able to index the content of a dataframe(generated from a json file). Method Not Found exception

Hi,
I am trying to index the content of a dataframe (genearte from a simple json file) in solr using the following command:
val df = sqlContext.read.json("emp.json"); val solrOpts = Map("zkhost" -> "<ip>:<port>/solr", "collection" -> "sample_test2") df.write.format("solr").options(solrOpts).mode(org.apache.spark.sql.SaveMode.Append).save()
I am getting "Method Not Found" exception.
It says

Request to collection mycollection failed due to (405) org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error from server at http://:8983/solr/mycollection: Expected mime type application/octet-stream but got text/html.

Can I provide mime type in the **solrOpts **parameter?
Also, when I try to add a document from Apache Solr admin portal, then its getting indexed properly.
The schema.xml file has only three fields:

empid (unique)
employeename
country

Sample json : {"empid":"102","employeename":"Peter","country":"US"}
Thanks

@Chandanap99 Which version of spark-solr are you using or are you building from master ?
What Solr version are you using ?

@kiranchitturi I am building 2.1.0-SNAPSHOT of spark-solr
And the solr version is 4.10.
If this is a version compatibility issue, then please let me know which version of spark-solr I should build  to make it compatible with our solr version and to overcome this issue.
Thanks

Can you provide full logs from the script and also from your Solr server ?

Script error is attached
script_error.txt
sorl server does not show any error. It just has few rows with INFO
Thanks

@Chandanap99 The master branch is tested with Solr version 5.4.1. I can't think of any earlier releases that are compatible with 4.10.
If possible, I would recommend you to use Solr latest 5.4.1.
Regarding the error you saw Method not allowed, I think this is happening because the spark-solr is trying to update your schema via Schema API calls.
Can you share with us the commands you tried in spark-shell and all the logs from spark-shell REPL ?

we're not supporting Solr 4.x for this project, upgrade please


Wishlist: support Org?

(Original issue 719 created by sharyanto on 2011-12-14T14:49:56.445866+00:00)
Hi,
Any plans to support Org?
More about Org format: http://orgmode.org/
Thanks,
Steven

(Original issue was assigned to tshatch)

(Original comment by tshatch on 2014-05-17T01:26:16.477957+00:00)
If you can point us to something describing the syntax, then sure.

(Original comment by xparx on 2015-08-05T19:39:14.837669+00:00)
Hi,
I hope this is something useful to to you for implementing support for org-mode sytax.
There is an issue here on BB that at least show some traction for this here, so hopefully you can find some time to add it.
adding a link to what is org's own parser. May be it is helpful to you, org-elements
Regards, A

(Original comment by unhammer on 2015-10-14T08:18:25.010819+00:00)
https://github.com/gollum/gollum/blob/ab42c0c0dfc9879f73312ad2c804875b510a414c/lib/gollum/public/gollum/javascript/editor/langs/org.js seems to be gollum's org-mode handling

(Original comment by rustom on 2015-10-14T12:55:57.628115+00:00)
@tshatch: If you can point us to something describing the syntax, then sure.
http://orgmode.org/worg/dev/org-syntax.html

(Original comment by tshatch on 2015-10-17T01:04:31.624236+00:00)
I agree this would be useful, thanks for the links.  I'll try to get to it for the April 2016 release.

(Original comment by germanemotiv on 2015-12-17T07:44:08.788481+00:00)
I would like to get support for this :) Github does and it is very handy.

(Original comment by None on 2015-12-30T15:14:41.495033+00:00)
pls add i thought it is already supported :crying_cat_face:

(Original comment by malcook on 2016-01-08T19:35:46.637923+00:00)
+1, and, an implementation suggestion:
pandoc can be used to convert both markdown and org to html on the fly.
The following is an extract from an Apache .config file that allows for such conversions when docs are served by Apache.  I imagine something similar might work for bitbucket configuration.
#!shell

       # mec: Interpret markdown files to html on the fly
        ExtFilterDefine markdown-to-html mode=output \
                intype=text/markdown outtype=text/html cmd="/n/local/bin/pandoc -f markdown  -t html"
                ## --email-obfuscation=references
        SetOutputFilter markdown-to-html
        AddType text/markdown .md
        ##.markdown .md .Rmd
        # mec: Interpret orgmode files to html on the fly
        ExtFilterDefine orgmode-to-html mode=output \
                intype=text/orgmode outtype=text/html cmd="/n/local/bin/pandoc -f org  -t html"
                ## --email-obfuscation=references
        SetOutputFilter orgmode-to-html
        AddType text/orgmode .org

(Original comment by scott_harney on 2016-03-03T16:24:37.363828+00:00)
+1 for this addition. thanks

(Original comment by buenchaval on 2016-06-15T08:35:33.388944+00:00)
please add this. org-mode is awesome. thanks!

(Original comment by digash on 2017-07-20T15:07:11.954741+00:00)
(+ 1)

(Original comment by kaushalmodi on 2017-08-04T17:33:57.329518+00:00)
+1 please.
I am using Pygments with Hugo static site generator, and at the moment the Org source blocks are not recognized as code blocks.

(Original comment by amitthk on 2018-01-13T03:53:46.151994+00:00)
+1

(Original comment by kaushalmodi on 2018-08-01T18:15:16.856712+00:00)
I just implemented the Org mode syntax highlighting in the Go Chroma syntax highlighter (whose syntax is very much similar to Pygments'). Folks interested in Org mode syntax highlighting can switch to Chroma or port over that lexer from that PR to Pygments :)

As noted in the comments, it is possible to port Org mode support from Chroma (which is a Go port of Pygments) back to Pygments. However, this ticket has been open for nine years and nobody has chosen to implement this.
I recommend closing this ticket.


Email Message Update related to the additional record type inputs for MCFD Personal requests

As an IAO Intake Team member
I want  to see the the additional information from applicant on the Email Message
so that intake has the additional details for Processing and/or ministries to work efficiently during Request Document Review, analysis cycles
Assumptions & Scope
What are the assumptions for this story?

What is IN scope?

Refer #2861
This change for email message content should occur "only" for the personal requests, and only if applicant selects any of the new personal MCFD specific record type options.

What is NOT in scope?

General Requests and Personal Requests without "Yourself" option/checked on "Who are you requesting records about?"

Acceptance Criteria
Scenario 1: FOI Request email message with value "Myself" for  "Requesting info about" section

GIVEN ... a Personals Intake Team member reviewing FOI Request Emails
WHEN ... a personal FOI Request email message has "Requesting info about" section with value "Myself"
THEN ... a new section with main header "MCFD Records" should appear with subsection(s) related with new multi select options as per user story #2861

Scenario 2: Subsection on email message under "MCFD Records" main section

GIVEN ...  when applicant submitted a personal request and a Personals Intake Team member is reviewing FOI Request Email and
WHEN ... applicant has selected all the new additional record type options while submitting -  refer scenarios under US #2861
THEN ... on the email message received by Intake should look like below. Also, sub sections are conditional based on the selections. And all selections made should be listed with commas in between for easy copying to AXIS

Scenario 3: Display of selected sub-sub options on email message

GIVEN ...  when applicant submitted a personal request and a Personals Intake Team member is reviewing FOI Request Email and
WHEN ... applicant has selected all the new additional record type options while submitting - refer scenarios under US #2861
THEN ... on the email message received by Intake should look like above, with all "children" to the selected sub sections to be "comma" delimited - refer image above
...

Dependencies? What is the impact of this dependency? (If so, link dependency in the ticket, make it visible in a team´s backlog)
#2861
Validation Rules? (If yes, list here)
Design
@xxx - please link the Design here
Definition of Ready

[ ] Is there a well articulated User Story?
[ ] Is there Acceptance Criteria that covers all scenarios (happy/sad paths)?
[ ] If there is a user interface, is there a design?
[ ] Does the user story need user research/validation?
[ ] Does this User Story needs stakeholder approval?
[ ] Design / Solution accepted by Product Owner
[ ] Is this user story small enough to be completed in a Sprint? Should it be split?
[ ] Are the dependencies known/ understood? (technical, business, regulatory/policy)
[ ] Has the story been estimated?

Definition of Done

[ ] Passes developer unit tests
[ ] Passes peer code review
[ ] If there's a user interface, passes UX assurance
[ ] Passes QA of Acceptance Criteria with verification in Dev and Test
[ ] Confirm Test cases built and succeeding
[ ] No regression test failures
[ ] Test coverage acceptable by Product Owner
[ ] Ticket ready to be merged to master or story branch
[ ] Developer to list Config changes/ Update documents and designs
[ ] Can be demoed in Sprint Review
[ ] Tagged as part of a Release
[ ] Feature flagged if required
[ ] Change Management activities done?

@lmullane , @m-prodan  , @JHarrietha-AOT  - ACs updated - Please have a look!

@m-prodan this story is good for testing

QA Passed


FIX : MQTTDiscovery git branch (master is empty)

If you check MQTTDiscovery GitHub project page you will notice that plugin live in development branch.

Thanks!

Thanks!