complexmenu

Where can I find the complexMenu filed referred to in your examples?
https://prolayout.ant.design/example

Nevermind, I found it here:
https://github.com/ant-design/ant-design-pro-layout/blob/ad8ccc672ea136908b5eba05ca88a152f81367e4/docs/example/complexMenu.ts


Markers disappear when selecting a place on the map

The markers disappear when selecting a place on the map:
https://github.com/chairemobilite/evolution/assets/545502/dc320428-a369-4a89-9ce8-4d451e0ba323
Not sure if this is intended or not, but this behaviour is a bit odd. If someone accidentally misclicks, the markers are gone and they must click "Chercher le lieu à partir du nom" again, which isn't intuitive.
@kaligrafy  was this intended?

It was intended, but we may keep them until confirmed

Fixed


Implement the interdiff and combinediff bindings

Updated patchutils and integrated the limited version of combinediff.

I will look over the PR again before merging but it will be after I do push some breaking changes (in regards to #239 with updating rlua to 0.16), but I can rebase this PR when I do merge so you dont have to make changes yourself.

No problem. Do as it is more convenient for you.


Livecoding 9 - Add embed in the listing + loader utility

Embed of the video in the listing

Loader utility for testing purposes
stack exec twitch-analytics-loader

I'll merge as there's no conflict but this repository will be archived right after.


Jupyter notebook fails to start training

After disabling the quick_demo and starting the proper training, I immediately get an error message saying the following
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-17-dc35f3fe5fa8> in <module>
----> 1 model.train(X_trn, Y_trn, validation_data=(X_val,Y_val), augmenter=augmenter)

/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/stardist/models/model2d.py in train(self, X, Y, validation_data, augmenter, seed, epochs, steps_per_epoch)
    353         n_data_val = len(validation_data[0])
    354         n_take = self.config.train_n_val_patches if self.config.train_n_val_patches is not None else n_data_val
--> 355         _data_val = StarDistData2D(*validation_data, batch_size=n_take, length=1, **data_kwargs)
    356         data_val = _data_val[0]
    357

/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/stardist/models/model2d.py in __init__(self, X, Y, batch_size, n_rays, length, patch_size, b, grid, shape_completion, augmenter, foreground_prob, **kwargs)
     30     def __init__(self, X, Y, batch_size, n_rays, length, patch_size=(256,256), b=32, grid=(1,1), shape_completion=False, augmenter=None, foreground_prob=0, **kwargs):
     31
---> 32         super().__init__(X=X, Y=Y, n_rays=n_rays, grid=grid,
     33                          batch_size=batch_size, patch_size=patch_size, length=length,
     34                          augmenter=augmenter, foreground_prob=foreground_prob, **kwargs)

/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/stardist/models/base.py in __init__(self, X, Y, n_rays, grid, batch_size, patch_size, length, use_gpu, sample_ind_cache, maxfilter_patch_size, augmenter, foreground_prob)
     93            isinstance(Y, (np.ndarray, tuple, list)):
     94             all(y.ndim==nD and x.ndim==x_ndim and x.shape[:nD]==y.shape for x,y in zip(X,Y)) or _raise("images and masks should have corresponding shapes/dimensions")
---> 95             all(x.shape[:nD]>=patch_size for x in X) or _raise("Some images are too small for given patch_size {patch_size}".format(patch_size=patch_size))
     96
     97         if x_ndim == nD:

/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/csbdeep/utils/utils.py in _raise(e)
     88
     89 def _raise(e):
---> 90     raise e
     91
     92

TypeError: exceptions must derive from BaseException

I have not changed any of the default settings otherwise. Any idea on how to fix this?
Thanks so much!

okay, I have found that it would have prompted out an error message, saying "Some images are too small for given patch_size {patch_size}"
So the bug should be somewhere in block 3, but the error message would have come anyways so I will focus on adjusting my ROIs.
Don't hesitate to correct me if I'm wrong, please - Thanks!

It seems that some of your image/label pairs have different sizes.

I changed the code like this and now my model is finally on its way. Thanks for the support!
2_training: In[14]
# 32 is a good default choice (see 1_data.ipynb)
n_rays = 32

# Use OpenCL-based computations for data generator during training (requires 'gputools')
use_gpu = False and gputools_available()

**# prevent error message, set train_patch_size to < lowest image patch_size
train_patch_size = (128,128)**

# Predict on subsampled grid for increased efficiency and larger field of view
grid = (2,2)

conf = Config2D (
    n_rays       = n_rays,
    grid         = grid,
    use_gpu      = use_gpu,
    n_channel_in = n_channel,
    **train_patch_size = train_patch_size,**
)
print(conf)
vars(conf)

I am not sure whether the bug with the error message still needs to be fixed, but the underlying problem was in my data, so my bad -  thanks anyway!

I am not sure whether the bug with the error message still needs to be fixed, but the underlying problem was in my data

Yes, we should maybe change the error message :)
Thanks for the feedback!

okay, I have found that it would have prompted out an error message, saying "Some images are too small for given patch_size {patch_size}"
So the bug should be somewhere in block 3, but the error message would have come anyways so I will focus on adjusting my ROIs.
Don't hesitate to correct me if I'm wrong, please - Thanks!

Yes. That bug is already fixed in the dev branch and will be included in the next release.


add non root option to pr-merged and to docs

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


change -l argument approach, extract band choice from .tif data itself?

Based on the Issues so far, I believe it is not always clear for the user when to use the
-l , --lcz-band  Band to use from LCZ file (DEFAULT: 0). For maps produced with LCZ Generator, use 1
argument.
Now, files created by the LCZ Generator have long_names as attributes, where the second one is 'lczFilter':
long_name:     ('lcz', 'lczFilter', 'classProbability')
An internal check could be done to see if this long name is present, so that the second band is automatically chosen.
But the -l argument option could be kept, in case someone has a different format of LCZ map ...
Any thoughts on this?

sounds good to me. So not specifying any argument would be your function checking if the tif is from the Generator and then choosing band 1 (we should have a message saying that this was chosen) otherwise still use band 0 as default. Specifying the --lcz-band argument overrides everything? correct?


Title: Adding images in the drum kit

Which pre-existing JavaScript project will you be working on?
Drum Kit
Describe your enhancement/improvement
Adding images on keys
Anything you need to say to the Reviewers
No response
Add any other context or relevant screenshots about the enhancement here.
No response

@Ishani-p7 Thank you for providing your insight but it is not required as of now


Return an actual newest version of the directory latest is not available

Fixes #556
Proposed Changes

The field spec.version is able to set to latest. If the directory latest is not available, return the newest actual version instead.

Thank you @houshengbo Could you please tell me how to use the spec.version locally? It is different from the step with https://github.com/knative/operator/issues/556#issue-856683701 ?

@nak3 Should be no difference.
You can specify latest to spec.version, or any other version, like 0.22, 0.22.0, etc.
If the semantic version is not available, operator will log the error in the CR.

Hmm... In that case, I think this fix still does not work. I tested it but the release label is v0.22.0
$ kubectl get deploy --show-labels
NAME                               READY   UP-TO-DATE   AVAILABLE   AGE   LABELS
activator                          1/1     1            1           12h   serving.knative.dev/release=v0.22.0
autoscaler                         1/1     1            1           12h   serving.knative.dev/release=v0.22.0
  ...

$ kubectl get knativeserving ks -o template="{{.spec.version}}"
latest

upgrade e2e test did not catch this issue as well, so I think upgrade test should be improved.

@nak3 That is what we expected.
If latest is not available, return 0.22 instead for your case.

@nak3 Here is what I did:
I created a dir called latest. I copied all the manifests under 0.19.0 into this directory.
Run the command ko apply -f config.
Everything is launched.
Apply the CR:
apiVersion: v1
kind: Namespace
metadata:
 name: knative-serving
---
apiVersion: operator.knative.dev/v1alpha1
kind: KnativeServing
metadata:
  name: knative-serving
  namespace: knative-serving
spec:
  version: latest

When the CR is ready, check the labels:
NAME               READY   UP-TO-DATE   AVAILABLE   AGE     LABELS
activator          1/1     1            1           6m      serving.knative.dev/release=v0.19.0
autoscaler         1/1     1            1           6m      serving.knative.dev/release=v0.19.0
autoscaler-hpa     1/1     1            1           5m57s   autoscaling.knative.dev/autoscaler-provider=hpa,serving.knative.dev/release=v0.19.0
controller         1/1     1            1           5m59s   serving.knative.dev/release=v0.19.0
istio-webhook      1/1     1            1           5m54s   networking.knative.dev/ingress-provider=istio,serving.knative.dev/release=v0.19.0
networking-istio   1/1     1            1           5m55s   networking.knative.dev/ingress-provider=istio,serving.knative.dev/release=v0.19.0
webhook            1/1     1            1           5m58s   serving.knative.dev/release=v0.19.0

The label is 0.19.0, which means the label matches what I put in the manifests. OK!
Check the CR:
apiVersion: operator.knative.dev/v1alpha1
kind: KnativeServing
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"operator.knative.dev/v1alpha1","kind":"KnativeServing","metadata":{"annotations":{},"name":"knative-serving","namespace":"knative-serving"},"spec":{"version":"latest"}}
  creationTimestamp: "2021-05-13T12:49:09Z"
  finalizers:
  - knativeservings.operator.knative.dev
  generation: 1
  managedFields:
  - apiVersion: operator.knative.dev/v1alpha1
    fieldsType: FieldsV1
    fieldsV1:
      f:metadata:
        f:annotations:
          .: {}
          f:kubectl.kubernetes.io/last-applied-configuration: {}
      f:spec:
        .: {}
        f:version: {}
    manager: kubectl-client-side-apply
    operation: Update
    time: "2021-05-13T12:49:09Z"
  - apiVersion: operator.knative.dev/v1alpha1
    fieldsType: FieldsV1
    fieldsV1:
      f:metadata:
        f:finalizers:
          .: {}
          v:"knativeservings.operator.knative.dev": {}
      f:spec:
        f:cluster-local-gateway: {}
        f:controller-custom-certs:
          .: {}
          f:name: {}
          f:type: {}
        f:knative-ingress-gateway: {}
        f:registry: {}
      f:status:
        .: {}
        f:conditions: {}
        f:manifests: {}
        f:observedGeneration: {}
        f:version: {}
    manager: operator
    operation: Update
    time: "2021-05-13T12:49:21Z"
  name: knative-serving
  namespace: knative-serving
  resourceVersion: "1489581"
  selfLink: /apis/operator.knative.dev/v1alpha1/namespaces/knative-serving/knativeservings/knative-serving
  uid: 5c424b2d-75a0-40ae-977e-59a86f43bd98
spec:
  version: latest
