uint32_t is not defined in zconf.h

In ff9162c1a0da8d60ae664e5930b256de99ad83b3, z_crc_t type has been added as uint32_t. However, uint32_t is not defined in zconf.h. zlib's zconf.h uses some macros to select the correct type of integer for z_crc_t, so stdint.h does not need to be included. But when using z_crc_t in zlib-ng, stdint.h must be included, causing compatibility issues between zlib-ng and zlib.
[   98s] gcc -DHAVE_CONFIG_H -I.  -include config.h -I./include -DLOCALEDIR=\"/usr/share/locale\" -D_PATH_RUNSTATEDIR=\"/run\" -D_PATH_SYSCONFSTATICDIR=\"/usr/lib\" -D_PATH_VENDORDIR=\"/usr/etc\"   -fsigned-char -fno-common -Wall -Wextra -Waddress-of-packed-member -Wdiscarded-qualifiers -Wimplicit-function-declaration -Wmissing-declarations -Wmissing-parameter-type -Wmissing-prototypes -Wnested-externs -Wno-missing-field-initializers -Wpointer-arith -Wredundant-decls -Wsign-compare -Wstrict-prototypes -Wtype-limits -Wuninitialized -Wunused-but-set-parameter -Wunused-but-set-variable -Wunused-parameter -Wunused-result -Wunused-variable -Werror=sequence-point -O2 -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=3 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -flto=auto -ffat-lto-objects -D_GNU_SOURCE -c -o disk-utils/mkfs.cramfs.o disk-utils/mkfs.cramfs.c
[   98s] In file included from disk-utils/mkfs.cramfs.c:38:
[   98s] /usr/include/zconf.h:130:9: error: unknown type name 'uint32_t'
[   98s]   130 | typedef uint32_t z_crc_t;
[   98s]       |         ^~~~~~~~
[   98s] make[2]: *** [Makefile:9393: disk-utils/mkfs.cramfs.o] Error 1
[   98s] make[2]: *** Waiting for unfinished jobs....
[   98s] make[2]: Leaving directory '/home/abuild/rpmbuild/BUILD/util-linux-2.37.4'
[   98s] make[1]: *** [Makefile:14432: all-recursive] Error 1
[   98s] make[1]: Leaving directory '/home/abuild/rpmbuild/BUILD/util-linux-2.37.4'
[   98s] make: *** [Makefile:6254: all] Error 2

The error happened while building util-linux-2.37.4 in a staging project for openSUSE Tumbleweed, using latest develop branch.

Fixing this isn't easy as the standard headers must be included in specific order, otherwise the compilation will fail when building zlib-ng. As such, the issue must be fixed first in the headers distributed by the compilers before we can fix the issue in zlib-ng.
zlib-ng doesn't guarantee 100% source compatibility or that it can be compiled without changes using any of the common or uncommon compilers. Some changes we have introduced were for catching errors that zlib silently ignores and would cause unexpected behavior, including incorrect results due to integer widths being wider on 64-bit platforms... zlib itself supports only 16-bit and 32-bit platforms and does give no guarantee that it works correctly on 64-bit platforms.

We can change to unsigned int..

@nmoinvaz Changing it back to unsigned int would violate our style guide, but I guess that's inevitable if we want to avoid depending on broken system headers. If somebody tries to compile zlib-ng on system where it isn't exactly 32-bits, a lot more will likely be broken.

This is the relevant snippet from zlib:
#if !defined(Z_U4) && !defined(Z_SOLO) && defined(STDC)
#  include <limits.h>
#  if (UINT_MAX == 0xffffffffUL)
#    define Z_U4 unsigned
#  elif (ULONG_MAX == 0xffffffffUL)
#    define Z_U4 unsigned long
#  elif (USHRT_MAX == 0xffffffffUL)
#    define Z_U4 unsigned short
#  endif
#endif

#ifdef Z_U4
   typedef Z_U4 z_crc_t;
#else
   typedef unsigned long z_crc_t;
#endif

They are not using unsigned long unconditionally though.
Which is the issue in the compiler headers that you are referring to?

Which is the issue in the compiler headers that you are referring to?

Including stdarg.h before stdint.h will cause compiler errors, because the headers have circular dependency. This will be an issue when a function has variadic arguments.

This has been resolved in the develop branch.


No more debug output after removal of traffic.cop

There is no longer debug output in traffic.out since the removal of the traffic.cop process
-Enable debug
-Set debug string, e.g. http*
traffic.out not generated and no debug output seen

This was triggered by the elimination of traffic_cop.

Debug output is now going to traffic_server.stderr

Looks like there is a problem with systemd.

I changed the startup scripts to output stdout and stderr to traffic.out.  This is how traffic_cop handled it before.


Remove usage of SaaSType enum

Is your feature request related to a specific problem?
SaaS connectors are in constant development and having tests that rely on a hard-coded list of connectors or connector counts causes issues during new development. We have to maintain awareness of which tests to update when a new connector is added but ideally this shouldn't be the case.
Describe the solution you'd like

Remove the SaaSType enum
Update any tests that assert a specific SaaS connector count to rely on the count of SaaS connectors from the SaaS connector registry
Update any tests that rely on specific connectors to be present to be independent of which connectors are available

For example: test_search_connection_types and test_get_connection_types in tests/ops/api/v1/endpoints/test_connection_template_endpoints.py

There are ui dependencies on this. We will need to find another way to handle this on the frontend.


[stable/nginx-ingress] Remove stats exporter

A Prometheus metrics parser was added to nginx-ingress in 0.9-beta.3.
The separate stats exporter is no longer needed.

/cc @mgoodness @jackzampolin @chancez

/assign @lachie83

/lgtm


test(dm): add retry to avoid query-status test failed

What problem does this PR solve?

Issue Number: close https://github.com/pingcap/tiflow/issues/4134
What is changed and how it works?
Check List
Tests

No code

Release note
`None`.

Codecov Report

Merging #4144 (75f5a76) into master (3873d39) will decrease coverage by 1.8843%.
The diff coverage is 66.6384%.

Flag
Coverage Δ

cdc
58.7252% <66.6384%> (+0.4886%)
:arrow_up:

