Updates codelabs

What's changed, or what was fixed?

Updates the Your First PWA code Lab

Target Live Date: 2019-04-19

Whoops!
There were 57 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/fundamentals/codelabs/debugging-service-workers/img/132f9c0cd308546f.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/debugging-service-workers/img/132f9c0cd308546f.png'
src/content/en/fundamentals/codelabs/debugging-service-workers/img/265d8ff469201930.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/debugging-service-workers/img/265d8ff469201930.png'
src/content/en/fundamentals/codelabs/debugging-service-workers/img/2ba393cf3d41e087.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/debugging-service-workers/img/2ba393cf3d41e087.png'
src/content/en/fundamentals/codelabs/debugging-service-workers/img/2e41dbf21437944c.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/debugging-service-workers/img/2e41dbf21437944c.png'
src/content/en/fundamentals/codelabs/debugging-service-workers/img/306ae05a5ccff37f.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/debugging-service-workers/img/306ae05a5ccff37f.png'
src/content/en/fundamentals/codelabs/debugging-service-workers/img/317d24238f05e69c.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/debugging-service-workers/img/317d24238f05e69c.png'
src/content/en/fundamentals/codelabs/debugging-service-workers/img/3dea544e6b44979d.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/debugging-service-workers/img/3dea544e6b44979d.png'
src/content/en/fundamentals/codelabs/debugging-service-workers/img/5116146f838a566.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/debugging-service-workers/img/5116146f838a566.png'
src/content/en/fundamentals/codelabs/debugging-service-workers/img/59838a73a2ea2aaa.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/debugging-service-workers/img/59838a73a2ea2aaa.png'
src/content/en/fundamentals/codelabs/debugging-service-workers/img/5f7ecd7d7f9c043a.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/debugging-service-workers/img/5f7ecd7d7f9c043a.png'
src/content/en/fundamentals/codelabs/debugging-service-workers/img/5fcfd389f5357c09.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/debugging-service-workers/img/5fcfd389f5357c09.png'
src/content/en/fundamentals/codelabs/debugging-service-workers/img/70e461338a0bb051.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/debugging-service-workers/img/70e461338a0bb051.png'
src/content/en/fundamentals/codelabs/debugging-service-workers/img/739dc5811e4aa937.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/debugging-service-workers/img/739dc5811e4aa937.png'
src/content/en/fundamentals/codelabs/debugging-service-workers/img/830dc8e341890d23.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/debugging-service-workers/img/830dc8e341890d23.png'
src/content/en/fundamentals/codelabs/debugging-service-workers/img/873b58278064b627.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/debugging-service-workers/img/873b58278064b627.png'
src/content/en/fundamentals/codelabs/debugging-service-workers/img/8c59c74286a01362.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/debugging-service-workers/img/8c59c74286a01362.png'
src/content/en/fundamentals/codelabs/debugging-service-workers/img/9377be2a4e29c16b.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/debugging-service-workers/img/9377be2a4e29c16b.png'
src/content/en/fundamentals/codelabs/debugging-service-workers/img/a039ca69d2179199.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/debugging-service-workers/img/a039ca69d2179199.png'
src/content/en/fundamentals/codelabs/debugging-service-workers/img/a6f485875ca088db.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/debugging-service-workers/img/a6f485875ca088db.png'
src/content/en/fundamentals/codelabs/debugging-service-workers/img/ac3b3feec0554231.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/debugging-service-workers/img/ac3b3feec0554231.png'
src/content/en/fundamentals/codelabs/debugging-service-workers/img/ad313b2b4e3105be.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/debugging-service-workers/img/ad313b2b4e3105be.png'
src/content/en/fundamentals/codelabs/debugging-service-workers/img/af2b3981c63b1529.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/debugging-service-workers/img/af2b3981c63b1529.png'
src/content/en/fundamentals/codelabs/debugging-service-workers/img/b380532368b4f56c.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/debugging-service-workers/img/b380532368b4f56c.png'
src/content/en/fundamentals/codelabs/debugging-service-workers/img/c59b54a853215598.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/debugging-service-workers/img/c59b54a853215598.png'
src/content/en/fundamentals/codelabs/debugging-service-workers/img/ce7b5e8df4e8bc07.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/debugging-service-workers/img/ce7b5e8df4e8bc07.png'
src/content/en/fundamentals/codelabs/debugging-service-workers/img/d2458f80800f4c2.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/debugging-service-workers/img/d2458f80800f4c2.png'
src/content/en/fundamentals/codelabs/debugging-service-workers/img/d6c0cc08665a2429.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/debugging-service-workers/img/d6c0cc08665a2429.png'
src/content/en/fundamentals/codelabs/debugging-service-workers/img/d960b322c020d6cc.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/debugging-service-workers/img/d960b322c020d6cc.png'
src/content/en/fundamentals/codelabs/debugging-service-workers/img/da7b5f76723ca525.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/debugging-service-workers/img/da7b5f76723ca525.png'
src/content/en/fundamentals/codelabs/debugging-service-workers/img/f0f6d3b0a1b1f18d.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/debugging-service-workers/img/f0f6d3b0a1b1f18d.png'
src/content/en/fundamentals/codelabs/offline/img/9246b0abd8d860da.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/offline/img/9246b0abd8d860da.png'
src/content/en/fundamentals/codelabs/web-perf/img/17aaa204bd2ff067.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/web-perf/img/17aaa204bd2ff067.png'
src/content/en/fundamentals/codelabs/web-perf/img/1bd8f7700f55a6c4.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/web-perf/img/1bd8f7700f55a6c4.png'
src/content/en/fundamentals/codelabs/web-perf/img/2e40b3134f26b0fa.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/web-perf/img/2e40b3134f26b0fa.png'
src/content/en/fundamentals/codelabs/web-perf/img/36d93b5f28eb60c5.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/web-perf/img/36d93b5f28eb60c5.png'
src/content/en/fundamentals/codelabs/web-perf/img/3d74ba7552fa6aaf.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/web-perf/img/3d74ba7552fa6aaf.png'
src/content/en/fundamentals/codelabs/web-perf/img/5c2a91c2a63b2c10.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/web-perf/img/5c2a91c2a63b2c10.png'
src/content/en/fundamentals/codelabs/web-perf/img/d6fb17faaa99e6f.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/web-perf/img/d6fb17faaa99e6f.png'
src/content/en/fundamentals/codelabs/web-perf/img/fce56d36285bc1fc.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/web-perf/img/fce56d36285bc1fc.png'
src/content/en/fundamentals/codelabs/your-first-pwapp/img/156b5e3cc8373d55.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/your-first-pwapp/img/156b5e3cc8373d55.png'
src/content/en/fundamentals/codelabs/your-first-pwapp/img/166c3b4982e4a0ad.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/your-first-pwapp/img/166c3b4982e4a0ad.png'
src/content/en/fundamentals/codelabs/your-first-pwapp/img/1f454b6807700695.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/your-first-pwapp/img/1f454b6807700695.png'
src/content/en/fundamentals/codelabs/your-first-pwapp/img/39b4e0371e9703e6.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/your-first-pwapp/img/39b4e0371e9703e6.png'
src/content/en/fundamentals/codelabs/your-first-pwapp/img/433870360ad308d4.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/your-first-pwapp/img/433870360ad308d4.png'
src/content/en/fundamentals/codelabs/your-first-pwapp/img/7656372ff6c6a0f7.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/your-first-pwapp/img/7656372ff6c6a0f7.png'
src/content/en/fundamentals/codelabs/your-first-pwapp/img/81347b12f83e4291.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/your-first-pwapp/img/81347b12f83e4291.png'
src/content/en/fundamentals/codelabs/your-first-pwapp/img/8a959b48e233bc93.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/your-first-pwapp/img/8a959b48e233bc93.png'
src/content/en/fundamentals/codelabs/your-first-pwapp/img/9efdf0d1258b78e4.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/your-first-pwapp/img/9efdf0d1258b78e4.png'
src/content/en/fundamentals/codelabs/your-first-pwapp/img/aa64e93e8151b642.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/your-first-pwapp/img/aa64e93e8151b642.png'
src/content/en/fundamentals/codelabs/your-first-pwapp/img/ab9c361527825fac.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/your-first-pwapp/img/ab9c361527825fac.png'
src/content/en/fundamentals/codelabs/your-first-pwapp/img/b1728ef310c444f5.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/your-first-pwapp/img/b1728ef310c444f5.png'
src/content/en/fundamentals/codelabs/your-first-pwapp/img/bf15c2f18d7f945c.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/your-first-pwapp/img/bf15c2f18d7f945c.png'
src/content/en/fundamentals/codelabs/your-first-pwapp/img/cbfdd0302b611ab0.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/your-first-pwapp/img/cbfdd0302b611ab0.png'
src/content/en/fundamentals/codelabs/your-first-pwapp/img/cf095c2153306fa7.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/your-first-pwapp/img/cf095c2153306fa7.png'
src/content/en/fundamentals/codelabs/your-first-pwapp/img/daefd30e8a290df5.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/your-first-pwapp/img/daefd30e8a290df5.png'
src/content/en/fundamentals/codelabs/your-first-pwapp/img/dc07bbc9fcfe7c5b.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/your-first-pwapp/img/dc07bbc9fcfe7c5b.png'
src/content/en/fundamentals/codelabs/your-first-pwapp/img/ed4633f91ec1389f.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/fundamentals/codelabs/your-first-pwapp/img/ed4633f91ec1389f.png'

:tada: This has been pushed live to https://developers.google.com/web/


Quick stage removal typo fix

Stage name wasn't displaying in remove stage modal because of a typo. Fixed that and added notice to the user if they are about to delete the environment (by removing the last stage).

Thanks for the improvement! r+


Faucet cannot send transactions with more than 25 ancestors

This issue arises if too many users request satoshis within the same block. The tatooine wallet/faucet currently creates transactions using unconfirmed UTXOs and if too many of them are already in the mempool you can't broadcast new transactions.

Could the issue be related to the bdk-jvm library version we are using in tatooine faucet currently?

