build broken (macOS 10.12.3)

I can't build Lean at the moment, at 6887a99f08b0bc7e5480ba0a1ac1778d319ec326. The error message is:
/Users/scott/bin/lean/src/shell/server.cpp:222:5: error: no member named 'setlocale' in namespace 'std'; did you mean simply 'setlocale'?
    std::setlocale(LC_NUMERIC, "C");
    ^~~~~~~~~~~~~~
    setlocale
/usr/include/locale.h:53:8: note: 'setlocale' declared here
char            *setlocale(int, const char *);
                 ^

This occurs on two different computers:
-- The CXX compiler identification is AppleClang <IP_ADDRESS>00042
-- The C compiler identification is AppleClang <IP_ADDRESS>00042
-- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++
-- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc
-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Lean emacs-mode will be installed at /usr/local/share/emacs/site-lisp/lean
-- Lean library will be installed at /usr/local/lib/lean
-- Found GMP: /opt/local/include (Required is at least version "5.0.5")
-- Using standard malloc.
-- Found PythonInterp: /usr/bin/python (found version "2.7.10")
-- git commit sha1: 6887a99f08b0bc7e5480ba0a1ac1778d319ec326
-- Configuring done
-- Generating done
-- Build files have been written to: /Users/scott/bin/lean/build/release

and
-- The CXX compiler identification is AppleClang <IP_ADDRESS>00181
-- The C compiler identification is AppleClang <IP_ADDRESS>00181
-- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++
-- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc
-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Lean emacs-mode will be installed at /usr/local/share/emacs/site-lisp/lean
-- Lean library will be installed at /usr/local/lib/lean
-- Found GMP: /usr/local/include (Required is at least version "5.0.5")
-- Using standard malloc.
-- Found PythonInterp: /opt/local/bin/python (found version "2.7.13")
-- git commit sha1: 6887a99f08b0bc7e5480ba0a1ac1778d319ec326
-- Configuring done
-- Generating done
-- Build files have been written to: /Users/scott/bin/lean/build/debug

This seems to have been resolved by the parallel compilation merge.


Current layout display on Collection & Profile

Describe the bug
On collection page, the current layout button is not active
To Reproduce
Steps to reproduce the behavior:

Go to any collecion id
See current layout display

Expected behavior
When on collection, activate button with current display
Screenshots
Current

Excepted

Additional context
We need to create a <ToggleLayout /> component for #967

@roiLeo is this still an issue? as I don't see it happening anymore.

@roiLeo is this still an issue? as I don't see it happening anymore.

merged in #1003 but we still need a ToggleLayout component

@roiLeo is this still an issue? as I don't see it happening anymore.

merged in #1003 but we still need a ToggleLayout component

Sure, will pick that up then

closed by @prachi00 if I'm right but can't find the linked PR


[PROPOSAL] IFERROR Exception handling

It would be nice to have a way to handle exceptions (or specify a value to use on exception) in the excel sheet being loaded.
Example: if you are loading a sheet with IFERROR() functions from Google docs the second argument is optional (according to the intellisense from Google). While there are other ways to dive into the spread sheet I'm not seeing a way to discover all the sheets without doing a get() or each() and have been hitting this error.
Luckily this time around I am able to edit the sheet but there will be cases where I can't.

CompleteList!AF4 -> Formula Error: Wrong number of arguments for IFERROR() function: 1 given, 2 expected

 in Cell.php line 293 at PHPExcel_Cell->getCalculatedValue() in ExcelParser.php line 528 at ExcelParser->getCalculatedValue() in ExcelParser.php line 502 at ExcelParser->parseCell('') in ExcelParser.php line 460 at ExcelParser->parseCells() in ExcelParser.php line 378 at ExcelParser->parseRows() in ExcelParser.php line 183 at ExcelParser->parseWorksheet() in ExcelParser.php line 133 at ExcelParser->parseFile(array()) in LaravelExcelReader.php line 1355 at LaravelExcelReader->_parseFile(array()) in LaravelExcelReader.php line 649 at LaravelExcelReader->get() in LaravelExcelReader.php line 710 at LaravelExcelReader->each(object(Closure)) in SongController.php line 50

If you get problem in working of IFERROR while export then you can use
$sheet->setCellValue($cell_name, "=IF(ISERROR($val1*$val2),0,$val1*$val2)");
It works for me :)


Disable charts when merit is disabled

Like the charts described in https://github.com/quintel/etmodel/issues/1922, the following charts only display relevant information when the merit order is enabled. Could you implement the same warning you implemented in a2346ed4452fbffd664e2b23fb41ea95fd68b6c9 for these charts, @grdw ?

Chart 163: Use of excess electricity
Table 164: Storage options

@antw do you know how "Chart 163: Use of excess electricity" is rendered?
I found the app/assets/javascripts/lib/views/vertical_stacked_bar_chart_view.coffee file but when I alert something in the initialize method nothing much happens. Am I using the wrong file or?

I think it's a D3.stacked_bar. Many of the old javascripts/lib/views/ charts were replaced with D3 versions (in javascripts/d3/) some time ago. I think the old ones were kept to retain support for older browsers in which D3 was not supported (IE6).

https://github.com/quintel/etmodel/pull/2003

Closed by #2003.


appaloosa 1.2.0

Fix:

description was breaking when user put quotes and special characters.

Feature:

add support for a new changelog field.

New Pull Request Checklist
Please mark the points which you did / accept.

[x] I read the Step Development Guideline
[ ] I have a test for my Step, which can be run with bitrise run test (in the step's repository)
[ ] I did run bitrise run audit-this-step (in the step's repository - note, if you don't have this workflow in your bitrise.yml, you can copy it from the step template.)
[x] I read and accept the Abandoned Step policy

Please update your step so that it includes a test and audit.
Right now this is not a show stopper, but we might change this in the future for new step versions.

You are right, tests for the win!

And for encouraging / helping contributions for the project/step ;)

Merged, will be available on bitrise.io too in ~10 mins, after the caches expire (if you wouldn't see it after that please try to reload the page a couple of times, to clear the browser's cache too).
Thanks for the contribution! 🚀 ;)


cli: Create schema 'views' if it does not exist

Note that this is not in the code to reduce the required PostgreSQL privileges of the Kingfisher Summarize user. Please add a try/except to log an error that the schema needs to be created as documented.

Doesn't Kingfisher Summarize need the same privileges to create the view_data_ schemas? https://github.com/open-contracting/kingfisher-summarize/blob/master/manage.py#L229-L231

Indeed! I'm confused as to why this was ever a manual step.
Anyway, please update the docs and ci.yml, since this step is no longer necessary with this PR.

I've updated the docs and ci.yml, as suggested.

Thanks. Please avoid force-pushing as it makes it impossible to see new changes. If you are doing it to have a clean git log, then please just use "Squash and merge" after approval.


Provide meaningful config error message by tracking sub configurations

References:

#1497
#1498

Now they look like:
Value "[]" set for config parameter "RuleSet > Rule > active" is not of required type Int.

Add "closes #1516" to description so issue is closed when this is merged?


NoMethodError: undefined method +' for nil:NilClass` on doggy push

What did you do?
I ran the command /home/vagrant/.gem/ruby/2.1.6/bin/doggy push 124448

What did you expect to happen?
I expected Doggy to push 124448.json to data dog

What happened instead?
Instead, what actually happened was it barfed, see stack trace below

Error details
NoMethodError: undefined method `+' for nil:NilClass
  /home/vagrant/.gem/ruby/2.1.6/gems/doggy-0.2.0/lib/doggy/model/monitor.rb:95:in `push'
  /home/vagrant/.gem/ruby/2.1.6/gems/doggy-0.2.0/lib/doggy/model/monitor.rb:16:in `block in upload'
  /home/vagrant/.gem/ruby/2.1.6/gems/doggy-0.2.0/lib/doggy/worker.rb:21:in `call'
  /home/vagrant/.gem/ruby/2.1.6/gems/doggy-0.2.0/lib/doggy/worker.rb:21:in `block (2 levels) in call'
  /home/vagrant/.gem/ruby/2.1.6/gems/thread-0.2.2/lib/thread/pool.rb:67:in `call'
  /home/vagrant/.gem/ruby/2.1.6/gems/thread-0.2.2/lib/thread/pool.rb:67:in `execute'
  /home/vagrant/.gem/ruby/2.1.6/gems/thread-0.2.2/lib/thread/pool.rb:405:in `block (2 levels) in spawn_thread'
  /home/vagrant/.gem/ruby/2.1.6/gems/thread-0.2.2/lib/thread/pool.rb:372:in `loop'
  /home/vagrant/.gem/ruby/2.1.6/gems/thread-0.2.2/lib/thread/pool.rb:372:in `block in spawn_thread'

my changes are already in DD so I'm not fussed about this.

@bai I was running into other problems and some digging revealed I was using the deprecated Shopify version of this repo, which I suspect is to root cause of this issue as well, so I'm closing this.


Kpl testkit

Codecov Report

Merging #160 into master will decrease coverage by 0.64%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master     #160      +/-   ##
==========================================
- Coverage   46.26%   45.61%   -0.65%
==========================================
  Files          24       24
  Lines         281      285       +4
  Branches        2        2
==========================================
  Hits          130      130
- Misses        151      155       +4

Impacted Files
Coverage Δ

...la/fs2/aws/testkit/TestKinesisProducerClient.scala
0% <0%> (ø)
: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 f962a5c...b0fe40f. Read the comment docs.


Nothing happens

Hi,
Nothing happen, I executed the code on Git bash (windows), npm version 6.7, node version 11.8

My conf :
{
"KEYS": {
    "API": "xxx",
    "SECRET": "xxx"
},

"INVESTMENT": {
    "BASE": "BTC",
    "MIN": 0.011,
    "MAX": 0.018,
    "STEP": 0.005
},

"TRADING": {
    "ENABLED": false,
    "EXECUTION_STRATEGY": "parallel",
    "EXECUTION_CAP": 1,
    "PROFIT_THRESHOLD": 0.3,
    "AGE_THRESHOLD": 300,
    "WHITELIST": ["BTC","ETH","BNB","USDT","EOS"]
},

"HUD": {
    "ENABLED": true,
    "ARB_COUNT": 10
},

"LOG": {
    "LEVEL": "info",
    "PRETTY_PRINT": true
},

"DEPTH": {
    "SIZE": 50,
    "INITIALIZATION_INTERVAL": 50
},

"CALCULATION_COOLDOWN": 100

}
There is nothing in the logs in info mode.
Log in debug mode :
["2019-4-14 12:16:15"] DEBUG: Operating System: Windows_NT
["2019-4-14 12:16:15"] DEBUG: Cores Speeds: [3500,3500,3500,3500,3500,3500,3500,3500] MHz
["2019-4-14 12:16:19"] DEBUG: Completed 12/12 (100.0%) calculations in 2 ms
["2019-4-14 12:16:19"] DEBUG: Completed 12/12 (100.0%) calculations in 1 ms
["2019-4-14 12:16:19"] DEBUG: Completed 12/12 (100.0%) calculations in 1 ms
["2019-4-14 12:16:19"] DEBUG: Completed 12/12 (100.0%) calculations in 1 ms
["2019-4-14 12:16:19"] DEBUG: Completed 12/12 (100.0%) calculations in 1 ms
...
Thanks for your help