dm
52.1902% <ø> (-3.8444%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.
@@               Coverage Diff                @@
##             master      #4144        +/-   ##
================================================
- Coverage   57.0741%   55.1898%   -1.8844%
================================================
  Files           478        486         +8
  Lines         56551      60089      +3538
================================================
+ Hits          32276      33163       +887
- Misses        20978      23554      +2576
- Partials       3297       3372        +75

/merge


Mention that Markdown is parsed in @file/@overview as well?

First time using JSDoc. I see at http://usejsdoc.org/plugins-markdown.html that

This will cause Markdown in @description tags (including implicit descriptions without tags), @classdesc tags, @param tags, @property tags, and @returns tags to be parsed.

Practice shows that Markdown is parsed from @overview tags as well:
/**

@overview # Heading goes here

This module is the interface to the API. It provides access to objects, and formats
the response objects to a simple, linear model.
...
*/

Should @overview be added to the list of tags?

Thanks for pointing this out. The docs live in jsdoc3/jsdoc3.github.com, which is the right place to file doc issues. I've updated jsdoc3/jsdoc3.github.com#38 to get this cleaned up as well.


adding bskdany.com to the readme

What problem does this PR solve?
just adding my website to the readme
Is this PR adding a new feature?
no
Is this PR related to any issue or discussion?
no
PR Checklist

[ x ] I have verified that the code works as described/as intended.
[ ] This change adds a social icon which has a permissive license to use it.
[ x ] This change does not include any external library/resources.
[ x ] This change does not include any unrelated scripts (e.g. bash and python scripts).
[ x ] I have enabled maintainer edits for this PR.

@bskdany, I am glad you found this theme useful.
Thanks for listing your website.


[Bug]: Battery Values Incorrect

Adapter version 1.0
JS-Controller version 4.0.23
Node version 18.16
Operating system version Debian Bullseye
Values are x% below the values the eufy Security App shows.
x depends, currently 4% lower than the App, but if I restart the adapter values change, are 1% higher than before.
battery_temperature values are off the charts.
In the chart below battery values for 2 eufy2 cams are shown for the past 7 days

bropat added the fixed label
Sorry but I think you didn't.
Nothing changed....

Should be fixed in latest version.


Implementation of is.undefined?

Hello, there.
Is there a reason you used value === void 0; to check if value is undefined rather than typeof value === 'undefined'?
Thanks for the awesome library, btw.

As far as i know using value===void 0; is more efficient than typeof value==='undefined' or value===undefined

:+1: @omer-demir
undefined is a permissible variable name, so you can assign a new value to it.
void takes any value and returns undefined always. It's a convention to give 0 for `void' though.


Else indent off in soundingmaps.py

Hey Jack,
I just tried your latest version and I see that you made some changes to the else statements in soundingmaps.py.
However, it flags the else statement in line 169 as having an incorrect indent. Instead of trying to figure out your process here, I figured I'd just post an issue.
Would the new changes also throw off the following else statements in lines 222, and 261?
Thanks,
Nick Luchetti

Hi Nick,
Thanks for writing this up as a separate issue! I believe the 0.2.2 update I sent out yesterday should have corrected this. It is working on my end this morning. Let me know if that's not the case for you!
Jack


[FEATURE] chrome extension repo

Description
This project could use repo for a future chrome extension
Screenshots
No response
Additional information
No response

I think this would be part of another repo, so I will close


Gutter highlighting broken

This bug wasn't there in 4.1.0 but is in the latest nightly.
Create a new Dafny file.
Write manually (don't copy paste)
method Test() {
  assert false;
}

You'll get this::

After git bisecting, this regression appeared on merging #4201
I'll investigate.


Crashing on Linux for me

Transcribing..
[New Thread 0x7f040122d700 (LWP 226)]
[New Thread 0x7f0401a2e700 (LWP 227)]

Thread 33 "python" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f040122d700 (LWP 226)]
0x00007f044d9c8f41 in <lambda(int)>::operator() (ith=<optimized out>, __closure=0x1e3b430)
    at ./whisper.cpp/whisper.cpp:2089
2089    ./whisper.cpp/whisper.cpp: Is a directory.
Missing separate debuginfos, use: debuginfo-install keyutils-libs-1.5.8-3.amzn2.0.2.x86_64 krb5-libs-1.15.1-37.amzn2.2.2.x86_64 libcom_err-1.42.9-19.amzn2.x86_64 libffi-3.0.13-18.amzn2.0.2.x86_64 libgcc-7.3.1-13.amzn2.x86_64 libselinux-2.5-12.amzn2.0.2.x86_64 libstdc++-7.3.1-13.amzn2.x86_64 openssl-libs-1.0.2k-19.amzn2.0.8.x86_64 pcre-8.32-17.amzn2.0.2.x86_64 zlib-1.2.7-18.amzn2.x86_64
(gdb) where
#0  0x00007f044d9c8f41 in <lambda(int)>::operator() (ith=<optimized out>, __closure=0x1e3b430)
    at ./whisper.cpp/whisper.cpp:2089
#1  std::__invoke_impl<void, log_mel_spectrogram(float const*, int, int, int, int, int, int, const whisper_filters&, bool, whisper_mel&)::<lambda(int)>, int> (__f=...) at /usr/include/c++/7/bits/invoke.h:60
#2  std::__invoke<log_mel_spectrogram(float const*, int, int, int, int, int, int, const whisper_filters&, bool, whisper_mel&)::<lambda(int)>, int> (__fn=...) at /usr/include/c++/7/bits/invoke.h:95
#3  std::thread::_Invoker<std::tuple<log_mel_spectrogram(float const*, int, int, int, int, int, int, const whisper_filters&, bool, whisper_mel&)::<lambda(int)>, int> >::_M_invoke<0, 1> (this=0x1e3b428) at /usr/include/c++/7/thread:234
#4  std::thread::_Invoker<std::tuple<log_mel_spectrogram(float const*, int, int, int, int, int, int, const whisper_filters&, bool, whisper_mel&)::<lambda(int)>, int> >::operator() (this=0x1e3b428) at /usr/include/c++/7/thread:243
#5  std::thread::_State_impl<std::thread::_Invoker<std::tuple<log_mel_spectrogram(float const*, int, int, int, int, int, int, const whisper_filters&, bool, whisper_mel&)::<lambda(int)>, int> > >::_M_run(void) (this=0x1e3b420)
    at /usr/include/c++/7/thread:186
#6  0x00007f044d6c2acf in ?? () from /lib64/libstdc++.so.6
#7  0x00007f045531440b in start_thread () from /lib64/libpthread.

Updated to whisper.cpp master but still crashing.

The context struct might need updating if it has been changed in whisper.cpp.
Feel like there must be a better way of handling the definitions in cython; something similar to ctypes gen.

this might be related to #3

I went through the cython definition and the whisper.cpp one and they looked right.

In which case, can you first send the Python code you used to run this?
Is the model successfully loaded? Can you show the printed model info on load?
Also, if possible at some point, can you let me know if this still occurs using this ctypes generated solution described here? https://github.com/ggerganov/whisper.cpp/issues/9#issuecomment-1342138572
I have experienced something similar on Windows (including the ctypes implementation) (see #3  and https://github.com/ggerganov/whisper.cpp/issues/9#issuecomment-1360272368), however this didn't seem to occur at all on macOS. My previous hunch was that it's related to a threading issue as I did get some asserts complaining about rv!=0 on a Windows debug build, but now I'm unsure.

Sure thing. It loads the model and dies in transcribe:
from whispercpp import Whisper

w = Whisper('small')

result = w.transcribe("/audio.wav")
text = w.extract_text(result)
print(text)

I'm in Docker, running on Windows, using an Amazon Linux 2 kernel.

Should be fixed by commit https://github.com/stlukey/whispercpp.py/commit/d8c0617b0e1573e8e78d4f37d7f8967003e5a852 let me know if there's any further issues.


Add support for absolute imports

Currently only relative imports are supported for local packages, however that is definitely not the pythonic way to do things. In Python absolute imports are preferred over relative imports.
Also few things are difficult by just using relative imports:
# file: constants.py
A = "a"
B = "b"

# file: main.py
from .constants import A, B  # works fine
import .constants   # Doesn't work!

By this behaviour, Python functions app forces from ... import ... syntax which is not always preferred and many times against organization specific style guidelines.
Repro steps
Covered above.
Expected behavior
Absolute imports should be supported as per python guidelines.
Actual behavior
It fails!
Known workarounds
Use relative imports
Related information
On issue #81, relative imports are suggested.

@maiqbal11 moving this to sprint 44 to track the remaining work.

With #325, __app__ is the function application's top level module and can be used as an anchor for performing absolute imports.
Taking the following function example:
__app__
  Function1
    __init__.py
    func_module.py
  HelperCode
    __init__.py
    helper_module.py

We have support for the following sytaxes (as examples):

from __app__ import HelperCode
from __app__.HelperCode import helper_module
import __app__.Function1
import __app__.HelperCode

We do not currently have plans to support implicit relative imports of the form import func_module from within Function1.__init__.py. This is by design as it has the potential to cause conflicts with other libraries that are using the same module name. Explicit relative imports are preferred: from . import func_module.
@asavaritayal, we should be able to document the use of __app__ and close on this (plus other issue about absolute imports).

Thanks @maiqbal11 . Assigning myself for documenting.

One key point that I want to make sure gets documented is if you're going to require __app__ as the top-level directory, then anyone who wants to run their Function code outside of the Function runtime (e.g. CI for unit tests) must keep their entire Function directory in an __app__ folder in order for those imports to resolve appropriately. IOW this will will essentially dictate the folder name that everyone's Function-related files must be kept in if anyone chooses to use absolute imports.

Hello, I keep trying to import a local module into a Python function, without success.
Here's my project structure:
functions_python
    |_ ml-service
        | __init__.py
        | model_helper.py
        | function.json

I want to import model_helper into init, and here are some of the things I tried:
from . import model_helper (no module named model_helper)
from ..ml-service import model_helper (Invalid syntax)
from functions_python.ml-service import model_helper (Invalid syntax)
import functions_python.ml-service (Invalid syntax)
from app.ml-service import model_helper (Invalid syntax)
import app.ml-service (Invalid syntax)
I'm using Python 3.7 and not 3.6 - could it be the reason why I can't get this to work?

Hi @Kagigz, would it be possible to move your description to a separate issue? We can address it there. Just trying to keep this issue focused on what was originally being discussed :)

@maiqbal11 no problem! I've created another issue: #374

Addressed in this PR - https://github.com/MicrosoftDocs/azure-docs-pr/pull/78522

@maiqbal11 I am having a similar problem, as described in detail in https://github.com/Azure/azure-functions-python-worker/issues/577.  My functions were all working fine as of Oct 31, and without any code changes it is no longer working after upgrading VSC and Azure Functions core tools to the latest versions earlier this week.  I have tried numerous changes, including putting all the code folders under the __app__ directory, to no avail.  Any suggestions you can offer would be greatly appreciated!  Thank you for your time.

@dxkaufman please open a separate issue with all the details of your case and we can investigate.

@maiqbal11 i opened issue 577 for it.  Thank you!


Windows Front-End

Hello, will you ever make a Windows front-end to use your beautiful program?
Thank you.

Go is working on creating a library called "shiny" to allow the creation of GUIs. The other solutions that exist today are bindings to C. If I do that, I can no longer cross compile to any other system than my machine (64bit linux). Also they likely would be specific to a certain system.
At one point I wrote a web front end. Basically run the script, it gave you a URL, and you interacted with a web page, but I wasn't happy with it and never released it.

Thank you! :-)
You tell me a command that allows me to have the name of the game like this:
Astro Chase and not Astro Chase (USA)
And PNG covers at maximum resolution, THANK YOU !!!!

-use_nointro_name=false -img_format=png -max_width=0

Sorry, didnt mean to barge in announced :P But here is maybe helpfull information, since i am on Win and compiled throu GO.
Its super easy if u follow instructions for build on git first page all u have to do is to ammend $ from commands.
So example:
Open CMD with admin in folder where go.exe is and type in :
go get github.com/sselph/scraper
instead of
$ go get github.com/sselph/scraper
Have fun!


naming: resources

As commented here: https://github.com/inveniosoftware/invenio-rdm-records/pull/139 and in many others.

BlaBlaBlaRecordDraftResourceConfig, etc. are really long names. Shall we make ResourceConfig into an acronym? Otherwise shall we just call "Draft" and "Record".
What is a deposit? Shall we use it? if so, does it mean "draft" or "draft+resource"?

@fenekku @lnielsen @zzacharo This can be closed? I think we cleared out:

Deposit won't be used. Need name for draft+resource
Acronyms won't be used, it's true that is long, they are clear.

Here is my naming approach vote:
At the edge level (i.e. Authors, BibliographicRecords, Terms, Licenses...) just using <Name>Service (even if it inherits from draft service). For example: BibliographicRecordService is the service that deals with all functionalities for bibliographic records.
For Resources, variations in naming that reflect the endpoints is fine by me. (reiterates value in creating resources that could combine action endpoints too...)
If nothing else to discuss, we can close.


consider html parser from dom.js

reading http://www.davidflanagan.com/2011/10/html-parsing-wi.html you sure get the idea that the new parser in https://github.com/andreasgal/dom.js is hot shit.

is it hot shit?
should it be in jsdom?

I think it is absolutely worth looking into, not sure where the real speed comes from though. if I had to guess it'd be the dom implementation itself. Using weakmaps and friends allows dom.js to avoid costly caching operations (read: getElement(s)By* and NodeList).
parser source: https://github.com/andreasgal/dom.js/blob/master/src/impl/HTMLParser.js

@fgnass we've done some thinking about how the parser adaptors should look in #370.  Looks like a great start though!


Add ratio calculator

Deploy preview for recalc ready!
✅ Preview
https://recalc-1ivsv7e9p-tervay.vercel.app
Built with commit<PHONE_NUMBER>aadf452743d92fc478af5acdbe296f.
This pull request is being automatically deployed with vercel-action


Add additional best-practices for testing

This attempts to reflect existing best-practices, rather than
introducing new practices.
Motivation
A rising tide that lifts all test-reliability boats :)

(I didn't mention aliasing here since this is a testing-related document.. we can add that separately)

What other languages would that include?  I can add some text to scope these practices to Go, anyway.

Cool, thanks.  I have no objections to best-practices for other languages, too, but I also don't know what those best practices would be, so I'll let others write them or wait until I do know :)

(These docs may also evolve to be more than just testing best practices, and cover non-testing code too.. time will tell!)

Thanks for doing this!! 🙇


Fix docker build.

What changed?

Why?

How did you test it?

Potential risks

Release notes

Documentation Changes

Pull Request Test Coverage Report for Build 0182dc68-1191-4902-b8e3-63b9e6138b6c

0 of 0   changed or added relevant lines in 0 files are covered.
210 unchanged lines in 21 files lost coverage.
Overall coverage decreased (-0.1%) to 57.693%

Files with Coverage Reduction
New Missed Lines
%

common/task/weightedRoundRobinTaskScheduler.go
1
89.64%

client/history/client.go
2
38.1%

client/history/metricClient.go
2
45.3%

common/cache/lru.go
2
92.2%

common/membership/hashring.go
2
83.54%

common/persistence/persistenceMetricClients.go
2
55.17%

service/history/handler.go
2
47.3%

service/matching/taskListManager.go
2
76.37%

common/persistence/nosql/nosqlplugin/cassandra/workflow.go
3
56.99%

common/task/fifoTaskScheduler.go
3
84.54%

Totals

Change from base Build 0182dbf5-9874-4bf7-b37d-0af03eb9ba6d:
-0.1%

Covered Lines:
84222

Relevant Lines:
145984

💛  - Coveralls

Bash wasn't found in the image, but is needed to run scripts/check-gomod-version.sh, so I added it to the alpine image.

do we use any bash-isms?  we can very likely change that to use sh instead and get rid of bash.


Time interval difference between the real time visit and the visits Timline graph

Hello,
KP  displays visits with a difference (-1 hour) on the visits timline graph, on the dashboard, please see the attached files;