I am assuming it will require a good amount of bdk libs digging, and once done, implementation won't be hard for android.
Can you suggest some resources to get started with?
Or should I have some digging into bdk docs: https://docs.rs/bdk/latest/bdk/ ?


Piped responses truncated when running under node 0.8.x

I'm using this module to forward certain incoming requests to a backend server:
var dbReq = request({uri:dbURL, jar:false, pool:foreverPool});
req.pipe(dbReq).pipe(res);

// debugging code
dbReq.on('data', function (d) { console.warn("DATA FROM API REQUEST", d.toString()); });

However, when the dbReq returns a large amount of data the response often gets truncated running under node 0.8.x. I've confirmed that the upstream server is returning valid data, but the debugging logs on the 'data' events show only what the client is seeing: a bunch of output during the the first part of the dbReq response but then suddenly stopping.
Running under node.js 0.10.x seems to fix (or at least mask) the problem.

This is affecting a project I'm working on as well. I can't find a version combo that resolves the issue.

Ah, it seems if gzip is set to true, the response is truncated. Works fine with gzip false.

I'm running into what I think is the same issue.
Specifically I've got a program that writes the response to an HTTP(S) request to stdout using request(params).pipe(process.stdout).
When writing directly to the console  (node foo.js) , things work fine.
When writing to a file (node foo.js > file.txt), things work fine.
When piping to another process (eg. node foo.js | cat or node foo.js | json_pp), the stream seems to be truncated.
The truncation appears to happen consistently after 1024 bytes (or characters, at least).
Strangely enough, while:

node foo.js | cat seems to be truncated at 1024 bytes
both node foo.js and node foo.js > foo; cat foo displays all 8814 bytes (for example)

each of:

node foo.js > foo; wc foo
node foo.js > foo; cat foo | wc
node foo.js | wc
and node foo.js | cat | wc

yield the same result (specifically 1     582    8814).
In other words, it may be the case that the truncation is only a visual one.  While not all the characters appear on the terminal, the wc command sees them as the same (and correct) size.
Is it possible an extra \x00 byte is being added to the end of the block or something like that?
Note that all of this is independent of the specific data in my file -- this is not a function of the particular character found at the 1024th position in the file.
This is also independent of the command to which the stream is being piped, or at least there is more than one command that sees the truncated stream (e.g., the aforementioned cat and json_pp).
Setting gzip:false didn't seem to help me.
Versions:

<EMAIL_ADDRESS>node v0.10.31
OSX Darwin Kernel Version 13.4.0 (MacBook Pro)

@rodw I suspect that it is just an intermittent issue rather than something related to visual display or which command comes next in the chain.  Any chance you could give us a self-contained test case that either reports success or failure (and fails sometimes)?

@nylen There's really nothing intermittent about it - in the cases in which this "fails", it fails every time in exactly the same way and at exactly the same place.  (Suspiciously right at 1024 bytes.)
I'll try to pull together a simple test case, but I don't think I'm doing much more than this example from the README request('http://google.com/doodle.png').pipe(fs.createWriteStream('doodle.png')) save that I'm using an HTTPS URL that returns JSON and piping it to process.stdout.

@nylen Oddly enough, it appears that the underlying issue is related to an interaction between request and a module called term-list.
For example, using this program:
var request = require('request');
request.get("https://github.com/request/request/issues/511").pipe(process.stdout);

the command:
node issue-511.js

and
node issue-511.js | cat

give the same results.
However, if we load the term-list module:
var TermList = require('term-list');
var request = require('request');
request.get("https://github.com/request/request/issues/511").pipe(process.stdout);

Now:
node issue-511.js

works the same as before, but:
node issue-511.js | cat

is truncated after 1024 characters and throws and error, as in the following output:
<!DOCTYPE html>
<html lang="en" class="">
  <head prefix="og: http://ogp.me/ns# fb: http://ogp.me/ns/fb# object: http://ogp.me/ns/object# article: http://ogp.me/ns/article# profile: http://ogp.me/ns/profile#">
    <meta charset='utf-8'>
    <meta http-equiv="X-UA-Compatible" content="IE=edge">
    <meta http-equiv="Content-Language" content="en">

    <title>Piped responses truncated when running under node 0.8.x · Issue #511 · request/request · GitHub</title>
    <link rel="search" type="application/opensearchdescription+xml" href="/opensearch.xml" title="GitHub">
    <link rel="fluid-icon" href="https://github.com/fluidicon.png" title="GitHub">
    <link rel="apple-touch-icon" sizes="57x57" href="/apple-touch-icon-114.png">
    <link rel="apple-touch-icon" sizes="114x114" href="/apple-touch-icon-114.png">
    <link rel="apple-touch-icon" sizes="72x72" href="/apple-touch-icon-144.png">
    <link rel="apple-touch-icon" sizes="144x144" href="/apple-touch-icon-144.png">
    <met
stream.js:94
      throw er; // Unhandled stream error in pipe.
            ^
Error: write EPIPE
    at errnoException (net.js:904:11)
    at Object.afterWrite (net.js:720:19)

I don't know which module is doing something wrong (if either), but this sort of makes sense as term-list does work with stdout, possibly in a non-standard way.
I'm not sure if this is exactly the same issue as others on this thread are seeing, but the basic symptoms are quite similar.

Actually, it's not even term-list, the problem seems to be related to module that term-list loads called keypress.
The following program creates the issue:
require("keypress")(process.stdin);
var request = require('request');
request.get("https://github.com/request/request/issues/511").pipe(process.stdout);

but taking out line 1, or just changing it to require("keypress")(); does not create the issue.

Seeing this issue under node v4.4.7, request v.2.75.0 on Windows 10 (anniversary edition, under the Linux Subsystem).  Same identical code runs fine on node v6.6.0, request v2.75.0 on OS X.
Have never used the  term-list and keypress modules, and neither are present on the system.
I am only seeing it on fairly large sized resources.
For a specific URL where I expect a bit over 3344 * 1k bytes back, if I pass the option encoding:null for a specific URL (expecting ) it always stops at the same exact spot (2976 * 1k), but if I omit this it varies slightly - but it is still always on a 1k boundary. For instance in four runs it returned 2832, 2928, 2944 and 2976 times 1k bytes.


web page with https://fw/ui/ does not display correctly

web page with https://fw/ui/ does not display correctly
ex: https://fw/ui/core/firmware/#checkupdate it takes around 10sec to display the page

System:
OPNsense 15.7.9-i386
FreeBSD 10.1-RELEASE-p17
LibreSSL 2.2.2

We've seen this one other time, the package contents not being installed correctly. Can you check if your disk is full:
# df -h

Console root menu option 12 should upgrade to 15.7.10 ok and fix the GUI if it wasn't due to a full disk. Note that the 15.7.10 update will reboot.

It's a vbox dynamic disk of 10GB,
root@OPNsense:~ # df -h
Filesystem      Size    Used   Avail Capacity  Mounted on
/dev/ada0s1a    9.7G    809M    8.1G     9%    /
devfs           1.0K    1.0K      0B   100%    /dev
devfs           1.0K    1.0K      0B   100%    /var/dhcpd/dev
I installed OPNsense from OPNsense-15.7_LibreSSL-cdrom-i386.iso, updated to 15.7.9 from the console menu then updated to 15.7.10 from console menu, the bug still remains

Browser cache maybe? We moved themes around. E.g. Firefox cache handling is very sticky. Try another browser, close and reopen, maybe empty cached css and javascript.

