tensorboard first example problem

On MacOS High Sierra, after installing virtual environment and requirements, obtained this error when trying first tensorboard demo:
(rlenv) ➜  Chapter03 git:(master) ✗ tensorboard --logdir runs --host localhost
Traceback (most recent call last):
File "/anaconda3/bin/tensorboard", line 6, in
from tensorboard.main import run_main
File "/anaconda3/lib/python3.6/site-packages/tensorboard/init.py", line 4, in
from .writer import FileWriter, SummaryWriter
File "/anaconda3/lib/python3.6/site-packages/tensorboard/writer.py", line 28, in
from .summary import scalar, histogram, image, audio, text
File "/anaconda3/lib/python3.6/site-packages/tensorboard/summary/init.py", line 25, in
from tensorboard.summary import v1
File "/anaconda3/lib/python3.6/site-packages/tensorboard/summary/v1.py", line 24, in
from tensorboard.plugins.audio import summary as _audio_summary
File "/anaconda3/lib/python3.6/site-packages/tensorboard/plugins/audio/summary.py", line 36, in
from tensorboard.plugins.audio import metadata
File "/anaconda3/lib/python3.6/site-packages/tensorboard/plugins/audio/metadata.py", line 21, in
from tensorboard.compat.proto import summary_pb2
File "/anaconda3/lib/python3.6/site-packages/tensorboard/compat/proto/summary_pb2.py", line 15, in
from tensorboard.compat.proto import tensor_pb2 as tensorboard_dot_compat_dot_proto_dot_tensor__pb2
File "/anaconda3/lib/python3.6/site-packages/tensorboard/compat/proto/tensor_pb2.py", line 15, in
from tensorboard.compat.proto import resource_handle_pb2 as tensorboard_dot_compat_dot_proto_dot_resource__handle__pb2
File "/anaconda3/lib/python3.6/site-packages/tensorboard/compat/proto/resource_handle_pb2.py", line 22, in
serialized_pb=_b('\n.tensorboard/compat/proto/resource_handle.proto\x12\x0btensorboard"r\n\x13ResourceHandleProto\x12\x0e\n\x06\x64\x65vice\x18\x01 \x01(\t\x12\x11\n\tcontainer\x18\x02 \x01(\t\x12\x0c\n\x04name\x18\x03 \x01(\t\x12\x11\n\thash_code\x18\x04 \x01(\x04\x12\x17\n\x0fmaybe_type_name\x18\x05 \x01(\tBn\n\x18org.tensorflow.frameworkB\x0eResourceHandleP\x01Z=github.com/tensorflow/tensorflow/tensorflow/go/core/framework\xf8\x01\x01\x62\x06proto3')
File "/anaconda3/lib/python3.6/site-packages/google/protobuf/descriptor.py", line 878, in new
return _message.default_pool.AddSerializedFile(serialized_pb)
TypeError: Couldn't build proto file into descriptor pool!
Invalid proto descriptor for file "tensorboard/compat/proto/resource_handle.proto":
tensorboard.ResourceHandleProto.device: "tensorboard.ResourceHandleProto.device" is already defined in file "tensorboard/src/resource_handle.proto".
tensorboard.ResourceHandleProto.container: "tensorboard.ResourceHandleProto.container" is already defined in file "tensorboard/src/resource_handle.proto".
tensorboard.ResourceHandleProto.name: "tensorboard.ResourceHandleProto.name" is already defined in file "tensorboard/src/resource_handle.proto".
tensorboard.ResourceHandleProto.hash_code: "tensorboard.ResourceHandleProto.hash_code" is already defined in file "tensorboard/src/resource_handle.proto".
tensorboard.ResourceHandleProto.maybe_type_name: "tensorboard.ResourceHandleProto.maybe_type_name" is already defined in file "tensorboard/src/resource_handle.proto".
tensorboard.ResourceHandleProto: "tensorboard.ResourceHandleProto" is already defined in file "tensorboard/src/resource_handle.proto".

That's weird. Could you please send the output of pip list command in your environment?

Package             Version

absl-py             0.7.1
astor               0.7.1
atari-py            0.1.6
certifi             2019.3.9
chardet             3.0.4
cycler              0.10.0
future              0.17.1
gast                0.2.2
grpcio              1.20.1
gym                 0.10.9
h5py                2.9.0
idna                2.8
Keras-Applications  1.0.7
Keras-Preprocessing 1.0.9
kiwisolver          1.1.0
Markdown            3.1
matplotlib          3.0.2
numpy               1.15.4
opencv-python       <IP_ADDRESS>
Pillow              6.0.0
pip                 18.1
protobuf            3.7.1
ptan                0.3
pybullet            2.3.6
pyglet              1.3.2
pyparsing           2.4.0
python-dateutil     2.8.0
requests            2.21.0
scipy               1.1.0
setuptools          40.6.2
six                 1.12.0
tensorboard         1.12.0
tensorboard-pytorch 0.7.1
tensorflow          1.12.0
termcolor           1.1.0
torch               0.4.1
torchvision         0.2.1
urllib3             1.24.2
Werkzeug            0.15.2
wheel               0.33.1

Thanks!
Sorry, cannot reproduce this. Your dependencies looks fine, but tensorboard fails to start due to presence of some protobuf files I don't have in my own installation of this tensorboard. Have you had some later version installed which were downgraded in this environment? If yes, I'd suggest to create a new environment with proper dependencies installed from the beginning.
If it won't help, you can create a separate environment with only tensorflow and tensorboard installed, and use it to start tensorboard service.

Thanks for helping but it was a silly mistake.  I just needed to run tensorboard in the virtual environment rather than the default tensorboard.


Support multi-gpu transformers inference

Add a script for multi-gpu inference

Is it possible to use one script for both single-gpu and multi-gpu inference (for instance, users can launch the script with --single-gpu (default) or --multi-gpu) ? so that we only have to maintain one script.

Thank you for your contributions. We are indeed interested in your multi-gpu implementation. As requested, please consider merging the original inference script and yours into a unified one, so that the users can use with more flexibilities.

Okay, I will finish that work, thank you for your concern.

Is it possible to use one script for both single-gpu and multi-gpu inference (for instance, users can launch the script with --single-gpu (default) or --multi-gpu) ? so that we only have to maintain one script.

Thank you for your advice. I will complete the task as per your instructions.


Accumulator mode

Design a mode in which the QR-code remains displayed, and multiple resources successively sent stack up below.
Successive resources may come from one or multiple phones.

Make a nice (non-annoying) sound on target, at each reception.

Better keep QR on the left half, and resource(s) on the right half.


KeyError: 23， “self.env.step(action)”is wrong

The self-written DQN algorithm reports an error "KeyError", the gym version is 0.21.0, and the highway version is 1.6
`Traceback (most recent call last):
File "main.py", line 218, in
agent.train(n_episodes=opt.num_episodes, eps_decay=opt.eps_decay)
File "/home/sl/iv_rl-master/dqn/dqn.py", line 192, in train
self.test(episode=i_episode)
File "/home/sl/iv_rl-master/dqn/dqn.py", line 213, in test
next_state, reward, done, _ = self.env.step(action)
File "/home/sl/anaconda3/envs/213/lib/python3.8/site-packages/gym/wrappers/order_enforcing.py", line 37, in step
return self.env.step(action)
File "/home/sl/anaconda3/envs/213/lib/python3.8/site-packages/gym/wrappers/env_checker.py", line 39, in step
return self.env.step(action)
File "/home/sl/anaconda3/envs/213/lib/python3.8/site-packages/highway_env/envs/common/abstract.py", line 216, in step
self._simulate(action)
File "/home/sl/anaconda3/envs/213/lib/python3.8/site-packages/highway_env/envs/common/abstract.py", line 233, in _simulate
self.action_type.act(action)
File "/home/sl/anaconda3/envs/213/lib/python3.8/site-packages/highway_env/envs/common/action.py", line 240, in act
self.controlled_vehicle.act(self.actions[action])
KeyError: 23
`

Hi,
I don't know which DQN implementation you are using, but it seems to be returning an invalid action: 23.
When using discrete actions, the set of available actions is defined here:
https://github.com/eleurent/highway-env/blob/ffb35eacdfb2671623dc12d99b2ed5b6cb76e531/highway_env/envs/common/action.py#L183
and the maximum action is 4,which is why your action 23 is unavailable.
Your DQN implementation should read the number of actions available from the env's action_space.


Compile libmraa for Android and Brillo

Add makefile for building libmraa library.
Import glob functionality from the NetBSD project where the glob.c and
glob.h files are released under BSD 3-clause License. Minor changes were
applied in order to make them compile for Android and Brillo.
This patch adds a control pipe used to interrupt the poll() function
as an alternative to pthread cancellation API.
Change-Id: Id719da4c839acbd320b0cc0e0113c2a5239c8029
Signed-off-by: Mihai Serban<EMAIL_ADDRESS>

Small update - this is just watiing on QA aproval, should be merged by end of week

Merged with 5cf54fdbc26be56b9ac19887d0f86223bfe21c8d. Thanks!
You may be interested in the new -DMRAAPLATFORMFORCE option so you can compile for only the board you're interested in.

@tingleby we use the 3.10 kernel for edison. More exactly this one: https://android-review.googlesource.com/#/admin/projects/platform/hardware/bsp/kernel/intel branch edison-3.10 plus this patch still  under review: https://android-review.googlesource.com/#/c/183371/. That patch adds the pinmux under /sys/class...


branch-2.1 Fix CCR task repeat attach task DCHECK failed

Proposed changes
pick #32784
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Question tailing microsoft/mssql-server-linux logs

So, I'm following the pattern of using entrypoint.sh to start and seed the server inside of a docker-compose file. The problem I'm running into is my app resides in a separate container. So, I can't just run npm start to keep the container alive. I'm wondering if I can do something like this:
/opt/mssql/bin/sqlservr & /app/mssql-import.sh && tail -f <MSSQL_LOGS>

Any insights are much appreciated! Been banging my head on this one for a while. Thanks!

Are you saying that with only this: /opt/mssql/bin/sqlservr & /app/mssql-import.sh the container is dying after the mssql-import.sh script exits?

Yup, if I run just this:
/opt/mssql/bin/sqlservr & /app/mssql-import.sh

Then I get "exited with code 0", and the container is in a stopped state.

