Blackburne Shilling Kostić?

Re naming of the below:
a) C50 Blackburne Shilling Gambit 1. e4 e5 2. Nf3 Nc6 3. Bc4 Nd4 4. Nxe5 Qg5 5. Nxf7 Qxg2 6. Rf1 Qxe4+ 7. Be2 Nf3#
b) C50 Italian Game: Schilling-Kostic Gambit 1. e4 e5 2. Nf3 Nc6 3. Bc4 Nd4
I believe the legend behind this is that Blackburne played games for a shilling using this line.
Looking around the web, it sounds like in version b), "Schilling" comes from a misunderstanding that "shilling" was a name.
Borislav Kostić was apparently the person who actually played the line in recorded games.
If this is accurate, either "Blackburne Shilling-Kostić", or "Blackburne-Kostić", or "Kostić" would make sense as the name for b), and likely the middle one strikes the right balance between accuracy and common usage.
Also note the name is spelled Kostić, not Kostic.
A separate issue is whether the current a) entry makes sense as an inclusion in the opening database given it's a full game and a "mainline" extension of b)?
If it should be kept, it would sound like a) should be classified along the lines of: "Italian Game: Blackburne-Kostić Gambit, Blackburne Shilling Variation" to make it consistent.
Therefore I would propose to change the names as follows:
a) to "Italian Game: Blackburne-Kostić Gambit, Blackburne Shilling Variation"
b) to "Italian Game: Blackburne-Kostić Gambit"
Relevant wikiepedia entry: https://en.wikipedia.org/wiki/Blackburne_Shilling_Gambit

Thanks! I have removed (a), adjusted (b) as you recommended, and fixed the spelling of Kostić in one other entry.

Thanks so much, appreciated!
I have a few other observations, I will try to submit as PRs so it's less hassle for you.


[QUESTION]: module 'google.protobuf.descriptor' error

Is your question answered elsewhere?

[X] searched the existing issues.
[X] asked MilMil.
[X] read the documentation.

What is your question?
When running hello_milvus.py on an Ubuntu 20.04 system I got:
AttributeError: module 'google.protobuf.descriptor' has no attribute '_internal_create_key'

Anything else?
I checked the version of protobuf installes:
$ pip3 show protobuf
Name: protobuf
Version: 3.6.1
Summary: Protocol Buffers
Home-page: https://developers.google.com/protocol-buffers/
Author: None
Author-email: None
License: 3-Clause BSD License
Location: /usr/lib/python3/dist-packages
Requires:
Required-by: grpcio-tools

I then checked the version required by pymilvus by looking in requirements.txt:
protobuf==3.17.1

The needed version was much newer than the installed version, so I upgraded with pip:
pip install --upgrade protobuf

Verified the upgrade:
$ pip3 show protobuf
Name: protobuf
Version: 3.19.4
Summary: Protocol Buffers
Home-page: https://developers.google.com/protocol-buffers/
Author: None
Author-email: None
License: 3-Clause BSD License
Location: /home/efm/.local/lib/python3.8/site-packages
Requires:
Required-by: grpcio-tools

And then was able to successfully run hello_milvus.py

Hi @evelynmitchell , Thank you for your report. I have update this issue to PyMilvus FAQ via https://github.com/milvus-io/pymilvus/pull/886, and it will soon be on https://milvus.io/api-reference/pymilvus/v2.0.0/faq.html.


