lightning.app.storage.Path tool fails to share a files between works

Bug description
The lightning.app.storage.Path tool fails to share a file from work1 to work2 in the cloud
How to reproduce the bug
import lightning as L
from lightning_app import LightningFlow, LightningWork
from lightning_app.storage.path import Path
import torch
import os

class ModelTraining(LightningWork):
    def __init__(self, *args, **kwargs):
        super().__init__(*args, **kwargs)
        self.checkpoint_dir = "lit://outputs/checkpoints"
        self.best_model = None

    def run(self):
        # create a directory
        os.makedirs(self.model_checkpoints_path, exist_ok=True)
        # make fake checkpoints
        checkpoint_1 = torch.tensor([0, 1, 2, 3, 4])
        torch.save(checkpoint_1, os.path.join(self.checkpoint_dir, "checkpoint_1.ckpt"))
        self.best_model =  os.path.join(self.checkpoint_dir, "checkpoint_1.ckpt")

class ModelDeploy(LightningWork):
    def __init__(self, *args, **kwargs):
        super().__init__()

    def run(self, best_model):
        checkpoint_1 = torch.load(best_model)
        print(checkpoint_1)

class Flow(LightningFlow):
    def __init__(self):
        super().__init__()
        self.train = ModelTraining()

        # pass the checkpoint path
        self.deploy = ModelDeploy()

    def run(self):
        self.train.run()
        self.deploy.run(self.train.best_model)

app = L.LightningApp(Flow())

## Requirements.txt:

torchvision==0.13.0
jsonargparse[signatures]
wandb==0.12.16
pyyaml==5.4.0
protobuf<4.21.0
lightning_hpo
websockets
lightning

## in terminal
lightning run app app.py --cloud

Error messages and logs
[root.deploy] 2022-10-07T21:57:35.339Z /usr/local/lib/python3.8/dist-packages/pkg_resources/init.py:123: PkgResourcesDeprecationWarning: 0.23ubuntu1 is an invalid version and will not be supported in a future release
[root.deploy] 2022-10-07T21:57:35.339Z   warnings.warn(
[root.deploy] 2022-10-07T21:57:35.343Z Traceback (most recent call last):
[root.deploy] 2022-10-07T21:57:35.343Z     sys.exit(main())
[root.deploy] 2022-10-07T21:57:35.343Z   File "/home/zeus/.local/lib/python3.8/site-packages/click/core.py", line 1130, in call
[root.deploy] 2022-10-07T21:57:35.343Z     return self.main(*args, **kwargs)
[root.deploy] 2022-10-07T21:57:35.343Z   File "/home/zeus/.local/lib/python3.8/site-packages/click/core.py", line 1055, in main
[root.deploy] 2022-10-07T21:57:35.343Z     rv = self.invoke(ctx)
[root.deploy] 2022-10-07T21:57:35.343Z   File "/home/zeus/.local/lib/python3.8/site-packages/click/core.py", line 1657, in invoke
[root.deploy] 2022-10-07T21:57:35.343Z     return _process_result(sub_ctx.command.invoke(sub_ctx))
[root.deploy] 2022-10-07T21:57:35.343Z   File "/home/zeus/.local/lib/python3.8/site-packages/click/core.py", line 1657, in invoke
[root.deploy] 2022-10-07T21:57:35.343Z     return _process_result(sub_ctx.command.invoke(sub_ctx))
[root.deploy] 2022-10-07T21:57:35.343Z   File "/home/zeus/.local/lib/python3.8/site-packages/click/core.py", line 1404, in invoke
[root.deploy] 2022-10-07T21:57:35.343Z     return ctx.invoke(self.callback, **ctx.params)
[root.deploy] 2022-10-07T21:57:35.343Z   File "/home/zeus/.local/lib/python3.8/site-packages/click/core.py", line 760, in invoke
[root.deploy] 2022-10-07T21:57:35.343Z     return __callback(*args, **kwargs)
[root.deploy] 2022-10-07T21:57:35.343Z   File "/home/zeus/.local/lib/python3.8/site-packages/lightning_launcher/cli/main.py", line 86, in run_work
[root.deploy] 2022-10-07T21:57:35.343Z     run_lightning_work(
[root.deploy] 2022-10-07T21:57:35.343Z   File "/home/zeus/.local/lib/python3.8/site-packages/lightning_launcher/utils.py", line 49, in wrapper
[root.deploy] 2022-10-07T21:57:35.343Z     res = func(*args, **kwargs)
[root.deploy] 2022-10-07T21:57:35.343Z   File "/home/zeus/.local/lib/python3.8/site-packages/lightning_launcher/utils.py", line 73, in wrapper
[root.deploy] 2022-10-07T21:57:35.343Z     res = func(*args, **kwargs)
[root.deploy] 2022-10-07T21:57:35.343Z   File "/home/zeus/.local/lib/python3.8/site-packages/lightning_launcher/launcher.py", line 145, in run_lightning_work
[root.deploy] 2022-10-07T21:57:35.343Z     WorkRunner(
[root.deploy] 2022-10-07T21:57:35.343Z   File "/home/zeus/.local/lib/python3.8/site-packages/lightning_app/utilities/proxies.py", line 316, in call
[root.deploy] 2022-10-07T21:57:35.343Z     raise e
[root.deploy] 2022-10-07T21:57:35.343Z   File "/home/zeus/.local/lib/python3.8/site-packages/lightning_app/utilities/proxies.py", line 299, in call
[root.deploy] 2022-10-07T21:57:35.343Z     self.run_once()
[root.deploy] 2022-10-07T21:57:35.343Z   File "/home/zeus/.local/lib/python3.8/site-packages/lightning_app/utilities/proxies.py", line 437, in run_once
[root.deploy] 2022-10-07T21:57:35.343Z     self.work.on_exception(e)
[root.deploy] 2022-10-07T21:57:35.343Z   File "/home/zeus/.local/lib/python3.8/site-packages/lightning_app/core/work.py", line 537, in on_exception
[root.deploy] 2022-10-07T21:57:35.343Z     raise exception
[root.deploy] 2022-10-07T21:57:35.343Z   File "/home/zeus/.local/lib/python3.8/site-packages/lightning_app/utilities/proxies.py", line 402, in run_once
[root.deploy] 2022-10-07T21:57:35.343Z     ret = work_run(*args, **kwargs)
[root.deploy] 2022-10-07T21:57:35.343Z   File "untitled/app_script_V1.py", line 28, in run
[root.deploy] 2022-10-07T21:57:35.343Z     checkpoint_1 = torch.load(best_model)
[root.deploy] 2022-10-07T21:57:35.343Z   File "/home/zeus/.local/lib/python3.8/site-packages/torch/serialization.py", line 699, in load
[root.deploy] 2022-10-07T21:57:35.343Z     with _open_file_like(f, 'rb') as opened_file:
[root.deploy] 2022-10-07T21:57:35.343Z   File "/home/zeus/.local/lib/python3.8/site-packages/torch/serialization.py", line 230, in _open_file_like
[root.deploy] 2022-10-07T21:57:35.343Z     return _open_file(name_or_buffer, mode)
[root.deploy] 2022-10-07T21:57:35.343Z   File "/home/zeus/.local/lib/python3.8/site-packages/torch/serialization.py", line 211, in init
[root.deploy] 2022-10-07T21:57:35.343Z     super(_open_file, self).init(open(name, mode))
[root.deploy] 2022-10-07T21:57:35.343Z FileNotFoundError: [Errno 2] No such file or directory: '/content/.storage/outputs/checkpoints/checkpoint_1.ckpt'
Environment
#
#- Lightning Component: LightningFlow, LightningWork, LightningApp, lightning_app.storage.path
#- Lightning App Version: 0.6.3 (cloud)
#- PyTorch Version:  torch-1.12.0 (cloud)
#- Python version: 3.8.3 (Cloud)
#- How you installed Lightning: pip (locally)
#- Running environment of LightningApp (e.g. local, cloud): cloud

More info
The code works perfect locally

@tchaton


[POC] Transfer Multi Denom Support

Description

closes: #XXXX
Commit Message / Changelog Entry
type: commit message

see the guidelines for commit messages. (view raw markdown for examples)

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against the correct branch (see CONTRIBUTING.md).
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Code follows the module structure standards and Go style guide.
[ ] Wrote unit and integration tests.
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/).
[ ] Added relevant godoc comments.
[ ] Provide a commit message to be used for the changelog entry in the PR description for review.
[ ] Re-reviewed Files changed in the Github PR explorer.
[ ] Review Codecov Report in the comment section below once CI passes.

Codecov Report
Attention: 11 lines in your changes are missing coverage. Please review.

Comparison is base (310a4bd) 81.49% compared to head (c956367) 81.51%.
Report is 9 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #5763      +/-   ##
==========================================
+ Coverage   81.49%   81.51%   +0.02%
==========================================
  Files         199      200       +1
  Lines       15203    15285      +82
==========================================
+ Hits        12389    12460      +71
- Misses       2348     2357       +9
- Partials      466      468       +2

Files
Coverage Δ

modules/core/04-channel/keeper/keeper.go
90.84% <100.00%> (+0.06%)
:arrow_up:

modules/core/04-channel/keeper/upgrade.go
92.52% <100.00%> (+0.21%)
:arrow_up:

modules/apps/transfer/v2/transferv2.go
92.45% <92.45%> (ø)

modules/apps/transfer/types/packet.go
79.16% <0.00%> (-13.52%)
:arrow_down:

Should this remain open if the work has been moved to the feature branch? Took me a bit to realize these weren't the latest changes

This is will superseded by the PR from https://github.com/cosmos/ibc-go/tree/feat/ics20-v2.


Unordered list characters (bullets) don't appear

Examples are: Changelog, Privacy Policy, and more
Some CSS rules hide these bullets

https://trackmyindoorworkout.github.io/privacy/
https://trackmyindoorworkout.github.io/changelog/
It'd be great to treat this site-wide


⚠ Bofrost.lu has degraded performance

In 2c537e8, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 2147 ms

Resolved: Bofrost.lu performance has improved in ce65e9e.


move proof verification logic into libraries

🟡 Heimdall Review Status

Requirement
Status
More Info

Reviews

🟡
0/1

Denominator calculation

Show calculation

1 if user is bot
0

1 if user is external
0

From .codeflow.yml

1

Additional review requirements

Show calculation

Max
0

0

From CODEOWNERS

0

Global minimum
0

Max

1

1

1 if commit is unverified
0

Sum
1


Null is not the same as unset

There's an issue with the object processor:
Arg•1 Chevere\Tests\_resources\DummyClass#76
public public null
public readonly readonly null
private private null
private protected null
private circularReference null
private deep null

final class DummyClass
{
    public object $public;

    public readonly string $readonly;

    private object $private;

    private object $protected;

    private object $circularReference;

    private object $deep;
}

DummyClass has these properties unset, so either indicate "unset" or simply don't populate unset variables.

Already does this since https://github.com/chevere/var-dump/commit/35c08c865d6df7dcb52e7f0ed417727e7051ab62


Fixe issue sanitizing attributions

reviewer @xavijam

I miss a test ;)

cc @xavijam This fix works both on cartodb.js standalone and editor. But we need to talk about an strange issue on layer models construction.

any news with this.

Could you cc rest of frontend guys explaining the problem you want to solve please?

cc @javierarce @alonsogarciapablo @viddo @xavijam
This PR tries to salve an issue with sanitization. It is simply but has an impact in the way we coding until now.
Whats the problem?
Right now we load data as it comes from user (editor) or vizjson and sanitizes the attribute to be use when it is going to be used, ie. tooltips, legends, etc. That is, the data is wrapped in a xxxModel class and data is accesed using this.model.get('someAttrib').
In addition, on the editor implementation, for models, there are a subclass that extends or modifies the parent functionality. For example, cdb.geo.map.CartoDBLayer has its corresponsing subclass cdb.admin.CartoDBLayer. In the editor, data is also accessed using  this.model.get('someAttrib').
The main problem is we need to sanitise any attribute susceptible to be sanitized all time we are going to retrieve it.
The solution proposed
Sanitize data when it is set in the model so it was valid when we need to use it.
If the idea is to wrap the literal data into a model class, the solution is to sanitize the attributes susceptibles to be sanitized when: 1)model is created from a literal object or 2) when an attribute is set.
Because the initial problem is reported with attribution property, I have modified the top most common class that works with attribution, the cdb.geo.map.MapLayer class, from which all other layer model classes inherits.
So a have override the set method to do the sanitization taks. For the moment only on the attribution property but I think it could be made on other properties like template.
Note: With this solution, only cartodb.js need to be updated. Otherwise, if we sanitize when attribs are used, I need to modify too cartodb-editor.
Waiting for your opinions.