status:
  conditions:
  - lastTransitionTime: "2021-05-13T12:49:21Z"
    status: "True"
    type: DependenciesInstalled
  - lastTransitionTime: "2021-05-13T12:51:41Z"
    status: "True"
    type: DeploymentsAvailable
  - lastTransitionTime: "2021-05-13T12:49:21Z"
    status: "True"
    type: InstallSucceeded
  - lastTransitionTime: "2021-05-13T12:51:41Z"
    status: "True"
    type: Ready
  - lastTransitionTime: "2021-05-13T12:49:09Z"
    status: "True"
    type: VersionMigrationEligible
  manifests:
  - /var/run/ko/knative-serving/latest
  observedGeneration: 1
  version: latest

spec.version is latest and status.version is latest as well. Everything seems ok.

Then, I removed the dir latest. Clean the cluster.
Rebuild the image ko apply -f config.
Everything goes up.
Apply the CR:
apiVersion: v1
kind: Namespace
metadata:
 name: knative-serving
---
apiVersion: operator.knative.dev/v1alpha1
kind: KnativeServing
metadata:
  name: knative-serving
  namespace: knative-serving
spec:
  version: latest

When the CR is ready, check the labels: k get deploy -n knative-serving --show-labels
NAME               READY   UP-TO-DATE   AVAILABLE   AGE   LABELS
activator          1/1     1            1           41s   serving.knative.dev/release=v0.22.0
autoscaler         1/1     1            1           40s   serving.knative.dev/release=v0.22.0
autoscaler-hpa     1/1     1            1           38s   autoscaling.knative.dev/autoscaler-provider=hpa,serving.knative.dev/release=v0.22.0
controller         1/1     1            1           40s   serving.knative.dev/release=v0.22.0
istio-webhook      1/1     1            1           35s   networking.knative.dev/ingress-provider=istio,serving.knative.dev/release=v0.22.1
networking-istio   1/1     1            1           35s   networking.knative.dev/ingress-provider=istio,serving.knative.dev/release=v0.22.1
webhook            1/1     1            1           39s   serving.knative.dev/release=v0.22.0

The newest version is 0.22, so the labels are correct.
Check the CR:
apiVersion: v1
items:
- apiVersion: operator.knative.dev/v1alpha1
  kind: KnativeServing
  metadata:
    annotations:
      kubectl.kubernetes.io/last-applied-configuration: |
        {"apiVersion":"operator.knative.dev/v1alpha1","kind":"KnativeServing","metadata":{"annotations":{},"name":"knative-serving","namespace":"knative-serving"},"spec":{"version":"latest"}}
    creationTimestamp: "2021-05-13T13:03:39Z"
    finalizers:
    - knativeservings.operator.knative.dev
    generation: 1
    managedFields:
    - apiVersion: operator.knative.dev/v1alpha1
      fieldsType: FieldsV1
      fieldsV1:
        f:metadata:
          f:annotations:
            .: {}
            f:kubectl.kubernetes.io/last-applied-configuration: {}
        f:spec:
          .: {}
          f:version: {}
      manager: kubectl-client-side-apply
      operation: Update
      time: "2021-05-13T13:03:39Z"
    - apiVersion: operator.knative.dev/v1alpha1
      fieldsType: FieldsV1
      fieldsV1:
        f:metadata:
          f:finalizers:
            .: {}
            v:"knativeservings.operator.knative.dev": {}
        f:spec:
          f:cluster-local-gateway: {}
          f:controller-custom-certs:
            .: {}
            f:name: {}
            f:type: {}
          f:knative-ingress-gateway: {}
          f:registry: {}
        f:status:
          .: {}
          f:conditions: {}
          f:manifests: {}
          f:observedGeneration: {}
          f:version: {}
      manager: operator
      operation: Update
      time: "2021-05-13T13:03:51Z"
    name: knative-serving
    namespace: knative-serving
    resourceVersion: "1497356"
    selfLink: /apis/operator.knative.dev/v1alpha1/namespaces/knative-serving/knativeservings/knative-serving
    uid: a2431493-fdd3-4803-a3d8-c41c5d64dd0a
  spec:
    version: latest
  status:
    conditions:
    - lastTransitionTime: "2021-05-13T13:03:51Z"
      status: "True"
      type: DependenciesInstalled
    - lastTransitionTime: "2021-05-13T13:04:21Z"
      status: "True"
      type: DeploymentsAvailable
    - lastTransitionTime: "2021-05-13T13:03:51Z"
      status: "True"
      type: InstallSucceeded
    - lastTransitionTime: "2021-05-13T13:04:21Z"
      status: "True"
      type: Ready
    - lastTransitionTime: "2021-05-13T13:03:39Z"
      status: "True"
      type: VersionMigrationEligible
    manifests:
    - /var/run/ko/knative-serving/0.22.0
    observedGeneration: 1
    version: 0.22.0
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""

spec.version is latest, status.version is 0.22.0.
They seems correct.

Thank you. Okay, I understand the "rule". When spec.version: latest is used for serving, latest directory must be created in cmd/operator/kodata/ingress as well. Then it worked.

Ingresses need to be in sync with the knative serving structure all the time.
There is no validation for ingress only. The validation is for knative serving. So any version working with knative serving must match the version for ingresses.

@nak3 I can add some logic into this function
func getIngress(version string, manifest *mf.Manifest) error, to check if the version is a valid semantic version, before running semver.MajorMinor(common.SanitizeSemver(version))[1:].

That's also good but I mean that current upgrade test prints all "Passed" even though operator keeps causing go panic. It could be a upgrade test bug. We can not fix it?

@nak3 I have no idea why prow does not catch the panic :-(
What I can do with operator is to avoid the panic in golang code as much as possible.

/approve

/approve


Feature Roadmap Proposal - Onchain Buster 2.0

Describe the solution you'd like
Feature Requests
Support non-EVM blockchain
Onchain Buster brings a lot of values to the onchain users on ETH, it give insights to normal users to understand their onchain behaviour. However, right now, it only supports Ethereum and L2 rollups. My suggestion is to expand the functionalities to blockchain outside of ETH-ecosystem.

[ ] Solana: One of the biggest memecoin ecosystem in the blockchain space. And with that obvious demand, Solana wallet users definitely find Onchain Buster useful to track their efficiency in meme trading and onchain activity tracking.
[ ] Polkadot: Niche market, not too many consumer apps. If we build on Polkadot, we can easily raise for the funding.

Progressive Web App
Great way to convert the app to reach mobile Web3.0 users (which is huge). Tried apps like POAP and Devcon Passport (PWAs) and the experience with PWA right now is very seamless.
Personalization
Currently, sign in with wallet does not bring any additional features (aside from minting). This is will be more useful if we can provide a feature to index and analyze insights for the signed-in wallet automatically. Does not need to ask them to input their own wallet to see the data. Similar to apps like CoinStats or Zapper.

[ ] Minting to the signed-in wallet
[ ] Automatically fetch and store data of the signed-in wallet.

Smart Portfolio

I analyzed the features and UX of current portfolio-only apps in the market and the best apps I can find is CoinStats. However, it is still not what I truly need for a real smart portfolio app. If we can make something similar to Zapper (Multichain) + SonarWatch (Solana only), that would be awesome:

[ ] Not only tracking token transfer transactions, app also need to track the money flow through Dapps (DeFi protocol transactions like swapping, staking - this is solved by SonarWatch)
[ ] Simpler UX. Coinstats is great but too many redundant features.

Current Issues

[ ] Not mobile friendly.
[ ] Frequent issues with RPC calls: rate limits - Considering switching from thirdparty services to native WS requests.

Revenue model
Describe alternatives you've considered.
No response

Hi Tin,
The proposal is great. Just want to add one possible technical improvement related to RPC call optimization.
Currently, we're using fully 3rd party APIs to get the data (Etherscan, Alchemy, Reservoir,...). To go with fully self-sovereign in data control, we can consider running a node in our targeted chain and consume the raw data (like explorer).
Adapted from Devcon 7 speech, here's a really nice talk including a hands-on demo on what we're looking at: https://youtu.be/bKrnOnfx9io?si=EzZ5IwxndU8Yfx0w
TL:DR: We can leverage the open-source paradigmxyz/cryo to do the data extraction, then use DuckDB or Polars to in-memory process the data (transform, mutate,...) - which I strongly believe can optimize the procedure call a lot.
However, keep in mind that Data Sovereignty is OPOE (Only Possible on Ethereum) - as mentioned in the speech. It could be both challenge but our innovation to push toward non-EVM support to aggregate the data from multi-chain

I agree that we should include rich, culturally significant non-EVM chains like Solana.
My thought for this proposal is that these arguments seem to assume we should build something near to a smart portfolio. Should this be the direction to explore further, given that there are already many established solutions (Zapper, CoinStats, DeBank)? Some of these platforms only need to integrate non-EVM chains and aggregate DeFi data to reclaim their competitive edge compared to our product.
In my belief, another area that remains a 'blue ocean' is the social graph and human connection aspect. For example: identifying & matching people with similar interactions with DeFi protocols or active on similar blockchains, flagging a potentially scam project and notifying my 0xcircle, analyzing the majority behaviors within an NFT community, etc.
In this case then, the question would be: How to make these social aspects 'actionable' so that users would join in, take some actions within the app.
As for the business model, a premium package seems the most viable option at the moment. Alternatively, we could charge a one-time fee for specific features (like Warpcast has 5$ fee for account creation).
Thank you for the proposal, bro.

One possible feature that I think we can do is Tinder-like profile matching feature. :)

One possible feature that I think we can do is Tinder-like profile matching feature. :)

Have thought ab this too, but it should be designed in a 'safe' way for anonymous folks to match with one another.

In fact there are a lot of room for improvements. The point is we have to identify the key features we want to build. So would be great to keep this conversation going.


Unedit nodes early when closing scene tab

Same error as in #80609 also affects GridMap and probably other node-based editors. The reason is that when scene was closed, the editor selection was cleared in a deferred manner, so by the time editors received edit(nullptr) to unedit node, the node was already freed.
This PR ensures that the editors can properly unedit nodes before they are freed.
#80610 is not needed anymore after this change.

Thanks!


Why not just forEach?

https://github.com/Foso/compose-snake-web/blob/01ca6c59492fbf52e3f9b21eced28bf501d6736e/src/commonMain/kotlin/de.jensklingenberg.composesnake/Utils.kt#L3

Hi, good question. I got the code from https://github.com/arkivanov/CompoSnake/blob/main/src/main/kotlin/com/arkivanov/composnake/Utils.kt and haven't changed much on the logic part. I think forEach should work fine

Just tried it. It's working fine. I removed forEachFast

forEachFast does not allocate the iterator for each iteration, this is the only benefit.

But is fast only for arrays and array list, and even for them, I don't
really think it is faster than the classic implementation.
czw., 3 cze 2021 o 02:17 Arkadii Ivanov @.***>
napisał(a):

forEachFast does not allocate the iterator for each iteration, this is
the only benefit.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Foso/compose-snake-web/issues/5#issuecomment-853464573,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABUIRY6SNXOPYBJYMJTZYXLTQ3C23ANCNFSM456GVCEA
.

