Update docs, getParts

Im trying to send post method which has a json and a file. I've seen the jsonpost and upload example but i cant find the combination of those two.
Heres the parsed from google chrome devtools from network tab
orm: [{"7920afe5-35d4-4bb8":[{"table":"filtest","refOnly":false,"id":null,"o":"i","d":{"image":"p@r@d1&41|e$-//ac428a17-d310-44a3","message":"adsadasd"},"relTable":null,"relID":null,"relType":null,"rID":"d6d46472-618c-4935"}]}] type: write 7920afe5-35d4-4bb8.image.ac428a17-d310-44a3: (binary)
Heres the formdata
`
------WebKitFormBoundaryCZAzpwArS08GV2Cp
Content-Disposition: form-data; name="orm"
[{"7920afe5-35d4-4bb8":[{"table":"filtest","refOnly":false,"id":null,"o":"i","d":{"image":"p@r@d1&41|e$-//ac428a17-d310-44a3","message":"adsadasd"},"relTable":null,"relID":null,"relType":null,"rID":"d6d46472-618c-4935"}]}]
------WebKitFormBoundaryCZAzpwArS08GV2Cp
Content-Disposition: form-data; name="type"
write
------WebKitFormBoundaryCZAzpwArS08GV2Cp
Content-Disposition: form-data; name="7920afe5-35d4-4bb8.image.ac428a17-d310-44a3"; filename="svelte preproess bug.png"
Content-Type: image/png
------WebKitFormBoundaryCZAzpwArS08GV2Cp--
`

uWS.getParts(arrayBuffer) is your friend

https://github.com/uNetworking/uWebSockets.js/blob/61fa4bd06cf9db078716dc0c70bc5e8274d742f6/docs/index.d.ts#L319

@alexhultman
Im not able to make it work
 // im using babel-node
import server from "./uws"
import contentType from "content-type"
async function serve() {
    let prom = Promise
    let app = server.App()
    app.get("/*", async (res, req) => {
        console.log("log")
        res.writeHeader("Access-Control-Allow-Origin", "*") //allow cors
        res.end("hello world")
    })

    app.post("/paradis", async (res, req) => {
        res.writeHeader("Access-Control-Allow-Origin", "*") //allow cors
        let headers = {}
        req.forEach((k, v) => {
            headers[k] = v
        })
        //content-type
        let type = contentType.parse(headers["content-type"]).type
        res.onData(async (chunk, isLast) => {
            /* Buffer this anywhere you want to */
            console.log("Got chunk of data with length " + chunk.byteLength + ", isLast: " + isLast)
            /* We respond when we are done */
            if (isLast) {
                let buffer = Buffer.from(chunk)
                let string = Buffer.from(chunk).toString()
                let payloadFromChunk = server.getParts(chunk,type)
                let payloadFromBuffer = server.getParts(buffer,type)
                let payloadFromString = server.getParts(string,type)
                console.log(payloadFromChunk) //returns undefined
                console.log(payloadFromBuffer) //returns undefined
                console.log(payloadFromBuffer) //returns undefined
                res.end('Thanks for the data!');
            }
        })

        console.log("request received")
        res.onAborted(() => {
            console.log("aborted")
        })
        return Promise.resolve(true)
    })

    app.listen(1234, (token) => {
        if (token) {
            return prom.resolve(true)
        } else {

            console.log("failed listening")
            return prom.reject()
        }
    })
}

;(async function main() {
    await serve()
    console.log("Server is now listening")
})()

Log

Im only able to get parts using Busboy. I hope there's a better way coz i dont want to uws to slow down a bit bcoz of Busboy.
let buffer = Buffer.from(chunk)
let bb = new Busboy({headers: {'content-type': headers["content-type"]}})
//some Busboy events
bb.end(buffer)

You are not passing content-type, you're passing some kind of parsed-up nonsense. Why would the library have a feature that would be dependent on some other module? It makes no sense, but I'll give you a pass since there is in fact no documentation explicitly stating that, yes, you pass contentType as in content-type...

 I fucked it up seriously.
``javascript
let payloadFromChunk = getParts(chunk,headers["content-type"]) // that worked,
Thank you for your quick respond and I really appreciate your hard-work. God bless.

Well I cannot sleep so nothing else to do


Pandoc - allow citeproc extension to be invoked, with bibliography.

The start of improved pandoc support by being able to pandoc's commandline arguments, ref #8152.

It looks like the venerable https://github.com/gohugoio/hugo/pull/7529 is a more developed + better PR for this.


New version: Nemo v0.33.0

Registering package: Nemo
Repository: https://github.com/Nemocas/Nemo.jl
Created by: @thofma
Version: v0.33.0
Commit: 4a9a6ff83b956d2151f294745f724e801e8cbae7
Reviewed by: @thofma
Reference: https://github.com/Nemocas/Nemo.jl/commit/4a9a6ff83b956d2151f294745f724e801e8cbae7#commitcomment-78604341
Description: Julia bindings for various mathematical libraries (including flint2)

can be closed


The requested module does not provide an export named 'computed'

Hi, would you please consider making vite-plugin-vue-layouts compatible with vue2 as well?
https://github.com/hannoeru/vite-plugin-pages works fine with vite & vue2.
Adding layouts doesn't work though, as this
https://github.com/JohnCampionJr/vite-plugin-vue-layouts/blob/44d27894f1baf6b4f3011c4531af6fc23d6db9de/src/RouteLayout.ts#L8
results in
The requested module does not provide an export named 'computed'
Any suggestions on how to tackle this?
Thanks for considering!

Looks like this provides computed
https://github.com/vuejs/composition-api/search?q=computed
but needs to be imported like this?
import { ref, reactive } from '@vue/composition-api'
Or, maybe vue version could be checked and for vue2 don't import computed, as it just works (I think)

vue-router-layout works fine with vite and vue2, so I'll keep that until vue3.

@mariusa  Hello. Please tell me how you could make friends vue-router-layout + vite-plugin-pages + vue 2.
I keep catching the "Maximum call stack size exceeded" error and don't know how to fix it.
I took the assembly as a basis.
https://github.com/lstoeferle/vite-vue2-windicss-starter
And an example of using vue-router-layout from here.
https://github.com/antfu/vitesse
I created a repository with my problem, you can see
https://github.com/Batyodie/vite-starter-vue2
Here is a screenshot of the error.

Screenshot of my router file.

My main js file.

Hi, I've moved to vue3... I think I started from https://github.com/matt-auckland/vite-vue2-starter and added layout, it just worked for me.


Fix russian missed

Could you please create a new pull-request without that ugly "merge pull request" commits? You can follow Yii2 tutorial.


Unable to download webpage

I used to download from youtube but it gives me errors now. I have python3.4.3+ but it seems youtube-dl uses python 2.7.10.
mahdi@JackJack:~$ youtube-dl --verbose -F https://www.youtube.com/watch?v=XxWU-09R1SM
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'--verbose', u'-F', u'https://www.youtube.com/watch?v=XxWU-09R1SM']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2015.07.07
[debug] Python version 2.7.10 - Linux-4.0.0-2-amd64-x86_64-with-debian-stretch-sid
[debug] exe versions: none
[debug] Proxy map: {}
[youtube] XxWU-09R1SM: Downloading webpage
ERROR: Unable to download webpage: <urlopen error [Errno 104] Connection reset by peer> (caused by URLError(error(104, 'Connection reset by peer'),))
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 312, in _request_webpage
return self._downloader.urlopen(url_or_request)
File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 1729, in urlopen
return self._opener.open(req, timeout=self._socket_timeout)
File "/usr/lib/python2.7/urllib2.py", line 431, in open
response = self._open(req, data)
File "/usr/lib/python2.7/urllib2.py", line 449, in _open
'_open', req)
File "/usr/lib/python2.7/urllib2.py", line 409, in _call_chain
result = func(*args)
File "/usr/local/bin/youtube-dl/youtube_dl/utils.py", line 717, in https_open
req, **kwargs)
File "/usr/lib/python2.7/urllib2.py", line 1197, in do_open
raise URLError(err)

Can you watch the video in browsers directly?

Not without a proxy and I've tried setting up a proxy for youtube-dl too and it doesn't work. But my brother who uses the same ISP can download youtube videos even without proxy.

Sometimes I get an error different from the first one.
mahdi@JackJack:~$ youtube-dl --verbose -F https://www.youtube.com/watch?v=Ss39UktpXk0
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'--verbose', u'-F', u'https://www.youtube.com/watch?v=Ss39UktpXk0']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2015.07.07
[debug] Python version 2.7.10 - Linux-4.0.0-2-amd64-x86_64-with-debian-stretch-sid
[debug] exe versions: none
[debug] Proxy map: {}
[youtube] Ss39UktpXk0: Downloading webpage
ERROR: Unable to download webpage: <urlopen error [SSL: UNKNOWN_PROTOCOL] unknown protocol (_ssl.c:590)> (caused by URLError(SSLError(1, u'[SSL: UNKNOWN_PROTOCOL] unknown protocol (_ssl.c:590)'),))
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 312, in _request_webpage
return self._downloader.urlopen(url_or_request)
File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 1729, in urlopen
return self._opener.open(req, timeout=self._socket_timeout)
File "/usr/lib/python2.7/urllib2.py", line 431, in open
response = self._open(req, data)
File "/usr/lib/python2.7/urllib2.py", line 449, in _open
'_open', req)
File "/usr/lib/python2.7/urllib2.py", line 409, in _call_chain
result = func(*args)
File "/usr/local/bin/youtube-dl/youtube_dl/utils.py", line 717, in https_open
req, **kwargs)
File "/usr/lib/python2.7/urllib2.py", line 1197, in do_open
raise URLError(err)

What's the error message when using a proxy with youtube-dl?

