jQuery not defined

W20150516-14:51:28.683(8)? (STDERR)
W20150516-14:51:28.689(8)? (STDERR) /Users/yiluxin/.meteor/packages/meteor-tool/.<IP_ADDRESS>wysac9++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/server-lib/node_modules/fibers/future.js:245
W20150516-14:51:28.690(8)? (STDERR)                                             throw(ex);
W20150516-14:51:43.307(8)? (STDERR)                                                   ^
W20150516-14:51:43.312(8)? (STDERR) ReferenceError: jQuery is not defined
W20150516-14:51:43.312(8)? (STDERR)     at app/ui/definitions/behaviors/api.js:875:5
W20150516-14:51:43.312(8)? (STDERR)     at app/ui/definitions/behaviors/api.js:877:3
W20150516-14:51:43.312(8)? (STDERR)     at /Users/yiluxin/WebstormProjects/untitled/.meteor/local/build/programs/server/boot.js:222:10
W20150516-14:51:43.312(8)? (STDERR)     at Array.forEach (native)
W20150516-14:51:43.312(8)? (STDERR)     at Function._.each._.forEach (/Users/yiluxin/.meteor/packages/meteor-tool/.<IP_ADDRESS>wysac9++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/server-lib/node_modules/underscore/underscore.js:79:11)
W20150516-14:51:43.313(8)? (STDERR)     at /Users/yiluxin/WebstormProjects/untitled/.meteor/local/build/programs/server/boot.js:117:5
=> Exited with code: 8
=> Your application is crashing. Waiting for file change.

Maybe a bit of context? Existing app or brand new? :)

在 2015年5月16日，16:06，Frederic Lemay<EMAIL_ADDRESS>写道：
Maybe a bit of context? Existing app or brand new? :)
—
Reply to this email directly or view it on GitHub https://github.com/Semantic-Org/Semantic-UI-Meteor/issues/14#issuecomment-102585704.

I tried again, deployed in the lib folder of meteor client folder, everything is normal, as the problem of path, but still don't understand why

It's been a few weeks but I think this is what was happening to me when I was attempting to convert an app from Bootstrap. I tried to go through and rebuild it piece-by-piece to find out what the cause was, but it was too much work. :)

Same issue. I managed to generate semantic-ui after editing custom.semantic.json. After that, it got stuck with the error message above ... ReferenceError: jQuery is not defined.
I am doing a new/simple demo app. I will tried to meteor add jquery for the project. Problem did not go away. I will try to manually paste jQuery in lib/definitions/behavior later and see what happens.
I notice the generated lib/definitions/behaviors/api.js needs jquery:
(function ( $, window, document, undefined ) {
  ...
})( jQuery, window , document );

Any pointer would be appreciated.

Yay! I managed to get Semantic UI to work by creating custom.semantic.json in client/lib.
Previously, I placed it in /lib directory causing Meteor to process it as server side code. It would be good to put this in README.md's "Usage" section so that new Meteor users like myself do not make such mistake.

Additional note: I went back and attempted to recreate this error, and was unable to.

Anyone willing to try adding the following section to the package.js file?
Package.onUse(function(api) {
  api.versionsFrom('1.0.1');
  api.impy('jquery', 'client');
});

At the moment we're not requiring jquery explicitely, so I guess there are no problems if in the same project the are other packages implying it, but could be required to solve your issues.
Unfortunately I have no time to test this :(

@kctang Thanks a lot for testing the package and finding the problem. :)
@splendido Good suggestion but unfortunately it didn't solve the problem. I think the best approach would be what @kctang suggested.

...woops, I've missed the comment by @kctang :(
Any way to intercept this case and print a warning on the server?

The problem is not the package itself because it only generates files. It does not compile anything. :) Maybe flemay:less-autoprefixer could..

@kctang's solution is the correct one. jQuery is not available on the server, only the client.

See this comment from @leijing7 which seems to clarify why you can get jQuery is not defined...

It is only necessary to put custom.semantic.json under the /client folder, not necessarily in /client/lib.  For example, I put custom.semantic.json in /client/semantic-ui.

in my simple-todo tutorial on Windows, there's no /client folder... Added client\semantic-ui and moved the custom.semantic.json to that folder... still experiencing the same issue.
thoughts??

@sheshmantha -- OK here was the issue:

First I added the file in root folder -- so when I had custom.semantic.json in the root folder for the project, the 3 folders of definitions, sites, themes along with the .less files were created in that folder.
afterwards I created a subfolder of client\semantic-ui and moved ONLY the custom.semantic.json to that folder...

That kept crashing (even though new definitions, less files were in the client\semantic-ui)... after a bit of aggravation, I noticed these folders and files in the root project folder... AND when i removed them and restarted... VOILA she works!!

@sheshmantha this worked for me too and had the added benefit of clearing up the files from the root folder

I m not getting, How to solve this problem. I am using windows and I am having this problem in starting meteor. Plz suggest me how to solve it..

@rajakedia1 To solve this problem, make sure you create your custom.semantic.json in a /client/.. folder, so meteor treats it as frontend code only and not as server code which has no jQuery.


Want to add features, unclear where to start

I am a little new to adding features to someone elses code..  So here's my take
I want a flag to generate a "Master" image set, that I believe reflects the correct screen.. and save it in some folder aside from the test results.
On subsequent passes, when generating the test results.. if this master image set exists (and matches the number of shots to some agreeable number), then perform a stitching or concatenation of the two side by side.  Such that,
Each resulting screenshot is stitched side by side with the master-correct image, on the left.  The new resulting image from the test on the right.
Where can I get started, I can fork the project.. and I guess I'd create a small tester-test suite ?

Fork the project.
Clone the fork and add your functionalities
If you think the new functionality is a generally useful one, please create a pull request (PR) also so that it can be merged in this repo

I am knowledgeable about how to fork a repository.  Thank you.
Where can I research how these plugins / reports work?  In particular with this specific project.


GHA: Upload to Production workflow

Task/Issue URL:
Description
Steps to test this PR
Feature 1

[ ]
[ ]

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

#5241  👈
develop

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @malmstein and the rest of your teammates on  Graphite


update ci to golang 1.16

/assign @otaviof @gabemontero

/lgtm

/assign @adambkaplan can I get an approval from you?

