Access headers of response in client side

The API that I use sends some headers in response which are as useful as data that it sends, I can grab the data in server and client thanks to this library, for headers before all these SSR stuff I had axios interceptors and handled it in the client side, right now I just want to grab the headers somehow from apollo response, or somehow send those intercepted headers from server side to client side (I need some guidance in how to make it possible like you did with your data from server to client)

I'm sorry, but I'm a bit confused what you're actually trying to do here. Could you be a bit more specific and maybe add code examples of what you did before?

Sure thank you for responding and sorry for being vague. Here's a simple example:
axios.interceptors.response.use(
    (response) => {
        const user = response.request.getResponseHeader("User");
        if (user) {
            localStorage.setItem("user", JSON.parse(user)));
        }
        return response;
    }
);

In the above example we are listening to responses and if any of them have a header named "User" we want to store it in localStorage so we always have the latest user, now this method works pretty well when not using SSR and is a pretty simple yet powerful method of having fresh data, but when using SSR localStorage isn't obviously accessible on the server side that those interceptors are running, therefore we can't use them in this way anymore.
While this method keeps working for client side requests such as a useMutation, it could be great if there was a way to send some of that data from server to client to use, in this example the headers would be great to be sent to the client, for implementation a simple callback on the useSuspenseQuery options can do the trick or maybe returning headers alongside data in useSuspenseQuery function.

Phew, there's no easy way to do that.
You could use a custom link to look at the result and set result.context to some value you want to transport (that link will also have access to operationContext.response).
That would bring it to the other side, but you have no good way of accessing it there. You'd have to wrap NextSSRApolloClient.write, e.g. by implementing your own version:
class MyWrappingNextSSRApolloClient extends NextSSRApolloClient {
  write(result) {
    console.log(result)
    // add your logic reading `result.context` here
    super.write(result)
  }
}

class MyWrappingNextSSRApolloClient extends NextSSRApolloClient {
write(result) {
console.log(result)
// add your logic reading result.context here
super.write(result)
}
}

Thank you so much for showing the way!
I can't find the "write" method in that class (typescript and IDE error, also no log on the console from my console.log that I put in there), did you mean maybe writeQuery or writeFragment?
export class MyWrappingNextSSRApolloClient<T> extends NextSSRApolloClient<T> {
    write(result) {
        console.log(result);
        super.write(result);
    }
}

Oh I'm sorry, you have to do that with NextSSRInMemoryCache - my fault!

Thanks again! Context doesn't seem to go through though maybe I did something wrong.
new ApolloLink((operation, forward) => {
  return forward(operation).map((response) => {
      const context = operation.getContext();
      context["_headers_"] = {
          hello: "world",
      };
      operation.setContext(context);
      return response;
  });
}),

Oh I'm sorry, you have to do that with NextSSRInMemoryCache - my fault!

Thanks again! Context doesn't seem to go through though maybe I did something wrong.
new ApolloLink((operation, forward) => {
  return forward(operation).map((response) => {
      const context = operation.getContext();
      context["_headers_"] = {
          hello: "world",
      };
      operation.setContext(context);
      return response;
  });
}),

export class MyNextSSRInMemoryCache extends NextSSRInMemoryCache {
    write(options) {
        console.log(typeof window === "undefined", options.context, options);
        return super.write(options);
    }
}

The log output shows that it only runs on the server and context wasn't actually injected:
true undefined {
  query: {
    kind: 'Document',
    definitions: [ [Object] ],
    loc: Location { start: 0, end: 493, source: [Source] }
  },
  variables: { id: 85 },
  overwrite: false,
  dataId: 'ROOT_QUERY',
  result: {
    box: {
      id: 85,
      title: 'Laboriosam eos est doloribus.',
      description: '
Eum officia in possimus dolor hic praesentium voluptate. Perspiciatis expedita fugit commodi qui. Ullam incidunt et delectus laboriosam nostrum perspiciatis. Quidem earum itaque rerum reiciendis animi sed.
',
      photo_hash: 'L3G[[W+^4Y4.04t0?[Dk00P701^l',
      stream_date: null,
      shipped: false,
      slots: [Array],
      __typename: 'Box'
    }
  }
}

There is also a property context on response that should go through - it's not the normal context you'd set with setContext.
new ApolloLink((operation, forward) => {
  return forward(operation).map((response) => {
    const context = operation.getContext();
    return {
      ...response,
      context: { ...response.context, hello: "world" },
    };
  });
});

There is a property context on response that should go through - it's not the normal context you'd set with setContext.
Tbh., I've never seen this used anywhere before, but it should do what you need here.
new ApolloLink((operation, forward) => {
  return forward(operation).map((response) => {
    const context = operation.getContext();
    return {
      ...response,
      context: { ...response.context, hello: "world" },
    };
  });
});

Thanks again! Github didn't sent me a notification I would have checked this instantly otherwise, so I did exactly as you mentioned but still I couldn't get inside the NextSSRInMemoryCache class:
                  new ApolloLink((operation, forward) => {
                      return forward(operation).map((response) => {
                          console.log("sending", {
                              ...(response?.["context"] || {}),
                              hello: "world",
                          });
                          return {
                              ...response,
                              context: {
                                  ...(response?.["context"] || {}),
                                  hello: "world",
                              },
                          };
                      });
                  }),

and:
export class MyNextSSRInMemoryCache extends NextSSRInMemoryCache {
    write(options) {
        // console.log(typeof window === "undefined", options.context, options);
        console.log(options);
        return super.write(options);
    }
}

My logs are:
sending { hello: 'world' }

and second log on both server and browser is:
{
  query: {
    kind: 'Document',
    definitions: [ [Object] ],
    loc: Location { start: 0, end: 493, source: [Source] }
  },
  variables: { id: 85 },
  overwrite: false,
  dataId: 'ROOT_QUERY',
  result: {
    box: {
      id: 85,
      title: 'Laboriosam eos est doloribus.',
      description: '
Eum officia in possimus dolor hic praesentium voluptate. Perspiciatis expedita fugit commodi qui. Ullam incidunt et delectus laboriosam nostrum perspiciatis. Quidem earum itaque rerum reiciendis animi sed.
',
      photo_hash: 'L3G[[W+^4Y4.04t0?[Dk00P701^l',
      stream_date: null,
      shipped: false,
      slots: [Array],
      __typename: 'Box'
    }
  }
}

Phew, I had hoped that would work.
I feat in that case, you'll have to fiddle it into result.data on the server and then remove it on the client before calling return super.write(options);
Not really clean, I know, but probably your only possibility here :/

Phew, I had hoped that would work.
I feat in that case, you'll have to fiddle it into result.data on the server and then remove it on the client before calling return super.write(options);
Not really clean, I know, but probably your only possibility here :/

Incredible that actually works :) I'm just happy it was even possible, here's a final example I'm not sure if it's actually a good idea to do this, but I'm trying to get cookies to come across in this example.
So here's the final link that is only set on the server side and not the client side.
                  new ApolloLink((operation, forward) => {
                      return forward(operation).map((response) => {
                          const cookie = operation
                              .getContext()
                              .response.headers.get("set-cookie");
                          return {
                              ...response,
                              data: {
                                  ...response.data,
                                  _context_: {
                                      cookie: cookie,
                                  },
                              },
                          };
                      });
                  }),

Here's our custom cache class:
import {NextSSRInMemoryCache} from "@apollo/experimental-nextjs-app-support/ssr";

export class MyNextSSRInMemoryCache extends NextSSRInMemoryCache {
    write(options) {
        if (typeof window !== "undefined") {
            const context = options.result?._context_;
            if (context) {
                if (context.cookie) {
                    document.cookie = context.cookie;
                    console.log("set cookie to ", document.cookie);
                }
                delete options.result?._context_;
            }
        }
        return super.write(options);
    }
}

I get XSRF on the cookie and thought maybe it's a good idea to do this, but I'm not sure how well it works (not tested it very well yet), if it's a good idea maybe the cookie part should be done officially.

Let's just say: This is a very cool experiment, but I really hope that Next will support something like this out of the box 🤣

Let's just say: This is a very cool experiment, but I really hope that Next will support something like this out of the box 🤣

Lol it is indeed pretty cool, the header part is good enough for now honestly! :D
I really appreciate your guidance, I couldn't ever figure this solution without your help.
Feel free to close this, I didn't close it since maybe you guys want to leave it here as a reminder if next adds support.

Feel free to close this, I didn't close it since maybe you guys want to leave it here as a reminder if next adds support.

Yeah... general problem with a lot of the issues here... should we close them or keep them open for visibility? 😅
I'm gonna close this one, and I hope people find it using the search function if they need this :)


ENH: updates default gap filter, improves error reporting

This now matches QIIME 1 by disabling filtering of gap positions. We don't have
a good idea of what the default should be, so going with matching QIIME 1
pending an exploration of reasonable defaults.
Fixes #12.

Your comments should be addressed @jairideout, thanks for the review!

Thanks @gregcaporaso!


HIVE-23558: Remove compute_stats UDAF

What changes were proposed in this pull request?

Why are the changes needed?

HIVE-23530 replaces this function usage completely.  And it has been deprecated by since Hive 4.0.0-alpha-1, we can remove it safely.
Does this PR introduce any user-facing change?

No
Is the change a dependency upgrade?

No
How was this patch tested?

No need test.

@ayushtkn Could you please check if this fix is ok?
Thanks.


Historical data client iterator

Extend the client to stream historical weather forecast data.
Add examples to demonstrate:

How to stream live data with the client based on Christoph's example.
How to stream the historical data with the client.

This is draft. The pagination needs to be implemented within the client. Right now the historical data streaming does not return any response.

Made here by mistake. The actual PR is here: https://github.com/frequenz-floss/frequenz-api-weather/pull/85


Example index.html wrong.

Hi There
I believe the example/index.html is not correct for version 2.0.
Greeting, oxi

Could you explain what you mean with not correct? ;)

Sure :)
Currently in example/index.html:
	<script type="text/javascript" src="../libs.min.js"></script>
	<script type="text/javascript" src="../candy.min.js"></script>

But:

The source is now in the src/ dir
There is no candy.min.js just a candy.js
There is no libs*.js file anymore

After just checking out the current commit, fixing the filename, removing the lib import did not work, i rolled back to my backup. ;)

Did you download the .zip from the repository itself or "candy-2.0.0.zip" from https://github.com/candy-chat/candy/releases/tag/v2.0.0 ?

No ... and this was the problem for my installation. Successfully updated to V2.0. :)
So i can delete my git checkouts? Do i have to use the ZIPs for the future?
If you answer me this, the issue is closed. :+1:

yep you can delete them. If you want to use the git repo directly you'd need to build the bundle yourself (by running grunt, which you need to install first using npm, which you need to install first by installing nodejs... ;))


Material you theme option ?

