feat!: use function.knative.dev for Functions related labels

Signed-off-by: Zbynek Roubalik<EMAIL_ADDRESS>
Changes
Proposal:
We should change labels that are applied to Functions from boson.dev -> function.knative.dev (or func.knative.dev).
I am not sure which components are dependent on this, so we should be careful about the change.

Why is pkged.go updated? (I know that file is a nightmare)

I don't know 🤷♂  I can omit it from the PR.


Credential id not sent to awx when set

Describe the bug
I have an operation with specific awx credentials with id "5", the id of my credentials. My awx job templates is set without credentials but with "ask credential on launch".
The field "Default credentials ids" in the operation page is not sent when launching the operation, AWX does not see any credentials provided. it is like the field is totally ignored. If i call my job template from awx and credentials set when asked, the credential appears well in the job but not when calling from SQuest.
My job templates are created with the AWX API automatically (i know there is some problems with this way, like some missing attributes in  awx objects that can lead to bug, i have another example with min and max value from awx survey when not set for character field)
To Reproduce
Steps to reproduce the behavior:
Create a job templates with empty credentials in awx and the option ask credentials on launch, set credentials ids in the corresponding of an operation in SQuest,
Expected behavior
Send the credential id from the field in the operation detail when calling awx job templates
Screenshots
the field with its value

when calling from SQuest, no credential appears

when calling from awx:

Squest version or GIT commit number:
2.6.0
Ansible Tower/AWX version:
24.5.0

the credentials is a custom credential type not an awx native one

Interesting. We'll take a look. Thanks for reporting !
As a workaround I guess you figured it out by yourself but you can create a clone of your Job template with different credentials set for each.

I can confirm, I see this as well. Both adding the int directly like @delloos did and {{ request.instance.spec.cred }} (which I made during testing).
Squest: 2.6.0
RHAAP: 4.5.8

I'm not able to reproduce. I've set an ID in one of my operation

When I reach the approve page, I can see the credentials dropdown is well updated wit the value set in the operation

Is your operation set to auto process ?


Restore-GPO with -BackupId parameter recreates missing GPO but documentation says that should fail

The Description section of the Restore-GPO documentation says, "if the GPO no longer exists in the domain, the cmdlet fails." I find that's true if I identify the GPO with the -Name or -Guid parameters. But using the -BackupId parameter works, it recreates a missing GPO. Is this intended and reliable functionality that I can depend on?
I observed this on a Windows Server 2019 domain controller in a Windows Server 2016 domain.  The domain only has one DC and the commands were run locally on the DC so I don't think I'm getting a false result due to replication delays or other factors.  This is with PowerShell 5.1 and version <IP_ADDRESS> of the GroupPolicy PowerShell module.  To reproduce, either run Restore-GPO with the -BackupId parameter or pass a GpoBackup object to Restore-GPO through the pipeline, for example, given a GPO "Test GPO":
$Backup = Backup-GPO -Name "Test GPO" -Path <backup path>
Remove-GPO -Name "Test GPO"
# Calling Restore-GPO with -Name parameter gives "GPO was not found" exception, consistent with documentation.
Restore-GPO -Name "Test GPO" -Path <backup path>
# Also GPO not found using -Guid parameter, consistent with documentation
Restore-GPO -Guid "<GPO Guid>" -Path <backup path>
# This works, using -BackupId parameter, contrary to documentation, and this also works with the string literal of the backup Id.
Restore-GPO -BackupId $Backup.Id -Path <backup path>
# This works too
$Backup | Restore-GPO

The above works with and without removing the GPO, but my question is in the case of removing the GPO, Restore-GPO works when the documentation says it would fail, but only with the -BackupId parameter.  Thank you very much.

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

ID: c93a37fb-a7f2-025a-90d6-a48e1bf1e6b1
Version Independent ID: e23abbeb-19ae-469f-a24f-7ae35e26d229
Content: Restore-GPO (GroupPolicy)
Content Source: docset/winserver2022-ps/grouppolicy/Restore-GPO.md
Product: w10
GitHub Login: @JasonGerend
Microsoft Alias: jgerend

To make it easier for you to submit feedback on articles on learn.microsoft.com, we're transitioning our feedback system from GitHub Issues to a new experience.
As part of the transition, this GitHub Issue will be moved to a private repository. We're moving Issues to another repository so we can continue working on Issues that were open at the time of the transition. When this Issue is moved, you'll no longer be able to access it.
If you want to provide additional information before this Issue is moved, please update this Issue before December 15th, 2023.
With the new experience, you no longer need to sign in to GitHub to enter and submit your feedback. Instead, you can choose directly on each article's page whether the article was helpful. Then you can then choose one or more reasons for your feedback and optionally provide additional context before you select Submit.
Here's what the new experience looks like.
Note: The new experience is being rolled out across learn.microsoft.com in phases. If you don't see the new experience on an article, please check back later.
First, select whether the article was helpful:

Then, choose at least one reason for your feedback and optionally provide additional details about your feedback:

Article was helpful
Article was unhelpful

Finally, select Submit and you're done!


improve behavior and fix bugs in CLI history handling and completion

-if readline.set_auto_history() is not implemented, as in pyreadline3, will fall back gracefully to automatic history saving. The only issue with this is that !history commands will be recorded in the history.
-!fetch on missing file no longer crashes script
-!history is now one of the autocomplete commands
-.dream_history now stored in output directory rather than ~user directory.
An important limitation of the last feature is that the history is loaded and saved to the .dream_history file in the --outdir directory specified at script launch time. It is not swapped around when the --outdir is changed during the session.

LGTM.
I'd consider adding !clear as an option to clear history.

LGTM. Thank you for the changes.
I'd consider adding !clear as an option to clear history.

That's a nice idea. I'll add it to the list. The other thing I'd like to do is to add a !search function to search through the history.

LGTM. Thank you for the changes.
I'd consider adding !clear as an option to clear history.

That's a nice idea. I'll add it to the list. The other thing I'd like to do is to add a !search function to search through the history.

That would be fantastic. Also I'd recommend adding !history 10 or something to only show the last 10 results. This might be handy if there's a hundreds of history lines.


API: Add 'ref' for primitives for direct access to Node

This change proposes adding a ref to the primitive nodes, that gives access to the underlying node. This isn't meant to be a common scenario by any means, but there are a few reasons I think we need this:

For a control like <Slider />, we need to know the calculated layout values (the width/height) of the component. We can get that directly via the node, but perhaps a better event would be useful for that down the road - like onLayoutChanged?
For a widget like <Clickable />, we really want to capture the mouse input at the start of the mousedown gesture, and then, when it is released, check if the mouseup occurred in the bounds of the widget. We can use the hitTest method on the node for this.
For focus management - we need some underlying handle to call focus on - I think the node is a natural choice

I'm open to other ideas for this (exposing ref always feels dirty 😄 ), but this can at least help us move forward on some of these other UI widgets.

Thanks for the review, @OhadRau ! 🎉

The one question I have is whether we want to use the term id here, as this could cause some confusion to people coming from HTML/if we want to use external stylesheets in the future.

Good point, I didn't think about this - I could see confusion. Do you have any alternatives? The only thing I can think of is perhaps making it uniqueId, but I'm not sure if that is better?

Thanks for the suggestions, @OhadRau ! Went with internalId 👍


Add new article for ExportTo for Paginated Reports

Adding a new article for ExportTo for Paginated Reports (as there are a lot of differences to ExportTo for Power BI Reports).
The samples contain code (ReportName & ResourceFileExtension properties) that is yet to be released and it also needs to linked to from the doc tree once checked in.
This is the first draft and will be reviewed in the product team as well.

@onegoodsausage : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Hi @onegoodsausage - Working on a draft article would best be done in the private repository (you are currently working in the public repo). The article will have to be moved to the private repo before being published, in any case, so the content can be validated and viewed on staging before publishing, added to a TOC, be PR-reviewed, etc.
For more information, see Should I work in a private or a public repo?
If you need help getting set up to work in the private repo, see Set up Git repository locally for documentation.
Would you close this PR and create a pull request in the private repo instead? Thanks.
cc @kfollis

Closing this PR as suggested


Issue #1734 - support :in and :not-in modifiers for Token search

Signed-off-by: Mike Schroeder<EMAIL_ADDRESS>

I wonder if we'll want to support the same COMMON_TOKEN_VALUE optimization that we made for the normal case...
See #1929 for more detail.

I wonder if we'll want to support the same COMMON_TOKEN_VALUE optimization that we made for the normal case...
See #1929 for more detail.

Not sure we can do that here since we're dealing with a list of values.

I wonder if we'll want to support the same COMMON_TOKEN_VALUE optimization that we made for the normal case...
See #1929 for more detail.

Not sure we can do that here since we're dealing with a list of values.

Since issue #1733 will use very similar SQL constructs, use of COMMON_TOKEN_VALUE optimization will be investigated as part of that work.

I wonder if we'll want to support the same COMMON_TOKEN_VALUE optimization that we made for the normal case...
See #1929 for more detail.

Not sure we can do that here since we're dealing with a list of values.

Since issue #1733 will use very similar SQL constructs, use of COMMON_TOKEN_VALUE optimization will be investigated as part of that work.

Mike opened #2184 for making this possible, so I think this PR is good-to-go.


[1.3.x] RHIDP-3816: feat(homepage): enable plugins to extend the homepage

This is a manual cherry-pick of #1532, only yarn.lock had a conflict.
/cc @gashcrumb @ciiay @invincibleJai
/assign @jerolimov

/test e2e-tests

/retest

/approve

/retest

Closing this as we couldn't ensure yet that it breaks the customizable sidebar.

/lgtm
Verified the changes and works as expected

I've verified the latest build pr-1649-7cdfd42 on a cluster with helm as well:

Without any customization:

With custom homepage with MarkdownCard and Markdown:

With two SearchBars:

@invincibleJai asked me to add hold to wait for @nickboldt ACK that we can merge this right now.
/override "SonarCloud Code Analysis"
/hold
/cc @nickboldt

/retest

Unhold this PR based on the slack conversation here and below.
/unhold
/test e2e-tests

Note: this is blocker, since incomplete for feature and code freeze but must be in 1.3

/test all

/override ci/prow/e2e-tests


header not proper

not arrenged properly , also have colour difference

Yeah Fixed and push done.
@subhadipbhowmik look once

okk

I pushed like Bug: Navbar Links are properly centered and after hover bg-color fixed instead of header not proper #212.
@Amankr200 @subhadipbhowmik  Look Once.
Thank You.


Client side dependency bump

What this PR does / why we need it:

Updated all dependencies to latest versions,
Fixed a few lint problems due to new linter rules,
Addressed some unit test flakiness

Which issue(s) this PR fixes
Fixes #788

Calling out more explicitly a part of this PR more explicitly, prettier 2.0 always defaults to using arrow function parentheses but it looks like we are keeping it to the 1.x behavior for the time being.

Calling out more explicitly a part of this PR more explicitly, prettier 2.0 always defaults to using arrow function parentheses but it looks like we are keeping it to the 1.x behavior for the time being.

