Feat(eos_cli_config_gen): Global poe configuration options

Enhancement summary
Add global poe options to configure the switch behaviour for poe on reboot or interface shutdown:
Which component of AVD is impacted
eos_cli_config_gen
Use case example
Global configuration of the switch behaviour regarding poe supply for all interfaces:
poe
   reboot action maintain
   interface shutdown action power-off

Describe the solution you would like
poe:
  interface_shutdown_action: < maintain | power-off>
  reboot:
    action: < maintain | power-off>

Describe alternatives you have considered
This can be accomplished today with cvp configlet or eos_cli:.
Additional context
No response
Contributing Guide

[X] I agree to follow this project's Code of Conduct

@pvinci-arista
I have currently seen your partial request on this:
https://github.com/aristanetworks/ansible-avd/issues/2611
Should we combine both?

sure!

@pvinci-arista
Could you please review my yaml model. Which one do you prefer: yours or mine.

Yours is perfect.

LGTM. Let us know if you need any help.

Hey guys,
I'm working on #2683 and it looks like there is also a link down action.  It was pointed out that there is an optional power-off delay parameter for this action.
Leaf1(config-if-Et3)#show cli commands | grep poe
[no|default] poe [disabled]
[no|default] poe legacy detect
[no|default] poe limit ( ( class CLASS_NUM ) | ( NUM_WATTS watts ) ) [ fixed ]
[no|default] poe link down action ( maintain | ( power-off [ NUM_SECONDS seconds ] ) )
[no|default] poe negotiation lldp [disabled]
[no|default] poe pairset ( ( alternative ( a | b ) ) | 4-pair )
[no|default] poe priority PRIORITY
[no|default] poe reboot action ( maintain | power-off )
[no|default] poe shutdown action ( maintain | power-off )

Since that's the case, for consistency purposes, the interface poe data model we came up with for the poe interface actions looks like:
poe:
  reboot:
    action: [maintain, power-off]
  shutdown:
    action: [maintain, power-off]
  link_down:
    action: [maintain, power-off]
    delay: <1-86400> # with a comment that it works only for power-off

In speaking with the author of this TOI, he mentioned it's likely possible Arista adds support for configuring poe interface link down action at the global level.  Since that's the case, I think we should probably adjust the global poe data model to match the interface data model for these poe interface behaviors.
Maybe
poe:
  reboot:
    action: [maintain, power-off]
  interface_shutdown:
    action: [maintain, power-off]

Any issues with that?

@jrecchia1029 just to be clear:
The additional global commands you are suggesting are currently not available in latest EOS 4.29.2F, right?
Do you know any roadmap or timeframe with which version this commands could be available?
maybe it would be better to wait until an EOS would be GA supporting this commends.
that is my opinion.

There is no roadmap afaik but the reason for adjusting the data model now is so we would not need to modify it later down the road in the likely scenario the global command for link down action is added to EOS.

Got it!
Your suggestion looks to me.
I thought first, that you also want to add the link_down command right now. Sorry, was a missunderstanding.

Thank you both for your contributions and for your help on optimizing the data models!
I have updated the description in this issue to reflect the suggestion.


Fix #44: Rename lib1g-dev to zlib1g-dev

Fixes #44: Rename library lib1g-dev to zlib1g-dev, this is because the naming changed in linux.

@seanlip When I create a PR on this repo I cannot see assignees at the right column.


Filter button

Make the filter button the same size as the course box for both team.html and courses. html (until it is 75% on phones)

commit 171a82fcbffc3c673c87bc5d37540d6808f669f3


Proposal: Build a web interface for Ingress administration

Similar to kubernetes/dashboard to allow:

display of current configuration
add/edit/remove Ingress rule/s
show the annotations used in each Ingress
allow to add/remove annotations with drag and drop
show conflicts (you can create multiple rules for the same FQDN and path)
show errors/misconfigurations (like bad service selectors)
abstract the user of yaml/json files

It makes sense to build such app?

Are you proposing a separate app or to help out on kubernetes/dashboard development? I agree the ingress section of dashboard could use some love.

rather than using a separate app, it would be better to add support for managing ingress in the kubernetes/dashboard itself. Just my 2 cents :)

I was thinking the same thing, @bryk

@bprashanth Yep, improving ingress management in dashboard should be the way to go. We're more than happy to accept contributions in this space :)


Sample images too big

The sample images are layered behind the custom ones and they are too big for the frame.

not true


various operations fail with method not found error: 'net.sf.saxon.s9api.XdmSequenceIterator net.sf.saxon.s9api.XdmValue.iterator()'

Various operations fail with an error message similar to the one below.
Oxygen: 24.1
oxbytei: 0.17.0
The application detected an error that is not automatically handled. It is possible that this error is not critical and the application may continue to work normally but our recommendation is to report the error and restart the application. If the application has become unstable and cannot be closed normally, you can use the Force Quit button from this dialog. Be aware that by doing this you will lose all unsaved changes in the opened documents.

Here are the error details:

[ AWT-EventQueue-0 ]  -  Couldn't execute operation: 'de.wwu.scdh.oxbytei.SelectAttributeValueOperation' for action: 'Select tag' because of: 'net.sf.saxon.s9api.XdmSequenceIterator net.sf.saxon.s9api.XdmValue.iterator()'
java.lang.NoSuchMethodError: 'net.sf.saxon.s9api.XdmSequenceIterator net.sf.saxon.s9api.XdmValue.iterator()'
        at de.wwu.scdh.teilsp.extensions.AbstractLabelledEntriesX.getEntries(AbstractLabelledEntriesX.java:62)
        at de.wwu.scdh.teilsp.extensions.LabelledEntriesXSLT.getLabelledEntries(LabelledEntriesXSLT.java:178)
        at de.wwu.scdh.teilsp.ui.CheckBoxSelectDialog.doUserInteraction(CheckBoxSelectDialog.java:154)
        at de.wwu.scdh.oxbytei.SelectLabelledEntryInteraction.doUserInteraction(SelectLabelledEntryInteraction.java:321)
        at de.wwu.scdh.oxbytei.SelectAttributeValueOperation.doOperation(SelectAttributeValueOperation.java:85)
        at ro.sync.ecss.extensions.o.h(Unknown Source)
        at ro.sync.ecss.extensions.o.b(Unknown Source)
        at ro.sync.ecss.extensions.o.d(Unknown Source)
        at ro.sync.ecss.extensions.j.d(Unknown Source)
        at ro.sync.ecss.extensions.j.y(Unknown Source)
        at ro.sync.ecss.extensions.j.performAction(Unknown Source)
        at ro.sync.ecss.component.editor.y$4$1.run(Unknown Source)
        at ro.sync.ui.ve$_b.run(Unknown Source)
        at java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:318)
        at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:771)
        at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:722)
        at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:716)
        at java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
        at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:86)
        at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:741)
        at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
        at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
        at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
        at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)
        at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
        at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)

oXbytei's Java classes depend on Saxon. oXygen also depends on Saxon and every version ships with an other version of Saxon. Saxon's API evolves from major version to major version (9.x.x.x ... 12.x.x.x). That's why we offer oXbytei built (compiled) for different versions of oXygen: The builds are compiled against different versions of Saxon.
oXbytei build for oXygen 24 and 24.1 expect that Saxon 10.x (10.6) is used. You can check which version ships with your oXygen under the menu Help -> About -> Libraries.

oXygen 23, 23.1: Saxon EE 9.9.1-7
oXygen 24, 24.1: Saxon EE 10.6
oXygen 25, 25.1: Saxon EE 11.2
oXygen 26+: Saxon EE 12.3

In the case reported, it was an installation of oXygen 24.1, but it used Saxon EE 9.9.x. So the installed build of oXbytei was compiled against an other version of Saxon than the one in use.
Uninstalling oXygen and re-installing oXygen 24.1 as shipped in the software archive solved the issue.


Updated Datafaker?

Hi there,
My name is Erik Pragt, and I'm one of the maintainers of Datafaker. Thanks for adding our library into this IntelliJ plugin, I had no idea about this, and this is so great, thank you for that!
I saw you are using a somewhat older version of Datafaker (1.2.0), and we're about to release a new version (1.7.0).
Would you be interested in a PR which updates to the latest version of Datafaker?
Cheers,
Erik

Hi @bodiam!
Sure, feel free to add a PR with datafaker version update. When do you plan to release 1.7.0 version?
Thanks,
Michał

Great, and thanks for your reaction!
The plan is soon, hopefully within a week.

Any news on this?

Hey @bodiam @xVemu new version will be released this week!

Great! Just keep in mind that Datafaker 2.x is now a Java 17 library, I'm not sure if that's an issue or not.

Hi @bodiam,
I'm trying to update datafaker version to 1.9.0 (Java 8 is limiting here) but I'm having some weird issue. I can get plugin running with v1.6.0 but 1.7.0 onwards is not displaying Faker in context menu. Is there anything in my code that has to be adjusted to get it working with 1.9.0? Here's main code:
link
Thanks!

Hi @tigersoftdev , that's a bit hard to say, I can't easily run that code since it's so integrated in the IntelliJ framework, but what I expect is the plugin isn't properly dealing with the new interfaces.
If you look at this:
https://github.com/datafaker-net/datafaker/blob/v1.6.0/src/main/java/net/datafaker/Faker.java
vs this:
https://github.com/datafaker-net/datafaker/blob/v1.7.0/src/main/java/net/datafaker/Faker.java
You can see that all of functionality has moved to the super interfaces, instead of being in Faker itself, so my guess is that this line is failing:
https://github.com/tigersoftdev/faker-intellij-plugin/blob/master/src/main/java/pl/tigersoft/intellij/faker/actions/FakerActionGroup.java#L40
Here you are using getDeclaredMethods, while I think you should be using getMethods instead. Also, the .instance() method of Faker has been removed; instead you can create a new instance of Faker, it's no longer expensive to instantiate a Faker object.
Hope that helps!

Btw, IntelliJ seems to be using Java 17 these days: Runtime version: 17.0.9+7-b1087.7 aarch64
Any reason why you want to stay at Java 8?

