Linux kernel headers deb fails to install on Ubuntu 19.04

It seems there is a libssl dependency issue:
dpkg: dependency problems prevent configuration of linux-headers-4.19.24-c52ea7b07f93:
linux-headers-4.19.24-c52ea7b07f93 depends on libssl1.0.0 (>= 1.0.0); however:
Package libssl1.0.0 is not installed.
On Ubuntu 19.04. libssl 1.1 is installed.

I've asked @stefanlupsa to research this and decide if this requires a build vm upgrade from current 16.04 ubuntu, or see what other solution is available.

I could repro the issue and tried a potential fix but this does not solve the problem:
If the kernel builder is on xenial the header install will fail on distros that have libssl1.1 as xenial has libssl1.0 and no release candidate for libssl1.1
I tried adding the libssl1.1 from a bionic repo to the xenial kernel builder, this fixes the problem on disco but creates the same problem when installing on xenial (and probably on any other distro that has libssl1.0 or less).

Resolved in https://github.com/dbcli/mssql-cli/issues/252


Add disruption test for sequence no and primary terms

Summary of the changes / Why this improves CrateDB
Checklist

[x] User relevant changes are recorded in CHANGES.txt
[x] Touched code is covered by tests
[x] Documentation has been updated if necessary
[x] CLA is signed
[x] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in CHANGES.txt
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