Right.  I decided to keep it as is for now as it would require quite a few changes, plus actually I like it more the way it is.


Fix #3597

This change is

@dotnet-bot test daily_slow_x64_test

@dotnet-bot test Windows ci_slow_x64_test

@dotnet-bot test Windows daily_slow_x64_test

You could run all the slow tests if you wanted as well. https://github.com/Microsoft/ChakraCore/wiki/Jenkins-Build-Triggers#daily-builds-with-slow-tests


Add Bitbucket 6 compatibility

Pull Request (PR) description
Adds compatibility with Bitbucket 6, including on Ubuntu 18.04
This Pull Request (PR) fixes the following issues

Hi @dickp. thanks for the PR. I had a few minutes and gave this a quick review. Please join us on our IRC chat #voxpupuli on freenode or our slack at http://slack.puppet.com/ if you've any questions (or respond here in the PR).


Exception ignored in: function CapturableResource.del after upgrading to TF 2.5

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): MacOS X 11.2.3
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: No
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): v2.5.0-rc3-213-ga4dfb8d1a71 2.5.0
Python version: 3.8.6
Bazel version (if compiling from source): No
GCC/Compiler version (if compiling from source): No
CUDA/cuDNN version: No
GPU model and memory: No

Describe the current behavior
After upgrading from TF 2.4.1 to TF 2.5.0 i see strange messages in console when run training/testing of my model. See logs below.
Describe the expected behavior
No ignored exceptions should be printed
Contributing - Do you
want to contribute a PR? (yes/no): No
Standalone code to reproduce the issue
https://colab.research.google.com/drive/1IpmIj3WI17j6JkfgGWH0YEpowja7m71Y?usp=sharing
Other info / logs
In some cases i got only such logs
Exception ignored in: <function CapturableResource.__del__ at 0x15ad1c790>
Traceback (most recent call last):
  File "/Users/alex/.pyenv/versions/3.8.6/lib/python3.8/site-packages/tensorflow/python/training/tracking/tracking.py", line 277, in __del__
    self._destroy_resource()
  File "/Users/alex/.pyenv/versions/3.8.6/lib/python3.8/site-packages/tensorflow/python/eager/def_function.py", line 889, in __call__
    result = self._call(*args, **kwds)
  File "/Users/alex/.pyenv/versions/3.8.6/lib/python3.8/site-packages/tensorflow/python/eager/def_function.py", line 924, in _call
    results = self._stateful_fn(*args, **kwds)
  File "/Users/alex/.pyenv/versions/3.8.6/lib/python3.8/site-packages/tensorflow/python/eager/function.py", line 3022, in __call__
    filtered_flat_args) = self._maybe_define_function(args, kwargs)
  File "/Users/alex/.pyenv/versions/3.8.6/lib/python3.8/site-packages/tensorflow/python/eager/function.py", line 3444, in _maybe_define_function
    graph_function = self._create_graph_function(args, kwargs)
  File "/Users/alex/.pyenv/versions/3.8.6/lib/python3.8/site-packages/tensorflow/python/eager/function.py", line 3279, in _create_graph_function
    func_graph_module.func_graph_from_py_func(
  File "/Users/alex/.pyenv/versions/3.8.6/lib/python3.8/site-packages/tensorflow/python/framework/func_graph.py", line 999, in func_graph_from_py_func
    func_outputs = python_func(*func_args, **func_kwargs)
  File "/Users/alex/.pyenv/versions/3.8.6/lib/python3.8/site-packages/tensorflow/python/eager/def_function.py", line 672, in wrapped_fn
    out = weak_wrapped_fn().__wrapped__(*args, **kwds)
AttributeError: 'NoneType' object has no attribute '__wrapped__'

But in another, it prepended with another one:
  Traceback (most recent call last):
    File "/Users/alex/.pyenv/versions/3.8.6/lib/python3.8/site-packages/tensorflow/python/framework/ops.py", line 2560, in get_attr
      pywrap_tf_session.TF_OperationGetAttrValueProto(self._c_op, name, buf)
  tensorflow.python.framework.errors_impl.InvalidArgumentError: Operation 'raggedconcat_assert_equal_3_assert_assertguard_placeholder_1' has no attr named '_class'.

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
    File "/Users/alex/.pyenv/versions/3.8.6/lib/python3.8/site-packages/tensorflow/python/training/tracking/tracking.py", line 277, in __del__
      self._destroy_resource()
  ...
    File "/Users/alex/.pyenv/versions/3.8.6/lib/python3.8/site-packages/tensorflow/python/eager/def_function.py", line 672, in wrapped_fn
      out = weak_wrapped_fn().__wrapped__(*args, **kwds)
  AttributeError: 'NoneType' object has no attribute '__wrapped__'

Can you share a very very minimal standalone code example that we could copy, paste and run or a Colab to reproduce this?

Here is a sample code to reproduce issue
test.py.zip
Also i made a demo in colab https://colab.research.google.com/drive/1IpmIj3WI17j6JkfgGWH0YEpowja7m71Y?usp=sharing
Note, that it should be runned from console, not from notebook
As far as i noticed, the issue gone if code from "main()" function is moved to the top level (drop "def main" line and remove tabs in body code)

@shkarupa-alex
I  reproduced the code shared with no errors in tf-nightly.please find the gist.Thanks

I am seeing this exception get printed a lot in my code, and found this example of it also showing up in the Tensorflow docs:
https://www.tensorflow.org/tfx/tutorials/transform/census?hl=el#put_it_all_together_2
Exception ignored in: <function CapturableResource.__del__ at 0x7ff6dd76f050>
Traceback (most recent call last):
  File "/tmpfs/src/tf_docs_env/lib/python3.7/site-packages/tensorflow/python/training/tracking/tracking.py", line 277, in __del__
    self._destroy_resource()
  File "/tmpfs/src/tf_docs_env/lib/python3.7/site-packages/tensorflow/python/eager/def_function.py", line 889, in __call__
    result = self._call(*args, **kwds)
  File "/tmpfs/src/tf_docs_env/lib/python3.7/site-packages/tensorflow/python/eager/def_function.py", line 924, in _call
    results = self._stateful_fn(*args, **kwds)
  File "/tmpfs/src/tf_docs_env/lib/python3.7/site-packages/tensorflow/python/eager/function.py", line 3022, in __call__
    filtered_flat_args) = self._maybe_define_function(args, kwargs)
  File "/tmpfs/src/tf_docs_env/lib/python3.7/site-packages/tensorflow/python/eager/function.py", line 3444, in _maybe_define_function
    graph_function = self._create_graph_function(args, kwargs)
  File "/tmpfs/src/tf_docs_env/lib/python3.7/site-packages/tensorflow/python/eager/function.py", line 3289, in _create_graph_function
    capture_by_value=self._capture_by_value),
  File "/tmpfs/src/tf_docs_env/lib/python3.7/site-packages/tensorflow/python/framework/func_graph.py", line 999, in func_graph_from_py_func
    func_outputs = python_func(*func_args, **func_kwargs)
  File "/tmpfs/src/tf_docs_env/lib/python3.7/site-packages/tensorflow/python/eager/def_function.py", line 672, in wrapped_fn
    out = weak_wrapped_fn().__wrapped__(*args, **kwds)
AttributeError: 'NoneType' object has no attribute '__wrapped__'

Ccing @robert-crowe.
Facing a similar problem.

Any update on this?

Any update on this?

No issue at 2.6.0

This is a side effect of how Evaluator expects to receive examples, and can be fixed by adding to the ModelSpec in the EvalConfig:
model_specs {
  signature_name: "serving_default"   <--- ADD THIS
  label_key: "tips"
}

So far, this has always fixed this problem for me.

@rcrowe-google running into this weirdly enough. Do you know any other reason this may cause it? We dont have Evaluator on the pipeline

@rcrowe-google running into this weirdly enough. Do you know any other reason this may cause it? We dont have Evaluator on the pipeline

I've garbage collected those neurons.  Do you have a code sample to reproduce?

So we actually ran the TFX taxi quickstart in a k8s pod (without Evaluator). However we have now been able to work around it, so no pressure. Will ping back if we hit it again.


Regression in build times for Travis CI using 2.2.300 SDK

From @martincostello on Saturday, June 8, 2019 9:32:34 AM
I've noticed across several different projects I maintain that since the SDK was updated from 2.2.1xx or 2.2.2xx to 2.2.300, the time to build the projects in Travis CI has regressed by up to an order of magnitude on both Linux and macOS.
However I'm not seeing the same regression in Azure DevOps pipelines for Linux, macOS or Windows, or AppVeyor for Windows.
Below are a selection of projects that show a build time regression immediately after merging a PR that contains a commit that updates the SDK to 2.2.300:

History
Build time pre-update
Build time post-update
Delta
PR with SDK update
Commit with SDK update

project-euler
3 min 40 sec
37 min 13 sec
+1,015%
#33
b2c7ed3

JustEat.StatsD
2 min 33 sec
12 min 19 sec
+483%
#177
4f4ac55

sqllocaldb
3 min 31 sec
16 min 28 sec
+468%
#88
671307a

adventofcode
7 min 4 sec
31 min 51 sec
+450%
#72
8ecc3a7

JustSaying
6 min 49 sec
25 min 55 sec
+380%
#545
88f241c

httpclient-interception
6 min 26 sec
16 min 26 sec
+255%
#85
065c722

alexa-london-travel-site
5 min 34 sec
11 min 31 sec
+206%
#267
48b47a5

api
5 min 54 sec
9 min 46 sec
+165%
#112
40c1dee

website
4 min 26 sec
7 min 13 sec
+162%
#263
3a43580

My hunch is that it is related to the new "progress bar" when running dotnet test which is causing the Travis agents to waste a lot of time trying to "draw" it because the actual test run times printed in the build output are equivalent:

Build before - Time Elapsed 00:00:10.86
Build after - Time Elapsed 00:00:15.31
Test before - Test execution time: 46.8778 Seconds
Test after - Total time: 46.5308 Seconds

Copied from original issue: dotnet/sdk#3314

From @martincostello on Saturday, June 8, 2019 9:35:12 AM
Maybe requires integration of https://github.com/microsoft/vstest/pull/2024? These projects are all using the 16.1.1 NuGet reference, which shows no improvement (commit, build).

From @martincostello on Saturday, June 8, 2019 9:42:31 AM
Related fix: https://github.com/dotnet/cli/pull/11497

From @livarcocc on Monday, June 10, 2019 8:53:19 PM
Just to confirm further this is potentially a regression on vstest, would it be possible for you to gather these numbers if you turned off tests on your CI, just to collect data?
cc @singhsarab

From @singhsarab on Tuesday, June 11, 2019 8:25:59 AM
@martincostello
Progress indicator would not come into play if Console.IsOutputRedirected is set, which I am guessing should be true.
I looked at logs of one of the PRs, https://travis-ci.org/justeat/JustEat.StatsD/jobs/541122616, the total time reported for test run is 10 seconds, let's add some start and cleanup time, even then it should not call for printing the progress bar more than 20 times as it is called after an interval of 1 sec.
Can you please enable logging and share the logs with me?

