BIGTOP-3910: Bigtop-select support Ranger

Description of PR
Bigtop-select support Ranger
How was this patch tested?
Tested in local cluster
For code changes:

[ ] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'BIGTOP-3638. Your PR title ...')?
[ ] Make sure that newly added files do not have any licensing issues. When in doubt refer to https://www.apache.org/licenses/

Test steps (based on Bigtop 3.2.0)
`[root@bigtop1 current]# ll /usr/bigtop/current
total 0
lrwxrwxrwx. 1 root root 32 Apr  6 13:06 hadoop-client -> /usr/bigtop/3.2.0/usr/lib/hadoop
lrwxrwxrwx. 1 root root 37 Apr  6 13:06 hadoop-hdfs-client -> /usr/bigtop/3.2.0/usr/lib/hadoop-hdfs
lrwxrwxrwx. 1 root root 37 Mar 10 14:55 hadoop-hdfs-datanode -> /usr/bigtop/3.2.0/usr/lib/hadoop-hdfs
lrwxrwxrwx. 1 root root 37 Mar 10 15:42 hadoop-hdfs-journalnode -> /usr/bigtop/3.2.0/usr/lib/hadoop-hdfs
lrwxrwxrwx. 1 root root 37 Mar 10 14:56 hadoop-hdfs-namenode -> /usr/bigtop/3.2.0/usr/lib/hadoop-hdfs
lrwxrwxrwx. 1 root root 37 Mar 10 15:54 hadoop-hdfs-zkfc -> /usr/bigtop/3.2.0/usr/lib/hadoop-hdfs
lrwxrwxrwx. 1 root root 42 Apr  6 13:06 hadoop-mapreduce-client -> /usr/bigtop/3.2.0/usr/lib/hadoop-mapreduce
lrwxrwxrwx. 1 root root 37 Apr  6 13:06 hadoop-yarn-client -> /usr/bigtop/3.2.0/usr/lib/hadoop-yarn
lrwxrwxrwx. 1 root root 37 Apr  6 13:05 hadoop-yarn-nodemanager -> /usr/bigtop/3.2.0/usr/lib/hadoop-yarn
lrwxrwxrwx. 1 root root 31 Apr  6 12:36 hbase-client -> /usr/bigtop/3.2.0/usr/lib/hbase
lrwxrwxrwx. 1 root root 31 Mar 15 10:07 hbase-regionserver -> /usr/bigtop/3.2.0/usr/lib/hbase
lrwxrwxrwx. 1 root root 30 Apr  6 13:29 hive-client -> /usr/bigtop/3.2.0/usr/lib/hive
lrwxrwxrwx. 1 root root 39 Apr  6 13:28 hive-webhcat -> /usr/bigtop/3.2.0/usr/lib/hive-hcatalog
lrwxrwxrwx. 1 root root 31 Apr  6 12:57 kafka-broker -> /usr/bigtop/3.2.0/usr/lib/kafka
lrwxrwxrwx. 1 root root 31 Apr  6 13:06 spark-client -> /usr/bigtop/3.2.0/usr/lib/spark
lrwxrwxrwx. 1 root root 29 Apr  6 13:29 tez-client -> /usr/bigtop/3.2.0/usr/lib/tez
lrwxrwxrwx. 1 root root 35 Apr  6 10:07 zookeeper-client -> /usr/bigtop/3.2.0/usr/lib/zookeeper
lrwxrwxrwx. 1 root root 35 Mar 10 15:00 zookeeper-server -> /usr/bigtop/3.2.0/usr/lib/zookeeper
[root@bigtop1 current]# /usr/lib/bigtop-select/distro-select set  ranger-admin 3.2.0
[root@bigtop1 current]# /usr/lib/bigtop-select/distro-select set  ranger-usersync 3.2.0
[root@bigtop1 current]# /usr/lib/bigtop-select/distro-select set  ranger-tagsync 3.2.0
[root@bigtop1 current]# ll /usr/bigtop/current
total 0
lrwxrwxrwx. 1 root root 32 Apr  6 13:06 hadoop-client -> /usr/bigtop/3.2.0/usr/lib/hadoop
lrwxrwxrwx. 1 root root 37 Apr  6 13:06 hadoop-hdfs-client -> /usr/bigtop/3.2.0/usr/lib/hadoop-hdfs
lrwxrwxrwx. 1 root root 37 Mar 10 14:55 hadoop-hdfs-datanode -> /usr/bigtop/3.2.0/usr/lib/hadoop-hdfs
lrwxrwxrwx. 1 root root 37 Mar 10 15:42 hadoop-hdfs-journalnode -> /usr/bigtop/3.2.0/usr/lib/hadoop-hdfs
lrwxrwxrwx. 1 root root 37 Mar 10 14:56 hadoop-hdfs-namenode -> /usr/bigtop/3.2.0/usr/lib/hadoop-hdfs
lrwxrwxrwx. 1 root root 37 Mar 10 15:54 hadoop-hdfs-zkfc -> /usr/bigtop/3.2.0/usr/lib/hadoop-hdfs
lrwxrwxrwx. 1 root root 42 Apr  6 13:06 hadoop-mapreduce-client -> /usr/bigtop/3.2.0/usr/lib/hadoop-mapreduce
lrwxrwxrwx. 1 root root 37 Apr  6 13:06 hadoop-yarn-client -> /usr/bigtop/3.2.0/usr/lib/hadoop-yarn
lrwxrwxrwx. 1 root root 37 Apr  6 13:05 hadoop-yarn-nodemanager -> /usr/bigtop/3.2.0/usr/lib/hadoop-yarn
lrwxrwxrwx. 1 root root 31 Apr  6 12:36 hbase-client -> /usr/bigtop/3.2.0/usr/lib/hbase
lrwxrwxrwx. 1 root root 31 Mar 15 10:07 hbase-regionserver -> /usr/bigtop/3.2.0/usr/lib/hbase
lrwxrwxrwx. 1 root root 30 Apr  6 13:29 hive-client -> /usr/bigtop/3.2.0/usr/lib/hive
lrwxrwxrwx. 1 root root 39 Apr  6 13:28 hive-webhcat -> /usr/bigtop/3.2.0/usr/lib/hive-hcatalog
lrwxrwxrwx. 1 root root 31 Apr  6 12:57 kafka-broker -> /usr/bigtop/3.2.0/usr/lib/kafka
lrwxrwxrwx. 1 root root 38 Apr 14 17:39 ranger-admin -> /usr/bigtop/3.2.0/usr/lib/ranger-admin
lrwxrwxrwx. 1 root root 40 Apr 14 17:39 ranger-tagsync -> /usr/bigtop/3.2.0/usr/lib/ranger-tagsync
lrwxrwxrwx. 1 root root 41 Apr 14 17:39 ranger-usersync -> /usr/bigtop/3.2.0/usr/lib/ranger-usersync
lrwxrwxrwx. 1 root root 31 Apr  6 13:06 spark-client -> /usr/bigtop/3.2.0/usr/lib/spark
lrwxrwxrwx. 1 root root 29 Apr  6 13:29 tez-client -> /usr/bigtop/3.2.0/usr/lib/tez
lrwxrwxrwx. 1 root root 35 Apr  6 10:07 zookeeper-client -> /usr/bigtop/3.2.0/usr/lib/zookeeper
lrwxrwxrwx. 1 root root 35 Mar 10 15:00 zookeeper-server -> /usr/bigtop/3.2.0/usr/lib/zookeeper`

@iwasakims  Could you review this patch ?

conf-select is not needed for Ranger?

conf-select is not needed for Ranger?

Indeed,  i find conf-select don't works in ambari 2.8.0/trunk
When intalling service or component, we can see following logs
2023-03-10 14:55:46,418 - The conf-select tool reported an error for the package zookeeper. The configuration linking will be skipped. 2023-03-10 14:55:46,418 - Skipping the conf-select tool on phoenix since /etc/phoenix/conf does not exist. 2023-03-10 14:55:46,426 - Unable to create versioned configuration directories since the parameters supplied do not support it 2023-03-10 14:55:46,427 - The conf-select tool reported an error for the package flink. The configuration linking will be skipped. 2023-03-10 14:55:46,428 - Unable to create versioned configuration directories since the parameters supplied do not support it 2023-03-10 14:55:46,428 - The conf-select tool reported an error for the package hadoop. The configuration linking will be skipped. 2023-03-10 14:55:46,429 - Unable to create versioned configuration directories since the parameters supplied do not support it 2023-03-10 14:55:46,429 - The conf-select tool reported an error for the package hive. The configuration linking will be skipped. 2023-03-10 14:55:46,431 - Unable to create versioned configuration directories since the parameters supplied do not support it 2023-03-10 14:55:46,431 - The conf-select tool reported an error for the package kafka. The configuration linking will be skipped. 2023-03-10 14:55:46,431 - Skipping the conf-select tool on tez since /etc/tez/conf does not exist. 2023-03-10 14:55:46,431 - Skipping the conf-select tool on zeppelin since /etc/zeppelin/conf does not exist. 2023-03-10 14:55:46,433 - Unable to create versioned configuration directories since the parameters supplied do not support it 2023-03-10 14:55:46,434 - The conf-select tool reported an error for the package hive-hcatalog. The configuration linking will be skipped. 2023-03-10 14:55:46,435 - Unable to create versioned configuration directories since the parameters supplied do not support it 2023-03-10 14:55:46,435 - The conf-select tool reported an error for the package ranger-admin. The configuration linking will be skipped. 2023-03-10 14:55:46,436 - Unable to create versioned configuration directories since the parameters supplied do not support it 2023-03-10 14:55:46,436 - The conf-select tool reported an error for the package hbase. The configuration linking will be skipped. 2023-03-10 14:55:46,437 - Unable to create versioned configuration directories since the parameters supplied do not support it 2023-03-10 14:55:46,438 - The conf-select tool reported an error for the package ranger-usersync. The configuration linking will be skipped. 2023-03-10 14:55:46,438 - Skipping the conf-select tool on solr since /etc/solr/conf does not exist. 2023-03-10 14:55:46,438 - Skipping the conf-select tool on spark since /etc/spark/conf does not exist. 2023-03-10 14:55:46,439 - Unable to create versioned configuration directories since the parameters supplied do not support it 2023-03-10 14:55:46,439 - The conf-select tool reported an error for the package ranger-tagsync. The configuration linking will be skipped.

conf-select is not needed for Ranger?

