Add fuzzing seeds to recently contributed fuzzing harnesses

Add fuzzing seeds to recently contributed fuzzing harnesses.
Seeds for:

https://github.com/bitcoin/bitcoin/pull/17050 – "tests: Add fuzzing harnesses for functions parsing scripts, numbers, JSON and HD keypaths (bip32)"
https://github.com/bitcoin/bitcoin/pull/17051 – "tests: Add deserialization fuzzing harnesses"
https://github.com/bitcoin/bitcoin/pull/17071 – "tests: Add fuzzing harness for CheckBlock(...) and other CBlock related functions"
https://github.com/bitcoin/bitcoin/pull/17093 – "tests: Add fuzzing harness for various CTx{In,Out} related functions"
https://github.com/bitcoin/bitcoin/pull/17109 – "tests: Add fuzzing harness for various functions consuming only integrals"
https://github.com/bitcoin/bitcoin/pull/17136 – "tests: Add fuzzing harness for various PSBT related functions"
https://github.com/bitcoin/bitcoin/pull/17229 – "tests: Add fuzzing harnesses for various Base{32,58,64} and hex related functions"

Thanks, I will merge them with libFuzzer -merge=1

I found that only some script flags seeds increased coverage. See 3c3b16c3791a017299b6a75fee87bcf723da4dbd

@MarcoFalke That's expected since the script flags seeds I submitted were not bootstrapped with the seeds in the repo :)
Anything I need to do to get the others in? :)

All others didn't increase coverage for me. Feel free to double check

@MarcoFalke Please note that script flags was the only fuzzer in master that got added any seeds. The rest of the seeds are to fuzzers not yet merged (see linked PR:s).
Take fuzz_seed_corpus/addr_info_deserialize/166c9b7e8a5d54837ddf5f752051c692115219ab as an example. That is a fuzzer for addr_info_deserialize and AFAICT there are no seeds for that fuzzer in this repo, right? :)

Ah, thx

Can we move forward with adding the additional seeds? :)

I'd like to add them only after the fuzzers have been merged. Otherwise I can't calculate coverage information.

Is there anything I can do to get the fuzzers merged? :)

review on them would help

@MarcoFalke Can we move forward with some of the remaining fuzzing harnesses? :)

Thanks merged in 5c4e9f981ccd5a39a0a3b1093a9ad69117d28557

Let me know if I forgot some files which increase coverage, otherwise feel free to close

Before:

After:

@MarcoFalke I'll investigate! To make sure we measure exactly the same way: what commands/options did you use to generate the coverage reports?

It looks like this:
Run prefilled_transaction_deserialize with args ...
... ['./src/test/fuzz/prefilled_transaction_deserialize', '-merge=1', '../btc_qa_assets/fuzz_seed_corpus/prefilled_transaction_deserialize', '../btc_qa_assets/fuzz_seed_corpus_other/prefilled_transaction_deserialize']
Output: INFO: Seed:<PHONE_NUMBER>
INFO: Loaded 1 modules   (14253 inline 8-bit counters): 14253 [0x55a62cdea258, 0x55a62cdeda05),
INFO: Loaded 1 PC tables (14253 PCs): 14253 [0x55a62cdeda08,0x55a62ce254d8),
MERGE-OUTER: 417 files, 207 in the initial corpus
MERGE-OUTER: attempt 1
INFO: Seed:<PHONE_NUMBER>
INFO: Loaded 1 modules   (14253 inline 8-bit counters): 14253 [0x5615a461a258, 0x5615a461da05),
INFO: Loaded 1 PC tables (14253 PCs): 14253 [0x5615a461da08,0x5615a46554d8),
INFO: -max_len is not provided; libFuzzer will not generate inputs larger than 1048576 bytes
MERGE-INNER: using the control file '/tmp/libFuzzerTemp.14696.txt'
MERGE-INNER: 417 total files; 0 processed earlier; will process 417 files now
#1	pulse  lim: 4 exec/s: 0 rss: 33Mb
#2	pulse  lim: 4 exec/s: 0 rss: 33Mb
#4	pulse  lim: 4 exec/s: 0 rss: 33Mb
#8	pulse  lim: 4 exec/s: 0 rss: 33Mb
#16	pulse  lim: 4 exec/s: 0 rss: 34Mb
#32	pulse  lim: 4 exec/s: 0 rss: 37Mb
#64	pulse  lim: 4 exec/s: 0 rss: 44Mb
#128	pulse  lim: 4 exec/s: 0 rss: 51Mb
#256	pulse  lim: 4 exec/s: 0 rss: 59Mb
MERGE-OUTER: succesfull in 1 attempt(s)
MERGE-OUTER: the control file has 114441 bytes
MERGE-OUTER: consumed 0Mb (34Mb rss) to parse the control file
MERGE-OUTER: 0 new files with 0 new features added

So that is using libfuzzer. And libfuzzer is using "features" to determine if a seed adds coverage. You can get the "feature" coverage by just running libfuzzer. One of the lines will say:
#25	INITED cov: 714 ft: 1087 corp: 16/645b lim: 4 exec/s: 0 rss: 35Mb

@MarcoFalke I'm well aware of libFuzzer reports: I was thinking about what series of commands you ran to collect data for and to generate the lcov report. Trying to reproduce your results :)

Did you use test/fuzz/test_runner.py?

Oh :sweat_smile:
https://github.com/MarcoFalke/btc_cov/blob/travis/.travis.yml

Hosted here: https://marcofalke.github.io/btc_cov/fuzz.coverage/index.html

Excellent! Exactly what I needed. Thanks!


Empty component

WIP

Alignment seems wrong

Remember to upgrade package version by a patch number, also check this item off in the todo list in README


Update target URL for LPC54114 and LPC54608

Point to the newly created mbed pages
Signed-off-by: Mahadevan Mahesh<EMAIL_ADDRESS>

cc @c1728p9

/morph test


UUID generating "----" during tests

During tests upon calling the scripts it will generate "----" as an UUID, this however does not happen when i run the actually scripts itself.
I am running Node8 and the line that invokes UUID is a simple as:
const X = uuid()

Pretty sure this an issue @Pyrathar's setup.  If/when an SSCCE is provided I'll reopen and humbly apologize.  😄


feat: Create Retrieve Aggregation Data Service

Description
this pr aims to add a new function for getting aggregate items from the database
Context

Type of changes

[ ] Refactoring (non-breaking change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would change existing functionality)
[ ] Bug fix (non-breaking change which fixes an issue)

Checklist

[ ] I am familiar with the contributing guidelines
[ ] I have followed the code style of the project
[ ] I have added tests to cover my changes
[ ] I have updated the documentation accordingly
[ ] This PR is a result of pair or mob programming

Sensitive Information Declaration
To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.

[ ] I confirm that neither PII/PID nor sensitive data are included in this PR and the codebase changes.

Are we missing a Dockerfile?


Change UI of "Accept top up request"

Member wants to top up KSH.. Should be limited to 2 digits after the decimal.

You earn cUSD 0.05

Total you send (agent currently pays the fee, at least on the UI, which should not be).

Math of total you send:
(Top up amount in KSH * conversion rate) - fee in cUSD = total you send

@steffenkrogmann please review


Fix example name and Github links for all examples

The Problem/Issue/Bug:
A directory must have been changed at some point.
Also, file links in Github seems to have 'blob' instead of 'tree' in the path.
How this PR Solves The Problem:
Fixes the name and URLs to make them work.
Manual Testing Instructions:
Do the links work?
Automated Testing Overview:
None. Only change is to the documentation.
Related Issue Link(s):
Release/Deployment notes:
Maybe the example name is used somewhere else as well? I did not check.

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

Thanks for this. These examples are actually populated in .ddev, so maybe we don't even need to link to them? But showing them online is a better way to explain how they work.

I don't have a strong opinion. But I think that page is linked to from the release notes, so a cross-link to source does help.

Thanks so much for catching and fixing this.


Clean up unused util classes...

There are a lot of unused util classes.... we should pay more attention to the usage of util classes, I think they are kind of overused...

Codecov Report

Merging #6154 (5bd631b) into dev (e8ddc91) will decrease coverage by 0.41%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                dev    #6154      +/-   ##
============================================
- Coverage     39.52%   39.11%   -0.42%
+ Complexity     3382     3301      -81
============================================
  Files           650      640      -10
  Lines         25976    25660     -316
  Branches       2872     2812      -60
============================================
- Hits          10267    10036     -231
+ Misses        14769    14708      -61
+ Partials        940      916      -24

Impacted Files
Coverage Δ

...heduler/alert/processor/AlertRequestProcessor.java
92.85% <ø> (ø)

.../master/processor/HostUpdateResponseProcessor.java
0.00% <ø> (ø)

...r/server/master/processor/StateEventProcessor.java
0.00% <ø> (ø)

...uler/server/master/processor/TaskAckProcessor.java
23.80% <ø> (ø)

...er/master/processor/TaskKillResponseProcessor.java
83.33% <ø> (ø)

...server/master/processor/TaskResponseProcessor.java
0.00% <ø> (ø)

...er/server/worker/processor/DBTaskAckProcessor.java
0.00% <ø> (ø)

...rver/worker/processor/DBTaskResponseProcessor.java
0.00% <ø> (ø)

...r/server/worker/processor/HostUpdateProcessor.java
0.00% <ø> (ø)

.../server/worker/processor/TaskExecuteProcessor.java
0.00% <ø> (ø)

... and 4 more

Continue to review full report at Codecov.

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


Error: [validTypePdf] == false

@ShubhamBansal1997 thanks so much for this great package. I'm periodically getting the following error from an implementation:
[*] Occurent some error... [validTypePdf] == false
Can you provide any info on why that would occur?

@richietyler Please elaborate a bit.


I Need video Quality high for compressed video

Hi
I am using this library for video compression. the output quality is low of compressed video. I am getting some fadded lines over video which shows video is compressed. I want to overcome this. I saw some hardcorde stuff in media controller.Tried by changing bitrate and frame rate but nothing seems to have impact. Can you please let me know which parameters i have to change to get high quality video?.

@Tourenathan-G5organisation Can u help me out??

Changing bitrate and frame widths could assist but i suggest you hold on for these parameters to be added in the upcoming version. Also can you please specify your android API level in which you are having issues?

API level was 23. I changed bitrate high and resolution to smaller. It worked but problem comes when we upload video to server, as bitrate are high I takes more time to stream and run smoothly. Which is kind of drawback.

@larrytech7 any ETA on the update??


Control is nil?

I'm not sure why, but it's not intializing. The object is nil after calling:
self.mySegmentControl = BadgeSegmentControl(
            frame: CGRect(x: padding * 0.8, y: self.segmentedPlaceholder.frame.height - (padding * 2),
                          width: self.segmentedPlaceholder.frame.width - padding,
                          height: padding),
            segmentAppearance: self.segmentAppearance())