I was able to reproduce this, and the difference is due to how timezones are handled. All times are stored in UTC on the server and converted to the users local timezone in the client. In this case the Visits Timeline graphs was not converting the timestamps from UTC to local.
This has been fixed in commit d67e71d6, thanks for reporting it.

thank you , but can u please tell me how to correct this probleme, should i modify the code source on : king_phisher/client/graphs.py
first_visits = [visit.first_visit for visit in visits]

 first_visits = [utilities.datetime_utc_to_local(visit.first_visit) for visit in visits]

No you should never ever ever modify the code because if you do you will no longer be able to update without alot of additional complexity that I can't begin to support. You have to wait for the changes to be merged into the master branch or opt in to beta testing to get them now. If you choose to opt into beta testing, there are instructions in the wiki on how to do this.

Ok thank you;


[Event Request] codeunit 90 "Purch.-Post" - OnBeforePostCombineSalesOrderShipment

Please extend Event OnBeforePostCombineSalesOrderShipment with Handled pattern and with additional parameters. Also please include sender in this event.
    IsHandled: Boolean;
begin
    IsHandled := false;
    OnBeforePostCombineSalesOrderShipment(PurchHeader, SalesShptHeader, TempDropShptPostBuffer, ItemLedgShptEntryNo, ItemJnlPostLine, TempTrackingSpecification, TempHandlingSpecification, IsHandled);
    if IsHandled then
        exit;

[IntegrationEvent(true, false)]
local procedure OnBeforePostCombineSalesOrderShipment(var PurchaseHeader: Record "Purchase Header"; var SalesShptHeader: Record "Sales Shipment Header"; var TempDropShptPostBuffer: Record "Drop Shpt. Post. Buffer" temporary; var ItemLedgShptEntryNo: Integer; var ItemJnlPostLine: Codeunit "Item Jnl.-Post Line"; var TempTrackingSpecification: Record "Tracking Specification" temporary; var TempHandlingSpecification: Record "Tracking Specification" temporary; var IsHandled: Boolean)
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 41235.


using 'default' as an identifier results in a long series of utterly confusing messages

The following program gets six error messages in dartanalyzer:
   const default = const Object();
   void main() { }
They are:
   [error] Expected to find ';' (test.dart, line 1, col 7)
   [error] Expected an identifier (test.dart, line 1, col 7)
   [error] Unexpected token 'default' (test.dart, line 1, col 7)
   [error] Expected a method, getter, setter or operator
           declaration (test.dart, line 1, col 7)
   [error] The const variable 'default' must be initialized
           (test.dart, line 1, col 7)
   [error] A function body must be provided (test.dart, line 1,
           col 31)
It also gives one error when compiling:
   'test.dart': error: line 1 pos 1: unexpected token 'const'
None of these errors are useful. The useful error message here would be "default is a reserved word, and cannot be used as an identifier" or some such.

Down to 1 error message - "error • Expected an identifier at /tmp/try.dart:1:7 • missing_identifier"
Leaving the issue open since it could still be improved by changing to "default is not a valid identifier"


konduit.yaml RFC (basic implementation)

Konduit CLI for quick Python experiments
Install with python setup.py install from this folder. This will expose a CLI tool called
konduit. Assuming you have put a konduit.jar in the tests folder as described
in the main README.md, you can test this tool as follows:
cd tests
konduit --help

which should prompt all currently available commands, i.e.
Usage: konduit [OPTIONS] COMMAND [ARGS]...

Options:
  --help  Show this message and exit.

Commands:
  build          Build the underlying konduit.jar (again).
  init           Initialize the konduit-python CLI.
  predict-numpy  Get predictions for your pipeline from numpy input.
  serve          Serve a pipeline from a konduit.yaml
  stop-server    Stop the Konduit server associated with a given YAML file.

For more help on individual commands you can do
konduit serve --help

to get help for the serve command (and all others in the same way)
Usage: konduit serve [OPTIONS]

  Serve a pipeline from a konduit.yaml

Options:
  --config TEXT        Relative or absolute path to your konduit serving YAML file.
  --start_server TEXT  Whether to start the server instance after initialization.
  --help               Show this message and exit.

Basic usage
You should be in the tests folder still. There are a lot of YAML files in the yaml folder
to test Konduit with. Let's say we want to serve the pipeline described in yaml/konduit.yaml.
Let's have a look at it first:
serving:
  http_port: 1337
  input_data_type: NUMPY
  output_data_type: NUMPY
  log_timings: True
  extra_start_args: -Xmx8g
  jar_path: konduit.jar
  sleep: 1
steps:
  python_step:
    type: PYTHON
    python_path: .
    python_code_path: ./simple.py
    python_inputs:
      first: NDARRAY
    python_outputs:
      second: NDARRAY
client:
    url: http://localhost:1337

This Konduit experiment describes how your model will be run, what inputs it takes and
what types of output it will generate. In essence, this configuration will run the script
simple.py on input data that you can specify. To serve this Konduit pipeline you can
just run:
konduit serve --config yaml/konduit.yaml

and to get predictions from it you can use:
konduit predict-numpy --config yaml/konduit.yaml --numpy_data ../data/input-0.npy

@agibsonccc @ShamsUlAzeem this is ready now, please review again

@maxpumperla I saw that it needs a konduit.jar file all the time. If we don't have a konduit.jar file it won't show the --help details. Having it prompt something like, build konduit-serving before proceeding with konduit build --os windows-x86_64 or something along the lines would be helpful since most users won't know that we're using a konduit jar file under the hood. Or maybe we can build a konduit jar file on startup?


Limit number of tweets in the list in the newsroom

Reason/Context
In the new Newsroom section, among other items, we also display a list of tweets: https://www.asyncapi.com/community/newsroom
We do not have any limit there, so the list is getting long. You need to scroll a lot to get to the bottom.
Description
Set some limits on the number of tweets. I think 2 is the max, as, in the end, it is just about highlighting the latest and encouraging to see more on Twitter.
In code look for TwitterTimelineEmbed component in https://github.com/asyncapi/website/blob/master/components/newsroom/Newsroom.js
Looks like it can be easily achieved by adding another prop -> https://github.com/saurabhnemade/react-twitter-embed/blob/master/src/components/TwitterTimelineEmbed.tsx#L66
/gfi ts

/gfi ts

Agreed! I say we should make this change. Thanks for raising this, @derberg 🎉

Hi @derberg  I am new to open source I wanted to work on this issue just cloned the project. Is there is any specific thing that I need to keep in mind before contributing

@Jitulteron7 welcome 👋🏼 happy your first contribution will be to AsyncAPI 🍺
Things to remember:

do not clone this repo directly but fork it, and then follow -> https://github.com/asyncapi/community/blob/master/git-workflow.md to configure it properly on your local machine
then remember that the PR title should follow specify prefix -> https://github.com/asyncapi/.github/blob/master/CONTRIBUTING.md#conventional-commits

thanks @derberg for the quick relpy

hi @derberg  I am getting this error when i run npm run dev
wait  - compiling /_error (client and server)...
event - compiled client and server successfully in 213 ms (1573 modules)
error - components\newsroom\FeaturedBlogPost.js (11:15) @ FeaturedBlogPost
TypeError: Cannot read properties of undefined (reading 'type')
   9 |     let typeColors = ['bg-indigo-100', 'text-indigo-800']
  10 |