Same here. The problem is that the container only persists for the life of PID 1, which in this case becomes the script, rather than SQL Server.
@jaredmeakin Did you try your tail solution? If so, have you had success with it?
I'm currently working around it by calling RUN on the entrypoint.sh during the build and getting rid of the CMD, but this requires the SQL environment variables be defined at build time rather than runtime. However, it does accomplish the seeding as expected. Still looking for a better way.

Fix (TL;DR):
Thanks to this comment on issue #4, I discovered that reversing the two commands resolves the issue:
/usr/src/app/import-data.sh & /opt/mssql/bin/sqlservr

My thoughts & speculation:

This allows the script to run and SQL Server to start like before, but the container doesn't bail out as soon as it finishes the data seeding. Now that the container persists, I can see that PID 1 is /bin/sh -c /bin/bash ./entrypoint.sh
From that, my guess is that with the script the original way, sqlservr is spawned and detached, import-data.sh runs and completes and therefore entrypoint.sh is considered complete. The container sees PID 1 exit and stops as well.
With the commands reversed, import-data.sh is spawned and detached and then sqlservr is invoked, which runs and blocks indefinitely. This causes entrypoint.sh to remain open as PID 1 and the container to live on as expected.

Other tweaks & improvements (?):
Also, I wasn't confident in that arbitrary sleep command in import-data.sh. I replaced it with the following:
# wait for the SQL Server to come up
until /opt/mssql-tools/bin/sqlcmd -S localhost -U sa -P "$SA_PASSWORD" -d master -Q "SELECT 1"
do
    (>&2 echo "Failed to connect to SQL Server; waiting 2 seconds...")
    sleep 2s
    echo "Trying again..."
done
echo "Success! SQL Server is ready."

# run the setup script to create the DB and the schema in the DB
/opt/mssql-tools/bin/sqlcmd -S localhost -U sa -P "$SA_PASSWORD" -d master -i setup.sql

This loops attempting to run a SELECT 1 statement against the master database. Initially it gets Login timeout expired errors. While I was messing around, I also saw Login failed; invalid SA password (or something like that). If the call is unsuccessful (non-zero exit code), it will wait 2 seconds and try again. Once that call succeeds, we can be relatively sure that the subsequent call to run the setup.sql script will work as well. Feels cleaner than hoping we slept long enough.
Also worth mentioning, since sqlservr requires the SA_PASSWORD environment variable, we should be able to safely use it in the scripts as well, instead of repeatedly hard-coding the password.
@twright-msft, if you'd like to see any of these tweaks as a PR, let me know (specifically the change for the loop wait and the password variable). Obviously, the first part in reversing the commands isn't relevant to the node demo app, but certainly helpful to know for those of us attempting to use this idea in other ways.

@bzier that seems to do the trick. Thanks! What I was doing as a workaround was this:
/opt/mssql/bin/sqlservr & /app/mssql-import.sh && tail -f /dev/null

I also ended up with a similar check using sqlcmd for determining when to seed the database, but it hadn't occurred to me to use to determine its availability—nice one!
At this point, I think the original intent of my inquiry has been satisfied. I'll go ahead and close this issue out. Thanks, @bzier & @twright-msft !


Replit

Hello, @owersite, @Bekston, @flowitoo, @v01d2, deep apologies for the pings, I was just wondering if any of you know how to make it work on Replit? If so, contact me on Discord at Shkeffy#9999, and thank you so very much for taking the time to actually read this, most developers don't :/

it doesnt work on replit

😭


Support FragmentActivity for plugins

This is a documentation ticket that explains why FragmentActivity is not currently supported for plugin access. Other tickets that reference this limitation can link to this one, and developers can thumbs up this issue if they run into use-cases that are significantly hampered by the lack of FragmentActivity support.
Why not make FlutterActivity a FragmentActivity in all cases?
Flutter's use of FragmentActivity requires the inclusion of the Fragment support library. The Fragment support library adds a 100k binary size increase (when optimized). Most full-Flutter apps do not require any use of Fragments, making that 100k binary size increase unnecessary. Therefore, a standard Flutter project uses FlutterActivity, which extends a regular Activity.
A FlutterFragmentActivity is made available within the Android embedding for those projects that require a FragmentActivity. However, the ActivityAware plugin API only exposes a regular Activity via getActivity(). This is because the only thing the embedding knows for sure is that an Activity is available, but not necessarily a FragmentActivity.
Some plugins really do require a FragmentActivity. The current solution for those plugins is to attempt to cast the Activity to a FragmentActivity. It then becomes the responsibility of the app developer to manually switch from FlutterActivity to FlutterFragmentActivity.
This ticket exists to collect issues and concerns about this approach. If a strong enough argument is made to add some kind of support for FragmentActivity exposure in the plugin APIs then the ecosystem team and the embedding team should work together to design the appropriate solution.

CC @xster

The use of biometrics is a good use case for this. It looks like this library no longer works with the new ActivityAware: https://github.com/authpass/biometric_storage
I wanted to use that library because they use the new BiometricManager which supports face unlock in the latest Android devices.

In my opinion the lack of support for FragmentedActivity is forcing people to choose between subset of packages. For example using the audio_service package and local_auth together is not possible. Changing FlutterActivity to FlutterFragmentedActivity for plugins that require it results in other plugins failing.
https://github.com/ryanheise/audio_service/issues/87

@snaeji can you describe why an app developer can't explicitly use a FlutterFragmentActivity to resolve the issue you're disussing?
Also, can you provide examples where "Changing FlutterActivity to FlutterFragmentActivity for plugins that require it results in other plugins failing."?

I cannot reproduce this issue and everything is working great on the latest stable Flutter release. Thanks 👍
@matthew-carroll i was having this issue in end of October 2019. The audio_service package was throwing a null error when getting the context.
From the audio_service issue linked in my last comment:

It could be that application.getCurrentActivity() simply doesn't work (returns null) when you're using a FlutterFragmentActivity, and if that is the case, there's unfortunately nothing I can do on my end, and yes, it may be necessary to raise the issue with the Google team.

It sounds like maybe the audio_service should update to the new plugin API. Plugins should not be invoking application.getCurrentActivity() any more.

Is this still relevant for the V2 embedding?
/cc @blasten

https://stackoverflow.com/a/69432333/13389569
This is a temporary workaround for this issue.


Change Google Analytics tracking to use Twitter OSS account

@scosenza, @cacoco, this is a new property tied to the official Twitter OSS Google Analytics account.

@travisbrown Thanks!

@travisbrown Changes have been deployed -- should show up shortly.


Is openapi_core compatible with falcon 3.0.0?

I am getting the error while using openapi_core with falcon as middleware. All requests without body give error code 400 and following error message:
{'title': 'Invalid JSON', 'description': 'Could not parse an empty JSON body'}
Looks like fixing the following code fixes this error:
https://github.com/p1c2u/openapi-core/blob/master/openapi_core/contrib/falcon/requests.py#26
body = (
dumps(request.json) if getattr(request, "json", None)

       else dumps(request.media)

       else dumps(request.get_media({}))

personally I get:
{
    "title": "415 Unsupported Media Type",
    "description": "text/plain is an unsupported media type."
}

On a route that doesn't take any body.

Falcon integration is compatible with falcon 2.x


Editor UI: 3d viewport

Improved grid and interactions
New 3d gizmo
Gizmos visibility

@NathanLovato what do you think of covering the 3D editor in general, together with the new features? The video won't be too long I believe.

Yup, I'll leave it up to you.

Done, it's going to be rendered tonight and uploaded tomorrow.


Return storage alias in dataset information service response

Pull Request Test Coverage Report for Build<PHONE_NUMBER>5
Details

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.04%) to 86.322%

Totals

Change from base Build<PHONE_NUMBER>6:
0.04%

Covered Lines:
284

Relevant Lines:
329

💛  - Coveralls


