Link to cross compile libraries is bunk

In the tutorial for cross compiling Windows from Linux, there is a link to download the mingw-w64-gtk3 libraries from win32builder.gnome.org. However, that site does not exist. Is there another place to get the libraries for distributions other than Arch?

The only place I found these packages was on Fedora (https://apps.fedoraproject.org/packages site broken atm :disappointed:).
Before anyone tries to work with this, you need to know that the crt2.o file shipped with the Rust toolchain is (was?) broken, and needs to be copied from /usr/x86_64-w64-mingw32/sys-root/mingw/lib/ to $RUSTUP_INSTALL_DIR/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-pc-windows-gnu/lib/. Once that is done, it should work.
For me this is a little too much work to do every time which is why I made a docker container for this exact purpose.

cd to your code
Start the container like this:

docker run \
    -it \
    --volume=$(pwd):/home/circleci/project \
    --volume=$(pwd)/.cargo-cache:/home/circleci/.cargo/registry \ # this is optional, make sure that $(pwd)/.cargo-cache exists before running this to avoid permission errors
    olback/rust-gtk-windows /bin/bash

When you're in the container, simply run your build command:

export RUST_BACKTRACE=full
export PKG_CONFIG_ALLOW_CROSS=1
cargo build --release --target=x86_64-pc-windows-gnu

Commenting to confirm what olback said. On Fedora the dlls are availabe after installing the relevant mingw packages (for example mingw64-gtk3). Subsequently you can find the dlls in /usr/x86_64-w64-mingw32/sys-root/mingw/bin.


[minor] Remove matomo from other dependencies

But keep the image around until June 2025 for continued support until then

Relevant discussion https://islandora.slack.com/archives/CM5PPAV28/p1715949100627349

I won't have my laptop till Monday, so I'm a bit limited. But I've noticed there are other references to Matomo, to be removed.
Though I would suggest that we completely remove Matomo and do a major release instead. If organizations want to upgrade they can continue to use the previous release of the Matomo image.


support data transformation on the query result before visualize

Sometimes, user have defined metrics on the query result itself. For example

new metric column per row = col(A) / col(B)
further aggregate across different rows:  (A B 1) (A C 2) => (A B/C=0.5)

No matter what - we will pass the raw JSON blob to user and let it transform uses its own transform lambda, new schema will be discovered in the transformed result.

solved by SDK to support pivot and map functions.


wasi: Handle EFBIG from OS onfd_filestat_set_size

This commit handles potential EFBIG returned from the OS and maps it to WASI's fbig.  It also fixes an integer truncation bug in the fd_filestat_set_size handler.
fixes https://github.com/tetratelabs/wazero/issues/1870

cool


Not a problem, just recomendation

I like this program very much. But I have a recommendation...
It would be very useful if the program would remember the size and the position when you close it. So next time it would open at the same size and position. Now you must resize it and position it every time...
Could this be done, please?

What is the purpose of different position and size, you ask for ?
For now program have ability to set screen and full size in command line parameters: https://user-images.githubusercontent.com/36440722/36472447-aaf96b04-1713-11e8-921c-6fa95168e6a7.jpg

I have 6 cameras and I like to view them on my 4k monitor at the top of the screen. I resize the window to this: https://drive.google.com/file/d/1SeOp9ukTJvFWRnYBDGGXvOZ6JzaZGgPO/view?usp=drivesdk.
But when I close the program and reopen it then it's like this: https://drive.google.com/file/d/1EQMZBPJrsdTtCK4uz5BlHGOT0CPgHTvB/view?usp=drivesdk

I see... I think, It's a good function.
Will try to find some time to add it.

Happy new year.


Deprecated function camel_case in Laravel 5.7+

Since global string and array helpers are deprecated (Laravel news) this package isn't working anymore with newest versions of Laravel.
Proposed solution
use Illuminate\Support\Str;

public function encodeArray($array)
{
	$newArray = [];
	foreach ($array as $key => $val) {
		// Deprecated
		// $newArray[\camel_case($key)] = $this->encodeJson($val);

		// Use this directly
		$newArray[Str::camel($key)] = $this->encodeJson($val);
	}
	return $newArray;
}

Another workaround since pull request is still open:
app/Http/Helpers.php
use Illuminate\Support\Str;

if (!function_exists('camel_case')) {
    function camel_case($input)
    {
        return Str::camel($input);
    }
}

Fixed with version 2.0.


[Don't merge yet] attempt to use aasm to simplify model structure

https://www.pivotaltracker.com/story/show/167550020

AASM works differently than described in its documentation.
The benefits of such a transformation are doubtful.


⚠ ClamAV has degraded performance

In e64bbf5, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 69 ms

Resolved: ClamAV performance has improved in b853239 after 7 minutes.


Could leveldb avoid some compactions? [JIRA: RIAK-1810]

While loading up some data (64 workers loading to Q=4 ring starting off with <Key:64> from 1..64+64) I noticed that after loading for 12 hours, 676 / 24921 compactions (~3%) were single file from lower level, zero files from higher level.  Should these be moves?
2015/05/17-02:01:17.614037 7f85b1ffb700 Compacted 1@2 + 0@3 files => 209776678 bytes
2015/05/17-02:03:21.585423 7f85b1ffb700 Compacted 1@4 + 0@5 files => 419553560 bytes
2015/05/17-02:09:42.569225 7f85b27fc700 Compacted 1@2 + 0@3 files => 209776563 bytes
2015/05/17-02:11:44.670296 7f85b27fc700 Compacted 1@2 + 0@3 files => 209777140 bytes
2015/05/17-02:13:37.785211 7f85b1ffb700 Compacted 1@4 + 0@5 files => 419553547 bytes
2015/05/17-02:13:41.615433 7f85b17fa700 Compacted 1@2 + 0@3 files => 209777115 bytes
2015/05/17-02:15:50.199730 7f85b1ffb700 Compacted 1@2 + 0@3 files => 209776844 bytes
2015/05/17-02:17:18.329543 7f85b17fa700 Compacted 1@4 + 0@5 files => 419553584 bytes
2015/05/17-02:18:56.660011 7f85b27fc700 Compacted 1@2 + 0@3 files => 209776751 bytes
2015/05/17-02:25:59.590528 7f85b17fa700 Compacted 1@2 + 0@3 files => 209777167 bytes
2015/05/17-02:27:45.373177 7f85b2ffd700 Compacted 1@4 + 0@5 files => 419553417 bytes
2015/05/17-02:28:21.881114 7f85b27fc700 Compacted 1@2 + 0@3 files => 209776898 bytes
2015/05/17-02:36:01.577150 7f85b1ffb700 Compacted 1@2 + 0@3 files => 209776876 bytes
2015/05/17-02:37:23.790984 7f85b2ffd700 Compacted 1@4 + 0@5 files => 419553682 bytes

This was addressed in Dec 2014.  See: https://github.com/basho/leveldb/pull/146
Likely to be part of 2.0.6.


Add support for WebRTC

Is your feature request related to a problem? Please describe.
We must allow syft.js and other worker libraries to connect via the WebRTC protocol.
This issue is blocked by:

https://github.com/OpenMined/PyGrid/issues/411

Describe the solution you'd like
To allow for the direct, peer-to-peer connection of workers, we need PyGrid to act as a signaling server in the WebRTC workflow. The good news is that this code is 100% feature-complete in grid.js and may (more or less) be copied and changed from Javascript to Python.
Additional context
Here is some required reading for fully understanding the requirements of this ticket.
In particular, please read the sections titled webrtc: join-room, webrtc: internal-message, and webrtc: peer-left. The API in PyGrid must follow the API in grid.js 100%.

Closed by #447


Report rule eval failures, remove extraction.Result type

@beorn7

This depends on this client library change: https://github.com/prometheus/client_golang/pull/43

Otherwise :+1:


button text option doesn't set

previous_button_text & next_button_text value doesn't change even after you pass it in options

I've just checked it and it works as expected.
Maybe you are not passing the options properly.
Check this.

Your right. I had an error on my part. closing issue

Great!


The same general report as for workers.

Proposal
Provide a short description of the change you are proposing and the reasons for it.
Checklist

[x] I have made this pull request to the master branch
[x] I have run npm run lint and there are no errors

Awesome, great job! You just forgot again to add routes' permissions to the README.md and I left a comment to fix the broken "Run" after a customer was reset.


Spec: Specify Create pNSM

Create a pNSM that is capable of creating Kubernetes resources if they do not exist.
E.g. if a VPN is requested but the VPN does not exist, create the pod then facilitate the connection.
https://docs.google.com/document/d/1hI0960GLsvBveBn7EqRs7aih1RFeEk6KCNsplv8zQko/edit

Pinned to call off stalebot


CustomBanList.json File Not Working?

I have a custom ban list file (CardBanList.json) but it doesn't work with the new update. Not sure if there's something wrong with my file or if I'm not putting it in the right place after the new update for Offline Master Duel. The current place for my .json file is D:\Steam\steamapps\common\Yu-Gi-Oh!  Master Duel\YgoMaster\Data. If that's the right place, then can you send me a working CardBanList.json file or tell me how I can extract the Online Master Duel card ban list? Thank you!

I figured out my issue. If possible, could you make a note somewhere telling people how they can make their own ban list?
How I Solved My Issue: Deleted "CardBanList.json" file because that doesn't work anymore w/ YgoMaster v1.35
Custom Ban List Tutorial (Windows PC):

Open the "Data" folder in "YgoMaster" and open "Regulation.json"
Press "Ctrl & F" at the same time then type "1011":   type it exactly like that then press "Find Next"
Scroll Down until you find "a0": and some numbers, look at the following key below

a0 = forbidden
a1 = limited
a2 = semi-limited
a3 = no longer on the list (you can have card ID's here or just delete any card ID's in this section)

The numbers you will see under these sections in "Regulation.json" are card ID's - I'll attach a Microsoft Excel Sheet w/ ID's
-If for some reason the attachment doesn't work for you then use the link below
https://docs.google.com/spreadsheets/d/1IXpwCaabi47Ly8dAf4aJtFdYwi29yGkCJ4bvMhnsvc8/edit#gid=1081892055

Using the spreadsheet w/ the card ID's you can press "Ctrl & F" to find the Yu-Gi-Oh! card you are looking for.

After you find the card you are looking for, copy the card ID number.

Go back to the "Regulation.json" file and paste the card ID number like the other numbers you see.
-You can do this for sections a0, a1, a2, or a3

You can also delete cards from a ban list by deleting the card ID numbers too. Congrats you have your own ban list.

Extra Info:
-Refer to "RegulationInfo.json" for more info. This tutorial is only for the "Normal/Standard" duel regulation
-I added an example text document to help get you started if you want to copy & paste your list into "Regulation.json"
1_Custom Ban List Tutorial.txt
2_Regulation (1011 - normal banlist) - Example.txt
Yu-Gi-Oh! Master Duel Card IDs.xlsx

At some point I'd like to add some UI based tools for editing things like the ban list, solo mode, shop packs, structure decks, etc.

Press "Ctrl & F" at the same time then type "1011"

This will change over time as the ids in RegulationInfo.json change which impacts Regulation.json so you need to open RegulationInfo.json, search for IDS_CARDMENU_REGULATION_NORMAL, take the value to the left of that and use that to Ctrl+F.
I'm going to close this as you answered your question. Feel free to make a PR to add the info to https://github.com/pixeltris/YgoMaster/tree/master/Docs

Hey @pixeltris I'm not sure if I did the pull request correctly or not since I never done one before, but I'm going to leave the link to it just in case for you to check it out whenever you get the chance. Also, I didn't see an option where I could upload the .txt document that has the updated explanation for you to look over. If there's anything that needs changing, I could change it or you could change it to your liking.
1_Custom Ban List Tutorial.txt
https://github.com/pixeltris/YgoMaster/compare/master...RedRobin16:YgoMaster:patch-1


update context, react-router

see if react-router-dom 5.0 works well enough to use

https://github.com/ReactTraining/react-router/issues/6885


i18n(es): update datocms, decap-cms & hygraph

Description (required)
updates datocms, decap-cms & hygraph based on this commit 0bad0edf9ee997a9be8ff4a4af3e4107a498a3e1

Related issues & labels (optional)

Closes # N/A
Suggested label: i18n

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

es
guides/cms/datocms.mdx
Localization changed, will be marked as complete.

es
guides/cms/decap-cms.mdx
Localization changed, will be marked as complete.

es
guides/cms/hygraph.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


chore: Remove old policy addon images

What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Flagged for CVEs in 20221215 and 20220512 which are not used in >=1.24. Removing as 1.23 is EOL
Which issue(s) this PR fixes:

Requirements:

[x] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

@alexeldeib Just to confirm, we've got about 15k clusters still on 1.23, for those that don't autoupgrade to 1.24 will they still have access to the old image? Thank you!

yes, this is purely a caching mechanism, any cluster can use any images

Holding off for one more person's sign off, my teammate will merge after that


Reviewers' statistics notification

As user at reviewers' statistics, I want to see stripe at list's row where any type of notification appears, additionally I want to see notification at list's row next to the value with a warning.
Show a notification if a reviewer has to check more PRs than are specified in Common warning points #215
Show a notification if the longest waiting PR is waiting longer than it is specified for its repository. #216

Needs #215

I will do this


Creates empty page ii depending on how often you run pdflatex

Prerequisites

[x] Put an X between the brackets on this line if you have done all of the following:

Check that you are using the latest version of kaobook.
Check that your issue isn't already filed: https://github.com/fmarotta/kaobook/issues

Description
When I run pdflatex once, I get a PDF with two pages: page i for the front page and page 1 for the chapter
If I run pdflatex one more time, the PDF has three pages: there's now a page ii which is complete empty.
If I now run pdflatex again, the PDF has two pages again.
Basically: running pdflatex an odd number of times: 2 pages; and even number of times: 3 pages
I'm not sure if I'm doing something wrong, or if this is a problem with the template.
Minimal example:
\documentclass{kaobook}
\usepackage[english]{babel}
\usepackage{blindtext}

\begin{document}

\title{Bug Report}
\author{Author}
\date{\today}

\frontmatter

\KOMAoptions{twoside=semi}
\maketitle
\KOMAoptions{twoside=false}

\mainmatter
\setchapterstyle{kao}

\chapter{First Chapter}
\blindtext

\end{document}

This is a weird bug.
Here is what I found out:

The .aux file changes between the runs.
If I delete the .aux file and compile the document, it will always have two pages.
The .aux file after 2, 4, 6, ... runs is identical.
The .aux file after 3, 5, 7, ... runs is identical.
The .aux file after 1 run is not the same as after 2 or 3 runs.
The problem appears only in very minimal examples. Inserting a \tableofcontents just before \mainmatter fixes the bug.
The bug appears with pdflatex, LuaLaTeX and XeLaTeX.

I am not familiar with reading .aux files, but perhaps the following is helpful to someone:
Difference between .aux files after 1 and 2 runs

Difference between .aux files after 2 and 3 runs

Difference between .aux files after 1 and 3 runs

The problem appears only in very minimal examples.

My document is around 60 pages so size doesn't seem to matter...

Inserting a \tableofcontents just before \mainmatter fixes the bug.

... but this seems to be true.  After I added a TOC I haven't noticed this issue. (Now I always get the empty page, which I personally don't like, but which I guess is the expected behaviour.)

The problem appears only in very minimal examples.

My document is around 60 pages so size doesn't seem to matter...

Sorry, with "minimal examples", I didn't mean "short documents". I was referring to the fact, that once the book contains all parts a traditional printed book has, e.g.  \tableofcontents, the bug seems to go away.
The bug should, however, be fixed anyway.

Now I always get the empty page, which I personally don't like, but which I guess is the expected behavior.

The empty page is a legacy from the time where books were still primarily printed and not read on screen.
I agree, that this empty page is superfluous nowadays.

@AlexanderZeilmann right, agreed. Thanks for posting your analysis!

The bug is caused by \KOMAOptions{twoside=semi}-\KOMAOptions{twoside=false}, which is a workaround I added in the old days because in one-side mode the \uppertitleback and \lowertitleback are not displayed. Currently I have removed the \KOMAOptions lines from my examples in GitHub, but I think they are still there in the Overleaf version of kaobook, and many users of course still have them in their documents. By removing the \KOMAOptions lines around \maketitle, the bug disappears, but \uppertitleback and \lowertitleback are not printed unless twoside=true.
If you want to remove the extra white page before the first chapter, simply pass twoside=false as a class option, and omit the KOMAOptions lines around \maketitle. Note that twoside=false is not the same tihng as twoside=true + open=any, because with the latter combination the extra white page is still there.
As general rules, I'd suggest to:

Never use \KOMAOptions.
Choose twoside=true or twoside=false according to your needs, but beware that with twoside=false you don't have the upper/lower titleback.
If you don't want the extra whitepage in the frontmatter, choose twoside=false.
If you want to have the upper/lower titleback, choose twoside=true.
If you want to have the upper/lower titleback, and a one-side document at the same time, add manually the contents that you'd put in the upper/lower titleback. For instance, the copyright page in the example_and_documentation.pdf can be achieved by writing

...
\makeatletter
\@titlehead
\vfill
\textbf{Disclaimer}\\
You can edit this page to suit your needs. For instance, here we have a no copyright statement, a colophon and some other information. This page is based on the corresponding page of Ken Arroyo Ohori's thesis, with minimal changes.

\medskip

\textbf{No copyright}\\
\cczero\ This book is released into the public domain using the CC0 code. To the extent possible under law, I waive all copyright and related or neighbouring rights to this work.

To view a copy of the CC0 code, visit: \\\url{http://creativecommons.org/publicdomain/zero/1.0/}

\medskip

\textbf{Colophon} \\
This document was typeset with the help of \href{https://sourceforge.net/projects/koma-script/}{\KOMAScript} and \href{https://www.latex-project.org/}{\LaTeX} using the \href{https://github.com/fmarotta/kaobook/}{kaobook} class.

The source code of this book is available at:\\\url{https://github.com/fmarotta/kaobook}

(You are welcome to contribute!)

\medskip

\textbf{Publisher} \\
First printed in May 2019 by \@publishers

I think this behaviour is OK, but let me know :)

Sounds good. Maybe you can add the general rules to the docs, but anyway since you removed the KOMAoptions from the examples I think this can be closed.


Fix qualified imports

Solve #1265 and the includes with examples/nitcorn/src/xymus_net.nit

Cool! +1

:shipit:


[BUG] typewriter.jpg is linked from pages but not in repo

Expected behavior
typewriter.jpg should not be reported as missing on page load
Actual behavior
typewriter.jpg is reported as missing on page load
Reproduction steps
load main app page in browser
How to fix
Either add typewriter.jpg to repo or remove links to it from app

Fixed


Dafny extension spawns endless instances of Z3.

Hello,
I'm really enjoying learning Dafny and the plugin is essential so great work so far!
I keep running into the following issue.

After using dafny for a while on both mac and windows using extension version Dafny v2.4.0, there is an explosion of z3 processes created and they never seem to close. Eventually, it seems like it overwhelms my system and I am forced to close and restart vscode. Sometimes on mac even after I exit vscode I need to manually kill dotnet and z3.

If you look at the Dafny version on the right side of the VSCode status bar, what does it say? The current version is <IP_ADDRESS>511. We did have some bugs in older versions related to cleaning up old processes, but as far as I know they've been fixed in the latest version.

That is the version I see in my editor.

Reproduction as reported by @MikaelMayer:
Copy the following code and
class Test {
    var a: nat
    var b: nat
    var c: nat

    predicate Valid()
        reads this
    {
        && a < b
        && b < c
    }

    method Foo()
        requires Valid()
        ensures Valid()
        modifies this
    {
        c := 10;
    }
}

put it in VSCode. Look at the task manager, it has one dangling z3 process. Add newlines in this file, wait, every newline you add, one more z3 process is created

I can confirm the reproduction steps work for me as well.


Can't connect to NodeJS socket io server from C++ client

Hi Everyone,
I am trying to connect NodeJS socket io server from  socket io c++ client, But I keep getting below error on c++ side.
[2021-10-05 15:32:55] [error] handle_read_frame error: asio.system:104 (Connection reset by peer)
[2021-10-05 15:32:55] [info] asio async_shutdown error: asio.system:32 (Broken pipe)
[2021-10-05 15:32:55] [disconnect] Disconnect close local:[1006,Connection reset by peer] remote:[1006]

Below is my socket io server which is attached to existing https server, which is running on docker container
const fs = require("fs");
const httpServer = require("https").createServer({  key: fs.readFileSync("/tmp/key.pem"),  cert: fs.readFileSync("/tmp/cert.pem")});
const io = require("socket.io")(httpServer, {
           allowEIO3: true,
            cors: {
                methods: 'GET,POST,PATCH,DELETE,OPTIONS',
                optionsSuccessStatus: 200,
                origin: true,
                credentials: true,
                allowedHeaders: ["content-type"]
            }});
io.on("connection", socket => { /* ... */ });
httpServer.listen(3000);

I have integrated socketio c++ client as static library in cmake.
find_library(sioclient_location NAMES libsioclient_tls.a)
message(STATUS ${sioclient_location})

add_library(sioclient_tls STATIC IMPORTED)
set_target_properties(sioclient_tls PROPERTIES IMPORTED_LOCATION ${sioclient_location})
target_link_libraries(TestNode  sioclient_tls)

I tried to create c++ client almost like console example using lock and conditional wait after calling connect method.
sio::client m_client

m_client.set_open_listener(
            std::bind(&TestNode::onConnected, this));
m_client.set_close_listener(
            std::bind(&TestNode::onClose, this, std::placeholders::_1));
m_client.set_fail_listener(
            std::bind(&TestNode::onFail, this));

m_client.connect("https://localhost:3000"); // I did try using "<IP_ADDRESS>" and I exposed the port in my docker compose
m_client. socket()->on(
            "new_message",
            std::bind(&TestNode::OnMessage, this, std::placeholders::_1));

Any ideas?

Any update on fix or workaround of this issue? I am facing similar issue where I am unable to connect to a NodeJS socketio server. The server runs socket.io version 4.4.1. The error I see from my c++ client:
Error: No active session
[2022-02-27 22:45:08] [connect] Successful connection
[2022-02-27 22:45:09] [error] handle_read_http_response error: websocketpp.transport:7 (End of File)
Error: No active session

Hi @AnushaPulichintha , I figured out the issue for me which could be a possible issue in this case.
The issue is that when using EIO v3 the server sends the CONNECT message packet. However, for EIO v4, the client has to send the CONNECT message packet.
CONNECT message packet is identified by text 40 where,
4 => engine.io packet type MESSAGE
0 => socket.io packet type CONNECT
This issue seems to be in handling of the engine.io protocol, after the shift from v3 to v4.
If this is identified as a bug, it needs to be fixed.

Hi @hrishibawane could you point me to the part of the engine.io documentation where this is addressed? From the socket.io-protocol documentation (link) I see that the client is the one that should always send the CONNECT message packet

@jmigual Yes it does but somehow when I was using EIO v3 I (as client) didn't need to send CONNECT message packet to the server as I was receiving it from the server (verified from a Postman client too). In case of EIO v3, the client was not sending any extra messages after the initial connect attempt. The namespace is default namespace.
If the client explicitly needs to send a CONNECT even for a default namespace, I am not sure why the server sent it in the above case.


feat/cached-img

I checked it and the cache is used quite frequently as we have many parallel things that call the screen grab(). Only downside is that we might have a maximum delay of 20ms to get the "new" frame.
TODO: making it thread safe...

I love this idea.
I'm curious--if we know a frame lasts 40 ms why do we check if within 20 ms?
Gonna tag a few people I think this might be interesting to. @Ezro @Aimware0 @ramfjord

I was thinking nyquist theorem, but actually the "wavelength" is 80ms. Thus 40ms will be good. Thx for pointing this out.

I did some testing and it felt like I saw some issues where we would click e.g. on waypoints with a few frames delay or over teleporting. But could have been just random bug. I will test this a bit more and merge it myself once I am more convinced that it is fine.


Fixed some grammar errors

A contribution to the issue: https://github.com/tiagoporto/swillboilerplate.rocks/issues/1

Thanks @lhphan, there some conflicts, can you fix please?


Add switch for claw version prior to 2.1

The package was not working anymore with older version

launch jenkins --test=root cosmo<EMAIL_ADDRESS>real_type=double cosmo_target=gpu +claw +eccodes

@elsagermann FYI the cosmo master and PR are currently broken. This should fix them. I will merge without review to have test over night before the upgrade

the spack_PR jenkins test is using install cosmo which is not taking the same claw version as devbuildcosmo.
The devbuildcosmo and installbuildcosmo have been tested manually


[BUG]

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
Couldn't read config /config/config.yml Service is not in known list "mq"
Expected Behavior
Create and use proper config with helm
Steps To Reproduce
jobs:
- region: eu-west-1
  type: "es"
  searchTags:
    - Key: type
      Value: ^(easteregg|k8s)$

Anything else?
https://artifacthub.io/packages/helm/mogaal/prometheus-yace-exporter?modal=values

Did you use the newest version?

I use default from helm tag: v.0.13.7

with latest image it's ok. but search tags do not work


[BUG] export [type] FieldPath from "@pankod/refine-react-hook-form"

Describe the bug
Typescript Type FieldPath is not exported from @pankod/refine-react-hook-form.
However it is a valid type exported from react-hook-form
Steps To Reproduce
import type { FieldPath } from "@pankod/refine-react-hook-form" Does not work
import type { FieldPath } from "react-hook-form" Does work
Expected behavior
All types of react-hook-form should exported from @pankod/refine-react-hook-form
Screenshot
No response
Desktop
No response
Mobile
No response
Additional Context
thank you

Hey @capsloq
All missing types in react-hook-form have been exported 🚀


  Look at f61ccb1 as an example.

Thanks Jeff, will sort out


container copy on dir backend on xenial hangs

It seems that something is different with how xenial's rsync behaves w.r.t. exiting when it gets EOF (I think, this is all just based on a 5 minute look at the problem). The result of this is that lxc copy foo otherhost:foo hangs indefinitely when using the directory backend. The workaround here is just to use ZFS.

Container copy and move on the try-it server appear to work fine and those I believe are using rsync, so it may be a bit trickier than we first thought.
Our testsuite also does rsync migration and it's been similarly passing for me on Xenial.


added storm wiki frontend with extra themes

related issue
https://github.com/stanford-oval/storm/issues/64
changes

Dracula soft dark color and other light and dark themes
Duckduckgo search. and added searxng and SEARXNG_BASE_URL env var as a fallback option
using ollama and added gpt-4o-mini as a fallback option
save result files as '*.md'
add date to to top of the result file
added arize-phoenix to trace.

note
because this frontend is using "fallbacks", I thought it would be better to have separate example instead of overwriting the existing demo_light.
some tests files are added and checked with https://github.com/jaigouk/storm_wiki

There are 6 themes. 3 light themes and 3 dark themes.
we can add or adjust colors.

i guess we can refine this further to configure search and llm models.

list available search engines and add configuration options if there is api key for them in secrets. and we can also define which engine will be the fallback option.
same for the LLMs.

Previously meant to assign the team members as the reviewer, since this looks like a pretty good enhancement. Sorry for any confusion!

is it ok to reopen and fix some issues that people have?

Of course! Sorry for previous confusion.

Thanks! Feel free to at me once you think it's ready for review. We are happy to help merge this.


[Parse] Fix type parsing when preceded by '-'

It was mentioned post merge in this PR https://github.com/swiftlang/swift/pull/75518 that we accept parsing types as -Int now and these go undiagnosed. This patch fixes that to only parse - if it is preceded by an integer literal for integer type parsing. This also fixes an issue when same type constraining a type parameter to an integer type which previously would give diagnostics, for example,  about the type 1 not conforming to Copyable or Escapable which is a pretty poor diagnostic.

@swift-ci please test


Test system information

Firstly, WOW! Thank you for doing this!
One detail you skipped in your summary, which is absolutely key in evaluating the results, in the test system configuration. Number of cores is helpful, but some libraries are OS specific. If you could provide a detailed box about the system that would be hugely appreciated.

The followings are some snapshots from the results of MacBook Pro (Retina, 15-inch, Mid 2015<EMAIL_ADDRESS>with clang 7.0 64-bit.

The tests were ran on a Dell R710, 2x<EMAIL_ADDRESS>with 64Gb RAM on an Ubuntu Server 16.04.3.

Just a quick sentence for us to better understand you test vector =)
Thanks again for these results!

Hi @prince-chrismc
Thanks for your interest and valid point. I have updated the benchmark with system information.

Wonderful! Exactly what I needed!


[BUG] not opening

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.
[X] I have thoroughly looked through the available Wiki articles and could not find a solution to my problem.
[X] I am using the latest version of Bloxstrap.
[ ] I did not answer truthfully to all the above checkboxes.

What problem did you encounter?
idk its no opening can someone help me
Bloxstrap Log
N/A

we kinda need more information

Can you send your log file?

Is it Roblox or Bloxstrap that isn't opening?

Issue has stale for over a month, and will be reopened if further information is given.


Recognize CPU core count in FreeBSD

At the moment FreeBSD can't recognize the CPU count, however FreeBSD uses the same method as OS X does so provided PR fixes that.
If this could be included in the 1.2.0 release that would be great.

Can one of the admins verify this patch?

Jenkins, test this please

Makefile failure unrelated. Merging


Resolves #1618, preserve the markup if it's the last element

@Mogztter No, plugins are not tested (at least right now).

It seems like the current implementation of Keep Markup assumes that every tag contains at least one character, causing #1618.
This PR does handle the case of the last tag correctly but it handles some other case worse than the current implementation.

Order swapping:
The order of all zero-length tags which have the same start position will the reversed. E.g.:
<x></x><y></y> -> <y></y><x></x>
Tag inclusion:
Zero-length tags after a closing tag will be included into the preceding tag (in reversed order). E.g.:
<x>foo</x><y></y><z></z> -> <x>foo<z></z><y></y></x>

Tag inclusion is probably just a symtom of #1640.
Right now, this implementation does more harm than good, so we will have to address the above points before we can merge this.

OH! we really need tests :smile:
Can I submit a proposal to add unit tests on this plugin ? Otherwise it will be a nightmare to fix :neutral_face:

Of course, you can submit the proposal but it will require to implement a very different test suite than the one we have right now. So, no small task.

Otherwise it will be a nightmare to fix

I don't see why that is. A little hacky but I just made a little test page based on the index page of the plugin. Insert the markup to be tested and verify yourself. Not pretty but it works.

If we wanted to go all-out, something w/ JSDOM + snapshot tests could work. We have a (admittedly complex) mocha/chai setup for the current tests. Might be nice to get some tests going for the plugins.

If we wanted to go all-out, something w/ JSDOM + snapshot tests could work.

That's exactly what I had in mind :+1:
I've added a failing tests but I don't know how to solve this issue. To be honest I'm a bit lost with all the start/end position...

@Mogztter I really appreciate the enthusiasm and the contribution. I think if we're going to do this (introduce testing for plugins), we should break up this PR into one that introduces the framework and maybe some basic, passing tests, then a separate PR that adds tests for & fixes this bug. That'll allow us to evaluate each of those things separately.

I think if we're going to do this (introduce testing for plugins), we should break up this PR into one that introduces the framework and maybe some basic, passing tests, then a separate PR that adds tests for & fixes this bug.

@mAAdhaTTah Sure no worries.
My initial bugfix is a one-liner. I can revert this change and only add a test that check that the extension has been registered ? ie. Prism.hooks.all['before-highlight'] and Prism.hooks.all['after-highlight'] are not empty ? Does it sound good to you ?

@Mogztter I'd prefer to evaluate the bugfix in a separate PR. It's not clear to me this comment isn't a result of introducing that change. What I'd suggest is ending up with 2 PRs:

Introduce the testing infrastructure, including some basic tests for this plugin that pass, without changing any plugins. We can then start adding tests for the plugins as we go.
A PR that fixes this bug and introduces tests to cover the bugfix.

How you want to break that up (modifying this PR to be just tests, or closing and creating them separately) is up to you, but that's the place I'd like to end up if we want to add tests at this time.
The smaller the PR, the easier it will be to get each of them in, and I'd like to evaluate & think through the testing infrastructure as well as whatever tests you're introducing without also needing to evaluate the change(s) you're making to the plugin.
Does that make sense? My apologies for making this complex; I threw out the suggesting not expecting you to run with it so fast. And I appreciate it, but it does ramp up the overall complexity of what you're doing, and I just want to simplify it as much as possible.

@mAAdhaTTah Done, see https://github.com/PrismJS/prism/pull/1646

Let's get the tests in first, then we'll get this fix.

@mAAdhaTTah Rebased :+1:
@RunDevelopment You're right, I can reproduce the "order swapping" regression. With this fix the test "should preserve markup order" is failing :wink:

Hey, sorry for the delay on this, but coming back to this now. I see one code change, which I guess is fine? Does this change the commented out test? We should either delete it and replace it with a test that represents the intended behavior or update it.
That said, if this change removes that <a> tag in the test, that seems like a breaking change to me, and if the underlying issue is #1640, then I think this fix is invalid, unfortunately. We should probably tackle that problem holisitically.
I'm going to go ahead & close, but happy to reopen if anything above I've said it wrong.


No Animations when using @tanstack/router

Shadcn-ui elements do not animate when using @tanstack/router v1
To recreate

Clone the @tanstack/router basic example. I did this by opening the example with Stackblitz and downloading the code.

As written in the README.md run:

npm install npm start

Add an empty index.css file.

Follow steps 1 to 6 of the shadcn-ui vite installation guide.  The settings I used were:

Would you like to use TypeScript (recommended)? yes
Which style would you like to use? › Default
Which color would you like to use as base color? › Slate
Where is your global CSS file? › › src/index.css
Do you want to use CSS variables for colors? › no
Where is your tailwind.config.js located? › tailwind.config.js
Configure the import alias for components: › @/components
Configure the import alias for utils: › @/lib/utils
Are you using React Server Components? › no

Add the sheet component with

npx shadcn-ui@latest add sheet

Edit the main.tsx file to import and use the sheet component

import {
  Sheet,
  SheetContent,
  SheetDescription,
  SheetHeader,
  SheetTitle,
  SheetTrigger,
} from "@/components/ui/sheet"

function RootComponent() {
  return (

      <Sheet>
        <SheetTrigger>Open</SheetTrigger>
        <SheetContent>
          <SheetHeader>
            <SheetTitle>Are you sure absolutely sure?</SheetTitle>
            <SheetDescription>
              This action cannot be undone. This will permanently delete your account
              and remove your data from our servers.
            </SheetDescription>
          </SheetHeader>
        </SheetContent>
      </Sheet>

        <Link
          to="/"
          activeProps={{
            className: 'font-bold',
          }}
          activeOptions={{ exact: true }}
        >
          Home
        </Link>{' '}
        <Link
          to={'/posts'}
          activeProps={{
            className: 'font-bold',
          }}
        >
          Posts
        </Link>

      <Outlet />
      <TanStackRouterDevtools position="bottom-right" />

  )
}

Attempted Debug
When reverting to react-router all issues were resolved.
TailwindCss animations still work for example if you add animate-pulse to the parent div of rootComponent the elements pulse as expected.
Footnotes
p.s. Thank you for building shadcn/ui, it's brilliant.

Just FYI the issue was with tailwind. When importing with a script in main the animations failed. Reverting to a package manager import such as npm and removing the script import solved the issue.


Lowercase the method names

This would fit standard js naming conventions better:
CustomEvent.DISPATCH => dispatch
CustomEvent.ON => on
CustomEvent.OFF => off

Good point. Thanks
uppercase more readable for me :)

let's see what community think about that :)
https://twitter.com/shystrukk/status/1120765695959003136

changes in v.1.0


[BUG] Memory overflow on M1 MacBookAir when running snowpack dev

Bug Report Quick Checklist

[x] I am on the latest version of Snowpack & all plugins.
[x] I use package manager npm
[x] I run Snowpack on OS macOS 11.0.1 (M1)
[x] I run Snowpack on Node.js v12+ 14.15.4

Describe the bug
I was running snowpack dev for the first time in my project and got this output:

><EMAIL_ADDRESS>dev /Users/benc/code/benc.io
> snowpack dev

[17:23:58] [snowpack] Welcome to Snowpack! Because this is your first time running
this project, Snowpack needs to prepare your dependencies. This is a one-time step
and the results will be cached for the lifetime of your project. Please wait...

<--- Last few GCs --->

[23860:0x138008000]      100 ms: Scavenge 20.3 (27.4) -> 19.6 (29.2) MB, 0.5 / 0.0 ms  (average mu = 1.000, current mu = 1.000) allocation failure
[23860:0x138008000]      134 ms: Scavenge 25.8 (31.0) -> 24.1 (32.2) MB, 0.5 / 0.0 ms  (average mu = 1.000, current mu = 1.000) allocation failure
[23860:0x138008000]      141 ms: Scavenge 26.4 (32.2) -> 25.0 (34.0) MB, 0.7 / 0.0 ms  (average mu = 1.000, current mu = 1.000) allocation failure

<--- JS stacktrace --->

FATAL ERROR: wasm code commit Allocation failed - process out of memory
 1: 0x1020aa9d8 node::Abort() [/Users/benc/.nvm/versions/node/v14.15.4/bin/node]
 2: 0x1020aab58 node::errors::TryCatchScope::~TryCatchScope() [/Users/benc/.nvm/versions/node/v14.15.4/bin/node]
 3: 0x1021c4384 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/Users/benc/.nvm/versions/node/v14.15.4/bin/node]
 4: 0x1021c4318 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/Users/benc/.nvm/versions/node/v14.15.4/bin/node]
 5: 0x102759cdc v8::internal::wasm::WasmCodeAllocator::AllocateForCodeInRegion(v8::internal::wasm::NativeModule*, unsigned long, v8::base::AddressRegion, v8::internal::wasm::WasmCodeAllocator::OptionalLock const&) [/Users/benc/.nvm/versions/node/v14.15.4/bin/node]
 6: 0x10275a970 v8::internal::wasm::NativeModule::CreateEmptyJumpTableInRegion(int, v8::base::AddressRegion, v8::internal::wasm::WasmCodeAllocator::OptionalLock const&) [/Users/benc/.nvm/versions/node/v14.15.4/bin/node]
 7: 0x102759638 v8::internal::wasm::NativeModule::AddCodeSpace(v8::base::AddressRegion, v8::internal::wasm::WasmCodeAllocator::OptionalLock const&) [/Users/benc/.nvm/versions/node/v14.15.4/bin/node]
 8: 0x10275a780 v8::internal::wasm::NativeModule::NativeModule(v8::internal::wasm::WasmEngine*, v8::internal::wasm::WasmFeatures const&, v8::internal::VirtualMemory, std::__1::shared_ptr<v8::internal::wasm::WasmModule const>, std::__1::shared_ptr<v8::internal::Counters>, std::__1::shared_ptr<v8::internal::wasm::NativeModule>*) [/Users/benc/.nvm/versions/node/v14.15.4/bin/node]
 9: 0x10275ccf4 v8::internal::wasm::WasmCodeManager::NewNativeModule(v8::internal::wasm::WasmEngine*, v8::internal::Isolate*, v8::internal::wasm::WasmFeatures const&, unsigned long, std::__1::shared_ptr<v8::internal::wasm::WasmModule const>) [/Users/benc/.nvm/versions/node/v14.15.4/bin/node]