I don't think this is the way to go. Sanitizing is a concern on the output, what kind of escaping is necessary depends on where it's going to be presented.

If there aren't more opinions I consider this a :-1:  :( So I close the PR and work solving the bug in another way.


missingmethodexception

i get this for some reasone "[Error  : Unity Log] MissingMethodException: UnityEngine.GameObject[] EffectList.Create(UnityEngine.Vector3,UnityEngine.Quaternion,UnityEngine.Transform,single)
Stack trace:
(wrapper dynamic-method) Player.DMDPlayer::Update(Player) "

Sorry, that is not really helpful. Please use the bug report template and provide the needed information.


feat(require): bind multiple events with single common handler

I was browsing through the Ractive documentation and saw

...

and I thought that
data-on-childevent1-childevent2-....="parentevent"

data-listen-childevent1-childevent2-...="parentevent"

could also be possible.
Here's a sample on how I use it:
<rv-require name="dataList"
            src="widgets/data-list"
            data-title="等級色分類"
            data-addbtnlabel="追加・変更"
            data-sortable="false"
            data-on-resetdata-cleardata="clear-list-data"
            data-listen-clearselected-resetrange="clear-ranges"></rv-require>

Thanks again @frostbane!
Please can you follow the coding style?
name.split('-').forEach(function(eventName) {
  if (eventName.trim()) {
    events[eventName] = attr.value;
  }
});

I have updated the documentation with your work :wink:
http://dev.ractiverequire.com/#events

I have refactored the code.

Sorry sorry but a if, even in single ligne needs its brackets. :sweat_smile:
if (eventName.trim()) {
  events[eventName] = attr.value;
}

(I prefer to let you correct that to add commits after your work :wink:)

