Allow Vault CR service to use run on a different port than the pod API

Is your feature request related to a problem? Please describe.
I cannot configure Vault CR to create a service available under port 443 pointing to the pod API on a different port.
Vault per default exposes its HTTPS endpoint under port 8200.
The k8s service I like to create would need to look like this:
spec:
 ports:
 - name: api-port
   port: 443
   protocol: TCP
   targetPort: 8200
 - name: metrics
   port: 9091
   protocol: TCP
   targetPort: 9091
 - name: statsd
   port: 9102
   protocol: TCP
   targetPort: 9102
 selector:
   app.kubernetes.io/name: vault

With the fields available in the Vault CR I can define:
  servicePorts:
    api-port: 8200
    external-port: 443

But the resulting k8s svc only provides:
spec:
 ports:
 - name: api-port
   port: 8200
   protocol: TCP
   targetPort: 8200
 - name: external-port
   port: 443
   protocol: TCP
   targetPort: 443
 - name: metrics
   port: 9091
   protocol: TCP
   targetPort: 9091
 - name: statsd
   port: 9102
   protocol: TCP
   targetPort: 9102
 selector:
   app.kubernetes.io/name: vault

The Vault pods also do not start if they are configured to run the API directly on port 443 (probably does make sense):
Error initializing listener of type tcp: listen tcp4 <IP_ADDRESS>:443: bind: permission denied
2021-05-19T15:18:14.067Z [INFO]  proxy environment: http_proxy= https_proxy= no_proxy=

Describe the solution you'd like
The CR should support configuration like:
  servicePorts:
    api-port:
      port: 8200
      targetPort: 443

Describe alternatives you've considered
Until this is supported I do not use the Vault Service created from the CR and create another one next to it.
Thanks for looking into this!

Second that Vault should be possible to access on the default ports like 80/443

I am wondering... Which problem does this solve? Just an aesthetic one -- that the URL does not need to specify the port :8200? Or am I missing something?

Couple of policy reasons and requirements that come into play.
First we can safely say there is no benefit in running at a high port, it causes human confusion and requires documentation overhead deviating from the standards.
Nevertheless, in our company the firewall policy does not permit other random high ports for http/https for firewall rules zone transitions other than the approved default ports. So kind of a hard requirement, and we don't want to treat access differently whether it's in- or cluster external.


circle: pin to<EMAIL_ADDRESS>

Tests in latest docker image circleci/node:6.13.1-browsers fail with
error:
/home/circleci/falcon/node_modules/electron/dist/electron:
error while loading shared libraries:
libgconf-2.so.4:
cannot open shared object file:
No such file or directory

hi @tarzzz , please, could you review this PR?

💃
I also faced a similar error earlier (in a different repo though). One way to fix it is to install libgconf-2-4 in Dockerfile (using apt-get) .. Mentioning this in case we need to upgrade in future.. (to 6.13.1 or later versions)

Goot to know (thanks!)


Remove module field in production webpack config

This crops up in the form of uglify errors during a production build, e.g. #2236, #2433, #2475. The suggestion there is to transpile deps down to ES5 and/or remove module. This is correct with respect to main, however module is there specifically to indicate ES module support, which uglify doesn't support. Therefore, ask webpack not to resolve it.
You can test this by depending on a package that ships with multiple targets i.e. main pointing to a transpiled/common JS target and module targeting ES6+, e.g. tlvince-reduced-test-case-cra-module:
src/index.js
import test from 'tlvince-reduced-test-case-cra-module'
test()

Before:
> react-scripts build

Creating an optimized production build...

Failed to compile.

static/js/main.1b21038d.js from UglifyJs
Unexpected token: punc (}) [./~/tlvince-reduced-test-case-cra-module/dist/tlvince-reduced-test-case-cra-module.es.js:1,14][static/js/main.1b21038d.js:79667,19]

After:
> react-scripts build

Creating an optimized production build...
Compiled successfully.

We encourage the use of module as it should contain code which is just that -- modules. Code is supposed to be compiled down to the target ES version (in any package that supports a browser environment, ES5 or older).
Those issues you referred to are unfortunately caused by improper package publishing.
Packages shipping code which requires compilation should be using the esnext field, not the module field.
Please refer to the module field specification. Also see the lengthy discussion in https://github.com/webpack/webpack/issues/1979.

While we greatly appreciate your contribution, this is not something we will be merging.
I look forward to contributions from you in the future!

For clarification, the issue isn't with modules; it's because the packages contain ES6 function syntax/object syntax, e.g. () => {} and:
let a = 5;
let b = { a };

Thanks! That and rollup wiki's pkg.module cleared it up for me.


Send logs after support bundle collection

Send logs after support bundle collection so its possible to get the s3 url from the logs.

This shooould already be handled by the "upload logs of completed runs" code, but that's got a lot of lag

[sc-59261]


When discovering iOS devices: ProcessException: Resource temporarily unavailable

As of today (8/20), on 3.24.0: 221 reports from 102 unique clients (top 20ish crasher)
From flutter commands (looking at first 20 reports): flutter daemon
ProcessException: Resource temporarily unavailable  Command: /usr/bin/xcrun simctl list devices booted iOS --json
at _ProcessImpl._start(process_patch.dart:402)
at Process.start(process_patch.dart:38)
at _runNonInteractiveProcess(process_patch.dart:579)
at Process.run(process_patch.dart:49)
at LocalProcessManager.run(local_process_manager.dart:72)
at ErrorHandlingProcessManager.run.<anonymous closure>(error_handling_io.dart:669)
at _run(error_handling_io.dart:564)
at ErrorHandlingProcessManager.run(error_handling_io.dart:668)
at _DefaultProcessUtils.run(process.dart:312)
at SimControl._listBootedDevices(simulators.dart:162)
at SimControl.getConnectedDevices(simulators.dart:187)
at IOSSimulatorUtils.getAttachedDevices(simulators.dart:75)
at IOSSimulators.pollingGetDevices(simulators.dart:49)
at PollingDeviceDiscovery._initTimer.<anonymous closure>(device.dart:498)
at _rootRun(zone.dart:1391)
at _CustomZone.run(zone.dart:1301)
at _CustomZone.runGuarded(zone.dart:1209)
at _CustomZone.bindCallbackGuarded.<anonymous closure>(zone.dart:1249)
at _rootRun(zone.dart:1399)
at _CustomZone.run(zone.dart:1301)
at _CustomZone.bindCallback.<anonymous closure>(zone.dart:1233)
at Timer._createTimer.<anonymous closure>(timer_patch.dart:18)
at _Timer._runTimers(timer_impl.dart:398)
at _Timer._handleMessage(timer_impl.dart:429)
at _RawReceivePort._handleMessage(isolate_patch.dart:184)

ErrorHandlingProcessManager could handle this error code more generically and suggest the command be run again?

ErrorHandlingProcessManager could handle this error code more generically and suggest the command be run again?

Doing some research around what Resource temporarily unavailable actually means, I think this is a good suggestion.

I actually don't see this crash on 3.24.1? I might need to find a way to search the internal tool by GitHub issue ID

https://github.com/flutter/flutter/pull/154306 seems like a fine change, though I don't think it's the right fix for this.  I think when devices are being discovered, if there's an error when getting the simulators (even a "temp" error) then the right thing would be to skip the simulators, not tool exit.
It looks like there may just be a missing check to see if the simulator command line is working:
https://github.com/flutter/flutter/blob/55af75d57bc702d2cbd43ceaf2d5fd71c8f85d74/packages/flutter_tools/lib/src/ios/simulators.dart#L186-L187
+   if (!_xcode.isSimctlInstalled) {
+     return <BootedSimDevice>[];
+   }
    final Map<String, Object?> devicesSection = await _listBootedDevices();

isSimctlInstalled will catch process errors:
https://github.com/flutter/flutter/blob/55af75d57bc702d2cbd43ceaf2d5fd71c8f85d74/packages/flutter_tools/lib/src/macos/xcode.dart#L189-L191

#154306 seems like a fine change, though I don't think it's the right fix for this. I think when devices are being discovered, if there's an error when getting the simulators (even a "temp" error) then the right thing would be to skip the simulators, not tool exit.

Makes sense. However, if we skip a discovery step for any reason, we should tell the user. Every now and then, users file issues in the class of "flutter won't discover my device", and these are very difficult to troubleshoot (many things can go wrong, high likelihood of user error, etc.).


share initial gee assets on AssetSelect widget

While testing AssetSelect performance, I noticed that it was taking way too long to load the component, and it is because of two reasons:

the component requests all the user assets by calling a recursive function, this is good, but when the user has several folders, the process takes more time.

the component observes the types traitlet with the decorator, this causes a double call of the _get_items() function:

the first happens at the initialization stage with _get_items and the second happens when the type trait changes from empty to the default, that can easily be fixed if we observe at the init function instead of using the decorator.

finally, the problem is even worst if we create apps with more than one AssetSelect component, since it will do the same operation several times.

this is also related to: https://github.com/openforis/sepal_ui/issues/455

closed by https://github.com/openforis/sepal_ui/pull/932


Revert "Restore state on call error"

Reverts grpc/grpc#27899
Reason for revert - The PR has caused continuous build failures on master.

Example failures caused by the original PR:
https://source.cloud.google.com/results/invocations/d56ddb58-18c3-41d2-9a45-5c12d3963ecd
https://source.cloud.google.com/results/invocations/9d0f7d31-ba04-40e1-adb7-7efe6ac2751b
https://source.cloud.google.com/results/invocations/ff8cd804-0c1f-4265-a3e3-f0b2ae71d82a
(and possibly more)


[AKS] Fix apiServerAccessProfile when updating --api-server-authorized-ip-ranges

History Notes:
(Fill in the following template if multiple notes are needed, otherwise PR title will be used for history note.)
[AKS] Fix apiServerAccessProfile when updating --api-server-authorized-ip-ranges

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

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

[x] I adhere to the Command Guidelines.

Fixes #12587

/assign @yonzhan @zqingqing1

add to S167

hi @feiskyer  could you pls fix the CI failure?

@yungezz The error message shows it needs 'az login' and I found there are a lot of credentials in test recordings files. Why do we need to commit the credentials in the opensource project?

Let's see whether the tests could pass without test recording files.

CI passed with faked credentials. PTAL @qwordy @yungezz


Example code cannot run

Environment: hub.baidubce.com/paddlepaddle/paddle:2.0.0rc1
I tried to run example code in https://github.com/PaddlePaddle/FleetX/tree/develop/examples/wide_and_deep.
Got the import error in train.py:
ImportError: No module named 'paddle.distributed.fleet.utils.ps_util'

Am I supposed to run the code with 2.0.0rc1?
Also, the code is different from the code in the doc https://fleet-x.readthedocs.io/paddle_fleet_rst/parameter_server/ps_quick_start.html, but according to the doc, they should be the same. I have also tried to run the code in the doc, but it doesn't work with the model.py in the repo.

2.0rc1后对paddle.distributed.fleet.base.util_factory进行修改，paddle.distributed.fleet.utils.ps_util不兼容2.0rc1，可将2.0rc1包替换为develop包进行训练，paddlepaddle develop包下载地址：
https://www.paddlepaddle.org.cn/documentation/docs/zh/develop/install/Tables.html