After reading http://unix.stackexchange.com/questions/71481/use-socks-proxy-for-commands-in-terminal I used this command:
export http_proxy=socks5://<IP_ADDRESS>:8080 https_proxy=socks5://<IP_ADDRESS>:8080
And then:
mahdi@JackJack:~$ youtube-dl --verbose --proxy <IP_ADDRESS>:1080 -F https://www.youtube.com/watch?v=JG9c3uF8NbY
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'--verbose', u'--proxy', u'<IP_ADDRESS>:1080', u'-F', u'https://www.youtube.com/watch?v=JG9c3uF8NbY']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2015.07.18
[debug] Python version 2.7.10 - Linux-4.0.0-2-amd64-x86_64-with-debian-stretch-sid
[debug] exe versions: none
[debug] Proxy map: {u'http': u'<IP_ADDRESS>:1080', u'https': u'<IP_ADDRESS>:1080'}
[youtube] JG9c3uF8NbY: Downloading webpage
ERROR: Unable to download webpage: '' (caused by BadStatusLine("''",)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 314, in _request_webpage
return self._downloader.urlopen(url_or_request)
File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 1731, in urlopen
return self._opener.open(req, timeout=self._socket_timeout)
File "/usr/lib/python2.7/urllib2.py", line 431, in open
response = self._open(req, data)
File "/usr/lib/python2.7/urllib2.py", line 449, in _open
'_open', req)
File "/usr/lib/python2.7/urllib2.py", line 409, in _call_chain
result = func(*args)
File "/usr/local/bin/youtube-dl/youtube_dl/utils.py", line 717, in https_open
req, **kwargs)
File "/usr/lib/python2.7/urllib2.py", line 1194, in do_open
h.request(req.get_method(), req.get_selector(), req.data, headers)
File "/usr/lib/python2.7/httplib.py", line 1052, in request
self._send_request(method, url, body, headers)
File "/usr/lib/python2.7/httplib.py", line 1092, in _send_request
self.endheaders(body)
File "/usr/lib/python2.7/httplib.py", line 1048, in endheaders
self._send_output(message_body)
File "/usr/lib/python2.7/httplib.py", line 892, in _send_output
self.send(msg)
File "/usr/lib/python2.7/httplib.py", line 854, in send
self.connect()
File "/usr/lib/python2.7/httplib.py", line 1265, in connect
HTTPConnection.connect(self)
File "/usr/lib/python2.7/httplib.py", line 834, in connect
self._tunnel()
File "/usr/lib/python2.7/httplib.py", line 811, in _tunnel
(version, code, message) = response._read_status()
File "/usr/lib/python2.7/httplib.py", line 417, in _read_status
raise BadStatusLine(line)

socks5 proxies are not supported yet. See #402.

I know :-/ that's why I googled it. I use a SSH connection. But my point is, I used to download videos without any proxy as my brother does right now

Sorry if you can't watch the video in browsers, youtube-dl can't help more.

I switched to Ubuntu 14.04 and now it works, despite being unable watch the videos in youtube.com


Analyse encoding of arrays in msgpack

Msgpack supports both maps and arrays for lists of data. When a packing is done from php, a map could be created both with string or integer keys. An msgpack array is created when the php array has only integer keys that are sequential and starting from 0.
Katana has strong types and map keys must be strings, so any integer key in a map will result in error.
Some solution is needed to prevent those errors.
The library could have some options. https://github.com/rybakit/msgpack.php#type-detection-mode

@fcastilloes It's quite easy to achieve with the new msgpack.php v0.3.0:
First, create a "packable" type transformer:
class StringKeyMapTransformer implements Packable
{
    public function pack(Packer $packer, $value)
    {
        if (!$value instanceof Map) {
            return null;
        }

        $data = $packer->packMapHeader(\count($value->map));
        foreach ($value->map as $key => $val) {
            $data .= $packer->packStr($key).$packer->pack($val); // keys get packed to str
        }

        return $data;
    }
}

Then register it and wrap your assoc arrays with MessagePack\Type\Map objects:
use MessagePack\Packer;
use MessagePack\Type\Map;

$packer = new Packer();
$packer->registerTransformer(new StringKeyMapTransformer());

$packed = $packer->pack(new Map($data));

Thanks a lot @rybakit, I am busy in other projects now, but this looks great for this and a couple of other types I need to serialize. I'll definitely give it a try.


Explore checksum applied to OSF

We need to look at how OSF handles checksums in order to be applied to fixity.

@jeff gave a presentation about this at one of the presqt workshops - i’ll get a link and share here - also loop him in on fixity - osf  to save time ?

