fix header hover issue, removed transition

@keybase/react-hackers if its a warning you should see it on hovering the x always. Having this an the animation doesn't really work so we backed that out (approved by design, they never wanted animation in the first place here)

:+1:


PURL to the rescue

Should fix: #21

Codecov Report

Merging #22 (6feedc9) into develop (7630fb7) will decrease coverage by 1.51%.
The diff coverage is 97.59%.

@@             Coverage Diff             @@
##           develop      #22      +/-   ##
===========================================
- Coverage    99.48%   97.97%   -1.52%
===========================================
  Files           11        5       -6
  Lines          392      148     -244
===========================================
- Hits           390      145     -245
- Misses           2        3       +1

Flag
Coverage Δ

unittests
97.97% <97.59%> (-1.52%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

mdbom/bom/processor.py
93.47% <94.11%> (-6.53%)
:arrow_down:

mdbom/bom/bom.py
100.00% <100.00%> (ø)

mdbom/bom/urls.py
100.00% <100.00%> (ø)

mdbom/mdbom.py
100.00% <100.00%> (+3.77%)
:arrow_up:

tests/bom/test_processor.py

tests/md/test_md.py

tests/test_mdbom.py

Continue to review full report at Codecov.

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


OverlayPortal breaks RenderAbstractViewport

Steps to reproduce

Create an OverlayPortal with 2 TextFields inside a Column as shown below
Focus the first TextField
Press TAB key to move to the next focus

Expected results
The focus moves to the next TextField
Actual results
The focus moves to the next TextField but failing an assertion:
The following assertion was thrown while processing the key message handler: RenderAbstractViewport.of() was called with a render object that was not a descendant of a RenderAbstractViewport. No RenderAbstractViewport render object ancestor could be found starting from the object that was passed to RenderAbstractViewport.of(). The render object where the viewport search started was:   RenderPointerListener#ebb53 relayoutBoundary=up11
Code sample
Code sample
OverlayPortal(
  controller: c,
  overlayChildBuilder: (context) => Column(
    children: [
      TextField(),
      TextField(),
    ],
  ),
),

Screenshots or Video
No response
Logs
Logs
══╡ EXCEPTION CAUGHT BY SERVICES LIBRARY ╞══════════════════════════════════════════════════════════
The following assertion was thrown while processing the key message handler:
RenderAbstractViewport.of() was called with a render object that was not a descendant of a
RenderAbstractViewport.
No RenderAbstractViewport render object ancestor could be found starting from the object that was
passed to RenderAbstractViewport.of().
The render object where the viewport search started was:
  RenderPointerListener#ebb53 relayoutBoundary=up11

When the exception was thrown, this was the stack:
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 294:3       throw_
packages/flutter/src/rendering/viewport.dart 68:9                                 <fn>
packages/flutter/src/rendering/viewport.dart 77:14                                of
packages/flutter/src/widgets/scroll_position.dart 800:68                          ensureVisible
packages/flutter/src/widgets/scrollable.dart 1038:55                              [_performEnsureVisible]
packages/flutter/src/widgets/scrollable.dart 474:44                               ensureVisible
packages/flutter/src/widgets/focus_traversal.dart 181:16                          defaultTraversalRequestFocusCallback
packages/flutter/src/widgets/focus_traversal.dart 522:29                          [_moveFocus]
packages/flutter/src/widgets/focus_traversal.dart 295:39                          next
packages/flutter/src/widgets/focus_manager.dart 1149:46                           nextFocus
packages/flutter/src/widgets/focus_traversal.dart 1914:12                         invoke
packages/flutter/src/widgets/actions.dart 338:16                                  [_invoke]
packages/flutter/src/widgets/actions.dart 666:27                                  invokeActionIfEnabled
packages/flutter/src/widgets/shortcuts.dart 851:81                                handleKeypress
packages/flutter/src/widgets/shortcuts.dart 1042:20                               [_handleOnKey]
packages/flutter/src/widgets/focus_manager.dart 1837:25                           handleKeyMessage
packages/flutter/src/services/hardware_keyboard.dart 996:16                       [_dispatchKeyMessage]
packages/flutter/src/services/hardware_keyboard.dart 1061:75                      handleRawKeyMessage
dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 84:54                runBody
dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 127:5                _async
packages/flutter/src/services/hardware_keyboard.dart 1022:51                      handleRawKeyMessage
packages/flutter/src/services/platform_channel.dart 223:49                        <fn>
dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 84:54                runBody
dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 127:5                _async
packages/flutter/src/services/platform_channel.dart 222:58                        <fn>
packages/flutter/src/services/binding.dart 567:35                                 <fn>
dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 84:54                runBody
dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 127:5                _async
packages/flutter/src/services/binding.dart 564:98                                 <fn>
lib/_engine/engine/platform_dispatcher.dart 1305:5                                invoke2
lib/ui/channel_buffers.dart 25:12                                                 invoke
lib/ui/channel_buffers.dart 65:7                                                  push
lib/ui/channel_buffers.dart 131:16                                                push
lib/_engine/engine/platform_dispatcher.dart 408:10                                invokeOnPlatformMessage
lib/_engine/engine/raw_keyboard.dart 145:30                                       [_handleHtmlEvent]
lib/_engine/engine/raw_keyboard.dart 12:7                                         <fn>
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 574:37  _checkAndCall
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 579:39  dcall

KeyMessage: KeyMessage([KeyDownEvent#b2ff6(physicalKey: PhysicalKeyboardKey#7002b(usbHidUsage:
  "0x0007002b", debugName: "Tab"), logicalKey: LogicalKeyboardKey#b151c(keyId: "0x100000009",
  keyLabel: "Tab", debugName: "Tab"), character: null, timeStamp: 0:00:07.447699)])
════════════════════════════════════════════════════════════════════════════════════════════════════

Flutter Doctor output
Doctor output
[✓] Flutter (Channel stable, 3.16.5, on macOS 14.2.1 23C71 darwin-arm64, locale it-IT)
    • Flutter version 3.16.5 on channel stable at /Users/leonardo/Documents/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 78666c8dc5 (3 weeks ago), 2023-12-19 16:14:14 -0800
    • Engine revision 3f3e560236
    • Dart version 3.2.3
    • DevTools version 2.28.4

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.2)
    • Android SDK at /Users/leonardo/Library/Android/sdk
    • Platform android-34, build-tools 33.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15C65
    • CocoaPods version 1.14.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)

[✓] VS Code (version 1.85.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.80.0

[✓] Connected device (3 available)
    • iPhone di Leonardo (mobile) • 00008120-000638C03AF3C01E • ios            • iOS 17.3 21D5026f
    • macOS (desktop)             • macos                     • darwin-arm64   • macOS 14.2.1 23C71 darwin-arm64
    • Chrome (web)                • chrome                    • web-javascript • Google Chrome 120.0.6099.199

[✓] Network resources
    • All expected network resources are available.

• No issues found!

Thanks for the report @LeoRc01
I am unable to replicate the reported error using latest stable and master channels. Below is runnable code sample I used:

 runnable code

import 'package:flutter/material.dart';

/// Flutter code sample for [OverlayPortal].

void main() => runApp(const OverlayPortalExampleApp());

class OverlayPortalExampleApp extends StatelessWidget {
  const OverlayPortalExampleApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        appBar: AppBar(title: const Text('OverlayPortal Example')),
        body: const Center(child: ClickableTooltipWidget()),
      ),
    );
  }
}

class ClickableTooltipWidget extends StatefulWidget {
  const ClickableTooltipWidget({super.key});

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

class ClickableTooltipWidgetState extends State<ClickableTooltipWidget> {
  final OverlayPortalController _tooltipController = OverlayPortalController();

  @override
  Widget build(BuildContext context) {
    return TextButton(
      onPressed: _tooltipController.toggle,
      child: DefaultTextStyle(
        style: DefaultTextStyle.of(context).style.copyWith(fontSize: 50),
        child: OverlayPortal(
          controller: _tooltipController,
          overlayChildBuilder: (context) => Column(
            children: [
              TextField(),
              TextField(),
            ],
          ),
          child: const Text('Press to show/hide tooltip'),
        ),
      ),
    );
  }
}

Can you try above and check ?

Hi, thanks for your answer.
Your code snippet above is working fine, but I still have some problems on my codebase and I may have understood why.
Would you please try out this code block and then try again but removing the SingleChildScrollView.
As of my experience, if I keep the SingleChildScrollView it will throw me the assertion error. If I remove it, it will work just fine.
Same thing happens whenever I wrap the OverlayPortal in a scrollable view.
Thank you for your attention.
import 'package:flutter/material.dart';

void main() => runApp(ExampleApp());

class ExampleApp extends StatelessWidget {
  ExampleApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Example(),
    );
  }
}

class Example extends StatelessWidget {
  Example({super.key});

  final portalController = OverlayPortalController();

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: Padding(
        padding: const EdgeInsets.all(8.0),
        child: SingleChildScrollView(
          child: Column(
            mainAxisAlignment: MainAxisAlignment.center,
            children: [
              OverlayPortal(
                controller: portalController,
                overlayChildBuilder: (context) => FocusTraversalGroup(
                  child: Card(
                    child: Column(
                      children: [
                        TextField(),
                        TextField(),
                      ],
                    ),
                  ),
                ),
              ),
              FilledButton(
                  onPressed: () {
                    portalController.toggle();
                  },
                  child: Text('SHOW OVERLAY'))
            ],
          ),
        ),
      ),
    );
  }
}