> 11 |   switch (post.type.toLowerCase()) {
     |               ^
  12 |     case 'video':
  13 |       typeColors = ['bg-pink-100', 'text-pink-800']

@Jitulteron7 you are probably using Windows. Sorry, I keep forgetting that we have issues on Windows :(
you will have to work in virtual environment -> https://github.com/asyncapi/website#spin-up-gitpod-codespace
just go to -> http://gitpod.io/#https://github.com/Jitulteron7/website and work on the project from there. It is like local but in the cloud 😄

Hey @derberg , I was working on solution for this one, but the version current being using website is 3.0.3, while latest version for react-twitter-embed is 4.0.4
Solution for 3.0.3:
<TwitterTimelineEmbed
                sourceType="profile"
                screenName="AsyncAPISpec"
                options={{ tweetLimit='1', height: 570, width: '100%' }}
              />

Solution for 4.0.4:
<TwitterTimelineEmbed
                sourceType="profile"
                screenName="AsyncAPISpec"
                options={{ height: 570, width: '100%' }}
                tweetLimit={1}
              />

As you can notice, diff is only where we put tweetLimit. Which way should I proceed?

Also, I did some experimentations, and found 2 tweetLimit with overflow-y-auto max-h-120 styling to match the NewsRoomArticle Components styling to be visually appealing. Here is screenshot for the same:

I say let's stay with 3.0.3 if we do not need to bump version to have tweet limit option
and yeah, from your showcase looks like we need to limit to 1 and not 2, right?

2 tweetLimit with overflow-y-auto max-h-120 would also work, if we want to have a fix height (same height as that of NewsroomArticle Component) of TweetTimelineEmbed Component, with minor to no scrolling. Else 1 would be good.

Kindly Review the PR: https://github.com/asyncapi/website/pull/910 Thank you!

hello @derberg  I have made changes as per the issue. It is looking like this

Thanks for this awesome cloud  vscode advice it is really amazing experience
One question is that how can I push my changes from the cloud to the project

hello @derberg I have made the changes as per the requirement. It is looking something like this

Thanks for this amazing advice on cloud vscode it is really cool.

hey @derberg  plz check my PR fix:Tweetui #914

Resolved by https://github.com/asyncapi/website/pull/804


fix: deploy with kontinuous

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Plugin is generally unreliable.

This is the worst bug report ever, and I won't blame you for closing it, but it's true.
Much of the time, SublimeLinter does not work. The reasons seem to be varied, but it is simply not very robust.
Just now, the jshint extension did not work. I put it into debug mode and there was no console output. I fixed this by deleting the folder's .jshintrc file and then restoring it.
The time before that, the culprit was a broken .eslintrc in a parent directory. Even though the directory that I was in had a good .eslintrc, the one above it seems to have caused the problem. This time, the debug console did print the shell command that it used to run eslint, but there was no indication of what the error might be.
Now, I agree, both of these issues were probably my fault. But comparing this plugin to something like JSHint Gutter, which seems to work no matter what you do, it's a much more frustrating experience. Might be good to have some sensible defaults or at least some better error reporting.

Either of those times, did you check that the linter itself worked from the command line?
As you probably know, SublimeLinter is a framework for simply running command line linters and searching the standard output for known values. This makes it pretty fragile between the user's setup ecosystem of software and SublimeText. JSHint Gutter, on the other hand, utilizes a builtin version of JSHint and a JS script to interact with the library directly instead of its command line output. Leaving the only obligation/fault/point-of-entry being where the user has their Node runtime. I realize it's frustrating when it fails to work, but where the blame lies is tougher to determine than a overall blanket at SL.

But comparing [SL] to something like JSHint Gutter, which seems to work no matter what you do, it's a much more frustrating experience.

Comparing this plugin to JSHint Gutter is comparing a swiss army knife to an allen wrench. The allen wrench (JSHint Gutter and the like) does one thing very well, but the swiss army knife (SL) has to do a whole lot of things, and sometimes, it's got what you need but it falls short comparatively to that one-purpose tool.
With that said, if the allen wrench does what you need it to, by all means use that :smile:. Let us know if you come across those problems again and what the linter's command line output says.
Thanks for the voice though!


LOGIN] Failed to login TypeError: Cannot read properties of undefined (reading 'split')

i can't publish

[LOGIN] Failed to login TypeError: Cannot read properties of undefined (reading 'split')
at D:\shoppe\node_modules\threads-api\build\threads-api.js:1:5064
at D:\shoppe\node_modules\threads-api\build\threads-api.js:1:1798
at Object.next (D:\shoppe\node_modules\threads-api\build\threads-api.js:1:1903)
at a (D:\shoppe\node_modules\threads-api\build\threads-api.js:1:379)
at i (D:\shoppe\node_modules\threads-api\build\threads-api.js:1:576)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

I am also getting this error. Notably, however, I am also encountering the same error when logging in with Meta's Threads application. So I am thinking that this is not a problem with this library, but that we are temporarily banned from Threads by Meta.
(I think it can be pointed out that the current threads-api model is to log in to threads for each execution, and this can easily lead to banning. A simple mechanism to serialize login sessions and use them across executions may be required.)

If you don't want to log in for each execution, you should persist your auth token somewhere, in a DB for example, and reuse that in future executions

I am also getting this error. Notably, however, I am also encountering the same error when logging in with Meta's Threads application. So I am thinking that this is not a problem with this library, but that we are temporarily banned from Threads by Meta.
(I think it can be pointed out that the current threads-api model is to log in to threads for each execution, and this can easily lead to banning. A simple mechanism to serialize login sessions and use them across executions may be required.)

As @wack-overflow said to prevent login each time you can run the code using userID and token, you can get them with getToken and getUserIDfromUsername plus you can pass device identifier and device id so it doesn't trigger the "Unauthorized login" each time you do something, this just a measure to lower the chances Instagram flags the account as compromised or spam.

@Aerglonus Could you show us the code how you can login with token and userId ?

@Aerglonus Could you show us the code how you can login with token and userId ?

Just pass the values to client, in my case i passed some extra properties to avoid requesting new values each time and also avoid getting the account flagged as if it was compromised because of the different deviceID, so my deviceID its the one from my actual phone and on device I passed also my phone actual specifications that way Instagram thinks its login in from my already authorized phone.

Note: the device and fbLSDToken properties are not  necessary I just use them as an extra step to not trigger any flags on Instagram side..

const threadsAPI = new ThreadsAPI({
  verbose: true,
  device: {
    manufacturer: 'your-phone-manufacturer',
    model: 'your-phone-model',
    os_version: android-version,
    os_release: 'phone-os-version',
  },
  fbLSDToken: 'redacted',
  noUpdateLSD: true,
  token: 'redacted', // Your token
  deviceID: 'android-redacted', // Your device ID
  userID: 'redacted'
});

For those who were having problems finding some of these values, I used an app called Device Info on the Google play store to get the device ID. The rest should be easily available in the settings (model, os version, etc.)

@Aerglonus I tried your approach, but didn't work for me. Here is the code.
const threadsAPI = new ThreadsAPI({
			verbose: true,
			noUpdateLSD: true,
			token,
			userID
		});
const user = await threadsAPI.getUserProfile(userID);

The result:
TypeError: Cannot read properties of undefined (reading 'userData')
    at a.<anonymous> (/Users/taishi/Desktop/threads-engagement-app/node_modules/threads-api/build/threads-api.js:1:9626)
    at /Users/taishi/Desktop/threads-engagement-app/node_modules/threads-api/build/threads-api.js:1:1769
    at Object.next (/Users/taishi/Desktop/threads-engagement-app/node_modules/threads-api/build/threads-api.js:1:1874)
    at a (/Users/taishi/Desktop/threads-engagement-app/node_modules/threads-api/build/threads-api.js:1:350)
    at i (/Users/taishi/Desktop/threads-engagement-app/node_modules/threads-api/build/threads-api.js:1:547)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

@Aerglonus I tried your approach, but didn't work for me. Here is the code.
const threadsAPI = new ThreadsAPI({
			verbose: true,
			noUpdateLSD: true,
			token,
			userID
		});
const user = await threadsAPI.getUserProfile(userID);

The result:
TypeError: Cannot read properties of undefined (reading 'userData')
    at a.<anonymous> (/node_modules/threads-api/build/threads-api.js:1:9626)
    at /node_modules/threads-api/build/threads-api.js:1:1769
    at Object.next (/node_modules/threads-api/build/threads-api.js:1:1874)
    at a (/node_modules/threads-api/build/threads-api.js:1:350)
    at i (/node_modules/threads-api/build/threads-api.js:1:547)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

This could be related to what i was seeing recently, when using getToken that returns the userID as undefined this is a new issue related to the data that comes back from Threads


Add aria-label to Spinner component

Closes https://github.com/github/primer/issues/2202

This adds a new option for setting the accessible label of the Spinner component. When it's not provided, we default to "Loading" so you have to intentionally hide the element with label="". Where we find Loading state is communicated to screenreader users twice in dotcom, we can set this label value to "", I have intentionally opted for the most accessible default so it over communicates rather than under-communicating the loading state.
Changelog

New
label option on Spinner component. Defaults to "Loading". When set (or left as default) it adds aria-label={label} to the Spinner's svg.
Adds role="img" to the svg element.
If the label is set to an empty string, it adds aria-hidden='true' to the svg element.
Changed

Removed

Rollout strategy

[ ] Patch release
[x] Minor release
[ ] Major release; if selected, include a written rollout or migration plan
[ ] None; if selected, include a brief description as to why

Testing & Reviewing

Merge checklist

[x] Added/updated tests
[x] Added/updated documentation
[ ] Added/updated previews (Storybook)
[ ] Changes are SSR compatible
[ ] Tested in Chrome
[ ] Tested in Firefox
[ ] Tested in Safari
[x] Tested in Edge
[ ] (GitHub staff only) Integration tests pass at github/github (Learn more about how to run integration tests)

So interestingly, the loading spinner is used on TextInput (via TextInputInnerVisualSlot) - need to work out whether we want to make it aria-hidden or not 🤔

@broccolinisoup I had not seen that, thanks for bringing it to my attention!

Converting to draft because there's ongoing discussions about this component.

Going to close this. We need to handle it differently anyway!


Augment decorator

resolves #841
model Foo {name: string}

@@doc(Foo, "This is some post doc");
@@doc(Foo.name, "This is some more post doc");

op test(): Foo;

https://cadlplayground.z22.web.core.windows.net/prs/1036/?c=bW9kZWwgRm9vIHtuYW1lOiBzdHJpbmd9CgpAQGRvYyhGb28sICJUaGlzIGlzIHNvbWUgcG9zdCBkb2MiKTvKJS7EPtAqbW9yzi8Kb3AgdGVzdCgpOsR0Ow%3D%3D
Todo:

[x] Add docs for website
[x] Formatter
[x] Spec emu

Rules:

Cannot use augment decorator inside a namespace. It can be used inside a blockless namespace but not within a block one.

It can be used inside a blockless namespace but not within a block one.

Hmm, this feels like an arbitrary rule to me. Why do we have this rule?

I am curious what @bterlson thinks on this. We can refine it later so I'll review the rest and we shouldn't block on it.
My gut is that making more ways blockless is different from blockful is not great, though.


Har file is not created

I am trying to create a har file with the following code, however there is no har file saved anywhere. This used to work previously, but I don't know from which Browser version is not working anymore since I am not updating regularly.
*** Settings ***
Library    Browser    strict=False

*** Test Cases ***

Test Har
    New Browser    chromium    headless=false
    ${har_data} =    Create Dictionary    path=test.har    omitContent=False
    New Context    recordHar=${har_data}
    New Page    https://edition.cnn.com/
    Wait For Elements State    text=World
    Close Page
    Close Context
    Close Browser

Most likely har file is created, but it is created in the installation directory. Try this one:  ${har_data} =    Create Dictionary    path=${OUTPUTDIR}/test.har    omitContent=False

Thanks. This issue was caused initially by https://github.com/microsoft/playwright/issues/11435. Closing a context created with recordHar would hang my test runs, so as a quick solution I commented out Close Context but then har file was not created. Later I discovered this playwright issue and that if I Close Page before Close Context, it will not hang test runs.


Improve implementation of open solvers for SBGrid

We want a set of working open solvers to be able to put qFit into SBGrid

IMO, this was done in #363, which reimplemented cvxopt (QP), osqp (QP) and miosqp (MIQP).
Or is this just an issue to track until dev is merged with main?

The open MIQP solver does not work currently (https://github.com/osqp/miosqp)

It crashes? Doesn't load?
Can you give me a crash log, and I'll look into it tonight?

This issue is with the following line:
class MIOSQPSolver(MIQPSolver):
driver_pkg_name = "miosqp"
driver = lazy_load_module_if_available(driver_pkg_name)
if TYPE_CHECKING:
import miosqp
The import fails. This package is not included in osqp. (https://github.com/osqp/miosqp)

That's correct. miosqp is a separate package.
Unfortunately though, the authors haven't distributed it in the pip repositories, only on GitHub.
It's not installing for 2 reasons:

I made a mistake in setup.py. Where it says extra_dependencies, it should read extras_require.
Even if that was fixed: it's not obvious, but when you install qfit with pip install . (or pip install qfit one day, I guess), you'd have to specify the set of qfit "extensions" you'd like in square-brackets (pip install .[osqp] or pip install .[cplex,osqp]).[^cplex]

Since we need to have at least one set of solvers, we should probably make the osqp solvers default, and just include them straight up in the install_requires. This would satisfy SBGrid.
I will put in a PR to fix this tomorrow morning?
[^cplex]: Even then, cplex is only partially available through pip, so this only really works on old macs, or on linux machines.

Completed in a different PR


Adding Ludium and ATS reporting forms for kevin

Just needed to add a community.  Question for you @alexkeating

[ ] When we add a community, should we still push to staging first?
[ ] To add a community, should the flow be 'Govrn remote staging' => 'local' => 'Aaron Remote' => 'Govrn remote'?  Or should we do the first pull from 'Govrn remote master'

We should still merge into staging


gen: discriminator property is removed from structures

The discriminator field is removed from the generated structs. Suppose some API endpoint accepts a String and not a TypeDef and it expects to receive the kind property. Currently, the generated API client can not call such an endpoint since it wont be including the discriminator field. There could also be cases where the value of the discriminator property is useful for other things than deciding the type. Should it not always be included in the types? Especially if I manually put it as a required field like in the example below.
What version of ogen are you using?
$ go list -m github.com/ogen-go/ogen

github.com/ogen-go/ogen v0.81.0

Can this issue be reproduced with the latest version?
Yes
What did you do?
TypeDef:
  oneOf:
    - $ref: '#/components/types/String'
    - $ref: '#/components/types/Int'
  discriminator:
    propertyName: kind
    mapping:
      string: '#/components/types/String'
      int: '#/components/types/Int'

String:
  type: object
  required:
   - kind
  properties:
    kind:
      type: string
Int:
  type: object
  required:
   - kind
  properties:
    kind:
      type: string

What did you expect to see?
// Ref: #/components/types/String
type String struct{
    Kind string `json:"kind"`
}

// Ref: #/components/types/Int
type Int struct{
    Kind string `json:"kind"`
}

What did you see instead?
// Ref: #/components/types/String
type String struct{}

// Ref: #/components/types/Int
type Int struct{}

@johanhenriksson did you find a workaround for this issue?
The only thing I've found it to define a kind of type alias to use in oneOf schema, e.g.
StringForDiscriminator:
  allOf:
    - $ref: '#/components/types/String'
    - type: object
      properties:
         kind:
           type: string

In that case we have 2 objects generated, one to be used in the case with discriminator, and another one without. But it looks a bit ugly, tbh.

So having following schema
openapi: 3.0.3
info:
  title: Discriminator example
  description: Example
  version: 1.0.0
paths:
    /example:
      get:
        responses:
          200:
            description: OK
            content:
              "application/json":
                schema:
                    $ref: '#/components/schemas/Response'
components:
  schemas:
    Alpha:
      type: object
      required:
        - kind
        - variant
        - data
      properties:
        kind:
          type: string
        variant:
          type: string
        data:
          type: string
    Beta:
      type: object
      required:
        - kind
        - variant
        - value
      properties:
        kind:
          type: string
        variant:
          type: string
        value:
          type: string
    SumAuto:
      oneOf:
        - $ref: '#/components/schemas/Alpha'
        - $ref: '#/components/schemas/Beta'
    SumFirst:
      discriminator:
        propertyName: kind
        mapping:
          alpha: '#/components/schemas/Alpha'
          beta: '#/components/schemas/Beta'
      oneOf:
        - $ref: '#/components/schemas/Alpha'
        - $ref: '#/components/schemas/Beta'
    SumSecond:
      discriminator:
        propertyName: variant
        mapping:
          a: '#/components/schemas/Alpha'
          b: '#/components/schemas/Beta'
      oneOf:
        - $ref: '#/components/schemas/Alpha'
        - $ref: '#/components/schemas/Beta'
    Response:
      type: object
      required:
        - Auto
        - First
        - Second
        - Alpha
        - Beta
      properties:
        Auto:
          $ref: '#/components/schemas/SumAuto'
        First:
          $ref: '#/components/schemas/SumFirst'
        Second:
          $ref: '#/components/schemas/SumSecond'
        Alpha:
          $ref: '#/components/schemas/Alpha'
        Beta:
          $ref: '#/components/schemas/Beta'

Discriminator properties are removed from Alpha and Beta, but should not.
@tdakkota please take a look.

@vkuptcov I have not found a good workaround to this, no. We managed to do without it, but having the discriminator field on the generated types would make life easier.


suggest to use npm ci in example && typo fix

In short, the main differences between using npm install and npm ci are:

The project must have an existing package-lock.json or npm-shrinkwrap.json.
If dependencies in the package lock do not match those in package.json, npm ci will exit with an error, instead of updating the package lock.
npm ci can only install entire projects at a time: individual dependencies cannot be added with this command.
If a node_modules is already present, it will be automatically removed before npm ci begins its install.
It will never write to package.json or any of the package-locks: installs are essentially frozen.

From: https://docs.npmjs.com/cli/ci

Use npm ci to ensure npm install packages according to package-lock.json.

Thank you for your contribution. This is indeed a very useful improvement.

Hi @sma11black I found I missed one typo:
https://github.com/sma11black/hexo-action/blob/3d8f6f64ca070c069a7bb6db099e085b5f5454af/README.md#L86
Maybe you can fix it latter?

@binotaliu I found that you have fixed this "delete" typo. Is it because you didn’t refreshed your webpage?

@sma11black Yes, I did a refresh. It's now delele (two l) on master (Line 86) while it should be delete.

@binotaliu OK, I fixed it now. 😂


[http-client-python] update for eng

Fix eng

No changes needing a change description found.

You can try these changes here

🛝 Playground
🌐 Website
📚 Next docs


Cache is empty

I was wondering if someone has experienced this problem where despite creating a cache successfully, the cache itself is empty. This makes it impossible to return items using objectAtIndex:

Oops never mind. Bug issue on our end!


Feature: UnivNet implementation

Thanks for your great work!
I want to implement univnet vocoder but your model is written in  haiku and jax numpy.
https://github.com/mindslab-ai/univnet
I followed your convert code but got stuck:

jax numpy has no function unfold or to or transpose ?
How can I fix that problems ?

If I were you, I would use the pytorch implementation instead of reimplementing the model in haiku/jax.
You will need to convert the predicted mel spectrogram to pytorch's tensor for your vocoder model.
An example:
mel = HaikuTacotron(text)
mel = jax.device_get(mel)
mel = torch.from_numpy(mel)
wav = TorchVocoder(mel)

Output shape of Acoustic model is : x = [1 151 80]
But  shape of input in Vocoder is: [1 80 151]
How to fix this ?  I also tried to reshape tensor from [1 151 80] to [1 80 151] by torch,reshape but it's didn't work.

Ah, thank you! All done!


Timestamps before epoch would be inserted into Vector with +1s.

Added/fixed tests:

properly generate dates/timestamps
generate null values too
properly verify that the expected output and the result are the same

ship it


Reply in threads?

The bot will not react / reply inside a thread, where @-pinged. (scenario: users are discussing in a thread and then pings the bot)  I can see in the log that it reacts to the call, but is not responding... I've added the rights in the .yml file.

Hi @Christolito, thank you for writing in!
Regarding ignoring mentions in a thread, it is an intentional behavior.
When a user includes the ChatGPT bot in an existing conversation with other humans after certain interactions, receiving a bot reply suddenly for every single message after that could be quite surprising to other people in the thread. This is why I hesitate to change the behavior.
My recommendation is to begin a new thread for interactions with the ChatGPT bot. If you would like to include messages from a different thread as context, please copy and paste those message texts when starting the new thread.

Thats a good point! Thanks..


Complex scalars for Algodiff

It would be nice to have support for complex scalars in the Algodiff module.
This would require the addition of a Owl_maths_complex module first.

A new owl_base_complex module has been added to support complex number maths. Unit tests only has place holder so not fully tested, use with care.
Check the ref: http://www.cl.cam.ac.uk/~lw525/owl/apidoc/owl_base_complex.html


[Backport 2.0.x]: Upgrade helm procedure test

Backport fix https://github.com/apache/camel-k/pull/4927
Release Note
[NONE](fix: Helm upgrade procedure with CRD management)

Do we need to backport to 2.0.x? I doubt we are going to make any release on 2.0.x branch.

There has been some other documentation change added and this feature from what I could see.


Add SoftwareApp metadata

To allow Google to better index details of the cards.
https://developers.google.com/search/docs/data-types/software-app

This isn't generally available and so isn't worth working on yet.


Disconnect with book content and exercise file layout

The exercise file layout in the book's screenshots for lesson 2 look very different from the code in this repository.  The package names are different between the book and repo.  This makes it very difficult to follow along with the content of the book.

That shouldn't be the case, can you elaborate where it differs?

You didn't provide any pointers, so I'll close this one. Feel free to reopen it when you can provide more information.


Replace HTML comment

Use JSX comment instead of HTML comment. so they won't appear in production.

@jamesli2021 Thanks for the suggestion! ☺


Feature: Enable the ability to use cy.log outputs as "steps" in cucumber.json for reports

Current behavior
Currently when using cy.log, all of the output is ignored. None of it is output into cucumber.json files which are generally used in reports. This makes it difficult to view what's happening inside my step definitions during a test run on CI.
Desired behavior
I would like to be able to see my cypress logs in the json file so that I can easily view it alongside the rest of the test output.
E.X If I have this test (I know it's trivial):
Scenario: I log in and post a tweet
  Given I am logged in
  And I go to the homepage
  When I post a tweet with text "tweet"
  Then I see my tweet with text "tweet"

And I have this step definition with this command:
// in commands.ts
Cypress.Commands.add('login', (username: string, password: string) => {
  cy.log('Logging in as user', username || Cypress.env('user').email)
  cy.APIRequest({
    method: 'POST',
    url: '/accounts/login/',
    body: {
      username: username || Cypress.env('user').email,
      password: password || Cypress.env('user').password,
  });
});

// in login.cucumber.ts
Given(/^(I am logged in|I log in)$/, () => {
  cy.login();
});

I have other commands that generate users and save them to env variables, so at runtime I want to know what they are for logging purposes. So I'd like to be able to view my report that says something like this on CI by pulling it out of the test output.
 Given I am logged in
 LOG Logging in as user<EMAIL_ADDRESS>  .........

Please let me know if I can clarify in any way.

Due to personal reasons, the previous maintainers of this package are stepping down and handing the reigns over to me, a long-time contributor to the project and a user of it myself. This is a responsibility I'm very excited about. Furthermore, I'd like to thank @lgandecki ++ for all the work that they've done so far.
Read more about the transfer of ownership here.
The repository has however moved and all outstanding issues are being closed. This is not a reflection of the perceived importance of your reported issue. However, if after upgrading to the new version, you still find there to be an issue, feel free to open up another ticket or comment below. Please make sure to read CONTRIBUTING.md before doing so.

Is this feature added??

https://github.com/badeball/cypress-cucumber-preprocessor/blob/master/docs/json-report.md#attachments


Heroku Memory Exceeded

The Heroku instances are exceeding their memory and are being constantly killed and recycled. We need to figure out why this is occurring:
2015-06-07T02:52:37.067350+00:00 heroku[web.1]: Process running mem=2632M(514.1%)
2015-06-07T02:52:37.067350+00:00 heroku[web.1]: Error R15 (Memory quota vastly exceeded)

The best thing to do is try to figure out the exact reason why the memory bottleneck is occurring.

I'm taking a look at the dev app using the bullet gem to see if we have any greedy queries in the mix.

cautiously closing this after following sugggestions from Heroku support:
"Hi there,
I see it seems to settle into R14 errors under little traffic, that's problematic. Running oink in production all the time is definitely not recommended, so consider turning it off it is running in production.
Another simple course of action in this case might be to lower WEB_CONCURRENCY to 1. Seeing as it is on a 1X dyno anyway, and the vCPU count is only 1 there isn't too much benefit to having Puma run with multiple workers. The Puma worker count is usually the largest consumer of memory, so if you can lower the worker count and perhaps consider increasing the thread count you can often get some good savings.
Hope that helps,
Steven"


Seasonstatus

Season status is now 100% width div and can be added into the full layout later.

Closes #164 and #158


Error

[00:19:30 ERROR]: Could not pass event EntityDamageByEntityEvent to Citizens v2.0.22-SNAPSHOT (build 1498)
org.bukkit.event.EventException: null
at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:306) ~[minecraft_server.jar:git-Spigot-4bd94dc-c765646]
at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:62) ~[minecraft_server.jar:git-Spigot-4bd94dc-c765646]
at org.bukkit.plugin.SimplePluginManager.fireEvent(SimplePluginManager.java:500) [minecraft_server.jar:git-Spigot-4bd94dc-c765646]
at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:485) [minecraft_server.jar:git-Spigot-4bd94dc-c765646]
at org.bukkit.craftbukkit.v1_12_R1.event.CraftEventFactory.callEvent(CraftEventFactory.java:93) [minecraft_server.jar:git-Spigot-4bd94dc-c765646]
at org.bukkit.craftbukkit.v1_12_R1.event.CraftEventFactory.callEntityDamageEvent(CraftEventFactory.java:580) [minecraft_server.jar:git-Spigot-4bd94dc-c765646]
at org.bukkit.craftbukkit.v1_12_R1.event.CraftEventFactory.handleEntityDamageEvent(CraftEventFactory.java:483) [minecraft_server.jar:git-Spigot-4bd94dc-c765646]
at org.bukkit.craftbukkit.v1_12_R1.event.CraftEventFactory.handleNonLivingEntityDamageEvent(CraftEventFactory.java:631) [minecraft_server.jar:git-Spigot-4bd94dc-c765646]
at org.bukkit.craftbukkit.v1_12_R1.event.CraftEventFactory.handleNonLivingEntityDamageEvent(CraftEventFactory.java:617) [minecraft_server.jar:git-Spigot-4bd94dc-c765646]
at net.minecraft.server.v1_12_R1.EntityFireball.damageEntity(EntityFireball.java:171) [minecraft_server.jar:git-Spigot-4bd94dc-c765646]
at net.minecraft.server.v1_12_R1.EntityArrow.a(EntityArrow.java:286) [minecraft_server.jar:git-Spigot-4bd94dc-c765646]
at net.minecraft.server.v1_12_R1.EntityArrow.B_(EntityArrow.java:194) [minecraft_server.jar:git-Spigot-4bd94dc-c765646]
at net.minecraft.server.v1_12_R1.EntityTippedArrow.B_(EntityTippedArrow.java:86) [minecraft_server.jar:git-Spigot-4bd94dc-c765646]
at net.minecraft.server.v1_12_R1.World.entityJoinedWorld(World.java:1631) [minecraft_server.jar:git-Spigot-4bd94dc-c765646]
at net.minecraft.server.v1_12_R1.World.h(World.java:1601) [minecraft_server.jar:git-Spigot-4bd94dc-c765646]
at net.minecraft.server.v1_12_R1.World.tickEntities(World.java:1435) [minecraft_server.jar:git-Spigot-4bd94dc-c765646]
at net.minecraft.server.v1_12_R1.WorldServer.tickEntities(WorldServer.java:665) [minecraft_server.jar:git-Spigot-4bd94dc-c765646]
at net.minecraft.server.v1_12_R1.MinecraftServer.D(MinecraftServer.java:817) [minecraft_server.jar:git-Spigot-4bd94dc-c765646]
at net.minecraft.server.v1_12_R1.DedicatedServer.D(DedicatedServer.java:406) [minecraft_server.jar:git-Spigot-4bd94dc-c765646]
at net.minecraft.server.v1_12_R1.MinecraftServer.C(MinecraftServer.java:679) [minecraft_server.jar:git-Spigot-4bd94dc-c765646]
at net.minecraft.server.v1_12_R1.MinecraftServer.run(MinecraftServer.java:577) [minecraft_server.jar:git-Spigot-4bd94dc-c765646]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_74]
Caused by: java.lang.ClassCastException: org.bukkit.craftbukkit.v1_12_R1.entity.CraftLargeFireball cannot be cast to org.bukkit.entity.LivingEntity
at org.mcmonkey.sentinel.SentinelTrait.whenAttacksHappened(SentinelTrait.java:390) ~[?:?]
at sun.reflect.GeneratedMethodAccessor180.invoke(Unknown Source) ~[?:?]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_74]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_74]
at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:302) ~[minecraft_server.jar:git-Spigot-4bd94dc-c765646]
... 21 more

