[Q&A]: How does a release happen?

Question
Hi @shmuelzon!
After our changes last week, I saw that CI action succeed but no new release has been created with the latest changes.
How do you do generally? I know I can generate one locally, but having one here updated is also important.

Hey, releases are generated when I add a tag to the repository. I wanted to wait until your PR will be merged before I create a new release but will only have time to code-review it over the weekend.

Oh, I see. I thought you wanted to create one release per each PR or something similar. Otherwise, the release/tag can have a delay depending on this change. That's okay then.
Let me know your comments on #49, and I will try to push this week as well.

BTW - Just released v0.5.0. Thanks for all you help in improving this plugin!

I loved your project since beginning, it deserves attention! Thanks for letting me contribute to it 🚀


Option to remove menu bar extra (icon) on macOS

Tell us about your request
As a user of Docker Desktop, who runs it on startup, but likes to keep the menu bar area clear - an icon telling me Docker's running isn't useful to me, because it's supposed to be running - I'd like that icon to be a preference rather than required.
I'd expect the preference to be accessible by running /Applications/Docker Desktop.app or similar - to be in the same window as "Start Docker (Desktop) when you log in" for example.
Any options specific to the icon's menu (notably, and possibly only, the option that stops the service) should be available within the Docker Desktop window/app. I would expect that window/app can be quit, its Dock icon closed, without stopping the service.
The icon/menu that should be optional is pictured here:

Which service(s) is this request for?
Docker Desktop (for Mac)
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Apple HIG suggests "menu bar extras" should be optional ("Users, not apps, should choose when a menu bar extra is added to the menu bar.  Typically, this is done by changing a setting in an app’s preferences window.") You'll find a lot of Mac users are particular about what's shown there, and rely on developers following this HIG.
Are you currently working around the issue?
No known workaround with Docker Desktop. The icon cannot be removed e.g. by command-click and drag - it can only be rearranged with respect to the other icons.

This is especially important on a notched 14" MacBook Pro which has a very constrained menu bar space.

Yes! I don't really understand how any application can be so arrogant and not to have this option even though it's in the MacOS design guidelines
https://developer.apple.com/design/human-interface-guidelines/macos/extensions/menu-bar-extras/

pls!

Yes, please add!

How hard can it be? People have been asking for this for several years. I agree with @julierakovcova that the right word is arrogance, but by now its downright negligence.

I just use OrbStack now instead of Docker. I highly recommend it.

I vote for this bug/feature to be solved

Hi
Is there any progress on this?
Pretty sure its a high priority feature request from multiple users!

It's been three years, they don't seem to care.
What I do now that could circumvent this problem is Ice, which is an app that lets you customise your menu bar (i.e. hide icons). It's totally free and can be installed with brew (brew install jordanbaird-ice).


FermionicOp simplify fails to do its task

Environment

Qiskit Nature version: qiskit-nature==0.5.2
Python version: 3.10.10
Operating system: macos

What is happening?
Calling simplify on a FermionicOp doesn't yield a fully simplified representation of the operator.
Calling normal order first seems to be a work around for this issue, but it makes simplifying SparseLabelOp in a generic manner impossible.
Simplify for Fermionic op should likely make use of normal ordering to perform simplification. The current implementation doesn't work.
This is similar to issue #901, but it's not that simplify is not agressive enough, but that it fail entirely to simplify the fermionic operator.
How can we reproduce the issue?
from qiskit_nature.second_q.hamiltonians import FermiHubbardModel
from qiskit_nature.second_q.hamiltonians.lattices import LineLattice,BoundaryCondition
from qiskit_nature.second_q.operators import commutators
from qiskit_nature.second_q.operators import FermionicOp

#Create a hamiltonian, Hubbard model because that's what i have on hand.
U = 4
mu = 2
t=1
L=2
line_lattice = LineLattice(num_nodes=L, boundary_condition=BoundaryCondition.OPEN)
Hamiltonian = FermiHubbardModel(line_lattice.uniform_parameters(uniform_interaction=t,uniform_onsite_potential=-mu),onsite_interaction=U).second_q_op()

#secondary operator
C0 = FermionicOp({ "+_0": 1 },    num_spin_orbitals=4)

#create a more complicated fermionic operator
F = commutators.commutator(Hamiltonian,commutators.commutator(Hamiltonian,C0))
print(len(F)) #prints 106
print(len(F.simplify())) #prints 106
print(len(F.normal_order())) #prints 6

What should happen?
simplify should manage to reduce the number of label in F as much or more than normal_order
Any suggestions?
aplying normal ordering could be part of simplify's implementation.

Had you seen this https://qiskit.org/ecosystem/nature/stubs/qiskit_nature.second_q.operators.FermionicOp.index_order.html It was done as part of #902 which addressed the #901 issue you referred to above. #902 has some comment in there as regards the choice things that way.

It's of little help when working with generic SparseLabelOp. simplify is apart of the generic interface, but not normal_order, nor index_order.
At best, those are workaround for FermionicOp simplify failing to simplify the fermionic operator.

With the current development version of Qiskit Nature F has only 6 terms from the beginning (and never 106).
Regardless of that, as Steve also pointed out earlier, this behavior is intentional as explained here:
https://github.com/qiskit-community/qiskit-nature/blob/eb30b6b0e8b042a1f431a1ce7a633856b8b5bcf4/qiskit_nature/second_q/operators/fermionic_op.py#L437-L444
Arguably, we should add this note to the docstring of the FermionicOp.simplify method, too.


opt jemalloc conf lg_tcache_max restore default

Proposed changes
tc/jemalloc_free_memory in web beip:8040/mem_tracker is the cache size of Jemalloc.
Previously lg_tcache_max:20, this will cache up to 1M Bin in the thread cache, which will cause the Jemalloc cache to be too large in some scenarios.
Restore the default lg_tcache_max:16, which can cache a maximum of 64K Bins.
If you are doing a performance POC, you can consider increasing it.

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Scaling of historical stacked observations

I'm not sure if this is a bug or not or maybe I am missing something. When a raw action a~[0, n) is sent to the dynamics network, the network will convert the raw action into a feature plane such that the values are 1/a (which follows the paper):
# models.py
# MuZeroResidualNetwork.dynamics() ...
action_one_hot = (
    action[:, :, None, None] * action_one_hot / self.action_space_size
)

If no stacked observations are being used, then the prediction network simply takes in the current state. If however M stacked observations are being used, then the previous M observations and actions are stacked and used as input the prediction network. Since we are stacking, the raw actions need to be converted to planes as done in the dynamics network. What isn't being done though is the action feature plan scaling:
# self_play.py
# GameHistory.get_stacked_observations() ...
previous_observation = numpy.concatenate(
    (
        self.observation_history[past_observation_index],
        [
            numpy.ones_like(stacked_observations[0])
            * self.action_history[past_observation_index + 1]
        ],
    )
)

I believe the expected behaviour is that the action planes are to be scaled, and I think the wording from the paper suggests that this is the case. Thus, I believe the above code should be as such, assuming game history structs have the action_space_size as a member variable:
# self_play.py
# GameHistory.get_stacked_observations() ...
previous_observation = numpy.concatenate(
    (
        self.observation_history[past_observation_index],
        [
            numpy.ones_like(stacked_observations[0])
            * self.action_history[past_observation_index + 1] / self.action_space_size
        ],
    )
)

I also believe there is a related issue with the representation function. The result of get_stacked_observations is a stack of observations + action planes. Each action plane has a tiled value a (and above I think it should be a / num_action). In any case, the representation function then will min/max scale each channel in the stacked observation: https://github.com/werner-duvaud/muzero-general/blob/master/models.py#L526.
Wouldn't this cause every action channel in the stacked observation to just be a tile of all 0's? Since the action channel is a channel of the same value, min_encoded_state - max_encoded_state = 0 for those action channels. I've attached a quick gist demo to show that if we have a plane of all the same values passed to the representation function, then that channel gets 0'd (as would be the case for action planes): https://gist.github.com/tuero/67c4e99a1547ad4101973a4a7dcd3623

Hello @tuero ,
Thank you for your interest in the project and for reporting this issue ! The commit 0c4c335d0492d48f7cb8979d479b2761b5d267fb should have fixed this issue.


Detect ASE in host_exerciser to adjust timeout for simulation

Coverage remained the same at 66.091% when pulling 5f7faa311b3589ada3983a518a5c95304643fdab on mcadler/he_ase into 214c25cc1257aebe2b147031057789847986f1ed on master.


HEX (hexadecimal) ident

Hello,
In the moment you can set only one ident. And for example if someone ban this ident multiple uses will be impact and that's not good for me. This future is already done in webirc clients like qwebirc and lightirc.
Example:
[19:28:58] * BGChat70516<EMAIL_ADDRESS>has joined #Bulgaria
Where the ident : 5ec578c8 = IP ( <IP_ADDRESS> )

WEBIRC support has already been merged: #240

This is partly being addressed in #256. The hex indent is non-standard and so far I think only Freenode uses that. If the user connects over IPv6 the number won't fit anymore. For that purpose webirc is a better solution.

Can be closed as of #749

Can someone open an issue with details in https://github.com/thelounge/thelounge.github.io ? The moment that I'll go into heavily improving our docs is getting closer and closer, and that would help making sure there is room for this.


Switch "docker-compose" to "docker compose".

💡 Summary
The docker command is now capable of doing the work of docker-compose.    This message is now emitted by docker-compose:
❱ docker-compose up
Docker Compose is now in the Docker CLI, try `docker compose up`

Motivation and context
Eventually this will be the way™.
Implementation notes
https://docs.docker.com/compose/cli-command/
I've noticed that the new command is more pedantic about the docker-compose.yml files.
Specifically, it does not permit quoted integers for port numbers.
Acceptance criteria
How do we know when this work is done?

[ ] all docker-compose references converted to docker compose
[ ] all included docker-compose.yml files work with new command

Greetings,
I have no clue what skeleton-docker is, but having stumbled on this ticket, I would advise you to have a look at the ticket about compose-cli's new message, which indicates that docker compose up in currently in preview, before proceeding with this.

This appears to have been done in https://github.com/cisagov/skeleton-docker/pull/105.


Angular 7 Integration

Hi, I'm just wondering on how one can integrate this into Angular 7. Like a simple component where I just a field in a text field and it updates the value in the other text field.
Thank you in advance!

How would I apply this in this example here?
https://stackblitz.com/edit/angular-zw8qp8
Like, I want to remove RxJs and replace it with observer-util


Re-generating speech assets does not remove old customSlots

After removing customSlot and re-generating speech assets using app.saveSpeechAssets() the customSlots that were removed are kept in customSlots dir

PR #31


Using ctid as IV base instead of offset calculation

