Listing contexts fails when managing a large number of contexts

With growing number of contexts and variables in CircleCi, we are getting more often this error:
Error: failed to load context list: Non-nullable field was null. Something unexpected happened.
Set -parallelism=1 for terraform plan is helped for some time, but after add more new contexts, we started to see this error again.
Also, after add 18 contexts via terraform, we got email from CircleCi support with request to explain why we produce so many requests  to CircleCi v1 API and have recommended to switch to v2 REST API:
https://circleci.com/docs/api/v2/#tag/Context

The context feature uses their GraphQL API which isn't officially supported. I'm aware of the added REST support for contexts (finally!) but haven't had a chance to investigate client support and switch here.

This shouldn't be too much trouble:
https://github.com/CircleCI-Public/circleci-cli/blob/master/api/context_rest.go
Might even be able to get to it today, since I'm coincidentally working on some refactoring some CircleCI contexts/vars right now. The REST API does have proper support for fetching a context by ID:
https://circleci.com/docs/api/v2/#operation/getContext
Whereas GraphQL, based on the implementation I borrowed from CircleCI's CLI, only supported listing contexts, and required client-side filtering.
Kinda wild that Circle falls over with that number of requests, but perhaps not so surprising considering contexts were available with no API and then an "unofficial" API for years. Better late than never!

Might even be able to get to it today, since I'm coincidentally working on some refactoring some CircleCI contexts/vars right now.

Oh, It's would be grate. Thank you @bendrucker

Started on this in https://github.com/mrolla/terraform-provider-circleci/pull/44. I want to convert everything over to v2 (including things that were on REST v1). Should definitely have a tested PR up today, so you can expect this to be released in the next week or two.

A mixed update for you on this. I did a bunch of work to port everything over to API v2. While I want to be respectful to the people at CircleCI who are working hard on this stuff, there are serious, obvious quality problems with this API. I'm working through a long list of failing acceptance tests and am filing bug reports on Circle's discussion board as I identify the causes.
This was the first one:
https://discuss.circleci.com/t/api-v2-malformed-json-bodies-returned-on-400s/39393/2
I expected to be able to use Circle's REST client from their CLI, similar to how I borrowed the GraphQL client from the same place. Instead, I'm finding myself inlining almost all of the client functionality over seemingly small but critical issues, like the one above, or their CreateContext method not actually returning the created context (and its ID).
I am a CircleCI customer via @takescoop and will reach out to support to try to escalate this a bit. If you could also mention it on your open support thread that might help as well. Feel free to link them here or to my discussion threads.

Hi, @bendrucker . Thanks for your work. I've asked CircleCi support for help in our support thread. Will back, when got a response.

Hi, @bendrucker I've got response from CircleCi with same message actually which they have posted in your support thread https://discuss.circleci.com/t/api-v2-malformed-json-bodies-returned-on-400s/39393/4
Also, I've checked this case and it works for me via curl request:
curl --request POST \      --url https://circleci.com/api/v2/context \   --header 'Circle-Token: REDACTED' \   --header 'content-type: application/json'  \   --header 'Accept: application/json' \   --data '{"name":"context-test","owner":{"slug":"gh/myorg","type":"organization"}}' {"message":"A context named context-test already exists."}
Also, have checked with not existed context and I see id for created context in response:
{"name":"context-test2","id":"764177b6-e38b-4650-adea-323555614ab1","created_at":"2021-03-19T15:45:20.762Z"}
Please, check when you have time. Also, do you have other blockers?

Yep I'll look into it. This was using their own API client from their CLI. I just have to work through the acceptance tests and figure things out. We're somewhat hamstrung here by the lack of an official API client to rely on. Thought that the package in their CLI would work. It worked pretty flawlessly on the GraphQL side (despite lack of official support) but has been a bit less consistent on the REST side, perhaps because that's not actually hooked up in their CLI yet.
Should have some more free time to work through more acceptance tests today. Will continue to update the PR with notes.

Hi, @bendrucker
Have built your last changes from circleci-api-v2 branch and it works incredibly fast and without errors so far.  Only one warning pop up on each plan:
Warning: "graphql_url": [DEPRECATED] CircleCI's v2 REST API has replaced the GraphQL API in this provider. This attribute is unused and will be removed in the next major version.


[Critical] Fix Filament new Page method

Update the shouldRegisterNavigation properties

This update is observed in Filament's /Resources/Pages/Page.php.

[!WARNING]This bug is breaking PHP and preventing Composer workflow.

Nice catch! thank you ❤


[GLUTEN-2346][VL] Move Velox-Substrait plan conversion to Gluten cpp

