Add "see also" attribute to user model

should be an Uri towards some informations (multivalued)

Thanks for the PR, but I see that I wasn't precise enough. My idea was that we could want to add some external information to an user.
As I saw it, we would add a seeAlsoAttribute containing, an uri, and the content of the resource at that uri would be directly add to the user.
In my head (but it could be better designed maybe) If i add a seeAlso attribute like https://api.github.com/search/users?q=cedric.couralet@insee.fr+in:email|items[0].login|github_username sugoi would make the http request extract the json from the response and provide the value in the user attribute github_username.
This could work by adding a decorator in services responsible to parse seeAlso attribute on entities and add the information.


certificate verify failed with Proxmox 8.0.3 and pm_tls_insecure = true

My Terraform script was working fine, then I upgraded Proxmox from 7.4 to 8.03, and now started to fail.
I have been using from day 1 -> pm_tls_insecure = true
Error looks like this:
Error: error creating VM: 596 error:0A000086:SSL routines::certificate verify failed, error status:  (params: map[agent:0 args: bios:seabios boot: cores:7 cpu:host description: hotplug:network,disk,usb ide2:local:iso/talos-v1.4.6.iso,media=cdrom kvm:true machine: memory:15360 name:vm-k8s-3x-15gigmem-1 net0:virtio=02:49:6F:F7:AC:FE,bridge=vmbr0 numa:false onboot:true ostype:other scsihw:lsi serial0:socket sockets:1 startup: tablet:true tags: virtio0:local-lvm:100 vmid:103])
│
│   with proxmox_vm_qemu.vm["1"],
│   on main.tf line 68, in resource "proxmox_vm_qemu" "vm":
│   68: resource "proxmox_vm_qemu" "vm" {

Same over a year later. Any pointers?


Merge updates to slurm plugin

[ ] I have added the tests to cover my changes.
[x] I have updated the documentation, VERSION, and CHANGELOG accordingly.
[ ] I have read the CONTRIBUTING document.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: Emmanuel289:x: cjaoYou have signed the CLA already but the status is still pending? Let us recheck it.


Middleware for Web3.py

When calling certain function & properties in web3.py, python developers aren’t allowed access. I talked to some of the web3.py developers and they say a middleware is needed. A middleware for POA has been created. Would anybody be able to assist in creating a middleware for GoChain in Web3.py?

@brockmcblockchain you know python, thoughts on this?
@CoreytMayweather what data are you trying to get specifically?

Do we know the specific error that is occurring? The block headers are 99% the same, and the only differences would be on epoch blocks IIRC (which are very rare).
Is it possible that the code is calling blocked methods on the public proxy?

It's also possible that the existing Rinkeby middleware could be used as-is.

I'll put a few minutes into this and whip up a demo.  I used web3.py without issues but I don't know what functions we're trying to access.  Can we have an example to test against for an acceptance test?

Trying to get node version via "w3.version.node",  syncing data using w3.eth.syncing and trying to assign default accounts using the w3.eth.defaultaccount methods. all give me this exact screen

Also this is at the bottom page of Middleware, maybe applies to Gochain also?

All of those methods only make sense when talking to a local node, are you trying to connect to a local node or to our RPC endpoints?

Ok thanks @treeder


feat: Add Gator Oscillator

Description

Add Gator Oscillator.

Checklist

[x] My code follows the existing style, code structure, and naming taxonomy
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have performed a self-review of my own code and included any verifying manual calculations
[x] I have added or updated unit tests that prove my fix is effective or that my feature works, and achieves sufficient code coverage.  New and existing unit tests pass locally and in the build (below) with my changes
[x] My changes generate no new warnings and running code analysis does not produce any issues
[x] I have added or run the performance tests that depict optimal execution times
[x] I have made corresponding changes to the documentation

Is there test for Gator with Alligator?

Default Gator simple uses Alligator with default params, so it’s covered here:
https://github.com/DaveSkender/Stock.Indicators/blob/d87bf98feb3aa5eb4f0685791d61523839f102d4/tests/indicators/e-k/Gator/Gator.Tests.cs
A user can do something like:
// with custom Alligator configuration
IEnumerable<GatorResult> results = quotes
  .GetAlligator([see Alligator docs])
  .GetGator();

As long as Gator and Alligator are independently tested, that’s all we need, right?  I could be wrong.

Ah it makes sense.


Payment Allocation 2 way sync bug, Opportunity level allocation change updates payment level allocation incorrectly

Critical Changes
Changes
Issues Closed
New Metadata
Deleted Metadata

@KietTruongSFDO - I had to close this so we could delete payment-allocations-sync branch.  Please recreate your pull request against master.


NOT NECESSARILY A ISSUE ON YOUR END

Hi, sorry to bother you again, Im having issues with questions 4 and 5 for the calculator lesson, the program gives me one answer, but the correct one is completely different could you possibly look at my code and advise me what I could be doing wrong?
Here is number 4s:
selma = 9-5*(3-4)/6-2
print(selma)
I dont know the proper way to format number 5. :((

That long bar implies grouping, so you need parentheses in the denomator:
 9 - 5*(3-4)/(6-2)

Oops, and the numerator (9 - 5*(3-4)) / (6-2)

disregard the question about the top one with the decimals. still have questions about that bottom one if you dont mind

thank you! 💯


EmbeddedEventLoop + .submit + .wait in tests with Vapor

Expected behavior
Tests to run normally.
Actual behavior
Tests pause and wait on line where .wait() is called
Steps to reproduce

Create a method taking Worker as argument and use worker.eventLoop.submit
Create test using EmbeddedEventLoop as worker and call that method with try and .wait()
Run test
Observe test never finishes and the closure passed to .submit() is never called

SwiftNIO version/commit hash
1.9.5 | 5d8148c8b45dfb449276557f22120694567dd1d2
Swift & OS version
Apple Swift version 4.2 (swiftlang-1<IP_ADDRESS> clang-1<IP_ADDRESS>)
Target: x86_64-apple-darwin17.7.0
Darwin czsfpgspri16fad.local 17.7.0 Darwin Kernel Version 17.7.0: Thu Jun 21 22:53:14 PDT 2018; root:xnu-4570.71.2~1/RELEASE_X86_64 x86_64

Unfortunately this expected behaviour.
EmbeddedEventLoop does not spawn a new thread to run tasks on the event loop. Instead, it runs tasks when you call run or advanceTime(by:). This is mostly for testing purposes, allowing you to create fully deterministic tests.
This means that wait, called on the same thread that created the EmbeddedEventLoop, will create a deadlock. This deadlock cannot be resolved without violating the thread-safety of the EmbeddedEventLoop. As a rule, you must not call wait when using EmbeddedEventLoop.


chore(updatecli) track terraform providers with native updatecli reso…

Since updatecli v0.60.0, there are a new native resource available to track terraform providers from the hashicorp registry to the terraform lock files.
This PR fixes the broken updatecli builds of this repository and switches to native terraform resources which includes:

Cleaning up the list of providers (versions.tf), removing unused providers
One manifest per provider is added
Removed the "all in one" updater and the former script
No need to use a custom hashicorp agent image to execute updatecli as it's native in updatecli now (no docker, no terraform required)

Result of updatecli diff:

2023-09-23T12:51:27.440Z] Run Summary
[2023-09-23T12:51:27.440Z] ===========
[2023-09-23T12:51:27.440Z] Pipeline(s) run:
[2023-09-23T12:51:27.440Z]   * Changed:	4
[2023-09-23T12:51:27.440Z]   * Failed:	0
[2023-09-23T12:51:27.440Z]   * Skipped:	0
[2023-09-23T12:51:27.440Z]   * Succeeded:	0
[2023-09-23T12:51:27.440Z]   * Total:	4

Result of the production plan check: No changes. Your infrastructure matches the configuration.

Self merging:

I want to test the full lifecycle of this new updatecli resource to see if the resulting new PR are doing what we expect without failing checks
No changes and checks output are ok.

If it works, I'll start opening PRs on other terraform project with the same kind of change BUT I won't automerge these other ones.


Adding environment variables breaks startup process?

After adding environment variables for SMTP and saving the changes I'm not facing an infinite loop of failures to start this image:
Jun 20 20:59:45 systemd Started GitLab.service.
Jun 20 20:59:45 docker Status: Image is up to date for centurylink/gitlab:7.3.0
Jun 20 20:59:46 docker Creating SSH2 RSA key; this may take some time ...
Jun 20 20:59:46 docker Creating SSH2 DSA key; this may take some time ...
Jun 20 20:59:46 docker Creating SSH2 ECDSA key; this may take some time ...
Jun 20 20:59:46 docker Creating SSH2 ED25519 key; this may take some time ...
Jun 20 20:59:47 docker invoke-rc.d: policy-rc.d denied execution of restart.
Jun 20 20:59:48 docker sed: -e expression #1, char 18: unknown option to `s'
Jun 20 20:59:48 systemd GitLab.service: main process exited, code=exited, status=1/FAILURE
Jun 20 20:59:48 docker Error response from daemon: No such container: GitLab
Jun 20 20:59:48 docker time="2015-06-20T18:59:48Z" level="fatal" msg="Error: failed to stop one or more containers"
Jun 20 20:59:48 systemd Unit GitLab.service entered failed state.
Jun 20 20:59:48 systemd GitLab.service failed.
...

Seems that the relevant line is:
Jun 20 20:59:48 docker sed: -e expression #1, char 18: unknown option to `s'

as after removing the strange characters ("%-.") from the SMTP_PASS environment variable, the container started without any problem, even though it still printed the invoke-rc.d: policy-rc.d denied execution of restart. message.
Before getting it to work, I had to rename the container to Gitlab_2 as I was also getting an error that there was a Gitlab container already, even though the only one is itself. Seems that somewhere there are references of old container versions that are not being removed...

@andredasilvapinto Some characters need to be escaped in bash. It is not possible to handle such cases in the scripts. Best I found is avoid using &, %, /, etc. characters that mess with command line.
Use docker ps -a to list all running and stopped containers. Remove the stopped containers that you don't need docker rm -f gitlab. You cannot name two containers the same (includes stopped containers).

Thanks for your reply.
Regarding the duplicated names, yes that was the reason, but that should have been dealt with by Panamax. I just changed an environment variable and said to restart the application, there was only one gitlab container in the Web UI, so I was expecting Panamax to avoid creating duplicated containers - like it usually does - even if the start process of the container breaks. I guess this is probably a Panamax bug though.


Patch 36

fix

OPS Build status updates of commit d2b1958:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

dynamics-gp/financials/uk-tax-mtd.md
:white_check_mark:Succeeded
View

dynamics-gp/upgrade/introduction.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Enable parsing text in array key

Hello @rasmusbe,
Parsing is not enabled in array keys. This PR fixes this issue.

Thanks for this PR. I'll merge it right away.

Thanks! Are you planning to release a new tag?

Yes, I'm switching to a new computer right now so as soon as I have the environment up and running again I will release it :)

Thank you :) I’ll keep an eye on updates

Released now as 1.9.7 🎉


Gateway-NodeJS-Prototype

Need to create a basic prototype of backend microservice communication with gateway API

PR merged. closing the issue.


add codein

Fix https://github.com/django-commons/membership/issues/41

No, though I am not sure how to prevent it from showing..

I like the idea for sorting alphabetically


🚀 Feature: Add Global-Agent support to techdocs-cli

🔖 Feature description
Adds the ability to traverse the proxy when using the techdocs-cli
🎤 Context
Connecting to public cloud providers from within a proxied network requires the ability to traverse a proxy. By including global-agent in the dependencies, it allows the techdocs-cli to pick up the proxy configuration and successfully access the public cloud resource.
✌ Possible Implementation
Verified adding global-agent to the dependencies successfully allows connection.
👀 Have you spent some time to check if this feature request has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
Yes I am willing to submit a PR!

Pull Request #16601 to resolve this.

@benjdlambert With the update I made, I published a version of techdocs-cli internally in our organization and then was able to have a pipeline ran that installed that version and successfully did a generate and publish of our docs through our firewall to an AWS account. So, I'm a bit confused as to the connection to the other item, but perhaps I don't understand the other problem well enough.

And one other note for context, this isn't a new problem. We've been managing an internal version of the techdocs-cli for a while to enable this. It just felt silly to manage for basically a one line change that other orgs may benefit from as well. So, that's why I put the PR in.


Timeout parameter for the searchText() function

From<EMAIL_ADDRESS>on February 25, 2011 03:35:51
I think the possibility of providing a timeout parameter for the searchText function could be pretty useful. Right now it is using a timeout constant of 5 seconds. The code that needs to be added or modified would be:
In file Solo.java:
/**
* Searches for a text string and returns {@code true} if at least one item
* is found with the expected text. Will automatically scroll when needed.
*
* @param text the text to search for. The parameter will be interpreted as a regular expression
* @param timeout the time the function is going to wait when looking for the text expressed in miliseconds
* @return {@code true} if the search string is found and {@code false} if it is not found
*
*/
public boolean searchText(String text, int timeout) {
	boolean found = searcher.searchWithTimeoutFor(TextView.class, text, 0, true, false, timeout);
	return found;
}

In file Searcher.java:
/**
 * Searches for a {@code View} with the given regex string and returns {@code true} if the
 * searched {@code Button} is found a given number of times. Will automatically scroll when needed.
 *
 * @param viewClass what kind of {@code View} to search for, e.g. {@code Button.class} or {@code TextView.class}
 * @param regex the text to search for. The parameter \will be interpreted as a regular expression.
 * @param expectedMinimumNumberOfMatches the minimum number of matches expected to be found. {@code 0} matches means that one or more
 * matches are expected to be found
 * @param scroll whether scrolling should be performed
 * @param onlyVisible {@code true} if only texts visible on the screen should be searched
     * @param timeout the time the function is going to wait when looking for the text expressed in miliseconds
 * @return {@code true} if a {@code View} of the specified class with the given text is found a given number of
 * times, and {@code false} if it is not found
 *
 */

public boolean searchWithTimeoutFor(Class<? extends TextView> viewClass, String regex, int expectedMinimumNumberOfMatches, boolean scroll, boolean onlyVisible, int timeout) {
	final long endTime = System.currentTimeMillis() + timeout;

	while (System.currentTimeMillis() \< endTime) {
		sleeper.sleep();
		final boolean foundAnyMatchingView = searchFor(viewClass, regex, expectedMinimumNumberOfMatches, scroll, onlyVisible);
		if (foundAnyMatchingView){
			return true;
		}
	}

	return false;
}

Original issue: http://code.google.com/p/robotium/issues/detail?id=77

From<EMAIL_ADDRESS>on February 25, 2011 03:43:38
Hi,
Please use waitForText() instead. Same behaviour as searchText() but with the possiblity of setting timeout.
/Renas
Status: Invalid


step-ca: re-enable tests on darwin by enabling local networking

Motivation for this change
re-enable tests on darwin by enabling local networking
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

Doesn't doCheck need to be set to true as it's false by default?

AFAIK for buildGoModule the doCheck is set to true by default.

@GrahamcOfBorg test step-ca


Delete Module

Hi
I am missing a delete button somewherw is i would like to remove or delete a module
As creator /owner that would be great
Always with a question "Do you really want to DELETE ?" and some buttons too accept or not ,  with default focus to NO

There is a delete-function, but it is disable at the moment. When you delete a module, there are a lot of consequences to consider. Should we automatically delete the station if the module is a station, or require you to delete the station first? If the module is submitted to a meeting, should you be able to delete it then? Should we analyse the consequences and let you know?
Deleting a module is not just deleting a module, there will be cascading deletes in a number of tables, and some of the relations should block deletes and other should just cascade delete. So it is complex, and there will be NO undo-button.

The idea is that you may delete a module under the following conditions:

The module is 100% owned by you.
The module has no reference to a station
The module is not submitted to any upcoming meetings.

Implemented in release 1.0.5.


fraction bar too high in tonicdev integration

https://tonicdev.com/nicole/katex

My guess is that one of the styles from outside of the katex container is bleeding in.

Very strange. I can't find any styles that are being changed in the frame, but I remember seeing something like this before on android. Probably needs more investigation.

This seems unrelated to Tonic, it reproduces in a normal plain html file for me:

I can open a new bug "fractions are broken" if you prefer.

Missing DOCTYPE?

Is HTML5 a requirement? If it is I'm happy to consider it fixed as missing doctype.

Not HTML5 necessarily, but we probably don't work great in quirks mode. Any valid doctype should work (though <!DOCTYPE html> is of course the shortest). Does that fix it?

Yup, pushing a fix to tonic now. Thanks!

Sweet. We should add a warning for this though. (jQuery doesn't support quirks mode, for instance.)

We do have a warning for it! https://github.com/Khan/KaTeX/blob/master/katex.js#L33

Yeah the problem here is that that warning doesn't happen on the client if its rendered on the server (which is what was happening here). It'll actually be kind of a common case if you do lots of server rendering of stuff as opposed to relying on it coming in on the client.

Ahh, gotcha.


endAngle is ignored after updated to 1.4.2

Please provide the current version of the library you are using

Version = 1.4.2

Have you read the documentation?

[x] Yes
[ ] No

Bug
I was using the library with startAngle = 45 and endAngle = 270 to have a progress view in the non-complete fraction of a circle.
After updating to 1.4.2, my circles are now complete instead of a 62.5% fraction of a circle.
The startAngle seems to still be functioning, but whatever the value of my endAngle, The circle remains complete.

This is due to a new property, fullCircle
Please read the change log


code block inside ListItem in BulletedList

CodeBlock
// empty at all
Paragraph
some text

If this is meant to be a bug report, I don't understand it.

How can i get code block inside ListItem? Not all document:
example:

some question + code?

static dispatch_once_t onceToken = 0;

other question?

output look like: ListItem, codeBlock, ListItem. But I want codeBlock inside list Item as child

The code block needs an extra 4 spaces of indentation. This is standard markdown.
* A

    ```
code
```

* B

A

code

* B

Thanks!!!


Out of date documentation?

I am unable to find the CreateGremlinQuery method on the DocumentClient object as shown in the example in this document. The new way seems to be to use the GraphExtensions.CreateGremlinQuery method instead. If that's correct, then please update the documentation as it is very hard for beginners to be successful at using the Graph capabilities of CosmosDB.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: c5192394-5028-f577-e382-14c126b39ab1
Version Independent ID: 6e908eec-b16a-b09e-bf4a-4b982c804337
Content: Azure Cosmos DB: Develop with the Graph API in .NET
Content Source: articles/cosmos-db/tutorial-develop-graph-dotnet.md
Service: cosmos-db
GitHub Login: @LuisBosquez
Microsoft Alias: lbosq

@sunilab
Thanks for the feedback! We are currently investigating and will update you shortly.

@sunilab I have assigned the issue to the content author to evaluate and update as appropriate.

@sunilab Thanks for your feedback, this tutorial uses, Microsoft.Azure.Graphs library, and we are in the process of deprecating the library and the associated docs. We recommend you to use the Gremlin.Net opensource library as documented in this quickstart: https://docs.microsoft.com/en-us/azure/cosmos-db/create-graph-dotnet . The doc also has a sample that should help you.

#please-close


Still getting the same issue Glue 4 and hudi 0.13 metastore hive error

          Still getting the same issue

Glue 4, Hudi 0.13
An error occurred while calling o616.save.
: org.apache.hudi.exception.HoodieException: Multiple exceptions during meta sync:
Could not sync using the meta sync class org.apache.hudi.hive.HiveSyncTool
Could not sync using the meta sync class org.apache.hudi.aws.sync.AwsGlueCatalogSyncTool
But working fine with hudi 0.12
Originally posted by @HarjeetSinghGoldy in https://github.com/apache/hudi/issues/9134#issuecomment-1711918641

@HarjeetSinghGoldy I checked, it will be working fine with 0.14.0. Can you try with master or 0.14.0-rc1 ? 0.14.0 will be out soon.

Sure !!!
From where i can get a jar of 0.14.0-rc-1 jar???

getting this error while creating jar from master

@HarjeetSinghGoldy You should use java 8 to build the jar.

@HarjeetSinghGoldy Did you got a chance to build theta again?

@HarjeetSinghGoldy Closing out this issue. Please reopen in case of any concerns. Thanks a lot.

Sorry for not getting back to you sooner, I have tried Java 8 but still getting some issues while building jars.
We can close this for now, will open in future when I get back to the same thing.


Update get_coding_ssm to load variants from latest results

get_ssm_by_sample has recently been updated to load variants from the latest and greatest deblacklisted MAFs. We definitely need to update all other functions that get ssms to load from the same files or their derivatives. The most important one is get_coding_ssm. I've created the .CDS derivative files for the files that are loaded by get_ssm_by_sample so this should be relatively easy to adopt into the other functions by pointing them to these new files.

It's VERY important that the new functions all have the same functionality to drop variants with low read support and the same default as the new function. This is because the augmented MAFs can contain variants with even zero supporting reads in that sample due to their detection in another sample from the same patient. For many applications those definitely should not be present but for some applications they're needed.

Other affected functions that need to be updated accordingly are:

get_ssm_by_region
get_ssm_by_gene
get_coding_ssm_status

we also need to check that any function that calls these still works with the updated version, e.g.
calc_mutation_frequency_sliding_windows
get_ssm_by_regions
etc

This issue was resolved in PR https://github.com/morinlab/GAMBLR/pull/71


Tries to recreate the entire database from scratch when generating between db/schema.json and tables.go

To duplicate this issue:
All scripts are run in the main directory of the repo

Setup the empty Postgres db using the docker compose in the repo and then
Run mkdir zz-testing to use for the migrations
Run the following commands

## Command
sqddl generate -src $POSTGRES_URL -dest ddl/testdata/postgres_schema/dest.go.txt -output-dir zz-testing/

## Output
zz-testing/20240913050813_01_schemas.sql
zz-testing/20240913050813_02_tables.sql
zz-testing/20240913050813_03_add_bar_movie_actor_bar_movie_fkeys.tx.sql
zz-testing/20240913050813_04_add_bar_movie_actor_actor_fkeys.tx.sql
zz-testing/20240913050813_05_add_bar_movie_award_bar_movie_fkeys.tx.sql
zz-testing/20240913050813_06_add_bar_movie_award_actor_fkeys.tx.sql

## Command
sqddl migrate -db $POSTGRES_URL -dir zz-testing/

## Output
BEGIN
[OK]<PHONE_NUMBER>0813_01_schemas.sql (400.208µs)
[OK]<PHONE_NUMBER>0813_02_tables.sql (6.90175ms)
COMMIT
BEGIN
[OK]<PHONE_NUMBER>0813_03_add_bar_movie_actor_bar_movie_fkeys.tx.sql (1.706334ms)
COMMIT
BEGIN
[OK]<PHONE_NUMBER>0813_04_add_bar_movie_actor_actor_fkeys.tx.sql (647.709µs)
COMMIT
BEGIN
[OK]<PHONE_NUMBER>0813_05_add_bar_movie_award_bar_movie_fkeys.tx.sql (693.875µs)
COMMIT
BEGIN
[OK]<PHONE_NUMBER>0813_06_add_bar_movie_award_actor_fkeys.tx.sql (1.163625ms)
COMMIT

## Command
sqddl generate -src $POSTGRES_URL -dest ddl/testdata/postgres_schema/dest.go.txt -output-dir zz-testing/

## Output
zz-testing/20240913050858_01_tables.sql

## Command
sqddl migrate -db $POSTGRES_URL -dir zz-testing/

## Output
BEGIN
[FAIL]<PHONE_NUMBER>0858_01_tables.sql (4.017ms)
ROLLBACK
CREATE TABLE actor (
    actor_id INT NOT NULL GENERATED BY DEFAULT AS IDENTITY
    ,name TEXT

    ,CONSTRAINT actor_actor_id_pkey PRIMARY KEY (actor_id)
);

migrate:<PHONE_NUMBER>0858_01_tables.sql: ERROR: relation "actor" already exists (SQLSTATE 42P07)
exit status 1

I have only tested this using Postgres.

Thanks for bringing this to my attention. The problem was that $POSTGRES_URL has "public" as the current schema whereas ddl/testdata/postgres_schema/dest.go.txt has an empty current schema. So sqddl thinks that those are two different schemas, when they are actually the same. I've changed it such that if dest has an empty current schema, it should follow the src's current schema.

fixed by v0.4.14


Non Persistent selection after changing sort criteria

UI does not retain the selection of the items (chart or dashboard) in the list view after a user changes sort parameters.
Expected results
Selection should persist throughout all the sort parameter changes
Actual results
All selected items change their state back to unselected
https://user-images.githubusercontent.com/57817186/114986649-1b22d180-9e49-11eb-82ad-db378c98451e.mov
How to reproduce the bug

Go to Dashboards from the toolbar
Click on 'Bulk Select' button from the top
Select the dashboard items from the list
Sort by any list parameter (e.g: 'Title', 'Modified by')
Selected items will change their state back to the unselected lists

Environment

superset version: commit# c9a755f25
python version: Python 2.7.16
node.js version: v13.11.0

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[x] I have reproduced the issue with at least the latest released version of superset.
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

This issue has been already fixed and merged to the main branch so please close this ticket


[sntp-clinet] simplify uint64 constants

How about apply the same to SNTP-related code in src/cli/cli.cpp?

@jwhui , I updated the commits. I also added a second commit to remove the UINT32_MAX definition from the toolchain.h (since with this change it will not be used in core anymore).


Add PHP 7.4 to travis build matrix

I will never understand why Travis outright refuses to have "7.4" as the version during the prerelease period. I just don't understand why they want config files that will be broken in the future when 7.4 is stable...

They also do not seem to offer support for PHP under OS X, so hacky/brittle solutions need to be employed. And I still haven't had luck getting the Windows build to pass ...

Excellent progress: OS X builds are passing, and Windows builds are at least running (several legitimate errors and failures are being detected by phpunit tests). Windows tests are outside the scope of this PR, though, so I've set them back to being allowed to fail.


[Vue warn]: The client-side rendered virtual DOM tree

In my  ssr project , there is a warming :
[Vue warn]: The client-side rendered virtual DOM tree is not matching server-rendered content. This is likely caused by incorrect HTML markup, for example nesting block-level elements inside <p>, or missing <tbody>. Bailing hydration and performing full client-side render.

I didn't test it with ssr, so cant guarantee it working.
Will take look, thanks 👍

@justyeh Are you using this with nuxt.js?  doesn't seem to work with the 1.0 rc release

yeh , I have used it, bu it doesn't work with SSR
<EMAIL_ADDRESS>From: joshua Oguche
Date: 2017-08-21 17:08
To: euvl/vue-notification
CC: justyeh; Mention
Subject: Re: [euvl/vue-notification] [Vue warn]: The client-side rendered virtual DOM tree (#11)
@justyeh Are you using this with nuxt.js? doesn't seem to work with the 1.0 rc release
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Hey @joshua1, @justyeh,
Completely forgot about this issue 😭 I have not looked into it yet. If anyone has a bit of free time to make a review of what might be causing problems - i will be very-very happy to review a PR 😄

waiting for this 👍

Hi!
it doesn't work with SSR yet

FYI for people using Nuxt and want to render this component only on client-side:
First, create a plugin /plugins/vue-notification.js
import Vue from 'vue'
import Notifications from 'vue-notification'

Vue.use(Notifications)

Then, add it to your nuxt.config.js
...
  plugins: [
     ...
    { src: '@/plugins/vue-notifications', ssr: false }
     ...
  ],
...

Finally, at thelayout or vue app file, add the notification component inside a no-ssr tag
<template>
  <div>
    <no-ssr>
      <notifications/>
    </no-ssr>
    <nuxt/>
  </div>
</template>

Thanks! Exactly that  tag disable this nasty notification! Works on vue-carousel as well too!


feat: Re-add Gravity Bridge gentx

Description
Re-add the gentx command for the Gravity Bridge that collects also the orchestrator address and the ethereum address.

Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...

[x] included the correct type prefix in the PR title
[x] added appropriate labels to the PR
[ ] added ! to the type prefix if API or client breaking change
[x] targeted the correct branch (see PR Targeting)
[ ] provided a link to the relevant issue or specification
[ ] added a changelog entry to CHANGELOG.md
[ ] included comments for documenting Go code
[ ] updated the relevant documentation or specification
[ ] reviewed "Files changed" and left comments if necessary
[ ] confirmed all CI checks have passed

Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...

[ ] confirmed the correct type prefix in the PR title
[ ] confirmed ! in the type prefix if API or client breaking change
[ ] confirmed all author checklist items have been addressed
[ ] reviewed state machine logic
[ ] reviewed API design and naming
[ ] reviewed documentation is accurate
[ ] reviewed tests and test coverage
[ ] manually tested (if applicable)

MY HERO <3


Add basic auth support via URL

https://github.com/vmw-loginsight/webhook-shims/issues/52

Coverage decreased (-0.3%) to 76.367% when pulling 24b189b4961afeaf84e1b55525f33c1ac84154eb on feature/basicauth into b1fd9529dc4fd9ec9feb0d12075d11b71090f011 on master.


Bottom Nav Bar issue when running Chrome on Android

Just giving this an initial test and when using the new interface using Chrome (v: 109.0.5414.86) on Android (v:11) the bottom of what looks to be all pages are covered up by the bottom navigation bar.  At this time I've not tested any other browsers or OS.  I will do some more testing and update as I go.
Is there any further information that you need to assist in resolving this anomaly.

Can you post a screenshot here + resolution of your screen?

The Phone is an Oppo A9 2020
Screen resolution is 1600x720

The Phone is an Oppo A9 2020
Screen resolution is 1600x720

it's normal it's called responsive design :) layout change according to available space.
The page scroll downs if there's not enough space .
I've removed the scroll inside the box and now extend the box itself as it's more ergonomic on little screen

I can slide the page down, but not enough to see the last two selections.  What you see in the screen shot is the page scrolled down as far as I can go, so I'm only able to view the top of the Developer box, but not the About box at all.
Once there is a new firmware to test, I'll install and test to let you know if you're changes have resolved this issue. Thanks

Thanks I have reprroduced your issue.

@aklnlh it's fixed now with many other things. You can grab new binaries
Have not finished yet to redo all the config forms. I have started to remove all unnecessary save button ( HTPP, MQTT for now )

I've updated and can confirm that the issue is no longer present.
Thanks for your assistance.


card of home page are overlapping

Issue Description
card of home page are still overlapping with each other in tablet size.
()
Are you a Hacktoberfest'21 contributor

[X] Yes, I'am Hacktoberfest'21 contributor

ok @Tanujkanti4441


Default bigtable connection pool size is inconsistent

Default constructing a ClientOptions object and calling ClientOptions::set_connection_pool_size(0) results in different pool sizes despite the documentation claiming both are the default. See here.

Fixed in #3261


Refactoring task

Issue description
Describe your issue in detail here
Do Kays refactoring task

PDF Book: http://silab.fon.bg.ac.rs/wp-content/uploads/2016/10/Refactoring-Improving-the-Design-of-Existing-Code-Addison-Wesley-Professional-1999.pdf
Code Starting Point: https://github.com/gnilkreb/Fowler/tree/c0e1c7a21a5335d7e475c2c795ed77deec37b776
From Last Semester: https://commonplayground.wordpress.com/week-5-refactoring/
Definition Of Ready (DoR)
This issue can be worked on if

[x] a developer is assigned
[x] the issue is labeled
[x] the issue is assigned to the current sprint
- [ ] the issue is estimated
[x] a meaningful title has been set
[ ] the issue is described in detail

This is not even a task relevant to VIGAD...

https://miro.com/app/board/uXjVPQEGXOw=/?moveToWidget=3458764553381313162&cot=14

Everyone left their repo links, added to blogpost


Update to README

What does this PR do?
Added the option DD_DD_URL for using an alternate URL to send metrics to DD.  This is helpful for enterprise orgs that do not have the ability to frequently change or modify outbound internet firewall rules to accommodate the DD ingestion URL.
Motivation
Options missing from docs
Additional Notes

The tests fail because your branch is too old, could you rebase with our master branch and push again please?

Thanks @pulberg. Grabbing this in #3552


chore: jsonfmt securityinsights

Automation for azure-sdk-for-python

Automation for azure-sdk-for-go

Can one of the admins verify this patch?

Automation for azure-sdk-for-java


An error occurred: Policy document must be version 2012-10-17 or greater.

Following the readme for cfs:s3, I tried creating a new custom policy as shown below...
{
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "s3:ListAllMyBuckets",
        "s3:ListBucket"
      ],
      "Resource": "arn:aws:s3:::*"
    },
    {
      "Action": [
        "s3:PutObject",
        "s3:PutObjectAcl",
        "s3:GetObject",
        "s3:GetObjectAcl",
        "s3:DeleteObject",
        "s3:DeleteObjectAcl"
      ],
      "Effect": "Allow",
      "Resource": [
        "arn:aws:s3:::myBucketName/*"
      ]
    }
  ]
}

