boot2docker download error (SSL)

Can anyone give me workarounds for this if not a solution? I sense that this is not boo2docker's fault and if so would just like to know if there is a manual process I can take here.
⧑ boot2docker download
2014/07/10 12:38:10 Downloading boot2docker ISO image...
2014/07/10 12:38:10 Failed to get latest release: Get https://api.github.com/repos/boot2docker/boot2docker/releases: x509: certificate signed by unknown authority

This is more or less easy to solve,
The start script is not able to locate your iso image.
Fire up a Termine (git shell) and execute "echo $HOME"
the default location where the start.sh is looking for the iso is "$HOME/.boot2docker/boot2docker.iso"
Place the iso there or relocate your home by setting the Environment var

I'm using the latest boot2docker release and have this problem too.

Boot2Docker-cli version: v1.5.0
Git commit: ccd9032

However, I can download the releases file by wget like below

wget https://api.github.com/repos/boot2docker/boot2docker/releases
--2015-03-18 22:14:38--  https://api.github.com/repos/boot2docker/boot2docker/releases
Connecting to <IP_ADDRESS>:8087... connected.
Proxy request sent, awaiting response... 200 OK
Length: 108566 (106K) [application/json]
Saving to: 'releases'

releases                                100%[===============================================================================>] 106.02K  57.4KB/s   in 1.8s

2015-03-18 22:14:42 (57.4 KB/s) - 'releases' saved [108566/108566]

Any thoughts?

I have a similar problem (running OS X 10.9.5):
% boot2docker upgrade
docker is up to date (1.6.2), skipping upgrade...
error in run: Error upgrading boot2docker binary: Error attempting to get the latest boot2docker-cli release: Get https://api.github.com/repos/boot2docker/boot2docker-cli/releases: x509: certificate signed by unknown authority

Having similar issue on Yosemite (10.10.3).  I'm behind HTTP & HTTPS proxies with MITM spoofed CAs.  Here's what's happening:
➜  ~  boot2docker -v init
Boot2Docker-cli version: v1.6.2
Git commit: cb2c3bc
2015/05/27 09:07:28 executing: VBoxManage showvminfo boot2docker-vm --machinereadable
error in run: Failed to get latest release: Get https://api.github.com/repos/boot2docker/boot2docker/releases: x509: certificate signed by unknown authority

