Handlebars Compatibility

Not sure if this is the right place to file this issue, perhaps the main purifycss repository is more appropriate, but anyway. I'm trying to use this plugin together with some Handlebars templates, like so:
new PurifyCSSPlugin({
    basePath: __dirname,
    resolveExtensions: ['.hbs'],
    paths: ['resources/assets/views/*.hbs'],
    purifyOptions: {
        rejected: true
    }
})
...
<body>
  <main class="wrapper">
    <nav class="navigation" id="main-navigation">
    </nav>
...

But no luck. All css rules are removed (e.g. .wrapper, .navigation) and I end up with an empty file. Does this plugin only work for HTML files?

Can you try against vanilla purify so we can rule out a plugin specific issue?

I kinda ditched handlebars for an all React solution by now, so I am not really concerned about this issue anymore. Maybe I should close it then? Or perhaps someone else is willing to take this up.

Yeah, let's close. Thanks. 👍

almost the same issue here... my css all remains... seems nothing happens
new HtmlWebpackPlugin({
    filename: 'index.html',
    template: 'assets/views/index.handlebars'
}),
new ExtractTextPlugin({
    filename: 'css/bundle.[contenthash].css',
    allChunks: true
}),
new PurifyCSSPlugin({
    moduleExtensions: ['.handlebars'],
    paths: [
        glob.sync(path.join(context, 'assets/views/**/*.handlebars'))
    ],
    verbose: true,
    purifyOptions: {
        rejected: true
    }
})

and somewhere else in a .scss file
....
.iShouldBeRemovedAsNoOneIsUsingMe {color: black}