Does not work with CE 2.14.0 :-(

Tried to use this CLI to integrate container deployment via bitbucket pipeline... Seems to no longer work.
+ portainer-cli login apiuser apipassword
Traceback (most recent call last):
  File "/usr/local/bin/portainer-cli", line 6, in <module>
    plac.call(p.main)
  File "/usr/local/lib/python3.11/site-packages/plac_core.py", line 436, in call
    cmd, result = parser.consume(arglist)
                  ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/plac_core.py", line 287, in consume
    return cmd, self.func(*(args + varargs + extraopts), **kwargs)
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/portainer_cli/__init__.py", line 260, in main
    plac.call(self.login, args)
  File "/usr/local/lib/python3.11/site-packages/plac_core.py", line 436, in call
    cmd, result = parser.consume(arglist)
                  ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/plac_core.py", line 287, in consume
    return cmd, self.func(*(args + varargs + extraopts), **kwargs)
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/portainer_cli/__init__.py", line 105, in login
    response = self.request(
               ^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/portainer_cli/__init__.py", line 236, in request
    response.raise_for_status()
  File "/usr/local/lib/python3.11/site-packages/requests/models.py", line 1021, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 422 Client Error: Unprocessable Entity for url: https://myportainer.tld:9443/api/auth

Seems that API has changed? Would also recommend to switch to access token instead of user/pass.

Same error, not working with ce 2.18


Add labels to scorecard tests

Description of the change:
part of the v1alpha2 implementation of the scorecard, this PR only adds the pre-defined labels to the basic and olm test definitions and adds the labels into the test results for displaying in JSON format (v1alpha2 only).
Motivation for the change:
this PR sets up future work where label selectors will be added and used to determine
what tests get executed.

/test e2e-aws-subcommand
/test e2e-aws-go
/test e2e-aws-helm

/test e2e-aws-helm
/test e2e-aws-subcommand

/test e2e-aws-subcommand
/test e2e-aws-helm


Add touch PEPs to the README

[ ] main
[ ] 4-3-stable

Documentation
The touch API PEPs are supported, but aren't listed in the README. We should add those.

There are other PEPs that need to be added as well.

pep_api_mod_avu_metadata_pre


Add possibility to authorized external access token to login

Hi,
I am Benoit Ducarouge and I work in Oslandia. For the purposes of a client project we need to be able to connect to QWC2 (configured with the OIDC service) from QGIS.
This PR allows you to authorize a QWC2 connection from an Access Token obtained from QGIS (OAuth2 configuration).
The QWC2 JWT Token is seen here as a protected resource and the Access Token received is validated according to the specifications of the Authlib library: https://docs.authlib.org/en/latest/jose/jwt.html#jwt- payload-claims-validation.
The implementation and configuration of the OIDC service makes it possible to authorize several Access Tokens potentially from different authorities with fine control over the content of the payload.
I am open to comments and recommendations if you feel that this is not the right way to do it.
This PR has been tested and is functional with Keycloack and Azure.
Thank you in advance for your feedback.

As far as my understanding goes this looks good to me. Would it be possible to add a word or two to the README?

Thanks for this quick review, some documentation has been added in the README, tell me if this is sufficient or if i need to detail some use case.

Thanks!


Location - CMS Fields layout

After working on a project, I ran into some issues with tab order for Location in the CMS. Simplest solution is not to remove the main tab and use Main for the Info tab. This will help ensure new tabs added through extensions will not be the opening tag when adding/editing.

closed via #64


Format Publications Office

When mapping ISO to DCAT Distributions, the list of formats by the EU Publications Office is used (https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/file-type) in Flanders. We would suggest that this list is used by all parties (mentioned in a usage note?).

Actually, this is already specified by GeoDCAT-AP 2.0.0 in the Controlled Vocabularies section.


✨[Feature] Let users set input shape, dtype and format using example tensors

Is your feature request related to a problem? Please describe.

Now that we are going to be able to specify tensor properties for inputs such as data type and format, it should be easier to use a tensor I already have as an example of the shape dtype and format I want.
Describe the solution you'd like

compile should be able to accept a list of Tensors to represent my graph inputs. From those tensors compile should be able to infer shape, data type and tensor format for the user. These should be logged in the debug log for easy debugging.
Describe alternatives you've considered

Note: I dont think theres a way to support dynamic shape using this method, so users will need to use trtorch.Input for that
Additional context

Why, if you supply 3 Tensors for min/opt/max, it's no less flexibility than we have with size arguments.

This also correlates with https://github.com/NVIDIA/TRTorch/issues/538

Why, if you supply 3 Tensors for min/opt/max, it's no less flexibility than we have with size arguments.

There are some issues I see with defining min/opt/max with example tensors, at least how i pictured it. For instance:
trtorch.compile(my_mod, {"inputs": [example_in]})

From example_in we can infer shape, dtype and tensor format directly from the Tensor.
In the case of dynamic shape, we need some sort of grouping for the tensor, so maybe you do something like
trtorch.compile(my_mod, {"inputs": [
    {"min": example_in_min,
     "opt": example_in_opt,
     "max": example_in_max}
]})

But, in this case, what do we do if something like the dtype or tensor format is inconstant between tensors?
Also doesnt seem like this is that different than doing at this point:
trtorch.compile(my_mod, {"inputs": [
    trtorch.Input(min_shape=example_in_min.shape(),
        opt_shape=example_in_opt.shape(),
        max_shape=example_in_max.shape(), dtype=torch.float)
]})

We could maybe have trtorch.Input pull out the shape and error out if the types are inconstant. Really though we wanted to give users a bypass around trtorch.Input with this feature.


Test on major distros on travis

We should test the script in docker containers on travis. At least these distros:

debian
ubuntu
fedora
centos
opensuse
archlinux
...?

Testing should also include compiling a very simple haskell file.


Cannot skip parsing png file

I saved an ER diagram to a .png file and added it to my --files list.  However, yard is generating errors and potentially unpredictable behavior because it is scanning the .png file for links and markup.  How can I indicated to yard that this is a binary file so it will not try to parse it?

@marlinpierce using --files is explicitly meant to parse file contents. You're probably looking for the --asset option to copy any extra image assets over to your doc/ directory after generation.


Use getMethod() instead of getDeclaredMethod().

This add support for implementing a base interface or extending
a base abstract class while using @JsonQualifier annotations.
Closes https://github.com/rharter/auto-value-moshi/issues/32

LGTM pending fixing the checkstyle issues

@hzsweers most are simple line lenght that I'll fix, but this one:
:auto-value-moshi:checkstyleTest[ant:checkstyle] [ERROR] /home/travis/build/rharter/auto-value-moshi/auto-value-moshi/src/test/java/com/ryanharter/auto/value/moshi/AutoValueMoshiExtensionTest.java:1: File length is 2,062 lines (max allowed is 2,000). [FileLength]
can I increse the FileLength vaule?

I'd just comment out the check.
On Fri, Sep 22, 2017 at 5:48 PM Lucio Maciel<EMAIL_ADDRESS>wrote:

@hzsweers https://github.com/hzsweers most are simple line lenght that
I'll fix, but this one:
:auto-value-moshi:checkstyleTest[ant:checkstyle] [ERROR]
/home/travis/build/rharter/auto-value-moshi/auto-value-moshi/src/test/java/com/ryanharter/auto/value/moshi/AutoValueMoshiExtensionTest.java:1:
File length is 2,062 lines (max allowed is 2,000). [FileLength]
can I increse the FileLength vaule?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/rharter/auto-value-moshi/pull/94#issuecomment-331568503,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEEEV8aVJakutF_pgxN4catElhUl0z1ks5slCsmgaJpZM4PhJUI
.

Thanks!


Switch default kvm flavour from lkvm to qemu

A private semaphoreCI run on this branch shows:

No test failures (same as lkvm)
The same number of test passes

lgtm
(pending CI)

@reviewer lucab

I'm :+1: on this. For release scheduling purposes, we have 1.24.0 being cut on 02/02 and https://github.com/coreos/rkt/pull/3484 still pending, how do we prefer to proceed?
My suggestion would be:

rebase and merge #3484
tag 1.24.0 (current week), last one defaulting to lkvm
switch rkt SemaphoreCI to test qemu-kvm and perform a smoke run
merge this PR
ensure that we have everything in place for releasing it (eg. rkt-builder)
tag 1.25.0 (in two weeks), first one defaulting to qemu-kvm

@lucab - Thanks. +1 for your suggested plan.

yep, @jodh-intel and I had a chat and agreed - +1

I built a rkt-builder image which works with this PR (rebased locally on master), but I get a few warnings during linkage.
@jodh-intel @grahamwhaley could you please take a look at the output below?
Here's the relevant log output:
config.status: creating Makefile

        rkt 1.24.0+gitdb46cd9a-dirty

        stage1 setup

        type:                                   'flavor'
        default stage1 location:                '/usr/lib/rkt/stage1-images/stage1-coreos.aci'
        default stage1 images directory:        '/usr/lib/rkt/stage1-images'

        built stage1 flavors:                   'coreos,kvm,fly'
        default stage1 flavor:                  'coreos'
        implied default stage1 name:            'coreos.com/rkt/stage1-coreos'
        implied default stage1 version:         '1.24.0+gitdb46cd9a-dirty'

        coreos/kvm flavor specific build parameters

        local CoreOS PXE image path:            ''
        local CoreOS PXE image systemd version: ''
        stage1 CoreOS board:                    'amd64-usr'

        kvm flavor specific build parameters

        hypervisors:                            'qemu'

        coreos flavor specific build parameters

        interpreter:                            '/usr/lib/ld-linux-x86-64.so.2'

        other build parameters

        functional tests enabled:               'no'
        incremental build:                      'no'
        features:                               '-TPM +SDJOURNAL'
        ACI arch:                               'amd64'
        go version:                             '1.7.4'
        go arch:                                'amd64'
...
  ACTOOL       /opt/build-rkt/target/bin/stage1-fly.aci
  ACTOOL       /opt/build-rkt/target/bin/stage1-coreos.aci
  BUILD EXT    qemu
  COPY BIOS    bios-256k.bin
  COPY BIOS    kvmvapic.bin
  COPY BIOS    linuxboot.bin
  COPY BIOS    linuxboot_dma.bin
  COPY BIOS    vgabios-stdvga.bin
  COPY BIOS    efi-virtio.rom
  UNTAR        /opt/build-rkt/tmp/usr_from_kvm/kernel/linux-4.9.2.tar.xz => /opt/build-rkt/tmp/usr_from_kvm/kernel
  BUILD EXT    bzImage
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libglib-2.0.a(libglib_2_0_la-gutils.o): In function `g_get_user_database_entry':
(.text+0x26d): warning: Using 'getpwuid' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libglib-2.0.a(libglib_2_0_la-gutils.o): In function `g_get_user_database_entry':
(.text+0xdc): warning: Using 'getpwnam_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libglib-2.0.a(libglib_2_0_la-gutils.o): In function `g_get_user_database_entry':
(.text+0x114): warning: Using 'getpwuid_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libglib-2.0.a(libglib_2_0_la-gutils.o): In function `g_get_user_database_entry':
(.text+0x26d): warning: Using 'getpwuid' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libglib-2.0.a(libglib_2_0_la-gutils.o): In function `g_get_user_database_entry':
(.text+0xdc): warning: Using 'getpwnam_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libglib-2.0.a(libglib_2_0_la-gutils.o): In function `g_get_user_database_entry':
(.text+0x114): warning: Using 'getpwuid_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libglib-2.0.a(libglib_2_0_la-gutils.o): In function `g_get_user_database_entry':
(.text+0x26d): warning: Using 'getpwuid' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libglib-2.0.a(libglib_2_0_la-gutils.o): In function `g_get_user_database_entry':
(.text+0xdc): warning: Using 'getpwnam_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libglib-2.0.a(libglib_2_0_la-gutils.o): In function `g_get_user_database_entry':
(.text+0x114): warning: Using 'getpwuid_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
libqemuutil.a(qemu-sockets.o): In function `inet_connect_saddr':
qemu-sockets.c:(.text+0xc12): warning: Using 'getaddrinfo' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libglib-2.0.a(libglib_2_0_la-gutils.o): In function `g_get_user_database_entry':
(.text+0x26d): warning: Using 'getpwuid' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libglib-2.0.a(libglib_2_0_la-gutils.o): In function `g_get_user_database_entry':
(.text+0xdc): warning: Using 'getpwnam_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libglib-2.0.a(libglib_2_0_la-gutils.o): In function `g_get_user_database_entry':
(.text+0x114): warning: Using 'getpwuid_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
libqemuutil.a(qemu-sockets.o): In function `inet_connect_saddr':
qemu-sockets.c:(.text+0xc12): warning: Using 'getaddrinfo' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libglib-2.0.a(libglib_2_0_la-gutils.o): In function `g_get_user_database_entry':
(.text+0x26d): warning: Using 'getpwuid' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libglib-2.0.a(libglib_2_0_la-gutils.o): In function `g_get_user_database_entry':
(.text+0xdc): warning: Using 'getpwnam_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libglib-2.0.a(libglib_2_0_la-gutils.o): In function `g_get_user_database_entry':
(.text+0x114): warning: Using 'getpwuid_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
libqemuutil.a(qemu-sockets.o): In function `inet_connect_saddr':
qemu-sockets.c:(.text+0xc12): warning: Using 'getaddrinfo' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libglib-2.0.a(libglib_2_0_la-gutils.o): In function `g_get_user_database_entry':
(.text+0x26d): warning: Using 'getpwuid' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libglib-2.0.a(libglib_2_0_la-gutils.o): In function `g_get_user_database_entry':
(.text+0xdc): warning: Using 'getpwnam_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libglib-2.0.a(libglib_2_0_la-gutils.o): In function `g_get_user_database_entry':
(.text+0x114): warning: Using 'getpwuid_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libglib-2.0.a(libglib_2_0_la-gutils.o): In function `g_get_user_database_entry':
(.text+0x26d): warning: Using 'getpwuid' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libglib-2.0.a(libglib_2_0_la-gutils.o): In function `g_get_user_database_entry':
(.text+0xdc): warning: Using 'getpwnam_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libglib-2.0.a(libglib_2_0_la-gutils.o): In function `g_get_user_database_entry':
(.text+0x114): warning: Using 'getpwuid_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
../os-posix.o: In function `os_setup_post':
os-posix.c:(.text+0x515): warning: Using 'initgroups' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
../os-posix.o: In function `os_parse_cmd_args':
os-posix.c:(.text+0x2c4): warning: Using 'getpwnam' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
../net/slirp.o: In function `slirp_smb':
slirp.c:(.text+0x4b5): warning: Using 'getpwuid' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libglib-2.0.a(libglib_2_0_la-gutils.o): In function `g_get_user_database_entry':
(.text+0xdc): warning: Using 'getpwnam_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libglib-2.0.a(libglib_2_0_la-gutils.o): In function `g_get_user_database_entry':
(.text+0x114): warning: Using 'getpwuid_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
../net/l2tpv3.o: In function `net_init_l2tpv3':
l2tpv3.c:(.text+0xade): warning: Using 'getaddrinfo' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
../net/net.o: In function `parse_host_port':
net.c:(.text+0x674): warning: Using 'gethostbyname' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
  COPY FILES   kvm-qemu
  ACTOOL       /opt/build-rkt/target/bin/stage1-kvm.aci

I did a small smoke test, and it seems to work though:
$ sudo ./release-build/target/bin/rkt run --stage1-path=./release-build/target/bin/stage1-kvm.aci --interactive --insecure-options=image,ondisk docker://progrium/busybox --exec=/bin/sh
/ # uname -a
Linux rkt-598436b9-e48f-4e7e-929a-ee33e76dc144 4.9.2-rkt-v1 #2 SMP Mon Feb 13 16:31:28 CET 2017 x86_64 GNU/Linux

switch rkt SemaphoreCI to test qemu-kvm and perform a smoke run

This was a dumb comment. As per this PR, Semaphore has already happily performed a smoke run.

Holding this against https://github.com/coreos/rkt-builder/pull/5, and then in turn holding 1.25 against this. Plan is to get a rkt-builder release out earlier tomorrow and then proceed with rkt one.
/cc @squeed @s-urbaniak


Introduce mapInPlace for Property types

As raised in https://github.com/gradle/gradle-native/issues/884, we currently hide the translation of a native task's properties into the underlying tool chain's arguments.
To move this translation out of the internals, the task/plugin would need to add a Provider to compilerArgs and the spec to compiler arguments transformer would be removed from the lower level infrastructure (NativeCompiler and down). Translation of link paths/include paths can be kept separate for now.  This would make the true compiler arguments an input to the compile task vs individual properties in the task.
Pseudo:
def compilerArgs = project.objects.listProperty(String).empty()

compilerArgs.addAll toolChain.map {
    // tool chain specific arguments
}
compilerArgs.addAll platform.map {
    // add specific platform arguments
}
compilerArgs.addAll provider {
    // other arguments that are always present
}
// etc

This works fine for replacing the low-level translation infrastructure, but it doesn't make it user defined. To allow a user to have control over the translation, we could introduce a new mapInPlace for compilerArgs, pseudo:
compilerArgs.mapInPlace { existing ->
    // modify existing however you want
    return newArgs
}

Proposed signature for ListProperty:
void mapInPlace(Transformer<List<T>, List<T>> transformer);

Each call to mapInPlace adds a transformer to be called in order after resolving the value of the provider but before returning from get().  If get() is never called, the transformers are never called. If the value of the provider is finalized, we can also choose to never call the transformers again.
Exceptions from the transformer would propagate out.
The transformer would not be called if the value is null. The transformer would not be allowed to return null.
Calling set would clear the list of "in-place" transformers.
Alternatively to using Transformer, we could also provide a mutable value to an Action. I think Transformer is a better fit for non-List values.
Alternative names:
finalize - this better reflects when this transform runs
modify - used in Haskell
adapt - we're adapting the value into something else before anyone sees it
tweak - we're tweaking the value as above.
replace - we're replacing the value with something else.
I think mapInPlace is a bit ugly looking but is easy to find along with map and flatMap. mapInPlace is used by Swift and some Scala libraries, so it's not an unusual name. I would stay with mapInPlace, but I like the feeling of finalize.
Since this probably makes more sense with Collection-like things, we could consider doing this only for ListProperty and SetProperty until we have a good use case for why this would be a generic feature of Property.
Examples:
ListProperty<Integer> args = project.objects.listProperty(Integer).empty()
args.addAll(1, 2, 3)
assert args.get() == [ 1, 2, 3 ]
args.mapInPlace { existing ->
    existing.collect { it*2 }
}
assert args.get() == [ 2, 4, 6 ]

// clears on set
args.set([1, 2, 3])
assert args.get() == [ 1, 2, 3 ]

// applied in order
args.mapInPlace { existing ->
    existing.collect { it*2 }
}
args.mapInPlace { existing ->
    existing.collect { it-1 }
}
assert args.get() == [ 1, 3, 5 ]

// propagates through map
def mapped = args.map { provided ->
    provided.collect { (it+1)/2 }
}
assert mapped.get() == [ 1, 2, 3 ]

args.set([1, 2, 3])
assert mapped.get() == [ 1, 1.5, 2 ]

args.mapInPlace { existing ->
    existing.collect { it*2 }
}
assert mapped.get() == [ 1.5, 2.5, 3.5 ]

// fails always
args.mapInPlace { existing ->
    null
}

args.finalizeValue()
assert args.get() == [ 2, 4, 6 ]

// fails after finalizeValue
args.mapInPlace { existing ->
    existing.collect { it*2 }
}

WDYT @adammurdoch ?

Before I forget this bit of information... when we talked about this issue a couple of weeks ago, we thought there was a strong resemblance between TaskProvider.configure and this mapInPlace idea.  Instead of supplying a transformer, we can just pass a mutable value to an action.
It's pretty clear in my mind how this could work with configurable things (where you can just set properties/add/remove like a List, Set or Task), but it's less clear how you'd configure a RegularFile since it's immutable.


context.getConfig usage documented incorrectly, missing functionality

Context.getConfig is documented a bit incorrectly. Here's the part I'm talking about:

It seems to imply from an api level that you can actually pass in an element which is not the case. That also spawns a question. Should there a way to get the config of another module without referencing Box.Application directly or writing a service to do so?

I'll fix the documentation. The short answer is no, a module should not be aware of another module so it doesn't make sense to grab configs for it.

Yep, after some thought I completely agree.

Fixed by #157.


Create Testimonial 10 black

One need to make this component using HTML and Tailwind CSS. I would suggest to use Tailwind Playgrounds to make things faster and quicker.
Here is a reference to the component.

Follow figma design and to make the button use Button Design System
After building the component please raise a PR with a screenshot of the component and add the component in Feature Cards/src/testimonials-10-black.html & Please do not add hover effect in the main div
If you need to use any icon please use it from Hero Icons
Good luck.

I would like to work on this issue


[Pager] HorizontalPager behaving like a Row on fast scroll

** I use compose 1.2.1 version but I have still this issue
** If you use a fast horizontalpager, it will not work and you receive an error

Could you please add more details on what do you mean by "fast horizontalpager" and what error do you receive

Hi, If I use the horizontal pager fastly, it wouldn't work or it may be freeze

I found the solving

@YusufbekIbragimov How do you slove this problem finally? I have the same problem now. Hope there is a solution. Thanks!


Batch size and iteration

Hi,
First of all thanks a lot for the code.
This is sort of an absolute beginner question, but if you use 150 batch size samples, and the total images of the CUHK03 dataset are 13164, the numbers of iteration per epoch should be 13164/batch size, right?. If you use 30000 iteration don't you risk to fall in the overfitting problem?
In the article, there was written that they use 210000 iteration, but they don't clarify if they use 210000 iterations per epoch or this number include all training iterations.
Thanks

Hi, to estimate how many iterations the model should be trained for this task is different with what you think.
First, though the total images of the CUHK03 dataset are about 13000, they are not the direct input of the model. The input of the model is a pair of two images, and has two labels: positive and negative. If one person has 10 images and each camera has 5 images, the total positive instances are 25. If the ratio of positive instance to negative instance is 1:3, the total instances for one person are 100. So it may have 130000 training examples. The total params of the model are nearly 20 millions so it's fine with about 100k iterations.
Hope this can help you.

Ok, i understand the first part of your answer, but i still can not understand why with 20 millions params you need 100k iterations. what kind of formula you use to determine the iterations number?
Thank you so much for your help!

There may be a formula to compute the number of iterations but I don't know what it is. In my opinion, at least let the model see every instance 5-20 times. Besides, saving the interval model weights and watching the loss curve also give you some help.

Thanks!!

Hi,
Thanks a lot for the code.
I wonder that if it's better to set the batch_size 128, or 32, 64 ?
And how long does it take to run all the 100 * 30,000 epochs?
Thanks!

Hi ,
Can you please tell how many training samples you have used in the code and how many testing samples?

@Ning-Ding
Hi,
Can you please explain what the parameters of train method (inside main.py) denotes?


Bump calcite SQL parser identifier max length from default 128 (SqlParser.DEFAULT_IDENTIFIER_MAX_LENGTH) to 1024.

For Pinot queries that involve heavy text matching, such as searching logs with long stack traces or strings, the default SQL parser identifier max length of 128 is inadequate. This PR increases the limit from the default of 128 (SqlParser.DEFAULT_IDENTIFIER_MAX_LENGTH) to 1024. Currently, this maximum value cannot be modified through configuration, but if needed in the future, the public static variable that stores this value could be made configurable easily.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 0.00%. Comparing base (59551e4) to head (aee5f42).
Report is 1277 commits behind head on master.

:exclamation:  There is a different number of reports uploaded between BASE (59551e4) and HEAD (aee5f42). Click for more details.
HEAD has 53 uploads less than BASE

Flag
BASE (59551e4)
HEAD (aee5f42)

integration
7
1

integration2
3
1

temurin
12
1

java-21
7
1

skip-bytebuffers-true
3
0

skip-bytebuffers-false
7
1

unittests
5
0

unittests1
2
0

java-11
5
0

unittests2
3
0

integration1
2
0

custom-integration1
2
0

Additional details and impacted files
@@              Coverage Diff              @@
##             master   #14363       +/-   ##
=============================================
- Coverage     61.75%    0.00%   -61.76%
=============================================
  Files          2436        3     -2433
  Lines        133233        6   -133227
  Branches      20636        0    -20636
=============================================
- Hits          82274        0    -82274
+ Misses        44911        6    -44905
+ Partials       6048        0     -6048

Flag
Coverage Δ

custom-integration1
?

integration
0.00% <ø> (-0.01%)
:arrow_down:

integration1
?

integration2
0.00% <ø> (ø)

java-11
?

java-21
0.00% <ø> (-61.63%)
:arrow_down:

skip-bytebuffers-false
0.00% <ø> (-61.75%)
:arrow_down:

skip-bytebuffers-true
?

temurin
0.00% <ø> (-61.76%)
:arrow_down:

unittests
?

unittests1
?

unittests2
?

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Can you elaborate more on why text search might use long identifier? Identifier is column name, instead of literal. What is the overhead of increasing it?

Can you elaborate more on why text search might use long identifier? Identifier is column name, instead of literal. What is the overhead of increasing it?

I have updated the PR description which explains the problem better. I don't think there is any overhead of increasing it as it is an artificial limit within the sql parser. For cases where the identifier does not exceed 128 characters, the overhead should be the same. For identifiers that exceeds 128 characters, we haven't noticed any observable overhead since query parsing constitute minimal run-time overhead compared to the query itself. It is extremely rare to encounter identifiers over 128 characters, but if we do encounter it, with this PR, queries will still be able to complete.


customizable timeout for template initialization?

Hello, following the elixir mix PR, I noticed that the elixir tasks are not always displayed. I tracked it down to the one overseer setting which is not configurable :D that is, the template init timeout:
https://github.com/stevearc/overseer.nvim/blob/master/lua/overseer/template/init.lua#L395
Sadly, mix help takes most of the time for me 0.7s, but it does go over 1s quite often... If we changed the code to take an override timeout through opts, I could call the overseer functions manually, passing a custom timeout, instead of calling the provided vim command. I could send a PR to that effect, but would you accept it? Or can you think of a better approach...
In the PR you mentioned possible future caching for these settings, but cache invalidation would not be trivial, because in elixir you can add tasks outside of the main exs file, and the timestamp of that file would not be updated. So I guess in my case increasing the timeout is probably the best I can do, bar manual cache invalidation (which actually would be ok in my case, i guess).
What do you think about that?

In a perfect world, we would populate the list as the results come, so they would tickle in asynchronously, but I don't believe it would be possible with a reasonable amount of effort in a neovim plugin.

Yet another alternative could be that instead of dynamically loading tasks, there is a function to generate tasks from elixir tasks, that the user may run manually. I believe overseer could support that. In that case display would be instant, but discovery worse. Maybe overseer could say something like "elixir project detected, consider importing tasks by running xxx"

instead of dynamically loading tasks, there is a function to generate tasks from elixir tasks, that the user may run manually

I think that functionally this would be the same as caching, so I'd prefer caching since it can be generalized.

In a perfect world, we would populate the list as the results come

This is doable, but not with the current API for vim.ui.select, unfortunately. Going down this road would mean a lot of custom code for one specific selection frontend.
For the time being I'll make the timeout a config option; that should unblock you. I'll make the template caching logic a priority since this is starting to matter more. I'll be trapped on a plane for 8 hours on Saturday, so I might be able to do it then.

I think that functionally this would be the same as caching, so I'd prefer caching since it can be generalized.

it's the same as caching except that for caching to work, the user might have to increase the timeout the first time? Unless if, thanks to caching, you enable to remove the timeout "the first time", or something like that.
Otherwise sounds like a great plan! :+1:

Whelp, it was a productive flight! If any provider takes longer than 100ms (configurable with template_cache_threshold), the results will be cached for the next run. There is some amount of smart cache clearing (e.g. if you write a Makefile, it will clear the cache for that Makefile), but it won't handle all cases (as you mentioned, a lot of files could impact the commands available to mix). You can add your own custom cache handling logic with preload_task_cache and clear_task_cache. You can also use the OverseerClearCache command to manually clear the cache.
I've also bumped up the default timeout, since long waits should only happen once now. Also, we cache the results of the provider even if it times out.

:tada: great! it works great and is super helpful. thanks a lot. and thanks again for overseer in general. I also wrote a custom component to parse the output of a build watcher we have, does marvels!
i'll close this issue, as I consider it fixed, but if you prefer to reopen it for your own needs, feel free of course!
thanks again!


Test ZetaSQLPlanner in DataCatalogBigQueryIT

Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Run SQL PostCommit

Run SQL PostCommit

@kennknowles

The semantics of getTable() are well defined in both Calcite and Beam as only taking the table name and not a fully qualified path. This changes that behavior to work around a bug. We should fix the root cause, not change the semantics of the API.

We should have a well documented design on our table naming resolution along with API design, which is a to-do work.

I think these points are not as mutually-exclusive as it may appear. Currently the protocol as far as I have grokked it is to call getSubProvider until it returns null, and then call getTable with the bit for which it returned null.
I don't like this protocol. It seems fragile and it also does not ensure that the entire list of qualifications on the names has been consumed. But in my conversations with Anton, he mentioned that this is what Calcite expects so we are not able to make a better protocol. Though Calcite is unaware of TableProvider so it must be via some other interface.
Notably, if you try to resolve a.b.c (which parses as ["a", "b", "c"]) and getSubProvider("b") returns null then what should you do? It is a bug in the table provider. As I understand it, the ZetaSQLPlanner does a fairly reasonable thing and concatenates the remainder and calls getTable("b.c"). This allows a TableProvider to own a whole prefix of the fully qualified name. Instead, it might uncover the bug if the ZetaSQLPlanner threw an error: getSubProvider not found for namespace "b" for TableProvider <current provider>.
Why is the TableProvider returning null? Is it because the DataCatalogTableProvider needs to have all the names up front and it is not receiving all of them?

Under the calcite API semantics if getSubProvider returns null and not all the tokens have been consumed then the subschema (and therefore table) doesn't exist. Under the new API established by this PR, it would seem getSubProvider is not longer needed and . is now a reserved character in table names. It turns out the DataCatalogTableProvider (and other FullNameTableProvider classes) have a getTableByFullName call that handles  your concern with the calcite APIs, is that something you could use instead?
To answer the last question, FullNameTableProvider requires a call to registerKnownTableNames to look up tables using the old Calcite APIs. This is a workaround for the inability to lazily load subschemas.
In this PR is a significant change to the semantics of an API. The title doesn't reflect this, there is no JIRA, no discussion, and there are a number of critical issues that are being deferred to followup PRs. There were no failing tests in Beam that would justify the abnormal approach taken here and this bug actually existed before the ZetaSQL dialect went into Beam, so it would seem if we need an emergency fix the correct approach would be to roll back #9210.
The next Beam release isn't scheduled to be cut until Wednesday. Hopefully we can get the right fix in before then?

I do not agree that this PR changes API semantics. It changes DataCatalogTableProvider and ZetaSQLQueryPlanner. Neither of these own any API semantics.
Your argument convinces me of something, though: this PR introduces incorrect behavior to DataCatalogTableProvider to compensate for incorrect clients. Let's definitely fix that ASAP.
My point is that "if getSubProvider returns null and not all tokens are consumed" is a fragile contract prerequisite. My understanding is that clients may be somewhat oblivious to whether or not all tokens have been consumed / they may not have access to the full list of tokens. The comments on FullNameTableProvider imply a protocol where a client is expected to always ask for a subprovider and only ask for a table if no subprovider is returned. This may be compensation for now-obsolete limitations in Data Catalog. In the world you posit where one can know if there are any further tokens, this exchange is unnecessary. The client knows whether to call getSubProvider and when to call getTable. I like that world; it is much simpler. Can we move to it immediately?
Minor nit: TableProvider is not a Calcite concept. That is our proxy for Calcite's Schema, am I wrong? And definitely . is not a reserved character. But rather, a client of TableProvider (specifically DataCatalogTableProvider) that concatenates the tail of a fully qualified name is enabled. As you point out, it should not be.

This is PR is actually a partial rollback of #9353(that PR was long time ago so cannot auto-rollback).
I am not know what design decision was made in the past. If you guys still think we should use that design, the right fix is to fix #9353 for sure. My fix can be considered as a temporal fix.


Remove default behavior of comparing RAX

By default, WP will compare the final values of RAX at the end of a subroutine's execution. We should remove this behavior as a default, and only compare these registers when the use specifies --wp-compare-final-reg-values=RAX. We should also change the name of the flag from output-vars to compare-final-reg-values.

Currently, switch_cases is failing. #178 should fix this test.


[question] Is it really necessary to handleKeybinds twice for each keyboard event?

The lines 174, 176 as well as 193, 193 of the KeybindManager.cpp call the manager's handleKeybinds method twice for each keyboard event, and are of the form found = handleKeybinds(...) || found;. I suspect that it's so to handle different events assigned to the same binding but using both the keysym and keycode (the question is why would anyone do so).
I'm writing a patch to add a new binding type: if a binding is pressed and held for n milliseconds and no other events occur, a specified handler is called. It's useful to have a status bar always hidden, and show it only when a user wants to move a window to a workspace but forgot which ones are currently empty (like mod + shift is pressed, and then nothing follows), for example. This involves removing a timer used to call the handler whenever any events occur, and is currently solved with the following "hack" in the beginning of the handleKeybinds:
// Literally any other event should suppress the timed one.
// The problem is, the method is called twice for each keyboard event,
// and removing the timer unconditionally results in the timer being killed
// by the same event that added it (but in the second call).
// Thus the newEvent flag is introduced
static int newEvent = 0;
newEvent += key.empty();  // keyboard event -> + 1, mouse event -> + 0
newEvent %= 2;
newEvent |= !key.empty(); // key string isn't empty in case of mouse events,
                          // and those call this method only once per event,
                          // hence, always new

if (m_pTimedKeybindEventSource && newEvent){
    wl_event_source_remove(m_pTimedKeybindEventSource);
    m_pTimedKeybindEventSource = nullptr;
}

Alternatively, the aforementioned lines can be rewritten as
found = g_pKeybindManager->handleKeybinds(MODS, "", keysym, 0, true, e->time_msec);
found = found || g_pKeybindManager->handleKeybinds(MODS, "", 0, KEYCODE, true, e->time_msec);

which'll allow removing the timer unconditionally (except checking for its existence) as well as removing the repeat timers the same way, but will make it possible to handle either a keysym or a keycode bind, with the former being prioritized. Is this approach viable?

I suspect that it's so to handle different events assigned to the same binding but using both the keysym and keycode (the question is why would anyone do so).

ye

This involves removing a timer used to call the handler whenever any events occur, and is currently solved with the following "hack" in the beginning of the handleKeybinds:

ugly af, why not see how binde works?

which'll allow removing the timer unconditionally (except checking for its existence) as well as removing the repeat timers the same way, but will make it possible to handle either a keysym or a keycode bind, with the former being prioritized. Is this approach viable?

no, you're breaking backwards compat for no reason

how binde works
Yap, sorry, killing the timer in the onKeyEvent/onMouseEvent section definitely makes more sense.


How to calculate the threshold accuracy based on the retrieved image ？

Dear AAnoosheh, thanks for your work. I have a question. I can utilize the NetVLAD to obtain the retrieved image, but I don‘t know how to calculate the threshold accuracy (I know the calculation formula). In other words, I don’t know how to get the location information of the query image and retrieved image. I think they should come from overcast-reference.db and query.db. However, I don't know how to use them. Thanks very much if you share that. My email address is<EMAIL_ADDRESS>thanks in advance.

Hi,
Yes it's confusing, I'll admit.  The dataset here is used:
https://data.ciirc.cvut.cz/public/projects/2020VisualLocalization/RobotCar-Seasons/
The .txt files provide 6DOF matrix ground truth localizations.
I put a query image in (from either the Night or Night-rain image folders), convert to "daytime", find the closest image in the Overcast folder, then compare the localization of the closest Overcast image to that of the Night query.

Thank you very much for your reply, I think I understand what you mean, thank you！


Information when load the model

Is this no parameters phenomenon normal?

aux_fpn and aux_head are auxiliary modules used only during training. If you are not resuming a training process, there is no need to load these parts.

Thank you, really appreciate!


feat: update layout for ledger tx

Update layouts for:

/approvals.html#/confirm-ledger-tx
/approvals.html#/confirm-sign-tx

@euharrison This works well for Ledger! I did notice a little discrepancy between button styles between the detail view & the view on submit, where the rounded corners are sharper on Details:

I think this is a problem with Tx Details though, since everywhere else they have more radius. There is a discrepancy in the Figma designs too, so not an issue with your PR!

@jurevans thanks for noticing it!
Border radius fixed :)

As your PR wasn't merged to main yet, do you think it's better if you press the merge button here?
Then you have a better control to decide the best moment to avoid conflicts for yourself

As your PR wasn't merged to main yet, do you think it's better if you press the merge button here? Then you have a better control to decide the best moment to avoid conflicts for yourself

nice! Yeah, I ended up having to make some changes, so I can handle that once everything is confirmed to work! Thanks!

Merged these changes to #815  via another branch, thanks!


Updated README to reflect relevant changes.

See #4 for an overview of the changes.

Looks good, thanks.


feat: add metadata title support for transactions

Problem solved
Short description of the bug fixed or feature added
Changes made

[ ] Public API changes: list the public API changes made if any
[ ] Internal API changes: explain the internal logic changes

How to test

[ ] Automated tests: link to unit test file
[ ] Manual tests: step by step instructions on how to test

Contributor NFT
Paste in your wallet address below and we will airdrop you a special NFT when your pull request is merged.
Address:

PR-Codex overview
This PR updates multiple components across different files to add a title prop for better customization and consistency in the UI.
Detailed summary

Added title prop to various components for customization and consistency in UI display.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#3664  👈
#3662
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @joaquim-verges and the rest of your teammates on  Graphite


Complete extension of the framework nuclides

Description
Update to the nuclides that are built into the ARMI framework. This expands the set of nuclide bases to include 4614 nuclides and imports the half-life data from the chart of the nuclides from a combination of the RIPL-3 database and from the IAEA chart of the nuclides.
Other Changes:

Each Element now has a phase and a group.
Element.nuclideBases becomes Element.nuclides - This is an API-breaking change.

Checklist

[x] This PR has only one purpose or idea.
[x] Tests have been added/updated to verify that the new/changed code works.

[x] The code style follows good practices.
[x] The commit message(s) follow good practices.

[ ] The release notes (location doc/release/0.X.rst) are up-to-date with any bug fixes or new features.
[x] The documentation is still up-to-date in the doc folder.
[x] The dependencies are still up-to-date in setup.py.

This will take some time to review, but please see the attached ipython notebook that can be used to check the data that is being proposed in this PR against the IAEA Chart of the Nuclides - https://www-nds.iaea.org/relnsd/vcharthtml/VChartHTML.html
Note that GitHub doesn't allow file uploads of .ipynb so the extension is changed to .txt.
iaea-check.txt

@john-science - I am not sure why the tests didn't run. Is this something that has been failing? Unit tests pass locally for me.

mass-comparisons.txt
nusf-comparisons.txt
abundance-comparisons.txt
halflife-comparisons.txt

@jakehader Assuming we get the unit tests working and all that...

Do you think this will require any breaking to our downstream projects?

NOTE: @opotowsky @sombrereau @drewj-usnctech

@jakehader @ntouran How much do we expect this to slow down ARMI?  This is a lot more nuclides.

@john-science - I am not sure why the tests didn't run. Is this something that has been failing? Unit tests pass locally for me.

  File "/home/runner/work/armi/armi/armi/physics/neutronics/fissionProductModel/lumpedFissionProduct.py", line 506, in createLFPsFromFile
    lfp = self._readOneLFP(lfpLines)
  File "/home/runner/work/armi/armi/armi/physics/neutronics/fissionProductModel/lumpedFissionProduct.py", line 576, in _readOneLFP
    nuc = nuclideBases.byMccId[nucLibId]
KeyError: 'GE73 5'

Once this is handled I can run some tests downstream. They also fail on the above unit test failure

Thanks for the ping. No problems on our end

Any recommendations or other needs coming from this? I'm not sure if you're still using Serpent @drewj-usnctech, but maybe a run down on if the nuclide bases work for getting Serpent IDs correctly would be nice. I am not sure if it's the same between ENDF/B-VII.0, ENDF/B-VII.1, and ENDF/B-VIII.0. Is there any good resource for this?

Thanks for the ping. No problems on our end

Any recommendations or other needs coming from this? I'm not sure if you're still using Serpent @drewj-usnctech, but maybe a run down on if the nuclide bases work for getting Serpent IDs correctly would be nice. I am not sure if it's the same between ENDF/B-VII.0, ENDF/B-VII.1, and ENDF/B-VIII.0. Is there any good resource for this?

Except for some rare exceptions, Serpent and MCNP ids align very well. We haven't hit major stumbling blocks

I think this docstring needs to be modified:

Thanks @keckler! Looking at the comments now to address

I can also confirm that all of the half-life data for ground state isotopes compares well against the IAEA data that was referenced above. In this case, "well" means that none of the half-lives are more than 1e-8% different than each other, with the exception of N11, which has 2 half-lives produced by the IAEA's API. One of those values agrees very well, and the other is off by >200%. However, that isotope has a half-life down near 1e-22 seconds.
Still working on verifying the following:

[ ] Half-lives of excited states
[ ] Mass
[ ] Abundance
[ ] Spontaneous fission yields

I will get to these tomorrow.

The current status of the review on the nuclides.dat file is as follows:

The half-life data that is currently in nuclides.dat does not appear to come from the RIPL-3 database, as is claimed in the header of nuclides.dat. It appears to align with the half-life data from the IAEA chart of the nuclides. Either the data in nuclides.dat should be updated to align with the RIPL-3 database as is claimed, or the text at the top of the nuclides.dat file should be updated to reflect where the data actually comes from.
The spontaneous fission yield data appears to align with its underlying source, however its source is not documented. The nuclides.dat header should be updated to reflect the source of this data (such a comment was suggested previously as well). This data cannot be compared against the IAEA chart of the nuclides because such data is not available from that source.
The mass and abundance data appear to align well with both their underlying sources and with the equivalent data from the IAEA chart of the nuclides.

My final request on this topic is the following:

The script used to process the RIPL-3 data and produce the nuclides.dat file should be uploaded to the repo. A user should be able to specify a local directory containing their own RIPL files, and should be able to reproduce the nuclides.dat file. This will help to retain the traceability, verifiability, and reproducibility of the data that is in the nuclides.dat file

Therefore, once the following items are successfully completed, I will be happy with nuclides.dat:

[ ] Update the half-life data and/or source
[ ] List the source of the spontaneous fission yield data
[ ] Upload the script that can be used to reproduce the nuclides.dat

@keckler  - ready for your final checks, sorry for all the commits it took some time to decouple the fission product model code. I opened https://github.com/terrapower/armi/issues/1013 in response to your last comment.

Looks like we lost 40 lines of code coverage somewhere.


Potential bug where main thread is out of sync with physics worker

Occasionally when reloading react-three-game-starter, you're unable to move. I suspect this might be an issue pertaining to the main thread and the physics worker no longer synchronizing the physics data. Need to verify if this is the case by tracking time since last update received. (Set a timeout that's cleared on new update, but if not logs a warning.)

