iOS simulator in Android Platform Mode

Hi,
I'm having some difficulties and after some confusion, it appears to be that when running the react-native application in the iOS simulator, the application appears to think it's on the Android Platform and is trying to render some components accordingly when on an iOS device. The app works fine on an android device with no errors but in the iOS simulator, it does not. There are various parts of the app which will error such as:

Note this isn't any platform specific code but cross-platform and this error is only occurring in the iOS simulator and otherwise works on an Android device.
Even with adding in a platform checker such as for event listeners for Androids back button, the platform OS is equaling android even though it's the iOS simulator.
Thanks, this is slightly confusing me particularly the last screen as this is just for a regular TextInput .... standard components and nothing platform specific.

Hi again,
... Basically, there was a bad equality checker of:
if (Platform.OS = 'android') { ...
for
    componentDidMount() {
        if (Platform.OS === 'android') {
            BackAndroid.addEventListener('hardwareBackPress', this.handleBackOnOverlay);
        }

Which resulted in the event listener being added for the android back button in the iOS app. The above errors were showing as a result of this it seems. Never assume the error message is the error as such.


Getting an error when trying to create a new input field on create ticket

I have a very complicated problem here. I followed the tutorial on the issue #454.

Publish views so you can edit the html layout of the form: php artisan vendor:publish

Publishing the view and adding the new input field was easy, here is what i added:
{!! CollectiveForm::text('address', null, ['class' => 'form-control', 'required' => 'required']) !!}

Create a migration that extends the table ticketit with fields you want.

And on phpmyadmin, i made this:

And it has its own index too, just like the "subject" one.

Override TicketsController so that in the store method you can add the functionality to store extra fields. This is how to override a vendor class (read the comments too): https://stackoverflow.com/a/34600074

I created the overrides folder and added the "autoload" thing into composer.json
Now for the problem im having:
When i try to submit the new ticket, i get this error:
SQLSTATE[HY000]: General error: 1364 Field 'address' doesn't have a default value (SQL: insert into ticketit (subject, content, html, priority_id, category_id, status_id, user_id, agent_id, updated_at, created_at) values (TEST SUBJECT, TEST DESC, TEST DESC, 1, 1, 1, 1, 1, 2020-01-29 19:01:41, 2020-01-29 19:01:41))
And if i add a default value to "address" on phpmyadmin, or if i make it nullable, it will be an empty field or the default value i set.
Basically, the "address" data is not being sent to the database, and i have no idea why.

try to add 'address' to fillable=['address',...] in the tickite model


[Enhancement][Lake] Add some metrics and logs for compaction jobs

What type of PR is this：

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

[FE PR Coverage Check]
:disappointed: fail : 2 / 50 (04.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/lake/compaction/CompactionScheduler.java
0
47
00.00%
[106, 123, 129, 131, 132, 133, 151, 152, 154, 155, 156, 157, 166, 252, 253, 344, 345, 356, 357, 358, 359, 360, 361, 362, 363, 364, 365, 366, 367, 368, 369, 370, 371, 372, 373, 374, 375, 445, 446, 449, 453, 454, 457, 461, 462, 465, 469]

:large_blue_circle:
com/starrocks/lake/compaction/CompactionManager.java
1
2
50.00%
[106]

:large_blue_circle:
com/starrocks/common/Config.java
1
1
100.00%
[]

run starrocks_be_unittest

[FE PR Coverage Check]
:disappointed: fail : 2 / 50 (04.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/lake/compaction/CompactionScheduler.java
0
47
00.00%
[106, 123, 129, 131, 132, 133, 151, 152, 154, 155, 156, 157, 166, 252, 253, 344, 345, 356, 357, 358, 359, 360, 361, 362, 363, 364, 365, 366, 367, 368, 369, 370, 371, 372, 373, 374, 375, 445, 446, 449, 453, 454, 457, 461, 462, 465, 469]

:large_blue_circle:
com/starrocks/lake/compaction/CompactionManager.java
1
2
50.00%
[106]

:large_blue_circle:
com/starrocks/common/Config.java
1
1
100.00%
[]

starrocks_be_unittest succeeded.

[FE PR Coverage Check]
:disappointed: fail : 0 / 45 (00.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/lake/compaction/CompactionManager.java
0
1
00.00%
[106]

:large_blue_circle:
com/starrocks/lake/compaction/CompactionScheduler.java
0
44
00.00%
[119, 125, 127, 128, 129, 147, 148, 150, 151, 152, 153, 162, 248, 249, 352, 353, 354, 355, 356, 357, 358, 359, 360, 361, 362, 363, 364, 365, 366, 367, 368, 369, 370, 371, 441, 442, 445, 449, 450, 453, 457, 458, 461, 465]

starrocks_be_unittest succeeded.


Added missing import to __init__.py

Fixed a missing import.

Codecov Report

Merging #53 into master will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master      #53   +/-   ##
=======================================
  Coverage   79.37%   79.37%
=======================================
  Files          77       77
  Lines        9624     9625    +1
  Branches     1234     1234
=======================================
+ Hits         7639     7640    +1
  Misses       1930     1930
  Partials       55       55

Impacted Files
Coverage Δ

hikari/__init__.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


fix(react-loadable): add missing  webpack optimize

Deploy preview ready!
Built with commit 99886d0ff1801344bd9d1a9bc2ecca21cb4950dc
https://deploy-preview-328--mcs-lite-introduction.netlify.com

Deploy preview ready!
Built with commit 99886d0ff1801344bd9d1a9bc2ecca21cb4950dc
https://deploy-preview-328--mcs-lite-ui.netlify.com


helping GC free memory faster

when troubleshooting a memory leak i realized that object references remain in Event objects even after all other references where removed.  Events returning to their object pools currently keeps target and currentTarget values and prevents the GC from freeing those objects.
Running cpp.vm.Gc.trace  on one of my memory intensive movieclips reviled  that it was not released due to a reference in an inactive event object.
Class referenced from:
MarkClassStatics.(null)
openfl.events.Event.__pool
ObjectPool.__inactiveObject0    <------
Event.target
MovieClip.__totalFrames
...

this pull request should fix this by clearing  target and currentTarget when Events are returned to the object pool.

Accidentally committed manually
https://github.com/openfl/openfl/commit/0b07276fded91fd6b30b8520683eab3e872a9623
Thank you :smile:


Add argument --ssh-port to my_init

Hi,
My deployment needs to start several baseimage docker instances on the same physical host. But there is no way to specify the ssh listening port in a flexible way. That's why I add the argument --ssh-port to my_init, so that the ssh server port can be changed before running the image.
Usage:
docker run YOUR_IMAGE /sbin/my_init --ssh-port=SOME_PORT

The default port is 22.
SSH still needs to be enabled first.

nice addition!
+1 for merge to master

I'll create a feature branch and do the PR again.


Login error: Invalid TDS stream: Unknown token type: 0

Getting the error below when using the driver to access a table in my database.
"Login error: Invalid TDS stream: Unknown token type: 0" . What could I be doing wrong?

You are probably connecting to something that is not an MSSQL server


Impossible to use docker logs (at least when using journald)

After some small modifications to home-assistant's supervised-installer (see https://github.com/home-assistant/supervised-installer/pull/140) I've been able to correctly install and use hassio in my raspberry pi4 running Ubuntu with docker-snap.
Once it's installed in a snap-readable prefix all works fine, but unfortunately it seems that logs are not properly readable via docker logs homeassistant (even though I can read them via journalctl):
Dec 29 00:57:33 uberry docker.dockerd[1760]: time="2020-12-29T00:57:33.891258733+01:00" level=error msg="Handler for GET /v1.40/containers/23984b41e39fbb180ce14baf502c5e86975216cde6ca0b481ddf863c4a05a63f/logs returned error: configured logging driver does not support reading"

To be clear, I've modified (before installing hassio) my $(snap run --shell docker -c 'printenv SNAP_DATA')/config/daemon.json to use:
{
    "log-level":        "error",
    "storage-driver":   "overlay2",
    "log-driver":       "journald"
}

Nice catch!  I've opened https://github.com/docker-snap/docker-snap/pull/17 which should hopefully fix this (however, it might also require the log-observe interface to be defined and connected -- need to wait for the GitHub Actions to finish there to determine for sure because my local environment is always wonky/permissive about things like that).

@tianon finally got time to test this again, works great!
Thanks


nestjs microservice kafka

Hello,
I like your library but i wanted to know how it is different from nestjs microservice kafka transport?

Hi @kodeine,
The main difference is that the nestjs microservice transport uses a request reply channel pattern for communication, where as this library allows your to subscribe to any topic and produce to any topic. This then allows you to build microservices that could transform that data and push to a new topic for example. This library also support Avro message encoding and decoding.
Hope that answers your question?

@rob3000 yep it answers my question, looks like i'll migrate to this lib.
Also, does this library validate the dto's?

Hey @kodeine not sure i understand what you mean by the dto's?

input validation using class-validator.

Ah! So it kind of does that if you are using the Avro Serialiser as when a message is received it will decode it against the registered schema from schema registry. You'd defined your schema such as:
{
  "type": "record",
  "name": "value",
  "namespace": "account",
  "doc": "",
  "fields": [
    {
      "name": "id",
      "type": "number",
      "doc": "An id."
    },
    {
      "name": "something",
      "doc": "an array of strings",
      "type": {
        "type": "array",
        "items": "string"
      }
    }
 ]
}

Upload it to schema registry and then you could convert the avro schema into types and then use that as validation. Hope that helps.

okay let me research more on registry schema, im new to kafka so trying to absorb its knowledge.
one last question, i dont need to use nestjs microservice for kafka if im using your library right?

A good article on schema registry is: https://docs.confluent.io/platform/current/schema-registry/index.html
It does have a dependency on nestjs/microservice as we do use some of the types:

https://github.com/rob3000/nestjs-kafka/blob/master/src/deserializer/kafka-response.deserializer.ts#L1
https://github.com/rob3000/nestjs-kafka/blob/master/src/serializer/kafka-request.serializer.ts#L8

If you were just looking to create a Kafka consumer/producer with node take a look at KafkaJS which is the library we use for the service. Basically this library integrates KafkaJS  and Schema registry for use with NestJS.

awesome and thank you for quick responses really appreciate your help.
I'll review the links and will come to you if any questions.

No Problems. I'll close this issue off, but feel free to reach out if you have any issues.

So I have a question, how do we handle errors?
For example, if we throw an exception to consumer side. How can we catch that error and display on api endpoint side?
So this is the flow (I think)
Http post, /users/, verify input at http api level.
Pass request to microservice.
Kafka receives the user obj as payload.
If something item is missing, we throw exception, now how that exception would go back as an error to be displayed?


[WIP] Typed racket

The goal of this pull request is to make Ob-racket work with Typed Racket for result types list, and table.
Consider the following example:
#+BEGIN_SRC racket :results list
'(1 2 3)
#+END_SRC
#+RESULTS:
- 1
- 2
- 3

Now, switch to Typed Racket:
#+BEGIN_SRC racket :results list
#lang typed/racket
'(1 2 3)
#+END_SRC
#+RESULTS:
: - /tmp/babel-trSf0K/org-babel-kRhEhy.rkt:4:0:

I figured that by changing :results list to :results list drawer I can obtain the complete error message:
#+BEGIN_SRC racket :results list drawer
#lang typed/racket
'(1 2 3)
#+END_SRC
#+RESULTS:
:results:
- /tmp/babel-trSf0K/org-babel-k01r03.rkt:4:0: Type Checker: missing type for identifier;
- consider using `require/typed' to import it
- identifier: datum->table
- from module: (file /home/scolobb/.emacs.d/elisp/emacs-ob-racket/ob-racket-runtime.rkt)
- in: (ob-racket-begin-print-table (quote (1 2 3)))
- location...:
- /tmp/babel-trSf0K/org-babel-k01r03.rkt:4:0
- context...:
- /gnu/store/qsz0284ivqymwmafqn3szrlddnvqcpg7-racket-8.12/lib/racket/pkgs/typed-racket-lib/typed-racket/typecheck/tc-toplevel.rkt:481:0: type-check
- .../private/parse-interp.rkt:643:50
- /gnu/store/qsz0284ivqymwmafqn3szrlddnvqcpg7-racket-8.12/lib/racket/pkgs/typed-racket-lib/typed-racket/tc-setup.rkt:115:12
- /gnu/store/qsz0284ivqymwmafqn3szrlddnvqcpg7-racket-8.12/lib/racket/pkgs/typed-racket-lib/typed-racket/typed-racket.rkt:22:4
:end:

The gist of the error: datum->table imported from ob-racket-runtime.rkt has no type.
After asking the question on Racket Discourse and reading ob-racket.el, I ended up with the idea of adding a Typed Racket runtime for Ob-racket. This pull request does exactly this in the file ob-racket-runtime-typed.rkt.  I currently use this file by setting the variable ob-racket-locate-runtime-library-function in Emacs using the following Elisp code:
(setq-local ob-racket-locate-runtime-library-function
      (lambda ()
	"/absolute/path/to/ob-racket-runtime-typed.rkt"))

While converting ob-racket-runtime.rkt to ob-racket-runtime-typed.rkt, I made the following reductions:

Replaced the usage of dictionaries with hash tables.  The dict generic interface is more general and covers hash tables, but I didn't find a way to translate this to Typed Racket.
Removed support for mutable lists functions.  These seem obsolete/deprecated, and I couldn't/didn't have the motivation to translate them Typed Racket.

While the code I am submitting with this pull request "works for me", it feels like a kludge: using it requires switching the entire Ob-racket runtime, it comes in a separate file for what seems to be "just another language" (i.e., Typed Racket), etc. So, I see it rather as a work in progress and I would be happy to have suggestions about how I could improve it to better integrate with the existing code and also be more transparent to the user.  Ideally, it would be nice if the typed runtime was loaded automatically whenever Typed Racket is detected, but I must confess I am not yet comfortable enough with ob-racket.el to attempt such changes on my own.

Thank you for the investigation and the PR.
How to deal with languages that are different enough that they require a
different runtime library and/or a different use of it is a question I
had neglected so far.
Probably the answer can be something similar to what is already there,
but as you suggest for convenience it should be possible to
transparently use another runtime.
I've prepared a draft change (1) to have
ob-racket-raco-make-runtime-library handle multiple libraries, (2) to
move runtime library selection into the code templates, and (3) to allow
code fragment selection to be a function of the #lang. I've pushed
that into a typed-racket feature branch. Does it look something like
what you had in mind?
Switching to a different (typed) runtime for Typed Racket sounds right,
but it's true that the current "ob-racket-runtime-typed.rkt" module adds
duplication to the codebase. If the "ob-racket-runtime.rkt" internals
were to be exposed, perhaps from a "private" module, would that make it
possible to implement "ob-racket-runtime-typed.rkt" mostly in terms of
the untyped code?
Or maybe that's not even much of an issue in this case, since the basic
data types of languages tend not to change that often, and probably
these conversion routines don't often need touching either. So if you
prefer we can also go with the current "ob-racket-runtime-typed.rkt", at
least for the time being.

Thank you for your feedback @hasu ! I am currently on a research visit, so kind of short on time, but I'll take a deeper look at your suggestion as soon as I have a spare brain moment.

Hello again @hasu . I read your commit and yes, it is exactly what I wanted, thank a lot!  I particularly like the fact that you can now easily switch and fine-tune Racket runtimes directly within code block parameters.

If the "ob-racket-runtime.rkt" internals were to be exposed, perhaps from a "private" module, would that make it possible to implement "ob-racket-runtime-typed.rkt" mostly in terms of the untyped code?

If such a private module existed, then ob-racket-runtime-typed.rkt could be a simple typed module containing a bunch of require/typed/provide statements, assigning type signatures to the identifiers and re-exporting them. This could avoid a lot of code duplication.
As you saw in my commits, a few of the things currently defined in ob-racket-runtime.rkt are not supported by Typed Racket (e.g., mutable lists), but I believe that is straightforward to solve by provide appropriately (lightly) restrictive type signatures.
Now that I have finished writing this, I realize that no private module is needed in fact: ob-racket-runtime-typed.rkt could just import ob-racket-runtime.rkt directly, assigning the type signatures and re-exporting the identifiers!

Or maybe that's not even much of an issue in this case, since the basic data types of languages tend not to change that often, and probably these conversion routines don't often need touching either. So if you prefer we can also go with the current "ob-racket-runtime-typed.rkt", at least for the time being.

I am not really sure, frankly.  I suppose it's not such a big deal having ob-racket-runtime-typed.rkt duplicating most of the code from ob-racket-runtime.rkt, since as you say it seems to be quite an edge case, which becomes easier to solve now with the new functionality you added.  On the other hand, rewriting ob-racket-runtime-typed.rkt to just re-export identifiers with types seems really easy.
I guess I'd suggest you merge the typed-racket branch, and then I just submit another PR changing ob-racket-runtime-typed.rkt to require/typed/provide identifiers from ob-racket-runtime.rkt.
What do you think?
Also, I start having wondering about the performance penalty of using require/typed and require/typed/provide. I guess I could just write up the PR and ask on Racket Discourse.

Thanks for reviewing my change.
I've merged the initial implementation, and so in that respect this PR
is ready to be closed.
I've also pushed another draft change to the typed-racket branch to
split a "private" module out of "ob-racket-runtime.rkt", one that
actually exports all the implementation functions, for reuse in runtime
libraries with different conversion behavior or a different (e.g.,
typed) interface.
I assume that with those exports available it is then possible to
require/typed much of the currently duplicated code, even if that
means assigning more restrictive type signatures in some cases, as you say.
Perhaps it's worth doing if it's not much work and doesn't involve a
noticeable performance penalty, but I'll leave it to you to decide
whether to submit that PR.

Thanks @hasu ! I will look into submitting the other change on top of your new commit over the next couple of days.


Add exception handling for clashing validator and field names in crea…

Change Summary
When creating a model using create_model, if a field name matches a validator and the field has a default value, the field takes precedence in the namespace. However, in the case of BaseModel, the validator takes precedence when defined later, which is expected behavior.
For create_model, since the precedence is not obvious to the user, Pydantic should raise an exception to avoid confusion.
Related issue number
fix #10646
Checklist

[x] The pull request title is a good summary of the changes - it will be used in the changelog
[x] Unit tests for the changes exist
[x] Tests pass on CI
[x] Documentation reflects the changes where applicable
[x] My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

Selected Reviewer: @sydney-runkle

please review

Raise an exception is not infeasible, but a little bit counter-intuitive. In the original case, it was hard to realise that the key of __validators__ could not have the same name as fields.

from pydantic import create_model, field_validator

def bar(cls, v):
    print("bar_called", v)
    return v

validator = field_validator("bar", mode="before")(bar)

# OPTION1: validator is not called
validators = {"bar": validator}

# OPTION2: validator is called
# validators = {"bar_validator": validator}

Foo = create_model("Foo", bar=(str, ...), __validators__=validators)
foo = Foo(bar="bar")

@sydney-runkle points out that the following example works, notice that the name of the validator function and the name of the field can be the same.

from pydantic import BaseModel, field_validator

class Model(BaseModel):
    a: int

    @field_validator('a')
    def a(cls, v) -> int:
        return v + 1

m = Model(a=1)
print(repr(m))
#> Model(a=2)

I commented under the original issue that perhaps we could rename the validator function to address this.

I was thinking that another possible solution would be to add a prefix to all __validators__, like a -> _validator_func_a.
    if __validators__:
        for validator_name, validator in __validators__.items():
            namespace[f"_validator_func_{validator_name}"] = validator

What happens when __base__ is specified, and the base(s) has a field name clashing with one of the validator names?

What happens when __base__ is specified, and the base(s) has a field name clashing with one of the validator names?

In this scenario the validator function is being used as default value of the field. Which is a separate bug. Here's the snippet which highlights this:
from pydantic import BaseModel, create_model, field_validator

class FooModel(BaseModel):
    foo: str
    bar: str

def bar(s: str) -> str:
    return "foo" + s

validator = field_validator("apple", mode="before")(bar)
validators = {"bar": validator}

BarModel = create_model(
    'BarModel',
    apple=(str, 'russet'),
    banana=(str, 'yellow'),
    __base__=FooModel,
    __validators__=validators
)

print(BarModel(foo="a"))
# foo='a' bar=<function bar at 0x104b4d080> apple='russet' banana='yellow'

Hey folks - sorry for the delay in reviews here. We were pushing to get v2.10 out. Looking forward to catching up on reviews here soon :).

We discussed about this with @sydney-runkle and while having this would be somewhat beneficial, it still feels incomplete as this won't error when such fields are defined in the provided __bases__. We decided to just add a note in the documentation, as this is a pretty uncommon mistake (and is caught by the type checker with normal class definitions).

Going to close this, given the above. Thanks folks!


not getting emails

Hi, the zip that I download does not have the php mailer autoload, anyway I fix that, so far I can create users, but i am not getting the emails in order to verify the accoint and log in, help please, what I may doing wrong?

I have the same problem, Im configuring a admin email using a gmail account pls help

I fix it, add me on facebook<EMAIL_ADDRESS>so I can help you directly! My email server is up and running without any problem now!

Thanks perhaps you can put it up here so others can read it is that okay?

did you edit the config.php file correctly? if yes what are the configuration of your config.php file? please share

Give me a few minutes to see how to share those files, the php mailer is incomplete in this zip folder , and on Gmail you can receive but can't send to Gmail, hotmail or Yahoo! Because you need
1 have an business IP address
2 you have to encrypt your server in order to send to those mails accounts

I'll connect in my pc in a while and upload those file and the while solution to  this!

thanks man, I really appreciate it. Looking forward for your response and your advice

Sorry my bad, I thought this was a thread for round cube, so what's your problem again!
Not getting emails?

first what kind of email server are You using to send the mail responses?

let me know or add me on facebook or messenger for a fast solution!

ok I remember now, i have to open my files and check my server to remember, the first error I did have was that the php mailer was empty in the /login/scripts/phpmailer , let me know if you have that already or if you need that file first, then we do the second step!

I'll wait here if need me

add me on messenger
Tobias Sopu

or email me is better
<EMAIL_ADDRESS>

I add you on messenger, waiting for your response

Again : when new user register, no email is sent for verification before they could log in. according to the SQL if verified column is still 0, user cannot log in. I think when user verify, it changes to 1 before they could login it. but the email is not sent inorder to verify

send me the link to your pagetest!

https://sitio1.ecsignsla.com/login/signup.php
this is mine and is just the main page you can check and we star from there!


Clicking on pictures in Reddit results in redirect error in Firefox

New Issue Checklist (tick off like this: [x])

[ X] I checked existing issues (open and closed) for possible duplicates
[X ] I can reproduce the problem on the latest stable version (not nightly!)
[ ] If you have a problem with a specific website: adding the domain to your no-skip-urls-list does not solve the problem
[ ] The issue is not about adding entries to the default no-skip-urls-list

What is your browser?

[ X] Firefox
[ ] Chrome

What is your operating system?

[ ] Linux
[ ] Mac
[ X] Windows

Description (please include examples/screenshots where applicable)
When clicking on a picture in a reddit post on www.reddit.com in Firefox the new tab with the enlarged picture gets the following error:
The page isn’t redirecting properly
An error occurred during a connection to preview.redd.it.
This problem can sometimes be caused by disabling or refusing to accept cookies.
This happens with any picture in a post, can recreate.  Turning off the extension fixes it.  I'm not sure how to add a url to the exception list or if that's possible.

Just add reddit.com to the no-skip-urls list.

Awesome TY that worked!


using docker exec with existing container instead of spawning new contai...

Hi
I believe that health check script shall be run within "container to be checked" not from clone-container  attached to network stack of the "container to check". The health check script shall simply have access to a process tree, file system and rest of resources of "container to be checked" but by running it from a brand new container with network attached, no such an access except for networking is provided. For that case i would simply go for check-http script.

BTW
I modified check-cmd command so it is backward compatible with gliderlabs/registrator (port passed to  check-cmd invocation is simply ignored). An alternative option would be to pass that port as health check script parameter or interpolate script invocation with SERVICE_PORT

This is a reasonable proposal as this was done before docker exec existed. However, the whole health checking system of this container is probably wrong. So until we figure it out, this PR may stall unless there are others than can verify this works and is needed.

Hi
I see. Can you elaborate a little why you think "the whole health checking system of this container is probably wrong" ?

For one, it was designed before exec, so it should have been designed
closer to this patch. Second, it's a complicated area that should be more
decoupled from the concern of just running consul. Even from a
documentation standpoint it's tricky in the context of Docker. It
introduces the docker binary for some cases, and this is yet another
dependency that some don't care to have included.
Basically the way it's designed it's creating more confusion than
convenience, so another approach should be considered.
On Tue, Mar 31, 2015 at 3:34 AM, jmilkiewicz<EMAIL_ADDRESS>wrote:

Hi
I see. Can you elaborate a little why you think "the whole health checking
system of this container is probably wrong" ?
—
Reply to this email directly or view it on GitHub
https://github.com/progrium/docker-consul/pull/66#issuecomment-87994919.

--
Jeff Lindsay
http://progrium.com

I do agree with you and still believe that exec is much better than executing command against new container. The health-check is indeed not trivial especially in a fact that services in consul are registered on behalf of consul agent (client or server), and a particular agent is responsible for running health checks against services it registered. So in case of a "Script check" the biggest value would be to run "Script check" locally to the service and docker exec seems to be the best idea for that...
Checking a service from outside (remotely) is much easier (using curl) as it does not rely on check to be local to service .
Maybe a slightly better idea would be to simply have 2 docker images: one for "pure" consul which is perfect for consul servers (no dep to docker at all) and the second image (with deps to docker) for consul agents(clients) with some check scripts.

Right that is closer to what is planned.
On Tue, Mar 31, 2015 at 8:38 AM, jmilkiewicz<EMAIL_ADDRESS>wrote:

I do agree with you and still believe that exec is much better than
executing command against new container. The health-check is indeed not
trivial especially in a fact that services in consul are registered on
behalf of consul agent (client or server), and a particular agent is
responsible for running health checks against services it registered. So in
case of a "Script check" the biggest value would be to run "Script check"
locally to the service and docker exec seems to be the best idea for that...
Checking a service from outside (remotely) is much easier (using curl) as
it does not rely on check to be local to service .
Maybe a slightly better idea would be to simply have 2 docker images: one
for "pure" consul which is perfect for consul servers (no dep to docker at
all) and the second image (with deps to docker) for consul agents(clients)
with some check scripts.
—
Reply to this email directly or view it on GitHub
https://github.com/progrium/docker-consul/pull/66#issuecomment-88088368.

--
Jeff Lindsay
http://progrium.com

Perfect. I am closing PR. Thx for conversation. I managed to learn a lot in area of docker and go lang analyzing your code.


Visualizations no longer open

Discord username
No response
What type of issue is this?
Permanent – Occurring repeatably
Is this issue blocking you from using Enso?

[X] Yes, I can't use Enso because of this issue.

Is this a regression?

[X] Yes, previous version of Enso did not have this issue.

What issue are you facing?
Opening visualizations fails with the following error:

Expected behaviour
Visualizations should work.
How we can reproduce it?

Create a node.
Click the show visualization icon.

Screenshots or screencasts
https://github.com/enso-org/enso/assets/1428930/52e78dbe-7b5d-4a5d-8e16-0092a106b70d
Logs
No response
Enso Version
develop 56688ec1e7af144e2533d74f4b23f9208d858b59
Browser or standalone distribution
Standalone distribution (local project)
Browser Version or standalone distribution
standalone
Operating System
Linux
Operating System Version
No response
Hardware you are using
No response

First failing commit is 4e5cb9cca63273149b87fec2490725ed148a6ea4
I'm starting the IDE with ./run ide watch --backend-source release --backend-release latest so I think it could be an incompatibility issue between nightly build and develop.

Seems to work fine when building the engine locally. So, I guess this is caused by a nightly build that is incompatible with develop. Hopefully, will be fine tomorrow.


Vandana/shin19.final.2

allowed subnetwork to be generated with a gene list in a file

Amazing! Maybe we can move the action button on ui.R line 254 to inside the mainPanel so it appears on the left

and also label plots in the ui

Nice! All good to merge


Charts | Sunburst: Add different click types, highlighting, selection, remove animations

[x] Implement highlighting (in order to sync with other viewers)
[x] Implement ctrl + click for selecting specific parts of the plot
[x] Implement shift + click for adding selection on the plot
[x] Implement ctrl + shift + click for removing selection
[ ] Turn off animations or make them shorter (especially, remove animation in ctrl + click)
[x] Remove delays from animations
[ ] Fix selection - if selecting from the grid or viewer - select only a segment or part of the chart

Animation and selection improvements are related to the changes in the ECharts library - moved them to a separate ticket:
https://github.com/datagrok-ai/public/issues/2262


Grouping bug?

Components are rearranged in a strange way after hitting apply. Suspected is screen resolution changes (people are opening on different screens)

I have tested this problem and I can't simulate it. I tested various resolutions and devices. Do you know how to simulate it?


New PPA for latest UIbuntu

Added guidelines about how to install the scripts included in drive-google on latest Ubuntu - Also reorganized the file

I've added a couple of comments, PTAL. Thanks for working on this.

@jean-christophe-manciot can you describe the difference between your .deb offering vs existing one from PPA by twodopeshaggy?

@idvoretskyi Everything is described on the home page.

@jean-christophe-manciot yes, I'm aware of. As an end-user, I'd like to see this information in a single place - this repo.

Yeah, @idvoretskyi has a point there, it helps to list out a summary so that folks can find
the information easily and pick which PPA to use.
@jean-christophe-manciot, thanks for the patience, if you could address @idvoretskyi's request for clarity in the differences as well as remove the addition of [Ubuntu Linux], we'll be ready to merge it in.
At the end please squash your commits into one, e.g if we have made 3 commits that we want to squash into one:
$ git rebase -i head~3
$ git commit -a --amend
platform-packages: add sync scripts Ubuntu PPA

and then we'll be gucci to go.
Thank you.

I'm not following @idvoretskyi 's request: the detailed explanations described on the home page of my repository also appear within README-Automation.md, corresponding to this PR.
what addition of Ubuntu Linux are you talking about? If you take a look at my proposed platform_packages.md vs the original one, you'll see that:

neither Ubuntu Linux nor Debian Linux have been added: the differences which appear above your first comment are misleading.
the only real additions relate to my PPA. The rest is just original text which has been reorganized alphabetically.
my scripts are only available on Ubuntu. It would be misleading to detach that information from Automation

am I missing something?

My apologies @jean-christophe-manciot. I hadn't caught on your heading.
It seemed before that the PPAs' titles alone were competing but actually they are different
@shaggytwodope's PPA's title is
### Ubuntu, or Ubuntu based distros.

yours is
### Automation on the latest stable Ubuntu distribution.

LGTM, let's squash the commits into one as I had requested and merge it in!

@idvoretskyi :  I've added a few lines.to clarify the differences with twodopeshaggy's Ubuntu PPA.

@jean-christophe-manciot, I see 3 new separate commits. Please let me know when you are
finished making additions to this PR so that I can squash and merge it.
Thanks.

Done: squashed & pushed.

Awesome! Thank you for working on this and for sharing your working, plus for the patience.
LGTM!


Schedule TE in min sku

Context
Currently, the TE allocation is greedy and uses the first TE with a machine size big enough for the request. Switching the allocation logic to use the min size available for the request instead.
Checklist

[x] ./gradlew build compiles code correctly
[x] Added new tests where applicable
[x] ./gradlew test passes all tests
[x] Extended README or added javadocs where applicable

@sundargates I will merge for rc for now. Feel free to comment and I will follow-up.


System unavailable: https://ci.adoptopenjdk.net/label/build&&linux&&arm/ all offline : <10Gb disk space

https://ci.adoptopenjdk.net/label/build&&linux&&arm/
These machines have too little free disk space, i've had a look and cannot see anything obvious to delete

Stop
On Wed, Nov 18, 2020, 1:07 AM Andrew Leonard<EMAIL_ADDRESS>wrote:

https://ci.adoptopenjdk.net/label/build&&linux&&arm/
These machines have too little free disk space, i've had a look and cannot
see anything obvious to delete
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/AdoptOpenJDK/openjdk-infrastructure/issues/1687, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AQ3LBBD7AAGRUS5HTUJG6RTSQOFEBANCNFSM4TZV4FEQ
.

Removed build-scripts-testing directories from the workspace and re-enabled


Fixed console specs link

Old link is deprecated: ~~https://github.com/DeveloperToolsWG/console-object/blob/master/api.md~~
New link is now: ~~https://github.com/DeveloperToolsWG/console-object~~ ➡ ~~https://github.com/whatwg/console~~ ➡ https://console.spec.whatwg.org

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

Ping 🏓


"npm install" additional libs

Hi, how can I "npm install" additional libs (like rxjs, lodash etc) and use them in the project? Thanks, Marco

try following these steps


Convert text into locale keys

Converts user facing text throughout the application into locales. The pattern in the app was to have a locale file, per controller, which I've continued in this work. As a result, there have been a number of extra locale files added.
Trello:
https://trello.com/c/ugOLyTju/2532-add-hardcoded-text-to-collections-locale-files
⚠ This repo is Continuously Deployed: make sure you follow the guidance ⚠

Thanks for the reviews @brucebolt and @thomasleese! I think all the comments have been addressed.


libraries for support mcuboot serial FWU

This patch introduce libraries which are need for support Mcuboot serial recovery mode.
These libraries are in usage by newtmgr protocol encoding and parsing. Mcuboot serial recovery protocol simply implements image related piece of newtmgr protocol.
Libraries:

tinycbor:  cbor library
cborattr: attribute based decoder cbor
base64: base64 library

These libraries will be useful for future OTA DFU works as well.
As the serial recovery functionality consumes additional flash, the bootloader partition was extended as well for nRF52840 SoC.
Fixed #3081.
Signed-off-by: Andrzej Puzdrowski<EMAIL_ADDRESS>

@carlescufi, @utzig

@nvlsianpu "ext: lib: Add cboorattr library" s/cboorattr/cborattr

did mynewt have patches on top of upstream
Yes it has. The status is that origin dosen't fit to the cborattr and newtmgr anymore.

@thiagomacieira your thoughts?

Comparing to TinyCBOR v0.4
+struct cbor_encoder_writer;
+
+typedef int (cbor_encoder_write)(struct cbor_encoder_writer *, const char *data, int len);
+
+typedef struct cbor_encoder_writer {
+    cbor_encoder_write *write;
+    int                 bytes_written;
+} cbor_encoder_writer;
+
+
 /* Encoder API */
 struct CborEncoder
 {
-    union {
-        uint8_t *ptr;
-        ptrdiff_t bytes_needed;
-    } data;
-    const uint8_t *end;
+    cbor_encoder_writer *writer;
+    void *writer_arg;
     size_t added;
     int flags;
 };
@@ -172,7 +179,8 @@ typedef struct CborEncoder CborEncoder;

 static const size_t CborIndefiniteLength = SIZE_MAX;

-CBOR_API void cbor_encoder_init(CborEncoder *encoder, uint8_t *buffer, size_t size, int flags);
+
+CBOR_API void cbor_encoder_init(CborEncoder *encoder, cbor_encoder_writer *pwriter, int flags);

This is a wholly patched and unsupported version. This is not upstream.
TinyCBOR team has been trying to design a writer that would be able to work with Zephyr's net_buf but has not come to an API yet. When we do, it will be different from the above.
My recommendation is to reject this import and instead work with TinyCBOR upstream to design this feature sooner rather than later (it's not in the v0.5 roadmap).

@thiagomacieira @nashif @nvlsianpu I understand. Can we take a middle-ground way forward here? i.e. accept this temporarily and work upstream in parallel. The problem is that it's not only the serial recovery mode that will need this, but also the DFU work that will start next week, and unless we can really add this upstream in that timeframe we will be blocked by the lack of CBOR support in Zephyr.

Not sure that's a good idea. There's other software using TinyCBOR and Zephyr at the same time. Introducing this patched version will cause symbol collision and subtle errors.

We can move this tinycbor to mynewt_tinycybor as temporary resolution and us it only for a newtmgr like dfu. Then in near future we should move to original tinycbor.

You need to rename all non-static functions.

I mean to move it to separate code piece  in sense of Kconfig + Make file. So if it will be kept as not enable i will be not included in the build by any means.  I'm not sure if using both version simultaneously make sense. Is it a case?
As @carlescufi wrote: we want this as temporary (but not shadow) solution for much bigger  and important for use and Zephyr DFU development.

My point is that if you import a patched TinyCBOR, you may break applications that use TinyCBOR because the symbols will clash with the application-provided copy. The only way out for that is to rename all non-static symbols, until we manage to upstream the feature and then deduplicate.

Another option might be to break tinycbor out of this PR, add it to the DFU "branch" and/or to mcuboot (for serial recovery) for the time being, and start working ASAP on designing and upstreaming the writer interfaces. Would that work?

@utzig I would accept that. It should touch both tinycbor and cborattr. @carlescufi you thoughts?

I close this as replayed by https://github.com/zephyrproject-rtos/zephyr/pull/4237


Add "Cite as" button or pane

Following the lengthy discussion with @satra in slack, we ASAP need a prominently visible to a visitor guidance on how to cite any particulat dandiset.  I think it could be quickly achieved (even before publish functionality lands) by adding a  "Cite as" button next to "Get shareable link " which would open a similar pane with information such as
"{contributors} {title}, {last-modified year}, https://dandiarchive.org/dandiset/{identifier}/{version}"
Later, whenever DOI-grade metadata records are established and DOIs minted, we should be able to produce citations in a selected number of styles and export (may be just redirect queries with proper headers to doi.org) in various styles for released dandisets.

For all means and purposes #684 (thanks @sanuann @satra et al) addressed this issue


FE: Hotswap models in In-Game Preview

Currently it looks like the rendering context is completely reset when a new card is selected. It would be much faster to retain the rendering context and environment, and hotswap the model.

This is true, and probably a good idea.
However, the problem is that old NFT state can linger unless we do a reset, so resetting the context here is the safe option.
I'd like to explore ways to speed up engine load, which would solve a lot of this concern, and which I'm convinced can be massively improved (possibly with caching, building to tree shake, or getting rid of dependencies, none of which have been tried yet).

Ok, we can explore that avenue first, that's low hanging fruit


blog: blog updates

Split multiples in one post to singles. (Need to do that with 'Here Comes Da Judge')
Back dated filenames and dates to match day of news article, or day after.

Error: YAML Exception reading /home/runner/work/blog/blog/_posts/2024-10-08-ShitHereWeGoAgain.md: (): did not find expected key while parsing a block mapping at line 2 column 1
Error: YAML Exception reading /home/runner/work/blog/blog/_posts/2024-10-10-SharpiegateTrumpAddedDickheadConeUncertainyDorian.md: (): could not find expected ':' while scanning a simple key at line 7 column 1


Ubuntu 20.04 support?

Please see link to github gist : https://gist.github.com/xandrellas/a30fcfc5bd2d307260dd752e1385668e
This is on a fresh vagrant ubuntu 20.04 host, running puppet agent 6.25.1, puppetserver 6.17.1, all packages updated/upgraded, kernel version 5.4.0-91-generic.
Host is idempotent after 2 puppet runs, but this is obviously problematic.

Are there any plans to officially support Ubuntu 20.04 soon? 22.04 LTS is there for quite a while too

Hi @xandrellas, @Hans-Maulwurf
I don't have a solution for you for this, but we're building a new one. You can find the details here: https://github.com/newrelic/puppet-install
Would love to hear your thoughts.
Thanks


Update README.md

Corrected grammar

LGTM

@ibuildthecloud

Clearing out email reminded me about this PR.
Wasn't very easy to see the change so I've updated the description.


Signal Desktop has error connecting to Phone

I find that I'm running into this issue https://github.com/signalapp/Signal-Desktop/issues/1075 from time to time. It may happen when behind a VPN. I'm confirming now.

I still have access when behind a VPN. There must be a separate source of the problem, perhaps related to the WebSocket issue mentioned in the ticket.

I haven't encountered this in awhile, so here's the close on this ticket.


feat(raw_vehicle_cmd_converter): add vehicle adaptor

Description
add empty vehicle adaptor which compensates control commands by taking into account vehicle-specific dynamic characteristics.
this feature is set false by default
we will add an algorithm of vehicle adaptor
Related links
Parent Issue:

Link

How was this PR tested?
check if ACTUATION_CMD sim works with fase and true.
false

true

Notes for reviewers
None.
Interface changes
None.

Effects on system behavior
None.

@maxime-clem
could you approve as a code owner?

I'm now checking how it was possible to merge this in the first place.

This bypass list only has @mitsudome-r in it and no one else should be able to merge without passing the status checks.
Maybe something is wrong with the required checks maybe?
Right now it is like this:

@kosuke55 do you remember if you had to press this button before merging this PR?

@xmfcx
hmm, thanks for checking. I don't remember doing a bypass merge, ignoring the required ...

I am not sure the reason why I could mere but sent PR to fix too long line
https://github.com/autowarefoundation/autoware.universe/pull/9716


Error getting accountId - Invalid base64 - atob is not defined - RequiredHeaderMissing

After updating to the last version, v2.7.3, because I had errors after some LibreLikUp changes, It's still failing. Now it looks like it's failing trying to use atob.
Dec 16 16:16:00 diabetes-vm start2.sh[26510]: [error]: Error getting accountId:  Invalid token specified: invalid base64 for part #2 (atob is not defined)
Dec 16 16:16:01 diabetes-vm start2.sh[26510]: [error]: {"message":"RequiredHeaderMissing"}
Dec 16 16:16:01 diabetes-vm start2.sh[26510]: [error]: getting libreLinkUpConnection:  Cannot read property 'data' of undefined

How can I fix it?
Thanks.

I've fixed it, with a workaround, using postman to log in and get the id, then I calculate the sha256 hex of the id and I modified the code to use it hardcoded, then it works. It's a little bit weird, in the original code, it fails to get the id from the jwt token (decoding) so the accountId header is null and the I get the error "RequiredHeaderMissing". I think we can use the id from the login response instead of decoding the jwt token... I will try to refactor the code to make it work in my scenario. I try to investigate why is failing decoding the JWT token too.
Thanks.

So the current implementation failes at docoding the jwt? That is strange. Why does it stop working from one day to another? Here in the DE region, it still works for me with 2.7.3.
I am on vacation right now but will certainly look into this as soon as I get back home (December 29).
Thank you so much for investigating this issue!

Hi !! Thanks for your reply. It started to fail when they deprecated the old versions, below 4.12.0 I think. Then I updated the repository because I saw new releases of this uploader but It fails anyways. Then I cloned the repository again, a fresh install, I created the script to run it and I still had errors related to "RequiredHeaderMissing" for the account-id header. The error that I saw before the missing header error was:
Error getting accountId:  Invalid token specified: invalid base64 for part #2 (atob is not defined)

So maybe there is a problem in my google cloud instance, maybe some package to update, I don't know, but It worked fine during the year. I've to take a closer look to see what happening, maybe it's something related with node... The code looks very fine to me and it worked before.
Let's see. If I have any other update I will post it ASAP.
Thanks very much, your project help me a lot to have my glucose metrics in my watch and have the nightscout ready.


'rye build' with maturin produces the wheel using the bootstrap Python interpreter

Steps to Reproduce

rye init --build-system maturin -p 3.8 rusty; cd rusty
rye pin --relaxed 3.8
rye sync
rye build

Expected Result
The binary wheel should be for Python 3.8.
Actual Result
The binary wheel is for Python 3.12 (rusty-0.1.0-cp312-cp312-linux_x86_64.whl).
Version Info
rye 0.34.0
commit: 0.34.0 (d31340178 2024-05-20)
platform: linux (x86_64)
self-python<EMAIL_ADDRESS>symlink support: true
uv enabled: true

Stacktrace
No response

same on macos(arm)
log
❯ rye init --build-system maturin -p 3.8 rusty; cd rusty
success: Initialized project in /Users/***/git/python/test/qwe/rusty
  Run `rye sync` to get started
❯ rye pin --relaxed 3.8

pinned 3.8 in /Users/***/git/python/test/qwe/rusty/.python-version
❯ rye sync

Initializing new virtualenv in /Users/***/git/python/test/qwe/rusty/.venv
Python version<EMAIL_ADDRESS>Generating production lockfile: /Users/***/git/python/test/qwe/rusty/requirements.lock
Generating dev lockfile: /Users/***/git/python/test/qwe/rusty/requirements-dev.lock
Installing dependencies
   Built file:///Users/***/git/python/test/qwe/rusty                                                        Built 1 editable in 3.97s
Installed 1 package in 1ms
 + rusty==0.1.0 (from file:///Users/***/git/python/test/qwe/rusty)
Done!
❯ rye build

building rusty
* Creating isolated environment: venv+uv...
* Using external uv from /Users/***/.rye/uv/0.1.44/uv
* Installing packages in isolated environment:
  - maturin>=1.2,<2.0
* Getting build dependencies for sdist...
* Building sdist...
Running `maturin pep517 write-sdist --sdist-directory /Users/***/git/python/test/qwe/rusty/dist`
🍹 Building a mixed python/rust project
🔗 Found pyo3 bindings
🐍 Found CPython 3.12 at /private/var/folders/27/xcyb5y7j5ql7sklfygs11m940000gn/T/build-env-3u6gfgo3/bin/python3
📡 Using build options features from pyproject.toml
📦 Built source distribution to /Users/***/git/python/test/qwe/rusty/dist/rusty-0.1.0.tar.gz
rusty-0.1.0.tar.gz
* Building wheel from sdist
* Creating isolated environment: venv+uv...
* Using external uv from /Users/***/.rye/uv/0.1.44/uv
* Installing packages in isolated environment:
  - maturin>=1.2,<2.0
* Getting build dependencies for wheel...
* Building wheel...
Running `maturin pep517 build-wheel -i<EMAIL_ADDRESS>--compatibility off`
🍹 Building a mixed python/rust project
🔗 Found pyo3 bindings
🐍 Found CPython 3.12 at<EMAIL_ADDRESS>📡 Using build options features from pyproject.toml
💻 Using `MACOSX_DEPLOYMENT_TARGET=11.0` for aarch64-apple-darwin by default
   Compiling target-lexicon v0.12.14
   Compiling autocfg v1.3.0
   Compiling proc-macro2 v1.0.85
   Compiling once_cell v1.19.0
   Compiling unicode-ident v1.0.12
   Compiling libc v0.2.155
   Compiling syn v1.0.109
   Compiling parking_lot_core v0.9.10
   Compiling cfg-if v1.0.0
   Compiling scopeguard v1.2.0
   Compiling smallvec v1.13.2             ] 0/43: proc-macro2(build.rs), scopeguard, parking_lot_core(buil...
   Compiling unindent v0.1.11             ] 1/43: proc-macro2(build.rs), scopeguard, parking_lot_core(buil...
   Compiling indoc v1.0.9                 ] 2/43: proc-macro2(build.rs), parking_lot_core(build.rs), syn(b...
   Compiling lock_api v0.4.12             ] 7/43: indoc, proc-macro2(build), parking_lot_core(build), syn(...
   Compiling memoffset v0.9.1             ] 8/43: indoc, proc-macro2(build), parking_lot_core(build), syn(...
   Compiling quote v1.0.36               ] 17/43: syn(build), memoffset(build), libc(build), target-lexico...
   Compiling pyo3-build-config v0.19.2   ] 24/43: memoffset(build), target-lexicon, syn, lock_api(build)
   Compiling pyo3-macros-backend v0.19.2 ] 28/43: pyo3-build-config(build), syn, lock_api(build)
   Compiling parking_lot v0.12.3         ] 29/43: pyo3-build-config(build), lock_api, syn, pyo3-macros-bac...
   Compiling pyo3-ffi v0.19.2====>       ] 33/43: pyo3-build-config, pyo3-macros-backend
   Compiling pyo3 v0.19.2
   Compiling pyo3-macros v0.19.2===>     ] 36/43: pyo3-ffi(build), pyo3-macros-backend
   Compiling rusty v0.1.0 (/private/var/folders/27/xcyb5y7j5ql7sklfygs11m940000gn/T/build-via-sdist-varl957f/rusty-0.1.0)
    Finished `release` profile [optimized] target(s) in 6.16s
📦 Built wheel for CPython 3.12 to /private/var/folders/27/xcyb5y7j5ql7sklfygs11m940000gn/T/build-via-sdist-varl957f/rusty-0.1.0/target/wheels/rusty-0.1.0-cp312-cp312-macosx_11_0_arm64.whl
/private/var/folders/27/xcyb5y7j5ql7sklfygs11m940000gn/T/build-via-sdist-varl957f/rusty-0.1.0/target/wheels/rusty-0.1.0-cp312-cp312-macosx_11_0_arm64.whl
Successfully built rusty-0.1.0.tar.gz and rusty-0.1.0-cp312-cp312-macosx_11_0_arm64.whl

version
❯ rye --version
rye 0.34.0
commit: 0.34.0 (d31340178 2024-05-20)
platform: macos (aarch64)
self-python<EMAIL_ADDRESS>symlink support: true
uv enabled: true

Same issue here with the hatch-mypyc build hook. Trying to build for 3.11, but getting a 3.12 wheel out.

I believe I have a fix here: https://github.com/astral-sh/rye/pull/1250

Success:
❯ ../rye/target/debug/rye build
Python version<EMAIL_ADDRESS>building rusty
* Creating isolated environment: venv+uv...
* Using external uv from /Users/crmarsh/.rye/uv/0.2.24/uv
* Installing packages in isolated environment:
  - maturin>=1.2,<2.0
* Getting build dependencies for sdist...
* Building sdist...
Running `maturin pep517 write-sdist --sdist-directory /Users/crmarsh/workspace/rusty/dist`
    Updating crates.io index
  Downloaded redox_syscall v0.5.3
  Downloaded 1 crate (23.8 KB) in 0.16s
🍹 Building a mixed python/rust project
🔗 Found pyo3 bindings
🐍 Found CPython 3.8 at /private/var/folders/nt/6gf2v7_s3k13zq_t3944rwz40000gn/T/build-env-r1j7m8yr/bin/python3
📡 Using build options features from pyproject.toml
📦 Built source distribution to /Users/crmarsh/workspace/rusty/dist/rusty-0.1.0.tar.gz
rusty-0.1.0.tar.gz
* Building wheel from sdist
* Creating isolated environment: venv+uv...
* Using external uv from /Users/crmarsh/.rye/uv/0.2.24/uv
* Installing packages in isolated environment:
  - maturin>=1.2,<2.0
* Getting build dependencies for wheel...
* Building wheel...
Running `maturin pep517 build-wheel -i /private/var/folders/nt/6gf2v7_s3k13zq_t3944rwz40000gn/T/build-env-cy75lkxx/bin/python --compatibility off`
🍹 Building a mixed python/rust project
🔗 Found pyo3 bindings
🐍 Found CPython 3.8 at /private/var/folders/nt/6gf2v7_s3k13zq_t3944rwz40000gn/T/build-env-cy75lkxx/bin/python
📡 Using build options features from pyproject.toml
💻 Using `MACOSX_DEPLOYMENT_TARGET=11.0` for aarch64-apple-darwin by default
   Compiling target-lexicon v0.12.15
   Compiling autocfg v1.3.0
   Compiling once_cell v1.19.0
   Compiling proc-macro2 v1.0.86
   Compiling unicode-ident v1.0.12
   Compiling libc v0.2.155
   Compiling syn v1.0.109
   Compiling parking_lot_core v0.9.10
   Compiling cfg-if v1.0.0
   Compiling smallvec v1.13.2
   Compiling scopeguard v1.2.0
   Compiling indoc v1.0.9
   Compiling unindent v0.1.11
   Compiling lock_api v0.4.12             ] 7/43: parking_lot_core(build), target-lexicon(build.rs), unindent, indoc,...
   Compiling memoffset v0.9.1
   Compiling quote v1.0.36               ] 19/43: target-lexicon(build), proc-macro2, memoffset(build), lock_api(buil...
   Compiling pyo3-build-config v0.19.2   ] 23/43: parking_lot_core, syn, target-lexicon, memoffset(build), lock_api(b...
   Compiling parking_lot v0.12.3         ] 26/43: lock_api, syn, pyo3-build-config(build.rs), memoffset(build)
   Compiling pyo3-ffi v0.19.2====>       ] 32/43: syn, pyo3-build-config
   Compiling pyo3 v0.19.2
   Compiling pyo3-macros-backend v0.19.2 ] 36/43: pyo3-ffi, syn, pyo3(build)
   Compiling pyo3-macros v0.19.2=====>   ] 39/43: pyo3-macros-backend
   Compiling rusty v0.1.0 (/private/var/folders/nt/6gf2v7_s3k13zq_t3944rwz40000gn/T/build-via-sdist-l3xd2jfr/rusty-0.1.0)
    Finished release [optimized] target(s) in 4.24susty
📦 Built wheel for CPython 3.8 to /private/var/folders/nt/6gf2v7_s3k13zq_t3944rwz40000gn/T/build-via-sdist-l3xd2jfr/rusty-0.1.0/target/wheels/rusty-0.1.0-cp38-cp38-macosx_11_0_arm64.whl
/private/var/folders/nt/6gf2v7_s3k13zq_t3944rwz40000gn/T/build-via-sdist-l3xd2jfr/rusty-0.1.0/target/wheels/rusty-0.1.0-cp38-cp38-macosx_11_0_arm64.whl
Successfully built rusty-0.1.0.tar.gz and rusty-0.1.0-cp38-cp38-macosx_11_0_arm64.whl


Text spacing adjust on selected point

Currently the selected point pop up display box is fixed size, but values have different numbers of digits, so it some starts to overlap/bump into copy icon. Should either:

change the display formatting (duplicate the function used currently used/just add extra slicing)
or dynamically size the selected point box

Plan: adjust existing display format function to have max ~5/6 (whatever it is) characters long.

Fixed here.


Allow Git basic authentication in user session

Due to the GIT_ASKPASS configuration, the usage of the Git integration of Eclipse is not possible. However, users would like to clone and push Git repositories with authentication. Therefore, we have to set a proper git credential manager during preparation.

Seems to work already in persistent session. Issue can be closed.


Improve Scan Areas tab functions

Option to assign smaller areas to bigger ones and create sections, eg. section called New York with areas assigned to it: Manhattan, Harlem, Chinatown, etc. Each smaller areas could be in columns instead of one big column long af 😬 Example below taken from PMSF

Add specific areas to role perms so roles with area restrictions won't see areas that are outside of their area

Also resolved in #518


Can't select any model if Ollama has a long list of models

Describe the bug
If i have a large number of models on my ollama instance, it will only show me the top 8 or something, i can't scroll down to see more models.
To Reproduce
Install many models, like 10 on a ollama server. and edit providers.
Expected behavior
Should be a scrollbar, to see more models.
Screenshots

Logging
N/A
API Provider
Ollama
Chat or Auto Complete?
N/A this happens with any model list.
Model Name
N/A any model
Desktop (please complete the following information):

OS:  Archlinux
Browser Brave
Twinny Version 3.15.6

Additional context
Its a regression... on 3.14.7, it has the scrollbar.

Hey, when I tested it I could see all my models in there?


⚠ sgm2.serverssh.net has degraded performance

In a26624b, sgm2.serverssh.net (http://sgm2.serverssh.net:10000/) experienced degraded performance:

HTTP code: 200
Response time: 10627 ms

Resolved: sgm2.serverssh.net performance has improved in cb389f8.


README: fix Jenkins badge

Let's see...

The pretty version? http://ci.px4.io:8080/blue/organizations/jenkins/Dronecode%2FDronecodeSDK/branches/

Thx @dagar.

Don't know why this is failing, but the change looks good.


Register HTMLForge.jl

@JuliaRegistrator register()

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

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


Remove environment management file

Reference Issues or PRs
While I was working on something else, I came across this environment management page and realized that its completely incorrect. This PR removes it.

What does this implement/fix?
Put a x in the boxes that apply

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds a feature)
[ ] Breaking change (fix or feature that would cause existing features not to work as expected)
[x] Documentation Update
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build related changes
[ ] Other (please describe):

Testing

[x] Did you test the pull request locally?
[ ] Did you add new tests?

Documentation

Access-centered content checklist
Text styling

[ ] The content is written with plain language (where relevant).
[ ] If there are headers, they use the proper header tags (with only one level-one header: H1 or # in markdown).
[ ] All links describe where they link to (for example, check the Nebari website).
[ ] This content adheres to the Nebari style guides.

Non-text content

[ ] All content is represented as text (for example, images need alt text, and videos need captions or descriptive transcripts).
[ ] If there are emojis, there are not more than three in a row.
[ ] Don't use flashing GIFs or videos.
[ ] If the content were to be read as plain text, it still makes sense, and no information is missing.

Any other comments?

I just realized file is actually directed an admin who is about to build the platform - not at end users who are creating an environment while working on the platform. In that case, I will rework the messaging on this page.


Add composer plugin to auto-install missing implementations

Q
A

Bug fix?
no

New feature?
yes

BC breaks?
no

Deprecations?
no

Documentation
https://github.com/php-http/documentation/pull/301

License
MIT

This PR makes discovery able to auto-install a missing implementation when a dependency requires both php-http/discovery and one of the supported *-implementation virtual packages.
The code comes from https://github.com/FriendsOfPHP/well-known-implementations, which I plan to retire if this approach is accepted.
Note that we started discussing this topic with @dbu at SymfonyCon and we agreed this could be the best path forward.
To Do

[x] Updated CHANGELOG.md to describe new feature
[x] Documentation pull request created
[x] Make the plugin work with Composer v1 and PHP 7.1
[x] Add rule to install http-interop/http-factory-guzzle when Guzzle's PSR-7 v1 is needed/installed and PSR-17 implementation is required
[x] Add more test

PR is ready. It comes with updates to the CI. (The remaining failure is unrelated)

i merged the build setup cleanups to 1.x branch. please rebase this MR :-)

PR rebased and green, comments addressed. Thanks for the review!

Comments addresses

Rebased, all green, ready for merge + tag :)

just to ping the relevant people: this PR lead to a breaking change for the current minor version which was reported in https://github.com/php-http/discovery/issues/213

It also has a bug, running composer install now with the plugin enabled leads to an infinite loop of composer install

@Tofandel thanks for the reproducer, I opened https://github.com/php-http/discovery/pull/214 to fix the issue.

There is another issue with this plugin. If you pass options to composer update such as —ignore-platform-reqs they are discarded when the second update is discarded, and so the second update fails.

Good catch @dunglas. This should be fixed by https://github.com/php-http/discovery/pull/216


Make GoogleCloudServiceAccountDictProfileMapping dataset profile argument optional

Description
This PR follows the methodology in https://github.com/astronomer/astronomer-cosmos/pull/683/ by modifying the GCP GoogleCloudServiceAccountDictProfileMapping() profile_args not require dataset as a required argument.
Related Issue(s)
Closes #837
Breaking Change?
Not to my knowledge.
Checklist

[x] I have made corresponding changes to the documentation (if required)
[x] I have added tests that prove my fix is effective or that my feature works

tagging @astro-cosmos-admins @tatiana for review, I wasn't able to tag anyone as reviewer since I don't have permissions so hopefully writing it as a comment is okay. Thank you

Hey @oliverrmaa, Thanks for your contribution! Could you please rebase and respond to @jbandoro's feedback? we're excited to see this move forward.

Hi @oliverrmaa, I was wondering if you had a chance to read my previous comments. Are you still working on it, or would it be alright if I take it forward from here? Thank you!

Since we consider this change very relevant, we ended up rebasing and addressing conflicts in a separate PR and adding @oliverrmaa as a co-author: #1017


Bundler plugin without a gem, show wrong message

Hi, i have a wrong message error when i execute bi command without a gem bundler installed
I got this message:
Can't 'bundle install' outside a bundled project
i'm inside the project path.
The error message should be something as:
Bundler gem is not installed.

If there is no Gemfile then it isn't a bundled project. I think that's what the error means.


Add CVE number to name attribute in JUnit output so that it will be displayed on Azure Pipeline Runs results

Is your feature request related to a problem? Please describe.
Azure Pipeline supports publishing the DependencyCheck report generated by maven in Junit format to its Test Runs report page.
The CVE number which is arguably the most important piece of information in the generated report is missing from being displayed on the Azure DevOps Runs Report page. Instead, the attribute "name" under the tag testcase is displayed, .e.g<EMAIL_ADDRESS>Describe the solution you'd like
Add the CVE number to the attribute "name" so that it will be displayed on Azure DevOps Runs Report page, e.g.,
Current:
<testcase classname="CVE-2022-25857"<EMAIL_ADDRESS>Proposed:
<testcase classname="CVE-2022-25857" name="CVE-2022-25857<EMAIL_ADDRESS>Describe alternatives you've considered
Any other means so that the CVE number is displayed on the Azure DevOps Runs page are appreciated.
Additional context
Exhibit 1 - Azure DevOps screen : On the Runs > Test results page, no CVE number is displayed:

Exhibit 2 - Azure DevOps screen : Drill down the failed test case, no CVE number is displayed. The title seems like to be extracted from the "name" attribute only.

Exhibit 3 - The sample junit report xml file showing the proposed attribute change, i.e., prepend CVE number to the "name" attribute of the testcase tag.

I would say 'classname' should be an attribute that a junit test results display should be capable of revealing and would suggest to request to the Azure DevOps team to make exposure of it an option in the pipeline test results page.

Agreed, thank you for the suggestions.


Revert "Rotated Paragraph 😁"

Reverts jeffreycharters/station#51 - I need to re-examine the changes to the list styles

@jeffreycharters I wasn't quite sure what to do! 😅
I think in the future I will take a little more time with the code review.
I guess if something gets overlooked in that process, we could always add it as an issue... 🤔


Alarm panel kepad showing

Checklist

[X] I checked for similar existing issues (both open and closed) before posting.
[X] I am running the latest version.

Expected behavior
[What you expected to happen]
The core Lovelace alarm panel card keypad to not show if the alarm is in the disarmed state and Use Arm Code is off.
Actual behavior
[What actually happened]
The keypad is always visible.

Steps to Reproduce
[Explain how to see the behaviour]
Set Use Arm Code switch off:

Disarm the alarm:

Keypad should not be visible in this case.

The Lovelace Alarm Panel card only looks at the code_format option for determining whether the keypad should be visible (see code).
This property only is intended for indicating whether the code is numeric or text.
The property code_arm_required (as defined in the native alarm_control_panel entity) is not evaluated by the card, while Alarmo implements it (together with code_disarm_required, those two are essentially controlled by the switches you mentioned).
Summarizing I think the problem is on the side of the Lovelace Alarm Panel card, and on the side of Alarmo I cannot do much to improve this.
Since the card lacks some more essential features, there is an Alarmo Card which offers a slightly better experience.
It will hide the keypad when not applicable, but also it will also show reason why arming failed, and some more additions.
My recommendation would be to use it instead, or file a bug report in HA frontend for this.

Interesting. I was wondering how bwalarm managed to do it and found this:
https://github.com/akasma74/Hass-Custom-Alarm/blob/master/custom_components/bwalarm/alarm_control_panel.py#L718
Looks like it sets code_format to none when disarmed and an arm code is not required.
As your integration is just an easy way to set up the required parts of a manual alarm I guess requesting this is beyond the scope of the project.
I was hoping to use the core card as I have quite a bit of card-mod customisation of the core card that does not work with the alarmo card. Looks like I will have to spend the to do this.  As your integration is just an easy way to set up the required parts of a manual alarm I guess requesting this is beyond the scope of the project.

This is definitely worth considering.
For me a small change so if it helps you and doesn't bother others, I'm fine with it.

I was hoping to use the core card as I have quite a bit of card-mod customisation of the core card that does not work with the alarmo card. Looks like I will have to spend the to do this. I hate css :)

I am not a user of card-mod, but I know it is used by a lot of people. I do want to walk the extra mile and make alarmo-card card-mod-friendly. But I would need some pointers on what to change for this.
If you are willing to assist on this, please open a github issue in alarmo-card for follow-up.
I will re-open this and make the update for code_format (when I find the time to do so).

Nice one. Thanks Niels.

I made some changes to accommodate this (https://github.com/nielsfaber/alarmo/commit/82b428f11199abe80e92f861473399c95f8ebb69).
Will try to release it soon.
Disarmed (left=Alarmo card, right=Alarm Panel card)

Armed(left=Alarmo card, right=Alarm Panel card)

This is implemented in the latest release (v1.8.0).
Please update Alarmo locally and check whether it works as you would expect.
If so, you can close the issue. Otherwise, please let me know.
Thanks for the help 👍

Thanks for the update.


Getting an "Unable to create Meetup account" error on signing within an app

We have an iOS app using server flow authentication (https://secure.meetup.com/oauth2/authorize?client_id=<client_id>&response_type=code&redirect_uri=<redirect_uri>&set_mobile=on). It works fine on the iOS simulator but run into issues on an actual device. Upon signing in with either Google or Facebook credentials, the user is taken back the login screen with an "Unable to create a Meetup account." error message displayed at the top. The sign in process works fine in Safari, just not within the app.

Closing as I'm no longer doing any work with the APIs


How to compile diesel with SQLite JSON support

SQLite comes with JSON support, but it's only enabled by default in the SQLite shell. I'm trying to create a column of type JSON, which works fine from the SQLite shell, but fails with Unsupported type: json when run as a migration via diesel.
The SQLite docs mention a compile-time option to enable the JSON extension, but I don't know how that applies in the context of diesel. Is there a way to pass this option through via cargo? If not, is there another way to enable the extension?
Or maybe the JSON type is not supported by design in diesel and I should stop trying?

Having slept on it, the compile-time option doesn't make sense: I'm using the SQLite library as provided by my OS, which is already compiled (with the option enabled, I've checked), and diesel just links against that, right? So either there is another way to enable JSON support (a --feature perhaps?) or I'm out of luck :)


Typo "@mycol"→"@mycol"

bold with escape characters
https://docs.microsoft.com/en-us/sql/relational-databases/errors-events/mssqlserver-137-database-engine-error?view=sql-server-ver15

@hyoshioka0128 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Thanks.


All emails in sendgrid needs review

@BUUPE/eboard Please review emails for wording

Moving this to the firebase master project since everything is there


token-cli: bulk_signers has too much stuff

theres two things here:

~keys are duplicated all over the place. this is trivial, wrap push() in contains() checks~
payer shouldnt be in the vec if its not also an authority on something, because in this case it doesnt need to be a signer on the instruction, and construct_tx handles signing on the transaction. this can be fixed after everything is refactored to go through the client

to expand on the rationale, since i lost the place where i orginally explained it: the token client takes signing_keypairs (which is called bulk_signers in the cli) and checks to see if it the the signer for the authority: &Pubkey arg that almost all functions take. if so, it passes an empty array to the token instruction constructor, and the the instruction will be signed with authority only. if not, it presumes the array contains signers for a multisig, and provides them to the instruction so their pubkeys can all be marked on the instruction
this means we want to strip down bulk_signers to just the authority in the non-multisig case, so it doesnt demand signatures from accounts it doesnt need them from


Rollback to use a generated name for each TaskRun

Similar to how a Deployment resource generates names for pods, we
should stick to an auto-generated name for TaskRuns. This will
avoid issues like #315.
We use to have the auto-generated name before, but it was modified
with PR #313
With different names between BuildRuns and TaskRun, some code refactoring
on the buildrun controller was required to preserve the improvements done
in PR #313. Also, unit-tests were improved to deal with different Reconcile
request on the BuildRun controller, depending if they come from a BuildRun
object or a TaskRun object event.

/ok-to-test

/lgtm
/approve


Performance is very bad when grpc concurrency is set to a large value

Testing Update statement in a cluster with each host (40 core) running 6 tikv:

GRPC Concurrency
QPS

40
10000

4
18000

This result is tested with @jackysp

can you see any big difference between them through Perf or metrics?

@siddontang Context switch increased about 60% with grpc concurrency is set to 40.


remove  node update based on enclosure node update

Update removing node based on @iceiilin 's PR https://github.com/RackHD/on-tasks/pull/26

when removing a compute node, check the relationship within this node, if it's enclosed by an enclosure node, after remove compute node, also remove the relationship within enclosure node, when all nodes   of an enclosure are removed, remove the enclosure automatically.
add nodes-api-service.js to handle nodes api function.
add unit tests

We are testing Travis CI. Since there are no .travis.yml files it will fail.

test this please

:+1:
with a suggestion about some potential cleanup.

codes has been refactored and updated

Thanks @anhou! Still :+1:

still :+1: , though I have some minor suggestion


the gamePassword volume also breaks the lowercase RFC 1123 name requirement.

the gamePassword volume also breaks the lowercase RFC 1123 name requirement.
Originally posted by @avanier in https://github.com/SQLJames/factorio-server-charts/pull/20#issuecomment-1312622917

Wokring on it right now, PR to be expected soon


Cleaned up language in the README

Just a couple fixes to the wording in the README. Fixed a typo and simplified the language regarding adding disposables to disposable bags.

Thanks 👍


Checkbox not working

Description can be found there: https://getgrav.org/forum#!/general:checkbox-form-field-on-modu

copied forum post here for clarity:

I have got a frontend form working, but adding a checkbox field throws validate errors on the first two required fields, removing the checkbox field lets work again like a charm. Using a radion button field does work instead, but not a checkbox (Grav v1.1.0-rc.3).

name: confirmation
label: ‘I want to get a confirmation’
type: checkbox

I don't understand, is this a problem on frontend or backend?
On frontend we aren't using any JS for forms, the validation is purely from the form plugin.

It have been on the Frontend! I have tried to get a checkbox into the form, which was not validating right. I had a form with three text inputs, one textarea and then a checkbox. Filling in the form, and using recaptcha should send a mail. I was always getting validation errors for the first text fild. I have then changed the checkbox to a radio button to get the form work.

Can you paste the whole form definition, so I can try it?

title: Home
content:
items<EMAIL_ADDRESS>order:
by: default
dir: asc
custom:
- _teaser
- _event
- _program
- _sessions
- _registration
body_classes: home
onpage_menu: true
form:
action: /
name: registration
fields:
    - name: name
      label: Name
      placeholder: Your name
      autofocus: on
      autocomplete: on
      type: text
      validate:
        required: true

    - name: email
      label: E-Mail
      placeholder: Your e-mail-adress
      type: email
      validate:
        required: true

    - name: organisation
      label: Name of your institution/organization/company (optional)
      placeholder: Institution/Organization/Company
      type: text

    - name: sessionsubject
      label: Sessiontheme (optional)
      placeholder: Your Sessionsubject
      type: text

    - name: sessiondescription
      label: Beschreibung des Sessionthemas (freiwillig)
      placeholder: Beschreibung der Session
      type: textarea

	//That did not work, getting validation errors from the first two fields! But using type: radio there, it does work!
    - type: checkbox
      label: You want to get a confirmation for attending?
      validate:
        required: true

    - name: g-recaptcha-response
      label: ReCaptcha
      type: captcha
      recatpcha_site_key:
      recaptcha_not_validated: 'Antispam not valid!'
      validate:
        required: true

buttons:
    - type: submit
      value: Send

process:
    - captcha:
        recatpcha_secret:
    - email:
        from: "{{ config.plugins.email.from }}"
        to: "{{ form.value.email|e }}"
        bcc: "{{ config.plugins.email.to }}"
        subject: "[Sign] {{ form.value.name|e }}"
        body: "{% include 'forms/data2.html.twig' %}"
    - save:
        fileprefix: contact-
        dateformat: Ymd-His-u
        extension: txt
        body: "{% include 'forms/data.txt.twig' %}"
    - message: Thank you! :)
    - display: /thankyou

I tried and I don't see any problem with it. Which browser are you using?
Can you make a short video of what is happening?

Firefox

Will do it again and you show the result in the next days!

I'm also unable to reproduce this.

There you have the screenshot of the validation errors I am getting with checkbox.

And this missing required fields I am getting after filling the form correctly. That is only happening with type: checkbox, but type: radio does work.

FYI, even after updating the system to the last releases the checkbox is still throwing errors.

I just realized that in your YAML the checkbox field doesn't have a name.
You have:
- type: checkbox
  label: You want to get a confirmation for attending?
  validate:
    required: true

Should be something like:
- name: confirmation
  type: checkbox
  label: You want to get a confirmation for attending?
  validate:
    required: true

Can you try changing that?

Even with name: confirmation I get the same validation errors as shown in the screenshot!

I can't reproduce with antimatter. PM me on Gitter your user folder and I'll try with your same setup.

Thanks for the user folder, I was able to reproduce this now. This is a form plugin issue with backward incompatibility.
I have now fixed it with https://github.com/getgrav/grav-plugin-form/commit/83f34d401a1952dfb4dd97f2c0d229c71ca56fc0
Can you try applying the change and confirm that works?
Also please next time open the issue in the proper repository, that way we can keep things more organized.
Thanks!

Yes, getgrav/grav-plugin-form@83f34d4 does work now! Thanks!

Awesome 👍

Thank you, commit #83f34d4 solved the form validation problem I was trying to fix for two days (missing required fields while they were correctly filled) :+1:

Doing a point release now, which includes that fix

Seems that checkbox with validation required is not working

Yes, I have the same problem as well. My contact form with checkbox as required field is not working. Only if i set the default value to true. But that is not the right way for agreements to terms or something like this.
Is there a solution to this problem?

Can confirm that it is not working.

I can't replicate this.
I have this form:
---
title: Checkboxes
form:
    name: issue-form
    client_side_validation: false
    fields:
        checkboxes:
            label: Checkboxes
            default:
                - option-a
            type: checkboxes
            options:
                option-a: 'Option A'
                option-b: 'Option B'
                option-c: 'Option C'
            validate:
                required: true
                min: 2
                message: 'Pick at least 2'
        accept_rules:
            label: 'Accept rules'
            type: checkbox
            validate:
                required: true
                message: 'Please accept the rules to send'
    buttons:
        -
            type: submit
            value: Send
    process:
        -
            message: 'Thank you!'
---

# GitHub Form Issues


[bug 1153120] show linkedin username or old url

If the url is the new style show the nickname like for the others, if it is old style with id number show the complete link

Coverage decreased (-0.04%) to 92.911% when pulling<PHONE_NUMBER>2e758f3508f7920f6128ff424bd509 on Mte90:Mte90/1153120 into 338097d0a54849a43e5d2c0cdc07f96f809ae5ad on mozilla:master.

This needs a rebase to master.

I had some problems on the rebase, do you have any suggestions for that? with the tool of github was not good and also manually :-/

@Mte90 I rebased this to a new branch on my fork. It's actually this commit. You can checkout and push this to your fork and open a new PR.

done https://github.com/mozilla/mozillians/pull/1604!


Menu is collapsed

This is supposed to be mobile view.

@guo , so what is wrong on the above screenshot?


Bad request when submitting Kaggle entry

On my GPU server, I've started getting 400 response when submitting Kaggle entries.
$ kg submit -v "sample_submission.csv" -u <my_username> -p <my_password> -c digit-recognizer -m "test submission"
Starting new HTTPS connection (1): www.kaggle.com
https://www.kaggle.com:443 "GET /c/digit-recognizer HTTP/1.1" 200 15896
https://www.kaggle.com:443 "POST /blobs/inbox/submissions HTTP/1.1" 200 303
https://www.kaggle.com:443 "POST /blobs/inbox/submissions/59d0cf127a134bc2a0c0a746aede19cf/240909/1512782907983 HTTP/1.1" 200 525
https://www.kaggle.com:443 "POST /c/digit-recognizer/submission.json HTTP/1.1" 400 235
list indices must be integers, not str

I wanted to make sure it wasn't my submission that was malformed, so I checked with the sample_submission.csv that came with the digit-recognizer competition. Same error. The sample submission file and my own submission file look fine. To be extra careful, I download one of my recently-successfully-submitted entries to Kaggle, and that submission CSV file gives me the exact same error message.
I try with both Python 3 and Python 2.7. I am using kaggle-cli 0.12.13. I'm SSH'd into a remote machine and I am using a VPN.

Found out that I reached the team limit of submissions. Maybe a better error message could be added here?

Thanks for the report. The error message should be handed. I'll check it.


Show roadmaps info in the work item.

Within a work item (Epic/Feature), I want to be able to reflect which roadmaps is that work item being tracked in. Is there a way to reflect this info within the work item?

Sorry, but this code in this repo is not currently being maintained. We recommend you use the Delivery Plans feature that is core to Azure DevOps.


Build DCMTK with optional dependencies enabled

The current port of DCMTK does not enable its many optional dependencies. Given many (all?) of these optional dependencies are available in vcpkg, it would be nice to enable them. The main dependencies are:

libiconv or icu
libjpeg-turbo
openjpeg
libpng
libxml2
openssl
tiff
zlib

When you install the official DCMTK sources, they provide these dependencies as pre-built binaries + headers, and their CMake scripts can find them. Unfortunately the naming scheme for these pre-built dependencies differs from the standard names, so some CMake patches will be required.

This branch  on my fork gets most of the way there. We don't use OpenJPEG so I don't have that sorted out. Here's a summary of the changes.
Some things to note:

I opted to copy CMake 3.14's find modules as some of them have only been added to CMake recently and we don't always have access to the latest version.
I had to update the CMake config template to expose the dependencies to consumers of DCMTK.

example
vcpkg_configure_cmake(
    SOURCE_PATH ${SOURCE_PATH}
    PREFER_NINJA
    OPTIONS
        -DWITH_LIBICONVINC:PATH=${CURRENT_INSTALLED_DIR}
        -DWITH_OPENSSLINC:PATH=${CURRENT_INSTALLED_DIR}
        -DWITH_LIBXMLINC:PATH=${CURRENT_INSTALLED_DIR}
        -DWITH_LIBTIFFINC:PATH=${CURRENT_INSTALLED_DIR}
        -DWITH_LIBPNGINC:PATH=${CURRENT_INSTALLED_DIR}
        -DWITH_SNDFILEINC:PATH=${CURRENT_INSTALLED_DIR}
        -DWITH_ZLIBINC:PATH=${CURRENT_INSTALLED_DIR}
        -DDCMTK_WITH_ICONV:BOOL=ON
        -DDCMTK_WITH_OPENSSL:BOOL=ON
        -DDCMTK_WITH_PNG:BOOL=ON
        -DDCMTK_WITH_SNDFILE:BOOL=ON
        -DDCMTK_WITH_STDLIBC_ICONV:BOOL=ON
        -DDCMTK_WITH_TIFF:BOOL=ON
        -DDCMTK_WITH_XML:BOOL=ON
        -DDCMTK_WITH_ZLIB:BOOL=ON
)

example
vcpkg_configure_cmake(
    SOURCE_PATH ${SOURCE_PATH}
    PREFER_NINJA
    OPTIONS
        -DWITH_LIBICONVINC:PATH=${CURRENT_INSTALLED_DIR}
        -DWITH_OPENSSLINC:PATH=${CURRENT_INSTALLED_DIR}
        -DWITH_LIBXMLINC:PATH=${CURRENT_INSTALLED_DIR}
        -DWITH_LIBTIFFINC:PATH=${CURRENT_INSTALLED_DIR}
        -DWITH_LIBPNGINC:PATH=${CURRENT_INSTALLED_DIR}
        -DWITH_SNDFILEINC:PATH=${CURRENT_INSTALLED_DIR}
        -DWITH_ZLIBINC:PATH=${CURRENT_INSTALLED_DIR}
        -DDCMTK_WITH_ICONV:BOOL=ON
        -DDCMTK_WITH_OPENSSL:BOOL=ON
        -DDCMTK_WITH_PNG:BOOL=ON
        -DDCMTK_WITH_SNDFILE:BOOL=ON
        -DDCMTK_WITH_STDLIBC_ICONV:BOOL=ON
        -DDCMTK_WITH_TIFF:BOOL=ON
        -DDCMTK_WITH_XML:BOOL=ON
        -DDCMTK_WITH_ZLIB:BOOL=ON
)

Got error ninja: error: 'C:/workspace/vcpkg/installed/x86-windows/lib/dcmtkssl_d.lib', needed by 'bin/dcmtlsd.dll', missing and no known rule to make it

_d.lib = debug
C:/workspace/vcpkg/installed/x86-windows/debug/lib/...


Changing sampling rate effect?

Does training on audio data that has a different sampling rate from LJ Speech Dataset have a negative effect on final outcome? I ask because I have audio data with 16000 sampling rate, haven't tried training on it yet.

One can train Tacotron 2 on 16khz sampling rate. Note that the highest representable frequency will be 8khz.


Implement new curation and reassembly

This PR implements a new approach to receiving and applying curations, including the handling of multiple curation types, handling project-specific curations, and making changes according to curations during assembly.

Some tests are failing for Travis technical reasons, will fix in a subsequent PR.


Maintain order of attributes when encoding to JSON

The GSON library for Android allows to keep order of attributes when encoding the object to JSON.
Is there anything that could be done to develop this feature for this library?
https://github.com/google/gson

Unfortunately this is not a priority for me. JSON objects are un ordered by specification. If you need to maintain order I suggest including a order key in your model object.


blog for Artificial Intelligence casting future in Web Development added

Checklist

Please note that in case of below checklist not updated accordingly, the maintainers have the right to immediately close your pull request.

[x] You created a branch from dev branch.
[x] You PR is raised on dev branch and not onmaster.
[x] Blog follows Blog Guidelines.
[x] You have read the Contribution Guidlines before creating this PR.
[x] Checked for any duplicate blog entry.
[x] Checked for all grammatical errors in the blog.
[x] You have not published the blog content anywhere else on the internet on platforms like medium, dev.to etc.
[x] The content is not copy-pasted from anywhere else on the Internet.

Description of change

Author Details for Blog Post Entry

Closing the PR due to lack of response.


Transparancy

Hello o/
I've been using Slab Turf blocks around a farm, and whenever I harvest the items frequently land inside/under the Turf Slabs, which makes me wonder if they're transparent - And whether they should or shouldn't be?

I think you meant like intangible/non solid rather than transparent. Either way they're supposed to act exactly like slabs and nothing in the code would make them behave differently.
Try the same setup with vanilla slabs and see if the issue is there.

Alright, thank you.


Suggestion: update code style to ES6

Hi @chill117 ,
Thanks for this awesome tool. I suggest to update and refactor code to ES6 style. It's more clear and more robust.

@mnlbox Thank you for the kind words. Unfortunately, for the near-term I do not plan to migrate the code-bases that I maintain to ES6. I do not yet have much experience working with it. I feel that it would take some dedicated time to learn the syntax and research the features, performance trade-offs, support, etc.


Missing encore functions "encore_entry_css_files" and "encore_entry_js_files"

In Webpack Encore we have those two functions encore_entry_css_files and encore_entry_js_files.
It would be nice if we have similar functions for Vite, otherwise it's difficult to replace Encore with Vite.

I wojto, has you can see if you observe the generated entrypoints.json there is

css
js
preloaded-js
dynamic-preloaded-js
assets

associated to one entry point.
in dev mode there is also inline content added.
it's not only an array of js file and an array of css files.
if you have a specific use case you can develop your own twig functions EntrypointRenderer and EntrypointsLookup can be injected has dependencies in your TwigExtension.
hoping to help you move forward with your proposal
doc: https://symfony-vite.pentatrion.com/guide/tips.html#dependency-injection
current twig functions: https://github.com/lhapaipai/vite-bundle/blob/main/src/Twig/EntryFilesTwigExtension.php

Hi @wojto,
with v5.x you can define listeners to add/remove/modify your <script>/<link> on the runtime. I think it can be helpful for you ?
migration v4->v5
custom attributes


`Extension 'cannot act on auto derived type' var '

dart sdk version: Dart SDK version: 2.12.0-29.10.beta (beta) (Tue Nov 17 10:50:22 2020 +0100) on "macos_x64"
Is is my code
void main(){
    var a;
    a = "Test";
    print(a.sayHello());
}

extension HelloString on String {
  String sayHello() {
    return 'Hello World';
  }
}

output
NoSuchMethodError: Class 'String' has no instance method 'sayHello'.

I believe it is working as intended, the type inferencing for local variables works by intefering types from the initializer, if any. Subsequent assignments are not taken into account, see https://dart.dev/guides/language/type-system#local-variable-inference.
Your code written as
void main(){
    var a = "Test";
    print(a.sayHello());
}

extension HelloString on String {
  String sayHello() {
    return 'Hello World';
  }
}

should work.

I believe it is working as intended, the type inferencing for local variables works by intefering types from the initializer, if any. Subsequent assignments are not taken into account, see https://dart.dev/guides/language/type-system#local-variable-inference.
Your code written as
void main(){
    var a = "Test";
    print(a.sayHello());
}

extension HelloString on String {
  String sayHello() {
    return 'Hello World';
  }
}

should work.

Type promotion has been enhanced substantially in Dart with null safety (a new feature bundle which is enabled in Dart 2.12), and that's the mechanism that could have given a a different type than dynamic (which is what it gets by default when there is no information at all in the declaration, as in var a;).
So you can move the initialization into the declaration, as @a-siva mentioned. But with null safety you can also get a promotion (in this case: from dynamic to String) if the target type String is 'a type of interest' for the given variable. One way to achieve that a type is 'of interest' for a variable is to test for it:
// Requires that null safety is enabled.

void main() {
  var a;
  if (a is! String) { // `String` now of interest for `a`.
    a = "Test"; // This will promote `a` to have type `String`.
  }
  // At this point it is known that `a` was already a `String`,
  // or a `String` was assigned to it, so it is a `String`.
  print(a.sayHello()); // .. and then we can invoke an extension method `on String`.
}

extension HelloString on String {
  String sayHello() {
    return 'Hello World';
  }
}

The situation is tricky, because the type of a is dynamic if no promotion has occurred, and then a.sayHello() will be accepted at compile-time, because we can invoke any method on a dynamic receiver. But it will still fail at run time (a receiver of type dynamic never gets an invocation of an extension method).
So it's a good habit to use an initializer in the declaration when possible. You may still want, and get, type promotions for a variable like var a = "Test";, but when the type at the declaration is String (or any other type T different from dynamic), you know that it will always have a type which is a subtype of String (resp. T), and then it will never give rise to a dynamic method invocation, that is, all method invocations on that variable are type checked statically.
@rhymelph - I'll close the issue, because the example is working as intended.

Type promotion has been enhanced substantially in Dart with null safety (a new feature bundle which is enabled in Dart 2.12), and that's the mechanism that could have given a a different type than dynamic (which is what it gets by default when there is no information at all in the declaration, as in var a;).
So you can move the initialization into the declaration, as @a-siva mentioned. But with null safety you can also get a promotion (in this case: from dynamic to String) if the target type String is 'a type of interest' for the given variable. One way to achieve that a type is 'of interest' for a variable is to test for it:
// Requires that null safety is enabled.

void main() {
  var a;
  if (a is! String) { // `String` now of interest for `a`.
    a = "Test"; // This will promote `a` to have type `String`.
  }
  // At this point it is known that `a` was already a `String`,
  // or a `String` was assigned to it, so it is a `String`.
  print(a.sayHello()); // .. and then we can invoke an extension method `on String`.
}

extension HelloString on String {
  String sayHello() {
    return 'Hello World';
  }
}

The situation is tricky, because the type of a is dynamic if no promotion has occurred, and then a.sayHello() will be accepted at compile-time, because we can invoke any method on a dynamic receiver. But it will still fail at run time (a receiver of type dynamic never gets an invocation of an extension method).
So it's a good habit to use an initializer in the declaration when possible. You may still want, and get, type promotions for a variable like var a = "Test";, but when the type at the declaration is String (or any other type T different from dynamic), you know that it will always have a type which is a subtype of String (resp. T), and then it will never give rise to a dynamic method invocation, that is, all method invocations on that variable are type checked statically.
@rhymelph - I'll close the issue, because the example is working as intended.