Thanks for the update. I was able to replicate the reported exception on latest stable, but not on latest master where it appears to be fixed. See https://github.com/flutter/flutter/issues/140547 for reference.
So I suggest you to switch to latest master and run your scenario to see the error is fixed. Per our triage policy, I'll close this as fixed. The fix should be available in next stable release.


Use welcoming language

To comply with the new Swift code of conduct, let's make the language a little more welcoming.
Modifications:

Replaced usages of "sanity" with "soundness"
Added "sanity" to the list of unacceptable terms.
Changed the CI name to soundness

Result:

Swift HTTP Structured Headers is nicer.

@swift-server-bot add to whitelist

@swift-server-bot add to whitelist

@tomerd Can we update the CI here to support this changed language?

@tomerd Can we update the CI here to support this changed language?

@swift-server-bot test this please

@swift-server-bot test this please


Don’t set document.title when running in FastBoot

I would actually like this to work with fastboot properly, so apps running fastboot work with this addon out of the box.
@tomdale, could you suggest any approaches here? I'm not too familiar with fastboot, and don't know what the best approach for this would be.

Relevant code from ember-fastboot-server:
FastBootServer.prototype.insertIntoIndexHTML = function(title, body, head) {
  var html = this.html.replace("<!-- EMBER_CLI_FASTBOOT_BODY -->", body);

  if (title) {
    html = html.replace("<!-- EMBER_CLI_FASTBOOT_TITLE -->", "<title>" + title + "</title>");
  }
  if (head) {
    html = html.replace("<!-- EMBER_CLI_FASTBOOT_HEAD -->", head);
  }

  return html;
};

The title, body and head arguments can be traced back to ember-app.js#L113-L136:
/*
 * After the ApplicationInstance has finished rendering, serializes the
 * resulting DOM element into HTML to be transmitted back to the user agent.
 */
function serializeHTML(doc, rootElement) {
  return function(instance) {
    var head;

    if (doc.head) {
      head = HTMLSerializer.serialize(doc.head);
    }

    try {
      return {
        url: instance.getURL(), // TODO: use this to determine whether to 200 or redirect
        title: doc.title,
        head: head,
        body: HTMLSerializer.serialize(rootElement) // This matches the current code; but we probably want `serializeChildren` here
      };
    } finally {
      instance.destroy();
    }
  };
}

doc, in this case, is a simple-dom.Document.
In theory, ember-page-title should be compatible out of the box - at least it shouldn't throw. However, the order of
  if (title) {
    html = html.replace("<!-- EMBER_CLI_FASTBOOT_TITLE -->", "<title>" + title + "</title>");
  }
  if (head) {
    html = html.replace("<!-- EMBER_CLI_FASTBOOT_HEAD -->", head);
  }

should probably be reversed, so document.title takes precedence over the <head> inner HTML. Or am I missing something?

https://github.com/ember-fastboot/ember-fastboot-server/issues/32

@buschtoens The current order makes sense to me, but maybe we're thinking about it differently.
<title> is, by definition, subordinate to <head>. That is a <title> will always live inside a <head>, but a <head> may not necessarily have a <title>.
We added a convenience for <title>, since it's so common, but my feeling is that if you're specifying a <head> you can also specify a <title>. In any case, I think the presence of <title> clobbering <head> (as I think happens in the PR submitted) seems like it would surprise the end developer.
One thing that might be nice would be to have ember-page-title work in conjunction with https://github.com/ronco/ember-cli-head. But there's a general composability problem here and I would love some help thinking through it.

Sounds great! I'd be happy to help with this process to get ember-page-title and ember-cli-head working together

Paging @ronco

@tim-evans Can you hit me up on the ember community slack.  I'd love to talk through this with you, I need to tackle it myself for a couple other addons.

@tomdale,
@tim-evans just had a chat and here's the plan we're thinking of executing.  Please let us know what you think.
Update ember-cli-head to have basic title support.  This would be analogous to the simple title that was originally included in the ember-cli default index.html.  We would update the default head.hbs to:
<!-- `app/templates/head.hbs` -->
<!-- Add content you wish automatically added to the documents head -->
<!-- here. The 'model' available in this template can be populated by -->
<!-- setting values on the 'head-data' service. -->
<title>{{model.title}}</title>

Then ember-page-title can depend upon ember-cli-head, and update it's internal logic to set title on the head-data service.

@tim-evans I started looking into the updates to ember-cli-head as we discussed, and it became evident that won't be necessary.  We should be able to achieve FastBoot compatibility completely within this addon by using ember-cli-head.  I'll have a PR ready shortly, just ironing out the kinks.

Awesome. I looked through some of the code today, and saw that it was going to be super easy (just changing the page-title helper)

Closed by https://github.com/tim-evans/ember-page-title/pull/27.
This may require a minor change to your existing app. See https://github.com/tim-evans/ember-page-title#post-install-cleanup for more details :tada:


Signpost does not maintain correct arrow positioning on content update

[x ] bug
[ ] feature request
[ ] enhancement

Expected behavior
Signposts resize according to their content and maintain the correct positioning for the arrow to remain pointing at the signpost trigger origin
Actual behavior
When binding signpost to variable sized content, signpost are fixed to their top-left corner position while extending / shrinking the remaining window around this position.
Reproduction of behavior
Plunkr on request, but the behavior seems obvious enough.
Environment details

Angular version: 4.2.6

Clarity version: 0.10.0-alpha.4

OS and version: Windows 10 / latest

Browser: [ tested in Chrome / latest, probably in all browsers ]

@TekSiDoT: Thanks for filing the issue. Its always good to have the plnkr which replicates the issue. That way we know exactly what the issue is and make sure we test that case thoroughly before merging in the fix.

Alright, I'll add one.


fix(@angular-devkit/build-angular): add output location in build stats

This can be used by users to determine where the output path is located without needing to read the angular.json.

Merged into https://github.com/angular/angular-cli/pull/26995


Strings using \r do not get serialized with | notation

Hi @eemeli, it's been a while! 👋🏼 Just stumbled on this library of yours, thanks for making it!
Here’s a testcase of the issue: https://codepen.io/leaverou/pen/Rwqzadv
Input is:
{
	"language": "html",
	"code": "Username:\r\n<input name=\"username\">\r\n"
}

Expected output of YAML.stringify:
language: html
code: "Username:\r

  <input name=\"username\">\r

  "

Actual output:
language: html
code: |-
  Username:
  <input name="username">

