[CI-8238], [CI-8239] Small CI doc updates related to Windows

CI-8238: Local runner install steps for Windows must use PowerShell to install the Drone Runner. Updated the self-signed cert command. Fix capitalization of "PowerShell".
CI-8239: Describe troubleshooting for certificate signed by unknown authority error with Upload Artifact to JFrog Artifactory step.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


Fix #17 : ADC related functions

Created PSLAB_ADC.c and PSLAB_ADC.h files with functions extracted from functions.c

Thanks alot @jithinbp and @mariobehling ! :blush:


⚠ GitLab Server has degraded performance

In bff2183, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 11030 ms

Resolved: GitLab Server performance has improved in 81201d6.


]Protos v2 in v3  testing

TESTING: please ignore

For an explanation of how to fill out the fields, please see the relevant section
in PULL_REQUESTS.md
Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Deprecated:]
[Optional API Considerations:]

testing arbitrary change to api to ensure readding protos has worked correctly and proto format is happy


Killed 9: with custom dataset

Describe the bug
I have a network with

adjacency matrix of shape (X,X) 3 gb approx
feature matrix of shape (X,Y) 38 mb
binary classes

I am loading the data into StellarGraph using
    def conv2list(adj_m):
        """
        converts adjacency matrix to adj list to load into stellargraph
        """
        idx = np.triu_indices(n=adj_m.shape[0])
        v = adj_m[idx].reshape(-1, 1)
        col = idx[0].reshape(-1, 1)
        row = idx[1].reshape(-1, 1)
        final = np.concatenate((row, col, v), axis=1)
        d = pd.DataFrame(final)
        d.columns = ['source', 'target', 'weight']
        return d

     def get_data(path):
        df = pd.read_csv(path, sep="\t")
        df.fillna(0, inplace=True)
        Y = df['class'] + df['class_x'] + df['class_y']
        #  Y[np.where(Y>0)] = 1
        Y.replace(np.min(Y), 0, inplace=True)
        Y.replace(np.max(Y), 1, inplace=True)
        ids = df[['GeneNames', 'Uniprot']]
        X = df.drop(['class', 'GeneNames', 'Uniprot', 'class_x', 'class_y'], axis=1).values
        return X

X = get_data('df_sigm.txt')

A = np.load('adj_str.npy')

y = pd.read_csv('classes.txt', sep="\t")['0']
train_subjects, test_subjects = model_selection.train_test_split(
    y, test_size=0.2, stratify=y
)
val_subjects, test_subjects = model_selection.train_test_split(
    test_subjects, test_size=0.3, stratify=test_subjects
)

# this are all np array
# y = OneHotEncoder().fit(y.reshape(-1,1)).transform(y.reshape(-1,1)).toarray()
train_targets = train_subjects.values
val_targets = val_subjects.values
test_targets = test_subjects.values

all_targets = y.values

G = StellarGraph(X, edges=conv2list(A))
G.info()
StellarGraph: Undirected multigraph
Nodes: 20379, Edges: 207662010

Node types:
  default: [20379]
    Features: float64 vector, length 128
    Edge types: default-default->default

Edge types:
  default-default->default: [207662010]
     Weights: range=[0, 1], mean=0.0263249, std=0.1601
     Features: none

But then when I run
generator = FullBatchNodeGenerator(G, method="gat", sparse=False)
train_gen = generator.flow(train_subjects.index, train_targets)

gat = GAT(
    layer_sizes=[8, 1],
    attn_heads=8,
    generator=generator,
    bias=True,
    in_dropout=0.3,
    attn_dropout=0.3,
    activations=["elu", "sigmoid"],
    normalize=None,
    saliency_map_support=True,
)

x_inp, predictions = gat.in_out_tensors()

model = Model(inputs=x_inp, outputs=predictions)
model.compile(
    optimizer=optimizers.Adam(lr=0.005),
    loss=losses.binary_crossentropy,
    weighted_metrics=["acc"],
)

val_gen = generator.flow(val_subjects.index, val_targets)
N = G.number_of_nodes()
history = model.fit(
    train_gen, validation_data=val_gen, shuffle=False, epochs=10, verbose=1
)

Killed: 9 at first epoch
I have 32 gb of memory and can load larger networks/train on exactly the same network  in other GNN frameworks. Is there something that I am missing like loading the data in another way?  The goal would be to obtain saliency maps for each node.

Thanks for including such detail in your report!
Unfortunately, I suspect this is caused by the saliency map implementation requiring dense matrices (as hinted by the sparse=False argument to FullBatchNodeGenerator). In particular, the key piece enabled by saliency_map_support=True does some heavy weight manipulations on dense matrices at the moment:
https://github.com/stellargraph/stellargraph/blob/ec132647e5cf43ff683e3f2e72e18ac6daa98202/stellargraph/layer/graph_attention.py#L331-L341
From a quick look, it looks like that code is potentially holding many dense N x N matrices. I suspect that code was written as a direct translation of a paper, and little thought was given to performance, given there's various things that could be factored out, to reduce the (source-level) instances, something like:
exp = K.exp(dense - K.max(dense, axis=1, keepdims=True))
W = exp * (
    A * (self.delta - 2 * self.non_exist_edge * self.delta + self.non_exist_edge) +
    self.non_exist_edge * (self.delta * tf.ones((N, N)) + tf.eye(N))
)
dense = W / K.sum(W, axis=1, keepdims=True)