The time complexity is sti O(N), it just doesn't allocate anything. This is specifically important with nested iteration:
a.forEach {
    b.forEach {
        c.forEach {
        }
    }
}

Space complexity of the sample above is O(Na * Nb + Na), whereas forEachFast would have O(1) space.


syntax to add string mac address aspart of the topic

hi
I would like to add the mac address of a node and include it inthe topic. for example I would like to get the mac address of each node with the function WiFi.macAddress() and use this in the topic like (home/"the macc add returned from WiFi.macAddress()"/).
would you please help me with this?
Best regards

Hi,
I want to avoid this issue list become a general support forum for standard arduino programming topics - they are many better suited forum available, such as Stack Overflow, for general questions like this. I hope you understand.
Nick


syntax error  on right json string

I've been trying to implement this solution and I have been  getting the same  error:
terminate called after throwing an instance of 'nlohmann::detail::parse_error'
  what():  [json.exception.parse_error.101] parse error at 97: syntax error - unexpected '}'; expected string literal

My code:

  auto s =  create_json_config(); // return content from file jsonstr.txt
   cout<<s;
   json uuid;

   uuid.parse(s);
    if (uuid.is_object())
    {
        auto obj = uuid.get<json::object_t>();
        for (auto& kvp : obj)
        {
            std::cout << kvp.first << ":" << kvp.second << "\n";
        }
    }

jsonstr.txt

From your jsonstr.txt: Your JSON contains an invalid , at the end of object:
{
"index":4,
"frequency":8,
"frame_index":2100,
"displace":256,
},

Here the , after 256 is invalid JSON.

@pboettch is right, and the error message hints at this: after the comma, an object key (i.e., a string literal) is expected. You can verify that jsonstr.txt is invalid by using, e.g., https://jsonlint.com.


add checkpoint_dir arguments to fix multi-user save error

when multiuser save the file in /tmp, the file that created by user A can't be changed by user B.

Thank you, @junxnone, for your contribution. This PR has been superseded by https://github.com/tensorflow/hub/pull/311 and can safely be closed.


Where to get this "postman/api/id"?

Hi,
i have installed both frontend and backend Postman plugins. Added PostmanCard component inside EntityLayout. And i have published a api in postman. Added workspace id and api id (from info button in postman app) inside yaml file. Added apikey and baseurl in app-config as well. Still iam getting "Request failed with status code 400". Is there any issue with postman/api/id. How to get this postman/api/id from postman ?
Thanks in advance

Hi @VasKumarSel  - you should be able to get the API ID from the information section in the API view. Here is an example:

If you are still experiencing the same issue after using this ID, could you share your Postman team domain, which you can find at https://go.postman.co/settings/team/general? I will have a look for you.

Hi @aphanor Please find the team domain and a sample request which is failing even with correct api id. Kindly check and let me know if you need any.
Team domain: planetary-star-547941-7213
This image shows api id from info button.

I am using the same in my yaml file. Still iam getting the 400 bad request.
//API information in yaml file
apiVersion: backstage.io/v1alpha1
kind: API
metadata:
name: claimsdsd-form-v1.0
postman/workspace/id: 3552e2c2-f147-4da3-8073-7400a69aa191
postman/api/id: 39807572-0280884e-c568-4887-90f4-f5776072cd2f
//
Request details
http://localhost:7007/api/postman/apis/39807572-0280884e-c568-4887-90f4-f5776072cd2f
Request Method: GET
Status Code: 400 Bad Request
Response:
{"error":"Request failed with status code 400","status":400}

Hi @VasKumarSel - I think the term "API" might have caused some confusion. Let me clarify:
API View in Backstage
Postman has a feature called APIs, which allows you to create an API and sync the API definition to its collection. This Postman backstage plugin allows you to display your API content (name, API versions and collections) stored in the APIs tab and visualise it directly within Backstage. Here is an example:
My API in Postman:

My API information in yaml file:
apiVersion: backstage.io/v1alpha1
kind: API
metadata:
  name: users-api
  title: Users API
  description: "My Users API."
  postman/domain: "MY_TEAM_DOMAIN"
  postman/api/id: "3fc0bfef-c6e0-45da-ab65-9486fec8a478"
  # others options

API View in Backstage:

Collections
If you have standalone collections stored in the Collections tab, you can also retrieve the collection ID and configure it in your project like this:
Collection in Postman:

Collection configuration in my yaml file:
# https://backstage.io/docs/features/software-catalog/descriptor-format#kind-api
apiVersion: backstage.io/v1alpha1
kind: API
metadata:
  name: nova-security-api
  title: NOVA Security API
  description: "This API to a collection in Postman."
  postman/collections/ids: ["23451556-d2e6df12-de0c-405f-bb68-7376545eb34f"]

Collection view in my Backstage catalogue:

To finish, I would recommend checking your postman configuration in your app-config.yaml file. It should look as follows:
postman:
  baseUrl: https://api.postman.com/
  apiKey: POSTMAN_API_KEY

Hi @aphanor
I have made the changes. Now i am able to view the both API and Collections. But in API view, i am not able to see the list under the collections. Only Name, Description and View in Postman (able to navigate to postman web) is showing. Find below image for the reference.

This is the sample metadata for the above image.
apiVersion: backstage.io/v1alpha1
kind: API
metadata:
name: claim-form-v1.0
postman/workspace/id: 3552e2c2-f147-4da3-8073-7400a69aa191
postman/domain: "planetary-star-547941-7213"
postman/api/id: fd1b1e5b-bf91-4240-a9a9-81f5c13c1169
Anything is missing in postmancontext. I can see the API View component in postman card. It is looking for _collections. I am not sure about how to debug the postmancontext in backstage. I just manually checked the processPostmanMetadata function and got the json. Added json below. Could you please help me why the collections is not being rendered.
{
"postman": {
"workspace": {
"id": "3552e2c2-f147-4da3-8073-7400a69aa191"
},
"domain": "planetary-star-547941-7213",
"api": {
"id": "fd1b1e5b-bf91-4240-a9a9-81f5c13c1169"
},
"collection": {
"ids": [
"39807572-a86e67fe-4654-4097-b657-dafa19820233"
]
}
},
"goUrl": "go.postman.co"
}

Hi @aphanor Can you let me know how to resolve the above case?
Thanks in advance.

Hi @VasKumarSel - I apologise for the delay. Does your Test API have one or multiple collections? If so, the plugin will only display the API collections if you publish a version of your API. When you publish a version, it will display the version and the collection associated with that version.
To publish an API, you can follow these steps:

In your workspace, click on the APIs tab in the sidebar.
Select the API you want to edit.
Make sure your API has a collection. If it doesn't, you can generate a collection from your API definition.
Once the API collection is generated, on the main API page, click on the Publish button.

Once published, you will be able to display the API collection(s) in the API view. You can also add a description to your API so that it's also included in the API view in Backstage.

Hi @aphanor Thanks. Working with published collections.

 If you want to display your APIs or collections without having to hardcode their values in your yaml  files, please check out our Entity Provider: https://github.com/postman-solutions-eng/backstage-postman-plugin?tab=readme-ov-file#configuring-the-postman-entity-provider-optional


请问unified hyperparameter和searched hyperparameter有什么区别呢

如题

请参考文章附录E中的相关讨论：

To ensure a fair comparison between models, we conducted experiments using unified parameters and reported results in the main text, including aligning all the input lengths, batch sizes, and training epochs in all experiments.

In addition, considering that the reported results in different papers are mostly obtained through hyperparameter search, we provide the experiment results with the full version of the parameter search.


Icon index as class constants

Provides index of all available icons as class constans, so it can be used by IDE as hints in php code, i.e. in Filament panels

While I do think this is cool I'm not sure I want to take this on in the library itself. These constants would be re-generated on each icon update and while a renamed icon isn't a breaking change, a renamed constant is. So I'm going to pass on this. But want to thank you for your proposal 👍

I understand your concern, I'm new to Laravel and blade templates, and I don't know how often things get renamed and how (like are there aliases to old name and deprecation notices?) In my understanding, if icon get renamed and old name is not available, things breaks anyway. On my first try I got a typo in icon name and got error page instead of working panel with one missing icon

Hence the idea of an index, missing constant is easily detected by IDE or static analyzers, while typo in some string is harder to spot on.


Netlify deploy preview failing.

This is a...

[ ] Feature Request
[X] Bug Report

