document  need for higher max_locks_per_transaction for pg_dump/pg_restore

Because of the many tables created by the promscale schema, backup and restore operations are a little brittle.
pg_dump calls were frequently failing due to max_locks_per_transaction:
pg_dump: error: query failed: ERROR:  out of shared memory
HINT:  You might need to increase max_locks_per_transaction.
pg_dump: error: query was: LOCK TABLE prom_data.node_xfs_block_map_btree_compares_total IN ACCESS SHARE MODE
2020/10/21 10:30:51 pg_dump run failed with: exit status 1

Ultimately, I had to raise max_locks to 1000 to allow a pg_dump to go through, trying at 100, 300, 500 first.
This database has 119628 tables (according to select count(*) from information_schema.tables;)
Coincidentally, this also makes the backup process take forever, as pg_dump does a lot of scanning on every table first. For about 15gb of data, a pg_dump took about 48 minutes.
On restore, even with max_locks set to 1000, it fails due to max_locks:
pg_restore: while PROCESSING TOC:
pg_restore: from TOC entry 66856; 1259 7011345 TABLE compress_hyper_465_109509_chunk postgres
pg_restore: error: could not execute query: ERROR:  out of shared memory
HINT:  You might need to increase max_locks_per_transaction.
Command was: CREATE TABLE _timescaledb_internal.compress_hyper_465_109509_chunk (
)
INHERITS (_timescaledb_internal._compressed_hypertable_465)
WITH (toast_tuple_target='128');
ALTER TABLE ONLY _timescaledb_internal.compress_hyper_465_109509_chunk ALTER COLUMN "time" SET STATISTICS 0;
ALTER TABLE ONLY _timescaledb_internal.compress_hyper_465_109509_chunk ALTER COLUMN value SET STATISTICS 0;
ALTER TABLE ONLY _timescaledb_internal.compress_hyper_465_109509_chunk ALTER COLUMN series_id SET STATISTICS 1000;
ALTER TABLE ONLY _timescaledb_internal.compress_hyper_465_109509_chunk ALTER COLUMN _ts_meta_count SET STATISTICS 1000;
ALTER TABLE ONLY _timescaledb_internal.compress_hyper_465_109509_chunk ALTER COLUMN _ts_meta_sequence_num SET STATISTICS 1000;
ALTER TABLE ONLY _timescaledb_internal.compress_hyper_465_109509_chunk ALTER COLUMN _ts_meta_min_1 SET STATISTICS 1000;
ALTER TABLE ONLY _timescaledb_internal.compress_hyper_465_109509_chunk ALTER COLUMN _ts_meta_max_1 SET STATISTICS 1000;
ALTER TABLE ONLY _timescaledb_internal.compress_hyper_465_109509_chunk ALTER COLUMN _ts_meta_min_2 SET STATISTICS 1000;
ALTER TABLE ONLY _timescaledb_internal.compress_hyper_465_109509_chunk ALTER COLUMN _ts_meta_max_2 SET STATISTICS 1000;

So seems like we need to work out some strategy to allow for backup/restore of this data more efficiently, or outline a set of instructions to allow for it to happen.

@antekresic can we please document that we need a higher max_locks_per_transaction  for pg_dump/pg_restore in our FAQ.
Left as a TODO: consider making this setting higher with ts_tune

I am hitting this too and I can't upgrade because of it. I'm not sure why its causing a problem as my promscale data is very very small
postgres=# select count(*) from information_schema.tables;
 count
-------
   194
(1 row)

pg_database_size(pg_database.datname)/1024/1024/1024 AS sizegb
FROM pg_database
WHERE pg_database.datname='promscale'
ORDER by pg_database_size(pg_database.datname) DESC;
 databasename | sizegb
--------------+--------
 promscale    |      4
(1 row)

I've tried setting the max_locks_per_transaction as high as 100,000. My shared_buffers are 32GB... there's no clear reason why this is happening.
Fortunately I don't need this data so I'm just doing to destroy it before the upgrade, but it would have been nice for this upgrade to have gone smoothly. It makes me wary of upgrading any promscale servers in production at work now...


Banding and yellowish effects on gradients even using UASTC mode

I've tried to compress a reference image several times with different options without luck:
Here is the reference image:

And here are the results (there are almost no difference on different high quality transcoding methods)
Default parameters:

Default parameters in KTX2 format:

UASTC enabled

If I can help you with any other test just let me know.

Just another (probably clearer to understand) image:


Add is_assoc_array() ad is_numeric_array()

Often I'll want to know if the data I have is an associative array (i.e. a hash), or if it's a flat numeric array (0,1,2). My use case for this is in unit testing where I want to see if a function is returning the correct data type (hash vs array). For example array_keys() always returns an array, while pathinfo() always returns a hash.
I added two functions to test for this, and their associated unit tests.
In my mind (I come from a Perl world) there are "arrays" and "hashes". I'd be open to renaming these functions to is_hash() and is_array(), but that's because that's what I'm used to in Perl. There isn't an exact mapping in PHP. Thoughts?

The only caveat to this is the weird case of array(2=>'a', 1=>'b', 0=>'c'); which is an "array" but built in the wrong order. Currently this tests out as associative. I don't know how common this is, or if this should be considered an array.

Coverage increased (+0.03%) to 97.47% when pulling ed1b64694f73b369089995a4384e38fd3e23bf74 on scottchiefbaker:master into a718b375cc54bdc13412de641e3cc5ce216c27f5 on brandonwamboldt:master.

Coverage increased (+0.03%) to 97.47% when pulling ed1b64694f73b369089995a4384e38fd3e23bf74 on scottchiefbaker:master into a718b375cc54bdc13412de641e3cc5ce216c27f5 on brandonwamboldt:master.

Coverage increased (+0.03%) to 97.47% when pulling ed1b64694f73b369089995a4384e38fd3e23bf74 on scottchiefbaker:master into a718b375cc54bdc13412de641e3cc5ce216c27f5 on brandonwamboldt:master.


Ensure Vim script track is ready for v2 launch

There are a number of things we're going to want to check before the v2 site goes live. There are notes below that flesh out all the checklist items.

[x] The track has a page on the v2 site: https://v2.exercism.io/tracks/vimscript
[ ] The track page has a short description under the name (not starting with TODO)
[x] The "About" section is a friendly, colloquial, compelling introduction
[ ] The "About" section follows the formatting guidelines
[x] The code example gives a good taste of the language and fits within the boundaries of the background image
[ ] There are exercises marked as core
[ ] Exercises have rough estimates of difficulty
[ ] Exercises have topics associated with them
[x] The first exercise is auto_approve: true

Track landing page
The v2 site has a landing page for each track, which should make people want to join it. If the track page is missing, ping @kytrinyx to get it added.
Blurb
If the header of the page starts with TODO, then submit a pull request to https://github.com/exercism/vimscript/blob/master/config.json with a blurb key.  Remember to get configlet and run configlet fmt . from the root of the track before submitting.
About section
If the "About" section feels a bit dry, then submit a pull request to https://github.com/exercism/vimscript/blob/master/docs/ABOUT.md with suggested tweaks.
Formatting guidelines
In order to work well with the design of the new site, we're restricting the formatting of the ABOUT.md. It can use:

Bold
Italics
Links
Bullet lists
Number lists

Additionally:

Each sentence should be on its own line
Paragraphs should be separated by an empty line
Explicit <br/> can be used to split a paragraph into lines without spacing between them, however this is discouraged.

Code example
If the code example is too short or too wide or too long or too uninteresting, submit a pull request to https://github.com/exercism/ocaml/blob/master/docs/SNIPPET.txt with a suggested replacement.
Exercise metadata
Where the v1 site has a long, linear list of exercises, the v2 site has organized exercises into a small set of required exercises ("core").
If you update the track config, remember to get configlet and run configlet fmt . from the root of the track before submitting.
Topic and difficulty
Core exercises unlock optional additional exercises, which can be filtered by topic an difficulty, however that will only work if we add topics and difficulties to the exercises in the track config, which is in https://github.com/exercism/vimscript/blob/master/config.json
Auto-approval
We've currently made any hello-world exercises auto-approved in the backend of v2. This means that you don't need mentor approval in order to move forward when you've completed that exercise.
Not all tracks have a hello-world, and some tracks might want to auto approve other (or additional) exercises.
Track mentors
There are no bullet points for this one :)
As we move towards the launch of the new version of Exercism we are going to be ramping up on actively recruiting people to help provide feedback. Our goal is to get to 100%: everyone who submits a solution and wants feedback should get feedback. Good feedback.
If you're interested in helping mentor the track, check out http://mentoring.exercism.io/

When all of the boxes are ticked off, please close the issue.
Tracking progress in https://github.com/exercism/meta/issues/104

Still has:

TODO: The maintainers have not provided a description for this track

@kotp That is taken from the blurb key in config.json, not the docs/ABOUT.md file

Things still to do:

Add blurb
Add topics to all exercises
Set ~8 exercises as core, and set unlocked_by on exercises which are non-core
Add difficulties to all exercises

@kotp That is taken from the blurb key in config.json, not the docs/ABOUT.md file

You are correct @jackhughesweb Sorry, if I did accidentally checked that off.  I did not mean to.

Blurb
If the header of the page starts with TODO, then submit a pull request to https://github.com/exercism/vimscript/blob/master/config.json with a blurb key. Remember to get configlet and run configlet fmt . from the root of the track before submitting.


Bug: problem with package's depedency "@kinde-oss/kinde-auth-pkce-js".

Prerequisites

[X] I have searched the repository’s issues and Kinde community to ensure my issue isn’t a duplicate
[X] I have checked the latest version of the library to replicate my issue
[X] I have read the contributing guidelines
[X] I agree to the terms within the code of conduct

Describe the issue
error:  unhandledRejection: Error [ERR_REQUIRE_ESM]: require() of ES Module<EMAIL_ADDRESS>from<EMAIL_ADDRESS>not supported. kinde-auth-pkce-js.umd.min.js is treated as an ES module file as it is a .js file whose nearest parent package.json contains "type": "module" which declares all .js files in that package scope as ES modules.
Instead rename kinde-auth-pkce-js.umd.min.js to end in .cjs, change the requiring code to use dynamic import() which is available in all CommonJS modules, or change "type": "module" to "type": "commonjs" in<EMAIL_ADDRESS>to treat all .js files as CommonJS (using .mjs for all ES modules instead).
Library URL
"https://github.com/kinde-oss/kinde-auth-react"
Library version
"^3.0.21"
Operating system(s)
Ubuntu
Operating system version(s)
Ubuntu 20.04
Further environment details
No response
Reproducible test case URL
No response
Additional information
No response

Hey @DiarFonda thanks for raising this one :)
I haven't been able to reproduce the issue, is there anything else you can tell me about your setup which could help me to reproduce it?

I believe the issue is that the library is ESM only, and doesn't support commonJS. although the kinde-typescript-sdk package seems to support both.

@ThatOneAwkwardGuy Interesting, I thought it supported both. I don't think it would be a huge effort to update the bundler to export a commonjs version