(I haven't verified that's a correct refactoring, so it'll definitely need double checking.)
One way to apply this right now without needing to do a pull request would be to copy the whole graph_attention.py file and adjust those lines, as well as replacing from ..mapper with from stellargraph.mapper import ... and from.misc import ... with from stellargraph.layer.misc import ....

Thanks for including such detail in your report!
Unfortunately, I suspect this is caused by the saliency map implementation requiring dense matrices (as hinted by the sparse=False argument to FullBatchNodeGenerator). In particular, the key piece enabled by saliency_map_support=True does some heavy weight manipulations on dense matrices at the moment:
https://github.com/stellargraph/stellargraph/blob/ec132647e5cf43ff683e3f2e72e18ac6daa98202/stellargraph/layer/graph_attention.py#L331-L341
From a quick look, it looks like that code is potentially holding many dense N x N matrices. I suspect that code was written as a direct translation of a paper, and little thought was given to performance, given there's various things that could be factored out, to reduce the (source-level) instances, something like:
exp = K.exp(dense - K.max(dense, axis=1, keepdims=True))
W = exp * (
    A * (self.delta - 2 * self.non_exist_edge * self.delta + self.non_exist_edge) +
    self.non_exist_edge * (self.delta * tf.ones((N, N)) + tf.eye(N))
)
dense = W / K.sum(W, axis=1, keepdims=True)

(I haven't verified that's a correct refactoring, so it'll definitely need double checking.)
One way to apply this right now without needing to do a pull request would be to copy the whole graph_attention.py file and adjust those lines, as well as replacing from ..mapper with from stellargraph.mapper import ... and from.misc import ... with from stellargraph.layer.misc import ....

Thanks for the quick answer, will try to do local import of graph attention and see if it works. will post here on the outcome and do a pull request in case needed.

Thanks for the quick answer, will try to do local import of graph attention and see if it works. will post here on the outcome and do a pull request in case needed.

Thanks for the quick answer, but still does not work. Is there any way to import the adjacency matrix without having to specificy empty edges? Might be more memory efficient if I can throw in a numpy array with only source and target for node that actually exists

Thanks for the quick answer, but still does not work. Is there any way to import the adjacency matrix without having to specificy empty edges? Might be more memory efficient if I can throw in a numpy array with only source and target for node that actually exists

Unfortunately no, not for saliency maps: saliency maps only work with sparse=False specified to FullBatchNodeGenerator, which forces it to use a full NxN dense matrix. Training the model without saliency map support can use sparse=True (which is also the default), which uses a sparse adjacency matrix along the lines of what you're hoping for.

Unfortunately no, not for saliency maps: saliency maps only work with sparse=False specified to FullBatchNodeGenerator, which forces it to use a full NxN dense matrix. Training the model without saliency map support can use sparse=True (which is also the default), which uses a sparse adjacency matrix along the lines of what you're hoping for.

Hi,  A suggestion I would have is to use GCN saliency which supports sparse matrices – this would be a good start particularly as GAT saliency is experimental.
Alternatively, if using GAT is important, you could try training on the full dataset with sparse=True, save the trained weights, and then create a new GAT model on a small sub-graph containing the nodes that you are specifically interested in, and finally loading the trained weights into this new model and calculating the saliency map using this new dense model on the sub-graph of interest.  This should give the same results in the sub-graph as long as nodes k-hops away from the target node(s) where the saliency is required are included in the sub-graph (where k is the depth of the GAT layer).
If model is the full sparse GAT model (with saliency_map_support=False), and model2 is the dense GAT model with saliency_map_support=True then the weights can be transferred as follows:
model_weights = model.get_weights()
model2.set_weights(model_weights)

I hope this helps!

Hi,  A suggestion I would have is to use GCN saliency which supports sparse matrices – this would be a good start particularly as GAT saliency is experimental.
Alternatively, if using GAT is important, you could try training on the full dataset with sparse=True, save the trained weights, and then create a new GAT model on a small sub-graph containing the nodes that you are specifically interested in, and finally loading the trained weights into this new model and calculating the saliency map using this new dense model on the sub-graph of interest.  This should give the same results in the sub-graph as long as nodes k-hops away from the target node(s) where the saliency is required are included in the sub-graph (where k is the depth of the GAT layer).
If model is the full sparse GAT model (with saliency_map_support=False), and model2 is the dense GAT model with saliency_map_support=True then the weights can be transferred as follows:
model_weights = model.get_weights()
model2.set_weights(model_weights)

I hope this helps!

the solution with pulling the weights out worked like a charm, thanks!

the solution with pulling the weights out worked like a charm, thanks!


Customizable directory history save filter

There should be a directory name regex filter in Elvish that filters if a directory should be saved into the location history.
Example use case: don't pollute the location history with directories in Linux /proc, so add this regex: ^/proc.
It should be a list that contains regexes, allowing more flexible regex adding.

Currently there is edit:loc-hidden=[''] but I can't quite put my finger on any Regex

I currently use a temporary workaround using edit:loc-hidden, but it only hides the items.
My idea is that Elvish wouldn't save it in the db.
A few advantages of it:

don't change the weight of other directories if an item isn't saved.
easier to write Elvish script that uses directory history, if it don't need to filter unnecessary elements.
scripts also works faster with a clean directory history.

Note that edit:loc-hidden is now edit:location-hidden (it was renamed by commit 032d047d on 2018-02-08).
Given that this feature request is now 4.5 years old I wonder whether it is worth implementing. A google search of elvish edit:loc-hidden and elvish edit:location-hidden returned only this document: https://gist.github.com/notramo/9c4d579d4faf54ca5c31661fae54891a. Which suggests that there are effectively zero uses of the edit:loc-hidden (or edit:location-hidden) feature.
It seems like the behavior requested by this feature makes more sense than the current edit:location:hidden variable. However, what does it mean to set a hypothetical edit:exclude-location variable? Should that scrub the history of locations matching the patterns in that variable? Or should it only exclude adding matching directories to the location history? If the former when, exactly, should that scrubbing of history occur?


Feature request: implement search API

It would be great to be able to search datasets for a given string from the Python API (should be supported by the native API, right?)

The search API is technically distinct (see http://guides.dataverse.org/en/latest/api/search.html).
I haven't implemented it because I haven't needed it for any of our use cases on the OSF, but I think this would make a great addition to the client.

@rliebz me too. I'm guessing that @leeper is considering implementing search in the R client based on this issue he opened: https://github.com/IQSS/dataverse/issues/2558 . There are some details in that ticket that might be of interest to anyone who wants to work on this.


How to reproduce the result for SciERC in the paper?

Thanks for your amazing work!
I do the data-preprocess and train as the guide in the Readme.md
I see the code set the seed for random、torch and np.
I train the model with the SciERC dataset and early stop at epoch 229 , get the result:

I train it with a RTX3090 GPU without any modify the code (same as the Readme.md)
I see, in the paper, the result is:

the F1 for the ent is 68.4 and i get 66.03
How to reproduce the result in the paper?
Sincerely looking forward to your reply!

It is confusing that the second figure shows the entity F1 score is 69.67 rather than 66.03.
As mentioned in the paper, all experiments are conducted on the Xeon(R) W-3175X CPU and Quadro RTX 8000 GPU.
To explore the impact of different machine conﬁguration, we retrain our model on the Tesla-V100-SXM2-32GB, the entity F1 is 67.86, the exact relation F1 is 35.77, which is indeed inferior to the reported result.

We recommend minor hyperparameter changes in different machine conﬁguration.
For example,tring different  random seed, more training epochs, different early stopping strategy.
In addition, you can also try to change the batch size from 32 to 16 or 64.
If there are further questions about reproducing the results, please feel free to discuss with us.

Really Thanks to your apply.
Sorry..I screenshot the result uncorrectly...the 69.67 is the last valid, the real test score is :

So the answer for why the score is lower than that the paper said is the different GPU and CPU?
I will do some experiment on the my 3090....
So if i use different GPU and modify some hyperparameter , maybe it can improve the score? the hyperparameter and score should be different from different machine?
Sincerely looking forward for your reply~!

The results on different GPU and CPU shows that different machine conﬁgurations do influence the final performance.
It is very possible that minor hyperparameter changes will lead to better results.
Note that just modifying few training hyperparameters, such as random seed, number of epochs, and batch size.
If there are further questions about reproducing the results, please feel free to discuss with us.

where is the file 'train.json'?


SQLA - fix column names error for export and details view

The SQLA backend has some special logic for determining column names for relations. But, that logic wasn't getting applied to the list of columns in the export and details view. It's what's causing tests to fail on @xqliu in: https://github.com/flask-admin/flask-admin/issues/1263
This pull request fixes the issue, and I was also able to refactor duplicate code in get_list_columns, get_details_columns, and get_export_columns into the new get_column_names.
This changes some behavior in two edge cases:

If column_list, column_export_list, or column_details_list evaluate to false (instead of just None), flask-admin will get columns from the model (scaffold_list_columns). I'm not sure why anyone would want to use an empty list for these.
Columns in column_exclude_list, column_details_exclude_list, or column_export_exclude_list will never be shown on their respective views. Before, these were only excluded if column_list, column_export_list, or column_details_list were None. I'm not sure why anyone would have the same column in both the exclude_list and include list.

@mrjoes have time to review this one?
Users will see errors like Neither 'InstrumentedAttribute' object nor 'Comparator' object associated with Model1.test1 has an attribute 'replace' when they try to use export or details views with SQLA relations until this is fixed.


[BlockPair] Tiny PR that adds some comments and Assert to the BlockPair

Added xmldoc for BlockPair and an assert that ensures that chained block was created from the block provided.

ok i've run the tests just to be sure


fix: adjust package name

one more fix as publishing to NPM failed cause of mismatch between package name and repo address

@GreenRover 1.0.0 was released as artificial release I created to prevent it was created without v prefix. Is this a problem for you? are you somehow radical in opinion about releasing major releases?
from my point of view it is not a problem 1.0 is released and that 2.0 will have to be released in a week or two because of new parser API. But if you have serious issues with that, I can revert and remove 1.0 from npm

@GreenRover nevermind, npm do not allow to remove releases after few hours

Sorry missed the second last message. No its just eye candy. Will start adopting to 2.0 today.


[WIP] 2018 cleanup

Part 2
Add

[ ] #180
[ ] Manifests e.g. https://news.google.com/_/NewsUi/manifest.json
[ ] "Browse" section or ProTips
[ ] ooni probes

Remove

[ ] Dead links (TBD)

Prepare

[x] Choose dataset of the month for April

Part 1
Add

[x] Other cryptocurrencies
[x] USA population since 1960
[x] Dataset of the month?

Remove

[x] Cars (Broken JSON)
[x] Browse links e.g. https://data.michigan.gov/browse
[x] Useless Government datasets (Tariff Rates, Business Service Providers, etc)

@Mandihamza possible OSF assignment


ipam: fix crd mode

Fix regression affecting IPAM CRD mode introduced in #15160.
In buildAllocationResult an "ENI" error was wrongly constructed
in fallthrough case affecting all modes not specifically handled
within the switch statement.
Fixes: #16492
Signed-off-by: Jussi Maki<EMAIL_ADDRESS>

test-me-please

How did we miss this in CI??

By the virtue of not having tests for this particular IPAM mode. That really should be addressed.

Tested manually in minikube with: cilium install --ipam crd --agent-image quay.io/cilium/cilium-ci:75d4e37b370f9ee80a786ef6e23b4237279dd0d5 --operator-image quay.io/cilium/operator-generic-ci:75d4e37b370f9ee80a786ef6e23b4237279dd0d5 --version latest and apiVersion: "cilium.io/v2" kind: CiliumNode metadata:   name: "minikube" spec:   ipam:     pool:       <IP_ADDRESS>: {}       <IP_ADDRESS>: {}       <IP_ADDRESS>: {}       <IP_ADDRESS>: {}.

How did we miss this in CI??

By the virtue of not having tests for this particular IPAM mode. That really should be addressed.

Arf! We should track this with an issue.

How did we miss this in CI??

By the virtue of not having tests for this particular IPAM mode. That really should be addressed.

Arf! We should track this with an issue.

Created a placeholder issue: https://github.com/cilium/cilium/issues/16496

test-1.19-5.4

test-1.19-5.4

Marked ready to merge since relevant tests for this pass and this passed manual test, but feel free to disagree and pull the label and wait for provisioning issues to be solved.


fixes register_devices action bug

team_id is retrieved from params and not from platform
I had this error using the register_devices action:
"NameError: undefined local variable or method `platform' for Fastlane::Actions::RegisterDevicesAction:Class"
I think the problem is that the parameter is being retrieved with platform instead of params.
I didn't found the tests for this action and had no way to test it

Thanks @tiagomartinho, and sorry for introducing this bug


Set SingleDomainLoaderOptimization to false for AutoMLService

The issue #818 seems to be caused by a CLR bug related to App Domains, where servicehub reuses App Domain for perf reason. One of a workround is to simply close LoaderOptimization.MultiDomain in servicehub config file.
See the example below about how to close that option
https://devdiv.visualstudio.com/DevDiv/_git/VSUnitTesting?path=%2Fsrc%2FTestWindow%2FSetup%2FTestDiscoveryListener.servicehub.service.json&version=GBmaster&_a=contents

@LittleLittleCloud I cannot access the link of how to close the option, I get 401 unauthorized

@LittleLittleCloud I cannot access the link of how to close the option, I get 401 unauthorized

The fix is on ModelBuilder side, I'm working on a fix, and once it's done, I will put a link here and you can download and install.

thanks for the explanation, looking forward to trying it out!

https://test1storageafyok6j49.blob.core.windows.net/grantsetfix/Microsoft.ML.ModelBuilder.Gallery.vsix

The fix allowed training to proceed for me. Thank you!
However, it does seem like training is taking significantly longer that it was before. Maybe this is unrelated, and I haven't done a lot of runs yet but though it worth mentioning.

The fix allowed training to proceed for me. Thank you!
However, it does seem like training is taking significantly longer that it was before. Maybe this is unrelated, and I haven't done a lot of runs yet but though it worth mentioning.

Do you mean the gap between you click on training and the result of first iteration comes out?

Yes, there is definitely a increase in time in that stage. The Model Builder recommends 10 seconds for the training period (for smaller data sets) but the first model build doesn't get out for anywhere from 15 to 140+ seconds. As an example, I took a 2 MB data set and it recommended 10 seconds, in which time it could not train any mode. I increased the limit to 100 seconds and it took 13.3 seconds for AveragedPerceptronOva and 21.6 seconds for SdcaMaximumEntropyMulti and stopped. I don't have much historical data on build times before the hotfix was applied, but it seemed odd that no models can be built in the "recommended" time to train now.

Hmmmm, Thanks for the update. We were aware that one of the drawbacks for disabling multi domain optimization is perf, but I don't know the perf loss will be that huge. We will keep looking into to see if there's another solution

I seem to be getting a similar issue. In the autoML Log:
06/28/2020 19:49:36 GMT Standard Time : Error : Error creating Microsoft.ML.ModelBuilder.AutoMLService.AutoMLService instance of CLR service module 'MicrosoftMLModelBuilderAutoML': System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. HResult='-2146232828'  ... ===InnerException=== System.IO.FileLoadException: Loading this assembly would produce a different grant set from other instances. (Exception from HRESULT: 0x80131401) HResult='-2146233343'
Updating with the VIX above gives me a different error. Runtime exception:
2020-06-28 20:12:25.0912 DEBUG Training failed with the exception:    System.InvalidOperationException: Splitter/consolidator worker encountered exception while consuming source data --->      System.InvalidOperationException: Splitter/consolidator worker encountered exception while consuming source data --->        System.FormatException: Parsing failed with an exception: Could not parse value unknown in line 24875, column Plugin --->          System.InvalidOperationException: Could not parse value unknown in line 24875, column Plugin    at Microsoft.ML.Data.TextLoader.Parser.ProcessOne(FieldSet vs, ColInfo info, ColumnPipe v, Int32 irow, Int64 line) ...

I seem to be getting a similar issue. In the autoML Log:
06/28/2020 19:49:36 GMT Standard Time : Error : Error creating Microsoft.ML.ModelBuilder.AutoMLService.AutoMLService instance of CLR service module 'MicrosoftMLModelBuilderAutoML': System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. HResult='-2146232828' ... ===InnerException=== System.IO.FileLoadException: Loading this assembly would produce a different grant set from other instances. (Exception from HRESULT: 0x80131401) HResult='-2146233343'
Updating with the VIX above gives me a different error. Runtime exception:
2020-06-28 20:12:25.0912 DEBUG Training failed with the exception: System.InvalidOperationException: Splitter/consolidator worker encountered exception while consuming source data ---> System.InvalidOperationException: Splitter/consolidator worker encountered exception while consuming source data ---> System.FormatException: Parsing failed with an exception: Could not parse value unknown in line 24875, column Plugin ---> System.InvalidOperationException: Could not parse value unknown in line 24875, column Plugin at Microsoft.ML.Data.TextLoader.Parser.ProcessOne(FieldSet vs, ColInfo info, ColumnPipe v, Int32 irow, Int64 line) ...

Hi @W1zb1t
it seems to be a different dataset issue, can you create a new issue and share us with the dataset you have. Thanks

I tried this fix and was able to continue training
https://test1storageafyok6j49.blob.core.windows.net/grantsetfix/Microsoft.ML.ModelBuilder.Gallery.vsix

happy to test the fix

Fix here worked for me

Can someone update the link with the fix please?


chore(main): release 0.1.28

:robot: I have created a release beep boop
0.1.28 (2023-08-14)
Bug Fixes

Pipelines: set timeout when uploading a version (#72) (7703794)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/BLSQ/openhexa-sdk-python/releases/tag/0.1.28 :sunflower:


1345100   update content

Document updated

Docs Build status updates of commit 6129f47:
:clock10: Pending: waiting for processors (21 builds ahead of you)
:warning: Docs Build is busy, currently there are 21 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 6129f47:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/concepts/deploy-and-publish/appsource/prepare/app-manifest-checklist.md
:warning:Warning
View
Details

msteams-platform/concepts/deploy-and-publish/appsource/prepare/frequently-failed-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/deploy-and-publish/appsource/publish.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/deploy-and-publish/appsource/prepare/app-manifest-checklist.md

Line 26, Column 16: [Warning-file-not-found] Invalid file link<EMAIL_ADDRESS>
For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Thank you @Mahesh2516!


Add AUTHORS file

@akheron, @Kamirus, @rightfold I want to add AUTHORS file with contributors (in an alphabetical order) before the next release.
Do you have anything against listening you there?
If you want I can put your full name there too. Just please let me know.

Seems fine to me
Sent from my iPhone.

Op 6 dec. 2018 om 20:26 heeft paluh<EMAIL_ADDRESS>het volgende geschreven:
@akheron, @Kamirus, @rightfold I want to add AUTHORS file with contributors (in an alphabetical order) before the next release.
Do you have anything against listening you there?
If you want I can put your full name there. Just please let me know.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Cool!


*: update several deps

What problem does this PR solve?
Problem Summary:
to resolve:

RUSTSEC-2021-0072
RUSTSEC-2021-0078
RUSTSEC-2021-0079
CVE-2021-32810

Check List
Tests

Unit test
Integration test

Release note
None

/merge


Failed to build --with-oracle with existing instantclient install?

Hi, I ran:
brew install --with-oracle --with-odbc  usql

and it failed with the following output stating that oci8 is not on the pkg-config path.
==> Installing usql from xo/xo
==> Downloading https://github.com/xo/usql/archive/v0.6.0.tar.gz
Already downloaded: /Users/ruthb/Library/Caches/Homebrew/usql-0.6.0.tar.gz
==> dep ensure --vendor-only
==> go build -tags most fts5 vtable json1 no_adodb oracle odbc -ldflags -s -w -X
Last 15 lines from /Users/ruthb/Library/Logs/Homebrew/usql/02.go:
most fts5 vtable json1 no_adodb oracle odbc
-ldflags
-s -w -X github.com/xo/usql/text.CommandVersion=v0.6.0
-o
/usr/local/Cellar/usql/0.6.0/bin/usql

# /usr/local/opt/pkg-config/bin/pkg-config --cflags oci8
Package oci8 was not found in the pkg-config search path.
Perhaps you should add the directory containing `oci8.pc'
to the PKG_CONFIG_PATH environment variable
No package 'oci8' found
/usr/local/opt/pkg-config/bin/pkg-config: exit status 1
# github.com/xo/usql/vendor/github.com/alexbrainman/odbc/api
ld: warning: directory not found for option '-L/opt/local/lib'
ld: warning: directory not found for option '-L/opt/local/lib'

If reporting this issue please do so at (not Homebrew/brew or Homebrew/core):
https://github.com/xo/homebrew-xo/issues

/usr/local/Homebrew/Library/Homebrew/exceptions.rb:426:in `block in dump': undefined method `check_for_bad_install_name_tool' for #<Homebrew::Diagnostic::Checks:0x00000103059368> (NoMethodError)
Did you mean?  check_for_tap_ruby_files_locations
	from /usr/local/Homebrew/Library/Homebrew/exceptions.rb:425:in `each'
	from /usr/local/Homebrew/Library/Homebrew/exceptions.rb:425:in `dump'
	from /usr/local/Homebrew/Library/Homebrew/brew.rb:138:in `rescue in <main>'
	from /usr/local/Homebrew/Library/Homebrew/brew.rb:30:in `<main>'

However, it is:
$ /usr/local/opt/pkg-config/bin/pkg-config --cflags oci8
-I/usr/local/lib/instantclient_11_2/sdk/include/

I totally missed the brew tap xo/xo and explicit install of the packaged instantclient-sdk. Apologies for that. I was able to install successfully. I just told brew to overwrite my existing files with the new symlinks. usql built properly after that. Thanks!


Multiplexed data

Here is a dataset with multiplexed data.
Only one read aligns to the current reference file but it seems to run just fine.

Can we get away with having two test-datasets? i.e. with and without multiplexed data?
Would be nice to test both if possible.

Going to merge this so I can play with the test profiles.


Remove: chrisant996.Clink version <IP_ADDRESS>658e

Reason for removal: This version is older than what has been set in max-versions-to-keep by the publisher.
Pull request has been automatically created using 🛫 WinGet Releaser.
Microsoft Reviewers: Open in CodeFlow

@wingetbot run


Note about onMouseEnter vs onMouseOver in docs

Everytime I need hover stuff, I can't decide between Html.Events.onMouseEnter and onMouseOver. Then I google "onmouseover vs onmouseenter" and find this StackOverflow answer.
It says I should use onMouseOver/Out, because onMouseEnter/Leave are IE-only.
If you agree with that assessment, it would be helpful for the docs to differentiate the ones that should be used from the ones that are IE legacy.

That comment is from 2009, and the subcomment claims that they work in browsers as of 2013.
Can you find more recent information on this?

Ah, didn't look at the metadata. I will try to find a current and authoritative source on the differences and recommendations.

So, Mozilla docs:

mouseover
mouseenter

mouseover bubbles, mouseenter doesn't bubble. That means mouseenter fires only for the topmost element, mouseover for the element and all its parents.
Usable scenarios seem to be either
a) to use mouseenter, or
b) to use mouseover with stopPropagation = True.

Otherwise, mouseover with default behaviour seems clumsy.

Here's the Ellie playground.
https://ellie-app.com/qPWtPP4f9fa1
It seems a bit more research could go into describing what usecase is each of those good for. The original premise of this issue has been debunked, but maybe we still can make the docs better :)

Makes sense! If you have suggestions for the docs based on it, let's do it in a new issue.
I have trouble evaluating changes when things start to get out of the initial comment.


[FEAT]: Add option to have LLM rephrase user question before querying vector store

What would you like to see?
When an LLM rephrases a user’s question, it often leads to better vector matches. Please add a setting to make this an option, including a prompt template. I guess maybe it’d be good to search by BOTH the user’s initial request AND the LLM’s rephrased question. This would be relatively easy to put in, but it might slow down initial response time for some, if only slightly.
Can you do the same with hallucination detection and mitigation. Again. User would encounter a perceived performance hit if they weren’t aware of what was going on underneath.
Would be a trade off of performance and utility.

There are far faster ways to improve retrieval and accuracy over doing this. You would be surprised, but doing this would be quite high latency and result in minimal gains. Eventually, what ends up happening is you have re-built a Reranking model (https://github.com/Mintplex-Labs/anything-llm/issues/1124) because that is what those solve and is the logical conclusion of following this path!
Improvements we will add that can be done far prior to resorting to this:

Include sources from previous chats in history
Knowledge Graphs (https://github.com/Mintplex-Labs/anything-llm/tree/knowledge-graph-support)
Reranker support

All behind what you mentioned!
On Sun, May 19, 2024 at 1:40 PM Timothy Carambat @.***>
wrote:

There are far faster ways to improve retrieval and accuracy over doing
this. You would be surprised, but doing this would be quite high latency
and result in minimal gains. Eventually, what ends up happening is you have
re-built a Reranking model (#1124
https://github.com/Mintplex-Labs/anything-llm/issues/1124) because that
is what those solve and is the logical conclusion of following this path!
Improvements we will add that can be done far prior to resorting to this:

Include sources from previous chats in history
Knowledge Graphs (
https://github.com/Mintplex-Labs/anything-llm/tree/knowledge-graph-support
)
Reranker support

—
Reply to this email directly, view it on GitHub
https://github.com/Mintplex-Labs/anything-llm/issues/1455#issuecomment-2119310186,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AF632FJMH5I7PFOPE6CQMADZDDPYJAVCNFSM6AAAAABH6DXLZ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJZGMYTAMJYGY
.
You are receiving this because you authored the thread.Message ID:
@.***>


Support custom resolvers for @nuxt/components

Similar approach to https://github.com/antfu/unplugin-vue-components#importing-from-ui-libraries
I been using this pattern for unplugin-vue-components for a while and I think it turns out a flexible and straightforward solution to support various component libraries without the changes need to be done on the author side. For example, some components might use JSX to build up the library, or uses all named exports on the top-level module, or imports styles separately. Additionally, the resolver opens more possibility to integrate on-demand usages, for example unplugin-icons which the icons are served virtually via module name. This would also be great if we could join the force from the Vite side to provide a uniformed resolver solution and made it easier for ppl adopting to more libraries at ease.

I believe this issue can be closed since we can extend the components dirs as well as the auto-imports. cc @danielroe

Hi. I think supporting custom component resolver makes sense. Extending the components dirs option still doesn't cover the above cases.

@Atinux By supporting resolvers, framework users can just import the resolver and use it instead of copying the dirs from the resolver source code and following their changes. For example, I',m using ElementP lus UI framework with ElementPlusResolver.


flux reconcile on helmrelease leaves erroneously modified object in bad state

Describe the bug
A HelmRelease contains a cronjob as part of a release. If we edit that cronjob in k8s and then run flux reconcile -n <namespace> helmrelease <hr name> --with-source, the edited cronjob is not replaced with the correct cronjob.
To Reproduce
Steps to reproduce the behavior:

HelmRelease is READY, and helm shows STATUS as deployed

$ kubectl get hr
NAME             READY   STATUS                             AGE
blerg           True    Release reconciliation succeeded   9d
$ helm ls
NAME          	NAMESPACE	REVISION	UPDATED                                	STATUS  	CHART               	APP VERSION
blerg        	prod     	224     	2021-05-14 19:30:24.051846927 +0000 UTC	deployed	blerg-0.2.0        	1.0

I can see my cronjob spec in the cluster, it is exactly what helm says it should be

$ kubectl get cronjob myjob -o yaml
...
spec:
  containers:
  - args:
    - /bin/bash
    - /app/scripts/run
    ...
###
$ helm get all blerg > manifests.yaml
# grep for CronJob
...
spec:
  containers:
  - args:
    - /bin/bash
    - /app/scripts/run
    ...

Manually edit the cronjob, adding a "command" section to the container spec

$ kubectl edit cronjob myjob
...
spec:
  containers:
  - args:
    - /bin/bash
    - /app/scripts/run
    command:
    - /bin/bash
    - -c
    ...

Reconcile, which should replace the edited job with the correct job

$ flux reconcile -n prod helmrelease blerg --with-source
► annotating GitRepository myrepo in flux-system namespace
✔ GitRepository annotated
◎ waiting for GitRepository reconciliation
✔ GitRepository reconciliation completed
✔ fetched revision master/<sha>
► annotating HelmRelease blerg in prod namespace
✔ HelmRelease annotated
◎ waiting for HelmRelease reconciliation
✔ HelmRelease reconciliation completed
✔ reconciled revision 0.2.0

I can see reconciliation working, the update hooks are running, etc

$ kubectl get hr
NAME             READY     STATUS                             AGE
blerg           Unknown   Reconciliation in progress
...
$ helm ls -a
NAME          	NAMESPACE	REVISION	UPDATED                                	STATUS         	CHART               	APP VERSION
blerg        	prod     	225     	2021-05-14 19:43:50.894886714 +0000 UTC	pending-upgrade	blerg-0.2.0        	1.0

I wait for helm to complete. HelmRelease is READY, and helm shows STATUS as deployed

$ kubectl get hr
NAME             READY   STATUS                             AGE
blerg           True    Release reconciliation succeeded   9d
$ helm ls
NAME          	NAMESPACE	REVISION	UPDATED                                	STATUS  	CHART               	APP VERSION
blerg        	prod     	225     	2021-05-14 19:43:50.894886714 +0000 UTC	deployed	blerg-0.2.0        	1.0

I can now look at the cronjob and see that my modification has remained in place, even though it is not supposed to be there.

$ kubectl get cronjob myjob -o yaml
...
spec:
  containers:
  - args:
    - /bin/bash
    - /app/scripts/run
    command:
    - /bin/bash
    - -c
    ...
###
$ helm get all blerg > manifests.yaml
# grep for CronJob
...
spec:
  containers:
  - args:
    - /bin/bash
    - /app/scripts/run
    # no "command" section
    ...

Expected behavior
The invalid cronjob should have been replaced with helms manifest
Additional context

Kubernetes version:
Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.2", GitCommit:"faecb196815e248d3ecfb03c680a4507229c2a56", GitTreeState:"clean", BuildDate:"2021-01-14T05:14:17Z", GoVersion:"go1.15.6", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"17+", GitVersion:"v1.17.12-eks-7684af", GitCommit:"7684af4ac41370dd109ac13817023cb8063e3d45", GitTreeState:"clean", BuildDate:"2020-10-20T22:57:40Z", GoVersion:"go1.13.15", Compiler:"gc", Platform:"linux/amd64"}
Git provider:
Github

Below please provide the output of the following commands:
flux --version
flux version 0.11.0
flux check
► checking prerequisites
✗ flux 0.11.0 <0.13.4 (new version is available, please upgrade)
✔ kubectl 1.20.2 >=1.18.0-0
✔ Kubernetes 1.17.12-eks-7684af >=1.16.0-0
► checking controllers
✔ helm-controller: deployment ready
► ghcr.io/fluxcd/helm-controller:v0.9.0
✔ kustomize-controller: deployment ready
► ghcr.io/fluxcd/kustomize-controller:v0.10.0
✔ notification-controller: deployment ready
► ghcr.io/fluxcd/notification-controller:v0.11.0
✔ source-controller: deployment ready
► ghcr.io/fluxcd/source-controller:v0.10.0
✔ all checks passed
kubectl -n <namespace> logs deploy/source-controller
{"level":"info","ts":"2021-05-14T19:53:48.826Z","logger":"controller.gitrepository","msg":"Reconciliation finished in 350.449894ms, next run in 1m0s","reconciler group":"source.toolkit.fluxcd.io","reconciler kind":"GitRepository","name":"...","namespace":"..."}
kubectl -n <namespace> logs deploy/kustomize-controller
{"level":"info","ts":"2021-05-14T19:54:37.116Z","logger":"controller.kustomization","msg":"Kustomization applied in 456.616953ms","reconciler group":"kustomize.toolkit.fluxcd.io","reconciler kind":"Kustomization","name":"...","namespace":"...","output":{"<all unchanged>}}
{"level":"info","ts":"2021-05-14T19:54:37.141Z","logger":"controller.kustomization","msg":"Reconciliation finished in 640.896612ms, next run in 3m0s","reconciler group":"kustomize.toolkit.fluxcd.io","reconciler kind":"Kustomization","name":"...","namespace":"...","revision":"master/<sha>"}

I am seeing this as well on flux 0.20 it seems like diffing with helmreleases is broken. It also seems that if I delete a resource manually flux doesn't seem to be picking up that it should put it back and won't until the chart version is modified or the git repo is updated when using reconcileStrategy: Revision.

I am seeing this as well on flux 0.20 it seems like diffing with helmreleases is broken. It also seems that if I delete a resource manually flux doesn't seem to be picking up that it should put it back and won't until the chart version is modified or the git repo is updated when using reconcileStrategy: Revision.

I experience the same with deleted objects from a HelmRelease, lets say an ingress.
If I delete it, it is not recreated on a reconcile.

Same here.
Imho helm-controller should act as "helm upgrade" command as this updates the resources to it's desired state.

If I delete it, it is not recreated on a reconcile.

@zaggash @monotek This is expected behavior. To understand why, you must understand how Helm resolves drifts, (and what obstacles it has placed in its own way with respect to that story)

https://github.com/fluxcd/helm-controller/issues/186

Tl;dr: helm controller doesn't reconcile drift in the cluster, except when it is performing an actual upgrade (and that drift in the cluster wouldn't currently be able to trigger any upgrade, because for Helm Controller it's perfectly indistinguishable from any side-effects that might have been the intended result of any post-render or lifecycle hook behavior in the chart.)
I am not certain if these reports are the same as the original report, but the behavior that both @zaggash and @monotek are describing are already explained by #186 as I'll elaborate further on below. (This is a complicated story, so save yourself and look the other way, unless the tl;dr above has made you hungry to understand what the problem is and why this issue can't easily be resolved.

Helm uses a 3-way merge to incorporate: (1) the old manifest, (2) its live state on the cluster, and (3) the new manifest.
Helm also provides various opportunities for the installing agent to manipulate the state before, around and after install, both within the chart (lifecycle hooks) that are permitted to be non-deterministic (and so may have outputs that are not declaratively formed), and also outside of the chart, with Post Render behavior, that outside of Flux, would also be capable of non-deterministic behavior.
Simplified: The installer can create secrets on the first run (helm install), that won't be generated again during a second run (helm upgrade).
Though Flux makes the postrender behavior declarative, it's still running the Helm code under the hood, which does not assume declarativeness, and that means we can't assume anything that Helm itself would not have assumed or guaranteed.
Every upgrade produces a new release artifact, in the form of a secret of the type: helm.sh/release.v1
So when you have just installed for the first time and you have a handful of Helm charts, your cluster-wide secrets may look like this:
chartmuseum           sh.helm.release.v1.chartmuseum-chartmuseum.v1                  helm.sh/release.v1                    1      4d13h
deis                  sh.helm.release.v1.deis-hephy.v1                               helm.sh/release.v1                    1      4d13h
harbor                sh.helm.release.v1.harbor.v1                                   helm.sh/release.v1                    1      4d13h
ingress-nginx         sh.helm.release.v1.ingress-internal.v1                         helm.sh/release.v1                    1      4d13h
ingress-nginx         sh.helm.release.v1.ingress-public.v1                           helm.sh/release.v1                    1      4d13h
kube-oidc-proxy       sh.helm.release.v1.kube-oidc-proxy.v1                          helm.sh/release.v1                    1      4d11h
minio-lusers          sh.helm.release.v1.minio-lusers-minio.v1                       helm.sh/release.v1                    1      4d13h
minio-stage           sh.helm.release.v1.minio-stage-minio.v1                        helm.sh/release.v1                    1      4d13h
monitoring            sh.helm.release.v1.kube-prometheus-stack.v1                    helm.sh/release.v1                    1      2d22h
monitoring            sh.helm.release.v1.kube-prometheus-stack.v2                    helm.sh/release.v1                    1      2d22h
openvpn               sh.helm.release.v1.openvpn.v1                                  helm.sh/release.v1                    1      4d13h

Three-way diffs are complicated, even more complicated than three-way merges. Now imagine instead of comparing the inputs to the outputs, Helm controller just runs an upgrade each time, producing a new revision and a new versioned secret.
The two secrets shown here for v1 and v2 revisions in the monitoring namespace will quickly fall off the edge, as new release secrets are generated upon each upgrading reconcile, and we've effectively made Helm's rollback feature useless. Helm controller can only infer from the changing state in any inputs, that it should perform an upgrade.

I am virtually certain this does not have anything to do with the original issue, sorry for contributing to the noise, but this is a hard issue to explain, and I'm sure it comes up all the time. Though I am afraid I have not quite understood the cronjob issue that started this thread, doing my best to steer the discussion back on topic and find out if any fix is possible, (or if we might have already fixed it somehow without noticing)


feat: add upload api backend about uploading file to s3 from url directly

Description
Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[ ] 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 not work as expected)
[ ] This change requires a documentation update

We identified new issues on unchanged lines of code. Navigate to the Amazon CodeGuru Reviewer console to view the recommendations to fix them.

need a UI component in WebUI to use the api. Other than that, it's good to go.


Error when building docker container

I have the following error when building the docker container.

Reading package lists...
Building dependency tree...
Reading state information...
build-essential is already the newest version (12.4ubuntu1).
python-rosinstall is already the newest version (0.7.8-1).
python-wstool is already the newest version (0.1.17-1).
python-wstool set to manually installed.
The following additional packages will be installed:
  dbus libpython-all-dev python-all python-all-dev python-crypto python-dbus
  python-gi python-keyring python-keyrings.alt python-pip-whl
  python-secretstorage python-wheel python-xdg
Suggested packages:
  default-dbus-session-bus | dbus-session-bus python-crypto-doc
  python-dbus-dbg python-dbus-doc python-gi-cairo gnome-keyring
  libkf5wallet-bin gir1.2-gnomekeyring-1.0 python-fs python-gdata
  python-keyczar python-secretstorage-doc
The following NEW packages will be installed:
  dbus libpython-all-dev python-all python-all-dev python-crypto python-dbus
  python-gi python-keyring python-keyrings.alt python-pip python-pip-whl
  python-rosinstall-generator python-secretstorage python-wheel python-xdg
0 upgraded, 15 newly installed, 0 to remove and 107 not upgraded.
Need to get 2626 kB of archives.
After this operation, 6315 kB of additional disk space will be used.

(Reading database ... 105310 files and directories currently installed.)
Preparing to unpack .../00-dbus_1.12.2-1ubuntu1.2_amd64.deb ...
Unpacking dbus (1.12.2-1ubuntu1.2) ...
Selecting previously unselected package libpython-all-dev:amd64.
Preparing to unpack .../01-libpython-all-dev_2.7.15~rc1-1_amd64.deb ...
Unpacking libpython-all-dev:amd64 (2.7.15~rc1-1) ...
Selecting previously unselected package python-all.
Preparing to unpack .../02-python-all_2.7.15~rc1-1_amd64.deb ...
Unpacking python-all (2.7.15~rc1-1) ...
Selecting previously unselected package python-all-dev.
Preparing to unpack .../03-python-all-dev_2.7.15~rc1-1_amd64.deb ...
Unpacking python-all-dev (2.7.15~rc1-1) ...
Selecting previously unselected package python-crypto.
Preparing to unpack .../04-python-crypto_2.6.1-8ubuntu2_amd64.deb ...
Unpacking python-crypto (2.6.1-8ubuntu2) ...
Selecting previously unselected package python-dbus.
Preparing to unpack .../05-python-dbus_1.2.6-1_amd64.deb ...
Unpacking python-dbus (1.2.6-1) ...
Selecting previously unselected package python-gi.
Preparing to unpack .../06-python-gi_3.26.1-2ubuntu1_amd64.deb ...
Unpacking python-gi (3.26.1-2ubuntu1) ...
Selecting previously unselected package python-secretstorage.
Preparing to unpack .../07-python-secretstorage_2.3.1-2_all.deb ...
Unpacking python-secretstorage (2.3.1-2) ...
Selecting previously unselected package python-keyring.
Preparing to unpack .../08-python-keyring_10.6.0-1_all.deb ...
Unpacking python-keyring (10.6.0-1) ...
Selecting previously unselected package python-keyrings.alt.
Preparing to unpack .../09-python-keyrings.alt_3.0-1_all.deb ...
Unpacking python-keyrings.alt (3.0-1) ...
Selecting previously unselected package python-pip-whl.
Preparing to unpack .../10-python-pip-whl_9.0.1-2.3~ubuntu<IP_ADDRESS>_all.deb ...
Unpacking python-pip-whl (9.0.1-2.3~ubuntu<IP_ADDRESS>) ...
Selecting previously unselected package python-pip.
Preparing to unpack .../11-python-pip_9.0.1-2.3~ubuntu<IP_ADDRESS>_all.deb ...
Unpacking python-pip (9.0.1-2.3~ubuntu<IP_ADDRESS>) ...
Selecting previously unselected package python-rosinstall-generator.
Preparing to unpack .../12-python-rosinstall-generator_0.1.22-1_all.deb ...
Unpacking python-rosinstall-generator (0.1.22-1) ...
Selecting previously unselected package python-wheel.
Preparing to unpack .../13-python-wheel_0.30.0-0.2_all.deb ...
Unpacking python-wheel (0.30.0-0.2) ...
Selecting previously unselected package python-xdg.
Preparing to unpack .../14-python-xdg_0.25-4ubuntu1.1_all.deb ...
Unpacking python-xdg (0.25-4ubuntu1.1) ...
Setting up python-pip-whl (9.0.1-2.3~ubuntu<IP_ADDRESS>) ...
Setting up python-crypto (2.6.1-8ubuntu2) ...
Setting up python-wheel (0.30.0-0.2) ...
Setting up libpython-all-dev:amd64 (2.7.15~rc1-1) ...
Setting up python-keyrings.alt (3.0-1) ...
Setting up python-gi (3.26.1-2ubuntu1) ...
Setting up dbus (1.12.2-1ubuntu1.2) ...
Setting up python-dbus (1.2.6-1) ...
Setting up python-pip (9.0.1-2.3~ubuntu<IP_ADDRESS>) ...
Setting up python-all (2.7.15~rc1-1) ...
Setting up python-rosinstall-generator (0.1.22-1) ...
Setting up python-xdg (0.25-4ubuntu1.1) ...
Setting up python-secretstorage (2.3.1-2) ...
Setting up python-keyring (10.6.0-1) ...
Setting up python-all-dev (2.7.15~rc1-1) ...
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  libfcl-dev libfcl0.5 liboctomap-dev liboctomap1.8
  ros-melodic-eigen-stl-containers ros-melodic-geometric-shapes
  ros-melodic-moveit-core ros-melodic-moveit-msgs
  ros-melodic-moveit-ros-occupancy-map-monitor ros-melodic-moveit-ros-planning
  ros-melodic-object-recognition-msgs ros-melodic-octomap
  ros-melodic-octomap-msgs ros-melodic-pybind11-catkin
  ros-melodic-random-numbers ros-melodic-srdfdom
The following NEW packages will be installed:
  libfcl-dev libfcl0.5 liboctomap-dev liboctomap1.8
  ros-melodic-eigen-stl-containers ros-melodic-geometric-shapes
  ros-melodic-moveit-core ros-melodic-moveit-fake-controller-manager
  ros-melodic-moveit-msgs ros-melodic-moveit-ros-occupancy-map-monitor
  ros-melodic-moveit-ros-planning ros-melodic-object-recognition-msgs
  ros-melodic-octomap ros-melodic-octomap-msgs ros-melodic-pybind11-catkin
  ros-melodic-random-numbers ros-melodic-srdfdom
0 upgraded, 17 newly installed, 0 to remove and 107 not upgraded.
Need to get 4610 kB of archives.
After this operation, 49.9 MB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu bionic/universe amd64 libfcl0.5 amd64 0.5.0-5 [902 kB]
Get:2 http://packages.ros.org/ros/ubuntu bionic/main amd64 ros-melodic-eigen-stl-containers amd64 0.1.8-0bionic.20201015.033045 [6816 B]
Get:3 http://packages.ros.org/ros/ubuntu bionic/main amd64 ros-melodic-octomap amd64 1.9.7-1bionic.20210504.141732 [191 kB]
Get:4 http://packages.ros.org/ros/ubuntu bionic/main amd64 ros-melodic-random-numbers amd64 0.3.2-0bionic.20201015.065429 [28.0 kB]
Get:5 http://packages.ros.org/ros/ubuntu bionic/main amd64 ros-melodic-geometric-shapes amd64 0.6.4-1bionic.20210519.200253 [80.6 kB]
Get:6 http://archive.ubuntu.com/ubuntu bionic/universe amd64 liboctomap1.8 amd64 1.8.1+dfsg-1 [72.5 kB]
Get:7 http://archive.ubuntu.com/ubuntu bionic/universe amd64 liboctomap-dev amd64 1.8.1+dfsg-1 [119 kB]
Get:8 http://archive.ubuntu.com/ubuntu bionic/universe amd64 libfcl-dev amd64 0.5.0-5 [88.6 kB]
Get:9 http://packages.ros.org/ros/ubuntu bionic/main amd64 ros-melodic-object-recognition-msgs amd64 0.4.1-0bionic.20210505.043500 [70.1 kB]
Get:10 http://packages.ros.org/ros/ubuntu bionic/main amd64 ros-melodic-octomap-msgs amd64 0.3.5-1bionic.20210505.011716 [29.4 kB]
Get:11 http://packages.ros.org/ros/ubuntu bionic/main amd64 ros-melodic-moveit-msgs amd64 0.10.1-1bionic.20210505.043840 [664 kB]
Get:12 http://packages.ros.org/ros/ubuntu bionic/main amd64 ros-melodic-pybind11-catkin amd64 2.4.3-1bionic.20200731.225101 [118 kB]
Get:13 http://packages.ros.org/ros/ubuntu bionic/main amd64 ros-melodic-srdfdom amd64 0.5.2-1bionic.20210505.022841 [60.5 kB]
Get:14 http://packages.ros.org/ros/ubuntu bionic/main amd64 ros-melodic-moveit-core amd64 1.0.8-1bionic.20210719.224614 [1192 kB]
Get:15 http://packages.ros.org/ros/ubuntu bionic/main amd64 ros-melodic-moveit-ros-occupancy-map-monitor amd64 1.0.8-1bionic.20210719.231211 [135 kB]
Get:16 http://packages.ros.org/ros/ubuntu bionic/main amd64 ros-melodic-moveit-ros-planning amd64 1.0.8-1bionic.20210719.231635 [787 kB]
Get:17 http://packages.ros.org/ros/ubuntu bionic/main amd64 ros-melodic-moveit-fake-controller-manager amd64 1.0.8-1bionic.20210719.233337 [66.4 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 4610 kB in 24s (195 kB/s)
Selecting previously unselected package libfcl0.5.
(Reading database ... 105876 files and directories currently installed.)
Preparing to unpack .../00-libfcl0.5_0.5.0-5_amd64.deb ...
Unpacking libfcl0.5 (0.5.0-5) ...
Selecting previously unselected package liboctomap1.8.
Preparing to unpack .../01-liboctomap1.8_1.8.1+dfsg-1_amd64.deb ...
Unpacking liboctomap1.8 (1.8.1+dfsg-1) ...
Selecting previously unselected package liboctomap-dev.
Preparing to unpack .../02-liboctomap-dev_1.8.1+dfsg-1_amd64.deb ...
Unpacking liboctomap-dev (1.8.1+dfsg-1) ...
Selecting previously unselected package ros-melodic-eigen-stl-containers.
Preparing to unpack .../03-ros-melodic-eigen-stl-containers_0.1.8-0bionic.20201015.033045_amd64.deb ...
Unpacking ros-melodic-eigen-stl-containers (0.1.8-0bionic.20201015.033045) ...
Selecting previously unselected package ros-melodic-octomap.
Preparing to unpack .../04-ros-melodic-octomap_1.9.7-1bionic.20210504.141732_amd64.deb ...
Unpacking ros-melodic-octomap (1.9.7-1bionic.20210504.141732) ...
Selecting previously unselected package ros-melodic-random-numbers.
Preparing to unpack .../05-ros-melodic-random-numbers_0.3.2-0bionic.20201015.065429_amd64.deb ...
Unpacking ros-melodic-random-numbers (0.3.2-0bionic.20201015.065429) ...
Selecting previously unselected package ros-melodic-geometric-shapes.
Preparing to unpack .../06-ros-melodic-geometric-shapes_0.6.4-1bionic.20210519.200253_amd64.deb ...
Unpacking ros-melodic-geometric-shapes (0.6.4-1bionic.20210519.200253) ...
Selecting previously unselected package libfcl-dev.
Preparing to unpack .../07-libfcl-dev_0.5.0-5_amd64.deb ...
Unpacking libfcl-dev (0.5.0-5) ...
Selecting previously unselected package ros-melodic-object-recognition-msgs.
Preparing to unpack .../08-ros-melodic-object-recognition-msgs_0.4.1-0bionic.20210505.043500_amd64.deb ...
Unpacking ros-melodic-object-recognition-msgs (0.4.1-0bionic.20210505.043500) ...
Selecting previously unselected package ros-melodic-octomap-msgs.
Preparing to unpack .../09-ros-melodic-octomap-msgs_0.3.5-1bionic.20210505.011716_amd64.deb ...
Unpacking ros-melodic-octomap-msgs (0.3.5-1bionic.20210505.011716) ...
Selecting previously unselected package ros-melodic-moveit-msgs.
Preparing to unpack .../10-ros-melodic-moveit-msgs_0.10.1-1bionic.20210505.043840_amd64.deb ...
Unpacking ros-melodic-moveit-msgs (0.10.1-1bionic.20210505.043840) ...
Selecting previously unselected package ros-melodic-pybind11-catkin.
Preparing to unpack .../11-ros-melodic-pybind11-catkin_2.4.3-1bionic.20200731.225101_amd64.deb ...
Unpacking ros-melodic-pybind11-catkin (2.4.3-1bionic.20200731.225101) ...
Selecting previously unselected package ros-melodic-srdfdom.
Preparing to unpack .../12-ros-melodic-srdfdom_0.5.2-1bionic.20210505.022841_amd64.deb ...
Unpacking ros-melodic-srdfdom (0.5.2-1bionic.20210505.022841) ...
Selecting previously unselected package ros-melodic-moveit-core.
Preparing to unpack .../13-ros-melodic-moveit-core_1.0.8-1bionic.20210719.224614_amd64.deb ...
Unpacking ros-melodic-moveit-core (1.0.8-1bionic.20210719.224614) ...
Selecting previously unselected package ros-melodic-moveit-ros-occupancy-map-monitor.
Preparing to unpack .../14-ros-melodic-moveit-ros-occupancy-map-monitor_1.0.8-1bionic.20210719.231211_amd64.deb ...
Unpacking ros-melodic-moveit-ros-occupancy-map-monitor (1.0.8-1bionic.20210719.231211) ...
Selecting previously unselected package ros-melodic-moveit-ros-planning.
Preparing to unpack .../15-ros-melodic-moveit-ros-planning_1.0.8-1bionic.20210719.231635_amd64.deb ...
Unpacking ros-melodic-moveit-ros-planning (1.0.8-1bionic.20210719.231635) ...
Selecting previously unselected package ros-melodic-moveit-fake-controller-manager.
Preparing to unpack .../16-ros-melodic-moveit-fake-controller-manager_1.0.8-1bionic.20210719.233337_amd64.deb ...
Unpacking ros-melodic-moveit-fake-controller-manager (1.0.8-1bionic.20210719.233337) ...
Setting up ros-melodic-octomap (1.9.7-1bionic.20210504.141732) ...
Setting up ros-melodic-random-numbers (0.3.2-0bionic.20201015.065429) ...
Setting up ros-melodic-eigen-stl-containers (0.1.8-0bionic.20201015.033045) ...
Setting up ros-melodic-srdfdom (0.5.2-1bionic.20210505.022841) ...
Setting up ros-melodic-octomap-msgs (0.3.5-1bionic.20210505.011716) ...
Setting up ros-melodic-pybind11-catkin (2.4.3-1bionic.20200731.225101) ...
Setting up ros-melodic-object-recognition-msgs (0.4.1-0bionic.20210505.043500) ...
Setting up liboctomap1.8 (1.8.1+dfsg-1) ...
Setting up libfcl0.5 (0.5.0-5) ...
Setting up ros-melodic-geometric-shapes (0.6.4-1bionic.20210519.200253) ...
Setting up ros-melodic-moveit-msgs (0.10.1-1bionic.20210505.043840) ...
Setting up liboctomap-dev (1.8.1+dfsg-1) ...
Setting up libfcl-dev (0.5.0-5) ...
Setting up ros-melodic-moveit-core (1.0.8-1bionic.20210719.224614) ...
Setting up ros-melodic-moveit-ros-occupancy-map-monitor (1.0.8-1bionic.20210719.231211) ...
Setting up ros-melodic-moveit-ros-planning (1.0.8-1bionic.20210719.231635) ...
Setting up ros-melodic-moveit-fake-controller-manager (1.0.8-1bionic.20210719.233337) ...
Processing triggers for libc-bin (2.27-3ubuntu1.4) ...
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  liburdfdom-tools python-bs4 python-chardet python-html5lib python-lxml
  python-webencodings
Suggested packages:
  python-genshi python-lxml-dbg python-lxml-doc
The following NEW packages will be installed:
  liburdfdom-tools python-bs4 python-chardet python-html5lib python-lxml
  python-webencodings ros-melodic-moveit-kinematics
0 upgraded, 7 newly installed, 0 to remove and 107 not upgraded.
Need to get 1400 kB of archives.
After this operation, 7774 kB of additional disk space will be used.
Get:1 http://packages.ros.org/ros/ubuntu bionic/main amd64 ros-melodic-moveit-kinematics amd64 1.0.8-1bionic.20210719.232855 [248 kB]
Get:2 http://archive.ubuntu.com/ubuntu bionic/main amd64 python-bs4 all 4.6.0-1 [67.9 kB]
Get:3 http://archive.ubuntu.com/ubuntu bionic/main amd64 python-chardet all 3.0.4-1 [80.3 kB]
Get:4 http://archive.ubuntu.com/ubuntu bionic/main amd64 python-webencodings all 0.5-2 [10.3 kB]
Get:5 http://archive.ubuntu.com/ubuntu bionic/main amd64 python-html5lib all 0.999999999-1 [83.6 kB]
Get:6 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 python-lxml amd64 4.2.1-1ubuntu0.4 [897 kB]
Get:7 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 liburdfdom-tools amd64 1.0.0-2ubuntu0.1 [12.5 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 1400 kB in 2s (623 kB/s)
Selecting previously unselected package python-bs4.
(Reading database ... 107628 files and directories currently installed.)
Preparing to unpack .../0-python-bs4_4.6.0-1_all.deb ...
Unpacking python-bs4 (4.6.0-1) ...
Selecting previously unselected package python-chardet.
Preparing to unpack .../1-python-chardet_3.0.4-1_all.deb ...
Unpacking python-chardet (3.0.4-1) ...
Selecting previously unselected package python-webencodings.
Preparing to unpack .../2-python-webencodings_0.5-2_all.deb ...
Unpacking python-webencodings (0.5-2) ...
Selecting previously unselected package python-html5lib.
Preparing to unpack .../3-python-html5lib_0.999999999-1_all.deb ...
Unpacking python-html5lib (0.999999999-1) ...
Selecting previously unselected package python-lxml:amd64.
Preparing to unpack .../4-python-lxml_4.2.1-1ubuntu0.4_amd64.deb ...
Unpacking python-lxml:amd64 (4.2.1-1ubuntu0.4) ...
Selecting previously unselected package liburdfdom-tools.
Preparing to unpack .../5-liburdfdom-tools_1.0.0-2ubuntu0.1_amd64.deb ...
Unpacking liburdfdom-tools (1.0.0-2ubuntu0.1) ...
Selecting previously unselected package ros-melodic-moveit-kinematics.
Preparing to unpack .../6-ros-melodic-moveit-kinematics_1.0.8-1bionic.20210719.232855_amd64.deb ...
Unpacking ros-melodic-moveit-kinematics (1.0.8-1bionic.20210719.232855) ...
Setting up liburdfdom-tools (1.0.0-2ubuntu0.1) ...
Setting up python-chardet (3.0.4-1) ...
Setting up python-bs4 (4.6.0-1) ...
Setting up python-lxml:amd64 (4.2.1-1ubuntu0.4) ...
Setting up python-webencodings (0.5-2) ...
Setting up ros-melodic-moveit-kinematics (1.0.8-1bionic.20210719.232855) ...
Setting up python-html5lib (0.999999999-1) ...
Processing triggers for libc-bin (2.27-3ubuntu1.4) ...
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  libglew-dev libglew2.0 libomp-dev libomp5 ros-melodic-eigenpy
  ros-melodic-moveit-ros-manipulation ros-melodic-moveit-ros-move-group
  ros-melodic-moveit-ros-perception ros-melodic-moveit-ros-planning-interface
  ros-melodic-moveit-ros-robot-interaction
  ros-melodic-moveit-ros-visualization ros-melodic-moveit-ros-warehouse
  ros-melodic-warehouse-ros
Suggested packages:
  glew-utils libomp-doc
The following NEW packages will be installed:
  libglew-dev libglew2.0 libomp-dev libomp5 ros-melodic-eigenpy
  ros-melodic-moveit-ros-manipulation ros-melodic-moveit-ros-move-group
  ros-melodic-moveit-ros-perception ros-melodic-moveit-ros-planning-interface
  ros-melodic-moveit-ros-robot-interaction
  ros-melodic-moveit-ros-visualization ros-melodic-moveit-ros-warehouse
  ros-melodic-moveit-setup-assistant ros-melodic-warehouse-ros
0 upgraded, 14 newly installed, 0 to remove and 107 not upgraded.
Need to get 4912 kB of archives.
After this operation, 25.6 MB of additional disk space will be used.
Get:1 http://packages.ros.org/ros/ubuntu bionic/main amd64 ros-melodic-eigenpy amd64 2.6.4-1bionic.20210527.213718 [1009 kB]
Get:2 http://archive.ubuntu.com/ubuntu bionic/universe amd64 libglew2.0 amd64 2.0.0-5 [140 kB]
Get:3 http://archive.ubuntu.com/ubuntu bionic/universe amd64 libglew-dev amd64 2.0.0-5 [120 kB]
Get:4 http://archive.ubuntu.com/ubuntu bionic/universe amd64 libomp5 amd64 5.0.1-1 [234 kB]
Get:5 http://archive.ubuntu.com/ubuntu bionic/universe amd64 libomp-dev amd64 5.0.1-1 [5088 B]
Get:6 http://packages.ros.org/ros/ubuntu bionic/main amd64 ros-melodic-moveit-ros-move-group amd64 1.0.8-1bionic.20210719.233440 [344 kB]
Get:7 http://packages.ros.org/ros/ubuntu bionic/main amd64 ros-melodic-moveit-ros-manipulation amd64 1.0.8-1bionic.20210719.234512 [299 kB]
Get:8 http://packages.ros.org/ros/ubuntu bionic/main amd64 ros-melodic-moveit-ros-perception amd64 1.0.8-1bionic.20210719.233424 [274 kB]
Get:9 http://packages.ros.org/ros/ubuntu bionic/main amd64 ros-melodic-warehouse-ros amd64 0.9.4-1bionic.20210505.034027 [90.2 kB]
Get:10 http://packages.ros.org/ros/ubuntu bionic/main amd64 ros-melodic-moveit-ros-warehouse amd64 1.0.8-1bionic.20210719.233518 [349 kB]
Get:11 http://packages.ros.org/ros/ubuntu bionic/main amd64 ros-melodic-moveit-ros-planning-interface amd64 1.0.8-1bionic.20210719.235155 [527 kB]
Get:12 http://packages.ros.org/ros/ubuntu bionic/main amd64 ros-melodic-moveit-ros-robot-interaction amd64 1.0.8-1bionic.20210719.233456 [125 kB]
Get:13 http://packages.ros.org/ros/ubuntu bionic/main amd64 ros-melodic-moveit-ros-visualization amd64 1.0.8-1bionic.20210720.000350 [546 kB]
Get:14 http://packages.ros.org/ros/ubuntu bionic/main amd64 ros-melodic-moveit-setup-assistant amd64 1.0.8-1bionic.20210720.001858 [850 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 4912 kB in 19s (264 kB/s)
Selecting previously unselected package libglew2.0:amd64.
(Reading database ... 107913 files and directories currently installed.)
Preparing to unpack .../00-libglew2.0_2.0.0-5_amd64.deb ...
Unpacking libglew2.0:amd64 (2.0.0-5) ...
Selecting previously unselected package libglew-dev:amd64.
Preparing to unpack .../01-libglew-dev_2.0.0-5_amd64.deb ...
Unpacking libglew-dev:amd64 (2.0.0-5) ...
Selecting previously unselected package ros-melodic-eigenpy.
Preparing to unpack .../02-ros-melodic-eigenpy_2.6.4-1bionic.20210527.213718_amd64.deb ...
Unpacking ros-melodic-eigenpy (2.6.4-1bionic.20210527.213718) ...
Selecting previously unselected package ros-melodic-moveit-ros-move-group.
Preparing to unpack .../03-ros-melodic-moveit-ros-move-group_1.0.8-1bionic.20210719.233440_amd64.deb ...
Unpacking ros-melodic-moveit-ros-move-group (1.0.8-1bionic.20210719.233440) ...
Selecting previously unselected package ros-melodic-moveit-ros-manipulation.
Preparing to unpack .../04-ros-melodic-moveit-ros-manipulation_1.0.8-1bionic.20210719.234512_amd64.deb ...
Unpacking ros-melodic-moveit-ros-manipulation (1.0.8-1bionic.20210719.234512) ...
Selecting previously unselected package libomp5:amd64.
Preparing to unpack .../05-libomp5_5.0.1-1_amd64.deb ...
Unpacking libomp5:amd64 (5.0.1-1) ...
Selecting previously unselected package libomp-dev.
Preparing to unpack .../06-libomp-dev_5.0.1-1_amd64.deb ...
Unpacking libomp-dev (5.0.1-1) ...
Selecting previously unselected package ros-melodic-moveit-ros-perception.
Preparing to unpack .../07-ros-melodic-moveit-ros-perception_1.0.8-1bionic.20210719.233424_amd64.deb ...
Unpacking ros-melodic-moveit-ros-perception (1.0.8-1bionic.20210719.233424) ...
Selecting previously unselected package ros-melodic-warehouse-ros.
Preparing to unpack .../08-ros-melodic-warehouse-ros_0.9.4-1bionic.20210505.034027_amd64.deb ...
Unpacking ros-melodic-warehouse-ros (0.9.4-1bionic.20210505.034027) ...
Selecting previously unselected package ros-melodic-moveit-ros-warehouse.
Preparing to unpack .../09-ros-melodic-moveit-ros-warehouse_1.0.8-1bionic.20210719.233518_amd64.deb ...
Unpacking ros-melodic-moveit-ros-warehouse (1.0.8-1bionic.20210719.233518) ...
Selecting previously unselected package ros-melodic-moveit-ros-planning-interface.
Preparing to unpack .../10-ros-melodic-moveit-ros-planning-interface_1.0.8-1bionic.20210719.235155_amd64.deb ...
Unpacking ros-melodic-moveit-ros-planning-interface (1.0.8-1bionic.20210719.235155) ...
Selecting previously unselected package ros-melodic-moveit-ros-robot-interaction.
Preparing to unpack .../11-ros-melodic-moveit-ros-robot-interaction_1.0.8-1bionic.20210719.233456_amd64.deb ...
Unpacking ros-melodic-moveit-ros-robot-interaction (1.0.8-1bionic.20210719.233456) ...
Selecting previously unselected package ros-melodic-moveit-ros-visualization.
Preparing to unpack .../12-ros-melodic-moveit-ros-visualization_1.0.8-1bionic.20210720.000350_amd64.deb ...
Unpacking ros-melodic-moveit-ros-visualization (1.0.8-1bionic.20210720.000350) ...
Selecting previously unselected package ros-melodic-moveit-setup-assistant.
Preparing to unpack .../13-ros-melodic-moveit-setup-assistant_1.0.8-1bionic.20210720.001858_amd64.deb ...
Unpacking ros-melodic-moveit-setup-assistant (1.0.8-1bionic.20210720.001858) ...
Setting up ros-melodic-warehouse-ros (0.9.4-1bionic.20210505.034027) ...
Setting up ros-melodic-eigenpy (2.6.4-1bionic.20210527.213718) ...
Setting up libomp5:amd64 (5.0.1-1) ...
Setting up ros-melodic-moveit-ros-move-group (1.0.8-1bionic.20210719.233440) ...
Setting up ros-melodic-moveit-ros-robot-interaction (1.0.8-1bionic.20210719.233456) ...
Setting up libomp-dev (5.0.1-1) ...
Setting up libglew2.0:amd64 (2.0.0-5) ...
Setting up libglew-dev:amd64 (2.0.0-5) ...
Setting up ros-melodic-moveit-ros-warehouse (1.0.8-1bionic.20210719.233518) ...
Setting up ros-melodic-moveit-ros-manipulation (1.0.8-1bionic.20210719.234512) ...
Setting up ros-melodic-moveit-ros-perception (1.0.8-1bionic.20210719.233424) ...
Setting up ros-melodic-moveit-ros-planning-interface (1.0.8-1bionic.20210719.235155) ...
Setting up ros-melodic-moveit-ros-visualization (1.0.8-1bionic.20210720.000350) ...
Setting up ros-melodic-moveit-setup-assistant (1.0.8-1bionic.20210720.001858) ...
Processing triggers for libc-bin (2.27-3ubuntu1.4) ...
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  ros-melodic-joint-state-publisher-gui
0 upgraded, 1 newly installed, 0 to remove and 107 not upgraded.
Need to get 12.0 kB of archives.
After this operation, 55.3 kB of additional disk space will be used.
Get:1 http://packages.ros.org/ros/ubuntu bionic/main amd64 ros-melodic-joint-state-publisher-gui amd64 1.12.15-1bionic.20210716.091334 [12.0 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 12.0 kB in 1s (16.9 kB/s)
Selecting previously unselected package ros-melodic-joint-state-publisher-gui.
(Reading database ... 108543 files and directories currently installed.)
Preparing to unpack .../ros-melodic-joint-state-publisher-gui_1.12.15-1bionic.20210716.091334_amd64.deb ...
Unpacking ros-melodic-joint-state-publisher-gui (1.12.15-1bionic.20210716.091334) ...
Setting up ros-melodic-joint-state-publisher-gui (1.12.15-1bionic.20210716.091334) ...
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  blt tk8.6-blt2.5
Suggested packages:
  blt-demo tix python-tk-dbg
The following NEW packages will be installed:
  blt python-tk tk8.6-blt2.5
0 upgraded, 3 newly installed, 0 to remove and 107 not upgraded.
Need to get 603 kB of archives.
After this operation, 2122 kB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu bionic/main amd64 tk8.6-blt2.5 amd64 2.5.3+dfsg-4 [572 kB]
Get:2 http://archive.ubuntu.com/ubuntu bionic/main amd64 blt amd64 2.5.3+dfsg-4 [4944 B]
Get:3 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 python-tk amd64 2.7.17-1~18.04 [26.0 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 603 kB in 2s (259 kB/s)
Selecting previously unselected package tk8.6-blt2.5.
(Reading database ... 108557 files and directories currently installed.)
Preparing to unpack .../tk8.6-blt2.5_2.5.3+dfsg-4_amd64.deb ...
Unpacking tk8.6-blt2.5 (2.5.3+dfsg-4) ...
Selecting previously unselected package blt.
Preparing to unpack .../blt_2.5.3+dfsg-4_amd64.deb ...
Unpacking blt (2.5.3+dfsg-4) ...
Selecting previously unselected package python-tk.
Preparing to unpack .../python-tk_2.7.17-1~18.04_amd64.deb ...
Unpacking python-tk (2.7.17-1~18.04) ...
Setting up tk8.6-blt2.5 (2.5.3+dfsg-4) ...
Setting up blt (2.5.3+dfsg-4) ...
Setting up python-tk (2.7.17-1~18.04) ...
Processing triggers for libc-bin (2.27-3ubuntu1.4) ...
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  evemu-tools evtest inputattach joystick libevemu3 libsdl1.2debian
The following NEW packages will be installed:
  evemu-tools evtest inputattach joystick libevemu3 libsdl1.2debian
  ros-melodic-joy
0 upgraded, 7 newly installed, 0 to remove and 107 not upgraded.
Need to get 337 kB of archives.
After this operation, 1145 kB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu bionic/universe amd64 libevemu3 amd64 2.6.0-0.1 [12.2 kB]
Get:2 http://packages.ros.org/ros/ubuntu bionic/main amd64 ros-melodic-joy amd64 1.14.0-1bionic.20210505.032331 [53.9 kB]
Get:3 http://archive.ubuntu.com/ubuntu bionic/universe amd64 evemu-tools amd64 2.6.0-0.1 [12.7 kB]
Get:4 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libsdl1.2debian amd64 1.2.15+dfsg2-0.1ubuntu0.1 [175 kB]
Get:5 http://archive.ubuntu.com/ubuntu bionic/universe amd64 joystick amd64 1:1.6.0-2 [45.9 kB]
Get:6 http://archive.ubuntu.com/ubuntu bionic/universe amd64 evtest amd64 1:1.33-1build1 [15.6 kB]
Get:7 http://archive.ubuntu.com/ubuntu bionic/main amd64 inputattach amd64 1:1.6.0-2 [21.5 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 337 kB in 1s (225 kB/s)
Selecting previously unselected package libevemu3:amd64.
(Reading database ... 108590 files and directories currently installed.)
Preparing to unpack .../0-libevemu3_2.6.0-0.1_amd64.deb ...
Unpacking libevemu3:amd64 (2.6.0-0.1) ...
Selecting previously unselected package evemu-tools.
Preparing to unpack .../1-evemu-tools_2.6.0-0.1_amd64.deb ...
Unpacking evemu-tools (2.6.0-0.1) ...
Selecting previously unselected package libsdl1.2debian:amd64.
Preparing to unpack .../2-libsdl1.2debian_1.2.15+dfsg2-0.1ubuntu0.1_amd64.deb ...
Unpacking libsdl1.2debian:amd64 (1.2.15+dfsg2-0.1ubuntu0.1) ...
Selecting previously unselected package joystick.
Preparing to unpack .../3-joystick_1%3a1.6.0-2_amd64.deb ...
Unpacking joystick (1:1.6.0-2) ...
Selecting previously unselected package ros-melodic-joy.
Preparing to unpack .../4-ros-melodic-joy_1.14.0-1bionic.20210505.032331_amd64.deb ...
Unpacking ros-melodic-joy (1.14.0-1bionic.20210505.032331) ...
Selecting previously unselected package evtest.
Preparing to unpack .../5-evtest_1%3a1.33-1build1_amd64.deb ...
Unpacking evtest (1:1.33-1build1) ...
Selecting previously unselected package inputattach.
Preparing to unpack .../6-inputattach_1%3a1.6.0-2_amd64.deb ...
Unpacking inputattach (1:1.6.0-2) ...
Setting up inputattach (1:1.6.0-2) ...
Setting up libsdl1.2debian:amd64 (1.2.15+dfsg2-0.1ubuntu0.1) ...
Setting up evtest (1:1.33-1build1) ...
Setting up libevemu3:amd64 (2.6.0-0.1) ...
Setting up evemu-tools (2.6.0-0.1) ...
Setting up joystick (1:1.6.0-2) ...
Setting up ros-melodic-joy (1.14.0-1bionic.20210505.032331) ...
Processing triggers for libc-bin (2.27-3ubuntu1.4) ...
Reading package lists...
Building dependency tree...
Reading state information...
ros-melodic-moveit-msgs is already the newest version (0.10.1-1bionic.20210505.043840).
ros-melodic-moveit-msgs set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 107 not upgraded.
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  ros-melodic-ompl
The following NEW packages will be installed:
  ros-melodic-moveit-planners-ompl ros-melodic-ompl
0 upgraded, 2 newly installed, 0 to remove and 107 not upgraded.
Need to get 1888 kB of archives.
After this operation, 10.5 MB of additional disk space will be used.
Get:1 http://packages.ros.org/ros/ubuntu bionic/main amd64 ros-melodic-ompl amd64 1.4.2-5bionic.20191212.045602 [1527 kB]
Get:2 http://packages.ros.org/ros/ubuntu bionic/main amd64 ros-melodic-moveit-planners-ompl amd64 1.0.8-1bionic.20210719.233345 [361 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 1888 kB in 14s (137 kB/s)
Selecting previously unselected package ros-melodic-ompl.
(Reading database ... 108685 files and directories currently installed.)
Preparing to unpack .../ros-melodic-ompl_1.4.2-5bionic.20191212.045602_amd64.deb ...
Unpacking ros-melodic-ompl (1.4.2-5bionic.20191212.045602) ...
Selecting previously unselected package ros-melodic-moveit-planners-ompl.
Preparing to unpack .../ros-melodic-moveit-planners-ompl_1.0.8-1bionic.20210719.233345_amd64.deb ...
Unpacking ros-melodic-moveit-planners-ompl (1.0.8-1bionic.20210719.233345) ...
Setting up ros-melodic-ompl (1.4.2-5bionic.20191212.045602) ...
Setting up ros-melodic-moveit-planners-ompl (1.0.8-1bionic.20210719.233345) ...
Processing triggers for libc-bin (2.27-3ubuntu1.4) ...
Reading package lists...
Building dependency tree...
Reading state information...
ros-melodic-moveit-ros-move-group is already the newest version (1.0.8-1bionic.20210719.233440).
ros-melodic-moveit-ros-move-group set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 107 not upgraded.
Reading package lists...
Building dependency tree...
Reading state information...
ros-melodic-moveit-ros-visualization is already the newest version (1.0.8-1bionic.20210720.000350).
ros-melodic-moveit-ros-visualization set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 107 not upgraded.
executing command [apt-get install -y ros-melodic-moveit-fake-controller-manager]
executing command [apt-get install -y ros-melodic-moveit-kinematics]
executing command [apt-get install -y ros-melodic-moveit-setup-assistant]
executing command [apt-get install -y ros-melodic-joint-state-publisher-gui]
executing command [apt-get install -y python-tk]
executing command [apt-get install -y ros-melodic-joy]
executing command [apt-get install -y ros-melodic-moveit-msgs]
executing command [apt-get install -y ros-melodic-moveit-planners-ompl]
executing command [apt-get install -y ros-melodic-moveit-ros-move-group]
executing command [apt-get install -y ros-melodic-moveit-ros-visualization]
#All required rosdeps installed successfully
Removing intermediate container ea7ef011be0e
 ---> ebc79e332092
Step 12/16 : ARG PYMYCOBOT_VERSION
 ---> Running in cea6ee5459b7
Removing intermediate container cea6ee5459b7
 ---> d29a06c5bb6b
Step 13/16 : RUN pip install "pymycobot $PYMYCOBOT_VERSION" --user
 ---> Running in d38a7a7eb23a
Collecting pymycobot>=2<3
  Downloading https://files.pythonhosted.org/packages/f6/2e/766270044b6ec965e4fc37e908578497b402452cd94f755e87c8686e1263/pymycobot-2.6.0b1.tar.gz
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/tmp/pip-build-6DbU8C/pymycobot/setup.py", line 12, in <module>
        import pymycobot
      File "pymycobot/__init__.py", line 9, in <module>
        from pymycobot import utils
      File "pymycobot/utils.py", line 7, in <module>
        except ModuleNotFoundError:
    NameError: name 'ModuleNotFoundError' is not defined

    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-6DbU8C/pymycobot/
The command '/bin/bash -c pip install "pymycobot $PYMYCOBOT_VERSION" --user' returned a non-zero code: 1
ERROR: Service 'ros' failed to build : Build failed

Same issue, at same 13th step

Maybe we should pin the pymycobot version in the docker container? :thinking:

@apockill could be, I am using Ubuntu 18.04 LTS
Also if you want to share the dockerfile I can help you with the debugging

I've created a PR that should fix the issue https://github.com/elephantrobotics/mycobot_ros/pull/39/files
I think we might want to add some CI to the repo that tests the builds complete.

How are you running the build?

@abrahamperz it appears you didn't check out my PR, and typed it yourself. The package name is python3-pip not python-pip3


chore: adding access on get and update verbs of crd

Currently in DSP operator init we check if crd is diskpool crd is present on cluster. If no, then only we create crd defined in the image. In case crd is already present, We dont update the crd with new changes. This PR modifies access to crd resource. Adding get and update verb to the cluster role mayastor-cluster-role
Signed-off-by: Abhilash Shetty<EMAIL_ADDRESS>

bors merge


Extend WiFiEventHandler. Add info arguments.

Please review this request and decline it if brakes your code because i changed the parameter for got_ip.
Briefly: Added two more methods:
staScanDone(system_event_sta_scan_done_t info)
staAuthChange(system_event_sta_authmode_change_t info)
The event for 6 more methods is passed to the overridden method the same way as staGotIp so i can use it like:

virtual esp_err_t apStaConnected(system_event_ap_staconnected_t info)
{
printf("New client connected. ");
printf("MAC Address : %02x:%02x:%02x:%02x:%02x:%02x\n",
(unsigned char) info.mac[0],
(unsigned char) info.mac[1],
(unsigned char) info.mac[2],
(unsigned char) info.mac[3],
(unsigned char) info.mac[4],
(unsigned char) info.mac[5]);
}

Output: New client connected. MAC Address : ec:1f:72:9a:7e:43
This class was used in NeoPixelWiFiEventHandler too so i fixed it. The problem is that i changed staGotIp(system_event_sta_got_ip_t info)

Always happy to accommodate pull requests.  I'm never a happy camper when I submit a PR to other projects and they sit there for months.  When I see a PR, I read to make sure that there is nothing grossly wrong and then merge ... with Github, we never lose anything so if the community doesn't like, we can always back out.

You are right, Neil. You can always revert it. For the event info i firstly looked for a method returning the real event info but didnt find one. Another way is to implement something like:
virtual esp_err_t staConnected()
{
this.event()->event_info.connected // event() returning the last system_event_t* event

which is also clean.
or just pass system_event_t* event to all methods..


Bug/1689 accessibility modal open

Reference: https://www.w3.org/WAI/ARIA/apg/patterns/dialog-modal/examples/dialog/
Explanation: We need to focus the focusable element on the modal, so the screen reader can announce it.
2 new properties of a modal are introduced:

arialabel: the modal name. Otherwise the screen reader just announces it as "dialog"
alert: If it is set to be true, the screen reader will read all the content inside the dialog.

The first focusable element logic:

If the dialog has no focusable elements (no focusable elements, no close button, no action buttons) --> The screen reader won't announce the modal when it opens.  In that case, developers should set alert to be true, so the screen reader will announce all the content. https://www.w3.org/WAI/ARIA/apg/patterns/alertdialog/examples/alertdialog/ This case is perfect for use cases such as a confirmation dialog, an announcement dialog, a warning dialog...
If the dialog has no focusable elements beside the close button (closable true), the screen reader won't announce it. In this case, it is similar to the above situation, set alert to be true.
If the dialog has some focusable elements (button, link, input, select), when the modal opens, the first focusable element will be focused, and the screen reader will announce it.

Discussed with @chrisolsen  that we don't allow developers to set the focusable element they want to focus when the modal opens, to reduce the complexity.

https://github.com/GovAlta/ui-components/assets/120135417/23069286-853f-4617-b10c-d8fae706b8ed
Coding examples (provided in Angular)
<goa-button id="dialog1-button" (_click)="openAddDeliveryAddressModal()">Add Delivery Address</goa-button>
<goa-modal arialabel="Add Delivery Address" [open]="isAddDeliveryAddressModalOpen"
           (_close)="closeAddDeliveryAddressModal()" closable>
  <goa-form-item label="First name" ml="xs">
    <goa-input name="firstName"></goa-input>
  </goa-form-item>
  <goa-icon-button icon="refresh"></goa-icon-button>
  <goa-form-item label="Basic dropdown">
    <goa-dropdown name="item" (_change)="onChange()">
      <goa-dropdown-item value="red" label="Red"></goa-dropdown-item>
      <goa-dropdown-item value="green" label="Green"></goa-dropdown-item>
      <goa-dropdown-item value="blue" label="Blue"></goa-dropdown-item>
    </goa-dropdown>
  </goa-form-item>
  <goa-form-item label="Item">
    <goa-date-picker id="calendar" (_change)="onChange()" name="item" value="Fri Mar 15 2024 16:17:45 GMT-0400 (Eastern Daylight Time)"></goa-date-picker>
  </goa-form-item>
  <goa-chip content="Chip text" id="chip"></goa-chip>
  <goa-form-item label="Basic">
    <goa-radio-group name="item" value="1" (_change)="onChange()">
      <goa-radio-item value="1" label="Label1"></goa-radio-item>
      <goa-radio-item value="2" label="Label2"></goa-radio-item>
      <goa-radio-item value="3" label="Label3"></goa-radio-item>
    </goa-radio-group>
  </goa-form-item>
  <goa-form-item label="Basic">
    <goa-textarea id="textarea" name="item" (_change)="onChange()"></goa-textarea>
  </goa-form-item>

  <goa-form-item label="Last name" ml="xs">
    <goa-input name="lastName" id="lastName"></goa-input>
  </goa-form-item>
  <goa-form-item label="Basic" id="basic">
    <goa-checkbox name="item" text="Item"></goa-checkbox>
  </goa-form-item>
  <goa-button (_click)="closeAddDeliveryAddressModal()">
    Special button to close the modal
  </goa-button>

    <goa-button-group alignment="end">
      <goa-button type="secondary" (_click)="closeAddDeliveryAddressModal()">Cancel</goa-button>
      <goa-button type="primary" (_click)="closeAddDeliveryAddressModal()">Save</goa-button>
    </goa-button-group>

</goa-modal>

Hi, I notice something, when selectorprimaryfocus is set to goa-radio-group or goa-checkbox, the voice over will read extra element, please see attached screen shot

one more issue we found
Model selectorprimaryfocus will not focus on the button that is with in an
Description:
Please see attached screen record, as you can see, when I set selectorprimaryfocus  to a button that is with in the  Tag, it will not be focused, when I change to , it will auto focus alright
Uploading Recording 2024-03-20 151248.mp4…
``
<goa-button id="dialog1-button" (_click)="openAddDeliveryAddressModal()">Add Delivery Address
<goa-modal arialabel="Add Delivery Address" [open]="isAddDeliveryAddressModalOpen"
(_close)="closeAddDeliveryAddressModal()" closable selectorprimaryfocus="button3">

Href
<goa-button (_click)="closeAddDeliveryAddressModal()" id="button1">
Special button to close the modal

<goa-dropdown name="item" (_change)="onChange()" id="dropdown">

<goa-date-picker id="calendar" (_change)="onChange()" name="item" value="Fri Mar 15 2024 16:17:45 GMT-0400 (Eastern Daylight Time)">

<goa-radio-group name="item" value="1" (_change)="onChange()" id="radio">

<goa-textarea id="textarea" name="item" (_change)="onChange()">

Cancel
Save

``

one more issue we found
Model selectorprimaryfocus will not focus on normal html tag such as input, a, select or button
Description:
have selectorprimaryfocus set to an ID of normal html tag with in modal,
Expected:
When model open, the html should be focused
Actual
the close button is focused
Env
Windows, Chrome and firefox
``
<goa-button id="dialog1-button" (_click)="openAddDeliveryAddressModal()">Add Delivery Address
<goa-modal arialabel="Add Delivery Address" [open]="isAddDeliveryAddressModalOpen"
(_close)="closeAddDeliveryAddressModal()" closable selectorprimaryfocus="button33">
Href
TTDDSS

A
B
C

``

We found this issue,
When we have GoAButton as first focusable element, when model open, the screen reader will read the whole model instead only read the GoAButton
Enviroment, Chrome, Desktop, NVDA
code:
``
import { useState } from "react";
import {
GoAContainer,
GoADropdown,
GoADropdownItem,
GoAFormItem,
GoATabs,
GoATab,
GoAButton,
GoAPopover,
GoAModal, // Assuming GoAModal is the correct component
GoAInput,
GoADatePicker,
GoAChip,
GoARadioGroup,
GoARadioItem,
GoATextarea,
GoACheckbox,
GoAButtonGroup
} from "@abgov/react-components";
export function Bug1689Page() {
const [isOpenOne, setIsOpenOne] = useState(false);
const [isOpenTwo, setIsOpenTwo] = useState(false);
return (
<>
<GoAButton id="dialog1-button" onClick={()=>setIsOpenOne(true)}>Add Delivery Address
<GoAModal open={isOpenOne} ariaLabel="please read this" closable={true} onClose={()=>setIsOpenOne(false)}>
Save

Save
  <GoAFormItem label="Basic dropdown">
    <GoADropdown name="item">
      <GoADropdownItem value="red" label="Red" />
      <GoADropdownItem value="green" label="Green" />
      <GoADropdownItem value="blue" label="Blue" />
    </GoADropdown>
    <GoAFormItem label="First name">
      <GoAInput name="firstName" />
    </GoAFormItem>
    </GoAFormItem>
    <GoAFormItem label="Item">
    </GoAFormItem>
    <GoAChip content="Chip text" id="chip" />
    <GoAFormItem label="Basic">
      <GoARadioGroup name="item" value="1">
        <GoARadioItem value="1" label="Label1" />
        <GoARadioItem value="2" label="Label2" />
        <GoARadioItem value="3" label="Label3" />
      </GoARadioGroup>
    </GoAFormItem>
    <GoAFormItem label="Basic">
      <GoATextarea id="textarea" name="item" />
    </GoAFormItem>
    <GoAFormItem label="Last name">
      <GoAInput name="lastName" id="lastName" />
    </GoAFormItem>
    <GoAFormItem label="Basic" id="basic">
      <GoACheckbox name="item" text="Item" />
    </GoAFormItem>

      <GoAButtonGroup alignment="end">
        <GoAButton type="secondary" onClick={()=>setIsOpenOne(false)}>Cancel</GoAButton>
        <GoAButton type="primary">Save</GoAButton>
      </GoAButtonGroup>

  </GoAModal>

  <GoAButton id="dialog1-button2" onClick={()=>setIsOpenTwo(true)}>Alert</GoAButton>
  <GoAModal open={isOpenTwo} ariaLabel="please read this" closable={true} onClose={()=>setIsOpenTwo(false)}>
  <GoAButton type="primary">Save</GoAButton>
  <GoAFormItem label="First name">
    <GoAInput name="firstName" />
  </GoAFormItem>
  <GoADropdown name="item">
    <GoADropdownItem value="red" label="Red" />
    <GoADropdownItem value="green" label="Green" />
    <GoADropdownItem value="blue" label="Blue" />
  </GoADropdown>
  <GoAButton type="primary">Save</GoAButton>

  <GoAFormItem label="Basic dropdown">
    <GoADropdown name="item">
      <GoADropdownItem value="red" label="Red" />
      <GoADropdownItem value="green" label="Green" />
      <GoADropdownItem value="blue" label="Blue" />
    </GoADropdown>
    <GoAFormItem label="First name">
      <GoAInput name="firstName" />
    </GoAFormItem>
    </GoAFormItem>
    <GoAFormItem label="Item">
    </GoAFormItem>
    <GoAChip content="Chip text" id="chip" />
    <GoAFormItem label="Basic">
      <GoARadioGroup name="item" value="1">
        <GoARadioItem value="1" label="Label1" />
        <GoARadioItem value="2" label="Label2" />
        <GoARadioItem value="3" label="Label3" />
      </GoARadioGroup>
    </GoAFormItem>
    <GoAFormItem label="Basic">
      <GoATextarea id="textarea" name="item" />
    </GoAFormItem>
    <GoAFormItem label="Last name">
      <GoAInput name="lastName" id="lastName" />
    </GoAFormItem>
    <GoAFormItem label="Basic" id="basic">
      <GoACheckbox name="item" text="Item" />
    </GoAFormItem>

      <GoAButtonGroup alignment="end">
        <GoAButton type="secondary" onClick={()=>setIsOpenTwo(false)}>Cancel</GoAButton>
        <GoAButton type="primary">Save</GoAButton>
      </GoAButtonGroup>

  </GoAModal>
</>

);
}
export default Bug1689Page;
`
Please see attached screen shot
https://github.com/GovAlta/ui-components/assets/7528736/422502ba-58f1-4e75-9e63-7a32796e203c

Issue is tested for react and angular for chrome, firefox and edge for NVDA on windows

Just adding a comment here so everyone is aware. I noticed a change to FocusTrap, which is used in Popover, which in turn is used in both the AppHeader and Datepicker components. I've asked @lizhuomeng71 to test both those components as well, just to make sure they still function as expected.

:tada: This PR is included in version 1.17.0-alpha.37 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 4.17.0-alpha.21 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 4.20.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 3.0.0-alpha.4 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 3.0.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Multiple URLs for publicPath to allow multiple CDN subdomains

Does webpack have the ability to use multiple URL aliases for the publicPath?
I would like to use the common trick of having 4 CDN urls to improve  load performance

No, but with a little hack this may be possible:
var idx = 0;
Object.defineProperty(__webpack_require__, "p", {
  get: function() {
    idx = (idx + 1) % 4;
    return "cdn" + idx + ".server.com/";
  }
});

With HTTP2 you don't need this anymore.

@sokra and how about now?

I don't think the situation has changed. As mentioned by Tobias, you can work around this with a __webpack_require__ specific tweak. Maybe publicPath could accept a function where similar customization could be performed so you get entirely static output. If someone is interested, please open a separate issue and propose an API.


Euler method in js

+Fixed the ODE(hopefully), cuz there was an inconsistency with ODE and the code

oops uh the bash commit is there

Ah ok

oops misspelt XD

oh whoops missed that PR


New version: Bitwarden.CLI version 2024.8.1

Pull request has been created with komac v2.4.1 :rocket:
Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Installation failed with exit code -1978335187
2024-08-26 13:38:20.416 [FAIL] Installer failed security check. Url: https://github.com/bitwarden/clients/releases/download/cli-v2024.8.1/bw-windows-2024.8.1.zip Result: 0x80004005

Automated error analysis suggests -1978335187 may mean Installer failed security check. Another script should retry this every 18 hours.
Automated error analysis suggests 80004005 may mean Resource missing
(Automated response - build 888.)

/azp run