It's working with PowerShell... strange

Same error on xfce terminal
-Linux Mint 19.1 (Tessa) xfce

The terminal that started the app shouldn't show anything after the stat overview printout (unless you have the HUD turned on).
If you turn the log level to "trace" you will see the calculation time of each cycle in the performance log. The execution log will only show logging when a position is executed
@Memoi I think you have resolved your issue right?
@Davee-io What is your issue more precisely? Are you saying nothing is being logged, or the app is not running?

edit: I see you have opened a new issue. Let's discuss there unless memoi wishes to reopen this


Update faq.md with example on running JuliaCall inside Blender

Would it be okay to copy the example directly in the docs somewhere? Would help with discoverability.

Thanks!


Does not work on NodeJS v12

Minimal Repro: https://github.com/luxalpa/repro-eslint-resolver-bug/tree/main
Using NodeJS version 12.22.10 or 13.14.0 it throws an error:
repro-eslint-resolver-bug/src/main.ts
  1:26  error  Unable to resolve path to module 'fs/promises'  import/no-unresolved

on 14.2 and 16.14.0 it does not report this error.
I minimalized the reproduction to show this specific issue - it's possible that in doing so I might have removed other bits that are important to work correctly. I however tested 100 or so possible configurations without finding a single one that does not throw an error on v12 (while at the same time still being enabled at all).
Not sure if I'm doing something wrong or this is a bug. Not sure how to workaround this issue either :/
I reproduced this on Elementary OS and inside dockers node:12-alpine image.

is-core-module is used by resolve and then used in this project.
See https://github.com/inspect-js/is-core-module/blob/main/core.json#L38
It says the range is [">= 10 && < 10.1", ">= 14"], if you think it's wrong, PR there instead, thanks for reporting.

thanks a lot for that link. I wish this was mentioned on the Readme, as I was just assuming that this tool would simply follow the typings to @types instead of doing this kind of thing. At the very least I feel it could give a better error message (if that is possible). :sweat_smile:

We ignore core module as intended, PR welcome for notice.


MicroProfile Metrics 4.0 Specification Review

Specification issue template
When creating a specification project release review, create an issue in the MicroProfile-WG repository repo with the content defined as follows.

[x] Specification name and version
[x] Add the label Release Review
[x] Naming conventions for artifacts:

[x] Specification PDF in the form of microprofile-project-spec-version.pdf
[x] Specification HTML in the form of microprofile-project-spec-version.html
project is the microprofile specification short project name (config, health, ...)
version is the two digit x.y version of the specification