10: 0x102768808 v8::internal::wasm::WasmEngine::NewNativeModule(v8::internal::Isolate*, v8::internal::wasm::WasmFeatures const&, std::__1::shared_ptr<v8::internal::wasm::WasmModule const>, unsigned long) [/Users/benc/.nvm/versions/node/v14.15.4/bin/node]
11: 0x102737b54 v8::internal::wasm::AsyncCompileJob::CreateNativeModule(std::__1::shared_ptr<v8::internal::wasm::WasmModule const>, unsigned long) [/Users/benc/.nvm/versions/node/v14.15.4/bin/node]
12: 0x102737d1c v8::internal::wasm::AsyncCompileJob::GetOrCreateNativeModule(std::__1::shared_ptr<v8::internal::wasm::WasmModule const>, unsigned long) [/Users/benc/.nvm/versions/node/v14.15.4/bin/node]
13: 0x102740380 v8::internal::wasm::AsyncCompileJob::PrepareAndStartCompile::RunInForeground(v8::internal::wasm::AsyncCompileJob*) [/Users/benc/.nvm/versions/node/v14.15.4/bin/node]
14: 0x10274014c v8::internal::wasm::AsyncCompileJob::CompileTask::RunInternal() [/Users/benc/.nvm/versions/node/v14.15.4/bin/node]
15: 0x102107c08 node::PerIsolatePlatformData::RunForegroundTask(std::__1::unique_ptr<v8::Task, std::__1::default_delete<v8::Task> >) [/Users/benc/.nvm/versions/node/v14.15.4/bin/node]
16: 0x1021068a0 node::PerIsolatePlatformData::FlushForegroundTasksInternal() [/Users/benc/.nvm/versions/node/v14.15.4/bin/node]
17: 0x1028bdc20 uv__async_io [/Users/benc/.nvm/versions/node/v14.15.4/bin/node]
18: 0x1028cf7e0 uv__io_poll [/Users/benc/.nvm/versions/node/v14.15.4/bin/node]
19: 0x1028be0b0 uv_run [/Users/benc/.nvm/versions/node/v14.15.4/bin/node]
20: 0x1020e2f40 node::NodeMainInstance::Run() [/Users/benc/.nvm/versions/node/v14.15.4/bin/node]
21: 0x1020837d0 node::Start(int, char**) [/Users/benc/.nvm/versions/node/v14.15.4/bin/node]
22: 0x18ce8cf54 start [/usr/lib/system/libdyld.dylib]
[1]    23859 abort      npm run dev