To some degree, should be fixed by: https://github.com/simonghales/react-three-game-engine/releases/tag/0.13.2

To some degree, should be fixed by: https://github.com/simonghales/react-three-game-engine/releases/tag/0.13.2


Unbearably slow sorting on big mapped datasets

Describe the bug
For me, with ~40k lines, sorting took 3.5 seconds on a flattened dataset (including the flatten operation) and 22.7 seconds on a mapped dataset (right after sharding), which is about x5 slowdown. Moreover, it seems like it slows down exponentially with bigger datasets (wasn't able to sort 700k lines at all, with flattening takes about a minute).
Steps to reproduce the bug
from datasets import load_dataset
import time

dataset = load_dataset("xnli", "en", split="train")

dataset = dataset.shard(10, 0)

print(len(dataset))

t = time.time()

# dataset = dataset.flatten_indices()  # uncomment this line and it's fast

dataset = dataset.sort("label", reverse=True, load_from_cache_file=False)

print(f"finished in {time.time() - t:.4f} seconds")

Expected behavior
Expect sorting to take the same or less time than flattening and then sorting.
Environment info

datasets version: 2.12.1.dev0 (same with 2.12.0 too)
Platform: Windows-10-10.0.22621-SP0
Python version: 3.10.10
Huggingface_hub version: 0.14.1
PyArrow version: 12.0.0
Pandas version: 2.0.1

Hi ! shard currently returns a slow dataset by default, with examples evenly distributed in the dataset.
You can get a fast dataset using contiguous=True (which should be the default imo):
dataset = dataset.shard(10, 0, contiguous=True)

@lhoestq

contiguous=True (which should be the default imo)

For IterableDataset, it's not possible to implement contiguous sharding without knowing the number of examples in advance, so setting the default value to contiguous=True would result in an inconsistency between Dataset and IterableDataset (when we add IterableDataset.shard)

Actually sharded iterable datasets are made of sub iterables that generally yield contiguous data no ? So in a way it's possible to shard an iterable dataset contiguously.
If the dataset is made of one shard it's indeed not possible to shard it contiguously though

Actually sharded iterable datasets are made of sub iterables that generally yield contiguous data no ? So in a way it's possible to shard an iterable dataset contiguously.

But sharding an iterable dataset by sharding its gen_kwargs would still yield approximate shards(not equal to Dataset.shard), no?

I understand the issue doesn't exist with non-mapped datasets, but if flattening is so much more efficient than sorting the indices, that's an issue in itself.
There are plenty of issues people posted for which the root cause turns out to be the same. It seems like mapped datasets are terribly inefficient. I think I saw some issue like that somewhere (about the mapped datasets in general), but can't find it now.
Maybe indices should be flattened before any additional processing, then.


[BUG] Fix Flaky tests

2x TestCreateNamespaceProjectMember and TestCreateNamespaceProjectOwner
TestSystemChartsVersionSuite/TestInstallWebhookMinVersion
test_project_create_default_role
Additional Info:
ERROR test_default_roles.py::test_cluster_create_role_locked
https://drone-publish.rancher.io/rancher/rancher/9861/6/2
and:
ERROR test_rbac.py::test_member_can_edit_secret
ERROR test_rbac.py::test_readonly_cannot_edit_secret
https://drone-publish.rancher.io/rancher/rancher/9863/6/2
SURE 6453

Note: This issue was due to a different test which caused the webhook to be unavailable during these tests, causing the issue. The test in question was reverted and is currently not being ran.
This issue aims to fix the currently disabled test, so that it can be ran safely alongside these other tests.

Also adding TestCRTBRoleTemplateInheritance to the list.


Add user pytests

Reviewer: @sidravi1
Estimate: 30mins

Ticket
Fixes: 518
Description
Goal
Add pytests for

the api key rotation endpoint
user table functions
content CRUD user overlaps
UD CRUD
user2 token denial for retrieval and UD detect

How has this been tested?

Activate the aaq environment and run make tests in core_backend
Added where to find login credentials to dev docs

Checklist
Fill with x for completed. Delete any lines that are not relevant

[x] My code follows the style guidelines of this project
[x] I have reviewed my own code to ensure good quality
[x] I have tested the functionality of my code to ensure it works as intended
[x] I have resolved merge conflicts
[x] I have updated the automated tests (if applicable)
[x] I have updated the requirements (if applicable)

Hey @sidravi1 @suzinyou  I’ve done my best on adding pytests for the multi-user feature.

All my tests work now but the way async is being handled is making some UD tests fail and I can’t figure it out. Could you guys have a look and let me know if you can find out why it’s failing?
Also, I don’t have much experience with fixtures and pytests so it’s likely there’s a better way to handle the manual user additions that are done right now.

This is not part of this PR but I'm seeing this deprecation warning:

The method "utcnow" in class "datetime" is deprecated
Use timezone-aware objects to represent datetimes in UTC; e.g. by calling .now(datetime.UTC)

Yup, been ignoring it lol added a backlog ticket to fix this


docs: JR-572: Updates Service Registry 'Using Quarkus' with PM+QE fee…

…dback

@smccarthy-ie Made the changes in the RHOSAK+Quarkus doc now, while the changes are still fresh in my mind! Please review again to make sure I caught everything.
@AedinC Will you please review the changes in the RHOSAK+Quarkus doc too, to make sure you're happy with them?


Add AOP to default /dispatch route

Describe the feature
Add the ability to read AOP from dispatch route
Additional Context
No response

Done!


Change name to turf-spatialjoin or turf-spatial-join

Because I don't know what tag is, and this does a spatial join. Thoughts?

The tag name came from a couple other GIS engines I was familiar with that contained this exact same function. "spatial join" is very loaded in my experience, with everyone having a slightly different definition and expectations. I would like to stay away from the "JOIN" phrasing entirely, since people will expect it to be just like SQL, when this not really the same thing. Calling it a spatial join sets the expectation that it does all of this stuff, when it actually does not do any of those things 1:1.
\my 2 cents

Point taken! Closing. :+1: :smile:


fr: add missing translation for distributed-systems (resolves #1973)

Describe your changes
This PR adds the French translation for the distributed-systems concept.
Related issue number or link
Resolves #1973
Checklist before opening this PR

[X] This PR does not contain plagiarism.
[X] I have signed off on all commits

Commit is not signed-off yet due to not being on a laptop where I have my private GPG key. Opening the PR nonetheless to get some early feedback on it :slightly_smiling_face: Will rebase with a signed commit in a couple days.

Rebased and pushed a signed-off commit :heavy_check_mark:


Functional Testing for Groups

Key points:

[ ] Test all the baseline policies
[ ] Test different use cases and edge cases
[ ] For each policy verify if the output as expected when the tests pass/fail
[ ] For policies with multiple settings check that only the expected sub-policy will pass/fail and the other
[ ] dependent/independent policies are unaffected
[ ] Perform tests to verify multiple OU and OU inheritance settings wherever applicable
[ ] Perform tests to verify Group settings wherever applicable
[ ] Report and file bugs for any issues found

Functional testing done as part f reviewing #87

Issue marked done but not closed, closing now.


AMBARI-26232 There will be failure when executing shell.py

What changes were proposed in this pull request?
The shell.py is executed when installing services by ambari.
However, there will be no failure when executing the shell.py because of some syntax error and undefined variables.
This changes will fix the syntax error and undefined variables in shell.py, and make the shell.py work well.
How was this patch tested?
Applying this changes, and manual test
Please review Ambari Contributing Guide before opening a pull request.

@JiaLiangC  Can you take a look when you have time? thanks


Update zio and zio-interop-cats to 1.0.0-RC19

Fixes #174
Fixes #175

This fails as described here https://github.com/sksamuel/pulsar4s/pull/173#issuecomment-626980478

yeah I'm trying to figure out why its hanging in travis.

I have fixed master but there was one test in CatsAsyncHandlerTest that I had to disable as it was failing on a missing method exception. If you have time would you mind taking a look?

Will check :smile:

Thank you :)
On Tue, 19 May 2020 at 04:21, Ciprian Sofronia<EMAIL_ADDRESS>wrote:

Will check 😄
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/sksamuel/pulsar4s/pull/176#issuecomment-630699235,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFVSGRGIT4RAQDHRXZ3EYDRSJFR7ANCNFSM4NDQGJPQ
.

Check #178


mercurial: Adding hg-git breaks builds on darwin

922c5550154a3d6c518279835161757cc1c3a941
This commit breaks anything that uses Mercurial on darwin. With the addition of the pythonPackages.dulwich package the pythonPackages.gevent package is also brought in. With no support for darwin enabled in the gevent package, this causes Mercurial to not build. I would recommend rolling back this commit and keeping hg-git as a separate package, not tied to mercurial itself, if possible, or making the hg-git and dulwich packages only included in the mercurialFull package.

Moved to pull request.


Can't Undo Crop

Version
3.2.0
Development Environment
Browser: Chrome Version 69
OS: macOS
Current Behavior
After cropping an image and then clicking undo, a user cannot undo a crop and the crop rectangle remains and can't be deleted.
Can be reproduced in this example:
http://nhnent.github.io/tui.image-editor/latest/tutorial-example01-includeUi.html
Successfully crop and apply that crop. Then try to undo it. There is no way to remove the crop rectangle unless the entire image is reset.
Expected Behavior
Clicking undo should remove the crop.

This problem is solved.


gradlew does not create build/jpackage

Basic information

My operating system and version: Arch Linux
My mzmine version: 4.0.3

What happened
The README says:
https://github.com/mzmine/mzmine3/blob/777f36db920127fe5819bfbf2e19bf38cfd0d38b/README.md?plain=1#L57-L61
but that does not create a build/jpackage folder.

Nevermind, I found it in mzmine-community/build/jpackage/. Created https://aur.archlinux.org/packages/mzmine3


Support args in cli

This is an example of usage:
oxo scan run --agent agent/ostorlab/nmap --arg ports:8080,8082 ip <IP_ADDRESS>

This pull request will be closed. and new PRs will be created. since some extra cases were discovered during the local testing of this feature.
We will support string, number, and boolean first, and then a new implementation will take place for the array and object cases.


fix(intersection): fixed stuck vehicle detection area

Signed-off-by: Mamoru Sobue<EMAIL_ADDRESS>PR Type

Bug Fix

Related Links
feature fix: https://github.com/autowarefoundation/autoware.universe/pull/2463
Pre-Review Checklist for the PR Author
PR Author should check the checkboxes below when creating the PR.

[X] Code follows coding guidelines
[X] Assign PR to reviewer

Checklist for the PR Reviewer
Reviewers should check the checkboxes below before approval.

[X] Commits are properly organized and messages are according to the guideline
[X] Code follows coding guidelines
[X] (Optional) Unit tests have been written for new behavior
[X] PR title describes the changes

Post-Review Checklist for the PR Author
PR Author should check the checkboxes below before merging.

[X] All open points are addressed and tracked via issues or tickets
[X] Write release notes

CI Checks

Build and test for PR: Required to pass before the merge.
Check spelling: NOT required to pass before the merge. It is up to the reviewer(s). See here if you want to add some words to the spell check dictionary.

Could you fix spell and title?

@shmpwk thx!


[Enhancement] Add OUTPUT command in SQL Changeset and allow option for SQL session output to be redirected

Environment N/A
Liquibase Version: 3.8.x and later
Liquibase Integration & Version: All
Liquibase Extension(s) & Version: N/A
Database Vendor & Version: MS SQL and SAP ASE,
Operating System Type & Version: N/A
Description
As a user of Liquibase I want to be able to emit messages from my SQL code that can be seen in the STDOUT and/or STDERR output these could be session output from SELECT or other statements such as non-fatal messages from (PRINT, SELECT, or RAISERROR (SEVERITY 1-10)) which current do not appear anywhere in the output of a Liquibase session.

Extending the OUTPUT command to support streaming of the session output to the designated stream would allow progress for complex changes to be monitored. This would require an addition stream support to support SESSION capture to STDOUT.
Adding support for the OUTPUT command in sql changesets would also be helpful and would bring SQL more inline with YAML, JSON and XML.

e.g.
--OUTPUT stream:(STDERR|STDOUT|INFO|WARNING|ERROR|SEVERE|SESSION) literal-message-string
Steps To Reproduce
N/A
Actual Behavior
Expected/Desired Behavior

Allow OUTPUT redirection of current SQL session to STDOUT or STDERR
Support for OUTPUT sub-command in SQL Changesets

Screenshots (if appropriate)
Additional Context
┆Issue is synchronized with this Jira Bug by Unito

Thanks @sqlsleuth for writing up this issue.  We will add it to our list of issues to process.


Subtraction for condition objects

This adds c1 - c2 to be defined as c1 and not c2 for condition objects. This seems clear and intuitive to me, and prettier than c1 * (-c2).
My use case looked like condition = tex.in_mathzone - tex.in_command.
EDIT: On deeper thoughts, perhaps this could be confused with c1 + (-c2).

Hey, thank you for the PR :)
I'd agree that this could lead to some confusion, both with +- (as you said), but it might also be confusing to have the unary minus and minus, for pretty different things.
OTOH, weirdly, I do agree that cond1 - cond2 intuitively means cond1 given cond2 does not hold, but I'm not sure where this intuition is coming from, and so am hesitant to add - just based on that :sweat_smile:
Can you think of a reason for this intuition? Maybe a good mnemonic device to put into DOC.md, so it's easy to understand for those who don't think it's intuitive?