Problem:
Netlify deploy previw fails. It's failing on master as well.
Error
Liquid Exception: persistent-volume is not a valid glossary term id. Please see ./_data/glossary/* for the complete list. in docs/reference/glossary.md

Proposed Solution:
Fix this as soon as possible high priority.
Cc @zacharysarah @steveperry-53 .

Fixed.


Recursively unwrap values in arrays

This was in server_db but I forgot to put it in embedded_db

Coverage decreased (-0.02%) to 95.72% when pulling f201630c50b6fa7dd2ec3bdaf665cbedd52d1aed on embedded_array_unwrap into 83b1be2a1f8d65b5100080f61852d30be8757d76 on master.

Coverage decreased (-0.02%) to 95.72% when pulling 60bc8201fe8d4331b68e9c22cb20a43d851c6f46 on embedded_array_unwrap into 83b1be2a1f8d65b5100080f61852d30be8757d76 on master.

Coverage decreased (-0.02%) to 95.72% when pulling 608f08356ab26dbd5e05961f3be90695aaf8ed83 on embedded_array_unwrap into 83b1be2a1f8d65b5100080f61852d30be8757d76 on master.


Does the Azure DMS online migration support schema changes?

Hi! After reviewing the documentation for Postgres logical streaming replicas, I've found the WAL based replication supports DDL operations, including table creation and column changes. When reviewing the DMS documentation, I saw that there are required steps to transfer the DB schema from the old database to the new database. Is this a required step, and will Azure DMS handle schema changes that occur during the live migration? I'll test this out with Azure DMS while waiting a response, if it's not known.

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

ID: f233fef5-5db2-8444-22ab-92045e36b119
Version Independent ID: c243f2b3-febe-22aa-03de-0fa068fb7243
Content: FAQ - Azure Database Migration Service
Content Source: articles/dms/faq.yml
Service: dms
GitHub Login: @croblesm
Microsoft Alias: roblescarlos

jordansafer We are looking into this and will get back shortly.

Hi @Oury-MSFT, please contact Aditya Duvuri for this issue? Unfortunately, I don't have his GitHub user.


Using FBP with modular beam that is close to a cone beam geometry

I am trying to simulate a CT scanner where there are many tangential flat modules arranged in a curve. The geometry is very close to an ideal cone beam geometry. To do this, I repeat each source position num_modules times, so that numAngles = number of views * number of modules. This works fine with, for example, SART and RWLS, and the FORBILD example is reconstructed well, with the expected slight module boundary ring artifacts. But an FBP call with the same geometry produces something close to a constant value in the FOV, with no detail at all. There are no warnings or errors reported. Is this expected behavior? I guess rebinning as in d09_curved_polygon_detector_array.py is the preferred approach.

@jsmaltz It looks like my posting  #114 issue, please check your FBP call goes into modularBeamBackprojectorKernel_eSF() function rather than modularBeamBackprojectorKernel_SF(). If it is, then this is related to my posting issue(#114).

@hws203 please don't suggest that people use your suggestion from issue #114 .  If this worked for you, you got lucky.  One cannot replace the extended SF projectors for the regular ones.  This could lead to some big errors.
@jsmaltz, note that FBP reconstruction cannot be applied to any geometry.  Only some geometries defined as modular-beam will work.  LEAP should have printed an error message.  I'll see if I can work on this.
You are correct in that if you want to use FBP in your case, you should do what is outlined in d09_curved_polygon_detector_array.py.

@kylechampley I added to some more comments not to use  my temp solution to #114.

Has this issue been resolved?  If so, I'd like to close this issue.

Yes, please close thanks.


Go back to CommonJS modules for now...

...until https://phabricator.babeljs.io/T2817 is resolved.
First crack at the conversion, not entirely sure if this works but I'll verify tomorrow.

Fixes #213

@gaearon Could this be looked at? :)
@kevana Tests doesn't need to change, do they?

@SimenB I don't think it needs any test changes, module behavior should be the same as before. I did add exports.spec.js as a sanity check for exports. I dropped this version into my apps and didn't see any issues but I'm still not completely confident that I got the default and named exports correct.

Thanks, but I think I won't support DevTools on IE8.
Even Microsoft ends support for IE < 11 tomorrow.
You can use something like es3ify as a global transformation on your project if you need it.

I understand completely, it's an easy fix with webpack. Hopefully the really long tail of IE8 traffic starts dying a bit faster...

IE8 will still be supported in enterprise, so my project is stuck with it for now...
In this case we can just use es3ify though, so no real problem. As long as no getters are used, I'm happy :smile:

Microsoft is not going to support it for anybody, not even enterprise customers. If some enterprises still decide to use unsupported version without security fixes at this point it's their problem.

The security fixes are their problem but the lost revenue is my problem. It's hard for me to make a business case for dropping support when a material percentage of our customers still use it. Hopefully this pushes the stragglers to finally upgrade.

It's a pain for library authors and it's gotta go at some point. I understand your concerns but JS libraries are going this way now that MS doesn't support it, and at this point the only solution we can offer is transpile to ES3 by yourself or use older versions of the tools. Cheers.


Template fetching fallback

Changes

If a call to convenience.getTemplates fails, the node will now fall back to fetching individual templates using airnode.getTemplate() (in parallel)
I've exported the new fetchTemplate function since it seems pretty useful as is
Added some explanation comments to the constants.ts file

Addresses
https://github.com/api3dao/airnode/issues/64 although there are other areas where the node should fallback to individual calls. I'm going to add a checklist to the Github issue and leave it open

My main complaint is that updating the values at constants.ts either breaks things or results in unexpected outcomes. This PR is not about constants.ts so you can merge it. It's just that the added comments brought it to my attention as an issue.


go through SOGPF changelog and confirm new assets were added

https://community.sogpf.com/d/4-official-dlc-changelog
https://wiki.sogpf.com/index.php/Category:Assets
Better respawn vehicle, maybe m113 medical

Missing some aircraft because I am unsure about how many are needed.

Thank you for bringing this up, I didn't realize truly how many small arms were missing from the arsenal preset. The list of available guns is about to double.


Delayed-like functionality

There are some cases where it would be useful to have a way of setting up a parallel map over inputs, then calling compute on it later - like Dask Delayed.
In particular this would be needed to support xarray's open_mfdataset (see https://github.com/pydata/xarray/pull/7811), or creating Kerchunk files in parallel.
The main question is what this looks like and where it belongs.

Here's a basic proof of concept: https://github.com/tomwhite/cubed/commit/5f6e38e8e790a05298ca9b7ee89a55e7b7e9edfd


Enhancement: Healthbar Colors

YoshMan, Why do you not making a options from healthbar colors and the old healthbars from green color?

yoshi said that he would not like to add health bar colors a while back, you can implement them in your mod if you want them that badly.

There is an official mod for this on the official Discord server.

Won't be added in, but theres a script for it in the CNE Discord Server is you want to get it

Won't be added in, but theres a script for it in the CNE Discord Server is you want to get it

but it wasted my space when i put all of these scripts

Won't be added in, but theres a script for it in the CNE Discord Server is you want to get it

ok, but also, why you didn't updating this engine yet


Any API / can we unload the .so library?

Is there any support / API to unload the .so, like dlclose() ?

That's not something we plan to support. It's a very unsafe API and we would have no way of ensuring that no code gets called in the shared library once it has been unmapped.

Thanks for letting us know.


Change pressure to Inches

How would you change the pressure to inches of mercury?

I have pushed a new version [0.1.5] (https://github.com/liu044100/SmileTouchID/releases/tag/0.1.5) to cocoapods, that give the SmileWeatherCurrentData a new property pressure_mercuryInch.
SmileWeatherData *data = ...
data.currentData.pressure_mercuryInch = ...

/BuildRoot/Library/Caches/com.apple.xbs/Sources/ProtocolBuffer_Sim/ProtocolBuffer-242/Runtime/PBRequester.m:807 server (https://gsp13-cn.ls.apple.com/localshift) returned error: 500
2015-12-02 09:03:27.913 Smile Weather[5496:40623] error -> The operation couldn’t be completed. (kCLErrorDomain error 2.)

Hello, @Zero-zhou, could you give me more detail or a example project?

@liu044100  I'm sorry, there has been no attention. This problem has been solved,Thank you。


finer-grained rsync control

I am working with a project at the moment that writes a couple of files from templates when it boots up. Because these files are written inside the directory structure that is being rsynced over, when I make any change to a file in that directory in my host I find these generated files are deleted by rsync. This is due to the --delete flag being set here:
https://github.com/brikis98/docker-osx-dev/blob/master/src/docker-osx-dev#L51
I have tested running docker-osx-dev with that flag removed, and my generated files are then persisted during the rsync cycle.
I am trying to envision some sort of per-path rsync configuration that would allow me and other users to special-case the rsync flags to deal with this sort of idiosyncrasy. Has there been any discussion around this sort of thing in the past?
Perhaps some sort of .docker-osx-dev or .rsync file that if found in a synced directory was used instead of the default options?
--archive --log-format 'Syncing %n: %i' --omit-dir-times --inplace --whole-file

Is there a more elegant way of doing this?

Good question. I'm not sure of the best way to handle this case. You typically want the --delete flag to ensure the remote directory is truly in sync, especially after file deletes, but that does conflict with code generation. Usually, generated files are stored in a non-source directory, so you can just add them to the ignore flags in docker-osx-dev (run docker-osx-dev -h to see all supported flags). Are your files being generated into the exact same folder as normal source files? Is there any sort of file name pattern you could rely on for ignoring them?

It looks like explicitly --includeing all my non-generated source files and then --excludeing * in that directory gives me the behaviour I want from rsync. I've patched the .dockerignore parsing so it understands the ! prefix syntax.


Removed pose topic from LogRecord

Signed-off-by: Jenn Nguyen<EMAIL_ADDRESS>
🦟 Bug fix
Fixes https://github.com/ignitionrobotics/ign-gazebo/issues/753
Summary
With changes from #742 , pose information was being logged twice (in the dynamic_pose/info and changed_state topics). This PR removes the recording dynamic_pose/info topic from LogRecord and updates the integration test.
LogPlayback still uses pose messages for backward compatibility (i.e., users have log files before #742 changes) but should probably be removed when ported to Fortress.
Checklist

[X] Signed all commits for DCO
[X] Added tests
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[x] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge

Could we please get a Changelog and Migration entry for this effect?

How's this a3438b62b7f9643ce33ae96e1540b4eb02dfb82d?

How's this a3438b6?

I think is fine, thanks @jennuine . If I understand correctly, anyone using the old topic should just change to changed_state. Is this correct?

If I understand correctly, anyone using the old topic should just change to changed_state. Is this correct?

Correct.

Probably unrelated to this PR, but if I run make INTEGRATION_log_system , the result is ... Is this a known problem?

The failure is coming from LogSystemTest.LogPlaybackStatistics which this PR doesn't affect (does not change playback only changes record) and is the first time I've seen this error. Also, that test is the first test in log_system.cc which leads me to think maybe there's something different with your setup?

Probably unrelated to this PR, but if I run make INTEGRATION_log_system , the result is ... Is this a known problem?

There doesn't seem to be any history of it in the ign-gazebo4 builds that I saw.

Hold off on merging until get a confirm from @nkoenig

Please don't merge this until after July 8th.

I'm not sure about changing the contents of the logs in a stable release, downstream users may be counting on this topic. Can this be targeted at Fortress?

Can this be targeted at Fortress?

I believe so, what do you think @nkoenig?

Retargeting to Fortress and will be removing pose from LogPlayback

The new recorded state.tlog file is from rolling_shapes.sdf but with only the sphere and ground plane models so that the log file would be relatively small.

c7c943c7c9cb32097aa02e250d3f624b7b62b6ab Left a comment to not re-record state.tlog file with -r flag and to pause sim before terminating. Previously, I had done this and it resulted in strange pose behavior. The log file was 5.7s long and in the LogSystemTest.LogControl test, after seeking to 5s (close to the end but not exactly), x = -74 then after rewinding and calling server.Run for 2 iterations x = -75. If it was 3 iterations then the pose would be the expected initial pose x=0. When I re-recorded the log without -r, started/unpaused the sim manually, and made sure the program was paused before terminating everything worked as expected.

All changes looks good to me. I've merged the latest state of the branch and restart the Windows build to get fresh CI. Seems to be a flaky test in github actions.
If Windows build ends nicely, consider this approved. Nice work Jenn.

If Windows build ends nicely, consider this approved

Windows didn't end nicely :( but looking through other merged PRs similar tests failed for windows as well (including LogSystemTest)

Windows didn't end nicely :( but looking through other merged PRs similar tests failed for windows as well (including LogSystemTest)

Oh, "nicely" in the context of Windows meant "compilation is ok" since we did not fix the failing tests yet.


MQTT restart

Hi,
Sometimes my device becomes unresponsive via mqtt command. I haven't yet worked out if its due to the device or the server.
I have to restart the esp device to get it to respond again. Is there a way to restart the connection without restarting device and automatically too?
Running the latest dev build.
Also when I restart my device it sends a message by mqtt to say the door has been opened by the push button. Is there a way to disable this message being sent, or change the message to say device has restarted.

hello @timknowlden are you only sending MQTT commands and then it stops responding or are you also using the Web UI?
If MQTT only, which messages are you sending?

It's only mqtt commands that it is not working with.
The Web ui is still functional and that is how I'm restarting the device

Can you share a log of calls that you are sending/receiving from the esp-rfid, so that I can try reproducing? Or some steps that you take that reproduce the problem. I have a very stable system with MQTT (mostly sending from esp-rfid)

I am using home assistant to issue commands via mosquito broker, the log will be flooded with messages to and from other devices. It can last for days on end before becoming unresponsive.
If the message on restart was not that the door was operated then I could set the device to restart daily?

Yes @timknowlden that's what I would do! You can setup the autorestart from here:

You can also set a custom time, if 24h are too much.
I'm going to close this for now, but reopen if this is not good enough. Unfortunately there's only so much we can do from esp-rfid to mitigate these type of issues.


Discord invite link is expired

Clicking on the link in the readme leads to an expired link.

Thanks for reporting. Sorry about that. Please try now.


feat(dsb-client-gateway-api): ecdh basics

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


IAM: missing CreateDate from get_group response

Closes https://github.com/getmoto/moto/issues/6320

@bpandola @bblommers ready for review


Ship Particle Weapons Double Dip Damage Perks

Ship particle weapons are benefiting from the Energy Weapon Systems and Particle Beam Weapon Systems perks. They should only benefit from the latter. Solution; Remove SpaceshipEnergyWeapon [KYWD:0002226A]

Details
0022ec51,
0022ec52,
0022ec57,
0022ec58,
0022ec5e,
0022ec5f,
0000424c,
0016ad51,
0022ec41,
0022ec42,
0022ec46,
0022ec47,
0022ec4b,
0022ec4c
Game Version
<IP_ADDRESS>
Language
English (EN)
New Game
Yes
Reproduction Steps
Load up xedit and check keywords for said weapons.

This does appear to be intended as this only happens with "Electron/Proton" Beam weapons; keep in mind particle turrets also get a double perk buff from eg Particle Weapons and Automated Weapons.

Unless I'm mistaken, the most recent patch worked in a change to buff all the other electron/proton weapons in this way. But yeah, removing these energy tags is a different way to achieve consistency. Unless we hear from a dev, I couldn't actually pick a side for which is correct.

The specific EM weapons that benefit from both perks are "disruptor" weapons that are only made by a Ballistics-heavy manufacturer.  Some o fthese were properly set to beneft from laser and particle by default, and Ship Fixes made all of them consistent.
Note that this is not ALL EM weapons.
From the creator of Ship FIxes:
There are 187 references in the Starfield.esm file to the EMP-80 Suppressor.   At a quick glance, almost all of them appear to be ships of some sort.  This is one of several reasons why I believe it was the game designer's intention that the EMP Suppressor weapons are supposed to inflict hull and shield damage in addition to EM damage, because the primary use of EM weapons is to board ships, and NPC ships cannot engage in boarding which negates most of an EM weapon's usefulness.   I believe that the game designers gave EM weapons to NPC ships so that we the players can experience something of what it is like to be targeted by an EM weapon, but then gave the weapons hull/shield damage as well, because otherwise the NPC ships would be severely under-powered in ship combat.  This also follows what I found in the records themselves where there are AMMO/PROJ/EXPL records specifically for the EMP Suppressor weapons to make them different than the other EM weapons.
Also from him:
I wrote a small novel with my set of fixes explaining the reasoning behind the fixes.  While I agree that an EM weapon inflicting hull/shield damage seems odd, when I was looking through the details of the records for the EMP Suppressor weapons it looked like the game designers had actually intended the EMP Supressor weapons to be different than the other EM weapons.  So in line with the overall objective of the patch - namely to correctly implement what appears to have been the intention of the game designers - I made all the EMP Supressor weapons consistent with what appeared to be the original intent.    Just load the patch-of-the-patch after the main ESM files.

This one falls into the wheelhouse of balancing changes, which we generally don't touch.


Roll Flutter Engine from 8389ad914b21 to 5d022fdb68ca (2 revisions)

https://github.com/flutter/engine/compare/8389ad914b21...5d022fdb68ca
2023-09-11<EMAIL_ADDRESS>Pipe VMA asserts to FML. (flutter/engine#45661)
2023-09-11<EMAIL_ADDRESS>Roll Skia from e6225224fb4e to 0b8d2203ab35 (9 revisions) (flutter/engine#45671)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


Next.js App Router

Next.js's App Router is stable as of Aug 2023. This PR removes the existing Pitfalls section warning that App Router is in beta.
https://nextjs.org/blog/next-13-4

duplicate of #6005

Ah


How implement Method Override?

Hi, how to override polka method? This is useful for method spoof like this https://laravel.com/docs/9.x/routing#form-method-spoofing.
I tried to implement this behavior on polka but not works as expected.
For example I have route
polka().put("/user/:id", (req)=>{
...
})

I want to to access this route via form using POST method and include body: _method = "PUT".
I try to use express middleware method-override before declaring polka routes. This middleware override successfully the req.method value. But polka PUT router not triggered. It's still routed to POST. Is I missing something here?

@lukeed just want to confirm. Should I override req.method just before this line excecuted? Is this the only way?

Hello @lukeed. I ended up to override polka parse to support method override. For others that looking this issue, this is my working code
const originalParser = polka.parse;
polka.parse = (req) => {
      const parsedReq = originalParser(req);

      // just return parsed request if method is get
      if (req.method?.toLocaleLowerCase() == "get") return parsedReq;

      // handle method override if provided by client.
      if (parsedReq.query?._method) {
        req.method = (parsedReq.query._method as string).toUpperCase();
      }
      return parsedReq;
};


FYI Cats Effect Implementation

I took your implementation and added Cats Effect for my own exploration to compare the implementations and implications. You can view them at the repository I have forked from yours.

I just looked into it, the stream usage is an interesting idea, right now, I'm not willing to merge such code but I'm not discarding it in the future.
Thanks!


fix(NOJIRA-123): trigger ci-standard-checks on draft->ready PR transition

Since additionalChecks was implemented in ci-standard-checks, some checks only run on PRs that are marked as "Ready for review" and are ignored on Draft PRs.
This means that for PRs that are opened in Draft and then marked as Ready for review without adding any new commits, CI Standard Checks will never execute additionalChecks.
This PR adds the ready_for_review PR event type to the CI Standard Checks workflow template.

Really nice catch @trapped !


Parameter 'cookbook' doesn't work

Hello guys,
I'm using your cookbook for a long time, and now I noticed one issue:
"NoMethodError
undefined method `cookbook' for Custom resource logrotate_app from cookbook logrotate
Cookbook Trace:
/tmp/chef-solo/cookbooks/logrotate-scup/recipes/default.rb:30:in block in from_file'   /tmp/chef-solo/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/resource_builder.rb:90:in instance_eval'
/tmp/chef-solo/cookbooks/compat_resource/files/lib/chef_compat/monkeypatches/chef/resource_builder.rb:90:in build'   /tmp/chef-solo/cookbooks/logrotate-scup/recipes/default.rb:29:in from_file'
Relevant File Content:
/tmp/chef-solo/cookbooks/logrotate-scup/recipes/default.rb:
23:
24:  if node[:logrotate_scup][:sudo_enabled]
25:    include_recipe "logrotate-scup::sudo_options"
26:  else
27:
28:    if node[:logrotate_scup][:app][:name] == "plataforma"
29:      logrotate_app node['logrotate_scup']['app']['name'] do
30>>       cookbook  'logrotate'
31:        path      node['logrotate_scup']['app']['path']
32:        frequency node['logrotate_scup']['app']['frequency']
33:        rotate    node['logrotate_scup']['app']['rotate']
34:        create    node['logrotate_scup']['app']['create']
35:      end
36:    end
37:
38:    if node[:logrotate_scup][:app][:name] != "plataforma"
39:      logrotate_app node['logrotate_scup']['app']['name'] do
"
I created one cookbook that I'm using by interface, my parameters are:
logrotate_app node['logrotate_scup']['app']['name'] do
cookbook  'logrotate'
path      node['logrotate_scup']['app']['path']
frequency node['logrotate_scup']['app']['frequency']
rotate    node['logrotate_scup']['app']['rotate']
create    node['logrotate_scup']['app']['create']
size      node['logrotate_scup']['app']['size']
end
The tag v1.7.0 still works well, but code of master branch has this issue.

Apologies this broke you, this was an intentional change in the 2.0 refactor.  Are you always calling cookbook with the argument logrotate?  If so, you can likely remove the cookbook attribute from the call sites.  If you are supplying custom templates in some cases, would you mind sharing your use cases so that we could see if we can support them in this cookbook via some other means?  I'd prefer not to allow users to set their own template because it means we are always tied to maintaining the representation of data we pass to the template resource.

all the examples in the README use it.

@TD-4242 Updated.

breaks our setup, as we heavily need the cookbook attribute

@rmoriz Do your templates use anything not included here: https://github.com/stevendanna/logrotate/blob/master/resources/app.rb#L49-L56

@rmoriz @nullck I just pushed a change to master to re-add the cookbook attribute.  Let me know if that works for you.

and please release updated cookbook to supermarket

@scopenco I will release it to supermarket hopefully today or tomorrow. I would like some confirmation from the people who have spoken up about this that the current interface will work for them before releasing it so that we don't have to

Test coverage for this added here: https://github.com/stevendanna/logrotate/commit/2e069e50fe11f0a54329d957787eddcc911a1d87

keep in mind when making these types of breaking changes - it helps to keep the old around for a while and add WARNING's about the option being deprecated.    The end user who gets the error might not be the one who's directly consuming your cookbook - it could be 3 or 5 levels of dependancies deep.  (in my case, it's the openresty cookbook - which I wrap, but don't maintain.)
for me, the fix now is going to be to version lock to 1.9.2 in my wrapper cookbook. :(
Relevant File Content:
----------------------
/opt/chefprov/Provisioning/berkshelf-cookbooks/openresty/recipes/commons_conf.rb:

100:
101:    # Log rotation
102:    logrotate_app 'openresty' do
103:      path "#{node['openresty']['log_dir']}/*.log"
104:      enable true
105:      frequency 'daily'
106:      rotate node['openresty']['logrotate_days']
107>>     cookbook 'logrotate'
108:      create "0644 #{node['openresty']['user']} adm"
109:      options node['openresty']['logrotate_options']
110:      postrotate "test -f #{node['openresty']['pid']} && kill -USR1 $(cat #{node['openresty']['pid']})"
111:    end
112:
113:  end
114:

I've shipped 2.1.0 to the community site.  Please let me know if any of y'all still run into problems.
@keen99 +1 I did that for a few other options but missed it for this one.  I had the mistaken assumption that this option was barely used but I think that it being in the README meant that it was used in lots of places even when people are just setting it to the default value.

👍  thanks - working for me!


Minimum/Maximum age in Playground

There is an issue with the "wizard" for leisure=playground : the fields "Maximum age" and "Minimum age" are both linked to tag max_age and change at the same time.

You have to add manually min_age tag to have both tags !

Thanks for fixing @JamesKingdom 👍


Change xmx/xms ordering

I propose that xmx/xms be reordered here (min memory -> max memory as opposed to max memory -> min memory) which makes the overall readability of the script.

I've made some of the changes here. Let me know if I missed any <3 Thank you!

LGTM - Thanks :)


Potential Bug: Stack is cleared after Daedalus function call

There might be a problem with this code, if a Daedalus function is called from within an external, because the entire stack (including previous function's stacks) might be cleared:
https://github.com/GothicKit/ZenKit/blob/7121a33e809905d68a6d13b9eb9fa619f84ae2df/include/zenkit/DaedalusVm.hh#L153-L170
Instead, we should clear the stack up to the previous call frame (taking into account return values). There should also be an unsafe function to trigger this behaviour from C and wrappers.

Fixed in f53a955 by properly counting stack size.


fix: union like classes fail to synth

In https://github.com/cdk8s-team/cdk8s-core/pull/1573, we changed the resolution logic flow to take into account custom resolvers. This caused a regression where now union like classes such as IntOrString are no longer resolved properly.
This PR introduces a simple built-in resolver that handles such classes explicitly, instead of the implicit handling that we used to do.

💚 All backports created successfully

Status
Branch
Result

✅
1.x

Questions ?
Please refer to the Backport tool documentation


Negative path support for glob parameter into .groc.json

Did I miss something or glob parameter do not support negative paths as exclude from array into .groc.json?
Some example to clear minds:
"glob": [
  "src/**/*.coffee", "!src/**/*.spec.coffee",
  "gulp/**/*.coffee", "!gulp/**/*.spec.coffee",
  "README.md"
],
...

