how Integrate with llama_index?

Thank you for using the Issue submission template. Please follow the steps below to provide relevant information. We will prioritize issues with relatively complete information. Your cooperation is appreciated.
Hint: Fill in the [ ] with an x to mark it as checked. Delete any option that is not related to this issue.
Please check the following before asking

[ ] Due to frequent dependency updates, please ensure you have followed the steps in our Wiki
[ ] I have read the FAQ section AND searched for similar issues and did not find a similar problem or solution
[ ] Third-party plugin issues: e.g., llama.cpp, text-generation-webui, LlamaChat, we recommend checking the corresponding project for solutions

Choose the issue type
Base model:

[ ] LLaMA
[x] Alpaca

Issue type:

[ ] Download issue
[ ] Model conversion and merging issue
[ ] Model inference issue (🤗 transformers)
[ ]  Model quantization and deployment issue (llama.cpp, text-generation-webui, LlamaChat)
[ ] Performance issue
[x] Other issues

Describe the issue in detail
Please describe the problem you encountered as specifically as possible. This will help us locate the issue more quickly.
Provide a screenshot or log of the issue
(If necessary) Please provide a text log or screenshot to help us better understand the issue details.

Thank you for your suggestion.
We will consider the support for llama_index in our recent plan.


Vibration in local notifications

Hi
Is it possible to vibrate iphone when receiving local notification?

take a look at. https://pub.dev/packages/vibration
receiving notifications and vibrating on that event is two different topics.
p.s please use stackoverflow for development questions.

No, i am asking when we receive local notification in native application then phone vibrates but in flutter it doesn't. I am asking about that.


Rephrase title/desc without slash

This looks more natural in English.

Hi @amire80 ,
Thanks for submitting this. However, the reason the short form was chosen was because this text is on a button underneath the title and desc fields - having a long sentence might be a bit unwieldy there. We are quite new to localization; is there a convention we should use for denoting that a particular string needs to be short (for a button, etc)?

Just don't do it. Strings may have to be longer in many languages by their nature; Russian, Finnish, and Tamil are common examples. It can be a problem in English, too, because many devices may be smaller than the developer's device. Because of all this, forcing strings to be short is usually a bad idea. The right solution is to make sure that the interface element can grow with the string.
Technically, you can suggest this in the documentation (values-qq), but I strongly recommend not doing this.

The button is able to grow with the string - however, it looks better when relatively short.

If this app is supposed to be useful for people who aren't used to developers jargon, it's better to say "description" in English and not "desc".

Could "use previous title & description" work?

Yeah, that's OK in English. I can do it.

I have created https://translatewiki.net/wiki/Wikimedia:Commons-android-strings-use_previous/qqq . I guess it is acceptable to suggest, rather than to enforce, translators to use short forms, is it?

Oh, just noticed this was still in the list of PRs. There was a misunderstanding where I made the change in my fork at the same time that @amire80 modified his PR. Closing, feel free to reopen if you disagree.


training

How to train this model on my dataset???

Hello @mayanksingh1998 , have you successfully train the model on your dataset?
If yes, do you have a repo where I can find it ?

Hello @mayanksingh1998 , have you successfully train the model on your dataset?
If yes, do you have a repo where I can find it ?


ncp: Rename MAC_FILTER_MODE to MAC_PROMISCUOUS_MODE

After some internal discussion, it was decided to rename this property to
be more in line with the usage of OpenThread and 802.15.4.

Current coverage is 71.96% (diff: 0.00%)

Merging #788 into master will decrease coverage by 0.64%

@@             master       #788   diff @@
==========================================
  Files           107        106     -1
  Lines         15994      15985     -9
  Methods        2181       2177     -4
  Messages          0          0
  Branches       1901       1901
==========================================
- Hits          11612      11503   -109
- Misses         3761       3854    +93
- Partials        621        628     +7

Powered by Codecov. Last update 0754ac7...587f820


Update of odata4 support documentation to inclued an example stored …

…procedure call for odata4
inclued an example stored procedure call

Thank you.


Implement check for routing loops

This doesn't appear to be practical without more information about the network. Closing.


Func with custom gradient using tf.numpy_function/tf.py_function incompatible with tf.vectorized_map

Please make sure that this is a bug. As per our
GitHub Policy,
we only address code/doc bugs, performance issues, feature requests and
build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 20.04
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary): installed via pip
TensorFlow version (use command below): v2.7.0-rc1-69-gc256c071bb2 2.7.0
Python version: 3.8.5
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version: -
GPU model and memory: -

You can collect some of this information using our environment capture
script
You can also obtain the TensorFlow version with:

TF 1.0: python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
TF 2.0: python -c "import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)"

Describe the current behavior
When using tf.vectorized_map on a function that provides a custom gradient and the function uses either tf.numpy_function or tf.py_function, then unexpected behaviour arises:

tf.numpy_function: the gradient is a vector of zeros;
tf.py_function: UnknownError:  KeyError: b'pyfunc_12' error arises.

Describe the expected behavior
The gradient is computed without issues.
Contributing

Do you want to contribute a PR? (yes/no): no
Briefly describe your candidate solution(if contributing):

Standalone code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate
the problem. If possible, please share a link to Colab/Jupyter/any notebook.
import tensorflow as tf
import numpy as np

@tf.function
@tf.custom_gradient
def sin(x):

    # Note: change the following line to use tf.numpy_function to
    # reproduce the other issue mentioned
    res = tf.py_function(func=np.sin, inp=(x,), Tout=tf.float64)

    def grad_fn(dy):
        j = tf.cos(x)
        return dy * j

    return res, grad_fn

inputs = tf.Variable(tf.ones((10,), dtype=tf.float64))

with tf.GradientTape() as tape:
    loss = tf.reduce_sum([sin(x) for x in inputs])

print("loss:", loss)
print("gradient:", tape.gradient(loss, inputs))

with tf.GradientTape() as tape:
    loss = tf.reduce_sum(tf.vectorized_map(sin, inputs))

print("Vectorized loss:", loss)
print("Vectorized gradient:", tape.gradient(loss, inputs))

Other info / logs Include any logs or source code that would be helpful to
diagnose the problem. If including tracebacks, please include the full
traceback. Large logs and files should be attached.
Output when using
loss: tf.Tensor(8.414709848078965, shape=(), dtype=float64)
gradient: tf.Tensor(
[0.54030231 0.54030231 0.54030231 0.54030231 0.54030231 0.54030231
 0.54030231 0.54030231 0.54030231 0.54030231], shape=(10,), dtype=float64)
Vectorized loss: tf.Tensor(8.414709848078965, shape=(), dtype=float64)
Vectorized gradient: tf.Tensor([0. 0. 0. 0. 0. 0. 0. 0. 0. 0.], shape=(10,), dtype=float64)

loss: tf.Tensor(8.414709848078965, shape=(), dtype=float64)
gradient: tf.Tensor(
[0.54030231 0.54030231 0.54030231 0.54030231 0.54030231 0.54030231
 0.54030231 0.54030231 0.54030231 0.54030231], shape=(10,), dtype=float64)
Vectorized loss: tf.Tensor(8.414709848078965, shape=(), dtype=float64)

Then getting UnknownError:  KeyError: b'pyfunc_12'.
For both, a WARNING:tensorflow:Using a while_loop for converting EagerPyFunc is also emitted.

Hi @Saduf2019 ! Could you please look at this issue ? Attaching Gist in 2.6 and 2.7 for reference. Thanks!

Hi,
Thank you for opening this issue. Since this issue has been open for a long time, the code/debug information for this issue may not be relevant with the current state of the code base.
The Tensorflow team is constantly improving the framework by fixing bugs and adding new features. We suggest you try the latest TensorFlow version with the latest compatible hardware configuration which could potentially resolve the issue. If you are still facing the issue, please create a new GitHub issue with your latest findings, with all the debugging information which could help us investigate.
Please follow the release notes to stay up to date with the latest developments which are happening in the Tensorflow space.


Ring tactic

When making some theorems of my own I encountered the following goal:
⊢ t + t + 1 + (s + s + 1) = t + s + 1 + (t + s + 1)
I expected the ring tactic to solve this but it appears that ring is missing from the repository.
Would it be possible to add functionality so that the ring tactic would solve this?

It's currently not possible to import Mathlib (which contains the ring tactic) from the NNG. The reason is that the NNG would like to use some modified versions of tactics different from Mathlib (e.g. a simplified version of rw).
Here is a game that uses Mathlib: https://github.com/hhu-adam/Robo. Maybe you can start from there?
Or you could copy the entire ring tactic from Mathlib.

hey @ifarabella , I've been chatting with Kevin and I'm working today on the NNG, getting some tactics to work. Maybe we could chat on zulip to coordinate efforts

FWIW I have a branch of NNG where this goal (and even  is being solved by my variant of ac_rfl, namely simp only [add_assoc, add_left_comm, add_comm]. But this trick won't scale to multiplication.

Now, few weeks later, the NNG imports mathlib


Add missing blazorwasm options

I've noticed the blazorwasm options were missing
Also, I've noticed some issues with the CLI options and descriptions. @danroth27 @KathleenDollard who would be the right person to follow up with? I could try to put a PR to fix.
For example:

auth option doesn't list MultiOrg as a possible value, but then other options mention that auth (I'm assuming on this PR that the auth values were correct)
//// in one of the default value URLs
a few typos

@mairaw Did you want to wait for @danroth27 or is this ready to merge?

It's up to you guys! I made some assumptions re. this as I indicated in the original description, which would be nice to confirm.


Directory parser is too brittle on bad data

Problem:
The 2022-06-07 VCI Directory snapshot is malformed (strings instead of numbers, see below) for a single Issuer entry.  This causes the entire Directory load to fail despite these errors not being noted as fatal.
Desired Behavior:
An issuer entry with data format errors should cause that Issuer to be omitted and the rest of the Directory to load normally.
Steps to reproduce:
import {verify, Directory} from 'smart-health-card-decoder'

// Attempt to retrieve the 2022-06-07 snapshot
const vciDirectory = await Directory.create('https://raw.githubusercontent.com/the-commons-project/vci-directory/4501e9cab45ebf82e15f8612f91196226e524859/l\
ogs/vci_snapshot.json');
if(vciDirectory.errors) {
    console.log("errors: " + JSON.stringify(vciDirectory.errors, null, 2));
}
console.log("directory size: " + vciDirectory.export().directory.length);