Did you make a fireball NPC and give it the Sentinel trait?

Or are you maybe on an older version? http://ci.citizensnpcs.co/job/Sentinel/

Most cases when I see the failed to pass event thing, it's just when the plugins exceeded the time in which one should of told citizens that an npc/player got hurt.
You could try making sure your server and the plugins are up to date and, from what a non-coder like me can tell, the error seems to be thrown when you use projectiles. There might be something interfering with how projectiles path/damage is delt with. Like I mean something might be blocking the damage and/or registering the path/entity as it's own, rather than have been shot by the player.
If the NPC is being hurt during theses errors then, that might be because of versions. As normal Minecraft and some plugins can track damage delt and register things like knockback and hp and use it as intended, but that doesn't necessarily means that citizens/sentinel picked up on it. Sure the server and other plugins say you hit the npc as it thinks it's a mob or player, but citizens/sentinel isn't picking up on the damage entity event.
The reason for the error, is most likely the versions of Citizens an the server. Why? Because as things update, methods are often changed to work differently, get removed, or updated to work better. Thus either your server or the plugin is using an older method and so it doesn't communicate property.
Such as:
"Could not pass event EntityDamageByEntityEvent to Citizens v2.0.22-SNAPSHOT (build 1498)
org.bukkit.event.EventException: null"
"EntityDamageByEntityEvent" might end up being called something like "DamageByEntityEvent" or like have "EntityDamagedByPlayerEvent" & "EntityDamageByMobEvent" to serve a purpose as to either change the methods name or give it capabilities, with the player/mob event one, those could allow coders to detect if a mob or player is hitting an entity.
If versions are outdated, they won't register (use or reconize) the events in use because the server isn't coded to run the events the plugin has.
That or you just have some grade A laaaag.... in which cases I call lagtastic.