The difference of two sets is defined very similarly. A - B (or A \ B) = {a in A | a not in B}.
Moreover, if you want -(a + b) = - a - b, where the unary minus and binary plus are defined as 'not' and 'or', binary minus would have to be defined as above for de Morgan's law to hold (not (a or b) = not a and not b). Also, a - a should obviously be false (0), not always true as a + -a would be.
I don't know if any of these make a good mnemonic.

Ahhh it's probably the set-minus, okay.
Would you address the potential for confusion in the documentation, as well as that mnemonic (and mention that there is some internal inconsistency in the boolean algebra if - is set to either definition (either DeMorgan holds, or A + (-B) = A-B))
Would you also squash the commits into just one?

Does this look fine?
Sorry about all the force-pushing messages. I am learning my way around git.

Force-pushing is necessary if you need to squash the commits. (And it's absolutely fine if you don't expect someone else working on the same branch, which holds for a PR here)
I like the reference to sets :+1:
Implementation also looks good to me :+1:

Thanks for taking a look @atticus-sullivan!
I think the test-failure is due to some weird race-condition I've yet to see during normal usage, but I'll merge once i can verify it myself (am away rn), or CI reports success (or until anyone else can confirm that no test fails, wink wink nudge nudge)

Ah there it is :D
Thank you @bhataktaBhai, a nice addition :)


