SECP256k1 support

This closes #4233, together with the relevant cardano-base PR. Currently, this PR depends on the MLabs fork of cardano-base; once the linked PR merges, I will amend to work against master again. This shouldn't affect review, as while this depends on functionality from cardano-base, nothing in here is affected by precisely what branch of cardano-base we pull from.
Edit: This is now done.
I've added some property-based tests using Hedgehog to ensure all possible paths are equally covered. Specifically, we check each of the following:

Malformed pubkey
Malformed signature
Malformed message hash
Use of the wrong verification key
Checking the wrong signature for a given message
The happy path (that is, everything works)

As per @kwxm's feedback on my prior work on plutus-tx, I've raised the test count high enough to ensure that fewer than 1 in a 1000 executions fail due to probabilistic coverage failures (a flaw in Hedgehog, and one we can't avoid).
A few concerns remain:

The builtin for SECP256k1 verification is extremely demanding of how its inputs are formatted, but currently, this is left entirely to the user to ensure: all arguments are BuiltinByteStrings. I didn't know if we wanted helpers (in plutus-tx or elsewhere) to make this process less nasty with newtype wrappers and helper functionality, so I haven't added it.
The tests for untyped-plutus-core are far too few in number: almost everything in there should be a property test, but even those which are run 200 tests, which is too few to indicate anything. For a demonstration of why: I found multiple bugs in how I implemented the SECP256k1 builtin only after over a thousand tests, and even then it took several attempts! Furthermore, coverage is not checked at all, which is alarming. The tests I wrote for the SECP256k1 primitive are vulnerable to neither.
As per @michaelpj's suggestion here, the costing function is currently mempty. I don't know how much of an issue this is.

It's confusing to refer to all of this as "SECP256k1 support" since SECP256k1 is just a curve. Since you are using secp256k1-haskell, it seems you do not support the Schnorr (BIP-340) signatures recently added to Bitcoin. So I suspect that you have in fact added ECDSA signature support using the SECP256k1 curve. Is that correct?

Ah, yeah, it must conflict horribly with my recent refactoring, I'll fix it for you.

Ah, yeah, it must conflict horribly with my recent refactoring, I'll fix it for you.

Done (not horribly at all).

For some reason it won't let me respond to the existing comments...
I agree that it's harmless to include tracing here. It's interesting that this is the first builtin other than trace that emits things, but probably good.
I'm not worried about specifying the tracing. We deliberately don't specify anything to do with log emitting since it's not observable in the main behaviour of the program.

Could the off-chain part of a contract run some validation code (also off the chain), look at the log files and then branch on the contents to determine the future behaviour of the contract (which you could do even using trace)?

Yes, but you can do whatever you want off-chain. You can run your PLC through a symbolic executor and buy a sandwich iff it returns true on Tuesday 22nd 2024. So I don't think we need to care about that.

I agree that it's harmless to include tracing here. It's interesting that this is the first builtin other than trace that emits things, but probably good.

I suppose there's not much that can go wrong with most of the existing builtins (mostly out of range errors), so there's no need give details when something goes wrong.  Maybe we could be more informative with some of the other ones though.  I 'll have to benchmark this for costing purposes at some point and while I'm doing that I'll check that the logging isn't adding any overhead.  It's highly unlikely that it will be since nothing at all should be happening on chain, but there's no harm checking.

@ysangkok Thank you for bringing this to our attention. We do indeed need Schnorr signature support; therefore, I'm marking this PR as WIP for now. I'll keep it current with plutus, but to add those will require me to do additional PRs to cardano-base at least, and possibly secp256k1-haskell as well.
@michaelpj and @kwxm: I have attempted, based on these instructions here and your feedback here, to generate a cost model for VerifySECP256k1Signature. However, after running cabal bench plutus-core:update-cost-model, the builtinCostModel.json doesn't seem to contain any reference to VerifySECP256k1Signature at all. I'm pretty sure I missed something, but I don't know what. The cost model in this case is fairly simple: the arguments are all fixed-width, so it should just be a constant function: I only don't know what said constant should be.

I have attempted, based on these instructions here and https://github.com/input-output-hk/plutus/issues/4375#issuecomment-1029864939, to generate a cost model for VerifySECP256k1Signature.

@kozross Please undo this!!!!  As mentioned in the second link above, these benchmarks MUST be run on a specific machine which at the moment only we have access to (unfortunately, but that's hard to change and there may even be legal difficulties because the machine is provided to us by an external party and we may be limited in who's allowed to access it).  The changes to costModel.json involve drastic changes to the costing functions for all of the builtins and it would be disastrous to merge this because it would lead to significant changes in the costs of scripts.  We need the costs to remain relatively consistent and to ensure this we have to use the same machine every time.
We can generate a suitable cost model once this PR is merged.  In the meantime mempty will be OK, especially because the function should have constant cost.
I did send an email about this to the address on your GitHub account a few days ago, but I'm not sure if you got it.

@kwxm OK, I'll revert the change. I did receive your email, but the 'reference machine' part must have eluded me.

@kwxm OK, I'll revert the change. I did receive your email, but the 'reference machine' part must have eluded me.

Thanks!  I'm afraid that this situation's not very satisfactory, but it's not clear what else we can do at the moment.  Eventually there'll have to be some community process for this kind of thing, but that's probably quite a long way off at the moment.

I'm glad we discovered the confusion about the signature algorithm before we merged this!
@kozross I'll let you work out what it is that you actually need, I guess the only thing to bear in mind for coming back to this PR is that we should indeed include the algorithm name as well as the curve in the name of the builtin, so we don't get confused in future.

@michaelpj, @effectfully and @kwxm - I have now added the missing builtin we needed, addressed all concerns (as well as some naming concerns raised both here and in cardano-base). This currently depends on the MLabs fork of cardano-base, pending this PR landing.

Windows builds seem to be failing according to the logs.

@michaelpj I have no access to a Windows machine to test this on, and frankly don't even know how this combination of Nix and Windows works. I'm happy to do something if instructed how, but it's very far out of my understanding.

I can take a look. It would really help if you checked the box to allow commits to your branch by maintainers.

@michaelpj I would like to, but I'm having trouble finding it. This is all I can see:

Hmm, I don't know why that isn't there, normally you can do that :thinking:
Summon @hamishmack , who set up the windows stuff, perhaps you can give us a hand?

@michaelpj I think I fixed that issue, but now Agda's blowing up instead.

@michaelpj In that case, @hamishmack might know why. I took my best guess at the problem. I'll merge your PR in the meantime.

Try this https://github.com/hamishmack/plutus/commit/57469864592d77eded0b0f3983f368d15525d329

Edit: It seems they were moved into plutus-core-testlib, which means I now can't depend on them.

You can, just see Nikos' suggestion.

Now the build issues are sorted out I think we can return to this. I'm not totally clear where we are on it: I think we're basically good to go? The failing builds are darwin (we have build machine issues, so it's disabled on master); merging master should fix that. And there are a few conflicts.

@michaelpj I've resolved the conflicts. Other than this, I believe the work is done: I have addressed reviewer concerns, I'm not aiming at any branches (such as for cardano-base), and the tests are present and passing.

The error message is hard to read because megaparsec errors don't Show well, but the issue is that you need to add cases for the new builtins to https://github.com/input-output-hk/plutus/blob/master/plutus-core/plutus-core/src/PlutusCore/Parser/Builtin.hs.
(@thealmarty can we make this list auto-generated so this doesn't happen in future? I think we should just be able to enumerate DefaultFun and populate the list with the value and its pretty-printed version.)

https://github.com/mlabs-haskell/plutus/pull/5

(@thealmarty can we make this list auto-generated so this doesn't happen in future? I think we should just be able to enumerate DefaultFun and populate the list with the value and its pretty-printed version.)

(It's how it used to be. Not only doing this automatically is way more convenient, but also allows us to handle sets of built-in functions other than DefaultFun)

@michaelpj Yeah, I believe it used to work this way, and must have changed without my noticing.

I can't seem to reproduce this failure locally:
      deconstructorData2:             FAIL
        Test output was different from 'test/Plugin/Primitives/deconstructorData2.plc.golden'. Output of ["diff","-u","test/Plugin/Primitives/deconstructorData2.plc.golden","/build/deconstructorData2.plc13-54.actual"]:
        --- test/Plugin/Primitives/deconstructorData2.plc.golden        1970-01-01 00:00:01.000000000 +0000
        +++ /build/deconstructorData2.plc13-54.actual   2022-04-21 19:51:44.217039864 +0000
        @@ -239,6 +239,31 @@
                   (termbind
                     (strict)
                     (vardecl
        +              fst (all a (type) (all b (type) (fun [ [ (con pair) a ] b ] a)))
        +            )
        +            (builtin fstPair)
        +          )
        +          (termbind
        +            (strict)
        +            (vardecl
        +              snd (all a (type) (all b (type) (fun [ [ (con pair) a ] b ] b)))
        +            )
        +            (builtin sndPair)
        +          )
        +          (termbind
        +            (strict)
        +            (vardecl
        +              unsafeDataAsConstr
        +              (fun
        +                (con data)
        +                [ [ (con pair) (con integer) ] [ (con list) (con data) ] ]
        +              )
        +            )
        +            (builtin unConstrData)
        +          )
        +          (termbind
        +            (strict)
        +            (vardecl
                       chooseList
         <truncated>
        Use --accept or increase --size-cutoff to see full output.
        Use -p '/deconstructorData2/' to rerun this test only.

I had to repair a similar issue before, but on my local copy of my branch (which I just pushed), this test passes:
      deconstructData1:               OK
      deconstructorData2:             OK
      deconstructData2:               OK
      deconstructData3:               OK
    Data

I can't seem to reproduce this failure locally

I agree it's weird, but I suspect you can just revert the change contained in your PR, I suspect it will accept the old one.

That's a static test I don't see why it would do that either. Anyway lmk if you think the parser is suspicious. It seems my fix works.

@thealmarty - your fix looks like it worked. I also have no idea why this test fails.

What a saga. Thanks!


Unable to find factory method for Kiota.Builder.CodeDOM.CodeUnionType for oneOf and allOf schema

Hi I'm using VSCode extension to generate Typescript SDK from an OpenAPI Spec file but having the following error. I believe it's related to the schema contains allOf or oneOf in it. I tried different scenarios that when the schema hierarchy doesn't contain one of them then the generator works fine without any error.
Error message

OpenAPI Spec file
openapi: 3.0.0
info:
  title: Mock API
  version: '1.0.0'
  description: Mock API to reproduce issue with kiota generator
paths:
  /mystuff:
    get:
      operationId: mystuff_get
      responses:
        '200':
          description: The request has succeeded.
          headers:
            schema:
              required: true
              schema:
                type: string
          content:
            application/json:
              schema:
                type: object
                properties:
                  results:
                    $ref: '#/components/schemas/ParentSchema'
                required:
                  - results
                x-typespec-name: (anonymous model)

components:
  schemas:
    ParentSchema:
      type: object
      properties:
        name:
          type: string
        firstChild:
          allOf:
            - $ref: '#/components/schemas/NormalChild'
        secondChild:
          $ref: '#/components/schemas/ChildCOntainsOneOf'
      required:
        - name
        - firstChild
        - secondChild
    NormalChild:
      type: object
      properties:
        key:
          type: string
      required:
        - key
    ChildCOntainsOneOf:
      discriminator:
        propertyName: schemaType
      oneOf:
        - $ref: '#/components/schemas/RandomSchema_1'
        - $ref: '#/components/schemas/RandomSchema_2'
    RandomSchema_1:
      type: object
      properties:
        schemaType:
          type: string
          enum:
            - absolute
        key:
          type: integer
      required:
        - key
    RandomSchema_2:
      type: object
      properties:
        schemaType:
          type: string
          enum:
            - relative
        key:
          type: integer
        index:
          type: integer
      required:
        - index
        - key
servers:
  - url: https://example.com
    description: Single server endpoint
    variables: {}

Steps to reproduce:

In VSCode extension, run > Kiota OpenAPI Explorer and choose this file
Put in the parameters required
An error will show up in the bottom right corner

Also can be reproduced by running Kiota CLI: kiota generate -l typescript -d gh-issue.yml -c Client -o ./client

Note
The error doesn't show up when generating the SDK in Python.
Any help would be appreciated. :)

Hey @zoeyzuo-se,
This is expected, composed types serialization hasn't been implemented yet in TypeScript.
But this is being worked on right now #1812 and the hope is that it'll be available with the next minor version of kiota.
Closing as duplicated.

Hi @baywet
Thanks for the reply. May I ask is there an ETA for the next minor version?

Early September


Uncaught Error: Unknown system error -122: Unknown system error -122, close

Working in dir with python and large text files. Using python to read the files. Issue when saving the python doc that reads and plots the large text files. Unsure of exact steps.
Issue due to exceeding memory on hard drive.
Atom: 1.18.0 x64
Electron: 1.3.15
OS: "Red Hat
Thrown From: Atom Core
Stack Trace
Uncaught Error: Unknown system error -122: Unknown system error -122, close
At /usr/share/atom/resources/app/src/pane.js:1095

Error: Unknown system error -122: Unknown system error -122, close
    at Error (native)
    at Object.fs.closeSync (fs.js:609:18)
    at Object.closeSync (/usr/share/atom/resources/app/node_modules/graceful-fs/graceful-fs.js:51:27)
    at Object.fs.writeFileSync (fs.js:1361:23)
    at Proxy.writeFileSync (/usr/share/atom/resources/app/node_modules/fs-plus/lib/fs-plus.js:295:29)
    at File.module.exports.File.writeFileSync (/usr/share/atom/resources/app/node_modules/pathwatcher/lib/file.js:289:25)
    at File.module.exports.File.writeFileWithPrivilegeEscalationSync (/usr/share/atom/resources/app/node_modules/pathwatcher/lib/file.js:467:27)
    at File.module.exports.File.writeSync (/usr/share/atom/resources/app/node_modules/pathwatcher/lib/file.js:384:18)
    at TextBuffer.module.exports.TextBuffer.saveAs (/usr/share/atom/resources/app/node_modules/text-buffer/lib/text-buffer.js:1127:25)
    at TextBuffer.module.exports.TextBuffer.save (/usr/share/atom/resources/app/node_modules/text-buffer/lib/text-buffer.js:1108:25)
    at TextEditor.module.exports.TextEditor.save (/usr/share/atom/resources/app/src/text-editor.js:925:32)
    at Pane.module.exports.Pane.saveItem (/usr/share/atom/resources/app/src/pane.js:780:24)
    at Pane.saveItem (/usr/share/atom/resources/app/src/pane.js:3:65)
    at Pane.module.exports.Pane.saveActiveItem (/usr/share/atom/resources/app/src/pane.js:763:25)
    at Workspace.saveActivePaneItem (/usr/share/atom/resources/app/src/workspace.js:1548:46)
    at atom-workspace.core:save (/usr/share/atom/resources/app/src/register-default-commands.js:236:38)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/usr/share/atom/resources/app/src/command-registry.js:265:35)
    at /usr/share/atom/resources/app/src/command-registry.js:3:65
    at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/usr/share/atom/resources/app/node_modules/atom-keymap/lib/keymap-manager.js:610:22)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/usr/share/atom/resources/app/node_modules/atom-keymap/lib/keymap-manager.js:401:28)
    at WindowEventHandler.module.exports.WindowEventHandler.handleDocumentKeyEvent (/usr/share/atom/resources/app/src/window-event-handler.js:100:42)
    at HTMLDocument.<anonymous> (/usr/share/atom/resources/app/src/window-event-handler.js:3:65)

Commands
     -2:06.6.0 core:move-up (input.hidden-input)
     -2:06.3.0 core:move-right (input.hidden-input)
  2x -2:04.2.0 core:backspace (input.hidden-input)
     -2:01.3.0 core:move-right (input.hidden-input)
     -1:36 core:backspace (input.hidden-input)
     -1:24.9.0 core:copy (input.hidden-input)
     -1:23.5.0 core:paste (input.hidden-input)
     -1:21.6.0 core:backspace (input.hidden-input)
     -1:20.5.0 core:save (input.hidden-input)
     -1:18.7.0 editor:newline (input.hidden-input)
     -1:14.5.0 snippets:next-tab-stop (input.hidden-input)
     -1:14.5.0 snippets:expand (input.hidden-input)
     -1:14.5.0 editor:indent (input.hidden-input)
  4x -1:13.9.0 core:backspace (input.hidden-input)
     -1:11.7.0 autocomplete-plus:confirm (input.hidden-input)
  4x -1:11.1.0 core:save (input.hidden-input)

Non-Core Packages
atom-clock 0.1.13
atom-html-preview 0.1.22
atom-latex 0.7.11
git-plus 7.9.3
language-matlab 0.2.1
minimap 4.28.3
minimap-pigments 0.2.2
nebula-syntax 0.4.4
nebula-ui 0.6.0
pigments 0.39.1
split-diff 1.4.3
zentabs 0.8.8

Thanks again for your issue!
We haven't received a response to our question in this comment https://github.com/atom/atom/issues/15092#issuecomment-318189598. With only the information that is currently in the issue, we don't have enough information to take action. I'm going to close this but don't hesitate to reach out if you have or find the answers we need, we'll be happy to reopen the issue.


Scripts Folder

Hey all, I have created a new branch where I pushed my script for the EDA. Please feel free to pull my work after merging to add your scripts to the script folder.

Well organized! Just put mine in the folder

Closing the scripts issue now that we are done with it.


Make serverRequestCall interruptible

This PR proposes a way to make Servers stoppable. Currently, Servers are most of the time blocked in a uninterruptible foreign call (pluck), making them impossible to kill.
Instead of making a blocking foreign call without a timeout, we set a timeout of one second. This way, the thread returns in Haskell code (and thus is interruptible) at least every second. This is useful in order to be able to kill Servers, see https://github.com/awakesecurity/gRPC-haskell/issues/22.

I'd thought perhaps interruptible would be useful here

I thought so too, however switching the relevant call to interruptible didn't work for me. I hypothesized that maybe that piece of gRPC code did not react to the SIGPIPE signal, since this is the signal sent to interruptible calls, but I didn't dig further.

LGTM, thanks @OlivierNicole!


test: link-check: misc fixes

[x] fix git diff (yarn link-check-diff) exclusion bug #1148

fix execution syntax $() bug
fix missing include . bug
fix missing path sep -- bug
use same syntax for excluding exclude-links.txt and redirects-list.json

[ ] consider only including *.md and *.js as with yarn link-check?

[x] support mac sed
[x] spaces in file path safety
[x] running outside repo safety
[x] report more than just the first error per file in git diffs
related #1000
fixes #1148

found more links in the additionally included files:
https://dvc.org/blog/$1
https://dvc.org/blog$1
https://dvc.org/doc/command-reference$1
https://s3-us-east-2.amazonaws.com/dvc-public/$1/$2
https://s3-us-east-2.amazonaws.com/dvc-s3-repo/$1

Presumably ok to add these to exclusions?


add pseudocode makefile

This provides the pseudocode makefile for the reorganization. We need to fill this out with the correct bash/python scripting to make this happen.

Coverage remained the same at 83.056% when pulling b7d95835369934f62241ce57733a36779e6f1636 on ljwolf:reorg into fa1e8116dabdbbcfb33e31ce5aa9cbf330a91569 on pysal:reorg.

Coverage remained the same at 83.056% when pulling b7d95835369934f62241ce57733a36779e6f1636 on ljwolf:reorg into fa1e8116dabdbbcfb33e31ce5aa9cbf330a91569 on pysal:reorg.

Coverage remained the same at 83.056% when pulling b7d95835369934f62241ce57733a36779e6f1636 on ljwolf:reorg into fa1e8116dabdbbcfb33e31ce5aa9cbf330a91569 on pysal:reorg.

Coverage remained the same at 83.056% when pulling b7d95835369934f62241ce57733a36779e6f1636 on ljwolf:reorg into fa1e8116dabdbbcfb33e31ce5aa9cbf330a91569 on pysal:reorg.


Added support for relationships in Dynamic Groups.

Closes: #3220
What's Changed
This is the version for the next branch

This unblocks fields starting with cr_ from being used in filters for Dynamic Groups
Augmented the edit view to break fields down by "object fields", "custom fields" (not shown), and "relationships":

TODO

[ ] Explanation of Change(s)
[ ] Added change log fragment(s) (for more information see the documentation)
[ ] Attached Screenshots, Payload Example
[ ] Unit, Integration Tests
[ ] Documentation Updates (when adding/changing features)
[ ] Example Plugin Updates (when adding/changing features)
[ ] Outline Remaining Work, Constraints from Design

Blocked by #3353

Is this not negated when #3353 gets merged into develop then develop gets merged into next you'll have to address the failing tests/merge conflict problem?

Is this not negated when #3353 gets merged into develop then develop gets merged into next you'll have to address the failing tests/merge conflict problem?

Indeed. Closed by #3353


'Heron.gui.settings' has no attribute 'settings_dict' on windows with pip install

Hi there,
I am very interested in using this framework. I am having a couple of issues. This issue is related to the pip install on a windows 10 machine. I am finding that the paramiko client fails when the settings_dict attribute is not getting set. Is there an easy fix for this?

\anaconda3\envs\NewPipHeron\Lib\site-packages\Heron\communication\sink_worker.py", line 206, in heartbeat_loop
heartbeat_rate = settings.settings_dict['Operation']['HEARTBEAT_RATE']
^^^^^^^^^^^^^^^^^^^^^^
AttributeError: module 'Heron.gui.settings' has no attribute 'settings_dict'

Hi Iceweasle.
Thanks for the bug report. Try again (pip uninstall the old Heron and re install). The new version should have no problems with the settings. Let me know if it is ok and I will close the issue, otherwise I will have another look at it.

Also, forgot to mention. pip uninstall will leave behind the Heron folder which needs deleting before reinstalling.

I am closing this now since I asume the problem is fixed.


MRVC PlayBack

I am using 5.5.0f3 personal unity editor to create the LowLatencyMrcSample app from source. When I use the viewer, it is always timing out. I have restarted the app and rebooted the device multiple times, but to no avail. I have put some Logging statements in MrvcManager to see if playback connector ever gets called, but the log statement isn't getting hit. I am wondering if that is because of a different version of Unity Editor, or something wrong that I doing. Any help would be appreciated.

Figured out my mistake, it works fine now.

@deaga What was the mistake and how you were able to fix? I am also facing the exact problem and not able to figure out what is wrong, Viewer application always timeout when trying to connect to Low Latency app running in HoloLens.

@mannu598 Do you fix the mistake? I also meet this problem, every time I try to connect the capture device in the hololens it is always timing out, which shows "A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond."

@txliang Sorry I was not able to fix and moved to a high priority project. Maybe I will be able to get back to it after a couple of weeks, once done with the current project on plate.


Remove unused dependencies

This version fix problem of import library in project

@augmity can you please see this PullRequest ?

sorry, I'm pretty busy recently, but I'll try to check it over the weekend


No module named 'pl_bolts.models.autoencoders'

As what "https://github.com/PyTorchLightning/lightning-bolts/issues/707" said, I removed pytorch lightning bolts module, and I successfully installed lightning bolts, but I kept getting an error below:
---------------------------------------------------------------------------
ModuleNotFoundError                       Traceback (most recent call last)
/tmp/ipykernel_3033447/2816402708.py in <module>
      2 from torch import nn
      3 import torch
----> 4 from pl_bolts.models.autoencoders.components import (
      5     resnet18_decoder,
      6     resnet18_encoder,

ModuleNotFoundError: No module named 'pl_bolts.models.autoencoders'

I am running it on ipynb
Torch 1.9.1
lightning-bolts 0.4.0
How you installed PyTorch (conda, pip, source): pip
Build command you used (if compiling from source):
Python version: 3.8.2

I tried this localy but it works.
Env

Torch - 1.9.1
PyTorch Lightning - 1.4.9
Lightning Bolts - 0.4.0
Python - 3.8.8
Env(pip,conda) - Conda

Thanks for getting back to me. But I faced the similar issues below:

ModuleNotFoundError                       Traceback (most recent call last)
/tmp/ipykernel_4044614/4231511349.py in
1 from torch import nn
2 import torch
----> 3 from pl_bolts.callbacks.ssl_online import SSLOnlineEvaluator
4 from pl_bolts.models.autoencoders.components import (
5     resnet18_decoder,
ModuleNotFoundError: No module named 'pl_bolts.callbacks.ssl_online'
PyTorch Lightning - 1.4.9
Lightning Bolts - 0.4.0
torch  -  1.10.0+cu113

requirements.txt

These are the dependencies I used

Can you try downgrading from 1.4.9

Thanks for sharing the env lists.
Yeah I downgraded to 1.3.8 but still faced the same issue. By the way I am using the jupyter lab on the server.

hi,
Is it different in VSCode and other.

Oh no, I found a problem here.
I upgraded python version to 3.8.8 and now it is working fine.
3.8.2 keeps facing error. Not sure why though...


InteractiveViewer has a delay in recognizing a zoom gesture when wrapped in a GestureDetector

When starting a pinch-to-zoom gesture on an InteractiveViewer wrapped in a GestureDetector, there is a delay before anything happens, which causes a sort of jarring jump:

This is probably caused by weird interactions between the internal and external GestureDetectors in Flutter's gesture arena.  If the onTap callback is removed here, the bug doesn't happen.
import 'package:flutter/material.dart';

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Text field',
      home: Scaffold(
        body: Center(
          child: GestureDetector(
            onTap: () {},
            child: InteractiveViewer(
              child: Container(
                width: 300,
                height: 300,
                color: Colors.limeAccent,
              ),
            ),
          ),
        ),
      ),
    );
  }
}

flutter doctor -v
[✓] Flutter (Channel master, 1.19.0-4.0.pre.47, on Mac OS X 10.15.5 19F96, locale en-GB)
    • Flutter version 1.19.0-4.0.pre.47 at /Users/tahatesser/Code/flutter_master
    • Framework revision 28138ec5e3 (6 hours ago), 2020-06-04 00:33:01 -0400
    • Engine revision 2608f2ee9f
    • Dart version 2.9.0 (build 2.9.0-13.0.dev 54adfeb93f)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/tahatesser/Code/sdk
    • Platform android-29, build-tools 29.0.3
    • ANDROID_HOME = /Users/tahatesser/Code/sdk
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

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

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

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 46.0.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

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

[✓] Connected device (3 available)
    • macOS      • macOS      • darwin-x64     • Mac OS X 10.15.5 19F96
    • Web Server • web-server • web-javascript • Flutter Tools
    • Chrome     • chrome     • web-javascript • Google Chrome 83.0.4103.61

• No issues found!

This same problem also manifests itself in the InteractiveViewer gallery demo.  Dragging a piece that has been placed inside the InteractiveViewer has a delay before the drag is recognized.
I noticed that if I removed the GestureDetector inside of InteractiveViewer, then the delay was gone.

I have similar issue, but I did not wrap in GestureDetector.
The zoom gesture has delay.

I think the real issue is, that in the interaktive Viewer is not the delay, which is normal as you need a small offset to detect that it infact is a zoom gesture that is performed right now.
It's the same in google fotos.
But the difference is, that in google fotos the zoom starts from 0 when it was detected, that a zoom gesture happening right now.
The interactive viewer in comparison calculates the zoom from when the gesture started. So when we detect that the current gesture is a zoom gesture it will not start scaling from that point on, but start scaling from when we started touching the screen. So the offset will cause it to jump to a specific zoomed in / out state instead of just starting to zoom in / out from that point on

Agree!. Is there any way that we can set zoom starts form 0 like Google photos ?

@lazylazyllama That is a great observation!  I really appreciate you writing that out.  Let me know what you think of this PR if you get a chance: https://github.com/flutter/flutter/pull/71497

@justinmc that looks really good, glad I could help :)


Add ~nedia/auto-save.nvim

Checklist:

[x] The plugin is specifically built for Neovim, or if it's a colorscheme, it supports treesitter syntax.
[x] The lines end with a .. This is to conform to awesome-list linting and requirements.
[x] It's not already on the list.
[x] The title of the pull request is Add/Update/Remove `username/repo`  when adding a new plugin.
[x] The description doesn't start with A Neovim plugin for... or A plugin for..., and doesn't end with ... for Neovim.
[x] The description doesn't mention that it's a Neovim plugin, it's obvious from the rest of the document.
[x] Neovim is spelled as Neovim (not nvim, NeoVim or neovim), Vim is spelled as Vim (capitalized), Lua is spelled as Lua (capitalized).

Thanks for the PR!


Error on Fresh Install

Looks like a great package! I just composer required it, though and when I run php artisan tests:watch I immediately get this error thrown.
Argument 1 passed to Dotenv\Dotenv::create() must implement interface Dotenv\Repository\RepositoryInterface, string given, called in /Users/brian/Projects/Trig/Repos/backend/vendor/wackystudio/laravel-test-watcher/src/Console/TestWatcherCommand.php on line 24

  at vendor/vlucas/phpdotenv/src/Dotenv.php:62
    58|      * @param bool                                   $shortCircuit
    59|      *
    60|      * @return \Dotenv\Dotenv
    61|      */
  > 62|     public static function create(RepositoryInterface $repository, $paths, $names = null, $shortCircuit = true)
    63|     {
    64|         $builder = StoreBuilder::create()->withPaths($paths)->withNames($names);
    65|
    66|         if ($shortCircuit) {

      +16 vendor frames
  17  artisan:37
      Illuminate\Foundation\Console\Kernel::handle(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))

Any ideas?

Hey @bjenkins24 thank you for adding this issue.
It throws this error because of the changes to the initialisation of DotEnv v4 (which Laravel 7 uses). In v4 Dotenv is not using the Dotenv::create() method anymore, but Dotenv::createMutable() or Dotenv::createImmutable() instead.
The package is now updated to support both DotEnv v3 and v4, so if you update you project to use v1.0.13 of Laravel Test Watcher the issue should be fixed.
Let me know how it goes.

Closing this issue since the package update solves the issue


#3 Implement basic obstecale avoidence.

This commit makes the car drive forward and stop 15 cm befor hitting an obstecale. solves: #8

@platisd the changes you requested is now in the latest commit.

@platisd the changes you requested is now in the latest commit.

There's a little "refresh" icon next to my username. If you press on it a review will be re-requested. :+1:


when i try to open this close really quickly

A fatal error occurred. The required library hostfxr.dll could not be found.
If this is a self-contained application, that library should exist in [C:\Users\USER~1\AppData\Local\Temp.net\LawinServer (1)\5vyyafkr.tgt].
If this is a framework-dependent application, install the runtime in the global location [C:\Program Files\dotnet] or use the DOTNET_ROOT environment variable to specify the runtime location or register the runtime location in [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x64\InstallLocation].
The .NET Core runtime can be found at:

https://aka.ms/dotnet-core-applaunch?missing_runtime=true&arch=x64&rid=win10-x64

Yo. It's self explanatory. You have to download the runtime : https://dotnet.microsoft.com/download/dotnet-core/thank-you/runtime-desktop-3.1.7-windows-x64-installer


karpenter.azure.com/zone requirement causes continuous drift

Version

Karpenter Version: https://github.com/Azure/karpenter-provider-azure/commit/99d1bb0730b3462e40267ec28024368c90801b26 (current main)

Kubernetes Version: v1.27.9
Expected Behavior
One should be able to specify requirements with karpenter.azure.com/zone constraint, for example to only provision nodes in a specific zone, without adverse effects.
Actual Behavior
Specifying any kind of karpenter.azure.com/zone constraint in a NodePool current triggers continuous drift.
Here is what I am thinking is going on. Right now, we cannot (and do not) record this requirement/constraint as a label on NodeClaim. This is because Karpenter will try applying all of these as labels to Node object - and topology.kubernetes.io/zone
is a protected label in AKS. (It will be applied to a new Node correctly, but by a different component). So for now, as a workaround, we use an alternative label karpenter.azure.com/zone. I suspect that it is this discrepancy that causes Karpenter to detect Requirements Drift: Based of NodePool, the NodeClaim is expected to have the zone label, and it does not => out of spec, to be replaced. I also suspect that, while we do have E2E tests in this area, they likely only test that the node gets provisioned, and don't notice the subsequent drift.
Steps to Reproduce the Problem
Use NodePool with any kind of karpenter.azure.com/zone requirement.
Resource Specs and Logs
Continuous drift observed.
Workaround
Specify zone-based constraints (including topologySpreadConstraint, if needed) via workload, rather than NodePool.
Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Hello @tallaxes @Bryce-Soghigian
I've been throughly testing karpenter as I plan to leverage it on my workloads and I am also having problems with the zone configuration in the nodepool. I have a nodepool configured with the following requirement:
...         - key: karpenter.azure.com/zone           operator: In           values: ["eastus-1", "eastus-2", "eastus-3"]
Whenever I apply it, i get the following message:
The NodePool "krptpool" is invalid: spec.template.spec.requirements[6].key: Invalid value: "string": label domain "karpenter.azure.com" is restricted.
Thus, the workaround mentioned doesn't seem to work (unless I am doing something really silly).
Can you guys please take a look at it?
Also, I would like to point out that the documentation here https://learn.microsoft.com/en-us/azure/aks/node-autoprovision?tabs=azure-cli#sku-selectors-with-well-known-labels provides another key (also reserved) that doesn't work topology.kubernetes.io/zone so it would be a good idea to update it imo.

We’re facing the issue. Any workaround?


closeOnClickOutside doesn't work for ipad

I ran into an issue when I try to use this dropdown in safari on an ipad when the user clicks outside of the drop down it doesn't close the the dropdown.

did anyone find a solution for this?


Terminology: "Component" vs "Session"

In almost all examples, and in much of the documentation, the term "session" and "component" are mixed in a slightly confusing way.
E.g. many of the examples: class Component(ApplicationSession):. This just rhymes bad to me. Why not call the derived class Session? It derives from an Autobahn ApplicationSession.
I guess you could argue that you build your "component", and that "component" happen to be implemented as an Autobahn ApplicationSession. But I think naming things are important and would really like to hear why the terms "session" and "component" are mixed like this in the code.
I'm itching to call my own such classes FooSession and BarSession, to follow the naming of the superclass... but then in the API there's autobahn.wamp.types.ComponentConfig... Again, why is this called "component"? Isn't it a configuration for an application session? In fact, this is the only class I can find in the public API which is named something with "component". I would expect this class to be called either ApplicationSessionConfig or just SessionConfig (if ApplicationSession is to keep its name).

I would vote for keeping the names in the code and the API 100% "session". And let "component" be something more abstract that you use when talking in general about building your applications... I can understand how the two have become somewhat intermingled, but I think it's important that such dualities doesn't creep into the API.
In the API right now it's autobahn.wamp.types.ComponentConfig class, the allowEmptyComponents parameter of the autobahn.wamp.message.check_or_raise_uri method and the documentation of the config parameter of autobahn.wamp.protocol.ApplicationSessionFactory where I think the use of "component" sticks out. (Also the convenience Application and ApplicationRunner I see now..).

I agree with this. Everything that reduces confusion is good. Systematic terminology is important.
An application "component" uses a "session" to connect to a router.

subseded/fixed in https://github.com/crossbario/autobahn-python/issues/964


Extra line break in molecule status for better visibility

Before:

After:

:+1: after my remarks.

@rgreinho Cleaned up the use of print keyword for this change and the last. Interestingly, print() will be treated like the keyword and will literally print '()' to the screen. Had to print a blank string to get the intended behavior.

@abrown-sg Good to know. It is a python 2 specific behavior though. Maybe a python bug?
Python 3.5.1 (default, Dec  7 2015, 21:59:08)
[GCC 4.2.1 Compatible Apple LLVM 7.0.0 (clang-700.1.76)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> print()

>>>

@rgreinho Yeah, looks like a behavior of 2.X.  Should we use print_function from future?
>>> print()
()
>>> from __future__ import print_function
>>> print()

Sure, that does not sound like a bad idea to me.

@rgreinho @retr0h I went ahead and cleaned up the usage of print() everywhere and standardized on using the future version. We were already doing this in utilities. May as well make it consistent.  future imports have to come first in the file.

Big :+1: !

Why don't we just have utilities.print() that implements future print vs having to import all over the place?

Hummm... because you did not propose this great idea before? :)

@retr0h @rgreinho It doesn't look like you can redefine the print statement as a function in Python 2 because it's a language construct. Attempting to do def print(line):... in utilities ends in tears. I think to do what @retr0h suggested we'd have to name it something else. Not sure I prefer utilities.my_print() everywhere over just living with the import and using print(). Or doing away with the import and keeping the 2.x behavior until we make a real push toward 3.x compatibility.

Disregard that, looks like it's possible with the future stuff. That said, is using utilities.print() everywhere instead of print() cleaner and more clear than a single import line?

Right, it is kind of the the same. I'm fine with the __future__ import.

@rgreinho @retr0h Threw another quick fix into this since it's related.

:+1:


:warning: Action Required: Replace Deprecated gcr.io/kubebuilder/kube-rbac-proxy

Description
:warning: The image gcr.io/kubebuilder/kube-rbac-proxy is deprecated and will become unavailable.
You must move as soon as possible, sometime from early 2025, the GCR will go away.

Unfortunately, we're unable to provide any guarantees regarding timelines or potential extensions at this time. Images provided under GRC will be unavailable from March 18, 2025, as per announcement. However, gcr.io/kubebuilder/may be unavailable before this date due to efforts to deprecate infrastructure.

If your project uses gcr.io/kubebuilder/kube-rbac-proxy, it will be affected.
Your project may fail to work if the image cannot be pulled. You must take action as soon as possible.

However, if your project is no longer using this image, no action is required, and you can close this issue.

Using the image gcr.io/kubebuilder/kube-rbac-proxy?
kube-rbac-proxy was historically used to protect the metrics endpoint. However, its usage has been discontinued in Kubebuilder. The default scaffold now leverages the WithAuthenticationAndAuthorization feature provided by Controller-Runtime.
This feature provides integrated support for securing metrics endpoints by embedding authentication (authn) and authorization (authz) mechanisms directly into the controller manager's metrics server, replacing the need for (https://github.com/brancz/kube-rbac-proxy) to secure metrics endpoints.
What To Do?
You must replace the deprecated image gcr.io/kubebuilder/kube-rbac-proxy with an alternative approach. For example:

Update your project to use WithAuthenticationAndAuthorization:

You can fully upgrade your project to use the latest scaffolds provided by the tool or manually make the necessary changes. Refer to the FAQ and Discussion for detailed instructions on how to manually update your project and test the changes.

Alternatively, replace the image with another trusted source at your own risk, as its usage has been discontinued in Kubebuilder.

For further information, suggestions, and guidance:

📖 FAQ and Discussion
💬 Join the Slack channel: #kubebuilder.

NOTE: This issue was opened automatically as part of our efforts to identify projects that might be affected and to raise awareness about this change within the community. If your project is no longer using this image, feel free to close this issue.

We sincerely apologize for any inconvenience this may cause.
Thank you for your cooperation and understanding! :pray:

This looks like spam.

Hi @clayrisser,
This is not spam—I wanted to bring to your attention that you're using the image in your repository here: manager_auth_proxy_patch.yaml#L12-L25.
We've been in communication for almost a year, striving to support the community and help everyone move forward. However, if no action is taken on your part, please be aware that your solution may stop functioning when the image becomes unavailable.
If this is being used by others, your users could also be affected when the image is no longer accessible. If you need any help understanding the next steps, please don’t hesitate to reach out—we’re here to assist.
For further information, please ensure you check this discussion: kubernetes-sigs/kubebuilder#3907.


Scam URL Galxe

Name
Scam URL Galxe
Description
Users are redirected to a suspicious platform known as Galxe.com. It is designed with malicious intent, attempting to deceive visitors and potentially fund transfers from users who interacted with this website. The funds are being directed to the following address: 0x000082cc936dbb9d995d5a83bfcd38fa15b20000. URL is added below.
Addresses
0x000082cc936dbb9d995d5a83bfcd38fa15b20000
Meta Article URLs
<EMAIL_ADDRESS>

As mentioned in the issue template, this repository is not for reporting individual losses, only for large scale smart contract exploits. If you need support, please join the Revoke.cash Discord (see website footer for a link).


fix: simplify <head> management

This a draft and thus I will force-push in here.

I decided against the trick: https://github.com/vikejs/vike-react/pull/70/commits/e371912ad72d6a11b27dbc06600bdd5bc1a157a6. In order to keep vike-react as simple as possible (important for encouraging ejecting & forking).

to keep vike-react as simple as possible (important for encouraging ejecting & forking)

@AurelienLourot That's why I think it's best we release 0.4.0 and hard deprecate everthing. I will add migration notes to the changelog.
This PR now LGTM.
See https://vike.dev/head for what I believe to be the best design. This PR essentially aligns with https://vike.dev/head.

I just forced pushed to amend a BREAKING CHANGE: note.

Released as 0.4.0.

Happy to change things accordingly in vike-{vue,solid} and Bati.

That'd be great 🙏 (Feel free to let me know if you're busy I can also do it.)

on it now :)


