migrate.InstallXrootd

This is a documentation migration pull request and you must have write access to this repository to complete this work. If you do not have write access, please contact BrianL or Mat. Follow the instructions below to migrate the document in this pull request.
Note: The following instructions assume that origin is associated with opensciencegrid/docs, your remote name may be different so check with git remote -v.

To begin working on this conversion, please claim ownership of this pull request to the right.

If you don't have a local copy of the docs repo, clone it:
 git clone https://github.com/opensciencegrid/docs.git

cd into the directory containing

Create a local branch based on the branch from this pull request:
 git checkout migrate.InstallXrootd origin/migrate.InstallXrootd

Fixup the document (if there are issues you don't know how to address, leave a comment):

[ ] Save any images to the docs/images/ directory and add them to the document

[ ] Address any common problems outlined in the Completing the Conversion section

[ ] Search the docs/ for any links to the old TWiki document and fix them to point at the new document

[ ] Add the document to mkdocs.yml under the Install Guides - Data section:
  - 'Install XRootD': 'data/install-xrootd.md'

Stage and commit your changes

Push your changes upstream:
 git push origin migrate.InstallXrootd

Request a review

There's a reference to https://twiki.opensciencegrid.org/bin/view/Storage/HadoopXrootd in the docs.  Is this getting migrated or should I drop the reference?

Leave the reference (but make sure there's a full twiki link). I'll need to review the Storage area to see if we need to keep anything.

I believe everything has been fixed and it's good to go.


Upgrade the cert-manager dependency to the 1.12-relaese HEAD commit

/kind cleanup
Release Note
NONE

/cherry-pick release-1.12


Connecting Backend Paging with a Graph

Question
Hey team,
I have a question regarding the use of Connecting Backend Paging with a Graph.
Based on the filtering of the table graph needs to be change, How we can achieve the same by using vizro.
Thank you so much for the amazing work on this tool, and for the help in advance!
from dash import Dash, dash_table, dcc, html, Input, Output, callback
import pandas as pd

app = Dash(__name__)

df = pd.read_csv('https://raw.githubusercontent.com/plotly/datasets/master/gapminder2007.csv')

PAGE_SIZE = 5

app.layout = html.Div(
    className="row",
    children=[
        html.Div(
            dash_table.DataTable(
                id='table-paging-with-graph',
                columns=[
                    {"name": i, "id": i} for i in sorted(df.columns)
                ],
                page_current=0,
                page_size=20,
                page_action='custom',

                filter_action='custom',
                filter_query='',

                sort_action='custom',
                sort_mode='multi',
                sort_by=[]
            ),
            style={'height': 750, 'overflowY': 'scroll'},
            className='six columns'
        ),
        html.Div(
            id='table-paging-with-graph-container',
            className="five columns"
        )
    ]
)

operators = [['ge ', '>='],
             ['le ', '<='],
             ['lt ', '<'],
             ['gt ', '>'],
             ['ne ', '!='],
             ['eq ', '='],
             ['contains '],
             ['datestartswith ']]

def split_filter_part(filter_part):
    for operator_type in operators:
        for operator in operator_type:
            if operator in filter_part:
                name_part, value_part = filter_part.split(operator, 1)
                name = name_part[name_part.find('{') + 1: name_part.rfind('}')]

                value_part = value_part.strip()
                v0 = value_part[0]
                if (v0 == value_part[-1] and v0 in ("'", '"', '`')):
                    value = value_part[1: -1].replace('\\' + v0, v0)
                else:
                    try:
                        value = float(value_part)
                    except ValueError:
                        value = value_part

                # word operators need spaces after them in the filter string,
                # but we don't want these later
                return name, operator_type[0].strip(), value

    return [None] * 3

@callback(
    Output('table-paging-with-graph', "data"),
    Input('table-paging-with-graph', "page_current"),
    Input('table-paging-with-graph', "page_size"),
    Input('table-paging-with-graph', "sort_by"),
    Input('table-paging-with-graph', "filter_query"))
def update_table(page_current, page_size, sort_by, filter):
    filtering_expressions = filter.split(' && ')
    dff = df
    for filter_part in filtering_expressions:
        col_name, operator, filter_value = split_filter_part(filter_part)

        if operator in ('eq', 'ne', 'lt', 'le', 'gt', 'ge'):
            # these operators match pandas series operator method names
            dff = dff.loc[getattr(dff[col_name], operator)(filter_value)]
        elif operator == 'contains':
            dff = dff.loc[dff[col_name].str.contains(filter_value)]
        elif operator == 'datestartswith':
            # this is a simplification of the front-end filtering logic,
            # only works with complete fields in standard format
            dff = dff.loc[dff[col_name].str.startswith(filter_value)]

    if len(sort_by):
        dff = dff.sort_values(
            [col['column_id'] for col in sort_by],
            ascending=[
                col['direction'] == 'asc'
                for col in sort_by
            ],
            inplace=False
        )

    return dff.iloc[
        page_current*page_size: (page_current + 1)*page_size
    ].to_dict('records')

@callback(
    Output('table-paging-with-graph-container', "children"),
    Input('table-paging-with-graph', "data"))
def update_graph(rows):
    dff = pd.DataFrame(rows)
    return html.Div(
        [
            dcc.Graph(
                id=column,
                figure={
                    "data": [
                        {
                            "x": dff["country"],
                            "y": dff[column] if column in dff else [],
                            "type": "bar",
                            "marker": {"color": "#0074D9"},
                        }
                    ],
                    "layout": {
                        "xaxis": {"automargin": True},
                        "yaxis": {"automargin": True},
                        "height": 250,
                        "margin": {"t": 10, "l": 10, "r": 10},
                    },
                },
            )
            for column in ["pop", "lifeExp", "gdpPercap"]
        ]
    )

if __name__ == '__main__':
    app.run(debug=True)

https://dash.plotly.com/datatable/callbacks
Code/Examples
No response
Other information
No response
Which package?
None
Package version
No response
Python version
No response
OS
No response
Code of Conduct

[X] I agree to follow the Code of Conduct.

hi @BalaNagendraReddy 👋 thanks for the question! we will double check and reply with guidance on how this might be achieved in Vizro 👍
in the meantime we wanted to check whether you're also aiming to retain the ability to sort and filter the data in the table, using the inbuilt controls at the top of the table?

Hi @Joseph-Perkins ,
Thanks for your reply.
Mainly, focusing on filter rather than sorting, based on the filter, graph needs to be change. That is my expectation.


Global leaks old firefox versions strange behavior

Hi, i'm currently doing lot of tests using Browserstack.
Today I executed unit tests on the ~500 browsers Browserstack supports and encountered a strange Error: global leak detected: navigator which appears only with old Firefox versions (the error is encountered in Firefox 5.X and older).
My settings are very simple ;
<script type="text/javascript">
    mocha.setup({ui: 'bdd'});
</script>

<script type="text/javascript" src="test/spec/my-tests.js"></script>

<script type="text/javascript">
    mocha.checkLeaks();
    mocha.run();
</script>

The first time I execute the tests the following error is reported : Error: global leak detected: navigator.
But if I refresh the tab it works without problem, what's strange is that if I add only navigator.userAgent; before mocha.checkLeaks(); then it works.
...
<script type="text/javascript">
    navigator.userAgent;
    mocha.checkLeaks();
    mocha.run();
</script>

Do you know why I encounter this strange behavior ? Is it a bug in Mocha's leaks detection ?
If somebody else encounters the same error the workaround is simply to change you Mocha settings.
mocha.setup(
    {
        ui: 'bdd',
        globals: ['navigator']
    }
);

Thanks,
Baptiste

if a new property appears in the global context between the mocha.run() and its completion, the global leak detection error will occur.  what FF is doing, I don't know, but that's why.  good to know for people using older FF versions though--thanks

Hi @boneskull, ok I understand now, makes sense.
So old FF versions should have a buggy page initialization.
Thanks for the explanations !


Update README.md

Make some example code consistent with its introduction.

Agreed, my bad. I changed.. well I wanted to explain desktop as well now, since that used to be pc instead of desktop, so its more clear.


Added gfos.txt

Faculty of civil engineering in Osijek.
website: http://www.gfos.unios.hr/portal-en/
email template<EMAIL_ADDRESS>

@epson121 Pull request merged. Could you please change the content of the file and submit another pull request? The content now is "Faculty of civil engineering". I recommend to change it to "Faculty of civil engineering at the University of Osijek" or any other appropriate title reflecting actual organizational structure. It's important to make it searchable if anyone tries to find the domain by the university name. Thank you!


ZEVA - Credit application error download

Description: The Excel error download provided to the supplier needs to be changed to include any VIN not issued credits. Presently it only includes error that were first identified when the application is run against ICBC data. It should include any VIN the analyst unchecked and should not include VIN the analyst checked manually.
Wireframe:
Purpose and benefit to user: The purpose of the download is to communicate with the supplier the error reason that the VIN was not issued credits so that they may submit certain VIN again dependent on the error.
Acceptance Criteria:

[ ] Given I am a BCeID ZEVA user, When I am reviewing an issued credit application with error VIN, then I can download an Excel file containing all VIN that were not issued credits and see the reason for that

Development Checklist:

[ ] Use the record_of_sale and sales_submission_content tables to determine the VINs that were not issued credits, and attach any saved warnings and reasons to the missing vins.

Notes:

Hey team! Please add your planning poker estimate with Zenhub @tim738745 @JulianForeman @emi-hi

Is it possible to get a specific report we see this happening on so I can pull the data in locally and see what's going on?

see CA 480 Ford on test


JavaScript error: failed to get 'appData' path

I got an error after my first installation on a Linux Mint 19 x64 machine.
After starting the wallet software I received this error message:

OpenSuse is not officially supported: https://iohk.zendesk.com/hc/en-us/articles/360010496553-Daedalus-System-Requirements
Still, you might try these steps to get Daedalus Mainnet working: https://iohk.zendesk.com/hc/en-us/articles/900000776446-Installing-Daedalus-Mainnet-on-Linux-

I am running Linux mint, its a fork of Ubuntu, which is said to be supported.
Does that mean only Ubuntu is supported?

Officially yes. Please make sure you covered all these steps: https://iohk.zendesk.com/hc/en-us/articles/900000776446-Installing-Daedalus-Mainnet-on-Linux-


[local-volume] New controller to handle node deletion

Extension to https://github.com/kubernetes/community/pull/1484
In cloud environments, nodes can be deleted and recreated fairly often.  When nodes are deleted, the local disks are also deleted along with them, however local PVs remain and pods will get stuck scheduling because they are bound to a node that no longer exists.
For workloads that tolerate data loss and can recover with a brand new disk, the user can delete and recreate the PVC, which will cause the new PVC to be bound to a new disk.  If using StatefulSets, the StatefulSet controller will automatically recreate a PVC if it doesn't exist.
The process of detecting node deletion and deleting the PVC could be automated by a controller.  There's a few things to consider:

Workload needs to opt in to this controller.  Not all workloads want this behavior.
Node deletion detection can be tricky in some environments.  I know in GCE, the managed instance group recreates nodes with the same name.  And in K8s 1.11, I think the Node object is no longer recreated by kubelet if the instance ID changes.
There are two scenarios: 1) PVC is already bound to a local PV. When local PV is released, there may be additional cleanup needed too since the daemonset provisioner no longer runs on that node.   2) Local PV Is unbound and available (but not actually since node is gone)