From @martincostello on Tuesday, June 11, 2019 8:28:11 AM
@singhsarab Can you let me know exactly what logging parameters you need setting through dotnet test (info, verbose, debug?), and I'll do a PR to add them to the slowest run and see what happens.

From @singhsarab on Tuesday, June 11, 2019 10:26:43 AM
@martincostello You can use --diag:log.txt argument
https://github.com/microsoft/vstest-docs/blob/master/docs/diagnose.md#dotnet-test

From @martincostello on Tuesday, June 11, 2019 11:04:00 AM
There's a test running now, it hasn't gotten as far as printing out anything yet, but it seems like whatever is slow is running after the last test finishes before the process exits.

From @martincostello on Tuesday, June 11, 2019 12:58:12 PM
There appears to be a 17 minute gap between these two log messages:
TpTrace Verbose: 0 : 5334, 9, 2019/06/11, 12:37:13.427,<PHONE_NUMBER>60, vstest.console.dll, ParallelProxyExecutionManager: HandlePartialRunComplete: Total completed clients = 1, Run complete = True, Run canceled: False.
TpTrace Verbose: 0 : 5334, 9, 2019/06/11, 12:54:14.143,<PHONE_NUMBER>773, vstest.console.dll, TestRunRequest:TestRunComplete: Starting. IsAborted:False IsCanceled:False.

From @livarcocc on Wednesday, June 12, 2019 11:58:36 PM
@singhsarab is @martincostello's lastest reply and logs enough for you to make headway on this?

From @singhsarab on Thursday, June 13, 2019 12:43:37 AM
@martincostello Thanks for the logs. I am not able to come up with a hypothesis right away. There seems to be some issue while clean up.
Is this issue happening only on travis CI ? I am trying to see if I can get a local repro to debug this one.

From @singhsarab on Thursday, June 13, 2019 12:45:08 AM
Let's transfer this to microsoft/vstest, will help us track this better

From @martincostello on Thursday, June 13, 2019 5:37:05 AM
@singhsarab Yes, only Travis CI. Locally, AppVeyor and Azure DevOps Pipelines are all fine.

From @martincostello on Thursday, June 13, 2019 5:58:37 PM
@singhsarab This issue does not seem to affect .NET Core 3.0 preview 6: https://travis-ci.org/martincostello/project-euler/builds/545376053

From @martincostello on Monday, June 17, 2019 7:39:00 PM
One thing I've noticed that's different in Travis CI compared to Azure Dev Ops is that Test run in progress.. gets printed to the console a lot in Travis, but not in Azure.
Could something different be making vstest think it should be printing progress to an interactive console, rather than say not because $(CI) is true in the environment?

this should be fixed via https://github.com/dotnet/cli/pull/11497, will keep it open for tracking

I stumbled upon this issue as well. Our build times went up from around 1 minute to over 30 minutes.
I fails using the 2.1.700 sdk, rolling back to 2.1.604 solved the issue temporarily, but we are interested to know if there is another workaround. We would like to update to dotnet 2.2.

I believe the fix for this is in the 2.2.301 SDK that was just released.

It looks like Travis has now incorporated the latest SDK releases.

Thanks for confirmation @JSkimming @martincostello. Closing this issue.

Since this issue is closed, posted a new issue since this issue still occurs with 2.2.401 on CircleCI
https://github.com/microsoft/vstest/issues/2120

I'm also still observing this with the 3.0.100-preview8-013656 SDK - has the fix been ported to the 3.0.0 SDK yet?


Allow GraphQL service components to query via GraphiQL in Definitions screen of API Docs

Context

I did some digging into this problem and I found a way to reproduce it

Go to https://demo.backstage.io/catalog/default/api/starwars-graphql/definition
Add the following query and hit play button

{
  allFilms {
    edges {
      node {
        id
    }
  }
}
}

You'll get the following error.

{
  "errors": {
    "message": "Cannot use 'in' operator to search for 'subscribe' in null",
    "stack": "TypeError: Cannot use 'in' operator to search for 'subscribe' in null\n    at $r (https://demo.backstage.io/static/550.ae2c2479.chunk.js:80:297)\n    at https://demo.backstage.io/static/550.ae2c2479.chunk.js:49:169"
  }
}

This error is actually GraphiQL's attempt to parse response from the default fetcher.
This is happening because GraphQlDefinition doesn't use the fetchers that are configured in apis.tsx.
Feature Suggestion
My understanding of the use case here is to allow users to query the API. Api Docs seems to be setup to use GraphiQL for documentation but not for querying. GraphiQL plugin can query using fetchers.
Possible Implementation
We could allow querying from GraphQLDefinitionWidget which would require providing a way to reuse or configure fetchers. Alternatively, we could change how we should documentation for GraphQL to no use GraphiQL.

There may be some confusion here and I completely understand why. The definition in apis.ts for graphQlBrowseApiRef is meant for the @backstage/plugin-graphiql plugin. Although the @backstage/plugin-api-docs plugin uses the same component (https://github.com/graphql/graphiql), they are not connected in any way.
Introspection and querying would be nice in the api-docs version. However, discussed in #5590, doing so in a generic way that works across all catalog api's and org envs might be tricky to cover sufficiently. That said, having a programmatic interface similar or possibly shared across the graphiql and api-docs plugins might be the way to go here. There could be a shared package with the graphql endpoint config, etc. which requires programmatic wiring in the app or backend (possibly proxy in some cases?). There would need to be some gluing metadata to match a catalog api entity to an appropriate endpoint config though.

I think this issue should be reopened because users keep bumping into it.

Our team is going to be looking into the GraphQL docs situation internally starting next week. There might be something we can contribute back once we have a closer look at this.
@taras - Do you have any particular ideas/thoughts on this? In my mind there are 2 things here. There is documentation (usually best done with static docs generators) & there is the interactive usage of the schemas (typically through introspection). Graphiql v2 was released and is much more modular so was thinking of investigating what it offers over the current v1. Beyond that, it's an open road.

@andrewthauer I've been keeping an eye on GraphQL documentation options. I haven't found anything. Did your look at the new GraphiQL docs yield anything?

@andrewthauer I've been keeping an eye on GraphQL documentation options. I haven't found anything. Did your look at the new GraphiQL docs yield anything?

@taras - Unfortunately, plans changed and we haven't looked into this further. For pure GraphQL documentation there is now https://magidoc.js.org. However, it's not a react component so it would likely require building static sites in CI, etc. and then having a link out to the static site. However, I haven't tried it out so perhaps there might be a nicer way. I kind of thing there are 2 personas here. One where someone wants to interact with the GraphQL schema using introspection and the other is a more traditional API documentation approach. Perhaps there is a new for both given the GraphQL SDL itself isn't really tailored to do both really well (or at all) like OpenAPI can.

Did this ever make it into the RFC? I do agree that it's currently confusion that it uses Graphiql to give the illusion that your query is going to work. I'd almost rather see it just render the schema in a decent format if getting it to run actual queries is too big of a hill to climb.

Did this ever make it into the RFC? I do agree that it's currently confusion that it uses Graphiql to give the illusion that your query is going to work. I'd almost rather see it just render the schema in a decent format if getting it to run actual queries is too big of a hill to climb.

I don't think there is an official RFC, but there have been a few related GH issues on the general subject and improvements of the GraphQL API Docs experience. I think we should probably split this into a couple of issues? For example:
a) Remove the confusing GraphiQL query building and execution and just have a pure "docs" view.
I started playing around with GraphiQL v2 and it appears you can compose just the docs part without the rest of the editor. However, it's a bit sparse and looks funny initially. Maybe some styling would help. Another option is to use something like https://magidoc.js.org/ which is purpose built for this, but since it's a static site generator it doesn't integrate with react in any way and would either need build & hosted externally and linked to.
b) Allow API Docs of type graphql to be interactive similar to OpenAPI
Since the GraphQL SDL spec doesn't support these annotations out of the box we'd need to define a way to do this. Possibly options are through custom annotations on the SDL, having an annotation configuration on the related entity to define the connection, through code, through app-config.yaml or a combination. Technically not hard, but a proposal would be required to handle appropriate uses cases and requirements (connection types, auth, etc.)

@andrewthauer Thanks for your thoughtful feedback. I like A for now. I don't know about you, but our GraphQL Api's expose a playground off each API and there isn't a place to drop that link on the definition page. So, a definition page that 1) links to the playground for the API (if available) and lists out the spec for browsing would clear up any confusion.

So we already have the Raw view of the SDL. Would be really nice if it was syntax highlighted though. Might be something to also investigate. Few potentially immediate options I see are:

Replace the graphiql page with a component that can read some annotation that links to a dedicated docs site (e.g. graphql.org/docs-site-url: https://some.place.hosting/graphql/api/
Look at upgrading to graphiql v2 and only showing the Docs part.
A combination of the 2 or possibly providing a pick and choose model between the existing view and a new view.

Technically removing the graphiql view and adding support for a custom annotation shouldn't be too difficult. The challenge being this would be a breaking change from a feature/user perspective potentially. Granted it might not be that big of a deal. Technically you can override the entire component now, so another approach could be to provide a new component that links to docs as the default or optionally configurable to replace the current view.
I'd love to contribute this, but given my focus, I definitely won't have the time in the short to medium term.

Any alternative solutions to this? I would like to see our developers running queries from the GraphiQL interface rather than using that interface for just showing the schema

Since the GraphQL SDL itself does not contain provisions for auth, endpoints etc like OpenAPI this would require something custom which entities themselves may need to provide this information or be coded outside the API spec. Might be worth looking at the new graphql-voyager plugin. I haven't tried it myself but am curious if it could be adapted to the API docs plugin in a more general way. I think the problem again being that it requires introspection and this could require auth which could need to be handled differently for each API.

@andrewthauer the voyager might be a good option. I was setting it up earlier and there is one wrinkle. It requires voyager.worker.js to be added to the public directory. It's in node_modules. I don't know if there is an API for adding files from node_modules to public directory from a plugin.

@taras @andrewthauer seeing that this issue has gone stale and closed, is there a different plan for GraphQL APIs to be executed from within Backstage?

@shrutiyer do you mean to experiment with a GraphQL API in API Docs?

Correct. Similar to the "Try it out" feature within swagger/openapi specs. Is there any feature planned to do the same for GraphQL APIs?

Part of the challenge is that it's unclear how this should be solved. Each backend usually needs credentials and we don't have a way to provide these. We discussed remove the "try it" and replacing it with just documentation but it wasn't a priority for anyone.

@taras @andrewthauer Seems we cannot query the graphql apis in backstage but only can view the schema with the existing code??                       if I integrate @backstage/plugin-graphiql, will this allow me to query the graphql endpoints from the backstage UI?

@shalinichennoju - The graphiql plugin will let you query through introspection when configured for each endpoint. However, this is a separate UI and plugin from the api-docs plugin and not based on the catalog or API entities.

started to work on some enhancements for this one. First for plugin-graphiql, I added a function to GraphQLEndpoints.ts to allow it query all API with type=graphql, then create the endpoints automatically. This depends on a annotation for the API entity. (backstage.io/api-graphql-url). then in GraphiQLPage.ts, I call this function after the GraphQLBrowserAPI.getEndpoints().
With this approach, when I enabled graphiql plugin, I can play with the APIs that defined with API entities.
another change I made is to replace the tab with Select and also set another annotation backstage.io/api-graphql-url-auth-url for remind user where to get the token for querying this graphql api.
The last change I made is to upgrade the graphiql plugin to 3.0.5 which is the latest, I am still working on some details of this change, and would like to raise a PR for this enhancements.

https://github.com/backstage/backstage/pull/19312


🐞 [BUG] There is a potential bug in using the function useStoryblok to get data in livePreview: true mode

Describe the issue you're facing
e.g: when you edit the homepage in real time in the visual editor (it really works), but when you edit the [...] .astro file, the rendered page will not be consistent with your edits.
Figure 1: Visual editor: livePreview

Figure 2: [...slug].astro after being modified

[!CAUTION]
The data obtained after modifying [...slug].astro is still a version from a long time ago.

Reproduction
Please refer to playgound/ssr
Steps to reproduce
No response
System Info
Astro                    v5.0.9
Node                     v20.18.0
System                   macOS (x64)
Package Manager          pnpm
Output                   server
Adapter                  @astrojs/vercel
Integrations             @astrojs/svelte
                         @astrojs/vue
                         @astrojs/react
                         @storyblok/astro
                         @astrojs/tailwind

Used Package Manager
pnpm
Error logs (Optional)
No response
Validations

[x] Follow our Code of Conduct

Hey @JakiChen, thank you for reporting this. In most real-world scenarios, content editors would use a dedicated, deployed preview environment that is not undergoing code changes while content is being edited. 🙂
Please note that useStoryblok will be deprecated fairly soon in favor of the new getLiveStory function. Stay tuned for the release and announcement.


Create a dark theme

That's important. Many friends told me it would be great.
It shouldn't be done right now as some major changes are on the road.

Related to #16.
a theme.scss could be great. Or simply a color.scss modifying every color.

Aaaaand it's done.


Bundle does not find gems after bundle install.

Bundle failed to find nokogiri and other gems that is build with native extension.
The gems that is used is packaged during pre-build pipeline by running
bundle package --all.
In build stage, gems were install using bundle install --binstubs --local --path vendor/bundle but
bundle check throws me the following error.
The following gems are missing
 * nokogiri (1.10.5)
 * nio4r (2.5.2)
 * websocket-driver (0.6.5)
 * bloomfilter-rb (2.1.1)
 * byebug (9.0.6)
 * json (2.1.0)
 * semian (0.9.1)
 * shoulda-callback-matchers (1.1.4)
Install missing gems with `bundle install`

while the gems are found in
vendor/bundle/ruby/2.4.0/extensions/x86_64-linux/2.4.0-static.
I tried renaming the folder to
vendor/bundle/ruby/2.4.0/extensions/x86_64-linux/2.4.0
and the gems was found.
bundler version : 1.17.3
Any idea what could be the cause of this issue ?

Found out that this is more of a rbenv issue. Refer: https://github.com/rbenv/ruby-build/issues/1387


'libhostpolicy.so' required to execute the application was not found

I created an MVC .Net Core 1.1 application. It works on windows and I'd like to run in my raspberry py too.
But It doesn't work.
Environment:

VS17 enterprise
Mvc .net core 1.1
Raspberry pi with Debian 9.4
Repo on github

Expected behavior
After publishing in windows for linux-arm I have pull my repo into raspberry, but when
I run
dotnet  myapp.dll
I have the error:
A fatal error was encountered. The library 'libhostpolicy.so' required to execute the application was not found in [path]
Actual behavior
It doesn't work and I don't know how to solve

.NET Core 1.* didn't support arm images.  .NET Core 2.1+ has support for arm32v7 images which are compatible with Raspberry Pi devices.


Feature boxplot figure

adds enhancement described in https://github.com/blab/pathogen-embed/issues/8

@nandsra21 Thank you for getting this started! I rebased this branch onto main just to keep this branch's changes separate from those in other branches and I pushed a couple of commits that convert the plotting logic to use base matplotlib, so we don't need to keep the seaborn dependency. In some ways, commit 116372c simplifies logic a bit by removing the "scatterplot" function (which we needed in the context of the paper's analyses) in favor of working with scipy's "compressed distance matrix" format where we know each entry in the genetic distance matrix maps one-to-one with the corresponding position in the Euclidean distance matrix. In other ways, the commit makes the logic more complex by needing to group Euclidean distances by genetic distance for matplotlib's boxplot function. Also, matplotlib's boxplot function is way more verbosely configured than the seaborn implementation!
For your reference, here is what the boxplots looked like with the seaborn implementation you originally pushed to the branch:

And here is what the plots look like after my changes:

One important subtle difference is that the new implementation creates a boxplot entry on the x-axis for every integer value between the min and max genetic distance even for genetic distances we didn't observe. This means the observed genetic distance of 76 appears on the x-axis at position x=76 (see the small gray median line tick), while our original seaborn implementation placed that same distance value at position 71 (see the small blue/gray tick in the original plot above). This means our original plots for the paper need to be updated, too, to make sure that the boxes are placed on the x-axis position that matches the genetic distance.


Make actual releases

I know being able to tweak the code is nice and building it is easy but it's so much more of a hassle than a simple DLL!

Can I just know.... why not?


I want to get a PFS service from the service registry

User Story
As Chris I want to get a PFS service from the service registry so that I can use any PFS service in the network
See Raiden Client implementation
Acceptance criteria

Get the data from the JSON
If the PFS is undefined, it pulls one from the contracts
It is an asynchronous operation
Let the user confirm the PFS on start-up (after pressing connect)
It is stored in the state
It is getting validated if the PFS is reachable
If the PFS is not reachable the user gets proposed a new one

Tasks

It is not complicated at all.
There are 2 non-tech related problems though:

If there is one free pfs in the ServiceRegistry, then everybody is using this free PFS. So we will destroy the merely existing market for the other PFS
BBLE will not operate a PFS on their own on mainnet. So we would need to find someone offering this service for free but stake the min. nec. 500 RDN

@Dominik1999 We have changed this to request any PFS service from the registry

If the user gets a list of available PFS servers presented, what's the criteria for him to select one?

At the moment the one with the fastest response time.
In #386 it would be the cheapest one or a combination of both.


xdescribe() for ignored/pending suite

xdescribe("A spec that is ignored", () -> {
    // will not run

    it("might have tests, but they will also not run", () -> {
        // will not run
    });
});

Closed by #33


Deliver ignores iPhone4 screenshots

Hi, I am using deliver plain (without fastlane). For some reason it does not consider my iPhone4 (3,5 inch) screenshots. They are not in the HTML preview and also don't get uploaded. Uploading them manually works fine, so they have the right resolution.

Please share your version of deliver, Deliverfile, and full log. Thanks!

Also please send us a screenshot of the directory and the image sizes of the screenshots that are not recognised

$ deliver -v
deliver 1.10.3

$ ls -R fastlane/screenshots-4-appstore
de-DE	en-US

fastlane/screenshots-4-appstore/de-DE:
iPhone4s-0-timeline.png					iPhone6-0-timeline_framed.png
iPhone4s-1-food-editor.png				iPhone6-1-food-editor_framed.png
iPhone4s-2-food-editor-ingredients.png			iPhone6-2-food-editor-ingredients_framed.png
iPhone4s-3-symptom-editor.png				iPhone6-3-symptom-editor_framed.png
iPhone4s-4-filter.png					iPhone6-4-filter_framed.png
iPhone5-0-timeline_framed.png				iPhone6Plus-0-timeline_framed.png
iPhone5-1-food-editor_framed.png			iPhone6Plus-1-food-editor_framed.png
iPhone5-2-food-editor-ingredients_framed.png		iPhone6Plus-2-food-editor-ingredients_framed.png
iPhone5-3-symptom-editor_framed.png			iPhone6Plus-3-symptom-editor_framed.png
iPhone5-4-filter_framed.png				iPhone6Plus-4-filter_framed.png

fastlane/screenshots-4-appstore/en-US:
iPhone4-0-timeline.png					iPhone6-0-timeline_framed.png
iPhone4-1-food-editor.png				iPhone6-1-food-editor_framed.png
iPhone4-2-food-editor-ingredients.png			iPhone6-2-food-editor-ingredients_framed.png
iPhone4-3-symptom-editor.png				iPhone6-3-symptom-editor_framed.png
iPhone4-4-filter.png					iPhone6-4-filter_framed.png
iPhone5-0-timeline_framed.png				iPhone6Plus-0-timeline_framed.png
iPhone5-1-food-editor_framed.png			iPhone6Plus-1-food-editor_framed.png
iPhone5-2-food-editor-ingredients_framed.png		iPhone6Plus-2-food-editor-ingredients_framed.png
iPhone5-3-symptom-editor_framed.png			iPhone6Plus-3-symptom-editor_framed.png
iPhone5-4-filter_framed.png				iPhone6Plus-4-filter_framed.png

The image size of the iPhone4 ones is 640x960. I also tried renaming them to from iPhone4-... to iPhone4s-... as you can see for the de-DE directory.
Log
$ rvm use 2.2.1
Using /Users/__me__/.rvm/gems/ruby-2.2.1
$ deliver
[10:27:33]: Login to iTunes Connect<EMAIL_ADDRESS>[10:27:37]: Login successful

+--------------------+-----------------------------------+
|                 deliver 1.10.3 Summary                 |
+--------------------+-----------------------------------+
| app_identifier     | com.examlpe.myapp                |
| username           |<EMAIL_ADDRESS>                 |
| screenshots_path   | ./fastlane/screenshots-4-appstore |
| metadata_path      | ./fastlane/metadata               |
| skip_binary_upload | false                             |
| skip_screenshots   | false                             |
| skip_metadata      | false                             |
| force              | false                             |
| submit_for_review  | false                             |
| automatic_release  | false                             |
+--------------------+-----------------------------------+

[10:27:38]: Loading './fastlane/metadata/de-DE/description.txt'...
[10:27:38]: Loading './fastlane/metadata/de-DE/keywords.txt'...
[10:27:38]: Loading './fastlane/metadata/de-DE/release_notes.txt'...
[10:27:38]: Loading './fastlane/metadata/de-DE/support_url.txt'...
[10:27:38]: Loading './fastlane/metadata/de-DE/marketing_url.txt'...
[10:27:38]: Loading './fastlane/metadata/de-DE/name.txt'...
[10:27:38]: Loading './fastlane/metadata/de-DE/privacy_url.txt'...
[10:27:38]: Loading './fastlane/metadata/en-US/description.txt'...
[10:27:38]: Loading './fastlane/metadata/en-US/keywords.txt'...
[10:27:38]: Loading './fastlane/metadata/en-US/release_notes.txt'...
[10:27:38]: Loading './fastlane/metadata/en-US/support_url.txt'...
[10:27:38]: Loading './fastlane/metadata/en-US/marketing_url.txt'...
[10:27:38]: Loading './fastlane/metadata/en-US/name.txt'...
[10:27:38]: Loading './fastlane/metadata/en-US/privacy_url.txt'...
[10:27:38]: Loading './fastlane/metadata/copyright.txt'...
[10:27:38]: Loading './fastlane/metadata/primary_category.txt'...
[10:27:38]: Loading './fastlane/metadata/secondary_category.txt'...
[10:27:38]: Loading './fastlane/metadata/primary_first_sub_category.txt'...
[10:27:38]: Loading './fastlane/metadata/primary_second_sub_category.txt'...
[10:27:38]: Loading './fastlane/metadata/secondary_first_sub_category.txt'...
[10:27:38]: Loading './fastlane/metadata/secondary_second_sub_category.txt'...
[10:27:38]: Verifying the upload via the HTML file can be disabled by either adding
[10:27:38]: `force true` to your Deliverfile or using `deliver --force`
Does the Preview on path './Preview.html' look okay for you? (y/n)

Any update on this? FYI: I am now on version 1.10.5 and it's still ignoring my 3,5 inch screenshots.
For me it's not to much of an issue as I have only two locales. So no rush from my side here.

Hi @martnst - thanks for the report :+1:
I believe I have spotted the problem! deliver's screenshot collecting logic will prefer "framed" screenshots to the exclusion of all others if any of the file names it discovers contain _framed. Because all of your screenshots are framed except the iPhone4 ones, those are the only ones being ignored.
So! The question then becomes, why aren't the iPhone4 shots being framed...
Can you share your output from running frameit? Thanks!

Hi @mfurtak, this sound like a bit tricky one to find out. Thx so far.
Do to custom framing (which unf. I can't do with frameit for now) I apparently simply forgot to append _framed (within my Sketch file).
That said I think a warning would have been nice here. It could be checking for additional files that are matching a missing devices resolutions and tell my as a user, that it had skipped those for what ever reason. 😉
Cheers, Martin

Agreed - we'll improve the messaging for sure. :+1:
If it's OK with you, I'll close this out for now, and we'll let you know when a new build goes out with better warnings. Thanks for your help!


Gutenburg Editor Disappeared - Wordpress

In December, the Gutenberg editor disappeared from the CDF's wordpress. Can someone help bring it back?

@zestyroxy I have a ticket in with creative services to look in to this. I'll keep you posted!
internal reference: https://jira.linuxfoundation.org/browse/LP-7074

@zestyroxy I have a ticket in with creative services to look in to this. I'll keep you posted!
internal reference: https://jira.linuxfoundation.org/browse/LP-7074

This has been resolved.


Bug: table无限滚动有问题

Version
Vben Admin V5
Describe the bug?

没有标签栏的情况下，gridEvents的scroll事件中isBottom显示错误

Reproduction

System Info
ios，chorme

Relevant log output
No response
Validations

[X] Read the docs
[X] Ensure the code is up to date. (Some issues have been fixed in the latest version)
[X] I have searched the existing issues and checked that my issue does not duplicate any existing issues.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

最新版本没能重现。


Actual tasks on 2023

Dear  @dayo09  @llFreetimell
I with @stamalakhov and @staddy would like to join to the ONE-vscode extensions development, can we discuss the actual tasks in this direction?

:exclamation: Work in writing :exclamation:

Summary for 2022
Let's collect all the features which are developed until 2022 to plan actual tasks on 2023!
Official Features
These features are remarked as official and can be seen in release note.
JsonTracer
TBA
Mondrian
TBA
cfg Editor
TBA
ONE Explorer
TBA
ONE Toolchain
TBA
ONE Device
TBA
Unofficial Features
These features are included in the release package, but not remarked as official.
As a result, we can execute them with release package but just remember that there can be some bugs or unresolved issues.
Metadata Viewer
TBA
Metadata Manager
TBA
circleGraph
TBA
PartEditor
TBA
circle Editor
TBA
visquv
TBA
Feature Requests
These features are not developed at all.
However, they are either good to have or must to have in the near future :)
ONE workflow
TBA

@Torrero, @stamalakhov, @staddy
All the candidate tasks are collected :)

We have also discussed the feature of weight visualization. It will help to detect model issues easily and speed up debugging. Then error visualization may also be implemented.
@dayo09 @llFreetimell, what do you think about this feature?

what do you think about this feature?

This feature can be introduced in ONE-vscode. Welcome!
PartEditor was implemented by @seanshpark. He has a lot of knowledge about netron and UI implementation in VSCode extension. He can help you with what you're trying to do. /cc @seanshpark
First of all, please make an issue of what you want to do for weight visualization.
And let's continue the discussion there.

In ONE-vscode, AMPQ or above items will be developed this year. (Who? 👀)

I think I could do some reviews related with UI and circle viewer control applications :)