Hello !
Humm, can you provide me more information or a simple project with an exemple ?


[Question]: Change the output language

What is your question?
After reading the documentation, I am still not sure how to get the output in a language other than English. I tried changing the patterns manually by adding "- Output always in German language, no matter what input language is given", but that is not very convenient.
Is there a way to do this in the ~/.config/fabric/.env file or during setup? Maybe by adding the preferred output language, or translating the output to another language after generating

Create a "context.md" file with "always output in German" (no quotes).  Put it in "~/.config/fabric".  Worked for me.

Maybe - if that is not implemented yet it could be an enhancement. fabric -l or fabric --language  with the ISO Language Code as option. e.g. fabric -l de or an option like --changeDefaultOutputLanguage de

Right now, the only way to do this is what @snafu4 mentioned. Make a context.md file and write that you want everything outputted in german

Is it possible to create various "context.md" files for different languages, and call them with different options in the 'fabric 'line.
Something like:

context_us.md. => -c_us
context_spain.md. => -c_es

Yeah, I was curious about multiple contexts as well. Not multiple languages in my case but I'm sure this would be a common usecase as well. I was curious if there was the possibility of having a setting that would automatically include a default context.md too (but this might warrant a separate issue).


Avoid ClassNotFoundException on Android (API level < 19)

There was removed usage of following classes: Objects and StandardCharset. When support of Android below KitKat (API level 19) becomes not-actual these changes can be reverted.

Thanks :).


Helper for injecting locals to view specs

I the past I was testing view templates that rely on locals to be passed in (e.g. partials for rendering a collection) like this:
let(:item) { double 'Item' }

before do
  allow(view).to receive(:item) { item }
end

Current versions of RSpec verify the existence of partially stubbed methods by default and will fail with the following error:
#<#<Class:0x007f9688803b00> [...] >> does not implement: item

For the discussion of a similar issue when stubbing out helper methods from the controller see also #1076.
As I do not want to disable verification of partially stubbed methods completely, I came up with the following workaround:
let(:item) { double 'Item' }
let(:options) { _default_render_options.merge locals: {item: item} }

it 'renders label' do
  allow(item).to receive(:label) { 'My Item' }
  render options
  expect(rendered).to have_text('My Item')
end

I think it would be nice to have a helper method that hides the internals and allows to call render without arguments as usual. Something similar to assign, but passing the defined locals to each call of render behind the scenes:
let(:item) { double 'Item' }

before do
  assign_locals item: item
end

it 'renders label' do
  allow(item).to receive(:label) { 'My Item' }
  render
  expect(rendered).to have_text('My Item')
end

I am not sure about the naming and the signature of this call, though. An alternative could be something more generic like the following:
stub_local :item, item

or
stub_local :item { item }

It can then also be used to stub out other local method calls from controllers e.a. (example taken from #1076):
stub_local :current_customer, customer

This allows to keep partial double verification for view examples enabled while providing a pragmatic and explicit way to deal with the Rails view context.
If you agree, I would be happy to contribute and create a pull request.

:+1:

I'd support this, it's better than trying to "fix" the verification (because a view could be used by multiple controllers etc) and would mean the methods do actually exist on the view.

I have used:
helper.class.send(:attr_reader, :item)
assign(:item, value)

But assign_locals would be more convenient way.
assign_locals item: item

Wow, it has been quite some time since I originally posted this. :sunglasses:  I will have a look at it and create a PR whenever I find some time this week.

It is required for view and helper specs If mocks.verify_partial_doubles = true is used. I don't understand how people workaround this problem for a 6 months.

Most people have probably either turned off verify_partial_doubles or worked around it by mixing in modules or the like. Also I'm not sure how common it is to write view specs.

@codebeige @yevhene is there any reason why you can'd render ... :locals => some_hash as per the docs: https://relishapp.com/rspec/rspec-rails/docs/view-specs/view-spec#passing-spec-with-rendering-of-locals-in-a-partial ?

It is all just about clarity and convenience. In order to pass in the :locals option we would have to explicitly pass the partial in every render call as well.
Look at this gist for a basic implementation of my proposal that can easily be included in your project.

@codebeige Can you explain to me why you prefer having add_local or whatever, and an implicit render call, instead of render :view_name, :locals => some_hash, it feels like the explicit call makes it more obvious what's going on.
That gist link doesn't look quite right (it's some html and JS), can you give us an updated one?

Fixed the link to the gist.
It is a matter of taste, I guess. I like to set the general prerequisites like the subject and mandatory assigns inside a before block for the context and then only override what is different for a specific example.

@JonRowe I'd like your opinion here. So I'm not sure we should support this, given that :locals is a thing, and it's easy for users to put their own in. I'm not convinced this is a "core" RSpec thing, but I could be convinced. Do you have thoughts?

@samphippen could we implement this with :locals? We're kind of about making these things easier but to be honest I'm not strongly committed to this, I don't think view specs are worth it anyway.

Labelling this ticket as ready to go. Look at this gist for a starter implementation strategy: https://gist.github.com/codebeige/86905eb7dd7cef33230223ae456fe2f0

Closing in favour of https://github.com/rspec/rspec-mocks/issues/1102

Three years later and already closed, this issue still pops up on top in search results. For everyone who landed here looking for solution:
describe "orders/show", type: :view do
  it "renders order's number" do
    order = create(:order, "abc")

    render template: subject, locals: {
      order: order
    }

    expect(rendered).to have_text("abc")
  end
end

To improve upon @lunohodov's suggestion, if you're testing partials, you can also do this.
RSpec.describe 'orders/order' do
  it 'renders order partial' do
    order = create(:order)

    render subject, order: order

    # ... Your expectations ...
  end
end


Add @argument to %ruff  for ignoring errors due to cell by cell linting

Some of the violations printed by %ruff do not make sense in the context of Jupyter Notebook environments due to the cell by cell linting that occurs. This was previously handled via configuration in pyproject.toml
Since %ruff will only be used in Ipython environments and, algoesup is on the PyPi, we could add an @argument to %ruff so that  violations that do not make sense for this environment are ignored.

If this is something you could do and test w/ Colab, I'd appreciate.

Yes sure no problem.

Thanks. From https://docs.astral.sh/ruff/configuration/#full-command-line-interface it seems we can do in the CLI all that is in  src/essays/pyproject.toml, with ruff check --ignore D100,W292,... --select ... --output-format pylint.

pytype also needs to be configured from the command line, but the pyproject.toml file can remain for those linting from the terminal


C627 chipset failed with Asym query

[root@localhost build]# lspci | grep -i quick
4e:00.0 Co-processor: Intel Corporation C62x Chipset QuickAssist Technology (rev 05)
4f:00.0 Co-processor: Intel Corporation C62x Chipset QuickAssist Technology (rev 05)
50:00.0 Co-processor: Intel Corporation C62x Chipset QuickAssist Technology (rev 05)
[root@localhost build]# ./du_mgr query 4e:00.0 0
[DevUtil]: Device:4e:00.0
[DevUtil]: Operation: query
ADF_UIO_PROXY err: du_user_ioctl: Failed to execute ioctl command
ADF_UIO_PROXY err: icp_adf_userDuQuery: Failed to send device utilization query
[root@localhost build]# ./sla_mgr caps 4e:00.0
ADF_UIO_PROXY err: icp_adf_userSlaGetCaps: Failed to get SLA capabilities
[error] Failed to get SLA caps for 4e:00.0
[error] Failed to execute SLA command
[root@localhost build]#
[root@localhost build]# lsmod | grep -i qat
qat_c62x               18064  0
intel_qat             251126  2 usdm_drv,qat_c62x
uio                    19338  1 intel_qat
[root@localhost build]#
[root@localhost build]# modinfo qat_c62x
filename:       /lib/modules/3.10.0-1160.el7.x86_64/updates/drivers/crypto/qat/qat_c62x/qat_c62x.ko
version:        4.15.0
description:    Intel(R) QuickAssist Technology
firmware:       qat_c62x_mmp.bin
firmware:       qat_c62x.bin
author:         Intel
license:        Dual BSD/GPL
retpoline:      Y
rhelversion:    7.9
srcversion:     39C1168CAEC5B7DC47A118F
alias:          pci:v00008086d000037C8svsdbcsci*
depends:        intel_qat
vermagic:       3.10.0-1160.el7.x86_64 SMP mod_unload modversions
[root@localhost build]#

For du_mgr, you can refer the README file under quickassist/utilities/apps/du_mgr directory. Please check the "ServicesProfile" parameter is set to one of the values: CRYPTO, CUSTOM1, COMPRESSION in device config files (/etc/c6xx_devX.conf). Please restart the device if device config files are modified.
The order of du_mgr should be:
du_mgr start
(wait for 5-10 seconds)
du_mgr stop
du_mgr query


Fix/redis pvc

Updates for search chart to handle inconsistent behavior setting up the redis PVC

Bumped the versions, didn't see a script to update the README?

Bumped the versions, didn't see a script to update the README?

I usually use this helm-docs container when doing those updates

docker run --rm --volume "$(pwd):/helm-docs"  jnorwood/helm-docs:latest

https://github.com/norwoodj/helm-docs

helm-docs, as Yaphete stated, is what is used to update/create the readme files.  Run it with your CWD as devops/helx.

Something is funky with this and the other ambassador changes @pj-linebaugh merged in. I'm going to make a clean PR to make sure it's all sorted out


fix(books): free-programming-books-pt_BR broken links

What does this PR do?
Improve repo
For resources
Description
Updates cocoaheads brasil podcast link.
Why is this valuable (or not)?
How do we know it's really free?
Open the site and scroll a little bit for all the free podcasts audio, also there are free links to google podcast platform.
For book lists, is it a book? For course lists, is it a course? etc.
It is a podcast list links with the same topic as mentioned before ios.
Checklist:

[X] Read our contributing guidelines.
[X] Search for duplicates.
[X] Include author(s) and platform where appropriate.
[X] Put lists in alphabetical order, correct spacing.
[X] Add needed indications (PDF, access notes, under construction).
[X] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

Thanks, and welcome to free-programming-books!


Unwanted vertical scrollbar in mobile grid docked summary row

Noticed this on mobile with a client project when I turned on the new docked summary row.

To replicate in Toolbox you need to adjust the primary name column from flex:1 to some fixed width (I used 200) and then expand a node in the tree to trigger vertical scrolling.

Fixed via #1185


Cant find the syntax Error