What changes were proposed in this pull request?
To simply the process of Velox rebase and enhance code maintainability, this PR moves the Velox-Substrait plan conversion from Velox to Gluten cpp.
(Fixes: #2346)
How was this patch tested?
under test

Hi @rui-mo,  does that mean we can exclude build substrait in oap/velox?

Hi @rui-mo, does that mean we can exclude build substrait in oap/velox?

@Yohahaha Yes, that's right. @zhejiangxiaomai will help remove the compilation of Substrait module in next rebase. All local changes on Substrait will also be remove from oap/velox.

https://github.com/oap-project/velox/pull/366 remove the compilation of Substrait module


Duplicate events

Describe the bug
We've been observing duplicate events (on push at least) in TriggerMesh's internal end-to-end testing pipeline lately. The timing seems to match with the release of v0.25.0.
We confirmed events were indeed triggered by the same commit ID. However, the CloudEvent id attribute does differ between events.

:page_facing_up: event 1
{
  "specversion": "1.0",
  "id": "acfeaf00-d130-4a5a-afdd-9d3bcc529645",
  "source": "https://gitlab.com/triggermeshDev/e2e-gitlab-sqs-5656",
  "type": "dev.knative.sources.gitlab.push",
  "datacontenttype": "application/json",
  "time": "2021-08-24T00:09:12.191890206Z",
  "data": {
    "object_kind": "push",
    "before": "0000000000000000000000000000000000000000",
    "after": "d5d67064fe50e85c6a9642678d831eba1483077c",
    "ref": "refs/heads/main",
    "checkout_sha": "d5d67064fe50e85c6a9642678d831eba1483077c",
    "user_id": 6913632,
    "user_name": "Triggermesh",
    "user_username": "triggermeshDev",
    "user_email": "",
    "user_avatar": "https://secure.gravatar.com/avatar/e01a92939a506691181a489e99a705fd?s=80&d=identicon",
    "project_id": 29076284,
    "Project": {
      "id": 29076284,
      "name": "e2e-gitlab-sqs-5656",
      "description": "Generated by the TriggerMesh e2e test suite",
      "web_url": "https://gitlab.com/triggermeshDev/e2e-gitlab-sqs-5656",
      "avatar_url": "",
      "git_ssh_url": "git@gitlab.com:triggermeshDev/e2e-gitlab-sqs-5656.git",
      "git_http_url": "https://gitlab.com/triggermeshDev/e2e-gitlab-sqs-5656.git",
      "namespace": "Triggermesh",
      "visibility_level": 0,
      "path_with_namespace": "triggermeshDev/e2e-gitlab-sqs-5656",
      "default_branch": "main",
      "homepage": "https://gitlab.com/triggermeshDev/e2e-gitlab-sqs-5656",
      "url": "git@gitlab.com:triggermeshDev/e2e-gitlab-sqs-5656.git",
      "ssh_url": "git@gitlab.com:triggermeshDev/e2e-gitlab-sqs-5656.git",
      "http_url": "https://gitlab.com/triggermeshDev/e2e-gitlab-sqs-5656.git"
    },
    "repository": {
      "name": "e2e-gitlab-sqs-5656",
      "url": "git@gitlab.com:triggermeshDev/e2e-gitlab-sqs-5656.git",
      "description": "Generated by the TriggerMesh e2e test suite",
      "homepage": "https://gitlab.com/triggermeshDev/e2e-gitlab-sqs-5656"
    },
    "commits": [
      {
        "id": "d5d67064fe50e85c6a9642678d831eba1483077c",
        "message": "Create file README.md",
        "timestamp": "2021-08-24T00:09:04Z",
        "url": "https://gitlab.com/triggermeshDev/e2e-gitlab-sqs-5656/-/commit/d5d67064fe50e85c6a9642678d831eba1483077c",
        "author": {
          "name": "TriggerMesh e2e",
          "email": "<redacted>"
        },
        "added": [
          "README.md"
        ],
        "modified": [],
        "removed": []
      }
    ],
    "total_commits_count": 1
  },
  "comgitlabevent": "Push Hook",
  "knativearrivaltime": "2021-08-24T00:09:12.205358596Z"
}

:page_facing_up: event 2
{
  "specversion": "1.0",
  "id": "7d442459-e063-4fa4-8617-efdfe597efac",
  "source": "https://gitlab.com/triggermeshDev/e2e-gitlab-sqs-5656",
  "type": "dev.knative.sources.gitlab.push",
  "datacontenttype": "application/json",
  "time": "2021-08-24T00:09:12.191887709Z",
  "data": {
    "object_kind": "push",
    "before": "0000000000000000000000000000000000000000",
    "after": "d5d67064fe50e85c6a9642678d831eba1483077c",
    "ref": "refs/heads/main",
    "checkout_sha": "d5d67064fe50e85c6a9642678d831eba1483077c",
    "user_id": 6913632,
    "user_name": "Triggermesh",
    "user_username": "triggermeshDev",
    "user_email": "",
    "user_avatar": "https://secure.gravatar.com/avatar/e01a92939a506691181a489e99a705fd?s=80&d=identicon",
    "project_id": 29076284,
    "Project": {
      "id": 29076284,
      "name": "e2e-gitlab-sqs-5656",
      "description": "Generated by the TriggerMesh e2e test suite",
      "web_url": "https://gitlab.com/triggermeshDev/e2e-gitlab-sqs-5656",
      "avatar_url": "",
      "git_ssh_url": "git@gitlab.com:triggermeshDev/e2e-gitlab-sqs-5656.git",
      "git_http_url": "https://gitlab.com/triggermeshDev/e2e-gitlab-sqs-5656.git",
      "namespace": "Triggermesh",
      "visibility_level": 0,
      "path_with_namespace": "triggermeshDev/e2e-gitlab-sqs-5656",
      "default_branch": "main",
      "homepage": "https://gitlab.com/triggermeshDev/e2e-gitlab-sqs-5656",
      "url": "git@gitlab.com:triggermeshDev/e2e-gitlab-sqs-5656.git",
      "ssh_url": "git@gitlab.com:triggermeshDev/e2e-gitlab-sqs-5656.git",
      "http_url": "https://gitlab.com/triggermeshDev/e2e-gitlab-sqs-5656.git"
    },
    "repository": {
      "name": "e2e-gitlab-sqs-5656",
      "url": "git@gitlab.com:triggermeshDev/e2e-gitlab-sqs-5656.git",
      "description": "Generated by the TriggerMesh e2e test suite",
      "homepage": "https://gitlab.com/triggermeshDev/e2e-gitlab-sqs-5656"
    },
    "commits": [
      {
        "id": "d5d67064fe50e85c6a9642678d831eba1483077c",
        "message": "Create file README.md",
        "timestamp": "2021-08-24T00:09:04Z",
        "url": "https://gitlab.com/triggermeshDev/e2e-gitlab-sqs-5656/-/commit/d5d67064fe50e85c6a9642678d831eba1483077c",
        "author": {
          "name": "TriggerMesh e2e",
          "email": "<redacted>"
        },
        "added": [
          "README.md"
        ],
        "modified": [],
        "removed": []
      }
    ],
    "total_commits_count": 1
  },
  "knativearrivaltime": "2021-08-24T00:09:12.205347778Z",
  "comgitlabevent": "Push Hook"
}

Expected behavior
A single action shouldn't cause the delivery of multiple events through the source.
To Reproduce
We had trouble reproducing this manually, but just in case, here is the manifest used in e2e tests:
 apiVersion: sources.knative.dev/v1alpha1
 kind: GitHubSource
 metadata:
   name: github
 spec:
   ownerAndRepository: ''
   eventTypes:
   - push
   accessToken:
     secretKeyRef:
       name: ''
       key: ''
   secretToken:
     secretKeyRef:
       name: ''
       key: ''
   sink:
     ref:
       apiVersion: eventing.knative.dev/v1
       kind: Broker
       name: mybroker

Knative release version
v0.25.0
Additional context
-
cc. @FranBarrera FYI

I have a feeling this is occurring because - in tests especially - things are happening very fast between the moment the webhook is reconciled and the actual action is performed (a Git commit in our case). Read on.
In v0.25.0, we started actually reconciling the webhook on changes to GitLabSource objects:
https://github.com/knative-sandbox/eventing-gitlab/blob/52af621192458576458a57bfe80d775ab5e23426/pkg/reconciler/source/gitlabsource.go#L142-L143
During the creation of such object especially, updates are very frequent due to status conditions being initialized, etc. It could be that, at the same time the commit is happening, the controller is calling cli.Edit() on the webhook, and who knows, maybe this isn't truly a no-op on GitLab's side, even if the webhook's config doesn't technically change.
It would probably be better to avoid relying on things that may or may not have side effects on GitLab's side, and perform a get() + compare() during the webhook reconciliation, instead of a update() in every loop.
Just my assumptions.

/remove-lifecycle stale


Move PyUnstable_Module_SetGIL out of "if MODULE_STATE"

This was causing single-phase freethreading builds not to work correctly.

The diff looks funny, but yes, that seems right.


In V4 router events don't seem to propagate into redux connected components

Version
4.0.0
Test Case
import React from 'react'
import {
  BrowserRouter as Router,
  Route,
  Link,
  NavLink
} from 'react-router-dom'
import { connect } from 'react-redux'

class Nav extends React.Component {
  render() {
    return (

<NavLink exact to="/" activeClassName="is-selected">Home</NavLink>

<NavLink to="/about" activeClassName="is-selected">About</NavLink>

<NavLink to="/topics" activeClassName="is-selected">Topics</NavLink>

    );
  }
}

var ConnectedNav = connect((state) => {
  return {};
})(Nav);

const BasicExample = () => (
  <Router>

      <ConnectedNav />

  </Router>
)

export default BasicExample;

Steps to reproduce
Expected Behavior
activeClassName should be applied to current NavLinks
Actual Behavior
As you navigate around nothing activeClassName is not applied, isActive method is not called, etc.

Please see our guide to dealing with blocked updates. Also, react-redux v5 is going to stop blocking updates using shouldComponentUpdate, AFAICT.


Add Go version source file for cloud-provider-nutanix

Adding the Go version source of truth file for nutanix-cloud-native/cloud-provider-nutanix.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/cherry-pick release-0.20

/cherry-pick release-0.19

/lgtm
/approve


chore(main): release 0.48.2

:robot: I have created a release beep boop
0.48.2 (2024-05-27)
Miscellaneous

Files: Improve messaging of hidden files viewer (#606) (6648e47)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/BLSQ/openhexa-frontend/releases/tag/0.48.2 :sunflower:


batch mode

Is this library designed, or easily adapted, to run in offline/batch mode, such as to estimate emotions in 10,000 images stored locally?

Hmm, seems easier to build it in Python by starting with this code
https://github.com/auduno/clmtools/blob/master/pdm_builder/create_classifier.py

The library wasn't designed to do it, but it should be possible to do just by modifying the code in the emotiondetection example  and the image tracking example, e.g. just adding a loop over several files which fit a face model and then classify the emotions. Note that you will have to run this in a webpage, as I haven't yet ported clmtrackr to node.js.
You're going to have problems using the clmtools code for this, since it was just made for training the models, not for running them.

Thank you for the quick reply.
I assume I can adapt clmtools to pickle the model in Python format instead of saving it in JavaScript. Then I can preprocess each image the same way it does for training, but then apply the pretrained model to it to score it.
If that doesn't work, I would consider running it in a web page.

You can run the emotion classification in python, but for preprocessing the images I used for training, I manually annotated the points of the faces, so there's no python script to do that :/


Add section in README describing how to consume the component

Now that modaq is an npm package, the README should describe how to consume it as one.

Fixed by #99, but it should include text about what each prop does.


Parquet file fails to load into the ModelarDB

Timestamp column in parquet file should be in int64 format

invalid


[Docs] [Mail > Localizing Mailables] The code throws an exception: Method Illuminate\Mail\Mailer::locale does not exist.

Laravel Version
11
PHP Version
8.2
Database Driver & Version
No response
Description
The code in https://laravel.com/docs/11.x/mail#localizing-mailables, throws an exception: Method Illuminate\Mail\Mailer::locale does not exist.
Steps To Reproduce
I generate a Mailable (ThanksMail in this case) and send the mail in a class with this code:
Mail::locale('es')->send(new ThanksMail());

Hi there,
Thanks for reporting the problem you are encountering, but it looks like this is a question which may be better suited for a support channel. We only use this issue tracker for reporting bugs with the library itself. If you have a question on how to use functionality provided by this repository you can try one of the following channels:

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

However, this issue will not be locked and everyone is still free to discuss solutions to your problem!
Thanks.

@crynobone thanks, but is not a question, it's a bug in the documentation, i.e. code that doesn't and won't work. There is only in this repository the option to create an issue, in the documentation repository you can only make pull requests.

Your code isn't the same as documentation.

Excuse me, sorry, I just realised that to() returns a PendingMail object which does have a locale method.
My confusion was because I put the recipient in the Mailable and I thought that removing the to() would work.


Calculator example

Coverage decreased (-0.5%) to 92.286% when pulling 5c246fc81fd2fcf8feda63b8621559051cb28b22 on calculator-example into 7b95a8c683364c81141707a006a1efe84050e330 on master.

Coverage decreased (-0.5%) to 92.281% when pulling 5c246fc81fd2fcf8feda63b8621559051cb28b22 on calculator-example into 7b95a8c683364c81141707a006a1efe84050e330 on master.


Better name for CursorManager.updateCursors

Closing since no one came up with a better name

Fixed by #159


fix: param value assignment

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Error reporting from the UI

Have a button for users to send a non personally identifiable debug log when shit goes wrong
See https://njump.me/nevent1qvzqqqqqqypzq52yl6y07sjnceqga6yuulawdagpmpzen0zm69qpf5ywfz2c04d0qyv8wumn8ghj7mn0wd68ytnxd46zuamf0ghxy6t69uq32amnwvaz7tmwdaehgu3wdau8gu3wv3jhvtcqyrswu6jaskxzp0c6ss5efnsgyh0zkqzznpuyapjd57c3rptu2ugcwt9y8st

Allow viewing what is being sent for privacy reasons

Crash data should be collected, including screenshots, and allow the user to tap on Send to submit


Bugfix for order-by all sorted optimization

Codecov Report

Merging #8263 (51d69de) into master (e6330bb) will decrease coverage by 49.88%.
 Consider uploading reports for the commit 90a53d8 to get more accurate results

@@              Coverage Diff              @@
##             master    #8263       +/-   ##
=============================================
- Coverage     64.06%   14.17%   -49.89%
+ Complexity     4246       81     -4165
=============================================
  Files          1586     1586
  Lines         83399    83547      +148
  Branches      12641    12667       +26
=============================================
- Hits          53427    11842    -41585
- Misses        26129    70817    +44688
+ Partials       3843      888     -2955

Flag
Coverage Δ

unittests1
?

unittests2
14.17% <45.76%> (+0.07%)
:arrow_up:

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

Impacted Files
Coverage Δ

...ache/pinot/common/metadata/ZKMetadataProvider.java
0.00% <0.00%> (-20.15%)
:arrow_down:

...g/apache/pinot/common/utils/helix/HelixHelper.java
0.00% <0.00%> (-16.02%)
:arrow_down:

.../org/apache/pinot/core/plan/SelectionPlanNode.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...er/api/resources/PinotInstanceRestletResource.java
51.48% <50.00%> (-4.08%)
:arrow_down:

...e/pinot/broker/broker/helix/BaseBrokerStarter.java
72.58% <77.77%> (+0.69%)
:arrow_up:

...ntroller/helix/core/PinotHelixResourceManager.java
63.31% <82.55%> (+1.12%)
:arrow_up:

.../controller/helix/ControllerRequestURLBuilder.java
74.41% <100.00%> (+0.40%)
:arrow_up:

...ain/java/org/apache/pinot/core/data/table/Key.java
0.00% <0.00%> (-100.00%)
:arrow_down:

.../java/org/apache/pinot/spi/utils/BooleanUtils.java
0.00% <0.00%> (-100.00%)
:arrow_down:

.../java/org/apache/pinot/core/data/table/Record.java
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 1095 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 e6330bb...90a53d8. Read the comment docs.


Small convertTo fix

With the debug mode enabled, one failing test of https://github.com/Kotlin/dataframe/issues/713 was in convertTo.
It likely didn't cause any user issues, but it could prevent https://github.com/Kotlin/dataframe/pull/712, so best to solve it.
It was a relatively small fix. I renamed createEmptyColumn to createNullFilledColumn as that better reflects is behavior. Then, instead of creating the erroneous column, it throws an exception. This eliminates the need for the large boolean check in the convertToImpl function. Finally, since update cannot target non-existing columns, I needed to update the fill option of convertTo, to update or add columns depending on whether they were there already or not.

@Jolanrensen could you please check do we need to update a documentation for that? If yes, please include changes in the PR

I could understand very high-level what happens in changes, but it could be difficult in the future!

convertToImpl (as well as many of the other internal implementations of functions in DF) are hard to follow indeed. I hope I now made it at least a bit less complicated :)

Interestingly, adding kotlinLogging breaks the compiler plugin in the black box tests wherever it is used with:
java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory
@koperagen can we add this dependency to the plugin too?


Wrong output value written in Why Not to Use eval Section

In Why Not to Use eval Section
It is already mentioned that eval only executes in the local scope when it is being called directly and when the name of the called function is actually eval.
So, Here we are not calling it directly so it will not change the value of Global variable number.
Hence Global variable number will remain same i.e - 1

var number = 1;
function test() {
    var number = 2;
    var copyOfEval = eval;
    copyOfEval('number = 3');
    return number;
}
test(); // 2
number; // 3     (Here value of number will be 1 instead of 3)

Please Assign me this issue I want to contribute .

I've just tested this in node v6.4.0 and number ends up as 3, as expected. What version of JS/node are you using?

I am using this version node v7.3.0

see !

Actually if I run this from a file, I get the same result.
However running this in the node terminal or in Chrome produces the original result.
Javascript Garden doesn't technically cover node - and this seems to be a node feature.

I tried to fix the issue by cloning repo. locally but the problem that I encountered was that whatever changes I was doing inside the site folder those changes are not reflected in the git status one reason might be .gitignore file but what is the purpose of having site folder in git ignore file .
How one can send you a PR if doing any change inside site folder will not reflect in git status.


Some random cleanups of the python code

I can not reproduce the failure on travis locally. Not even if I run the docker commands from the travis file.
This is part of a more general clean up effort that also includes #323 and hopefully a redesign of our window handling as mentioned in #381.

Thanks


memlab is not accessible after installation

Hello Team,
I have installed the memlab on a CentOS machine and after installation, I am not able to access it.
Version used:
node: 16.19.1
npm: 8.19.3
Error:
/usr/bin/env: invalid option -- 'S'
Try '/usr/bin/env --help' for more information.
Please suggest how to fix the above-mentioned issue.
Refer to the screenshots.
Thank you!

Thank you @JacksonGL - the above-shared solution has fixed the issue.


Make TSDataset slice return TSDataset

🚀 Feature Request
Now the slice form TSDataset should also be TSDataset
Proposal

Change current behaviour of __getitem__, head, tail methods -- now it should return the corresponding TSDataset
Method __getitem__ should work using the following rules:

If 1 item -- [timestamp]
If 2 items -- [timestamp, feature]
If 3 items -- [timestamp, segment, feature]
timestamp = int, str, slice[int], slice[str]
segment/feature = str, list[str] or ":"

Remove methods loc, tsdataset_idx_slice
Fix all the places, where the slice of dataset is used including notebooks
Improve the existing tests

Test cases

Method head(10) works the same as ts[-10:]
Method tail(10) works the same as ts[:10]
Test all the possible cases of __getitem__

Additional context
No response

Slow down the work of the library, wait for better times


Add bag.read_avro

Involves a little copying of code from uavro, but stands alone.

[ ] Tests added / passed
[ ] Passes flake8 dask

I would not advise trying to add a to_avro counterpart to bag, since in general we cannot know whether the items in a bag all share the same schema.

@mrocklin , do you think it's reasonable to touch every file in the client part of the code, since each will have a different sync marker, and there's no way to load in chunks without that. The amount loaded for each file would be small, but this is exactly the case we are trying to avoid in the parquet case. The reads could be parallelised, at least.

@mrocklin , do you think it's reasonable to touch every file in the client part of the code

Obviously it would be nice to avoid this.  From what you say though it sounds like that's not possible?  Seem like an easy decision in that case :)

Already commented but want to add that according to the avro spec (and the reference implementation), every file will have a different sync marker.

Out of curiosity, how expensive would it be to also write avro?

how expensive would it be to also write avro?

Using fastavro, one file per partition, and with no checks around consistency of the items, it would be easy. The hardest part would be inferring the schema, I don't think fastavro has a way to do that automatically (in the test it is hard-coded).

Is it reasonable to ask users to provide the schema?
On Fri, Sep 21, 2018 at 9:43 AM, Martin Durant<EMAIL_ADDRESS>wrote:

how expensive would it be to also write avro?
Using fastavro, one file per partition, and with no checks around
consistency of the items, it would be easy. The hardest part would be
inferring the schema, I don't think fastavro has a way to do that
automatically (in the test it is hard-coded).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/pull/4000#issuecomment-423535164, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AASszIWwAX-XusEfhjF2iC-Zjui2yw93ks5udOz2gaJpZM4Wy7bp
.

Is it reasonable to ask users to provide the schema?

I think that @rmax and @ian-whitestone might have a better feeling for that.

Full disclosure: I haven't done any avro writing before.
I think it's reasonable, and I feel like it enforces good practices. With that said, schema inference could be a nice, separate feature, or an option when calling the write function, for those looking to prototype pipelines quickly. I know spark lets you dump a dataframe to avro without specifying a schema.

@mrocklin , I'd be happy to attempt both provided-schema and inference writing. The latter I would imagine using the first N records, where N is user-specified. Things like "enum" (category) would not be inferable.
Maybe that should be in a new PR, and maybe lower priority that dataframe.read_avro. I have already put a bit of work into uavro to update to the things learned in this PR so far.

Agreed.  No pressure from me on write_avro.  It was just a question.  I'd
be more than happy to wait until someone actually asks for it.
On Fri, Sep 21, 2018 at 10:56 AM, Martin Durant<EMAIL_ADDRESS>wrote:

@mrocklin https://github.com/mrocklin , I'd be happy to attempt both
provided-schema and inference writing. The latter I would imagine using the
first N records, where N is user-specified. Things like "enum" (category)
would not be inferable.
Maybe that should be in a new PR, and maybe lower priority that
dataframe.read_avro. I have already put a bit of work into uavro to update
to the things learned in this PR so far.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/pull/4000#issuecomment-423561442, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AASszM9dVc4og44ulgOPOJUDcCbuQjsaks5udP4ggaJpZM4Wy7bp
.

I think this is pretty simple and good like this, and I can come back for the other features in the future.

Sounds good to me
On Fri, Sep 21, 2018 at 7:38 PM, Martin Durant<EMAIL_ADDRESS>wrote:

I think this is pretty simple and good like this, and I can come back for
the other features in the future.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/pull/4000#issuecomment-423697326, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AASszL2DzNc9JgXoXN4ST5cqpJnuRHmUks5udXhsgaJpZM4Wy7bp
.


Carthage support -  schemes need to be set shared

Hi
Was hoping to use GPUImage with Carthage, but neither of the project's schemes are marked shared which is the way Carthage figure out where the frameworks are in the project.
*** Skipped building GPUImage2 due to the error:
Dependency "GPUImage2" has no shared framework schemes

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

Oops!  Sorry - I see someone has already submitted a PR with the schemes set to shared.


Task-6: BurpSuite

Task: Install and Set Up Burp Suite
📌 Objective:
Install Burp Suite, configure it to intercept and inspect HTTP requests from your browser.
🎯 Submission Format:

Submit the screenshot showing the intercepted HTTP request in Burp Suite. Ensure no sensitive information is visible.

🚨 Privacy Note:
Make sure the request you intercept doesn’t contain any personal information such as passwords, tokens, or private URLs.

✨ Bonus Tip:
Explore the HTTP history and Target tabs in Burp Suite to further inspect and analyze the captured data!

Happy intercepting! 😊

💡 Steps to Follow:

Install Burp Suite:

Download Burp Suite from the official site:
Burp Suite Download
Install Burp Suite on your system following the instructions provided on the website.

Configure Burp Suite as a Proxy:

Open Burp Suite and navigate to the Proxy tab.
In the Intercept sub-tab, click Intercept is on to start capturing HTTP requests.
Under Options, configure your browser to use Burp Suite as a proxy (usually by setting the proxy to <IP_ADDRESS>:8080).

Set Up Your Browser:

Open your browser and configure the proxy settings to route traffic through Burp Suite.
If using Firefox, go to Preferences > Network Settings > Manual proxy configuration and set HTTP Proxy to <IP_ADDRESS> and Port to 8080.
If using Chrome, you may need to configure the proxy via system settings or use an extension like FoxyProxy.

Intercept and Inspect an HTTP Request:

In your browser, visit any website (preferably one that doesn’t use HTTPS for easy interception).
Burp Suite will intercept the request. You can inspect the headers, body, and other details of the HTTP request.

Capture and Submit Your Output:

Take a screenshot showing Burp Suite’s Intercept tab with the HTTP request captured from your browser.

Also, submit your screenshots through a Google Drive link


tiledbsoma 1.11.4 pre-check

Following our established procedure

Second commit:
mamba upgrade -c conda-forge conda-smithy -n base
conda smithy rerender --commit auto


Completed assignment 1

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
Completion of assignment 1
What did you learn from the changes you have made?
Using Dask to calculate time series data
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
No
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
Not able to combine the creation of "Adj_close_lag_1" with the creation of "Close_lag_1" in combined line of code. When trying to add "Adj_close_lag_1" with ".apply()", the code failed to run and it suggested increasing the number of partition. To get around the problem I had to split the creation of "Adj_close_lag_1" column into separate line of code.
How were these changes tested?
Manually verified samples of the data including the moving averages
A reference to a related issue in your repository (if applicable)
Not applicable.
Checklist

[x] I can confirm that my changes are working as intended

A1 complete


#172: Release v0.1.68

@rultor merge

@rultor merge

@proshin-roman OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@proshin-roman Done! FYI, the full log is here (took me 2min)


[Efficiency] The InMemorySessionRepository uses Mutex instead of RWLock

In order to avoid threads waiting for reading when no writing is being done, all Mutexs must be changed for RWLocker. Furthermore, the vector of sids in the group_by_app map must have its own Locker in order to release the map once the vector is gotten.

Done in this commit


add asdf to Packages under README

Nice, thank you!
I don't know how asdf works, but is this command right:
asdf install asdf <version>

Should it be:
asdf install just <version>

Also, is it possible to do asdf install just <version> without doing asdf plugin add just? (Wondering if the command can be made shorter.)

In my experience it's best to think of asdf as a package manager manager.
asdf plugin add just is actually the shortened version of asdf plugin add just https://github.com/ggilmore/asdf-just.git. The reason there is a shortcut is because someone added it to the asdf community plugins repo.
asdf plugin add just to add the alias. asdf list all just to view possible versions. asdf install just <version> to get the specific version you want, and asdf global just <version> to make change the global just version.
So from that perhaps you could make the command there longer to include && asdf global just <version>, but most asdf users are used to that already.

Gotcha, thanks for the explanation!
Should it be asdf install just <version> then? (Currently it's asdf install asdf <version>.)

Whoops i see what you mean now i made a small typo.

Sorry that took a while, just got home :D. I hope it's useful to other asdf users.

Sweet, merging! Thank you!


ESP32c3 BLE RPA (Privay) Address doesn't change (IDFGH-9564)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
v5.1-dev-3778-g370e250072
Operating System used.
Linux
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
None
Development Kit.
esp32c3
Power Supply used.
USB
What is the expected behavior?
When advertising with an RPA addr type my ota ADDR should be a random rotating RPA addr.
What is the actual behavior?
The advertising address has the fixed value 7e:1e:1e:79:4f:f7. I've verified this is the physically transmitted address with nrf sniffer
7e:1e:1e:79:4f:f7 is an RPA with a constant prand rand part of 1e:1e:1e concatenated hash of ah(irk, 7e:1e:1e) == 79:4f:f7. Which makes sense based on irk setup here.
Why is rand part always the same? Why doesn't it change. Nimble calls BLE_HCI_OCF_LE_SET_RPA_TMO here to setup 15 minute ttl.
Steps to reproduce.

examples/bluetooth/nimble/bleprph
set-target esp32c3
main/main.c line 197; ble_gap_adv_start(BLE_OWN_ADDR_RPA_PUBLIC_DEFAULT...
Observe the ADV_IND addr is 7e:1e:1e:79:4f:f7

I've mostly tested with undirected ext_adv, but had no luck with any configuration (adv or directed).
Does the ESP32c3 actually support controller based RPA generated addresses? Am i somehow supposed to seed prand?
Debug Logs.
Frame 1894: 58 bytes on wire (464 bits), 58 bytes captured (464 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM1, id 0
Nordic BLE Sniffer
Bluetooth Low Energy Link Layer
    Access Address:
    Packet Header: 0x2060 (PDU Type: ADV_IND, ChSel: #2, TxAdd: Random)
        .... 0000 = PDU Type: 0x0 ADV_IND
        ...0 .... = Reserved: 0
        ..1. .... = Channel Selection Algorithm: #2
        .1.. .... = Tx Address: Random
        0... .... = Reserved: 0
        Length: 32
    Advertising Address: 7e:1e:1e:79:4f:f7 (7e:1e:1e:79:4f:f7)
    Advertising Data
        Flags
        16-bit Service Class UUIDs
        Device Name: nimble-bleprph
        Tx Power Level
    CRC: 0x9acc59

More Information.
No response

From few years ago, on bluedroid stack, i remember you can set only PUBLIC or PRIVATE own address. You cant tell host you want it to be RPA or STATIC, because in LL packet there is only TxAdd bit flag, which means private or public.

I don't think that can be case? When with privacy extensions enabled TxAdd=0 implies RPA? The physically captured broadcast package is absolutely and RPA address (i computed the address hash manually to verify).
The Link Layer may use resolvable private addresses or non-resolvable private
addresses for the advertiser’s device address (AdvA field) when entering the
Advertising State and using connectable and scannable undirected events.
BLUETOOTH CORE SPECIFICATION Version 5.4 | Vol 4, Part E, 7.8.5 LE Set Advertising Parameters command provides 4 options for own address.

TxAdd = 0 - means public address
I had to recolect what was the problem; well, beside of setting this value in bludroid i also had to call this function esp_ble_gap_config_local_privacy()
https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/bluetooth/esp_gap_ble.html#_CPPv432esp_ble_gap_config_local_privacyb

Im not sure if similar function is used in nimble thou.

Thanks for the suggestion. I'll take look. I'm assuming esp_ble_gap_config_local_privacy implies host mode privacy, but I'm specifically looking for controller based privacy on the esp32c3.

Traced that bluedriod code path. It essentially does HCI_LE_Set_Address_Resolution_-Enable. The analogous call in NimBLE happens in  ble_hs_pvcy_set_our_irk → ble_host_rpa_enabled. I've already made sure this is happening. :(. Thanks for the tip though. I'm a a bluedroid user will find this thread.

Since the controller is a binary blob I really need espressif's help for a fix.

I've verified nimble enables address resolution, sets a timer for address rotation, and adds the correct irk to resolve list.
I've verified the controller generates a valid a valid RPA address with a correctly computed hash.

... but as I mention the RPA is neither random nor changes.
Vol 6, Part B, 6.1:
The Link Layer shall set a timer determined by the Host. A new resolvable
private address shall be generated when the timer expires. If the Link Layer is
reset, a new resolvable private address shall be generated and the timer
started with any value in the allowed range.
As a terrible hack I've called r_lld_rpa_renew() symbol exported by the linker and implemented in rom(?), and have had some success getting RPA address to change, but this is clearly the wrong path.

Most recent findings: three bugs one of them mine:

Most importantly: The RPA address changes only when advertising starts. After restarting adverting every 30 seconds the RPA began to rotate. I'm not able to decipher the BLE spec well enough to know for sure this is working-as-intended, but its at least good enough.
However the RPA rotates every 15 minutes ignoring CONFIG_BT_NIMBLE_RPA_TIMEOUT even though a timeout is set: ble_hs_pvcy_ensure_started() →  ble_hs_pvcy_set_addr_timeout() → BLE_HCI_OCF_LE_SET_RPA_TMO. Controller Bug?
The random address always starts with a non-random fixed value. Controller Bug?

Oh, and I also alluded to the fact that nimble uses a hard coded IRK. I'd expect this will causing boning to more than one privacy enabled ESP device. More of a nimble issue, but I'll mention in here for anyone finding this thread. See micro-python for workaround to that issue. https://github.com/micropython/micropython/blob/cacc96d98c2a70dc7e5194331ea70746c39746ec/extmod/nimble/modbluetooth_nimble.c#L281

However the RPA rotates every 15 minutes ignoring CONFIG_BT_NIMBLE_RPA_TIMEOUT even though a timeout is set: ble_hs_pvcy_ensure_started() → ble_hs_pvcy_set_addr_timeout() → BLE_HCI_OCF_LE_SET_RPA_TMO. Controller Bug?

Manually sending HCI_LE_Set_Resolvable_Private_Address_-Timeout (Vol 4, Pt E, 7.8.45) in the sync callback fixes this. Unclear why. NimBLE calls this too. Maybe something to do with order of the commands being issued (e.g. must enable resolve list first)? So could be either a NimBLE bug or a controller bug?

Hi,
This thread was the only result in Google after copy pasting the MAC address I was getting on my two ESP32-S3 devices (with different manufacturers and form factors), while advertising using Controller-based RPA Public MAC address with NimBLE. I'm glad that I'm not the only one having the same issue.
@braiden the workaround you've published for the ESP32 is just for host-based privacy right? Unfortunately, my use-case requires controller-based privacy since I'm using the whitelist feature, which doesn't work with host-based privacy.
So, I can see this issue while enabling GAP advertising with the following line:
rc = ble_gap_adv_start(BLE_OWN_ADDR_RPA_PUBLIC_DEFAULT, NULL, BLE_HS_FOREVER,
			 &adv_params, rfble_gap_event, NULL);

This is making the MAC address to be set on my two devices to 7e:1e:1e:79:4f:f7. The resolution of the peer's RPA works perfectly though. I'm not very familiar with NimBLE stack nor Bluetooth in general, so I'm not sure if there's anything else that I need to do to setup the controller for using RPA or this is indeed a controller/host stack bug. Any guidance is appreciated.

I'm using device based privacy.  I may not have updated the bug with my latest findings:
Do not use ble_gap_adv_start with BLE_HS_FOREVER. Instead I restart advertisement ever 5 minutes. After this change, the device will rotate the address every 15 minutes. Remaining issues are:

The initial address is always 7e:1e:1e:79:4f:f7, but a new random address will be assigned in ~15 minutes.
The API to change the timeout to something shorter than 15 minutes didn't work.

This is reproducible on my side while using Controller-based privacy. Restarting the advertisement every 5 minutes, after 15 minutes the device will start advertising a new RPA address, but the initial address is always 7e:1e:1e:79:4f:f7. For my case changing the setting BT_NIMBLE_RPA_TIMEOUT won't have any effect because it is only applicable to host-based privacy.

We are seeing this issue on our ESP32-C3 devices as well with the same initial address: 7e:1e:1e:79:4f:f7.

thanks for report the problem,you can set RPA timeout with menuconfig:
(Top) → Component config → Bluetooth → NimBLE Options ->(5) RPA timeout in seconds

@achugbGL @devcexx
This is an issue (with the same initial address). could you please specify how this issue affects your usage? We will fix it ASAP.

@zhp0406, thanks for looking into this. Like @braiden mentioned above, the RPA timeout setting seems to be getting ignored for some reason. Regarding the initial address issue, the biggest problem for us is that when multiple devices using our firmware boot around the same time, they have conflicting addresses.

sorry for that,it will take some time for us to solve the issue(The initial address is always 7e:1e:1e:79:4f:f7). In the meantime, to avoid affecting your usage, you can set a different Identity Resolving Key (IRK) for each device. This way, the addresses will be different during the first initialization.
Note:
You can use the API *int ble_hs_pvcy_set_our_irk(const uint8_t irk) to set the IRK for each device.

Thank you! Appreciate your attention to this issue

Hi @achugbGL ,
The attached patch has a change to generate a new IRK for each device on boot without the need for user to call any API. Please help check if it works for you. The patch should go in $IDF_PATH/components/bt/host/nimble/nimble path.
0001-Added-change-to-generate-unique-IRK-based-on-chip-ma.txt

Since there is no response from the user, closing the issue, if there will be any questions or issues feel free to reopen or create a new issue. Cheers.


[3.3] failed to dump v3 code object

When I use rocm 3.3 to dump TensorFlow data, it pops below error.
Does that mean it does not support V3 code object for now?
error(4096) "QueryKernelName(), Error: V3 code object detected - code objects tracking should be enabled

You may add option "--obj-tracking on" to enable this feature.

You may add option "--obj-tracking on" to enable this feature.
Thanks for your reply.

I could continue with the object option. but the number of kernel increases a lot.

without the option, 62 kernel are tracked with pmc data
with the option, 76481 kernel are traced with pmc data

what's different in doing profiling when the option is enabled?
Thanks.

Hi zjunweihit, coudl you explain what do you mean under:

without the option, 62 kernels are tracked with pmc data
with the option, 76481 kernels are traced with pmc data

What option do you mean?
My understanding that without  "--obj-tracking on" option it is crashed, doesn't it?

"--obj-tracking on" will be enabled in 3,6 by default.
The option enabling V3 code object support.

Hi zjunweihit, coudl you explain what do you mean under:

without the option, 62 kernels are tracked with pmc data
with the option, 76481 kernels are traced with pmc data

What option do you mean?
My understanding that without "--obj-tracking on" option it is crashed, doesn't it?

I'm running a tensorflow app. When I use rocprofiler with --obj-tracking on to get PMC data, it could trace more kernel in the output file. otherwise, there are only 62 kernels tracked in the output file.
So I guess it not only enable v3 code object support, but also track more kernels.
Is that right?

@zjunweihit, when you don't use --obj-tracking on to get PMC data, at that time it got crashed when trying to execute kernel with V3 code object so no kernels dump after that. But with --obj-tracking on you full Application running with rocprof so now you are able to capture more kernels.

@zjunweihit, when you don't use the option --obj-tracking on to get PMC data, at that time it got crashed while executing kernel with V3 code object. So no kernels dump after rocprof crash. But with the option --obj-tracking on your full Application running with rocprof without any issue so now you are able to capture more kernels.

Exactly.
Sorry I missed one thing to comment. I did some hack here to set invalid data.
If no --obj-tracking on, rocprofiler could not get the data there, so I set the value as -1, then the profiler could continue the work with invalid data.
In this case, I could run the profiler both with and without --obj-tracking on.
And the results are different.
However, I think it a bit more, maybe some kernels didn't get tracked at all during profiling(even no invalid data then).
  166       ############ Junwei ########################
  167       #print ("--> each key: {}, {}".format(ind, entry))
  168       dispatch_number = entry['Index']
  169       if ind != dispatch_number: fatal("Dispatch #" + ind + " index mismatch (" + dispatch_number + ")\n")
  170       #val_list = [entry[var] for var in var_list]
  171       ############ Junwei ########################
  172       val_list = []
  173       for var in var_list:
  174         if var in entry.keys():
  175           val_list.append(entry[var])
  176         else:
  177           val_list.append('-1')
  178       ############################################


Error: Cannot find symbol

When I install flutter by
flutter pub add flutter_serial_communication
and
run flutter run
It show error
.pub-cache/hosted/pub.dev/flutter_serial_communication-0.2.7/android/src/main/java/id/farellsujanto/flutter_serial_communication/PluginConfig.java:4: error: cannot find symbol
    public static final String INTENT_ACTION_GRANT_USB = BuildConfig.LIBRARY_PACKAGE_NAME + ".GRANT_USB";
                                                         ^
  symbol:   variable BuildConfig
  location: class PluginConfig

Any updates regarding this?

Same issue here :(

Hi guys, sorry for the late reply. Please update to v0.2.8. Thanks!


fix: equinix_fabric_cloud_router ignore empty order block and set max 1 for project block

fix #428
Add MaxItems:1 for project argument. Although this is generally not a problem in terraform, it does affect the way the Pulumi bridged plugin is generated. All fields of the type set without a MaxItems or MaxItems different to 1 are generated with a plural noun: project --> projects

Codecov Report
Attention: 13 lines in your changes are missing coverage. Please review.

Comparison is base (26b2f3d) 60.11% compared to head (e6f8240) 59.87%.
Report is 22 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #429      +/-   ##
==========================================
- Coverage   60.11%   59.87%   -0.25%
==========================================
  Files          99       99
  Lines       20045    20035      -10
==========================================
- Hits        12051    11995      -56
- Misses       7691     7740      +49
+ Partials      303      300       -3

Files
Coverage Δ

equinix/errors.go
86.95% <100.00%> (+0.59%)
:arrow_up:

equinix/fabric_cloud_router_schema.go
100.00% <100.00%> (ø)

equinix/helpers_device.go
82.26% <97.14%> (-2.65%)
:arrow_down:

equinix/data_source_metal_device.go
88.33% <89.47%> (-0.71%)
:arrow_down:

equinix/resource_fabric_cloud_router.go
9.69% <0.00%> (-0.05%)
:arrow_down:

equinix/resource_metal_device.go
78.63% <87.50%> (-0.45%)
:arrow_down:

... and 8 files with indirect coverage changes

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

Local test:
make build
mv terraform-provider-equinix /Users/${USERNAME}/.terraform.d/plugins/developer/equinix/equinix/9.0.0/darwin_amd64
cd examples/fabric/v4/cloudRouter

Edit file terraform.tf to use local binary
required_providers {
    equinix = {
        source = "developer/equinix/equinix"
        version = "9.0.0"
    }
...

Remove or comment order block in main.tf
  # order {
  #   purchase_order_number= var.purchase_order_number
  # }

Now I can move forward and get a different error, in my case, my account has a limit of FCR devices,  but I don't see the "reason": "Invalid purchase order number" error anymore. You can see in the screenshot the request doesn't include an empty order argument

The same test now including the order block:


Improve test coverage

Coverage increased (+0.9%) to 95.575% when pulling f82a556fb10cc5daae5587574567acf7b3f92b4c on improve-test-coverage into aeffbd32c74391cce9e4132e57e60a518dd31b46 on master.

Coverage increased (+0.9%) to 95.575% when pulling f82a556fb10cc5daae5587574567acf7b3f92b4c on improve-test-coverage into aeffbd32c74391cce9e4132e57e60a518dd31b46 on master.

Coverage increased (+0.9%) to 95.575% when pulling f82a556fb10cc5daae5587574567acf7b3f92b4c on improve-test-coverage into aeffbd32c74391cce9e4132e57e60a518dd31b46 on master.

Coverage increased (+0.9%) to 95.575% when pulling f82a556fb10cc5daae5587574567acf7b3f92b4c on improve-test-coverage into aeffbd32c74391cce9e4132e57e60a518dd31b46 on master.

Coverage increased (+1.7%) to 96.421% when pulling c6d1c726948fb6a2bc32a9340da5930f52fee9e5 on improve-test-coverage into aeffbd32c74391cce9e4132e57e60a518dd31b46 on master.

Coverage increased (+1.7%) to 96.421% when pulling c6d1c726948fb6a2bc32a9340da5930f52fee9e5 on improve-test-coverage into aeffbd32c74391cce9e4132e57e60a518dd31b46 on master.

Coverage increased (+1.7%) to 96.421% when pulling c6d1c726948fb6a2bc32a9340da5930f52fee9e5 on improve-test-coverage into aeffbd32c74391cce9e4132e57e60a518dd31b46 on master.


mini.tabline: colored icons

Contributing guidelines

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

Module(s)
tabline
Description
The mini.icons module allows icons to be colored using MiniIcons* highlight groups. However, mini.tabline does not actually use these highlights. It would be nice if there was an option for that.
Note that since the tabline often uses a different background color, it may be impossible to make the icons look right with the default highlight groups. This could be solved by having separate highlights for each combination of tabline and icon highlight group: MiniTablineCurrentIconRed, etc.
Attempted workaround
I tried to implement this myself by using a custom MiniTabline.config.format function which adds highlight specifiers. However, it turns out that mini.tabline escapes percent signs, which makes it impossible to use any tabline formatting in the result. So another option, which could also have other use-cases, would be to allow not escaping the string returned by MiniIcons.config.format.

Thanks for the suggestion, Adam! Glad you still use 'mini.nvim' :)
Similar suggestion was discussed in #153. Those are indeed slightly different cases: 'nvim-web-devicons' has separate highlight group for each icon while 'mini.icons' intentionally uses fixed set of highlight groups. So indeed defining own set of highlight groups is possible here.
Having it be possible to achieve with config.format is indeed a good approach. So forced % escaping I'd say even a bug and should be done inside default_format() (not after format).
There is still an issue, though: highlighting in tabline/statusline/winbar can only be done as a "switch" (i.e. "highlight all characters to the right with this highlight group). As tabs in tabline can change colors interactively, adding colors to icons needs to also "reset" added color to the highlight group of the tab, which is not passed to format currently. But I think the use case with 'mini.icons' is reasonable enough for this to be added.
I'll take a look.

I thought I have resolved this, but I didn't take into account that tab width is computed based on the config.format output. If it contains any special constructs (like %#HLname#, for example), it interferes with computing which tabs should be shown.
This needs more time and effort, I am afraid.

I am afraid I have to close with resolution "'mini.tabline' can have only predefined set of full tab colors". Another way to put it is "an output of config.format will be treated strictly as text".
The full explanation is in 70862cc80182dfb6ff6f0e869c439011e4e874b8 commit message. TL;DR:

Allowing colored icons requires respecting special 'statusline' like constructs in output of config.format.
It conflicts with the requirement of being able to partially show a tab.
Together with other complexity issues I think it is reasonable to document this as a known limitation.

I guess I’ll have to configure my tabline manually now. :P

It's a bit more tedious than statusline specifically for the reason mentioned here: the content can not fit in the available width and there needs to be some truncating going on. So beware.


Enable config flow for Luftdaten

Description:
Enable the configuration of Luftdaten stations through the frontend.
Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#7393
Example entry for configuration.yaml (if applicable):
luftdaten:
  sensor_id: SENSOR_ID
  sensors:
    - p1

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass

If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[x] New dependencies have been added to the REQUIREMENTS variable (example).
[x] New dependencies are only imported inside functions that use them (example).
[x] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[x] New files were added to .coveragerc.

If the code does not interact with devices:

[x] Tests have been added to verify that the new code works.

Luftdaten sensors are no longer exposed to HomeKit after this change.

No issue reporting on PRs


Update sass.md, You need to specify 'style-loader' instead of 'style'

React Boilerplate
Thank you for contributing! Please take a moment to review our contributing guidelines
to make the process easy and effective for everyone involved.
Please open an issue before embarking on any significant pull request, especially those that
add a new library or change existing tests, otherwise you risk spending a lot of time working
on something that might not end up being merged into the project.
Before opening a pull request, please ensure:

[ ] You have followed our contributing guidelines
[ ] double-check your branch is based on dev and targets dev
[ ] Internal code generators and templates are updated (if necessary)
[ ] Pull request has tests (we are going for 100% coverage!)
[ ] Code is well-commented, linted and follows project conventions
[ ] Documentation is updated (if necessary)
[ ] Description explains the issue/use-case resolved and auto-closes related issues

Be kind to code reviewers, please try to keep pull requests as small and focused as possible :)
IMPORTANT: By submitting a patch, you agree to allow the project
owners to license your work under the terms of the MIT License.

@proserve Thanks for contributing.
Please review the PR template (above).

You have followed our contributing guidelines
double-check your branch is based on dev and targets dev


[tf] Move terraform to use dynamic configs

Motivation
This is a doozy. This moves us to use the new dynamic-config-builder. I think this is in a pretty good state but will likely need some more tweaks to work across all the deployment environments.
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
terraform deploy to personal workspace

So awesome!!
@bors-libra r+

:pushpin: Commit f8a1698 has been approved by sherry-x

:hourglass: Testing commit f8a169816844493e55bd6081f74611215a262762 with merge 693b26e33f6ffeb84c1257cb6fa0c99049b00e41...

:sunny: Test successful - checks-circle_commit_workflow
Approved by: sherry-x
Pushing 693b26e33f6ffeb84c1257cb6fa0c99049b00e41 to master...


Beautify model arguments

Hello guys, I've just started using this awesome package, but I found out the WP fields are quite awful :(
  "ID" => 3
    "post_author" => 1
    "post_date" => "2016-01-30 16:50:25"
    "post_date_gmt" => "-0001-11-30 00:00:00"
    "post_content" => ""
    "post_title" => "Auto Draft"
    "post_excerpt" => ""
    "post_status" => "auto-draft"
    "comment_status" => "open"
    "ping_status" => "open"
    "post_password" => ""
    "post_name" => ""
    "to_ping" => ""
    "pinged" => ""
    "post_modified" => "2016-01-30 16:50:25"
    "post_modified_gmt" => "-0001-11-30 00:00:00"
    "post_content_filtered" => ""
    "post_parent" => 0
    "menu_order" => 0
    "post_type" => "post"
    "post_mime_type" => ""
    "comment_count" => 0
    "meta" => []
  ]

The post_title field instead of title kills me a little bit.
Would you approve something generic to translate this ugly field names into something more legible? Maybe an array located on every model with a trait to make the conversions?
If you agree with me I can work on this :)

Hi @josec89! I agree with you and this is something that make me fell bad hehe. post_title sounds bad. These fields are default from Wordpress but I think we can change it. We must provide both field names because compatibility purposes (post_title and title).
We can work on this  together. Any help is welcome. Thanks!

Hmmm I think this won't be as easy as I firstly though:
I think we need to use Eloquent accessors (https://laravel.com/docs/5.1/eloquent-serialization#appending-values-to-json)
So we'd need to add $append = [<all the new field names>] and one method for every new field.
Something like:
    protected $appends = ['title'];

    public function getTitleAttribute()
    {
        return $this->post_title;
    }

What do you think?

Yes, accessors  is the best fit  with append properties. I think now we can map all post fields (and authors, etc) the original names and what's the best replace for each one. I'm on mobile now, sorry :-(

Done! #58
Thanks for the support @josec89


workaround for making tests pass

subj

It absolutely doesn't enforce Python 2 and is supposed to stay backwards compatible (unless I did it wrong).

From what I understand "py.test" could be either

You are right. On a system with Python 3 only, I believe it's possible to have a py.test-3.x executable and a py.test symlink to it. As I said above, since my system has both versions of Python, py.test points to the Python 2 version of pytest, while py.test3 points to the Python 3 version.
All I've tried to do was to catch the exception I was getting on my system, since it doesn't have the hardcoded py.test-2.7 or py.test-3.3 executable, and try the more generic py.test and py.test3 names.


Add MultiWOZ 2.4 DST evaluation

We aim to conduct DST evaluation on the MultiWOZ 2.4 corpus. This PR shows our proposed extension to the existing code to achieve this.

Oops, meant to create a PR in my fork. I'll create a new PR here once it is reviewed in my fork.

@smartyfh I would greatly appreciate your comments on this!

@smartyfh I would greatly appreciate your comments on this!

Thank you, Weixuan. That would be great. Please let me know what I can do.

@smartyfh I would greatly appreciate your comments on this!

Thank you, Weixuan. That would be great. Please let me know what I can do.

@smartyfh Thanks! It would be great if you could have a look at our dataset loading logic and let us know if there is anything that we may have missed/done differently. Especially, your insights on whether slots with value none should be dropped (https://github.com/WeixuanZ/MultiWOZ_Evaluation/blob/55fb7c26a7b6ecc6d62b7a068c1f890bc9e3f2e4/mwzeval/utils.py#L214).

@smartyfh I would greatly appreciate your comments on this!

Thank you, Weixuan. That would be great. Please let me know what I can do.

@smartyfh Thanks! It would be great if you could have a look at our dataset loading logic and let us know if there is anything that we may have missed/done differently. Especially, your insights on whether slots with value none should be dropped (https://github.com/WeixuanZ/MultiWOZ_Evaluation/blob/55fb7c26a7b6ecc6d62b7a068c1f890bc9e3f2e4/mwzeval/utils.py#L214).

I don't fully understand why the NONE value should be removed. When we evaluate the performance of DST, we should take all slots into account. It seems to be easier to keep all the slots and their values. If we remove the NONE values, we need to take care of post-processing when calculating evaluation metrics.

@smartyfh I would greatly appreciate your comments on this!

Thank you, Weixuan. That would be great. Please let me know what I can do.

@smartyfh Thanks! It would be great if you could have a look at our dataset loading logic and let us know if there is anything that we may have missed/done differently. Especially, your insights on whether slots with value none should be dropped (https://github.com/WeixuanZ/MultiWOZ_Evaluation/blob/55fb7c26a7b6ecc6d62b7a068c1f890bc9e3f2e4/mwzeval/utils.py#L214).

I don't fully understand why the NONE value should be removed. When we evaluate the performance of DST, we should take all slots into account. It seems to be easier to keep all the slots and their values. If we remove the NONE values, we need to take care of post-processing when calculating evaluation metrics.

Hi @smartyfh , thanks so much for engaging! To clarify, does the none value indicate that the user did not yet mention a slot value or is it a special value that indicates slot "deletion"? Our reason to "remove" it is that the authors of D3ST (https://arxiv.org/pdf/2201.08904.pdf) ignored it during pre-processing and so we ought to do so during post-processing. To make the evaluator implementation agnostic, should we add a flag that states whether none should be removed or not? In this way, future users who did not pre-process their data to remove none slot values will be able to fairly evaluate their models too?

@smartyfh I would greatly appreciate your comments on this!

Thank you, Weixuan. That would be great. Please let me know what I can do.

@smartyfh Thanks! It would be great if you could have a look at our dataset loading logic and let us know if there is anything that we may have missed/done differently. Especially, your insights on whether slots with value none should be dropped (https://github.com/WeixuanZ/MultiWOZ_Evaluation/blob/55fb7c26a7b6ecc6d62b7a068c1f890bc9e3f2e4/mwzeval/utils.py#L214).

I don't fully understand why the NONE value should be removed. When we evaluate the performance of DST, we should take all slots into account. It seems to be easier to keep all the slots and their values. If we remove the NONE values, we need to take care of post-processing when calculating evaluation metrics.

Hi @smartyfh , thanks so much for engaging! To clarify, does the none value indicate that the user did not yet mention a slot value or is it a special value that indicates slot "deletion"? Our reason to "remove" it is that the authors of D3ST (https://arxiv.org/pdf/2201.08904.pdf) ignored it during pre-processing and so we ought to do so during post-processing. To make the evaluator implementation agnostic, should we add a flag that states whether none should be removed or not? In this way, future users who did not pre-process their data to remove none slot values will be able to fairly evaluate their models too?

Hi @alexcoca, my pleasure. NONE is not a special value. When either a slot is not mentioned or its value has been deleted, the value is NONE. "Not Mentioned" is another value that is also used to indicate ''not mentioned'' slots. So it is safe to change "not mentioned" to "none". Regarding the last question, it sounds like a good option to add a flag. Cheers!

@smartyfh I would greatly appreciate your comments on this!

Thank you, Weixuan. That would be great. Please let me know what I can do.

@smartyfh Thanks! It would be great if you could have a look at our dataset loading logic and let us know if there is anything that we may have missed/done differently. Especially, your insights on whether slots with value none should be dropped (https://github.com/WeixuanZ/MultiWOZ_Evaluation/blob/55fb7c26a7b6ecc6d62b7a068c1f890bc9e3f2e4/mwzeval/utils.py#L214).

I don't fully understand why the NONE value should be removed. When we evaluate the performance of DST, we should take all slots into account. It seems to be easier to keep all the slots and their values. If we remove the NONE values, we need to take care of post-processing when calculating evaluation metrics.

Hi @smartyfh , thanks so much for engaging! To clarify, does the none value indicate that the user did not yet mention a slot value or is it a special value that indicates slot "deletion"? Our reason to "remove" it is that the authors of D3ST (https://arxiv.org/pdf/2201.08904.pdf) ignored it during pre-processing and so we ought to do so during post-processing. To make the evaluator implementation agnostic, should we add a flag that states whether none should be removed or not? In this way, future users who did not pre-process their data to remove none slot values will be able to fairly evaluate their models too?

Hi @alexcoca, my pleasure. NONE is not a special value. When either a slot is not mentioned or its value has been deleted, the value is NONE. "Not Mentioned" is another value that is also used to indicate ''not mentioned'' slots. So it is safe to change "not mentioned" to "none". Regarding the last question, it sounds like a good option to add a flag. Cheers!

Thanks so much @smartyfh !

Hi all!
I was interested in using the MultiWOZ 2.4 evaluator implemented here. For my understanding, is the implementation in this PR is complete & correct, and any remaining changes would be API and documentation improvements? If so I may try and use it, and could possibly even help resolve remaining issues if the PR is no longer active.
Thanks all for building such a useful tool! The discussion here has also been helpful for my understanding of the evaluation process.

@kingb12 This sounds like a great idea. Let's have a fresh look at the work and maybe ask one or two additional MultiWOZ experts to validate the work to be extra sure the evaluator is correct. @Tomiinek , apart from yourself, who do you think would be suited to sing off this evaluation PR?

Hey guys,
I think I do not have enough capacity to meaningfully and thoroughly review (it has been a long time since I did something related to dialogs). If you guys are going to test it and finish the remaining bits, I would be more than happy to merge it ... just ping me.
Maybe @tuetschek, @vojtsek or @oplatek could chimme in


ci(actions): Setup workflow actions

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


Generate Updates

Currently the transactions generated in the LEDGER STS Trace generator do not produce any Updates.
Add generation of Updates to genTxBody (in test/Generator/Utxo.hs)

closing and making this a part of #1034


unable to import jason

whenever i try to import jason in rx resume webapp/website nothing happens
Could you pl guide to resolve the issue as without it updsting the resume is just like making it again.
i Have the json file with me as well as the pdf of the same.
Kindly help
Swati Middha.

Hi Amruth,
I too am unable to import the resume in json format, I attempted in multiple browsers too and its a blank screen without any error message. Could you please correct it soon.
Thanks,
Mohan

Hi !
If you created the json via RXResume, you have to select "Import from Reactive Resume" then, select your json file.
Cheers

Hi Team,
Thanks for your response, I used the json file created using the Rxresume portal however it remains blank.
Thanks,
Mohan

From: MushPsykotik @.>
Sent: Monday, February 7, 2022 6:39 PM
To: AmruthPillai/Reactive-Resume @.>
Cc: Mohan Murali Kumar @.>; Comment @.>
Subject: Re: [AmruthPillai/Reactive-Resume] unable to import jason (Issue #607)
Hi !
If you created the json via RXResume, you have to select "Import from Reactive Resume" then, select your json file.
Cheers
—
Reply to this email directly, view it on GitHubhttps://github.com/AmruthPillai/Reactive-Resume/issues/607#issuecomment-1031451293, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFCDQFHS3MNNXIPLBYMERITUZ7AADANCNFSM5MTPBHWQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID: @.***>


Fix: use dvh to fix iOS sidebar style issue

This pr:

fix: #882 . Using dvh to replace vh will fix this bug.
fix wrong style jsx typing

In order to make sure it 100% compatible with old and new browser, I use style jsx here.

https://caniuse.com/viewport-unit-variants
safari 15.4 start support dvh, maybe there is a better way to resolve this issue.


isItMe and getTeam improved

Made the 2 slightly faster

Please tab the stuff within the function that you didn't.

What do you mean? How?

I'll do it.

Ok! So, I know most of the stuff I need to know, now off to rewriting half of the code! XD (Ok, it isn't that bad, it's great!)

lol, I agree a lot of things can be cleaned up.


Auto  deploy from Travis.

Currently, I need to do a deploy myself. It would be good if travis can be setup to auto-deploy. I am not sure whether it is possible through some webhooks.

@saurabhnanda @ajnsit @psibi. Is it possible to auto-deploy from travis directly. I have not done this but I guess this should be possible if we set up travis appropriately.

https://gist.github.com/willprice/e07efd73fb7f13f917ea might be relevant investigate.

First we need to move to a stack based build. The ppa for stack is not yet white listed. So we wait for that to happend before attempting this issue.

I think it's whitelisted: https://github.com/travis-ci/apt-source-whitelist/pull/7 ?

On Fri, Sep 09, 2016 at 10:30:47PM -0700, Sibi wrote:

I think it's whitelisted: https://github.com/travis-ci/apt-source-whitelist/pull/7 ?

Great. Can you get this issue fixed? The steps involved are

move from cabal build to stack build: To improve speed you can

cache .stack-work or ~/.stack or any such relevant directory.
pre-install the right ghc version from hvr (I think that is already done).

In the after success field, put in a stack exec website deploy
(with necessary modification to use the security token based push.

May be you can start by just moving the build to stack. I am unsure about https://gist.github.com/willprice/e07efd73fb7f13f917ea. Will it deploy for travis builds from pull requests as well. That would be unacceptable (I do not see where it ensure that the pushes to the master repository will only be deployed

Sure, I can look into it. But I don't think I have proper privilege access for this repository in Github and for changing the settings in Travis.

I just made you an owner of this repo. But before you enable auto deploy make sure that deploys do not happen from pull requests.

Also I recommend that you first push to your private branch and explicitly send a pull request. This way you are sure that the changes that you make are not breaking. When travis passed you can push onto develop on the main repo

Here's the config I wrote for Hakyll and Travis:
https://github.com/sakshamsharma/acehack/blob/master/.travis.yml
Running a bit busy, but you can copy the code almost verbatim from here (along with one or two scripts in the parent folder).


How to clickable table row and return the object data?

How to clickable table row and return the object data?
And how to add some button on table cell?

I already answered a similar question, look in the closed issues

can you give a link?

Example - How to draw components and elements in table cell https://codepen.io/olton/pen/mdRwqBB

To create a clickable row you must use live event binding/delegation
$(table).on("click", "tr", function(event){
    ...
})

thank you for the example.


covid-19

As the pandemic grows worldwide and developers working from home might have some extra time, we can have a tag for covid-19 for open issues to encourage contributions and focus efforts.

There are only 95 open issues with this label, and it doesn't seem like something that will have long term relevance.


Escape to close CQUI options panel

I keep trying to close CQUI options with Escape, which is doing nothing.  Then I look for an X and it's not there.  Finally I click the minimap button again.  Sure, I could train myself to get it right every time, but it'd be cool if the other two common methods of exiting a panel were available.

Yeah, it's just something I've been dragging my feet on, definitely a thing that should have been there from the start


problem with python and homebrew

HI,
thanks for your code, it saved my life!
I stll have something weird happening with my code.
The code (https://github.com/aflux/neutrino/) links on libPythonQt  (http://pythonqt.sourceforge.net/) which links on Python.
I installed homebrew and compiled pythonqt by hand
Then I compile my code and run both macdeployqt and macdeployqtfix.py and everything is fine except the Python framework linked by pythonqt
As you can see the dependencies of both Pythonqt libs are still pointing to /usr/local/Frameworks (although Python Frameworks get copied in my .app)
It should be macdeployqt job to fix this, but it seems it has a lot of problems....
I ended up fixing this with install_name_tool, but I was wondering if it was possible to add a hook to your script to fix this issue too.
many thanks!

These are the dependencies of Pytohnqt:
otool -L lib/libPythonQt.dylib
lib/libPythonQt.dylib:
	libPythonQt.1.dylib (compatibility version 1.0.0, current version 1.0.0)
	/usr/local/Frameworks/Python.framework/Versions/2.7/Python (compatibility version 2.7.0, current version 2.7.0)
	/usr/local/opt/qt5/lib/QtWidgets.framework/Versions/5/QtWidgets (compatibility version 5.5.0, current version 5.5.0)
	/usr/local/opt/qt5/lib/QtGui.framework/Versions/5/QtGui (compatibility version 5.5.0, current version 5.5.0)
	/usr/local/opt/qt5/lib/QtCore.framework/Versions/5/QtCore (compatibility version 5.5.0, current version 5.5.0)
	/System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration (compatibility version 1.0.0, current version 1.0.0)
	/System/Library/Frameworks/IOKit.framework/Versions/A/IOKit (compatibility version 1.0.0, current version 275.0.0)
	/System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL (compatibility version 1.0.0, current version 1.0.0)
	/System/Library/Frameworks/AGL.framework/Versions/A/AGL (compatibility version 1.0.0, current version 1.0.0)
	/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 104.1.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1213.0.0)

otool -L lib/libPythonQt_QtAll.dylib
lib/libPythonQt_QtAll.dylib:
	libPythonQt_QtAll.1.dylib (compatibility version 1.0.0, current version 1.0.0)
	/usr/local/Frameworks/Python.framework/Versions/2.7/Python (compatibility version 2.7.0, current version 2.7.0)
	libPythonQt.1.dylib (compatibility version 1.0.0, current version 1.0.0)
	/usr/local/opt/qt5/lib/QtWebKitWidgets.framework/Versions/5/QtWebKitWidgets (compatibility version 5.5.0, current version 5.5.0)
	/usr/local/opt/qt5/lib/QtWidgets.framework/Versions/5/QtWidgets (compatibility version 5.5.0, current version 5.5.0)
	/usr/local/opt/qt5/lib/QtGui.framework/Versions/5/QtGui (compatibility version 5.5.0, current version 5.5.0)
	/usr/local/opt/qt5/lib/QtCore.framework/Versions/5/QtCore (compatibility version 5.5.0, current version 5.5.0)
	/System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration (compatibility version 1.0.0, current version 1.0.0)
	/System/Library/Frameworks/IOKit.framework/Versions/A/IOKit (compatibility version 1.0.0, current version 275.0.0)
	/usr/local/opt/qt5/lib/QtWebKit.framework/Versions/5/QtWebKit (compatibility version 5.5.0, current version 5.5.0)
	/usr/local/opt/qt5/lib/QtNetwork.framework/Versions/5/QtNetwork (compatibility version 5.5.0, current version 5.5.0)
	/usr/local/opt/qt5/lib/QtSvg.framework/Versions/5/QtSvg (compatibility version 5.5.0, current version 5.5.0)
	/usr/local/opt/qt5/lib/QtOpenGL.framework/Versions/5/QtOpenGL (compatibility version 5.5.0, current version 5.5.0)
	/usr/local/opt/qt5/lib/QtPrintSupport.framework/Versions/5/QtPrintSupport (compatibility version 5.5.0, current version 5.5.0)
	/usr/local/opt/qt5/lib/QtMultimediaWidgets.framework/Versions/5/QtMultimediaWidgets (compatibility version 5.5.0, current version 5.5.0)
	/usr/local/opt/qt5/lib/QtMultimedia.framework/Versions/5/QtMultimedia (compatibility version 5.5.0, current version 5.5.0)
	/System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL (compatibility version 1.0.0, current version 1.0.0)
	/System/Library/Frameworks/AGL.framework/Versions/A/AGL (compatibility version 1.0.0, current version 1.0.0)
	/usr/local/opt/qt5/lib/QtXmlPatterns.framework/Versions/5/QtXmlPatterns (compatibility version 5.5.0, current version 5.5.0)
	/usr/local/opt/qt5/lib/QtSql.framework/Versions/5/QtSql (compatibility version 5.5.0, current version 5.5.0)
	/usr/local/opt/qt5/lib/QtXml.framework/Versions/5/QtXml (compatibility version 5.5.0, current version 5.5.0)
	/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 104.1.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1213.0.0)

Hi @iltommi, happy to hear that macdeployqtfix is useful for you.
It should be easy to extend macdeployqtfix so that it copies and corrects every shared library found in the bundle, provided that those paths are paths of Qt libraries.
So for your specific case, the Qt libraries on which libPythonQt.dylib and libPythonQt_QtAll.dylib  depend would be copied (if needed), and their rpath corrected, etc.
I'll do it when i have a bit of time...
Stay tuned :wink:

This seems to be happening for me with some Homebrew-specific libraries that macdeployqt fails to copy.  Can the tool be run against a non-qt prefix?
Furthermore, QtXml seems to be having a linking issue as well, requiring a subsequent run of the tool.

@tresf  made some fixing check the latest version. I'm closing the issue.
If you still have problems, maybe it's better to open another issue

@tresf made some fixing check the latest version. I'm closing the issue.

Yes, the fix I had employed (not macdeployqtfix related) was to roll our project's Homebrew back to Qt 5.5, using brew install qt55 since the underlying linking bugs in Qt 5.6.1 seemed to be the major cause of the linking issues.  Once this was done, we removed macdeployqtfix from our source tree and used the built-in linking utility combined with some of our existing install_name_tool post-build tasks.
To be clear I've made no Python code changes to this -- macdeployqtfix -- project.

@tresf *I made some fixing check the latest version. I'm closing the issue.

Disregard my previous comment.  I understand the context of your comment now.

Ok thanks for the clarification
Le 7 juil. 2016 20:23, "Tres Finocchiaro"<EMAIL_ADDRESS>a
écrit :

@tresf https://github.com/tresf made some fixing check the latest
version. I'm closing the issue.
Yes, the fix I had employed (not macdeployqtfix related) was to roll our
project's Homebrew back to Qt 5.5, using brew install qt55 since the
underlying linking bugs in Qt 5.6.1 seemed to be the major cause of the
linking issues. Once this was done, we removed macdeployqtfix from our
source tree and used the built-in linking utility combined with some of our
existing install_name_tool post-build tasks.
To be clear I've made no Python code changes to this -- macdeployqtfix --
project.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/aurelien-rainone/macdeployqtfix/issues/1#issuecomment-231164722,
or mute the thread
https://github.com/notifications/unsubscribe/AAdF6vs4WAHj75JjZAYGc1OGKNXUzNoAks5qTUQhgaJpZM4F1tAW
.

Well I don't know, but the problem with the library pythonqt has gone. I now build that library using cmake rather than qmake and since my program uses the same build-system, I suspect things got somehow harmonised.


Update sources

:robot_face: Updating sources to the latest version.
New commits on tezos/tezos Trunk

CI: Revert tezos/tezos!6787
Merge tezos/tezos!8769: CI: Revert "Merge tezos/tezos!6787"
Proto,SCORU: Add unit test for the reveal instruction
Merge tezos/tezos!8742: Proto,SCORU: Add unit test for the reveal instruction
WASM: Functorize the debugger
Merge tezos/tezos!8638: WASM: Functorize the debugger
SCORU/Node: fix permissions for store data file when run in readonly
Test: test store load
Merge tezos/tezos!8687: SCORU/Node: fix permissions for store data file when run in readonly
kernel/sequencer: add an input predicate
kernel/sequencer: add input predicate to macro
Merge tezos/tezos!8668: kernel/sequencer input predicate
Proto: add parameter staking_over_baking_limit
Tests: update regression outputs
Merge tezos/tezos!8744: Proto: add parameter staking_over_baking_limit
Tezt/long_tests: disable [script_cache.ml] tests
Tezt/long_tests: disable [block.*] tests in [block_validation.ml]
Merge tezos/tezos!8714: Tezt/long_tests: disable failing [script_cache.ml] & [block_validation.ml] tests
doc: enable flag ODOC_WARN_ERROR
doc: fix docstring errors
doc: patch the doc of snapshotted protocols
doc: explain odoc errors in the coding guidelines
Merge tezos/tezos!8690: doc: fix remaining Odoc errors and enable ODOC_WARN_ERROR flag
DAL/Node: ability to provide a different PoW at configure
DAL/Node: expose the worker instance in gs_interface
DAL/Node: expose the Monad module's interface
DAL/GS: extend the worker with facilities to monitor/log its events
DAL/Node: implement logging for worker events
DAL/Node: expose GS logging module in Gossipsub
DAL/Node: enable worker events logging in daemon.ml
Manifest: add needed deps to implement components interconnction
DAL/Node: start implementhing GS and P2P interconnection: new connections
DAL/Node: expose Interconnection module in Gossipsub wrapper
DAL/Node: add the ability for activate to add points to the pool
DAL/Node: provide additional peers at P2P activation
DAL/Node: enable GS and transport layer interconnection in daemon
Tezt/lib_tezos: expose function listen_addr
Tezt/lib_tezos: Dal.init_config can now take a different PoW
Tezt/lib_tezos: expose a function to read DAL nodes identity files
Tezt/DAL: test for dal node p2p connection
Merge tezos/tezos!8495: DAL/Node: forward new p2p connections events to GS
Client/Michelson: `typecheck script` can typecheck several scripts
Client/Michelson: backport change on the typecheck script command
Tezt: support multiple scripts in {spawn_,}typecheck_script
Tezt/Michelson: move iteration over typechecked scripts
Tezt/Michelson: all scripts typechecked in the same test
Tezt: Regenerate regression traces
Tezt/Michelson/Typechecking: call `typecheck script` only once
Tezt: reset regression traces
Client/Michelson: add the --display-name flag to typecheck script
Client/Michelson: backport to Mumbai and Nairobi
Tezt/Michelson: add the ?display_names option to typecheck_script
Tezt/Michelson/Typechecking: use ~display_names in test
Tezt: reset regression traces
Client/Michelson/TCscript: compute name even without --display-names
Client/Michelson: backport to Mumbai and Nairobi
Client/Michelson: move display-names logic to print_typecheck_result
Client/Michelson: backport to Mumbai and Nairobi
Client/Michelson: change format of "typecheck script" output
Client/Michelson: backport to Mumbai and Nairobi
Tezt: reset regression traces
Client/Michelson: display the name of ill-typed scripts
Client/Michelson: backport to Mumbai and Nairobi
Client/Michelson: fix numbering of literal scripts
Client/Michelson: backport to Mumbai and Nairobi
Tezt/Michelson: update error pattern for ill-typed scripts
Tezt/Michelson: new numbering of literal scripts in hash script
Merge tezos/tezos!8231: Client/Michelson: Typecheck several scripts
DAC: get rid of useless LWt on certificate tests
Merge tezos/tezos!8783: DAC: get rid of useless Lwt on certificate tests
SCORU/Node: fix incorrect inbox for migration blocks
SCORU/Node: rename incorrect migration_block to first_block
Test: basic protocol migration for rollup node
SCORU/Node: backport !8689 to Nairobi rollup node
Merge tezos/tezos!8689: SCORU/Node: fix incorrect inbox for migration blocks
DAL/Node: init the store with the GS worker
DAL/Node: expose implem details of topic, message, and message_id
DAL/Node: rework/fix worker events logging
DAL/Node: join the corresponding topics when adding a profile
Tezt/Dal: add a test for GS topic join
Merge tezos/tezos!8681: DAL/Node: join corresponding topics when adding a profile
DAL/Node: rework the GS/Transport interconnection interface
DAL/Node: add handlers to forward messages from/to GS to/from P2P
Tezt/DAL: test subscribe & graft
Merge tezos/tezos!8727: DAL/Node: send/recv p2p messages (test subscribe & graft)

Diff URL: https://gitlab.com/tezos/tezos/-/compare/6064e8b7052294305324ca1925c128414f3cd345...fd754eceb3a2d4d91c1908f27541e279bcf3fa06

Superseeded by #110


Configure CI/CD

Recommended: CircleCI
Backup: Azure DevOps
(both have free plans)

Also require Dockerfile configuration

Configured via Azure App Service for Containers and Docker Hub


[Epic] RHDH Operator Monitoring

[ ] Add ability in CRD to create a ServiceMonitor resource (follow-up to https://github.com/janus-idp/operator/issues/180)
[ ] Implement Prometheus metrics in RHDH Operator for Backstage CR reconciliation failure/success
[ ] Implement Grafana dashboards to monitor a) Whether the operator is up and running as well as how long it has been running, b) memory & CPU consumption by the operator
[ ] Implement alerts so that when the operator is down, certain actions get triggered, eg, a notification gets sent to the user's slack channel, a Jira ticket is created, etc.

Do we also consider upstream (vanilla K8s) here or Openshift only?

Do we also consider upstream (vanilla K8s) here or Openshift only?

Not only OpenShift, I think. It should work on both.

As part of the migration from janus-idp to redhat-developer in https://issues.redhat.com/browse/RHIDP-1021, this will be tracked in https://issues.redhat.com/browse/RHIDP-1337


chore(release): release 16.2.2

PR Checklist
Please check if your PR fulfills the following requirements:

[ ] The commit message follows our guidelines: https://github.com/NG-ZORRO/ng-zorro-antd/blob/master/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Application (the showcase website) / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
[ ] Yes
[ ] No

Other information

@simplejason @OriginRing it seems that in the npm repo we have still the version 16.2.1.
Is the version 16.2.2 already deployed ?


Requests not set to default Radarr profile (manual approval)

Hi.
I added a Radarr profile with the initial Petio release. I updated to 0.4-4-alpha and let users give it a try.
Requests are added, but when i go to "edit" the request itself does not adhere to my default radarr profile settings.
if i set and process request manually it works (but requires a lot of clicking if you have many requests)
Expected behavior
Not having to set default server/profile/root folder for every request that needs manual approval
Desktop (please complete the following information):

Win Server 2016
Chrome 89

Default Radarr profile

Request does not adhere to above settings

Can you confirm this bug persists in the latest release, it should have been fixed now, please re-open if it persists


Updated Salesforce

Brand color per https://www.lightningdesignsystem.com/resources/tokens

Thanks dotten
can you add the color in index.html and readme.md?

@Dottenpixel you there?

Hi! sorry I missed your message here. I'm not sure what you mean by adding the color to index.html and readme. Isn't the brandColors.js file the single source for the color data?

@Dottenpixel no worries at all! I merged it after I implemented a script that generates everything from data/brandColors.js so we're all good. :)


New Folder creation looses focus with each letter

Describe the bug
When I create a new folder and start typing its name, the popup keeps loosing focus and I have to click again on it after each letter
To Reproduce
Steps to reproduce the behavior:
Create a new folder and start typing the name. Doesn't matter if the folder is created through the toolbar or the right-click menu
Expected behavior
The focus should be kept on the popup, so that you can type the full name without issues
Desktop (please complete the following information):

OS Version: Windows 10 1909
App version: v<IP_ADDRESS>

We are planning on fixing this issue with the v0.7.7 release https://github.com/duke7553/files-uwp/issues/486.


Newly added files do not have icons next to them until refreshing nerd tree.

If you add new files through NERDTree (press m then a) the newly added files do not have icons next to them.

:+1:  Ah, I have seen this before and I never put a ticket. At least I think it is pre-existing v0.4.0 so I am glad I didn't break that

@jordwalke
Sorry I keep pushing this off but bugs and easier fixes come up. I actually did delve into this but got a bit stuck, I might even need to submit a PR for NERDTree itself for listener on new nodes


Fixes a race condition and deleting only teams that you no longer belong to

Summary
There was a race condition caused by the team_sidebar where we fetched other teams as the screen could've mount before finishing with the requests in the background on a normal or push notification app entry, this could conflict with team record preparation.
On top of that the conflict was mainly cause we use to delete all teams that we had no membership present in the fetch response, this was changed to only delete the teams if you were previously a member and are no longer.
NONE

@larkox @jfrerich can I have this reviewed please ?


[system] Add enableColorScheme option to getInitColorSchemeScript

The enableColorScheme option did not pass to getInitColorSchemeScript. By adding this option, the script attaches the color-scheme before the application is rendered on the screen.
Next step: I will add a script to minimize via terser.

[x] I have followed (at least) the PR section of the contributing guide.

@siriwatknp This change breaks the dark mode on http://mui.com/, it was released in v5.8.6. Compare:

v5.8.5 https://62b20869868499000935015c--material-ui-docs.netlify.app/material-ui/getting-started/overview/

v5.8.6 https://62ba17befe0264000813edc4--material-ui-docs.netlify.app/material-ui/getting-started/overview/

In practice, it's a regression from #29454. I think that the issue is here:

Shouldn't we get a single light/dark mode for @mui/system, and have Material UI/Joy UI directly rely on it?

@siriwatknp Could you prioritize fixing this regression? It seems important