This happens even when defaultStringType: "BLOCK_LITERAL" (it seems to only affect language: html.
When the \rs are removed, it produces the correct result.

👋 Hi! Are you sure that with that exact input, you're getting that exact output? Because it Works On My Machine™, and in your codepen example the \r are missing from the input.

{
	"language": "html",
	"code": "Username:\r\n<input name=\"username\">\r\n"
}

Gah, I was experimenting with the pen, not realizing it was in autosave mode. Restored it now.

Am confused. The codepen results now match your expected output?

Am confused. The codepen results now match your expected output?

Must not file issues at 3 in the morning — I had swapped "actual" and "expected 🤦🏽♀

Ok, that makes more sense. The reason for using the double-quoted form is that the input includes an explicit \r\n sequence, which can't be represented within a | block scalar. That's because the spec says this:

Line breaks inside scalar content must be normalized by the YAML processor. Each such line break must be parsed into a single line feed character. The original line break format is a presentation detail and must not be used to convey content information.

So in order to retain it, the carriage return must be escaped, and that means that the scalar value must be double-quoted, as that's the only scalar form which supports \ escapes.

Fair enough, thanks! I’ll close this then.


GoSublime: browse declarations and browse packages no response

There is no response when execute GoSublime: browse declarations and GoSublime: browse packages.The MarGo is pending at the "fetching pkg dirs" status.
** 2017-02-22 12:19:41.466289 **:
GoSublime init r17.02.16-1 (0.001s)
|   install margo: no
|   install state: done
| sublime.version: 3126
| sublime.channel: stable
|       about.ann: a17.02.16-1
|   about.version: r17.02.16-1
|         version: r17.02.16-1
|        platform: osx-x64
|            ~bin: ~/Library/Application Support/Sublime Text 3/Packages/User/GoSublime/osx-x64/bin
|       margo.exe: ~bin/gosublime.margo_r17.02.16-1_go1.8.exe (ok)
|          go.exe: /usr/local/opt/go/libexec/bin/go (ok)
|      go.version: go1.8
|          GOROOT: /usr/local/opt/go/libexec
|          GOPATH: ~/Work/code/goroot
|           GOBIN: (not set) (should usually be (not set))
|       set.shell: []
|       env.shell: /bin/zsh

shell.cmd: ['/bin/zsh', '-l', '-c', '${CMD}']

Same for me... just hangs.

Is go list all also slow?

Thanks @baloo32, is there any way I might be able to reproduce this?

Do you have large repos in GOPATH? any that I can clone?
Do you have lots of non-go files e.g. node_modules?

What's the slowest run of go list ./... inside GOROOT and each entry in GOPATH?
The current version of margo scans GOROOT and GOPATH in parallel so it should take only slightly longer than the slowest directory but I'm exploring faster ways to do said scanning before I port the package browsing over.

GOPATH directory contains 49 different repos, including our main work project - only in our own do we have lots of no .go files - as suggested, bulk is node_modules (using Angular for front end).
Hosted on secondary SSD drive.
Files in GOPATH:

Files excluding the project with node_modules:
8,082 files, 3,077 folders
~178Mb
List of packages in use:

go list ./... in GOROOT = 39 seconds
go list ./... in GOPATH = 1 minute 8 seconds
Hope that helps.

Thanks @baloo32.
For comparison:
Inside my GOROOT on Linux with i/o caches cleared I get ~5s from go list. Inside GOPATH with a lot of junk, go list is ~35s while my planned new solution using godirwalk is ~24s (~3s warm) with the actually directory traversal taking ~8s (~1.5s warm).
At the moment you can see the timings in the Sublime Text console at startup in line like margo:...Scan GOPATH...packages=123, list=12.3s. That timing is with go list so the planned solution will be faster and hopefully enables lazy loading of the package data which will also be cached so package browsing should take little to no extra time since many of the packages are already being loaded by autocompletion, etc.
We might also be able to speed it up more by skipping directories like node_modules.

Update: the new code (still experimental, with little testing) is on the next branch. It's not being used yet, but it's running at startup and prints timings in the Sublime Text console like margocode.go: VFS.Scan.....

After a bunch of optimization and experimentation, the junk GOPATH preloading is now ~10s (~1.5s warm) and GOROOT is ~350ms (~80ms warm).
If we need to re-scan the whole directory tree again e.g. due to running go get, that takes ~400ms and ~20ms respectively.


To do list Testing: Add and remove

Activities Done:

Used jest framework for testing.
Created a test file for testing add and remove functions.
Mocked the local storage.
Grouped tests using the describe() method.
Checked that it works properly.

THANK YOU


Include root node

Extended to have an option to include the root node in the sitemap

Thanks for the PR @AaronSadlerUK!
This is an issue that was also picked up in #2 - something I previously missed due to the way I structure my sites. Definitely a bug that needs fixing!
I'm not entirely sure about the approach you have taken. What is the use case for making this a configuration option? I don't know of a case where the site root shouldn't be included... Maybe you can think of one? 😊
In my opinion, the fix here should be simply changing DescendantsOrSelf to Descendants on line 39 of SitemapController. What do you think?

That was my initial thought, but then I figured someone may have a use for this even if I don't.

I have also added output caching of 1800, for larger sitemaps this will save massive overheads each on each request

The package does need a caching mechanism, but this needs to be carefully considered.
We can't cache the whole output of the controller, as the same controller may be used to render multiple sitemaps (based on the domain or configuration).
Furthermore we need a way to purge the sitemap cache on publish, and ensure this is done in a specific enough way that doesn't affect performance of other sitemaps.
Unfortunately I can't accept this pull request in its current form. There are 2 very separate features under this 1 PR that need to be reviewed separately.
If you're willing to submit a new PR with changing DescendantsOrSelf to Descendants on line 39 of SitemapController I will happily accept it.


new take on "Kompose will keep trying its job #477"

This is reopening of #477 there were some issues that we forgot to address.
Issue was that if it can't connect to cluster it panics.
Problem is that we continue after every error.
There should be return after some errors, and after every error in switch should be break so we don't
try to get reaper using client which creation field or calling Stop on reaper that field to create.
I've added new commit on top of  original @surajnarwade's commit, so its easier to review.
Once we agreed that this is the way we wan't to do it we can squash it

LGTM


Set Durability to 'HIGH' for most inputs and third-party libraries

That's exactly the improvement I wanted to see!

Lol wow


Add security policy

I believe I found a vulnerability in JStachio and would like to report it privately, so that it is not disclosed until you released a patch for it. Maybe you could add a security policy to the project (https://github.com/jstachio/jstachio/security)?
When looking into it, I just noticed there is a new Github Feature called Security Advisories, which sounds really neat: Privately discuss, fix, and publish information about security vulnerabilities in your repository's code.

Oh no!
Thank for the find!
I just saw some projects add the new security feature and forgot to put it on my TODO list.
I will be curious what it is as I imagine it is probably something to do with files being read from the annotation processor or the tiny bit of reflection in the runtime (ignoring jmustache).
BTW while I have you I was going to file a bug that JTE does not have reproducible builds from what I can tell. Build plugins and annotation processors ideally should be reproducible.

I'm going to close the issue. You can file it through the standard github process.
Again thanks for the find @casid !

@casid when you get a chance let me know if you can see the security issue as I’m not sure if I did it right.
BTW if it is about escaping HTML we can discuss but I can’t do context sensitive escaping and attribute escaping is a known issue in all Mustache implementations.


bug: Panic on Running Tests with Scarb Due to Issue in Sierra Code Generation

Panic on Running Tests with Scarb Due to Issue in Sierra Code Generation
Cairo version: 2.2.0
Scarb version: 0.7.0 (58cc88efb 2023-08-23)
Sierra version: 1.3.0
Current behavior:
When attempting to run tests on my Cairo contract using Scarb, a panic arises at a specific point within the Sierra crate (specifically within the cairo-lang-sierra-gas-2.2.0/src/gas_info.rs file). This panic appears to be triggered by a discrepancy in expected values at StatementIdx(49786), Pedersen.
Here is the full error:

Expected behavior:
scarb build does not catch this issue, but it surfaces when running tests with scarb test.
Steps to reproduce:

Clone the repository from https://github.com/henryf10h/reflect_cairo.
Navigate to the reflect_cairo directory.
Run the command scarb test to initiate the testing process.

Other information:
I am not fully versed with the inner workings of the Sierra or Cairo compiler, hence I might not understand the exact root of this issue. However, following the suggestions from the Scarb community, it seems like there might be a bug within the compiler.
Thanks beforehand.

This issue was already reported.


Side Scrolling Scene part

BTW how do I get the SatinFeather scenario to work. Keeps getting stuck at the Side Scrolling Scene part. It doesn't press the first "Skip" button but the second and it also doesn't press the "OK" button whn the item picked up screen pops up.

You need to change the setting so that the side scrolling scene is completely skipped

Ahhh aite aite thx man sry to bother xD
On Dec 29, 2017 11:00 PM, "Izra Faturrahman"<EMAIL_ADDRESS>wrote:

You need to change the setting so that the side scrolling scene is
completely skipped
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Frizz925/gbf-autopilot/issues/8#issuecomment-354456428,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQ1_IjvcXEFXU73ewQBUW3oyTeMcRWFzks5tFP6ggaJpZM4RPBfz
.


using latest api

Coverage remained the same at 15.775% when pulling 68c84624d20a76805c5aa7371ec46ca842fc1e2a on update-4.4.3 into 392608e59a5fb86e796728453e1e26af77bcee53 on master.


Script not unloaded when exception is thrown

Steps to reproduce the problem:

Don't give an argument to the script
e.g. mitmdump -s "examples/complex/har_dump.py"

Exception is thrown but the script keeps working and throws even more exceptions
Any other comments? What have you tried so far?
I haven't tried it for any other script, this may be har_dump.py specific issue but I think would affect other scripts as well.
Ideally, the script should be unloaded after throwing an exception
System information
Mitmproxy version: 2.0.0 (1.0.1dev0121-0xc540762)
Python version: 3.5.2
Platform: Linux-4.4.0-38-generic-x86_64-with-elementary-0.4-loki
SSL version: OpenSSL 1.0.2g  1 Mar 2016
Linux distro: "elementary" 0.4 loki

Yes, this sounds like a reasonable way to handle script errors.

I have been looking into this issue and got some idea about:

That's reasonable to unload the script if we meet some exceptions at the start stage, the most common case, as @ujjwal96 mentioned, is the user forget to give some arguments. In this situation, if we unload the script directly, the user could either restart the program with right arguments or go ahead without the script.
However, when we meets an exception in request or response stage,  if we unload the script immediately, I am not sure whether it is good for a developer to debug the script.
So my question is , should we put this unload mechanism only in the start stage or in the scriptenv?

I'm happy to hear any idea about this and give a PR once it is settled.


python311Packages.beartype: 0.13.1 -> 0.14.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.beartype is: Fast runtime type checking for Python
meta.homepage for python311Packages.beartype is: https://github.com/beartype/beartype
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.14.0 with grep in /nix/store/vj6cfrf5qjxab2z69lpxgzwm31a10ja5-python3.11-beartype-0.14.0
found 0.14.0 in filename of file in /nix/store/vj6cfrf5qjxab2z69lpxgzwm31a10ja5-python3.11-beartype-0.14.0

Rebuild report (if merged into master) (click to expand)

6 total rebuild path(s)

6 package rebuild(s)

First fifty rebuilds by attrpath
python310Packages.beartype
python310Packages.nptyping
python310Packages.pynrrd
python311Packages.beartype
python311Packages.nptyping
python311Packages.pynrrd

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/vj6cfrf5qjxab2z69lpxgzwm31a10ja5-python3.11-beartype-0.14.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.beartype https://github.com/r-ryantm/nixpkgs/archive/06e53523b024279ebfcdb4137d13b41262f0bc12.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/vj6cfrf5qjxab2z69lpxgzwm31a10ja5-python3.11-beartype-0.14.0
ls -la /nix/store/vj6cfrf5qjxab2z69lpxgzwm31a10ja5-python3.11-beartype-0.14.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

6 packages built:

python310Packages.beartype
python310Packages.nptyping
python310Packages.pynrrd
python311Packages.beartype
python311Packages.nptyping
python311Packages.pynrrd

Maintainer pings
cc @bcdarwin for testing.

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

12 packages built:

python310Packages.beartype
python310Packages.beartype.dist
python310Packages.nptyping
python310Packages.nptyping.dist
python310Packages.pynrrd
python310Packages.pynrrd.dist
python311Packages.beartype
python311Packages.beartype.dist
python311Packages.nptyping
python311Packages.nptyping.dist
python311Packages.pynrrd
python311Packages.pynrrd.dist


Example: Gh action comment output

Description
This PR adds fixes to the go program output and github action output, along with a demo GitHub action which analyses an example infrastructure and adds a GitHub comment to a PR with current carbon intensity for the infra's region and predicted CO2 emissions for that infra over 24 hours.
If necessary, this PR can be split into two separate ones -> one into Dev, introducing the fix and another one into a new, Demo branch. The Demo branch could show example usages of the Project and give starting points for different solutions/demos + tangible example. (might be of interest to @lydia-rc)
IMPORTANT NOTE: 3 Secrets need to be set up for the demo to work (depending on carbon rate provider [watttime/electricitymap]):

ELECTRICITY_MAP_AUTH_TOKEN -> can be left empty if using WattTime
WATT_TIME_PASS -> can be left empty if using ElectricityMap
WATT_TIME_USER-> can be left empty if using ElectricityMap

Not setting these up will result in unexpected behaviour/program crashing, see #20
Demo:

Type of change

Bug fix (Setting Go script output as GitHub Actions outputs)
New non-breaking feature (demo)

Issues
Closes #18 and works towards #19

This is awesome!


nixpkgs-review: 2.6.4 -> 2.7.0

Description of changes
Update to latest version.
Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 176820 run on x86_64-darwin 1

2 packages built:

nix-update
nixpkgs-review

Looks like makeWrapperArgs needs to be updated to match upstream?

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

2 packages built:

nix-update
nixpkgs-review

@zowoq, do you mean replacing nix with nixStable?

do you mean replacing nix with nixStable?

No, NIX_SSL_CERT_FILE and PYTHONPATH.
https://github.com/Mic92/nixpkgs-review/blob/9c6158465e14212133fd4259451c324ef9a8d079/default.nix#L41-L43

@zowoq, happy to add those, but just want to check whether they should be added, since those were also there for version 2.6.4, and the derivation in nixpkgs didn't have them.


[Add A Ride] 'From:' and 'To:' edit boxes aren't clickable after closing the 'Add A Ride' page with opened ellipses menu and returning back, and the ellipses menu doesn't appear after first tapping it

Environment: Android 10, Samsung A7.
Reproducible: always.
Build found: v1.0.384
Preconditions
The user is logged in to the 'Car' and the app is opened.
Steps to reproduce

Tap 'Add a Ride'
Tap ellipses menu
Tap 'Back
Tap 'Add a ride'
Tap ellipses menu

Actual result
'From:' and 'To:' edit boxes aren't clickable after closing the 'Add A Ride' page with opened ellipses menu and returning back, and the ellipses menu doesn't appear after first tapping it but because of that edit boxes become clickable
Expected result
'From:' and 'To:' edit boxes are clickable after closing the 'Add A Ride' page with opened ellipses menu and returning back and the ellipses menu appears after tapping it
User story #24
Labels to be added
"Bug" ("bug"), Priority ("pri:high ")
https://user-images.githubusercontent.com/91271776/139479575-3f1bd873-d0cf-4200-84ce-202860713334.mp4

the same situation


Replace Vent Logo on Readme

Be sure and add yourself to AUTHORS along with your changes.

thanks!

No Problem, glad to help!


Incorrect syntax for installing ORDS in Dockerfile

Dockerfile for building ords image (https://github.com/oracle/docker-images/blob/main/OracleRestDataServices/dockerfiles/Dockerfile) contains following command on line# 65:
java -jar $ORDS_HOME/ords.war configdir $ORDS_HOME/config && \
When building image with ords-<IP_ADDRESS>.1239.zip in current folder using
./buildContainerImage.sh -i -o '--build-arg BASE_IMAGE=localhost/oracle/jdk:17-ol8'

line 65 in Dockerfile produces following messages on standard output (It looks like ords 22.4.3 does not support the "configdir" command.):
Warning: Support for executing: java -jar ords.war has been deprecated.
Please add ords to your PATH and use the ords command instead.
Run the following command to add ords to your PATH:

echo -e 'export PATH="$PATH:/opt/oracle/ords/bin"' >> ~/.bash_profile

Start a new shell to pick up this change.
2023-02-20T07:17:46.832Z INFO        Your configuration folder /opt/oracle/ords is located in ORDS product folder.  Oracle recommends to use a different configuration folder.

ORDS: Release 22.4 Production on Mon Feb 20 07:17:46 2023

Copyright (c) 2010, 2023, Oracle.

Configuration:
  /opt/oracle/ords/

Usage:
  ords [OPTIONS] [COMMAND]

Oracle REST Data Services command line interface

Options:
        --config <folder>        Path to Oracle REST Data Services
                                 configuration folder

        --debug                  Equivalent to --verbose

    -h, --help                   Show usage information for the command

    -v, --verbose                Configure Oracle REST Data Services to run in
                                 verbose mode

        --version                Show version information

Commands:
        config                   Configure application and database connection
                                 pool settings

        extract                  Extracts Oracle REST Data Services scripts.

        install                  Configure database connection and
                                 install/upgrade Oracle REST Data Services
                                 schema, ORDS database user and related
                                 database objects.

        migrate                  Migrates Oracle REST Data Services
                                 configuration files and parameter file from
                                 release 21.4.x and earlier releases.

        serve                    Launch Oracle REST Data Services in standalone
                                 mode

        uninstall                Uninstall Oracle REST Data Services schema,
                                 ORDS database user and related database
                                 objects.

        war                      Create a web application from the the
                                 distributed ords.war that can be deployed in a
                                 supported servlet container.

Run ords <COMMAND> --help for more information on a command.

For example run: ords config --help

While waiting on the Dockerfile & scripts to be updated for ORDS 22.1.0+, can the README.md be updated ( perhaps in the Known Issues section ) that the scripts in the repo are only valid for ORDS 21.4.3 and earlier?


Improvement: disambiguate the tree command from its display?

I am using manifestoo as a Python library rather than as a command line tool.
That might be a non-common use case, but I find manifestoo way easier to use that its predecessor, acsoo in that particular case, because the usage of classes makes a clear disambiguation between the display, the usage of it as a command line tool and the business logic. So one can import those classes and use them in their own Python script.
One command that is still missing a bit this simplification is the tree command which does not have a clear distinction between its business process and its display, as the last line of it prints the tree.
Wouldn't it be a good idea to have a build_tree function containing all the logic and along with a tree_command function?
This way, one could either print the tree, as it is now but could also fetch the tree and traverse it for its own purpose.
Something like:
def build_tree(
    addons_selection: AddonsSelection,
    addons_set: AddonsSet,
    odoo_series: OdooSeries,
    fold_core_addons: bool,
) -> List[Node]:
    nodes: Dict[NodeKey, Node] = {}

    def add(addon_name: str) -> Node:
        key = Node.key(addon_name)
        if key in nodes:
            return nodes[key]
        addon = addons_set.get(addon_name)
        node = Node(addon_name, addon)
        nodes[key] = node
        if not addon:
            # not found
            return node
        for depend in addon.manifest.depends:
            if depend == "base":
                continue
            node.children.append(add(depend))
        return node

    root_nodes: List[Node] = []
    for addon_name in sorted(addons_selection):
        if addon_name == "base":
            continue
        root_nodes.append(add(addon_name))

    return root_nodes

def tree_command(
    addons_selection: AddonsSelection,
    addons_set: AddonsSet,
    odoo_series: OdooSeries,
    fold_core_addons: bool,
) -> None:
    root_nodes = build_tree(addons_selection, addons_set, odoo_series, fold_core_addons)
    for root_node in root_nodes:
        root_node.print(odoo_series, fold_core_addons)

Hi, thanks for the feedback.
I'm fine with the proposed refactoring. PR welcome.
However, if you use it as an API, do keep in mind this page of the documentation. TL;DR: there is no public documented nor stable API :)
If you want stability guarantees, we need to work on
1/ feedback and fine tuning of the public API to real use cases
2/ refactoring to expose the public API explicitly (e.g. in manifestoo.__init__.py)
3/ making sure we have complete test coverage of the API entry points
4/ generating API documentation with sphinx
Help is most welcome in this area.

Thanks Stéphane, this was duly noted, I pinned the version I am using at a really specific version, because I red the linked page already.
I am still a recent comer in the Python/Odoo world, so I don't feel like I am up to the task just yet. I am planning to start with simpler ones to start with, though.


fix recording tests, regenerate data

@jscotka How did  you do this? :smiley: It would be great if you could provide some explanation and share the knowledge :)

@jscotka How did you do this? smiley It would be great if you could provide some explanation and share the knowledge :)