Indeed,  i find conf-select don't works in ambari 2.8.0/trunk
When intalling service or component, we can see following logs
2023-03-10 14:55:46,418 - The conf-select tool reported an error for the package zookeeper. The configuration linking will be skipped. 2023-03-10 14:55:46,418 - Skipping the conf-select tool on phoenix since /etc/phoenix/conf does not exist. 2023-03-10 14:55:46,426 - Unable to create versioned configuration directories since the parameters supplied do not support it 2023-03-10 14:55:46,427 - The conf-select tool reported an error for the package flink. The configuration linking will be skipped. 2023-03-10 14:55:46,428 - Unable to create versioned configuration directories since the parameters supplied do not support it 2023-03-10 14:55:46,428 - The conf-select tool reported an error for the package hadoop. The configuration linking will be skipped. 2023-03-10 14:55:46,429 - Unable to create versioned configuration directories since the parameters supplied do not support it 2023-03-10 14:55:46,429 - The conf-select tool reported an error for the package hive. The configuration linking will be skipped. 2023-03-10 14:55:46,431 - Unable to create versioned configuration directories since the parameters supplied do not support it 2023-03-10 14:55:46,431 - The conf-select tool reported an error for the package kafka. The configuration linking will be skipped. 2023-03-10 14:55:46,431 - Skipping the conf-select tool on tez since /etc/tez/conf does not exist. 2023-03-10 14:55:46,431 - Skipping the conf-select tool on zeppelin since /etc/zeppelin/conf does not exist. 2023-03-10 14:55:46,433 - Unable to create versioned configuration directories since the parameters supplied do not support it 2023-03-10 14:55:46,434 - The conf-select tool reported an error for the package hive-hcatalog. The configuration linking will be skipped. 2023-03-10 14:55:46,435 - Unable to create versioned configuration directories since the parameters supplied do not support it 2023-03-10 14:55:46,435 - The conf-select tool reported an error for the package ranger-admin. The configuration linking will be skipped. 2023-03-10 14:55:46,436 - Unable to create versioned configuration directories since the parameters supplied do not support it 2023-03-10 14:55:46,436 - The conf-select tool reported an error for the package hbase. The configuration linking will be skipped. 2023-03-10 14:55:46,437 - Unable to create versioned configuration directories since the parameters supplied do not support it 2023-03-10 14:55:46,438 - The conf-select tool reported an error for the package ranger-usersync. The configuration linking will be skipped. 2023-03-10 14:55:46,438 - Skipping the conf-select tool on solr since /etc/solr/conf does not exist. 2023-03-10 14:55:46,438 - Skipping the conf-select tool on spark since /etc/spark/conf does not exist. 2023-03-10 14:55:46,439 - Unable to create versioned configuration directories since the parameters supplied do not support it 2023-03-10 14:55:46,439 - The conf-select tool reported an error for the package ranger-tagsync. The configuration linking will be skipped.

conf-select is not needed for Ranger?

Indeed,  i find conf-select don't works in ambari 2.8.0/trunk
When intalling service or component, we can see following logs
2023-03-10 14:55:46,418 - The conf-select tool reported an error for the package zookeeper. The configuration linking will be skipped. 2023-03-10 14:55:46,418 - Skipping the conf-select tool on phoenix since /etc/phoenix/conf does not exist. 2023-03-10 14:55:46,426 - Unable to create versioned configuration directories since the parameters supplied do not support it 2023-03-10 14:55:46,427 - The conf-select tool reported an error for the package flink. The configuration linking will be skipped. 2023-03-10 14:55:46,428 - Unable to create versioned configuration directories since the parameters supplied do not support it 2023-03-10 14:55:46,428 - The conf-select tool reported an error for the package hadoop. The configuration linking will be skipped. 2023-03-10 14:55:46,429 - Unable to create versioned configuration directories since the parameters supplied do not support it 2023-03-10 14:55:46,429 - The conf-select tool reported an error for the package hive. The configuration linking will be skipped. 2023-03-10 14:55:46,431 - Unable to create versioned configuration directories since the parameters supplied do not support it 2023-03-10 14:55:46,431 - The conf-select tool reported an error for the package kafka. The configuration linking will be skipped. 2023-03-10 14:55:46,431 - Skipping the conf-select tool on tez since /etc/tez/conf does not exist. 2023-03-10 14:55:46,431 - Skipping the conf-select tool on zeppelin since /etc/zeppelin/conf does not exist. 2023-03-10 14:55:46,433 - Unable to create versioned configuration directories since the parameters supplied do not support it 2023-03-10 14:55:46,434 - The conf-select tool reported an error for the package hive-hcatalog. The configuration linking will be skipped. 2023-03-10 14:55:46,435 - Unable to create versioned configuration directories since the parameters supplied do not support it 2023-03-10 14:55:46,435 - The conf-select tool reported an error for the package ranger-admin. The configuration linking will be skipped. 2023-03-10 14:55:46,436 - Unable to create versioned configuration directories since the parameters supplied do not support it 2023-03-10 14:55:46,436 - The conf-select tool reported an error for the package hbase. The configuration linking will be skipped. 2023-03-10 14:55:46,437 - Unable to create versioned configuration directories since the parameters supplied do not support it 2023-03-10 14:55:46,438 - The conf-select tool reported an error for the package ranger-usersync. The configuration linking will be skipped. 2023-03-10 14:55:46,438 - Skipping the conf-select tool on solr since /etc/solr/conf does not exist. 2023-03-10 14:55:46,438 - Skipping the conf-select tool on spark since /etc/spark/conf does not exist. 2023-03-10 14:55:46,439 - Unable to create versioned configuration directories since the parameters supplied do not support it 2023-03-10 14:55:46,439 - The conf-select tool reported an error for the package ranger-tagsync. The configuration linking will be skipped.

Hi @iwasakims
This pull request is precondition for deploying Ranger by ambari.
Could you please review again?
Thanks.


Use a logging library as a logger implementation instead of console.log

Is your feature request related to a problem? Please describe.
I feel that using something like pino or winston will be best for logging purposes, since there is no need to create our own logger and reinvent the wheel.
Describe the solution you'd like
Rewrite the current logger package to use a fully-featured logging library.
Describe alternatives you've considered
Using console.log has disadvantages, some users would like to save the logs to a file, log via http, etc... This is not possible using our current logging solution.

We could add an option called output which would be a function that accepts only one arg, like this:
logger({ output: console.log })

or like this:
logger({ output: async (x) => await writeFile('my-log.txt', x) })

and then in the logger:
options.output(x)

About re-inventing the wheel. That was the point. @tinyhttp/logger is a basic logger that will fit to most cases, but for something advanced it's recommended to use Pino. It's written in the readme. We can add the output option - but I'm not sure if it should be as full featured as Pino.

Cool, I'll make a PR.

@Arnovsky nice, looking forward to it


Support notebook parameters

https://quarto.org/docs/computations/parameters.html

Behaviour of https://papermill.readthedocs.io/en/latest/usage-parameterize.html#how-parameters-work seems most reasonable to implement.

I think I would do a mixture of both behaviors. I actually like the yaml header syntax better than the tagged cell, because tagging a cell is a new kind of behavior vs. just adding more configuration at the top. And because papermill itself notes that one cannot use the parameter settings like code:

If there's a code cell, people will be tempted to write arbitrary Julia expressions, while the parameters features is just for basic datatypes anyway, as it's specified through YAML.
Unlike knitr, I wouldn't introduce a params variable but just use the param names directly as variables, like in python.
So to sum up, something like this:
---
params:
    a: 1
    b: 2
---

```{julia}
a + b
```
# 3

Agreed, that seems like reasonable behaviour to me.


SAML not working in any Matrix client.

Steps to reproduce
I've been trying to get on the ubuntu.com matrix instance. I've followed the instructions written here: https://discourse.ubuntu.com/t/synchronous-communication-with-matrix/39535
Outcome
SAML always fails with an error message in this picture

Client information
Element Desktop:
1.11.48:
Ubuntu 23.10 - snap
FluffyChat:
rc1.15.1:
Ubuntu 23.10 - snap
Element Web:
Ubuntu 23.10 - Firefox webapp
FluffyChat:
1.15.0:
iOS 17
Element Messenger:
1.11.4:
iOS 17

I have the same problem.
I do also note that the post references chat.ubuntu.com but Synapse appears to be running at chat-server.ubuntu.com, in case this is a canonical URL issue...

i'm having the same prob as @tylnesh

Nhaines, Tylnesh, and Fenris are all members of the Launchpad group Ubuntu Members, therefore should be allowed to use SSO on the chat.ubuntu.com Matrix instance during this stage of testing.

Thanks @ilvipero , @amandahla can you have a look please?

There may be some mismatch in the URL that the SAML expects. We're using ubuntu.com as the server URL for the matrix client, but Ubuntu One mentiones chat-server.ubuntu.com as the requested service. Just to be sure, I've tried using that URL as well, but still no progress.

@tylnesh @fenris @nathanhaines We changed settings to fix the issue, could you please try and login with SAML again and share the result?

\o/ finally, it's working


 Make sure to confirm this in the BIOS and not with GPU-Z or similar since it can be inaccurate
[x] 4G decoding is enabled. Make sure to confirm this in the BIOS and not with GPU-Z or similar since it can be inaccurate
[x] UEFIPatch is applied (see Using UEFIPatch for more information). On some motherboards DSDT Patching is also needed
[x] I have read Common issues (and fixes)

Description
DSDT patching has been applied as per wiki.

The following patches appear to prevent this motherboard from booting:
PciHostBridge | Replace 16GB MMIO region with complete use of physical address space (Ivy Bridge).
PciHostBridge | Remove 4GB limit for PciRootBridgeIo.Mem
The following patches do not appear to cause issues:
PciHostBridge | Remove <4GB BAR size limit in SubmitResources (Ivy Bridge)
PciBus | Remove <16GB BAR size limit (Ivy Bridge/Haswell)
Runtime | Remove 4GB limit for CpuIo2
If I do not patch UEFI, I can get Rebar to work up to 2 GB as expected. Applying PciHostBridge | Replace 16GB MMIO region with complete use of physical address space (Ivy Bridge). with DSDT will POST, enter Windows, and allow RebarState to be set. Attempting to enter BIOS configuration with this patch applied, however, results in a hard lock of the system. The system freezes with "A2" on the screen. PciHostBridge | Remove 4GB limit for PciRootBridgeIo.Mem results in a failed POST if PciHostBridge | Replace 16GB MMIO region with complete use of physical address space (Ivy Bridge) is not applied.
Windows does not show "PCI Bus" under "Large Memory." I saw that this was an issue seen on Haswell systems and wondered if I may need a similar patch.
GPU-Z does show ReBAR and Above 4G Decoding enabled.
This does not appear to be a case of losing display during POST - the BIOS initially shows up and just hangs if I attempt to enter configuration. Trying to use the IGP doesn't fix the problem.
It appears that the patches only cause this failure after turning on Above 4G Decoding. While Above 4G Decoding is disabled, BIOS setup can be entered without issue. I've attached my modification that includes only changes to option visibility (to display Above 4G Decoding and CSM options) and the procedures outlines in the Wiki. DSDT has been modified. All files were injected with MMTool to prevent any pad file issues.
rebarZ77OCF2.zip
DSDT:
                    CreateQWordField (BUF0, \_SB.PCI0._Y0F._LEN, M2LN)  // _LEN: Length
                    CreateQWordField (BUF0, \_SB.PCI0._Y0F._MIN, M2MN)  // _MIN: Minimum Base Address
                    CreateQWordField (BUF0, \_SB.PCI0._Y0F._MAX, M2MX)  // _MAX: Maximum Base Address
                    M2MX = 0xFFFFFFFFF
                    If ((TUUD >= 0x1000))
                    {
                        M2MN = (TUUD << 0x14)
                    }
                    Else
                    {
                        M2MN = 0x0000000100000000
                    }

                    M2LN = (M2MX - M2MN) + One
                }

                Return (BUF0) /* \_SB_.PCI0.BUF0 */

Looking further into it, it looks like "PCI Express Root Complex" and "PCI Bus" may be the same device. Furthermore, the patching actually seems to work - setting any value (including 32) works without issue, but attempting to enter BIOS setup fails when patches are applied.
While this allows me to use whatever BAR I want, it does prevent any access to BIOS to load settings after flashing the patched image. Once the patch is applied, attempting to enter BIOS setup is nonfunctional.