Uh... none of that made much sense @Midnight9746 :/
My earlier replies are what it would be: Either a non-living NPC (a fireball NPC) was given a Sentinel trait for some hilarious reason, or just an outdated version of Sentinel.
For reference, the portion of the error you quoted doesn't even particularly matter much, the most significant area is:
 Caused by: java.lang.ClassCastException: org.bukkit.craftbukkit.v1_12_R1.entity.CraftLargeFireball cannot be cast to org.bukkit.entity.LivingEntity at org.mcmonkey.sentinel.SentinelTrait.whenAttacksHappened(SentinelTrait.java:390) ~[?:?]
That's the exact error at fault (a LargeFireball entity was assumed to be a Living entity by some section of code, but of course is not) and as well the exact line of code it occurred on (by pathname and line number).

No i had no Fireball as npc and sentinel together .

Then your copy of the plugin was outdated.


[🐛] Cannot fetch pub packages in macOS

Describe the bug
When I try to search a package EG: at_contacts. It shows an error message.
To Reproduce
Steps to reproduce the behavior:

Go to the pub tab
Search for a package

Expected behavior
It must show the resulting packages list.
Screenshots

Desktop (please complete the following information):

OS: macOS

Logs (please upload the logs file by following the instructions):
Unable to generate logs.

This is not an issue. The search feature is in pre-release. Nothing should work properly in it.

This issue was raised as of the feature available.

This issue was raised as of the feature available.

Well, the feature is partially available. As stated in the pre-release tag.

Will keep this open until the search for pub packages becomes stable.

This issue has been fixed with the latest push. Please pull the changes and check to see if it works as expected.

I will update this sometime later

If you are experiencing this issue still, please file it in a new issue.

Please close this with a valid fix

FYI this is for MacOS not for any other platforms. So please keep this opened until this is fixed

If you are experiencing this issue still, please file it in a new issue.
Keep this in mind. THIS is now CLOSED. Reference it in a new issue if it persists.

But why new ticket? when we already have one here

Last time, this issue has been fully resolved in a recent commit. Please DO NOT reopen this issue one more time. If you have anything that doesn't work, create a separate issue for it. Once an issue IS CLOSED, it REMAINS CLOSED.

Once an issue IS CLOSED, it REMAINS CLOSED

@ZiyadF296 Any specific reason?

Consistency. It's not about whether or not the author likes the fix. And it's not up to the author if the fix works or not. The person who created the fix has tested it on their own machine. If you test on your own machine and it doesn't work then that is a separate issue that is specific to your machine, which should be filed in a new issue to fix that system specific issue.

the author likes the fix.

FYI Please watch them.
I never said I like it or dislike it. Moreover, this issue/ticket was raised with a platform-specific.
The ticket handler(@ZiyadF296) has removed the platform-specific tag and asking to duplicate the issue now?

The person who created the fix has tested it on their own machine.

Can you please provide what machine it is and a screenshot of it so that I(the ticket author) can make sure of confirming the fix?
Again FYI duplication of tickets is a bad practice of managing a project as a team. So would like to reopen it again with the above reason mentioned. Hoping you will provide a macOS fix but not a Windows/Linux fix.

This has been fixed. Please check the LATEST COMMIT.

I didn't have to mention that this ISSUE IS FIXED. IT IS NOT PLATFORM-SPECIFIC. STOP REOPENING ISSUES. You aren't even contributing to this project to be bossing and managing around here.

I used to. Still, I can but there are quite some complications to contribute to this. And moreover, respect the customers.

Launching lib[/main.dart]() on macOS in debug mode...
lib/main.dart:1
--- xcodebuild: WARNING: Using the first of multiple matching destinations:
{ platform:macOS, arch:x86_64, id:99C53EBE-5E59-52B9-A911-CAB3325DD8FC }
{ platform:macOS, name:Any Mac }
Connecting to VM Service at ws://<IP_ADDRESS>:59079[/ZgWzw9U6t_Y]()=[/ws]()
flutter: 📂 AppData path: [/Users/minnu/Library/Application]() Support[/FlutterMatic]()
[log] INFORMATION [01:11:13] - Dark theme setter set to true.
[log] INFORMATION [01:11:14] - : 208.67 GB out of 229.37 GB left
[log] INFORMATION [01:11:14] - : 0.47 GB out of 0.48 GB left
[log] WARNING [01:11:14] - Disk  has only 0.47 left.
[log] INFORMATION [01:11:14] - : 0.47 GB out of 0.47 GB left
[log] WARNING [01:11:14] - Disk  has only 0.47 left.
[log] INFORMATION [01:11:14] - : 208.67 GB out of 209.12 GB left
[log] INFORMATION [01:11:14] - : 208.67 GB out of 208.68 GB left
[log] INFORMATION [01:11:14] - : 0.47 GB out of 0.48 GB left
[log] WARNING [01:11:14] - Disk  has only 0.47 left.
[log] INFORMATION [01:11:14] - : 208.67 GB out of 432.38 GB left
[log] INFORMATION [01:11:14] - : 208.67 GB out of 214.67 GB left
[log] INFORMATION [01:11:14] - DEVFS: 0.00 GB out of 0.00 GB left
[log] WARNING [01:11:14] - Disk DEVFS has only 0.00 left.
[log] INFORMATION [01:11:14] - : 208.67 GB out of 229.37 GB left
[log] ERROR [01:11:14] - Drive conflicting error found. Drives: [/dev/disk3s1](), [/dev/disk1s1](), [/dev/disk1s3](), [/dev/d...]()
[log] INFORMATION [01:11:14] - Disk space check passed. Disk is writable.
[log] WARNING [01:11:14] - Lost connection. FlutterMatic is offline.
[log] INFORMATION [01:11:15] - Back online. FlutterMatic is online.
[log] INFORMATION [01:11:15] - Dart version: 2.16.1
[log] INFORMATION [01:11:15] - Dart channel: stable
[log] INFORMATION [01:11:16] - VSCode found on system: 1.64.2
[log] INFORMATION [01:11:16] - ADB found on system: 1.0.41
[log] INFORMATION [01:11:17] - Flutter found on system: 2.10.2
[log] INFORMATION [01:11:17] - Java found on system: 1.8.0-321
[log] INFORMATION [01:11:17] - Git found on system: 2.32.0
[log] INFORMATION [01:11:21] - No new FlutterMatic version found. Current version: v0.0.1-alpha