Heapster sink events to InfluxDB

This implements the second part of #118 (follow up to PR #192).
Related Kubernetes Issues:

GoogleCloudPlatform/kubernetes/issues/4432
GoogleCloudPlatform/kubernetes/issues/5638

Screenshot showing events in InfluxDB (pulled by heapster from Kubernetes API server and pushed by heapster to influxdb):

Branched from #205
CC @vishh

Can one of the admins verify this patch?

@cadvisorJenkinsBot: ok to test

Integration tests pass when run locally:
--- PASS: TestHeapsterInfluxDBWorks (508.96s)
PASS
ok  	github.com/GoogleCloudPlatform/heapster/integration	508.996s

Looks like all recent Travis runs are failing with
The command "go get golang.org/x/tools/cmd/vet" failed and exited with 1 during .

Travis is now green

LGTM.


NIFI-9893 - Ensure orderly cluster node removal on node delete via UI

Description of PR
Alter order of steps executed when UI cluster node deletion is requested.  The node should be removed from the cluster state before any notifications are sent to the cluster participants.  This ensures that communications failures do not cause the operation to fail.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[X] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[X] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[X] Has your PR been rebased against the latest commit within the target branch (typically main)?

[X] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[X] Have you verified that the full build is successful on JDK 8?
[ ] Have you verified that the full build is successful on JDK 11?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.