Note: this is the technical bug tracker, please use other platforms for getting support and starting a (non technical) discussion. See the [getting help page]((https://gekko.wizb.it/docs/introduction/getting-help.html) for details.
I'm submitting a ...
[x ] bug report
[ ] question about the decisions made in the repository
Action taken (what you did)
Modefied the parameters and tried run the config.
Expected result (what you hoped would happen)
That the config runs
Actual result (unexpected outcome)
Got this error:
SyntaxError: Unexpected token :
at createScript (vm.js:80:10)
at Object.runInThisContext (vm.js:139:10)
at Module._compile (module.js:616:28)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at Object. (C:\Users\threi\Gekko\gekko-stable\gekkoga\run.js:16:16)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Function.Module.runMain (module.js:693:10)
at startup (bootstrap_node.js:191:16)
at bootstrap_node.js:612:3
I checked the sytax and see no error
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, etc)
This is the code:
const randomExt = require('random-ext');
const config = {
stratName: 'neuralnet',
gekkoConfig: {
watch: {
exchange: 'kraken',
currency: 'EUR',
asset: 'XRP'
},
//    daterange: 'scan',
daterange: {
  from: '2018-02-01 00:00',
  to: '2018-05-21 16:55'
},

simulationBalance: {
  'asset': 1,
  'currency': 1
},

slippage: 0.05,
feeTaker: 0.25,
feeMaker: 0.15,
feeUsing: 'taker', // maker || taker

},
apiUrl: 'http://localhost:3000',
// Population size, better reduce this for larger data
populationAmt: 20,
// How many completely new units will be added to the population (populationAmt * variation must be a whole number!!)
variation: 0.25,
// How many components maximum to mutate at once
mutateElements: 8,
// How many parallel queries to run at once
parallelqueries: 5,
// profit || score
// score = ideas? feedback?
// profit = recommended!
mainObjective: 'profit',
// optionally recieve and archive new all time high every new all time high
notifications: {
email: {
enabled: false,
receiver<EMAIL_ADDRESS>senderservice: 'gmail',
sender<EMAIL_ADDRESS>senderpass: 'password',
},
},
stoploss: [ture,false],
getProperties: () => ({
historySize: randomExt.integer(100, 1),

threshold_buy: randomExt.float(25,0).toFixed(2),
threshold_sell: randomExt.float(0,-25).toFixed(2),

price_buffer_len: randomExt.integer(1000,10),
hodl_threshold: randomExt.float(1,0).toFixed(2),
learning_rate: randomExt.float(1,0).toFixed(2),

momentum: randomExt.float(1,0).toFixed(2),
decay: randomExt.float(1,0).toFixed(2),
min_predictions: historySize,

stoploss_enabled:randomExt.pick(config.stoploss),
stoploss_threshold: randomExt.float(1,0).toFixed(2),

 },

candleSize: randomExt.integer(1000, 1),

})
};
module.exports = config;

Maybe this stoploss: [ture,false], should be stoploss: [true,false], ?

There is no difference between stoploss: [ture,false],
and                                             stoploss: [true,false],

Not sure what you mean, there is a difference between spelling things correctly and not spelling things correctly. Did you try correcting that error and seeing if you still experience the same problem? The problem you're having is a problem with gekkoGA, not gekko. Maybe you will get better support by using the bug/issue tracker at https://github.com/gekkowarez/gekkoga instead of this one.

Ohh you are right. I didn't saw the difference.
Thank you!
Now I have one question. How can min_predictions and historySize use the same random number.
historySize: randomExt.integer(100, 1), min_predictions: historySize, was my idea but it didn't worked.

Closing this as it's an issue with GekkoGA!


Code splitting: all chuncks are loaded at once

Do you want to request a feature or report a bug?
Report a bug

What is the current behavior?
Routing with react-router, redux and redux-saga entails a lot of repeated code, just have a look here. 21 lines for a single route. In my app I have dozens of routes, so it is very important to DRY it out somehow. Otherwise this file routes.js will be a mess with 1000+ lines.
This is what I came up to.
It works quite well despite one big problem. Webpack's code splitting works incorrectly: all the chunks get loaded when any page of the app is opened.
If the current behavior is a bug, please provide the steps to reproduce.
Here is the link to the demo repo.

What is the expected behavior?
It should load only the needed chunks for the exact route and load other chunks on demand when a user goes to another page.
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.
Tried on different OSs and node versions with no luck.

I consider this a bug, because my bundle is split into chunks and the app knows which route I open (I tried to insert console.log into getComponent method and it prints correct route name for different routes).
When the bundle is divided into chunks and routing works correctly, webpack can work correctly and load the needed chunks on demand, right? But this doesn't happen. Please, correct me if I'm wrong.