Like 4 mins

I haven't crossed the line of respect, my friend. As a matter of fact, I have been trying to explain all along that this issue is solved, and you fail to notice that. I think that we can just leave this issue closed because:

It wasn't a bug
It isn't platform-specific
It is a feature request (and it is implemented)

I think that you didn't look over the issue very well, instead, you just are logging issue after issue, without uploading the log files saved on your system, associating the wrong tags, always adding the macOS tag, before confirming in any way that it is only on macOS and not also on windows or linux. You don't tag them as triage at first to get opinions and ideas and a proven log that shows the issue taking place. This is not well coordinated and needs to change.
Having to deal with fixing all issues as soon as they are created so that I can make each individual using this app satisfied with minimal complications with errors is surely no easy task. Additionally, you are adding the burden of dealing with all of this rather than following the extremely simple set of instructions for how issuing on this repo should work and is supposed to work.
If you can't keep up with these simple instructions, then simply you don't have to file these issues or be related to this app in any way, it's isn't a requirement, and nobody is forcing you to do any of this. This is a free contribution you are providing, and you are crossing the line in some zones.
I am sure anyone using this app appreciates each and every single contributor, but come on, we must have a fun little zone of ours where we respect one another and keep this open-source community toxic-free. It's a sheer will, but worthy.
Think about it, lets follow a consistent ticketing scheme that I suggested and have been using since the beginning. That is all I am asking for, only that.
In any case, I do appreciate you filling and catching sneaky glitches and bugs across the app, I really do.

Launching lib[/main.dart]() on macOS in debug mode...
lib/main.dart:1
--- xcodebuild: WARNING: Using the first of multiple matching destinations:
{ platform:macOS, arch:x86_64, id:99C53EBE-5E59-52B9-A911-CAB3325DD8FC }
{ platform:macOS, name:Any Mac }
Connecting to VM Service at ws://<IP_ADDRESS>:59079[/ZgWzw9U6t_Y]()=[/ws]()
flutter: 📂 AppData path: [/Users/minnu/Library/Application]() Support[/FlutterMatic]()
[log] INFORMATION [01:11:13] - Dark theme setter set to true.
[log] INFORMATION [01:11:14] - : 208.67 GB out of 229.37 GB left
[log] INFORMATION [01:11:14] - : 0.47 GB out of 0.48 GB left
[log] WARNING [01:11:14] - Disk  has only 0.47 left.
[log] INFORMATION [01:11:14] - : 0.47 GB out of 0.47 GB left
[log] WARNING [01:11:14] - Disk  has only 0.47 left.
[log] INFORMATION [01:11:14] - : 208.67 GB out of 209.12 GB left
[log] INFORMATION [01:11:14] - : 208.67 GB out of 208.68 GB left
[log] INFORMATION [01:11:14] - : 0.47 GB out of 0.48 GB left
[log] WARNING [01:11:14] - Disk  has only 0.47 left.
[log] INFORMATION [01:11:14] - : 208.67 GB out of 432.38 GB left
[log] INFORMATION [01:11:14] - : 208.67 GB out of 214.67 GB left
[log] INFORMATION [01:11:14] - DEVFS: 0.00 GB out of 0.00 GB left
[log] WARNING [01:11:14] - Disk DEVFS has only 0.00 left.
[log] INFORMATION [01:11:14] - : 208.67 GB out of 229.37 GB left
[log] ERROR [01:11:14] - Drive conflicting error found. Drives: [/dev/disk3s1](), [/dev/disk1s1](), [/dev/disk1s3](), [/dev/d...]()
[log] INFORMATION [01:11:14] - Disk space check passed. Disk is writable.
[log] WARNING [01:11:14] - Lost connection. FlutterMatic is offline.
[log] INFORMATION [01:11:15] - Back online. FlutterMatic is online.
[log] INFORMATION [01:11:15] - Dart version: 2.16.1
[log] INFORMATION [01:11:15] - Dart channel: stable
[log] INFORMATION [01:11:16] - VSCode found on system: 1.64.2
[log] INFORMATION [01:11:16] - ADB found on system: 1.0.41
[log] INFORMATION [01:11:17] - Flutter found on system: 2.10.2
[log] INFORMATION [01:11:17] - Java found on system: 1.8.0-321
[log] INFORMATION [01:11:17] - Git found on system: 2.32.0
[log] INFORMATION [01:11:21] - No new FlutterMatic version found. Current version: v0.0.1-alpha

Like 5 mins @ZiyadF296

This is a different issue :) please create a new issue for it. It's not related to this one ✌

okie please tell me what this issue should be named

It's your issue, whatever is suitble should be named.