@seanshpark @dayo09 @jyoungyun
BTW is anyone interested in providing/viewing metadata for compiler products?

I'm going to implement only toolchain related things in ONE-vscode this year. :)

@stamalakhov It was planned and drafted last year, but not merged. If you are interested, you can go on with that. I am currently not planned, too

@stamalakhov It was planned and drafted last year, but not merged. If you are interested, you can go on with that. I am currently not planned, too

ok. Thank you.

I'm going to implement only toolchain related things in ONE-vscode this year. :)

ok. Thank you.


[Bug]: FastAPI Swagger /docs does not working correctly

Your current environment
The latest vLLM docker: vllm/vllm-openai:v0.4.0
Issue seems to exist as far back as 0.2.7.
🐛 Describe the bug
Visiting http://localhost:8080/docs when running the server offline shows a blank page however loads with the proper title for the page. I haven't yet attempted this with an online / non-firewalled running instance of vLLM.
Inspecting the page with developer tools shows some html, however there are errors in downloading .js files from a cdn so I suspect that is the problem.
Is there a way to enable support for the Swagger documentation offline?
Since I'm unable to test, http://localhost:8080/docs properly functioning with online instances?

This doesn't seem to be a vLLM issue


Do I have to install this version of PyTorch==1.8?

my cuda version is 11.1 .
i cant install the pytorch-gpu==1.8 that  support cuda11.1?
so i want to ask that if pytorch==1.9 is ok?

Pytorch 1.9 1.10 but not 1.11 is ok.

But then I run into the next error:
  File "/home/zosurban/anaconda3/envs/prismalearn/lib/python3.9/site-packages/MQBench-0.0.6-py3.9.egg/mqbench/deploy/deploy_onnx_qnn.py", line 199, in search_and_replace_input
    for idx, _input_name in enumerate(next_node.input):
AttributeError: 'str' object has no attribute 'input'

@PannenetsF

@urbste Please provide the detailed reproduction code and steps so that I can solve the problem.

Cool thanks for taking a look at it.
Tested with:

pytorch 1.8.1+cu111
onnx 1.12.0

MinimalExample.zip

#126 Fix this issue, and we will add unet to our unittest. Thanks for your feedback!

Great it works! Just a remark about the Unet that I used. I had to comment the automatic padding calculations in the UP sampling block: So this network only works for specific input sizes. (I think divisible by 8). Otherwise the PyTorch tracing does not work.
def forward(self, x1, x2):
        x1 = self.up(x1)
        #diffY = x2.size()[2] - x1.size()[2]
        #diffX = x2.size()[3] - x1.size()[3]
        #print(diffY, diffX)
        #x1 = F.pad(x1, [diffX // 2, diffX - diffX // 2, diffY // 2, diffY - diffY // 2])
        x = torch.cat([x2, x1], dim=1)

        return self.conv(x)

 You can open a new issue so we can talk about this problem.
---Original---
From: "Steffen @.>
Date: Mon, Jul 4, 2022 15:01 PM
To: @.>;
Cc: "Yunqian @.>;"State @.>;
Subject: Re: [ModelTC/MQBench] Do I have to install this version ofPyTorch==1.8? (Issue #121)
Great it works! Just a remark about the Unet that I used. I had to comment the automatic padding calculations in the UP sampling block: So this network only works for specific input sizes. (I think divisible by 8). Otherwise the PyTorch tracing does not work.
def forward(self, x1, x2):         x1 = self.up(x1)         #diffY = x2.size()[2] - x1.size()[2]         #diffX = x2.size()[3] - x1.size()[3]         #print(diffY, diffX)         #x1 = F.pad(x1, [diffX // 2, diffX - diffX // 2, diffY // 2, diffY - diffY // 2])         x = torch.cat([x2, x1], dim=1)         return self.conv(x)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you modified the open/close state.Message ID: @.***>


Add information about the keepalive intervals

:)

I don't see the point in leaving them out. If its too much work to update the code lines on an update, they could simply be deleted. The links where also permanent, meaning if the exact line quoted would actually shift up or down on the raiblocks' master, it wouldn't affect the link.
Apart form that, it's your repository, hope this suits what you're looking for better :)

Thanks!


Doesn't delete correctly once print line has been reformatted across multiple lines

I don't see any easy way to fix this given that lines are inserted without any semantic understanding. I'm going to close this as something I won't support.


DevOps Pipeline Variables Not Working

I have a variables set for [Name of file/page:] and they do not appear to work as intended. Does this option support variables? I had intended on creating a new file per release but if that is not supported I will just append to a concrete file.
Release-Notes/$(Date:yyyyMMdd)$(Hours)$(Minutes).md
Please let me know.
Thank you!

Can't see why that won't work, I will do a test as soon as I get a chance

This was on WIKI Updater Tasks which I am using in conjunction with GenerateReleaseNotes (XPlat version).
https://marketplace.visualstudio.com/items?itemName=richardfennellBM.BM-VSTS-WIKIUpdater-Tasks&ssr=false#overview

##[error]Error: fatal: pathspec 'Release-Notes/$(Date:yyyyMMdd)$(Hours)$(Minutes).md' did not match any files
Options
[]  Replace the file in the WIKI
[]  Append to end of file in the WIKI
[x] Data is a file

I have done some checking.
Inside the build pipeline (whether it use UI or YAML based) you can only access the built in variables. If you check this list you can see the date ones are not there. It seem the$(date) etc. are only available for the build name i.e. set prior to the pipeline starting.
So, you are getting the errors the $(date) is not being expanded, and the unexpanded value is being used as a file name that is invalid.
I can confirm using the build variables are fine as this is the technique I use for testing both the release note and wikiupdater
A snippit of the YAML is
steps:
- task: richardfennellBM.BM-VSTS-XplatGenerateReleaseNotes.XplatGenerate-Release-Notes.XplatGenerateReleaseNotes@2
  displayName: 'Generate Release Notes based on Release Comparision API V2 '
  inputs:
    outputfile: '$(System.DefaultWorkingDirectory)\$(RELEASE.ENVIRONMENTNAME)SortedList.md'
    outputVariableName: OutputTextSorted
    templateLocation: InLine
    inlinetemplate: |
         < all the template>
    sortWi: true