This commit modifies the ID calculation of normal tuples to just use the alrady exisitng ItemPointer to offset the IV instead of the actual offset addresses, as the ItemPointer doesn't change during moves and also easier to use for replication.
As part of this, the structure of the IV is also changed: instead of using the offset as the base number, and incrementing it sequentially, we now insert the "base" ItemPointer at the high part of the IV, and start the counter at the other end, at the low part of the IV.
This means that we are no longer using AES-CTR, but instead rely on a custom AES based encryption, but this is also required for toast, as with that, we can't rely on the uniqueness of the address in the entire data range.
Old encryption tests are also deleted, as they no longer work with these changes.

There is also a tiny typo in the commit message. "alrady"


Show mutations in voyager

Modified the property displayOptions.rootType so it takes an array of strings rather than a string by representing the root types. By default, this is ["Query"].
This additional functionality allows both Query and Mutation types to be seen on Voyager.
Resolves #37, resolves #200

any update on this? looks promising!

I disagree with this.
In GraphQL the read and write model are separated. Purposefully separated. The root, but definition, is one, any type can be root. An array of roots feels weird and logically it does not make a lot of sense.
What's the effect of returning multiple root type in a bigger model?

@LunaticMuch I agree with you on that, voyager is already too noisy for big graphs.
At the same time, the current way of switching query/mutation/subscription is not very intuitive.
Also, it is bad that you need to wait each time you switch between query and mutation.
What we can do is to make tabs on top of the graph view (only if API has Mutation or Subscription root types): https://mui.com/material-ui/react-tabs/#basic-tabs
Also, we can run multiple web workers so query/mutation is rendered in parallel.

I moved the discussion into a separate PR and closed this one since we wouldn't be rendering multiple roots simultaneously.


Flow to Power Automate and Power BI reference please

[Enter feedback here]
Please can we update to refer to Power Automate and not Flow on this page
Additionally there is no mention of Power BI which would seem logical to mention here. Even if its just a link to this page would be useful https://docs.microsoft.com/en-us/power-bi/admin/service-admin-premium-multi-geo
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: b890c9af-0bab-84c6-8b9d-1ee93cb4683f
Version Independent ID: 98fddfad-754b-ef65-7f5f-5f8bd8f59004
Content: Administering a multi-geo environment - Microsoft 365 Enterprise
Content Source: microsoft-365/enterprise/administering-a-multi-geo-environment.md
Service: o365-solutions
GitHub Login: @MikePlumleyMSFT
Microsoft Alias: mikeplum

@sksumner Thank you for your feedback. We have made changes to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/3948
Thanks
Sri

@sksumner Thank you for your feedback. We have made changes to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/3948
Thanks
Sri

@sksumner Thank you for your feedback. We have received confirmation from the author and reviewers that Power BI regions are not related to Microsoft 365 Multi-Geo.
@yogkumgit Please proceed with closing the case as there are no changes required in the document.
Thanks
Sri

@msbemba Thank you very much for the contribution and sharing this explanation. @sksumner Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Dropdown is not behaving correctly

Yay, first real issue.
The dropdown as is as we have it now (even with pawel changes on toggle) is not working right on the CSS.
Check this plunker
First two works good, the third one doesnt.
There seems to be a dropdown and button dropdown. First two are button dropdown (they need a btn-group) and the third one which is the raw one (the one we support directly) has the popup weirdly.