It was very easy :-) just steps what I've suggested to @lachmanfrantisek, but Franta failed to regenerate it. I have fear that it was caused by some venv/pycharm tooling versions. for him.
Finally I've just do  some
git rm -rf tests_recording/test_data/*
pytest -v -x tests_recording
requre-purge ...

git add tests_recording/test_data/*

very simple, nothing special :-)
But I'm now focusing to rewrite it to new decorators in requre. so have to wait untill it will land in master
https://github.com/packit/requre/pull/188
It fixes several potantial issues what were there.

continues in: https://github.com/packit/packit/pull/1235

but Franta failed to regenerate it. I have fear that it was caused by some venv/pycharm tooling versions. for him.

To be correct, I can generate the files but the script for symlinking the same archives did not work for me.

I"ll close this PR and it continues in #1235


Completed the past events front-end

These are the screenshots

These are the screenshots of the new Past events page


Release a deprecated library for our last release

Publishing a new library that deprecates topologic in favor of graspologic and endeavours to redirect any new users toward the actually living topologicpy by https://topologic.app

Output:
(venv) dax@valinhall:~/dev/topologic$ python
Python 3.8.14 (default, Sep  8 2022, 00:02:07)
[GCC 11.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import topologic as tc
/home/dax/dev/topologic/topologic/__init__.py:25: UserWarning: The python library `topologic` has been deprecated in favor of `graspologic` in PyPI. Please update your consuming code.  Perhaps you meant the library `topologicpy` https://pypi.org/project/topologicpy/ ?
  warnings.warn("The python library `topologic` has been deprecated in favor of `graspologic` in PyPI. Please update your consuming code.  Perhaps you meant the library `topologicpy` https://pypi.org/project/topologicpy/ ?", UserWarning)
>>> exit()


Bug: Filtering by repos on the workspace activity page no longer works

When the feature for the pull requests table got merged, a table available from the workspace activity page, you were able to filter by one or more repositories. This no longer seems to be the case.
I came across this after I had created a Netlify workspace, https://app.opensauced.pizza/workspaces/8b856470-d615-45f0-b001-ebedaae29bed.

I've tested this in prod with the provided link and beta and the issue seems to be resolved.


sap.ui.commons.DropdownBox in table

OpenUI5 version:
latest
Browser/version (+device/version):
all affected
Any other tested browsers/devices(OK/FAIL):
URL (minimal example if possible):
https://plnkr.co/edit/6u5RBfsKxZNjsVsYEQvg
User/password (if required and possible - do not post any confidential information here):
Steps to reproduce the problem:
1.run the app
2.scroll down
3. the value of the dropdown in first row got changed
What is the expected result?
no change
What happens instead?
Any other information? (attach screenshot if possible)
two issue:
1.
I have a dropdown in first column of a table.
for the first table row, the selected key is not in the dropdown list
for the second table row, the selected key is in the dropdown list
if scroll, the selected key of dropdown in first row got changed.
2.
if selected key not in the dropdown list, no option should be selected in the dropdown, actually it select the first one(at least it appears).

Hi Jun,
the dropdownbox is deprecated. With a sap.m.Select it looks better.
Main points are:
compact mode so the select is small
<body class="sapUiBody sapUiSizeCompact"
width 100% for select so nothing flickers
 new sap.m.Select("DropdownBox1",{selectedKey:"{Customer}", width: "100%"});
sap.m Library in your bootstrap
" data-sap-ui-libs="sap.ui.table, sap.ui.commons, sap.m"
Hope this helps.
best regards,
Tobias

@TobiasOetzel
using m lib whenever possible? can I conclude that?

Yes this is the conclusion.


Testing on full study test case

Full test on a full study - ideally large Ph3
@reesnj @alanaharris22 for proposed study/location

Hi @barnett11,
I checked with Mike, we can use the NP30179 study.
Although since it's currently going througha filing, he asked if we could possibly use an older snapshot of SDTMv (~Nov 2021).
eICE Location - root/clinical_studies/RO7082859/CDT70029/NP30179
Thanks,
Alana

That should be perfect thanks, will setup

Full test completed - https://code.roche.com/barnett1/datacutr_testing/-/tree/devel


Appstudio update test-component-pac-daya

Pipelines as Code configuration proposal

Pipelines as Code CI/test-component-pac-daya-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
7 seconds
init

✅ Succeeded
17 seconds
clone-repository

✅ Succeeded
31 seconds
build-container

✅ Succeeded
13 seconds
deprecated-base-image-check

✅ Succeeded
14 seconds
inspect-image

✅ Succeeded
9 seconds
clair-scan

✅ Succeeded
35 seconds
clamav-scan

✅ Succeeded
8 seconds
sbom-json-check

✅ Succeeded
18 seconds
label-check

✅ Succeeded
18 seconds
optional-label-check

✅ Succeeded
5 seconds
show-sbom

✅ Succeeded
6 seconds
show-summary

Pipelines as Code CI/test-component-pac-daya-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
7 seconds
init

✅ Succeeded
17 seconds
clone-repository

✅ Succeeded
31 seconds
build-container

✅ Succeeded
14 seconds
inspect-image

✅ Succeeded
13 seconds
deprecated-base-image-check

✅ Succeeded
9 seconds
clair-scan

✅ Succeeded
35 seconds
clamav-scan

✅ Succeeded
8 seconds
sbom-json-check

✅ Succeeded
18 seconds
label-check

✅ Succeeded
18 seconds
optional-label-check

✅ Succeeded
5 seconds
show-sbom

✅ Succeeded
6 seconds
show-summary


Daily Test failed on 02/12/2024 09:04

https://github.com/voedger/voedger/actions/runs/12115909801

temporary fixed by excluding edger/ dir from tests


Update: Contributors in package.json

While I think the author on a package's page in npmjs.org is determined by the user doing the initial publication, I wonder if we should update at least the contributors field in package.json.

Please go ahead and make the necessary changes.
On Sun, Apr 10, 2016, 11:41 PM Andreas Windt<EMAIL_ADDRESS>wrote:

While I think the author on a package's page in npmjs.org is determined
by the user doing the initial publication, I wonder if we should update at
least the contributors field in package.json.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/sarbbottam/eslint-rule-finder/issues/12

Will do.


Corrects vendor colors for Evernote & GitLab

The Evernote icon didn't look quite right with a white background, so I took an eyedropper tool to the Evernote.com site and grabbed the elephant icon's exact hex color. Changed the fill color in the SVG to match that.
Similar story with GitLab, but since the original logo is so multicolored, I opted for the main color their site uses for emphasis. It visually looks close enough to the original logo and it better mimics their branding, which is the whole point here, right?
Final change is to correct an issue with the Meetup reference logo. Looks like someone decided to rename a PNG and thought that would convert it to a JPG file, then upload it to the Akamai CDN. Running file images/reference/meetup.jpeg from the terminal indicated it was a PNG originally, so I made the change to the file extension and the index.md file where it was referenced.

Nifty!


Fatal Error. Uncaught error: Class 'CI_Controller' not found

So this is a kinda old project running CI3 and we're facing this issue. It's very sporadic, it seems like it happens when requesting Ajax routes and the temporary fix testers have found is to "Clear the browser's cache".
From what I can see, people that faced this exact error and reported on StackOverflow have so many different causes too far and between, so I couldn't pinpoint the exact issue.
Of course we don't touch core files, just extend from them in our own controllers, and the fact that it happens at random doesn't help to the issue.
This is a screenshot of what we see in one of the Ajax responses:

This stack trace points to this file called MY_Exceptions.php which has this code, reading another issue report here I kinda thought it was because at this point in the lifecycle CI_Controller wasn't loaded, but this is an Ajax call though, wouldn't the Core components be up even before my code is executed at that point?:

Again, let me emphasize that this doesn't happen all the time with all the existing Ajax requests, nor consistently through all the user machines and browsers, it just happens, a browse cache clear and it's working as intended again.
Can you people help me try to find the cause of this issue? thanks in advance

The error causing this must be happening early in your application, before CI_Controller has been included. Due to the way in which PHP works, the get_instance function will be available, but the controller class may not have been loaded yet.
If you remove the code that is calling get_instance, at least you will be able to ascertain what the actual cause of the error is. You cannot rely on CI_Controller being available here - you could check for it.

The error causing this must be happening early in your application, before CI_Controller has been included. Due to the way in which PHP works, the get_instance function will be available, but the controller class may not have been required/included yet. If you remove the code that is calling get_instance, at least you will be able to ascertain what the actual cause of the error is. You cannot rely on CI_Controller being available here - you could check for it.
This isn't a bug in CI as far as I can see, so should probably be a Stack Overflow / forum question.

You and I know, this will never be answered on stack overflow, actually I came here after radio silence in there.
I tried something, which was removing the file MY_Exception, thinking it wasn't being really used/referenced anywhere and it was just being loaded as a result of a line batch loading the files of a folder in codeigniter, also, that it seemed to be made by one of the previous developers of this project.
Turns out it's absolutely needed, any Exception thrown in the project goes through this file, so everything was breaking in it's absence.
Now, that got me thinking, this CI error is happening on the development environment after any exception is thrown out? maybe? that would've been worrysome because that would compromise the entire try - catch structure we have in the code, fortunatelly it wasn't the case, I forced a condition to throw an Exception and it worked just fine.
But that puts us to the beginning, the only thing we know is that this is a random thing we can't catch just yet, I'll even say more, our tester said last week he got the CI error in another random place, but a couple hours later when I told him to check something for me, he went to test it again and it wasn't happening anymore, he didn't even need to clear cache.
This is a really weird bug tbh

You might have better luck on the CodeIgniter forum if SO isn't helping.
The "MY_" classes are override classes (by default) in CI. They will be loaded instead of "CI_"
In still believe your exception is happening before the CI_Controller class is included/required in line 308 above.

You might have better luck on the CodeIgniter forum if SO isn't helping.
The "MY_" classes are override classes (by default) in CI. They will be loaded instead of the "CI_" classes.
I still believe your exception is happening before the CI_Controller class is included/required in line 308 above.
For debug purposes:

remove the code that is calling get_instance, at least you will be able to ascertain what the actual cause of the error is.

But If I remove that line that means I would need to also remove the line that's refreching the csrf token, wouldn't that just make the code unable to keep the token up to date?

I literally mean remove that line and print out the exception that you have rather than trying to do something with CI_Controller which isn't available to you at the point your app throws it.


vscode auto create .vscode folder when I open any project

VSCode Version:1.13.1
OS Version:windows7

Steps to Reproduce:
1.how can I forbid this function?
2.

Reproduces without extensions: Yes/No

I also have the same thing, but only for some of my project folders. Not sure what is causing it to only happen for certain projects but not others..

I wonder if this issue is being caused by an installed extension. Can you try to run VS Code without extensions? From the command line (NOT the integrated terminal in Code), execute: code --disable-extensions and try your steps again to see if it reproduces. If you see it is an issue with the extension, please file it against the extension repository itself.

The donjayamanne.python extension makes this happen. When I uninstall the extension, the .vscode will not be created.

Reading your description it seems that the issue originates from an extension and not VS Code itself. Thereby I will close this issue and kindly ask you to report this issue against the extension repository.
Most extensions are on GitHub as well so it should be easy to file it against the extension. If you open an extension on the market place, click on the Support link to find out more.

Thanks again for your feedback!


Dataset and training codes release

It's a great work for the few-shot medical image segmentation problem! And I'd like to know whether the prepocessed dataset (or tasks) and the training codes will be released in the near future.

Due to data user agreements, we cannot re-release other people datasets without their consent. Moreover, many of the datasets require that the user agrees to specific conditions first. Nevertheless, you can find the datasets we used in MegaMedical in Table3 of Appendix A.
Our training code is fairly standard and should be easy to reproduce, we will study releasing it. Appendix B includes additional implementation details to help with this.

I'll just add that there are some datasets you can download and try.
See https://github.com/adalca/medical-datasets/blob/master/neurite-oasis.md for example for brains --- which includes a mid-slice selection. You'll need to do some minimal processing (resize to 128x128 and extract a label of interest) but it should be fairly quick to do!

Update: @CSCYQJ we have now added an example of downloading and using neurite-oasis in the tutorial (at the bottom, current section 8). See https://universeg.csail.mit.edu.


Handle db, database_grant and table_grant from class postgresql::server

Greetings.
In this submission I add the ability to declare databases and grants from postgresql::server (roles, config entries and pg_hba were already handled).
So we may only include postgresql::server, then with hiera we can control major tasks of the module without calling any defined resources.

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

HI @molivier-fcms, thank you for your contribution. Please sign the CLA in order to get this PR merged.
kind regards,
@adrianiurca

Hi,
I have signed the CLA. However one test failed, but I'm not sure the changes are responsible.
Regards,
Matthieu

Thanks @molivier-fcms for your contribution. Could you please add unit tests to verify the changes. Thank you.

Hi,
I have signed the CLA. However one test failed, but I'm not sure the changes are responsible.
Regards,
Matthieu

No worries. We have a ticket opened separately for the  failures on centos 8 platform. It's not related to the changes from this PR. Thank you.

@molivier-fcms Your work here looks good, and the underlying issue regarding CentOS-8 has been resolved. Once you add some unit test coverage for your change we will be more than happy to merge.

Hi @sheenaajay , @david22swan ,
Do you have some documentations about these unit tests? I don't know where they are expected to be nor how the should work.
Thank you,
Matthieu

@molivier-fcms Apologies but there isn't much documentation on this that I know of sorry, the best that I could give you would be a ink to this blog post which deals with how to write them:
https://puppet.com/blog/unit-testing-rspec-puppet-for-beginners/
Unfortunately the unit testing in this module is somewhat unique and so the documentation that does exist might not be as much use. The best way forward, and the route that I usually follow in times like this, is to go through the existing unit tests, find the file that corresponds to the area that has been added to and then use it as a base for the changes that I need to make.
Taking a look into the module this file looks to be where to start:
https://github.com/puppetlabs/puppetlabs-postgresql/blob/main/spec/unit/classes/server_spec.rb
With this line running test's that cover a similar function to the one you've change, i.e. $roles.each |$rolename, $role| {:
https://github.com/puppetlabs/puppetlabs-postgresql/blob/main/spec/unit/classes/server_spec.rb#L234-L245
I'm sorry that I'm not being more help on this, if you are till having trouble with this then I encourage you to reach out on the Puppet Community slack, the team holds an open answer session every week on Monday and there are usually community members willing to help give you advice.


Always use the latest version of the azure package. (If we only use v…

…ersion 1.0.0 we won't be able to pickup fixes and some times substantial perf improvements of the azure python package, e.g., the v1.0.2 has a 10x improvement in 1 byte request latency due to connection reuse)

@cmccoy @yuyantingzero @voellm
This is a one-liner but has significant impact in latency numbers measured on Azure.
The summary of the issue is:

PKB (with versions <=0.21.0) used to always grab the latest version of Azure python package.
Due to a breaking change of Azure when they released 1.0 in early September, our PKB code was broken (namespace was changed).
As part of fixing 2, we decided to just always install azure = v1.0.0 because we know it works.
Sure, it works, but after v1.0.0, Azure folks made an important fix in their client side that would reuse HTTP connection across multiple requests, and that fix is available in v1.0.1 and later, and that fix has significant performance benefit.

Here is the CL in Azure python client that made the improvement in their v1.0.1
https://github.com/Azure/azure-storage-python/commit/20d6c240e3ced45f48eb8b5900c8783c4e1f8dc6
So, the situation on the PKB side is now:

If you have an old PKB binary (<=v.0.21), that PKB will actually always download the LATEST version of Azure and therefore get GOOD latency numbers. (that's why we have been seeing good numbers in Azure in mid-to-late September!!)

However, if you have the latest PKB binary (>=v.0.22) which was shipped in early Oct, that PKB will always download Azure client v1.0.0 which does not have the aforementioned perf fix Azure folks made in their client package.

Therefore, I believe we should always download the latest Azure client package from this point on so we always pickup their latest and greatest fix!
Here is the difference between Azure client v1.0.0 and v1.0.2:
v1.0.0, one byte upload/download latency:
Upload p50: 0.0673, Download p50: 0.0327
v1.0.2, one byte upload/download latency:
Upload p50: 0.005462, Download p50: 0.006987
10x difference!, and if you take a closer look at v1.0.2 logs, you will see message for the initial connnection establishment, and the time to do the first request is about the same as the old binary, but subsequent requests will use the same connection and take much less time:
INFO:root:Storage provider is AZURE, bucket is pkbb4be8938, scenario is OneByteR
W
INFO:urllib3.connectionpool:Starting new HTTPS connection (1): pkbb4be8938.blob.
core.windows.net
INFO:root:Individual results of one byte upload:
INFO:root:0.051287
INFO:root:0.005961
INFO:root:0.005789
INFO:root:0.005494

@cmccoy - I believe this is a p0 must have for the next release (which starts early next week)...

lgtm


PANIC: Missing emulator engine program for 'x86' CPU on Mac

Ionic version:  (check one with "x")
[ ] 2.x
[ X ] 3.x
[ ] 4.x
I'm submitting a ...  (check one with "x")
[ X ] bug report
[ ] feature request

Current behavior:
When I try ionic cordova run android and then I see this "PANIC: Missing emulator engine program for 'x86' CPU."
Expected behavior:
This will launch a real device or virtual device to run the app.
Steps to reproduce:

I have removed entire Android Studio and all files and folder on MacOs and then I have installed the last version of Android Studio and after that I have created a test application on Android Studio to test it and finally The app runs correctly with virtual device. Later I have created an App with Ionic and I have tried to test it, but I get this error "PANIC: Missing emulator engine program for 'x86' CPU."
Other information:

Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
cli packages: (/usr/local/lib/node_modules)

    @ionic/cli-plugin-proxy : 1.5.8
    @ionic/cli-utils        : 1.19.2
    ionic (Ionic CLI)       : 3.20.0

global packages:

    cordova (Cordova CLI) : 8.0.0

local packages:

    @ionic/app-scripts : 3.1.8
    Cordova Platforms  : android 7.0.0
    Ionic Framework    : ionic-angular 3.9.2

System:

    Android SDK Tools : 26.1.1
    ios-deploy        : 1.9.2
    Node              : v6.11.3
    npm               : 3.10.10
    OS                : macOS High Sierra
    Xcode             : Xcode 9.2 Build version 9C40b

Environment Variables:

    ANDROID_HOME     : /Users/wilfredonoyola/Library/Android/sdk/
    HTTP_PROXY       : not set
    http_proxy       : not set
    HTTPS_PROXY      : not set
    https_proxy      : not set
    IONIC_HTTP_PROXY : not set
    PROXY            : not set
    proxy            : not set

Misc:

    backend : pro

I encountered the same problem, I refer to  this method to solve the problem

Note sure if you've fixed your problem but check which system image your android virtual device is using (you can check on android studio under the 'API' column in the AVD list). Make sure you're not using anything too new, I tried using 28 and 27 and neither worked but 26 (Android Oreo 8.0) did. Cheers!

Had the same problem, solved it with these lines added to .bash_profile:
export ANDROID_SDK_ROOT=/Users//Library/Android/sdk
export PATH=$ANDROID_SDK_ROOT/emulator:$ANDROID_SDK_ROOT/tools:$PATH

@ElLocoNutz , it is not working for me, Ran both commands, still the same output.

Ok my wrong, apparently I used the wrong expression when I wrote the path, it should look like this:
export ANDROID_SDK_ROOT=/Users/**[username]**/Library/Android/sdk
export PATH=$ANDROID_SDK_ROOT/emulator:$ANDROID_SDK_ROOT/tools:$PATH