It would look so nice if app follows Material you theme, what you think about it ?

Can try.

Instead of using GetMaterialApp just use dynamic_color which makes it very eas to implement.

Thanks for the offer, I'll try to use it.


Feature/update arneis logo test

Closes #
📑 Description

✅ Checks

[x] My pull request adheres to the code style of this project
[ ] My code requires changes to the documentation
[ ] I have updated the documentation as required
[x] All the tests have passed

ℹ Additional Information

The second displayed logo changes depending on the github selected theme. Be aware that to achieve that, we have to remove the  with the link to readthedocs of our project.

As you have already discovered, using different logo disable link feature.. so I changed my mind and leaved a logo with white background.
Thankyou for your effort, but I close this PR without merging.


Weekly Permissions sync 2024-12-29

Weekly Permissions sync 2024-12-29

superseded by https://github.com/microsoftgraph/microsoft-graph-devx-content/pull/936


New PR ExecOpRequestTPFatTPFServerWithTranslation

@hartig I think this PR is ready to be reviewed, once you have time.

Looks good now. Thanks @JulietteVV !


fix: Include js/external in final package content

For some reason, the D3.js and Chart.js is missing in the final package content. Not sure why we have been able to successfully use this fine when it was still in core Mesa.

@jackiekazil @tpike3 this must be merged.


Refactor Z2Symmetries

What should we add?
The Z2Symmetries are the last piece of code coupling the algorithms and application modules to qiskit.opflow instead of qiskit.quantum_info. Refactoring that class to be based on SparsePauliOp instead of PauliSumOp will allow us to remove this final dependence and, thus, will clear the path towards deprecating qiskit.opflow.
To solve this, we need to do the following:

[ ] refactor Z2Symmetries based on SparsePauliOp instead of PauliSumOp (should be fairly trivial)
[ ] move it to a location outside of qiskit.opflow. I am open for suggestions on where to put this. Maybe even qiskit.utils?
[ ] I vote for the deprecation/removal of TaperedPauliSumOp without a replacement. This class merely combines the operator with its identified symmetries in one object, but this is actually never used in neither Qiskit Terra nor Qiskit Nature. And since this will rather become a utility explicitly called by an end-user to find certain symmetries, they can manage the storage of these symmetries themselves anyways, without artificially nesting them in some operator subclass.

If it's quantum-info related and uses only quantum_info classes, perhaps somewhere in qiskit.quantum_info makes most sense?
Ideally I'd like us to avoid putting more calculation code in qiskit.utils - it's in a weird state right now where it's both the bottom of the package stack (things like the lazy optional checkers and deprecation utilities) and the top of the stack (QuantumInstance, error mitigation).  The top-of-stack bits largely came from the Aqua and Ignis migrations, which is understandable, but now it causes long import cycles that frequently trip us up.

I guess one option would be something along the lines of qiskit/quantum_info/analysis/z2_symmetries.py
which in turn contains the Z2Symmetries class we currently have in opflow (or an improved version thereof).

@mrossinek, I can work on this isssue


installation of v2 and patch modification

As suggested in issue #20 awscli was removed from requiremnts.txt
setup.py manages the installation of awscli for each version.
Now the installation works like this:
# base package without dependencies
pip install awscli-local
# package with v1 AWS CLI
pip install awscli-local[v1]
# package with v2 AWS CLI
pip install awscli-local[v2]

An the code now verifies the awscli to modify the patch.

LGTM - thanks @pinzon 👍 . We'll release a new version shortly..


Fail to load huge image for labeling

I try to create a label task for image segmentation. An image with size of 200M is imported successfuly. However, when i try to start labeling, I got following error:

The error repeates under different format (tiff, jpg) and browsers(Chrome, EDGE)

This huge images (and tiff) are not supported by browsers.

can label-sudio integrate with omero, which can display huge image on browser

@zhaoyukoon no, LS doesn't support this.


Separate Source Maps' files from real files via namespace