[x] The Nexus Staging links (orgeclipsemicroprofile-NNNN where NNNN is the staging repository id) (eg, https://oss.sonatype.org/content/repositories/orgeclipsemicroprofile-NNNN/org/eclipse/microprofile/config/) which contain all the binaries and relevant documentation:

[x] Staging Repo
[x] Spec PDF
[x] Spec HTML
[x] Javadoc
[x] API Jar
[x] API TCK Jar REST TCK Jar Optional TCK Jar

[x] A link in the Eclipse downloads sections is still available for specs and apidocs:

[x] https://download.eclipse.org/microprofile/staging/microprofile-metrics-4.0/
[x] An apidocs directory containing the javadoc associated with the API jar.

[x] Summary that a Compatible Implementation is complete, passes the TCK, and that the TCK includes sufficient coverage of the specification.

[x] [Compatible Certification Request] (https://github.com/eclipse/microprofile-metrics/issues/651)

[ ] Release Review

[x] Follow governance process and create/update release record

Component Release Record

[x] Email to PMC (more info here)
[x] Start release review by emailing EMO (more info here)(Track the bug issue created by EMO after the email)
[x] A member of Steering Committee initiates the ballot by sending an email to [microprofile-wg]<EMAIL_ADDRESS>(more info here
[ ] After the voting has ended, email [microprofile-wg]<EMAIL_ADDRESS>with the ballot result (more info here

Similar comment as https://github.com/microprofile/microprofile-wg/issues/101#issuecomment-964539972
The javadoc jar file contains the Apache license and the EFSL license, which are okay. But, it also contains the EF TCK license? That should not be part of the javadoc jar file. I don't think this update is a requirement for a respin, but the TCK license should be removed. Open an issue/pr to clean this up after the release.
On a similar vein, the TCK Javadoc jar file contains the EFSL, which doesn't seem right. I think this EFSL should be removed from the TCK Javadoc jar file. Just include this with the issue/pr you create for the previous comment.
Otherwise, looks good!  Thanks!


could not connect to postgres: error: no PostgreSQL user name specified in startup packet

I'm getting the following error:
could not connect to postgres: error: no PostgreSQL user name specified in startup packet
When I use the following command:
node-pg-migrate up --envPath ./.env.local -m infra/migrations/
My .env.local file:
POSTGRES_USER=local_user
POSTGRES_PASSWORD=local_password
POSTGRES_DB=controle_de_gastos
POSTGRES_HOST=localhost
POSTGRES_PORT=54320
DATABASE_URL=postgres://local_user:local_password@localhost:54320/controle_de_gastos
I tried to connect to my database using DATABASE_URL string and I got success.

Hi @GHCMelo,
I'm not 💯 sure, but I just searched a bit around and e.g. https://hub.docker.com/_/postgres does not show me POSTGRES_HOST and POSTGRES_PORT
Maybe these are not supported environment variables at all (out of the box)?
But with the right dotenv you maybe could achieve this by using expansions like
POSTGRES_USER=local_user
POSTGRES_PASSWORD=local_password
POSTGRES_DB=controle_de_gastos
POSTGRES_HOST=localhost
POSTGRES_PORT=54320
DATABASE_URL=postgres://$POSTGRES_USER:$POSTGRES_PASSWORD@$POSTGRES_HOST:$POSTGRES_PORT/$POSTGRES_DB

I'm not sure this is an issue with node-pg-migrate and as you wrote

I tried to connect to my database using DATABASE_URL string and I got success.

I think this is the way to go
So I will close this issue for now for housekeeping/maintenance


Injecting a custom dispatch pass after iree-linalg-strategy-decompose-pass

Hi, as @benvanik suggested on Discord I've attached a print-after-all dump. The input is taken from one of our pipelines:
module {
  func.func @pipeline(%arg0: tensor<1080x1932x1xi32>) -> (tensor<1080x1920x1xi32>) {
    %cst_10 = arith.constant dense<[[[1],[2],[3],[4],[5],[6],[7],[6],[5],[4],[3],[2],[1]]]> : tensor<1x13x1xi32>
    %c0_i32 = arith.constant 0 : i32
    %21 = tensor.empty() : tensor<1x1080x1920x1xi32>
    %148 = linalg.fill ins(%c0_i32 : i32) outs(%21 : tensor<1x1080x1920x1xi32>) -> tensor<1x1080x1920x1xi32>
    %36 = tensor.expand_shape %arg0 [[0, 1], [2], [3]] : tensor<1080x1932x1xi32> into tensor<1x1080x1932x1xi32>
    %149 = linalg.depthwise_conv_2d_nhwc_hwc {dilations = dense<1> : tensor<2xi64>, strides = dense<1> : tensor<2xi64>} ins(%36, %cst_10 : tensor<1x1080x1932x1xi32>, tensor<1x13x1xi32>) outs(%148 : tensor<1x1080x1920x1xi32>) -> tensor<1x1080x1920x1xi32>
    %39 = tensor.collapse_shape %149 [[0, 1], [2], [3]] : tensor<1x1080x1920x1xi32> into tensor<1080x1920x1xi32>
  return %39 : tensor<1080x1920x1xi32>
  }
}

My pass injecting the custom dispatch logic (Stream dialect) is iree-linalg-conv-to-kernel. It replaces a linalg.depthwise_conv_1d_nwc_wc op with flow.dispatch op calling a kernel. It's ran after iree-linalg-strategy-decompose-pass such that the 2d convolution has been decomposed into a 1d conv on which it operates.
Integrating the pass at this point in the pipeline is leading to a bunch of issues that's making me question if it's feasible. The first error (from iree-convert-to-llvm) isconv2d-examples/1080p_horizontal/1_13_1080_1920_1_hwc.mlir:8:12: error: failed to legalize operation 'func.func' that was explicitly marked illegal. The pass is inserting ops from the func dialect which are illegal in iree-convert-to-llvm. I noticed iree-vm-conversion pass converts func.func -> vm.func but this pass is ran earlier in the pipeline. I tried running this pass after the pass I added which fixes this particular issue, but hit another error and so on.
I'd just like to understand if what I'm trying to do is feasible or if there's a better approach?
I also have a version with HAL dialect I could share.
Let us know if you need anything else, and thanks in advance!
1_13_1080_1920_1_hwc.kernel.print.after.all.txt

I think you're doing something out of order - you're creating flow.dispatch ops inside of a dispatch which isn't supported (maybe one day we can have nested dynamic parallelism, but not today :).
There are two paths for custom device code. One is to swap out ops at the frontend and have those tiled automatically - that'll be useful for hand-authored code or externally-defined microkernels you want to target specifically. The other is to turn ops inside of dispatches into external calls during codegen. I think your LinalgConvToKernelPass is doing the first style (creating dispatches) but doing it at the location where the second style goes (swapping with calls) causing issues. Since you can turn linalg.depthwise_conv_1d_nwc_wc into your call then it should be as simple as replacing that with a func.call (+ the func.func declaration) where you are instead of doing anything with dispatch ops.
This second path will get easier with the work on #12292 to make injecting codegen passes easier. There's an idea for how we can expose microkernels to the frontend to make the first path possible to fuse/tile/distribute microkernels and that'd make it easier to define custom calls all the way from the tosa/linalg input level.

Thanks for clarifying. It sounds like replacing 2d convs in the frontend is the extent of this pass then. I'll have a look at calling these kernels as externals calls instead for 1d ops. I guess this is a standard MLIR mechanism and not special to IREE like custom dispatch? If you could point me to any examples I would appreciate that.
Thanks for your help!

Doing it in the frontend isn't yet wired up - that'll require #12300 - but doing it where you're doing it now should work ala custom_dispatch. So instead of turning your conv op into a dispatch you just turn it into a func.call and declare the func.func just like custom_dispatch does. I'd recommend doing that for now until the other ways get more support.

Sorry by frontend I meant the similar pass I have that operates on 2d convs and is run really early in the pipeline alongside the InputConversion passes (briefly mentioned it on Discord). That does work.

Does it? We may be talking about different things :) If you have something working then that's great!

@c-rhodes Is this issue still open?

It can be closed now, thanks all!


Evaluate custom predicates in the context of the validator

This way we could create a set of custom predicates that make use of injected variables, such as:
require 'dry-validation'

User = Struct.new(:name, :email)

class UserRepository
  USERS = []

  def create(attributes)
    USERS << User.new(*attributes.values_at(:name, :email))
  end

  def find_by_email
    USERS.find { |email| user.email == email }
  end
end

module CustomPredicates
  include Dry::Logic::Predicates

  predicate(:unique?) do |value|
    uniqueness_finder.call(value).nil?
  end
end

UserSchema = Dry::Validation.JSON do
  configure do
    option :uniqueness_finder

    config.predicates = CustomPredicates

    def self.messages
      super.merge(en: { errors: { unique?: 'must be unique' } })
    end
  end

  required(:name).required
  required(:email).required(:unique?)
end

user_repo = UserRepository.new
user_validator = UserSchema.with(uniqueness_finder: user_repo.method(:find_by_email))
user_repo.create(name: 'John', email<EMAIL_ADDRESS>
user_validator.call(
  name: 'John',
  email<EMAIL_ADDRESS>)
# Failure
user_validator.call(
  name: 'Jill',
  email<EMAIL_ADDRESS>)
# Success

/cc @solnic, @timriley @jodosha

@AMHOL This could be a great feature.
I'm thinking about CSRF protection too. When the :_csrf_token is sent within the body of a request, a framework needs to verify the input value matches with the one stored in the session.
As now, it would be an extra step after the validations. But with this feature, CSRF check can be integrated within data validations, which makes sense.
👍

You can achieve that w/o the complexity that comes with changing exec context of predicates. Predicate interface is very simple, you can provide your own objects as predicates and register them under predicate registry that you can share across schemas. We can easily marry that with dry-container API so that custom predicate objects can be provided through IoC.
Defo 👎 for executing predicates in the context of schema. External predicates should have their own exec context. Besides, you can always delegate predicate application to an external predicate and pass in a dependency as a predicate argument.

Has anyone come up with a solution to this problem?


Documentation generated from .proto file doesn't specify if something is an array/repeated

For instance, from https://www.envoyproxy.io/docs/envoy/latest/api-v2/api/v2/cds.proto#cluster:
hosts
(core.Address) If the service discovery type is STATIC, STRICT_DNS or LOGICAL_DNS, then hosts is required.

It would be useful if the type said repeated core.Address, so similar.

I would like to take up this. @ggreenway Could please suggest where to start? I think need to modify tools/protodoc/protodoc.py

That would be great if you could work on this. I don't know where the docs are generated from, so I can't offer much guidance. @htuch did you write this originally?

Yes, protodoc.py, thanks for taking this on @mk46.


GPU storage fixes

Description
This PR resolves two issues in the GPU storages uncovered during FV3 dynamical core verification.

Is this still in progress? If the test you added covers the case you discovered, this is fine to merge for me. (I can't merge now, since it is flagged as draft)

No, this is ready. The added test does capture the error. I have removed the draft status. Thank you!


add interfaces for individual fund by using data from xueqiu

add interfaces for individual fund by using data from xueqiu:

Fund basic info
Fund achievement
Fund data analysis
Fund profit probability
Fund trading rules
Fund asset positions

Thanks for your PR


fix: "fatal: Could not parse object"

[x] I have pointed s-r-p to a latest commit in the cardano-addresses repo.

Comments
Not sure if this update doesn't break anything, but at least it fixes the broken reference.
Issue Number
None

bors merge

bors r+


v0.27.0 ROADMAP

The purpose of this roadmap is to let anyone know about the different steps in the Meilisearch release.
Draft phase (weeks 1-4)
Start: 14/02/2022
End: 14/03/2022

[x] Planification of the next release content (features, improvements, bug fixes). Meeting with the PM & and the core manager to discuss and agree on what we are going to put in the next release.
[x] Presentation of the next release content to the core team. Discussions with the team that can lead to some corrections.
[x] Discovery phase (most of the time, not every time, depending on the feature). The PM writes specifications, and devs prototype solutions.
[x] At the middle/end of the Draft phase, the PM and the core manager review together and agree a firm version of the next release plan. Nothing is strongly definitive, still needs to be validated by Guillaume.
[x] The core manager shares the firm version of the next release plan on #ms-release (internal Slack). It’s for information at this stage, no team can start working since the specs are not fully available yet.
[x] The PM provides the firm version of the specs, which means the implementation phase can begin.
[x] The core manager opens issues (including an issue for the version update in the Cargo.toml files) to add them to the Milestones. Issues related to bugs could also be added to the Milestones.

Implementation phase (weeks 5-8)
Start: 14/03/2022
End: 11/04/2022

[x] The core manager posts a summary of the release dates on #ms-releases (internal  Slack), links the milestones, and gives an overview of the main features. This could interest other teams, especially DevRel.
[x] At the beginning of the Implementation Phase, sync meeting with each manager of the open-source teams about the current implemented release. It’s an opportunity to remind where we need their review regarding the specs.
[x] Core team implements the planned content of the release according to the specifications. The code changes are merged into the main branch.
[x] Docs team organizes their preparation: identify the effect of new changes on the documentation, discussion phase and planning.
[x] According to the feedback we receive from the devs, changes may be made to feature specs
[x] At the end of the Implementation Phase, the core manager writes the changelog for the release
[x] Docs team reviews the changelogs.
[x] Integration team opens a central issue on integration-guides gathering all the release changes that will impact the integration team and how they will handle them
[x] Integration team opens draft branches in every repository to make the integrations up-to-date with the new version of Meilisearch.
[x] At the end of the Implementation Phase, all the issues related to the Milestone are solved, meaning every implementation has been merged into main. If something differs from the original plan, the core manager should inform the other teams on #ms-releases (internal Slack).

Pre-release phase (weeks 9-12)
Start: 11/04/2022
End: 09/05/2022

[x] Core team release the first RC (release candidate) using the prepared changelogs.
[x] At the beginning of the Pre-release Phase, sync meeting with each manager of the open-source teams about the coming release. It’s an opportunity to plan and identify the parts where sync will be needed between the different teams during the Pre-release Phase.
[x] Integrations team updates the SDKs and their integrations according to the new release.
[x] Docs team updates the documentation to reflect the changes of the new release.
[x] Optional - In some situation, the mini-dashboard also needs an update. This update might involve the integration team to release beta version of meilisearch-js and/or instant-meilisearch.
[x] According to feedback and bug reports from the integrations and the docs teams, the core team modify the code and fix bugs as soon as possible. Other RCs are released if necessary.
[x]  DevRel team write a blog post “What’s new in v0.X.Y?”.
[x] The core manager, the PM, and the docs team review the blog post.
[ ] Integration team confirms the latest RC (so at the end of the Pre-release Phase) works with their DevOps tools

Release phase (week 13)
Release date: 09/05/2022

[x] Core team releases the official version and lets the other teams know when the binary and the Docker images are available on #ms-releases (internal Slack).
[x] New documentation deployment by the docs team
[x] Release of all the updated integrations by the integration team
[x] DevRel team takes care of external communications (blog, socials, etc) but might want for the documentation and the assets of the release to be ready (including Docker image)
[x] Bring changes from stable branch of Meilisearch into the main branch
[x] Lock the discussions in the product repo.
[x] Close this issue
[x] Close the release Milestones

Dooooooone well done to everyone @meilisearch/core-team @meilisearch/docs-team @meilisearch/integration-team and @meilisearch/product-team ❤


Update #glossary_validity: Replace validity time

Fixes #2911

In English, the glossary now shows 90 days instead of 180 days of validity for certificates of recovery
Replace outdated link with link to German Infection Protection Act
Fix missing "<" in glossary "digital_certificate"

Good morning @Ein-Tim and @MikeMcC399 Thanks for reviewing and commenting!


Fix server scripts runtime error due to mixed import and require usage

The error arose when you run npm run build which produces a fresh bin/server.js chunk containing mixed import and require syntax and then, run npm run server:dev which runs the server.js produced from last command.
Refer this.

error arose when you run npm run build

you meant the webpack or watch command ?

error arose when you run npm run build

you meant the webpack or watch command ?

Oh yeah! i forgot, you updated the build to watch. And, yes, I meant the watch command

Okay, let me look into it. As far as this is concerned this should not happen as those are webpack output files. I don't know why it's happening. Maybe because of the target: node  in the server config.

Still dont know why its coming but merging this as this is a valid fix for this issue


Possible to use with Extended Image?

It would be amazing if this could be used to mock tests with Extended Image! Is this a possibility?

It should be possible if the mentioned package uses Image.network() for getting the image. Although it might have a custom logic for fetching the image, because it provides many customisable options, like caching. You could definitely try it out and report back if it works 😉


[Discussion] 2D: Car steering

Discussion for http://godotrecipes.com/2d/car_steering/

Thank you for the great tutorial that was extremely helpful.  While adding some extra features I found it helpful to know what (if any) the maximum speed of the vehicle would be ahead of time.  I thought I would share my slapped together and not particularly rigorous function in case anyone else found it useful:
var max_speed: float

func _ready() -> void:
	max_speed = _calculate_max_speed()

func _calculate_max_speed() -> float:
	if drag >= 0 and friction >= 0:
		return -1.0
	elif drag >= 0 and friction < 0:
		return engine_power / friction
	elif drag < 0 and friction >= 0:
		return sqrt(engine_power / drag)

	var discriminant: float = (friction * friction) - (4 * drag * engine_power)
	return (-friction - sqrt(discriminant)) / (2 * drag) if discriminant >= 0 else -1.0

I enforce engine power, friction, and drag values through export hints, so the function doesn't do much checking to compensate for it.  If drag or friction are not negative then I just return -1 to indicate that there isn't a max speed, although I suppose you could also return the maximum float as a value instead since that is what it will effectively be.
If only drag or friction are relevant than I solve the simple algebraic equation and return that.  If both are relevant (as is usual) then I solve the quadratic that results from the sum of both the drag and friction functions at the given engine power and return the relevant (positive) real result.  There isn't whole lot of error checking going on here but as long as you keep negative values for drag and friction as well as a positive value for engine power the max speed you get should be a good result.

Thank you for this great tutorial.


Solarized-dark doesnt display properly

Hi all! I'm new to doom emacs and emacs at all. But when i tried to change theme of doom emacs to solarized-dark via doom-themes i noticed that it doesn't display properly. Also, im using fork of st terminal, but i experienced same problem with alacritty too.
System Information

Emacs version: 27.1
Emacs Distro: Doom Emacs
Operating System: Gentoo
Installed commit of doom-themes: idk where to view it

I found solution here, so sorry for excess issue


Add old simplified Au ruletset

Uses FISAC1718 as base with slight modifications shown in
https://github.com/svbeon/RopeScore/blob/c7d59a6e74c54c21f7f959085630ae686a7b96cf/app/configs/au.js#L181-L219

Superseeded by #97


Spam of "errors"

I updated cogs of carmita to 1.0.22, everything was fine until I entered Twilight, it seems that as I load and advance through the mines in Twilight, a lot of spam appears.

[Worker-Main-15/ERROR] [minecraft/Util]: Detected setBlock in a far chunk [4, 9], pos: MutableBlockPos{x=66, y=-14, z=156}, status: minecraft:features , currently generating: ResourceKey[minecraft:worldgen/placed_feature / cogsofcarminite:striated_andesite_twilight_forest]

latest.log
I think this also causes fps drops for me.

Fixed in 0411df762553ffba2fd37ffddb6ad300cf03fee2
file is being uploaded


Change delete file modal confirmation process

From user testing:
Currently, to delete a file, you must confirm the entire file name:

This is a little bit painful for some users, because the file name can get pretty long.
Instead, we should change this modal so that we require the project name for confirmation.

Good First Issue: This issue is good for first time contributors. If you've already contributed to Warehouse, please work on another issue without this label instead. If there is not a corresponding pull request for this issue, it is up for grabs. For directions for getting set up, see our Getting Started Guide. If you are working on this issue and have questions, please feel free to ask them here, #pypa-dev on Freenode, or the pypa-dev mailing list.

@aalmazan could I ask for you to help with this?

@brainwane Sure, however, I can't seem to find a good way to test uploading packages. Are there some docs you can point me to? Or at least a high-level of how I can create a test package?
Would I need to follow the packaging guide while having pypi.org point to localhost?

@aalmazan As a first step, if you haven't uploaded a package to PyPI before, I suggest you follow the packaging guide and then upload your package to Test PyPI, just to see how the whole process works. Here's a toy project I have set up reasonably well in case you want to clone and use that (you'll have to modify the package name in setup.py so Test PyPI will let you upload it).
I am realizing now that our Getting Started guide lacks information on uploading packages locally. @waseem18 and @lgh2 I think you've dealt with this -- how did you manage it? Whatever you advise, we should write it up and add it to the docs!

@aalmazan Sorry for this oversight!

@aalmazan What you can do is - Find a user from local database who has one or more packages then reset the user's password and login with the same user. You can use those packages to reproduce any issues.

Hi everyone, we actually already have documentation for how to login locally here: https://warehouse.readthedocs.io/development/getting-started/#logging-in-to-warehouse

@brainwane Our guide already has some details about uploading packages locally, but it's not in the "Getting Started" section: https://warehouse.pypa.io/development/reviewing-patches/?highlight=twine#testing-with-twine

I just spoke with Nicole and we agreed that this can wait till after we shut down legacy PyPI.

@aalmazan do you have what you need to proceed on this? Please do go ahead and work on it -- if we can merge your fix before shutting down legacy, all the better!

Below is a screenshot of what I currently have for the modal copy. Let me know if this should change. I think with how the confirm_modal macro is now, I'm not able to add more detail about what's deleted unless I add in some sort of extra_details=[html_strings] to the macro? Maybe we can add in the filename in the modal title if we're fine with having the title wrap to two lines? (i.e. "Delete File (filename.tar.gz) From pypusu?")

Additionally, there seems to be a bug with the delete modal not clearing the delete button's previous state on close (see gif below). I don't think I see this reported in issues either -- has it been reported yet? I can fix the bug as well as I work on this issue.

Hi @aalmazan - thanks for your work on this!  I think just "delete file from " for the title is fine (we had feedback during user tests that the file name itself could be really really long).
I agree that it would be nice to make another argument in the macro - but maybe for an additional line of information in the modal.  For example:

This would allow us to be more flexible with the main macro content in the future.  What do you think?

Thanks for finding the button bug as well, I'll open a new issue for this :)


onChange Event not fired for boolean and null property value

Hi,
I've a  problem with json object with  boolean property.
If i write my json through "Properties" button all works fine.
If i write my json through "JSON" button the onChange event is not fired if my object have a boolean or null property.
The result is that the layout is updated while my data isn't updated.
( I've used version 0.2.1 but i try to reproduce the same case also using your demo page with the latest version of plugin )

Can you confirm that this works in the original jdorn/json-editor project?

Sorry, the problem is in the original  jdorn/json-editor project.


Preview?

Maybe add a Preview, I won't download something If idk how it looks

You can preview when you click on the latest release!


catch2: 2.13.3 -> 2.13.4

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/catchorg/Catch2/releases.
meta.description for catch2 is: "A multi-paradigm automated test framework for C++ and Objective-C (and, maybe, C)"
meta.homepage for catch2 is: "http://catch-lib.net"
meta.changelog for catch2 is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

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

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

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

found 2.13.4 with grep in /nix/store/ivjgq18rbx8acbmv040mmq9jidh8sqsy-catch2-2.13.4

directory tree listing: https://gist.github.com/de66bfb21fda002b9f59a261c3a45779

du listing: https://gist.github.com/407de7354474e3ba1811223a14388612

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

99 total rebuild path(s)

33 package rebuild(s)

28 x86_64-linux rebuild(s)
20 i686-linux rebuild(s)
20 x86_64-darwin rebuild(s)
31 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
catch2
cloudcompare
d-seams
fcppt
giada
grip-search
imgbrd-grabber
irods
irods-icommands
libjson-rpc-cpp
nrfutil
nuspell
pc-ble-driver
pdal
python37Packages.pc-ble-driver-py
python37Packages.qiskit
python37Packages.qiskit-aer
python37Packages.qiskit-aqua
python37Packages.qiskit-ignis
python37Packages.tiledb
python38Packages.pc-ble-driver-py
python38Packages.qiskit
python38Packages.qiskit-aer
python38Packages.qiskit-aqua
python38Packages.qiskit-ignis
python38Packages.tiledb
python39Packages.qiskit
python39Packages.qiskit-aer
python39Packages.qiskit-aqua
python39Packages.qiskit-ignis
python39Packages.tiledb
tiledb
yuzu

Instructions to test this update (click to expand)

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

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

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

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

6 packages failed to build:

python37Packages.qiskit
python37Packages.qiskit-aqua
python37Packages.qiskit-ignis
python38Packages.qiskit
python38Packages.qiskit-aqua
python38Packages.qiskit-ignis

22 packages built:

catch2
cloudcompare
d-seams
fcppt
giada
grip-search
imgbrd-grabber
irods
irods-icommands
libjson-rpc-cpp (libjson_rpc_cpp)
nrfutil
nuspell
pc-ble-driver
pdal
python37Packages.pc-ble-driver-py
python37Packages.qiskit-aer
python37Packages.tiledb
python38Packages.pc-ble-driver-py
python38Packages.qiskit-aer
python38Packages.tiledb
tiledb
yuzu

Maintainer pings
cc @edwtjo @knedlsepp for testing.

Build failures are already failing on target branch.

Build failures are already failing on target branch.


Garbled characters are displayed when setting cookie attribute

Description:

Fail to set cookie attributes because the results are garbled.
Repro steps:
...
attributre := routev3.RouteAction_HashPolicy_CookieAttribute{
	Name:  "test",
	Value: "test",
}
...

use routev3.RouteAction_HashPolicy_CookieAttribute

@MregXN  Hi I think it will be great if you can provide more details and context: like detailed repro steps, repro environement configuration example etc

@MregXN Hi I think it will be great if you can provide more details and context: like detailed repro steps, repro environement configuration example etc

golang version :  go1.22.0 linux/amd64
go-control-plane server version : v3
The backend ground is I'm trying to configure the cookie hashpolicy feature of Envoy. The Name , Path and TTL are all displayed normally, but my custom attribute is garbled. Code snippet is as follows：
...
	if httpRoute.LoadBalancer.ConsistentHash.Cookie != nil {
		hashPolicy := &routev3.RouteAction_HashPolicy{
			PolicySpecifier: &routev3.RouteAction_HashPolicy_Cookie_{
				Cookie: &routev3.RouteAction_HashPolicy_Cookie{
					Name: httpRoute.LoadBalancer.ConsistentHash.Cookie.Name,
				},
			},
		}

		if httpRoute.LoadBalancer.ConsistentHash.Cookie.Path != "" {
			hashPolicy.PolicySpecifier.(*routev3.RouteAction_HashPolicy_Cookie_).Cookie.Path = httpRoute.LoadBalancer.ConsistentHash.Cookie.Path
		}

		if httpRoute.LoadBalancer.ConsistentHash.Cookie.TTL != nil {
			hashPolicy.PolicySpecifier.(*routev3.RouteAction_HashPolicy_Cookie_).Cookie.Ttl = durationpb.New(httpRoute.LoadBalancer.ConsistentHash.Cookie.TTL.Duration)
		}

		if len(httpRoute.LoadBalancer.ConsistentHash.Cookie.Attributes) > 0 {
			var attributes []*routev3.RouteAction_HashPolicy_CookieAttribute
			for k, v := range httpRoute.LoadBalancer.ConsistentHash.Cookie.Attributes {
				attribute := routev3.RouteAction_HashPolicy_CookieAttribute{
					Name:  k,
					Value: v,
				}
				attributes = append(attributes, &attribute)
			}
			hashPolicy.PolicySpecifier.(*routev3.RouteAction_HashPolicy_Cookie_).Cookie.Attributes = attributes
		}

		return []*routev3.RouteAction_HashPolicy{hashPolicy}
...

I was able to reproduce this. Please assign this to me. I will try to fix this

@MregXN @ramaraochavali in the future please be careful about opening issues like this and instead email envoy-security@ first. This is an undefined memory access leak which exposes random memory back to the clients, which is very serious. The only reason we aren't considering this a zero day is that the only code that uses this is an extension that is marked alpha. Thanks!


Shortcut key is not correct

Alt+F does not do a thing on Edge

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 4be833d4-f235-4029-258d-6ef2387f4189
Version Independent ID: 09525733-35da-0bf0-522b-d3f9decb367a
Content: Microsoft Edge language support
Content Source: edgeenterprise/microsoft-edge-supported-languages.md
Product: microsoft-edge
GitHub Login: @dan-wesley
Microsoft Alias: kvice

Clean up of old issues.  Appears the question has been previously answered.  Closing.
If you have general questions regarding Microsoft Edge please reach out on the Microsoft Edge Tech Community or for Enterprise specific questions please visit the Enterprise section of the Tech Community. Thanks!


Modules: Modules Field in RPC

As a Run App user, I would like to know if what modules I have connected, and in which deck slots.
Acceptance Criteria

Add modules field to RPC session

@btmorr given that there is additional RPC work to be done (on top of the presence of a Module class in the API) before RPC is going to start reporting modules in sessions, I don't think it's appropriate to close this ticket


[!] TypeError: The "path" argument must be of type string. Received an instance of RegExp

Hi Jelte,
I'm learning Mendix and I'm following the Mendix learning path 'Build a Pluggable Widget'. For some reason the widget is not getting built correctly by MX Generator. I tried reinstalling Node.js, Yeoman and the MX Generator, closed my Studio Pro to see whether that was it, looked for the error on Google but couldn't find it.
Do you know what might be the problem here?
Stack trace:
Running MX Widgets Tools script lint:fix...
src\components\HelloWorldSample.tsx 276ms
src\TestWidget.editorPreview.tsx 18ms
src\TestWidget.tsx 14ms

<EMAIL_ADDRESS>build C:\Users\Gebruiker\documents\mendix\Build_a_pluggable_widget-main\CustomWidgets\testWidget
pluggable-widgets-tools build:web

Running MX Widgets Tools script build:web...
Project Path: C:\Users\Gebruiker\Documents\Mendix\Build_a_pluggable_widget-main/
[!] TypeError: The "path" argument must be of type string. Received an instance of RegExp
TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received an instance of RegExp
at validateString (internal/validators.js:124:11)
at Object.resolve (path.js:162:9)
at C:\Users\Gebruiker\Documents\Mendix\Build_a_pluggable_widget-main\CustomWidgets\testWidget\node_modules\rollup-plugin-sass\node_modules\rollup-pluginutils\dist\pluginutils.cjs.js:183:68
at Array.map ()
at Object.createFilter (C:\Users\Gebruiker\Documents\Mendix\Build_a_pluggable_widget-main\CustomWidgets\testWidget\node_modules\rollup-plugin-sass\node_modules\rollup-pluginutils\dist\pluginutils.cjs.js:183:35)
at Object.plugin [as default] (C:\Users\Gebruiker\Documents\Mendix\Build_a_pluggable_widget-main\CustomWidgets\testWidget\node_modules\rollup-plugin-sass\src\index.ts:134:14)
at C:\Users\Gebruiker\Documents\Mendix\Build_a_pluggable_widget-main\CustomWidgets\testWidget\node_modules@mendix\pluggable-widgets-tools\configs\rollup.config.js:298:45
at Array.forEach ()
at rollup_config (C:\Users\Gebruiker\Documents\Mendix\Build_a_pluggable_widget-main\CustomWidgets\testWidget\node_modules@mendix\pluggable-widgets-tools\configs\rollup.config.js:286:23)
at getConfigList (C:\Users\Gebruiker\Documents\Mendix\Build_a_pluggable_widget-main\CustomWidgets\testWidget\node_modules\rollup\dist\shared\loadConfigFile.js:565:11)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>build: pluggable-widgets-tools build:web
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!      C:\Users\Gebruiker\AppData\Roaming\npm-cache_logs\2021-08-24T10_15_58_070Z-debug.log
Widget successfully built!! Please open Mendix Studio Pro and start playing with your new widget.

I managed to solve the issue. I did not use the right folders for my commands:
Being in the main folder from the Windows Powershell I need to run:
C:\Users\Gebruiker\Documents\Mendix\Build_a_pluggable_widget-main> yo @mendix/widget x
(in which x will be the name of the folder with all dependencies of the generated widget)
And then in the questions from the MX Generator the project path also needs to be the main folder:
Mendix project path: C:\Users\Gebruiker\Documents\Mendix\Build_a_pluggable_widget-main
With this configuration I was able to get custom widgets in the Widget folder.


[Bug] Automated speed tests are reporting slower speeds than manual speed tests

General

[X] I have updated to the latest version of MySpeed.
[X] My bug has not been reported yet.

The Bug
When running the tests manually using the "start speedtest" button top right, I am getting expected speeds from my ISP. But when an automated test runs the speeds are far lower.

In the provided image, the test at the top is the automated hourly test, and the two below are ones i have ran manually. My instance is running in a proxmox LXC with 1 core and 512mb of ram
What device are you using to access the page?
In the browser
Which operating system is your MySpeed instance running on?
Linux

+1


Number type does not handle really big numbers

I noticed this while sniffing DropBox LAN sync packets which were using a 39-digit "host_int" number. With the existing serde_json Number storage, only ~16 digits of precision are preserved as it saves it as a floating point. I wasn't able to try num_bigint::BigUint as the crates.io version hasn't upgraded to serde 1.0 yet (it looks like the github version may have).
To see the packets themselves, set up DropBox's LAN sync feature and then do:
nc -lu 17500
See also:
https://nmap.org/nsedoc/scripts/broadcast-dropbox-listener.html

Please try with the arbitrary_precision feature enabled.
[dependencies]
serde_json = { version = "1.0", features = ["arbitrary_precision"] }

I believe the arbitrary_precision feature addresses this.
#[macro_use]
extern crate serde_derive;

extern crate serde;
extern crate serde_json;

use serde_json::Number;

#[derive(Deserialize)]
struct LanSyncPacket {
    host_int: Number,
}

fn main() {
    let j = r#" {"host_int":<PHONE_NUMBER>12345678901234567890123456789} "#;
    let packet = serde_json::from_str::<LanSyncPacket>(j).unwrap();
    println!("{}", packet.host_int);
}

123456789012345678901234567890123456789


Enhancements for replies hiding feature

The changes let users configure the plugin to always show all replies by setting maxRepliesVisible to a negative value or hide all replies by setting it to 0.

Currently setting maxRepliesVisible to a negative value might result in an unexpected behaviour, and there's no dedicated setting to always show all replies, so hiding feature is disabled. There's also no option to hide all replies, @jjtykkyl


French words list could be better

I'm french speaker.
French words list aren't good. Many accents are not respected :
We can read :

"a^cre" instead of "âcre"
"a`-propos" instead of "à-propos"
"abandonne'" instead of "abandonné"
"paranoi"a" instead of "paranoïa"
some words are not words but some abbreviation like "al." (?) "ac."  I think those words could not be included.
And every word is written 2 times.

I submit a corrected list with accents, without words with ".", and without duplications.
The old list count : 276506 words (which contains all words in double)
The new list contains : 138253 words.
proper-french-list.tar.gz

Hi! Apologies for the delay in getting to this.
Which word list are you seeing the issue in? I ran some tests with fr-freelang and fr-freelang-bernard-vivier and see correct accenting, and only ~23k entries.
I'm more than happy to add another French list if you can confirm where it originated to ensure the licences are OK

I took the french list in your README.rst of this repository

French: Cleaned version of this list. Public domain.
https://packetstormsecurity.com/files/download/32007/french.gz
You mention that is a Public Domain, but there is no licence in the .gz file
But this file isn't correctly written.
I correct it and publish on this post.

Please incorporate this proposed dictionnary because
fr-freelang and fr-freelang-bernard-vivier
have injourious words !
like "salope" => means bitch
or "viol" => means rape

Thank you for your contribution - these changes have been made in v1.17.4 or later

Hello,
The wordlist provided by @webafrancois is in utf8, which isn't correctly read by KeepassXC on windows.
Here is a cp1252 version which  correctly shows accentuated letters.
cp1252_french.txt


Implement net.bytebuddy.asm.Advice.ExceptionHandler to log exceptions in agent log

Currently, we are using net.bytebuddy.asm.Advice.ExceptionHandler.Default#PRINTING which means the exceptions may not be in the agent logs. We should create a custom net.bytebuddy.asm.Advice.ExceptionHandler which logs the exception with the agent logger.
If possible make that generic enough so that we can contribute that to Byte Buddy

Not a bad idea, actually. One could write the exception to a free offset and make it available like that. This way, all the other annotations that work in (at)Enter advice would also work.
I have not looked into how difficult this would be to implement but it would certainly be possible.


Unable to review terminal output with NVDA in focus mode / navigation mode doesn't work

Type: Bug
STR:

Start NVDA
Open a terminal with control+`
Run a few commands to generate output.
Try to navigate the output with control+up and down.

I hear list item, list item, list item. To actually read the text of each item, I have to hit NVDA space, read, then hit NVDA space again.
I don't remember exactly when, I think in the 1.6x days, this used to work, but it hasn't for quite a while now.
VS Code version: Code 1.74.3 (97dec172d3256f8ca4bfb2143f3f76b503ca0534, 2023-01-09T16:59:02.252Z)
OS version: Windows_NT x64 10.0.22000
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
AMD Ryzen 7 5800H with Radeon Graphics          (16 x 3194)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
15.41GB (9.47GB free)

Process Argv
--crash-reporter-id 5211d001-3acc-473c-a716-32f72b6395d5

Screen Reader
no

VM
0%

Extensions (9)

Extension
Author (truncated)
Version

copilot
Git
1.70.8099

isort
ms-
2022.8.0

python
ms-
2022.20.2

vscode-pylance
ms-
2023.1.40

jupyter
ms-
2022.11.1003412109

jupyter-keymap
ms-
1.0.0

jupyter-renderers
ms-
1.0.14

vscode-jupyter-cell-tags
ms-
0.1.6

vscode-jupyter-slideshow
ms-
0.1.5

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
vscorecescf:30445987
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vsclangdc:30486549
c4g48928:30535728
dsvsc012:30540252
azure-dev_surveyone:30548225
pyindex848:30577860
nodejswelcome1cf:30587006
2e4cg342:30602488
f6dab269:30613381
2i9eh265:30646982
vscup:30628656

We can track navigation mode, what you're describing, not working in this issue. We're aware of it and hoping that our new terminal accessibility buffer offers a better solution over time so we can remove this all together.

related #170988


python310Packages.pulumi-aws: 5.13.0 -> 5.14.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.pulumi-aws is: "Pulumi python amazon web services provider"
meta.homepage for python310Packages.pulumi-aws is: "https://github.com/pulumi/pulumi-aws"
meta.changelog for python310Packages.pulumi-aws is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 5.14.0 with grep in /nix/store/n7d0s03q8b1xpzz3m3phm2wcfm196zbi-python3.10-pulumi-aws-5.14.0
found 5.14.0 in filename of file in /nix/store/n7d0s03q8b1xpzz3m3phm2wcfm196zbi-python3.10-pulumi-aws-5.14.0

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
python310Packages.pulumi-aws
python39Packages.pulumi-aws

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/n7d0s03q8b1xpzz3m3phm2wcfm196zbi-python3.10-pulumi-aws-5.14.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/n7d0s03q8b1xpzz3m3phm2wcfm196zbi-python3.10-pulumi-aws-5.14.0
ls -la /nix/store/n7d0s03q8b1xpzz3m3phm2wcfm196zbi-python3.10-pulumi-aws-5.14.0/bin

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

2 packages built:

python310Packages.pulumi-aws
python39Packages.pulumi-aws

Maintainer pings
cc @costrouc for testing.

Result of nixpkgs-review pr 191763 run on x86_64-linux 1

2 packages built:

python310Packages.pulumi-aws
python39Packages.pulumi-aws


Fieldset along with the Select all checkbox.

I would like to implement the functionality shown in the screenshot below, which includes a fieldset along with a 'Select All' checkbox. Is this possible? If so, could you provide me with the schema for it?

well, its not in the schema.. its in the form.
{
  "schema": {
    "menu": {
      "type": "array",
      "title": "Options",
      "items": {
        "type": "string",
        "title": "Option",
        "enum": [
          "starter",
          "maincourse",
          "cheese",
          "dessert"
        ]
      }
    }
  },
  "form": [
    {
     "title":"<input type=\"checkbox\" onchange=\"handlechange()\"> Options ( check all)",
      "type": "fieldset",
      "expandable": false,
      "order": 0,
      "items": [
    {
      "key": "menu",
      "notitle":true,
      "type": "checkboxes",
      "htmlClass":"foo",
      "titleMap": {
        "starter": "Starter would be great",
        "maincourse": "No way I'll skip the main course",
        "cheese": "Cheddar rules!",
        "dessert": "Thumbs up for a dessert"
      }
    }
  ]
    }
    ]
}

then the handleChange function might look like this  (untested)
function handlechange(evt, node){
var all_checked=$(evt.target).checked  // get 'all' checkbox state.. should be true/false
// use jquery to get all the checkboxes under the 'foo' class
// loop thru them
$('.foo .checkbox').forEach((box)=>{
box.checked = all_checked
})
}

Hey @sdetweil , Using your code and the generated form appears as shown in the screenshot below. However, I would like the 'select all' checkbox to be positioned in front of the options to select all fields. By the way, I am using ajsf  in my project.

I don't know what you mean asjf.
this is the jsonform library
I see there is a different library for asjf  angular
I do not know on the positioning. my literal coding places the checkbook in front
there IS a problem.  we defined this as a string with a single choice.  so checking all has no place to store it.

I see you posted to the asjf github repo too
https://github.com/hamzahamidi/ajsf

closing, wrong project reference


:recycle: Chore: Refactor test

Description
Concise description of proposed changes
Testing
Explain the quality checks that have been done on the code changes
Additional Information

[ ] I read the contributing docs (if this is your first contribution)

Your ENS/address:

#1023  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @roninjin10 and the rest of your teammates on  Graphite


Split DM cases to speed up CI

replay: https://ci2.pingcap.net/job/dm_ghpr_integration_test/8380/

PTAL @purelind

replay https://ci2.pingcap.net/job/dm_ghpr_integration_test/8568/


Order by Random in our query

ORDER BY should also include where user can get his data in random order rather than using ASC or DESC order.
It would be a nice feature for OrientDB for having this kind of feature.
Thanks

agree that this would be a really nice feature for things like randomized experiments (random allocation) or random sampling to create a subset

agree that this would be a nice feature. I currently have a very large healthcare database and to get a random sample i have to do it through a python query rather than directly from the query. this functionality would definitely solve my problem

I was hoping this functionality would become a priority soon.  Really needed this for a problema with randomization.

Yup, would be tremendously helpful. Right now I am using an R script to do the same thing after the query.

seems like a lot of people like this feature and so I will join the group. I use orientdb to store large healthcare databases and sampling in the query would certainly save me a few steps and a good amount of time

this would be extremely useful, thumbs up for this feature

Hi,
I'm just another person that decided to create a github account on Feb 2nd.

Hey, so many votes for this issue! Ok, let's move its priority. WDYT about this syntax:
select ... order by random

This would be very useful for problems that requires subsetting.
Order by random combined with traverse would be a killer feature for analysis of large databases.
Right now I'm doing this directly in Python.

i think is more correct a sintax like:
order by field [ask| desc|random]

Why use the field also for random?

Field is not needed in my opinion.
The sintax below is perfect:
select ... order by random

select .. order by random conflict with the case you have a field called random.

You are right.
The convention dictates that asc is not mandatory, so making it mandatory it is not good.

this can be easily achieved this way:

define your random() function in js

SELECT *, random() as random from YourClass order by random

@luigidellaquila - Could you please elaborate on your your remark that:

this can be easily achieved this way:
define your random() function in js
SELECT *, random() as random from YourClass order by random

I have tried both:
js r=function() { return Math.random();}; print( r() ); end

select r() from ouser
and
CREATE FUNCTION random return Math.random() LANGUAGE JAVASCRIPT

select random() from ouser

but no luck.  Thank you.

Hi @lucasxteixeira
did you try to create and test the funciton from Studio?
Thanks
Luigi

Sorry, my last comment was for @pkoppstein

@luigidellaquila - I would like to know how to get this to work using console.sh.  I have an uptodate version (2.1.x branch):
$ git log -1
commit aabf99e1aab1c6e21495c18b079fc3748cbcb4a8
Author: lvca<EMAIL_ADDRESS>Date:   Tue Jan 12 20:22:07 2016 +0100

    Fixed compilation problems
$ git branch
* 2.1.x
  master

Thanks.

Already available by using math_rand() function and ordering by it. Example:
select a, b, math_rand() as c from X order by c


Add simple samples for controls

Basic sample pages will be extremely useful for anyone starting up with angular-winjs

Would be very useful ... any Progress ?

Hey @FauClausen, the samples are now available on our Try Site, which you can find here. Hope this helps!


Refactor "move to function in module scope" moves function past the following variable declaration

TypeScript Version:  3.1.0-dev.20180807

Search Terms: refactor function module
Code
import "fs";

function foo() {
	const bar = 1; // select this line
}

let flag = false;
function doSomethingWithFlag() {
}

select the line with the comment
choose "extract to function in module scope"

Expected behavior:
import "fs";

function newFunction() {
	return 1;
}

function foo() {
	const bar = newFunction();
}

let flag = false;
function doSomethingWithFlag() {
}

or
import "fs";

function foo() {
	const bar = newFunction();
}

function newFunction() {
	return 1;
}

let flag = false;
function doSomethingWithFlag() {
}

Actual behavior:
import "fs";

function foo() {
	const bar = newFunction();
}

let flag = false;
function newFunction() {
	return 1;
}

function doSomethingWithFlag() {
}

The same behavior for global scope or for inner function extraction., that's because
https://github.com/microsoft/TypeScript/blob/5f46d42ad111e8cfc689b47c0532b120d42d2698/src/services/refactors/extractSymbol.ts#L1327
tries to find the nearest function declaration after the selected range
function foo() {
    [|const a = 1;|] // Extract to inner function
     let flag = false;

     function newFunction() {
        return 1;
    }

    function doSomethingWithFlag() {}
}

function foo() {
    [|const a = 1;|] // Extract to function in global scope
}

let flag = false;

function newFunction() {
    return 1;
}

function doSomethingWithFlag() {}

I'm not sure which the right fix for this issue, maybe need to add function declaration at the end of the score, like so
function foo() {
    [|const a = 1;|] // Extract to inner function
    let flag = false;
    function doSomethingWithFlag() {}
    function newFunction() {
        return 1;
    }
}

function foo() {
    [|const a = 1;|] // Extract to function in global scope
}

let flag = false;
function doSomethingWithFlag() {}
function newFunction() {
    return 1;
}

@RyanCavanaugh @andy-ms @DanielRosenwasser What do you think?

Insert a new function before the current function (the first example in the expected section)
Insert a new function after the current function  (the second example in the expected section)
Insert at the end of the scope

All parameters break the current tests, so I think need to decide which option to use before adding changes. I think @jessetrinity can help ;).

IMO, both 1 and 2 make sense.

It seems like the logical for all "extract to function in X scope" extracts to the position before the next function declaration in that scope (or the end of that scope).
Is this undesirable because the new function declaration potentially appears far away, or does it break something?

I think the logic is correct, however, I'm not sure why this issue was labeled as a "bug". Maybe the main concern that any statements except functions will be before a new/old function declaration.
import "fs";

function foo() {
	const bar = newFunction();
}

let flag = false;
// new function 3
// new function 2
// new function 1
function doSomethingWithFlag() {
}

@AlCalzone was there more context when you originally opened this issue that would help us out?

For me it was just the placement of the function. The refactor works, but it seems unlogical where the function is placed.
In the above example, newFunction and foo belong together and flag and doSomethingWithFlag logically belong together.
After the refactor, this is not immediately clear, especially if there is more than one variable declaration between the functions.


Lab 4.2 Create a custom page - Steps not matching power apps portal

Lab: 4.2
Task: 2.1
Step: 7
Description of issue
The steps state to do the following:

Navigate to the Power Apps Maker portal https://make.powerapps.com/.
Make sure you are in the Dev One environment.
Select Solutions.
Open the Fabrikam Environmental solution.
In the Objects pane on the left, select Apps.
Select the + New drop-down and select App then Page.
Select With layout and select Split Screen.

However, when you add a new App > Page, you are not prompted with any "with layout" or "split screen* option, neither is this option on the screen which follows. Steps need correcting.

This is what you see after step 6

My apologies! You are right. This wasn't appearing very clearly for me initially. Thanks for the quick response


Wrong deb/rpm Download-Link for german page version

Hi. In the german version of this page the links for rpm and deb are e.g. https://aka.ms/getteamsvon . The trailing "von" has to be separated by a space from the link.

Dokumentdetails
⚠ Bearbeiten Sie diesen Abschnitt nicht. Er ist für die Verknüpfung von docs.microsoft.com zum GitHub-Artikel erforderlich.

ID: 6457d204-d229-9154-28fd-ca9bbb4bddcd
Version Independent ID: f5d82846-41cb-3548-6997-ce23bd8f89c6
Content: Beziehen von Clients für Microsoft Teams - Microsoft Teams
Content Source: Teams/get-clients.md
Service: msteams
GitHub Login: @LolaJacobsen
Microsoft Alias: lolaj

@guija Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

Hi @guija, thank you for your feedback.
@OfficeGlobal could you kindly help? This link shouldn't be translated. Thanks!

Working on a fix

@OfficeGlobal Any update? Thanks

@guija , @scanum  article was HumanTranslated and published live. The link is fixed

@guija Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.


java.lang.ClassCastException: class java.lang.Byte cannot be cast to class java.lang.Integer ERROR

Hi guys.
We are experiencing the following error in the connector:
ERROR  ||  ******* ERROR inserting Batch *****************   [com.altinity.clickhouse.sink.connector.db.DbWriter] java.lang.ClassCastException: class java.lang.Byte cannot be cast to class java.lang.Integer (java.lang.Byte and java.lang.Integer are in module java.base of loader 'bootstrap')         at com.altinity.clickhouse.sink.connector.converters.ClickHouseDataTypeMapper.convert(ClickHouseDataTypeMapper.java:175)         at com.altinity.clickhouse.sink.connector.db.DbWriter.insertPreparedStatement(DbWriter.java:603)         at com.altinity.clickhouse.sink.connector.db.DbWriter.addToPreparedStatementBatch(DbWriter.java:466)         at com.altinity.clickhouse.sink.connector.executor.ClickHouseBatchRunnable.flushRecordsToClickHouse(ClickHouseBatchRunnable.java:199)         at com.altinity.clickhouse.sink.connector.executor.ClickHouseBatchRunnable.processRecordsByTopic(ClickHouseBatchRunnable.java:169)         at com.altinity.clickhouse.sink.connector.executor.ClickHouseBatchRunnable.run(ClickHouseBatchRunnable.java:101)         at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)         at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)         at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)         at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)         at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)         at java.base/java.lang.Thread.run(Thread.java:829)
As a result, the connector is unable to convert data from some tables.
Is there a workaround for this error?
We are using the version clickhouse-kafka-sink-connector-0.0.4.jar

Hi @jramorim13 ,
can you please provide the schema of the MySQL tables that's getting this exception.

It would also help to have the ClickHouse table.

The connection is made via a debezuim connector that puts the data from the Oracle tables into Kafka. Then the Altinity connector reads the messages in Kafka and places them in Clickhouse. But when it comes to putting this data into Clickhouse, the connector is giving this error above when trying to convert the data.
So the table is empty in the clickhouse

@jramorim13 we only support MySQL / Postgres / MongoDB at the moment, not Oracle database yet. What error do you get in the log file ?
Feel free to contribute if you can fix the issue.
Pretty sure this is a data type mapping issue (a blob or binary field that is not recognized).
In CH it would be escaped at base64 or hex not to lose information.
Please paste the Oracle table that is failing.


WIP: ts_test rule

Some things to note about this approach:

We still only publish one npm package, @bazel/typescript and since it includes ts_test you need all the karma dependencies
The karma dependencies are regular deps, not peer deps, so we control versions. Probably a good thing, but it doesn't really work that way - if the user installs karma, our karma_bin will require('karma') at the top level and see the users version, not the one under node_modules/@bazel/typescript
Doesn't yet include any way to discover and connect to an existing karma instance, so it starts a bunch of browser windows, one per test target. Can add that later
depends on a fix in rules_nodejs that might be tricky to land (still don't have the module resolution search path ordering quite right for all cases)

/cc @bowenni

Once we like the basic shape, I'll do a copybara import into google3 and mark some files as integrated (eg. the concatjs node impl) and we can do more review internally.


Fix existing diagram snapshot tests for latest diagram

Codecov Report

Merging #14624 into master will increase coverage by 0.01%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master   #14624      +/-   ##
============================================
+ Coverage        64%   64.01%   +0.01%
  Complexity      523      523
============================================
  Files          2274     2274
  Lines         99054    99054
  Branches      13164    13164
============================================
+ Hits          63397    63409      +12
+ Misses        30659    30655       -4
+ Partials       4998     4990       -8

Impacted Files
Coverage Δ
Complexity Δ

...n/java/org/ballerinalang/bre/bvm/BVMScheduler.java
43% <0%> (-3%)
0% <0%> (ø)

...e/src/main/java/org/ballerinalang/bre/bvm/BVM.java
78.48% <0%> (+0.03%)
0% <0%> (ø)
:arrow_down:

...a/org/ballerinalang/bre/bvm/GlobalMemoryBlock.java
79.41% <0%> (+0.98%)
0% <0%> (ø)
:arrow_down:

.../java/org/ballerinalang/bre/bvm/BLangVMErrors.java
73.95% <0%> (+1.04%)
0% <0%> (ø)
:arrow_down:

...org/ballerinalang/bre/bvm/WaitCallbackHandler.java
82.88% <0%> (+1.8%)
0% <0%> (ø)
:arrow_down:

...va/org/ballerinalang/util/codegen/PackageInfo.java
85.26% <0%> (+2.1%)
0% <0%> (ø)
:arrow_down:

...ang/net/http/actions/websocketconnector/Close.java
72.72% <0%> (+2.27%)
0% <0%> (ø)
:arrow_down:

...a/org/ballerinalang/bre/bvm/WorkerDataChannel.java
84.56% <0%> (+2.46%)
0% <0%> (ø)
:arrow_down:

...va/org/ballerinalang/channels/ChannelRegistry.java
97.29% <0%> (+2.7%)
0% <0%> (ø)
:arrow_down:

...java/org/ballerinalang/bre/bvm/BLangVMStructs.java
50.81% <0%> (+3.27%)
0% <0%> (ø)
:arrow_down:

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 b0bc0d5...e0a0322. Read the comment docs.


Always get an 403 forbidden error

When i run this container with the dockersock proxy, i always get these errors:
time="2020-02-26T19:59:13+01:00" level=fatal msg="Error response from daemon: 403 Forbidden\nRequest forbidden by administrative rules.\n",
time="2020-02-26T19:59:14+01:00" level=debug msg="Sleeping for a second to ensure the docker api client has been properly initialized.",
time="2020-02-26T19:59:15+01:00" level=debug msg="Retrieving containers including stopped and exited"
Traefik with the dockersock-proxy is working fine.

Can you show me your docker-compose.yml or docker run commands used? My image is directly based off of https://github.com/tecnativa/docker-socket-proxy so it accepts all environment variables from it. You may need to add more environment variables to give the proxy more permissions.

  `dockersock-proxy:
    hostname: dockersock-proxy
    image: demyx/docker-socket-proxy
    container_name: dockersock-proxy
    restart: unless-stopped
    privileged: "true"
    environment:
      CONTAINERS: 1
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    networks:
      - dockersock-proxy
      - reverseproxy
    ports:
      - "<IP_ADDRESS>:2375:2375"

  ouroboros:
    image: demyx/ouroboros
    container_name: ouroboros
    hostname: ouroboros
    restart: unless-stopped
    user: ${PUID}
    networks:
      - dockersock-proxy
      - reverseproxy
    environment:
      - TZ=Europe/Amsterdam
      - LOG_LEVEL=debug
      - SELF_UPDATE=true
      - CLEANUP=true
      - IGNORE=traefik autelia authelia-mariadb authelia-redis
      - DOCKER_SOCKETS=tcp://dockersock-proxy:2375
      - DOCKER_TLS_VERIFY=false
      - DOCKER_TLS=false``

Traefik works because it just needs the CONTAINERS env. Here's what I have for my Demyx stack:
- CONTAINERS=1
- EXEC=1
- IMAGES=1
- INFO=1
- NETWORKS=1
- POST=1
- VOLUMES=1

Its working fine now. Maybe a good idea to update the documentation? With only containers it wont works.

I will make a note about updating the the README, as for Portainer, sorry I don't use it. Try the environment variables I posted and see what happens.

I'm closing this due to inactivity, also I've updated the README. Feel free to open a new issue.


Codestyle: enforce consistent statement-spacing and indentation

TLD/checkstyle.xml does not contain rules that would flag the below code. We should add them.

import javax.ws.rs.core.MediaType;
    import org.apache.commons.lang3.tuple.Triple; // wrong indent

// too many lines between statements

@Path("query")
@Produces(MediaType.APPLICATION_JSON)
@Consumes(MediaType.APPLICATION_JSON)
public class QueryResource {
        private final JavaxRestFramework httpAsync;   // wrong indent
    private final QueryManager query;

Hi @spotify/prism (sorry if this is irrelevant to you, I couldn't be arsed typing in ~10 names), please add your pet peeves with our current checkstyle
e.g. "I hate more than one parameter a line!!!" or "we must stop unsorted imports. It is an abomination."

So I've managed to implement most of the above, apart from inconsistent indentation in import statements - see my SO question.
I'll commit my changes for now and give it until Monday 23rd for an answer on SO. If no answer, I'll call this done.

I am putting this back in To-Do because it wasn't as straightforward as it seemed and the stability work must be wrapped up within 2 sprints (IIRC).

OK. So. Adding the two checkstyle directives/modules (Indentation and EmptyLineSeparator) spawned literally hundreds of errors in the heroic-component module alone :(
Hence I will create a second issue to fix all the errors. That will take a fair bit of manual work!


Support to linux?

Yeah sopport tu linux?

Just as an update, I've created minihost.
It's a lightweight solution to start servers and access them using names that works on every platform (Linux, OS X, Windows).


CI/CD Pipeline

Add in a CI/CD pipeline that will automatically run the django (and other) tests with commits.

Added in, currently in 22.05, but should get to main when that gets released.
Should trigger on all pull requests, and any pushes directly to main.


Support SSO logs mapping

Simple Schema for Observability - SSO - will support the 3 major Observability types:

Traces
Logs
Metrics

SSO will comply with the OTEL schema and continue supporting proprietary index structure
SSO for Logs was also inspired by ECS
Issues Resolved

https://github.com/opensearch-project/observability/issues/1398
https://github.com/opensearch-project/observability/issues/1404

Check List

[ ] New functionality includes testing.

[ ] All tests pass, including unit test, integration test and doctest

[x] New functionality has been documented.

[ ] New functionality has javadoc added
[ ] New functionality has user manual doc added

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

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

this PR is no longer relevant since introducing the integration as part if the 2.x branch


Use RNG (random number generator) provided by RAFT

Replace the random number generator (RNG) implemented by wholegraph with RNG provided by RAFT.
It is put forward by issue #7 and issue #23.

/ok to test

/ok to test

/rerun tests

/ok to test

/merge


Feature: Implement an indicator of the number of new posts (including normal loading of posts at the end of the list)

Fixed by 23b3c70 commit


[SPARK-40796][CONNECT][DOC][FOLLOW-UP] Add check command in Readme

What changes were proposed in this pull request?
1, fix the code gen cmd;
2, add the check cmd
Why are the changes needed?
fix the wrong cmd
Does this PR introduce any user-facing change?
yes, user will use correct cmd and know how to check
How was this patch tested?
doc only

Merged into master


[JENKINS-30826] fixed deprecation warnings

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests


Failure to delete _acme-challenge record

Nov 22 17:40:02 neo caddy[3373040]: {"level":"error","ts":1700703602.645972,"logger":"tls.issuance.acme.acme_client","msg":"cleaning up solver","identifier":"sub.domain.tld","challenge_type":"dns-01","error":"deleting temporary record for name \"_acme-challenge.sub.domain.tld\" in zone \"domain.tld.\": scaleway-sdk-go: error executing request: Patch \"https://api.scaleway.com/domain/v2beta1/dns-zones/domain.tld./records\": EOF"}
The TXT record is indeed still present after the challenge is finished.

Hey @AlyoshaVasilieva,
I could not recreate the issue using the underling library https://github.com/libdns/scaleway
Can you maybe share your Caddyfile with me?


compare with cat-seg?

yours:

cat-seg paper:

Why in your experiment, the effect of cat-seg is much worse than that provided in the cat-seg paper?

And except for the results of cat-seg, the results you provided are the same as cat-seg.

Thank for your attention !
I checked the experimental results from CAT-Seg. The results you provided came from v2.pdf, but when I wrote the paper, only  v1.pdf  was available.

Thank you for your reply. It seems that they made a lot of changes, such as removing the dependency on additional backbones. And their code currently only has the first version.


[polymetis] Hardware robustness benchmarking

Description
Please include a summary of the change and link to an issue this PR fixes. Please also include relevant context. List any downstream components that might be affected by this change.
Fixes # (issue)
Type of change
Use airspeed velocity to keep a historical view of benchmarks, including robustness.
Please check the options that are relevant.

[ ] Bug fix (non-breaking change that fixes an issue)
[ ] Proposes a change (non-breaking change that isn't necessarily a bug)
[ ] Refactor
[x] New feature (non-breaking change that adds a new functionality)
[ ] Breaking change (fix or feature that would break some existing functionality downstream)
[ ] This is a unit test
[ ] Documentation only change
[ ] Datasets Release
[ ] Models Release

Type of requested review

[x] I want a thorough review of the implementation.
[ ] I want a high level review.
[ ] I want a deep design review.

Before and After
If this PR introduces a change or fixes a bug, please add before and after screenshots (if this is causes a UX change) or before and after examples(this could be plain text, videos etc ) to demonstrate the change.
If this PR introduces a new feature, please also add examples or screenshots demonstrating the feature.

Testing
Added benchmarks under polymetis/polymetis/tests/python/polymetis/benchmarks/ which use asv to produce a historical set of benchmarks per commit.
Checklist:

[x] I have performed manual end-to-end testing of the feature in my environment.
[x] I have added Docstrings and comments to the code.
[x] I have made changes to existing documentation where needed.
[x] I have added tests that show that the PR is functional.
[x] New and existing unit tests pass locally with my changes.
[x] I have added relevant collaborators to review the PR before merge.
[x] [Polymetis only] I have verified that all scripts in tests/scripts runs on hardware.

Yeah I agree it'll be a bit better with a separate testing package that only gets installed if you need to run the tests, though it'll make the CI a bit more complicated. Let's fix it in the future if it proves an issue.


Regarding Postnet training

Hey!
Thanks for open-sourcing the code for GeneFace.
I get the following error while training Postnet for a person present in lrs3 (shaheen).
ERROR: Unexpected bus error encountered in worker. This might be caused by insutticient shared memory (shm).
ERROR: Unexpected bus error encountered in worker. This might be caused by insufficient shared memory (shm).
3.39s/step, adv=0.277, disc_fake_loss=0.232, disc_neg_conf=0.4
177. disc nos conf=0. 489. disc true loss=0. 263. 1r 0=9.000469. 1r 1=0.0001.
"/home/ubuntu/anaconda3/envs/gentace/11b/python3.9/site-packages/torch/utils/data/dataloader.py",line1134, in _try_get_data
aala = selT. aaca Qu
leue.gettimeout=Limeout
File "home ubuntuanaconda‹ envs gentaceb ovthons. 9 queuerv. ane 189. 1n det

Can you please help me on what are the kind of system requirements? I am currently using a machine with 24GB GPU RAM and 64 GB RAM with 16 cores.

Hi， this is strange. It seems the data loader is waiting too long and got killed. Maybe you could set load_ds_to_memory=True in the config, with this setting we will accelerate the IO, and ideally can handle this problem.

Okay. Let me try it.


Closing channel card shows funding transaction

After closing a channel this is the card view I'm shown:

As a user, I am personally more interested in the newly broadcasted closing transaction. I think Zap should show the closing transaction instead

@JimmyMow the same logic should probably apply to a card itself

@JimmyMow I've checked the code and am fairly sure we are displaying both funding and closing tx in that popup. For instance

The only reason why you are not seeing that must that either closing tx wasn't broadcasted at that point by the LND or somehow we didn't get that update. Could you please keep an eye on that? I'm trying to repro it too. Also, in the card view we indeed were always showing only funding tx. See #2583  that addresses that


Adding Gateway on_ready

For what thing this feature?
Using Gateway, add Gateway event "READY" as on_ready in bot.on()
Ideal solution
@bot.on("ready")
async def on_ready():
    print("Ready!")

Not ideal but cool colution
Nothing

Done


Add parsing error

Codecov Report

Merging #12 into master will not change coverage by %.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master       #12   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines           26        30    +4
=========================================
+ Hits            26        30    +4

Impacted Files
Coverage Δ

lib/ex_json_path.ex
100.00% <100.00%> (ø)

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 3a74df6...6745e0f. Read the comment docs.


Restructure README and in-repo documentation for clarity

Our current README is kind of a hodge-podge of different details. We should refocus it around a new user spinning Lift up and link to other contributor-centric details elsewhere.

I think this will be an ongoing effort, but with the things I've done in some other PRs I'm happy to close this for now.


'botocore' is necessary to use 'datasets' modules

It should ot be the case. Botocore should be required only for the functions that need it (very few actually).
The dependece on botocore should be indicated on a by-script/module basis.

Its actually boto3, botocore is installed as part of it. Openneuro uses it for downloads I believe.

The dependece on botocore should be indicated on a by-script/module basis.

That would be pretty ugly handling. Create an env for nistats based on the documentation and then run into the import error when trying to run the dependent examples? Ugly. Users not used to package management may not immediately think to check pip or conda list for package lists.


Large amount of allocations during evaluation due to boxing of KeyedObject

The call to RetrievableHashSet.Get(string) and RetrievableHashSet.Get(string, int, int) is boxing a huge amount of KeyedObject instances:

These are boxed, only to be compared as a "string" anyway. We should avoid the boxing if the enumerator already implements IConstraintedEqualityComparer/IEqualityComparer.

Here it is consuming 1.4% (348 MB):


Process aborts in the preparation stage

I attache the feedback file for your reference
centos2alma_feedback.zip
Describe the bug
A clear and concise description of what the bug is.
Feedback archive
Please attach a feedback archive to the bug report.
You could create it by calling centos2alma --prepare-feedback.
The archive will help us investigate the problem better and faster.

@FranSarr Are you using Postfix on your server or what other email configuration are you using?

Yes it does (but shouldn't). I was asking, because on the other report https://github.com/plesk/centos2alma/issues/177 the same was reported but with a different motivation to not having Postfix on the server. So it seems that when Postfix is missing, conversion fails.

Nice to know, thanks for your support and interest, pls let me know if I can be of any further help
Francisco Sarrias
Telecom Engineer
E: @.***
P: +34 607 287953
W:https://www.linkedin.com/in/fsarrias/

El 21 feb 2024, a las 21:00, Bitpalast GmbH @.***> escribió:
Yes it does (but shouldn't). I was asking, because on the other report #177 https://github.com/plesk/centos2alma/issues/177 the same was reported but with a different motivation to not having Postfix on the server. So it seems that when Postfix is missing, conversion fails.
—
Reply to this email directly, view it on GitHub https://github.com/plesk/centos2alma/issues/176#issuecomment-1957804099, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALT7X7UUQWTDGP4REREOCVDYUZG53AVCNFSM6AAAAABDMJ32XCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJXHAYDIMBZHE.
You are receiving this because you were mentioned.

The problem should be fixed with #180 merged.
Please find attached centso2alma with the fix:  centos2alma.zip

ThanksI will let you know my experience when I have time to deploy itBestFrancisco SarriasEl 22 feb 2024, a las 12:46, SandakovMM @.***> escribió:
Closed #176 as completed.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

Hello
Sorry for my late reply, just to let you know that I tried with the latest version the upgrade and it worked like a charm, thanks for your work
Best regards
Francisco Sarrias
Telecom Engineer
E: @.***
P: +34 607 287953
W:https://www.linkedin.com/in/fsarrias/

El 22 feb 2024, a las 12:48, SandakovMM @.***> escribió:
Closed #176 https://github.com/plesk/centos2alma/issues/176 as completed.
—
Reply to this email directly, view it on GitHub https://github.com/plesk/centos2alma/issues/176#event-11890026239, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALT7X7TPDKYTZENKLNXH5FTYU4WA5AVCNFSM6AAAAABDMJ32XCVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRHA4TAMBSGYZDGOI.
You are receiving this because you were mentioned.


Update onboarding.md

What changed? Why?
Adding thirdweb in onboarding sections of docs.
Notes to reviewers
How has it been tested?

🟡 Heimdall Review Status

Requirement
Status
More Info

Reviews

🟡
0/1

Denominator calculation

Show calculation

1 if user is bot
0

1 if user is external
0

From .codeflow.yml

1

Additional review requirements

Show calculation

Max
0

0

From CODEOWNERS

0

Global minimum
0

Max

1

1

1 if commit is unverified
0

Sum
1