link and conflicts_with options do not work as expected

From the docs:
# 'brew install', always 'brew services restart', 'brew link', 'brew unlink mysql' (if it is installed)
brew<EMAIL_ADDRESS>restart_service: true, link: true, conflicts_with: ["mysql"]

We want<EMAIL_ADDRESS>installed and linked. So we have this in our Brewfile:
brew<EMAIL_ADDRESS>link: true, conflicts_with: ["mysql"]

This does not work. The linking fails. Here's what happens.
$ brew install mysql
$ brew bundle
Using<EMAIL_ADDRESS>Error: Could not symlink bin/comp_err
Target /opt/homebrew/bin/comp_err
is a symlink belonging to mysql. You can unlink it:
  brew unlink mysql

To force the link and overwrite all conflicting files:
  brew link --overwrite<EMAIL_ADDRESS>
To list all files that would be deleted:
  brew link --overwrite<EMAIL_ADDRESS>--dry-run
Linking<EMAIL_ADDRESS>Homebrew Bundle complete! 1 Brewfile dependency now installed.
$ echo $?
0

The linking fails. Also brew bundle incorrectly exits with status code 0 for successful execution. This is not true.
The docs reference a -f to force overwriting. This also does not work as expected. The brew link step fails in the same way:
$ brew bundle -f
Using<EMAIL_ADDRESS>Error: Could not symlink bin/comp_err
Target /opt/homebrew/bin/comp_err
is a symlink belonging to mysql. You can unlink it:
  brew unlink mysql

To force the link and overwrite all conflicting files:
  brew link --overwrite<EMAIL_ADDRESS>
To list all files that would be deleted:
  brew link --overwrite<EMAIL_ADDRESS>--dry-run
Linking<EMAIL_ADDRESS>Homebrew Bundle complete! 1 Brewfile dependency now installed.
$ echo $?
0

Note the command still exits 0 even though a part failed.
The only way to resolve the issue is to manually run brew unlink mysql prior to brew bundle. This apparently defeats the purpose of the link and conflicts_with options.
$ brew unlink mysql
Unlinking /opt/homebrew/Cellar/mysql/9.0.1... 97 symlinks removed.
$ brew bundle
Using<EMAIL_ADDRESS>Homebrew Bundle complete! 1 Brewfile dependency now installed.
$ mysql --version
mysql  Ver 8.0.39 for macos14.4 on arm64 (Homebrew)

This issue seems similar to #932.
My Current bundle version
git:master >> pwd
/opt/homebrew/Library/Taps/homebrew/homebrew-bundle
git:master >> git show
commit 980753399e0bc5802610cd1eeacdb16cba53744b (HEAD -> master, origin/master, origin/HEAD)
Merge: d368f81 c33837a
Author: Patrick Linnane<EMAIL_ADDRESS>Date:   Tue Sep 3 15:15:48 2024 -0700

    Merge pull request #1441 from Homebrew/dependabot/bundler/rspec-core-3.13.1