2.0rc1后对paddle.distributed.fleet.base.util_factory进行修改，paddle.distributed.fleet.utils.ps_util不兼容2.0rc1，可将2.0rc1包替换为develop包进行训练，paddlepaddle develop包下载地址：
https://www.paddlepaddle.org.cn/documentation/docs/zh/develop/install/Tables.html

换成develop后解决了
(以及现在文档里的代码因为依赖repo里的model.py所以并不工作

换成develop后解决了
(以及现在文档里的代码因为依赖repo里的model.py所以并不工作


drake_bazel_installed: Add import_all_test canary

This will show any issues related to #154

This change is

nice.  thanks.  (and I see it failed as expected)


Initial image

This is a pull request with a setup for an initial image. It hasn't yet been confirmed working but contains most of the scaffolding needed. This pull request will be merged so others can begin to work upon the image. Any issues will be addressed and fixed forward.

Working on #2 as an alternative to producing images this way.

Closing in favour of #2.


DateTime culture

Im HA settings are set correctly -

But the date format is month/ day/ year, rather than day/ month /year -

Checked the code, not sure why its not picking up the culture home assistant is set too, maybe its not set correctly for .net to pick it up -https://github.com/lavinir/hassio-onedrive-backup/blob/f1a2973847e00c95653c5f0a8447b33b9c428088/onedrive-backup/Shared/BackupCard.razor#L45C91-L45C102

Because the addons are running in an isolated container, the culture settings do not apply automatically from the host.
I've looked for a way to retrieve the culture from Home Assistant but did not find anything that exposes this in the Supervisor API.  (Except getting the set timezone).
I'm considering adding this to the settings so users would be able to set this themselves though..


Ability to provide more fine-grained cluster updates

Currently during delivering updates to the cluster with kube-aws update all cluster is getting redeployed starting from Etcd nodes.
When I want to deliver some simple update to worker nodes it is quite an overhead.
I would like to have ability to perform updates to worker nodes only, preferably to target worker pool.

Uhm, just now kube-aws did exactly what i wanted - provided update to worker nodes only when i did only worker related changes. Can local gurus point me to a code responsible for that ? :)

I've seen this in cases where I don't specify the amiId parameter.
When unspecified, kube-aws will check which is the latest AMI for the given release channel and use that in the upgrade. If the AMI currently in use by your instances don't happen to be the latest one, all your nodes are going to be updated.
That's why I personally keep the AMI ID fixed in my cluster.yaml.

Thanks a lot for the hint!

@danielfm @ytsarev Ah, good point!
Perhaps kube-aws would better fill the latest AMI ID into amiId at the time of writing cluster.yaml?

Perhaps kube-aws would better fill the latest AMI ID into amiId at the time of writing cluster.yaml?

May I ask for a render commandline switch to retain previous behaviour? Otherwise it is going to cause constant merge conflicts :(
use of coreos channels works best for us,  because coreos built in autoupgrade doesn’t work well with Kubernetes and ASG, so periodically running kube-awe update is our way t keep up with security updates

@redbaron what is your schedule for running updates ?

hey @ytsarev, I worked with redbaron - updates are sporadic right now - we roll when there are new features we'd like to introduce. But the goal for our automation would be a daily roll - we're getting good feedback from developers consuming our clusters when we roll often as it helps them stay focused/aware of involuntary (on their part) cluster disruptions.
Sorry for the lateness of this answer - just browsing issues and saw this.

@tyrannasaurusbanks sounds good, thanks!


Jinja filter_values function not working in charts used as annotation in another chart

Expected results
the filter_values function should work in a datasource query used in a chart, even if the chart is used as a annotation chart
Actual results
if a chart is used as a annotation in another chart, the filter_values function used inside the datasource query doesn't work, it doesn't return any value. Important to note: a filter value is selected in the dashboard.
How to reproduce the bug

Create a line chart to be used as a annotation in another chart. The datasource query should use the filter_values function
Create another line chart, add the previosly created line chart as a annotation
Add the line chart created in the previous step in a dashboard, add a filter box with the same field used as a parameter in the filter_values of the Step 1
The annotation doesn't show up as expected

Environment

superset version: superset version
Superset 0.37.0:
Python 3.6.9
Flask 1.1.2
Werkzeug 1.0.1
python version: python --version
Python: 3.6.9
node.js version: node -v
node: v12.10.0
npm version: npm -v
npm: 6.10.3

Checklist
Make sure these boxes are checked before submitting your issue - thank you!

[X] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[X] I have reproduced the issue with at least the latest released version of superset.
[X] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
I changed the following the line if (!isDashboardRequest && fd) { (line 254) in chartAction.js to if (fd !== null) { and it solved the problem but I'm not sure about the impact in other behaviours

@oashton , does this change fix the behaviour in explore chart mode for you? Do you know how to change this?
Considering your question on the impact, it seems  (#10115) this behaviour was chosen on purpose.
I did not get the point of  having no control on annotation.
For me if you want to avoid this problem  (mentioned in #10115)
" This will cause chart and annotation layer both have same query, so we can't compare filtered data vs original annotation layer."
You can simply create a new view/table for this annotation using fields name different from the ones you use in your filters.
@graceguo-supercat Any clue on this? Thank you

@lilila , it doesn't work in explore mode, right now I don't know how to change it.
Thanks for the reference to the issue #10115... so the behaviour is by design.
I agree with you, I don't get why lose the possibility to add dynamic behaviours to the annotation. Let's see what @graceguo-supercat says about this.
cc @camilo-uptime, check this thread, this is why we weren't receiving the filter values in the annotations line chart

Dear @oashton ,
I wrote this lite patch to get annotation considering extra_filters in Explore view as well.
I add these lines at line 260 in your screenshot
    //case for explore view (have extra params given to annotation)            var new_extra_from_adhoc = [];     if (!fd.extra_filters && fd.adhoc_filters){         for(var i=0; i<fd.adhoc_filters.length; i++){             if (fd.adhoc_filters[i]['isExtra']){                     var new_extra = {"col":fd.adhoc_filters[i]['subject'],                                      "op": fd.adhoc_filters[i]['operator'],                                      "val": fd.adhoc_filters[i]['comparator']};                     new_extra_from_adhoc.push(new_extra);}             }         sliceFormData.extra_filters = new_extra_from_adhoc;     }
@villebro , I don't know if you remember but we discussed this point.
The problem was that in explore mode, extra_filters are already merge with adhoc filters so they were not passed to the annotations. The code snippet (sorry for the quality I never code in Javascript) simply recreates the extra_filters from the adhoc_filters available in Explore mode

Over the holidays I'll try to take a look at how this could be properly integrated into the annotation requests.

@oashton Have you tried the patch I proposed few months ago?
I have it and it is not causing any collateral problem.
By any chance, do you have a solution for native filters to be considered in Annotations ? :o

Does anyone know if this issue is still an issue? Tempted to close it, since we no longer support any of the 0.x.x releases.

Assuming we're all good by now and the patch worked. Closing, but happy to revisit!


Define number of parallel threads

Have a way to specify number of parallel threads that the user can run and have a default

GOMAXPROCS variable
https://golang.org/pkg/runtime/
https://docs.google.com/document/d/1At2Ls5_fhJQ59kDK2DFVhFu3g5mATSXqqV5QrxinasI/edit


The select stack frame lost focus after "Load more stack frames"

VSCode Version: 1.1
OS Version: Windows10, Ubuntu 14.04

Steps to Reproduce:

Select a stack frame and click "Load more stack frames"
The original selected frame will lose it's focus/highlight, it's hard to figure out which frame is currently selected

Setting to may to investigate


Doesn't seem to work with plain-text class names?

I updated my import map to match the twind version used in this code repo and use the plugin in place of the official one.
tw.target seems to not pick up anything in plain-text class names. I currently have to wrap them all in tw().

I think we're missing this https://github.com/denoland/fresh/blob/1b3c9f2569c5d56a6d37c366cb5940f26b7e131e/plugins/twind/shared.ts#L30

I think you're right. Unfortunately, that setup depends on hydration which I haven't figured out yet (see #1).
It may be a while before I find time to figure out how to get Twind v1 snapshots to work with Fresh. If you have more knowledge or time than me, you're welcome to take a crack at it!

Freshwind 3.0.0-beta should fix this issue

I tried 3.0.0, which seems to work but besides the duplicate styles you mention in #4, I also see an ugly flash when the page first loads and the styles have not been loaded.
That behavior can be consistently observed here: https://fresh-flowbite.deno.dev/
The source code for that demo site is here: https://github.com/khuongduybui/fresh-flowbite-site

Thanks for pointing out the flash. I'm going to close this issue for now, and open up a separate issue for the flash.

@khuongduybui, the flashing should be fixed in Freshwind 4.0.0. I was able to replicate the issue running your test site locally (thanks for sharing that by the way). And I was able to confirm that it's fixed locally.
There are some breaking changes (hence the major version change). I've added a usage section to the readme that should make it pretty straightforward to upgrade.

I'm glad you figured it out! Thanks for the quick investigation. I planned to give it a look tomorrow but since you got it already I will wait to see the PR!


Can't seem to scroll down to buttons in Genotype Builder window

As described in title. Reproduced on Safari and Chrome in macOS. There doesn't seem to be a way to reach the buttons at all. This is as far as I get:

Thanks for reporting.  I confirmed the issue and it will be fixed today.

Resolved in current version.


JSON::Schema::SchemaError: Schema not found

I'm trying to validate a JSON payload that should conform to this schema but I can't get past this error:
#<JSON::Schema::SchemaError: Schema not found: http://json-schema.org/schema#>

I feel like I've tried everything but I must be missing something. I tried to tweak JSON::Validator.schema_reader so it would accept a URI and fetch the document from the Internet. I also tried staging the schema on disk ahead of time, parsing it, and adding it with JSON::Validator.add_schema and the http://json-schema.org/schema# URL. I've tried with/without :strict, :validate_schema, :json, etc. Any suggestions?

It seems support for version 1.0 final of the spec isn't ready yet, try with the default version of the spec, which is "$schema": "http://json-schema.org/draft-04/schema#".
I've tried with both and got the same error as you with the final 1.0 version of the spec; the last draft worked properly though.

I get the same error when using http://interagent.github.io/interagent-hyper-schema#. Is it actually fetching the schema from the Internet, or just locally?

I had the same problem, but turns out it was related to a custom extension that didn't have a properly registered validator to it's url. The error description was misleading on validator.rb:346. It's looking for a validator for a given uri and when that validator is not found it raises a Schema not found error.
If any of you are using schema extensions, I think checking this is worth a shot.


Fix ENV variable append to resolve build failure

This request is to change an environment variable's append directive to support newer syntax to resolve a build failure.

Thank you!
To be honest, I don't know if I'll ever find time to try to finish this thing, but at least it won't give problems to anyone :)


Enable jump to source in docs

Hi,
This enables jumping to the source code in the docs.
wdyt
example of [source] link:

I use this option in dnspython and think this is a nice thing.


Unable to add a validator to an arg from a subcommand using YAML

Hi,
I am not able to make my validator work with an argument attached to a subcommand. I would like to attach a validator to something I declared in my YAML file.
Rust Version
rustc 1.17.0 (56124baa9 2017-04-24)
Affected Version of clap
clap 2.23.2
Expected Behavior Summary
Validator error should be thrown when my argument is not valid
Actual Behavior Summary
When I run the code my argument is treated as valid even though it is not
Sample Code or Link to Sample Code
My cli.yml file:
name: blabla
version: "0.0.4"
author: blabla
about: blabla

settings:
    - ColorAlways
    - ColoredHelp
    - VersionlessSubcommands
    - DisableHelpSubcommand
    - DeriveDisplayOrder
    - SubcommandRequiredElseHelp

args:
    - format:
        help: blabla
        global: true
        possible_values: [json, csv]
        short: f
        long: format
        takes_value: true

subcommands:
    - info:
        about: blabla
    - firmware-update:
        about: blabla
        args:
          - firmware-file-path:
              help: blala
              required: true
              takes_value: true

My main.rs file:
let yaml = load_yaml!("cli.yml");
let cli = App::from_yaml(yaml);
let cli_with_validators = cli.subcommand(SubCommand::with_name("firmware-update").arg(Arg::with_name("firmware-file-path").validator(validate_firmware_file_path)));
let matches = cli_with_validators.get_matches();

fn validate_firmware_file_path(file_path: String) -> Result<(), String> {
  let path = Path::new(&file_path);

  if path.starts_with("bla") && path.ends_with(".bla") {
    return Ok(());
  } else {
    return Err(String::from("Firmware file name is not valid."));
  }
}

Thanks !

Thanks for the details and taking the time to file this! This is a known issue, but the workaround is decently simply. Any args which contain validators, will need to be defined in the Rust source.
I'm actively working on a solution to allow mutating args once they've been added which will solve this particular issue.

@kbknapp Great ! Thank you :)


The c++ multiplication modular P does not produce correct result.

The function mul in risc0/zkp/core/fp.h for multiplying two uint32_t integers modular P=15*(2^27)+1 does not produce correct result. As a very simple example, when the input a and b have product 2^32, this function returns 1, while 2^32 modular P is not 1.
https://github.com/risc0/risc0/blob/54eca8d513cecc83f75bdb781376da0c25a220b0/risc0/zkp/core/fp.h#L73

Oh, the inputs are encoded. Didn't notice that.


Empty output on circular dependencies

After updating from 0.13.* to 0.14.* build began producing empty output without any error indications.
I narrowed it down to circular dependencies. I use es6 modules and babel, config below
var builder = new Builder({
	baseURL     : "./src/main/js",
	transpiler  : 'babel',
	babelOptions: {
		modules  : 'es6',
		blacklist: [],
		comments : false
	}
});

builder
	.build('fail.js', 'fail-bundle.js', {minify: true, sourceMaps: true})
	.then(function () {
		console.log('Build complete');
	})
	.catch(function (err) {
		console.log('Build error');
		console.log(err);
	});

File contents:
fail.js:
import "fail2.js";
console.log("fail"); // just anything to have some code

fail2.js:
import "fail.js";

fail-bundle.js (output):

//# sourceMappingURL=fail-bundle.js.map

Also tried with export and default export, same result. Staying with 0.13 for now

Odd, this works for me fine. If you add an output argument to your build, perhaps check the contents of output.modules, output.trace and output.source to see where the issue is? If the trace sources look ok, try removing your custom babelOptions?

I re-checked and I have this issue in 0.14.8 (and I did in 0.14.0 so probably anything in between too) but 0.14.9 seems to work fine. But it wouldn't hurt to investigate to prevent regression.
I tried printing the whole output to console, here's what I get (0.14.8):
{ source: '',
  sourceMap: { add: [Function: add], get: [Function], toString: [Function] },
  modules: [ 'fail.js', 'fail2.js' ],
  entryPoints: [],
  tree:
   { 'fail.js':
      { name: 'fail.js',
        path: 'fail.js',
        metadata: [Object],
        deps: [Object],
        depMap: [Object],
        source: 'import "fail2.js";\r\nconsole.log("fail"); // just anything to have some code',
        runtimePlugin: null },
     'fail2.js':
      { name: 'fail2.js',
        path: 'fail2.js',
        metadata: [Object],
        deps: [Object],
        depMap: [Object],
        source: 'import "fail.js";',
        runtimePlugin: null } } }

I removed not just babelOptions, but everything except baseURL, as well as minification options, still the same. I should have mentioned I used babel-core 5.8.25 in all builds, which is latest on npm.

Update: I in fact still have this problem on 0.14.9 with prod build.

This could be due to the missing entryPoints entry. Are you still getting the error when entryPoints is populated?

Huh?
What are those entry points in the first place? Am I missing something in my config? I ran to docs after reading your comment, but I can't quite find anything about specifying entry points manually.

@enlait in your previous comment you showed two examples - one with and one without entrypoints in the list. This array is generated internally - you don't need to specify it, but I just wanted to know if your failing case has entrypoints as an empty array? An empty entrypoints array would definitely mean the build would output nothing.

These two outputs are for the same minimalistic test case from the first comment, with 2 files importing each other (this is important part, without circular dependency everything's fine).
First output is for systemjs-builder 0.14.8 and second is for 0.14.9. As you can see, build fails in 0.14.8, and works for 0.14.9.
In my real project build also results in empty output using 0.14.9, but to be honest I didn't check if entryPoints array is empty - will do tomorrow. I suspect it is, since symptoms are the same.
Why 0.14.8 when 0.14.9 is out: if you didn't fix anything related to dependency resolution in 0.14.9, I speculate that it's the same bug, and it would be simpler to find it in 0.14.8, since it fails on just two files. Of course no sooner than you can reproduce the issue.

Played with test sources a bit, and have one more observation: build fails only if an entry point (that is, the js file from which I start making bundle via builder.bundle / builder.build) is part of dependency loop.
For example A.js imports B.js, B.js imports C.js, C.js imports A.js - builder.build("A.js") results in empty entryPoints . If B imports C and C imports B, but neither imports A then build succeeds.
This is true for 0.14.8.

Soo, disregard my doubts above, the bug is definitely there in 0.14.9 too.
Builder produces empty output on this input: https://gist.github.com/enlait/30266c703e551df8a627
The difference between 0.14.8 and 0.14.9 is that 0.14.8 fails on dependency loop of size 2, whereas 0.14.9 doesn't; but both fail with bigger loops.

@enlait thanks. I assume out.entryPoints.length == 0 in that case as well. The entry point detection does struggle with circular references - I will look into this.

Thanks, fixed in https://github.com/systemjs/builder/commit/d82be245c53c631213c703ae350094d96ee0a76b.

//cc @Munter the above commit changes the build order from post-order to reverse pre-order in order to handle the detection of circular entry points, but this should still provide the correct dependency execution order for your use cases.

Ok. I'll see if I run into any hardships when I get the build runtime up

Released in 0.14.10.


How to keep material not lose ?

Such as,
Object A substract Object B, what's result about original material?

What do you mean original material? Do you mean the texture that's on the object?


Tags on Account gets removed when page gets refreshed.

To Reproduce
Steps to reproduce the behavior:

Go to 'Account List Page'
Expand any Account.
Add Tag
Now, Refresh that page.

Live pe tag ke liye kya role chahiye?
Role ka issue he

Advance Role ke bad barobar kar raha he
so ither humko design change karna hoga ya fir Role

Advance role ON ho ya Off, mein usi Accounts pe tag add kar pa rha hu jisme mein hu...

Now, advance role ON ho ya Off sare Account pe tag add kar pa rha hu...

#258


CDM Android Agent code cleanup

Cleaning up and formatting the CDM Android Agent code.

Fixed above issues.

Fixes for issues reported on 24/03/15 are done.

Added fixes.

Adding fixes to the above.

Added one more fix to progress dialog context.


Rustup

@bors r+

:pushpin: Commit 6cbb540150f846d49633006c45d4e5cb837375bf has been approved by RalfJung
It is now in the queue for this repository.

:hourglass: Testing commit 6cbb540150f846d49633006c45d4e5cb837375bf with merge cf4c0d1ae460506604fd1997e563f300f8d6074d...

:broken_heart: Test failed - checks-actions

:pushpin: Commit a1aed159d181282b9e93b974103745b2dd2bfa45 has been approved by RalfJung
It is now in the queue for this repository.

:hourglass: Testing commit a1aed159d181282b9e93b974103745b2dd2bfa45 with merge 25d6cd1c4ecb524b54d89ebbe8b1374a5fa93516...

:sunny: Test successful - checks-actions
Approved by: RalfJung
Pushing 25d6cd1c4ecb524b54d89ebbe8b1374a5fa93516 to master...


Parse redirected page

How to parse redirected page such as ISOHUNT, the download button and magnet buttons are on detail page, there are no download button / magnet button on search result page.

if you don't need all the torrents links, try to override the download method like 1337x and zetorrents providers.
If you really need all the torrents links override the search method to add a step where you fetch each torrent detail page and get all the download links one by one.

Using _downloadTorrent callback ?

Yes

hmm, but the link doesn't show on search request

No, if you want the links on the search request, you have to override the search method and add a loop to fetch all the torrents details pages and get the download link.

Oh okay, I will try that later. Thanks


Setting node priority and disabling load balancer

I have on-prem deployments and I want to provide High availability for my applications and DB. I'm deploying applications in a swarm but I don't want the swarm to load balance multiple instances. Rather, I want the swarm to always connect to a node with the highest priority (which could be set during deployment/swarm creation). If that node ever goes down, then it should connect all incoming requests to the next higher priority node.
I want to have multiple nodes as backups only. Is it possible in the current swarm?
If not, can this be implemented as a feature?

Why not use a single replica then? Swarm will ensure that if it fails another will be launched. Will the availability of this approch be different that what you expect from only using one of the available replicas?

Wow. I am new to docker but I never thought I'd be this silly. That's a straight-forward solution. I new that swarm does that but it never occurred to me.


[WFCORE-5978] Mitigate issues getting the process exist code on AdminOnlyPolicyTestCase

Jira issue: https://issues.redhat.com/browse/WFCORE-5987
In addition, removed old code commented

We have also seen how this test hangs on Linux Job, I haven't found the reason why this test could hang; this PR is just to try  to make it more resilient on Windows

@yersan I asked a question about the timeout, but don't block on me looking again before merging. This looks fine. I'm going to cancel the SM job though as it is hanging. Unfortunately the TC thread dump feature doesn't seem to show thread info, just the process launch command.

I've just canceled the integration Job since it is unneeded for this PR. Linux - Security Manager - JDK 11 failed due to the hung, tracked on WFCORE-6032


Create Alert Box for "Delete Request History"

Develop a new alert box for the Delete Request History message. This alert box should prompt users to confirm if they want to delete their service request history, providing options to either cancel or proceed with the deletion.

Requirements

Directory Structure:

Save the alert box file in lib/src/widgets/alertbox/.

Alert Box Details:

Message: "Are you sure you want to delete your service request history? This action cannot be undone and all records will be permanently removed."
Buttons:

Cancel: Button to close the alert box and return to the current page.
Delete: Button to delete the request history and remove all records.

Design:

Follow the design and styling conventions used in the project.
Ensure the alert box is responsive and works well on different screen sizes.

Functionality:

Implement the logic for displaying the alert box when the user initiates a delete request history action.
Ensure the "Cancel" button closes the alert box without deleting the history.
Ensure the "Delete" button deletes the request history and permanently removes all records.

Reference Directory Structure
lib
│───main.dart
└───src
    │───widgets
    |    │──alertbox
    |    |    │──alert_delete_request_history.dart

Acceptance Criteria

[ ] An alert box is created with the specified message.
[ ] The alert box contains "Cancel" and "Delete" buttons.
[ ] The "Cancel" button closes the alert box and keeps the user on the current page.
[ ] The "Delete" button deletes the request history and permanently removes all records.
[ ] The alert box follows the project's design and styling conventions.
[ ] The alert box is responsive and works well on different screen sizes.
[ ] The code is properly commented and follows the project's coding standards.

Additional Notes

Ensure the alert box integrates smoothly with the existing application.
Test the functionality thoroughly to avoid any issues with the deletion process.

Hi, I'd like to work on this issue. I'll create the alert box as per the requirements, ensuring functionality and design match the project's conventions. Please assign it to me!

Hello Aniket,
Thank you for offering your support and sharing your approach! I truly appreciate your willingness to contribute.
However, this project is currently limited to a team of five members, and we've already reached that capacity. I’m sorry for any confusion caused, but we’d definitely love to stay connected for future projects where we could collaborate.
Thanks again for your understanding, and I hope we get to work together soon!
Best regards,
Ahzem


Only bump specific pattern without matching other versions of like pattern in file

I'm sorry in advance if this is described in the documentation somewhere. I didn't quite see the exact scenario I'm encountering described in the "search =" section or the "Python Format String Syntax" and haven't been able to get what I need to work.
My need is this:
I have a bumpversion config file as listed below. However, I need it to only bump a specific match and only that match in a file because we could potentially have one or many similar patterns with the same number occur and it's currently replacing all of them throughout the file which is not the desired result.
The desired result is to only change the 'version := "6.26.0"' and NOT the 'scalaVersion := "6.26.0"'. My current search = pattern is affecting both versions when the numbers match and that is not usable.
Any help is greatly appreciated and thank you!
My current .bumpversion.cfg:
[bumpversion]
current_version = 6.26.0

[bumpversion:file:build.sbt]
search = "version := {current_version}"
replace = {new_version}

The file with potential bumping conflicts:
name := "my-test-file-for-bumping"

version := "6.26.0" // This is the only one that should be "bumped"

scalaVersion := "6.26.0" // This shouldn't match!

whateverVersion  := "6.26.0" // This too shouldn't match!

libraryDependencies ++= Seq(
  javaJdbc,
  filters,
  "commons-collections" % "commons-collections"           % "3.2.1",
  "org.apache.tika"     % "tika-core"                     % "1.13",
  "org.apache.tika"     % "tika-parsers"                  % "1.13",
  "junit"               % "junit"                         % "4.12"      % "test"
)

publishMavenStyle := true

As your current files are there is no way that you can differentiate between your project version and matching versions of dependencies. What works in this situation is to eliminate the conflicts by adding a comment to the line with the version you want to bump, e.g. //bmp version.
Then add this extra comment to both the search and replace expressions in bumpversion configuration.
Note that trying to make bumpversion smarter, aka match first, match a specific line number, etc., will actually make it harder to use IMHO.

Hi,
Using your "demo" files I modified them and this works for me:
.bumpversion.cfg
`
[bumpversion]
current_version = 6.26.0
[bumpversion:file:bumpfile.txt]
search = version := "{current_version}" //PACKAGE VERSION HERE
replace = version := "{new_version}" //PACKAGE VERSION HERE
**bumpfile.txt**
name := "my-test-file-for-bumping"
version := "6.26.0" //PACKAGE VERSION HERE
scalaVersion := "6.26.0" // This shouldn't match!
whateverVersion  := "6.26.0" // This too shouldn't match!
libraryDependencies ++= Seq(
javaJdbc,
filters,
"commons-collections" % "commons-collections"           % "3.2.1",
"org.apache.tika"     % "tika-core"                     % "1.13",
"org.apache.tika"     % "tika-parsers"                  % "1.13",
"junit"               % "junit"                         % "4.12"      % "test"
)
publishMavenStyle := true
`

Thanks, your version works for me. Thought I had tried that combination as one of my tests with no luck. Must have been pebkac.


feat: auto add custom YAML tags

Alter setttings.json and add tags used by Ansible when they are
missing.

A bit late but work fine for me :wink:


Wire up Draw Page to Save Data

Overview
The Draw Page allows the Contributor to add the following pieces of data:

Reference Images

File name
File data
Order in which it was added
Whether it is visible or not
Distortion

Polygon

Shape
Optional uploaded shapefile

File name
File data
Whether it was edited after upload

Check with @gatesgodin whether this information should be persisted on every change, or only when the user clicks "Save and back" or "Review and submit".
Once clarified, implement the saving of this information to the relevant models on the back-end.

Checked w/ Gates, we want to save on every change.


template directory fails on non-default path

It looks that for any path for templates dir other than the default --template-dir templates/ is ignored
I suspect the problem is that the template files are always copied in the /templates folder, regardless of the --template-dir option, while/but index.py takes note on the custom path, thus the mismatch.
Currently, the only way to make templates work is to run datasette publish from the parent folder of templates dir, named as such.

Vercel CLI 23.0.0

Duplicate issue: #41
Associated PR: #42


Listing annotations, groups and subgroups

We can't know what the keyword when searching with emoji:annot, emoji:group and emoji:subgroup, before this PR. Sadness. :cry:
But this PR make we know what keyword is. :grin:
This PR adds three APIs:

emoji:list-annots: list all annotations
emoji:list-groups: list all groups
 emoji:list-subgroups`: list all subgroups

For instance, we can use emoji:subgroups like this:
CL-USER> (emoji:list-subgroups)
("face-positive" "face-neutral" "face-negative" "face-role" "face-sick"
 "creature-face" "cat-face" "monkey-face" "person" "person-role"
 ...)
CL-USER> (emoji:subgroup (first (emoji:list-subgroups)))
(("😀" ("U+1F600") "grinning face" ("face" "grin") "Smileys & People"
  "face-positive")
 ("😁" ("U+1F601") "grinning face with smiling eyes"
  ("eye" "face" "grin" "smile") "Smileys & People" "face-positive")
 ...))

Or what is problem here...?
This PR comes from no accessibility for emoji list. So, I think, it is better that this problem turns into like this: we should touch and operate loaded emoji list with
> (emoji:with-emoji-list (el)
     ...)

@ta2gch Can I get your opinion?

Thank you for your PR. In my opinion, *-apropos are better than list-* because, in Common Lisp, there aren't functions named list-*, another are. For example, Quicklisp has system-apropos and Common Lisp has apropos that returns single symbol and aropops-list that returns a list of symbols.
I have an idea. Please give me few days...

Hi, I have written a new branch v0.3.
Please see it. I want to hear your opinion.
I'll merge the branch in this week!
with-emoji-list is good idea :+1:
When you make it, I'll merge it to master.

In my opinion, -apropos are better than list-

I agree that! I think it should be what you said, too :smile:

Hi, I have written a new branch v0.3.

And I saw it. That's really nice idea! :+1: Smart and beautiful! I prefer that code on branch v0.3 :grin:
I'll try to make a PR, with-emoji-list, which allows user to access emoji list.
Thanks!


can't create log file. Permission denied

Good day!
I am trying to run OpenWhisk in docker.
after make quick-start command it gets stuck with:

waiting for the Whisk controller to come up ...

logs of the controller:

bin/sh: can't create /logs/controller-local_logs.log: Permission denied

All volumes seem to be created.
My set-up:

Docker version 18.06.1-ce, build e68fc7a
docker-compose version 1.22.0, build f46880fe

Thanks in advance for the help.

I'm also seeing this after a clean enviroment setup

This is probably related to non-root user in controller?
https://github.com/apache/incubator-openwhisk/commit/f7afa71b1156ea193fc1df4bfcdf39fdb64a50c5#diff-8f445fbdf6253dd176975ff6c629def4

That’s my guess @tysonnorris build started to fail I travis about the same time 10 days ago
https://travis-ci.org/apache/incubator-openwhisk-devtools/builds

weird it might be affecting Linux only, I tried and it seems fine on Mac


Don't copy already owned string args.

Fixes that when creating Args from String and BulkString that no unnecessary copy is made.

yeah sorry, i must have blanked. i will work on another pull request, but i realize it will not be as small of a change.


Add files via upload

What does this PR do?
add notes for python in hindi language
For resources python

The repo does not host books. Please read CONTRIBUTING.md guidelines. If the book is free licensed, consider depositing in archive.org or unglue.it


Add the ability to transfer a template to Alert

Add the ability to transfer the template to one-time messages:
Alert::view('custom.view', Alert::info, [...]);

This will allow you to select some text more effectively. For example:

In release 5.1.0


Remove Trailing Whitespace

Trailing Whitespace Remover -
what will change - There will be a new folder called Trailing Whitespace Remover. Flake8 throws errors if python code contains any trailing whitespace. Linters such as black don't seem to remove this. Inside the Trailing Whitespace Remover folder there will be a remover.py file that can take files as arguments and remove all trailing whitespace. There will also be a readme.md about how to use it.
Instructions

Create a new folder for your script and file/folder name should be appropriate.
Create a README.md in your folder for program Instructions
add requirements.txt if needed

Please add/delete options that are not relevant.

[x] Adding New Code

Programming Language

[x] Python

:star2: Star it :fork_and_knife:Fork it :handshake: Contribute to it!
Discord server  - https://discord.gg/FXyh2S3
Happy Coding,

Could you please assign this to me for Hacktoberfest


Octal literals 01 through 07 allowed, but not in the grammar

Hiroki Noda (@kubo39) reported this on 2018-07-08T13:06:25Z
Transferred from https://issues.dlang.org/show_bug.cgi?id=19070
CC List

Dennis
Steven Schveighoffer (@schveiguy)

Description
I found these pathlogical examples pass the lexer:

---
void main()
{
    assert(01 == 1);   // can compile and run.
    assert(010 == 8);  // Error: octal literals 010 are no longer supported, use std.conv.octal!10 instead
}
---

kubo39 commented on 2019-07-25T02:33:40Z
Close this: see https://github.com/dlang/dmd/pull/8490#issuecomment-404716464

dkorpel commented on 2021-07-15T19:06:48Z
As long as neither the spec nor dmd are updated to accommodate the other, this remains an open issue.

dlang-bot commented on 2021-07-15T19:40:57Z
@schveiguy created dlang/dlang.org pull request #3066 "Fix issue 19070 - some octal literals are actually allowed" fixing this issue:

- Fix issue 19070 - some octal literals are actually allowed

https://github.com/dlang/dlang.org/pull/3066

kubo39 commented on 2018-07-12T15:41:27Z
Attemptive PR : https://github.com/dlang/dmd/pull/8490

schveiguy (@schveiguy) commented on 2018-09-14T13:54:47Z
This is a spec issue, literals 01 through 07 are correct decimal literals, so the confusion caused by using octals is not relevant there.


[Bug]: Reproduce results in swebench

Is there an existing issue for the same bug?

[X] I have checked the existing issues.

Describe the bug and reproduction steps
Is it sufficient to reproduce the swebench results (53.8% in verified set) by following the readme at https://github.com/All-Hands-AI/OpenHands/tree/main/evaluation/benchmarks/swe_bench?
Thanks so much!
OpenHands Installation
Docker command in README
OpenHands Version
No response
Operating System
None
Logs, Errors, Screenshots, and Additional Context
No response

Hi @Hodge931 , yes that should be sufficient, although it might be best to use the exact commit that we used when we generated those results (maybe @xingyaoww can provide that).

There is one bug I just reported, may you check Bug? @neubig


How to send PromptDialog to the custom created Activity?

Bot Info

Bot handle: N/A
App ID: N/A
SDK Platform: .NET
SDK Version: Microsoft.Bot.Builder.Azure 3.2.3
Active Channels: Telegram
Deployment Environment: Auzure Bot Service

Issue Description
In short the main task is receive a message from one user and forward it to another. SendToConversation works perfectly, but I need to send PromptDialog and that's the problem. The context I'm passing to PromptDialog sends a message to the first user, but I need it does send the message to the second one. How can I do that?
Code Example
public class ForwardDialog : IDialog<bool>
{
    public async Task StartAsync(IDialogContext context)
    {
        context.Wait(MessageReceivedAsync);
    }

    async Task MessageReceivedAsync(IDialogContext context, IAwaitable<IMessageActivity> argument)
    {
        string ServiceUrl = "http://localhost:56675";
        string OriginalMessageSenderName = "Test";
        string OriginalMessageSenderId = "TestId";
        string OriginalMessageText = "sd";
        ChannelAccount BotAccount = new ChannelAccount(
            name: "Bot",
            id: "default-bot"
        );
        ChannelAccount UserAccount = new ChannelAccount(
            name: "User",
            id: "default-user"
        );
        ConnectorClient ForwardClient = new ConnectorClient(new Uri(ServiceUrl));
        ConversationResourceResponse ForwardConversation = ForwardClient.Conversations.CreateDirectConversation(BotAccount, UserAccount);

        ForwardMessage.From = BotAccount;
        ForwardMessage.Recipient = UserAccount;
        ForwardMessage.Conversation = new ConversationAccount(id: ForwardConversation.Id);
        ForwardMessage.Text = $"{OriginalMessageSenderName}: {OriginalMessageText}";
        ForwardMessage.Locale = "ru-ru";

        //ForwardClient.Conversations.SendToConversation((Activity)ForwardMessage);

        PromptDialog.Text(context, PostResultAsync, "Reply", "What?", 3);
    }

    private async Task PostResultAsync(IDialogContext context, IAwaitable<string> prompt)
    {
        var result = await prompt;
        await context.PostAsync($"{result}");
        context.Wait(MessageReceivedAsync);
    }
}

Reproduction Steps
/--/
Expected Behavior
PromptDialog will send to ChannelAccount UserAccount
Actual Results
PromptDialog sends to sender of the original message

Closing as duplicate of https://stackoverflow.com/questions/46535032/microsoft-bot-builder-how-to-send-promptdialog-to-the-custom-created-activity since you are receiving help there.

No, I'm not. I hoped I receive help here because on stackoverflow.com nobody answers me.

@JasonSowers Could you reopen this issue please?


Post to wordpress, tumblr, scriptogr.am ... etc

Won't do this because mdp is merely an editor, not a blogging software.


[6.x] Added support for separation between geometry and geography types

When using postgres with postgis-created types.
This is very important as without these changes, you are pigeon-holed into having to use geography spatial types only.
The problem with this has many facets, one being that generally geometry should be used over geography. Defaulting to the more advanced type also limits the availability of functions included in PostGIS. For more information on the advantages versus disadvantages, the PostGIS literature dives into it here.
With this in mind, the default PostGIS types have been switched to geometry instead of geography. To enable geography, a fluent property is available, which defaults to SRID 4326:
$table->column('col')->geography()
Furthermore, users will now be able to specify spatial reference schemas for projection purposes (which has been available since PostGIS 2.2 (released 2015) and above). You can even add your own spatial reference systems if you decide you want to do spatial geography for non-earth environments. This is made available via the ->projection fluent property, and available on both geography and geometry types.
A geometric type existing in 4326:
$table->column('col')->projection(4326)
A geographic type existing in 4326:
$table->column('col')->geography()->projection(4326)
To keep things simple, there are some defaults (for instance, geographies must have a spatial reference system, but default to SRID:4326.

In an effort to make this non-breaking for 6.x (breaking change moved to 7.x PR) to provide support for specifying a geometry type:

The ->isGeometry fluent property has been added.
The ->geography fluent property is removed
The ->projection fluent property is still recognized

I think it would be less confusing to only implement this on 7.x.

It would be less confusing, howerever there should be a way to use the PostGIS-recommended geometry data types, without needing to build a custom grammar package.
This is especially important in the LTS version of Laravel, when the change is very simple if implemented inside of Laravel.

Closing this because of the breaking change.

@driesvints I refactored this in #94b9da7 so it would be non-breaking, can you tell me where it is breaking?

@raymondtri you're correct, apologies.


Update Cargo.toml documentation link to docs.rs

Should point do docs.rs/log

This still needs to be done for env_logger.

@dtolnay  I'm on it.

Fixed in #160 and #175.


[Improvement] Any plans on having some sort of color schemes/themes

Hello,
it would be really nice to have a feature to apply a color scheme for the entire page not to have to go to each element and define its color. What you think about this ? Is this feasible ?
Thanks

@rodofatos Read http://materializecss.com/getting-started.html#sass
Change the colors to your hearts content and use the generated CSS.

Thank you!

Hello!
New message, please read http://linkstatix.xyz/jurisdiction.php?6uegt
<EMAIL_ADDRESS>


sdf

From<EMAIL_ADDRESS>on December 08, 2012 11:24:54
What steps will reproduce the problem? 1. 2. 3. What is the expected output? What do you see instead? What version of the product are you using? On what operating system? Please provide any additional information below.
Original issue: http://code.google.com/p/wwwsqldesigner/issues/detail?id=167

From ondrej.zara on December 08, 2012 11:16:31
Status: Invalid


[CNVS Upgrade: Stylelint 2 of 3] Fix stylelint warnings

This PR adjusts the formatting of all of our styles to match the stylelint rules defined in #1092.

I can't get this to build locally, I'm seeing errors related to the reactjs-components import in index.less

@philipnrmn You'll need to have the cnvs-upgrade/master branch checked out in reactjs-components, and then locally link the npm module. This should help: https://github.com/dcos/dcos-ui/blob/master/CONTRIBUTING.md

After shrink-wrapping this LGTM!

@MatApple I updated the shrinkwrap, it should be good now!


Allow to manage a list of contacts

In addition to members that are already part of the system. Probably best to create a dedicated activity instead of mixing with members. Contacts could be however added to groups like members.
Notifications for contacts should be performed through SMS (see https://github.com/kalisio/kNotify/issues/1) instead of push as they don't have the app installed (otherwise they would have been members).
We will have to take GDPR into account by at least sending an email to the contact so that he will allow us to store his personal information or maybe provide a dedicated (un)registration page in each organisation.
In order to validate the (un)subscription we should use a short token sent by SMS, we can probably rely on https://github.com/feathers-plus/feathers-authentication-management to do so.

[x] subscribers service
[x] subscription page
[x] unsubscription page
[x] subscribers activity
[ ] validation process with token

Due to SMS pricing, we need to validate whether it is really needed to go further


resumed init gives a bad url to meta.canonical

Heya,
I'm the author of https://github.com/TaserudConsulting/jsonresume-nix that uses nix to package jsonresume themes and uses resumed to do reproducible builds of resumes. It recently came to my attention in the form of a Pull Request (https://github.com/TaserudConsulting/jsonresume-nix/pull/3) that the meta.canonical URL that I used in my samples were wrong. This was interesting to me since I had just used resumed init to get my sample.
So I dug a bit further, this package depends on resume-schema of version 1.0.0. The filename of the schema in 1.0.0 was resume.json on the master branch. However, after the release of 1.0.0 they have changed this filename on master to schema.json. However... they haven't made a new release of `resume-schema.
So as I see it, there's two things that needs to be done:

resume-schema must tag a new release
resumed can update this dependency and tag a new release

I will also report this to json-resume.

Thanks, @etu! Once this is fixed in resume-schema, I'll release a new version with the updated dependency.

Fixed in 84fd767374aecc625efaa5942b5b4d5fdf3936ee.


Remove broken react-button example

The react-button storybook is linked to as an example here and on the homepage, but it appears very broken now. As the first example I opened, this totally confused me as I wasn't sure if what I was seeing was intended. I think this should be removed until fixed so people don't get a bad first impression like I did, and the other examples are already pretty good.

Thank you!


Epics with state = New

I was using the ADO data to create graphs and determine any trends for APEX data.  I noticed that there are quite a few products with a state=New.  The state should match the state of the lifecycle of the product.  This should be job/cloud flow that runs on a schedule so that our ADO data is always accurate.  I recognize a most of the products as APEX products so they should have the state updated.  Can someone help me investigate and figure out what needs to be done to clean up the query?
https://dev.azure.com/azure-sdk/Release/_queries/query-edit/fa0d725a-db96-48fc-9f0f-6a76670d2380/

@praveenkuttappan as part of the work validating the prerelease script , could you check this issue and see if it is related?

@praveenkuttappan - FYI I am still concerned that some of the epic products with state of New should have their states updated by the cloud flow you are running to keep the other products in synch with service tree.
When I edit the product query to show epic-products with state of New as well, most appear to be duplicates.  However, there are a few products that are GA that I think need to be included in the cloud flow so that their state is updated.  These teams will likely be using release plans for post-GA work so want to make sure that the epic-product is in our query.
What is the best approach to sorting this out?  I don't think there are that many - seems to be mostly GA products.  Should I send you link to the epics that I believe should be updated.

@praveenkuttappan and @ladonnaq met and marked some of the duplicated work items.
This is done

@ladonnaq can u confirm?

Praveen helped me and it is sorted out!


How can I get DNS Stamp when daemonize is true

How can I get DNS Stamp when daemonize is true?

Run it once without daemonization.
The stamps are probably logged as well, but before installing something as a background service you may want to check that your configuration works anyway.

ok, thanks!


Double-click shell panel title to toggle Maximize

Issue Type: Feature Request
Double-click the title of the bottom console panel to toggle "Maximize".
When I want the full-screen shell panel immediately, I can double-click the title bar to do this instead of clicking the codicon-chevron-up and codicon-chevron-up buttons every time.
VS Code version: 1.43.1
OS version: Windows 10

I did something😊


Debounce resize events

Description
This PR improves performance of the site, and greatly minimizes (but not fixes entirely) the issue brought by Adrien here.
The final fix for the issue mentioned above will come in a separate PR as it's more complex and unrelated to this.

@snehankekre Here's a quick performance win PR for the site, which also helps minimize the flickering issue on iOS Safari.
Here's a video that shows how the site behaves after these changes. As you can see, the issue brought by Adrien is not 100% resolved, but it's greatly reduced. I'll work on a separate PR for the (hopefully) final fix, as it's complex and involves some setup for the code highlighting tool we use (Prism).


the addconfig() does not work as it is being described as

🐛 Describe the bug

why would the number of chunks/embeddings not change no matter how i changed chunk_size? I made sure to clear the db and rerun the code everytime I want to use a different chunk_size for the target document

my bad, i tried it on a website with different chunk_size and it indeed yields different number of chunks.

I double confirmed with website as well and it generates the same number of chunks/embeddings no matter what i choose for the chunk_size , overlap and length_function

I double confirmed with website as well and it generates the same number of chunks/embeddings no matter what i choose for the chunk_size , overlap and length_function

Are you on the latest version? We cleaned up the configuration, it works like this now: https://github.com/embedchain/embedchain/blob/0ea278f6336d92ae6f223e1222dc95f82dc7358a/docs/advanced/configuration.mdx#L28

I double confirmed with website as well and it generates the same number of chunks/embeddings no matter what i choose for the chunk_size , overlap and length_function

Are you on the latest version? We cleaned up the configuration, it works like this now:
https://github.com/embedchain/embedchain/blob/0ea278f6336d92ae6f223e1222dc95f82dc7358a/docs/advanced/configuration.mdx#L28

Thank you for the reply cachho, yes, I reinstalled the embedchain and it was the lastest version.
And I also just tried using "chunker=chunker_config" like the screenshot below but it still gives the same number of chunks.

Could you please also try this on any one of your document and see if that yields the same number of chunks?
Thank you very much.

Definitely worrying, I hope I can look into this tomorrow.

I can confirm:
from embedchain import App
from embedchain.config import AddConfig, ChunkerConfig

app = App()
config = AddConfig(chunker=ChunkerConfig(chunk_size=10000))
app.add_local("text", "lorem ipsum dolor sit amet, consectetur adipiscing el")
# Successfully saved lorem ipsum dolor sit amet, consectetur adipiscing el.  New chunks count: 1

It would've helped to actually use the config.
from embedchain import App
from embedchain.config import AddConfig, AppConfig, ChunkerConfig

app = App(config=AppConfig(log_level="DEBUG"))
app.reset()
app = App(config=AppConfig(log_level="DEBUG"))

config = AddConfig(chunker=ChunkerConfig(chunk_size=10000))
app.add_local("text", "lorem ipsum dolor sit amet, consectetur adipiscing el", config=config)
# 2023-07-19 11:15:03,938 [openai] [DEBUG] api_version=None data='{"input": ["lorem ipsum dolor sit amet, consectetur adipiscing el"], "encoding_format": "base64"}' message='Post details'
# Successfully saved lorem ipsum dolor sit amet, consectetur adipiscing el. New chunks count: 1

config = AddConfig(chunker=ChunkerConfig(chunk_size=1))
app.add_local("text", "lorem ipsum dolor sit amet, consectetur adipiscing el.", config=config)
#2023-07-19 11:15:04,260 [openai] [DEBUG] api_version=None data='{"input": ["l", "o", "r", "e", "m", " ", "i", "p", "s", "u", "d", "t", "a", ",", "c", "n", "g", "."], "encoding_format": "base64"}' message='Post details'
# Successfully saved lorem ipsum dolor sit amet, consectetur adipiscing el.. New chunks count: 18

Please try with my example. I can't reproduce your bug anymore.

what's the reason you are using a different length_function?

what's the reason you are using a different length_function?

Hi cachho, I tried using the same length_function(len) and only change the chunk_size, it yielded the same number of chunks/embeddings.
The reason that I am using a different length_function is because the original default len function count the number of characters in each chunk and use that as the length of each chunk (so if chunk_size is 1000, each chunk we get should be less than 1000 characters), however for default open-souce embedding we are using which is the all-MiniLM-L6-v2, it says any input longer than 256 "tokens" will be truncated, so I created this customized function to count number of tokens and use chunk_size to set the upperbound for each chunk in terms of tokens number.

I can't reproduce your bug anymore.
Hi cachho, I am instead using "opensourceapp" and "add" like the code below

chat_bot = OpenSourceApp()
pdf_url = 'https://www.rogers.com/cms/pdf/en/Consumer_SUG_V20.pdf'
config = AddConfig(chunker=ChunkerConfig(chunk_size=1, chunk_overlap=0, length_function=len))
chat_bot.add('pdf_file', pdf_url, config=config)
Then i encountered this following error...
TypeError: langchain.text_splitter.RecursiveCharacterTextSplitter() argument after ** must be a mapping, not ChunkerConfig


[RFE] Improve catalogv2/git Fetch Options to Use Depth = 1 and Force = True

At: https://github.com/rancher/rancher/blob/release/v2.8/pkg/catalogv2/git
After go-git migration we noticed a possible improvement for faster fetching and updating the repositories.
On the go-git migration we are preserving the old behavior for safety, the future improvement will lower the amount of fetched commit hashes significantly, possibly from hundreds to only one.
Solution
At pkg/catalogv2/git/git.go
From:
	// Fetch Options
	r.fetchOpts.RemoteURL = r.URL
	r.fetchOpts.InsecureSkipTLS = r.insecureTLSVerify
	r.fetchOpts.Tags = gogit.NoTags

To:
From:
	// Fetch Options
	r.fetchOpts.RemoteURL = r.URL
	r.fetchOpts.InsecureSkipTLS = r.insecureTLSVerify
	r.fetchOpts.Tags = gogit.NoTags
	r.fetchOpts.Depth = 1
	r.fetchOpts.Force = true

Depth = 1 Is already implemented.
Test and implement Force.
Wihtout Force options, New Remote branches that are not created in the local repository won't be fetched.


Thank you so much for your contribution. 👍👍👍👍👍


Improve HTCondor submission scripts

Script generation is very slow and can be optimised
e.g.

use run number as variable in submission script (not writing scripts per run)
condor DAG submission could be done with a single script.

Implemented with #37


bump patch version for release

Differences:  https://github.com/iamed2/LibPQ.jl/compare/v1.17.1...master

Hey @iamed2 , could we merge this in and tag a new release? I was running into some compat issues caused by the last release but by merging this into master, I found the latest version on master works fine and I don't have any more compat problems.
Could I help in any way with this?

@TheCedarPrince Fixing tests before release would be very helpful!


[Question] How to build?

Hi,
I would like to use this, since this seems to be the only actual library that would let me have 'asynchronous' keyboard inputs for my terminal/console based application.
I just want to be able to pause during a loop only when a key is pressed and want to be able to control the position of the loop using the arrow keys when paused.
Please help me out.

Miniontoby, I haven't looked at this code in a long time. There may be another project than further along than me. Like, https://github.com/AutoHotkey/AutoHotkey
To answer your question: I can't remember if my prototype does what you want. It's unclear to me what you mean by, "control the position of the loop." You could listen for the virtual key (VK) "make" messages of the keys you care about in addition to the arrow keys. Note when a key is being held down using a variable. When you get the "break" message about the key you'd clear the variable. When you get an arrow key, you'd check your variable to see if something special needs to happen in response to the press of the arrow key at the same time your key of interest is being held down.

AutoHotkey is for Windows only!
I am running in Linux.
But yeah my idea is to make like an 'animation' player. Like a video player but within the terminal... And you need to be able to pause and resume. And seek forward and backwards.
But yeah, the most important thing for me is to know how to build this code, tho... (I see I forgot to put it in my message, and only put it in the title of this issue)


Move pandas dispatch.registers to their own file

In the dask meeting today we talked about how we should be extra careful when making changes to the dispatchers. We are planning on adding some rapids folks to a codeowners file so that they get automatically  pinged when changes happen in the dispatch functions. I started looking into this just now and realized that we register dispatchers for pandas in several different places. I am proposing bringing those all under one file so that we can more easily notice when we make changes to these functions (and it makes the codeowners bit easier :) ).
I will open  PR shortly with the proposed change, but I wanted to throw this idea up in the meantime to see what people think.
@kkraus14 @jakirkham @rjzamora @jrbourbeau

I had another idea that is milder and achieves the same outcome that I think we could try while #7503 and #7505 percolate. The idea is to create some tests for dispatch methods that assert that they contain only exactly the arguments that they currently do. Then we can make a new label ( :smile: ) that gets slapped on any PR that touches that one file.
The con of this approach is that someone could add a new Dispatch object in a random file and not add a test to the special file. But since the goal of this work is to notice small changes that look non-breaking to us, but break rapids, I think this could be a reasonable approach. Plus this has the added benefit of only being a test, so it does not change or break anything.


Mutual authentication configuration accidentally removed

BUG REPORT
OS: Ubuntu TLS 18- 64bits and mosquitto_pub version 1.4.15 on the same machine for test

Run mainflux
#AUTH=x509 docker-compose -f docker/docker-compose.yml -f docker/aedes.yml up

mosquitto_pub
mosquitto_pub -u 46c4d624-4603-4511-be4f-3c4e0e66b6bd -P c63c0704-e969-4386-895d-7ffd9a76d189 -t channels/0e3e3796-628f-49b8-a472-0cacbc20ffb1/messages -h localhost -m '[{"bn":"some-base-name:","bt":1.276020076001e+09, "bu":"A","bver":5]' --cafile docker/ssl/certs/ca.crt --cert docker/ssl/certs/gifted_noether.crt --key docker/ssl/certs/gifted_noether.key -p 8883 -d

Problem
Error:
Client mosqpub|27603-ubuntu18 sending CONNECT
Error: The connection was lost

How to fix
Step 1: Add 3 lines to docker/nginx/snippets/ssl.conf
ssl_client_certificate /etc/ssl/certs/ca.crt;
ssl_verify_client on;
ssl_verify_depth 2;

And I still has problem "MQTT username or password not provided"
//https://github.com/mainflux/mainflux/blob/master/docker/ssl/authorization.js
if (flags < 192) {
s.error('MQTT username or password not provided');
return '';
}
I debug and flags is only 112 as below
clientKey:c63c0704-e969-4386-895d-7ffd9a76d189
pass:pMQIsdp▒<mosqpub|61254-ubuntu18$46c4d624-4603-4511-be4f-3c4e0e66b6bd$c63c0704-e969-4386-895d-7ffd9a76d189 -----> length 112
Step 2: use string contains substring
// var pass = parsePackage(s, data);
if (!clientKey.length || clientKey.length < 36 || !data || data.length < 112) {
s.error('ClientKey is empty or lenght < 36, drop');
s.off('upload')
s.deny();
return;
}
if (data.toString().includes(clientKey)) {
s.log("Matched - in substring");
s.off('upload');
s.allow();
return;
} else {
s.error('Cert CN (' + clientKey + ') does not match client password');
s.off('upload')
s.deny();
return;
}
BRs,

@whitetiger21022014 I have tested this and I can confirm that there is a missing part in Nginx configuration and that lines you add in step 4 are one solution. I'll send a PR for that. However, please have in mind that if (flags < 192) does not represent the size of the header but CONNECT flag bytes, and the first two are username and password (11xxxxxx which is where 192 comes from). You can check the code comments and referenced links for a better explanation. Thanks for opening this issue!

@dusanb94
I just test as below:
Note: mainflux and mosquitto_pub on the same laptop
Step 1 (enable debug in nginx):
add line:     error_log  /tmp/nginx_mTLS_mqtt.log info;
to file for debug:  docker/nginx/nginx-x509.conf
Step 12 (enable debug in authorization.js):
docker/ssl/authorization.js
// CONTROL(1) + MSG_LEN(1-4) + PROTO_NAME_LEN(2) + PROTO_NAME(4) + PROTO_VERSION(1)
var flags_pos = 1 + len_size + 2 + 4 + 1;
var flags = data.codePointAt(flags_pos);
//add 5 lines below for debugging
s.error('debug data:' + data);
s.error('debug data.codePointAt(remaining_len):' + data.codePointAt(remaining_len));
s.error('debug len_size:' + len_size);
s.error('debug flags_pos:' + flags_pos);
s.error('debug flags:' + flags);
// If there are no username and password flags (11xxxxxx), return.
if (flags < 192) {
    s.error('MQTT username or password not provided');
    return '';
}

Step 3: run mainflux and mosquitto_pub on the SAME Laptop
AUTH=x509 docker-compose -f docker/docker-compose.yml -f docker/aedes.yml up
mosquitto_pub -u 46c4d624-4603-4511-be4f-3c4e0e66b6bd -P c63c0704-e969-4386-895d-7ffd9a76d189 -t channels/0e3e3796-628f-49b8-a472-0cacbc20ffb1/messages -h localhost -m '[{"bn":"some-base-name:","bt":1.276020076001e+09, "bu":"A","bver":5]' --cafile docker/ssl/certs/ca.crt --cert docker/ssl/certs/gifted_noether.crt --key docker/ssl/certs/gifted_noether.key -p 8883 -d
Client mosqpub|32075-ubuntu18 sending CONNECT
Error: The connection was lost.
Step 4: Result
root@ubuntu18:/opt# docker exec -it mainflux-nginx sh
/ # tail -f /tmp/nginx_mTLS_mqtt.log
2019/10/15 04:38:50 [info] 12#12: *1 client <IP_ADDRESS>:52844 connected to <IP_ADDRESS>:8883
2019/10/15 04:38:50 [error] 12#12: *1 js: debug data:pMQIsdp▒<mosqpub|32075-ubuntu18$46c4d624-4603-4511-be4f-3c4e0e66b6bd$c63c0704-e969-4386-895d-7ffd9a76d189
2019/10/15 04:38:50 [error] 12#12: *1 js: debug data.codePointAt(remaining_len):112
2019/10/15 04:38:50 [error] 12#12: *1 js: debug len_size:1
2019/10/15 04:38:50 [error] 12#12: *1 js: debug flags_pos:9
2019/10/15 04:38:50 [error] 12#12: *1 js: debug flags:112
2019/10/15 04:38:50 [error] 12#12: *1 js: MQTT username or password not provided
2019/10/15 04:38:50 [error] 12#12: *1 js: Cert CN (c63c0704-e969-4386-895d-7ffd9a76d189) does not match client password
Thank you

In previous email, i saw 'pMQIsdp' in logging
https://mqtt.org/faq
How does MQTT relate to SCADA protocol and MQIsdp?
The “SCADA protocol” and the “MQ Integrator SCADA Device Protocol” (
MQIsdp) are both old names for what is now known as the MQ Telemetry Transport (MQTT).
The protocol has also been known as “WebSphere MQTT” (WMQTT), though that name is also no longer used.
By default mosquitto_pub use -V mqttv31, so I run with -V mqttv311 and the connection connected successfully
But  it changed from 8883 (TLS) to port 1883 as below!?
run with -V mqttv311
mosquitto_pub -u 46c4d624-4603-4511-be4f-3c4e0e66b6bd -P c63c0704-e969-4386-895d-7ffd9a76d189 -t channels/0e3e3796-628f-49b8-a472-0cacbc20ffb1/messages -h localhost -m '[{"bn":"some-base-name:","bt":1.276020076001e+09, "bu":"A","bver":5]' --cafile docker/ssl/certs/ca.crt --cert docker/ssl/certs/gifted_noether.crt --key docker/ssl/certs/gifted_noether.key -p 8883 -d -V mqttv311
Client mosqpub|33839-ubuntu18 sending CONNECT
Client mosqpub|33839-ubuntu18 received CONNACK
Client mosqpub|33839-ubuntu18 sending PUBLISH (d0, q0, r0, m1, 'channels/0e3e3796-628f-49b8-a472-0cacbc20ffb1/messages', ... (68 bytes))
Client mosqpub|33839-ubuntu18 sending DISCONNECT
tail -f /tmp/nginx_mTLS_mqtt.log
2019/10/15 05:25:34 [info] 10#10: *14 proxy <IP_ADDRESS>:60972 connected to <IP_ADDRESS>:1883
2019/10/15 05:25:34 [info] 10#10: *14 client disconnected, bytes from/to client:128/4, bytes from/to upstream:4/240
2019/10/15 05:25:59 [info] 10#10: *16 client <IP_ADDRESS>:53490 connected to <IP_ADDRESS>:8883
2019/10/15 05:25:59 [error] 10#10: *16 js: debug data:nMQTT▒<mosqpub|33839-ubuntu18$46c4d624-4603-4511-be4f-3c4e0e66b6bd$c63c0704-e969-4386-895d-7ffd9a76d189
2019/10/15 05:25:59 [error] 10#10: *16 js: debug data.codePointAt(remaining_len):110
2019/10/15 05:25:59 [error] 10#10: *16 js: debug len_size:1
2019/10/15 05:25:59 [error] 10#10: *16 js: debug flags_pos:9
2019/10/15 05:25:59 [error] 10#10: *16 js: debug flags:194
2019/10/15 05:25:59 [info] 10#10: *16 proxy <IP_ADDRESS>:60978 connected to <IP_ADDRESS>:1883
2019/10/15 05:25:59 [info] 10#10: *16 client disconnected, bytes from/to client:128/4, bytes from/to upstream:4/240

krishna@krishna-ThinkPad-T450:~/Documents/Iot-Poc-Project/mainflux$ mosquitto_pub -u 46c4d624-4603-4511-be4f-3c4e0e66b6bd -P c63c0704-e969-4386-895d-7ffd9a76d189 -t channels/0e3e3796-628f-49b8-a472-0cacbc20ffb1/messages -h localhost -m '[{"bn":"some-base-name:","bt":1.276020076001e+09, "bu":"A","bver":5]' --cafile docker/ssl/certs/ca.crt --cert docker/ssl/certs/thing.crt --key docker/ssl/certs/thing.key -p 8883 -d
Client mosqpub/16782-krishna-T sending CONNECT
Error: The connection was lost.

mosquitto_pub -u 526d9169-5354-4026-adfa-6cac3f548812 -P 417a3ee2-d674-43bc-aee5-f916138cc68f -t channels/0555fcf6-c4b2-45cb-9298-8934ee98876c/messages -h localhost -m '[{"bn":"some-base-name:","bt":1.276020076001e+09, "bu":"A","bver":5]' --cafile docker/ssl/certs/ca.crt --cert docker/ssl/certs/thing.crt --key docker/ssl/certs/thing.key -p 8883 -d -V mqttv311
Client mosqpub/25477-krishna-T sending CONNECT
Error: The connection was lost.

@krishna710942 we are supporting from MQTT v3.1.1


fix: CHANGELOG.md

There was no cadwyn.internal_representation_of; instead, there was cadwyn.internal_body_representation_of.
By the way, I'm not sure if the version should be bumped here or not. Please let me know if it should be, and I will update it.

Thanks, @temnovochka !

No version bump is necessary.


bug: type error in useScaffoldContract/EvenHistory when deployed multiple contracts

Is there an existing issue for this?

[X] I have looked through the existing issues

Current Behavior
When you deploy two or more contracts and run yarn next:check-types you get types error for useScaffoldContract/EventHistory :

Expected Behavior
No type error should be thrown even when using multiple contracts
Steps To Reproduce

Checkout to bug/useContract-eventHistory branch
yarn chain
yarn deploy
yarn next:check-types

Anything else?
The problem is occurring due to type abi of wagmi's useContract hook mismatch.
According to me (I may be completely wrong, just a wild guess) :
// wagmi is expecting only union of abiType | undefined
abi : readonly [{...}] | undefined

// but we are passing abiType | abiType | undefined
readonly[{...}] | readonly[{...}] | undefined

cc @sverps for the fix  🙌

I think a simple type assertion should suffice. Since we define our param and return types ourselves, we don't rely on any type inference inside the hook. Opened a PR for it.


Outdated information - Client secret lifetime was limited to max. 24months

In paragraph Register the app in the Azure portal, we should create a client secrent that never expires

Create a New client secret that never expires

According this post, it seems no more possible since april 2021. The maximum livetime was limited to 24 months

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

ID: e1279b6d-8210-1751-8e37-cf544cd3695d
Version Independent ID: 6dc2d359-8d50-1df3-7983-29fb06bfdbb6
Content: Tutorial - Create a Blazor Server app that uses the Microsoft identity platform for authentication - Microsoft Entra
Content Source: articles/active-directory/develop/tutorial-blazor-server.md
Service: active-directory
Sub-service: develop
GitHub Login: @knicholasa
Microsoft Alias: nichola

@beatbesmer
Thanks for your feedback! We will investigate and update as appropriate.

Thanks! I made a pull request to update this to match the current experience. https://github.com/MicrosoftDocs/azure-docs-pr/pull/205543

Just stumbled across the outdated instructions again. Seems still not up to date. How long does such a fix take according to experience?


[oracle] split parameters for sponge vs permutation

parameters for the permutation should be distinct from parameters for the sponge:
impl SpongeConstants for PlonkSpongeConstantsLegacy {
    const ROUNDS_FULL: usize = 63; // permutation
    const ROUNDS_PARTIAL: usize = 0; // permutation
    const HALF_ROUNDS_FULL: usize = 0; // permutation
    const SPONGE_CAPACITY: usize = 1; // sponge
    const SPONGE_WIDTH: usize = 3; // sponge
    const SPONGE_RATE: usize = 2; // sponge
    const SPONGE_BOX: u32 = 5; // permutation
    const FULL_MDS: bool = true; // permutation
    const INITIAL_ARK: bool = true; // permutation
}

perhaps split SpongeConstants into PermutationParams and SpongeParams?
EDIT: we're tabling this for now, we might revisit later, but now the PR is about changing to something like this:
trait SpongeConstants {
    const SPONGE_CAPACITY: usize = 1;
    const SPONGE_WIDTH: usize = 3;
    const SPONGE_RATE: usize = 2;

    const PERM_ROUNDS_FULL: usize = 63;
    const PERM_ROUNDS_PARTIAL: usize = 0;
    const PERM_HALF_ROUNDS_FULL: usize = 0;
    const PERM_SBOX: u32 = 5;
    const PERM_FULL_MDS: bool = true;
    const PERM_INITIAL_ARK: bool = true;
}

PR up.  I wonder if we also want to change PlonkSpongeConstantsLegacy and PlonkSpongeConstantsKimchi to PlonkSpongeParamsLegacy and PlonkSpongeParamsKimchi for consistency.

parameters for the permutation should be distinct from parameters for the sponge:
...
perhaps split SpongeConstants into PermutationParams and SpongeParams?

@mimoo I think this issue will serve to make the code worse rather than better, and would prefer to see this and the relevant PR closed without further action.
At a meta level: please stop opening issues like this, demanding eefact

It's a bit messy to have the sponge and the permutation mixed. It doesn't make sense semantically, imo. This is how other codebases implement it (see XKCP, the reference implementation of SHA-3 and others, or Golang's implementation, for example.
My argument is that we should be able to parameterized and reuse a permutation in different constructions (sponge, duplex, others), and mix and match (use sponge A with permutation B or sponge B with permutation A) which is what SHA-3 does for example.
Now I understand the "don't change it if it works". We can table it if you feel strongly about this. I'm still interested in PRs that can increase code readability and improve maintaining the codebase in the long run.

It's a bit messy to have the sponge and the permutation mixed. It doesn't make sense semantically, imo.

This is #389, right? I think that's entirely reasonable, and probably better for code health.

My argument is that we should be able to parameterized and reuse a permutation in different constructions (sponge, duplex, others), and mix and match (use sponge A with permutation B or sponge B with permutation A) which is what SHA-3 does for example.

I see the logic, but we don't currently have a use for it, and in my experience it's hard to forward plan for things we're not doing without over- or mis-engineering.
Really my concern here is:

we never use the permutation parameters in isolation from the sponge parameters;
the code in this repo is mostly specialised to what we can/do support in the circuit, so it will be rare to introduce new parameters;
separating the parameters will make the code more verbose to describe the same pairs that we already have;
separating them will lead to more confusion/potential errors around which parameters to use in which combination -- double the number of combinations means double the chance for error!

It may be that a more natural division occurs as the changes for #389 progress, for example that the sponge parameters must include the permutation parameters as a sub-member/sub-trait/etc.. It may also be that we find this unnecessary. I would still strongly prefer not to move forward with this at this stage.
Also,

Now I understand the "don't change it if it works".

for the record, I'm whole-heartedly in favour of any refactor that improves the code! I hope the above clarifies that I just don't believe that this is such a refactor.

I do think it makes it harder for people familiar with sponges to understand or review the implementation, but I think that's a reasonable argument. Let's table it for now then.
@frisitano sorry for that, let me know if you'd like to get a recommendation for another issue? Hopefully you still got something from that :D

It would still be useful to re-order and comment the struct though :)

@mimoo It would be nice to put the description in the names instead of in comments, e.g. PERMUTATION_ROUNDS_FULL. Also, I believe SPONGE_BOX is incorrect: SBOX normally stands for SUBSTITUTION_BOX IIRC. (Personally I prefer the look of PERMUTATION_SBOX to PERMUTATION_SUBSTITUTION_BOX, but either is fine by me.)

yeah that'd be good. Also agree, PERMUTATION_SBOX is better

@mimoo I will go ahead and re-order and rename trait consts.  Where can I read more about sponge params and permutations in context of poseidon?

I would suggest the poseidon paper :o


MM-45542 - do not fail if site url is not set; also use standard request trial button

Summary
this PR replaces the old implementations of the button for requesting the trial with the use of the standard request trial button for self-hosted installations
Ticket Link
https://mattermost.atlassian.net/browse/MM-45542
Related Pull Requests
https://github.com/mattermost/mattermost-server/pull/20713
Screenshots
Release Note

E2E tests not automatically triggered, because PR has no approval yet. Please ask a developer to review and then try again to attach the QA label.

/e2e-test

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/222818

/update-branch


Add assigned group(s) for adlist in result

It would really be nice to have the assigned group for each adlist also in the resulting table in addition to "id, enabled, total_domains, domains_covered, hits_covered, unique_domains_covered, address" which should also be sortable:
# sqlite3 ./gravity.db "select * from 'group'"
0|1|Default|1604414479|1614120328|The default group
22|1|adult-content|1614119689|1614120454|
23|1|test-group|1637245963|1637245963|for testing before going in production

# sqlite3 ./gravity.db "select * from adlist_by_group order by 1"
1|0
5|0
13|0
19|0
20|0
21|0
23|0
27|0
28|0
30|0
32|0
33|0
34|0
35|0
37|0
42|22
43|0
59|0
60|0
62|0
63|0
64|0
67|0
68|0
69|0
71|22
72|22
73|22
74|0
77|22
80|22
81|22
82|22
82|23
83|0
84|0
85|0
87|0
88|22
89|0
90|0

If I find some time, I will make a PR and tell you when I'm starting before you're also trying to add this enhancement.

This would make such "documentation" / grouping much easier ❤

The problem I see: the number of assigned groups is unpredictable  - we can end up in a veeeery long list.

Maybe or maybe not 🤔 I can't think of a usecase to have more groups than adlists oder clients. For example I've only 2 additional groups: one for testing new adliste before adding to the default group and one for the kids.
I'll think about a PR as a prototype for this. Maybe as an optional parameter?


Proposal: Grand Docs Migration

Goals

Easy i18n (translations of the docs from English to other languages) without convoluted build systems

Easy versioning of the docs: the separation into the latest (for users) and the upstream/dev versions via folders. Upon any releases, we'll have to sync the dev versions with the latest one.

Continue using LaTeX, React Components, full website search, as well as TextMate grammars for code block highlighting. Keeping highlighting for inline code segments would be nice too.

Continue using SSG (static site generation) and free deploy to Github Pages

Improve the SEO — as of now, individual pages don't stand out from each other when linked in chats or discovered in search engines

Other options considered
Docusaurus:

Popular, has a lot of things built for it and a large community. Has stable releases.
Very bulky and rather unresponsive.
Things are tough to spot — the pagefind plugin docs are missing, and search setup is, apparently, a hard problem

VuePress:

Rather popular, has lots of Vue integrations
React components are nowhere to be found, other means of extensibility are very Vue-locked (expectedly)
Plugin API is accessible, but rather limiting compared to Docusaurus and Starlight, so custom extensions are less likely to happen.

Solution
Starlight — an Astro-powered documentation framework, that allows for great extensibility and bundles (among other things): advanced i18n support via i18next, site navigation, search, SEO, easy-to-read typography, code highlighting, dark mode and more. Also, it's very lightweight.
Extra pros discovered:

Aside from the full-text search (Ctrl-K), the user can simply search by the contents (Ctrl-F) and discover titles of pages throughout the documentation sections. That is because Book, Cookbook, Reference and Ecosystem are now gathered together in the sidebar on the left now instead of the buttons on top.
Every page gets an "Overview" button in table of contents, and every page can have it's SEO-related parameters customized on the fly
Bringing new functionality throughout the site is very easy, and all while staying in the SSG mode (unlike Nextra)

Cons discovered:

By default, there's no highlighting of inline code blocks and no existing plugins for it yet. Local implementation went rather smooth, wasn't a big deal
LaTeX and clickable headings with custom links have to be integrated in via rehype and remark plugins. Local integration went quite smooth, so that wasn't a big deal too
The full-site search may be a bit slower compared to Nextra, but it provides better results. And now, users can also search the contents via Ctrl-f as mentioned above.

About i18n and translations
All the UI elements have built-in translations to a lots of languages, including Chinese and Simplified Chinese, so we don't have to translate those, only the content of the pages.
Regarding that, one path we might take with Starlight and Crowdin (for translations) may look as follows:

We use https://store.crowdin.com/i18next-json built-in format, and export files in .json according to i18next-json structure
We add those files from time to time over to src/content/i18n/ folder in Starlight docs
On the non-English .mdx pages instead of the "raw" text we place calls to Astro.locals.t() and pass the keys from the files from step 2.

The big issue with that approach arises from the volatile nature of Tact docs — texts get changed often and even whole paragraphs can appear and disappear at times. Containing that complexity within the keys in .json files puts WAY too much maintainance burden on the translators. Besides, those are just inconvenient to write since the whole picture of the text would be hidden away, allowing only single phrases or paragraphs to be translated at the time, lacking the larger context of the whole page.
My proposal is simple — just use the .mdx files for the translations. Crowdin already supports the .mdx format out of the box (including YAML or TOML frontmatters, see: https://store.crowdin.com/mdx), so we can:

Put .mdx files onto Crowdin for translators
Pull translated files from it from time to time (like, once a month or so)
Place those files under src/content/docs/zh-cn (for Simplified Chinese) and that's it

Now, regarding sidebar and the translations of titles — nothing extra has to be done there! If we use internal links (i.e. just names of the files, which must stay the same in all localizations), we get the localized titles out of content frontmatters of translated pages for free. See: https://starlight.astro.build/guides/sidebar/#internationalization-with-internal-links.
P.S.:
I believe that all technical writers and translators must know Markdown and bits of HTML and YAML to be able to figure MDX out in less than an hour, really. And giving more context (i.e. full file instead of the disjoint set of strings/lines) to translators is ALWAYS a plus.
Steps

[ ] Migrate the existing pages (almost there, only need to replace React Components such as <Callout> where appropriate)
[ ] Convert the index page
[ ] Send a PR integrating the new docs to this repo:
Gradually deprecate tact-docs repo, while keeping the list of issues stored there for a little while

By default, there's no highlighting of inline code blocks and no existing plugins for it yet. Local implementation went rather smooth, wasn't a big deal

What does it mean "Local implementation went rather smooth"?

What does it mean "Local implementation went rather smooth"?

Under that I meant that I just wrote a small rehype plugin (a single file with <100 lines with comments) and included it into the astro.config.mjs. Tested, debugged, and then achieved the same (theme and all) inline code highlighting, as it's seen in Nextra framework in the current Tact docs


New Tailer lacks search option

Forgive me if I missed something but to search the tailer (which is admittedly inefficient but kind of ncie) I have to click switch back to old tailer? Is this deliberate?

The goal is to eventually add it. The new tailer was first focused on performance. We have not gotten the time to go back in and add filtering yet (which is why the old tailer is still there as well)


Task-based backtracing

Write a new tracer called BackTraceTracer. In the StartTask method, record the task in the dictionary. In the EndTask method, simply delete the task. Add a DumpBackTrace method, which takes a task (current task) as an argument. Print the current task. Then, recursively print the parent tasks.


Does not generate same paths on Mac and Windows

I'm working on a React Boilerplate: https://github.com/VincentCharpentier/boilerplate-react
I've seen my build and run tasks fail because of relative paths generated by babel-plugin-root-import.
this plugin is configured in .babelrc file like so:
["babel-plugin-root-import",
  {
    "rootPathSuffix": "shared"
  }
]

So ~/something should lead to ${projectRoot}/shared/something
On MacOS (10.13.2) everything is fine and the plugin do the job. However, on Windows (10) it fails.
Server-side error
The server is started with npm run start (or start:local). The first file to be called is ${projectRoot}/server/server.js
It resolves ~/router/MainRouter to ${projectRoot}/server/shared/router/MainRouter instead of ${projectRoot}/shared/router/MainRouter
So I get this error:

Error: Cannot find module './shared/router/MainRouter'

Build-time error
The build operation is started with  npm run build (or build:local). The first file to be called is ${projectRoot}/client/client.js
It resolves ~/router/MainRouter to ${projectRoot}/client/shared/router/MainRouter instead of ${projectRoot}/shared/router/MainRouter.
So I get this error:

Module not found: Error: Can't resolve './shared/router/MainRouter' in 'C:\www\boilerplate-react\client'

For what I understand with these errors is that the directory of my first file (client or server) is considered as the root directory of my project, which is wrong.
Do you have any suggestions to fix this without breaking any other features ?
Thank you for your time and help

I believe this is fixed now, but I'm unable to test.


Send handshake for heartbeat/2 if no block - develop

Change Description

Send handshake message if we have not seen or sent a block for heartbeat/2.
Always send handshake message even if it has not changed since it was last sent.

Change Type
Select ONE:

[ ] Documentation

[x] Stability bug fix

[ ] Other

[ ] Other - special case

Testing Changes
Select ANY that apply:

[ ] New Tests

[ ] Existing Tests

[ ] Test Framework

[ ] CI System

[ ] Other

Consensus Changes

[ ] Consensus Changes

API Changes

[ ] API Changes

Documentation Additions

[ ] Documentation Additions

https://github.com/EOSIO/eos/pull/10627


Add link to Medium

Thanks for the tutorial! The dad joke took me a second and then got the expected groan - well played. 😉
One note on the article: In the Setup section, you're linking to Oracle's JDK, but that's not free to use in prod, so I recommend to link to jdk.java.net instead.

Thank you thank you 😁 and that's a good point! Good looking out

Thank you thank you 😁 and that's a good point! Good looking out