but I get the error An error occurred: Policy document must be version 2012-10-17 or greater.. I'm new to AWS, how can we resolve the error?

Where are you getting this error?

You need to set the version, like the example below:
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": "s3:ListAllMyBuckets",
      "Resource": "arn:aws:s3:::*"
   },

@vertangelx adding the above will fix your issue.


[rv_core_ibex, dv] V2(S) sign-off

Shortly before finishing writing this I realised I need to factor in this PR as well: https://github.com/lowRISC/ibex/pull/2170 which is not yet merged into Ibex but will be part of the M4 RTL.
I'll do a little delta update to this to take it into account.
Commits since ES
OpenTitan Review commit: b79e491e33
08f19b0ed7 [rtl,rv_core_ibex] Mask off lower bits of mapping address
092400ac01 [rv_core_ibex] Reduce number of PRINCE rounds in ICache for timing
ad5f7b947b Update lowrisc_ibex to lowRISC/ibex@eea2bf0c
8295903d7e [bazel,autogen_hjson] Split C and rust header generation
30d7e787c7 (tag: Earlgrey-PROD-M2-RC5, tag: Earlgrey-PROD-M2) Add the project name to the copyright header
f4c2bb9030 Remove trailing whitespaces
6766fc8a0f [rtl, rv_core_ibex] Add alert assertion for lockstep reset count
b402d1cc7a [rv_core_ibex,lint] Update lint waiver with lockstep reset changes
56399241e7 Revert "[edn] Move prim_edn_req out of prim"
61a237e197 [util/reggen] reverse order of substruct generation
fc8484601e [reggen,hw] Create index parameter for registers windows
ce648ca68e [ipgen.pwrmgr] Change core files to vlnv naming and label as virtual
b2e29a57a1 [rv_core_ibex] Update AscentLint waiver for newly added onehot muxes
818f1fd870 [rv_core_ibex] Connect refgile onehot checker asserts
3b4e36e01c [edn] Move prim_edn_req out of prim
de31bdf1c2 [reggen] Remove the devmode input
963a5006cc [doc] Minor tweak to md sanitisation code
ca2b62b28a [dv, testplan] Replace descr by desc for consistency
1ce014fd67 [hw,ibex,rtl] Change fatal alert to for RW1S register
619ce83526 [rv_core_ibex, sival] Extend rv_core_ibex testplan with SiVal tests
1b16ca2122 [reggen] Add mubi support SWAccess that sets/clears a reg
59f8142826 [doc] Moved badges over to using hosted images
70843207c1 [doc] rv_core_ibex registers and interfaces now use CMDGEN
7688e714e8 [reggen] Add initial support for version and cip_id hjson fields
fbd888eea8 Revert "[reggen] Add CIP_IDs and bump all major versions"
0ba10b3cd3 [reggen] Add CIP_IDs and bump all major versions
4e615dedac [rtl/rv_core_ibex] Fix RTL assertion for CDC
Of these 6 have occurred since the D2S sign-off:
08f19b0ed7 [rtl,rv_core_ibex] Mask off lower bits of mapping address
092400ac01 [rv_core_ibex] Reduce number of PRINCE rounds in ICache for timing
ad5f7b947b Update lowrisc_ibex to lowRISC/ibex@eea2bf0c
8295903d7e [bazel,autogen_hjson] Split C and rust header generation
30d7e787c7 (tag: Earlgrey-PROD-M2-RC5, tag: Earlgrey-PROD-M2) Add the project name to the copyright header
f4c2bb9030 Remove trailing whitespaces
3 of these effect functionality
08f19b0ed7 [rtl,rv_core_ibex] Mask off lower bits of mapping address
092400ac01 [rv_core_ibex] Reduce number of PRINCE rounds in ICache for timing
ad5f7b947b Update lowrisc_ibex to lowRISC/ibex@eea2bf0c
ad5f7b947b is a lowRISC vendoring update and changes it introduces are covered
below. 092400ac01 is covered by existing tests and 08f19b0ed7 is covered by
pending PR https://github.com/lowRISC/opentitan/pull/23532
Of the changes that had occurred at the D2S sign-off only 1ce014fd67 resulted in
a functional change and this is covered by the chip_sw_all_escalation_resets
chip level test. The relevant bit of which had been disabled until 1ce014fd67 fixed the bug, it is
now re-enabled: https://github.com/lowRISC/opentitan/blob/ca6e918cee40e3fe69b76e75b9caaef7023028f8/hw/top_earlgrey/dv/env/seq_lib/chip_sw_all_escalation_resets_vseq.sv#L52
Ibex repository commits
Ibex review commit: lowRISC/ibex@5977d4e3
Ibex ES commit: lowRISC/ibex@1120e8dd
The Ibex core itself is vendored in from the Ibex repository. Changes in that
repository that related to the Ibex RTL also need to be considered. Those
changes that effect RTL files are below:
lowRISC/ibex@5977d4e3 [rtl] Guard against false memory responses for secure configurations
lowRISC/ibex@eea2bf0c [rtl] Expose ICacheScrNumPrinceRoundsHalf parameter
lowRISC/ibex@c1139477 Add missing copyright headers
lowRISC/ibex@27dd6b2e [rtl] Update use of prim_count following port changes
lowRISC/ibex@5a8a1a99 [tracer] Fix reporting of load/store data
lowRISC/ibex@8ec0c6f1 [rtl] Harden lockstep enable against FI
lowRISC/ibex@56413ecf [icache] Disable S&P diffusion layer in memory scrambling
lowRISC/ibex@35bbdb7b [rtl] Fix FI vulnerability in RF
lowRISC/ibex@d097c918 [rtl] Avoid name collision in ibex_pmp.sv
lowRISC/ibex@fe84d64d [verilator] Slight refactor in ibex_tracer to avoid BLKSEQ warning
lowRISC/ibex@bac72d96 [ibex_pmp/lint] Declare functions before using them
lowRISC/ibex@1084ac11 [dv] Add asserts to check alerts for memory integrity failures
Of these 3 have occurred since the D2S sign-off:
lowRISC/ibex@5977d4e3 [rtl] Guard against false memory responses for secure configurations
lowRISC/ibex@eea2bf0c [rtl] Expose ICacheScrNumPrinceRoundsHalf parameter
lowRISC/ibex@c1139477 Add missing copyright headers
Only lowRISC/ibex@5977d4e3 has any functional RTL impact. There is no test for
the new security hardening measure it introduces however the functionality it
covers is well exercised by existing tests for normal operating scenarios. A
test should be written to check the new hardening measure.
Of the changes that had occurred at the D2S sign-off lowRISC/ibex@8ec0c6f1 and
lowRISC/ibex@35bbdb7b are security hardening measures which do not have tests
for fault injection, these should be written.
Closed issues
New since D2S sign-off
This issues have been closed since the D2S sign-off