this suits and this is the issue getting continued :(

Did you take your time to read this message?

I haven't crossed the line of respect, my friend. As a matter of fact, I have been trying to explain all along that this issue is solved, and you fail to notice that. I think that we can just leave this issue closed because:

It wasn't a bug
It isn't platform-specific
It is a feature request (and it is implemented)

I think that you didn't look over the issue very well, instead, you just are logging issue after issue, without uploading the log files saved on your system, associating the wrong tags, always adding the macOS tag, before confirming in any way that it is only on macOS and not also on windows or linux. You don't tag them as triage at first to get opinions and ideas and a proven log that shows the issue taking place. This is not well coordinated and needs to change.
Having to deal with fixing all issues as soon as they are created so that I can make each individual using this app satisfied with minimal complications with errors is surely no easy task. Additionally, you are adding the burden of dealing with all of this rather than following the extremely simple set of instructions for how issuing on this repo should work and is supposed to work.
If you can't keep up with these simple instructions, then simply you don't have to file these issues or be related to this app in any way, it's isn't a requirement, and nobody is forcing you to do any of this. This is a free contribution you are providing, and you are crossing the line in some zones.
I am sure anyone using this app appreciates each and every single contributor, but come on, we must have a fun little zone of ours where we respect one another and keep this open-source community toxic-free. It's a sheer will, but worthy.
Think about it, lets follow a consistent ticketing scheme that I suggested and have been using since the beginning. That is all I am asking for, only that.
In any case, I do appreciate you filling and catching sneaky glitches and bugs across the app, I really do.

I haven't crossed the line of respect, my friend. As a matter of fact, I have been trying to explain all along that this issue is solved, and you fail to notice that. I think that we can just leave this issue closed because:

It wasn't a bug
It isn't platform-specific
It is a feature request (and it is implemented)

I think that you didn't look over the issue very well, instead, you just are logging issue after issue, without uploading the log files saved on your system, associating the wrong tags, always adding the macOS tag, before confirming in any way that it is only on macOS and not also on windows or linux. You don't tag them as triage at first to get opinions and ideas and a proven log that shows the issue taking place. This is not well coordinated and needs to change.
Having to deal with fixing all issues as soon as they are created so that I can make each individual using this app satisfied with minimal complications with errors is surely no easy task. Additionally, you are adding the burden of dealing with all of this rather than following the extremely simple set of instructions for how issuing on this repo should work and is supposed to work.
If you can't keep up with these simple instructions, then simply you don't have to file these issues or be related to this app in any way, it's isn't a requirement, and nobody is forcing you to do any of this. This is a free contribution you are providing, and you are crossing the line in some zones.
I am sure anyone using this app appreciates each and every single contributor, but come on, we must have a fun little zone of ours where we respect one another and keep this open-source community toxic-free. It's a sheer will, but worthy.
Think about it, lets follow a consistent ticketing scheme that I suggested and have been using since the beginning. That is all I am asking for, only that.
In any case, I do appreciate you filling and catching sneaky glitches and bugs across the app, I really do.

we can talk about this private thing somewhere else but it isn't about toxicity. You aren't providing a valid reason to file a new issue.

Moreover, I can't find the logs where I choose. and not in the application support dir. It is empty BTW

this suits and this is the issue getting continued :(

I am the one who wrote the code, I know what is what. This code is not related at all to the code of the search. It is completely two different things. This issue is a feature. And the 5 minute loading error is a bug. Please just follow simple instructions and create a new issue, please. For our sake. Please. I don't have to beg for you to listen for once. lets make this simple and straightforward.

Moreover, I can't find the logs where I choose. and not in the application support dir. It is empty BTW

Really? Hmm... file a new issue for that too.

What the duck is this? How many times i should file a ticket of the same?

These are all different issues you are mentioning.


Support hx-on:event

keys in python can't have - or :. And while a user can get around this by doing:
Div(**{"hx-on:click": "thing"}

I don't really like that.
Thankfully htmx also supports having -s instead of all these colons ref the doc

Finally, in order to make this feature compatible with some templating languages (e.g. JSX) that do not like having a colon (:) in HTML attributes, you may use dashes in the place of colons for both the long form and the shorthand form:

<!-- These two are equivalent -->
<button hx-get="/info" hx-on-htmx-before-request="alert('Making a request!')">
    Get Info!
</button>

<button hx-get="/info" hx-on--before-request="alert('Making a request!')">
    Get Info!
</button>

So I think we should just keep to underscores and also allow double underscores.
Div(hx_on_click="js string")

Div(hx_on_htmx_before_request="alert('Making a request!')")

Div(hx_on__before_request="alert('Making a request!')")

closed by: #21


DaprBindingTrigger not triggering when running dapr locally

I have been developing azure function (tried both isolated and in process model) which utilizes the Dapr trigger binding, set to connect to Azure Service Bus. Azure function is supposed to get invoked with new message landing in the queue. When testing the setup locally I noticed very strange behavior. If I run the app using dapr run command, function doesn't get invoked. However if I start functions project via VS Code and only then start dapr, the trigger gets invoked on the already running function instance
This is my dapr.yaml file which I reference in command dapr run -f . -H 3500
version: 1
common:
  resourcesPath: ./components
apps:
  - appDirPath: ./functions-be
    appID: functionapp
    command: ["func", "host", "start"]
    appPort: 3001
    daprHTTPPort: 3500
    logLevel: ''
    enableApiLogging: true    ```

And this is my service bus component:

apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: servicebus
spec:
type: bindings.azure.servicebusqueues
version: v1
metadata:

name: connectionString # Required when not using Azure Authentication.
value: "Endpoint=sb://.servicebus.windows.net/;SharedAccessKeyName=policy1;SharedAccessKey=;EntityPath=queue1"
name: queueName
value: "queue1"

May I know where is your function app running AKS or ACA or on-prem?


[e2e]: delegator-generic workflow_dispatch main checkout slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/8273369064
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.delegator-generic.workflow_dispatch.main.checkout.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.delegator-generic.workflow_dispatch.main.checkout.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Thu Mar 14 00:16:27 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/8289284811
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.delegator-generic.workflow_dispatch.main.checkout.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.delegator-generic.workflow_dispatch.main.checkout.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Fri Mar 15 00:16:40 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/8303755674
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.delegator-generic.workflow_dispatch.main.checkout.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.delegator-generic.workflow_dispatch.main.checkout.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Sat Mar 16 00:16:15 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/8311490581
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.delegator-generic.workflow_dispatch.main.checkout.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.delegator-generic.workflow_dispatch.main.checkout.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Sun Mar 17 00:17:57 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/8319319277
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.delegator-generic.workflow_dispatch.main.checkout.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.delegator-generic.workflow_dispatch.main.checkout.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Mon Mar 18 00:17:28 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/8319319277
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.delegator-generic.workflow_dispatch.main.checkout.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.delegator-generic.workflow_dispatch.main.checkout.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Mon Mar 18 19:27:24 UTC 2024

Hopefully fixed in https://github.com/slsa-framework/example-trw/pull/3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/8335416957
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.delegator-generic.workflow_dispatch.main.checkout.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.delegator-generic.workflow_dispatch.main.checkout.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Tue Mar 19 00:17:12 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/8351846741
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.delegator-generic.workflow_dispatch.main.checkout.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.delegator-generic.workflow_dispatch.main.checkout.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Wed Mar 20 00:16:11 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/8364997811
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.delegator-generic.workflow_dispatch.main.checkout.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.delegator-generic.workflow_dispatch.main.checkout.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Wed Mar 20 20:09:56 UTC 2024
Tests are passing now. Closing this issue.


🗽New Feature: support youtube / netflix

how to get youtube subtitle, by content script or API?
maybe this help I'll check it when i am available.
https://github.com/kyamashiro/youtube-subtitle-download-helper

how to get netflix subtitle?

build an UI to display subtitle,  should highlight text before display.

start supporting youtube transcript element from ffb38dc11a60ec74a29bcfcd3b4c6626d5ca5341

there is a problem:
the transcripts / subtitles / captions are often lack of sufficient context. it could be very short, like 2 or 3 words, and you might not know what's that exactly.
So, saving only one sentence in transcript might not always be a good choice as my own opinion. That's one of the reason that i do not make the caption in youtube be selectable. and the second reason is that is troublesome 😥.
What I mean is, using the transcript function that built-in the youtube, you can get as much context as you want! (though it is not that easy to select 😅)


fix: 修复中英文标点符号

👀 PR includes

✨ Feature

[ ] New feature

🎨 Enhance

[ ] Code style optimization
[ ] Refactoring
[ ] Change the UI
[ ] Improve the performance
[ ] Type optimization

🐛 Bugfix

[x] Solve the issue and close #2440

🔧 Chore

[ ] Test case
[ ] Docs / demos update
[ ] CI / workflow
[ ] Release version
[ ] Other ()

📝 Description

🖼 Screenshot

Before
After

❌
✅

🔗 Related issue link

🔍 Self-Check before the merge

[ ] Add or update relevant docs.
[ ] Add or update relevant demos.
[ ] Add or update test case.
[ ] Add or update relevant TypeScript definitions.

希望跟 vue 组件保持一致，把前后括号去掉，我已经改好了
https://github.com/antvis/S2/pull/2443

建议这样改
https://github.com/antvis/S2/pull/2443#issuecomment-1835701058

啥时候发版呀

:tada: This PR is included in version @antv/s2-v1.52.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version @antv/s2-v1.53.0-alpha.3 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version @antv/s2-react-v1.45.0-alpha.2 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Adds BooleanVariable

Coverage increased (+0.2%) to 87.214% when pulling 51e7b22410fa145e9a0673af046b9b6431090bd3 on jt/boolean_variable into 3e78c13adc88315ec82b1b2d933c376eca6a7c8f on master.

Coverage increased (+0.2%) to 87.214% when pulling 51e7b22410fa145e9a0673af046b9b6431090bd3 on jt/boolean_variable into 3e78c13adc88315ec82b1b2d933c376eca6a7c8f on master.

Coverage increased (+0.2%) to 87.214% when pulling 51e7b22410fa145e9a0673af046b9b6431090bd3 on jt/boolean_variable into 3e78c13adc88315ec82b1b2d933c376eca6a7c8f on master.


updated sponsor file to correct misspelling

Dinis asked me to correct this

Thanks for the correction Kelly.

Rock and roll @kellysantalucia  :)


zipfile.BadZipFile: File is not a zip file

I'm trying to run it for Python 3.6 and getting this error why try to run the given example.
from tenseflow import change_tense

change_tense('I will go to the store.', 'past')

Error:
Traceback (most recent call last):
  File "<input>", line 1, in <module>
  File "/home/irfan/.local/share/JetBrains/Toolbox/apps/PyCharm-P/ch-0/201.7846.77/plugins/python/helpers/pydev/_pydev_bundle/pydev_import_hook.py", line 21, in do_import
    module = self._system_import(name, *args, **kwargs)
  File "/home/irfan/PycharmProjects/tenseflow/tenseflow/__init__.py", line 1, in <module>
    from .change_tense import *
  File "/home/irfan/.local/share/JetBrains/Toolbox/apps/PyCharm-P/ch-0/201.7846.77/plugins/python/helpers/pydev/_pydev_bundle/pydev_import_hook.py", line 21, in do_import
    module = self._system_import(name, *args, **kwargs)
  File "/home/irfan/PycharmProjects/tenseflow/tenseflow/change_tense.py", line 3, in <module>
    from pattern.text.en import conjugate, PAST, PRESENT, SINGULAR, PLURAL
  File "/home/irfan/.local/share/JetBrains/Toolbox/apps/PyCharm-P/ch-0/201.7846.77/plugins/python/helpers/pydev/_pydev_bundle/pydev_import_hook.py", line 21, in do_import
    module = self._system_import(name, *args, **kwargs)
  File "/home/irfan/PycharmProjects/tenseflow/.tense/lib/python3.6/site-packages/pattern/text/en/__init__.py", line 80, in <module>
    from pattern.text.en import wordnet
  File "/home/irfan/.local/share/JetBrains/Toolbox/apps/PyCharm-P/ch-0/201.7846.77/plugins/python/helpers/pydev/_pydev_bundle/pydev_import_hook.py", line 21, in do_import
    module = self._system_import(name, *args, **kwargs)
  File "/home/irfan/PycharmProjects/tenseflow/.tense/lib/python3.6/site-packages/pattern/text/en/wordnet/__init__.py", line 57, in <module>
    nltk.data.find("corpora/" + token)
  File "/home/irfan/PycharmProjects/tenseflow/.tense/lib/python3.6/site-packages/nltk/data.py", line 557, in find
    return find(modified_name, paths)
  File "/home/irfan/PycharmProjects/tenseflow/.tense/lib/python3.6/site-packages/nltk/data.py", line 544, in find
    return ZipFilePathPointer(p, zipentry)
  File "/home/irfan/PycharmProjects/tenseflow/.tense/lib/python3.6/site-packages/nltk/compat.py", line 41, in _decorator
    return init_func(*args, **kwargs)
  File "/home/irfan/PycharmProjects/tenseflow/.tense/lib/python3.6/site-packages/nltk/data.py", line 396, in __init__
    zipfile = OpenOnDemandZipFile(os.path.abspath(zipfile))
  File "/home/irfan/PycharmProjects/tenseflow/.tense/lib/python3.6/site-packages/nltk/compat.py", line 41, in _decorator
    return init_func(*args, **kwargs)
  File "/home/irfan/PycharmProjects/tenseflow/.tense/lib/python3.6/site-packages/nltk/data.py", line 936, in __init__
    zipfile.ZipFile.__init__(self, filename)
  File "/usr/lib/python3.6/zipfile.py", line 1131, in __init__
    self._RealGetContents()
  File "/usr/lib/python3.6/zipfile.py", line 1198, in _RealGetContents
    raise BadZipFile("File is not a zip file")
zipfile.BadZipFile: File is not a zip file

Okay, after googling I found the solution related to nltk packages.
https://github.com/clips/pattern/issues/252


feat: add styling to signIn btn solves #241

Fixes #
Describe the changes you have made in this PR -
I have added the styling to the sign-in button so that it could be differentiated between buttons and links to improve the UI.
Screenshots of the changes (If any) -

Hence solves the issue #241
Note: Please check Allow edits from maintainers. if you would like us to assist in the PR.

already fixed by #212

Hey @Arnabdaz  if there is any enhancement in button  sign-in, that  is required please let me know.

nope atm there is already a pr #176


Update README.md to hyperlink pr-20

That's strange. I thought GitHub auto linked PRs and issues by the #20 number. Guess this isn't the case for the README. Oh well.


vectorize process + enable early quitting/storage + enable delete ann…

BACKPORTED FROM https://github.com/Itseez/opencv/pull/6382
What does this PR change?
This PR adds new updated functionality to the OpenCV annotation tool

The complete pipeline has been vectorized so that modifications are easier then directly converting the rectangles to string format as what was being done in the past.

[Feature Request] We enabled early quitting and storage option: in the past, pressing the ESC key earlier in the annotation process closed down the annotation tool, but left you with no annotation file of the work done being present. We adapted the storage of the results, so that at any time during the process, when you decide to leave using the ESC button, the results to that point are being stored.

[Feature Request] We added a delete option. Since the annotations are stored inside a vectorized structure, deleting the last added annotation is fairly simple now. This allows users to correct wrongful annotations, without needing to restart the application.

A video of the functionality can be seen below
https://youtu.be/EV5gmvoCTSk

@mshabunin Applied the suggested fixes, going to take a look why it failed for the master branch ...

Looks good to me. :+1:

Then who do we assign to this to get it merged? :yum:

Oh great! Feel free to add the master one also!


Using Row status With Selection

Hey guys!
Got a question. I have a table where I am using both row status and selected. It is working great except that when a row is selected, it is not updating the row background color to the default color (of which it should when using the selected property), but is rather staying in the row status background color. With this said do I have to use one or the other or can I get them to work together? I would prefer for them to work together.
Thanks!

@tytondon1234 You should compare row in row-class function with selected. In this case you don't apply your custom class.

Hey Walter,
Okay. Is there any way that you could give me a snippet of an example of
this in practice? No worries if not.
Thanks!
On Nov 24, 2017 12:02 PM, "Walter Tommasi"<EMAIL_ADDRESS>wrote:

@tytondon1234 https://github.com/tytondon1234 You should compare row in
row-class function with selected. In this case you don't apply your custom
class.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rafaelpimpa/buefy/issues/438#issuecomment-346877506,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARgHI8OPGPIC49zv1sYu36eNwB84fNGyks5s5wTIgaJpZM4QqFQk
.

https://jsfiddle.net/3tufc7de/2/
As default the selected row with custom style has inverted color but if you check the switch component you can see what i told you (if selected is equal to current row -> no class, for example empty string)

Wow! Thanks @jtommy! You are the best! :)