Screenshot looks like a problem I also experienced (somehow the theme was set to 'pfsense_ng' instead of 'opnsense'.  (had to set it to 'simple' and then back to 'opnsense' to restore it completely but this does not work anymore since 'simple' theme is gone with 15.7.10).
@gitdevmod could you try this:
Connect to the box by using your browsers dev tools/network. Watch if you get any 404 back and have a look at the URL of that file (most probably a css file). Do you see any references to the 'simple' or the 'pfsense_ng' theme?

The pfsense_ng issue happens when a pfsense config was imported and affects all pages. It reads like this only happens on the firmware upgrade page?

@fichtner I tried firefox and chrominium with removing cache and still the same. It was also the case from ui/proxy
@mschilt I tried to change the theme to simple to try and did not see anything I switched then back to opnsense. The issue is now resolved since I selected opnsense theme (only one theme in the list like you said) in  settings in page and applied
In source code of the ui/firmware page there is no reference to pfsense_ng

@mschilt @gitdevmod is this somehow reproducible? the workaround described by @mschilt seems odd, it points to a bug in the theme load process we've been unable to trigger locally.

@mschilt from the opnsense installation there is no access.log file at least in /var/log/lighttpd directory

@gitdevmod last question for today, was the rest of the GUI affected or only the /ui parts?

@gitdevmod great that it is now solved.
@fichtner Happened to me the last time when I was updating (there is another 'issue' regarding the messed up interface order, etc.). For me only the new parts of the gui were affected (/ui/)

Thanks guys, keeping this open for further investigation.

@fichtner if I recall correctly, possible way to reproduce:
install 15.7 then upgrade to 15.7.9 select simple theme then change back to opnsense
ui/ display issue appears
update to 15.7.10 still the same
select again opnsense in settings page then apply and ui/ page works now

Found the issue, the new code handled an empty theme tag differently.
Fixed in https://github.com/opnsense/core/commit/358318954034bf5a9410c3bd05346fbcd73b7ace

Could reproduce... closed, thanks!


100% memory/cpu usage

IDE Visual Studio Code(1.87) w/ platformIO and the yosys extension
As I was getting some code to pass formal verification with 'sby', the visual code "update complete" notification popped up.
my IDE was updated to v1.88.
the next time I ran 'sby', I received an error code
SBY 22:04:02 [counter] base: starting process "cd counter/src& yosys -ql ../model/design.log ../model/design.ys"
SBY 22:04:02 [counter] base: finished (returncode=3221225781)
SBY 22:04:02 [counter] base: task failed. ERROR.
SBY 22:04:02 [counter] summary: Elapsed clock time [H:MM:SS (secs)]: 0:00:00 (0)
SBY 22:04:02 [counter] summary: Elapsed process time unvailable on Windows
SBY 22:04:02 [counter] summary: engine_0 (smtbmc) did not return a status
SBY 22:04:02 [counter] summary: engine_0 did not produce any traces
SBY 22:04:02 [counter] DONE (ERROR, rc=16)

After restarting my pc, reinstalling visual code(1.87), platformio, oss-cad-suite, the error was still the only output I could get. even running sby -E did not help.
Running :\oss-cad-suite\enviroment.bat did not change is problem. But
running :\oss-cad-suite\start.bat from the 'visual studio' terminal, got me back up and running.
I have no idea what is going on, now if I start visual code, it starts yosys.exe which quickly consume all memory and page resources on my pc (32gig)
One thing I have noticed, after uninstalling, then installing the IDE, none of the extensions  where removed. I had to do that manually.
The current working dir was also saved, opening back up when I started visual code after the fresh install.
yosys.exe 100% cpu and 100% memory. on starting visual code.
I managed to close the folder, then visual code, then 'task end' yosys.exe.
But now if I open any folder containing *.v files, yosys.exe starts up and consumes all the ram and cpu

Hi, I tried to replicate the setup with v1.88 and Lushay code 0.0.19 and platformIO and unfortunately, I have not been able to reproduce the issue yet.
from your description, I think this might be two separate issues, I see SBY is calling yosys without specifying a full path, which means it expects it to already be loaded, which would explain why after running start.bat it would work.
But I don't think this is related to the LushayCode extension issue you mentioned with the 100% since SBY I assume you are running manually and not via our plugin.
Our plugin gets instantiated whenever there is a project open with a .v file so it makes sense that it would be triggered by that and there are a few steps for things like the module debugger or the constraints editor which use yosys, but again I was still unable to pinpoint exactly what is causing the issue for you.
Does this happen for a specific verilog project or does it happen to all projects, for example if you open our examples repo https://github.com/lushaylabs/tangnano9k-series-examples does it happen as-well (this will help understand if it is project related or if I can reproduce using this repo)
Another thing that might help is to know the path to OSS CAD Suite and the version if you know, and the settings for the lushay code plugin (mainly Lushay.Oss Cad Suite: Path)
sorry for the inconvenience, hopefully together we can get to the bottom of this

As you suggested, I opened the examples published, thank you btw, good stuff. and everything works as always.
From what 'filemon' shows me, anytime I open, or tab to a file in visual code, yosys.exe opens and reads the entire file.
yosys.exe keeps reading my counter.v file into memory, over and over. After taking a memory dump, I see my verilog text repeating in ram. a lot.
I have been trying to edit a simple counter with a pipelined carrieover chain( for higher fmax) and I guess its so bad yosys is choking on it. Thank yall for making this plugin. Its fuel a passion.

            for( idy = 1; idy != CHUNK_COUNT-1; idy = idy + 1 ) begin
                counter[ (idy*LUT_SIZE) + LUT_SIZE - 1 ] <= 0;  // clear the carry bit for this chunk
                if( counter[ (idy*LUT_SIZE) - 1 ] )             // if the previous chunk has the carry bit set, do the subtraction
                    counter[idy*LUT_SIZE+:LUT_SIZE] <= counter[idy*LUT_SIZE+:LUT_SIZE] - 1'b1;
                chunk_equal_zero[idy-1] <= counter[idy*LUT_SIZE+:REG_SIZE] != 0;   // Set the equal_zero flag if the register(without carry bit) == 0
            end

This loop, under default parameters, is never ending. by changing '!=' to '<' all is well and the stars can twinkle once again. Sorry for wasting your time

Thank you, both for reporting this and the in-depth debugging to get to the root cause. I will try and see if there is a way to put a limit on the running process so that it can catch situations like this and provide an error message instead of running indefinitely and locking up.

I was looking for a method to get yosys running with the -g switch.
        globally enable debug log messages

It looks like src/stages/yosys-synth.ts line# 44 would be where to inject it. I wasn't sure if that would even help. so I used the tools I was familiar with instead of trying to learn the visual code extension api


Fix ch libvirt

This patch series fixes the libvirt version parsing and sets the domain based on the underlying hypervisor.

fyi, working on flake8 failures.

fyi, working on flake8 failures.

You can follow this doc to set local dev env, so check errors could be fixed locally.
https://mslisa.readthedocs.io/en/main/write_test/dev_setup.html


Feature: Elastic tabstops

Can zprint utilize elastic tabstops?

Not having ever heard of "elastic tabstops", I followed the link, read about them, and downloaded the "elastic notepad".  All of this is interesting, but I'm not sure what you are looking for zprint to actually do.  That is to say, what do you mean by "utilize"?  zprint works hard to get the indentation right for a monospaced font.  It could certainly output tabs instead of 2 character spaced indents, but sometimes the indent is way across the page.  Frequently it isn't associated with any other tabstops -- a "hang" is just something placed below something else with a lot of space in front of it.  Perhaps every space between things becomes a tab?  Not clear.
If all you are asking is "Does zprint support elastic tabstops now?", the answer is no.  If you are asking "Could zprint be made to support elastic tabstops?", then I need more information.
At this point, I would need to see a better description of what you want in order to decide if zprint can be made to do it in a reasonable way.  I'm asking you to show me some Clojure code and where you would put the elastic tabstops to get what you want.  If that is even what you want.
Once I undersand that, before I were to dive in to implementing elastic tabstop support in zprint, I would also need to understand a reasonably compelling use case.  It is entirely possible that you could enthuse me to do this work.  That said, I don't yet even understand what work needs to be done.

Thanks for taking the time to look at this @kkinnear!
I don't think it's a tabs versus spaces thing since that's where soft tabs comes in. My question is really about if zprint could support elastic tabstops.
Here's an example of what I mean: https://github.com/clojure-emacs/clojure-mode#vertical-alignment
By doing this kind of formatting across different data structures, it'll make the code more readable. As a data point, Golang uses it as their standard formatter for the language via https://golang.org/pkg/text/tabwriter/ .

If your question is: "Can zprint output code like the vertical alignment in the first link?", then the answer is yes.
First, will zprint do it for code? (Which is why I'm doing this as a string):
zprint.core=> (def issue "(def my-map {:a-key 1 :other-key 2})")
#'zprint.core/issue
zprint.core=> (zprint issue 20 {:parse-string? true})
(def my-map
  {:a-key 1,
   :other-key 2})
nil
zprint.core=> (zprint issue 20 {:parse-string? true :style :justified})
(def my-map
  {:a-key     1,
   :other-key 2})
nil

Second, can zprint do it for a map at the repl?
zprint.core=> my-map
{:a-key 1, :other-key 2}
zprint.core=> (zprint my-map 20)
{:a-key 1,
 :other-key 2}
nil
zprint.core=> (zprint my-map 20 {:style :justified})
{:a-key     1,
 :other-key 2}

In both case, the answer is yes.  I called this "jusitify" instead of "vertical alignment".  This is available individually for binding pairs, maps, and pair-fn's (mostly cond variants).  The :justified style is defined as:
    :justified {:binding {:justify? true},
                :map {:justify? true},
                :pair {:justify? true}}

You can see this in more detail if you do (czprint nil :explain).
Some code looks better justified, some doesn't.  A particularly striking example is the definition of defn  Look at the big let form in the middle.
zprint.core=> (czprint-fn defn)
(def
  ^{:doc
      "Same as (def name (fn [params* ] exprs*)) or (def
    name (fn ([params* ] exprs*)+)) with any doc-string or attrs added
    to the var metadata. prepost-map defines a map with optional keys
    :pre and :post that contain collections of pre or post conditions.

  Spec:
    args: (cat :fn-name simple-symbol?
               :docstring (? string?)
               :meta (? map?)
               :fn-tail
                 (alt :arity-1 :clojure.core.specs.alpha/params+body
                      :arity-n
                        (cat :bodies
                               (+ (spec :clojure.core.specs.alpha/params+body))
                             :attr-map (? map?))))
    ret: any?",
    :arglists '([name doc-string? attr-map? [params*] prepost-map? body]
                [name doc-string? attr-map? ([params*] prepost-map? body) +
                 attr-map?]),
    :added "1.0"}
  defn
  (fn defn [&form &env name & fdecl]
    ;; Note: Cannot delegate this check to def because of the call to (with-meta
    ;; name ..)
    (if (instance? clojure.lang.Symbol name)
      nil
      (throw (IllegalArgumentException.
               "First argument to defn must be a symbol")))
    (let [m (if (string? (first fdecl)) {:doc (first fdecl)} {})
          fdecl (if (string? (first fdecl)) (next fdecl) fdecl)
          m (if (map? (first fdecl)) (conj m (first fdecl)) m)
          fdecl (if (map? (first fdecl)) (next fdecl) fdecl)
          fdecl (if (vector? (first fdecl)) (list fdecl) fdecl)
          m (if (map? (last fdecl)) (conj m (last fdecl)) m)
          fdecl (if (map? (last fdecl)) (butlast fdecl) fdecl)
          m (conj {:arglists (list 'quote (sigs fdecl))} m)
          m (let [inline (:inline m)
                  ifn (first inline)
                  iname (second inline)]
              ;; same as: (if (and (= 'fn ifn) (not (symbol? iname))) ...)
              (if (if (clojure.lang.Util/equiv 'fn ifn)
                    (if (instance? clojure.lang.Symbol iname) false true))
                ;; inserts the same fn name to the inline fn if it does not have
                ;; one
                (assoc m
                  :inline (cons ifn
                                (cons (clojure.lang.Symbol/intern
                                        (.concat (.getName ^clojure.lang.Symbol
                                                           name)
                                                 "__inliner"))
                                      (next inline))))
                m))
          m (conj (if (meta name) (meta name) {}) m)]
      (list 'def
            (with-meta name m)
            ;;todo - restore propagation of fn name
            ;;must figure out how to convey primitive hints to self calls first
            ;;(cons `fn fdecl)
            (with-meta (cons `fn fdecl) {:rettag (:tag m)})))))
nil
zprint.core=> (czprint-fn defn {:style :justified})
(def
  ^{:doc
      "Same as (def name (fn [params* ] exprs*)) or (def
    name (fn ([params* ] exprs*)+)) with any doc-string or attrs added
    to the var metadata. prepost-map defines a map with optional keys
    :pre and :post that contain collections of pre or post conditions.

  Spec:
    args: (cat :fn-name simple-symbol?
               :docstring (? string?)
               :meta (? map?)
               :fn-tail
                 (alt :arity-1 :clojure.core.specs.alpha/params+body
                      :arity-n
                        (cat :bodies
                               (+ (spec :clojure.core.specs.alpha/params+body))
                             :attr-map (? map?))))
    ret: any?",
    :arglists '([name doc-string? attr-map? [params*] prepost-map? body]
                [name doc-string? attr-map? ([params*] prepost-map? body) +
                 attr-map?]),
    :added "1.0"}
  defn
  (fn defn [&form &env name & fdecl]
    ;; Note: Cannot delegate this check to def because of the call to (with-meta
    ;; name ..)
    (if (instance? clojure.lang.Symbol name)
      nil
      (throw (IllegalArgumentException.
               "First argument to defn must be a symbol")))
    (let [m     (if (string? (first fdecl)) {:doc (first fdecl)} {})
          fdecl (if (string? (first fdecl)) (next fdecl) fdecl)
          m     (if (map? (first fdecl)) (conj m (first fdecl)) m)
          fdecl (if (map? (first fdecl)) (next fdecl) fdecl)
          fdecl (if (vector? (first fdecl)) (list fdecl) fdecl)
          m     (if (map? (last fdecl)) (conj m (last fdecl)) m)
          fdecl (if (map? (last fdecl)) (butlast fdecl) fdecl)
          m     (conj {:arglists (list 'quote (sigs fdecl))} m)
          m     (let [inline (:inline m)
                      ifn    (first inline)
                      iname  (second inline)]
                  ;; same as: (if (and (= 'fn ifn) (not (symbol? iname))) ...)
                  (if (if (clojure.lang.Util/equiv 'fn ifn)
                        (if (instance? clojure.lang.Symbol iname) false true))
                    ;; inserts the same fn name to the inline fn if it does not
                    ;; have one
                    (assoc m
                      :inline (cons
                                ifn
                                (cons (clojure.lang.Symbol/intern
                                        (.concat (.getName ^clojure.lang.Symbol
                                                           name)
                                                 "__inliner"))
                                      (next inline))))
                    m))
          m     (conj (if (meta name) (meta name) {}) m)]
      (list 'def
            (with-meta name m)
            ;;todo - restore propagation of fn name
            ;;must figure out how to convey primitive hints to self calls first
            ;;(cons `fn fdecl)
            (with-meta (cons `fn fdecl) {:rettag (:tag m)})))))
nil

In addition, you might note the addition of the specs for defn added to the docstring. Which has nothing to do with your issue, but is a nice feature nevertheless.
If by "utilize elastic tabstops", you mean "make it look like the vertical alignment example in the first link", then the answer is most certainly "yes"!

That's awesome! Since it can do it, a user somehow run it on saving a file so code can be neatly formatted as you edit it?

There are about three ways that you can use zprint when editing:

You can use the zprint-filter (a program which accepts Clojure(script) source on stdin and outputs formatted Clojure(script) source on stdout.  Most editors allow you to pipe a section of text through an external program.  Certainly vi and emacs and sublime do.  This is what I do while editing, as having it formatted correctly while I'm creating or modifying a function is a big help to me.  So, mostly, I keep my files formatted while I'm working on them.  If the graalvm stuff isn't to your liking, there is also a slightly slower but still pretty fast way to get a zprint-filter working.
You can trigger the zprint-filter when you save a file to do the formatting whenever you save the file.  Not every editor can be configured to do this, but many can.  Exactly how you would do that is pretty much up to you to figure out for your editor.  I know some people are using zprint to do this, but it isn't my personal approach.
You can format your file at the command line, using lein-zprint or other tool like that.  I do this before I push my code to github, but otherwise I mostly just do #1.

Thanks @kkinnear I'll close this issue for future reference to those interested!


FAST.Farm vtk files

Hello everyone, I would like to know in which order the data of the wind velocity contained in the vtk files coming from a simulation are stored...I mean, which order is followed?
My opinion is that, since I have 25 points in each of the 3 directions (so, 25 in x, 25 in y and 25 in z) to define the grid and since each 625 lines (that is 25*25) the x-velocity of the wind changes increasing ( I have a steady inflow wind), the first 625 lines are referred to the XY plane at z=0, the next 625 to the XY plane at z=10 (the spacing between eacxh point in the grid is 10 m), and so on...am I correct?
Moreover, I don't know if, in each block of 625 lines, I firstly moved in x (so y fixed) or vice versa.
Thanks a lot!

Hi @Tommi,
You can try the following example script to read your VTK plane:
https://github.com/OpenFAST/python-toolbox/blob/main/pyFAST/input_output/examples/Example_VTKPlanesGrid.py

Dear @Tommi1198,
I agree with your interpretation.
Just to add to what @ebranlard said.  The order is described in the online FAST.Farm User's Guide and Theory Manual here: https://openfast.readthedocs.io/en/main/source/user/fast.farm/InputFiles.html#ambient-wind-precursor-files-in-visualization-toolkit-format.  As stated, the first data point corresponds to the ORIGIN and the remaining points involve looping through X, then Y, and then Z.  For more information on the simple legacy VTK format used by FAST.Farm, see: https://www.vtk.org/wp-content/uploads/2015/04/file-formats.pdf.
Best regards,

Perfect, thanks a lot to both of you!


fix: cypress tests checkout workspace branch

Description
Change default FT Repo branch to workspace
Issues Resolved

Screenshot

Testing the changes

Check List

[ ] All tests pass

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

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

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

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

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

Flag
Coverage Δ

Linux_
?

_1
?

_2
55.30% <ø> (ø)

_3
?

_4
?

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

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


fix e2e for planting cursor

Tasks

[ ] comment in planting cursor again (commented out in #1077)
[ ] fix e2e

Use case
No response
Related Pull request
No response

@absurd-turtle any idea how this could be done?


Messages API is missing a whitespace after data: to be compliant

System Info
ghcr.io/huggingface/text-generation-inference:2.0.4
Information

[X] Docker
[ ] The CLI directly

Tasks

[X] An officially supported command
[ ] My own modifications

Reproduction

Start container
run curl request with streaming

Expected behavior
TGI
data:{"id":"","object":"text_completion","created":1717586509,"model":"meta-llama/Meta-Llama-3-8B-Instruct","system_fingerprint":"2.0.4-sha-f426a33","choices":[{"index":0,"delta":{"role":"assistant","content":"Here"},"logprobs":null,"finish_reason":null}]}

vLLM
data: {"id":"cmpl-a33baad7fc1b46518194d433bd046551","object":"chat.completion.chunk","created":1717586822,"model":"meta-llama/Meta-Llama-3-8B-Instruct","choices":[{"index":0,"delta":{"content":""},"finish_reason":"stop"}],"usage":{"prompt_tokens":23,"total_tokens":68,"completion_tokens":45}}

OpenAI
data: {"id":"chatcmpl-9Wj3xCu6xZ2GlmuQ3hKQuAeeNki4C","object":"chat.completion.chunk","created":1717586745,"model":"gpt-4o-2024-05-13","system_fingerprint":"fp_319be4768e","choices":[{"index":0,"delta":{},"logprobs":null,"finish_reason":"stop"}]}

Hey @philschmid this should be resolved in the main
The issue was originally related to axum. In versions before 0.7.0 there was no space added after the data: field. This PR fixes it and should be available https://github.com/tokio-rs/axum/pull/2149
As of last week TGI bumped axum to 0.7.0 https://github.com/huggingface/text-generation-inference/pull/1959 so we should see the space in out responses now


Make Python Wrappers for Hyperparameters

this will be fixed by #232

Closing as PR #232 has been merged


stabilize upgrade in response

Hi @yoshuawuyts / @jbr, I start working in an example using websocket based on littoral and I found that some changes are needed in this branch stabilize-upgrade to support ws.
I tested ok in my example but let me know if something is wrong, thanks for the awesome job!!! 🙌

refs: #291

#291 doesn't work without this, and this is a pr into #291. There is no reason to merge #291 without this

Oh, guess i had it backwards then 😅


TS-4837: Add -Wextra to the build

FreeBSD build failed! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/759/ for details.

Linux build failed! See https://ci.trafficserver.apache.org/job/Github-Linux/655/ for details.

👍

Linux build successful! See https://ci.trafficserver.apache.org/job/Github-Linux/656/ for details.

FreeBSD build successful! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/760/ for details.


storescu.py AttributeError

I've been attempting to send images into a remote pacs, but receiving the following error when using the storescu.py from the cli.  I'm calling with arguments host, port, dicom-in, and -aec.  (I did rename the file to cstore.py to have it better organized in my project.)  I added a print statement for dataset after the file was read so I could see if the metadata was available.  It returns: (0008, 0016) SOP Class UID UI: CT Image Storage.
Traceback (most recent call last):
  File "cstore.py", line 156, in <module>
    status = assoc.send_c_store(dataset)
  File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/pynetdicom3-0.1.0-py3.6.egg/pynetdicom3/association.py", line 929, in send_c_store
    rsp, _ = self.dimse.receive_msg(wait=True)
  File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/pynetdicom3-0.1.0-py3.6.egg/pynetdicom3/dimse.py", line 306, in receive_msg
    self.on_receive_dimse_message(self.message)
  File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/pynetdicom3-0.1.0-py3.6.egg/pynetdicom3/dimse.py", line 421, in on_receive_dimse_message
    callback[type(message)](message)
  File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/pynetdicom3-0.1.0-py3.6.egg/pynetdicom3/dimse.py", line 848, in debug_receive_c_store_rsp
    sop_class = uid_to_sop_class(cs.AffectedSOPClassUID)
  File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/pydicom/dataset.py", line 480, in __getattr__
    return super(Dataset, self).__getattribute__(name)
AttributeError: 'Dataset' object has no attribute 'AffectedSOPClassUID'

Suggestions?

What was the SOP Class UID of the dataset you're trying to send?
Could you attach an anonymised copy of the dataset?

Greatly appreciated @scaramallion.  I'll give it a whirl.

The CT's are working now, but I'm still getting errors for SOP Class UID "1.2.840.10<IP_ADDRESS>.1.1.7  Secondary Capture Image Storage".  I noticed that this class has been deprecated so I don't think it's a priority issue to solve, maybe just something to note.
Thanks again.

Hmm, what do you mean by deprecated? We should be pretty much SOP Class UID agnostic for C-STORE operations. Do you mind posting the error?

Sure.  Let me grab a CTA that I know I had issues with earlier.  I'll post the error once I can reproduce it.

Here is the error:
E: Association.send_c_store - no valid Presentation  Context for: 'Secondary Capture Image Storage' E: Store SCU failed due to there being no valid presentation context for the current dataset
...
File "path/to/pynetdicom3-0.1.0-py3.6.egg\pynetdicom3\association.py", line 899, in send_c_store     raise ValueError("No accepted Presentation Context for 'dataset'.") ValueError: No accepted Presentation Context for 'dataset'. E: Association Aborted

Could you upload an anonymised version of the dataset?

Did you figure this out?


ID Localization for Scheduling Framework.

Hello,
I have completed the translation for the scheduling framework page as mentioned in PR #20111
Thanks.

/assign

/cc

Great localization mas @ariscahyadi , thanks for this page! this page reflects one of the latest features from Kubernetes where we can make our own custom scheduler, give it a try when you get time :)
/lgtm
/approve


feat: constraining note owner

Fixes #1817
Checklist:
Remove the checklist to signal you've completed it. Enable auto-merge if the PR is ready to merge.

[ ] If the pull request requires a cryptography review (e.g. cryptographic algorithm implementations) I have added the 'crypto' tag.
[ ] I have reviewed my diff in github, line by line and removed unexpected formatting changes, testing logs, or commented-out code.
[ ] Every change is related to the PR description.
[ ] I have linked this pull request to relevant issues (if any exist).

Thank you for the review @spalladino .

I'd move the constrain to within the get_secret_key call.

Great idea. Will address.

why flipping secret's high and low in this PR? I believe we usually go big-endian, which would mean serialising high first, right?

I initially followed the big endian but then @kevaundray flipped it here so I flipped it in aztec-packages as well so that it's consistent. I guess in crypto they are used to having it like that.

Thank you for the review @spalladino .

I'd move the constrain to within the get_secret_key call.

Great idea. Will address.

why flipping secret's high and low in this PR? I believe we usually go big-endian, which would mean serialising high first, right?

I initially followed the big endian but then @kevaundray flipped it here so I flipped it in aztec-packages as well so that it's consistent. I guess in crypto they are used to having it like that.

I can open up an issue to make barretenberg use little endian everywhere, because I believe in some places it may use little endian and in others it will use big endian


It seems that there is a bug in function "raySphereIntersection"

//Sphere Intersection Testing
Intersection raySphereIntersection(in vec3 rO, in vec3 rD, in vec3 sphereCenter, in float sphereRadius)
{
    Intersection isect;
    isect.valid = false;
    isect.point = vec3(0.0);
    isect.normal = vec3(0.0, 1.0, 0.0);

    // Transform Ray such that the spheres move down, such that the camera is close to the sky dome
    // Only change sphere origin because you can't translate a direction
    rO -= sphereCenter;
    rO /= sphereRadius;

    float A = dot(rD, rD);
    float B = 2.0*dot(rD, rO);
    float C = dot(rO, rO) - 1.0; //uniform sphere
    float discriminant = B*B - 4.0*A*C;

    //If the discriminant is negative, then there is no real root
    if(discriminant < 0.0)
    {
        return isect;
    }

    float t = (-B - sqrt(discriminant))/(2.0*A);

    if(t < 0.0)
    {
        t = (-B + sqrt(discriminant))/(2.0*A);
    }

    if(t >= 0.0)
    {
        vec3 p = vec3(rO + t*rD);
        isect.valid = true;
        isect.normal = normalize(p);

        p *= sphereRadius;
        p += sphereCenter;

        isect.point = p;
        isect.t = length(p-rO);
    }
    return isect;
}

Variable rO is changed during the function, but it is use to calulate isect.t finally. Maybe this function should me modified as below
Intersection raySphereIntersection(in vec3 rO, in vec3 rD, in vec3 sphereCenter, in float sphereRadius)
{
        vec3 old_rO = rO;
...
        // isect.t = length(p-rO);
        isect.t = length(p-old_rO);
...
}

The error caused in this program is small, but could be large with large eye coordinate.

It is correct. The displacement to the ray origin is to mimic an observer standing on the surface of the planet. The raySphereIntersection name should be better named but I digress.
Also, I'm not actively updating this repo anytime in the near future.

Thank you for your reply. I misused it when the center of the sphere is at the origin of the coordinate system and the ray origin is on the surface of the sphere.


pythonPackages.qiskit-aqua: init at 0.6.5

Motivation for this change
Qiskit Aqua: An extensible library of quantum computing algorithms.
This commit follows the new Qiskit scheme of breaking one large package
into smaller packages (terra, aer, etc), and then having a single
meta-package "qiskit" that comprises them.
Broken out of #78772.
Waiting on #83306 #80662 #83372 to pass, builds cleanly when they're cherry-picked.
python38Packages.qiskit-aqua will be broken due to upstream broken python38Packages.scikit-build (#83305 )
I disabled a lot of tests here, but there's still some 900 that run. So it's pretty well-tested.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@jonringer at this point it's just #83306 & #80662 left, which are in the same topic. I could wrap up the rest of the qiskit fixes in one PR, there's no new packages at this point. That way I could also demonstrate via bot that they all build.
Summary of remaining qiskit fixes (all done, just didn't want to keep spamming PRs):

Add pythonPackages.qiskit-[aer, ignis, aqua]. See #83306, #80662
Delete pythonPackages.IBMQuantumExperience (superseded by pythonPackages.qiskit-ibmq-provider in merged #83320 )
bump pythonPackages.qiskit -> 0.16.2, remove broken tag, make it a superset of the qiskit-[terra,aer,ignis,aqua] packages. #78772

@GrahamcOfBorg eval
running build locally (both via nixpkgs-review and nix-build). Will update with status

Update: builds clean via nixpkgs-review pr 83447.
2 package built:
python37Packages.qiskit-aqua python38Packages.qiskit-aqua

Looks fine to me, will try to build later.

Let's see if we can actually build it now via borg after #84124...
@GrahamcOfBorg build python37Packages.qiskit-aqua
@GrahamcOfBorg build python38Packages.qiskit-aqua
Took everyone's code review suggestions into account, and added an ugly-ish description of why pyscf #78872 isn't included, along with an ImportWarning when someone would try to use the appropriate chemistry section of this package.

@GrahamcOfBorg build python37Packages.qiskit-aqua python38Packages.qiskit-aqua
Left python3Packages.pyscf discussions "unresolved" above, even though they're actually resolved, as future notes for anyone who finds this issue linked in description.
Traced failing build to pythonPackages.qiskit-aer which had original unfree dependency and so couldn't test against aarch64 on ofborg. Left notes about what the issue is; fully resolving it would require packaging https://github.com/beltoforion/muparserx, which I'll leave for another day.

Looks good, thanks!


SyntaxError: Unexpected token < in JSON at position 0

I've had Dyson up and running for weeks/months without an issue. Today I've noticed my TV turning itself up and when I turned it off it would be up again.
It seems that while my TV was up it was Dyson doing the work.
Jun 21 08:29:01 evoservices homebridge[3074]: [6/21/2019, 8:29:01 AM] SyntaxError: Unexpected token < in JSON at position 0
Jun 21 08:29:01 evoservices homebridge[3074]:     at JSON.parse (<anonymous>)
Jun 21 08:29:01 evoservices homebridge[3074]:     at IncomingMessage.res.on (/usr/local/lib/node_modules/homebridge-dyson-link/index.js:179:40)
Jun 21 08:29:01 evoservices homebridge[3074]:     at emitNone (events.js:111:20)
Jun 21 08:29:01 evoservices homebridge[3074]:     at IncomingMessage.emit (events.js:208:7)
Jun 21 08:29:01 evoservices homebridge[3074]:     at endReadableNT (_stream_readable.js:1064:12)
Jun 21 08:29:01 evoservices homebridge[3074]:     at _combinedTickCallback (internal/process/next_tick.js:138:11)
Jun 21 08:29:01 evoservices homebridge[3074]:     at process._tickCallback (internal/process/next_tick.js:180:9)
Jun 21 08:29:01 evoservices homebridge[3074]: [6/21/2019, 8:29:01 AM] Got SIGTERM, shutting down Homebridge...

You may want to add some logic try/catch for parser so it doesn't crash the whole home bridge and affect other devices.
Thank you, and thank you for your work.

Hi,
i've the same issue hier.
Did you solved you problem?

I've edited some code to prevent the plugin from crashing however I believe this is related to wrong return from Dyson.
I started updating home bridge all plugins and suddenly it went away. So my guess it must be something on Dyson's end that's causing JSON requests to crash because there's no try/catch logic. I'm too weak in JavaScript area/Homebridge dev to fix stuff like that. But I should try and find out because there's a lot of areas you are on your own.

thank you for a quick replay!
your HB doesn't crash anymore but you do still have an error?

No, the error went away so I've removed my modifications because as far as I could tell the "fix" I did prevent crashes but it didn't get Dyson to work. That's why I believe the problem is on Dyson's (vendor) end and not something we can fix. We can only fix the behavior of the plugin to stop crashing HB and impacting other devices. In my case, it was turning on my SONY TV and driving me crazy.

appreciate you help!
it's pretty curios, because it worked all the time and suddenly, without changing anything, stoppt working.
Ich guess it's Dyson server problem.

I am all of a sudden having problems too. Maybe involving Dyson. Homebridge stuck “Updating”
Sent with GitHawk

I'm hitting this with my dyson plugin as well, interested in how to fix. So far I've had to remove the plugin from my config to get homebridge to run.
[1/14/2021, 1:33:20 PM] SyntaxError: Unexpected token e in JSON at position 0
    at JSON.parse (<anonymous>)
    at IncomingMessage.<anonymous> (/usr/local/lib/node_modules/homebridge-dyson-link/index.js:179:40)
    at IncomingMessage.emit (events.js:215:7)
    at endReadableNT (_stream_readable.js:1183:12)
    at processTicksAndRejections (internal/process/task_queues.js:80:21)

I'm hitting this with my dyson plugin as well, interested in how to fix. So far I've had to remove the plugin from my config to get homebridge to run.
[1/14/2021, 1:33:20 PM] SyntaxError: Unexpected token e in JSON at position 0
    at JSON.parse (<anonymous>)
    at IncomingMessage.<anonymous> (/usr/local/lib/node_modules/homebridge-dyson-link/index.js:179:40)
    at IncomingMessage.emit (events.js:215:7)
    at endReadableNT (_stream_readable.js:1183:12)
    at processTicksAndRejections (internal/process/task_queues.js:80:21)

The latest update fixes the issue! I'm switching back from "Homebridge Dyson Pure Cool" because this plugin publishes a fan service which is easier to interact with than the air filter service in Home App.

The latest update fixes the issue! I'm switching back from "Homebridge Dyson Pure Cool" because this plugin publishes a fan service which is easier to interact with than the air filter service in Home App.

Wow it came back today! Crash looping with the same error as before.

Wow it came back today! Crash looping with the same error as before.


feat: Add v2 API version support for all resources

The background has already been introduced in #707.
This issue is tracked for tasks in v1.5.
This will be the last task blocking the v1.5 release.
To achieve this goal we have a lot of tasks to do.  In order to facilitate the review, we need to split it into multiple tasks. (There was a huge PR, #820 was closed)

[x] Base code to initialize v2 version  #939
[x] ApisixRoute  #943
[ ] ApisixUpstream #944
[ ] ApisixTls #967
[ ] ApisixConsumer #989
[ ] ApisixClusterConfig #977
[ ] ApisixPluginConfig #984
[ ] Update samples/deploy/crd CRD to add v2 resources
[ ] Add e2e tests for v2 resources

In this process, we need to increase the support for multiple versions of various resources, instead of directly replacing the current v2beta3 with v2. So we need to be more careful.
This issue is used to track the progress of this task, if anyone is interested in this task, can comment and choose any task to implement.

https://github.com/apache/apisix-ingress-controller/pull/967#discussion_r857082894


Fix repo service and image path. - [closed]

In GitLab by @wknet123 on Jun 6, 2018, 06:32
Merges dev-image-path -> dev

In GitLab by @wknet123 on Nov 13, 2019, 11:03
closed


remove '-f' flag from unzip

unzip -f doesn't do what you think it does.

Hi @Spongman, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

fixes #536

@Spongman Thanks for fixing this!


Logout doesn't really log-out, another person can see my details when they simply click Login With Google

Project runs successfully. I was able to login via Google OAuth2. However,
logout doesn't really log-out the user. Seems to just take you back to the login link.
No authentication required afterwards, and can just click on the Login With Google link and get logged back in right-away.
Branch: v24
Latest commit I see:
$ git log

commit ce1d20b657fd00564db3732019866efc6e5d605b (HEAD -> v24, origin/v24, origin/HEAD)
Author: Vaadin Bot<EMAIL_ADDRESS>Date:   Tue Aug 15 08:17:30 2023 +0200

    chore: Update Vaadin 24.1.5 (#114)

If it doesn't log you out from Google, essentially there is no need of a Logout button. When using SSO, logout is at the Provider level, not at the client.
Agree with your point there. But that's not the "Authentication", that's "Authorisation". Logout therefore needs to logout from everywhere. If to re-authenticated, credentials must be provided, either it be certificate, device, credentials, tokens, etc etc... whatever the user has agreed to.

In that sense, you are right that "log out" is the wrong label. At the same time, I just tried a bunch of web apps that I happen to have nearby with SSO through Google and they all behave in exactly the way that "log out" just clears the session for that app whereas "log in" takes you to Google which lets you in again without providing credentials (since you only logged out from the app but not from Google). This seems to be a general convention and it's basically a tradeoff with using a generic SSO provider (aka "social login" even though Google SSO can also be used with corporate accounts).
I'm not sure exactly what we should change here other than to consider providing another example with e.g. Keycloak where it's more expected that you also log out from the SSO provider when you log out from the application.

Now that's the magic right, Google gets to decide whether to keep logged in, now that doesn't happen in this issue. Agree?
I tried just now with YouTube, Gmail and with my Google Account. So I logged into account, navigated to YouTube, selected my profile, and now I see my YouTube  videos. Next, browsed into Gmail, the same flow, I selected my email address, I'm in. Now I go back to YouTube, logout from there, Go back to Gmail, now here's what I observed. I am logged out from Gmail as well! This is the correct behaviour, I logout from my account meaning, on that device I should be logged out from that account. So from that browser there is no access to the rest of the services too. Otherwise it is a security loophole.

YouTube is special since it's an integrated part of Google's own services.
A more relevant comparison is a 3rd party application such as https://trello.com/.

Right. Trello/Miro has a different model. I see your point. Perhaps they don't use the backchannel logout?


Errors in svn checkout do not propagate correctly

TestSvnRepo panics for me on the current master:
-> % go test -v -run TestSvnRepo .
=== RUN   TestSvnRepo
--- FAIL: TestSvnRepo (0.05s)
	vcs_repo_test.go:45: Problem checking out repo or SVN CheckLocal is not working
	vcs_repo_test.go:51: Unable to update SVN repo version. Err was unable to update checked out version
	vcs_repo_test.go:57: Error checking checked SVN out version
	vcs_repo_test.go:60: Unable to retrieve checked out version
	vcs_repo_test.go:66: unable to update repository
	vcs_repo_test.go:75: Unable to retrieve checked out version
	vcs_repo_test.go:80: unable to retrieve commit information
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
	panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x13d9ed7]

goroutine 21 [running]:
testing.tRunner.func1(0xc42026a340)
	/Users/snelson/go1.8/src/testing/testing.go:622 +0x29d
panic(0x14b91e0, 0x1a93810)
	/Users/snelson/go1.8/src/runtime/panic.go:489 +0x2cf
github.com/sdboyer/gps.TestSvnRepo(0xc42026a340)
	/Users/snelson/go/src/github.com/sdboyer/gps/vcs_repo_test.go:82 +0x727
testing.tRunner(0xc42026a340, 0x1551ce0)
	/Users/snelson/go1.8/src/testing/testing.go:657 +0x96
created by testing.(*T).Run
	/Users/snelson/go1.8/src/testing/testing.go:697 +0x2ca
exit status 2
FAIL	github.com/sdboyer/gps	2.695s

This panic is happening because even though the err = repo.Get() line at L45 doesn't return an error, it is, in fact, failing. I hacked into the internals to print the command output, and I saw this:
2017/03/20 18:34:20 running command &{%!s(*exec.Cmd=&{/usr/bin/svn [svn checkout https://github.com/Masterminds/VCSTestRepo/trunk /var/folders/07/3tqty4fn0pqdmk8kyscf2g2m0wg_zb/T/go-vcs-svn-tests045048261/VCSTestRepo] []  <nil> 0xc420249800 0xc420249830 [] <nil> <nil> <nil> <nil> <nil> false [] [] [] [] <nil> <nil>}) %!s(time.Duration=120000000000) %!s(*gps.activityBuffer=&{{0 0} 0xc4201a7810 {0 0 <nil>}}) %!s(*gps.activityBuffer=&{{0 0} 0xc4201a7880 {0 0 <nil>}})}
2017/03/20 18:34:20 out=svn: E170013: Unable to connect to a repository at URL 'https://github.com/Masterminds/VCSTestRepo/trunk'
svn: E230001: Server SSL certificate verification failed: issuer is not trusted

Is it that the svn command exits with 0? No, it exits with 1:
-> % svn checkout "https://github.com/Masterminds/VCSTestRepo/trunk" . --non-interactive
svn: E170013: Unable to connect to a repository at URL 'https://github.com/Masterminds/VCSTestRepo/trunk'
svn: E230001: Server SSL certificate verification failed: issuer is not trusted

-> % echo $?
1

So it appears that the failure isn't getting correctly plumbed through.

Hmm, odd. (thanks for digging!)
Honestly, I haven't looked closely at the svn stuff (it's recently added, we didn't really support it before). All of the error handling there should follow a pretty standard pattern (that certainly does catch non-0 exit codes), so at first glance, it seems most likely that what we have just doesn't quite follow the pattern correctly.

There are a few things happening here.
I'm fairly certain that the reason that err didn't return an error even though the command failed was because of a bug in runFromCwd. I've fixed this in #204.
I don't know why you saw an SSL verification error, it works for me currently. You had to dig a bit to find this, because the errors returned from the vcs package don't print the entire error message by default. It stores the error returned from running the command in the Original variable, however this isn't printed in the tests. @sdboyer this might be a case where including the original error in unwrapVcsErr() could be useful, but I'll have to investigate a bit more to be sure.
And finally, the reason for the nil pointer panic is that these tests don't stop when encountering errors, instead of calling t.Error it should actually be calling t.Fatal. I've created #205 to address this.

@jstemmer yeah, I'm convinced. I was also noting the actual errors not making it through the other night while working on #196. If you make a PR to fix unwrapVcsError(), I'll merge it 😄

Sorry, it looks like I was mistaken. I've ran a few tests with invalid repo urls and the original error only contains the string exit status 1. The actual error message is already captured from the command output and unwrapVcsErr propagates that correctly. For this particular case it wouldn't add much value to include the original error. I'd be interested to know if it actually contained some useful information for the particular case you mentioned when working on #196.

Eh...it was late, and I was debugging a massively concurrent test, so I don't remember exactly :/ It may have been that I didn't have the fix from #204 yet at that point (I later adapted it into #196).

This issue was moved to golang/dep#416


Login not works on embed

Describe the bug
We own the paid version of Orchest and would like to use the URL inside an . The embed works normally, but when logging in the user is always redirected to the same page. The projects page does not open.
Expected behavior
When logging in with orchest, even in embed form, I would like the user to be redirected to the projects page.
To Reproduce
Steps to reproduce the behavior:

Create HTML simples page and run in localhost
Use  to embed deployed version of orchest, with auth server
Login with valid credentials
See same page. User is not redirected.

Environment

OS: Ubuntu 22.04.1 LTS
Browser (e.g. Chrome): Chrome Version 107.0.5304.87 (Official Build) (64-bit)
Orchest's version (in the settings page): v2022.10.5

Relevant conversation that ensued: https://community-chat.orchest.io/t/4977127/Hello-guys-I-m-from-Dadosfera-and-I-m-facing-a-problem-when-

Marked #wontfix for the time being. As mentioned in the public Slack conversation, we currently don't have the bandwidth to add the necessary configurability to make the  version work. We'd be open to a PR for it though :)!


don't replicate the deleted documents

1.0.5_agent version of #5355

thanks Seangchan! I suggest to keep this one opened for the next week or so, until we run a few more tests in testbed.

The original patch was not cleanly applied due to other changed. Definitely we should keep this open until we test. (There might be a bug)

Also applied to production agents, feel free to merge it.


Update formatting-text.rst

The links are updated in the exact location

Summary

Ticket Link

Thank you for your PR. Unfortunately as the source repo has been deleted, we're not able to merge these changes. We really appreciate your contribution! :)


Python: Catch correct error for does_collection_exist

Motivation and Context
Fixes #6949.
Description
Catches the correct error for does_collection_exist.
Contribution Checklist

[x] The code builds clean without any errors or warnings
[x] The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
[x] All unit tests pass, and I have added new tests where possible
[x] I didn't break anyone :smile:

Python 3.10 Test Coverage Report • FileStmtsMissCoverMissingTOTAL652274789% report-only-changed-files is enabled. No files were changed during this commit :)
Python 3.10 Unit Test Overview

Tests
Skipped
Failures
Errors
Time

1533
1 :zzz:
0 :x:
0 :fire:
23.427s :stopwatch:

@0xMihir hi there, this change looks to have caused the following integration test to fail: https://github.com/microsoft/semantic-kernel/actions/runs/9687441955/job/26732085226#step:7:350


ISSUE-917 Test mode-UI: Validate test case data on clicking

Test mode validation integrated on UI, when the user tries to save test case.
@shahsank3t  please review and comment thanks in advance.

@sameer79 can you fix the conflicts, please.


Support for lengthening of vowels for emphasis

ichi.moe messes up with things like "歩いたぁ". It separates it into "歩" and "いたぁ", and gets confused.
I think that just removing these small characters (ぁ,ぃ,ぅ,ぇ,ぉ) when querying could work.

Thanks, I agree it's a good idea, I'll think about it

also add という? Right now, it separates into と and いう, which doesn't fully convey the meaning.
"〜という is a phrase with a wide array of functions, but it always denotes that what it's marking is based on hearsay or something that's said by people." - tofugu.com


[About Us] Lowercase company name in the content section of the page in EN localization

Environment: Windows 11 Home Version 22H2 Build	22621.2506
Chrome Версія 118.0.5993.118 (Official build) (64-bit)
Reproducible: always
Build found:
Preconditions

https://zero-waste-staging.onrender.com/en site is opened in browser
'About Us' page is opend

Steps to reproduce

Navigate to the third line of About Us container

Actual result
The main goal of zero waste is to move to a circular economy, where there is no garbage as such, and what is called garbage becomes a valuable resource. is displayed

Expected result
The main goal of Zero Waste is to move to a circular economy, where there is no garbage as such, and what is called garbage becomes a valuable resource. is displayed
User story and test case links
E.g.:User story
[Test case] https://jira.softserve.academy/browse/ZER-255
Labels to be added
"Bug", Priority ("pri: high"), Severity ("severity: low"), Type ("UI").

Not a defect. Text from official ZeroWaste site
https://zerowastelviv.org.ua/pro-zero-waste/


jst.js is not being generated in .tmp\public folder, on app startup

Not sure exactly why this is happening, but moving 'jst:dev' under 'copy:dev' in compileAssets.js fixes the problem. Noticed on 0.12RC3

//tasks\register\compileAssets.js

module.exports = function (grunt) {
	grunt.registerTask('compileAssets', [
		'clean:dev',
		'less:dev',
		'copy:dev',
		'jst:dev',  // <-- moved after copy:dev
		'coffee:dev'
	]);
};

I figured out, that the server has to be lifted twice, because it tries to create the templates, but they're not there yet. After this step they'll get moved and/or created.

Not sure about this. I've noticed, that jst.is is generated "on the fly", I.e. when sails is started and template file is being saved, but not at the moment of actual server lifting.
Will try to check this again.

Just found the same issue a bit down the list:
https://github.com/balderdashy/sails/issues/3367

Thanks @muradaliyev, closing in favor of #3367.


0xChat is disrespecting Amber?

https://github.com/greenart7c3/Amber/issues/151#issuecomment-2503454963

https://github.com/greenart7c3/Amber/issues/151#issuecomment-2503454963

Working on it 👍


Implement CollapsingToolbar using Jetpack compose

I am trying to implement collapsing toolbar in my Detail screen using Jetpack compose with the idea taken from sunflower Google Github project : https://github.com/alirezaeiii/Compose-MultiModule-Cache/blob/master/feature_list/src/main/java/com/android/sample/app/feature/list/ui/detail/DetailsScreen.kt
val toolbarHeightPx = with(LocalDensity.current) {
        278.dp.roundToPx().toFloat()
    }
    val toolbarOffsetHeightPx = remember { mutableStateOf(0f) }
    val nestedScrollConnection = remember {
        object : NestedScrollConnection {
            override fun onPreScroll(available: Offset, source: NestedScrollSource): Offset {
                val delta = available.y
                val newOffset = toolbarOffsetHeightPx.value + delta
                toolbarOffsetHeightPx.value = newOffset.coerceIn(-toolbarHeightPx, 0f)
                return Offset.Zero
            }
        }
    }

    Box(
        Modifier
            .fillMaxSize()
            // attach as a parent to the nested scroll system
            .nestedScroll(nestedScrollConnection)
    ) {
        DetailsContent(
            scrollState = scrollState,
            onNamePosition = { newNamePosition ->
                // Comparing to Float.MIN_VALUE as we are just interested on the original
                // position of name on the screen
                if (detailScroller.namePosition == Float.MIN_VALUE) {
                    detailScroller =
                        detailScroller.copy(namePosition = newNamePosition)
                }
            },
            item = item,
            imageHeight = with(LocalDensity.current) {
                420.dp + toolbarOffsetHeightPx.value.toDp()
            },
            sendNotification = sendNotification,
            contentAlpha = { contentAlpha.value }
        )
        DetailsToolbar(
            toolbarState, item.name, pressOnBack,
            contentAlpha = { contentAlpha.value }
        )
    }

When we scroll up it works as expected but when we scroll down, it will not sometimes fully scrolled. toolbarOffsetHeightPx should become 0 when we scroll down, but sometimes it is a negative value that cause image does not fully scrolled. It is not stable at all and 0 or any negative value may happen. it happens since we have :
imageHeight = with(LocalDensity.current) {
                420.dp + toolbarOffsetHeightPx.value.toDp()
            }

Same story exist in Sunflower collapsing toolbar. Why is that and how to resolve it?

Please see the new implementation in https://github.com/android/sunflower/blob/main/app/src/main/java/com/google/samples/apps/sunflower/compose/plantdetail/PlantDetailView.kt which should have this issue addressed

Yes, thank you for your fix. Then why we need to observe NestedScrollConnection when we are not using toolbarOffsetHeightPx no longer? That can be removed.


[rps] Fix RPS linting configuration

Seems like the lint:check command was broken recently. This fixes it.

I set this up to also run Prettier on files that ESLint doesn't check... Why is this breaking?

@Alonski sorry I missed that this was only for scss and json. Fixed.

I ran into the above problem again. It may be related to this https://github.com/okonet/lint-staged/issues/677.


dotnet test swallows unit tests

From @DerAlbertCom on Friday, August 9, 2019 12:35:27 PM
dotnet swallows silently xunit tests (maybe also test from other test frameworks) when there is a problem on the test discovery. I filed the same under: https://github.com/xunit/visualstudio.xunit/issues/164
Steps to reproduce
Checkout the repository https://github.com/DerAlbertCom/MisbehavingUnittestRunners run dotnet test. More details why the problem occurs is also there.
Expected  behavior
At least the exception within the test discovery shows up. It would be better if it is possible to give more detail on exact type or test method.
Actual behavior

In the sample repository are 6 Unit Test, 2 of them get swallowed without any hint because of an exception within the test discoery on one test.
Environment data
.NET Core SDK (reflecting any global.json):                                                                              Version:   2.2.301
 Commit:    70d6be0814

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.18362
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\2.2.301\

Host (useful for support):
  Version: 3.0.0-preview7-27912-14
  Commit:  4da6ee6450

.NET Core SDKs installed:
  2.1.508 [C:\Program Files\dotnet\sdk]
  2.1.701 [C:\Program Files\dotnet\sdk]
  2.1.801 [C:\Program Files\dotnet\sdk]
  2.2.108 [C:\Program Files\dotnet\sdk]
  2.2.204 [C:\Program Files\dotnet\sdk]
  2.2.301 [C:\Program Files\dotnet\sdk]
  2.2.401 [C:\Program Files\dotnet\sdk]
  3.0.100-preview7-012821 [C:\Program Files\dotnet\sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.12 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.2.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.2.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.12 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.2.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.2.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.0.0-preview7.19365.7 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.1.12 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.2.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.2.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.0.0-preview7-27912-14 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 3.0.0-preview7-27912-14 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download

Copied from original issue: dotnet/cli#12187

@livarcocc could you run this with diag logs enabled and share them here?

@ShreyasRmsft I just transferred the issue here.
@DerAlbertCom  can you share diag logs here so that this can be further investigated?

@ShreyasRmsft @livarcocc  you now that there is a repository with an easy reproduction sample, and a lot more details  https://github.com/DerAlbertCom/MisbehavingUnittestRunners
But anyway :) here the logs.
diag.host.19-08-12_19-59-49_08946_6.log
diag.log

@DerAlbertCom i took a quick look. The diag logs are basically open for the test adapters to use as they please. The test host process simply invokes the adapter and listens to exceptions if any. In this case the xunit adapter did not throw any exceptions.
I know for a fact that mstest does log the reason/exception if any when discovery has issues. I would recommend you either try and debug through the xunit adapter to see why there are no logs.

@ShreyasRmsft thank for the information.
I filed already the bugs under https://github.com/xunit/visualstudio.xunit/issues/164 and https://github.com/xunit/visualstudio.xunit/issues/165 no reaction so far.

@DerAlbertCom since all of these are open source you should be able to just add a throw in the discovery code of the xunit adapter and see who is handling/catching it.

Changing how errors are handled and reported in discovery would have unforseen impact on existing adapters, because discovery heavily relies on skipping some errors in adapters which it cannot load.


⚠ Samsung has degraded performance

In 0f46e56, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2623 ms

Resolved: Samsung performance has improved in f3bb0f5.


Association Error

I have this
@Table({
  tableName: "peso_productos"
})
export class PesoProducto extends Model<PesoProducto> {
  @ForeignKey(() => Vendedor)
  @Column
  vendedor_id: number;

  @BelongsTo(() => Vendedor, "vendedor_id")
  vendedor: Vendedor;
}

Vendedor side:
  @Table({
    tableName: "vendedores"
  })
  export class Vendedor extends Model<Vendedor> {
    @HasMany(() => PesoProducto)
    pesoProductos: PesoProducto[];
  }

And just initializing sequelize throws this error
SequelizeAssociationError: You have used the alias vendedor in two separate associations. Aliased associations must have unique aliases.

What I'm doing wrong?

I just figured out what was happening, I was initializing sequelize twice. You can close this issue guys and btw great library 👍


Removed references to dublincore submodule

@hyi Please review this code change. It's quite a bit of change - so take your time. Though I did lot of testing with resource creation/update for various resource types on my local machine, we also need to do quite a bit of testing either on sandbox or playground before we can merge into develop.

@pkdash - For the purposes of testing on as close to live data as we can, beta's resource data and database have been migrated to sandbox.
Please verify that:

Existing resources render themselves as expected
New resources are equally compliant

If you have an account on beta, you can use these same credentials on sandbox

I tested and was unable to find any unknown problems (and known problems remained the same)

@dtarb Should I then create a pull request for this branch or we need to do more testing?

I think create a pull request.  Time is better spent on unit testing not hand testing.


No documentation at all on how to get the pipelines for example. A link to the rest API does not help

I have no idea how to use this API. I hope Microsoft guys can take some time to write some useful API documentation. Wasting of timing trying to find some information is the feeling I'm left with when trying to find a way around Microsoft created things.

credentials = BasicAuthentication('', ado_personal_access_token)
connection = Connection(base_url=organization_url, creds=credentials)
pipeline_client = connection.clients_v6_0.get_pipelines_client()
pipelist = pipeline_client.list_pipelines("projectname")
# pipelist is now a list of Project objects

The Pipeline objects are pretty useless though - there doesn't seem to be any way to find a link between a git repo and a pipeline, or a build and a pipeline, even though both can be seen in the ADO portal itself.


Open results in VisIt

Dear all,
I've got some issues trying to open results produced by MFEM in VisIt. For example, after running Example5 and trying to open the file Example5_000000.mfem_root, I've got the following:

VisIt could not read from the file "/u/artemyev/software/mfem-3.0.1/examples/Example5_000000.mfem_root".
The generated error message was:
There was an error opening /u/artemyev/software/mfem-3.0.1/examples/Example5_000000.mfem_root. It may be an invalid file.
VisIt tried using the following file format readers to open the file: Silo
If you know the specific format reader VisIt should use to read this data, you can use Open As... (GUI) or '-o , (CL arg.) and identify that specific reader for VisIt to try. This will possibly give more information on the exact error.

MFEM results are represented not in Silo format, obviously. But I didn't find any JSON support (plugin) in VisIt (I tried version 2.9.2 on Linux Mint 64bit).
So, how should I do that?
Thank you,
Mikhail

Hi Mikhail,
It looks like Visit is guessing that it is a Silo file.  If you select Open File from the File Menu, there should be an open file as type drop down menu.  You should be able to select MFEM in there which will fix your problem.
Cheers,
Aaron Fisher

Hi Aaron,
Thank you for the reply. Actually, I have tried this approach, but I haven't found MFEM in the list of the supported types. I'm looking at the list right now, and there are M3DC1, M3D, MFIXCDF, MFIX, MM5, MatrixMarket and Miranda types started with 'M' (the list is ordered alphabetically). No MFEM, though.
Best,
Mikhail

Hi Mikhail,
Hmm, can you doublecheck your version of Visit in the Help->About page?  I believe the MFEM support arrived at version 2.9, so it should be in there.
Cheers,
Aaron

Aaron,
Yes, it is the version 2.9.2. But I finally found where I was wrong - I installed VisIt incorrectly: I just unpacked an archive which contained executable files, while I was supposed to run a special script for unpacking and installing, and that, turns out, is crucial.
Now, I see the MFEM file type in that list.
Thank you!
Best,
Mikhail

Mikhail,
Ahh, good catch.  I'm glad it's working for you now.  Happy computing.
Cheers,
Aaron


dependabot: added tests/extendrtests to the directory to keep track of

this fixes what happened in #774.

I've tried to enable this on https://github.com/cgmossa/extendr to see if it made an effect or PRs.. and I honestly don't think this directories thing is supported. So I'll leave this open, but it needs.. a miracle?


Mix.Config is deprecated

When compiling this package, there is a warning given:
warning: use Mix.Config is deprecated. Use the Config module instead
  config/config.exs:3

The only way I'm aware of to fix this is to replace use Mix.Config with import Config, but this does mean that the code will no longer be compatible with older versions of Elixir.  Only versions 1.9 and older will be supported with this change, so it would correspond with a major  (?) bump in the version number. (e.g. to v1.0.0 or at least v0.6.0)

Should be resolved by #13


Add support for env vars instead of CLI arguments?

It's a matter of style, but it shouldn't be too hard to implement, doesn't bloat the code too much and some people (like me) would much rather have that (instead of running the risk of clashing with other extensions defining their own args).
Would you be open to a PR on this?

Sorry about the long delay -- yep would be totally fine with a PR! Makes sense for integrating with other test runners on top of minitest for sure.

What do you think these should be named? The only source for inspiration I found was https://github.com/bahmutov/snap-shot-it#advanced-use, but I didn't feel very convinced. I thought that jest had some mechanism like this where we could draw inspiration from, but I was wrong.
Do you have any examples you wanna follow? Maybe some names in mind already? If not, I'd say let's just roll with UPDATE_SNAPSHOTS and LOCK_SNAPSHOTS.

Hi @pkoch , not sure if you are still interested, but I would be open to a PR for this. My recommendation would be MT_UPDATE_SNAPSHOTS and MT_LOCK_SNAPSHOTS, since there is a precedent for using the MT_ prefix for Minitest.
https://github.com/minitest/minitest/blob/a2c6c18570f6f0a1bf6af70fe3b6d9599a13fdd6/lib/minitest.rb#L141

Uff, it's been a while. I'm not using this anymore. 😅
Let's close this for now. I'll open up a new issue if I ever get back into a contributing position.


[BIT-601] Scaling law on EMA loss

BIT-601 Scaling law on EMA loss
The neural language model scaling law [1] is typically meant to be computed on a loss averaged over the entire training data. Currently it is computed within-batch only, which frequently sees losses below 1.69 (the natural entropy of text).
Here we now compute the scaling law and the resultant effective number of model parameters on the exponentially moving average loss for a server, which should greatly improve the definition of the result.
[1] (OpenAI scaling laws) Kaplan, Jared, et al. "Scaling laws for neural language models." arXiv:2001.08361 (2020)

Comparative analysis of BIT-601
We compare the neuron stats of two types of nakamoto validators, one on current master branch, and the other on the BIT-601 branch. The change from master is that BIT-601 now applies the scaling law on the average loss across multiple batches, instead of on each batch_loss separately like master.
We expect a change in base_params_nxt and shapley_values_nxt from master to BIT-601. We measure the probability distribution shift and see that overall BIT-601 has smaller values.

Generally avg(batch_losses) > 1.69, because over a lot of batches we start to be limited by the natural entropy of test, which means that BIT-601 will rarely clamp in the scaling law.
Frequently batch_loss < 1.69, because small individual batches on fine-tuned data can often get the next token prediction correct, which means that master often clamps the scaling law.
Generally when batch_loss < avg(batch_losses), then despite clamping on batch_loss this inequality still seems to be the case in the result obtained where base_params_nxt is then larger in master compared to BIT-601.
However, since less clamping happens in BIT-601, we expect a more accurate scoring and separation of model sizes because the noise due to clamping is removed, which means that larger models will be able to separate themselves better.

master: avg(scaling_law(batch_loss))
# estimate the effective number of model parameters from the batch_loss
_num_params = scaling_law_loss_to_params(_loss)

BIT-601: scaling_law(avg(batch_losses))
# estimate the effective number of model parameters from EMA loss
_num_params = scaling_law_loss_to_params(torch.tensor(stats['loss_nxt']))


Defined Role

@Songkey1
@hoonkim
@zzttt
@왕석
@TaeyoungJang

저 @왕석 대신에  @seok0721 로 사용할게욥

we should make synonym dictionary
https://github.com/hoonkim/rune/wiki/Synonym---Definition-for--our-words
write our own words for information