Support for custom imodelclient

to be used with iTwin Stack

missing rush change,
just to confirm no core bump needed for this right?

No core bump right....which pkg needs rush change?

missing rush change,
just to confirm no core bump needed for this right?

No core bump right....which pkg needs rush change?

ah sorry, im blind, looks good to go


[GitVote] Test Issue

Testing git vote
/vote-maintainers

it would be nice if gitvote automatically populated with the 3 choices

@TerryHowe can you describe what you would like to see here. @caniszczyk and @tegioz might be interested in feedback.

Actually setting the 3 emoticons on the post instead of just the log so people can just click on them rather than the first person has to set.

Done I think


Bluetooth with Rx thread returns multiple instances

My following code is returning me multiple instances of bluetooth connection. And hence, most of my commands to the bluetooth devices are getting called repetitively. Please let me know the solution to have one periodic observer.
    fun getObservableService(
        connection: RxBleConnection,
        onServiceDiscovered: (customService: BluetoothGattService) -> Unit = {}
    ): Observable<Observable<ByteArray>> =
        connection.discoverServices()
            .flatMap { services -> services.getService(getServiceId()) } //here it gets multiple instances
            .flatMapObservable { customService: BluetoothGattService ->
                onServiceDiscovered(customService)

                // Setup service or use existing one
                 connection.setupNotification(
                        customService,
                        getCharacteristicUuid()
                    )
                }.apply { isServiceConnected = true }
            }

Hello,
I am afraid that you have created an issue in a wrong repository — this probably should go to https://github.com/Polidea/RxAndroidBle/. When creating an issue please follow the issue template — it will help us help you more efficiently.
Best regards


MacOS Big Sur compatability - any way to get it to work?

can't seem to get the plugin to work in Ableton having followed the steps to deal with unidentified developer application issues, vst3 just appears as a folder in Ableton (which contains components but not the actual plug-in) having searched plug-ins and custom plug-ins folder.

thanks! really hope I can get this working in Big Sur as it looks great :-)

same issue here with macOS Monterey


deprecated Files API Google App Engine to be completely removed

gwtupload-gae uses the Google App Engine deprecated Files API.  This API will be permanently removed from App Engine on August 4th, 2015.  All references to com.google.appengine.api.files should be removed or migrated to either the Blobstore or Google Cloud Storage.
Class that needs to be changed/removed:
FilesApiFileItemFactory

The quota on the blob store has been replaced with a default bucket on cloud storage with instructions on how to set up here https://cloud.google.com/appengine/docs/java/googlecloudstorageclient/activate
@manolo do you mind if I attempt to solve this issue? My plan is to replace FilesApiFileItemFactory.java
and FilesApiUploadAction.java with CloudStorageFileItemFactory.java and CloudStorageUploadAction.java

FilesApi files are left intact for now.

Anyone:question:

It would probably be best to strip out the FilesApi as per the depreciation warning from Google.
https://cloud.google.com/appengine/docs/deprecations/files_api

I did initially then put them back in just so that I am not jumping the gun... quite happy to remove them and the pom dependency if I get green light for a merge.

Up ! Please this is really disturbing !

I tried to replace the file api with the new Cloud Storage version but local on jetty i get the error message "com.google.appengine.tools.cloudstorage.NonRetriableException: com.google.apphosting.api.ApiProxy$FeatureNotEnabledException: The Files API is disabled. Further information: https://cloud.google.com/appengine/docs/deprecations/files_api" and in the gae "com.google.common.base.Stopwatch.createUnstarted()Lcom/google/common/base/Stopwatch"


WRONG URL in GPT README

🐛 Describe the bug
The link openwebtext in gpt README dosen't exist.
Environment
No response

Hi @Wesley-Jzy , that sentence is no longer valid and I have removed it in #45 .


EventLog / MessageStore cursor should not be a messageCID

Prior to this PR we used messageCid as a cursor for paginating the MessageStore, as well as EventLog.
This generally works well since all messages throughout the system can be identified by a messageCid, however it becomes tricky if a messageCid which was returned as a pagination cursor, was no longer in the MessageStore by the time the subsequent call came in using that messageCid as a cursor.
To remedy this the cursor is now a string which represents the sortProperty of the query, the sortValue and itemId of the last item returned from a query.
This allows us to construct a sorted point in which to either start iterating through (gt iterator in level), or an index to slice the in-memory paging results.
Additionally there is a new property added to queryOptions, we can now set strictCursor when we'd like to only return a cursor if there are additional results. This will internalize the logic for whether or not to return a cursor value to within the actual IndexLevel.

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

Comparison is base (9c0fdb5) 98.80% compared to head (e8d4b1d) 98.80%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #638   +/-   ##
=======================================
  Coverage   98.80%   98.80%
=======================================
  Files          71       71
  Lines        9004     9059   +55
  Branches     1365     1380   +15
=======================================
+ Hits         8896     8951   +55
  Misses        100      100
  Partials        8        8

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


fix: dialog and select behaviour with overflow

Description
Dialog and select behaviour with overflow. Removed outline focus visible on select. Now the dialog show the select options outside the dialog and not cut it.

Test

[x] I have added tests that prove my fix is effective or that my feature works

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update platform.h to include new pins for Adafruit Grand Central M4

on behalf of @lalauria2000. Part 2 of 2.
See: microsoft/pxt-maker#324
May need to find a better way to move to the 128 pin packages.  I just made it so that if the board is SAMD51, it will always default to 128 pins.  Not sure if this is 100% accurate since a lot of the variants do not have 128 pins.

This PR is outdated I beleive.


[GlobalOpt] Add reshape propagation and transpose fusion into linalg results to transpose propagation

This PR enables fusion of transposes into the DPS init of linalg ops during PropagateLinalgTranspose. This also enables fusion by expansion and collapsing to propagate reshapes up and down during transpose propagation. After this PR, transpose propagation works as follows:

First, canonicalize named contractions by fusing nearby transpose operations to create new named ops.
Propagate both reshapes and transposes up, and fuse transposes into the DPS inits of linalg ops.
Propagate both reshapes and transposes down, and fuse transposes into the inputs of linalg ops.
Compose adjacent transpose operations into a single transpose.

Why do we propagate reshape and transpose within a single pass? Can it be two passes? We are planning to enable transpose propagation by default, and most of issues in https://github.com/openxla/iree/pull/16059 are addressed. I'm afraid that this is adding more issues to block the enablement.