Thanks @greyp9 changes look good to me. +1 merged to main


Remove VOLUME declaration from Dockerfile

These VOLUME lines are more trouble than they're worth. When building in CI, the build artifacts will not persist in the final image.

Thanks!


How to set http_proxy?

How can I set http proxy?
I'm getting SSL handshake error:
pkl-gen-go --help
panic: –– Pkl Error ––
	Exception when making request `GET<EMAIL_ADDRESS>	Error during SSL handshake with host `pkg.pkl-lang.org`:
	Connection reset

There's no way to directly configure an HTTP proxy on the pkl-gen-go CLI, but it looks like you may be able to specify one via a PklProject file. In a PklProject file:
evaluatorSettings {
  http {
    proxy {
      address = "proxy.example.com:80"
      noProxy { "internal.example.com"; "localhost" }
    }
  }
}

This file needs to be in the directory where you run pkl-gen-go, a parent directory, or in the directory specified by the --project-dir flag.


[API] - Undocumented response when import new policy from zip file

Problem description
In our API documentation, when a user sends policies/import/file the response should be 201 but currently request returns 200.
 Ticket is closed on April 26th


What is the status of this project, given the recent microsoft purchase announcement

I'd be lying if I said the future of Xray was 100% certain, but that's always been true. For the foreseeable future nothing is changing. It's full speed ahead. I'm still here and I'm still excited about this project.

Glad to hear it. That's about all I think I could fairly expect. I'm looking forward to seeing what this becomes.

No activity on this project since a month 😔Is it time to say THANK YOU for taking us with you on this wonderful journey?

@mofux indeed there have been progression on other branches such as on eon and refactor-builder, but it looks like there is a big slowdown on the development.

Focus shifted to eon, wich started as a part of xray: https://github.com/atom/eon

Yo. I know I've fallen on my face on the communication front. I'm still here, and realize these gaps undermine trust. I'm working actively on this project, and view the UI component as on pause while we focus deeper. I need to do a better job explaining the situation. I'll do another update early next week and make more of an effort to be consistent.


App crashes on launch

App version 1.10.4
Sagemcom gateway
iOS 17.4.1
iPhone 14 Pro Max
Every time I launch the app, it briefly (like, half a second) shows the login screen then crashes. I’ve rebooted my phone to the same result. Have not tried deleting/reinstalling the app. Screen recording attached.
https://github.com/zacharee/ArcadyanKVD21Control/assets/162072547/d8ee8feb-4c89-4802-b23e-3db5f54ae3f9

Does 1.10.5 work?

So far, so good. Thanks!


new calcs

Hello are you currently open to adding new calculators? I am happy to open a pull request for one some I use sometimes including Inflation-adjusted returns.

Hi @Ju66ernaut,
This library is always hungry for new methods. I merged your Inflation-adjusted PR.
Keep up the good work :)


Column profiler crashes when column contains lists

Traceback (most recent call last):
  File "/Users/arnov/Documents/code/project/src/utils/monitoring.py", line 20, in log_dataframe
    ylog.log_dataframe(df)
  File "/Users/arnov/.pyenv/versions/imputations/lib/python3.8/site-packages/whylogs/app/logger.py", line 569, in log_dataframe
    self._profiles[-1]["full_profile"].track_dataframe(df)
  File "/Users/arnov/.pyenv/versions/imputations/lib/python3.8/site-packages/whylogs/core/datasetprofile.py", line 293, in track_dataframe
    self.track(col_str, xi, character_list=None, token_method=None)
  File "/Users/arnov/.pyenv/versions/imputations/lib/python3.8/site-packages/whylogs/core/datasetprofile.py", line 229, in track
    self.track_datum(columns, data)
  File "/Users/arnov/.pyenv/versions/imputations/lib/python3.8/site-packages/whylogs/core/datasetprofile.py", line 247, in track_datum
    prof.track(data, character_list=None, token_method=None)
  File "/Users/arnov/.pyenv/versions/imputations/lib/python3.8/site-packages/whylogs/core/columnprofile.py", line 109, in track
    if pd.isnull(value):
ValueError: The truth value of an array with more than one element is ambiguous. Use a.any() or a.all()

The column looks like this:
df['codes']
0       [6420, 68204, 68203, 6832, 6810]
1                                 [6630]
2                          [4726, 47789]
3             [6420, 70102, 66292, 6612]
4             [6420, 70102, 64923, 6612]
                     ...
696                               [6420]
697    [6420, 70102, 64923, 70101, 6612]
698                              [70221]
699                        [49391, 4932]
700                [47713, 47712, 47711]
Name: codes, Length: 701, dtype: object

The problem is that pd.isnull() evaluates for each element of the list, and if tries to convert that to one boolean, which doesn't work

Thanks for the details, this was very helpful, I will get a small fix for this to not throw and release updated release with a fix.


switched to use static_path

Using static_path vs. static_url allows for the code to work despite the scheme of the website

Thanks, @erichulser. We've got a bit of work to do here fixing up the test suite, though.


Add 'public' parameter

This change allows the 'public' parameter to be passed in, which defines the job visibility level. It works at both a job level and a task level. More details here:
https://docs.saucelabs.com/reference/test-configuration/#job-visibility
Closes #77

yay :+1:


[BUG] Roblox Game Client just hanging in the background

Acknowledgement of preliminary instructions

[x] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.

What problem did you encounter?

after "starting roblox" it just disappears and makes a background process, i also do not have any windows insider builds or even in it. the normal roblox launcher works completely normal besides the bloxstrap one.

Do this please: https://github.com/pizzaboxer/bloxstrap/wiki/Uploading-your-Bloxstrap-configuration

Issue has been awaiting clarification for over a month, closing as stale. If you have anything further to add, just respond and I'll reopen.


"dotnet ef --help" does not display all possible options

"dotnet ef --help" command does not display all possible options that are listed in the documentation:
https://docs.microsoft.com/en-us/ef/core/miscellaneous/cli/dotnet
Is there any reason these commands are not listed? In my experience it hurts discoverability of possible options. It would be helpful to have them listed or provide a link to documentation.
Further technical details
EF Core version: 2.2.1-servicing-10028

What is missing?

Command flags mentioned in this site: https://docs.microsoft.com/en-us/ef/core/miscellaneous/cli/dotnet
For example:
--json
--context
--startup-project
--startup-project
--framework
--configuration
--runtime

@jaworek Those options are associated with specific commands, not with the top level ef. For example, as it says in the output shown above, to get info on migrations add:
C:\aspnet\EntityFrameworkCore>dotnet ef migrations add --help

Usage: dotnet ef migrations add [arguments] [options]

Arguments:
  <NAME>  The name of the migration.

Options:
  -o|--output-dir <PATH>                 The directory (and sub-namespace) to use. Paths are relative to the project directory. Defaults to "Migrations".
  --json                                 Show JSON output.
  -c|--context <DBCONTEXT>               The DbContext to use.
  -p|--project <PROJECT>                 The project to use.
  -s|--startup-project <PROJECT>         The startup project to use.
  --framework <FRAMEWORK>                The target framework.
  --configuration <CONFIGURATION>        The configuration to use.
  --runtime <RUNTIME_IDENTIFIER>         The runtime to use.
  --msbuildprojectextensionspath <PATH>  The MSBuild project extensions path. Defaults to "obj".
  --no-build                             Don't build the project. Only use this when the build is up-to-date.
  -h|--help                              Show help information
  -v|--verbose                           Show verbose output.
  --no-color                             Don't colorize output.
  --prefix-output                        Prefix output with level.

Thanks for the explanation.


Upgrade version.maven 3.8.5 -> 3.9.6 (minor)

This PR contains the following updates:

Package
Type
Update
Change

Maven API
compile
minor
3.8.5 -> 3.9.6

Maven
compile
minor
3.8.5 -> 3.9.6

Release Notes

apache/maven (Maven API)
v3.9.6: 3.9.6
Release Notes - Maven - Version 3.9.6
Improvement

[MNG-7939] - Allow to exclude plugins from validation

Dependency upgrade

[MNG-7913] - Upgrade Sisu version to 0.9.0.M2
[MNG-7934] - Upgrade Resolver version to 1.9.18
[MNG-7942] - Upgrade to parent POM 41
[MNG-7943] - Upgrade default plugin bindings

v3.9.5: 3.9.5
Release Notes - Maven - Version 3.9.5
Bug

[MNG-7851] - Error message when modelVersion is 4.0 is confusing

Improvement

[MNG-7875] - colorize transfer messages
[MNG-7895] - Support ${project.basedir} in file profile activation

Task

[MNG-7856] - Maven Resolver Provider classes ctor change
[MNG-7870] - Undeprecate wrongly deprecated repository metadata
[MNG-7872] - Deprecate org.apache.maven.repository.internal.MavenResolverModule
[MNG-7874] - maven-resolver-provider: introduce NAME constants.

Dependency upgrade

[MNG-7859] - Update to Resolver 1.9.16

v3.9.4: 3.9.4
Release Notes - Maven - Version 3.9.4
        Bug

[MNG-7846] -         endless loop in DefaultExceptionHandler.getMessage()

        Dependency upgrade

[MNG-7828] -         Bump guava from 31.1-jre to 32.0.1-jre

[MNG-7847] -         Upgrade to Resolver 1.9.14

Full Changelog: https://github.com/apache/maven/compare/maven-3.9.3...maven-3.9.4
v3.9.3: 3.9.3
Release Notes - Maven - Version 3.9.3
Bug

[MNG-7786] - Maven Plugin Validation message is misleading
[MNG-7795] - IllegalArgumentException: 'other' has different root during plugin validation
[MNG-7796] - Top directory cannot be computed
[MNG-7799] - Plugin validation falsely reports there are issues (but shows none)
[MNG-7811] - Plugins verification - reports are inconsistent
[MNG-7818] - [REGRESSION] maven improperly excludes hamcrest-core from junit
[MNG-7819] - Create IT that exercise file locking with snapshots

Improvement

[MNG-7698] - Allow comments in .mvn/maven.config
[MNG-7785] - Clean usage of SessionData
[MNG-7787] - Introduce new options for plugin validation
[MNG-7788] - Plugin Validation Report should be printed before build summary
[MNG-7789] - Plugin Dependency Validations use wrong data set
[MNG-7806] - Plugins verification - remove used in module(s) report
[MNG-7823] - Make plugin validation level parsing more consistent

Task

[MNG-5987] - Document the algorithm calculating the order of plugin executions inside a phase.
[MNG-7743] - Make the build work on JDK 20
[MNG-7790] - Update lifecycle plugins
[MNG-7791] - Split validation issues into "user actionable" and "plugin dev actionable"
[MNG-7797] - Return BRIEF mode, simply map it onto SUMMARY
[MNG-7807] - Update Super POM plugins

Dependency upgrade

[MNG-7800] - Upgrade to Maven Resolver 1.9.13
[MNG-7816] - Bump maven parent from 39 to 40

v3.9.2: 3.9.2
Release Notes - Maven - Version 3.9.2
Bug

[MNG-7750] - Interpolated properties in originalModel in an active profile.
[MNG-7759] - java.lang.NullPointerException at org.apache.maven.repository.internal.DefaultModelCache.newInstance (DefaultModelCache.java:37)

Improvement

[MNG-7712] - Core should issue a warning if plugin depends on maven-compat
[MNG-7741] - Add more information when using -Dmaven.repo.local.recordReverseTree=true
[MNG-7754] - Improvement and extension of plugin validation
[MNG-7767] - Tone down plugin validation report
[MNG-7778] - Maven should print suppressed exceptions when a mojo fails

Task

[MNG-7749] - Upgrade animal-sniffer from 1.21 to 1.23
[MNG-7774] - Maven config and command line interpolation

Dependency upgrade

[MNG-7670] - Upgrade misc dependencies
[MNG-7753] - Upgrade to Maven Resolver 1.9.8
[MNG-7769] - Upgrade to Maven Resolver 1.9.10

v3.9.1: 3.9.1
Release Notes - Maven - Version 3.9.1

Overview About the Changes
Regression fixes from Maven 3.9.0. General performance and other fixes.
Potentially Breaking Core Changes (if migrating from 3.8.x)

The Maven Resolver transport has changed from Wagon to “native HTTP”, see Resolver Transport guide.

Maven 2.x was auto-injecting an ancient version of plexus-utils dependency into the plugin classpath, and Maven 3.x continued doing this to preserve backward compatibility. Starting with Maven 3.9, it does not happen anymore. This change may lead to plugin breakage. The fix for affected plugin maintainers is to explicitly declare a dependency on plexus-utils. The workaround for affected plugin users is to add this dependency to plugin dependencies until issue is fixed by the affected plugin maintainer. See MNG-6965.

Mojos are prevented to boostrap new instance of RepositorySystem (for example by using deprecated ServiceLocator), they should reuse RepositorySystem instance provided by Maven instead. See MNG-7471.

Each line in .mvn/maven.config is now interpreted as a single argument. That is, if the file contains multiple arguments, these must now be placed on separate lines, see MNG-7684.

Bug

[MNG-7213] - StackOverflowError when version ranges are unsolvable and graph contains a cycle
[MNG-7544] - MavenMetadataSource#retrieve(MetadataResolutionRequest) does not check for null when reading from project map
[MNG-7676] - On Maven 3.9.0+ release, sha512 hashes have "null" classifier
[MNG-7677] - Maven 3.9.0 is ~10% slower than 3.8.7 in large multi-module builds
[MNG-7679] - [REGRESSION] Build fails when executing a single mojo without a POM
[MNG-7685] - Unable to ignore certificate errors with v3.9.0
[MNG-7693] - NPE in createModelCache, modelCacheFactory is null
[MNG-7697] - Cannot parse POM that contains an emoji in a comment
[MNG-7708] - Resolver in Maven 3.9+ no longer retries on a conection failure
[MNG-7709] - plexus-utils upgrade changes the way configuration is parsed
[MNG-7710] - Upgrade plexus-utils to 3.5.1
[MNG-7716] - ConcurrencyDependencyGraph deadlock if no root can be selected
[MNG-7717] - Maven warns wrongly about ${localRepository} expression
[MNG-7720] - [REGRESSION] Build order is incorrect and does not respect Reactor Build Order
[MNG-7721] - Maven 3.9 resolver ignores proxy configured via MAVEN_OPTS
[MNG-7726] - Maven 3.9.0 resolves properties in file profile activation incorrectly
[MNG-7731] - MNG-7520 incorrectly back ported to Maven 3.9.0

Improvement

[MNG-5185] - Improve "missing dependency" error message when _maven.repositories/_remote.repositories contains other repository ids than requested
[MNG-7686] - Speed up by replacing non-pattern #replaceAll() with #replace() or precompiled patterns
[MNG-7706] - Deprecate ${localRepository} mojo parameter expression

Task

[MNG-7197] - Simplify exit code handling in Windows command startup script
[MNG-7583] - Allow concurrent access to the MavenPluginManager
[MNG-7702] - Update to Maven Deploy Plugin 3.1.0
[MNG-7713] - Drop option legacy-local-repository
[MNG-7722] - Investigate GH Package Registry peculiarities

Dependency upgrade

[MNG-7695] - Upgrade to resolver 1.9.5
[MNG-7715] - Upgrade to Maven Resolver 1.9.6
[MNG-7723] - Upgrade to Maven Resolver 1.9.7
[MNG-7725] - Update surefire to 3.0.0 in default binding

v3.9.0: 3.9.0
Release Notes - Maven - Version 3.9.0
Sub-task

[MNG-7019] - Notify also at start when profile is missing
[MNG-7447] - Several Improvements by using Stream API

Bug

[MNG-5222] - Maven 3 no longer logs warnings about deprecated plugin parameters.
[MNG-6965] - Extensions suddenly have org.codehaus.plexus:plexus-utils:jar:1.1 on their classpath
[MNG-7055] - Using MINSTALL/DEPLOY 3.0.0-M1+ does not write plugin information into maven-metadata.xml
[MNG-7106] - VersionRange.toString() produces a string that cannot be parsed with VersionRange.createFromVersionSpec() for same lower and upper bounds
[MNG-7131] - maven.config doesn't handle arguments with spaces in them
[MNG-7160] - Extension And Classloaders: difference of result given extension types
[MNG-7316] - REGRESSION: MavenProject.getAttachedArtifacts() is read-only
[MNG-7352] - org.apache.maven.toolchain.java.JavaToolchainImpl should be public
[MNG-7413] - Fix POM model documentation confusion on report plugins, distribution repository and profile build
[MNG-7425] - Maven artifact downloads sometimes result in empty zip files in local repository
[MNG-7432] - [REGRESSION] Resolver session contains non-MavenWorkspaceReader
[MNG-7433] - [REGRESSION] Multiple maven instances working on same source tree can lock each other
[MNG-7441] - Update Version of (optional) Logback to Address CVE-2021-42550
[MNG-7448] - Don't ignore bin/ otherwise bin/ in apache-maven module cannot be readded
[MNG-7459] - Revert MNG-7347 (SessionScoped beans should be singletons for a given session)
[MNG-7471] - Resolver 1.8.0 introduces binary breakage in plugin using Resolver
[MNG-7487] - Fix deadlock during forked lifecycle executions
[MNG-7493] - [REGRESSION] Resolving dependencies between submodules fails
[MNG-7504] - Warning about unknown reportPlugins parameters for m-site-p are always generated
[MNG-7511] - Ensure the degreeOfConcurrency is a positive number in MavenExecutionRequest
[MNG-7515] - Cannot see a dependency tree for apache-maven module
[MNG-7529] - Maven resolver makes bad repository choices when resolving version ranges
[MNG-7545] - Multi building can create bad files for downloaded artifacts in local repository
[MNG-7563] - REGRESSION: User properties now override model properties in dependencies
[MNG-7564] - Potential NPE in MavenMetadataSource
[MNG-7568] - [WARNING] The requested profile "ABCDEF" could not be activated because it does not exist.
[MNG-7578] - Building Linux image on Windows impossible (patch incuded)
[MNG-7600] - LocalRepositoryManager is created too early
[MNG-7606] - Maven 3.9.0-SNAPSHOT cannot build Maven 4.0.0-SNAPSHOT
[MNG-7621] - Parameter '-f' causes ignoring any 'maven.config' (only on Windows)
[MNG-7624] - Plugins without non-mandatory goalPrefix are now logging incomplete info
[MNG-7637] - Possible NPE in MavenProject#hashCode()
[MNG-7644] - Fix version comparison where .X1 < -X2 for any string qualifier X
[MNG-7648] - Generated model reader is not setting location information
[MNG-7672] - Aggregate goals executed in a submodule forks the whole reactor

New Feature

[MNG-3655] - Allow multiple local repositories
[MNG-6270] - Store snapshots in a separate local repository
[MNG-7193] - Introduce MAVEN_ARGS environment variable
[MNG-7353] - Add support for "mvn pluginPrefix:version:goal"
[MNG-7391] - Add MojoExecution strategy and runner required by Maven Build Cache Extension
[MNG-7454] - Include resolver-transport-http in Maven
[MNG-7457] - Warn about deprecated plugin Mojo
[MNG-7464] - Warn about using read-only parameters for Mojo in configuration
[MNG-7468] - Unsupported plugins parameters in configuration should be verified
[MNG-7486] - Create a multiline message helper for boxed log messages
[MNG-7612] - Chained Local Repository

Improvement

[MNG-6609] - Profile activation by packaging
[MNG-6826] - Remove condition check for JDK8+ in FileSizeFormatTest
[MNG-6972] - Allow access to org.apache.maven.graph
[MNG-7068] - Active dependency management for Google Guice/Guava
[MNG-7350] - Introduce a factory for ModelCache
[MNG-7401] - Make MavenSession#getCurrentProject() using a thread local
[MNG-7438] - add execution id to "Configuring mojo xxx with basic configurator" debug message
[MNG-7445] - to refactor some useless code
[MNG-7463] - Improve documentation about deprecation in Mojo
[MNG-7474] - SessionScoped beans should be singletons for a given session
[MNG-7476] - Display a warning when an aggregator mojo is locking other mojo executions
[MNG-7478] - Improve transport selection for resolver
[MNG-7501] - display relative path to pom.xml
[MNG-7520] - Simplify integration of Redisson and Hazelcast for Maven Resolver
[MNG-7547] - Simplify G level metadata handling
[MNG-7561] - DefaultVersionRangeResolver should not try to resolve versions with same upper and lower bound
[MNG-7590] - Allow configure resolver by properties in settings.xml
[MNG-7608] - Make Resolver native transport the default in Maven
[MNG-7614] - Maven should translate transport configuration fully to resolver transports.
[MNG-7619] - Maven should explain why an artifact is present in local repository
[MNG-7645] - Implement some #toString() methods
[MNG-7651] - Simplify and document merge of maven.config file and CLI args
[MNG-7658] - CI-friendly versions should only come from/rely on user properties
[MNG-7666] - Update default binding and lifecycle plugin versions

Task

[MNG-6399] - Lift JDK minimum to JDK 8
[MNG-7452] - Remove JDK7 run on Maven 3.9.X Branch
[MNG-7466] - Align Assembly Descriptor NS versions
[MNG-7513] - Address commons-io_commons-io vulnerability found in maven latest version
[MNG-7523] - Back port MAVEN_ARGS to Apache Maven 3.9.0
[MNG-7556] - Clean up notion between user properties and system properties
[MNG-7618] - Use goalPrefix instead of artifactId to display mojos being executed
[MNG-7634] - Revert MNG-5982 and MNG-7417
[MNG-7636] - Partially revert MNG-5868 to restore backward compatibility (see MNG-7316)

Dependency upgrade

[MNG-6878] - Upgrade Guice to 4.2.3
[MNG-7247] - Upgrade Maven Resolver to 1.7.2
[MNG-7453] - Upgrade Maven Resolver to 1.8.0
[MNG-7488] - Upgrade SLF4J to 1.7.36
[MNG-7489] - Upgrade JUnit to 4.13.2
[MNG-7491] - Update parent POM to 36
[MNG-7499] - Upgrade Maven Resolver to 1.8.1
[MNG-7502] - Upgrade Guice to 5.1.0
[MNG-7506] - Upgrade Maven Wagon to 3.5.2
[MNG-7522] - Upgrade Maven Resolver to 1.8.2
[MNG-7530] - Upgrade Apache Maven parent POM to version 37
[MNG-7586] - Update Maven Resolver to 1.9.2
[MNG-7613] - Upgrade Apache Maven parent POM to version 38
[MNG-7641] - Upgrade Maven Wagon to 3.5.3
[MNG-7668] - Update Maven Resolver to 1.9.4
[MNG-7675] - Update Maven Parent to 39

v3.8.7: 3.8.7
Sub-task

[MNG-7019] - Notify also at start when profile is missing

Bug

[MNG-7106] - VersionRange.toString() produces a string that cannot be parsed with VersionRange.createFromVersionSpec() for same lower and upper bounds
[MNG-7316] - REGRESSION: MavenProject.getAttachedArtifacts() is read-only
[MNG-7352] - org.apache.maven.toolchain.java.JavaToolchainImpl should be public
[MNG-7529] - Maven resolver makes bad repository choices when resolving version ranges
[MNG-7563] - REGRESSION: User properties now override model properties in dependencies
[MNG-7568] - [WARNING] The requested profile "ABCDEF" could not be activated because it does not exist.
[MNG-7578] - Building Linux image on Windows impossible (patch incuded)
[MNG-7600] - LocalRepositoryManager is created too early
[MNG-7621] - Parameter '-f' causes ignoring any 'maven.config' (only on Windows)
[MNG-7637] - Possible NPE in MavenProject#hashCode()
[MNG-7644] - Fix version comparison where .X1 < -X2 for any string qualifier X

Improvement

[MNG-7590] - Allow configure resolver by properties in settings.xml
[MNG-7645] - Implement some #toString() methods

Task

[MNG-7513] - Address commons-io_commons-io vulnerability found in maven latest version
[MNG-7634] - Revert MNG-5982 and MNG-7417
[MNG-7636] - Partially revert MNG-5868 to restore backward compatibility (see MNG-7316)

Dependency upgrade

[MNG-7506] - Upgrade Maven Wagon to 3.5.2
[MNG-7641] - Upgrade Maven Wagon to 3.5.3

v3.8.6: 3.8.6
What's Changed

[MNG-7441] 3.8.x Update version of logback by @cstamas in https://github.com/apache/maven/pull/708
[MNG-7432] Resolver session contains non-MavenWorkspaceReader by @laeubi in https://github.com/apache/maven/pull/695
[MNG-7459] Revert "[3.8.x][MNG-7347] SessionScoped beans should be singletons for a given session" by @gnodet in https://github.com/apache/maven/pull/715
[3.8.x] [MNG-7476] Display a warning when an aggregator mojo locks other mojos executions by @gnodet in https://github.com/apache/maven/pull/736

Full Changelog: https://github.com/apache/maven/compare/maven-3.8.5...maven-3.8.6

[ ] If you want to rebase/retry this PR, check this box

Suggested commit message:
Upgrade Maven 3.8.5 -> 3.8.6

See https://github.com/apache/maven/compare/maven-3.8.5...maven-3.8.6

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.


Using the 'query' option

In the readme file where the items property is described there is a reference to a query property for those of us who would like to load the select box with non-local data. Is this feature not fully implemented - or is it not fully documented?

1

A quick search through the source code shows no reference to 'query' in that kind of way, so it's definitely not implemented.

This has confused me so much. please fix the documentation.

Any way to do this?


add code of conduct

use template from http://todogroup.org/opencodeofconduct/

see https://github.com/blog/2039-adopting-the-open-code-of-conduct

We should have some code of conduct, and http://todogroup.org/opencodeofconduct/ makes this easy. Do we want to add this?

@gwpenn :+1:'d via uproxy-eng → merging. (build failure is unrelated.)


always run require-pr-label-comment job

resolves #3688
Description
I tested a PR from a forked repository and GHA worked as expected except the feature to add a comment to the PR to request permission with write access to provide permission to run integration tests on the PR. This PR ensures this step always runs.
Checklist

[x] I have signed the CLA
[x] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[ ] I have updated the CHANGELOG.md and added information about my change to the "dbt next" section.

This doesn't actually work for permission reasons on PRs from forked repositories.


Ensure importer does not start when running tasks that import data

This should fix https://github.com/stellar/horizon/issues/99

Great job, thank you


Planning

Accept this update in order to let this file in the main branch and let people fill their tasks and

Hello, from my side, GitHub told me that this branch has conflicts that must be resolved. Is it a format problem? Because when I open this file I saw that the system includes all the content with a yellow column on the left.


Request Logging - Control Plane Spec

Proposal for request logging as initial discussed in community call.
From discussion with the Istio team it is suggested that request logging not be an istio addition but part of our application. A simple solution suggested is to add to Transformer. The base Transformer image will if request logging Sink is provided in spec send request and response to the sink.

Request Logging is an optional addition to Transformer spec.
It will be handled automatically by base python Transformer code.
If user only specifies requestLogging and no Transformer Custom container then the base Transformer code is run which will simply call Predictor and send request and response to Sink specified.

The Sink Object Reference is an Addressable Duck Type. It could be a Knative channel abstracting over a particular implementation, e.g. Kafka channel. It is the user's responsibility to ensure a valid Sink exists with the given ObjectReference.

This change is

Would love to hear some more details in the next weekly :)

Close as will create new PR for work.


no "troubleshooting" section or similar

There's no "troubleshooting" section nor does the page mention that a common error is the utterly infuriating "Error: the Project Cannot be Created". Indeed, I can't seem to find any documentation of this error that outlines common causes and potential solutions.

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

ID: d66bb4f9-c4f0-27be-f4f4-71e824844e25
Version Independent ID: f2be45ac-9863-3842-5bfd-8f7e65f984a3
Content: Create your first document-level customization for Word
Content Source: docs/vsto/walkthrough-creating-your-first-document-level-customization-for-word.md
Product: visual-studio-windows
Technology: office-development
GitHub Login: @John-Hart
Microsoft Alias: johnhart

@WilliamAntonRohm I've searched around for support for my issue and tried a few possible solutions. However, almost all references to this particular set of circumstances are from between 2012 and 2016, and there are hardly any replies to posts on this in the time since then. As I said, I've tried numerous proposed and accepted solutions to no avail so I think this is a different niche issue that has the same error message (which must be some sort of catch-all, but there's no obvious way to get more information).

@chrstfer it would really help if you could provide this feedback by using the Help > Send Feedback > Report A problem menu in Visual Studio.  Once you have done that let me know and I'll have someone help you.

We can drop this, there are better channels for actual support. I do think this and similar pages need a troubleshooting section, though.

#please-close


Compile benchmark directory

The benchmark directory was not compiling on a fresh checkout. Some of this was because of changes to the Google Caliper dependency, some to Breeze APIs in the "root" directories, some other.
The benchmark directory now compiles cleanly, locally.

sure that's great. I'm gonna merge this as-is  if you want to follow up with more PR's, please lmk!


Numerical SOAP derivatives for periodic systems

Hi,
as mentioned in issuer #95, for   deriv , desc = soap.derivatives(mol, ... ) the option of calculating SOAP derivatives for periodic systems periodic = True  is currently not available. I would be interested in this option and hoped  it could  be added in the future.

Hi,
Thank you for the suggestion. We will see what we can do, and try to get back to you in a few weeks.

We have made a plan to implement soap derivatives, both numerical and analytical, on periodic systems  (with some constraints). We will make an effort to finish it by the end of this year.

Hi,
I want to train the nn potential to predict energy and force for materials. However, when periodic = True, and the  derivatives are not realized. So, I hope the derivatives can be applied for materials in the future

Hey, would it be possible to use numerical derivatives for periodic systems if the lines 706 - 709 are deleted? I had tried it, and it worked, but I am not sure if I am not missing something

Could you try installing directly from branch v2.0.0? The numerical derivatives for periodic systems are implemented there, and will be made into a new release soon.

Now available in v2.0.0


ERROR: manifest for hyperledger/fabric-ca:latest not found: manifest unknown: manifest unknown
How do we install ?

@mttrbrts are those amazon images those you had built for a demo / tutorial a while back? Are they related to the HLF tutorial in the documentation? CC @dselman

I have a loader/tutorial I can add. One covers v1.4.6 of hlf , the other is written for hlf v2 (suitable for the hlf project) and builds on the new test network. Happy to contribute

Please follow the new guide, here: https://deploy-preview-309--accordproject-docs.netlify.app/docs/next/tutorial-hyperledger.html


Option to minimize networks and user settings?

Is your feature request related to a problem? Please describe.
When connected to multiple IRC networks and channels the list on the left side gets very long especially also because all the user setting links are always shown there.
Describe the solution you'd like
It would be nice if there was a small icon to collapse the network to a single line to temporarily hide all the channels in it. Similarly the user settings could be also temporarily collapsed by a button or so.
Thanks!

This should be fixed by @mostlyvirtual in #840.


HARP-7271: Tune the styling rules for the extruded buildings.

Show extruded buildings only when the zoom level is greater than 15.
Signed-off-by: Roberto Raggi<EMAIL_ADDRESS>

Codecov Report

Merging #815 into master will decrease coverage by 0.04%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #815      +/-   ##
==========================================
- Coverage   47.58%   47.53%   -0.05%
==========================================
  Files         235      224      -11
  Lines       21721    21521     -200
  Branches     4933     4904      -29
==========================================
- Hits        10336    10231     -105
+ Misses      11385    11290      -95

Impacted Files
Coverage Δ

@here/harp-mapview/lib/ThemeHelpers.ts
6.55% <0%> (-0.68%)
:arrow_down:

@here/harp-datasource-protocol/lib/Outliner.ts
100% <0%> (ø)
:arrow_up:

...ere/harp-materials/lib/LuminosityHighPassShader.ts
100% <0%> (ø)
:arrow_up:

...p-geoutils/lib/tiling/QuadTreeSubdivisionScheme.ts
100% <0%> (ø)
:arrow_up:

@here/harp-utils/lib/Mixins.ts
70% <0%> (ø)
:arrow_up:

@here/harp-materials/lib/CopyMaterial.ts
100% <0%> (ø)
:arrow_up:

...e/harp-geoutils/lib/tiling/MercatorTilingScheme.ts
100% <0%> (ø)
:arrow_up:

@here/harp-omv-datasource/lib/OmvTile.ts
50% <0%> (ø)
:arrow_up:

...ere/harp-geoutils/lib/projection/EarthConstants.ts
100% <0%> (ø)
:arrow_up:

...outils/lib/tiling/HalfQuadTreeSubdivisionScheme.ts
100% <0%> (ø)
:arrow_up:

... and 25 more

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 7f940e2...8aee96a. Read the comment docs.


Feature request: E2 Per player limits

Currently E2 doesn't have per player limits like SF, this means that limiting E2's on larger servers is incredibly annoying as you either give people few chips or a bunch of low quota chips which both will break peoples builds. So currently i have to choose between low single chip limits which breaks a lot of badly coded public E2's which sadly a large amount of people use or i lower the chip count which breaks a lot of long term builders their stuff as they tend to use lots of low powered chips.
Here's how SF does it https://github.com/thegrb93/StarfallEx/blob/ba765969401b4171ad22157b9a0f6ab69ac56dba/lua/starfall/instance.lua#L755

please add this bro

add this pls


[BUG] fields starting with __ is missing in the returned result when query by SQL with extra filter

What is the bug?
Fields starting with __ is missing in the returned result when query by SQL with extra filter.
How can one reproduce the bug?
Steps to reproduce the behavior:

Create an index with serval fields, some of them are starting with __. For example, an index test, contains a field whose name is '__time'.
Construct some document.
Query with the SQL select * from test and extra filter.

What is the expected behavior?
The result should contains __time.
What is your host/environment?

environment: docker.
version: 1.0.1、2.2.0
plugin: opensearch-sql

Do you have any screenshots?

Do you have any additional context?
It seems that the query is fallback to legacy sql engine. In this situation, when populating columns, it will ignore meta fields (starting with _).
https://github.com/opensearch-project/sql/blob/eeb90cf44d6031204e8bbab586f0c6dbf87ae81b/legacy/src/main/java/org/opensearch/sql/legacy/executor/format/SelectResultSet.java#L434-L480
https://github.com/opensearch-project/sql/blob/eeb90cf44d6031204e8bbab586f0c6dbf87ae81b/legacy/src/main/java/org/opensearch/sql/legacy/esdomain/mapping/FieldMapping.java#L95-L97

@yxwyoyoyo Thanks for reporting the issue! Your investigation is very helpful. In our engine v2, we did miss this support for identifier starting with underscore: https://github.com/opensearch-project/sql/blob/main/sql/src/main/antlr/OpenSearchSQLLexer.g4#L428
Could you elaborate a little your use case and if this kind of naming is required? Thanks!

@dai-chen In our use case, we provide service based on ES and open the ability to customize mapping. In addition, we have serval system fields to save meta data, so we preserve names start with __ as system fields. We also take other prefixes into consideration, but none of them were ideal.

@dai-chen In our use case, we provide service based on ES and open the ability to customize mapping. In addition, we have serval system fields to save meta data, so we preserve names start with __ as system fields. We also took other prefixes into consideration, but none of them were ideal.

Thanks for the info! Will evaluate if we can support this.

@dai-chen this issue can be closed as part of https://github.com/opensearch-project/sql/pull/1456
We now accept any field with __ or _ so long as the field is not reserved by OpenSearch.


feat(workload) create catalogue item

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

What is the current behavior? (You can also link to an open issue here)

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

We've tried to mirror the API routes as example directories, hence there is no route workload_catalogue_version. Can you please move the workload_catalogue_version files (keep the same file name) into the workload_catalogue directory?

Instead will move them all into the workloads folder to replicate the structure of the sdk


Implement izip! using .zip()s and single tupple-flattening .map()

This should probably enable vectorization-friendly specializations from std.
In theory, it's a breaking change, since it no longer returns multizip::Zip.

Thanks!

This should resolve the performance trouble with izip... Maybe it should be tested before it's merged though! itertools itself keeps some zip benchmarks on file (but they are kind of imperfect; I'm generally skeptical of leaning hard on the black_box function -- it blocks optimizations that are important as well.)
We still need to keep multizip and Zip to provide a named type for a multi zip, and to avoid too much breaking changes. I can update docs for them both to refer to each other and the details.

@bluss

itertools itself keeps some zip benchmarks on file

What does "on file" mean in this context? Haven't found anything for izip or multizip in the repo.
I've done quick test using the following bench:
#![feature(test)]

#[macro_use] extern crate itertools;
extern crate test;

use test::Bencher;
use test::black_box;

#[bench]
fn fmul_izip(b: &mut Bencher) {
    let aa: &[f32] = &[1.0; 1000];
    let bb: &[f32] = &[2.0; 1000];
    let cc: &mut [f32] = &mut[0.0; 1000];
    b.iter(|| {
        let aa = black_box(aa);
        let bb = black_box(bb);
        let cc = black_box(&mut *cc);
        for (a, b, c) in izip!(aa, bb, cc) {
            *c = *a * *b;
        }
    })
}

#[bench]
fn fmul_multizip(b: &mut Bencher) {
    let aa: &[f32] = &[1.0; 1000];
    let bb: &[f32] = &[2.0; 1000];
    let cc: &mut [f32] = &mut[0.0; 1000];
    b.iter(|| {
        let aa = black_box(aa);
        let bb = black_box(bb);
        let cc = black_box(&mut *cc);
        for (a, b, c) in itertools::multizip((aa, bb, cc)) {
            *c = *a * *b;
        }
    })
}

The results seem promising:
test fmul_izip     ... bench:          62 ns/iter (+/- 8)
test fmul_multizip ... bench:         798 ns/iter (+/- 49)

I can update docs for them both to refer to each other and the details.

So I should leave the docs as they are in this PR, right?

There's a heap of zip benchmarks in the benches/bench1.rs file. Not izip!(), but for other zips. Not editing docs more is fine.

We will have to treat this as a breaking change, we have to be careful with a lot of dependents.  We're going to add the #![no_std] breaker at the same time (which is much more of a theoretical case, about those using --no-default-features for a crate with no crate features...).

I'm sorry for taking the time here. Making a breaking update requires some more work, so I'll do the other stuff first.

Let's go! Thanks for writing this macro :-)


Make sure flash.keep is kept

Test if unobtrusive_flash clears the messages declared flash.keep, and fix if that's the case.

Looks like it is the case from my testing.


Prepare for releases

Hmm... I need to work out what's got a dependency on System.Linq.Async 5.1.0...

Got it - it's a common dependency. Unfortunately that means this PR needs to build everything...


Prisma error when migrating

Hi Prisma Team! The following command just crashed.
Command
db push
Versions

Name
Version

Platform
windows

Node
v20.3.0

Prisma CLI
4.16.2

Engine
4bc8b6e1b66cb932731fb1bdbbc550d1e010de81

Error
RustPanic: Error in migration engine.
Reason: [quaint\src\connector\result_set\result_row.rs:59:64] index out of bounds: the len is 1 but the index is 1

Hey @dakotadavis58, can you please:

try again with a recent Prisma version, e.g<EMAIL_ADDRESS>post your schema.prisma file
post which database you are using
describe the steps needed for us to reproduce this exact bug?

Thank you so much!

@dakotadavis58 please check Alberto's message above, we will soon close this issue without an answer.

Hey @dakotadavis58 ,
With the lack of information and our inability to reproduce this issue, we're now closing it. Feel free to comment if you have any updates about it.
Thank you 🙏


We are facing issue in Azure DevOps release pipeline in a pne of the task to install cloud Foundry CLI

(https://github.com/cloudfoundry/cli/assets/140050817/321b33c7-2d03-49be-a04c-464e7a56c6a3)
Please fill out the issue checklist below and provide ALL the requested information.

[ ] I reviewed open and closed github issues that may be related to my problem.
[ ] I tried updating to the latest version of the CF CLI to see if it fixed my problem.
[ ] I attempted to run the command with CF_TRACE=1 to help debug the issue.
[ ] I am reporting a bug that others will be able to reproduce.

Describe the bug and the command you saw an issue with
Provide details on what you were trying to do (and why).
What happened
Getting error in Cloud Foundry CLI installation. that certificate has expired. Please check it on priority.
Expected behavior
Cloud foundry CLI version 8 should get updated
Exact Steps To Reproduce
Steps to reproduce the behavior; include the exact CLI commands and verbose output:

Run cf ...
Bind a service cf bind-service
See error

Provide more context

platform and shell details ( e.g. Mac OS X 10.11 iTerm)
version of the CLI we were using is 6.43.0 and we want to update it version 8 now
version of the CC API Release you are on

Notes regarding V6 and V7 CLI support:

V6:

Minimum supported version of CF Deployment: v7.0.0 (CAPI Release: 1.74.0 (APIs 2.128.0 and 3.63.0))
Maximum supported version of CF Deployment: v13.4.0 (CAPI Release: 1.94.0 (APIs 2.149.0 and 3.84.0))

V7:

Minimum supported version of CF Deployment: v13.5.0 (CAPI Release: 1.95.0 (APIs 2.150.0 and 3.85.0))

Hello,
What version of CLI are you using? we currently only support v7 and v8 lines.
Thanks
Joao

We also did had some networking and cert issues around those dates. Is this still happening? or was it temporary?

I'm resolving this issue for now, but please don't hesitate to reopen it if you have any more questions or comments.


Add fastdom js dependency

The nvd3 docs say that it if the fastdom library is present it makes use
of it.
"Including Fastdom in your project can greatly increase the performance
of the line chart (particularly in Firefox and Internet Explorer) by
batching DOM read and write operations to avoid layout thrashing. NVD3
will take advantage of Fastdom if present."
Annectodal evidence refreshing a 4*nvd3 slices dashboard before/after fastdom

Oh makes sense, I assumed the lib could just be discovered and used as it would in Python, but that's actually not the case with JS/Webpack. So I'm guessing we have to import it explicitly.


Global object registry for common chrome components

Today, we use a module level cache to store things like BTN_BACK and BTN_NEXT as global references that can be imported from child screens to manipulate the labels and some limited attributes. This pattern doesn't feel like it's the best approach and I'd like to spend time finding a better way to surface items like this, from the parent view, that needs to be shared around each child screen.

I had some ideas, can we have something like components with shared provider to achieve better DX?

Do you have a brief example you could share?

Do you have a brief example you could share?

in web frontend world we usually do something like this:
Parent
<script>
export default {
  data() {
    return {
      btnBack: null,
      btnNext: null,
    }
  },
  provide() {
    return {
      setBtnBack: this.setBtnBack,
      setBtnNext: this.setBtnNext
    }
  },
  methods: {
    setBtnBack(data) {
      this.btnBack = data;
    },
    setBtnNext(data) {
      this.btnNext = data;
    }
  }
}
</script>

<template>
  <div :setBtnBack="setBtnBack" :setBtnNext="setBtnNext"></div>
</template>

Index
<template>
  <Parent>
    <Child>
       <!-- This child will then use those methods -->
    </Child>
  </Parent>
</template>

i think this is called provide/inject, in python and gtk we could create our own widget maybe, that provides this functionality?

I this the new design resolved this please correct me if i am wrong.