Currently copying and pasting the provider into my project... will this be fixed?

@DaveOrDead please assign this to me, since I intend to work on an issue in the same upstream package this weekend. :+1:. I'll take a look at this too.

I am running into the same issue, any update on the fix ?
using nextjs
"@kinde-oss/kinde-auth-react": "^3.0.28",
"axios": "^1.6.8",
"next": "14.1.3",
"react": "^18",
"react-dom": "^18"

I can't get Kinde to work because of this issue. @atifcppprogrammer if you could please look at it, that would be great.

Oh hey @ikx94 ! my apologies. I was assigned this a while ago and I totally forgot. I'll get this patched today or tomorrow at the very latest.

Oh hey @ikx94 ! my apologies. I was assigned this a while ago and I totally forgot about it. I'll get this patched today or tomorrow at the very latest.

Thank you. The same thing happens with the Node/Express package, it happens both client and server side, I think because they use the same common library that's causing this.
Thank you for looking into it.

Hi @ikx94, can you be a little more specific with regards to what packages you are referring to the "Node/Express package".


Change over to standalone authn API outside ERMrest

The /ermrest/authn/ API will change to /authn/ after other work in this epic is completed.
If the authn API path is made configurable in chaise_config.js, this work could be done in advance and we simply change the deployed config when ready...

@karlcz is this ready to be changed?

@hongsudt   The /authn/ API on dev-isrd is working now, so someone can start working on making Chaise talk to it instead of /ermrest/authn/...

Can we schedule this small task soon?

I think we should get this going in master soon and coordinate with transitioning of VMs to Fedora-based recipes so that the new VMs are using the new /authn/ API, in anticipation of eventually using the other mod_webauthn features and disabling the legacy copy of webauthn nested as /ermrest/authn/

@karlcz  Is #822 a duplicate of this issue?

yes, I think #822 is a duplicate

Should #258 be handled at the same time?  Is this touching the same code?


Unable to load regular npm modules from withing component

Hi there
First: Thank you so much for continuously working on Vue Brunch. We're really happy to use it.
After upgrading to Vue 2.0 and Vue Brunch 1.2.1, I can no longer import any regular npm modules from within my components.
Here's the error:
Uncaught Error: Cannot find module 'lodash' from 'web/static/js/components/task.vue'
The relevant section from task.vue:

Will generate
require.register("App.vue", function(exports, require, module) {
;(function(){
//

var fn = (a) => 'Hello, ' + a

})()

Using these dependencies
  "dependencies": {
    "browser-sync-brunch": "0.0.9",
    "vue": "^2.0.3"
  },
  "devDependencies": {
    "brunch": "^2.8.2",
    "vue-brunch": "^1.2.1",
    "babel-brunch": "^6.0.6",
    "babel-preset-es2015": "^6.16.0",
    "javascript-brunch": "^2.0.0",
    "sass-brunch": "^2.7.0"
  }

@AfraidKnot vue-brunch is basically a wrapper for vueify at the moment so it inherits any problems it may have. In this case babel-core is required as a peer dependency or it will not attempt to transpile anything within the


[PAY-1527] Local Reward Feature Flag Removed

📲 What
So Optimizely feature flag ios_local_pickup is no longer needed to be a check for displaying rewards in the app.
🤔 Why
The feature has been in production for over 6 months and therefore considered safe for permanent use.
🛠 How
Removed all Optimizely related code for storing and mapping the key from the the optimizely client.
Removed the logic for filtering the rewards based on this flag. So double the logic in RewardsCollectionViewModel but since we're not required to filter out any local rewards, we no longer need the feature flag or the backing reward.
Previously a reward was hidden only when ALL these conditions were true 1) feature flag OFF 2) reward is local 3) reward is not backed. So now that we don't need the flag check, the rest of the conditions (2, 3) should no longer gate any rewards.
✅ Acceptance criteria

[ ] - [ ] Run the app, check out a project with local rewards, see if they are displayed the same as web.

SwiftFormat found issues:

File
Rules

Library/ViewModels/RewardsCollectionViewModelTests.swift:163:1
warning: (indent) Indent code in accordance with the scope level.

  Generated by :no_entry_sign: Danger


Use rfc2119 keywords to indicate guidance levels

The guidelines mandate guideline levels without explaining what they mean. It's customary to use RFC2119 in such cases as they're widely understood in the industry. MSFT and GOOG guidelines both use RFC2119. There doesn't seem to be much value in having  undefined terminology.
This can be added to the introduction:

Conventions Used in These Guidelines
The requirement level keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" used in this document (case insensitive) are to be interpreted as described in RFC 2119.

With the following mapping:

Current term
RFC2119

Must
Must

Should
Should

Could
May

The changes in the text are minimal (could is replaced by may). Also the required term allows the guidelines to indicate and discuss mandates that come from aspects such as rules of play.

👍

From the meeting: We agree this is a good idea.
When changing the word could to may, we need to make sure the build process (Gitbook plugin for highlighting) still works.
@dehora Do you want to work on this?

Ok, see https://github.com/zalando/restful-api-guidelines/pull/232


Examples Broken

Version
Tell us which versions you are using:

react-native-router-flux v4.0.0-beta.30

Environment:
OS: macOS High Sierra 10.13.3
Node: 8.2.1
Yarn: 1.3.2
npm: 5.3.0
Watchman: 4.7.0
Xcode: Xcode 9.1 Build version 9B55
Android Studio: 3.0 AI-171.4443003
Packages: (wanted => installed)
react: 16.3.0-alpha.1 => 16.3.0-alpha.1
react-native: 0.54.2 => 0.54.2
Expected behaviour
Following example steps should successfully build example locally
Actual behaviour
I get this error in simulator

Steps to reproduce
For non-obvious bugs, please fork this component, modify Example project to reproduce your issue and include link here.
# Get the code
git clone https://github.com/aksonov/react-native-router-flux.git
cd react-native-router-flux/Example

# Install dependencies
yarn

# Run it
react-native run-ios

There is unfortunately some crazy things going on upstream, https://github.com/react-navigation/react-navigation/issues/3416
To get you going, and just for my own curiosity, can you try to uninstall the react-native-router-flux package in the project and then install the version pinned 4.0.0-beta.28 or 4.0.0-beta.22

Tried with 4.0.0-beta.28 and it works

4.0.0-beta.31 fixes it as well


[Shell] Add input method?

Extension
https://www.raycast.com/asubbotin/shell
Description
I can type out commands or responses (eg. answering [Y/n] prompts) for the process running in the raycast terminal. Also an indicator for when the command finishes.
Who will benefit from this feature?
Any developer who needs to quickly install an api, or a simple user installing stuff will benefit from the first. Anyone and every terminal user could benefit from the second.
Anything else?
No response

@ChedRed I’m not the author of this extension, but just a small contributor.
I’m submitting a PR to add an indicator for the result, which should partially address your request.
Meanwhile, I don’t think handling prompt replies is part of the extension’s current scope, as supporting that would require changes to how the command is evaluated and might even necessitate changes to the UI based on which command is entered.

Ello kevin, thank you for submitting a PR and contributing to the project. For the prompt handling, I was wondering if there was some builtin system that enabled for following commands to be sent. That being said, I have not looked at the code for any raycast plugin nor have I developed one. However, I do have an example from the Raycast Arcade extension, where a guess can be submitted. Thank you for your help!

Hello @ChedRed , after the execution has started and the Detail view is showing, it is incredibly hard to take user input based on prompts. We can parse each statement and use:
osascript -e 'display dialog ...

or a Form
to open a dialog for user input, but based on the variabilities, it is much easier to just pipe the command with a yes, so execute this: yes | <your command...>


Fix variable All value handling

Fixes #31

No idea, you‘re on your own, sorry...

Haha! Grafana sends $__all value for All option. So when that is set I fetch all value options except the first one (All option). There's also option to set custom All value. When set I pass that instead of all options.


Select the best chart library for Frestyle Opscenter usecase

There's different options and paths to follow when it comes to metric visualization through JavaScript. We must decide which one will better suit our project, from the wider scope D3.js or other ones more chart only focused like Chart.js.
Some links on different options here:

D3.js
Chart.js
Highcharts
C3
NVD3
Plotly.js
Chartist

A good comparison between these libraries, and different factors to consider when choosing one of them (even including use examples):
Comparing JS chart libraries in 2017

Another one I just spotted, pretty interesting:
Billboard.js

After some digging around them, given that all these options have all needed features for our project, we are gonna focus on a specific feature that can get tricky depending on the selected option, proper live data representation (meaning a soft transition when new data comes):

D3.js

[X] Live data support
Being a wide scope library, you obviously can have live data support, though you have into account these considerations.

Chart.js

[X] Live data support
Supported usecase by its documentation. Also there are lots of examples using different approaches. There's also a specific plugin tackling this. This page is pretty explanatory.

Highcharts

[X] Live data support
Full support for live data representation. But its non-commercial licenses states the following: Although Highsoft's Software have open source codes, our software is not licensed as an open source software and is unfortunately not compatible with any open source software license like Apache 2 or any GPL. See also Non-Commercial Redistribution

C3.js

[ ] Live data support
Though including a Flow method in its API, it looks more akin to sporadic addition of new data, not a data stream.

NVD3

[ ] Live data support
Not a pretty/specifically dedicated support for it it's included, but it can be successfully drawn by setting the chart animation duration to 0.

Plotly.js

[ ] Live data support
Supported through the use of extendTraces(), Present on the documentation. Not realtime data proper animations are supported though.

Chartist

[ ] Live data support
Usecase not covered actually.

Billboard.js

[ ] Live data support.
As based on C3.js, though including a Flow method in its API, it looks more akin to sporadic addition of new data, not a data stream.

ngx-charts

[ ] Live data support
Live data and updating it it's supported, the only thing that needs taking care it's the current animation or data flow, as it's not natural with the current implementation. PRs are welcome for this. Also there's a PR open now to be able to disable animations, which would help with this.

There's also another options, pretty focused on real time data:

Rickshaw

[X]  Live data support
There are examples showing how well this works with realtime data. There's even a wrapping component for Angular.

Epoch

[X]  Live data support
Real-time charts are first class citizens in this library, so the examples are mainly aimed to this usecase. Sadly, the library seems kinda abandoned with no activity at all on the last two years.

All things considered, the most promising option right now seems to be ngx-charts.
This JS libraries compilation has also been added to the project wiki: Dataviz JS libraries


Fuse convolution and addition

This patch is to fuse ONNXAddOp(ONNXConvOp %X, %Y) into a single ONNXConvOp if %Y is a constant, e.g.
%0 = "onnx.Conv"(%input, %weight, %bias)
%1 = "onnx.Constant"()
%2 = "onnx.Add"(%0, %1)

will become
%new_bias = "onnx.Constant"()
%0 = "onnx.Conv"(%input, %weight, %new_bias)

where new_bias is computed as %bias + onnx.squeeze(%1) by using constant propagation.
Constant propagation for ONNXSqueezeV11 is implemented to support the above fusion.
This patch also moves all canonicaliatione patterns from combine.td into rewrite.td. This is to reduce duplication code between combine.td and 'rewrite.td` where both have the same purpose that is canonicalization.