What is the best way to handle large models?

Hi all,
I was trying to fine-tune GPT-J 6B but I encounter Out Of Memory errors if I use a single-gpu, for non-private training I managed to solve them by using deepspeed but it seems that I cannot use that with opacus or with this codebase. Do you know how I could solve this problem?
Thank you in advance:)

Hi,
Thanks for your interest. I have detailed thoughts on this, but the short answer is that we likely need to make some non-trivial changes to the codebase to enable that (If you have 80G A100 GPUs, things might be easier).
If you're interested in making progress on this, I'm happy to chat in depth via email.
Thanks.

Closing this now.


Remove x/y scaling in EIP1559 calculation

Describe the feature request
From Brecht:

The exp implementation has as input and output values in 10**18 fixed format notation, so exp(0) == 10**18. Let's say that's 1 wei (so plenty of precision). The exp function also works with inputs up till ~135, which will return an enormous number: log10(exp(135)) == 58. The total ETH supply is ~100,000,000 ETH, and 10*18 wei/ETH, so log10(100,000,000*(10**18)) == 26, much smaller than the max value returned by exp.

I don't think it has something to do with value boundaries or accuracy, it's about finding the parameters to shape the curve's slope to ensure that at the initial best-guess price, the 2x/1x basefee ratio is as expected.
I tried but didn't find a way to just use one scaling factor to make it work.