To Reproduce
(you might have to be on an M1 mac to reproduce this)

git clone https://github.com/bencooper222/benc.io.git
git checkout snowpack
nvm use
Verify that node -e "console.log(process.arch)" prints out arm64
npm i
npm run dev

Expected behavior
To not memory overflow.
Anything else?
Could try increasing the memory given to Node? I don't know what Snowpack defaults to: https://support.circleci.com/hc/en-us/articles/360009208393-How-can-I-increase-the-max-memory-for-Node-

Try running node using the x64 architecture. Details are in the Macs with M1 chip section here:
https://github.com/nvm-sh/nvm#macos-troubleshooting

Wow, I didn't know about that issue with the M1 chip.
Can you try running with the --verbose flag to see where it's getting stuck?

Closing because I don't think that this is actionable on our end. If you haven't used mount config yet, that can help cut down on the number of files being handled, which may be where your issue is coming from.

Yeah sounds like we’re all just waiting for the Node project’s maddeningly long timelines.

Yeah sounds like we’re all just waiting for the Node project’s maddeningly long timelines.

@bencooper222 Curious to know... did that solution work? ie, running node with the x64 architecture.

It did! I ran node through volta.sh not nvm but volta did the x64 stuff.


fix #257 and add optional domain handling

Fix

#257 should be fixed by checking username and password for non empty values