This code:
  const childRoutes = [
    createRoute(
      '/',
      'home',
      import('pages/Home'),
    ),

calls import().
You better pass a closure:
  const childRoutes = [
    createRoute(
      '/',
      'home',
      () => import('pages/Home'),
    ),


KivyMD Studio

Description of the Feature
https://www.youtube.com/watch?v=Cz_1IFpmIgQ
where do i get kivy studio?

KivyMD Studio is currently (10.03.2020) is under development. You cannot get it for now.


Infer container image properties from Project metadata

Users should be able to easily set the key aspects of image configuration from their project file. There should be a clear integration point at which those values are 'fixed' and can no longer be changed, and there should be reasonable inference for these properties where it makes sense. Where relevant, we should rely on properties that are already conventionally available - packaging information from NuGet and source control information from SourceLink are good examples of these. That lets us make use of documentation and examples from those projects to lessen the number of new concepts here.

Image Metadata
Required*
Element Type
Element Name
Data Type
Inference algorithm
Example

Base Image Name
✅
Property
ContainerBaseImageName
string
Based on the ProjectCapabilities of the project - if AspNetCore is present, prefer the dotnet/aspnet base image, otherwise prefer the dotnet/runtime image
mcr.microsoft.com/dotnet/aspnet

Base Image Tag
✅
Property
ContainerBaseImageTag
string
Based on the TargetFrameworkVersion of the project - net6.0 maps to the 6.0 tag, for example
6.0

Base Image
✅
Property
ContainerBaseImage
string
If this is specified, it completely overrides ContainerBaseImageName and ContainerBaseImage. Otherwise, it is the result of concatenating them together, separated by :.
mcr.microsoft.com/dotnet/aspnet:6.0

Image Name
✅
Property
ContainerImageName
string
The value of the $(AssemblyName) property, lowercased so that it matches image name requirements
weatherapp

Image Tag
✅
Property
ContainerImageTag
string
The value of the Version property. This one is a bit loose, would folks prefer multiple tags here?
1.0.0

Working Directory
✅
Property
ContainerWorkingDirectory
string
Defaults to /app. This directory will be the 'root' of the project's deployed files.
/app

Entrypoint
✅
Item?
ContainerEntrypoint
string[]
If the project is self-contained, the entrypoint defaults to the name of the generated apphost. Otherwise, for a framework-dependent project, the entrypoint defaults to dotnet <path to project's output.dll>
dotnet weatherapp.dll. The path to the apphost or output dll will change based on the ContainerWorkingDirectory

Cmd
❌
Item?
ContainerCommand
string[]
No inference. If specified, these arguments will be supplied to the container's entrypoint
-

Ports
❌
Item
ContainerPort
<ContainerPort Include="<port number>" Type="tcp, udp" />
If the project has the AspNetCore capability, port entries for TCP 5000 and TCP 5001 will be created
<ContainerPort Include="5000" Type="tcp"/><ContainerPort Include="5001" Type="tcp"/>

Environment Variables
❌
Item
ContainerEnvironmentVariable
<ContainerEnvironmentVariable Include="ASPNETCORE_URLS" Value="http://localhost:5000" />
If the project has the AspNetCore capability, the ASPNETCORE_URLS variable will be set to http://localhost:5000;https://localhost:5001

Labels
❌
Item
ContainerLabel
string key, string value
We may set some of the well known labels, see below.
<ContainerLabel Include="org.opencontainers.image.created" Value="2022-06-07T12:10:12Z" />

NOTE: Required in this case means required to have a working container image, not that the user is required to provide a value for the item. We will do inference to fill in all required items, erroring on validation if necessary.

Labels
There are some well-known labels that we should consider setting by default:

Annotation Key
Derived from

org.opencontainers.image.created
$([System.DateTime]::UtcNow.ToString("o"))

org.opencontainers.image.authors
$(Authors)

org.opencontainers.image.url
$(RepositoryUrl) if present.

org.opencontainers.image.documentation
Since $(PackageLicenseUrl) is deprecated, we may just have to default to $(RepositoryUrl). Users should be able to override this easily though.

org.opencontainers.image.source
$(RepositoryUrl) if present.

org.opencontainers.image.version
$(Version) if present. Note that there's not really a consistent place to hook into where we can be assured of a version being set, so we'll want to be sometime directly before Build, but as late as possible otherwise.

org.opencontainers.image.vendor
There's no $(PackageOwners) or $(Owners) to bootstrap off of, but maybe we should make one?

org.opencontainers.image.licenses
$(PackageLicenseExpression)

org.opencontainers.image.ref.name
$(RepositoryBranch) or $(RepositoryCommit). There's not a baked-in for git repo tags in SourceLink, which would be ideal. Commit is probably the best one.

org.opencontainers.image.title
$(Title)

org.opencontainers.image.description
$(Description)

org.opencontainers.image.base.digest
The resolved digest of $(ContainerBaseImage)

org.opencontainers.image.base.name
$(ContainerBaseImage)

Example project file

<Project Sdk="Microsoft.NET.Sdk">
    <PropertyGroup>
        <TargetFramework>net7.0</TargetFramework>
        <OutputType>Exe</OutputType>
        <Version>1.2.3</Version>
    </PropertyGroup>

    <ItemGroup>
        <PackageReference Include="Dotnet.ReproducibleBuilds"  Version="1.1.1" PrivateAssets="all" />
    </ItemGroup>

    <ItemGroup>
        <ContainerPort Include="1234" Type="udp" />
        <ContainerEnvironmentVariable Include="LOG_LEVEL" Value="trace" />
        <ContainerLabel Include="org.contoso.businessunit" Value="C+AI" />
    </ItemGroup>
</Project>

@BenVillalobos I updated the table - one thing I'm wrestling with is that a mix of properties and items is not great from a end-user experience point of view - the user has to hop around to separate XML elements to describe their container. Another thing that's worth digging into is that the Entrypoint and Cmd properties natively are string arrays, so that we don't have to handle shell token escaping, but the most 'natural' way for a user to define them in MSBuild would be a single string property. @rainersigwald  and I have chatted a bit about maybe a CLI-splitting property function? or just accepting the pain and requiring Items for this. What are your thoughts?

All of the items other than the command line could be semicolon-delimited properties (and there's precedent for that in other places in MSBuild). That's not ideal but it would keep things together.
Another option to keep things together, maybe, is metadata on an item, but that's a lot harder to customize in targets at build time.

Focusing on Cmd & how users should define that for a bit, I'm gonna brain dump the options I immediately see.
The Item Route
<Project>
	<!-- I'm a user that wants to containerize an app, but I have a specific command-line that I need to run. Idk... `cmd echo 'foo'`-->

	<ItemGroup>
		<!-- Here's one way to do it, just shove it all into the include. -->
		<!-- Pros: Leaves room for metadata on a command. Not much else...? -->
		<!-- Cons: If the entire cmd could be placed in the include, why not make it a property? -->
		<ContainerCommand Include="cmd.exe echo foo"/>

		<!-- Another option: Main command is the include, args come from metadata -->
		<!-- Pros: Slightly more organized. -->
		<!-- Cons: Is the 'possibility of metadata on this item' enough of a pro that it justifies items?-->
		<!-- Thoughts: I like this more than the previous, but I'm leaning towards properties for commands. -->
		<ContainerCommand Include="cmd.exe" Arguments="echo foo"/>
	</ItemGroup>
</Project>

The Property Route
<Project>
	<!-- I'm a user that wants to containerize an app, but I have a specific command-line that I need to run. Idk... `cmd echo 'foo'`-->

	<!-- Pros: Simplicity -->
	<!-- Cons: Needs to be converted eventually. Having tons of properties in general has always felt "disconnected". -->
	<!-- Thoughts: Our future 'ParseTheContainerInfo' task could theoretically handle the logic. This does feel more intuitive.-->
	<PropertyGroup>
		<ContainerCommand>cmd.exe echo 'foo'</ContainerCommand>
	</PropertyGroup>

</Project>

I have chatted a bit about maybe a CLI-splitting property function?

The CLI portion is where I'm not 100% in sync. Can you describe a super brief scenario for that? My understanding is: Add a property function that will turn a space-delimited command line into a string[]? Or Item to flow into the build?

Another option to keep things together, maybe, is metadata on an item, but that's a lot harder to customize in targets at build time.

To play devil's advocate: Do we care about modifying this stuff during the build? Would the output of some build step determine some metadata within an item? I think I'm just lacking scenarios to base this on so it's difficult to think in terms of flexibility (complexity) vs simplicity

ProjectCapabilities are Yet Another MSBuild Item that VS (and other IDEs) can use to light-up UI or editor capabilities. They are 'markers' more than anything else. The AspNetCore one is included in a set of props/targets called the ProjectSystem targets, but that's always included in the 'core' WebSDK so for an aspnet project it should always be present. That's why I thought it would be a good, reliable differentiation point for the feature.

Right now we're fixated on the framework-dependent scenario, especially when it comes to inferring what the base image should be.
For single-file, self-contained style deployments, though, we should support using the runtime-deps images for linux or the nanoserver images for Windows (even though we're not explicitly looking at Windows at the moment).

Some random thoughts after reading through this list:

Currently an ENTRYPOINT gets generated that starts the app.
Sometimes you want to preserve the entrypoint of the base image, and start the app using a CMD instead.
Cmd allows to do this, but then requires to manually specify the command which is otherwise auto-generated. It would be nice to be able to opt-in to using a CMD instead of an ENTRYPOINT.

For User and Group. If the base image does not have this user/group, will they be added? In that case, does the string format accept both a numeric id, as well as a name (like tmds:1000)?

Maybe add something like ContainerBaseImageTagSuffix to enable picking the -alpine, ... variants of the Microsoft images.

Sorry for the delay here @tmds -

Let's talk this one over in #398 - I agree that we need a better pattern for these use cases
This tooling supports username, uid, groupname, and gid - with the caveat that anything you provide must already be on the base image (or some other layer included in the image through some other means). We can't easily modify the actual OS configs since there's no underlying VM to run commands against.
I'll make a separate issue to track this - it is already very apparent with the MS images, and seems to be a prevalent pattern.


No support for placeholder translation

Hello,
django_select2 breaks when the widget placeholder is initialized using Django ugettext_lazy function, like this:
select2_options={'placeholder': _(u'Add category...')}

This results in TypeError:
<django.utils.functional.__proxy__ object at 0x7fc2280c9b10> is not JSON serializable

Hi @emorozov, have you tried ugettext instead of it's lazy version?

@codingjoe I know that this will work. But usually widget options are set in form definition which is executed when module is loaded, so using ugettext is pointless here.

And your point is? It should work, but it doesn't, yet there is a perfectly fine solution to it?
I don't mind having this fixed but you'd need to provide a pull request.

@codingjoe It's not a perfectly fine solution because if you use ugettext, placeholder will be translated only once: when you start the application and all modules are loaded by Django.
ugettext_lazy is used because translation should happen on every page render, to display placeholder in user's locale. Application can be accessed by users preferring different languages: Russian, Spanish, French, etc. Every user needs to see placeholder translated to their own language.
When ugettext is used on module level, placeholder will be translated only once. When ugettext_lazy is used, translation will be different for every user.
It's the same with Django models: help text and other properties are translated using ugettext_lazy exactly for this reason.
Sorry, if my explanation is difficult to understand. I don't have much time now, but maybe in a week or two I can try to fix this issue and submit the pull request.

There is simple workaround how to handle placeholder translation. In MyForm.__init__, you can do
self.fields['add_people'].widget.options['placeholder'] = ugettext("Select user here")

which is not-so-elegant-but-working-solution.

@emorozov I don't think this is a select2 problem, but rather a django one. Thus I'll close the thicket. But feel free to submit a pull-request.
For the record @VerosK your's is a very valid and good solution.

@codingjoe Yes, I've used the same workaround myself for all this months, but it's pretty ugly in my opinion.
I've finally decided to fix the bug properly and created a pull request.


Fix IVariant -Wdeprecated-copy-with-dtor

Since C++11 the generation of implicit copy constructor is deprecated if
the type has a user-defined constructor or destructor (even if defaulted).
Fix this by adding a defaulted copy-constructor for IVariant that remove
the implicit default constructor, so add it too.

Thank you!


npm show causing EAUTHUNKNOWN with VSO Package feeds

Hey, I realise that this is likely a limitation / bug within VSO's package feed itself and have raised it as an issue over there.
The recent addition of "npm show audit-ci version" in 2.4.2 is causing an authentication issue in Azure DevOps, even with an authenticated token in my projects .npmrc (No issues with npm installs etc, so authentication is working fine).
I don't think there is any way to avoid this other than fixing my version to 2.4.1, or am I missing something here?

I had no idea this would be a blocking issue for some builds.
The two approaches I would be comfortable moving forward with would be:

Somehow fix it by avoiding npm show audit-ci version call (potentially by reading the disk).
Have a config option to toggle showing the version.

@Lokiem, thoughts?

The command now miraculously works, I'm sorry for flagging this as a possible issue. (Though I'd tend to favour the QoL default, with a flag to disable. But no fix is required now!)
Whether this was some issue with my setup, or if the raised issue on the VSO boards had someone do a sneaky fix I'll never know.

Thanks! Feel free to re-open if the issue arises again.


Visualize growth trend with historic SPARQL queries

I would like to expand visualization graphs such as shown here in order to increase understanding of trends.
Sources of inspirations on LinguaLibre:Stats/Time

Status
Focus
Added semantic value
Visualization
Code pad

✅
Records per months
Shows overall recording trend
gdoc
paws

✅
Active languages per months
Shows overall diversity and popularity trend
gdoc
paws

✅
Active speakers per months
Shows overall participants trend
gdoc
paws

✅
Monthly cumulative
Shows overall cumulative evolution
-
paws

✅
HAL publications
HAL Open Archive Publications, yearly
-
paws

🕐
Records per languages (rows) and per months (columns)
Shows when a language starts to be active and how it progresses along time

🕐
Active speakers per languages (rows) and per months (columns)
Idem, but with focus on participants.

Example

https://public-paws.wmcloud.org/User:Yug/QueryWikidata-Copy1.ipynb

@kaze_no_oni


Make draft admin links previewable

It is common that publishers may work on documents that need to be published more or less simultaneously. In such cases, the desired functionality is that a draft edition should be previewable from another draft edition.
Until now, if the edition was not "linkable" (i.e. not live or about to be published due to it being scheduled), its associated admin link would render as plain text. An admin link is an internal link in the format govuk/admin/.... As a workaround, users had to use draft-origin full public URLs when drafting, and then change them to admin links before publishing.
These changes ensure we manipulate an admin link so that it serves the draft origin version if the edition is in draft, and live if the edition has been published.
If the user published a document containing a draft link, the linked draft edition will not get published. Nonetheless, there is now a risk that the draft link will be rendered on the live document where it is embedded, as opposed to rendering as plain text as it used to. The publishers would be required to exercise caution and ensure the correct order of publishing.
Trello card

@lauraghiorghisor-tw any objection to my closing this? I think we agreed it wasn't a great idea, based on my comment on the linked Trello ticket:
"We could make the links work in the preview, but if the linked document wasn't published before the linking document was published, the link would cause a "page not found" error for end users. We don't want to make publishers responsible for ensuring that they publish linked documents in the correct order."

@lauraghiorghisor-tw any objection to my closing this? I think we agreed it wasn't a great idea, based on my comment on the linked Trello ticket:
"We could make the links work in the preview, but if the linked document wasn't published before the linking document was published, the link would cause a "page not found" error for end users. We don't want to make publishers responsible for ensuring that they publish linked documents in the correct order."

Can close 🆗


DO NOT MERGE: draft multitenancy

@mattbroussard @davidbkay just opening an MR that we will not merge. Mostly just to discuss specific code changes that we can isolate into github issues.


Hackage doc missing @

Not sure if this is known already or not but it seems like the doc in hackage is missing @ in the example:

Supposed to be val @"foo" 123 instead of val "foo" 123
Link to hackage: https://hackage.haskell.org/package/composite-base-<IP_ADDRESS>/docs/Composite-Record.html

nice catch, thanks!


About recaptcha

I have no clue from where to start the recaptcha like it is login page or signup can anyone help me with that.

Add the following code to your website:

<script defer src="https://www.google.com/recaptcha/api.js?render=6Lf495wpAAAAAF2j0F9_Y1e-xhHyoCKlIOr8uybS"></script>

Add the following code to your JavaScript, continuing the fetch function and changing parts to meet your specific needs:

document.querySelector('form#login')?.addEventListener('submit', (e) => {
        e.preventDefault();
        document.getElementById('errors').innerHTML = "";
        grecaptcha.ready(function() {
            grecaptcha.execute('6Lf495wpAAAAAF2j0F9_Y1e-xhHyoCKlIOr8uybS', {action: 'submit'}).then(function(token) {
                const formData = new FormData(e.target);
                formData.append("g-recaptcha-response", token);
                fetch("/php/login.php", {
                    method: "POST",
                    body: formData,

Then within your PHP file, add the following code right at the top:

$captcha = $_POST['g-recaptcha-response'];
$reCAPTCHA = json_decode(file_get_contents('https://www.google.com/recaptcha/api/siteverify?secret=' . RECAPTHCA_SECRET_KEY . '&response=' . $captcha . '&remoteip=' . $_SERVER['REMOTE_ADDR']));

if ($reCAPTCHA->score <= 0.5) die("Error goes here");

@gchodancar19 Looking over the login section of the PRL, it seems the MFA (ReCaptcha) has been assigned to Mikael, so you do not need to worry about implementing it.

Yeah just realised now.


One is that the default link format be a straight line, connected to the middle of the linked shapes

Maybe later, when we have some sort of layout algorithm(s) implemented, we might prefer a different link format - but for the moment, the suggested default is simpler and better-behaved than the current draw.io default


[WIP] Build v1_1

Hello @RiesBen! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file src/kartograf/tests/test_atom_mapping_scorer.py:

Line 74:5: E128 continuation line under-indented for visual indent
Line 74:34: E231 missing whitespace after ','


VACUUM command for PostgreSQL

This PR adds the VACUUM command parsing to cover PostgreSQL syntax. The implementation follows the PostgreSQL documentation: https://www.postgresql.org/docs/current/sql-vacuum.html

Marking as draft as this is no longer waiting on comments


Enable border customization for ButtonComponent

Is your feature request related to a problem? Please describe.
I'm using an ButtonComponent of type Informational with a white background.
The button borders are not visible and it is not possible to customize the borders.

Describe the solution or feature you'd like
Enable customizing the button borders via CSS. The UI design calls for some shadowing.
Describe alternatives you've considered
Change background color to non-white.
Additional context
Here's how the UI design looks like:

@languy  I will take a look.

@languy you can use the CSSStyles to specify the border, see example below.
view.modelBuilder.button().withProps({
			buttonType: azdata.ButtonType.Informational,
			...
			CSSStyles: {
				'border-color':'red',
				'border-style':'solid',
				'border-width':'1px'
			}
		}).component();

since you are using custom color, you have to handle the theme change event and assign the proper color for the theme.
		vscode.window.onDidChangeActiveColorTheme(e=>{
			buttonContainer.updateCssStyles({
				...
			});
		});


hyperterminator: Hyperterm theme for cybernetic organisms

hyperterminator: Hyperterm theme for cybernetic organisms, by the hard working @jxnblk.

@brianzelip so, would you submit a pull-request?

Closing this stale issue.
Open a PR if you want to add it.


Add autocompletion

This is what clap recommends https://crates.io/crates/clap_complete

@zie1ony test and close

it works


[Docs] Provide instructions for different OSs

All the instructions [here](https://sainsburywellcomecentre.github.io/cellfinder/main/user_guide/install.html] assume a Linux environment. Although the instructions are very similar, it would be useful to explicitly state them all for each OS.

Added here


Aggregation of multiple responses from downstream services

Hi,
It would be great to have multiple response aggregation functionality. Some time ago I was participating in the development of one microservice-based solution, and there was  a custom made API Gateway service which was able to create multiple requests to different downstream services, then, when all responses are received Gateway was making a data aggreagation (from multiple DTOs to single one). It was a nice approach for UI, instead of multiple requests we were able to collect data from multiple microservices at once.
Is it possible to do something similar with Ocelot?
Example:
UI [api/something] => Ocelot [api1/resource1, api2/resource2, ...] => Aggregate and return single object

Hi @xxsybreedxx
This feature has previously been requested in issue #79 it is something that I have considered implementing but haven't done yet. If this is something you would like to try implement yourself in Ocelot then there has been a discussion around it in that issue.
I will close this as a duplicate of the that issue! Hope thats OK.

duplicate of #79


APT whitelist request for libvirt-bin

Closed because this package is already in the pull request #732.


Add OpenStackDataPlaneService osdps shortname

Adds an additional osdps shortname for OpenStackDataPlaneService, to
align with the other dataplane-operator CRDs, which offer shortnames
with single characters per word.
Signed-off-by: James Slagle<EMAIL_ADDRESS>

/test dataplane-operator-build-deploy-kuttl

/test dataplane-operator-build-deploy-kuttl


StatusCake demo

Context

Changes proposed in this pull request

Guidance to review

Link to Trello card

Screenshots

 Front door outage: why was monitoring green?

Demo done, closing


'Time' class. Undefined class.

I got 'Time' class of property.
Is it 'TimeSpan'?

Welcome To Odata2Poco Project.
Can you show me the fragment of the generated c# code, so I can know the issue?

Thank you!
Public Time PropertyName {get;set;}
Edmx : Type = EDM.TIME (sharepoint service)
(I writr shortly from mibile, sorry)

It seems that it is OData  service V2. Is it ?
EDM.TIME in that case can be converted to TimeSpan
Can you confirm me the version of Odata service(V2).
It's shown when you run o2pgen.

issue. Tool does not support default proxy. I downloaded manualy metadata file. Where can i see version?

In the header of the  xml file, Something like this:
                <edmx:Edmx Version="1.0" xmlns:edmx="http://schemas.microsoft.com/ado/2007 /06/edmx">
        <edmx:DataServices xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata"
                m:DataServiceVersion="2.0">

here DataServiceVersion= 2.0

3.0

Thanks @lobster.
I will add TimeSpan data type as equivalent to EDM.TIME in the next release.
Also, Proxy will be supported too.

Thank you. I Will add separated issue about proxy and another one about overlapping properties.

Hi @lobster
You can download the  new version  3.2.0 from github

fix EDM.TIME to TimeSpan
Support Integrated windows Ntlm without credential.
support Ntlm with windows credential and a separate domain option, example:
-u user  -p password --domain my_AD_domain -o ntlm
support proxy with a new option, example:
--proxy  http://myserver.com:8888

Try it, and I appreciate your feedback.

Hi, @moh-hassan
Ntlm without credential +
Time +
Default ntlm proxy with config +


Interface is funky at medium resolutions

Around 400p, 768p, 900p and such, the top, bottom, and side interface bars don't react to the screen size properly. These resolutions rest somewhere in between our 1080p fullscreen view and mobile.
Autumn's laptop sits in one of these categories, most likely 768p. She reported that the top bar on the Fosters page containing the "New Foster" button was almost entirely obscured. This is easily replicated in Chrome's device mode.

This is urgent

Makes user think you can't edit cats on iPads

On my iPad there is:
1-no option to edit a cat after it is already input (so if I make a mistake or need to add something)

Windows Desktop and iPad:
1-The care field w adoption fee, microchip # is not visible after a cat is added, I would have to click "edit" to see that information.


Improvements | gitignore and Spam System

Hi! Today i added a lots of improvements on HSpam System and NPC system and fixed titles, ignore the commit "3548e6d", "d3a91ab" and "195c1a5" because i failed on messages ;)

Do not push at the moment, i'm working on some fixes and improvements

How to create npcs

Done, if for your is fine you can merge ;)


Relax sphinx dependency

Fixes #81. We don't really need strict sphinx versioning.

Thank you very much @LilSpazJoekp :clap:

Done.


Error while linting

I got this error on the console:
DEPRECATION WARNING on line 1, column 1:
The subject selector operator "!" is deprecated and will be removed in a future release.
This operator has been replaced by ":has()" in the CSS spec.
For example: foo bar:has(baz)

DEPRECATION WARNING on line 1, column 1:
The subject selector operator "!" is deprecated and will be removed in a future release.
This operator has been replaced by ":has()" in the CSS spec.
For example: foo.x bar.y:has(baz.z)

DEPRECATION WARNING on line 1, column 1:
The subject selector operator "!" is deprecated and will be removed in a future release.
This operator has been replaced by ":has()" in the CSS spec.
For example: .foo:has(.bar)

DEPRECATION WARNING on line 1, column 1:
The subject selector operator "!" is deprecated and will be removed in a future release.
This operator has been replaced by ":has()" in the CSS spec.
For example: .bip .bap

DEPRECATION WARNING on line 1, column 1:
The subject selector operator "!" is deprecated and will be removed in a future release.
This operator has been replaced by ":has()" in the CSS spec.
For example: .bip:has(.bap)

DEPRECATION WARNING on line 1, column 1:
The subject selector operator "!" is deprecated and will be removed in a future release.
This operator has been replaced by ":has()" in the CSS spec.
For example: x:has(.bar)

DEPRECATION WARNING on line 1, column 1:
The subject selector operator "!" is deprecated and will be removed in a future release.
This operator has been replaced by ":has()" in the CSS spec.
For example: y:has(.bap)

SCSSLint::Linter::BangFormat raised unexpected error linting file node_modules/gulp-sass/node_modules/node-sass/test/fixtures/spec/spec/libsass-todo-tests/libsass/lists/input.scss: '[BUG] Unknown operator nil'
/Library/Ruby/Gems/2.0.0/gems/sass-3.4.6/lib/sass/script/parser.rb:206:in `precedence_of'
/Library/Ruby/Gems/2.0.0/gems/sass-3.4.6/lib/sass/script/tree/list_literal.rb:33:in `block in to_sass'
/Library/Ruby/Gems/2.0.0/gems/sass-3.4.6/lib/sass/script/tree/list_literal.rb:32:in `map'
/Library/Ruby/Gems/2.0.0/gems/sass-3.4.6/lib/sass/script/tree/list_literal.rb:32:in `to_sass'
/Library/Ruby/Gems/2.0.0/gems/sass-3.4.6/lib/sass/tree/prop_node.rb:132:in `val_to_sass'
/Library/Ruby/Gems/2.0.0/gems/sass-3.4.6/lib/sass/tree/prop_node.rb:109:in `declaration'
/Library/Ruby/Gems/2.0.0/gems/sass-3.4.6/lib/sass/tree/visitors/convert.rb:233:in `visit_prop'
/Library/Ruby/Gems/2.0.0/gems/sass-3.4.6/lib/sass/tree/visitors/base.rb:36:in `visit'
/Library/Ruby/Gems/2.0.0/gems/sass-3.4.6/lib/sass/tree/visitors/convert.rb:10:in `visit'
/Library/Ruby/Gems/2.0.0/gems/sass-3.4.6/lib/sass/tree/node.rb:201:in `to_sass'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/linter/bang_format.rb:9:in `visit_prop'
/Library/Ruby/Gems/2.0.0/gems/sass-3.4.6/lib/sass/tree/visitors/base.rb:36:in `visit'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/linter.rb:127:in `visit'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/linter.rb:138:in `block in visit_children'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/linter.rb:136:in `each'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/linter.rb:136:in `visit_children'
/Library/Ruby/Gems/2.0.0/gems/sass-3.4.6/lib/sass/tree/visitors/base.rb:38:in `visit'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/linter.rb:127:in `visit'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/linter.rb:138:in `block in visit_children'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/linter.rb:136:in `each'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/linter.rb:136:in `visit_children'
/Library/Ruby/Gems/2.0.0/gems/sass-3.4.6/lib/sass/tree/visitors/base.rb:38:in `visit'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/linter.rb:127:in `visit'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/linter.rb:21:in `run'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/runner.rb:58:in `run_linter'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/runner.rb:39:in `block in find_lints'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/runner.rb:37:in `each'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/runner.rb:37:in `find_lints'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/runner.rb:21:in `block in run'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/runner.rb:20:in `each'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/runner.rb:20:in `run'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/cli.rb:52:in `scan_for_lints'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/cli.rb:46:in `act_on_options'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/cli.rb:25:in `run'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/bin/scss-lint:6:in `<top (required)>'
/usr/bin/scss-lint:23:in `load'
/usr/bin/scss-lint:23:in `<main>'
Report this bug at https://github.com/causes/scss-lint/issues

This is my .scss-lint.yml file:
scss_files: "public/style/scss/**/*.scss"

linters:
  BorderZero:
    enabled: true
    convention: 0

  ColorKeyword:
    enabled: true

  ColorVariable:
    enabled: true

  Comment:
    enabled: true

  DeclarationOrder:
    enabled: true

  DuplicateProperty:
    enabled: true

  EmptyLineBetweenBlocks:
    enabled: true

  EmptyRule:
    enabled: true

  FinalNewline:
    enabled: true

  HexLength:
    enabled: true
    style: long

  HexNotation:
    enabled: true
    style: lowercase

  IdSelector:
    enabled: true

  ImportantRule:
    enabled: true

  ImportPath:
    enabled: true

  Indentation:
    enabled: true

  LeadingZero:
    enabled: true

  MergeableSelector:
    enabled: true
    force_nesting: true

  NameFormat:
    enabled: true
    allow_leading_underscore: false

  NestingDepth:
    enabled: true
    max_depth: 2

  PropertySpelling:
    enabled: true
    extra_properties:
      - will-change

  QualifyingElement:
    enabled: true

  Shorthand:
    enabled: true

  SingleLinePerProperty:
    enabled: true
    allow_single_line_rule_sets: false

  SingleLinePerSelector:
    enabled: true

  SpaceAfterComma:
    enabled: true

  SpaceAfterPropertyColon:
    enabled: true

  SpaceBeforeBrace:
    enabled: true

  SpaceBetweenParens:
    enabled: true

  StringQuotes:
    enabled: true

  TrailingSemicolon:
    enabled: true

  TrailingZero:
    enabled: true

  UnnecessaryMantissa:
    enabled: true

  UnnecessaryParentReference:
    enabled: true

  UrlFormat:
    enabled: true

  UrlQuotes:
    enabled: true

  VariableForProperty:
    enabled: true
    properties:
      - color
      - font
      - box-shadow
      - border

  VendorPrefixes:
    enabled: true

  ZeroUnit:
    enabled: true

It took about 30 seconds for the error to appear, and it was the first and only output I received.
OSX 10.10.2, Ruby 2.0.0p481

Tested with Ruby 2.2.0, same result

Thanks for the report @albertorestifo! It seems to be blowing up on this file: https://github.com/sass/sass-spec/blob/master/spec/libsass-todo-tests/libsass/lists/input.scss
I'll need some more time to look into this, but in the meantime it would be helpful if you could whittle it down to a small repro case.
 You probably want to add this to your configuration file:
exclude:
  - 'node_modules/**'

@sds do you think it would make sense to add this exclusion to the default.yml config?

@lencioni I'm really sorry but it's a private project, and also a quite big one (there are 41 different SCSS files).
If you see any specific file that's causing the bug I can post it

As I mentioned, it seems to be blowing up on this file, which is already public: https://github.com/sass/sass-spec/blob/master/spec/libsass-todo-tests/libsass/lists/input.scss

@lencioni  by the way, about the node_modules question, the behaviour I was expecting was the following:
I have specified the files I wanted to lint, using:
scss_files: "public/style/scss/**/*.scss"

What I expect is that only those files are going to be considered. I think this should be the correct behaviour

The originally reported issue is a bug with the to_sass method of the Sass::Tree::Node class of the sass gem. In other words, not a problem on scss-lint's end.
However, I was able to work around the problem on scss-lint's side by removing our use of to_sass from a few linters in c72392b7e59f029be96ba8ee518b9a7403c9aff9.

Unfortunately v0.39.0 doesn't fix the problem for me.
The following errors occur:
$ /bin/sh -c scss-lint /path/to/some/scss/file.scss --config=/path/to/scss-lint/config/scss-lint.yml --format=XML
DEPRECATION WARNING on line 1, column 1:
The subject selector operator "!" is deprecated and will be removed in a future release.
This operator has been replaced by ":has()" in the CSS spec.
For example: foo bar:has(baz)

DEPRECATION WARNING on line 1, column 1:
The subject selector operator "!" is deprecated and will be removed in a future release.
This operator has been replaced by ":has()" in the CSS spec.
For example: foo.x bar.y:has(baz.z)

DEPRECATION WARNING on line 1, column 1:
The subject selector operator "!" is deprecated and will be removed in a future release.
This operator has been replaced by ":has()" in the CSS spec.
For example: .foo:has(.bar)

DEPRECATION WARNING on line 1, column 1:
The subject selector operator "!" is deprecated and will be removed in a future release.
This operator has been replaced by ":has()" in the CSS spec.
For example: .bip .bap

DEPRECATION WARNING on line 1, column 1:
The subject selector operator "!" is deprecated and will be removed in a future release.
This operator has been replaced by ":has()" in the CSS spec.
For example: .bip:has(.bap)

DEPRECATION WARNING on line 1, column 1:
The subject selector operator "!" is deprecated and will be removed in a future release.
This operator has been replaced by ":has()" in the CSS spec.
For example: x:has(.bar)

DEPRECATION WARNING on line 1, column 1:
The subject selector operator "!" is deprecated and will be removed in a future release.
This operator has been replaced by ":has()" in the CSS spec.
For example: y:has(.bap)

SCSSLint::Linter::LeadingZero raised unexpected error linting file node_modules/becklyn-gulp/node_modules/gulp-sass/node_modules/node-sass/test/fixtures/spec/spec/libsass-todo-tests/libsass/propsets/input.scss: 'undefined method `[]' for nil:NilClass'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter/leading_zero.rb:18:in `visit_script_number'
/usr/local/lib/ruby/gems/2.1.0/gems/sass-3.4.14/lib/sass/tree/visitors/base.rb:36:in `visit'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:131:in `visit'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:142:in `block in visit_children'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:140:in `each'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:140:in `visit_children'
/usr/local/lib/ruby/gems/2.1.0/gems/sass-3.4.14/lib/sass/tree/visitors/base.rb:38:in `visit'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:131:in `visit'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:142:in `block in visit_children'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:140:in `each'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:140:in `visit_children'
/usr/local/lib/ruby/gems/2.1.0/gems/sass-3.4.14/lib/sass/tree/visitors/base.rb:38:in `visit'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:131:in `visit'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:142:in `block in visit_children'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:140:in `each'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:140:in `visit_children'
/usr/local/lib/ruby/gems/2.1.0/gems/sass-3.4.14/lib/sass/tree/visitors/base.rb:38:in `visit'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:131:in `visit'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:142:in `block in visit_children'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:140:in `each'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:140:in `visit_children'
/usr/local/lib/ruby/gems/2.1.0/gems/sass-3.4.14/lib/sass/tree/visitors/base.rb:38:in `visit'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:131:in `visit'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:142:in `block in visit_children'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:140:in `each'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:140:in `visit_children'
/usr/local/lib/ruby/gems/2.1.0/gems/sass-3.4.14/lib/sass/tree/visitors/base.rb:38:in `visit'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:131:in `visit'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:25:in `run'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/runner.rb:48:in `run_linter'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/runner.rb:29:in `block in find_lints'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/runner.rb:27:in `each'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/runner.rb:27:in `find_lints'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/runner.rb:17:in `block in run'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/runner.rb:16:in `each'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/runner.rb:16:in `run'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/cli.rb:54:in `scan_for_lints'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/cli.rb:48:in `act_on_options'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/cli.rb:27:in `run'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/bin/scss-lint:6:in `<top (required)>'
/usr/local/bin/scss-lint:23:in `load'
/usr/local/bin/scss-lint:23:in `<main>'
Report this bug at https://github.com/brigade/scss-lint/issues

To help fix this issue, please include:
- The above stack trace
- SCSS-Lint version: 0.39.0
- Sass version: 3.4.14
- Ruby version: 2.1.2

even though the refernced scss-lint.yml file has the following settings
exclude:
    - '/**/vendor/**'
    - '/**/node_modules/**'
    - 'node_modules/**'
    - '../node_modules/**'
    - '**/node_modules/**'
    - '*/node_modules/**'

The massive amount of glob patterns were just a test to really make sure it's not a configuration issue on our side. It seems like scss-lint is still scanning the directories it shouldn't want which makes it slower as needed and more importantly cause exceptions.
I've already tried removing everything that is related to ruby (by executing rvm implode) and then re-installed it via rvm again to make sure it's a fresh installation.
Any ideas what I could try in order to fix the issue?

Hey @cH40z-Lord,
The following configuration excludes all files in the node_modules directory from all linters. I've tested it locally with scss-lint 0.39.0 and it works as expected.
exclude:
  - node_modules/**


vision2

[x] Make it easy to ingest the generated image (instead of saving and uploading). Drag-n-drop seems to work, but we removed.
[ ]  Image change in front of UI
[x]  LLaVa endpoint with gradio stream for talk to image in front of UI
[ ] Set Add Doc to Chat default to off until improved.  maybe use accordion in case large text.
[ ] Only generate image once for all_bot(), not super useful to generate for each
[ ] Auto-response when done uploading if adding chat to doc
[ ] Accordion away longer text for adding doc to chat. -- e.g. audio and then make from audio image, then repeats audio text.
[ ] Make models on gradio endpoint
[ ] Round-robin outer gradio since seem to be core limited and saturating that single core.
[ ] remove posthog
[ ] Need to put image stuff as endpoint, either separate gradio or part of llava.
[ ] If text, can add to chat
[x] distil whisper makes obvious mistakes compared to whisper large v3 from porche mp3

https://www.adept.ai/blog/fuyu-8b
OKVQA
Question:
“What instrument is the toy bear playing?”
Fuyu’s answer:
“snare”
OKVQA Score:
0 (all reference answers are simply “drum”)

VQAv2
Question:
“What type of foods are in the image?”
Fuyu’s answer:
“fish, carrots”
VQAv2 Score:
0 (reference answers were “hot dogs”, “sausages”, and “healthy”)

Fuyu’s caption:
“A nighttime view of Big Ben and the Houses of Parliament.”
Reference captions:
“A fast moving image of cars on a busy street with a tower clock in the background.”
“Lit up night traffic is zooming by a clock tower.”
“A city building is brightly lit and a lot of vehicles are driving by.”
“A large clock tower and traffic moving near.”
“there is a large tower with a clock on it.”
CIDEr Score:
0.4 (No reference caption mentions Big Ben or Parliament)

Question:
“Aidan Gillen acted in how many series?”
Fuyu’s answer:
“2”

Question:
“Find missing data of the sequence 24, _ ,32, 33, 42?”
Fuyu’s answer:
“29”

Question:
“What was the fair amount of paid vacation days in the UK?”
Fuyu’s answer:
“28”

Question:
“Which is the metro in California that has a good job Outlook?”
Fuyu’s answer:
“Los Angeles”

Question:
“What was the pack spinner capacity?”
Fuyu’s answer:
“118 packs.”

Question:
“What letter does a keel-shaped cross-section look like?”
Fuyu’s answer:
“The letter V”

Question:
“If in the food web shown in the diagram, Douglas fir tree needles are absent, which organism would starve?”
Fuyu’s answer:
“Red tree vole”

Question:
“is the 2nd email starred? [‘yes’, ‘no’]”
Fuyu’s answer:
“no”

Question:
“is La Taqueria north of the 24th St Mission Bart station?”
Fuyu’s answer:
“no”

According to the table below, which food is the most likely cause of the outbreak of food poisoning:
A. Cold chicken
B. Potato salad
C. Egg sandwiches
D. Fruit pie and cream

B

Answer the following MMMU question based on the image.
Janet Ludlow’s firm requires all its analysts to use a two-stage dividend discount model (DDM) and the capital asset pricing model (CAPM) to value stocks. Using the CAPM and DDM, Ludlow has valued QuickBrush Company at $63 per share. She now must value SmileWhite Corporation. Calculate the required rate of return for SmileWhite by using the information in the following table:

A. 14%
B. 15%
C. 16%
C: 16%
Answer: C

Table 11.47 provides a recent survey of the youngest online entrepreneurs whose net worth is estimated at one million dollars or more. Their ages range from 17 to 30. Each cell in the table illustrates the number of entrepreneurs who correspond to the specific age group and their net worth. We want to know whether the ages and net worth independent. $\chi$^2 test statistic = ______

A. 1.56
B. 1.76
C. 1.96
D. 2.06
B. 1.76
Answer: B

28.01 m/s


fixes TurnerSoftware/Pingalot#10 DivideByZeroException when first ping fails

Created a unit test to cover https://github.com/TurnerSoftware/Pingalot/issues/10
Add in a fix for https://github.com/TurnerSoftware/Pingalot/issues/10
Confirmed unit test fails prior to fix
Confirmed unit test passes after adding fix

Looks good to me! Thanks for contributing!


Implement is new condition for product streams

We need this for one of our customers and I think it will fit in the core.

Hi @FiveDigital, thank you for this PR. At a first glance it looks very promising.
This PR will be tracked with Ticket SW-13929 and is currently scheduled for our next sprint that goes from Feb. 9 to Feb. 19.

Thanks :+1: Let me know if there's anything to fix.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/#/issues/SW-13964.
Please use this issue to track the state of your pull request.

Now there are two tickets for this PR:
https://issues.shopware.com/#/issues/SW-13929
https://issues.shopware.com/#/issues/SW-13964

Good catch, the bot created another one. I removed the duplicate Ticket and updated my comment form yesterday.

Fixed & merged with commit 88c8db1.
Thanks you @FiveDigital.


Is there a convenient way to get dataset with all information?

I need to get a .csv file with maximum amount of information about a game (heroes level, positions, gold, exp, scores, tower status and so on - some kind of game's timestamp) at specific moments of time (each 20 seconds, for example). Is there a convenient way to parse all that information?
It will be used in machine learning project.
Sorry if it is a silly question, I have no experience in Java at all and it is hard for me to figure it out by myself.

Nope, there isn't.
A good way to start would be to look at OpenDota's parser, which is a good example of what you're trying to achieve.


belinda-closet-nextjs_5_279_mission-page-with-route

Resolves #279
This pr is to create a placeholder page for mission and add route to Navbar.

Good afternoon, @JoyZhang2023 . I have tested and can confirm everything works as expected (though my approval is redundant at this point.) Since you have 2 or more approving reviews you can squash and merge this branch into main 👍 Just click on the green button below and then confirm. Git will take a minute to check if everything is copacetic and then it'll commit your changes to the main branch. Don't forget to run a git pull on your local version of the main branch afterwards. 👌


Node 8 util.promisify

TypeScript Version:  2.3.4
Code
import * as fs from 'fs'
import * as util from 'util'

const readdir = util.promisify(fs.readdir)

Expected behavior:
No error
Actual behavior:
Property promisify does not exist on type 'typeof "util"'.
I did a quick search for 'promisify' in typescript's repository and only found references in test files about bluebird.

Duplicate of DefinitelyTyped/DefinitelyTyped#16860.
node.js types are not part of TypeScript itself, they are in the @types/node package.

Oops, thanks!


Support separate custody (including multisig) for validator definition and validator voting

Is your feature request related to a problem? Please describe.
The signing authority which controls the identity of a Penumbra validator is exactly a Penumbra spendkey. In the simplest custody setup (a single software wallet), whichever wallet is used to broadcast a validator definition is also the same spend authority used to authorize that update to the validator.
The protocol does not, however, require this conflation; indeed, the design of the validator system for Penumbra is deliberately made so that a validator operator can practice rigorous separation of concerns: a validator's non-custodial funding streams need not remit funds to addresses controlled by the key which controls the validator definition.
One possibly desirable validator configuration would be separated custody for the validator's funding (from reward streams, and optionally self-delegation) and the validator's identity. Additionally, it should be possible to custody the validator's identity just as securely (or not) as any other Penumbra spend key, with the choice of custody backend (online software wallet, airgapped software wallet, threshold multisig, hardware wallet) informed by the operator's requirements, not by the limitations of client software.
The above affordances are all permitted by the protocol but not the current client tooling. This issue describes a sequence of steps to resolve all of these problems and permit validator identity custody to be as first-class as any other type of custody in the system.
Describe the solution you'd like
In order to close this gap, I propose the following augmentations to the client tooling. Note that none of them require changing any protobuf or RPC definitions in a way that is backwards-incompatible.

The first step is to permit separated signing and broadcasting of validator-related actions:

[x] The command pcli validator definition upload should take an additional argument --signature which should be attached to the validator definition, in place of the default locally-generated signature using this pcli's own custody backend.
[x] A new command pcli validator definition sign should take the same arguments as upload (excepting the new addition above), but instead use the local custody backend to produce a signature for that validator definition and output it to the command line.
[x] The command pcli validator vote should be turned into a subcommand pcli validator vote cast, to make room in the hierarchy of commands for other vote actions.
[x] The command pcli validator vote cast should take an additional argument --signature which should be attached to the validator's vote, in place of the default locally-generated signature using this pcli's own custody backend.
[x] A new command pcli validator vote sign should take the same arguments as cast (excepting the new addition above), but instead use the local custody backend to produce a signature for that vote and output it to the command line.

With the above implemented, validator custody can now function across an airgap.

Now it's time to resolve the longstanding issue in the client tooling that separate governance keys are supported by the protocol but not the client tooling:

[x] The command pcli init should take a new subcommand governance-key which takes the same arguments as the rest of pcli init, but initializes a separated governance subkey and stores it in the pcli configuration alongside the other root key. If there is already a governance key in the configuration, this command should fail. The custody method for the governance key should not need to match the custody method for the spend key.
[x] The commands pcli validator vote cast and pcli validator vote sign should use the configured governance key, if one is present.
[x] The command pcli validator definition template should use the configured governance key, if one is present.

Now both the validator identity and the separate governance key can be custodied separately from the spend authority used to broadcast the transactions, and independently from one other.

Finally, the above setup does not yet permit the validator identity to sign definitions or votes, because the current threshold custody backend does not permit signing anything other than transaction plans. To resolve this, the following:

[ ] The protobuf message penumbra.custody.threshold.v1.CoordinatorRound1 should be augmented to be a "go style enum" by adding the additional fields validator_definition and validator_vote. Its corresponding domain type should be a Rust enum which expects precisely one of those fields to be present.
[ ] The custody RPC penumbra.custody.v1.CustodyService should be augmented with two new RPC methods: AuthorizeValidatorDefinition and AuthorizeValidatorVote, each of which take as input their respective things-to-authorize, as well as the repeated PreAuthorizations, as AuthorizeRequest does, and each of which produce as output a message containing a single crypto.decaf377_rdsa.v1.SpendAuthSignature.
[ ] The SoftKMS custody implementation should be updated to implement these new methods.
[ ] In pcli, the place where previously the SoftKMS spendkey was directly used to produce signatures for these things, instead the custody backend should be requested to produce a signature.
[ ] The threshold custody backend implementation should be enhanced to implement these new methods. This is largely type-directed refactoring starting in the place where the domain type CoordinatorRound1 is made to contain an enum of possible things-to-sign.

Describe alternatives you've considered
The alternative is to not implement this work, or to partially implement it. The above chunks (1-3) are described in dependency order, and I believe also in priority order.

Not doing this prevents any validator from placing their validator identity key — the one thing whose compromise cannot be recovered from, and which cannot be rotated — behind even an airgap, let alone hardware or threshold custody. I think this is important to fix.
Not doing this prevents validators from separating governance keys from their identity key, which means that a validator must choose between higher availability of the governance key vs. higher security of the identity key. I think this is somewhat important to fix, but validators could likely make do.
Not doing this prevents validators from keeping their identity and/or governance keys in threshold custody, which is substantially less cumbersome, error-prone, and vulnerable to catastrophic loss than is an airgap setup. Validators could make do without threshold custody, but it would be highly desirable for them to be able to use it to safeguard their identity key just as effectively and flexibly as they can safeguard their funds.

Additional context
I think this is probably 2–4 days of work: 1–2 days to implement parts (1-2) to permit remote authorization flow, and another 1–2 days to make threshold signing work for validator definitions and validator votes.

On the "go style enum" point, can we change the message to a proto oneof to have proper extensibility in the future? This is sometimes and sometimes not possible without breaking compatibility. The Buf docs have more details. It would be good to use a oneof if possible.


ROX-20783: add GCP credentials manager

Description
Add a credentials manager that watches a secret in the stackrox namespace (stackrox/gcpCloudCredentials) for STS configuration to use in workload identity integrations. If the secret does not exist, the default GCP credential chain is returned. The secret must be provided by users when they intend to use workload identities on non-GKE clusters.
Example STS config:
   "type": "external_account",
   "audience": "//iam.googleapis.com/projects/123456789/locations/global/workloadIdentityPools/test-pool/providers/test-provider",
   "subject_token_type": "urn:ietf:params:oauth:token-type:jwt",
   "token_url": "https://sts.googleapis.com/v1/token",
   "service_account_impersonation_url": "https://iamcredentials.googleapis.com/v1/projects/-/serviceAccounts/fake@stackrox.com:generateAccessToken",
   "credential_source": {
      "file": "/var/run/secrets/openshift/serviceaccount/token",
      "format": {
         "type": "text"
      }
   }

Checklist

[x] Investigated and inspected CI test results
[x] Unit test and regression tests added
[ ] ~Evaluated and added CHANGELOG entry if required~
[ ] ~Determined and documented upgrade steps~
[ ] ~Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)~

If any of these don't apply, please comment below.
Testing Performed
Here I tell how I validated my change
CI
Reminder for reviewers
In addition to reviewing code here, reviewers must also review testing and request further testing in case the
performed one does not seem sufficient. As a reviewer, you must not approve the change until you understand the
performed testing and you are satisfied with it.

Current dependencies on/for this PR:

master

PR #8705

PR #8706   👈

PR #8707

This stack of pull requests is managed by Graphite.

/retest


Need more information when showing ds in phpinfo()

I compiled and installed the package (as described in README.md). Then I checked phpinfo() and I cannot find any details about ds (except it is enabled).

What additional information should it show?

+1
I think showing version info is interesting because the APIs could change. I know that the API is stable... but eventually a 2.0 version will be released with backwards-incompatible changes :p .

I like the version idea. Eg
json

json support => enabled
json version => 1.4.0

Added in 6a4a1d9f221a71eb47b4299983f3f5f667b7768d


[Bitnine Tech Team] - It is not applied property index according to position of condition

Hello, I'm Hyundong working in Bitnine, Korea.
When I execute SELECT clause with condition, It is not applied property index according to position of condition.
When the condition is located in WHERE clause, it doesn't work index scan, just full scan.
But when it is located in vertex, like photo, it works index scan.

I tested in this environment(256GB - server memory)

shared_buffers = 64GB
temp_buffers = 16GB
work_mem = 512MB
maintenance_work_mem = 8GB

GIN indices are not usabale in the WHERE clause (see https://github.com/apache/age/issues/45#issuecomment-1121493128).

@pdpotter
I tried the method in the link you sent, but the index is not applied.(#45)
select create_vlabel('test', 'comment');
CREATE UNIQUE INDEX test_comment_id_idx ON test.comment (properties);

SELECT * FROM cypher('test', $$ EXPLAIN ANALYZE MATCH (v:comment {content: 'thanks'}) RETURN v $$) AS (v agtype);
                                                    QUERY PLAN
------------------------------------------------------------------------------------------------------------------
 Seq Scan on comment v  (cost=0.00..98778.79 rows=2052 width=32) (actual time=0.118..2765.764 rows=85559 loops=1)
   Filter: (properties @> agtype_build_map('content'::text, '"thanks"'::agtype))
   Rows Removed by Filter: 1966610
 Planning Time: 0.642 ms
 Execution Time: 2773.867 ms
(5 rows)

SELECT * FROM cypher('test', $$ EXPLAIN ANALYZE MATCH (v:comment) where v.content = 'thanks' RETURN v $$) AS (v agtype);
                                                                            QUERY PLAN
-------------------------------------------------------------------------------------------------------------------------------------------------------------------
 Seq Scan on comment v  (cost=0.00..109080.68 rows=10261 width=32) (actual time=0.414..9792.321 rows=85559 loops=1)
   Filter: (agtype_access_operator(VARIADIC ARRAY[_agtype_build_vertex(id, _label_name('25129'::oid, id), properties), '"content"'::agtype]) = '"thanks"'::agtype)
   Rows Removed by Filter: 1966610
 Planning Time: 0.130 ms
 Execution Time: 9802.126 ms
(5 rows)

Could you tell me how to execute it works in the WHERE clause as well?

It is currently impossible to make it work in the WHERE clause.
I think there might b a small issue in the code in your previous comment to make the index work in the MATCH clause: I think
CREATE UNIQUE INDEX test_comment_id_idx ON test.comment (properties);

should be
CREATE UNIQUE INDEX test_comment_id_idx ON test.comment USING gin (properties);

Thank you for your reply.
I have one more question, how do I use conditions such as range search using an inequality sign or like search?


Address issue #390, Adjustment types for inventory need to be localized

Fixes #390.
There are two issues, which are related:

Localization of drop-down
Added translation keys to app/mixins/inventory-adjustment-types.js. So now the drop-down list for Adjustment Types is translated. Added English translations. I didn't update the files for the other languages - I'm not sure of the process for getting translation text in multiple languages - let me know if you'd like me to do something more about that.

Localization of the 'submit' button.
In app/inventory/adjust/controller.js I use the the Transaction Type to find a localized Adjustment Type name.

cc @HospitalRun/core-maintainers

@jkleinsc Thanks for the review. I've reorganized the localization values as suggested.

@sweeneydavidj looks good to me.  Thanks for the PR!


tensorflow and terminal issue

PS C:\Users\Shadab\Downloads\Emotion Music Recommendation> & "c:/Users/Shadab/Downloads/Emotion Music Recommendation/env/Scripts/python.exe" "c:/Users/Shadab/Downloads/Emotion Music Recommendation/camera.py"
2023-01-27 18:25:36.599542: I tensorflow/core/platform/cpu_feature_guard.cc:193] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  AVX AVX2
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
This is coming in the terminal
Import "tensorflow.keras.layers" could not be resolvedPylance
is coming

https://stackoverflow.com/questions/58202095/cant-import-tensorflow-keras-in-vs-code/72482851#72482851
Refer this please

"C:\Users\Shadab\Downloads\Emotion Music Recommendation\env\Scripts\python.exe" "C:\Users\Shadab\Downloads\Emotion Music Recommendation\app.py"
2023-01-30 19:13:15.956112: I tensorflow/core/platform/cpu_feature_guard.cc:193] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  AVX AVX2
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
This is coming in the terminal and app is not opening

Hello. Just go back in my commit history to June 2021 and install the versions of packages from the requirements.txt the issue is mostly due changes in newer versions


Give each standard its own URL

As someone interested in a specific standard,
I want to give someone a url to that standard, such as https://acmsigsoft.github.io/EmpiricalStandards/standards/experiment,
so that they can view that standard directly without having to go to https://acmsigsoft.github.io/EmpiricalStandards/docs/ and choose from a list.

Does it necessarily need to be separate pages (e.g., "docs/CaseStudy")?
It is simpler to make it as a parameter assigned to the same page (e.g., "docs?standard=CaseStudy").

Either would be fine. docs/CaseStudy would be marginally better from a usability perspective, but if docs?standard=CaseStudy is significantly easier to implement, it's ok.

Right. I suggested doing it like "docs?standard=CaseStudy" to keep all on the same page. Doing it like "docs/CaseStudy" would require creating additional separate pages for each standard in which we markdownify the contents.

I've implemented it like "docs?standard=CaseStudy". Please check it out. Thanks.

I've implemented it like "docs?standard=CaseStudy". Please check it out. Thanks.

Looks good to me.


Replace CppUnit with GoogleTest in AX tests

This is a work-in-progress pull request. I've begun by adding GoogleTest to the AX unit test runner and am currently running both the existing CppUnit test suite as well as any added GoogleTest tests. The intention is to migrate the test cases one-by-one and then remove CppUnit completely afterwards.
Resolves https://github.com/AcademySoftwareFoundation/openvdb/issues/1917

These changes are ready for review. I've completely removed CppUnit from the AX tests but it remains a dependency at the top level. I think I'll put in a second pull request to remove it there as well, separately from this one.
@Idclip @richhones @danrbailey

I've created a secondary branch off of this one that further removes all mentions of CppUnit from the build dependencies and instructions. Shall I create a merge request into this branch, wait until this is merged, or just push the changes to this branch?
https://github.com/tstraubinger/openvdb/tree/feature/remove_cppunit

I've created a secondary branch off of this one that further removes all mentions of CppUnit from the build dependencies and instructions. Shall I create a merge request into this branch, wait until this is merged, or just push the changes to this branch? https://github.com/tstraubinger/openvdb/tree/feature/remove_cppunit

Thanks, I'm fine to have these changes in this branch as they're all closely related. I've just approved the CI running, but note there are some conflicts, so this branch likely needs to be updated and the conflicts resolved which may affect the result of the CI.


fix(ui): remove lodash _ all

clean up complete
Closes #15694
Describe your proposed changes here.

[ ] CHANGELOG.md updated with a link to the PR (not the Issue)
[ ] Well-formatted commit messages
[ ] Rebased/mergeable
[ ] Tests pass
[ ] http/swagger.yml updated (if modified Go structs or API)
[ ] Documentation updated or issue created (provide link to issue/pr)
[ ] Signed CLA (if not already signed)

I wonder if we should incorporate this eslint-plugin so enforce these import changes so that future developers don't undo all this hard work:
https://github.com/wix/eslint-plugin-lodash

This issue is going on hold for now, to be addressed at a later time when we have the ability to solve some of its issues.

@zoesteinkamp should we close this?

Since we are now using the UI assets from the ui repository (#21090), I am closing this PR!


Changing messages comments/descriptions affects protocol version

Here is what protocol version calculator should take into account:

Msgs IDs and names
Order of msgs fields and their types
Fields names (e.g. changing single field name from "uint32 capacity_liters" to "uint32 capacity_ml" must change the hash)

Fields comments and message descriptions must not affect protocol version

Reverted pull request as it did not consider swapping two consecutive data with same size


KOGITO-3563 Force Process definition beans to created once Quarkus ap…

…p starts

@Sgitario I'm not sure really how I could reliably test that ( app does not start without Infinispan connection ), open to suggestions :)


Buffer writes for latency

Right we provide strong durability. We can relax this by returning to clients early and then trying to write to S3

hi avinash, if we return to cilents early how would we return the offset back to client ? rn we return offset to client by returning offset from Append func.

let me know incase of any clarification, i'm interested to contribute.

hey @mrmagicpotato007 ! thanks for showing interest.
I am still thinking about the API. I would first solve https://github.com/avinassh/s3-log/issues/11 then allow concurrent goroutines to call Append.
the question I am pondering is, do all the successful callers get same Offset?  Now application layer needs to be aware of this and I still thinking if this is a good idea or not

You may really want to batch writes into a single object. With a key per record, you are moving your cost towards consumers. Not just $$ cost of GET API's but even latency of invoking a GET per record/key ( which will quickly add up. unfortunately S3 doesn't support Batch GET to amortize the cost )

@fhalde all are valid concerns. Buffering / batching solves these, to some extent

@avinassh  Lets say, u returns unique offest early to all the callers ,before putting those in s3. what about the data in the local buffer if application crashes ? (introducing the risk of data loss) Is there any plan for that ?

@avinassh Lets say, u returns unique offest early to all the callers ,before putting those in s3. what about the data in the local buffer if application crashes ? (introducing the risk of data loss) Is there any plan for that ?

The idea is to make library handle multiple Insert requests, combine them and insert them in S3. Only then it can return the unique offset to the caller, not before.

What do u mean early return here?