I have my corporate CA installed - curling that URL directly works:
➜  ~  curl https://api.github.com/repos/boot2docker/boot2docker/releases |head
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0[
  {
    "url": "https://api.github.com/repos/boot2docker/boot2docker/releases/1293985",
    "assets_url": "https://api.github.com/repos/boot2docker/boot2docker/releases/1293985/assets",
    "upload_url": "https://uploads.github.com/repos/boot2docker/boot2docker/releases/1293985/assets{?name}",
    "html_url": "https://github.com/boot2docker/boot2docker/releases/tag/v1.6.2",
    "id": 1293985,
    "tag_name": "v1.6.2",
    "target_commitish": "master",
    "name": "v1.6.2",
<snip>

I found a work around, it's pretty...heavy handed but it worked.
I hadden't updated boot2docker for a while, so i went ahead and did a boot2docker upgrate, i got this error:
12:09:17 ~ > docker ps -a
2015/07/02 12:09:22 Get https://<IP_ADDRESS>:2376/v1.15/containers/json?all=1: x509: certificate is valid for <IP_ADDRESS>, <IP_ADDRESS>, not <IP_ADDRESS>
12:09:22 ~ > boot2docker -v init
Boot2Docker-cli version: v1.3.1
Git commit: 57ccdb8
2015/07/02 12:12:47 executing: VBoxManage showvminfo boot2docker-vm --machinereadable
Virtual machine boot2docker-vm already exists

I went ahead:
rm ~/.boot2docker

then Removed the VM from virtualbox
then
12:15:22 ~ > boot2docker init
Latest release for boot2docker/boot2docker is v1.7.0
Downloading boot2docker ISO image...
Success: downloaded https://github.com/boot2docker/boot2docker/releases/download/v1.7.0/boot2docker.iso
	to /Users/jasghar/.boot2docker/boot2docker.iso

then
12:16:43 ~ > boot2docker start
Waiting for VM and Docker daemon to start...
.......................ooooooooooooooooo
Started.

and yay it worked:
12:17:20 ~ > docker run hello-world
Unable to find image 'hello-world' locally
latest: Pulling from hello-world
a8219747be10: Pull complete
91c95931e552: Already exists
hello-world:latest: The image you are pulling has been verified. Important: image verification is a tech preview feature and should not be relied on to provide security.
Digest: sha256:aa03e5d0d5553b4c3473e89c8619cf79df368babd18681cf5daeb82aab55838d
Status: Downloaded newer image for hello-world:latest
Hello from Docker.
This message shows that your installation appears to be working correctly.

To generate this message, Docker took the following steps:
 1. The Docker client contacted the Docker daemon.
 2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
    (Assuming it was not already locally available.)
 3. The Docker daemon created a new container from that image which runs the
    executable that produces the output you are currently reading.
 4. The Docker daemon streamed that output to the Docker client, which sent it
    to your terminal.

To try something more ambitious, you can run an Ubuntu container with:
 $ docker run -it ubuntu bash

For more examples and ideas, visit:
 http://docs.docker.com/userguide/


Module request: inadyn

ddclient was removed in #241462, with inadyn being the closest suggested replacement. inadyn is packaged in Nixpkgs, but does not have a NixOS module. An inadyn NixOS module would be useful as a replacement.

The first step is fixing inadyn itself, since it currently won't start due to a wrongly configured localstatedir, see #243785.

We will also need to decide if it's better to run as a systemd service, timer, or give the user the option to choose. I lean towards the latter.

AFAICS inadyn does not contain additional logic to detect IP address changes. Because of this I would also lean towards the timer functionality.

I think it does. Looking at inadyn.conf(5), inadyn will only update the ip if changed every preroid seconds and always update it every forced-update seconds. I'm not clear on how those options behave in oneshot mode.

Well, so far I called ddclient with cron, since the machine running will not easil see altered public IP change. I tried to use inadyn but can't get it to work with desec.io / dedyn.io.

I've had some time to poke around this a bit more, and it seems like inadyn cannot read credentials from the environment or a file separate to the config, so all your DDNS credentials will end up world-readable in the store.

I've made a pretty barebones module for my personal config here https://gitlab.com/lunik1/nix-config/-/blob/master/modules/system/inadyn.nix?ref_type=heads. It runs inadyn in oneshot mode using a timer, and is configured entirely by specufying a configFile.

Submitted a full NixOS module as https://github.com/NixOS/nixpkgs/pull/260962, I would appreciate if inadyn users could test it :slightly_smiling_face:.

Submitted a full NixOS module as #260962, I would appreciate if inadyn users could test it 🙂.

Add a small example for how to use it?

Sure, here's a config to use namecheap:
  services.inadyn = {
    enable = true;
    # controls how often your IP is checked, should be a format a systemd timer will understand
    interval = "*-*-* *:*:00";
    # these settings map 1:1 to those in inadyn.conf, check inadyn.conf (5)
    settings = {
      allow-ipv6 = false;
      forced-update = 60;
      custom."namecheap" = {
        # you can use include to keep your auth info in a seperate file and manage it with e.g. sops-nix
        include     = ./auth.txt;
        ddns-server = "dynamicdns.park-your-domain.com";
        ddns-path   = "/update?domain=%u&password=%p&host=%h&ip=%i";
        hostname    = [ "@" "*" ];
      };
    };
    # alternatively to settings, just speify a full config file
    # configFile = ./your/existing/inadyn.conf;
  };


Ignore lock files

Lock files are a good idea for full applications but they're kinda overkill for library-style projects like this one. So ignore the npm5/yarn-generated lock files for now to reduce noise.


chore: fix reviewers team

Could we use @containers/podman-desktop-reviewers even if it is a different organization?

it seems the file is invalid (team is not having access)

LGTM but the group misses some members like Axel and Tim https://github.com/orgs/redhat-developer/teams/podman-desktop-reviewers

Florent removed them temporaly because they did not update their GitHub status

it seems the file is invalid (team is not having access)

Should be good now

Florent removed them temporaly because they did not update their GitHub status

Ah right, i forgot. Ok 👍


Update user invite controller

pass office_id to controller
Display users' office on index and details view
improved tests to ensure data sent to controller

Go, merge.


Update the docs index page

Minor changes:

Fix location of search bar
Make note of 3.4 release, and a more general statement to update between them.

Major Changes:

Add an ordered list of items to install an OSG site.
Change order so that installation of CE is before WN.

Updated @brianhlin


dbt run hangs after getting list of object from database

Describe the bug
Running dbt CLI from a Windows server, we noticed sometimes that the run hangs undefinetely without executing any model.
Looking at Snowflake query history, we see a "show terse" command for each schema, a begin/commit and then nothing else (see attached screenshot).
This happened with different selections, so seems not related to specific models.
We tried adding dbt.exe in our antivirus whitelist, but without any effect.
We saved a dbt.log of one of these strange executions, but we didn't notice any error message (see attached log).
Steps To Reproduce
This behaviour happens randomly, we've not been able to systematically reproduce it.
Expected behavior
dbt should go ahead and run the selected models.
Screenshots and log output
dbt_stg_2021-07-20_14-10-15.17.log

System information
Which database are you using dbt with?

[ ] postgres
[ ] redshift
[ ] bigquery
[x] snowflake
[ ] other (specify: ____________)

The output of dbt --version:
installed version: 0.19.0
   latest version: 0.20.0

Your version of dbt is out of date! You can find instructions for upgrading here:
https://docs.getdbt.com/docs/installation

Plugins:
  - bigquery: 0.19.0
  - postgres: 0.19.0
  - redshift: 0.19.0
  - snowflake: 0.19.0

The operating system you're using:
Windows Server 2016 Datacenter
The output of python --version:
Python 3.7.9

@danielefrigo Thanks for the report. It's hard to know exactly what's going on here, and I imagine it's going to be difficult to reproduce.
Based on the logs you've attached, it looks like the metadata queries are returned successfully, and the adapter cache manages to populate. Then, when dbt goes to run two models, each in its own thread, it just hangs there:
2021-07-20 12:11:03.191447 (MainThread): 14:11:03 | Concurrency: 8 threads (target='prod')
2021-07-20 12:11:03.191447 (MainThread): 14:11:03 |
2021-07-20 12:11:03.191447 (Thread-1): Began running node model.dwh.BILLING_PRICE__STG
2021-07-20 12:11:03.191447 (Thread-2): Began running node model.dwh.BILLING_STAGE__STG

Could you guess at how often you see this happen? Is this every other run, every 10th, every 100th?

it's probably every 10th run (more or less).
if I look at a log for a good run, I see that next step is acquiring a snowflake connection.
is it possible that dbt for some reason cannot acquire a new connection to run the models?
do you expect to see some specific error if this is the case?

If dbt is able to connect to Snowflake to run the first metadata queries (show terse objects), I'd think that it should be able to acquire subsequent connections to run specific models.
I'm still not sure what's going on here. Could it be an issue with threading, when multiple models kick off to run in the same instant? One way to check would be by running with threads: 1, and seeing if this bug surfaces.

in the past days we run the job almost 20 times with 1 thread and it never hanged, so your idea could be correct


[MM-23670] Improve formatting of Channel header change message

Summary
Make update header message easier to read.

I took some liberties on where to put break lines in Japanese, Korean, Turkish, Chinese (simplified), and Chinese (Taiwan)

Ticket Link
github issue was created at server repo -> Fixes https://github.com/mattermost/mattermost-server/issues/14256
jira ticket -> https://mattermost.atlassian.net/browse/MM-23670
Related Pull Requests
n/a
Screenshots

Hello @lestgabo,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

I didnt run npm run check ill fix asap, I see where the lint failed.

Will try to auto merge this PR once all tests and checks are passing. This might take up to an hour.

Trying to auto merge this PR.

Pull Request successfully merged
SHA: e0a78f74625db8e3cb097599a8094f15ac87bd00


ListAndWatch only sends device if the list has changed

Signed-off-by: Harrison Tin<EMAIL_ADDRESS>
What this PR does / why we need it:
As suggested here, the change keeps a vector of previously returned virtual devices and only send updates to kubelet if the list has changed.
It closes #379
Special notes for your reviewer:
Test: passed all unit tests, and manually tested it with some debug messages.
If applicable:

[ ] this PR has an associated PR with documentation in akri-docs
[ ] this PR contains unit tests
[ ] added code adheres to standard Rust formatting (cargo fmt)
[x] code builds properly (cargo build)
[ ] code is free of common mistakes (cargo clippy)
[x] all Akri tests succeed (cargo test)
[ ] inline documentation builds (cargo doc)
[ ] all commits pass the DCO bot check by being signed off -- see the failing DCO check for instructions on how to retroactively sign commits

@harrison-tin I think with the latest merge there's a clippy error that popped up

/version patch

@harrison-tin @adithyaj are we good to merge this?

@harrison-tin @adithyaj are we good to merge this?

yep LGTM. I can go ahead and merge it.


[SPARK-6765] Fix test code style for mllib.

So we can turn style checker on for test code.

LGTM.

Test build #29839 has started for   PR 5411 at commit d8a2569.

Test build #29839 has finished for   PR 5411 at commit d8a2569.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.
This patch does not change any dependencies.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/29839/
Test PASSed.


Make it easier to contribute

[x] Add dev instructions in the README
[x] Add a coder.com or stackblitz thing

Coder.com is free when self-hosted, so I went with Stackblitz


Ameerul / FEQ-2676 The loader icon is shifted towards the left corner of the screen when loading p2p.deriv.com

Wrapped Suspense Loader component in a div to position it in the centre.

https://github.com/user-attachments/assets/80878213-4370-4716-8749-7cbeea7aecad

Pull Request Test Coverage Report for Build<PHONE_NUMBER>9
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 85.411%

Totals

Change from base Build<PHONE_NUMBER>7:
0.0%

Covered Lines:
5931

Relevant Lines:
6476

💛  - Coveralls


Sonar Cloud plugin for Policy style checks

There was a project called Apollo that performed style and flow checks on policy. Use the idea's behind the Apollo project to create a Sonar Cloud plugin that will perform checks on policy. https://docs.sonarqube.org/display/PLUG/Plugin+Library
I would be able to run something like:
./gradlew check
This should then return policy style checks and warnings.
I should also be able to setup a build that will send the policy to sonar cloud for validation.

Tracked internally by F81666


Write Bendo test Program

I think this issue is too vague. We have the bstress program. A new, more detailed, ticket should be used if bstress is not good enough.


AFEW8.0的数据集

您好，可以发一份数据集吗？在官网不能下载啊，给个百度云链接，可以吗，谢谢

Could you please send an email to the organizer to ask for the AFEW dataset? I think they will share the dataset with you.
EmotiW Organizer Email：
1<EMAIL_ADDRESS>2<EMAIL_ADDRESS>

请问你们拿到了数据集嘛

@LinQinLiang @zhichao711
Merry Christmas! I recently update the Emotion-FAN, new features include data process, environment install, CK+ code, and Baseline code. Also, you can find the old version directory of Emotion-FAN in the README.md. I hope my new updates can help you greatly. Please see the Emotion-FAN for more details.


Is it possible to specify parameter constraints in scipy.odr?

I'm interested in using scipy.odr to fit a nonlinear model, but in some cases the fitted parameters become unrealistically large. Before using ODR I used scipy.optimize.curve_fit to fit my models, where I could specify constraints using the "bounds" option, but I now need to use ODR because curve_fit didn't allow for uncertainties in both my y and x to be accounted for in the fit.
From what I can tell, in scipy I can either have my fit parameters constrained, or have an errors-in-variables model, but not both. Is there any way to do this in scipy, or indeed in Python at all?

No, the version of ODRPACK that we wrap does not support constraints.


Store module annotations in meta model

Right now no annotations placed on the module descriptor are stored in the meta model, eg:
native("js")
module test "1.0.0" {
}

This is needed for https://github.com/ceylon/ceylon-spec/issues/946 and https://github.com/ceylon/ceylon-spec/issues/499

They are in the metamodel; available at runtime only. But the model used for compilation indeed doesn't have them.

Package annotations also aren't stored in the model BTW

OK I think this is done but please check @quintesse

Tests confirm this is done.


[FEA] Possible improvements to Qualification tool

Is your feature request related to a problem? Please describe.
Here are a few things I've found during migrating some jobs we may want to look at more to see if Qualification tool can give us hints about.  ie perhaps configs to use or things for user to look for.

look for explicit settings of shuffle.partitions and max partition bytes... others?  I had a case CPU side has shuffle partitions set and that job was spilling which caused slowness in transitioning to GPU
Look for spilling
look for heavily skewed tasks
summarize IO to total bytes intput/output/shuffle read remote/shuffle read local/shuffle write/spilled

duplicate of #1152


Add instructions for building the App

In relation to issue #1, I think it would be a good start to have build instructions,

Build instructions were added to the Wiki: https://github.com/chRyNaN/Android-Guitar-Tuner/wiki/How-To-Build


Create DB function to get all checkpoint data

Background
We need to read all the measurements across a checkpoint of certain name within a flow.
Feature
Create a DB function that will return all checkpoint and its measurements for the given flow (identified by main partitioning)
Proposed Solution
Function signature
CREATE OR REPLACE FUNCTION flows.flow_checkpoing(
    IN  i_fk_partitioning  BIGINT,
    OUT status             INTEGER,
    OUT status_text        TEXT,
    OUT id_checkpoint      UUID,
    OUT checkpoint_name    TEXT,
    OUT measure_name       TEXT,
    OUT measure_columns    TEXT[],
    OUT measurement_value  JSONB,
    OUT checkpoint_time    TIMESTAMP WITH TIME ZONE
) RETURNS SETOF record AS

for output order by checkpoint_time  and id_checkpoint
Depends on #178

This item depends on:

AbsaOSS/atum-service#178
By Dependent Issues.

This item depends on:

AbsaOSS/atum-service#178
By Dependent Issues.


Incompatible dependency graphs across rules

The failures in the github CI/CD workflow indicate that different tools end up resolving into different dependency versions (e.g. in libxml2). The way to address this would be to insulate the snakemake rules from each other and have them sit in separate conda environments or docker containers.

As of commit https://github.com/naturalis/barcode-constrained-phylogeny/commit/c37e912f020157107ecf1e3f9b446443daf66c72 this is now resolved. The consequence is that snakemake rules now have to be run with the --use-conda directive.


Peak Element using java

💥 Proposal
When the element is greater then the neighbours is peak element.
Have you read the Contributing Guidelines on Pull Requests?
yes

/assign


Compatibility with current version of Beanie (1.17)

Describe the bug
As Beanie v1.17 was released on Jan 19 and fastapi-users-db-beanie has it's dependencies defined as
dependencies = [
    "fastapi-users >= 10.0.1",
    "beanie >=1.11.0,<1.17",
]

users that are on the current Beanie version (1.17) who want to install fastapi-users[beanie] will not be able to.
In short: Beanie dependency version should be bumped again (after testing compatibility, of course).
To Reproduce
Steps to reproduce the behavior:

Have a project using Beanie 1.17
Try to install fastapi-users[beanie]

Expected behavior
fastapi-users[beanie] should be compatible with the current version of Beanie.
Configuration

Python version : 3.10
FastAPI version : 0.89
FastAPI Users version : 1.1.3

You're quite fast to respond :+1:

😄⚡

Released in v1.1.4


I have created an image based location identifier using google API.

I am Aayush Kumar a student at VIT BHOPAL UNIVERSITY, I have created an image-based location identifier as an ML project.
Please merge it with the main repository.
Thank you.

Can you please add some screenshot for our reference. Would love to take a look at it before merging this.

I have updated the documentation and also resolves some of the minor bugs.
Please review it and merge it.

Can you please review the Documentation, I have updated it and also resolve some minor bug.
Please review it and merge it.
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Monday, January 10th, 2022 at 2:13 PM, Aayush Mishra @.***> wrote:

Can you please add some screenshot for our reference. Would love to take a look at it before merging this.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


plotEpitopeMap peptides too long

This is an issue I only just recognised, but also exists in the HOIP dataset: if you look carefully at the plots from the plotEpitopeMap function, each peptide is 1 residue too long on the N-terminus.

I noticed this as I was getting a perhaps related error that I couldn't resolve that implies that my fasta file was one residue too long/short, where maximum redundancy = 11:
Error in $<-.data.frame(*tmp*, "Z", value = c(1L, 1L, 1L, 1L, 1L,  :
replacement has 4719 rows, data has 4708
If I artificially reduce the length of the fasta file by 1 aa, the function works. So I also thought that this error occurs when numlines is not a factor of the number of residues (which is an issue when your construct has a prime number of residues!)

Thanks for spotting - for some reason start was offset by -1. Not sure how that got there but it's fixed and will be correct in the next patch


Add annotation layer to plot to indicate average of averages

Would like some indication on the plot of average number of rrn copies by taxonomic rank that indicates the mean for that taxonomic rank. Ideas...

box and whisker plot
point
line plot
segment marking each mean

A bit concerned that stripchart doesn't adequately show data well. Let's look at alternatives...

box plot
histogram
density plot
Ridgeline plot - using density or histogram


getWilayat not working properly, the same with searchWilayatByName

some wilayat does not satisfy the conditions in the getWilayat methode ,
example wilayat not retrieved: Alger, Illizi
in the case of illizi the data is not correct
in the case of Alger , the condition is not correct because commune name is Alger centre , and daira is sidi m'hamed
in total I think there is problem with 6 wilayat

Hello benyoub , thank you for reporting the issue , I'll try to check what is not right with the functions

the package now has been updated.
I'll close this issue and wait for the analysis to complete.
for any other issues make sure to report them and thank you.


fix: remove memory leak in sublist_search.cpp

Description of Change

sublist_search.cpp has a memory leak. This PR adds the function deleteList in order to fix it.
Checklist

[x] Added description of change
[x] Added documentation so that the program is self-explanatory and educational - Doxygen guidelines
[x] Relevant documentation/comments is changed or added
[x] PR title follows semantic commit guidelines
[x] Search previous suggestions before making a new one, as yours may be a duplicate.
[x] I acknowledge that all my contributions will be made under the project's license.

Notes:
Removes memory leak in sublist_search.cpp.

@CarlosZoft you have some recent experience with reviewing pull-requests fixing memory leaks - maybe you could have a look here as well?

@Panquesito7, @realstealthninja: please dont-close.


Bug: Embedded driver enforced in version 3.0.0 but not working

I have been writing an application using Neo4J 3.2.6 and Neo4J-OGM 2.1.5 and the Bolt driver on Mac OS X 10.9.5 and Java 8. Everything has worked fine so far until I tried to upgrade the OGM drivers to version 3.0.0. I simply replaced the version number in my pom.xml. The code compiles just fine as before but I get errors at runtime.
These are my dependencies in pom.xml:
<dependencies>
  <dependency>
    <groupId>org.neo4j</groupId>
    <artifactId>neo4j-ogm-core</artifactId>
    <version>3.0.0</version>
    <scope>compile</scope>
  </dependency>
  <dependency>
    <groupId>org.neo4j</groupId>
    <artifactId>neo4j-ogm-bolt-driver</artifactId>
    <version>3.0.0</version>
    <scope>runtime</scope>
  </dependency>
</dependencies>

My ogm.properties looks like:
driver=org.neo4j.ogm.drivers.bolt.driver.BoltDriver
URI=bolt://localhost

At runtime I get the following exception:
org.neo4j.ogm.exception.ConfigurationException: Could not load driver class org.neo4j.ogm.drivers.embedded.driver.EmbeddedDriver
at org.neo4j.ogm.session.SessionFactory.newDriverInstance(SessionFactory.java:93)
at org.neo4j.ogm.session.SessionFactory.<init>(SessionFactory.java:81)
at org.neo4j.ogm.session.SessionFactory.<init>(SessionFactory.java:63)

This is strange because I don't want to use the embedded driver at all. If I add the demanded dependency to my pom.xml, then I get this exception:
java.lang.NoClassDefFoundError: org/neo4j/graphdb/GraphDatabaseService
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Class.java:2671)
at java.lang.Class.getConstructor0(Class.java:3075)
at java.lang.Class.newInstance(Class.java:412)
at org.neo4j.ogm.session.SessionFactory.newDriverInstance(SessionFactory.java:91)
at org.neo4j.ogm.session.SessionFactory.<init>(SessionFactory.java:81)
at org.neo4j.ogm.session.SessionFactory.<init>(SessionFactory.java:63)

I do not have any of these problems when I downgrade to version 2.1.5 again.
So there seems to be two problems:

The EmbeddedDriver is suddenly enforced at runtime even though it is not needed
The GraphDatabaseService is not found. Is this class still supposed to be there in 3.0.0?

The way of configuring OGM has changed in the 3.0 version.
Can you check the configuration doc ?
The migration checklist can also be useful in your case.
PS : The exceptions happen, because the ogm.properties file is not picked up by default anymore. Then OGM tries to configure a default embedded server which leads to the error.


Merge two Github releases from build matrix output?

First of all thanks for the awesome action! Works like a charm!
I am currently using GItHub actions to build an (ionic cordova) mobile app which is built on linux  (android apk) and mac (ios) in a matrix and upload the asset to Gi
Unfortunately when the jobs finish, I have a separate release for each asset.
I don't know if the api allows this, but would it be somehow possible to merge the releases into one?

Ah, the draft : true is a clue. Thanks for sharing. There may be something specific about that case.
I'm curious if you could do a test where you removed the draft: true and see if you see the same results

@softprops  Thanks for the hint, it was indeed the draft option. When I set draft to false it works fine.
I remember having the same problem with travis as well. So it seems like it's a bug or a "feature" of the github API...

It's a fair think to call out. I'll add a note in this actions readme before closing this

I did some digging and I think I can do one better. This action uses this api call to fetch a release by tag if it already exists when we update that release. It seem's it only fetches "published" releases   for a tag which is slightly inconvenient for drafts for a tag! But there is a work around by fetching all releases then filtering by tag mentioned here This isn't ideal but may make for a more seamless UX.  I'm going to close this and open a new issue to support that, cross referencing this as the usecase

Ah thanks for the update! This indeed is odd.

Consiquence of of maybe adding drafts after they had an API to get a release by tag :/ in any case thanks for surfacing this issue!


feTS not working with cloudflare worker

feTS not working with cloudflare worker. I got 302 Found redirected to /docs with blank page.

@francelwebdev can you share a reproduction?
For now I'm labeling this according to our new Contribution Guide and issue flow to stage 0.
Now in order to advance to stage 1 we'll need a simple reproduction, maybe in code-sandbox.
Later to progress to stage 2, a failing test would be needed, would be great if someone could help progress the issues through the stages.
Thank you and sorry that this comment is not a complete solution (yet).

Now we have a landing page instead of redirection. This should be fixed in the latest version. Closing the issue for now. If you still have the issues, let's know!


Make the minify method return a more useful error message

 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.


Makefile updates

@matentzn
I hadn't merged this pull request before running the release pipeline (about 20 minutes ago). Should I merge this and then rerun the build?

I think you can. Make sure that you run this as well (in the src/ontology directory):
docker pull obolibrary/odkfull
cd src/ontology
mkdir tmp
mkdir oort

And let me know how it goes! If there is a problem (and time pressure), I will make a release for you.


tsdb: SeriesIterator.Seek() is vaguely defined

Context: I was looking into cleaning up the iterator code, as I'm trying to add a separate SeekBefore() method, that would return the value at time t as defined by Prometheus without always parsing and iterating over a whole chunk covering the previous 5 minutes (when the looked up value is toward the beginning of a chunk).
However, I ran into some issues regarding how chunked series and iterators should actually work. There are a couple of gray areas that are only partially covered by comments or test code, making it impossible to figure out what is the expected correct behavior:

blockQuerier and the resulting chunkedSeries and chunkSeriesIterator all have mint and maxt fields, which (along with (*chunkSeriesIterator).Seek() implementation details) suggest that iterators should only return samples with timestamps mint <= t <= maxt. However, there are bugs (such as the one I'm attempting to fix with prometheus/tsdb#327) and even confusing/confused unit tests -- which appear to create an iterator with mint = 5, maxt = 8 and expect (*chunkSeriesIterator).Seek() to return a value with timestamp 3.Aremint and maxt supposed to be "hard" limits on the respective iterators or only on which chunks are selected?
I gather (from the implementation again) that SeriesIterator.Seek() is only supposed to seek forward (which doesn't work as expected, as it will also seek backward within the same chunk). Is this assumption correct?
Is Seek() supposed to always advance the iterator or should a second Seek() call with the same timestamp as the immediately preceding one leave the iterator positioned where it was before?
Is it actually a good idea for a Seek() with a timestamp t < mint to ever succeed? If so a poorly defined series e.g. [now - 10m, now] will "successfully" produce a value of the series at now - 1y equal to the first value after now - 10m.

I'm glad to do the work (including properly documenting the code) regardless of what the answers are, I'd just like to get some "authoritative" input. Thanks.

@bwplotka @free Was this resolved in the end?

Is there anything left to do here?

Hello from the bug scrub.

Is there anything left to do here?

We take three years of silence as "no". Closing.


Fix suggestion for git push -u

This was broken by https://github.com/nvbn/thefuck/pull/559

Coverage decreased (-0.2%) to 92.912% when pulling feb36ede5c518fdc3b6eddf945b2d8b1e2294d15 on josephfrazier:git-push-u into ce6b82c92d78ae283cb3db001766b76f6647bc47 on nvbn:master.

Coverage decreased (-0.2%) to 92.912% when pulling feb36ede5c518fdc3b6eddf945b2d8b1e2294d15 on josephfrazier:git-push-u into ce6b82c92d78ae283cb3db001766b76f6647bc47 on nvbn:master.

Coverage decreased (-0.2%) to 92.912% when pulling feb36ede5c518fdc3b6eddf945b2d8b1e2294d15 on josephfrazier:git-push-u into ce6b82c92d78ae283cb3db001766b76f6647bc47 on nvbn:master.

Coverage decreased (-0.2%) to 92.912% when pulling feb36ede5c518fdc3b6eddf945b2d8b1e2294d15 on josephfrazier:git-push-u into ce6b82c92d78ae283cb3db001766b76f6647bc47 on nvbn:master.

Thanks!


Remove all warnings

dozens of warnings show up when running npm start. I want to clear them all up so we can see warnings in real time as we develop.

Fixed them! Instead of seeing dozens of warnings, we see:

Now when we do something dumb, it should spit yellow texted poison at us. :)

Nice!


feat(just) Add bazzite - cli bling for issue #1385

Cloned the bluefin-cli bling into bazzite and added the requirements like the prexec for bash. Renamed the scripts to bazzite-cli in ujust and at their base to reduce confusion for users.
With a slightly different directory structure I ended up placing a majority of the scripts into shared space.
Test via VM via rebasing a bluefin build into this version running locally.

Thank you!!


w/o promt ?

./cf-dns.sh -d example.com -t A -n "*" -c <IP_ADDRESS>
i want to use it with cron. how it can be executed without promt where i must press 1 button?

@Nuke142

how it can be executed without promt where i must press 1 button?

Unfortunately it can't. See comment  Don't wait for user input.

Resolved by using yes
Iyes 1 |. /cf-dns.sh....

yes 1 | ./cf-dns.sh -d example.com -t A -n "*" -c <IP_ADDRESS>

This is fine if you only ever want to update the first matching record, which I assume is your use case. Others should be aware that by doing so there won't be the option to update any other matching records or add a new record.


[bct] Add changelog reporting information in the README

Add info about how to get the changelog output in the readme.

Completed in #36570


Minor improvements to mixins readability

@pjbreaux
Tests:  New assertions in test_share.py

Thanks much better readability in getattr


Adding basic file configuration options

We will now generate the configuration file for every run of mongodb, using environment variables as input. Substitution is done with envsubst.

@mnagy @mfojtik PTAL

LGTM

@mnagy PTAL

LGTM


Adopt me visibilty

#1322
Closes: #1322

Description
The adopt me button was not visible, with the text color that was used. I changed the text color to be more visible
Screenshots

Checklist

[ x] My code adheres to the established style guidelines of the project.
[x ] I have included comments in areas that may be difficult to understand.
x[ ] My changes have not introduced any new warnings.
[ x] I have conducted a self-review of my code.

@akshitagupta15june Please add the hacktoberfest tag


Documentation

Changes Unknown when pulling 29d911808f8890b34b1b66e3b842e8cf17ff58cb on IamKritika:master into ** on angular-libs:master**.

Current coverage is 17.78%

Merging #9 into master will not affect coverage as of c5216c9

@@            master      #9   diff @@
======================================
  Files            8       8
  Stmts          253     253
  Branches        28      28
  Methods          0       0
======================================
  Hit             45      45
  Partial          0       0
  Missed         208     208

Review entire Coverage Diff as of c5216c9

Powered by Codecov. Updated on successful CI builds.

Changes Unknown when pulling 29d911808f8890b34b1b66e3b842e8cf17ff58cb on IamKritika:master into ** on angular-libs:master**.

1). mention about source map support and give a example
2). mention libs used under the hood and their role

logger can be used to log any information not just exceptions .. so mention it and put an example


TestNG reporter marks test as passed despite the test was not run by the IHookable.

I have a custom listener which sets some global flag when any test fails:
public class MyListener extends TestListenerAdapter
{
@Override
public void onTestFailure(ITestResult tr)
{
super.onTestFailure(tr);
GlobalFlag.failureStatus = true;

}
Then, I have a MyHookable which checks if that flag is set. If set, just print to skip else call the method.
public class MyHookable implements IHookable
{
@Override
public void run(IHookCallBack icb, ITestResult testResult)
{
//if previous tests pased , allow next tests to run
if(GlobalFlag.failureStatus == false)
{
  icb.runTestMethod(testResult);
}

//don't allow any more tests to run
else
{
System.out.println("Skipping test execution for "+testResult.getTestName());
}

}
}
I created 3 tests(Test1, Test2, Test3) and I made all the tests to fail with
Assert.assertEquals(true, false);
when I am executing these tests, I see that it's always coming in else block after executing Test1 and printing that test2 and test3 is getting skipped but, in the result at the end , it says
Test1 Failed
Test2 Passed(despite Assertion failure)
Test3 Passed. (despite Assertion failure)
It looks like reporter doesn't know if the test being skipped by IHookable.

TestNG is working as designed here. If there are any scenarios wherein one needs to simulate a failure (or) a skip, then one has to trigger them.
To trigger an explicit test skip, one needs to throw SkipTestException and to trigger a failure one needs to throw any sub-variant of Throwable.
Here's a sample that shows all this
Test class looks like below
package com.rationaleemotions.github.issue201;

import org.testng.Assert;
import org.testng.IHookCallBack;
import org.testng.IHookable;
import org.testng.ITestResult;
import org.testng.SkipException;
import org.testng.annotations.Test;

public class TestASample implements IHookable {
    @Override
    public void run(IHookCallBack callBack, ITestResult testResult) {
        if (Github201TestRunner.FailureTracker.proceedFurther) {
            System.err.println(prettyPrintExecuting(testResult));
            callBack.runTestMethod(testResult);
        } else {
            System.err.println(prettyPrintSkipping(testResult));
            throw new SkipException("Skipping");
        }
    }

    @Test
    public void testMethodFails() {
        Assert.fail();
    }

    @Test
    public void testMethodSkips() {
        Assert.assertTrue(true);
    }

    private static String prettyPrintExecuting(ITestResult result) {
        return prettyPrint("Executing", result);
    }

    private static String prettyPrintSkipping(ITestResult result) {
        return prettyPrint("Skipping", result);
    }

    private static String prettyPrint(String prefix, ITestResult result) {
        return prefix + " " + result.getTestClass().getRealClass().getName()
                + "." + result.getMethod().getMethodName() + "()";
    }
}

Test runner looks like below
import org.testng.Assert;
import org.testng.ITestNGListener;
import org.testng.ITestResult;
import org.testng.TestListenerAdapter;
import org.testng.TestNG;
import org.testng.annotations.Test;

public class Github201TestRunner {
    @Test
    public void runTest() {
        TestNG testng = new TestNG();
        testng.setTestClasses(new Class[]{TestASample.class});
        FailureTracker tracker = new FailureTracker();
        testng.addListener((ITestNGListener) tracker);
        testng.run();
        Assert.assertEquals(tracker.getFailedTests().size(), 1);
        Assert.assertEquals(tracker.getSkippedTests().size(), 1);
        Assert.assertTrue(tracker.getPassedTests().isEmpty());
    }

    public static class FailureTracker extends TestListenerAdapter {
        static boolean proceedFurther = true;

        @Override
        public void onTestFailure(ITestResult tr) {
            super.onTestFailure(tr);
            proceedFurther = false;
        }
    }
}

Test output looks lie below
Executing com.rationaleemotions.github.issue201.TestASample.testMethodFails()
Skipping com.rationaleemotions.github.issue201.TestASample.testMethodSkips()

===============================================
Command line suite
Total tests run: 2, Failures: 1, Skips: 1
===============================================

===============================================
Default Suite
Total tests run: 1, Failures: 0, Skips: 0
===============================================


agent: use onlineCPUMem to online vCPUs

After hot adding vCPUs in the POD, agent's funtion onlineCPUMem
must be called to request the agent to online the vCPUs
fixes #67
Signed-off-by: Julio Montes<EMAIL_ADDRESS>

changes applied, thanks

@bergwolf PTAL and merge if you're fine with this.


compare PAC to preregistrations for clinical trials

I have no expertise here but this sounds good!

This is a very specific type of preregistration, which a lot of readers may not be familiar with in detail, so I'd rather not address this in detail as it could distract from the main message.

I guess we can mention this in #235 as a promising case for PAC


Allow embedding metadata in elf's to pick the right probe (similar to teleprobe-meta).

Teleprobe supports embedding metadata in the elf, so that the host tool can pick it up and choose for instance the probe automatically.
With the coming addition of probe-rs test (via embedded-test), it would be nice to have something similar in probe-rs.
Although we could add this functionality to all subcommands, not only probe-rs test.
(initially requested by @vollbrecht:matrix.org )

Why is that useful? You want an ELF to be flashable with any probe, no?

The main idea are HIL Tests, where you have multiple probes connected to a computer and you want to run the different test (suites) on the different targets.
When using teleprobe you can do exactly that: embedd some metadata into the test and teleprobe will then choose the right probe for you.
But yeah, it might make sense to only add this for the probe-rs test subcommand and not to all subcommands in general...


Support pulling backup from remote sftp server

What does this PR change? What problem does it solve?
Support pulling backups from remote sftp server.

Was the change discussed in an issue or in the forum before?
#299
https://forum.restic.net/t/backup-of-files-at-remote-sftp-server/3068/2

Checklist

[x] I have read the Contribution Guidelines
[x] I have enabled maintainer edits for this PR
[ ] I have added tests for all changes in this PR
[x] I have added documentation for the changes (in the manual)
[ ] There's a new file in changelog/unreleased/ that describes the changes for our users (template here)
[x] I have run gofmt on the code in all commits
[ ] All commit messages are formatted in the same style as the other commits in the repo
[ ] I'm done, this Pull Request is ready for review

Works fine here.
Would be cool if it were possible to mix local and sftp targets.

Thanks a lot for your contribution! Before spending any more time on it, please wait for us to have a look, we're not entirely sure how to proceed here. Thanks! :)


Support Locust 1.0.3

This is to support Locust 1.0.3, which includes updates like option names, etc
Related Issue
https://github.com/karol-brejna-i/docker-locust/issues/15

@youngkih thank you for this PR. give me a couple of days to review.

@karol-brejna-i Any updates on this?

I am back from vacation. Starting testing today.

@youngkih Thank you for this contribution. And thank you for thinking about a dedicated example for 1.0.x versions


Make it possible to download the osc file

Since the iD editor is a great editor, but is not able to resolve conflicts, it would be nice, if it is possible to download the osc and then edit/resolve the conflicts using another editor.
This is at least the first step to introduce some kind of conflict resolution and will help users that did many changes and are then not able to upload them because of a conflict in the first change they did (here undo does not help, because it does not allow to undo "only" the first change (and yes that just happened to me)).
This issue is a feature request and was also suggested in #1053

closing, as this will be implemented in #2489


Make Row.get throw instead of crash.

This isn't backwards compatible with the old .get, but subscripts still work the same. I figure most use subscripts so this won't be too big of a deal, but if you want me to think of a backwards compatible way to do this, let me know.

Applied in bd1fc80414c89b8d7b756899cff2a153d5fd04f1


Cannot install from scratch

Following the instructions from this section: https://github.com/ejp-rd-vp/FiaB#installing-from-scratch
I run sh ./run-me-to-install.sh
Is this a production installation, or are you just trying the installer?
Production? [y/n]: n

I navigate to http://localhost:7200 but it doesn't work.
http://localhost:7070 also doesn't work.
However, I can manage to have them working if I follow the instructions from this repo: https://github.com/ejp-rd-vp/cde-in-box
Am I missing something from the instructions?

The installer is working as far as I know... I used it just yesterday!
Can you give me more information?
cde-in-a-box is deprecated, so I don't recommend you use that...

Thanks for the quick reply!
This is the full log:
-e Is this a production installation, or are you just trying the installer?
Production? [y/n]:n
-e
-e Just trying things out!  Great!  Continuing with some sensible defaults for you...
-e URI: http://localhost:7070
-e Component-prefix: test
-e FDP Port: 7070
-e GraphDB Port: 7200
-e Beacon2 Port: 8000
-e RDF Transformation trigger port: 4567
-e
mkdir: /Users/dlemos/tmp: File exists
Error response from daemon: network bootstrap_default not found
Error response from daemon: No such container: bootstrap_graphdb_1
Error response from daemon: No such container: metadata_fdp_1
Error response from daemon: No such container: metadata_fdp_client_1
test-graphdb test-fdp-client-assets test-fdp-client-css test-fdp-client-scss test-fdp-server test-mongo-data test-mongo-init
test-graphdb
test-fdp-server
test-fdp-client-assets
test-fdp-client-scss
test-mongo-data
test-mongo-init

-e Creating GraphDB and bootstrapping it - this will take about a minute
-e Go make a nice cup of tea and then come back to check on progress
-e

sed: 1: "docker-compose-test.yml": extra characters at the end of d command
parsing /Users/dlemos/Documents/work/ejp-rd/docker/FiaB/CDE Version2 Models FiaB/bootstrap/docker-compose-test.yml: yaml: line 10: did not find expected '-' indicator

-e Setting up FAIR Data Point client and server

sed: 1: "docker-compose-test.yml": extra characters at the end of d command
sed: 1: "docker-compose-test.yml": extra characters at the end of d command
sed: 1: "./fdp/application-test.yml": invalid command code .
sed: 1: "./fdp/application-test.yml": invalid command code .
sed: 1: "./fdp/application-test.yml": invalid command code .
parsing /Users/dlemos/Documents/work/ejp-rd/docker/FiaB/CDE Version2 Models FiaB/metadata/docker-compose-test.yml: yaml: line 29: did not find expected '-' indicator

-e Creating a production server folder in  ./test-ready-to-go/

sed: 1: "./test-ready-to-go/dock ...": invalid command code .
sed: 1: "./test-ready-to-go/dock ...": invalid command code .
sed: 1: "./test-ready-to-go/dock ...": invalid command code .
sed: 1: "./test-ready-to-go/dock ...": invalid command code .
sed: 1: "./test-ready-to-go/dock ...": invalid command code .
sed: 1: "./test-ready-to-go/fdp/ ...": invalid command code .
sed: 1: "./test-ready-to-go/fdp/ ...": invalid command code .
sed: 1: "./test-ready-to-go/fdp/ ...": invalid command code .
sed: 1: "./test-ready-to-go/.env": invalid command code .
sed: 1: "./test-ready-to-go/.env": invalid command code .

-e Installation Complete!
-e you now have 10 minutes to test things.
-e If GraphDB is working, you should be able to access it at: http://localhost:7200  (NOTE: this is NOT the port that will serve GraphDB in your production service!  This is only used for the test phase you are currently doing...
-e If Your FAIR Data Point is working, you should be able to access it at: http://localhost:7070

-e NOTE: If you see the message:

-e                  unable to get data

-e       in your FAIR Data Point web page,
-e       it is likely because GraphDB hasn't finished setting itself up.
-e       wait until you are able to connect to http://localhost:7200 and then try again!
-e       It can take up to a minute after GraphDB comes alive before the FDP completes its initialization...

-e For further instructions and tests, read the documentation on the FAIR-in-a-box GitHub page

-e You can stop this test phase at any time with CTRL-C, then wait for the docker images to shut down cleanly before continuing

There are a few parsing errors.

Gosh... that's nothing but errors!
A bit more detail:  Which operating system are you on?   The errors suggest that you are not using bash... how are you invoking the installer?
can you try explicitly using bash?
/bin/bash run-me-to-install.sh

I'm running on macOS 13.4.1
Docker version 24.0.6, build ed223bc
Docker Compose version v2.22.0-desktop.2

Hmmmm.... I've never followed anyone installing on a Mac, and I have never touched one myself, so... I'm not sure what to suggest.   It's definitely not executing the bash commands the way that Linux does, and so nothing is getting installed at all as far as I can see from your logs.
Did you try invoking bash directly?

Yes, tried with your suggestion. I get the exact same errors.
I'm going to try on a different machine which is not macOS.

Sounds good!  I just ran it for a non-production installation and both graphdb and the FDP came up on localhost, so... the installer is working correctly on Linux :-)  (I know that doesn't help you!)

I just did a bit of searching and, indeed, there are differences between bash in MacOS vs. Linux related to some commands in the installer:
 The major problem is that the MacOS coreutils are FreeBSD-based while the utilities you are used to are most likely from the GNU project. The FreeBSD coreutils are not always compatible with the GNU coreutils. There are performance and behavioral differences between the GNU and FreeBSD versions of [sed](http://forums.freebsd.org/showthread.php?p=207335), [grep](http://lists.freebsd.org/pipermail/freebsd-current/2010-August/019310.html), [ps](https://serverfault.com/questions/324945/what-is-the-os-x-bsd-equivalent-of-the-gnu-ps-auxf-command), and [other utilities](https://unix.stackexchange.com/questions/79355/what-are-the-main-differences-between-bsd-and-gnu-linux-userland/79357#79357).   You can install the GNU coreutils but they have g- prefixes (e.g. gcat for cat). It's [not a good idea](https://apple.stackexchange.com/questions/69223/how-to-replace-mac-os-x-utilities-with-gnu-core-utilities) to replace the MacOS coreutils with the GNU coreutils.

Beacon2 is a query interface designed specifically for EJP.  It allows privacy-preserving queries over the data (e.g. patient counts).  It is entirely optional.

Thanks for the clarification.
Unfortunately I hit another problem.
In this step https://github.com/ejp-rd-vp/FiaB#find-the-folder-with-your-final-server-config-ready-to-go
After copying the files to ~/SERVERS/
I run the command: docker-compose -f docker-compose-ensemblvep.yml up
I got an error:
Status: Downloaded newer image for pabloalarconm/ejprd-counting-api:0.0.2
Creating ensemblvep-ready-to-go_hefesto_1      ... done
Creating ensemblvep-ready-to-go_beacon_count_1 ... done
Creating yarrrml-rdfizer                       ... done
Creating ensemblvep-ready-to-go_updater_1      ... done
Creating ensemblvep-ready-to-go_graphdb_1      ... done
Creating ensemblvep-ready-to-go_mongo_1        ... done
Creating cde-box-daemon                        ... done
Creating ensemblvep-ready-to-go_fdp_1          ... done
Creating ensemblvep-ready-to-go_fdp_client_1   ...
Creating ensemblvep-ready-to-go_fdp_client_1   ... error

ERROR: for ensemblvep-ready-to-go_fdp_client_1  Cannot start service fdp_client: driver failed programming external connectivity on endpoint ensemblvep-ready-to-go_fdp_client_1 (85de725821a2c58dcc3a0719ad7d2a346c3f94f29dcf6a825e4e7768c081298c): Bind for <IP_ADDRESS>:8080 failed: port is already allocated

ERROR: for fdp_client  Cannot start service fdp_client: driver failed programming external connectivity on endpoint ensemblvep-ready-to-go_fdp_client_1 (85de725821a2c58dcc3a0719ad7d2a346c3f94f29dcf6a825e4e7768c081298c): Bind for <IP_ADDRESS>:8080 failed: port is already allocated
ERROR: Encountered errors while bringing up the project.

Port 8080 is the one I defined for the FAIR data point. The ports 8080 and 8200 are running since I created my server.
Port 8200 is for the GraphDB as far as I understand graphdb created successfully.


Add hal::stream_dac

This interface would allow a user to pass a span of dac values to a dac driver. The dac driver should use DMA to manage the stream to the peripheral. Interrupts can be used as well but ill advised for performance reasons. And polling can be done, but it would make the interface less useful in general.

List of MCUs with DMA DACs

msp430 (maybe only 8 bit since it's right justified)
stm32f1
lpc40
stm32f4
samd21
samd20
TBD (update this comment later)

Proposed interface
#pragma once

#include <concepts>
#include <span>

#include "units.hpp"

namespace hal {
/**
 * @brief Hardware abstraction for a dac that accepts a stream of data
 *
 * This interface can be used for the following:
 *
 * 1. Audio output using PCM8 or PCM16 streams
 * 2. Arbitrary waveform generation
 * 3. Single wire data protocols (ex: neopixel LEDs)
 *
 * The driver is likely to use the following to operate:
 *
 * 1. DMA: preferred choice as it removes the need for the CPU to handle the
 *    transfer.
 * 2. SPI (using DMA): preferred when communicating with an external dac
 * 3. Interrupts & Timers: Not recommended but can be used. The CONs of this
 *    approach is a low maximum sample rate, sample rate accuracy due to
 *    interrupt & software latency, and requires cycles from the CPU.
 *
 * @tparam data_t - container size for the sample data. For such things as PCM8
 * and PCM16 this would be std::uint8_t and std::uint16_t respectfully.
 */
template<std::unsigned_integral data_t>
class stream_dac
{
public:
  struct samples
  {
    /**
     * Sample rate sets the update rate of the dac. For example, if the sample
     * rate is 44.1kHz (typical for consumer audio), then the samples will be
     * read from the data array and written to the dac output at that frequency.
     *
     */
    hal::hertz sample_rate;
    /**
     * Span of unsigned integer data to be written to the dac at the rate
     * specified by the sample rate field.
     *
     * If this is empty (empty() == true), then the write command simply
     * returns without updating anything.
     */
    std::span<data_t> data;
  };

  /**
   * @brief Write a sequence of data to the dac
   *
   * This API is blocking call. The expectation is that implementors
   *
   *
   * @param p_samples - sample data to be written to the dac output
   * @throws hal::argument_out_of_domain - when the sample rate is not possible
   * for the driver. This can happen if:
   *     - The sample rate is above the input clock rate of the dac making it
   *       impossible to produce.
   *     - The dac could not reach a sample rate close enough to the desired
   *       sample rate. This can occur if the dac's source clock and the sample
   *       rates are close and as such no divider cleanly reaches a reasonable
   *       sample rate for the device. For example, if the desired sample rate
   *       is 750kHz and the clock rate is 1MHz and divider is an integer. You
   *       would either operate at 1MHz or 500kHz which are very far away from
   *       the desired sample rate. The driver should, but is not required, to
   *       provide a means to control the allowed "error" between the desired
   *       sample rate and the achievable sample rate in order tune what
   *       samples are rejected and an exception thrown.
   *     - Sample rate is too low and cannot be achieved by the dac.
   */
  void write(samples p_samples)
  {
    driver_write(p_samples);
  }

private:
  virtual void driver_write(samples p_samples) = 0;
};
}  // namespace hal

Meant to make the span const. I considered leaving it mutable such that a driver can mutate the memory in place in order to arrange the data in such a way that a right justified DAC register could work with DMA.
But this would be a bad API design. It means that any buffer you pass into these APIs is liable to destroy/truncate the data. Which would require the user to make duplicate buffers, one for each copy of the buffer it wants to transfer over DAC or to other stream drivers. Using const allows us to pass the same buffer to every stream API without concern.
Also this would impact the ability to stream data from FLASH and rodata sections without a copy.
Prevent the data from being modified is the right choice here.

When I used audacity I realized that PCM 8-bit unsigned is a thing, but PCM 16 bits and above is signed. This is a bit of an issue since all of the DACs are unsigned. Will have to consider what is reasonable for this.

I think its fine to require unsigned data to be passed into the DAC. For example, if an application is converting MP3 data into signed 16-bit PCM, then the code will also have to perform a step to convert those samples to unsigned PCM16 by adding (2^15 - 1) to each of the values in the set. Then pass that resulting info to the dac.

Resolved by #48


Data table: Fail to focus on the Search button through keyboard TAB button

Detailed description

Describe in detail the issue you're having.

When using IBM datatable component cannot open table search using keyboard.
Failed to use tab key to focus on the  Search icon.
This is Accessibility testing issue

Is this a feature request (new component, new icon), a bug, or a general issue?

BUG

Is this issue related to a specific component?

ibm-table-toolbar-search

What did you expect to happen? What happened instead? What would you like to see changed?

Expected The search icon should be operated using a keyboard but instead cannot focus on search icon in  in datatable component

What version of the Carbon Design System are you using?

"carbon-components-angular": "3.49.7"

What offering/product do you work on? Any pressing ship or release dates we should be aware of?

I am working in MCMP. This is expected to be fixed by OCTOBER.
What browser are you working in?
Chrome
Tools
JAWS2019
Steps to reproduce the issue

https://angular.carbondesignsystem.com/?path=/story/components-table--with-toolbar
Use TAB button to navigate to search icon.

Additional information

Screenshots or code

Does #1528 solve this issue?

@tacho090 Sorry for the delayed response, #1528 did close this and it doesn't seem to be a problem in version 4, so I'll close this but feel free to reopen if there are any issues.


3D Lessons?

I've been trying to teach my wife some basics of shader programming, and along with some of the introductory material at the .NET OpenTK website, your tutorial videos were extremely helpful. Being able to see the results real-time as you make changes really clicked with her, like no other tutorial ever has.
I realize they're pretty old and they're time-consuming to plan and publish, but is there any chance you'll ever get around to the 3D videos you said were coming "next time" at the end of your Lesson 05?
Either way, your content is greatly appreciated! Everyone knows about shadertoy, your site deserves just as much exposure in my opinion.

Sorry, I don't think I'll be making vertexshaderart videos 😢
I think IQ the shadertoy guy, ig, has some videos:
https://www.youtube.com/channel/UCdmAhiG8HQDlz8uyekw4ENw
Otherwise, stuff I helped on that teach 3D
https://webglfundamentals.org
https://webgpufundamentals.org
https://threejs.org/manual


Project output files

Place intermediate output files in build/obj and final output files in build/bin to ensure a clean project build.

Thank you!


Fixed nan assertion failures

PR checklist

[ ] Has a descriptive title
[ ] Has a descriptive body
[ ] Passes checks (to auto-fix a pre-commit.ci failure, add a comment
containing "pre-commit.ci autofix")

pre-commit.ci autofix


Merge 1.6.0

Codecov Report

Merging #684 into master will decrease coverage by 0.15%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #684      +/-   ##
==========================================
- Coverage   68.53%   68.38%   -0.16%
==========================================
  Files         384      382       -2
  Lines       20726    20635      -91
==========================================
- Hits        14205    14111      -94
- Misses       6521     6524       +3

Impacted Files
Coverage Δ

extend/os/requirements/osxfuse_requirement.rb
50% <0%> (-10%)
:arrow_down:

extend/os/system_config.rb
50% <0%> (-10%)
:arrow_down:

extend/os/extend/ENV/std.rb
50% <0%> (-10%)
:arrow_down:

extend/os/requirements/java_requirement.rb
50% <0%> (-10%)
:arrow_down:

extend/os/dependency_collector.rb
50% <0%> (-10%)
:arrow_down:

extend/os/keg_relocate.rb
50% <0%> (-10%)
:arrow_down:

extend/os/diagnostic.rb
50% <0%> (-10%)
:arrow_down:

extend/os/bottles.rb
50% <0%> (-10%)
:arrow_down:

cask/lib/hbc/container/generic_unar.rb
46.15% <0%> (-3.85%)
:arrow_down:

diagnostic.rb
43.39% <0%> (-3.45%)
:arrow_down:

... and 97 more

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 0a0defb...8bd8aa2. Read the comment docs.


Variables Within Sections Won't Render

JObject properties will not render with a mustache variable inside a section.
Example:
{ "foo": { "bar": "foobar" } }

{{#foo}}{{bar}}{{/foo}}

Will render an empty string.
It looks like the problem is that a JProperty is returned when getting the foo value, but JProperty doesn't inherit JObject so the JsonNet.ValueGetters are not used.
I think I've fixed the issue and will submit a pull request.

PR #4

Hi there,
Thanks for the contribution. I'll look at getting this merged and fixing the failing linux build later today.

Thanks for your contibution. This has been merged and released in version v1.1.5
Thanks!


Evaluate checks for sandbags only on building rooftops (above AGL)

Concerns over gameplay being affected by building bunkers, etc, on rooftops. Limit build capabilities when not within 2m of ground level?

I've restricted it before and found things to be more interesting when players could build higher up

It's just to limit the larger emplacements from being placed, like a full-size bunker. Sandbags are fine, Hescos are maybe, two story camo bunker should be a no

Changed in commit https://github.com/Mjolnir64/FNF/commit/e0020892684317c4b9fcc765ebd73ec77d6f6956
Uses PositionATL, so the object has to be terrain level. You won't be able to build on rocks. If building on rocks is a wanted ability, then I can check if there is any object inheriting from 'Rocks_base_F' class directly underneath the fortification piece.


PLAT-140834: Add UI Test for VirtualGridList

Enact-DCO-1.0-Signed-off-by: Dongsu Won<EMAIL_ADDRESS>Checklist

[x] I have read and understand the contribution guide
[ ] A CHANGELOG entry is included
[x] At least one test case is included for this feature or bug fix
[x] Documentation was added or is not needed
[ ] This is an API breaking change

Issue Resolved / Feature Added

Need to add VirtualGridList ui-test.
Need to add button to add item.

Resolution

Add VirtualGridList ui-test.
Add button to add item.

Additional Considerations
Links
PLAT-140834
Comments

Jenkins Passed:
/job/enact-ui-tests/1633/


Add Aby Abraham to Contributors list

Adding Aby to CONTR. LIST

Hi, @abyabrkal, could you please add your name to Contributors.md rather than CONTRIBUTING.md?


dropdown: Fix dropdown partially hidden at small heights.

We generalize the approach used for compose box to apply it for all the dropdowns.
discussion: https://chat.zulip.org/#narrow/stream/9-issues/topic/dropdown.20widget.20not.20fully.20visible.2E
Tested all the dropdowns at various heights.

Works for me in manual testing!

Merged, huge thanks for cleaning this up @amanagr!


pre-babelify javascript code

This can make the code run faster.

The delay is caused by update check. This does not increase code performance significantly.

But if we implement this, it's easy to install mup. Because user does not
need to download a huge chunk of babel related modules.
On Wed, Dec 2, 2015 at 2:55 PM Muhammed Thanish<EMAIL_ADDRESS>wrote:

The delay is caused by update check. This does not increase code
performance significantly.
—
Reply to this email directly or view it on GitHub
https://github.com/kadirahq/meteor-up/issues/16#issuecomment-161232908.

I didn't think of that so I deleted the branch. We can do this after porting all core features or else we'll have to run npm run prepublish often.

We can use NPM base for this.
Use this: https://github.com/kadirahq/npm-base


Laravel 11.x Compatibility

This is an automated pull request from Shift to update your package code and dependencies to be compatible with Laravel 11.x.
Before merging, you need to:

Checkout the l11-compatibility branch
Review all comments for additional changes
Thoroughly test your package

If you do find an issue, please report it by commenting on this PR to help improve future automation.

:warning: The latest version of Laravel has a dependency for phpunit/phpunit of ^10.5. If you would like to also upgrade your tests, you may run the PHPUnit 10 Shift for free.

:warning: Shift detected GitHub Actions which run jobs using a version matrix. Shift attempted to update your configuration for Laravel 11. However, you should review these changes to ensure the desired combination of versions are built for your package.

:alembic: Using this package? If you would like to help test these changes or believe them to be compatible, you may update your project to reference this branch.
To do so, temporarily add Shift's fork to the repositories property of your composer.json:
{
    "repositories": [
        {
            "type": "vcs",
            "url": "https://github.com/laravel-shift/laravel-route-attributes.git"
        }
    ]
}

Then update your dependency constraint to reference this branch:
{
    "require": {
        "spatie/laravel-route-attributes": "dev-l11-compatibility",
    }
}

Finally, run: composer update

@laravel-shift The L11 tests are failing, could you take a look?

Thanks!


cargo fix --edition fails to fix trait objects with multiple constraints when leading :: present

Problem

cargo fix --edition cannot correctly fix the following code:
type Foo = Box<::std::error::Error + Send>;

I would expect it to correct to
type Foo = Box<dyn std::error::Error + Send>;

or
type Foo = Box<dyn (::std::error::Error + Send)>;

but instead, it outputs this
type Foo = Box<dyn ::std::error::Error + Send>;

which fails to compile with the following message:
error[E0433]: failed to resolve: use of undeclared type or module `dyn`
 --> src/lib.rs:1:16
  |
1 | type Foo = Box<dyn ::std::error::Error + Send>;
  |                ^^^ use of undeclared type or module `dyn`

Steps

cargo new --lib foo --edition 2015
cd foo
echo 'type Foo = Box<::std::error::Error + Send>;' > src/lib.rs
cargo fix --edition --allow-dirty

Here is the full output of that command on my system:
warning: failed to automatically apply fixes suggested by rustc to crate `foo`

after fixes were automatically applied the compiler reported errors within these files:

  * src/lib.rs

This likely indicates a bug in either rustc or cargo itself,
and we would appreciate a bug report! You're likely to see
a number of compiler warnings after this message which cargo
attempted to fix but failed. If you could open an issue at
https://github.com/rust-lang/rust/issues
quoting the full output of this command we'd be very appreciative!
Note that you may be able to make some more progress in the near-term
fixing code with the `--broken-code` flag

The following errors were reported:
warning: `dyn` is a keyword in the 2018 edition
 --> src/lib.rs:1:16
  |
1 | type Foo = Box<dyn ::std::error::Error + Send>;
  |                ^^^ help: you can use a raw identifier to stay compatible: `r#dyn`
  |
  = note: `-W keyword-idents` implied by `-W rust-2018-compatibility`
  = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in the 2018 edition!
  = note: for more information, see issue #49716 <https://github.com/rust-lang/rust/issues/49716>

error[E0433]: failed to resolve: use of undeclared type or module `dyn`
 --> src/lib.rs:1:16
  |
1 | type Foo = Box<dyn ::std::error::Error + Send>;
  |                ^^^ use of undeclared type or module `dyn`

warning: trait objects without an explicit `dyn` are deprecated
 --> src/lib.rs:1:16
  |
1 | type Foo = Box<dyn ::std::error::Error + Send>;
  |                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `dyn`: `dyn dyn ::std::error::Error + Send`
  |
  = note: #[warn(bare_trait_objects)] on by default

error: aborting due to previous error

For more information about this error, try `rustc --explain E0433`.
Original diagnostics will follow.

warning: trait objects without an explicit `dyn` are deprecated
 --> src/lib.rs:1:16
  |
1 | type Foo = Box<::std::error::Error + Send>;
  |                ^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `dyn`: `dyn ::std::error::Error + Send`
  |
  = note: #[warn(bare_trait_objects)] on by default

warning: trait objects without an explicit `dyn` are deprecated
 --> src/lib.rs:1:16
  |
1 | type Foo = Box<::std::error::Error + Send>;
  |                ^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use `dyn`: `dyn ::std::error::Error + Send`
  |
  = note: #[warn(bare_trait_objects)] on by default

warning: type alias is never used: `Foo`
 --> src/lib.rs:1:1
  |
1 | type Foo = Box<::std::error::Error + Send>;
  | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  |
  = note: #[warn(dead_code)] on by default

warning: type alias is never used: `Foo`
 --> src/lib.rs:1:1
  |
1 | type Foo = Box<::std::error::Error + Send>;
  | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  |
  = note: #[warn(dead_code)] on by default

    Finished dev [unoptimized + debuginfo] target(s) in 0.32s

Possible Solution(s)

Notes
Output of cargo version:
λ cargo --version
cargo 1.37.0 (9edd08916 2019-08-02)

λ rustc --version
rustc 1.37.0 (eae3437df 2019-08-13)

Additionally, while the code emits a warning in this test repo, in my real code, cargo fix did actually emit and write the broken code, which I then later had to manually fix.

Thanks for the report!  This looks to be the same as https://github.com/rust-lang/rust/issues/63330, so I'm going to close in favor of that.  This isn't specific to the --edition flag, but that the suggestion doesn't work on 2015 at all.


Change usages of uint to int in code to conform with guidance doc

NullableUInt32 has a few usages that may need a NullableInt32. But I'm interested in the fallout of #91 before making those changes.


selectedSegmentIndex doesn't work ?

I am trying to set selectedSegmentIndex = 0 but it doesn't work. Any idea?

DispatchQueue.main.async {
self.segmentedControl.selectedSegmentIndex = 0
}
It works now...


use environment configs to parametrize genlims database connection

Parse a local parameters/config (.ini) file to determine the host and database name to use for connection.

Coverage decreased (-0.1%) to 98.418% when pulling d99c67be6bbccd2b854992b6780ccfca0c9c0d7d on config-db-connect into e08316657c553c24b3a1b2fdcac392e2311c52a6 on master.


Add support for sending out a specific interface

I've added a pull request for this #131

Specifically this project: https://github.com/projectdiscovery/retryablehttp-go


how to increase training speed if i have 600 categories that we have to train we have GPU 1050 with 4 GB Ram and 16 GB system Ram with 1TB hardisk how could we train it fastly either need to increase GPU and RAM?

Hello @DeveloperRachit,
To train faster I would recommend that you increase the batch size of your training data and also use a much more powerful system if available.


Black does not format correctly strings containing emojis

It seems that this extension does not handle correctly formatting strings containing emojis when formatting from vscode. Formatting the file with the black command via cli works correctly.
Examples:
before
s = '😊'
x = 'foo'

after
s = ""'
x = "foo"

or
s = '🤵 hi!'

after
s = "🤵 hi"'

Investigating a bit, it seems that the positions sent back from the language server to the client count the emojis as a single character while the visual studio code editor doesn't, as for the first example the line edits relative to the line 0 are 0:4-0:5, new_text='"' and 0:6-0:7, new_text='"', but the second one seems to replace something other than the second '. Tampering with the server code and setting 0:7-0:8 to the second edit fixes the problem.
Tested on Windows 10.

This may be related to the fact that in python assert len("😊") == 1 while in javascript (that uses utf-16) "😊".length == 2.
Javascript recommends converting the string into an array to retrieve the number of characters (see https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/length#strings_with_length_not_equal_to_the_number_of_characters).
I don't know it it's easier to return from the python server the adjusted offsets by encoding the string into utf-16 (also taking the correct endianness into account) or to make vscode position API unicode aware (probably the first).

@DavideCanton Can you share the logs you captured?

@DavideCanton I think this has to be handled in python itself. Looks like the general specification is to handle it based on the positionEncoding field passed in the initial configuration : https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocuments
We calculate text edits here: https://github.com/microsoft/vscode-black-formatter/blob/main/bundled/tool/lsp_edit_utils.py
The update would be to pass in value of positionEncoding, encode the string based on that, then calculate the diffs.
Tests can be added here: https://github.com/microsoft/vscode-black-formatter/blob/main/src/test/python_tests/test_edit_utils.py

Hi @karthiknadig , thanks for the response! I can confirm that the encoding of the document was set on UTF-8 in all the examples.
I didn't capture any log, but I can definitely do if you can give me an hint on what do you need.

In my previous comment I have tried to summarize the problem. Basically, we need to use UTF-16 to calculate the range offsets but return UTF-8 strings.
/cc @dbaeumer is that accurate?

What needs to be utf-8 encoded is the stringified result JSON return from the request. So the strings that you have when you build up the result JSON can be encoded in the  way your programming language wants.

/cc @charliermarsh This is something to note for ruff diff ranges.

I was going to open a separate bug, but I feel it's possible this is related. I had added a comment following a line printing an f string, which happened to also have emojis.

@crwilcox yeah, it seems kinda the same

I was about to file similar bug. The formatter introduces invalid strings when formatting lines with emojis.
Here is screencast of it in action in vscode:

My initial thought was that it might be related to https://github.com/psf/black/issues/1197

My initial thought was that it might be related to psf/black#1197

Have you tried running black on the source code via cli? It shouldn't happen

Have you tried running black on the source code via cli? It shouldn't happen

Just tried it and can confirm the issue does not exist when calling from the cli.
Given this, as a workaround until this bug is fixed we could use a keyboard shortcut to run black from the cli. (via this SO)
Open Preferences: Open Keyboard Shortcuts (JSON)) and paste in this:
// Place your key bindings in this file to override the defaults
[

    {
        "key": "ctrl+shift+f",
        "command": "workbench.action.terminal.sendSequence",
        "args": { "text": "black '${file}'\u000D" }
      }

]

I've experienced this emoji problem multiple times too, would really be helpful to get a fix for this

I have a potential fix for this, please give this a try: https://github.com/microsoft/vscode-black-formatter/actions/runs/7426466173/artifacts/1150857594

Verification steps:

Install the latest pre-release
Create something.py:

s = '😊'

Trigger formatting with black using Format document with.
It should update to:

s = "😊"

So when will this fix be released to the extension marketplace?

@JokerQyou This is in pre-release version.


lint: ban lazy_static crate as a direct dependency

This adds a lint to ban the lazy_static crate as a direct dependency and instead suggests that you use once_cell::sync::Lazy.
I've been building up these lints slowly. at some point i'll need to create a uniform config that can be used across all our repos.

Well this way you can prevent even having the dependency as a direct dependency ;)


Incorrect DNABERT behavior?

Hi, thanks for the great efforts in organizing this easy-to-use benchmark suite!
I noticed a potentially incorrect implementation of DNABertEmbedder:

In the embed() function, any input sequence is first k-merized, tokenized, and padded to sequence length +2. For a sequence of length 512 (as in the case for all tasks except for Gene finding and Enhancer Annotation), the model_input would have a length of 514.
In the current implementation, the model_input would be 1) split into 2 chunk of length 512 and 2, 2) combine the embeddings of shape (512,768) (2,768) -> (514,768), and 3) remove the first and last position embedding to be (512,768). This won't happen if line 238 is  if model_input.shape[1] > 514:

Yes, I think your description of the current implementation is correct. We chunk, combine, and remove the special tokens.  What would be the correct behaviour you expect?

Since the DNABERT paper, "DNABERT takes a sequence with a max length of 512 as input", I would expect that a sequence of length 512 would not be chunked. By changing if model_input.shape[1] > 514 to if model_input.shape[1] > 512 would fix this, since the sequence of length 512 would have a tokenized length of 514.

You're right -  the padding should not be there, it's unnecessary.
  #    padding = 'max_length',
  #    max_length = len(sequence[0])+2,

Commenting out these two lines should give the expected behavior.  I'll do a few more checks to be sure and then update the code.

Thanks for the fix! One additional thing, in line 249,
embeddings.append(embedding[:,1:-1] if remove_special_tokens else embedding)
should be:
embeddings.append(embedding)
otherwise the length of the embedding is inconsistent with the length of the sequence


refactor: use pcre regexp engine for custom rule

IMPORTANT: Please do not create a PR without creating an issue first!
(Any change needs to be discussed before proceeding. Failure to do so may result in the rejection of the pull request).
Summary

Supporting PCRE pattern for custom rule condition.
Proposed of changes
This PR fixes/implements the following bugs/features:

Feature #83

How has this been tested?
Proof:
Before
$ go test -run "^$" -bench "^BenchmarkInitializeCustomRule" -cpu=4 -count 10 | tee /tmp/old.txt
goos: linux
goarch: amd64
pkg: github.com/kitabisa/teler-waf
cpu: 11th Gen Intel(R) Core(TM) i9-11900H @ 2.50GHz
BenchmarkInitializeCustomRules-4   	       1<PHONE_NUMBER> ns/op	51628184 B/op	  137066 allocs/op
BenchmarkInitializeCustomRules-4   	      64	  16842722 ns/op	40538818 B/op	   86929 allocs/op
BenchmarkInitializeCustomRules-4   	      58	  19287922 ns/op	40538565 B/op	   86927 allocs/op
BenchmarkInitializeCustomRules-4   	      61	  18448952 ns/op	40539070 B/op	   86928 allocs/op
BenchmarkInitializeCustomRules-4   	      61	  20377034 ns/op	40539019 B/op	   86929 allocs/op
BenchmarkInitializeCustomRules-4   	      62	  17853707 ns/op	40538648 B/op	   86927 allocs/op
BenchmarkInitializeCustomRules-4   	      66	  18291841 ns/op	40538705 B/op	   86928 allocs/op
BenchmarkInitializeCustomRules-4   	      55	  18771989 ns/op	40538675 B/op	   86928 allocs/op
BenchmarkInitializeCustomRules-4   	      54	  19569256 ns/op	40538421 B/op	   86926 allocs/op
BenchmarkInitializeCustomRules-4   	      57	  18205604 ns/op	40538455 B/op	   86926 allocs/op
PASS
ok  	github.com/kitabisa/teler-waf	14.273s

After
$ go test -run "^$" -bench "^BenchmarkInitializeCustomRule" -cpu=4 -count 10 | tee /tmp/new.txt
goos: linux
goarch: amd64
pkg: github.com/kitabisa/teler-waf
cpu: 11th Gen Intel(R) Core(TM) i9-11900H @ 2.50GHz
BenchmarkInitializeCustomRules-4   	       1<PHONE_NUMBER> ns/op	51602368 B/op	  137023 allocs/op
BenchmarkInitializeCustomRules-4   	      61	  19268530 ns/op	40536153 B/op	   86902 allocs/op
BenchmarkInitializeCustomRules-4   	      52	  19921854 ns/op	40535659 B/op	   86901 allocs/op
BenchmarkInitializeCustomRules-4   	      62	  17659282 ns/op	40535529 B/op	   86900 allocs/op
BenchmarkInitializeCustomRules-4   	      56	  18588371 ns/op	40535385 B/op	   86900 allocs/op
BenchmarkInitializeCustomRules-4   	      52	  19926338 ns/op	40535689 B/op	   86901 allocs/op
BenchmarkInitializeCustomRules-4   	      69	  19771510 ns/op	40535983 B/op	   86902 allocs/op
BenchmarkInitializeCustomRules-4   	      52	  20148745 ns/op	40535630 B/op	   86901 allocs/op
BenchmarkInitializeCustomRules-4   	      66	  18331248 ns/op	40535946 B/op	   86902 allocs/op
BenchmarkInitializeCustomRules-4   	      58	  17675152 ns/op	40536178 B/op	   86902 allocs/op
PASS
ok  	github.com/kitabisa/teler-waf	13.790s

Conclusion
$ benchstat old.txt new.txt
goos: linux
goarch: amd64
pkg: github.com/kitabisa/teler-waf
cpu: 11th Gen Intel(R) Core(TM) i9-11900H @ 2.50GHz
                        │   old.txt   │            new.txt            │
                        │   sec/op    │   sec/op     vs base          │
InitializeCustomRules-4   18.61m ± 9%   19.52m ± 9%  ~ (p=0.579 n=10)

                        │   old.txt    │               new.txt               │
                        │     B/op     │     B/op      vs base               │
InitializeCustomRules-4   38.66Mi ± 0%   38.66Mi ± 0%  -0.01% (p=0.001 n=10)

                        │   old.txt   │              new.txt               │
                        │  allocs/op  │  allocs/op   vs base               │
InitializeCustomRules-4   86.93k ± 0%   86.90k ± 0%  -0.03% (p=0.001 n=10)

Closing issues
Fixes #83
Checklist:

[x] My code follows the code style of this project.
[x] My changes successfully ran and pass linters locally (run make lint).
[x] I have written new tests for my changes.

[x] My changes successfully ran and pass tests locally.

[ ] My change requires a change to the documentation.

[ ] I have updated the documentation accordingly.

Codecov Report
Patch coverage: 80.00% and project coverage change: -0.97% :warning:

Comparison is base (d700f3b) 79.88% compared to head (024aca9) 78.91%.
Report is 8 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master      #92      +/-   ##
==========================================
- Coverage   79.88%   78.91%   -0.97%
==========================================
  Files           5        5
  Lines        1059     1034      -25
==========================================
- Hits          846      816      -30
- Misses        162      164       +2
- Partials       51       54       +3

Files Changed
Coverage Δ

analyze.go
74.84% <80.00%> (+0.06%)
:arrow_up:

teler.go
77.41% <80.00%> (-2.79%)
:arrow_down:

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


Update multiplication-operator_1.cs

Fix comment formatting.

I change comment format to format like here.


Have tests

No tests sounds like a bad idea*:
I would suggest to use linagora/james-memorydocker image to start a JMAP server against which to test the cient...

In general I support presence of tests, but there should be a distinction between unit tests and E2E tests. From my understanding you are talking about the latter.

Should at least have unit tests. Meanwhile we can discuss if we should have or not tests towards some simulated backend like James memory but I think we can agree that no tests at all is not good

My suggestion for unit tests would be https://jestjs.io/. It is lightweight, provides enough functionality for unit testing and has a huge community

From my understanding you are talking about the latter.

Yes, you are right.
From my experience, they are more expensive to write/run but they enable easier refactorings as they make little assumptions about the tested code and its APIs (no mock)
On apache/james a memory integration test suite with 600+ tests takes about 3 minute to run, I believe this would be a good addition to this project.

I started using Mocha, but for parts of the app that are not used yet.
Making E2E tests seems very useful for this project yes.

@alagane I strongly recommend to consider Jest.

Closed by #16 & #17

I don't think this issue should be closed. For now I have found only integration tests. I don't think I can run them locally, since they don't contain any mocks.
Therefore IMO there also should be unit tests, beside integrations tests.


errors prerendering site from mdast-util-to-hast: state.patch is not a function

Encountered some issues when upgrading Nuxt Image to the latest docus version, flowing from mdast-util-to-hast, it seems.

Build logs
12:06:37 PM: [error] [nuxt] [request error] [unhandled] [500] state.patch is not a function
12:06:37 PM:   at defaultUnknownHandler (./node_modules/mdast-util-to-hast/lib/state.js:542:9)
12:06:37 PM:   at one (./node_modules/mdast-util-to-hast/lib/state.js:466:10)
12:06:37 PM:   at all (./node_modules/mdast-util-to-hast/lib/state.js:488:22)
12:06:37 PM:   at containerComponent (./.nuxt/prerender/chunks/nitro/nitro-prerenderer.mjs:10559:55)
12:06:37 PM:   at one (./node_modules/remark-rehype/node_modules/mdast-util-to-hast/lib/traverse.js:56:51)
12:06:37 PM:   at all (./node_modules/remark-rehype/node_modules/mdast-util-to-hast/lib/traverse.js:81:22)
12:06:37 PM:   at root (./node_modules/remark-rehype/node_modules/mdast-util-to-hast/lib/handlers/root.js:16:41)
12:06:37 PM:   at one (./node_modules/remark-rehype/node_modules/mdast-util-to-hast/lib/traverse.js:56:51)
12:06:37 PM:   at toHast (./node_modules/remark-rehype/node_modules/mdast-util-to-hast/lib/index.js:272:16)
12:06:37 PM:   at ./node_modules/remark-rehype/lib/index.js:70:20
12:06:37 PM:   at wrapped (./node_modules/trough/index.js:115:27)
12:06:37 PM:   at next (./node_modules/trough/index.js:65:23)
12:06:37 PM:   at done (./node_modules/trough/index.js:148:7)
12:06:37 PM:   at then (./node_modules/trough/index.js:158:5)
12:06:37 PM:   at wrapped (./node_modules/trough/index.js:136:9)
12:06:37 PM:   at next (./node_modules/trough/index.js:65:23)
12:06:37 PM:   at done (./node_modules/trough/index.js:148:7)
12:06:37 PM:   at then (./node_modules/trough/index.js:158:5)
12:06:37 PM:   at wrapped (./node_modules/trough/index.js:136:9)
12:06:37 PM:   at next (./node_modules/trough/index.js:65:23)
12:06:37 PM:   at done (./node_modules/trough/index.js:148:7)
12:06:37 PM:   at then (./node_modules/trough/index.js:158:5)
12:06:37 PM:   at wrapped (./node_modules/trough/index.js:136:9)
12:06:37 PM:   at next (./node_modules/trough/index.js:65:23)
12:06:37 PM:   at Object.run (./node_modules/trough/index.js:36:5)
12:06:37 PM:   at executor (./node_modules/unified/lib/index.js:321:20)
12:06:37 PM:   at Function.run (./node_modules/unified/lib/index.js:312:5)
12:06:37 PM:   at executor (./node_modules/unified/lib/index.js:393:17)
12:06:37 PM:   at Function.process (./node_modules/unified/lib/index.js:383:5)
12:06:37 PM:   at ./.nuxt/prerender/chunks/nitro/nitro-prerenderer.mjs:10705:12
12:06:37 PM:   at new Promise (<anonymous>)
12:06:37 PM:   at generateBody (./.nuxt/prerender/chunks/nitro/nitro-prerenderer.mjs:10696:10)
12:06:37 PM:   at parse (./.nuxt/prerender/chunks/nitro/nitro-prerenderer.mjs:10778:22)
12:06:37 PM:   at async Object.parse (./.nuxt/prerender/chunks/nitro/nitro-prerenderer.mjs:10822:20)
12:06:37 PM:   at async transformContent (./.nuxt/prerender/chunks/nitro/nitro-prerenderer.mjs:11781:18)
12:06:37 PM:   at async parseContent (./.nuxt/prerender/chunks/nitro/nitro-prerenderer.mjs:11940:18)
12:06:37 PM:   at async getContent (./.nuxt/prerender/chunks/nitro/nitro-prerenderer.mjs:11917:18)
12:06:37 PM:   at async Promise.all (index 0)
12:06:37 PM:   at async getContentsList (./.nuxt/prerender/chunks/nitro/nitro-prerenderer.mjs:11881:20)
12:06:37 PM:   at async ./.nuxt/prerender/chunks/nitro/nitro-prerenderer.mjs:9360:18
12:06:37 PM:   at async ./.nuxt/prerender/chunks/nitro/nitro-prerenderer.mjs:12087:20
12:06:37 PM:   at async Object.handler (./node_modules/h3/dist/index.mjs:1247:19)
12:06:37 PM:   at async toNodeHandle (./node_modules/h3/dist/index.mjs:1322:7)
12:06:37 PM:   at async ufetch (./node_modules/unenv/runtime/fetch/index.mjs:9:17)
12:06:37 PM:   at async $fetchRaw2 (./node_modules/ofetch/dist/shared/ofetch.502a4799.mjs:180:24)
12:06:37 PM:   at async ./.nuxt/prerender/chunks/app/server.mjs:1741:16
12:06:37 PM:   at async Promise.all (index 3)
12:06:37 PM:   at async refresh (./.nuxt/prerender/chunks/app/server.mjs:1953:12)
12:06:37 PM:   at async ./.nuxt/prerender/chunks/app/server.mjs:1991:22
12:06:37 PM:   at async Object.callAsync (./node_modules/unctx/dist/index.mjs:53:16)

@Atinux This fixed it for me


[docs] Rewrite the docs for diff

I intend to squash these commits, but this is what I'd consider to be pretty close to the final version of the new diff docs.
As I wrote more and more, it made sense to create a brand new file. The diff docs for specifically the GUI (https://github.com/Szelethus/codechecker/blob/diff_docs_rewrite/web/server/vue-cli/src/assets/userguide/userguide.md#compare-runs) seem to be a mess, but I'm not sure there is a need for rewriting, and if there is, I'm pretty sure it can wait a little :)
Check out the final docs here: https://github.com/Szelethus/codechecker/blob/diff_docs_rewrite/docs/web/diff.md
Depends on #3995 and #3996.

TODO: I linked my branch to the 6.23.0-rc1 release notes, that needs to point to the Ericsson/master branch after release.

I fixed all the remaining comments. Unless there is factually wrong information found here, I strongly insist on finally landing this patch. Its already miles better than the current docs, and we can always make it prettier later down the line.


Fix fft dtype for norm='ortho'

FFT orthogonal normalization factor dtype was undefined.

Hmm... looks like there are some new test failures. Do you understand why that is?

Not really sure...
allclose failed with some quite big differences (8 vs 64), for a change of dtype. That's strange.

A new unit test that passes only with this change would probably also be a good idea, to ensure we don't have a regression.

It looks like the failure has input of type bool, which suggests that the new dtype casting may be throwing away information. You should probably cast to the expected output type rather than the input type.

I added some checks as part of testFftn (with some duplicated computations...)

Thanks!


Confusing error message when using different prop type and casting from a type with private prop

Say I have two classes and I want to cast one type into the other like this:
class Test {
  private foo: string = 'foo';
  bar: string = 'bar';
}

class MockedTest {
  bar: string = 'mocked-bar';
}

const myTest: Test = new Test();
const myTest2: Test = new MockedTest() as Test;

This works quite well. But if I change the property in MockedTest from bar: string = 'mocked-bar'; to   bar: number = 1; I get a confusing error message.
class Test {
  private foo: string = 'foo';
  bar: string = 'bar';
}

class MockedTest {
  bar: number = 1;
}

const myTest: Test = new Test();
const myTest2: Test = new MockedTest() as Test;
                      ~~~~~~~~~~~~~~~~~~~~~~~~
                      ^ Neither type 'MockedTest' nor type 'Test' is assignable to the other. Property 'foo' is missing in Type 'MockedTest'.

We actually had this error when we tried to mock our classes in unit tests and couldn't figure out why property foo throws the error until we noticed a different property had a wrong type.
A better error message would be that property bar should be a string and not a number.

Note : if you have a private member, that effectively makes the class nominal and you will have a hard time mocking it without assertions:
class A {
	private foo: number;
}
class B {
	private foo: number;
}
let a:A, b:B;
a = b; // Error
b = a; // Error

And of course assertions can siliently ignore certain type incompatabilities that would result in runtime errors :rose:

I think this is just a consequence of the way the compiler generates error messages - it only puts the first reason. In this case it complains about the first difference between the two types.

There is not a clear way to define what error message is "better" than another. the compiler is checking new MockedTest() as Test, so either 1. MockedTest is assignable to Test, or 2. Test is assignable to MockedTest. neither were true, and as @Arnavion you get the first error.
I do not think there is much we can do about this behavior.


i did not find any way to pass JSON instead of Sending parameters

i was going to call a API that takes more then 15 parameters in Body and it doesn't looks good to send such number of parameters in function call /Moya Api Call
and I think Passing Full JSON Will be a Good option for such type of problems

@kaleemozitech  Please take a look at my answer #1629
This is what you need? If yes, I think it can be closed.

@SeRG1k17 #1629 did not solved the issue of passing JSON (Created from Some Model)
i am talking about
case .youCase, return .requestParameters(parameters: myJSONobject, encoding: URLEncoding.queryString)

@SD10  thanks


merge commits from rustfmt-2.0 branch

Thought it might be helpful to go ahead and merge these commits to minimize the chance of potential conflicts, but can close this if it'd be better to wait
Follow up of #3906

Ah looks like this needs a bump based on the rustc-ap* 606 changes

Awesome, thank you!


Head

Also , this sort arrow doesn't have any work , arrange it so that it can sort the states by name.

Kindly delte this issue.

Please delete this complete issue.


FIELD        Field update error to field.carriota.com: 400 null { error: 'bad format' }

Hi,
since the last start field.cli is giving the following errors:
FIELD        Field update error to field.carriota.com: 400 null { error: 'bad format' }

Hi,
I've copied my ID to a new file in my host machine volume and it didn't work.
Deletet it and let  CarrIOTA Field create a new one.
No more errors. Even though it lost all the statistics.


tweaks to _core_utils

Change Summary
some trivial cleanup to _core_utils::Walk.
Related issue number
related to #6768
Checklist

[ ] The pull request title is a good summary of the changes - it will be used in the changelog
[ ] Unit tests for the changes exist
[ ] Tests pass on CI
[ ] Documentation reflects the changes where applicable
[ ] My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

please review.


[MINOR] fix typo

Tips

Thank you very much for contributing to Apache Hudi.
Please review https://hudi.apache.org/contributing.html before opening a pull request.

What is the purpose of the pull request
Fix typo
Brief change log
Fix typo
Verify this pull request
(Please pick either of the following options)
This pull request is a trivial rework / code cleanup without any test coverage.
Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Good catch


Enable to restrict the anchor point for FloatingPanelAdaptiveLayoutAnchor

Addressed #469 and resolved #413.

Can we increase priority of this pull request?

Of course 😄 Thank you for your feedback. I was wondering if this feature was really necessary because there was no feedback. I'm going to work in progress to merge this.

Thank you @scenee!
This feature was indeed necessary 😄


Hitting error when attempting to create org:Inventory resource

upstream: https://github.com/Juniper/terraform-provider-mist/issues/5

closed as resolved upstream


Create UI for Winning Submission and show on VotingResults

https://github.com/sopra-fs24-group-12/PeekSeek-client/compare/ca9cb1bb0a02b245133647f891bfe00adf8138b4...87db439b047ae26792263d5e8a5e18a35ac4ba8a


Provide method to add tags to the accesslogs s3 bucket

The remote_state configuration block currently allows specifying accesslogging_bucket_name for s3 remote state.  This is a feature request to add the capability to add tags to this bucket accesslogging_bucket_tags for example, similar to s3_bucket_tags.

This issue should be solved by https://github.com/gruntwork-io/terragrunt/pull/2355