Relationship inclusion in views can result in duplicate resources

Thanks for all the work on this, it’s made things pretty smooth apart from my problem here. I have an application where I want JSON responses to include a lot of related resources but I’m getting semi-duplication.
A run has many participations, I also need to preload the participation’s run so it can be correlated on the client, and the participation’s user. This results in a response that has duplicate participations in the included block with different relationships, and even the root run is in there.
Here’s an example response with irrelevant parts removed:

{
  "data": [
    {
      "attributes": {…},
      "id": "59e1382a-2cf1-4fc5-abd5-e5a22cc213e2",
      "links": {…},
      "type": "runs",
      "relationships": {
        "specification": {…},
        "participations": {
          "data": [
            {
              "id": "6098e3cb-f58e-4e48-9ceb-0ef6b55e38a0",
              "type": "participations"
            }
          ],
          "links": {…}
        },
        "submissions": {…}
      }
    }
  ],
  "links": {…},

The root run

  "included": [
    …,
    {
      "attributes": {
        "ready_at": null
      },
      "id": "6098e3cb-f58e-4e48-9ceb-0ef6b55e38a0",
      "links": {…},
      "type": "participations",
      "relationships": {}
    },

An included participation with no relationships

    {
      "attributes": {…},
      "id": "59e1382a-2cf1-4fc5-abd5-e5a22cc213e2",
      "links": {…},
      "type": "runs",
      "relationships": {
        "specification": {
          "data": {
            "id": "a5b1b47e-a180-4ca0-95e4-75888b630901",
            "type": "specifications"
          },
          "links": {…}
        },
        "participations": {
          "data": [
            {
              "id": "6098e3cb-f58e-4e48-9ceb-0ef6b55e38a0",
              "type": "participations"
            }
          ],
          "links": {…}
        },
        "submissions": {…}
      }
    },

The root run again, included because ParticipationView includes run.

    {
      "attributes": {…},
      "id": "6098e3cb-f58e-4e48-9ceb-0ef6b55e38a0",
      "links": {…},
      "type": "participations",
      "relationships": {
        "run": {
          "data": {
            "id": "59e1382a-2cf1-4fc5-abd5-e5a22cc213e2",
            "type": "runs"
          },
          "links": {…}
        }
      }
    },

An included participation lacking its user relationship.

    …,
    {
      "attributes": {…},
      "id": "6098e3cb-f58e-4e48-9ceb-0ef6b55e38a0",
      "links": {…},
      "type": "participations",
      "relationships": {
        "run": {
          "data": {
            "id": "59e1382a-2cf1-4fc5-abd5-e5a22cc213e2",
            "type": "runs"
          },
          "links": {…}
        },
        "user": {
          "data": {
            "id": "ce8112be-a9db-4ef1-ae1a-4d75a1916975",
            "type": "users"
          },
          "links": {…}
        }
      }
    }
  ]
}

The same relationship, now including its user.

This double inclusion means I need defensive client code to select the included resource that has the expected relationships.
I have baroque preloads to span the object graph, further complicated by the users table being in another Postgres schema:
    Run
    |> filter_runs_query(filters)
    |> Repo.all()
    |> Repo.preload(run_preloads())
    |> Repo.preload(participations: [run: run_preloads()])
    |> Repo.preload([participations: [:user]], prefix: "public")

And my views are mutually referencing:
defmodule RegistrationsWeb.ParticipationView do
  use JSONAPI.View, type: "participations"
  …
  def relationships do
    [run: {RegistrationsWeb.RunView, :include}, user: {RegistrationsWeb.JSONAPI.UserView, :include}]
  end
end

defmodule RegistrationsWeb.RunView do
  use JSONAPI.View, type: "runs"
  …
  def relationships do
    [
      participations: {RegistrationsWeb.ParticipationView, :include},
      specification: {RegistrationsWeb.SpecificationView, :include},
      submissions: {RegistrationsWeb.SubmissionView, :include}
    ]
  end
end

It may be that this library can’t properly deduplicate included resources because it has no way of knowing which is correct to choose. But is there any best practice for getting this chaos under control? 😳

I’ll start by saying that the library does attempt to deduplicate includes so it is possible there’s room for improvement here.
The current deduplication uses Enum.uniq/1 so it isn’t going to see two resources that will be serialized differently as the same even if they have the same type/id which is theoretically the only thing that should be considered in identifying a JSON:API resource.
The fact that you get the primary resource also serialized in the includes because some other include refers to it sounds like desired behavior to me.
I think that leaves the question of includes that are indeed the same (same type/id) but are showing up twice in your responses. As I said above, this does feel like an area with room for improvement, but it leaves us with the question you posed above: how should we choose between two copies of the same resource with different fields/relationships on them? At some level the fact that the “same” resource has different attributes feels a bit counter to JSON:API, but I don’t think we need to debate that here per se. The easiest thing for you to do would be to find a way to control the shape of a given resource based on the request being made and therefore serialized a given resource the same way each time for a single request; this would alleviate the question of how to choose one and it would also fix the issue of duplication since Enum.uniq/1 would catch the duplicates.

👍🏻 thanks for the clarification that deduplication does happen, then it seems you’re right that I need consistent serialisation of the object graph regardless of the starting point. I’ve made some efforts in that direction but have so far failed. I’ll keep trying though, thanks!

I do wonder if it’s worth a duplication function that can optionally be configured. I have not thought on whether such a thing is worth it for the library but there’s a chance it would be because regardless of whether I personally would like to see a resource serialized the same way in all places I think including a resource twice in the includes with the same type/id is not good. It’s probably worse that the library makes it easy to end up in that situation than it would be to provide a way to handle deduplication explicitly.

ya an escape valve when an abstraction is failing is often helpful! I’d definitely make use of that feature in the event I can’t figure out a clean way to normalise my tangled object graph 🤓


Static build

Motivation
We want to be able to use it in unknown environments
Feature
CMake can produce a statically linked pdig binary
Alternatives
Keep the dynamically linked build.
Additional context
Discussed in the Falco userspace working group.

/assign @fntlnz

Done in #19
/close

@leodido: Closing this issue.

In response to this:

Done in #19
/close

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


GT_Encoder f1_score always 0

I tried overfitting on fewer images [24] to see if issue is real, f1 error array and hence np.amax(f1) both are coming out to be 0. Any solutions?

I believe there is a correction to be made:
pre,rec,f1,mae = f1_mae_torch(pred_val*255, gt, valid_dataset, i_test, mybins, hypar)
should be
pre,rec,f1,mae = f1_mae_torch(pred_val255, gt255, valid_dataset, i_test, mybins, hypar)

I have the same issue. F1 is 0 always.

Multiplying gt by 255 solved it for me

I tried overfitting on fewer images [24] to see if issue is real, f1 error array and hence np.amax(f1) both are coming out to be 0. Any solutions?

The code has been updated, please try to use that to see whether the error still happens?


Will there be an update for this adapter in the near future?

Ask your question
Will there be an update for this adapter in the near future like it was done for HOAS?
Thank you for the information in advance.

Anything ?


fix docs typo "developper" -> "developer"

Thanks Jesko, fixed here for convenience: https://github.com/TARGENE/targene-pipeline/tree/simulation


Not an issue.