- task: richardfennellBM.BM-VSTS-WIKIUpdater-Tasks.WikiUpdaterTask.WikiUpdaterTask@1
  displayName: 'Git based WIKI Updater c'
  inputs:
    repo: 'dev.azure.com/richardfennell/Git%20project/_git/Git-project.wiki'
    filename: 'xPlatReleaseNotes/$(RELEASE.ENVIRONMENTNAME)SortedList.md'
    dataIsFile: true
    sourceFile: '$(System.DefaultWorkingDirectory)\$(RELEASE.ENVIRONMENTNAME)SortedList.md'
    message: 'Update from Release - $(Release.ReleaseName) with Creds'
    gitname: builduser
    gitemail: 'build@demo'
    useAgentToken: false
    user: richardfennell
    password: '$(AzureDevOpsPAT)'
    localpath: '$(System.DefaultWorkingDirectory)\repo1'

So to get around your problem, the technique I would use here is to set your build number to be something like
$(Build.DefinitionName)_$(Date:yyyyMMdd)$(Hours)$(Minutes)

Though I prefer to use variables I control to get a date in the form MyBuild_1.0.20125.1

So I create a major and minor variable that I update as changes occur
the build variable increments on the date
the rev is the build on the day

$(Build.DefinitionName)_$(Major).$(Minor).$(Year:yy)$(DayOfYear).$(rev:r)

Either way in the release notes and WIKI updater use the $(Build.BuildNumber)
 filename: 'ReleaseNotes/$(Build.BuildNumber).md'

I think that makes it easier to associate the build with the document.

As per my standard practice I am closing this issue as I have heard nothing for a while. If this issue remains a problem please do not hesitate to re-open it


chore(pkger): unify all template workflows under the Template vocabulary

Closes #18580

[x] Well-formatted commit messages
[x] Rebased/mergeable
[ ] Tests pass
[ ] http/swagger.yml updated (if modified Go structs or API)

I ooopsie the git commit here... closing for new one


[BUG]

Describe the bug
When trying to kick off a Checkmarx scan via Github, we're receiving an error in the Checkmarx AST CLI Action step that causes the action to fail.
Expected behavior
The Github action runs successfully and kicks off a scan in Checkmarx.
Actual behavior
The Github action is failing before a scan in Checkmarx can be initiated.  This first happened on our weekly scheduled scan on 1/21, then has happened on each subsequent try when attempting to re-run failed jobs manually.
Steps to reproduce

Go to our organization's private repo
Click on Actions
Click on the fail Checkmarx SAST workflow
Select Re-run failed jobs
Job runs for 10-30 seconds and then fails on Checkmarx AST CLI Action

Additional comments
Add any other context about the problem here.

Hi @walkerbryan
Can you please generate a new API key and use it ?
We will try to reproduce the case locally.
Thanks,

@pedrompflopes I generated a new API key in Checkmarx and updated our secret in the CX_API_KEY in the affected repo, but the action again failed with the same error.

@walkerbryan  Please try again.

@pedrompflopes action failed, but different message in logs:
Run checkmarx/ast-github-action@main
with:
project_name: tyler-technologies/eagle-cm-frontend
cx_tenant: tylertech
base_uri: https://ast.checkmarx.net
additional_params: --apikey ***
branch: refs/heads/develop
github_token: ***
repo_name: eagle-cm-frontend
namespace: tyler-technologies
/usr/bin/docker run --name ce98cd4d98183411f862e8ff7a56eec08_1ab379 --label 49859c --workdir /github/workspace --rm -e "INPUT_PROJECT_NAME" -e "INPUT_CX_TENANT" -e "INPUT_BASE_URI" -e "INPUT_ADDITIONAL_PARAMS" -e "INPUT_CX_CLIENT_ID" -e "INPUT_CX_CLIENT_SECRET" -e "INPUT_BRANCH" -e "INPUT_GITHUB_TOKEN" -e "INPUT_REPO_NAME" -e "INPUT_NAMESPACE" -e "INPUT_PR_NUMBER" -e "CX_BASE_URI" -e "CX_TENANT" -e "CX_CLIENT_ID" -e "CX_CLIENT_SECRET" -e "GITHUB_TOKEN" -e "BRANCH" -e "PROJECT_NAME" -e "ADDITIONAL_PARAMS" -e "REPO_NAME" -e "NAMESPACE" -e "PR_NUMBER" -e "HOME" -e "GITHUB_JOB" -e "GITHUB_REF" -e "GITHUB_SHA" -e "GITHUB_REPOSITORY" -e "GITHUB_REPOSITORY_OWNER" -e "GITHUB_REPOSITORY_OWNER_ID" -e "GITHUB_RUN_ID" -e "GITHUB_RUN_NUMBER" -e "GITHUB_RETENTION_DAYS" -e "GITHUB_RUN_ATTEMPT" -e "GITHUB_REPOSITORY_ID" -e "GITHUB_ACTOR_ID" -e "GITHUB_ACTOR" -e "GITHUB_TRIGGERING_ACTOR" -e "GITHUB_WORKFLOW" -e "GITHUB_HEAD_REF" -e "GITHUB_BASE_REF" -e "GITHUB_EVENT_NAME" -e "GITHUB_SERVER_URL" -e "GITHUB_API_URL" -e "GITHUB_GRAPHQL_URL" -e "GITHUB_REF_NAME" -e "GITHUB_REF_PROTECTED" -e "GITHUB_REF_TYPE" -e "GITHUB_WORKFLOW_REF" -e "GITHUB_WORKFLOW_SHA" -e "GITHUB_WORKSPACE" -e "GITHUB_ACTION" -e "GITHUB_EVENT_PATH" -e "GITHUB_ACTION_REPOSITORY" -e "GITHUB_ACTION_REF" -e "GITHUB_PATH" -e "GITHUB_ENV" -e "GITHUB_STEP_SUMMARY" -e "GITHUB_STATE" -e "GITHUB_OUTPUT" -e "RUNNER_OS" -e "RUNNER_ARCH" -e "RUNNER_NAME" -e "RUNNER_TOOL_CACHE" -e "RUNNER_TEMP" -e "RUNNER_WORKSPACE" -e "ACTIONS_RUNTIME_URL" -e "ACTIONS_RUNTIME_TOKEN" -e "ACTIONS_CACHE_URL" -e GITHUB_ACTIONS=true -e CI=true --entrypoint "/app/entrypoint.sh" -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" -v "/home/runner/work/_temp/_runner_file_commands":"/github/file_commands" -v "/home/runner/work/eagle-cm-frontend/eagle-cm-frontend":"/github/workspace" 49859c:e98cd4d98183411f862e8ff7a56eec08  "https://ast.checkmarx.net/" "tylertech" "" "" "***" "tyler-technologies/eagle-cm-frontend" "--apikey ***" "eagle-cm-frontend" "tyler-technologies" ""
Creating directory
Error validating scan types: Token decoding error: json: cannot unmarshal string into Go struct field JWTStruct.aud of type []string
PR decoration not created.

@walkerbryan  Please try again with the new version.
Thanks

@pedrompflopes Everything is running again without issue.  Thank you for your assistance.


fixing compiler issues for gcc 6.0

the compiler error was: error: invalid use of incomplete type ‘class yarpl::single::Single’ [-Werror]

Other failures are known ... merging so we can move forward and build on top of this.


bug fix: close result file writer

Hi,
Deleting suite XML file from allure-results directory fails with IO exception ("The process cannot access the file because it is being used by another process"). JAXB marshaller does not close the file Writer, it should be done explicitly.
Thanks!

@ilyin371 thanks!


failing without clear reason