Add

Optional configurations for domain handling

 'ldap_userFieldMapping'=> [
...
       'username_AddDomain'<EMAIL_ADDRESS>       'username_RemoveDomains'<EMAIL_ADDRESS><EMAIL_ADDRESS>
...

username_RemoveDomains are removed from the username, so an user can login either with
username<EMAIL_ADDRESS>or<EMAIL_ADDRESS>username_AddDomain is the quite the opposite. It enforces to use the configured domain and adds it on the login-username and the ldap-usernames (if missing). That's useful if you use mailaddresses as usernames and are facing user request like 'our domain is soo long, do I really have to type it too?'

Codecov Report

Merging #258 (ea2e3dc) into master (006c953) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #258   +/-   ##
=========================================
  Coverage     99.89%   99.89%
  Complexity      368      368
=========================================
  Files            25       25
  Lines           944      944
=========================================
  Hits            943      943
  Misses            1        1

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 006c953...ea2e3dc. Read the comment docs.


Push buildpack from github using commit id

Command
cf push buildpack-hash -b https://github.com/cloudfoundry/java-buildpack.git#96dac92cbcbd365d81959d9130de2f97cb688093

What occurred
2017-11-16T15:21:12.61+0200 [STG/0] ERR Failed to clone git repository at https://github.com/cloudfoundry/java-buildpack.git
What you expected to occur
In the past this way of pulling buildpack using a specific commit id used to work. See: https://github.com/cloudfoundry/cli/issues/215#issuecomment-62853478
Is it intentional that it doesn't work anymore?
CLI Version
cf version 6.26.0+9c9a261.2017-04-06
CC API Endpoint Version
2.98.0
Platform & Shell Details
Windows 8.1 cmd.exe

Ah interesting!
@sclevine and I were looking at that a few months ago, found that it didn't work, had the impression it could have never worked, and removed the related article on docs.cloudfoundry.org about it.
The CLI just passes the specified value to the backend, so nothing changed on the CLI side.
The backend, in a component that I believe is now maintained by the Buildpacks team, simply invokes git clone -b command to check out the right branch, and doesn't support commit sha's.
@emalm I believe Diego owned this code before Buildpacks. Do you remember anything about this?

@dkoper Looks like Diego did work to support custom git buildpacks in https://www.pivotaltracker.com/story/show/76320826, and was intended to match the functionality in the DEAs (presumably from https://github.com/cloudfoundry-attic/dea_ng/pull/90/files). I don't see any discussion on either side of intentionally supported cloning from a particular commit SHA, just branch heads and tags.

@emalm It was on docs.cloudfoundry.org, which I recently removed after a discussion with Stephen.

Yeah, but that functionality isn't covered in any of the tests in those code bases.

I believe this was erroneously added to the docs here:
https://github.com/cloudfoundry/docs-buildpacks/commit/16906e1d3fa804e14212d4ff610bcf60b05af6a7
We have never supported specifying a commit SHA, to the best of my knowledge.

@aminjam I hope that answer your question?

Thanks for the answers.


Conditionally list child objects

Add an option that allows the listing of child objects in a parent (e.g. notes in a notebook).
Read the option from the environment and turn it off by default.
This will:

improve performance by eliminating a database query per child relation
simplify the output

Option name: SHOW_CHILD_OBJECTS

Fixed by 6e8ef666f1b016d05aeb042690cb30c347a38cd4


Firewall-faq typo

'How to wildcards work' should be 'How do wildcards work'.

@remcoeissing : Thanks for your contribution! The author, @vhorne, has been notified to review your proposed change.

Verified editorial corrections.


[chore] Add grpc instrumentation e2e test

Add e2e test for grpc instrumentation.

Close #85

I've tested the app runs and calls the grpc server. Do we know for sure grpc instrumentation is working?

I've tested the app runs and calls the grpc server. Do we know for sure grpc instrumentation is working?

No, we don't 😄  Check out #78 . That was the main drive behind wanting a test on this sooner than later. Did you create the traces.json part of the test from scratch based on the others?

Looks like the sample job is timing out in the CI failure: https://github.com/open-telemetry/opentelemetry-go-instrumentation/actions/runs/4811053910/jobs/8564536923?pr=106#step:15:5
Checking out your branch and running make fixture-grpc on my machine, the Pod logs appear to have the same error that @JamieDanielson pointed out in #78:
$ kubectl logs pod/sample-job-4prmc -c auto-instrumentation
...
{"level":"error","ts":1682607535.4222052,"caller":"instrumentors/runner.go:86","msg":"error while loading instrumentors, cleaning up","name":"google.golang.org/grpc","error":"field UprobeHttp2ClientCreateHeaderFields: program uprobe_Http2Client_CreateHeaderFields: load program: permission denied: ;: 977: (07) r6 += -384 (truncated, 1060 line(s) omitted)","stacktrace":"go.opentelemetry.io/auto/pkg/instrumentors.(*instrumentorsManager).load\n\t/app/pkg/instrumentors/runner.go:86\ngo.opentelemetry.io/auto/pkg/instrumentors.(*instrumentorsManager).Run\n\t/app/pkg/instrumentors/runner.go:34\nmain.main\n\t/app/cli/main.go:86\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:250"}
{"level":"info","ts":1682607535.4222748,"caller":"grpc/probe.go:228","msg":"closing gRPC instrumentor"}
{"level":"error","ts":1682607535.4222934,"caller":"cli/main.go:88","msg":"error while running instrumentors","error":"field UprobeHttp2ClientCreateHeaderFields: program uprobe_Http2Client_CreateHeaderFields: load program: permission denied: ;: 977: (07) r6 += -384 (truncated, 1060 line(s) omitted)","stacktrace":"main.main\n\t/app/cli/main.go:88\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:250"}

Also blocked by:

#135

Going to wait for #150 as it resolves part of the issue I was working through. The content of the traces json still has some fixes that we'll need to resolve.


simple command line interface

I am adding a simple CLI interface to make things a bit more friendly..
This is a draft of something quiqly not trying to overstep the design phase of the CLI interface.

Added Cobra root command calling the translation pkg.
Added output-format -o flag.
Skipping viper/configuration setting for now.

Run go run cmd/demo-ingest/*go -h
Translate SBOM formats

Usage:
  protobom [TARGET] [flags]

Examples:
  protobom [sbom-path] [flags]

	protobom [sbom-path] -o cyclonedx output a cyclonedx sbom
	protobom [sbom-path] -o spdx output a spdx sbom

Flags:
  -h, --help                   help for protobom
  -o, --output-format string   Select output format, [[text/spdx+text;version=2.3 text/spdx+json;version=2.3 text/spdx+text;version=2.2 text/spdx+json;version=2.2 application/vnd.cyclonedx+json;version=1.4 application/vnd.cyclonedx+json;version=1.5]] (default "application/vnd.cyclonedx+json;version=1.4")
  -v, --version                version for protobom

It needs a bit more work to get the format string more suitable to humans , sadly i am out of time today , continue tomarrow.

Nice @houdini91 !
This proves that. as the project matures, we need a stronger debugger tool, I have two comments, one is a simple typo but the other one is more important: let's be careful on what we export from this module.

What do you mean debugger tool, like a sbom viewer?
I was thinking about how to bootstrap unittest and integration tests but i think i better start with writing up a suggestion issue for our CLI structure (user interface, build, test, release) so that we can discuss the details on it

Once you expose an API publicly, people will start using it and then it's hard to roll back. So let's start by hiding as much as we can.
As these are the internals to power a demo app, can we make this package private? Move it internal/pkg so that it cannot be imported outside of the modeule.

Can you clarify if your talking about the Translate func or Application Config structure or both?
I agree with you we should expose the minimum required to use the library.
I am ok with moving everything to an internal sub-directory but i just write down why i chose to expose this.
I think the highest level function used by our command is valuable for library users.
I also find it easier to explain the library when the command and library expose some reflection of each other.
import "github.com/bom-squad/protobom/pkg"

func main() {
  cfg := pkg.Application{}
  pkg.Translate(target, cfg)
}

FYI:
What i normally do is something weird like have the Application struct under internal/config/application.go and then in the pkg/command.go.
package pkg

type Application = internal.Application

Translate(cfg *Application)

What do you mean debugger tool, like a sbom viewer?

No, not really, just a binary that let's us test everything without being the actual CLI we are building. Especially while we scaffold all the tests.

I was thinking about how to bootstrap unittest and integration tests but i think i better start with writing up a suggestion issue for our CLI structure (user interface, build, test, release) so that we can discuss the details on it

Sounds good, it is a great idea to start working on. We should get a design doc/issue/etc going for the CLI tool to start thinking about how to expose the translation to the users.

Can you clarify if your talking about the Translate func or Application Config structure or both?

I was talking about hiding all that's in pkg/application.go. Since this tiniy app is just a test binary (probably bound to be removed in the future altogether) we should hide it completely.

I fixed the comments.

Move application to internal subdir.
Fixed typo

I also added some basic flags for humans but i was not sure if i am breaking @puerco vision of options based flags so put it in a seperate PR in my fork take a look and ping me if its ok to merge in to this PR as well or leave comments on it.
https://github.com/scribe-security/protobom/pull/1
Basically the new interface is something like
key@mikey-Latitude-5520:~/scribe/DHS/protobom$ go run cmd/demo-ingest/*go examples/vt.spdx.json -f cyclonedx -v 1.3
Translate SBOM formats such as cyclonedx and spdx

Usage:
  protobom [TARGET] [flags]

Examples:
  protobom [sbom-path] [flags]

	protobom [sbom-path] -o cyclonedx output a cyclonedx sbom
	protobom [sbom-path] -o spdx output a spdx sbom

Flags:
  -h, --help                        help for protobom
  -f, --output-format string        Select output format type, [cyclonedx spdx] (default "cyclonedx")
  -m, --output-mime-format string   Select mime format, [json xml] (default "json")
  -v, --output-version string       Select version, map[cyclonedx:[1.3 1.4 1.5] spdx:[2.2 2.3]] (default "1.4")
      --version                     version for protobom

I think this is what we need to start testing! My only request would be to just fold the CLI details into internal/ (as mentioned here)  to no export them and let's merge it :rocket:

@puerco Ok, i moved the application.go to internal.
Basica command
eitan@eitan:~/scribe/DHS/protobom$ go run cmd/demo-ingest/*go -h
Translate SBOM formats such as CycloneDX and SPDX

Usage:
  protobom [sbom] [flags]

Examples:
  protobom [sbom] -f cyclonedx                   output CycloneDX
  protobom [sbom] -f cyclonedx -v 1.3            output CycloneDX version 1.3
  protobom [sbom] -f spdx                        output SPDX
  protobom [sbom] -f spdx -v 2.3                 output SPDX SBOM version 2.3
  protobom [sbom] -f spdx -e xml                 output XML encoded SPDX

Flags:
  -e, --encoding string   Select encoding, Options=[json xml] (default "json")
  -f, --format string     Select format, Options=[cyclonedx spdx] (default "cyclonedx")
  -h, --help              help for protobom
  -v, --version string    Select version, Options=map[cyclonedx:[1.3 1.4 1.5] spdx:[2.2 2.3]] (default "1.4")

Ah I see.. but IIUC this is just a test binary right? It is not supposed to be the final CLI binary. Or am I understanding it wrong? Tha's why I want to make it non importable.

I was thinking that the real CLI will be built ontop the POC but i think we need to sync on some details such as where is the proto/specific generated libraries/CLI hosted in relation to each other (not sure how this is normally done for protobuf based project? monorepo?)
I am totally ok with hiding everything for now, its easier to expose new interface in a library later in the process than hide a existing one.

I think it is fine if we build a cli here in any dir (under another directory under cmd/ or whatever) and its libs hidden under /internal. If it becomes something useful we can relocate it, if not we can use it as the foundation of a new design. My goal is to start using your CLI, it's looking awesome :)

@puerco Moved root.go to cmd/cli .
What about the changes to formats.go such as FormatOpt and the command line arguments lists, should we have something like internal/cli/options.go or something similar?

@puerco Ping me if there anything missing from this PR


Excuse me, how does this code work on the voc dataset?

https://github.com/open-mmlab/mmdetection/tree/master/configs/pascal_voc


Synology DS Audio Player

Im not sure this is even possible but player support for synologys ds audio player would be awesome.

#174 #97 #2
Triplicate :)
I going to try and work on it.

Thank you for trying to make this work, good luck!

You are welcome !!! :)
@brogalski
but please continue discussion in #2.
Thank you.


Fix some typos

This PR is fix some typos.

assigment -> assignment
offensewhen -> offense when
interpoloation -> interpolation
someghing -> something
nodein -> node in

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[-] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[-] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[-] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.
[-] If this is a new cop, consider making a corresponding update to the Rails Style Guide.

already created a PR on codespell.
https://github.com/codespell-project/codespell/pull/2701

[memo] keeping what we are dealing with https://github.com/rubocop/rubocop-rails/pull/904


[Question]: i am trying to call _storeAttendance(action);  based on distance but however the distance is wrong even though the location is same

Please check the following before submitting a new issue.

[X] I have searched the existing issues.
[X] I have carefully read the documentation.

Please select for which platform(s) you need help

[X] Android
[ ] iOS
[ ] Linux
[ ] macOS
[ ] Web
[ ] Windows

Your question
  Future<void> getCurrentPos(String action) async {
    currentPos = await Geolocator.getCurrentPosition(
        desiredAccuracy: LocationAccuracy.medium);
    print("latitude: ${currentPos.latitude} , target latitude : ${targetLatitude}");
    print("longitude: ${currentPos.longitude}, target longitude  : ${targetLongitude}");

    double distance = Geolocator.distanceBetween(
      currentPos.latitude,
      currentPos.longitude,
      targetLatitude,
      targetLongitude,
    );
    print("the distance is ${distance}");

    if (distance <= 100) {
      await _storeAttendance(action);
    } else {
      _showResultDialog("Failed", "You are not within the required distance to check in/out.");
    }
  }

here is the console prints :
I/flutter (13227): latitude: 20.9931481 , target latitude : 20.9911605
I/flutter (13227): longitude: 75.5525976, target longitude  : 75.5515482
I/flutter (13227): the distance is<PHONE_NUMBER>217311
Version
12.0.0

I am experiencing the same issue. There is even a significant difference in the distanceBetween values between Android and iOS devices. On Android, the distance is reported as 18 meters, while on iOS, it is reported as 47 meters.

Dear @devlprRohit,
I can't see that your current location and target location are the same. Furthermore, please give some more context about the issue. How do you know that the distance is wrong?  Have you tried playing around with this and did you find different answers?
Dear @eunseoDev,
I appreciate your effort, but your issue seems like a different issue. based on your input I cannot help you. Please file a separate issue with clear steps to reproduce. The plugin uses the different api's of iOs and Android I can expect that there is a difference in accuracies.
Kind regards,


Update Customer Points

Commit: Added update customer points. #86
Cosumed time: 1 hour.
Lines of code by file:

CustomerPointsPersistence.java -------------- 2 lines of code
CustomerPointsService.java ------------------ 8 lines of code
CustomerPointsEntity.java -------------------- 4 lines of code
CustomerPointsPersistenceMongodb.java--- 8 lines of code
CustomerPointsPersistenceMongodbIT.java- 52 lines of code

---- Total lines of code: 74 lines of code ----


Bug Fixed in UI of Contact us section

Pull Request
Proposed Changes

Changed font color of labels and, wrapped the form under container, fixed layout in mobile screen and added box shadow like cards :)
Fixes #150
Live Link

Types of changes made

[ ] Fixed Bug
[ ] Added new Features
[ ] Edited Documentations
[ ] Enhanced the working of code
[ ] Additional Changes
Mention any Additional Change here

Additional Info
Provide additional information(if any) you want to convey.
Viability of Code
Describe the tests that you ran to verify the changes made. Mention the tests for easy reproducibility.

Test 1
Test 2

Mention(if any) specific Test Configurations used:

Filmware version:
Hardware:
Toolchain:
SDK:

Screenshots or GIFs (if any)
Attach screenshots of the changes made for easy reference.

Original
Updated

Attach_Original_Screenshot
Attach_Updated_Screenshot

Checklist:

[ ] My code follows the Mentioned Guidelines for the project
[ ] I have self-reviewed the changes made
[ ] I have made the changes easy to understand by adding comments
[ ] My changes does not generate new warnings/errors
[ ] I have attached relevant screenshots to display the changes made
[ ] I have made the required changes to the documentations

Cool :)


Push fails because of random route length

Command
cf push the-over-40-character-very-long-app-name --random-route
What occurred
In https://github.com/cloudfoundry/cloud_controller_ng/issues/581 a limited length of the app-name was introduced.
Our app-name has 43 characters. The app uses the random-route feature.
In this way the route can become longer than the limit of 63 characters.
This results in
Server error, status code: 400, error code: 210001, message: The route is invalid: host must be no more than 63 characters
What you expected to occur
CF push must be reproducible.
Possible fix
a) Use shorter suffix names in case of longer app-names.
b) Define a max-length for app-names, so they don't conflict with random-routes. (Didn't see documentation which defines the max-length of the suffix).
CLI Version
6.34.1+bbdf81482.2018-01-17
CC API Endpoint Version
2.102.0
Platform & Shell Details
Linux (Bash)
Any other relevant information
Original issue https://github.com/cloudfoundry/cloud_controller_ng/issues/1098

Hi, @elgohr . Can you give me more background on why you want app names over 40 characters plus a random route? Why would shortening app names not work?

We have many Java apps. In this way developers tend to be super expressive (at least there are no factories ;-)).
We're using random routes because we also have a service registry and don't need a fixed one.
It would totally work. What's the max length of the suffix? How short do they have to be?

@elgohr According to my math, the longest app name is 34 characters, assuming:

a max combined hostname length of 63 characters for app name and random route
random route value 1 is up to 12 characters ("appreciative")
random route value 2 is up to 14 characters ("tasmaniandevil")
2 dashes (between app and rr value 1 plus rr value 1 and value 2)

@jbpivotal if this is known, it would be good to check it in the client, before pushing.

I mean today the longest values are 12 and 14. As a user I would not like to check every value in this list on every update.
Furthermore the length is not constantly 12 and 14. In this way the push might work sometimes, sometimes it doesn't.

Ping

Hey @elgohr thanks again for reaching out and thanks for the ping - apologies it's taken so long to respond. We don't have current plans to prioritise this work in the near future - wondered if you've found a suitable workaround with the information provided to you above.

Hi @abbyachau , the solution was: don't use it and do it yourself

Hey @elgohr sorry we didn't provide a solution but great to hear you were able to provide one internally. We can leave this issue open to see if it garners any other reactions but unfortunately we are unlikely able to prioritise the work in the near future. Here is a comment to give you information on our current priorities.

Hi @elgohr thanks again for creating this issue. Please see the link issue #1360 above. We've received community feedback that there is increasing name collision whilst pushing with --random-route and will likely be moving forward with a fix,  to extend the random name that we generate. As mentioned in the issue, we are also looking at a more future-proof solution. We wanted to give you a heads up about related but separate issues in case it affects your workflows. Please reach out if you have any questions.

Hi again @elgohr, we decided to go with a different solution for #1360, one where we just changed the app name instead of adding an additional word to --random-route.
However, given our current workload, we don't have any immediate plans to delve into your use case. It sounds like you have a workaround so I'm going to close this issue. Please do not hesitate to get in touch if you have any questions/feedback.

Sorry, I don't get why bugs go away with workarounds. It's called workaround, not fix

Hi @elgohr sorry we couldn't help here, it's more of a priority issue - we unfortunately have a fairly large workload and so cannot help even where we would like to. Please do not hesitate to reach out to us again though. Best.


Not working with custom interpolateProvider configuration

error: Controller 'ngModel', required by directive 'uiSelectSingle', can't be found!
with config: $interpolateProvider.startSymbol('[[').endSymbol(']]');
code: <ui-select>                             <ui-select-choices repeat="company in companies" ng-model="company.data">                                 [[ company.comp_name ]]                             </ui-select-choices>                         </ui-select>

ng-model should be on ui-select not ui-select-choices.
Closing.


Optimize the simple iptables wrapper to go-xtables.

The inner pkg nf_wrapper should be obsoleted, and it can be replaced by go-xtables.

Refactoring agenda:

replacement on nf_wrapper.
nftables for linux 4.18


sega

hi i open
segaplatformer\SGDK_PlatformerStudio-main\SGDK_PlatformerStudio-main\StudioType\SGDK\Engines\platformer\build\res
but it shuts automatically. do i need godot to run this too? also is it possible to export to c64 from godot? thanks

Hello. You don't need to download Godot, just use compiled one from this link. Also, you need to install SGDK (because this tool, is just code generator for SGDK project), and BlastEm. It's not possible to export to c64.

ahh ook that opens but i have no idea where to start! is there a sample game i can load to see? its a shmup engine as well as platformer? thanks.

I have a sample  platformer, and yes, it's possible make shump, but, all shumps have a large map, and without chunk entity load optimization, fps will suffer. Right now, chunk optimization working, but with some problems. And, i recommend to wait for new version of studio a day or so, because in new version i modified physics engine, and joystick logic. Since, you will modify joystick logic 100%, for your needs.

Ok, it's done, new version is available.

great will find time to look at videos. as for set up i put blastem in folder but it doesnt open when building maybe my path is wrong?

great will find time to look at videos. as for set up i put blastem in folder but it doesnt open when building maybe my path is wrong?

You need put BlastEm in Emulators/BlastEm folder, because studio looking for file Emulators/BlastEm/blastem.exe

hi i put it here (but i messed up somehow)

 hi i put it here (but i messed up somehow)

You need to put BlastEm files in Emulators/BlastEm directory

Probably, you got a compilation error, try to make a new project in studio.

here is animated gif of whats happening in new project thanks

Your SGDK is installed correctly, try to compile some projects in SGDK/sampe folder.

didnt work but i see you have 1.8 i wiill try the update soon


Data splitting of MTAT dataset

Hi, thank you for your great work and for building benchmark results for all the representative auto-tagging models. I have a further question on the data splitting of the MTAT dataset.
In the SMC paper, you mentioned that you did not discard the tracks with no associate labels (which might lead to performance decay). However, both the split npy files in this repo and also the split files in this repo you referred to in the SMC paper discard those tracks away. Could I kindly ask whether the results are based on the cleaned version of the dataset which discard those tracks?
For your reference, the original version should have 18706 tracks for training, 1825 for validation, and 5329 for testing (25860 in total). The clean version should have 15247 for training, 1529 for validation, and 4332 for testing (21108 in total).

Hi,
If I remember correctly, the results on the table are using the cleaned version (21k clips in total). Due to the data spli discrepancy described in the paper, we reproduced all the results using this new split.


Pigeon: support builtin types as arguments and return values

Right now you can't say:
@HostApi
abstract class Foo {
  int getValue(int identifier);
}

You have to say:
class Output {
  int value;
}

class Input {
  int identifier;
}

@HostApi
abstract class Foo {
  Output getValue(Input input);
}

It would be convenient and less wasteful if builtin types could be used directly.

seo: primitives


Only one Dialer receives messages from STAR pattern

When running the code below, the only output is the following:
2016/10/12 02:23:40 READY
2016/10/12 02:23:40 [ S1 ] HELLO WORLD

Based on the documentation, which states that

that the messages are delivered not just to immediate peers, but to all members of the topology

I expected something like following output:
2016/10/12 02:23:40 READY
2016/10/12 02:23:40 [ S2 ] HELLO WORLD
2016/10/12 02:23:40 [ S1 ] HELLO WORLD

What am I doing incorrectly?  Is this a bug?
package main

import (
	"log"
	"time"

	"github.com/go-mangos/mangos"
	"github.com/go-mangos/mangos/protocol/star"
	"github.com/go-mangos/mangos/transport/inproc"
)

var (
	err            error
	master, s1, s2 mangos.Socket
)

func init() {
	if master, err = star.NewSocket(); err != nil {
		log.Fatal(err)
	}

	if s1, err = star.NewSocket(); err != nil {
		log.Fatal(err)
	}

	if s2, err = star.NewSocket(); err != nil {
		log.Fatal(err)
	}

	master.AddTransport(inproc.NewTransport())
	s1.AddTransport(inproc.NewTransport())
	s2.AddTransport(inproc.NewTransport())

	if err = master.Listen("inproc:///"); err != nil {
		log.Fatalf("error in listening (master): %s", err)
	}

	if err = s1.Dial("inproc:///"); err != nil {
		log.Fatal(err)
	}

	if err = s2.Dial("inproc:///"); err != nil {
		log.Fatal(err)
	}

	log.Println("READY")
}

func main() {
	if err = master.Send([]byte("HELLO WORLD")); err != nil {
		log.Fatal(err)
	}

	go func() {
		for {
			msg, e := s1.Recv()
			if e != nil {
				log.Printf("[ ERR S1] %s", err)
			} else {
				log.Printf("[ S1 ] %s", string(msg))
			}
		}
	}()

	go func() {
		for {
			msg, e := s2.Recv()
			if e != nil {
				log.Printf("[ ERR S1] %s", err)
			} else {
				log.Printf("[ S2 ] %s", string(msg))
			}
		}
	}()

	<-time.After(15 * time.Second)
}

Many thanks in advance!

looks like a bug indeed.  stay tuned.  (does tcp suffer the same problem?)
Sent from my iPhone

On Oct 11, 2016, at 5:28 PM, Louis Thibault<EMAIL_ADDRESS>wrote:
When running the code below, the only output is the following:
2016/10/12 02:23:40 READY
2016/10/12 02:23:40 [ S1 ] HELLO WORLD
Based on the documentation, which states that
that the messages are delivered not just to immediate peers, but to all members of the topology
I expected something like following output:
2016/10/12 02:23:40 READY
2016/10/12 02:23:40 [ S2 ] HELLO WORLD
2016/10/12 02:23:40 [ S1 ] HELLO WORLD
What am I doing incorrectly? Is this a bug?
package main
import (
"log"
"time"
"github.com/go-mangos/mangos"
"github.com/go-mangos/mangos/protocol/star"
"github.com/go-mangos/mangos/transport/inproc"

)
var (
err            error
master, s1, s2 mangos.Socket
)
func init() {
if master, err = star.NewSocket(); err != nil {
log.Fatal(err)
}
if s1, err = star.NewSocket(); err != nil {
    log.Fatal(err)
}

if s2, err = star.NewSocket(); err != nil {
    log.Fatal(err)
}

master.AddTransport(inproc.NewTransport())
s1.AddTransport(inproc.NewTransport())
s2.AddTransport(inproc.NewTransport())

if err = master.Listen("inproc:///"); err != nil {
    log.Fatalf("error in listening (master): %s", err)
}

if err = s1.Dial("inproc:///"); err != nil {
    log.Fatal(err)
}

if err = s2.Dial("inproc:///"); err != nil {
    log.Fatal(err)
}

log.Println("READY")

}
func main() {
if err = master.Send([]byte("HELLO WORLD")); err != nil {
log.Fatal(err)
}
go func() {
    for {
        msg, e := s1.Recv()
        if e != nil {
            log.Printf("[ ERR S1] %s", err)
        } else {
            log.Printf("[ S1 ] %s", string(msg))
        }
    }
}()

go func() {
    for {
        msg, e := s2.Recv()
        if e != nil {
            log.Printf("[ ERR S1] %s", err)
        } else {
            log.Printf("[ S2 ] %s", string(msg))
        }
    }
}()

<-time.After(15 * time.Second)

}
Many thanks in advance!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I will check tcp ASAP.  In the meantime, I get similar behaviour with the bus protocol.

A few updates:
Firstly the bug appears to be stochastic in nature.
Third, when using TCP (for both STAR and BUS), the only behaviour I observe is no output.
For the purposes of sanity-check, I defined my TCP sockets as follows:
    if err = master.Listen("tcp://localhost:9000"); err != nil {
        log.Fatalf("error in listening (master): %s", err)
    }

    if err = s1.Dial("tcp://localhost:9000"); err != nil {
        log.Fatal(err)
    }

    if err = s2.Dial("tcp://localhost:9000"); err != nil {
        log.Fatal(err)
    }

Any ideas?
Louis

Ok, I've looked at this, and the problem is that Dial() is occurring asynchronously (by design), so you can have a situation where you wind up calling Send() before the Dial() completes.  Whether this happens or not is entirely dependent on the scheduler, and can change.
In order to solve this problem, you need to not assume that Dial() returning indicates that a connection is established.  (Underlying connections can come and go... Dial just sets up the "logical" connection.)
As a workaround, you can try adding a time.Sleep(time.Second) (or some smaller increment) at the start of main().  (Because init() runs immediately before main().)  If I do that, then your example completes  successfully every time.

Thanks for the detective work!  Should I make this same assumption for all sockets, regardless of protocol?  Are all protocols "best-effort" or do some (most?) have stronger guarantees?
Thanks again!

Yes.  With the exception of Req/Rep, which has an implied retry.  (Though it can take it a while before it decides to retry your message.)


Updated README with new installation from sources. [5995]

This PR adds changes to the readme file, hence no need to wait for the tests to pass.


Question - any plans for address extraction?

Are there any plans to implement address extraction. Say extracting an array of addresses from a large body of text?

Excellent question. It's something I've thought a bit about, though it's not on the short-term roadmap. It would be great to have an open source version of what your phone does (extracting addresses from emails, etc. though I believe most of those implementations are regex-based and hence somewhat limited, probably more than a little US-biased).
The NLP approach would be to treat it as an entity recognition problem and get/generate some labeled sentences, e.g.
We/O are/O located/O at/O 123/I Main/I Street/I ./O

This is using simple I/O encoding (each token is labeled "I" for "inside" an address or "O" for "outside" the address). The current address parser is trained on something similar, although in the parsing case every token is known to be part of an address and our model needs to figure out whether it's part of a street name vs. a country vs. a suburb, etc.
I personally don't know of any such "address entity recognition" data set (if you do, please share!) but have a hunch that one could be constructed. One way to accomplish this would be to insert known addresses into, say, Wikipedia articles that link to venues. Replace the venue link with its address, and it's likely you'll start to see patterns of locatives e.g. "at", "by", etc. which tend to precede mentions of places. Since it's Wikipedia, this could be replicated in basically every language (which we like in libpostal). A structured learning model similar to the one we have for the current address parser could be trained using almost the exact same code, just different labels.
If you know of/are using any data sets that might be useful for this task, or if I'm missing some elephant in the proverbial room, let me know.

I would really love to see this feature :+1:

Me too! Has there been any news on this?

This is my primary use case with this library and I would love to see it implemented.

datamade/usaddress uses parserator to kind of do this. It can parse the string "yeah I live at 1200 valley lane st I think"

@SephVelut not exactly. If you're willing to provide your own training data and write your own feature extraction, sure, parserator (or CRFSuite, on which parserator is based, or any other sequence modeling library/toolkit) can be trained to extract addresses from strings, but to be clear for others reading this in the future, that is not at all what usaddress does at the time of this writing.
Here the actual usaddress parse for that string:
[(u'yeah', 'Recipient'),
 (u'I', 'Recipient'),
 (u'live', 'Recipient'),
 (u'at', 'Recipient'),
 (u'1200', 'AddressNumber'),
 (u'valley', 'StreetName'),
 (u'lane', 'StreetNamePostType'),
 (u'st', 'PlaceName'),
 (u'I', 'PlaceName'),
 (u'think', 'PlaceName')]

i.e. it is only able to return the labels on which it was trained. That's fine in the geocoder use case or when trying to separate a combined address field in a database/CSV because all of the text is known to be part of an address and must be labeled one component or the other, but doesn't work for web scraping, bots, etc.
What was being discussed here is a model that is specifically trained to label each word in a sentence with "is this word part of an address or not?" as shown above. Libpostal already has a decent model for the "in" text, but modeling the "out" text (non-address words and more importantly, how they transition into addresses in real text) in a principled way is quite an undertaking, especially implementing it at libpostal's scale with high accuracy in multiple languages such that it could be used on arbitrary websites.
It's possible, and I've posited some ways to do it above, so if an NLP researcher wants to take that on, that's great, but as far as me implementing it, a company would need to sponsor the work.


Adjust mobile zoom y target for leaves displaying below panel #210

Tested on render site with Firefox emulator for iPhone SE 2 - working properly for leaves throughout the tree.


Withdraw page

Hi, I just finished the 6th chapter but my withdraw page looks like this: http://prntscr.com/iarsdb. Even though I have no traces of any redlines or asiimovs in my codes. How can I fix this? How can I have it load skins from my bot's inventory?

@andrewda

@AidaMati; How did you resolve this issue?  I'm curious.

I think it kinda fixed itself. I had it load items from user's inventory, since then the asiimovs and redlines haven't shown up.
Might've been a Mongo issue but not sure.


Setting cache topic replication factor

I want to have the cache topic to be replicated. I have set props.put(KafkaCacheConfig.KAFKACACHE_TOPIC_REPLICATION_FACTOR_CONFIG, 3). In logs it says Creating the topic cache-test using a replication factor of 1, which is less than the desired one of 3.

Hi
@rayokota
, I am working on kcache and was stuck.I want to connect to a kafka-server that is using saslssl protocol but we are not able to connect to that server.what is the exact kafkacache config which we have to set where we can set jaas config also?https://github.com/rayokota/kcache

@bharathr9889 , did you look at https://www.javadoc.io/doc/io.kcache/kcache/latest/io/kcache/KafkaCacheConfig.html

@rayokota
io.kcache.exceptions.CacheInitializationException: Timed out trying to create or validate topic "mytopicname"
I am getting the above error, I have tried the above link too.
Checked the above link too, but it takes about all the parameters...it does not talk about which one to use to connect to sasl ssl...Pls help

hi @rayokota
I have started using 4.0.3 which has the parameter to provide jaas config.

However there is a issue in that if I use a topic that is already created :
props.setProperty(KafkaCacheConfig.KAFKACACHE_TOPIC_CONFIG, "<Existing_topic>");

We get below error :
io.kcache.exceptions.CacheInitializationException: Failed trying to create or validate topic <Existing_topic>
......
Caused by: java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.TopicAuthorizationException: Authorization failed.
at java.base/java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:395)
at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2022)
at org.apache.kafka.common.internals.KafkaFutureImpl.get(KafkaFutureImpl.java:180)
at io.kcache.KafkaCache.createTopic(KafkaCache.java:396)
at io.kcache.KafkaCache.createOrVerifyTopic(KafkaCache.java:350)
Note :
The calling method's class, io.kcache.KafkaCache, was loaded from the following location:
jar:file:/Users/breddy3/.m2/repository/io/kcache/kcache/4.0.3/kcache-4.0.3.jar!/io/kcache/KafkaCache.class

The called method's class, org.apache.kafka.clients.admin.DescribeTopicsResult, is available from the following locations:
jar:file:/Users/breddy3/.m2/repository/org/apache/kafka/kafka-clients/3.0.1/kafka-clients-3.0.1.jar!/org/apache/kafka/clients/admin/DescribeTopicsResult.class

The called method's class hierarchy was loaded from the following locations:
org.apache.kafka.clients.admin.DescribeTopicsResult: file:/Users/breddy3/.m2/repository/org/apache/kafka/kafka-clients/3.0.1/kafka-clients-3.0.1.jar

If we use a topic that is non Existing :
props.setProperty(KafkaCacheConfig.KAFKACACHE_TOPIC_CONFIG, "");

io.kcache.exceptions.CacheInitializationException: Failed trying to create or validate topic
at io.kcache.KafkaCache.createOrVerifyTopic(KafkaCache.java:360)
at io.kcache.KafkaCache.init(KafkaCache.java:276)

@bharathr9889 did you configure the SASL/JAAS properties correctly? For me, it worked by using the following properties:

KafkaCacheConfig.KAFKACACHE_SECURITY_PROTOCOL_CONFIG
KafkaCacheConfig.KAFKACACHE_SASL_MECHANISM_CONFIG
KafkaCacheConfig.KAFKACACHE_SASL_JAAS_CONFIG_CONFIG

We were using below configuration :
Properties props = new Properties();
props.setProperty(KafkaCacheConfig.KAFKACACHE_BOOTSTRAP_SERVERS_CONFIG, "something.us-east-1.aws.confluent.cloud:9092");
props.setProperty(KafkaCacheConfig.KAFKACACHE_TOPIC_CONFIG, "some.topic");
props.setProperty(KafkaCacheConfig.KAFKACACHE_SECURITY_PROTOCOL_CONFIG, "SASL_SSL");
props.setProperty(KafkaCacheConfig.KAFKACACHE_SASL_MECHANISM_CONFIG,"PLAIN");
props.setProperty(KafkaCacheConfig.KAFKACACHE_SASL_JAAS_CONFIG_CONFIG,
"org.apache.kafka.common.security.plain.PlainLoginModule required username='SOMETHING' password='ENCRYPTED SOMETHING';");

But this does not work.Could you please share your configuration?

@nadjahagen

@bharathr9889 , it looks like you are using Confluent Cloud.  Are you passing a valid API key as the username and a valid API secret as the password in the PlainLoginModule configuration?


Remove redundant pass-through shuffle manager classes [databricks]

Closes #9456
Contributes to #6565

additionally remove unsued pom properties
move as much of ShimLoader as possible to the api module
get shuffle manager definition to the point of an easy template, probably can be a shimplify feature

/*** spark-rapids-shim-json-lines
{"spark": "${buldver}"}
spark-rapids-shim-json-lines ***/
package com.nvidia.spark.rapids.spark${buldver}

import org.apache.spark.SparkConf
import org.apache.spark.shuffle.rapids.ProxyRapidsShuffleInternalManagerBase

/** A shuffle manager optimized for the RAPIDS Plugin for Apache Spark. */
sealed class RapidsShuffleManager(
    conf: SparkConf,
    isDriver: Boolean
) extends ProxyRapidsShuffleInternalManagerBase(conf, isDriver)

Signed-off-by: Gera Shegalov<EMAIL_ADDRESS>

build

build

build

build

It would be nice to have more description in the issue saying what exactly is redundant and why its redundant.

It would be nice to have more description in the issue saying what exactly is redundant and why its redundant.

@tgravescs described it in the issue #9456

build

Seems like the changes intended for this PR got mixed in with another PR that starts moving classes into sql-plugin-api. Makes it more difficult to review since there's sorta separate concerns happening in one PR.

The idea is to move the shuffle manager classes I am touching anyways and the minimum required. I'll separate the concerns

build


docs: LEAP-615: Mention spaces saving for Text tag

Text tag is displayed as html, so all spaces are smashed by browser, and they also go like this to result. To avoid this users can add custom style in config, described in docs. But it only says that this affects displaying, not saving the result. Adding this note as well.
PR fulfills these requirements

[ ] Tests for the changes have been added/updated
[x] Docs have been added/updated
[x] Best efforts were made to ensure docs/code are concise and coherent (checked for spelling/grammatical errors, commented out code, debug logs etc.)
[ ] Self-reviewed and ran all changes on a local instance

Describe the reason for change
https://github.com/HumanSignal/label-studio/issues/5338

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

Comparison is base (e9c9552) 68.70% compared to head (af738d8) 68.70%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1682   +/-   ##
=======================================
  Coverage   68.70%   68.70%
=======================================
  Files         443      443
  Lines       28734    28734
  Branches     7641     7641
=======================================
  Hits        19742    19742
  Misses       7748     7748
  Partials     1244     1244

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

/merge master

/git merge master


Throw an error if string variables are not passed to translate.

Translation strings can have variables inside them e.g. "hello":"Hello ${name}".
I'd like to have an error thrown if I forget to include the variable name when I do something like translate('hello').

Thanks for the suggestion, but I'm not sure I agree with this approach. My main concern is that throwing an error may be severe for this particular user error. An uncaught error, especially in React 16, could result in the entire application not working. I would prefer this to be a recoverable error that would allow the application to continue working. For that reason I prefer the current functionality that renders the translation string as is with missing variable name. e.g. Hello ${name} would be rendered.
One option could be to log a warning to the console. If you like this idea let me know or feel free to send a PR with the implementation.

Good point. Yes I agree an error is probably too aggressive, while a warning would still get the developer's attention without causing too much trouble.
I'd be more than happy to send a PR with that implementation, however I won't have the time for a week or so. If you want to get it done quick that's great. Otherwise I'll see what I can do in about a week.

Closing this as there has been no further requests for feature.


Add more binlogging

In trying to troubleshoot a couple build issues I realized that MSBuild binlogs were nice to have.  This change adds binlogging everywhere we can without changing the submodules' build scripts.  It also fixes up submodules' RepoBuilds so that they execute with the project directory as their current directory - this was the cause of getting random log files in the repos directory.

Instead of editing BuildCommand in individual repo files, would changing repos/dir.targets directly work? It contains lines like
<Exec Command="$(BuildCommand) $(RepoApiArgs) $(RedirectRepoOutputToLog)" WorkingDirectory="$(ProjectDirectory)" EnvironmentVariables="@(EnvironmentVariables)" />


Implement ZIP-253: Deployment of the NU6 Network Upgrade

Implement final version of zcash/zips#878:

[x] #8689
[x] #8681

It seems https://github.com/ZcashFoundation/zebra/issues/8689 and https://github.com/ZcashFoundation/zebra/issues/8681 are part of this major issue.

All tasks are now done. Closing


doc: Add a note on how to use CompactlyGeneratedSpace

Following this discussion : https://leanprover.zulipchat.com/#narrow/stream/116395-maths/topic/Compactly.20generated.20spaces/near/453958229.
Indicate that CompactlyGeneratedSpace should be used with an explicit universe parameter.

Can you also change the docstring of CompactlyGenerated to
"CompactlyGenerated.{u, w} is the type of u-compactly generated w-small topological spaces."
to indicate that it should also be used with explicit universe parameters.

Done!

Thanks! :tada:
bors merge


Remove usages of rapids-env-update

Reference: https://github.com/rapidsai/ops/issues/2766
Replace rapids-env-update with rapids-configure-conda-channels, rapids-configure-sccache, and rapids-date-string.
Description

Checklist

[ ] I am familiar with the Contributing Guidelines.
[ ] New or existing tests cover these changes.
[ ] The documentation is up to date with these changes.
[ ] The cmake-format.json is up to date with these changes.
[ ] I have added new files under rapids-cmake/

[ ] I have added include guards (include_guard(GLOBAL))
[ ] I have added the associated docs/ rst file and update the api.rst

/merge


Using zippa on a complex tree (concrete syntax tree)

Is there a way to make use of zippa on a non-uniform JS tree with both objects and arrays? Basically I'm looking for a way to traverse an arbitrary JS object that has arrays and other properties, and be able to mutate them and work with them using the zipper pattern.
SpecificallyI have a concrete syntax tree produced out of from chevrotain. Here's the example: https://github.com/SAP/chevrotain/blob/master/docs/concrete_syntax_tree.md
So something like this:
{
  name: "grammar rule",
  children: [ TokenObject, anotherCstNode ]
}

According to the README, making a zippa requires 3 functions, determining if something is a branch, getting the children, and making a new node.
However in my case, I may want to make a specific kind of token object, a complete cst node with a certain name... etc. These are all different.

You are correct, zippa interfaces with your data only through the three functions provided. From looking at the CST data, you may be able to operate on it with a zipper, though I'm not familiar enough with the chevrotain, its CST and the problem domain to say if it is practical or the best approach. Anyway, I'll give it a shot.
I see that the CST data often uses objects as children, where the value on each property has a distinct semantic meaning based on the key:
{
  name: "qualifiedName",
  children: {
      Dot : ["."],
      Identifier : ["foo", "bar"]
  }
}

I'm referring to the Dot and Identifier keys above. If we consider the above data as a node in a tree, and we want to consider ['.'] and ['foo', 'bar'] as its children, we have a problem. Reconstructing Identifier: ['foo', 'bar'] from only ['foo', 'bar'] is not possible—it could be something else than Identifier for all we know. Writing makeNode would not be possible.
My initial thought would be to treat these kinds of objects as a list of associations (of type Array<[String, Any]> in TypeScript notation), where you treat each association [String, Any] as a (child) node. You would then write the three functions so that they handle both nodes of type { name: String, children: Object } and [String, Any]. Without handling any of the edge cases, the basic pattern looks like this:
import {
    fromPairs,
    toPairs,
} from 'ramda';

function getChildren(node) {
    if (node instanceof Array && node.length === 2) {
        // What you want to do here depends on the problem domain.
        // (Maybe these are always leaves in the tree)?
        const [name, children] = node;
        return children;
    }
    return toPairs(node.children);
}
function makeNode(oldParent, children) {
    if (oldParent instanceof Array && oldParent.length === 2) {
        const [oldName, _oldChildren] = oldParent;
        return [oldName, children];
    }
    return {
        name: oldParent.name,
        // Note that your application should enforce that all the children
        // here are of type [String, Any]
        children: fromPairs(children),
    };
}

function isBranch(node) {
    // TODO
}

These should set up the zipper structure for operating on the CST. In your tree operations you need to know when to return nodes of type [String, Any] and { name: String: children: Object }.

I realised that the cst is not very good due to lack of ordering between subrules. So I'm building my own CST now, this issue shouldn't be a problem.

Another issue I discovered, is that I actually want to mutate a single CST. So that way zipper cursors all operate on all the same tree. But I don't think this kind of concurrent/mutable zipper pattern has been well investigated.

If you want to mutate a tree in-place, the zipper data structure is not the right choice. The zipper data structure originated from needing a functional, immutable, but still fairly performant approach to modifying trees—see this paper. Instead you can use the tree visitor pattern that far predates zippers, and you should find plenty of information and real world examples on that on the internet.

I don't know if this is relevant https://pavpanchekha.com/blog/zippers/multi-zippers.html but I'll take a look in the future.