But don't just run those commands or the change won't stay. You should add those lines to your ~/.bashrc or ~/.bash_profile and after that you need to reload the bash, restart the console or source the edited file, e.g.
"me@localhost:~$ source .bashrc"
But keep in mind those are the folders that worked for me, your system might be using different ones, check the folder before you change anything, you should find there the emulator.


Refactor Action Contents

Currently, the delta specified in an Action is a Vec<String>.  I think it makes more sense to be a Vec<&str>.

Ditto for Marker.filename


Update python Azure Batch AI example doc

Corrected some typos.
Also, I think the azure_file_share_name needs to be included in the path when mounting.

@dlepow - could you please address this feedback?  Thanks!

@benalexkeen - Ben, Thanks very much for taking the time to contribute. Apologies it has taken us a while to respond. We fixed up the typos you pointed out in the article the meantime, and according to our product experts the azure_file_share_name should not be included in the path when mounting. Accordingly, I will close this PR. Please feel free to contribute again.
#please-close


Footer Contents Misaligned and Congested

The contents in the footer section of the repository are currently misaligned and congested, resulting in a bad UX. The lack of proper spacing makes it difficult to distinguish between different elements in the footer.

please assign me this issue.

@rishika-g31 done

please merge this pull request under hactoberfest, or tell me if their is some other requirements or changes to be done.