@jenkins-droid test this please

Could you add how new_bias is generated (related to %bias and %1) in the comment?

Could you add how new_bias is generated (related to %bias and %1) in the comment?

I updated the comment.

Jenkins Linux ppc64le Build #996 [push] Fuse convolution and add... started at 09:18

Jenkins Linux amd64 Build #1876 [push] Fuse convolution and add... started at 08:18

Jenkins Linux s390x Build #1874 [push] Fuse convolution and add... started at 09:18

Jenkins Linux s390x Build #1874 [push] Fuse convolution and add... passed after 53 min

Jenkins Linux amd64 Build #1876 [push] Fuse convolution and add... passed after 54 min

Jenkins Linux ppc64le Build #996 [push] Fuse convolution and add... passed after 1 hr 4 min


Introducing OUT_GAIN parameter for Heteroscedastic Tasks

Description
This pull request is to introduce out_gain parameter in the backend code so that when the new version, pytagi V1 has the heteroscedastic feature, it can use both the gain parameters.
Changes Made
The changes were made in these backend files wherever noise_gain was found:
cuTAGI/src/net_init.cpp
cuTAGI/src/net_prop.cpp
cuTAGI/include/struct_var.h
cuTAGI/src/python_api_cpu.cpp
cuTAGI/src/python_api.cu
cuTAGI/test/fnn_heteros/test_fnn_heteros_cpu.cpp

And in these config files, where noise gain was assigned.
cuTAGI/cfg/fc_heteros_mnist.txt
cuTAGI/cfg/fc_heteros_toy.txt
cuTAGI/cfg/fc_homosce_mnist.txt
cuTAGI/cfg/fc_homosce_toy.txt

Note for Reviewers
These changes cannot immediately be used in pyTAGI_V1 as the python scripts also needs to be carried over from the older version present in the branch UCI_Benchmark_Baseline. To run the benchmarks, please follow the README file in this branch.

@lhnguyen102 Can you take a look at Bhargob suggested changes for introducing a out_gain parameter?

Sure, I will go through it next week

This PR wont be necessary unfortunately because out_noise is equivalent to gain_w. More specifically, gain_w allows us to define the gain factor for each layer instead of one value for all layer like out_noise

Hi Ha,
If that is the case, its okay.
However, the pull request also has a change in how the biases are initialized. For Heteroscedastic, there is no need for noise_gain for the biases. Hence, the gaussian_param_init_ni is not required in Line 1055. Please look at the attached screenshot.
Bhargob
￼

On Apr 15, 2024, at 18:30, Luong-Ha Nguyen @.***> wrote:
@lhnguyen102 commented on this pull request.
In src/net_prop.cpp https://github.com/lhnguyen102/cuTAGI/pull/65#discussion_r1566502479:

@@ -1040,7 +1040,7 @@ Param initialize_param(Network &net) {
if (net.noise_type.compare("heteros") == 0 &&
j == num_layers - 1) {
std::tie(mw_j, Sw_j) = gaussian_param_init_ni(

                   scale, net.gain_w[j], net.noise_gain,

                   scale, net.out_gain, net.noise_gain, //net.gain_w[j]

@bhargobdeka https://github.com/bhargobdeka you dont need to introduce out_gain because net.gain_w is equivalent to net_out_gain.
For example, the net layer is defined as
layers: [1,     7,       7,       1]
gain_w: [0,     1,       1,       1]
gain_w is for mean and noise_gain is for std in the heteros case
—
Reply to this email directly, view it on GitHub https://github.com/lhnguyen102/cuTAGI/pull/65#pullrequestreview-2002280440, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQS77FQVTODBEQF3BEWRY73Y5RIIBAVCNFSM6AAAAABGGHVUGKVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDAMBSGI4DANBUGA.
You are receiving this because you were mentioned.

Bhargob, let me think about how to handle properly in the code because noise_gain is only required for the weight but not the bias.

Sure!

On Apr 15, 2024, at 19:16, Luong-Ha Nguyen @.***> wrote:
Bhargob, let me think about how to handle properly in the code because noise_gain is only required for the weight but not the bias.
—
Reply to this email directly, view it on GitHub https://github.com/lhnguyen102/cuTAGI/pull/65#issuecomment-2057966430, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQS77FRDOU43PTCIFTTWCLDY5RNUZAVCNFSM6AAAAABGGHVUGKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJXHE3DMNBTGA.
You are receiving this because you were mentioned.

@bhargobdeka line 1055 should be as you implemented if we don't want to touch the bias gain of the std's hidden state.
I will close this PR because you'll need to reverse all changes that you made on out_gain  and modify just line 1055 of code. I will incorporate this change in the upcoming PR instead.
Bhargob and @jamesgoulet  I was thinking about this ad-hoc technique of parameter initialization. It seems to me it is not generalizable since we need to introduce different method to get the good results.

@jamesgoulet I was thinking about this ad-hoc technique of parameter initialization. It seems to me it is not generalizable since we need to introduce different method for initializing the parameters to get the good results.

@lhnguyen102 I see what you mean and I think that, as you point out, we can keep the current setup where net.gain_b[j] are equal to one by default anyway, and one can adjust net.gain_w[j] if needed.
However, another thing I do not understand is why are we initializing the bias parameters like the weights? In my understanding, only the weights' variance should be initialized with a scale that is function of 1/fan_in and/or fan_out. For the biases, I think it should be std::tie(mb_j, Sb_j) = gaussian_param_init(1, net.gain_b[j], net.num_biases[j]); in all cases.
If you think this is a possibility, I can run a comparative benchmark to see if it performs well. But from a theoretical standpoint, I think it makes more sense.

@jamesgoulet I saw that pytorch use the same way back then as default implementation. Only difference is that they use uniform distribution but we use Gaussian (see Pytorch code).  I just transformed a bit to match with our framework but I am not sure it is optimal. It is always worth trying.

@jamesgoulet I saw that pytorch uses the same way back then as default implementation. Only difference is that they use uniform distribution but we use Gaussian (see Pytorch code). I just transformed a bit to match with our framework but I am not sure it is optimal. It is always worth trying.

@lhnguyen102 👌, I will look into it.


Getting compiler errors with snmp.h (IDFGH-12578)

Using latest master of esp-idf,
I get compiler errors when including lwip/apps/snmp.h:
<firmware-path>/esp-idf/components/lwip/include/apps/esp_sntp.h:287:9: error: 'uint8_t sntp_getreachability(uint8_t)' was declared 'extern' and later 'static' [-fpermissive]
  287 | uint8_t sntp_getreachability(uint8_t idx)
      |         ^~~~~~~~~~~~~~~~~~~~
<firmware-path>/esp-idf/components/lwip/lwip/src/include/lwip/apps/sntp.h:62:6: note: previous declaration of 'u8_t sntp_getreachability(u8_t)'
   62 | u8_t sntp_getreachability(u8_t idx);
      |      ^~~~~~~~~~~~~~~~~~~~
<firmware-path>/esp-idf/components/lwip/include/apps/esp_sntp.h:293:26: error: conflicting declaration of C function 'esp_sntp_operatingmode_t sntp_getoperatingmode()'
  293 | esp_sntp_operatingmode_t sntp_getoperatingmode(void)
      |                          ^~~~~~~~~~~~~~~~~~~~~
<firmware-path>/esp-idf/components/lwip/lwip/src/include/lwip/apps/sntp.h:52:6: note: previous declaration 'u8_t sntp_getoperatingmode()'
   52 | u8_t sntp_getoperatingmode(void);
      |      ^~~~~~~~~~~~~~~~~~~~~

Hi @0xFEEDC0DE64
This is probably a regression from c30f2825d5 (added a forwarding layer for some potentially thread unsafe lwip API to espressif wrappers).
This is probably causing trouble when building your project with some custom lwip features (not selected by Kconfig options), I wasn't able to reproduce it, though. I'd like to know how you're building and enabling the SNMP module.
We protect this compat layer with ESP_LWIP_COMPONENT_BUILD macro, so it's not taken into account when building lwip component. I guess you can workaround this issue by defining this macro for the component using SNMP (or adding the SNMP build to the lwip library).
Adding this line to the component makefile (maybe main component?) may fix the issue:
    target_compile_definitions(${COMPONENT_LIB} PRIVATE ESP_LWIP_COMPONENT_BUILD)

@0xFEEDC0DE64 Could you please share more details on how you're building your project with snmp module?
this seems unrelated to c30f2825d554dfe25afa450bb6aaa3aeb58782ef since you're also getting errors on sntp_getoperatingmode() API

Closing due to short of feedback, feel free to reopen.


Updates spfx project doctor and upgrade commands. Closes: #5679

Closes: #5679

Merged manually. Awesome work 👏


Tweak UI to show option value for back for card

Add showing of numbered list for options.
Add EditCardCommandSystemTest.
Add annotation for authorship.

Pull Request Test Coverage Report for Build 440

3 of 8 (37.5%) changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.09%) to 87.927%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/main/java/seedu/address/ui/CardBack.java
3
5
60.0%

src/main/java/seedu/address/ui/CardCard.java
0
3
0.0%

Totals

Change from base Build 439:
-0.09%

Covered Lines:
2214

Relevant Lines:
2518

💛  - Coveralls


WIP: Stablize GCP Tests

This PR continues on from https://github.com/gruntwork-io/terratest/pull/756 and aims to fix a consistent test failure in TestPackerBasicExample. We have broken the GCP tests out to a seperate Docker executor for better isolation and resiliency. Using the Docker executor ensures GCP tests do not errornously make metadata network calls within CircleCI's private environment. We also bump Packer to v1.6.6 as it includes improved error handling in the GCP builder.
Tasks

[x] Split GCP test execution out to a separate CircleCI docker executor.
[x] Tag all GCP tests as gcp.

Summary of Changes to GCP Account

[X] Ensure the default network allows inbound SSH connections.
[X] Remove dangling TICK firewall rules
[x] Cleanup temporary SSH keys

Looks like the tests passed in https://app.circleci.com/pipelines/github/gruntwork-io/terratest/377/workflows/fbb4a896-9450-4d45-ad8c-a8daf888ba95. They were still a bit flakey, but I think now that I've cleaned up some of the SSH keys, this PR should be good to go.

Looks like the tests passed in https://app.circleci.com/pipelines/github/gruntwork-io/terratest/377/workflows/fbb4a896-9450-4d45-ad8c-a8daf888ba95. They were still a bit flakey, but I think now that I've cleaned up some of the SSH keys, this PR should be good to go.

Looks like the tests passed in https://app.circleci.com/pipelines/github/gruntwork-io/terratest/384/workflows/3643c443-6969-45be-bace-4f7b6153ff20

Looks like the tests passed in https://app.circleci.com/pipelines/github/gruntwork-io/terratest/384/workflows/3643c443-6969-45be-bace-4f7b6153ff20


native/examples/6_rotation.cpp issue

Hi,
According to this link https://www.youtube.com/watch?v=XaYEHnaAg8M&list=WL&index=61&t=2643s
the primes digits should be like 60, 40, 40, 60 or so. At least the first prime digit 60 should be bigger than the second prime digit 40.
So why the primes are chosen to be "parms.set_coeff_modulus(CoeffModulus::Create(poly_modulus_degree, { 40, 40, 40, 40, 40 }));"  ?
shouldn't the first 40 be like 60? if first prime is 40, how could the multiplication result have correct integer digits?
BR

Good observation. Choosing { 60, 40, 40, 40, 60 } helps when you get to the last supported level. However, the example does not consume that many levels; so the prime sizes are not that important.

Good observation. Choosing { 60, 40, 40, 40, 60 } helps when you get to the last supported level. However, the example does not consume that many levels; so the prime sizes are not that important.

ok, it makes sense.
so basically, multiplication will consume levels, while rotation and addition will not consume levels, right?

Right. To be precise, multiplication does not consume levels, the consequential rescaling operation does.


fix(input): add default input height

Fixes an issue where inputs are not aligned when using flex-layout and datetime-local, because there is no default height for input fields in the code, and the default browser's height for datetime-local input fields is not the same as other inputs.
Fixes #8012

@mmalerba, I think I will have an update tomorrow. I saw your change in the importance of this solution. I am just waiting a device for testing. I do not have a mac available, so I'm taking too long to update this PR. But I want you know that I will have a device available tomorrow, then I will submit the updates.

cool, no worries, I just updated the priority since I realized it affected more types of inputs than I initially realized.

@saulotoledo are you still working on this?

@mmalerba Hi, yes. I tried some approaches, but I had some issues with older IE versions. But my problem is the device's availability for Safari. I have another to borrow this weekend. How much time can you give me yet?

Still no rush, I just wanted to confirm if you're still working on it

Hi @mmalerba. I did a rebase before starting to clean up my code to submit. I just noticed that my fixes were not necessary. I removed them and returned to the previous version of the code; sounds that the duplicated placeholder is no longer a problem. If you have some time, could you take another look at my code? In the meantime I will keep looking for issues.

@saulotoledo The placeholder issue may have been indirectly fixed by some of the changes we've been making to support the appearance=fill and appearance=outline versions of the form-field. But the underlying problem of the <input> being a different height still seems to exist. It can be seen when you try to align inputs of different types. For example:
<div style="display:flex">
  <mat-form-field>
    <input matInput type="datetime-local" placeholder="Date">
  </mat-form-field>
  <mat-form-field>
    <input matInput type="number" placeholder="Duration" >
  </mat-form-field>
</div>

Results in this:

If your solution helps with this, it would be good to still submit it.

@mmalerba The current changes solves that. There is a a demo in the following link:
https://saulotoledo-ng-material2-demo1.firebaseapp.com/input
Let me know if I need to make changes.

Looks great on Chrome, I'll test it out on a few other browsers after you fix the Safari bug. Thanks for the work on this!

@mmalerba, the last problem is fixed for Safari, but Microsoft Edge crashes while using ::first-line (used for solving that clipping problem in Safari. You can see on Travis, and I was able to reproduce in a Windows Machine). I am trying to find another solution for that.

Hi @mmalerba. As I said in my previous comment some minutes ago, Microsoft Edge will crash if we have ::first-line for inputs in the code. Sounds like an issue on Edge (you can also check the previous travis builds to see that it also fails, like here). While trying to find a solution, I updated my PR to contain a padding hack. I did not like that magic number there, but this is the straightforward solution I have found to solve the problem on Safari and on every other web browser. I would like to hear from you what do you think about.
Preview:
https://saulotoledo-ng-material2-demo2.firebaseapp.com/input

Hmm the 1px padding seems to through off the baseline a bit. What about this instead?  Use the safari check in @angular/cdk/platform to apply a specail class to the input if the browser is safari (e.g. mat-input-safari) then target your rule at that instead of the generic mat-input-element

Hi @mmalerba. Thanks for the feedback. Could you confirm if my last changes are what you are expecting?
I did a rebase with the master branch, but sounds something is broken in the master and my branch is not working. But tomorrow I will do another rebase and upload a new live preview.

There seems to be some unexpected screenshot diffs when trying to sync this into google3, needs to be investigated.

@saulotoledo If you want to try it out the change in an app and see if it causes differences feel free. The screenshot diffs I'm talking about are for internal Google applications, so a Googler will need to investigate. It's not even necessarily anything wrong with the PR, could be that someone has global styles for input { height: 1em; } or something like that.

Hi @mmalerba, I just rebased the branch to solve the merge conflict at src/lib/input/input.ts. :)

@mmalerba to revisit this PR to see if it's still relevant

I think this one is just infeasible to land. It causes too many broken looking screenshots inside Google.

I think this one is just infeasible to land. It causes too many broken looking screenshots inside Google.


Employing Apalache for test case generation

Problem description
I am trying to use Apalache for test case generation, and have found that it behaves in an interesting way; would appreciate any help to improve my understanding.
Suppose I have the following (toy) spec, for which I want to generate test cases:
---- MODULE Test5 ----
EXTENDS Integers
VARIABLE
    \* @type: Int;
    x,
    \* @type: Int;
    y

Init == x = 0 /\ y = 0

Next == \/ x' = x + 1 /\ UNCHANGED <<y>>
        \/ y' = y + 1 /\ UNCHANGED <<x>>

Sum5And2x == x + y >= 5 /\ x >=2
NotSum5And2x == ~Sum5And2x

Sum5And2y == x + y >= 5 /\ y >=2
NotSum5And2y == ~Sum5And2y

======================

So either x or y is incremented at each step, and I am interested in traces where the sum reaches 5, and either x or y is incremented at least twice.
I do it by running Apalache like this: apalache check --inv=NotSum5And2x --max-error=10 Test5.tla. I expect to get 10 different traces where x is implemented at least twice. Instead, I get 10 identical traces like this:
---------------------------- MODULE counterexample ----------------------------

EXTENDS Test5

(* Constant initialization state *)
ConstInit == TRUE

(* Initial state *)
State0 == x = 0 /\ y = 0

(* Transition 0 to State1 *)
State1 == x = 1 /\ y = 0

(* Transition 0 to State2 *)
State2 == x = 2 /\ y = 0

(* Transition 0 to State3 *)
State3 == x = 3 /\ y = 0

(* Transition 0 to State4 *)
State4 == x = 4 /\ y = 0

(* Transition 0 to State5 *)
State5 == x = 5 /\ y = 0

(* The following formula holds true in the last state and violates the invariant *)
InvariantViolation == x + y >= 5 /\ x >= 2

================================================================================

From apalache check --inv=NotSum5And2y --max-error=10 Test5.tla I get the traces that increment y twice, but also 10 identical ones:
---------------------------- MODULE counterexample ----------------------------

EXTENDS Test5

(* Constant initialization state *)
ConstInit == TRUE

(* Initial state *)
State0 == x = 0 /\ y = 0

(* Transition 0 to State1 *)
State1 == x = 1 /\ y = 0

(* Transition 1 to State2 *)
State2 == x = 1 /\ y = 1

(* Transition 1 to State3 *)
State3 == x = 1 /\ y = 2

(* Transition 1 to State4 *)
State4 == x = 1 /\ y = 3

(* Transition 0 to State5 *)
State5 == x = 2 /\ y = 3

(* The following formula holds true in the last state and violates the invariant *)
InvariantViolation == x + y >= 5 /\ y >= 2

================================================================================

I can try to use Apalache in simulation mode, like this apalache simulate --length=5 --max-run=10 --output-traces Test5.tla. This way I do get 10 different traces, but they are not constrained by the invariant, so I may get traces that do not increment x twice, for example; in other words I can't focus the search.
I can try to do invariant checking in simulation mode, like this: apalache simulate --inv=NotSum5And2x --max-error=10 --length=5 --max-run=10 --output-traces Test5.tla; but then after the first or second of generated example traces violate the invariant, simulation stops, and again 10 equivalent traces are produced, like this one:
---------------------------- MODULE counterexample ----------------------------

EXTENDS Test5

(* Constant initialization state *)
ConstInit == TRUE

(* Initial state *)
State0 == x = 0 /\ y = 0

(* Transition 1 to State1 *)
State1 == x = 0 /\ y = 1

(* Transition 1 to State2 *)
State2 == x = 0 /\ y = 2

(* Transition 0 to State3 *)
State3 == x = 1 /\ y = 2

(* Transition 1 to State4 *)
State4 == x = 1 /\ y = 3

(* Transition 0 to State5 *)
State5 == x = 2 /\ y = 3

(* The following formula holds true in the last state and violates the invariant *)
InvariantViolation == TRUE

================================================================================

Note that this trace is different than the one obtained via apalache check, because it was obtained via simulation first; but then it is again multiplied 10 times.
To summarize: I don't see the way how to currently employ Apalache for test case generation. Probably I am missing some options or configuration parameters?
Desired solution
I would like to be able to do the following:

When used in invariant checking mode, apalache check --max-error=N should produce N different traces violating the invariant
When used in simulation mode, apalache simulate --inv=INV --max-error=N --max-run=M should do M simulation runs even if invariant is violated. If it is violated for one of the simulated traces, then the model checker should try to produce N different violating traces that are similar to the current violating trace. The important point is that M different simulation traces should be produced in any case, violating the invariant or not.

I don't know whether the desired solution is feasible, only describing my ideal scenario. I would really appreciate your help here in either improving my understanding, or in bringing some enhancements to Apalache.

Hi Andrey!
Apalache will produce different counter-examples under the hood in SMT, but their projection onto spec variables may be equivalent. You can manually define equivalence classes by giving the projection to exclude via --view to enumerate counterexamples (Apalache manual).
For your given spec, this could be as simple as
\* @type: <<Int>>;
View == << x >>

and
apalache-mc check --inv=NotSum5And2x --max-error=10 --view=View Test5.tla.

Is this a feasible solution for your purposes, or do you need a more automated approach?

Technical question for @konnov: Looks like SeqModelChecker.excludePathView() is currently a no-op if no view is provided. Is that intended?

Correct. The first point is a duplicate of #1004.

Technical question for @konnov: Looks like SeqModelChecker.excludePathView() is currently a no-op if no view is provided. Is that intended?

We've never implemented it, as it will most likely have very poor performance without a view. But in the @andrey-kuprianov's example it will definitely work fine. @thpani, would you like to try implementing #1004? It can be either implemented in SeqModelChecker.excludePathView() or by adding a default view in:
https://github.com/informalsystems/apalache/blob/b39ce05b2f8f51858d6ae5262fe5812a59e7ebaf/tla-bmcmt/src/main/scala/at/forsyte/apalache/tla/bmcmt/VCGenerator.scala#L86-L108

This one is probably also related: #1040

To summarize: I don't see the way how to currently employ Apalache for test case generation. Probably I am missing some options or configuration parameters?

As @thpani suggested, introduce:
\* requires a type annotation in this case, as <<Int, Int>> can either be a tuple, or a sequence
\* @type: <<Int, Int>>;
View == <<x, y>>

and run:
apalache-mc check --inv=NotSum5And2x --max-error=10 --view=View Test5.tla

We will see what can be done about #1004. However, the default view will be a very suboptimal solution.

I can try to use Apalache in simulation mode, like this apalache simulate --length=5 --max-run=10 --output-traces Test5.tla. This way I do get 10 different traces, but they are not constrained by the invariant, so I may get traces that do not increment x twice, for example; in other words I can't focus the search.

@andrey-kuprianov, note that this is the feature that lets you generating traces, when the user did not want to specify an invariant.

When used in simulation mode, apalache simulate --inv=INV --max-error=N --max-run=M should do M simulation runs even if invariant is violated. If it is violated for one of the simulated traces, then the model checker should try to produce N different violating traces that are similar to the current violating trace. The important point is that M different simulation traces should be produced in any case, violating the invariant or not.

I do not understand this point. Why do you need to perform M runs, if you have already found N errors? I think it would make sense to add another flag that limits the number of errors per run, so you could say produce 1000 errors in total, while each prefix generates 10 errors max. Most likely, nobody will get the meaning of these flags, so it has to be well hidden in the front-end tooling.

CC from #1004:

Actually, the command documentation says:

--view : the state view to use with --max-error=n, default: transition index

Apparently, the transition index is not used by default.

This may be another option for the default exclusion behavior: Generate counterexamples that differ in transition indices.

I think it would make sense to add another flag that limits the number of errors per run, so you could say produce 1000 errors in total, while each prefix generates 10 errors max.

@konnov this also sounds like a nice option: to provide the global maximum, and then a local maximum for each case. This is actually what I want; we'll figure out the details later.

@thpani, @konnov the suggestion about using Views is the right one, thanks! I of course new about them, but somehow forgot in this case...
Having some automation by default would be nice though... with either default views, defaulting to a tuple of all state variables, or simply to transition index, smth. like this; you know the technical details better, whatever makes more sense.
From the MBT side, we will of course later employ smth. more advanced via the server mode to come. But for the end user, seeing 10 identical examples is confusing. Would be great to improve the experience of unexperienced users:)