[Input]: Support `color=inherit' to input base component

[x] Label color is inheriting
[ ] Border color is inheriting

Fixes #16278

[x] I have followed (at least) the PR section of the contributing guide.

@oliviertassinari By this approach, label color is changing but border-color is not able to change. Any suggestions?

It's not possible, the input text color is already applied to the parent, to ease customizability.


Treatment of 'kind' in the parser

I implemented treatment of special word kind similarly to treatment of role. But I don't really understand why role and family are treated differently:
-- Note that 'role', 'family' and 'kind' get lexed separately regardless of
-- the use of extensions. However, because they are listed here, this
-- is OK and they can be used as normal varids.
-- See Note [Lexing type pseudo-keywords] in Lexer.x
varid :: { Located RdrName }
        : VARID            { sL1 $1 $! mkUnqual varName (getVARID $1) }
        | special_id       { sL1 $1 $! mkUnqual varName (unLoc $1) }
        | 'unsafe'         { sL1 $1 $! mkUnqual varName (fsLit "unsafe") }
        | 'safe'           { sL1 $1 $! mkUnqual varName (fsLit "safe") }
        | 'interruptible'  { sL1 $1 $! mkUnqual varName (fsLit "interruptible")}
        | 'forall'         { sL1 $1 $! mkUnqual varName (fsLit "forall") }
        | 'family'         { sL1 $1 $! mkUnqual varName (fsLit "family") }
        | 'role'           { sL1 $1 $! mkUnqual varName (fsLit "role") }
        | 'kind'           { sL1 $1 $! mkUnqual varName (fsLit "kind") }

-- These special_ids are treated as keywords in various places,
-- but as ordinary ids elsewhere.   'special_id' collects all these
-- except 'unsafe', 'interruptible', 'forall', 'family', and 'role',
-- whose treatment differs depending on context
special_id :: { Located FastString }
special_id
        : 'as'                  { sL1 $1 (fsLit "as") }
        | 'qualified'           { sL1 $1 (fsLit "qualified") }
        | 'hiding'              { sL1 $1 (fsLit "hiding") }
        | 'export'              { sL1 $1 (fsLit "export") }
        | 'label'               { sL1 $1 (fsLit "label")  }
        | 'dynamic'             { sL1 $1 (fsLit "dynamic") }
        | 'stdcall'             { sL1 $1 (fsLit "stdcall") }
        | 'ccall'               { sL1 $1 (fsLit "ccall") }
        | 'capi'                { sL1 $1 (fsLit "capi") }
        | 'prim'                { sL1 $1 (fsLit "prim") }
        | 'javascript'          { sL1 $1 (fsLit "javascript") }
        | 'group'               { sL1 $1 (fsLit "group") }

test if kind can be used as a type variable


Array slice initialization with implicitly castable type

bearophile_hugs reported this on 2013-01-20T15:36:26Z
Transfered from https://issues.dlang.org/show_bug.cgi?id=9363
CC List

andrej.mitrovich

Description
This code works:

import std.typecons: Typedef;
alias Typedef!(int[]) MyArray;
void main() {
    MyArray arr;
    arr.length = 10;
    arr[] = 0;
}

While this:

import std.typecons: Typedef;
alias Typedef!(ubyte[]) MyArray;
void main() {
    MyArray arr;
    arr.length = 10;
    arr[] = 0;
}

Gives (dmd 2.062alpha):

...\dmd2\src\phobos\std\typecons.d(2811): Error: cannot implicitly convert expression (v) of type int to ubyte[]
temp.d(6): Error: template instance std.typecons.Typedef!(ubyte[], null).Typedef.Proxy!(Typedef_payload).opSliceAssign!(Typedef!(ubyte[], null), int) error instantiating

andrej.mitrovich commented on 2013-01-21T07:36:05Z
std.typecons.Proxy is really poorly designed. Essentially every possible operator is shoved in there without doing any sort of check on what is being wrapper (except for the one check for classes).

Btw please don't use the Platform field unless it's a platform-specific bug, thanks.

bearophile_hugs commented on 2013-01-21T09:15:34Z
(In reply to comment #1)

> Btw please don't use the Platform field unless it's a platform-specific bug,
> thanks.

The Platform tag was set to Windows because the error message that I have put here comes from Windows. It doesn't mean it's a Windows-only problem.

andrej.mitrovich commented on 2013-01-21T07:36:32Z
(In reply to comment #1)
> wrapper

I mean wrapped.


Add documentation for HTTP/2

The underlying servlet container supports HTTP/2, but the Trellis documentation does not describe how to configure it. This information should be added to the README and possibly also to Trellis wiki page.

Moved to https://github.com/trellis-ldp/trellis-rosid/issues/3


onDone event fires right after opening a file

The logs below explain it best.
I'm super confused and tried everything.
OmxInstance open() for layer # 0 holdMode? undefined
finalOpenCommand: omxplayer "./media/atmo.mp3" -o local --no-keys --no-osd --dbus_name org.mpris.MediaPlayer2.omxplayer_layer0 < omxpipe0
onDone event
onStart event
20:18:14 - info: on Start triggered (My logging, safe to ignore)
waitTillPlaying()
getplaystatus success after 476ms, 21 attempts: Paused

confirmed started ok
onStart event
getplaystatus success after 487ms, 21 attempts: Paused

getplaystatus success after 507ms, 21 attempts: Playing

getplaystatus success after 527ms, 21 attempts: Playing

getplaystatus success after 549ms, 21 attempts: Playing

getplaystatus success after 569ms, 21 attempts: Playing

getplaystatus success after 591ms, 21 attempts: Playing

getplaystatus success after 629ms, 21 attempts: Playing

getplaystatus success after 641ms, 21 attempts: Playing

The issue isn't there when adding the module from git directly. Any chance NPM is behind in versions?


Unit tests!

Unit tests using the mock AmazonFoo client will go a long way towards guaranteeing the core implementation is (and stays!) correct without having to rely totally on slow and potentially-expensive integration tests that actually provision resources from AWS. Write them and hook up some automation to run them regularly.
Comment here if you'd like to see this prioritized, but there's absolutely no way this project will make it to 1.0 until this gets resolved.

It has been a puzzle to me for a while how do you test the aws-java-sdk internally because there are almost no tests in the public repo.


Roll Plugins from 6d88e3a2a184 to 3daf0b7f14c5 (3 revisions)

https://github.com/flutter/plugins/compare/6d88e3a2a184...3daf0b7f14c5
2022-02-23<EMAIL_ADDRESS>Roll Flutter from 3b05d806222a to c74a646b7bba (21 revisions) (flutter/plugins#4913)
2022-02-23<EMAIL_ADDRESS>[in_app_purchase] Updates the dependency on in_app_purchase_storekit. (flutter/plugins#4910)
2022-02-23<EMAIL_ADDRESS>Roll Flutter from 617de911982a to 3b05d806222a (2 revisions) (flutter/plugins#4905)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-plugins-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


Support URL in ModelConfig

When using an OpenAI-API-compatible API provider (like Azure) to generate embeddings, you need to be able to specify the URL of the service.

let schema = {
  "name": "products",
  "fields": [
    {
      "name": "product_name",
      "type": "string"
    },
    {
      "name": "embedding",
      "type": "float[]",
      "embed": {
        "from": [
          "product_name"
        ],
        "model_config": {
          "model_name": "openai/text-embedding-ada-002",
          "api_key": "your_api_key_as_required_by_the_custom_provider",
          "url": "https://your-custom-openai-compatible-api.domain.com"
        }
      }
    }
  ]
};

client.collections('products').create(schema);

This PR adds the URL property to the ModelConfig.

Hi @dejonghee, looks good and thanks for the contribution! :+1:

@dejonghee this has now been released with version 7.8.0.


please add some news commands that will provide news when called

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

https://api.zeks.me/api/foxnews?apikey=apivinz


Add Form Component with Docked Footer Support

Since InlineEdit is going to be deprecated. The form editing pattern is a Popover/Edit icon button for single input fields and the SLDS Form Edit mode for multiple field forms.
I propose creating a <Form> component that wraps form elements and allows adding a Docked Form Footer. The following is a mockup. Docked Footer should always be paired with Read/Edit mode of forms.

Consumers would still need to update inputs from read only variants to base inputs themselves, but I'm open to suggestions. I would be difficult to pass a prop down into the inputs directly since they may be nested in formatting. This might be a place to use React's context?
The primary issue with Docked Form footer is that it might need to be fixed to the bottom of the page and not scroll.
I need additional input from stakeholders.

As a FYI...I need to share/discuss the visual aspects of this with Alan on the SLDS team. I will reach out to him next week.

Hi @kwilloughby @interactivellama
Would be glad to help out this issue 😄 Are there any updates discussed offline for the direction for this issue?

This needs a props proposal with some sample example JSX. I recommend throwing together some non-working JSX of what would be in the examples first. That is mockup of https://www.lightningdesignsystem.com/components/form-element/#View-Mode and of https://www.lightningdesignsystem.com/components/form-element/#Edit-Mode
This would also add a DockedFooter component (that also needs a props proposal) that would put passed into a prop of the RecordForm component. The form component would have an edit and view mode. The RecordForm could have any children (since it could be one column, two column, etc), but all the inputs inside of it in the example would switch between a readonly mode like <Input variant="read-only"/> and the base <Input />. It would be fine to ask the consumer developer to manage the view and edit modes of the child inputs, since are some complex examples like a mailing address might get changes from simple text to 5 inputs when in edit mode.

What you don't see in the examples unfortunately, is that DockedFooter https://www.lightningdesignsystem.com/components/docked-form-footer/ his fixed to the bottom of the form and does not move on scroll. If the RecordForm does off the page, the DockedFooters sits on the bottom of the page. If the form doesn't go off the page, then it sits at the bottom of the form HTML element.


Add missing F-key bindings for xkb and Windows.

With keyboard-types 0.7, we have additional F-keys that can be mapped when using xkb.
On Windows, we had not fully added mappings for some F13-F24.
I haven't found scan codes yet for the F25-F35 keys.

Is there evidence that these keys even exist?

Assuming you mean F25-F35, xkb has stuff for them, winit does as well, and the winit folks asked that these get added to keyboard-types.
My keyboards are (apparently) rather dull and don't have anything past F12.

In trying some things out, I've found at least a couple of bugs in other code in Glazier ...


How to fix the clean problem in realbasicvsr

I used realbasicvsr for super-resolution my own video, bug got this result:

A lot of detail has lost and result is nearly like a cartoon picture。
My question is what lead to this problem? How to adjust the training config to fix it?
My model config is realbasicvsr_c64b20_1x30x8_lr5e-5_150k_reds

What is the size (in pixel) of these persons? Are they too small on the cavans?

the picture is 540x960, maybe these persons size is 20x50. And the more urgent questions is the picture is like a carton picture

Seems to be a intrinsic issue of RealBasicVSR itself, you can check #877 for reference.

Closing due to inactivity, please reopen if there are any further problems.


Can't make Swarm talk to etcd when TLS (--discovery-opt) is enabled

Hello,
I just can't make swarm manager connect to a TLS-protected etcd. Everything works flawlessly without TLS, but as soon as I add security - nothing works.
The problem is, I don't know how to diagnose - all I see (with --debug) is only three lines repeating ad infinitum:
time="2016-08-19T22:55:15Z" level=error msg="Leader Election: watch leader channel closed, the store may be unavailable..."
time="2016-08-19T22:55:16Z" level=info msg="Leader Election: Cluster leadership lost"
time="2016-08-19T22:55:16Z" level=error msg="client: etcd cluster is unavailable or misconfigured"

My setup:

I'm prototyping Ansible-based Docker Swarm deployment in a Vagrant Ubuntu 16.04 boxes (running Docker 1.12.1, although I doubt it's relevant at this stage). I've tried to slim down my setup to a relatively small demonstrable test case in this repo - there's a Vagrant box that replicates my issue, with all the steps documented in README.md.

etcd is running in a Docker container, image quay.io/coreos/etcd:v2.3.3, ports 4001 and 7001 mapped to the same ports on the host, and etcd is ran with the following command (entrypoint already implies etcd binary):
--name discovery
--advertise-client-urls 'https://<IP_ADDRESS>:4001'
--listen-client-urls 'https://<IP_ADDRESS>:4001'
--listen-peer-urls 'https://<IP_ADDRESS>:7001'
--trusted-ca-file '/etc/ssl/ansible-pki/ca.pem'
--cert-file '/etc/ssl/ansible-pki/testbox.pem'
--key-file '/etc/ssl/ansible-pki/testbox.key'
--client-cert-auth
--peer-trusted-ca-file '/etc/ssl/ansible-pki/ca.pem'
--peer-cert-file '/etc/ssl/ansible-pki/testbox.pem'
--peer-key-file '/etc/ssl/ansible-pki/testbox.key'
--peer-client-cert-auth

swarm is started with port 4000:4000 mapping and the following command:
  --debug manage -H :4000 --advertise <IP_ADDRESS>:4000
  --replication
  --tlsverify
  --tlscacert /etc/ssl/ansible-pki/ca.pem
  --tlscert /etc/ssl/ansible-pki/testbox.pem
  --tlskey /etc/ssl/ansible-pki/testbox.key
  --discovery-opt kv.cacertfile=/etc/ssl/ansible-pki/ca.pem
  --discovery-opt kv.certfile=/etc/ssl/ansible-pki/testbox.pem
  --discovery-opt kv.keyfile=/etc/ssl/ansible-pki/testbox.key
  etcd://<IP_ADDRESS>:4001

For the both containers, all certificates and keys are mapped from the host as /etc/ssl/ansible-pki:/etc/ssl/ansible-pki:ro volume (I'm aware about ca.key being exposed to the container)

I'm positive, etcd TLS is working correctly. I can confirm this with  echo "GET /" | openssl s_client -connect <IP_ADDRESS>:4001 -CAfile /etc/ssl/ansible-pki/ca.pem -cert  /etc/ssl/ansible-pki/testbox.pem -key /etc/ssl/ansible-pki/testbox.key
I've tried to toy with certificates (tried both ECDSA and RSA, switched between IP or hostname for CN, toyed around with SANs, enabled and disabled various extensions), but all my attempts were futile. I've also tried to use different keys for etcd's server and swarm's client (instead of one) - but this also hadn't worked. I'm always getting the same exact error.
As soon as I remove --trusted-ca-file and all its following options from etcd, and remove --discovery-opt from swarm (i.e. completely disable TLS), things work. I believe --discovery-opts are properly recognized, as swarm doesn't connect to a non-TLS etcd whon those specified, and the logs indicate this from the very first lines:
time="2016-08-20T00:23:05Z" level=debug msg="Initializing discovery service" name=etcd uri="<IP_ADDRESS>:4001"
time="2016-08-20T00:23:05Z" level=info msg="Initializing discovery with TLS"
time="2016-08-20T00:23:05Z" level=debug msg="Trusting certs with subjects: [0:1\x120\x10\x06\x03U\x04\n\f\tACME Inc.1$0\"\x06\x03U\x04\x03\f\x1bLocal Certificate Authority]"

(There's absolutely nothing else of interest in the container logs, besides this. "Initializing ...", then "Registering HTTP route", then "Listening for HTTP" and then the 3 error lines repeating.)
I'm not sure what I'm doing wrong, and, unfortunately, documentation is somewhat scarce on the subject (or I'm looking at all the wrong places). Please forgive me if I'm missing something obvious!
Can someone please help me to diagnose the problem further and, hopefully, resolve it?
Thanks!

Did some shotgun debugging with log.Printf around the etcd's client.go and finally found the cause.
SimpleHTTPClient.Do fails with "x509: cannot validate certificate for <IP_ADDRESS> because it doesn't contain any IP SANs". My mistake was using DNS:<IP_ADDRESS> in [subjectAltName] while it must've been IP:<IP_ADDRESS> instead. And seems that CN with IP address doesn't mean a thing. Everything makes sense now.
While the failure's all mine here, I'd still suggest to make discovery client errors more prominent (when available), at least when --debug option is passed.
I'm not sure this is entirely possible and whenever etcd (and other) client libraries would return the meaningful and well-printable errors to swarm (I haven't found where client is actually called in the swarm's code) - but if it does, I'd urge to please add some log statements.
Thanks!


Acceptable Use Policy

Closes https://github.com/r-multiverse/help/issues/88.
This document is designed to protect Administrators and Moderators from Content and Behaviour of Contributors and Users. It references the Code of Conduct.
This is as distinct from the Terms of Use, which is designed to protect Administrators, Moderators and Contributors from claims by Users.
A combination of the Terms of Use, this AUP, and the Code of Conduct creates a multi-layered approach that is more comprehensive than relying on a single document.
Review and comments welcome.

most naive comments ever

Thanks for the review! naive is good!

Another thing, actually: we have "Terms of Use" and "Acceptable Use", which sound similar because of the word "Use". Maybe this one could be called "Terms of Service" and then the definitions section defines "Service".


fix: apply correct markup to select

Summary
Fixes #918

Test Plan
Manual test on local machine

Thanks! I'm actually surprised we haven't ran into more of these since it was extremely hard to track it down.


How to invoke TronLink to sign a transaction that has already been signed by someone else and broadcast it to the blockchain?

How to invoke TronLink to sign a transaction that has already been signed by someone else and broadcast it to the blockchain?

You could use tron.tronWeb.trx.multiSign() function which is
exposed by TronLink wallet to sign your transaction. Then use tron.tronWeb.trx.sendRawTransaction(signedTranscation) to broadcast it to the blockchain.


Remove parsing capabilities

Parsing data from string to Dataset becomes the responsibility of the lib's users.
Will fix conflicts with #8 once one of the PRs is merged.

I'm not sure I understand your comment. What does "it's no longer just a graph but a dataset" mean?


Scaling and UV flip fixed.

SonarQube analysis reported 1 issue
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 AncientFungus:LGEPR: Cppcheck cannot find all the include files (use --check-config for details)

SonarQube analysis reported 2 issues
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 AncientFungus:LGEPR: Cppcheck cannot find all the include files (use --check-config for details)
 Hymn.cpp#L177: Variable 'model' is assigned a value that is never used.

After a dice roll with chainsawkitten, the code standard is without bracers.

SonarQube analysis reported 2 issues
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 AncientFungus:LGEPR: Cppcheck cannot find all the include files (use --check-config for details)
 Hymn.cpp#L175: Variable 'model' is assigned a value that is never used.

SonarQube analysis reported 2 issues
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 AncientFungus:LGEPR: Cppcheck cannot find all the include files (use --check-config for details)
 Hymn.cpp#L177: Variable 'model' is assigned a value that is never used.


Fix license clause

@jh-bate

LGTM just double checked based on this http://tidepool.org/2013/12/19/tidepool-license-update/


Add types to axes in lax_numpy.

I have mixed feelings about adding annotations in a couple of cases where the code needed changes to work around mypy.

Looks good, although I agree that it's a bit unfortunate that satisfying mypy forces changes that arguably make the code less clear...

Looks good, although I agree that it's a bit unfortunate that satisfying mypy forces changes that arguably make the code less clear...


[CT-2286] [Bug] return behaves in unexpected ways when used within a call tag / block

Is this a new bug in dbt-core?

[X] I believe this is a new bug in dbt-core
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
When I try to use return() from within a call block, I get an error.
Example:
# macros/something.sql:
{% macro callable() %}
  {% do print(caller()) %}
{% endmacro %}

# models/something.sql
{% call callable() %}
     {% do return([1, 2, 3]) %}
{% endcall %}

dbt compile
Observed: TypeError: sequence item 9: expected str instance, list found
Expected Behavior
I expect the value passed to return() to be returned by the call to caller() . In this particular case, I expect it to print [1, 2, 3]
Steps To Reproduce
# macros/something.sql:
{% macro callable() %}
  {% do print(caller()) %}
{% endmacro %}

# models/something.sql
{% call callable() %}
     {% do return([1, 2, 3]) %}
{% endcall %}

dbt compile
Relevant log output
No response
Environment
- OS: Linux
- Python: Python 3.10.9
- dbt:
dbt --version
Core:
  - installed: 1.4.4
  - latest:    1.4.4 - Up to date!

Plugins:
  - bigquery: 1.4.1 - Up to date!
  - postgres: 1.4.4 - Up to date!

Which database adapter are you using with dbt?
postgres, bigquery
Additional Context
This part in the code looks suspicious :)
https://github.com/dbt-labs/dbt-core/blob/main/core/dbt/exceptions.py#L18
class MacroReturn(builtins.BaseException):
    """
    Hack of all hacks
    This is not actually an exception.
    It's how we return a value from a macro.
    """

Thanks for reaching out @darist !
You found a true (not so hidden) gem in our codebase with the MacroReturn class 💎
Could you tell me more about what you are trying to do? I can't really tell, so I rewrote it a bit to try to do some similar things.
Could you try this and see how it works for you?
# macros/something.sql:
{% macro callable() %}
    {% do return([1, 2, 3]) %}
{% endmacro %}

# models/something.sql
-- print the result of the callable() macro
{{ callable() }}

{% set result = callable() %}

-- print the result the return value of the callable() macro
{{ result }}

-- iterate through the results and print each item
{% for i in result %}
    {{ i }}
{% endfor %}

Sure thing @darist 👍
I took a look -- that's some impressive dark magic you are working on 🧙
I think return() will only work with macros and not within {% call %} bodies. For the case where it appeared to work, my guess is that it didn't actually reach the return() -- maybe mock_fn is always defined?
Anyways, I don't think is a bug -- we expect macros to be able to return values, but we don't expect the same for call blocks.
I don't have any great suggestions for workarounds, but have faith that you'll figure out something clever now that you know how it's expected to behave. 🧠
I'm going to close this as "not planned" since we don't plan on adding this ability to call blocks.

oh no! I'm having to do a lot of business logic in jinja, which is pretty painful. Being able to define anonymous macros "on the fly" and associate them with the data they manipulate (so we can program like we do with structs or objects) would be helpful. Would you be open to contributions to enable support of return from call blocks?
Actually, I'd prefer to be able to implement macros in Python. Jinja is not really designed as a programming language, but I'm using (abusing?) it that way because dbt locks us out of the Python side of the jinja context. Are there any plans or discussions around supporting Python implementations of macros?
Cheers!


hex_to_rgb: invalid hex_str: normal

modes.nvim not working.

My config:
--- init.lua
vim.o.cursorline = true

-- modes.lua
require('modes').setup({
  colors = {
    copy = "#f5c359",
    delete = "#c75c6a",
    insert = "#78ccc5",
    visual = "#9745be",
  },
  line_opacity = 0.9
})

nvim --version
NVIM v0.6.0-dev+43-g02bf251bb
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3

Great package!!!

Thanks for report! I noticed this issue if you were to say set colors.copy = 'blue' or some other word because only hex's are supported but not sure where it's getting normal from in this case. Will look into it ☺

I was able to reproduce this with some default themes (eg. "blue" colorscheme) where some colors are set to words instead of hex values. Fixed those cases but if it is still broken for you please reopen and let me know which theme you're using and I'll investigate further :)

i'm using https://github.com/marko-cerovac/material.nvim
-- theme config
vim.g.material_style = 'darker'
vim.g.material_italic_comments = true
vim.g.material_italic_keywords = false
vim.g.material_italic_functions = false
vim.g.material_italic_variables = false
vim.g.material_contrast = true
vim.g.material_disable_background = true
vim.g.material_custom_colors = {
  black = "#1A1A1A",
  bg = "#1A1A1A"
}
vim.g.material_variable_color="#82AAFF"
require('material').set()

Thanks for your theme config, it was the vim.g.material_disable_background = true that was causing issues

Fixed :hugs:


same Submodel Reference can be applied to same AAS again without trowing 409 (already exisits)

Describe the bug
I am creating a new Submodel Reference using the POST /shells/{aasIdentifier}/submodel-refs endpoint and executing it multiple times, the submodel Reference gets added successfully (201 created) and if i execute again it returns again a 201.
From my perspective it does not make sense to "re-create" an already exisiting Reference. I would expect to get a 409 (already exisits) here.
To Reproduce

Open Postman and create a new POST Request and enter {{aas_environment}}/shells/:aas_id_base64/submodel-refs

for aas_environment set the adress of the aas environment e.g. localhost:8081
for aas_id_base64 set a base-64 utf-8 encoded aas id
enter the request body and replace with a known submodel from your environment

{
     "type": "MODEL_REFERENCE",
     "keys": [
         {
             "value": "<<none_base_64_encoded_submodel_id_to_reference_to>>",
             "type": "Submodel"
         }
     ]
}

Send the request. (This should come back with a 201 (Created) Response)
Wait a bit.
Send the request again.
It should return again a 201.

Expected behavior
By already existing Reference / trying to recreate the same reference it should throw a 409 (already exists.)
BaSyx:

BaSyx Version v2.0 Snapshot (also made sure to update/redownload my images before posting)
BaSyx SDK Java
AAS Version DotAAS V3

Screenshots

Used Asset Administration files (.aasx/.json/.xml)
I believe this error can be reproduced in any running aas environment with at least 1 submodel and 1 aas, even if the submodel is already referenced to the aas.
BaSyx configuration
I do not think this is necessary if needed i will present it.
System (please complete the following information):

OS: Windows [Host] - AAS Off the Shelf Components [Docker]

Additional context
If there are any suggestions for this issue, especially how I presented the content of this issue, feel free to let know.

Hi @merlinseela
Thanks for raising this issue.
We will analyze this issue and get back to you soon.
If we need further information, I'll let you know.


Update our Antlr version to latest (4.10.1)

Currently using 4.9.3, but 4.10.1 is out now as of April 15, 2022.
Also, "commons-validator" is now at version 1.7 (we are using 1.6).

Unfortunately (maybe) this Antlr version is built for target of Java 11 (version 55), so our Java 8 builds are failing. Maybe I can build Antlr to target Java 8 somehow, but until then I will disable the Java 8 CI builds.

Hmm, according to here: https://github.com/antlr/antlr4/releases/tag/4.10.1 4.10.1 was specifically built to fix the Java 11 bug.... And using "javap -v" to list some random classes in both Antlr .jar files shows version 52.... Very strange -- needs more investigation.

Aha: Exception in thread "main" java.lang.UnsupportedClassVersionError: org/antlr/v4/Tool has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0
Dumping "org.antlr.v4.Tool" class file does indeed show version 55... Other classes in that .jar, though, show version 52.

Response is "The tool is requiring Java 11 now but the run time is still 8."
So, I guess I have to figure out how to do some sort of hybrid Java version build, or figure out a way to generate the grammar and save it for the Java 8 build. Or drop back to 4.9.3, or just forget building with Java 8...

I think this will solve it:
for JDK8 build, do:

setup JDK11
run new script that does "ant clean process-grammars"
setup JDK8
run new script that does "ant jar doc test"


Default --output-dir to overwrite the old image

Is your feature request related to a problem? Please describe.
I was surprised when the CLI tool didn't overwrite the files it was optimizing. Instead, it wrote the files to the root of my directory, where I was running the command from.
In referencing the document, I see that the --output-dir defaults to ., the location where you're running the tool from.
The current behavior is as follows:
> pwd
/tmp/example-repo
> ls -al assets/images
total 500
drwxr-xr-x 5 blimmer wheel    160 Jul 14 12:44 ./
drwxr-xr-x 4 blimmer wheel    128 Jul 14 12:44 ../
-rw-r--r-- 1 blimmer wheel  34292 Jul 14 09:57 1.png
-rw-r--r-- 1 blimmer wheel 248841 Jul 14 10:21 2.png
-rw-r--r-- 1 blimmer wheel 222644 Jul 14 10:24 3.png
> npx @squoosh/cli --oxipng '{"level": 2}' assets/images/*.png
npx: installed 37 in 3.498s
3/3 ✔ Squoosh results:
 assets/images/1.png: 33.49KB
  └ 1.png → 20.44KB (61.0%)
 assets/images/2.png: 243.01KB
  └ 2.png → 127.58KB (52.5%)
 assets/images/3.png: 217.43KB
  └ 3.png → 111.63KB (51.3%)
> ls -al
total 268
drwxr-xr-x  8 blimmer wheel    256 Jul 14 12:46 ./
drwxrwxrwt 13 root       wheel    416 Jul 14 12:44 ../
drwxr-xr-x 12 blimmer wheel    384 Jul 14 12:46 .git/
-rw-r--r--  1 blimmer wheel  20930 Jul 14 12:46 1.png
-rw-r--r--  1 blimmer wheel 130638 Jul 14 12:46 2.png
-rw-r--r--  1 blimmer wheel 114306 Jul 14 12:46 3.png
drwxr-xr-x  4 blimmer wheel    128 Jul 14 12:44 assets/
-rw-r--r--  1 blimmer wheel    226 Jul 14 12:44 package.json

Describe the solution you'd like
It would be great if this tool overwrote the unoptimized file by default. Considering the example from above, this is the behavior I'd expect:
> pwd
/tmp/example-repo
> ls -al assets/images
total 500
drwxr-xr-x 5 blimmer wheel    160 Jul 14 12:44 ./
drwxr-xr-x 4 blimmer wheel    128 Jul 14 12:44 ../
-rw-r--r-- 1 blimmer wheel  34292 Jul 14 09:57 1.png
-rw-r--r-- 1 blimmer wheel 248841 Jul 14 10:21 2.png
-rw-r--r-- 1 blimmer wheel 222644 Jul 14 10:24 3.png
> npx @squoosh/cli --oxipng '{"level": 2}' assets/images/*.png
npx: installed 37 in 3.426s
3/3 ✔ Squoosh results:
 assets/images/1.png: 33.49KB
  └ assets/images/1.png → 20.44KB (61.0%)
 assets/images/3.png: 217.43KB
  └ assets/images/3.png → 111.63KB (51.3%)
 assets/images/2.png: 243.01KB
  └ assets/images/2.png → 127.58KB (52.5%)

I can get this behavior by passing -d assets/images (npx @squoosh/cli -d assets/images --oxipng '{"level": 2}' assets/images/*.png), but it would be nice if this were the default. Users who want to place the files in a different location could still override the behavior via the -d/--output-dir flag.
Additional context
A change to the default behavior would help support my use of lint-staged to automatically compress images at commit time. Today, I have to do something like this for my lint-staged configuration:
{
  "lint-staged": {
    "assets/images/*.png": ["npx @squoosh/cli -d assets/images --oxipng '{\"level\": 2}']
  }
}

Note that I have to restrict the staged pattern to assets/images/*.png so I can pass the proper -d variable.
If the default were changed, I could simplify this to:
{
  "lint-staged": {
    "*.png": ["npx @squoosh/cli --oxipng '{\"level\": 2}']
  }
}

This would be preferable so all png images committed to this repo (regardless of the directory) would be optimized.
Does other service/app have this feature?

svgo:
 > npx --no-install svgo
 Usage: svgo [options] [INPUT...]

 ... truncated output ...
   -o, --output <OUTPUT...>   Output file or folder (by default the same as the input), "-" for STDOUT

imageoptim: by default, it overwrites the file when optimizing.

Would love to see this feature! I don't think it should be the default output source though, too easy to accidentally overwrite.

+1! The current default behaviour can be destructive: The original file is overwritten with the compresed one!

who solves this problem?

Unfortunately, due to a few people leaving the team, and staffing issues resulting from the current economic climate (ugh), the CLI and libsquoosh packages are no longer actively maintained. I know that sucks, but there simply isn't the time & people to work on this. If anyone from the community wants to fork it, you have my blessing. The squoosh.app web app will continue to be supported and improved.


feat: no longer load full table into ram in write

Description
Well, I suffered quite a bit and am still not finished. But here's what I've learned so far:

If you pass around the Iterator from Python to Rust, it's Send, but not Sync which complicates the usage in a future. To work around limitations of this, I had to split the WriterBuilder into two Structs, one for the data and one for the config
DataFusion is a pretty cool thing! You can really pick what you want from it and it uses good abstractions. I need to have a deeper look at it :)

About the implementation:
Instead of doing something proper, I wanted to first create this PR that basically just takes the iterable and breaks in into chunks to process. This is not ideal, it does not parallelize as good as using things like channels, but that would be a bigger thing. Still a big win for large tables!
Related Issue(s)
Fixes #2255
Documentation

@aersam haven't checked yet, but are you streaming data to open file handles?
Or do you close the files after writing chunks?

I just create many files 🙂

Streaming would be better, but way more complicated to do

@aersam in that case I don't think it's the right way, with small sized recordbatches you could potentially get many many small parquets which then suddenly would require to constantly run optimize afterwards to fix that

Ok, true. What if I'd count the rows in a chunk and let it grow to a certain threshold?

@aersam in that case I don't think it's the right way, with small sized recordbatches you could potentially get many many small parquets which then suddenly would require to constantly run optimize afterwards to fix that

This is resolved now, it will now produce few big files using streams

I also removed lot's of duplicate code now, the writer was dividing stuff into partitions twice. Column Mapping in Write would also be pretty straightforward now

I could implement From for the WriteData Enum to make usage a bit simplier, if you want

@aersam I'll try to take a look tonight!

Yep. I tried using a StreamingTable, but this one has to be Sync which is an issue. The stream worked fine

I could implement From for the WriteData Enum to make usage a bit simplier, if you want

Maybe do that and have the DeltaOps().write use an into

I could implement From for the WriteData Enum to make usage a bit simplier, if you want

Maybe do that and have the DeltaOps().write use an into

this is done now

One thing came to my mind, I'm not a 100% sure, but is it a good idea to to py.allow_threads in lib.rs on Python Side? Since we're iterating accross language borders, I guess, we need to hold the GIL, no? I pushed a commit that should resolve it, but feel free to undo if you disagree

On this I'm not entirely sure, it is a python object and consuming a reader can only be done once but  @emcake 's description of his PR suggests it's safe? https://github.com/delta-io/delta-rs/pull/2091
@wjones127 @emcake any insights or comments on this?

It think it can only be safe if pyarrow itself would take care of getting the GIL. I don't know if they do this

If that's the case, then we need to apply GilIterator change to merge_execute as well, since that one also wouldn't be safe anymore with your changes

If that's the case, then we need to apply GilIterator change to merge_execute as well, since that one also wouldn't be safe anymore with your changes

I tried getting myself through the pyarrow code and see if it does acquire the GIL and it looks like it does: https://github.com/apache/arrow/blob/93816475f75d751067d4ff427fb9ae64e85acebe/python/pyarrow/src/arrow/python/ipc.cc#L39
So I'll revert the last two commits

The failure is not related to my changes, I guess?

Closing this in favor of #2289 which I'll keep up to date with the main branch


Add support for building with cabal-<IP_ADDRESS>

Use symlink-bindir or install-dir depending on cabal version
Add support for building in windows, using install-method=copy
Use v2- prefix instead new- (available since cabal-<IP_ADDRESS>)

Fixes #1250

Oh, i've disabled tests when building hie, it makes the installation takes longer to finish and afaik it is not needed for install it.

This seems nice! Thanks

Does this fix https://github.com/haskell/haskell-ide-engine/issues/1376 as well?

Nope, this is just for building the executables

Ah, my bad.


Bugfix missing data dir

Create data directory if not present. Additionally small refactoring, added a constant for the folder name.
Previous discussion: https://github.com/badlogic/heissepreise/pull/19

Cheers!


Is it possible to fetch db.each results by field name?

Hi! I'm going along with this query below. And there's no way apparently to pick up values by field name (row.req_name for example). It seems you just can do row[0], row[1] etc.. Is that so?  Any alternative? Thanks!
// select all records
    new sqlite("cacg.db", function(err, db) {
        db.each("SELECT req_cuit,req_name FROM req_mst ORDER BY id", [], function(err, row) {
            console.log(row);
        });
    });

Please read the docs; it has how to switch to field names rather than arrays.


Cannot install local Visual F# Tools on RC2

Install F# through VS Installer.
Build a release build of Visual F# tools.
Uninstall F#.
Run VSIXInstaller.exe /a release\net40\bin\VisualFSharpOpenSource.vsix to install locally.

Expectected: I can open an F# project and work in it with the new tools installed locally.
Actual: Projects fail to load, some as "Incompatible" and some as "Unavailable".

12/15/2016 9:25:37 PM - Microsoft VSIX Installer
12/15/2016 9:25:37 PM - -------------------------------------------
12/15/2016 9:25:38 PM - Initializing Install...
12/15/2016 9:25:38 PM - Extension Details...
12/15/2016 9:25:38 PM - 	Identifier         : VisualFSharp
12/15/2016 9:25:38 PM - 	Name               : Visual F# Tools
12/15/2016 9:25:38 PM - 	Author             : Microsoft.VisualFSharpTools
12/15/2016 9:25:38 PM - 	Version            : <IP_ADDRESS>55
12/15/2016 9:25:38 PM - 	Description        : Deploy Visual F# Tools templates to Visual Studio
12/15/2016 9:25:38 PM - 	Locale             : en-US
12/15/2016 9:25:38 PM - 	MoreInfoURL        :
12/15/2016 9:25:38 PM - 	InstalledByMSI     : False
12/15/2016 9:25:38 PM - 	SupportedFrameworkVersionRange : [4.6,)
12/15/2016 9:25:38 PM -
12/15/2016 9:25:38 PM - 	SignatureState     : Unsigned
12/15/2016 9:25:38 PM - 	Supported Products :
12/15/2016 9:25:38 PM - 		Microsoft.VisualStudio.Pro
12/15/2016 9:25:38 PM - 			Version : [15.0]
12/15/2016 9:25:38 PM -
12/15/2016 9:25:38 PM - 	References         :
12/15/2016 9:25:38 PM - Signature Details...
12/15/2016 9:25:38 PM - 	Extension is not signed.
12/15/2016 9:25:38 PM -
12/15/2016 9:25:38 PM - Searching for applicable products...
12/15/2016 9:25:39 PM - Found installed product - Microsoft Visual Studio Professional 2013
12/15/2016 9:25:39 PM - Found installed product - Microsoft Visual Studio 2013 Shell (Integrated)
12/15/2016 9:25:39 PM - Found installed product - Microsoft Visual Studio Community 2015
12/15/2016 9:25:39 PM - Found installed product - Microsoft Visual Studio 2015 Shell (Integrated)
12/15/2016 9:25:39 PM - Found installed product - Global Location
12/15/2016 9:25:39 PM - Found installed product - ssms
12/15/2016 9:25:39 PM - VSIXInstaller.NoApplicableSKUsException: This extension is not installable on any currently installed products.
   at VSIXInstaller.App.InitializeInstall(Boolean isRepairSupported)
   at VSIXInstaller.App.InitializeInstall()
   at System.Threading.Tasks.Task.InnerInvoke()
   at System.Threading.Tasks.Task.Execute()

Closing this for now - will re-open/rename if I get the same issues on RC3.  I know @brettfo has been doing a lot of setup work and may have this resolved.


[Config] register ConfigPanel in extension.ts

import ConfigPanel in extension.ts so now we can see webview extension
ONE-vscode-DCO-1.0-Signed-off-by: TaeKyuRyu<EMAIL_ADDRESS>

from issue #58
from draft #117

import ConfigPanel in extension.ts so now we can see webview extension

How about this?

This will enable 'onevscode.configuration-settings' invoke 'ConfigPanel' to show configuration GUI.

i think your message is better explain for this commit, i will change it

@OTKRyu  , please resolve conflict.


nuget packages not loading

Hi there,
I decided to use dotnet script instead of linqpad as most of my development is in vscode. so I started with dotnet script init.
First I got issue with .Net Script Debug. I figured that vscode is looking for .vscode folder in parent of .csx directory.
Now, I am at main.csx with following code. Inteli-sense doesn't recognize namespace System.Net.Http. Obviously omnisharp/msbuild is not restoring packages. I also tried Nuget.Config in directory where main.csx is, and also its parent directory. Nuget.config may be irrelevant as msbuild issue needs to be resolved first.
#r "nuget: System.Net.Http, 4.3.4"
using System.Net.Http;
var client=new HttpClient();
Console.WriteLine("Hello world!");

As I see in other issues, I changed omnisharp logging level to trace. I got lot of trace, but not sure what causing my issue.
I have 3 locations for msbuild. 2019, 2017 (installed from chocolatey installation) and stand alone.
I also tried to change omnisharp.json to override msbuild path like below, which didn't make any difference.
{
  "script": {
    "enableScriptNuGetReferences": true,
    "defaultTargetFramework": "net5.0"
  },
"msbuild": {
  "MSBuildSdksPath":"C:\\Program Files (x86)\\Microsoft Visual Studio\\2017\\BuildTools\\MSBuild\\15.0\\Bin",
  "enabled": true,
  }
}

I am uploading the omnisharp log here. its quite big.
omnisharp.log
I appreciate your help!!

according to the log the your omnisharp.json is not discovered.
Is it located at the root of the workspace you are opening in VS Code?
The log shows that instead of net5.0, the CSX scripts are offered with .NET 4.6.1 desktop mode, without nuget support.
[info]: OmniSharp.Script.ScriptContextProvider
        Searching for compilation dependencies with the fallback framework of 'net461'.
[fail]: OmniSharp.Script.ScriptContextProvider
        Failed to resolve compilation dependencies
[info]: OmniSharp.Script.ScriptContextProvider
        Unable to find dependency context for CSX files. Will default to non-context usage (Desktop CLR scripts).

Thanks for that insight @filipw. You are right about workspace. Now I moved omnisharp.json to workspace directory.
What version should I pick if net5.0 is not supported. Here is my dotnet --info. I changed it to netcore3.1 though.
it still fails.
.NET SDK (reflecting any global.json):
 Version:   5.0.100
 Commit:    5044b93829

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.18363
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\5.0.100\

Host (useful for support):
  Version: 5.0.0
  Commit:  cf258a14b7

.NET SDKs installed:
  3.1.402 [C:\Program Files\dotnet\sdk]
  5.0.100 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.All 2.1.23 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.23 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.1.9 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 5.0.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.1.23 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.1.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 5.0.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 3.1.9 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 5.0.0 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Here is my project structure.

Here is omnisharp.json
{
  "script": {
    "enableScriptNuGetReferences": true,
    "defaultTargetFramework": "netcore3.1"
  },
  "msbuild": {
    "MSBuildSdksPath": "C:\\Program Files (x86)\\Microsoft Visual Studio\\2017\\BuildTools\\MSBuild\\15.0\\Bin",
    "enabled": true
  }
}

Here is omnisharp log file again..
omnisharp2.log

The TFM for .NET Core 3.1 is netcoreapp3.1 not netcore3.1.
Also, you should not set MSBuildSdksPath to VS 2017 as it uses MSBuild 15.9.
The minimum MSBuild for .NET Core 3.1 is 16.3 and for .NET 5.0 is 16.8. Leaving this to default and letting OmniSharp choose is the best option.

one more thing, you don't need to pull System.Net.Http from NuGet - it's available there by default so you can just start using it directly

I was trying as an example for System.Net.Http. Originally I wanted to get nuget: System.Net.Http.Json, 5.0.0.
I tried with netcoreapp3.1 as well. Now moved back to default net5.0 and it doesnt complain about fallback to net461.
script.csproj also created in temp folder. However, no referenced package downloaded.
[fail]: OmniSharp.Script.ScriptContextProvider
        Failed to resolve compilation dependencies
[info]: OmniSharp.Script.ScriptContextProvider
        Unable to find dependency context for CSX files. Will default to non-context usage (Desktop CLR scripts).
[dbug]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Attempting to resolve 'System.Runtime'
[dbug]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        FAILURE: Could not locate 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\System.Runtime.dll'.

I am ok with any framework. just wanted the #r "nuget: "

I tried with a fresh workspace and it works with net5.0 flawless. I think Nuget.Config was the issue in my old setup also. After I remove that file, even old workspace works as intended. Thank you very much for your help @filipw.


Dont allow zero balance TX

Warn when user trying to send a zero balance transaction.

@JamesSmartCell you might have just rebased the definition of rebase ;)


[bug]: AccordionTrigger throws error with asChild

Describe the bug
If you try to use the asChild prop with AccordionTrigger React throws an error because we try to render a icon and our children, but it can only render 1 (Radix limitation)
Affected component/components
Accordion
How to reproduce
Add asChild prop to an AccordionTrigger
Codesandbox/StackBlitz link
No response
Logs
No response
System Info
None

Before submitting

[X] I've made research efforts and searched the documentation
[X] I've searched for existing issues

Heres my fix:
export const AccordionTrigger = React.forwardRef<React.ElementRef<typeof AccordionPrimitive.Trigger>, React.ComponentPropsWithoutRef<typeof AccordionPrimitive.Trigger>>(
  ({ className, children, ...props }, ref) => {
    const content = props.asChild ? (
      children
    ) : (
      <>
        {children}
        <ChevronDown className="size-4 shrink-0 transition-transform duration-200" />
      </>
    );

    return (
      <AccordionPrimitive.Header className="flex">
        <AccordionPrimitive.Trigger
          ref={ref}
          className={cn('flex flex-1 text-[16px] tracking-normal items-center justify-between py-4 font-medium transition-all hover:underline [&[data-state=open]>svg]:rotate-180', className)}
          {...props}
        >
          {content}
        </AccordionPrimitive.Trigger>
      </AccordionPrimitive.Header>
    );
  }
);

I agree with this

I understand “asChild” in “radix-ui” to be a way to replace the default rendering element with the one you specify.
For example
<AccordionTrigger> is <button> by default, but <AccordionTrigger asChild>
test
</AccordionTrigger>
should be
 by default
Default EX:
  <AccordionTrigger>

test

  </AccordionTrigger>

asChild EX:
  <AccordionTrigger asChild>

test

  </AccordionTrigger>

But “accrodion” in “shadcn” contains an icon by default
So the “children” in <AccordionPrimitive.Header> renders two elements, returning an error
shadcn Default EX:
  <AccordionPrimitive.Header className="flex">
    <AccordionPrimitive.Trigger
      ref={ref}
      className={cn(
        "flex flex-1 items-center justify-between py-4 font-medium transition-all hover:underline [&[data-state=open]>svg]:rotate-180",
        className
      )}
      {...props}
    >

test

      <ChevronDown className="h-4 w-4 shrink-0 transition-transform duration-200" />
    </AccordionPrimitive.Trigger>
  </AccordionPrimitive.Header>

shadcn asChild EX:
  <AccordionPrimitive.Header className="flex">

svg]:rotate-180",
        className
      )}
      {...props}
    >
      test

    <ChevronDown className="h-4 w-4 shrink-0 transition-transform duration-200" />
  </AccordionPrimitive.Header>

Two React elements are being rendered in “<AccordionPrimitive.Header>” as shown in the code example above
However, “radix-ui” receives a child component as “children” in <AccordionPrimitive.Header>, which violates the React rule “children can only receive one child component”
@shadcn


Bz2 library import error on macos, python3.7

Describe the bug
When executing from huggingface_hub import HfFileSystem, HfApi in macOS with Python 3.7, the following error occurs:
test/conftest.py:4: in <module>
    from huggingface_hub import HfFileSystem, HfApi
../../../hostedtoolcache/Python/3.7.17/x64/lib/python3.7/site-packages/huggingface_hub/__init__.py:311: in __getattr__
    submod = importlib.import_module(submod_path)
../../../hostedtoolcache/Python/3.7.17/x64/lib/python3.7/site-packages/huggingface_hub/hf_file_system.py:10: in <module>
    import fsspec
../../../hostedtoolcache/Python/3.7.17/x64/lib/python3.7/site-packages/fsspec/__init__.py:12: in <module>
    from .compression import available_compressions
../../../hostedtoolcache/Python/3.7.17/x64/lib/python3.7/site-packages/fsspec/compression.py:2: in <module>
    from bz2 import BZ2File
../../../hostedtoolcache/Python/3.7.17/x64/lib/python3.7/bz2.py:19: in <module>
    from _bz2 import BZ2Compressor, BZ2Decompressor
E   ModuleNotFoundError: No module named '_bz2'

Reproduction
See logs part.
The issue can be consistently reproduced on macOS runner of Github Actions.
Logs
https://github.com/deepghs/tbsync/actions/runs/5314756187/jobs/9622324523#step:14:33

**This issue seems to only occur in Python 3.7 on macOS**.

System info
The execution environment is GitHub Actions, and I cannot perform this operation. Additionally, I do not have an available macOS environment locally. Sorry for this.

`huggingface-hub`'s version is 0.15.1

Hi, thanks for reporting. I don't think this is related to huggingface_hub but more fsspec itself, isn't it? According to their repo, it is supported only for Python>=3.8. To be honest I didn't know and thought it was >=3.7 as well. As Python 3.7 itself is coming to an end as well, I don't think we'll investigate time to check how to make it compatible. Maybe we could more gracefully handle the issue though.
would it be possible to run your github CI on macos Python>=3.8 instead?

@Wauplin
This issue is indeed quite tricky. I have reviewed the relevant information on fsspec, but couldn't find any further details. Later, I tried testing it on some temporary macOS environments and found that the problem cannot be consistently reproduced on certain macOS systems. It may be related to the presence of libbzip2 in the system during Python compilation and installation. Therefore, we will exclude the unit tests on macOS with Python 3.7 and inform users about this situation in the README or documentation.

@narugo1992 thanks for investigating further and letting us know. On our side, we'll not try to support it either but it's good to know the limitation exists.


Improve Mobile Responsiveness

The current layout of the AlgoVisualizer application is not fully responsive on mobile devices. Users have reported that the UI elements do not adapt well to smaller screens, making it difficult to navigate and visualize algorithms effectively.

Hi Sandeep,
I've reviewed the issue regarding the mobile responsiveness of the AlgoVisualizer application, and I’d like to take on this task. I've noticed that the navbar does not change & appears to be weird on smaller screens, which affects navigation.
Additionally, the main section's content doesn't display well on mobile, making it challenging for users to visualize algorithms effectively.
I believe I can address these issues to improve the mobile experience.
Let me know if you want me to resolve it...!

@abdullahkalim21 Go ahead , I'm assigning this issue to you


Issue for JuliaRegistrator

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/86578
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.9.0 -m "<description of version>" 6a6a6e6739edffe052051fd20bc43ed58d4e7c6b
git push origin v0.9.0

Also, note the warning: This looks like a new registration that registers version 0.9.0.
Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

@JuliaRegistrator register()

Error while trying to register: Register Failed
@giopaglia, it looks like you are not a publicly listed member/owner in the parent organization (aclai-lab).
If you are a member/owner, you will need to change your membership to public. See GitHub Help

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/87047
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.9.1 -m "<description of version>" 501c605c03887ed3aeda1858e03203e4782ea51c
git push origin v0.9.1

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/87583
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.10.0 -m "<description of version>" ad71732098df3029d28c5d3e912e5d0b81d64a50
git push origin v0.10.0

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/89123
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.10.1 -m "<description of version>" 4d075211ddfd9a186a209a1020d0b6bbd9363d33
git push origin v0.10.1

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/95091
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.11.0 -m "<description of version>" bc0666db0774ba677e4ebd4afa5bfaf533961d50
git push origin v0.11.0

@JuliaRegistrator register

Registration pull request updated: JuliaRegistries/General/95091
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.11.0 -m "<description of version>" 54d729935cddb2601752a5348ffd1f3f1ada1494
git push origin v0.11.0

@JuliaRegistrator register()

Error while trying to register: Version 0.11.0 already exists

Registration pull request created: JuliaRegistries/General/95290
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.11.1 -m "<description of version>" 23420796f6efbcb1155be3d51ac6b6607f59694b
git push origin v0.11.1

@JuliaRegistrator register()

Registration pull request updated: JuliaRegistries/General/95290
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.11.1 -m "<description of version>" b225cf7ffaab0ad3c9cf8fd873884fd69294a0ec
git push origin v0.11.1

@JuliaRegistrator register()
Release notes:
Breaking change: AbstractDimensionalDataset's are not AbstractArray's anymore, but AbstractVector's of AbstractArray's of the same dimension.

Registration pull request created: JuliaRegistries/General/96119
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.12.0 -m "<description of version>" 6a438da98b9879cd655a8daace0c87d5bd9743d9
git push origin v0.12.0

Registration pull request updated: JuliaRegistries/General/96119
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.12.0 -m "<description of version>" f0cc25deb364b9d44758add2abad144f6de256e0
git push origin v0.12.0

@JuliaRegistrator register()
Release notes:
Breaking change
AbstractDimensionalDataset's are not AbstractArray's anymore, but AbstractVector's of AbstractArray's of the same dimension.

Registration pull request updated: JuliaRegistries/General/96119
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.12.0 -m "<description of version>" f73bfdcf4103fd441ba22893cb27c5b0afa211e1
git push origin v0.12.0

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/96199
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.12.1 -m "<description of version>" 10e177b46f53fc8dd2404003c7d48e4222eeaeb0
git push origin v0.12.1

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/97084
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.12.2 -m "<description of version>" 1de9e10b793a68d59bb3d489971f34aba2a2685c
git push origin v0.12.2

@JuliaRegistrator register()

Error while trying to register: Version 0.12.2 already exists

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/100854
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.13.0 -m "<description of version>" e02c06e827dea8bc0f55a23f0f3c4c1acd992c34
git push origin v0.13.0

@JuliaRegistrator register()

Registration pull request updated: JuliaRegistries/General/100854
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.13.0 -m "<description of version>" 69bb46c3eef410d0b72383acbf3a17033c8f1c99
git push origin v0.13.0

Registration pull request created: JuliaRegistries/General/101717
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.13.1 -m "<description of version>" b93163c06189f2b445e8664712ce34af9830a5dc
git push origin v0.13.1

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/108634
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.14.0 -m "<description of version>" dc816f18ec1e41cf907ba692e6e290e37c068af4
git push origin v0.14.0

@JuliaRegistrator register
Release notes:

Add PropositionalLogiset
Deprecate UnboundedScalarConditions and BoundedScalarConditions in favor of UnionAlphabet{UnivariateScalarAlphabet}.
Base.rand(a::AbstractAlphabet, ...) -> randatom(a, ...)
Add ObliqueScalarCondition (untested)
Add Fayyad's alphabet discretization algorithm
Rename: UnivariateValue -> VariableValue
Rename: Univariate(Min|Max|SoftMin|SoftMax) -> Variable(Min|Max|SoftMin|SoftMax)
Improve featval, check, checkcondition interface

Registration pull request updated: JuliaRegistries/General/108634
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.14.0 -m "<description of version>" ee55c39a95fdfb34e4fe34ae1f65d066b311c85f
git push origin v0.14.0

@JuliaRegistrator register()

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/110423
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.15.0 -m "<description of version>" 66b603c4c0a72d64b5a8c9346a41cb205432c397
git push origin v0.15.0

@JuliaRegistrator register()

Registration pull request updated: JuliaRegistries/General/110423
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.15.0 -m "<description of version>" 66b603c4c0a72d64b5a8c9346a41cb205432c397
git push origin v0.15.0

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/112953
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.15.2 -m "<description of version>" 995e31739595bd09c4293ac22e7239b960d05009
git push origin v0.15.2

Also, note the warning: Version 0.15.2 skips over 0.15.1
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/118060
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.15.1 -m "<description of version>" 5c17930784a10940a9cf2561362f1b005f549659
git push origin v0.15.1

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/118204
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.15.2 -m "<description of version>" 98a08615b46302b9a89392751fc0fcffd3246794
git push origin v0.15.2

@JuliaRegistrator register()

Error while trying to register: Version 0.15.2 already exists

Registration pull request created: JuliaRegistries/General/118289
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.15.3 -m "<description of version>" 644288cbecf0d5abbfba3d0649f521bd8f9ff1a3
git push origin v0.15.3

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/118933
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.15.4 -m "<description of version>" f03c81333a77d018367b78623c8cbdc381c40286
git push origin v0.15.4

@JuliaRegistrator register()

Registration pull request updated: JuliaRegistries/General/118933
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.15.4 -m "<description of version>" 77c3495de87df42b41c446098eedc3260ea47ac3
git push origin v0.15.4

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/119168
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.15.5 -m "<description of version>" 09bcde39f3f52fb915e2b38d087a8974e3c992ec
git push origin v0.15.5

Also, note the warning: Version 0.15.5 skips over 0.15.4
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

Registration pull request updated: JuliaRegistries/General/119168
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.15.5 -m "<description of version>" 1cc96b7cf7d616c938395b825ccc13f4c7f32c9b
git push origin v0.15.5

Also, note the warning: Version 0.15.5 skips over 0.15.4
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

@JuliaRegistrator register()

Registration pull request updated: JuliaRegistries/General/119168
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.15.5 -m "<description of version>" 1cc96b7cf7d616c938395b825ccc13f4c7f32c9b
git push origin v0.15.5

Also, note the warning: Version 0.15.5 skips over 0.15.4
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/121110
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.15.6 -m "<description of version>" 1fc92fd1a48954995fe3739290fbcc76109c7eba
git push origin v0.15.6

Also, note the warning: Version 0.15.6 skips over 0.15.4
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

@JuliaRegistrator register()


Set closable notification

My app syncs with another software in the background. If the other software is not open then the data will not be sent to my app. Hence, I would like to add a closable notification. HOw can I do this?

Issues of electron-sample-apps are for feature requests and bug reports. I'd suggest you asking questions about using Electron community or the Slack Channel.


Does pdf.js support form-filling then saving the resulting 'filled' PDF?

I would like to understand if pdf.js support my use case of embedded form filling and also saving the resulting 'filled' PDF either to the file system or via an HTTP POST.
Sample code as part of the examples would be fantastic!

Yes, once a form has been filled in (using e.g. the viewer) the "new" PDF file can be obtained with the PDFDocumentProxy.saveDocument method; please see https://github.com/mozilla/pdf.js/blob/fc487c8aa99f5910315ad55dcb413c3fc0cf243e/src/display/api.js#L1025-L1031

When opening an issue, please remember to provide all of the information requested in https://github.com/mozilla/pdf.js/blob/master/.github/ISSUE_TEMPLATE.md and please also see https://github.com/mozilla/pdf.js/blob/master/.github/CONTRIBUTING.md (emphasis mine):

If you are developing a custom solution, first check the examples at https://github.com/mozilla/pdf.js#learning and search existing issues. If this does not help, please prepare a short well-documented example that demonstrates the problem and make it accessible online on your website, JS Bin, GitHub, etc. before opening a new issue or contacting us in the Matrix room -- keep in mind that just code snippets won't help us troubleshoot the problem.


Initial commit

Initial commit

@AndrewAR2 - is this PR ready for code review?

The code is working on all platforms, however I have to add error handling.

The code is working on all platforms, however I have to add error handling.

Please do and let @noamnelke know when this PR is ready for code review.

I think this is ready for review.

Fixed!


Adding Issue template

Adding an Issue template so it is easier for both maintainer and contributer to put issues.
please assign this issue to me.

Hi @Mayank77maruti thanks for contributing!
Please write here what is your template suggestion and we will consider

Hey @orsa-classiq , I have mentioned template for bug report and feature request template. Please do have a look.


Update chat_to_files.py

I ran into issues where i was moving the file around and renaming it but renamed it back before i launched gpt engineer and ran into it an error because the file was not in the file_dict. This will address that. I am also making a comment in this issue https://github.com/gpt-engineer-org/gpt-engineer/issues/928

I dont believe this should be failing. its possible the CI/CD tool isnt passing the filename.

I know this is closed but i am running into this quite a bit and it tends to eat up some $$ every time this happens. Is there anything i can do to prevent these from happening @ATheorell ?
WARNING:gpt_engineer.core.chat_to_files:While applying an edit to New-VMClone2.ps1, the code block to be replaced was not found. No instances will be replaced

Good question:

All code that you paid for is saved in the .gpteng/memory subdirectory of you project. If the paste fails, you can paste in the revised code manually
To improve the situation, you can implement PR https://github.com/gpt-engineer-org/gpt-engineer/issues/869


Cannot connect to IAM only instance on IBM Cloud with VCAP_SERVICES

Please read these guidelines before opening an issue.

Bug Description
Cannot connect to IAM only instance on IBM Cloud with VCAP_SERVICES because VCAP_SERVICES does not contain a credentials.host.
1. Steps to reproduce and the simplest code sample possible to demonstrate the issue
i.create cloudant instance with only IAM authentication.
ii. connect to the instance with ClientBuilder#bluemix method.
ClientBuilder.bluemix(System.getenv("VCAP_SERVICES")).build()
and gets java.lang.IllegalArgumentException: The Cloudant service instance information was invalid.
I can connect to that instance with ClientBuilder#url and ClientBuilder#iamApiKey.
2. What you expected to happen
Connected to IAM only instance.
3. What actually happened
java.lang.IllegalArgumentException: The Cloudant service instance information was invalid.
at com.cloudant.client.api.ClientBuilder.vcapClientBuilder(ClientBuilder.java:780)
at com.cloudant.client.api.ClientBuilder.bluemix(ClientBuilder.java:743)
at com.cloudant.client.api.ClientBuilder.bluemix(ClientBuilder.java:683)
at com.cloudant.client.api.ClientBuilder.bluemix(ClientBuilder.java:651)
Environment details
my VCAP_SERVICES
VCAP_SERVICES:{"cloudantNoSQLDB":[{   "name": "Cloudant-iam",   "instance_name": "Cloudant-iam",   "binding_name": null,   "credentials": {     "apikey": "???",     "iam_apikey_description": "Auto generated apikey during resource-bind operation for Instance - ???",     "iam_apikey_name": "auto-generated-apikey-???",     "iam_role_crn": "???::::serviceRole:Manager",     "iam_serviceid_crn": "crn:v1:bluemix:public:iam-identity::???",     "url": "https://???-bluemix.cloudant.com",     "username": "???-bluemix"     }, ... blah-blah
Thank you.

Thank you , ricellis.
As follow as your instruction, I posted this issue to Cloudant support team.
I'll share the message when I got reply.

I've gotten a reply from cloudant support.

Hello,
Thankyou for opening this support case.
The issue you are reporting is a bug on the Cloudant side for which a fix has yet to be implemented.
Regards,

Thank you ,all.


Nip 12 generic tags support

Does this support query for tags that are not 't'? My reading of NIP 12 says that it can be any single-letter key. But it seems this crate only supports e,p,t,r?
https://github.com/rust-nostr/nostr/blob/a1b84ce2eb28c654048dbe867ba461027957e5e4/crates/nostr/src/message/subscription.rs#LL63C15-L63C15

The best solution that I find for now is to add a custom filed where you can pass a Map<String, Value>.


twikit.errors.BadRequest: status: 400, message: "{"errors":[{"code":366,"message":"flow name LoginFlow is currently not accessible"}]}"

I'm facing this error and I tried all methods like using user-agent or updating twikit 2.1.2 or with other X account and nothing happened!!
Please Help Me Guys...

try to use a user agent in Client. Is in issue #169

https://github.com/d60/twikit/issues/163#issuecomment-2253068820
This way should work.

try to use a user agent in Client. Is in issue #169

Hi AritzUMA and thanks for your comment
as you can see I tried this method and it didn't work for me
`client = Client(user_agent = 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36'
, language ='en-US')
async def main():
await client.login(
auth_info_1=USERNAME ,
auth_info_2=EMAIL,
password=PASSWORD
)
client.save_cookies('cookies.json')