Update Composer dependencies (2021-11-16-00-04)

Visual regression test passed!
View the visual regression test report


NAT Assignment clears when editing IP address.

Issue type: Bug Report

Python version: 3.5
NetBox version: 2.0.7

When editing an existing IP address that has a NAT assignment, the NAT assignment clears when saving whatever changes are made.
For instance I edited an IP address to change the description, saved my changes and the NAT assignment was gone after saving the description changes.
So everytime I edit an IP address I have to add the NAT assignment back.

I'm not able to replicate this behavior. Could you please provide the list of steps needed to recreate the bug, beginning with creating a new IP?

Closing due to lack of activity.

I'm suggest we reopen this.  It happens for me too!
Python 2.7.9
v2.0.8-dev
When I view an IP with a NAT Address assigned it's there:

But when I click "Edit" on the IP address, the NAT details don't load, and thus when I click "Update" the NAT Assignment is lost.

Step By Step
1AddFirstIP.png
2AddSecondIP.png
3ViewSecondIP.png
4EditSecondIP.png
5NATMissingSecondIP.png

Thanks, will have a look.

To provide additional context: This occurs only when the inside NAT IP address is not assigned to a device/interface. The problem is that the chained select widgets in the form are not allowing the initialization of the assigned NAT IP.


Toward application-specific reduction such as TurboPlonk and Halo2