I think it would make sense to add another flag that limits the number of errors per run, so you could say produce 1000 errors in total, while each prefix generates 10 errors max.

@konnov this also sounds like a nice option: to provide the global maximum, and then a local maximum for each case. This is actually what I want; we'll figure out the details later.

Here is the relevant issue, we have to do some planning for it: #2143

From the MBT side, we will of course later employ smth. more advanced via the server mode to come. But for the end user, seeing 10 identical examples is confusing. Would be great to improve the experience of unexperienced users:)

We have the relevant discussion about inexperienced users: https://github.com/informalsystems/apalache/discussions/2142


KAFKA-17928: Make remote log manager thread-pool configs dynamic

Description

KIP-1105
KAFKA-17928

Related Link

KIP-1105
KAFKA-17928

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Hi @kamalcph, Thanks for the review.
I do some refactors with your advice, PTAL, thanks! 😄

@kamalcph Thanks for the detailed review, I made some correction base on it.
Please take a look ~
Thanks again!

@peterxcli
There are 3 failed tests, could you fix them?
https://github.com/apache/kafka/actions/runs/11907042194/job/33180295070?pr=17793
FAILED ❌ KRaftClusterTest > testStartupWithNonDefaultKControllerDynamicConfiguration()
FAILED ❌ KRaftClusterTest > testIncreaseNumIoThreads()
FAILED ❌ DynamicBrokerReconfigurationTest > testThreadPoolResize(String).groupProtocol=classic

@peterxcli
I've fixed the unit tests and opened #17859 PR. Added you as the co-author. Thought to open a PR against your branch but you've multiple trunk merges instead of rebase. PTAL.

Hi @kamalcph
Should I close this PR?

yes, we can close this PR and follow-up on #17859


Setup snapshots based on purs-backend-es

Fixes #2

I'm not sure how to setup CI for chez scheme, but that's something that should be done after this.

LGTM. I guess CI for Chez would just involve evaluating the files?

Yeah, I think that's a good idea


Synthesis failed for nodejs-speech

Hello! Autosynth couldn't regenerate nodejs-speech. :broken_heart:
Here's the output from running synth.py:
2020-05-14 06:37:06,768 autosynth [INFO] > logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/nodejs-speech
2020-05-14 06:37:06,771 synthtool [ERROR] > Failed executing git clone --single-branch https://github.com/googleapis/nodejs-speech.git /home/kbuilder/.cache/synthtool/nodejs-speech:

fatal: could not create work tree dir '/home/kbuilder/.cache/synthtool/nodejs-speech': No space left on device

Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 600, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 472, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 519, in _inner_main
    working_repo_path = synthtool_git.clone(f"https://github.com/{args.repository}.git")
  File "/tmpfs/src/github/synthtool/synthtool/sources/git.py", line 83, in clone
    shell.run(cmd, check=True)
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['git', 'clone', '--single-branch', 'https://github.com/googleapis/nodejs-speech.git', PosixPath('/home/kbuilder/.cache/synthtool/nodejs-speech')]' returned non-zero exit status 128.

Google internal developers can see the full log here.

Autosynth is still having trouble generating nodejs-speech. :sob:
Here's the output from running synth.py:
2020-05-14 16:12:48,983 autosynth [INFO] > logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/nodejs-speech
2020-05-14 16:12:48,987 synthtool [ERROR] > Failed executing git clone --single-branch https://github.com/googleapis/nodejs-speech.git /home/kbuilder/.cache/synthtool/nodejs-speech:

fatal: could not create work tree dir '/home/kbuilder/.cache/synthtool/nodejs-speech': No space left on device

Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 600, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 472, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 519, in _inner_main
    working_repo_path = synthtool_git.clone(f"https://github.com/{args.repository}.git")
  File "/tmpfs/src/github/synthtool/synthtool/sources/git.py", line 83, in clone
    shell.run(cmd, check=True)
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['git', 'clone', '--single-branch', 'https://github.com/googleapis/nodejs-speech.git', PosixPath('/home/kbuilder/.cache/synthtool/nodejs-speech')]' returned non-zero exit status 128.

Google internal developers can see the full log here.

Autosynth is still having trouble generating nodejs-speech. :sob:
Here's the output from running synth.py:
2020-05-14 19:39:03,361 autosynth [INFO] > logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/nodejs-speech
2020-05-14 19:39:03,366 synthtool [ERROR] > Failed executing git clone --single-branch https://github.com/googleapis/nodejs-speech.git /home/kbuilder/.cache/synthtool/nodejs-speech:

fatal: could not create work tree dir '/home/kbuilder/.cache/synthtool/nodejs-speech': No space left on device

Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 601, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 473, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 520, in _inner_main
    working_repo_path = synthtool_git.clone(f"https://github.com/{args.repository}.git")
  File "/tmpfs/src/github/synthtool/synthtool/sources/git.py", line 83, in clone
    shell.run(cmd, check=True)
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['git', 'clone', '--single-branch', 'https://github.com/googleapis/nodejs-speech.git', PosixPath('/home/kbuilder/.cache/synthtool/nodejs-speech')]' returned non-zero exit status 128.

Google internal developers can see the full log here.

Autosynth is still having trouble generating nodejs-speech. :sob:
Here's the output from running synth.py:
2020-05-15 05:48:28,522 autosynth [INFO] > logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/nodejs-speech
2020-05-15 05:48:28,525 synthtool [ERROR] > Failed executing git clone --single-branch https://github.com/googleapis/nodejs-speech.git /home/kbuilder/.cache/synthtool/nodejs-speech:

fatal: could not create work tree dir '/home/kbuilder/.cache/synthtool/nodejs-speech': No space left on device

Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 601, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 473, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 520, in _inner_main
    working_repo_path = synthtool_git.clone(f"https://github.com/{args.repository}.git")
  File "/tmpfs/src/github/synthtool/synthtool/sources/git.py", line 83, in clone
    shell.run(cmd, check=True)
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['git', 'clone', '--single-branch', 'https://github.com/googleapis/nodejs-speech.git', PosixPath('/home/kbuilder/.cache/synthtool/nodejs-speech')]' returned non-zero exit status 128.

Google internal developers can see the full log here.

Autosynth passed, closing! :green_heart:


Adding github action, component definition, schema

Adding github action
Adding component definition
Adding component schema
Adding demo python app which hits http end point and need python requests package from pypi.org

@anandchugh what is the DCO check that was not successful? I haven't seen that before.

@anandchugh what is the DCO check that was not successful? I haven't seen that before.

Fixed DCO(Developer Certificate of Origin) issue, it says we need to signoff each commit.
Quick way to signoff each commit by using git commit -s command
Or we can add following in commit message

Signed-off-by: Random J Developer<EMAIL_ADDRESS>

@anandchugh what is the DCO check that was not successful? I haven't seen that before.

Fixed DCO(Developer Certificate of Origin) issue, it says we need to signoff each commit. Quick way to signoff each commit by using git commit -s command Or we can add following in commit message

Signed-off-by: Random J Developer<EMAIL_ADDRESS>


Error when deepcopy the variable(s) which is defined in json file(s) in robot testcase

An error KeyError: '__deepcopy__' occurs when deepcopy the variable which is defined in json configuration file.
Sample robot testcase to deepcopy an __TESTBENCH__CONFIG which defined in json file
*** Settings ***
Library     RobotFramework_Testsuites    WITH NAME    testsuites
Library     Collections
Suite Setup      testsuites.testsuite_setup    ../../../config/testsuites_config.json
Suite Teardown   testsuites.testsuite_teardown

*** Test Cases ***
Error when deepcopy a variable from json configuration file
    ${new_config}=     Copy Dictionary   ${__TESTBENCH__CONFIG}    deepcopy=True

I have investigated and found that the error comes from the dotdit module which is used in testsuitesmanament.
I observe that robotframework also has dotdict module which works properly as our expectation.
Thank you,
Ngoan

Hello Ngoan,
I have just checked, this is limited of deepcopy() method on dotdict object.
I will try to find the solution to fix this issue.

Thank you,
Son

Hello Ngoan,
 I made the change regarding to this issue: Pull request #21

Thank you,
Son

This issue is solved.


Workflow registration extended parameters

Continuing on from #1, more parameters:

Default task priority
Default Lambda role (after #6)
Default child policy (after #5)

Default task-priority is waiting on spulec/moto#2756

Closed by e9fc698


Cow: Watch zyro.in

Cow requests the watch of the watch_keyword zyro\.in. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

zyro\.in has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by VLAZ in Charcoal HQ


Add explicit numericalization of labels

Currently, the numericalization of labels is dependent on the order of the folders in the filesystem.
A possible improvement would be to explicitly define a file with mapping information.
For example
{
  'positive':0,
  'negative':1,
}

Alternatively the order of classes in metadata.yaml file of each dataset could be used.
This would allow the user to explicitly filter the data by label and make the numericalization more consistent.
The following are code snippets that rely on the order of folders to label samples.
https://github.com/ML-Bioinfo-CEITEC/genomic_benchmarks/blob/75e3f190104625445f79363522fc8bf16f41590f/src/genomic_benchmarks/data_check/info.py#L99-L105
https://github.com/ML-Bioinfo-CEITEC/genomic_benchmarks/blob/75e3f190104625445f79363522fc8bf16f41590f/src/genomic_benchmarks/dataset_getters/pytorch_datasets.py#L38-L39
Tensorflow notebook demo :arrow_down:
CLASSES = [x.stem for x in (SEQ_PATH/'train').iterdir() if x.is_dir()]

train_dset = tf.keras.preprocessing.text_dataset_from_directory(
    SEQ_PATH / 'train',
    batch_size=BATCH_SIZE,
    class_names=CLASSES)

Update:
We dont have to require explicit labels, but we need to give users the opportunity to explicitly numericalize labels.
This means we should add optional parameter to the pytorch datasets, which will allow for explicit numericalization.


Add support for relative paths in Open

This is just a simple fix to allow nesting files in a resource folder, like this:

And calling Open like this: goaseprite.Open("assets/player.json").
A bit more context
When the aseprite json has meta.image = player.png, and the .go file executing the goaseprite.Open() call is in another folder, the path to the png is incorrect.
This PR addresses this by parsing the folder path and "correcting" imagePath.
This means that goaseprite.Open("assets/player.json") now works as expected:
Small concern here, but I tested it and it works fine: filepath.Dir behaves nicely when there's no folder in the path, it just returns a ., which means that we get ./player.png for example, and it's all good :)

Thanks for the PR request!
There's a few problems, though. Firstly, this shouldn't use forward slash ( "/" ) directly, but instead use filepath.Join() to be cross-platform compatible.
Secondly, this assumes the image is in the same folder as the .json file; it might not be, and Aseprite doesn't export the full path, but rather just the image name. So unfortunately, I don't think this will work; I think the only real "solution" would probably be to just rename File.ImagePath attribute to File.ImageName or something like that.

No problems at all, happy to close it! I've since found workarounds anyway :)
Thanks for the review, and don't worry at all about the late reply 😀


Kodezi authentication

Kodezi authentication problem, I cannot connect my account to the extension in VS code. So I cannot use Kodezi in vs code.
To Reproduce
Steps to reproduce the behavior:

Go to "Extensions"
Click on 'The search bar'
Type 'Kodezi'
Install 'Kodezi'
Go to "Kodezi"
Click on "Sign Up/ Sign In (It will open the authentication link in a browser)"
Then "Sign Up/Sign In and come back to vs code)

Expected behavior
After all this steps you should be able to use Kodezi in VS cosde
Desktop

OS: Windows 11
Browser: Opera Gx
Version: 97.0.4719.89

I haven't tried to see if it works on Firefox, Safari, Opera or Edge, but it works on Chrome to authenticate.
So Opera Gx the auth fails on log?format=json&hasfast=true...
but it would be nice if it got fixed for Opera Gx as well.

Consider making an alternative way to put a token into a VSCode session, because not everyone uses plain VSCode. I use VSCode Insiders. Some might use Codium or some other Codium-based vscode build.


[YUNIKORN-1860] fix totalContainers

What is this PR for?
After we add omitempty, we miss TotalContainers in /ws/v1/partitions. Add a default value to fix it.

What type of PR is it?

[ ] - Bug Fix
[X] - Improvement
[ ] - Feature
[ ] - Documentation
[ ] - Hot Fix
[ ] - Refactoring

Todos

[ ] - Task

What is the Jira issue?
https://issues.apache.org/jira/browse/YUNIKORN-1860
How should this be tested?
Screenshots (if appropriate)
Questions:

[ ] - The licenses files need update.
[ ] - There is breaking changes for older versions.
[ ] - It needs documentation.

Codecov Report

Merging #128 (fe59a6f) into master (91fe955) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #128   +/-   ##
=======================================
  Coverage   66.66%   66.66%
=======================================
  Files           1        1
  Lines          30       30
=======================================
  Hits           20       20
  Misses          7        7
  Partials        3        3

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


add a error prop for setting the error message manually

Please makes sure these boxes are checked before submitting your PR, thank you!

[ ] Make sure you follow Element's Contributing Guide.
[ ] Make sure you are merging your commits to dev branch.
[ ] Rebase before creating a PR to keep commit history clear.
[ ] Add some descriptions and refer relative issues for you PR.

#1216


External link should open in new tab

Steps to reproduce the problem

Go to 'The QML course Introduction page '
In the right-side panel, click on 'qRAM > Read more'
(The same link can be found in the qRAM annotation, by hovering over the word

What is the current behavior?
This link opens in the same tab.
What is the expected behavior?
All other external links on the page open in a new tab, this should be treated similarly (if possible)
Screenshots of where the Read more link can be found

This repository is no longer maintained. It has been superseded by IBM Quantum Learning.


wrong getClientRects

I am using getClientRects to render custom selection box. but KaTeX generates wired border box. is there anyway to fix this?
compare this:

@molikto this is a long standing issue.  We've deprecated support for older browsers which opens the door for us to try things like #1409 to solve this issue.  Another benefit of that approach is that it should greatly simplify the markup we produce.


Can't remove white spaces separator from the middle of the masked phone number

Hello. Can't remove white spaces separator from the middle of the masked phone number.
React Native: 0.64.1,
react-native-masked-text: 1.13.0
OS: iOS
Same issue: #35 , #198
<TextInputMask   type={'custom'}   options={{      mask: '+999 999 999 999 99'    }} />
After i putt phone number i can delete it if cursor on a number but if i put it on empty space separator nothing happening!
Any ideas?

same here


Inactive autolinks and missing producers/consumers in Artemis - restarts don't help

We have just gotten in a situation, where brokered addresses are all marked isReady=false because of missing autolinks and seemingly can't be made to get ready again (by restarting enmasse components).
In the broker, queues are there but producers and consumers for the addresses are missing.
Logs:
logs.zip

Admin pod restart doesn't change things (logs_3_admin_restart.zip).
The Connections tab contains one entry:

Ok, so this connection that is there doesn't look like the connector service, since the local address iss :5673 which is the incoming port. It would be interesting if you could list the connector services. I think it might be possible to do in the broker console if you use the 'broker' object and find and an attribute or operation called 'getConnectorServices'.

The ConnectorServices attribute contains "amqp-connector router-connector".
So I guess that looks ok.

I think this means there is some issue with the connector service, since it is created, but you don't see an outgoing connection established, neither to the agent (amqp-connector) or the router.  If you can provide me a jstack and a jmap heap dump for analysis I can try to figure out what has happened.

I think the "Connections" tab doesn't show these connections - at least it doesn't on another system of ours where all addresses are ready.
Thread dump is here:
threads.dump.zip

Here the router connections:
router_connections.txt

The autolinks from qdmanage point to the issue I think. After the change to support per-address limits in the broker, the agent changed to create a connector service per queue. However, it looks like this is not happening for some reason, as only connector services amqp-connector and router-connector are present.

Looking at the agent code, it looks like the agent only checks if addresses/queues exists and not connector services, thereby not recreating the connector services if an address already exists. This is similar to a bug that was in the queue-scheduler at some point.
@grs In broker_controller.js BrokerController.prototype._sync_broker_addresses it looks like it is doing a listAddresses(), and then creates addresses + connector service for each missing address. If the broker is restarted, however, the broker will return the addresses, but the connector services will be missing in the broker, so the logic must be changed to check the connector services as well. I guess this was introduced when it was changed to create a connector service per address.


Collect feature usage stats from VSCode telemetry API

Fixed with https://github.com/ballerina-platform/plugin-vscode/issues/186


Eth connect issues with allowance function

This was reported by Baus and his team
The problem seems to be new. It worked fine on eth-connect 4.0.2, but not in 5.0.0
The following snippet fails:
providerMatic = new EthConnect.HTTPProvider(maticRPCURL);
requestManagerMatic = new EthConnect.RequestManager(providerMatic);
const factoryMANA = await new EthConnect.ContractFactory(
    requestManagerMatic,
    ABIMANA
);
contractInstanceMANA = (await factoryMANA.at(
    manaTokenAddress
)) as any;
approved = await contractInstanceMANA.allowance(
    userWalletAddress,
    treasuryContractAddress
);

The problem is when calling allowance function.

Uncaught (in promise) Error: invalid argument 0: json: cannot unmarshal invalid hex string into Go struct field CallArgs.data of type hexutil.Bytes

Test values for each variable are required to debug. Including contract addresses please

@menduz can you drop your email here?
I will share via email.

Please share the details here, I will receive the email notifications.
I wrote specific tests for this specific issue, testing against geth and ganache. https://github.com/decentraland/eth-connect/pull/36/files#diff-d013a98cbb4e8036db3f6b5dd308d151b282e69fc327792dfe864020963efb04R182-R191
We need the specific request body you are sending to matic that is yielding that error, among with the exact values you provided to the function call allowance.

PS: you can see what is being exchanged with matic to help us debug by writing providerMatic.debug = true

SEND >> {"jsonrpc":"2.0","id":6,"method":"eth_call","params":[{"from":"0x6224fe0bea79701d338cf65ebc0da0caa566c544","to":"0x11e46DB40d4438D1c64f68993CA43b03Ac1B6A6B","data":"0x39c2a5380000000000000000000000006224fe0bea79701d338cf65ebc0da0caa566c544"},"latest"]}

RECV << {"jsonrpc":"2.0","id":4,"error":{"code":-32602,"message":"invalid argument 0: json: cannot unmarshal invalid hex string into Go struct field CallArgs.data of type hexutil.Bytes"}}

I have tried to reproduce the issue installing eth-connect@next
My wallet address is 0x6224fe0bea79701d338cf65ebc0da0caa566c544.
And treasuryContractAddress is 0xBF79cE2fbd819e5aBC2327563D02a200255B7Cb3.

Please attack the whole debug log. The error corresponds to the RCP id 6, but you are only attaching the 4th (SEND & RECV things)

Hey @menduz ,
I am adding a whole screenshot of my console logs.

Ok, you should be able to provide me more data with that screenshot.
the lines with SEND id: 3 SEND id: 4 SEND id: 5 in the middle of the console have a NaN at the end of the HEX
The contract is  0xA1c57f48F0Deb89f569dFbE6E2B7f46D33606fD4 and the selector is allowance(address,address) => 0xdd62ed3e
Could you print exactly what you are passing to the allowance functions? (you are calling it three times by the way, beware of that since you must execute it once per account)

approved = await contractInstanceMANA.allowance(
        walletAddress,
        contractAddress
);

this is how I am calling allowance function.

I need the arguments. Print what you are passing to it

because it seems that contractAddress is an invalid value

-115,133:  walletAddress -------------------- 0x6224fe0bea79701d338cf65ebc0da0caa566c544
-115,133:  contractAddress ---------------  0xBF79cE2fbd819e5aBC2327563D02a200255B7Cb3

does it has a heading space? [space]0xBF79cE2fbd819e5aBC2327563D02a200255B7Cb3

No.

try printing it with JSON.stringify(contractAddress) because it has tests working, and I have no clue on why is it being converted to NaN instead of a valid bignumber in your code

-115,133:  walletAddress --------------------: "0x6224fe0bea79701d338cf65ebc0da0caa566c544"
-115,133:  contractAddress ---------------: "0xBF79cE2fbd819e5aBC2327563D02a200255B7Cb3"

Here you go.

approved = await contractInstanceMANA.allowance(
      "0x6224fe0bea79701d338cf65ebc0da0caa566c544",
      "0xBF79cE2fbd819e5aBC2327563D02a200255B7Cb3"
    );

I changed the code like this and tried again but got same result.

Nailed it, it was a wild bug. For some reason the upper case of the address made the big number library fail. I'm pushing a fix now. In the meantime, could you try with a walletAddress.toLowerCase(), contractAddress.toLowerCase() to see if it works?

OK!

Here is the fix, in case you wonder. It should be available for you in some minutes installing it with @next

Fixed


release: v0.5.0

Description
- chore!: remove excluded users from ListUsers response

BREAKING CHANGE:

This version removes the `excluded_users` property from the `ListUsersResponse` and `ClientListUsersResponse` interfaces,
for more details see the [associated API change](https://github.com/openfga/api/pull/171).

References

Review Checklist

[x] I have clicked on "allow edits by maintainers".
[ ] I have added documentation for new/changed functionality in this PR or in a PR to openfga.dev [Provide a link to any relevant PRs in the references section above]
[x] The correct base branch is being used, if not main
[ ] I have added tests to validate that the change in functionality is working as expected

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

Project coverage is 83.57%. Comparing base (2c78c5d) to head (beade10).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #115   +/-   ##
=======================================
  Coverage   83.57%   83.57%
=======================================
  Files          18       18
  Lines         968      968
  Branches      168      220   +52
=======================================
  Hits          809      809
  Misses         76       76
  Partials       83       83

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


Add function to rebuild hg workspace on a new machine

I would wait to make sure this works correctly first


Fix/init blocking

What

moves the init integration test into the integration dir
makes the init command async, and then uses the async reqwest client.

Why
I was seeing this error when running contract init on main:
thread 'main' panicked at .cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.39.2/src/runtime/blocking/shutdown.rs:51:21:
Cannot drop a runtime in a context where blocking is not allowed. This happens when a runtime is dropped from within an asynchronous context.
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

This happens because we were trying to use the blocking reqwest client inside of an async runtime, since all of the cli is in an tokio runtime. This doesn't work well together, so I've changed the init command to be async and then we're able to await the HTTP calls.
Known limitations
This won't be an issue once https://github.com/stellar/stellar-cli/pull/1628/files is merged - but we'll still want to move the init test into the integration dir - I think that this test was previously not being run.

Because #1628 is merged, does anything from this change still need to be merged?

Because https://github.com/stellar/stellar-cli/pull/1628 is merged, does anything from this change still need to be merged?

Sorry for missing this question earlier! You're right, since #1628 was merged, this can just be closed.

I should also note that I think this error wasn't caught in the init integration test because of https://github.com/stellar/stellar-cli/issues/1682


install errors

hi, I am trying to install your rpi-dashboard on Raspian and hit a build error when trying to set up monkey in dudac.  Here is my complete log for reference.  Any ideas?  I got a build error at the dudac/dudac step that seems to cause the problem later,
Looking fwd to working wit this app and REST for my project.
Thanks
Rick
pi@Symmetry-RPI ~ $ git clone git://git.drogon.net/wiringPi
Cloning into 'wiringPi'...
remote: Counting objects: 742, done.
remote: Compressing objects: 100% (676/676), done.
remote: Total 742 (delta 537), reused 94 (delta 58)
Receiving objects: 100% (742/742), 262.85 KiB | 126 KiB/s, done.
Resolving deltas: 100% (537/537), done.
pi@Symmetry-RPI ~ $ cd wiringPi && ./build
wiringPi Build script
WiringPi Library
[UnInstall]
[Compile] wiringPi.c
[Compile] wiringSerial.c
[Compile] wiringShift.c
[Compile] piHiPri.c
[Compile] piThread.c
[Compile] wiringPiSPI.c
[Compile] wiringPiI2C.c
[Compile] softPwm.c
[Compile] softTone.c
[Compile] mcp23008.c
[Compile] mcp23016.c
[Compile] mcp23017.c
[Compile] mcp23s08.c
[Compile] mcp23s17.c
[Compile] sr595.c
[Compile] pcf8574.c
[Compile] pcf8591.c
[Compile] mcp3002.c
[Compile] mcp3004.c
[Compile] mcp4802.c
[Compile] max31855.c
[Compile] mcp3422.c
[Compile] max5322.c
[Compile] sn3218.c
[Compile] drcSerial.c
[Compile] wpiExtensions.c
[Link (Dynamic)]
[Install Headers]
[Install Dynamic Lib]
WiringPi Devices Library
[UnInstall]
[Compile] ds1302.c
[Compile] maxdetect.c
[Compile] piNes.c
[Compile] gertboard.c
[Compile] piFace.c
[Compile] lcd128x64.c
[Compile] lcd.c
[Compile] piGlow.c
[Link (Dynamic)]
[Install Headers]
[Install Dynamic Lib]
GPIO Utility
[Compile] gpio.c
[Compile] readall.c
[Compile] pins.c
[Link]
[Install]
All Done.
NOTE: To compile programs with wiringPi, you need to add:
-lwiringPi
to your compile line(s) To use the Gertboard, MaxDetect, etc.
code (the devLib), you need to also add:
-lwiringPiDev
to your compile line(s).
pi@Symmetry-RPI ~/wiringPi $ git clone https://github.com/monkey/dudac.git
Cloning into 'dudac'...
remote: Counting objects: 305, done.
remote: Total 305 (delta 0), reused 0 (delta 0), pack-reused 305
Receiving objects: 100% (305/305), 85.35 KiB, done.
Resolving deltas: 100% (177/177), done.
pi@Symmetry-RPI ~/wiringPi $ dudac/dudac -s
Duda Client Manager - v0.31
http://duda.io
http://monkey-project.com
[i] HOME        : /home/pi/.dudac/
[i] STAGE       : /home/pi/.dudac/stage/
[+] Monkey: cloning source code                                            [OK]
[+] Duda: cloning source code                                              [OK]
[+] GIT Monkey  : switch HEAD to 'dst-1'                                   [OK]
[+] GIT Duda    : switch HEAD to 'dst-1'                                   [OK]
[+] GIT Monkey  : archive                                                  [OK]
[+] GIT Duda    : archive                                                  [OK]
[+] Monkey      : prepare build                                            [OK]
[+] Monkey      : building                                                 [OK]
--- Compiler Warnings ---
mk_method.c:121:29: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
mk_epoll.c:302:18: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
mk_epoll.c:399:18: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
--- * --- * --- * --- * ---
pi@Symmetry-RPI ~/wiringPi $ git clone https://github.com/matematik7/rpi-dashboard.git
Cloning into 'rpi-dashboard'...
error: The requested URL returned error: 403 while accessing https://github.com/matematik7/rpi-dashboard.git/info/refs
fatal: HTTP request failed
pi@Symmetry-RPI ~/wiringPi $ git clone https://github.com/matematik7/rpi-dashboard.git
Cloning into 'rpi-dashboard'...
remote: Counting objects: 1565, done.
remote: Total 1565 (delta 0), reused 0 (delta 0), pack-reused 1565
Receiving objects: 100% (1565/1565), 295.48 KiB | 327 KiB/s, done.
Resolving deltas: 100% (1041/1041), done.
pi@Symmetry-RPI ~/wiringPi $ cd rpi-dashboard &&git checkout tags/v0.2.0
Note: checking out 'tags/v0.2.0'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b new_branch_name
HEAD is now at 86419c4... Docs: Updated version on release of v0.2.0.
pi@Symmetry-RPI ~/wiringPi/rpi-dashboard $ dudac/dudac -w rpi-dashboard/src
bash: dudac/dudac: No such file or directory
pi@Symmetry-RPI ~/wiringPi/rpi-dashboard $ dudac/dudac -w rpi-dashboard/src
bash: dudac/dudac: No such file or directory
pi@Symmetry-RPI ~/wiringPi/rpi-dashboard $ cd ..
pi@Symmetry-RPI ~/wiringPi $ dudac/dudac -w rpi-dashboard/src
Duda Client Manager - v0.31
http://duda.io
http://monkey-project.com
[i] HOME        : /home/pi/.dudac/
[i] STAGE       : /home/pi/.dudac/stage/
[+] WebService  : clean                                                    [OK]
[+] WebService  : build                                                    [FAILED]
[-] Command exit (status=2): make -C /home/pi/wiringPi/rpi-dashboard/src
make: Entering directory '/home/pi/wiringPi/rpi-dashboard/src'
[CC]   rpi_main.o
[CC]   rpi_modules.o
[CC]   rpi_security.o
[CC]   rpi_config.o
[CC]   rpi_cpu.o
[CC]   rpi_network.o
[CC]   rpi_memory.o
[CC]   rpi_storage.o
[CC]   rpi_string.o
[CC]   rpi_logger.o
[CC]   rpi_websocket.o
[CC]   rpi_gpio.o
[CC]   rpi_i2c.o
[CC]   rpi_serial.o
[CC]   rpi_spi.o
[CC]   rpi_shift.o
rpi_logger.c:27:17: fatal error: rrd.h: No such file or directory
compilation terminated.
[CC]   rpi_general.o
Makefile:29: recipe for target 'rpi_logger.o' failed
make: *** [rpi_logger.o] Error 1
make: *** Waiting for unfinished jobs....
make: Leaving directory '/home/pi/wiringPi/rpi-dashboard/src'
pi@Symmetry-RPI ~/wiringPi $ cd ..
pi@Symmetry-RPI ~ $ dudac/dudac -w rpi-dashboard/src
bash: dudac/dudac: No such file or directory
pi@Symmetry-RPI ~ $ cd /wiringPi
bash: cd: /wiringPi: No such file or directory
pi@Symmetry-RPI ~ $ cd wiringPi
pi@Symmetry-RPI ~/wiringPi $ dudac/dudac -w rpi-dashboard/src
Duda Client Manager - v0.31
http://duda.io
http://monkey-project.com
[i] HOME        : /home/pi/.dudac/
[i] STAGE       : /home/pi/.dudac/stage/
[+] WebService  : clean                                                    [OK]
[+] WebService  : build                                                    [FAILED]
[-] Command exit (status=2): make -C /home/pi/wiringPi/rpi-dashboard/src
make: Entering directory '/home/pi/wiringPi/rpi-dashboard/src'
[CC]   rpi_main.o
[CC]   rpi_security.o
[CC]   rpi_modules.o
[CC]   rpi_config.o
[CC]   rpi_memory.o
[CC]   rpi_cpu.o
[CC]   rpi_network.o
[CC]   rpi_storage.o
[CC]   rpi_string.o
[CC]   rpi_websocket.o
[CC]   rpi_logger.o
[CC]   rpi_gpio.o
[CC]   rpi_i2c.o
[CC]   rpi_spi.o
[CC]   rpi_serial.o
[CC]   rpi_shift.o
rpi_logger.c:27:17: fatal error: rrd.h: No such file or directory
compilation terminated.
[CC]   rpi_general.o
Makefile:29: recipe for target 'rpi_logger.o' failed
make: *** [rpi_logger.o] Error 1
make: Leaving directory '/home/pi/wiringPi/rpi-dashboard/src'

You are missing headers of rrd library, please install librrd-dev. This is noted in installation instructions: http://docs.rpi-dashboard.com/build_from_source/README.html
Please follow them.

This website isn't up anymore and isn't in the wayback machine, does anyone know how to build from source?

@tech189 as specified in README new documentation location is on gitbooks: https://matematik7.gitbooks.io/rpi-dashboard-docs/content/


Implement Task Tag

implement tag for task class
add new test cases for the classes involved
improve some of the previous test cases related to tasks
task tag is updated automatically in the storage (like other fields)

What needs to be done

update GUI to show the task tag (Cheng Yi's task)

Codecov Report

Merging #74 (83afb46) into master (96addd7) will increase coverage by 0.29%.
The diff coverage is 77.04%.

@@             Coverage Diff              @@
##             master      #74      +/-   ##
============================================
+ Coverage     68.85%   69.15%   +0.29%
- Complexity      545      554       +9
============================================
  Files            95       96       +1
  Lines          1782     1822      +40
  Branches        204      212       +8
============================================
+ Hits           1227     1260      +33
- Misses          491      492       +1
- Partials         64       70       +6

Impacted Files
Coverage Δ

...a/seedu/address/logic/commands/AddTaskCommand.java
80.00% <ø> (ø)

...in/java/seedu/address/storage/JsonAdaptedTask.java
50.00% <45.45%> (-5.18%)
:arrow_down:

src/main/java/seedu/address/model/tag/TaskTag.java
70.00% <70.00%> (ø)

src/main/java/seedu/address/model/task/Task.java
84.37% <81.25%> (+13.54%)
:arrow_up:

.../seedu/address/logic/commands/EditTaskCommand.java
84.21% <81.81%> (-0.11%)
:arrow_down:

...edu/address/logic/parser/AddTaskCommandParser.java
91.66% <100.00%> (+0.75%)
:arrow_up:

...ain/java/seedu/address/logic/parser/CliSyntax.java
91.66% <100.00%> (+0.75%)
:arrow_up:

...du/address/logic/parser/EditTaskCommandParser.java
100.00% <100.00%> (ø)

...in/java/seedu/address/logic/parser/ParserUtil.java
98.59% <100.00%> (+0.10%)
:arrow_up:

Continue to review full report at Codecov.

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


some changes xcode 9 suggested

Xcode 9 (GM) complained about the following things. All of them look reasonable.

Thanks!

Welcome, though Xcode did most of the work here 😉.


Scheduler prefers nodes without connection failures

Current swarm scheduler may keep trying the same node until its state changes to 'Unhealthy'. This change makes scheduler aware of connection failures and prefer nodes without failures.
Signed-off-by: Dong Chen<EMAIL_ADDRESS>

LGTM
ping @abronan

@dongluochen This may not be practical to do it (and we might hit timing issues on the CI), but that would be cool if we had the integration tests testing 3 or more engines with different health scores to test the impact of the health score on the scheduling more thoroughly.
LGTM though this should not block the merge.


Improve username behavior

Fixes the behavior of validate_user function in validations.py.
Closes. #1
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[x] Tests pass
[ ] Appropriate changes to README are included in PR

@googlebot  I signed it!


Groovy 8562 wrong closure delegation for property access and compile static

Roundup:
The StaticTypeCheckingVisitor would not look consider FieldNode to potentially delegate to a different Field. I think this could only occur for name collisions, i.e. the owner has a field with the same name as the delegate.
Calling tryVariableExpressionAsProperty solved this, however this broke other tests. To solve this I cheked IMPLICIT_RECEIVER, if unset and PROPERTY_OWNER is present, checkOrMarkPrivateAccess must be called to ensure the accessors are generated.
The VariableExpressionTransformer ignored delegation metadata when a private field accessor was present. I inversed that logic to give delegation metadata precedence over private field accessors.
Build passes https://travis-ci.org/MeneDev/groovy/builds/382561549

@paulk-asert It looks good for me. What do you think about the PR?

on my TODO list to review - at first glance I am optimistic

Merged. Thanks!


Fine-tune journal prompting (maybe use Chat-GPT4?)

Describe the feature or improvement you're requesting
No response
Additional context
No response

Modified the prompt using learnings from https://www.deeplearning.ai/short-courses/chatgpt-prompt-engineering-for-developers/, will probably need more refinement as we iterate, but good for now.


Benjin/delete

Fixes #10819
Adds a Delete option to file/folder context menus, and prompts the user for confirmation before deletion.

I got partway through the deletion work for database references, but I've got some questions on how they work/how it works so I've split that out to a separate PR.

Coverage remained the same at 34.801% when pulling 6a34a5783dbdcaed317814f779dd78a80ae635bb on benjin/delete into cfbce96fe213f5d01c0c010f6def2d63d3de254b on main.


Add a hint about the compatibility with Tasks plugins of the task field emoji shorthands

I was trying to find about this compatibility and and in the docs I did find this.
https://github.com/blacksmithgu/obsidian-dataview/blob/bb594a27ba1eed130d7c2ab7eff0990578e93f62/docs/docs/annotation/metadata-tasks.md?plain=1#L14-L15
While this is a hint (very subtle at that[^1]), I think Dataview would gain to be more explicit about the Tasks compatibility.
I think a simple rewrite of the intro paragraph for the shorthand fields could be read something likes
## Field Shorthands

Another plugin, [Tasks](https://publish.obsidian.md/tasks/Introduction) introduced a different [notation by using Emoji](https://publish.obsidian.md/tasks/Reference/Task+Formats/Tasks+Emoji+Format) to configure the different dates related to a task.
In the context of Dataview, this notation is called `Field Shorthands`.
The current version of Dataview only support the dates shorthands as shown below.
The priorities and recurrence shorthands are not supported.

=== "Example"

Also, regarding the opposite compatibility, the Tasks plugin seems to have made quite an effort to document the compatibility with Dataview format on their side.
[^1]: As a side note, as a reader that English is not my first language and having difficulty to understand nuances in writing (that part is also in my first language), when reading this part the first time, I didn't make the connection to the Tasks plugin right away. In fact, I felt that the tone used was kinda elitist or trying to minimize the existence/reduce the impact of other plugins (the round-trip translation and interpretation in my head kinda sounded like "we know about other methods for tasks, we don't agree with those but we kinda support them in spite of our opinions"). This is probably NOT what you wanted to convey, but I just want to point out this is what my feeling was while reading this portion.


Composer detected issues in your platform: Your Composer dependencies require a PHP version ">= 7.3.0".

I have added docker today and getting this error.  I have used docker image the latest one.
can anyone point me into right direction?
Thanks in advance.

I may have messed up with different composer and vendor folder.
Just delete vendor folder and composer.lock file and restart. I fixed it. Thanks


404 on CDN

https://cdn.rawgit.com/google/code-prettify/master/loader/lang-json.js
Is unavailable. Is there an updated link?

There is no separate extension for lang-json.js.
JSON support is included in the core prettify.js, just specify the lang-json class.
Here is a live example: https://jsfiddle.net/amroamroamro/swybxhmw/


Investigate compression support

Docs: https://github.com/typhoeus/typhoeus/#compression

Verified that Content-Encoding: gzip is part of the response headers. Unsure if adding support in the call will make difference, or just be idiomatic.

Added as part of #7


Checking the length of the name field

The errors are now thrown by the data service and handled in the view by showing an alert.
Tests have been added.


refactor: change wallet.js to wallet.ts

Changes description
Changing wallet.js to wallet.ts and fix all compiler warning about the types

Need to close this PR
I have messed things up by committing into the branch after submitting the PR, I should have working on a new branch instead.


[Feature]: Integrate new backend

🚀 The feature, motivation and pitch
Currently, vLLM supports TPU and XPU. We would like to use vLLM on new backend.
What are the community's suggestions or plans for integrating new devices?
Alternatives
There may be the following two methods:
1. Add new backend by modify codebase
Such as XPU, Added XPUExecutor, XPUWorker, XPUModelRunner to isolate XPU backend with others.
How the community reviews new backend integrations?
2. Provide Out-of-Tree backend registration
Integrate a backend without modifying the vLLM codebase.
We use PrivateUse1 to integrate new backend in PyTorch, and expected to integrate new backend in vllm in the similar way.
maybe need to do:

Add privateuse1 in DeviceConfig
Provide ExecutorRegistry register CustomExecutor, and create instances of CustomWorker and CustomModelRunner in CustomExecutor.
Provide forward register in CustomOp, and dispatch_forward in forward_privateuse1 if use new backend.
Provide AttentionBackend register, and add new branch for new backend.

Additional context
No response

@WoosukKwon cc

您的邮件已收到，我会尽快处理！.

您的邮件已收到，我会尽快处理！.

Closing because:

Inactivity
Many other backends have been added


[IRGen/Runtime] Update Function Metadata

Series of changes to streamline the way function metadata is stored.

@DougGregor could you please take a look at visitFunctionType changes I have so far?

This looks cleaner. Is there a change of behavior here? I notice we no longer treat the argument list as a single tuple when its materializable.

@slavapestov yes, I still need to take a look at getFunctionTypeMetadata @rjmccall suggested to see if I need to make any changes and write some tests which use coercion to verify that everything behaves correctly.

Did some more digging tonight and it looks like when we try to convert function types into SILFunctionType that looses parens in AbstractionPattern::getFunctionInputType(), so even with changes to metadata I made, casts with and without parens still succeed because they point to the same function type...

Needs tests to commit, of course ;)

@DougGregor since my changes to mangling went in, I've updated this changes with test cases to verify that casts are executed correctly now as well as calls to metadata are emitted to the right swift_getFunctionTypeMetadata function. Please take a look.

@swift-ci please clean smoke test

Next up going to be adding labels and missing flags for each parameter metadata entry

Ok, it looks like empty parameters have to be handles specially here as well as case (()) -> Void where it's actually 1 parameter of empty type. Will handle it tomorrow.

@swift-ci please clean smoke test

@swift-ci please clean test

Build failed
Swift Test OS X Platform
Git Sha - baf9f8d5105ae22a56223a01e8ea19db9e0d23ad

Build failed
Swift Test Linux Platform
Git Sha - baf9f8d5105ae22a56223a01e8ea19db9e0d23ad

@swift-ci please clean test

Build failed
Swift Test OS X Platform
Git Sha - a174c5c3bfdeaaf646311d30bad121f3e3ad8cd1

Build failed
Swift Test Linux Platform
Git Sha - a174c5c3bfdeaaf646311d30bad121f3e3ad8cd1