As for implementation ideas, I think metacontroller would be a cool framework to try out for this.

/area local-volume

Thinking about it a little more, the scenario where node is recreated with the same name could be handled by kubernetes/community#1484, which can detect that the path/disk no longer exists on the node.
So maybe there are actually 3 controllers involved here:

Daemonset that monitors disks on each node: kubernetes/community#1484
Single controller that monitors deletion of node objects
Single controller that manages workloads using local PVs

1 and 2 are being implemented here in https://github.com/caicloud/kube-storage-monitor

Migrating to new repo: https://github.com/kubernetes-sigs/sig-storage-local-static-provisioner/issues/10
/close


Without the bot being asked, it sends this message below in the groups

[Sydney Bot]: Too many unread messages (4) since I've last seen this chat. I'm ignoring them. If you need me to respond, please @mention me or quote my last completion in this chat.

@solution01  This message should happen only after the bot is restarted to inform the user it will ignore the messages. Did you restart the bot before these messages or did it just send out of nowhere?

The message was sent out of nowhere.

I collected some pm2 logs for you to take a look at

@solution01  That is all how it should work, what it shoudnt do is send more than one of the "Too many unread messages (4) since..." messages per chat when it restart. If it's than there is a problem.
I am gonna do something to give a option to disable this message in the .env to fix it temporarily

That is all how it should work, what it shoudnt do is send more than one of the "Too many unread messages (4) since..." messages per chat when it restart. If it's than there is a problem.
I am gonna do something to give a option to disable this message in the .env to fix it temporarily

Ok @Luisotee I'll wait for you to create this solution, thank you :)

@solution01 I added the option in #222. A definite fix will only be out when I have time i.e.: Só Deus sabe

@solution01 tem que deixar como false

Done and it's functional, thanks for your help :)


Errors when trying to create invoice