https://github.com/lowRISC/opentitan/issues/22884
RTL bug in address translation (lower bits of remap_addr field should be
ignore), now fixed in
https://github.com/lowRISC/opentitan/pull/23178. The chip level test for
address translation has a pending PR to add junk to the lower bits of
remap_addr to cover this case: https://github.com/lowRISC/opentitan/pull/23532
https://github.com/lowRISC/opentitan/issues/22025

Number of Ibex performance counters reduced to improve area
(https://github.com/lowRISC/opentitan/pull/22047). No DV impact as
we do not test performance counters.

https://github.com/lowRISC/opentitan/issues/21023

V1 signoff for M2
https://github.com/lowRISC/opentitan/issues/20988
D2S sign-off for M2

https://github.com/lowRISC/opentitan/issues/20779

Make lockstep enable multi-bit encoded, usage covered by existing tests
No test to corrupt enable and observe alert occurs

https://github.com/lowRISC/opentitan/issues/19782

Timing fix with rv_core_ibex RTL impact was reducing the number of
scrambling rounds in ICache memory. Existing testing already covers this

https://github.com/lowRISC/opentitan/issues/12777

Decision was not to enable branch predictor, no DV impact

Closed at D2S sign-off
These were also closed at the D2S sign-off and the comments there suffice for the
V2S signoff

https://github.com/lowRISC/opentitan/issues/21461
https://github.com/lowRISC/opentitan/issues/21128
https://github.com/lowRISC/opentitan/issues/20715
https://github.com/lowRISC/opentitan/issues/20700
https://github.com/lowRISC/opentitan/issues/19774
https://github.com/lowRISC/opentitan/issues/11403

Open issues
Earlgrey relevant

https://github.com/lowRISC/opentitan/issues/22684
V3 signoff, not yet achieved
https://github.com/lowRISC/opentitan/issues/22647
D3 signoff, not yet achieved
https://github.com/lowRISC/opentitan/issues/20453
Minor documentation issue
https://github.com/lowRISC/opentitan/issues/18421
Still work to do to improve pass rates, but no concerns with current failures
https://github.com/lowRISC/opentitan/issues/15427
Not done, though this area is already covered by chip-level tests and
assertions. Extra coverage would bring limited value
https://github.com/lowRISC/opentitan/issues/11794
Integrating Ibex regressions into dvsim based flow, not required for M4 or
V2S
https://github.com/lowRISC/opentitan/issues/8945
Software/tooling related

Darjeeling specific

https://github.com/lowRISC/opentitan/issues/20896
https://github.com/lowRISC/opentitan/issues/20489

Tagged as future release

https://github.com/lowRISC/opentitan/issues/18093
https://github.com/lowRISC/opentitan/issues/14510
https://github.com/lowRISC/opentitan/issues/1867

Follow-up

https://github.com/lowRISC/opentitan/issues/21460

Implemented?

https://github.com/lowRISC/opentitan/issues/16838

Implemented?

Ibex repository issues
A detailed review of issues in the Ibex repository has not been conducted due to
the large number of issues, most of which are not relevant to OpenTitan. A brief
review has been conducted and issues of note are blow
Open Issues
(Issues opened within the last year have been looked at only)

https://github.com/lowRISC/ibex/issues/2057
PoR value of all CSRs should be checked, not a major concern for M4/V2S
https://github.com/lowRISC/ibex/issues/2053
Inefficient test that requires many iterations to hit certain bins, not a
major concern for M4/V2S

Closed issues

https://github.com/lowRISC/ibex/issues/2054
Bad PoR value for mstatus, now fixed

Regression Results
The latest Ibex regression result (which was against the reviewed commit lowRISC/ibex@5977d4e3) is available at: https://ibex.reports.lowrisc.org/opentitan/ibex-regr-report-06-06-2024.html
Overall pass rate is 92.7%, coverage results are:

Functional
Block
Branch
Statement
Expression
Toggle
FSM
Assertion

93.7%
95.7%
90.3%
95.8%
90.5%
97.3%
100.0%
98.1%

These maintain V2(S) standards.
A representative regression result for ES is https://ibex.reports.lowrisc.org/opentitan/ibex-regr-report-10-05-2023.html (run against ES commit lowRISC/ibex@1120e8dd)
Overall pass rate was 93.3%, coverage results were:

Functional
Block
Branch
Statement
Expression
Toggle
FSM
Assertion

93.6%
94.6%
90.5%
94.6%
91.4%
96.6%
100.0%
98.1%

So coverage has remained very similar to ES.
Failures between the two sets of results have been compared and there are no new signatures in the latest regression.
Summary
Some new minor security hardening features have been added that should be
covered by a test that checks a fault injection triggers an assert:

lowRISC/ibex@8ec0c6f1
lowRISC/ibex@35bbdb7b
lowRISC/ibex@5977d4e3

lowRISC/ibex@8ec0c6f1 and lowRISC/ibex@35bbdb7b utilize existing primitives that are well tested, so only the connectivity that triggers the alert would be an area of concern.
lowRISC/ibex@5977d4e3 relates to Ibex specific micro-architectural concerns so doesn't use standard countermeasures, however the security issue it relates to (https://github.com/lowRISC/ibex/issues/2144) is of low concern and had a software workaround. It has been observed working correctly in ad-hoc testing.
Tests should be written here but I think there's low risk of undiscovered issues so don't think it should gate M4.
Other than these missing tests there is nothing else that would effect V2(S) status.
I feel it would be appropriate to maintain V2(S) here with a waiver that these tests will be written.

Realised I left two issues under 'follow-up', they're SiVal test tracking issues, just wanted to check what their current status is as it wasn't clear from the issue

Delta report with most recent PR now merged:
Review commit: lowrisc/ibex@d019dccb4b
New commits:

lowrisc/ibex@d019dcc

DV only change, fixing lint

lowrisc/ibex@957529c

Add new RTL to fusesoc core files required due to changes below

lowrisc/ibex@21da9b3

Vendor in latest OT IP

lowrisc/ibex@5cea5d6

Wire up new alert port from prim_ram_1p_scr

lowrisc/ibex@0b0b010

Add new ports from latest prim_ram_1p_scr (outputs which aren't used in Ibex)

The new prim_ram_1p_scr has new security hardening that uses MUBI encoding for various internal signals: https://github.com/lowRISC/opentitan/commit/856e402f740d40dbdb06013320f1697670154fc0 which these commits introduce into Ibex.
These internal signals will be well exercised by existing Ibex testing (as well as being tested elsewhere in OpenTitan). One gap is the need for a test to inject faults and check for an alert from the new hardening. As with the other coverage gaps around countermeasures discussed above I think this is minor enough that we can consider it waived for V2(S) and should not gate M4, but should be completed for M5.

I've read through the analysis and I think I agree. A "short-term" thing that might be worth doing is to spec out the tests you describe and add them to the testplan. That way, we'll have obviously visible gaps (that we can waive) and I think everything ends up feeling a bit more robust.
Other than that, I'm happy that the current status be considered V2S.

Just read through this and I'm happy to close this issue once we create another issue under M5 to track:

One gap is the need for a test to inject faults and check for an alert from the new hardening. As with the other coverage gaps around countermeasures discussed above I think this is minor enough that we can consider it waived for V2(S) and should not gate M4, but should be completed for M5.

Do we have to wait for https://github.com/lowRISC/opentitan/pull/23532 to be merged to test https://github.com/lowRISC/opentitan/commit/08f19b0ed76c9f2329d54707e2abd108442a08c7?

Created an issue for the test here: https://github.com/lowRISC/opentitan/issues/23569
Please edit if you think it needs to be captured differently.

A "short-term" thing that might be worth doing is to spec out the tests you describe and add them to the testplan.

As the Ibex testplan pretty much just points at the test list, rather than add dummy/placeholder tests to that (that then need to be removed from regressions etc) I've added some issues to cover the tests that describe the functionality:

https://github.com/lowRISC/opentitan/issues/23572
https://github.com/lowRISC/opentitan/issues/23573
https://github.com/lowRISC/ibex/issues/2175
https://github.com/lowRISC/ibex/issues/2174
https://github.com/lowRISC/ibex/issues/2173

I'll also plan to properly document all of the current failures in the Ibex testbench and explain why they're of low concern, this is tracked by: https://github.com/lowRISC/opentitan/issues/18421

If I understand correctly, the required tests are implemented in the Ibex PRs that you linked above. Of course, they haven't landed yet (nor have they been vendored into OpenTitan). We definitely cannot claim V2S until the required testing has actually landed on this side.
For arguing that the "M4 side of things" is solid enough, I suggest that you get the PRs merged on the Ibex side and (possibly manually) run a regression at your end showing that they work correctly. Maybe do that and take a screenshot? Then the only remaining task for this issue (rather than the M4 milestone) is to do the vendoring update.

@rswarbrick they're not PRs, they're just issues explaining the tests that need to be written (As we don't have an Ibex testplan that exists in the same way as other OpenTitan IPs do so you can't do a doc-only style PR to add un-written tests to the testplan).
There are no outstanding PRs that require merging, the delta report above links the relevant regression. This has been vendored into OpenTitan here: https://github.com/lowRISC/opentitan/pull/23575
Would you prefer we leave this open and just move it to the M5 milestone then? I.e. we don't waive the small gaps (documented by the new issues) for V2(S)?

Ah, I see: sorry for misunderstanding. I guess that if we believe there are tests that should eventually be written and haven't yet been written, we probably shouldn't claim V2S status. Maybe the best thing is to:

Claim V2 (by filing a PR to drop the current V2S to V2 in rv_core_ibex.hjson)
Keep this issue open, but bumped to the M5 milestone
Write some tests :-)

Thanks for putting this together @GregAC . Regarding the currently untested security countermeasures: we do have the chip_sw_rv_core_ibex_lockstep_glitch TLT to test the lockstep countermeasure. I think the easiest thing to do would be extending this test to also cover the other countermeasures.

Here is the PR vendoring Ibex back in once more: https://github.com/lowRISC/opentitan/pull/23937
There are just DV changes, some of them in the RTL files but they are not synthesized. In addition, I also wanted to study Greg's regression report here https://github.com/lowRISC/ibex/issues/2187 and then we can do the sign off.

Alright, I've now reviewed @GregAC 's regression report in https://github.com/lowRISC/ibex/issues/2187 and can confirm that the observed issues are not concerning but rather well understood testbench / co-simulation issues which are in most cases tedious to fix. There was one RTL bug identified which isn't critical and for which a workaround exists, see https://github.com/lowRISC/ibex/issues/2186.
Delta report compared to https://github.com/lowRISC/opentitan/issues/23542#issuecomment-2154629103
Review commit: lowRISC/Ibex@668233699df9ec2a40413e69e0de0a5b10185980
New commits:
lowRISC/Ibex@66823369 [dv] Add spurious responses to memory agent
lowRISC/Ibex@0e0f27ad [dv] Add riscv_ram_intg_test
lowRISC/Ibex@3384bf4c [cosim] Clang lint fix
lowRISC/Ibex@e1f2df24 [ci] Bump co-sim version
lowRISC/Ibex@470b39a2 [dv] Output warning message on problematic MIP changes
lowRISC/Ibex@65a7231a [cosim] Correctly deal with checking top of range memory accesses
lowRISC/Ibex@e784d274 [dv] Update testbench to use new 'pre_val' MIP
lowRISC/Ibex@39648048 [dv] Fix model mismatches in cases where an access crosses PMP regions
lowRISC/Ibex@89f4d867 [dv] Fix exception_stall_instr_cross illegal bins
lowRISC/Ibex@2c132113 [dv] Add riscv_rf_ctrl_intg_test
lowRISC/Ibex@e2b721d4 [ci] update private CI
lowRISC/Ibex@1449ed5e [dv] Add cover points for memory interface behaviour
lowRISC/Ibex@604ba343 [dv] Fix race condition in ibex_mem_intf_agent
lowRISC/Ibex@d97a0b4a [doc] Fix C++ style guide link in README
The commits contain DV and doc changes only, including many fixes to improve test pass rates.
Latest regression is here: https://ibex.reports.lowrisc.org/opentitan/ibex-regr-report-05-07-2024.html
97.1% pass rate, coverage is:

Functional
Block
Branch
Statement
Expression
Toggle
FSM
Assertion

94.3%
95.9%
90.6%
95.9%
90.8%
97.2%
100.0%
98.1%

There have two new signatures been identified:

The first one revealed an possible but uncritical RTL bug for which a workaround exists, for details see lowRISC/Ibex#2186.
The second one is an old testbench / co-simulation bug which was thought to be fixed lowRISC/ibex#1313 - also uncritical.

In OpenTitan, the following commits have been merged in hw/ip/rv_core_ibex since 9f43e67210314c47f7ec991bba4d82f49c281e4c
9a18359abb [rv_core_ibex] Waive uncritical AscentLint errors
There is one oustanding PR to re-vendor Ibex with the latest DV changes here: #23937
In terms of issues the state is as follows:

The issues mentioned in this comment have all been addressed and closed by implementing the additional tests.
#16838 has been moved to M7 as part of V3.
#21460 has been closed as the mentioned test has already been implemented.

Summary
To summarize, the items identified previously to be taken care of before we can sign off Ibex at V2S have all been taken care of. Pass rates have been improved further and the test failures are well understood. The risk of critical RTL bugs is deemed low.
There has one possible bug been identified which is considered uncritical and for which a software workaround exists, see lowRISC/Ibex#2186.
I thus recommend signing of Ibex at V2S once the latest vendor PR #23937 has been merged. What do you think @andreaskurth , @GregAC , @rswarbrick ?

I thus recommend signing of Ibex at V2S once the latest vendor PR #23937 has been merged. What do you think @andreaskurth , @GregAC , @rswarbrick ?

Agreed, thanks for this summary @vogelpi, and thanks @GregAC for your analysis above and all the great work you did on Ibex!

Yep, I agree: Great work from @GregAC , thanks for all this!


Dedupe modules linked by keeping a list of linked names

Prevents linking a module multiple times causing a __ is already used to build a source directory error while building. This assumes that the modules with the same name are the same module and so do not need to be built twice.

The module traversal should never visit the same directory more than once in the first place, so this treats a symptom of an underlying issue rather than the issue itself. It also does so incorrectly as the "same" module may exist multiple times in the module hierarchy, but at different versions. Ultimately, the only place module deduplication should happen is in your package manager.
In the interest of not collectively running our heads against the https://xyproblem.info wall, could you open an issue instead, ideally with a minimal reproduction?

Let me see if I can package up what I have in a branch and I'll open the issue. Thanks @lejeunerenard for trying to solve 🙇

@kasperisager here you go:
https://github.com/holepunchto/pear-expo-hello-world/compare/main...saimonmoore:pear-expo-hello-world:experiment?expand=1
If you check out that branch, you should get the error with bare-pipe and not sure what else I need to remove then.

cc @lejeunerenard

Ah very cool!  Thanks!


SteppedBar plots everything as Scatter when set via getStyler().setDefaultSeriesRenderStyle

When using
chart.getStyler().setDefaultSeriesRenderStyle(CategorySeriesRenderStyle.SteppedBar);

The chart is plotted as if the default render style is Scatter. For a minimal reproducible case (Repro.java):
import java.util.Arrays;
import java.io.FileOutputStream;
import org.knowm.xchart.BitmapEncoder;

import org.knowm.xchart.CategoryChart;
import org.knowm.xchart.CategoryChartBuilder;
import org.knowm.xchart.CategorySeries;
import org.knowm.xchart.CategorySeries.CategorySeriesRenderStyle;

public class Repro {
    public static void main(String[] args) throws Exception {
        CategoryChart chart = new CategoryChartBuilder().width(600).height(450).title("Temperature vs. Color").xAxisTitle("Color").yAxisTitle("Temperature").build();

        CategorySeries[] categorySeries = new CategorySeries[2];
        categorySeries[0] = chart.addSeries("fish", Arrays.asList("Blue", "Red", "Green", "Yellow", "Orange"), Arrays.asList(40, 30, 20, 60, 60));
        categorySeries[1] = chart.addSeries("worms", Arrays.asList("Blue", "Red", "Green", "Yellow", "Orange"), Arrays.asList(50, 10, -20, 40, 60));

        chart.getStyler().setDefaultSeriesRenderStyle(CategorySeriesRenderStyle.SteppedBar);

        FileOutputStream fos = new FileOutputStream("out.png");
        try {
            fos.write(BitmapEncoder.getBitmapBytes(chart, BitmapEncoder.BitmapFormat.PNG));
        }
        finally {
            fos.close();
        }
    }
}

Compile with javac -cp xchart-3.5.0.jar Repro.java and java -cp xchart-3.5.0.jar:. Repro, assuming you have xchart-3.5.0.jar in the same directory. This will emit a PNG image which looks like this:

Replacing the default styler call with calls to manually set SteppedBar works fine, however:
categorySeries[0].setChartCategorySeriesRenderStyle(CategorySeriesRenderStyle.SteppedBar);
categorySeries[1].setChartCategorySeriesRenderStyle(CategorySeriesRenderStyle.SteppedBar);

This was tested on XChart 3.5.0.

EDIT: There are also some strange interactions between the default render style and manual render styles as well. This will also just print in the Scatter style:
chart.getStyler().setDefaultSeriesRenderStyle(CategorySeriesRenderStyle.SteppedBar);
categorySeries[0].setChartCategorySeriesRenderStyle(CategorySeriesRenderStyle.SteppedBar);
categorySeries[1].setChartCategorySeriesRenderStyle(CategorySeriesRenderStyle.SteppedBar);

After some digging, this seems to be an issue with other styles as well. If we use the same code as above and want to print one Scatter and one Bar series, we end up with an ok result here:
chart.getStyler().setDefaultSeriesRenderStyle(CategorySeriesRenderStyle.Bar);
categorySeries[0].setChartCategorySeriesRenderStyle(CategorySeriesRenderStyle.Scatter);

However, if we invert the logic, like so (They should be equivalent):
categorySeries[1].setChartCategorySeriesRenderStyle(CategorySeriesRenderStyle.Bar);
chart.getStyler().setDefaultSeriesRenderStyle(CategorySeriesRenderStyle.Scatter);

We end up with the same issue as mentioned above:

Thanks I'll fix it soon hopefully...

Hey @timmolter
Currently I'm looking into this issue.
I digged into the code and find the code in class Plot_Category like this:
    if (CategorySeriesRenderStyle.Bar.equals(stylerCategory.getDefaultSeriesRenderStyle())
        || CategorySeriesRenderStyle.Stick.equals(stylerCategory.getDefaultSeriesRenderStyle())) {
      this.plotContent = new PlotContent_Category_Bar<ST, S>(chart);
    } else {
      this.plotContent = new PlotContent_Category_Line_Area_Scatter<ST, S>(chart);
    }

It seems that if chart.getStyler().setDefaultSeriesRenderStyle(CategorySeriesRenderStyle.SteppedBar);  was called, the defaultSeriesRenderStyle would be set to SteppedBar, and the code in Plot_Category would process the painting job using PlotContent_Category_Line_Area_Scatter here.
Some questions:

Should we change the code in Plot_Category to let PlotContent_Category_Bar do the painting job when drawing SteppedBar? Is this enough? Sample code here:

    if (CategorySeriesRenderStyle.Bar.equals(stylerCategory.getDefaultSeriesRenderStyle())
        || CategorySeriesRenderStyle.Stick.equals(stylerCategory.getDefaultSeriesRenderStyle())
        || CategorySeriesRenderStyle.SteppedBar.equals(stylerCategory.getDefaultSeriesRenderStyle())) {
      this.plotContent = new PlotContent_Category_Bar<ST, S>(chart);
    }

Actually I have no idea what SteppedBar should be look like as it's only used here. Is PlotContent_Category_Bar working correctly on painting SteppedBar? If not, should we add a new class like PlotContent_Category_SteppedBar to do the job?


Possible to train Llama 3.1?

Hi,
I tried training llama 3.1 with run_mntp.py but get an obsucre error
AttributeError: 'LlamaBiModel' object has no attribute 'rotary_emb'
What is that about ?

I encountered the same issue yesterday while using the Llama 2 model. It started working after I downgraded the transformers to version 4.40.2.

you can check this:
https://github.com/McGill-NLP/llm2vec/pull/127/commits/03382c358494a4e2f07222455b366fb75d625ab7

hmm still not sure what to do...

Hi everyone,
@bzantium thanks for pointing us to the commit. I added the respective lines and used a more recent version of transformers to make it work. MNTP training for Llama 3.1 seems to work now for me. However, I failed to do the MTEB evaluation locally so far, see #123.
Did you make any progress in training Llama 3.1 for LLM2Vec?

@bzantium Thanks i was able to get the embeddings after adding in the lines, haven't been able to train it yet through MNTP but i'll keep on trying

@stefanhgm Once Llama 3.1 (I presume the 8B parameters model) is trained, can you use it for generating images the way ELLA uses t5, with better prompt adherence?

@andupotorac I am not familiar with the ELLA project, but you could use the model to create embeddings just as with the other LLM2Vec models.
However, the eval on MTEB currently hangs #135

Thanks, I will keep an eye on it as well.


Draft: Separation of application and server output

Reason for This PR
[💡 FEATURE REQUEST]: Improve clarity of worker errors when starting a server
Description of Changes
Separation of logs from the application and plugin for their separate configuration. I left comments on the code.
License Acceptance
By submitting this pull request, I confirm that my contribution is made under
the terms of the MIT license.
PR Checklist
[Author TODO: Meet these criteria.]
[Reviewer TODO: Verify that these criteria are met. Request changes if not]

[ ] All commits in this PR are signed (git commit -s).
[ ] The reason for this PR is clearly provided (issue no. or explanation).
[ ] The description of changes is clear and encompassing.
[ ] Any required documentation changes (code and docs) are included in this PR.
[ ] Any user-facing changes are mentioned in CHANGELOG.md.
[ ] All added/changed functionality is tested.

Summary by CodeRabbit

New Features

Introduced a dedicated application logger for improved logging capabilities.
Enhanced separation of application-specific logs from server logs.

Bug Fixes

Updated logging behavior to prevent interference between application and server logs.

Added this repo to the @roadrunner-server/contributors team, so, you won't need to do forks.

@Kaspiman Do you have plans to do something in this PR according our last discussion or it can be closed?

@Kaspiman Do you have plans to do something in this PR according our last discussion or it can be closed?

Yep, I just need some free time in real life...


Seperate tox environments  for Travis

Well that didn't built. This is why we need Travis integration inside PRs :B


Update K to 6.0.108

Outputs of the integration tests test/imp/max-symbolic.imp.out.golden and test/smt-none/program.test.out.golden neede to be updated because of the commit 8200fdb41f268a875044c18dda5dd206e5435d16 to K

Closing on favor of https://github.com/runtimeverification/haskell-backend/pull/3656


Not seeing country flags

Hi there,
I am not seeing the country flags on youtube videos.   I'm on a mac OS X 10.9.5 using Firefox 33.1.
Thanks!

Migrating all issues about country flags not working to one issue, check out issue number "1877".


Create a repository and tickets for Smart Contract Verification Service

Create a repository and tickets for Smart Contract Verification Service

I think I have covered all the issues. The repository for the service is set up in https://github.com/aeternity/smart-contract-verificator
@michele-franchi Let me know if I should make it public right away or upon the production release


Oops! Something went wrong. Please try again later

I keep getting this problem after completing a task. Duplicate user problem?

Closing as a duplicate of #6958. We are aware of the problem and working on it. It's been hard to get to the bottom of. Thanks and happy coding!


Permission Error in Accessing Workspace

After starting the client server the workspaces for my girder user account does not appear and I get the following error message:
Executing GraphQL Request
request: query {
      workspaces { name }
    }
An error occurred while resolving field Query.workspaces
Traceback (most recent call last):
  File "/Users/jen/.local/share/virtualenvs/multinet-girder-NQjY1GFC/lib/python3.7/site-packages/graphql/execution/executor.py", line 450, in resolve_or_error
    return executor.execute(resolve_fn, source, info, **args)
  File "/Users/jen/.local/share/virtualenvs/multinet-girder-NQjY1GFC/lib/python3.7/site-packages/graphql/execution/executors/sync.py", line 16, in execute
    return fn(*args, **kwargs)
  File "/Users/jen/Documents/Github/multinet-girder/multinet/multinet/resolvers/query.py", line 7, in workspaces
    return [workspace for workspace in db.get_workspaces(name) if not name or workspace == name]
  File "/Users/jen/Documents/Github/multinet-girder/multinet/multinet/db.py", line 13, in wrapper
    return fun(*args, **kwargs)
  File "/Users/jen/Documents/Github/multinet-girder/multinet/multinet/db.py", line 48, in get_workspaces
    workspaces = sys.databases()
  File "/Users/jen/.local/share/virtualenvs/multinet-girder-NQjY1GFC/lib/python3.7/site-packages/arango/database.py", line 700, in databases
    return self._execute(request, response_handler)
  File "/Users/jen/.local/share/virtualenvs/multinet-girder-NQjY1GFC/lib/python3.7/site-packages/arango/api.py", line 58, in _execute
    return self._executor.execute(request, response_handler)
  File "/Users/jen/.local/share/virtualenvs/multinet-girder-NQjY1GFC/lib/python3.7/site-packages/arango/executor.py", line 81, in execute
    return response_handler(response)
  File "/Users/jen/.local/share/virtualenvs/multinet-girder-NQjY1GFC/lib/python3.7/site-packages/arango/database.py", line 697, in response_handler
    raise DatabaseListError(resp, request)
arango.exceptions.DatabaseListError: [HTTP 401][ERR 11] not authorized to execute this request
Errors in request: 1
[HTTP 401][ERR 11] not authorized to execute this request
<IP_ADDRESS> - - [17/Jun/2019:12:03:51] "POST /api/v1/multinet/graphql HTTP/1.1" 200 87 "http://localhost:8080/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.90 Safari/537.36"

Along with this - error message from the google chrome devtool console:

I am not providing a password as I assume it would use default password. I get no other errors starting the process aside from the above.
The girder portal shows no workspaces under my account.
Things I have tried so far:
retrying the set up process
logging out of the girder portal and logging in
providing the password with yarn:serve

I think this is a problem of data persistence.
The very first time you launch the Docker container for Arango (using the docker-compose step in the instructions), whatever password is specified--whether the default one, or one you supply--gets baked into the newly created Arango database data. Every subsequent time you launch the container, that password will be used (even if you continue supplying a password through the environment variable).
So, if you try again but launch Girder using the correct password (again, through the environment variable) then it should work. This is ultimately a problem of deployment, so hopefully this hiccup (which I faced myself a few days ago) will sort of go away now that we've shifted how the environment variables and defaults work.

Though now I see that you did say you tried supplying the password with the yarn:serve command. If that didn't work then maybe there's something deeper going on.

@jenrogers1207 and I looked at this more closely and it was indeed a password issue. We solved it by rebuilding the Arango database from scratch, using a new password.


setup multi-arch builds with goreleaser

Description of the change:
Motivation for the change:
Reviewer Checklist

[ ] Implementation matches the proposed design, or proposal is updated to match implementation
[ ] Sufficient unit test coverage
[ ] Sufficient end-to-end test coverage
[ ] Docs updated or added to /docs
[ ] Commit messages sensible and descriptive

Codecov Report

Merging #1 (10bba99) into master (6072760) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master       #1   +/-   ##
=======================================
  Coverage   49.07%   49.07%
=======================================
  Files          96       96
  Lines        8190     8190
=======================================
  Hits         4019     4019
  Misses       3391     3391
  Partials      780      780

Continue to review full report at Codecov.

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


fix: workspace routes integration failed

Description

Issues Resolved

Screenshot

Testing the changes

Check List

[ ] All tests pass

[ ] yarn test:jest
[ ] yarn test:jest_integration
[ ] yarn test:ftr

[ ] New functionality includes testing.
[ ] New functionality has been documented.
[ ] Update CHANGELOG.md
[ ] Commits are signed per the DCO using --signoff

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

Project coverage is 55.30%. Comparing base (089ad04) to head (66febdd).

Additional details and impacted files
@@                   Coverage Diff                    @@
##           workspace-pr-integr     #251       +/-   ##
========================================================
- Coverage                67.02%   55.30%   -11.72%
========================================================
  Files                     3318     1192     -2126
  Lines                    63965    24113    -39852
  Branches                 10255     4050     -6205
========================================================
- Hits                     42871    13336    -29535
+ Misses                   18585    10124     -8461
+ Partials                  2509      653     -1856

Flag
Coverage Δ

Linux_
?

_1
?

_2
55.30% <ø> (ø)

_3
?

_4
?

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

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

@wanglam backport to workspace failed


Fix to calling flash when the request object doesn't support it

In cases, such as a rails api controller ActionController::API, the request object does not have flash capabilities loaded.  The is_flashing_format? should gracefully return false in those cases.
Addresses #4947

Seems good, thanks @colinross!


implementing OAStackViewProxy in Objective-C rather than Swift

This fixes issue #100 but keeps the intent behind OAStackViewProxy.  Also adds an additional tab to the demo app to show the three ways of using it (OAStackView, UIStackView, OAStackViewProxy) with some additional NSLogging to show what's going on.

Looking Cool!


Spherical harmonic data is not saved on export: what does it mean ?

Sorry but does this limitation mean ?

Instead of having just a single colour value, each gaussian splat can have a spherical harmonic instead. A spherical harmonic stores colour values for all directions on a sphere. Individual splats can then be rendered with different colours depending on the direction you're viewing them from. This means the scene can have "view specific" effects, like shiny reflections on car surfaces and windows and puddles etc.
We are currently not loading and saving all the spherical harmonic data because it is large and the results we've seen so far were good enough using just a single colour per splat.
However these are early days and we will most likely be adding support for full spherical harmonics in future!

Closing


enhancement(node_exporter): add vrf var to node_exporter

We're using node-exporter on nvidia switches running cumulus. Within these switches it's mandatory for us to use the node-exporter within a vrf provided via ifupdown2. This is not limited to our usecase but can also be used on a linux vm.
The systemd option ProtectControlGroups is needed for usage of vrf. Without setting the option this error is reported:
Apr 23 14:57:16 test-01 node_exporter[1817356]: mkdir failed for /sys/fs/cgroup/unified/system.slice/node_exporter.service/vrf: Read-only file system
Apr 23 14:57:16 test-01 node_exporter[1817356]: Failed to setup vrf cgroup2 directory

Not sure if this is something you want to support. If not please feel free to close this PR. If something is missing I'm happy to amend changes.
I wasn't sure about your test requirements, if required I'm happy to extend the molecule tests.

This might be a bit too system specific for this role.
Maybe another way to handle this would be to add a systemd overlay like this:
In /etc/systemd/system/node_exporter.service.d/vrf.conf add this:
[service]
ExecStart=...
ProtectControlGroups=false

See the "drop-in" pattern in the systemd docs.

Thanks for the push into the direction of drop-ins, totally forgot about them! If anybody in the future needs this, this is a working example from a cumulus device:
[Service]
ExecStart=
ExecStart=ip vrf exec mgmt runuser -u node-exp -g node-exp -- /usr/local/bin/node_exporter \
    '--web.listen-address=<IP_ADDRESS>:9101' \
    '--web.telemetry-path=/metrics' \
    '--collector.ethtool'\
    '--collector.netdev.netlink'\
    '--collector.systemd'\
    '--collector.textfile'\
    '--collector.textfile.directory=/var/lib/node_exporter'
ProtectControlGroups=false

First empty ExecStart= is needed to overwrite.


feat: helpers for My Collection tracking events

Addresses CX-885.
This PR adds tracking helpers for all events used by the My Collection app in Eigen.
Some adjustments were made to the underlying events according to this conversation: https://artsy.slack.com/archives/C01B2P6LJUU/p1607444872180400
Follow-up work

Update the cohesion dep in Eigen and start using these helpers!

:rocket: PR was released in v1.65.0 :rocket:


Monitor NGINX logs for critical & error messages after NGINX reload

Proposed changes
Monitor NGINX logs for critical & error after an NGINX reload
Checklist
Before creating a PR, run through this checklist and mark each as complete.

[x] I have read the CONTRIBUTING document
[x] I have run make install-tools and have attached any dependency changes to this pull request
[x] If applicable, I have added tests that prove my fix is effective or that my feature works
[x] If applicable, I have checked that any relevant tests pass after adding my changes
[x] If applicable, I have updated any relevant documentation (README.md)
[ ] If applicable, I have tested my cross-platform changes on Ubuntu 22, Redhat 8, SUSE 15 and FreeBSD 13

Codecov Report
Patch coverage: 84.00% and project coverage change: +0.29 :tada:

Comparison is base (0e16af7) 67.26% compared to head (2ec0afa) 67.56%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #385      +/-   ##
==========================================
+ Coverage   67.26%   67.56%   +0.29%
==========================================
  Files         113      113
  Lines       12743    12695      -48
==========================================
+ Hits         8572     8577       +5
+ Misses       3601     3550      -51
+ Partials      570      568       -2

Impacted Files
Coverage Δ

src/core/message.go
100.00% <ø> (ø)

src/core/network/network.go
31.48% <ø> (+0.21%)
:arrow_up:

src/core/os.go
42.85% <0.00%> (ø)

...ed-metrics/tables/priority_table/priority_table.go
77.27% <ø> (+4.54%)
:arrow_up:

...b.com/nginx/agent/v2/src/core/metrics/aggregate.go
88.29% <ø> (-0.25%)
:arrow_down:

.../agent/v2/src/core/metrics/collectors/container.go
90.69% <ø> (ø)

...inx/agent/v2/src/core/metrics/collectors/system.go
92.85% <ø> (+5.35%)
:arrow_up:

...t/v2/src/core/metrics/sources/cgroup/cgroup_cpu.go
83.87% <ø> (-0.13%)
:arrow_down:

...com/nginx/agent/v2/src/core/metrics/sources/cpu.go
76.31% <ø> (-0.61%)
:arrow_down:

...om/nginx/agent/v2/src/core/metrics/sources/disk.go
69.56% <ø> (-1.27%)
:arrow_down:

... and 31 more

... and 5 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


fix libusb deprecation. fix #703

Looks good, seems the continuous integration of the linux and macosx builds is happy. Now wait for @LeisureLadi to verify.


Add manifests in release bundle

Currently the release contains the binaries but not the manifests you can find in config with references to pre-built public images.
We should publish a all in one manifest that people can kubectl apply

@sameersbn since we use docker (kaniko more precisely) and not ko to perform image releases (unlike Knative), maybe it would be sufficient to concatenate all manifests from config/ and perform the necessary string replacements ko:// -> <actual image> when we press the release button. WDYT?

concatenate all manifests from config/ and perform the necessary string replacements ko:// -> <actual image>

yea, that makes sense

@sameersbn can we get this done


Authentication with SSH Server on OSX is failing

https://github.com/chef/inspec/issues/788

https://github.com/chef/train/issues/112


Update overview.md - managed identity page

Changed the word "ideantity" to "identity"

@lorrinferdinand : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Thanks for the typo fix, @lorrinferdinand!

Thanks for the typo fix, @lorrinferdinand!

Thanks for the typo fix, @lorrinferdinand!


Design issues

Design of Login/Register page needs to be like the rest of the site
Design of verifyEmail/VerifiedEmail

fixed in #18


using COALESCE when making an index, escapes the comma in the function

This is what I expect to get:
CREATE UNIQUE INDEX "IndexName" ON "Table" ("foo", COALESCE ("bar", ''));

This is my schema definition:
uniqueIndex("IndexName").on(table.foo, sql`COALESCE(${table.bar}, '')`)

The comma in COALESCE get escaped:
CREATE UNIQUE INDEX `IndexName` ON `Table` (`foo`,`COALESCE("bar"`,` '')`);

This is for the sqlite dialect with:
drizzle-orm: 0.31.2
drizzle-kit: 0.22.6

should not be an issue on latest(0.30.0+), if it's still an issue - please reopen


False positive: hardlinked -> hardline

oh thats bad.

Hello. Has there been any progress fixing this? There's been no activity for almost 2 years.
I would send a PR for words.go but apparently the code is generated automatically and I don't see where the code generator DB is.


Markers wiggle on React 18

Reproducible by upgrading React version of website example to version 18
Before (React 17):
https://user-images.githubusercontent.com/10248395/178124854-0de1e9bc-7e79-48ee-8a57-37c2c3dd8ad3.mov
After (React 18):
https://user-images.githubusercontent.com/10248395/178124860-bec3d0be-b9fe-410c-b538-9d28a0f64982.mov

+1 to this. Thanks for the videos.

1 to this, any one know how to fix this issue?

@agusterodin Have you fixed this prolem?

Because React 18 events is auto batching state update, you guys can fork this repo and put flushSync to map 'move' event in ProjectedLayer component

Is there any interest in making this part of the repo here instead of having to clone and go that way?

Hi @nickpolet . I created 2 files and use the Marker component instead of forking


Support negative numbers as value

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

19 of 34 (55.88%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.2%) to 89.662%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/parser.rs
5
6
83.33%

src/ast/value.rs
3
17
17.65%

Totals

Change from base Build<PHONE_NUMBER>:
-0.2%

Covered Lines:
5924

Relevant Lines:
6607

💛  - Coveralls

hello @sundy-li .don't i need to modify this?

hello @sundy-li .don't i need to modify this?

You can modify the git version of sqlparser  crate in databend in your pr to verify datafuselabs/databend#3197

ok

I edit two file: common/exception/Cargo.tom, query/Cargo.tom.
in my number type stateless both ok.
select toTypeName(a) from (select 42 as a);
select toTypeName(a) from (select -1 as a);
select toTypeName(a) from (select -128 as a);
select toTypeName(a) from (select -32768 as a);
select toTypeName(a) from (select -2147483648 as a);
select toTypeName(a) from (select -9223372036854775808 as a);
select toTypeName(a) from (select 255 as a);
select toTypeName(a) from (select 65535 as a);
select toTypeName(a) from (select<PHONE_NUMBER> as a);
select toTypeName(a) from (select<PHONE_NUMBER>3709551615 as a);
select toTypeName(a) from (select<PHONE_NUMBER>370955161522 as a);

but 02_0014_function_maths happen error, nohup.out:
[2021-12-05T12:57:00Z ERROR databend_query::servers::mysql::mysql_session] Unexpected error occurred during query execution: Code: 10, displayText = Unsupported column type:UInt16(while in query SELECT abs(-10086)).

       0: backtrace::backtrace::libunwind::trace
                 at /Users/kous/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.63/src/backtrace/libunwind.rs:93:5
          backtrace::backtrace::trace_unsynchronized
                 at /Users/kous/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.63/src/backtrace/mod.rs:66:5
          backtrace::backtrace::trace
                 at /Users/kous/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.63/src/backtrace/mod.rs:53:14
       1: backtrace::capture::Backtrace::create
                 at /Users/kous/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.63/src/capture.rs:176:9
          backtrace::capture::Backtrace::new
                 at /Users/kous/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.63/src/capture.rs:140:22
       2: common_exception::exception::ErrorCode::BadDataValueType
                 at common/exception/src/exception.rs:113:77
       3: databend_query::servers::mysql::writers::query_result_writer::DFQueryResultWriter<W>::ok
                 at query/src/servers/mysql/writers/query_result_writer.rs:174:48
       4: databend_query::servers::mysql::writers::query_result_writer::DFQueryResultWriter<W>::write
                 at query/src/servers/mysql/writers/query_result_writer.rs:40:45
       5: <databend_query::servers::mysql::mysql_interactive_worker::InteractiveWorker<W> as msql_srv::MysqlShim<W>>::on_query
                 at query/src/servers/mysql/mysql_interactive_worker.rs:167:40
       6: msql_srv::MysqlIntermediary<B,R,W>::run
                 at /Users/kous/.cargo/git/checkouts/msql-srv-62b5153e0120bb3a/e4c8f3d/src/lib.rs:528:25
       7: msql_srv::MysqlIntermediary<B,R,W>::run_on
                 at /Users/kous/.cargo/git/checkouts/msql-srv-62b5153e0120bb3a/e4c8f3d/src/lib.rs:308:9
       8: msql_srv::MysqlIntermediary<B,std::net::tcp::TcpStream,std::net::tcp::TcpStream>::run_on_tcp
                 at /Users/kous/.cargo/git/checkouts/msql-srv-62b5153e0120bb3a/e4c8f3d/src/lib.rs:274:9
       9: databend_query::servers::mysql::mysql_session::MySQLConnection::session_executor
                 at query/src/servers/mysql/mysql_session.rs:44:29
      10: databend_query::servers::mysql::mysql_session::MySQLConnection::run_on_stream::{{closure}}
                 at query/src/servers/mysql/mysql_session.rs:35:13
      11: common_base::thread::Thread::spawn::{{closure}}
                 at common/base/src/thread.rs:32:17
      12: std::sys_common::backtrace::__rust_begin_short_backtrace
                 at /rustc/6db0a0e9a4a2f55b1a85954e114ada0b45c32e45/library/std/src/sys_common/backtrace.rs:123:18
      13: std::thread::Builder::spawn_unchecked::{{closure}}::{{closure}}
                 at /rustc/6db0a0e9a4a2f55b1a85954e114ada0b45c32e45/library/std/src/thread/mod.rs:484:17
      14: <core::panic::unwind_safe::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once
                 at /rustc/6db0a0e9a4a2f55b1a85954e114ada0b45c32e45/library/core/src/panic/unwind_safe.rs:271:9
      15: std::panicking::try::do_call
                 at /rustc/6db0a0e9a4a2f55b1a85954e114ada0b45c32e45/library/std/src/panicking.rs:406:40
      16: <unknown>
                 at /rustc/6db0a0e9a4a2f55b1a85954e114ada0b45c32e45/library/std/src/panicking.rs:434:6
      17: std::panicking::try
                 at /rustc/6db0a0e9a4a2f55b1a85954e114ada0b45c32e45/library/std/src/panicking.rs:370:19
      18: std::panic::catch_unwind
                 at /rustc/6db0a0e9a4a2f55b1a85954e114ada0b45c32e45/library/std/src/panic.rs:133:14
      19: std::thread::Builder::spawn_unchecked::{{closure}}
                 at /rustc/6db0a0e9a4a2f55b1a85954e114ada0b45c32e45/library/std/src/thread/mod.rs:483:30
      20: core::ops::function::FnOnce::call_once{{vtable.shim}}
                 at /rustc/6db0a0e9a4a2f55b1a85954e114ada0b45c32e45/library/core/src/ops/function.rs:227:5
      21: <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
                 at /rustc/6db0a0e9a4a2f55b1a85954e114ada0b45c32e45/library/alloc/src/boxed.rs:1694:9
          <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
                 at /rustc/6db0a0e9a4a2f55b1a85954e114ada0b45c32e45/library/alloc/src/boxed.rs:1694:9
          std::sys::unix::thread::Thread::new::thread_start
                 at /rustc/6db0a0e9a4a2f55b1a85954e114ada0b45c32e45/library/std/src/sys/unix/thread.rs:108:17
      22: __pthread_body
      23: __pthread_start

At the same time, the result of 06_0000_show_queries shows the output of other strings
06_0000_show_queries:                                                   [ FAIL ] - result differs with:
--- /Users/kous/myProjects/rustproject/databend/tests/suites/0_stateless/06_0000_show_queries.result    2021-10-27 21:48:32.000000000 +0800
+++ /Users/kous/myProjects/rustproject/databend/tests/suites/0_stateless/06_0000_show_queries.stdout    2021-12-05 20:57:10.000000000 +0800
@@ -1,3 +1,4 @@
+math_sample_numbers
 t1
 t2
 t3
@@ -8,6 +9,7 @@
 t1
 t2
 t3
+math_sample_numbers
 t1
 t2
 t3

You can debug this by printing data_type in https://github.com/datafuselabs/databend/blob/1600ee1e678c12cff6fe41ad5861bac491a29be5/query/src/servers/mysql/writers/query_result_writer.rs:176

error data_value : 10086, data_type: UInt16


legal?

Thanks for making available this wonderful tool!
Just a short question: is retrieving tweets by using this tool legal when using it for academic purposes? Somewhere in the developer terms I read:
"If you provide Twitter Content ... you will only distribute or allow download of Tweet IDs, Direct Message IDs, and/or User IDs. ... You may not do any of the following while accessing or using the Services: (iii) access or search or attempt to access or search the Services by any means (automated or otherwise) other than through our currently available, published interfaces that are provided by Twitter (and only pursuant to the applicable terms and conditions), unless you have been specifically allowed to do so in a separate agreement with Twitter (NOTE: crawling the Services is permissible if done in accordance with the provisions of the robots.txt file, however, scraping the Services without the prior consent of Twitter is expressly prohibited);"

According to the Twitter Automation rules (https://help.twitter.com/en/rules-and-policies/twitter-automation), making tools that automatically use the twitter API is allowed; also, one of the main ideas of the usage of the Application programming interface, is to automate long and tiring processes.
I have seen this tool used in academic papers, such as this one https://drive.google.com/file/d/1we5kywWQqQRYX0Hy8edsKKN7PdaaFuzY/view (it is in Spanish)
However, I would recommend you to read the Automation rules on Twitter's General guidelines and policies. Maybe ask the question on https://twittercommunity.com/c/dev-rules-and-policies/rules-and-policies to make sure you do not get in trouble because it depends if Twitter finds this legal or not because it is not directly bypassing a specific ban, instead just repeating a long process and taking advantage of a feature on the API.

Thank you so much for your response and answer!
We tried to  get an enterprise account from Twitter, but they did not
respond on our request, so we found GetOldTweets3 being a wonderful
solution. Thanks for making the tool available.
Best regards,
Wilbert Heeringa
Op wo 22 apr. 2020 om 03:48 schreef monchi<EMAIL_ADDRESS>
According to the Twitter Automation rules (
https://help.twitter.com/en/rules-and-policies/twitter-automation),
making tools that automatically use the twitter API is allowed; also, one
of the main ideas of the usage of the Application programming interface, is
to automate long and tiring processes.
I have seen this tool used in academic papers, such as this one
https://drive.google.com/file/d/1we5kywWQqQRYX0Hy8edsKKN7PdaaFuzY/view
(it is in Spanish)
However, I would recommend you to read the Automation rules on Twitter's
General guidelines and policies. Maybe ask the question on
https://twittercommunity.com/c/dev-rules-and-policies/rules-and-policies
to make sure you do not get in trouble because it depends if Twitter finds
this legal or not because it is not directly bypassing a specific ban,
instead just repeating a long process and taking advantage of a feature on
the API.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Mottl/GetOldTweets3/issues/59#issuecomment-617492751,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFKKNGL76VWYW3VM345HXOTRNZEGRANCNFSM4KTCNOXA
.

According to Twitter's TOS  "scraping the Services without the prior consent of Twitter is expressly prohibited".

Why can't this tool make use of robots.txt or can anyone confirm if it does use it already?


child.method = () => parent.method.call(child)

What problem does this feature solve?
i try create component based on the pattern facade. On example my component named Windows and it would add data variables, methods, watchers and listeners to direct child, which wrap and make component with window-functional.
I can't use methods: , because this.getDraggableElement.call(comp) not work!
I use this construction:
var DEBUG = true
function getDraggableElement () {
  if (DEBUG) console.log('getDraggableElement()', this.$el)
  return this.$el
}
export default {
  methods: {
    implantateChild (comp, i) {
      comp.$el.classList.add('window')
      comp.$el.style.width = '500px'
      comp.$el.style.height = '500px'
      comp.$el.style.top = `${50 * (i   1)}px`
      comp.$el.style.left = `${50 * (i   1)}px`
      comp.getDraggableElement = () => getDraggableElement.call(comp)
    }
  },
  updated () {
    this.$children.forEach((comp, i) => {
      this.implantateChild(comp, i)
    })
  }
}

so i I carry function getDraggableElement () beyond export default. I fear that, when i would expand my facade-component, file of component turn unreadable monster...
Also pay attention to how i assign classes and styles to DOM of my child. I think that this artisanal method, but i don't find better solution.
What does the proposed API look like?
export default {
  methods: {
    getDraggableElement () {
      return this.$el
    },
    implantateChild (comp, i) {
      let class = 'window'
      let styles = {
        width: '500px',
        height: '500px',
        top: `${50 * (i   1)}px`,
        left: `${50 * (i   1)}px`
      }
      comp.$class.add(class)
      comp.$styles.add(styles)
      comp.getDraggableElement = () => this.getDraggableElement.call(comp)
    }
  },
  mounted () {
    this.$children.forEach((comp, i) => {
      this.implantateChild(comp, i)
    })
  }
}

Please, don't disguise a question as a feature request. You can ask questions on the forum or StackOverflow.
You can pass around functions in the same way you pass objects, declaring the functions on the data should suffice for you 🙂

function which passed same way pass objects with .call(child) return this = parent
if i would declaring functions on the data, i will stumble across:
[Vue warn]: Avoid adding reactive properties to a Vue instance or its root $data at runtime - declare it upfront in the data option.
every DOM updating resetting my styles and classes, how about this?

http://jsfiddle.net/posva/780g9dmr/
Please, use the forums, gitter or stack overflow next time, thanks 🙂


python3 support

Your docs clearly state

ROS for Windows expects the 64-bit Python2.7

but is it possible to build ROS on Windows with python>=3.6 support?

@missxa For ROS, there are ROS 1 and ROS 2. For ROS 2, the Python 3 is already the target runtime and you can find more information here. For the ROS 1, Noetic will be the release focused on Python 3.7/3.8 migration. And that would be the first ROS 1 release which you can expect to work with Python 3.7/3.8.

I meant ROS 1, sorry I wasn't precise about that.
So noetic releases in May as I can see. Are there any build instructions  from source already available?

You can install noetic prerelease builds by using choco install ros-noetic-ALL --pre. Please understand that this is a pre-release package, and most 3rd packages have not been enabled on noetic.


IntelliJ executes mirrord twice in Gradle based runs on Kotlin

When running IntelliJ on macOS with a ~Kotlin based project and Gradle~ Scala project with Application run configuration type,  mirrord executes twice, leading to undefined experience.
Also causes agent to be stuck as long as gradle daemon is ran

Trying to reproduce in https://github.com/t4lz/gradle-play-scala-application/tree/main
That repo isn't working yet, can't even run without mirrord.