+1
Otherwise, the name glob should be changed to files.


No note-level pitch

Acknowledgement

[X] I have read Getting-Started and FAQ

🐛 Describe the bug
For example, on FL Studio, you can change the pitch of the whole note from the bottom of the piano roll.

However, all I can find on OpenUtau is an imprecise curve editor.

Due to the song being in a different tuning other than 12-tone equal temperament, I want to, for example, select all B notes and lower it down by 16 cents, or even lower the entire song by a few cents because the instrumental isn't in A440.
Explains how to reproduce the bug

Create an UTAU track
Add a melody
Try to lower an entire note evenly by a set number of cents

OS & Version
Windows 10
Logs
log20230828.txt

I've tried editing the "Pitch deviation (PITD)" expression to stop it from being of type "Curve", but it could not be edited. I created a new expression with the same abbreviation but as "Numeric", but the editor errored out and stopped me from editing it further or deleting it.

You can add a t flag which is supported by moresampler, tn_fnds and f2resamp:

OpenUtau (and the other singing voice synthesizers) don't support non-12-tone equal temperament natively, because the pitch curves of real-world human singing voices already have a uncertainty larger than the difference of various tuning systems, so tuning system switching isn't needed.

Human voice is different from musical instrument. There are complex singing techniques in each note. That's why the PITD should be curve