I think the y scaling can be avoided (I haven't done the math, so take with a grain of salt). To target p you would pick some ADJUSTMENT_QUOTIENT (total x scaling is done with TARGET * ADJUSTMENT_QUOTIENT). Then to get gasExcess to target some initial fee, you would just do the inverse basefee calculation:
initial_basefee = 10**8
gasExcess = (TARGET * ADJUSTMENT_QUOTIENT) * math.log(initial_basefee * (TARGET * ADJUSTMENT_QUOTIENT))

I suggest that we keep it as-is to reduce risk. Removing y-scale still ends up with the same number of storage slots that we have to write (1 for now), the only small downside is that we have an extra DIV opcode to be optimized away, it's too small of a gain I think.


[TechDebt] Sync conversations and prompts stores methods

Currently we have different methods for prompts and conversations stores so it will require additional effort to use mostly same logic for this entities - use same names and same behavior to simplify it

and file store mtehods also. E.g. don't request folders and files sepearately when we can make one request for them

Investigate why unselected conversations aren't automatically shown if duplicate


fix: Nuxt Auth cannot register a module in store

🐛 The bug
Nuxt Auth cannot register a module in store, look the devtools
🛠 To reproduce
https://codesandbox.io/s/distracted-platform-hw4xe
🌈 Expected behaviour
Nuxt Auth can register a module for authentification.
ℹ Additional context
Nothing

@MrJmpl3 I think this may be related to #39. The auth module is being correctly registered, it's just not showing up in the devtools. If you click on a component in the devtools Component mode (first tab), and then switch to console, you can verify this:
console.dir($vm0.$store.state.auth)
// loggedIn: false
// strategy: "local"
// user: null

Unfortunately, I believe this to be a bug in the devtools as nuxt-typed-vuex doesn't change, modify or interfere with the Vue store at all (or in other libraries' access to the store) - it only provides an accessor to it.