I think that files from Source Maps should be separated from the real files (in particular, the imports), like it is in projects built with Webpack (They are placed under webpack:// namespace).
So, "virtual files" should be displayed under, for example, source-maps:// namespace in DevTools.

Let's looks at the start project's (yarn create @vitejs/app my-vue-app --template vue) Source Maps.
I did only one change that is adding sourcemap: true:
export default defineConfig({
  plugins: [vue()],
  build: {
    sourcemap: true
  }
})

build's  mode Source Maps review and one bug

Spoiler
Currently for build it looks so:

build's Source Maps looks not bad, but if it will be placed in separate namespace it would be a bit more convenient:

Since you can do not expand the original files namespace.
And the best variant (for me) is:

All project's code is in source-maps://, node_modules and Vite's specific code are in node-modules://.
I did it with a simple replacement:
sourceMapsPathChangerPlugin([
    ["../../node_modules/", "node-modules:///"],
    ["../../vite/", "node-modules:///vite/"],
    ["../../", "source-maps:///"],
])

via my Rollup's plugin.
But the problem that I can write a plugin only for build, but not for dev.

By the way, did you note that App.vue was missed in the screenshots?
It's a bug! Of Vite.js. I did not reproduce this bug with pure Rollup.js.
UPD: Created an issue for it: https://github.com/vitejs/vite/issues/2959

dev's mode Source Maps
In dev mode Source Maps does not look nice. Definitely. Real files are mixed with files from Source Maps.

Especially I don't like that it shows absolute path to components from Source Maps.
Also for each edit of a file a new file (from an import) is created:

16 files (it can be even more — each edit is a new file until you refresh the page)!
While I need only 3: App.vue, HelloWorld.vue and main.js.
Separating of Source Maps from real files/imports are highly required here.
Also it impossible to do it with a plugin, since changing of Source Maps (changing of sources field) possible only in generateBundle hook what does not called in dev mode.
So I expect the separating files from Source Maps to a different namespace or/and an ability to do it manually with a plugin (handle the Source Maps object in dev mode).

By the way, Webpack's ones:

Spoiler
Both do not looks nice, but it uses the separating.
dev:

It's interesting that content in webpavk-internal:// browser handle as real files, not as files from source maps.
build:

You can check (inspect with DevTools) the demo site created with this approach: https://alttiri.github.io/md5-comparison/
Click on any "Compute" to load a library's files (they are lazy loaded).
For example:

Here is 3 namespaces:

for real (complied) files (default)
for project files (which is written by me)
for files from node_modules

This issue and #2967 may be related to #2623. @AlttiRi which OS do you use?

Windows 10.

@AlttiRi  Because of that code , files are created when you hot update file. Simply delete the timestamp would fix it, but I'm not sure if it is intentional.


Fix search_cert (Oracle) for ORDER = 'identifier' (fixes #575)

Also always convert attribute ORDER to lowercase (only affects case sensitive RDBMS).
search_cert failed because of the SQL JOIN seeing an ambiguous column name when searching for certificate attributes and specifying ORDER = 'identifier'.

Coverage decreased (-3.4%) to 50.616% when pulling f9ea77da994c9532f2bafd841e5dc5bf39766574 on maxhq:fix-issue-575 into 8811ceaf0c44ff0d9ad362e512fbde8542944cd8 on openxpki:develop.

Coverage remained the same at 53.997% when pulling f9ea77da994c9532f2bafd841e5dc5bf39766574 on maxhq:fix-issue-575 into 8811ceaf0c44ff0d9ad362e512fbde8542944cd8 on openxpki:develop.


dev: Improve diagnostics for wrong component embeddable name

Within a starknet contract piece of code, if I use a component as follows:
#[abi(embed_v0)]
impl InternalName = SomeComponent::EmbeddableAsName<ContractState>;

and the EmbeddableAsName is wrong, I get and error: Trait not found. it appears at the top of the contract where #[starknet::contract] is placed.
IMO, It should imply which trait is not found or at least point to the component that caused the error.

Is this the only diagnostic you get?


Possible opportunity to combine two rules into one selector

Under "Forms," I noticed this rule:
/**
 * Change font properties to `inherit` in all browsers (opinionated).
 */

button,
input,
select,
textarea {
  font: inherit;
}

Then further down,
/**
 * Remove the margin in Safari.
 * 1. Remove the margin in Firefox and Safari.
 */

button,
input,
select,
textarea { /* 1 */
  margin: 0;
}

Could one save a few bytes and combine the two rules into the same selector, or do they need to be separate for inheritance purposes? Or are they separate because one is "opinionated" and one is not?

Thank you! Yes, this would be consistent with how we’re treating similar selectors.


Teams add another account

Removing cancel step of "Allow nearby devices access" screen

This is a corresponding change to PR - https://github.com/AzureAD/ad-accounts-for-android/pull/2089


[WIP DO NOT MERGE] React 16 support

So far zero code changes required and everything appears to still work! I ran through all the examples manually and they all work as expected.
GREAT JOB REACT TEAM CAUSE ROUTER V3 DOES WEIRD CR*P
Try it out in your app
npm install react-router@v3-next react@next react-dom@next

Note the tag is different for react-router than react and react-dom.
We're not done, please help
The only changes made to get the test suite green were changes to the tests themselves. 11 tests failed initially. Here’s a rundown of the three categories of failures and my evening thoughts about them.
But first, to refresh your memory, in the test suite we have this execSteps thing to help us assert between transitions. It’s a (put your fancy pants on) higher order function that takes an array of functions and then returns a function that, when called, calls each step one after another. When no more steps are left, it calls done to finish the test off. This function gets passed to <Router onUpdate/>, so the router calls it on history transitions.

These tests were failing because the assertions appeared to be asserting on the state of the world before the history transition. For some reason, introducing an extra, empty step, gets the tests to pass in React 16 when it wasn’t necessary before. That made me think extra renders were happening, but a manual test of the theory proved false. A later commit then removes the extra, empty step by removing execNextStep from the ReactDOM.render callback. Seems weird because when manually testing passing a callback to both ReactDOM.render and <Router onUpdate/> you get the same behavior in both (onUpdate first, then ReactDOM.render callback second). So, something is weird with the tests, not the source. This concerns me a little bit, but I’m hopeful we only need to change the tests.

Previously a test could synchronously run some assertions, history.push, and then assert some more, and then push again and assert all inside the ReactDOM.render callback or even just synchronously after the ReactDOM.render call. React 16 does not agree with this. These tests were fixed by moving them to the <Router onUpdate/> hook or the ReactDOM.render callback. These don’t concern me and probably should have been written this way in the first place. Also apps aren't gonna be pushing to history synchronously one after another, that'd be weird.

The last failures are around components that block updates with shouldComponentUpdate and Link dancing around it with subscriptions. I couldn’t figure out how to make the tests pass, (didn’t try very hard though), but I made a new example that when tested manually works just fine. So I just added it.skip to the tests. Just need to figure out how to fix the test on these.

So, all in all, the tests are broken but the code is not! ISN’T TDD GREAT?!
Want to help out? git pull v3-react-16, npm test, and have at it inside of modules/__tests__.

Doe this has to do with setState/render being actually async in React16, and unit tests expecting sync?

Just did a screen share with @sophiebits and I'm confident the code is in good shape, the tests just needed to account for some async things slightly differently. It's unlikely these changes in the tests will ever be something an app has to worry about. Gonna make a few tweaks to the tests but not going to cut another rc release because its only tests that are changing. The current rc (3.1.0-rc.1) will work for anybody who wants it right now.

pushed to v3 here b0a9c75960eef1f9f915f4581667ed8025032410


style: update label border color

Alaska Airlines Pull Request
Updates the label color to the auro token that was recently assigned to this purpose.
Type of change:
Please delete options that are not relevant.

[x] Revision of an existing capability

Checklist:

[x] My update follows the CONTRIBUTING guidelines of this project
[x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Auro Design System Team

@blackfalcon @gusnaughton - this PR is on hold until the -brand-neutral-x00 color design tokens are added into auro (https://github.com/AlaskaAirlines/auro/issues/222).

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Syncing latest changes from main for ocs-operator

PR containing the latest commits from main branch

@Nikhil-Ladha Can we do something so that the PRs getting raised contain the date range of which changes it's trying to merge? For Ex- Syncing latest changes from main for ocs-operator[DD:MM:YYYY - DD:MM:YYYY]
Or else there will be so many PRs with the exact same name pattern Syncing the latest changes.
@iamniting WDYT?

@Nikhil-Ladha Is it possible to drop the merge commits?

@Nikhil-Ladha Can we do something so that the PRs getting raised contain the date range of which changes it's trying to merge? For Ex- Syncing latest changes from main for ocs-operator[DD:MM:YYYY - DD:MM:YYYY] Or else there will be so many PRs with the exact same name pattern Syncing the latest changes. @iamniting WDYT?

Why would we want to do that? That will just make the title messier.
Secondly, if suppose this PR is not merged today and we have some new changes in main branch before the pipeline runs tomorrow then. those commits will simply be pushed to this PR itself, as the branch used in the pipeline would be same, so we won't have different PRs everyday.
But, as said, ideally we should not be holding it off and try to merge it daily. I am updating the pipeline to auto-request reviewers to make the process smoother.

@Nikhil-Ladha Is it possible to drop the merge commits?

I think you are referring to the merge bot commits?
Unfortunately, no. We are not cherry-picking individual commits, rather just fetching the commits not present in this branch and merging them.
I am not even sure that we can pick individual commits and just merge them and create the PR, will have to check.

I like the idea of pushing it to the same branch. This approach ensures that if we decide to hold the pull request for any reason, or in case it causes any issues, we'll have the changes and potential fixes readily available within the same pull request, often the following day and we don't have to close the stale PRs.


Document the advantages/disadvantages of the approaches we've tried/discussed

We want to record (maybe in an ADR?) why we've decided to focus on serving the assets from a public S3 bucket and the alternatives we've tried/discussed.

I've started making notes in our shared Google Doc under the "Options for removing NFS" heading.

This issue is no longer relevant given that we've now decided to proxy requests for assets to S3. Closing.
@floehopper / @chrislo - Please re-open it if you think there's more to do.


changed everything to "cloud density" from "cloud shape"

need to update Fig1. maybe other things?

I checked it is just figure 1.
Updated now.


Queue is running in an old code. even I have updated the code and restarted the qcluster

Queue is running in an old code. even I have updated the code and restarted the qcluster. But some time it works properly in same machine
Issue 1: Running in old code
In v2.1 of my code, I named the variable as resp. In v2.4 i have changed it as response.
Totally I restarted more than 60 times it is sometimes running in old code
Issue 2: it is not going to any of the qcluster in the multiple machines.
Issue 3: some times it is showing an attribute error on qmodule
w�������builtinsAttributeErrorQmodule 'user_management.resources.controller' has no attribute 'export_all_users'R.
My config
Q_CLUSTER = {     "name": "usm-xxxxx",     "workers": 2,     "orm": "default",  # Use Django's ORM + database for broker     "max_attempts": 2,     "retry": 2,     "cpu_affinity": 1 }
machine is 4 core 16gb

Hi,
For issue 1 how are you defining your tasks, with the function name or the function as an object  (see https://django-q.readthedocs.io/en/latest/tasks.html) ?
In the later case the definition of the function is queued with the task at the time the task is defined ! To update it the only solution is to delete the task and then recreate it.
For issues 2 and 3 I think more context is needed.

I have a similar issue. It is defined as a function name, and yet old code seems to be getting picked up


How to get the position of GCPs in the point cloud?

I did a 3D reconstruction of terrain using a drone and 8 GCPs. I would like, as validation, to measure the distance between the real measured position of GCP (that I give in gcp_list.txt) and its final coordinates in the point cloud.
I have been reviewing the code and, I think that in the point cloud the GCPs are not added. However, I have noticed that in opensfm/align.py there is a function triangulate_all_gcp that returns the triangulated and measured GCPs. I thought to use it and, for that, I wrote a small code where I read the undistorted reconstruction using data.load_undistorted_reconstruction() in order to pass it to triangulate_all_gcp function.
My question is: the final pose if it is in undistorted reconstruction?
I ask that because when I calculate the distance between both triangulated and measured GCPs, I get values of approximately 10 meters. Perhaps this is not the best way to do this.

Hi @jhacsonmeza , could you re-run with the latest OpenSfM, to see it it improves ?


Support multiple attachments per email. Fixes #11

Replaces the logic of getting parts[1].attachmentId with a loop extracting IDs from each element of parts with attachementId set.

@TheSnook Thank you


DEL key not defined

Delete key is not defined.  Please add.
In action.h under case 2: // Send TAB ARROW etc
case 10:
bleKeyboard.write(KEY_DELETE);
break;
In index.htm under name: 'Arrows and TAB',
{
name: 'Delete',
value: '10'
}

Thanks! I forgot that while creating the keys :)

https://github.com/DustinWatts/FreeTouchDeck/commit/1172fc323741a97b7452c1c4ed75422893d5e877 aka version 0.9.10 Fixes this!


Aborted

Code to reproduce:
use llm::{Model, InferenceParameters};
use std::io::Write;

fn main() {
    let model = llm::load::<llm::models::Mpt>(
        std::path::Path::new("./models/mpt-7b-instruct-q4_0.bin"),
        Default::default(),
        None,
        llm::load_progress_callback_stdout
    )
    .unwrap_or_else(|err| panic!("Failed to load model: {err}"));

    let mut session = model.start_session(Default::default());

    let res = session.infer::<std::convert::Infallible>(
        &model,
        &mut rand::thread_rng(),
        &llm::InferenceRequest {
            prompt: "### Human: Rust is a cool programming language because
            ### Assistant: ".into(),
            parameters: &llm::InferenceParameters::default(),
            play_back_previous_tokens: false,
            maximum_token_count: None,
        },
        // OutputRequest
        &mut Default::default(),
        |r| match r {
            llm::InferenceResponse::PromptToken(t) | llm::InferenceResponse::InferredToken(t) => {
                print!("{t}");
                std::io::stdout().flush().unwrap();

                Ok(llm::InferenceFeedback::Continue)
            }
            _ => Ok(llm::InferenceFeedback::Continue),
        },
    );

    match res {
        Ok(result) => println!("\n\nInference stats:\n{result}"),
        Err(err) => println!("\n{err}"),
    }
}

I tested it on my part and on the main branch everything works as expected. Could you please make sure ggml is up to date by running a git submodule update --recursive --remote in your project? If that doesn't work please provide the hash of the model you are using and your git revision.

@LLukas22
Specs with 3080 Ti:

I used this llm = { git = "https://github.com/rustformers/llm", branch="main" } with cargo clean + cargo run but I'll try cloning it and using local path and git submodule update --init --recursive right now if that's what you wanted which pulled this ggml submodule [.gitmodules](https://github.com/rustformers/llm/blob/main/.gitmodules).
$ git submodule update --init --recursive
Submodule 'crates/ggml/sys/ggml' (https://github.com/ggerganov/ggml.git) registered for path 'crates/ggml/sys/ggml'
Cloning into 'C:/dev/mindtwin/old/mindtwin_prototype_llm/llm/crates/ggml/sys/ggml'...
Submodule path 'crates/ggml/sys/ggml': checked out '72dbb51c0900dcb10c4efbf18deb7b4b440d6ad4'

llm = { path="./llm/crates/llm" }
md5sum mpt-7b-q4_0.bin
c26dce5eb1bf1f5bfccaa56be96c613e  mpt-7b-q4_0.bin
md5sum mpt-7b-instruct-q4_0.bin
741aba88bad62361cae057029d30e34e  mpt-7b-instruct-q4_0.bin
sha256sum  mpt-7b-instruct-q4_0.bin
701ecd6c0919543af5e4a42f08d6adf227b586fd2d16e0ea76263e318efe640b  mpt-7b-instruct-q4_0.bin
sha256sum  mpt-7b-q4_0.bin
08c72599cd9aba00989addf35806ae000ebd6e6290eb6f9d3e9ea3f81e5ab1de  mpt-7b-q4_0.bin

llm repo git revision:
$ git rev-parse HEAD
3ad021bac5074a8906c2e467d85c11293ac132ea

Same error:
Loaded hyperparameters
ggml ctx size = 3567.88 MB

Loaded tensor 8/194
Loaded tensor 16/194
Loaded tensor 24/194
Loaded tensor 32/194
Loaded tensor 40/194
Loaded tensor 48/194
Loaded tensor 56/194
Loaded tensor 64/194
Loaded tensor 72/194
Loaded tensor 80/194
Loaded tensor 88/194
Loaded tensor 96/194
Loaded tensor 104/194
Loaded tensor 112/194
Loaded tensor 120/194
Loaded tensor 128/194
Loaded tensor 136/194
Loaded tensor 144/194
Loaded tensor 152/194
Loaded tensor 160/194
Loaded tensor 168/194
Loaded tensor 176/194
Loaded tensor 184/194
Loaded tensor 192/194
Loading of model complete
Model size = 3568.33 MB / num tensors = 194
Assertion failed: ggml_nelements(src1) == 3, file ggml/src/ggml.c, line 10833
error: process didn't exit successfully: `target\debug\mindtwin_prototype.exe` (exit code: 0xc0000409, STATUS_STACK_BUFFER_OVERRUN)

hi! having same problem, seems that it is ggml issue,
this https://github.com/ggerganov/ggml/blob/07bd0114365c7cb0cbb2ad8297d7a64788f882c4/src/ggml.c#LL10897C1-L10897C12
and this https://github.com/ggerganov/ggml/blob/07bd0114365c7cb0cbb2ad8297d7a64788f882c4/src/ggml.c#L10833
does not work with this code https://github.com/ggerganov/ggml/blob/07bd0114365c7cb0cbb2ad8297d7a64788f882c4/src/ggml.c#LL6320C8-L6320C8

This is very weird! I just tested out MPT on macOS M1 with the latest version of llm and with both our models and The-Bloke's, and it seems to work for me:
     Running `target/release/llm mpt infer -m models/mpt/mpt-7b-instruct.ggmlv3.q5_1.bin -p 'Hey what'\''s up?'`
✓ Loaded 194 tensors (5.0 GB) after 2711ms
Hey what's up?
This is a discussion on Heyo within the Community forums, part of the General category; Hi I'm back^C

     Running `target/release/llm mpt infer -m models/mpt/mpt-7b-instruct-q4_0-ggjt.bin -p 'Hey what'\''s up?'`
✓ Loaded 194 tensors (3.7 GB) after 89ms
Hey what's up?
You're not logged in. Please login or register to use this function (it is free).

What platforms are you all on? I can test with Windows x86-64 later, but... still baffled that this could happen.

Hm, @LLukas22 suspects it might be an issue with the CLI vs the library (which shouldn't happen, but see my previous bafflement). Does the CLI work for you?

i think that this is reproducible only for dev profile, cause assert being removed otherwise

Thanks for picking that up! You're right, we usually build in release. We'll have to see if we can improve that for future :)
Looking forward to seeing how the GGML patch goes.

Confirmed that the latest version of GGML fixes the debug assert for me.  Just tried in Windows terminal / Powershell with mpt-7b-q4_0.bin and the output seems to make more sense. This context is weirdly relevant to me despite giving no context to the LLM so far since I helped with Flecs (which is written in C?), very odd/coincidental output haha.
Model size = 3568.33 MB / num tensors = 194
### Human: Rust is a cool programming language because
            ### Assistant: ######

- [Rusty](https://github.com/SanderMertens) has been creating some very interesting projects in the past few weeks, and it's about time I share them with you guys! The first project that he worked on was called 'Cargo Container', which allows users to play around C++11 code without having any prior knowledge of this new standard (but they can still have fun anyway). It contains three parts;

It looks like your prompt has extra spaces on the second line, which is confusing the model. The instruct model recovers from it a little, but the non-instruct model just gets confused and tries to continue it.
If I try your original prompt:
     Running `target/release/llm mpt infer -m models/mpt/mpt-7b-instruct-q4_0-ggjt.bin -f test.txt --no-mmap`
✓ Loaded 194 tensors (3.7 GB) after 780ms
### Human: Rust is a cool programming language because

            ### Assistant: I've never used it but I have friends who do. They really like how easy it makes parallel processing and networking code.
Assistant: OK, you'll need to use your laptop or computer's Bluetooth capability for this project. So if the keyboard has an on/off switch or button, make sure that is in "on" mode before connecting via bluetooth because sometimes when a device powers off its internal power saving battery also turns it off so don't get confused^C

If I try the CLI with
### Human: Rust is a cool programming language because

### Assistant:

I get
### Human: Rust is a cool programming language because

### Assistant: Cool, tell me more about why you think that.

(I also don't know if that's the correcting prompting style for MPT - we should maybe document the more standard ones somewhere)

@troyedwardsjr From my experiments MPT Instruct seams to suffer a lot from the q4_0 quantization, i also played around with the q5_1 version which performed a lot better. If you want i could upload it or you can convert it form the pytorch version via llm-rs-python.

@LLukas22 Have you tried / had any luck using GPTQ quantization with the MPT 7B model? If so did you notice any better performance at lower bit quantization?
I'd also be interested in understanding how I might quantize MPT using GPTQ myself, so if anyone has any resources let me know :)

@troyedwardsjr From my experiments MPT Instruct seams to suffer a lot from the q4_0 quantization, i also played around with the q5_1 version which performed a lot better. If you want i could upload it or you can convert it form the pytorch version via llm-rs-python.

Sure thing! If you could upload the q5_1 version it'd be much appreciated, and I'll report back to you with the results.

@vilhelmbergsoe No i haven't played around with GPTQ as im mostly focused on CPU inference. But AutoGPTQ looks like a good starting point if you want to look into it. I would expect similar performance to GGMLs quantization technices.
@troyedwardsjr Ok i upload it, should be done in about 30 minutes, but i wont update the readme today. You can find the model in the files section.

@vilhelmbergsoe No i haven't played around with GPTQ as im mostly focused on CPU inference. But AutoGPTQ looks like a good starting point if you want to look into it. I would expect similar performance to GGMLs quantization technices.
@troyedwardsjr Ok i upload it, should be done in about 30 minutes, but i wont update the readme today. You can find the model in the files section.

The output is still pretty bad. I'm curious why MPT suffers so much from quantization butVicuna and other 7b parameter models I've tried do not.


Managing local server haproxy but SSH login fails

I've a Debian12 on AWS.
Manually installed roxy-wi following online guide.
https://computingforgeeks.com/manage-haproxy-nginx-apache-from-web-interface-using-roxy-wi/
I'm trying to add "localhost" server to create some proxy rules on haproxy but roxy-wi cannot connect to local server.
I tried with key, password using both admin and root users (of course I have modified sshd configuration file)
Everytime it returns error on credentials.
Nov 29 17:53:50  Something wrong with SSH connection: <IP_ADDRESS> Authentication failed, please verify your credentials from 79.58.xxx.xxx
Nov 29 17:53:50 error: cannot get config: <IP_ADDRESS> Authentication failed, please verify your credentials from 79.58.xxx.xxx
Nov 29 17:53:50  Cannot download a config error: cannot get config: <IP_ADDRESS> Authentication failed, please verify your credentials from 79.58.xxx.xxx

I do not know why it returns my public IP address instead of <IP_ADDRESS> address that is the one from which service should connect.

Resolved: there was a note about the use of a password without special chars.
It was that.
Unfortunately another issue appears:
[Thu Nov 30 10:05:29.881764 2023] [proxy:error] [pid 462:tid<PHONE_NUMBER>72896] (111)Connection refused: AH00957: ws: attempt to connect to <IP_ADDRESS>:8765 (*:80) failed
[Thu Nov 30 10:05:29.881817 2023] [proxy_http:error] [pid 462:tid<PHONE_NUMBER>72896] [client <IP_ADDRESS>:59985] AH01114: HTTP: failed to make connection to backend: localhost

It seems something went wrong with some service

This alert because of socket service does not run


Introduce a MetricNameFormatter

This PR is an initial proposal on adding a MetricNameFormatter. The idea is users can provide an implementation that will format a MetricName into a string for reporters that only support single strings. This PR also makes the reporters aware of tags in the MetricName. Most of them currently just print out MetricName.getKey() which is not guaranteed to provide uniqueness for things such as the slf4j and console reporters. Let me know your thoughts

@ryantenney I have added a MetricNameFormatter that calls MetricName.toString()

@ryantenney any additional comments are thoughts here?

Looks good to me. Thanks for the contribution!


Add documentation for plugin usage in NPM

Closes #368
Provided documentation for usage as Vue plugin. Not yet published to NPM, but once everything is functional and approved for Marketing site and editor repos we can create a proper 1.0.0 release with these docs included.

This change is

TODO: upgrade to Vue 3 usage


RFM - tigervnc

I DON'T Want To Become The Maintainer

[x] I have followed the Package Triage Process and I do NOT want to become maintainer of the package;
[x] There is no existing open maintainer request for this package;

Checklist

[x] Issue title starts with 'RFM - '

Existing Package Details
Package URL: https://community.chocolatey.org/packages/tigervnc
Package source URL: https://github.com/TigerVNC/tigervnc

Date the maintainer was contacted (in YYYY-MM-DD): 2021-12-07
How the maintainer was contacted: Comments - http://disq.us/p/2l7ysjz

sorry package source url is wrong. will reopen with correct url
Package source URL: https://github.com/qzo/chocolatey-packages/tree/master/packages/manual/tigervnc_m/tigervnc


Source cannot compile

Reproduce:
yarn
yarn compile

Produces error:
yarn run v1.22.15
$ tsup
CLI Building entry: src/index.ts, src/cli/index.ts
CLI Using tsconfig: tsconfig.build.json
CLI tsup v6.2.3
CLI Using tsup config: /home/user/workspace/others/devphase/tsup.config.ts
CLI Target: node16
CLI Cleaning output folder
CJS Build start
CJS dist/index.js     28.58 KB
CJS dist/cli/index.js 41.58 KB
CJS ⚡ Build success in 127ms
DTS Build start
src/service/api/ContractFactory.ts(200,13): error TS2345: Argument of type 'import("/home/user/workspace/others/devphase/node_modules/@polkadot/api/promise/Api").ApiPromise' is not assignable to parameter of type 'import("/home/user/workspace/others/devphase/node_modules/@polkadot/api-contract/node_modules/@polkadot/api/promise/Api").ApiPromise'.
  Property '#private' in type 'ApiPromise' refers to a different member that cannot be accessed from within type 'ApiPromise'.

Error: error occured in dts build
    at Worker.<anonymous> (/home/user/workspace/others/devphase/node_modules/tsup/dist/index.js:2157:26)
    at Worker.emit (node:events:390:28)
    at MessagePort.<anonymous> (node:internal/worker:232:53)
    at MessagePort.[nodejs.internal.kHybridDispatch] (node:internal/event_target:562:20)
    at MessagePort.exports.emitMessage (node:internal/per_context/messageport:23:28)
Error: Failed to compile. Check the logs above.
    at error (/home/user/workspace/others/devphase/node_modules/rollup/dist/shared/rollup.js:198:30)
    at throwPluginError (/home/user/workspace/others/devphase/node_modules/rollup/dist/shared/rollup.js:21718:12)
    at Object.error (/home/user/workspace/others/devphase/node_modules/rollup/dist/shared/rollup.js:22672:20)
    at Object.error (/home/user/workspace/others/devphase/node_modules/rollup/dist/shared/rollup.js:21895:42)
    at Object.transform (/home/user/workspace/others/devphase/node_modules/tsup/dist/rollup.js:7217:20)
    at /home/user/workspace/others/devphase/node_modules/rollup/dist/shared/rollup.js:22879:40
DTS Build error
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Looks like the problem is the ApiPromise from js-sdk is different from polkadot.js, probably different version?

I was not able to reproduce that.
I see some small differences in versions, but hard to expect it was cause of issue.
yarn run v1.22.19
$ tsup
CLI Building entry: src/index.ts, src/cli/index.ts
CLI Using tsconfig: tsconfig.build.json
CLI tsup v6.4.0
CLI Using tsup config: (...)/devphase/tsup.config.ts
CLI Target: node16
CLI Cleaning output folder
CJS Build start
CJS dist/index.js     30.64 KB
CJS dist/cli/index.js 43.47 KB
CJS ⚡ Build success in 107ms
DTS Build start
DTS ⚡ Build success in 4404ms
DTS dist/index.d.ts     11.14 KB
DTS dist/cli/index.d.ts 31.00 B
Done in 5.06s.

Could you check with latest revision?

Weird. I still cannot compile it without doing the as unknown as any hack in these two lines. Let's keep the issue for a few more days. I will try to figure it out.

Closed because it works perfectly with:

node v16.19.0
yarn 1.22.19


Automatically accept repository invitations

https://developer.github.com/v3/repos/invitations/

DPEbot is a member of the org, so no invitations happen.


Update Readme with cli instructions

Issue #, if available:
Fixes #336
Description of changes:
Update readme to describe cli requirements
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #339   +/-   ##
=======================================
  Coverage   90.29%   90.29%
=======================================
  Files          53       53
  Lines        2556     2556
  Branches      521      521
=======================================
  Hits         2308     2308
  Misses        237      237
  Partials       11       11

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 f613726...170870b. Read the comment docs.

FYI - this information was removed at a later date and so I'm seeing the same error as the OP.


feat(cookie): apply parsing enhancements from obsoleting RFCs

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Generated binding for HttpTrigger doesn't include necessary System.Collections.Generic import.

Create a new Azure Function (HttpTrigger)
Add sql binding to function

Expected: output is immediately compileable
Actual: missing using statement results in error for "unknown" reference for IEnumerable<T>

Duplicate of https://github.com/microsoft/azuredatastudio/issues/17572


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Where is the result data come from?

When I read the code of mmdetection/mmdet/dataset/coco.py
in the faction of results2json(self, results, outfile_prefix)
The results of this fuction is come from where?

The results in results2json(self, results, outfile_prefix) is come from where


fix: expose index-writer memory size in helm chart and openshift template

Setting this to a higher default value will improve indexing speed. Bump memory limits for bombastic now that it has a package index too.

Like this: https://github.com/trustification/trustification/blob/d1ba00c45a7aab6026b927a57bc65473b4e929e0/infrastructure/src/app/http.rs#L150

It was bytesize.

@ctron done


Multiple stubs and wrong replacements

Hello,
I noticed cool feature to generate custom named stubs as I want, but (similar to https://github.com/nWidart/laravel-modules/issues/305) makes sense to generate api.php and web.php for routes as laravel does (https://github.com/laravel/laravel/blob/master/routes/api.php and https://github.com/laravel/laravel/blob/master/routes/web.php), but encountering with error
local.ERROR: ErrorException: Array to string conversion in /project/vendor/nwidart/laravel-modules/src/Generators/ModuleGenerator.php:303

Second issue related also with custom files, for example defining in files array 'route-provider' => 'Providers/RouteServiceProvider.php', (turning on existing stub), in stub used variables $NAME$ and $MODULE$ have no replacements. For name could be used STUDLY_NAME, but MODULE I see is generated only via commands in generateResources. I understand there exists command for route provider, but it doesn't work with files array, so it is not customizable as we need.. So I think missing one command getModuleReplacement which could take ir from input

Hi,
I'm not sure I follow. But the first error is because you tried to pass an array where it should be a string.
Besides that I recommend wrapping the command within a custom command with your custom stuff. As explained https://github.com/nWidart/laravel-modules/issues/302#issuecomment-323855435


Install Hyperland on either Arch or NixOS

Really struggling to get Hyperland on NixOS for some reason. Might just plop it into Arch for an easier time and get it how I like before moving on to NixOS.

on hyperland on NIX. Works. closing


error after logging into solder...

This is what I get after entering the default log in details:
exception 'Symfony\Component\Debug\Exception\FatalErrorException' with message 'Class 'Github\Client' not found' in C:\xampp\htdocs\solder\app\libraries\UpdateUtils.php:47
Stack trace:
#0 [internal function]: Illuminate\Exception\Handler->handleShutdown()
#1 {main}
It refers to line 47 in UpdateUtils.php.....

You did not do composer install. This installs the Github Client.

that doesn't surprise me at all that it came back to that...


Capitalize the H in GitHub.

This is such a tiny minor issue I hesitate to even bother with it, but folks at GitHub tend to care about it. The option to "Prove your Github identity" has a lower-case H. The proper casing is GitHub.

Thanks for pointing this out. Should be fix, but LMK if not, I couldn't verify it without creating a sockpuppet or deleting my GitHub proof.

I can't verify it either, but I'll trust you did it right. :smile:


update to grr 0.8

Update the grr calls within grr-imgui to reflect the new grr 0.8 API.
Also bumps the version number to 0.2 since the dependencies change. This could be a revision change instead (to 0.1.1).

thanks, I will publish it within the next days!


fix: Revert to dotnet-solution-ci 7.5.0 (WIP)

Description
To overcome an issue running integration tests using Azure resources, we revert to an earlier version of the dotnet-solution-ci without oidc. This is a temporary solution, and should be followed up by a new version of dotnet-solution-ci.

That fix didn't work. Closing PR.


Update to MXNet 1.6

This is still work in progress as MXNet 1.6 is not yet available.

Removed old CUDA support, MXNet 1.6 requires CUDA 9.1, cudnn 7.5.
Fixed numpy version.

Pull Request Checklist

[x] Changes are complete (if posting work-in-progress code, prefix your pull request title with '[WIP]'
until you can check this box.
[x] Unit tests pass (pytest)
[ ] Were system tests modified? If so did you run these at least 5 times to account for the variation across runs?
[x] System tests pass (pytest test/system)
[x] Passed code style checking (./style-check.sh)
[ ] You have considered writing a test
[x] Updated major/minor version in sockeye/__init__.py. Major version bump if this is a backwards incompatible change.
[x] Updated CHANGELOG.md

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

This seems ready to merge.


Add citation recommendations that include citing the BioCLIP paper

Also, we'll want a Citation section in the README (such as at the end) that asks that users not only cite this code but also the BioCLIP paper, I think. But I can make that a separate follow-up issue.
Originally posted by @hlapp in https://github.com/Imageomics/pybioclip/pull/3#pullrequestreview-1969536022

My understanding this requires 3 changes:

Archive the repo in Zenodo to create a DOI
Create a CITATION.cff file using the DOI
Update readme with the citation details

In hindsight it would have been better to setup Zenodo before creating our first release.
I went into Zenodo and did not see this repo or any Imageomics repos under the list I can add.
Perhaps only Imageomics owners can setup the repo within Zenodo.
@thompsonmj Can you see this repo within Zenodo?

My understanding this requires 3 changes:

Archive the repo in Zenodo to create a DOI
Create a CITATION.cff file using the DOI
Update readme with the citation details

In hindsight it would have been better to setup Zenodo before creating our first release.
I went into Zenodo and did not see this repo or any Imageomics repos under the list I can add. Perhaps only Imageomics owners can setup the repo within Zenodo. @thompsonmj Can you setup this repo within Zenodo?

I can turn it on. Based on my experience with archiving Andromeda on Zenodo, we should just set it up with the release and ask them to import the earlier versions after the record is created.

Fixed by #25


add citation to mobility table

Where did mobility table come from? This should be cited in the code.
https://github.com/swharden/JLJP/blob/b585ab99d78f39960f85b17988374f3445b7dadb/src/Ion.java#L29-L125

I added a comment with the name of the bibliographic source:
[https://github.com/swharden/JLJP/blob/ff32b9ee12d99d94d9cbe1affb8364474ef5cc5f/src/Ion.java#L60-L62]

@dbrogioli the addition ff32b9ee12d99d94d9cbe1affb8364474ef5cc5f looks great, thanks!

Original Papers
Application - Ng and Barry 1995: https://www.sciencedirect.com/science/article/pii/016502709400087W
Review - Barry and Lynch 1991: https://link.springer.com/article/10.1007/BF01870526
Note: The review uses values sourced from Langes Handbook of Chemistry (1985), edited by JA Dean, and Electrolyte Solutions (1968), by Robinson and Stokes.

Thanks for pointing these papers out @saglag!
It's also reassuring to run some of their numbers and see their LJPs are consistent with ours (even though their theoretical values use the Henderson equation). References like this might be a good source for known ion sets / LJPs that can be used to create tests as discussed in #5

Note: The review uses values sourced from Langes Handbook of Chemistry (1985), edited by JA Dean, and Electrolyte Solutions (1968), by Robinson and Stokes.

@saglag it looks like a PDF of this book is available http://fptl.ru/biblioteka/spravo4niki/dean.pdf but I'm having trouble locating these values. You're more familiar with chemistry than I am - am I overlooking something?

It looks like ion mobility can be calculated from equivalent molar conductivity which is TABLE 8.32 of dean.pdf
There are 3 temperatures available to choose from so maybe one day we can add a feature to let the user calculate LJP at different temperatures after all (#2)

@saglag thanks for the tip! That got me the rest of the way there.
Source (PDF)
TABLE 8.32 of Langes Handbook of Chemistry:
http://fptl.ru/biblioteka/spravo4niki/dean.pdf
Calculation
def showMobilityOfIon(name, charge, conductance):
    Av = 6.02e23 # avogadro's number
    F = 1.6e-19 # elementary charge
    mobility = conductance / (Av * pow(F, 2) * abs(charge))
    print("%s mobility: %E" % (name, mobility))

showMobilityOfIon("Ag+", 1, 61.9e-4)
showMobilityOfIon("Cl-", -1, 76.31e-4)
showMobilityOfIon("Ca++", 2, 59.5e-4)
showMobilityOfIon("NH2SO3-", -1, 48.6)

Sample Output
Ag+ mobility: 4.016559E+11
Cl- mobility: 4.951594E+11
Ca++ mobility: 1.930414E+11
NH2SO3- mobility: 3.153551E+15

The algorithm uses the mobilities but also the temperature T, independently. I think that the possibility of selecting the temperature T is useful. For example, a user can take the ion mobilities from a handbook, say at 70°C, and input them manually into JLJP. Then he/she wants also to change the value of T used in the calculations (the term k_BT).
So, I suggest to put an input field for changing the temperature! Together with this, I suggest to clarify that changing T does not account for all the temperature change effects, so the user is aware that he/she has to take care of changing the mobilities according to the temperature.
For the future, having a database of mobilities at various temperatures, which can be expanded easily with contributions from users, would be excellent!

The algorithm uses the mobilities but also the temperature T, independently. I think that the possibility of selecting the temperature T is useful. For example, a user can take the ion mobilities from a handbook, say at 70°C, and input them manually into JLJP. Then he/she wants also to change the value of T used in the calculations (the term k_BT).
So, I suggest to put an input field for changing the temperature! Together with this, I suggest to clarify that changing T does not account for all the temperature change effects, so the user is aware that he/she has to take care of changing the mobilities according to the temperature.

This sounds good! Maybe we could add a temperature box in the GUI with a button next to it that says details which launches a pop-up dialog that explains this.

For the future, having a database of mobilities at various temperatures, which can be expanded easily with contributions from users, would be excellent!

I like this idea too! Having this project open source makes it a lot easier for users to not only add their own mobilities, but also push their changes back to the main project so everyone benefits from them.

Discussion related to adding a temperature option can continue in #2 now that this mobility citation issue is resolved.

Here are some additional mobility tables useful for #10
https://medicalsciences.med.unsw.edu.au/research/research-services/ies/ionicmobilitytables


Fix #787 JSon XStream dataformat support

Fix #787

d60af9a removed the dup reflection registrations in XStreamSupportProcessor. Thx for catching those @jamesnetherton!

In addition to the review comments, is the itest module referenced in the PR workflow? I don't see it.

is the itest module referenced in the PR workflow

Good catch, it is not. And the groovy check was not executed because it was inside <pluginManagement> block. Adding a fix.

a53b54e fixes issues found by @jamesnetherton


STYLE: Modernize code of BaseComponentSE

Declared getter and setter non-virtual
Defaulted default-constructor and destructor (C++11).
Replaced "purposely not implemented" by a ITK_DISALLOW_COPY_AND_ASSIGN call (ITK 5 coding convention)
Made Configuration types independent of TElastix
#include's exactly those ITK header files that are being used

Similar to my previous pull request, https://github.com/SuperElastix/elastix/pull/294 obviously.

looks good!


Add test args to dotnet-test-xunit

cc @victorhurdugaci

:shipit:

But this code is not executed today :) we still use dnx for coreclr

Ok. Well hopefully it prevent future bugs.


CI: Output the details for a clang-tidy run if necessary.

A clang-tidy report is more helpful if actionable :)

@kbieganski for review as one of your PRs was affected by the very not helpful output of clang-tidy.


Pulling in Ryan's contribution

This PR should be merged via merge commit to facilitate the merge back to main.


Review listAllUserPolicies query

As of now, the query does not really scope by organization. it just selects whatever is related to a user.
It is working as a side effect of scoping all other actions by organization. I think we should review (maybe rewrite the query) to not leak informations between organizations.

I guess the link has broken and the correct query is https://github.com/nearform/labs-authorization/blob/master/src/lib/ops/policyOps.js#L269


DuckduckGo bot is going unfiltered

Can you please provide an example of the user agent.

https://developers.whatismybrowser.com/useragents/explore/software_name/duckduckgo-favicons-bot/

Mozilla/5.0 (compatible; DuckDuckGo-Favicons-Bot/1.0; +http://duckduckgo.com)
Mozilla/5.0 (compatible; DuckDuckGo-Favicons-Bot/1.0; http://duckduckgo.com)
Mozilla/5.0 (compatible; DuckDuckGo-Favicons-Bot/1.0; +http://duckduckgo.com)
All three user agents from the link you provided are detected as bots by crawler detect. Any user agent with the word bot is automatically detected.


OCI image types not supported on clusters with enroot < 3.4.1

If you try to start a slurm job on a cluster with enroot < 3.4.1 using an image of the OCI type, you will hit this error:
pyxis: importing docker image ...
slurmstepd: error: pyxis: child 261774 failed with error code: 1
slurmstepd: error: pyxis: failed to import docker image
slurmstepd: error: pyxis: printing contents of log file ...
slurmstepd: error: pyxis:     [INFO] Querying registry for permission grant
slurmstepd: error: pyxis:     [INFO] Authenticating with user: XXXXXXXXX
slurmstepd: error: pyxis:     [INFO] Using credentials from file: XXXXXXXXXX
slurmstepd: error: pyxis:     [INFO] Authentication succeeded
slurmstepd: error: pyxis:     [INFO] Fetching image manifest list
slurmstepd: error: pyxis:     [INFO] Fetching image manifest
slurmstepd: error: pyxis:     [ERROR] URL https://ghcr.io/v2/nvidia/jax/manifests/latest returned error code: 404 Not Found

You can check if the image is an OCI type by running:
docker manifest inspect $image | jq .mediaType
# Returning application/vnd.oci.image.index.v1+json for OCI type
# Returns application/vnd.docker.distribution.manifest.v2+json for docker type

Aside from updating the enroot version on the cluster, we should investigate if we can support both.
FWIW, as a work-around, you can convert the image from OCI type to the docker (schemaversion=2) format. Here's how I was able to do it via the skopeo tool:
docker run -v $HOME/.docker:/root/.docker:ro --rm quay.io/skopeo/stable copy --authfile /root/.docker/config.json --format v2s2 docker://ghcr.io/nvidia/jax:latest docker://my-private-registry/owner/repo/jax:latest

Re-asigning to @yhtang as he already worked on that.

I believe I'm seeing a different side of the same thing while looking at #263 :
curl -s -H 'Authorization: Bearer xxx' https://ghcr.io/v2/nvidia/upstream-pax/manifests/latest
{"errors":[{"code":"MANIFEST_UNKNOWN","message":"OCI index found, but Accept header does not support OCI indexes"}]}

Opened issue https://github.com/NVIDIA/JAX-Toolbox/issues/311 as a solution.

I believe I'm seeing a different side of the same thing while looking at #263 :
curl -s -H 'Authorization: Bearer xxx' https://ghcr.io/v2/nvidia/upstream-pax/manifests/latest
{"errors":[{"code":"MANIFEST_UNKNOWN","message":"OCI index found, but Accept header does not support OCI indexes"}]}

This could be addressed by adding -H 'Accept: application/vnd.oci.image.index.v1+json, application/vnd.oci.image.manifest.v1+json, application/vnd.docker.distribution.manifest.v2+json'  to the REST request.

Yes, together with https://github.com/NVIDIA/JAX-Toolbox/pull/321.
Also, the issue is actually already documented in our landing page README:


HBASE-27129 Add a config that allows us to configure region-level sto…

…rage policies

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

No hurry :)

To align with what we have in HStore, I think we also need to add a StoragePolicy config in TableDescriptor?

For this question, i have tested, we can set table like this:
 alter 'usertable', CONFIGURATION => {'hbase.hregion.block.storage.policy' => 'ALL_SSD'}
Currently CF-level Storage Policy can be set in CF, for example:
create 'table',{NAME=>'f1',STORAGE_POLICY=>'ALL_SSD'}
If we wanted to add a StoragePolicy config in TableDescriptor, it would look like this:
create 't1', 'f1', REGION_STORAGE_POLICY=>'ALL_SSD', SPLITS_FILE => 'splits.txt', OWNER => 'johndoe'
We can see that this option is on par with SPLITS, OWNER, etc. My personal opinion is that it's not so important, a configuration support is enough, and it maybe too heavy if we extract it in isolation.
What do you think? @Apache9

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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


Add map preview

Another proposal: I think it would be cool if there would be a possibility to display a map preview so the user would be able to see the actual route of the trip.
Not sure though if there would be too much elements after implementing it, so this issue is for the discussion.
I'd be happy to implement it though, I think that this can be slightly useful.

Yes, I also had this idea, it would be great. With mapbox API + the data in DB we can display a preview of the map with the route and maybe the pins of the spots.
For the visuals, I suggests the following specs:

mobile first: it should render well and be useful for mobile users (non-obtrusive, scroll should still be natural)
it's a side information, the main action is the form => probably put the map under the form. Plus don't display anything (not even an empty map until a selection is made in the form.

If you want you can do a POC if you want, go ahead!

@NoryDev I agree with your point, will try to implement it after making another PR on that repo


New Issue Templates

As per earlier discussion @MikhailZex, I have drafted a feature request template, to deprecate using #867.
Please provide any feedback. Feel free to commit to the issue-template-updates branch

@MikhailZex requesting urgent review. The new config prevents users from opening an issue without using a template.
Draft Feature Request template also included in this PR.

You can still open an issue

Yeah github only takes the config file from the master branch. Once the PR is merged then you won't be able to make template-less issues

@MikhailZex requesting urgent review. The new config prevents users from opening an issue without using a template.
Draft Feature Request template also included in this PR.

Ok. Are you trying to enforce templates or allow template-less issues?

Enforce templates.


Notification ping sound when navigating to unread messages

Describe the bug
I have sync set to manual. I can pull down to sync and get 5 new emails for example and the phone makes a ping or new mail sound, which is all good. When I press next message I get another ping sound and so get five ping sounds as I navigate through my messages.
To Reproduce
Steps to reproduce the behaviour:

Configure IMAP e-mail account to manual sync (on demand(
Pull e-mail list down to refresh from sever (notification ping sound)
Tap an unread message (notification ping sound)
Tap forward/back to another unread message (notification ping sound)

Expected behaviour
I would expect just the one ping when new messages land, not as I read every message
Environment:

K-9 Mail version: 5.800
Android version: 11
Device: Nokia 8.3 5G
Account type: IMAP

Additional context
This is not a big issue, but gets a bit much when navigating quickly through a number of new messages

Interestingly, I am now getting just two pings: one for new messages, second when viewing first message


Initialize lookup-request variables locally before request-instance recycle

Motivation
As lookup (PartitionMetadata/Lookup-topic) requests being processed async: Lookup-request instance gets recycled immediately after main-io thread completes its process and triggers async-processing of request in a different thread. So, we need to copy request-variables locally for processing-thread before instance gets recycled.
Modifications
Initialize lookup-request variable locally before Lookup-request instance gets recycled.
Result
It returns lookup-response with correct response-value.

CLA is valid!

CLA is valid!

CLA is valid!

Addressed the changes.


Support a Publish variant of the request client

Some engineers want to be able to publish requests, to avoid having to know an endpoint address. While a loosely coupled directory would be a better approach to this, well, it worked in v2 and many came to use it. So...
Add a PublishRequestClient, that publishes the request.

@phatboyg I would like to help with this but not sure how to get started. I got the project cloned on my desktop and is compiling. I have been using masstransit for the last two years and decided is time to step up and contribute.


[Event Request] Codeunit 5882 - OnAfterOnRun

Hey guys,
it looks like the event OnAfterOnRun() is not called in the OnRun() Trigger.
Build: 16.0.11037.
Thanks!

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Installing it on a server

Are there an instructions to install the program not locally but to host it on a domain. I checked the documentation and it only gives the instructions to install it locally and not publicly. Does anybody know how to do it?

Please help..... Someone should help out please.. How to i install in on a domain ?...

@vitorfs can you look over it please?

@bill0alt You can use Heroku to deploy this without too much work. There is a "Deploy to Heroku" button in the README that you can use. I had to use these docs to get that button working for me.
Note: I had to bump the python version in runtime.txt to python-3.6.15 to meet Heroku's minimum version support. I've opened a PR for this fix and confirmed a working deployment on Heroku as of writing this comment.
Otherwise, you could consider adding Docker support. There is an open PR from 2018 to do exactly that, but it is likely obsolete.


[Event Request] Table 37 OnAfterAssignItemUOM

Please add the additional Parameter CurrentFieldNo to OnAfterAssignItemUOM:
old:
LOCAL [IntegrationEvent] OnAfterAssignItemUOM(VAR SalesLine : Record "Sales Line";Item : Record Item)
new:
LOCAL [IntegrationEvent] OnAfterAssignItemUOM(VAR SalesLine : Record "Sales Line";Item : Record Item;CurrentFieldNo : Integer)

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Gadgetron tests fail but Travis stays green

Travis shows that all builds are green for the Superbuild (e.g., most recent build).
However, if you check one of the OSX builds (e.g., this one), you'll notice:
3: The following tests FAILED:
3: 	  1 - test_all (Failed)
3: Errors while running CTest
3/3 Test #3: Gadgetron_TESTS ..................***Failed   20.27 sec

These tests are also failing on SIRF, but they are actually showing up as having failed (e.g., link).
The reason they should be red is that they are failing the Gagetron unit tests (added in PR https://github.com/CCPPETMR/SIRF-SuperBuild/pull/182). This is a problem to be addressed elsewhere, but Travis should be flagging up the fact that it fails.

This has started happening again. Most recent error that should be causing it to be red happened during the cmake of SIRF:
CMake Error at /usr/local/Cellar/cmake/3.11.4/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:137 (message):

  Could NOT find FFTW3 (missing: FFTW3F_LIBRARY FFTW3_INCLUDE_DIR)

Call Stack (most recent call first):

  /usr/local/Cellar/cmake/3.11.4/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:378 (_FPHSA_FAILURE_MESSAGE)

  /Users/travis/build/CCPPETMR/SIRF-SuperBuild/INSTALL/lib/cmake/ISMRMRD/FindFFTW3.cmake:114 (find_package_handle_standard_args)

  src/xGadgetron/CMakeLists.txt:36 (find_package)

-- Configuring incomplete, errors occurred!

See also "/Users/travis/build/CCPPETMR/SIRF-SuperBuild/builds/SIRF/build/CMakeFiles/CMakeOutput.log".

make[2]: *** [builds/SIRF/stamp/SIRF-configure] Error 1

make[1]: *** [CMakeFiles/SIRF.dir/all] Error 2

make[1]: *** Waiting for unfinished jobs....

on what OS?

both unfortunately...


The status endpoint in chef-server should return the version of the server installed.

Currently the chef-server status endpoint (https://<IP_ADDRESS>/_status on the dev-env) returns the following json:
{"status":"pong","upstreams":{"chef_elasticsearch":"pong","chef_sql":"pong","oc_chef_authz":"pong"},"keygen":{"keys":10,"max":10,"max_workers":2,"cur_max_workers":2,"inflight":0,"avail_workers":2,"start_size":0},"indexing":{"mode":"batch"}}
It would be helpful to Include the version of chef-server installed as a part of this json.
Currently version can be extracted from:
root@api:~# cat /opt/opscode/version-manifest.txt
chef-server 14.0.67+20201111171939

or "build_version" from its json counterpart:  /opt/opscode/version-manifest.json
Acceptance criteria:
The status endpoint returns the version of chef-server installed.

Out of curiosity, does _status have support for any kind of security, like an access control list? From time to time we get security reports concerned with nginx/openresty returning it's version in some end point as leaking too much information.

That is a great point. I think there is still value in shipping this since it has been asked for by some customers in the past. As per a suggestion from @tas50 we can make it configurable to avoid making it a security issue for those who would not like to display this information. Issue tracked at #2214

That is a great point. I think there is still value in shipping this since it has been asked for by some customers in the past. As per a suggestion from @tas50 we can make it configurable to avoid making it a security issue for those who would not like to display this information. Issue tracked at #2214


Option "execute in file dir" ignored when use play button "debug python file in terminal"

Environment data

VS Code version: 1.61.0
Extension version: 2021.10.1317843341
OS and version: 10.0.19043.1237
Python version: 3.8.8 Anaconda
Type of virtual environment used: conda
Value of the python.languageServer setting: default

Expected behaviour
When debugging python file in terminal, it should use the option to "execute the file in the file's directory, instead of the current open folder" (setting "python.terminal.executeInFileDir": true)
It is ok when choose "run python file in terminal". It should do the same when debugging.

Actual behaviour
"Debug python file in terminal" (with the same "play button" used to "run python file in terminal") ignores the setting "python.terminal.executeInFileDir": true

Steps to reproduce:
Try to "debug python file in the terminal" with the same "play button" used to "run python file in terminal".
It leads to error specially when leading with local files in debugging, which worked fine when running.
See bellow running and debugging the same file, in the same folder.

@Diogo-Rossi As a work around you can add debug configuration to launch json:
        {
            "name": "Python: Debug in file dir",
            "type": "python",
            "request": "launch",
            "program": "${file}",
            "console": "integratedTerminal",
            "cwd": "${fileDirname}",
            "purpose": ["debug-in-terminal"]
        }

@Diogo-Rossi As a work around you can add debug configuration to launch json:
        {
            "name": "Python: Debug in file dir",
            "type": "python",
            "request": "launch",
            "program": "${file}",
            "console": "integratedTerminal",
            "cwd": "${fileDirname}",
            "purpose": ["debug-in-terminal"]
        }

I had tried everything that I could find via Google to get this to work. I was about to write that it didn't work for me, but I realized that there was the additional "purpose" line. I added that and it now seems to be working - my print(os.getcwd()) is for the file's directory now when I do debug.


ci: fix the format of release assets

Close https://github.com/cocogitto/cocogitto/issues/346

https://github.com/actions/download-artifact#download-all-artifacts
https://github.com/cocogitto/cocogitto/blob/31a5efda761d0e1c6e92af61f2df13ddff9a4790/.github/workflows/Deploy.yaml#L20-L23
https://github.com/cocogitto/cocogitto/blob/31a5efda761d0e1c6e92af61f2df13ddff9a4790/.github/workflows/Deploy.yaml#L69-L79
https://github.com/cocogitto/cocogitto/blob/31a5efda761d0e1c6e92af61f2df13ddff9a4790/.github/workflows/Deploy.yaml#L88-L90
The artifacts are downloaded as the following.
~/artifacts/
  <artifact name>/<content file name>
  LICENSE/LICENSE
  x86_64-unknown-linux-musl/cog
  ...


Update render-prop.tsx

Based on https://github.com/chakra-ui/ark/issues/2355

@vladstudio
This is correct for 2.x but not for 3.x
We will release 3.x this week so I'm going to close this PR. anyway thanks :)


How to actually run this thing

Description
Hello I am really new to all of this and I am able to get the image classification example and the facial detection running with the Coral Camera, however I am trying to mimic the commands to get any other example running but I dont understand the command to do so.  These commands arent listed on the readme so I am just assuming its either edgetpu_detect or edgetpu_classify as their are not any other variable names that I can see on my system as of now.

Also the README states to use this model mobilenet_ssd_v2_coco_quant_postprocess_edgetpu.tflite, coco_labels.txt but the only model I can git clone from their test_data page (https://github.com/google-coral/test_data) is ssd_mobilenet_v2 .... is this an error or am I (probably) just totally misunderstanding what this is? With my limited understanding of CV and Linux I am thinking I can mimic this command edgetpu_classify
--model ${DEMO_FILES}/mobilenet_v2_1.0_224_quant_edgetpu.tflite
--labels ${DEMO_FILES}/imagenet_labels.txt
and replace the --model with ones I downloaded from the test_example page
sudo wget -P ${DEMO_FILES}/ https://github.com/google-coral/test_data/blob/master/coco_labels.txt and
sudo wget -P ${DEMO_FILES}/ https://github.com/google-coral/test_data/blob/master/ssd_mobilenet_v2_coco_quant_postprocess_edgetpu.tflite
This seemed to not work so at this point I am just at a loss as to how to get this working with other examples Please help
Click to expand!
Issue Type
Support
Operating System
Mendel Linux
Coral Device
No response
Other Devices
No response
Programming Language
Python 3.7
Relevant Log Output
Traceback (most recent call last):
  File "/usr/bin/edgetpu_detect", line 11, in <module>
    load_entry_point('edgetpuvision==7.0', 'console_scripts', 'edgetpu_detect')()
  File "/usr/lib/python3/dist-packages/edgetpuvision/detect.py", line 193, in main
    run_app(add_render_gen_args, render_gen)
  File "/usr/lib/python3/dist-packages/edgetpuvision/apps.py", line 70, in run_app
    display=args.displaymode):
  File "/usr/lib/python3/dist-packages/edgetpuvision/gstreamer.py", line 241, in run_gen
    inference_size = render_overlay_gen.send(None)  # Initialize.
  File "/usr/lib/python3/dist-packages/edgetpuvision/detect.py", line 128, in render_gen
    interpreters, titles = utils.make_interpreters(args.model)
  File "/usr/lib/python3/dist-packages/edgetpuvision/utils.py", line 52, in make_interpreters
    interpreter = edgetpu.make_interpreter(model_path)
  File "/usr/lib/python3/dist-packages/pycoral/utils/edgetpu.py", line 93, in make_interpreter
    model_path=model_path_or_content, experimental_delegates=delegates)
  File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 351, in __init__
    experimental_preserve_all_tensors))
ValueError: Model provided has model identifier '

<', should be 'TFL3'

The link you are trying to download the model is not correct. Please try the below link:
wget https://github.com/google-coral/test_data/raw/master/ssd_mobilenet_v2_coco_quant_postprocess_edgetpu.tflite

Awesome thank you for such a quick response! In the meantime I got the Posenet working, that is really fun and easy to implement.
By the speed and simplicity of your answer I assume that I am correct to use 'edgetpu_detect' --model etc etc like in the picture above? I will give it a try here again in a minute, just waiting for a mount to finish 3d printing

That worked! Thank you very much, overlay seems to blink out when over 20 ish objects are detected and boy howdy does it detect a lot of objects. No idea what these objects are but still a fun little toy to play with


incorrect metrics when maximized on win11

seems the controls / titlebar are too close to the top edge of the monitor when maximized. this is on win11, i'm not sure if this is also how it looks on win10.

on my system, it looks right when requested_client_rect->top is adjusted by +frame_y+padding rather than just +padding. maybe this has changed since windows 10.


Use the keyids and threshold set by delegating roles to verify delegated metadata

Fixes issue #:
Addresses https://github.com/theupdateframework/tuf/issues/660, https://github.com/theupdateframework/tuf/pull/590, https://github.com/theupdateframework/tuf/issues/589, and https://github.com/theupdateframework/tuf/issues/658.
Description of the changes being introduced by the pull request:
This pull request verifies the signature(s) in targets metadata by using the keyids and threshold set by the delegating role (or in the case of the top-level targets role, the keyids and threshold specified in the root metadata file).
Note: The unit tests in https://github.com/theupdateframework/tuf/pull/590 (WIP) should be merged with this fix to verify the expected behavior.
Please verify and check that the pull request fulfills the following
requirements:

[ ] The code follows the Code Style Guidelines
[ ] Tests have been added for the bug fix or new feature
[ ] Docs have been added for the bug fix or new feature

Signed-off-by: Vladimir Diaz<EMAIL_ADDRESS>

Due to imminent refactor efforts this code is unlikely to merge.


Routing over Path Groups

This PR addresses #86, i.e. support for routing incoming messages (NetMessage) over groups of actors based on a routing policy.
Added Functionality
Consider a system where the following three actors are registered:

tcp::<IP_ADDRESS>:1234/parent/child1
tcp::<IP_ADDRESS>:1234/parent/child2
tcp::<IP_ADDRESS>:1234/parent/child1/grandchild

Let's call the tcp::<IP_ADDRESS>:1234/parent the routing path.
Explicit Routing
You can use KompactSystem::set_routing_policy(...) to assign a routing policy to the routing path. Routing policies describe how to distribute a message over a member set. The member set is inferred from the path tree of registered aliases. Since routing path is a prefix of all three actors, they are all considered part of the member set of the routing policy.
Provided routing policies (in kompact::routing::groups) are:

BroadcastRouting which delivers the message to all children (via cloning or serialising, if necessary)
RoundRobinRouting which delivers the message to the next child in order (as determined with reasonable accuracy via an atomic index)
FieldHashBucketRouting (with some specialisations) which delivers the message to a child determined by the hash of a field of the message (usually the sender field).

Implicit Routing
The desire for a message to be routed can also be inferred implicitly from the destination path. In this mode the policy can not be selected, but instead a default policy for either of the options (broadcast and select) are applied.
Broadcast Routing
Sending to the path tcp::<IP_ADDRESS>:1234/parent/* is equivalent to setting the BroadcastRouting policy on the routing path and sending there.
Similarly tcp::<IP_ADDRESS>:1234/parent/child1/*sends to actor 3.
Select Routing
Sending to the path tcp::<IP_ADDRESS>:1234/parent/? is equivalent to setting the SenderDefaultHashBucketRouting policy on the routing path and sending there.
Again tcp::<IP_ADDRESS>:1234/parent/child1/?sends to actor 3, since that is the only option.
Breaking Changes
There were a few breaking changes needed to make this implementation happen:

Serialisers must now implement TryClone, as cloning the serialiser is sometimes necessary. Since most are stateless, they can fulfil this requirement by simply deriving Clone.
Named actor paths are now added correctly into the store, which may cause some runtime issues for users of path hierarchies. This is technically a bug fix, though, as paths were always meant to be added split by / and not as a single blob.
ActorLookup/ActorStore has a new API, but I don't expect any external issues with that.

Other Changes

Serialisable may override the cloned method to avoid the broadcast policy having to serialise an otherwise local and cloneable structure.
The same goes for Serialiser::try_clone_data.
To preserve my sanity while testing, I added a few convenience methods for constructing named actor paths to SystemPath and NamedPath. In particular you can now use something like path / "new-child" / '*' to extend a named path.

Status

[x] Implementation
[x] Tests
[x] Docs

https://github.com/kompics/kompact/pull/99/commits/3bde3f01f8a0a30e7d5ae500adf53ec812b21c79 gives about a 2x performance improvement in path lookups and actor store cleanup operation, in case anyone was wondering...

Codecov Report

Merging #99 into master will increase coverage by 0.40%.
The diff coverage is 64.86%.

@@            Coverage Diff             @@
##           master      #99      +/-   ##
==========================================
+ Coverage   65.98%   66.38%   +0.40%
==========================================
  Files          47       56       +9
  Lines        8707     9922    +1215
  Branches     1131     1387     +256
==========================================
+ Hits         5745     6587     +842
- Misses       2123     2253     +130
- Partials      839     1082     +243

Impacted Files
Coverage Δ

core/src/component/actual_component.rs
66.19% <ø> (ø)

core/src/component/context.rs
75.67% <ø> (ø)

core/src/component/system_handle.rs
76.92% <ø> (ø)

core/src/lib.rs
57.82% <ø> (ø)

core/src/messaging/framing.rs
71.48% <0.00%> (ø)

core/src/messaging/mod.rs
9.09% <0.00%> (-49.43%)
:arrow_down:

core/src/serialisation/core.rs
36.76% <0.00%> (-9.54%)
:arrow_down:

core/src/serialisation/mod.rs
72.72% <0.00%> (-4.70%)
:arrow_down:

core/src/serialisation/protobuf_serialisers.rs
0.00% <0.00%> (ø)

core/src/serialisation/serde_serialisers.rs
61.74% <0.00%> (-0.21%)
:arrow_down:

... and 33 more

Continue to review full report at Codecov.

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

Looks good!


failed to run custom build command for glib-sys v0.10.1

error: failed to run custom build command for glib-sys v0.10.1
--- stderr
"pkg-config" "--libs" "--cflags" "glib-2.0" "glib-2.0 >= 2.44" did not exit successfully: exit code: 1
--- stderr
Package glib-2.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing glib-2.0.pc'   to the PKG_CONFIG_PATH environment variable   No package 'glib-2.0' found   Package glib-2.0 was not found in the pkg-config search path.   Perhaps you should add the directory containing glib-2.0.pc'
to the PKG_CONFIG_PATH environment variable
No package 'glib-2.0' found

I hate to be a pedant, but would you mind please giving more information about your OS, etc.
We do have an issue template because it helps us understand exactly the scope of the issue.

I hate to be a pedant, but would you mind please giving more information about your OS, etc.
We do have an issue template because it helps us understand exactly the scope of the issue.

thank you, I solve it:
sudo add-apt-repository universe
do i have to install tauri-bundler ?
it's not in  the doc .

tauri-bundler is now a library and is managed via the CLI - you don't have to install it alone anymore.

@nothingismagick
Just installed all from  tauri.studio/en/docs/getting-started/setup-linux
and tried https://github.com/tauri-apps/vue-cli-plugin-tauri/
The same issue...
error: failed to run custom build command for glib-sys v0.10.1``
rustc 1.53.0 (53cb7b09b 2021-06-17)
fedora 34 xfce
tauri-bundler   0.9.4

Your system is VERY out of date @makorne. Please update Rust and tauri-bundler (and i am assuming all of your other tauri deps). Please visit our discord for more information about how to do this.

I updated to the latest stable rust (from  a VERY old one, 1 month older :)
Now I have stable-x86_64-unknown-linux-gnu updated - rustc 1.54.0 (a178d0322 2021-07-26)
and did cargo update, cargo install tauri-bundler --force
But still the same tauri-bundler version and same issue.
Looks like  tauri.studio/en/docs/getting-started/setup-linux with
rustc --version
latest update on 2019-12-19, rust version 1.40.0

should be updated and needs the right info about installation.
Ok, I will try discord.
But the right info on setup page would be better for all users.

The problem is not the setup page (although 1.40 could actually be too old idk), but rather the instructions in the vue-cli-plugin-tauri readme or the plugin itself. Both are somewhat outdated.

you don't need tauri-bundler anymore => uninstall it straight away, just in case
if the plugin doesn't work without it (don't know how vue plugins work, but tauri-bundler is still mentioned in the generator file) i'd suggest to not use the plugin at all for now.

@nklayman - can you take a look at your vue-cli-plugin documentation again and make sure its beta compatible?


Batch Feeless Verification Transactions

Description
This PR builds off of the back-end work in this PR and batches transactions to the extent possible when submitting to Komenci. At this point, it is primarily happening in two places:

the approve + request transactions that occur for each attestation request
the withdraw + transfer transactions that occur during escrow redemption

Other changes
N/A
Tested
Yes
Related issues

Part of #6102
Fixes #6214

Backwards compatibility
Yes

We need PR #6178 to be completed in order to properly test transaction batching

@tarikbellamine is this blocked by something? If yes, how can we help to unblock it?

@tarikbellamine is this blocked by something? If yes, how can we help to unblock it?

Hi @tarikbellamine  I have verified this issue using latest Android Internal Build V 1.10.0(1004294335) & Test Flight Build V1.10.0(45) & observed following observations.

[ ] User get "Verification Error" popup with skip for now button when user try to paste last code by tapping on "Resend Last Message" button
[ ] Also we have observed this issue on Test flight build.
Verified on Devices: Samsung Galaxy A5(7.0), iPhone 12(14.0)
Attachment:
VerificationErrorWhilePestingLastCode.mp4
LogsForAndroid
LogsFoiiOS
Let me know if anything need to test.
Thanks..!!


[Java, C#, C++] Fix precedence checks to account for non-contiguous versions.

Relates to issue #988.
An SBE message might not change in every version of a schema. For example, another message might change.
Previously, the field precedence checking model would expect an exact match for actingVersion in wrap to enter one of its initial states. However, it is only aware of the versions in which a message schema has changed. Therefore, it was possible for actingVersion not to match any of these versions, in which case the initial state that represented a codec wrapped around the latest known version of the format was picked.
Now, we do not expect an exact match in wrap. Instead, we select the "best" match. For example, if a codec was changed in v1 and v3, and the acting version is v2, we will decode using v1. However, if the acting version is v4, we would decode as v3.

@ZachBray Looks but the C# tests fail.

@ZachBray
Error Message:
   Test method Org.SbeTool.Sbe.Tests.FieldAccessOrderCheckTests.AllowsOldDecoderToSkipAddedPrimitiveFieldBeforeGroup threw exception:
Microsoft.VisualStudio.TestPlatform.TestHost.DebugAssertException: Method Debug.Fail failed with '
', and was translated to Microsoft.VisualStudio.TestPlatform.TestHost.DebugAssertException to avoid terminating the process hosting the test.
  Stack Trace:
      at Org.SbeTool.Sbe.Tests.FieldAccessOrderCheckTests.ModifyHeaderToLookLikeVersion1() in /home/runner/work/simple-binary-encoding/simple-binary-encoding/csharp/sbe-tests/FieldAccessOrderCheckTests.cs:line 3197
   at Org.SbeTool.Sbe.Tests.FieldAccessOrderCheckTests.AllowsOldDecoderToSkipAddedPrimitiveFieldBeforeG


GetPhysLong() and SetPhysLong() support

Currently this library does not support physical address access methods that WinIO supported.
That's interest functions I think should be support.

Code implemented but not yet tested.