asyncio.run(main())`

#163 (comment) This way should work.

Hi thanks for commenting
again the same error
here is the code:
with open('C:/IdeaProjects/coockii.json', 'r') as file:
    data = json.load(file)

result = {}
for item in data:
    name = item.get("name")
    value = item.get("value")
    if name and value:
        result[name] = value

with open('C:/IdeaProjects/coockiTwikit.json', 'w') as file:
    json.dump(result, file, indent=4)

client = Client(user_agent = 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36'
, language ='en-US')

async def main():
    await client.login(
        auth_info_1=USERNAME ,
        auth_info_2=EMAIL,
        password=PASSWORD
    )
    client.save_cookies('cookies.json')
asyncio.run(main())

#163 (评论)这种方法应该可行。

嗨，谢谢 再次评论同样的错误， 这里的代码是：
with open('C:/IdeaProjects/coockii.json', 'r') as file:
    data = json.load(file)

result = {}
for item in data:
    name = item.get("name")
    value = item.get("value")
    if name and value:
        result[name] = value

with open('C:/IdeaProjects/coockiTwikit.json', 'w') as file:
    json.dump(result, file, indent=4)

client = Client(user_agent = 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36'
, language ='en-US')

async def main():
    await client.login(
        auth_info_1=USERNAME ,
        auth_info_2=EMAIL,
        password=PASSWORD
    )
    client.save_cookies('cookies.json')
asyncio.run(main())

Remove the code below and try again
await client.login(
auth_info_1=USERNAME ,
auth_info_2=EMAIL,
password=PASSWORD
)

Fixed it HERE


Improve $INPUT_RECORD_SEPARATOR deprecation check

Ref: https://github.com/casperisfine/csv/commit/1f9cbc170ea4f3d9a9db48d12bcf9895bfe86c25
Setting $VERBOSE = false is not quite enough because some applications
define Warning.warn to collect and process warnings beyond just priting
them on STDERR.
For instance some apps might translate warnings into errors:
def Warning.warn(message)
  raise Deprecated, message
end

So hooking into Warning.warn to catch the deprecation warning is much less likely to cause issues.
cc @kou

I've had the same issue and worked around it like this: https://github.com/Shopify/maintenance_tasks/commit/734e949bce13f0ef0a2f4648df0bb1f810cd1d9d
I had started working on a fix, this was my test harness, which all pass with this branch:
if ARGV.delete("singleton")
  module Warning
    def self.warn(message)
      raise message.to_s
    end
  end
else
  module RaiseWarning
    def warn(message)
      raise message.to_s
    end
  end
  if ARGV.delete("prepend")
    Warning.prepend(RaiseWarning)
  else
    Warning.extend(RaiseWarning)
  end
end
Warning[:deprecated] = true
$VERBOSE = true

begin
  require "csv"
rescue
  p $!
  exit(1)
end

begin
  warn("should raise")
rescue
  exit(0)
end

puts "expected to raise"
exit(1)

$ ruby -Ilib test.rb || echo failed
$ ruby -Ilib test.rb singleton || echo failed
$ ruby -Ilib test.rb prepend || echo failed

Good catch!
But I feel that this approach is overkill...
I pushed simple RUBY_VERSION based check approach. Sorry.

Haha, yeah that makes sense :)


Enable slack integration with granfana and setup a warning channel for each supported network

https://github.com/MinaProtocol/mina/issues/11933 this is a more recent ticket but the same end goal


volumepolicies & configmaps should be added as a resource in ClusterRole

This is to avoid below errors while provisioning openebs volumes using VolumePolicy:
volumepolicies.openebs.io "openebs-policy-taints-0.6.0" is forbidden: User "system:serviceaccount:openebs:openebs-maya-operator" cannot get volumepolicies.openebs.io at the cluster scope

configmaps "volume-service-0.6.0" is forbidden: User "system:serviceaccount:openebs:openebs-maya-operator" cannot get configmaps in the namespace "openebs"

Below is the suggested ClusterRole
# Source: openebs/templates/clusterrole.yaml
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: ClusterRole
metadata:
  name: openebs-maya-operator
  labels:
    chart: "openebs-0.5.3"
rules:
- apiGroups: ["*"]
  resources: ["nodes","nodes/proxy"]
  verbs: ["get", "list", "watch"]
- apiGroups: ["*"]
  resources: ["namespaces", "services", "pods", "deployments", "events", "endpoints", "configmaps"]
  verbs: ["*"]
- apiGroups: ["*"]
  resources: ["persistentvolumes","persistentvolumeclaims"]
  verbs: ["*"]
- apiGroups: ["storage.k8s.io"]
  resources: ["storageclasses"]
  verbs: ["*"]
- apiGroups: ["*"]
  resources: ["storagepools","volumepolicies"]
  verbs: ["get", "list"]
- nonResourceURLs: ["/metrics"]
  verbs: ["get"]

Duplicate Issue #1307

Tracked under #1318


ppx: don't assume external components are functions

Fixes #123

There. I did try to do it like this initially, but couldn't quite figure out how things fit together. Thanks for the pointers!


Multimodal infomax does not have modules.encoders file

https://github.com/declare-lab/MSA-Robustness/blob/2466d33c767411f6490c8c022666e8d9167696b9/Multimodal-Infomax/src/model.py#L8

The encoders.py file is part of the BBFN directory ([https://github.com/declare-lab/MSA-Robustness/blob/main/BBFN/src/modules/encoders.py]). However, this file has only LanguageEmbeddingLayer class and the other classes mentioned above are missing.
I hope they can provide these files otherwise it won't be possible to run the code.

The author seems to have deliberately left out these documents.


picosoc: fixed missing use of BOARD_BUILDIR

The BOARD_BUILDIR was set but never used in xc7/picosoc_demo/Makefile. Solved (as used in the other examples).

Great @mithro but it seems that CI will never end :laughing: (is running from yesterday in "Queued" state). I saw the same in a PR from Dec 2020 (#105).

Great @mithro but it seems that CI will never end  (is running from yesterday in "Queued" state). I saw the same in a PR from Dec 2020 (#105).

@rodrigomelo9 we're looking at the CI issue

Ok @kgugala I saw that is a known issue in GitHub (messages from 2019) but I didn't found how is it solved.
Regards

Ok @kgugala I saw that is a known issue in GitHub (messages from 2019) but I didn't found how is it solved.
Regards

CI is now running


Subtitle issue

Hi, Great job !
Method for WebOs work fine and resolutions are ok on a 49UB850V (4K model).

When clicking on option "subtitle:disabled"  appear a "Error 2" message on the upper right corner and subtitle are not disabled.
Sometimes subtitles freeze on words, need to resume, stop and on menu launch again from last position to erase it.
When i push "pause" the timer in the down bar stay on a xx:xx position not corresponding to reality but lenght of time bar is at the correct position (resume time position correct too)

cheers
Nico

I have this issue too, on the LG 65UB9500 with WebOS.
Every video has subtitles and you can't turn them off.

Same issue.
LG 42LB652 with WebOS

+1 on LG42LB6500

simonjhogan can we assume development on this has ceased with the official client coming to the LG TVs?

I am still tinkering ...
Sent from my iPhone

On 27 Mar 2015, at 9:04 am, fkick<EMAIL_ADDRESS>wrote:
simonjhogan can we assume development on this has ceased with the official client coming to the LG TVs?
—
Reply to this email directly or view it on GitHub.

oficial app need a plex pass

I have the same problem and it bothers me alot. Will this be fixed?

there is nothing I can do about embedded subtitles ... the api for subtitles is literally on or off for external subtitles only ... so either use transcoding or re-encode you movies