Summary
We may need to get some clarity in how to enable arkworks-rs to support a large class of Plonk implementation and their variants.
Problem Definition
Implementing a specific version of Plonk, or providing a standard implementation like zk-Garage efforts (https://github.com/ZK-Garage/plonk), does not actually appeal to me very much.
I see a trend that different applications and systems will design different Plonk. For example, Rescue can be very efficient if the powering is made into a customized gate type. For example, twisted Edwards curve operations can be made efficient as well.
Customized gates are basically using FFT to exchange for fewer MSM. It also has a lot to do with sparsity when Lagrange bases are used.
The current use of TurboPlonk already goes beyond the notion of "gates". For example, one can add binary checking over existing wires of a gate, by playing with the polynomials. Halo2 can also do this as well.
This leads to a question:

What would be a (Turbo)Plonk interface that would be suitable for a large number of Plonk variants?

Proposal
This would just be the beginning and followup of #155 discussion.
First, we probably should start with finding a way to have Halo2 in arkworks-rs, as it has a very comprehensive implementation of PLONKish, and our work would be mostly filling in gadgets, i.e., instead of "r1cs-std" we would have "plonkish-std".
This is likely going to be a separate implementation, since Halo2 does not need to, and probably should not, be built over arkworks-rs since it already has its own foundation. So, a question is: how stable or finalized Halo2 is? (@daira)
Second, Jordi Baylina (@jbaylina) has been working on polynomial identity language (PIL) which seems to be closer to the different Plonk variants that are not plonkish, which is here: https://github.com/0xpolygonhermez/pilcom
This is a step that arkworks-rs needs to go sooner or later.

For Admin Use

[x] Not duplicate issue
[x] Appropriate labels applied
[x] Appropriate contributors tagged
[x] Contributor assigned/self-assigned

We're currently migrating https://github.com/ZK-Garage/plonk into a halo2-like system with Plonkish arithmetization.
It still uses arkworks as base and should allow to write almost anything you would like without the learning curve that halo2 has.
We did some initial documents on the API shape. See: https://hackmd.io/3v8dBSfuQiGlGLAx2RQe9w?view
The actual implementation is being done in another repo. But we want to start migrating it now under ZKGarage since it's already decently started.
I'm not suggesting that you change your direction nor anything similar. Just wanted to inform that this effort is happening in case you might want to check it and take stuff from it or collaborate or whatever :smile:


[BUG] SOFTWARE UPDATE MANAGER 2.0 SP14 Patch 6 is no longer available

Describe the bug
Please update the BOM catalog for SUM20SP14_latest. SOFTWARE UPDATE MANAGER 2.0 SP14 Patch 6 is no longer available. SAP replaced it by Patch 7.
To reproduce
Steps to reproduce the behavior:

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

Expected behavior
A clear and concise description of what you expected to happen.
Additional context
Add any other context about the problem here.

@yertaylan67 you have to adjust the BOM manually with the versions SAP changes to often. Provide the new file details (name, URL, hash, etc.) commit the change and rerun the pipeline.

Please find here the updated code block for file deploy/ansible/BOM-catalog/SUM20SP14_latest/SUM20SP14_latest.yaml:
---
name:    'SUM20SP14'
target:  'SUM20SP14'
version: 007

materials:

  media:
   # SUM
    - name:         "Patch 7 for SOFTWARE UPDATE MANAGER 2.0 SP14"
      archive:      SUM20SP14_7-80002456.SAR
      checksum:     b207e0c1b832e50603a46b6e678d1f2eea63750acee49d7cdc9403f29257278c
      download:     false
      url:          https://softwaredownloads.sap.com/file/0020000001246852022

    - name:         "Patch 7 for SOFTWARE UPDATE MANAGER 2.0 SP14 (Windows)"
      archive:      SUM20SP14_7-80002458.SAR
      checksum:     73c72687e291992f4f0b605c6ee6111e4d0d667d50c310fb6816aaadff700612
      download:     false
      url:          https://softwaredownloads.sap.com/file/0020000001246872022

@yertaylan67 This resolved in the repo, closing


Deleted package detected

I'm a Cyber Security researcher and developer of PackjGuard [1] to address open-source software supply chain attacks.
Issue
During my research, I detected a deleted package in this repository.
Details
Specifically, the package osuny mentioned in file README at line 10 does not exist on the public RubyGems registry. A bad actor can hijack this package to propagate malicious code.
Impact
Not only your apps/services using https://www.github.com/noesya/osuny-api repo code are vulnerable to this attack, but the users of your open-source Github repo could also fall victim.
You could read more about such attacks here<EMAIL_ADDRESS>Remediation
Please highlight this in file README and register a placeholder package for osuny on public RubyGems soon to remediate.
To automatically fix such issues in future, please install PackjGuard Github app [1].
Thanks!

PackjGuard is a Github app that monitors your repos 24x7, detects vulnerable/malicious/risky open-source dependencies, and creates pull requests for auto remediation: https://github.com/marketplace/packjguard

Sorry about this false positive.


Update browser support list

Removes browsers we no longer want to support for v2 from the site.

Good point, yes don't merge this.
@mourner the doc changes of #8196 already published too

Do we want to mention Brave? Do we want to group Chrome & Edge under "blink engine browsers" or something like that?

Yea, I was also not quite sure how to formulate this, naturally supporting Chromium-based browsers such as Brave and Samsung Internet would be fine considering they're all based on the same platform.


Reduce the verbocity of function calls

Currently instantiating a Dataset is done using a call to iati.core.data.Dataset. This type of thing seems too verbose, and in this example I would suggest that the same could be achieved by iati.core.Dataset.
This could be achieved by importing Dataset in to the iati/core/__init__.py file, as exemplified by the Requests library.
I would suggest that the following functions have easier calls:
iati.core.codelists.Code -> iati.core.Code
iati.core.codelists.Codelist -> iati.core.Codelist
iati.core.data.Dataset -> iati.core.Dataset
iati.core.rulesets.Rule -> iati.core.Rule
iati.core.rulesets.Ruleset  -> iati.core.Ruleset
iati.core.schema.Schema -> iati.core.Schema

This is now merged into dev, so will be can be closed when dev is next merged to the master branch.

Since it's in dev, will close this


The docc-plugin preview-documentation sometimes fails to preview content with snippets

The docc-plugin preview-documentation command appears to be failing to generate a module index page when snippets are added to the project.
This is with Swift 6.0.2 and swift-docc-plugin 1.4.3 (Xcode 16.1 release).
When I run the command to preview my documentation:
swift package --disable-sandbox preview-documentation --target Voxels

I see the (mostly) normal output:
Building for debugging...
[1/1] Write swift-version--58304C5D6DBC2206.txt
Build of product 'snippet-extract' complete! (0.18s)
Building for debugging...
[1/1] Write swift-version--58304C5D6DBC2206.txt
Build of target: 'Voxels' complete! (0.15s)
Input: /Users/heckj/src/Voxels/Sources/Voxels/Documentation.docc
Template: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/share/docc/render
========================================
Starting Local Preview Server
	 Address: http://localhost:8080/
========================================
Monitoring /Users/heckj/src/Voxels/Sources/Voxels/Documentation.docc for changes...

A difference from what I expected is that there's no documentation/voxels on the URL presented, which happens on other projects.
When I opened a browser, going to http://localhost:8080/documentation/voxels, the JS browser error reports a missing file voxels.json.
Looking at the .build directory, I see .build/plugins/Swift-DocC Preview/outputs/Voxels.doccarchive/data/documentation, the directory of which voxels within it and a collection of all the symbols in JSON format. However, there isn't a voxels.json file in that directory.
Checklist

[x] If possible, I've reproduced the issue using the main branch of this package.
[X] This issue hasn't been addressed in an existing GitHub issue.

Expected behavior
Describe what you expected to happen.
Actual behavior
Describe or copy/paste the behavior you observe.
Steps to Reproduce
git clone https://github.com/heckj/voxels
cd voxels
git checkout 7c70985
swift package --disable-sandbox preview-documentation --target Voxels

(URL for the above shows http://localhost:8080/documentation/voxels and resolves correctly)
git checkout 6089364
swift package --disable-sandbox preview-documentation --target Voxels

(URL for the next commit shows http://localhost:8080/ and fails to resolve)
The only difference between these two commits is adding the file Snippets/example-snippet.swift to the project.
Swift-DocC Plugin Version Information
Swift-DocC plugin version: 1.4.2 for example, or a commit hash.
Swift Compiler version: Output from swiftc --version:
swift-driver version: 1.115 Apple Swift version 6.0.2 (swiftlang-<IP_ADDRESS>.2 clang-16<IP_ADDRESS>)
Target: arm64-apple-macosx15.0

I just thought to try swift-markdown, but it doesn't exhibit the same behavior. When running swift package --disable-sandbox preview-documentation --target Markdown on that project, the address shown is http://localhost:8080/documentation/markdown and the documentation renders as expected. That said, I'm not sure what the meaningful difference is between the two projects in terms of how it generates the results.

I switched back and forth between 1.4.3 and main, with the same results in both cases, so the underlying issue may be in DocC, not in the plugin.
Working when there's a @Snippet reference:
git commit with snippet curated into catalog
git checkout c7dcaf514abc318c1ab7aded31b3a4b4ebb35023
swift package update
rm -rf .build # clean the build
swift package --disable-sandbox preview-documentation --target Voxels

-->
========================================
Starting Local Preview Server
	 Address: http://localhost:8080/documentation/voxels
========================================

Prior commit with only the snippet
git checkout 6089364a89cfa1360c26a85d6ad005994274833e
rm -rf .build # clean the build
swift package --disable-sandbox preview-documentation --target Voxels

-->
========================================
Starting Local Preview Server
	 Address: http://localhost:8080/
========================================

5 iterations of this same command:

no content
content rendered
no content
content rendered
no content

And a variation I didn't expect
I moved back forward to verify - the commit that previously worked - and used this same sequence of commands, and the contents didn't resolve
git checkout c7dcaf514abc318c1ab7aded31b3a4b4ebb35023
swift package update
rm -rf .build # clean the build
swift package --disable-sandbox preview-documentation --target Voxels

-->
========================================
Starting Local Preview Server
	 Address: http://localhost:8080/
========================================

Running the following steps repeatedly (5 iterations)
git checkout c7dcaf514abc318c1ab7aded31b3a4b4ebb35023
rm -rf .build # clean the build
swift package update
swift package --disable-sandbox preview-documentation --target Voxels

no content
no content
content rendered
content rendered
content rendered

Since this seems to be more of a race-condition issue, I jumped back to a commit before I added snippets to see if that's a factor:
git checkout 0.2.4
rm -rf .build # clean the build
swift package --disable-sandbox preview-documentation --target Voxels

5 iterations:

content rendered
content rendered
content rendered
content rendered
content rendered

From this, I'm hypothesizing that there's a race condition in there somewhere, acerbated by Snippets existing that doesn't otherwise normally show up.

Double checking with main branch of swift-docc-preview on commit with both snippet and content curated into the catalog:
rm -rf .build
swift package --disable-sandbox preview-documentation --target Voxels

content rendered
content missing
content missing
content rendered
content missing

Repeating just the preview command (without clearing the build):

after a content missing build:

content missing
content rendered
content missing
content rendered
content rendered

Based on this, the build portion of this doesn't appear to make a difference.

I broke this down and started down the path of debugging the plugin, only to realize the issue is upstream in docc. The raw command being invoked:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/docc preview /Users/heckj/src/Voxels/Sources/Voxels/Documentation.docc --emit-lmdb-index --fallback-display-name Voxels --fallback-bundle-identifier Voxels --additional-symbol-graph-dir /Users/heckj/src/Voxels/.build/plugins/Swift-DocC\ Preview/outputs/.build/symbol-graphs/unified-symbol-graphs/Voxels-7 --output-path /Users/heckj/src/Voxels/.build/plugins/Swift-DocC\ Preview/outputs/Voxels.doccarchive
Is what appears to have the race condition.
In repeated tests of just this command:

no content
no content
content rendered
no content
no content

So the issue appears to be in the underlying docc preview command.

detail migrated to https://github.com/swiftlang/swift-docc/issues/1084 and closing this, since it's not docc-plugin specific.


[PKG-4871] 0.3.2

hmmlearn 0.3.2 :snowflake:
Destination channel: Snowflake
Links

PKG-4871
Upstream repository
Upstream changelog/diff

Explanation of changes:

Forced openblas on osx-64 to prevent a segfault error.
Added upstream tests.

The tests require the package to be built in place and editable, so it's currently being rebuilt in the test block. Please let me know if there's a better way to go about that.

Added $RPATH/ld64.so.1 to missing_dso_whitelist for s390x

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_b8iflxnl06/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:61: missing_description: The recipe is missing a description
clone/recipe/meta.yaml:28: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.

===== ERRORS =====

clone/recipe/meta.yaml:28: missing_wheel: For pypi packages, wheel should be present in the host section
===== Final Report: =====
1 Error and 2 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_04w0vgazwm/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:28: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
===== Final Report: =====
0 Errors and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_cffhv4rr3j/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:30: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
===== Final Report: =====
0 Errors and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_2d3roj_dif/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:30: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
===== Final Report: =====
0 Errors and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_47fy0mrt8y/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:30: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
===== Final Report: =====
0 Errors and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_e7wyvczymq/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:30: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
===== Final Report: =====
0 Errors and 1 Warning were found

The tests on osx-64 are triggering a segfault any time _AbstractHMM.fit is called. I suspect it might be connected to thescikit-learn version is pulled in.

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_34zy_3spyu/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:30: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.

===== ERRORS =====

clone/recipe/meta.yaml:38: version_constraints_missing_whitespace: Packages and their version constraints must be space separated
===== Final Report: =====
1 Error and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_1ckgcfl1nh/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:30: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
===== Final Report: =====
0 Errors and 1 Warning were found

let's create and merge first 0.3.0 and then this one, otherwise we will have to have a versioned feedstock for 0.3.0

let's create and merge first 0.3.0 and then this one, otherwise we will have to have a versioned feedstock for 0.3.0

It's still unclear whether the client actually needs both versions. The production code is identical aside from a single exception message. Jack asked them about it last week, but there was no response.

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_73g3bjwvqe/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:30: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
===== Final Report: =====
0 Errors and 1 Warning were found


Autocomplete Off is not working

Describe the bug
Not able to turn off the auto-complete for ngx-otp-input
To Reproduce
Not able to turn off the autocomplete for ngx-otp-input by using several below methods -:

autocomplete = "off"
autocomplete = "new-password"
By making custom directive for disabling the autocomplete
By creating a similar input field and setting it to display:none

Expected behavior
It should not give the suggestion list for ngx-otp-input
Screenshots

Desktop (please complete the following information):

Browser Chrome
Version 108.0.5359.125

Hey @Shreyabhanot!
Thanks for opening the issue. Could you reproduce the same behavior in other browsers too? Chrome tends to ignore the autocomplete="off" attribute.

Hey @pkovzz !
It was not working because ngx-otp-input is only a wrapper for input elements. Resolved by manipulating the inside input elements.
Check the below link for the resolution
https://stackoverflow.com/questions/76051809/not-able-to-turn-off-auto-complete-for-ngx-otp-input-in-angular

Hello @Shreyabhanot and @pkovzz
I am experiencing the same problem, I noticed that if I include in the settings isPasswordInput: true the auto complete stops occurring as expected. And as described in this link:
https://pt.stackoverflow.com/questions/61510/como-remover-auto-complete-de-input-do-google-chrome
In current versions of Google Chrome it is possible to solve this if autocomplete="off" is in the form tag.
Suggestion:
Modify the file receiving the boolean autocomplete definition received from the NgxOtpInputConfig interface.
https://github.com/pkovzz/ngx-otp-input/blob/master/projects/ngx-otp-input/src/lib/component/ngx-otp-input.component.html
Modify the file by making the NgxOtpInputConfig interface have the autocomplete configuration property.
https://github.com/pkovzz/ngx-otp-input/blob/master/projects/ngx-otp-input/src/lib/component/ngx-otp-input.model.ts
Does that make sense to you? Is this a good approach to solving the problem?

Hello @wescleysrn!
Thank you very much for your effort to fix this issue. To be honest, I'm not really satisfied with the current state of the library, so I've decided to rewrite it in the near future, including this and other fixes as well. Since I can't tell you exactly when this will happen, if you have a strict deadline, I suggest checking other OTP libraries too.