@johnmccutchan The steps to reproduce are outlined above (https://github.com/flutter/flutter/issues/112254#issuecomment-2009866637) the only requirement is to use one of the listed devices(Samsung SM-A032M, MotoG13, MotoG23).
The issue persists in Flutter 3.19.6 but we have tried in Flutter 3.22.0-0.3.pre and is not crashing anymore in the Samsung SM-A032M device.
@johnmccutchan would you validate this fix please? because we need to solve this as soon as possible (we have 4k affected user in 10 days and 1k crashes everyday).

Sounds like this is fixed in 3.22, we recommend people upgrade.

It's good to hear it has been fixed in 3.22. Another question would be when will 3.22 be released on Stable channel. @johnmccutchan

@YuxuanDu based on history, it will be released by 5/14 for Google I/O.

I hope this bug has finally been fixed. Although few devices are affected, such devices have a large number of users, especially Samsung. With me, according to Play Console, only the Samsung A03 Core, in production, raises the crash rate above the tolerated limit of 8%, making the app subject to punishment

The issue persists in Flutter 3.19.6 but we have tried in Flutter 3.22.0-0.3.pre and is not crashing anymore in the Samsung SM-A032M device.

@fernan88 Hi, what is the Android version of your SM-A032 device ?

The issue persists in Flutter 3.19.6 but we have tried in Flutter 3.22.0-0.3.pre and is not crashing anymore in the Samsung SM-A032M device.

@fernan88 Hi, what is the Android version of your SM-A032 device ?

Hi Bian, this is an Android 13 OS.

3.22 now was released in stable


Also disallow "..._Localised" properties in "Factions" list

This is a breaking change!

Should *_Localised also be disallowed in Materials (of course defining Materials as an array would disallow journal landable planet scans from before 2.3 - i.e. more than 2 years old)


two items

Users often need to re-send a push notification (the first attempt times out).  I've seen this multiple times while observing my users in the preview experience.

There needs to be some roadmap communication regarding when this feature is supposed to leave Preview and go GA.  The O365 roadmap is sorely lacking updates across the board at this point.

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

ID: 91ad4424-8d90-7947-2f95-aec67acfec45
Version Independent ID: 0ebfde0e-5597-fed9-f87c-761fd778fb25
Content: Converged registration for Azure AD SSPR and MFA (public preview)
Content Source: articles/active-directory/authentication/concept-registration-mfa-sspr-converged.md
Service: active-directory
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

@philliplyle Thanks for the feedback !  I have assigned this issue to content author to investigate and update the document as appropriate.

@philliplyle We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


[1.12] Fix TLS handshake

High-level description
Fix TLS handshake for RSA based end-entity certificate signed by EC based CA with TLS insufficient security alert.
Corresponding DC/OS tickets (obligatory)
These DC/OS JIRA ticket(s) must be updated (ideally closed) in the moment this PR lands:

DCOS-44367 [ERL-763] TLS handshake fails for RSA based end-entity certificate signed by EC based CA with TLS insufficient security alert
ERL-763 TLS handshake fails for RSA based end-entity certificate signed by EC based CA with TLS insufficient security alert

Related tickets (optional)
Other tickets related to this change:
Checklist for all PRs

[x] Added a comprehensible changelog entry to CHANGES.md or explain why this is not a user-facing change: ee only
[x] Included a test which will fail if code is reverted but test is not. If there is no test please explain here: none
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

PLEASE FILL IN THE TEMPLATE ABOVE / DO NOT REMOVE ANY SECTIONS ABOVE THIS LINE
Instructions and review process
What is the review process and when will my changes land?
All PRs require 2 approvals using GitHub's pull request reviews.
Reviewers should be:

Developers who understand the code being modified.
Developers responsible for code that interacts with or depends on the code being modified.

It is best to proactively ask for 2 reviews by @mentioning the candidate reviewers in the PR comments area. The responsibility is on the developer submitting the PR to follow-up with reviewers and make sure a PR is reviewed in a timely manner. Once a PR has 2 ship-it's, no red reviews, and all tests are green it will be included in the next train.

@mesosphere-mergebot bump-ee

@mesosphere-mergebot bump-ee

@mesosphere-mergebot label [Ready For Review]

@Fabs please check EE PR, @mhrabovcin enabled ec_* tests there and they pass.


Create Oauth2UserPatTrait.php

Q
A

Is bugfix?
✔/❌

New feature?
✔/❌

Breaks BC?
✔/❌

Tests pass?
✔/❌

Fixed issues
comma-separated list of tickets # fixed by the PR, if any

Thanks 👍


Documentation/Examples of Previous/Next functionality.

Examples of how to implement previous/next functionality in templates would be greatly appreciated.

I know this isn't a substitute for good docs, but the previous/next functionality is very simple.once the collection is built, the plugin just loops through the collection, adding a prev and next property to the file metadata, which is just the name of the previous and next file in the list of files I the collection.

In case others are seeing [Object object] when you try to use the above, try this instead:

      {{#if previous}}
        ← {{{previous.title}}}
      {{/if}}
      {{#if next}}
        {{{next.title}}} →
      {{/if}}

+1


Parts of the installation process are inconsistent

While installing regent I found a few inconsistencies in the installation process.

The prerequisites listed on http://regent-lang.org/install/ seem to differ compared to the ones listed on https://github.com/StanfordLegion/legion/tree/stable/language#prerequisites

The circuit.rg file is not present anymore https://github.com/StanfordLegion/legion/tree/stable/language#running

Thanks for reporting this.
For now, stick to the instructions at http://regent-lang.org/install/ . The repo is out of date in this case.
The Circuit example can be found under examples/circuit_sparse.rg.

I've updated http://regent-lang.org/install/ and https://gitlab.com/StanfordLegion/legion/-/blob/master/language/README.md. Please check the new instructions and let me know if you have any issues.
It'll take a while for our GitHub mirror to sync from Gitlab (and stable won't update until our next release anyway), but your original link should update eventually.

Following the updated instructions, everything worked fine and I can execute the examples! Thanks for clearing that up. I will close this.


add serialization convertor

Motivation:
add serialization convertor
Modification:
add xsd
serialize-type
Result:
Fixes  make user can set serialization in xml

Codecov Report

Merging #48 into master will decrease coverage by 0.37%.
The diff coverage is 26.66%.

@@            Coverage Diff             @@
##           master      #48      +/-   ##
==========================================
- Coverage   59.19%   58.81%   -0.38%
==========================================
  Files          45       45
  Lines        1272     1287      +15
  Branches      210      215       +5
==========================================
+ Hits          753      757       +4
- Misses        396      403       +7
- Partials      123      127       +4

Impacted Files
Coverage Δ

...c/boot/runtime/binding/RpcBindingXmlConstants.java
0% <ø> (ø)
:arrow_up:

...y/sofa/rpc/boot/runtime/param/RpcBindingParam.java
37.3% <16.66%> (-1.04%)
:arrow_down:

...t/runtime/adapter/helper/ConsumerConfigHelper.java
56.52% <33.33%> (-0.79%)
:arrow_down:

...pc/boot/runtime/converter/RpcBindingConverter.java
54.9% <33.33%> (-0.44%)
:arrow_down:

...t/runtime/adapter/helper/ProviderConfigHelper.java
54.09% <33.33%> (-1.08%)
:arrow_down:

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 dc3b35a...57bbe12. Read the comment docs.


Uncaught TypeError: path must be a string or Buffer

When trying to compile my latex document on windows 10, I get the above error message. The issue seems also to be discussed in https://github.com/James-Yu/Atom-LaTeX/pull/47 , although there is no solution presented there?
Please note I am not too familiar with the technical details of your project. I tried a couple of things, like setting a %!TEX root= ...  but it seems to have no effect.
What am I doing wrong?

Could you kindly provide the entire issue log?

I got the same error, on a different situation.
[Enter steps to reproduce:]

Ctrl + Left mouse click on PDF viewer to sync with the corresponding position on a latex file.
Notes:
The exception occured on an Ubuntu 16.04 machine. The PDF was originally built on an other Mac OS machine.
The problem went away after cleaning all build files and rebuilding the PDF.

Atom: 1.19.4 x64
Electron: 1.6.9
OS: Ubuntu 16.04.3
Thrown From: atom-latex package 0.8.1
Stack Trace
Uncaught TypeError: path must be a string or Buffer
At fs.js:871

TypeError: path must be a string or Buffer
    at Object.fs.readdirSync (fs.js:871:18)
    at Object.fs.readdirSync (ELECTRON_ASAR.js:576:28)
    at Manager.module.exports.Manager.loadLocalCfg (/packages/atom-latex/lib/manager.coffee:33:5)
    at Manager.module.exports.Manager.findMainConfig (/packages/atom-latex/lib/manager.coffee:123:6)
    at Manager.module.exports.Manager.findMainSequence (/packages/atom-latex/lib/manager.coffee:86:21)
    at Manager.module.exports.Manager.findMain (/packages/atom-latex/lib/manager.coffee:53:15)
    at Manager.module.exports.Manager.findPDF (/packages/atom-latex/lib/manager.coffee:144:10)
    at Locator.module.exports.Locator.locate (/packages/atom-latex/lib/locator.coffee:49:31)
    at Viewer.module.exports.Viewer.wsHandler (/packages/atom-latex/lib/viewer.coffee:29:24)
    at /packages/atom-latex/lib/server.coffee:23:47)
    at emitTwo (events.js:106:13)
    at WebSocket.emit (events.js:191:7)
    at Receiver.ontext (/packages/atom-latex/node_modules/ws/lib/WebSocket.js:841:10)
    at /packages/atom-latex/node_modules/ws/lib/Receiver.js:536:18
    at /packages/atom-latex/node_modules/ws/lib/Receiver.js:368:7
    at /packages/atom-latex/node_modules/ws/lib/PerMessageDeflate.js:249:5
    at afterWrite (_stream_writable.js:386:3)
    at onwrite (_stream_writable.js:377:7)
    at afterTransform (_stream_transform.js:79:3)
    at TransformState.afterTransform (_stream_transform.js:54:12)
    at Zlib.callback (zlib.js:625:5)

Commands
 27x -3:27.8.0 core:backspace (input.hidden-input)
     -3:12.1.0 atom-latex:preview (input.hidden-input)
 18x -2:03.4.0 core:select-right (input.hidden-input)
  2x -0:49.1.0 intentions:highlight (input.hidden-input)

Non-Core Packages
atom-latex 0.8.1
intentions 1.1.5

@vmetsis how many projects did you have open in Atom at the point of this error, and what kind of project structure do you utilise?

I had just one project open as far as I can remember. The project is broken down into multiple Latex files. A main.tex file and a few other .tex files which are imported using the \input{...} command.

Here I got same error. I just installed the package and run a test file [Enter steps to reproduce:]

...
...

Atom: 1.20.0 x64
Electron: 1.6.9
OS: Mac OS X 10.12.6
Thrown From: atom-latex package 0.8.1
Stack Trace
Uncaught TypeError: path must be a string or Buffer
At fs.js:871

TypeError: path must be a string or Buffer
    at Object.fs.readdirSync (fs.js:871:18)
    at Object.fs.readdirSync (ELECTRON_ASAR.js:576:28)
    at Manager.module.exports.Manager.loadLocalCfg (/packages/atom-latex/lib/manager.coffee:33:5)
    at Builder.module.exports.Builder.setCmds (/packages/atom-latex/lib/builder.coffee:142:20)
    at Builder.module.exports.Builder.build (/packages/atom-latex/lib/builder.coffee:16:6)
    at HTMLElement.click (/packages/atom-latex/lib/view/panel.js:106:85)

Commands
     -3:54.2.0 atom-latex:synctex (a.stack-toggle)

Non-Core Packages
atom-latex 0.8.1
git-control 0.9.0
Hydrogen 1.22.0

I had the same, issue. I figured it was caused by the fact that the LaTeX file wasn't in any of my projects, so to fix it, I did:

Open the .tex file in a separate Atom session, so that it is within a project.
Build LaTeX in Atom.

This does build the document successfully. I don't think this behaviour is intended, so it's probably a bug.

@HanKruiger  I do not follow - How did you set the LaTeX root file  when you ran into this error?

Same error occurred when clicking on the option "Clean Latex auxiliary files" on Atom-Latex.
[Enter steps to reproduce:]

Clicked on "Clean Latex auxiliary files"
...

Atom: 1.19.4 x64
Electron: 1.6.9
OS: Ubuntu 16.04.3
Thrown From: atom-latex package 0.8.1
Stack Trace
Uncaught TypeError: path must be a string or Buffer
At fs.js:871

TypeError: path must be a string or Buffer
    at Object.fs.readdirSync (fs.js:871:18)
    at Object.fs.readdirSync (ELECTRON_ASAR.js:576:28)
    at Manager.module.exports.Manager.loadLocalCfg (/packages/atom-latex/lib/manager.coffee:33:5)
    at Manager.module.exports.Manager.findMainConfig (/packages/atom-latex/lib/manager.coffee:123:6)
    at Manager.module.exports.Manager.findMainSequence (/packages/atom-latex/lib/manager.coffee:86:21)
    at Manager.module.exports.Manager.findMain (/packages/atom-latex/lib/manager.coffee:53:15)
    at Cleaner.module.exports.Cleaner.clean (/packages/atom-latex/lib/cleaner.coffee:12:24)
    at /packages/atom-latex/lib/main.coffee:35:48)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/usr/share/atom/resources/app/src/command-registry.js:265:35)
    at CommandRegistry.handleCommandEvent (/usr/share/atom/resources/app/src/command-registry.js:3:65)
    at CommandRegistry.module.exports.CommandRegistry.dispatch (/usr/share/atom/resources/app/src/command-registry.js:166:25)
    at AtomEnvironment.module.exports.AtomEnvironment.dispatchApplicationMenuCommand (/usr/share/atom/resources/app/src/atom-environment.js:1338:34)
    at EventEmitter.outerCallback (/usr/share/atom/resources/app/src/application-delegate.js:334:31)
    at emitThree (events.js:116:13)
    at EventEmitter.emit (events.js:194:7)

Commands
     -0:51.6.0 tabs:close-other-tabs (div.title)
     -0:36.8.0 atom-latex:clean (input.hidden-input)

Non-Core Packages
atom-latex 0.8.1
intentions 1.1.5

@vmetsis Can you give me information about your project structure?

@ashthespy When I did ran into the error, I tried setting the LaTeX root with the magic comment:
% !TEX root = \path\to\root\file.tex

However, since I just used one .tex file, it shouldn't have been necessary for me to set the root file, right?

Regarding my previous post, the project structure is a single latex file. The file was previously compiled on a different machine and the auxiliary files were copied to the current machine. It seems to me that the error is caused by an old file path inside one of the auxiliary files.

I did some digging around and was able to reproduce this error! 😁
The package normally expects the LaTeX file to be in it's own Atom Project i,e
└── Document_1
    ├── Img
    ├── .latexcfg
    ├── Document_1.tex
    └── Document_1_Chapter1.tex

Then, multiple attempts are used to try and determine the main LaTeX file.
However, to reproduce this error I did:

Open a new Atom window, and then a new editor
Paste some LaTeX file,
Build from Active Editor
Get this error

Will fix this, sorry everyone!


feat(Divider): render content inside

@bamje can i request more reviewers?

Hi! Thx for the PR. I will do a review of PR very soon
@blasdfaa

@v4dyar4 ready

@v4dyar4 added

@blasdfaa Could you rebase branch and merge it?

@blasdfaa Could you rebase branch and merge it?

approve please

@v4dyar4 I don't have the necessary access to merge


FormatException: Encoded surrogate (at offset 12)

Please check this nbt file
minecraft_building.zip
When i using visual code to read, it all fine. The endianness is little.

But the code below return the error: FormatException: Encoded surrogate (at offset 12)
var result = await FilePicker.platform.pickFiles(allowMultiple: false);                     File f = File(result!.files.first.path!);                     final nbtReader = NbtReader.fromFile(f.path);                     nbtReader.setEndianness = Endian.little;                     nbtReader.read();                     NbtCompound rootNode = nbtReader.root!;

Using nbtReader.setEndianness = Endian.host is return a same error

Do you have a call stack for when the exception/error got thrown? Also since it's little endian I'll assume this is a NBT file from Bedrock? In that case you should be using setEndianness = Endian.little since most modern computers use big endianness.

i don't understand your first sentence, i using setEndianness little, it
work on almost Bedrock file (end with .mcstructure) but the file i note in
this thread doesn't work. Visual code plugin still can read it so i think
the problem is this package.
NGUYỄN HOÀNG GIA HUY
Email: @.*** | Mobile:<PHONE_NUMBER>
Vào CN, 29 thg 9, 2024 lúc 03:57 sean @.***> đã viết:

Do you have a call stack for when the exception/error got thrown? Also
since it's little endian I'll assume this is a NBT file from Bedrock? In
that case you should be using setEndianness = Endian.little since most
modern computers use big endianness.
—
Reply to this email directly, view it on GitHub
https://github.com/spnda/dart_minecraft/issues/14#issuecomment-2380893038,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APDWGXVAK7ZE63AT3JLPBKTZY4J5PAVCNFSM6AAAAABO63J5L6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBQHA4TGMBTHA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Add some methods to sea_orm_migration::migrator::Migration

Right now, you can't really do anything with this struct, so e.g. programmatically checking the status of all migrations using MigratorTrait::get_migration_with_status is not possible.

Hi @tp971! Could you describe your problem in more detail?

It's not necessarily a problem, rather an inconvenience. The only thing I need is the number of applied migrations, which can be done using MigratorTrait::get_applied_migrations or MigratorTrait::get_migration_models, but for logging and debugging purposes, it would be nice to have more information. My suggestion is to implement methods for Migration to get the name and the status (and maybe store the applied_at when status is Applied).

Can you attach code examples what and how you do it now and how you want do it with possible new api

A simple use case would be:
let migrations = Migrator::get_migration_with_status(db).await?;
//let migrations = Migrator::get_applied_migrations(db).await?; //if only applied migrations are needed
//let migrations = Migrator::get_pending_migrations(db).await?; //if only pending migrations are needed
for migration in &migrations {
    let name = migration.name(); //new method, returning &str
    let status = migration.status(); //new method, returning MigrationStatus
    debug!("migration {}: {}", name, status);
    //do something with name and status here
}

Yes, its strange that methods return Vec, but Migration have pub visibility with private fields and does not actually provide any information. I'll try to fix it

@tp971 please see #1519


Fix a racy test.

Fixes #4533

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: douglas-reid
Assign the PR to them by writing /assign @douglas-reid in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

mixer/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Aha, yes, there was indeed a startup race. This should be all better now,
and race -count 1000 worked well.
On Thu, Mar 29, 2018 at 3:01 PM, codecov[bot]<EMAIL_ADDRESS>wrote:

Codecov https://codecov.io/gh/istio/istio/pull/4637?src=pr&el=h1 Report
Merging #4637 https://codecov.io/gh/istio/istio/pull/4637?src=pr&el=desc
into master
https://codecov.io/gh/istio/istio/commit/bfd7a4ad2589c4f87e10048806cc46b1b0f02365?src=pr&el=desc
will increase coverage by 1%.
The diff coverage is 100%.
[image: Impacted file tree graph]
https://codecov.io/gh/istio/istio/pull/4637?src=pr&el=tree
@@          Coverage Diff           @@##           master   #4637   +/-   ##
======================================+ Coverage      75%     76%   +1%
Files         297     297
Lines       24743   24728   -15
======================================+ Hits        18501   18557   +56     + Misses       5469    5404   -65     + Partials      773     767    -6
Impacted Files
https://codecov.io/gh/istio/istio/pull/4637?src=pr&el=tree Coverage Δ
mixer/adapter/list/list.go
https://codecov.io/gh/istio/istio/pull/4637/diff?src=pr&el=tree#diff-bWl4ZXIvYWRhcHRlci9saXN0L2xpc3QuZ28= 100%
<100%> (+1%) ⬆
mixer/adapter/opa/opa.go
https://codecov.io/gh/istio/istio/pull/4637/diff?src=pr&el=tree#diff-bWl4ZXIvYWRhcHRlci9vcGEvb3BhLmdv 79%
<0%> (-3%) ⬇
mixer/adapter/fluentd/fluentd.go
https://codecov.io/gh/istio/istio/pull/4637/diff?src=pr&el=tree#diff-bWl4ZXIvYWRhcHRlci9mbHVlbnRkL2ZsdWVudGQuZ28= 76%
<0%> (-1%) ⬇
mixer/adapter/servicecontrol/client.go
https://codecov.io/gh/istio/istio/pull/4637/diff?src=pr&el=tree#diff-bWl4ZXIvYWRhcHRlci9zZXJ2aWNlY29udHJvbC9jbGllbnQuZ28= 0%
<0%> (ø) ⬆
pilot/pkg/model/controller.go
https://codecov.io/gh/istio/istio/pull/4637/diff?src=pr&el=tree#diff-cGlsb3QvcGtnL21vZGVsL2NvbnRyb2xsZXIuZ28= 100%
<0%> (ø) ⬆
mixer/adapter/memquota/dedup.go
https://codecov.io/gh/istio/istio/pull/4637/diff?src=pr&el=tree#diff-bWl4ZXIvYWRhcHRlci9tZW1xdW90YS9kZWR1cC5nbw== 100%
<0%> (ø) ⬆
mixer/adapter/solarwinds/solarwinds.go
https://codecov.io/gh/istio/istio/pull/4637/diff?src=pr&el=tree#diff-bWl4ZXIvYWRhcHRlci9zb2xhcndpbmRzL3NvbGFyd2luZHMuZ28= 0%
<0%> (ø) ⬆
mixer/adapter/stdio/stdio.go
https://codecov.io/gh/istio/istio/pull/4637/diff?src=pr&el=tree#diff-bWl4ZXIvYWRhcHRlci9zdGRpby9zdGRpby5nbw== 100%
<0%> (ø) ⬆
mixer/adapter/denier/denier.go
https://codecov.io/gh/istio/istio/pull/4637/diff?src=pr&el=tree#diff-bWl4ZXIvYWRhcHRlci9kZW5pZXIvZGVuaWVyLmdv 100%
<0%> (ø) ⬆
mixer/adapter/dogstatsd/dogstatsd.go
https://codecov.io/gh/istio/istio/pull/4637/diff?src=pr&el=tree#diff-bWl4ZXIvYWRhcHRlci9kb2dzdGF0c2QvZG9nc3RhdHNkLmdv 100%
<0%> (ø) ⬆
... and 8 more
https://codecov.io/gh/istio/istio/pull/4637/diff?src=pr&el=tree-more
Continue to review full report at Codecov
https://codecov.io/gh/istio/istio/pull/4637?src=pr&el=continue.
Legend - Click here to learn more
https://docs.codecov.io/docs/codecov-delta
Δ = absolute  (impact), ø = not affected, ? = missing data
Powered by Codecov
https://codecov.io/gh/istio/istio/pull/4637?src=pr&el=footer. Last
update bfd7a4a...804536b
https://codecov.io/gh/istio/istio/pull/4637?src=pr&el=lastupdated. Read
the comment docs https://docs.codecov.io/docs/pull-request-comments.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/4637#issuecomment-377385858, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AVucHT7C4WXkx235TfSLUw45pf3SksFmks5tjVnEgaJpZM4TA6qB
.

@geeknoid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests.sh
c4723688c0b1f621c78be19a125bbe65421f20a2
link
/test e2e-bookInfo

prow/istio-pilot-e2e.sh
c4723688c0b1f621c78be19a125bbe65421f20a2
link
/test istio-pilot-e2e

prow/istio-pilot-e2e-v1alpha3.sh
d205f2ee658369ead2c1f53ce6c3966b80f01da6
link
/test istio-pilot-e2e-v1alpha3

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

@geeknoid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-v1alpha3.sh
d205f2ee658369ead2c1f53ce6c3966b80f01da6
link
/test istio-pilot-e2e-v1alpha3

prow/istio-pilot-e2e.sh
d205f2ee658369ead2c1f53ce6c3966b80f01da6
link
/test istio-pilot-e2e

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

@geeknoid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
d205f2ee658369ead2c1f53ce6c3966b80f01da6
link
/test istio-pilot-e2e

prow/istio-pilot-e2e-v1alpha3.sh
9d604535f1896fb6f1259559e8d33c5e42672180
link
/test istio-pilot-e2e-v1alpha3

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

@geeknoid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-v1alpha3.sh
9d604535f1896fb6f1259559e8d33c5e42672180
link
/test istio-pilot-e2e-v1alpha3

prow/istio-pilot-e2e.sh
9d604535f1896fb6f1259559e8d33c5e42672180
link
/test istio-pilot-e2e

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

@geeknoid: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-v1alpha3.sh
62a81447f0730b91139bcf63437ef245ce76d54a
link
/test istio-pilot-e2e-v1alpha3

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


k8s Deployment of Funman Service

Ensure that the Funman service is properly deployed in the Kubernetes cluster.

duplicate


Remove process/exec for git binaries

Test with
bb bbin install io.github.borkdude/carve --as carve-dev && cat $(which carve-dev) && carve-dev ; time carve-dev

0.069
Vs
bbin install io.github.borkdude/carve --as carve-wrapped && cat $(which carve-wrapped) && carve-wrapped ; time carve-wrapped

0.100
Please answer the following questions and leave the below in as part of your PR.

[X] This PR corresponds to an issue with a clear problem statement.

#50

I need to fix the tests, but this is a first proof of concept that seems to work.

[ ] Look into failing tests

@rads I have two tests failing locally without my changes (with my changes a few more though). I don't see this on the main branch here. I'll investigate a bit later.
FAIL in (install-tool-from-local-root-test) (/Users/jeroen/Projects/Github/babashka/bbin/test/babashka/bbin/scripts_test.clj:239)
install ./ --tool
expected: (str/includes? (run-bin-script "footool" "k" ":a" "1") "(:a)")
  actual: (not (str/includes? "" "(:a)"))

FAIL in (install-tool-from-local-root-test) (/Users/jeroen/Projects/Github/babashka/bbin/test/babashka/bbin/scripts_test.clj:239)
install ./ --tool
expected: (str/includes? (run-bin-script "footool" "v" ":a" "1") "(1)")
  actual: (not (str/includes? "" "(1)"))

Maybe we should prevent running the private repo tests for GITHUB_ACTOR != rads?

@jeroenvandijk @borkdude: My intent was to set things up so we can still run the private repo tests without being tied to a specific environment. The private repos can be checked out using the git-wrapper instead of git, which overrides the Git SSH command to include the private key for the test repos. (If there are any alarms going off about storing a private key in a public repo, rest assured that this private key is only used for the test repos and only grants read access.)
That said, I think there may be an issue with how I swapped out the Git command using the clojure.gitlibs.command property. I'm only setting it right now in the test runner, not the subprocesses, so I'm confused why it's actually working in GitHub Actions on main (where there is no private key outside of the bundled one in the repo). I'm not sure if deps.clj supports the clojure.gitlibs.command property or GITLIBS_COMMAND env var since it's not actually using tools.gitlibs directly as far as I know.

@rads GITLIBS_COMMAND should work (if that is supported by the clojure CLI)

You can run this to check if the git-wrapper is working as intended locally:
./test-resources/git-wrapper clone git@bitbucket.org:radsmith/bbin-test-lib-private.git

@borkdude: Good to know, I'll can try using the env var instead of the system property (ensuring that subprocesses also have it set) and see if that fixes it.

@rads ./test-resources/git-wrapper clone git@bitbucket.org:radsmith/bbin-test-lib-private.git works for me.
I've tried to export the GITLIBS_COMMAND and run it with bb test, but no success here, maybe I'm doing it wrong.

If the git-wrapper is working for you, that's good news. Now we just have to ensure that the git-wrapper is being used when calling run-bin-script in the tests. If that's the case and the tests are still failing then the test failures are likely due to separate issue.

Btw, locally the tests are failing for me like this, but it seems the private git repo works (without changes in my env):
Testing babashka.bbin.cli-test

Testing babashka.bbin.scripts-test

FAIL in (install-tool-from-local-root-test) (/Users/borkdude/dev/bbin/test/babashka/bbin/scripts_test.clj:239)
install ./ --tool
expected: (str/includes? (run-bin-script "footool" "k" ":a" "1") "(:a)")
  actual: (not (str/includes? "" "(:a)"))

FAIL in (install-tool-from-local-root-test) (/Users/borkdude/dev/bbin/test/babashka/bbin/scripts_test.clj:239)
install ./ --tool
expected: (str/includes? (run-bin-script "footool" "v" ":a" "1") "(1)")
  actual: (not (str/includes? "" "(1)"))

If we solve the Git wrapper thing, tests should pass now. The last two that are failing are failing like mentioned by @borkdude.
Having said that, the implementation I just added feels quite bad and it needs a separate test for the -m option I believe. When I remove this branch in the code. The same two tests fail, but due to the git wrapper I assume.

@jeroenvandijk: Those failing tests are installing from the file system rather than Git so I’m thinking it’s something else.

Regarding the code quality: I plan to refactor the installation functions as part of the next chunk of work, so I’m fine with the code being messy right now as long as the tests pass.
In the future, I will likely add a protocol for installing and set up each procurer/artifact pair as its own implementation, which will require rewriting most of the existing installation code. The tests should stay the same though.

@jeroenvandijk: Those failing tests are installing from the file system rather than Git so I’m thinking it’s something else.

Ah true, I wasn't paying enough attention. So the Git tests are working then, sorry. Getting late here.

@jeroenvandijk: Those failing tests are installing from the file system rather than Git so I’m thinking it’s something else.

@rads I've reverted the commits to see if the tests would be green again (locally they are not), but CI is now showing the same errors as locally, without any diff with main.

@jeroenvandijk: Should we keep this PR open still?

@rads No it can be closed. There is some work left and I need to dive into it again. I'll create a new PR when I get to it.


running the code with python 3.9

in python 3.9 the _write_sentence ( ord()) and send_command function (startswith(), endswith()) produce errors, hereby a proposal instead:

    def _write_sentence(self, bytestring):
        for char_index in bytestring:
            # self._i2c.write_byte(self._i2c_addr, ord(char_index)) # original
            self._i2c.write_byte(self._i2c_addr, char_index)

    def send_command(self, command, add_checksum=True):
        # TODO replace with pynmea2 functionality
        #if command.startswith("$"): # original
        if command[0] == "$":
            command = command[1:]
        if command[-1] == "*":
        #if command.endswith("*"): # original
            command = command[:-1]

        buf = bytearray()
        buf += b'$'
        buf += command
        if add_checksum:
            checksum = 0
            # bytes() is a real thing in Python 3
            # so `for char in commaud` iterates through char ordinals
            for char in command:
                checksum ^= char
            buf += b'*'  # Delimits checksum value
            buf += "{checksum:02X}".format(checksum=checksum).encode("ascii")
        buf += b'\r\n'
        print(buf)
        self._write_sentence(buf)

Thank you.
Added tests and fixes for this in https://github.com/pimoroni/pa1010d-python/pull/13
Need to verify this doesn't horribly break with real hardware and push a release.

Thank you.
Added tests and fixes for this in https://github.com/pimoroni/pa1010d-python/pull/13
Need to verify this doesn't horribly break with real hardware and push a release.


Update CVT Logo

Hi there,
We have changed our logo 4 months ago, besides we have not updated it on iMToken. Please review our pull request and merge our branch to the master.
Best regards,
CyberVein Team

imToken has completed updating your project’s token, please proceed to search and add in imToken app. At the same time, please recommend imToken to your community!


SchemaParserOptions.Builder Beans

Added ability to specify SchemaParserOptions.Builder options that can't be coerced using application properties so that one does not need to override the build entirely to add to the schema parser options.
Recently, a change was made such that the SchemaParserOptions usage was removed and a builder bean was added to GraphQLJavaToolsAutoConfiguration. A @ConfigurationProperties was added to the bean so that the options can be set easily via the application properties. However, for those properties that can't be coerced from a simple type in the application properties, there is no other way to specify said options unless one overrides the builder bean entirely. This PR adds detection of beans that can be used in the SchemaParserOptions.Builder class such that one no longer needs to completely override the builder bean in order to specify these options, thus allowing all defaults to remain intact even after library updates (at least, without manually updating the code of the library client).

Thanks!


Return URL setting after logging in instead of going to homepage

Is your feature request related to a problem? Please describe.
When I go to site.com/admin/ to login using Netlify Identity, it always returns me to the home page after login, but I went to /admin/ because I wanted to be in Netlify CMS.
Describe the solution you'd like
I would love if there was a setting to say what URI to go to after logging in:
backend:
  name: git-gateway
  branch: master
  after_login_uri: "/admin/"

Closing as stale and/or outdated.


SyntaxError in Demo

import thulac
thu1 = thulac.thulac(seg_only=True, model_path='C:\Users\liu zongying\Documents\Python\Zongying\THULAC-Python-master\thulac')  #设置模式为行分词模式
a = thu1.cut("我爱北京天安门")
print(a)
I used python3.7 to run demo, and defined the path of model, but error is shown as follow:
SyntaxError: (unicode error) 'unicodeescape' codec can't decode bytes in position 2-3: truncated \UXXXXXXXX escape

Hi, you run the THULAC in windows system, I think.
This bug is caused by a path input error. You need write path like “C:\Users\liu zongying\Documents\Python\Zongying\THULAC-Python-master\thulac”
Thank you!
发送自 Windows 10 版邮件应用
发件人: liuzongying
发送时间: 2017年12月19日 16:37
收件人: thunlp/THULAC-Python
抄送: Subscribed
主题: [thunlp/THULAC-Python] SyntaxError in Demo (#57)
import thulac
thu1 = thulac.thulac(seg_only=True, model_path='C:\Users\liu zongying\Documents\Python\Zongying\THULAC-Python-master\thulac') #设置模式为行分词模式
a = thu1.cut("我爱北京天安门")
print(a)
I used python3.7 to run demo, and defined the path of model, but error is shown as follow:
SyntaxError: (unicode error) 'unicodeescape' codec can't decode bytes in position 2-3: truncated \UXXXXXXXX escape
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Thank you, problem is solved


didnt respond failed to respond

ADD ISSUE DESCRIPTION HERE
Version: 1.95.2
Commit: e8653663e8840adaf45af01eab5c627a5af81807
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Embedder: codespaces
Extension version: 0.22.2

Can you please describe what type of request you're making so we can reproduce the issue? Example files / queries will help a lot. You can also try clearing your chat history.


PTX-1755 check whether AttachedOn is a node-id or an ip

tests succeeds https://jenkins.portworx.co/job/Torpedo/job/tp-dev-test/55/console


using WebContentsObserver::NavigationEntryCommitted to set virtualurl

Fixes #1116 . The problem was not GetURL ,apparently subframe transition urls were recorded in NavigationEntry as about:blank for file:// . Tried changing params opton in LoadUrl with frame_ids, transition types etc but none helped. So for the moment this the best fix that works. If there is a better way let me know :)

This fix works perfectly, thanks!

I'm sorry to bother you again, but is there some way I can track when this is released in Atom?  I want to remove an ugly kludge I have in my package to work around this.
I guess it wouldn't be too hard to check on every atom release what version of atom-shell it uses and then compare that atom-shell release date to today's date.  Right?

I guess it wouldn't be too hard to check on every atom release what version of atom-shell it uses and then compare that atom-shell release date to today's date. Right?

@mark-hahn Unless I misunderstand you, wouldn't it be enough to check if the atom-shell version is > 0.21.3 (latest release without this patch).

@mark-hahn You can see what branches and tags any given commit is contained in on the commit's page in GitHub. For example, if you look at Fix styling of #1209, you will see that it is currently only present on master. If however, you look at Bump v0.21.3, you will see that it is currently present on master and on the v0.21.3 tag.

wouldn't it be enough to check if the atom-shell version is > 0.21.3
(latest release without this patch).

Yes, that would be more logical than using the date.  Thanks.

You can see what branches and tags any given commit is contained in on the commit's page in GitHub.

Thanks.  I didn't realize that.

If however, you look at Bump v0.21.3, you will see that it is currently present on master and on the v0.21.3 tag.

I'm confused.  What do you mean by it?  There is no mention of this merge on that page, is there?

That's correct. By it, I was referring to the "Bump v0.21.3" commit.


Upgrade forc to 0.52.1

Sway changelogs:

https://github.com/FuelLabs/sway/releases/tag/v0.52.0
https://github.com/FuelLabs/sway/releases/tag/v0.52.1

Superseded by:

https://github.com/FuelLabs/fuels-ts/issues/2042


Add description field to Python cursor

Hi,
in the current Python implementation of PEP 249, the description field of the cursor is missing. This is an attempt to implement the field. I've adapted (blindly) the code from sqlite3.
With this PR, one can use pandas sql functionnalities:
import duckdb
import pandas as pd
purchases = pd.DataFrame({ 'apples': [3, 2, 0, 1],  'oranges': [0, 3, 7, 2]})
con = duckdb.connect(':memory:')
purchases.to_sql('purchases', con)
pd.read_sql_query('SELECT * FROM purchases', con)

Thank you for this PR! It looks good, could you maybe add a test for them as well? I see that the PEP lists these fields for descriptions:

name
type_code
display_size
internal_size
precision
scale
null_ok

It states that the first two are mandatory, but I see sqlite also only setting the first one, so thats fine for us as well. So all normal in Pythonland there.

Yes. I'm discovering this "country" (being more a Rlander) and I'm having a
lot of surprise. This missing mandatory field is the reason why I was
saying this was a "blind" adaptation!
I will build a few tests for this functions.
On Mon, Mar 23, 2020 at 9:28 AM Hannes Mühleisen<EMAIL_ADDRESS>wrote:

Thank you for this PR! It looks good, could you maybe add a test for them
as well? I see that the PEP lists these fields for descriptions:

name
type_code
display_size
internal_size
precision
scale
null_ok

It states that the first two are mandatory, but I see sqlite also only
setting the first one, so thats fine for us as well. So all normal in
Pythonland there.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cwida/duckdb/pull/467#issuecomment-602452604, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AB4BD2NEKHHIQWZXWTUYYLTRI4MUHANCNFSM4LRLQ45A
.

I've added a test.

Nice, thanks. Will merge when the tests have completed.


mock as runtime dependency

Hi,
When using
az network public-ip create --resource-group xxx --name yyy
the code attempts to load the Python mock module, this appears to be counter intuitive. At runtime, i.e. when using the tools one would expect that things actually happen rather than actions/responses being mocked. Having a dependency on mock outside of testing appears strange.
File "/usr/lib/python3.4/site-packages/azure/cli/command_modules/network/custom.py", line 8, in
import mock
and in that code:
@mock.patch('msrestazure.azure_operation.AzureOperationPoller._poll', _poll)
def _generate_vpn_profile(....
@mock.patch('msrestazure.azure_operation.AzureOperationPoller._poll', _poll)
def _generatevpnclientpackage(....
@glaubitz please follow this as well
Environment summary
openSUSE Leap 42.3 azure-cli packages

I'm already subscribed.

Yes, it is strange. Everything from lines 2096-2221 (as of the moment I'm looking at it) is a workaround for a service level issue. Once the issue is fixed, the workaround will be removed (as well as the mock dependency)

https://github.com/Azure/azure-cli/issues/4392

I'm currently packaging 2.2.4 and mock is now part of the dependency list. So it seems this issue was silently fixed:
DEPENDENCIES = [
    'azure-mgmt-network==2.0.0rc3',
    'azure-mgmt-trafficmanager==0.50.0',
    'azure-mgmt-dns==2.0.0rc2',
    'azure-cli-core',
    'mock'
]


Add .mesgignore documentation

we can add a .mesgignore file to ignore specific folders/files that we don't want as in the .dockerignore. We should document this

Can't someone use .dockerignore for that?

.mesgignore and .dockerignore are working very similar but are not the same.
The problem is .dockerignore is implemented in the CLI of Docker, not by the Docker Engine.
So as Core is using directly the Docker Engine, we had to recreate the same functionality.
We name it .mesgignore to show that it's not a .dockerignore file because it's a different implementation and we may not be compatible with feature of a .dockerignore.

But actually, we are using the tar package from Docker that take care of parsing the filenames to ignores.
Except the read of .mesgignore, we are using Docker's package:
https://github.com/mesg-foundation/core/blob/0ff23cf04a764c4aa715730b3c6331b9512eeea1/container/build.go#L23-L29

Agree to rename it .dockerignore. I wanted to have a .mesgignore for later when we will have the possibility to share the sources and stuff like that but we will add this later if it's needed and like that for now it stays simple

closed with https://github.com/mesg-foundation/core/pull/392


Add support for setting content offset of specified section

Will focus on providing a drop in replacement UICollectionView and not exposing any implementation details.


Add support for recursive dep graph

This PR is to address Issue #89 and to add support to check recursively if the project and test dependencies are packaged for Debian or not.

It will add a -r sub-flag to current estimate flag, which will be separate from plain estimate command.
It will add a -format sub-flag, to supports three output formats ("Graph", "Map", "List")

Usage
$ dh-make-golang estimate -r github.com/zyedidia/micro/cmd/micro

$ dh-make-golang estimate -format map -r github.com/zyedidia/micro/cmd/micro

I have also created a standalone tool for it, which you can check out here.

@rajudev can you review, or assign it to the maintainer for the review. For some reason Github don't show me that option anymore.

Hi @anthonyfok,
Could you take a look at this?


Feature request: highlight waveform span when using protocol analyzer

Apologies if this isn't the right place to put feature requests.
I'm using the protocol analyzer, and find it incredibly useful to click on different packets in the protocol analyzer to jump to the timestamp in the waveform. However, when the waveform is zoomed out, it can be tough to tell what the highlighted (grey) packet refers to on the waveform. It would be great to have a same-colored bar on the time axis to indicate where in the waveform the packet refers:

If you have an X axis cursor enabled, it should jump to the start of the packet when you select one.

This works well! Thanks.


Respin of AL2023 21

PKG update only as the version is still same

Does this file needs to be updated?

Yes, we need to update pkg versions


HBASE-24719: Renaming invalid rsgroup throws NPE instead of proper er…

…ror message

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 42s
Docker mode activated.

-0 :warning:
yetus
0m  6s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m 46s
branch-2 passed

+1 :green_heart:
compile
0m 23s
branch-2 passed

+1 :green_heart:
shadedjars
4m 58s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 23s
branch-2 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 22s
the patch passed

+1 :green_heart:
compile
0m 23s
the patch passed

+1 :green_heart:
javac
0m 23s
the patch passed

+1 :green_heart:
shadedjars
5m  3s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 22s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
3m  7s
hbase-rsgroup in the patch passed.

23m 49s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2074/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2074

JIRA Issue
HBASE-24719

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux d2baaaf50ea8 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / ad826a43a2

Default Java
1.8.0_232

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2074/1/testReport/

Max. process+thread count
3580 (vs. ulimit of 12500)

modules
C: hbase-rsgroup U: hbase-rsgroup

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2074/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 42s
Docker mode activated.

-0 :warning:
yetus
0m  6s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
4m 34s
branch-2 passed

+1 :green_heart:
compile
0m 29s
branch-2 passed

+1 :green_heart:
shadedjars
6m  5s
branch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 25s
hbase-rsgroup in branch-2 failed.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m  3s
the patch passed

+1 :green_heart:
compile
0m 28s
the patch passed

+1 :green_heart:
javac
0m 28s
the patch passed

+1 :green_heart:
shadedjars
6m 39s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 23s
hbase-rsgroup in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
3m  1s
hbase-rsgroup in the patch passed.

28m  5s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2074/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2074

JIRA Issue
HBASE-24719

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 341361684e60 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / ad826a43a2

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2074/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-rsgroup.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2074/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-rsgroup.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2074/1/testReport/

Max. process+thread count
3862 (vs. ulimit of 12500)

modules
C: hbase-rsgroup U: hbase-rsgroup

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2074/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 18s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
4m  3s
branch-2 passed

+1 :green_heart:
checkstyle
0m 13s
branch-2 passed

+1 :green_heart:
spotbugs
0m 42s
branch-2 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 35s
the patch passed

+1 :green_heart:
checkstyle
0m 12s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
12m 45s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1.

+1 :green_heart:
spotbugs
0m 50s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 12s
The patch does not generate ASF License warnings.

31m 42s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2074/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2074

JIRA Issue
HBASE-24719

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle

uname
Linux 842528546d1e 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / ad826a43a2

Max. process+thread count
84 (vs. ulimit of 12500)

modules
C: hbase-rsgroup U: hbase-rsgroup

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2074/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f) spotbugs=3.1.12

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

@pankaj72981 can you please review it

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  5s
Docker mode activated.

-0 :warning:
yetus
0m  6s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m 58s
branch-2 passed

+1 :green_heart:
compile
0m 23s
branch-2 passed

+1 :green_heart:
shadedjars
5m 29s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 21s
branch-2 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 32s
the patch passed

+1 :green_heart:
compile
0m 23s
the patch passed

+1 :green_heart:
javac
0m 23s
the patch passed

+1 :green_heart:
shadedjars
5m 27s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 20s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
4m 41s
hbase-rsgroup in the patch passed.

26m 39s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2074/3/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2074

JIRA Issue
HBASE-24719

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 058ae7021c8e 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / cee7431d0a

Default Java
1.8.0_232

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2074/3/testReport/

Max. process+thread count
2443 (vs. ulimit of 12500)

modules
C: hbase-rsgroup U: hbase-rsgroup

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2074/3/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
2m 15s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
5m 35s
branch-2 passed

+1 :green_heart:
checkstyle
0m 16s
branch-2 passed

+1 :green_heart:
spotbugs
0m 55s
branch-2 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 35s
the patch passed

+1 :green_heart:
checkstyle
0m 16s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
16m 21s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1.

+1 :green_heart:
spotbugs
0m 58s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 15s
The patch does not generate ASF License warnings.

40m 48s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2074/3/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2074

JIRA Issue
HBASE-24719

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle

uname
Linux 63f59b2b453e 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / cee7431d0a

Max. process+thread count
84 (vs. ulimit of 12500)

modules
C: hbase-rsgroup U: hbase-rsgroup

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2074/3/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f) spotbugs=3.1.12

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  8s
Docker mode activated.

-0 :warning:
yetus
0m  6s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m 56s
branch-2 passed

+1 :green_heart:
compile
0m 23s
branch-2 passed

+1 :green_heart:
shadedjars
6m 25s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 22s
branch-2 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 34s
the patch passed

+1 :green_heart:
compile
0m 23s
the patch passed

+1 :green_heart:
javac
0m 23s
the patch passed

+1 :green_heart:
shadedjars
6m 26s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 20s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
4m 11s
hbase-rsgroup in the patch passed.

28m  5s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2074/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2074

JIRA Issue
HBASE-24719

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux fc7809abfa39 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / ad177059cf

Default Java
1.8.0_232

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2074/1/testReport/

Max. process+thread count
2300 (vs. ulimit of 12500)

modules
C: hbase-rsgroup U: hbase-rsgroup

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2074/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 26s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m 59s
branch-2 passed

+1 :green_heart:
checkstyle
0m 13s
branch-2 passed

+1 :green_heart:
spotbugs
0m 43s
branch-2 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 31s
the patch passed

+1 :green_heart:
checkstyle
0m 11s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
12m 26s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1.

+1 :green_heart:
spotbugs
0m 50s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 12s
The patch does not generate ASF License warnings.

29m 53s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2074/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2074

JIRA Issue
HBASE-24719

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle

uname
Linux ab2bab78e8e9 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / ad177059cf

Max. process+thread count
84 (vs. ulimit of 12500)

modules
C: hbase-rsgroup U: hbase-rsgroup

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2074/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f) spotbugs=3.1.12

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 35s
Docker mode activated.

-0 :warning:
yetus
0m  5s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
4m 57s
branch-2 passed

+1 :green_heart:
compile
0m 31s
branch-2 passed

+1 :green_heart:
shadedjars
7m 24s
branch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 28s
hbase-rsgroup in branch-2 failed.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 18s
the patch passed

+1 :green_heart:
compile
0m 31s
the patch passed

+1 :green_heart:
javac
0m 31s
the patch passed

+1 :green_heart:
shadedjars
7m  9s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 25s
hbase-rsgroup in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
3m 11s
hbase-rsgroup in the patch passed.

30m 36s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2074/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2074

JIRA Issue
HBASE-24719

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 0fd78abfa35f 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / ad177059cf

Default Java
2020-01-14

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2074/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-rsgroup.txt

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2074/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-rsgroup.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2074/1/testReport/

Max. process+thread count
3167 (vs. ulimit of 12500)

modules
C: hbase-rsgroup U: hbase-rsgroup

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2074/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

This is pending for commit from long time. Can someone please commit it.


terms for media content

Suggestion
I could not find any information from the terms list or in the media schema so I will ask here instead. Are you considering adding terms to specify what the content of an image is? For example, some collections digitize a specimen by including images of the specimen and the labels separately. It could be useful for a user to be able to filter on labels or images specifically.

Hi Cecilie, thanks for your feedback!
I am looking into the ods:DigitalMedia and see if we can align it better with the Audiovisual Core and the DWCA extension Audubon Media Description.
However, when I go through the terms, I don't see any term covering your question.
Terms such as ac:subtype or especially ac:subjectPart feel appropriate, but the Controlled Vocabulary attached to these two terms do not contain a value for indicating if this is an image of a label or a specimen.
I rather than solving this at DiSSCo level, we would like to solve this at the TDWG level.
Would you be open to discuss this question in the Audiovisual Core Maintenance Group?
I might also just have missed the appropriate term, but hopefully they can help with that as well.

Excellent, yes, that looks to exactly match our discussion. I DiSSCo will add this AC term in a later iteration after the AC Maintenance Group has accepted it. Closing this ticket, but feel free to reopen when there are additional questions/comments.


WLS is not working properly

Issue Type: Bug
I am not able to open WLS most of the time, even it is opening, it takes a lot of time. Please fix it ASAP.
VS Code version: Code 1.47.2 (17299e413d5590b14ab0340ea477cdd86ff13daf, 2020-07-15T18:22:06.216Z)
OS version: Windows_NT x64 10.0.18362
Fetching remote diagnostics for 'WSL: Ubuntu-20.04' failed: VS Code Server for WSL failed to start. No messages received for 90s
Check WSL terminal for more details.

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz (4 x 2808)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.86GB (5.30GB free)

Process Argv

Screen Reader
no

VM
0%

Fetching remote diagnostics for 'WSL: Ubuntu-20.04' failed: VS Code Server for WSL failed to start. No messages received for 90s
Check WSL terminal for more details.
Extensions: none

I assume you mean WSL.


Column labels in results and dowload can be confusing

When you filter on "gene products" the column heading with the "gene name" is called "Acc"
I searched on "biological_process"
selected the gene products link,
filtered on H. sapiens to get all gene products annotated to BP node
Filtered on type "protein"
The confusing thing is that there is not a "gene/name product" column heading in this view...the column is called "Acc" but sometimes it   is containing the "gene product" label. Sometimes a UniProt type Identifier
e.g.
KDM4A_HUMAN
filter on "SAA1" and you will see what I mean.
You see
SAA1
and
SAA1_HUMAN
This means that the "get products" link filtering does not give you a unique list of gene products because SAA1 is represented twice in this list.
Mainly now (as I think Chris is onto the redundency issues)  I can't figure are why the column is called "Acc" here and not "gene/product" (as it is called in the link to "annotations"
It seems that the "gene/product" column is the name that biologist will usually expect to see.
I was also pretty confused by the labels for the download options. I think they need explaining more clearly (maybe how they match the GAF, or exactly what they will contain?)
Acc(id)
Acc(bioentitiy)
Label(bioentity_label)
name(bioentity_name)
Is there any document describing these?
I tried all of these and none of them seems to consistently supply me with the label which I was looking for DB Object Symbol (column 3 in the GAF)?

There seem to be three issues in this one ticket; it's best to split them up as fixes would be independent:

The column names aren't always great and can be confusing.
There are duplicate GPs in the view. Maybe this is a question for somebody else--maybe @cmungall. From my perspective, every ID (discounting the fact that their labels collide) represented in that list seems to referring to a distinct entity, so I'm not quite sure what the expected behaviour should be (again, ignoring the not-so-great labelling).
Column 3 is not a download choice. You are trying to find GAF column 3 in the download, however, that would currently only be available in the "annotations" view, not the "gene product/bioentity" view. If you're trying to work with the data as if it was a view on the GAFs, you'd probably want to be working with the former view. If that particular information is desired for this view, it will need to be added separately at load time.

I'm going to make this issue about the first. This is touched on in berkeleybop/bbop-js#14, so I'm tempted to dupe this or the other. I've changed this one to reflect a more broad labelling issue (and it has better examples).

@kltm, let's not close this ticket prematurely - afraid berkeleybop/bbop-js#14 is written in language I think only you understand...if you like perhaps start a separate ticket that is specifically about the naming of what we internally call the bioentity. Whatever we call this, it should be consistent across the board. "Acc" is weird (and probably my fault).
The third issue is a golr loading bug and could be assigned to @hdietze -- gene_association.goa_human uses SAA1 for P0DJI8, whereas for whatever reason it is ending up as SAA1_HUMAN in golr. See:
http://amigo.geneontology.org/amigo/gene_product/UniProtKB:P0DJI8
You are right though, it has nothing to do with column labels.
Not fully sure I understand your third point. But I think making the column labels consistent should help clarify this.

Thinking about the implementation for berkeleybop/bbop-js#14 and this, they are distinct issues and not dupes (edited above).
@cmungall , I think you meant to say "second" above, edited for clarity.
I've added the ticket #196 and will edit this item to reflect just the scope of bad general labelling.

Not sure if dupe now with #195.


Add helper-test blueprint

the new one includes both integration and unit options.

Moved to https://github.com/ciena-frost/ember-cli-frost-blueprints/issues/3


Key xxx is already defined!(all keys)

Version
Tell us which versions you are using:

react-native-router-flux v3.37.0
react v16.0.o
react-native v0.4.4

Expected behaviour
Actual behaviour
Steps to reproduce
For non-obvious bugs, please fork this component, modify Example project to reproduce your issue and include link here.
1.
2.
3.
Reproducible Demo

Please provide a minimized reproducible demonstration of the problem you're reporting.
Issues that come with minimal repro's are resolved much more quickly than issues where a maintainer has to reproduce themselves.

Not enough information


docs(speculative-module-fetching): remove that it doesn't work in preview because it does

Overview

What is it?

[ ] Feature / enhancement
[ ] Bug
[x] Docs / tests / types / typos

Description
I tested in a fresh qwik app and speculative module fetching appears to be working in preview.
To verify, just install a qwik starter project with the flower and todos. On the home page click on the + button of the counter on a fresh page and you'll see that the signal code is being retrieved from the service worker.
Checklist:

[x] My code follows the developer guidelines of this project
[x] I have performed a self-review of my own code
[x] I have made corresponding changes to the documentation
[ ] Added new tests to cover the fix / functionality

Looks good! Merging.


[Feature Request] Console command tenancy:run

Description of your feature
Version 2.x of Hyn/multi-tenant had a command called multi-tenant:run  which could be used to run any artisan command on a specific tenant.
One usage scenario is for confirming tenant specific routes with the artisan route:list command.

Proposed behavior
For version 5.x of Hyn\Multi-tenant I suggest the command tenancy:run having the following signature:
protected $signature = 'tenancy:run {tenantcommand}
        {--tenant= : The tenant(s) to apply on; use all|5,8 }
        {--arguments= : Arguments for the delegated command}
        {--options= : Options to pass on to the delegated command}
    ';

Current behavior
The feature is currently not supported/implemented.

Information

hyn/multi-tenant version: 5.x
laravel version: 5.6

@luceos Please look into the PR and suggest change if any required!

@mintunitish I too need this (asap) so I merged your code into my versions - problem is, I get errors when using it.
ReflectionException  : Method Hyn\Tenancy\Commands\RunCommand::handle() does not exist
So I change the method fire() to handle() and am presented with this error:
Call to undefined method Hyn\Tenancy\Repositories\WebsiteRepository::all()
I then tried to adapt the code to work within the command I am trying to run and that didn't work either.
Any advice on getting this to work would be most appreciated.
Daniel

I tried the proposed PR and it does not "fully" work.  I had tried to port the 2.x command over as well and pretty much got the same result.
The issue I have is that some routes are missing when running route:list via this command.   I am comparing Laravel 5.6 with Hyn 5.1 to Laravel 5.3 with Hyn 2.x and not sure if this is due to Laravel changes.  The problem, I believe, is that with Laravel 5.6, the app isn't fully booted / bootstrapped when artisan runs.
I know that some routes are missing based on 1) the routes being accessible via URL and 2) installing this package: https://github.com/recca0120/laravel-terminal which show all of the routes described below.
My setup customizes routes in three ways:
1 - conditional statements in routes\web.php
2 - tenant routes in storage\app\tenancy\tenants\XXXX\routes.php
3 - per tenant modules based on https://github.com/caffeinated/modules
Using tenancy:run with the code in this PR, #2 and #3 above are missing.
These routes are displayed when using the laravel-terminal package.
These routes are displayed when using multi-tenant:run Laravel 5.3 + Hyn 2.x