@seut this fixes the flakiness that was caused by a possible delayed shard allocation taking 1 minute (default) and we were waiting for a maximum of 30seconds in assertBusy. This changes the delayed time to 5 seconds (I pondered setting it to 0 but thought that having a delay might be more realistic, however I'm also ok to change it to 0)

@seut fixed the flakiness further 🤞🏻

retest this please

retest this please


'_coverage_penalty_weight' attribute not found:

When running in a ipython notebook
reformulator = reformulator.Reformulator(
      hparams_path='px/nmt/example_configs/reformulator.json',
      source_prefix='<en> <2en> ',
      out_dir='/tmp',
      environment_server_address='localhost:10000')

AttributeError: 'DiverseBeamSearchDecoder' object has no attribute '_coverage_penalty_weight'
When running via the cli:
python -m px.nmt.reformulator_and_selector_training \
--environment_server_address=localhost:10000 \
--hparams_path=px/nmt/example_configs/reformulator.json \
--enable_reformulator_training=true \
--enable_selector_training=false \
--train_questions=$SQUAD_DIR/train-questions.txt \
--train_annotations=$SQUAD_DIR/train-annotation.txt \
--train_data=data/squad/data_train.json \
--dev_questions=$SQUAD_DIR/dev-questions.txt \
--dev_annotations=$SQUAD_DIR/dev-annotation.txt \
--dev_data=data/squad/data_dev.json \
--glove_path=$GLOVE_DIR/glove.6B.100d.txt \
--out_dir=$REFORMULATOR_DIR \
--tensorboard_dir=$OUT_DIR/tensorboard

AttributeError: 'DiverseBeamSearchDecoder' object has no attribute '_coverage_penalty_weight'
This should be set in the parent object as per https://github.com/tensorflow/tensorflow/blob/master/tensorflow/contrib/seq2seq/python/ops/beam_search_decoder.py#L338
Not clear on what is missing

This was fixed some hours ago. Please try again and let us know if the error persists.


CI failing

What happened?
Main branch builds are failing after the last commit as noted by #team-provider-alerts channel.
Expected Behavior
NA
Steps to reproduce
NA
Output of pulumi about
NA
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

intermittent failure, re-ran build and master is green https://github.com/pulumi/pulumi-rancher2/actions/runs/4642205050


added retry count if failed to send

In my system, there is Kafka only for logging but as Kafka is not yet completely installed, it often crashes. If Kafka is down, an application gets blocked. I believe an application never gets affected by logging. Therefore, I added a attribute for retry count.
I changed only two java files below.

org.apache.logging.log4j.kafka.appender.KafkaManger
org.apache.logging.log4j.kafka.appender.KafkaAppender

Thanks.

sorry, this is showing 115 files changed. Did you modify line endings or something? I can't really review this as is.

I modified and reopened

This patch looks good to me. Can you also provide a patch to the release-2.x branch?  Also, is there any way a test can be provided to verify this?

PR manually merged with minor changes.


Bypass polkit dialog if user is already on input group

This PR implements the feature of bypass the Polkit dialog when the user belongs to the input group, which autoamically grants access to udev/evdev events. This functionality is important for two reasons:

Non-privileged Users: Users who cannot elevate privileges but are members of the input group should still be able to access the program without requiring additional authentication.
User Convenience: Users in the input group can access the program more quickly, enhancing user experience by eliminating unnecessary authentication prompts.

Additionally, please note that the inclusion of the grp.h header file is essential, as it provides the necessary group-related functions required for this implementation.

I suggest to rename the function if you accept any group name as parameter, or just remove the parameter if you only check input group.

User Convenience: Users in the input group can access the program more quickly, enhancing user experience by eliminating unnecessary authentication prompts.

Please remember that adding a user to input group is also a security risk, which means all process running with this user can access your input devices and listen to your keyboard events (even your user is not logging in), this is generally not recommended by most distros. Desktop session and normal clients gain input permission by udev and logind, and this app get the permission dynamically when running. We could merge this, but adding user to input group to use this app is always discouraged.

I think it can be undocumented or unrecommended behavior, like "the program can do that, but it's at your own risk", which is the situation of the majority of people who decide to have their user in input.
about the is_user_oninput function, i think is better to have that as function although in the program the only check is only for input (flexibility reasons), but if you want it can be in smtk_keys_emitter_start_async, if you want to leave the function in the code, what name might be appropriate?
btw and talking about security, I think (though I'm not sure) it might be possible to use Polkit via polkit.h to get read permissions for /dev/input on another thread, without stopping the GUI in user space. This could be useful since using system commands can be somewhat insecure. Anyway, this is outside the context of this PR, but just a suggestion. I might experiment with that.

about the is_user_oninput function, i think is better to have that as function although in the program the only check is only for input (flexibility reasons), but if you want it can be in smtk_keys_emitter_start_async, if you want to leave the function in the code, what name might be appropriate?

If you are checking any group, why not just call it is_group?


ng-repeat on a  throws away anything that's not a  or

What is the current behavior?

repeats every td and th but plonks anything else before the first repeater contrary to documentation.
e.g.
{{name}}

would generate:
`

bob
jim
`

What is the expected behavior?
I expect the divs to be copied as well despite it being dissuaded HTML - it's not Angular's job to ignore dissuaded HTML (is it?)

What is the motivation / use case for changing the behavior?
Specifically I'm trying to create an expanding table and using the next tr would ruin colouring and screw with the design.

Which version of Angular, and which browser and OS does this issue affect? Did this work in previous
versions of Angular? Please also test with the latest stable and snapshot versions.

Affects latest stable

This is not done by ngRepeat nor Angular.
It's the browser (enforcing the spec).


Production ready?

Would you the author @gcanti estimate that this framework is production-ready?

Performance?
Breaking types in upcoming typescript versions?
Your ability to maintain this project?
Caveats for usage?

It looks very promising and as I have already implemented query and body parsing using io-ts and other parts of my app using fp-ts this seems like the perfect fit.

hyper-ts is an experimental middleware architecture for HTTP servers written in TypeScript

@gorillatron definitely not production-ready (monthly downloads), not much feedback so far.

It seems I am one of the main users of hyper-ts so far I can tell you

Performance?

Performance was never a concern I have to take in account in the projects I use hyper-ts for so I can say nothing about that aspect. But I would argue that express is the biggest bottleneck and fp-ts (this framework is based on) is benchmarked, so you can take a look into it.

Breaking types in upcoming typescript versions?

Who knows? But these problems have all typescript based frameworks. hyper-ts had already two breaking iterations but the concepts are still the same and projects with strict typings are much easier to upgrade than without. I think the api is about to stabilise cause of the experience made with fp-ts@2.

Your ability to maintain this project?

This project can be overlooked and understand very quickly it just adds the Middleware monad with some utility functions. No fancy stuff to find here which is a good thing! In generell everybody can contribute and @gcanti is an excellent maintainer of his projects since years.

Caveats for usage?

Haven't found anything so far. The framework has a high quality but experience is key cause there isn't that much guidance how you should setup a project with hyper-ts like in express or koa etc. But feel free to ask.

I rewrote a production backend using hyper-ts, and it passes all my unit tests (and honestly it lacks the bugs that I spotted in the current backend), but haven't pulled the trigger on committing it to a testing branch in the central repo. I'll have to decide soon because there's about to be a number of endpoints I need to write, and it'd be nice to write them functionally and with typesafety instead of imperatively.


Move held suarez into forcing subfolder

This PR moves the held suarez forcing into a subfolder

bors r+


How do I import org.jetbrains.skija?

Sorry, I'm having trouble getting started. I was looking at the clojure examples in the skija project and tried adding ... (:import [org.jetbrains.skija BackendRenderTarget ... but I get java.lang.ClassNotFoundException: org.jetbrains.skija.BackendRenderTarget. I added common.fetch_maven("org.jetbrains.skija", "skija-windows", "0.93.4"), to the run.py file.
How do I import skija?
Thanks!

Initially I tried ... (:require [io.github.humbleui.skija-windows :as skj]) ... but that just gives me java.io.FileNotFoundException: Could not locate io/github/humbleui/skija_windows__init.class, io/github/humbleui/skija_windows.clj or io/github/humbleui/skija_windows.cljc on classpath. Please check that namespaces with dashes use underscores in the Clojure file name.
Ditto with ... (:require [io.github.humbleui.skija :as skj]) ....

I am sorry for the confusion! Both Skija and JWM have moved from JetBrains organization to this one, and Maven coordinates changed from JetBrains repo to Maven Central, which I hope is more convenient for the future.
The way it’s setup right now is: Skija after version 0.96.0 lives at io.github.humbleui.skija:skija-<platform> and the package name is io.github.humbleui.skija.
Versions before 0.96.0 continue to live under org.jetbrains.skija:skija-<platform>, but to use them, make sure to specify the JetBrains repo as well (https://packages.jetbrains.team/maven/p/skija/maven). I don’t recommend this because only HumbleUI version will continue to be updated/supported.
I did my best to update all the examples, but I might very well missed something — let me know!
Also let me know if you need further assistance, or have any questions. I hope you’ll get Skija running in no time!

Thanks!
I was looking at snake/main.clj which refers to org.jetbrains.skija but that's probably correct since the build.py for that project also references org.jetbrains.skija.
The deps.edn file didn't give me any hints. It's just referring to the project's build output.


ace: 6.5.4 -> 6.5.5

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/ace/versions.
meta.description for ace is: '"ADAPTIVE Communication Environment"'.

Checks done (click to expand)

built on NixOS
/bin/sh passed the binary check.
1 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 6.5.5 with grep in /nix/store/j4kyzpb94brnbmssrsr62s1xfsawdc18-ace-6.5.5
directory tree listing: https://gist.github.com/ca656a22ec2debcb86571e5289273d37
du listing: https://gist.github.com/84eb6c810d68e725bc94776cd068cdcc

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

6 total rebuild path(s)
2 package rebuild(s)
2 x86_64-linux rebuild(s)
2 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
2 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
ace
yarp

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/j4kyzpb94brnbmssrsr62s1xfsawdc18-ace-6.5.5 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A ace https://github.com/r-ryantm/nixpkgs/archive/07bcdd5ed7e1cfcf60baff60960b6a94a0f4b769.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/j4kyzpb94brnbmssrsr62s1xfsawdc18-ace-6.5.5
ls -la /nix/store/j4kyzpb94brnbmssrsr62s1xfsawdc18-ace-6.5.5/bin

cc @nico202 for testing.

This pull request has been mentioned on Nix community. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/12


piped: init at 0-unstable-2024-11-04

Signed-off-by: lucasew<EMAIL_ADDRESS>
Things done

Add the piped frontend assets

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 354259

x86_64-linux

:white_check_mark: 1 package built:

piped

@ofborg build piped

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 354259

x86_64-linux

:white_check_mark: 1 package built:

piped

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 354259

x86_64-linux

:white_check_mark: 1 package built:

piped


The update check is failing pipeline runs unexpectedly

@imjasonh noticed output like this:
2023/03/31 17:10:58 error during command execution: 9 errors occurred:
	* failed to create a version from package python-3.12: 3.12.0_alpha6: Malformed version: 3.12.0_alpha6
	* failed to create a version from package openssh: 9.3_p1.  Error: Malformed version: 9.3_p1
	* package llvm-lld: update found newer version 16.0.0 compared with package.version in melange config
	* package py3.11-installer: update found newer version 0.7.0 compared with package.version in melange config
	* package libsm: update found newer version 1.2.4 compared with package.version in melange config
	* package clang-15: update found newer version 15.0.7 compared with package.version in melange config
	* package libpaper: update found newer version 2.0.10 compared with package.version in melange config
	* package py3-more-itertools: update found newer version 9.1.1 compared with package.version in melange config
	* package py3.10-installer: update found newer version 0.7.0 compared with package.version in melange config

There might be 2 underlying problems here:

The failed to create a version from package — this appears to be an error from hashicorp/go-version bubbling up when it shouldn't be.
We should have "newer updates available" be a concern during lint checks (except possibly as a warning)

cc: @kaniini @rawlingsj

@kaniini @rawlingsj @imjasonh Does this need our attention urgently? Or should we keep this on the back burner?


Pylance Issue

 Environment data

Language Server version: 2024.9.2
OS and version: darwin x64
Python version (and distribution if applicable, e.g. Anaconda):
python.analysis.indexing: true
python.analysis.typeCheckingMode: off

 Code Snippet

XXX

 Repro Steps

XXX

 Expected behavior
XXX
 Actual behavior
XXX
 Logs

XXX

Thanks for the report. Unfortunately, this is not enough information for us to investigate this issue.
If this continues to be a problem, would you please reopen the issue and add the information described in the troubleshooting guide?


Support extra decks

Now that we have multiple decks:
https://github.com/grifferz/pah-irc/blob/master/decks/cah_2nd_uk.yml
there needs to be a way to pick which one(s) to use.
The bot could simply just use every deck it has available, but the original idea was that there might be, say, the original edition (non-UK) that channels might prefer to use instead.

I think this is going to need some redesign to make possible. To make things simpler and get the multiple decks working as soon as possible, I'll start with assumptions that in the initial version:

There's going to be no user interface. The deck in use will be defined in the config file and apply to all games.
The only way to change deck will be to change the config file and restart the bot.

Some terminology changes will be necessary:

Rename decks/ directory to packs/.
"The deck" is the set of Black and White cards in use; it is comprised of one or more packs.

Currently the deck content is loaded into $self->_deck->{$deckname}->{Black} and $self->_deck->{$deckname}->{White}. The $deckname comes from the name of the file in the decks/ directory.
If there's only going to be one global deck then that layer can be done away with, so there will be just $self->_deck->{Black/White}. I will probably also store the list of packs which comprise that deck, as e.g. $self->_deck->{packs} = "cah_uk cah_2nd_uk".
The games database table currently has a column called deck where the name of the deck file is stored, e.g. cah_uk. That will be renamed to packs and will be the same as what is stored in $self->_deck->{packs}. So the schema update can simply rename deck to packs to begin with since all games currently in existence have cah_uk in that column.
To construct the deck on bot load, it will take the list of packs and simply concatenate each of their Black and White arrays onto each other (in the order specified in the packs setting) to produce one big $self->_deck->{Black} array and one big $self->_deck->{White} array.
A difficulty arises where a game already exists but has a packs value different to the global packs setting. This would indicate that the packs have been changed since the game began, so it must be checked for before the bot is on IRC available for commands or other events. All rows in the bcards and wcards tables for that game can be deleted and then re-populated from the new deck.
The hard part then is what to do about White cards that are still in people's hands, and the current Black card. Taking just the case of the cards in the hands, this is the content of the users_games_hands table, and all we have is a list of indices in to the (old) $self->_deck->{White} array. Not only will these indices now be completely different cards, the old card content may not even be anywhere in the new deck.
One hacky way around it may be to add all the hand cards and the black card onto the end of the deck and adjust the indices to point there. Any duplicate card content can then be removed.
It looks like a proper fix will require a more extensive redesign not based on indices of cards, however I think that will take me a long time to do, which would be a shame.
A later enhancement allowing change of packs from IRC would still be possible even without the redesign, as it would just be the same case of populating the deck again as happens at every reshuffle anyway. My only reason for not tackling that at first is that it will require a whole infrastructure of voting or something, to ensure that eveeryone currently playing wants that change.

Got sick of all the poking around in $self->{_deck} so made PAH::Deck into a proper module that handles all that.


Publish to cargo

We need to publish quickwit to crates.io.
Now that artillery-core has been published the only road block is our tantivy fork.
We can publish it as tantivy-quickwit if necessary, or use a git submodule.
It will however require to publish all of the new subcrate (fastfield_codec) for instance.
It probably would be nicer to prefix all of the tantivy specific crate with "tantivy-".
@PSeitz what do you think?

Is there something else blocking the usage of the original tantivy except the blocked term-dicitonary?
Ideally if the fork is just temporary we would bundle tantivy-quickwit into quickwit without publishing anything to crates.io, but I don't think that's supported?

It will however require to publish all of the new subcrate (fastfield_codec) for instance.
It probably would be nicer to prefix all of the tantivy specific crate with "tantivy-".

Yes a prefix would be good.
They would also have their own release cycle in quickwit, which isn't great.
Do we need to publish to crates.io currently, additionally to the installer script?

As far as I know it is not supported if it is a separate crate.

Do we need to publish to crates.io currently, additionally to the installer script?

It's always nice for rustacean to use cargo install

It's always nice for rustacean to use cargo install quickwit

That's true, but in that case I would prefer to delay until we use original tantivy, since it's a more efficient use of our time and the installer should work fine.

I agree with @PSeitz but I don't really know the amount of work to be able to use the original tantivy. @PSeitz do you have an idea on that?

The blocked term dictionary would mean to move the sstable to tantivy and have a layer to address both implementations. fuzzy queries requiring a full scan should probably be disabled. Not sure if merging is implemented for the current sstable.
Not sure if there are more differences.

You can look at the diff here: https://github.com/tantivy-search/tantivy/pull/1115/files
The async part should be easy to backport so the main work concerns the sstable.
For fuzzy queries, we are currently using tantivy grammar which does not include this type of query, the only type of query which we needed to disable was RangeQuery.


If condition against an integer fails

Hi,
Considering the code below, I don't see why _test_tuple works fine in both  'if' cases whereas _test_int fails in one of the two cases :
from numba import njit, prange
import numpy as np

def _test_int(_input, additional_dimension: int):
    for x in prange(_input.shape[0]):
        if additional_dimension > 0:

            for dim_idx in prange(0, additional_dimension):

                local_slice = _input[x, dim_idx]
                # Do some specific treatement here
        else:
            local_slice = _input[x]
            # Do some other treatement here

def _test_tuple(_input, additional_dimension: tuple):
    """Same function as above but addtional_dimension is a tuple"""
    for x in prange(_input.shape[0]):
        if len(additional_dimension) > 0:

            for dim_idx in prange(0, additional_dimension[0]):

                local_slice = _input[x, dim_idx]
                # Do some specific treatement here
        else:
            local_slice = _input[x]
            # Do some other treatement here

np.random.seed(2021)
data_simple = np.random.random((10,))
data_complete = np.random.random((10, 2))

# Compilation :
_test_int_jitted = njit(_test_int)
_test_tuple_jitted = njit(_test_tuple)

# Executions :
# OK
_test_tuple_jitted(data_complete, (2,))
# OK
_test_tuple_jitted(data_complete, (0,))
# OK
_test_int_jitted(data_complete, 2)
# KO : why the if branching does fail here?
_test_int_jitted(data_simple, 0)

The latest line fails with the following error (meaning we took the wrong branch in the if since addtional_dimension equals zero :
numba.core.errors.TypingError: Failed in nopython mode pipeline (step: nopython frontend)
No implementation of function Function(<built-in function getitem>) found for signature:

 >>> getitem(array(float64, 1d, C), UniTuple(int64 x 2))

There are 22 candidate implementations:
  - Of which 20 did not match due to:
  Overload of function 'getitem': File: <numerous>: Line N/A.
    With argument(s): '(array(float64, 1d, C), UniTuple(int64 x 2))':
   No match.
  - Of which 2 did not match due to:
  Overload in function 'GetItemBuffer.generic': File: numba/core/typing/arraydecl.py: Line 162.
    With argument(s): '(array(float64, 1d, C), UniTuple(int64 x 2))':
   Rejected as the implementation raised a specific error:
     TypeError: cannot index array(float64, 1d, C) with 2 indices: UniTuple(int64 x 2)
  raised from /home/claire/.virtualenvs/sunmet/lib/python3.8/site-packages/numba/core/typing/arraydecl.py:84

During: typing of intrinsic-call at numba_test.py (11)

File "numba_test.py", line 11:
def _test_int(_input, additional_dimension: int):
    <source elided>

                local_slice = _input[x, dim_idx]

The fact that the code works fine with a tuple and fails with an int feels incoherent to me, does any one have any tips or hints on this behaviour?
(Python==3.8.5, numba==0.52.0, numpy==1.19.4)
Thanks.

@mathisc thank you for asking about this on the Numba issue tracker. The problem here is that Numba isn't interpreted. So the error you are seeing is not actually during execution or runtime (i.e. the if branch isn't even being executed yet). Numba will try to do type inference based on the type of input_, it will see that this is a 1D array, then it will look for uses of _input and see that you are trying to index into a 1D array with a tuple. This doesn't make any sense and so Numba yields the error message above. My suggestion would be to make two Numba njit compiled functions, one for 1D arrays and one for 2D arrays. Then check the  dimensionality of your array and then decide on which Numba function to call.
Hope this makes sense and helps?

I should add that _test_tuple_jitted(data_simple, (0,)) will also fail. So, both test_* functions will fail if presented with a 1D array as input.

Arg, this is an error of me trying to reproduce my issue (I indeed wanted to run _test_tuple_jitted(data_simple, (0,)) but I mistakingly run _test_tuple_jitted(data_complete, (0,))). Also in the actual code I wasn't using (0,) but a true empty tuple. Sorry about that, please find another snippet below that works with with tuples but not an int :
from numba import njit, prange
import numpy as np

@njit()
def _test_int(_input, additional_dimension: int):
    for x in prange(_input.shape[0]):
        if additional_dimension > 0:

            for dim_idx in prange(0, additional_dimension):

                local_slice = _input[x, dim_idx]
                # Do some specific treatement here
        else:
            local_slice = _input[x]
            # Do some other treatement here

@njit()
def _test_tuple(_input, additional_dimension: tuple):
    """Same function as above but addtional_dimension is a tuple"""
    for x in prange(_input.shape[0]):
        for y in prange(_input.shape[1]):
            for z in prange(_input.shape[2]):

                if len(additional_dimension) != 0:
                    for dim_idx in prange(0, additional_dimension[0]):

                        local_slice = _input[x,y,z,dim_idx]
                        # Do some specific treatement here
                else:
                    local_slice = _input[x,y,z]
                    # Do some other treatement here

np.random.seed(2021)
data_simple = np.random.random((10,9,8))
data_complete = np.random.random((10,9,8,2))

# Executions :
# OK
_test_tuple(data_complete, (2,))
# OK
_test_tuple(data_simple, tuple())
# OK
_test_int(data_complete, 2)
# KO : why the if branching does fail here?
_test_int(data_simple, 0)

Indeed, this is an error of me trying to make a snippet reproduce the behaviour I am seeing : I indeed wanted to run _test_tuple_jitted(data_simple, (0,)) but I mistakingly run _test_tuple_jitted(data_complete, (0,))). What's more in the actual code I wasn't using (0,) but a true empty tuple.
Sorry about that, please find another snippet below that actually reproduces the behaviour I am talking about :
from numba import njit, prange
import numpy as np

@njit()
def _test_int(_input, additional_dimension: int):
    for x in prange(_input.shape[0]):
        if additional_dimension > 0:

            for dim_idx in prange(0, additional_dimension):

                local_slice = _input[x,dim_idx]
                # Do some specific treatement here
        else:
            local_slice = _input[x]
            # Do some other treatement here

@njit()
def _test_tuple(_input, additional_dimension: tuple):
    """Same function as above but addtional_dimension is a tuple"""
    for x in prange(_input.shape[0]):
        if len(additional_dimension) != 0:
            for dim_idx in prange(0, additional_dimension[0]):

                local_slice = _input[x,dim_idx]
                # Do some specific treatement here
        else:
            local_slice = _input[x]
            # Do some other treatement here

np.random.seed(2021)
data_simple = np.random.random((10))
data_complete = np.random.random((10,2))

# Executions :
# OK
_test_tuple(data_complete, (2,))
_test_tuple(data_simple, tuple())

# KO
#_test_int(data_complete, 2)
#_test_int(data_simple, 0)

@mathisc thank you for updating your question. Just to make sure we are aligned:
_test_int(data_complete, 2) <--- this works
_test_int(data_simple, 0) <--- this doesn't

@mathisc I am not sure exactly why this example works for tuple. I think it is because the length of the tuple is not known at typing time, whereas the value of an integer may be literal and may be known at typing time. So with an int as parameter Numba can reject the function outright, but with a tuple it needs to partly execute before it can determine which branch to take.
@stuartarchibald do you concur?

On my side, neither of the _test_int methods work, but both of the _test_tuple calls are working fine on my side.
This feels weird as they basically do the same kind of branching.
Given your explanations above, what actually puzzles me really is that :
_test_tuple(data_simple, tuple())  works like a charm.

@esc yes, it's essentially that Numba "sees" the type of the tuple as "tuple with X things in it", and so at compile time len(<some tuple>) can be resolved to a constant X, the branch pruning algs then kick in and remove unreachable code based on constants they can work out. In the case of an integer input, Numba just sees the type as "it's some integer" and so cannot specialise further (without doing something complicated to tell it to do this). This is to prevent creating a new version of the function being compiled for every value of integer provided.

@esc @stuartarchibald thanks a lot of the clarification.
Would you consider this to be a "valid and sustainable trick" or would you recommend to split the code into 2 functions depending on the branching ?

@esc @stuartarchibald thanks a lot of the clarification.
Would you consider this to be a "valid and sustainable trick" or would you recommend to split the code into 2 functions depending on the branching ?

No problem. Numba uses it internally, and there's compiler passes on the default compilation pipelines to ensure this behaviour works. It was originally designed in part to deal with the common pattern:
def foo(n, x=None):
  if x is None:
    x = np.empty(n)
  #... do work with `x`

Thanks a lot guy ;)

Thanks a lot guys!

@mathisc no problem, thank you for using Numba.


Question: RPC multi-request support?

The jsonrpc standard supports sending an array of request objects (and receiving an array of response objects), hence the id field to differentiate. Does neon-js already support this feature?
It would be very beneficial for reducing the number of RPC endpoint hits while retrieving balances for multiple tokens for a single address (think neon-wallet as use-case). For NEO2 I believe neon-js uses NEOSCAN as API provider for retrieving the balances, for NEO3 (assuming all NEP5 tokens) we would have to send a rpc.invokeFunction call for each token.

Its not currently supported but yes, we should support it.

@snowypowers #812 solves this, right?

Yes it should.


networking.cc: shorten ssid  to at most 18 characters wide

How did you choose 18? Isn't there space for more?

maybe we should do truncate in AbstractControl later

How did you choose 18? Isn't there space for more?
can adjust to 22

Maybe we should make a nice helper function to fit some text in a max width within a range of font sizes?

maybe a helper function like this.but it's hard to use.will increase a lot of code
inline QString elideString(QWidget *w, const QString &str, int width = 0, Qt::TextElideMode mode = Qt::ElideRight) {
  QFontMetrics fm(w->font());
  return fm.elidedText(str, mode, width <= 0 ? w->width() : width);
}

override resizeEvent and paintEvent, so that it can be displayed correctly in all situation


[Ask] About Sequential Parallel

Hi! Thanks for sharing great work!
I have 3 questions.

If I enable sequential parallelism option, then model-sharding (along patch dimension) is applied across GPUs ?
There are 2 operation for sequential parallel.

split_forward_gather_backward before forward pass to DiT block
gather_forward_split_backward right before final layer
What is difference between those two?

Multi-node training is supported ??

Thanks!

Yes
The first one is to shard the input along the sequence dimension before feeding it into the transformer blocks, the second one is to gather the sharded tensors along the sequence dimension to recover its original shape so that the model will output a full tensor.
Yes, you can use torchrun or colossalai run to launch multi-node training.

Thanks!


bug in adding loads to nodes, wrong index

to be fixed

code was double-checked, no copy past error was made


Some apStar paths that don't follow the data model path format

Examples include:

Anything observed with the 1m telescope.

From the Tree the expected path should be:
$APOGEE_REDUX/{apred}/stars/{telescope}/{field}/{prefix}Star-{apred}-{obj}.fits
Which works for anything observed with the APO 2.5m telescope. But for the 1m the field is always "1", but the true folders are things like "calibration", "hip", etc (see here, which is actually the LOCATION_ID in the "allStar...fits"

All "Bestars" observed with the 1-m telescope, but for another reason.

An example path is:
https://dr15.sdss.org/sas/dr15/apogee/spectro/redux/r8/stars/apo1m/Bestars/
https://dr15.sdss.org/sas/dr15/apogee/spectro/redux/r8/stars/apo1m/Bestars/
apStar-r8-2MASS-J00431825+6154402-57280.fits
Which would imply from $APOGEE_REDUX/{apred}/stars/{telescope}/{field}/{prefix}Star-{apred}-{obj}.fits that the {obj} should be "2MASS-J00431825+6154402-57280", but in the "allStar....fits" file the APSTAR_ID, TARGET_ID, ASPCAP_ID, and APOGEE_ID do not mention the "2MASS" prefix. However, FILE does.

The other problem (which links to sdss/tree, sdss/sdss_access, and other things) is that the template keywords in the Tree do not match those in the "allStar....fits" file.

For example, {telescope} (in template) -> {TELESCOPE} (in "allStar....fits"), {field} -> {FIELD}, {apred} -> (nothing! only extractable from other things), and the worst one: {obj} -> {APOGEE_ID}?

/cc @holtzmanjon for when you are not swamped down with DR16


refine API base on spec

issue#77 - implement metadata update and delete APIs
issue#109 - fix metadata API to support mixed case queries
implement schema update and delete APIs
implement entity update API
unify API return as json format

close this PR due to it needs UI code change too, will submit new PR later


Fix - video player width responsiveness

Fixes #58
Added full width to the flexbox containing video player and other div(s).

Before

After

Fixed this in #64

already fixed


Finding Subaccount by Friendly Name

In the Twilio docs, one can fetch a subaccount sid by calling Read on the friendly name.  Can this be done in ExTwilio?  I can pull a subaccount by sid, but I would prefer not to have to store the sid in my database and instead call via the friendly name, which I can associate with an existing value.

You might be able to pass the friendly name as the account: option instead of a SID. Have you tried that?

I haven't, but I will give it a try and update here

Sadly, it doesn't work.  Message has no :account in its struct definition.  Would it be passed to Twilio?

This works using all/1 function in Account resource
ExTwilio.Account.all friendly_name: "some name"


Update local-storage.js

** Type: bug **
** Description: **
Delete versions and history in package.json, to fix issue #1359.
https://github.com/verdaccio/verdaccio/issues/1359

Is this relevant?

I think it should be an option in verdaccio

If so please make it configurable. Or does it fix another issue which is not about the initial comment in the linked issue?

Can you add some unit tests which fail without your changes and succeed with your changes?

Is this relevant?

I think it should be an option in verdaccio

If so please make it configurable. Or does it fix another issue which is not about the initial comment in the linked issue?

I think it's part of the design.maybe we can discuss:

when to complete the configuration
which is the default way

@AllenBird, thanks for the PR, looks promising, this fix requires a unit test or update the current ones, you can find more info about it here https://github.com/verdaccio/verdaccio/blob/master/test/README.md or ask here for any mentoring, I'll be happy to help.

I find that this solution introduces problems.
When developer delete the latest version, All version cannot be displayed normally.
I will found another solution.


.load() doesn't seem to support lists

DataFrame reader supports a list for load:
https://spark.apache.org/docs/latest/api/python/pyspark.sql.html?highlight=load#pyspark.sql.DataFrameReader.load
But when I try the same on spark 2.3.0 (on Databricks) with spark-xml 2.11-0.4.1:
sqlContext.read.format('xml').load([file1, file2])
i get the error:
'path' must be specified for XML data

It should be an issue in Spark ...

Did you have more information about this issue ?


RFC + code: better default 'type' for responses

Talked about this a little in https://github.com/arc-repos/architect/issues/220 but wanted to raise it as a separate idea because I think it should be in architect itself:
Some observations

Typing text/html; charset=UTF-8 (and the various other content types) is repetitive, makes code less interesting to read, and more prone to failure.

It's very easy for us to distinguish from HTML, text and JSON and set the content type accordingly if it's omitted

RFC
Routes should be able to return arc responses just like they do now.
But also:
return {
  status: 403,
  body: `

hello world

  `
}

should return a 403 Forbidden response with type: text/html; charset=UTF-8 - because the body is a String and the first non-whitespace character is a <
But also:
return {
  status: 200,
  body: 'hello world'
}

should return a 200 OK response with type: text/plain; charset=UTF-8 - because the body is a String and the first non-whitespace character is not a '<'
return {
  status: 201,
  body: {
    dinosaurID: 26
  }
}

should return a 201 created response with type: application/json and the body being the JSON encoded object - because the body is an Object.
In other words
Routes should be able to return strings, and the content type assigned be either JSON for objects, and for Strings, HTML or test based on the first non-whitespace character

This is pretty dope, there's two ways, either in JavaScript or with Velocity Templates in API Gateway. The former is a lot easier. The latter would be difficult, but possible! Not sure how this would impact other runtime languages either. We could prototype in arc.middleware tho I like the idea of leaving middleware agnostic of req/res schemas. Maybe we can make it smart enough to 'know' if its middleware for HTTP, SNS or SQS…

Thanks! Looking at doing this in JavaScript. I could throw it in arc.middleware, but it would be better to be seamless, eg. just make type optional in the returned response. I'm having trouble finding the right point in @architect/architect to inject this though - I want to put it somewhere that's agnostic of the sandbox / aws / future cloud providers. Where would be the best function/method to add this?

This is going to go in one of two places (correct me if I'm wrong, @brianleroux!):

API Gateway / dep-free: gonna require some magic in the response VTL template, more here
JS via dependency: @architect/functions -likely here

Thanks Ryan. The VTL is specific to AWS and doesn't affect the sandbox right? I was hoping for some shared code between AWS and the sandbox - maybe in/before the validation of responses. I've been trying to break AWS with bad responses to see where it errors but AWS just seems tolerant of bad (missing keys, wrong types etc) responses.

Yeah, forgot to add the sandbox impl point, which should be here.
And yes, we aren't attempting to mock AWS-flavored VTL in sandbox (for better or worse, I'd argue vastly for the better), so they wouldn't share code.

Ah so AWS and sandbox are implemented seperately, and there's no shared
validation code for responses.
Hrm. Learning VTL sounds like a time suck and adding it to functions
defeats the purpose of making responses simpler (since you now have to run
a function rather than just return an object).
Maybe (since people might mess up responses on AWS) spme shared (basic)
response validation code should exist?
On Wed, 2 Jan 2019 at 10:16 pm, Ryan Block<EMAIL_ADDRESS>wrote:

Yeah, forgot to add the sandbox impl point, which should be here
https://github.com/arc-repos/architect/blob/107a7608b10cd209bb90c10a49d839841a3d20c3/src/sandbox/http/register-route.js#L40
.
And yes, we aren't attempting to mock AWS-flavored VTL in sandbox (for
better or worse, I'd argue vastly for the better), so they wouldn't share
code.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/arc-repos/architect/issues/244#issuecomment-451002482,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAKiMinEiba8xWRSoctU83ORFFrvKcOQks5u_S_EgaJpZM4ZcPEu
.

Example ways to mess up a response: return a non existant status code,
return an array for an HTTP header value, set location for a redirect to be
undefined, etc.
I don't know enough about VTL and what it does. I just imagine there would
need to be some validation in JS to ensure arc user's  errors are caught
and users get good error messages back.
On Wed, 2 Jan 2019 at 10:27 pm, Ryan Block<EMAIL_ADDRESS>wrote:

Hm, unclear to me how people might mess up responses on AWS, can you
elaborate further? It kind of sounds like you're proposing we mock API
Gateway's VTL impl, but I'm not sure.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/arc-repos/architect/issues/244#issuecomment-451004800,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAKiMhm3F5EWPIqGxZ93n2sxox2pEEX_ks5u_TI2gaJpZM4ZcPEu
.

Jumped on a laptop (it's nearly midnight here) to check out the vtl in more detail.
OK responses can be manipulated in VTL on AWS, and for in JS around the implementation point @ryanblock  mentioned for sandbox. Leave this with me and I'll check it out further.

Hey, I was in our VTL stuff working working on something else and was able to get content type detection working. Are we still interested? If so, what are the rules?
As a reminder: not specifying content type currently defaults to application/json (and does not specify charset=utf-8).
Some ideas in pseudocode:

if (!type && startsWith('<')) type = 'text/html; charset=utf-8;'
if (!type) type = 'application/json; charset=utf-8;'

Not sure if it would be reliable or desirable to do any other content types.
sandbox mocking of the above should be trivial though.


Rambo dpex

Enabled Rambo numba dpex implementation.
In this version ,due to numpy.random.rand() is not replaceable by dpnp, gen_rand_data function is done on CPU only. Should consider to offload in the future.

Passed the test locally:
***** Testing Numba with rambo on the S dataset *****
NumPy - default - validation: 34865ms
Numba - nopython-mode - first/validation: 658ms
Numba - nopython-mode - validation: SUCCESS
Numba - nopython-mode - median: 314ms
Numba - nopython-mode-parallel-range - first/validation: 641ms
Numba - nopython-mode-parallel-range - validation: SUCCESS
Numba - nopython-mode-parallel-range - median: 157ms
***** Testing numba_dpex with rambo on the S dataset *****
NumPy - default - validation: 34542ms
Unable to join threads to shut down before fork(). This can break multithreading in child processes.
numba_dpex - kernel-mode - first/validation: 7294ms
numba_dpex - kernel-mode - validation: SUCCESS
numba_dpex - kernel-mode - median: 7031ms
Unable to join threads to shut down before fork(). This can break multithreading in child processes.
numba_dpex - numpy-mode - first/validation: 7535ms
numba_dpex - numpy-mode - validation: SUCCESS
numba_dpex - numpy-mode - median: 6995ms
Unable to join threads to shut down before fork(). This can break multithreading in child processes.
numba_dpex - prange-mode - first/validation: 7438ms
numba_dpex - prange-mode - validation: SUCCESS
numba_dpex - prange-mode - median: 6989ms

We can add a njit decorator on gen_rand_data, so it will at least be jit-compiled. See numba versions.

After discussion, it seems it is better to replace numpy function with dpnp implementation which will be taken care of in a separate issue. The gen_rand_data function will stay on CPU only for now.

@mingjie-intel @adarshyoga Based on how we are now implementing all of the benchmarks, the initialization should be moved to a separate rambo_initialize.py module and the framework copy_to_func will copy NumPy into usmndarray. We do not need the random number generation to be done in dpex.
If you agree, can you revive the PR and get it merged into main?

numba_dpex_k implementation is failing in this test, with error message:
TypeError: Datatypes of array passed to @numba_dpex.kernel has to be the same. Passed datatypes: (array(float64, 2d, C), array(float64, 2d, C), array(float64, 2d, C), int64, USM:ndarray(float64, 3d, C))
dbscan numb_dpex_k is having the same issue. Dipto is looking at it, since it was possible introduced by framework changes.


All certificate renewals suddenly fail. Has worked for months if not years.

After using this container for months, if not years, with minimal interaction necessary, suddenly certificates are no longer automatically updated.   Nothing changed in my environment so I'm a bit at a loss what happened.
From the log:
nginx-proxy-manager-app-1  | [9/15/2022] [4:50:19 PM] [Global   ] › ℹ  info      Generating MySQL knex configuration from environment variables
nginx-proxy-manager-app-1  | [9/15/2022] [4:50:19 PM] [Global   ] › ⬤  debug     Wrote db configuration to config file: ./config/production.json
nginx-proxy-manager-app-1  | [9/15/2022] [4:50:20 PM] [Migrate  ] › ℹ  info      Current database version:<PHONE_NUMBER>5214
nginx-proxy-manager-app-1  | [9/15/2022] [4:50:20 PM] [Setup    ] › ℹ  info      Creating a new JWT key pair...
nginx-proxy-manager-app-1  | [9/15/2022] [4:50:24 PM] [Setup    ] › ℹ  info      Wrote JWT key pair to config file: /app/config/production.json
nginx-proxy-manager-app-1  | [9/15/2022] [4:50:24 PM] [Setup    ] › ℹ  info      Logrotate Timer initialized
nginx-proxy-manager-app-1  | [9/15/2022] [4:50:24 PM] [Setup    ] › ℹ  info      Logrotate completed.
nginx-proxy-manager-app-1  | [9/15/2022] [4:50:24 PM] [IP Ranges] › ℹ  info      Fetching IP Ranges from online services...
nginx-proxy-manager-app-1  | [9/15/2022] [4:50:24 PM] [IP Ranges] › ℹ  info      Fetching https://ip-ranges.amazonaws.com/ip-ranges.json
nginx-proxy-manager-app-1  | [9/15/2022] [4:50:24 PM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v4
nginx-proxy-manager-app-1  | [9/15/2022] [4:50:24 PM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v6
nginx-proxy-manager-app-1  | [9/15/2022] [4:50:24 PM] [SSL      ] › ℹ  info      Let's Encrypt Renewal Timer initialized
nginx-proxy-manager-app-1  | [9/15/2022] [4:50:24 PM] [SSL      ] › ℹ  info      Renewing SSL certs close to expiry...
nginx-proxy-manager-app-1  | [9/15/2022] [4:50:24 PM] [IP Ranges] › ℹ  info      IP Ranges Renewal Timer initialized
nginx-proxy-manager-app-1  | [9/15/2022] [4:50:24 PM] [Global   ] › ℹ  info      Backend PID 246 listening on port 3000 ...
nginx-proxy-manager-app-1  | [9/15/2022] [4:50:49 PM] [Express  ] › ⚠  warning   invalid signature
nginx-proxy-manager-app-1  | [9/15/2022] [4:52:43 PM] [SSL      ] › ✖  error     Error: Command failed: certbot renew --non-interactive --quiet --config "/etc/letsencrypt.ini" --preferred-challenges "dns,http" --disable-hook-validation
nginx-proxy-manager-app-1  | Failed to renew certificate npm-1 with error: Some challenges have failed.
nginx-proxy-manager-app-1  | Failed to renew certificate npm-10 with error: Some challenges have failed.
nginx-proxy-manager-app-1  | Failed to renew certificate npm-11 with error: Some challenges have failed.
nginx-proxy-manager-app-1  | Failed to renew certificate npm-12 with error: Some challenges have failed.
nginx-proxy-manager-app-1  | Failed to renew certificate npm-13 with error: Some challenges have failed.
nginx-proxy-manager-app-1  | Failed to renew certificate npm-2 with error: Some challenges have failed.
nginx-proxy-manager-app-1  | Failed to renew certificate npm-25 with error: Some challenges have failed.
nginx-proxy-manager-app-1  | Failed to renew certificate npm-3 with error: Some challenges have failed.
nginx-proxy-manager-app-1  | Failed to renew certificate npm-31 with error: Some challenges have failed.
nginx-proxy-manager-app-1  | Failed to renew certificate npm-32 with error: Some challenges have failed.
nginx-proxy-manager-app-1  | Failed to renew certificate npm-34 with error: Some challenges have failed.
nginx-proxy-manager-app-1  | Failed to renew certificate npm-35 with error: Some challenges have failed.
nginx-proxy-manager-app-1  | Failed to renew certificate npm-36 with error: Some challenges have failed.
nginx-proxy-manager-app-1  | Failed to renew certificate npm-38 with error: Some challenges have failed.
nginx-proxy-manager-app-1  | Failed to renew certificate npm-39 with error: Some challenges have failed.
nginx-proxy-manager-app-1  | Failed to renew certificate npm-4 with error: Some challenges have failed.
nginx-proxy-manager-app-1  | Failed to renew certificate npm-40 with error: Some challenges have failed.
nginx-proxy-manager-app-1  | Failed to renew certificate npm-41 with error: Some challenges have failed.
nginx-proxy-manager-app-1  | Failed to renew certificate npm-42 with error: Some challenges have failed.
nginx-proxy-manager-app-1  | Failed to renew certificate npm-5 with error: Some challenges have failed.
nginx-proxy-manager-app-1  | Failed to renew certificate npm-6 with error: Some challenges have failed.
nginx-proxy-manager-app-1  | Failed to renew certificate npm-7 with error: Some challenges have failed.
nginx-proxy-manager-app-1  | Failed to renew certificate npm-8 with error: urn:ietf:params:acme:error:rateLimited :: There were too many requests of a given type :: Error creating new order :: too many failed authorizations recently: see https://letsencrypt.org/docs/failed-validation-limit/
nginx-proxy-manager-app-1  | Failed to renew certificate npm-9 with error: Some challenges have failed.
nginx-proxy-manager-app-1  | All renewals failed. The following certificates could not be renewed:
nginx-proxy-manager-app-1  |   /etc/letsencrypt/live/npm-1/fullchain.pem (failure)
nginx-proxy-manager-app-1  |   /etc/letsencrypt/live/npm-10/fullchain.pem (failure)
nginx-proxy-manager-app-1  |   /etc/letsencrypt/live/npm-11/fullchain.pem (failure)
nginx-proxy-manager-app-1  |   /etc/letsencrypt/live/npm-12/fullchain.pem (failure)
nginx-proxy-manager-app-1  |   /etc/letsencrypt/live/npm-13/fullchain.pem (failure)
nginx-proxy-manager-app-1  |   /etc/letsencrypt/live/npm-2/fullchain.pem (failure)
nginx-proxy-manager-app-1  |   /etc/letsencrypt/live/npm-25/fullchain.pem (failure)
nginx-proxy-manager-app-1  |   /etc/letsencrypt/live/npm-3/fullchain.pem (failure)
nginx-proxy-manager-app-1  |   /etc/letsencrypt/live/npm-31/fullchain.pem (failure)
nginx-proxy-manager-app-1  |   /etc/letsencrypt/live/npm-32/fullchain.pem (failure)
nginx-proxy-manager-app-1  |   /etc/letsencrypt/live/npm-34/fullchain.pem (failure)
nginx-proxy-manager-app-1  |   /etc/letsencrypt/live/npm-35/fullchain.pem (failure)
nginx-proxy-manager-app-1  |   /etc/letsencrypt/live/npm-36/fullchain.pem (failure)
nginx-proxy-manager-app-1  |   /etc/letsencrypt/live/npm-38/fullchain.pem (failure)
nginx-proxy-manager-app-1  |   /etc/letsencrypt/live/npm-39/fullchain.pem (failure)
nginx-proxy-manager-app-1  |   /etc/letsencrypt/live/npm-4/fullchain.pem (failure)
nginx-proxy-manager-app-1  |   /etc/letsencrypt/live/npm-40/fullchain.pem (failure)
nginx-proxy-manager-app-1  |   /etc/letsencrypt/live/npm-41/fullchain.pem (failure)
nginx-proxy-manager-app-1  |   /etc/letsencrypt/live/npm-42/fullchain.pem (failure)
nginx-proxy-manager-app-1  |   /etc/letsencrypt/live/npm-5/fullchain.pem (failure)
nginx-proxy-manager-app-1  |   /etc/letsencrypt/live/npm-6/fullchain.pem (failure)
nginx-proxy-manager-app-1  |   /etc/letsencrypt/live/npm-7/fullchain.pem (failure)
nginx-proxy-manager-app-1  |   /etc/letsencrypt/live/npm-8/fullchain.pem (failure)
nginx-proxy-manager-app-1  |   /etc/letsencrypt/live/npm-9/fullchain.pem (failure)
nginx-proxy-manager-app-1  | 24 renew failure(s), 0 parse failure(s)
nginx-proxy-manager-app-1  |
nginx-proxy-manager-app-1  |     at ChildProcess.exithandler (node:child_process:399:12)
nginx-proxy-manager-app-1  |     at ChildProcess.emit (node:events:526:28)
nginx-proxy-manager-app-1  |     at maybeClose (node:internal/child_process:1092:16)
nginx-proxy-manager-app-1  |     at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5)
nginx-proxy-manager-app-1  | `QueryBuilder#allowEager` method is deprecated. You should use `allowGraph` instead. `allowEager` method will be removed in 3.0
nginx-proxy-manager-app-1  | `QueryBuilder#eager` method is deprecated. You should use the `withGraphFetched` method instead. `eager` method will be removed in 3.0
nginx-proxy-manager-app-1  | QueryBuilder#omit is deprecated. This method will be removed in version 3.0
nginx-proxy-manager-app-1  | Model#$omit is deprected and will be removed in 3.0.
nginx-proxy-manager-app-1  | Duplicate relation "access_list" in a relation expression. You should use "a.[b, c]" instead of "[a.b, a.c]". This will cause an error in objection 2.0
nginx-proxy-manager-app-1  | [9/15/2022] [4:55:08 PM] [Nginx    ] › ℹ  info      Reloading Nginx
nginx-proxy-manager-app-1  | [9/15/2022] [4:55:30 PM] [Nginx    ] › ℹ  info      Reloading Nginx
nginx-proxy-manager-app-1  | [9/15/2022] [4:55:53 PM] [Nginx    ] › ℹ  info      Reloading Nginx
nginx-proxy-manager-app-1  | [9/15/2022] [4:55:58 PM] [SSL      ] › ℹ  info      Requesting Let'sEncrypt certificates for Cert #46: myapp.mydomain.com
nginx-proxy-manager-app-1  | [9/15/2022] [4:55:58 PM] [SSL      ] › ℹ  info      Command: certbot certonly --config "/etc/letsencrypt.ini" --cert-name "npm-46" --agree-tos --authenticator webroot --email<EMAIL_ADDRESS>--preferred-challenges "dns,http" --domains "myapp.mydomain.com"
nginx-proxy-manager-app-1  | [9/15/2022] [4:56:05 PM] [Nginx    ] › ℹ  info      Reloading Nginx
nginx-proxy-manager-app-1  | [9/15/2022] [4:56:05 PM] [Express  ] › ⚠  warning   Command failed: certbot certonly --config "/etc/letsencrypt.ini" --cert-name "npm-46" --agree-tos --authenticator webroot --email<EMAIL_ADDRESS>--preferred-challenges "dns,http" --domains "myapp.mydomain.com"
nginx-proxy-manager-app-1  | Saving debug log to /var/log/letsencrypt/letsencrypt.log
nginx-proxy-manager-app-1  | Some challenges have failed.
nginx-proxy-manager-app-1  | Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.

@Waldorf3 There is a problem with renewing if force SSL is turned on, if that is true for you, turn off force SSL, renew then turn back on.
Its awaiting a fix to be merged #2038

We have the same symptoms. The certificates not renewed by automatically. When I try to renew manually on the GUI, it provide an "internal error" message (without any error code, or details). Sadly this solution is not reliable :/

We have the same symptoms. The certificates not renewed by automatically. When I try to renew manually on the GUI, it provide an "internal error" message (without any error code, or details). Sadly this solution is not reliable :/
Edit:

Turning off the "force SSL" option not worked for me.
This solution, (from 2022 March 24) worked for me: Renew now on SSL Certificates page gives internal error #1816 (comment)

Looks like this problem is very old :/ and still exist.

I already tried the "uncheck force ssl and reissue cert", it just throws an "internal error".
I'm running NPM in docker, not sure how to start fiddling with a script to fix this. Would be better if the author would acknowledge the bug and offer a proper solution.

I'm just realizing I might be barking up the wrong tree. Is jc21 the actual developer/maintainer of this code, or just the docker-packager?  If not, who is responsible for the code, who can fix this bug?
I actually find the NPM SSL subsystem to be quite fragile. If for example you try to enable SSL for a site that does not have a root directory, such as for example ubooquity (requires http://ubooquity/ubooquity) it will also fail with a nondescript "internal error", and only way to fix is manually cleaning up the database.  That's a viable solution for a single failed certificate, not for a system with 30 or more proxy hosts with failed certs.

JC21 is the developer and the only fragility at the moment that I see is the renew issue outstanding a merge.
I simply don't see how NPM fronting for ubooquity results in an internal error that requires DB cleanup. The application isn't even hit for letsencrypt SSL certs to be created via the HTTP auth method.
Also picking a pretty broken by modern standards application like ubooquity to measure success is odd. It has, as you say, no root directory so requires special measures and also a different port for admin so requires special measures again, no tool calling itself easy to use can be expected to handle both those broken by modern standards decisions.
Often internal errors are after people remove active SSL certs breaking Nginx config i.e. ignoring the warning. What specific errors are you still getting?

Just to confirm that PR #2038 by @the1ts seems to be doing the trick for me.

👍


Report issue decoding multisend (ERC20 short address attack)

Describe the bug
When decoding multisend transaction 0x008ea708617148d871ac77eccb8caa785f53efbc47000000000000000000000000000000000000000000000000016345785d8a00000000000000000000000000000000000000000000000000000000000000000044e9bb84c2000000000000000000000000b00b585bbc642612dbedc0f7c31e9962fde55c71000000000000000000000000000000000000000000000000016345785d8a0000000d8775f648430679a709e98d2b0cb6250d2887ef00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000043a9059cbb0000000000000000000000002c4db8a83f7ae70c00548c53ac55579b9a8744e50000000000000000000000000000000000000000000002c182040d8f7d0000 we get 0xe9bb84c2000000000000000000000000b00b585bbc642612dbedc0f7c31e9962fde55c71000000000000000000000000000000000000000000000000016345785d8a0000 and 0xa9059cbb0000000000000000000000002c4db8a83f7ae70c00548c53ac55579b9a8744e50000000000000000000000000000000000000000000002c182040d8f7d0000
This last transaction seems to be a transfer but it's missing one byte for the value field. Decoding of multisend seems to be alright as traces show that data without the byte: https://etherscan.io/vmtrace?txhash=0x66674c095e636a7e581cfcc968f0c499fedb90c44730cc7b7a94ff7f696bea35&type=parity#raw
To Reproduce
Steps to reproduce the behavior:
from gnosis.eth.contracts import get_erc20_contract
from web3 import Web3

erc20 = get_erc20_contract(Web3())
erc20.decode_function_input('0xa9059cbb0000000000000000000000002c4db8a83f7ae70c00548c53ac55579b9a8744e50000000000000000000000000000000000000000000002c182040d8f7d0000')

A InsufficientDataBytes: Tried to read 32 bytes.  Only got 31 bytes is raised

https://github.com/ethereum/web3.py/issues/1678


[3.x] Physics Interpolation - Fix behaviour on pause

Resets nodes on pause, which prevents them pausing in a glitchy state (where prev and current transforms are different, and no longer being updated).
Fixes https://github.com/godotengine/godot/pull/92391#issuecomment-2179553490
Notes

This may not fix every scenario for pausing, but should fix the major ones.
It is possible skinned 2D might need a tweak or any other manually interpolated nodes, but will wait for MRP.

Regarding the glitch, it is possible we can later look into having both a paused interpolation fraction and a running interpolation fraction, but this should hopefully deal with the major problem of paused nodes continuously interpolating between different prev and curr transforms, so should be quite serviceable for the meantime.

Thanks!


fstar: add symlink to ocaml lib

Description of changes
Nix adds the library to OCAMLPATH automatically if the library is installed in its standard Nix location.
This allows building F* programs extracted to OCaml more easily. The library has been renamed to fstar.lib, though.
Some libraries need to be propagated as they are needed when building a program that depends on fstar.lib.
Fixes #275866
Note: it would probably be better to build this package with dune, but a straightforward attempt ran into an issue that I don't know how to fix. In the mean time, I came up with this fix instead.
cc @marsam @gebner @pnmadelaine

Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Thanks for reporting the issue and looking into it!
Also, sorry for letting this happen in the first place.
I just opened #275924, which was long overdue, to build F* with Dune.


Fix e2e tests by upgrading kind version to v0.11.1

Upgrade kind to v0.11.1 to fix problems with the cluster startup in github actions, which forced e2e test to fail.
/kind bug
/priority important-soon
/assign
Happened also at https://github.com/3scale-ops/marin3r/pull/114

/retitle Fix e2e tests by upgrading kind version to v0.11.1

/approve


ValueError: Expected more than 1 value per channel when training, got input size torch.Size([1, 12, 1])

Always reporting errors on different samples,
Has anyone encountered the same problem before？

hello，have you solved the problem? and how?

hello，have you solved the problem? and how?

no, how about you now?

I have solved this problem, after checking I found that because I am using a self-built dataset, the image size is not the same as kitti (mine is 19201080, kitti's is 1270400), so I did not modify the input and output sizes when generating the depth map resulting in a pseudo-point cloud generated that does not correspond to my image. The specific solution is to modify the code when generating the depth map to 1920*1080, and modify the w,h parameter in the sfd_head.py at about line 505 (modify it to be slightly larger than the size of the input image).

I have solved this problem, after checking I found that because I am using a self-built dataset, the image size is not the same as kitti (mine is 1920_1080, kitti's is 1270_400), so I did not modify the input and output sizes when generating the depth map resulting in a pseudo-point cloud generated that does not correspond to my image. The specific solution is to modify the code when generating the depth map to 1920*1080, and modify the w,h parameter in the sfd_head.py at about line 505 (modify it to be slightly larger than the size of the input image).

I am using a self-built dataset,too.I changed the values of w and h（1280960） according to your suggestion, but the problem still exists, and I found that when I increase the batch size, the problem will be alleviated, but it still exists.  Could you please tell me how did you modify the code when generating the depth map to 19201080?  Or do you have any other good suggestions?

I have solved this problem, after checking I found that because I am using a self-built dataset, the image size is not the same as kitti (mine is 1920_1080, kitti's is 1270_400), so I did not modify the input and output sizes when generating the depth map resulting in a pseudo-point cloud generated that does not correspond to my image. The specific solution is to modify the code when generating the depth map to 1920*1080, and modify the w,h parameter in the sfd_head.py at about line 505 (modify it to be slightly larger than the size of the input image).

I am using a self-built dataset,too.I changed the values of w and h（1280960） according to your suggestion, but the problem still exists, and I found that when I increase the batch size, the problem will be alleviated, but it still exists. Could you please tell me how did you modify the code when generating the depth map to 19201080? Or do you have any other good suggestions? @vacant-ztz

I have solved this problem, after checking I found that because I am using a self-built dataset, the image size is not the same as kitti (mine is 1920_1080, kitti's is 1270_400), so I did not modify the input and output sizes when generating the depth map resulting in a pseudo-point cloud generated that does not correspond to my image. The specific solution is to modify the code when generating the depth map to 1920*1080, and modify the w,h parameter in the sfd_head.py at about line 505 (modify it to be slightly larger than the size of the input image).

I am using a self-built dataset,too.I changed the values of w and h（1280960） according to your suggestion, but the problem still exists, and I found that when I increase the batch size, the problem will be alleviated, but it still exists. Could you please tell me how you modify the code when generating the depth map to 19201080? Or do you have any other good suggestions?

I have solved this problem, after checking I found that because I am using a self-built dataset, the image size is not the same as kitti (mine is 1920_1080, kitti's is 1270_400), so I did not modify the input and output sizes when generating the depth map resulting in a pseudo-point cloud generated that does not correspond to my image. The specific solution is to modify the code when generating the depth map to 1920*1080, and modify the w,h parameter in the sfd_head.py at about line 505 (modify it to be slightly larger than the size of the input image).

I am using a self-built dataset,too.I changed the values of w and h（1280960） according to your suggestion, but the problem still exists, and I found that when I increase the batch size, the problem will be alleviated, but it still exists. Could you please tell me how you modify the code when generating the depth map to 19201080? Or do you have any other good suggestions? @vacant-ztz

I have solved this problem, after checking I found that because I am using a self-built dataset, the image size is not the same as kitti (mine is 1920_1080, kitti's is 1270_400), so I did not modify the input and output sizes when generating the depth map resulting in a pseudo-point cloud generated that does not correspond to my image. The specific solution is to modify the code when generating the depth map to 1920*1080, and modify the w,h parameter in the sfd_head.py at about line 505 (modify it to be slightly larger than the size of the input image).

I am using a self-built dataset,too.I changed the values of w and h（1280960） according to your suggestion, but the problem still exists, and I found that when I increase the batch size, the problem will be alleviated, but it still exists. Could you please tell me how do you modify the code to generate the depth map to 19201080? Or do you have any other good   suggestions? @vacant-ztz

I have solved this problem, after checking I found that because I am using a self-built dataset, the image size is not the same as kitti (mine is 1920_1080, kitti's is 1270_400), so I did not modify the input and output sizes when generating the depth map resulting in a pseudo-point cloud generated that does not correspond to my image. The specific solution is to modify the code when generating the depth map to 1920*1080, and modify the w,h parameter in the sfd_head.py at about line 505 (modify it to be slightly larger than the size of the input image).

I am using a self-built dataset,too.I changed the values of w and h（1280960） according to your suggestion, but the problem still exists, and I found that when I increase the batch size, the problem will be alleviated, but it still exists. Could you please tell me how do you modify the code to generate the depth map to 19201080? Or do you have any other good suggestions? @vacant-ztz

I have solved this problem, after checking I found that because I am using a self-built dataset, the image size is not the same as kitti (mine is 1920_1080, kitti's is 1270_400), so I did not modify the input and output sizes when generating the depth map resulting in a pseudo-point cloud generated that does not correspond to my image. The specific solution is to modify the code when generating the depth map to 1920*1080, and modify the w,h parameter in the sfd_head.py at about line 505 (modify it to be slightly larger than the size of the input image).

I am using a self-built dataset,too.I changed the values of w and h（1280  *960） according to your suggestion, but the problem still exists, and I found that when I increase the batch size, the problem will be alleviated, but it still exists. Could you please tell me how do you modify the code to generate the depth map to 1920 *1080? Or do you have any other good suggestions? @vacant-ztz

If you want to modify the output size of the depth map, first, you need to modify the values of oheight, owidth, cwidth in SFD-TWISE-main/dataloaders/kitti_loader.py and make sure that they can be divisible by 16, and after that, you need to modify the size of pred_dep tensor in evaluate.py as the size of your output image. @HuangLLL123

Thank you very much. I have also solved my problem through your method, but I have encountered a new problem when using my self-built dataset, The problem is as follows:
File "/home/tianran/workdir/SFD/pcdet/models/roi_heads/target_assigner/proposal_target_layer.py", line 162, in subsample_rois
raise NotImplementedError
NotImplementedError
maxoverlaps:(min=nan, max=nan)
ERROR: FG=0, BG=0
I have tried many methods mentioned in the answers of other issues, such as normalizing point cloud features and reducing learning rates, but the problem has not been completely solved. Have you ever encountered this problem while using a self-built dataset? Could you please tell me your solution?

Thank you very much. I have also solved my problem through your method, but I have encountered a new problem when using my self-built dataset, The problem is as follows:
File "/home/tianran/workdir/SFD/pcdet/models/roi_heads/target_assigner/proposal_target_layer.py", line 162, in subsample_rois
raise NotImplementedError
NotImplementedError
maxoverlaps:(min=nan, max=nan)
ERROR: FG=0, BG=0
I have tried many methods mentioned in the answers of other issues, such as normalizing point cloud features and reducing learning rates, but the problem has not been completely solved. Have you ever encountered this problem while using a self-built dataset? Could you please tell me your solution? @vacant-ztz

Thank you very much. I have also solved my problem through your method, but I have encountered a new problem when using my self-built dataset, The problem is as follows:
File "/home/tianran/workdir/SFD/pcdet/models/roi_heads/target_assigner/proposal_target_layer.py", line 162, in subsample_rois
raise NotImplementedError
NotImplementedError
maxoverlaps:(min=nan, max=nan)
ERROR: FG=0, BG=0
I have tried many methods mentioned in the answers of other issues, such as normalizing point cloud features and reducing learning rates, but the problem has not been completely solved. Have you ever encountered this problem while using a self-built dataset? Could you please tell me your solution? @vacant-ztz

@HuangLLL123
maxoverlaps:(min=nan, max=nan)
ERROR: FG=0, BG=0
Hi, I'm experiencing the same problem on self-built dataset, have you solved it please?


TEST ANDREA GITHUB ISSUE

TEST ANDREA GITHUB ISSUE  BODY

Thanks for opening this issue. The ticket  was created for internal tracking.


refactor(shared-data): remove .dev_types submodules

The dev_types submodule is vestigial. This PR moves dev_types definitions to the respective init file and deletes dev_types
EXEC-220

Overview

Test Plan

Changelog

Review requests

Risk assessment

Moved to #15793


submit edited rows only to the server

hi  @tabalinas ,
can you help me with this issue.  m editing few rows in jsgrid, when i click on "submit" button , only those edited rows should get submitted on server.  i have more than 5000 records in a grid and i can not save all of them (will take a lot time). i just want to submit rows that edited by user.

Hi,
In updateItem of controller mark item as edited, for instance item.isEdited = true. Once you submit data, filter out only edited items.
This should do the trick.

can you tell me where ???
updateItem: function(item, editedItem) {
if(arguments.length === 1) {
editedItem = item;
}
        var $row = item ? this.rowByItem(item) : this._editingRow;
        editedItem = editedItem || this._getValidatedEditedItem();

        if(!editedItem)
            return;

        return this._updateRow($row, editedItem);

    },

I'm not talking about the source code of jsgrid. You have to define it in the controller.updateItem. Checkout demos and docs on the project site http://js-grid.com/


iOS 7 support

README says that the minimum deployment target is iOS 7, but the Podspec is set to iOS8. Which one is correct? Is there a way to use it with iOS 7?

Hey @almas73 I'm going to take a look at this today. If I remember correctly I was using something that required iOS 8 but I'm not sure. I'll check.


Exception when selecting on TextField

Steps to Reproduce

On iOS, press and hold on a TextField

Logs
[        ] flutter: The following assertion was thrown during performLayout():
[        ] flutter: 'package:flutter/src/rendering/box.dart': Failed assertion: line 1694 pos 18: 'debugDoingThisResize
[        ] flutter: || debugDoingThisLayout ||
[        ] flutter:                  (RenderObject.debugActiveLayout == parent && _size._canBeUsedByParent)': is not
[        ] flutter: true.
[        ] flutter:
[        ] flutter: Either the assertion indicates an error in the framework itself, or we should provide substantially
[        ] flutter: more information in this error message to help you determine and fix the underlying cause.
[        ] flutter: In either case, please report this assertion by filing a bug on GitHub:
[        ] flutter:   https://github.com/flutter/flutter/issues/new?template=BUG.md
[        ] flutter:
[        ] flutter: When the exception was thrown, this was the stack:
[        ] flutter: #2      RenderBox.size.<anonymous closure> (package:flutter/src/rendering/box.dart:1694:18)
[        ] flutter: #3      RenderBox.size (package:flutter/src/rendering/box.dart:1700:6)
[        ] flutter: #4      RenderFractionalTranslation.applyPaintTransform (package:flutter/src/rendering/proxy_box.dart:2425:24)
[        ] flutter: #5      RenderObject.getTransformTo (package:flutter/src/rendering/object.dart:2167:24)
[        ] flutter: #6      RenderBox.globalToLocal (package:flutter/src/rendering/box.dart:2244:31)
[        ] flutter: #7      _ToolbarRenderBox.performLayout (package:flutter/src/cupertino/text_selection.dart:167:35)
[        ] flutter: #8      RenderObject.layout (package:flutter/src/rendering/object.dart:1619:7)
[        ] flutter: #9      _RenderProxyBox&RenderBox&RenderObjectWithChildMixin&RenderProxyBoxMixin.performLayout (package:flutter/src/rendering/proxy_box.dart:105:13)
[        ] flutter: #10     RenderObject.layout (package:flutter/src/rendering/object.dart:1619:7)
[        ] flutter: #11     _RenderProxyBox&RenderBox&RenderObjectWithChildMixin&RenderProxyBoxMixin.performLayout (package:flutter/src/rendering/proxy_box.dart:105:13)
[        ] flutter: #12     RenderObject.layout (package:flutter/src/rendering/object.dart:1619:7)
[        ] flutter: #13     RenderStack.performLayout (package:flutter/src/rendering/stack.dart:510:15)
[        ] flutter: #14     RenderObject._layoutWithoutResize (package:flutter/src/rendering/object.dart:1496:7)
[        ] flutter: #15     PipelineOwner.flushLayout (package:flutter/src/rendering/object.dart:765:18)
[        ] flutter: #16     _WidgetsFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding&PaintingBinding&SemanticsBinding&RendererBinding.drawFrame (package:flutter/src/rendering/binding.dart:346:19)
[        ] flutter: #17     _WidgetsFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding&PaintingBinding&SemanticsBinding&RendererBinding&WidgetsBinding.drawFrame (package:flutter/src/widgets/binding.dart:701:13)
[        ] flutter: #18     _WidgetsFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding&PaintingBinding&SemanticsBinding&RendererBinding._handlePersistentFrameCallback (package:flutter/src/rendering/binding.dart:285:5)
[        ] flutter: #19     _WidgetsFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1016:15)
[        ] flutter: #20     _WidgetsFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:958:9)
[        ] flutter: #21     _WidgetsFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding._handleDrawFrame (package:flutter/src/scheduler/binding.dart:874:5)
[        ] flutter: #25     _invoke (dart:ui/hooks.dart:236:10)
[        ] flutter: #26     _drawFrame (dart:ui/hooks.dart:194:3)
[        ] flutter: (elided 5 frames from class _AssertionError and package dart:async)
[        ] flutter:
[        ] flutter: The following RenderObject was being processed when the exception was fired: _ToolbarRenderBox#3eb03 NEEDS-LAYOUT NEEDS-PAINT NEEDS-COMPOSITING-BITS-UPDATE:
[        ] flutter:   needs compositing
[        ] flutter:   creator: CupertinoTextSelectionToolbar ← CompositedTransformFollower ← FadeTransition ←
[        ] flutter:     _OverlayEntry-[LabeledGlobalKey<_OverlayEntryState>#f279e] ← Stack ← _Theatre ←
[        ] flutter:     Overlay-[LabeledGlobalKey<OverlayState>#d6d11] ← _FocusMarker ← Semantics ← FocusScope ←
[        ] flutter:     AbsorbPointer ← Listener ← ⋯
[        ] flutter:   parentData: <none> (can use size)
[        ] flutter:   constraints: BoxConstraints(w=414.0, h=736.0)
[        ] flutter:   size: Size(414.0, 736.0)
[        ] flutter: This RenderObject had the following descendants (showing up to depth 5):
[        ] flutter:     child: RenderDecoratedBox#7f472 relayoutBoundary=up1 NEEDS-PAINT NEEDS-COMPOSITING-BITS-UPDATE
[        ] flutter:       child: RenderFlex#e2bf8 relayoutBoundary=up2 NEEDS-PAINT NEEDS-COMPOSITING-BITS-UPDATE
[        ] flutter:         child 1: RenderSemanticsGestureHandler#46929 relayoutBoundary=up3 NEEDS-PAINT NEEDS-COMPOSITING-BITS-UPDATE
[        ] flutter:           child: RenderPointerListener#40223 relayoutBoundary=up4 NEEDS-PAINT NEEDS-COMPOSITING-BITS-UPDATE
[        ] flutter:             child: RenderSemanticsAnnotations#d9e45 relayoutBoundary=up5 NEEDS-PAINT NEEDS-COMPOSITING-BITS-UPDATE
[        ] flutter:         child 2: RenderConstrainedBox#bd267 relayoutBoundary=up3 NEEDS-PAINT
[        ] flutter:         child 3: RenderSemanticsGestureHandler#deb4a relayoutBoundary=up3 NEEDS-PAINT NEEDS-COMPOSITING-BITS-UPDATE
[        ] flutter:           child: RenderPointerListener#54aae relayoutBoundary=up4 NEEDS-PAINT NEEDS-COMPOSITING-BITS-UPDATE
[        ] flutter:             child: RenderSemanticsAnnotations#a5ece relayoutBoundary=up5 NEEDS-PAINT NEEDS-COMPOSITING-BITS-UPDATE
[   +2 ms] flutter: ════════════════════════════════════════════════════════════════════════════════════════════════════
[        ] flutter: Another exception was thrown: NoSuchMethodError: The method 'toDouble' was called on null.

No issues found! (ran in 4.7s)

    • Flutter version 1.7.8+hotfix.4 at /Users/robson/work/flutter
    • Framework revision 20e59316b8 (8 days ago), 2019-07-18 20:04:33 -0700
    • Engine revision fee001c93f
    • Dart version 2.4.0

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/robson/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 28.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 10.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 10.2.1, Build version 10E1001
    • CocoaPods version 1.7.2

[✓] iOS tools - develop for iOS devices
    • ios-deploy 1.9.4

[✓] Android Studio (version 3.4)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 37.1.1
    • Dart plugin version 183.6270
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)

[✓] IntelliJ IDEA Community Edition (version 2019.1.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 35.2.3
    • Dart plugin version 191.7019

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

[✓] Connected device (1 available)
    • Fingo’s iPhone • 48bb3178ff6a329c776e8ff9535fbc11b7e76ebf • ios • iOS 12.2

• No issues found!

CC @justinmc

@robsonfingo Can you modify my code below to show me how to reproduce this?  I don't see any error when long pressing this CupertinoTextField on the iOS simulator.
import 'package:flutter/cupertino.dart';

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

class TextFieldOnlyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return CupertinoApp(
      debugShowCheckedModeBanner: false,
      title: 'Text Field Test',
      home: CupertinoPageScaffold(
        child: Center(
          child: Padding(
            padding: const EdgeInsets.all(16.0),
            child: Column(
              mainAxisAlignment: MainAxisAlignment.center,
              children: <Widget>[
                CupertinoTextField(),
              ],
            ),
          ),
        ),
      ),
    );
  }
}

I can't reproduce it with a simple app. I can reproduce it at will from my complicated non-open source app, but that doesn't help you much. I was hoping the stack trace would give you enough information. Let me know if you want me to try something else.

One more thing, we're using MaterialApp, Scaffold and TextField, not the Cupertino versions.

I'm not sure :( It looks like it has something to do with laying out the text selection menu, but I can't think of any cause off the top of my head.
If anyone else runs into this, please post with any info you have.

hey, I have the same issue here

I'm not sure how true is this fix but it did work for me
a temporary fix for that issue is to edit :
packages/flutter/lib/src/rendering/box.dart file and make those changes :
`Size get size {
assert(hasSize, 'RenderBox was not laid out: ${toString()}');
assert(() {
if (_size is _DebugSize) {
final _DebugSize _size = this._size;
assert(_size._owner == this);
if (RenderObject.debugActiveLayout != null) {
// We are always allowed to access our own size (for print debugging
// and asserts if nothing else). Other than us, the only object that's
// allowed to read our size is our parent, if they've said they will.
// If you hit this assert trying to access a child's size, pass
// "parentUsesSize: true" to that child's layout().
      //The edit is here in adding  || true making it always true
      assert(debugDoingThisResize || debugDoingThisLayout || true ||
             (RenderObject.debugActiveLayout == parent && _size._canBeUsedByParent));

    }
    assert(_size == this._size);
  }
  return true;
}());
return _size;

}`

can you post your material app code?
I suspect you're using localizations, which at some point didn't work and cause the app to crash when displaying the text handles in ios, one option is to limit the platform to android (the ui platform not the underlying code) which you can do from the theme data in your material app
   theme: ThemeData(
        primarySwatch: Colors.blue,
        accentColor: Colors.blueAccent,
        platform: TargetPlatform.android,
      )

In my case we do not use localizations.

@justinmc I've been able to reproduce this and create a small app that shows the problem.
It seems to relate to when a TextField (both CupertinoTextField and Material) exists inside a CupertinoTabView.
import 'package:flutter/cupertino.dart';

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

class TextFieldOnlyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return CupertinoApp(
      debugShowCheckedModeBanner: false,
      title: 'Text Field Test',
      home: CupertinoTabView(
        builder: (_) {
          return Center(child: CupertinoTextField());
        },
      )
    );
  }
}

@rakis Thanks, I do see an exception when long pressing with that code!  I'll try to take a deeper look at why this is happening.

I can repro the same exception on the latest master bits with an open source sample, in case it's helpful.
Sample is here: https://github.com/timsneath/flutter_flip_view/tree/df0a98a0c2862a8a2d8231e0595b722fee695e17/example
crash-log.txt

Worth nothing that this is true for all text fields inside Nested Navigators, not just CupertinoTabView.
import 'package:flutter/material.dart';

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

class TextFieldOnlyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Text Field Test',
      home: Navigator(
        onGenerateRoute: (_) =>
          MaterialPageRoute(builder: (_) => Scaffold(body: TextField()))
      )
    );
  }
}

That explains why we have the crash. We use nested navigators too.

@VHCBlade Thanks for the small test case. I can reproduce the problem on master on Android by setting the target platform to iOS. Seems to be a problem with the cupertino text selection menu; it's failing in _ToolbarRenderBox.performLayout.
void main() => runApp(TextFieldOnlyApp());

class TextFieldOnlyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Text Field Test',
      theme: ThemeData(platform: TargetPlatform.iOS),
      home: Navigator(
        onGenerateRoute: (_) =>
          MaterialPageRoute(builder: (_) => Scaffold(body: TextField()))
      )
    );
  }
}

CC @justinmc

i have the almost same problem #47901


make compute metrics dictionary so you can have one per variable

thanks @jservonnat

@doutriaux1 Linked with #219?

no it's a different thing, as explained in #219, if no custom is defined it's not computed so we don't need a flag

Ok so I'm starting to understand this a little better - the aim here is to have multiple custom metrics - and the dictionary is the way to pass these to the package?

@jservonnat let's talk about this, if you look at the example parameter file I show how to fill the custom_metrics with many custom metrics.
In the above example (to be placed in parameter file for example)
the function "my_custom" receives "var",obs,mod
and then send them back to my_min and my_max
If it easily conceivable that "my_custom" looks at the value of "var" and THEN decides which functions to call. I will push a PR with the updated example to reflect this.
def mymax(slab,nm):
  return {"custom_%s_max" % nm:float(slab.max())}

def mymin(slab,nm):
  return {"custom_%s_min" % nm:float(slab.min())}

def my_custom(var,dm,do):
  out = {}
  for f in [mymax,mymin]:
    out.update(f(dm,"model"))
    out.update(f(dm,"ref"))
  out["some_custom"]=1.5
  return out
compute_custom_metrics = my_custom

@doutriaux1 Sounds interesting. I'll put it on test and get back to you soon.

@jservonnat the PR is at
https://github.com/PCMDI/pcmdi_metrics/pull/243


DTVF/FIA: Time series only - no metadata query.

It would be great if the metadata query in the Feature Info Agent config json was optional, too, with the front-end displaying just the PostGIS metadata if no such query is provided. This would allow attaching time series to datasets that have metadata from PostGIS, without having to write an OBDA mapping and a metadata query that pulls out the metadata that would be displayed otherwise anyway.
Originally posted by @sm453 in https://github.com/cambridge-cares/TheWorldAvatar/issues/466#issuecomment-1344121256

This has been address in PR #466.


CocoaPod release?

Hello!
Our app is using your library, and you included a few additions recently (being able to set colors, restrict timeframe) which we really need before the release. I see that you are actively improving the library currently. When do you plan to release a new CocoaPod version which includes these changes? Shall I wait for it or just use a git source in my project?

Hi,
I definitely plan to release a new CocoaPod with version 2.0 within a few weeks (maybe 2 or 3), although I can't be really precise about the date... There are a few more changes I'm working on now, especially on the month view. If you are in a hurry, maybe the best is indeed to include the library directly. I think it's fairly stable, but it's difficult for me to test thoroughly every configuration. Any report is very welcome in that matter!

Thank you. If it inspires you, we can donate you a small amount for your efforts :)

Also please note that version 2 will require iOS 8 or later, due to the use of the new presentation controllers. I hope that’s not a problem for you.
And thanks for the offer! ;)

iOS 8 is our target too. Do you have a paypal address maybe?

Hi, yes I have a Paypal address, which is the same as the one on my profile.
Thanks! In any case, it's already nice for me to know that this thing is useful for some people...

Thanks for the release. We have sent you a little amount of donation for your work.

Thank you, I very much appreciate!


Use the atom-workspace tag instead of the workspace class.

In keymaps/rails.cson: Use the atom-workspace tag instead of the workspace class.

Closed by #6


Julio/phenomenon and constant merger

This PR adds schema merging support for Constant, Phenomenon, Unit System schema items and Enumeration enumerators.
It only handles the case when those items are missing when merging two schemas, complex conflict resolution will be handled in future iterations, for the time being it throws an error if such conflicts exists.
Fixes #5993 #5992 #5991

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 3 committers have signed the CLA.:x: aurelija.monkevice:x: Julioalva:x: StefanApfelaurelija.monkevice 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.

/azp run iTwin.js


fix: file extension validation

What does this PR do?
This PR fixes the file input upload extension validation. First found in the create function step 2.

Test Plan
(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work.)
Related PRs and Issues
Fixes #7362
Have you read the Contributing Guidelines on issues?
Yes

Not sure resetting the input value when a file with a wrong extension is submitted is the way to go.
This is not following native behavior 👍🏻

@TorstenDittmann thank you for pointing that out. What other approach can I take into consideration? Can you please help me with this.