The thing about human voice is that there’s nothing keeping it stuck to 12TET. Well-trained singers can entrain themselves to the harmonics of the instrumentals, which OpenUTAU can make easier to simulate by making it possible to set a fine pitch value to every note.

Yes, I understand your point that PITD should be a curve to account for the most possibilities, but I haven’t touched it in any of my songs so far, only the pitch bend/ease controls between notes. For my workflow, it is a much cleaner method to retune the vocals to match the instrumental than to try to draw as steady and flat a line as I can with my mouse, starting and ending exactly where the notes do, at the exact height representing the number of cents I want to tune each note, one by one.

Update: The renderer I'm using doesn't support the T expression.
This would've been such a non-issue if 1) I could zoom into the expression bar and 2) I had a hotkey to prevent the mouse cursor from moving up and down (i.e. holding the same expression value as the mouse moves left and right).

Make sure to select the Classic renderer on the left, instead of Worldline-R. Then click on the gear icon to change the resampler to a compatible one (aka TIPS or f2resamp, as mentioned).

So no fine pitch control, then.

It seems you haven't read my comment.

I think this is indeed an unsolved issue.
We don't really have note-level fine pitch. We only have phoneme-level one.

https://github.com/stakira/OpenUtau/discussions/921


Chart dont animate

For some reason, there's no animation of the charts if my window dont have the vertical scroll.

@lgBatista can you post a fiddle?

Well, on the jsFiddle dont it happened, but I put it on the link for you see. In matter of fact the bug happens when i apply the plugin in the 'each' structure. To see this in action go to http://www.squadra.com.br/nucleoportais/chart-bug/chart-bug.html
When you open and dont have to scroll on the window vertical, the plugin renders the chart but it does not animate, if you resize the window until the scroll Appear ( or put on CSS " overflow- y: scroll ) and reload the page you will see the animation.
I tried to put the zip here but it dont work T_T to see the files go in http://www.squadra.com.br/nucleoportais/chart-bug.zip
I tested it on Firefox 47.0

@lgBatista I tried in Chrome 51.0.2704.103 and Firefox 47 and it animated fine on a 1080p monitor.

I see now that this only happens if the developer tool are opened (tested on chrome and firefox) ... I think that's no so important to fix if we consider that final user wont have it opened...

Did you have breakpoints set? That could affect the animation

Closing since it only exists when the dev tools are open. I think this ends up being as designed. We dynamically drop frames based on how long they take to run so that we don't slow the animation unnecessarily. This code probably ran in this case.


Let return all set method $this to allow a fluent use of the interface

Hi Ignace,
I would like you to consider my PR to implement a fluent interface for all setter methods.
I changed it mainly to later query parts.
With the current version, you always have to store the query-object to alter it:
$url = \League\Url\UrlImmutable::createFromServer($_SERVER);
$query = $url->getQuery();
$query->set(['page' => 123]);
$newurl = $url->setQuery($query);

The fluent interface would allow to alter the query string in a single line:
$url = \League\Url\UrlImmutable::createFromServer($_SERVER);
$newurl = $url->setQuery($url->getQuery()->set(['page' => $page]));

Thanks for considering!
Greets,
Dennis

Sorry to bother you again and for not just accepting your denial. But I think some of your statements just can't go unanswered:
@nyamsprod: I think it is really obvious that the $url->getQuery() method returns a QueryInterface object. If you are familiar with fluent interfaces, the additional ->set() call will not change your expectation.
I just don't understand why the top level classes (Url/UrlImmutable) have a fluent interface (setScheme(), setUser(), setPass(), setQuery() all return $this) but the secondary classes like QueryInterface does not. That is highly inconsistently and confusing. So please reconsider your decision and do not frustrate users with inconsistent interfaces, thank you!
And I have to strongly oppose @makasim: The arguments (in the supplied link) against fluent interfaces are more or less non-arguments:
'Fluent Interfaces break Encapsulation': that is exactly what happens if you use Url and UrlImmutable. But for QueryInterface this is not ok?
'Fluent Interfaces are harder to Mock': every object that has at least some non-trivial functionality is hard to mock, so that too is a non-argument.
'Fluent Interfaces make diffs harder to read': this is my favorite:
*** left.txt    Fri Nov  8 15:05:09 2013
--- right.txt   Fri Nov  8 15:05:22 2013
***************
*** 11,16 ****
--- 11,17 ----
$foo->addTab('tab');
$foo->addBar('bar');
$foo->addBaz('baz');
+$foo->addBaz('tab');
$foo->addTab('tab');
$foo->addBar('bar');
$foo->addBaz('baz');

is so much better to read than
*** left.txt    Fri Nov  8 15:05:09 2013
--- right.txt   Fri Nov  8 15:05:22 2013
***************
*** 11,16 ****
--- 11,17 ----
    ->addTab('tab')
    ->addBar('bar')
    ->addBaz('baz')
+     ->addBaz('tab')
    ->addTab('tab')
    ->addBar('bar')
    ->addBaz('baz')

With the $foo-> I also do not know where the $foo came from and again if you write non-trivial code, you nearly always have to look at the complete context (e.g. see in what method you are) to find the diff useful.
And finally, the websites arguments when a fluent interface may be good just match exactly all the secondary classes like the Query classes. So I don't understand your harsh opposition which seems based just on my example.

Sorry to bother you again and for not just accepting your denial. But I think some of your statements just can't go unanswered:
@nyamsprod: I think it is really obvious that the $url->getQuery() method returns a QueryInterface object. If you are familiar with fluent interfaces, the additional ->set() call will not change your expectation.
I just don't understand why the top level classes (Url/UrlImmutable) have a fluent interface (setScheme(), setUser(), setPass(), setQuery() all return $this) but the secondary classes like QueryInterface does not. That is highly inconsistently and confusing. So please reconsider your decision and do not frustrate users with inconsistent interfaces, thank you!
And I have to strongly oppose @makasim: The arguments (in the supplied link) against fluent interfaces are more or less non-arguments:
'Fluent Interfaces break Encapsulation': that is exactly what happens if you use Url and UrlImmutable. But for QueryInterface this is not ok?
'Fluent Interfaces are harder to Mock': every object that has at least some non-trivial functionality is hard to mock, so that too is a non-argument.
'Fluent Interfaces make diffs harder to read': this is my favorite:
*** left.txt    Fri Nov  8 15:05:09 2013
--- right.txt   Fri Nov  8 15:05:22 2013
***************
*** 11,16 ****
--- 11,17 ----
$foo->addTab('tab');
$foo->addBar('bar');
$foo->addBaz('baz');
+$foo->addBaz('tab');
$foo->addTab('tab');
$foo->addBar('bar');
$foo->addBaz('baz');

is so much better to read than
*** left.txt    Fri Nov  8 15:05:09 2013
--- right.txt   Fri Nov  8 15:05:22 2013
***************
*** 11,16 ****
--- 11,17 ----
    ->addTab('tab')
    ->addBar('bar')
    ->addBaz('baz')
+     ->addBaz('tab')
    ->addTab('tab')
    ->addBar('bar')
    ->addBaz('baz')

With the $foo-> I also do not know where the $foo came from and again if you write non-trivial code, you nearly always have to look at the complete context (e.g. see in what method you are) to find the diff useful.
And finally, the websites arguments when a fluent interface may be good just match exactly all the secondary classes like the Query classes. So I don't understand your harsh opposition which seems based just on my example.

To just come to a friendly conclusion here and stop with 'religious' argument for or against fluent interfaces, I will prepare a new pull request these days that has something like this:
interface UrlInterface { ...
  /**
   * Modify the URL query component
   *
   * @param array<string, string|null>
   *
   * @return static
   */
  public function modifyQuery($data);
... }

that will prevent the user from actually requirering something like my example by just using:
$obj = $url->modifyQuery(['page' => 123]);

where $obj is the same instance if $url was of type Url or a new instance if $url was UrlImmutable.
For consistency there should by similar methods for the other components but atm I don't have a use-case for that and changing portions of e.g. the host seems a little strange to me.
So I hope you will include this patch for a consistent fluent interface and my upcoming PR for a modify query method on the UrlInterface. Thanks for your work and your understanding.

To just come to a friendly conclusion here and stop with 'religious' argument for or against fluent interfaces, I will prepare a new pull request these days that has something like this:
interface UrlInterface { ...
  /**
   * Modify the URL query component
   *
   * @param array<string, string|null>
   *
   * @return static
   */
  public function modifyQuery($data);
... }

that will prevent the user from actually requirering something like my example by just using:
$obj = $url->modifyQuery(['page' => 123]);

where $obj is the same instance if $url was of type Url or a new instance if $url was UrlImmutable.
For consistency there should by similar methods for the other components but atm I don't have a use-case for that and changing portions of e.g. the host seems a little strange to me.
So I hope you will include this patch for a consistent fluent interface and my upcoming PR for a modify query method on the UrlInterface. Thanks for your work and your understanding.

'Fluent Interfaces break Encapsulation': that is exactly what happens if you use Url and UrlImmutable. But for QueryInterface this is not ok?

I was not aware that url object has fluent interface. From my own opinion it should not be there as well as in query object...

'Fluent Interfaces break Encapsulation': that is exactly what happens if you use Url and UrlImmutable. But for QueryInterface this is not ok?

I was not aware that url object has fluent interface. From my own opinion it should not be there as well as in query object...

'Fluent Interfaces are harder to Mock': every object that has at least some non-trivial functionality is hard to mock, so that too is a non-argument.

I can admit it from my own experience

'Fluent Interfaces are harder to Mock': every object that has at least some non-trivial functionality is hard to mock, so that too is a non-argument.

I can admit it from my own experience

@dennisbirkholz adding a modifyQuery method to the Url object is a bad idea as you will provide 2 methods to do the same thing with the modifyQuery being only a proxy to url->getQuery()->modify()
@makasim I'll write a better explanation and a possible solution to the fluent issue tomorrow

@dennisbirkholz adding a modifyQuery method to the Url object is a bad idea as you will provide 2 methods to do the same thing with the modifyQuery being only a proxy to url->getQuery()->modify()
@makasim I'll write a better explanation and a possible solution to the fluent issue tomorrow

@makasim  @dennisbirkholz just highlighted the problem with the current API. The methods named used with the Url classes seems to recommend using a fluent interface while this was not the first intent.
The misunderstanding comes from how v3 was developped. I started with a single Url class which did not expose any fluent interface. But during the version development, I choose to add the UrlImmutable class which required to return a new object each time one component is modified. Since I wanted both classes to expose the same API (like DateTime and DateTimeImmutable do) I choose to add the fluent interface on the mutable version of the class.
Now there's a way out of this mess. After working with v3 for a while I noticed that I was working much more with UrlImmutable than with Url because of its immutability.
Since I'm working on version 4 we could (should?) remove one of those classes. IMHO we should:
1.remove the v3 League\Url\Url class from v4
2.renamed the v3 League\Url\UrlImmutable as the new League\Url\Url class in v4.
3.renamed all v3 League\Url\UrlImmutable:setXXX methods as  League\Url\Url:withXXX
Here's a simple usage of v4:
use League\Url\Url;

$url = Url::createFormUrl('http://www.example.com/path/to/index.php?key=value#fragment');
$alt = $url
           ->withHost('::1')
           ->withFragment('bar'); // returns http://[::1]/path/to/index.php?key=value#bar
$url->sameValueAs($alt); //returns false
$alt->getQuery()->sameValueAs($url->getQuery()); //returns true

$alt is constructed from $url but $alt is not the same as $url.
Making League\Url\Url an immutable value object with better methods named should simplify the package, clarify the class behavior and resolves the Fluent Interface issue.

In my current project I use the Url for two things:

it holds the current Url of the page and upon ajax-requests this Url is adjusted and pushed back to the browser. It would be extremely impractical if I had to replace the Url everytime because it is Immutable.
I use the "fluent" interface to create paginations. This is where my initial PR came from. When I look at your example from the previous post, I miss a ->withQuery(['param' => 'value']) method that does not replace but alter the query. Otherwise the query is the only part that requires to get the query, change it and set it back (which creates a new Url object) whereas all other parts can be changed directly.

I would really like to know why you try to avoid a consistent fluid interface like the devil the holy water ;-) What is wrong with an interface that is quite a common known pattern and reduces a lot of boilerplate code for the user of your package? I am not sure if it is really advisable to change the behavior of the package so fundamentally and potentially loose a lot of users if it is not really necessary (from by POV).