after compilaiton.. the output file bundle.dc0832b85be1c37669971edfa8db533e.css
...
.iShouldBeRemovedAsNoOneIsUsingMe{color:#000}

Can you see anything in the verbose output?

@bebraw yes .. i see these
.....
89% additional chunk assets processing
1ms additional chunk assets processing
 90% recordingAssets to purify:
Assets to purify:
Assets to purify:
Assets to purify:
Assets to purify:

4ms recording
 91% additional asset processing
.....

at first i thought maybe my paths were leading empty or something but logging it outputs the right array of files
console.log(glob.sync(path.join(context, 'assets/views/**/*.handlebars')))

->

[ '/Users/milewski/Documents/Code/projectX/source/assets/views/index.handlebars',
  '/Users/milewski/Documents/Code/projectX/source/assets/views/partials/facebook.handlebars',
  '/Users/milewski/Documents/Code/projectX/source/assets/views/partials/footer.handlebars',
  '/Users/milewski/Documents/Code/projectX/source/assets/views/partials/google.handlebars',
  '/Users/milewski/Documents/Code/projectX/source/assets/views/partials/head.handlebars' ]

Ok, that print comes from https://github.com/webpack-contrib/purifycss-webpack/blob/master/src/index.js#L41 . You could dig into the query above to understand why the results are empty. Maybe there are no css files to look up against? Esp. investigating compilation.assets might reveal a lot.

@bebraw the reason why it is failing to match any files is:
here if i console.log(asset.name, chunkName) i get
js/bundle.218ce7d00e9ec0cea3f51c8cb985f1a3.css js/main
css/bundle.d39efdc6120e1c5e1b3e09c041f49c48.css js/main
css/bundle.d59f8dc7083d5cec294a24c3afd7ca54.css js/main

so that filter function can never match any file asset.name.indexOf(chunkName) >= 0, because i am used a fixed name.. bundle instead of [name]..
however switching the names to allow it to match something
new ExtractTextPlugin({
    filename: 'css/[name].[contenthash].css',
    allChunks: true
})

i will finally get:
Assets to purify: js/main.218ce7d00e9ec0cea3f51c8cb985f1a3.css
Assets to purify: css/main.d39efdc6120e1c5e1b3e09c041f49c48.css
Assets to purify: css/main.d59f8dc7083d5cec294a24c3afd7ca54.css

however i get a crash together with it.... and webpack exits..
...
/Users/milewski/Documents/Code/projectX/node_modules/minimatch/minimatch.js:116
    throw new TypeError('glob pattern string required')
          ^
TypeError: glob pattern string required
...

Ok. There's likely some logic missing.
I'll try to look into this once I have some time (might be weeks).

thats alright.. meanwhile i did find the reason of the crash.. here is returning me an array of array of files...
so by doing this fixed the issue and everything is working fine now
compilation.assets[name] = new ConcatSource(
    purify(
        ...filesToSearch, <-- here ...
        asset.source(),
        {
            info: options.verbose,
            minify: options.minimize,
            ...options.purifyOptions
        }
    )
)

Ok, if you can PR a fix that would be great. Most likely the search algo needs a little tweak. It needs a test too (logic is fully covered by tests).

@Milewski Any chance for a little project to study? I have hard time figuring out the problem to fix and I can't get the fix done without.

@bebraw while i was making a sample i found that the issue i raised of https://github.com/webpack-contrib/purifycss-webpack/issues/57#issuecomment-278246155 was actually my mistake i was sending an array of array instead of just an array
paths: [glob.sync(path.join(context, 'assets/views/*.handlebars'))]

should be
paths: glob.sync(path.join(context, 'assets/views/*.handlebars'))

however the main problem is when i set my filename to a fixed name instead of using [name]
Works
new ExtractTextPlugin({
    filename: 'css/[name].[contenthash].css',
})

Doesn't work
new ExtractTextPlugin({
    filename: 'css/bundle.[contenthash].css',
})

here is a sample
https://gist.github.com/Milewski/077df081ad03a1e7884316b2863c6d17

@Milewski Cool. Thanks. The current code might capture the first case. An array of array should trip at validation (good extra test to add, though). The latter is more puzzling.
About output.filename, [ext] doesn't work there (by design?). This could be a webpack bug, though. I think the assumption is that it's going to be .js always so that might explain the current state.

@bebraw the[ext] doesn't work even when the entries are just .js, I had reported it as a webpack bug https://github.com/webpack/webpack/issues/4276 on the main repo but looks like a bot comes closing all the issues that wasn't following the default issue template...

@Milewski Thanks for bringing that up. Re-opened.


Workaround for ky-universal not being able to be used with Jest

This is not a bug report or an issue with ky-universal.
I'm sharing a solution to a problem I had, hoping it would be visible to people having the same problem if I put it here.
I'd be glad to move it to somewhere else if this is not the best place to share this.
TLDR;
I wasn't able to import ky-universal in a Jest test file.
I worked around this by creating the following file:
jest.setup.js:
const fetch = require('node-fetch');

globalThis.fetch = fetch;
globalThis.Request = fetch.Request;
globalThis.Headers = fetch.Headers;

And adding this to jest.config.js:
module.exports = {
   ...
   setupFiles: ["./jest.setup.js"],
   ...
}

More details
ky-universal is an ES6 module.
No matter how hard I tried, I was not able to make Jest load an ES6 module.
It got transformed to something like this, probably by Babel:
 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,global,jest){import ky from "ky";

And imports can't be anywhere except at the top level in ES6 Modules.
With ky, I was able to get it transformed to cjs by installing esbuild:
yarn add -D esbuild esbuild-jest
and adding this in my jest.config.js:
module.exports = {
   ...
   transform: {
     "^.+\\.(t|j)sx?$": [
       "esbuild-jest",
       {}
     ],
   },
   transformIgnorePatterns: [
     '/node_modules/(?!ky)'
   ]
   ...
}

But ky-universal is doing top-level await inside it, and neither esbuild-jest nor ts-jest was able to process top level await.
I tried so hard to make this work with just ES6 support and not using a bundler like esbuild. But I had to conclude this is pretty much impossible after two days of digging.
So I tried to start with just ky, which works fine when converted into cjs by esbuild, and started putting stuff into globalThis, one by one, by looking at the errors that came up.
For my code, errors stopped appearing after I assigned the above three things, but there could be more.
If it happens just check the error to see what's missing and add it to globalThis.

Thank you @itsfarseen 👍
After adopting your solution, it worked well!
Note:
In my project, node-fetch v3 didn't work. Only v2 worked


update chai and sinon-chai to latest revisions

Upgrade to<EMAIL_ADDRESS>and<EMAIL_ADDRESS>these are developer only dependencies.

Coverage remained the same at 81.68% when pulling 3238fd0989a900783281b1c55052871542a0c777 on upgrade-chai into ff6323d4ed6edc8f3ca36a0920871cf02fb3c6b8 on master.


Zarf Init should warn when the binary is out of sync with a release

Is your feature request related to a problem? Please describe.
If I brew upgrade zarf, I may forget to download the release associated with the updated binary.
Describe the solution you'd like
Warn / remind users that the binary is out of sync with the release.
Describe alternatives you've considered
Remember to download the associated release when I update the binary
Additional context
Blame @jeff-mccoy

Due to the way that homebrew work, this should no longer be an issue as zarf is place in a new directory on upgrade, can you confirm this is still an issue @ntwkninja?

If I am on the latest Zarf version the current workflow is good. If I am on an older version of the binary and did not execute a zarf init, or deleted the previous zarf init file I could run into parity issues because zarf init is built to download the latest init package.
Steps to Reproduce

Manually install Zarf v0.20.0 binary (aside from the $PATH, this would be the same as brew install zarf and failing to brew upgrade when a future version is released)
Check Zarf Version and Clone Repo

➜  tmp  `which zarf`
/usr/local/bin/zarf
➜  tmp  `zarf version`
v0.20.0
➜  tmp  `git clone https://github.com/defenseunicorns/zarf.git` && `cd zarf`

Run zarf init

➜  zarf `zarf init`
It seems the init package could not be found locally, but can be downloaded from
https://github.com/defenseunicorns/zarf/releases/download/v0.21.1/zarf-init-arm64.tar.zst

Note: This will require an internet connection.
? Do you want to download this init package? `Yes`

# downloads v0.21.1 init package to /usr/local/bin.

Note: brew install currently only supports the current version of zarf so v0.20.0 had to be installed manually because the tap only contains the latest version.
➜  tmp `brew install<EMAIL_ADDRESS>==> Auto-updated Homebrew!
Updated 1 tap (homebrew/core).

Warning: No available formula with the name<EMAIL_ADDRESS>==> Searching for similarly named formulae...
Error: No similarly named formulae found.
==> Searching for a previously deleted formula (in the last month)...
Error: No previously deleted formula found.
==> Searching taps on GitHub...
Error: No formulae found in taps.

Sounds like an edge case that could be covered by docs simply encouraging users to upgrade or manually download an init package that corresponds to their zarf version.
If the init packages will always be backwards compatible with zarf binaries then this issue can be closed.

Also I worded the initial issue very poorly but this should capture this dialogue should capture the initial intent

This happens because of this code: https://github.com/defenseunicorns/zarf/blob/b478dabe0395506d1668f6cbac04881b67c213de/src/cmd/initialize.go#L62 It tries to strictly parse the semver but semver does not expect the leading "v" in the version string and errors out.

Are you sure about the v prefix?

https://semver.org/#is-v123-a-semantic-version

Yes, StrictNewVersion does not use that regex:
// Parsing here does not use RegEx in order to increase performance and reduce
// allocations.

Lol I seem to recall changing to strict, but don't remember why now 😑

Lol I seem to recall changing to strict, but don't remember why now expressionless

Yeah that whole block of code looks to have come from a single commit, but that may have been a squash and merge.

Maybe worth a PR back to that project potentially too.  At least to fix their spelling mistakes:
// If you want to coerce a version, such as 1 or 1.2, and perse (sic) that as the 1.x
// releases of semver provided use the NewSemver() function.

Per their README though that is the design of the StrictNewVersion.  It adheres to the spec precisely (so doesn't try to coerce the string into a semantic version)

I only uses that library because helm already used it and that was a last-minute fix to get around some release issues for zarf init with homebrew.  Probably should just drop the library and use a simple string parsing or regex.

Yeah that is the only thing it is used for. I can change that in the PR to just drop it entirely.


cant flash nrf52 dongle using nRFconnect for desktop.

I am using nRF52840 dongle with raspberry pi 4 to create a thread network. I downloaded nRFconnect for desktop to flash the hex files into the dongles.
I successfully flashed a dongle when i downloaded a hex file from https://golioth.github.io/golioth-openthread-demo-docs/docs/create-rcp#build-your-own. Its rcp hex file.
but when i was try to flash the dongle with the hex file generated using https://openthread.io/codelabs/openthread-border-router-ipv6-multicast#2 i was unable to write the hex file. The write option was disabled and could only be used when i select the Enable MCUboot. Not sure why.
When i select Enable MCUboot and try to write the hex file it shows an error,
mcu boot failed with error operation, program not supported error when starting fw program
can you please help me to solve this problem.
i want to to flash both rcp and ot-cli-ftd.hex into the dongles as i need to make a thread network. and if how can i flash the dongle from the raspberry pi command line, what packages i need to install and what commands will be used if i could get this information.

Closing stale issue.


:book: Add sdwilsh to CONTRIBUTORS.md

Signed-off-by: Ettore Di Giacinto<EMAIL_ADDRESS>
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #856

Codecov Report

Merging #859 (7210236) into master (fa152b2) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##           master     #859   +/-   ##
=======================================
  Coverage   21.60%   21.60%
=======================================
  Files          21       21
  Lines        1523     1523
=======================================
  Hits          329      329
  Misses       1142     1142
  Partials       52       52

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


There aren’t any releases here

Fontmin-app cannot be downloaded.

here is it. releases :smiley: , thx


Dropzone.js error on uploading file with 32MB+ size

Gitea version (or commit ref): 1.12.3
Git version: 2.28
Operating system: win10 station, win server 2008 server
Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[x] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[x] Not relevant

Log gist:

Description
I'm unable to upload any files above 32MB despite setting the MAX_SIZE attribute.
Whenever I try to upload anything bigger than 32MB, the dropzone.js throws an error (see below).
Anything below 32MB works well. Is there a hard limit that cannot be reconfigured?
This is my attachment section in app.ini.
[attachment]
ENABLED = true
MAX_SIZE = 512
MAX_FILES = 2
STORE_TYPE = local
PATH = D:\GiteaAttachments
ALLOWED_TYPES = */*
Screenshots

Are you using a reverse proxy such as Nginx or Apache HTTPD?

Are you using a reverse proxy such as Nginx or Apache HTTPD?

Yes, we are hosting Gitea on an IIS server so the upload limit was due to IIS settings.
We have changed the upload limit in the web.config and now the upload is correct.
Thank you for helping!


Seems like only plans directory is used from this whole repository

Hi, is there any reason for this repository to contain roles/, group_vars/ and other files expect for readme and plans/?
The plan themselves do not seem to include any roles, etc.
CC: @phracek

We plan to convert this shell into a playbook, as we do it internally.
I will do it as a rest work.

Ok, thanks for the information :).


refactored magic strings and took them out to consts

Refactored 'magic strings and number' from Models and Modules(1-12)
Created new consts files for saving strings and numbers

done

joined db-refs with db-collections


Cannot parse alias.* as column definition in select statements

statement like "select m.* from modell m  where m.name = null" fails

Support of * select statements in combination with aliases now supported.


fix delete an image of multiple images field

This PR to fix issue #5578

Thanks for the correction. I've tried to upgrade my voyager to v1.5, but the problem still out there.
My issue was updated.


Does not parse JSON by default

I think it would make sense to automatically parse JSON with the express json parser, otherwise people might get confused why their Request-Bodies are empty.
Looking at the code, I think the idea was that it is supposed to do that, though I found out that it does not.
Making the following changes to the src/plugin/write/handlerFile.ts would fix this:
//...
export const handler = express();

// Add JSON-Parsing
handler.use(express.json());
handler.use(express.urlencoded({ extended: true }));

//...

It was applied in 1.0.2.


⚠ Bofrost.lu has degraded performance

In 434240f, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 3033 ms

Resolved: Bofrost.lu performance has improved in 9689810 after 9 minutes.


Add script to generate ONE_OF_LIST values

Change .cogs tracked files to .cogs/tracked in Makefile (this is updated in the latest release of COGS)
Fix an error in id-generator-template.py if there were no IDs
Add create-data-validation.py and cogs_apply step to the automated_mapping

Unfortunately, gspread-formatting does not add the dropdown menu to the cell. If you hit ENTER or double click on a cell with the ONE_OF_LIST, it will show the list (in the correct order). To get the dropdown arrow, you need to select the range and go to Data -> Data Validation and select "Show dropdown list in cell".
This is potentially something we could add support for in COGS, but we will need to write our own version of the gspread_formatting.set_data_validation_for_cell_range function. This might be something to discuss in COGS, though. It will probably be a pain to implement, but it seems important...

I will merge this now and fix it up.. There are some things that James does not like to see in here :D which were wrong in my branch. Like directly referencing .cogs. Thanks! I will take it from here :)


BUG:  The text link pop-up window does not pop up when it is full screen

What browser are you using?
chrome(64)   version 115.0.5762.4

Reproducible demo link
https://grapesjs.com/demo-mjml.html

Describe the bug
How to reproduce the bug?

Drag a text

Click the mjml editor full screen button

Double-click the text and click the rich text link （or ctrl+k）

What is the expected behavior?
Pop-up pop-up box configuration link
What is the current behavior?
no response

set z-index


[DOC] Documents related "Installing as a Windows Service" need to be update

The current document which is discredited "Installing as a Windows Service" [1] should be updated,
Under the Prerequisites, it should update and can recommend that we can use  "Yet Another Java Service Wrapper" (YAJSW) version 11.03 as well as version 12.13 (the latest version).
I have tested and verified this in the latest wso2is-5.8.0-beta6-SNAPSHOT  in Windows environment.
I tested with both yajsw-stable version-11.03 and -12.13a.
[1]https://docs.wso2.com/display/IS570/Installing+as+a+Windows+Service

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


(hack) Improve 'group show' output

This updates the output for the bolt group show / Get-BoltGroup
commands to better align with other show commands. The command now
lists information under colorized headers and also lists the source of
the inventory file if one was loaded.
!feature

Improved group information output
The bolt group show and Get-BoltGroup commands now display human
output in a similar format to other show commands. The json output
now includes the path to the inventory file that the groups are loaded
from.

The commit message should also list fixing the bug that the inventory file was printed even if the inventory was loaded from an env var.

bolt group show

[x] Always shows the 'all' group
[x] Prints reasonably when no inventory file can be loaded
[x] Lists the environment variable as a source if set
[x] Lists inventory groups loaded from plugins

bolt inventory show

[x] Only modifies the 'Inventory source' header for inventory show

[x] Lists the environment variable as a source if set

bolt inventory show --detail

[x] Only modifies the 'Inventory source' header for inventory show

[x] Lists the environment variable as a source if set


Set AudioStreaming interface name on default interface too.

The audio interface name is what's visible to the user in most OSs, so having it be something more descriptive than "0-Bandwidth AudioStreaming Interface" is desirable. As we already have an app-supplied interface name available here I changed the function to use that instead.

@fiskbil this change sets both default and alternate interface names the same, are you fine with that?

@fiskbil this change sets both default and alternate interface names the same, are you fine with that?

For our purpose this works well, and it doesn't change the api.


feat: Run block-proving jobs in parallel by forking world-state

Goal
We want to be able to kick off more than one prove(blocknumber) job in the prover-node at the same time.
We currently cannot do it because the prover-node has a single world-state, and building a proof modifies world-state. In particular, preparing the inputs for base rollups modifies state trees, and finalising the block modifies the archive tree.
Why?
This'll be needed for the proving integration contest, in case we generate blocks faster than the time it takes to prove them.
It may still be useful once we move to epoch proving and sequencer-prover coordination, since the same prover could be picked for generating proofs for two consecutive epochs.
How?
The easy way
Easiest approach is to keep everything as-is today, and clone the world state before kicking off a job. Eventually, once we implement Phil's world-state, we can use the writeable world-state snapshots for this.  This is what we're doing on this PR.
The not-so-easy way
Another approach is to decouple input-generation from proving. Today the prover-orchestrator is responsible for computing all inputs, but this is not strictly needed. We can have one component that generates all inputs, modifies world-state, and outputs a graph of proving jobs (as Mitch commented here). And then another component that orchestrates the execution of proving jobs exclusively based on their dependencies.
Note that this new component would be a good fit for generating a block in the sequencer, which today runs an orchestrator without proving enabled to get to a block header.
It's unclear whether this component should run everything serially (like the old block builder did), or it makes more sense to fan out circuit simulation jobs to workers (like the proving orchestrator can do now).

Benchmark results
No metrics with a significant change found.

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Proof generation
Each column represents the number of threads used in proof generation.

Metric
1 threads
4 threads
16 threads
32 threads
64 threads

proof_construction_time_sha256_ms
5,728 (-1%)
1,543 (-1%)
705
750 (-1%)
772

proof_construction_time_sha256_30_ms
11,919
3,161 (-1%)
1,413 (-1%)
1,441
1,466 (-1%)

proof_construction_time_sha256_100_ms
43,907
12,027
5,476 (+1%)
5,425
5,384

proof_construction_time_poseidon_hash_ms
78.0
34.0
34.0
58.0 (-2%)
87.0 (-2%)

proof_construction_time_poseidon_hash_30_ms
1,518 (-1%)
418 (-2%)
201
225 (-1%)
274 (+2%)

proof_construction_time_poseidon_hash_100_ms
5,626 (-1%)
1,505 (-1%)
678 (+1%)
741 (+1%)
745

L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
4 txs
8 txs
16 txs

l1_rollup_calldata_size_in_bytes
708
708
708

l1_rollup_calldata_gas
6,576
6,594
6,600

l1_rollup_execution_gas
584,256
584,425
584,582

l2_block_processing_time_in_ms
760 (-1%)
1,422 (-1%)
2,890 (+5%)

l2_block_building_time_in_ms
10,887 (-1%)
21,059 (-3%)
42,022

l2_block_rollup_simulation_time_in_ms
10,886 (-1%)
21,059 (-3%)
42,021

l2_block_public_tx_process_time_in_ms
9,081 (-1%)
19,063 (-3%)
39,913

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 8 txs.

Metric
3 blocks
5 blocks

node_history_sync_time_in_ms
7,066 (-1%)
9,915 (-1%)

node_database_size_in_bytes
12,718,160
16,883,792

pxe_database_size_in_bytes
16,254
26,813

Circuits stats
Stats on running time and I/O sizes collected for every kernel circuit run across all benchmarks.

Function
time_ms
bytecode_size_in_bytes

GasToken:_increase_public_balance
101 (+1%)
13,790

GasToken:set_portal
17.0 (+11%)
3,339

Token:constructor
123 (+29%)
23,692

FPC:constructor
94.2
13,592

GasToken:mint_public
84.3 (+3%)
10,158

Token:mint_public
99.0 (+3%)
19,034

Token:assert_minter_and_mint
99.4 (-10%)
12,925

AuthRegistry:set_authorized
47.9 (+2%)
7,812

FPC:prepare_fee
255 (+3%)
11,068

Token:transfer_public
39.0 (-27%)
44,012

FPC:pay_refund
73.5 (-4%)
15,961

Benchmarking:increment_balance
1,062
11,281

Token:_increase_public_balance
16.0 (+7%)
15,006

FPC:pay_refund_with_shielded_rebate
134 (-1%)
17,056

Public DB Access
Time to access various public DBs.

Function
time_ms

get-nullifier-index
0.181 (+13%)

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
1 leaves
16 leaves
64 leaves
128 leaves
256 leaves
512 leaves
1024 leaves

batch_insert_into_append_only_tree_16_depth_ms
10.3 (-1%)
16.6
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.8
31.7
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.597 (-1%)
0.511
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
47.8
75.7 (-1%)
131
244 (-2%)
470 (-2%)

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
95.9
159
287
543
1,055

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.488
0.465 (-1%)
0.452
0.443 (-1%)
0.440 (-2%)

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
59.3
111 (-1%)
183
352
733 (+5%)

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
109
207
355
691
1,363

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.501
0.499
0.485
0.476 (-1%)
0.501 (+5%)

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
73.0
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
133
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
0.519
N/A
N/A
N/A
N/A

Miscellaneous
Transaction sizes based on how many contract classes are registered in the tx.

Metric
0 registered classes
1 registered classes

tx_size_in_bytes
72,017
666,910

Transaction size based on fee payment method
| Metric |  |
| - |  |


fix: avoid TypeError when using sorted search

Based on #64
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[ ] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[ ] Ensure the tests and linter pass
[ ] Code coverage does not decrease (if any source code was changed)
[ ] Appropriate docs were updated (if necessary)

Towards #28 🦕

Re: "Do not merge" I meant for this to be a Draft until #64 can be merged.


Receipt for sublime_text (sublime_text.yml)

'''
You can easily make your own using this recipe like this on a Debian/Ubuntu system:
wget -c "https://github.com/AppImage/AppImages/raw/master/pkg2appimage"
bash -ex pkg2appimage sublime_text
app: sublime_text
ingredients:
dist: trusty
sources:
- deb http://us.archive.ubuntu.com/ubuntu/ trusty main universe
- deb https://download.sublimetext.com/ apt/stable/
script:

cp /usr/bin/subl ./AppRun
chmod a+x ./AppRun
cp /usr/share/icons/hicolor/48x48/apps/sublime-text.png sublime-text.png
'''

You can easily make your own using this recipe like this on a Debian/Ubuntu system:
wget -c "https://github.com/AppImage/AppImages/raw/master/pkg2appimage"
bash -ex pkg2appimage sublime_text
app: sublime_text
ingredients:
dist: trusty
sources:
- deb http://us.archive.ubuntu.com/ubuntu/ trusty main universe
- deb https://download.sublimetext.com/ apt/stable/
script:

cp /usr/bin/subl ./AppRun
chmod a+x ./AppRun
cp /usr/share/icons/hicolor/48x48/apps/sublime-text.png sublime-text.png

fricking formatting. here is the pastebin
https://pastebin.com/KYhpWLYP

nah, it doesn't work. will update it  if i manage to make it work.

here is a working version https://ptpb.pw/0_Ro.yml

those icons for formatting do not work with my browser. I should have entered ``` instead of the ''', then it would work
here is a test for md formatting

Thank you @flux242, added to https://github.com/AppImage/pkg2appimage/blob/master/recipes/Sublime_Text.yml. Would still be good to let the Sublime Text team know that an official AppImage from them would be appreciated.


Please provide support for M1 Macs

Hi Yuce,
It is impossible to run pyswip on M1 architecture (more specifically I have the M1 Pro). I have tried every combination of python SWI-PROLOG and pyswip versions to no avail.
It would be highly appreciated if you offered support for M1 arm64 architecture. SWI-Prolog is working on a Beta for it.
Kindest regards,
Amr

Hi @AmrSol a contributor updated https://github.com/yuce/pyswip/blob/master/INSTALL.md#macos-m1 for M1 Macs.

Thank you so much @yuce. Works like a charm. =)


volvomate: Infrastructure

Apologies - fat-fingered the branch target. I'm working on a flavour of this to support the Volvo Cars API, and that's not safe for consumption in this project.


Saras changes

Added notebooks that clean up and sort the SGA catalog based on morphological type and create 152x152 pixel cutouts of select SGA galaxies.

Thanks for the contributions @sgmoore1! I'll merge this PR, but we'll want to do a reorganization to separate out the SGA-2020 from the SGA-2024 stuff at some point.


what is the fastest detection model?

Sorry if it's not something I am supposed to ask here.
I understood that SqueezeDet is really fast in models for doing both of detection and classification. When you wanted to do only detection, what is the fastest model for it? I tested SqueezeDet for detection task and it seems not really fast if it's only for detection.
If anyone has ideas for this, it would be really helpful. Thanks!

if you are running the detection with only using CPU then this is the fastest among all the others out there.
if you like, you can still see darknet and run it using tiny yolo cfg and weights. it might be almost as fast as this but wont be as accurate as this
when you use CUDA enabled GPU, all this wont matter much because you can choose any model and it will run fast


Add ObjectSelector Configuration for Webhooks

Summary
This pull request introduces the capability to configure objectSelector for both podMutatingWebhook and pvcMutatingWebhook in the Helm chart. This enhancement allows users to specify which Pods or PVCs should be targeted by the mutating webhooks based on specific labels, improving the flexibility and control of webhook operations.
Key Changes

Pod MutatingWebhook:

Added an objectSelector configuration to the YAML template, enabling users to define specific labels that Pods must match for the webhook to take action.
Updated values.yaml to include the objectSelector for podMutatingWebhook, with the default set to an empty object.

PVC MutatingWebhook:

Added an objectSelector configuration to the YAML template, allowing users to specify labels that PVCs must match for the webhook to take action.
Updated values.yaml to include the objectSelector for pvcMutatingWebhook, with the default set to an empty object.

Documentation
For more details on how objectSelector works and how to configure it, please refer to the Kubernetes documentation on Matching Requests: ObjectSelector.
Additional Information

This update maintains backward compatibility by setting the objectSelector defaults to empty objects, ensuring that existing configurations will not be affected unless explicitly modified by the user.

Hi @dsvetl,
Thank you for your PR. I have a question and a suggestion:

What are the concrete use cases for this feature?
The Pod mutating webhook of TopoLVM is one of the core parts of scheduling. I'd like to emphasize that manually editing the objectSelector must be done with sufficient knowledge of what is being done, as it might break TopoLVM's functionality.

I completely agree with your concern regarding the critical nature of the Pod MutatingWebhook for TopoLVM's scheduling. Misconfiguring the objectSelector could indeed interfere with the proper scheduling of Pods using TopoLVM.
I see this feature as an advanced use case of MutatingWebhookConfiguration`s for environments with multiple StorageClasses. It allows administrators to prevent unnecessary webhook calls from affecting other controllers. In my scenario, the objectSelector can be used to reduce the number of calls to the topolvm-controller for PVCs that are not managed by TopoLVM, ensuring that the webhooks only operate on relevant resources.

The comments in the Helm chart and the description in README.md must match. It would be good if you could check.

Thanks for pointing, I found that it is should be generated via helm-docs and fixed.


Autocomplete for .get() .set() implemented

possible Fix: #24460
auto complete property name as string just like .connect()

This should be implemented for set_deferred() as well.

Closing this as stale. Feel free to ask for reopen if you want to update it or open a new PR. Thanks for your contribution in any case.


Use proper types instead of Text

For example Errors and Channels/Events etc.

Errors done in: https://github.com/pusher-community/pusher-http-haskell/pull/30

Done in: https://github.com/pusher-community/pusher-http-haskell/pull/33


Add createLoanScheme dftx

What kind of PR is this?:

/kind feature
What this PR does / why we need it:
Add createLoanScheme dftx
Which issue(s) does this PR fixes?:

Fixes part of #532
Additional comments?:

PS there is a conflict because I had to revert #562 that was not supposed to be merged.

@fuxingloh  I have resolved the conflicts


Proposal to change the Apache license to MIT

Hi @thomseddon,
What do you think of  changing the license of this project from Apache to MIT?
The Apache license requires the license header to be included in every source file which takes up at least 15 lines at the beginning of each file.
There are also many projects that have changed from Apache to MIT due to its incompatibility with the GPL license.
It seems to me that the major difference between these licenses is the added patent grant that Apache provides. Are you at all concerned about possible patent issues?

I'd be up for it, I started this a while ago and since then almost all projects I've done use MIT, happy to do this in 3.0.0

Great :)
That brings me to a related question:
We at Seegno feel that this project has enough reputation and responsibility in the community that it is worth moving to its own organization. What do you think?

Interesting idea, few questions:

what difference do you think this would make / what is the main goal?
how would it work?

I guess my immediate thought would be that this is nowhere near the popularity of some projects that don't have an organisation?

We feel that this project is the de-facto standard for implementing an OAuth2 server in node.
In our opinion, migrating to an OAuth organization (for example: oauth.js/oauth2-server) would:

Give the project a more serious tone.
Encourage developers to contribute other OAuth-related projects (such as our seegno/angular-oauth2 project which we would be happy to move as well)
We could time this with the release of 3.0.0 and introduce a more modern ES6 implementation, using Babel (we would contribute this PR, of course).

/cc @ruimarinho, @fixe

Welcome comments from anyone else on this
/cc @mjsalinger @alex-whitney

I agree on both points - moving to the MIT license will foster even more contributions and creating an organization for OAuth related work can be greatly beneficial to the node ecosystem and increase awareness both in terms of compliance and security.

I agree completely with @nunofgs.

This was done in PR #203


Add H2 dependency

Description of changes
As a part of issue #2 these changes were performed.

Added h2 dependency to pom.xml file
configured the h2 using application.properties file
Initialized the db with mock data present in data.sql file

Screenshot

wouldn't it be better to bootstrap data using spring boot?

wouldn't it be better to bootstrap data using spring boot?

How are we planning on doing that?


Stub currentUser in Test

I'm trying to stub currentUser with a fresh user (via factory_guy) in testing, but running into issues..
let user = make('user');
authenticateSession(this.application);
currentSession(this.application).set('currentUser', user);

I’m fully following the guide here: https://github.com/simplabs/ember-simple-auth/blob/master/guides/managing-current-user.md and using a dedicated endpoint for the current user, as stated here: https://github.com/simplabs/ember-simple-auth/blob/master/guides/managing-current-user.md#using-a-dedicated-endpoint
All the testing stubs that i’m seeing are with setting the user_id on the session when authenticating like authenticateSession(this.application, { user_id: user.get('id')})
I’d like to do something like authenticateSession(this.application, { currentUser: user })
Anyone done this before that can help me out and also document it?

In the guide you're linking to above we're using a dedicated service to keep the current user but you're trying to set the property on the session service itself. Also authenticateSession(this.application, { currentUser: user }) won't work as the session can not store Ember.Objects - only serializable data that can be stored in the session store as JSON (we might actually remove even that in the future and only allow atomic values like strings and integers and not even hashes or arrays).
I think the best solution in you case would be to simply stub the server response for loading the current user as that's also the most acceptance test-like approach as it would execute all of the code that loads the current user from the backend. You can use either mirage or just plain Pretender (or another solution even if you prefer that) for stubbing the response.

Got it, thanks @marcoow.  For reference, I solved it by extending the ModuleForAcceptance like this:
import { module } from 'qunit';
import Pretender from 'pretender';

var pretender;

export default function moduleForAcceptance(name, options = {}) {
  module(name, {
    beforeEach() {
      // Stub currentUser
      this.currentUser = make('user');
      let userJSON = this.currentUser.toJSON({includeId: true});
      pretender = new Pretender(function() {
        this.get('/api/v1/user', function() {
          return new Promise(function(resolve) {
            var response = [
              200,
              {'content-type': 'application/javascript'},
              `{"user": ${JSON.stringify(userJSON)}}`
            ];
            resolve(response);
          });
        });
      });
    },

    afterEach() {
      pretender.shutdown();
    }
  });
}


Migrate to pyproject to be a library

Closes #19

I've given this a test. It seems to work after I've changed an import as you can see. There are a couple of problems though.

It currently is conflicting main branch
It can be installed using the git URL, which is fine by me, but this can't be uploaded to pypi since it has an URL dependency (xx-ent-wiki-sm). To fix this we would have to either add functionality to download xx-ent-wiki-sm from within the code or replace spacy entirely.

So, to clarify things, for this PR to be merged it's fine if only point 1 is fixed, point 2 is not necessary for me. But if you want me to upload this to pypi it should be fixed too.
Thanks!

For now the git URL is also fine for my use. Perhaps the spacy thing can be done separately to limit the scope of this PR.

This seems good to go now. Thanks a lot for the PR and for the patience you've shown during it.


implement std::ostream / std::streambuf  (tentative)

This is a complete header-only implementation of the streambuf, and iostream interfaces for NNG messages.
I am not sure if supplementary features like this belong in NNGPP, but it's quite useful.  As such, consider this PR tentative.  I haven't yet conformed it to NNGPP's code style as I expect some discussion about whether it ought to be integrated.
For example:
nng::msg msg;
nng::omsgstream write(msg);
write << "POST /messages HTTP/1.1" << std::endl;
write << "Content-Type: text/plain" << std::endl;
write << std::endl;
write << "Hello, world" << std::endl;

This code relies on nng_msg_capacity and nng_msg_reserve functions, which I contributed to NNG only a few days ago.  As such it requires the "tip" version of NNG to function.
In addition to reading and writing nng::msg like a file, a sub-range of the message may be specified using open_range or additional constructor arguments.  This is intended for exposing sections of messages or omitting application-layer headers from I/O operations.  The parameter scheme for specifying ranges is a recent addition and might need more thinking.
Unlike ordinary iostreams, msgbuf and msgstream are copyable, and multiple msgbuf may refer to the same message at the same time.  No special provisions are made for concurrency.
I have performed basic consistency testing with this facility in my own library.  If it's put into production, more detailed unit tests are probably necessary.
† Note: similar to most implementations of std::stringstream, these classes lack full support for the ios_base::app flag.

I've fleshed the implementation out somewhat.  I've gotten it working on osx/clang in addition to windows/msvc.  It also now supports unusual character types such as std::byte and custom traits classes.


build Error on mac

commit: a1126c2
os:
ProductName:	macOS
ProductVersion:	12.4
BuildVersion:	21F79
make
mkdir -p /private/tmp/easeprobe//build/bin
go mod tidy
CGO_ENABLED=0 go build -a -ldflags '-s -w -extldflags "-static"' -gcflags=-G=3 -o /private/tmp/easeprobe//build/bin/easeprobe /private/tmp/easeprobe/cmd/easeprobe
directory /private/tmp/easeprobe/cmd/easeprobe outside main module or its selected dependencies
make: *** [/private/tmp/easeprobe//build/bin/easeprobe] Error 1

 RELEASE_DIR := ${MKFILE_DIR}/build/bin ->  ./build/bin ?

@killua525 just a quick question - why do you check out the EaseProbe into /tmp directory? this directory would be clean by the system periodically.
Please check out the code into the regular directory.
Thanks.

Move the folder to home and is work. Thx a lot


fix browserCompatible issue

#1742

Codecov Report
Patch coverage has no change and project coverage change: -1.88% :warning:

Comparison is base (5881331) 75.25% compared to head (97ac614) 73.38%.

Additional details and impacted files
@@             Coverage Diff              @@
##               main    #1747      +/-   ##
============================================
- Coverage     75.25%   73.38%   -1.88%
+ Complexity    21313    20456     -857
============================================
  Files           632      620      -12
  Lines         84684    84174     -510
  Branches      18723    18580     -143
============================================
- Hits          63727    61767    -1960
- Misses        13066    14373    +1307
- Partials       7891     8034     +143

Files Changed
Coverage Δ

...in/java/com/alibaba/fastjson2/JSONWriterUTF16.java
80.29% <ø> (-1.14%)
:arrow_down:

... and 59 files with indirect coverage changes

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


only PDF link to GNC charter?

@claudioruiz i think https://creativecommons.org/network/charter/ should just have the text as HTML, not only PDF link or link to github page. what do you think?

We discussed that with Diane and Rob. We have this page because it was important to legal to have one canonical version of the Charter somewhere outside network.cc.org, considering we have the source code on Github.
And we thought the best way to keep that canonical is with a PDF like that. It won't be complicated to put also an HTML version there, but I thought it might be totally lost under the website. We can easily change that later on.


Global DNS Entry shows active but no DNS entries created

Rancher Server Setup

Rancher version: 2.5.8
Installation option (Docker install/Helm Chart): Helm Chart

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): RKE1

Proxy/Cert Details: Wildcard cert with ACM

Information about the Cluster

Kubernetes version: v1.19.9
Cluster Type (Local/Downstream): Downstream

If downstream, what type of cluster?:

Infrastructure Provider = AWS

Describe the bug
I have configured the Global DNS Provider as Route53, and created a Global DNS Entry that points to the project that houses the Ingress I want fronted by DNS. Everything shows as "Active" in the Cluster Manager but I don't see any entries being created in Route53.
To Reproduce

Create a Global DNS Provider that points to Route53
Create a Global DNS Entry that uses the above Provider, and targets the Project housing the Ingress you want DNS entries for
Create an Ingress inside the project you targeted in step 2:
a) Add the annotation key = rancher.io/globalDNS.hostname, value = FQDN from Global DNS Entry above
b) Ensure the host field matches the FQDN from the Global DNS Entry above

Result
No DNS entries are created in Route53.
However, I can confirm that Rancher has used the IAM account I created to log into AWS and configure Route53.
Expected Result
Route53 should have a new DNS entry matching the FQDN from the Gllobal DNS Entry above

@ccittadino-ctic Your issue might be related to mine at https://github.com/rancher/rancher/issues/31638
This was fixed in v2.6.0

@abhi1693 Can you help me determine if I'm seeing the same issue as you? I'm trying to find logs that would narrow it down but unsure of where exactly they should be

Decided to upgrade to 2.6 and try again. Turns out the IAM account I used didn't have all the permissions it needed to alter the Route53 zone. Found this out by check Rancher's local cluster pod logs. Filter by 'dns' and you'll find it on the Pods page.


Incorrect order of modules: modules from project root are loaded before the ones in layer

Environment

Operating System: Linux
Node Version:     v18.18.0
Nuxt Version:     3.10.1
CLI Version:      3.10.0
Nitro Version:    2.8.1
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      extends, modules
Runtime Modules:  ()
Build Modules:    -

Reproduction
https://stackblitz.com/edit/github-vg4ayj
You can see in the console that the module from the root folder is loaded first.
Describe the bug
I'd expect modules from any layers to be loaded before the ones in project root.
Additional context
This issue seems to be in defu when merging arrays in config object here https://github.com/unjs/defu/blob/main/src/defu.ts#L33
Logs
No response

@pi0 do you think we could revisit merging order for c12?

Tracking in https://github.com/unjs/c12/issues/138.

Somewhat confused right now how to deal with the ordering of layer config.
E.g. when defining CSS, you'd want the order to be root layer -> ... -> application (https://github.com/nuxt/nuxt/issues/25167).
Same for resolving layer/module tree (e.g. if a layer extends another module the main application would expect this to be loaded before its own registered layers/application code)?


Create JSON from form

To minikomi
in https://github.com/minikomi/Bootstrap-Form-Builder/issues/40#
in above you give ans in that you said that add some code in my-form.js
Add:
this.collection.on("add", this.toJson, this);
this.collection.on("remove", this.toJson, this);
this.collection.on("change", this.toJson, this);
, toJson: function() {
console.log(this.collection.toJSON());
}
Open the console, and look at the output. i m follow ur instruction but in console there is no JSON object

Did you build the script using r.js? Or change the index.html to use the unbuilt version?

@minikomi can you explain a little bit more how to render form as Json object instead of html markups?
I check issues like #40 and #63 and others, but none of them explains it explicitly.
Thank you very much.

I was able to output json obj in console, but how to see them in "rendered view"?


Passing forecast data do not work

I have posted most of the description of the problem here:
https://community.home-assistant.io/t/emhass-an-energy-management-for-home-assistant/338126/111?u=haraldov
What is the Home Assistant log saying when you execute that shell command?
2022-08-28 20:38:03.701 DEBUG (MainThread) [homeassistant.components.shell_command] Stdout of command: curl -i -H "Content-Type: application/json" -X POST -d '{"load_cost_forecast": {{ ((( state_attr('sensor.nordpool', 'raw_today') + state_attr('sensor.nordpool', 'raw_tomorrow')) |map(attribute='value')|list)[:48]) }}' http://localhost:5000/action/dayahead-optim, return code: 0:
2022-08-28 20:38:03.701 DEBUG (MainThread) [homeassistant.components.shell_command] Stderr of command: curl -i -H "Content-Type: application/json" -X POST -d '{"load_cost_forecast": {{ ((( state_attr('sensor.nordpool', 'raw_today') + state_attr('sensor.nordpool', 'raw_tomorrow')) |map(attribute='value')|list)[:48]) }}' http://localhost:5000/action/dayahead-optim, return code: 0:
➜  config
However it doesn't get updated in the model.
Home Assistant 2022.8.7
Supervisor 2022.08.3
Operating System 8.5
Frontend 20220802.0 - latest
Raspberry Pi 4
EMHASS
Current version: 0.2.20
[2022-08-28 00:14:04,984] INFO in web_server: Launching the emhass webserver at: http://<IP_ADDRESS>:5000
[2022-08-28 00:14:04,985] INFO in web_server: Home Assistant data fetch will be performed using url: http://supervisor/core/api
[2022-08-28 00:14:04,985] INFO in web_server: The base path is: /usr/src
[2022-08-28 00:14:04,989] INFO in web_server: Using core emhass version: 0.3.18
[2022-08-28 00:15:24,545] INFO in web_server: EMHASS server online, serving index.html...
[2022-08-28 00:20:29,186] INFO in web_server: EMHASS server online, serving index.html...
[2022-08-28 00:22:31,750] INFO in web_server: EMHASS server online, serving index.html...
[2022-08-28 00:22:33,664] INFO in command_line: Setting up needed data
[2022-08-28 00:22:33,759] INFO in forecast: Retrieving weather forecast data using method = scrapper
[2022-08-28 00:22:39,605] INFO in forecast: Retrieving data from hass for load forecast using method = naive
[2022-08-28 00:22:39,607] INFO in retrieve_hass: Retrieve hass get data method initiated...
[2022-08-28 00:22:53,887] INFO in web_server: EMHASS server online, serving index.html...
[2022-08-28 00:22:56,188] INFO in web_server:  >> Performing dayahead optimization...
[2022-08-28 00:22:56,189] INFO in command_line: Performing day-ahead forecast optimization
[2022-08-28 00:22:56,198] INFO in optimization: Perform optimization for the day-ahead
[2022-08-28 00:22:56,755] INFO in optimization: Status: Optimal
[2022-08-28 00:22:56,756] INFO in optimization: Total value of the Cost function = -2.02
[2022-08-28 20:37:38,794] INFO in web_server: EMHASS server online, serving index.html...
[2022-08-28 20:38:27,230] INFO in web_server: EMHASS server online, serving index.html...
System Information

version
core-2022.8.7

installation_type
Home Assistant OS

dev
false

hassio
true

docker
true

user
root

virtualenv
false

python_version
3.10.5

os_name
Linux

os_version
5.15.32-v8

arch
aarch64

timezone
Europe/Oslo

config_dir
/config

Home Assistant Community Store

GitHub API
ok

GitHub Content
ok

GitHub Web
ok

GitHub API Calls Remaining
5000

Installed Version
1.26.2

Stage
running

Available Repositories
1164

Downloaded Repositories
12

Home Assistant Cloud

logged_in
true

subscription_expiration
September 7, 2022 at 02:00

relayer_connected
true

remote_enabled
true

remote_connected
true

alexa_enabled
false

google_enabled
true

remote_server
eu-west-2-3.ui.nabu.casa

can_reach_cert_server
ok

can_reach_cloud_auth
ok

can_reach_cloud
ok

Easee EV Charger

component_version
0.9.44

reach_easee_cloud
ok

connected2stream
true

Home Assistant Supervisor

host_os
Home Assistant OS 8.5

update_channel
stable

supervisor_version
supervisor-2022.08.3

agent_version
1.2.1

docker_version
20.10.14

disk_total
118.3 GB

disk_used
14.8 GB

healthy
true

supported
true

board
rpi4-64

supervisor_api
ok

version_api
ok

installed_addons
ESPHome (2022.3.1), SSH & Web Terminal (12.0.2), Mosquitto broker (6.1.2), File editor (5.3.3), Frigate NVR Proxy (1.3), Home Assistant Google Drive Backup (0.108.4), Z-Wave JS to MQTT (0.45.0), EMHASS (0.2.20)

Dashboards

dashboards
1

resources
2

views
10

mode
storage

Recorder

oldest_recorder_run
August 25, 2022 at 08:33

current_recorder_run
August 28, 2022 at 09:14

estimated_db_size
575.15 MiB

database_engine
sqlite

database_version
3.38.5

Spotify

api_endpoint_reachable
ok

Yes I have refreshed the webpage after triggering the service "Shell Command: load_cost_forecast". The page do not update using Chrome or with Firefox.

Hi, the problem persists after updating to the latest version?

Yes, the problem is the same with EMHASS add-on v0.2.20

I solved it! I found out I have done two errors.
The first was passing wrong amount of data in this list. Nordpool publish prices for every hour so the list must have 24 data points, not 48 points.
You need to be careful here to send the correct amount of data on this list, the correct length. For example, if the data time step is defined to 1h and you are performing a day-ahead optimization, then this list length should be of 24 data points.
The second was using template with errors. My template was wrong with the parenthesis and curly bracket. After fixing the template the shell_command worked and the passing of load_cost_forecast and prod_price_forecast was successful.
shell_command:
  publish_data: "curl -i -H 'Content-Type:application/json' -X POST -d '{}' http://localhost:5000/action/publish-data"

  post_nordpool_forecast: "curl -i -H 'Content-Type: application/json' -X POST -d '{\"load_cost_forecast\":{{(
        (state_attr('sensor.nordpool_euro', 'raw_today')|map(attribute='value')|list)[:24])
        }},\"prod_price_forecast\":{{(
        (state_attr('sensor.nordpool_euro', 'raw_today')|map(attribute='value')|list)[:24])}}}' http://localhost:5000/action/dayahead-optim"

Question:
1)
Load cost forecast: the price of the energy from the grid on the next 24h. This is given in EUR/kWh.
PV production selling price forecast: at what price are you selling your excess PV production on the next 24h. This is given in EUR/kWh.

Can I use NOK (norwegian) as price instead of Euro?

Ok perfect!
I'm glad that you find the problem.
Yes of course you can use whatever currency you want as long as you use the same currency everywhere, no problem at all.


[BUG] why zero++ need number of weights be a multiple of 8.

AssertionError: Qantized weight requires the number of weights be a multiple of
8. Yet 2305 cannot be divided by 8*2305

Hi @QingruiSun. It is a requirement by our quantization CUDA kernel to achieve the maximal throughput. You can get around it by changing the way the weight buffer is created in zero-3 to make it a multiple of 8 and then narrow it afterward

Thanks for your answer, but i can't understand it. Is it exist one simple solution to solve it and i can use quantized model parameter and gradient communication.

Hi @QingruiSun. Unfortunately, there is no simple way to get around this. Either to patch the CUDA kernel or to patch the way DeepSpeed creates and uses the parameter buffer.

Hi @HeyangQin. I also met the problem when I set zero_quantized_weights=true, I want to know how to patch the way DeepSpeed creates to use this?

afterward

Hi @QingruiSun. It is a requirement by our quantization CUDA kernel to achieve the maximal throughput. You can get around it by changing the way the weight buffer is created in zero-3 to make it a multiple of 8 and then narrow it afterward

Hi, I tried to modify the code in parition_parameters.py and I had modify the function CUDAQuantizer.quantize as follow:
def quantize(self, param, groups=None):
        remainder = param.numel() % 8
        if remainder != 0:
            padding_size = 8 - remainder
            padding = torch.zeros(padding_size, device=param.device, dtype=param.dtype)
            if not hasattr(param, 'original_size'):
                param.original_size = param.numel()
            param = torch.cat([param, padding])
        if groups is None:
            try:
                groups = self.group_size_cache[param.numel()]
            except KeyError:
                groups = math.ceil(param.numel() / self.target_group_size)
                while groups < param.numel():
                    if param.numel() % (8 * groups) == 0:
                        break
                    groups += 1
                while True:
                    if param.numel() % (8 * groups * 2) == 0 and param.numel(
                    ) / groups > self.target_group_size:  #hard limit of 16k group_size
                        groups *= 2
                    else:
                        break
                assert (
                    param.numel() % (8 * groups) == 0
                ), f"Qantized weight requires the number of weights be a multiple of 8. Yet {param.numel()} cannot be divided by 8*{groups}"
                assert (param.numel() / groups < 16000), f"{param.numel()} / {groups} is larger than 16k"
                assert param.numel(
                ) > groups, f"Adaptive grouping algorithm cannot find a group size for input tensor of size {param.numel()}"
                self.group_size_cache[param.numel()] = groups
        return self.quantizer_cuda_module.quantize(param.to(get_accelerator().device_name()), groups, 8,
                                                   self.quantizer_cuda_module.Symmetric)

but I cannot find a right position to narrow the param object, leading to the error: RuntimeError: output tensor size must be equal to world_size times input tensor size.
So in which position can I narrow the param?


Docs don't seem to work on Firefox

Hmm... I don't see any issues on FF 44.0.2

I'm on 44.0.2 as well and the problem persists after restarting Firefox and force-refreshing :-/
It works in Chrome and Safari. Not sure what's going on.

Do you have another machine you could use to test?

It works on my wife's laptop. Hmpf.

Ugh, it was Privacy Badger being overzealous and blocking npmcdn.com. Really sorry for the noise!


#461 Remove md tags by using temporary div

Closing this. I'm going to create a new branch for this fix in a couple of minutes. There are more things I would like to contribute.


Disable Chromium GPU blacklist

Fixes #2838
Context: https://github.com/zeit/hyper/issues/2838#issuecomment-382453354
Fix confirmed here: https://github.com/zeit/hyper/issues/2838#issuecomment-383240324
It maybe needs some more testing, especially it should not prevent using --disable-gpu Chromium flag

Adding --disable-gpu works!
Ready to merge

Well, according to https://www.khronos.org/webgl/wiki/BlacklistsAndWhitelists and https://chromium.googlesource.com/chromium/src/gpu/+/master/config/software_rendering_list.json there are a few devices that could run into problems with the blacklist disabled. But it seems it's mostly WebGL that is disabled and we don't actually use that, yet? Right?

@Stanzilla Yes, I am pretty confident that it will work well on these blacklisted GPUs.
If feedback proves me that I am wrong, we'll add an option to disable/enable this blacklist. In this case, we'll maybe add some detection mechanisms to directly advice concerned users to enable/disable this option.


⚠ ClamAV has degraded performance

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

HTTP code: 200
Response time: 77 ms

Resolved: ClamAV performance has improved in c09b9a7.


Dead links

While browsing the site (very impressive, sad I only just found it) I found some of the READMEs have dead links. In particular
On https://wltools.github.io/LanguageSpec/Specification/Syntax/ the List of all operators with precedence, associativity, affix, and arity link should be https://wltools.github.io/LanguageSpec/Specification/Syntax/OperatorTable/.
On https://wltools.github.io/LanguageSpec/ there are three in a row in the Table of Contents under Language Specification -> Resources for Implementers -> General Advice For Implementers:

the Exploring Mathematica link should be to https://wltools.github.io/LanguageSpec/Resources/Exploring-Mathematica/
the List of Independent Wolfram Language Projects link should be to https://wltools.github.io/LanguageSpec/Resources/List-of-W-Language-Projects/
the Software Development Tools for Wolfram Language link should be to https://wltools.github.io/LanguageSpec/Resources/ProgrammingTools/

Also http://visx.io/ and packagedata.net may be relevant (though inclusion of lists of libraries like packagedata.net may be orthogonal and thus a nongoal/distraction from the purpose of this site).

Thanks for the bug report! I'll add it to my to-do list.
I haven't heard of VisX before. Very interesting. I'm not sure it's right for my effort,  but it's worth knowing about for sure.


Remove annual revenue from settings

Q
A

Bug report?
[ ]

Feature request?
[ ]

Support request?
[ x ]

hi ,
I removed the html data from the twig on src/Cocorico/UserBundle/Resources/views/Dashboard/Profile/edit_bank_account.html.twig

                                {{ form_errors(form.annualIncome) }}
                                {{ form_label(form.annualIncome) }}

                                {{ form_widget(form.annualIncome,{
                                    'attr': {
                                        'class': "numbers-only form-control"
                                    }
                                } ) }}

but the field still stays in the page off the form : http://imgur.com/ouchsnUl.png
Thanks !

Hi,
You have to remove it also from this FormType : Cocorico/UserBundle/Form/Type/ProfileBankAccountFormType.php:75

It's perfect, thanks


Cheat key to go to next level

If you hit the 'n' key during the game it will go to the next level


updates related to upstream changes

combines #686 and #679

doc failure is because the pygfx gallery scraper now checks for BaseRenderCanvas instead of WgpuCanvas. Anyways wgpu.gui is going to be dropped soon so we should update things to use rendercanvas instead.

I think the current failures in the nb tests might be due to changes in the latest jupyterlab


Remove aliasing of OSFUser and AbstractNode [OSF-8223]

Purpose
Some model names have changed, and lots os usages are aliased to their old names. For consistency and clarity, get rid of the aliases and use their concrete classes instead.
Changes

Remove aliasing in import statements
Change previously aliased usages
Remove some unused imports

Side effects
None anticipated
Ticket
https://openscience.atlassian.net/browse/OSF-8223

Rebased and merged into develop!


Enhance Union Type Error Details

Prerequisites

[X] I have written a descriptive issue title
[X] I have searched existing issues to ensure the feature has not already been requested

🚀 Feature Proposal
Problem
When using fastify-type-provider-typebox, union type validation failures provide minimal error details:
{
  message: 'Expected union value',
  instancePath: ''
}

This lacks the detailed validation information that TypeBox provides through its errors property in the ValueError interface, making it difficult for developers to debug union-type validation failures.
Background
TypeBox's ValueError interface contains rich error information:
export interface ValueError {
    type: ValueErrorType;
    schema: TSchema;
    path: string;
    value: unknown;
    message: string;
    errors: ValueErrorIterator[]; // Contains detailed validation results for each union member
}

Current error mapping in fastify-type-provider-typebox:
error: errors.map((error) => ({
  message: `${error.message}`,
  instancePath: error.path
}))

Proposal
Enhance the error mapping to include detailed union validation information:
import { TypeCompiler, ValueError, ValueErrorIterator } from '@sinclair/typebox/compiler';
import { Type } from '@sinclair/typebox';

const CreateActionDelayBody = Type.Object({
	action: Type.Literal('DELAY'),
	days: Type.Number(),
});

const CreateActionSMSBody = Type.Object({
	action: Type.Literal('SMS'),
	phone: Type.String(),
});

const CreateActionEmailBody = Type.Object({
	action: Type.Literal('EMAIL'),
	email: Type.String({ format: 'email' }),
});

const CreateActionBody = Type.Union([
	CreateActionDelayBody,
	CreateActionSMSBody,
	CreateActionEmailBody,
]);

const C = TypeCompiler.Compile(CreateActionBody);

type ReducedError = [{ message: string; path: string; errors: ReducedError[] }];

const MapValueIterator = (iterator: ValueErrorIterator): ReducedError[] =>
	[...iterator].map((error) => MapValueError(error)) as never;

const MapValueError = (error: ValueError) => ({
	message: error.message,
	path: error.path,
	errors: error.errors.map((iterator) => MapValueIterator(iterator)),
});

const value = { action: 'ONE' };

const R = MapValueIterator(C.Errors(value));

console.dir(R, { depth: 100 });

Example Output
[
	{
		"message": "Expected union value",
		"path": "",
		"errors": [
			[
				{
					"message": "Expected required property",
					"path": "/days",
					"errors": []
				},
				{ "message": "Expected 'DELAY'", "path": "/action", "errors": [] },
				{ "message": "Expected number", "path": "/days", "errors": [] }
			],
			[
				{
					"message": "Expected required property",
					"path": "/phone",
					"errors": []
				},
				{ "message": "Expected 'SMS'", "path": "/action", "errors": [] },
				{ "message": "Expected string", "path": "/phone", "errors": [] }
			],
			[
				{
					"message": "Expected required property",
					"path": "/email",
					"errors": []
				},
				{ "message": "Expected 'EMAIL'", "path": "/action", "errors": [] },
				{ "message": "Expected string", "path": "/email", "errors": [] }
			]
		]
	}
]

I understand we need to stick to FastifySchemaValidationError. I'm raising this here to discuss how to better support it.
Motivation
No response
Example
No response

For Reference, below is the fastify-type-provider-zod error
When empty JSON is provided
[
	{
		"keyword": "invalid_union_discriminator",
		"instancePath": "/action",
		"schemaPath": "#/action/invalid_union_discriminator",
		"params": {
			"issue": {
				"code": "invalid_union_discriminator",
				"options": ["DELAY", "SMS", "EMAIL"],
				"path": ["action"],
				"message": "Invalid discriminator value. Expected 'DELAY' | 'SMS' | 'EMAIL'"
			}
		},
		"message": "Invalid discriminator value. Expected 'DELAY' | 'SMS' | 'EMAIL'",
		"[Symbol(ZodFastifySchemaValidationError)]": true
	}
]

When action is provided, but days aren't
[
	{
		"keyword": "invalid_type",
		"instancePath": "/days",
		"schemaPath": "#/days/invalid_type",
		"params": {
			"issue": {
				"code": "invalid_type",
				"expected": "number",
				"received": "undefined",
				"path": ["days"],
				"message": "Required"
			}
		},
		"message": "Required",
		"[Symbol(ZodFastifySchemaValidationError)]": true
	}
]

Thanks for reporting! Would you like to send a Pull Request to address this issue? Remember to add unit tests.

Thanks for reporting! Would you like to send a Pull Request to address this issue? Remember to add unit tests.


BB-BLACK x BB-BLACK WIFI

May I run a BB-BLACK REVc program on a BB-BLACK WIFI straightly ???

This query doesn't belong here. Please post to https://beagleboard.org/discuss.
Short answer, in most cases, yes, but you've said nothing about what your program would do. Will an ARM Linux program run on an ARM Linux board? In most cases, yes.

Hi Jason.
Sorry for my wrong post ... And I thank yo so much for your short answer.
Regards,
Xavier

On Tuesday, April 17, 2018, 12:03:21 AM GMT-3, Jason Kridner<EMAIL_ADDRESS>wrote:

This query doesn't belong here. Please post to https://beagleboard.org/discuss.
Short answer, in most cases, yes, but you've said nothing about what your program would do. Will an ARM Linux program run on an ARM Linux board? In most cases, yes.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Move fortigate imports at top-level

Breaking Change:
None
Description:
Related issue: partially f!x #27284 + isort
Checklist:

[ ] The code change is tested and works locally.
[ ] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[x] I have followed the development checklist

Yep @kifeo, tests are broken on dev actually


multi arc gauge enhancement to draw more than one arc in gauges

See issue #1077.
For each data_column one arc, the related background arc, arc label and a line to highlight the relation from arc to label will be drawn. When there are multiple data_column the legend is shown. For cleaner calculation in functions some variables are added. When there only is one data_column visible the old behaviour didnt changed.
This is my first pull request. We are already using the feature. I spend much time to refactor but i am sure there are still some optimiziations left.
All existing tests passed.
I would be glad to hear your opinion to the changes.

hi there, will you be merging this soon? I would really love this feature as well but currently compiling it myself...

+1 Seems a really good feature.

This looks amazing! Would love to add it, but it seriously needs some unit tests — we're not adding any new features to 0.4.x without them, especially when it has this many LOC.
Could you please do that, @GoekhanOezen? Thanks!

I will try but I would appreciate every help from the community.

@GoekhanOezen Try using the tests in spec/arc-spec.js as a guide. Seriously, the screenshots look amazing and this would make gauge charts much cooler than they presently are! Do let me know if you need any help, am usually on Gitter. 😄

ok i have rebased, refactored, bugfixed, refactored and added some test. i fixed the warnings and the tests who are related to my changes. But i cannot understand the error shown in travis. Because everytime i run tests on my PC there are different error displayed. i have a screenshot added below. I didnt change anything on axis.js.
Can someone help pls?

Would be great if this feature could be merged!

Would love this feature in c3! I wish I knew enough about this to help finish it

Landed here in master branch.
Released in v0.4.21. Thanks for the big contribution. Sorry for the serious delay!

thanks for the efforts! 🎊

@GoekhanOezen  can we provide two different max values for each data source like you've data1 and data2. I want to set 100 as max value for data1 and 200 as max value for data2 is that possbile in c3.js library. how to achieve it?


Fixes merge conflicts

This fixes merge conflicts so we can merge https://github.com/ReactiveX/rxjs/pull/2135

No clue. #YOLO


Version Packages

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
<EMAIL_ADDRESS>Patch Changes

#361 7f30721 Thanks @jevakallio! - Fix relative paths in create-partykit

<EMAIL_ADDRESS>Patch Changes

#353 a634046 Thanks @sylwiavargas! - Updates readme and package metadata

Let's get this out there


Statusline flicker with laststatus=3

Contributing guidelines

[X] I have read CONTRIBUTING.md
[X] I have read CODE_OF_CONDUCT.md
[X] I have updated 'mini.nvim' to latest version

Module(s)
statusline
Description
When switching between buffers, mini.statusline resets to Neovim's default statusline and then redraws itself, resulting in significant flickering. This can be solved by removing the following autocommand: https://github.com/echasnovski/mini.nvim/blob/f75b954473b11dc98a82475d8d1cf4f84560791b/lua/mini/statusline.lua#L473
Neovim version
NVIM v0.10.0-dev+3027-gc3061a40f
Steps to reproduce

nvim -nu minimal.lua
Swap with w

Expected behavior
No flickering should happen, redraw should be extremely fast, e.g.:
https://github.com/echasnovski/mini.nvim/assets/91024200/4d5def24-6772-4c86-aca9-71758b92328f
Actual behavior
https://github.com/echasnovski/mini.nvim/assets/91024200/1e91f40a-2f93-4206-b5eb-d4ad432d2252

Thanks for the issue!
Unfortunately, I can not reproduce. Even after (what looks like a) more precise identification of a problem: temporarily shown text seems to be from inactive content. It is visible and perceived as flicker because a global statusline (laststatus = 3) is used.
My guess is that there is some plugin which not appropriately triggers on which 'mini.statusline' relies. Removing entirely those autocommands in a plugin is certainly not a good idea, as they power the main laststatus = 2 case.
Could you try only with 'mini.statusline' enabled?

If you want to stress-test a heavier component, here's one that integrates with Coc diagnostics and LSP Progress (disclaimer: not optimized):

I see. I did not test this particular case, but I just added vim.loop.sleep(20) to one of the components and can see slight flicker with laststatus = 3.
The following patch seems to fix the issue:
diff --git a/lua/mini/statusline.lua b/lua/mini/statusline.lua
index 9fc290c..f196388 100644
--- a/lua/mini/statusline.lua
+++ b/lua/mini/statusline.lua
@@ -511,9 +511,9 @@ end
 H.ensure_content = vim.schedule_wrap(function()
   -- NOTE: Use `schedule_wrap()` to properly work inside autocommands because
   -- they might temporarily change current window
-  local cur_win_id = vim.api.nvim_get_current_win()
+  local cur_win_id, is_global_stl = vim.api.nvim_get_current_win(), vim.o.laststatus == 3
   for _, win_id in ipairs(vim.api.nvim_list_wins()) do
-    vim.wo[win_id].statusline = win_id == cur_win_id and '%{%v:lua.MiniStatusline.active()%}'
+    vim.wo[win_id].statusline = (win_id == cur_win_id or is_global_stl) and '%{%v:lua.MiniStatusline.active()%}'
       or '%{%v:lua.MiniStatusline.inactive()%}'
   end
 end)

Would you be comfortable applying it to confirm if it works for you?

If you want to stress-test a heavier component, here's one that integrates with Coc diagnostics and LSP Progress (disclaimer: not optimized):

I see. I did not test this particular case, but I just added vim.loop.sleep(20) to one of the components and can see slight flicker with laststatus = 3.
The following patch seems to fix the issue:
diff --git a/lua/mini/statusline.lua b/lua/mini/statusline.lua
index 9fc290c..f196388 100644
--- a/lua/mini/statusline.lua
+++ b/lua/mini/statusline.lua
@@ -511,9 +511,9 @@ end
 H.ensure_content = vim.schedule_wrap(function()
   -- NOTE: Use `schedule_wrap()` to properly work inside autocommands because
   -- they might temporarily change current window
-  local cur_win_id = vim.api.nvim_get_current_win()
+  local cur_win_id, is_global_stl = vim.api.nvim_get_current_win(), vim.o.laststatus == 3
   for _, win_id in ipairs(vim.api.nvim_list_wins()) do
-    vim.wo[win_id].statusline = win_id == cur_win_id and '%{%v:lua.MiniStatusline.active()%}'
+    vim.wo[win_id].statusline = (win_id == cur_win_id or is_global_stl) and '%{%v:lua.MiniStatusline.active()%}'
       or '%{%v:lua.MiniStatusline.inactive()%}'
   end
 end)

Would you be comfortable applying it to confirm if it works for you?

Yes, give me a moment :+1:

LGTM, I don't see flickering anymore 🥳

Great! I have the fix which I intend to re-review tomorrow and merge if everything is OK.

This should now be the part of main. Thanks for the early testing!


JSON converted utility

Can u share or recommend any utility for convert my own historical to JSON

You might want to use doctor-dok just for this.  I mean when you add your files then ther's an option to export all other records to JSON archive (including JSON but not only) - so it's a way


Scripts for building wheel with Python 3.6, 3.7, and 3.8

This should be done rather than #23

Done with #30


openfortivpn: 1.7.0 -> 1.7.1

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/openfortivpn/versions.
These checks were done:

built on NixOS
/nix/store/qn1hzzhcv20cyk6q58wlgjar03dbqbqv-openfortivpn-1.7.1/bin/openfortivpn passed the binary check.
1 of 1 passed binary check by having a zero exit code.
1 of 1 passed binary check by having the new version present in output.
found 1.7.1 with grep in /nix/store/qn1hzzhcv20cyk6q58wlgjar03dbqbqv-openfortivpn-1.7.1
directory tree listing: https://gist.github.com/8d202ae1f27f632d9f02045900200b02
du listing: https://gist.github.com/809d7d83e583187909b98ed31fae9fab

meta.description for openfortivpn is: '"Client for PPP+SSL VPN tunnel services"'.
cc @madjar for testing.
Experimental: this build is cached with Cachix. To use the cache follow these experimental instructions:
One time setup in nixpkgs Git checkout:
cachix use r-ryantm
git remote add r-ryantm https://github.com/r-ryantm/nixpkgs.git

Test this build:
git fetch r-ryantm && git checkout 591e8de248b47b0a056a3b3ed14a1c7e29c2b30c && nix-shell --pure -I nixpkgs=. -p openfortivpn

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: openfortivpn
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: openfortivpn
Partial log (click to expand)
make[1]: Leaving directory '/build/source'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/qn1hzzhcv20cyk6q58wlgjar03dbqbqv-openfortivpn-1.7.1
shrinking /nix/store/qn1hzzhcv20cyk6q58wlgjar03dbqbqv-openfortivpn-1.7.1/bin/openfortivpn
gzipping man pages under /nix/store/qn1hzzhcv20cyk6q58wlgjar03dbqbqv-openfortivpn-1.7.1/share/man/
strip is /nix/store/4mf2xm9p32lzrim927yk92xhx35yaz62-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/qn1hzzhcv20cyk6q58wlgjar03dbqbqv-openfortivpn-1.7.1/bin
patching script interpreter paths in /nix/store/qn1hzzhcv20cyk6q58wlgjar03dbqbqv-openfortivpn-1.7.1
checking for references to /build in /nix/store/qn1hzzhcv20cyk6q58wlgjar03dbqbqv-openfortivpn-1.7.1...
/nix/store/qn1hzzhcv20cyk6q58wlgjar03dbqbqv-openfortivpn-1.7.1

Success on aarch64-linux (full log)
Attempted: openfortivpn
Partial log (click to expand)
make[1]: Leaving directory '/build/source'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/k2laciwzbwn4nr59sj62nnnnjyirk799-openfortivpn-1.7.1
shrinking /nix/store/k2laciwzbwn4nr59sj62nnnnjyirk799-openfortivpn-1.7.1/bin/openfortivpn
gzipping man pages under /nix/store/k2laciwzbwn4nr59sj62nnnnjyirk799-openfortivpn-1.7.1/share/man/
strip is /nix/store/min150lkigznaayzpwvf8d4jdl1dqvx6-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/k2laciwzbwn4nr59sj62nnnnjyirk799-openfortivpn-1.7.1/bin
patching script interpreter paths in /nix/store/k2laciwzbwn4nr59sj62nnnnjyirk799-openfortivpn-1.7.1
checking for references to /build in /nix/store/k2laciwzbwn4nr59sj62nnnnjyirk799-openfortivpn-1.7.1...
/nix/store/k2laciwzbwn4nr59sj62nnnnjyirk799-openfortivpn-1.7.1


Improve pretty-printing of BigInt byte values.

https://github.com/ChainSafe/forest/blob/6bb8dde95efe0d3c05361e9f7f7d5f5c0fa1492f/forest/src/cli/mod.rs#L330-L334

[ ] Use u128::try_from
[ ] Remove the clone.
[ ] Include the number in the error message if we cannot convert to u128.
[ ] Use unwrap_or_else for lazy formatting of the error message.

Currently, this method doesn't really do what it's supposed to do according to the comment above. Namely, it operates on e.g. kilobytes (K, 1000) and not kibibytes (Ki, 1024). It's a flag to the get_appropriate_unit, but should we keep the existing behaviour and change the description or the other way around? Personally, I'm for the latter, operating in powers of 2 seems more natural in the space. What do you think?

Yeah, I think powers of 2 is the way to go.


Circular dependency

Got this when by MBrace scripting session had included some WPF and charting. Can give a full repro if needed.
#load "../../../FSharpDemoScripts/extlib/EventEx-0.1.fsx"
#load "../../../FSharpDemoScripts/packages/FSharp.Charting/FSharp.Charting.fsx"
#load "../../../FSharpDemoScripts/vizlib/load-wpf.fsx"
#load "../../../FSharpDemoScripts/vizlib/show.fsx"

Nessos.Vagabond.VagabondException: Found circular dependencies: PresentationFramework, ReachFramework, System.Printing.
   at Nessos.Vagabond.DependencyAnalysis.getAssemblyOrdering(FSharpList`1 dependencies) in c:\Users\eirik\Development\nessos\Vagabond\src\Vagabond\SliceCompiler\DependencyAnalysis.fs:line 23
   at Nessos.Vagabond.DependencyAnalysis.traverseDependencies(FSharpFunc`2 ignoreF, Boolean requireLoaded, FSharpOption`1 state, IEnumerable`1 assemblies) in c:\Users\eirik\Development\nessos\Vagabond\src\Vagabond\SliceCompiler\DependencyAnalysis.fs:line 107
   at MBrace.Azure.Runtime.Primitives.BlobAssemblyManager.ComputeDependencies[T](T graph) in C:\workspace\krontogiannis\MBrace.Azure\src\MBrace.Azure.Runtime\Primitives\BlobAssemblyManager.fs:line 193
   at <StartupCode$MBrace-Azure-Client>.$Client.CreateProcessAsync@240.Invoke(Unit unitVar) in C:\workspace\krontogiannis\MBrace.Azure\src\MBrace.Azure.Client\Client.fs:line 248
   at Microsoft.FSharp.Control.AsyncBuilderImpl.callA@803.Invoke(AsyncParams`1 args)
   at MBrace.Core.Internals.ExceptionDispatchInfoUtils.Async.RunSync[T](FSharpAsync`1 workflow, FSharpOption`1 cancellationToken) in c:\Users\eirik\Development\mbrace\MBrace.Core\src\MBrace.Core\Utils\ExceptionDispatchInfo.fs:line 136
   at <StartupCode$FSI_0028>.$FSI_0028.main@() in C:\GitHub\dsyme\MBrace.StarterKit\azure\HandsOnTutorial\0-demo.fsx:line 79

Thanks, this has been fixed in the latest Vagabond.

Great!  will upgrade my cluster (is it in MBrace.Azure 0.6.10?)

I'm afraid not. It'll probably take some time before this finds itself in MBrace.Azure.

ok, no problem
BTW am happy to start to contribute to MBrace.Azure, e.g. to help things like this move along and help make releases - we can probably start to bring in more community people too. I know @krontogiannis has to do some army service! :)

Great, we'd be happy to have you!

Could you add a DEVGUIDE.md that covers building, testing and releasing, and a CONTRIBUTING.md that covers contribution guidelines, to both MBrace.Azure and MBrace.Core?
Ideally you want it so I or another contributor could build, test and make a release (assuming we have the keys to push packages and to the docs repo).
best
don


Need to recompile error

I'm trying to test the viewer, but I'm getting this error
Module build failed (from /Users/rzu/Workspace/gaia-viewer/node_modules/ts-loader/index.js):
Error: Typescript emitted no output for<EMAIL_ADDRESS>You should not need to recompile .ts files in node_modules.
Please contact the package author to advise them to use --declaration --outDir.
More https://github.com/Microsoft/TypeScript/issues/12358
at successLoader (/Users/abc/Workspace/gaia-viewer/node_modules/ts-loader/dist/index.js:39:15)
at Object.loader (/Users/abc/Workspace/gaia-viewer/node_modules/ts-loader/dist/index.js:21:12)
@coyotte508 Can you help me on this?
Thanks
R

solved linking local Gaia-engine.
thanks

Looks promising, even if I didn’t fully understood the final architecture. Will you be able to run multiple games?
I tried a couple of months ago to create something using board game.io, but then I had to refocus on real work... anyway, I’m willing to help if you are committed to move it to the final stage
Best
R

Il giorno 12 giu 2018, alle ore 18:25, coyotte508<EMAIL_ADDRESS>ha scritto:
Good. Not that this is very far from being complete at the moment!
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.

Right now there's the engine and the viewer. The engine can be ported to anywhere as it's pure javascript (not the server part), for example it could be in an android app, a web page, or a server.
The plan in the future is to make a website using both the engine in backend, and the viewer as frontend. The website would have the seed & list of moves for each game in db, as well as player info. That's how multiple games are handled.
Of course the engine can be reused by other people for plenty of other things, like building an AI and so on.
Right now all that's available on the engine is board generation & faction choice. Like this:
init 5 seed
p1 faction terrans
p2 faction geodens
...

The next thing to do is to place buildings on the map, and do it with a click. We'll see how it goes.

I can help on the build command on the engine side, if you need help.
Where are you planning to store which building is in each space in the map?
Which is the best way to debug this architecture? Do you have suggestions or can you point me to tutorials?

I created a gitter room here: https://gitter.im/gaia-engine , so we can chat


JSON fields are not supported

Error:
2022/12/29 22:13:10 :10: got "JSON", want scalar type
JSON is a normal type and should be supported, at least as a black box

Set the Default App for JSON Files · Go to Settings > Apps > Default Apps, then choose Set Default by File type
this  should work if u r using a windows 8 or +

I am on Mac, and the problem is that Google parser does not support JSON as well. Can't work this around

Thanks for creating issue.
This caused that spanner-er used old version of cloud.google.com/go/spanner.
I updated at https://github.com/nktks/spanner-er/pull/8


Node Restart using Redfish API

FEATURE REQUEST
What happened:
Currently Litmus is using SSH based auth to execute reboot command to target nodes. for this, we are creating a keypair and adding the public key to all target nodes manually.
What you expected to happen:
Eliminate SSH , Use Redfish api to directly perform restart on target node using IP, UserName and Password.
EX: Reset Dell iDRAC
API request: POST request to "https:///redfish/v1/Managers/iDRAC.Embedded.1/Actions/Manager.Reset/"

@rbalagopalakrishna this is cool. Definitely somey we will explore

@ksatchit I would like to work on this with @rbalagopalakrishna

Great! Thanks @gpsingh-1991 - please feel free to post your approach here!


Feature Request: Import/Export

It would be helpful to be able to export and  reimport a list of all subscribed twitter handles for changing devices and factory resets.

Fully agree - I'm working on this already!

As an extension to this the support for Android Backup Service can be added (http://android-doc.github.io/google/backup/index.html)
LineageOS added SeedVault so it is no longer Google dependent.


Icons8

Description
Current Features :

Search for icons by name.
Filter the icons by the common styles.
Recolor the colorable icons.
View details about the icon such as style, category, and tags.
Configure the download settings such as file name, format, and size.
Download SVG and image formats including PNG, JPG, and WEBP.
Pin the icons and view recent icons.

Feel free to suggest other features.
Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Hi @yug2005,
Thank you so much for your contribution.
I just tested the extension and noticed that for some symbols the "Open in Browser" action doesn't do anything. Like for example for the "Smiling Sun" one from the "Cloud" collection. And I guess it should open this url: https://icons8.com/icon/7UYg9itOH2r7/smiling-sun no?


proposal: net: context variants for udp functions

net/udpsock: exposes contexts for several UDP related functions:
In the udpsock package are several (exposed) functions (see below) which use context.Background() as context for calls to unexposed internal functions.

ResolveUDPAddr
DialUDP
ListenUDP
ListenMulticastUDP

I propose to expose the contexts to the user. See PR https://github.com/golang/go/pull/59880. This makes it possible for the user to hand over its own context and allows hin/her to e.g. cancel or timeout the named UDP actions.
The PR does not change the API for the existing functions above, it just adds another function for each of them with the suffix WithContext and an additional argument (namely the context ctx). This would add the following functions:

ResolveUDPAddrWithContext
DialUDPWithContext
ListenUDPWithContext
ListenMulticastUDPWithContext

With the same signature but a context.Conteext added as first argument. Internally the "non-context" function from above, are then just wrappers for the WithContext functions and call them with context.Background().

cc @ianlancetaylor @neild

This is largely a dup of #49097, which is a proposal that has been accepted but not yet implemented.

@ianlancetaylor Ok, so how do we go forward? In https://go.dev/cl/490975 are changes, shall I incorporate them into my PR?

If you think #49097 is making a poor choice of API, then please comment on that issue.
For this issue I suggest that we first complete the work on #49097, then consider whether there is anything to do here.


Single photo modal close

When looking at a single photo, the modal close button should be an 'X' at the top right - it is verbiage under the photo.

Fixed


{Packaging} Bump OAuthLib to 3.2.2

Description

Close #25351, oauthlib 3.2.0 fixes PRISMA-2021-0041:

There is no support for PKCE implementation in the oauthlib client. Client-side PKCE for OAuth2 RFC 7636 is required for applications to have secure communication with the authorization server. OAuth 2.0 public clients utilizing the Authorization Code Grant are susceptible to the authorization code interception attack.   -- https://github.com/oauthlib/oauthlib/issues/774

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Packaging

Why is oauthlib installed?

azure-mgmt-monitor/azure-mgmt-recoveryservicesbackup -> msrest -> requests-oauthlib -> oauthlib


Feature request :) Be able to install several themes

It would be nice to be able to install several themes in one project :)
The idea I have is to use different themes for different parts of the page.
For this, it would be necessary to wrap the bootstrap theme CSS like:
.flatly-theme {
  /* bootstrap here */
}

Just a suggestion :)

Hi @akuz,
It's not related to boostwatch-dist. You want to add a feature to all bootswatch themes.


Create load from parquet

PR that creates a generic component to load data stored as a parquet from remote storage
Largely based on the load from hub component with some modification. Currently needed for the datacomp pipeline.
Future modification could include loading data from local storage though we'd need to make sure that the data is mounted locally

The component does probably the job for now. I am just curious about if we can reuse the load from hub component completely. In the load_from_hub component we do something like this:
dask_df = dd.read_parquet(f"hf://datasets/{self.dataset_name}")

If I see it correctly, the only part that is different here is hf:// vs. gs// or s3://. What do you think about to adjust the load from hub component to a more generic one?

Fairpoint, there is not a lot of difference between them and it can be generalized. I would tackle this in another PR though since it might affect other pipelines (need to change the load from hub component name, examples, docs, ...) #475


Added a basic guide for use with TypeScript

Is there any concern over the requirement that the component managed by Reach has to take a coupling to it?
What if I'm adding a component that isn't part of my project?  I can't force it to use the reach props interface.

Is this the best place to ask that question? Seems like someone not using TypeScript could easily have the same concern.

Not necessarily. In JS, the component will happily work, totally oblivious to how it's being run.
Yes there may be design implications, if intended. But we haven't ascertained that yet. And if there are, then yeah, this is a great place to get those intentions noted explicitly.

It's possible that the type definitions have been changed by the community since I last installed them, but I don't think I was required to use the RouteComponentProps interface. I could opt in if I needed the props, but any component was allowed. Same as JS.

If you don't include the interface in your component's props, you run into https://github.com/reach/router/issues/141 .
This is not a problem in plain JavaScript obviously because duck-punching.  In TypeScript however, it's wanting you to declare the presence of a new prop.
Because of this difference, in the JS world, you can use reach with any component, without anything trying to suggest that it's a possible error.  In TS, it's explicitly an error.
The biggest drawback I see is that it'll force people to write arbitrary wrappers for code they don't control, just to satisfy the compiler.  This would only happen because they're using TypeScript, which might at that point seems to me to make it wrong.
The point overall here is that I think this still remains an unresolved question for reach.  Any documentation should at least be pointing out the presence of this difference.  And ideally any solution or conclusions (as they happen).

If you don't include the interface in your component's props, you run into #141 .

Oh yes, I forgot about that. I haven't had to touch the routing related parts of my app's code in a while.