(And strings are always in ' instead of ")
More on the JSCS rules


Feature Request: Support for Apple M1

Since Apple is migrating their entire lineup to the M1 processor, it would be nice if we could get M1 support for this provider. Thanks!

Looks like they started releasing for M1s in V1.0.9


Explore export of metadata to other standard formats (JSON-LD)

@mianzg: when you develop the package, please also include a brief review of this: https://github.com/openwashdata-dev/book/issues/13#issuecomment-1621165618

Please review and close/raise issue for washr, @larnsce.

transferred


Article on "Build, Test, and Publish a Docker Image for a sample React application"

Signed-off-by: Dhrubajyoti Chakraborty<EMAIL_ADDRESS>Summary
This PR contains an article on Build, Test, and Publish a Docker Image for a sample React application that helps the user to get started with a sample Harness workflow for an React application hosted under harness-community.

Created a new folder section ci-react-quickstart under ./tutorials/build-code/static/ to store the static image files
Added one file ci-react-quickstart.md

What Type of PR is This?

[x] Tutorials

HouseKeeping
Some items to keep track of. Screenshots of changes are optional but would help the maintainers review quicker.

[x] Tested Locally
[x] Optional Screen Shoot.

Preview environment: https://ci.pr.harness.io/pr-309

@codewdhruv thanks for the PR. A few items.

Can you un-commit the yarn.lock file in the root of the project?
Can you add tiles specifically to the /src/components/landingpage -> AllTutorials.tsx and ContinuousIntegration.tsx.

As a general heads up, this one is pretty similar to The JAVA HTTP one, minus the app.

Preview environment: https://ci.pr.harness.io/pr-309

changes added @ravilach

Preview environment: https://ci.pr.harness.io/pr-309

Preview environment: https://ci.pr.harness.io/pr-309


UnexpectedApiError on viewer

https://huggingface.co/datasets/RepoFusion/Stack-Repo/viewer/bm25_contexts

Error code:   UnexpectedApiError

From the logs (internal) we see two error responses:

https://datasets-server.huggingface.co/statistics?dataset=RepoFusion%2FStack-Repo&config=bm25_contexts&split=train

{"error":"IO Error: No files found that match the pattern \"/storage/stats-cache/72194527872800-split-descriptive-statistics-RepoFusion-Stack-Rep-0ab447b7/bm25_contexts/train/*.parquet\""}

https://datasets-server.huggingface.co/rows?dataset=RepoFusion%2FStack-Repo&config=bm25_contexts&split=train&offset=0&length=100

{"error":"Unexpected error."}

due to
libcommon.parquet_utils.TooBigRows: Rows from parquet row groups are too big to be read: 308.26 MiB (max=286.10 MiB)

Same errors for https://huggingface.co/datasets/deepmind/code_contests/viewer/default/train?p=1

https://datasets-server.huggingface.co/statistics?dataset=deepmind%2Fcode_contests&config=default&split=train

{"error":"IO Error: No files found that match the pattern \"/storage/stats-cache/10704050661432-split-descriptive-statistics-deepmind-code_contes-d4a66b3c/default/train/*.parquet\""}

https://datasets-server.huggingface.co/rows?dataset=deepmind%2Fcode_contests&config=default&split=train&offset=100&length=100

{"error":"Unexpected error."}

log:
libcommon.parquet_utils.TooBigRows: Rows from parquet row groups are too big to be read: 381.36 MiB (max=286.10 MiB)

Just launched the recreation of these two datasets.
https://huggingface.co/datasets/RepoFusion/Stack-Repo is now disabled because of the dataset script.
https://huggingface.co/datasets/deepmind/code_contests ...

-> JobManagerCrashedError


terraform creating terraform-provider file in temp folder, how to remove via build pipeline run

using task to perform terraform

after build pipeline complete will remain terraform-provider file left in agent machine

how to remove via pipeline or manually only to be remove?
due to this agent machine drive is getting full

Hi, thanks for reporting. We will take a look at this.

@mericstam
Do we have an estimate on when this bug will be resolved?
@manishlak,
May I please know if this is sorted? Any workaround?

After investigaing some: this is an issue with terraform CLI on windows machines
https://github.com/hashicorp/terraform/issues/28477
So nothing to do with the extension code.
As a workaround I would delete the files with a separate script task after terraform deploy is done
br
Manuel

Thanks @mericstam for the confirmation.

Closing this as it is not related to extension code.


are there any papers related to the library?

Yes, the paper will be presented at this year RSS.

Not yet. It will be released along with the other RSS2018 papers, and we will link to it in this repo once that happens.

Please see http://arxiv.org/abs/1805.07703


Dummy App

WORK IN PROGRESS
in preparation for #5

So it seems to work in general, but no CSS gets loaded, any idea why @courajs

I’m trying to setup acceptance test, but looks like it cannot connect to Hoodie. Might it be something with the ports?

I think `server/index

I think server/index and serverMiddleware are meant mainly for development, not test. Usually ajax calls are mocked out in test with pretender or similar. I haven't looked into how we would get the server running in test yet

No reason off the top of my head the css wouldn't load, I'd have to dig into it.

Closing in favor of #16


Could you help me understand why we need to drop all index of 'clas' collection and recreate again?

The code snippets here and here are a little bit confusing for me. Could you help me understand why we need to drop all index and recreate again? Why only 'repos' and 'clas' collections need to recreate index? Can I just keep the previous index as it is?

Hi Michael,
I've updated the indexes as reaction to the bug reported by @splix in his comment on the issue #264 The problem was, that a repository can be deleted and newly created with the same name. If the deleted repo was already linked in CLA assistant, then we select and check not unique signatures and repositories without considering the repoId.


add theme-color for better Android browser integration

Same fix as for core: https://github.com/owncloud/core/pull/17965
Please review @owncloud/designers @jospoortvliet

If you say so... I'm good with it ;-)

:+1:


ngx_pagespeed/src/log_message_handler.cc error on FreeBSD

While I compiling the ngx_pagespeed module with nginx 1.8.0 on FreeBSD 10.2 RELEASE ports, I get some error on ngx_pagespeed/src/ngx_pagespeed/src/log_message_handler.cc:

-o objs/addon/src/log_message_handler.o  /usr/ports/www/nginx/work/ngx_pagespeed/src/log_message_handler.cc
/usr/ports/www/nginx/work/ngx_pagespeed/src/log_message_handler.cc:102:3: error:
reference to 'log' is ambiguous
log = log_in;
^
/usr/include/math.h:251:8: note: candidate found by name lookup is 'log'
double  log(double);
^
/usr/ports/www/nginx/work/ngx_pagespeed/src/log_message_handler.cc:41:12: note:
candidate found by name lookup is '::log'
ngx_log_t* log = NULL;
^
/usr/ports/www/nginx/work/ngx_pagespeed/src/log_message_handler.cc:107:7: error:
reference to 'log' is ambiguous
if (log->log_level >= NGX_LOG_DEBUG) {
^
/usr/include/math.h:251:8: note: candidate found by name lookup is 'log'
double  log(double);
^
/usr/ports/www/nginx/work/ngx_pagespeed/src/log_message_handler.cc:41:12: note:
candidate found by name lookup is '::log'
ngx_log_t* log = NULL;
^
/usr/ports/www/nginx/work/ngx_pagespeed/src/log_message_handler.cc:107:7: error:
unknown type name 'log'
if (log->log_level >= NGX_LOG_DEBUG) {
^
/usr/ports/www/nginx/work/ngx_pagespeed/src/log_message_handler.cc:107:10: error:
cannot use arrow operator on a type
if (log->log_level >= NGX_LOG_DEBUG) {
^
/usr/ports/www/nginx/work/ngx_pagespeed/src/log_message_handler.cc:107:10: error:
variable declaration in condition must have an initializer
5 errors generated.
*** Error code 1

Stop.
make[3]: stopped in /usr/ports/www/nginx/work/nginx-1.8.0
*** Error code 1
Stop.
make[2]: stopped in /usr/ports/www/nginx/work/nginx-1.8.0
*** Error code 1
Stop.
make[1]: stopped in /usr/ports/www/nginx
*** Error code 1
Stop.
make: stopped in /usr/ports/www/nginx

ngx_pagespeed doesn't currently support BSD because it depends on PSOL which also doesn't support BSD.  So even if we fix these issues around log you're still not going to be able to run ngx_pagespeed without a lot of additional work.
To follow this, please subscribe to https://github.com/pagespeed/mod_pagespeed/issues/1073


Pixhawk + Raspberry Pi 4 + Mavsdk autonomous flight error

Hi, can anybody help me this out? I'm trying to make a flight with pixhawk orange cube and raspberry pi 4 via mavsdk. I can connect pi and pixhawk with usb cable and connect serial ttyACM0, I can arm the drone but this error comes up immediately. Any idea?

Looks like mavsdk_server is not running. Do you have mavsdk_server installed on your system (it should have come with pip install somewhere)? If yes, can you try to start it manually to confirm that it works?

we solved the server problem but now there is another problem while setting the takeoff altitude. Any idea ?@JonasVautherin

@julianoes: Could that be related to recent changes in the parameters handling in MAVSDK?

I didnt get what you mean and also the MultiThreadRandezvous error still occurs some time to time without changing anything

@erdoski what is the mavsdk_server version that you're using? Do you build it yourself or use the one that comes with the pip install?

pi@raspberrypi-MP:~/backup_jai $ python buster_dronekit_test.py --connect /dev/ttyAMA1 --baud 921600
/dev/ttyAMA1
921600
Connecting to vehicle on: /dev/ttyAMA1
A Mode: ALT_HOLD
indoors
prearm_check: 0
B Mode: ALT_HOLD
ARM
Vehicle is ready for arm
Wait for drone to transit to arm
vehicle is now armed.
Propellers are spinning
Wait for drone to transit to disarm
Wait for drone to transit to disarm
Wait for drone to transit to disarm
close
End of python test script
Time take: 29.08
pi@raspberrypi-MP:~/backup_jai $ ~/.local/lib/python3.7/site-packages/mavsdk/bin/mavsdk_server serial:///dev/ttyAMA1:921600
[03:57:59|Info ] MAVSDK version: v1.2.0 (mavsdk_impl.cpp:28)
^C
just to check is mavsdk ready in python 3.7? I cannot get it to work.
I am sure my hardware serial port is correct as I can use it with dronekit.

finally, I am able to get mavsdk server 1.4.9 to work with Arducopter. both the below works. command line, the server takes about 20-30 secs to return the connection. Python, the connection is faster. I am not sure which server version onwards work. last week, decided to try again. upgrade the mavsdk.
pip3 install --user --upgrade mavsdk
Successfully installed grpcio-1.59.0 mavsdk-1.4.9
~/.local/lib/python3.9/site-packages/mavsdk/bin/mavsdk_server serial:///dev/ttyAMA1:921600
and
python3 bullseye_mavsdk_test_2.py
async def run():
# Init the drone
#UART 4
print(f"System server b4")
drone = System()
print(f"System server done")
await drone.connect(system_address="serial:///dev/ttyAMA1:921600")
print("Waiting for drone to connect...")
async for state in drone.core.connection_state():
    if state.is_connected:
        print(f"Drone discovered!")
        break

info = await drone.info.get_version()
print(info)

if name == "main":
# Run the asyncio loop
asyncio.run(run())
[11:42:20|Info ] MAVSDK version: v1.4.17 (mavsdk_impl.cpp:20)
[11:42:20|Info ] Waiting to discover system on serial:///dev/ttyAMA1:921600... (connection_initiator.h:20)
[11:42:20|Debug] New: System ID: 1 Comp ID: 1 (mavsdk_impl.cpp:496)
[11:42:20|Debug] Component Autopilot (1) added. (system_impl.cpp:377)
[11:42:20|Warn ] Vehicle type changed (new type: 2, old type: 0) (system_impl.cpp:225)
[11:42:20|Debug] Discovered 1 component(s) (system_impl.cpp:578)
[11:42:20|Info ] System discovered (connection_initiator.h:63)
[11:42:20|Info ] Server started (grpc_server.cpp:53)
[11:42:20|Info ] Server set to listen on <IP_ADDRESS>:50051 (grpc_server.cpp:54)
[11:42:25|Debug] MAVLink: critical: PreArm: Throttle below failsafe (system_impl.cpp:250)
[11:42:25|Debug] MAVLink: critical: PreArm: Hardware safety switch (system_impl.cpp:250)
[11:42:25|Debug] MAVLink: critical: PreArm: Battery 1 below minimum arming voltage (system_impl.cpp:250)
and
System server b4
System server done
Waiting for drone to connect...
Drone discovered!
Version: [flight_sw_major: 4, flight_sw_minor: 3, flight_sw_patch: 0, flight_sw_vendor_major: 52, flight_sw_vendor_minor: 51, flight_sw_vendor_patch: 57, os_sw_major: 0, os_sw_minor: 0, os_sw_patch: 0, flight_sw_git_hash: 313762383 , os_sw_git_hash:<PHONE_NUMBER>65363 ]

You might have to set the rate of the battery message:
http://mavsdk-python-docs.s3-website.eu-central-1.amazonaws.com/plugins/telemetry.html#mavsdk.telemetry.Telemetry.set_rate_battery

set the rate of the battery message

Thank you, this code work with Arducopter 4.3.0.
async def run():
    # Init the drone
    #UART 4
    print("System server b4")
    drone = System()
    print("System server done")
    await drone.connect(system_address="serial:///dev/ttyAMA1:921600")

    drone.telemetry.status_text() #Subscribe to ‘status text’ updates.
    await asyncio.sleep(1)
    status_text_task = asyncio.ensure_future(print_status_text(drone))

    print("Pi4B Waiting for drone to connect...")
    async for state in drone.core.connection_state():
        if state.is_connected:
            print("-- Connected to drone!")
            break

    info = await drone.info.get_version()
    print(info)

    # Start the tasks
    await drone.telemetry.set_rate_battery(1) #1hz
    await asyncio.sleep(1)
    telem_battery = asyncio.ensure_future(print_battery(drone))

    print("-- Arming")
    #await drone.action.arm()

    print("-- Taking off")
    #await drone.action.takeoff()

    print("-- Landing")
    #await drone.action.land()

    await asyncio.sleep(3)
    status_text_task.cancel()
    await asyncio.sleep(3)
    telem_battery.cancel()

async def print_status_text(drone):
    try:
        async for status_text in drone.telemetry.status_text():
            print(f"Status: {status_text.type}: {status_text.text}")
    except asyncio.CancelledError:
        print("print_status_text CancelledError")
        return

async def print_battery(drone):
    try:
        async for battery in drone.telemetry.battery():
            print(f"Battery: {battery.remaining_percent}")
            print(f"Battery_v: {battery.voltage_v}")
    except asyncio.CancelledError:
        print("print_battery CancelledError")
        return

if __name__ == "__main__":
    asyncio.run(run())


MTL-1954 Fix bootloader test

Summary and Scope
Summarize what has changed. Explain why this PR is necessary. What is impacted? Is this a new feature, critical bug fix, etc?
The bootloader test was refactored to restrict testing to only validating that grub.cfg is in alignment and that the initrd and kernel artifacts exist.
Examples:
When everything is kosher:

The disk's kernel exists and is validated.
The disk's initrd was validated. The initrd name in GRUB's configuration exists on the filesystem and is a proper CPIO archive.

When just the kernel is missing:
kernel missing at /metal/recovery/boot
The disk's initrd was validated. The initrd name in GRUB's configuration exists on the filesystem and is a proper CPIO archive.
The disk bootloader will not work and is broken.

When the initrd is missing:
The disk's kernel exists and is validated.
Grub expects /metal/recovery/boot/initrd but it did not exist!
No initrd was found in the bootloader; [/metal/recovery] is missing an initrd!
The original initrd exists [/squashfs/initrd.img.xz].
The errors that were found will prevent the disk bootloader from working.
The disk bootloader will not work and is broken.

When the kernel and initrd are missing:
kernel missing at /metal/recovery/boot
Grub expects /metal/recovery/boot/initrd but it did not exist!
No initrd was found in the bootloader; [/metal/recovery] is missing an initrd!
The original initrd exists [/squashfs/initrd.img.xz].
The errors that were found will prevent the disk bootloader from working.
The disk bootloader will not work and is broken.

When the kernel and initrd are missing, and the dependent initrd needed by cloud-init is missing so the built image is technically bad:
kernel missing at /metal/recovery/boot
Grub expects /metal/recovery/boot/initrd but it did not exist!
No initrd was found in the bootloader; [/metal/recovery] is missing an initrd!
The original initrd is also missing [/squashfs/initrd.img.xz].
The errors that were found will prevent the disk bootloader from working.
The disk bootloader will not work and is broken.

Missing a call to invoke the test.
Another part of the problem was we never were invoking the previous tests.

Backported to 1.3 via #397

Looks good. Do we have a doc for remediation? If so, should link it here on error.

No, if it's wrong then something more serious is wrong like a bad image, bad image customization, or a cloud-init failure. I'll add a message detailing this to the error cases.


Ectoplasm Composter recipes missing

Missing recipes, item type and block information (using hwyla) of Ectoplasm Composter

Put ectoplasm into a non-empty composter.

Put ectoplasm into a non-empty composter.


IE hack issue

I tried to use IE 10 css hack by Jeff Clayton:
/* only works in IE 10 */
_:-ms-lang(x), .selector { property:value\9; }

My real input CSS:
/* IE 10 special css */
_:-ms-lang(x), @-ms-viewport {
  width: auto\9 !important;
}

Expected output:
_:-ms-lang(x),@-ms-viewport{width:auto\9!important}

But real output is empty.
I use clean-css through Minify package for Sublime Text (it uses clean-css directly).
Command line parameters: --s0 -s --skip-rebase
Latest version of clean-css (now is v3.3.1) on Windows 8.1 Pro x64.

@thekondrashov it seems to be lost somewhere during parsing process

outline: thin dotted \9; /* IE6-9 */
get's parsed as
outline: thing dotted;

I'm having the same issue, but in my case it's completely removing the line. I'm using this in my grunt build.
cssmin: {
  build: {
    options: {
      compatibility: '*,-properties.ieSuffixHack'
    },
    files: {
      'assets/styles/global.css': 'assets/styles/global.cs'
    }
  }
}

input {
background: #fff;
line-height: 1 \9;
}

outputs:
input {
background: #fff;
}

Seems like two different bugs, one with selector parsing, the other with value parsing. Stay tuned, fix is coming.

Thank you.

Fixed in 3.3.2.

Gave this another try by updating grunt-contrib-cssmin but no luck. IE9 hacks still getting removed.

grunt plugin is apparently still at version 3.1.x - I've opened an issue so it hopefully gets fixed soon: https://github.com/gruntjs/grunt-contrib-cssmin/issues/228

Thanks.


Consider creating a "delete-problem" command to ramp-database

When using the add-problem ramp-database command (or  ramp setup deploy-event) it creates a problem in DB.
There is a command to delete an event: delete-event but not to delete a problem.
I propose to add a delete-problem command to ramp-database to remove a problem from "problems" in DB.

would be great yes ! do you want to give it a shot?

Message ID: @.***>


Support for Dependency Injection

It would be nice if users could perform dependency injection and/or use non-default constructors to create objects. This would likely require moving off of espresso.

We have moved off of espresso. This could be implemented with a ConfigurableInstanceFactoryScanner that looks for @Inject or similar.


Training loss NaN

Thanks for your awesome work.
I'm trying to reproduce your results for distilling SD-XL. I ran bash examples/train/distill_xl.sh on an 8 - GPU machine. It has been running normally for 25 epochs, with more than 260,000 steps. However, the loss has always been NaN, as shown below:
step_loss: nan, step_loss_noise: nan, step_loss_kd: nan, step_loss_feat: nan
The only modification I made was changing certain lines to ensure the script runs properly. The modified code is as follows:
# Convert images to latent space
with torch.no_grad():
    latents = vae.encode(
        batch["image"].to(accelerator.device, dtype=weight_dtype)
    ).latent_dist.sample()
    latents = latents * vae.config.scaling_factor
    latents = latents.to(accelerator.device, dtype=weight_dtype)

Are there any parameters that should be adjusted? Could you provide your training loss curve or training log?
Looking forward to your reply.

Dear @NSun-S ,
Thanks for your interest in our work! We actually only run 100,000 steps and have not run so long in fact. If there is a problem for a longer training, I suggest trying bfloat16 data type or first training without loss_kd and loss_feat for about 50,000 steps and then adding these loss terms.
Please let us know if the problem persists.

Dear @NSun-S ,
Thanks for your interest in our work! We actually only run 100,000 steps and have not run so long in fact. If there is a problem for a longer training, I suggest trying bfloat16 data type or first training without loss_kd and loss_feat for about 50,000 steps and then adding these loss terms.
Please let us know if the problem persists.

Thanks for your reply. I have attempted to use bf16, and it seems that all three kinds of losses are computed normally.
I will check the performance after training :)


Add a warning banner for outdated docs pages

We've had a couple of people looking at outdated docs, having come from Google, without realising.
A warning banner would probably help with this.
A good example is the SQLAlchemy docs: https://docs.sqlalchemy.org/en/14/

i would like to work on this issue can you please assign it to me ?

You're welcome to give it a go!

@Mause Please let me know if there are any other tasks or issues I can help with.

To add to this, maybe we should also add a similar banner to the dev version of the docs to indicate that content on this page might not be available on the latest release.
And perhaps we should not default to dev version of the docs, unless it's the only version available.

Related to #1732

This will be done when rolling out the next design for the docs. We do the project management for the docs in Trello, so I'm closing this issue to avoid duplication.


fix #189 and fix #197: support non-titled commits and markdown in EDITOR

Codecov Report

Merging #199 into master will increase coverage by 0.02%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #199      +/-   ##
==========================================
+ Coverage   71.06%   71.08%   +0.02%
==========================================
  Files          39       39
  Lines        1980     1982       +2
==========================================
+ Hits         1407     1409       +2
  Misses        433      433
  Partials      140      140

Impacted Files
Coverage Δ

internal/git/edit.go
79.41% <100%> (+0.62%)
:arrow_up:

Continue to review full report at Codecov.

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


Move imports in stream component

Description:
Moved import from function to top-level as requested in #27284
Related issue (if applicable): #27284
Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[x] I have followed the [development checklist][dev-checklist]

I suspect this is the cause of google_assistant component now suddenly needing "av" component. It will pull in camera, which will pull in stream which in turn pulls in av.

Fix in #27935


fix:Added missing keywords in artifacthub-pkg.yml

datadog-service does not shows up in keptn integration page under observability and SLI section.
Signed-off-by: Tarang Verma<EMAIL_ADDRESS>

This PR is related to the issue
https://github.com/keptn-sandbox/datadog-service/issues/75


pause and unpause

I do not understand how to add the dowloadable pause/unpause extension that is documented in (https://craig.is/killing/mice) Mousetrap.
How does the code get inserted in the .js file?
Bob Abarbanel
<EMAIL_ADDRESS>

Hello
Just download this file that you save in your project /Web site as
mousetrap-pause.min.js
https://raw.githubusercontent.com/ccampbell/mousetrap/master/plugins/pause/mousetrap-pause.min.js
And then in the page where you want to use it, just after the line where
you download mousetrap.js add a script tag to download it.
It should look like this:

Le lun. 14 mars 2016 21:59, bobabarbanel<EMAIL_ADDRESS>a
écrit :

I do not understand how to add the dowloadable pause/unpause extension
that is documented in (https://craig.is/killing/mice) Mousetrap.
How does the code get inserted in the .js file?
Bob Abarbanel
<EMAIL_ADDRESS>—
Reply to this email directly or view it on GitHub
https://github.com/ccampbell/mousetrap/issues/335.

Closing this since @michaelmathy provided instructions

How would this work with import? This works: import Mousetrap from 'mousetrap', but I cannot add the pause plugin for some reason.

How would this work with import? This works: import Mousetrap from 'mousetrap', but I cannot add the pause plugin for some reason.

I have the same problem

Not sure if people are still having problem with import or not, but I had the same problem and got it working by doing this in a Vue application:
const mousetrap = require("mousetrap")
require("mousetrap/plugins/pause/mousetrap-pause")

const vueMousetrap = {
  install: function (Vue) {
    Vue.prototype.$mousetrap = mousetrap
  }
}

export default vueMousetrap


query GO:0001193  maintenance of transcriptional fidelity during transcription elongation by RNA polymerase II

GO:0001193  maintenance of transcriptional fidelity during transcription elongation by RNA polymerase II
has 5 EXP annotations to 2 GPfrom SGD.
This term seems like a combination of a MF + a phenotype?

Will add consider GO:0140673 transcription elongation-coupled chromatin remodeling
@colinlog


App shouldn't pause when resizing is happening

or at least it should be behind a config

Rendering should at least be paused we don't want to recreate a swapchain continuously while we are dragging the screen. this should only happen when we stop resizing

PR has been made https://github.com/New-Creta/Rex/pull/166


encoding/csv bug?

go version go1.10.2 darwin/amd64
I need to process a csv file that uses '|' as a separator,
The fields of the file contain several quotation marks character [ " ], evidently the result of an incorrect quoting.
The question is, why the parser goes into error considering the characters [ " ] if the separator is [ | ]?
is it a bug or is it correct?
Try this example.
https://play.golang.org/p/PsB8aOec9Rz
T.I.A.
Franco

Regardless of the separator a " starts a quoted-field and inside a quoted-field "" is treated as a single quote.  Thus "Rob""|"Pike"|rob is seen as "Rob"| I presume.

The behavior you're seeing is correct.
encoding/csv follows the format described in RFC 4180. See §2c7 (emphasis mine):

If double-quotes are used to enclose fields, then a double-quote appearing inside a field must be escaped by preceding it with another double quote. […]


Dev: Make test runnable out of the box, without having to update them

Unify both deployment name and API key. This API key is also pre-written in the example config. As this, user can run test out-of-the-box, without having to update the test files manually.

Good point! I have adopted your idea and modified the code accordingly. Not approving this PR because I think it is better if the test code contains explicit engines. Was quicker to modify directly than ping pong.


Properly add windows-specific deps

This handles #19 properly, using a Specification extension rather than doing it through bundler.

The filenames don't seem to properly match: mkrf vs mkfr.

@sickill Ping :P

@elifoster oh, I didn't notice your last commit. Thanks!

@elifoster looks like this break the build on Rubinius: https://travis-ci.org/sickill/rainbow/jobs/110784324 Can you look at it?

Super strange. I honestly have no clue why this commit in particular would cause that...

If we don't figure out why this fails on Rubinius I'm considering reverting this change.
While one could argue that by supporting Windows we support more users than by supporting Rubinius, it's this unknown behavior that occurs on Rubinius now that is worrying me, because we don't know what's wrong here versus knowing exactly why it didn't work on Windows. Not sure if I made myself clear, but yeah, my current thoughts.


Text boxes disappear when embedding PDFs

What were you trying to do?
Embed the pages of a PDF into a new, blank PDF.
File being embedded: https://researchtorevenue.files.wordpress.com/2015/04/1r41ai10801601_fong.pdf (saved locally as embed-multi.pdf)
Output file: test-embed-multi-output.pdf
How did you attempt to do it?
import fs from 'fs';

import { PDFDocument, PDFForm, StandardFonts, PDFFont, PageSizes } from 'pdf-lib';

const pdfDoc = await PDFDocument.create();

// Embed PDF pages:
let embedsource = fs.readFileSync('./embed-multi.pdf');
let embedPDF = await PDFDocument.load(embedsource);

for (let i = 0; i < embedPDF.getPageCount(); i++)
{
	console.log("Embedding page", i);
	let embedded = await pdfDoc.embedPage(embedPDF.getPage(i));
	let pg = pdfDoc.addPage(PageSizes.Letter);
	pg.drawPage(embedded);
}

fs.writeFileSync('test-embed-multi-output.pdf', await pdfDoc.save());

What actually happened?
The document was embedded, but all Text Boxes in the original embed document were lost.
Screenshot of original embed-multi.pdf: http://is.am/5bwt
Screenshot of test-embed-multi-output.pdf: http://is.am/5bwu
The floating text boxes were gone on the output PDF.
What did you expect to happen?
I expected the embedded document to look identical to the original document being embedded, without losing any components.
How can we reproduce the issue?
Run the code sample attached above.
Version
1.17.1
What environment are you running pdf-lib in?
Node
Checklist

[X] My report includes a Short, Self Contained, Correct (Compilable) Example.
[X] I have attached all PDFs, images, and other files needed to run my SSCCE.

Additional Notes
No response

Did you found any workaround for this issue?


Replace invalid panic_unwind std feature with panic-unwind

What does this PR try to resolve?
The documentation for the unstable build-std-features flag mentions that a default-enabled feature for std is panic_unwind. However, as of 2023-07-16, that feature does not even exist in the latest nightlies:

The std Cargo.toml does not contain the panic_unwind feature either, but it defines a panic-unwind feature, which works as intended with the build-std-features flag.
Therefore, let's update the documentation to refer to the intended feature instead, which improves its accuracy and reduces developer time waste.
How should we test and review this PR?
Run e.g. cargo build --release -Z build-std -Z build-std-features=panic-unwind --target x86_64-unknown-linux-gnu instead of cargo build --release -Z build-std -Z build-std-features=panic_unwind --target x86_64-unknown-linux-gnu, and watch how the first one works as intended but the second one just shows an error.

Thanks, this was changed via https://github.com/rust-lang/rust/pull/108865.
@bors r+

:pushpin: Commit b8ac2f6b62d784d515ba1b4afb99bd907c547c46 has been approved by ehuss
It is now in the queue for this repository.

:hourglass: Testing commit b8ac2f6b62d784d515ba1b4afb99bd907c547c46 with merge da4f189ac1a4f8eac8f5a42ce8269559335f7a20...

:sunny: Test successful - checks-actions
Approved by: ehuss
Pushing da4f189ac1a4f8eac8f5a42ce8269559335f7a20 to master...


[Coverity CID :205673]Memory - corruptions in /tests/net/ppp/driver/src/main.c

Static code scan issues seen in File: /tests/net/ppp/driver/src/main.c
Category: Memory - corruptions
Function: ppp_verify_fcs_1
Component: Tests
CID: 205673
Please fix or provide comments to square it off in coverity in the link: https://scan9.coverity.com/reports.htm#v32951/p12996

*** CID 205673:  Memory - corruptions  (OVERRUN)
/tests/net/ppp/driver/src/main.c: 357 in ppp_verify_fcs_1()
351
352        net_pkt_unref(pkt);
353     }
354
355     static void ppp_verify_fcs_1(void)
356     {
     CID 205673:  Memory - corruptions  (OVERRUN)
     Overrunning array "ppp_recv_data1" of 45 bytes by passing it to a function which accesses it at byte offset 45 using argument "45".
357        ppp_verify_fcs(ppp_recv_data1, sizeof(ppp_recv_data1));
358     }
359
360     static bool calc_fcs(struct net_pkt *pkt, u16_t *fcs)
361     {
362        struct net_buf *buf;

False positive


[Feat]: Images on About us page

Feature Description
I will add highquality images which goes with the theme and makes website more attrative
Provide a detailed description of the feature
These current images are not going with the theme and are over expanding making the ui quite weak

Put here any screenshots or videos (optional)
No response
By submitting this issue, you agree to

[X] I agree to follow this project's Code of Conduct
[X] I’ve read all the issues in the issue section, and this feature has not been proposed yet.

Other Information

[X] I'm a GSSoC '24 Extended contributor
[X] I'm a Hacktoberfest '24 contributor
[X] I am willing to work on this feature (optional)

I would like to add another feat into this feature

@Vaishh18 Please change the images to new ones that align with our theme. Please make sure the new images are optimized for size, since the current images are over 1 MB, which negatively impacts loading times.

@Khizarshah01 yes sure!!

Go ahead!


feat: splitting multihead attention into all nodes.

Test
Model: Llama 3 8B Q40
Buffer: Q80
Setup: 4 x Raspberry Pi 5 8GB + TP-Link LS1008G Switch
Transfer size / token

Devices
0.3.0
This PR
Percentage change

2 x Raspberry Pi 5
S 646 kB + R 476 kB = 1122 kB
S 578 kB + R 442 kB = 1020 kB
-9.09%

4 x Raspberry Pi 5
S 2295 kB + R 714 kB = 3009 kB
S 2193 kB + R 663 kB = 2856 kB
-5.08%

Avg tokens / secon

Devices

0.3.0
This PR
Percentage change

2 x Raspberry Pi 5
Avg generation time
444.27 ms
381.81 ms

Avg inference time
362.73
349.94 ms
-3.53%

Avg transfer time
80.11 ms
30.31 ms*

4 x Raspberry Pi 5
Avg generation time
331.47 ms
359.44 ms

Avg inference time
267.62 ms
258.00 ms
-3.59%

Avg transfer time
62.34 ms
99.69 ms

* I think the used switch is completely non-deterministic, it achieves a random speed at different times. So I recommend to compare only the avg inference time.

To merge this PR I need to fix mixtral & grok architectures.

I changed the implementation a bit, now there is no synchronization between llamaQuantizeMultiheadAtt and llamaAtt.
Transfer size / token

Devices
0.3.0
This PR v2
Percentage change

2 devices
S 646 kB + R 476 kB = 1122 kB
S 510 kB + R 442 kB = 952 kB
-15.15%

4 devices
S 2295 kB + R 714 kB = 3009 kB
S 1887 kB + R 867 kB = 2754 kB
-8.47%

8 devices
S 5771 kB + R 833 kB = 6604 kB
S 4819 kB + R 1487 kB = 6306 kB
-4.51%

The final state of the attention synchronization looks like this for a single block:
root --- xb  ---> node
root <-- xbv ---- node
merge att

The previous implementation:
root --- xb  --> node
root <-- q  ---- node
root <-- k  ---- node
root <-- v  ---- node
root --- xb ---> node
root <-- xb2 --- node
merge att

Not sure why but I pulled the latest code and now it won't generate any tokens, getting stuck here
float* logits = inference->infer(token, pos);
Thought it might be the changes I was working on, as I was cleaning up server.cpp but then I tried it on main and I get same behavior.
sudo nice -n -20 ./main inference --steps 10 --prompt "Hello World!" --model ~/Meta-Llama-3-8B-Instruct-Distributed/dllama_original_q40.bin --tokenizer ~/Meta-Llama-3-8B-Instruct-Distributed/dllama-llama3-tokenizer.t --weights-float-type q40 --buffer-float-type q80 --nthreads 8 --workers <IP_ADDRESS>:9990
💡 arch: llama2
💡 dim: 4096
💡 hiddenDim: 14336
💡 nLayers: 32
💡 nHeads: 32
💡 nKvHeads: 8
💡 vocabSize: 128256
💡 seqLen: 2048
💡 nSlices: 2
💡 ropeTheta: 500000.0
📄 bosId: 128000
📄 eosId: 128001
🕒 ropeCache: 16384 kB
⏩ Loaded 6175568 kB
Then nothing happens, CPU usage goes up to around 70% but no tokens are generated, any idea what might be happening?

@DifferentialityDevelopment have you pulled to this commit? Accidentally I disabled memory allocation.

No I think it might have been my bad as I just realized I forgot to rebuild with latest on the worker


fix(test runner): Use ExUnit testPaths and testPattern

First draft of a new way to identify through ExUnit's testPaths and testPattern parameters. For single app projects, we get the values directly from the project configuration.
For umbrella apps, I went with a configuration for now. Should we decide that we want this to be seamless, I thought we could evaluate each app's mix.exs file and execute the project/0 function, but that would imply running client code on the server.
As far as I know, these configurations are rarely changed, so while it is an inconvenience, I don't think it will affect too many people.
I'll start working on tests once I've had confirmation that we want to move forward with this.
Here's an example of what we expect these new configs to look like:
testPattern
{
  "app1": "*_custom_app1_pattern.exs",
  "app2": "*_custom_app2_pattern.exs"
}

testPaths
{
  "app1": ["my_app1_custom_path"],
  "app2": ["my_app2_custom_path"]
}

As of opening, this should fix the last of the issues described in https://github.com/elixir-lsp/elixir-ls/issues/438.

I think we could take a simpler way and only support the default test path and the default _test.exs pattern in umbrella apps.

Hi @lukaszsamson!

I think we could take a simpler way and only support the default test path and the default _test.exs pattern in umbrella apps.

By "simpler way" I assume you mean the implementation would be simpler? While that is true, I don't feel like the current implementation is that complex (although maybe it could be extracted somewhere else to make it easier to find and work with) and I think it would be unfortunate to leave some (admittedly probably very few) users in the dust.
That said, you're the maintainer and more experienced with the project so I'll remove the functionality if you really believe it's not worth it.

That said, you're the maintainer and more experienced with the project so I'll remove the functionality if you really believe it's not worth it.

That was only a suggestion. If you find it's not too costly then feel free to do it :)

That was only a suggestion. If you find it's not too costly then feel free to do it :)

Well it's already done and I really don't think it adds too much complexity :)
I'll fix your other comment and update the tests then!

All right, tests are updated, along with a couple bug fixes! @lukaszsamson I think this should fix the last of the issues in https://github.com/elixir-lsp/elixir-ls/issues/438 on the elixir-ls side.


Add type hint to histograms for superior tally integration

Summary: Currently, all histograms created through netmetrics will
always be recorded as values.  This mostly affects the bucket name tags
that are recorded with the histograms.  Currently, the histograms are
being recorded as "1.00000-2.00000" where ideally they would be
"1ms-2ms".
This PR keeps the "Value" as the default for histograms, but adds a Type
field to the HistogramSpec that we thread through to the
push.HistogramSpec so that our tally integration can do the right thing
based on the type of histogram.
Biggest part of this PR that's iffy for me is the repeated const values
in the metrics and push packages, open to suggestions to isolate that.

Great catch. Will review in detail this morning and hash out any required changes - we should release this first thing in the morning on Monday.

Closing since we've determined this is a change that will need to be created in tally to change "1.0000" to "1" or "1.0" (basically just remove the unnecessary granularity.


PR, troubleshoot them until they're all passing

Why:
Closes:

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

[x] I have reviewed my changes in staging (look for the "Automatically generated comment" and click the links in the "Preview" column to view your latest changes).
[x] For content changes, I have completed the self-review checklist.

Why:
Closes:
What's being changed (if available, include any code snippets, screenshots, or gifs):
Check off the following:

[x]  I have reviewed my changes in staging (look for the "Automatically generated comment" and click the links in the "Preview" column to view your latest changes).
[x]  For content changes, I have completed the self-review checklist.
Screenshot or gif not essential.

removed the previous changes to the file

This seems to have been opened accidentally, I am going to close it now :yellow_heart:
Take a look at the contributing.md to learn how to contribute in this repo. You can open a discussion if you have any questions or check out issues with the help wanted label. :sparkles:


Fix artists with names having slavic chars

It's impossible to use the APIs for bands/albums with names having slavic chars (ex. ŽALVARINIS)

 Fix artists with names having slavic chars


Mark ol.style.Icon#load() @api

We currently rely on the renderer to load the styles it intents to use.
In Ol3-Cesium we want to allow different styles for 3D and for 2D.
This commit fixes the issue by allowing application code to explicitely
initiate the loading process.

Any review?

How about adding a line of documentation saying that the application developer normally doesn't need to load the icon image himself?

@elemoine, I added some documentation. Is it clear enough?

Thank you for the quick review @elemoine.


Use set flag with kops to configure nodeport

This seems to be the proper syntax for updating cluster spec fields since kops v1.22.0.
$ kops edit cluster --help
Usage:
  kops edit cluster [CLUSTER] [flags]

Examples:
  # Edit a cluster configuration in AWS.
  kops edit cluster k8s.cluster.site --state=s3://my-state-store

Flags:
  -h, --help            help for cluster
      --set strings     Directly set values in the spec
      --unset strings   Directly unset values in the spec
...

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/close
Duplicate of #707


use python-dateutils parser

Hello! It sounds like in #1, you're looking for the python-dateutil library. Its parse function handles several date/time formats. This means you could type "Wed" for the next Wednesday available, "28" for the 28th of the current month, and several other shorthand date representations.
Please note:

This code hasn't been tested: I couldn't recreate the environment the bot runs in for testing, as I haven't worked with Heroku or Telegram bots before.
You'll need to install python-dateutil through pip.

I will rework the current remind system into an automatic one where you can /subscribe to receive a notification every day that there is a visible Iridium flare, so this part of the code will be scraped.
But thanks for the contribution!I've never used python-dateutil before, currently I'm trying to figure out how to implement the system that I just mentioned.


Add support for markdown syntax

Would improve readability and allows for more formatting in the summary panel

(https://github.com/remarkjs/react-markdown)[React Markdown Package documentation]


Update MsBuild.Engine.Corext.nuspec reference to README.md

Rename occurred here: https://github.com/Microsoft/msbuild/pull/3198
PR build failed: https://ci2.dot.net/job/Microsoft_msbuild/job/master/job/innerloop_Windows_NT_Full_prtest/343/consoleFull#181472954279494335-f7bd-47d0-8771-8661e00c2db2
But we merged anyway :(

Are we currently ignoring RHEL7.2 failures?

The CI job should work after I update the repotoolset for sourcebuild.


Create local file with dns records to be made, for easier further processing

defaulting to FALSE (to maintain current behaviour), this toggle (description included in README.md) allows for the creation of local (to the ansible server) files that contain the required DNS changes.
That way they can much easier be used for further processing, than taking them from ansible debug output.

Also, merge commits together please

Can you accept this merge request? I know it should be done differently and better, but the more I do it, the better it will become. Started with git (both cli and github combined) only yesterday.
The way I understand it, even though one commit is the same, it should be mergeable?  :-(

Sorry, but I won't accept until I like it. I like good commit history and this would break it.
You don't need to start again, you only need to learn how to work with git. You could always add changes in next commit. When you have final version, you just merge commits using git rebase.

Also, you can rebase this branch from latest version to not start over.
https://medium.com/@topspinj/how-to-git-rebase-into-a-forked-repo-c9f05e821c8a


Temporary workaround for SNAP-2627. If the unique constraint violatio…

…n is due to removed/destroyed AbstractRegionEntry, attempt is made to remove it from index & another try is made to put the new value against the index key.
If the unique constraint violation i is due to removed/destroyed AbstractRegionEntry, then we make an attempt to remove the old value from the skipList map, & loop again to see if the putIfAbsent succeeds.
(Fill in the changes here)
Patch testing
(Fill in the details about how this patch was tested)
Is precheckin with -Pstore clean?
ReleaseNotes changes
(Does this change require an entry in ReleaseNotes? If yes, has it been added to it?)
Other PRs
(Does this change require changes in other projects- snappydata, spark, spark-jobserver, aqp? Add the links of PR of the other subprojects that are related to this change)

The reason for throwing is that stack will not be available till I throw. A
stack trace would help us in identifying the path during debugging...
On Mon, Oct 15, 2018 at 12:31 PM kneeraj<EMAIL_ADDRESS>wrote:

@kneeraj approved this pull request.
LGTM. One minor comment though.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/SnappyDataInc/snappy-store/pull/438#pullrequestreview-164861018,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AL1zaFQpQ0QVY3__kaQAsH3M0_4jPKBVks5ulOKkgaJpZM4Xc7_e
.

As for test for the same, let me think how I can introduce the bug in the test without source mod.


Support HQQ method.

peft version 0.10.0
base_model=Qwen1.5-14B-Chat_llamafy-1bit
model = AutoHQQHFModel.from_quantized(base_model).half().cuda()
modules = find_all_linear_names(model)
# Add Peft
######################################################################################
config = LoraConfig(
r=lora_r,
lora_alpha=lora_alpha,
target_modules=modules,
lora_dropout=lora_dropout,
bias="none",
task_type="CAUSAL_LM",
)
model = get_peft_model(model, config)

Target module HQQLinear() is not supported. Currently, only the following modules are supported: torch.nn.Linear, torch.nn.Embedding, torch.nn.Conv2d, transformers.pytorch_utils.Conv1D.

Indeed, HQQ is currently not implemented in PEFT. They have their own LoRA implementation, so you can check that out, but from what I can tell, it's not as feature complete as the PEFT LoRA implementation.
I checked out the HQQ LoRA layer and I think it should be possible to port it to PEFT so that PEFT can natively support HQQ. This would require a few modifications to make it compatible and to support more PEFT features (like multiple adapters).
If this is something you're interested in adding to PEFT, let us know. Otherwise, we may take a look at it in the future.
Also pinging @younesbelkada for when he's back in office.

I make my LoRA implementation for HQQ in my fork to peft. I'm not sure if I could do a pull request because I don't know if this implementation is right or not.

I make my LoRA implementation for HQQ in my fork to peft. I'm not sure if I could do a pull request because I don't know if this implementation is right or not.

Traceback (most recent call last):
File "/root/autodl-tmp/merge-with-lora-hqq2.py", line 25, in
model = PeftModel.from_pretrained(model, lora_patch,device_map={"": "cpu"},torch_dtype=torch.float16)
File "/root/miniconda3/envs/train/lib/python3.10/site-packages/peft-0.10.1.dev0-py3.10.egg/peft/peft_model.py", line 387, in from_pretrained
File "/root/miniconda3/envs/train/lib/python3.10/site-packages/peft-0.10.1.dev0-py3.10.egg/peft/peft_model.py", line 1212, in init
File "/root/miniconda3/envs/train/lib/python3.10/site-packages/peft-0.10.1.dev0-py3.10.egg/peft/peft_model.py", line 131, in init
File "/root/miniconda3/envs/train/lib/python3.10/site-packages/peft-0.10.1.dev0-py3.10.egg/peft/tuners/lora/model.py", line 136, in init
File "/root/miniconda3/envs/train/lib/python3.10/site-packages/peft-0.10.1.dev0-py3.10.egg/peft/tuners/tuners_utils.py", line 165, in init
File "/root/miniconda3/envs/train/lib/python3.10/site-packages/peft-0.10.1.dev0-py3.10.egg/peft/tuners/tuners_utils.py", line 342, in inject_adapter
File "/root/miniconda3/envs/train/lib/python3.10/site-packages/peft-0.10.1.dev0-py3.10.egg/peft/tuners/lora/model.py", line 220, in _create_and_replace
File "/root/miniconda3/envs/train/lib/python3.10/site-packages/peft-0.10.1.dev0-py3.10.egg/peft/tuners/lora/model.py", line 301, in _create_new_module
ValueError: Target module HQQLinear() is not supported. Currently, only the following modules are supported: torch.nn.Linear, torch.nn.Embedding, torch.nn.Conv2d, transformers.pytorch_utils.Conv1D.

I make my LoRA implementation for HQQ in my fork to peft. I'm not sure if I could do a pull request because I don't know if this implementation is right or not.

Thanks for the link. I did a quick check on the diff and it looks reasonable to me. It probably would require a few changes to make it fully PEFT-compatible and as you mentioned, we would have to verify the correctness (maybe we can compare outputs with the HQQ PEFT implementation). So if you're interested in giving this a try, feel free to open a (draft) PR and we can iterate from there.

@Minami-su use the hqq-lora branch, not the main branch.

@BenjaminBossan the problem is preparing for k-bit training because currently there is no sign nor param that show that current model is quantized with HQQ. That's why I change some config in my HQQ fork so that peft could know that the model is quantized with HQQ. I already test training. Forward dan backward works without any problem. I didn't check training result though.

the problem is preparing for k-bit training because currently there is no sign nor param that show that current model is quantized with HQQ. That's why I change some config in my HQQ fork so that peft could know that the model is quantized with HQQ.

That's okay. We can make such changes as long as they're backwards compatible. If you open a PR, we can discuss there whether your solution is the best one or if we can find something better.

@BenjaminBossan added to #1618

@Minami-su use the hqq-lora branch, not the main branch.

Ok,can be used.

@fahadh4ilyas How to merge lora with 1bit model?
Traceback (most recent call last):
  File "/root/autodl-tmp/merge-with-lora-hqq2.py", line 26, in <module>
    model = model.merge_and_unload()
  File "/root/miniconda3/envs/train/lib/python3.10/site-packages/peft-0.10.1.dev0-py3.10.egg/peft/tuners/lora/model.py", line 785, in merge_and_unload
  File "/root/miniconda3/envs/train/lib/python3.10/site-packages/peft-0.10.1.dev0-py3.10.egg/peft/tuners/lora/model.py", line 439, in _unload_and_optionally_merge
  File "/root/miniconda3/envs/train/lib/python3.10/site-packages/peft-0.10.1.dev0-py3.10.egg/peft/tuners/lora/hqq.py", line 80, in merge
TypeError: 'NoneType' object is not a mapping

#1618 has been merged :tada:


Update _signaltools.py

The last documentation was very ambiguous.
Also, added an example to clarify the idea behind zero-padded values.

Reference issue

What does this implement/fix?

Additional information

Please see #13509, #13530 as a reference.

Thanks for the update @VitalyChait. Could we add some interpretation to the example? Otherwise I don't feel this help too much users to understand what the function does.

Hey, sure I will add but I think it is quite straightforward.
I also assume the text should be added after both of the examples.
To clarify, I mean that the example is here only to quickly let the user know that it is a zero-padded function, thus the first example starts with a window size of 5 and later goes to the default size of =3.
We should be careful with long texts and interpretations as well, it's often distracting.
In addition, users that are unaware of what a median filter is (or a median number in general) will never read the docs from the file, they will just quickly hop into google.

Lot of assumptions there. Adding a few lines is always wanted. If users don't want to read them it's fine, for those who need more than the code, we have a short description of what is happening. I am not asking for more than a description of input/output and why it's expected.
Having some text also helps SEO and makes things more discoverable. We don't want to restrict these tools to only people who know that such tools exists and documentation goes a long way democratising things.


Handle responsive images

src attributes are handled, but not srcset which provides a comma delimited list of image urls to be used for different screen sizes. More info on srcset here.
Ultimately I'll take a look forking & issuing a pull request, but I thought I'd log the issue for the moment.

@bwthomas did you find any solution to this? Maybe some other library?


LE1 vocabulary mismatch

Some of the LE1 problems display a vector equation but refer to it as an augmented matrix in Task 1. (Task 2 is correct.)

moving this to https://github.com/TeamBasedInquiryLearning/linear-algebra/issues


Using Nylas Node v3 SDK, create a code sample to create calendar

Using Nylas Node v3 SDK, create a code sample to create calendar

Hello! I would like to take this on if possible :)

Thanks, @kelbri10 - just assigned this to you. Some further details:

Here are the details to install the Nylas SDK for Nylas v3: https://www.npmjs.com/package/nylas/v/7.0.0-beta.2
Send us an email at devrel @ nylas.com and we can help set up a dev account for testing the code sample.

thanks for the email, next steps:

@kelbri10 accept verification email from Nylas
@relaxedtomato to set up the dev dashboard for testing
@relaxedtomato to provide access to the dev dashboard

Accepted the email ! @relaxedtomato

Steps 1, 2, and 3 are done :)


Include Action object when it is triggered

refluxjs is interesting so i tried using it
i just noticed something that may be improved, if this actually makes sense
in this sample code:
var Actions = Reflux.createActions({
    "load": {async: true}
});

var Store = Reflux.createStore({
    listenables: Actions,
    onLoad: function() {
        // i will do something async here
        dummyAsyncOperation(arguments)
            .then(Actions.load.completed)
            .fail(Actions.load.failed);
    }
});

when the promise resolves, i have to call Actions.load.completed
i am thinking of having the action itself in the arguments, like:
var Store = Reflux.createStore({
    listenables: Actions,
    onLoad: function(action, data) {
        // i will do something async here
        dummyAsyncOperation(data)
            .then(action.completed)
            .fail(action.failed);
    }
});

Considering the store has a reference to the actions it has registered and every callback is mapped to one action it seems unnecessary (as in the first code snippet). I'd also say it is confusing when the actions uses multiple arguments.
Idk. I'm on the fence on this one.

This is a built in language feature of javascript. Use this, or bind depending on your implementation details of the calling object.


Nightly builds in test docker repo

I'm recovering the nightly builds and I've noticed we're publishing them into some testcamelk/camel-k repository (see https://hub.docker.com/r/testcamelk/camel-k/tags). I wonder if we should instead use the official repo (apache/camel-k). I don't know if there is any policy limitation though from the foundation.
Then, another thing I noticed is that we are not using latest tag at all. I think we should label the latest stable release with this tag as well.
@astefanutti @oscerd @lburgazzoli any thought?

Thanks @oscerd. I've managed to setup a single nightly release which is pushing to testcamelk repo. That configuration is taken from some organization secret (see https://github.com/apache/camel-k/blob/main/.github/workflows/release.yml#L52-L53). Can you please tell me if we have the equivalent for camelk/camelk staging as you were suggesting? replacing that should be enough to publish the nightly in the staging repo.

I don't think we have something like that for camelk/camelk. We need @nicolaferraro for this purpose, because he set up the original account.

@oscerd Now that we have a single rolling tag, would that be acceptable to push it in apache/camel-k? That may not be obvious for users that camelk/camelk is legit, and requires the prudent ones to do their own research to assess whether it's fishy or not.

Yes, it makes sense totally sense now.

Do we already have the secret configured for that account?

@oscerd is it something already present in the setting of the project as it happens for TEST_DOCKER_HUB_USERNAME? Thanks.

As far as I know no. The only case when we push on docker is when we release.. so it is done with personal accounts. We ask Infra to enable some accounts of the PMC.

Great, thanks. Let me know when we have any news so we I can do the needed changes. In the while we can use the testing docker hub. I've just checked and it replaces correctly the image.

Hi @oscerd can I ask you if you have any update on this one? Thanks in advance.

I didn't ask to Infra. I would probably first ask to @zregvart because he's the expert about Infra and credentials.

There are some notes on this towards the bottom of this document.
The ASF policy allows distribution of compiled binaries, for end user convenience. For snapshot builds we need to carefully steer end users away as they are not official voted-upon releases, so make sure to indicate that these are only for development/testing.

There are some notes on this towards the bottom of this document. The ASF policy allows distribution of compiled binaries, for end user convenience. For snapshot builds we need to carefully steer end users away as they are not official voted-upon releases, so make sure to indicate that these are only for development/testing.

Thanks @zregvart . I see in the example it mentions the usage of certain secrets (DOCKERHUB_USER and token DOCKERHUB_TOKEN), but they must be provided in the configuration setting. As I understand from a previous comment from @oscerd, we don't have them set. The official release process is done with personal user accounts, so, if we want to proceed ahead we will need to ask those credentials.

I've provided some detail in the release notes to let people know the test account is the one we use. We can keep it as it is I guess.


fix: cognitive services create example

Empty schema/body for create action

Automation for azure-sdk-for-python

Automation for azure-sdk-for-go

Can one of the admins verify this patch?

Automation for azure-sdk-for-java


search work but music dont play

i think its same problem https://github.com/terreng/computercraft-streaming-music/issues/6

fixed


Random create or delete resource

Hello,
I'm creating an eks cluster using this module and I have an issue with a resource that is created from ci/cd and deleted when using manual execution.
# module.eks.time_sleep.this[0] will be destroyed
  # (because time_sleep.this is not in configuration)
  - resource "time_sleep" "this" {
      - create_duration = "30s" -> null
      - id              = "2023-02-19T17:21:57Z" -> null
      - triggers        = {
          - "cluster_certificate_authority_data" = "xxxxxxxxxxxx"
          - "cluster_endpoint"                   = "https://xxxxxxxx"
          - "cluster_name"                       = "xxxxx"
          - "cluster_version"                    = "1.24"
        } -> null
    }

I don't know how to properly add or remove this resource. I can't let it do randomly any action.
Any idea plz ?

what is the issue you are facing, I don't follow

when I run terraform  apply, there is a resource module.eks.time_sleep that is destroyed or added randomly. But I don't have any resource time_sleep in the code.
When I execute terraform apply directly on my laptop, this resource is destroyed. When terraform apply is executed from a ci/cd pipeline, this ressource is added.
All state files/lock are stored in the same backend (http on gitlab). So I don't understand what is that module and how to control it stop the random action.

https://github.com/terraform-aws-modules/terraform-aws-eks/commit/78027f37e43c79748cd7528d3803122cb8072ed7#diff-f18568a32bfa70d11a736400eff74d8c51858b9fcbb8af637c14d94c3562a431R22-R40
Do you have a reproduction that reproduces this behavior

I dont know how to reproduce this.
My code:
module "eks" {
  source  = "terraform-aws-modules/eks/aws"
  version = "~> 19.0"

  cluster_name    = local.cluster_name
  cluster_version = var.eks.kubernetes_version

  vpc_id                               = module.vpc.vpc_id
  subnet_ids                           = module.vpc.private_subnets
  cluster_endpoint_public_access       = true
  cluster_endpoint_public_access_cidrs = var.eks.public_acls

  cluster_addons = {
    coredns = {
      most_recent = true
    }
    kube-proxy = {
      most_recent = true
    }
    vpc-cni = {
      most_recent = true
    }
    aws-ebs-csi-driver = {
      most_recent = true
    }
  }

  eks_managed_node_group_defaults = {
    key_name          = "xps"
    enable_monitoring = true
    ami_type          = "AL2_x86_64"
    update_config = {
      # max_unavailable_percentage = 50 # or set `max_unavailable`
      max_unavailable = 1
    }
    iam_role_additional_policies = {
      AmazonEBSCSIDriverPolicy          = "arn:aws:iam::aws:policy/service-role/AmazonEBSCSIDriverPolicy"
      AmazonElasticFileSystemFullAccess = "arn:aws:iam::aws:policy/AmazonElasticFileSystemFullAccess"
    }
  }

  eks_managed_node_groups = {
    one = {
      name = var.eks.node_groups[0].name

      labels = {
        role = "worker"
      }

      instance_types = var.eks.node_groups[0].instance_types

      min_size     = var.eks.node_groups[0].min_size
      max_size     = var.eks.node_groups[0].max_size
      desired_size = var.eks.node_groups[0].desired_size
    }
  }

  node_security_group_additional_rules = {
    inress_ingress_http_tcp = {
      description = "Access EKS Nginx Pod HTTP"
      protocol    = "tcp"
      from_port   = 80
      to_port     = 80
      type        = "ingress"
      cidr_blocks = ["<IP_ADDRESS>/0"]
    }
    inress_ingress_https_tcp = {
      description = "Access EKS Nginx Pod HTTPS"
      protocol    = "tcp"
      from_port   = 443
      to_port     = 443
      type        = "ingress"
      cidr_blocks = ["<IP_ADDRESS>/0"]
    }
    inress_ingress_nfs_tcp = {
      description = "Access NFS for EFS"
      protocol    = "tcp"
      from_port   = 2049
      to_port     = 2049
      type        = "ingress"
      cidr_blocks = var.eks.vpc.private_subnets
    }
  }
}

I'm using the same version of terraform in local and in ci/cd (hashicorp/terraform:1.3.4).

if you are unable to share a reproduction, what shall I do then? Closing until a reproduction that produces the same issue can be provided

I faced the same problem.
But I don't know how to reproduce it.


some devops stuff

@mafintosh Mind flipping the switch on travis?

Updating depencies after this PR.

I have enabled it on travis now

Sweet. I did a quick update locally on dependencies but things break. Will have to make a PR for that to discuss what's wrong since I currently have limited knowledge of some of the important dependencies.


Fixed to support python 3

urllib2 doesn't exist within python3. The proposed changes should be compatible with python2 and 3, tested on 2.7.13 and 3.6.0.
Sorry looks like I commited this early without running more tests, let me refine & push a new update to fix compatibility with both Python2 and 3.

Thanks a lot for this great contribution!

Does the version need to be bumped in setup.py and a new version uploaded to pypi?

Yes, I believe the graphcool team is pretty busy and will get to that soon.

It's been a while since we've dealt with Python packages the last time. What's the command needed to publish a new version @ssshah86?

<python setup.py register -r pypi>
and
<python setup.py sdist upload -r pypi>
But @rcy is right, the version should be incremented first otherwise PyPI will reject it.
see: http://sherifsoliman.com/2016/09/30/Python-package-with-GitHub-PyPI/#release-testing

This is what I'm getting here. Can I add you as a collaborator somehow?

Yea my PyPI u/n is ssshah86, but I believe you have to update it in setup.py for me to be a maintainer though.
I think it's the version of Python you are using, 3.5.2. There's an update in distutils for 3.5.3 that uploads to pypi.org instead of pypi.python.org, which was shut down July 3rd.
What's the repository information in your .pypirc file? If you upgrade you can delete the line starting with repository and you will use your upload tool’s default URL.
OR you can also use twine by installing it via pip3 install twine, which should be version 1.9.x. Then after  you build your source dist, you can use twine upload --repository testpypi dist/* where the --repository flag will read from your .pypirc file.

Added you as an owner on PyPI!

Thanks. Just uploaded v0.2.0. Everything looks great. There's one issue when upgrading on OSX when installing something with a dependency on the package 'six', detailed here: https://github.com/pypa/pip/issues/3165

you can uninstall and reinstall to avoid the error

Just installed 0.2.0 here, everything is working great... thank you both for your work!


Announcing self-sufficient PR merges to automatically publish Operators

Dear OperatorHub.io and OpenShift Operator Community,
we are pleased to announce, that we have invested significantly in the Operator contribution process to allow for your contributions and PRs to be merged faster. This means you can publish your new Operators quickly and without review from the community maintainers. Your PR needs to meet a couple of criteria that are documented here: https://operator-framework.github.io/community-operators/self-merge-updates/
If your PR fits the criteria it will be merged automatically. In this process you have complete control over which GitHub user is able to leverage this feature and by default no auto-merging is allowed until the PR author (including you) is part of the reviewers list.
We hope this change enables you to work more effectively and self-sufficiently in publishing updates to your Operator.
Kind Regards,
The community-operators maintainers team
mentions:
@2uasimojo, @AdheipSingh, @ArangoGutierrez, @AstroProfundis, @Avni-Sharma, @Carrefour-Group, @CohenAviad, @DTMad, @DhritiShikhar, @EmilyM1, @EnterpriseDB, @Flagsmith, @Fryguy, @HubertStefanski, @J0zi, @JohnStarich, @Kaitou786, @Kong, @LCaparelli, @LaVLaS, @Listson, @LorbusChris, @LouisPlisso, @OchiengEd, @Rajpratik71, @RakhithaRR, @SDBrett, @Simonzhaohui, @SteveMattar, @Tatsinnit, @TheWeatherCompany, @aavarghese, @abaiken, @aceeric, @akhil-rane, @akoserwal, @akram, @alien-ike, @aliok, @andreaskaris, @aneeshkp, @antonlisovenko, @anyasabo, @apahim, @apeschel, @aravindhp, @ashenoy-hedvig, @aslakknutsen, @astefanutti, @atef23, @avalluri, @bart0sh, @bcrochet, @bigkevmcd, @blaqkube, @blublinsky, @brian-avery, @cap1984, @chanwit, @charith-elastic, @chatton, @chbatey, @che-bot, @che-incubator, @che-incubator-bot, @cheesiong-lee, @chetan-rns, @christophd, @clamoriniere, @cliveseldon, @cloudant, @containers-ai, @couchbase-partners, @cschwede, @ctron, @dabeeeenster, @dagrayvid, @danielpacak, @dannyzaken, @darkowlzz, @david-kow, @deeghuge, @deekshahegde86, @devOpsHelm, @dgoodwin, @dinhxuanvu, @djzager, @dlbock, @dmatch01, @dmesser, @dragonly, @dtrawins, @dvropsmx, @dymurray, @ecordell, @eguzki, @eresende-nuodb, @erikerlandson, @esara, @evan-hataishi, @f41gh7, @fbladilo, @fcanovai, @flaper87, @frant-hartm, @gallettilance, @gautambaghel, @gee4vee, @gregsheremeta, @gunjan5, @gurushantj, @guyyakir, @gyliu513, @haibinxie, @hasancelik, @hco-bot, @houshengbo, @husky-parul, @iamabhishek-dubey, @ibuziuk, @ingvagabund, @instana, @irajdeep, @ivanstanev, @jeesmon, @jfchevrette, @jitendar-singh, @jkatz, @jkhelil, @jmazzitelli, @jmeis, @jmesnil, @jmontleon, @joeschram, @jogetworkflow, @jomkz, @jonathanvila, @jpkrohling, @jsenko, @juljog, @k-wall, @kerenlahav, @kerrygunn, @knrc, @ksatchit, @kubemod, @kubemq, @kubemq-io, @kubernetes-projects, @kulkarnicr, @kyguy, @lbroudoux, @leifmadsen, @leochr, @little-guy-lxr, @liuruiyiyang, @lrgar, @lumjjb, @madhukirans, @madorn, @maistra, @maskarb, @matzew, @max3903, @mdonkers, @mflendrich, @microcks, @miguelsorianod, @mkuznyetsov, @mrethers, @mrizzi, @mtyazici, @mvalahtv, @mvalarh, @n1r1, @nickboldt, @nicolaferraro, @nikhil-thomas, @olukas, @open-cluster-management, @operator-framework, @oranichu, @orenc1, @oriyarde, @pavelmaliy, @pb82, @pebrc, @pedjak, @phantomjinx, @piyush-nimbalkar, @portworx, @prft-rh, @pweil-, @radtriste, @raffaelespazzoli, @rainest, @rajivnathan, @rareddy, @raunakkumar, @rayfordj, @redhat-cop, @rensyct, @renuka-fernando, @rgolangh, @rhm-samples, @ricardozanini, @rigazilla, @rodrigovalin, @rohanjayaraj, @rojkov, @rrati, @rubenvp8510, @rvansa, @ryanemerson, @saada, @sabre1041, @sbose78, @scholzj, @seanmalloy, @sebsoto, @secondsun, @selvamt94, @shivanshs9, @shubham-pampattiwar, @slaskawi, @slopezz, @snyk, @snyksec, @spolti, @squids-io, @sunsingerus, @svallala, @sxd, @tahmmee, @tanalam2411, @thbkrkr, @tmckayus, @tolusha, @tomashibm, @tomgeorge, @tphee, @tplavcic, @tumido, @turbonomic, @twiest, @ursais, @vaibhavjainwiz, @vassilvk, @vboulineau, @vkvamsiopsmx, @vmuzikar, @waveywaves, @waynesun09, @weii666, @welshDoug, @wiggzz, @willholley

So hey, this is cool, but per doc:

If author of PR is not in reviewers list, PR will not be merged automatically. For automatic merging PR needs to have authorized-changes label set.

I'm observing 1 2 that even an /approve or /lgtm by a pre-existing member of the reviewer list (in ci.yaml) doesn't trigger automatic merge. Can it be made so?


Feature Request: Show the 7 segment display status for turbo pmacs

Amp Status bits (7 Segment Display Status):
Mx90 – Amp Status word
Mx90 & 448 – Amp Status bits (but this isn't a valid on-line command so you need to use the Watch Window or PLC code below or do it manually with bitwise AND in the Windows calculator in programmer mode)

This feature has been added to the released v3.0.0.


integrate with RESTful backend to implement igorm math provider function

Expectation:

a POST endpoint that accepts exp:number and varNames: string[]
the endpoint does some validation and  responds with an error or succeeds with structure like:

export type MathOperationResult = {     goal: string     result: string     duration: number }

the response for Kordano Build in general will be different and for now is not yet developed
the POST endpoint should perform a few seconds maximum and it should also cache the results to respond faster net time.

backend should not serve more than one client at a time. If there is another request in process the client should get server is busy status immediately. And after a request is handle it should debounce next request for at least 1 second.


Implement new logging policy

This issue is to track the implementation of #5299 into Lodestar's logging. After the Shapella hard fork, we experienced a consistent, ignorable error messages relating to the QUEUE_ERROR_QUEUE_MAX_LENGTH which created a poor logging UX to users of Lodestar during the fork transition due to the flow of large batches of BLStoExecution messages. This is a wake up call for us to urgently implement the new logging policy for the next attainable release to fix our poor logging UX.
There are many errors we would like to fix listed in #4400 which should now also abide by the new policy.

Potential candidate to move from warn to debug as this log happens quite frequently even if there is nothing wrong with the node itself. This was mentioned by a users in discord but I also see this log a lot and don't know what to do with it.
https://github.com/ChainSafe/lodestar/blob/ad0c58ffd3a875c869b1e28cc1afc23c2f962696/packages/beacon-node/src/network/peers/peerManager.ts#L609
warn: Unclean disconnect peer=16...A3GmAv Socket close timeout
CodeError: Socket close timeout
    at Timeout._onTimeout (file:///usr/app/node_modules/@libp2p/tcp/src/socket-to-conn.ts:143:28)
    at listOnTimeout (node:internal/timers:569:17)
    at processTimers (node:internal/timers:512:7)

Probably someone with more experience in the networking stack needs to access this but I don't see how this log would be actionable to an end user and if a user is not able to get sufficient peers then the debug logs should be looked at.

These should be less verbose if it is due to Service Unavailable: Node is syncing, we do not need the stack trace and should consider logging as warning as this is expected but user should still be aware that something is not yet working
Error: Error on getProposerDuties - Service Unavailable: Node is syncing - headSlot 5529152 currentSlot 5529417
    at Function.assert (file:///usr/app/packages/api/src/utils/client/httpClient.ts:44:13)
    at BlockDutiesService.pollBeaconProposers (file:///usr/app/packages/validator/src/services/blockDuties.ts:155:14)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at BlockDutiesService.pollBeaconProposersAndNotify (file:///usr/app/packages/validator/src/services/blockDuties.ts:129:5)
    at BlockDutiesService.runBlockDutiesTask (file:///usr/app/packages/validator/src/services/blockDuties.ts:87:9)
    at Clock.runAtMostEvery (file:///usr/app/packages/validator/src/util/clock.ts:96:7)
Apr-30 13:23:24.418[]                error: Failed to download attester duties epoch=172794 Failed to obtain attester duty - Service Unavailable: Node is syncing - headSlot 5529152 currentSlot 5529417
Error: Failed to obtain attester duty - Service Unavailable: Node is syncing - headSlot 5529152 currentSlot 5529417
    at Function.assert (file:///usr/app/packages/api/src/utils/client/httpClient.ts:44:13)
    at AttestationDutiesService.pollBeaconAttestersForEpoch (file:///usr/app/packages/validator/src/services/attestationDuties.ts:214:14)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at AttestationDutiesService.pollBeaconAttesters (file:///usr/app/packages/validator/src/services/attestationDuties.ts:163:7)
    at async Promise.all (index 1)
    at AttestationDutiesService.runDutiesTasks (file:///usr/app/packages/validator/src/services/attestationDuties.ts:124:5)
    at Clock.runAtMostEvery (file:///usr/app/packages/validator/src/util/clock.ts:96:7)
Apr-30 13:23:24.423[]                error: Failed to download SyncDuties epoch=172794 Failed to obtain SyncDuties - Service Unavailable: Node is syncing - headSlot 5529152 currentSlot 5529417
Error: Failed to obtain SyncDuties - Service Unavailable: Node is syncing - headSlot 5529152 currentSlot 5529417
    at Function.assert (file:///usr/app/packages/api/src/utils/client/httpClient.ts:44:13)
    at SyncCommitteeDutiesService.pollSyncCommitteesForEpoch (file:///usr/app/packages/validator/src/services/syncCommitteeDuties.ts:233:14)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at SyncCommitteeDutiesService.pollSyncCommittees (file:///usr/app/packages/validator/src/services/syncCommitteeDuties.ts:178:7)
    at async Promise.all (index 1)
    at SyncCommitteeDutiesService.runDutiesTasks (file:///usr/app/packages/validator/src/services/syncCommitteeDuties.ts:140:5)
    at Clock.runAtMostEvery (file:///usr/app/packages/validator/src/util/clock.ts:96:7)

There's a not so great attempt at controlling those type of error logs, see https://github.com/ChainSafe/lodestar/blob/1e4ca97594b75ba87332a315abc7f46931144199/packages/validator/src/util/logger.ts#L43 but should be improved and applied to all paths that query the API

We create those two logs when block error happens
Jun-25 23:09:25.255[chain]           debug: Block error slot=5935547 code=BLOCK_ERROR_ALREADY_KNOWN, root=0xdc3da9c9eaf50c1fbb2a140e006dc6f8007feaee195eb4ed8ea7f18c9ff2dbb8
Error: BLOCK_ERROR_ALREADY_KNOWN
    at verifyBlocksSanityChecks (file:///home/devops/goerli/lodestar/packages/beacon-node/src/chain/blocks/verifyBlocksSanityChecks.ts:102:15)
    at BeaconChain.processBlocks (file:///home/devops/goerli/lodestar/packages/beacon-node/src/chain/blocks/index.ts:61:82)
    at JobItemQueue.BlockProcessor.jobQueue.JobItemQueue.maxLength [as itemProcessor] (file:///home/devops/goerli/lodestar/packages/beacon-node/src/chain/blocks/index.ts:27:30)
    at JobItemQueue.runJob (file:///home/devops/goerli/lodestar/packages/beacon-node/src/util/queue/itemQueue.ts:101:33)
    at JobItemQueue.runJob (file:///home/devops/goerli/lodestar/packages/beacon-node/src/util/queue/itemQueue.ts:118:15)
    at runNextTicks (node:internal/process/task_queues:60:5)
    at listOnTimeout (node:internal/timers:540:9)
    at processTimers (node:internal/timers:514:7)
Jun-25 23:09:25.255[network]         error: Error receiving block slot=5935547, peer=16Uiu2HAmR7yebF8ip58VVxCcbnSv27WFys9osJBncAi15wCSdGdk code=BLOCK_ERROR_ALREADY_KNOWN, root=0xdc3da9c9eaf50c1fbb2a140e006dc6f8007feaee195eb4ed8ea7f18c9ff2dbb8
Error: BLOCK_ERROR_ALREADY_KNOWN
    at verifyBlocksSanityChecks (file:///home/devops/goerli/lodestar/packages/beacon-node/src/chain/blocks/verifyBlocksSanityChecks.ts:102:15)
    at BeaconChain.processBlocks (file:///home/devops/goerli/lodestar/packages/beacon-node/src/chain/blocks/index.ts:61:82)
    at JobItemQueue.BlockProcessor.jobQueue.JobItemQueue.maxLength [as itemProcessor] (file:///home/devops/goerli/lodestar/packages/beacon-node/src/chain/blocks/index.ts:27:30)
    at JobItemQueue.runJob (file:///home/devops/goerli/lodestar/packages/beacon-node/src/util/queue/itemQueue.ts:101:33)
    at JobItemQueue.runJob (file:///home/devops/goerli/lodestar/packages/beacon-node/src/util/queue/itemQueue.ts:118:15)
    at runNextTicks (node:internal/process/task_queues:60:5)
    at listOnTimeout (node:internal/timers:540:9)
    at processTimers (node:internal/timers:514:7)

The error log might look scary to users and raise concerns (see discord). AFAIK those errors are kinda expected to happen, we could consider logging all those to debug or just for a subset based on error code.
https://github.com/ChainSafe/lodestar/blob/f5d12a893f5b913a04938275bb248ace1ca47539/packages/beacon-node/src/network/processor/gossipHandlers.ts#L165

duplicate of https://github.com/ChainSafe/lodestar/issues/5320


Show the List of Sales and Marketing Reports

Is your feature request related to a problem? Please describe.
On the reports page created in issue #1232, we need to show the list of the reports with type sales-and-marketing.
Describe the solution you'd like
Part 1

[x] The list should be shown like the design provided below with the name of the report on the togglable bar.
[x] The report list should be togglable. Just like the shown below
[x] Every report should have a edit button in the bottom

Reference images

Part 2

[x] The togglable bar containing the report name should also contain a view button that should redirect the user to a new page (mentioned in next point) where the report should be loaded.
[x] We need to create a page where the report should be displayed. The page should contain

[x] Menubar
[x] Report Name
[x] Report Description
[x] An iframe tag in which the report will be loaded. An example is provided below
<iframe width="600" height="900" src="https://datastudio.google.com/embed/reporting/7d875374-261f-4f61-a9e5-4b632417d227/page/Js2hC" frameborder="0" style="border:0" allowfullscreen></iframe>

Describe alternatives you've considered
NA
Additional context
NA

The feature for sales and marketing is implemented
Part 1
The report list should be togglable.

Every report should have a edit button in the bottom

Part 2
-The togglable bar containing the report name should also contain a view button that should redirect the user to a new page (mentioned in next point) where the report should be loaded.

We need to create a page where the report should be displayed. The page should contain
-Menubar
-Report Name
-Report Description

This issue PR is merged. Closing it.


Is VIRTUAL_ALLOC_RESERVE_GRANULARITY necessary?

I could not find a single usage of this macro in the source tree while I was trying to find the proper value for arm64.

Delete it since it is unused and wrong for non-Windows OSes.
It is redundant with g_SystemInfo.dwAllocationGranularity that has the right values already (64k on Windows, OS page size on Unix).

Will do. It will be part of my PR for the initial arm64 port which will be mostly a skeleton as many things will need to be implemented but at least it will enable compilation of the source code.


(BOLT-1422) Update command reference docs

This updates the command reference documentation to show available
options for each subcommand-action. Previously, the documentation had a
list of subcommand-actions and a list of options, making it difficult to
tell which options applied to which subcommand-actions.
This also adds the 'secret' subcommand to the command reference.

CLA signed by all contributors.

I'm not sure exactly how this would work, but this seems like it can be generated from the existing help text. Should we explore doing that instead?


Unable to select() on IRC session

While closing the server in linux with CTRL+C [ERR] Unable to select() on IRC session appears and then it gets freezed and nothing happens. I have to kill the screen or close the ssh session to close the server.
Also, it happens sometimes but most of the times.

I have no idea what's wrong with this one and the IRC module is already on life support and one bad encounter away from being deprecated.


superTux: set meta.mainProgram

Description of changes
This will eventually allow  nix run nixpkgs#superTux to run the game.

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@ofborg eval

Confirmed by running nix run .#superTux on a local checkout.

Thank you for the confirmation. For other occasions, if you dont want to deal with a local checkout, you can also test it like so:
nix run github:NixOS/nixpkgs/pull/192095/merge#superTux