@DeveloperOnCall my hack to make the PR work was:
in RunCommand.php function getWebsitesFromOption():

change queryBuilder() to query()

temporary source hack
in WebsiteRepository.php add:
    public function all()
    {
        return $this->website->all();
    }

OR
in RunCommand.php

add use Hyn\Tenancy\Models\Website;
change function getWebsitesFromOption():
return $repository->all(); to return Website::all();

@athiffau Is your hack working properly?? I am a little bit confused why the PR isn't working. I will incorporate your changes and will see where it goes. Thanks for the update!

I have incorporated the hack that was mention @athiffau . However I am running blind how to incorporate tests for all the commands that Laravel has for the tenant.

@mintunitish the hack is working as per my initial comment: not all routes are returned with the command route:list.  The hack only address issues preventing the PR to execute as intended.
Regarding tests; I'm not sure how to proceed either.
Glad to continue testing as the PR is WIP.  Also glad to contribute in developing tests if some we can come up with some sort of strategy/spec

Brainstorming on the tests. @luceous any tips?? 🤔

@mintunitish I'll take a look at the PR, thank you both for picking this up!

I took inspiration from the example PR and added a custom implementation.


Add benchmark tests

Pull Request Test Coverage Report for Build 24

3 of 3 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.4%) to 79.086%