(we're really going to want to rewrite these kind of things to use the Explorer - local propagation is fine today because we generate single functions from frontends and inline everything, but we won't be forever - being able to propagate across calls and global loads/stores is going to be important and we don't want two (or more) ways of doing that - fine for now I guess, but keep that in mind that any local propagation is a subset of what we need at the whole-program level)

Why do we propagate reshape and transpose within a single pass? Can it be two passes? We are planning to enable transpose propagation by default, and most of issues in #16059 are addressed. I'm afraid that this is adding more issues to block the enablement.

There are some reshapes blocking transpose fusion with matmuls in SDXL. The idea is to propagate reshapes at the same time as propagating transposes to open up more transpose fusions. @qedawkins added the reshape propagation part, so he may have additional details, but I'm not sure if there is a nice way to move the reshape propagation to a separate pass, since we first propagate up and then down.

Why do we propagate reshape and transpose within a single pass? Can it be two passes? We are planning to enable transpose propagation by default, and most of issues in #16059 are addressed. I'm afraid that this is adding more issues to block the enablement.

When we have
%0 = linalg.generic tensor<?xf32>
%1 = tensor.expand_shape [[0, 1]] to tensor<?x?xf32>
%2 = linalg.transpose %1 permutation = [1, 0]

we cannot propagate the transpose through the reshape because the transpose is acting on the dimensions introduced by the reshape, however it is possible to first bubble the reshape up through the producer generic and then fuse the transpose. There isn't really a way to avoid doing both at the same time.

(we're really going to want to rewrite these kind of things to use the Explorer - local propagation is fine today because we generate single functions from frontends and inline everything, but we won't be forever - being able to propagate across calls and global loads/stores is going to be important and we don't want two (or more) ways of doing that - fine for now I guess, but keep that in mind that any local propagation is a subset of what we need at the whole-program level)

I see this as supplementary to the patterns added here. Full model transpose analysis is a lot more than what this pass is supposed to do, and has the danger of introducing cost models. This pass is just supposed to fold away/fuse a few transposes already present in the model, and one such pattern can be to use the explorer to look across the call graph/global users to fold away a transpose. We aren't expected to handle CFGs either at this level, so I don't see how the existing local propagation patterns here are related to what the explorer offers.

Removing benchmark flags because I realized they don't do anything to this PR.


Short solution needed: "How to add row to data frame" (python-pandas)

Please help us write most modern and shortest code solution for this issue:
How to add row to data frame (technology: python-pandas)
Fast way
Just write the code solution in the comments.
Prefered way

Create pull request with a new code file inside inbox folder.
Don't forget to use comments to make solution explained.
Link to this issue in comments of pull request.

How to add row to data frame


Collection View Cells on top of one another

I have a UITableView with cells some of which have a UICollectionView as subview. All collection views have a cell type with one text label, except for one which has a UIImageView, no text label. Since photos can be portrait or landscape, the collection view cells can have different heights and widths. the collection view cell type with only a label only has varying widths, but all cells have the same height.
Now here is the problem: adding new cv cells of the one with the image view will put them all on top of each other instead of side by side, row by row.

With the label type cv cell, that problem does not occur:

I can't exclude I'm overlooking something  - but with the standard UICollectionViewFlowLayout the problem does not occur.
thanks for any hints in the right direction

We will test it by the end of the week and come back to you ASAP. You might spotted an issue regarding the height differences.

Thanks. I think the problem lies in this line:
let firstInRow = previousFrame.origin.y != attributes.frame.origin.y
If I add more cells, they actually get displayed in additional rows, too. But all cells in the same row have the same origin x...  that's why they appear clustered in the same place in each row.
I have replaced it with this line
let firstInRow = (previousFrame.origin.y + previousFrame.height / 2.0)  !=  (attributes.frame.origin.y + attributes.frame.height / 2.0)
and it seems to work. Despite the change, I still have trouble to make it work in my own app, I need to look into this further.
But it seems to work in the example project:

There seems to be an issue if the heights are even and odd numbers, so the centre points might not always be the same for each row. therefore I changed the firstInRow definition again:
let firstInRow = (previousFrame.origin.y + previousFrame.height / 2.0)  <  (attributes.frame.origin.y + attributes.frame.height / 2.0)  - 1.0
I have forked the repository and committed the change.
I'm not 100% sure this works for all cases but I checked it for equal and unequal heights in your example.

You are right. To determine either or not the current attributes represent a new row, we are checking if the previous attributes origin (y) is different. This involve a massive side effect regarding the height. If an item has a different height from its previous neighbour it will be considered as a new row, meaning it will be placed at the most left position. I'm not sure you're formula is taking all cases into account, but it will definitely reduce the side effect. My team and I will try to fix this tomorrow.
Thanks again!

let firstInRow = previousAttributes?.center.y != attributes.center.y

Works perfectly for me for different sizes, or same sizes, or just different height. So far it covers all use cases.

Thanks, that is even simpler.  However, this doesn't work in my app. To calculate the size of each collection view cell in my app, the image is rescaled (keeping the width height ratio) to fit into a square of 100 x 100.  I logged the heights of the sizes that are returned in the collectionviewlayout delegate function  - e.g. 74.9063670411985   .  there might be a problem with rounding or decimal imprecision...   This means that the centre y  values are not necessarily exactly the same among the cells of the same row.
Therefore I would suggest:
let firstInRow = previousAttributes!.center.y < attributes.center.y - 1.0
The centre y value of the last cell in the previous row must be smaller than the centre y value of first cell in the current row. The question is by how much. I tried deducting 0.1, even that doesn't work. but in my tests, - 1.0 does work.

anyway, the issue is solved from my point of view, feel free to close it.


Move away from 2015 edition?

Right now, the libc crate is at Rust edition 2015. Is there a desire to bump to a newer edition?
That would require a significant amount of changes, such as adding crate to paths that being with :: (e.g., crate::c_int instead of ::c_int). It would also require types inside an union to be Copy or wrapped in a ManuallyDrop.

Yeah, we should probably target 2021 as part of 1.0. Thanks for writing this up, I have been meaning to for a while but never got to it.

Note that doing this may make some backports more involved.

It looks like https://github.com/JohnTitor/ctest2/issues/48 blocks this.

@ChrisDenton are you just referring to maintaining both 1.0 and 0.2 at the same time like we do currently? We have a handful of planned changes like this that would make backports worse, it would probably be good to get everything else lined up then do them right before we plan to release 1.0.

are you just referring to maintaining both 1.0 and 0.2 at the same time like we do currently?

Yes, that's what I was referring to.

We have a handful of planned changes like this that would make backports worse, it would probably be good to get everything else lined up then do them right before we plan to release 1.0.

Makes sense.

I have tried to migrate it to 2021 using cargo fix --edition, and cargo build is now working with the edition set to 2021 in Cargo.toml. Isn't this that simple?

We cherry pick commits from main to libc-0.2 for the stable release. Doing a lot of tiny changes from the autofix means that these many cherry picks won't apply as cleanly, which would be a huge annoyance - since doing this change is so easy/automated, we can defer it until we get closer to 1.0.

We upgraded the MSRV of 0.2 to 1.63, meaning that both main and libc-0.2 can use edition 2021. If anyone would like to put up a PR making this change, that would be welcome!

Completed in https://github.com/rust-lang/libc/pull/4132 and https://github.com/rust-lang/libc/pull/4155.


DevTools failed to load SourceMap

DevTools failed to load SourceMap: Could not parse content for http://localhost:3010/contenteditable.vue.map: Unexpected token < in JSON at position 0

in console

not work, last vue ver 2 + SSR

hum... I will look at it when I have some time

Is it still a proble with the new update ?

Is it still a proble with the new update ?


Remove SDX_HOME and fix order of make targets

What? and Why?
Remove unused SDX_HOME that causes the build to fail if it's not present
Supersedes #57

Codecov Report

Merging #59 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #59   +/-   ##
=======================================
  Coverage   79.56%   79.56%
=======================================
  Files           9        9
  Lines         279      279
=======================================
  Hits          222      222
  Misses         57       57

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 34d4d8b...55c34a3. Read the comment docs.


Distroless image support?

Now that Ubuntu has launched distroless docker images do we want to consider shipping these as part of our set of images?
https://ubuntu.com/containers/chiselled

One for the PMC?  There's multiple flavours of distroless (weirdly)


log: export a default logger

I keep seeing this redefined all over. Thought I'd just export the default one.

I don't see how this is a significant change at all.
This changes nothing about the API guarantees the log package makes. Yes, the newly exported symbol must remain there forever -- but it already had to, because std can never be changed according to the API guarantee.

It is a new API. Any new API (regardless of how small or big it is) needs to go through the proposal process.
If what you say makes sense to the team, then it will be accepted anyways and then the change can be made. There is no harm done in following the process.

I feel like this change is harmful, since it encourages people to use mutable global state.


(WIP) Rotation undo transform for Aleatoric uncertainty

We need to implement Rotation undo transform for Aleatoric uncertainty purposes. See issue #136
Sister PR: https://github.com/neuropoly/medicaltorch/pull/16
Todo:

test with and without
paint

To test this PR:

Run:

python testing/test_undoTrans.py

Use cmd_test with:

uncertainty: {aleatoric: true}.
in transformation_training: RandomRotation: {degrees: XX}

Fix #136

Important note: I have introduced transformation_testing in the config file. Reason: when using aleatoric MC, the DA differs from the validation (no DA) and from the training (Elastic or RandomAffine have no undo_transform, which is needed during inference).

Important note: I have introduced transformation_testing in the config file. Reason: when using aleatoric MC, the DA differs from the validation (no DA) and from the training (Elastic or RandomAffine have no undo_transform, which is needed during inference).

To make it explicit, the transformations are now displayed in the terminal:
Applied transformations:
	- Resample
	- ROICrop2D
	- ToTensor
	- NormalizeInstance

I moved all the "uncertainty" code from cmd_test to utils --> we are just calling run_uncertainty in cmd_test.

Preliminary results: on the testing set, median and IQR.
(Note: Ideal score for Dice and LTPR are 100., while we aim at minimizing LFDR)
No Epistemic & No Aleatoric:
3D Dice: 52.4 (0 - 58.2) %
3D LFDR: 33.3 (25 - 50) %
3D LTPR: 87.5 (68.8 - 100) %

Epistemic & No Aleatoric:
3D Dice: 38.4 (0 - 58.3) %
3D LFDR: 63.6 (39.3 - 78.9) %
3D LTPR: 75 (68.7 - 93.8) %

No Epistemic & Aleatoric (RandomRotation, 20°):
3D Dice: 47.2 (0 - 55.3) %
3D LFDR: 38.8 (34.4 - 60) %
3D LTPR: 87.5 (43.8 - 100) %

Preliminary experiments conclusion: We are gaining information with uncertainty / soft prediction but the first results are showing less good results on hard masks compared to "no Dropout & DA at testing time".
Will keep digging & keep you posted.

New results on the same dataset / conditions:
Preliminary results: on the testing set, median and IQR.
(Note: Ideal score for Dice and LTPR are 100., while we aim at minimizing LFDR)
No Epistemic & No Aleatoric:
3D Dice: 52.4 (0 - 58.2) %
3D LFDR: 33.3 (25 - 50) %
3D LTPR: 87.5 (68.8 - 100) %

Epistemic & No Aleatoric:
3D Dice: 38.4 (0 - 46.1) %
3D LFDR: 72.4 (64.7 - 74.6) %
3D LTPR: 87.5 (68.8 - 100) %

No Epistemic & Aleatoric (RandomRotation, 30°):
3D Dice: 43.8 (0 - 53.4) %
3D LFDR: 45 (40 - 66.1) %
3D LTPR: 100 (81 - 100) %

Conclusion: Improved results in terms of lesion wise metrics. But still less than without uncertainty. Keep looking

I run an aleatoric experiment without RandomRotation --> it gives the same results than without MC --> expected behaviour, okay, next.

I run an aleatoric experiment without RandomRotation --> it gives the same results than without MC --> expected behaviour, okay, next.

Same result and conclusion with RandomRotation(degrees=0).

When removing the binarisation in save_nii:
No Epistemic & No Aleatoric:
3D Dice: 52.4 (0 - 58.2) %
3D LFDR: 33.3 (25 - 50) %
3D LTPR: 87.5 (68.8 - 100) %

Epistemic & No Aleatoric:
3D Dice: 37.2 (0 - 51.3) %
3D LFDR: 63.3 (52.5 - 75) %
3D LTPR: 100 (81.25 - 100) %

No Epistemic & Aleatoric (RandomRotation, 30°):
3D Dice: 47.7 (0 - 55.5) %
3D LFDR: 39.3 (25.9 - 57.5) %
3D LTPR: 100 (81 - 100) %

Conclusion:

Improved results compared to previous experiment for both aleatoric & epistemic. Give him a chocolate.
Aleatoric: We now have similar results between with and without TestTimeDA. Expected behaviour --> I feel personally happy with that. Of course, will need to be further validated & dissected.
Epistemic: why do we have this drop of results? No idea at this point. Should I reduce the p_dropout? Am I doing something wrong here? Will look at it tomorrow. Any opinion more than welcome.

Final results of this PR: on the entire testing set, median and IQR.
(Note: Ideal score for Dice and LTPR are 100., while we aim at minimizing LFDR. Best scores indicated in bold.)
Baseline:
3D Dice: **42.8** (**15** - **57.6**) %
3D LFDR: **33.3** (**0** - **60**) %
3D LTPR: 100 (66.7 - 100) %

Epistemic (n_it=20, p_dropout=0.3):
3D Dice: 34.3 (11.4 - 51.7) %
3D LFDR: 66.7 (50 - 81.8) %
3D LTPR: **100** (**88.9** - **100**) %

Aleatoric (n_it=20, RandomRotation, 30°):
3D Dice: 39.3 (13.7 - 55.5) %
3D LFDR: 55.1 (28.6 - 70.4) %
3D LTPR: 100 (80 - 100) %

Conclusion: The MC samples introduce some FP which pulls down the overall scores. Future work will focus on implementing post-processing tools benefiting from the uncertainty metrics to mitigate this limitation.


Jetpack 6.0-b52 needs missing dustynv/jetson-inference:r36.2.0

Hello,
Just did a fresh install of latest Jetpack (19 dec 2023)
user@ubuntu:~/jetson-inference$ ./docker/run.sh
ARCH:  aarch64
reading L4T version from /etc/nv_tegra_release
L4T BSP Version:  L4T R36.2.0
CONTAINER_IMAGE:  dustynv/jetson-inference:r36.2.0
DATA_VOLUME:      --volume /home/user/jetson-inference/data:/jetson-inference/data --volume /home/user/jetson-inference/python/training/classification/data:/jetson-inference/python/training/classification/data --volume /home/user/jetson-inference/python/training/classification/models:/jetson-inference/python/training/classification/models --volume /home/user/jetson-inference/python/training/detection/ssd/data:/jetson-inference/python/training/detection/ssd/data --volume /home/user/jetson-inference/python/training/detection/ssd/models:/jetson-inference/python/training/detection/ssd/models --volume /home/user/jetson-inference/python/www/recognizer/data:/jetson-inference/python/www/recognizer/data
V4L2_DEVICES:     --device /dev/video0  --device /dev/video1
Unable to find image 'dustynv/jetson-inference:r36.2.0' locally
docker: Error response from daemon: manifest for dustynv/jetson-inference:r36.2.0 not found: manifest unknown: manifest unknown.
Indeed r36.2.0 missing https://hub.docker.com/r/dustynv/jetson-inference/tags 0 can you please push it ?
Additional info:
cat /etc/nv_tegra_release
R36 (release), REVISION: 2.0, GCID: 34956989, BOARD: generic, EABI: aarch64, DATE: Thu Nov 30 19:03:58 UTC 2023
root@ubuntu:~# apt-cache show nvidia-jetpack
Package: nvidia-jetpack
Version: 6.0-b52

Hi @plecluse, please try again now, I have pushed dustynv/jetson-inference:r36.2.0

Hi @dusty-nv , confirmed as working now – many thanks for your quick support - closing

@dusty-nv Thank you for the new docker interface! It works with docker/run.sh.
Unfortunately, when I run ~/Repos/jetson-inference$ docker/run.sh --ros=humble, I the issue appears again:
user@ubuntu:~/Repos/jetson-inference$ docker/run.sh --ros=humble
ARCH:  aarch64
reading L4T version from /etc/nv_tegra_release
L4T BSP Version:  L4T R36.2.0
CONTAINER_IMAGE:  dustynv/ros:humble-pytorch-l4t-r36.2.0
ROS_DISTRO:       humble
DATA_VOLUME:      --volume /home/user/Repos/jetson-inference/data:/jetson-inference/data --volume /home/user/Repos/jetson-inference/python/training/classification/data:/jetson-inference/python/training/classification/data --volume /home/user/Repos/jetson-inference/python/training/classification/models:/jetson-inference/python/training/classification/models --volume /home/user/Repos/jetson-inference/python/training/detection/ssd/data:/jetson-inference/python/training/detection/ssd/data --volume /home/user/Repos/jetson-inference/python/training/detection/ssd/models:/jetson-inference/python/training/detection/ssd/models --volume /home/user/Repos/jetson-inference/python/www/recognizer/data:/jetson-inference/python/www/recognizer/data
V4L2_DEVICES:     --device /dev/video0  --device /dev/video1
Unable to find image 'dustynv/ros:humble-pytorch-l4t-r36.2.0' locally
docker: Error response from daemon: manifest for dustynv/ros:humble-pytorch-l4t-r36.2.0 not found: manifest unknown: manifest unknown.
See 'docker run --help'.


Feature/basket simplification

Incomplete.

Ignore failure - aware of the issues.

Ready for review - given the DataQuery work I've not been able to thoroughly check whether the code handles all possibilities and I've still got a few aspects that I would like to discuss further but the code currently covers the majority of the logic outlined.


github action: unit test error

Your github action unit test references a "tests.py" file but there isn't any.

Yes, I also noticed that last night, but I guess, That is because that member just added a raw code because the unit test file was not available till then.

Your github action unit test references a "tests.py" file but there isn't any.

We haven't started yet any unittesting.


Add License: FPA General Code License

Reference to the Fairfield Programming Association General Code License can be found here: https://about.fairfieldprogramming.org/licenses/code.
The main benefit is that it separates the conditions between educational/ personal use and commercial use. The condition included in the commercial use section is significant modification- to prevent asset rips which are a problem in certain open source communities.

It does not meet the criteria for inclusion here as @nschonni points out.
Just a personal comment, the license seems very limited and or unclear. Is it (personal OR educational) AND noncommercial-unless-substantial-changes? What are "asset rips"?

Sorry- did not see the criteria about a 1,000 repository minimum.
On another note @mlinksva, many open-source projects in areas like Game Development or Tooling want to provide their code while also not closing themselves off to revenue steam. This MIT-style license allows community contribution and uses in personal and educational settings while also not allowing corporations from taking the project and putting it onto stores themselves (a very common situation in open-source asset store projects). In other words, yes, it is (personal OR educational) AND noncommerical-unless-substantial-changes

Limiting a particular group is a violation of 5, so it actually wouldn't be considered an open source license https://opensource.org/osd
If you've also modified an existing license without using a lawyer to validate it, you may not be protecting yourself as the resulting changes @mlinksva found confusing might also be found unenforcable by a court

@nschonni Yes- the license is legally binding as it was written by the legal professionals at the Fairfield Programming Association. As per not fitting into one organization's open-source definition, it is disappointing to hear about the lack of innovation that these rather closed organization have.

@William-McGonagle, Nick probably meant (6) fields of endeavor rather than (5). (2) pertains to a program, not its license. The OSD does not mandate a license require source code, but a program without source code is not OSS per that definition even it is under an open license.
OSD aside (clearly you have no intention for the license to conform to it, which is of course totally up to you), I'm idly curious about whether I didn't misread and it is not actually (personal OR educational) OR noncommerical-unless-substantial-changes. It isn't super clear to me which it is, but if it were AND I'm not sure what the commercial term is supposed to permit -- a for-profit educational institution to substantially change and use? I guess from your described use case above, you want to allow any commercial use if substantially changed, such as making a new game and selling it on an app store? (Just a question of idle curiosity/learning.)

ps not that you shouldn't make your own license, and indeed it's not quite the same, but noting it's a bit reminiscent of https://creativecommons.org/licenses/sampling/1.0/ and https://polyformproject.org/licenses/perimeter/1.0.0/

@mlinksva - Yes! I'm delighted to hear about your curiosity, though it may be idly 😉. The license is designed so that users can support their projects commercially while still making their code and knowledge public to the open-source world. The reason that the 'educational context' is included is because the Fairfield Programming Association is a non-profit focused on education, so we wanted to let educational institutions (schools, universities, etc.) use the projects without running into problems with the 'commerical' section of the license. We told this to legal, and they gave us the 'educational context' wording. From what they explained, the legal precedent would allow 501(c)(3) educational institutions and for-profit educational institutions to "use, copy, modify, merge, publish, and/ or distribute copies" but not "sell and/ or distribute".
One example of this is the MongoDB project, which has always been in collaboration with the community and switched its license to SSPL in 2018. They ran into a bit of a problem when it came to Amazon because Amazon simply forked the project for its own commercial gain. If say, MongoDB choose a semi-permissive, non-commercial license (I'm not really sure how else to word it) to start the project, they would have been able to keep this (FPA) license and pair it with a their own commercial license to sustain the project. Amazon would also be able to then fork the project and license it as its own if it significantly modified the code (Adding new features, making it lightweight, changing around the underlying systems, etc.) to make it its own type of MongoDB server.
I know it doesn't fit the case of MongoDB quite perfectly, but this would be how licensing with something like this would work. Also if a school or person wanted to host their own MongoDB server, they would fully be able to– outside of a commercial context (financially gaining).


Some classes don't load

e.g. Magic of Art 5/6, probably due to slash

Some of our classes also have the following characters in them which often cause problems when scraping data.
. " : , & ' - ?

@guberti, you'll probably want to adjust the normalizer to flatten all punctuation to '_'

Examples?


specs: namespaced padding shares

The current specs (on the specs-staging branch) don't specify the format of namespaced padded shares.

Closed by https://github.com/celestiaorg/celestia-app/pull/1248


upgrading @faker-js/faker to 8.1.0

Please check if the PR fulfills these requirements

[x] Followed the Contributing guidelines.
[x] Tests for the changes have been added (for bug fixes/features) with 100% code coverage.
[x] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
upgrading @faker-js/faker to 8.1.0

Codecov Report

Merging #603 (249aadc) into master (05dd29c) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@            Coverage Diff            @@
##            master      #603   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            5         5
  Lines          292       292
  Branches        75        75
=========================================
  Hits           292       292


Unsoundness with covariant type

Flow version: 0.156.0 (at least since 0.135.0)
Expected behavior
Making type generic does not introduce unsoundness.
Actual behavior

Link to Try-Flow or Github repo:
https://flow.org/try/#0PTAEBUCcE9UhTAtgewG4EsB2BzUAiAaj1AAt4EAaUAQwBtbRzJlIBnUAE3VeoAdf41SACgsAF3IAzagGN4oAIIy5vMa3AAeAuAB8oAN7CAkLJViAFGIBcEAJQ3UydBwDcwgL7DhkgK6YZYujImKA+rPCsSmYsGrrmpvCqLDZRiWqaulSodD7wNuC2Bl6e3n4BQSFhEalJkADCtNSsrLE65jK0rDYNTS016a06WTl5dkUeXh29oADKYpBY2P0soOiIvLRI8Jhqispp6hqs84t6hib7qpY2xws49qCOzuNGniVVkZdiLOaY8ADusxOOGWkHMtioeGoeFswg+oN+AKBdyWXx+ENAACZCiBQGISNxQKwSMgfLQOKBpOhaF54Wj6o1muY5ijQZDobC6dEGb1mcDUdyqNjQLj8YTiaTyZTqNSvMIxNABKAAPIAIwAVvAAgAxFig0AAXiKRmytFyN35E2EU2ayMWas1AX1aw2Wx27H6hwdWrEusgoLOxgSV2sKo1Pr9oMKhmMb1p4U+3MRgJZ9vDTvp4Ko+lN5vw0PcnITCL+Kf53ozSYx+kLcOLmdLdpwFbECOrudGmMLIrAYvYErJFKpNK5aRYPSZqeb6db9OztdHtQnrD5KJbbIMHZsULwC-r3OXq7Tjtngs3IxsXZxvYJ-ZJg+l1KAA

Context
Our Mithril definitions use types which looks similar to these:
export interface Vnode<Attrs> {
	attrs: Attrs,
	children: ChildArray,
	dom: HTMLElement,
}

declare interface Mithril {
	<AttrsT>(
		component: Class<MComponent<AttrsT>>,
		attributes: AttrsT,
		children?: Children
	): Vnode<any>;
}

interface MComponent<+Attrs> {
	/** Creates a view out of virtual elements. */
	view(vnode: Vnode<Attrs>): Children;
}

export type Child = Vnode<any> | string | number | boolean | null;
export type ChildArray = Array<Children>;
export type Children = Child | ChildArray;

declare var m: Mithril;

// --
// --
// --

type TestAttrs = {
	test: number,
}

class TestComponent implements MComponent<TestAttrs> {
	view(vnode: Vnode<TestAttrs>): Children {
		return String(vnode.attrs.test)
	}
}

function test(): Children {
	return m(TestComponent, {
		test: "c" // this should not be allowed
	})
}

Yep, this is a bug. We should not allow you to make Attrs covariant in the definition of MComponent, since it appears in an input position in the interface's definition.

Ah, of course, it should be contravariant, thanks!

This might be another issue but even when I declare it as contravariant (interface MComponent<-Attrs>) it accepts things like
m(TestComponent, {})

but at least not
m(TestComponent, { another: 2 })

Issue from your last message is likely due to Flow treating {} as an unsealed object.  You can spread null to achieve an empty object without it being unsealed: { ...null }.  See #7424


A project created in the organization from the CLI is not visible users with the developer role

A project created in the organization from the CLI is visible only to a user with the admin role, users with the developer role of the organization do not see this project. If created on the platform, all participants have access.
Steps:

Create a second GitHub account
Add an organization to the team as an admin of the GitHub organization
Add a developer to the team
On the CLI, create a project in the organization (it doesn't matter which user)
Log in to uffizzi platform as a user with the developer role
Open the organization's projects tab

Expected result: A project created in the CLI is displayed in the project list
Actual result: A project created in the CLI is not displayed in the project list

TESTED - OK


Current Firefox (46) cannot update broken SW

See this bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1267733
Basically, if SW is broken and throws an error for navigation request, so request document is never loaded and nothing can tell to Firefox to update SW.
Should we disable support SW for all Firefox version which do not have fix for that? I opinion is -- yes.

Fixed in Firefox 46.0.1

Yes, I know. Do, do you think we should block Fx versions prior that?
I now think we can just force SW update on Shift+Reload. This should cover those unfixed Fx and possible new browsers with same bug.

Okay, will make a force-update for Firefox prior 46.0.1.

Okay, I think we can ignore this since no one reports problems with it.


@layer at-rule not recognised

The new @layer at-rule is not recognised in the editor, and it seems to block hover information and color decorators from showing.
This is as of recently supported natively in CSS in most browsers, so it should definitely be supported in a postcss extension.

Apart from this, I'd like to thank you for this superb extension and for keeping it maintained! ☀

this should be fixed on latest version


update photos for MSR Modules

I took new photos of the EC30 MSR modules that I have. I think I followed the guidelines. I put them here If you like them please update them in the device catalog.

You can find the current pictures in https://github.com/microsoft/jacdac/tree/main/devices/microsoft-research and override them. Then the build will optimize them automatically and they will trickle up to the web site once we upgrade the submodule references.
Make sure your picture are 4:3 form factor


Error when trying to get the SID score of a predicted graph

I am working on windows, python version (3.9.1), cdt (0.5.23), pytorch (1.10.0).
I'm trying to predict the DAG of some discrete synthetic data. When I try to get the SID between a predicted graph and the ground truth using SID = cdt.metrics.SID(ground_truth, output), it throws up the error:
Traceback (most recent call last):
  File "C:\Users\order\Documents\Oxford\4th Year\4YP\Pyro practice\discovery6.py", line 139, in <module>
    SID = cdt.metrics.SID(ground_truth, output)
 File "C:\Users\order\Documents\Oxford\4th Year\4YP\Pyro practice\venv\lib\site-packages\cdt\metrics.py", line 273, in SID     raise ImportError("SID R package is not available. Please check your installation.")
ImportError: SID R package is not available. Please check your installation.
This looks like I haven't got SID installed, but when I run
print(cdt.utils.R.RPackages)
print(cdt.RPackages.check_R_package('SID'))
I get :
['init: False', 'pcalg: True', 'kpcalg: True', 'bnlearn: True', 'sparsebn: True', 'D2C: False', 'SID: True', 'CAM: False', 'RCIT: True']
True
showing SID should be installed and accessible. What's stranger is that when I include the two print statements in the same script, above the line where I call SID, I get a different error:
R Python Error Output
C:\Users\order\AppData\Local\Temp\cdt_SID_89751cd4-4522-437b-a1bd-e449092d8fac\result.csv not found.
Error in library(SID) : there is no package called 'SID'
Execution halted
Traceback (most recent call last):
  File "C:\Users\order\Documents\Oxford\4th Year\4YP\Pyro practice\discovery6.py", line 139, in <module>
    SID = cdt.metrics.SID(ground_truth, output)
File "C:\Users\order\Documents\Oxford\4th Year\4YP\Pyro practice\venv\lib\site-packages\cdt\metrics.py", line 296, in SID
raise e
File "C:\Users\order\Documents\Oxford\4th Year\4YP\Pyro practice\venv\lib\site-packages\cdt\metrics.py", line 288, in SID
    sid_score = launch_R_script(Path("{}/utils/R_templates/sid.R".format(os.path.dirname(os.path.realpath(__file__)))),
 File "C:\Users\order\Documents\Oxford\4th Year\4YP\Pyro practice\venv\lib\site-packages\cdt\utils\R.py", line 224, in launch_R_script
raise RuntimeError("RProcessError ") from None
RuntimeError: RProcessError
Any help would be greatly appreciated!

There isn't an issue when using a docker container so I'm assuming the problem is windows specific


Logging overhaul

Here we go. It’s not done yet:

The timing stuff isn’t yet implemented. I think we just do timing stuff when doing “info” level logging, correct?
If yes, we probably just need to override RootLogger.info so it sets self.handlers[0].formatter.passed_time = kwargs.get('t', False).

All the places hackily using _settings_verbosity_greater_or_equal_than(2|3) have to work differently. I propose that we just add a kwarg deepinfo: str or so which only adds the passed string to the message if the active verbosity is higher than the function’s (i.e. calling logging.warn('foo', deepinfo='bar') and the loglevel/verbosity is 'INFO' or noisier adds 'bar')

We now use vanilla log function syntax, so no more using it like print. We switched to Python 3.7+ though, so I propose f-strings everywhere! That looks better and works.

3\. We switched to Python 3.7+ though

No more support for python 3.6? That was a quick move from 3.5 support to only 3.7+...

Oh, whoops, 3.6 of course. That was the one introducing f-strings. Sorry, I’m not that good in ancient history :wink:

Very cool, @flying-sheep! Really the only concern I have is whether we need an option to prevent setting the timer (or for setting the timer) when calling logg.info...

I’m doing all the tests @ivirshup proposed. If my explanations to the questions I left open are sufficient, I’ll merge this! :smile:

OK, one more change. The log functions now all return the current time and have the optional parameter time: datetime. If you pass something there, the time will be logged:
start = log.info('foo')
# do stuff
log.hint('bar', time=start)  # --> bar (00:00:02)

You can customize where the time ends up via log.*('blah {time_passed}: blub', time=...)

Cool solution! Really cool new logging module! :)

logg.warning vs. logg.warn. I liked the short and verbal .warn better. I know there is some confusion, because of how python's core warning and logging modules possible, but meanwhile, several other packages have adapted Scanpy's logging module.
All of them now need to change each line from logg.warn to logg.warning and even I will tend to make a lot of errors being used to logg.warn (still most of the time using emacs without autosuggest...). So, as Isaac, I'd also like the equivalent logg.warn function but wouldn't even deprecate it.

Well, the logging module is undocumented, only logging.print_versions() is public. Python has warnings.warn and logging.warning. I think we should follow suit.
If you want you can of course do from warnings import warn and use that.


Typo in degradation example

In GitLab by @wtbarnes on Nov 22, 2019, 10:08
In the degradation example in the gallery, there is a typo in the description of the data download. It says we grab an image every year, but it should be every two years.

In GitLab by @wtbarnes on Feb 24, 2020, 21:16
closed via commit 8a7edd3a8205f0bdd77c20cce01bb1e5eb35da0a


Relax key-spacing slightly

The key-spacing rule can get a bit funky when properties in an object have other objects as values, reading to less readability than before the rule is applied! It also can cause issues with exceeding the max line length when it otherwise wouldn't if alignment was not happening on the property values. This tweak makes property keys have at least 1 space after the colon, allowing the values to aligned when it makes sense, or not when it doesn't.
Review

@ascott1
@wpears
@mistergone

:+1: from me

Side-issue: I'm not an expert with eslint (I can run it from the CLI!), so I try to read the documentation whenever our eslintrc changes. But checking on eslint.org and the eslint github repo, it seems like this should be mode: minimum instead of mode: minimal, so can someone point out what I'm missing?

@mistergone Right you are! Argh! I think I'll just open a new PR instead of pulling down this branch.

gooood catch @mistergone!

https://github.com/cfpb/front-end/pull/90


device width in viewport is fixed

https://issues.apache.org/jira/browse/CB-4323

Hi, we don't really track the issues on this repo and we ask that folks having problems with PhoneGap please use our forum:
https://forums.adobe.com/community/phonegap


Indicate plugin will compile on JDK 17

Fixes a build error on AGP 8

when u can merge it ?

Please merge this!!!!🙏🙏


Pin to an earlier version of es5-ext

@dw511214992 I'm going ahead and merging this to unblock some other pipelines. Please let me know if you see any issues with it later.


Usage of capturing the listener runnable as a CompletableFuture

          Wdyt about dropping this reference since its not referenced anywhere - the one on the DPMLC is still not referenced either so good bet we do not need the ref.

Originally posted by @onobc in https://github.com/spring-projects-experimental/spring-pulsar/pull/342#discussion_r1106589801

While we are not using it currently, this future gives us the ability to do something whenComplete like possibly log if failure occurs etc. We are not using it currently and that is ok. Closing this accordingly.


Backspace button for Dial Pad

JS widget:

RingCentral for Mac

From the screenshots above you can see that a Backspace button is missing from JS widget.
I noticed it the first time I used the Dial Pad.
And it is a must-have if we do have plan to support mobile.

Since this component is also used internally for one of our soon to be public production app, I am not exactly sure if we should just add the enhancement. If we are to modify this particular component, we need to talk to the PM's about it first, as well as define the behaviors we want with such changes.
However, if you are eager to make a prototype and submit it via PR, I think you can create a DialPad2 component that is based on the original and submit it as an enhanced version that we can use to use in certain apps.
What I think we'd also need is to discuss the need to have versioned components. I can anticipate that in our internally developed applications based on this lib, there will be cases where some apps requires certain features that are totally different than another. Rather than building all the features into one component and just use flags to turn them on/off, we can probably build them into different components that may (or may not) have a common base component.


Assign Task - "User can not be found..." appears when selecting existing user to Share

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

On LHN, click on the FAB button
Select Assign Task
Enter a title or description
Assign the task to yourself
On Share Somewhere, select a conversation with another user you have access to

Expected Result:
User should be able to select conversation to share the task. The task should be created and displayed in the conversation with the other user
Actual Result:
At first message "Invalid e-mail" is displayed. When continue to type "User can not be found..." appears when selecting existing user to Share Assign task with
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android / native
[ ] Android / Chrome
[x] iOS / native
[ ] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/78819774/8770c21b-34fb-4eda-9ce5-478bd374d80e
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub

Thanks @GItGudRatio! Agree this is intentional, unless you've chatted with the user before you won't be able to select them here.


Add Documentation for Gitpod

Description
Closes #229
Requirements

[x] how to use gitpod is documented in the contributing guide

Submitter checklist

[x] If the issue exists, it is well described and linked in the description
[x] The description of this pull request is detailed and explain why this pull request is needed
[x] The changeset is on a specific branch

feature/ for new feature, or improvements
fix/ for bug fixes
docs/ for any documentation changes

[x] If required, the documentation has been updated
[ ] There is automated tests to cover the code change / addition

If there is no test, include an explanation why in the description

[ ] Run mvn verify locally and all tests are passing successfully

It is OK to create a pull request which has failing tests if it is created as a draft, is to fix a bug and the first commit is the test to prove the existence of the bug.

[x] There is no new warnings (checkstyle nor spotbugs) on the code

Thank you so much for the review!


Not sure why this doesn't work, but commander package doesn't import when using this loader

So, if I use commander with my TypeScript code and try to run it using tsx - it doesn't work. commander is a very popular npm package.
Here are steps to reproduce:
nvm use 16
npm init -y
npm add commander
echo "import { program } from 'commander';" > index.mjs
npx tsx index.mjs

I get this:
SyntaxError: The requested module './index.js' does not provide an export named 'default'
    at ModuleJob._instantiate (node:internal/modules/esm/module_job:128:21)
    at async ModuleJob.run (node:internal/modules/esm/module_job:194:5)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:385:24)
    at async loadESM (node:internal/process/esm_loader:88:5)
    at async handleMainPromise (node:internal/modules/run_main:61:12)

However, using just pure node ... works. Setting "type": "module" and using .js extension has same effect.
The now deprecated https://github.com/antfu/esbuild-node-loader works fine with above steps.

Fixed in<EMAIL_ADDRESS>


Some PIPs can only be solved with a SLICEM LUTRAM endpoint

Some PIPs, such as "FAN_ALT0->>FAN_L0" cannot be solved with the current code.  The only place "FAN_ALT0->>FAN_L0" leads when going downhill looking for site pins is to a SLICEM AI pin.
The original code did not allow SLICEM pins at all to avoid having to correctly configure SLICEM's with all their special cases.
In #12 it was suggested that allowing SLICEM's but restricting the allowable site pins to be those on SLICEL's would let SLICEM's  be used but allow them to be treated like SLICEL's.  That worked for PIPs like "GFAN0->>BYP_ALT1" which tie to SLICEL-compatible pins on a SLICEM.  Sample code for this fix is given in #12, has been tested, and works for a subset of previously unsolved PIPs.
But, there are other PIPs like "FAN_ALT0->>FAN_L0" which only tie to SLICEM-only pins such as any of {WE, AI, BI, CI, DI} will not be reconstructed correctly.
Proposed fix: create a single LUTRAM instance that is legal (obeys all DRC rules) that is always used when any of these 5 pins are used.   Difficulty level: low?

Testing shows there are only 5 PIPs for this case.


Fix: Remove duplicate classes in nested polymorphic models

This is based on #283.
As discussed this is the fix for the issue that I'm seeing in the nested polymorphic model creation as separate pull request.
See issue #281 for detailed explanation

Moved to #285


Implement conditional requests using ETag

Fixes #104
Hey @softprops, here's my initial implementation. It's just an initial proposal and I'm happy to make adjustments as you see fit.  What I'm after is I'd like to have this functionality (in one shape or other) in hubcaps without having to maintain a fork of hubcaps, so any solution that avoids that is good for me.

Like the builder pattern.

Could you give an example of what you mean?

WDYT?

This impacts paging, I don't understand why. When the call is made to content no in the cache, all the content is fetched from GitHub, unfolding the pages. On the second call only the first page is uncached.
Do you know why that might be, @softprops?

apologies for dragging on this on @dwijnand I'm in the process of moving into a new apartment. I'll try to take a closer look soon. I haven't forgot about this pull!

I'm going to opt for iteration here. I'm trying to get better at not lerting pulls go stale. I'd be open to follow ups if needed. I want to roll out some of the recent changes so I'm trying to get as much as I can in. We can iterate on this

This impacts paging, I don't understand why. When the call is made to content not in the cache, all the content is fetched from GitHub, unfolding the pages. On the second call only the first page is uncached.

Fixed in #183.


'frameInterval' is deprecated

FLAnimatedImageView.m:299:26: 'frameInterval' is deprecated: first deprecated in iOS 10.0 - use preferredFramesPerSecond
0_0

There is any update on this warning issue.
'frameInterval' is deprecated: first deprecated in iOS 10.0 - preferredFramesPerSecond


@Singular clearXXX not recognized

When using the clearXXX methods for @Builder fields annotated with @Singular, you get a 'Cannot resolve method' error in the editor.  I am running version 0.11.16 of the plugin and IntelliJ Ultimate 2016.1.1.

Lombok features of v1.16.8 are not currently supported.  See #192

Support for clearXXX methods for @Builder and @Singular annotated classes will be available in the next release of plugin (>= 0.12)


⚠ Bofrost.de has degraded performance

In 61eb7e3, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1672 ms

Resolved: Bofrost.de performance has improved in 86701da after 6 minutes.


Time out server

When  I first installed geocoder in my project everything worked fine, but after a while I got this error: Error:
Timed out waiting for response from server.
And its not working anymore.
Please help! Thanks!

@alxgeoaln  Kindly check your internet connection. I am also facing the same issue. After check my internet connection , It works fine.


aarch64 build for AWS Linux - Failed to load image Python extension

🐛 Describe the bug
Built Torch 2.1.2 and TorchVision 2.1.2 from source and running into the following problem:
/home/ec2-user/conda/envs/textgen/lib/python3.10/site-packages/torchvision/io/image.py:13: UserWarning: Failed to load image Python extension: '/home/ec2-user/conda/envs/textgen/lib/python3.10/site-packages/torchvision/image.so: undefined symbol: _ZNK3c1017SymbolicShapeMeta18init_is_contiguousEv'If you don't plan on using image functionality from torchvision.io, you can ignore this warning. Otherwise, there might be something wrong with your environment. Did you have libjpeg or libpng installed before building torchvision from source?
previously the error was about missing libs and not undefined symbol, so I believe the libs are correctly installed now. Building says:
Compiling extensions with following flags:
   FORCE_CUDA: False
   FORCE_MPS: False
   DEBUG: False
   TORCHVISION_USE_PNG: True
   TORCHVISION_USE_JPEG: True
   TORCHVISION_USE_NVJPEG: True
   TORCHVISION_USE_FFMPEG: True
   TORCHVISION_USE_VIDEO_CODEC: True
   NVCC_FLAGS:
 Compiling with debug mode OFF
 Found PNG library
 Building torchvision with PNG image support
   libpng version: 1.6.37
   libpng include path: /home/ec2-user/conda/envs/textgen/include/libpng16
 Running build on conda-build: False
 Running build on conda: True
 Building torchvision with JPEG image support
   libjpeg include path: /home/ec2-user/conda/envs/textgen/include
   libjpeg lib path: /home/ec2-user/conda/envs/textgen/lib
 Building torchvision without NVJPEG image support
 Building torchvision with ffmpeg support
   ffmpeg version: b'ffmpeg version 4.2.2 Copyright (c) 2000-2019 the FFmpeg developers\nbuilt with gcc 10.2.0 (crosstool-NG <IP_ADDRESS>0_510dbc6_dirty)\nconfiguration: --prefix=/opt/conda/conda-bld/ffmpeg_1622823166193/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeh --cc=/opt/conda/conda-bld/ffmpeg_1622823166193/_build_env/bin/aarch64-conda-linux-gnu-cc --disable-doc --enable-avresample --enable-gmp --enable-hardcoded-tables --enable-libfreetype --enable-libvpx --enable-pthreads --enable-libopus --enable-postproc --enable-pic --enable-pthreads --enable-shared --enable-static --enable-version3 --enable-zlib --enable-libmp3lame --disable-nonfree --enable-gpl --enable-gnutls --disable-openssl --enable-libopenh264 --enable-libx264\nlibavutil      56. 31.100 / 56. 31.100\nlibavcodec     58. 54.100 / 58. 54.100\nlibavformat    58. 29.100 / 58. 29.100\nlibavdevice    58.  8.100 / 58.  8.100\nlibavfilter     7. 57.100 /  7. 57.100\nlibavresample   4.  0.  0 /  4.  0.  0\nlibswscale      5.  5.100 /  5.  5.100\nlibswresample   3.  5.100 /  3.  5.100\nlibpostproc    55.  5.100 / 55.  5.100\n'
   ffmpeg include path: ['/home/ec2-user/conda/envs/textgen/include']
   ffmpeg library_dir: ['/home/ec2-user/conda/envs/textgen/lib']
 Building torchvision without video codec support

So I believe I do have things set up correctly to be able to do image calls (I don't care about video). Any idea why I would still be getting the undefined symbol warning? Thanks!
Versions
Collecting environment information...
PyTorch version: 2.1.2+cu121
Is debug build: False
CUDA used to build PyTorch: 12.2
ROCM used to build PyTorch: N/A
OS: Amazon Linux 2023.3.20240304 (aarch64)
GCC version: (GCC) 11.4.1 20230605 (Red Hat 11.4.1-2)
Clang version: Could not collect
CMake version: version 3.28.3
Libc version: glibc-2.34
Python version: 3.10.9 (main, Mar  8 2023, 10:41:45) [GCC 11.2.0] (64-bit runtime)
Python platform: Linux-6.1.79-99.164.amzn2023.aarch64-aarch64-with-glibc2.34
Is CUDA available: True
CUDA runtime version: 12.2.140
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration: GPU 0: NVIDIA T4G
Nvidia driver version: 550.54.14
cuDNN version: Probably one of the following:
/usr/local/cuda-12.2/targets/sbsa-linux/lib/libcudnn.so.8.9.4
/usr/local/cuda-12.2/targets/sbsa-linux/lib/libcudnn_adv_infer.so.8.9.4
/usr/local/cuda-12.2/targets/sbsa-linux/lib/libcudnn_adv_train.so.8.9.4
/usr/local/cuda-12.2/targets/sbsa-linux/lib/libcudnn_cnn_infer.so.8.9.4
/usr/local/cuda-12.2/targets/sbsa-linux/lib/libcudnn_cnn_train.so.8.9.4
/usr/local/cuda-12.2/targets/sbsa-linux/lib/libcudnn_ops_infer.so.8.9.4
/usr/local/cuda-12.2/targets/sbsa-linux/lib/libcudnn_ops_train.so.8.9.4
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True
CPU:
Architecture:                       aarch64
CPU op-mode(s):                     32-bit, 64-bit
Byte Order:                         Little Endian
CPU(s):                             4
On-line CPU(s) list:                0-3
Vendor ID:                          ARM
Model name:                         Neoverse-N1
Model:                              1
Thread(s) per core:                 1
Core(s) per socket:                 4
Socket(s):                          1
Stepping:                           r3p1
BogoMIPS:                           243.75
Flags:                              fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs
L1d cache:                          256 KiB (4 instances)
L1i cache:                          256 KiB (4 instances)
L2 cache:                           4 MiB (4 instances)
L3 cache:                           32 MiB (1 instance)
NUMA node(s):                       1
NUMA node0 CPU(s):                  0-3
Vulnerability Gather data sampling: Not affected
Vulnerability Itlb multihit:        Not affected
Vulnerability L1tf:                 Not affected
Vulnerability Mds:                  Not affected
Vulnerability Meltdown:             Not affected
Vulnerability Mmio stale data:      Not affected
Vulnerability Retbleed:             Not affected
Vulnerability Spec rstack overflow: Not affected
Vulnerability Spec store bypass:    Mitigation; Speculative Store Bypass disabled via prctl
Vulnerability Spectre v1:           Mitigation; __user pointer sanitization
Vulnerability Spectre v2:           Mitigation; CSV2, BHB
Vulnerability Srbds:                Not affected
Vulnerability Tsx async abort:      Not affected
Versions of relevant libraries:
[pip3] numpy==1.26.4
[pip3] torch==2.1.2+cu121
[pip3] torchaudio==2.1.2
[pip3] torchvision==0.16.2+cu121
[pip3] triton==2.1.0
[conda] numpy                     1.26.4                   pypi_0    pypi
[conda] torch                     2.1.2+cu121              pypi_0    pypi
[conda] torchaudio                2.1.2                    pypi_0    pypi
[conda] torchvision               0.16.2+cu121             pypi_0    pypi
[conda] triton                    2.1.0                    pypi_0    pypi

 [pip3] torchvision==0.16.2+cu121
 [conda] torchvision 0.16.2+cu121 pypi_0 pypi

Try uninstalling these versions first?

 [pip3] torchvision==0.16.2+cu121
 [conda] torchvision 0.16.2+cu121 pypi_0 pypi

Try uninstalling these versions first?

What would that accomplish? That's literally the package that I'm trying to use and that is throwing the error.

Built Torch 2.1.2 and TorchVision 2.1.2 from source

What version of torchvision are you building from source, exactly? There's no torchvision 2.x. The latest stable version is 0.17.
The fact that there already is a stable 0.16.2 version installed while you're trying to build from source is very likely to be causing some issues.

Built Torch 2.1.2 and TorchVision 2.1.2 from source

What version of torchvision are you building from source, exactly? There's no torchvision 2.x. The latest stable version is 0.17.
The fact that there already is a stable 0.16.2 version installed while you're trying to build from source is very likely to be causing some issues.

Updated original post, torchvision version was a typo.
I did finally get torchvision to build and be functional, but only by forcibly editing the build scripts to pull in my custom build of torch+cuda 2.1.2. The build scripts were importing a non-cuda build because there is no aarch64 torch+cuda out there for pip to pull down. So finally, after forcing my own torch+cuda 2.1.2 whl into the torchvision build, now my torchvision actually works.
I need to say - it's been PAINFUL dealing with building anything that relies on torch because all the build scripts pull down the non-cuda version and mess up the builds. Every time I want to build something relying on torch, now I need to hack in pulling my own torch whl instead for them to work (this also resolved issues I was having building a few other things).
I reaaaaaally hope official aarch64 torch+cuda builds start to be made available so I don't have to keep doing this hackjob.

The box is shut down but I believe it was pyproject.toml that I had to update to point directly at my torch whl and the command I used was "python setup.py bdist_wheel". I had the same outcomes with "pip install -v ." to directly install, though.


Add VsCode support for pydoclint

Since flake8 has been removed, VsCode no longer provided feedback during development about new docstring errors.
This PR add a new task called pydoclint that runs pydoclint in the background.  Message from pydoclint are parsed with a regex and presented in the problems tab of VsCode by the task.
VsCode does not have native support for running a task on save, so a new extension is added to support that.
The flake8 extension is removed which was an oversight in #4235
Related #4236

Gonna merge this one so it can be carried over to other projects


Remove process.exit calls in the error path

I wanted to put less into a long running server side process. However, the process.exit calls prevent that. These commits are the first step to making less integration possible.
deb5b3ec is really the only commit that contains that change. However, I believe the rest of the patches here are useful as well:

I integrated poswald's 'watch' option to command line lessc, and then fixed it to run immediately on startup (9a42c364).
fd107ce1 -- patch for moving to the recommended method of not modifying require.paths, and using relative requires for local sources.
a95f9caf	-- fixes a failing test
6d27d0bc -- adds a test for less.render

Thanks

Following up the discussion from #246:
process.exit called from importer:
https://github.com/cloudhead/less.js/blob/master/lib/less/index.js#L119
But, beyond the process.exit calls (which I needn't have removed from bin/lessc btw) is the pervasive use of throw everywhere that leads to uncatchable exceptions. For example, create a less file like this: "body {" and try compiling it with lessc -- you don't get the nice error output from less.writeError, you get an extremely short stack trace from an uncaught exception.

Ah yes, I will look into that. The error handling needs a revamp for sure, as some errors, as you noticed, don't output nicely.


Fixes and tests related to the Indexer process.

Three bugs fixed:

Indexers would not announce themselves as segment servers if they
did not have storage locations defined. This used to work, but was
broken in #9971. Fixed this by adding an "isSegmentServer" method
to ServerType and updating SegmentLoadDropHandler to always announce
if this method returns true.

Certain batch task types were written in a way that assumed "isReady"
would be called before "run", which is not guaranteed. In particular,
they relied on it in order to initialize "taskLockHelper". Fixed this
by updating AbstractBatchIndexTask to ensure "isReady" is called
before "run" for these tasks.

UnifiedIndexerAppenderatorsManager did not properly handle complex
datasources. Introduced DataSourceAnalysis in order to fix this.

Test changes:

Add a new "docker-compose.cli-indexer.yml" config that spins up an
Indexer instead of a MiddleManager.

Introduce a "USE_INDEXER" environment variable that determines if
docker-compose will start up an Indexer or a MiddleManager.

Duplicate all the jdk8 tests and run them in both MiddleManager and
Indexer mode.

Various adjustments to encourage fail-fast errors in the Docker
build scripts.

Various adjustments to speed up integration tests and reduce memory
usage.

Add another Mac-specific approach to determining a machine's own IP.
This was useful on my development machine.

Update segment-count check in ITCompactionTaskTest to eliminate a
race condition (it was looking for 6 segments, which only exist
together briefly, until the older 4 are marked unused).

Javadoc updates:

AbstractBatchIndexTask: Added javadocs to determineLockGranularityXXX
that make it clear when taskLockHelper will be initialized as a side
effect. (Related to the second bug above.)

Task: Clarified that "isReady" is not guaranteed to be called before
"run". It was already implied, but now it's explicit.

ZkCoordinator: Clarified deprecation message.

DataSegmentServerAnnouncer: Clarified deprecation message.

https://github.com/apache/druid/issues/10538 and https://github.com/apache/druid/issues/10258 will be fixed by this PR. Perhaps https://github.com/apache/druid/issues/9820 as well.

#10538 and #10258 will be fixed by this PR. Perhaps #9820 as well.

I agree, it should fix all of those. I commented in those patches.

One test left. Trying to figure out what the problem is with "Kafka index integration test with various formats". Strangely, the Indexer version works fine, but the MM version is busted.

One test left. Trying to figure out what the problem is with "Kafka index integration test with various formats". Strangely, the Indexer version works fine, but the MM version is busted.

I ran it locally and it passed. It might be flaky; I'll try running it again in CI.


Get Netlify Function to work when deployed to Netlify

I can get the Netlify Function to work locally but in Netlify get this message: errorMessage":"Cannot find module 'axios'". This despite axios being in token-hider's package.json.
I still get error if I change package.json to include these:-
"prod": "npm run build && npm run build:lambda",
"build:lambda": "netlify-lambda build functions"
After adjusting command in netlify.toml to "npm run prod", the following deploy error in Netlify results:-
Error: netlify-lambda Error: Function source folder (specified in netlify-lambda serve/build command) and publish folder (specified in netlify.toml) should be different. They are both set to /opt/build/repo/functions.This is a common mistake for people switching from Netlify Dev to netlify-lambda. For an easy fix, change your functions key inside netlify.toml to something else, like "functions-build".
If I then change functions key in netlify.toml as suggested, then just get 404 pages for the functions.
How to get the Netlify Function token-hider working both locally and in Netlify when deployed?
Thanks

hard to tell without a repro. are you sure you need netlify-lambda? you may not need it.

I was referring to other repos, for another Gatsby starter. Your repo works fine, both locally and after Netlify Deploy, whether or not the Deploy by Netlify button is clicked.
After studying your files, I found there is much in your starting repo which is not commented on in the README. This is a bit misleading if one does not use the deploy button. Here is what I believe must be included in a repo for Netlify Function to work:-

Install gatsby-plugin-netlify-identity @reach/dialog @reach/tabs @reach/visually-hidden react-netlify-identity-widget gatsby-plugin-netlify-identity
add devDep "netlify-lambda": "^1.6.3",
add netlify.toml
put function in functions-src folder
Add to package.json this script:- "postinstall": "netlify-lambda install",
add react-netlify-identity-widget in gatsby-config.js

With all these inclusions the function worked in other repos after deploying to Netlify.

ah ok. may need more work on docs. happy to take PR if you wanna help :)


Demonstrate task runner use cases expressed in terms of async channels

The goal is to write a test module/s that makes use of async channels as we envision employing them to  launch and coordinate:

Long-running tasks (e.g. running nim-waku or status-go on its own thread).
Short-running tasks that are async I/O dominated. (e.g. many concurrent async http requests running on a shared thread).

Note that long-running tasks will need to support bidirectional communication between the running task and the launcher of the task.
For short-running async I/O tasks the pattern is expected to look more like "request-response", albeit through the lens of async channels.
A separate issue will be created to track development of the API offered by import task_runner, which should encapsulate the setup and usage of async channels for those types of tasks. In other words, developing the task_runner API outright is not the goal for this issue.

Work has been started in PR #7.


Report policy revision implemented by the proxy in Endpoint model

This PR plumbs the Repository revision and endpoints into the NetworkPolicyDiscoveryService, where these are cached and associated with NetworkPolicyCache versions. When Envoy receives the relevant resources and acknowledges them, it looks up in this cache to determine which policy revision is being acked and calls back into the endpoint objects to update a new field, proxyPolicyRevision.
For more details, see #3144.
Fixes: #3122
Fixes: #3144

test-me-please

test-me-please

test-me-please

test-me-please

Something fishy happening in the unit tests, upserts into AckingNetworkPolicyMutator are not showing up in NetworkPolicyCache.

@joestringer Maybe the order of initialization of variables in resources.go?

You could move the initialization of the variables into an init()? Or move that into the StartXDSServer() in pkg/envoy/server.go.

@joestringer which unit tests are failing?

@rlenglet DaemonEtcdSuite.TestRemovePolicy is failing, it sees an empty NetworkPolicyCache.
I tried shifting the mutator update into an init() in pkg/envoy/resources.go, that didn't work. Will try the StartXDSServer() approach next.

I think the problem is that we moved updateNetworkPolicy() but the tests are expecting it to be updated during dry runs. Fix incoming.

test-me-please

test-me-please

test-me-please

Good call.
You should just call d.l7Proxy.UpdateNetworkPolicy with a nil WaitGroup.

test-me-please

test-me-please

The last test failed. A priori unrelated to this PR. This test seems flaky.

Suspecting another test flake in tests PolicyEnforcement updates, will re-run.

test-me-please

@tgraf could you please review this? Thanks!


feat: add artifact_name option

close #6
I just added the artifact_name setting. The description is not written. Can you please? @AlexTMjugador
TODO

[x] Add option: artifact_name
[ ] Add description to yml (action.yml)
[ ] Add description to readme (README.md)

Test
name: Test - Change Artifact Name
on: [workflow_dispatch]
jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - name: Clone repository
        uses: actions/checkout@v2
        with:
          fetch-depth: 0
      - name: Run PackSquash
        uses: ./ # Uses an action in the root directory
        with:
          path: test/empty_resource_pack
          artifact_name: Test Artifact Name

https://github.com/sya-ri/PackSquash-action/actions/runs/1718311242

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

Thank you so much! The changes look great, as usual :heart:
I'll write the descriptions you asked and squash merge the PR.

Thank you <3


Fixed non string fields not rendering

We use snippet fallbacks and try to render everything by using
snippet values. However, non-string fields will not have
fallbacks. Because of this, we need to use raw values. Raw values
must be html safe to be considered safe to use.

LGTM. 👍


[tbb] update to <2021.2.0>

Library name: tbb
New version number: 2021.2.0
Please update it.

@byxrolland , Thank you for posting this issue!.
Issue #15152 use new CMake build system to 2021.1.1, but the fix pr #16321 need Upstream fix or response,so Please waiting for official response. then i will update tbb to the latest version

It can be updated now I guess.

It can be updated now I guess.

Please wait for  pr #16321 merged

TBB 2021.3.0 is available: https://github.com/oneapi-src/oneTBB/releases/tag/v2021.3.0

latest is 2021.5.0 reference: https://github.com/oneapi-src/oneTBB/releases

The only thing that block this issue is https://github.com/PixarAnimationStudios/USD/issues/1471

@JackBoosY close? tbb was updated wasn't it ?

@JackBoosY close? tbb was updated wasn't it ?

Yes, finally.


bad case on filenames in the solution .sln

bad case on filenames in the solution .sln

forget ?

Done. The problem was already solved in last version.

YAHOUU ! thanks a lot @Yobatman38
so, did you check if you can close the ticket at:
https://github.com/orgs/OrbitalShell/projects/1#card-55149732
this would be the first ticket closed on the project (in this version). so you collect all the first times, with 'first pull request'.
what will be your next first ? 🤸♀

i got the response now 🙄

the ticket moves in real timesin my navigator when you make it change column. nice software

Oh yeaah !

if you like smiley like me, just type : and try to input the name of one of this extended unicode symbol 💩