The console output indicates you already have<EMAIL_ADDRESS>installed (the Using<EMAIL_ADDRESS>line).
Do a brew uninstall<EMAIL_ADDRESS>and then retry the brew bundle step.
The code paths are different for new installs/upgrades vs when already installed.
The link option is processed in all cases, conflicts_with option is only used on new installs/upgrades.
Because mysql8.0 is already installed, no call to brew unlink mysql is made. Hence the link is in the way when the brew link --force<EMAIL_ADDRESS>step is tried.
The brew link step is only a '--force' and not an '--overwrite'. A new install should call with a --force --overwrite if you pass -f but it looks like there is a very minor bug preventing that (I have a fix i'll PR in the next couple of days).
There is an unfinished PR to add a link: :overwrite option to the Brewfile spec https://github.com/Homebrew/homebrew-bundle/pull/1116. This would address the already installed case. I'm happy to look at picking this up.
As to why the exit status code is 0. Well it only cares about whether things are successfully installed. Rightly or wrongly, link and service state aren't considered as part of this.


Update config.yml

Add thing banner pattern to printing press as similar to the globe and snout banner patterns there is no way to get this renewably. The recipe costs are based off of the old cost of an enchanted gloden apple before mojang removed the recipe from the game.

#202 Merged to this branch


Prev/next nav: Add trailing slash, use rel prop

What kind of changes does this PR include?

[ ] Minor content fixes (broken links, typos, etc.)
[ ] New or updated content
[ ] Translated content
[X] Changes to the docs site code
[ ] Something else!

Description
This PR fixes two small bugs in the prev/next links in the page footer:

The links were not using the proper canonical URLs of the target pages due to missing trailing slashes.
The rel="..." attribute of the links was always set to prev, even for the next links.

@delucis PTAL


chore(wir): allow user to select from existing reports

https://wandb.atlassian.net/browse/WB-15454
https://www.figma.com/file/CfR8OyJH2aa7YO1pve1SwZ/Weave-in-Reports?node-id=420%3A27546&mode=dev
Flow:

User can select an entity that are ordered based on last edit
If op to get list of entities is still loading, the select should be disabled and have a loading indicator
If no entities are found, Select should be disabled and  placeholder should display "No entities found."
Once a user selects an entity, they can then go select a report across all the projects within the entity
If the op to get a list of reports is still loading, the select should be disabled and have a loading indicator
If no reports are found, Select should be disabled and placeholder should display "No reports found."
The Add panel button is disabled until a report is selected
When user clicks Add panel, an alert() will be displayed (for now)

Ability to select and re-select an existing report
https://github.com/wandb/weave/assets/103448723/4e26b917-055a-4f08-97d8-6240450c1e62
Evidence of list by recency and how we format the time:
THESE SCREENSHOTS ARE FROM TWO DIFFERENT ENTITIES

No reports found example:
https://github.com/wandb/weave/assets/103448723/28b9ce42-54db-4443-aa34-506231826ee4
A bit of responsive styling after increasing select menu height
https://github.com/wandb/weave/assets/103448723/9c37d5d1-2888-482e-a1c8-70b2ec565f00

Also clicking on Add to report doesn't close the popup menu. It seems to be consistent for other actions, so didn't address it in this PR
https://github.com/wandb/weave/assets/103448723/71d1ccc2-d30b-47a2-a4fa-b494adde69b3


Change the name of the platform shown in the tab

@marcovidonis we wanted to change the name of the platform bc we thought it was too long: Hybrid meetup Platform.
So we asked ChatGPT for possible names and one that came up is Hybridly.
Do you like the name? Please say yes 😆

YES! We definitely need a proper name! 😁
Hybridly sounds catchy, it's growing on me :) Yes, let's go with that if everyone's on board!


Encapsulation in C++

This Closes #4200

Hi @jamarh35. Welcome to Section EngEd 😄
Encapsulation is a pretty basic concept in programming languages. There are numerous amount of resources on this topic.
Is there something you can add to make this article unique/original?
cc @section-engineering-education/content-moderator-team

Greetings @zolomohan
In the article, I will add an explanation of how encapsulation is implemented. Here there will be the use of a real-life code snippet example that will help the user understand more about encapsulation. Moreover, I'll add a detailed description of the types of encapsulation. Lastly, the article will ensure the user understands how encapsulation relates to inheritance. This will be achieved by highlighting the differences and similarities of both encapsulation and inheritance.

Hello @zolomohan
I have made the requested addition.
The article is now ready for review.

Why did you delete the template before submitting your PR? @jamarh35

Greetings @ahmadmardeni1
I did not delete any template... The template checkboxes were empty by default by the time of submitting the PR

Greetings @zolomohan In the article, I will add an explanation of how encapsulation is implemented. Here there will be the use of a real-life code snippet example that will help the user understand more about encapsulation. Moreover, I'll add a detailed description of the types of encapsulation. Lastly, the article will ensure the user understands how encapsulation relates to inheritance. This will be achieved by highlighting the differences and similarities of both encapsulation and inheritance.

Hi @jamarh35
Since Encapsulation is programming 101, there's a lot of resources for this topic available on the internet. I don't think this topic will provide a lot of value to our program. Please consider working on another topic.
If you have a unique view on Encapsulation that you can enhance this article with and make it stand out from the rest, please let me know.


Plotly Scatter plot height problem

shinywidgets version: 0.2.3
Python version: 3.11
Operating System: Windows/Linux(Ubuntu) observed in both

Description
When the plot height of a Plotly scatter plot set to >450, bottom of the plot cannot be seen.
What I Did
I am building a data dashboard using Plotly plots and I set the height and width of the plots using user inputs, so users can change the plot sizes. When I (unintentionally) upgraded shinywidgets from v0.2.1 to v0.2.3 I ran into an issue with the height adjustments. When user input is larger than 450, some of the plot is not visible. (I simply rolled back to v0.2.1 which fixes the problem yet I think it would be better if it can be fixed.) A simplified code to reproduce the problem is below.
from shinywidgets import output_widget, render_widget
import numpy as np
import plotly.graph_objects as go

app_ui = ui.page_fluid(
    ui.row(
        ui.column(12,
            ui.input_slider(
                    "plt_width",
                    "Plot width:",
                    min=100,
                    max=2400,
                    value=600,
                    step=50,
                ),
            ui.input_slider(
                    "plt_height",
                    "Plot height:",
                    min=100,
                    max=2400,
                    value=600,
                    step=50,
                )
        )
    ),
    ui.row(
        ui.column(12,
            output_widget("scatter_plot")
        )
    )
)

def server(input, output, session):
    @output
    @render_widget
    def scatter_plot():
        fig = go.Figure(go.Scatter(x = np.random.rand(1000),
                y = np.random.rand(1000),
                mode="markers+text",
                marker={"color":"blue",
                        "size":4}))
        fig.update_layout(
            width = input.plt_width(),
            height = input.plt_height()
        )
        return fig

app = App(app_ui, server, debug=True)

enviroment is created running pipenv install with the Pipfile:
[[source]]
url = "https://pypi.org/simple"
verify_ssl = true
name = "pypi"
[packages]
numpy = "1.26.2"
shiny = "0.6.0"
shinywidgets = "0.2.3"
plotly = "5.18.0"
[dev-packages]
[requires]
python_version = "3.11"

The issue is that the default CSS provided is setting the plotly container's height to 400px always.  Code for this is here.  A temporary solution is to override this CSS with something like this at the top of your page.
app_ui = ui.page_fluid(
    ui.include_css("PATH_TO_MY_CSS"),
...

and the overriding css would be:
.plotly.plot-container {
  height: 100% !important;
}

All this being said, I don't think this solution is great.  Ideally, the figure's layout information would lead to generated HTML with the correct sizes, but looking at the source in the repo that I linked it seems that there is confusion on how to do this:
/*
  For most/all ipywidgets, we can set these defaults via the Layout() API,
  but go.FigureWidget().layout points to plotly.js' layout, and I'm not
  sure how to get at the ipywidget's layout object from there.
*/

Thanks for the report! I just merged a fix in #124


Add missing cache control and content type to supabase storage cli sub-commands

Is your feature request related to a problem? Please describe.
When using the supabase cli to interact with the storage layer, two crucial file options seem to be missing

the cache control option to customize caching, and
the content type option, to customize mime types

Both file options seem to be present e.g. in the javascript library
Compare

https://supabase.com/docs/reference/cli/supabase-storage-cp
https://supabase.com/docs/reference/javascript/storage-from-upload fileOptions (expand to see the options)

These two missing options are crucial for certain workflows and use cases and the supabase storage cli would greatly benefit in supporting them. Otherwise the only workaround is using the javascript library for one-off scripts for these specific file upload use-cases, defeating the purpose of having the supabase storage cli in the first place.
Describe the solution you'd like
Ideally the supabase storage cli sub-commands creating or modifying files get two new optional arguments:

--cache-control
--content-type

Example usage
supabase storage cp --cache-control 'public, max-age=30758400, immutable' myfile.ext ss:///mybucket/myfile.ext
supabase storage cp --content-type 'text/html' myfile.ext ss:///mybucket/myfile.ext

Describe alternatives you've considered
None
Additional context
As an inspiration, check the aws cli
aws s3 cp \
  --cache-control 'public, max-age=30758400, immutable' \
  --content-type 'binary/octet-stream' \
  myfile.ext s3://mybucket/myfile.ext

Here is one example to reproduce this

Use supabase storage cp to upload an index.html file
Check the response at https://xxx.supabase.co/storage/v1/object/public/mybucket/index.html

See how

the response content type from the file getting served is text/plain
the content type that is displayed in the supabase bucket management UI funnily enough is text/html

Here is a workaround to upload a file with cache control and content type until we have it in the supabase storage cli
curl --proto =https --tlsv1.3 'https://xxxx.supabase.co/storage/v1/object/mybucket/index.html' \
  -H "Authorization: Bearer $SUPABASE_SERVICE_KEY" \
  -H 'Cache-Control: max-age=3600' \
  -H 'Content-Type: text/html; charset=utf-8' \
  --data-binary<EMAIL_ADDRESS>

Note: an unrelated issue I ran into (also visible in the screen grab above) and what's not obvious as a user:
The content type text/html is not supported on the storage API side at the moment
Even if we set text/html manually, we'll get a text/plain response back from the served content. It would be great to have this in the documentation somewhere. More on this in https://github.com/orgs/supabase/discussions/7377

Thanks for the suggestion. Currently the content-type is automatically determined based on the first 512 bytes of the file being uploaded and the cache-control defaults to max-age=3600.
In the linked PR, I'm adding support for custom --cache-control and --content-type flags so that you can override these defaults.


[BUG] RangeError (start): Invalid value: Not in inclusive range 0..57: -1

:information_source: Info
Version: v3.6.1
:speech_balloon: Description
When trying to build an MSIX using a custom output path set, the build fails with the following error:
running "flutter build windows"...     65.1s
building msix files...                 4.5s
packing msix files...                  2.6s
Unhandled exception:
RangeError (start): Invalid value: Not in inclusive range 0..57: -1
#0      RangeError.checkValidRange (dart:core/errors.dart:351:7)
#1      _StringBase.substring (dart:core-patch/string_patch.dart:400:27)
#2      Msix._msixOutputPath (package:msix/msix.dart:91:26)
#3      Msix._printMsixOutputLocation (package:msix/msix.dart:141:42)
#4      Msix.create (package:msix/msix.dart:59:5)
<asynchronous suspension>
#5      main (file:///C:/tools/flutter/.pub-cache/hosted/pub.dartlang.org/msix-3.6.1/bin/create.dart:4:3)

If --output-path is not set, the build completes successfully. v3.5.1 works as expected, v3.6.0 is the first version where this starts to occur.
Note that the actual MSIX does get packaged and outputted to the right location, but it throws trying to print the path to the MSIX file. Since it returns an error, it causes CI/CD scripts to fail which is causing it to be a breaking change for us.

Hello @JagandeepBrar
I Publish new version (3.6.2) with a fix for that,
please check if it solves this problem for you.
Thank you for reporting this bug! 👍

Sorry for the delay but I can confirm that it 3.6.2 fixes the issue, thank you!


Fixed path for loading cookiecutter.json

Fixed path when loading an existing cookiecutter.json file issue #9313. Now passing in the template path and contents path in the values JsonObject.
Hey, I just made a Pull Request!

:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

I'll note also, that this PR needs a changeset.


AAD payment page not found [404]

hello,
i'm intereseted in taking AAD,but the payment link seems broken..
any idea ?

Hi @SheikhZayed,
I really don't know. Maybe could try inform them about the issue @AndroidDev and @udacity


2022-04-22 Security Debrief

Thanks for the feedback @stockandawe - how does the latest push look?

@tradesmanhelix , looks great. Just made a small change to remove the header since the title is included in the post


Add automatic-generated documentation

Related with #3
I think I should add more code examples and fix some typos in this PR, but for now it seems OK to me
Preview

Documentation? Sounds reasonable, very unlike aniyomi...


"encountered EOF while reading checksum" Exception when working with large compressed data files

When running on an EMR Cluster and pulling files from s3 we are experiencing an issue trying to map large compressed data files.
The issue is in the CompressionInputStream. When reading the checksum you check to see that 4 bytes were read. However sometimes less bytes may have been read and no attempt is made to see if there are more bytes available.
We have implemented a fix for this, I can submit a pull request if you want.
The fix is to replace:
    private void readInput(int length) throws IOException {
        int offset = 0;
        while (offset < length) {
            int size = in.read(input, offset, length - offset);
            if (size == -1) {
                throw new EOFException("encountered EOF while reading block data");
            }
            offset += size;
        }
        // ignore checksum for now
        byte[] checksum = new byte[4];
        int size = in.read(checksum);

        if (size != 4) {
            throw new EOFException("encountered EOF while reading checksum");
        }

        valid = cm.compressor().uncompress(input, 0, length, buffer, 0);
        position = 0;
    }

with
    private void readInput(int length) throws IOException {
        int offset = 0;
        while (offset < length) {

            int size = in.read(input, offset, length - offset);
            if (size == -1) {
                throw new EOFException("encountered EOF while reading block data");
            }
            offset += size;
        }

        // ignore checksum for now
        readChecksum(4);

        valid = cm.compressor().uncompress(input, 0, length, buffer, 0);
        position = 0;
    }

    private void readChecksum(int length) throws IOException {
        byte[] checksum = new byte[length];
        int offset = 0;
        while (offset < length) {

            int size = in.read(checksum, offset, length - offset);
            if (size == -1) {
                throw new EOFException("encountered EOF while reading checksum. Chunk: " + cm.currentChunk() + ", length: " + cm.currentLength());
            }
            offset += size;
        }
    }

Thanks for the report and the pull request!


removed timestamp parameter

Remove the timestamp parameter used to define the to and from periods (using one parameter to generate another one was generating errors for the api generation).
Note: this PR also contains the changes done by @cdmNSIDE for the flexibilityZones and has to be merged after her PR.

Hello @pruN-SIDE :)
Can you change the destination of this PR (use the branch with the flexibility zones instead of "main") ? It will be much easier for us to do the review. Thanks

I would suggest another approach. This way we have lots of duplications in the file.
As far as I can see, the problem was that the timeStamp-definition was put in the parameters section but it should have been in the schemas-section.

Can you have a look at my PR and see if that solves the problem? Or otherwise detail the problems so we can find a better solution?

Not needed since timeStamp was moved to Schemas


UI color configuration refactor

Current UI color is scattered in the code that describes the UI components. Many components use hard-coded color which does not care about the overall look and feel in anyway and may not be configuration. One such example is, if you search for "Color.BLUE" you will likely get a tons of such hard coded color.
One possible solution for this is to refactor all the place that needs the color and use a seperate config file (xml or json, whatever) to describe those colors.
As a side note of how this can be implemented, ghidra instance always need an ApplicationLayout to start,
For example, the GhidraLauncher uses GhidraApplicationLayout class:

The application layout stores many whole-ghidra level directory structure:

So, when instantiating the GhidraApplicationLayout, we can use the dir info to find the color configuration file resided in the ghidra installation dir.
Then, we can instantiate a singleton called something like ColorConfig and parse the file (xml or json?) to get a configuration.
To ease the choice of color, we can just name the colors like "primary", "secondary", "foreground_default".
Whenever some class wants the color, it should query the singleton and get a color of a particular name.
In this way, if the LaF of java swing switched (just like in dark theme), we should also provide a new configuration of colors so that the colors switches accordingly.

Closed due to project restructuring. Now it should be here.


Make Seconds optional in TimePickers

Time pickers have hours minutes and seconds currently with no way to disable seconds - make seconds optional as hours & minutes and hours, minutes and seconds are both useful combinations

I Can Go With The Issue But I Need Some Mentoring To Solve The Issue

@Hirdey-1999 Sorry we missed this, I believe John already has an implementation of this in an internal repo, so it doesn't make sense for you to start on this.
In future I'll take issues that are reasonably appropriate for first time committers to Horologist with the "good first issue" label. This would have been one, but I missed your comment.

https://github.com/google/horologist/pull/194


Submit the SoS job submitter to a compute node

Similar to https://github.com/cumc/dsc/issues/5, in SoS we often have to submit a job to the cluster compute node that submits SoS tasks from there. An interface is proposed in the DSC ticket, and an implementation potentially will not need to involve SoS. But I'm opening this ticket just in case it is something better solved at SoS level.

I'd like to add that the login nodes at my cluster are often congested, so the SoS job submitter runs very slowly. Forwarding the job submitter to a compute node would likely considerably speed up my runs and not annoy my fellow users.

For this particular request, what you want to do was

execute a workflow on a computing node (not a task), presumably requesting a single node.
let the workflow submit tasks, which creates new PBS jobs that requests additional nodes.

I never tried this but with the right hosts.yml file, the computing nodes should be able to ssh to headnode and submit jobs, right? What is the problem here?
Also I think the cluster-executing mode was designed to avoid the trouble by

submit a workflow, requesting multiple nodes.
multiple sos instances are started and the master one will send jobs to the workers.

This would be conceptually easier and more efficient if there are many small substeps.

If the purpose.is to submit tasks from computing nodes, we may have to

On the cluster definition, define both workflow_template and task_template. The workflow_template will be used to execute workflow on computing node, and task_template will be needed to submit tasks.

On the head node, execute

sos run myworkflow -r cluster -q cluster

Because cluster is defined as a PBS queue, the workflow will be submitted using a template (workflow_template).

Hopefully, the workflow would be executed on computing node as command

sos run myworkflow -q cluster

which will then submit jobs to the cluster.
These should all in theory work after recent improvement on remote execution (#1418, not yet released). I will create a test case and try it on our cluster.

It is working. Here is how to reproduce,

Under test, run build_test_docker.sh, which will start a docker instance and a configuration file ~/docker.yml, with the following text (port number will vary, and with unrelated hosts removed)

localhost: localhost
remote_user: root
hosts:
    localhost:
        description: localhost
        address: localhost
        paths:
            home: /Users/bpeng
    docker:
        address: "{remote_user}@localhost"
        port: 55004
        paths:
            home: "/{remote_user}"
    ts:
        description: task spooler on the docker machine
        based_on: hosts.docker
        queue_type: pbs
        status_check_interval: 5
        task_template: |
            #!/bin/bash
            # {task}
            cd {cur_dir}
            sos execute {task} -v {verbosity} -s {sig_mode} {'--dryrun' if run_mode == 'dryrun' else ''}
        max_running_jobs: 100
        submit_cmd: tsp -L {job_name} sh {job_file}
        status_cmd: tsp -s {job_id}
        kill_cmd: tsp -r {job_id}
        workflow_template: |
            #!/bin/bash
            #
            {command}

Note that the cluster (in this case docker/ts) needs to have sos-pbs installed, so that the tasks could be submitted as a PBS

Have a workflow with a task

task:
sh:
   echo this is task.

Submit the workflow with command

sos run test -c ~/docker.yml -r ts -q ts

What will happen is that
a. A script will be submitted as a workflow to docker
#!/bin/bash
#
sos run /root/vatlab/sos/test/test.sos -q ts -c ~/.sos/tmp3xv_vygv.yml

b. When the workflow is executed, a second job will be submitted with script
#!/bin/bash
# b64cd2a6a63ed501
cd /root
sos execute b64cd2a6a63ed501 -v 2 -s default

This example is simple but I suppose the key elements are there.
@gaow Let me know if this scenario helps.

I tried running a job using your template as an example on a SLURM cluster, but nothing shows up in sos status on my local machine or the cluster. All I can find is
[pgc29@c19n08 ~]$ sacct -j 45256211
       JobID    JobName  Partition    Account  AllocCPUS      State ExitCode
------------ ---------- ---------- ---------- ---------- ---------- --------
45256211     60435cb54+    general pgc29          1     FAILED      1:0
45256211.ba+      batch            pgc29          1     FAILED      1:0
45256211.ex+     extern            pgc29          1  COMPLETED      0:0

Where can I get more debug info for these types of jobs if not sos status?

@pgcudahy I got an email notification but did not see your post here.
The remote execution feature is currently not very user friendly because there is no way to check the status and stdout/err of remote workflows. I am aware of the problem (#1420) but do not know how to address it yet.
That said, you can manually check the status by checking the output of the workflow from the output captured by SLURM, and see what went wrong. It is also possible that the job was not submitted correctly due to lack of WALLTIME etc, which should be specified from command line.
I will try again today on a PBS system and post a configuration file for a real cluster, and have a harder look at #1420.

Thank you. I deleted my post because I'm having some issues with my jobs using both the task queue method I was using before and this new method since upgrading to 0.22.3 and wanted to try and untangle what was specific to this issue.

I am sorry about that. There have been some changes to the use of named path, basically absolute local paths are no longer translated (#1417), but the change might have introduced other bugs. I will be happy to have a look at your script / configuration if you cannot figure out what caused the problem.

Just to report my progress.
On a true PBS cluster, I have the definition:
host:
  hpc:
    based_on: hosts.cluster
    queue_type: pbs
    status_check_interval: 30
    wait_for_task: false
    modules: []
    max_running_jobs: 500
    submit_cmd: qsub {job_file}
    status_cmd: qstat {job_id}
    kill_cmd: qdel {job_id}
    task_template: |
      #!/bin/bash
      #PBS -N {task}
      #PBS -l nodes={nodes}:ppn={cores}
      #PBS -l walltime={walltime}
      #PBS -l vmem={mem//10**9}GB
      #PBS -o /home/{user_name}/.sos/tasks/{task}.out
      #PBS -e /home/{user_name}/.sos/tasks/{task}.err
      #PBS -m ae
      #PBS -M<EMAIL_ADDRESS>      #PBS -v {workdir}

      module load {' '.join(modules)}

      {command}
    workflow_template: |
       #!/bin/bash
       #PBS -N {job_name}
       #PBS -l nodes={nodes}:ppn={cores}
       #PBS -l walltime={walltime}
       #PBS -l vmem={mem}
       #PBS -o /home/{user_name}/.sos/workflows/{job_name}.out
       #PBS -e /home/{user_name}/.sos/workflows/{job_name}.err
       #PBS -m ae
       #PBS -M<EMAIL_ADDRESS>
       module load {' '.join(modules)}
       {command}

From sos notebook with the following workflow
%run -q hpc -r hpc mem=2GB cores=1 walltime=00:10:00 nodes=1

input: for_each=dict(i=range(2))
output: f'test_{i}.txt'

task: expand=True, walltime='10m', cores=1, mem='1G'
sh:
    echo `pwd` > {_output}
    echo I am {i} >> {_output}

The workflow is correctly submitted to the cluster, which results in a directory ~/.sos/workflows/ and some related files. The .sh file is the shell script, the .err file is the error.
I got error
INFO: Running default:
qsub: Job rejected by all possible destinations (check syntax, queue resources, ...)
WARNING: Check output of qsub ~/.sos/tasks/9e83077913e509c3.sh failed: Command 'qsub ~/.sos/tasks/9e83077913e509c3.sh' returned non-zero exit status 193.
ERROR: Failed to submit task 9e83077913e509c3:

And the jobs are pending
$ sos status
9e83077913e509c3	86bbadb568b7e0ab default u233771	              	pending
a62dceff0a12a526	86bbadb568b7e0ab default u233771	              	pending

The jobs can be submitted manually:
$ qsub ~/.sos/tasks/a62dceff0a12a526.sh
2276807.radiation.dldcc.bcm.edu
$ sos status
9e83077913e509c3	86bbadb568b7e0ab default u233771	              	pending
a62dceff0a12a526	86bbadb568b7e0ab default u233771	Ran for 0s    	completed

I guess that the qsub command is not available on the computing node, but we will see.

ok, just to update that with #1420, it is now possible to check the status of remote workflows using command
sos status -q host

or
sos status workflow_id -q host

or
sos status workflow_id -f -q host

here -f (for --full) is a new option that is the same as -v4, corresponding to qstat -f.
Also
sos kill -q host

and
sos purge -q host

should also work on remote workflows submitted via sos run -r host.
Now we are in a better position to figure out details on sos -r host -q host.

OK, the problem is that,
when the workflow is submitted to a computing node, it still get hold of the specified configuration file, and think it is on hpc. Therefore, when it tries to submit the task, it assumes that it is the "localhost" and try to submit the job from there, which will fail because qsub can only be executed from the headnode.
So the key is to let qsub executed on headnode...

The solution of this problem is to let the computing node "think" that they are not on the headnode. The trick is to

Define another cluster by adding

  hpc1:
    based_on: hosts.hpc

to ~/.sos/hosts.yml`

Execute the workflow with command

%run -q hpc -r hpc1 mem=2GB cores=1 walltime=00:10:00 nodes=1 -s force

In this way, when the workflow is executed on hpc1, the localhost becomes hpc1.  When the workflow tries to submit tasks from computing nodes, it submit jobs to hpc, which is now considered to be a "remote host" so the qsub command is executed with ssh hpc qsub.
The output of the workflow is
!sos status wf40f6a95aff0e516 -q hpc -f
WORKFLOW:	wf40f6a95aff0e516
status	completed
Created 56 sec ago
Started 56 sec ago
Ran for 37 sec

TAGS:
=====
/home/u233771/BoPeng/.tmp_script_88wilxgq.sos

WRAPPER SCRIPT:
==============
#!/bin/bash
#PBS -N wf40f6a95aff0e516
#PBS -l nodes=1:ppn=1
#PBS -l walltime=00:10:00
#PBS -l vmem=2GB
#PBS -o /home/u233771/.sos/workflows/wf40f6a95aff0e516.out
#PBS -e /home/u233771/.sos/workflows/wf40f6a95aff0e516.err
#PBS -m ae
#PBS -M<EMAIL_ADDRESS>
module load
sos run /home/u233771/BoPeng/.tmp_script_88wilxgq.sos -q hpc -s force -c ~/.sos/config_hpc1.yml -M wf40f6a95aff0e516

STDERR:
=======
INFO: Running default:
Pseudo-terminal will not be allocated because stdin is not a terminal.
Pseudo-terminal will not be allocated because stdin is not a terminal.
INFO: t9c7c8ebda9545599 submitted to hpc with job id 2281199.radiation.dldcc.bcm.edu
Pseudo-terminal will not be allocated because stdin is not a terminal.
INFO: t4c814939abbe5590 submitted to hpc with job id 2281200.radiation.dldcc.bcm.edu
Pseudo-terminal will not be allocated because stdin is not a terminal.
INFO: t4c814939abbe5590 received 'test_1.txt' from hpc
INFO: t9c7c8ebda9545599 received 'test_0.txt' from hpc
INFO: default output:   test_0.txt test_1.txt in 2 groups
INFO: Workflow default (ID=wf40f6a95aff0e516) is executed successfully with 1 completed step, 2 completed substeps and 2 completed tasks.

I do not know if I should do anything to avoid the need to define hpc1.

The case was specifically handled so no aliasing of hpc is needed.
%run -q hpc -r hpc mem=2G cores=1 walltime=00:10:00 nodes=1 -s force

works.


Error during building

Run-time dependency wayfire found: NO (tried cmake)

meson.build:18:10: ERROR: Dependency lookup for wayfire with method 'pkgconfig' failed: Could not generate cflags for wayfire:
Package glm was not found in the pkg-config search path.
Perhaps you should add the directory containing `glm.pc'
to the PKG_CONFIG_PATH environment variable
Package 'glm', required by 'wf-config', not found

This turns up when I was running meson setup build --prefix=/usr, I've installed glm and wayfire packages (tried both AUR and chaotic-aur).

I think the basic problem is that, due to a change in glm, you should install cmake and then reinstall wayfire and pixdecor.

I'm still unable to build this, but anyway thx for ur efforts!

Thank you for following up. Do you still get the same error even after installing cmake before rebuilding wayfire and wf-config? If you can post the complete output starting with the command you're running to build, we might be able to spot the problem.

Actually I can't build wayfire manually, either. The built wayfire binary can't find wf-config

I see. It might be that you need to set LD_LIBRARY_PATH to the directory containing libwf-config.so. In any event, if you would like to try to fix it, we can keep communicating here, on IRC/Matrix/Discord or you can create a discussion on github.com/wayfirewm/wayfire.

Thanks for your advice, however I am currently busy and can just accept building from AUR.
I'll try to figure out the problem as soon as I have some free time.


cdl: Add pipeline barriers after AMD marker writes

From the spec:
While consecutive buffer marker writes with the same pipelineStage parameter are implicitly complete in submission order, memory and execution dependencies between buffer marker writes and other operations must still be explicitly ordered using synchronization commands. The access scope for buffer marker writes falls under the VK_ACCESS_TRANSFER_WRITE_BIT, and the pipeline stages for identifying the synchronization scope must include both pipelineStage and VK_PIPELINE_STAGE_TRANSFER_BIT.
Fixes #109

CI CrashDiagnosticLayer build queued with queue ID 280941.

CI CrashDiagnosticLayer build # 269 running.

CI CrashDiagnosticLayer build # 269 passed.


Older set C1/2/3 U1/2/3 Rarities

In older expansions, Arabian Nights - Alliances excluding Ice Age, cards were printed multiple times on the common and uncommon sheets, up to 3 times per sheet.

i wouldn't mind dropping the older sets, they were never meant to be drafted


wslConf: introduce extraOptions

Closes #559
Pretty much what it says on the tin

Maybe make it proper RFC42 then?

Should've read that earlier 😅
Naming-wise: Should the options be moved to wsl.settings or stay as wsl.wslConf then? While the first one would be more in the spirit of the RFC from what i gathered so far, it doesn't make it as clear that the values end up in /etc/wsl.conf

Maybe wsl.wslConf.settings?

Wouldn't that be redundant? All the options currently in wsl.wslConf are 1:1 representations of the config file entries anyway, just with checks attached. I would keep the checks in place and just convert the whole thing to a freeform type

I guess we could just keep wsl.wslConf then.

Done, seems to work just fine from my quick test


Session returning login_required

Form
Put an [x] if you meet the condition, else leave [ ].

[x] I've searched the Issues
[x] I've read the basic concepts
[x] I'm using the latest version

Question
A specific question, so it's understandable to anyone.
You may add pictures.
I'm trying to store and restore session, anyway as soon as I request something with ig.user.searchExact(), I get the "login_required" error. To do so, when I login, I store the session (as it is inside serialized). Then when I call login, before I check if I already have a session for that user, in which case I restore that and return the igapiclient associated. Thanks.
Code
await ig.simulate.preLoginFlow();
ig.request.end$.subscribe(() => {
      ig.state.serialize().then((serialized) => {
        delete serialized.constants;
        sessionHandler.updateSession(
          account.username,
          serialized,
        );
      });
    });
ig.account
        .login(account.username, account.password)
        .then((res) => {
          // The same as preLoginFlow()
          // Optionally wrap it to process.nextTick so we dont need to wait ending of this bunch of requests
          ig.simulate.postLoginFlow().then(() => {
            // done
          });
        })
...
private async login(): Promise<IgApiClient> {
    const ig = new IgApiClient();
    ig.state.generateDevice(account.username);
    if (sessionHandler.getSession(account.username)) {
      await ig.state.deserialize(
        sessionHandler.getSession(account.username),
      );
      return ig;
    }
   ... otherwise login again
    // Execute all requests prior to authorization in the real Android application
    // Not required but recommended
    await ig.simulate.preLoginFlow();
   ...
}

Error and Output
If you've got an error put it here.
You can get the stacktrace in the most environments using
Error.stack (MDN Docs).
YOUR WELL FORMATTED ERROR

IgLoginRequiredError: GET /api/v1/users/search/?timezone_offset=7200&q=randomuser&count=30 - 403 Forbidden; login_required
IgLoginRequiredError: GET /api/v1/users/search/?timezone_offset=7200&q=randomuser&count=30 - 403 Forbidden; login_required

same problem here

Same here, did anybody found a way to fix this?

same problem here, did anyone found a way to fix this?
"i moved session to hosting service"

Same but trying tu upload a video

same problem here


Specs that a string abort the test run.

CLJ specs exhibit the same behavior.  SpecFailures are not distinguished from other exceptions.

Doh!  I looks like convention is to treat errors like failures except in compilation/parse errors.


require future

While testing this shard, I noticed that future.cr needs to be explicitly required (require "./lib/concur/src/**") which is not mentioned on the readme (without explicitly requiring it, Future is not defined).
Example Solutions

require future inside concur.cr
rename concur.cr into channel.cr, move that and future.cr into a separate folder and create a new concur.cr that just requires them.

(Unless there's something wrong with my setup or explicitly requiring it is by design 😅)

Hey @GeopJr, thanks for raising this. You are right, the intention was for Future to be available as soon as one requires concur :+1:
I've published v1.0.2, where the issue should be fixed - hopefully I haven't messed anything else up in terms of namespace :sweat_smile:
Let me know if you notice anything else suspicious, and do feel free to open more issues, I'm really looking for some feedback on the usability of this shard :pray:

Thanks for the quick fix! 🙌
Future#on_complete (/success/error) is very useful so I'll probably end up using it on a few projects!


JTC trajectory end time validation fix

The time_from_start member for a JointTrajectoryPoint is monotonically increasing, not a delta time, so I think we can just use the last one in the vector; summing them up seems incorrect. I also moved the points empty check earlier because .back().time_from_start would seg fault with an empty points vector.

Could you please check the docs if this is clearly documented how to fill the trajectory field? Here is a comment, but maybe we should add this in a more prominent place.

Could you please check the docs if this is clearly documented how to fill the trajectory field? Here is a comment, but maybe we should add this in a more prominent place.

@christophfroehlich
That page seems clear to me, the plots in there are very helpful. Perhaps it should be in the main JTC page, but where it is seems fine IMO.

@christophfroehlich is there anything I can do to help get this across the finish line?

No, we have to wait for an approval of @destogl or @bmagyar


ARM build

Summary
Would be great to have a build that runs on ARM64/aarch64 architecture.
Motivation
This would enable Atom to be run on arm devices running linux such as various Pine64 devices, Librem 5 etc as well as new Apple products.
Describe alternatives you've considered
Only alternative right now would be to try to compile from source for that architecture. Not sure if that's currently possible.

+1, would love to use atom for editing notes on an old ARM chromebook.
Some previous discussions:
https://github.com/atom/atom/issues/7822
https://github.com/atom/atom/issues/15881
This old comment https://github.com/atom/atom/issues/7822#issuecomment-389575309 made me very optimistic:

Electron has been upgraded to 2.0.0 recently, now it has native working mksnapshot binaries for armv7l. Node.JS started working on armv7l binaries and I hope they'll release properly compiled binaries soon (if they didn't). I think my work is done and there is no use of me anymore. If Atom team want to make armv7l support, they realize it soon.

v2 Electron? I think Atom's currently trying to upgrade from version 9 to version 11...!


The Metrics BOM causes issues for projects depending transitively on Logback

Hi,
I have a project depending on the cassandra-all artifact (e.g. https://mvnrepository.com/artifact/org.apache.cassandra/cassandra-all/3.11.3). It has dependencies on logback-classic and logback-core.
When I add the Metrics BOM to my project, the logback-classic version is overridden to 1.2.3, but logback-core is left at 1.1.3.
I think either the BOM should only lock versions for the Metrics artifacts (as e.g. JUnit and Camel do https://mvnrepository.com/artifact/org.junit/junit-bom/5.2.0, https://mvnrepository.com/artifact/org.apache.camel/camel-bom/2.22.0) and not all dependencies, or the BOM should set logback versions for all 3 artifacts (logback-core, logback-classic and logback-access) from the Logback project.

I think the general approach for BOMs seems to be that they should only manage the versions of a project's own artifacts, not the versions of its transitive dependencies.

This should be addressed in 4.0-maintenance, 4.1-development, and 5.0-development.


ConfigFactory.invalidateCaches() also resets environment variables cache

While in production you are unlikely to modify environment variables on the fly (it's very difficult to do so), it's helpful to be able to do so in testing to ensure that you've configured your application correctly and it responds appropriately to environment variable change.

Hi @camullen,
Thank you for your contribution! We really value the time you've taken to put this together.
Before we proceed with reviewing this pull request, please sign the Lightbend Contributors License Agreement:
http://www.lightbend.com/contribute/cla

Thanks, looks good. I don't have access to see if you clicked through the CLA, so let me know.

I clicked through
On Wed, Mar 22, 2017 at 12:13 PM Havoc Pennington<EMAIL_ADDRESS>wrote:

Thanks, looks good. I don't have access to see if you clicked through the
CLA, so let me know.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/typesafehub/config/pull/464#issuecomment-288508396,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACqTAywcF0cfffdCOyEamEqjMg7DPPUnks5roXLCgaJpZM4MlDx8
.

--
Cameron Mullen
Founder & CEO - Skio
+1<PHONE_NUMBER>
<EMAIL_ADDRESS>

Thanks for the fix!


Printables for verification preconditions

Continuation of #2527
Additions include unit test for assume and Scaladoc group for internal macros
Contributor Checklist

[ ] Did you add Scaladoc to every public function/method?
[ ] Did you add at least one test demonstrating the PR?
[ ] Did you delete any extraneous printlns/debugging code?
[ ] Did you specify the type of improvement?
[ ] Did you add appropriate documentation in docs/src?
[ ] Did you state the API impact?
[ ] Did you specify the code generation impact?
[ ] Did you request a desired merge strategy?
[ ] Did you add text to be included in the Release Notes for this change?

Type of Improvement

API Impact

Backend Code Generation Impact

Desired Merge Strategy

Release Notes

Reviewer Checklist (only modified by reviewer)

[ ] Did you add the appropriate labels?
[ ] Did you mark the proper milestone (Bug fix: 3.4.x, [small] API extension: 3.5.x, API modification or big change: 3.6.0)?
[ ] Did you review?
[ ] Did you check whether all relevant Contributor checkboxes have been checked?
[ ] Did you do one of the following when ready to merge:

[ ] Squash: You/ the contributor Enable auto-merge (squash), clean up the commit message, and label with Please Merge.
[ ] Merge: Ensure that contributor has cleaned up their commit history, then merge with Create a merge commit.

The ScalaDoc still leaves much to be desired (see screenshot below). Compare it to how things are grouped on UInt (https://javadoc.io/doc/edu.berkeley.cs/chisel3_2.13/latest/chisel3/UInt.html).
Can we:

Make sure every _applyMacro... function is in the VerifPrintMacros group?
Ensure the warning description of VerifPrintMacros shows up?
Put VerifPrintMacros below the "Ungrouped" group?

ScalaDoc looks great, thanks!


TST: test DCT and DST for given dtype

What does this implement/fix?

The test of DCT and DST is parametrized, giving different data types,
this variable is, however, never used.
This changes the input data to the according data type the same way test_identity_nd_overwrite does.
Additional information

Thanks @DerWeh, merged.


Update kernel/firmaware

- What I did
- How I did it

@kraj I can't seem to find much information on what the latest version of the RPI firmware is. I see some tags, in some repos, but I can't seem to figure it out.
I was wondering if you could help me to understand why you are updating to the buster version of the firmware and not the latest version of bullseye?
It is my understanding that if we are on the 6.1.54 kernel for the yocto recipe, we would want to also have the bullseye firmware as it will support that kernel (as opposed to 5.x.x version for buster).
I have tried the latest bullseye and it works just fine. Should I expect issues? or should I be fine?
https://github.com/RPi-Distro/firmware/blob/pios/bullseye/debian/changelog
https://github.com/raspberrypi/firmware/releases/tag/1.20230405

You should be fine if it tests out fine infact post a pull here as well

Sounds good thanks, we've been testing quite a bit if don't see any issues I might open a PR.


ENH: Add version test

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

Okay replicated WARNING: Package(s) not found: openmeeg. Probably need to fix openmeeg to fix this actually


Mouse action move should raise window

Steps to reproduce issue
# required configuration
yabai -m config focus_follows_mouse autofocus
yabai -m config mouse_modifier fn
yabai -m config mouse_action1 move

Tile two windows
Raise one window by clicking on it
Move mouse over other window to focus it, but do not raise it
Hold down fn and try to move the window over raised (but unfocused window) to swap their positions

This currently does not work because the focused window gets moved under the raised window.
Proposed fix
The mouse action move should raise the window that gets moved.

No need to raise the window. Fixed on master.

Changed the title accordingly. Thanks for the quick fix.


Project should target RFC5545 and possibly RFC7265

Hey this may just an oversight but I noticed the readme said:

It's aimed at providing full RFC 2445 compliance

RFC 2445 was made obsolete by RFC5545 so we should probably target that instead. Also, I was wondering if there was a roadmap to use jCal according to (RFC7265)?
https://tools.ietf.org/html/rfc5545
https://tools.ietf.org/html/rfc7265

From @terebi42 in #96

https://tools.ietf.org/html/rfc7529
https://stackoverflow.com/questions/35757778/rrule-for-repeating-monthly-on-the-31st-or-closest-day

267ecadb84c94f8260b50c029a43f9a2f943581b


Gripper 85 bug when changing force

Hello,
Thank you for this model!
I am working on an simulation where I need to modify the force in the gripper, so in the ControlGripper method that you provide, I changed the value of the force. Specifically I change the variable desired_force in the following parts:

p.setJointMotorControl2(robotID, parent.id, controlMode, targetPosition=pose, force=desired_force, maxVelocity=parent.maxVelocity)

p.setJointMotorControl2(robotID, child.id, controlMode, targetPosition=childPose, orce=desired_force, maxVelocity=child.maxVelocity)

I have tried different force values but I have the behavior that you can see in the image, where some of the parts of the gripper are not attached when I try to grab an object. Are there some parameter in the urdf that I must change?

Hi @cyd8a18 ,
Thank you for reaching me.
It's a known issue, which we can not 100% avoid.
First, can you confirm that you are using the code from the robotflow branch, instead of the main branch?
Second, can you tell me the value of desired_force?

Thank you for your quick reply. Regarding your questions:

I made a mistake and I was using the wrong code, I changed to robotflow branch
I have tried different values for desired_force as 5, 25, 50.

I don't have the same behavior anymore. However, when i tried to open and close (using the same code that you have), the gripper moves from one side to the other as you can see in the following image:

Do you have any suggestion to solve this problem?

Hi @cyd8a18 ,
Sorry for the late reply. I am quite busy these days.
I think this problem may come from the non-convex objects that you add to the environment.
Are they decomposed? (See section V-HACD in https://docs.google.com/document/d/10sXEhzFRSnvFcl3XxNGhnD4N2SedqwdAvK3dsihxVUA/edit#)
Can you try removing them totally?


Add support for USB/GSM modem dongles

Fix for issue 484
This is important to allow hassio installation to be able to send notifications while offline using SMS.
More info here
This change does 2 things:

Install the drivers for USB modems.
Install usb_modeswitch to deal with dual mode USB devices. More info here

Size impact: (Measured in VDI image)
70.26 Kb which is increase of 0.040%
Test:
Tested on a VDI virtual appliance with this device
After this change the modem is visible to hassio.

How do you now use that modem connection?

Usb_modeswitch does not interact with network or modem manager, it interacts with udev to setup new USB serial devices under /dev/
I will post details on how we are using this from home assistant

Using something like this would be easier for everyone: https://www.home-assistant.io/components/netgear_lte/

I actually using one, and there are multiple reasons why this will not work for everyone:

Cost, this device is hundreds of dollars  VS 30 bucks.
Power consumption, ideally you want to have power backup, now you need to feed power to 2 devices instead of just one.
This is a terrible switch, I have a 1gigabit/s service and it can only route about 200mbit/s
GSM service: I use my netgear with google fi as backup but Google fi does not support SMS and their data Sims.
Complexity, more points of failure, if the internet is down of if the netgear is down, then you won't actually be able to get notifications.

I am also planning on writing a proper SMS integration for home assistant to make it super simple for everyone. But I need to ensure that such integration will work in All flavors of home-assistant.
Hassos is the only flavor will that this won't work today.

You need this to send SMS only?

This is the complete use case in with this fix on homeassistant:
send_sms.sh script:
#!/bin/bash

DEST=$1
# Modify the MD variable to match your hardware configuration
MD="/dev/ttyUSB0"

if [ -z "$2" ]
then
    read message
else
    message="$2"
fi

echo "Sending $message to $DEST"

echo "AT+CMGF=1" > $MD
sleep 1
echo "AT+CMGS=\"$DEST\"" "OK" > $MD
sleep 1
echo "$message^Z" > $MD

configuration.yaml:
notify:
  - platform: command_line
    name: sms_person1
    command: !secret notify_sms_person1
  - platform: command_line
    name: sms_person2
    command: !secret notify_sms_person2

secret.yaml:
notify_sms_person1: "/config/send_sms.sh +1NNNNNNNNNN"
notify_sms_person2: "/config/send_sms.sh +1NNNNNNNNNN"

Discussion about this integration here

I will ask someone to test that with an RFlink adapter. Since we did not know what the bug affected with USB dongles, I'm a bit carefully.

This change is a "pay for play" change, and even then, this is only affecting if the new serial port is referenced by home-assistant configuration.
I will try to get a hold of a RF stick, do you know where I can buy one?

Here is nmcli con show:

Here is nmcli:

I have read the warning about ModemManager, I also happen to use a dual dongle for Z-Wave and ZigBee, and given that this change does not interact with the modemmanager or the networkmanager, I wont interfere with RFLink also.

You can approve that:

Zwave/Zigbee is working (on HA)
The use case is solved and working on HA

Everything working as runtime module in the kernel:


Niko Home Control : TypeError: string indices must be integers

Hi, i wanted to try and setup the new platform "Niko Home Control" but i receive the error below whan i start HA
any idea whats wrong?
2018-12-13 14:30:08 ERROR (MainThread) [homeassistant.components.light] Error while setting up platform niko_home_control
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/homeassistant/helpers/entity_platform.py", line 128, in _async_setup_platform
    SLOW_SETUP_MAX_WAIT, loop=hass.loop)
  File "/usr/local/lib/python3.6/asyncio/tasks.py", line 358, in wait_for
    return fut.result()
  File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/light/niko_home_control.py", line 44, in setup_platform
    [NikoHomeControlLight(light, hub) for light in hub.list_actions()],
  File "/usr/local/lib/python3.6/site-packages/nikohomecontrol/_init_.py", line 35, in list_actions
    return [Action(action, self) for action in self.list_actions_raw()]
  File "/usr/local/lib/python3.6/site-packages/nikohomecontrol/_init_.py", line 35, in <listcomp>
    return [Action(action, self) for action in self.list_actions_raw()]
  File "/usr/local/lib/python3.6/site-packages/nikohomecontrol/_init.py", line 86, in __init_
    self._id = action['id']
TypeError: string indices must be integers

What does your config look like? What version of Home Assistant?

tried it with 82.x 83.x and 84.x
config is quite basic, just like this
light:

platform: niko_home_control
host: <IP_ADDRESS>

also tried manually specifiying port, but didnt help either
also in debug log, i see this :
2018-12-13 14:54:41 INFO (MainThread) [homeassistant.components.light] Setting up light.niko_home_control
but then that error afterwards

anyone that can help me with this? what info do you guys need?

Hi, i have the same issue. Did you find a way to setup NHC with HA ?

Nope, not working, also opened a thread on forum, but no reply either

I have this error in the logs:
File "/usr/local/lib/python3.6/json/decoder.py", line 355, in raw_decode
obj, end = self.scan_once(s, idx)
json.decoder.JSONDecodeError: Expecting ',' delimiter: line 1 column 1339 (char 1338)
I looked for the decoder.py but i cannot find the folder python3.6
Same for this file(niko_home_control.py)  :
/usr/local/lib/python3.6/site-packages/homeassistant/components/light/niko_home_control.py
Do you know how to find them ? Via putty, i dont see them.

i didnt troubleshoot any further
your error is different though?

hi, when will this component be ready for use?

Hello, I don't know if the component have been updated. But i tried it last WE  but still the same issue.
I suppose it's not so easy to adapt it .
I think the problem is that i don't only have lights devices defined for the smartphone (in NHC), but also shutters.

Don't think there was an update since release... It's strange they even did release it

I guess there hasn't been any progress regarding this issue. Just updatet to version 0.89.1 but still get the same error as described in issue #20005

Nope, never worked, seems it was not tested before it get released

Anyone who's been able to get this to work?
It looks like OpenHAB has a nice binding going on at the moment:
https://www.openhab.org/addons/bindings/nikohomecontrol/
I'm thinking about running OpenHAB on another Raspberry PI and using it as a gateway for Niko Home Control, connecting OpenHAB and Home Assistant through MQTT.

nope
you using niko 1 or 2 ?
seems this platform is created for v1 only

I'm using Niko Home Control 1.
(I have a controller and IP Interface from the 1st generation > incompatible with NHC2)

yeah, ,not sure why this platform was introduced, it never worked
i asked developer here : https://github.com/NoUseFreak/niko-home-control/issues/7

Thank you, pergolafabio.
Ideally I'd like to have everything work in Home Assistant of course, but it seems that only lights are supposed to be supported right now. It would be interesting if they had a look at the OpenHAB binding. They've managed to make their binding compatible with lights, dimmers, thermostats, blinds, power sockets (?), ... (also NHC V1)

ah, so you have lights working in Home Assistant , coming from Niko V1 ?
so you dont have the error that i posted in the first reply ?
what did you do to make it work?

No, I might not have been clear enough. I haven't gotten the lights to work. It's just that only the lights are in scope of this project and are SUPPOSED to work.

Ah ok ;)

Anyone who's been able to get this to work?
It looks like OpenHAB has a nice binding going on at the moment:
https://www.openhab.org/addons/bindings/nikohomecontrol/
I'm thinking about running OpenHAB on another Raspberry PI and using it as a gateway for Niko Home Control, connecting OpenHAB and Home Assistant through MQTT.

I have it up and running in OpenHAB. Working very well. But since I have my whole configuration in Home Assistant, I would like to use it in Home Assistent directly.
When you got the MQTT working, please let me know. That would be an option as well but the problem is that I'm totally not into MQTT. I don't have any clue on how to use it :-)
Regards
Vincent

Hi Vincent. Setup in OpenHAB works perfectly fine, indeed. Almost everything was autodetected after installing the OpenHAB binding. The only thing missing were my switched power sockets.
I've quickly tried playing around with MQTT as well and was able to set up a connection to the MQTT broker I've got running in HomeAssistant (Mosquitto): all the MQTT devices I've got set up in there were automatically discovered by OpenHAB, but none of my "things" in OpenHAB get published to the MQTT broker, meaning I can't see/manipulate them in HomeAssistant. Maybe I need to map my "things" to MQTT objects in some way?!

closed => https://github.com/home-assistant/home-assistant/pull/23093

@NoUseFreak
this was merged in 92.0 ? well we did update, but the same error in log file as in post 1 ?

error from log 👍
2019-04-25 13:03:38 ERROR (MainThread) [homeassistant.components.light] Error while setting up platform niko_home_control
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/homeassistant/helpers/entity_platform.py", line 126, in _async_setup_platform
SLOW_SETUP_MAX_WAIT, loop=hass.loop)
File "/usr/local/lib/python3.7/asyncio/tasks.py", line 416, in wait_for
return fut.result()
File "/usr/local/lib/python3.7/site-packages/homeassistant/components/niko_home_control/light.py", line 43, in async_setup_platform
NikoHomeControlLight(light, niko_data) for light in nhc.list_actions()
File "/usr/local/lib/python3.7/site-packages/nikohomecontrol/nikohomecontrol.py", line 36, in list_actions
return [Action(action, self) for action in self.list_actions_raw()]
File "/usr/local/lib/python3.7/site-packages/nikohomecontrol/nikohomecontrol.py", line 36, in
return [Action(action, self) for action in self.list_actions_raw()]
File "/usr/local/lib/python3.7/site-packages/nikohomecontrol/nikohomecontrol.py", line 77, in init
self._id = action['id']
TypeError: string indices must be integers

error from log 👍
2019-04-25 13:03:38 ERROR (MainThread) [homeassistant.components.light] Error while setting up platform niko_home_control
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/homeassistant/helpers/entity_platform.py", line 126, in _async_setup_platform
SLOW_SETUP_MAX_WAIT, loop=hass.loop)
File "/usr/local/lib/python3.7/asyncio/tasks.py", line 416, in wait_for
return fut.result()
File "/usr/local/lib/python3.7/site-packages/homeassistant/components/niko_home_control/light.py", line 43, in async_setup_platform
NikoHomeControlLight(light, niko_data) for light in nhc.list_actions()
File "/usr/local/lib/python3.7/site-packages/nikohomecontrol/nikohomecontrol.py", line 36, in list_actions
return [Action(action, self) for action in self.list_actions_raw()]
File "/usr/local/lib/python3.7/site-packages/nikohomecontrol/nikohomecontrol.py", line 36, in
return [Action(action, self) for action in self.list_actions_raw()]
File "/usr/local/lib/python3.7/site-packages/nikohomecontrol/nikohomecontrol.py", line 77, in init
self._id = action['id']
TypeError: string indices must be integers

if we remove the IP address from config, the error is gone
but how to see lights?

Anybodu got this to work with the new version 0.92.0?
I still get an error:
2019-04-26 22:23:33 ERROR (MainThread) [homeassistant.components.light] Error while setting up platform niko_home_control Traceback (most recent call last):   File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/helpers/entity_platform.py", line 126, in _async_setup_platform     SLOW_SETUP_MAX_WAIT, loop=hass.loop)   File "/usr/lib/python3.5/asyncio/tasks.py", line 400, in wait_for     return fut.result()   File "/usr/lib/python3.5/asyncio/futures.py", line 293, in result     raise self._exception   File "/usr/lib/python3.5/asyncio/tasks.py", line 241, in _step     result = coro.throw(exc)   File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/niko_home_control/light.py", line 37, in async_setup_platform     await niko_data.async_update()   File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/niko_home_control/light.py", line 113, in async_update     self._nhc.list_actions_raw)   File "/usr/lib/python3.5/asyncio/futures.py", line 380, in __iter__     yield self  # This tells Task to wait for completion.   File "/usr/lib/python3.5/asyncio/tasks.py", line 304, in _wakeup     future.result()   File "/usr/lib/python3.5/asyncio/futures.py", line 293, in result     raise self._exception   File "/usr/lib/python3.5/concurrent/futures/thread.py", line 55, in run     result = self.fn(*self.args, **self.kwargs)   File "/srv/homeassistant/lib/python3.5/site-packages/nikohomecontrol/nikohomecontrol.py", line 33, in list_actions_raw     return self._command('{"cmd":"listactions"}')   File "/srv/homeassistant/lib/python3.5/site-packages/nikohomecontrol/nikohomecontrol.py", line 51, in _command     data = json.loads(self.connection.send(cmd))   File "/usr/lib/python3.5/json/__init__.py", line 312, in loads     s.__class__.__name__)) TypeError: the JSON object must be str, not 'bytes'
When I remove the IP address I get an invalid configuration notification even though the host parameter is said to be optional on the component page of the Niko component.

Hi Raphael
I have the same issue...
Regards
Vincent

Hi Vincent, Raph, Fabio,
I just upgraded to 0.92.0 as well and my lights are coming up as entities.
I had to specify the IP address of my Niko IP Interface, though. Otherwise I was getting a config error.
I'm currently playing around a bit and a "bug" I've immediately noticed, is that there is a significant delay in the reading of the state (on/off) of my lights. This means that - if you want to change the state in Home Assistant, while the current state hasn't been updated yet - the action will fail.
The lights also seem to only support simple on/off state changes. No dimming.

Yes, state is not implemented yet, will be better in newer release, this version was just a bugfix...
Strange that it works on your end...

Are you not even seeing the entities coming up, after changing configuration?
Have you specified the IP address of the Niko IP Interface and performed a restart of Home Assistant?

Yes , well Vincent did, I don't have Niko, just helping... Tried with and without ip address and offcourse restarted Hassio, still the same error as in first post

I just found out some of my lights are NOT detected after all.
Will try to find out what the difference is in my Home Control config and will report back ...

@pergolafabio It was indeed merged into 0.92.0
@Microfi I am aware of the delays of the states. Can you verify the missing lights are dimmable? These are expected not to work as NHC1 does not support these. They also don't show up in the Official NHC app.

@raphk82 Can you verify your installation is v1, I'm unable to reproduce your error?

@Microfi I am aware of the delays of the states. Can you verify the missing lights are dimmable? These are expected not to work as NHC1 does not support these. They also don't show up in the Official NHC app.

You're absolutely correct. They don't show up in the app either.
Do you know whether there is some kind of workaround to get them integrated anyway?
I see that the people at OpenHAB have been able to integrate dimmers as well: https://www.openhab.org/v2.2/addons/bindings/nikohomecontrol/

But what about the error as in 1st post? What could it be?

@raphk82 Can you verify your installation is v1, I'm unable to reproduce your error?

@NoUseFreak : Yes according to my iOs app I'm running version <IP_ADDRESS>209 of Niko Home Control and API 1.19.

@legovaer Did you have any luck reproducing this issue. From the error, it seems the action is decoded as a string instead of a list. I'm unable to get this in my current setup.
For reference, I only use lights and switches.


The 'opencivicdata' app is missing an init.py

This addition makes opencivicdata a proper Python package
Its absence can cause strange errors like this: http://stackoverflow.com/questions/35838989/runtimeerror-list-must-be-none-or-a-list-not-class-str-while-trying-to-s

Hey!
IIRC is actually a PEP 420 implicit namespace package, was it causing a
particular issue?
On Dec 16, 2016 7:49 PM, "Tobias McNulty"<EMAIL_ADDRESS>wrote:

This addition makes opencivicdata a proper Python package
Its absence can cause strange errors like this:
http://stackoverflow.com/questions/35838989/runtimeerror-list-must-be-
none-or-a-list-not-class-str-while-trying-to-s
http://stackoverflow.com/questions/35838989/runtimeerror-list-must-be-none-or-a-list-not-class-str-while-trying-to-s

You can view, comment on, or merge this pull request online at:
https://github.com/opencivicdata/python-opencivicdata-django/pull/67
Commit Summary

add missing init.py

File Changes

A opencivicdata/init.py
https://github.com/opencivicdata/python-opencivicdata-django/pull/67/files#diff-0
(1)

Patch Links:

https://github.com/opencivicdata/python-opencivicdata-django/pull/67.
patch
https://github.com/opencivicdata/python-opencivicdata-django/pull/67.
diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/opencivicdata/python-opencivicdata-django/pull/67,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAfYrMaCNpmm5B31Rgm22pcQ_hB7IMdks5rIzGVgaJpZM4LPuUt
.

Hey James! Yes, the missing init.py causes celery's auto discovery to
die with an error like the one mentioned in the stack overflow post.
On Dec 16, 2016 10:34 PM, "James Turk"<EMAIL_ADDRESS>wrote:

Hey!
IIRC is actually a PEP 420 implicit namespace package, was it causing a
particular issue?
On Dec 16, 2016 7:49 PM, "Tobias McNulty"<EMAIL_ADDRESS>wrote:

This addition makes opencivicdata a proper Python package
Its absence can cause strange errors like this:
http://stackoverflow.com/questions/35838989/runtimeerror-list-must-be-
none-or-a-list-not-class-str-while-trying-to-s
<http://stackoverflow.com/questions/35838989/runtimeerror-list-must-be-
none-or-a-list-not-class-str-while-trying-to-s>

You can view, comment on, or merge this pull request online at:
https://github.com/opencivicdata/python-opencivicdata-django/pull/67
Commit Summary

add missing init.py

File Changes

A opencivicdata/init.py
<https://github.com/opencivicdata/python-opencivicdata-django/pull/67/
files#diff-0>
(1)

Patch Links:

https://github.com/opencivicdata/python-opencivicdata-django/pull/67.
patch
https://github.com/opencivicdata/python-opencivicdata-django/pull/67.
diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/opencivicdata/python-opencivicdata-django/pull/67,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AAAfYrMaCNpmm5B31Rgm22pcQ_hB7IMdks5rIzGVgaJpZM4LPuUt>
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/opencivicdata/python-opencivicdata-django/pull/67#issuecomment-267740294,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJxhCFm0p5awShwmu1Zk_huJ_a8pnJ7ks5rI1g2gaJpZM4LPuUt
.

Hmm, OK.
We'll have to look into a solution that allows opencivicdata.divisions to
still be packaged separately since a lot of things depend on the current
setup.
Hmm, I wonder if there's a workaround from celery's side or if using an
old-style namespace package will work here.
On Sat, Dec 17, 2016 at 4:34 PM, Tobias McNulty<EMAIL_ADDRESS>wrote:

Hey James! Yes, the missing init.py causes celery's auto discovery to
die with an error like the one mentioned in the stack overflow post.
On Dec 16, 2016 10:34 PM, "James Turk"<EMAIL_ADDRESS>wrote:

Hey!
IIRC is actually a PEP 420 implicit namespace package, was it causing a
particular issue?
On Dec 16, 2016 7:49 PM, "Tobias McNulty"<EMAIL_ADDRESS>wrote:

This addition makes opencivicdata a proper Python package
Its absence can cause strange errors like this:
http://stackoverflow.com/questions/35838989/runtimeerror-list-must-be-
none-or-a-list-not-class-str-while-trying-to-s
<http://stackoverflow.com/questions/35838989/
runtimeerror-list-must-be-
none-or-a-list-not-class-str-while-trying-to-s>

You can view, comment on, or merge this pull request online at:
https://github.com/opencivicdata/python-opencivicdata-django/pull/67
Commit Summary

add missing init.py

File Changes

A opencivicdata/init.py
<https://github.com/opencivicdata/python-opencivicdata-django/pull/67/
files#diff-0>
(1)

Patch Links:

https://github.com/opencivicdata/python-opencivicdata-django/pull/67
.
patch
https://github.com/opencivicdata/python-opencivicdata-django/pull/67
.
diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<https://github.com/opencivicdata/python-opencivicdata-django/pull/67
,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AAAfYrMaCNpmm5B31Rgm22pcQ_hB7IMdks5rIzGVgaJpZM4LPuUt>
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/opencivicdata/python-opencivicdata-django/pull/67#
issuecomment-267740294>,
or mute the thread
<https://github.com/notifications/unsubscribe-
auth/AAJxhCFm0p5awShwmu1Zk_huJ_a8pnJ7ks5rI1g2gaJpZM4LPuUt>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/opencivicdata/python-opencivicdata-django/pull/67#issuecomment-267788341,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAfYvaUFRCDXXY4Gs_CKmTpn5kvFuuxks5rJFV2gaJpZM4LPuUt
.

Ah, didn't realize that. There's no particular urgency from my side so I'll close this for now. I just touch the file manually in my virtualenv and all is well.


Cleanliness and standards compliance

The code so far needs to be brought in-line with our code style. This includes, but is not limited to:

Linting and formatting
Removing unused modules
Documentation

I would like a make file that gives us a make format command.

We have a make format command :rocket: and the green checkmarks


Print the dock widgets of the respective plugins

Description
Visualize plugin dock widgets on --plugin-info
This PR needs https://github.com/napari/npe2/pull/245 to be merged.
Type of change

[X] New feature (non-breaking change which adds functionality)

I am not sure how to moch a Dock widget in the test.

Cool stuff, thanks @mstabrin! Sorry for the lack of answers :) Keeping this on hold, since we need to both merge and release the npe2 change first.


Rework alias command to not to use external tools

This includes following changes:

Adds handling of duplicate aliases internally by alias script instead of external perl script.
Adds additional /d option to remove already defined alias (and replaces unalias.bat -> unalias alias :) ).
Adds the way to show defined aliases by typing alias command without arguments.

@MartiUK, @bliker PTAL

+1 from me, I'm actually using it ;)
THanks

You're welcome! :)

Looks good, thanks @vladimir-kotikov

Thanks for merging @MartiUK


Error after installation

Please provide us with the following information:

OS?  Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)

Mac OS X Yosemite

Versions. Please run ng --version. If there's nothing outputted, please
run in a Terminal:
node --version
And paste the result here.

node --version
v5.11.1

Repro steps. Was this an app that wasn't created using the CLI? What change did you
do on your code? etc.

Fresh install of Node via NVM. Ran npm install -g angular-cli, completes without issue (just lodash warnings, no errors).
Unable to run ng --version, ng --help, or any other command without generating the below error.

The log given by the failure. Normally this include a stack trace and some
more information.

/Users/josephpowers/.nvm/versions/node/v5.11.1/lib/node_modules/angular-cli/node_modules/ember-cli/lib/models/project.js:669
      throw reason;
      ^

SyntaxError: /Users/josephpowers/package.json: Unexpected end of input
    at Object.parse (native)
    at Object.Module._extensions..json (module.js:430:27)
    at Module.load (module.js:357:32)
    at Function.Module._load (module.js:314:12)
    at Module.require (module.js:367:17)
    at require (internal/module.js:20:19)
    at Function.Project.getProjectRoot (/Users/josephpowers/.nvm/versions/node/v5.11.1/lib/node_modules/angular-cli/node_modules/ember-cli/lib/models/project.js:655:15)
    at module.exports (/Users/josephpowers/.nvm/versions/node/v5.11.1/lib/node_modules/angular-cli/node_modules/ember-cli/lib/cli/index.js:51:22)
    at module.exports (/Users/josephpowers/.nvm/versions/node/v5.11.1/lib/node_modules/angular-cli/lib/cli/index.js:102:10)
    at /Users/josephpowers/.nvm/versions/node/v5.11.1/lib/node_modules/angular-cli/bin/ng:31:5

Mention any other details that might be useful.

Thanks! We'll be in touch soon.

Somehow an empty package.json was initialized in the home directory which was conflicting with it. Once I deleted that file, it started working fine.

I had the same issue today on Linux (immediately after a new global install). The empty package.json wasn't in my home dir though, it was in the parent of the dir I was in when I issued the install command.
I also solved the problem by removing this file.

I had the same, with a package.json being created in my home dir, on Mac OS X El Capitan (10.11.5)  (#1133).

I had a similar issue on Windows 10 using npm 3.10.10...
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules@angular\cli\node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"}
I did 2 things that were supported in the discussion: firstly I created the package.json and then I added the "optionalDependencies": {"fsevents: "*" }. Both of these were suggested by posts in this discussion but I can't get back to the top portion of the blog (??). So I can't get the names of the contributors.
Now it seems to work without down grading.
Thanks


Update thoughtbot brand red

Per https://github.com/thoughtbot/presskit/pull/30

Done: https://github.com/thoughtbot/design-system/commit/63ef6b21293d41354bff65faedb91d994e950381


check-block with old block failed with Could not fetch epoch at

$ ./target/debug/acala check-block --pruning=archive 130000
2020-02-14 11:32:52 Importing 1 blocks
2020-02-14 11:32:52 There was an error importing block with hash 0x756060db2b4ec9913ba37071dcaae8834fe8bbaf0d9fdbdbf42362400a84fd28: VerificationFailed(None, "Could not fetch epoch at 0x1d439b949dd15a0f3056b1aab6f460a0e68a283ab2b61bb088a11fa77eea35ed")
2020-02-14 11:32:52 Stopping after #0 blocks because of an error
Completed in 101 ms.
Segmentation fault: 11

Pruning mode is already archive. Anything I can do so I can replay old block to debug it?

CC @arkpar

Must be related to some additional pruning by grandpa/babe verifier. @andresilva Do we prune epoch changes regardless of --pruning setting? Ideally we should keep everything in archive mode, so that any old block could be re-checked.

Currently epoch data for BABE and GRANDPA is pruned on finality, the idea is that you'd never need to import anything before the finalized block. With the current implementation there's no way to do this that doesn't lead to performance regressions if we never prune these data structures.

Is it possible to skip those digest verifications? I just want to debug why a tx in a block resulted an unexpected change.

I guess you can just pass the client directly to the import queue to use as BlockImport (rather than running grandpa and babe block import logic).
https://github.com/paritytech/substrate/blob/master/bin/node/cli/src/service.rs#L88
Here you'd replace this parameter with client.clone().

@andresilva I think that's not enough. BabeVefifier that created by import_queue still causing the issue.

I am trying to temporary replace the consensus to manual-seal which seems like a no-verification consensus, but can't get it working #4926


[memory] fix leak on Selector.write error

Switch where the networkSend variable is assigned so that it is assigned
prior to the place where the IOException can occur, allowing the catch
block to release it.
Fix NPE in AmbryRequests.

Codecov Report

Merging #1740 (e5d5834) into master (e4cc7a3) will decrease coverage by 58.54%.
The diff coverage is 0.00%.

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

Codecov Report

Merging #1740 (e5d5834) into master (e4cc7a3) will decrease coverage by 58.54%.
The diff coverage is 0.00%.

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


Update is_fixed_role column in babelfish catalog for logins and use

Description
Update the is_fixed_role column in babelfish catalogs babelfish_authid_login_ext and babelfish_authid_user_ext for fixed database and server roles.
Issues Resolved
Task: BABEL-5333
Signed-off-by: Shalini Lohia<EMAIL_ADDRESS>Test Scenarios Covered

Use case based -

Boundary conditions -

Arbitrary inputs -

Negative test cases -

Minor version upgrade tests -

Major version upgrade tests -

Performance tests -

Tooling impact -

Client tests -

Check List

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>9
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

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

Totals

Change from base Build<PHONE_NUMBER>4:
0.001%

Covered Lines:
46399

Relevant Lines:
62087

💛  - Coveralls


docs: update link

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


Show default value in docs

Hello @mehagar ,
Thank you for your pull, the default value comment has been merged.
Just to let you know, the source file is found in the src/HtmlAgilityPack.Shared/ directory.
Check this commit: https://github.com/zzzprojects/html-agility-pack/commit/f6b69de470a4b90ca4b51aea6be998cb17537de9
We will eventually clean this repository to make it easier for everyone.
Best Regards,
Jonathan

Performance Libraries
context.BulkInsert(list, options => options.BatchSize = 1000);
Entity Framework Extensions • Entity Framework Classic • Bulk Operations •  Dapper Plus
Runtime Evaluation
Eval.Execute("x + y", new {x = 1, y = 2}); // return 3
C# Eval Function • SQL Eval Function


ci: try to trigger CI error

What does this PR do
Checklist:

[ ] I have read CONTRIBUTING.md
[ ] I have written necessary tests and rustdoc comments
[ ] A change log has been added if this PR modifies nix's API

libc 0.2.154 has been yanked due to this issue: https://github.com/rust-lang/libc/issues/3677#issuecomment-2093991553
ref: https://crates.io/crates/libc/0.2.154

Let's wait for https://github.com/rust-lang/libc/pull/3682


[App][CLI] wandb.ai/authorize creates team token instead of personal token

Describe the bug
I have created a new personal project under wandb.ai/<username>/<projectname> on the website.
In the then visible setup instructions, it gives me an authorization token that is identical to the token that I get when visiting wandb.ai/authorize
If I log in with this token from the command line it says 'logged in as ' instead of 'logged in as '
When I start a new run, the just created project is ignored and a new project is created under wandb.ai/<teamname>/<projectname> and synced.
It seems like I have no way of creating a personal (non-team) login token to sync personal projects.
To Reproduce
Steps to reproduce the behavior:

Be member of one team
Create a new personal project
Log in with the shown authorization token from the command line
Start run

Expected behavior
The website gives me a token that makes the CLI say 'logged in as ' and the CLI syncs to the just created personal project instead of creating a new team project.
Additional context
Google Colab
Python 3.7.12
wandb version 0.12.6
Chrome Version 95.0.4638.69 (Official Build) (64-bit)

Hey @epistoteles the token showed on /authorize is the same as the first token in your personal settings page: https://wandb.ai/settings
If you want projects to be logged to a team by default, you can set your default entity in the settings page to that team.  You can also set the WANDB_ENTITY environment variable, or the entity keyword arg of wandb.init to send results to a team.
You can create a service account for a specific team by going to https://wandb.ai/teams/$TEAM_NAME and adding a "Service" user to the team.  This api token can then be used to post experiments to that team.  If you want to attribute experiments to actual members of the team you can set the WANDB_EMAIL or WANDB_USER_NAME environment variables.

Thank you for the thorough explanation!
I tried out the entity parameter and this resulted in the run being synced to the right project.
Maybe you can include this parameter by default in the shown instructions when default and project entity diverge? This would have helped me a lot, as they only included the line logger = WandbLogger(project="<projectname>") instead of logger = WandbLogger(project="<projectname>", entity='<username>') in my case (in the pytorch-lightning example, I didn't check the others).
Again, thanks for the help!


Component is Re-rendering even if data is equal

Problem
This polling causes re-render every time. Even if data is equal:
  const { data: matches } = useQuery<Array<ITournamentMatch>>(
    ["matches", endpoint],
    getMatchData,
    {
      initialData: [],
      refetchInterval: 10000,
    }
  );

Even after adding this check, it still causes re-render:
  const { data: matches } = useQuery<Array<ITournamentMatch>>(
    ["matches", endpoint],
    getMatchData,
    {
      initialData: [],
      refetchInterval: 10000,
      isDataEqual: (oldData, newData) => {
        console.log(JSON.stringify(oldData) === JSON.stringify(newData));
        return JSON.stringify(oldData) === JSON.stringify(newData);
      },
    }
  );

  console.log("runs", Math.random());

Console every 10 seconds outputs:

MatchList.tsx:62 runs 0.32818948818415516
MatchList.tsx:58 true
MatchList.tsx:62 runs 0.7568808987116595

On a different component the same occurs:
  const { data: match } = useQuery<ITournamentMatch>("match", getMatch, {
    initialData: {
      externalId: null,
      id: null,
      matchStatus: "",
      matchTime: "",
      matchTimeUTC: "",
      matchType: "",
      teamA: {} as ITournamentMatchTeam,
      teamB: {} as ITournamentMatchTeam,
    },
    refetchInterval: 10000,
    isDataEqual: (oldData, newData) =>
      JSON.stringify(oldData) === JSON.stringify(newData),
  });

  console.log('runs', Math.random())

LiveMatch.tsx:46 runs 0.20183955814094712
LiveMatch.tsx:46 runs 0.9209062385862188

That is happening because your component transitions to isFetching: true when there is a background update, and then back to isFetching: false. Try notifyOnChangeProps: 'tracked' or giving an Array of props you want to "track".
usually, the re-renders don't matter. your component should be able to render every 10 seconds without showing impact. Imagine there are changes in the data one every poll - then you are also rendering, and need to be able to handle that :)

That is happening because your component transitions to isFetching: true when there is a background update, and then back to isFetching: false. Try notifyOnChangeProps: 'tracked' or giving an Array of props you want to "track".
usually, the re-renders don't matter. your component should be able to render every 10 seconds without showing impact. Imagine there are changes in the data one every poll - then you are also rendering, and need to be able to handle that :)

This worked but is a little bit confusing:
      notifyOnChangeProps: ["isLoading", "isSuccess", "data", "isError", "status"],

Any way I can listen to the loading status again. I want to know if data loads when dependancy array changes but that is all I care about

well it depends on which fields your component is using. Are you also displaying an error ? If so, you also want to re-render when there is an error, otherwise, it will not be shown ... That is why we introduced notifyOnChangeProps: 'tracked', where react-query will track which properties of the returned queryInfo are actually used during rendering, and only re-render if one of those fields change.

I changed to latest and notifyOnChangeProps: 'tracked' gives me the error
Uncaught TypeError: notifyOnChangeProps.some is not a function
    at _loop (webpack:///./node_modules/react-query/es/core/queryObserver.js?:359)

which version are you running? This feature was added in 3.6.0 (minor release): https://github.com/tannerlinsley/react-query/releases/tag/v3.6.0

which version are you running? This feature was added in 3.6.0 (minor release): https://github.com/tannerlinsley/react-query/releases/tag/v3.6.0

I was using 3.12.0, but I think I had not rebuilt using webpack so perhaps it was just an issue due to that, it's working fine now... :)