Left the same comment in the other issue but this is how I managed to fix it:
I was having a similar issue with the store state not getting updated in vue dev tools.  I managed to fix this by doing the following:

In the Vue Dev Tools tab, click on the Settings icon.
Check the box to enable New Vuex Backend.
After restarting the browser, vuex state should now work as designed.

I do @ShaggyTech fix in the example, but auth module registration and store of auth module don't show 😢

@MrJmpl3 i had enabled New Vuex Backend already, but it's not updating for me either.
@danielroe does it work for you?

Also there's similar behavior, when you rehydrate state from a localstorage with this package: https://github.com/robinvdvleuten/vuex-persistedstate
In a console i see, it's rehydrated, but not in devtools. @danielroe is it on the devtools side problem? Can we report it?

@webcoderkz Yes, I believe this is a bug with devtools.


Allas tutorial

1st Allas tutorial

This should be also added to the tutorials section (https://csc-guide-preview.rahtiapp.fi/origin/allas_tutorial/#support/tutorials/)  AND also reference from the tutorial on moving to puhti: https://csc-guide-preview.rahtiapp.fi/origin/allas_tutorial/#support/tutorials/puhti_quick/
Did not read through everything else yet.

The test fail due to manual html anchors, this is ok and we are aware of this.


unwrap_cluster does not reproduce gromacs

unwrap_cluster() does not exactly reproduce what gromacs does with the trajectory. It's not far off but it's a bit different, probably due to different initial molecule. Can be easily tested by a) transforming a pre-transformed trajectory b) calculating e.g. inertia tensor with and without unwrapping on a gromacs clustered trajectory -- should be the same and unwrap should be siltent.
Probably not worth putting loads of time in -- differences are miniscule.

It doesn't matter that much.


Don't create a new scene when double-clicking empty space in scene tabs

Follow-up to https://github.com/godotengine/godot/pull/65302 and https://github.com/godotengine/godot/pull/70800.

This behavior was often accidentally triggered when using the scroll tab arrow buttons. Web browsers also lack equivalent behavior, which means that it's not an UX pattern that people often rely upon.
If you need to create a scene quickly from the scene tabs, a "+" button remains visible at the right of the last scene tab.

This closes https://github.com/godotengine/godot/issues/72313.

Web browsers also lack equivalent behavior, which means that it's not an UX pattern that people often rely upon.

That's not fully accurate, Firefox behaves like this (at least on Linux).
I don't mind removing the feature (I don't use it).

That's not fully accurate, Firefox behaves like this (at least on Linux).

Indeed, this feature exists, or at least existed, in various browsers and tabbed applications. So I think that the feature is fine. But navigation arrows should consume clicks.

That's not fully accurate, Firefox behaves like this (at least on Linux).

I guess it depends on whether you have window borders shown, as doing this on my setup (also Linux) makes the window maximize itself (or restore itself is already maximized).

I think this was fixed in the TabBar itself by #79852

I think this was fixed in the TabBar itself by #79852

I can still reproduce this on 4.2.beta2:
https://github.com/godotengine/godot/assets/180032/6a60f4be-91a2-42a3-822b-4af5e236a2ef

Oh, I meant the linked issue #72313 was fixed, so it doesn't trigger when using the scroll buttons.
I don't know if we still want the double click to create new tabs feature to be removed or not, since that seemed like the main issue with it.