I use the "fluent" interface to create paginations.

For pagination IMHO using UrlImmutable is better approach as you don't loose your current URL when creating your pagination look at the given example in the documentation

it holds the current Url of the page and upon ajax-requests this Url is adjusted and pushed back to the browser.

I fail to see how using UrlImmutable you would have a huge impact ? PHP wise each ajax call is a different execution script. So you would end up with a code looking somewhat like below depending on what your are returning to your client.
//using v3
$orig_url = UrlImmutable::createFromServer($_SERVER);
$dest_url = $orig_url->setQuery(['param' => 'value']);

In this latter example you have a clarity of intent. you do have a copy of the current URL and you clearly know what you destination url will be.
The main reason I want to stay away from fluent interfaces in case of dealing with URL is because it may confused developers. If you go back to @ocramius post you'll see that the current package is breaking encapsulation and may break decorators and composition. These are issues I'm trying to fix by removing one of the two Url class and by renaming the methods. I understand that by not implementing fluent interfaces on the component classes you might end up writing more lines of codes but that won't affect the execution code/time of your script.
For the record I'm not trying to avoid the fluent interface at all costs, (they are still in use in the package) but every solution has its tradeoffs.Going full immutable and restricting fluent interfaces to the URL class only IMHO will provide a better cohesive package.

I use the "fluent" interface to create paginations.

For pagination IMHO using UrlImmutable is better approach as you don't loose your current URL when creating your pagination look at the given example in the documentation

There was a missing UrlImmutable in my comment, sorry. I wanted to express that I use both classes and I would opt against dropping the Url class. And I use pagination similar to your example.

it holds the current Url of the page and upon ajax-requests this Url is adjusted and pushed back to the browser.

I fail to see how using UrlImmutable you would have a huge impact ? PHP wise each ajax call is a different execution script.

As the page shown is changed with subsequent ajax requests, the state of the page is persisted. The actual ajax calls have a different Url than what is presented to the user so the Url in the page state is created on the initial page load and than adjusted in the ajax requests. I would have to overwrite the Url each time I change the query which is very unintuitive. And I don't see why you should limit the features of the package by dropping the mutable Url class.

adding a modifyQuery method to the Url object is a bad idea as you will provide 2 methods to do the same thing with the modifyQuery being only a proxy to url->getQuery()->modify()

I would propose to give methods to directly manipulate the parts to the UrlInterface classes. I just would really like to reduce the actual code required to modify the UrlInterface instance. In case of the UrlImmutable class this is not only a proxy but will clone itself and apply a method call. I don't see why such a convenience method (maybe only as part of the UrlImmutable class) would harm anything.


raw.pick_channels modify the raw object

raw.pick_channels modify the raw instance. The following code shows the behavior:
from __future__ import print_function
import mne
import numpy as np

fs = 1
t = [1,2,3]
x = [1,1,1]

ch_types = ['eeg', 'eeg']
ch_names = ['ch1', 'ch2']

data = np.atleast_2d(np.vstack((x, x)))
info = mne.create_info(ch_names=ch_names, sfreq=fs, ch_types=ch_types)
raw = mne.io.RawArray(data, info)

print('Before', raw.ch_names)
new_raw = raw.pick_channels(['ch1'])
print('After', raw.ch_names)

Output:
Before ['ch1', 'ch2']
After ['ch1']

I think this is either a bug or an undocumented behavior.
The change happens here https://github.com/mne-tools/mne-python/blob/master/mne/channels/channels.py#L760:
pick_info(self.info, idx, copy=False)

Using copy=True change the behavior, but that will change the behavior of _pick_drop_channels.

It is meant to do this by design (all object. methods should work inplace like this when possible), do you have time to make a PR to mention this inplace operation?

FYI to avoid such behavior you can do raw_pick = raw.copy().pick_channels(...)

I'll do a PR by tomorrow.


Refactor relationship classes to structure differently for Generic "Relationship" to which Stix Object Relationship and Sighting Relatinoships are children of the "Generic Relationship"

As per conversation in: https://github.com/oasis-tcs/cti-stix2/issues/113

done


Decorator to add nodes

It'd be neat if there was a decorator, so you could do this:
@loman.node(comp)
def b(a):
  return a+1

and it's equivalent to
comp.add_node('b', lambda a: a+1)

Initial version added in 8c66bbe49f027409a56ca0c3797cfd4d8ca400f0.


How to enable  to allow JavaScript site!

Bug Report
I added AngleSharp.Js and WithJs and also added user agent but I'm getting "You need to allow JavaSript for this site!" from our testing web site.
Prerequisites

[ ] Can you reproduce the problem in a MWE?
[X] Are you running the latest version of AngleSharp?
[X] Did you check the FAQs to see if that helps you?
[ ] Are you reporting to the correct repository? (there are multiple AngleSharp libraries, e.g., AngleSharp.Css for CSS support)
[X ] Did you perform a search in the issues?

Steps to Reproduce

Thank you for your help.

Not sure about the specific page, but since JS is on I suppose this is not a noscript block, but rather a "JS script not loaded" issue.
Make sure the JS is not crashing (i.e., AngleSharp.Js is capable of running the script). Also note did you did not enable resource loading; if the JS is in an external *.js file, i.e., not inlined, then it won't be loaded with the configuration you supplied.
Please try to create a MWE to reproduce the problem in isolation.

Anything? cc @muhammetsahin


Commitlint Set Up

We need to add commitlint to ensure that all commits follow a defined convention, making it easier to understand the changes made in a project's history.


onShouldBlockNativeResponder

Currently the zoomable view conflicts with other packages like react native tab view because of line 130 in src/ReactNativeZoomableView.tsx:
     onShouldBlockNativeResponder: () => false,
This line can lead to the PanResponder being terminated if there are other instances of PanResponder, meaning that the zoomable view can't pan or zoom properly, if at all. Could you please fix this, either by changing false to true, or just by making onShouldBlockNativeResponder an optional prop?

Hi! This sounds like a great candidate for a pull request. If you are able to fix the problem in a PR, please submit it and we'll take a look.

@lukahc Thank you for the help! Turns out I needed this functionality almost immediately. Very useful.
Do you think this should be true by default? It seems like it would always be a good idea for it to block pan responders.

@lukahc Thank you for the help! Turns out I needed this functionality almost immediately. Very useful.
Do you think this should be true by default? It seems like it would always be a good idea for it to block pan responders.

I agree, I can't think of many scenarios where it would be better for it to be false, I can make a PR for that change

@elliottkember https://github.com/openspacelabs/react-native-zoomable-view/pull/75

