Added ability to set a custom routing key per message

As discussed in #51, it is an extremely common requirement to set a routing key of a message based on, for example it's content. The current implementation sets the routing key to the QueueName.
This PR proposes an abstraction in the generic of the IAsyncCollector implementation which enables common meta data related to the message body to be expressed, in this case the RoutingKey.
This is an optional property, and is only used if it is explicitly defined, else normal operation resumes.

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

Sorry to chase on this, is it possible to make this adjustment? While I understand this is a API change, I can't imagine many developers could use this library without a meta object, or a way to configure additional details pertaining to and around the message?

@creyke apologies for the delayed response. We're reviewing the open PRs that have gone stale (not your fault) in the repo.
Is this still relevant? Do you know if there's a specific reason why the SDK doesn't expose that? (sorry, haven't looked at the details, just assuming it would be needed there as well, unless it's provided as part of a method call).

Hi @fabiocav, thanks for picking this up.
I believe this has not been exposed yet due to the most basic of use cases not requiring it.
Anyone using topic exchanges will require control over the routing key.
If this can come in I'm confident many more customers can move over to this library, and it will not overly complicate the use cases for users which do not need to define it.


Add M1 Max to tested GPUs

@artyom-beilis I'd like to lightly ask, if you don't mind, if there's a status update on this PR. I was hoping the README could acknowledge built-in support for Apple GPUs, as this library could be of interest to other Mac users. From our discussions in #13, it seems you aren't currently able to readily test Apple GPUs, and might not be able to integrate it into your CI. Thus, you might want to restrict the README to GPUs that you can readily test. If that's a concern, I wouldn't mind testing recent commits on my computer, to ensure the Apple GPU is still supported.

Yes you are right. Updated.
CI is very problematic on GPUs. In any case I can't test them all on each updatde. I ususlly check on one nVidia, one AMD and Intel GPU before update - since they all in one PC.
At some point I may upgrade to a PC that supports more than 2 PCI-E slots to handle an additional GPU.

A good thing to note is Apple GPUs are integrated, not discrete. I’m not sure you were aware of this fact. This means you can’t plug in an Apple GPU to a PC; you must own an M1 Mac to test it. But if you ever want something resembling CI tests for Apple silicon, you can count on me :) Just send a ping over GitHub.


Made changes in website content

Added emojis to make it a bit interactive! Let me know any more changes or additions needed.

@all-contributors add @namruthahari for content


Can't make it to work

Describe the bug
I'm using only this and starlightBlog plugin, but the img cant seem to be zoomable
It actualy creates a little non-interactive button

To Reproduce
plugins: [
  starlightBlog(),
  starlightImageZoom(),
],

the line 30 is the code from this img (it occours with every img at my blog)

Expected behavior
The plugin work
How often does this bug happen?
Every time
System Info
"dependencies": {
"@astrojs/check": "^0.9.4",
"@astrojs/starlight": "^0.29.2",
"astro": "^4.16.14",
"sharp": "^0.32.5",
"starlight-blog": "^0.15.0",
"starlight-image-zoom": "^0.9.0",
"typescript": "^5.4.5"
}
Additional Context
No response

Thanks a lot for your report.
Based on your reproduction code, it looks like you're using 2 plugins: starlight-blog and starlight-image-zoom. The 2 plugins use component overrides and they both happen to override the same component (<MarkdownContent>) which is indicated by a warning message in the console.
As there is no obvious way to resolve this conflict, you manually have to compose your own override that combines both plugins as documented here. Here is how you can do it:

Specify an override in your astro.config.mjs file for the <MarkdownContent> component:

// astro.config.mjs
import { defineConfig } from 'astro/config';
import starlight from '@astrojs/starlight';

export default defineConfig({
  integrations: [
    starlight({
      title: 'My Docs',
      plugins: [starlightImageZoom(), starlightBlog()],
      components: {
        // Override the default `MarkdownContent` component.
        MarkdownContent: './src/components/MarkdownContent.astro',
      },
    }),
  ],
});

Create an Astro component to use as the override in src/components/MarkdownContent.astro:

---
// src/components/MarkdownContent.astro
import type { Props } from '@astrojs/starlight/props';
import StarlightBlog from 'starlight-blog/overrides/MarkdownContent.astro';
import StarlightImageZoom from 'starlight-image-zoom/components/ImageZoom.astro';
---

<StarlightImageZoom />
<StarlightBlog {...Astro.props}><slot /></StarlightBlog>

This custom override will render both the ImageZoom component from starlight-image-zoom and the MarkdownContent component override from starlight-blog.


Fix JSDocs for Feather

Fixes various Feather JSDocs issues and cleans up some spacing

There is a conflicting file.
Also i have yet to test it locally, but there is sometimes an issue of when defining ///@function that they will show up as a suggestion even outside the specific camera object. Ie the move function will be suggested even when not next to a stanncam.
If that isn't an issue here though, then perfect.

Fixed the conflicts.
I haven't noticed the issue you're describing, but when I type mov, it's trying to suggest __moving from the stanncam struct. Which it shouldn't. Seems like a bug with Feather.

Fixed the other conflicts that were created with the LTS change.


VOTE: who let the dogs out?

This is a react vote issue. Please vote on the question below, using thumbs up for yes and thumbs down for no. Other reactions will not be counted.
Additional guidance: here's some extra info for you
QUESTION: who let the dogs out?

i did


Question: why mutable hashmap for xgboost 4j

Why do you choose to use a mutable and not a "normal" immutable hash map for xgboost 4j's example code for the scala API?

no special reason, feel free to revise that in a PR


update @terrestris/base-util to 0.1.0

Nice one, merging.. :pineapple:

Pull Request Test Coverage Report for Build 4

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 81.509%

Totals

Change from base Build 3:
0.0%

Covered Lines:
372

Relevant Lines:
439

💛  - Coveralls


[DatePicker] Fix layout when used with border-box