Totals

Change from base Build 21:
1.4%

Covered Lines:
813

Relevant Lines:
1028

💛  - Coveralls


Update xero_accounting.yaml

Removing invalid account types as noted on https://xero.slack.com/archives/C56QA7KEY/p1665675365964839

Description

Removing
PAYGLIABILITY
SUPERANNUATIONEXPENSE
SUPERANNUATIONLIABILITY
WAGESEXPENSE
Release Notes

Screenshots (if appropriate):
Types of Changes

[ ] Bug fix (non-breaking change that fixes an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Rolled this into the latest release (2.39.1)


INCLUDE: unknown module 'sched.time_in_state'

E:\tools\anaAnaly_myself\perfetto-43.1\python
λ python
Python 3.7.9 (tags/v3.7.9:13c94747c7, Aug 17 2020, 18:58:18) [MSC v.1900 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.

from perfetto.trace_processor import TraceProcessor
tp = TraceProcessor(trace='trace')
tp.query('INCLUDE PERFETTO MODULE sched.time_in_state')
Traceback (most recent call last):
File "", line 1, in
File "C:\olib\python37\lib\site-packages\perfetto\trace_processor\api.py", line 284, in query
perfetto.trace_processor.api.TraceProcessorException: INCLUDE: unknown module 'sched.time_in_state'

tp.query('INCLUDE PERFETTO MODULE sched.time_in_state;')
Traceback (most recent call last):
File "", line 1, in
File "C:\olib\python37\lib\site-packages\perfetto\trace_processor\api.py", line 284, in query
perfetto.trace_processor.api.TraceProcessorException: INCLUDE: unknown module 'sched.time_in_state

Is there any other way I can obtain this table, sched_percentage_of_time_in_state?

Two options:

Wait for us to do a release
Copy the statement which creates the table (and its dependencies) from https://github.com/google/perfetto/blob/main/src/trace_processor/perfetto_sql/stdlib/sched/time_in_state.sql and run that directly instead.

Thank you!

@ddiproietto are we OK to do a release of Perfetto this week?

Yep, let's get that done today.

Why do the same problems still occur？
E:\tools\anaAnaly_myself\perfetto-44.0\python
λ python
Python 3.7.9 (tags/v3.7.9:13c94747c7, Aug 17 2020, 18:58:18) [MSC v.1900 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
from perfetto.trace_processor import TraceProcessor
tp = TraceProcessor('trace101_1')
tp.query('INCLUDE PERFETTO MODULE sched.time_in_state;')
Traceback (most recent call last):
File "", line 1, in
File "E:\tools\anaAnaly_myself\perfetto-44.0\python\perfetto\trace_processor\api.py", line 284, in query
raise TraceProcessorException(response.error)
perfetto.trace_processor.api.TraceProcessorException: INCLUDE: unknown module 'sched.time_in_state'
tp.query('INCLUDE PERFETTO MODULE sched.states;')
<perfetto.trace_processor.api.TraceProcessor.QueryResultIterator object at 0x00000274BCC45EC8>

This should now be resolved with the latest release.


QA for 2016.11

This is on staging now.

[x] Bug fixes for Education Summit Proposals (#551, #552, #547, #548)
[x] Fix for uploading PDFs of financial aid receipts (#549, #550)
[x] Add Caktus logo to footer (#525, #555)
[x] Update Pycon favicon (#525, #555)

All tasks pass QA. :mount_fuji:


The initial pseudocode documentation

Please review carefully and leave LGTM, then I'll merge this to the main branch
@kimseongyu  @purplepig4657
This is the first draft of pseudocode. Some details are not written yet but it still providews a good overview.
Added a link to pseudocode.md in README.md

Just made math expressions to work, like this:
refcnt\_addr = (start\ address\ of\ refcnt\ space) + \frac{(virtual\ address\ of\ a\ buffer)} {16}


[Task]: Consume map of autogenerated names and actual binding parameters and ensure compatibility

Is there an existing issue for this?

[X] I have searched the existing issues

Summary
As part of the Datatype Handling project, the client-side will send the possible data type of each binding parameter along with its value. The client-side will send such payload with the autogenerated name of the actual binding parameter with a view to reducing the payload size.
Why should this be worked on?
The client-side will send the possible data type (JS Type) of each binding parameter along with its value. The client-side will send such payload with the autogenerated name of the actual binding parameter with a view to reducing the payload size.
The client-side will also send the mapping between the autogenerated name and the actual binding parameter name in a different part called parameterMap. The sample request with three binding parameters would look as follows:
------WebKitFormBoundaryj9bhZXa3DECRp83J
Content-Disposition: form-data; name="executeActionDTO"

{"actionId":"627a09673b06f26463e16ba8","viewMode":false, "paramProperties": [{"k1": "STRING"}, {"k2": "NULL"}, {"k3": "NULL"}]}
------WebKitFormBoundaryj9bhZXa3DECRp83J
Content-Disposition: form-data; name="parameterMap"

{"k1":"Text1.text","k2":"Table1.data", "k3": "Api1.data"}
------WebKitFormBoundaryj9bhZXa3DECRp83J
Content-Disposition: form-data; name="k1" filename="blob"
Content-Type: text/plain
abc
------WebKitFormBoundaryj9bhZXa3DECRp83J
Content-Disposition: form-data; name="k2"; filename="blob"
Content-Type: text/plain

null
------WebKitFormBoundaryj9bhZXa3DECRp83J
Content-Disposition: form-data; name="k3"; filename="blob"
Content-Type: text/plain

null
------WebKitFormBoundaryj9bhZXa3DECRp83J--

In this task, the server will consume this new payload and will not apply any logic to the identification of the data type rather it will use the parameterMap in order to decode the original binding parameter's name. It also needs to be ensured that the change in the action execution request body payload doesn't break any existing implementation and hence ensuring compatibility.

In order to consume the above payload the model ExecuteActionDTO needs to be changed like below:
public class ExecuteActionDTO {

    String actionId;

    List<Param> params;

    PaginationField paginationField;

    Boolean viewMode = false;

    Map<String, String> paramPropertiesMap; //"paramProperties": [{"k1": "STRING"}, {"k2": "NULL"}, {"k3": "NULL"}]

    Map<String, String> parameterMap; //{"k1":"Text1.text","k2":"Table1.data", "k3": "Api1.data"}
}

After this change has been implemented both on the client and the server-side do we expect the paramProperties will always exist in the payload even if it's an array?
@nidhi-nair @ChandanBalajiBP

We have decided to go with this structure instead as it helps the server to do less effort with respect to deserialization.
------WebKitFormBoundaryj9bhZXa3DECRp83J
Content-Disposition: form-data; name="executeActionDTO"

{"actionId":"627a09673b06f26463e16ba8","viewMode":false, "paramProperties": {"k1": "STRING", "k2": "NULL","k3": "NULL"}}
------WebKitFormBoundaryj9bhZXa3DECRp83J
Content-Disposition: form-data; name="parameterMap"

{"Text1.text": "k1","Table1.data": "k2", "Api1.data": "k3"}
------WebKitFormBoundaryj9bhZXa3DECRp83J
Content-Disposition: form-data; name="k1" filename="blob"
Content-Type: text/plain
abc
------WebKitFormBoundaryj9bhZXa3DECRp83J
Content-Disposition: form-data; name="k2"; filename="blob"
Content-Type: text/plain

null
------WebKitFormBoundaryj9bhZXa3DECRp83J
Content-Disposition: form-data; name="k3"; filename="blob"
Content-Type: text/plain

null
------WebKitFormBoundaryj9bhZXa3DECRp83J--

cc: @nidhi-nair @ChandanBalajiBP

Test Plan
The regression test suffices as this is a compatibility change.

A demonstration of this delivery is documented here.


math/big: incorrect handling of aliased inputs in GCD

What version of Go are you using (go version)?

$ go version
go1.11.2 linux/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env

What did you do?
Calculate the cofactors x, y using the input variables (a, b) to store the result
d.GCD(x, y, a, b) --> x = 1, y = -1 (correct)
d.GCD(a, b, a, b) --> a = 1, b = 1 (incorrect)
d.GCD(b, a, a, b) --> b = 1, a = -6 (incorrect)
https://play.golang.org/p/KwX7hGGIHu_k
What did you expect to see?
Correct results that match when independent x, y are used.
What did you see instead?
Incorrect results when x and y reference the input variables a, b.

/cc @griesemer


Python 2.6 is not supported, 3.7 tested

Add typing hints in subprocess

Pull Request Test Coverage Report for Build 33

7 of 7 (100.0%) changed or added relevant lines in 2 files are covered.
9 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.7%) to 94.344%

Files with Coverage Reduction
New Missed Lines
%

exec_helpers/subprocess_runner.py
1
83.48%

exec_helpers/proc_enums.py
1
99.09%

exec_helpers/_ssh_client_base.py
7
97.96%

Totals

Change from base Build 31:
-0.7%

Covered Lines:
834

Relevant Lines:
884

💛  - Coveralls


fixfix kerberos config read

Proposed changes
we should read kerberos config  from properties first, so use override hive conf to set.
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 45.58 seconds
stream load tsv:          506 seconds loaded<PHONE_NUMBER>9 Bytes, about 140 MB/s
stream load json:         19 seconds loaded<PHONE_NUMBER> Bytes, about 118 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          29.2 seconds inserted 10000000 Rows, about 342K ops/s
storage size:<PHONE_NUMBER>3 Bytes


Feature request: Print starting point of the scan in the output.

If would be helpful to include the path where the scan was started.
Now:
jlellis@graylog-cmi-008:~$ java -jar scanner-1.3.2.jar /usr/share/java
Logpresso CVE-2021-44228 Vulnerability Scanner 1.3.2 (2021-12-15)

Scanned 1 directories and 2 files
Found 0 vulnerable files
Completed in 0.00 seconds

Suggested:
jlellis@graylog-cmi-008:~$ java -jar scanner-1.3.2.jar /usr/share/java
Logpresso CVE-2021-44228 Vulnerability Scanner 1.3.2 (2021-12-15)
Scanning /usr/share/java

Scanned 1 directories and 2 files
Found 0 vulnerable files
Completed in 0.00 seconds

@jlellis Just released v1.4.0. Added status reporting like this:
Logpresso CVE-2021-44228 Vulnerability Scanner 1.4.0 (2021-12-15)
Scanning directory: c:\
Running scan (9s): scanned 13382 directories, 106337 files, last visit: c:\Users\xeraph\AppData\Local\Yarn\Cache\v1\npm-es6-promise-2.3.0-96edb9f2fdb01995822b263dd8aadab6748181bc\dist\test
Running scan (20s): scanned 28502 directories, 187935 files, last visit: c:\Users\xeraph\AppData\Roaming\Zoom\data\Emojis
Running scan (30s): scanned 48179 directories, 231713 files, last visit: c:\windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.1348.1.7\amd64_microsoft-windows-peerdist_31bf3856ad364e35_10.0.19041.1151_none_91f4a96c9f464c76\r


Add Custom Sample Dashboards

Recreating PR: https://github.com/stolostron/multicluster-observability-operator/pull/1110. The PR needed to be signed; therefore, I am recreating it.
Signed-off-by: dislbenn<EMAIL_ADDRESS>

/hold

Looks like this PR needs more updates, specifically,

adding a README.md
updating uid


Crash on  Compute EFM via CNA with reversibility: off and only consider convex basis: on

Project: SmallExample
Action: Compute Elementary Flux Modes/Vectors via CNA
check reversibility: off
only consider convex basis: on
Traceback (most recent call last):
  File "/home/sthiele/miniconda3/envs/cnapy/lib/python3.7/site-packages/cnapy-0.0.5-py3.7.egg/cnapy/gui_elements/efm_dialog.py", line 231, in compute
  File "/home/sthiele/miniconda3/envs/cnapy/lib/python3.7/site-packages/oct2py/core.py", line 500, in eval
    plot_res=plot_res)
  File "/home/sthiele/miniconda3/envs/cnapy/lib/python3.7/site-packages/oct2py/core.py", line 382, in feval
    store_as=store_as, plot_dir=plot_dir)
  File "/home/sthiele/miniconda3/envs/cnapy/lib/python3.7/site-packages/oct2py/core.py", line 582, in _feval
    raise Oct2PyError(msg)
oct2py.utils.Oct2PyError: Octave evaluation error:
error: questdlg is not available in this version of Octave
error: called from:
    questdlg at line 131, column 5
    conbasis_calc at line 244, column 16
    compute_elmodes at line 247, column 100
    CNAcomputeEFM at line 281, column 5

Fixed on CNA side.


New podspec

Could somebody clarify when we should expect to podspec version update of the AlamofireObjectMapper library update with the last changes of this project?

Hi @zulkis, I just released v1.1.2 of ObjectMapper. The AlamofireObjectMapper podspec should get the latest automatically now.


andreas-wachtel: enables optional proxy for NotificationClient

and removes various java warnings.

looks good - I'm happy to merge but can you bump the version in pom.xml?

👍  thanks for the addition @andreas-wachtel, i'll merge now