weird my lgtm should have approved (i'm an approver)
/approve


I can't unpack . masterbundle is an extension from the game unturned is not supported when unpacking in your program, please fix it. files.unity3d that can be unpacked in your program has become rarely used.

Game name: (please, specify the game name)
Engine version: (specify engine version, if known)
Platform: (specify platform, if known)
Error message: Read 24 but expected 219
Stack trace:    в uTinyRipper.BundleFileScheme.ReadMetadata(Stream stream, Int32 metadataSize)
в uTinyRipper.BundleFileScheme.ReadFileStreamMetadata(Stream stream, Int64 basePosition)
в uTinyRipper.BundleFileScheme.ReadScheme(Stream stream)
в uTinyRipper.GameCollection.ReadScheme(SmartStream stream, String filePath, String fileName)
в uTinyRipper.GameCollection.LoadScheme(String filePath, String fileName)
в uTinyRipper.GameStructure.ProcessPlatformStructure(GameStructureProcessor processor, PlatformGameStructure structure)
в uTinyRipper.GameStructure.Load(List1 pathes, LayoutInfo layinfo)    в uTinyRipper.GameStructure.Load(IEnumerable1 pathes, LayoutInfo layinfo)
в uTinyRipperGUI.MainWindow.LoadFiles(Object data)

I can't unpack . masterbundle is an extension from the game unturned is not supported when unpacking in your program, please fix it. files.unity3d that can be unpacked in your program has become rarely used.


kernel restarting at jupyter lab

Hi.
When I run several examples here in jupyter lab,
I got "kernel restarting" error at last "show" command, and I have no output.
My machine is Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz: 8 cores and 32 GB memory.
I think it is enough to calculate the example problems.
Also I reduced the number of parameters to reduce the calculation cost, but nothing changed.
Do you have any idea about this problem?

sorry for the late reply can you type
vedo --info
to check your system.
What if you try with the dev version:
pip install -U git+https://github.com/marcomusy/vedo.git

No problem.
Thank you very much for your reply.
I will try it.


V1 improvement

Just two small changes.

Fix protocol header for unknown protocols.

Before:
PROXY UNKNOWN <nil> <nil> 0 0\r\n
Now:
PROXY UNKNOWN\r\n

Set a larger capacity for the buffer to avoid extra allocations.

So a 108-byte buffer is always enough to store all the line and a trailing zero for string processing.
http://www.haproxy.org/download/2.3/doc/proxy-protocol.txt
[]'s

Coverage decreased (-0.3%) to 91.379% when pulling 36b3cabd66e41ea3e4cc977751afbe8bc9890d7e on navossoc:master into bd882ec9dcb4288c8724686bd228aa78df28e09b on pires:master.


Minor renaming of memory allocation macros for naming consistency. Cleanup comments around these interfaces in .h and elsewhere.

Is your feature request related to a problem? Please describe.
Not a problem but mostly like code cleanup. During code-walk through of memory allocation interfaces, discovered a slightly inconsistent naming of caller-macros relating to memory allocation, in platform.h:

Most are named as TYPED_MALLOC(), TYPED_ZALLOC(), TYPED_ARRAY_MALLOC(), TYPED_ARRAY_ZALLOC(), and so on, where the verb ALLOC is the last term.
These two are named dissimilarly: TYPED_MALLOC_MANUAL() and TYPED_ZALLOC_MANUAL()

Raised this in internal slack thread and the agreement was to do as suggested below (1).
Another minor interface issue raised in this slack thread is to do with use of raw platform_aligned_malloc() followed by a memset() to 0, in src/rc_allocator.c, whereas the equivalent work is done by existing caller macro TYPED_ALIGNED_ZALLOC(). Solution is to fix this also, as described below (2).
Describe the solution you'd like

Rename TYPED_MALLOC_MANUAL() -> TYPED_MANUAL_MALLOC() and  TYPED_ZALLOC_MANUAL() -> TYPED_MANUAL_ZALLOC()
Replace raw reference to platform_aligned_malloc() with call to TYPED_ALIGNED_ZALLOC (which seems to be the right thing to do; sort out the right fix during implementation.)
During code walk through of this area, some cleanup comments were found to be useful. Incorporate them.

Describe alternatives you've considered
No response
Additional context
No response

Issue addressed by code changes merged under this commit:
592d86a gapisback 2 minutes ago Fri, 30-Sep-2022, 11:03:38 AM (Authored: Fri, 30-Sep-2022, 11:03:38 AM)
 (#446) Rename couple of memory allocation macros. Add comments; code cleanup. (#447)

See above.


Does this also apply to the latest version or there might be some changes like support bacth messages Microsoft.Azure.WebJobs.Extensions.ServiceBus v5.13.3

[Enter feedback here]

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

ID: a0203fd1-e905-1db5-8ec1-4a0a00d0ca4e
Version Independent ID: 458d6304-e240-a5e9-d7cb-45573a279062
Content: ServiceBusOptions.MaxConcurrentSessions Property (Microsoft.Azure.WebJobs.ServiceBus) - Azure for .NET Developers
Content Source: xml/Microsoft.Azure.WebJobs.ServiceBus/ServiceBusOptions.xml
Service: azure-functions
GitHub Login: @azure-sdk
Microsoft Alias: azsdkdocs

Hi @XiaoYue2-22.  Thank you for reaching out and for your inquiry.  This option applies to v5.13.3 and any future versions of the Microsoft.Azure.WebJobs.Extensions.ServiceBus package, including the latest current release..


jitpack builds failing

hey,
the build are failing before even starting to compile, see https://jitpack.io/com/github/outwatch/outwatch/ea240c6/build.log
is this a jitpack issue or do you know what might cause this?

seems to be a recent issue: https://github.com/jitpack/jitpack.io/issues/3733

While I cannot provide a solution to the issue, I can provide a workaround.
Earlier in the development of my application I stopped using jitpack altogether, since (from my experience) turnaround times are way too slow for my purposes and it can fail in all kinds of ways, which are really hard to troubleshoot.
My project depends on a fork of outwatch and I use it as a testing ground for the changes I make (some of which #270 I am trying to get into upstream).
Since I do not want to wait anywhere between 2 Hours and 2 Days for jitpack to build my project every time I make a change, I have now switched to using sbt's ProjectRef to handle the retrieval of my outwatch fork.
Specifically I use it like this:
// Creates a reference to the outwatch project, which behaves like a sbt subproject.
lazy val outwatch = ProjectRef(uri("https://github.com/busti/outwatch.git#debug3"), "outwatch")

lazy val client = project
  .settings( ??? )
  .dependsOn(outwatch)

To my surprise this also seems to integrate nicely into IntelliJ, which creates a separate workspace for the ProjectRef and handles it like a git submodule.

However, there are some gotchas with this approach, which can be avoided

The Setting requireJsDomEnv in Test := true from ScalaJSBundler cannot be found when the ProjectRef is compiled. I avoid this by having a separate branch with a single commit which removes the setting. See https://github.com/Busti/outwatch/commit/58a5d3e55cb828215d2df1a836192b9a51ad0177
Even though sbt retrieves the ProjectRef through a git clone, which seems to integrate nicely with IntelliJ, making changes to the files in said git repository can sometimes lead to the whole project failing to compile due to Linking Errors. I still do not know what causes this and it is relatively annoying to fix, since all files created by sbt for that project have to be manually removed. This includes all target folders, aswell as the place where the ProjectRef is cloned to, but not the .sbt folder in the home directory. Due to this issue, I currently make changes to outwach in a separate clone and sync them via remote, since sbt re-clones the ProjectRef every time it launches.

I hope this can be useful to you and remind me to create an issue on ScalaJSBundler to ask them why requireJsDomEnv cannot be found in the context of ProjectRef.

I've got same issued.

@Busti thanks for the detailed workaround, this is definitely an option in cases i really need a fast update :+1:
turns out jitpack is working correctly again

I am goind to close this one, as it seems that it was caused by a jitpack problem. Feel free to reopen if there is something we can do.


Add Fade/Set Color

Hi there, I've been using the MMM-birthdays module and find it super useful.
My only slight issue (apologies I'm a complete newbie) is that the text colour does not match my other modules.
This maybe because I have fade: false set on other modules. Can this be implemented in this module?
Also, can a colour be picked for the text?

Hi @jonnyollet, glad you're finding this useful! Could you send me a screenshot so I can see exactly what you're after? I'm sure this should be pretty simple to add!
And yes, changing the text colour will also be fairly straight forward so I can implement that


RTT pushed to PostMVP

(module
  (type $Any (struct (field $type i32)))
  (type $BoxedInt (struct_subtype (field $type i32) (field $val i64) $Any))
  (import "console" "log32" (func $println32 (param i32)))
  (export "main" (func $main))
  (func $test (result (ref $BoxedInt))
    (struct.new $BoxedInt
      (i32.const 128)
      (i64.const 1028)))
  (func $main
    (local $0 eqref)
    (local.set $0
      (call $test))
    (call $println32
      (struct.get $Any $type
        (ref.cast_static $Any
          (ref.as_data
            (local.get $0)))))))

This program works when ./wasm-as is run with the --nominal flag.
New instructions used. struct.new, ref.cast, struct_subtype.
./wasm-as main.wat -o main.wasm --nominal -all

Will look into this once the documentation is updated


Closing AlwaysOnTop window leaves permanent border

Microsoft PowerToys version
0.55.2
Running as admin

[X] Yes

Area(s) with issue?
Always on Top
Steps to reproduce
Open Microsoft Outlook, and open an email as a popup. Set the email popup as Always on Top. Close the email popup.
PowerToysReport_2022-02-25-15-53-07.zip
✔ Expected Behavior
Always on Top border should disappear when the on top window is closed.
❌ Actual Behavior
Border remains. If another window is set to on top, the stuck border disappears. If on top is disabled from this new window, the stuck border returns.
Blue border below is an example of a stuck border:

Other Software
Microsoft Outlook (Office365 for business)

this is fixed with 0.56 which should be out on Monday.
/dup #15300


Library with multiple licenses declared in json file is displayed incorrectly

About this issue
I use AboutLibraries Gradle Plugin in Android project with (legacy) UI-module. I added an additional library with two licenses by creating a json file in configPath/libraries directory. I put two elements in "licenses" field. I expected that AboutLibraries will show two cards with different licenses, but only the one was displayed with one of the licenses. duplicationMode I used is MERGE, duplicationRule is GROUP. If I create two files with one license in each, two cards will be displayed as expected. Are multiple licenses in json file supported?
Details

[ ] Used library version - 10.0.1
[ ] Used gradle build tools version - 7.1.2
[ ] Used tooling / Android Studio version - Android Studio Bumblebee | 2021.1.1 Patch 3

Checklist

[x] Searched for similar issues
[x] Checked out the sample application
[x] Read the README
[x] Checked out the CHANGELOG
[x] Read the MIGRATION GUIDE

Thank you for your answer.


WTFPL for the win

👏🏽👏🏽👏🏽

this is an amazing license


increased readiness and liveness probe delay to 120

Increased default values initialDelaySeconds for livenessProbe and readinessProbe. Related to #73

I'm surprised this would be needed given that Kubecost never had to increase past 30 seconds. Are we potentially masking some other issue with this change?

My assumption was we were deploying to installations with less resources, but we should keep an eye out.


upgrade hive api

https://github.com/open-cluster-management/backlog/issues/17358

@elgnay

/cc @elgnay

/lgtm


feat: migrate onwards to typed field with a source (core.article message)

got consent to merge in Backend Weekly


Reorganize docs

Currently there's

http://scalameta.org/
http://scalameta.org/tutorial
https://github.com/scalameta/sbt-semantic-example (see readme)
https://github.com/scalameta/scalameta/blob/master/notes/quasiquotes.md
https://github.com/scalameta/sbt-macro-example

It would be nice if these documents were available from a single page.
I propose that we

rename tutorial to docs so that it will have the url http://scalameta.org/docs It's not really a tutorial anymore since I recently removed the exercise sessions because they were outdated and were based on an ancient fork of scalafix.
inline the quasiquote table into the tutorial around trees http://scalameta.org/tutorial/#Trees
add a section in the tutorial on sbt-scalahost and move the contents from the sbt-semantic-example readme to that new section
move sbt-semantic-example to sbt-scalahost.g8 and make it a giter8 template
move sbt-macro-example to paradise.g8 and make it a giter8 template

I find myself constantly referring to the quasi quote table. I like the idea of putting it right in the main doc.

Great points! Thanks for assembling them, they will be very useful.

I think it's best to push this issue back another release. The milestone has a lot of open issues considering the deadline https://github.com/scalameta/scalameta/milestone/3

@olafurpg Let's merge this ticket into https://github.com/scalameta/scalameta/issues/1265?

Closing as fixed, we have a new documentation site that aggregates our current documentation https://scalameta.org/ the website can still be improved by adding more content, but those changes can be handled by separate tickets.


Implemented support for loading excluded pixels from XML, issue #805

Contributor Checklist:

[x] I have added or updated my entry in the creators.json file
[x] I have added a changelog entry for my contribution
[x] I have added/updated documentation for all user-facing changes
[x] I have added/updated test cases
[ ] I have included the rebuilt production build of the client (only if changes were made to the GUI)

Reviewer Checklist:

[ ] /azp run libertem.libertem-data passed

/azp run libertem.libertem-data

I'll do a more detailed review later today, but for now: congrats on getting it working and the PR submitted! As you can see in the "checks" section on this page, there are still some issues that need to be solved, primarily formatting the code to make flake8 happy. You can run pre-commit locally, too, as described in the documentation.
Other than that, you can also already add a changelog entry for this change.

The check_example_notebooks failure is not your fault - this is caused by runtime variations because of more than usual load on the CI system.

@bdalevin Hi, I have noticed that in the test XML files there are two badPixelMaps one is binned and the other is not and I was wondering what is the purpose of the (smaller) binned one since its defect values could be calculated from the unbinned, bigger bad pixel map directly.

Hi @DYVZ8X, right now the entire SEQ test module is skipped if the test data is not available. Since your tests for excluded pixels don't depend on the data, you can modify the SEQ module to only skip tests that actually require the data.
Here's a diff with an example where I did this for FRMS6: https://github.com/LiberTEM/LiberTEM/pull/1067/commits/0543acb6737ccf4c909c78a083a10e959983a17e#diff-da2368c6194672d7394faed3a77a97da61edf62dcb57b81541805967174bf4cc
The "skipif" decorator is not assigned to the special pytestmark variable which applies it to the entire module, but any other variable, in this case needsdata. Now @needsdata can be added to any test function that requires data.

@DYVZ8X FYI the "cognitive complexity" measurement is not a hard guideline - if we feel that one of the functions is too complex, we will clear this up in the code review. If this is currently a blocker for you, feel free to ignore these codeclimate issues for now.

@DYVZ8X could you maybe try to bundle related changes in commits so that the number of commits stays lower? In particular, it would be a lot better to first run all checks and tests, and commit only after everything passes resp. after a significant milestone is reached. That way we don't end up with individual commits for each flake8 problem, like your last two commits. Just to be clear, separate commits for milestones, separating unrelated changes and commits for intermediate review are perfectly OK! It is just about finding the right balance here.

/azp run libertem.libertem-data

/azp run libertem.libertem-data

/azp run libertem.libertem-data

Thanks, merged!

Is the XML format documented somewhere? I am consolidating the changelog and couldn't find a public resource that describes the file format.

Is the XML format documented somewhere? I am consolidating the changelog and couldn't find a public resource that describes the file format.

I didn't write a documentation for the xml file, but If I should then please let me know where.

@DYVZ8X thank you for the feedback! For me it is still a bit unclear where these XML files come from. Are they written by the acquisition software or does a user write them "by hand"? Who else consumes these files? The point is not so much to define the format, but to specify what kind of workflow we support here. Since we don't define the format ourselves and also don't write these files, I'd prefer to link to an external resource such as official Direct Electron documentation. However, Google didn't find anything on this.
Did you obtain sample XML files from somewhere or did you write them following a specification from Direct Electron? Where did you obtain the former or the latter?

@DYVZ8X thank you for the feedback! For me it is still a bit unclear where these XML files come from. Are they written by the acquisition software or does a user write them "by hand"? Who else consumes these files? The point is not so much to define the format, but to specify what kind of workflow we support here. Since we don't define the format ourselves and also don't write these files, I'd prefer to link to an external resource such as official Direct Electron documentation. However, Google didn't find anything on this.
Did you obtain sample XML files from somewhere or did you write them following a specification from Direct Electron? Where did you obtain the former or the latter?

In the test_seq.py I wrote them by hand, but to test if really everything is working fine I got one from you at the beginning of my internship, also I think these files are written by the software as it would be really hard to write a binary metadata file for the xml file.

Ok, I see. I've included finding and linking proper documentation of the XML format from the vendor as a FIXME. CC @bdalevin :-)


I have run your experiments for 20 times, but I couldn't re-implement your results

Dear Edward,
Thanks for your contribution to the community.
But I couldn't re-implement your experiments by using the scripts you wrote in the LoRA/examples/NLG.
I feel down and don't know what to do.
......
:(

I'm sorry to hear that! Were you able to run our checkpoints and reproduce our reported numbers?
It's been a while since we released the repo. Many factors could have contributed to your not being able to get the same result. Unfortunately, I don't have the bandwidth to help you hunt down what the issues are in your experiment, but maybe getting our checkpoints to run first can help you debug things like the eval pipeline.

Thanks for your reply!  I have tested your pretrained model, and I found that some errors may occur in the beam search and decode process.

I see! Since many others were able to reproduce the numbers using our pretrained checkpoints, it is fairly certain that there are bugs in your code. I don't have any specific advice for you, but it might be a good idea to reach out to others who have successfully reproduced our checkpoints (see other GitHub issues).

After struggling of a couple of weeks, I  successfully re-implement your paper!  Thanks for your contribution to the community.

@zibojia can you please tell how did you use the pretrained models?
From where can we access the pretrained models?

After struggling of a couple of weeks, I successfully re-implement your paper! Thanks for your contribution to the community

hi, can you share your work details ,since i can not reimplement experiments in paper, related issue:https://github.com/microsoft/LoRA/issues/138


aixPb: Add steps to install dnf and deprecate yum for AIX 7.2 and higher

[x] commit message has one of the standard prefixes
[ ] faq.md updated if appropriate
[ ] other documentation is changed or added (if applicable)
[ ] playbook changes run through VPC or QPC (if you have access)
[x] VPC/QPC not applicable for this PR
[ ] for inventory.yml changes, bastillion/nagios/jenkins updated accordingly

ref https://github.com/adoptium/infrastructure/issues/3142#issuecomment-1662156865

As per @aixtools's comments in https://github.com/adoptium/infrastructure/issues/3149#issuecomment-1671000103 I am also in favour of using dnf only and deprecating yum

@aixtools I am not too familiar with https://github.com/adoptium/infrastructure/blob/1e3dfa0386893a1b023852d3c1b41be7e2a1d1aa/ansible/playbooks/AdoptOpenJDK_AIX_Playbook/roles/yum/tasks/main.yml#L15
Do you think it needs to be included in the dnf install?

Going to test this on https://ci.adoptium.net/computer/test-osuosl-aix72-ppc64-5/, its yum will be upgraded to dnf

Installed openssl3 on test-osuosl-aix72-ppc64-5. Doesnt look like there was a problem
root@adopt05:[/root/openssl3/openssl-<IP_ADDRESS>0]openssl version
OpenSSL 3.0.10 1 Aug 2023 (Library: OpenSSL 3.0.10 1 Aug 2023)

Its having trouble installing ca-certificates-2023.2.60-0.aix7.1.ppc.rpm which is included in the dnf bundle. A lot of conflicting files between ca-certificates-2023.2.60-0.aix7.1.ppc.rpm and the ca certs thats already installed, ca-certificates-2021.2.52-1.ppc. For example
file /opt/freeware/bin/update-ca-bundles from install of ca-certificates-2023.2.60-0.ppc conflicts with file from package ca-certificates-2021.2.52-1.ppc
        file /opt/freeware/etc/ssl/certs/ACCVRAIZ1.crt from install of ca-certificates-2023.2.60-0.ppc conflicts with file from package ca-certificates-2021.2.52-1.ppc
        file /var/ssl/certs/ACCVRAIZ1.crt from install of ca-certificates-2023.2.60-0.ppc conflicts with file from package ca-certificates-2021.2.52-1.ppc
        file /opt/freeware/etc/ssl/certs/AC_RAIZ_FNMT-RCM.crt from install of ca-certificates-2023.2.60-0.ppc conflicts with file from package ca-certificates-2021.2.52-1.ppc
        file /var/ssl/certs/AC_RAIZ_FNMT-RCM.crt from install of ca-certificates-2023.2.60-0.ppc conflicts with file from package ca-certificates-2021.2.52-1.ppc
        file /opt/freeware/etc/ssl/certs/AC_RAIZ_FNMT-RCM_SERVIDORES_SEGUROS.crt from install of ca-certificates-2023.2.60-0.ppc conflicts with file from package ca-certificates-2021.2.52-1.ppc
        file /var/ssl/certs/AC_RAIZ_FNMT-RCM_SERVIDORES_SEGUROS.crt from install of ca-certificates-2023.2.60-0.ppc conflicts with file from package ca-certificates-2021.2.52-1.ppc
        file /opt/freeware/etc/ssl/certs/ANF_Secure_Server_Root_CA.crt from install of ca-certificates-2023.2.60-0.ppc conflicts with file from package ca-certificates-2021.2.52-1.ppc
        file /var/ssl/certs/ANF_Secure_Server_Root_CA.crt from install of ca-certificates-2023.2.60-0.ppc conflicts with file from package ca-certificates-2021.2.52-1.ppc

(without posting the whole log)

Updating ca-certificates to ca-certificates-2021.2.52-3 I was able to fix the above error. Dnf successfully installed

Need to specify a python 3 interpreter
failed: [test-osuosl-aix72-ppc64-5] (item=bash) => {"ansible_loop_var": "item", "changed": false, "item": "bash", "msg":
"Could not import the dnf python module using /usr/bin/python (2.7.18 (default, Dec 15 2022, 05:12:43) [GCC 8.3.0]). Please
 install `python3-dnf` or `python2-dnf` package or ensure you have specified the correct ansible_python_interpreter.
(attempted ['/usr/libexec/platform-python', '/usr/bin/python3', '/usr/bin/python2', '/usr/bin/python'])", "results": []}

Changing the python interpreter to ansible_python_interpreter: /opt/freeware/libexec/python3 for whenever the dnf module is used works
more info here https://community.ibm.com/community/user/power/discussion/dnf-works-but-unable-to-import-dnf-python-module

Same problem with the cmake install
TASK [dnf : Install cmake 3.14.3 (See https://github.com/AdoptOpenJDK/openjdk-build/issues/2492)] ***
fatal: [test-osuosl-aix72-ppc64-5]: FAILED! => {"changed": false, "failures": ["cmake-3.14.3 All matches were filtered out by exclude filtering for argument: cmake-3.14.3"], "msg": "Failed to install some of the specified packages", "rc": 1, "results": []}

Should be made more idempotent

Lets see what adding a disable_excludes: all does. It should still install the excluded packages if theyre not present, and do nothing if theyre present since in the install list the autoconf and freetype2-devel include their version numbers

Added this to the cmake install. Should be fine if theres no cmake-3.14.3 present. Should do nothing if it is present

https://awx2.adoptopenjdk.net/#/jobs/playbook/2256?job_search=page_size:20;order_by:-finished;not__launch_type:sync
Looks good

Id say this is good to merge


Wheel I/O should be of type DaqChannel instead of DaqChannelType

If I understand correctly, all the I/O related properties in this device should be of type DaqChannel instead of DaqChannelType since the goal of the field is to add metadata that allows the user to track where the data is rounted to/from.
https://github.com/AllenNeuralDynamics/aind-data-schema/blob/f9e8ee2b848cf47b2477830e3bab382f878f16a8/src/aind_data_schema/models/devices.py#L675

On a side node, DAQChannel should be renamed to DaqChannel as it breaks MSDN pascal naming convention (https://learn.microsoft.com/en-us/dotnet/standard/design-guidelines/capitalization-conventions?redirectedfrom=MSDN), unless you have a different reference you are following?


Add levels

There is currently only one stage that is always the same. Adding more levels would increase the difficulty as well as add variety to the game

 Brick Breaker


fix cache issue

Fixes #74
Fixes #75

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


option for auto purge reconnecting hosts

Hi there,
i am currently setting up an infrastructure with self registering hosts and it would be awesome to have an option that rancher "auto purges" reconnecting hosts from the ui without the need to call rest api for that.

This should be configure with host.remove.delay.seconds, see http://rancher.com/docs/rancher/v1.6/en/hosts/#removing-hosts


Add project ID to column on dashboard

The id should be viewable in a column

forge 36922

PR opened

Done in #202


Fix location-based components build job

Fixes a bug on build on location based and also https://github.com/jeromeetienne/AR.js/issues/605

Currently, the build job needs pre ES6 syntax.
TODO fix that before merge this


 Oops!

World improvements branch tries to fix this with 3d perlin noise, but it's a bit wonky and slow.
How does minecraft actually handle this?
2d perlin for a "base" and then 3d for the hills/mountains?
Minecraft Coder Pack haven't mapped the worldgen source files so it's impossible to tell with those!

As of now, The world generation is flat and boring, but in the style of minecraft indev! (atleast on the world-improvements branch)


Works on iOS?

Tried on iOS 11, iPad 2017, but it’s all black, maybe some minor issue in shaders?
https://erichlof.github.io/THREE.js-PathTracing-Renderer/Geometry_Showcase.html

@fabiodr
Hi, I'm afraid for mobile devices, it only works on Google Chrome browser for Android at the moment.  Also I only own a Samsung phone so that's what I've been able to test it on for my projects.  I know some people who have iPhones but I would need to have one on hand to debug an application.  Yes, like you mentioned, it probably is an issue with the shaders.  Some of the shader source (1000 lines) for the demos are at the limits of compiling successfully on older machines.  I would have to start from scratch, make an all red screen (most simple Hello World shader) and slowly build up line by line to see where a compilation problem occurred on iOS.  Unfortunately GPU shader programming does not have a lot of debugging tools like one has in other environments.
Sorry it's not working for you. Thank you for the message and heads up.
-Erich

Indeed, GLSL can become tricky for many browser/gpu configurations, maybe a service for JS error tracking (Sentry, Rollbar...) can help to understand where it’s running or not, they have a free tier.
Thanks for the attention :)
Obs: just saw a very interesting technique for realtime illumination, it’s in Processing (Java) but the creator said it’s based on OpenGL ES 3.0, so it may be possible with acceptable performance in WebGL 2.0
http://thomasdiewald.com/blog/?p=2949
http://thomasdiewald.com/blog/?p=3159

@fabiodr
Thanks for the Sentry and Rollbar error tracking tip, I will check those out. Also I think Firefox had some sort of GLSL inspector that shows all of the execution steps on the GPU so you can kind of see what's being called. I think originally it was intended to profile for optimizations because there could be too many draw calls at times when you weren't expecting them. But maybe that can help. I think Chrome has a browser extension also nowadays.
Wow that 2d radiosity Java app is beautiful! I must admit I don't know quite how he is doing that via the rasterizer as he mentioned in his blog post.  I would guess he does some kind of shadowmap depth projection, then saving the ray cast bounce  info in a huge light map texture, then sampling from that on a pixel by pixel basis. I'll try to check out his source, although I don't think he has that particular project public on his github repos. It seems like magic though - it has given me some ideas for future scenes in my project!
Thanks again,
-Erich

@fabiodr  iPhone only supports HalfFloatType（even iPhone11pro） .
You can try to replace  THREE.FloatType in pathTracingRenderTarget(commandFunctions.js) and screenTextureRenderTargett(commandFunctions.js) with THREE.HalfFloatType.
@fabiodr 因为目前上面上的苹果手机只支持半浮点运算。（甚至是苹果11pro）,你可以试着把全浮点改成半浮点。希望对你有用。

@q750831855
Thank you for the tip!  Some of my family members have iPhones, so I will give this a try on their devices.  Thanks again!
-Erich

I also think the problem is safari doesn't support webgl2 by default. It must be enabled in preferences, at least on Mac it works like this


Add intro services template

Adds an intro services template
@scottsun94 , after this merges could you also add it to the templates file with a similar config as the Intro to Workspaces template?
@edoakes , let me know your feedback. I'm not a services expert though so ideally someone on the team could take a pass afterwards to improve the notebook.

LGTM. Do we land on "serve deploy" or "serve publish"?

Adds an intro services template
@scottsun94 , after this merges could you also add it to the templates file with a similar config as the Intro to Workspaces template?
@edoakes , let me know your feedback. I'm not a services expert though so ideally someone on the team could take a pass afterwards to improve the notebook.

Will do a quick review now and happy to do another pass through it after it's merged.

I'd like to have content somewhere about how to pass arguments to an application because it's a common use case, especially to have different dev. vs. prod args, and it's best to suggest an opinionated way to do it.

Sounds good. Can you let me know some snippets (don't actually know what you have in mind to show)?

I'd like to have content somewhere about how to pass arguments to an application because it's a common use case, especially to have different dev. vs. prod args, and it's best to suggest an opinionated way to do it.

Sounds good. Can you let me know some snippets (don't actually know what you have in mind to show)?

https://docs.ray.io/en/latest/serve/advanced-guides/app-builder-guide.html#pass-arguments-to-applications


Training on Mapillary

Hey @ekzhang
I have got access to the Mapillary dataset, however, I wanted to know how will I get about training a model on it?

Hi @amil-rp-work, I haven't used the Mapillary vistas dataset, but I don't believe it is very different. Have you tried the training scripts here? https://github.com/NVIDIA/semantic-segmentation

Thanks for the reference, will try it and re-open if something is a miss 👍


Bulk Insert with another outstanding result set should be run with XACT_ABORT

Hi,
when using Parallel.ForEach and TransactionScope I'm getting the error
Bulk Insert with another outstanding result set should be run with XACT_ABORT
Code sample:
       using (var scope = new TransactionScope(TransactionScopeAsyncFlowOption.Enabled))
        {

            using var context = await _dbContextFactory.CreateDbContextAsync();
            await context.TruncateAsync<SomeEntity>();

            ParallelOptions parallelOptions = new()
            {
                MaxDegreeOfParallelism = 20
            };

            await Parallel.ForEachAsync(allChunks, parallelOptions, async (chunk, token) =>
            {

                using var dbContext = await _dbContextFactory.CreateDbContextAsync(token);

                var clone = Transaction.Current.DependentClone(DependentCloneOption.BlockCommitUntilComplete);

                using (var ts = new TransactionScope(clone, TransactionScopeAsyncFlowOption.Enabled))
                {
                    // already tried this without luck
                    // await customerPortalDbContext.Database.ExecuteSqlRawAsync("SET XACT_ABORT ON", cancellationToken: token);
                    // do transactional stuff
                    await dbContext.BulkInsertAsync(chunk, cancellationToken: token);
                    ts.Complete();
                }
                clone.Complete();

            });

            scope.Complete();
        }

Btw: what do you suggest using Parallel processing with transactions and Bulk operations?

Not sure for Parallels.
Could you write complete Test for this.
You can use exiting test RunInsertAsync as sample.
What version of Sql do you have? (SQL Server 2008 fix)

Hi,
sorry for being late. SQL Server is Azure SQL.
We're ended up using a different library for Bulk Inserting.


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-2.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 290

Questions ?
Please refer to the Backport tool documentation


Published Test fixtures capability doesn't match published artifact coordinates

Create a java library project that publishes test fixtures
plugins {
    id 'java-library'
    id 'java-test-fixtures'
    id 'maven-publish'
}
publishing {
    repositories {
        maven {
            url = uri("../testrepo")
        }
    }
    publications {
        release(MavenPublication) {
            from components.java
            groupId = 'com.example.javaLib'
            artifactId = 'javaLib'
            version = '1.0'
        }
    }
}

consume the published test fixtures in another project
repositories {
    maven {
        url = '../testrepo'
    }
}
dependencies {
    testImplementation testFixtures('com.example.javaLib:javaLib:1.0')
}

Expected Behavior
The provided publishing coordinates should override the default testFixtures capability
Current Behavior
Looking at the published module metadata, it seems that the capability set has the coordinates ${project.group}:${project.name}-test-fixtures:${project.version} so the build fails to resolve the dependency
Unable to find a variant of com.example.javaLib:javaLib:1.0 providing the requested capability com.example.javaLib:javaLib-test-fixtures:
   - Variant apiElements provides com.example.javaLib:javaLib:1.0
   - Variant runtimeElements provides com.example.javaLib:javaLib:1.0
   - Variant testFixturesApiElements provides testFixturesApp:javaLib-test-fixtures:unspecified
   - Variant testFixturesRuntimeElements provides testFixturesApp:javaLib-test-fixtures:unspecified

A work around is to set project.group, and project name to match the coordinates being published, but it makes it not possible to publish more than one variant with testFixtures to different artifact coordinates

The mechanism to set...
 groupId = ...
 artifactId = ...

...inside a publication is flawed in many scenario. Because then this is only a detail of the publication, but not of the global project identity. Gradle should probably give some kind of warning (in certain cases).
Please avoid these. Instead let the publication use your project name as artifactId (this works automatically) and set the group globally for the project using group = "...". The project name corresponds to the folder name (if it is a subproject). If you want name and folder to differ, you can do this: https://docs.gradle.org/current/userguide/fine_tuning_project_layout.html#sub:modifying_element_of_the_project_tree

Not sure if this is related to this issue but I've worked around same issue by doing this instead:
    testImplementation('com.example.javaLib:javaLib:1.0:test-fixtures')

I found a different approach to reproduce this issue.
In the case of a multi-module project, only the rootProject cannot consume/resolve the test-fixture, if it uses java-test-fixtures plugin and the subProject name differs from the folder name.
Reproduction step

Create a regular empty Gradle project, e.g. with name: example
Create a subProject by adding this to the `settings.gradle.kts:

include("test-fixtures")
project(":test-fixtures").name = "example-test-fixtures"

Add java-test-fixtures plugin to both rootProject and subProject
Add this dependency to the rootProject:

dependencies {
    implementation(project(":example-test-fixtures"))
}

Try to build it

Current result
$ ./gradlew clean build

FAILURE: Build failed with an exception.

* What went wrong:
Could not determine the dependencies of task ':test'.
> Could not resolve all dependencies for configuration ':testRuntimeClasspath'.
   > Could not resolve root project :.
     Required by:
         root project :
      > Module 'com.example:example' has been rejected:
           Cannot select module with conflict on capability 'com.example:example-test-fixtures:1.0-SNAPSHOT' also provided by [com.example:example-test-fixtures:1.0-SNAPSHOT(runtimeElements)]
   > Could not resolve project :example-test-fixtures.
     Required by:
         root project :
      > Module 'com.example:example-test-fixtures' has been rejected:
           Cannot select module with conflict on capability 'com.example:example-test-fixtures:1.0-SNAPSHOT' also provided by [com.example:example:1.0-SNAPSHOT(testFixturesRuntimeElements)]
> There are 2 more failures with identical causes.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.

BUILD FAILED in 1s

Expected result
$ ./gradlew clean build

...

BUILD SUCCESSFUL in 2s


Super Linter will not lint .tsx files

Is there an existing issue for this?

[X] I have searched the existing issues

Are you using the latest Super-linter version available?

[ ] I am using the latest Super-linter version.

[X] I can reproduce the issue running Super-linter using complete version identifier (example: vX.Y.Z), and not just with a partial one (example: vX)

[X] I am using the super-linter/super-linter action or container image, and not the deprecated github/super-linter action or container image.

Are you resonably sure that it's a Super-linter issue, and not an issue related to a tool that Super-linter runs?

[X] I think that this is a Super-linter issue.

Current Behavior
All my .ts files are linted, but my .tsx files are not found by the linter
Expected Behavior
Both types of files should be linted
Super-Linter version
v6.7.0

Super-linter configuration
---
name: Lint

on:  # yamllint disable-line rule:truthy
  push: null

permissions: { }

jobs:
  build:
    name: Lint
    runs-on: ubuntu-latest

    permissions:
      contents: read
      packages: read
      # To report GitHub Actions status checks
      statuses: write

    steps:
      - name: Checkout code
        uses: actions/checkout@v4
        with:
          # super-linter needs the full git history to get the
          # list of files that changed across commits
          fetch-depth: 0

      - name: Super-linter
        uses<EMAIL_ADDRESS># x-release-please-version
        env:
          TYPESCRIPT_STANDARD_TSCONFIG_FILE: "tsconfig.json"
          VALIDATE_BASH: false
          VALIDATE_CLANG_FORMAT: false
          VALIDATE_GROOVY: false
          VALIDATE_JAVA: false
          VALIDATE_SHELL_SHFMT: false
          # To report GitHub Actions status checks
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
...
tsconfig.json:
{
  "extends"<EMAIL_ADDRESS>  "compilerOptions": {
    "target": "ES2022",
    "jsx": "react",
    "module": "ES2022",
    "moduleResolution": "node",
    "skipLibCheck": true,
    "allowSyntheticDefaultImports": true,
    "strictNullChecks": true
  },
  "include": ["src/**/*.tsx", "src/**/*.ts", "*.ts", "*.tsx", "/tmp/lint/test/linters"],
  "exclude": ["node_modules/"]
}

Relevant log output
/github/workspace/app.d.ts:1:1: Do not use a triple slash reference for nativewind/types, use `import` style instead. (@typescript-eslint/triple-slash-reference)
    /github/workspace/app.d.ts:2:1: Too many blank lines at the end of file. Max of 0 allowed. (no-multiple-empty-lines)
 ...

Steps To Reproduce

Create a repo with .ts and .tsx files in the root directory
Set up and run Super Linter

Anything else?

My .tsx file in the same directory as a .ts file being scanned
This is the page with the RN tsconfig.json file

Hi @mccabe-david !
We need a bit more information to understand what's happening. Can you attach the full super-linter debug log?
Your reproduction steps match a few of the existing Super-linter tests, so there's something more.

Upon further inspection, there appears to be some linting of .tsx files, but I can't seem to break any rules that would break the .ts rules (e.g. extra semicolons)

I will investigate more. I thought TSX linting errors would show up under TYPESCEIPT_STANDARD

It depends on how you configure ESLint. You might need to tune the default ESLint configuration to suit your needs. 😄

@ferrarimarco Are unused variables flagged by the default config for .TSX files? Because I can't seem to break any rules. Is there a way to see what files are found by the TSX linter? I just don't believe this TSX linted successfully message...

If you set SAVE_SUPER_LINTER_OUTPUT to true, you should find helpful output in the super-linter-output directory.
I also suggest that you check if the default eslint configuration suits your needs in terms of enabled rules, and eventually customize that configuration to include the rules that you need.

I finally got the default linter working. SOMETHING is definitely wrong because all I did was copy the .eslintrc.yml into a new file called .myeslintrc.yml and put it in .github/linters, and magically my tests weren't passing.
 This is the output of my current config, but after deleting TYPESCRIPT_ES_CONFIG_FILE: .myeslintrc.yml from my main.yml workflow file, the linter suddenly says all tests passed...

Just opened a PR to update the default eslint config: https://github.com/super-linter/super-linter/pull/6116


How many names might have OCR errors?

Can you please send me the number of rows where names might have OCR errors?

This might be too hard to find out.


chore: update lerna to latest legacy version

Description
Maintenance PR. Updates Lerna to 6.5.0 (the latest is 8.x.x, but it has significant breaking changes).

@noomorph Please align the env setup docs and verify that version releasing works properly 🙏🏻


Webview scrollbar is appearing at random place when is pushed into navigator on iOS

Steps to Reproduce

Run the app with dart script as provided in https://gist.github.com/Jasphere-Appsploration/2666e31b20581c2fb8c7c95be6567cb9
Tap on the button "Go to next screen"
Scroll the webview when it is loaded
The scrollbar will appear at random X position across the screen.

Note: This behaviour only happens on iOS devices with iOS version 13.1 (I do not have the chance to try on iOS 13)

[✓] Flutter (Channel master, v1.10.7-pre.77, on Mac OS X 10.14.6 18G103, locale en-MY)
    • Flutter version 1.10.7-pre.77 at /Users/jaspherelee/Desktop/Application/flutter
    • Framework revision 69af9adeac (8 hours ago), 2019-09-29 13:01:33 -0700
    • Engine revision 5b952f286f
    • Dart version 2.6.0 (build 2.6.0-dev.0.0 6ff8d2199d)

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/jaspherelee/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 28.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.1, Build version 11A1027
    • CocoaPods version 1.7.2

[✓] Android Studio (version 3.4)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 37.1.1
    • Dart plugin version 183.6270
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)

[✓] Connected device (2 available)
    • SM G960F • 2208229a21017ece                         • android-arm64 • Android 8.0.0 (API 26)
    • iPhone   • 54450a47f970529a18dbd35d22e5c558f062b51d • ios           • iOS 13.1

• No issues found!

Update: The issue seems only happen in notched iOS device. Tested on iPhone 6S and iPhone 8 both do not have this issue.
Update 2: Add in the screen capture for the issue

Since it also occurred in the Twitter app, there is a possibility of iOS trouble instead of Flutter.

Any update on this? There are some fixes I need for the webview but the newer release have this scrollbar issue and I can't release my app!

I also found this question

@janmoppel  Any update on this?

Any update on this?

我也出现了这个问题

We found a workaround by implementing a custom PageRoute with a different animation:
class FadeAnimationMaterialPageRoute<T> extends MaterialPageRoute<T> {
  FadeAnimationMaterialPageRoute({
    @required WidgetBuilder builder,
  }) : super(builder: builder,);

  @override
  Widget buildTransitions(BuildContext context, Animation<double> animation, Animation<double> secondaryAnimation, Widget child) {
    return FadeUpwardsPageTransitionsBuilder().buildTransitions(this, context, animation, secondaryAnimation, child);
  }
}

If you use this class instead of MaterialPageRoute in Navigator.push, you don't get the randomly positioned scrollbar.

The same question, while the WebView is not the first page of the app, the scrollBar will appear at the random place.
So the Demo app works correctly, but if we change the first page and add a button to navigate to the WebView, the problem appears.

class FadeAnimationMaterialPageRoute extends MaterialPageRoute {
FadeAnimationMaterialPageRoute({
@required WidgetBuilder builder,
}) : super(builder: builder,);
@override
Widget buildTransitions(BuildContext context, Animation animation, Animation secondaryAnimation, Widget child) {
return FadeUpwardsPageTransitionsBuilder().buildTransitions(this, context, animation, secondaryAnimation, child);
}
}

I tried but the edge swipe to back gesture stop working when using this page route class.

i got the same this issue. It looks pretty weird.

Any update? We really need a fix or a workaround.

Same here.

We were running into the problem and we managed to 'fix' it by wrapping the WebView into a ClipRect. A Translate with a non-zero offset also fixed it.
I hope this information is helpful for finding a fix.

any update on this？

We were running into the problem and we managed to 'fix' it by wrapping the WebView into a ClipRect. A Translate with a non-zero offset also fixed it.
I hope this information is helpful for finding a fix.

Nope I tried but I can't get the scrollbar to appear at the correct place.
@cyanglaz This will be fixed in June 2020? Thats another half year ahead, and our app cannot release just because of this!

any update on this？

You can fix it by using PopupRoute, bug will lose some features of MaterialPageRoute.
https://github.com/pizzalbj/flutter_demo_new/blob/master/lib/custom_route.dart
use PopRoute to test your code

The hero to solve the problem, but pr has not been closed.
webview_flutter:
    git:
      url: git://github.com/cyanglaz/plugins.git
      path: packages/webview_flutter
      ref: webview_scrollbar_issue

**ClipRect(
child: Align(
alignment: Alignment.bottomRight,
child: WebView(
initialUrl: widget.url,
javascriptMode: JavascriptMode.unrestricted,
onPageFinished: (_) {
setState(() {
isLoading = false;
});
},
            ),
          ),
        ),**

This one work for me. and hope work for others too.

just delay the load to fix this
import 'package:flutter/cupertino.dart';
import 'package:flutter/material.dart';
import 'package:webview_flutter/webview_flutter.dart';

class WebViewPage extends StatefulWidget {
  final String url;
  final String title;

  WebViewPage(this.url, this.title);

  @override
  State<StatefulWidget> createState() => new WebViewPageState();
}

class WebViewPageState extends State<WebViewPage> {
  String url;

  @override
  void initState() {
    super.initState();
    Future.delayed(const Duration(milliseconds: 500), () {
      setState(() {
        url = widget.url;
      });
    });
  }

  @override
  Widget build(BuildContext context) {
    Widget view = Container();
    if (url != null) {
      view = WebView(
        initialUrl: widget.url,
        javascriptMode: JavascriptMode.unrestricted,
        onPageFinished: (_) {},
      );
    }
    return Scaffold(
      appBar: AppBar(),
      body: view,
    );
  }
}

Any update on this? I tried everything you wrote but it doesn't work.

This is fixed with https://github.com/flutter/plugins/pull/2343.
Please try webview_flutter in 0.3.19+4.
If you see some issue with the SafeArea after applying the patch, you can add a SafeArea widget around the WebView widget.

This worked for me, thank you!


MGMT-18898: Allow transition from ClusterInstallationTimedOut to installComplete

MGMT-18898: Allow transition from ClusterInstallationTimedOut to installComplete
In case installation timed out but reconcilation ran we still want to validate if cluster managed to be installed or not, in case it finished successfully after timeout we will set installed

/retest

/test images

/lgtm

Based on the definitions in https://github.com/openshift/hive/blob/master/docs/enhancements/cluster-install-apis.md I think we're not using these conditions the correct way as of this change.
Specifically "stopped".
From the doc:

True once the controller is no longer working to reach desired state. Does not imply success or failure by itself, but can be combined with Completed/Failed.

If we're actually continuing to monitor the cluster, why not just not do a timeout or extend it?


Use flag's string type in usage

I have my own values in go program and values in usage were showed before like that:

It's fully informative, although my flags have type and return it in Type() method.
I think, with this PR library will be more flexible and everyone can see their own type. Now it looks like that:

I hope, you will merge this PR. It's very important for applications to be informative.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.


Update 1.12.1

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_f0cuz1ti52/clone/recipe/meta.yaml:45: non_url_source: A source of the recipe is not url of url type.
ERROR: /tmp/abs_f0cuz1ti52/clone/recipe/meta.yaml:45: missing_hash: The recipe is missing a sha256 checksum for a source file
WARNING: /tmp/abs_f0cuz1ti52/clone/recipe/meta.yaml:167: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_f0cuz1ti52/clone/recipe/meta.yaml:167: missing_description: The recipe is missing a description
WARNING: /tmp/abs_f0cuz1ti52/clone/recipe/meta.yaml:167: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_f0cuz1ti52/clone/recipe/meta.yaml:169: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_f0cuz1ti52/clone/recipe/meta.yaml:169: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_f0cuz1ti52/clone/recipe/meta.yaml:169: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_9cn69q0yfz/clone/recipe/meta.yaml:45: missing_hash: The recipe is missing a sha256 checksum for a source file
WARNING: /tmp/abs_9cn69q0yfz/clone/recipe/meta.yaml:45: non_url_source: A source of the recipe is not url of url type.
WARNING: /tmp/abs_9cn69q0yfz/clone/recipe/meta.yaml:167: missing_description: The recipe is missing a description
WARNING: /tmp/abs_9cn69q0yfz/clone/recipe/meta.yaml:167: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_9cn69q0yfz/clone/recipe/meta.yaml:167: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_9cn69q0yfz/clone/recipe/meta.yaml:169: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_9cn69q0yfz/clone/recipe/meta.yaml:169: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_9cn69q0yfz/clone/recipe/meta.yaml:169: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_66pb2xtkto/clone/recipe/meta.yaml:45: missing_hash: The recipe is missing a sha256 checksum for a source file
WARNING: /tmp/abs_66pb2xtkto/clone/recipe/meta.yaml:45: non_url_source: A source of the recipe is not url of url type.
WARNING: /tmp/abs_66pb2xtkto/clone/recipe/meta.yaml:167: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_66pb2xtkto/clone/recipe/meta.yaml:167: missing_description: The recipe is missing a description
WARNING: /tmp/abs_66pb2xtkto/clone/recipe/meta.yaml:167: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_66pb2xtkto/clone/recipe/meta.yaml:169: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_66pb2xtkto/clone/recipe/meta.yaml:169: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_66pb2xtkto/clone/recipe/meta.yaml:169: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_34th0ijcd5/clone/recipe/meta.yaml:45: non_url_source: A source of the recipe is not url of url type.
ERROR: /tmp/abs_34th0ijcd5/clone/recipe/meta.yaml:45: missing_hash: The recipe is missing a sha256 checksum for a source file
WARNING: /tmp/abs_34th0ijcd5/clone/recipe/meta.yaml:167: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_34th0ijcd5/clone/recipe/meta.yaml:167: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_34th0ijcd5/clone/recipe/meta.yaml:167: missing_description: The recipe is missing a description
WARNING: /tmp/abs_34th0ijcd5/clone/recipe/meta.yaml:169: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_34th0ijcd5/clone/recipe/meta.yaml:169: missing_description: The recipe is missing a description
WARNING: /tmp/abs_34th0ijcd5/clone/recipe/meta.yaml:169: missing_license_url: The recipe is missing a license_url
Errors were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_c8d_q5jq_1/clone/recipe/meta.yaml:45: non_url_source: A source of the recipe is not url of url type.
ERROR: /tmp/abs_c8d_q5jq_1/clone/recipe/meta.yaml:45: missing_hash: The recipe is missing a sha256 checksum for a source file
WARNING: /tmp/abs_c8d_q5jq_1/clone/recipe/meta.yaml:167: missing_description: The recipe is missing a description
WARNING: /tmp/abs_c8d_q5jq_1/clone/recipe/meta.yaml:167: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_c8d_q5jq_1/clone/recipe/meta.yaml:167: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_c8d_q5jq_1/clone/recipe/meta.yaml:169: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_c8d_q5jq_1/clone/recipe/meta.yaml:169: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_c8d_q5jq_1/clone/recipe/meta.yaml:169: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_b2wqmjes_1/clone/recipe/meta.yaml:47: non_url_source: A source of the recipe is not url of url type.
ERROR: /tmp/abs_b2wqmjes_1/clone/recipe/meta.yaml:47: missing_hash: The recipe is missing a sha256 checksum for a source file
WARNING: /tmp/abs_b2wqmjes_1/clone/recipe/meta.yaml:171: missing_description: The recipe is missing a description
WARNING: /tmp/abs_b2wqmjes_1/clone/recipe/meta.yaml:171: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_b2wqmjes_1/clone/recipe/meta.yaml:171: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_b2wqmjes_1/clone/recipe/meta.yaml:173: missing_description: The recipe is missing a description
WARNING: /tmp/abs_b2wqmjes_1/clone/recipe/meta.yaml:173: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_b2wqmjes_1/clone/recipe/meta.yaml:173: missing_doc_source_url: The recipe is missing a doc_source_url
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_58znmv9h2z/clone/recipe/meta.yaml:47: missing_hash: The recipe is missing a sha256 checksum for a source file
WARNING: /tmp/abs_58znmv9h2z/clone/recipe/meta.yaml:47: non_url_source: A source of the recipe is not url of url type.
WARNING: /tmp/abs_58znmv9h2z/clone/recipe/meta.yaml:171: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_58znmv9h2z/clone/recipe/meta.yaml:171: missing_description: The recipe is missing a description
WARNING: /tmp/abs_58znmv9h2z/clone/recipe/meta.yaml:171: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_58znmv9h2z/clone/recipe/meta.yaml:173: missing_description: The recipe is missing a description
WARNING: /tmp/abs_58znmv9h2z/clone/recipe/meta.yaml:173: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_58znmv9h2z/clone/recipe/meta.yaml:173: missing_license_url: The recipe is missing a license_url
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_f7_7h1xh39/clone/recipe/meta.yaml:47: missing_hash: The recipe is missing a sha256 checksum for a source file
WARNING: /tmp/abs_f7_7h1xh39/clone/recipe/meta.yaml:47: non_url_source: A source of the recipe is not url of url type.
WARNING: /tmp/abs_f7_7h1xh39/clone/recipe/meta.yaml:171: missing_description: The recipe is missing a description
WARNING: /tmp/abs_f7_7h1xh39/clone/recipe/meta.yaml:171: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_f7_7h1xh39/clone/recipe/meta.yaml:171: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_f7_7h1xh39/clone/recipe/meta.yaml:173: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_f7_7h1xh39/clone/recipe/meta.yaml:173: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_f7_7h1xh39/clone/recipe/meta.yaml:173: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_2dbjyvqmmx/clone/recipe/meta.yaml:47: missing_hash: The recipe is missing a sha256 checksum for a source file
WARNING: /tmp/abs_2dbjyvqmmx/clone/recipe/meta.yaml:47: non_url_source: A source of the recipe is not url of url type.
WARNING: /tmp/abs_2dbjyvqmmx/clone/recipe/meta.yaml:171: missing_description: The recipe is missing a description
WARNING: /tmp/abs_2dbjyvqmmx/clone/recipe/meta.yaml:171: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_2dbjyvqmmx/clone/recipe/meta.yaml:171: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_2dbjyvqmmx/clone/recipe/meta.yaml:173: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_2dbjyvqmmx/clone/recipe/meta.yaml:173: missing_description: The recipe is missing a description
WARNING: /tmp/abs_2dbjyvqmmx/clone/recipe/meta.yaml:173: missing_doc_source_url: The recipe is missing a doc_source_url
Errors were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_ba4xf3ie6n/clone/recipe/meta.yaml:47: non_url_source: A source of the recipe is not url of url type.
ERROR: /tmp/abs_ba4xf3ie6n/clone/recipe/meta.yaml:47: missing_hash: The recipe is missing a sha256 checksum for a source file
WARNING: /tmp/abs_ba4xf3ie6n/clone/recipe/meta.yaml:170: missing_description: The recipe is missing a description
WARNING: /tmp/abs_ba4xf3ie6n/clone/recipe/meta.yaml:170: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_ba4xf3ie6n/clone/recipe/meta.yaml:170: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_ba4xf3ie6n/clone/recipe/meta.yaml:172: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_ba4xf3ie6n/clone/recipe/meta.yaml:172: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_ba4xf3ie6n/clone/recipe/meta.yaml:172: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_75aolfsmne/clone/recipe/meta.yaml:48: missing_hash: The recipe is missing a sha256 checksum for a source file
WARNING: /tmp/abs_75aolfsmne/clone/recipe/meta.yaml:48: non_url_source: A source of the recipe is not url of url type.
WARNING: /tmp/abs_75aolfsmne/clone/recipe/meta.yaml:171: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_75aolfsmne/clone/recipe/meta.yaml:171: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_75aolfsmne/clone/recipe/meta.yaml:171: missing_description: The recipe is missing a description
WARNING: /tmp/abs_75aolfsmne/clone/recipe/meta.yaml:173: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_75aolfsmne/clone/recipe/meta.yaml:173: missing_description: The recipe is missing a description
WARNING: /tmp/abs_75aolfsmne/clone/recipe/meta.yaml:173: missing_license_url: The recipe is missing a license_url
Errors were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_11u7ak5iia/clone/recipe/meta.yaml:48: non_url_source: A source of the recipe is not url of url type.
ERROR: /tmp/abs_11u7ak5iia/clone/recipe/meta.yaml:48: missing_hash: The recipe is missing a sha256 checksum for a source file
WARNING: /tmp/abs_11u7ak5iia/clone/recipe/meta.yaml:171: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_11u7ak5iia/clone/recipe/meta.yaml:171: missing_description: The recipe is missing a description
WARNING: /tmp/abs_11u7ak5iia/clone/recipe/meta.yaml:171: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_11u7ak5iia/clone/recipe/meta.yaml:173: missing_description: The recipe is missing a description
WARNING: /tmp/abs_11u7ak5iia/clone/recipe/meta.yaml:173: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_11u7ak5iia/clone/recipe/meta.yaml:173: missing_license_url: The recipe is missing a license_url
Errors were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_a5kqcapz12/clone/recipe/meta.yaml:48: non_url_source: A source of the recipe is not url of url type.
ERROR: /tmp/abs_a5kqcapz12/clone/recipe/meta.yaml:48: missing_hash: The recipe is missing a sha256 checksum for a source file
WARNING: /tmp/abs_a5kqcapz12/clone/recipe/meta.yaml:171: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_a5kqcapz12/clone/recipe/meta.yaml:171: missing_description: The recipe is missing a description
WARNING: /tmp/abs_a5kqcapz12/clone/recipe/meta.yaml:171: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_a5kqcapz12/clone/recipe/meta.yaml:173: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_a5kqcapz12/clone/recipe/meta.yaml:173: missing_description: The recipe is missing a description
WARNING: /tmp/abs_a5kqcapz12/clone/recipe/meta.yaml:173: missing_license_url: The recipe is missing a license_url
Errors were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_3ed1poh2bu/clone/recipe/meta.yaml:48: non_url_source: A source of the recipe is not url of url type.
ERROR: /tmp/abs_3ed1poh2bu/clone/recipe/meta.yaml:48: missing_hash: The recipe is missing a sha256 checksum for a source file
WARNING: /tmp/abs_3ed1poh2bu/clone/recipe/meta.yaml:171: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_3ed1poh2bu/clone/recipe/meta.yaml:171: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_3ed1poh2bu/clone/recipe/meta.yaml:171: missing_description: The recipe is missing a description
WARNING: /tmp/abs_3ed1poh2bu/clone/recipe/meta.yaml:173: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_3ed1poh2bu/clone/recipe/meta.yaml:173: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_3ed1poh2bu/clone/recipe/meta.yaml:173: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_ab9ma6h3lo/clone/recipe/meta.yaml:48: non_url_source: A source of the recipe is not url of url type.
ERROR: /tmp/abs_ab9ma6h3lo/clone/recipe/meta.yaml:48: missing_hash: The recipe is missing a sha256 checksum for a source file
WARNING: /tmp/abs_ab9ma6h3lo/clone/recipe/meta.yaml:171: missing_description: The recipe is missing a description
WARNING: /tmp/abs_ab9ma6h3lo/clone/recipe/meta.yaml:171: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_ab9ma6h3lo/clone/recipe/meta.yaml:171: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_ab9ma6h3lo/clone/recipe/meta.yaml:173: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_ab9ma6h3lo/clone/recipe/meta.yaml:173: missing_description: The recipe is missing a description
WARNING: /tmp/abs_ab9ma6h3lo/clone/recipe/meta.yaml:173: missing_doc_source_url: The recipe is missing a doc_source_url
Errors were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_c6_byxn05i/clone/recipe/meta.yaml:48: non_url_source: A source of the recipe is not url of url type.
ERROR: /tmp/abs_c6_byxn05i/clone/recipe/meta.yaml:48: missing_hash: The recipe is missing a sha256 checksum for a source file
WARNING: /tmp/abs_c6_byxn05i/clone/recipe/meta.yaml:171: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_c6_byxn05i/clone/recipe/meta.yaml:171: missing_description: The recipe is missing a description
WARNING: /tmp/abs_c6_byxn05i/clone/recipe/meta.yaml:171: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_c6_byxn05i/clone/recipe/meta.yaml:173: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_c6_byxn05i/clone/recipe/meta.yaml:173: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_c6_byxn05i/clone/recipe/meta.yaml:173: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_18ng3skicb/clone/recipe/meta.yaml:49: non_url_source: A source of the recipe is not url of url type.
ERROR: /tmp/abs_18ng3skicb/clone/recipe/meta.yaml:49: missing_hash: The recipe is missing a sha256 checksum for a source file
WARNING: /tmp/abs_18ng3skicb/clone/recipe/meta.yaml:172: missing_description: The recipe is missing a description
WARNING: /tmp/abs_18ng3skicb/clone/recipe/meta.yaml:172: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_18ng3skicb/clone/recipe/meta.yaml:172: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_18ng3skicb/clone/recipe/meta.yaml:174: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_18ng3skicb/clone/recipe/meta.yaml:174: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_18ng3skicb/clone/recipe/meta.yaml:174: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_5byhfuh1lo/clone/recipe/meta.yaml:49: non_url_source: A source of the recipe is not url of url type.
ERROR: /tmp/abs_5byhfuh1lo/clone/recipe/meta.yaml:49: missing_hash: The recipe is missing a sha256 checksum for a source file
WARNING: /tmp/abs_5byhfuh1lo/clone/recipe/meta.yaml:172: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_5byhfuh1lo/clone/recipe/meta.yaml:172: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_5byhfuh1lo/clone/recipe/meta.yaml:172: missing_description: The recipe is missing a description
WARNING: /tmp/abs_5byhfuh1lo/clone/recipe/meta.yaml:174: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_5byhfuh1lo/clone/recipe/meta.yaml:174: missing_description: The recipe is missing a description
WARNING: /tmp/abs_5byhfuh1lo/clone/recipe/meta.yaml:174: missing_doc_source_url: The recipe is missing a doc_source_url
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_433d4zx6zy/clone/recipe/meta.yaml:49: missing_hash: The recipe is missing a sha256 checksum for a source file
WARNING: /tmp/abs_433d4zx6zy/clone/recipe/meta.yaml:49: non_url_source: A source of the recipe is not url of url type.
WARNING: /tmp/abs_433d4zx6zy/clone/recipe/meta.yaml:172: missing_description: The recipe is missing a description
WARNING: /tmp/abs_433d4zx6zy/clone/recipe/meta.yaml:172: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_433d4zx6zy/clone/recipe/meta.yaml:172: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_433d4zx6zy/clone/recipe/meta.yaml:174: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_433d4zx6zy/clone/recipe/meta.yaml:174: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_433d4zx6zy/clone/recipe/meta.yaml:174: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_d9h5yt62sn/clone/recipe/meta.yaml:49: missing_hash: The recipe is missing a sha256 checksum for a source file
WARNING: /tmp/abs_d9h5yt62sn/clone/recipe/meta.yaml:49: non_url_source: A source of the recipe is not url of url type.
WARNING: /tmp/abs_d9h5yt62sn/clone/recipe/meta.yaml:172: missing_description: The recipe is missing a description
WARNING: /tmp/abs_d9h5yt62sn/clone/recipe/meta.yaml:172: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_d9h5yt62sn/clone/recipe/meta.yaml:172: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_d9h5yt62sn/clone/recipe/meta.yaml:174: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_d9h5yt62sn/clone/recipe/meta.yaml:174: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_d9h5yt62sn/clone/recipe/meta.yaml:174: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_48ef_j4qiz/clone/recipe/meta.yaml:49: missing_hash: The recipe is missing a sha256 checksum for a source file
WARNING: /tmp/abs_48ef_j4qiz/clone/recipe/meta.yaml:49: non_url_source: A source of the recipe is not url of url type.
WARNING: /tmp/abs_48ef_j4qiz/clone/recipe/meta.yaml:172: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_48ef_j4qiz/clone/recipe/meta.yaml:172: missing_description: The recipe is missing a description
WARNING: /tmp/abs_48ef_j4qiz/clone/recipe/meta.yaml:172: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_48ef_j4qiz/clone/recipe/meta.yaml:174: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_48ef_j4qiz/clone/recipe/meta.yaml:174: missing_description: The recipe is missing a description
WARNING: /tmp/abs_48ef_j4qiz/clone/recipe/meta.yaml:174: missing_license_url: The recipe is missing a license_url
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_b7d_cz09ds/clone/recipe/meta.yaml:49: missing_hash: The recipe is missing a sha256 checksum for a source file
WARNING: /tmp/abs_b7d_cz09ds/clone/recipe/meta.yaml:49: non_url_source: A source of the recipe is not url of url type.
WARNING: /tmp/abs_b7d_cz09ds/clone/recipe/meta.yaml:172: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_b7d_cz09ds/clone/recipe/meta.yaml:172: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_b7d_cz09ds/clone/recipe/meta.yaml:172: missing_description: The recipe is missing a description
WARNING: /tmp/abs_b7d_cz09ds/clone/recipe/meta.yaml:174: missing_description: The recipe is missing a description
WARNING: /tmp/abs_b7d_cz09ds/clone/recipe/meta.yaml:174: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_b7d_cz09ds/clone/recipe/meta.yaml:174: missing_doc_source_url: The recipe is missing a doc_source_url
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_a9ngqcykjf/clone/recipe/meta.yaml:48: invalid_url: https://github.com/pytorch/pytorch/releases/download/v1.12.1/pytorch-1.12.1.tar.gz : Not reachable: 404
WARNING: /tmp/abs_a9ngqcykjf/clone/recipe/meta.yaml:176: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_a9ngqcykjf/clone/recipe/meta.yaml:176: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_a9ngqcykjf/clone/recipe/meta.yaml:178: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_a9ngqcykjf/clone/recipe/meta.yaml:178: missing_license_url: The recipe is missing a license_url
Errors were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_56wtiy4lxq/clone/recipe/meta.yaml:176: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_56wtiy4lxq/clone/recipe/meta.yaml:176: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_56wtiy4lxq/clone/recipe/meta.yaml:178: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_56wtiy4lxq/clone/recipe/meta.yaml:178: missing_doc_source_url: The recipe is missing a doc_source_url
Warnings were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_92qynmzp8k/clone/recipe/meta.yaml:177: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_92qynmzp8k/clone/recipe/meta.yaml:177: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_92qynmzp8k/clone/recipe/meta.yaml:179: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_92qynmzp8k/clone/recipe/meta.yaml:179: missing_license_url: The recipe is missing a license_url
Warnings were found

Note the linter errors are false positives

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_443yl81hm2/clone/recipe/meta.yaml:177: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_443yl81hm2/clone/recipe/meta.yaml:177: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_443yl81hm2/clone/recipe/meta.yaml:179: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_443yl81hm2/clone/recipe/meta.yaml:179: missing_license_url: The recipe is missing a license_url
Warnings were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_bexyhic5hj/clone/recipe/meta.yaml:177: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_bexyhic5hj/clone/recipe/meta.yaml:177: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_bexyhic5hj/clone/recipe/meta.yaml:179: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_bexyhic5hj/clone/recipe/meta.yaml:179: missing_license_url: The recipe is missing a license_url
Warnings were found


Fix "too complex" error in belongs expression

This PR solves this support issue https://github.com/CartoDB/support/issues/2197

🆒 A super-nice job with this @elenatorro, thx!


[PrestoSQL 316] Select filter query from prestocli fails with decimal overflow error

Environment - PrestoSQL 316, Spark 2.4.5, Carbon 2.0.1
Steps -
From SparkSQL create carbondata table and load data to table.
create table Test_Boundary (c1_int int,c2_Bigint Bigint,c3_Decimal Decimal(38,38),c4_double double,c5_string string,c6_Timestamp Timestamp,c7_Datatype_Desc string) stored as carbondata;
LOAD DATA INPATH 'hdfs://hacluster/chetan/Test_Data1.csv' INTO table Test_Boundary OPTIONS('DELIMITER'=',','QUOTECHAR'='','BAD_RECORDS_ACTION'='FORCE','FILEHEADER'='');
Issue : Select filter query from prestocli fails with decimal overflow error
presto:chetan> select min(c3_Decimal),max(c3_Decimal),sum(c3_Decimal),avg(c3_Decimal) , count(c3_Decimal), variance(c3_Decimal) from test_boundary where exp(c1_int)=0.0 or exp(c1_int)=1.0;
Query 20200804_142831_00527_ed34h, FAILED, 2 nodes
Splits: 18 total, 17 done (94.44%)
0:00 [16 rows, 0B] [63 rows/s, 0B/s]
Query 20200804_142831_00527_ed34h failed: Decimal overflow
Log-
2020-08-04T22:28:31.712+0800 ERROR remote-task-callback-635 io.prestosql.execution.StageStateMachine Stage 20200804_142831_00527_ed34h.0 failed
java.lang.ArithmeticException: Decimal overflow
at io.prestosql.spi.type.UnscaledDecimal128Arithmetic.throwOverflowException(UnscaledDecimal128Arithmetic.java:1663)
at io.prestosql.spi.type.UnscaledDecimal128Arithmetic.throwIfOverflows(UnscaledDecimal128Arithmetic.java:807)
at io.prestosql.operator.aggregation.DecimalSumAggregation.outputLongDecimal(DecimalSumAggregation.java:174)
at io.prestosql.$gen.Decimal_38_38_Decimal_38_38_SumAccumulator_20200804_142831_454.evaluateFinal(Unknown Source)
at io.prestosql.operator.Aggregator.evaluate(Aggregator.java:71)
at io.prestosql.operator.AggregationOperator.getOutput(AggregationOperator.java:181)
at io.prestosql.operator.Driver.processInternal(Driver.java:379)
at io.prestosql.operator.Driver.lambda$processFor$8(Driver.java:283)
at io.prestosql.operator.Driver.tryWithLock(Driver.java:675)
at io.prestosql.operator.Driver.processFor(Driver.java:276)
at io.prestosql.execution.SqlTaskExecution$DriverSplitRunner.processFor(SqlTaskExecution.java:1075)
at io.prestosql.execution.executor.PrioritizedSplitRunner.process(PrioritizedSplitRunner.java:163)
at io.prestosql.execution.executor.TaskExecutor$TaskRunner.run(TaskExecutor.java:484)
at io.prestosql.$gen.Presto_316____20200804_043006_1.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
2020-08-04T22:28:31.721+0800 INFO dispatcher-query-471 io.prestosql.event.QueryMonitor TIMELINE: Query 20200804_142831_00527_ed34h :: Transaction:[964fbdbf-23e5-4e54-b54a-a10250944b25] :: elapsed 252ms :: planning 104ms :: waiting 22ms :: scheduling 41ms :: running 97ms :: finishing 10ms :: begin 2020-08-04T22:28:31.460+08:00 :: end 2020-08-04T22:28:31.712+08:00

If the sum overflows the type, the query fails.  This behavior is defined in the ANSI SQL spec we follow in Presto.
That said, it is possible this is caused by bad data in the Carbondata code you are using. How are you integrating with carbon data? I don't believe that Presto supports this natively.
I'm going to close this issue.  We can followup about the carbondata code in one of the other issues you filed.


Add CanDestroyInCreativeComponent and BlockPlacerComponent

Can you please describe if CanDestroyInCreativeComponent is neccesary as that seems like a server-side feature. Can you also please describe the BlockPlacerComponent and what it does?

Thanks for the contribution!


Angular directive attributes get removed from translate-values

Hi! I'm using Angular translate 2.12. I've got a link similar to this:
<p class="board-helper__txt"
                   translate
                   translate-compile
                   translate-values="{
                        tasksLink: 'tasks',
                        risksLink: 'risks'
                   }"
                >objectives_help-2_content-1

Issue is this gets compiled into a link without ui-sref directive.
tasks

What am I doing wrong with it? Thanks!

Hello,
as we had already mentioned in the issue's template, we need a working and as minimal as possible demo covering your specific use case or issue.
Follow these steps:

Please open this plnkr base.
Fork it (at the top left).
Ensure the version of AngularJS and angular-translate is correct.
Ensure all angular-translate plugins are available; reduce and remove anything you can.
Write a minimal as possible demo for your specific issue.
Save and freeze. Provide us the final link to your demo.

Maybe a sanitize strategy chosen which removes html off values?

Hello,
I'm closing this issue due inactivity. We have asked for additional details, but you could not helped us. Therefore we close this issue as not reproducible.
If you still have an issue, please create a new issue because we cannot be sure to track closed issues.


Allow actor types to have labels in addition to their machine name

In GitLab by @Asacolips on Jul 9, 2021, 14:49
Example
[overlord]
  label = "Overlord"

  [overlord.stats]
    ...

Labels (do-not-change)
/cc @Asacolips

In GitLab by @mclemente on Nov 13, 2023, 20:18
mentioned in commit 0a55c7791288ed8db66d245ff71ffc58814f284b


Add to-yaml, from-yaml builtins

When writing a script to handle yaml, It's quite annoying as no language supports yaml format natively and have to install dependancies. If it's json, jq works fine, but cli tools for yaml like yq is quite annoying as there's quite many different versions of it. It would be quite useful if elvish can natively support various formats just like json.
fixes #1155

test for thatOutputErrorIsBubbled is commented out as I just can't get an easy fix. If implementation is accepted, I wish I can get some help.

This is a fine feature by itself. I'm not a fan of YAML, but supporting YAML in Elvish is a good idea since YAML is already used in quite a few places.
However, the additional dependency is quite chunky and adds 516,016 bytes to the Elvish binary in my local environment (darwin/amd64). Elvish's binary is already pretty large and I'm not quite keen to take on more dependency at the moment. So sorry, I'm going to close this PR.
Right now what I can offer as a workaround is to use a command to convert YAML from and to JSON in combination of from-json and to-json to implement from-yaml and to-yaml:
fn from-yaml { yj | from-json }
fn to-yaml { to-json | yj -r }

The main disadvantage is that the user needs to install yj themself, and there is no uniform way to do that across the platforms Elvish supports. For that I've written down some ideas in #1607.


Update s_client and s_server documentation about some missing arguments

I am completely lost with Git / GitHub :-(
Looks like I added unrelated commit (SRP one) into this pull request, Sorry for that.

Guess I should have created a distinct branch for each topic to avoid my last commit to join the 'current' PR ?

No, one merge request with all your changes in it is what we want.  Do something like this to undo the wrong-file changes:
git diff master ssl/statem/statem_srvr.c | patch -R
# verify that your changes are "undone"
git add ssl/statem/statem_srvr.c
git commit --am --no-e
git push -f github HEAD

Thanks Ritch for helping me with git. Seems that I was able to remove the last commit, but it was not without pain... (I am working under Windows using TortoiseGit).
Next big challenge : pushing the removed commit into its own, ANOTHER PR ...
;-)

a22f9c8 on master and d67fe76 on 1.1.0  thank you!


Improve warnings on unnecessary storage annotations

Fixes #1183: just trying to improve the error message.
This PR also provides a fix for the following issue: the purity analyzer did not report the case where both read and write storage annotations were unused, i.e. in this case there were no warnings:
contract;

abi MyContract {
    #[storage(read, write)]
    fn foo() -> u64;
}

impl MyContract for Contract {
    #[storage(read, write)]
    fn foo() -> u64 {
        0
    }
}

Thanks for your quick reviews, folks!


78 setup a minimal ci with es lint

Solving issue #78
Installing prettier and adding prettier check and run commands in package.json
Adding prettier ignore
Adding prettier config (prettierrc.json)
Adding prettier YAML script 'prettier-check.yml'
updating changelog

Looks good but there are conflicts to solve @ZMomo (we integrated a few little things in between I guess).
The easiest way would be to rebase and keep all the changes from the dev branch, and then re-run prettier
Let me know how it goes :)


Validation doesn't work for hidden input (display: none)

If a file input has CSS display: none property, validation passes with "true" result.

add ignore:[] paramter in validate, then hiddens will not be ignored


write_result() missing 1 required positional argument: 'options'

Discussed in https://github.com/dmarx/video-killed-the-radio-star/discussions/130

Originally posted by Kinggibbon1987 April 13, 2023
When I Infer speech from audio, I keep getting this error. Anyone know how to fix this ? This happens with and without whisper_seg checked

hey man im stuck here too !


Request: clarify what information is stored to snyk with snyk monitor

Hi,
I guess it is safe to assume that when starting to monitor a project with snyk monitor, it's only the package.json content which is pulled to snyk servers for monitoring. However, would be great to see this clarified in the docs explicitly (and/or also to be able to observe this data from my project page).

Hello,
This is covered in our Terms of Service, in Section 9 - "Project Data and Rights you give us" - and can be found here: https://snyk.io/policies
The Terms of Service has more detail that is worth reading, but to answer your question about what data we access, here is the relevant paragraph:
"This information includes, but is not limited to, information relating to the project (such as the project name and metadata), information relating to the dependencies, including open source and closed source but locally available to our tool, being used and how they are referenced by the project, Snyk-related files and environmental information (“Project Information”). We may also collect Project Information for each of the project’s dependencies (“Dependency Information”)."
Does this clarify it?

Hi,
Thanks, didn't realize to check the Terms of Service. Its content clarifies things indeed, although if I'd be very worried about the source code of my private repository, the ToS content might not be quite enough to convince me (I see "usual" parts such as the "[..] but is not limited to" etc).
But in any case, the potential risk is the same in all similar services, so in the case of a developer extremely cautious about the project sources, all similar cloud-style services would be out of the question.  Thus, all in all, all good here, thanks for the response, don't mean to go into hair-splitting mood here. A potential practical thing to keep this part more transparent would be to have all data related to a project visible/downloadable from your service.