Reproduction
it throws this error sometimes when accessing: https://openpix.com.br/pay/84c1b233-855c-4590-9e41-16734290c6a2
FetchError: request to https://openpix.com.br/pay/graphql failed, reason:
    at ClientRequest.<anonymous> (webpack://index/node_modules/node-fetch/lib/index.js:1491:11)
    at ClientRequest.emit (node:events:523:35)
    at ClientRequest.emit (node:domain:489:12)
    at TLSSocket.socketErrorListener (node:_http_client:495:9)
    at TLSSocket.emit (node:events:511:28)
    at TLSSocket.emit (node:domain:489:12)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

The related to is here
req.on('error', function (err) {
			reject(new FetchError(`request to ${request.url} failed, reason: ${err.message}`, 'system', err));

			if (response && response.body) {
				destroyStream(response.body, err);
			}

			finalize();
		});

Steps to reproduce the behavior:
Try to access this https://openpix.com.br/pay/84c1b233-855c-4590-9e41-16734290c6a2 and reload or use a anonymous navigator to try to trigger this error
Expected behavior
It should not error

Screenshots

Your Environment

software
version

node-fetch
2.7.0

node
20-alpine

npm
10.1.0

Operating System
linux

Additional context

How can I get more info on this bug? why reason is not defined?

I am facing the same issue. We're using error.message and the "reason" is empty. Reduced test case:
import fetch from 'node-fetch';
fetch('http://localhost:1234/regdvfs');

Result:
file:///Users/oliver/Code/unsplash/unsplash-web/node_modules/node-fetch/src/index.js:108
			reject(new FetchError(`request to ${request.url} failed, reason: ${error.message}`, 'system', error));
			       ^

FetchError: request to http://localhost:1234/regdvfs failed, reason:
    at ClientRequest.<anonymous> (file:///Users/oliver/Code/unsplash/unsplash-web/node_modules/node-fetch/src/index.js:108:11)
    at ClientRequest.emit (node:events:518:28)
    at Socket.socketErrorListener (node:_http_client:500:9)
    at Socket.emit (node:events:518:28)
    at emitErrorNT (node:internal/streams/destroy:169:8)
    at emitErrorCloseNT (node:internal/streams/destroy:128:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  type: 'system',
  errno: 'ECONNREFUSED',
  code: 'ECONNREFUSED',
  erroredSysCall: undefined
}

error.message:
FetchError: request to http://localhost:1234/regdvfs failed, reason:

mine was a failing dns service

Ah, but I think this is still an issue—that node-fetch doesn't return a more informative error message?

Ah, but I think this is still an issue—that node-fetch doesn't return a more informative error message?

I faced similar issue, no proxy, no VPNs, but deployed within docker using node:20 image, after downgrading to node:18 issue resolved.

I think this is Windows-specific. We see this issue with Node.js 20.17.0 and Node.js 22.10.0 on Windows. We do not see this issue with Node.js 18.20.4 on Windows, and we do not see it with Node.js 18/20/22 on Linux.


Full definition of a union type given in error messages related to union typed variables

Consider the following program:
type ValueType int|float|string|boolean|byte;
type DataType ValueType|table|json|xml|map|();

public function main() {
    map<DataType> m;
    map<int> m2 = m;
}

Running the above program results in the following compilation error:
error: .::test2.bal:6:19: incompatible types: expected 'map<int>', found 'map<int|float|string|boolean|byte|table|json|xml|map?>'

Instead of saying map<int|float|string|boolean|byte|table|json|xml|map?>, it should be saying map<DataType>.

The same requirement came for LS. This requires persists original typenode information into AST/symbols.

We need to prioritize this issue as the langserver generated codes are not intuitive. Related issue https://github.com/ballerina-platform/ballerina-lang/issues/28684

With https://github.com/ballerina-platform/ballerina-lang/pull/29362, the compilation error has been updated.
type ValueType int|float|string|boolean|byte;
type DataType ValueType|table<record {}>|json|xml|map<any>|();

public function main() {
    map<DataType> m;
    map<int> m2 = m;
}

now results in
ERROR [foo.bal:(6:19,6:20)] incompatible types: expected 'map<int>', found 'map<DataType>'

The original member types of a union type can be accessed via the BType using org.wso2.ballerinalang.compiler.semantics.model.types.BUnionType#getOriginalMemberTypes.

@MaryamZi Can this be closed now or are there other cases to consider?


Weird indentation of stats controls when the window is small

Browser: IE 11

This box is now left aligned on small window. Fixed with https://github.com/NuGet/NuGetGallery/pull/4304


Bump Installation Directions Version Number

The directions on the website currently say to install elm-make 0.1.1
with cabal install. This causes odd syntax errors to show up when
trying to compile elm-lang/core (probably the cause behind issue #218).
Therefore bumped to elm-make 0.1.2.

Didn't sign the contributor agreement, but hopefully something this small doesn't require that. Worst case scenario someone who has signed the contributor agreement can make the change for me.
Incidentally, any reason the directions don't just drop the version numbers altogether for the cabal install commands?


zilencer: Enforce uniqueness of server_id + remote_id.

This was previously just an index (not a unique one).  Enforce this data constraint.

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

It looks like we have some tests whose test data violates this, interesting.

Merged, thanks @alexmv!


Support a typedef which is conditionally defined

For example:
#if defined(USE_64BIT_INDEXTYPE)
using IndexType = std::int64_t;
#else
using IndexType = std::int32_t;
#endif

The Fortran and C equivalent is added via a splicer to the YAML file. But changes were required to allow a typemap to be defined in the YAML file and merge some user define include and USE statements with Shroud generated code.

Added file_code dictionary to input YAML file. It contains
directives to add header file and USE statements into generated files.
These are collated with headers and USE statements added by typemaps,
statements and helpers to avoid duplication.
Allow typemaps with base as integer and realto be added to the
input YAML file. This allows kind parameters to be defined via splicers
then used by a typemap.  i.e. integer(INDEXTYPE)

@kennyweiss The test problem typemap.yaml has an example of its use.  I added some documentation but it's a little lite. I plan on adding more detailed examples in appendix-A.rst later.


Error: Workflow failed! Uploading SARIF report to GitHub Advanced Security failed: Error: Cookies must be enabled to use GitHub.

I am using<EMAIL_ADDRESS>with the following config
blackducksca_url: ${{ secrets.BLACKDUCK_URL }}
blackducksca_token: ${{ secrets.BLACKDUCK_TOKEN }}
blackducksca_scan_full: false
blackducksca_scan_failure_severities: 'BLOCKER,CRITICAL'
github_token: ${{ secrets.GITHUB_TOKEN }}
blackducksca_prComment_enabled: true
blackducksca_reports_sarif_create: true
blackducksca_upload_sarif_report: true
and i can not see the result directly in github - I get the error mentioned in the title.
If I use<EMAIL_ADDRESS>github action with the same github token, it works fine so I think it has the permission that i need. Can someone please help me?

@sadmananik the comment from https://github.com/synopsys-sig/synopsys-action/issues/283 might help


Expose http headers in error

Summary
This PR aims to provide errors surfaced by the SlackAPI with response headers
This is accomplished by returning an HttpError instead of a generic Error.
The goal was to try and achieve a similar pattern as the Deno Http Error handling example.
In addition a new method toResponse() was added to the returned "response" from client.apiCall and client.response. toResponse() exposes the original Response object received from fetch without breaking backwards compatibility.
Putting this all together could look as follows
import { isHttpError } from<EMAIL_ADDRESS>import { SlackAPI } from "https://raw.githubusercontent.com/slackapi/deno-slack-api/703f9f09b358a3302f9e5f63bba0eb56590f8472/src/mod.ts";

const client = SlackAPI("my-token");

let response;
try {
	response = await client.api.test();
} catch (e) {
	if (isHttpError(e)) {
		console.log(e.status)
		console.log(e.message)
		console.log(e.headers)
	}
	throw e;
}
if (!response.ok){
	const fullResponse = response.toResponse();
	console.log(fullResponse.headers)
}

Usage example:

Compatibility
these changes should be backwards compatible
Requirements

[x] I've read and understood the Contributing Guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.

Instead, within the resp.json() is ok: false and we still don't expose the headers.
That means there are two separate instances of checking whether or not the request was ok

@shapirone thanks for pointing this out 🥇
I've adjusted this PR to fix this, it is a tricky situation, ideally we would want apiCall and response to return a Response this would provide the user with all the available information on this fetch. Unfortunately this requires a breaking change since the object currently returned is the output of Response.json() (any as BaseResponse)
To get around this I've extended the BaseResponse with a toResponse() method (FullResponse) this allows users to get the original Response object obtained by the base-client with the fetch function and access all the information they may need.


Solver can't solve to fractions with variables.

The solver can't solve to fractions with variables. For example the speed formula:
s = a/t. So the solver can solve for 'a' -> a = st, but not for 't' -> undefined. Probably because Fraction can't handle variables in the numerator or denominator. This is a serious issue.
    let expr = new Expression('s');
    expr = expr.multiply('t');

    const eq = new Equation(expr, new Expression('a'));
    const aAnswer = eq.solveFor('a');
    const tAnswer = eq.solveFor('t');

    console.log(`a = ${aAnswer}`); // this works: a = st
    console.log(`t = ${tAnswer}`); // this fails: t = undefined

I agree, this is a large problem. It prevents many simple things from being done. For example, simply doing new algebra.Expression("a").divide("b") causes an Uncaught TypeError: Invalid Argument (b): Divisor must be of type Fraction or Integer.


Move jest-runtime/_normalizeID to jest-resolve/getModuleID

Summary
Almost all methods and functions used by _normalizeID are from resolver. Because of that, it makes much more sense to move it to resolver and pass virtualMocks from runtime since it is the only runtime's data required. Besides that, this patch includes a refactor of use of this._getVirtualMockPath to getModulePath.
I want to contribute with the project but I am not familiar with the code. I will read it and refactor everything that would help to understand the code. Right now, my focus is in jest-runtime package and I intend to move to other packages as well.
If you guys don't want to receive patches where the purpose is only refactor the code to improve design and readability, you can let me know and I won't bother you guys anymore.
Test plan
I am not adding any new test because the code refactored is already covered by tests. Let me know if you need any extra tests.
I used yarn watch to re-build yarn flow && yarn lint && yarn jest to test after each time that I saved a file. Before send the PR, I've run yarn test to make sure that I am not breaking any test.

Current coverage is 67.56% (diff: 29.41%)

Merging #2668 into master will decrease coverage by 0.52%

@@             master      #2668   diff @@
==========================================
  Files           139        139
  Lines          5044       5034    -10
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits           3434       3401    -33
- Misses         1610       1633    +23
  Partials          0          0

Powered by Codecov. Last update 20b45bb...1146066

@wanderley wow, this is awesome. I definitely have always and will always appreciate refactors for the sake of refactors if it improves the overall architecture of the system. In this specific case it hasn't occurred to me that we should do this, so it's definitely interesting. I like that you moved the "global" cache into the instance of the resolver, that makes a lot of sense to me. However, I would prefer jest-resolve not to depend on jest-util.
 I wish we could move it to an optional third argument but I guess it doesn't improve anything, so let's keep it.

Closing in favor of https://github.com/facebook/jest/pull/2677


Properly enable +dotprod in int8 benchmarks.

In experimental mmt4d configs, we were unconditionally passing --iree-flow-mmt4d-target-options=arch=aarch64 features=+dotprod  AND NOT passing the corresponding -iree-llvm-target-cpu-features=+dotprod. That didn't matter as long as we were only testing fp32 benchmarks, but now that we have MobileBertSquad-int8, it does matter.
Concretely at the moment our MobileBertSquad-int8 first selects the dotprod-specific tile size (because we pass --iree-flow-mmt4d-target-options=arch=aarch64 features=+dotprod) but then it doesn't enable the corresponding asm kernel (because we don't pass -iree-llvm-target-cpu-features=+dotprod) so it ends up generating slow code.

Superseded by #8673


crashlog?

Anyone know where to find .crashlog? I can't find the Logs folder

The output of the game server is by default in /var/log/arklog/arkserver.log


Add support for deck.gl "polygon" layer

Add support for Polygon layer in Superset
https://uber.github.io/deck.gl/#/documentation/layer-catalog/polygon-layer

I'd like to create a choropleth map using polygon data in units of municipalities.
What type of data should I use?
If there is a table containing geojson in the column, can I visualize it?
I would like to know sample data and how to set up queries.


Add nodejs install instructions

I wanted to ensure the setup instructions in the contributing docs work perfectly with no extra steps than stated.
I realized tests were failing due to the missing configurable-http-proxy required by JupyterHub.
Added extra steps to install nodejs, configurable-http-proxy and yarn

Btw, I'm not confident about yarn etc, is that required? Is yarn an alternative to npm?

I am not confident about it too. Seems like an alternative. I will exclude it from this project.

@consideRatio Thank you for reviewing this PR.


Fixed Reloading

Hey @KiranPolaki I encountered an issue. Whenever we press "again" the answer was same every time. I've fixed it and now it's working fine. Kindly review changes and merge this PR.

What do u mean by same! elaborate.

What do u mean by same! elaborate.

The answer that is SecreteNumber was being the same whenever "again" was pressed. I fixed it by enabling it to reload once it's pressed.

What do u mean by same! elaborate.

You can check it. First time you have to guess the number but the subsequent times it was the answer is the same number. To avoid it I just added an eventListener and it is working fine

Yes i see now!


Multicast Discovery of Agents

It should be possible to (a) allow agents to respond to multicast requests for their URL and (b) triggering an MBean operation for finding all agents with a multi cast request.
See #125 for more details and an alternative approach.
Currently, most of the stuff is already implemented and can be tried out with the 1.2.0-SNAPSHOT where the discovery mechanism is enabled by default (for the WAR agent it has to be enabled by an ini param or a system property). The MBean can be found at jolokia:type=Discovery.
More documentation to follow, I also have still some points to discuss (but now I'm too tired ;-).

Long done.


2stackz: top-frame copying GC

Currently in #143 we hard-reset the stack after each event.. This wipes out our hot and warm states, which are not saved to the snapshot as they contain function pointers. Thus, we have to re-initialize both after every event. Saving the state of the stack and restoring to the saved state suffices to preserve the hot state, which should not change over the course of our execution. However, it is not sufficient to save the warm state, which is reinitialized whenever the cold state changes and thus requires collection of stale entries and HAMT stems.
Instead we should implement a top-frame copying GC as follows:

ensure (assert?) that the stack is popped to the top frame, preserving hot and warm states.
Set a new allocation pointer at the opposite end of the stack arena from the current allocation pointer, causing copies to overwrite the locals area of the current top frame.
Copy hot and warm state to the allocation arena tracked by the new pointer, using a lightweight stack in memory adjacent to the old pointer.
Set up new stack and frame pointers at the now-reclaimed end of the stack arena.
Ensure pointers to hot and warm are updated in interpreter context.

The effect of this is that each event will run with the opposite-orientation frame as top each time. This should be fine, though we should audit for assumptions that "the top is always west." If the top frame has no locals and wasn't using the lightweight stack when we pushed, then this wastes no space. However if for some odd reason we did use locals or the lightweight stack in the top frame, the wasted space is now just part of the allocation area for the new "top" frame, and will be reclaimed when we switch back next time.
@joemfb @frodwith @ashelkovnykov please review this idea.

I should have read this issue before looking at the PR. After much confusion, @eamsden explained this to me while I was reviewing #175 and I'm on board with it.
As @eamsden points out in the issue, and as @drbeefsupreme noted during the review for #175, we'll need to either audit the code for "top is west frame" assumptions, and we should keep this change in mind during future debugging efforts, when and if memory errors appear. (Maybe make a "likely candidates" playbook to document potential bug-causing PRs?).

This was fixed in #178 after being merged and reverted in #175 and #177


New version: SomePythonThings.WingetUIStore version 2.2.0

Pull request has been created with WinGet Releaser v2 :rocket:
Microsoft Reviewers: Open in CodeFlow

Same issue as always I guess

Automatic Validation ended with:

Installation failed with exit code 1

(Automated response - build 490.)

@wingetbot waivers Add Validation-Installation-Error


Add Xamarin.Forms C#

1200-page ebook is a deep dive for C# programmers who want to write applications using a single code base that targets the three most popular mobile platforms: iOS, Android, and Windows

Thanks! I'm not familiar with aka.ms, is it a file hosting service? An url shortener?
Is there a more authoritative source for this book? A homepage?

Hi vhf,
It's microsoft's shortener. Maybe we can use this link instead?
https://developer.xamarin.com/guides/xamarin-forms/creating-mobile-apps-xamarin-forms/
I thought pointing directly to download link was better.
Thanks

Yep, I'd prefer this link. I'll take care of this. Thanks!


Rolling deli into IDB

Now that deli is aligned with IDB, should we roll deli into IDB as you mentioned here before proceeding with extending features like the composite primary keys?
If so, what do you think should be done?

I think we should first try to implement all the indexed db features in deli and iterate over the API until we're satisfied. Then, we can merge it with idb.
As mentioned, some of the missing features are:

Composite primary keys
Indexes with multiple keys

Ok!


4.2.1 difference to 4.2.0 : Outlook on Android columns with mj-group

Firstly, thank you for MJML! It's made emails so much nicer for us to work with.
4.2.1 seems to have introduced some behaviour that breaks <mj-group> on Outlook for Android.
Here's the behaviour on 4.2.0:
https://cl.ly/c22361c184eb/Screen Shot 2018-11-23 at 11.16.06.png
And here's the same email (no changes to the MJML source) on 4.2.1:
https://cl.ly/24b29b611424/Screen Shot 2018-11-23 at 11.16.47.png
I'm not seeing this change on any other client that we test. We are minifying our HTML.
Our code looks like this (I did wonder if it's the mj-raw with the templating that's causing a change)?
    <mj-raw>{% for item_row in items_for_email %}</mj-raw>
    <mj-section padding="0">
      <mj-group>
        <mj-raw>{% for item in item_row %}</mj-raw>
        <mj-column width="50%">
          <mj-image border-radius="6px" padding="0 5%" src="{{item.img}}" />
          <mj-text mj-class=" item-details" padding-top="0">

{{item.brand}}

{{item.title}}

{{item.price}} · {{item.size}}

          </mj-text>
        </mj-column>
        <mj-raw>{% endfor %}</mj-raw>
      </mj-group>
    </mj-section>
    <mj-raw>{% endfor %}</mj-raw>

The screenshots above are taken from Litmus.

Quick update : I started deleting content from the columns to find the issue; and it turned out it was the paragraphs inside the mj-text doing it. I've ditched them (for more mj-text elements, not nested) and Outlook is happy again.
Feel free to close this if you like :)

Hi @jackfranklin, in the end did you get a different result with the same template with 4.2.1 vs 4.2.0, or was it caused by the content ?
The only components that have been modified on 4.2.1 are hero and social, so this would be surprising 🤔

@jackfranklin i think litmus shouldn't affect the result
Unfortunately it's hard to test without having the actual template generated with your variables.
Also outlook for android is not available on emailonacid, but i made a few tests with a template that could be generated from this (see below) and i didn't notice a difference on any client
  <mj-body>

    <mj-section padding="0">
      <mj-group>
        <mj-column width="50%">
          <mj-image border-radius="6px" padding="0 5%" src="https://images.pexels.com/photos/20787/pexels-photo.jpg?auto=compress&cs=tinysrgb&dpr=2&h=350" />
          <mj-text mj-class=" item-details" padding-top="0">

Base London

Greenwich Washed

$79.99 · UK 11 / EU45

          </mj-text>
        </mj-column>
        <mj-column width="50%">
          <mj-image border-radius="6px" padding="0 5%" src="https://images.pexels.com/photos/20787/pexels-photo.jpg?auto=compress&cs=tinysrgb&dpr=2&h=350" />
          <mj-text mj-class=" item-details" padding-top="0">

Base London

Greenwich Washed

$79.99 · UK 11 / EU45

          </mj-text>
        </mj-column>
      </mj-group>
    </mj-section>
    <mj-section padding="0">
      <mj-group>
        <mj-column width="50%">
          <mj-image border-radius="6px" padding="0 5%" src="https://images.pexels.com/photos/20787/pexels-photo.jpg?auto=compress&cs=tinysrgb&dpr=2&h=350" />
          <mj-text mj-class=" item-details" padding-top="0">

Base London

Greenwich Washed

$79.99 · UK 11 / EU45

          </mj-text>
        </mj-column>
        <mj-column width="50%">
          <mj-image border-radius="6px" padding="0 5%" src="https://images.pexels.com/photos/20787/pexels-photo.jpg?auto=compress&cs=tinysrgb&dpr=2&h=350" />
          <mj-text mj-class=" item-details" padding-top="0">

Base London

Greenwich Washed

$79.99 · UK 11 / EU45

          </mj-text>
        </mj-column>
      </mj-group>
    </mj-section>

  </mj-body>
</mjml>

@jackfranklin Sorry to go off topic here, but which templating language are you using in your template?

As we can't really reproduce, I'm closing this issue


Fix typo on the settings json

Thanks. I've gone ahead and fixed that up manually while updating other things.


Add support for Minecraft version 1.18?

Is there an ETA on when support for 1.18 will be added?

I am able to use the current version of this plugin on my 1.18 Paper server without any obvious issues, so maybe it does not need to be updated. But official support for 1.18 would be appreciated :)

Sorry for the late reply, holidays and new house has finally settled down. Plugin should still be working on 1.18

No worries, thank you for the confirmation!


Made DataTable layout independent of Bootstrap's grid column count

For our project we're using a customized version of Twitter's Bootstrap (http://getbootstrap.com/customize/). For better UI handling we changed the grid column count (@grid-columns) from 12 to 60 (which is quite common). The DataTables use the hard coded .col-xs-6 style for creating a 50% wide column - which breaks the layout for customized Bootstraps.
With this pull request the columns are created independently of the total grid column count.

Hi @alxppp,
I don't think a  good idea changing the DataTables original files, this gem only add the files inside the Rails asset.
It should be better send the PR to https://github.com/DataTables/DataTables and then we will update the gem.
Thanks for PR and the help.

Closed due user inactivity.


Add simple test framework

Add testFrameworks += new TestFramework("scalaz.zio.test.TestFramework") to your build.sbt and include scalaz-zio-testkit as a test dependency.
This is more a POC than anything.

The matchers are super simple
The output is not super pretty

But things work and everything seems to integrate with SBT fine.
package bla

import scalaz.zio._
import scalaz.zio.testkit._

object Bla {
  def helloWorld = ZIO.succeed("Hello World")
  def foobar     = ZIO.fail(new Exception("This is no good"))
}

object BlaSpec extends TestSpec with DefaultRuntime with SimpleMatchers {
  val tests = Map(
    "first test"  -> first,
    "second test" -> second,
    "third test"  -> third
  )

  def first: Task[Result] =
    Bla.helloWorld.map(expect("Hello World"))

  def second: Task[Result] =
    Bla.helloWorld.map(expect("FooBar"))

  def third: Task[Result] =
    Bla.foobar.mapError { e =>
      compare[Throwable]("Did not receive the expected error")(a => a.getMessage == e.getMessage)(e)
    }.flip
}

#717

I will review this over the weekend. Glad to see the pull request!

I think we should wait on this until the ZIO move. At which point I have some minor suggestions, but I think using something like this could solve our Scala.js woes and simplify a lot of code.

@NeQuissimus I like the direction this is headed. I think, however, that we should take a little time to do this inside the new ZIO organization, and give it an official name ZIO Test. We should make sure:

It's type safe
It's composable
It's "idiomatic"
It works on Scala 2.11, 2.12, 2.13, and 3.0
It makes it painless to run ZIO tests (including with environment)

This is a good building block but rather than merge this now and get a bunch of users on something we'd have to support for a while, I think the best option is to punt until after 1.0 and the new org relocation.
What do you think?

Absolutely, this was basically a PoC anyways. It was in no way in a good state :D
I'm still for dropping 2.11 but whatever :D
We will need code like this to hook into SBT, I think that stuff will remain similar. But I fully agree that a proper test framework should be built out around that.


What is git push tags?

What is git push tags?

I know about git tag, but not sure about git push tags.

read the section "Sharing Tags" on this site.


Absence of the ability to "attack move"

In the SC2 you can command your units to move to a position while attacking any nearby enemy units they encounter along the way. The base move function does not work in this way. I searched and experimented with several abilities found in the abilities id's file and the closest thing I could find that functioned in this manner was "PATROL". Sadly this results in units running back and forth instead of just forth like I want. I thought perhaps "ATTACK_ATTACKTOWARDS" might work but that's a no go as well.
From what I can tell, the ability isn't implemented currently. If it is however, mind sharing the ID?

I think the normal attack() command (ATTACK) should work. Just make sure you target a position rather than a unit. If you target a position it should just a-move towards that position, attacking enemies in sight. If you want to a-move towards a specific unit, I think you can use "unit.position" rather than "unit" as target, to a-move instead of target firing.
Here's an example:
# Select a unit
unit = self.units[0]

# Make unit a-move towards enemy start location.
await self.do(unit.attack(self.enemy_start_locations[0]))

That works exactly as I was hoping, thank you!