This is because of our choice to use element directives for dropdown. When you use an attribute it all works as expected: http://plnkr.co/edit/6e0TFcrlFXMQpuAWzvPO?p=preview
It seems like dropdown needs to be a block element but unknown elements are interpreted as inline by default (http://www.impressivewebs.com/default-css-display-values-html-elements/)
IMO we should have ngb-dropdown  as an attribute.

Weird, thought that I tried that too when I was playing with it. I was also going to recommend that change too.


typo: fourthcoffeecorp.onmicrsoft.com

[Enter feedback here]
typo in the following domain
fourthcoffeecorp.onmicrsoft.com

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

ID: 46a11050-b442-7a48-0d37-9bce8908fc14
Version Independent ID: 5456e564-2629-cfc2-dfc9-2b7934fcf43a
Content: Domains Frequently Asked Questions
Content Source: microsoft-365/admin/setup/domains-faq.yml
Service: microsoft-365-business
GitHub Login: @efrene
Microsoft Alias: efrene

@paulaustin-automutatio Thank you for your feedback. The changes have been made by @DMoenks via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/10159
Once the author approves, the changes will be live.
Thanks
Sri


Flake8

Enable flake8 linting in tox.ini
Currently, flake8 is accessible via make lint, but it does not run
along side the rest of the test suite. This change adds flake8 checks to
the tox.ini file to enable linting as a routine part of running tests.
Fix flake8 errors

Coverage increased (+0.2%) to 72.269% when pulling d853ed7dca97d957244f809fb929d628c8af096a on jonafato:flake8 into 08160bdf95719119343402149f3e1c21801c471c on bndr:master.

Coverage increased (+0.2%) to 71.008% when pulling 7bdf532c0fb0dcd36872fa5705dc99c49463d0a3 on jonafato:flake8 into 1d48345cb0dd3b8931d75741fb913d48cc94b80f on bndr:master.

Coverage decreased (-0.2%) to 70.588% when pulling 26714252fc30b54ba9721892266be0b59d5cea0e on jonafato:flake8 into 1d48345cb0dd3b8931d75741fb913d48cc94b80f on bndr:master.

Coverage increased (+1.5%) to 72.269% when pulling e88b5ab19cb5044acb5a05218865f4d5c1b8999f on jonafato:flake8 into 1d48345cb0dd3b8931d75741fb913d48cc94b80f on bndr:master.


zoomTouchPinch problems after switching images

After trying for hours to make this work I post this here because maybe its a bug.
I have only one element to display images with the zoomTouchPinch tool attached. There are two images to be loaded there, one with cornerstoneWebImageLoader, the other with cornerstoneWADOImageLoader.
When I load the first image (it doesn't matter the order, it can be Web or WADO), it works as expected (expand fingers zoom in, contract fingers zoom out), then I switch (*) the image and zoomTouchPinch goes crazy allways zoomming out. It looks like this tool is not "reseted" properly before attaching to the new image.
*: The switching process follows these steps inside loadAndCacheImage:
// the next two lines refreshes the element. I don't know if there's a better way
cornerstone.disable(element);
cornerstone.enable(element);
cornerstone.displayImage(element, image);
cornerstoneTools.touchInput.enable(element);
cornerstoneTools.zoomTouchPinch.activate(element);

I've tried zoomTouchPinch.disable(element) before activate, but it doesn't fix the issue.

Hmm yeah definitely sounds like a bug. Strange because pinch input handling is quite simple.. I'll look into it. You shouldn't need to disable and re-enable the element just to switch images.

Hi Erik!, great to know this can be a bug, hopefully you can help me find a workaround/fix.
I know disabling/enabling the element shouldn't be needed, but before switching the images I have to hide the element's canvas with display:none, then, when set display:inline-block again the only way I found to display the element is disable/enable. Do you know a way to clear the canvas without display:none?.

What about using visibility or opacity in CSS instead of display?

Thanks that allowed me to remove disable/enable. I had to add cornerstone.resize(element, true) after displayImage because if not, the image was displayed very tiny,
BTW, this doesn't solve the zoomPinchTool problem.

I can't seem to reproduce this bug. My code is here:
https://gist.github.com/swederik/8a416ad61dea2fcf9deb
Could you tell me if there anything you're doing that I'm not or vice versa?

Thanks to your example I found the problem, I was calling cornerstoneTools.touchInput.enable(element) inside loadAndCacheImage and you call it just after cornerstone.enable only once.
Fixed!.

Great! We actually had this same issue before for mouseInput (See #89), so now I've gone and made the same type of change for touch input so this type of bug doesn't occur anymore.
Thanks for the report.


various improvements

(0) Intro page:
compiler with python3 valec.py build hello.vale     <-- command changed in release v 0.1.1
(1) Sealed interfaces:

impl SomeInt for MaybeInt;   should be according to:
impl interface for struct

so:  impl None for MaybeInt; --> impl MayBeInt for NoInt
impl SomeInt for MaybeInt; --> impl MayBeInt for SomeInt
(2) Regions: Here, we're making an regioned object   <-- a
(3) On frontpage:  native (AOT compiled)
<-- A question I saw somewhere was: Is it interpreted or compiled, AOT or JIT, native or byte code? This info should be on the front page; adding AOT compiled to clarify
(4) Structs page:
immutable_structs
--> added ship2 to more clearly show that immutable structs can have multiple owning references
(5) Match statement:
on page: no highlighting ?
same on page: Interfaces: Simplified syntax
--> Added Vale after Perhaps this was intentionally left out? What doesVale: notest means?
If it was intentional to leave Planned Feature code without syntax highlighting, this is not consistent with the Interfaces page, where highlighting is done in Planned Features code.
(6) Bad link:

on homepage: link to Next Steps for Single ownership ... gives Page not found error with the bad link: https://vale.dev/blog/next-steps-raii
The correct link is: https://vale.dev/blog/raii-next-steps

I've not done a github review before, so this is unknown waters for me too!
I'm not seeing the adjustments you made, perhaps git push again?

I've not done a github review before, so this is unknown waters for me too!
I'm not seeing the adjustments you made, perhaps git push again?

Ok, I did a git push after changing, and there is a 2nd commit here. Normally you should be able to merge it I think.

Ok, I did a git push after changing, and there is a 2nd commit here. Normally you should be able to merge it I think.

Looks great, thanks for these changes!

Looks great, thanks for these changes!


spot_allocation_strategy feature for managed node groups

Is your request related to a problem? Please describe.
Currently unable to set the spot allocation strategy on AWS managed node groups.
Describe the solution you'd like.

It is possible to set spot allocation strategy in Self managed node groups with parameter  spot_allocation_strategy = "capacity-optimized"
A similar parameter for managed node groups would be very useful.
Additional context

I would like to be able change the spot allocation strategy of managed node groups to price-capacity-optimized

Does managed nodegroups support this?

Does managed nodegroups support this?

I'm able to go through the AWS console to the ASG and change it manually on a node group there. So I assumed it does, but I could be wrong.

managed nodegroups do create ASGs, but that doesn't mean that they expose all of the features/functionality of the ASGs. I would try setting this in the launch template to see if this works or not

closing this for now - if the EKS APIs and the AWS provider support this, then we can support it here as well


When using single-room mode, typing indicator for users not shown anywhere

Is your feature request related to a problem? Please describe
When using a single room, we miss typing indicator, as it is shown only in the rooms list.
But in the single-room mode, the rooms list is not visible, which is good and expected.
Only the typing indicator should be shown in another way in this case.
Describe the solution you'd like
When using single-room mode, typing should be shown in the chat message or in the chat header.
Describe alternatives you've considered
I have considered use of :messages-loaded="messagesLoaded" instead, but it shows a loading indicator at the very top of the chat history, not at the bottom, and therefore - not visible to a user.
Another way could be to add a temporary system message, like
{
        _id: lastId + 1,
        indexId: 12092,
        content: "User is typing...",
        senderId: "4321",
        username: "assistant",
        date: "23 April",
        timestamp: "10:20",
        system: true,
      },

and remove this message, when the async typing operation is done.
As system messages look different, that might work.
Additional context
Related to this question: https://github.com/antoine92190/vue-advanced-chat/issues/428

Typing should actually be shown in the header, if it's not the case then it's a bug

@antoine92190 it has is writing... indicator in the header, but doesn't specify which user is writing, even given that Users are set to the room object and userId is added to typing array.


Compiler doesn't resolve node dependency using "main" key value in package.json

package.json can declare a key "main" with a value that's a reference to a file in the package (npm docs). However Google Closure Compiler seems to ignore that value and always look for a file "index.js" as the default. So when a file using that package declares a dependency using require, GCC throws an error.
Example
End user's project
index.js
const xtend = require('xtend');
package.json
{   "dependencies": {     "xtend": "4.0.0"   } }
npm project
immutable.js
... useful utility...
package.json
{   "main": "immutable" }
When the end user runs GCC (ensuring they've supplied the xtend package using the --js flag to the command) they will get this error:
my-project.js:1: ERROR - Failed to load module "xtend" var xtend = require('xtend');             ^ 1 error(s)
This is sort of related to https://github.com/google/closure-compiler/issues/3149 (Packages with dir as "main" in package.json do not resolve.) but I'm filing it anyway just in case the solution for that bug doesn't address this.
I've patched xtend here to fix material-components-web compilation via GCC for my project (I pull in my fork via my package.json).

Created Google internal issue b/120550812.

@jmosney Did you supply the package.json file to the compilation? You need to pass --js node_modules/immutable/package.json along with your other source files.

Ah, that did it! Thanks very much Chad!


Add support for storybook

Fixes #1091
Changes proposed:

[X] Add

Things I've done:

[X] My pull request fixes an issue, I referenced the issue.

This adds the official storybook icon to the extensions 'story.js' and 'stories.js'.

Wrong button! I am looking forward to this landing

Does this also work for .stories.jsx and .stories.ts(x)?


redisson-spring-boot-starter RedissonAutoConfiguration customizer

In Spring Boot RedissonAutoConfiguration there is the need for post customizing the autoconfigured RedissonClient.
Would you consider a pull request with this functionality?

Yes I would consider it. What is the motivation for this?

We would like to keep the RedissonClient autoconfigurated and just override some of the default Config attributes (e.g. the Codec from Fst to Jackson)

You can use spring.redis.redisson.config spring setting to define path to redisson yaml config.

Actually we don't want to configure the RedissonClient from scratch, we want to keep the default autoconfiguration and implement a customizer interface which will customize some of the default Config attributes before the Redisson.create(config) invoked.
Maybe i can open a PR to show you what we have in mind ?

Yes, that would be better.

Thanks for you immediate response!!! I will open it asap.

@mrniko
I opened a pull request, with the enchancements i am proposing.
Thanks !!!


List reports configured

Closes #833
I still need to update the release notes - hence draft status.
I'm not sure how to note that report is non-default (it will not be enabled using all, currently only sarif works that way). Current output:
 robocop --list-reports
Available reports:
file_stats           - Prints overall statistics about number of processed files (disabled)
rules_by_error_type  - Prints total number of issues grouped by severity (disabled)
rules_by_id          - Groups detected issues by rule id and prints it ordered by most common (disabled)
sarif                - Generate SARIF output file (disabled - non-default)
scan_timer           - Returns Robocop execution time (disabled)
timestamp            - Returns Robocop execution timestamp. (disabled)
version              - Returns Robocop version (disabled)

Enable report by passing report name using --reports option. Use `all` to enable all default reports. Non-default reports can be only enabled using report name.

I'm not sure how to note that report is non-default (it will not be enabled using all, currently only sarif works that way).

Maybe, instead of the report, we should make SARIF report a separate CLI option (--sarif)?


change wording and link style

Issue
Fixes #232
Description
Guide the users to /search seamlessly
Testing instructions
https://localhost:3000/overview > check first section
Screenshots (optional)

@zperova What do you think of these new texts?


Foreknowledge Convos

You may wish to include this mod:
https://www.nexusmods.com/starfield/mods/5319?tab=files&file_id=18053&nmm=1
During the quest Foreknowledge, assuming you saved everyone, all your Constellation peeps will continue to talk as if someone died.

Details
Refer to this mod for details:
https://www.nexusmods.com/starfield/mods/5319?tab=files&file_id=18053&nmm=1
Game Version
<IP_ADDRESS>
Language
English (EN)
New Game
Yes
Reproduction Steps
Regular playthrough.

Is this not already fixed in a previous release?


Unable to generate KONG client credentials on HTTP protocol.

Can anyone please help me out. I'm getting error while generating KONG client credentials on HTTP port 8000.
{     "error_description": "You must use HTTPS",     "error": "access_denied" }
I have added trusted_ips = <IP_ADDRESS>/0,::/0 in kong.conf also, but it didn't work.

Yes, OAuth2.0 Plugin only allows HTTPS or HTTP if HTTPS was terminated and there was X-Forwarded-Proto with value of https added.

Please review the following codes,maybe you can fix it so easy!
--- Checks whether a request is https or was originally https (but already -- terminated). It will check in the current request (globalngxtable). If -- the headerX-Forwarded-Protoexists -- with valuehttpsthen it will also -- be considered as an https connection. -- @param trusted_ip boolean indicating if the client is a trusted IP -- @param allow_terminated if truthy, theX-Forwarded-Proto` header will be checked as well.
-- @return boolean or nil+error in case the header exists multiple times
_M.check_https = function(trusted_ip, allow_terminated)
if ngx.var.scheme:lower() == "https" then
return true
end
if not allow_terminated then
return false
end
-- if we trust this IP, examine it's X-Forwarded-Proto header
-- otherwise, we fall back to relying on the client scheme
-- (which was either validated earlier, or we fall through this block)
if trusted_ip then
local scheme = ngx.req.get_headers()["x-forwarded-proto"]
-- we could use the first entry (lower security), or check the contents of
-- each of them (slow). So for now defensive, and error
-- out on multiple entries for the x-forwarded-proto header.
if type(scheme) == "table" then
  return nil, "Only one X-Forwarded-Proto header allowed"
end

return tostring(scheme):lower() == "https"

end
return false
end
`

I'd like to fix this issue, I'll be grateful for any further tips on where to start.
Thanks!
Friendly /cc @bungle

@scorphus Have you fixed this issue?

@abimarank still finding my way around it. Do you have any tips?
/cc @thibaultcha 🙂

1.While using docker we have the option to choose from https and http when creating an instance using an image in a container this will remove the error.
2. Not Using nginx proxy server will remove this error becaue it work only with http response
3. Graphql API should be used on the client side.

Is anyone interested in this and can come up with a PR?


perlPackages.FileTouch: init at 0.11

Motivation for this change
Add File::Touch module from CPAN.
Things done
Also corrected alphabetization for the FileTemp and FileType packages.

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[X] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

Rebased to master in 2ecd96a135c97b83f4e2d3b8d2d08ed9832d9520. Thanks!


Bugfixes

This PR fixes the contact not being refreshed after editing bug (#1).
Also fixed another small bug where the phone number urlString wasn't using the cleanedValue.


Add cross-platform support for crypto in randomBytesBuffer function

Problem solved
This function is used in the generatePayload method when generating the payload in the login route to implement SIWE authorization on the server side. Currently, the function only works in the browser, but this fix will allow it to execute on the server as well, enabling it to generate the login payload without errors.
How to test
Just call thirdwebAuth.generatePayload method and you'll get an error without the fix:
TypeError: Cannot read properties of undefined (reading 'getRandomValues')

If the fix is applied, there will be no error.
Ref: https://portal.thirdweb.com/connect/auth/frameworks/react-express
Changes made

[ ] Public API changes: list the public API changes made if any
[x] Internal API changes: explain the internal logic changes

How to test

[ ] Automated tests: link to unit test file
[x] Manual tests: step by step instructions on how to test

Contributor NFT
Paste in your wallet address below and we will airdrop you a special NFT when your pull request is merged.
Address: 0x6047ec2435C5906241AeAcC13b09D3c0eb09Cb45

PR-Codex overview
The focus of this PR is to convert synchronous operations to asynchronous in the authentication and random generation processes.
Detailed summary

Converted randomBytesHex and randomBytesBuffer functions to be asynchronous.
Updated functions in cognitoAuth.ts and fetchers.ts to use await for randomBytesHex.
Modified functions in various files to await getSessionHeaders calls for nonce generation.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Also, there is a workaround to fix it without this PR, but it needs to be specified in the documentation, I think. It's not type-safe though.
import { webcrypto } from 'crypto';

globalThis.crypto = webcrypto;

thank you for the contribution! just need to double check this doesnt break anything with the metro bundler in react native. will report back

one interesting note here, starting in node20 this should no longer be required: https://nodejs.org/docs/latest-v20.x/api/webcrypto.html

one interesting note here, starting in node20 this should no longer be required: https://nodejs.org/docs/latest-v20.x/api/webcrypto.html

@sunsetlover36 I assume you're using node18 in a scenario where this breaks?

given the nodejs release cycle I wonder if there is a way to do this in a more polyfill-for-node-18 way, we're basically just slightly ahead of when we could ignore this problem and tell people "node 20+ only please"

one interesting note here, starting in node20 this should no longer be required: https://nodejs.org/docs/latest-v20.x/api/webcrypto.html

@sunsetlover36 I assume you're using node18 in a scenario where this breaks?

Yes, I was using version 18.19.0. I tried with a newer version, and it actually works. I wasn't aware of that. With Node 20+ the issue should be resolved.

thanks for confirming! - I think it this case it might be good enough to advise folks on node 18 to polyfill globalThis.crypto = require("crypto").webCrypto in this case. I'm a little worried about the consequences to bundlers etc across the stack (in frontend environments mostly) that might up this path and break otherwise.

Going to close this for now and add the note about the node 18 polyfill to the docs


Unable to create new subscription

Deleted my two subscription sandboxes to test on fresh sandbox, turned out I cannot create the third sandbox while the oldest(2 years ago) and the recently deleted sandbox are still there even it said "Deleted subscription". I thought old subscription will be removed after 60 days and the tenant will be available to pickup later.

Hi, sorry to hear you were having issues and they're resolved now! I'm closing this issue; if you still need assistance, contact<EMAIL_ADDRESS>As you can see, this repo isn't monitored regularly. We're working on that!


Support ONNX Operators: ScatterND and Range of YoloV5

Hi,
I use YoloV5 to ONNX. Then want to use the SageMaker Neo Compile ONNX.
I got the following error messages:
ClientError: OperatorNotImplemented:('The following operators are not supported for frontend ONNX: Range, ScatterND")
You can repeat the error via this notebook link

@imyoungyang hey! its been a while, but I'm trying to use Neo to compile the yolov5 model and running into the same issue, as well as a mismatched input shape. They updated the yolov5 repo a lot since then, so have you by chance got this working?


Add ability to mock static files in tests

This change introduces a new helper class for use in Python unit tests:
core.testutils.mock_staticfiles.MockStaticfilesFinder
This finder can be added to the list of Django staticfiles finders in the STATICFILES_FINDERS setting.
This class gives you the ability to mock the existence of static files for test purposes even if those files to not exist in the repository at test time. Generally this is useful when some other process (e.g. the frontend build) will be generating those files, and we don't want to make the backend tests dependent on that process. In particular this PR is being introduced to support the work in #3887 to add Capital Framework icons to this repository.
See the documentation and tests for a detailed explanation of how this code works. As an overview, in test settings you can now add:
from base_settings import *

STATICFILES_FINDERS += [
   'core.testutils.mock_staticfiles.MockStaticfilesFinder',
]

MOCK_STATICFILES_PATTERNS={
    'files/to/mock.jpg': 'file/to/serve/instead.jpg',
}

The mock finder acts like the files being mocked exist but return the path to another file instead; this other file must be findable by other staticfiles finders you have defined (e.g. Django's FileSystemFinder).
Note that unfortunately the Django docs currently say that "Static file finders are currently considered a private interface, and this interface is thus undocumented."
I've tried to add sufficient tests to verify the intended behavior and ensure that it continues to work in future Django upgrades.
Testing
The unit tests should demonstrate this new functionality; I haven't actually added this to test settings yet because we won't need it until we try to add the CF icons in #3887.
Checklist

[X] PR has an informative and human-readable title
[X] Changes are limited to a single goal (no scope creep)
[X] Code can be automatically merged (no conflicts)
[X] Code follows the standards laid out in the development playbook
[X] Passes all existing automated tests
[X] New functions are documented (with a description, list of inputs, and expected output)
[X] Reviewers requested with the Reviewers tool :arrow_right:

This all seems to make sense to me.


feat: sort custom resources by metadata.name

What this PR does / why we need it:
Currently, there is no determined order of clusterinputs, clusterfilters, and clusteroutputs. If a user wants to use fluentd rewrite_tag_filter, then unordered clusterfilters may affect the final results of log entries.
fluent-bit has similar feature.
Which issue(s) this PR fixes:

Fixes #
Does this PR introduced a user-facing change?

Fluentd  clusterinputs, clusterfilters, and clusteroutputs will be sorted by metadata.name

Additional documentation, usage docs, etc.:

That's great


Support to repLoad the clone files generated by Trust4 program.

🚀 Feature

Support to repLoad the clone files generated by Trust4 program.
Motivation

Among the clonotype identification tools, Trust4 is an emerging tool that are recently updated. Its previous paper were published on Nature: https://dx.doi.org/10.1038%2Fng.3581
I am not the developer of Trust4, I am just a user, however, the preliminary results of Trust4 show that the tool yields high quality clones. We want to chain the Trust4 and immunarch seamlessly in our research. We hope to use immunarch to analyze the results from Trust4 without manually converting the Trust4 result format to VDJtool result format.
Pitch

I wish to have repLoad() directly read the clonotype files from TRUST4. If there are some fields that are missed in the Trust4 results but needed in the immunarch input, please contact the Trust4 developers to request a new feature.
https://github.com/liulab-dfci/TRUST4
Alternatives

Additional context

Hi @whitehilltea
Thank you for the suggestion! Can you provide an example output of the software tool so we can test the immunarch parser on it please?

Hi, @vadimnazarov
Thanks for considering the feature request.
trust4_result.zip

Hi, @sciencepeak!
My name is Aleksandr Popov, I am a developer of the Immunarch package.
Thank you for using our software!
I'm happy to inform you that Immunarch starting from version 0.6.7 supports Trust4 format in repLoad function. You are welcome to use it!
Good luck,
Aleksandr

@Alexander230
Thanks for adding the feature.
I tested the new feature, and found that the automatical detection of the clonotyping tool label the trust4 as vdjtools. Perhaps there are more improvement room.
immdata <- repLoad(file.path(getwd(), "trust_clones_result_directory"))  # Replace it with the path to your data. Immunarch automatically detects the file format.
== Step 1/3: loading repertoire files... ==

Processing "D:/MyData/Git/TCR_integrated_project/01_old_tidy_individual_project/trust_clones_result_directory" ...
  -- [1/60] Parsing "D:/MyData/Git/TCR_integrated_project/01_old_tidy_individual_project/trust_clones_result_directory/SAMN13223146.trust_clones.txt.bz2" -- vdjtools
  -- [2/60] Parsing "D:/MyData/Git/TCR_integrated_project/01_old_tidy_individual_project/trust_clones_result_directory/SAMN13223147.trust_clones.txt.bz2" -- vdjtools
  -- [3/60] Parsing "D:/MyData/Git/TCR_integrated_project/01_old_tidy_individual_project/trust_clones_result_directory/SAMN13223148.trust_clones.txt.bz2" -- vdjtools
  -- [4/60] Parsing "D:/MyData/Git/TCR_integrated_project/01_old_tidy_individual_project/trust_clones_result_directory/SAMN13223149.trust_clones.txt.bz2" -- vdjtools
  -- [5/60] Parsing "D:/MyData/Git/TCR_integrated_project/01_old_tidy_individual_project/trust_clones_result_directory/SAMN13223150.trust_clones.txt.bz2" -- vdjtools
  -- [6/60] Parsing "D:/MyData/Git/TCR_integrated_project/01_old_tidy_individual_project/trust_clones_result_directory/SAMN13223151.trust_clones.txt.bz2" -- vdjtools

Hi, @sciencepeak!
Thank you for providing the data! There is a possible bug, I will investigate it and noitfy you when there will be a fix.
Best regards,
Aleksandr


PLNSRVCE-700: use volumeClaimTemplate instead of static PVC

Signed-off-by: Chenxiong Qi<EMAIL_ADDRESS>

Update: this pr includes the changes made by Michal in PR #63.

/retest build-service-e2e

/test build-service-e2e

/retest

/retest

/retest


AYS server does not want to die, which means that eventloops are stuck.

Installation information

jumpscale version: 8.2.0 (dfd1f642098fdb7d611386380b463aa94378a356)
operating system: Ubuntu 16.04

Detailed description

Pressing CTRL-c eventually did not work nor did send SIG_TERM. Needed to send SIG_KILL to be able to end the process.
Steps to reproduce
Install a resourcepool on be-g8-3.
Try to deploy a storagecluster (won't work due to other bug in ays)
Then wait for 6 hours.
Relevant stacktraces

Should be fixed in https://github.com/Jumpscale/jumpscale_core8/pull/923


locust doesn't record all the requests

Hello all,
I am using locust and there is a problem with the total number of requests recorded by the API and WebUI.
I started a tests with 1 client and hatch 1, and looked on my application log and counted the request. The locust WebUI showed me that they were 26 requests made after I stoped the test, but in the /var/log/httpd/access_log I counted 31 requests ..so there is a difference by 5 requests which haven't been displayed neither in API nor WebUI.

I have seen some requests happen while locust itself is initializing

This might also happen if a request returns a HTTP redirect, since I believe the default behaviour for python requests is to follow redirects, and Locust will then group them both (all) together and record them under a single request entry.
It could definitely be argued that they should be recorded separately, but that would cause problem in cases where one is using the name argument to group together URLs that have some dynamic parts (e.g. an ID).


Change the Map Point Tool icon

Change the map point tool to use the 16 bit image not the 32 bit image. This is based on the feedback from graphics.

There are a few other icons where we are using 32x32.  If we are going to update them to 16x16 then I think we should do them all.

pull request waiting #114

Working on another project right now.  Will get to it when I’m done.  Thanks.
From: Joseph McCausland<EMAIL_ADDRESS>Sent: Friday, June 03, 2016 9:12 AM
To: Esri/coordinate-conversion-addin-dotnet
Subject: Re: [Esri/coordinate-conversion-addin-dotnet] Change the Map Point Tool icon (#113)
pull request waiting #114https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Esri_coordinate-2Dconversion-2Daddin-2Ddotnet_pull_114&d=CwMCaQ&c=n6-cguzQvX_tUIrZOS_4Og&r=Be2h-b6W7qMAPj_wHL8K1A&m=ruUYTgmrvoOBTLO1g4s0JhRJxnu6hTeJYFdyPu3RmAg&s=AoSjoZtytIPMvzKaEdltY_ix_y3WhCWw39_xRPkgEpY&e=
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Esri_coordinate-2Dconversion-2Daddin-2Ddotnet_issues_113-23issuecomment-2D223574766&d=CwMCaQ&c=n6-cguzQvX_tUIrZOS_4Og&r=Be2h-b6W7qMAPj_wHL8K1A&m=ruUYTgmrvoOBTLO1g4s0JhRJxnu6hTeJYFdyPu3RmAg&s=mVhvaERXr-IDxR6jCWAJ1-GosDSegZSO6oW4LlU61D8&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe_ANCBIu41-2DWjqEK48wHOW7VdqVMmHoONeks5qICgqgaJpZM4IsPBy&d=CwMCaQ&c=n6-cguzQvX_tUIrZOS_4Og&r=Be2h-b6W7qMAPj_wHL8K1A&m=ruUYTgmrvoOBTLO1g4s0JhRJxnu6hTeJYFdyPu3RmAg&s=Htz15lzNmxIAufoDjeE9a7tDVSmu6cfURObC9pd8JYE&e=.

addressed in #114, verify and close

No one verified, closing


failed to download Data migration tool

Module: 03 Explore non-relational data in Azure
Lab: 04 Upload, download, and query data in a non-relational data store
Task: 00 Manage Azure Cosmos DB
Step: 00 Load data using the Cosmos DB Data Migration tool
Description of issue
While trying to download datamigration tool, URL is not working
https://cosmosdbtools.blob.core.windows.net/datamigrationtool/2019.09.23-1.8.3/dt1.8.3.zip
Couldn't find this tool in any other sites

We are removing references to this tool for the time being.


Cannot Launch App

Steps to reproduce:
OS: Mac OS X

Download application

Open terminal

npm install

npm start

Electron opens, but the application fails to boot. It just loads a blank grey background.

Since you're using an unix system, try sudo npm install

OS : Mac OSX
npm : 5.6.0
node : 8.5.0
I have same issue here.
It loads a blank background

Solved!
The problem was that index.html was unable to find ../dist/bundle.js
So I used webpack to generate bundle.js in dist folder.
Before launching electron, you have to build files in renderer directory.
package.json
"scripts": {     "test": "mocha --compilers js:babel-register test/test.js",     "start": "cross-env NODE_ENV=production electron .",     "dev-start": "cross-env NODE_ENV=development electron .",     "dev": "webpack-dev-server --inline --content-base ./renderer",     "build": "webpack"   },
I just add build scripts in package.json.

npm run build
npm start

Then it works!


refactor: explicit channels in conda env ymls

Hi! You may have noticed that, when creating a new conda environment from *.yml file, it takes ages to solve package dependencies.
I attempt to speed the process up by explicitly defining channel in which to search for a package. I also defined minimal pandas version to be 1.4.1 - the things were weird before that. I also allow for python versions newer than 3.7.13 and I believe you'll find it acceptable.
Please let me know if this is in any way helpful.

Hi Maciej,
Yes, I noticed that building an environment for PyPOTS does take some time. So your PR looks helpful indeed. Thank you for your idea!
But GitHub auto-testing met errors with your PR. Please check it out here.

Yeah, I noticed that so i closed the PR and am working on fixing it :)

Cool. Please reopen your PR when you think it's ready. Then we can run a test to see if your commits can speed up the process of environment building.

If the tests pass, we could probably speed it up a lot by determining possible version range per package, but I guess that would make us conda dependency resolvers :wink:

This commit works fine. You can try to specify the version of each package to see how much it can speed up. 👀

I froze the test env, each package with one version explicitly set. If the time gain is not huge I don't think it is worth testing each dependency and searching for minimal requirements.

The tests failed, i capitulate :sob:

last try with versions that conda found for me with python3.7.13

No worries. I'll give your idea a try by myself when I have time 😃. I add this idea in GitHub Discussion, you can check it out here #8
Many thanks for your suggestion and your efforts ;-)

I'm closing this PR due to the problem has been solved in the latest release v0.0.10. Please feel free to reopen it if anyone meets the same issue again.


xgboost_mnist classification example calls predict & not predict_prob

I'm trying to find a way to have the sagemaker hosted xgboost binary classification model call predict_prob as opposed to predict. Looking at the xgboost_minst example it looks like a classification model is trained but the hosted section is just getting the results from predict. Is there anyway to have a sagemaker hosted xgboost classification model call predict_prob and not predict? I even tried switching to text/x-libsvm MIME type but it still is only returning the results of calling predict on the model.

Hi @Zambonilli - XGBoost MNIST is a multiclass classification problem, and yes, the prediction result is just the class.  But, for binary classification (which it sounds like your use cases is), Sagemaker XGBoost's output is the probability.  For example, this notebook uses the prediction probabilities.

Thanks @djarpin . You're correct in that we are using a binary classifier. Oddly, our existing production python container with xgboost was using version .60 and returned different predictions when calling predict vs predict_proba. It looks like the update to Sagemaker and xgboost:latest container is using a newer version of xgboost and now return the same values from the two different methods. Thank you for your help here.


Camera Hood part

"Mushroom Pegs" on the camera hood need to be rotated and then files in hardware need to reflect change

fixed


Most Container do not handle SIGTERM

Describe the bug
While instrumenting the binaries for code coverage I noticed that some container did not provide any report (actually only pilot discovery and side car agent do) I realized that the server did not handle SIGTERM, and therefore the Test created to gather coverage could not report data.
Expected behavior
When a pod needs to be terminated, kubernetes sends a SIGTERM, which should be handle by the binary to gracefully shutdown or at least stop receiving new request. After a while a kubernetes will send a SIGKILL. Handling SIGTERM is very important for roll out and upgrade.
Steps to reproduce the bug
Start a binary and send a SIGTERM
Version
Master d836d2ffbe279cf74b38902f6f998dafafa55f4a, also present in most version before 1.0.
Is Istio Auth enabled or not?
Does not matter
Environment
Kubernetes

cc: @geeknoid we should add signal handling to Mixer.

On top, I believe that pilot should handle SIGTERM gracefully as well, especially the pilot-agent. It should gracefully shutdown all envoy proxies before exiting itself, causing a sidecar to vanish.


Update Meeting Time tests

Codecov Report

Merging #210 (b784f9c) into master (d661dd5) will increase coverage by 0.14%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #210      +/-   ##
============================================
+ Coverage     50.99%   51.14%   +0.14%
- Complexity      615      616       +1
============================================
  Files           118      118
  Lines          2706     2706
  Branches        322      322
============================================
+ Hits           1380     1384       +4
+ Misses         1227     1223       -4
  Partials         99       99

Impacted Files
Coverage Δ

.../java/seedu/address/model/meeting/MeetingTime.java
78.57% <0.00%> (+14.28%)
:arrow_up:

Continue to review full report at Codecov.

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


secretmanager.Secret.secretName translates to Fn::Split

I'm generating a secretsmanager.Secret in a seperate stack (SecretsStack) and using it in the ApiStack:
import * as secretsmanager from '@aws-cdk/aws-secretsmanager';
export class SecretsStack extends sst.Stack {
  public someSecret: secretsmanager.Secret

  constructor(scope: Construct) {
    super(scope, 'SecretsStack')

    this.someSecret = new secretsmanager.Secret(this, 'Secret')
  }
}

Then I use someSecret in the ApiStack:
    const api = new Api(this, 'SomeApi', {
      defaultFunctionProps: {
        environment: {
          SOME_SECRET_NAME: secretsStack.someSecret.secretName,
...

The generated CF looks like this:
SOME_SECRET_NAME:
  Fn::Select:
    - 6
    - Fn::Split:
      - ":"
      - Fn::ImportValue: mystage-myproject-SecretsStack:ExportsOutputRefSecretA720EF052D953DED

However, the secretName is wrong: the actual name isn't the last part of the ARN, it's shorter:
Secret name
SecretA720EF05-qXGVonf5vBIT
Secret ARN
arn:aws:secretsmanager:eu-central-1::secret:SecretA720EF05-qXGVonf5vBIT-kdVTH4

Notice the -kdVTH4 at the end.
I'm not sure if I'm doing something wrong or whether this is a bug.

I've tried to reproduce this with vanilla cdk, and this issue occurs also in<EMAIL_ADDRESS>This seems to be fixed in aws-cdk-lib@: the generated output splits on - and uses Fn::Select 0 and Fn::Select 1.
Looking forward to the v2 update!

Hey @q42jaap, we updated SST to use CDK v2 in 0.59.0, and have been iron out kinks here and there. The latest version 0.60.8 is stable.
Give that a try and please re-open this if the issue persist.


OSError and EOFError2

I learned to use your code on windows, but encountered the problem of oserror and eoferror. I checked it env.py I don't think the following paragraph is meaningful. Would you please explain the meaning of this code? Because my mother tongue is not English, can you understand what I mean??
#     for index in range(num_envs):
#
#         process = mp.Process(target=self.run, args=(index,))
#         process.start()
#
#         # self.env_conns[index].close()
#
# def run(self, index):
#
#     # self.agent_conns[index].close()
#     while True:
#
#         request, action = self.env_conns[index].recv()
#         print(request,action)
#         if request == "step":
#             self.env_conns[index].send(self.envs[index].step(action.item()))
#         elif request == "reset":
#             self.env_conns[index].send(self.envs[index].reset())
#
#         else:
#             raise NotImplementedError

我碰到了相同的问题，这两句逻辑不对，运行报错，注释掉以后又会在reset函数里出错，

I learned to use your code on windows, but encountered the problem of oserror and eoferror. I checked it env.py I don't think the following paragraph is meaningful. Would you please explain the meaning of this code? Because my mother tongue is not English, can you understand what I mean??
#     for index in range(num_envs):
#
#         process = mp.Process(target=self.run, args=(index,))
#         process.start()
#
#         # self.env_conns[index].close()
#
# def run(self, index):
#
#     # self.agent_conns[index].close()
#     while True:
#
#         request, action = self.env_conns[index].recv()
#         print(request,action)
#         if request == "step":
#             self.env_conns[index].send(self.envs[index].step(action.item()))
#         elif request == "reset":
#             self.env_conns[index].send(self.envs[index].reset())
#
#         else:
#             raise NotImplementedError

This problem does not occur when running Ubuntu, but it does on win10

我碰到了相同的问题，这两句逻辑不对，运行报错，注释掉以后又会在reset函数里出错，

I learned to use your code on windows, but encountered the problem of oserror and eoferror. I checked it env.py I don't think the following paragraph is meaningful. Would you please explain the meaning of this code? Because my mother tongue is not English, can you understand what I mean??
#     for index in range(num_envs):
#
#         process = mp.Process(target=self.run, args=(index,))
#         process.start()
#
#         # self.env_conns[index].close()
#
# def run(self, index):
#
#     # self.agent_conns[index].close()
#     while True:
#
#         request, action = self.env_conns[index].recv()
#         print(request,action)
#         if request == "step":
#             self.env_conns[index].send(self.envs[index].step(action.item()))
#         elif request == "reset":
#             self.env_conns[index].send(self.envs[index].reset())
#
#         else:
#             raise NotImplementedError

@yjh5246 @zhimakaimenxa @lvjinqiao  were you able to find any solution to this?

I figure out what the problem is in win10
first, comment this two lines in env.py,you can‘t use pipe like this in window
self.env_conns[index].close()
....
self.agent_conns[index].close()

next, in env.py
the class MultipleEnvironments create all envs in main process and try to access each single env in subprocess
but the _LIB in nes_py can't share during processes  because some share memory police in window,i guess.
so, we should create each single env in each subprocess, in function run()


Diff with master Tecsisa/constructr-consul

don't merge yet, just to see the diff

👍
But let's first see if this fork is still needed: https://github.com/wehkamp/blaze-basket-service/pull/452

closing as we're archiving this project


Q: Is there a way to make fields smaller in height?

I've searched the web and the sourcecode of fluent_ui, but haven't found an solution yet.  I would like to minimize the height of fields. Is there some generic way to do this?
Thanks.

Hello!. No, it's currently not possible. Their default height is their min height, which is 32.0

That's unfortunate... Thanks!


MAINT: improve error message in pipeline engine for misaligned dates

Coverage decreased (-0.01%) to 87.051% when pulling dd80e224b8ff4abd09691d137d15cf73afc646eb on naked-assertions-should-be-illegal into 27e6abcb3860084b5d73206ee19c62f5a862d1a5 on master.


Remove attribute when the value x is NaN

I found a un-caught exception regarding to NaN while following tutorial part 3.
The root cause of this is a parse error, and this occurs when the data file is not properly formatted.
When attempting to set attribute, we already avoid when the value x is NULL.
By removing attribute when the x is NaN, we can prevent un-handled NaN exception in browser.

I can’t see any browser exceptions when using element.setAttribute("foo", NaN).  Which browser are you using?

I have checked the exception in developer plugin in both chrome and firefox browser.
If you would like to see the exception, please set the data.tsv below and follow the instructions at http://bl.ocks.org/mbostock/3885304. "data.tsv" is expected to have "tab" as the separator, but I have used "space" instead of that, which causes parsing error and NaN exception.
letter frequency
A .08167
B .01492

OK, I see.  This is not an exception per se, but more of a warning, which is logged to the console if an invalid SVG attribute is set.  In fact, I think it’s actually a good thing, because it’s easier to figure out why things are not working.  In other words, we know that the chart is not displaying properly, because some values are NaN, which probably means a parsing issue.
The fact that null is treated specially (it means removal of attributes) doesn’t necessarily mean we should extend this special treatment to other values, such as NaN.  In fact, .attr(<name>, null) is part of the API, and I don’t think it would be sensible to make the API more complicated by making other values do the same thing.


remove default launchers

https://github.com/yahoo/android-range-seek-bar/issues/21

Thank you for submitting this pull request, however I do not see a valid CLA on file for you. Before we can merge this request please visit https://yahoocla.herokuapp.com/ and agree to the terms. Thanks! :smile:

CLA signed

CLA is valid!


Refactor default text selection range into modes for string assistance

Brings back and adds a test for the feature where by default Droplet does not select the quotes in a quoted string (or, now, regexes)

Thanks!


Support Terraform 0.14.x

I think I am hitting this bug in the modules due to the use of the dynamic providers but I cannot test to confirm since the modules do not support Terraform 0.14. Can we add support for that?
hashicorp/terraform-provider-helm#476

Sure if we are open to merge any PR TF 0.14 if you have any time on your hands. Just make sure you bump major version.

Sure if we are open to merge any PR TF 0.14 if you have any time on your hands. Just make sure you bump major version.

ALB ingress controller is deprecated, plase use https://github.com/lablabs/terraform-aws-eks-load-balancer-controller instead.


Colour spaces

Still WIP - don't merge!

I don't think I'm planning to do any more on this, so I guess that makes it ready for review.
I've rewritten the DRM stuff a bit. Previously I was duplicating the kernel enums so that I could use them directly (they don't seem to be provided to userspace). Now I'm searching for the correct enum values by matching strings - DRM does appear to provide name-to-value lookup tables. But I still don't particularly like it.

Should we submit this change now?

Well, I'm "happy enough" with it, though I can't say I love the messing around with DRM. But it would be good to commit it before we release our updated versions of everything, I think.

Done!


[BUG] Negative Spike in Lift Forces

Bug Description
Thank you for this great software. I am using it currently to analyse flapping flight with UVLM to incorporate Aeroelasticity effects. I observed an initial Negative spike in Lift Force after plotting results from Ptera. This spike makes no physical sense for a flapping wing, so I was wondering if this is a numerical issue that could potentially be solved.

Reproduction
Running the provided example
with the addition of
ps.output.plot_results_versus_time(
    show=True,
    save=True,
)

will reproduce the above results
Expected Behavior
No spike in the lift coefficient is observed in the README.
Desktop
Please complete the following information.

OS: 'Windows 10 Home'
Version: '22H2'
PteraSoftware Version : I have forked the "develop" branch, the closest release would be 3.0.1

Additional Context
A similar issue was being discussed about a year ago here #17 . I am wondering if any resolution was achieved to the same or any work is in progress. I am open to picking up some work towards this issue as I have been making myself familiar with Ptera's UVLM solver.

@MOLOCH-dev Thanks for the bug report. As you pointed out, the negative lift spike is most likely a numerical issue. The plot from the README was from an unsteady simulation of a static (non-flapping) wing. This may be the reason we don't see such a negative spike. The last time I looked into this, I hit a dead-end and, unfortunately, became sidetracked with other bugs.
However, I have a hunch about a potential culprit. During the first time step, there are a few things different from subsequent time steps:

There are no wake vortices. Normally, the rear line vortices of the ring vortices on a wing's trailing edge (red) are mostly canceled out by the front line vortices of the first row of wake ring vortices (blue).
Katz, J., & Plotkin, A. (2001). Low-speed aerodynamics (2nd ed.). Cambridge University Press. https://doi.org/10.1017/cbo9780511810329. Perhaps we should exclude the red line vortices on the initial time step?
There is no motion-velocity. During the first time step, a function calculates the velocity at each collocation point. This velocity is the sum of the freestream velocity and the velocity induced by all the vortices. However, during future time steps, the velocity calculations also include an approximate velocity due to each panel's movement, calculated by subtracting the current position from the last and dividing by the change in time. This method won't work for the first time step, but we could calculate it directly if this is causing the problem.

Please let me know if you have any luck finding the bug or need help. While I'm a bit overwhelmed with work this week, I will take a look and report back what I find!

@MOLOCH-dev Okay, I have some updates on this issue. I've ruled out the motion-induced velocity calculation as being the sole reason for this bug. This is because the negative lift spike still occurs in simulations with no motion.

Also, I found a few reference plots to compare our results against:

Katz, J., & Plotkin, A. (2001). Low-speed aerodynamics (2nd ed.). Cambridge University Press. https://doi.org/10.1017/cbo9780511810329
This case is something easily simulated in Ptera Software. The one catch is that Katz and Plotkin use a different method for calculating forces than I'm using. They use a modified version of Bernoulli's equation, whereas I use the unsteady Kutta-Joukowski equation. I've read a paper comparing the two approaches (referred to as the Katz method and the Joukowski method), and they generate extremely similar results for most converged simulations, but the transient lift might be different.
However, I also found the following plot from a paper that uses the Joukowski method:

Gao, W., Liu, Y., Li, Q., & Lu, B. (2023). Aerodynamic Modeling and Simulation of Multi-Lifting Surfaces Based on the Unsteady Vortex Lattice Method. Aerospace 2023, Vol. 10, Page 203, 10(2), 203. https://doi.org/10.3390/AEROSPACE10020203
As you can see, both examples show lift coefficients that begin at roughly positive infinity and then dip slightly lower than expected before finally asymptotically converging. This is the opposite of what we're seeing in our simulations.

@MOLOCH-dev I just created a branch ("hotfix-3.0.1") for us to work on this issue.

@MOLOCH-dev As a baseline, I created suddenly_accelerated_plate.py in a new directory, "issue testing." It runs a simulation identical to one of the simulations shown in the Katz and Plotkin figure. Here's what it looks like now:

I believe the "unsteady_near_field_forces_geometry_axes" term in the UnsteadyRingVortexLatticeMethodSolver.calculate_near_field_forces_and_moments() method has the wrong sign. It should be negative (or the order of subtraction of the circulations needs to be changed). After correcting this, the force behavior is correct as shown in the plot below that attempts to replicate the above plots. The large positive peak at the initial instant is actually the correct behavior due to the large acceleration. As the aspect ratio increases the solution converges to Wagner's analytical solution. The fact that early on the agreement with Wagner is not perfect is also expected. If anyone is interested, here is recent paper that explains why this is the case.

If the fix isn't obvious, checkout my hotfix branch.


Updating request body in Identity-verification-api Identity post request to include new mandatory fields

updated how-identity-documents-checked njk to use values expected by the identity verification api
Added additional fields expected by verification api
updated unit test

CI: No security warnings found


Ripple throws Unknown prop theme

Following the code from http://react-toolbox.com/#/components/ripple
Using:
"react": "^15.3.1",
"react-toolbox": "^1.2.1",

import Ripple from 'react-toolbox/lib/ripple';
import theme from 'react-toolbox/lib/ripple/theme';

...

    render() {

        const CustomLink = (props) => (
          <a {...props} style={{position: 'relative'}}>
            {props.children}
          </a>
        );

        const RippleLink = Ripple({spread: 3})(CustomLink);
        const RippleTest = () => <RippleLink>Test</RippleLink>;

        return <RippleTest />;
    }

The console throws the following error:
Warning: Unknown prop `theme` on <a> tag. Remove this prop from the element. For details, see https://fb.me/react-unknown-prop
    in a (created by CustomLink)
    in CustomLink (created by RippledComponent)
    in RippledComponent (created by Themed RippledComponent)
    in Themed RippledComponent (created by RippleTest)

Is there something I am missing?

The last line in the wiki: const RippleTest = () => <RippleLink href='#' theme={theme}>Test</RippleLink>;

I've tried with and without adding the theme={theme} code above since the ripple page example uses it, but the playground example doesn't. The problem persists with and without it.

This is expected behavior. The ripple HOC should always pass down a theme property because if you decorate a component that implements a ripple, the top theme should be received by the component itself. Also, it should be possible to receive the theme property in the ripple for customization purposes.
The way to avoid this is to extract the theme prop as a known prop passed by the ripple before spreading every given prop to the anchor. Consider using something like:
const CustomLink = ({ theme, ...other }) => (
  <a {...other} style={{position: 'relative'}}>
    {props.children}
  </a>
);

const RippleLink = Ripple({spread: 3})(CustomLink);
const RippleTest = () => <RippleLink>Test</RippleLink>;

I'm afraid the is no immediate solution from the lib without side effects.


Create the available open source projects feed

We include a list of cards in a web page that will have: project preview, or default image, project description, project name, button for contribution.

https://github.com/ahn-nath/thanks_for_your_contribution_to_equity/pull/16

To verify the contribution, we use: https://docs.github.com/en/rest/commits/commits#list-commits

#19


[Web][Accessibility] Actions with the OpenUrl onAction should render as an a tag

What platform is your feature request related to? (Delete other platforms).

.NET HTML
.NET WPF
Android
iOS
JavaScript
UWP

Is your feature request related to a problem? Please describe.
A European law has been passed that forces public websites to adhere to a AA accessibility rating.
Using adaptive cards prevents this.
All actions are rendered the same, as buttons.
For blind or poor sighted people who browse the web (using screen readers) this is incredibly confusing.
Describe the solution you'd like
By default, the Action.OpenUrl is rendered as an <a>-tag.
Users who rely on sight don't notice a difference.
Describe alternatives you've considered
Some rendering middleware, but could not find one that exists.

@felixvanleeuwen since version 2.3 of the JS SDK, all OpenUrl actions are rendered with the "aria-role": "link" attribute, which should be enough to satisfy the regulation. Rendering them as an <a> tag is only necessary if the proper aria-role is missing, which isn't the case.

Scrap what I wrote above. While that was true, another accessibility change has been applied on top of it that changes buttons' role to "menuitem".
We're going to have to look into this and determine what the right solution is.

Any news on this?

This issue has been fixed in #6763


Updating the Jupyter notebook version of bike tutorial

The Jupyter notebook version of bike tutorial is not up to date with the latest version of TerminusDB and Python client 😞 could you please give us a hand? 💪🏻

Install the latest versions of TerminusDB following the instructions here. You will need to have Docker. 🐳

Create a new Python environment (optional), install the Python client (pip install terminusdb-client[dataframe]) and Jupyter notebook (pip install notebook)

Referring to this code, update the code in the tutorial notebook here and make sure it works. ✅

Clear all output in the Jupyter notebook before you commit 🧽

When you make a PR, link to this issue by adding close #21  in the comment of the PR.

Hey all just to let you know I will look into this.


shape_predictor: allow dpoint as training input

Currently, the shape predictor training example showcases how to provide training and test data using integer coordinates.
Hoever, I would like to train a shape predictor using float coordinate pairs. I hope to gain increased precision by doing so. Since the shape predictor is also giving float numbers as output, I would assume that this should be possible.
However, there is no documentation to be found on the input format.
I'm happy to extend the documentation as soon as I know how this works.

This isn't supported by the current API.  There isn't any particularly good reason, it's just how the code is setup. It could use floating point coordinates.  I am somewhat skeptical that someone can label landmarks to sub-pixel accuracy though.  Do you really have a problem domain where humans, or whatever it is that generates the labels, somehow really knows the location of the landmarks to sub-pixel accuracy?

Thanks for getting back.
I am using this dataset, which supplies float coordinates. The images are quite small, therefore I assumed it might make a difference.

Were they annotated at a higher resolution and then downsampled?
In any case, if you want to put up a PR that switches the
full_object_detection to use dpoint instead of point (but in a way that's
reasonably backwards compatible so existing users are not bothered) that
would be cool with me.

Hi !
I am developing a software for which I need sub-pixel tracking with coordinates of points in float. Unfortunately the float rounding at the output of the shape predictor causes a jitter that is far too important for my needs. For the learning I have a database annotated very precisely in sub-pixel. I managed to give numpy matrices with floats as input (hoping they are not truncated internally ), but the shape predictor seems to only output integer points, contrary to the statement of "Since the shape predictor is also giving float numbers as output".
I unfortunately don't have the level in C ++ to do the modification cleanly and to offer a pool request. Does one of you two already tried to start modifying the code to allow dpoint as input to the training and as output of the predictor?
Thanks !

Yeah this would be a reasonable thing to upgrade. If someone wants to go replace point with dpoint in the right places and make any necessary attendant adjustments that would be cool.  It has to be done in a way that's backwards compatible with old code, but that shouldn't be hard though.


refactor: addead all the starlark apis

Description:

Is this change user facing?
YES/NO

References (if applicable):

Added all the Starlark commands and made the lsp consistent to our current docs;
pinned the tilt-releaser version to avoid having issues when something changes upstream;
moved lsp logic to cli/commands/lsp instead of having it as a separate module.


Admin check and GUI prompts

Added an admin check to see if the script is running with admin rights, if it isn't then it'll close and reopen with admin right and continue on with the script regardless of where it's started.
Also added a GUI to replace the need for "read-host" to get a response from USER

I did a lot.. but mostly just trimmed down a decent amount of code and added the GUI prompts.
And some more but yeah, Check it out and see if you like it, I got rid of a lot of redundant code and pushed a lot of directories into variables that are easier to use in the functions.
Tried to keep it slim but not too.. pseudo-code where it wasn't legible.  The only change that I am going to make is have it ask if you want OneDrive removed, instead of it being forced as some companies use OneDrive.


Fixed #33805 -- Made admin's many-to-many widgets do not display help text for selecting values when allow_multiple_selected is False.

The message help text will now render accordingly.

@ankurr0y Thanks for updates :+1:


fix(set millisecond):

Codecov Report

Merging #65 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master    #65   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           3      3
  Lines         172    173    +1
  Branches       26     26
=====================================
+ Hits          172    173    +1

Impacted Files
Coverage Δ

src/index.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[20.09, regression] LUKS2 password not accepted on boot

Describe the bug
I am running NixOS 20.03 with a LVM-on-LUKS setup (unencrypted boot).
After switching channel to 20.09 and rebuilding, my password is no longer accepted at boot.
When I select the last 20.03 generation from GRUB, the password is accepted and the system boots fine.
To Reproduce
Steps to reproduce the behavior:

Make 20.03-setup as above
Switch to 20.09
reboot

Expected behavior
Cryptsetup accepts password at boot and booting continues.
Additional context
I searched through release notes, issues and PRs, but found nothing related to my problem.
Notify maintainers

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
 - system: `"x86_64-linux"`
 - host os: `Linux 5.4.72, NixOS, 20.03.3191.504f993df9a (Markhor)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3.6`
 - channels(root): `"nixos-20.09.1599.d105075a1fd, mypkgs, nur, unstable-21.03pre250162.34ad166a830"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

> nix run unstable.cryptsetup -c sudo -i cryptsetup luksDump /dev/sdb2

LUKS header information
Version:       	2
Epoch:         	3
Metadata area: 	16384 [bytes]
Keyslots area: 	16744448 [bytes]
UUID:          	XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
Label:         	(no label)
Subsystem:     	(no subsystem)
Flags:       	(no flags)

Data segments:
  0: crypt
	offset: 16777216 [bytes]
	length: (whole device)
	cipher: chacha20-random
	sector: 512 [bytes]
	integrity: poly1305

Keyslots:
  0: luks2
	Key:        256 bits
	Priority:   normal
	Cipher:     aes-xts-plain64
	Cipher key: 512 bits
	PBKDF:      argon2i
	Time cost:  4
	Memory:     613056
	Threads:    4
	Salt:       XX .. XX
	AF stripes: 4000
	AF hash:    sha256
	Area offset:32768 [bytes]
	Area length:131072 [bytes]
	Digest ID:  0
Tokens:
Digests:
  0: pbkdf2
	Hash:       sha256
	Iterations: nnnnnn
	Salt:       XX .. XX
	Digest:     XX .. XX

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute: cryptsetup
# a list of nixos modules affected by the problem
module:

Do you set boot.initrd.luks.cryptoModules manually? If so try not setting it

Do you set boot.initrd.luks.cryptoModules manually? If so try not setting it

I do and unsetting didn't solve it.

Solved! I had
boot.initrd.luks.devices.enc-pv-disk.allowDiscards = true;

in my config.
Maybe related to this:
https://cdn.kernel.org/pub/linux/utils/cryptsetup/v2.3/v2.3.2-ReleaseNotes

... this option cannot be used for LUKS2 authenticated encryption (that uses dm-integrity for storing additional per-sector metadata).
At least there was a waning about DISCARD/TRIM not being usable after entering the password, thou I didn't relate this to the issue at first.

@wamserma 20.09 should be on cryptsetup 2.3.3, master is on 2.3.4.
The default kernel on 20.09 is still 5.4.x, but these release notes are about dm-integrity.
Can you copy-paste the exact error message here you get shown? That might help seeing what broke here.

@flokli Kernel: 5.4.73 #1-NixOS SMP Thu Oct 29 08:58:11 UTC 2020 x86_64 GNU/Linux (No customization.)
In stage 1 I get the prompt `Passphrase for [...]:, then after entering the passphrase:
Verifying passphrase for [...].
..Discard/TRIM is not supported.
 - failure
Passphrase for [...]:

If I disable Discard/Trim in my configuration, the fist message after Verifying is sth. like starting device mapper.

For what it's worth, I got a similar issue in the last two weeks, on the unstable channel (the bug was still on the channel yesterday): I would get messages of the form "could not load cipher" when my password was correct (and a normal rejection with an incorrect password).
Switching back to Linux 5.4 solved it (since I had deleted a few generations, that bug forced me to boot from a USB drive and reinstall NixOS). Here are the relevant lines from /etc/nixos/hardware-configuration.nix:
  boot.initrd.kernelModules = [ "nls_cp437" "vfat" "nls_iso8859_1" "xhci_pci" "ehci_pci" "ahci" "usb_storage" ];
  boot.initrd.luks.cryptoModules = [ "aes" "xts" "sha512" ];
  boot.kernelPackages = pkgs.linuxPackages_5_4;

@P-E-Meunier seems you got hit by this bug: https://github.com/NixOS/nixpkgs/issues/124902

To finally solve this (original issue): Discard/TRIM is incompatible with authenticated encryption and was silently ignored before. Upstream info: https://gitlab.com/cryptsetup/cryptsetup/-/issues/420#note_353552952
So, the warning is actually a bugfix, not a regression.


Conditioning signal in Diffusion ProjectedGAN

Great work! Thank you for sharing your code.
I have a question about Diffusion ProjectedGAN.
In Diffusion StyleGAN2 and Diffusion InsGAN, time-step information $t$ is provided to discriminators.
https://github.com/Zhendong-Wang/Diffusion-GAN/blob/05c6b0f07b855266563dc40ee97e9eaffe379932/diffusion-stylegan2/training/networks.py#L729-L732
https://github.com/Zhendong-Wang/Diffusion-GAN/blob/05c6b0f07b855266563dc40ee97e9eaffe379932/diffusion-insgen/training/networks.py#L732-L735
On the other hand, $t$ is not given to a discriminator in Diffusion ProjectedGAN, as the paper mentions in Appendix. $t$ is just used in a feature network where feature vectors are diffused.
https://github.com/Zhendong-Wang/Diffusion-GAN/blob/05c6b0f07b855266563dc40ee97e9eaffe379932/diffusion-projected-gan/pg_modules/discriminator.py#L184
I'm wondering why a discriminator in Diffusion ProjectedGAN works well without time-step information $t$. I'd appreciated it if you would give some insights.
Best regards.

Hi there, thanks for your interest and sorry for the late reply. Empirically we found the discriminator in ProjectedGAN doesn't need the $t$ as the condition. The discriminator in ProjectedGAN is different from StyleGAN2, which is light-weighed. Injection of $t$ will support our Theorem 2 but sometimes without $t$ condition, the algorithm still works.

Thank you for your reply!

Injection of $t$ will support our Theorem 2 but sometimes without condition
Yes, this is surprising to me. Now, I understand that you empirically found the algorithm works even without $t$.


Fix handling of request errors

Fixes #208.
Matches the API of http://api.jquery.com/ajaxSuccess/ and http://api.jquery.com/ajaxError/
cc @minrk

Actually, I'm going to make the internal errors throw proper IAjaxError as well.

Awesome, thanks!


Weaver as source

This adds the weaver as source,  it should fix #391
It should also fix issue #431

why did adding MIRROR as symbol definition fix this?

why did adding MIRROR as symbol definition fix this?

as the comment say,  adding a MIRROR definition causes unity to rebuild the user's dll.

what a strange coincidence.
will test.

works for me so far

merged this one: https://github.com/vis2k/Mirror/pull/437/
it would be cleaner if we keep preprocessor stuff in that preprocessor class from #437 .
perhaps just call PreprocessorDefine.AddDefineSymbols from weaver initialize again?

merged this one: #437
it would be cleaner if we keep preprocessor stuff in that preprocessor class from #437 .
perhaps just call PreprocessorDefine.AddDefineSymbols from weaver initialize again?

@vis2k  Done,  please check

looks fine. we can merge unless you want to wait for more people to test it

I did not do super extensive testing. But I was able to drop the files straight into my project. Imported without errors and the NetworkManagers acted like normal.

I think we are good to go


Torch-DirectML Layer Norm Produces Incorrect Result with Non-contiguous Input

torch-directml: 0.2.1.dev240521
python: 3.11.7
import torch
import torch_directml
from torch.nn.functional import layer_norm

device = torch_directml.device()

input = torch.randn(4, 4, 4)

weight = torch.randn(4)
bias = torch.randn(4)

cpu_output = layer_norm(input.permute(0, 2, 1), [4], weight, bias)

dml_output = layer_norm(input.to(device).permute(0, 2, 1), [4], weight.to(device), bias.to(device)).cpu()
print((cpu_output-dml_output).std().item(), (cpu_output-dml_output).abs().max().item())

0.6974620223045349 3.6198389530181885
The result isn't close to what it is on CPU or other devices.
dml_output = layer_norm(input.to(device).permute(0, 2, 1).contiguous(), [4], weight.to(device), bias.to(device)).cpu()
print((cpu_output-dml_output).std().item(), (cpu_output-dml_output).abs().max().item())

7.381072464340832e-08 2.384185791015625e-07
But it will work as expected as long as it is made contiguous.
dml_output = layer_norm(input.to(device)[::2], [4], weight.to(device), bias.to(device)).cpu()

This non-contiguous input will cause an error instead.
File "...\torch\nn\functional.py", line 2546, in layer_norm
    return torch.layer_norm(input, normalized_shape, weight, bias, eps, torch.backends.cudnn.enabled)
RuntimeError: m_device->CreateOperator(&opDesc, IID_PPV_ARGS(&op))

Hi @NullSenseStudio , thanks for your feedback. We'll be including a fix to address non-contiguous inputs in layer_norm in our upcoming torch-directml build releasing soon.

@NullSenseStudio We just released our new build that addresses the layer_norm issue. Please pip install torch-directml --upgrade to update to torch-directml 0.2.2.dev240614


Update overview.md

I found the first sentence in "### What are metrics ?" awkward especially the use of the word "mean".  Since I tripped over it I thought it was only fair to propose a small edit.

Thanks! Can you please sign the DCO?

Thanks! Can you please sign the DCO?

Hi - I'm new at this - can you point me to where I need to sign?  Thanks!

@sjnester: I'm trying to persuade the devs here to make the contribution process easier, and DCO is the thorn in the side here. See #2118.

This needs a DCO sign-off. You can use git commit -s --amend to add it.

@sjnester https://github.com/prometheus/docs/pull/2061/checks?check_run_id=4145616864 also shows a howto and links to https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally
Does that help?


[NHWC] support nhwc in ctest

This PR depend on https://github.com/ROCmSoftwarePlatform/MIOpen/pull/728
support parse argument --in_layout, --fil_layout, --out_layout to conv_2d/conv_3d driver to support different tensor layout
export MIOPEN_DEBUG_CONV_GEMM=0

./bin/test_conv2d --verbose --input 8 4 32 32 --weights 8 4 3 3 --pads_strides_dilations 1 1 1 1 1 1 --in_layout NHWC --fil_layout NHWC --out_layout NHWC
./bin/test_conv2d --verbose --input 16 128 36 36 --weights 32 128 1 1 --pads_strides_dilations 0 0 1 1 1 1 --in_layout NHWC --fil_layout NHWC --out_layout NHWC
./bin/test_conv2d --verbose --input 128 768 17 17 --weights 128 768 1 1 --pads_strides_dilations 0 0 1 1 1 1 --in_layout NHWC --fil_layout NHWC --out_layout NHWC
./bin/test_conv2d --verbose --input 128 128 35 35 --weights 128 128 3 3 --pads_strides_dilations 1 1 1 1 1 1 --in_layout NHWC --fil_layout NHWC --out_layout NHWC
./bin/test_conv2d --verbose --input 64 3 224 224 --weights 64 3 7 7 --pads_strides_dilations 3 3 2 2 1 1 --in_layout NHWC --fil_layout NHWC --out_layout NHWC
./bin/test_conv2d --verbose --input 8 512 4 4 --weights 512 16 1 1 --pads_strides_dilations 0 0 1 1 1 1 --cmode trans --pmode valid --group-count 32 --in_layout NHWC --fil_layout NHWC --out_layout NHWC

./bin/test_conv3d --verbose --conv_dim_type conv3d --input 16 32 4 9 9 --weights 64 32 3 3 3 --pads_strides_dilations 0 0 0 2 2 2 1 1 1 --in_layout NDHWC --fil_layout NDHWC --out_layout NDHWC
./bin/test_conv3d --verbose --conv_dim_type conv3d --input 16 128 4 56 56 --weights 256 4 3 3 3 --pads_strides_dilations 1 1 1 1 1 1 1 1 1 --group-count 32 --in_layout NDHWC --fil_layout NDHWC --out_layout NDHWC
./bin/test_conv3d --verbose --conv_dim_type conv3d --input 16 64 3 4 4 --weights 64 32 1 3 3 --pads_strides_dilations 0 0 0 1 2 3 1 2 3 --trans_output_pads 0 0 0 --group-count 4 --cmode trans --pmode default --in_layout NDHWC --fil_layout NDHWC --out_layout NDHWC

but below cases can not pass (no suitable solution)
./bin/test_conv2d --verbose --input 8 3 108 108 --weights 63 1 3 3 --pads_strides_dilations 1 1 1 1 1 1 --group-count 3  --in_layout NHWC --fil_layout NHWC --out_layout NHWC
./bin/test_conv3d --verbose --conv_dim_type conv3d --input 4 4 4 161 700 --weights 32 1 3 5 20 --pads_strides_dilations 1 1 1 2 2 2 1 1 1 --group-count 4 --in_layout NDHWC --fil_layout NDHWC --out_layout NDHWC

The reason is not because of this PR, but because a bug in TensorDescriptor::GetLayout().
Issue is created for this problem: https://github.com/ROCmSoftwarePlatform/MIOpen/issues/767

I worked out a heuristic such that it:

Do a depth first search to generate all possible layout
Examine every possible layout by checking if dimension generated strides can match the source stride. This way we can eliminate the "wrong" ambiguous results. Refer to the example above, only 2 out of 6 are valid cases.
Pick "NCHW" if it exists in possible results. Otherwise, pick "NHWC". Or else, pick the first possible layout. In the above example, NHWC will be picked because it has higher priority over the 2 valid cases.

The minimized example is here.

Please note, this is untested in miopen scope yet.

OK to run conv_2d/3d with C=1 test (in above description) and verified in miopen log that it peek NHWC/NDHWC naive kernel successfully.

@carlushuang This PR is still quite important to unblock rest of the changes needed for June Demo. Just want to make sure we are on the same page:

Do you have other changes to make in this PR or this is almost ready?
Do you find any bug in existing implementation of the heuristic, or have any thoughts between me/ @pfultz2 comments?

@jerryyin this PR is ready and no further changes. I'm relaunching https://github.com/ROCmSoftwarePlatform/MIOpen/pull/728 CI and hopefully if passed & merged this PR can remove draft label. Current the layout implementation is fine for this PR and other comments please see above conversation

@carlushuang Please merge from recent develop, assign urgency (and maybe other) labels, and assign reviewers. Thanks.

@atamazov Technically this PR is in my plate right now because @carlushuang has done all he has to do. I'm taking over to address all layout related problems.
The conflict is less concerning to me. Once I reached on the same page with the right way to implement layout heuristic, I will do a clean up, merge from develop. Then give @carlushuang back control.

Please merge from recent develop. Each push to this branch leads to waste of CI resources -- it builds obsolete dockers.

@carlushuang With latest commits I believe my job related with ambiguous layout is done in this PR. Sorry for flooding the PR with not the most relevant information to you. Could you take over the ownership of this PR from this point on (including formatting changes or reviewers' request on my commits)? If you find any further problem related with layouts please let me know. Thank you!

@jerryyin OK, thanks for your work in this PR, let me take over the left part and make this PR ready

Merged https://github.com/ROCmSoftwarePlatform/MIOpen/pull/806 https://github.com/ROCmSoftwarePlatform/MIOpen/pull/808

@jerryyin @atamazov @pfultz2 please help review this PR and if anything further need changed.

merged https://github.com/ROCmSoftwarePlatform/MIOpen/pull/814

Hi @atamazov please help check the review fix again. I've changed all the code according to review.

@DrizztDoUrden This looks good, and I am going to merge it now. But please have a look. Perhaps you'll have some ideas how to improve of refactor this.


Integration setup keeps failing to connect, using Nabu Casa

No matter what I try I seem to be getting the 'Failed to connect' error
Host: https://**********************.ui.nabu.casa
Port: 8889 (Which is also added in the Baby Buddy Add-On -> Configuration -> Network section)
Path: (blank)
API Key: ************************* (Taken from the Baby Buddy instance -> User Settings)
Not sure if this is a port forwarding issue or not.  Unfortunately, networking is not my strong suit, but any help is appreciated here.  Thank you

Host should likely be a local host rather than ui.nabu.casa. For example, my Home Assistant is locally a 192.168.1.X address and add-ons would be there. Add-ons, by design, likely aren't forwarded like Nabu Casa forwards your Home Assistant local instance.

Thank you so much. This did the trick.  One thing to note if anyone else is having this problem is that after entering the host address, do not include the forward slash or it will fail to connect.


Fixed the scene editor control problem

Mitigated the problem described in issue #10. The solution works for classes outside the superclass' package.
It doesn't fix the whole issue but until I find a better solution it should be better than nothing.

FIXED IT!!! :grinning:
It took me a while to figure it out but now it displays all children that implement/extend Control/AbstractControl.

I'll look into it tomorrow after my exam.
Thank you for your work so far :)
The old PR had the issue that you could have edge cases taking multiple iterations when the order of the classes was wrong.

Hehe learning for an exam here too ;)

Well this still has the same problem:
When you have the following order:
A extends B; B extends Control however the list looks like this: A, B. Then it will process A but the list doesn't have B yet. Then it goes to B where it notices that B has a Control..
However I'll implement something based on it :)

Darn, didn't think of that... I'll try to fix it if you won't be faster.

But I can't think of a way without recursion... :(

Note that every recursion can be turned into a loop (and this is basically what my fix does).
Also Note that you didn't take care of the interfaces in your case.
But thanks for the effort anyway and good luck with your exam :)


[DO-525] Implement breadcrumbs

DO-525
define breadcrumbs and call breadcrumbs in slug.vue

Bug is not resolved

changed code , can you check again please to see if it is fixed , thanks!


Hide NCDA feature [4h]

Tasks:

Remove NCDA activities and tasks.
Hide NCDA scoreboard tab on SPV and Patient record.

Deployed to live. Closing.