Nice – I think that should be fine.
An interesting note: onShouldBlockPanResponder is only implemented on Android.
However, I found that it was working on iOS too, but only because I happened to be using a react-native-gesture-handler wrapper. That library overrides UIManager to make this work. More info here: https://github.com/facebook/react-native/pull/40750


Just started using and love it so far.  If I keep updating the json from the website will that break any events I create in Obsidian?

I am actually not sure! Let me do some testing… I don’t think it will merge things if you re-import a new calendar from Fantasy-Calendar.
I can try to explore adding that, but managing conflicts can be a bit rough sometimes :)

Thanks for the response.  Appreciate all your work.


kubectl process exit status lost with kubecolor

kubecolor ignores the exit status of the kubectl process:
$ /usr/bin/kubectl get pod foo; echo $?
Error from server (NotFound): pods "foo" not found
1
$ kubecolor get pod foo; echo $?
Error from server (NotFound): pods "foo" not found
0

(use-case: in a script (so the exit status is necessary), where a human still sees the outputs (so the color is much useful).)

Nice catch. This should be fixed..

Nice catch. This should be fixed..

Forwarding the errors from cmd.Wait() hopefully may be enough?
https://github.com/dty1er/kubecolor/blob/b83ce9d89601e9d8b3d37544f864a0d56d2faca9/command/runner.go#L96

Forwarding the errors from cmd.Wait() hopefully may be enough?
https://github.com/dty1er/kubecolor/blob/b83ce9d89601e9d8b3d37544f864a0d56d2faca9/command/runner.go#L96

Currently this is fixed at the latest kubecolor (v0.0.11).
Thank you for opening this issue and sorry for my late work.

Thanks @dty1er! I confirm 0.0.11 fixes the issue.
No worries for the time to fix: you owe nothing to the internet, thanks for your great work!


Fix memory model violation / race condition: Dirty-flag must be volatile

If I read https://docs.oracle.com/javase/specs/jls/se8/html/jls-17.html right, then we must make that flag volatile.

Thank you! There's a ton more thread-unsafety in this codebase btw :)


Added routes / service relationships

Created routes / service relationships

@simon3z Please review.  I am unable to test as my local openshift provider won't work and the TLV one is unreachable.

@simon3z @screeley44 Federico, Scott reviewed this with me today and as able to test on his local VM that it's working properly.  Please let me know if you want me to rebase

@simon3z I added the UI to this PR since it hasn't been merged and they depend on one another

@simon3z please review when you can

@erinboyd can you squash all the patches in one? Thanks!

@erinboyd Please rebase and push again.
cc @simon3z @dclarizio @h-kataria @martinpovolny

@erinboyd Please rebase and push again.
Also, please add specs.  If you need help in doing so, please contact @tenderlove.
cc @simon3z @abonas

@erinboyd can you squash the patches? Thanks!

@erinboyd please also add the relationship in the UI from routes to services.

@simon3z please review

@erinboyd travis is failing, you have to fix the code/tests accordingly.

@erinboyd also according to travis you have to fix the spec test assert_specific_container_route that is asserting that the :service_name is frontend

@erinboyd Please review and fix the Travis failures.

@erinboyd vmdb/db/migrate/20150610031455_add_routes_to_services.rb should be renamed to db/migrate/20150610031455_add_routes_to_services.rb

@chessbyte I have aligned the code to be consistent with the previous stanzas.  Please let me know how this should be fixed

@erinboyd vmdb/db/migrate/20150610031455_add_routes_to_services.rb should be renamed to db/migrate/20150610031455_add_routes_to_services.rb
Also, you have to rebase before re-pushing.

@chessbyte I already renamed that file and put it up there.

@erinboyd If you click on the "Files changed" tab and scroll to the bottom, you will see it there.

Not sure why it's still there....?
Erins-MacBook-Pro:vmdb erinaboyd$ git rm db/migrate/20150610031455_add_routes_to_services.rb
rm 'vmdb/db/migrate/20150610031455_add_routes_to_services.rb'
Erins-MacBook-Pro:vmdb erinaboyd$ git commit -m "removed old migration script"
[routes 3ca4f96] removed old migration script
1 file changed, 6 deletions(-)
delete mode 100644 vmdb/db/migrate/20150610031455_add_routes_to_services.rb
Erins-MacBook-Pro:vmdb erinaboyd$

@erinboyd Now it is properly renamed.  Can start reviewing in earnest.


was deleted the MediaPluginBridge object - Error

the mejs.MediaPluginBridge object  was deleted of the library and reports an error on the method remove

Same issue here.

@krobing The fix was integrated on last release. can you close this issue, please?

it's done, thank you


Missing $ref paths for DELETE operations

Opening a new issue for better visibility.
Original request and details at https://github.com/microsoftgraph/microsoft-graph-devx-api/issues/567

@maisarissi  I'd like to close this issue because it's a duplicate of #567

Hi @adhiambovivian .
I decided to open a new issue because the #567 is kind old and I was concerned about the visibility of this request.
If this is not an issue, I have no problem closing this.

Was this fixed by https://github.com/microsoftgraph/msgraph-metadata/issues/131?
@peombwa @irvinesunday @adhiambovivian

The missing Remove-Mg* commands are now available as of https://github.com/microsoftgraph/msgraph-sdk-powershell/releases/tag/1.10.0.


Enhancement: Add Number Entry Support at Start

No idea if this is possible, but in a headless Pi install, it would be cool to be able to enter the IP address using streamdeck buttons. I'm envisioning a 0-9 and enter button to enter an ip address into the system.
That said, now that I'm writing this, you could probably do this reverse from a post command in Companion.
Just would be interesting to be able to connect to companion without having to pull out a laptop.
I'd say low priority if even possible.

That said, now that I'm writing this, you could probably do this reverse from a post command in Companion.

Yes, this is something I am thinking about doing, as well as adding mdns so that companion can discover satellite if wanted
Building an ip address input is unlikely to be something I will look into, it gets a bit complex and messy for first setup. And considering that satellite supports 10+ different surface types, some of which don't have displays, or don't have enough buttons to do 0-9 input, this will likely need to be tested or implemented slightly differently for each surface type.

Working on this! Here's progress:

Unfortunately I cannot get the code to commit until it lints and I'm really struggling to get ESLint and the TSConfigs to like each other. Modern JS development with its complex toolchains is very frustrating to work on.

Unfortunately I cannot get the code to commit until it lints and I'm really struggling to get ESLint and the TSConfigs to like each other. Modern JS development with its complex toolchains is very frustrating to work on.

Honestly the answer for now is probably to skip the hooks when committing.
I don't remember if I fixed the eslint issue you mention, or if I have been ignoring it by skipping the hooks


Cleanup

Codecov Report

Merging #3 into master will increase coverage by 3.44%.
The diff coverage is 86.49%.

@@            Coverage Diff             @@
##           master       #3      +/-   ##
==========================================
+ Coverage   64.76%   68.20%   +3.44%
==========================================
  Files          73       66       -7
  Lines        8078     7326     -752
==========================================
- Hits         5232     4997     -235
+ Misses       2846     2329     -517

Flag
Coverage Δ

#ecl
68.20% <86.49%> (+3.44%)
:arrow_up:

Impacted Files
Coverage Δ

EKF/EKFGSF_yaw.h
100.00% <ø> (ø)

EKF/common.h
100.00% <ø> (ø)

EKF/drag_fusion.cpp
0.00% <0.00%> (ø)

EKF/estimator_interface.cpp
67.49% <ø> (ø)

EKF/estimator_interface.h
100.00% <ø> (ø)

EKF/imu_down_sampler.cpp
100.00% <ø> (ø)

EKF/sideslip_fusion.cpp
0.00% <0.00%> (ø)

test/test_AlphaFilter.cpp
100.00% <ø> (ø)

EKF/mag_fusion.cpp
31.72% <19.04%> (-0.21%)
:arrow_down:

EKF/optflow_fusion.cpp
13.09% <20.00%> (+7.85%)
:arrow_up:

... and 41 more

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 b96c62e...e31fcc6. Read the comment docs.


Add support for styling the branch infobar

What's the issue:
Branch infobar wasn't getting styling treatment.
What's fixed:
Now it is :-)
Screenshots:
Before:

After:

Here are the befores/afters for the TutorialPopover:

@oubiwann Hi, thanks for helping! The infobar is already fixed in v2.6.0 release (Haven't push it). However, you can style the TutorialPopover but some color need to be changed.

@oubiwann Can you try this color? Background: #1a2632, btn #243447

I've changed the background color; trying to figure out how to get the tutorial messages back so that I can test the button color ...

Hrm, for the popovers and dropdowns, a caret is used. When the popover/dropdown background color is different from the page background, this caret (or wedge) is visiable; when #1a2632 is used instead, you can't see it :-(
Attaching screenshot:


[SaaS Connector Engine] Create Connection Test

Description
Each connector to a third party app should have a method to call test a connection. We need to create a way where we can programmatically test the logic against the schema.
Acceptance Criteria

Demonstrate that a user can perform a connection test for a SaaS Connector.
Show that we allow the ability to intake Authorization header and query params

Additional Information
This iteration must support the following authentication methods:

Basic auth
Bearer auth

Choose one or all of the following 3rd party applications to perform a connection test on Stripe, Zendesk, Slack (can pick something else if any connection test appears to be "off-standard")

Hi @adriaaaa.
I wanted to clarify what is meant by "API Token". Both Basic and Bearer are registered HTTP Authentication Schemas, but "API Token" is not. See: https://www.iana.org/assignments/http-authschemes/http-authschemes.xhtml
We can pass an "API Token" via the Authorization header using the Bearer schema. Would that be sufficient?

Spoke with @nschoenbrot and @galvana and updated the description


Update README.md

Update getting started - add info on cloning the repo. npm i essential-react would work but would bring not the expected result probably.

Coverage remained the same at 84.75% when pulling 2ea3f1d05c5231d41285c6fa7e45727c1a890cfe on sudodoki:patch-1 into d2a1ca925e2c1d0a2aae181ee861a82c92354add on pheuter:master.

Cloning the project like this also assumes that the default branch is stable.

Or rather, not taking an additional step to check out a tagged release


Add config option for default rendition preset to be applied

Motivation
Users are having a hard time adopting the new asset renditions feature as the SDKs always return the original asset URL by default. We'd like to add an option to configure the default preset codename to be applied when such rendition exists in the Delivery API response.
Underlying Jira issue: https://kentico.atlassian.net/browse/KCL-8387
Proposed solution
Let's get inspired by the JS implementation: https://github.com/Kentico/kontent-delivery-sdk-js/pull/336

See the linked PR and please, take a close look at this change (I think it was a bug): https://github.com/Kentico/kontent-delivery-sdk-net/pull/320/files#diff-41f337b8d1d0e7995f0335ec5851944005dc3edd57b1a651cfea71b927e1fca9L223

PR has been merged. Can we close this issue @MiroKentico?

Yes, I am closing it.