Hi @tigersoftdev , I've created a PR for this change here: https://github.com/tigersoftdev/faker-intellij-plugin/pull/13
It's not perfect, I had to disable the changelog and publish plugin, but it's now working for the latest IntelliJ version (I'd recommend using 2022.2 as the lowest minimal version, since that's the first Java 17 version, as indicated here: https://plugins.jetbrains.com/docs/intellij/build-number-ranges.html#platformVersions)
I hope you can finish this PR, and publish a new version. I've tried it, and it works fine:

Hi @bodiam
Thank you for your help and PR, I'm gonna review it shortly and try to release updated version of the plugin.
Regarding java 8 - just wanted to realease quicker with minimum effort but it looks like migration to java 17 will be necessary.

Hi @bodiam
I've decided to make this update with two phases - upgrade datafaker itself and later on bum up java version. Your PR is extremely helpful, I'm gonna use it again when upgrading java (and datafaker).
Feel free to upgrade Faker plugin to v1.3.0, it should be available for your Jet Brains IDE.
Thanks for help!


Disabling geometry buttons for read-only layers

This PR makes new geometry buttons look disabled (instead of hiding them) for read-only layers.
I've moved the is-disabled to the parent view, which requires a small change in styles & a slight change in the click handler as well.
This is how it looks like (like isVisible false)

I've updated the tests blindly because the cartodb3 tests don't run locally for me. It looks like the previous ones are broken (it expected .length 3 in both cases, which makes sense now, not before), so I don't know if my changes are correct or not.
We could add more coverage by testing the behaviour with isVisible as well, which produces the same result.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Yeah so I actually had a problem on the spec, thanks travis :heart_eyes:

Mmmm ok tests were still broken, just pushed another fix. this one should be fine I think.
I am setting the visible on each test, which should trigger a _renderContextButtons.
The tests were originally 'wrong' (always expecting 3, instead of 3 and 0) because it never re-renders, so it's always 3. Which I guess was done on purpose to keep the tests, but not break them.
Not being able to run tests locally sure is a handpicap.

Closing!


Harden Drupal version detection #545

The Problem/Issue/Bug:
Detecting the Drupal version can be weak if wrong docroot chosen.
How this PR Solves The Problem:
There must be an index.php and contain the word "Drupal", then follow structure patterns.
Manual Testing Instructions:
Automated Testing Overview:

Related Issue Link(s):
Release/Deployment notes:

Added reviewers and placed on our project board.

I'll wait for @rfay to take a first pass on code/tests before I jump in.

I'm not convinced that this adds significant value over what was there before.
We've been trying to deliberately treat d6/d7/d8 as separate things and not mix the code, so it's easier to maintain (despite some copying).

So I'm uncomfortable with this one.

@rfay  that's fine, we can close. The main thing is the index.php peek to ensure it's Drupal. That might help with other CMS support down the road. "We know that a file within X bytes will say its name"

Thanks, sorry.  But it's just a different direction than the code has been going. Thanks so much for your absolutely excellent contributions on so many fronts.


Avoid "Missing attribute: '_id'" error when using methods only or without

Force to use '_id' on method only and don't permit to remove '_id' with
method without.
Fixes #3740

Coverage increased (+0.0%) to 97.82% when pulling a808a841854ecd994965e0e420ca55ca2fa7166d on dx7:issue-3740 into cc69597eedb41e8b7e07d485f5095ae4ccbbbe22 on mongoid:master.

Coverage increased (+0.0%) to 97.82% when pulling a808a841854ecd994965e0e420ca55ca2fa7166d on dx7:issue-3740 into cc69597eedb41e8b7e07d485f5095ae4ccbbbe22 on mongoid:master.

Coverage increased (+0.0%) to 97.82% when pulling a808a841854ecd994965e0e420ca55ca2fa7166d on dx7:issue-3740 into cc69597eedb41e8b7e07d485f5095ae4ccbbbe22 on mongoid:master.

Coverage increased (+0.0%) to 97.82% when pulling a808a841854ecd994965e0e420ca55ca2fa7166d on dx7:issue-3740 into cc69597eedb41e8b7e07d485f5095ae4ccbbbe22 on mongoid:master.

Coverage increased (+0.0%) to 97.82% when pulling a808a841854ecd994965e0e420ca55ca2fa7166d on dx7:issue-3740 into cc69597eedb41e8b7e07d485f5095ae4ccbbbe22 on mongoid:master.

Coverage increased (+0.0%) to 97.82% when pulling a808a841854ecd994965e0e420ca55ca2fa7166d on dx7:issue-3740 into cc69597eedb41e8b7e07d485f5095ae4ccbbbe22 on mongoid:master.

Coverage increased (+0.0%) to 97.82% when pulling a808a841854ecd994965e0e420ca55ca2fa7166d on dx7:issue-3740 into cc69597eedb41e8b7e07d485f5095ae4ccbbbe22 on mongoid:master.

:+1:

Can you add a CHANGELOG entry for this and I will  merge.
thanks

@arthurnn Done.

thanks

Coverage increased (+0.89%) to 98.72% when pulling d873923910f5a4a419bc5a4fd4e9c7adc317e29b on dx7:issue-3740 into 70453659ca4eb26d00adc5aead28d5e6b66b21b3 on mongoid:master.

@dx7 Could you explain please what the problem was? Because now it's (almost) impossible to cover a query with mongoid


Incorrect copy in mobile pay component #183 is Fixed

Fixed the this.invoice in payment page

Thanks @harith-hacky03 ! please see my suggestion.

Yeah Completed your suggestion too. Thank you @rolznz

Hope it helps and you will merge it . Thank you

Thanks @harith-hacky03 !


Icons do not render in GNOME applications

Describe the bug
Icons won't render in GNOME applications, even though the icons are installed.
Steps To Reproduce
Steps to reproduce the behavior:

Install nixpkgs.elementary.
Execute io.elementary.calendar and observe the absence of icons.

Expected behavior
I was expecting for apps to use the installed icon library.
Screenshots

Additional context
Add any other context about the problem here.
Notify maintainers

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
    b4fa72a8bfe0% ls -a .config/plank
.  ..
b4fa72a8bfe0% nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.13.0-1021-gcp, Ubuntu, 20.04.2 LTS (Focal Fossa)`
 - multi-user?: `no`
 - sandbox: `no`
 - version: `nix-env (Nix) 2.3.16`
 - channels(runner): `"nixpkgs, nixpkgs-stable-21_11-21.11.tar.gz, nixpkgs-unstable"`
 - nixpkgs: `/home/runner/.nix-defexpr/channels/nixpkgs`

b4fa72a8bfe0% b4fa72a8bfe0% ls -a .config/plank
.  ..
b4fa72a8bfe0% nix-shell -p nix-info --run "nix-info -m"

Check that your VNC session is actual session in the eyes of systemd: loginctl. If it is, make sure systemd --user instance is running for your user (e.g. by ps aux), if it is, check dbus status: systemctl --user status dbus, it should running.

This should solve the dconf warnings. For icons themselves, you need to run gnome-settings-daemon I guess.

systemd is not running, is there a way that I could maybe kill init and start systemd as PID 1?

If you don't have systemd, you can wrap the command you start gnome with dbus-launch

E.g. if you have exec gnome-session in .xinitrc (or its alternative), you can use exec dbus-launch gnome-session

You can add dbus-uuidgen --ensure to your initscripts to generate machine-id

You can add dbus-uuidgen --ensure to your initscripts to generate machine-id

Unfortunately, I don't have root access, and my VNC server runs in a Docker container.

You can't use GNOME then, I'm afraid. It won't work correctly without dbus. You need to ask the one who has root access to do that.

You can't use GNOME then, I'm afraid. It won't work correctly without dbus. You need to ask the one who has root access to do that.

That'd be @replit , so it'd be difficult to do so. Maybe I'll try some other things.


With version 12.2, the dependencies no longer install behind corporate registry

🐞 Bug report
Command (mark with an x)

[x] new
[x] build
[x] serve
[x] test
[x] e2e
[x] generate
[x] add
[x] update
[x] lint
[x] extract-i18n
[x] run
[x] config
[x] help
[x] version
[x] doc

Is this a regression?
Yes, it works in the latest 12.1
Description
The esbuilder dependency tries to install its own dependencies in a post-install script and fails behind a corporate proxy / registry. See these (maybe related) issues: https://github.com/evanw/esbuild/issues/1382 https://github.com/evanw/esbuild/issues/1485, apparently this is correct behavior, but now it affects angular CLI as well.
🔬 Minimal Reproduction
I cannot create an online repoduction of this.
🔥 Exception or Error

><EMAIL_ADDRESS>postinstall C:\Repos\myrepo\node_modules\esbuild
> node install.js

Trying to install "esbuild-windows-64" using npm
Failed to install "esbuild-windows-64" using npm: Command failed: npm install --loglevel=error --prefer-offline --no-audit --progress=false<EMAIL_ADDRESS>npm ERR! code E401
npm ERR! Unable to authenticate, need: Basic realm="http://ourcorporateregistry", Negotiate, NTLM

npm ERR!      C:\Users\myuser\AppData\Roaming\npm-cache\_logs\2021-08-09T05_52_58_429Z-debug.log

Trying to download "https://registry.npmjs.org/esbuild-windows-64/-/esbuild-windows-64-0.12.17.tgz"
Failed to download "https://registry.npmjs.org/esbuild-windows-64/-/esbuild-windows-64-0.12.17.tgz": connect ECONNREFUSED <IP_ADDRESS>:443

🌍 Your Environment

Angular CLI: 12.2.0
Node: 12.21.0
Package Manager: npm 6.14.11
OS: win32 x64

Angular: 12.2.0
... cli, compiler, compiler-cli, core, language-service

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1202.0
@angular-devkit/build-angular   12.2.0
@angular-devkit/core            12.2.0
@angular-devkit/schematics      12.1.3
@schematics/angular             12.1.3
ng-packagr                      12.2.0
rxjs                            6.6.7
typescript                      4.3.5

Anything else relevant?
64-bit Windows 10 behind a corporate (Azure Artifacts) registry

It might be worth mentioning that we use project-level .npmrc files and that the postinstall script of esbuild tries to use the global .npmrc file (which might be the intended usage?). Anyway, current workaround is to manually copy my project-specific .npmrc file to the global location before running npm install.

I believe adding always-auth = true to your npmrc file should fix this.
Can you please try?

Yes we already have this, it really is about the fact that we use project-specific .npmrc files and that a postinstall script that just calls npm will use the global .npmrc (as described above). This is probably not something that can be fixed at Angular CLI level so I think I can better close this? It was just a very unpleasant surprise when upgrading to the new CLI. We have had similar things with other libraries trying to download packages by themselves (e.g. node-sass) but there were other workarounds for that.

Indeed, I don't see this as being actionable from our end. That said, the fact that it doesn't use the local NPMRC files seem like a different ESbuild bug.
This is caused because the CWD is changed from the project root to a temp directory, which caused the local NPMRC files not to be read by NPM/Yarn.
See: https://github.com/evanw/esbuild/blob/eb2872e1ab4ae09bef6fae71db6eb2381ede131b/lib/npm/install.ts#L178
I also suggest to subscribe to https://github.com/evanw/esbuild/issues/789

For what it's worth, we've "solved" this issue by adding a resolution replacing esbuild with the slower esbuild-wasm. I don't think npm supports this, but we use yarn which does have this capability (docs).
"resolutions": {
  // replace 0.12.17 with the version of esbuild your angular version is using
<EMAIL_ADDRESS><EMAIL_ADDRESS>}

@alan-agius4 I see that the esbuild bug you mentioned should be solved. Does that also mean that it is also solved in Angular CLI? And it is only solved in v13 then, right? I see 12.2.7 still uses a 0.12.x version of esbuild. If this is the case, would it be possible to put the fixed version in 12.2.8 (if there is still a version coming up)? Upgrading to Angular 13 is not planned soon for our company.


[WFRP4e System] GM Toolkit (WFRP4e)

The GM Toolkit "configure" buttons in the Configure Game Settings do not open anything. From: Ceodryn#2537wfrp4e: 5.0.3wfrp4e-archives1: 2.3.0wfrp4e-core: 2.3.2wfrp4e-dotr: 2.2.1wfrp4e-eis: 2.2.1wfrp4e-middenheim: 2.3.1wfrp4e-pbtt: 2.1.1wfrp4e-rnhd: 2.3.1wfrp4e-starter-set: 2.2.1wfrp4e-ua1: 2.2.1

In case anyone follows this trail ... It leads to https://github.com/Jagusti/fvtt-wfrp4e-gmtoolkit/issues/70


WM5 | Abdihamid Ali | Module HTML-CSS | Week 1

this was my first attempt to make the web page similar to the provided Wireframe picture
this comment is being edited to give the PR
Self checklist

[x]  I have committed my files and got a review to make changes using the grid layout
[x]  I have titled my PR with WM5 | Abdihamid Ali | Module HTML-CSS | Week 1
[x]  I have tested my changes and made a lot of adjustments using the concept of the CSS grid layout
[x]  My changes follow the style guide
[x]  My changes meet the requirements of this task and the reviewer's suggestions to make this project
more effective by applying what I learnt

Changelist
This is the Completed version of my wireframe project.
Questions
Ask any questions you have for your reviewer.
I'm grateful to CYF and the reviewer :pray:

this is my first attempt to make the web page similar to the provided Wireframe picture

Really good work, @AbdihamidAli . I can see you're using quite inflexible strategies in your CSS. This actually makes CSS much harder to write, and gets more and more vexing the more complicated your layout. It's also really common for beginners with CSS. We feel we are drawing on a page - this should be 200px by 400px and precisely 75px from the top left, and so on. But digital layouts are much more fluid; instead we must describe sizes in terms of their relationships and behaviours. Just like you can scale up an SVG without it going blurry, but jpegs break down.
I definitely recommend thinking and working a bit on writing flexible styles. Instead of setting everything by pixels. Always thinking this way -- in terms of maximums and minimums but never absolute values, is the absolute key to writing simple, robust CSS.
Take a look at the sample solution for this project. There are hardly any fixed values in it. Compare your solution and figure out what you can learn from the sample.

@SallyMcGrath thanks for your time and comments which I really benefited from.
I made the changes  and I'm still learning about the SVG concept this is my first time learning about this and going forward I'm surely going to apply SVG approach on the images that I'm using in my webpage
many thanks to you over and over :pray:

I think I closed my PR by accident :grimacing:


enabling git.git-signs.codeActions lead to a nil-indexing error

⚠ Please verify that this bug has NOT been reported before.

[X] I checked all existing issues and didn't find a similar issue

Description
Enabling Git's git-signs.codeActions option leads to a nil-indexing error.
i8cmp7b0zv45nfd9zr7lq4m6dpabrixs-init.vim.txt
-- SECTION: gitsigns-ca
table.insert(
  ls_sources,
  null_ls.gcode_actions.gitsigns
)

Seems like that g isn't supposed to be there. null_ls is indexed several times prior.
👟 Reproduction steps
Enable the option. I used mkDefault true, if that helps.
👀 Expected behavior
I can use code actions without my NeoVim turning minimalist.

😓 Actual Behavior
I can't use code actions without my NeoVim turning minimalist.

💻 Metadata

system: "x86_64-linux"  - host os: Linux 6.7.1, NixOS, 24.05 (Uakari), 24.05.20240210.d934204  - multi-user?: yes  - sandbox: yes  - version: nix-env (Nix) 2.18.1  - channels(root): "nixos, nixpkgs"  - nixpkgs: /home/noire/.nix-defexpr/channels/nixpkgs

📝 Relevant log output
Error detected while processing /nix/store/2wpjybh10bs5jlzkf04vlibr7cs04i0b-init.lua:
E5113: Error while calling lua chunk: /nix/store/2wpjybh10bs5jlzkf04vlibr7cs04i0b-init.lua:2: /nix/store/2wpjybh10bs5jlzkf0
4vlibr7cs04i0b-init.lua../nix/store/i8cmp7b0zv45nfd9zr7lq4m6dpabrixs-init.vim, line 1994: Vim(lua):E5108: Error executing l
ua [string ":lua"]:726: attempt to index a nil value
stack traceback:
        [string ":lua"]:726: in main chunk
        [C]: in function 'source'
        /nix/store/2wpjybh10bs5jlzkf04vlibr7cs04i0b-init.lua:2: in main chunk
stack traceback:
        [C]: in function 'source'
        /nix/store/2wpjybh10bs5jlzkf04vlibr7cs04i0b-init.lua:2: in main chunk
Press ENTER or type command to continue

Sorry for the delay, I was preoccupied with something else.
Could you see if commit 98e6782cf47ce6cb37d93c846cc2b8e4eb1c952b fixed the issue?

Works wonderfully! Thank'ya so much! :slightly_smiling_face:


[critical path] Add tolerance for negative one weight due to precision issues, improvements

What does this PR do?

Add tolerance for negative one weight due to precision issues
No need to have overlaid director exist, now just mkdir it

Before submitting

[ ] Was this discussed/approved via a Github issue? (no need for typos, doc improvements)

[x] N/A

[x] Did you write any new necessary tests?

[ ] N/A

[ ] Did you make sure to update the docs?

[x] N/A

[ ] Did you update the changelog?

[x] N/A

Codecov Report
Attention: Patch coverage is 90.00000% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 90.83%. Comparing base (9cad1f2) to head (abff786).

Files
Patch %
Lines

hta/analyzers/critical_path_analysis.py
80.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #138      +/-   ##
==========================================
+ Coverage   90.80%   90.83%   +0.02%
==========================================
  Files          52       52
  Lines        5186     5192       +6
==========================================
+ Hits         4709     4716       +7
+ Misses        477      476       -1

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


Finding Index.html

I am completely new person here nut after looking at your website (https://kubelabs.collabnix.com/) , I found a couple of things I can improve. But I am unable to find the source code for the respective webpage i.e index.html. If someone can point that out maybe I can contribute to this project

Cc @sangam14

Default.html under Layout will be the jekyll page which use markdown as index

@PratikLomte let me know if you need any help !


React to WebListener settings API changes

cc @Tratcher  - I'll create a rel/1.0.1 branch here and use that in our patch build.


stylesheet replace fails

stylesheet replace fails because href and not src is used for stylesheet tag. and there is no end tag for me. see #4

maybe the best way to solve it is by using a html parser and avoid string replacements. But i don't have the time to refactor the code in that way.

maybe the best way to solve it is by using a html parser and avoid string replacements. But i don't have the time to refactor the code in that way.

Should be resolved now in 0.5.0... see comments on PR

Should be resolved now in 0.5.0... see comments on PR


Display item quantity total

At top of screen, add a counter for the total number of items.

Commit: https://github.com/johneastman/todo/commit/d49958a99874fb2841f8bb4acdff8ac7734a6bcc


viu: add withSixel option

Description of changes
Add withSixel option for viu. Sixel support can be turned on using viu.override { withSixel = true; }.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

uwufetch
viu

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/1293


Can't process images in self-hosted

https://www.loom.com/share/243c08d2274d42f48b9abe8c3428508c

same on prod

fixed


Errors happening in other folders point to the wrong file

Describe the bug
While developing, some errors can crash the error formatted by trying to access non existing lines. This seems to happen with:

An npm package referring to a folder outside of the project
Using Tailwind + postcssnon-existing

I didn't manage to crash the server in the reproduction as it does in my dev environment but the crash happened at https://github.com/vitejs/vite/blob/1e711c0ef639511240523cb99c2bcc901b22b3e6/packages/vite/src/node/utils.ts#L250
(which is where the cannot read property 'length' of undefined happens)
Reproduction

Clone https://github.com/posva/vite-tailwind-bug-error-report
Go to project and npm i with npm 7
npm run dev
You should see an errorInternal server error: Cannot read property 'length' of undefined

Remove the whole comment in package/style.css
See the actual error is pointing to the wrong file and the line + column is just happening to also exist in the local file theme.css

System Info
System:
    OS: macOS 11.5.1
    CPU: (12) x64 Intel(R) Core(TM) i7-8700B CPU @ 3.20GHz
    Memory: 1.54 GB / 16.00 GB
    Shell: 5.8 - /usr/local/bin/zsh
  Binaries:
    Node: 16.6.1 - ~/.nvm/versions/node/v16.6.1/bin/node
    Yarn: 1.22.11 - ~/.nvm/versions/node/v16.6.1/bin/yarn
    npm: 7.20.3 - ~/.nvm/versions/node/v16.6.1/bin/npm

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

This seems to be fixed since https://github.com/vitejs/vite/pull/6293
I now get


Environment variables should be capitalized

Issue Summary
When using secrets manager like https://www.doppler.com/ the ENV variables are always enforced to be uppercase. It's always best practice to uppercase env variables to ensure compatibility across different shells.
Steps to Reproduce
Try to set uppercase env variable and it does not work.
Ghost Version
5.94
Node.js Version
20
How did you install Ghost?
Docker
Database type
MySQL 8
Browser & OS version
No response
Relevant log / error output
No response
Code of Conduct

[X] I agree to be friendly and polite to people in this repository

Hey adityapatadia, thanks for raising the issue.So that I understand your use case better, can you give an example of an env. variable that you'd like to set to uppercase?

I meant any config that can be set with ENV variable. Take this example database__connection__password. If this is uppercase, Ghost does not recognise it. Ideally it should be possible.

Got it, thank you for clarifying!

I would consider this a bug in Doppler rather than Ghost.
While it's a convention that env vars are upper case, it's not a requirement.

It's always best practice to uppercase env variables to ensure compatibility across different shells.

And this assertion is false. No common shells or tools have a problem with env vars not being upper case.
The format of Ghost environment variables serve a specific purpose to map exactly to the names of valid values in Ghost's config file.
There is already complexity in the system by supporting both the JSON config configuration and the environment variables that match exactly.
Supporting another format of environment variables adds unnecessary complexity.
I suggest filing a bug with Doppler instead. They are failing to support valid environment variables.

It's really impossible to set JSON config in container environments. ENV variables are the only problem. Anyway it's a request to consider this.

@adityapatadia
may be you can try out this in your Dockerfile
    environment:
     database__connection__host: ${DB_HOST} # Use Doppler's uppercase
     database__connection__user: ${DB_USER}

Sounds like a good idea but problem is doppler injects variables on RUN command and not before. Any idea if that would work in some way?

Hello @adityapatadia i would like to work upon this issue.Please assign it to me.

This isn't really a bug, but I do accept it would be more convenient if uppercase env vars were supported.
The full context for why it is not supported lives in the nconf repo here - essentially, their implementation causes a jump in memory usag, which needs to be solved first.
If the issue in nconf is resolved, we can update Ghost and tweak the configuration if needed to support it.
Anyone can work on this - we don't assign issues outside of our regular contributors.


GDScript 2.0: Array.pop_front() causes error when result is a freed object

Godot version
v4.0.alpha11.official.afdae67cc
System information
Linux
Issue description
Array.pop_front() raises the error Got a freed object as result of the call. when the result is a freed object, pausing project execution. This doesn't happen if the result is discarded or if the array is explicitly/implicitly typed.
Probably affects at least pop_back() and pop_at() as well.
Steps to reproduce
Create a node with the following script and at least 1 child.
extends Node2D

func _ready():
	var children = get_children() # returns an array
	children[0].free()
	var freed = children.pop_front() # this line errors out during runtime

Minimal reproduction project
No response

The error is not specific to Array functions, it happens for all calls where the return value is not discarded (when debug is enabled).
func f():
	var o = MyClass.new()
	o.free()
	return o

func _ready() -> void:
	var t = f()

With a typed Array, it uses an optimized version of function call which apparently doesn't check for this. So, the bug in this issue seems to be the check not happening for typed Arrays.

Should be already fixed by #76483. At least the snippet does not reproduce the error anymore.

Closing as per @vonagam's comment.


Evm debugging

Describe your changes and provide context
Testing performed to validate your change

turned out to be a bug in the evm test itself


Doubt in getting pretrained word embeddings

from where I can get this pretrained vectors?

WordEmbeddings/cnn-dailymail_doc-highlights-title-image_Org.txt.word2vec.vec
2.WordEmbeddings/cnn-dailymail_doc-highlights-title-image_Anonymized.txt.word2vec.vec

Hi Riddhi,
Please find our preprocessed input here.
http://kinloch.inf.ed.ac.uk/public/sidenet-cnn-inputs.tar.gz
Hope this helps,
Shashi


Pics Links

These links have no associated Picture

[x] Liam
[x] Emily
[x] Ethan
[x] Isabella
[x] Noah

shouldve auto closed this


Multiple input paths for BTC

Hey
It is possible to finalize the signing of a transaction for BTC for several utxos with their own paths?

Hello, can you explain a little bit what you mean by their own paths.

Thanks, I've already fixed it


Add example on how to use with @vue/composition-api

What problem does this feature solve?
I've recently started a Nuxt project, and as an answer to its size and complexity, I decided to use TypeScript everywhere I can - Vue, Nuxt + Nuxt runtime, and Vuex.
After going through a lot of documentation, it seems Vue Composition API - https://vue-composition-api-rfc.netlify.com/ - will become the de-facto way to create components in Vue 3.x, and is the best way to create components with native type inference.
Using https://github.com/vuejs/composition-api we can use the Composition API with Vue 2.x, and we should: as it's the way to go with the upcoming major release, it seems much more sensible to use this instead of the Class API - which is based on decorators, and thus will not be more supported in Vue 3.x - or the Options API which has a lot of flaws, particularly regarding type inference.
But I'm really having a hard time understanding if - and how - we can use Nuxt page lifecycle - say, asyncData - in the "mental framework" that the Composition API provides.
I'm currently using createComponent, and use both asyncData and setup top-level object properties, but that's almost an anti-pattern to the Composition API.
The example in https://typescript.nuxtjs.org/examples/composition-api/minimal.html, while a great initiative, is actually useless: we only see a tiny part of the API, and nothing specific to Nuxt :/
An example if it's compatible - or a disclaimer to tell people that Nuxt is not compatible with this API yet - would be great.
What does the proposed changes look like?
A new example with the composition API, showing how to use the Nuxt lifecycle methods (asyncData, fetch, validate, head....)

This feature request is available on Nuxt community (#c9865)

Hello, IM curious about the same

Looking forward to some information about this as well!

Please note that the Composition API is a major feature of Vue v3 which is still in pre-alpha state. Its probably safe to say that there won't be any official Nuxt.js documentation about it until Vue v3 is at least in beta state but maybe not even until v3 stable has been released.
That said, we welcome all early adopters to share their experiences in this topic.

Ok, i'm gonna create a non-profit web brand with Nuxt, using Typescript, Composition API & GraphQL.
I'll let you know any progress.

@reilue thanks, good luck with that!

@pimlie you're right BUT many library authors are already rewriting their solutions to composition API (not to look far vuelidate). People are just using better API and making their software future-proof. By not supporting current Composition API plugin NUXT is cutting itself off from every modern solution that will use it.

@filrak Indeed we will vue roadmap to have the best support for composition API out of the box. The vue2 plugin currently lacks SSR support (vuejs/composition-api#80)
Agree, we should have at least a community module for it and some examples. But still not recommended for everyday use until we test it enough :)

@pi0 I just came across the same PR, saved my day ^^
Also 100% agree with you. I believe most of new Vue projects right now will choose composition API over old one either to be more future-proof or just because it's better than previous composition options. It would be great if you make Nuxt a good environment for such projects. Are there any plans for such module already?

@filrak Yep. Actually, this module does nothing than just registring composition-api plugin. More for making it more official and accessible, and providing examples, docs, tips, etc. We also already have typescript support.
Re SSR, it is under question. runtimeContext depends on a global reference. We need to ensure no context sharing will happen when making concurrent requests.

@pi0 good to know this topic and moreover SSR support is given the attention it deserves!
I'd like to help but unfortunately that's above my TS skillset for now.
I'd be happy to help write some examples when Nuxt starts providing composition-api-ready lifecycle hooks though.
Should this issue stay opened until the Composition API PR makes it?

I think we can solve this issue via creating asyncProp function which does same logic with asyncData and merges returning object into props. Because we cannot access this.data in setup function.
Inspired from getInitialProps in next.js. :)

Here: https://typescript.nuxtjs.org/

As an example, I started to rebuild my portfolio page with the composition API ☺
Code is Open Source!

Ok, i could develop and deploy the non-profit web app, that i mention early, Peace Builder South Africa  using Nuxt, GraphQL, Apollo and Typescript.
I see the potential benefits and disadvantages.
TL:DR; Benefits: make the web software development a walk on a sunny day.
TL:DR; Disadvantages: (to me, so far) can't use Ref. I would like to know any alternative strategic for this ;)
I'm guilty by not use Typescript due legacy JS plugins that i've to used (as you can see, client's choose the template, and i didn't, guilty again, use some modern vue plugins, due matter of time and because 🇻🇪, next time i'll definitely use vue plugins ).
Also i didn't search for any tools that generate TS-Definitions from JS files.
Nevertheless i'll recommend use Composition API.
Caveats
Need generate TS Definition for legacy JS plugins

@reilue can you offer examples of what plugins don't have typings? It's not hard to add typings. I have a PR submitted for nuxt-auth right now that shows how to do it.

Also i didn't search for any tools that generate TS-Definitions from JS files.

Typescript itself does, something like tsc --declarationOnly --allowJS input.js

@surmon-china the example only uses the Composition API to add reactive data like we would have done with a data Option, still it's no help regarding how to implement Nuxt lifecycle using the composition API.
@manniL thanks for sharing, you're apparently using the same workaround as me, using the Options API for Nuxt and composition for stuff that allow using it.
So after all it still depends on https://github.com/vuejs/composition-api/pull/80 to make it to the Vue 2 plugin (or Vue 3 to be released and Nuxt to be updated to work with it but that may not be tomorrow)

https://github.com/vuejs/composition-api/pull/80 was merged :tada:
I don't know if you guys developing Nuxt already have an idea of how you're going to build it to be composition-friendly, but if you want some feedback, I think that providing a global Nuxt hook for asyncData / fetch, would be great and make it really easy to use asyncData in any component. If this is a reasonable thing to allow :sweat_smile:

I managed to run composition-api with NUXT, and it works fine with SSR.
It works on my open-source project: https://greenpress.herokuapp.com/
I found that it doesn't work well with components that uses nuxt-middleware or vuex getters.

@davidmeirlevy  where do you use the composition api in combination with asyncData or fetch. I can't seem to find it

@jessielaf i admit that to my opinion, it’s not as elegant as the nuxt middlewares, so I kept using middlewares.
Also, I’ll use the async soon to handle using vuex state inside the setup method (currently not playing together very well).

Looking forward for SSR support for @vue/composition-api 🙏

I just managed to use async state using useServerPrefetch
the example in my commit: https://github.com/greenpress/blog-front/commit/c2c8dc190f8818956a5e699c5206fc68289dabe5
previously I used nuxt-middlewares to create async calls and state change, and I set the data in vuex-store, and I managed to replace the nuxt-middlwares to compositions functions.
The only sad thing is that I couldn't use the getNamespacedState of vuex, and I can't return the result of mapState as the return of the setup function.

I found a small problem with a lack of context in the error function. Since onServerPrefetch already exists, the ability to specify the desired HTTP response for the error is required. But for the moment, it will cause an error.
import { createComponent, onServerPrefetch } from '@vue/composition-api';

export default createComponent({
	setup(props, { root }) {
		onServerPrefetch(async () => {
			await new Promise((resolve) => {
				setTimeout(resolve, 3e3);
			});

			root.nuxt.error({
				statusCode: 404,
				message: 'Not found'
			});
		});

		return {};
	}
});

The result will be:

At the moment, this can only be used like this:
root.nuxt.error.call({ nuxt: root.nuxt }, {
	statusCode: 404,
	message: 'Not found'
});

But such use is not a stable API

Looking at the latest plans for Vue 3 (including SSR and async components), it seems like a lot of Nuxt is getting built into Vue 3 itself. Is there any insight as to what this means for Nuxt in the future?

@Arcaster42 Vue 2 already supports SSR, so that isn't a change with Vue 3.
But the new features present in Vue 3 will make Nuxt even better 🙃

@Arcaster42 do you know exactly what changes Vue 3 will be making to better support SSR out of the box? Do you have any references for us?

I just managed to use async state using useServerPrefetch
the example in my commit: greenpress/blog-front@c2c8dc1

@davidmeirlevy I tried this exact approach:
// withPosts
import { computed, onServerPrefetch } from '@vue/composition-api'
import { postsStore } from '@/store'

export default () => {
  const promise = postsStore.fetchPosts

  onServerPrefetch(async () => await promise)

  return {
    posts: computed(() => postsStore.posts)
  }
}

`fetchPosts` is an async function that fetches posts and sets the state. However, it's never called during SSR. If I run it like this, posts are just never fetched. If I call `promise()` directly after `onServerPrefetch` it gets called both on SSR and client side. What am I missing?

@MarkSonn Feel free to check out Evan's talks from Vue Amsterdam 2020 and VueConf US 2020 (https://www.vuemastery.com/conferences/vueconf-us-2020/state-of-the-vuenion) ☺

So this is the best way I've found to use asyncData so far with @vue/composition-api
type Await<T> = T extends {
  then(onfulfilled?: (value: infer U) => unknown): unknown;
}
  ? U
  : T;
export function useAsyncData<T extends (...args: any) => void>(
  cb: (arg: Await<ReturnType<T>>) => void
) {
  onBeforeMount(function(this: any) {
    cb(this);
  });
}

You can then use this helper to get type safe access to the asyncData results in a callback (not immediately when setup is called, as setup isn't always called before asyncData is resolved).
function asyncData() {
  return new Promise(resolve=> {
    ... data fetching
  });
};

export default defineComponent({
  asyncData,
  setup() {
  	let data =
    useAsyncData<typeof asyncData>(data => {
      ... // can use async data results or assign to refs outside callback
    });
  }
});

let me know if anyone finds a better way as this is a bit kludgy.

I haven't tinkered with asyncData this much for now as the app I'm using the Composition API for will be deployed soon, so I need it to be quite stable.
In the meantime I've struggled pretty much to build composition "hooks" and make them work nicely with Nuxt on both server and client side, particularly when using programmatic components (with Buefy) that rely on a global Vue instance. Here's my two cents on how to use hooks while still using Nuxt's Vuex store and everything:

First, the hook:

// composable/useServices.js
/**
 * Services hook.
 *
 * @param nuxtContext
 *  Nuxt context, injected from plugin.
 * @param setupContext
 *  Optional. The component context, which is the 2nd argument of the component's `setup` function.
 *  Required only when using Buefy modal components from hooks (dialog, toast...)
 * @return Object
 */
function useServices(nuxtContext, setupContext = null) {
  const { store } = nuxtContext
  const { $api, $toast, $useAuth } = nuxtContext.app
  const { currentLocale } = nuxtContext.app.$useI18n() // Using another hook in this hook.

  // Example of generic reactive getter/setter using vuex-map-fields mutations under the hood.
  const getServiceFieldByServiceId = (field, id) => computed({
    get: () => {
      try {
        return store.getters['services/getField'](id)(field)
      } catch (e) {
        console.log(e, field)
      }
    },
    set: val => {
      return store.commit('services/updateField', {
        id,
        path: field,
        value: val,
      })
    },
  })

  // Example of using an API (previously injected as $api)
  async function fetchAll(providerId) {
    const res = await $api.get(`providers/${providerId}/services`)
    await store.dispatch('services/createMany', res)
  }

  // Example of using 2nd argument setupContext which is the 2nd argument of setup() fn.
  function deletePicture(id) {
    setupContext.root.$buefy.dialog.confirm({
      title: setupContext.root.$t('dialog.picture_delete.title'),
      message: setupContext.root.$t('dialog.picture_delete.message'),
      hasIcon: true,
      type: 'is-danger',
      async onConfirm() {
        await deleteFile(id)
      },
    })
  }
}

export default useServices

Then, inject your hooks in a plugin:

// plugins/hooks.js
import useServices from '~/composable/useServices'

export default function(context, inject) {
  // Pass Nuxt context so we get access to store etc.
  inject('useServices', setupContext => useServices(context, setupContext))

  // Make HMR work as hooks are edited quite frequently.
  if (module.hot) {
    module.hot.accept(['../composable/useServices'], () => {
       inject('useServices', setupContext => require('../composable/useServices')
        .default(context, setupContext))
    })
  }
}

Register the plugin:

// nuxt.config.js
module.exports = {
  // ...
  plugins: ['~/plugins/hooks.js'],
}

Finally in any component:

export default {
  setup({ service }, ctx) {
     // Call the hook and pass the setup context.
    const { getServiceFieldByServiceId } = ctx.root.useServices(ctx)

    return {
      // I'm using this kind of mapping a lot to keep things generic in my hooks.
      getField: field => getServiceFieldByServiceId(field, service.id),
    }
  },
}

I'm not sure why Nuxt doesn't play well when I'm using the hooks directly - probably something about the Vue global instance or so - but now that I've rewritten all my hooks this way there's not a single weird issue happening.
I know this may not help for the actual issue but this could be useful for "optimists" like me who are already using @vue/composition-api in production

I would recommend using getCurrentInstance() instead of passing context around.
For an example of using the Composition API with Nuxt SSR and serverPrefetch, see https://github.com/danielroe/vue-sanity/blob/master/src/cache.ts.

@danielroe  thanks, man!  somehow I didn't see it in the API documentation.

@danielroe very useful, seems I missed that in the docs too. Thanks!

@danielroe have you tried it with vuex?
Somehow I don’t get the vuex store on my vm instance (tried it with unit test only, not an actual component..).
Should I wait for the mounted hook?

I've just thrown together an onFetch hook to use the new Nuxt Fetch API.
An observation: setup() runs in the beforeCreated() lifecycle method, which is the same method wherein the Nuxt fetch() is set up. Sadly, this means it is not possible to access that by programmatically instantiating $options.fetch (unless @Atinux or Nuxt team would be up for moving some of the logic into created()? I'd happily create a PR if so).
However, it is possible to clone the methodology. If anyone's interested, you can find a gist here.

(unless @Atinux or Nuxt team would be up for moving some of the logic into created()? I'd happily create a PR if so).

That'd be a breaking change :/ Anyway, will pass it along.

Hi, @danielroe gist looks nice. But just as @manniL mentioned, this would be a breaking change. If it is required for hook implementation of fetch, we may make it customizable by an option :)

I've converted the gist above into a composition API module for Nuxt. Feature requests and bug reports very much welcome 😄
https://github.com/danielroe/nuxt-composition-api

I strongly recommend anyone interested in this topic to have a try at @danielroe 's module, it's evolving fast and is actually the most advanced solution I've used so far. Cheers Daniel, this was a wonderful initiative and really helps, even at a late development stage :1st_place_medal:

Module is now moved to nuxt-community. Let's move further works (for Nuxt2 support) over there:
https://github.com/nuxt-community/composition-api


build instructions in README out of date - Missing godeps?

Hi there.
It looks like the README's build instructions are out of date.  The instructions to use godep are now redundant as of ac5bea8355bf8f1620d8504265ad286e60daa9b8.
I'm a complete go noob, but I managed to get the project to build once I moved  my git clone to $HOME/go/src/twistlock-authz - only then did it pick up the vendor directory. Is this something that all golangers know?

Feel free to accept this patch :)
diff --git a/README.md b/README.md
index 877a2f1..ac1ee2a 100755
--- a/README.md
+++ b/README.md
@@ -57,12 +57,7 @@ Below are some examples for basic policy scenarios:
 ## Setting up local dev environment

   * Install [go 1.8](https://golang.org/dl/) and [docker](https://docs.docker.com/linux/step_one/).
-  * Install [godep](https://github.com/tools/godep).
-  * Clone the project.
-  * Restore go dependencies:
-```go
-  $ godep restore
-```
+  * Clone the project in to $HOME/go/src.
   * Build the binary and image:
 ```go
   $ make all


Feat/mfa

Changes for commit:
modified:   packages/itmat-commons/src/graphql/appUsers.ts
modified:   packages/itmat-commons/src/graphql/user.ts
modified:   packages/itmat-commons/src/models/user.ts
modified:   packages/itmat-interface/src/graphql/core/userCore.ts
modified:   packages/itmat-interface/src/graphql/resolvers/userResolvers.ts
modified:   packages/itmat-interface/src/graphql/schema.ts
modified:   packages/itmat-ui-react/src/components/login/login.tsx
modified:   packages/itmat-ui-react/src/components/users/userDetails.tsx

modified:   packages/itmat-utils/src/databaseSetup/collectionsAndIndexes.ts
modified:   packages/itmat-utils/src/databaseSetup/seed/users.js
modified:   packages/itmat-utils/src/models/user.ts

Untracked files:
packages/itmat-interface/src/utils/mfa.js
packages/itmat-utils/src/databaseSetup/collectionsAndIndexes.js
packages/itmat-utils/src/databaseSetup/seed/users.bak.js
yarn.lock

@nguyentb This branch is out of sync with the base develop. Also as I know that the react-script issue has been fixed in branch develop as @sou-chon push some changes, you might want to rebase you single commit directly off of there. This will avoid PR pollution with my commits which are not strictly related to the MFA 😉

Hi could you make sure the tests are passing first?

hi Chon, can you revise the pull request as I modify the tests accordingly

hi Chon, can you revise the pull request as I modify the tests accordingly

Hi, the tests are still not passing. Could you look into that?

Also I think there's a codependency issue with graphql. Some packages like ws-subscription requires graphql 14. Could you bump graphql version back to 14?

hi Chon, can you revise the pull request as I modify the tests accordingly

Hi, the tests are still not passing. Could you look into that?

Hi please get the latest version. the all tests get now passed

hi Chon, can you revise the pull request as I modify the tests accordingly

Hi, the tests are still not passing. Could you look into that?

Hi please get the latest version. the all tests get now passed

Thanks. but this PR has merge conflict. could you resolve them first

@nguyentb This branch is out of sync with the base develop. Also as I know that the react-script issue has been fixed in branch develop as @sou-chon push some changes, you might want to rebase you single commit directly off of there. This will avoid PR pollution with my commits which are not strictly related to the MFA 😉

I missed this comment :((

@nguyentb This branch is out of sync with the base develop. Also as I know that the react-script issue has been fixed in branch develop as @sou-chon push some changes, you might want to rebase you single commit directly off of there. This will avoid PR pollution with my commits which are not strictly related to the MFA 😉
I missed this comment :((

Not an issue. You can use a combination of git checkout and git rebase and some --cherry-pick to change the origin of commit e48f751 😉 .

@sou-chon @fguitton  I've already rebased the branch to merge the latest update from develop branch. All mfa-related features are now done. All test-cases are passed (132/132) Could you revise the pull request again?
Thanks :D

Hi, i know you changed the tests to fit the new functionality. but are there tests to test the OTP functions? like if the scenario where the OTP secrets are wrong


Add create_database_table to Database Table

This should allow for direct creation of a DB table based on a constructed DB query.
It should have the same API as #6326.

Clarifying the spec:
I assume the idea here is to avoid materializing the data and use an INSERT+SELECT query here.
If the target connection is different from the source, it will still fail and require explicit materialization of data (as inter-database transfer is not possible).

Yes this should be on the same backend for this ticket. If a mixed backend we should error and require the user to be explicit.
A SELECT ... INTO <New_Table> should work.


Fix wrong terminology in tvmc source

Thanks for contributing to TVM!   Please refer to guideline https://tvm.apache.org/docs/contribute/ for useful information and tips. After the pull request is submitted, please request code reviews from Reviewers by @ them in the pull request thread.

cc: @areusch

cc: @jwfromm

cc @leandron

Thanks @gromero !  Would you mind clarifying part of your comment?

... we can now pass a Runtime() object and a Executor() object

When you write Runtime() and Executor(), are you referring to actual C++/Python functions or class constructors?  Or should I read that as pseudocode that wouldn't be literally valid in TVM?

Thanks @gromero ! Would you mind clarifying part of your comment?

... we can now pass a Runtime() object and a Executor() object

When you write Runtime() and Executor(), are you referring to actual C++/Python functions or class names? Or should I read that as pseudocode that wouldn't be literally valid in TVM?

@cconvey I had the Runtime and Executor Python classes in mind yep, the ones found in the source below, which are actually  mapped to  the C++ code found in ./src, via the CFFI:
https://github.com/apache/tvm/blob/main/python/tvm/relay/backend/executor.py#L27
https://github.com/apache/tvm/blob/main/python/tvm/relay/backend/runtime.py#L27
and used, for instance, like in:
https://github.com/apache/tvm/blob/main/tests/micro/zephyr/test_zephyr_aot.py#L69-L72
But more broadly I was just saying that if I'm not mistaken in the past the concepts of runtime and executor were not as clear as they are now, back when there wasn't  the even the AOT executor and before the discussions/changes around:
https://github.com/apache/tvm/pull/9352
... and I think your patch is fixing what looks a reminiscent code of that period.

Thanks @gromero for all the background information, I find it very helpful!  AFAIK I've addressed your feedback.

@leandron It seems the CI failed due to an unrelated issue (something related to Ethos-U55 AOT tests, but I can't follow exactly what) Have you ever seen this error before? Is it known to be a flaky test? hmm just realized that @areusch seems to wresting with some ethos-u55 test in here too: https://github.com/apache/tvm/pull/10283#issuecomment-1050695312
@cconvey The CI failed but I can't see how it can be related to your change, hence while we try to understand it better could you please re-trigger the C please? (you can, for example, just do git --amend --no-edit to change the commit hash and push --force again).

@cconvey yeah i think these are the flaky ethos-u tests, can you push again? I think #10020 but unsure if there is a better bug for this particular flake

@tqchen Ready for merge


Simplify the NREL API Management for Users

Simplify the NREL API Credential Management

Proposed solution

One solution to manage this, would be to adopt a framework similar to the ECMWF ERA5 API:

user instructions, which are hopefully easier than managing user bash profiles
implementation infrastructure

Alternatives considered

Our discussion also talked about using bash profiles, but the easy flag there was this could be different depending zshell vs bash vs other, which becomes a bit of a hassle for HOPP to handle from a guidance standpoint.
Additional context

Note from Rob in a chat:
we could actually help people set their environment variables through the environment.yml
https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#setting-environment-variables


docs: add release process

I found that Chrome wouldn't let me load an extension where the version is set to something like 1.0.0-rc1, so we've come up with this thing where we'll use the patch number for release candidate builds leading up to a public release. This new document describes that.
rendered

new copy with everyone's suggestions, thanks

relevant diffs
diff --git a/docs/changelog.md b/CHANGELOG.md
similarity index 98%
rename from docs/changelog.md
rename to CHANGELOG.md
index 5211b90..c4c2e74 100644
--- a/docs/changelog.md
+++ b/CHANGELOG.md
@@ -1,4 +1,4 @@
-# Changelog
+# Change Log

 ## 1.0.0

diff --git a/README.md b/README.md
index c69b66f..72717d6 100644
--- a/README.md
+++ b/README.md
@@ -99,9 +99,18 @@ yarn test
 yarn buildProd

-## Preparing a Release
+## Preparing a Production Release Build
-Follow the applicable steps in the release process doc
+sh +VERSION=<VERSION> +rm -rf dist/ +yarn install --frozen-lockfile +yarn buildProd +zip -r oasis-wallet-$VERSION-$(git rev-parse --short HEAD).zip dist/ +
+
+If you're actually making a new release, follow the applicable steps in the
+release process doc
LICENSE
diff --git a/docs/RELEASE-PROCESS.md b/docs/release-process.md
similarity index 60%
rename from docs/RELEASE-PROCESS.md
rename to docs/release-process.md
index 2983a3d..1a562e2 100644
--- a/docs/RELEASE-PROCESS.md
+++ b/docs/release-process.md
@@ -1,7 +1,7 @@
-# Release process
+# Release Process
-## Determine the new version
-Extension versions may not have suffixes like "-rc1."
+## Determine the New Version
+Extension versions may not have suffixes like "-rc1".
We are incrementing patch versions to differentiate release candidate builds.
For example, the 1.0 release will start with a build at version 1.0.0.
@@ -10,15 +10,15 @@ If changes are needed, we move to the next build at version 1.0.1.
Version 1.0.1 is also a release candidate at first.
If no changes are needed, 1.0.1 becomes the first public release of 1.0.
-## Set the new version throughout
+## Set the New Version Throughout
You must update:
-- config.js
-- package.json
-- public/manifest.json
+- config.js
+- package.json
+- public/manifest.json
-## Add a changelog section
-Here's the changelog.
+## Add a Change Log Section
+Here's the Change Log.
If there is an "Unreleased changes" section, rename it to the new version.
Do not include a "v" prefix in the heading.
@@ -34,16 +34,16 @@ Suggested sections:
Items may include a link to GitHub issues if there is a relevant one, e.g. in bug fixes.
We especially encourage linking externally reported issues.
-If you feel like it, move one changelog item to a section on top titled "Spotlight change."
+If you feel like it, move one Change Log item to a section on top titled "Spotlight change".
-## Propose the new version
-Open a pull request (PR) for the version changes and changelog update, ideally separate from
+## Propose the New Version
+Open a pull request (PR) for the version changes and Change Log update, ideally separate from
any other changes.
When this PR gets merged into master, the chosen version permanently associated with the merge
commit.
-## Prepare an unsigned archive
+## Prepare an Unsigned Archive
Clean the output directory, build, and package:
@@ -54,29 +54,34 @@ yarn buildProd
zip -r oasis-wallet-$VERSION-$(git rev-parse --short HEAD).zip dist/

-## Add a pre-release on GitHub
+## Add a Pre-Release on GitHub
Create a tag and create a
new release on GitHub.
-TODO: standards on GitHub release title
+Enter "Oasis Wallet Release Candidate" for the title.
-Our changelog is a file under version control, so all we do is put the link in the description:
+Our Change Log is a file under version control, so all we do is put the link in the description:
-_Note: This is an internal release candidate._
+See the [Change Log](CHANGELOG.md) for what's new in this release.

-See the [changelog](docs/changelog.md) for what's new in this release.
+_Note: This is an internal release candidate._

Add the unsigned archive as an asset.
Check the box to indicate that this is a pre-release.
-## Submit crx for review
+## Submit Package for Review
-(Contact our web store account admins for this step.)
+This step is for our web store account admins.
+Contact an admin if you don't have access.
+Go to Chrome Web Store Developer Dashboard,
+browse to the Oasis Wallet item,
+select Package in the side bar and
+choose Upload new package.
-## Update GitHub pre-release
+## Update GitHub Pre-Release
Change the description:
@@ -85,3 +90,5 @@ Change the description:

Uncheck the pre-release box.
+
+Upload the artifact without the Git commit hash.

</details>

fixed missing version from release title
added a step to remove "Release Candidate" from gh rel
add a note not to add git commit hash to the unsigned archive filename


Added Unit/BoxedUnit serializers and tests

It addresses #89

It should be ready for 0.4.2 release. Do you want me to add also  the README/version changes for the release?

@luben Thanks, looks good!
And yes, if you could prepare the README/version changes for the release, it would be nice.

Updated the version. Please note that the README was also updated with information about the forthcoming 0.5.0 release based on Kryo-4.0

Thanks! Could you provide the release related changes in a separate PR? Let's not mix it with the code changes. I'm also not sure about the version.sbt change. IIRC, the release plugin updates it automatically.

Done. Moved it to a separate PR for 0.4.2 release. I have also reverted the version.sbt as you suggested. I am preparing the changes and PR for 0.5.0 based on Kryo-4.0


[Proposal] Enhancements to WindowStartupLocation

Looking for feedback if this would be wanted in Avalonia.
Is your feature request related to a problem? Please describe.
I need a way to open windows in the corner of the screen, with a margin separating them from the screen edge and taskbar.
Describe the solution you'd like
Extend WindowStartupLocation
public enum WindowStartupLocation
{
	// Existing
	Manual,
	CenterScreen,
	CenterOwner,

	// New
	TopLeft,
	TopRight,
	BottomRight,
	BottomLeft,
}

For the screen edge margin, I'd piggyback off of Layoutable.Margin (which as far as I can tell isn't used by Window currently).
I'm not sure if/how it would work with owned windows, or if it even should work with them.
Describe alternatives you've considered
I was planning to create a Window subclass for my own project, so if this is outside the scope of Avalonia itself then I'll just continue with that.
Additional context
This would likely have issues on wayland, although I haven't checked how CenterScreen works on wayland, so maybe it's no different.

For Wayland that feature won't work at all, so don't worry much about that.


[Go Live][July 08]

Push to live

Docs Build status updates of commit 1921109:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/conversation-messages.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


[Feature] Add possibility to use RangeQuery and other terms instances as value for $scoutQuery->where()

Is your feature request related to a problem? Please describe.
Problem: cannot use range condition through ->where() in scout query builder. And any other conditions except equation (ONGR\ElasticsearchDSL\Query\TermLevel\TermQuery)
It is expected that query should look like this:
Ad::search($request->keywords)
    ->when($request->minPrice || $request->maxPrice, function (ScoutBuilder $query) use ($request) {
        $params = [];
        if ($request->minPrice) {
            $params[RangeQuery::GTE] = $request->minPrice;
        }
        if ($request->maxPrice) {
            $params[RangeQuery::LTE] = $request->maxPrice;
        }
        $priceRange = new RangeQuery('price', $params);
        $query->where('price', $priceRange);
    });

Describe the solution you'd like
There is an interface ONGR\ElasticsearchDSL\BuilderInterface which is used to implement conditions like ONGR\ElasticsearchDSL\Query\TermLevel\TermQuery and ONGR\ElasticsearchDSL\Query\TermLevel\RangeQuery so we can use instances of these classes as a value for ->where() query when we need something special.
Describe alternatives you've considered
Currently to solve this task we need to use callback passed to Model::search() and do some magic which looks like overkill and also it is very complex.
Additional context
I've already tested the solution and will submit PR. It is actually very simple.

Hey @swayok and @matchish , I guess we can close the ticket :)

Yes, sure =)


Typo in generated XML report for dependency updates

The XML report for dependency updates contains typos. It would be nice to fix:

nextVersionAlailable to nextVersionAvailable
nextIncremetalAvailable to nextIncrementalAvailable

You missed the typo in nextIncremetalAvailable which should be nextIncrementalAvailable.


url caches

Hi,
There seems to be a problem with generation several links (with different transformation) on the same image (public_id). This is because they are stored in some cache variables (e.g: _private_urls).
What i'm doing right now is emptying the cache manually before I render any image but I guess this is not the best solution. Is there any other way to solve this issue?
Maybe trying to add the transformation to the key for each item stored in the cache!
Let me know what do you think.
Cheers

I hadn't thought about that but it's totally true. The reason I have them stored is to make sure they don't overflow the server with requests (since the image is signed). I just got a really good idea though! The signature only needs to be calculated when api keys and secrets change. You could instead build another similar helper that uses a stored signature to avoid hitting your server every time for the same signature. Storage of the signature could be done on the helper too, just need to break it apart a bit.

It is a good idea but wouldn't we just loose the security concept of the signature if we expose it to the client?

The only way to get real security from Cloudinary (sadly) is by purchasing their advanced plan so that only your site can make requests to their server. From my understanding, what really protects the image in the free tiers is adding a watermark to your images and serving that image with a signature. Then the original is fully private until you generate an expiring download URL.


8.x versions of modules are missing from the registry

For instance, drush extension "composer" - only the DEV version is available. Views - same story.

I look into the problem with composer soon. But i don´t understand the issue with views. Views is in D8 Core. There is not views module in contrib.

Doh, apologies - really just picked the first popular Drupal module that came to mind. panels would be a better example.

I found the problems with panels. We D8 version won´t show up because the parser throughs some errors. Becuase zhe panels repo contains a mix of D8 and D7 Modules. panels.info.yml is D8, but the submodule i18n_panels is not D8 compatibility.

It's really across the board it looks like: token, pathauto etc.

Look at the pathauto repo. The module has a d7 info file. It is not a valid d8 module

And the token dev release ia available OK Drupal packagist ...

Views: No d8 Version, moved to contrib
Composer: Fixed, https://packagist.drupal-composer.org/packages/drupal/composer
Panels: Fixed, https://packagist.drupal-composer.org/packages/drupal/panels
Pathauto: Won´t fix, the repo contains no valid [module].info.yml file
Token: is already available, https://packagist.drupal-composer.org/packages/drupal/token

@webflo thanks for fixing this!


Pb Mac OS 10.6 with Firefox et Chrome

From :Sylvain Naudin silvynATgmailDOTcom

Hi :)
I'll retry because on Gnu/Linux it doesn't work at my first try.
I use to copy/paste [[ and don't type character.. If i type it, it's working on my Fedora.

Hello,
I tried the actuel version (0.6.1) on a Mac with Firefox, Safari and
Chrome. It is working fine for me : if I type '[[', I trigger the
completion mecanism...
So I do not know what's going wrong with your setup.
Alain
On Tue, Apr 12, 2016 at 12:51 PM, Sylvain Naudin<EMAIL_ADDRESS>wrote:

Hi :)
I'll retry because on Gnu/Linux it doesn't work at my first try.
I use to copy/paste [[ and don't type character.. If i type it, it's
working on my Fedora.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/snowgoon88/TW5-extendedit/issues/5#issuecomment-208843812

You can close it @snowgoon88, like I said, I was trying with copy/paste of double brackets and typing. It doesn't work after.
But if I type Alt + Shift + ( twice, and start with existing title tiddler, I've the popup.


Avoid rebuilding the GAST on parser construction when using RULE_OVERRIDE

See comment in:
https://github.com/SAP/chevrotain/blob/13cc2eee7caa00bc8780d3a16e951e681f6515d4/src/parse/parser_public.ts#L1083

Will avoid doing "heavy duty" lifting every time a Parser using RULE_OVERRIDE is initialized.
The heavy lifting (analyzing the grammar) should only be done the first time a Parser is initialized.


How to continue to train with the saved model?

I was training the model to step 9200 but suddenly my computer stopped and restarted. How do I continue to train with the saved model.ckpt-9200 in my logdir? Tks

You can use: python train.py --help to see the help for the training. In there you will find that using the option "--logdir" you can tell the script the directory in which to store the logging information for TensorBoard. If the model already exists, it will restore the state and will continue training. There are other ways to restore a model but for me using the logdir option was the easiest.


Update jsoniter-scala-core, ... to 2.1.15

Updates

com.github.plokhotnyuk.jsoniter-scala:jsoniter-scala-core
com.github.plokhotnyuk.jsoniter-scala:jsoniter-scala-macros

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

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

labels: library-update, semver-patch

Codecov Report

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

@@          Coverage Diff           @@
##           master     #96   +/-   ##
======================================
  Coverage    0.00%   0.00%
======================================
  Files          24      24
  Lines         229     229
  Branches        7       8    +1
======================================
  Misses        229     229

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 087542a...bacbde6. Read the comment docs.


fix issue when two confirmed nodes are in the same implicit remote batch

(can trigger this against the btc room on keet now if i align the batches correctly)

ignore this, seems like the wrong solution


Enhancement: adaptations_pkg.vhd as parameter in compile script

Hello,
In uvvm_util the compile_src.do uses a fix location of the adaptations_pkg.vhd.
It would be nice, if an own adaptations_pkg.vhd can be passed as a parameter to compile_src.do. I think it would make sense regarding that this package might be project specific and located somewhere else.
For example, we integrated UVVM as a submodule in our git structure. In our project we have the custom adaptations_pkg.vhd saved. So, now we need to copy first our specific package to uvvm_util/src location and then run the compile script.
Thanks,
Jonas

Hi,
We see your point. However, in our experience most users have the UVVM library embedded (copied) in each project. In this way the requested enhancement is not required, and if there is a new project needing a newer version of UVVM, other projects will not be affected. Also, we have to prioritize other functionality already in our pipeline. Thus we cannot allocate any resources for this request. If you make the feature yourself, we would appreciate if you share it by making a pull request.
Best regards,
Arild


Transforming array inside the original resource

Hi,
I hope I can explain this right. I am building a REST API based on an industry standard which has a very deep nesting. It's a Laravel app with Model1->hasMany('Model2')->hasmany('Model3') kind of structure. This is the simplest example I could find:
array:9 [
  "id" => 2
  "created_at" => "2015-05-19 10:56:39"
  "updated_at" => "2015-05-19 10:56:39"
  "product_id" => 12901
  "title_type_id" => 2
  "value" => "01"
  "description" => "Distinctive title (book); Cover title (serial); Title on item (serial content item or reviewed resource)"
  "notes" => "The full text of the distinctive title of the item, without abbreviation or abridgement. For books, where the title alone is not distinctive, elements may be taken from a set or series title and part number etc to create a distinctive title. Where the item is an omnibus edition containing two or more works by the same author, and there is no separate combined title, a distinctive title may be constructed by concatenating the individual titles, with suitable punctuation, as in “Pride and prejudice / Sense and sensibility / Northanger Abbey”."
  "title_elements" => array:2 [
    0 => array:5 [
      "title_detail_id" => 2
      "title_text" => "Macbeth"
      "subtitle" => null
      "value" => "01"
      "description" => "Product"
    ]
    1 => array:5 [
      "title_detail_id" => 2
      "title_text" => "Shakespeare"
      "subtitle" => null
      "value" => "02"
      "description" => "Collection level"
    ]
  ]
]

I can control the top level just fine. But is there any way I could transform the array inside? In this case it is the title_elements, which comes out as is.
return [
    'value'             => $title_detail->value,
    'description'       => $title_detail->description,
    'title_elements'    => $title_detail->title_elements
];

Is this even possible or what should be the correct way to handle these deep nesting arrays so that I could still control the output with Fractal?

'title_elements' should me moved to the list of default includes on the title detail transformer. You can then specify a new collection of your title_elements to be transformed by fractal. Learn more about default includes here.

I knew about default includes before, but it did not came to my mind that I could use them for the nested structure. It actually makes sense now when I think of it. Dunno would this be worth mentioning in the documentation? But anyway thanks a lot, now I have nice looking nested output.


reverting use of the optimized isBootstrapRedeemer

A discrepancy was found on mainnet with the optimized isBootstrapRedeemer.

Let's merge this now, and can update later to try to optimise again.


Use standard C procedures for handling command-line arguments

We need replace homegrown command-line arguments parser with getopt or alike. The goal is to make xkb-switch CLI handling more standard. For example, now it doesn't process 'tightly coupled' one-letter flags, like -ld instead of -l -d. Getopt family of functions could do it.
Contributions are welcome here.

Locate the loop which parses command line arguements in XKbSwitch.cpp
Rewrite it using getopt family of C functions
Adjust linking libraries in CMakeLists.txt if required
Make sure that ./test.sh still prints OK
Send me a pull request

Please, do not introduce non-standard dependencies like boost. Use stdlib C or C++ < 11 tools.

I can try this @grwlf

I can try this @grwlf

@sonuishaq67 OK, then take it. Feel free to post questions here.

@sonuishaq67 OK, then take it. Feel free to post questions here.

I have added few words to the description

I have added few words to the description

Im using getopt3
and i have a doubt even though I specified no_argument in options
it asks for argument in small option
ex : ./xkb-switch --version works
but ./xkb-switch -v doesnt work but
gives an error of ./xkb-switch: option requires an argument -- 'v'
./xkb-switch -v. works

Im using getopt3
and i have a doubt even though I specified no_argument in options
it asks for argument in small option
ex : ./xkb-switch --version works
but ./xkb-switch -v doesnt work but
gives an error of ./xkb-switch: option requires an argument -- 'v'
./xkb-switch -v. works

How to check which test is failing ? @grwlf

How to check which test is failing ? @grwlf

@sonuishaq67 Thank you for help!

@sonuishaq67 Thank you for help!

Hi @sonuishaq67 ! I just found an issue in your implementation. Currently xkb-switch doesn't accept --arg=value format for set. So, ./xkb-switch --set=us doesn't work. But getopts's manpage says that it does support this format. This is likely because you read argument of -s from argv[i++] explicitly, while the correct way should be to use getopt-API.  I think one should try reading the values from optarg.
Could you please correct this?

Hi @sonuishaq67 ! I just found an issue in your implementation. Currently xkb-switch doesn't accept --arg=value format for set. So, ./xkb-switch --set=us doesn't work. But getopts's manpage says that it does support this format. This is likely because you read argument of -s from argv[i++] explicitly, while the correct way should be to use getopt-API.  I think one should try reading the values from optarg.
Could you please correct this?

Okay sure I'll try to correct it

Okay sure I'll try to correct it

Hey @grwlf
A few functions are not required because getopt already covers them
Should I remove those ?

Hey @grwlf
A few functions are not required because getopt already covers them
Should I remove those ?
Edit : For now I didn't remove those

Yep, I would prefer not to use temp variable, but the change is trivial so I removed it already and also made a few small adjustments. Thank you!


DEM Bathymetry Limitation:

FIM Evaluation

FIM Evaluation 2

Iowa Flood Models

change in coverage between GMS and Branch Zero

SRC Shortcomings

SRC Limitation

FIM Version 4 - GSM

Home page ideas

Synthetic Cross-section new image

SRC Adjustment

HAND Methodology fig 1:

An Issue: In GitHub wiki, how to change the order of pages?
Possible solutions:
https://stackoverflow.com/questions/39396362/github-wiki-pages-sort-order

Channel Properties:

Fig1: Hand Method

HAND SRC

Gif Test:

Target Reach

Blue background bathymetry limitation

GMS schematic:

Level Path Gif

FIM Version 4 - GSM Gif

SRC development gif

HAND Method Module V2.0 [HAND Schematic Model]


[Feature/agent_framework] Registers a single agent with multiple tools

Description
This PR has couple of new functionalities:

ToolStep for registering a tool.
RegisterAgentStep to register an agent.
Handled parsing for Number types for WorkflowNode.
Handled special case parsing for llm field

"llm": {
                        "model_id": "ldzS04kBxRPZ5cnWrqpd",
                        "parameters": {
                            "stop_when_no_tool_found": "true",
                            "max_iteration": "5"
                        }
                    }

Fixes CI for feature branch after repo name change.
Removed stale GetTask class.

TODO:

Fetch a modelId from previous step and add it in the parameter field of ToolStep.
This PR just creates a single agent. To create multiple agent and distinguish them, a nodeID should be passed with the <List<WorkflowData>> param in execute method and that nodeID can be used to store the response with the agent_id.
For the steps we are storing the modelId in response, need to attach the  nodeId to make that modelId unique in the map of WorkflowData.

Request:
{
    "name": "tool-register-agent",
    "description": "test case",
    "use_case": "REGISTER_AGENT",
    "version": {
        "template": "1.0.0",
        "compatibility": [
            "2.12.0",
            "3.0.0"
        ]
    },
    "workflows": {
        "provision": {
            "nodes": [
                {
                    "id": "workflow_step_1",
                    "type": "tool",
                    "user_inputs": {
                        "name": "MLModelTool",
                        "type": "MLModelTool",
                        "alias": "language_model_tool",
                        "description": "A general tool to answer any question. But it can't handle math problem",
                        "parameters": {
                            "model_id": "ldzS04kBxRPZ5cnWrqpd",
                            "prompt": "Answer the question as best you can.",
                            "response_filter": "choices[0].message.content"
                        }
                    }
                },
                {
                    "id": "workflow_step_2",
                    "type": "tool",
                    "user_inputs": {
                        "name": "MathTool",
                        "type": "MathTool",
                        "description": "A general tool to calculate any math problem. The action input must be valid math expression, like 2+3",
                        "parameters": {
                            "max_iteration": 5
                        }
                    }
                },
                {
                    "id": "workflow_step_3",
                    "type": "register_agent",
                    "previous_node_inputs": {
                        "workflow_step_1": "tools",
                        "workflow_step_2": "tools"
                    },
                    "user_inputs": {
                        "name": "Test_Agent_For_CoT",
                        "type": "cot",
                        "description": "this is a test agent",
                        "parameters": {"hello": "world"},
                        "llm": {
                            "model_id": "ldzS04kBxRPZ5cnWrqpd",
                            "parameters": {
                                "max_iteration": "5",
                                "stop_when_no_tool_found": "true"
                            }
                        },
                        "memory": {
                            "type": "conversation_buffer_window"
                        },
                        "app_type": "chatbot",
                        "created_time":<PHONE_NUMBER>499,
                        "last_updated_time":<PHONE_NUMBER>530
                    }
                }
            ],
            "edges": [
                {
                    "source": "workflow_step_1",
                    "dest": "workflow_step_3"
                },
                {
                    "source": "workflow_step_2",
                    "dest": "workflow_step_3"
                }
            ]
        }
    }
}

Response from the Logs:
[2023-11-26T10:19:25,300][INFO ][o.o.c.s.ClusterSettings  ] [ip-172-31-56-214] updating [plugins.flow_framework.enabled] from [false] to [true]
[2023-11-26T10:19:27,560][INFO ][o.o.f.t.CreateWorkflowTransportAction] [ip-172-31-56-214] create state workflow doc
[2023-11-26T10:19:33,327][INFO ][o.o.m.c.MLSyncUpCron     ] [ip-172-31-56-214] ML configuration already initialized, no action needed
[2023-11-26T10:19:33,427][INFO ][o.o.f.t.ProvisionWorkflowTransportAction] [ip-172-31-56-214] Queueing process [workflow_step_1]. Can start immediately!
[2023-11-26T10:19:33,427][INFO ][o.o.f.t.ProvisionWorkflowTransportAction] [ip-172-31-56-214] Queueing process [workflow_step_2]. Can start immediately!
[2023-11-26T10:19:33,427][INFO ][o.o.f.w.ProcessNode      ] [ip-172-31-56-214] Starting workflow_step_1.
[2023-11-26T10:19:33,428][INFO ][o.o.f.t.ProvisionWorkflowTransportAction] [ip-172-31-56-214] Queueing process [workflow_step_3]. Must wait for [workflow_step_1, workflow_step_2] to complete first.
[2023-11-26T10:19:33,428][INFO ][o.o.f.w.ProcessNode      ] [ip-172-31-56-214] Starting workflow_step_2.
[2023-11-26T10:19:33,429][INFO ][o.o.f.w.ProcessNode      ] [ip-172-31-56-214] Finished workflow_step_2.
[2023-11-26T10:19:33,429][INFO ][o.o.f.w.ProcessNode      ] [ip-172-31-56-214] Finished workflow_step_1.
[2023-11-26T10:19:33,429][INFO ][o.o.f.w.ProcessNode      ] [ip-172-31-56-214] Starting workflow_step_3.
[2023-11-26T10:19:33,447][INFO ][o.o.f.w.RegisterAgentStep] [ip-172-31-56-214] Remote Agent registration successful
[2023-11-26T10:19:33,448][INFO ][o.o.f.w.ProcessNode      ] [ip-172-31-56-214] Finished workflow_step_3.
[2023-11-26T10:19:33,448][INFO ][o.o.f.t.ProvisionWorkflowTransportAction] [ip-172-31-56-214] Provisioning completed successuflly for workflow CQIkC4wBYEMl9cSlJcWP
[2023-11-26T10:19:33,453][INFO ][o.o.f.t.ProvisionWorkflowTransportAction] [ip-172-31-56-214] updated workflow CQIkC4wBYEMl9cSlJcWP state to PROVISIONING

Issues Resolved
Fixes https://github.com/opensearch-project/flow-framework/issues/196
Part of https://github.com/opensearch-project/flow-framework/issues/194
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@owaiskazi19  Regarding the workflow_step_3 user inputs, why is there a separate parameters field outside of the llm field. I do not see this anywhere in the chain of thought agent documentation
"user_inputs": {
                        "name": "Test_Agent_For_CoT",
                        "type": "cot",
                        "description": "this is a test agent",
                        "parameters": {"hello": "world"},
                        "llm": {
                            "model_id": "ldzS04kBxRPZ5cnWrqpd",
                            "parameters": {
                                "max_iteration": "5",
                                "stop_when_no_tool_found": "true"
                            }
                        },
                        "memory": {
                            "type": "conversation_buffer_window"
                        },
                        "app_type": "chatbot",
                        "created_time":<PHONE_NUMBER>499,
                        "last_updated_time":<PHONE_NUMBER>530
                    }


Expose AVStream.r_frame_rate and av_guess_frame_rate()

This is continuing from #482.

Does base_frame_rate and guessed_frame_rate sound good for these two?

I think guessed_frame_rate is good:)
it's less confusing than base_frame_rate


JVM Crashes on GCTaskThread "ParGC Thread#21"

Platform:
Linux
Architecture:
2.6.32-754.10.1.el6.20190116.16.x86_64 AdoptOpenJDK/openjdk-build#1 SMP Wed Jan 16 21:27:59 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Please describe the issue that you are having with our binaries and if possible how to recreate it.
Seeing random crashes on GC thread (using Parallel GC)
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f058e5b23c0, pid=82341, tid=87535
#
# JRE version: OpenJDK Runtime Environment (13.0.1+9) (build 13.0.1+9)
# Java VM: OpenJDK 64-Bit Server VM (13.0.1+9, mixed mode, tiered, parallel gc, linux-amd64)
# Problematic frame:
# V  [libjvm.so+0xd183c0]  PSRootsClosure<false>::do_oop(oopDesc**)+0x30
#
# No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# If you would like to submit a bug report, please visit:
#   https://github.com/AdoptOpenJDK/openjdk-build/issues
#

...
Stack: [0x00007ef5c4c12000,0x00007ef5c4d12000],  sp=0x00007ef5c4d0f850,  free space=1014k
Native frames: (J=compiled Java code, A=aot compiled Java code, j=interpreted, Vv=VM code, C=native code)
V  [libjvm.so+0xd183c0]  PSRootsClosure::do_oop(oopDesc**)+0x30
V  [libjvm.so+0xc6bf0b]  OopMapSet::oops_do(frame const*, RegisterMap const*, OopClosure*)+0x2eb
V  [libjvm.so+0x765489]  frame::oops_do_internal(OopClosure*, CodeBlobClosure*, RegisterMap*, bool)+0x99
V  [libjvm.so+0xf68b17]  JavaThread::oops_do(OopClosure*, CodeBlobClosure*)+0x187
V  [libjvm.so+0xd190be]  ThreadRootsTask::do_it(GCTaskManager*, unsigned int)+0x6e
V  [libjvm.so+0x7f422b]  GCTaskThread::run()+0x1eb
V  [libjvm.so+0xf707fd]  Thread::call_run()+0x10d
V  [libjvm.so+0xc875b7]  thread_native_entry(Thread*)+0xe7
...
Threads with active compile tasks:
VM state:at safepoint (normal execution)
VM Mutex/Monitor currently owned by a thread:  ([mutex/lock_event])
[0x00007f0588015750] Threads_lock - owner thread: 0x00007f0588112800
[0x00007f0588016350] Heap_lock - owner thread: 0x00007ef4100f9000
...
Currently don't have a way to reproduce it, but from stack trace guessing it is something to do with compiler/interpreter/code blob corrupting the heap memory.
Note: This crash is observed on JVM 11.x and also in JVM 13.0.2.

hs_err_pid66684.log
hs_err_pid98684.log

@sundarms Can you try with 13.0.2 please.

I have seen the crash happening on 13.0.2 and 11.0.6

There's nothing we can do without an executable test case. Sorry.