I installed lnbits on Ubuntu VPS running a testnet LND lightning node, setting up .env file and installed necessary grpc libraries. After running the lnbits server I am able to create wallet, however this is what I get when trying to create an invoice:
table apipayments has no column named checking_id
At the same time, check pending payments endpoint returns an error as well:
no such column: bolt11
I checked my data directories for database files and they are created.
Is there something I might have ommitted? Is there any way to check whether the connection to lnd node has been established (like calling lnd's getinfo call)? Thank you for help & guidance!

It seems the database migrations only run partially, which is odd. Did you just install from master? Or did you have an old installation and updated to master now and then run it again?
What command are you using to run the LNbits server?
Running quart migrate should help you anyway (you must run that inside the virtualenv, or ./venv/bin/quart migrate).
If nothing helps, can you please run sqlite3 <your-lnbits-db-path>/database.sqlite3 'select * from dbversions'?

Hi thank you for quick answer. This is how I am running the server alongside the output:
lnd-testnet@sfc:~/lnbits-0.1.1$ pipenv run python -m lnbits
Loading .env environment variables…
/home/lnd-testnet/.local/share/virtualenvs/lnbits-0.1.1-3p68qwXV/lib/python3.7/site-packages/scss/selector.py:54: FutureWarning: Possible nested set at position 329
  ''', re.VERBOSE | re.MULTILINE)
running migration core.1
running migration core.2
running migration lnurlp.1
running migration usermanager.1
running migration events.1
running migration events.2
running migration tpos.1
running migration withdraw.1
running migration withdraw.2
running migration paywall.1
running migration paywall.2
running migration lnticket.1
running migration lnticket.2
Running on http://<IP_ADDRESS>:5000 (CTRL + C to quit)

And this is the return from sqlite3 select statement:
core|2
lnurlp|1
usermanager|1
events|2
tpos|1
withdraw|2
paywall|2
lnticket|2

As a sidenote to installation - After cloning master from github I could not get installation of dependencies done using lnbits.org docs (with python venv) as it complained about non existing version of hypercorn in requirements.txt. So I went with downloading the release archive and did pipenv installation described on github. I as well tried pipenv run quart migrate, however I got back 'No such command: migrate'

That seems correct, are you sure you're accessing the same LNbits server that outputted all those migration lines and was running on http://<IP_ADDRESS>:5000? I can't imagine anything wrong.
By the way, this has nothing to do with lnd connection. But indeed I think we should output debug information about connection status, database status etc. when starting LNbits, it will be helpful.

sqlite3 <your-lnbits-db-path>/database.sqlite3 '.schema apipayments' will confirm that the columns checking_id and bolt11 do exist. But at this point it's gotta be something else.
What is the value of LNBITS_DATA_FOLDER in your .env file?

I just pushed a commit to master that will print your data folder when starting LNbits with python -m lnbits.

Hi, I cleaned the environment and data folder, cloned the current master and I send you my install process and ouputs step by step (comments behind hashes are added as explanations):
lnd-testnet@sfc:~/lnbits$ pipenv install --dev
Creating a virtualenv for this project…
Pipfile: /home/lnd-testnet/lnbits/Pipfile
Using /usr/bin/python3.7m (3.7.5) to create virtualenv…
⠏ Creating virtual environment...created virtual environment CPython3.7.5.final.0-64 in 494ms
  creator CPython3Posix(dest=/home/lnd-testnet/.local/share/virtualenvs/lnbits-wqECVPIq, clear=False, global=False)
  seeder FromAppData(download=False, pip=bundle, setuptools=bundle, wheel=bundle, via=copy, app_data_dir=/home/lnd-testnet/.local/share/virtualenv)
    added seed packages: pip==20.2.3, setuptools==50.3.0, wheel==0.35.1
  activators BashActivator,CShellActivator,FishActivator,PowerShellActivator,PythonActivator,XonshActivator
✔ Successfully created virtual environment!
Virtualenv location: /home/lnd-testnet/.local/share/virtualenvs/lnbits-wqECVPIq
Installing dependencies from Pipfile.lock (ca7309)…
  🐍   ▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉ 64/64 — 00:00:52
To activate this project's virtualenv, run pipenv shell.
Alternatively, run a command inside the virtualenv with pipenv run.

pipenv run pip install lndgrpc
pipenv run pip install lnd-grpc ### not mentioned in docs but required
pipenv run pip install purerpc  ### mentioned in docs with typo

pipenv run python -m lnbits

lnd-testnet@sfc:~/lnbits$ pipenv run python -m lnbits
Loading .env environment variables…
running migration core.1
running migration core.2
running migration lnurlp.1
running migration lnurlp.2
running migration usermanager.1
running migration events.1
running migration events.2
running migration tpos.1
running migration withdraw.1
running migration withdraw.2
running migration paywall.1
running migration paywall.2
running migration lnticket.1
running migration lnticket.2
Starting LNbits with
  - site title: Sfc-LNbits
  - debug: True
  - data folder: /home/lnd-testnet/lnbitsdata
  - funding source: LndWallet
  - service fee: 0.0

Running on http://<IP_ADDRESS>:5000 (CTRL + C to quit)
Running on <IP_ADDRESS>:5000 over http (CTRL + C to quit)
[2020-10-06 21:57:05 +0200] [32310] [INFO] Running on <IP_ADDRESS>:5000 over http (CTRL + C to quit)

### I can create the wallet but app then fails to get/post payments endpoint with above mentioned errors. Same from frontend ### as with curl

lnd-testnet@sfc:~/lnbits$ sqlite3 /home/lnd-testnet/lnbitsdata/database.sqlite3 '.schema apipayments'
CREATE TABLE apipayments (
            payhash TEXT NOT NULL,
            amount INTEGER NOT NULL,
            fee INTEGER NOT NULL DEFAULT 0,
            wallet TEXT NOT NULL,
            pending BOOLEAN NOT NULL,
            memo TEXT,
            time TIMESTAMP NOT NULL DEFAULT (strftime('%s', 'now')),

            UNIQUE (wallet, payhash)
        );

not mentioned in docs but required

This is an indication that you're running an old version as it shouldn't be required.
But mysteriously your migration logs indicate you are running a new version.
Can you paste the output of git rev-parse HEAD in the lnbits folder?

Just pushed a thing to include current version in that which I hope will become helpful debugging information next time: 24c82019205137e8d0128c17066620385d3ec309

Head: 9a16dfa96092dbd185780cb7cf65d6584b660806
It might not be required in current master. I got the error when I used archive of 0.1.1 release and I automatically repeated the install it after cloning master, not aware it might not be needed anymore.

After cleaning & installing from master:
Loading .env environment variables…
Starting LNbits with
  - git version: 24c82019205137e8d0128c17066620385d3ec309
  - site title: Surfcity-LNbits
  - debug: True
  - data folder: /home/lnd-testnet/lnbitsdata
  - funding source: LndWallet
  - service fee: 0.0

Running on http://<IP_ADDRESS>:5000 (CTRL + C to quit)

I just ran the following (on a blank directory):
git clone git@github.com:lnbits/lnbits.git
cd lnbits
pipenv install --dev
cp .env.example .env
pipenv run python -m lnbits

Got the same migration outputs as you:
Loading .env environment variables…
running migration core.1
running migration core.2
running migration tpos.1
running migration withdraw.1
running migration withdraw.2
running migration lnurlp.1
running migration lnurlp.2
running migration paywall.1
running migration paywall.2
running migration usermanager.1
running migration lnticket.1
running migration lnticket.2
running migration events.1
running migration events.2
Starting LNbits with
  - git version: 0b1f3c22e05786a5894f4a2e02f4b3c905f0acda
  - site title: LNbits
  - debug: True
  - data folder: .
  - funding source: VoidWallet
  - service fee: 0.0

Running on http://<IP_ADDRESS>:5000 (CTRL + C to quit)

But sqlite3 database.sqlite3 '.schema apipayments' shows the correct output:
CREATE TABLE apipayments (
            checking_id TEXT NOT NULL,
            amount INTEGER NOT NULL,
            fee INTEGER NOT NULL DEFAULT 0,
            wallet TEXT NOT NULL,
            pending BOOLEAN NOT NULL,
            memo TEXT,
            time TIMESTAMP NOT NULL DEFAULT (strftime('%s', 'now')), hash TEXT, preimage TEXT, bolt11 TEXT, extra TEXT,

            UNIQUE (wallet, checking_id)
        );
CREATE INDEX by_hash ON apipayments (hash);

I have no idea of what is going on with your setup.

Hi I tried to put lnbits into isolated LXD container. After setting up networking to/from container, lnbits works as expected and connects to LND. Closing the issue, seems like quite weird special case. Thanks for your support.


Added Swedish holidays

Includes holidays as defined by Swedish law.

Ok, so it is a one year old request, will probably not be merged any time soon, but still.
@Faleij you missed out on date/dates, for example is Christmas Eve (Julafton) a "red" day and is a holiday.


Missing sign-out template

Hello,
There seems to be a template missing in the sign-out route. When you sign out the router goes to a template named 'EntrySignOut' which does not exist within the package.
On desktop the error message flashed by too quick to notice, but on my mobile phone I could read the error and when I made a new template with that name, it was rendered on sign out.

put this

somewhere in an html within your project

Suggestion from @xanatas works, but perhaps this should be part of the package.


CSSE Multiplayer Implemenation

Node.js Server

See node_backend folder
Packages specified in package.json: socket.io for socket communications, uuid used to generate unique identifiers for each player
index.js contains all the code: https://github.com/nighthawkcoders/teacher_portfolio/blob/main/node_backend/index.js

Listens for socket connections and socket messages

update = client to server player update,
stateUpdate = server to client player update
disconnection = client has left
connection = new client
id = assigns an id to the client

socket.io listens on port 3000

Run using node index.js

Creating a socket.io client

This is done in the Game Environment: https://github.com/nighthawkcoders/teacher_portfolio/blob/d6705898dd2a2d8786df2f08e4e1e21d0d54cc01/assets/js/multiplayer/GameEnv.js#L29

Obtaining and using the ID for this client

The ID is sent by the server to the client in a socket io message, this message is listened to in Game Environment and put into GameEnv to be used later: https://github.com/nighthawkcoders/teacher_portfolio/blob/d6705898dd2a2d8786df2f08e4e1e21d0d54cc01/assets/js/multiplayer/GameEnv.js#L32

Using the ID to determine the appropriate ID for the player object

The GameEnv.id is used when creating the player in the GameLevel class: https://github.com/nighthawkcoders/teacher_portfolio/blob/d6705898dd2a2d8786df2f08e4e1e21d0d54cc01/assets/js/multiplayer/GameLevel.js#L68

Exporting information about Objects to Server

Each gameObject has an attribute about whether it should be updated through the server

this.shouldBeSynced = false, set to true in the Player class

Each gameObject has a jsonify method to convert it to a JSON object that can be sent via socket.io

GameObject
Player which extends from GameObject

If this object is to be synced, then it is updated in the logElement method: see here

Being able to add a character to the level in realtime

In the GameLevel class, an addCharacter method has been added: https://github.com/nighthawkcoders/teacher_portfolio/blob/d6705898dd2a2d8786df2f08e4e1e21d0d54cc01/assets/js/multiplayer/GameLevel.js#L89

It first checks if a gameObject exists with this ID, otherwise it creates a character based on the character image for that level

Changing a gameObject based on JSON info

An updateInfo method was added to gameObject to change this gameObject based on data exported from jsonify

GameObject, Overriden in Character

Ingesting player Updates from the Server

This is handled as a part of the GameControl: when a level is loaded listeners are added to stateUpdate -> https://github.com/nighthawkcoders/teacher_portfolio/blob/d6705898dd2a2d8786df2f08e4e1e21d0d54cc01/assets/js/multiplayer/GameControl.js#L33
The handleSocketMessage looks for a gameObject with the ID specified in the message and uses the updateInfo method, if none exists it uses the level's addCharacter method: https://github.com/nighthawkcoders/teacher_portfolio/blob/d6705898dd2a2d8786df2f08e4e1e21d0d54cc01/assets/js/multiplayer/GameControl.js#L69

Deleting players when someone leaves

SImilar to the handleSocketMessage there is a handleSocketDisconnect which is assigned in the same part of code to the disconnection event: https://github.com/nighthawkcoders/teacher_portfolio/blob/d6705898dd2a2d8786df2f08e4e1e21d0d54cc01/assets/js/multiplayer/GameControl.js#L34
It searches for the ID in game objects and then uses the destroy method
https://github.com/nighthawkcoders/teacher_portfolio/blob/d6705898dd2a2d8786df2f08e4e1e21d0d54cc01/assets/js/multiplayer/GameControl.js#L83

Deployment Information

Change the Backend URL in GameEnv
https://github.com/nighthawkcoders/teacher_portfolio/blob/d6705898dd2a2d8786df2f08e4e1e21d0d54cc01/assets/js/multiplayer/GameEnv.js#L29
Use the Dockerfile and docker-compose in node_backend

adjust the actual output port in the docker-compose

In NGINX make sure to forward web socket traffic, here is a NGINX file from another project using socket.io

server {
    server_name game.rohanj.dev;
    location / {
         proxy_pass http://localhost:10550;

# this magic is needed for WebSocket
        proxy_http_version  1.1;
        proxy_set_header    Upgrade $http_upgrade;
        proxy_set_header    Connection $connection_upgrade;
        proxy_set_header    Host $http_host;
        proxy_set_header    X-Real-IP $remote_addr;
    }
}


Reduce IAM permissions scope for AWS operator role

Is your feature request related to a problem? Please describe.
In the current standing, the AWS operator policy is too broad. Some of our customers have independent accounts for Giant Swarm but some not. As an example, we have full rights for S3 ("s3:*"). Also, as today is possible the operator to create any policy, attach to a role and assume it. Which indeed give you full admin rights into the accounts, and in case they are peering VPC from different accounts they are vulnerable.
Describe the solution you'd like
There are three measures we can do

Limit action of service (instead of wildcard use only actions we need "s3:*" -> "s3:GetObject")
Restrict resources (instead of "Resource": "*" -> "arn:aws:iam::<CUSTOMER_ACCOUNT_ID>:role/*-EC2-K8S-Role")
Add conditions. Here will be useful specially for IAM itself
Example

"Statement": {
    "Effect": "Allow",
    "Action": [
      "iam:AttachRolePolicy"
    ],
    "Resource": [
      "arn:aws:iam::<CUSTOMER_ACCOUNT_ID>:role/gs-*"
    ],
    "Condition": {"ArnLike":
      {"iam:PolicyARN": "<CUSTOMER_ACCOUNT_ID>:policy/GiantSwarmAdminPolicy"}
    }
  }

For some services, like EC2 or Cloud Formation, is fine to have a wildcard but others need to be reviewed

[ ] autoscaling:*
[ ] cloudwatch:*
[ ] elasticloadbalancing:*
[ ] events:*
[ ] kms:*
[ ] logs:*
[ ] route53:*
[ ] route53domains:*
[ ] s3:*

Tight with conditions

[ ] sts:AssumeRole
[ ] iam:AttachRolePolicy
[ ] iam:CreatePolicy
[ ] iam:CreateRole
[ ] iam:DeletePolicy
[ ] iam:DeleteRole
[ ] iam:DeleteRolePolicy
[ ] iam:PassRole

Describe alternatives you've considered
No other alternatives considered

We get requests for this restriction of our access rights a lot in talks with potential customers or when existing customers onboard new projects and security or here rather data privacy is involved. This also applies to the IAM role that we require for Giant Swarm Operations staff.
As we separate Control Plane account and the accounts that Tenant Clusters are in and recommend to have nothing else in the CP account, this is more important for the roles we use in the TC accounts.

A concrete issue a potential customer mentioned is that they keep privacy/GDPR relevant customer data in S3 and cannot allow a third party like us to have access to those.

This will probably never be implemented given our current push to Cluster API for AWS.


Add export support

right now exports to different formats such as trt, openvino etc are not supported. It'd be nice to support them.The original D-fine repo can be used as a starting point for export module https://github.com/Peterande/D-FINE

@AyushExel  working on this.

#37  wip.


Static ShadowUI functions don't available via hammerhead api

TestCafe uses addClass and removeClass, they are not available now via api.
This issue stops https://github.com/superroma/testcafe-phoenix/issues/44

@AlexanderMoskovkin and everyone: Let's not use documentation requirement and modification level labels while issue is open. We will not pollute issue with yet unused labels and it's not always clear until the issue is not fixed if it requires documentation or major version bump. It's better to perform this analysis afterwards.


Update command system

Update command system to accept a command both when it's spelled like this: !command but also if you were to throw in some random caps like this: !cOMMand also works when you .register a command, can put in both bot.register("coMMand") and bot.register("command")

Few things here that I see

Needs to compile
Use 2 space tabs
You're not guaranteed that someone registered their command using all lowercase

I figured that out, working on that now
/tableflip
What do you mean?

Just seeing if it works now, I'll fix indention in a bit

Need to do more local testing of the handle() method, I'll reopen once that's fixed


Repo caching

Don't load the whole commit log on startup
Fix loading repos twice on startup
Use groupcache/lru along with SOFT_SERVE_CACHE_SIZE to cache commits, trees, and patches

Ok, this seems to be working fine and it's improving performance for huge repos, a lot! One thing I'm noticing however: whenever I connect to soft-serve via SSH and browse the commits of a sample kernel repo, the memory footprint of soft seems to increase by ~200MB. Investigating!


windows are not black

windows are not black

Hi, thanks for the feedback.
AFIAK, context windows are controlled by the OS; at least that's the case with Linux. Looks like that's MacOS if I'm not mistaken.
I'll double-check and look into it when I get a moment but I'm thinking there's nothing in VSCode's CSS to change that.

I stand corrected, that particular context menu is not controlled by the OS after all. It looked an awful lot like a MacOS menu to me at first glance, but clearly it is not. I suppose I just never paid those particular menus much mind.
I'll see if I can't find what property controls that quick and make the change. Might be a little bit even after fixing before I get the extension updated in the VSCode Marketplace, but I'll post here what the property is so you can change it in your settings.json file temporarily in either case.
If I can't find it in the next couple minutes, it might be a few days until I get around to digging into it; it's been a while since I've poked around in Code's CSS.

Hi, this is mac os, but it's not an os window, i use cmd + . or ctrl + . On windows to open this window

I found it, in addition to changing the code suggestions. I'm probably going to look for a couple other things I may have missed later today or this weekend before pushing out any changes since I haven't touched this in a while.
Add this to your settings.json in the meantime.
"workbench.colorCustomizations": {
		"editorActionList.background": "#000",
		"editorSuggestWidget.background": "#000",
},

Thanks again for the feedback!

Thank you for your work

Addressed this and some other backgrounds in v1.3.2


Add span error status to the OTel-Arrow exporter and receiver

#139 added spans and trace context propagation, but does not set the Span status according to the response or make any other annotations.  This issue is to remind us that tracing support is bare-bones and could use a few improvements to help pinpoint performance issues in the future.

Fixed across several PRs.


fix: always relock source dependencies

Do we also need a satisfiability test the other way around?

Otherwise it seems to work as a charm for me!

The satisfiability the other way around already exists. :)


libzmq assertion under Python 3

The following code works fine (i.e., exits cleanly) under Python 2, but under Python 3.2 with pyzmq-2.1.11 prints:
stopping
start returned
Assertion failed: get_load () == 0 (poller_base.cpp:32)
Abort trap: 6

from zmq.eventloop.ioloop import IOLoop
from zmq.eventloop.zmqstream import ZMQStream
import zmq

def stop_loop(stream, loop):
    print("stopping")
    stream.close()
    loop.stop()

loop = IOLoop()
ctx = zmq.Context()
socket = ctx.socket(zmq.REQ)
socket.linger = 0
socket.connect('tcp://<IP_ADDRESS>:12345') # nothing listening
stream = ZMQStream(socket, loop)
stop_func = lambda x,y: stop_loop(stream, loop)
stream.on_send(stop_func)
loop.add_callback(lambda: stream.send(b"abc"))
loop.start()
print("start returned")

It's possible I'm doing something wrong that just happens to work under Python 2, but I thought this might be a bug in pyzmq. Could someone with a little more experience take a look?

Interesting.  I can confirm the issue with Python 3.2.2 on OSX Lion 10.7.3, and pyzmq master.  Asserts in libzmq generally mean bugs in libzmq itself, but it is certainly strange that pyzmq could hit it differently in Python 2 and 3.
Adding an explict ctx.term() at the end of the script seems to reliably prevent the assert, so maybe it is a thread cleanup issue at shutdown.

I tried to dig into this a little this evening without a lot of success. The assertion is being thrown because the poller still has one file descriptor that wasn't removed (i.e., add_fd was called one time more than rm_fd). On a successful run (with ctx.term()), the kqueue_t destructor joins what I believe is the context's IO thread, and before that join returns the IO thread removes the final fd. On a failed run, the join returns immediately as though the IO thread had died somehow without ever removing one of its fds.

I think I tracked the problem down to this change in Python 3.2: http://hg.python.org/cpython/rev/c892b0321d23
I believe this is the approximate sequence of events:

A message is created at message.pyx:253 with the "free function" assigned to free_python_msg (I think on the IO thread)
Python interpreter goes into shutdown mode.
libzmq calls the free function associated with the message (i.e., free_python_msg).
Because of the Python change linked above, when free_python_msg tries to acquire the GIL, Python forcefully exits the thread.
The remaining cleanup libzmq needed to do on that thread never happens, eventually leading to the assertion.

I have no idea how to get started fixing this, but it definitely appears to be a Python/pyzmq issue and not a libzmq one. I suspect this "PyThread_exit_thread() if trying to acquire the GIL during shutdown" could cause all kinds of unclean shutdown issues with libzmq threads running.

Thanks for tracking that down!  Your analysis is correct that the free-function is called from the IO thread, and that's causing the problem.  This is unavoidable[1] for non-copying sends, but fortunately it only affects non-copying sends, and for that matter, only affects non-copying sends that will be discarded at termination due to LINGER and failure to cleanup the context in your own code.  Understanding that, here's a simpler repro script:
import zmq
ctx = zmq.Context.instance()
socket = ctx.socket(zmq.REQ)
socket.linger = 0
socket.connect('tcp://<IP_ADDRESS>:12345') # nothing listening
socket.send(b'abc', copy=False)

# explicit close&term prior to Python exit eliminates the issue
# ctx.destroy()

print("begin cleanup")
# if destroy was not called, this will crash in Python3

ZMQStream does non-copying sends by default for some reason, which is a bad choice, so I am going to revert that in PR #172.  For now, the answer is going to be: you must use explicit cleanup if you are doing non-copying sends and might discard them at shutdown due to LINGER.  In your sample script, that amounts to a simple ctx.term at the end to ensure clean shutdown.
I'm not sure this is a huge deal, because it only affects already exiting processes, but there have been other places where grabbing the GIL from the io_thread has caused weirdness.
[1] The only solution I have in my head is for the free_fn to actually be called from yet another thread that pyzmq creates, and the io_thread's callback somehow GIL-lessly puts the necessary info in a queue and notifies (or spawns) the thread, which grabs the GIL and deletes the object.  That should avoid this problem, because it doesn't really matter that the free_fn is aborted at shutdown, it only matters that the io_thread is killed, which will not happen if it never grabs the GIL.  But that means I would have to look up how to spawn and communicate with a C-thread in a platform-independent way, which isn't going to happen soon.

Thanks for the explanation. I'm surprised that the stream.close() in the original example doesn't take care of the problem. If stream.close() executes, why is there still a message hanging around to be cleaned up at ctx.term()?


Spacecharge memory footprint

To check memory occupancy I install gpustat:
$ pip install gpustat

You can monitor the memory occupancy continuously by:
$ watch -n1 gpustat

On cupy memory is freed only when needed. To see the actual memory footprint you need to run:
import cupy as cp
cp._default_memory_pool.free_all_blocks()

The result is that the occupancy of the spacecharge PIC lenses is 2GB/lens. Too much to allow realistic SPS case on TITAN V

Several improvements to minimise memory occupancy:

workspace for Poisson solve allocated on the fly (no visible overhead on computing time in cupy, some effect on pyopencl)
Avoid replicating Green matrix for all z slices (2.5D), use array broadcasting in cupy (no overhead) and explicit loop in pyopencl (some overhead)
Avoid putting all PICs in the same buffer (the the buffer grows it needs space to make a full copy of itself)


halc_greedy_decode triggers device-side assert

Hello! I try to run HALC with greedy decoding, which calls halc_greedy_decode function，but triggers device-side assert. The log is:
out = model.generate(
  File "/home/bingxing2/home/scx7ky7/.conda/envs/HALC/lib/python3.9/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
    return func(*args, **kwargs)
  File "/home/bingxing2/home/scx7ky7/zehao/HALC/./minigpt4/models/llava.py", line 224, in generate
    output_ids = self.llama_model.generate(
  File "/home/bingxing2/home/scx7ky7/.conda/envs/HALC/lib/python3.9/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
    return func(*args, **kwargs)
  File "/home/bingxing2/home/scx7ky7/.conda/envs/HALC/lib/python3.9/site-packages/transformers/generation/utils.py", line 1754, in generate
    return self.halc_greedy_decode(
  File "/home/bingxing2/home/scx7ky7/.conda/envs/HALC/lib/python3.9/site-packages/transformers/generation/utils.py", line 5447, in halc_greedy_decode
    context_logits, _ = self.get_intermediate_logits(
  File "/home/bingxing2/home/scx7ky7/.conda/envs/HALC/lib/python3.9/site-packages/transformers/generation/utils.py", line 5727, in get_intermediate_logits
    outputs = self(
  File "/home/bingxing2/home/scx7ky7/.conda/envs/HALC/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/bingxing2/home/scx7ky7/zehao/HALC/./minigpt4/models/llava_llama.py", line 80, in forward
    outputs = self.model(
  File "/home/bingxing2/home/scx7ky7/.conda/envs/HALC/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/bingxing2/home/scx7ky7/.conda/envs/HALC/lib/python3.9/site-packages/transformers/models/llama/modeling_llama.py", line 578, in forward
    layer_outputs = decoder_layer(
  File "/home/bingxing2/home/scx7ky7/.conda/envs/HALC/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/bingxing2/home/scx7ky7/.conda/envs/HALC/lib/python3.9/site-packages/transformers/models/llama/modeling_llama.py", line 293, in forward
    hidden_states, self_attn_weights, present_key_value = self.self_attn(
  File "/home/bingxing2/home/scx7ky7/.conda/envs/HALC/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/bingxing2/home/scx7ky7/.conda/envs/HALC/lib/python3.9/site-packages/transformers/models/llama/modeling_llama.py", line 204, in forward
    query_states, key_states = apply_rotary_pos_emb(query_states, key_states, cos, sin, position_ids)
  File "/home/bingxing2/home/scx7ky7/.conda/envs/HALC/lib/python3.9/site-packages/transformers/models/llama/modeling_llama.py", line 135, in apply_rotary_pos_emb
    gather_indices = gather_indices.repeat(1, cos.shape[1], 1, cos.shape[3])
RuntimeError: CUDA error: device-side assert triggered
CUDA kernel errors might be asynchronously reported at some other API call, so the stacktrace below might be incorrect.
For debugging consider passing CUDA_LAUNCH_BLOCKING=1.
Compile with `TORCH_USE_CUDA_DSA` to enable device-side assertions.

Could you please check halc_greedy_decode function once more? Thanks!

Hi, thanks for your interests in HALC. This seems to be a bug of inconsistent pytorch version. Have you successfully addressed issue?


Bugfix/gdk nfr latency fix

Description
Clean up some dead code and fix latency NFRs

Latency NFRs were fixed in a smaller PR

Latency NFRs were fixed in a smaller PR


issues/195 - Stylesystem Bugfix : Code refactored as per new design

Description
Existing code (v2.0.5) assumes appliedCssClassNames is available as a prop when obtaining component mapping. But with SPA 2.0 design the prop will be available only to children under EditableComponent. In addition, while authoring, when we change styles, model is updated, but EditableComponent doesn't recieve the new style info as our code is bound to model passed from parent e.g. container. With these inferences in mind, made changes below

Accessing appliedCssClassNames via model prop as it is not available
Enable applying styles dynamically while authoring
Rely on model state for re-rendering with new classes while authoring

package.json with new version can be updated upon confirmation from approvers. Additional unit tests can be added if approvers deem necessary
Related Issue
#195
Motivation and Context
Same as description, as we all understand the power of stylesystem and keeping this feature supported is critical for us to upgrade to SPA 2.0 where one may choose to do a hybrid of SPA implementations e.g an entire help section coming from AEM as-is and other pages from React app share some sections that are editable via AEM
How Has This Been Tested?

Confirmed that the changes reflect when using Responsive Grid component and a normal container component covering scenarios of altering styles on container based comps and normal comps
EditableComponent unit test has been modified with new structure of the data

Screenshots (if appropriate):

Issue link can be visited before this fix
After the PR is merged below is the behavior for the usecase explained in issue.

Inside AEM Editor with Changing Styles
Changed background of text from Skyblue to Gray

View as Published Experience

Types of changes

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[X] I have signed the Adobe Open Source CLA.
[X] My code follows the code style of this project.
[X] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[X] I have read the CONTRIBUTING document.
[X] I have added tests to cover my changes.
[X] All new and existing tests passed.

@sharanyavinod , @CezCz, @friendlymahi , @habansal , @niekraaijmakers , @vladbailescu - Requesting your help for moving this fix. Advise me if its not a valid usecase or if you want me to make any further changes, Thanks !

Hello. Good Morning to you ! Can someone please share some feedback on this PR? Thanks !

@sharanyavinod - Any feedback on this PR?

Thanks @sharanyavinod . Can you please merge the PR in this case?

Hello. Hope you are doing well. Any update on this request? Thanks


pyqt6: 6.6.0 -> 6.6.1

Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 276097 run on x86_64-linux 1

57 packages built:

activitywatch
anki
anki.dist
anki.doc
anki.man
aw-qt
aw-qt.dist
calibre
hydrus
hydrus.doc
khoj
khoj.dist
maestral-gui
maestral-gui.dist
mnemosyne
mnemosyne.dist
nanovna-saver
nanovna-saver.dist
python310Packages.echo
python310Packages.echo.dist
python310Packages.glueviz
python310Packages.glueviz.dist
python310Packages.openusd
python310Packages.openusd.doc
python310Packages.pvextractor
python310Packages.pvextractor.dist
python310Packages.pyqt6
python310Packages.pyqt6-charts
python310Packages.pyqt6-charts.dist
python310Packages.pyqt6-webengine
python310Packages.pyqt6-webengine.dev
python310Packages.pyqt6-webengine.dist
python310Packages.pyqt6.dev
python310Packages.pyqt6.dist
python311Packages.echo
python311Packages.echo.dist
python311Packages.glueviz
python311Packages.glueviz.dist
python311Packages.openusd
python311Packages.openusd.doc
python311Packages.pvextractor
python311Packages.pvextractor.dist
python311Packages.pyqt6
python311Packages.pyqt6-charts
python311Packages.pyqt6-charts.dist
python311Packages.pyqt6-webengine
python311Packages.pyqt6-webengine.dev
python311Packages.pyqt6-webengine.dist
python311Packages.pyqt6.dev
python311Packages.pyqt6.dist
qutebrowser
qutebrowser.dist
retext
retext.dist
unbook
zapzap
zapzap.dist


Bump react-scripts package

Update to latest react-scripts in the react UI.
Signed-off-by: SuperQ<EMAIL_ADDRESS>

Bleh, react.


Create rating-3.html

Created Component

Yeah you can also do a scale effect /. translate y on hover. Otherwise everything looks perfect. @nik132-eng

If you want i can do this

Yeah do that then it will look perfect. @nik132-eng

cool doing it


Create settings class for changing web whatsapp settings

Hey, guys
I finished the theme part. I opened the PR not to lose the deadline :D
Resolves #39

Well done! 🤗
@beatorizu those conflicts happen because I updated some things after you forked tithiwa
i.e we need to update our forked version to the new version to prevent those conflicts.

@NavpreetDevpuri could you add the hacktoberfest-accepted label?


Issues with side panel glitching out

Ever since I started using RuneLite, I found that the (right) side panel where the extra features are bugs out when you click on a setting / feature and then hover down below the feature for a quick second. The image / information displayed covers over features below it as you hover the mouse over the panel. I have only been using this program for a couple of days and so far it's worked great. I'm wondering if anyone else has been having this issue and ignoring it, or it's an issue unique to me. Thanks!

I haven't tried that, but maybe I got an outdated download when I installed on the 22nd. I'll keep you posted to see if that helps. Thanks!

It looks like that fixed it. Thanks!


Static routes existing in ConfigDrive are not applied

Hi,
I'm provisioning a Windows image by ConfigDrive with bellow openstack/latest/network_data.json:
{
  "links": [
    {
      "id": "default-windows-eth1",
      "name": "eth1",
      "type": "vif",
      "ethernet_mac_address": "0e:16:9b:84:61:fd",
      "mtu": 1500
    }
  ],
  "networks": [
    {
      "id": "default-windows-eth1",
      "type": "ipv4",
      "link": "default-windows-eth1",
      "ip_address": "<IP_ADDRESS>",
      "netmask": "<IP_ADDRESS>",
      "routes": [
        {
          "network": "<IP_ADDRESS>",
          "netmask": "<IP_ADDRESS>",
          "gateway": "<IP_ADDRESS>"
        }
      ]
    }
  ],
  "services": [
    {
      "type": "dns",
      "address": "<IP_ADDRESS>"
    },
    {
      "type": "dns",
      "address": "<IP_ADDRESS>"
    }
  ]
}

I expect a route to <IP_ADDRESS>/24 being set, but it's all I'd get in Windows:

I read openstack and configdrive tests and looks routes being parsed correctly but I don't see any test targeting routes in cloudbaseinit/tests/osutils/test_windows.py and they are all about static network address setting. Further investigation showed NetworkConfigPlugin itself just set network interface IP addresses and consequently just local routes. There is add_static_route function but looks it's unrelated to my case which datasource is ConfigDrive.
So IIUC ConfigDrive Network Routes are being ignored now. Am I right?

I pushed some unpolished work you can see here. I have no idea about codes trying to handle legacy and new API and my code lacking those. It works for Windows server 2019 at least.

Hi,
I would appreciate any thoughts or suggestions about this. Is it totally out of scope of this project? in that case it would be nice to document that cloudbase-init does not handle static routes, except for default gateway. Do you think it's good to cover static routes like cloud-init do?
I love to have this functionality in cloudbase-init rather than our private fork that would diverge us from upcomming developments and I should reach a decision at some point.

Hello,
Thank you for the contribution. Currently, we use the OpenStack review/gating for the patches, and Github for issue management. Can you add the patch to https://review.opendev.org/?
Here is a good how to for achieving this:
https://www.openstack.org/blog/submit-your-first-openstack-patch-in-three-steps/
https://docs.openstack.org/zaqar/latest/contributor/first_patch.html - you need to replace zaqar with cloudbase-init.
I would gladly get the code that you wrote and put it to gerrit, but because of how licensing works, you are required to sign the CLA.
Thank you,


options.eol should default to ""?

I was getting spurious newlines between log outputs using Visual Studio Code's debugger when I was not seeing it in the Chrome DevTools console.
  // No blank lines output in VSC or Chrome
  console.log("console: log");
  console.debug("console: debug");
  console.error("console: error");

  // Blank lines output in VSC but not Chrome
  logger.debug("winston: debug");
  logger.warn("winston: warn");
  logger.error("winston: error");

Chrome screenshot showing no blank lines for code above:

It turns out these newlines are because of the default eol option being equal os.EOL.  Given that by default console will place logs on their own line in both Node and the browser (e.g. Chrome), I would suggest a good default for options.eol is actually "" instead of os.EOL.
I'm going to set the option explicitly in my code, but would be happier to see the default changed so that both console and eol options are paired properly.

So it turns out setting the eol option to "" has no effect because options.eol   || os.EOL evaluates to os.EOL (the empty string is falsy).
Aside from merging the cited PR, the only other workaround is to pass an eol option as "\0" which isn't very intuitive.

the workaround yould be fixed with a test:
(options.eol || options.eol === "" && "\0") || os.EOL

this checks if the options.eol is falsy and then if it equals "" (empty string) and replaces it with \0 else it uses the fallback


Add more unittests for asyncio stream mode

It's not well covered.

Hi @yifeikong,  I would like to take this up.
Could you please give me more details, need a little bit of more context?

There are a number of tests for stream mode in sync version.
https://github.com/yifeikong/curl_cffi/blob/45e687b286dc0eb9402277d5f37c834cd4a75fd5/tests/unittest/test_requests.py#L430-L610
But the async tests are not matched.
https://github.com/yifeikong/curl_cffi/blob/45e687b286dc0eb9402277d5f37c834cd4a75fd5/tests/unittest/test_async_session.py#L319-L369

Ok, sounds good! 🚀
Shall I have it assigned it to me, please?
I will gladly work on it right after I have it. 🧐
I am happy to contribute to improving the test suite for this critical aspect of the project. My approach would involve thoroughly understanding the existing sync mode tests, identifying the gaps in the async mode tests, and then crafting robust and comprehensive tests to cover these areas effectively. 🔍
Thank you for considering my request.  🙏
Best regards!


Ros error: The 'sentence' field must be of type 'str'

ROS2 Humble
When running nmea_topic_serial_reader, receive this error. Think it is this
Should be data.decode("ascii")

Thank you for finding this and for the pull request!


goresym: 2.7.2 -> 2.7.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/mandiant/goresym/releases.
meta.description for goresym is: Go symbol recovery tool
meta.homepage for goresym is: https://github.com/mandiant/GoReSym
meta.changelog for goresym is: https://github.com/mandiant/GoReSym/releases/tag/v2.7.3
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.7.3 in filename of file in /nix/store/kzwj01zjs7fljhsz3bpxs1kh273pnwyw-goresym-2.7.3

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
goresym

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/kzwj01zjs7fljhsz3bpxs1kh273pnwyw-goresym-2.7.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A goresym https://github.com/r-ryantm/nixpkgs/archive/5c6a9c72e6360a86edbe92a36751a7c3827fad9b.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/5c6a9c72e6360a86edbe92a36751a7c3827fad9b#goresym

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

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

goresym

Maintainer pings
cc @pyrox0 for testing.

Result of nixpkgs-review pr 304412 run on x86_64-linux 1

1 package built:

goresym


Visual Studio 2017 tagged as incomplete c++11

Expected Behavior
I expect to be able to compile dlib with the latest visual studio 2017
Current Behavior
Get a warning saying that is not c++11 complete:
-- Your version of Visual Studio has incomplete C++11 support and is unable to compile the -- DNN examples. So we are disabling the deep learning tools.  If you want to use the DNN -- tools in dlib then update your copy of Visual Studio.
I do not have multiple installations of visual studio 2017
Steps to Reproduce
just running cmake

Version: latest, from master
Where did you get dlib: github
Platform: win10 64 bit
Compiler:
-- The C compiler identification is MSVC 19.11.25547.0
-- The CXX compiler identification is MSVC 19.11.25547.0

That's not the latest version of visual studio.  There is a new one and it has better C++11 support.

hasn't visual studio being c++11 complete since vs 2015? I did a fresh install of the latest 4 weeks ago.  I have visual studio 15.45, I checked the lastest 15.5 version and did not see anything related to c++11 in the release notes. Can you please tell me what is required such that a month old visual studio won't cut it?
Please advise
M.

No, visual studio has never had complete C++11 support.  It's far and away the worst compiler in terms of standards conformance.  However, the visual studio dev team is actively working on it and it gets better all the time.  What is required is a compiler with good enough C++11 support.  Get the newest visual studio.  It finally has good enough C++11 support to compile this stuff as of like 2 weeks ago.

Thank you so much for your reply, and thank you for correcting my understanding, I always referred to this:
https://msdn.microsoft.com/en-us/library/hh567368.aspx?f=255&MSPPError=-2147217396
And most the boxes for 2015 were ticked so I expected 2017 to be by far done. I will update and try.
Cheers and happy holidays

No problem :)


Fix grammatical error

Thanks for the contribution! However, this is a read-only mirror. please read the contribution guide. Also, feel free to join us on chat!


Add support for product patches

It would be great if vcc would support downloading product patches.
For example:
As of now ESXi 7.0U3j has been released but is currently only available via the Product Patches site in Customer Connect.
The latest currently available version under Product Downloads is ESXi 7.0U3g.
Even ESXi 7.0 U3i is missing in Product Download which as been released Dec 08 2022.
Thanks for this awesome tool!

@vzovko thanks for raising this. Can you provide an example URL and the workflow you use to find the patches?

Typically, I get a notification that a new ESXi update has been released. What I do then is as follows:

Check release notes and build details: https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-esxi-70u3j-release-notes.html
Log into customer connect via https://customerconnect.vmware.com/
Go to to Products and Accounts > My Products > VMware vSphere > View Download Components
Select version 7.0 and Go to downloads for VMware vSphere Hypervisor (ESXi). Currently the latest version available there is 7.0U3g but 7.0U3j is already available.
Go to Products and Accounts > Product Patches.
Select ESXi (Embedded and Installable) and version 7.0, then click Search.
The first result shows the latest release is VMware-ESXi-7.0U3j-21053776-depot.
Click Download now to retrieve the file.

It would be great if vcc could search, inspect and download those patches.

Thanks for providing further clarification. I see what's involved now and think that it would be a decent amount of work to update the SDK for this new workflow. I'll add it to the backlog, but can't commit that it will be done unless someone in the community picks it up, as vcc doesn't have the funding like you would get with an official product, meaning folks would likely be working on it during their own time.

Maybe someday this project will receive funding. I'll reach out to our TAM, maybe he can spread the word around of what a useful tool you provide here.
Thanks for adding this to your backlog.


Register cluster-id and cluster-name flags through hive

Currently, the clustermesh package already leverages a ClusterIDName struct to wrap the ClusterID and ClusterName information. Let's use it also to register the associated flags, so that we can directly depend on it on the different components, and reuse it for the kvstoremesh and clustermesh-apiserver binaries uniformly.
To avoid the need for modifying all usages, we preserve the current fields inside DaemonConfig, which continue to be populated as before.
With more subsystems relying on the ClusterInfo populated through the hive, let's stop automatically inferring these parameters in case of external workloads, as this introduces a problematic dependency order.
Depends on https://github.com/cilium/cilium-cli/pull/1948

/test

/test

Rebased onto main to pick CI changes

/test

Code-wise looks good to me.
I'd be interested to know more about the motivation behind this change, and what the plan is going forward. The cluster name is something that is needed by many subsystems to namespace global resources: Node names, EC2 network interface tags in ENI IPAM, service labels, identity labels.

Essentially this came up while refactoring the clustermesh-apiserver and kvstoremesh in preparation to merging them into a single binary (as part of a larger effort to unify all clustermesh-apiserver components into a single image for simplicity: https://github.com/cilium/cilium/issues/23770).
The idea is to extract these two flags into a separate object injected through Hive, so that we can reuse them uniformly in all the different components, as well as remove the hacky conversions from the global DaemonConfig, which were for instance used before in the clustermesh cell. Over time, it would be great if also the other subsystems requiring these parameter could depend directly on the ClusterIDName struct, rather than reading the global DaemonConfig.

Is the goal that all those subsystems (node discovery, IPAM, service, identity allocation, IPCache) eventually rely on the clustermesh cell? Will that not cause potentially circular cell dependencies?
While I agree we should reduce global configuration state, the cluster name is something that is inherently global and relevant to a lot of subsystems. If we want to make the clustername and cluster id a dependency to be injected into other subsystems, it should probably be a leaf dependency that depends on nothing else, so I'm not sure if the clustermesh cell is the right place (since it itself has lots of dependencies already). Did you consider introducing a separate cluster-id cell instead?

The different subsystems can depend on the ClusterIDName struct alone, without needing to depend on the whole ClusterMesh object (which would pose circular dependency issues as you mentioned). For the same reason, the struct is defined in a separate subpackage, and registered at the top of the cell hierarchy, not as part of the clustermesh cell (which only depends on it).

For the same reason, the struct is defined in a separate subpackage, and registered at the top of the cell hierarchy, not as part of the clustermesh cell (which only depends on it).

Awesome, thanks for clarifying. I'm still not super familiar with the hive framwork, so I didn't know one could depend on struct alone this way. Sounds good to me!

/test

/test

@derailed PTAL

/test

/test

Removed CI-related reviewers because that commit has been dropped.

/test

I've reverted the changes affecting external workloads, as the scope of this PR was increasing too much. Let's see if now it passes all tests.

/test

@derailed PTAL


HWKAPM-484 Refactor the MDBs to have a single processor mechanism for…

… handling individual and bulk processing, with the same retry mechanism
Review notes:

Consolidation of the processing of individual and bulk messages into the main processor mechanism, rather than managed separately by two derived MDB implementations.
Renamed processor methods to better reflect their purpose

LGTM

@jpkrohling Thanks!


Added Changelog

This is not really an issue, so please close, when read!
Hi everyone, Hi @awickert,
I took the liberty and added a changlog to the master branch to keep track of changes, additions, etc, that go into future versions. With more people contributing, I hope to keep track of more recent changes.
The structure is rather simple: The changelog consists of a list of sections, one per version, latest first. Above the latest version section, there is a section for the next, upcoming version. Whenever there is an addition of a feature or a change in code (either through direct edits or through PRs), add the changes as a bullet point to the upcoming versions sections.
When ready for the next version, change the upcoming version section to the next build-version and introduce a new upcoming version.
Final note on the bullet points: Be precise and comprehensive, just like in your commit messages.
Best regards,
Jacob

@awickert , @jnuernberg ,I am noticing a potential user-facing problem now that we have multiple people committing revisions. The version a user downloads with the Arduino IDE Library Manager becomes out of date. It appears we need to do additional steps after we merge a PR and enter a note in the Changelog?


redundant files in build directory after bundling

It looks like the bundling step from @snowpack/plugin-parcel doesn't do any kind of cleanup after bundling, so the build directory ends up containing the bundled/fingerprinted assets and the original output from snowpack build.
I think it'd make more sense to file this issue wherever that plugin code lives, but I can't find the repo!
{
  "scripts": {
    "mount:public": "mount public --to /",
    "mount:src": "mount src --to /_dist_"
  },
  "plugins": [
    "@snowpack/plugin-parcel"
  ]
}

Produces something like:
src/
  index.js      # original source
build/
  web_modules/
  _dist_/
    index.js           # this is the index.js with rewritten web_modules paths
  _dist_.a45130ae.js   # this is the bundled file

After bundling, I want to deploy the build dir, but I don't really want to deploy build/web_modules or build/_dist_ because they aren't going to be used.
Ideally the bundling plugins would output the bundled version to a separate directory (I think Parcel already does this with a .build directory) then clean build and copy the contents across.

No worries, moving to the proper repo


Assertions to guard against invalid CSS colors as fills/strokes

https://github.com/phetsims/capacitor-lab-basics/issues/148 was caused by the string 'none' being set as a fill, and it looks like there are no assertions to guard against this.

Added assertions, fixed both cases where failures were found.


Homepage doesn't say what this library does. You have to come to Git to read "Syntax Highlight"

Really. Just add that sentence to the home page. It's wonderfull it is trusted by stack overflow. Even works with zero dependencies. But there isnt a single clear, objective sentence describing what it does in the home page :)

There is a proposed fix in https://github.com/highlightjs/highlightjs.org/pull/12 incl. a preview:

https://deploy-preview-12--hljs.netlify.app

@malkiebr Would that be better?


Added RegisteredModel handlers and tests

PR Checklist

[ ] A description of the changes is added to the description of this PR.
[ ] If there is a related issue, make sure it is linked to this PR.
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If you've added or modified a feature, documentation in docs is updated

Description of changes

Added handers and tests for CRUD operations on registered models.
Added CLI support for CRUD operations on registered models.
Fixed some inconsistencies with the API definition.
Added model handling in schema deletion.

It took nearly a week for someone to review... Amazing.... _ _#

lgtm for the most part, would like to understand a couple of items:

why a separate storage root?
relation between registered model info and model version info.

So I am not married to having a separate storage root here.  I mainly wanted to make sure I was avoiding any conflict with the existing storage root and code around it vs. fixing everything that was using it for an uncertain implementation.  I can add a followup commit that unifies the storage roots, changes the existing usages to use catalogId and schemaId instead of names, and removes all references to deletion (since we punted deletion to a later version).
The registered models and model versions are related but not the same.  There is a one to many relationship with registered models to model versions.  A registered model, may contain any number of model versions.  Think of a registered model as a reserved namespace for the model in question.  As you iterate on your model, you want to keep track of the different versions of that model.  Lets say you used different input sources or you changed hyperparameters.  You would create a new version for each of those differences and the metadata w/in a model version would help you keep track of that.  That's why model versions have the notion of source (the location of the original experiments artifacts that generated that specific model version) and runId (your ML library's way of uniquely tracking the execution pipeline that created the model).  These pieces of metadata don't live on the registered model because the registered model is just the container.  In UC parlance, the registered model is the securable.  The model versions are simply sub-securables.  When we get ACL's into the system, then ACLs will apply to the registered model, and the registered model ACLs will transitively be applied to the model version.


Throughout, invoke build before commands

May need a bit of additional work to suppress build output from appearing in stdout, if it is desirable do do, e.g.:
FOO=$(spin run something)

Steps:

Use contextlib redirect_stdout around _run cmd
Extend build to allow a quiet mode, in which output=False on each _run call

Hrm that CI failure wasn't triggered by the code changes; something with Ubuntu update :/


Edit profile page UI

Description
The following changes have been implemented:

User information and projects summary organised using cards
User information displayed using Label component instead of Input components.
Modal added for editing the name and username.

This is done to make the information more concise and logical.
Fixes #371 (issue)
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?

The profile page was opened for a pre-existing user with 0 labels and images. 1 image and 1 label were added and the profile page was checked again.
The Edit button was clicked and the name and username of the user was changed and then saved.

Test Configuration:

New profile page UI:

Modal for editing user details:

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

@laksh22 Great work! But before merging this I think everyone should have say on the UI changes specially from now.

@laksh22 Codacy checks are failing, have a look on them.

@Tushar19varshney One of the checks is giving an error with const { name, username, open } = this.state saying that it's an unnecessary block. Not sure how to fix this one aside from removing destructuring


Remove the use of the word Breadcrumb from code not scheduled to be deleted

Goal
From this point forth, the word "Breadcrumb" will only apply to legacy code as well as the telemetry formerly known as "CustomBreadcrumb". So say we all
Testing
Just a rename

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

#668  👈
#667
#666
#436
#435 : 1 other dependent PR (#437 )
master

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

Join @bidetofevil and the rest of your teammates on  Graphite

Merge activity

Apr 8, 10:52 AM EDT: @bidetofevil started a stack merge that includes this pull request via Graphite.


Implement Pigeon fee market

Implement pigeons setting their own fees and paloma exposing the lowest price to users

Allow Pigeons to set their fee as a percentage over current gas fee
Paloma needs to track the pigeon's fees
Paloma needs to expose the total fee (gas fee + pigeon fee + security fee + community fund fee + ?) to users when they want to schedule a job

More info in epic: https://www.notion.so/volumefi/EPIC-09-26-22-Paloma-Gas-Management-78319280833e4c7c8ffad368eddb1d91

Closed and fixed with #1220


Options couldn't be activated

Hey,
I setted up a new HomeBridge Server. After enabling all devices in config, all switches for "options" are not visible.
"options": {
"wifi2": [
true,
true
],
"wifi5": [
true,
true
],
These switches should enable it, right?? If so, then this doesn't work :-(

Found the problem... Fritzbox wasn't set to active facepalm

Found the problem... Fritzbox wasn't set to active facepalm

Help me please, My homekit no show switch option
Thank you


OCPBUGS-42514: azureclient: stop validating credentials when creating the client

different operations in Azure require different sets of credentials. some operations for example only need a storage account key to authenticate with Azure API.
since we cannot predict which operation the caller will need, we cannot validate auth related options on client instantiation time.
this didn't use to be an issue because the client was only used for private endpoint configuration, which did not use account key for auth, so validation was more predictable.

/jira refresh

test failures look like flakes to me.
/retest

/retest

/label qe-approved
/label cherry-pick-approved

/cherry-pick release-4.17

Looks like merge conflicts are happening because this change has not yet merged on 4.17, but 4.18 has it: https://github.com/openshift/cluster-image-registry-operator/pull/1125
It's probably easier and safer to wait until that PR merges, then try the automated cherry-pick again, so I'll do that.

/jira backport release-4.17


Translate quality badges and quality names

Sumary of proposed changes
This is my second approach to https://github.com/sampotts/plyr/pull/878.
I have extended i18n to allow nested translations with the dot notation. So you can call i18n.t('qualityName.720', this.config). And with this change I added the ability to translate the badge and the quality name.
Result:

… another way to solve this issue would be to add a label to the <source> elements. That would be the same approach as captions is currently using. But this seems like a complicated change to me.

… another way to solve this issue would be to add a label to the <source> elements. That would be the same approach as captions is currently using. But this seems like a complicated change to me.

Thank's for the review. For some reason the ESLint tweak commit remained in my branch, but I guess this is not a problem.

You can remove commits, combine etc with an interactive rebase (ex git rebase -i HEAD~9), but do read up on the topic if you haven't used this before. I'm not sure it's a problem per se. It depends on Sam's merging strategy.

@sampotts What do you think about this changes?

Sure! I've renamed the variable 😄

Thanks mate! Awesome solution btw. I'll deploy a new version shortly. I just need to work on a small UI bug I've noticed.


Notifications tray lost the placeholder text

I don't have any notifications and this is what I see now

@rmisio take a look at this when you have a chance.

@morebrownies If you pull latest, this should be fixed.

I wasn't able to confirm since I have notifications now. @drwasho can you test and close if you can confirm it is working?

Definitely fixed.


envoy: Make the log level computation thread-safe

The previous logic was reading the Level of a Logger and an Entry
in a non-threadsafe manner. Also, using an Entry's Level was not
reliable since that is not set until the Entry's first log
statement.
Fixes: https://github.com/cilium/cilium/pull/4937
Fixes: https://github.com/cilium/cilium/commit/d5345cf282f219e05f91b2581b100711c95892ae
Signed-off-by: Romain Lenglet<EMAIL_ADDRESS>

This change is

This is a pretty critical bug fix, since we seems to systematically lose the Envoy logs with the implementation in 1.2 / master.
The symptom is that Envoy is started with the off log level:
$ ps -ef | grep envoy
...
root      7602  6087  2 05:52 ?        00:00:00 cilium-envoy -l off -c /var/run/cilium/bootstrap.pb --base-id 0 --log-format %t|%l|%n|%v

Successful CI build: https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/5695/


Peer dependencies for React 0.14

Hi,
I have updated my app to React 0.14 and I get a peerDependencies error. I have tried running react-datepicker with React 0.14 and it works fine except for some warnings. Do you need help to update the package to work with the new React 0.14 api?
Most of the warnings are related to react-dom:
Warning: React.render is deprecated.   Please use ReactDOM.unmountComponentAtNode from require('react-dom') instead.

Cheers,
Arnaud

Would be awesome if you could create a PR to upgrade React!

Sounds good, I will do that ;)

@martijnrusschen done!

Let me know when you bump up the version number ;)

I released a few minor versions to get this working, but it looks like we're still depending on React. things in https://github.com/Pomax/react-onclickoutside. We need to figure out what's wrong here, but I have no time left anymore for today. Would be awesome if you had some time today to look into this.

@martijnrusschen your PR on https://github.com/Pomax/react-onclickoutside have been merged. I think you can reference the main repository instead. I'm trying to make it work on react 0.14.

Version 0.14.5 should fix this issue.


Incorrect capitalisation of "ConfigParser"

Having upgraded pex from 1.1.4 to 1.1.5, my build now fails with:
pex: Building pex :: Resolving distributions :: Translating /var/lib/jenkins/home/jobs/deploy_dashboard/workspace/build/platforms/dashboard/tmp/tmptJvrim/python-jenkins-0.4.12.tar.gz into distribution
pex: Building pex :: Resolving distributions :: Translating /var/lib/jenkins/home/jobs/deploy_dashboard/workspace/build/platforms/dashboard/tmp/tmptJvrim/python-jenkins-0.4.12.tar.gz into distribution :: Packaging python-jenkins
pex: Building pex :: Resolving distributions :: Translating /var/lib/jenkins/home/jobs/deploy_dashboard/workspace/build/platforms/dashboard/tmp/tmptJvrim/python-jenkins-0.4.12.tar.gz into distribution :: Packaging python-jenkins :: Installing /var/lib/jenkins/home/jobs/deploy_dashboard/workspace/build/platforms/dashboard/tmp/tmpbRO1kr
**** Failed to install python-jenkins-0.4.12. stdout:

**** Failed to install python-jenkins-0.4.12. stderr:
ERROR:root:Error parsing
Traceback (most recent call last):
  File "/var/lib/jenkins/home/jobs/deploy_dashboard/workspace/build/platforms/dashboard/venv2/lib/python2.7/site-packages/pbr/core.py", line 111, in pbr
    attrs = util.cfg_to_args(path, dist.script_args)
  File "/var/lib/jenkins/home/jobs/deploy_dashboard/workspace/build/platforms/dashboard/venv2/lib/python2.7/site-packages/pbr/util.py", line 264, in cfg_to_args
    wrap_commands(kwargs)
  File "/var/lib/jenkins/home/jobs/deploy_dashboard/workspace/build/platforms/dashboard/venv2/lib/python2.7/site-packages/pbr/util.py", line 566, in wrap_commands
    cmdclass = ep.resolve()
  File "/var/lib/jenkins/home/jobs/deploy_dashboard/workspace/build/platforms/dashboard/venv2/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2386, in resolve
    module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/var/lib/jenkins/home/jobs/deploy_dashboard/workspace/build/platforms/dashboard/venv2/lib/python2.7/site-packages/pex/commands/bdist_pex.py", line 4, in <module>
    from configparser import ConfigParser
ImportError: No module named configparser
error in setup command: Error parsing /var/lib/jenkins/home/jobs/deploy_dashboard/workspace/build/platforms/dashboard/tmp/tmpHgSLc5/python-jenkins-0.4.12/setup.cfg: ImportError: No module named configparser

Surely this line should be "from ConfigParser import ConfigParser" not "from configparser import ConfigParser"?

Sorry about this, I should have demanded a test for bdist_pex.  We CI against 2.6 - 3.5 which would have caught this python3-only import.  I'll whip up a test and fix later today unless you beat me to it.

@tjwalton @pikeas - if either of you have bandwidth to review #246 I'd be grateful.

Fix is in master @ https://github.com/pantsbuild/pex/commit/a255b3ad7f0c72e6588be1059f70d14cdc94c7ce

@jsirois Thanks for this.  Looks good and is working for me now.


ObjLoader2 async

Make the obj parsing async so that the parsing of great amount of lines >100k does not freeze browser.

Make wu_3d_view as a class
Load diffusion image on the fly
Place objLoader2

Closed by 9ecab8a
I immitated $_POST to $_FILES
For big files you need to modify in php.ini
post_max_size=512M
memory_limit=512M
Change also in .htaccess
php_value upload_max_filesize 512M
php_value post_max_size 512M
php_value max_input_time 2400

We should do smth for the uploading. It may take a long time if the obj is too big ~150MB. Can we monitor POST submission data and provide a progress bar ?


Add explicit requirement for azure-core in mgmt-compute

https://github.com/Azure/azure-sdk-for-python/pull/34770 added a direct dependency for azure.core, and it actually requires this to be newer than 1.28.
Related to https://github.com/Azure/azure-sdk-for-python/issues/34091
Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

Hi @msyyc - could you confirm whether this setup.py is auto-generated and therefore the codegen needs updating for this dependency?

Python Mgmt SDK depends on azure-mgmt-core instead of azure-core directly
Python Mgmt SDK is auto generated and it doesn't use azure.core.pipeline.policies.SensitiveHeaderCleanupPolicy by default

Above all, if your application want to use SensitiveHeaderCleanupPolicy, it is better to add it by yourself instead of changing SDK dependency. After all, not all SDK users need SensitiveHeaderCleanupPolicy

actually, i don't want to use SensitiveHeaderCleanupPolicy, but if you write the following code:
self.credential = DefaultAzureCredential()
self.resource_client = ResourceManagementClient(self.credential, self.subscription_id)
self.compute_management_client = ComputeManagementClient(self.credential, self.subscription_id)
It will fail with "azure.core.pipeline.policies" does not have property 'SensitiveHeaderCleanupPolicy'.  that is when using the latest mgmt-compute with an azure-core prior to 1.28.1.  perhaps the reference is indirect via azure-mgmt-core, however the SDK itself uses this property so this fails at runtime.

/reopen

I'm having totally the same issue as it is described by @jim-cooley.
I'll try to simply access synapse notebook contents by using azure-synapse-artifacts.
Using the recommended ArtifactsClient by simply adding credentials and the endpoint I get the same error. Hence it should be reopened.


tensorflow crashed when use image.transform function

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): arch Linux latest and Ubuntu
TensorFlow version and how it was installed (source or binary): binary on arch, source on ubuntu
TensorFlow-Addons version and how it was installed (source or binary): source version 0.11.2
Python version: 3.8 on arch, 3.6 on ubuntu
Is GPU used? (yes/no): yes

Describe the bug
tensorflow crashed when use image.transform module
Code to reproduce the issue
import tensorflow as tf
import tensorflow_addons as tfa
import numpy as np
if name == 'main':
src = tf.Variable(np.random.random((1, 100, 100, 3)))
dst = np.random.randint(0, 3, (1, 100, 100))
with tf.GradientTape() as tape:
    out = tfa.image.transform(src, np.random.rand(8))
    loss = tf.nn.sparse_softmax_cross_entropy_with_logits(dst, out)
    loss = tf.reduce_mean(loss)
tape.gradient(loss, src)

Other info / logs
the output log may display failed at
2020-09-07 14:07:25.563878: F tensorflow/core/kernels/cuda_solvers.cc:120] Check failed: cublasCreate(&cublas_handle) == CUBLAS_STATUS_SUCCESS Failed to create cuBlas instance.
log.txt

This is probably your cuda error. Can you paste the detailed log?
https://colab.research.google.com/drive/1x70ApzFL01APODQxlcnvVPIJJVUQR3DI?usp=sharing

may be, i think it is a tensorflow issue before, bug when is replace the code about image.transform, the problem is gone, so i come here for help

What's your TensorFlow version btw? Try to print tf.__version__.

sorry, i did not check the provided code carefully, i run the above code on the Ubuntu, there is no error! but i can confirm the problem exist because my origin code still product error and can not continue, but when i remove the line about image.transform, it can train normally.
my tensorflow version is 2.3.0

It still seems not an addons' issue. Can you verify if the cublas install correctly? Maybe follow the link down below. Thanks!
https://stackoverflow.com/questions/52337791/verify-that-cublas-is-installed

the cublas is installed, but the cublas.h  location is different from the link, i found it in another system location
my arch machine use cuda 11.0, gtx 1660, the ubuntu use cuda 10.2, rtx2080

i checked the implement of image.transform, it is an tensorflow api wrapper.
my code can run ok with tensorflow 2.2 and addons v0.10.1,  i noticed that the old implement use addons own c++ kernel, and the tensorflow's implement seem's only used for some keras preprocessing module which may not require gradient

Oh I see, have you tried to install addons from source? I guess you might use different cuda version for tensorflow and tensorflow-addons. A proper version should be pip install tf-nightly (this is compatible with cuda 11.0) and tfa from source with specifying
TF_CUDA_VERSION="11.0"
TF_CUDNN_VERSION="YOUR_CUDNN_VERSION"

the tensorflow and addons both installed from source

i checked the implement of image.transform, it is an tensorflow api wrapper.
my code can run ok with tensorflow 2.2 and addons v0.10.1, i noticed that the old implement use addons own c++ kernel, and the tensorflow's implement seem's only used for some keras preprocessing module which may not require gradient

Nope, tensorflow also invokes underlying ImageProjectiveTransform c++ kernel too.

Can you try tensorflow==2.3.0 with tfa-nightly? (maybe in the virtualenv so it won't break your package management).

i just checked it out, but my driver version does not work with the default pip repo,  does the tfa-nightly is the latest master branch, i just build it from source, but the problem still exist

I just modified the TensorFlow code to get the explicit err code, what the cusolverDnCreate(&cusolver_dn_handle) return is 7

Is http://www.jcuda.org/jcuda/jcusolver/doc/jcuda/jcusolver/cusolverStatus.html#CUSOLVER_STATUS_INTERNAL_ERROR

To correct: check that the hardware, an appropriate version of the driver, and the cuSolver library are correctly installed.

the return code 7 is an impossible status for cusolverDnCreate (https://docs.nvidia.com/cuda/cusolver/index.html#cuSolverDNcreate), there may be some stack broken, and seems not addons bug, so i will not bother you any more


Add option for marking bookmarks as unread by default

Fixes https://github.com/sissbruecker/linkding/issues/669
This feature adds an option to the user profile to set the default state for Mark as unread.

The migration does not update the current default, therefore there is no migration impact.
I chose to make the field Mark as unread default, rather than a Mark as read default, this is so that it mirror the existing form. e.g if its checked in the setting it will be checked on the bookmarks form.

This is my first proper contribution to this project, so apologies if I have missed anything. I picked up this feature as it seemed like an easy one to implement.

Thanks!


Fix Amino MsgExec for x/gov

Closes: #XXX
What is the purpose of the change

Add a description of the overall background and high-level changes that this PR introduces

(E.g.: This pull request improves documentation of area A by adding ....
Brief Changelog
(for example:)

The metadata is stored in the blob store on job creation time as a persistent artifact
Deployments RPC transmits only the blob storage reference
Daemons retrieve the RPC data from the blob cache

Testing and Verifying
(Please pick one of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added unit test that validates ...
Added integration tests for end-to-end deployment with ...
Extended integration test for ...
Manually verified the change by ...

Documentation and Release Note

Does this pull request introduce a new feature or user-facing behavior changes? (yes / no)
Is a relevant changelog entry added to the Unreleased section in CHANGELOG.md? (yes / no)
How is the feature or change documented? (not applicable   /   specification (x/<module>/spec/)  /  Osmosis docs repo   /   not documented)

@tombeynon

Any chance this could be included in a release soon? It would be great to re-enable full Ledger/amino authz support for Osmosis in REStake.app 🙏🏻

??? @tombeynon

We would need answer on this: https://github.com/osmosis-labs/cosmos-sdk/pull/342#pullrequestreview-1137920504 to push this forward

We would need answer on this: #342 (review) to push this forward

Oh, IDK, I'm just applying the fix from the upstream SDK.

@tombeynon I've tried 🤷♂


Updated versions of qaac, ffmpeg, and LAME

The updated file is work in progress and can change. It does not impact any functionality currently and work is not finished. The work progress is monitored here: https://github.com/wieslawsoltes/BatchEncoder/issues/82
The file that should be updated:

https://github.com/wieslawsoltes/BatchEncoder/blob/master/scripts/download.ps1
https://github.com/wieslawsoltes/BatchEncoder/blob/master/README.md#supported-formats-and-tools

Also make sure you test tool and it does work with current progress functions: https://github.com/wieslawsoltes/BatchEncoder/tree/master/progress

@Metaphorce812 Thanks for PR, I have made several changes to tools file to there have been merge conflicts. I have pushed your changes to master branch manually.


chore(master): release git-remote-get 0.3.0

:robot: I have created a release beep boop
0.3.0 (2024-03-14)
Features

add token flag for passing github pat (b8d0b0d)

Bug Fixes

can download binary files (f5dd2ad)
ref option is now on HEAD (10d12c1)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/01Joseph-Hwang10/git-remote-get/releases/tag/git-remote-get-v0.3.0 :sunflower:


Clean a bit and go with typescript

Hi, I wanted to see how this project was implemented and ended up with converting the code to typescript and some minor things. The implementation of how the code works has not been touched, it should work all the same.
This PR doesn't bring any important change but since I put some effort in it I should make a PR.
The resulting code after compilation is pretty much the same, the class is converted to function and prototype as the original code.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.