A bit on checksum basics:
https://www.youtube.com/watch?v=SRvAGFJO0yw
And a presentation I gave at PresQt is here: [20180918_presqt_spies.pptx].
(https://github.com/ndlib/presqt/files/2891157/20180918_presqt_spies.pptx)

we need to have a look at bitcurator features too

OSF uses sha256 and MD5.


Quick start script broken by ocamlfind 1.9.6

This issue is for tracking a failure upstream in the recent release of ocamlfind 1.9.6. See https://github.com/ocaml/opam-repository/issues/23501. If there isn't a ready fix for that, we can work around it on the Dream side by adding a constraint on ocamlfind in the examples' esy.json.
For search purposes:

ocamlfind 1.9.6 is failing to build in Dream's quick start script on Ubuntu with
   Cannot find file /home/runner/.esy/3__________________________________________________________________/s/opam__s__ocamlfind-opam__c__1.9.6-fa4fed9f/lib/findlib/findlib.cma.
    Cannot find file /home/runner/.esy/3__________________________________________________________________/s/opam__s__ocamlfind-opam__c__1.9.6-fa4fed9f/lib/findlib/findlib_top.cma.
    File "/home/runner/.esy/3__________________________________________________________________/i/ocaml-4.12.1001-d0588c96/lib/ocaml/topfind", line 53, characters 0-22:
    53 | Topfind.add_predicates [ pred; "toploop" ];
         ^^^^^^^^^^^^^^^^^^^^^^
    Error: Unbound module Topfind
    Hint: Did you mean Topdirs?
    Unknown directive `require'.
    error: command failed: 'ocaml' 'pkg/pkg.ml' 'build' '--dev-pkg' 'false' '--with-base-unix' 'true' '--with-cmdliner' 'false' (exited with 2)

It is also failing on macOS with
    install: /Users/runner/.esy/3_________________________________________________________________/i/ocaml-4.12.1001-00b0534a/lib/ocaml//topfind: Operation not permitted

ocamlfind 1.9.5 builds succeeded on both Ubuntu and macOS earlier on the same day (the day ocamlfind 1.9.6 was released).

Probably will be fixed by https://github.com/esy-ocaml/esy-opam-override/pull/129.

Now fixed upstream.


How do I uninstall this?

I tried uninstalling this program while cairo was still open. It didn't work and now when I try to uninstall it, the control panel says there was an error uninstalling cairo and asks me if I want to remove if from the list of installed applications, so I clicked yes. But I found a Cairo Shell folder in Program Files, and clicking CairoDesktop.exe opens cairo, so clearly it isn't uninstalled. Can I just delete the Cairo Shell folder, or will that not be a total and clean uninstall?

All of Cairo's program files are in that one directory. As long as you didn't select to replace Explorer, and you have removed Cairo from your startup items, you can remove this folder and consider Cairo completely uninstalled.

Marking this as a bug since the uninstaller needs to check if Cairo is running first to prevent failed uninstalls. Thanks for reporting the issue!

One solution would be to, while using explorer as shell, reinstall Cairo and then immediately uninstall Cairo.
If you don’t mind me asking why are you choosing to remove Cairo? Missing functionality?
Sent from my iPhone
On Mar 11, 2019, at 4:49 PM, Sam Johnson <notifications<EMAIL_ADDRESS>wrote:
All of Cairo's program files are in that one directory. As long as you didn't select to replace Explorer, and you have removed Cairo from your startup items, you can remove this folder and consider Cairo completely uninstalled.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fcairoshell%2Fcairoshell%2Fissues%2F241%23issuecomment-471723983&data=02|01||74668d1789974fbf86d208d6a6631a8f|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636879341900199875&sdata=gDS9%2BowVohxGNoc5bVar7mB%2F85ZVuDmOoESS2%2B5VOw4%3D&reserved=0, or mute the threadhttps://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAGxXAYbLHV1VjjQTv85LzKWXfcwRCU8iks5vVsFtgaJpZM4bph69&data=02|01||74668d1789974fbf86d208d6a6631a8f|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636879341900209886&sdata=WcfmSUniXsXh8QndDWL%2B5lCtri%2FsN4GI8eveuOQf9qw%3D&reserved=0.

Thanks for the advice. And in regards to your question, I think I'm just stuck in my ways. I've had more or less the same setup for the last 20 years, be it on windows or KDE: two row height taskbar on primary monitor, one row height taskbar on secondary monitor, both with "combine taskbar entries" or whatever it's called disabled. Believe it or not, using Cairo shell for 10 minutes actually started giving me anxiety lol. The same thing happens when I use my sister's MacBook Pro. It's no fault of Cairo though, like I said I think I'm just stuck in my ways.

Fix available in the latest release.

Hi @Rofii 😊
You have probably found the solution as of 2019, I was in the same problem as of today August 2024. I will give you the step of how I was able to put my computer back to normal. Or if it could help others, then good for them.
It is simple as this 😅
Step 1 : Open task manager Crtl + Shift + Esc or Crtl + Alt + Delete and chose task manager it does the same
Step 2 : End task for cairo
Step 3: Don't forget to go to Startup section and put it on disabled
You should be fine to uninstall cairo. Try to restart your computer after ending task and after uninstall Cairo too.
Some things had changed for me when I got back to my old computer. The folder on my Desktop were not there.
So I did a right click on the desktop and then click on show desktop items
and my task bar didn't show either
So I clicked right on the task bar and then clicked on show task bar.
And here we go! Everything was back as normal !


Add sample component as we continue to move component specific scripts out of build repo

Signed-off-by: Peter Zhu<EMAIL_ADDRESS>Description
Add sample component as we continue to move component specific scripts out of build repo
Issues Resolved
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #1929 (38b2a56) into main (5cb1786) will increase coverage by 0.39%.
The diff coverage is n/a.

:exclamation: Current head 38b2a56 differs from pull request most recent head cf32955. Consider uploading reports for the commit cf32955 to get more accurate results

@@             Coverage Diff              @@
##               main    #1929      +/-   ##
============================================
+ Coverage     94.60%   95.00%   +0.39%
  Complexity       20       20
============================================
  Files           178       44     -134
  Lines          3633      220    -3413
  Branches         27       27
============================================
- Hits           3437      209    -3228
+ Misses          192        7     -185
  Partials          4        4

Impacted Files
Coverage Δ

...workflow/integ_test/integ_test_start_properties.py

.../ci_workflow/ci_check_gradle_properties_version.py

src/manifests_workflow/input_manifests.py

.../assemble_workflow/bundle_opensearch_dashboards.py

src/test_workflow/integ_test/integ_test_runner.py

src/manifests/build/build_manifest_1_0.py

src/assemble_workflow/dist.py

src/build_workflow/builders.py

src/system/zip_file.py

...teg_test_start_properties_opensearch_dashboards.py

... and 124 more

Continue to review full report at Codecov.

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


Force passing an Instance* into surface creation

Summary of the PR
This matches changes upstream in wgpu
Related issues, Discord discussions, or proposals
https://discord.com/channels/521092042781229087/607634593201520651/1075701251871866880
Further Comments
only about a month late :^)

Relies on #1318


How to train if there are multiple sources?

Suppose we have 3 sources domain and 1 target domain. How should I train DANN in this case? Should I combine all the 3 sources into only 1 source or should I label those 3 domain separately during training?

There's a paper for that: "Multi-adversarial domain adapation".
https://pdfs.semanticscholar.org/ffda/dffca8bb57e59db10e5ee702b8f6ccab52cf.pdf


chore: update for react hooks guidelines

Updating the user guidelines for React hooks.

Perhaps this is out of scope for this PR, but so long as we're discussing memoization tactics specifically, should we add some general remarks about React Compiler? This seems especially relevant now with the new react compiler beta release that supports react v17-18.
It appears that in general manual memoization will be stripped and replaced by React Compiler, and therefore could be removed altogether eventually. It doesn't seem like this should affect our current code.
However, an exception is memoization that is intended to ensure correctness instead of performance benefits. Maybe we should add a guideline to highlight any new additions that fall under this category with a comment, so that we know not to remove them in the future.

It is generally safe to leave manual memoization in your code – the compiler understands it but will compile in its own lower-level form of memoization even for manually memoized code. The compiler does however check its memoization against manual memoization to ensure that we memoized it exactly the same. The reason we need to do this is in case the manual memoization was used for correctness. For example, if a manually memoized value was passed as a dependency to a useEffect call somewhere else and it wasn't memoized in the same way, this might cause over/under firing of effects or even infinite loops.
For this reason, our current recommendation is to leave manual memoization in for existing code, but for new code written after the compiler is added you can omit them.
-- https://github.com/reactwg/react-compiler/discussions/16#discussioncomment-9991176


MjmlSelector and MjmlHtmlAttribute were not migrated to v3

Hey team,
I'm running into an issue when updating from 2.1.4 to 3.0.0. It looks like MjmlHtmlAttribute(singular) and MjmlSelector were removed and not migrated to typescript in #17. Only MjmlHtmlAttributes (plural) is being exported but the selector and html attribute are required to be used inside the HTML attributes in the mjml docs.
Is there a way to have the MjmlHtmlAttributes in the same way without using the selector and HTML attribute that I'm missing?
For context, I need to mark certain elements as a universal link for SendGrid. https://sendgrid.com/docs/ui/sending-email/universal-links/#flagging-your-universal-links
Let me know if I've missed anything. 😄 Thanks for your help in advance!

Hi @vongb Thanks for the heads up. These components weren't imported automatically because they aren't created as components in mjml
I've added them manually in #75

Awesome, thank you!!

@IanEdington works great thanks!!!


Improve RtL support

closing - app will be moved to mature support at 6.1. Use Minimal Gallery app instead.


Fix :: Ignore current selectedColumns when editing a step

A bug was introduced leading to potentially override an input that listen on selectedColumn when editing a step. To fix that, we remove the immediate: true on the watcher and handle the edition case in mounted cycle.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #229   +/-   ##
=======================================
  Coverage   99.26%   99.26%
=======================================
  Files          48       48
  Lines         678      678
  Branches      116      116
=======================================
  Hits          673      673
  Misses          5        5

Impacted Files
Coverage Δ

src/components/stepforms/StepForm.vue
100% <ø> (ø)
:arrow_up:

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 d931477...abef75f. Read the comment docs.


SpinBox value ignores step

Godot version:
3.0.6.stable.official
OS/device including version:
Ubuntu 18.04.1
Issue description:

The SpinBox .value member ignores the step value
I expect the value to always be equal to what appears visually on the control

Steps to reproduce:

Create a SpinBox control
Set the step to 0.1
Enter 1.11111 in the conrol

The control will show 1.1 but Spinbox.value is 1.11111. The value_changed signal also gives the unrounded value. Example project attached.
Minimal reproduction project:
SpinBox_Value_Debug.zip

Yes I think the correct behavior should be that display number always match real value (in this case 1.11111)
About the step, I do not think we should round it to step by default. It should be the add/sub value like it is. For example, If it is round to the nearest step, we cannot have a spinbox go like 0.05, 0.15, 0.25, ...
Although if "rounded" option is on, it may makes sense to round to multiples of step value instead of integer like current. But who know they may want to round to integer. So we may let it as generic and just manually snap it in script.

Fixed in 3.1 or 3.2


Fix coverage icon

Coverage remained the same at 89.908% when pulling 8526db9896ac2e9157a7d00513889aea7666ead4 on cgabard-patch-1 into eb9c670f16901dc033c44a60a4f47a2322530d89 on master-zds.


[BUG] - NVDashboard's "GPU Resources" inactive with K80s

Describe the bug
The GPU Resources graph is inactive when using Nebari instances with K80s:

It works as expected while using T4s though.
Expected behavior
The plot should report real-time usage:

OS and architecture in which you are running Nebari
GCP
How to Reproduce the problem?
Setup a Nebari instance with K80 GPUs, start the relevant instance, and open the GPUResources plot from the nvdashboards jupyterlab extension.
Command output
No response
Versions and dependencies used.
No response
Compute environment
GCP
Integrations
No response
Anything else?
I tested this on nebari.quansight.dev

@peterbell10 is this something you could help us reproduce / confirm if this is an issue for you?


[Question] Is it possible to deploy a daemon directly on the host which is running harvester?

I believe harvester is running some version of OpenSUSE. If I ssh into the server and try to deploy say an snmp  daemon, I get an error.
"The target filesystem is mounted as read-only. Please make sure the target filesystem is writeable."

Hi, Harvester has an immutable OS design, so most paths are read-only. Can you try to deploy the workload with a Kubernetes daemon set? It's possible to enable rw mode for debugging purposes, but keep in mind the change is gone after an upgrade.


Feature/blazor update

New Pull Request
For more information, see the CONTRIBUTING guide.
Prerequisites
Please make sure you can check the following boxes:

[x] I have read the CONTRIBUTING document
[x] My code follows the code style of this project
[x] All new and existing tests passed

Type(s) of Changes
Contribution Type
What types of changes does your code introduce? Put an x in all the boxes that apply:

[ ] Bug fix (non-breaking change which fixes an issue, please reference the issue id)
[ ] New feature (non-breaking change which adds functionality, make sure to open an associated issue first)
[x] Breaking change (fix or feature that would cause existing functionality to change)
[x] I have updated the documentation accordingly
[ ] I have added tests to cover my changes

Description
Update piral-blazor to use the blazor npm package under the hood, and consequently remove the internal files. This enables flexible versioning of Blazor, separates the concerns, and reduces fetching from NuGet.
Remarks
The README was altered to the best of my knowledge, ideally, it should be reviewed.

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


CVAT-CANVAS build FAILS running "yarn run build"

My actions before raising this issue

[ ] Searched past issues
[ ] Read/searched the docs

cvat-canvas build fails in two different ways.
Expected Behaviour

As it says in cvat/cvat-canvas/README.md I should be able to build the module from source using "yarn run build".
Current Behaviour

Running "yarn run build" results in this error:
yarn run build

yarn run v1.22.19

$ tsc && webpack --config ./webpack.config.js

src/typescript/masksHandler.ts:244:32 - error TS2349: This expression is not callable.

  Each member of the union type '{ <K extends "toString" | "left" | "flipY" | "center" | "top" | "visible" | "canvas" | "data" | "clipPath" | "toggle" | "fill" | "group" | "type" | "angle" | "points" | "width" | "height" | ... 182 more ... | "snapThreshold">(key: K, value: Polygon[K] | ((value: Polygon[K]) => Polygon[K])): Object; (options: Partial...' has signatures, but none of those signatures are compatible with each other.

244                         object.set({ fill: color.toRgba() });

Found 1 error.

error Command failed with exit code 1.

Even if i comment out line 244 in src/typescript/masksHandler.ts the build command fails anyway:
yarn run build

yarn run v1.22.19

$ tsc && webpack --config ./webpack.config.js

../node_modules/@types/three/src/renderers/WebGLRenderer.d.ts(34,34): error TS2304: Cannot find name 'OffscreenCanvas'.

../node_modules/@types/three/src/renderers/WebGLRenderer.d.ts(34,34): error TS2304: Cannot find name 'OffscreenCanvas'.

asset cvat-canvas.8cbe634c66d0b5940f5d.js 576 KiB [emitted] [immutable] [minimized] [big] (name: cvat-canvas) 2 related assets

orphan modules 323 KiB [orphan] 20 modules

runtime modules 972 bytes 5 modules

cacheable modules 1.5 MiB

  modules by path ../node_modules/ 1.17 MiB

    ../node_modules/polylabel/polylabel.js 4.76 KiB [built] [code generated]

    ../node_modules/fabric/dist/fabric.js 987 KiB [built] [code generated]

    + 8 modules

  modules by path ./src/ 333 KiB

    ./src/typescript/canvas.ts + 20 modules 326 KiB [built] [code generated]

    ./src/scss/canvas.scss 685 bytes [built] [code generated]

    ../node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[1].use[1]!../node_modules/postcss-loader/src/index.js??ruleSet[1].rules[1].use[2]!../node_modules/sass-loader/dist/cjs.js!./src/scss/canvas.scss 5.93 KiB [built] [code generated]

  modules by path jsdom/lib/jsdom/ 30 bytes

    jsdom/lib/jsdom/living/generated/utils (ignored) 15 bytes [built] [code generated]

    jsdom/lib/jsdom/utils (ignored) 15 bytes [built] [code generated]

  jsdom (ignored) 15 bytes [built] [code generated]

LOG from e

<i> No entry point specified, using webpack config for entrypoint(s)

<w> Failed to create .d.ts Error: Compiled with errors

<w>     at checkDiagnosticsErrors (/home/edoardo/cvat/node_modules/dts-bundle-generator/dist/helpers/check-diagnostics-errors.js:21:11)

<w>     at checkProgramDiagnosticsErrors (/home/edoardo/cvat/node_modules/dts-bundle-generator/dist/helpers/check-diagnostics-errors.js:12:5)

<w>     at getDeclarationFiles (/home/edoardo/cvat/node_modules/dts-bundle-generator/dist/compile-dts.js:99:66)

<w>     at compileDts (/home/edoardo/cvat/node_modules/dts-bundle-generator/dist/compile-dts.js:35:20)

<w>     at generateDtsBundle (/home/edoardo/cvat/node_modules/dts-bundle-generator/dist/bundle-generator.js:27:43)

<w>     at e.<anonymous> (/home/edoardo/cvat/node_modules/bundle-declarations-webpack-plugin/lib/index.js:1:4697)

<w>     at /home/edoardo/cvat/node_modules/bundle-declarations-webpack-plugin/lib/index.js:1:2623

<w>     at Object.next (/home/edoardo/cvat/node_modules/bundle-declarations-webpack-plugin/lib/index.js:1:2728)

<w>     at a (/home/edoardo/cvat/node_modules/bundle-declarations-webpack-plugin/lib/index.js:1:1442)

<w>     at processTicksAndRejections (node:internal/process/task_queues:96:5)

+ 2 hidden lines

WARNING in asset size limit: The following asset(s) exceed the recommended size limit (244 KiB).

This can impact web performance.

Assets:

  cvat-canvas.8cbe634c66d0b5940f5d.js (576 KiB)

WARNING in entrypoint size limit: The following entrypoint(s) combined asset size exceeds the recommended limit (244 KiB). This can impact web performance.

Entrypoints:

  cvat-canvas (576 KiB)

      cvat-canvas.8cbe634c66d0b5940f5d.js

WARNING in webpack performance recommendations:

You can limit the size of your bundles by using import() or require.ensure to lazy load some parts of your application.

For more info visit https://webpack.js.org/guides/code-splitting/

webpack 5.74.0 compiled with 3 warnings in 48021 ms

assets by status 3.15 MiB [cached] 1 asset

759 modules

LOG from e

<i> No entry point specified, using webpack config for entrypoint(s)

<w> Failed to create .d.ts Error: Compiled with errors

<w>     at checkDiagnosticsErrors (/home/edoardo/cvat/node_modules/dts-bundle-generator/dist/helpers/check-diagnostics-errors.js:21:11)

<w>     at checkProgramDiagnosticsErrors (/home/edoardo/cvat/node_modules/dts-bundle-generator/dist/helpers/check-diagnostics-errors.js:12:5)

<w>     at getDeclarationFiles (/home/edoardo/cvat/node_modules/dts-bundle-generator/dist/compile-dts.js:99:66)

<w>     at compileDts (/home/edoardo/cvat/node_modules/dts-bundle-generator/dist/compile-dts.js:35:20)

<w>     at generateDtsBundle (/home/edoardo/cvat/node_modules/dts-bundle-generator/dist/bundle-generator.js:27:43)

<w>     at e.<anonymous> (/home/edoardo/cvat/node_modules/bundle-declarations-webpack-plugin/lib/index.js:1:4697)

<w>     at /home/edoardo/cvat/node_modules/bundle-declarations-webpack-plugin/lib/index.js:1:2623

<w>     at Object.next (/home/edoardo/cvat/node_modules/bundle-declarations-webpack-plugin/lib/index.js:1:2728)

<w>     at a (/home/edoardo/cvat/node_modules/bundle-declarations-webpack-plugin/lib/index.js:1:1442)

<w>     at runMicrotasks (<anonymous>)

+ 2 hidden lines

WARNING in ../node_modules/ws/lib/buffer-util.js 113:23-44

Module not found: Error: Can't resolve 'bufferutil' in '/home/edoardo/cvat/node_modules/ws/lib'

 @ ../node_modules/ws/lib/websocket.js 31:21-45

 @ ../node_modules/ws/index.js 3:18-44

 @ ../node_modules/fabric/node_modules/jsdom/lib/jsdom/living/websockets/WebSocket-impl.js 7:18-31

 @ ../node_modules/fabric/node_modules/jsdom/lib/jsdom/browser/Window.js 21:22-83

 @ ../node_modules/fabric/node_modules/jsdom/lib/api.js 13:25-61

 @ ../node_modules/fabric/dist/fabric.js 24:14-30

 @ ./src/typescript/canvasView.ts 8:0-32 2661:18-38

 @ ./src/typescript/canvas.ts 9:0-46 24:20-34

WARNING in ../node_modules/ws/lib/validation.js 117:24-49

Module not found: Error: Can't resolve 'utf-8-validate' in '/home/edoardo/cvat/node_modules/ws/lib'

 @ ../node_modules/ws/lib/receiver.js 13:43-66

 @ ../node_modules/ws/index.js 7:21-46

 @ ../node_modules/fabric/node_modules/jsdom/lib/jsdom/living/websockets/WebSocket-impl.js 7:18-31

 @ ../node_modules/fabric/node_modules/jsdom/lib/jsdom/browser/Window.js 21:22-83

 @ ../node_modules/fabric/node_modules/jsdom/lib/api.js 13:25-61

 @ ../node_modules/fabric/dist/fabric.js 24:14-30

 @ ./src/typescript/canvasView.ts 8:0-32 2661:18-38

 @ ./src/typescript/canvas.ts 9:0-46 24:20-34

2 warnings have detailed information that is not shown.

Use 'stats.errorDetails: true' resp. '--stats-error-details' to show it.

ERROR in ../node_modules/canvas/build/Release/canvas.node 1:0

Module parse failed: Unexpected character '' (1:0)

You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders

(Source code omitted for this binary file)

 @ ../node_modules/canvas/lib/bindings.js 3:17-56

 @ ../node_modules/canvas/index.js 7:17-42

 @ ../node_modules/fabric/node_modules/jsdom/lib/jsdom/utils.js 154:2-27 160:17-34

 @ ../node_modules/fabric/dist/fabric.js 35:22-61

 @ ./src/typescript/canvasView.ts 8:0-32 2661:18-38

 @ ./src/typescript/canvas.ts 9:0-46 24:20-34

webpack 5.74.0 compiled with 1 error and 2 warnings in 103789 ms

error Command failed with exit code 1.

info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Steps to Reproduce (for bugs)

To reproduce the first error:

Download the git repo in ~/cvat
cd ~/cvat/cvat-canvas
yarn install
yarn run build

To reproduce the second error:

Download the git repo in ~/cvat
cd ~/cvat/cvat-canvas
yarn install
comment line 244 of ~/cvat/cvat-canvas/src/typescript/masksHandler.ts
yarn run build

Context

I was trying to build the canvas module alone to use the canvas elements defined by cvat itself in an external projects.
Your Environment

Git hash commit (git log -1):
develop 7df2b2fded320eef43166fc9689b9026bf0d45d3
master 2c4676ace32a68572b38205f002a98e93af917d0
Docker version docker version (e.g. Docker 17.0.05): building without docker.
Are you using Docker Swarm or Kubernetes? No
Operating System and version (e.g. Linux, Windows, MacOS): Ubuntu 22.04

@Dipsorum  Thank you for the report.


Does a user running build_visit need to download all this?

Examining a build_visit log in #5402, I happened to see that the invokation was...
./build_visit3_1_4 --thirdparty-path ./visit --makeflags -j4

and yet, it appears to have downloaded (I dunno if it also had to build), all this...
Downloading cmake-3.9.3.tar.gz . . .
Downloading openssl-1.0.2j.tar.gz . . .
Downloading Python-2.7.14.tgz . . .
Downloading qt-everywhere-src-5.10.1.tar.xz . . .
Downloading qwt-6.1.2.tar.bz2 . . .
Downloading VTK-8.1.0.tar.gz . . .
Downloading zlib-1.2.11.tar.xz . . .
Downloading Imaging-1.1.7.tar.gz . . .
Downloading setuptools-28.0.0.tar.gz . . .
Downloading Cython-0.25.2.tar.gz . . .
Downloading numpy-1.14.1.zip . . .
Downloading pyparsing-1.5.2.tar.gz . . .
Downloading requests-2.5.1.tar.gz . . .
Downloading seedme-python-client-v1.2.4.zip . . .
Downloading Python-3.7.7.tgz . . .
Downloading packaging-19.2.tar.gz . . .
Downloading setuptools-44.0.0.zip . . .
Downloading requests-2.22.0.tar.gz . . .
Downloading imagesize-1.1.0.tar.gz . . .
Downloading alabaster-0.7.12.tar.gz . . .
Downloading Babel-2.7.0.tar.gz . . .
Downloading snowballstemmer-2.0.0.tar.gz . . .
Downloading docutils-0.15.2.tar.gz . . .
Downloading Pygments-2.5.2.tar.gz . . .
Downloading Jinja2-2.10.3.tar.gz . . .
Downloading sphinxcontrib-qthelp-1.0.2.tar.gz . . .
Downloading sphinxcontrib-serializinghtml-1.1.3.tar.gz . . .
Downloading sphinxcontrib-htmlhelp-1.0.2.tar.gz . . .
Downloading sphinxcontrib-jsmath-1.0.1.tar.gz . . .
Downloading sphinxcontrib-devhelp-1.0.1.tar.gz . . .
Downloading sphinxcontrib-applehelp-1.0.1.tar.gz . . .
Downloading six-1.13.0.tar.gz . . .
Downloading pyparsing-2.4.6.tar.gz . . .
Downloading urllib3-1.25.7.tar.gz . . .
Downloading idna-2.8.tar.gz . . .
Downloading chardet-3.0.4.tar.gz . . .
Downloading certifi-2019.11.28.tar.gz . . .
Downloading pytz-2019.3.tar.gz . . .
Downloading MarkupSafe-1.1.1.tar.gz . . .
Downloading Sphinx-2.2.1.tar.gz . . .
Downloading sphinx_rtd_theme-0.4.3.tar.gz . . .

Does this make sense? It seems like a ton of this stuff is for developing VisIt and not needed to build VisIt simply to run it like any ordinary user might want.

If the user only wants to build visit, I think the better option is by hand with cmake and make.
build_visit imho is useful only when needing to build TP libs and to get a .cmake to point to them.
Also, there is --no-thirdparty option to build_visit which will turn off most TP libs (except required libs like qt, vtk, etc).

If the user only wants to build visit, I think the better option is by hand with cmake and make.
build_visit imho is useful only when needing to build TP libs and to get a .cmake to point to them.
Also, there is --no-thirdparty option to build_visit which will turn off most TP libs (except required libs like qt, vtk, etc).

If the user only wants to build visit, I think the better option is by hand with cmake and make.

Hmmm...They need to have the right CMake, the right Python, the right VTK, the right QT, right? I don't think building manually is best guidance for the average user. I get that build_visit feels like it gets in your way but for the average user, I think it is a way better option than manually, don't you?

build_visit imho is useful only when needing to build TP libs and to get a .cmake to point to them.
Also, there is --no-thirdparty option to build_visit which will turn off most TP libs (except required libs like qt, vtk, etc).

Forgot about that. That said, I would think the default behavior of build_visit would be to build a minimal VisIt for users ignoring anything developers might want and ignoring less common TPLs. Am I incorrect in the impression that was our goal, maybe in the distant past, and that we've maybe somehow unintentionally slipped away from that? Or, have we always kinda sorta been in the situation where build_visit defaults to a lot of stuff maybe user's don't need.

If the user only wants to build visit, I think the better option is by hand with cmake and make.

Hmmm...They need to have the right CMake, the right Python, the right VTK, the right QT, right? I don't think building manually is best guidance for the average user. I get that build_visit feels like it gets in your way but for the average user, I think it is a way better option than manually, don't you?

build_visit imho is useful only when needing to build TP libs and to get a .cmake to point to them.
Also, there is --no-thirdparty option to build_visit which will turn off most TP libs (except required libs like qt, vtk, etc).

Forgot about that. That said, I would think the default behavior of build_visit would be to build a minimal VisIt for users ignoring anything developers might want and ignoring less common TPLs. Am I incorrect in the impression that was our goal, maybe in the distant past, and that we've maybe somehow unintentionally slipped away from that? Or, have we always kinda sorta been in the situation where build_visit defaults to a lot of stuff maybe user's don't need.

The first 7 in the list are required. The libs from Imaging to seedme are libraries that go with Python. I don't think they take that much time to build. The remaining ones (from Python 3 down) are all for building our sphinx documentation. Those build pretty quickly, but they could be optional.
I agree that the default should be to do a minimal build. The other criteria is the likelihood of the build failing and those extra python libraries are pretty safe. I've never seen them fail. "--optional" turns on all the optional libraries that have a low likelihood of failure. There is actually quite a bit of information on build_visit in the users manual in the building visit chapter at the end of the users manual.

The first 7 in the list are required. The libs from Imaging to seedme are libraries that go with Python. I don't think they take that much time to build. The remaining ones (from Python 3 down) are all for building our sphinx documentation. Those build pretty quickly, but they could be optional.
I agree that the default should be to do a minimal build. The other criteria is the likelihood of the build failing and those extra python libraries are pretty safe. I've never seen them fail. "--optional" turns on all the optional libraries that have a low likelihood of failure.  So, I would expect that compared to Spack, we would look really good. By line count, we're not even 2x as good

😆 . So, I would expect that compared to Spack, we would look really good. By line count, we're not even 2x as good

Well the spack built doesn't even include all the sphinx stuff :-)

Well the spack built doesn't even include all the sphinx stuff :-)

We discussed this and decided that we should remove all the non-default python modules. We will need to make sure any scripts that call build_visit to add the stuff that is no longer done by default.


Consider extentions support on Android version？

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like, including relevant patches or source
A clear and concise description of what you want to happen.
Additional Notes
Add any other context or screenshots about the feature request here.

Duplicate


[bug] Model without system prompt fail

Hello,
When trying to benchmark google/gemma-2-9b-it i ran into an issue. It seems like guidellm uses [system](https://github.com/neuralmagic/guidellm/blob/f7947110ae1446ce765d6019cc4ab0a31d335923/src/guidellm/backend/openai.py#L109) message to sent request, which leads to
Template error: syntax error: System role not supported (in <string>:1)

I tried to change to user but this leads to pydantic validation errors. Trying to debug this but any pointers or help is appreciated.

Nope I worked from the fork i had and it worked, will confirm from main

Tested on commit works as well.


Cannot load underlying module for 'PKHUD'

when i get code from pod, import PKHUD error.version info:Installing PKHUD 4.2.3 (was 4.2.1)

sorry， i am clean projetc is ok，but why i am create new project will happen same error

I had the same issue. Run 'pod update' and update all your pods. That fixed it for me.


Integrating schema.description with docs?

Is there a way to populate the description column for each field in the automatically generated docs:

I have tried to use a custom schema like below without any success:
class Name(schema.String):
    description = 'Name for greeting'

def greet(name:Name):
    ...

Yup, that's intended but hasn't made it's way in yet.

How can  I add it manually?

@aidiss fork the repo and add it in manually, or make a PR to this library to add support for it

Is the intention to support description via custom schema as shown by @GeoTob or some other method?
Also, will e.g. default be able to be set and used in a similar manner?

I'm going to close this off, since we don't have the docs back in yet, but worth noting that the redesigned type system does support description=... on the validators, which we'll use to pull this info in, once we've got the redesigned docs going.


Cannot remove size attribute of .

Version
3.0.11
Reproduction link
https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICA8aW5wdXQgOnNpemU9XCJzaXplXCIgPlxuPC90ZW1wbGF0ZT5cblxuPHNjcmlwdD5cbmV4cG9ydCBkZWZhdWx0IHtcbiAgZGF0YSAoKSB7XG5cdFx0cmV0dXJuIHtcbiAgICAgIHNpemU6IG51bGwsXG4gICAgfSBcbiAgfSBcbn1cbjwvc2NyaXB0PiJ9
Steps to reproduce

Open the link.
Display error: Uncaught (in promise): Failed to set the 'size' property on 'HTMLInputElement': The value provided is 0, which is an invalid size.

What is expected?
Renders <input> without the size attribute because I specified null for the size.
What is actually happening?
An error will occur.

Even if undefined is given, an error will occur.

duplicate of https://github.com/vuejs/vue-next/issues/3294

Hi @edison1105.
That issue looked to me like <input: size="0"> issue.
This issue is <input: size ="null"> issue.
How do I remove the size attribute?

Is this what you want?
<template>
  <input ref="el" :size="size" >
</template>

<script>
export default {
  data () {
    return {
      size: 1,
    }
  },
  mounted(){
    this.$refs.el.setAttribute('size',1)
    this.$refs.el.removeAttribute('size')
  }
}
</script>

maybe we should remove the size attribute if it's set to null (like with other attributes)


Add execution_optimistic flag to responses

Overview
Adds an execution_optimistic: bool to the "metadata" of endpoints which might be "tainted" by an assumption about execution payload validity in an optimistic node.
This PR conflicts with the "Ethereum Beacon APIs" section of the optimistic sync spec. I propose that these changes should supersede the opt sync spec. That spec will need to be updated if this PR is merged.
I have not done a version bump (e.g., add a v2 and deprecate v1) for most endpoints. I am operating under the assumption that an optional field can be added to metadata without breaking the API. I'm interested to other opinions about bumping the version of all affected endpoints. I'm open to bumping all versions that's expected.
It should be mentioned that I'm not attached to this proposal, but I'm concerned that we're running out of time to standardise API behaviour with optimistic sync. I'm completely open to criticism and alternate proposals. I suggest reading the Optimistic Sync: HTTP API to understand the problem this PR is trying to address.
Notes
I've added help text for the execution_optimistic bool, but I'm not sure there's a way to view it from the UI. My Swagger skills are poor, perhaps someone could help understand how to access it or where to make that info more prominent.
When it comes to choosing if to set execution_optimsitic, I think clients should be free to return true whenever their head is optimistic. A lot of endpoints are based around an assumption about the head, for instance getting the block at slot 1 involves making an assumption about what the head is. Clients can also be free to set it on a more granular basis.

Shouldn't need to bump the version number - adding a field is backwards compatible.  And we do have precedent for that - we added dependent_root for duties without bumping the version number.

Shouldn't need to bump the version number - adding a field is backwards compatible.

this is only partially true: de-facto, clients have been strict on extra fields because adding a field may alter the semantic requirements of correctly handling the message - we've had cross-client compatibility problems with different parsing strictness requirements on this point. basically, this would mean that any existing versions of clients possibly will stop working, forcing an upgrade, when the new field is added, until the strictness is relaxed.
If we're going to start adding fields, we should also decide on a policy for where this is allowed, with which constraints and what "old" versions of clients should do when they encounter a field they do not understand: what happens for example if a field is added to a spec type (like BeaconBlock) that you didn't expect to be there? It seems trivial now, but with enough forks "out there" it will be hard to maintain compatibility.
Even the config endpoint, which is an "open experimentation ground" for random constants has seen exhibits strictness compatibility issues.

I would argue that metadata changes should not fall under the requirement of requiring a version bump.  One of the reasons we designed the API to return results under a data heading is to allow for additional fields at the top level without disrupting the data itself.  An optimistic-sync-unaware client should be able to continue with this change without any alteration in its behavior.

One of the reasons we designed

This is a useful distinction, and if this is the way to go, we should make it explicit so that clients can design compatible data validation routines.

This is a useful distinction, and if this is the way to go, we should make it explicit so that clients can design compatible data validation routines (and appropriately scope future additions to such "optional" fields)

Totally agree with that, unfortunately there are various pieces of the API that are still way too much implicit rather than clearly stated anywhere.  I'll see if I put together a PR to make this clear in the appropriate place in the spec.

checking in on this -- There seem to be two things under discussion

the use of execution_optimistic
how to extend the spec with additional optional data

Are we blocked on (1) until a subsequent PR for (2)
Or can we move forward tackling (1) here and now

Are we blocked on (1) until a subsequent PR for (2)

IMO we should move ahead with discussing execution_optimsitic regardless if we need to bump API versions or not. It's an important enough change to warrant a version bump if need be.

I'm looking for some help on getting CI passing :pray: @mpetrunic, perhaps you are familiar with the error I'm getting?

What does the block/state ID head mean during optimistic sync? Should it mean the optimistic head or the fully verified ancestor? I think given we're exposing optimistic data now I'd say it should be the optimistic head but we should make that clear.
Currently it's defined as "head" (canonical head in node's view)

@paulhauner could you check "Allow edits from maintainers" or rebase latest master to fix ci 😄

@paulhauner could you check "Allow edits from maintainers" or rebase latest master to fix ci smile

Unfortunately I can't allow edits, the checkbox is missing.
I did rebase on master, but that doesn't seem to have helped much sorry.

@paulhauner looked closely and it seems you have some wrong refs :)

Is this good to merge now?  Would be good to have the API locked down as much as possible before kiln is released.

Sorry for the late idea, but one thing that makes the transition period easier here would be that the field is only added after the client has transitioned into the merge epoch - this allows existing mainnet and testnets to not be affected by the change until the upgrade has happened and the field becomes relevant.
This is a better approach compatibility-wise because the hard fork guarantees that only updated clients access the api:s this way - thoughts?

Sorry for the late idea, but one thing that makes the transition period easier here would be that the field is only added after the client has transitioned into the merge epoch - this allows existing mainnet and testnets to not be affected by the change until the upgrade has happened and the field becomes relevant.

This is doable but does make things more complex than I'd ideally like and means that any incompatibility is only discovered when Bellatrix is enabled.
Currently Teku is setup to only add the field if Bellatrix is enabled for a network (ie the fork epoch is not FAR_FUTURE_EPOCH) which has a similar effect of delaying the appearance of the field to give people time to ensure compatibility, just with a condition that doesn't change without a restart so makes things a bit easier. By the time we set a fork epoch for MainNet people will have had plenty of time to update so the new field is handled safely, but it's not so late as to be caught up in the actual fork activation.


Suggestion - Open Discussions for asking questions

It'd be convenient to be able to open discussions for asking questions
I can ask them on Slack, but they'll disappear, and Discussions add more visibility to the questions

I've never used Github discussions before, but it does seem like a good tool for a little stack exchange for catlab. I bet my students would populate it with Q&A while working on their projects. @epatters any objection to enabling GH discussions on here?
@VarLad, there is also the catlab stream in the julia zulip, which is more permanent and also organized into threads.

I've never used GitHub Discussions but it seems like a promising feature, so let's see how it goes! I've turned it on.

Also, I'd like to contribute a small tutorial to the docs Need some help on it though I'm stuck on how to use Catlab.Syntax.functors for substitution
Catlab could really use some better docs and some tutorials

Any contributions along these lines would be very welcome. Thank you!
It is worth mentioning that Catlab does have additional materials that can serve as docs scattered across different places, especially the AlgbebraicJulia blog. @TheCedarPrince may be helping us organize these materials in a more coherent and accessible way.

@VarLad - we can connect more on this later.
Let's discuss on Zulip. :)


Compile crate with stable rust

Currently we have to use the nightly distribution of rust because we need some unstable features.
Nightly features we use:

[ ] slice_ptr_get
[ ] strict_provenance
[ ] hasher_prefixfree_extras

After removing all unstable features (or they get promoted to stable) we should expand the github actions matrix to run all the build and tests for multiple version of rust: nightly, beta, stable, and a pegged MSRV.

Additionally we're maintaining local copies of unstable methods behind the following features:

[ ] nonnull_slice_from_raw_parts
[ ] maybe_uninit_slice
[ ] maybe_uninit_uninit_array

I've subscribed to all 6 of these issues, so I should know if one moves to stable, in which case we can remove the local copy and use stdlib.

The crate now compiles with the stable version of rust, and there is also a nightly cargo feature to opt the internal back in to using nightly features.
See https://github.com/declanvk/blart/actions/runs/3512050106/jobs/5883375643 for an example of compile and testing with stable rust.


Add link to contract variation page to framework dashboard

If a supplier has returned their framework agreement then their documents page will show a link to any proposed contract variations.
Words agreed with Cath and Laurence.
Looks like this:

👍


Doc improvement : provide inventory sample without postgres Host groups

In order to disable the external postgres I had to remove and comment specific lines in the default/example inventory file.
People with limited knowledge of ansible might struggle to do it.
It would be nice so provide an inventory sample without postgres Host groups as it corresponds to deployment with internal postgres (which is likely the most common choice).
Thanks

Yeah I think we need a sample file for internal postgres.


Publish button isn't working

Publish button is not publishing the post. It isn't working on your demo website also.

What browser and version?

5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/601.7.7 (KHTML, like Gecko) Version/9.1.2 Safari/601.7.7

Ahhh looks like all Apple browsers then, I just posted this:  https://github.com/kenny-hibino/stories/issues/28


Add a link to the cheat sheet in Learn

This adds a link to the Pony Cheat Sheet on the Learn page so that
beginners can find the cheat sheet and start to use it to help them
learn.

Thoughts on hosting the cheat sheet on ponylang.org @aturley ? If you are comfortable with that, I'd rather do that.

Sure, I can do that.

@SeanTAllen added.

Thanks!


DX: lint-staged doesn't run on json files

Describe the bug
lint-staged doesn't run on json files
To Reproduce

Create a new json file, not nicely formatted
Commit it
It gets committed without formatting

Additional context
need to add json to lint-staged

thanks to @gpoliko for fixing this!


Add back GSProcessing EMR on EC2 guide for launching properly configured cluster and launch through spark-submit

https://github.com/awslabs/graphstorm/pull/902  will simplify our instructions for how to use GSProcessing on EMR-EC2.
Advanced users might still want to launch and configure their own clusters though

Is this done now @jalencato ?


Add Repo Maintainers to CODEOWNERS file

Update CODEOWNERS to provide maintainers ownership of all files in their repos
Description:
Update this repositories .github/CODEOWNER file to ensure that the repository maintainer
group(s) have full control of the files in this repository.

There is a CODEOWNERS in .github folder; however it is already configured.


HHH-13704 Makes Javassist optional

HHH-13704
Follows: https://github.com/hibernate/hibernate-orm/pull/3094
Now javassist is only needed when you want to use it as Bytecode provider.
I've cleaned up the changes I made before and added an integration test to check the module on WildFly.
@Sanne I checked and the existing test suite calls the part of the code in ORM that I've updated.

I would like to remove javassist from the hibernate-core jboss module as well but I couldn't find a way to make the tests work otherwise. I think it's fine for now and we could work to remove javassist in ORM 6 as soon as possible.

@Sanne I think I've fixed all the issue

@Sanne @DavideD I do not think this change can be applied to a minor release, it will break app using javassist for enhancement

@Sanne @DavideD I do not think this change can be applied to a minor release, it will break app using javassist for enhancement

It makes sense. I will let you gyu decide when to include it, ping me when you need it rebased

Thanks to @dreab8, I think we  fixed the problem with the build. The build was failing because karaf has a transitive dependency to Javassit. Add ing the bundle to the OSGi test solved the issue.

@dreab8 maybe update the issue to Fix version: 5.5.0

thanks the OSGi tests seem fixed now.
@DavideD no we're not planning a 5.5 release. Let's adapt this to make it better suited for 5.4, proposal:
I'd like to take the changes as, with one exception: Javassist still listed as an actual runtime dependency in the produced pom files.

We know this code works in case of an exclusion
We could keep the nice tests to proctect from regressionsby having an exclusion during the integration tests?
I can add an exclusion in the Quarkus pom...
marking the module dependency as "optional" is a change we can keep: Wildfly can choose to keep the module if they prefer.

WDYT? I'm going to needs this as it's a blocker for:

https://github.com/quarkusio/quarkus/issues/6020#issue-534537964

@Sanne I'm checking if it's doable

I've added a commit making Javassist a compile dependency again.  We should create an issue to revert the commit for the next Minor release.

merged! thanks all


Crash with new Tough As Nails Version

Crashes with new version of Tough as nails version-1.9.4-1.1.1
http://pastebin.com/eLUJYk5L
Cyberware version-1.9.4-1.10.2-beta-0.2.6

i got this aswell when i went to see if tough as nails would be good for my pack

Indeed TAN updated their API which you need to update!

Same problem, would you please update the integration thing, that would be awesome.

Just adding my voice to prioritize this request. Cyberware would be a great addition to the Forever Stranded pack. It is getting a lot of exposure at the moment. GWSheridan is the OP of this issue so apparently he was considering this inclusion.

Im also encountering this issue.

https://puu.sh/vchH4/ded4466d44.txt issue still occuring...would seem a downgrade is in order for TAN an Cyberware to work together

I fixed this in the 1.11.2 version, just FYI.

So this is not being fixed in 1.10?

Should have been fixed in the newest 1.10 update that came out about a week and a half ago

I can load a server and client instance with TAN & cyberware present


Fixed #30418 -- Added --skip-checks argument to management commands.

https://code.djangoproject.com/ticket/30418

Thanks Jon!


Rewrite copy/paste to move away from system clipboard

As discussed in https://github.com/excalidraw/excalidraw/issues/254 there are several issues with current implementation, which uses system clipboard:

Various permission issues & support issues, which may be behind all the reports: https://github.com/excalidraw/excalidraw/issues/382 https://github.com/excalidraw/excalidraw/issues/359 https://github.com/excalidraw/excalidraw/issues/249
For example, on my system (win7) in Chromium-based browsers, paste doesn't work by default (for first access) and gives no indication of what action needs to be taken. I need to paste using contextMenu which only then shows a permission prompt. Lately, I also need to refresh afterwards before the paste starts to work:

(also note that in the above GIF, what was actually pasted is some different clipboard from different scene, since it appears the copy didn't initially work, either).

Current solution overrides system clipboard with element JSON data (and potentially overrides whatever was presently in system clipboard).

If we move to in-app implementation (listening on Cmd/Ctrl+C/V), the above problems should disappear.
@vjeux also noted that one goal of current implementation is the ability to paste across different browser tabs. This can be solved by propagating the clipboard state using localStorage, which all tabs of the same domain share. On this note, since we're already storing scene state to localStorage, all tabs are being eventually synchronized, so cross-tab pasting doesn't make sense at this time, anyway.

@0x11-lgtm do you have any experience with copying image/svg+xml to clipboard? It seems that Async Clipboard API doesn't support it yet (even though it's specced). Can't get it to work with sync Clipboard API. It's supposedly working for execCommand, but that I reckon would work only for actual svg images.


Something for Nothing

No description provided.

Yeah, author, something wrong with your description. I guess pictures are missing.


Safety switch not changing its state

my system
pixhawk 2.1
px4 version : 1.8
gps+compass+safety switch is connected in GPS1 port of pixhawk 2.1
Issue : The safety switch doesn't changes its state to arm state. No console output .
how to debug this stuff.

Can you check the circuit breaker parameters?
To debug start with listener safety via nsh.

I ran a test on a 2.1 cube
flashed 1.8.0 stable and then current master
both look to be engaging the safety switch properly

@shabhu18 what are the leds on the GPS module doing?

i get the following if i so listener safety
TOPIC: safety instance 0 #1
safety_s
timestamp: 361180857 (0.021590 seconds ago)
safety_switch_available: 1
safety_off: 0
override_available: 0
override_enabled: 0
The state doesn't change even if i change safety switch for a while.
meanwhile on QGC i get the following
[11:08:11 522] Emergency: Mag 0 fail : Timeout
[11.08.25 512] critcal: PREFLIGHT FAIL :MAG SENSOR INCONSTANT

given mag 0 is giving error,s it might be a problem with the connector or GPS module... does the gps portion work properly?

I disabled the safety switch in software it worked .


Module 1.2 Assignment

$ mkdir campus-advisor-training
$ cd campus-advisor-training
$ git init
$ touch README.md
$ git status
On branch master

No commits yet

Untracked files:
  (use "git add <file>..." to include in what will be committed)
        README.md

nothing added to commit but untracked files present (use "git add" to track)

$ git add .
$ git status
On branch master

No commits yet

Changes to be committed:
  (use "git rm --cached <file>..." to unstage)
        new file:   README.md

$ git commit -m "Add README.md"
[master (root-commit) b96ab1e] Add README.md
 1 file changed, 0 insertions(+), 0 deletions(-)
 create mode 100644 README.md

$ git status
On branch master
nothing to commit, working tree clean

$ git log
commit b96ab1e4f418b80b23013adce1a372695a2684a8 (HEAD -> master)
Author: Daiji Fukagawa<EMAIL_ADDRESS>Date:   Sun Oct 6 10:44:15 2019 +0900

    Add README.md


How do I edit the code once it's encrypted?

Hi,
PageCrypt does not currently have the functionality to edit code after encryption. To modify your code, you will need to edit your original HTML file and then run it through PageCrypt again.
Regards,
-Max


Cursor | issues

I'm not able to see the cursor like "|" when I back press then first press miss out, second press is show bar (_) cursor

I'm not sure I understand the issue. Could you provide clear steps to reproduce?


requireNewlineBeforeBlockStatements is not working with 'switch'

Why requireNewlineBeforeBlockStatements option does not accept switch statement?

It totally should, would you like to implement it?

@markelog ok, I will try. What about to write nice work, bro mentioning me on twitter when you will close PR? JFF :)

We didn't do it before, but i don't see a reason why we can't :-)

@markelog oh, switch's body in AST is defined not even like class's body. It doesn't have a child node that will include braces, so we can't add switch support by adding 2-3 words to source code :).
I have added switch support by special check:
https://github.com/PaulAnnekov/node-jscs/commit/0ce22181f51af82cf30916592d9076d78bcde12e
https://github.com/PaulAnnekov/node-jscs/commit/b717058d017825b37f5cdc81085b2f8404b3739c
It is OK or maybe we should create separate rule for it because now it looks like exceptional case in sources?

It is OK

I'd say yes, but we need to structure it with low cyclomatic complexity


Electronic shop problem - C# based solution

Added a solution for electronic shop problem, https://www.hackerrank.com/challenges/electronics-shop/problem. I've created it in C# .Net.

I've created a new pull request #45 for updating readme.md file

It looks like your readme links are for Solution.cs while #43 and #44 are solution.cs. I will merge your pulls then fix this.


Definition of "random" for audit

Audit group recommends that the random audit be determined before the 'strategic'/'interesting' audit.

A. How do we determine the scope of random audit. E.g., do we randomly select (1) a submitting organization and then random a submission by the submitter, (2) a submission, (3) a unique HW/SW combo, or (4) a member of the review committee.
B. Audit group suspects that some submissions may use HW/SW components where the owner of the HW/SW component is not submitting. E.g., Google is not submitting for inference v0.7, but someone rents a TPU to submit. Audit group also expects that some submitters (e.g., OEMs/cloud providers) may submit systems using a variety of 1st and 3rd party components (e.g., GPU, CPU, TPU).

Audit group recommmends the following randomization:

Random pool is each unique submitter.
Randomly select a submitter from the pool and then randomly select a submission by the submitter.
Randomization to be performed by David Kanter using a RNG.

added to rules


Update GEF API use to latest version

This will be merged as soon as GEF PR: https://github.com/hugsy/gef/pull/796 is merged for related API problems.


Changing SQL backend to mssql from sqlite3

OS: Windows 7 32-bit
<EMAIL_ADDRESS><EMAIL_ADDRESS>I was able to change the backend from sqlite3 to mssql, my knexfile.js looks like this:
// Since Knex always runs this file first, all of our seeds and migrations are babelified.
require('babel-register');

module.exports = {
  development: {
    client: 'mssql',
    connection: {
      host : 'server',
      user : 'userName',
      password : 'P@$$w0rd',
      database : 'dbname'
    },
    useNullAsDefault: true,
  },
};

and changed seed.js#L87-L88 to:
        created_at: new Date(Date.now() - i * 10000).toISOString(),
        updated_at: new Date(Date.now() - i * 10000).toISOString(),

However, on seed.js#L91  I get an error:
      }).then(([id]) => { // <= here
        repoIds[repository_name] = id;
      });
    }));

I have narrowed it down to mssql returning null values, on the other hand, sqlite3 returns the row id (I think).
Any ideas? I am currently researching if there is a way to change mssql behaviour but have not found anything so far.

Update
I got it. To solve this issue, I added .returning('id') on seed.js#86
      return knex('entries').returning('id').insert({

I found some other issues which are out of the scope of conversation, like:
With my modification to the create_at and updated_at insertion make it ivalid format for graphql type TypeError: Float cannot represent non numeric value: 2016-09-23T17:02:47.319Z.
There are other issues with some queries that are invalid for MSSQL dbs. e.g. RequestError: select top (@p0) [entries].*, SUM(votes.vote_value) as score from [entries] left join [votes] on [entries].[id] = [votes].[entry_id] group by [entries].[id] order by [score] desc - Column 'entries.created_at' is invalid in the select list because it is not contained in either an aggregate function or the GROUP BY clause.
But, that is something to look into later.
Will be closing this issue now.

Yeah, unfortunately it's not possible with knex to just transparently switch the backing DB. You'd figure that since it's an abstraction on top of any SQL DB it would do that, but it doesn't...

I may look further into this or maybe explore using sequelize since it is being used succesfully on the apollo-tutorial-kit.
I think the complexity of the queries on the apollo-tutorial-kit is lower compared to GitHunt-API, so I do not know what issues I may encounter if I give it a go.
Thanks for your reply.

@aaroncalderon if you can migrate this repository to Sequelize, I'd be very thankful!

Coincidentally I have been running it in PostgreSQL and thought I'd leave me feeback here for anyone interested.

Add .returning("id") to the insert statements (even the migrations file).
Dates are a problem.  Likewise I was disappointed knex didn't do the translation properly.  My solution was to use "whereRaw" i.e:
.whereRaw('updated_at > now()- interval '1 hour'')
IMO if it's not going to be abstracted properly better to be obviously and clearly not portable.
And:
.insert({
created_at: 'now()',
updated_at: 'now()',
Label the count in getCommentCount:
.count('id as CNT');
return query.then(rows => rows.map(row => (row['CNT'] || '0')));

Otherwise pretty painless to get it working with postgres.
Thanks for the great demo app :)

Thanks! Yeah it's frustrating that knex doesn't handle the differences, but I guess it makes sense since it's just a query builder. If anyone wants to send a PR to move to a more fully featured ORM that could be great.


cimg: 2.9.2 -> 2.9.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/cimg/versions.
meta.description for cimg is: "A small, open source, C++ toolkit for image processing"
meta.homepage for cimg is: "http://cimg.eu/"
meta.changelog for cimg is: ""
Updates performed

Version update

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 2.9.3 with grep in /nix/store/a5qv1i553rr1zy1ndbxqxj4ba0z8kl2g-cimg-2.9.3

directory tree listing: https://gist.github.com/404fc516d3c7d10f2ac35654775ddd93

du listing: https://gist.github.com/fe11d794ac4b9fae742b5d17e1a1ed7f

Rebuild report (if merged into master) (click to expand)

11 total rebuild path(s)

3 package rebuild(s)

3 x86_64-linux rebuild(s)
3 i686-linux rebuild(s)
2 x86_64-darwin rebuild(s)
3 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
cimg
phash
wxcam

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/a5qv1i553rr1zy1ndbxqxj4ba0z8kl2g-cimg-2.9.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A cimg https://github.com/r-ryantm/nixpkgs/archive/88aedac5d34990bac0c3ebe4515b547e744e34fb.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/a5qv1i553rr1zy1ndbxqxj4ba0z8kl2g-cimg-2.9.3
ls -la /nix/store/a5qv1i553rr1zy1ndbxqxj4ba0z8kl2g-cimg-2.9.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review 1

3 packages built:

cimg
phash
wxcam

Maintainer pings
cc @AndersonTorres for testing.

LGTM


feat: adding InitChannel util function

Description
Adding a helper function to open a new channel in the case that a channel closes. This is necessary so that a controller chain can regain access to an ICA.
closes: #509

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against correct branch (see CONTRIBUTING.md)
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Code follows the module structure standards.
[ ] Wrote unit and integration tests
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added relevant godoc comments.
[ ] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[ ] Re-reviewed Files changed in the Github PR explorer
[ ] Review Codecov Report in the comment section below once CI passes

Codecov Report

Merging #534 (48f61cd) into interchain-accounts (3ff5bf8) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@                   Coverage Diff                   @@
##           interchain-accounts     #534      +/-   ##
=======================================================
+ Coverage                79.10%   79.11%   +0.01%
=======================================================
  Files                      134      134
  Lines                    10347    10354       +7
=======================================================
+ Hits                      8185     8192       +7
  Misses                    1753     1753
  Partials                   409      409

Impacted Files
Coverage Δ

...ules/apps/27-interchain-accounts/keeper/account.go
83.78% <100.00%> (+3.78%)
:arrow_up:

@AdityaSripal @colin-axner @damiannolan I'm actually questioning now if this is even necessary at all and maybe should be removed from the spec as well.
In the case that a channel closes, an ICA-auth module could just call the OnChanOpenInit function directly I imagine. Or just use a relayer to re-open a channel. Although perhaps this util will make things a bit easier.

Hmm it seems like the way you have it here is the cleanest option.
If you want to reopen the channel directly, you could do
icaKeeper.channelKeeper.ChanOpenInit(...)
// callback doesn't get called by channelKeeper's ChanOpenInit function
// it gets called by the msg server
icaModule.OnChanOpenInit(...)

But sending the message to IBC's msgserver, just abstracts the above lines for you since that is basically what the message server does. And it seems like easier maintanence to me, if core IBC ever refactors its message handling, then you don't have to reimplement the channel msg server function within ICA

@seantking I also question whether we need this. My hesitancy is that we don't fully understand when this might be needed. If the function is just creating a MsgChannelOpenInit then I wonder if it is best to let the caller handle this complexity (since it isn't very much). I don't have a preference though

Not sure if this is feasible, but would there be any way of using the InitInterchainAccount for this use case as well? Maybe the function needs to be renamed to something else more descriptive, but if we have only one function to initialize the interchain account whether the channel is open or not, then I guess the API is simplified for the user. For example, if the channel is closed and the caller calls InitInterchainAccount again (assuming with the same arguments as for the first time it was invoked), then you skip the port binding and do only the opening of the channel.

One point of consideration is that this change could be released in a minor release. Perhaps it is best to not add it for now and add it later if it becomes desirable? Relayers could always just send the MsgChanOpenInit themselves?

Closing this for the time being as we are deciding to leave this out of the API for the time being. @AdityaSripal We may want to remove this from the spec if we decide to leave it out of the release.


Install issue: To connect the Docker client to the Docker daemon, please set:

Hi,
I saw his issue
To connect the Docker client to the Docker daemon, please set:
    export DOCKER_HOST=tcp://<IP_ADDRESS>:2376
    export DOCKER_CERT_PATH=/Users/pascalandy/.docker/machine/machines/dinghy
    export DOCKER_TLS_VERIFY=1
    export DOCKER_MACHINE_NAME=dinghy

I read to FAQ. Ran docker-machine regenerate-certs dinghy
but I still have the issue dinghy status
VM: running
NFS: running
FSEV: running
DNS: running
HTTP: stopped

To connect the Docker client to the Docker daemon, please set:
    export DOCKER_HOST=tcp://<IP_ADDRESS>:2376
    export DOCKER_CERT_PATH=/Users/pascalandy/.docker/machine/machines/dinghy
    export DOCKER_TLS_VERIFY=1
    export DOCKER_MACHINE_NAME=dinghy

It would be great to know how to set those values :)

Try running eval $(docker-machine env dinghy) in your terminal

YES!!
Via $(dinghy shellinit) it worked. Please add this in the FAQ :)
Cheers!

Hm yeah this does assume some familiarity with shell env vars. We should tweak the "please set" message to make it clear.

Let's just change the help message to something more like docker-machine env:
Run this command to configure your shell:
eval $(dinghy env)

done on master in https://github.com/codekitchen/dinghy/commit/9032c1c80f7e6df2f0755dd1d8180beec5404cdf

:+1:


java.lang.NoClassDefFoundError

When I launched a small missile and it landed, the server crashed with this crash log:
http://pastebin.com/1y41pdP9

Looks like it was running client only code on the server. I should have time to fix the issue later this week once I'm done with finals.

Just to save you the troulbe of tracking it down, at the bottom of com/builtbroken/icbm/content/blast/effect/BlastEnderBlocks.java, you had an if statement that checked if world.isRemote is false. If world.isRemote is false, then it's a server world.

You mean https://github.com/BuiltBrokenModding/ICBM/blob/development/src/main/java/com/builtbroken/icbm/content/blast/effect/BlastEnderBlocks.java#L174
Right after you reported the bug I already looked at that line. There is nothing on that line, the entire class, or the packet it calls that should cause the issue. Which means I have to look into it more and most likely do some debug. Which I will get to tomorrow evening or Thursday as I will be done with my exams.

Isn't that the file I sent you?
Anyway, remove the '!' and it should be fixed, because isRemote is true only for client worlds.

!world.isRemote is the correct usage as I'm ensuring the code runs server side. That line generates a network packet that is sent to the client. Then the client itself renders the particle effect. If the packet is fired client side it will not work as the client does not contain the blast data to render the effect.
The bug is not happening in the class itself but is being caused by a class loaded during that method call. Most likely it is actually https://github.com/BuiltBrokenModding/VoltzEngine/blob/development/src/main/scala/com/builtbroken/mc/core/network/packet/PacketSpawnParticleStream.java#L60 which is calling a client-side only method. The class loader may be loading the EntityFx.class because of the World.class references it in that method.
You may be getting confused by the method name which notes to render effects for the blast. However, this method is only called server side and depends on the blast to sync with the client on it's own. It was originally fired on both sides when the blasts calculated on both the client and server. However, because of client ram issues the blasts only run on the server and then update the client as needed.

Oh, sorry.

Ok I just tested the issue and spotted the problem. I was looking at the wrong class and this is the actual packet class that was being used https://github.com/BuiltBrokenModding/VoltzEngine/blob/development/src/main/scala/com/builtbroken/mc/core/network/packet/PacketSpawnStream.java#L130
It references EntityFx code right on that line and the if statement bellow.


Option to buy assets (crypto) using fiat or depositing BTC should be on top menu too

Hi,
I see a lot of people that don't know yet that is possible to buy RBTC with fiat or depositing BTC because it's hard to find it. I think the option to buy assets (crypto) using fiat or depositing BTC should be on top menu too. In my opinion the option to buy with fiat, should allow not only RBTC but the other assets listed on Sovryn too.
Something like Binance page:

Related to: https://github.com/DistributedCollective/Sovryn-frontend/issues/492

Yes I agree with you this would be a good place to host this. I don't know when it will be possible to buy other assets with fiat too.


.Net: Add an APIM Concept sample

Can recommend people use this resource: https://jordanbeandev.com/how-to-set-up-an-asp-net-core-api-to-call-an-azure-openai-instance-that-is-behind-azure-api-management-and-requires-both-a-subscription-key-an-oauth2-access-token-using-semantic-kernel-c/


BUG: Empty card Allignment

When our cart is empty then it show empty cart but it show in left side instead of middle.

@harshit1142 Please review it and merge accordingly and assign to me under gssoc-ext, hacktoberfest-accepted, with level-2.

Please also assign the labels of  gssoc-ext, hacktoberfest-accepted


Invoking a topic each time a vow is run.

We're running into the issue concerning the fact that the topic is only run once per vow. Having it run before each vow is pretty useful, for example reseting state after a vow is run.
I'm quite happy to submit a pull request for this, but I thought I'd first check to see if it's something that's likely to get in - or if this behavior is an intentional architectural decision.

This seems complicated. Is the idea that the tests are mutating the topic?


Orientdb Studio: Index permissions

OrientDB Version: 2.2.22
Java Version: 1.8
OS: centos
Expected behavior
User should not be able to drop or recreate indexes if he has access to only database, database.command read resources
Actual behavior
User is able to drop and recreate indexes
Steps to reproduce
Create a new user with a role having database, database.command read resources
If we are dropping indexes with an user with insufficient permissions in distributed environment then only indexes in the node to which we are connected are getting deleted. But if user with correct permissions drops an index it gets dropped across all nodes.

@laa Can you please help us with the above issue? We are planning to use orientdb in prod and we are stuck on this as an user with restricted permissions can do query like drop index which is unwanted.

@dinakarreddy sorry I am responsible for very low-level stuff, but my colleagues will help you.

Thank you @laa


chef vault haproxy stats secret

Include:

Find all chef vault resources that will deploy on a node
grant the node access to the vault items
vault haproxy stats password

Please explain the process on how clients are found for Chef Vault. Also, please modify and test for Kafka clusters.

How long does FindResources.rb run? Can it be commented a bit more thoroughly; it requires a bit of in-depth reading today?

To be pedantic about the ruby file names, I see that its lower_case_with_underscore_between_words as opposed to CamelCase. It'd be good to have naming uniformity with what is generally used/acceptable.

find_resources.rb does not run longer than a minutes, several seconds something.
find_resources.rb will leverage Chef API to find chef vault resources running on a specified node, and return the chef vault resource ID and its data bag.
Node_auth.rb takes the data bag name and resource ID from find_resources.rb and the node needing to grant access to the vault item, and add the node key to the vault item.
Those two scripts will be called during cluster-assign-roles.rb after install_stub() to check chef vault resources on each node being cheffed and add the node key to vault items for accessing them in recipes.

I can say this builds successfully.  How can I verify that the built cluster is working?

You can check if my added feature working by "knife data bag show os haproxy-stats_keys". Then you should see all the nodes which need access to haproxy-stats password over there. That means my feature successfully grants those nodes the access to that vault item.

Ray, could you provide some example outputs and cases to cause them from find_resources.rb?

Merged into chef-back master locally and ran cluster-assign-role, without an issue.  Will do further testing

Thanks

Built from scratch everything looks good


Integrate CI for running benchmarks

Summary:
I have used Criterion benchmarks to check performance degradation and iai-callgrind to check increment in build time
https://github.com/marketplace/actions/criterion-compare-prs Criterion benchmarks comparision
https://lib.rs/crates/iai-callgrind iai-callgrind benchmarks
Check this pr for implementation of the changes https://github.com/alankritdabral/tailcall/pull/16#issue-1989326231
Issue Reference(s):
Fixes #436
Build & Testing:

[x] I ran cargo test successfully.
[x] I have run ./lint.sh --mode=fix to fix all linting issues raised by ./lint.sh --mode=check.

Checklist:

[x] I have added relevant unit & integration tests.
[x] I have updated the documentation accordingly (if applicable).
[x] I have performed a self-review of my own code.

/claim #436

I will be closing this Pr i have a different and simple way @tusharmath
but when comparing criterion benchmarks what should i keep the  criteria for degradation (keeping in mind all thee vaalues we have aree in nano seconds unit )
for build time it is 10%
and should i only print criterion benchmarks on Pr like a codecov report


Fix fuse-timeout in README.md

Sorry, I didn't notice this one existed until after the other PR was merged.

I think the proper edit would also change cursor to a-gui-cursor, so I'm closing this.


fix: transit-advanced - wrong duration value

Concerned demo: transit-advanced
Issue: duration value was interpreted like minutes instead of seconds
Fix: convert seconds into minutes

:tada: This PR is included in version 1.29.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Conflicts between typings exposed globally

TypeScript Version:  2.7.0-dev.201xxxxx

Search Terms:
cypress; beforeEach; global conflict; duplicate identifier
Code
Reproduction repo
Expected behavior:
To be able to use Cypress and Jest in the same project without explicitly specifying which @types packages to use.
Actual behavior:
See README in a repo
Related Issues:
https://github.com/cypress-io/cypress/issues/1087
As you can see in a linked issue, there were some workarounds suggested, but I am not happy about any of them. Setting skipLibCheck because of inclusion of a test framework feels mega dirty.
Specifying what @types/* packages to use is not a good DX imo. I already have these listed in my project and I am sure it will grow over time. Worst part is it's not always easy to find which package needs to be included there.
"types": ["node", "react", "jest", "debug", "googlemaps", "markerclustererplus"],

Possible solution
I think it might be worth to expand configuration of types to have a include/exclude variant. That way I could exclude mocha typings instead of listing everything I need to include. Also if I would want to write Cypress tests with TypeScript, I would be able to extend root tsconfig a include mocha there instead.

The issue here is caused by the declaration files defining the same global functions. this can be remedied by either 1. both defining them the same exact type, 2. refactoring the declaration files to be modules instead of global declarations, or 3. by refactoring the declaration files to have a third common package both packages depend on and have the shared declarations.

Hey, so you say this not something that can be fixed on TypeScript side? And what about my suggestion? Seeing a number of thumbs here I would say I am not the only one bothered by this. Why forcing the solution to the userland when there is such an easy fix?

Two different test frameworks, not really possible to force either one of them to use exact same type as other
I am not sure it can work in this case since there are global functions and you don't generally want to have imports in your tests
I cannot imagine how that would work and it feels a rather weird coupling together two different test frameworks.

I think it might be worth to expand configuration of types to have a include/exclude variant.

you already have types which is a list. i do not expect the list of your @types package to be that large, that you can not enumerate them all modulo mocha in the "types" property in your tsconfig.json.

@mhegazy Well, it certainly is possible but is it a good DX? I mean why not give another option that makes things easier and does not break anything?

I am not arguing there is value. The question is the cost of adding a new feature both in terms of complexity to new users, and in terms of maintenance cost vs the value added. I would argue the real issue is the declaration of  mocha and jest.

Well, they are both testing frameworks relying on globals (sadly). It's not really something that can be changed without a breaking change.
The complexity you mention is optional, the types config field can accept either array or object with include/exclude properties. For most people who are not solving this issue, it won't matter that this option is in there.

@mhegazy Can you please reconsider?

@FredyC did you end up with a workaround?

@kelly-tock The workaround is obvious since there is no exclude option, you have to do the opposite.
@mhegazy I don't understand why is to difficult for you to even talk about it. You did admit there is some value in it, so why to cut off discussion suddenly?

@FredyC The issue isn't locked. Maintainers are still reading the issue tracker.

@RyanCavanaugh I know it's not locked issue, but closed ones don't get much of the attention either :(

I have the same problem, and I don't even know which types to list in my tsconfig.json.
I was already listing "chrome" because I'm using some chrome APIs.
Any suggestions on how to find the list of types my project is using?

Any suggestions on how to find the list of types my project is using?

--traceResolution

Is there is any update? Issuing the same problem

I am afraid until this stays closed, it will never get any attention despite what @RyanCavanaugh said before.

@FredyC found an interesting solution though - here https://github.com/nrwl/nx/issues/816
@/FrozenPandaz What about the workaround of adding import 'jest'; to test-setup.ts? I seems to do the job and I haven't seen any side effects.

Feels kinda far fetched. I've opted for a much simple solution and have a cypress folder with its own package.json and yarn.lock. That way dependencies don't collide as long as I don't need Jest when writing cypress tests which does not make much sense :)

@FredyC, +1. I was bothered by the type conflicts here...  The black list feature is helpful for mono-repo to have their @types file properly mange at the root level.
Plz, reconsider to add this support since we have white list, logically it should not be too difficult to black list, I might be wrong though.

@hypeofpipe I wish I had found your comment a week ago. These type collisions have been murdering my productivity and now I can finally publish 🙏

I think what would really help in this case is to at least have the ability to turn off module @type declarations when they do clash.
For example:
Root tsconfig.json
{
   "paths": {
      "mocha": ["typings/mocha.d.ts"]
    }
}

typings/mocha.ts
declare module 'mocha';

We're really at the mercy of library authors to avoid using globals, but without another way for projects like Jest to express types for their globals or a way for users to intelligently turn them off, we're left with having to explicitly define each and every @type dependency in our tsconifg. I dont think this is a solution.

Is there any update ?
I am issuing the same problem for KeyboardEvent type.
The global name is conflicting with @types/react and DOM types (from typescript)

An open issue related to this can be found at #37053. Show your support with upvotes and comments.