Output:
errors: [
  {
    "message": "optional key.crlVersion is not a number",
    "code": 146,
    "fatal": false,
    "level": 3,
    "label": "KEY:https://www.hss.gov.nt.ca/covax"
  },
  {
    "message": "CRL.ctr must be a positive integer greater than 0 (ctr === 1)",
    "code": 140,
    "fatal": false,
    "level": 3,
    "label": "CRL"
  }
]
directory size: 0

Expected Output:
directory size: 89
Data error from 2022-06-07 load:
@@ -4742,7 +4742,7 @@
             "keys": [
                 {
                     "alg": "ES256",
-                    "crlVersion": 0,
+                    "crlVersion": "1",
                     "crv": "P-256",
                     "date":<PHONE_NUMBER>371,
                     "kid": "8C-9TNgyGuOqc-3FXyNRq6m5U9S1wyhCS1TvpgjzkoU",
@@ -4752,7 +4752,15 @@
                     "y": "_qaENBMJz6iLf1qyYMx2_D6fXxbbNoHbLcfdPF9rUI0"
                 }
             ],
-            "lastRetrieved": "2022-05-03T04:43:55Z"
+            "crls": [
+                {
+                    "ctr": "1",
+                    "kid": "8C-9TNgyGuOqc-3FXyNRq6m5U9S1wyhCS1TvpgjzkoU",
+                    "method": "rid",
+                    "rids": []
+                }
+            ],
+            "lastRetrieved": "2022-06-07T04:41:42Z"
         },
         {
             "issuer": {

thanks. I'll take a look.

I updated this with PR #17 that should fix this.
The default behavior is to now omit the invalid issuers and return an additional error showing that the issuer is being omitted.
The original idea was the 'maintained' Directories would employ their own validation and that failures were likely come from developers building smaller custom directories - so it made sense to fail the entire thing until the developer got it correct.
Thanks for the detailed issue submission.


Fix inconsistent translation key naming

Problem
Translation key names are inconsistently applied.
Sometimes we use an English phrase to repeat the exact text (which may change over time):
https://github.com/Expensify/App/blob/16942b556afe3250f06ac429b2ebebdbce2e0b8a/src/languages/en.js#L122
Other times we use a generic name or something misleading
https://github.com/Expensify/App/blob/16942b556afe3250f06ac429b2ebebdbce2e0b8a/src/languages/en.js#L139-L140
This can make it hard to provide guidance on how to label a key and lead to disagreements.
Solution
I am not too sure. But @chiragsalian had one idea about how translation keys should maybe reflect how they are used and not use short names that don't give any ideas.

Yeah, I personally don't mind if the label repeats the copy because iOUConfirmationList.whatsItFor describes the copy imo.
But welcomeText.welcome and welcomeText.welcomeBack does not describe the copy and is redundant. Its like the first words of the copy was used in the variable name rather than the parts that are relevant.
As i think about this a lot of copy is well plain text so "how they are used" might not help much (eg whatsItFor) and so instead i think we should just try to be as verbose to describe the copy as possible. Something which i think whatsItFor does fine but welcomeText.welcome or even phrase2 does not.

If we apply that verbose thinking we would end up with something like this:
welcomeText: {
  welcomeEnterPhoneOrEmailToContinue: 'Welcome to the New Expensify! Enter your phone number or email to continue.',
  moneyTalks: 'Money talks. And now that chat and payments are in one place, it\'s also easy.',
  yourPaymentsGetToYou: 'Your payments get to you as fast as you can get your point across.',
  welcomeBackEnterYourPassword: 'Welcome back to the New Expensify! Please enter your password.',
},

?
And maybe distilling that down we are saying something like...

A good translation key name should reference the copy itself. It does not need to include the entire phrase, but should capture the essence of the copy and should also be easy to differentiate from a key with similar copy.

Yeah i honestly like those verbose key names a lot more. I don't mind its redundancy and would rather have it redundant and more verbose than just ambigious keys.
I like the way you phrase it in the distilling it down section.


Update README.zh-Hans.md to 1.21

Update README.zh-Hans.md to 1.21.

Thank you, merged: 334f46995a92df381df4c0ce818c3a533eaa203c :+1:
I removed the references to the other translations files (we can't keep the reference to all translation files up to date in all translation files).


#35 layouts and member exports

Adds a new type of component: LAYOUT!
New Component Checklist

[ ] Includes unit tests for ALL required FDS use cases
[x] Does not mute any top level API props in React
[x] Includes an explanation for any changes to Jest snapshots (should be a PR tag automatically added if this happens)
[x] Component uses React.forwardRef() when a single DOM node is returned, AND it makes React-sense to access that DOM node

Need to remove prop API. Probably need to have these work with only children. Set all layout values to #root node. Hopefully having root CSS import there still works as expected for global styles if root level layout only returns fragment and child nodes.

Okay... this is close-ish for now. I discovered some issues with how we are defining imports of component groups and to make that easier we needed some more babel plugins.
There are also some significant tests for theming... both in terms of branding, checking contrast ratios for colors using a single branding variable, and also validating some things for dark mode.
There is going to be almost as much work defining the tools to reach for there. But honestly... some of the reusable style attribute stuff is going to be tricky to do with any sort of CSS in JS. The risk is that people may start mutating styles that we want. And in our case for this library... we actually want to enforce some of that. Possibly even have some custom lint rules to help.
Dart sass has a number of interesting, new patterns. There are some gotchas to get used to from node-sass.


Validate Context Variables in Finally Tasks

Changes

Prior to this change, Context Variables were not validated in
Finally Tasks. This change adds that validation and its tests.
/kind bug
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[x] Includes tests (if functionality changed/added)
[x] Commit messages follow commit message best practices
[x] Release notes block has been filled in or deleted (only if no user facing changes)

See the contribution guide for more details.
Double check this list of stuff that's easy to miss:

If you are adding a new binary/image to the cmd dir, please update
the release Task to build and release this image.

Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes

Added validation for Context variables in Finally Tasks

thanks @jerop
/lgtm

thanks @jerop
/lgtm

/test check-pr-has-kind-label

/test check-pr-has-kind-label

/test check-pr-has-kind-label

/test check-pr-has-kind-label


The page doesn't have steps for scopes

The sample uses scopes read and write, while this page doesnt't show any step to create them. The user gets error AADB2C90117: The scope 'read' provided in the request is not supported.

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

ID: fcf76a42-4ecb-63c9-8ca0-40af417006d7
Version Independent ID: 34c4f58e-a6a9-ab8c-0721-c4b8c5e0248b
Content: Tutorial - Enable a web application to authenticate with accounts using Azure Active Directory B2C
Content Source: articles/active-directory-b2c/active-directory-b2c-tutorials-web-app.md
Service: active-directory
GitHub Login: @davidmu1
Microsoft Alias: davidmu

@agrabhi Thank you for the feedback!  We are investigating this and will get back to you shortly.

@agrabhi Please note that as you refer to the sample, this section does have steps to add scopes -
Using your own Azure AD B2C Tenant.

@agrabhi We will now proceed to close this thread. If there are further questions regarding this matter, please open a new issue and we will gladly continue the discussion.


Disable rounded borders in yabai v5.0.0

Is there a way to do that? The rounded borders do not look good with windows that have no decorations.
Here is an example of emacs and alacritty:

You can only disable the radius globally. Have you looked into https://github.com/alacritty/alacritty/issues/1566#issuecomment-1121832279

How can i disable the radius globally then?

https://github.com/koekeishiya/yabai/blob/master/doc/yabai.asciidoc#config

window_border_radius []
Radius of window border.

Likely not going to look good when disabling it. This is why I previously did not make these changes, but enough people requested it and convinced me that it was worth the odd application that didn't conform to the system standard.
You can disable borders for specific windows using the rules system.

Thanks! That worked

If the window you're referring to is alacritty, changing the decorations: none to decorations: buttonless looks the same on Mac but correctly rounds the window and fixes the visual issue

Neovide doesn't have decorations: none for example. So to fix Neovide - I have to disable border radius globally for all apps also


Standardize ordering of Java modifiers

This is issue is very low and the main idea is to emphasis clean code. i know we might overlook but its much vital in organisation code of conduct  cc @antoine2711  @wetneb

I would not do such a normalization by hand without enforcing it in our linter in the CI.

Thanks for quick response. Do you mind helping me enforce it in or linter in the ci. We would definately enforce it.

Sorry I do not have time to work on this and it is not clear to me why we would need this normalization.

The idea to me is to have a standadized code of conduct. Am thinking in the next 10 years from now if this code is not having a clear code convention, it would not be appropriate. That's my kind of thinking.

The idea to me is to have a standadized code of conduct. Am thinking in the next 10 years from now if this code is not having a clear code convention, it would not be appropriate. That's my kind of thinking.

@sherrif10: I think that way you are raising here, are kind of issues that are not simple, nor short term planification. It involves so many variables, and also, which is very costly, a LOT of community discussions. And just that, while we are in the middle of the Outreachy project here at OR, it's an overwhelming tasks. So, if you really care about this kind of issue, I suggest that you come back in a month with it. And prepare yourself for a few weeks of discussions. This is not, unfortunatelty, a trivial task! ;-)
To understand the timing, you have to take in consideration that the quantity of task on Antonin's list are pretty numerous. For a month, he will not have time to discussion this kind of issue.
Regards, Antoine

The Checkstyle static checker could be used to check/enforce this. https://checkstyle.sourceforge.io/config_modifier.html#ModifierOrder
I'm not sure it's worth the churn in the code base, but if it ever were to be done, it'd be good to combine with as many other normalizations (e.g. import ordering, etc) as can be reasonably bundled together.

I wonder if our existing linter would be able to enforce that too (it is based on Eclipse style files). If that is the case, then all it would require is a change in the configuration file and re-linting: the integration in the CI is already there.

Given that there is not a huge appetite in tackling this specific linting change, I am closing this.


Update to Unicode 15

This reruns the script on current (Unicode 15) data. It also fix one operator in python script that doesn't work in python 3.

Didn't see #53 ... Never mind.


Issue 354: server-side encryption fix

@chrisjrd I'm getting an error when cluster provisioning.
│ An argument named "sqs_managed_sse_enabled" is not expected here.
╵
╷
│ Error: Unsupported argument
│
│   on ../modules/common/main.tf line 684, in resource "aws_sqs_queue" "isl_dead_letter_queue":
│  684:   sqs_managed_sse_enabled    = true
│
│ An argument named "sqs_managed_sse_enabled" is not expected here.
╵


App Service Terraform Module Improperly Formatted

When I try to execute Terraform Plan against the App Service Terraform module located at "infra/modules/providers/azure/app-service/", I encounter a syntax error stating
Error: Unsupported block type

  on main.tf line 10, in resource "azurerm_app_service" "appsvc":
  10:   app_settings {

Blocks of type "app_settings" are not expected here. Did you mean to define
argument "app_settings"? If so, use the equals sign to assign it a value.

To remedy this, the line app_settings { should be changed to app_settings = {

@ericpera-msft can you verify what version of terraform you are using?
This change is a part of the TF 12 upgrade (https://github.com/microsoft/cobalt/pull/172/files) but it has not been giving us issues in TF 11 so far.

@nmiodice I am using Terraform v0.12.1 so you are spot on about that. I'll close this issue.


Export Device Types from NetBox

Export Device Types from NetBox and map them to Containerlab node types. This would allow to emulate different device models of the same platform. On Containerlab side this is supported by SR Linux

Use-case: Be able to map between DeviceTypes and Containerlab kinds.
E.g.

Netbox DeviceType Slug of 7220-ixr-d3l could map to ixrd3l which is the string needed to represent this type as a Containerlab kind against the SR-Linux container image.

nodes:
       syd1-pd1-sp1:
            kind: srl
            type: ixrd3l <----------------------------------- type mapped from DeviceType.
            image: ghcr.io/nokia/srlinux:latest

Netbox device types MX104, MX204, MX480, MX960 all map to the juniper_vmx  kind in Containerlab.

nodes:
       syd1-edge1:
            kind: juniper_vmx <------- actually an MX204 in Netbox, only vMX is emulatable.
            image: vmx:23.1R10 <-------|

Looking into design choices to implement this:

Use DeviceType slug directly as type. Discarded, as there is less types supported by clab than different Nokia SR-Linux models (that would be a universal statement for most vendors).
Use a custom field in Netbox for type. Discarded, as nrx has to work with vanilla netbox deployments.
Create model_map.yaml in templates repo to map various Device Types from NetBox into types supported by clab. This is the last resort option, since it would effectively offload the function to track various models and what they should map to to the end users.
Rely on vendors or clab maintainers to provide up-to-date mappings. This could work for Nokia, but unlikely for others. But since it is only Nokia kinds that leverage type parameter, it might be enough. Checking feasibility of this option.
For the rest we could use the option 3, if/when needed.

Kinds that don't use type (everyone except Nokia at the moment) need to be mapped via kind and image. What that implies is a different type/flavor of the operating system, and that information is typically covered by platform field in Netbox. Nrx already provides mappings for platforms.

I think option 3 makes sense - users have to create some maps anyway for nrx so one more won't be too burdensome, especially if we create some sensible defaults - e.g. anything that looks like junuper-mx.* --> vMX kind. For this mapping, it would have to be a mapping of Device Type to kind (required) + image (required) then an optional type.

To implement option 3, we need a decision which property, model or platform, has higher precedence to map overlapping parameters. For example, both could be used to determine which node image to use in containerlab. Here is a list of parameters that could be defined by both:

kind
type
image
license
template (this one is for nrx to pick a proper j2 template)
and in general, all the other parameters too

My current thinking is that the following from model would take higher precedence:

type

And for these higher precedence would be from platform:

kind
image
license
template

In other words, when mapping parameters, I plan to first run through platform_map.yaml, and then through model_map.yaml by overriding type but leaving everything else as is if defined. If not defined, then use a value from model_map.yaml.


add own buuro options [feature request]

can a button be added that does that

You can already set tags in the Booru downloader settings, though after adding tags you may also need to remove the "all" tag for them to work.

no like diffrent buuros


Allow avax path only

These changes ensure that the BTC-integration works only with the avalanche path.

BIP44_COIN_TYPE_3 is set to 60 in our Makefile, right?

Yes, in our makefile


Add admin page & way to mark failures as resolved

Fix #1020

!!! 'golint' problems:
/home/travis/gopath/src/k8s.io/contrib/mungegithub/admin/admin.go:28:2: exported var Mux should have comment or be unexported /home/travis/gopath/src/k8s.io/contrib/mungegithub/mungers/e2e/resolved.go:35:1: comment on exported type ResolutionTracker should be of the form "ResolutionTracker ..." (with optional leading article)
Found flags in golang files not in the list of known flags. Please add these to hack/verify-flags/known-flags.txt
admin-port

fix incoming
On Thu, Jun 9, 2016 at 3:51 PM, Eric Paris<EMAIL_ADDRESS>wrote:

!!! 'golint' problems:
/home/travis/gopath/src/k8s.io/contrib/mungegithub/admin/admin.go:28:2: exported var Mux should have comment or be unexported /home/travis/gopath/src/k8s.io/contrib/mungegithub/mungers/e2e/resolved.go:35:1: comment on exported type ResolutionTracker should be of the form "ResolutionTracker ..." (with optional leading article)
Found flags in golang files not in the list of known flags. Please add these to hack/verify-flags/known-flags.txt
admin-port
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/contrib/pull/1177#issuecomment-225050162,
or mute the thread
https://github.com/notifications/unsubscribe/AAnglhxIM-ILFk7vXwg-miTVVhrsp0sqks5qKJj4gaJpZM4IydzF
.

Fixing tests...

this LGTM if you add a glog.Infof so we can see it in the logs.

I won't block on the 3rd endpoint.

It's easy, I'll push another iteration in a minute.
On Thu, Jun 9, 2016 at 4:29 PM, Eric Paris<EMAIL_ADDRESS>wrote:

I won't block on the 3rd endpoint.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/contrib/pull/1177#issuecomment-225056429,
or mute the thread
https://github.com/notifications/unsubscribe/AAnglm__qGDnmsexa-26uNAEyPfL7pleks5qKKHPgaJpZM4IydzF
.

Pushed. I added another commit for ease of reviewing.

(I mean, pushed to github. I didn't start this running in prod)

LGTM merge and kick if you like.

Thanks! I might as well restart it now, it's not like it's making progress.

And it gets a fresh set of tokens in 8 minutes...

Pushed!


Fix issue with view

There was an unexpected behaviour (pointed out by @KeithPJX) that occured when trying to limit the view to only search full words. This PR fixes it.

Codecov Report
Base: 68.33% // Head: 67.99% // Decreases project coverage by -0.33% :warning:

Coverage data is based on head (fd731f4) compared to base (87087eb).
Patch coverage: 50.00% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff              @@
##             master     #138      +/-   ##
============================================
- Coverage     68.33%   67.99%   -0.34%
- Complexity      534      537       +3
============================================
  Files            84       84
  Lines          1860     1878      +18
  Branches        235      237       +2
============================================
+ Hits           1271     1277       +6
- Misses          484      493       +9
- Partials        105      108       +3

Impacted Files
Coverage Δ

...model/person/PersonContainsAttributePredicate.java
33.89% <50.00%> (-0.59%)
:arrow_down:

.../java/seedu/address/logic/commands/AddCommand.java
60.86% <0.00%> (-39.14%)
:arrow_down:

...eedu/address/logic/parser/DeleteCommandParser.java
92.00% <0.00%> (-8.00%)
:arrow_down:

...c/main/java/seedu/address/model/person/Person.java
87.27% <0.00%> (-0.23%)
:arrow_down:

src/main/java/seedu/address/MainApp.java
0.00% <0.00%> (ø)

src/main/java/seedu/address/model/Model.java
100.00% <0.00%> (ø)

...rc/main/java/seedu/address/model/ModelManager.java
100.00% <0.00%> (ø)

...a/seedu/address/model/person/UniquePersonList.java
93.02% <0.00%> (+0.34%)
:arrow_up:

src/main/java/seedu/address/model/AddressBook.java
92.59% <0.00%> (+0.59%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


define ble_running for non-microbit NRF-based boards

ble_running is defined by MicroBitDevice.h and everything compiles successfully. For other boards with softdevice, ble_running is now defined here.

@mmoskal What do you think? Define ble_running here? or in the CODAL target?


VNC Issue

The 5900 port is allocated on my computer already. So I changed port setting in the docker-compose.yml file and Dockerfile.
RUN docker ps
CONTAINER ID        IMAGE                  COMMAND             CREATED             STATUS              PORTS                                                      NAMES
d445ef4a58fe        docker-unity3d_unity   "/entrypoint.sh"    6 minutes ago       Up 6 minutes        <IP_ADDRESS>:5555->5555/tcp, <IP_ADDRESS>:5910->5910/tcp, 5900/tcp   unity-service
RUN  ps aux
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
adminus+     1  0.0  0.1  18028  2760 pts/0    Ss+  01:01   0:00 /bin/bash /entr
adminus+     9  0.1  0.2  98860  5816 pts/0    S+   01:01   0:00 x11vnc -forever
adminus+    10  0.2  0.1  18220  3204 pts/1    Ss   01:05   0:00 bash
adminus+    18  0.0  0.1  34420  2828 pts/1    R+   01:05   0:00 ps aux

I am using a Mac, so <IP_ADDRESS> does not work for me, instead, I used localhost to start the VNC viewer.
Yet it asked me the username and password. I know the password is pass123, but what is the username?

@nenadg Thank you very much for the reply, I have tried multiple user names, including

root
adminus+
None
admin

but none of the above worked.

The window popped for credentials contains the following info,
" Enter the credentials expected by VNC Server running on the remote computer.
Note these are not your RealVNC account credentials.
VNC Server: localhost::5900
Username:
Password:
"
which does not look right, because as the docker message shown above, I configured the port to 5910.

note that adminus+ is just a way your console abbreviates adminuser, you can try that.
Tomorrow, I'll try to figure this out in more depth since I don't have working image on this machine.


Enable intersphinx to link main Python doc

Changes

Add intersphinx to the extensions list
Add the main Python repo to the externally linkable doc

Purpose
Keep pyglet documentation brief by linking external documentation more succinctly and reliably than full URLs.
Example use cases include:

Suggesting existing Python built-ins in the programming guide
Linking relevant dev dependency doc (pytest, sphinx) in future contributor doc

Merging #938 made this redundant.


In-house compositor design discussion

We're going to switch to an in-house compositor instead of using wlc. This issue should serve as a place to brainstorm about the design goals of this compositor. Some of the rationale for using our own compositor is described here: https://github.com/SirCmpwn/sway/issues/1027#issuecomment-279840028
Firstly, some refactoring will need to happen to what we already have:

Much of sway/* will move into i3wm/* as the i3 implementation. This directory will implement i3 commands, window management, IPC, etc as a compositor plugin
The wayland client support code will move to client/ and be refactored quite a bit
Current implementations of protocol extensions will be implemented as compositor plugins. desktop-shell and current sway-specific protocols will be removed in favor of surface-layers.

New subdirectories will be established:

server/ will contain server utility code, similar to the role our shared client code serves
targets/ will contain render "target" implementations, such as DRM, Wayland, X11, fbdev, etc
renderers/ will contain a gles2 renderer, which will render each output into a buffer, and cooperate with targets to offload work onto them when appropriate (i.e. fullscreen-shell)
sway/ will leverage server/, renderers/, and targets/ to provide the actual sway compositor

Each of these logical areas will provide their own APIs, which can be leveraged by the plugins. These new directories will constitute the core of sway, and features like i3 behavior can be implemented on top of their APIs. Note when I say plugins, I'm presently only talking about it from a design perspective - dynamic linking of external plugins is out of scope for the time being.
Some goals to set from the outset to address current problems or lack of features in wlc:

Output rotation and modesetting (note: I wish to deprecate setting resolutions that aren't available as modes)
Address performance issues inhernet in wlc's (immediate mode) design
Achieve flexibility necessary to cleanly implement things like surface-layers, input-injection, and other features that require a deeper connection with our compositor
TTY handling
Rendering views on multiple outputs at once (and dragging views between outputs)

Some discussion points for design:

Eliminate swayc_t from the non-i3 parts of the codebase, and consider renaming it to i3container_t or something similar?
Use wl_list and such instead of list_t?

wl_list is a linked list, which will be less efficient
wl_list has a lot of functions implemented as macros, which is strongly discouraged in sway code
We will have to use wl_list et al at least to some degree to expose lists over the wayland protocol, though.

Isolating i3 functionality to the i3wm directory is not only for organizational reasons, but to possibly in the future provide implementations of other WMs (bspwm, awesome, xmonad, openbox, etc), be it internal or external implementations. Should we design with such external plugins in mind? Should we move sway-i3wm into such a plugin?
Use multiple processes? We could leave a privledged process running to do things that we currently use caps for, which would improve security. We could also use this process to do TTY handling to isolate TTY handling from any problems that may arise in the compositor (which would make crashes easier to recover from).

Some useful software to reference while writing our compositor: wlc, weston, swc

Isolating i3 functionality to the i3wm directory is not only for organizational reasons, but to possibly in the future provide implementations of other WMs (bspwm, awesome, xmonad, openbox, etc), be it internal or external implementations. Should we design with such external plugins in mind? Should we move sway-i3wm into such a plugin?

If that's the direction you'd go in, would this attempt to be a replacement for wlc? I agree with the issues you raised about wlc -- We are running into the same issues on Way Cooler. Is this compositor implementation only going to be internal to Sway or do you foresee a situation closer to wlc where it's more general so any WM can be implemented?
Personally, I think that future of Wayland window managers hinges on good, general compositor libraries being the backbone for most non-"mainstream" window managers (e.g, everybody that isn't Gnome or KDE). Otherwise, it's too painful to the end user in terms of what features are actually implemented for a given window manager (e.g. good xwayland support, remote desktop,  other niceties like redshift, etc.).
I'm going to look into libweston as well, since that wasn't an option when I started Way Cooler. Is this something that this project is going to turn into, or is this first and foremost going to be for Sway?

I think designing sway in a way that permits it to be a replacement for wlc is a good design choice, though that's not necessarily the goal. I do foresee a time when more window managers could be built on top of sway if that design works out. However, since replacing wlc is a consequence of this design rather than the goal, I would be willing to sacrifice design details that support wlc-like use-cases in favor of design decisions that benefit the direct goals of the project. To that end I foresee other window managers being implemented as sway plugins rather than as standalone compositors that leverage sway like sway leverages wlc, for example.
However, within this model and if plugins work out, I see no reason why pretty much every WM of today's X ecosystem couldn't be implemented as a sway plugin. Similar to how some people thought weston was going to be.

To clarify, I think isolating the i3 implementation is a good design and I think that building a (plugin API)-like thing is a good design, but I'm not exactly aiming for supporting that for generalized use cases at the moment.

Ok, thanks for the response. I hope that this project achieves its goals.

I really like your last point. I think multiple processes and especially keeping privileged processes small and auditable is a good way to go forward.

I bet you have put some deep thought on this, but let me ask the obvious question: Why you want to restructure the whole repository, and rename everything?
It seems to me, an easier upgrade path would be the following:

Do not rename the actual compositor from sway to "i3wm" (it is a completely different implementation after all!) or change the repository structure
Create a new repository, that will have the replacement for wlc. Call it swaylc (sway library for compositors) or whatever :p
Begin replacing parts of wlc in sway with the new library, until everything is replaced.

The thing is, that sway is already used as day-to-day wm by some of us, including me, and I'd rather have a smooth transition than having stopped development and waiting for an unknown time period until wlc is replaced. Also the renaming will probably confuse people.
Plus I find it awkward to have one repository, that will now have the code of a wlc-replacement, "i3wm for wayland", and possibly "openbox for wayland", tons of other tiling/simplistic wms, and to call all that together "sway" from now on.
Aside from that, I think it is a good thing to replace wlc, if we can have a better/faster/stronger sway in the long run. And privilege separation is something I definitely would like to see.

I bet you have put some deep thought on this, but let me ask the obvious question: Why you want to restructure the whole repository, and rename everything?

I don't, really. I want to maintain the status quo. Right now the actual compositor of sway is being kept seperate, in wlc. If we write our own, I want to maintain that separation. We currently have some components that are compositor-like (such as protocol extensions, rendering window borders, etc). The bulk of the code is more analagous to a WM than to a compositor, and what little compository code we have is intermixed with it. If we're going to write an in-house compositor, I would prefer to move the handful of things that we currently have that belong there into it.

Do not rename the actual compositor from sway to "i3wm" (it is a completely different implementation after all!) or change the repository structure

The compositor renders windows to the screen. Strictly speaking wlc is the compositor. I'm not renaming sway to i3wm, I would like to clearly separate i3wm behavior into a seperate logical unit from the compositor, which is just a good design decision. It makes sense to call that module i3wm because that's what it does, implement i3wm. It is an implementation of i3wm. That is, any behaviors in i3wm that you can't reproduce in sway are considered bugs in sway (always have been).

The thing is, that sway is already used as day-to-day wm by some of us, including me, and I'd rather have a smooth transition than having stopped development and waiting for an unknown time period until wlc is replaced.

I use sway every day, too, I'm using it right now :) trust me, the transition will be careful, slow, and smooth. I don't intend to ship any release that causes major breakage. I don't want to halt development, but I also don't want to ship half-assed versions of the code. Though I want to avoid breaking changes, iif we have to make them, the time to do so is while doing 0.x releases. We'll be thankful for that attitude 10 years from now.

Also the renaming will probably confuse people.

No renaming is happening externally, this project is still called "Sway". How end-users use it isn't changing either. We're just talking about the internal organization of the codebase.

Plus I find it awkward to have one repository, that will now have the code of a wlc-replacement, "i3wm for wayland", and possibly "openbox for wayland", tons of other tiling/simplistic wms, and to call all that together "sway" from now on.

If we get to the point that we are implementing more WMs here (which is a dubious prospect in the first place), they won't all live in one repository and we'll find a way for it to make sense.

Thanks for the clarification, now it makes sense to me :+1:

Something else to mention: wlc abstracts some of wayland away from the user, as if it were designed to also be able to support some other display protocol. We should not do this with our thing, it will save us some headache and make it easier to do some things.

After some of the design discussion with way-cooler (even though way-cooler has decided to go another direction), I'm considering doing this out-of-tree and making it a generic library like wlc/swc/libweston, but with these design goals in mind. Thoughts?

I think having it out of tree would make the most sense -- it would allow others to easily bind with it better, and it will be easier to separate the concerns of the two layers if they live in separate projects. This also means issues with Sway won't get mixed in with issues about the compositor library.
Also--Way Cooler hasn't decided to go in another direction. Fireplace has decided to work on their own compositor framework Smithay. I'd still like to work with you on a non-Rust compositor library, as I think it will be easier to support in the future (there are more people who know C, there will more than likely be more compositors using it, I expect most of the contributors to wlc to contribute to this project, etc.). If it turns out to be better for my needs I might switch to Smithay in the future but for now I want to try to work on a more general solution.

Oh, I didn't realize Fireplace was a separate project.

Yes it's relatively new, despite the high version number. It's similar to orbment in that it's modular, but with Rust instead of C

Something I just thought about:
Please make the in-house compositor code (be it a separate library or not) fully POSIX (and therefore musl libc) compatible. This means, do not use any glibc specific features, such as qsort_r. wlc did this right from the start afaik, and it was later patched in sway. I think the best way would be, to specify a POSIX_SOURCE define when compiling sway.

Of course.

I hate GNUisms, they were added by mistake and anywhere you find them is a bug.

Here are my current thoughts. I want to better support @Timidger and others with similar use-cases, so instead of doing this in-tree we'll be making a new library that will fulfill a similar role as wlc, but with a different design. We'll call this library "wlroots" (or "wlr"). The design I have in mind is this:
Several independent components (compositor, wayland server, xwayland, xdg-shell, etc) that the user can compose freely. No functionality will be mandatory, and the user can implement any functionality themselves (no necessary information like libinput pointers will be hidden). The user will have ownership over lots of things that wlc currently has ownership over, but stewardship of these resources will be assisted by wlroots. Notably, the user will own the wayland registry and will probably own the event loop.
Assuming we like this design, I'm ready to get started in the next few weeks.

@SirCmpwn Thank you. I'd be interested in joining this project, or shadowing to some extent if possible.

Keep an eye on this thread and contribute when the code starts happening.

Thanks. Will do & I'll ping the IRC channel in the next few days as well.
Brad
+1<PHONE_NUMBER>
On Wed, Mar 15, 2017 at 10:30 PM, Drew DeVault<EMAIL_ADDRESS>wrote:

Keep an eye on this thread and contribute when the code starts happening.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/SirCmpwn/sway/issues/1076#issuecomment-286961997, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AKN8wee3AFTBaoTf6GsfDSofpXNESXu2ks5rmMj9gaJpZM4MBM2A
.

Will this support EGL streams/proprietary nVidia drivers? You said that's unlikely but does that mean it's unlikely to have it in the beginning or ever?

Ever.

I have started working on wlroots. The repository is available here: https://github.com/SirCmpwn/wlroots
I've started putting together the wayland backend (for running the compositor nested in another wayland session), since this should be the simplest backend to make.
My current plan is:

Flesh out the wayland backend
Establish the wayland server
Build the renderer

We'll go from there.

Since libweston is a reference implementation for Wayland what is the reason to write custom solution?
offtopic:
My team at university is about to write our own wayland based WM for mobile device (nothing fancy just one term project) and we have the same questions.
We've planed to use weston as a base due to its raspberry support but since vc4 it doesn't really mater.

libweston inherits all of the problems of weston, of which there are many. It also is run with a different philosophy than my approach and the changes I would want to make would be difficult to upstrema.

wlroots is well underway - closing this.


Consider mongodb style updates.

I found this project:
https://github.com/Automattic/mongo-query
And was wondering if there were any plans to add mutating operators to this lib? It would be pretty handy to have to full functionality of mongodb queries in the browser.

The intended purpose of this library is to filter arrays using mongodb queries. I think if anything it'd be appropriate to create another repo for this sorta of feature. That way you can opt-in or out of it without the additional bloat. For example:
var people = [{ age: 100 }, { age: 50 }, { age: 20 }];
update(sift({ age: { $gt: 20 }}), { $inc: { age: 1 }});

About that code sample, that's not always going to work:
update(sift({ 'nested.age': { $gt: 20 }}), { $inc: { 'nested.$.age': 1 }});


Add the error dictionary file

Add a new file for compiler errors as mentioned in https://github.com/malloydata/malloy/discussions/1787

I think we may want to auto-generate this file so it's easier to make sure links are valid, see comment here https://github.com/malloydata/malloy/discussions/1787#discussioncomment-10128115


keep-alive breaks v-ref on

Vue.js & vue-router.js version
1.0.18, 0.7.13
Reproduction Link
http://www.webpackbin.com/VJUv0eAl-
Steps to reproduce
Click on the "page 2" link and then click on the "page 1" link.
What is Expected?
It should say "current page is page 1". The text is bound to {{ $refs.page.name }} with <router-view v-ref:page keep-alive="true"></router-view> and name is part of the data for the page1 and page2 components.
What is actually happening?
The text disappears after switching back to page 1 because the v-ref on <router-view> is no longer respected. If you remove keep-alive it works as expected.

$refs is designed only for programmatic access,  and usage inside templates should be avoided.
As of now, for vue 2.0 and above $refs is completely not reactive (to avoid cases like this), so this is a won't-fix for 0.7.

Is this the same for Vue 3? I'm trying to cache a page and call $refs.userForm.submitUserEdit() inside a @click however once I navigate away and come back, it says $refs.userForm is undefined.


Set node ip to fixed address

The node-ip option for kublet will be set to the highest
non-broadcast address in the edgenet subnet.  Note that this
address will not necessarily have internet visibility.
Signed-off-by: Kyle Stein<EMAIL_ADDRESS>

@costanic, the short answer is I have no idea how that IP is used.  Evidence suggests that it is not actually used for anything.  (Perhaps it is a remnant of k8s before we modified it?).  I guess @c1728p9 is the most qualified to answer your question.


obsidian: 1.5.8 -> 1.5.11

Description of changes

Updated hashes of binaries
Added myself as maintainer

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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

[ ] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

There is https://github.com/NixOS/nixpkgs/pull/297217 generated via automation

It is lacking the darwin hash update which I hopefully got right

Result of nixpkgs-review pr 297215 run on aarch64-darwin 1

1 package built:

obsidian

Result of nixpkgs-review pr 297215 run on x86_64-linux 1

1 package built:

obsidian

Welcome @w-lfchen :D

It is lacking the darwin hash update which I hopefully got right. Also, this pr was opened before that pr existed.

Agreed. I just wanted to link them so reviewers of one know about the other. This seems more complete


better workaround for crbug #612836

On mobile, we currently work around https://crbug.com/612836 with this code:
// Force a repaint every 300 ms.
// Extremely hacky workaround for https://crbug.com/612836
setInterval(function() {
  window.top.dispatchEvent(new Event('resize'));
}, 300);

This forces a repaint of the entire viewport every 300 ms, even when the dirty region is smaller or empty. The performance impact of this is not just theoretical; it seems to be the cause of #2659.

Instead of dispatching a resize event every 300 ms, I experimented with dispatching one only after any Polymer element with an on-tap handler is tapped. In addition, I put this in a debounce with a 300 ms window, so multiple calls to the resize dispatcher within the window would be combined into one and delayed till the end of the window. Unfortunately, due to #2742, this was not enough to keep the UI from getting stuck after certain interactions. For example, tapping the "Create a cloud server" entry in the invite panel currently waits for Cloud to be "logged into" before showing the cloud UI, which takes a nondeterministic (and often much longer than expected, e.g. more than a second, in my testing) amount of time, so that the resize event gets fired before the UI has been updated with the effect of the tap. Given that experience, we may be better off taking a different approach and/or fixing some of the related issues first.

Not sure if related, but the comments section of http://stackoverflow.com/a/3485654 has quite the long list of other people reporting that WebKit is failing to issue repaints properly, and without Polymer implicated in any of them.

:-(
May be useful to share this information on the crbug.

I noticed the following warning in the javascript console after attaching to uProxy running on my Nexus 5:

Deferred long-running timer task(s) to improve scrolling smoothness. See crbug.com/574343.

Indeed, I think this is getting logged by the scheduler when it detects that our setInterval resize hack is expensive and defers it.

May be useful to share this information on the crbug.

Good call, done in https://bugs.chromium.org/p/chromium/issues/detail?id=612836#c19, thanks @fortuna

Closing as this is not a priority right now.


feat(renderer): implement tui renderer

Codecov Report

Merging #66 into v2 will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##               v2      #66   +/-   ##
=======================================
  Coverage   84.21%   84.21%
=======================================
  Files           3        3
  Lines          19       19
  Branches        3        3
=======================================
  Hits           16       16
  Misses          3        3

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 eb14cb9...d84ee73. Read the comment docs.


Generador de NITRO

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Issue invalid

Hola soy nuevo como puedo usar el generador de nitro??
Responde porfa.


Fix/Android: crash in Media Service

Lib versions:
    "react-native-theoplayer": "7.2.0",
    "theoplayer": "7.4.0",

Description:
We have a repetitive crash in Android app with the following logcat:
Fatal Exception: android.app.RemoteServiceException$ForegroundServiceDidNotStartInTimeException: Context.startForegroundService() did not then call Service.startForeground(): ServiceRecord{4020d8b u0 com.gotv.nflgamecenter.us.lite/com.theoplayer.media.MediaPlaybackService}
       at android.app.ActivityThread.generateForegroundServiceDidNotStartInTimeException(ActivityThread.java:2245)
       at android.app.ActivityThread.throwRemoteServiceException(ActivityThread.java:2216)
       at android.app.ActivityThread.-$$Nest$mthrowRemoteServiceException()
       at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2508)
       at android.os.Handler.dispatchMessage(Handler.java:106)
       at android.os.Looper.loopOnce(Looper.java:226)
       at android.os.Looper.loop(Looper.java:313)
       at android.app.ActivityThread.main(ActivityThread.java:8762)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:604)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1067)

Testing plan:
The issue occurs only in production so we're not able to provide a repro app/steps/snippets whatever. As we had this crash before and were able to resolve it in this way I'd like to suggest these changes for your codebase.
Also let's keep it open until we have a confirmation with the latest stats from Crashlytics that the crash is gone (it might take some time). Please lmk if any objections @tvanlaerhoven

Also adding this related issue from Google's tracker here:
https://issuetracker.google.com/issues/307329994

closing as it didn't resolve on our end (we've tested it as a patch)


Table without Border

Hi
I was trying to remove the border in the semantic ui react basic but it doesnt work .  Can u tell me how can I manage to remove the whole border?

Name
Status
Notes

John
Approved
None

Jamie
Approved
Requires call

Jill
Denied
None

.ui.table tr td { border-top: 0px !important; }

I'm a bit late, but I removed the whole border, from all the table children and the table itself, this way:
.ui.table * {
  border: 0px !important
}


Backup not stored to S3: Request Entity Too Large

Rancher Server Setup

Rancher version: v2.5.5
Installation option (Docker install/Helm Chart): helm
Kubernetes Version and Engine: v1.17.2

Describe the bug
Storing a backup to S3 aborts on upload with failed to upload backup file: 413 Request Entity Too Large
To Reproduce
Steps to reproduce the behavior:

Install Rancher Backup
Create a backup with S3 configuration (here, S3 compatible DigitalOcean Spaces are used)

Expected behavior
Expect: The backup to be uploaded to S3 Bucket
Additional context
As a "shot in the dark", the ingress exposing rancher got the annotation nginx.ingress.kubernetes.io/proxy-body-size: 0 to no avail

Can you see the size of the tar file you are trying to upload? Also, can you check the configuration of your S3 buckets to see what their upload limits are? That looks like the error is coming from your storage provider. A quick search shows that Digital ocean limits uploads to 5GB per part. If you have a backup larger than that, then we'll have to make a feature request in order to split backups into multiple parts.


Fix STDOUT and STDERR direction based on Log.* calls

Closes https://github.com/docker/machine/issues/2587
It's a big issue.  create, for instance, logs everything to STDERR rather than STDOUT in v0.5.3 today.  You can easily verify this with a shell function like this:
stderrcolor () {
    "$@" 2> >(while read line; do echo -e "\e[01;31m$line\e[0m" >&2; done)
}

Since we're not using the Bugsnag hook for logrus at all, my feeling is that we should just remove the use of logrus altogether (I can't see any particular advantages) and use only fmt logger.  That's what I've implemented here.  AFAICT there's no way to get logrus to change which stream it logs to based on logging levels.  I can followup PR to remove the vendored code for this.
During standup we need to discuss whether we feel like this merits a 0.5.4 release ASAP.  In my opinion it does, since the accidental regression is so large in scope, and could potentially affect a lot of downstream users and/or existing scripts for Docker Machine.
The bundled tests are a step in the right direction to ensure something like this doesn't happen again in the future.  More would be better, of course.
cc @dgageot @jeanlaurent
Signed-off-by: Nathan LeClaire<EMAIL_ADDRESS>

Well, this is doing two things at the same time, fixing the issue and removing logrus. I usually really don't think this is a good idea especially when we have an outstanding issue to fix. I would prefer we fix the issue, release 0.5.4, discuss the logrus case afterwards, one thing after the other.
I spent 1/2 hour fixing the issue while keeping logrus this give this code,
https://github.com/jeanlaurent/machine/commit/6e09858ec5dd6a5e45228d5cc2e298fd7a9decc4.
There is two major points of interest with logrus : It handle the log levels and has a hook system, which allow in theory to communicate logs to an external system.
To try to prove we still need logrus I tried to log everything that is logged to a file. I did it in https://github.com/jeanlaurent/machine/commit/7038122ac6d277d7c56570f281d4c7815a37e4ee. And this is failing badly, because logrus as only one LogLevel used as a threshold to decide to keep the log or not, ( I was accustomed to java logging library that handle that very well) . If the logger is set at the info level, all debug logs are not send nor recorded, they are lost. The hook system does not even receive the event.
So for our usecases, the hook system is useless, we have to listen to log event, before they are actually sent to logrus to bypass the one loglevel limitation. That what we do with the various record functions.
So the logrus usage boils down to library popularity and... standard logging.
So the PR which keeps logrus ( https://github.com/jeanlaurent/machine/commit/6e09858ec5dd6a5e45228d5cc2e298fd7a9decc4. ) actually add even more code and a bit of complexity than the current PR does.
So I'm going to LGTM this one, and give a good "farewell" to logrus.
There is a couple of points which needs some polish, that will be dealt in a followup PR.

I look at the https://github.com/docker/machine/blob/19ce7b79bd8/commands/status.go#L8 . I think it was fogiven to output the status to user. This function just writes it to log.
I suppose there are two different architectural things in this case: the status as anwer of command line UI to user, and status as 'technical' message writed by docker-machine to logging subsystem.
I think, the logging messages are totally "technical" aspect and is a subject of configuration by sysadmins. For example logging messages could be disabled, routed to syslog, to another log agregation host and etc.
But answers of tool is aspect of its user interface. This messages are could be formatted, coloured, translated to languages.
As for me its a strange trick to use logging subsystem here to output the anwer (status) to user here. I think the logrus is a good tool for logging (to deal with technical messages), but it is a bad place for answers from CLI.
sorry for my silly english.


"export default" in d.ts file breaks highlighting below

Hard to explain. Here's an easily reproducible example:
export default function x(): number;
export function y(): string;

Thanks!


Fix #294: call printer better output format

https://cilogs-ityfuzz.s3.amazonaws.com/a9e0c79e-94ce-4cb1-aacb-eeda2a6e9a52/res_Annex_exp.txt
It seems the reentrancy is broken in logging


the dimensions of bilateral_grid and guidemap_guide in slice operation are not match

the coef is obtained by:
coeff = F.grid_sample(bilateral_grid, guidemap_guide, align_corners=True)
where the dimension of bilateral_grid and guidemap_guide is Nx12x6x16x16 and Nx1xHxWx3 respectively.
in my opinion, the dimension of guidemap_guide should be Nx1x3xHxW. Could you confirm if the code is incorrect

On network.py line 76 , the dimensions of guidemap_guide are rearranged to fit the 5D input (N, D_out, H_out, W_out, 3) of torch.nn.functional.grid_sample. So guidemap_guide is Nx1xHxWx3 here.

ok, thanks for your work and reply.


[async-props] Warning: Required context activeDelegate was not specified in Link.

Not sure how this started happening, it seems like at one point it was working fine and all of a sudden it's broken. Getting a stack trace is being difficult as it's just warning me not erroring (it also seems ReactPerf is running on my stack, and I didn't explicitly enable it anywhere so I'll have to see whats up there).
Anytime I use a <Link /> now it seems to give this warning, but it also breaks my application.  You can see it happening with my repo: http://github.com/natew/react-base.
Console warning is: Warning: Required context activeDelegate was not specified in Link.

I have this issue in tests, where I do not have  component. I test logic that is not related to routing. Is there any way to workaround this requirement in tests?

@chaliy For 0.13, see https://github.com/rackt/react-router/blob/v0.13.3/docs/guides/testing.md. It should be similar for 1.0 beta if that's what you use, although the exact methods may differ.

@gaearon  thanks,  that's helpful


My app would not function until I added a route for robots933456.txt

Hello! My custom container kept failing to start correctly. I was able to find the logs and I saw my app logs showing that it had started correctly and was listening on port 80, but then it was quickly followed by a time out after 250 seconds or so and cease to function.
It contained a Node JS app made with express. When I reviewed the logs I noticed that my app would receive many requests for "robots933456.txt", which my app did not handle. I had to search this back through Google to find a previous issue where someone had complained this was not documented anywhere as being a necessary route for a health-check. I noticed this was specifically referencing PHP in particular and it was documented in that section, but my app is a custom container running a Node JS Express app.
I think the documentation for this requirement is important and still hard to see without deep digging and hours of debugging.

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

ID: f970943e-c7b4-919c-65ea-6ba20831e74d
Version Independent ID: 90c5dd06-ea6d-7af8-f88c-9d189e9ceef2
Content: Build a custom image and  for Web App for Containers - Azure App Service
Content Source: articles/app-service/containers/tutorial-custom-docker-image.md
Service: app-service
GitHub Login: @msangapu
Microsoft Alias: msangapu

@carlpoole Thanks for the feedback! We are currently investigating and will update you shortly.

@carlpoole , So in order to ensure a container is up and running and ready to serve requests our Platform has to ensure that the web server inside the container is capable of handling requests. While the app container is starting up, our platform keeps sending HTTP requests to /robots933456.txt inside the container. Now /robots933456.txt doesn't actually exist inside a container but the intention for which this is done is to get a non-5xx response from the webserver inside the container. Which implies the web server is ready to handle requests. Even a 404 response is a valid response since it confirms to the Platform that the web server inside the container is up and sent the 404.

Thanks for the info. Our app wasn't setup with this in mind but I have configured it to send 404 messages now.

@carlpoole , Thanks for the response. I will go ahead and close the issue. If you need any other assistance please feel free to re-open the same

@DashleenBhandari-MSFT and @BryanTrach-MSFT so how do you actually do this?

I figured out how to do this and this information should be added in documentation because it would prevent someone from running any angular app until this is implemented.

Hey, I am getting the same error on running my Angular application, can you please guide me how to proceed further.
Also, this error came today only.

I having the same problem on my express and react.js app running on azure web app. below are my logs

Hey Team,
You can safely ignore this message. /robots933456.txt is a dummy URL
path that App Service uses to check if the container is capable of serving
requests. A 404 response simply indicates that the path doesn't exist, but
it lets App Service know that the container is healthy and ready to respond
to requests.
Thanks & Regards
Gaurav Gupta
FullStack Developer @ Dev Centre House
Masters Computer Engineering | Bachelors Computer Engineering
Trinity College Dublin, Ireland
+353 899417858 (M)
@.*** | @.***
ᐧ
On Wed, 17 Nov 2021 at 10:15, Felix Omuok @.***> wrote:

I having the same problem on my express and react.js app running on azure
web app. below are my logs
[image: image]
https://user-images.githubusercontent.com/45859301/142145001-987e500d-b437-4c01-8856-a6eb16acac99.png
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/32472#issuecomment-971223674,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AI2HMB27VB2WJBUDTDTHQB3UMNCAVANCNFSM4HRPMPRQ
.

Hey Team, Faced the same issue on my angular application. You can safely ignore this message. /robots933456.txt is a dummy URL the path that App Service uses to check if the container is capable of serving requests. A 404 response simply indicates that the path doesn't exist, but it lets App Service know that the container is healthy and ready to respond to requests.

I finally understood it. I realized I did error handling but I was not returning a 404 status code

But it's really annoying to see "Failed requests" on your dashboard that we're monitoring to find potential issues:

But it's really annoying to see "Failed requests" on your dashboard that we're monitoring to find potential issues:

Did you figure out how to remove them? Kinda SUPER annoying.

yes
On Thu, Mar 24, 2022 at 5:43 PM JorgenSQ @.***> wrote:

But it's really annoying to see "Failed requests" on your dashboard that
we're monitoring to find potential issues: [image: image]
https://user-images.githubusercontent.com/125493/145811461-abdd54bb-7446-4cbe-8e05-dc86070076b5.png
Did you figure out how to remove them? Kinda SUPER annoying.
—
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/32472#issuecomment-1077704848,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AK54DZJXAAYVK2NUHAFMTULVBR5QNANCNFSM4HRPMPRQ
.
You are receiving this because you commented.Message ID:
@.***>

@dijiflex Test in development to make sure you're getting 404's from invalid file URLs (since any device on the internet could request any URL from you at any time). Thats down to whatever code you're running. I had this on my rails app until I adjusted the respont_to block to handle it. Code stuck below for anyone's future reference
rescue_from ActionView::MissingTemplate, with: :raise_not_found
def raise_not_found
    # render text: 'Not Found', status: 404, layout: 'application'
    render 'errors/not_found', status: :not_found, formats: [:html]
end

errors_controller.rb
def not_found
    respond_to do |format|
      format.any { render 'errors/not_found', status: :not_found, formats: [:html] }
    end
end

@carlpoole , So in order to ensure a container is up and running and ready to serve requests our Platform has to ensure that the web server inside the container is capable of handling requests. While the app container is starting up, our platform keeps sending HTTP requests to /robots933456.txt inside the container. Now /robots933456.txt doesn't actually exist inside a container but the intention for which this is done is to get a non-5xx response from the webserver inside the container. Which implies the web server is ready to handle requests. Even a 404 response is a valid response since it confirms to the Platform that the web server inside the container is up and sent the 404.

 You just flooding the app logs and stress the application with unnecessary requests. You have the health check URL, why not to use it? Or at least give option to change the URL. We need to put exclusion for monitoring, which is annoying.

App Services has configuration for health checks, so why do you need to call this unconfigurable robots file instead of just using the configured health check?

I agree this should be re-opened. Azure should not require a server to respond to certain requests. Also, I have some workers that I don't want to response on any requests, and now I have to do custom handling just to please Azure 💩.

Just created a ticket on our board to investigate why we have so many 404 responses. Thanks for the annoyance Microsoft.


docs: image broken on npm page

Self-explanatory 😁
I'm on Firefox, macOS

:tada: This issue has been resolved in version 3.0.0-beta.48 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Convert pool query to function call

Changes proposed in this PR

Convert pool query logic to pure function call

Why are we making these changes?

Easier to read
Easier to reuse
Better performance

New (no pool)
Evaluation count : 83280 in 60 samples of 1388 calls.
             Execution time mean : 724.906725 µs
    Execution time std-deviation : 7.126763 µs
   Execution time lower quantile : 717.701292 µs ( 2.5%)
   Execution time upper quantile : 740.208994 µs (97.5%)
                   Overhead used : 1.565043 ns

Found 3 outliers in 60 samples (5.0000 %)
	low-severe	 1 (1.6667 %)
	low-mild	 2 (3.3333 %)
 Variance from outliers : 1.6389 % Variance is slightly inflated by outliers

Old (no pool)
Evaluation count : 40980 in 60 samples of 683 calls.
             Execution time mean : 1.470291 ms
    Execution time std-deviation : 8.615948 µs
   Execution time lower quantile : 1.453152 ms ( 2.5%)
   Execution time upper quantile : 1.486338 ms (97.5%)
                   Overhead used : 1.565043 ns

New (has pool)
Evaluation count : 54660 in 60 samples of 911 calls.
             Execution time mean : 1.090170 ms
    Execution time std-deviation : 16.439733 µs
   Execution time lower quantile : 1.067333 ms ( 2.5%)
   Execution time upper quantile : 1.124302 ms (97.5%)
                   Overhead used : 1.565043 ns

Found 5 outliers in 60 samples (8.3333 %)
	low-severe	 4 (6.6667 %)
	low-mild	 1 (1.6667 %)
 Variance from outliers : 1.6389 % Variance is slightly inflated by outliers

Old (has pool)
Evaluation count : 35460 in 60 samples of 591 calls.
             Execution time mean : 1.754258 ms
    Execution time std-deviation : 51.372349 µs
   Execution time lower quantile : 1.706617 ms ( 2.5%)
   Execution time upper quantile : 1.871717 ms (97.5%)
                   Overhead used : 1.565043 ns

Found 9 outliers in 60 samples (15.0000 %)
	low-severe	 6 (10.0000 %)
	low-mild	 3 (5.0000 %)
 Variance from outliers : 15.8231 % Variance is moderately inflated by outliers

LGTM, will merge when the build is green

Build is now green


Failing unit-test

Hi, as part of an occasional "look at how the Go eco-system is doing" project I occasionally poke at, I found a failing unit test. This looks like it shoudl be relatively easy to fix, and I would be happy to prepare a PR that changes the string looked for in the unit test, but I simply don't know the code base well enough to say if "fix the expected string" is the right fix, or if this is actually highlighting a problem. FWIW, it was also present in 0.5.0, but I can't speak for versions before that.
$ go test github.com/IBM/keyprotect-go-client
go: downloading github.com/stretchr/testify v1.4.0
go: downloading gopkg.in/h2non/gock.v1 v1.0.15
go: downloading github.com/pmezard/go-difflib v1.0.0
go: downloading github.com/davecgh/go-spew v1.1.1
go: downloading gopkg.in/yaml.v2 v2.2.2
go: downloading github.com/h2non/parth v0.0.0-20190131123155-b4df798d6542
--- FAIL: TestKeys (0.02s)
    --- FAIL: TestKeys/New_API_with_Logger (0.00s)
        kp_test.go:179:
            	Error Trace:	kp_test.go:179
            	            				kp_test.go:991
            	Error:      	Error message not equal:
            	            	expected: "parse :/api/v2/: missing protocol scheme"
            	            	actual  : "parse \":/api/v2/\": missing protocol scheme"
            	Test:       	TestKeys/New_API_with_Logger
FAIL
FAIL	github.com/IBM/keyprotect-go-client	0.033s
FAIL

I had a closer look at this, and it happens with Go >= 1.14.
It stems from a formatting change in net.url.(*Error).Error(). I think a proper fix would be to not compare the error, but instead the op and the unwrapped error, i.e.
assert.IsType(t, &url.Error{}, err)
assert.Equal(t, err.(*url.Error).Op, "parse")
assert.EqualError(t, err.(*url.Error).Unwrap(), "missing protocol scheme")

Thanks, it appears they switch the url.Error.Error() output and the unit test was fragile
Should be fixed with PR #47


AI powered "category suggestion" + automate applying tags + spell checker

i will implement all this feature
as you can see wee are showing static category blog can of any category so show them the relavant category
instatnly there is no tag in mind after writing blog so automate this
as a human people can write wrong spelling we need to check it

@ANSHIKA-26 Please can i get level 3 for this PR , its required number of trial and error to match the AI response with your current UI

@ANSHIKA-26 will i get level 3?

@ANSHIKA-26 you can review the quality of code in my PR


Network Cache Added/Removed Console Spam

After updating FTB Beyond 1.8.1 -> 1.9.0
Current versions:

Flux Networks - FluxNetworks-1.10.2-1.2.4
Sonar Core - SonarCore-1.10.2-3.2.7

Issue

Console Snippet
Don't know if world saves are the trigger, but networks appear to be removed and added constantly (fresh server restart, no players online/interacting with Flux Networks)
Some networks are chunkloaded while other are not, FTB Utilities being used for chunkloading (bringing this up knowing chunkloading issues in the past and currently)

Does the network cache file need to possibly be removed to be freshly written?
Edit: Also noticed this during server startup. Don't know if the log output just isn't working, or if the network save file can't be read properly, i.e. corrupted.

Nothing wrong with the Network Cache this is only some unnecessary logging.
Fixed in dev (inc. the server startup logging)

Ok, thanks for the update.
But being curious, is it just unclear log entries (me misunderstanding) or are the networks really being removed then added back to the network cache this often?
Are removals/additions to cache triggered by something specific (other than player interaction)?


Metrics API: how to find the last (and first) timestamps available for a metric?

It would appear, that to reliably determine, when a particular metric was last updated (or first created), a remote needs to make multiple requests.
Yet, this is, probably, the easiest thing for the server to determine -- in case of Whisper DB backend, for example, the server does not even need to open the database -- it can respond by looking simply at the timestamps of the database-file(s) or directories (such as ctime, mtime).
It should be possible to do this reliably with a single API-request -- returning either the requested timestamp (last or first) or an error, if the metric does not exist.

The problem with using ctime to determine timestamps is that they aren't always going to be reliable, but at the same time they should be better than just assuming that the last modified time is now.

Using ctime was just an example. Yes, a careless copying of the Whisper file-tree or restoring from backup could break things -- though fixing them is easy too.
And the method may not work with other storage-methods. But some way of querying these timestamps ought to be available...

Also not sure if ctime/mtime is reliable enough. I would not rely on that for making requests anyway. If you just need to get this info for analytical purposes you can use what I proposed in https://github.com/graphite-project/graphite-web/issues/2036#issuecomment-329467099

Also not sure if ctime/mtime is reliable enough.

Why? Of course, someone may mess them up either out of malice or incompetence, but the same can be said about all of the Graphite data -- there are no checksums, much less cryptographic signatures of the databases, are there?
But using ctime/mtime was just a suggestion -- a possible implementation of the feature. Whether they are used or not, the functionality is needed.

If you just need to get this info for analytical purposes [...]

I didn't think, I need to explain my use-case, but here goes... I'm developing a program to feed some already timestamped values (such as web-server logs) into Graphite. The values available may go back for weeks and months, but the program does not know, when its previous instance ran, and so it can not know -- not reliably -- which values have already been submitted and which ones are new.
It would be very useful, if it were possible for the program to query the last timestamp of the value(s) from Graphite to avoid duplication.

The simplest way to do that right now will be to call render on the series you're interested in and walk the result to find the last non-null value.

and walk the result to find the last non-null value.

Yes, thank you. This is exactly what I meant, when I wrote -- in this very ticket -- the following: to reliably determine, when a particular metric was last updated (or first created), a remote needs to make multiple requests.


More complete description of mod

I can't find a thorough description of what this mod actually does to add compatibility.
For example, I want to know how it adds compatibility for Thaumcraft. Does it add ore-gen for the Thaumcraft ores (quicksilver, amber, etc.)? Does it fix any Thaumcraft recipes? The same goes for all of the other mods.

the thaumcraft module just add Thaumium and void metal as tfc metal. i changed the way to obtain quicksilver. the rest is unchanged.

the thaumcraft module just add Thaumium and void metal as tfc metal. i changed the way to obtain quicksilver. the rest is unchanged.


Allow on build to run Powershell Az commands to get information

Is your feature request related to a problem? Please describe.
Allow on build to run Az commands to get information
Describe the solution you'd like
When bicep build is run the Az PowerShell commands should be run that are in the .bicep file. The information from the commands you can put into variables, outputs and parameters. For example
var subscriptions = Get-AzSubscription

Also should apply for any PowerShell command.

Great idea! Full support for this. This would make Bicep so much better than the ARM.

Stan, presumably this would not be limited to Az right? If I can run the Az module, I should be able to run any arbitrary powershell at that point.

Stan, presumably this would not be limited to Az right? If I can run the Az module, I should be able to run any arbitrary powershell at that point.

Yes this would be ideal, just full Powershell support so you can import and use any cmdlet, even your own.

@alex-frankel yes. I have added one last sentence that it should apply to any PowerShell cmdlet thus module. Of course there are always things that you cannot do at build so for those scenarios you will still rely on deploymentScripts.

Is there any update on this feature yet?

This would be great and was one of the leading reasons why I was excited by PSARM as you'd have it already for free

I don't see us getting to this feature anytime soon, if ever. We can revisit if there are a lot of requests/feedback asking for this.


adds WITH_EDITOR for GetMetaData to avoid crash when packaged

packaged version was crashing with errors
Signal 11 caught.
Malloc Size=262146 LargeMemoryPoolOffset=262162
CommonUnixCrashHandler: Signal=11
[2023.06.15-08.44.40:707][ 10]LogCore: === Critical error: ===
Unhandled Exception: SIGSEGV: invalid attempt to write memory at address 0x0000000000000003

[2023.06.15-08.44.40:707][ 10]LogCore: Assertion failed: !FPlatformProperties::RequiresCookedData() [File:./Runtime/CoreUObject/Private/UObject/Package.cpp] [Line: 189]
MetaData is only allowed in the Editor.
0x0000000006e761e6 sootballs_UE!UPackage::GetMetaData()()
0x000000000458d4bc sootballs_UE!URRAssetUtils::SaveObjectToAsset(...

Thanks, I added some more checks to make sure UPackage creation is only possible in Editor


Getting Error Output From Pooling

Wondering what the issue could potentially be, is this just a general error happening somewhere?
mysql_1  | 2015-11-27T21:37:45.369582Z 2 [Note] Aborted connection 2 to db: 'text_rocket' user: 'text_rocket' host: '<IP_ADDRESS>' (Got an error reading communication packets)
mysql_1  | 2015-11-27T21:37:45.369937Z 12 [Note] Aborted connection 12 to db: 'text_rocket' user: 'text_rocket' host: '<IP_ADDRESS>' (Got an error reading communication packets)
mysql_1  | 2015-11-27T21:37:57.239633Z 6 [Note] Aborted connection 6 to db: 'text_rocket' user: 'text_rocket' host: '<IP_ADDRESS>' (Got an error reading communication packets)
mysql_1  | 2015-11-27T21:37:57.241124Z 8 [Note] Aborted connection 8 to db: 'text_rocket' user: 'text_rocket' host: '<IP_ADDRESS>' (Got an error reading communication packets)
mysql_1  | 2015-11-27T21:47:40.910759Z 22 [Note] Aborted connection 22 to db: 'text_rocket' user: 'text_rocket' host: '<IP_ADDRESS>' (Got an error reading communication packets)
mysql_1  | 2015-11-27T21:47:40.910877Z 21 [Note] Aborted connection 21 to db: 'text_rocket' user: 'text_rocket' host: '<IP_ADDRESS>' (Got an error reading communication packets)
mysql_1  | 2015-11-27T21:47:53.032948Z 15 [Note] Aborted connection 15 to db: 'text_rocket' user: 'text_rocket' host: '<IP_ADDRESS>' (Got an error reading communication packets)
mysql_1  | 2015-11-27T21:47:53.034742Z 16 [Note] Aborted connection 16 to db: 'text_rocket' user: 'text_rocket' host: '<IP_ADDRESS>' (Got an error reading communication packets)

I realize their is not a lot of information to go off of here, just wondering if this coming from the console indicated anything to someone else....


Feat(eos_cli_config_gen): Support of BGP default-originate per VRF #3941

Change Summary
Adding the support of default route originate per VRF for address families EVPN and VPN-IPV4/VPN-IPV6
Related Issue(s)
Fixes #3941
Component(s) name
arista.avd.eos_cli_config_gen
Proposed changes
Changes under schema fragment router_bgp:

Under vrfs items, adding a list of dict named default_route_export
Under address_family_evpn/peer_groups items, adding a dict named default_route. Same for address_family_vpn_ipv4 and address_family_vpn_ipv6

How to test
Tested locally for 1 address family (evpn) using the 4 different flavours (default, using always, using route-map and using rcf)
Checklist
Repository Checklist

[x ] My code has been rebased from devel before I start
[x] I have read the CONTRIBUTING document.
[ ] My change requires a change to the documentation and documentation have been updated accordingly.
[x] I have updated molecule CI testing accordingly. (check the box if not applicable)

We have moved a lot of things around in the code base these last few days, so I will rebase this one for you.


Running long tasks on heroku as a detached dyno

When running long tasks on heroku as detached one-off dyno as in:
heroku run:detached rake ns:task
The terminal is not connected to the task and all output is sent to heroku logs. This is useful if you are expecting a task to take hours or days and you can't sit and wait for it.
With progress_bar enabled tasks (like sunspot:reindex) monitoring the progress is impossible as the bar will only appear at the end (concatenated in the same line). I think this is because there is no new line character sent until at the very end.
Is there a way to allow this detached mode throw the current progress every minute or a configurable percentage?

This is a workaround I'm doing now:
    pbar.increment!
    puts "\n#{Rake.application.top_level_tasks.first}: <put some descriptive language like the current processed item id>\n"

It will put a new line, forcing the progress bar (if any) to get printed, then leaves room for the next progress bar (if any).


El tree is displayed in the dialog synchronously. Use this. $refs.tree to confirm

Element UI version
2.13.0
OS/Browsers version
Window10 Chrome80.0.3987.132
Vue version
2.5.22
Reproduction Link
https://jsfiddle.net/lipengjun/x45rnk3L/12/
Steps to reproduce
点击选择上级机构
What is Expected?
能够调用this.$refs.tree.setCurrentKey
What is actually happening?
this.$refs.tree.setCurrentKey 报错

$nextTick里面调用获取ref就可以使用了


Create guide for identity provider deployment

This guide outlines a minimally viable identity provider to provide non-interactive signing for clients or services. This guide could be followed by a package registry for example to create a basic identity provider that doesn't fully implement the OIDC protocol but issued OIDC-compliant tokens.

Summary

Release Note

Documentation

Wrote this up a bit ago to help onboard a new provider who didn't want to have an interactive signing flow where a user was present. This doc outlines the requirements of an identity provider that can issue ID tokens for those who are willing to stand up their own provider. This is effectively a generalization of GitHub Actions or other CI identity providers, where the identity provider a) will provide an OIDC-compliant ID token (which can be obtained by exchanging a user credential, the service generates it on behalf of a user, etc), b) the OIDC-compliant well-known endpoint, and c) the public keys endpoint provided by the configuration at the well-known endpoint.
I might merge this with the other IDP requirements doc later on, as well as an upcoming doc around public-good policy for IDPs.
PTAL and let me know if you have any feedback!

Do we want to continue to use email as a user identifier?

Do we want to continue to use email as a user identifier?

What's the alternative, for email-based IdPs? Sigstore has support for non-email identifiers as well, but email seems appropriate when the IdP is itself an email provider 🙂

Do we want to continue to use email as a user identifier?

What's the alternative, for email-based IdPs? Sigstore has support for non-email identifiers as well, but email seems appropriate when the IdP is itself an email provider 🙂
Edit: oh, I see what you mean -- yeah, IMO we should distinguish between emails as identities and service users as identities: both are fine, but a service that provides usernames should represent them with OtherName rather than shoehorning them into an RFC 822 format for an inbox that doesn't actually exist.

There are only 2 public providers (that I know of) that also email providers. Google and Apple. Neither works directly with Sigstore.
Using iss and sub tuple is the best practice in the identity community to  identify the user.
iss is already <IP_ADDRESS>.4.1.57264.1.8 in the certificate. A new OSI value to represent the sub in the OIDC ID Token would accurately link the ID Token and the cert


Minor typo in README

Prerequisites

[X] I am an Open Source Contributor
[X] I checked to make sure that this issue has not already been filed

Description
Hi I am contributor of GSSOC'23. I noticed a minor typo in README file.
https://github.com/Rakesh9100/ML-Project-Drug-Review-Dataset/blame/main/README.md#L256
In line 256 last word of README.md, the repo name is not correct
- Music-Recommendation-System.
+ ML-Project-Drug-Review-Dataset.

Screenshots

Code of Conduct

[X] I follow Contributing Guidelines of this project.

I would like to make a PR for this same, if that's okay

Assigned @lem0n4id

@lem0n4id Your PR update

@lem0n4id Your PR update

PR is up. Apologies for the delay!


Updated method names to better reflect the functions

Thank you very much! I'm very happy when someone helps to fix up the GPGS bindings. Haven't had time for that myself.


Multi page Survey

As a Survey Specialist I want to be able to create a multi page survey so that I can guide the users through the questions.
Acceptance Criteria
When creating a survey I can choose to have questions grouped by pages
Comments must be extracted from all pages (nested components)
BONUS POINTS if it has a progress bar

Hey team! Please add your planning poker estimate with Zenhub @djnunez-aot @jadmsaadaot @saravanpa-aot @VineetBala-AOT

@jadmsaadaot Looks great. I think we all wish for a "progress bar" but I think you can let us know if that is an option and the work required. I consider the work you have done good for this task to close it. One thing though... Can we change the buttons to match the rest:


Add OSSF Scorecard GitHub Action

Is your feature request related to a problem?
No
Related OSPO Tool
automatic-contrib-prs GitHub Action, cleanowners GitHub Action, evergreen GitHub Action, contributors GitHub Action, issues-metrics GitHub Action, stale-repos GitHub Action, internal-contribution-forks GitHub App
Describe the solution you'd like
Add the OSSF Scorecard GitHub Action to all OSPO GitHub Actions and Apps
Why?
Allows us to detect supply chain security for this GitHub Action.
Actions

setup GitHub Action
add badge to README once wired-up

Describe alternatives you've considered
Tools available on the Security -> Add Tools page.
Additional context
No response

whoops.  Duplicate of https://github.com/github/github-ospo/issues/84


Display abbreviation if available

Display the RSVs abbreviation if its not just a number.
Closes #79

Thank you, this looks good! I'll merge it.