[ ] PR has tests / docs demo, and is linted.
[x] Commit and PR titles begin with [ComponentName], and are in imperative form: "[Component] Fix leaky abstraction".
[x] Description explains the issue / use-case resolved, and auto-closes the related issue(s) (http://tr.im/vFqem).

DatePicker would display incorrectly when used with box-sizing: border-box as described in #4422.
Also remove an unnecessary Clearfix.
Also remove unnecessary assignment of prepareStyles (arguably these could go right into the style prop like in every other component).
Also add some props to the destructure in DateDisplay to prevent them being passed down.
Closes #4259.

We're finally upgraded to 0.15 and ran into this problem as well. We have a global box-sizing set to border-box and most things look reasonably OK but the header for DatePicker was weird and it took me awhile to track down what the problem was.

So I'm 👍 on finding a solution here if the end result is that this renders cleanly with my preferred box-sizing specified. :)

@simensen - this is a PR. This issue has already been documented in #4422.

Oops, looks like should have had a closer look at this PR 😬 :


Update http4s-client, http4s-core, ... to 0.23.7

Updates

org.http4s:http4s-client
org.http4s:http4s-core
org.http4s:http4s-dsl

from 0.23.0-RC1 to 0.23.7.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.http4s" } ]

labels: library-update, early-semver-minor, semver-spec-pre-release, commit-count:1

Superseded by #533.


Zoom out to bring the overlay to certain top

Hi
Just need an idea to how this can be acheived. I have two overlays.

{ overlay.bounds.y -> 0.2567,page.y->50px}
{ overlay.bounds.y -> 0.8567,page.y->150px}

i want to bring the second overlay to document top of 100px and keep the first overlay at the same top of 50px by zoom out . I tried to do with viewport.fitBounds and viewport.pixelFromPoint, but it's not perfectly coming. Do you have any idea..
Thanks
Ganesh

I'm not quite sure I understand. You want to move the overlay? Or you want to zoom/pan the viewer?

Yes..iangilman.. I want to move the overlay by zoom/pan the viewer.
I have 2 overlays in a viewer.
$("#Container").find("overlay=1st").position().top->-50px
$("#Container").find("overlay=2nd").position().top->-150px
I want to keep the first overlay still at the top of 50px and but second one top should be 100px by doing zoom/pan.
Finally...
$("#Container").find("overlay=1st").position().top->-50px
$("#Container").find("overlay=2nd").position().top->-150px
Hope you clear now..
Thanks
Ganesh

Probably the easiest is to do viewport.fitBounds() on the overlay's bounds in viewport coordinates, which you should have from when you created the overlay. Can you show me how you create the overlays?


add form for DOIs

something like https://unpaywall.org/products/simple-query-tool

this is actually done except for, separately

#30
#29
#45
#76
#77


Reorganize move-native

It is getting pretty unwieldy and I'm starting to get frustrated finding the routines I'm looking for. Some things to change:

move every module to its own file
extract all the vector code to its own module, called by both rt and std
don't call from the rt module into std - instead have both of them call into a lower-level module

Remove #![allow(unused)].

Hopefully this will address the code around "// fixme this is pretty awkward - this is intended to be a no-std crate". We're either going to be no_std or not.  Also, I think the panic handler needs to be factored out so that move-native can be linked into different scenarios without colliding with std. Otherwise the handler may be doubly defined at link time (I'm guessing this is the unresolved issue you alluded to in the original comment of #128.

Hopefully this will address the code around // fixme this is pretty awkward - this is intended to be a no-std crate. We're either going to be no_std or not

This comment is a bit misleading as std is only linked in when running move-native's own tests. This is not an uncommon arrangement to be no_std in production, but link to std in tests. Still I am thinking of deleting the drop bomb code as it is pretty confusing. It was helpful during initial testing.

Also, I think the panic handler needs to be factored out so that move-native can be linked into different scenarios without colliding with std. Otherwise the handler may be doubly defined at link time (I'm guessing this is the unresolved issue you alluded to in the original comment of #128)

I believe there were other linkage problems. Dealing with the panic handler is something I would have known how to do.
In what other scenarios does move-native need to link to std? At the moment the panic handler is only configured when targeting solana. If we decide the solana target should use std and/or solana_program we will need to delete or rework the panic handler and global allocator.

Hopefully this will address the code around // fixme this is pretty awkward - this is intended to be a no-std crate. We're either going to be no_std or not

This comment is a bit misleading as std is only linked in when running move-native's own tests. This is not an uncommon arrangement to be no_std in production, but link to std in tests.

Fair enough-- but it does seem awkward-- even if "everyone is doing it", and even if it is conditional.

Still I am thinking of deleting the drop bomb code as it is pretty confusing. It was helpful during initial testing.

Seems reasonable.
One similar guard-rail feature that I would still find useful today (would have saved me twice) is storing "magic numbers" in each of the descriptors (MoveType, MoveUntypedVector, and so forth). This way, if the compiler happens to (say) pass a bad descriptor to the runtime, it would likely be discovered easily (and earlier) instead of mostly processing things and returning bad results that are difficult to track down. Since we'll be processing almost solely financial applications, it does make me a bit nervous.

Also, I think the panic handler needs to be factored out so that move-native can be linked into different scenarios without colliding with std. Otherwise the handler may be doubly defined at link time (I'm guessing this is the unresolved issue you alluded to in the original comment of #128)

I believe there were other linkage problems. Dealing with the panic handler is something I would have known how to do.
In what other scenarios does move-native need to link to std? At the moment the panic handler is only configured when targeting solana. If we decide the solana target should use std and/or solana_program we will need to delete or rework the panic handler and global allocator.

That was the scenario I was thinking of. I'm sure there are others I could dream up, but like you say, let's burn the bridge when we get there.


Schema to Zod question

Are you considering adding the ability to add error messages to the schema to zod package? That prevents me right now from using it in my GraphQL server as I want much better error messages returned than the default Zod ones, which it doesn't seem like I can do currently. So I end up functionally just repeating the schema in my code, only with custom error messages.

Sure, I will work on it.
Such cases won't be a big deal to implement:
const name = z.string({
  required_error: "Name is required",
  invalid_type_error: "Name must be a string",
});

and:
z.string().min(5, { message: "Must be 5 or more characters long" });
z.string().max(5, { message: "Must be 5 or fewer characters long" });
z.string().length(5, { message: "Must be exactly 5 characters long" });

If you need something additional, like addIssue in refine or in superRefine let me know. I'd like to postpone more advanced validation things.

Closed accidently

Error messages are ready, here are the docs.
I updated Zod and added some new methods that appeared recently, such as datetime and ip for string, finite and safe for numbers.

@romeerez are we not considering unique a validator? Doesn't seem like it currently accepts a message. Useful for emails, for example.

Here is how I propose to catch unique errors: https://orchid-orm.netlify.app/guide/query-builder-error-handling.html#database-error
And I think it's not a good idea to have it in the validation.
Because what if the username/email is unique in one moment of time, but in the next moment when you perform the insert query it's already taken and need to handle a uniqueness error? So we have to wrap it into a transaction. And in my vision validation should be completely decoupled from a db, so validation happens in the controller (or it can be called somehow else) on the initial phase of the request, and db inserting happens in a different layer after all data was already validated. So in such a case, you would have to keep a single transaction open during various layers of code execution.


Trouble running NOAA OISST and World Ocean Atlas tutorial recipes

Hi, apologies for this long post, particularly as it's probably something very simple I'm doing wrong, but I'm having trouble running any of the pangeo-forge tutorial recipes I've found for converting netcdf to zarr.
I'm using python 3.7.10, the latest (as of April 20th) master branch of pangeo-forge, and xarray==0.17.0, zarr==2.7.0.
For the OISST recipe,

I don't think this one is important, but just for completeness, the output of recipe.inputs_for_chunk(all_chunks[-1]) is not the same as in the tutorial - rather than the full input URLs, I get a tuple of (I guess) IDs of the inputs.
Also don't think this one is important, but again, for completeness, I don't get the UninitializedTargetError when I try recipe.open_chunk(all_chunks[0]) (because open_chunk returns a GeneratorContextManager, so I guess it's not trying to open the chunk since it's not in a with context).

Same for Step 6, I had to do
with recipe.open_chunk(all_chunks[0]) as ds_chunk:     print(ds_chunk)  to see the expected output.

Then, the first real problem comes when I try to prepare the target:

>>> recipe.prepare_target()
Traceback (most recent call last):
  File "/Users/nbarlow/anaconda3/envs/pangeo-transfer-env/lib/python3.7/site-packages/pangeo_forge/recipe.py", line 266, in _prepare_target
    ds = self.open_target()
  File "/Users/nbarlow/anaconda3/envs/pangeo-transfer-env/lib/python3.7/site-packages/pangeo_forge/recipe.py", line 476, in open_target
    return xr.open_zarr(target_mapper)
  File "/Users/nbarlow/anaconda3/envs/pangeo-transfer-env/lib/python3.7/site-packages/xarray/backends/zarr.py", line 679, in open_zarr
    use_cftime=use_cftime,
  File "/Users/nbarlow/anaconda3/envs/pangeo-transfer-env/lib/python3.7/site-packages/xarray/backends/api.py", line 554, in open_dataset
    store = opener(filename_or_obj, **extra_kwargs, **backend_kwargs)
  File "/Users/nbarlow/anaconda3/envs/pangeo-transfer-env/lib/python3.7/site-packages/xarray/backends/zarr.py", line 324, in open_group
    zarr_group = zarr.open_group(store, **open_kwargs)
  File "/Users/nbarlow/anaconda3/envs/pangeo-transfer-env/lib/python3.7/site-packages/zarr/hierarchy.py", line 1166, in open_group
    raise GroupNotFoundError(path)
zarr.errors.GroupNotFoundError: group not found at path ''

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/nbarlow/anaconda3/envs/pangeo-transfer-env/lib/python3.7/site-packages/pangeo_forge/recipe.py", line 313, in _prepare_target
    ds.to_zarr(target_mapper, mode="a", compute=False, safe_chunks=False)
TypeError: to_zarr() got an unexpected keyword argument 'safe_chunks'

I don't know what to make of the "GroupNotFoundError", but I did look at the xarray Dataset.to_zarr method and didn't see a "safe_chunks" argument.  Is this a new/upcoming feature?
Next, I had a go at the NOAA World Ocean Atlas recipe.

If I go all the way through, and do flow.run(), the first 23 tasks (presumably caching the inputs?) succeed, but then I get the same error as above, with "GroupNotFoundError", and the "safe_chunks" unexpected keyword argument.
If I try to do the first chunk by hand I get:

>>> all_chunks = list(recipe.iter_chunks())
>>> recipe.prepare_target()
>>> recipe.store_chunk(all_chunks[0])
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/nbarlow/anaconda3/envs/pangeo-transfer-env/lib/python3.7/site-packages/pangeo_forge/recipe.py", line 359, in _store_chunk
    zarr_array = zgroup[vname]
  File "/Users/nbarlow/anaconda3/envs/pangeo-transfer-env/lib/python3.7/site-packages/zarr/hierarchy.py", line 349, in __getitem__
    raise KeyError(item)
KeyError: 'time'
>>> recipe.prepare_target()
>>> recipe.store_chunk(all_chunks[0])
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/nbarlow/anaconda3/envs/pangeo-transfer-env/lib/python3.7/site-packages/pangeo_forge/recipe.py", line 359, in _store_chunk
    zarr_array = zgroup[vname]
  File "/Users/nbarlow/anaconda3/envs/pangeo-transfer-env/lib/python3.7/site-packages/zarr/hierarchy.py", line 349, in __getitem__
    raise KeyError(item)
KeyError: 'time'

which is a bit strange to me, as if I do
>>> with recipe.open_chunk(all_chunks[0]) as ds_chunk:
>>>      print(ds_chunk.variables)

I do see "time" listed.
Apologies again if all this is just me missing something obvious, but any help in debugging this would be very welcome (and I'd be happy to contribute (at the very least a recipe) to pangeo-forge once I gain some more understanding!)

hi @nbarlowATI , I had many of the same issues when I tried the OISST recipe (see, for example, my comment on issue#51 and Ryan's helpful reply here.
To get past the safe_chunks problem, I resorted to editing recipe.py as explained here
I was going to try updating the OISST recipe/tutorial, but only got as far as introducing a CMIP6 tutorial instead. Sorry about that, I know how frustrating this is!  It is fantastic that the code base is advancing so quickly, but it makes it difficult to keep the tutorials current.

Many thanks for the super fast reply @naomi-henderson !
As you suggest, just commenting out the "safe_chunks" argument in recipe.py does fix this! :)
I'll try now with the mamba environment instead.
I'm happy to look into updating the tutorials (though if that xarray PR is going to be merged soon it might be better to wait for that rather than write instructions on installing that branch).
Thanks again! :)


issues with CMake dependency handling

Hey all,
I'm trying to build OI on arch and run into a lot of trouble.

the rocksdb version you reference doesn't support libstdc++ from gcc 13, giving compile errors due to missing cstdint includes
you hardcode LLVM 15, but I have LLVM 16
you have a mixed bag of system libs, and FetchContent, and  git submodules. Why is that? I'm all for system libs, unless you need to have a very specific version of your thirdparty libs - is that the case? If so, would you be opposed to using submodules everywhere? The big advantage there is that we can more easily patch things, and also share the downloaded code across multiple build folders (think debug vs. release)
your msgpack CMake hackery doesn't work anymore with msgpack-cxx 5.0.0

I have workarounded all of these issues locally now, and would like to clean things up a bit upstream. But for that I would need to know what your constraints are.
My suggestion would be:

replace FetchContent with git submodules
then update rocksdb to a newer versions that works with newer compilers.
alternatively (additionally?) we could use find_package for more dependencies. all of the following are covered by system packages on arch:

tomlplusplus
glog
rocksdb

support newer msgpack-cxx and only if that's not found fallback to the existing cmake hackery.

Would you be OK with patches going in direction?

OK, LLVM15 is available on my system after all, so updating that isn't that important for now after all.  I'll go through the bits you mentioned then say what I think will be the best solutions.

* the rocksdb version you reference doesn't support libstdc++ from gcc 13, giving compile errors due to missing cstdint includes

We can (and should) update this. We run at the head of RocksDB internally, so should always be compatible. I've updated it.

* you hardcode LLVM 15, but I have LLVM 16

Yeah, this is a pain. As you say in the follow up it almost always requires code changes to support a different version of LLVM. It's not impossible though, as https://github.com/iovisor/bpftrace/ manages it. We'll have a chat and see if we can devote a bit more effort to supporting more than one version. The downside is the one we're not using would be poorly tested, but this code rarely breaks so it should be okay. As you say later, a lot of distros package multiple versions of the LLVM libs, but this still isn't ideal.

* you have a mixed bag of system libs, and FetchContent, and  git submodules. Why is that? I'm all for system libs, unless you need to have a very specific version of your thirdparty libs - is that the case? If so, would you be opposed to using submodules everywhere? The big advantage there is that we can more easily patch things, and also share the downloaded code across multiple build folders (think debug vs. release)

I can explain some of the thought process behind this, though I've lost a little with time. We used to have several submodules but switched all but extern/drgn to FetchContent. drgn stayed in extern because we have our own fork for the foreseeable future and used to make changes to it regularly, so the ease of patching was more important than uniformity.
There's also the rocksdb build chaos. Not entirely sure why it invokes CMake separately but trying to swap it to a normal build failed due to flags for me. This should be fixed at some point.
Everything that one can expect to find on all distros has been left as a system dependency.
My view of the way forward here is to add FIND_PACKAGE_ARGS where appropriate to the FetchContent_Declare calls. This lets you use system deps if you have them, and fall back to a download/compile if you don't. It seems like the best of both worlds to me.
@ajor @ttreyer feel free to chime in on this bit.

* your msgpack CMake hackery doesn't work anymore with msgpack-cxx 5.0.0

I think changing msgpack to FetchContent would sort this. We can require a newer version of the system lib and if that fails to be found pull and compile a new version from source.

I have workarounded all of these issues locally now, and would like to clean things up a bit upstream. But for that I would need to know what your constraints are.
My suggestion would be:
* replace FetchContent with git submodules

I think we would still tend toward FetchContent over submodules, mainly due to the better integration with find_package (admittedly we haven't taken advantage of that yet). Again, appreciate the input of @ttreyer and @ajor here.

* then update rocksdb to a newer versions that works with newer compilers.

Done. Thanks for pointing this out! I put it on the latest tagged version which should work.

* alternatively (additionally?) we could use `find_package` for more dependencies. all of the following are covered by system packages on arch:

  * tomlplusplus
  * glog
  * rocksdb

I think adding FIND_PACKAGE_ARGS to tomlplusplus and glog FetchContents will achieve this, while keeping the backup of pulling from the web. rocksdb would be a bit more complicated because the build is awful and needs fixing first.

* support newer msgpack-cxx and only if that's not found fallback to the existing cmake hackery.

Mentioned above.

Would you be OK with patches going in direction?

Yeah! I appreciate the discussion first, but we should definitely move in the direction of easier builds for external contributors. Thanks for your patience and initiative to start working on it. As an aside, I've been working on a Nix flake to make this easier for people to get started with. Including FIND_PACKAGE_ARGS on the FetchContent is a great move for that too.


Eigenpy not found at configuration time

Hello,
I am installing pinocchio from source in order to use the devel branch. I installed Eigenpy as indicated here : https://github.com/stack-of-tasks/eigenpy but when running cmake for pinocchio I get the following error :
-- eigenpy >= 1.5.0 is required. -- Checking for module 'eigenpy>=1.5.0' --   No package 'eigenpy' found CMake Error at /home/vpadois/.local/lib/python2.7/site-packages/cmake/data/share/cmake-3.12/Modules/FindPkgConfig.cmake:436 (message):   A required package was not found Call Stack (most recent call first):   /home/vpadois/.local/lib/python2.7/site-packages/cmake/data/share/cmake-3.12/Modules/FindPkgConfig.cmake:602 (_pkg_check_modules_internal)   cmake/pkg-config.cmake:311 (PKG_CHECK_MODULES)   cmake/pkg-config.cmake:570 (ADD_DEPENDENCY)   bindings/python/CMakeLists.txt:48 (ADD_COMPILE_DEPENDENCY)
Should I just tell cmake to ignore Eignepy or is there something smarter to do ?
Thanks in advance for your help.
Best
Vincent

Hello Vincent,
It seems that the detection of eigenpy by  pkgconfig fails. Can you check

that executable pkg-config is installed (and accessible by your PATH). Simply type
pkg-config --version in the terminal in which you run make,
that eigenpy is installed and that eigenpy.pc is in a directory listed in PKG_CONFIG_PATH ?
pkg-config --modversion eigenpy should return something

Hello Florent,
Thank you for your help. This is what I get :

1. that executable `pkg-config` is installed (and accessible by your `PATH`). Simply type
   `pkg-config --version` in the terminal in which you run `make`,

vpadois@ychoux:~/Documents/Softs/pinocchio/build$ pkg-config --version 0.29.1

2. that eigenpy is installed and that `eigenpy.pc` is in a directory listed in `PKG_CONFIG_PATH` ?
   `pkg-config --modversion eigenpy` should return something

vpadois@ychoux:~/Documents/Softs/pinocchio/build$ pkg-config --modversion eigenpy Package eigenpy was not found in the pkg-config search path. Perhaps you should add the directory containing eigenpy.pc'
to the PKG_CONFIG_PATH environment variable
No package 'eigenpy' found`
So there is clearly a PATH problem for eigenpy

It is rather a PKG_CONFIG_PATH. When you install several packages that depend on one another from source, you should define a few environment variables to detect the files installed in non-standard directories.
For instance, if you install in a prefix called PREFIX, you should add

${PREFIX}/lib/pkgconfig in your PKG_CONFIG_PATH,
${PREFIX}/lib in your LD_LIBRARY_PATH
${PREFIX}/bin in your PATH,
${PREFIX}/lib/pythonx.y/site-packages:${PREFIX}/lib/pythonx.y/dist-packages in your PYTHONPATH.
${PREFIX} in your CMAKE_PREFIX_PATH.

I understand that well but the point is that I did not use a specific PREFIX (I did not install eigenpy from source but using the proposed bionic package) so I did not expect that I would have some environment variable to define. Does this make sense or am I missing something ?

Unfortunately, binary packages from third party sources are not installed in standard directories:

robotpkg installs in /opt/openrobots,
ros installs in /opt/ros/melodic (for ros-melodic packages).
Therefore, you still need to set environment variables.

Ok. I will do that. Thank for your help.

By the way, @vpadois you can set BUILD_PYTHON_INTERFACE to OFF when compile Pinocchio.

OK. Will do. Thx


Primary keys are cast instead of relying on serialization

The javascript multi views for dashboard choosers are inconsistent with handling of primary keys.  In some places they cast to int and others they rely on serialization.
For example, the images.views.multiple.add view uses both approaches in the same view.  It would be best to let Django handle serialization to avoid edge cases.
Similar to https://github.com/wagtail/wagtail/issues/6509 - I am happy to fix these today if you approve the issue.  Looks like there are two spots where this happens - document and image multiple add view.
There is already a field in the tests that can be used for testing on the custom image and custom document tests

Addressed in #8985 so that we don't end up version-bumping this yet again (sorry for the lack of response!). It looks like fully supporting non-integer IDs on image models will require much more widespread changes (e.g. to URL routes), and I'm not clear on what the use case of this is - but if you're still interested in pursuing this, we're happy to look at any follow-up PRs.


add Repeat type and use in patterns cmd enum

related to https://github.com/KittyCAD/engine/issues/2132

closing in favor of https://github.com/KittyCAD/engine/issues/2168


Sound not working.

I'm sorry to keep posting issues every time I need help, but I have no other way to contact you. I'm trying to follow the wiki pages but, I need an example to actually learn well. I was trying out sound and background music for my game, but It just showed the loading screen and when I clicked to enter the game, it closed the window. I don't know what is wrong. Also, how do I add a collider to an image with box2d? I am trying to make a platformer style combat game.

Oh, I am really sorry, I forgot to update wiki for Sounds and Music. That ", true" when trying to load sound is not present in engine. Updating wiki page for it.

And, collider to image? Simply draw image with position and rotation of Box2D body, something like this:
// JavaScript
body = network.body(.....);
......
graphics.draw(sometexture, body.getPosition().x, body.getPosition().y, body.getAngle());

Okay thanks, ur a lifesaver. Is there any other way I can contact you like e-mail or something? I some of my questions aren't issues, just help that I need.

You can mail me at<EMAIL_ADDRESS>


<IP_ADDRESS> fails to install on Windows - PEP 517

Expected behaviour
Install successfully.
Collecting opencv-python==<IP_ADDRESS>
  Using cached opencv_python-<IP_ADDRESS>-cp38-cp38-win_amd64.whl (33.5 MB)
Requirement already satisfied: numpy>=1.17.3 in c:\programdata\anaconda3\lib\site-packages (from opencv-python==<IP_ADDRESS>) (1.18.5)
Installing collected packages: opencv-python
Successfully installed opencv-python-<IP_ADDRESS>

Actual behaviour
Install fails with following output:
Collecting opencv-python
  Using cached opencv-python-<IP_ADDRESS>.tar.gz (88.9 MB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
    Preparing wheel metadata ... done
Requirement already satisfied: numpy>=1.17.3 in c:\programdata\anaconda3\lib\site-packages (from opencv-python) (1.18.5)
Building wheels for collected packages: opencv-python
  Building wheel for opencv-python (PEP 517) ... error
  ERROR: Command errored out with exit status 1:
   command: 'c:\programdata\anaconda3\python.exe' 'c:\programdata\anaconda3\lib\site-packages\pip\_vendor\pep517\_in_process.py' build_wheel 'C:\Users\TOM~1.THO\AppData\Local\Temp\tmpdgirsxmm'
       cwd: C:\Users\tom.thornton\AppData\Local\Temp\pip-install-hy3yx6x4\opencv-python
  Complete output (153 lines):
  Not searching for unused variables given on the command line.
  CMake Error: CMake was unable to find a build program corresponding to "Ninja".  CMAKE_MAKE_PROGRAM is not set.  You probably need to select a different build tool.
  -- Configuring incomplete, errors occurred!
  See also "C:/Users/tom.thornton/AppData/Local/Temp/pip-install-hy3yx6x4/opencv-python/_cmake_test_compile/build/CMakeFiles/CMakeOutput.log".
  Not searching for unused variables given on the command line.
  CMake Error at CMakeLists.txt:2 (PROJECT):
    Generator

      Visual Studio 15 2017 Win64

    could not find any instance of Visual Studio.

  -- Configuring incomplete, errors occurred!
  See also "C:/Users/tom.thornton/AppData/Local/Temp/pip-install-hy3yx6x4/opencv-python/_cmake_test_compile/build/CMakeFiles/CMakeOutput.log".
  Not searching for unused variables given on the command line.
  -- The C compiler identification is unknown
  CMake Error at CMakeLists.txt:3 (ENABLE_LANGUAGE):
    The CMAKE_C_COMPILER:

      cl

    is not a full path and was not found in the PATH.

    To use the NMake generator with Visual C++, cmake must be run from a shell
    that can use the compiler cl from the command line.  This environment is
    unable to invoke the cl compiler.  To fix this problem, run cmake from the
    Visual Studio Command Prompt (vcvarsall.bat).

    Tell CMake where to find the compiler by setting either the environment
    variable "CC" or the CMake cache entry CMAKE_C_COMPILER to the full path to
    the compiler, or to the compiler name if it is in the PATH.

  -- Configuring incomplete, errors occurred!
  See also "C:/Users/tom.thornton/AppData/Local/Temp/pip-install-hy3yx6x4/opencv-python/_cmake_test_compile/build/CMakeFiles/CMakeOutput.log".
  See also "C:/Users/tom.thornton/AppData/Local/Temp/pip-install-hy3yx6x4/opencv-python/_cmake_test_compile/build/CMakeFiles/CMakeError.log".
  Not searching for unused variables given on the command line.
  -- The C compiler identification is unknown
  CMake Error at CMakeLists.txt:3 (ENABLE_LANGUAGE):
    The CMAKE_C_COMPILER:

      cl

    is not a full path and was not found in the PATH.

    To use the JOM generator with Visual C++, cmake must be run from a shell
    that can use the compiler cl from the command line.  This environment is
    unable to invoke the cl compiler.  To fix this problem, run cmake from the
    Visual Studio Command Prompt (vcvarsall.bat).

    Tell CMake where to find the compiler by setting either the environment
    variable "CC" or the CMake cache entry CMAKE_C_COMPILER to the full path to
    the compiler, or to the compiler name if it is in the PATH.

  -- Configuring incomplete, errors occurred!
  See also "C:/Users/tom.thornton/AppData/Local/Temp/pip-install-hy3yx6x4/opencv-python/_cmake_test_compile/build/CMakeFiles/CMakeOutput.log".
  See also "C:/Users/tom.thornton/AppData/Local/Temp/pip-install-hy3yx6x4/opencv-python/_cmake_test_compile/build/CMakeFiles/CMakeError.log".

  --------------------------------------------------------------------------------
  -- Trying "Ninja (Visual Studio 15 2017 Win64 v141)" generator
  --------------------------------
  ---------------------------
  ----------------------
  -----------------
  ------------
  -------
  --
  --
  -------
  ------------
  -----------------
  ----------------------
  ---------------------------
  --------------------------------
  -- Trying "Ninja (Visual Studio 15 2017 Win64 v141)" generator - failure
  --------------------------------------------------------------------------------

  --------------------------------------------------------------------------------
  -- Trying "Visual Studio 15 2017 Win64 v141" generator
  --------------------------------
  ---------------------------
  ----------------------
  -----------------
  ------------
  -------
  --
  --
  -------
  ------------
  -----------------
  ----------------------
  ---------------------------
  --------------------------------
  -- Trying "Visual Studio 15 2017 Win64 v141" generator - failure
  --------------------------------------------------------------------------------

  --------------------------------------------------------------------------------
  -- Trying "NMake Makefiles (Visual Studio 15 2017 Win64 v141)" generator
  --------------------------------
  ---------------------------
  ----------------------
  -----------------
  ------------
  -------
  --
  --
  -------
  ------------
  -----------------
  ----------------------
  ---------------------------
  --------------------------------
  -- Trying "NMake Makefiles (Visual Studio 15 2017 Win64 v141)" generator - failure
  --------------------------------------------------------------------------------

  --------------------------------------------------------------------------------
  -- Trying "NMake Makefiles JOM (Visual Studio 15 2017 Win64 v141)" generator
  --------------------------------
  ---------------------------
  ----------------------
  -----------------
  ------------
  -------
  --
  --
  -------
  ------------
  -----------------
  ----------------------
  ---------------------------
  --------------------------------
  -- Trying "NMake Makefiles JOM (Visual Studio 15 2017 Win64 v141)" generator - failure
  --------------------------------------------------------------------------------

  ********************************************************************************
  scikit-build could not get a working generator for your system. Aborting build.

  Building windows wheels for Python 3.8 requires Microsoft Visual Studio 2017.
  Get it with "Visual Studio 2017":

    https://visualstudio.microsoft.com/vs/

  ********************************************************************************
  ----------------------------------------
  ERROR: Failed building wheel for opencv-python
Failed to build opencv-python
ERROR: Could not build wheels for opencv-python which use PEP 517 and cannot be installed directly

Steps to reproduce
On windows:
pip install opencv-python

Temporary Workaround
Install previous version
pip install opencv-python==<IP_ADDRESS>

The builds are in progress... there are almost 200 builds in queue and it will take over 24 hours before all the wheels have been built:

Windows: https://ci.appveyor.com/project/skvark/opencv-python/history
Linux and macOS: https://travis-ci.com/github/skvark/opencv-python/builds

I will write release notes here when all builds have passed successfully: https://github.com/skvark/opencv-python/releases
In the future, please pin your dependencies and use the search tool to find similar issues. The install fails because you have no build tools installed and pip tries to compile from the source distribution which has been already uploaded.


Headers not sticking

I don't know if I'm doing something wrong here but I can't seem to get my header changes to stick.
Here's what I'm doing:
Manager.instance.baseHeaders = mapOf(Pair("Content-Type", "application/json"))
val (request, response, data) = url.httpPost(listOf(Pair("emailAddress", email))).responseString()

However, when I debug the Manager class' request method (around line 57) the request's headers are set to:
"Content-Type" -> "application/x-www-form-urlencoded"
"Accept-Encoding" -> "compress;q=0.5, gzip;q=1.0"

This is using just Fuel (not the android lib) in a Spring Boot app with the Kotlin RC

I dug a little deeper and it looks like the Encoding class is overriding my headers. Looking at this class it seems that ultimately multipart/form-data and application/x-www-form-urlencoded are the only two Content-Type values that end up being used. Is this the desired behavior?

I put those 2 as the sane defaults. I anticipated that it would cover most of the case. It is true that those 2 values should be configurable. I will make some improvements in next coming release.
In the meantime, can you override this at the request level meaning that, you could do
url.httpPost(listOf("Content-Type" to "application/json", "emailAddress" to email).responseString() to override the defaults?

@kittinunf I tried that override but Content-Type needs to be a header not a request parameter, so it didn't work.

Oh I am sorry. I mean you can override it with header function at request level.

@erikthered I addressed this issue in PR #51. Thanks for reporting this.
I have used your use case as a test :yellow_heart:
https://github.com/kittinunf/Fuel/blob/fix-bugs-and-cleanup/fuel/src/test/kotlin/com/github/kittinunf/fuel/BlockingRequestTest.kt#L198-L213

Cool! One other suggestion I would make is to add the request level header function to the readme. I didn't even realize that function was available.

Agree. I'll do it.


Feat: Add scroll to top and scroll to down button

Todo:

[ ] When user scrolls up, show the "Scroll to top" button in bottom right of the screen
[ ] When user scrolls down, show the "Scroll to bottom" button in bottom right of the screen
[ ] If user is at top of the viewport, hide the button
[ ] If user is at bottom of the viewport, show the "Scroll to top" button

Closed in favour of #5


SECURE_CONNECTION flag not working

I was looking at the baseimage docker container and saw that there were flags to enable password protection as well as securing the vnc connection. I enabled the password protection variable which seems to work however setting the SECURE_CONNECTION variable to 1 doesn't seem to do anything. The lock in the top left of the window says Connected (unencrypted)

Setting SECURE_CONNECTION should definitely works.  You can make sure the variable is properly set by running docker inspect <container name>.  If you see that the variable is set, you can make sure to manually type the variable name when creating the container.  Sometime copy-pasting from browser introduce invisible characters.

Upon checking the variable using docker inspect <container name> i see that the SECURE_CONNECTION variable is set to 0 despite me setting it to 1. Could I be doing something wrong?

  Edit the container settings and make sure to remove any definitions of the variable.  The only setting that should be used is Secure Connection (click Show more settings...).

Deleting the duplicated variable definitions did the trick, thanks


CircuitForm is deprecated but CircuitState isn't?

It seems like CircuitForm is deprecated now, but somehow CircuitState is not.
This seems like an oversight, since CircuitState has a CircuitForm field.
@seldridge should CircuitState be deprecated?

We should eventually remove the form: CircuitForm member from CircuitState. This may have to be a 1.5 change to go through a full deprecation cycle.
Immediately, the apply methods for the CircuitState object that include forms: CircuitForm can be deprecated. Because I deprecated CircuitForm, I added an apply method that doesn't use it (so that we can get around deprecation warnings for the time being).
Fully removing CircuitState would mean that the underlying datatype for transforms would have to change. While I think this is fine to consider, I'm not sure it's worth it.

I added an apply method that doesn't use it

I think this is what I was searching for when I created this issue.


add production qadb migration test instructions

@jhoblitt I had the opportunity to test the steps to restore the squash qadb and apply the migrations as part of DM-9354. I would like to suggest the following changes in the documentation. Note that  the makemigrations command should not be needed here,  only the migrate.
Initialize the QA database
Note: this step must be executed if you want a fresh database and load some test data into it. Skip to the next section if you want to restore a copy of the latest production QA database.
vagrant ssh squash

cd /opt/apps/qa-dashboard
. /opt/rh/rh-python35/enable
. venv/bin/activate
cd squash

export DJANGO_SETTINGS_MODULE="squash.settings.production"
python manage.py migrate

export QA_USER="nobody"
export<EMAIL_ADDRESS>python manage.py createsuperuser --username $QA_USER --email $QA_USER_EMAIL --noinput

# the password can be changed after the fact via
python manage.py changepassword $QA_USER

python manage.py loaddata test_data

Restore a copy of the latest production QA database
This step can be used to validate a database migration included in a recent version of SQuaSH prior the production update. Use the following to restore a copy of the latest production database and apply the migrations (if any).
vagrant plugin install vagrant-scp

(
    cd ./terraform;
    ./bin/terraform show | egrep 'RDS_(FQDN|PASSWORD)' | sed 's|\s+*||g'
)
# copy output into cut'n'paste buffer

aws s3 cp s3://jenkins-prod-qadb.lsst.codes-backups/qadb/latest.sql.gz .
vagrant scp latest.sql.gz squash:.

vagrant ssh squash
gzip -d latest.sql.gz
# paste output from tf show
mysql -h "$RDS_FQDN" -u admin -p"$RDS_PASSWORD" qadb < latest.sql

cd /opt/apps/qa-dashboard
. /opt/rh/rh-python35/enable
. venv/bin/activate
cd squash

export DJANGO_SETTINGS_MODULE="squash.settings.production"
python manage.py migrate


inference scipt for custom pose classification model ? for both .tflite a5 hdf5 format

im using window 10
i tried the blog to train pose  model ,but there is no any inference script ,can you guys please provide script
https://github.com/tensorflow/tensorflow/issues/58101

Hi @akashAD98 !
Sorry for the late response.
You can set inference input and output as float32 as a work around.
converter.inference_input_type = tf.float32
converter.inference_output_type = tf.float32

Ref.
Detailed usage can be found here.
Thank you!

is that correct?
converter = tf.lite.TFLiteConverter.from_keras_model(model)
converter.inference_input_type = tf.float32   #
converter.inference_output_type = tf.float32 #

converter.optimizations = [tf.lite.Optimize.DEFAULT]
tflite_model = converter.convert()

print('Model size: %dKB' % (len(tflite_model) / 1024))

with open('pose_classifier.tflite', 'wb') as f:
  f.write(tflite_model)

sure @mohantym

@mohantym its not working, im getting a tracker warning, & no output
python pose_estimation.py --label_file  labels.txt  --model movenet_thunder  --classifier pose_classifierfloat32
#size of converted tflite model is 27kb is this fine? ```
warning  I'm getting
'''WARNING:root:No tracker will be used as tracker can only be enabled for MoveNet MultiPose model.'''
& I'm not using any tracker
default weight which provided my repo is working fine but trained model is not working here

@mohantym i m using the script provided by TF.  I just want to do inference of my trained model, so it s fine if it's not tf.lite weight even .hdf5 \ hf5 is inferencing is fine, but that part is not provided here.
my goal is to do inference of this model .
here is official colab for same
https://colab.research.google.com/github/tensorflow/tensorflow/blob/master/tensorflow/lite/g3doc/tutorials/pose_classification.ipynb

Ok @akashAD98 !
Tracker is a fair warning  which will trigger when mutipose model is not provided.
Got your point on inference with respect to custom pose estimation model though.
On the prediction part, You can use either signature runner/ invoke the interpreter with test image to predict the output.
Ref 1, 2.
Yeah! I also feel sample inference code snippet (with visualization) can be added in documentation.
@sachinprasadhs !
Could you look at this issue.
Thank you!

Hi @akashAD98
The inference for the TFLite model is provided in the evaluate function of the notebook. Similar thing can be done for custom tflite model as well.
def evaluate_model(interpreter, X, y_true):
  """Evaluates the given TFLite model and return its accuracy."""
  input_index = interpreter.get_input_details()[0]["index"]
  output_index = interpreter.get_output_details()[0]["index"]

  # Run predictions on all given poses.
  y_pred = []
  for i in range(len(y_true)):
    # Pre-processing: add batch dimension and convert to float32 to match with
    # the model's input data format.
    test_image = X[i: i + 1].astype('float32')
    interpreter.set_tensor(input_index, test_image)

    # Run inference.
    interpreter.invoke()

    # Post-processing: remove batch dimension and find the class with highest
    # probability.
    output = interpreter.tensor(output_index)
    predicted_label = np.argmax(output()[0])
    y_pred.append(predicted_label)

  # Compare prediction results with ground truth labels to calculate accuracy.
  y_pred = keras.utils.to_categorical(y_pred)
  return accuracy_score(y_true, y_pred)

# Evaluate the accuracy of the converted TFLite model
classifier_interpreter = tf.lite.Interpreter(model_content=tflite_model)
classifier_interpreter.allocate_tensors()
print('Accuracy of TFLite model: %s' %
      evaluate_model(classifier_interpreter, X_test, y_test))

Thanks.


Limited LPPE support for JDBC connections

Closes #2355

This adds support for expired and disabled fields in the query and queryAndEncode database authentication mechanisms. Simulates LPPE with LDAP authentication handlers
Test cases added, documentation updated to reflect new properties
no known side effects

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.John lister seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.

Only Query and QueryAndEncode supported as doesn't seem appropriate with bind. Could be implemented with more work for the Search handler, but as this matches against any matching user, could cause conflicts

hey @johnlister thanks very much again. I realize this pull might still need some work, but I am going to merge and carry on offline.
Once the changes show up in snapshots, etc please review and make other contributions/modifications as you see fit.

Hi, apologies I added the changes you requested, but I've struggled to get the build to run successfully locally. If I follow the instructions it builds fine, but if I use the build commands on travis I get a number of failures - either findBugs or checkStyle. These are in completely unrelated modules.
Clearly my local setup is broken somewhere...
Thanks for picking it up - any questions about the behaviour let me know

All good. Thank you!
I was just chatting with someone on gitter yesterday about this improvement and I think we are going to enhance it further. Thanks for getting the ball rolling.
I am also going to add this improvement to the changelog on the apereo blog.

I totally agree, I put in the basics for what I needed currently, but we have internally been talking about adding allowed time fields, password expiry dates, etc I stopped short of putting those in now as would require more work to generalise the password management side as well. I look forward to seeing what you come up with

Very cool. Going to ping @bbooth here to see if we can come up with a common/shared mechanism to enforce policies.
Blog updated https://apereo.github.io/2017/02/24/rc2-release/#database-password-policy-enforcement

Definitely, it should be straightforward to implement, just kicking myself I can't get the main branch to build locally...

How do you build and what does it tell you?

Using the standard instructions:
gradlew build --parallel -x test -x javadoc -DskipCheckstyle=true -DskipFindbugs=true
works fine, but travis does:
gradlew clean bootRepackage install --parallel -x test --stacktrace
followed by
`gradlew checkstyleTest test --stacktrace --parallel'
It used to fail with checkStyle issues on mongo related modules, but just done it now and the ldap tests are failing - presumably I need a server to connect to?

No. CAS ships with an embedded LDAP server for testing. [That's how Travis passes tests] There are no external setups. You might have something that is preventing the server to start up.
You should also remove all -x test -x javadoc -DskipCheckstyle=true -DskipFindbugs=true prior to shooting a pull request and building. Your build must be consistent with Travis as much as possible. That's how snapshots get build, and if that passes, then we know it's all good.


MATLAB bindings

MATLAB offers two alternatives for interfacing external C-API libs:

MEX
CallLib/LoadLibrary

Using MEX is like using the CPython internal API, but worse in several aspects. CallLib/LoadLibrary is analogous to Python's CFFI -- just like in DSS Python, we can use a tweaked C header in LoadLibrary and it will build a specialized DLL automatically (provided there is a compiler).
That specialized DLL can be redistributed, so end users should not need a C compiler. Just like with CFFI, the main difficulty will be building this. I still have no idea if a DLL built with older MATLABs would work on newer versions and vice-versa. If it doesn't work, distributing binaries the last two or three versions should be enough.
Using LoadLibrary and CallLib as the backend, the rest of the code should be pretty similar to DSS_Python and OpenDSSDirect.py. As soon as I have some free time, it should be a quick task now.
A new repository will be created to host the MATLAB bindings -- DSS_MATLAB? Maybe something else since it could include both a COM-like interface and an interface like OpenDSSDirect.py/.jl.
@kdheepak When you have some time, if you have any specific requirements about this, feel free to let me know.

Great! Thanks for deciding to tackle this!
I like the idea of building dss_matlab to tackle the bindings first and then including a COM-like/odd interface later.
I would prefer we used calllib/loadlibrary, because compiled MATLAB does not work with MEX. I also think if people want to generate the MEX file, they can do so (fairly) easily using swig, given that you already have header files that expose the C-ABI.
One challenge is how to create a test suite like that can be run on something like Travis. Do you know if Octave will work with calllib/loadlibrary? If so, we might be able to run Octave on Travis for testing purposes.

I would prefer we used calllib/loadlibrary, because compiled MATLAB does not work with MEX.

That's good to know.

One challenge is how to create a test suite that can be run on something like Travis. Do you know if Octave will work with calllib/loadlibrary? If so, we might be able to run Octave on Travis for testing purposes.

No, unfortunately Octave doesn't support those yet, they are still listed here: http://hg.savannah.gnu.org/hgweb/octave/file/88e87c69c8b8/scripts/help/unimplemented.m

@kdheepak Just made the repo public:
https://github.com/PMeira/dss_matlab
This is based on calllib. It seems the thunk DLL can be used across different MATLAB versions without issue. Most of the issues I found while porting to MATLAB were limitations on how pointers are handled.
I plan to test on Linux and Mac soon. Currently it reproduces the COM-like interface (I'd say 90% of the code is generated from the DSS Python code), we can add ODDpy-like interface later if there's interest. Most of the API should be covered already, some special cases (like DSSProperty) will need some changes.

One challenge is how to create a test suite that can be run on something like Travis.

I opened an issue about that -- https://github.com/PMeira/dss_matlab/issues/1
Independent of the CI system, I imagine custom workers (if allowed) with MATLAB installed on each platform would be enough.


Output: Add json output

This commit adds a command line flag that enables
outputting pwru events in json format.

Thanks! Could you drop the second commit (git fetch -u origin && git rebase origin/main should do the job instead).

@darox Thanks. The PR got into a funky state (it's undoing some changes in some previous PRs). Could you rebase against the latest main (git fetch -u origin && git rebase origin/main && git push --force-with-lease)?

@darox Thanks. The PR got into a funky state (it's undoing some changes in some previous PRs). Could you rebase against the latest main (git fetch -u origin && git rebase origin/main && git push --force-with-lease)?

I'm sorry. I had a merge conflict then fixed it, which merged main into this branch. Then I reset to my commit and pushed. I now executed your command.

@darox The CI failures look legit. With --backend=kprobe, the file content:
               SKB    CPU          PROCESS                     FUNC
               SKB    CPU          PROCESS                     FUNC
0xffff91a34c09cae8      8 [/usr/bin/curl:230522]             ip_local_out<IP_ADDRESS>:41624-><IP_ADDRESS>:8080(tcp)
0xffff91a34c09cae8      8 [/usr/bin/curl:230522]           __ip_local_out<IP_ADDRESS>:41624-><IP_ADDRESS>:8080(tcp)
0xffff91a34c09cae8      8 [/usr/bin/curl:230522]             nf_hook_slow<IP_ADDRESS>:41624-><IP_ADDRESS>:8080(tcp)
0xffff91a34c09cae8      8 [/usr/bin/curl:230522] kfree_skb_reason(SKB_DROP_REASON_NETFILTER_DROP)<IP_ADDRESS>:41624-><IP_ADDRESS>:8080(tcp)
0xffff91a34c09cae8      8 [/usr/bin/curl:230522]   skb_release_head_state<IP_ADDRESS>:41624-><IP_ADDRESS>:8080(tcp)
0xffff91a34c09cae8      8 [/usr/bin/curl:230522]                tcp_wfree<IP_ADDRESS>:41624-><IP_ADDRESS>:8080(tcp)
0xffff91a34c09cae8      8 [/usr/bin/curl:230522]         skb_release_data<IP_ADDRESS>:41624-><IP_ADDRESS>:8080(tcp)
0xffff91a34c09cae8      8 [/usr/bin/curl:230522]             kfree_skbmem<IP_ADDRESS>:41624-><IP_ADDRESS>:8080(tcp)

There is no space between "kfree_skbmem" and "<IP_ADDRESS>:41624".

@darox The CI failures look legit. With --backend=kprobe, the file content:
               SKB    CPU          PROCESS                     FUNC
               SKB    CPU          PROCESS                     FUNC
0xffff91a34c09cae8      8 [/usr/bin/curl:230522]             ip_local_out<IP_ADDRESS>:41624-><IP_ADDRESS>:8080(tcp)
0xffff91a34c09cae8      8 [/usr/bin/curl:230522]           __ip_local_out<IP_ADDRESS>:41624-><IP_ADDRESS>:8080(tcp)
0xffff91a34c09cae8      8 [/usr/bin/curl:230522]             nf_hook_slow<IP_ADDRESS>:41624-><IP_ADDRESS>:8080(tcp)
0xffff91a34c09cae8      8 [/usr/bin/curl:230522] kfree_skb_reason(SKB_DROP_REASON_NETFILTER_DROP)<IP_ADDRESS>:41624-><IP_ADDRESS>:8080(tcp)
0xffff91a34c09cae8      8 [/usr/bin/curl:230522]   skb_release_head_state<IP_ADDRESS>:41624-><IP_ADDRESS>:8080(tcp)
0xffff91a34c09cae8      8 [/usr/bin/curl:230522]                tcp_wfree<IP_ADDRESS>:41624-><IP_ADDRESS>:8080(tcp)
0xffff91a34c09cae8      8 [/usr/bin/curl:230522]         skb_release_data<IP_ADDRESS>:41624-><IP_ADDRESS>:8080(tcp)
0xffff91a34c09cae8      8 [/usr/bin/curl:230522]             kfree_skbmem<IP_ADDRESS>:41624-><IP_ADDRESS>:8080(tcp)

There is no space between "kfree_skbmem" and "<IP_ADDRESS>:41624".

I will take a look tomorrow.

@brb all checks passed now.


[Question] Remove save file to another device

My question is, how to remove save files to another device with Valkirie app.

In windows, the save files should be located in the directory:
C:\Users\user\AppData\Roaming\Valkyrie\MoM\Save
You can copy them from there to the other device using the same folder structure.

Android:
Device\Valkyrie\MoM\Save

@Plachon please confirm if this answers your question and close this issue if it does

Thank you for a tip.


[TextField]The text cursor can be dragged in windows, which is inconsistent with the native behavior

Video
https://user-images.githubusercontent.com/30982989/176576206-7bf0a739-0a78-431a-a232-2fb30144835a.mp4

Hi @yixiaco, Thanks for filing the issue. This is fixed on beta, You can expect the fix in the upcoming stable release.
closing as duplicate of https://github.com/flutter/flutter/issues/106676


Prepare for Release v0.2.0

Announcing Code Freeze for v0.2.0 Release
Hi all -
Thanks for everyone's contributions to powerlevel9k! We have added some significant new features since the v0.1.0 release tag, and I believe now is a good time to prepare for the v0.2.0 release.
The next branch is now frozen except for bug fixes and documentation improvements. If you aren't already using next, please switch over to help us test!
Thanks so much for contributing to this project! It makes a huge difference.
Contributors to-date for v0.2.0:
@dritter
@labianchin
@jkoelndorfer
@giladgo
@christian-schulze
@tusharsrivastava
@natemccurdy
@dsager

Hi all -
We have received some great bug fixes / improvements to next, and I think we are nearing the release.
I would like to give the README a nice facelift. A part of this will be providing some screenshots of different configurations.
 Thanks!
@dritter
@labianchin
@jkoelndorfer
@giladgo
@christian-schulze
@tusharsrivastava
@natemccurdy
@dsager

@bhilburn why don't we collect these screenshots on a new wiki page? I had this in mind for several weeks now.
Just started this page. Hopefully this is what you had in mind. By having a separate wiki page we motivate others to share their configurations, other users get help and a showcase, and we get some nice screenshots.

@dritter - Actually, yes, I was going to put most of them in a wiki page. Thanks for getting it started! I do want to take a couple of them and feature them at the top of the README, though.

@bhilburn I think besides new screenshots, we need a nice animated gif as many other themes have. That would be a nice-to-have in the readme as well as in the External themes page.

@dritter - I agree, an animated gif would be nice. Any recommendations for good tools to create them?

@bhilburn LICEcap http://www.cockos.com/licecap/

Another option would be ttystudio.
If we want videos instead of animated gifs, we could use asciinema.
For that I think we need a good script to record the best features. IMHO that should be features that most of our users customize, like flexible segments, overriding colors, the flexibility of the vcs segment, etc.

Hey all -
I'm going to update the readme and tag a new release this week. If you haven't already and are up for it, please post your configuration here for our users =)
https://github.com/bhilburn/powerlevel9k/wiki/Show-off-your-configuration!

v0.2.0 has been tagged and released!!
Thanks for your contributions and help, everyone!

Awesome!
The new README looks great! :+1:


Feat @ #26: adds link and icon for discord and substack

Solves #26
Header

Footer

@fernando-RA is this still valid PR?  If so can you fix conflicting files. - I will close after a couple of days if this is no longer valid


[BUG] fix for get_fitted_params in _HeterogenousMetaEstimator

Upstream version of sktime bugfix https://github.com/sktime/sktime/pull/4633

Codecov Report

Merging #191 (9ca751b) into main (83252bc) will decrease coverage by 0.19%.
The diff coverage is 0.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##             main     #191      +/-   ##
==========================================
- Coverage   82.75%   82.56%   -0.19%
==========================================
  Files          43       43
  Lines        2806     2811       +5
==========================================
- Hits         2322     2321       -1
- Misses        484      490       +6

Impacted Files
Coverage Δ

skbase/base/_meta.py
17.80% <0.00%> (-0.42%)
:arrow_down:

... and 1 file with indirect coverage changes


[Help] Can I use the pretrained models for Region Features

@endernewton
Hi I landed here while searching for a pre-trained object detection model , trained on VisualGenome using detectron2.
Can I use the models you have listed and get features from say the FC layers of the box head?
What I need actually is to extract region features of objects as done in most VQA models like Pythia

You can check this PR: https://github.com/facebookresearch/grid-feats-vqa/pull/3


feat: set the primary model

primaryModel defaults to 'model' but can be changed in cases where the model hook must return an array or hash of promises and the user wants to be explicit about the model in the template e.g. user vs model

@knownasilya @bcardarella any chance of getting this PR fixed and merged? I also require this feature.

I'll have a look today.

That's awesome, thanks 👍

I fixed the related test, but there are still failures in other versions of Ember, but not related to my changes, just the setup of the testing in this addon.

Cool, thanks for jumping on this. Hopefully the maintainer will get chance to fix that and merge this in.

Any chance this can be merged?

Just a friendly ping 🐱

We should have a notice up in the README but its not there, this library has been sunset for some time. Whenever we move repos to the DavyJonesLocker org it means we have abandoned it.
In this case, ember-data-route is a pattern to just implement within your own app and not rely on the addon.
Due to the lack of sunset notice, I'll merge this and consider the library fully sunset.

I'll also note that we won't be making any release

@bcardarella ah, yeah that wasn't very obvious, thanks for making it clear!

Note to self, don't delete this branch yet..


Allow to return objects from tab buttons

This PR adds a new feature to tabs which allows the user to return a custom object when the nav button of a tab has been clicked.
This is for use-cases where tabs are being used to render content for a list of objects. It's important to know which object is currently selected to adjust some logic on your blazor page.
I've added a short demo as well.
In my case I need this functionality to show a list of positions. Depending on the selected position I display additional information outside of the Tabs control.
Implementation might not be perfect but it works fine in my case. Feel free to suggest changes.

@gvreddy04 There is one thing left todo here. I've noticed that the property IsShown does not trigger a a tab activation when the property is changed from outside.

To reproduce:
<Tabs>
    @foreach (var customer in customers)
    {
        <Tab IsActive="selectedCustomer == customer" OnTabClicked="async () => await OnTabClickedAsync(customer)"<EMAIL_ADDRESS>            <Content>

                    This is the placeholder content for the<EMAIL_ADDRESS>tab.

            </Content>
        </Tab>
    }
</Tabs>

@if (selectedCustomer is not null)
{

Selected customer<EMAIL_ADDRESS>}

<Button Color="ButtonColor.Success">Add customer</Button>

@code {
    private List<Customer> customers = new()
                                       {
                                           new Customer(1, "Marvin Klein"),
                                           new Customer(2, "Vikram Reddy"),
                                           new Customer(3, "Bandita PA"),
                                           new Customer(4, "Daina JJ")
                                       };

    private Customer? selectedCustomer;

    protected override void OnInitialized()
    {
        selectedCustomer = customers.First();
    }

    private Task AddCustomerAsync()
    {
        var customer = new Customer(5, "Hello World");

        customers.Add(customer);

        selectedCustomer = customer;

        return Task.CompletedTask;
    }

    private Task OnTabClickedAsync(Customer customer)
    {
        selectedCustomer = customer;
        return Task.CompletedTask;
    }
}

Notice how active tab does not change when selectedCustomer changes outside of the tab control. This also applies for all other tabs.

@gvreddy04 did you consider my last comment here?

@MarvinKlein1508 I missed the scenario. I think a few people asked for dynamic tabs. I'll check.

Dynamically adding tabs #480

@MarvinKlein1508  Now dynamic tabs support added.
Demo code: https://github.com/vikramlearning/blazorbootstrap/blob/master/BlazorBootstrap.Demo.RCL/Pages/Tabs/Tabs_Demo_13_Dynamic_Tabs.razor

@gvreddy04 that's still not what I mentioned above.
I have use-cases where I set selectedCustomer for example from outside.
For example:
<Button Color="ButtonColor.Info" Class="mt-3" @onclick="Select2ndCustomer">Select 2nd customer</Button>

@code {
private void Select2ndCustomer() {
selectedCustomer = customers[1];
}
}

What I expect now is tab for customer Vikran Reddy to be shown.
In my use-case this is triggered when running validation for an object within the list. If the validation has failed I want the tab to open automatically so the user can see the error messages on a glance.

See this gif for an example:

BTW. is there any reason for the control to rely on JavaScript in the first place? Wouldn't it be easier to implement it with vanilla HTML and C#?
What I did in previous projects was someting like this:

            @foreach (var pos in Input.Positions)
            {
                <button type="button" role="tab" @onclick="() => SelectedPosition = pos" class="@GetTabNavLinkClass(SelectedPosition == pos)" id="pos-tab-@pos.GetHashCode()"<EMAIL_ADDRESS>@pos.Name</button>
            }

            @foreach (var pos in Input.Positions)
            {
                int posHash = pos.GetHashCode();

Content for tab

            }

public string GetTabNavLinkClass(bool active) => active ? "nav-link active" : "nav-link";
public string GetTabClass(bool active) => active ? "tab-pane fade active show" : "tab-pane fade";

ping @gvreddy04

See this gif for an example:

I understand the scenario. The IsActive property is currently used in the OnInitialized stage, which is why it's not working as expected. For now, please use @ref to reference the tabs and then call the appropriate methods. I'll address this issue in version 1.11.0. However, the caveat is that we cannot use both IsActive and the methods to activate any of the tabs simultaneously.

@gvreddy04 I don't think this is a problem. I think you are either using the activation via tabs or the attribute itself. The attribute might be used more frequently for dynamic tabs though.


chore: Add a note for db/migrate and docker-env

Cc: @dhirajsb

@dhirajsb or @valdar can you merge it? I don't have write access :smile:


Dynamic Addition for Exporters to Zeebe Cluster Containers

This PR has an initial approach to be able to use initContainers to register new Exporters to the official Zeebe Docker Images.
This PR should promote not creating your own Docker Images for adding your custom exporters. It also made me think about removing the ElasticSearch one, as we can clearly document how to add one with initContainers hence having the base image more reusable and not bloated.
An example of how to add hazelcast and kafka can be found here:
https://github.com/zeebe-io/zeebe-helm-profiles/blob/master/examples/zeebe-cluster/exporters-values.yaml

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

Needs approval from an approver in each of these files:

OWNERS

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

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

Needs approval from an approver in each of these files:

OWNERS

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

Generally looks fine for Zeebe pre 0.23.x - but from 0.23.x, injecting exporters becomes a piece of :cake:. Since we can now arbitrarily define exporters using environment variables, injecting exporters is now mostly just copying over the JAR to a pre-defined location and configuring your exporter. Whether we want to keep distributing these containers which contain the JAR + some default config is something to be discussed I guess.

@npepinpe what would you expect to change for 0.23.x forward? I mean.. this is just showing how to do that exactly.. configure + copy the jars.. I consider this more like an example on how to do that. But if you are already working in big changes for how to plug new exporters please let me know so we can reflect that in the charts.

With 0.23.x onwards, adding an exporter is a simple as mounting the fat JAR to the container, and configuring the environment variables such that it's loaded. The only upside of extra containers I can see would be some at best providing some kind of defaults and a simpler way of obtaining the fat JAR.

What is the state of this? @npepinpe @salaboy

@Zelldon I will try to rebase and re-test early next week.

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

Test name
Commit
Details
Rerun command

serverless-jenkins
f50a2573d259165bad1958ceee82066f2bdd128b
link
/test this

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

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

Test name
Commit
Details
Rerun command

serverless-jenkins
5a38b7de6242c48b3fe9747ec2779e4484256bc1
link
/test this

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


Why are triggers and rules under package in manifest.yml?

From the OpenWhisk getting started documentation:

Triggers cannot be created inside a package; they must be created directly under a namespace.

So why are triggers and rules underneath package in manifest.yml?
package:
  actions:
  ...
  triggers:
    ...
  rules:
    ...

Packages are compositional units, they can be composed into other packages (and form applications or services) and provide linkage to larger Orchestration templating, much as what you see in AWS Cloud Formation.

In addition, packages are units of delivery (catalog) and can be versioned, ascribed metadata, etc. as a whole.

I think john's point is that you can't create a trigger or rule inside a package so that's at odds with the principles you just outlined.

@rabbah I see.  Semantically, we have a conflict then since we established Package to mean a collection of Actions; whereas, we were trying to use it for a broader "packaging" of related whisk entities for publishing.  We have discussed using the term "service" or "bundle" (or "application" which was deemed too broad).  Good time to discuss again.

Good question.
I feel like this abstraction should extend to the OpenWhisk project itself. Shouldn't the goal of the wskdeploy tool to mirror the abstractions defined on the OpenWhisk platform?
In a way, these things (rules, feeds, triggers) are all associated if they are defined in the same manifest.yml file. Since they aren't reusable in the OpenWhisk platform itself, whats the advantages of having another layer that OW doesn't understand?
(I haven't been working on OW that long, just throwing out ideas based on what I have learned so far)

wskdeploy assume everything is associated to a package, even though this is not true for triggers in rules.  I did some internal refactoring (I changed the data structure so that triggers and rules are no longer contained in a package struct) because of this issue.  However, this isn't surfaced in the Manifest.  My current thought is that containment in a package is a useful abstraction to provide a default scope when writing out a manifest file.  Basically, can we reduce typing. For example, right now you can write:
package:
  name: MyPackage
  actions:
    greeting:
      inputs:
        name: name
          type: string
 triggers:
      myTrigger
 rules:
    myRule:
      trigger: myTrigger
      action: greeting

In the actual deployment, we deploy MyPackage/greeting, myTrigger, 'myRule.   However, we don't make the developer write out MyPackage/greeting` in the rule definition.  We just assume that any entity that doesn't explicitly state a package is contained in MyPackage.
I believe this still works when we add the dependency key (issue #41).  In this case, we could have a dependent package named YourPackage.  We could use the greeting action declared in YourPackage:
package:
  name: MyPackage
  dependencies:
     YourPackage:
           git: https://somegit
  actions:
    greeting:
      inputs:
        name: name
          type: string
 triggers:
      myTrigger
 rules:
    myRule:
      trigger: myTrigger
      action: greeting
   yourRule:
      trigger: myTrigger
      action: YourPackage/greeting

I don't know how you might reference a trigger in a dependent package in a unique way right now since internally we don't support triggers in packages.  We could just modify the trigger name somehow?

I tend to agree with @jzaccone, wskdeploy should follow the openwhisk terminology, and as such not have triggers under package. This is particularly confusing especially for newcomers.
In my opinion, bundle and module are both valid option.
This extra layer opens the door for having multiple packages under a single "project". This might be desirable or not.

We need to challenge the whisk terminology; package is not a strong concept other than to those that have learned the CLI.  @lionelvillard.  @paulcastro I wish we could have discussed this before making the change.  A "package" construct should exist to describe everything packaged in a filesystem/directory or eventually a zip provided for related entities; which I still contend is universally known as a package (best term).

@paulcastro if you indeed changed the code then the spec. is not incorrect and we lack a substitute construct.

The change I made is only in an internal data structure.  The manifest itself is not changed.

@mrutkows

package is not a strong concept other than to those that have learned the CLI.

Is this true? I was under the impression that the concept of package is core to OpenWhisk:

https://github.com/openwhisk/openwhisk/blob/master/docs/reference.md#openwhisk-entities
https://github.com/openwhisk/openwhisk/blob/master/docs/reference.md#rest-api

Disclaimer: I'm new to the OpenWhisk world, so bear with me.

@lionelvillard Someone made the decision to namespace in this way; we have already seen issues with it going forward.  Conceptually, what constitutes a package can and should be questioned in light of becoming accepted and part of a larger service/packaging ecosystem.

There is a proposal to have triggers/rules inside a package for v2: https://github.com/openwhisk/openwhisk/issues/219#issuecomment-272951007
(thanks Rodric)

@rabbah @lionelvillard Excellent!  As we add more compositions this will become important.

@pritidesai FYI


doc: update hyperlink for submission

Details
When I tried initializing my project, I noticed that the current link to the docs webpage, for submitting to the web   store, doesn't seem to work.  Specifically, the anchor doesn't seem to jump to any specific content on https://docs.plasmo.com/workflows.  I figured the following link is the right one.
https://docs.plasmo.com/workflows/submit
Code of Conduct

[x] I agree to follow this project's Code of Conduct
[x] I checked the current PR for duplication.

Oops, need to fix this for all the examples too xD....


Unit tests

Add unit tests using Jest.

I'm trying to use Jest to test a component that includes calls to react-native-ibeacon functions. I need to mock them out, but it is not clear how to do that. I would be grateful for any advice.

Still no joy. I have posted this question on stack overflow: http://stackoverflow.com/questions/41214265/how-do-i-mock-react-native-ibeacon-in-jest


bgpv2,operator: Fix the race condition in the nodeSelector conflict detection logic

Please see the commit description. The first commit should be backported to the v1.16 branch.
bgpv2,operator: Fix the race condition in the nodeSelector conflict detection logic

/test

Conformance K8s Kind / Installation and Conformance Test: https://github.com/cilium/cilium/issues/35779
Cilium E2E Upgrade: https://github.com/cilium/cilium/issues/35774
Conformance Ginkgo: https://github.com/cilium/cilium/issues/35780


[Popper] Fix scroll jump when content contains autofocus input

closes #16740

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

@alirezamirian It's a great first pull request on Material-UI 👌🏻. Thank you for working on it!


Null crash fix in OpCopyMemory.

I found a crash in OpCopyMemory where it assumed that var wasn't null. This looked like a small oversight as the lines directly above and below do the null check.
I attached a dissassembly file that caused this crash.
TestDissassembly.txt

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.joshua.davis seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Indeed, an oversight. Test coverage on OpCopy* isn't that great. Thanks for the fix.


name playbook

i have a problem,i was follow step by step, i use centos 6.5,but after "python cldstkdeploy.py --install all " it can't continues with folowing message,"cannot import name PlayBook You need to run python cldstkdeploy.py --setup all" i did already, but is not working.
pls help me it's urgent

@zarnst were you able to resolve this ? I'm got into same issue.

sorry but i don’t support this anymore.

On Dec 13, 2017, at 6:48 PM, Zain Mustafa<EMAIL_ADDRESS>wrote:
@zarnst https://github.com/zarnst were you able to resolve this ? I'm got into same issue.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/thehyperadvisor/cldstk-deploy/issues/11#issuecomment-351592553, or mute the thread https://github.com/notifications/unsubscribe-auth/AAouerCWLMuye9DZLUbQ8T2T-i0IUBiDks5tAIxxgaJpZM4JixDH.


ENOENT: no such file or directory

Hello, I have a problem with this action and I cannot figure it out.
Action def:

name: Create release

on:
  push:
    tags:
      - '*'

jobs:
  create_release:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v2
      - name: Test files
        run: ls -l && ls -l ./changelog && echo "v${GITHUB_REF/refs\/tags\//}" && ls -l ./changelog/v${GITHUB_REF/refs\/tags\//}
      - name: Release
        uses: softprops/action-gh-release@v1
        with:
          #  when tag has 'v' in name no need of adding it before ${GITHUB_REF/refs\/tags\//
          body_path: ./changelog/v${GITHUB_REF/refs\/tags\//}/version-summary.md
        env:
          # Cannot use GITHUB_TOKEN because of:
          # https://github.com/orgs/community/discussions/27028
          GITHUB_TOKEN: ${{ secrets.LOGCHANGE_PAT_TOKEN }}

And the logs

No progress :(

I cannot spot a problem :(

I solve it with:
      - name: Set env
        run: echo "RELEASE_BODY_FILE=$(echo $GITHUB_WORKSPACE/changelog/v${GITHUB_REF/refs\/tags\//}/version-summary.md)" >> $GITHUB_ENV
      - name: Release
        uses: softprops/action-gh-release@v1
        with:
          #  when tag has 'v' in name no need of adding it before ${GITHUB_REF/refs\/tags\//
          body_path: ${{ env.RELEASE_BODY_FILE }}


Folder for exam project

Hi!
Will a "template"-folder be created for the exam project in github upon starting the exam (similarly to the folders used for inaugural-, data- and modelproject, with a READ.ME, ipynb and py-file) - or do we have to create one ourselves ahead of the exam?
Kind regards,
Jos, P and Tex

Hi
You should add an exam folder to your existing project on Github yourselves.
Best regards
Asker

Hi,
What should the readme files include wrt. id? Should we list our exam number, names or our studyid?
kind regards,
Anders and Christian

Hi
You can just write your group name (but it's not that important since the other IDs are easy to find
Best regards
Asker


Import-Module .\HybridRegistration.psd1 is not supported on Powershell 7

Step 2 on Manual Install (https://docs.microsoft.com/en-us/azure/automation/automation-windows-hrw-install#step-2---install-the-runbook-environment-and-connect-to-azure-automation)
Import-Module .\HybridRegistration.psd1 is not supported on Powershell 7 (Tested latest version 7.1)
Import command fails with error:
Import-Module: Could not load type 'System.Web.HttpException' from assembly 'System.Web, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'.
Step 3 on Automatic Install (https://docs.microsoft.com/en-us/azure/automation/automation-windows-hrw-install#step-3---run-the-powershell-script)
Same as above, please specify that the script is only supported on PowerShell 5.1.

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

ID: 7b29372c-7bd9-7da2-4cff-9afbb432bccf
Version Independent ID: 66ce101d-d21b-3fdf-be70-7f9cadc1570e
Content: Deploy a Windows Hybrid Runbook Worker in Azure Automation
Content Source: articles/automation/automation-windows-hrw-install.md
Service: automation
Sub-service: process-automation
GitHub Login: @MGoedtel
Microsoft Alias: magoedte

@flarsmar Thanks for your comment! We will review and provide an update as appropriate.

@flarsmar Good catch! 👍 I was also able to reproduce the issue.

I will check with our internal team to understand if there is a current limitation on this feature and if required I will enhance the document as appropriate. Thanks again for the feedback!

@flarsmar - The HybridRegistration script requires POSH WSF 5.1 and the article was wrong to suggest later versions of PowerShell were supported. From what I understand, the System.Web assembly is not supported in PowerShell core. I've updated the article accordingly to reflect this. My apologies for the confusion this has caused. I'm going to close this PR as I believe the issue has been properly addressed. If I did not properly address your feedback, please feel free to respond.  #please-close.

This was true in 2020, and remains technically true, I've found that you can manually register the hybrid worker by importing the "HybridRegistration" module in PowerShell 7.x, using the -UseWindowsPowerShell switch parameter.
This could be applied to New-OnPremiseHybridWorker.ps1, too.


Reexported types are emitted in js files

Reexported types are emitted as actual modules in js files generating runtime errors.
Problem occurs in both commonjs and esmodule.
TypeScript Version:  3.8.3

Search Terms:
Reexported types interfaces dts
Code
// types.d.ts
export type Foo = 1;
export type Bar = 2;
//--------------------------------------
// index.ts
export * from "./types"

export default 1;

tsconfig
{
  "compilerOptions": {
    "target": "es5",
    "module": "commonjs", // or esmodules
    "strict": true,
    "esModuleInterop": true,
    "skipLibCheck": true,
    "forceConsistentCasingInFileNames": true
  }
}

Expected behavior:
Don't emit types reexports
Actual behavior:
commonjs
"use strict";
var __createBinding = (this && this.__createBinding) || (Object.create ? (function(o, m, k, k2) {
    if (k2 === undefined) k2 = k;
    Object.defineProperty(o, k2, { enumerable: true, get: function() { return m[k]; } });
}) : (function(o, m, k, k2) {
    if (k2 === undefined) k2 = k;
    o[k2] = m[k];
}));
var __exportStar = (this && this.__exportStar) || function(m, exports) {
    for (var p in m) if (p !== "default" && !exports.hasOwnProperty(p)) __createBinding(exports, m, p);
};
Object.defineProperty(exports, "__esModule", { value: true });
__exportStar(require("./types"), exports); // runtime error
exports.default = 1;

esnext
export * from "./types";
export default 1;

This was a known break scheduled for 3.9. (It should have been mentioned in the release announcement). Specifically, in the case of export *, the elision was (unintentionally) type directed, based on the contents of the target - this was not a behavior babel or other transpilers could mimic (and so users transpiling with other tools already saw this behavior). In addition, the unreliable elision made execution order at runtime unpredictable, which in turn made real runtime export availability in cases where references were circular unreliable.
You should endeavor to move the types directly into the module reexporting them, if you do not actually expect a file to be present at runtime corresponding to that declaration file (the locations of module declaration files correlate to valid runtime import paths). Failing that, explicit reexports of the types in question imported via import type declarations can work as well (as elision here is syntactically determinable).

Is that possible to have a tsconfig flag to prevent emitting empty import? export * is usually used in index.ts which sometimes import .d.ts declaration files should not get emitted.

@stephenzsy
Or something like:
export type * from "types"

Since this is supported:
export type { MyType } from "types"

It will be great if the following suggestion https://github.com/microsoft/TypeScript/issues/37238 can be implemented

You should endeavor to move the types directly into the module reexporting them, if you do not actually expect a file to be present at runtime corresponding to that declaration file (the locations of module declaration files correlate to valid runtime import paths). Failing that, explicit reexports of the types in question imported via import type declarations can work as well (as elision here is syntactically determinable).

@weswigham as a counter example we're re-exporting types automatically generated from JSON Schema (using https://github.com/bcherny/json-schema-to-typescript). We generate multiple files, some of which include 1k+ types over 3k+ lines. It's not practical to move them into modules or use named exports.
Another vote for #37238 as a workable solution to this.


1008p looks more blurry than 900p

1008p looks more blurry than 900p
with disable dynamic res and disable fsr mods

Check screenshots by opening them in at 100% size side by side
Link, the trees and his horse, all looks more blurry, less sharp
mods i'm using :
//Disable Variable Resolution Scaling
@enabled
00cea77c 15000014
@stop

// FSR (Pretty much just skipping the entire shader? (I could be wrong))
@enabled
027CA0DC 000080D2
0188D0D4 000080D2
00AEAC44 1F2003D5
@stop

// FXAA (Probably does nothing, but makes sure FXAA is not enabled)
@enabled
027CA13C 000080D2
0188D0A0 000080D2
@stop

// patchanon Disable FSR downscaling
@enabled
00CAD344 08008052
@stop

// patchanon Disable quality reduction when framerate dips
@enabled
00CAD34C C0000014
@stop

Is there a mod that "overlap" or have conflicts ?

I'm sorry i don't have the eyes for this slight differences, i'll ask to Hover to investigate
the only difference i see is on the horse's mane yes that's true

How can you not see ?
It's slightly less aliased, but it's way more blurry

 How can you not see ? It's slightly less aliased, but it's way more blurry

that's true, did you tried x2 resolution scale in the yuzu settings ? the performances lacks are from CPU and not GPU, you should try

I loose too much fps with 2x.
Also 2x makes it blurry with 900p, and shimmery with 1008p, so meh
Also I use Ryuinx :) way better.

1008 is not divisible by 1080 (in a whole number)
This means that scaling it to a 1080p viewport becomes blurry. This could possibly be fixed by using a 1008p sized windowed viewport, but I am not aware of any way to set windows to a certain height or width.
If anyone knows such software, it may be able to solve this issue, albeit by using a smaller viewport.
Now, to solve your specific issue, I think we have to get a bit more into opinion over fact, since the presentation of an image, is in some part, defined by user preference.
You should try the old, deprecated 1080p patch. It may be to your liking. It has great performance, and looks like this at x1:

If you would like further help to tailor your experience of TOTK to your personal preference, feel free to hit us up on the Yuzu discord, in the game-mods channel, but do keep in mind, that we can be quite busy at times.
We want to help though, so please be patient.

I don't use shitty emulators, sorry.


Switch -match to -eq to avoid errors on returning multiple certs

This command can return multiple cert's.
$Thumbprint = (Get-ChildItem cert:\CurrentUser\My\ | Where-Object {$_.Subject -match "CN=exampleappScriptCert" }
Switching '-match' to '-eq' will help reduce chance or error when returning thumbprint.

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

ID: 6329b3a8-32d6-c327-d3bc-2f6805d22ec8
Version Independent ID: a3fcf4d5-fb74-6f38-97f6-80dfafa66e06
Content: Create identity for Azure app with PowerShell
Content Source: articles/active-directory/develop/howto-authenticate-service-principal-powershell.md
Service: active-directory
GitHub Login: @CelesteDG
Microsoft Alias: celested

@RonStack Thank you for the valuable feedback,we are investigating the issue.

@RonStack Thanks for the feedback. If you have the certificates with the same CN then changing -match to -eq will not make a difference, as both commands return multiple certs. Can you elaborate a little bit more regarding your suggestion ?

Of course you are right. I didn't mean to say the exact same. I meant to use the example I ran into, having a cert called 'Ronny' and 'Ronny1'. Using -match to return the thumbprint would never work for 'Ronny'.

@RonStack I get it now. I will modify the command to use "-eq" and will update the doc. It will take some time for the doc to be update publicly.
Thanks again for reporting this.


Typehint causing build error in Symfony 3.4 - 4.4

https://github.com/contentful/ContentfulBundle/blob/9ebbf92865a5f109ae9958abe2ec191636fcf391/src/DataCollector/Delivery/ClientDataCollector.php#L52
In Symfony v3.4 we get a PHP compile error because the ClientDataCollector declaration does not match the Symfony DataCollector it extends. The collect method typehints the $exception variable to be \Exception rather than \Throwable.
In this case, the typehint should be removed in order to be compatible with supported versions of this bundle.

Thanks @phillyfan36 , we just fixed this in the latest 6.0.3 release.


Bump SMS local authenticator version.

Related to https://github.com/wso2/product-is/issues/19024

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/7596231155

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/7596231155
Status: success